bug_id,comment_date,comments
1653407,2017-01-01 07:03:41 UTC,ubuntu default setting.please
1653413,2017-09-25 09:47:57 UTC,For Greeter it was handled here: https://github.com/elementary/greeter/pull/71
1653413,2017-09-25 09:48:42 UTC,For Camera it was handled here https://github.com/elementary/camera/pull/40
1653413,2017-09-25 09:47:19 UTC,For Slinghshot it was handled here: https://github.com/elementary/applications-menu/pull/43
1653413,2017-01-10 16:17:28 UTC,Unmarking Photos since it has a more specific report here: https://bugs.launchpad.net/pantheon-photos/+bug/1654873
1653413,2017-09-25 09:42:37 UTC,In Wingpanel this was handled in https://github.com/elementary/wingpanel/pull/56
1653413,2017-09-25 06:39:50 UTC,In Scratch this was handled in https://github.com/elementary/scratch/pull/223
1653413,2017-09-25 09:43:23 UTC,In the Parental Controls plug this was handled in https://github.com/elementary/switchboard-plug-parental-controls/pull/29
1653419,2020-11-08 09:06:01 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1653419,2021-01-08 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1653420,2017-01-01 12:33:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1653420,2017-01-03 23:01:29 UTC,"Hi Guardfather,"
1653420,2017-01-25 12:24:41 UTC,Posted and updated at https://bugzilla.gnome.org/show_bug.cgi?id=777733
1653421,2017-02-11 15:55:07 UTC,"Now after update to OTA-15, I see two Ubuntu entries. Please see screenshot attached."
1653421,2017-01-23 22:24:40 UTC,"I have this issue, too. On my bq tablet and smartphone."
1653421,2017-01-23 22:22:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653425,2017-01-06 02:31:07 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1653425,2018-05-07 11:17:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653430,2018-03-15 14:51:22 UTC,"@trakatelis
yes, this solve the problem of openstack installed over ESXI but not openstack over baremetal directly. I tried host-model and host-passthrough and both options not working"
1653430,2018-03-14 03:53:00 UTC,After setting
1653430,2018-03-13 14:07:00 UTC,"I still have this problem in newton and above fixes doens't work for me. I have RDO Newton deployed on baremetal server (not ESXI) and every time I boot Cirros or cisco images I get ""Failed to boot error"""
1653430,2017-08-15 16:06:02 UTC,This issue seems similar as reported through
1653430,2017-02-01 21:47:43 UTC,Thank you Mohammed!
1653430,2017-02-01 18:44:45 UTC,"Hi Tim,"
1653430,2017-08-30 15:23:59 UTC,"If your compute host is centos/rhel 7.3 running as a VM on ESXi,
there is a quick fix to have hardware assisted virtualization (virt_type = kvm) work."
1653430,2017-01-11 14:48:19 UTC,I think believe it's the issue with qemu version. causing I am facing the same exact issur. I have launched instance on lab environment where qemu version is previous version  qemu. I even install virt-manager on both environment where different qemu version and I could have created a vm on previous version of qemu but not on the ltest version of qemu.
1653430,2017-01-06 15:00:31 UTC,"Hi there,"
1653430,2017-01-06 01:18:53 UTC,"All my services are normal, just like yours。"
1653430,2017-01-03 20:50:45 UTC,"I am also facing the same issue on vmware fusion and vmware v-center. I have tested on liberty, mitaka, and newton have the same isuue, but when I have deployed on virtual box it's working fine."
1653430,2017-01-04 19:01:54 UTC,"I have run this command egrep -c '(vmx|svm)' /proc/cpuinfo its returning 0
and I have double checked nova.conf file as well where virt_type=qemu,
restart libvirt service but no luck"
1653430,2017-01-04 14:50:34 UTC,"this is the actual output of my nova.conf. I have done this deployment
using packstack. Interesting part is, when I have deployed on virtualbox I
didn't face any issue. On vmwarefusion and vceneter having an issue."
1653430,2017-01-04 13:42:25 UTC,Unfortunately this isn't a valid or supported method for deploying nova-compute.
1653430,2017-02-01 18:08:03 UTC,"I'm having the same issue. Not sure why QEMU would be an invalid or non-supported manner of starting an instance (as mentioned in #3 as a reason to invalidate the bug), as kvm is an accelerator. Nice feature, but should not be essential.  This would also be indicated by this setting being in the /etc/nova/nova.conf file - using qemu would be a valid type of hypervisor. The file actually says this:
# Allowed values: kvm, lxc, qemu, uml, xen, parallels"
1653445,2017-01-02 22:25:50 UTC,Hello
1653446,2017-01-01 20:41:17 UTC,"confirmed on Windows 10, using Inkscape 0.92pre5 r15287."
1653448,2019-07-23 05:42:18 UTC,The version of xfce4-settings in the proposed pocket of Cosmic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1653448,2019-06-28 19:29:19 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1653448,2019-03-29 09:47:51 UTC,"Hello Kev, or anyone else affected,"
1653448,2019-03-27 01:20:06 UTC,Uploaded package version 4.13.4-1ubuntu1.18.10.1
1653448,2019-03-27 01:17:08 UTC,Attaching cosmic debdiff.
1653448,2019-03-05 21:44:19 UTC,This bug was fixed in the package xfce4-settings - 4.13.4-1ubuntu2
1653448,2018-10-24 18:02:24 UTC,*** Bug 13317 has been marked as a duplicate of this bug. ***
1653448,2018-10-23 23:58:14 UTC,Fix applied with the below commit.
1653448,2019-01-20 18:56:42 UTC,*** Bug 14879 has been marked as a duplicate of this bug. ***
1653448,2018-10-03 20:00:30 UTC,*** Bug 14732 has been marked as a duplicate of this bug. ***
1653448,2018-02-25 18:06:43 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1653448,2018-03-20 15:24:33 UTC,Scrolling works if you click on the mouse wheel and keep scrolling it
1653448,2018-03-17 21:41:24 UTC,"Yes, it affects any scrolled window of plugged gtk3 dialogs.
The workaround I found is to click (left or right) and hold on any part of the scrolled window then mouse wheel works.
After the mouse button is released, it'll briefly work. I suspect it's not an issue about events passage, but related to focus."
1653448,2018-03-17 14:12:25 UTC,New upstream bug reported for xfce4-settings
1653448,2018-03-17 14:11:33 UTC,Scrolling with mouse fails in some plugins.
1653448,2018-03-01 12:24:02 UTC,"Per the upstream bug, this affects xfce4-settings."
1653448,2018-03-01 12:22:45 UTC,Also affects bionic.
1653448,2018-10-23 14:12:17 UTC,Another workaround:
1653455,2017-02-01 16:09:05 UTC,"Sorry - I need to come back and update this bug. The package built fine in my ppa, and installed OK on my Xenial system. But running vagrant fails with a similar/same error to that listed in the Debian Bug that was closed with this version of vagrant. I need to find some time to report back properly."
1653457,2017-01-01 20:22:43 UTC,"output from ""cat /proc/bus/input/devices"""
1653457,2017-01-01 20:23:54 UTC,"output from ""/usr/bin/evtest /dev/input/event15"""
1653457,2017-01-01 20:28:22 UTC,"output from ""xev | grep -i button"" (recorded at the same time as the evtest output)."
1653457,2017-01-01 20:29:36 UTC,"output from ""xinput -list-props 14"""
1653457,2017-04-20 02:28:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653459,2017-01-04 12:34:24 UTC,"If I reconect the mouse, lag disappears."
1653476,2019-03-02 13:47:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653478,2017-01-02 17:16:25 UTC,Just stumbled upon this:
1653478,2017-01-03 04:10:28 UTC,"- which version did you use?

> python-swiftclient 3.2.1.dev9
> swift 2.12.0 (cbb99f97b02857dd638b0d61f5e19b584037b25f)
"
1653478,2017-01-03 05:45:51 UTC,@Christian
1653478,2017-01-03 09:06:02 UTC,"In your case you are setting the quota first, and then do a request with the same user.
However, that user must be an user with reseller rights, otherwise setting the quota would be not allowed. At the same time a user with reseller rights will always bypass the quota check. This is why you can exceed the quota."
1653478,2017-01-03 12:35:17 UTC,Ahh! That was my mistake. I was trying to upload an object with reseller_admin rights. Didn't noticed that quota is bypassed for reseller_admin in the code.
1653478,2017-01-05 16:37:32 UTC,FYI: an older patch https://review.openstack.org/#/c/312603/ Adds support for object count quotas at a storage account level.
1653478,2017-01-16 12:34:44 UTC,@jrichli: I'll go through the patch. Thanks for the info.
1653478,2017-01-02 15:36:19 UTC,I couldn't verify this using the current master branch - it worked as expected in my quick test.
1653481,2017-01-02 10:16:23 UTC,Repo case. Compile with gcc main.cpp -ldl
1653488,2017-03-29 05:30:40 UTC,"Yes, it is confusing users. I think we're supposed to change the name or the way to describe it. It's really ambiguous."
1653489,2017-01-04 20:35:34 UTC,But ipr.ko is already included. There must be some other missing boot essential module.
1653489,2017-01-02 08:59:16 UTC,"------- Comment From <email address hidden> 2017-01-02 03:57 EDT-------
Screening the issue."
1653489,2017-01-03 11:04:56 UTC,"Moving the ipr module from linux-image-extra to linux-image package should resolve this issue as well, no? Essential modules for booting should be kept in the linux-image package, whilst auxiliary can be kept in the -extra package."
1653498,2017-02-27 08:25:46 UTC,The server with kernel 4.9.2 reboots after 2.874 weeks.
1653498,2020-07-01 02:48:47 UTC,"Hi,"
1653498,2019-06-11 08:04:36 UTC,The similar problem is described on github: https://github.com/kubernetes/kubernetes/issues/70229
1653498,2019-06-11 07:52:56 UTC,"Hello,"
1653498,2017-02-27 08:28:33 UTC,kernel-bug-exists-upstream
1653498,2017-02-07 08:52:43 UTC,"We installed the 4.9.2 kernel a few days ago. We are still waiting for crash :)
For now, we have more or less 3.1 weeks of uptime.
I'll keep you posted."
1653498,2017-01-03 15:39:46 UTC,"I thought about this, but I've no idea which buffer fills"
1653498,2017-01-10 16:26:28 UTC,"In the meantime, I compiled the upstream 4.9.2
kernel + ubuntu patches + aufs
Let me know if make sense the test with this kernel version"
1653498,2017-01-10 09:57:13 UTC,"Hi Joseph Salisbury
I installed the upstream kernel but this kernel AUFS miss the support that's needed by our stack.
I also tried to compile the kernel with the upstream AUFS but the online AUFS is too old and patches do not apply correctly and the process goes in error."
1653498,2017-01-05 20:04:02 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1653498,2017-01-02 23:11:25 UTC,A possible interesting data point is that /proc/interrupts CAL interrupts (Function call interrupts) are reaching a 32 bit wrap around.
1653498,2017-01-02 11:30:16 UTC,This change was made by a bot.
1653498,2017-02-03 17:33:57 UTC,What is the latest on this. We are running into a similar problem with kubernetes only the most recent occurrence was in 13 days. Did upgrading the kernel to 4.9.2 work?
1653499,2017-01-09 17:13:37 UTC,@paelzer per the description and syslog this looks to be with Mellanox cards:
1653499,2017-01-08 09:36:22 UTC,which details do you need from my cards and drivers?
1653499,2017-01-05 07:39:34 UTC,"syslog after restart driver:
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Reached target Host and Network Name Lookups.
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Starting Notify NFS peers of a restart...
Jan  5 09:29:24 qa-h-vrt-044 rpc.statd[7847]: Version 1.2.8 starting
Jan  5 09:29:24 qa-h-vrt-044 rpc.statd[7847]: Flags: TI-RPC
Jan  5 09:29:24 qa-h-vrt-044 sm-notify[7846]: Version 1.2.8 starting
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Started Notify NFS peers of a restart.
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Started NFS status monitor for NFSv2/3 locking..
Jan  5 09:29:24 qa-h-vrt-044 kernel: [57029.219054] FS-Cache: Loaded
Jan  5 09:29:24 qa-h-vrt-044 kernel: [57029.236040] FS-Cache: Netfs 'nfs' registered for caching
Jan  5 09:29:28 qa-h-vrt-044 kernel: [57033.623710] mlx4_en: enp65s0: Close port called
Jan  5 09:29:28 qa-h-vrt-044 kernel: [57033.884115] mlx4_en 0000:41:00.0: removed PHC
Jan  5 09:29:28 qa-h-vrt-044 kernel: [57033.885654] mlx4_en: enp65s0d1: Close port called
Jan  5 09:29:28 qa-h-vrt-044 systemd[1]: Stopping ifup for enp65s0...
Jan  5 09:29:28 qa-h-vrt-044 ifdown[7896]: Cannot find device ""enp65s0""
Jan  5 09:29:29 qa-h-vrt-044 ifdown[7896]: Cannot find device ""enp65s0""
Jan  5 09:29:29 qa-h-vrt-044 systemd[1]: Stopped if..."
1653499,2017-01-03 17:49:07 UTC,Thanks for reporting this issue.
1653499,2017-01-06 10:01:21 UTC,"I'd quote something from that thread that I agree to for us I think:
""Up to now our position has been that this problem should be fixed in
libnl, so we have preferred to not patch libvirt for it, but instead get
libnl fixed."""
1653501,2017-01-02 12:21:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/416043"
1653501,2019-09-19 16:52:19 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.opendev.org/416043
Reason: Very old"
1653501,2020-06-02 09:18:02 UTC,Is this still valid? Marking as incomplete - will expire if no update in 6 months.
1653501,2020-06-04 08:55:11 UTC,"60 days, not 6 months!"
1653501,2020-08-04 04:17:16 UTC,[Expired for kolla because there has been no activity for 60 days.]
1653512,2017-01-08 00:35:49 UTC,oops
1653515,2017-01-02 15:36:57 UTC,"Specifically, I think the following should be promoted to Depends:"
1653518,2017-01-03 11:56:20 UTC,Tom Haddon <email address hidden> writes:
1653518,2017-01-03 09:54:42 UTC,"I just ran ""bzr branch lp:mojo"" and ""find . -name '*.deb'"". Comes up empty. What's mojo_0.4.1.tar.gz here?"
1653546,2017-01-05 23:01:40 UTC,"in src/MidiDriver.cpp, line 216 should be;
    diode_events.insert(std::make_pair(diode_event_id_next,diodeev));"
1653546,2020-02-01 20:58:55 UTC,"Hi Milk,
I believe this was resolved in 0.16.1.
https://github.com/rafalcieslak/harmonySEQ/releases/tag/v0.16.1
Also note that this project's development has been moved to GitHub."
1653559,2017-01-03 11:53:51 UTC,apport information
1653559,2017-01-03 11:53:48 UTC,apport information
1653559,2017-01-05 19:57:44 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1653559,2017-01-06 08:11:55 UTC,"Tried with the mainline kernel[0] v4.10-rc2 as suggested.
It fixed the problem, thanks a million."
1653559,2017-01-03 11:53:53 UTC,apport information
1653559,2017-01-03 11:53:46 UTC,apport information
1653559,2017-01-03 11:53:49 UTC,apport information
1653559,2017-01-03 11:53:43 UTC,apport information
1653559,2017-01-02 22:00:56 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1653559,2017-01-03 11:53:37 UTC,apport information
1653559,2017-01-03 11:53:39 UTC,apport information
1653559,2017-01-03 11:53:44 UTC,apport information
1653559,2017-01-03 11:53:41 UTC,apport information
1653559,2017-01-03 11:53:42 UTC,apport information
1653559,2017-01-03 11:53:40 UTC,apport information
1653560,2017-01-03 17:30:17 UTC,"See:
https://www.smartmontools.org/wiki/FAQ#Whyismydisktemperaturesreportedbysmartdas150Celsius"
1653560,2017-01-04 05:44:57 UTC,Normalization seems to be:
1653560,2017-01-04 08:36:04 UTC,Filed a new issue upstream at https://www.smartmontools.org/ticket/788
1653560,2017-01-04 09:53:19 UTC,Upstream issue got closed without a fix.
1653561,2017-01-10 04:33:53 UTC,"Yeah, centos6 should just be removed.  We stopped testing with [1].  I don't think there's any compelling reason to keep it, since py2.6 was dropped in Juno"
1653562,2018-11-30 08:29:47 UTC,"controller logs on the ERROR, as per bug 1805990"
1653562,2018-11-30 08:30:02 UTC,This bug is still present on 2.4.5.
1653562,2017-05-10 04:32:06 UTC,This can also occur during charm upgrades.  Retrying the upgrade usually works:
1653562,2017-02-17 08:32:00 UTC,Removing 2.1 milestone as we will not be addressing this issue in 2.1.
1653562,2018-09-25 22:41:05 UTC,"I ran into this today with a couple of 2.4.3 controllers, e.g.:"
1653572,2017-01-04 03:57:51 UTC,It sounds to me like you should reach out to Dell support. Considering your description (temperature and the erraticness of the touchpad device appearance) one shouldn't rule out a hardware issue.
1653574,2017-01-12 23:42:28 UTC,"Chiming in to hopefully get bug #1418274 resolved, maybe the importance can be increased as these remnants and left behind items make deployment situations tricky."
1653574,2019-06-09 13:23:58 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape/issues/300
1653577,2020-01-10 10:42:04 UTC,"Cannot this be addressed by adjusting the umask in the host before starting QEMU ? And maybe also by adjusting the umask inside the guest if using the ""passthrough"" or ""none"" security model of the ""local"" fsdev backend ?"
1653577,2020-03-12 04:17:16 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1653593,2017-01-03 05:42:16 UTC,Workaround:  systemctl stop lightdm
1653595,2017-09-01 16:16:12 UTC,Unassigning due to no activity for > 6 months.
1653597,2019-11-12 23:26:31 UTC,I just looked at the test results for this test suite across some GCP cloud instances and it looks like it's failing across the 4.15 kernels.
1653597,2018-11-13 21:52:04 UTC,This issue still exists 4.15.0-1031.32
1653597,2018-09-13 10:40:38 UTC,This issue still exists for 4.15.0-1019.20~16.04.1-gcp [1](every nodes for GCP) and 4.15.0-1022.22~16.04.1-azure [2] (some nodes for Azure)
1653597,2018-09-12 18:15:06 UTC,"This appears to be related to Azure giving the context of the bug, tagging as such, next is this still an issue to date?  if not, has there been a test generated to test for this specific issue in the future?  or can we forget it?"
1653597,2017-07-14 11:23:23 UTC,"For the record, it's found on linux-azure 4.11.0-1003 as well."
1653597,2017-05-22 10:13:29 UTC,"This bug also affects the -azure kernel:
http://kernel.ubuntu.com/testing/4.10.0-1005.5-azure/libhugetlbfs-4.10.0-1005.5-x86_64%20(azure)-index.html"
1653597,2017-02-17 10:26:37 UTC,I can't collect information as I don't have access to cloud instances yet.
1653597,2017-01-03 10:16:36 UTC,This failure can be found on Xenial kernel 4.4.0-58.79 on gce as well.
1653597,2017-01-03 06:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1653597,2017-05-31 19:11:05 UTC,"Also seen on 4.11 in artful. The assertion seems to be related to internal heap bookkeeping, so likely a glibc error or heap corruption and not a kernel problem."
1653598,2017-02-04 08:59:45 UTC,"Change abandoned by xhzhf (guoyongxhzhf@163.com) on branch: master
Review: https://review.openstack.org/416135"
1653601,2017-06-22 04:35:17 UTC,"Architecture: x64
Operating System & version: win7 ultimate SP1
Installation Method: setup .exe
OS language: ru_RU
Version of Openshot installed : OpenShot-v2.3.1-x86_64.exe
OpenShot language: default"
1653601,2017-06-22 04:47:45 UTC,"Architecture: x64
Operating System & version: win7 pro 6.1.7601 Service Pack 1 build 7601
Installation Method: setup .exe
OS language: ru_RU
Version of Openshot installed : OpenShot-v2.3.4-x86_64.exe
OpenShot language: default"
1653610,2017-01-03 19:00:18 UTC,"If user passes non-existing segment id to the ""host show"" command, then user should get proper error message saying ""no failover segment with id <id>"" instead of ""host not found: <hostname>"" as it might confuse user if host name passed to the command is really existing."
1653610,2017-02-28 09:51:25 UTC,This is what I got on masakariclient:
1653614,2017-01-03 07:21:20 UTC,"Even when changing the test to 'assertraises' it still fails, so something else must be going on ..."
1653621,2017-02-01 03:26:42 UTC,This may be another glPixelStorei mistake (or lack thereof).
1653621,2017-04-24 06:56:45 UTC,The Android platform was deleted from lp:mir at revision 4155.
1653625,2017-04-24 06:58:15 UTC,The Android platform was deleted from lp:mir at revision 4155.
1653632,2017-01-03 17:16:05 UTC,Is https://bugs.launchpad.net/podbird/+bug/1590277 a duplicate of this?
1653632,2017-01-03 13:14:52 UTC,"Seems to have fixed itself after downloading one new episode, now all episodes have the paper clip icon and i could delete them...strange"
1653632,2017-01-03 15:06:09 UTC,"Hi, thanks for taking the time to report this bug. I have personally noticed that the UI does not refresh when I have downloaded an episode (paper clip icon does not appear) until I restart podbird. In the backend, the episode has indeed been downloaded. Its just the UI that doesn't reflect the change."
1653635,2017-03-01 11:21:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653635,2020-10-20 12:31:04 UTC,"Hello, as workaround, using pkg-config to detect it should work
pkg_search_module(JSONCPP jsoncpp)"
1653636,2017-01-03 10:51:00 UTC,apport information
1653636,2017-01-11 10:04:45 UTC,"Thank you Joseph, the upstream kernel from months ago was the cause of the issue.  I had completely forgotten about it being there and did not recognise the change in version numbering as significant."
1653636,2017-01-11 09:06:28 UTC,"I expect I got the kernel the same way I get most of my kernels, though an `apt-get upgrade`.  Although I did try and compile a kernel a while ago... I wonder if that got left around as an install option and it was so long since I last rebooted I forgot about it!"
1653636,2017-01-05 19:35:18 UTC,Where did you happen to get the 4.4.21 kernel?  That is an upstream kernel and not an official Ubuntu kernel like 4.4.0-57.
1653636,2017-01-03 10:55:03 UTC,I have executed the command `apport-collect 1653636` as requested by brad-figg.  I can see that log files have been added.
1653636,2017-01-03 10:51:04 UTC,apport information
1653636,2017-01-03 10:51:03 UTC,apport information
1653636,2017-01-03 10:51:02 UTC,apport information
1653636,2017-01-03 10:50:59 UTC,apport information
1653636,2017-01-03 10:51:05 UTC,apport information
1653636,2017-01-03 10:50:57 UTC,apport information
1653636,2017-01-03 10:50:58 UTC,apport information
1653636,2017-01-03 09:35:49 UTC,As an upgrade from one kernel to the other seems to have brought about this problem I am attaching the recent /var/log/apt/term.log file.
1653636,2017-01-03 10:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1653636,2017-01-03 10:50:51 UTC,apport information
1653636,2017-01-03 09:34:25 UTC,As an upgrade from one kernel to the other seems to have brought about this problem I am attaching the recent /var/log/apt/history.log file.
1653636,2017-01-03 10:50:52 UTC,apport information
1653636,2017-01-03 10:50:54 UTC,apport information
1653636,2017-01-03 10:50:55 UTC,apport information
1653636,2017-01-03 10:50:56 UTC,apport information
1653636,2017-01-03 09:30:30 UTC,I did not choose the virtualbox package when opening this bug.  I wanted to choose some kind of kernel or smp related package but did not know what one to select.
1653640,2017-01-03 15:02:41 UTC,"Thanks for taking the time to report this bug. Firstly we need to indeed come up with a ""mark as read"" icon since it conflicts with the ""select all"" icon used by many ubuntu touch apps. Otherwise this should be rather easy to fix."
1653649,2017-01-10 01:57:57 UTC,Can you please file these issues with upstream?
1653649,2017-01-10 05:34:40 UTC,"https://github.com/mdadams/jasper/issues/89
https://github.com/mdadams/jasper/issues/88"
1653650,2017-06-17 10:49:32 UTC,"confirmed on Windows 10, Inkscape 0.92.1 r15371"
1653650,2017-08-13 13:10:06 UTC,"merged with trunk in gitlab rev:
https://gitlab.com/inkscape/inkscape/merge_requests/39"
1653650,2017-06-30 17:28:45 UTC,attached is a modified version of the file summersnight.py. This will fix the Modify Path->Envelope extension in the same way as the perspective extension.
1653650,2017-06-30 16:24:33 UTC,"attached is a proposed fix for this bug. The new code compensates for the viewbox size using essentially the same method as hpgl_encoder.py
   I will leave this code here for a few days for testing purposes before proposing a merge."
1653650,2017-06-16 23:37:22 UTC,"Still broken in trunk and 0.92.1 (but I cannot reproduce the fix by setting scale to 1.0, neither with px nor with mm)."
1653650,2017-01-03 10:14:14 UTC,I tested this on a Windows 7 machine.
1653650,2017-01-03 18:17:47 UTC,Please attach a test case (Inkscape SVG file created with Inkscape 0.92pre5 before and after applying the extension) to allow further investigation of the reported issue.
1653650,2017-01-03 17:45:21 UTC,I used the 7zip file to test and not the installer.
1653650,2017-01-03 17:29:39 UTC,"In the document properties of default.svg in the pre5 release the ""scale"" setting is not set to 1.00
When I change this to 1.00 the strange behavior with perspective disappears."
1653650,2017-01-03 12:44:35 UTC,"This is likely the same issue as reported earlier in
* Bug #1508400 “inkex.py: support arbitrary (but uniform) document scale (0.92)”
  https://bugs.launchpad.net/inkscape/+bug/1508400
It is exposed in Inkscape >= 0.92(preX) when applying certain extensions in SVG documents created with viewBox/viewport dimensions based on 90dpi (either with Inkscape 0.91, or e.g. based on custom user templates originating from Inkscape 0.91)."
1653650,2017-01-03 12:09:07 UTC,thank you for taking the time to issue a report.
1653650,2017-01-04 08:35:36 UTC,"In the first file perspective-scale-wrong.svg, the scale is set to the default
in default.svg (90/96 = 0.9375) then the perspective extension gives the
wrong result."
1653659,2020-10-29 12:02:11 UTC,"Replicated-ish. Note that in versions before 0.91, it fails to save as pdf entirely. However 0.91-1 (windows 10) seems to export well"
1653659,2017-01-06 10:32:44 UTC,"Also tested on 14.04 Inkscape 0.92.0 15301 (snap build).
The same problem occurs: rasterized output of 1.4MB instead the 66kB vectorized file."
1653659,2017-01-03 15:28:53 UTC,"Tested on Windows XP (32-bit) with lp:inkscape/0.92.x rev. 15302. The SVG document opens correctly, but Inkscape crashes when trying to save it as PDF."
1653659,2017-01-03 13:55:32 UTC,"Hi Hachmann.
IF you zoom the pdf image, (at least in my evince) it appears a bitmap file.
However, the inkscape on windows produces a standard vectorized PDF of 66.2KB."
1653659,2017-01-03 13:09:16 UTC,"Tested (export and import via GUI) on Ubuntu 16.04 base, can't reproduce.
The pdf *is* indeed 1.4 MB, but it does contain vector data, when I open it again with Inkscape (which takes minutes to load, for some weird reason)."
1653660,2017-01-06 16:53:39 UTC,"Hi,"
1653664,2017-01-31 12:05:14 UTC,"Change abandoned by Oksana Voshchana (<email address hidden>) on branch: master
Review: https://review.openstack.org/414557
Reason: resolve in generic_switch"
1653668,2017-01-03 12:19:47 UTC,"root cause should be fixed by https://review.fuel-infra.org/#/c/29641/
in two words: we made a mistake some time ago by putting jjb variable inside not templated job, where variables doesn't work, so 'recheck' keyword wasn't parsed properly."
1653668,2017-01-03 12:20:21 UTC,"Reviewed: https://review.fuel-infra.org/29641
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1653671,2017-01-03 11:42:36 UTC,I am going to add a notice about this behavior
1653671,2018-01-24 22:38:14 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-837
1653673,2019-01-11 06:02:54 UTC,"I have the same issue. When converting PDF to SVG with Inkscape Command line(with and without text as path both) text is not rendering as in PDF, in SVG."
1653673,2017-01-03 14:43:27 UTC,"The PDF import option 'Import via Poppler' (aka 'Poppler/Cairo import' in upcoming Inkscape 0.92) is not available via command-line in Inkscape (related feature request: bug #1507740) - on Linux, you can use the standalone binary 'pdftocairo' installed with the poppler library instead (it does the same as Inkscape's 'Import via Poppler' option). The command-line tool 'pdftocairo' is not part of Inkscape, and likely not easily available for Inkscape users on Windows."
1653673,2017-01-03 14:03:46 UTC,"When option ""Import via Poppler"" is checked, it seems that italic property is kept."
1653673,2017-01-04 10:31:56 UTC,"It seems that for PDF including bookmarks, SVG conversion is NOT done properly."
1653673,2017-01-03 13:52:10 UTC,Please find example of typical PDF including red text in italic.
1653673,2017-01-03 13:38:05 UTC,Please attach a test case (PDF file) which exposes the reported issue to allow further investigation on other systems. Please also provide any known details about fonts required to be installed locally (Inkscape does not use fonts embedded in PDF files).
1653673,2017-01-03 13:01:12 UTC,"Does it work correctly if you do it via the interface, and check the *import via poppler* option? (uncheck for comparison, to see if this only affects command line)"
1653673,2017-01-03 13:53:27 UTC,Text items are in Arial.
1653674,2017-01-03 11:42:31 UTC,openstack version - 13.1.1
1653679,2017-01-03 12:56:59 UTC,Isn't the printer page orientation a setting that needs to be made when sending data to the printer?
1653679,2017-01-04 07:41:09 UTC,"seems related - as when you print on labels, which haves landscape orientation by default inkscape /only/ makes that incorrectly as rotating image. seems make check that setting Landscape /that will be onscreen normaly visualisation for labels 104x90mm as sample/ but for printer 104x90 really is Portrait mode but data sent rotated ... so cutting and displacement occurs."
1653679,2020-07-08 16:27:04 UTC,"As Maren noted (#1), the orientation is only used for changing the dimensions of the page on canvas (isn't used by the printer)."
1653682,2017-01-23 01:53:25 UTC,I push a new version of wikia. Could you try it now?
1653686,2017-02-10 09:46:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653686,2017-02-10 09:52:04 UTC,The performance problems also affects Firefox (current and past versions) but not as bad as Chrome. The issue is caused by a very inefficient handling of the zlib decompression window. Upstream fixed the problem by replacing the zlib library with an efficient one.
1653686,2017-02-10 09:52:43 UTC,vnc-jsunzip-ring.js.patch is a proper fix uses the decompression window as a ring buffer thus avoiding any problems with limiting the window size.
1653686,2017-02-10 12:28:35 UTC,"The attachment ""vnc-perffix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1653687,2017-01-22 10:36:04 UTC,The sound comes back after suspending the machine with `sudo pm-suspend`.
1653687,2017-01-10 18:59:28 UTC,Any news on this bug? It's quite annoying to lose all sound...
1653687,2017-03-08 18:32:30 UTC,"Updated to 17.04, issue is still there. I think it comes from alsa driver instead of pulseaudio."
1653687,2017-01-03 12:38:54 UTC,PulseAudio log taken while the issue occurred
1653687,2017-01-03 16:28:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1653687,2017-01-03 12:38:28 UTC,Information generated by the also-info.sh script
1653693,2017-01-05 14:54:24 UTC,There is an issue in python-novaclient==7.0.0 package/
1653693,2017-01-06 15:11:36 UTC,"Vladimir,"
1653693,2017-01-09 05:17:23 UTC,"@Roman, as I mentioned - 6.0.0 works fine and it uses ""project_id"" too - https://github.com/openstack/python-novaclient/blob/6.0.0/novaclient/client.py#L836"
1653693,2017-01-09 12:34:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417858"
1653693,2017-01-10 10:27:37 UTC,">>> There is an issue in novaclient somewhere in session initialization. Fast solution is to pin novaclient<7.0 version, good fix - move OSTF to keystone session instead of user-password auth (and pin novaclient>=7.0 after this)"
1653693,2017-01-10 15:25:44 UTC,"Reviewed:  https://review.openstack.org/417858
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=e71059ac4d6546c153b7229d4d7763564c6cdf1f
Submitter: Jenkins
Branch:    master"
1653693,2017-02-27 16:26:30 UTC,This issue was fixed in the openstack/fuel-ostf 11.0.0.0rc1 release candidate.
1653694,2017-01-03 13:12:45 UTC,This element causes Inkscape to render the document blank:
1653694,2017-01-03 13:22:22 UTC,"Based on tests with archived builds (on OS X 10.7.5):
- not reproduced with Inkscape 0.48.5 r10040,
- not reproduced with lp:inkscape rev <= 10578,
- reproduced with lp:inkscape rev >= 10579,
- reproduced with Inkscape 0.91 r13725,
- reproduced with lp:inkscape/0.92.x rev 15301;
the reported symptom (blank canvas triggered by geometry of a single element) seems to have been exposed with the merge of the rendering cache branch in r10579:
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/changes/10579
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/10579"
1653694,2017-01-03 14:29:11 UTC,"Similar symptoms (blank canvas due to geometry/computed dimensions of a single object) are tracked in bug #1475875, bug #1565174."
1653694,2020-05-06 20:16:56 UTC,"Hi, this isue has been reported to Gitlab: https://gitlab.com/inkscape/inkscape/-/issues/1446"
1653695,2017-01-03 19:50:43 UTC,"Hello again,"
1653695,2017-01-03 22:45:25 UTC,"So I've just changed them to: ""save,saveAs"" and now have both icons appearing again."
1653703,2017-01-04 18:20:09 UTC,For now I added to /etc/profile  line
1653703,2017-01-04 16:12:11 UTC,"Funny is, becase ""echo"" is in /bin and working,
maybe somewhere is link."
1653703,2017-01-04 16:03:00 UTC,"Sorry maybe is not empty, but I have missing /bin in $PATH with only Lightdm"
1653704,2017-03-16 15:38:01 UTC,"Martin,"
1653707,2017-01-04 20:41:52 UTC,"Confirmed on Windows XP (32-bit), Inkscape 0.48.5, 0.91 and 0.92.
The hatches show correctly when open in LibreCad."
1653709,2017-01-03 13:49:47 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/416240"
1653709,2017-01-04 11:04:08 UTC,"Reviewed:  https://review.openstack.org/416240
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=62caab191192bebc9165008bb84e67a50701b5ca
Submitter: Jenkins
Branch:    stable/newton"
1653718,2017-06-05 16:19:09 UTC,"Driving any logic off the return value of migrateToURI* is really a bad idea. When migrateToURI* fails, there are many different states the VM can be in on either the src/dst host, and the migrateToURI return status gives no useful info about which applies. Migration might even have 100% succeeded, despite migrateToURI returning an error. This is why Nova stopped looking at migrateToURI error status and switched to the job info records, to solve https://bugs.launchpad.net/nova/+bug/1414065"
1653718,2017-06-27 19:27:47 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1653718,2017-06-29 11:43:49 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1653718,2017-08-01 09:53:50 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/409261
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1653718,2017-08-03 13:13:13 UTC,"Change abandoned by sahid (<email address hidden>) on branch: master
Review: https://review.openstack.org/409260"
1653718,2017-08-03 13:13:21 UTC,"Change abandoned by sahid (<email address hidden>) on branch: master
Review: https://review.openstack.org/409261"
1653723,2017-08-28 15:47:33 UTC,Just a note that this bug is opened against the upstream neutron-lbaas-dashboard project. The Ubuntu neutron-lbaas-dashboard bug is being tracked in https://bugs.launchpad.net/ubuntu/+source/neutron-lbaas-dashboard/+bug/1709604.
1653723,2017-08-22 17:59:41 UTC,Original commit:
1653723,2017-03-14 17:24:47 UTC,Seems both are there:
1653723,2017-01-14 01:01:51 UTC,"same here.
and when created a load balancer, it actually show up in ""load balancers"" instead of ""load balancers v2"""
1653723,2017-03-13 22:10:31 UTC,"Can you make sure that the ""_1480_project_loadbalancersv2_panel.py"" is not installed in the horizon/openstack-dashboard/enabled directory?  Only ""_1481_project_ng_loadbalancersv2_panel.py"" should be present."
1653724,2017-01-04 10:57:46 UTC,"2017-01-01T12:30:17.825911+00:00 err:  2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi [req-3627c6c9-e1b5-441e-bd7a-c5db3e5b4d81 - - - - -] (_mysql_exceptions.OperationalError) (1047, 'WSREP has not yet prepared node for application use') [SQL: u'SELECT local_user.id AS local_user_id, local_user.user_id AS local_user_user_id, local_user.domain_id AS local_user_domain_id, local_user.name AS local_user_name, anon_1.user_id AS anon_1_user_id \nFROM (SELECT user.id AS user_id \nFROM user \nWHERE user.id = %s) AS anon_1 INNER JOIN local_user ON anon_1.user_id = local_user.user_id ORDER BY anon_1.user_id'] [parameters: ('1ef2d18daa894a63bad8c441cbe46e80',)]
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi Traceback (most recent call last):
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi   File ""/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py"", line 249, in __call__
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi     result = method(context, **params)
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi   File ""/usr/lib/python2.7/dist-packages/oslo_log/versionutils.py"", line 165, in wrapped
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi     return func_or_cls(*args, **kwargs)
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi   File ""/usr/lib/python2.7/dist-packages/keystone/token/controllers.py"", line 100, in authenticate
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi     context, auth)
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi   File ""/usr/lib/python2.7/dist-packages/keystone/token/controllers.py"", line 303, in _authenticate_local
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi     password=password)
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi   File ""/usr/lib/python2.7/dist-packages/keystone/common/manager.py"", line 124, in wrapped
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi     __ret_val = __f(*args, **kwargs)
2017-01-01 12:30:17.807 28387 ERROR keystone.common.wsgi   File ""/usr/lib/python"
1653725,2017-01-03 16:30:13 UTC,What are the permissions on /var/lib/lxc on such devices?
1653725,2017-01-04 09:32:27 UTC,"Looking at my krillin from the recovery, /var/lib/lxc looks like this:
Access: (0700/drwx------)  Uid: (    0/    root)   Gid: (    0/    root)"
1653725,2017-01-04 15:07:05 UTC,"Thanks. I think the problem is a newly introduced check for path writeability which is harmless and in fact, potentially useful in just about all cases but the weird Ubuntu Phone case where / is read-only, confusing that check."
1653725,2017-01-04 22:49:27 UTC,This bug was fixed in the package lxc - 2.0.6-0ubuntu5
1653725,2017-01-05 00:57:34 UTC,This was fixed upstream and included in our stable branch. A cherry-pick was uploaded to Zesty and all tests were run successfully against it.
1653725,2017-01-05 09:12:24 UTC,Thanks! Greatly appreciated guys. I'll kick a test xenial image as soon as it's available.
1653725,2017-01-05 10:34:47 UTC,"Hello Łukasz, or anyone else affected,"
1653725,2017-01-05 10:36:13 UTC,"Hello Łukasz, or anyone else affected,"
1653725,2017-01-05 16:19:40 UTC,"I was able to test this on a m10 tablet. The fix seems to have gone through to the cooler image I was trying to test - r13 in ubuntu-touch/staging/bq-aquaris-pd.en, and now no longer hangs on install."
1653725,2017-01-18 20:54:43 UTC,"The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1653725,2017-01-18 20:55:02 UTC,This bug was fixed in the package lxc - 2.0.6-0ubuntu1~ubuntu16.10.2
1653725,2017-01-18 21:04:46 UTC,This bug was fixed in the package lxc - 2.0.6-0ubuntu1~ubuntu16.04.2
1653727,2019-05-17 09:59:15 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016."
1653729,2017-01-11 01:26:17 UTC,"Hi,
I gave an email about these issues to the maintainer of the project. And he
says xxxdecode.c are just test programs, so he refused to give them
patches.
I am a new to fuzzing and reporting bugs, Could you please tell how can I
handle these issues then?"
1653729,2017-01-11 02:14:27 UTC,"Hi Bobb,"
1653729,2017-01-10 20:27:09 UTC,"Nice find. I suspect this wouldn't have actual security consequences but it would be worth fixing, if only so that future fuzz runs don't trip it again. Could you please report this to upstream (probably via http://foo2zjs.rkkda.com/forum/ , I didn't see any other way to report issues to them), and link the topic here?"
1653733,2017-01-12 20:29:06 UTC,Can you paste the entire ~/.cache/conjure-up/conjure-up.log and also a little more specific as to what you are installing? Autopilot isn't installed through conjure-up on 16.04
1653733,2017-01-19 11:45:22 UTC,"Hello Adam,"
1653733,2017-01-19 12:17:31 UTC,How do I have to install Autopilot and testing Landscape and Openstack on Ubuntu 16.04Lts?
1653737,2017-04-06 07:06:38 UTC,Verified on 10.0 build #1571.
1653737,2017-01-10 06:14:39 UTC,Verified on 9.2 snapshot #741.
1653737,2017-01-30 17:06:59 UTC,Error was not reproduced. Move task to previous state.
1653737,2017-01-30 13:21:14 UTC,I've checked the log and see strong connection problem between master node and node. Astute try to connect and check status of node from
1653737,2017-01-30 10:52:17 UTC,Diagnostic snapshot: https://drive.google.com/open?id=0B6E70aHvCcRQTXg4a20zRF84SWs
1653737,2017-01-30 10:42:35 UTC,Reopening this bug for 9.2.
1653737,2017-01-06 13:36:52 UTC,"Reviewed:  https://review.openstack.org/417358
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=0497a610d2deeee528ea3af68cd95b1b8165dd41
Submitter: Jenkins
Branch:    stable/newton"
1653737,2017-02-27 16:26:59 UTC,This issue was fixed in the openstack/fuel-astute 11.0.0.0rc1 release candidate.
1653737,2017-01-06 12:02:34 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/417359"
1653737,2017-01-03 16:22:18 UTC,Another failure - https://product-ci.infra.mirantis.net/job/9.x.main.ubuntu.bvt_2/708/
1653737,2017-01-04 11:05:53 UTC,We encouter the same issue here as we had here https://bugs.launchpad.net/fuel/+bug/1644618
1653737,2017-01-04 14:55:25 UTC,"It seems that it recovered from the problem above and, the reason is a bit different:"
1653737,2017-01-06 13:35:43 UTC,"Reviewed:  https://review.openstack.org/417359
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=1b2bf8eaeec647cb1810347ebd4bdf96b0055c8e
Submitter: Jenkins
Branch:    stable/mitaka"
1653737,2017-01-05 14:34:41 UTC,BVT failed again:
1653737,2017-01-06 11:53:24 UTC,"Reviewed:  https://review.openstack.org/415860
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=7c0485eb1a8c75a57936eaecce935091659429e9
Submitter: Jenkins
Branch:    master"
1653737,2017-01-06 12:02:21 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/417358"
1653737,2017-01-04 16:23:49 UTC,"Network problem definitely took place, however it seems that there were no retry attempts afterwards:"
1653745,2017-01-03 20:32:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1653745,2017-03-23 16:30:19 UTC,Seems it was caused by DRI3 option enabled in Xorg config file.
1653745,2017-04-17 11:25:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653746,2017-01-03 17:10:11 UTC,"scollins@Sean-Collins-MBPr15 ~ » ssh -v  127.0.0.1 -p 2222                                     255 ↵
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/scollins/.ssh/config
debug1: /Users/scollins/.ssh/config line 11: Applying options for *
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 102: Applying options for *
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 2222.
debug1: Connection established.
debug1: identity file /Users/scollins/.ssh/id_rsa type 1
debug1: identity file /Users/scollins/.ssh/id_rsa-cert type -1
debug1: identity file /Users/scollins/.ssh/id_dsa type -1
debug1: identity file /Users/scollins/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
ssh_exchange_identification: Connection closed by remote host"
1653746,2017-01-03 18:08:51 UTC,Setting   config.vm.boot_timeout = 1200 allowed installation to continue. For some reason the guest boots extremely slow.
1653759,2017-04-11 14:10:59 UTC,"This is still affecting the final beta images, as of yesterday, confirmed via automatic and manual testing."
1653759,2017-01-11 21:08:38 UTC,"Not sure if this is related or a separate bug, but when I do a manual install and select encryption, grub fails to install to /dev/vda. When doing a preseeded install, the install finishes but the system never boots."
1653759,2017-01-11 19:35:57 UTC,"The only difference between this and the default preseed (which installs correctly) is that d-i partman-auto/method string is changed from regular to lvm. If I do a manual lvm install, it works, so this appear to be a problem interpreting that preseed directive."
1653763,2017-07-08 14:14:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653764,2018-07-11 08:28:14 UTC,"when truncate table,We have the same problem in 	5.7.21-21-log Percona Server (GPL), Release 21, Revision 2a37e4e.
Linux version 2.6.32-431.20.3.el6.mt20161028.x86_64 (<email address hidden>) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Fri Oct 28 17:50:35 CST 2016
log:
2018-07-06T20:01:18.064913+08:00 0 [ERROR] InnoDB: ibuf cursor restoration fails!. ibuf record inserted to page 3910:31517
2018-07-06T20:01:18.064980+08:00 0 [ERROR] InnoDB: Submit a detailed bug report to http://bugs.mysql.com
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 0
 0: len 4; hex 00000e59; asc    Y;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 0019515f; asc   Q_;;
 3: len 30; hex 000300010c0f000c00e00c0f001000e00c0f000800e00c0f002000e08603; asc                               ; (total 34 bytes);
 4: len 3; hex 303034; asc 004;;
 5: len 2; hex 5052; asc PR;;
 6: len 2; hex 3039; asc 09;;
 7: len 6; hex 2a2a2a2a2a2a; asc ******;;
 8: len 4; hex 8d78f926; asc  x &;;
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 0
 0: len 4; hex 00000e59; asc    Y;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 0019515f; asc   Q_;;
 3: len 30; hex 000300010c0f000c00e00c0f001000e00c0f000800e00c0f002000e08603; asc                               ; (total 34 bytes);
 4: len 3; hex 303034; asc 004;;
 5: len 2; hex 5052; asc PR;;
 6: len 2; hex 3039; asc 09;;
 7: len 6; hex 2a2a2a2a2a2a; asc ******;;
 8: len 4; hex 8d78f926; asc  x &;;
DATA TUPLE: 3 fields;
 0: len 4; hex 00000f46; asc    F;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 00007b1d; asc   { ;;
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 32
 0: len 4; hex 00000f46; asc    F;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 00007b1d; asc   { ;;
 3: len 30; hex 000400010c0f0020802d0c0f000c802d0c0f0014002d0c0f0014002d8608; asc          -     -     -     -  ; (total 34 bytes);
 4: len 6; hex 523150314752; asc R1P1GR;;
 5: len 2; hex 4b4c; asc KL;;
 6: len 3; hex 415448; asc ATH;;
 7: len 3; hex 545045; asc TPE;;
 8: len 8; hex 80000000f29c7f54; asc        T;;
2018-07-06T20:01:18.070471+08:00 0 [ERROR] [FATAL] InnoDB: Failed to restore ibuf position.
2018-07-06 20:01:18 0x7f828f8ca700  InnoDB: Assertion failure in thread 140198730835712 in file ut0ut.cc line 943
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
12:01:18 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/"
1653764,2018-01-25 09:43:38 UTC,"Shahriyar,"
1653764,2018-01-25 09:04:04 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3623
1653764,2017-12-11 09:14:41 UTC,No issues after 7 days running as a 5.6 slave - would appear to be an upgrade issue.
1653764,2017-12-04 13:08:20 UTC,Note going well.
1653764,2017-11-23 10:53:37 UTC,Update
1653764,2018-09-15 22:46:16 UTC,"Had this issue on A REPLACE...SELECT...
I set innodb_flush_neighbors=0 and problem went away."
1653764,2017-06-18 06:09:36 UTC,running: mysqld 5.7.18-14
1653764,2017-06-18 06:04:54 UTC,It looks like we ran into this bug.
1653764,2017-02-09 16:51:28 UTC,"Databases: 256065
Tables: 5212706"
1653764,2017-02-09 10:22:29 UTC,"Emily, how many tables does this instance have in total?"
1653764,2017-01-10 18:57:46 UTC,attaching the innodb status monitor output
1653764,2017-01-04 07:49:00 UTC,This is very non-specific - all it says that something (not clear what) was locked for more than 10 minutes. The bug report needs at least the stacktraces from all the threads and workload details.
1653764,2017-11-21 17:56:21 UTC,"running mysqld 5.7.19-17, as a new slave in a 1 Master 3 slave architecture"
1653764,2017-01-03 19:30:53 UTC,seems similar to http://bugs.mysql.com/bug.php?id=84108
1653774,2017-01-25 18:52:47 UTC,This issue was fixed in the openstack/python-muranoclient 0.12.0 release.
1653795,2017-09-26 22:49:11 UTC,Unassigning due to no activity for > 6 months.
1653796,2017-01-12 02:50:36 UTC,kernel-bug-exists-upstream
1653796,2017-01-12 02:35:58 UTC,possible progress here:
1653796,2017-01-11 19:45:31 UTC,still not showing after reboot with new kernel.  uname -r shows v4.10.
1653796,2017-01-11 19:33:16 UTC,"using ""all"" header package installed ok.
Then after that the image packages for generic and low latency both installed but with error ""Possible missing firmware""
see attached.
haven't reboot yet.."
1653796,2017-01-03 22:30:13 UTC,This change was made by a bot.
1653796,2017-01-11 19:11:54 UTC,First new kernel install attempt failed. See attached.
1653796,2017-01-11 18:56:41 UTC,I will be following the instructions from https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds to try out the newest upstream kernel.
1653796,2017-01-05 19:29:18 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1653796,2017-01-11 19:12:58 UTC,above comment shows that it may have to do with my dual boot system of Centos 7 and Ubuntu Studio.
1653805,2019-09-19 11:55:29 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1653808,2017-05-22 13:36:46 UTC,"%% Creator: Inkscape inkscape 0.92.1, www.inkscape.org
%% PDF/EPS/PS + LaTeX output extension by Johan Engelen, 2010
%% Accompanies image file 'test_text.pdf' (pdf, eps, ps)"
1653808,2017-01-04 21:23:47 UTC,Thanks for taking the time to write a report!
1653808,2017-01-07 11:50:00 UTC,"Or the pdf is multiple times exported. And this as many times plus 1
as text fields are in the SVG exported by LO."
1653808,2017-05-22 13:33:32 UTC,In V0.92 Bug is already existent.
1653813,2017-04-10 14:48:46 UTC,"don't we have ""juju model-defaults"" which is exactly the ""use this setting for all newly created models""."
1653826,2018-10-09 23:28:37 UTC,"Thanks for the confirmation, Brian.
:)
G"
1653826,2018-10-06 14:14:15 UTC,"Hello
Thank you for submitting this bug and reporting a problem with the system-config-printer package.  You made this bug report in 2016 and Ubuntu and the system-config-printer package have been updated since then."
1653826,2018-10-09 16:49:33 UTC,There are a lot of crashes in the Error Tracker about this and Ubuntu 18.04.
1653828,2017-01-04 18:22:54 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1653828,2020-09-19 12:37:09 UTC,Still present in Groovy https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/2:2.99.917+git20200714-1
1653832,2017-01-04 00:42:16 UTC,there appears to be a sql qiery syntax issue with influxdb in /monasca-api/monasca_api/common/repositories/influxdb/metrics_repository.py:
1653832,2017-01-04 01:48:33 UTC,"now I am wondering why we are using ""time"" to get the offset? should we be using the ""offset"" influxdb key?"
1653832,2017-01-04 07:25:11 UTC,"looks like most places in the code the offset is the time offset, not the count offset in the influxdb pagination."
1653832,2017-01-04 01:29:26 UTC,"the offset value was 0 in the test case. wondering what value is expected for the offet value, absolute epoch time or a timestamp, e.g., '2013-08-12 23:32:01.232' ?"
1653849,2017-01-04 02:01:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/416398"
1653849,2017-01-30 08:16:29 UTC,"Reviewed:  https://review.openstack.org/416398
Committed: https://git.openstack.org/cgit/openstack/fuel-menu/commit/?id=581f087124e15b03b255abe9c7b0c659d815846f
Submitter: Jenkins
Branch:    master"
1653849,2017-02-27 16:22:10 UTC,This issue was fixed in the openstack/fuel-menu 11.0.0.0rc1 release candidate.
1653860,2017-01-04 14:38:40 UTC,"I generally only bootstrap from s390x to s390x, but I can confirm that this is a problem."
1653866,2019-12-10 15:23:52 UTC,No longer seems to be pertinent.
1653866,2017-10-20 17:08:05 UTC,"The DB incompatibility only appears in the L3 tests, which I've temporarily removed from the test run.  At this point the old interface no longer works with master."
1653866,2017-01-18 06:27:59 UTC,"This demonstrably works with current master, which has the committed changes that change the interface.  Further investigation is required as to the impact of the change but since it clearly doesn't break the current driver version I'm setting a low priority and removing it from our current milestone - as we work with today's upstream master code."
1653866,2017-01-14 00:32:48 UTC,"Basically, in other words - test net-vpp with master."
1653866,2017-04-20 05:30:20 UTC,"We're now getting Ocata deprecation warnings, with a flag that this will fail to work in Pike."
1653868,2017-01-04 04:48:16 UTC,P.S 1: This has something to do with setting one modifier shortcuts because if I change the shortcut as 'Alt_L' the result is same.
1653869,2017-01-07 18:30:46 UTC,"OP, can you provide more information? Which environments did you try to run wingpanel in? When running from Terminal was there any output on environments where it did not launch? What do you mean by ""poor performance""? What exactly performed poorly?"
1653869,2017-01-11 07:00:16 UTC,I retested wingpanel under GNOME3 and Cinnamon desktop environments and they run but these are the issues I encountered.
1653869,2017-03-13 04:17:23 UTC,[Expired for Wingpanel because there has been no activity for 60 days.]
1653874,2017-01-04 05:17:14 UTC,Backtrace created with lp:inkscape/0.92.x r15301 using '--g-fatal-warnings' (no debug build available).
1653874,2017-01-04 08:25:43 UTC,"Reproduced on Xubuntu 16.04, Inkscape 0.92."
1653876,2017-01-08 15:39:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653883,2017-01-04 07:41:18 UTC,"2017-01-03T22:42:17.135231Z 0 [ERROR] InnoDB: Cannot allocate 18446744073709549656 bytes of memory after 60 retries over 60 seconds. OS error: Cannot allocate memory (12). Check if you should increase t
he swap file or ulimits of your operating system. Note that on most 32-bit computers the process memory space is limited to 2 GB or 4 GB.
2017-01-03 22:42:17 0x7fde367fa700  InnoDB: Assertion failure in thread 140592373802752 in file ut0ut.cc line 936
InnoDB: Failing assertion: !m_fatal
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
22:42:17 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/"
1653883,2018-01-25 09:03:56 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3624
1653883,2017-01-04 06:07:15 UTC,Linux free-mule 3.18.36-234.el6.x86_64 #1 SMP Tue Jul 5 18:21:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
1653887,2017-02-04 21:19:26 UTC,Try removing the 'defaults' option. The options contained in 'defaults' could be incompatible with the 'bind' option.
1653887,2017-02-06 09:53:14 UTC,I got the same behavior without the default option
1653892,2017-08-17 08:02:50 UTC,"Can be reproduced on one s390x zVM server as well.
$ apport-cli --version
2.20.4"
1653893,2017-01-05 04:52:05 UTC,"0.91 create
0.92 double click SVG file to open, no use import"
1653893,2017-01-05 04:43:19 UTC,"Reproduced with 0.91 r13725, 0.92 r15299 on OS X 10.7.5"
1653893,2017-01-05 04:35:06 UTC,Attaching ZIP archive with test case which was AFAICT mistakenly attached to bug #1653896.
1653893,2017-01-04 15:38:30 UTC,"Please attach example files:
- original Inkscape SVG file created with 0.91 not yet edited with Inkscape 0.92
- new version of the original SVG file opened and resaved in Inkscape 0.92
to the bug report to allow further investigation of the reported issue (screenshots do not allow to inspect internal editor data stored in the SVG file for features like guides, grid spacing and offset)."
1653893,2017-01-04 09:01:02 UTC,screenshot in windows 10
1653893,2017-01-04 08:37:40 UTC,"Hi,"
1653900,2017-02-28 10:36:42 UTC,"Hi Gary,
thank you for your report and your help to make Ubuntu better."
1653900,2017-03-28 04:53:12 UTC,fixed 5.7.12 according to https://bugs.mysql.com/bug.php?id=79999
1653907,2017-01-04 08:42:43 UTC,"Workarounded by omitting the file, for some reason it's not getting built."
1653912,2017-10-04 16:52:50 UTC,"Buster versions are not worked out yet, so this bug can be a placeholder for when Buster is released to prod. Encountered this on a testing virtual machine."
1653912,2017-10-04 16:37:59 UTC,"Also affects Debian 10, Buster"
1653912,2017-03-01 19:55:44 UTC,Marked invalid. Thanks for the update.
1653912,2017-02-28 10:08:56 UTC,"The two fixes passed SRU, does this still occur with 1.12.6-0ubuntu1~16.10.1?"
1653912,2017-01-04 10:03:26 UTC,"Yep, I encounter this while running the Kernel SRU test."
1653912,2017-01-04 09:05:43 UTC,"This is only if you have -proposed enabled, right? There is a fix waiting
in the SRU queue for this."
1653912,2017-03-01 09:21:24 UTC,"Hello,"
1653917,2017-02-04 01:21:49 UTC,"Change abandoned by Zhao Liqiang (<email address hidden>) on branch: master
Review: https://review.openstack.org/421678"
1653917,2017-12-29 22:31:50 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/421678
Reason: Abandoning due to a few months with no activity. Feel free to restore if you wish to continue working on this."
1653917,2017-09-01 16:16:26 UTC,Unassigning due to no activity for > 6 months.
1653917,2017-02-18 13:23:52 UTC,"Change abandoned by Zhao Liqiang (<email address hidden>) on branch: master
Review: https://review.openstack.org/421678"
1653917,2017-02-13 03:16:38 UTC,"Change abandoned by Zhao Liqiang (<email address hidden>) on branch: master
Review: https://review.openstack.org/418278"
1653917,2017-01-18 06:06:52 UTC,"Change abandoned by Zhao Liqiang (<email address hidden>) on branch: master
Review: https://review.openstack.org/418278
Reason: I find another way, it may be more reasonable."
1653917,2017-01-09 08:34:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417785"
1653917,2017-01-10 09:20:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/418278"
1653917,2017-01-09 09:30:20 UTC,"Change abandoned by Zhao Liqiang (<email address hidden>) on branch: master
Review: https://review.openstack.org/417793"
1653917,2017-01-09 08:58:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417793"
1653917,2017-01-09 08:41:27 UTC,"Change abandoned by Zhao Liqiang (<email address hidden>) on branch: master
Review: https://review.openstack.org/417785"
1653917,2017-01-06 06:11:01 UTC,"Change abandoned by Zhao Liqiang (<email address hidden>) on branch: master
Review: https://review.openstack.org/416498"
1653917,2017-01-04 14:30:14 UTC,https://review.openstack.org/#/c/416498/
1653917,2017-01-18 06:03:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421678"
1653922,2017-01-11 20:05:47 UTC,Seems Like this bug is similar to https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1313389
1653923,2017-01-05 01:56:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/416799"
1653923,2018-01-23 01:29:26 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/416799
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1653927,2017-01-04 10:07:16 UTC,"Updated description to indicate that seems just a flaky test, not failing always."
1653930,2020-08-10 02:46:15 UTC,collada-dom2.4-dp-base 2.4.4.4-ubuntu1~trusty1
1653930,2017-01-06 02:16:27 UTC,Thank you for using Ubuntu and taking the time to report a bug.
1653931,2017-07-28 18:59:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653932,2017-11-04 23:07:03 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/476094
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1653932,2017-08-24 17:34:16 UTC,"After some consideration, one way to tackle the use case you have in mind is to expose a new API that returns the mapping (external network UUID <-> list of SUBNET CIDRs), which is somewhat equivalent with what nova used to have with nova-network (CLI: nova floating-ip-pool-list), whose only reference I could find is [1]. That way, you can first find out which pool is suitable for your purposes and then go and uplink the router."
1653932,2017-08-25 07:00:32 UTC,"Thanks, that would work I hope."
1653932,2017-08-25 15:16:18 UTC,"It's a matter of preserving backward compatibility, and preventing leaking of infrastructure details to tenant users. I think the new API would still be admin only, but policy customization would allow to relax that."
1653932,2017-10-05 23:32:21 UTC,"We settled with proposal made at comment #19. Adding a new API is relatively straightforward, as in this case it requires no data model changes. It touches both client and server side and it would be a great way for someone to learn the ropes. We should approve this one and allow volunteers to pick it up."
1653932,2018-03-21 22:43:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555088"
1653932,2017-08-07 07:00:26 UTC,"Theoretically with the API it is possible yes, but practically we believe that two routers on the same internal network is a problem in general. Definitely it doesn't work with our hardware."
1653932,2018-06-13 18:26:59 UTC,"Reviewed:  https://review.openstack.org/556674
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=95e72ea7177aa53326a0e6c650cddcad3b4c9526
Submitter: Zuul
Branch:    master"
1653932,2018-07-20 19:42:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/584502"
1653932,2018-10-30 06:55:05 UTC,"Reviewed:  https://review.openstack.org/555088
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4e3fb3191927e07b37fe0937102dc17334e906d1
Submitter: Zuul
Branch:    master"
1653932,2018-11-08 17:30:33 UTC,"Reviewed:  https://review.openstack.org/584502
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=e0d27124f1abb12c08d366985bd4c19d63707636
Submitter: Zuul
Branch:    master"
1653932,2018-12-10 10:11:55 UTC,"Reviewed:  https://review.openstack.org/562038
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=db2e6c90f9085368c0bda5428051c6901ac435b8
Submitter: Zuul
Branch:    master"
1653932,2018-03-26 22:35:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/556674"
1653932,2017-08-04 18:15:11 UTC,"Two routers can be connected to the same internal network (subnet), it's just a different host route. I am not sure I understand what you mean by internal traffic being natted, as I don't think it would."
1653932,2017-05-30 11:40:05 UTC,"Yes, either expose it implicitly via the parent network, which would be good imho or what also could work would be the possibility to expose it explicitly.
For the latter I don't see a use-case right now, but this would give more control."
1653932,2017-08-03 21:33:31 UTC,"@Maurice,"
1653932,2017-01-04 17:47:30 UTC,Do you mean that the external network has multiple floating IP pools (as subnets) associated to the external network?
1653932,2017-01-04 17:47:39 UTC,Assigned to Kevin Benton for initial triage.
1653932,2017-05-16 07:47:01 UTC,I'm not quite I understand the request here. Doesn't the same problem of not being able to select a specific subnet from which to allocate apply to an external network available to everyone?
1653932,2017-05-16 16:02:16 UTC,The floating IP allocation is just an example to illustrate the usecase.
1653932,2017-05-25 21:53:00 UTC,So you want to be able to expose a subnet conditional on the parent network being exposed?
1653932,2017-06-08 23:00:25 UTC,So the policy engine can do lookups of parent resources. I need to dig in and see what we need to do to enable that type of policy to be written. Then we can have a separate discussion of if we should expose subnets by default.
1653932,2017-08-04 08:00:23 UTC,"No, because we would need two routers and two internal networks. And then internal traffic would need to be natted, not an option."
1653932,2017-06-22 22:33:14 UTC,"ok, so I am going to adjust the patch to make the change to the policy engine to allow this rule, but it won't be the default for now so you will need to edit /etc/neutron/policy.json in your deployment."
1653932,2017-08-03 14:39:43 UTC,"We extend our networks by adding additional subnets. Once one range is full we can add another, where needed - and it must be possible to choose the new one/that one that has IPs available."
1653932,2017-08-02 16:59:41 UTC,"Maurice, thanks for the extra feedback. I think what's still not clear is the workflow that the involves the selection of a subnet within an external network based on a specific CIDR. Multiple external networks and network tagging can potentially address the same need without the tight coupling of subnet selection and IP range, which doesn't seem very portable."
1653932,2017-06-21 11:24:58 UTC,POC here we can discuss next meeting: https://review.openstack.org/476094
1653932,2017-07-20 23:01:57 UTC,"We talked about this request during the latest drivers meeting. It turns out now that some prototyping has been made and more thought has been given, this request may turn out to be more hairy than it initially appeared."
1653932,2017-08-03 17:05:09 UTC,"I can see why one would want to choose one subnet over another because of different policies (routing or security related ones), but a tenant shouldn't be concerned about IP exhaustion because neutron will select an IP automatically from a range with available IPs, and I can't see this last one being a valid use case."
1653932,2017-08-02 09:51:18 UTC,"Currently I use the RBAC Feature 'access_as_shared' on external networks, so I can list the subnet via the policy ""field:networks:shared=True""."
1653936,2019-03-20 09:13:34 UTC,udev use builtin blkid so this is bug in systemd:
1653953,2019-09-27 09:02:26 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1653953,2019-08-19 15:41:10 UTC,This issue was fixed in the openstack/nova 17.0.12 release.
1653953,2019-06-27 18:43:32 UTC,"Reviewed:  https://review.opendev.org/457886
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d89e7d7857e0ab56c3b088338272c24d0618c07f
Submitter: Zuul
Branch:    master"
1653953,2019-08-12 20:41:49 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1653953,2019-08-09 15:44:18 UTC,"Reviewed:  https://review.opendev.org/668123
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2f91755ab74372a966b0ebae710beccabef0821
Submitter: Zuul
Branch:    stable/queens"
1653953,2019-06-29 01:30:50 UTC,"Reviewed:  https://review.opendev.org/668119
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e93bc57a73d8642012f759a4ffbe5289112ba490
Submitter: Zuul
Branch:    stable/rocky"
1653953,2019-06-28 23:22:32 UTC,"Reviewed:  https://review.opendev.org/668118
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e802ede4b30b21c7590620abc142300a57bcf349
Submitter: Zuul
Branch:    stable/stein"
1653953,2019-06-28 09:22:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/668123"
1653953,2019-06-28 09:08:25 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/668119"
1653953,2019-06-28 09:08:02 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/668118"
1653953,2017-07-28 07:33:04 UTC,"There was no tempest workaround here.
Nova fix has been this : https://review.openstack.org/#/c/457886/"
1653953,2019-08-12 21:11:42 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1653953,2017-04-19 06:41:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457886"
1653953,2017-01-05 01:53:18 UTC,"My first thought on this is that the cloned image is flattened as part of direct_snapshot, so I'm interested in finding out why that's not sufficient for the image-delete to work."
1653953,2017-01-05 11:56:56 UTC,Just to be complete this still reproduces for me without any issues on F24 and 1bcf3b55 :
1653953,2017-01-05 17:58:03 UTC,"Thanks for all that info. I'm using ubuntu trusty, so maybe there are some issues there. Will try again with fedora."
1653953,2017-01-05 21:02:55 UTC,"I first tried with CentOS7 and that didn't work with stack.sh failing during install of the ceph-* packages. Tried a third time with Fedora 24 and was able to get shelve/unshelve to work. But, I wasn't able to reproduce the bug. The shelved image gets removed from glance and the backend when I unshelve."
1653953,2017-01-05 09:40:02 UTC,"> My first thought on this is that the cloned image is flattened as part
> of direct_snapshot, so I'm interested in finding out why that's not
> sufficient for the image-delete to work.
"
1653953,2017-01-05 22:00:55 UTC,"Argh, sorry, that was my bad. Tried again with the RAW image and I see the same problem now, with this trace in n-cpu.log:"
1653953,2017-01-06 09:50:34 UTC,"I wouldn't say that we leak images here, we still have references to the snapshot in Glance and can remove these later once the instance disk is flattened. We also end up in this situation when initially booting an instance from a rbd image, thus my reluctance to call this a genuine bug :"
1653953,2017-04-13 09:55:45 UTC,I have tried to reproduce this issue today but could not able to reproduce
1653953,2017-04-19 05:19:49 UTC,Yes.. it is reproduce able with Ceph RBD only.
1653953,2017-01-05 21:21:11 UTC,"Yeah apologies, I didn't explicitly call it out in the description but this requires RAW images to be used otherwise we fallback to libvirt_utils.fetch_image."
1653953,2017-07-27 11:36:07 UTC,"Changed in nova:
status:	In Progress → Fix Committed"
1653966,2017-01-04 13:50:57 UTC,Got this error on a re-run
1653966,2017-01-04 13:52:14 UTC,More log lines (couple of them were missing from above trace):
1653967,2017-01-23 21:47:41 UTC,"Guys,"
1653967,2017-07-17 12:04:07 UTC,This issue was fixed in the openstack/requirements 1.1.0 release.
1653967,2017-05-31 15:47:34 UTC,Not seeing the issue from a requirements perspective so removing us.
1653967,2017-02-02 20:58:37 UTC,This should be fixed in xenial and yakkety now:
1653967,2017-01-25 14:18:19 UTC,"We released oslo.config  3.17.1 for branch stable/newton, that makes sure rfc3986>=0.2.2 to avoid ConfigFileValueError."
1653967,2017-01-10 11:56:51 UTC,Release Fix in https://review.openstack.org/418345
1653967,2017-01-05 20:42:55 UTC,I found one more source of this bug (It was pointed by Marsikus at habrahabr.ru): https://github.com/openstack/oslo.config/compare/3.18.0...master
1653967,2017-01-05 08:24:45 UTC,"A fix is already on its way, but the new python-rfc3986 package is only available in the {xenial,yakkety}-proposed repositories."
1653967,2017-01-05 00:16:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1653967,2017-01-04 13:37:47 UTC,I found source of the bug: python-rfc3986 is to blame (it is used by oslo-config). Version  0.2.0-2 contains bug which violates RFC3986. It was fixed in 0.2.2. Version of python-rfc3986 from zesty (0.3.1-2) fix this problem.
1653967,2017-01-10 11:48:01 UTC,"rfc3986>=0.2.2 in stable/newton and 3.18
https://github.com/openstack/oslo.config/blob/stable/newton/requirements.txt
https://github.com/openstack/oslo.config/blob/3.18.0/requirements.txt"
1653979,2017-01-04 15:09:22 UTC,"<greyback> Saviq: kenvandine: the mir work to enable orientation as a surface property is done, it has been a todo to enable that with unity8 for some time"
1653987,2019-09-25 19:35:08 UTC,conntrack-tools are installed in neutron-base image for a long time: https://github.com/openstack/kolla/commit/9688f95f58014f06fe0101eb319ed671425bb4c4
1653987,2019-09-27 09:02:38 UTC,"Reviewed:  https://review.opendev.org/684730
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d3b41a181a8f0bddb178c5cd831cfb56a81b1ccf
Submitter: Zuul
Branch:    master"
1653987,2019-11-11 15:39:21 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1653988,2017-01-04 18:14:35 UTC,this is obviously a devicetree setting we have not enabled by default in the pi2/pi3 gadgets:
1653988,2017-01-05 14:01:01 UTC,the fix is now in the gadget snaps in the edge channel.
1653993,2017-01-04 16:10:42 UTC,"Possibly related to
* Bug #1605334 “FeImage add position X and Y”
  https://bugs.launchpad.net/inkscape/+bug/1605334"
1653995,2017-09-08 22:53:48 UTC,There is no activity for fixing this bug for a while. I am going to remove assignee so that other contributors can take it.
1654007,2017-01-04 16:08:19 UTC,"It's happened against environments where Tempest jobs run, e.g. http://172.18.173.8:8080/jenkins/view/Tempest_9.%D0%A5/job/Tempest_9.x_Ceph_no_ssl/288/consoleFull"
1654007,2019-01-28 04:43:29 UTC,hey did you try pip install rally-openstack and after that your installation.
1654009,2017-12-16 13:52:14 UTC,"This is fixed in 0.5.0-3, which appears to already part of Bionic."
1654020,2017-01-11 05:24:02 UTC,"I removed info about lining figures instead of default oldtyle figures from description. To do this, you can fill a separate bugreport. Also I pushed MR."
1654020,2017-01-04 21:24:04 UTC,"I should be agreed that Raleway needs to be updated for better i18n, but why elementary OS should use lining figures?"
1654020,2017-01-05 02:15:14 UTC,"Lining figures should be used for short display texts, which is the context that Raleway is used in the system."
1654025,2017-01-04 17:13:46 UTC,Not sure I'm going to get to the bottom of this today.
1654025,2017-09-19 02:21:21 UTC,This bug was fixed in the package autopkgtest - 5.0
1654025,2017-01-22 19:56:43 UTC,Thanks pitti!
1654025,2017-01-22 11:04:01 UTC,https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=11d05a9ce
1654025,2017-01-21 17:41:55 UTC,"Hmm, yeah, for me it failed 4 times out of 100 runs. That's better than the previous state which failed every time I tried."
1654025,2017-01-21 09:56:19 UTC,"Hello Iain,"
1654025,2017-01-17 09:45:02 UTC,Still waiting for review (comment #9) if you have time
1654025,2017-01-05 17:28:25 UTC,"I cowboyed this in to test it live, and requeued the tests."
1654025,2017-01-22 11:03:48 UTC,"string vs. float comparison makes sense indeed. It could also be that by testpkg-reboot/'s nature, rebooting is pretty much the first thing it does, so it could happen that the uptime before reboot is even smaller than the first time we check after reboot -- but that's a bit academic in practice."
1654025,2017-01-05 12:00:24 UTC,"Inserted a time.sleep(30) in autopkgtest-virt-lxd/hook_wait_reboot, and now the test runs. So now I just have to find out why we don't wait for reboot properly."
1654025,2017-01-05 11:20:47 UTC,Haven't yet been dissuaded from that line of thinking:
1654025,2017-01-05 09:05:38 UTC,It's autopkgtest itself rebooting after installing a new kernel. I was just theorising that maybe this isn't properly waiting for the reboot to finish.
1654025,2017-01-04 23:00:37 UTC,"On Jan 04, 2017, at 10:28 PM, Iain Lane wrote:"
1654025,2017-01-04 22:28:33 UTC,"'lxc exec'ing the same command seems to always work, as does running bash and then poking things. I didn't yet try to do every single thing that autopkgtest does manually."
1654025,2017-01-04 17:44:48 UTC,"s/trusty/zesty/ works, FWIW"
1654025,2017-01-04 17:36:42 UTC,"Inserted an strace into the apt-get source, not sure what's going on"
1654025,2017-01-05 13:34:52 UTC,"I fixed (""fixed""?) this by removing the use of 'lxc exec ... -- sleep 3600' as a synchronisation method in favour of checking /proc/uptime directly - when that goes backwards, we've rebooted."
1654026,2017-01-12 15:17:45 UTC,Hi Daniel. If I understand correctly you want a dropdown to filter by location as well as rooms? So that if you select a location only the rooms in that location will be available from the room-dropdown?
1654030,2017-01-04 17:33:44 UTC,in OPNFV there is currently workaround to deploy MAAS manually
1654030,2017-06-14 19:21:03 UTC,: The repository 'http://ppa.launchpad.net/maas-deployers/stable/ubuntu xenial Release' does not have a Release file.
1654031,2017-02-28 10:19:01 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1654047,2017-03-18 09:18:56 UTC,"This is looks like a documentation bug:
options --run-time 3600 --sleep-collect 60
are used to determine interval for sampling vmstat-like tools:
/usr/bin/vmstat 60 60
/usr/bin/vmstat 3600 2
/usr/local/mysql/bin/mysqladmin --user=root --password=x xxxx ext -i60 -c60"
1654047,2018-01-24 22:28:48 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1405
1654056,2017-01-04 23:34:46 UTC,"Ubuntu just imports the package from Debian, I guess we have to remove it there."
1654057,2017-01-04 19:40:12 UTC,Here is the snippet from kern.log
1654057,2017-01-05 20:19:58 UTC,"Btrfs ran into this issue a couple of times on this partition, always falling back to read-only."
1654061,2017-01-06 01:38:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/417260"
1654061,2017-02-14 08:28:21 UTC,"Reviewed:  https://review.openstack.org/417260
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=1f93f80037f166a5a7f1a2e79ae738680a5f56ed
Submitter: Jenkins
Branch:    master"
1654061,2018-02-26 12:32:01 UTC,it's already classified for triage.
1654062,2017-01-04 21:20:23 UTC,"Does this only happen after suspend? I've seen similar issues in Chrome and Electron apps on my second display, but only after suspending."
1654062,2017-01-04 21:43:34 UTC,"This happens all of the time. Whether on the first boot, restart, suspend. Making the second monitor pretty much unusable. Totally fine on a separate PC with Windows."
1654064,2017-01-18 12:31:48 UTC,"Hello , I have tested the mainline kernel 4.10-rc3 and the bug has been fixed."
1654064,2017-01-05 19:28:44 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1654064,2017-01-04 20:31:08 UTC,This change was made by a bot.
1654064,2017-01-07 16:52:02 UTC,"Hello Joseph Salisbury, I cannot test another kernel because I'm currently using a module that solves a bluetooth bug which works only with my current kernel, as you can see from here:"
1654065,2017-01-09 16:11:50 UTC,0 vs 0.1 shouldn't make much difference
1654072,2017-01-04 23:33:08 UTC,Solved!!!
1654072,2017-02-21 19:38:38 UTC,"i have the same problem whit a g-340 ""Tablet WP4030U""
this not work for me
this directory ""/dev/input/by-id/"" don't have nothing about a tablet...
im using arch whit gnome driver nvidia-noveau"
1654084,2020-03-18 08:24:28 UTC,"Change abandoned by Tin Lam (<email address hidden>) on branch: master
Review: https://review.opendev.org/417315"
1654084,2018-10-26 10:13:23 UTC,"But but Morgan (said in a whiney voice) how would anyone know that they sent a bad query param, one that might have been a typo for a good one?"
1654084,2018-10-25 23:40:36 UTC,I want to point out I disagree with the guidance from the API-SIG. I rather have a server ignore (drop) query params than raise a 400.
1654084,2018-04-09 20:35:01 UTC,Automatically unassigning due to inactivity.
1654084,2017-01-13 05:34:47 UTC,Marking this as wishlist since we can't break API compatibility. The only way we could do this is by implementing microversions.
1654084,2017-01-10 18:45:56 UTC,"In response to Morgan: As I said in response to a similar issue in glance, I think the rules in that 'evaluating' guideline are potentially too strict, especially with regard to changes just like this: making people's lives better."
1654084,2017-02-02 16:59:38 UTC,"Reviewed:  https://review.openstack.org/417441
Committed: https://git.openstack.org/cgit/openstack/api-wg/commit/?id=b3e3b5f15344d130555f8f49f01336f7781d6ccb
Submitter: Jenkins
Branch:    master"
1654084,2017-01-06 16:36:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417441"
1654084,2017-01-06 08:41:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417315"
1654084,2017-01-05 15:24:08 UTC,"Thanks Chris, Ed said the same thing on IRC:"
1654084,2017-01-05 09:58:19 UTC,"We haven't formalized this yet for query strings (that I can find), but have discussed it and agree that 400 is the right response here as it is the only way of letting the client side know that something was less than correct about the query."
1654084,2017-01-05 04:13:05 UTC,"According to the HTTP spec the query args are part of the URL, these are invalid and should result in a 4xx error. However, even the great google doesn't adhere to that, try the following:"
1654084,2017-01-04 22:13:14 UTC,"I'm not sure if there is a standard for validating query strings, but I figured I'd triage this since it has an impact on user-experience for sure."
1654084,2017-01-10 18:33:20 UTC,"As said in the meeting, this is an API behavior break that is not security related. We cannot have this bug fixed without microversions or API version rev."
1654087,2017-02-05 00:16:23 UTC,"I've found a workaround, which is basically to use the same process I used for 14.04. To wit:"
1654089,2017-01-05 01:07:59 UTC,This is a good idea; it will help with people trying to spy with a modified client.
1654089,2017-01-05 01:11:03 UTC,"Also, you should do something to prevent the possibility of people filling up a server with empty clients [under different or same IPs as other clients]."
1654090,2017-09-21 10:15:43 UTC,"Thnaks mantas , I will test this next week."
1654090,2017-09-21 09:48:21 UTC,"I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive"
1654090,2017-03-01 13:53:50 UTC,"usb_modeswitch is only responsible for switching a device or (as in this case) select the config containing the cdc_mbim composition.
That's all usb_modeswitch does, what else needs to be done for bringing up the connection is done by other programs."
1654090,2017-03-01 14:03:14 UTC,"Thanks, Yes the last part of my report is a note , not the bug content"
1654090,2017-06-20 09:46:53 UTC,"Hi I don't see any update of modeswitch data in 16.04.2 to support this modem Huawei ME936 M.2 , does the LTS backports allow update of such package ? Or for 16.04.3 maybe ?"
1654094,2017-06-24 22:52:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654102,2017-01-31 10:06:19 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/427080"
1654102,2017-02-27 20:29:08 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1654102,2017-02-11 02:17:28 UTC,"Reviewed:  https://review.openstack.org/427080
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e30b75097840019c38e0619e70924ddc9f9487a0
Submitter: Jenkins
Branch:    stable/newton"
1654102,2017-01-07 00:47:29 UTC,"Reviewed:  https://review.openstack.org/416822
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2f1245a56c238646a056a20caa543f2a254b83d7
Submitter: Jenkins
Branch:    master"
1654102,2017-01-27 00:51:42 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1654102,2017-01-05 03:14:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/416822"
1654102,2017-01-05 00:17:51 UTC,"Actually when looking at logstash, the failures are mostly in the non-Ironic jobs which are using keystone v3, and those are failing because we create the compute_nodes record in the database from the resource tracker in the nova-compute service, but we fail to update the compute node record which sets the free_disk_gb value:"
1654102,2017-01-05 00:37:34 UTC,I've created bug 1654107 to handle the Unauthorized exception separately from the Ironic host manager update race.
1654102,2017-01-05 00:34:13 UTC,"I see that we check for Unauthorized responses in the nova-status upgrade check command, but not in safe_connect in the scheduler report client, so we need to handle that."
1654102,2017-01-05 00:31:15 UTC,This is the auth failure on the keystone side:
1654102,2017-01-05 09:24:20 UTC,"This issue is seen in Ironic HPE CI jobs
https://15.184.0.52/28/372428/18/check/gate-tempest-ironic-ilo-driver-iscsi_ilo/3d53e55/"
1654104,2017-01-05 17:13:39 UTC,Further info - correction
1654107,2017-01-27 00:51:51 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1654107,2017-01-13 22:16:52 UTC,"Reviewed:  https://review.openstack.org/419216
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9fb203f17e358760e9e40ef55ee79965343581f8
Submitter: Jenkins
Branch:    stable/newton"
1654107,2017-02-27 20:29:28 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1654107,2017-01-05 22:28:10 UTC,"Reviewed:  https://review.openstack.org/416810
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=180e6340a595ec047c59365465f36fed7a669ec3
Submitter: Jenkins
Branch:    master"
1654107,2017-01-05 02:13:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/416810"
1654107,2017-01-05 00:38:45 UTC,I've marked this high severity because what happens when we create the compute node record but fail to set free_disk_gb is the scheduler fails to update the HostState object and then we can't schedule anything.
1654107,2017-01-12 00:32:19 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/419216"
1654116,2017-03-16 14:47:48 UTC,Worker multiplier set to 1.0 relieves memory pressure and may have resolved this issue.
1654116,2017-02-07 07:42:03 UTC,I'm thinking also that a controller log (at debug or even trace level) may be useful to see how the controller is handling leadership changes. Just the part of the log around the time of the issue and what leads up to it.
1654116,2017-02-28 14:34:24 UTC,"So, this is a problem with charm-helpers or the charms themselves? I'm kinda thinking that 'under load' is the exact condition that you want features like leadership to work. I'll ask @thedac to review the updates to this bug since his last comment and see if there are any next steps from the charms/charm-helpers end."
1654116,2017-02-27 23:13:43 UTC,"Marking this as Invalid for Juju.
The problem occurs under heavy load and as per comment # 17, there is nothing Juju can do about it. It behaves as expected."
1654116,2017-02-27 16:59:44 UTC,"I was finally able to reproduce this issue with logging set to TRACE. The full logs of the deployment (basically /var/log/* from every unit and the bootstrap node) are available from https://private-fileshare.canonical.com/~fginther/juju/lp-1654116/unit-not-leader-with-trace-logs.tar.gz (it's nearly 50GB and only available within canonical, sorry). The logs for the bootstrap unit are under ""landscape-0-inner-logs/bootstrap/var/log""."
1654116,2017-02-17 04:30:48 UTC,"You are going to want some better instrumentation. The leader-elected hook is not run when the unit becomes leader. It is run some time after the unit has become leader, and as far as I know there is no guarantee that it is still the leader when it happens. I'd stick an 'assert is_leader()' in the leader_set wrapper, possibly by monkey patching charmhelpers.core.hookenv.leader_set()"
1654116,2017-02-09 14:34:02 UTC,"I'll note that 'peer_store' isn't safe to directly call, but looking at the traceback of the original description it is line ~217 of hooks/amqp-relation-changed which looks to be:
    # If this node is the elected leader then share our secret with other nodes
    if is_elected_leader('grp_ceilometer_vips'):
        peer_store('shared_secret', get_shared_secret())"
1654116,2017-02-09 14:19:55 UTC,"Sorry, I'm on crack, I missed line 70/71 which is exactly the 'check if I'm leader first':
    if not is_leader():
        return _leader_get(attribute=attribute)"
1654116,2017-02-09 14:16:32 UTC,"I haven't dug particularly deeply. However if I do
 charm pull ceilometer
I get: cs:ceilometer-24
And then dig into the contents of:
 charmhelpers/contrib/peerstorage/__init__.py"
1654116,2017-02-08 12:53:53 UTC,"One possible root cause may be that if the machine running the unit is loaded, the time between checking for leadership and the lease expiring may have passed before the hook gets to write the leadership settings. It's very unusual that the unit leader changes so often as seen in the logs. This fact points to a possible load issue because the leader should only change if the current leader did not to get update its lease before it expired; if it doesn't that is likely due to load."
1654116,2017-02-07 07:12:15 UTC,"Looking at the rabbitmq logs, it appears to me (I could be misinterpreting):"
1654116,2017-02-28 15:52:57 UTC,"Re: comment #21 and gating; if this is fully async, then gating is only going to tighten the race, but not eliminate it. i.e. code like:"
1654116,2017-01-26 15:46:42 UTC,Switch juju-core task to juju.
1654116,2017-01-30 05:08:06 UTC,"The actual promise from Juju is that from the time you call 'is-leader' and get a True value, that you will have 30s before we would possibly return True to any other unit."
1654116,2017-01-05 22:25:56 UTC,This would appear to be a change in Juju behavior for leader-set in juju 2.1b3.
1654116,2017-01-05 22:49:35 UTC,Juju 1.25.9 seems to behave the same. I can't find a .8 env to test against.
1654116,2017-01-05 22:57:35 UTC,Added ceilometer to the bug as I found it there too:
1654116,2017-01-05 22:58:19 UTC,Full log from previous comment.
1654116,2017-01-05 11:21:21 UTC,Please add a log analyser issue for this.
1654116,2017-01-12 00:16:26 UTC,Has there been any change from juju 2.1beta3 to 2.1beta4?
1654116,2017-01-12 01:48:51 UTC,"@thedac,"
1654116,2017-01-12 14:54:34 UTC,"@thedac,"
1654116,2017-01-17 18:24:55 UTC,This is a juju is-leader bug.
1654116,2017-01-17 20:37:08 UTC,"@thedac, I wonder if bug #1657245 might be related. It also happened with the rabbit charm and looks like it's a split brain issue (/0 and /1 formed a cluster, /2 is the juju leader and went to lala land)."
1654116,2017-01-10 00:20:08 UTC,My original theory is wrong on both fronts.
1654117,2017-01-18 08:23:40 UTC,"Reviewed:  https://review.openstack.org/417726
Committed: https://git.openstack.org/cgit/openstack/vmware-nsx/commit/?id=ade538424d3514697c8f920dad080959c697aaec
Submitter: Jenkins
Branch:    master"
1654117,2017-01-17 03:38:59 UTC,"Change abandoned by rajiv (<email address hidden>) on branch: master
Review: https://review.openstack.org/417735
Reason: Abandoned, not applicable as hacking version is lower than 0.10"
1654117,2017-01-11 04:24:42 UTC,"Change abandoned by rajiv (<email address hidden>) on branch: master
Review: https://review.openstack.org/417733
Reason: abandoned because it is duplicate."
1654117,2017-01-09 14:58:49 UTC,"Reviewed:  https://review.openstack.org/416807
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=57fc62659c09a99a0c79c2fa6e334155be9b1284
Submitter: Jenkins
Branch:    master"
1654117,2017-01-09 03:28:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417735"
1654117,2017-01-09 03:25:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417733"
1654117,2017-01-08 06:38:51 UTC,"Change abandoned by Tin Lam (<email address hidden>) on branch: master
Review: https://review.openstack.org/417652
Reason: Abandon - since it is a duplicate."
1654117,2017-01-10 08:33:20 UTC,"Reviewed:  https://review.openstack.org/416812
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=99ac3b09a8e5d29b128f452c0a46393d5aeabf83
Submitter: Jenkins
Branch:    master"
1654119,2017-01-12 15:45:25 UTC,"Change abandoned by Thomas Bachman (<email address hidden>) on branch: master
Review: https://review.openstack.org/417027
Reason: This is the wrong approach -- will document process to use for Edge NAT instead."
1654122,2017-02-22 16:45:39 UTC,Sure
1654122,2017-02-22 16:19:00 UTC,"All three reports seem to be about the same issue, and I'd prefer keeping everything grouped in one unique report. Would you mind if I mark two of them duplicates of the most relevant one?"
1654122,2017-01-08 12:13:35 UTC,Reproduced here with 0.92 win 8.1 64bit.
1654122,2017-02-22 12:49:37 UTC,Thanks for taking the time to file a report!
1654122,2017-02-22 15:13:53 UTC,I am the author of Bug #1545573. I also made another one for version 0.92.1 which coincides with this:
1654128,2017-01-10 15:42:48 UTC,Just to confirm; this bug is for the backport of fix in [1] to the mitaka/liberty branches since that wasn't done as part of the patch in [1]? Is this correct?
1654128,2017-01-11 02:05:46 UTC,"Hi, Boden,
yes, this bug was reported for mitaka/liberty release.
Upstream master fix was done here: https://review.openstack.org/#/c/400233
Current newton backport is still blocked: https://review.openstack.org/#/c/400192
And no backport patches for mitaka or liberty."
1654128,2017-01-11 02:07:53 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/418644"
1654128,2017-01-13 06:51:43 UTC,"Reviewed:  https://review.openstack.org/418644
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dd6fd625391d310040118ae5c3575ff6cff6e833
Submitter: Jenkins
Branch:    stable/mitaka"
1654139,2017-01-18 06:30:18 UTC,My current test shows that the DHCP port for the private network that devstack creates is not consistently forwarded to etcd which is a problem when using a devstack test setup.
1654141,2017-01-27 07:45:22 UTC,I'm having this issue as well but only when using my All-In-One built in speakers. If I plug in the external speakers the popping sound is gone.
1654152,2017-03-21 08:24:56 UTC,"Change abandoned by Kevin Benton (<email address hidden>) on branch: master
Review: https://review.openstack.org/416595
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns."
1654152,2017-01-10 21:44:59 UTC,I'm in favor to have a cleanup here.  Specially because having a configuration structure helps during the implementation of WSGI files[1].
1654173,2017-01-05 10:01:43 UTC,"Review in progress for https://review.opencontrail.org/27664
Submitter: Vinay Vithal Mahuli (<email address hidden>)"
1654173,2017-01-05 10:42:21 UTC,"Reviewed:  https://review.opencontrail.org/27664
Committed: http://github.org/Juniper/contrail-packaging/commit/892c1d4173c8e14ac8e7a26cd18901b1d0c28791
Submitter: Zuul (<email address hidden>)
Branch:    R3.1.1.x"
1654173,2017-01-06 04:35:41 UTC,"Review in progress for https://review.opencontrail.org/27689
Submitter: Vinay Vithal Mahuli (<email address hidden>)"
1654175,2017-01-06 09:44:37 UTC,"Thanks again,
well, I didn't know that there is a difference (and what it is) between ""inkscape"", ""inkscape.exe"" and ""inkscape.com"". (Probably, that's Windows basics of which I was not aware of)."
1654175,2017-01-05 19:32:17 UTC,"hello again,
    from the syntax you are using in your commands, I gather that you have probably put the Inkscape directory into the PATH variable on your computer, otherwise you would have had to write out the exact directory location explicitly in your commands. I normally do not do that. I prefer to leave Inkscape absent from the PATH and write in the exact location explicitly. However even if I temporarily put Inkscape into the path, I am still not able to duplicate the problem you are having. So I am confused.
    as an experiment you could try changing directory so that you are exactly in the Inkscape directory and then try running the commands. In this case the PATH variable will not be used, or will not be needed.
     somewhat off-topic, there is a difference between the command 'inkscape.exe' and 'inkscape' in all cases. The command inkscape.exe runs the file inkscape.exe directly and it runs it outside of DOS. Meaning that you will regain the DOS cursor immediately even while Inkscape is running. And also that you will not see any of the error messages that Inkscape produces.
    The command 'inkscape' actually runs the file inkscape.com which then calls inkscape.exe. In this case you will _not_ get a DOS cursor until Inkscape exits, and you _will_ get the error messages that Inkscape produces. I have forgotten the technical term for it, but it is similar to the difference between a modal versus non-modal dialog. Normally running 'inkscape' is ""better"" because you get more info. However this is probably why the .ps input is being affected, even though I have not been able to reproduce the problem. What I would try however is to run Inkscape from within its own directory as a trial. That way you do not need a PATH assignment."
1654175,2017-01-05 11:33:28 UTC,thank you for taking the time to issue a report.
1654175,2017-01-05 09:27:00 UTC,The described behaviour is actually observed with Inkscape 0.91 under Win7/64
1654175,2017-01-05 19:02:22 UTC,"Thanks, Alvin, for looking into this and the hint with the brand new version 0.92
I tried this with Version 0.92 r15299 64bit exe build"
1654177,2017-01-05 08:34:11 UTC,Also affects test_create_delete_stateless_subnet_with_ports
1654177,2017-08-23 15:29:56 UTC,"R4.0 + OSPD10, build CB-25 rhel7+newton"
1654192,2017-01-12 01:56:06 UTC,"Marking as incomplete instead, just so this bug shows up in the list of Unity8 resizing bugs:"
1654192,2017-01-11 11:13:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654192,2017-01-11 08:29:06 UTC,"checking unity8's code again, I am very confident this happens in lower layers, likely miral."
1654192,2017-01-10 16:05:46 UTC,"from the screenshots and description it doesn't seem to be exactly the same, however, it might very well be related as both happen on resizing. The other doesn't update the app to the new size, this one makes unity8 resize the window back to what the app thinks it is."
1654192,2017-01-10 15:41:06 UTC,I bet this is related/identical to lp:1649662
1654192,2017-01-11 02:06:06 UTC,"While seemingly different bugs, both could be caused by Unity8 failing to send resize events to clients. And one or two other Unity8 resizing bugs I've misplaced right now..."
1654200,2017-01-12 18:44:30 UTC,"Fix proposed to branch: master
Change author: Vladimir Kozhukalov <email address hidden>
Review: https://review.fuel-infra.org/29807"
1654200,2019-02-28 10:36:23 UTC,"Change abandoned by Vladimir Khlyunev <email address hidden> on branch: master
Review: https://review.fuel-infra.org/29807"
1654200,2017-02-21 01:30:46 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/419120
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1654200,2017-02-21 01:30:42 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/419626
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1654200,2017-01-12 19:41:37 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/419626"
1654200,2017-01-12 12:03:24 UTC,"Since this case (installing Fuel master node on vanilla Centos without Fuel ISO) was not originally in the scope of 9.x and does not affect 9.0 -> 9.x update procedure, I am moving bug priority to medium."
1654200,2017-01-11 20:19:00 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/419120"
1654200,2017-01-10 16:13:50 UTC,"Reviewed:  https://review.openstack.org/417829
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=4b13982ba458c38ec5245d0ca8a14de55782189b
Submitter: Jenkins
Branch:    stable/mitaka"
1654200,2017-01-09 11:24:48 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/417829"
1654200,2017-01-09 08:02:34 UTC,"FYI, ami-creator package should be in the local repo on the master node because it is in the list of rpm requirements https://github.com/openstack/fuel-main/blob/stable/mitaka/requirements-rpm.txt#L1"
1654200,2017-01-06 13:44:11 UTC,It seems that the test itself configures the environment in a way that the master node does not have access to the repostories. Here is the package that is required
1654200,2017-01-12 12:01:12 UTC,"This bug is not about Ceph, but it is more about deployment of the Fuel master node on vanilla Centos. To make it working we need to modify CI scripts that run the test so they inject necessary repositories before starting deployment."
1654203,2017-01-13 08:04:39 UTC,"Reviewed:  https://review.openstack.org/419427
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=e459589579fb247116943906f68b73db654a1d76
Submitter: Jenkins
Branch:    stable/newton"
1654203,2017-04-18 08:11:19 UTC,There is no update to 10.x feature - marking as fix released
1654203,2017-02-27 16:29:39 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1654203,2017-01-30 13:19:40 UTC,https://custom-ci.infra.mirantis.net/view/9.x/job/9.x.custom.ubuntu.system_test/1065/console
1654203,2017-01-23 18:11:38 UTC,"The logs provided contain info that the test ran against 9.0 repositories. Thus, I am closing this bug back"
1654203,2017-01-23 15:58:34 UTC,reproduced by https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.add_updated_node_to_environment/96/testReport/(root)/add_updated_controller_to_environment/
1654203,2017-01-18 09:29:20 UTC,"There is no ""Unrecognized attribute"" error during few last runs on 9.x"
1654203,2017-01-12 18:26:14 UTC,"Reviewed:  https://review.openstack.org/419421
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=9b0777331852c9e531b848ec58f4be9b0a5b2007
Submitter: Jenkins
Branch:    master"
1654203,2017-01-12 21:17:08 UTC,"Reviewed:  https://review.openstack.org/419426
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=a444570299c5313325943f62e7c6f852f187ecab
Submitter: Jenkins
Branch:    stable/mitaka"
1654203,2017-01-12 11:32:51 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/419426"
1654203,2017-01-12 11:24:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419421"
1654203,2017-01-12 08:04:43 UTC,"Neutron team, QAes don't change neutron configuration, how we can be related to patch info fuel-library repo?"
1654203,2017-01-11 13:47:22 UTC,"The only reason I can think of how we ended up with the wrong neutron server configuration is a stale snapshot (before https://review.openstack.org/#/c/390847/ was merged) that was used for the nodes.
Otherwise there should have been proper extension_drivers setting with ""dns"" value in list."
1654203,2017-01-11 12:15:19 UTC,"There is a problem with neutron server configuration - the driver extension lists are different.
node-4 (the updated one I presume) has dns,port_security enabled while the rest have either port_security (nodes 1-3) or port_security,qos (node 5) enabled. http://paste.openstack.org/show/594542/"
1654203,2017-01-09 15:32:47 UTC,"@Vladimir, how failure of creation vm can be handled by QA team? We just use clients for operations with OS. Reassigned to mos-maintenance."
1654203,2017-01-06 13:04:02 UTC,I suppose (due to Exception type) that this is either OpenStack bug or some discrepancy in tests or the fact that there could be some API incompatibility due to package version differences. I suggest we assign it to MOS-Neutron team for investigation.
1654203,2017-01-12 11:33:01 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/419427"
1654207,2017-01-05 10:41:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/416928"
1654207,2017-02-01 16:10:44 UTC,"Hi all.
Any chance to review proposed solution?"
1654207,2020-03-26 09:09:37 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/416928
Reason: The patch is stale. Feel free to restore it (or ping gibi on IRC to do so) if you are still working on this."
1654207,2020-03-26 09:48:16 UTC,Behavior is still visible in current master. -> Confirmed
1654214,2017-01-11 10:17:43 UTC,I have the same symptoms with 4.10.0-041000rc3-generic .
1654214,2017-01-16 10:26:53 UTC,"Post on linux-kernel mailing list:
http://lists-archives.com/linux-kernel/28739894-problem-belkin-thunderbolt-2-express-dock-hd-display-port-hot-plug-not-supported.html"
1654214,2017-01-11 21:41:09 UTC,"dunk, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Andreas Noever CC linux-kernel )?"
1654214,2017-01-05 11:30:14 UTC,This change was made by a bot.
1654214,2017-01-09 08:37:41 UTC,"""status:Incomplete"" carries the description
""Cannot be verified, the reporter needs to give more info."""
1654214,2017-01-05 17:11:44 UTC,"Christopher M. Penalver (penalvch) asked me to assign this to him in
bug/1551712
however i do not have the required permissions to assign bugs."
1654214,2017-01-09 19:39:39 UTC,"dunk, thank you for reporting this and helping make Ubuntu better."
1654215,2017-01-05 20:25:47 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1654223,2017-01-06 11:45:00 UTC,"Maybe GDB stops mixxx because a runtime instruction set test or something.
What happens if you ignore SIGILL in Gdb?"
1654223,2017-01-06 09:40:03 UTC,"Strange there seams to be nothing obvious at this point:
https://github.com/mixxxdj/mixxx/blob/master/vamp-plugins/plugins/KeyDetect.cpp#L357"
1654223,2017-01-06 09:48:37 UTC,Please post the output of the following. It will output the default compiler macros and the one for your device. Will there be a difference?
1654223,2017-01-06 10:15:56 UTC,Yes there is some differences.
1654223,2017-01-06 11:53:38 UTC,"I launch fresh build. I give result in some hours...
If necessary, I will try to ignore SIGILL."
1654223,2017-01-06 08:50:10 UTC,"With optimize=off, we progress.
Mixxx window now open, but I obtain new 'illegal Instruction' error, at around 1/3 of progress bar."
1654223,2017-01-06 16:18:44 UTC,"The result is as expected since the compiler produces slow code optimized
for debugging."
1654223,2017-01-08 23:18:38 UTC,"I have removed the msse2 flag and improved the comments:
https://github.com/mixxxdj/mixxx/commit/66fa24a6690fed77cae0423ce7b36704a31000de"
1654223,2017-01-10 09:25:51 UTC,"I try new build with optimize=native, but after modifying 'features.py'.
I use latest stable branch and comment line 1153 in features.py :
  build.env.Append(CCFLAGS='-msse2 -mfpmath=sse')"
1654223,2020-05-03 21:50:43 UTC,"The remaining crash is from the systems libportaudio.
We can't fix this. Sorry."
1654223,2020-05-04 06:41:33 UTC,"Thank you all for your time :-)
I recycled this venerable computer for other task (dmx)."
1654223,2017-01-06 14:18:38 UTC,"So have the same error when executing in build folder.
But after installing it (scons install) it work :-)"
1654223,2017-01-05 22:16:04 UTC,i5:
1654223,2017-01-05 15:07:59 UTC,I also receive this note from apt :
1654223,2017-01-05 22:06:41 UTC,I have checked again on my netbook and I am a bit disappointed
1654223,2017-01-05 22:11:49 UTC,the test of the link above gives:
1654223,2017-01-05 13:07:15 UTC,"The backtrace indicates that there is an issue with protobuf.
This can happen if you use a binary that is compiled with a different protobuf version."
1654223,2017-01-05 14:32:20 UTC,I try to start from the build folder and obtain same error.
1654223,2017-01-05 14:50:20 UTC,"Where did you get the source from?
Sometimes scons tricks us and does not complain about missing dependencies if you have switched branches.
Pleas start over in clean directory and follow the steps on the wiki.
https://www.mixxx.org/wiki/doku.php/compiling_on_linux"
1654223,2017-01-05 15:40:26 UTC,Did you?
1654223,2017-01-05 15:02:22 UTC,I already follow this page to compil.
1654223,2017-01-05 19:50:50 UTC,sigill implies Mixxx was built with options that are not supported on Pentium 3.
1654223,2017-01-05 16:17:28 UTC,"Yes I get source with :
git clone -b 1.12 https://github.com/mixxxdj/mixxx.git"
1654223,2017-01-05 22:06:33 UTC,I confirm that last build with 'optimize=native' give same error.
1654223,2017-01-05 20:12:45 UTC,Good catch! I did not noticed the Pentium 3.
1654223,2017-01-05 20:14:34 UTC,If this works we may consider to add it to the build instructions.
1654223,2017-01-05 20:39:46 UTC,"> optimize=native, should optimize for the building machine so this should be ideal in your case.
"
1654225,2017-05-31 20:18:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654241,2017-01-06 11:00:04 UTC,The direct cause for the collapse is the lack of session dbus: bug #1654365
1654241,2017-01-06 11:02:13 UTC,unity-system-compositor: bug #1654536
1654241,2017-01-06 11:35:51 UTC,click: bug #1654543 (unlikely to be a bigger problem)
1654241,2017-01-06 14:51:19 UTC,"diff of the rootfs between 102 (last known good image) and 116
device tarballs are identical"
1654241,2017-01-10 12:41:08 UTC,Images have been rebuilt with proposed disabled and boot successfully now. I added a comment to the SRU bug 1644323 and marked it as verification-failed. I'm closing this report.
1654241,2017-01-12 08:14:57 UTC,Reopening until root cause of the problem with dbus 1.10.6-1ubuntu3.2 in xenial-proposed is fixed and unblock the promotion of dbus to xenial updates.
1654241,2017-01-12 18:10:56 UTC,"Hello Jean-Baptiste, or anyone else affected,"
1654241,2017-01-17 16:07:11 UTC,"The verification of the Stable Release Update for dbus has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1654245,2017-03-16 10:41:09 UTC,https://bugs.launchpad.net/fuel/+bug/1664487
1654246,2017-02-01 02:46:55 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1654247,2017-01-05 15:27:19 UTC,Apparently the Python parser is able to parse expressions like the above properly.
1654247,2017-02-02 14:51:21 UTC,"There is more issues: Illegal characters in the dimension values are not recognized, again making the thresholder crash-loop."
1654247,2017-02-02 15:01:16 UTC,"diff --git a/monasca_api/expression_parser/alarm_expr_parser.py b/monasca_api/expression_parser/alarm_expr_parser.py
index 26568c9..97ce609 100644
--- a/monasca_api/expression_parser/alarm_expr_parser.py
+++ b/monasca_api/expression_parser/alarm_expr_parser.py
@@ -202,8 +202,9 @@ unicode_printables = u''.join(
     unichr(c) for c in xrange(128, 65536) if not unichr(c).isspace())"
1654247,2017-01-06 15:55:04 UTC,"I'm surprised it allowed that expression through as is, but I think it should be possible to fix that in pyparsing."
1654268,2017-01-12 01:57:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654276,2017-11-22 08:49:44 UTC,"Reviewed: https://review.fuel-infra.org/37244
Submitter: Dmitry Burmistrov <email address hidden>
Branch: stable/mitaka"
1654276,2017-01-05 18:23:05 UTC,2017-01-04 05:07:11 FAILURE Check state of haproxy backends on controllers (fuel_health.tests.ha.test_haproxy.HAProxyCheck.test_001_check_state_of_backends) Some haproxy backend has down state..
1654276,2017-01-05 18:42:11 UTC,http://paste.openstack.org/show/594036/ - haproxy logs
1654276,2017-01-06 13:07:45 UTC,"So, as we can see from the logs, haproxy backends get up a little bit later because haproxy has to perform at least 3 checks with interval of 3 seconds before declaring backends online. This means that we need to introduce a loop in the tests which checks several times which backends are online with an interval of 9 seconds."
1654276,2017-01-06 13:08:12 UTC,"2017-01-04 05:07:11 FAILURE Check state of haproxy backends on controllers (fuel_health.tests.ha.test_haproxy.HAProxyCheck.test_001_check_state_of_backends) Some haproxy backend has down state.. Please refer to OpenStack logs for more details.   File ""/usr/lib/python2.7/site-packages/unittest2/case.py"", line 67, in testPartExecutor"
1654276,2017-01-06 13:09:30 UTC,I mean that we need to wait for pacemaker to bring mysql up and then let haproxy set backends as online.
1654276,2017-11-21 13:28:51 UTC,"Fix proposed to branch: stable/mitaka
Change author: Vladimir Jigulin <email address hidden>
Review: https://review.fuel-infra.org/37244"
1654278,2017-01-23 21:30:41 UTC,"> This one ? lp:1399245
Hmmaybe it was this one.
But what I noticed now seems to be different:
Backpath is bigger and nicely scaled to fit the Widget, but it's always aligned to the left, regardless of 'background-position: center;' in qss.
Button text from <state_X_text> is always centered using 'text-align: center;', no matter if <Alignment> in button.xml is defined.
"
1654278,2017-01-21 12:04:33 UTC,"> (I seem to remember a bug report on this but can' find it)
"
1654293,2017-01-07 23:41:18 UTC,"It's easier to keep the language, I think, than removing and adding it back (I don't even know how that would work in the cms... but from previous experience, I suspect it will cause problems).
Maybe the availability will annoy someone so much, that they ask to join the translators ;-)"
1654294,2017-01-07 23:45:34 UTC,"Yes, we can do that, and you're very welcome to join website translators again :)"
1654294,2017-01-08 00:09:13 UTC,"Slovak added to trunk, rev. 1551."
1654294,2017-01-27 11:01:47 UTC,"I've been waiting for the website to update from r1445. It recently was updated, but only to r1550... ???"
1654294,2017-01-27 21:18:55 UTC,I believe that update was more of an accident...
1654298,2017-01-05 15:01:11 UTC,by the way: unav is working so gps works!
1654306,2017-01-12 19:21:13 UTC,"A bit more on the settings changes, I logged into the session again (and got windows) and the previous change to the show launcher setting got honored so it seems to have been written during the previous session. But again changing the setting did not adjust the UI dynamically. Perhaps something with the notification side of settings changes?"
1654306,2017-01-12 20:08:38 UTC,"Yeah that sounds about right, added gsettings-qt, but there's a chance the problem is with confinement, then."
1654306,2017-01-14 11:46:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654306,2017-01-12 16:46:08 UTC,according to the log in comment 3 it should actually have switched to windowed mode...
1654306,2017-01-12 11:37:30 UTC,I've tried to reproduce this but couldn't make it happen yet. Can you please attach unity8.log when it happens? Thanks.
1654306,2017-01-12 15:21:30 UTC,"Rebooted, opened a user session with unity8, and it was staged mode."
1654306,2017-01-11 21:12:48 UTC,"Just hit this again, here I have two users, one running unity7, and one with unity8 snap
This is the entire sequence but not sure if any of the steps are pre-requisites"
1654310,2017-07-05 22:23:21 UTC,"Hello Jason, or anyone else affected,"
1654310,2017-11-02 22:56:12 UTC,This bug was fixed in the package lxcfs - 2.0.8-1ubuntu1
1654310,2017-07-11 16:43:41 UTC,This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~17.04.2
1654310,2017-07-11 16:43:29 UTC,This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~16.10.2
1654310,2017-07-11 16:43:16 UTC,"The verification of the Stable Release Update for lxcfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1654310,2017-07-11 16:43:12 UTC,This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~16.04.2
1654310,2017-07-11 08:05:52 UTC,"After upgrading to lxcfs/xenial-proposed (2.0.7-0ubuntu1~16.04.2), the problem is fixed for me"
1654310,2017-07-05 22:22:55 UTC,"Hello Jason, or anyone else affected,"
1654310,2017-07-05 11:37:03 UTC,[Impact]
1654310,2017-07-05 22:21:56 UTC,"Hello Jason, or anyone else affected,"
1654310,2017-07-04 15:41:07 UTC,"@gozdal,"
1654310,2017-07-04 08:11:29 UTC,I believe that packages for several distributions (esp. Xenial) still contain this now-revered patch. Would it be possible to release packages with btime virtualization reverted?
1654310,2017-06-20 13:53:19 UTC,"On Mon, Jun 19, 2017 at 04:28:07PM -0000, Jason Baron wrote:

> Ok, I guess we could intercept the /proc/<pid>/stat read() call and
> overwrite the starttime there with the correct value? That is, add the
> starttime from /proc/<pid>/stat to the host boot time and then subtract
> that from the guest boot time.
"
1654310,2017-06-19 16:28:07 UTC,"Ok, I guess we could intercept the /proc/<pid>/stat read() call and overwrite the starttime there with the correct value? That is, add the starttime from /proc/<pid>/stat to the host boot time and then subtract that from the guest boot time."
1654310,2017-06-19 13:20:30 UTC,"On Mon, Jun 19, 2017 at 01:04:38PM -0000, gozdal wrote:

> This introduces a different problem: process creation time is counted as
> offset from btime:
>
> (22) starttime  %llu
>           The time the process started after system boot.  In
>           kernels before Linux 2.6, this value was expressed
>           in jiffies.  Since Linux 2.6, the value is expressed
>           in clock ticks (divide by sysconf(_SC_CLK_TCK)).
"
1654310,2017-06-19 13:04:38 UTC,This introduces a different problem: process creation time is counted as offset from btime:
1654310,2017-05-20 07:05:39 UTC,This is fixed in LXCFS 2.0.7
1654310,2017-01-30 17:49:49 UTC,"I've created a pull request to address this issue:
https://github.com/lxc/lxcfs/pull/169"
1654310,2017-01-06 15:43:23 UTC,Thanks I've created https://github.com/lxc/lxcfs/issues/164 to track this.
1654310,2017-07-04 15:45:25 UTC,I've pushed a package reverting that field to xenial-proposed - it will await approval there.
1654313,2017-02-08 17:21:35 UTC,"I could only reproduce it one way, by choosing switch user from the unity7 session. With this fix that path behaves properly.
I could not reproduce the other instance I'd seen where switching out of unity8 by selecting my unity7 account went to the lock screen, will keep watching."
1654313,2017-02-08 22:57:17 UTC,"Thanks Pat, I'll try and push the MP through then."
1654319,2017-03-24 18:33:42 UTC,vmss file is posted here: http://98.115.67.171/ex.zip
1654319,2017-03-28 00:51:42 UTC,"My VMs are running hwversion 13 on 6.5 (for several days now), but haven't hit this issue yet."
1654319,2017-03-19 01:26:03 UTC,"Im seeing this as well, from other posts ive seen the following is true:"
1654319,2017-07-07 07:08:01 UTC,"Please, can you confirm which is the ESX release or build with the fix implemented?"
1654319,2017-03-30 01:49:21 UTC,This is an issue in the vmxnet3 device emulation (ESX 6.5) and will be fixed in the next update.
1654319,2017-03-24 01:25:12 UTC,"also i saw your other thread where there is mention of the # of cpus being a factor. In my case i have 1 socket with 2 cpus assigned to each vm. I have 2 identical vms running haproxy. for whatever reason the primary typically locks up 2-3 times a day, the secondary is only once or twice a week."
1654319,2017-01-31 11:38:41 UTC,Is this still incomplete? I also think that importance should be higher
1654319,2017-03-23 00:58:10 UTC,I could not repro this issue locally despite running traffic for several hours.
1654319,2017-01-19 17:13:59 UTC,This is a fresh installation.
1654319,2017-01-05 19:16:56 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1654319,2017-01-05 16:31:54 UTC,This change was made by a bot.
1654319,2017-03-24 01:18:35 UTC,"Just to confirm your test, are you running a hw version 13 vm with kernel ~4.8? I am also using the driver provided in vmware tools 10.1.5"
1654320,2017-01-06 12:49:42 UTC,"Interesting. The failing test is the new ""sdk-examples"" autopkgtest that Debian added for 5.2."
1654321,2017-01-30 10:25:29 UTC,Another failure: https://ci.fuel-infra.org/job/10.0-community.main.ubuntu.bvt_2/1132/
1654334,2019-10-24 22:40:15 UTC,I think it would be better to pass decode_data=False as of 3.5 and handle the changed process_message signature.  I'm preparing a merge proposal to that effect.
1654334,2019-11-26 20:46:26 UTC,Fixed in lazr.smtptest 2.0.4.
1654338,2019-07-08 13:32:30 UTC,Please try again with a recent version. There was a switch vom python2 to python3 and gtk respectively.
1654342,2017-01-10 16:43:27 UTC,Not reproduced with Inkscape 0.92+devel r15407 (default prefs) on Ubuntu 14.04 with 'Scale test - all'.
1654342,2017-01-07 22:10:37 UTC,"Reduced test case created with Inkscape 0.48.5, displaying a regular and a flowed text created inside a vertically flipped group."
1654342,2017-01-07 21:07:59 UTC,@JazzyNico - could you please milestone to 0.92.1?
1654342,2017-01-05 18:13:31 UTC,"Nevermind - the reported issue is triggered by 'Scale elements' for the DPI change in Inkscape 0.92:
reproduced with Inkscape 0.92 r15299 on OX 10.7.5 and Windows 10"
1654342,2017-01-05 18:07:15 UTC,"Clarification:
My prior comment strictly refers to 'text put on path' in this specific file (sorry for the unclarity) - the existing text does not render flipped / mirrored in Inkscape 0.92, nor does regular or flowed text added to the current drawing level in Inkscape 0.92 appear flipped / mirrored."
1654342,2017-01-05 17:58:06 UTC,"Nothing specific to Inkscape 0.92 here (same happens expectedly with older Inkscape versions, too; tested and reproduced with 0.91 and 0.48.5)."
1654342,2017-01-05 18:22:26 UTC,Only affects flowed text (regular text is ok).
1654351,2017-01-05 19:06:39 UTC,The AI can't build anything from BuildWeapons. There should be a line in debug.log about this.
1654351,2017-01-05 20:29:54 UTC,Thank you. I forgot to put China as Owner of some buildings. Thanks :)
1654351,2017-01-10 04:58:11 UTC,"The [Animations] section and Warhead's AnimList= should have ApocAP, if not, then dunno what's the problem. In many cases the [Animations] section can be screwed and will require you to adjust the animation to another number."
1654351,2017-01-10 05:47:02 UTC,"^ *APOCEXP, my bad. It's in the Rulesmd"
1654351,2017-01-11 06:43:18 UTC,"That's right, the [Animations] list does not contain APOCEXP, and the game silently adds it when parsing AnimList= on ApocAP warhead. Ares expands the AnimList= tag to support more than 128 characters, but does not add the parsed values to the list like the game does. This can't be easily added back in, because the same function is used for 60 other tags. Generally it's bad style anyhow to silently add types like that, because every typo gets converted to a valid new type."
1654365,2017-02-01 03:55:32 UTC,"MIR_SOCKET is set by LightDM, so it will be present when the Xsession is run."
1654365,2017-01-27 08:37:11 UTC,"Well, if I comment out ""use-session-dbus"" in Xsession.options, the problem goes away, so I can't see how that doesn't get run..."
1654365,2017-01-26 20:35:28 UTC,I can't see any reason why LightDM could be affecting this - it only sets up the environment and then runs the session. Is this running under Mir? Because /usr/share/lightdm/lightdm.conf.d/52-ubuntu-touch.conf has:
1654369,2017-03-20 15:15:21 UTC,Do you have a branch for this?
1654369,2017-03-20 15:25:32 UTC,"I made the changes mentioned here and *thought* it did something, but on further testing it still fails when placing multiple holds for the same user. I haven't had a lot of time to fight with it. The short answer is no."
1654369,2017-03-20 15:47:29 UTC,OK. Thanks!
1654369,2017-11-15 15:26:44 UTC,Note: The code for bug 1694058 will make this easier once it goes in.
1654383,2017-01-05 20:51:36 UTC,Hi ScislaC. Here are a mockup. Individual page clear seems embarrasing to me.
1654383,2017-01-05 21:30:53 UTC,"Related earlier reports:
* Bug #170572 (sf1116104) “Revert to default settings”
  https://bugs.launchpad.net/inkscape/+bug/170572
* Bug #911700 “Preferences.xml file recovery”
  https://bugs.launchpad.net/inkscape/+bug/911700"
1654383,2017-01-05 21:48:20 UTC,"We even have a blueprint for that.
https://blueprints.launchpad.net/inkscape/+spec/multiple-preferences-management"
1654383,2017-01-24 13:28:16 UTC,"Related newer request (variation) filed as
* Bug #1658971 “Reset to default for each page in Preferences”
  https://bugs.launchpad.net/inkscape/+bug/1658971"
1654392,2017-01-06 09:37:31 UTC,"Hi,"
1654392,2017-02-09 04:39:35 UTC,"Thanks for the response and sorry for the delay! I actually don't burn optical discs very often anymore and needed to wait for another opportunity to arise (my discs are DVD+R which don't work with simulated writing, and I didn't want to waste them in order to test)."
1654392,2017-02-09 07:30:08 UTC,"Hi,"
1654395,2018-06-25 16:50:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577871"
1654395,2017-02-22 06:41:10 UTC,@David Moreau Simard  mind to push patch?
1654403,2017-01-12 00:25:16 UTC,Root cause:
1654403,2017-01-12 15:52:31 UTC,"Corey,"
1654403,2017-01-12 19:53:35 UTC,"This may have been fixed as of the 1.1.15-1 version of the pacemaker package. Prior to commit 071796e, ""Restart=on-failure"" was patched out. I've attached the diff of the commit that reverted that."
1654403,2017-01-12 20:01:05 UTC,"David, you could try adding ""Restart=on-failure"" back to the init file as a test.  If it works, we could look into backporting that to xenial, however I'm hesitant to do that until we know better why they dropped the restart bits in the first place."
1654403,2017-01-24 18:32:30 UTC,Additional information from the charm:
1654403,2017-01-25 16:04:59 UTC,"Reviewed:  https://review.openstack.org/419204
Committed: https://git.openstack.org/cgit/openstack/charm-hacluster/commit/?id=fda5176bd53f17a69f3e22b6b363bff96ff565c0
Submitter: Jenkins
Branch:    master"
1654403,2017-02-24 08:14:29 UTC,"Hi,
Corey mentioned 1.1.15 might be fixed a while ago.
You have all the context - is it?"
1654403,2019-07-04 03:09:06 UTC,"For this particular bug, it seems we have no description on why corosync was taking too long to start, just that it took too long and all the workaround made to pacemaker initialization and charm handling. With that, I'm marking corosync as incomplete for now, that I'm gathering all work to be done in HA packages. Please re-open this if you disagree, so we can discuss this bug again. Thank you!"
1654403,2017-01-12 13:19:01 UTC,"David, what release of ubuntu/openstack does this affect?  I'd like to see if we can get a package update in a PPA for you to test with."
1654404,2018-03-15 16:00:11 UTC,A patch has been posted that solved the ICE I get when compiling Clint's testcase. Once it gets committed and backported to stable branches of GCC we'll include it in our toolchain.
1654404,2017-01-05 23:13:20 UTC,"Oh, I forgot one additional thing:"
1654404,2017-01-12 17:32:06 UTC,The bug is due to s_buf not having the same alignment as struct MM. s_buf is 1-byte aligned (because the array element are char) but struct MM is 4-byte aligned because of the int attribute. I agree this should give an error rather than crash. That makes the fix lower priority though.
1654404,2017-01-24 16:34:33 UTC,"FYI, this has been raised against latest GCC version:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79085"
1654406,2017-03-06 17:45:50 UTC,Why is there no importance placed on this bug nor has it been assigned to anyone?
1654406,2017-01-30 03:21:13 UTC,As you can see tonight this was written to syslog almost exactly every 2 minutes between 8pm and 9pm
1654406,2017-03-04 14:43:38 UTC,I had to chance this from dconf to tracker. I filed the same bug with Gnome - https://bugzilla.gnome.org/show_bug.cgi?id=779342 and a fix has already been released.
1654406,2019-03-04 18:47:58 UTC,I have just now experienced this when doing an update on Linux Mint 19.1 Cinnamon.
1654406,2017-03-04 14:16:11 UTC,"Please see https://bugzilla.gnome.org/show_bug.cgi?id=779342 a fix has been made by Gnome tracker devs. Ubuntu tracker devs, please pick this up and apply."
1654406,2017-01-11 15:59:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654406,2017-02-25 04:14:14 UTC,I'm seeing this on Antergos recently. Have you been using gksu recently and otherwise-strange terminal errors started popping up?
1654406,2017-02-24 20:47:54 UTC,"Feb 24 13:05:11 localhost tracker-extract.desktop[3603]: (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
Feb 24 13:09:14 localhost tracker-extract.desktop[3603]: message repeated 2 times: [ (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.]
Feb 24 13:11:16 localhost tracker-extract.desktop[3603]: (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
Feb 24 13:13:18 localhost tracker-extract.desktop[3603]: (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
Feb 24 13:15:19 localhost tracker-extract.desktop[3603]: (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly."
1654406,2017-02-21 01:34:13 UTC,I'm still seeing this all the time. Is anything being done to fix the issue?
1654406,2017-02-25 14:02:18 UTC,"On Sat, 2017-02-25 at 04:14 +0000, Not Martin Wimpress wrote:

> I'm seeing this on Antergos recently. Have you been using gksu
> recently
> and otherwise-strange terminal errors started popping up?
>


I use gksu occasionally but not in the past month or so that I can
recall. This shows up constantly:"
1654414,2017-01-05 22:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1654414,2017-01-05 22:32:25 UTC,Unable to run the command as the system is completely frozen.
1654414,2017-01-06 16:00:53 UTC,Does this bug go away if you boot back into a kernel prior to 4.8.0-27?
1654414,2017-01-06 20:49:41 UTC,Booting back into 4.8.0-26 indeed makes the bug go away. 4.10-rc2 also does not freeze.
1654414,2017-01-13 16:29:45 UTC,Can you also give the latest upstream 4.8 kernel a test?  That will tell us if the fix in 4.10-rc2 was also cc'd to stable.  It can be downloaded from:
1654414,2017-01-15 12:48:04 UTC,"4.8.17 does not fix the issue, kern.log attached."
1654426,2017-07-23 04:50:23 UTC,I fixed this in my branch (linked).
1654426,2020-02-01 20:59:27 UTC,"Hi Philip,
Thank you for your contribution.
I believe this issue was resolved in 0.16.1.
https://github.com/rafalcieslak/harmonySEQ/releases/tag/v0.16.1
Also note that this project's development has been moved to GitHub."
1654428,2017-01-06 21:01:49 UTC,"Did you tried ? https://support.google.com/chrome/answer/95669
Why don't you report this bug to chromium ? https://bugs.chromium.org/p/chromium/issues/list"
1654428,2017-01-07 19:22:34 UTC,"Issue is resolved.  It appears I had a bad memory stick.  After removing the bad memory stick, everything seems stable."
1654428,2017-01-06 21:58:32 UTC,"Yes, I have tried those suggestions and none of them work.  I didnt report to Chromium issue/list because the problem  only occurs in Mint Linux 18.1 (i.e. on the same machine running Windows 7, the issue did not appear)."
1654447,2017-01-06 00:22:19 UTC,Bug #1624211  Duplicate of this bug....  sorry...
1654448,2019-02-22 11:28:45 UTC,"Chris,"
1654448,2019-02-22 11:06:04 UTC,"Hi Kai-Heng Feng, I experience a hissing noise on Ubuntu Ubuntu 18.04.2 LTS with Dell XPS 9370. Is there some patch I can apply to prevent this from happening?"
1654448,2019-01-08 01:37:20 UTC,"Not myself, no. That was just to cover duplicate bug 1809856. If that's incorrect, feel free to remove it."
1654448,2019-01-07 15:00:39 UTC,"Daniel,"
1654448,2017-07-04 08:35:07 UTC,"Thanks for your feedback, so I'll leave it as it is."
1654448,2017-07-04 08:16:07 UTC,"For the output volume I made the following observations:
* Even with a volume boost of 150% in Pulseaudio (the maximum), the output volume is still significantly lower than the unpatched kernel
* With 150% pulseaudio boost, I can hear disortions and crackling, so the sound quality gets significantly worse, the over-amplification is too much."
1654448,2017-07-03 04:57:42 UTC,Here you go:
1654448,2017-07-01 07:34:41 UTC,"On Sat, Jul 1, 2017 at 1:11 AM, Esokrates <email address hidden> wrote:

> Kai: I do not understand your last comment, could you elaborate? Did you
> mean we should test if software boost = pulseaudio boost performs well
> enough?
"
1654448,2017-06-30 17:11:57 UTC,"Kai: I do not understand your last comment, could you elaborate? Did you mean we should test if software boost = pulseaudio boost performs well enough?"
1654448,2019-02-25 01:41:05 UTC,You can use bug 1809856 for the 9370.
1654448,2017-06-30 12:13:11 UTC,Could you please post the patch for http://people.canonical.com/~khfeng/lp1654448-2/ ?
1654448,2017-06-30 12:12:36 UTC,"Kai, http://people.canonical.com/~khfeng/lp1654448-2/ does not have the hiss :-)."
1654448,2017-06-30 03:18:32 UTC,"Esokrates,
Traditional Microphone can work while disabling the hiss. I'll build a new kernel for you to test."
1654448,2017-06-30 02:53:27 UTC,I haven't yet tested the latest test kernels but disagree with comment #85.
1654448,2017-06-29 11:27:45 UTC,"Kai, Thank you very much for looking into this and answering questions. Kudos!
I think the behavior should remain as it is if the output volume is reduced that much AND support for microphone devices is crippled.
My arguments: It is still better to hear the hiss when music is at low volume than have low output volume enforced (on high output volume you do not notice the hiss) and additionally lose some functionality."
1654448,2017-07-01 07:57:38 UTC,"Kai, I compile my own kernels and I would like to use this right now, could you please link me the patch? The test kernel floods my syslog badly with touchpad debug entries (unrelated to this bug)."
1654448,2019-03-06 09:09:40 UTC,"Sure, Daniel, Kai-Heng. Please let me know what information you would like added to bug 1809856 for the 9370. FYI, the fix"
1654448,2019-10-12 21:49:19 UTC,The same happen with my XPS 13. Since a couple of days I have noticed this annoying hiss. I use Ubuntu 19.04.
1654448,2019-10-10 09:55:49 UTC,"I've recently just run into the same problem since recent updates, I've had my XPS since October 2017 and am currently running Ubuntu 18.04.3. No issues until last week. I think I may have selected ""headset with microphone"" by accident once when inserting headphones without a microphone, but no evidence that this was related; I just remember doing it when I don't recall doing that before."
1654448,2020-01-06 13:12:44 UTC,This bug was fixed in the package linux - 5.0.0-38.41
1654448,2020-01-06 12:53:38 UTC,This bug was fixed in the package linux - 5.3.0-26.28
1654448,2019-12-06 16:34:52 UTC,Verified the fix works on eoan with my 9360 running kernel 5.3.0-25 proposed. Updated the tag. Hope I did this right :S
1654448,2019-12-05 11:28:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1654448,2019-12-03 15:42:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1654448,2019-12-02 13:04:55 UTC,This bug was fixed in the package linux - 4.15.0-72.81
1654448,2019-11-29 07:43:00 UTC,It's the same one as #1845810 so we can mark it as verified.
1654448,2019-09-08 19:41:43 UTC,"Weird. I've had an XPS 9360 running ubuntu since November 2017. Last week I picked up all the updates from August, rebooted and ran straight into this bug with headphones that had previously been fine. I dual boot into Windows and that is fine so it isn't a hardware problem."
1654448,2019-11-29 07:22:13 UTC,@Kai-Heng: Is there something that needs to be done to verify this bug in -proposed?
1654448,2019-11-13 05:13:48 UTC,"I observe this on my XPS 13 9360.
As mentioned by others, the headphone hissing goes away when I mute the system or when I run ""amixer -c0 sset 'Headphone Mic Boost' 10dB"".  I created an even in /etc/acpi/events to call run this whenever headphones are inserted so that it persists after reboot."
1654448,2019-10-31 10:59:02 UTC,"Indeed, I forgot to upgrade so I missed the issue. Now that I did I see the hiss is indeed much louder. Thanks Kai for sending this upstream already."
1654448,2019-10-17 08:55:02 UTC,"The fix is now in upstream. Please refer to the patch for justification:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=1099f48457d06b816359fb43ac32a4a07e33219b"
1654448,2019-10-15 14:02:19 UTC,Like several of the most recent posters above I've had a 9360 for a couple of years without any hiss problems. A few days ago I started getting a pretty bad hiss thru headphones. Tried various headphones - all have bad hiss. All are ok on other devices. Running 19.04. Something has changed.
1654448,2019-10-14 07:15:34 UTC,"I've had this issue since 2017 all the time. As you can see in the comments, Kai suggested that this is an hardware issue. He developed a workaround for the kernel that I tested, however it made the general output volume significantly lower, see #96, which is the reason this fix was never shipped."
1654448,2019-10-13 22:18:28 UTC,"Same issue as previous 3 reporters. All was fine until the latest update(s), I now have the hiss back... Any idea on what might've changed?"
1654448,2017-06-29 11:11:26 UTC,"Yeah but I don't think it gets through to the right people. If I read most of the forums discussions no one acknowledges the problem. Only suggestions are to install the latest drivers.
The 9360 came out one year after the 9350 and still has the same issue. User's experiences are not that grave compared to driver developers that point out an issue."
1654448,2019-11-14 18:48:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1654448,2017-06-29 10:37:15 UTC,"I think they are already aware - a quick google on ""xps headphone noise"" shows several results, affecting all OS."
1654448,2017-06-30 13:40:34 UTC,That's exactly the testing kernel built for - to test if software boost performs well.
1654448,2017-05-29 14:03:50 UTC,"I tried blacklisting the snd_hda_codec_realtek module, sound works, but now I can hear the coil whine, depending on the activity of the cpu/gpu. Moving the mouse pointer around is clearly audible etc."
1654448,2017-05-19 07:42:59 UTC,Comment #12 suggests the fix is already released (a kernel fix). However that also suggests the fix was released before the bug was reported :) So logic says that first fix didn't work(?).
1654448,2017-05-19 06:30:55 UTC,I can't hear the hiss sound... either I am getting old or my headset is choppy.
1654448,2017-05-08 18:15:25 UTC,"@frail-knight, the right people are already subscribed to this bug. Please *stop* changing bugs to affect dell-sputnik"
1654448,2017-04-28 12:28:23 UTC,The mentioned workaround
1654448,2017-04-28 10:51:32 UTC,"Wow, thanks for the quick reply, I am willing to provide any information you need, thanks very much for having a look."
1654448,2017-04-28 09:49:10 UTC,"The patch is included in mainline, and it's included in Xenial since 4.4.0-25.
Also, our testing machines are not the final mass production version - I'll try get one and take a look on it."
1654448,2017-04-28 09:40:34 UTC,"Subscribed Kai-Heng Feng, the submitter of the linked patch (https://patchwork.kernel.org/patch/9128611/), maybe he could give a status update!?"
1654448,2017-04-23 11:21:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654448,2017-04-16 14:19:16 UTC,Looks like that patch has just sat there since last year :(
1654448,2017-06-29 09:45:41 UTC,"Kai: I understand what you are saying ... but I would find it great if you could point that out to Dell ... just because now it is bad, does not mean it can't be improved in the future. With proper hardware testing this could have been avoided."
1654448,2017-04-16 12:58:39 UTC,What's the diff between ALC256 and ALC3246??  It seems the 9350 has the ALC3246 as well.
1654448,2017-04-15 20:50:16 UTC,It looks like there was some activity with a kernel patch from someone at canonical at some point: https://patchwork.kernel.org/patch/9128611/
1654448,2017-03-12 13:52:51 UTC,It is!
1654448,2017-02-27 02:38:48 UTC,This bug is pretty obnoxious...
1654448,2017-02-23 15:42:30 UTC,"I would like to share that I found this post referring to a similar issue where sound settings weren't maintained, maintained being a better word than saved because I believe alsamixer might properly save the settings."
1654448,2017-02-22 16:08:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654448,2017-02-22 16:08:24 UTC,I'm experiencing the same issue:
1654448,2017-05-22 21:43:40 UTC,Here's an earlier bug report (~Dec 2015):
1654448,2017-05-24 16:38:19 UTC,"Kai, I have tested the 4.12 mainline kernel. The hiss is clearly audible.
Please make suggestions how I can help you."
1654448,2017-04-16 13:13:47 UTC,"ALC256 looks like a codec, and I always thought ALC 3246 was the Realtek ""model/chip"".  Not sure if my thoughts on that are accurate."
1654448,2017-05-25 00:12:18 UTC,"I would like to say I have plain old Sony earbuds, and the sound is very noticeable without playing any sound what so ever.  As previously mentioned, upping the dB gain on the headphone mic boost from 0.00 to 10.00 completely stops the hissing for whatever reason."
1654448,2017-05-24 17:00:14 UTC,Addendum to the original description:
1654448,2017-05-29 07:14:34 UTC,"Well, the problem might be more noticeable with low-impedance earphones/headphones. So more likely earphones, but possibly also headphones. (<--- This is now guessing)"
1654448,2017-05-29 06:54:30 UTC,"@vanvugt: I can clearly reproduce the problem with headphones too, I do not notice they ""hide"" anything."
1654448,2017-05-29 02:14:15 UTC,@kaihengfeng: I found the problem was only really noticeable with earbuds. Headphones tended to hide the problem.
1654448,2017-05-26 15:30:55 UTC,"Great, Kailiang has Launchpad account =)"
1654448,2017-05-26 15:25:45 UTC,"Sorry, my bad, ALC256 doesn't have aaloop at first place, so my kernel does nothing =("
1654448,2017-05-26 12:51:49 UTC,Confirming Daniel van Vugt: The kernel http://people.canonical.com/~khfeng/lp1654448/ does not improve the situation.
1654448,2017-05-26 10:46:58 UTC,@vanvugt: The earphones I tested (Bose Soundtrue Ultra) are Android ones. I have also tested headphones with no microphone (Sennheiser HD202).
1654448,2017-06-30 06:17:02 UTC,Here you go:
1654448,2017-05-26 07:05:16 UTC,"@Esokrates that's weird. I can install the kernel, even on my Zesty machine."
1654448,2017-05-26 01:47:35 UTC,There are multiple variables here you need to consider...
1654448,2017-05-25 20:39:56 UTC,@vanvugt  I do have both cable types (with and without cable mic).  In testing the Quiet Comfort 15s:
1654448,2017-05-26 09:58:27 UTC,"^^^
Confirmed on an XPS 13 9350 too. And the 'Headphone Mic Boost' workaround works. Although like others, I find that concerning since it should in theory make the problem worse or make no difference."
1654448,2017-05-25 19:30:31 UTC,"Regarding the Bose Quiet Comfort ... those are noise cancelling headphones, it is no surprise to me that those cancel the hiss.
I have tested multiple normal earphones and I can reproduce the issue everytime."
1654448,2017-05-25 19:12:25 UTC,"@spike speigel: The tlp issue in the arch Linux wiki is unrelated. The point I was that when tlp is installed and no audio is currently playing, tlp turns off the sound card and thus the hiss disappears.
The second point I was trying to say: Of course the white noise is audible when nothing is playing, but only if audio is not muted."
1654448,2017-05-25 09:43:35 UTC,"Please try this kernel: http://people.canonical.com/~khfeng/lp1654448/
AAMIX is disabled, I can't verify it through my bad ear though."
1654448,2017-05-25 01:45:38 UTC,Please try both cable types of the Bose Quiet Comfort (assuming you have two). And you might want to try my favourite trick of plugging in via a headphone splitter/extension/adapter. Sometimes you just have to piggyback on a different connector to get a clean connection.
1654448,2017-05-25 00:18:47 UTC,"Out of curiosity I tried my Bose Quiet Comfort 15s, and I can't detect the hiss in those at either a dB gain of 0.00 or 10.00 with the headphone mic boost."
1654458,2019-08-25 12:42:02 UTC,This still wasn't addressed in 2019...
1654458,2017-01-09 10:27:59 UTC,This was fixed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=753123
1654458,2017-01-16 00:54:18 UTC,"@Murray Thank you for your comment. I could not find any package for ubuntu that has this fixed. As it is an ABI breakage, as I understand, any project that wants to use C++11 standard (let alone C++17) will want to immediately start to demand and link with the new libxml++; so it's a problem that there isn't a package in ubuntu for that in 2017. Or am I missing something?"
1654459,2017-07-23 05:10:50 UTC,"Does this still occur on Ubuntu 17.04 ""Zesty Zapus"" with vlc 2.2.4-14ubuntu2.1 ?  If you are able to test on Ubuntu 17.10 ""Artful Aardvark"" with vlc 2.2.6-3build1 that would be even better."
1654459,2017-08-17 02:48:00 UTC,Tested with vlc 2.2.6-3build2 (from artful) and got the same behavior as originally reported.
1654459,2019-11-10 18:15:57 UTC,"vlc 2.2.x is no longer supported. If this issue still exists with vlc 3.0.8, please report it to the upstream bug tracker at https://trac.videolan.org/vlc/."
1654461,2017-03-15 22:44:05 UTC,"I have a similar result for a 32 bit install, see below.
however these settings are not sufficient to guarantee that Inkscape will be the default program for svg files. In my case IE11 is the default program for svg files, which is the way I prefer it. But Inkscape will show up when you do a right click and select ""Open With..."""
1654461,2017-03-15 21:54:28 UTC,"> could you at least export and attach the content of the registry key ""HKEY_CLASSES_ROOT\Applications\inkscape.exe""
"
1654461,2017-03-15 21:51:18 UTC,"> Great! Please provide a patch if you know the ""correct"" registry settings. ;-)
"
1654461,2017-03-15 09:16:55 UTC,Could calling inkscape64.exe the 64 bit executable help?
1654461,2017-03-15 06:52:15 UTC,"@Eduard
Yes, the bug in #5 describes exactly what I find. I'm using german Windows 7, 64-Bit. Had no idea that you cannot reproduce it or that it could be language dependent.
Deleting the registry key helped me out. Thank you."
1654461,2017-03-14 22:48:46 UTC,"> Both problems could easily be solved with the correct registry settings.
"
1654461,2017-03-14 13:29:51 UTC,"> This is not low priority!
"
1654461,2017-03-14 08:39:23 UTC,"Same problem here. On some machines I could ""open with"" and select inkscape as default, on some I can not select inkscape. I can browse to the inkscape program directory and select inkscape.exe but it still opens with IE. I also used 64 bit exe installer.
This is not low priority!"
1654461,2017-01-07 23:31:43 UTC,"We do not register .pdf so this is ""by design""."
1654461,2017-01-07 13:12:19 UTC,"A recurring issue? Some related earlier reports (there might be others):
Bug #1360906 “Inkscape does not register the *.svg file extension”
Bug #1399720 “91 pre msi breaks Chrome SVG render”
Bug #1417146 “0.91, 64-bit unable to associate SVG with Inkscape in Win7, 64-bit”"
1654461,2017-01-07 12:06:47 UTC,"> Could you please specify whether you used the .msi installer or the .exe installer?
"
1654461,2017-01-07 00:33:40 UTC,Could you please specify whether you used the .msi installer or the .exe installer?
1654461,2017-03-14 21:52:59 UTC,"> It would be very helpful to know if this is a duplicate of bug #1417146 or if this is a different issue.
"
1654461,2017-01-07 00:34:27 UTC,Also OS version is relevant.
1654462,2017-01-08 07:52:41 UTC,uwestoehr> SO I think it is a bug in the internal importer of Inkscape and not in the PDF.
1654462,2017-01-06 07:04:42 UTC,"Thanks for the report, Uwe!"
1654462,2017-01-07 12:15:51 UTC,"> Manually removing the element with id=""mask3724"" fixes the issue.
"
1654462,2020-11-19 15:32:42 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here. We don't really have a suitable label that meets out needs (per https://alpha.inkscape.org/bug-migration/), so we mark these bugs Invalid."
1654479,2017-01-20 17:41:28 UTC,"There's noting in apport that writes ""bad_core_pattern"". I also looked in ubuntu-system-settings and didn't find anything there either."
1654479,2017-01-20 19:29:53 UTC,This is set per the fix for lp:1505302 but that also sets suid_dumpable to 0. The core pattern seems moot in that case?
1654479,2017-01-23 01:46:59 UTC,"Indeed, it sounds like that would make this moot. So it's an invisible issue, but still worth fixing. We still don't want core files unexpectedly appearing if the other factors happen to go away in future."
1654480,2019-12-14 05:31:59 UTC,"With the SoundTouch algorithm there isn't much improvement with a window size below 10ms. I found a quicker way to test various parameters using mpv, which uses same/similar algo. When I get some time I'll generate random samples with various parameters and do a blind perceptual test."
1654480,2019-07-19 20:18:07 UTC,"Paul, do you have any thoughts on the difficulty of a fix here and if there are any related audio bugs we should be aware of/link to this bug?"
1654480,2019-07-22 16:11:20 UTC,"It would be 1383363, and it's not too hard for someone that knows how to write DSP code, but needs to be prioritized."
1654480,2019-07-22 21:06:05 UTC,"I also just want to clarify: I notice this at 1.5 and 1.75 and 2x speeds as well, it's just more subtle - definitely still there though. Since the title here is talking about the issue at higher speeds, just want to make sure that it's not ignored for speeds <2x."
1654480,2019-12-06 05:21:29 UTC,I used MOZ_DUMP_AUDIO=1 to capture samples from 1x vs 3x. The waveforms at 3x are identical to 1x for about 45ms. Then it skips and copies another 45ms.
1654480,2019-12-06 05:24:22 UTC,"Created attachment 9114054
2019-12-05_21-09-44 3x identical to 1x.png"
1654480,2019-12-06 05:25:26 UTC,"Created attachment 9114055
2019-12-05_21-14-30 missing samples.png"
1654480,2019-12-06 07:29:55 UTC,From the author: https://www.surina.net/article/time-and-pitch-scaling.html
1654480,2019-12-13 09:09:37 UTC,"Created attachment 9115722
sequence-size-comparisons.zip"
1654480,2019-12-13 15:23:38 UTC,Thanks. The patch is a significant improvement!
1654480,2019-07-19 19:29:41 UTC,"(In reply to Bryce Seager van Dyk (:bryce) from comment #7)

> I've been unable to repro this on OSX and a couple of other systems I've
> tested.
>
> Isaac, are you still seeing issue? If so, could you please gather a log
> using MOZ_LOG=MediaFormatReader:5?
"
1654480,2019-12-16 13:06:36 UTC,"Pushed by <email address hidden>:
https://hg.mozilla.org/integration/autoland/rev/f21621632fac
Improve libsoundtouch high playback rate speech clarity with pitch preservation by using a smaller time stretcher sequence size r=padenot"
1654480,2019-12-16 17:23:51 UTC,https://hg.mozilla.org/mozilla-central/rev/f21621632fac
1654480,2019-12-29 11:18:32 UTC,"Not sure whether this is considered inappropriate here, however I just wanted to say thank you tackling this issue."
1654480,2020-01-06 08:44:10 UTC,"Release Note Request (optional, but appreciated)
[Why is this notable]: Vastly improved audio quality when changing the audio playback rate during media playback. This was requested for years, and brings Firefox closer perceptually to other browsers
[Affects Firefox for Android]: yes
[Suggested wording]: Improved audio quality when playing back audio at a faster or slower speed
[Links (documentation, blog post, etc)]:"
1654480,2020-01-06 20:19:19 UTC,"Added to the Beta73 relnotes, thanks for flagging this."
1654480,2020-02-05 07:23:43 UTC,"Firefox is an essential project. I am so god damn happy that this has been fixed. omg. a basic feature built into youtube/audible, any major media distributor has built in speed controls expecting functional browser implementation. especially in the era of chromium based browser monopoly this is important. (I don't trust chromium even though it is open source) I listen to audio at like 3.5-5.5 speeds with closed backed studio tuned headphones and any improvement can be noticeable. I can't get past 2.0-3.0 with laptop speakers on chrome/firefox 73 or with pre firefox 73 and headphones. but now, YEET Chrome, google. I moved my bookmarks over and deleted most of my chrome data already this here is my last action on chrome before uninstall."
1654480,2020-02-05 11:31:27 UTC,Clearly something that we can do yes. I'm going to think about it today. Thanks for your kind message!
1654480,2019-12-13 09:54:12 UTC,"Created attachment 9115728
Bug 1427267 - Improve libsoundtouch high playback rate speech clarity with pitch preservation by using a smaller time stretcher sequence size"
1654480,2019-05-04 20:41:03 UTC,"I believe this is due to Firefox playing ~70ms samples of audio at original speed, and skipping between them. In my experience with a similar effect in mplayer (https://mplayerhq.hu/), blending samples of about 15ms produces quality comparable to Webkit (Chrome, Opera)."
1654480,2019-12-06 07:12:40 UTC,I started digging into the SoundTouch library and confirmed my suspicion. https://hg.mozilla.org/mozilla-central/file/tip/media/libsoundtouch/src/TDStretch.cpp#l637
1654480,2018-09-15 12:25:11 UTC,"Created attachment 9009354
wavy-intro-tune.png"
1654480,2018-12-27 05:29:35 UTC,*** Bug 1515054 has been marked as a duplicate of this bug. ***
1654480,2018-01-03 09:15:41 UTC,I can't repro the issue.
1654480,2018-01-09 07:17:01 UTC,Playing a video from the local filesystem has the same effect. Networking is not the issue since video playback works perfectly fine in WebKit-based browsers.
1654480,2018-01-10 03:59:04 UTC,"Can you launch firefox from the console by doing:
MOZ_LOG=MediaDecoder:4,AudioStream:3 path/to/your/firefox ""https://www.youtube.com/watch?v=K0Tsa3smr1w"""
1654480,2018-01-10 09:33:28 UTC,"Created attachment 8941359
fflog.log"
1654480,2018-02-20 18:56:39 UTC,"Bryce, do you have any interest in the playback rate stuff?"
1654480,2018-02-23 16:33:32 UTC,":rillian, I've taken a look and can't repro thus far. I'm going to hold the needinfo while I wait for some new hardware to arrive and then I'll be able to test this on OSX and see if I have any more luck."
1654480,2018-04-11 15:36:00 UTC,I've been unable to repro this on OSX and a couple of other systems I've tested.
1654480,2018-04-12 04:45:55 UTC,"Created attachment 8967249
newlog.log.gz"
1654480,2017-12-28 13:31:48 UTC,Steps to reproduce:
1654480,2018-04-12 04:52:28 UTC,"Created attachment 8967251
opera.mp3"
1654480,2018-09-15 12:24:34 UTC,"Created attachment 9009353
missing-word.png"
1654480,2018-04-12 04:51:46 UTC,"Created attachment 8967250
firefox.mp3"
1654480,2018-07-16 04:00:54 UTC,This bug should have been opened with Firefox instead. I found the ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1427267
1654480,2018-07-16 03:59:25 UTC,"This is the #1 reason I don't use Firefox for YouTube. Chrome plays back audio smoothly at 4x. Firefox sounds like it's dropping samples after 2x. This might not be problematic for music, but extremely problematic for speech."
1654480,2018-09-15 12:22:56 UTC,"I did a visual comparison of the two samples in Audacity and while they look similar there are occasionally dropped words which are detectable in playback. For example 8 seconds into the Firefox sample (27 seconds in original) is the line ""So for people who don't know"" and the word ""for"" is missing."
1654480,2018-05-20 09:43:50 UTC,"I can reproduce this bug on version 61.0b6, currently the latest release for Developer Edition."
1654480,2018-04-12 04:55:21 UTC,"If you play the recording from firefox, you can see that the words are mangled, compared to that from Opera. You can clearly tell that some audio segments are completely skipped over if you slow down the playback. The audio from Opera isn't that different, from what I can hear, to that of Chrome's. I haven't tested it on Safari."
1654480,2018-06-28 10:41:12 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version.
1654487,2017-01-11 13:39:03 UTC,Any update on this thread ?
1654487,2017-02-08 09:33:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430684"
1654487,2017-03-23 12:45:35 UTC,"Novaclient is perfectly capable of displaying allocation ratios, would they be exposed by nova-api."
1654487,2017-11-16 15:53:58 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/430684"
1654487,2018-04-03 03:02:40 UTC,"In nova side, the blueprint and spec are required because of API microversion is bumped.
So set the importance to 'Wishlist'."
1654491,2017-12-30 00:16:52 UTC,+1 this would be a great feature!
1654491,2020-01-19 10:25:21 UTC,Possibly related: https://bugs.launchpad.net/mixxx/+bug/1206676
1654491,2017-12-29 22:26:13 UTC,"Ferran, would you like to this for 2.2? We are planning to feature freeze 2.2 six months from now. If you want to implement this, please assign yourself to the bug."
1654491,2017-08-01 16:16:24 UTC,We could set the full allowed range of many parameters be very wide and by default narrow the range to what we think is most useful.
1654491,2017-12-29 20:56:56 UTC,"We could also let users choose among different curves for the parameter: linear, exponential,..."
1654493,2017-09-11 14:18:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654494,2017-01-06 08:57:15 UTC,"There are no tarballs because GBP hasn't caught up with Newton yet. It's definitely planned to release a stable/newton but the work to sync the master with newton has not yet started. We hope to do this soon, but all contributors to the project are still working on features and/or drivers that use mitaka as the base."
1654498,2019-02-05 20:33:54 UTC,moved from https://bugs.launchpad.net/yade/+bug/1654498 to https://gitlab.com/yade-dev/trunk/issues/31
1654515,2019-09-19 14:53:00 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1654518,2017-01-11 23:29:58 UTC,Manual doc issue created: https://github.com/juju/docs/issues/1592
1654518,2017-01-12 10:27:39 UTC,"Just for clarification, the substantive part of this bug is the help-text in Juju. Current stable docs are correct"
1654519,2017-01-06 10:02:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417334"
1654529,2020-02-20 16:41:52 UTC,"Pushed to master, 3.3 and 3.4 - thanks Kyle and all!"
1654529,2020-02-19 13:14:46 UTC,I changed call numbers for items in the sandbox server to match those in the examples above and they are still sorting incorrectly as in the first example. I tested it with and without spaces as well.
1654529,2020-02-19 16:36:57 UTC,"We (mostly Elaine Hardy) tested as well, and confirmed Remington's feedback that as long as the Library of Congress Call Numbers use the LCC schema, they sort correctly."
1654529,2020-02-19 14:36:54 UTC,"Kate, I just found that the HV call numbers that were in the ""Call Number Testing"" copy bucket on the sandbox server both had the call number classification of ""Generic"". When I changed them both to ""Library of Congress"", then the copy bucket sorted them correctly. (Thanks to Kathy's clue in comment #3.) Now I'm seeing this correct order:"
1654529,2020-01-21 22:41:00 UTC,https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1654529-callnumber-sorting-by-sortkey
1654529,2020-01-16 18:47:09 UTC,"I've also confirmed the issue. It appears this may be a limitation with the Grid, rather than the interface itself - I'm thinking an option to sort by sortkey(programatically looking for columns with the same name as the expected column, but appended with _sortkey) would be the way to go. Looking into how to implement this now."
1654529,2019-10-03 20:51:58 UTC,Blowing off the dust on this and setting to Confirmed. Call numbers are sorting by label rather than label sortkey in copy buckets and transit lists. Tested this on Evergreen 3.2.8.
1654529,2018-10-16 19:14:49 UTC,"Adding a note that I tried these specific call numbers on the community demo server. With the classification scheme set to LC, I saw the following in the call_number sortkey field:"
1654529,2018-10-16 19:04:37 UTC,"Hi Rosie,"
1654529,2018-10-16 18:17:36 UTC,This (I think it's the same bug) also affects the Shelf Browser (in the public OPAC). The sort is not parsing LC call numbers numerically.
1654532,2017-01-06 10:55:23 UTC,"Strangely, if I use ""play"" in my script rather than mplayer and start it with:
~/Softs/alarm.sh &
Then I have no sound until I type fg...
There MUST be some system-wide audio thing I do not understand."
1654532,2017-01-06 13:03:12 UTC,"Still more strangely, if I use ""play"" in my script, which makes it work, but then call the script from cron, it does not work again.
[BTW, mplayer never works in cron since it does not work in a script]"
1654532,2017-01-06 13:08:31 UTC,"I'm now wondering if that could be a bug in pulse, since the output of mplayer shows that it believes it plays the sound correctly, whereas there's no sound in the speaker..."
1654532,2017-01-08 11:31:47 UTC,"While shutting down my computer, and particularly when closing FF, I realized that sounds do indeed play!!"
1654536,2017-04-24 06:57:05 UTC,The Android platform was deleted from lp:mir at revision 4155.
1654536,2017-01-10 16:00:15 UTC,It could be that /etc/init/keep-display-on-during-boot.conf needs to be ported to the systemd services. Not quite sure I understand enough about the v+o to x+o (and upstart to systemd) to quickly diagnose if the startup power situation is correct at time of error during bootup.
1654536,2017-01-10 14:27:37 UTC,Was able to see the error on startup in the bug in USC.
1654536,2017-01-09 19:47:38 UTC,Is the frieza_arm64 channel in a sane state? (I remember it being usable about a month or so ago) I can't seem to even get to the dash. The mir demo stuff is seems to work though.
1654536,2017-01-09 18:24:22 UTC,"re the 600mb available, it could be some other resource than system memory that the driver cannot access, given the limited enums the gl driver can return."
1654536,2017-01-06 19:21:47 UTC,"Thing is this only ever happens on boot, and u-s-c gets restarted and subsequently works fine, with `free` reporting 600MB memory free. The leak would have to enormous as this happens within seconds from the device booting."
1654536,2017-01-06 13:03:18 UTC,"I somewhat doubt that quirk would help, iirc, it was added after reports that it helped from the bringup (but by the time it got released it didn't seem to do anything in my local testing)"
1654536,2017-01-06 12:57:05 UTC,"Too little too soon, just got the same exception thrown."
1654536,2017-01-06 12:55:04 UTC,"<greyback> Saviq: also can you get the value of the ""ro.build.product property"" and see if it matches ""Aquaris_M10_FHD"" - mir implements quirks which depend on that
<Saviq> ""frieza""
<greyback> Saviq: hmm that doesn't match what Mir expects
<Saviq> could be a clue
<greyback> could you add --fb-ion-heap=false to USC's command line?"
1654536,2017-01-06 12:37:24 UTC,Logcat output: http://paste.ubuntu.com/23751952/
1654536,2017-01-06 11:10:11 UTC,Thank you for your report!
1654536,2017-01-06 11:10:03 UTC,"Stacktrace:
 #0  0x0000007fa41dd5e8 in ?? ()
 No symbol table info available.
 #1  0x0000007fa52061e0 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()"
1654536,2017-01-06 12:57:39 UTC,This is what's shown in logcat when it crashes:
1654546,2017-01-09 01:08:14 UTC,"Firstly, it does not look like you are using the official raspberry pi kernel for Xenial. Your kernel is 4.1, and the Xenial kernel is 4.4, so it is possible that the kernel you are using does not have the required apparmor bits that Ubuntu needs."
1654546,2017-01-09 17:39:51 UTC,"Yes, I am using xenial 16.04 (I made a typo in the description). So its because the raspberrypi version ships with an older 4.1.19-v7 kernel in the package raspberrypi-bootloader i think."
1654546,2017-01-10 14:48:32 UTC,"In the logs I just get these repeated over
$ sudo journalctl -u brltty.service --since=today
-- Logs begin at Fri 2017-01-06 06:48:58 GMT, end at Tue 2017-01-10 14:47:03 GMT. --
Jan 10 14:45:27 sampi systemd[1]: Started Braille Device Support.
Jan 10 14:45:27 sampi systemd[16953]: brltty.service: Failed at step SECCOMP spawning /bin/sh: Invalid argument
Jan 10 14:45:27 sampi systemd[1]: brltty.service: Main process exited, code=exited, status=228/SECCOMP
Jan 10 14:45:27 sampi systemd[1]: brltty.service: Unit entered failed state.
Jan 10 14:45:27 sampi systemd[1]: brltty.service: Failed with result 'exit-code'.
Jan 10 14:45:57 sampi systemd[1]: brltty.service: Service hold-off time over, scheduling restart.
Jan 10 14:45:57 sampi systemd[1]: Stopped Braille Device Support.
Jan 10 14:45:57 sampi systemd[1]: Started Braille Device Support."
1654546,2017-02-21 19:57:43 UTC,Still an issue with the 4.4.38-v7+ kernel that recently arrived in Ubuntu MATE 16.04
1654546,2017-06-16 00:20:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654558,2017-01-06 14:17:44 UTC,Other options include:
1654558,2017-01-06 14:28:24 UTC,I should have noted.  I did pull v.6.12 from CPAN and it did not resolve the issue.
1654558,2017-01-06 14:39:41 UTC,"Thanks for the update, Bill! That will save some testing time."
1654558,2017-01-06 14:40:32 UTC,"Oh, I should add this also affects Content Cafe."
1654558,2017-01-08 00:05:58 UTC,"Yeah, I am probably not going to get to this right away, so removing myself in case someone else wants to have a look."
1654558,2019-02-08 18:01:09 UTC,Hello. We ran in to this bug as well after upgrading from Ubuntu 14 to 16 (Trusty to Xenial). Net::HTTP 6.17 appears to work correctly. We installed the Bionic libnet-http-perl package as found here:
1654559,2017-01-09 13:43:41 UTC,Is there anything else I should do to confirm whether or not this is an upstream issue?
1654559,2017-01-09 13:42:51 UTC,I have now confirmed the same behaviour with Realtek driver v1.029 and Kernel 4.4.0-21-generic.
1654559,2017-01-06 19:52:27 UTC,I have confirmed behaviour with mainline kernel 4.10.0rc2 both with the included driver module (r8169) and the recommended Realtek driver v1.030 (r8101). Both drivers exhibit the same behaviour.
1654559,2017-01-06 15:54:10 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1654559,2017-01-06 14:00:58 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1654559,2017-01-06 15:21:25 UTC,"Cannot execute apport-collect as it fails with error ""ERROR: connecting to Launchpad failed: Unable to find the server at Launchpad.net"""
1654561,2017-04-05 23:21:47 UTC,"The reference that was 192 MB of RAM was for the server edition only, and was updated to 256 MB recently. While 256 MB works for me, it doesn't work for someone else. See also: https://bugs.launchpad.net/serverguide/trunk/+bug/1294908"
1654562,2017-01-06 14:38:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417399"
1654562,2017-03-09 21:31:57 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/417399
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1654562,2017-09-26 22:49:20 UTC,Unassigning due to no activity for > 6 months.
1654565,2017-01-23 14:31:18 UTC,"I attached a (edited) screenshot. This is a simple recolour of the current workarea3.png and shows roughly what I had in mind. I'm not sure about the visibility of the colour, I'd be open for suggestions. It doesn't look so bad on this screenshot though and the viewing range doesn't have to stick out as much as the work area itself, in my opinion."
1654565,2017-01-06 21:08:02 UTC,"I am not against this but i feel it is not needed. You could just build a road on the border on mountains and dismantle the military building. Because the carriers have also a view-area, most of the mountains stay visible."
1654565,2017-01-08 08:40:13 UTC,"The benefit would be pretty much the same as displaying the work area. Sure, one can count the nodes manually but having an overlay for the work area then would be obsolete as well. Counting manually is rather tedious and error-prone. And it costs a lot of time, if you have to do it again and again (not good for powergaming, too :P )."
1654565,2017-01-17 17:58:06 UTC,"I think it's a good idea, if we can make the graphics work - it's of particular interest when choosing a building to place."
1654565,2017-01-17 19:12:21 UTC,"> I wanted to make a sample graphic but when I took a look
> at the current overlays I found out that a third overlay
> exists (workarea3.png). I have never seen it before ingame,
> what is it designed for?
"
1654565,2017-01-23 16:20:02 UTC,I think that looks pretty good :)
1654565,2019-09-17 08:23:01 UTC,Migrated to https://github.com/widelands/widelands/issues/2067
1654566,2017-01-09 09:49:51 UTC,"I can reliably observe the issue on my krillin running rc-proposed. A simple UA override seems to ""fix"" the issue. There’s nothing in the logs when tapping on the select dropdowns, so they must be disabled. Why a website would disable dropdowns conditionally on the UA string is beyond me…"
1654568,2017-01-09 01:46:44 UTC,"Interesting it's always and only the OSK we have rendering trouble with (see also bug 1590765, bug 1649077). Might be worth looking into how the OSK renders differently to other apps."
1654568,2017-01-11 01:36:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654570,2017-01-06 14:23:33 UTC,"""avprobe"" says:"
1654570,2017-01-12 22:53:16 UTC,"I can confirm this. I also noticed that, before I tried to generate a waveform, Openshot was using 187.6 MiB of RAM, after I told it to generate a waveform though it just started increasing forever. The few times I tried it got over 1 GiB before I killed it."
1654571,2018-02-23 16:47:35 UTC,Changed title to not be confused with copper zones.
1654571,2018-10-16 14:10:49 UTC,"One ideia of an EDA software that recently add this feature
http://labcenter.s3.amazonaws.com/movies/v8/DesignRules.html"
1654571,2019-05-08 23:52:08 UTC,"Linked with lp:1767349
See doc https://docs.google.com/document/d/1qvCH9aHwCzp5qtKTna4jJXuloNU0b96gAxAHSKPuXpU/edit#heading=h.ykrpi4h5njn"
1654576,2017-11-12 14:15:15 UTC,"I think a road map to this feature could be something like
https://www.youtube.com/watch?v=SoQPNqwEJhk"
1654577,2017-01-10 07:24:38 UTC,"Hello sureshbabu, thanks for reporting."
1654583,2019-09-15 16:58:03 UTC,Migrated to https://github.com/widelands/widelands/issues/1042
1654583,2019-08-31 11:31:45 UTC,"I guess the reason that we can't detect anything is that we'd need something like ""OpenGL shading language version string: 1.20"", which isn't reported by your graphics driver. 1.20 is our minimum supported version for the shading language."
1654583,2019-08-21 15:11:38 UTC,"Hi,"
1654583,2017-07-03 08:26:20 UTC,Came across this issue again since bug 1701966 was just reported.
1654583,2017-01-08 19:59:12 UTC,What I’m more concerned about is the OpenGL version. It’s said to be:
1654583,2017-01-08 19:04:22 UTC,"glxinfo only reports Mesa. AFAIK this is a software only renderer for OpenGL. It seems likely that SDL ignores this, as it will not provide hardware accelerated graphics (which are now required for b19)."
1654583,2017-01-08 15:55:56 UTC,"I now downloaded the build-18 package for reference (and data for build-18) and unpacked the deb. Got it from packages.ubuntu.com and it's the package for my Ubuntu version. After copying a font file around, I was able to run build-18 under my home dir. So:"
1654583,2017-01-08 14:27:39 UTC,please also report output of glxinfo.
1654583,2017-01-08 14:37:41 UTC,"dakkus@ubuntu:~$ glxinfo
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile,
    GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample,
    GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
    GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
    GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
    GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
    GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
    GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile,
    GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
    GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample,
    GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,
    GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float,
    GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context,
    GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
    GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
    GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
    GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
    GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile,
    GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB,
    GLX_ARB_get_proc_address, GLX_ARB_multisample,
    GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
    GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
    GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
    GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
    GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
    GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
    GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) 945GM x86/MMX/SSE2 (0x27a2)
    Version: 11.2.0
    Accelerated: yes
    Video memory: 192MB
    Unified memory: yes
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 1.4
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 945GM x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 11.2.0
OpenGL extensions:
    GL_3DFX_texture_compression_FXT1, GL_AMD_shader_trinary_minmax,
    GL_ANGLE_texture_compression_dxt3, GL_ANGLE_..."
1654583,2017-01-08 10:40:35 UTC,"Hello, and welcome to Launchpad :)"
1654583,2017-01-08 10:02:30 UTC,"dakkus@ubuntu:~$ lspci -nnk | grep -i VGA -A6
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
 Subsystem: Fujitsu Limited. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [10cf:137a]
 Kernel driver in use: i915
 Kernel modules: i915, intelfb
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
 Subsystem: Fujitsu Limited. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [10cf:137a]
00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02)
dakkus@ubuntu:~$"
1654583,2017-01-08 09:59:30 UTC,"dakkus@ubuntu:~$ lspci -nnk | grep -i VGA -A2
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
 Subsystem: Fujitsu Limited. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [10cf:137a]
 Kernel driver in use: i915
dakkus@ubuntu:~$ glxinfo | grep 'OpenGL version string'
OpenGL version string: 1.4 Mesa 11.2.0
dakkus@ubuntu:~$"
1654583,2017-01-07 12:29:20 UTC,Could you please provide the used graphics card and driver?
1654583,2017-01-08 15:15:37 UTC,"For comparison i attache the output of glxinfo from my Laptop, also Intel driven graphics."
1654584,2017-01-15 06:07:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654584,2017-02-02 16:59:59 UTC,This bug was fixed in the package linux - 4.8.0-37.39
1654586,2017-01-31 09:48:51 UTC,"Reviewed:  https://review.openstack.org/420188
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=e8996d9fff90eacc7bc56fa0aa46b613249016a4
Submitter: Jenkins
Branch:    master"
1654586,2017-02-16 12:57:32 UTC,This issue was fixed in the openstack/tripleo-heat-templates 6.0.0.0rc1 release candidate.
1654586,2017-01-13 21:44:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420188"
1654586,2017-01-12 10:15:17 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/419394"
1654586,2017-01-11 16:19:54 UTC,"Reviewed:  https://review.openstack.org/417417
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=84285539087720e2c25efaed4569b9ff1c1190a7
Submitter: Jenkins
Branch:    master"
1654586,2017-01-06 15:26:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417417"
1654586,2017-01-12 15:12:30 UTC,"Change abandoned by Itzik Brown (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/419394"
1654588,2017-01-17 11:21:56 UTC,"This has not landed yet in edge, has it? I don't see if on my pi2 (which is an upgraded system, that may make a difference)."
1654593,2019-07-08 06:57:58 UTC,"This failure looks to have been fixed as I cannot make this test to fail
locally and under stress."
1654594,2017-01-09 02:31:46 UTC,"Sounds similar to general resizing bugs seen in Unity8. For example Unity8 composites this window incorrectly (renders it with nonsquare pixels) until you grab it and resize it manually:
  mir_demo_client_target -- --desktop_file_hint=unity8"
1654599,2017-06-16 01:01:19 UTC,Having same issue on Arch Linux via the AUR.
1654599,2017-09-19 18:44:21 UTC,"I am encountering the same bug on Antergos, using this package from the Arch repositories:"
1654599,2018-02-22 09:03:56 UTC,Having the same issue on Arch Linux
1654599,2018-02-22 18:09:02 UTC,"Eek, this was six months ago! Sorry about that. I'd like to fix this (and a bunch of other things here), but may take a little while, as my personal project Fridays are currently devoted to building some furniture :/"
1654599,2020-11-30 21:11:43 UTC,Closing this as it is rather stale (and hopefully fixed in the next release). Please report future bugs at https://gitlab.gnome.org/GNOME/gnome-break-timer/-/issues.
1654602,2017-02-02 16:59:00 UTC,This bug was fixed in the package linux - 4.4.0-62.83
1654602,2017-01-09 18:29:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654605,2017-01-07 17:03:58 UTC,Here is a test being executed on a reverse dependency of qtbase-opensource-src-gles https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-1985/zesty/ppc64el/k/kdepim-addons/20170105_202155_b62b2@/log.gz
1654605,2017-01-06 17:10:50 UTC,Thanks - can you link to the log for an incorrect run please?
1654606,2017-01-06 21:00:38 UTC,Might be worth to consider:
1654616,2017-03-10 14:52:59 UTC,"Reviewed:  https://review.openstack.org/441855
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=f7502923f271d1edfc5b6236478725124f66506c
Submitter: Jenkins
Branch:    master"
1654616,2017-03-14 15:49:38 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/445540"
1654616,2017-03-14 17:26:27 UTC,"this bug has been split in to with the remainder of the bug captured in
https://bugs.launchpad.net/os-vif/+bug/1672812"
1654616,2017-04-24 20:17:48 UTC,"Reviewed:  https://review.openstack.org/445540
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=619c5e920e63109ed551fe2304fe7c394aa62b85
Submitter: Jenkins
Branch:    stable/ocata"
1654616,2017-04-27 23:25:16 UTC,This issue was fixed in the openstack/os-vif 1.4.1 release.
1654616,2017-06-01 01:02:18 UTC,This issue was fixed in the openstack/os-vif 1.5.0 release.
1654618,2017-01-06 18:04:44 UTC,Wrote quick patch for the issue. This patch adds the missing library to the control file dependencies for the webcamoid package.
1654618,2017-01-06 18:06:19 UTC,"Oops, forgot to edit the description of the patch. Reuploaded."
1654618,2017-05-28 17:16:00 UTC,"Hi,"
1654624,2017-01-28 12:17:02 UTC,"> Which are the perceivable consequences of this bug?
"
1654624,2017-01-31 23:43:51 UTC,"Hadmut, AppArmor's stacking support was intended to allow supporting unmodified Ubuntu inside LXD containers. If you're feeling up for some experimentation, you could try to disable this feature by setting the kernel.unprivileged_userns_apparmor_policy sysctl to 0 early in a system boot, preferably before LXD starts. This should cause the attempts to set policy within LXDs to fail, and either the services will then refuse to start or they'll fall back to their old behaviour. (This reflects my lack of familiarity with LXD.)"
1654624,2017-01-28 12:09:02 UTC,"> Removing the LXD task, this is yet another apparmor bug from the apparmor stacking/namespacing change which was backported to Xenial.
"
1654624,2017-01-27 23:38:26 UTC,Which are the perceivable consequences of this bug?
1654624,2017-01-28 04:03:14 UTC,"Removing the LXD task, this is yet another apparmor bug from the apparmor stacking/namespacing change which was backported to Xenial."
1654624,2017-01-25 16:12:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654628,2018-02-27 14:54:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654628,2018-02-27 14:55:42 UTC,Same happens with Raspberry Pi2 and Ubuntu 16.04.3
1654629,2017-01-23 02:11:13 UTC,"Also note the ""null"" result that is returned. This seems like it should either be omitted or be {}."
1654629,2017-01-24 07:57:09 UTC,https://github.com/snapcore/snapd/pull/2690
1654629,2017-01-26 21:04:42 UTC,"I suggest fixing the documentation instead of adding a Location header. We already provide the necessary data in the response. If the argument is avoiding parsing the response, that's not a great idea as it'll mean errors will also not be reported properly."
1654631,2017-01-12 11:37:23 UTC,"I can't reproduce the issue with the latest master code and Puppet 4. Can you provide some details on your test enviroment (OS, Puppet versions)?"
1654642,2017-05-18 04:44:21 UTC,"And -j4 keeps four cores pegged solid.  Overhead seems low now.
debuild times went from 11-20 hours down to 2.5 hours for one package.
Happy happy joy joy!"
1654642,2017-05-17 21:43:10 UTC,:)
1654642,2017-05-17 19:31:48 UTC,"omg it is so much better now.  with the new classic, make -j3 keeps three cores pegged solid, as the good $deity intended."
1654642,2017-05-17 19:05:50 UTC,Tested with iirc
1654642,2017-05-17 10:13:54 UTC,this has been resolved with the latest classic snap in the edge channel ...
1654642,2017-05-16 18:41:50 UTC,What's the status on this?   I'm being bitten by the slow builds again.
1654642,2017-01-17 15:41:25 UTC,"@gustavo: the latter ... it is essentially about everything you install in --devmode ... (every apparmored command then causes one ""ALLOWED"" line in the log), the classic snap is worse in that regard since everything you do inside the chroot needs to go through apparmor (because it is a chroot command)"
1654642,2017-01-17 15:26:14 UTC,"Is this about _the_ classic snap, or arbitrary snaps in classic confinement mode?"
1654642,2017-01-11 09:13:57 UTC,Oh and of course
1654642,2017-01-11 09:13:20 UTC,"Hey Jamie, thanks for your suggestions! Using (3) seems like the best option, however we do not allow installing classic snaps on a Ubuntu Core system (all-snap) system. So I think the next best option is (1)."
1654642,2017-01-06 23:58:57 UTC,"that workaround seems to have helped, thanks."
1654642,2017-01-06 19:32:20 UTC,I'm not sure of the long term goals of the classic snap but there are several options on how to fix this for the current situation:
1654651,2017-01-16 08:02:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654654,2017-01-07 06:26:48 UTC,This is not a bug in UTT but rather unity and/or its API.
1654654,2017-01-07 06:26:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654662,2017-01-24 15:55:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654662,2017-01-25 14:17:20 UTC,My wifi adapter is TL-WN722N
1654662,2017-02-28 13:20:51 UTC,"I'm not a 100% sure if network-manager is the right package to file this to, but is certainly is not cloud-initramfs-tools. I hope this now is at least closer to where it belongs to."
1654662,2017-01-24 15:08:07 UTC,"I have got the same problem with wifi and also with usbmodem E3276S (Ubuntu 16.04, 64bit, H170N-WIFI-CF). When I start Ubuntu without overlayroot (tmpfs) there is no problem with wifi and usbmodem. Only standard eth-connections works ok in both cases."
1654668,2018-01-24 22:37:25 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-724
1654668,2017-01-12 14:37:24 UTC,Thanks for the fix. It is already merged in the 2.2 branch
1654668,2017-01-06 22:50:43 UTC,I created a fix for this issue https://github.com/percona/percona-toolkit/pull/159
1654673,2017-06-26 07:28:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477425"
1654673,2017-06-27 09:38:10 UTC,"Change abandoned by RocDove (<email address hidden>) on branch: master
Review: https://review.openstack.org/477425
Reason: only one ""logical change"" per commit.
I will commit twice."
1654673,2017-11-06 18:53:51 UTC,"Change abandoned by Samuel Matzek (<email address hidden>) on branch: master
Review: https://review.openstack.org/477856"
1654673,2017-12-28 07:24:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530310"
1654677,2017-01-06 23:04:41 UTC,The network resource was accessed using Nemo bookmarks for network resources (smb://<user>@<host>/<dir>/)
1654688,2017-06-16 14:58:12 UTC,"In my opinion, this is not a bug (and probably not a feature either) but the expected behavior."
1654688,2017-07-28 17:01:35 UTC,"xhienne, that's a good point. My workaround is to switch to Python 3, which treats multi-byte chars the same as single-byte chars."
1654696,2017-01-26 01:11:36 UTC,"Update regarding #2 and #3:
Apparently there can't be any extra whitespace between ""string"" and the first command.  For example, this doesn't work:"
1654696,2017-01-26 18:51:20 UTC,"More detail about #5:
The existing documentation about adding extra packages to the live cd pool is pretty out of date:
https://help.ubuntu.com/community/InstallCDCustomization#Modify_pool_structure_to_include_more_packages"
1654696,2017-03-01 00:02:45 UTC,Another issue/comment (probably would be resolved by #1):
1654696,2017-03-17 16:43:11 UTC,Another item:
1654696,2018-01-09 16:12:07 UTC,nvidia isn't the correct project for this.
1654696,2018-01-09 17:10:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654696,2020-08-05 17:09:36 UTC,Is this issue still being tracked?  I still have question #2 from the OP.
1654699,2017-01-30 14:35:45 UTC,I’m getting the same message as before:
1654699,2017-01-30 02:15:27 UTC,"The reason for the 404 is this (see picture) in the inkscape-web settings.
V explained that it needs to be set to 'Everyone with access' - but I still would like to know if that means others can also directly commit - even if it's labelled as 'visibility'."
1654699,2017-01-30 14:50:14 UTC,"Sylvain, that's not how you clone a repository. You need to use ssh, upload an ssh key and etc."
1654699,2017-01-30 15:15:58 UTC,"Well, yeah, I know… The HTTPS way is meant not to work?"
1654699,2017-01-30 01:28:12 UTC,This is a hard design issue. I'm willing to close this report as fixed committed and open others to talk about design issues further.
1654699,2017-01-31 13:50:16 UTC,It gives the same result.
1654699,2017-01-31 14:06:36 UTC,"OK let's get this bug report closed and we can talk on IRC about the css some more, I know there's a new guy looking at this issue too. Wants to make it all responsive."
1654699,2017-01-31 17:21:07 UTC,"(That 'new guy' being the Frédéric from comment #4, who, unfortunately, wasn't subscribed here)"
1654699,2017-02-05 13:56:52 UTC,"> It gives the same result.
"
1654699,2017-01-30 16:57:40 UTC,"I'm sure it's meant to work, but honestly, ssh is how you should be doing it."
1654699,2017-01-30 01:06:26 UTC,"> Oh, now it's there, please ignore.
"
1654699,2017-01-31 00:23:04 UTC,"Martin changed the setting. Can you try again, Sylvain?"
1654699,2017-01-29 18:53:36 UTC,"Oh, now it's there, please ignore."
1654699,2017-01-29 18:53:05 UTC,(despite having that selected in the settings...)
1654699,2017-01-29 18:52:06 UTC,"Interesting. I'm not getting any messages for inkscape-web from gitlab. I thought I only don't get any for the commits, but I also don't get any for merge requests."
1654699,2017-01-29 18:25:55 UTC,"Sorry — :). I actually followed the discussion (but not the one from yesterday). Thanks Maren.
So I made a merge request on GitLab."
1654699,2017-01-29 17:21:55 UTC,"Sylvain, probably you missed the whole discussion on the devel mailing list..."
1654699,2017-01-29 12:09:34 UTC,"Well, I don’t know why my patch wasn’t applied (I think I tested it and it works); and I managed to make Bazaar work again but I’m getting an error when trying to commit:"
1654699,2017-01-27 22:03:42 UTC,I have an MR coming to move the caption to the right.
1654699,2017-01-29 21:41:20 UTC,Merge request accepted.
1654699,2017-01-07 23:20:05 UTC,The patch command doesn’t work?
1654699,2017-01-07 05:19:25 UTC,"Could you make a couple of screenshots? I found it hard to apply your patch and I'm not sure if I did it right, it didn't seem to do anything."
1654699,2017-01-07 02:17:39 UTC,"Unfortunately, I’m not currently able to commit myself (because Bazaar crashes on my system), so here is a patch for the things that can be fixed in CSS: captions on the right, pictures centered (for narrow view).
Thank you for committing."
1654703,2018-02-25 17:59:37 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1654703,2017-05-21 09:27:01 UTC,This looks like it is caused by the Ubuntu specific changes to dh_installchangelogs.
1654703,2018-02-25 18:22:34 UTC,"The bug is still present in 17.10, with fig2dev 1:3.2.6a-3.  Should this
bug report be updated and reopened, or should I create a new one?"
1654703,2017-01-07 10:41:50 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1654703,2018-02-26 17:31:27 UTC,"Thanks for checking back, Nate. I've reopened this, and tagget artful as well."
1654703,2017-01-07 12:06:49 UTC,"I looked a bit more into this issue and planned to forward the issue to Debian, but I discovered that the symlink is only broken in Ubuntu. Comparing the filelist for the package in Debian Sid [1] and Ubuntu Zesty [2], we can see that /usr/share/doc/fig2dev/changelog.gz is included on the Debian side, but is not present when the package is rebuilt on Ubuntu."
1654703,2018-02-26 17:41:00 UTC,I can confirm that the issue is also present in fig2dev 1:3.2.6a-6ubuntu1 on Ubuntu bionic.
1654717,2017-01-24 09:26:44 UTC,Failed on 10.0 community bvt:
1654717,2017-01-25 08:40:41 UTC,Another failure on 11.0 bvt:
1654717,2017-01-25 08:40:52 UTC,https://ci.fuel-infra.org/job/11.0-community.main.ubuntu.bvt_2/366/console
1654720,2017-01-07 13:01:38 UTC,"Attaching test case from external link to bug report (based on past experience, external links tend to disappear over time)."
1654720,2017-01-08 00:10:02 UTC,Appears that the document originated in Illustrator. AI use of masks on images with transparency might be problematic when repurposed in Inkscape and output to PDF.
1654730,2017-09-28 23:56:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654730,2017-03-09 11:09:10 UTC,This is probably due to a hardware bug.
1654733,2017-12-07 13:45:54 UTC,possibly https://bugzilla.gnome.org/show_bug.cgi?id=779723
1654733,2020-12-19 09:04:52 UTC,"seems still to be present under ubuntu 20.04.1 LTS/ Rhythmbox 3.4.4; (don't know yet which encoder is used, seems to be an issue of the encoder. Encoding in actual version produces correct encoding but wrong content of meta information about bitrate)"
1654733,2021-02-03 04:56:13 UTC,Seems to work fine here. Encoded a wav to mp3-vbr (quality=0.0)
1654738,2017-01-07 12:42:58 UTC,"This is a bug for the ""launchpad itself"" project, not an inkscape bug"
1654749,2017-07-08 12:32:26 UTC,Deleting the attached diffs - I am revoking my pending patches provided in this bug tracker for issues with python-based extensions distributed with Inkscape.
1654749,2017-05-29 06:03:25 UTC,Minor correction of v2.
1654749,2017-01-09 10:58:09 UTC,"Reproduced on Windows XP (32-bit), lp:inkscape/0.92.x rev. 15309."
1654749,2017-01-08 23:34:44 UTC,Ok the workaround works very well ! Thanks a lot and sorry for my misunderstanding.
1654749,2017-01-08 19:00:55 UTC,"@ivan - a quick workaround in any affected file is to
1) add a new layer
2) move the path to the new layer
3) apply the extension"
1654749,2017-01-09 11:04:00 UTC,"Patch tested quickly with the SVG file attached comment #1. Looks perfect, but needs some more tests."
1654749,2017-01-08 18:51:35 UTC,My question was also why the center of mass location is so far outside the object and far from the potential center of gravity of the shape (assuming it has an homogenous weight everywhere on its surface).
1654749,2017-01-07 17:23:44 UTC,"Updated proposal, includes fixes for text labels inserted at path start or center of mass, if selected path is inside transformed (translated) group or layer."
1654749,2017-01-07 16:58:02 UTC,Attaching proposal to fix insertion of 'center of mass' symbol in transformed layers - please review.
1654749,2017-01-07 17:09:29 UTC,Needs fixes for other use cases of center of mass too (to position text labels for length and area) - updated patch later.
1654749,2017-01-07 16:58:53 UTC,Reproduced with Inkscape 0.91 r13725 and lp:inkscape/0.92.x r15309 on OS X 10.7.5.
1654749,2017-01-08 18:57:26 UTC,ivan - the answer to the question «why the center of mass location is so far outside the object» is that the extension currently does not correctly take the translate() transformation of the parent layer group into account when drawing the path to symbolize the center of mass:
1654753,2019-02-05 20:33:07 UTC,moved from https://bugs.launchpad.net/yade/+bug/1654753 to https://gitlab.com/yade-dev/trunk/issues/32
1654761,2018-03-09 08:34:05 UTC,"On Thu, Mar 08, 2018 at 06:16:27PM -0000, Simon Quigley wrote:

> However, what also needs to be figured out is a stable way to access the
> queue items (read only is all that's needed) from Britney. This is
> because Britney sends the test directly to AMQP rather than going
> through request.cgi. So once duplicate tests can't be triggered (i.e.
> the above bug is fixed), it would certainly be confusing if these things
> show up in excuses but triggering them doesn't work (or even worse, they
> show as passed). You mentioned grabbing the data from queues.json, what
> about this isn't ideal, and what can be improved? (Because that's likely
> the way to go here.)
"
1654761,2018-03-08 20:15:17 UTC,I've gone ahead and made bug 1686929 a duplicate of this one so we can track it here. I've also edited the description.
1654761,2018-03-08 18:16:27 UTC,"That seems to solve part of the problem but not exactly all of it. So after implementing the fix for bug 1686929 (two birds with one stone here), when someone manually triggers a test, request.cgi won't let duplicate tests be queued. That should be relatively simple to implement from how you described it."
1654761,2018-03-18 01:13:58 UTC,"Alright, so I guess we can count Britney as not affected by this then. :)"
1654761,2018-03-08 14:06:17 UTC,proposed-migration can't check directly if things are in the queue. AMQP allows you only to insert something into the queue and remove it again.
1654761,2018-03-08 04:59:01 UTC,"So here's some general notes and some questions that I have gathered regarding the implementation of this. Please note that this is my first time working with the Britney2 or autopkgtest-cloud code, so I might be somewhat off on some specifics, so please do correct me if I'm inaccurate anywhere here."
1654761,2018-03-02 20:38:50 UTC,This actually isn't an issue with the autopkgtest infra on first glance; the bulk of work will need to be done in britney2's autopkgtest policy.
1654761,2018-03-08 14:28:36 UTC,proposed-migration can't check directly if things are in the queue. AMQP allows you only to insert something into the queue and remove it again.
1654768,2017-01-08 10:10:08 UTC,"I think the real issue here is the bug I filed - the build/ directory is
empty."
1654769,2017-01-07 18:30:13 UTC,This change was made by a bot.
1654769,2017-01-09 20:55:37 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1654769,2017-01-18 09:26:07 UTC,"Hello, I have tested the latest mainline kernel v4.10-rc3 and the bug has been solved."
1654769,2017-01-18 12:29:45 UTC,"Sorry , I made a mistake the airplane function key now works, that has been fixed in the mainline kernel 4.10-rc3 BUT THE LED STILL WORKS BACKWARDS, THAT HAS NOT BEEN FIXED IN THE KERNEL 4.10-RC3"
1654770,2017-01-07 20:29:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1654770,2017-01-07 20:41:11 UTC,"I choose udev package even if the bug is when I use nautilus.
For example, lsub is freezing too when I plug the watch."
1654770,2017-01-09 09:53:21 UTC,Extract from /var/log/kern.log
1654773,2020-05-11 17:29:50 UTC,"Okay, let's close this then."
1654773,2020-05-10 17:10:51 UTC,"Yeah, I think quantizing seeks from mouse clicks on the waveform would be reasonable."
1654773,2020-05-10 17:14:47 UTC,"Oh wait, Mixxx already does that when quantize is on."
1654773,2020-05-10 16:58:12 UTC,Thanks for the heads up.
1654773,2020-05-11 17:08:24 UTC,"OK, I just had a look at 2.3 and I think it's already very usable for me. Downbeat marking in the waveform would then be another very useful addition."
1654773,2020-05-10 15:40:56 UTC,"I got a bit more time again and would like to have another go, hence trying to assign the entry to myself."
1654773,2018-09-21 06:47:49 UTC,"I had worked on this one and a half years ago and came up with a demo including the hotkeys mentioned above (see screenshot attached), but my math for the jumps was off. Then RL got in the way and I never got round to giving it another look."
1654773,2017-07-09 15:29:52 UTC,"> I'm not sure what to do if something isn't 4/4 time.
"
1654773,2017-07-09 15:16:46 UTC,"I had a brief look at this. I think I may be able to do it myself (time permitting). But the question is, would such a feature be adopted?"
1654773,2020-05-10 16:07:55 UTC,"Doing anything with bars is premature until Mixxx has this information available. Fortunately we have two Google Summer of Code students working on that this summer. If you want to participate, take a look at:
https://github.com/mixxxdj/mixxx/pull/2512
https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/support.20for.20bar.20and.20phrase.20info.20and.20variable.20BPM
https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/beatgrid.20editing.20UI
https://mixxx.zulipchat.com/#narrow/stream/109122-general/topic/What.20is.20a.20phrase.20in.20music.3F"
1654774,2017-01-07 19:01:02 UTC,This change was made by a bot.
1654774,2017-01-09 20:54:41 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1654774,2017-01-12 10:07:19 UTC,"Hello Joseph Salisbury, I cannot test another kernel in my ssd install because I'm currently using a module that solves a bluetooth bug which works only with my current kernel, as you can see from here:"
1654774,2017-01-18 09:19:23 UTC,"Hello , I have tried the latest mainline kernel v4.10-rc3 and the bug is still there, the battery information is still displayed incorrectly."
1654774,2017-01-18 09:24:59 UTC,tag added 'kernel-bug-exists-upstream'
1654777,2017-08-04 02:45:59 UTC,This version is configurable via /etc/default/zram-config
1654777,2017-08-04 02:56:01 UTC,"There was a discussion about making better swap size guidelines at the Athens sprint in June 2016, I summarized the results at https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1566129/comments/3 and some additional questions were raised in https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1566129/comments/4"
1654777,2017-08-04 04:29:34 UTC,"That still talks about on-disk swap.  This doesn't create a swap file or swap partition; it creates a swap area in RAM.  In general, there is no reason to have any sort of swap area on disk, save for scientific applications where you have 100 times as much working set as you have physical RAM."
1654777,2017-08-28 09:57:59 UTC,I've found improved version of zram-config at lp:~eugenesan/+junk/zram-config with following improvements:
1654777,2017-08-28 10:01:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654780,2020-05-01 20:08:43 UTC,"Hi,"
1654780,2017-03-19 22:10:34 UTC,Here is the file.
1654780,2017-03-19 09:07:19 UTC,and here is the english translation
1654780,2020-04-29 13:39:59 UTC,"As you may noticed i have moved development of LASK from Launchpad to Codeberg.org.
I've also made a Android App LASKmobile.
It would be great if you can make a actual translation for the next version 0.8."
1654780,2017-03-12 15:00:36 UTC,"Hi,"
1654780,2017-03-12 14:12:34 UTC,"Hi fri,
i've made a new version of lask.
it would be great if you update your lask_cs.po so i can publish it with the next release."
1654780,2017-01-18 18:11:58 UTC,Thank you very much.
1654780,2017-03-19 09:06:11 UTC,Sorry i pushed a translation file without the new lask.ui
1654795,2017-01-07 23:23:06 UTC,"I don't have a minimal, reduced case to reproduce it. But here's how to reproduce it using Botan:"
1654795,2017-01-09 04:03:17 UTC,This may be useful. Someone else reported things were OK on Ubuntu 16.10. I exeprienced the issue under 16.10.1.
1654796,2017-01-10 16:42:45 UTC,Not reproduced with Inkscape 0.92+devel r15407 (default prefs) on Ubuntu 14.04 with 'Scale test - all'.
1654796,2017-01-12 09:44:49 UTC,"Also reproduced on Xubuntu 16.04, lp:inkscape/0.92.x rev. 15315."
1654804,2017-01-08 04:39:57 UTC,"also:
The text:
""use the command dpkg --info foo_VVV-RRR_AAA.deb (where VVV, RRR and AAA are the version, revision and architecture of the package in question, respectively). This displays, among other things, the package name corresponding to the archive file being unpacked."""
1654808,2017-01-09 22:55:13 UTC,ok!
1654808,2017-02-04 22:38:52 UTC,trunk
1654808,2017-02-04 22:38:44 UTC,fixed in r.15474
1654808,2017-01-09 22:20:56 UTC,@Jabiertxof: I would propose 0.93 (new feature).
1654808,2017-01-09 22:17:34 UTC,@su_v: whath milestone 0.93 or 0.92.1? 0.92.1 is on feature freeze.
1654808,2017-01-09 22:16:31 UTC,Sure. I hope can do this week.
1654808,2017-01-08 14:40:35 UTC,"One could imagine that the path effect 'Fill between strokes' could be extended with an additional option in the dialog to connect the other two end nodes as well to allow a continuous stroke around the fill (the fill is the topic of the effect, per its name), if this is considered a useful enhancement for the effect (both added connecting segments would be straight lines)."
1654808,2017-01-08 12:28:53 UTC,"Ah. OK. Thank you for checking into this, and sorry for reporting a nonbug.
This is actually a useful feature because now both behaviours are available: a stroke at one end with 'Fill between strokes', or strokes at both ends with 'Fill between many'."
1654808,2017-01-08 11:51:12 UTC,IIRC this is how the effect was designed - it connects the end node of one path with the start node of the second path. It does not aim to produce a filled shape with a fully closed stroke around it.
1654808,2017-01-08 03:57:55 UTC,"Since I could only attach a single file to my bug report, here is a PNG file exported from my previous SVG attachment, illustrating the behaviour that I observe."
1654812,2020-07-31 15:19:17 UTC,Closing as part of migration of issues to gitlab. You've opened the issue in https://gitlab.com/inkscape/inkscape/-/issues/760. :wave:
1654812,2017-05-01 09:05:11 UTC,Font size calculation has indeed some problems in 0.92.1. What could be root cause?
1654812,2017-01-12 10:25:24 UTC,"So the issue is not necessary in the widget itself, but could also stem from the font size calculation."
1654812,2017-01-08 12:28:40 UTC,"Based on tests with archived builds (on OS X 10.7.5):
- not reproduced with Inkscape 0.91 r13725,
- not reproduced with lp:inkscape rev <= 13638,
- reproduced with lp:inkscape rev >= 13646,
the issue was likely exposed with the merge of the experimental branch into trunk in r13641 (the stable release branch for 0.91.x had been forked much earlier and is not affected):
https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/changes/13646"
1654812,2017-01-12 10:00:40 UTC,"Also reproduced on Xubuntu 16.04, lp:inkscape/0.92.x rev. 15315."
1654812,2017-01-08 16:42:28 UTC,"Thank you for taking a look at this, su_v!"
1654812,2017-01-12 10:24:07 UTC,"With 0.91, when selecting a value in the font size widget, the widget always shows exactly the selected value.
Now with 0.92, Inkscape tends to show a value with decimals, which prevent the scroll wheel from working.
On my Xubuntu 16.04 computer, the widget only shows rounded values if you select a very big size (72 or 144), and in that case, the scroll wheel works as expected (until you reach 64...)."
1654820,2017-01-08 11:51:14 UTC,"For testing purposes, I uploaded a build of qtbase to our CI with amd64 added to nogoldlinker_architectures option."
1654820,2017-01-09 08:57:37 UTC,"I didn't see this on any of Ubuntu Touch reverse dependencies, but it seems it happens."
1654820,2017-01-15 09:16:34 UTC,This bug was fixed in the package qtbase-opensource-src - 5.7.1+dfsg-2ubuntu1~8
1654826,2021-01-08 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1654826,2020-11-08 09:06:16 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1654826,2017-01-10 07:34:27 UTC,"I have tried without ""repeat=on"" option, and with 2.8.0 I still seem to be getting weird behavior with mouse dropping out at points, and with keys seemingly being continued to be pressed (ie still running around in an fps game after releasing the key). I also experienced at one point l-ctrl+r-ctrl not passing keyboard control to guest, and needed to VNC in to shutdown/restart guest (this was after plugging in a usb xbox360 controller, not sure if related)."
1654826,2017-01-09 07:42:46 UTC,"quick workaround: drop ""repeat=on"".
some guests seem to have problems with that, not debugged yet why."
1654826,2017-01-08 10:01:51 UTC,Thought I might add:
1654826,2017-04-29 00:31:58 UTC,I am getting the same issue where I can even hear the sound glitch out. I'm on Arch Linux.
1654828,2017-01-08 12:13:44 UTC,"There is a related proposal in comment 2 of
* Bug #1422926 “Type units should be accessible from the text tool options”
  https://bugs.launchpad.net/inkscape/+bug/1422926
written after discussions with Gez on irc about the (costly) problems he experienced with the current state of keeping the font-size units as global preference hidden in a sub-section of the preferences dialog."
1654828,2019-02-10 21:00:17 UTC,"@Edward J (edwardj) I know this post is from a bit ago, but I had a similar request, & in speaking with Moini over in the forum she suggested I post to their brand new bug tracker here: (https://gitlab.com/inkscape/inbox/issues/)"
1654832,2017-05-06 15:09:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654856,2017-01-09 08:15:34 UTC,"on a second look, a possible solution for the problem of ""not being able to close the File Browser window"" might be to simply add a ""close"" option to the currently existing pull down window."
1654864,2017-01-08 19:56:21 UTC,This builds.  I haven't tested if it works--I don't have the environment for it--but it builds.  Corrects an out-of-date data format in compositor-rdp.c to make it build correctly.
1654864,2017-01-08 20:32:41 UTC,"The attachment ""[EXPERIMENTAL] A patch for weston 1.12.0-1"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1654864,2017-01-08 22:55:57 UTC,"The thing said to make a debdiff, so I figured out how to do that in the last 5 hours or so."
1654864,2017-01-23 04:48:30 UTC,Fixed in the latest ubuntu upload (via automatic sync from Debian).
1654864,2017-05-17 12:19:49 UTC,"Pardon my ignorance but how does one obtain the ""weston-rdp-compositor"" package?"
1654864,2019-02-27 10:00:40 UTC,This is not fixed!
1654864,2020-01-07 16:20:12 UTC,The Debian update has been reverted because freerdp2 isn't in testing and doesn't build everywhere.
1654875,2017-01-12 09:00:23 UTC,"Update: This seems to be triggered by a fractional (> 1, but < 2, 1.4 in my case) Displays -> Scale -> Scale Factor setting (which is meant for HiDPI displays, and probably for people with sight issues), not ""Force fonts DPI""."
1654875,2017-09-19 22:05:00 UTC,"A possible workaround is to create a sddm.conf (with sddm --example-config > /etc/sddm.conf) and add ""-dpi 144"" to ServerArguments. Then set Scale to 1 in System Settings and reboot."
1654875,2017-01-08 18:14:02 UTC,How I created the screenshot: Create text file with sufficient number of lines; open with vim; move cursor down until I'm at the terminal's last line and beyond; move back up until cursor is about in the vertical middle of the terminal.
1654875,2017-01-08 18:21:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1654875,2017-01-08 18:11:39 UTC,"Also reproducible with the ""Hack"" font instead of ""Oxygen Mono"", and/or disabling the fonts setting ""Force fonts DPI""."
1654875,2017-01-11 00:31:23 UTC,"... did I mention this bug makes Konsole unusable for anything like programming or text editing?  This is so annoying I really wonder why something like this can make into an Ubuntu release, actually."
1654877,2017-01-08 18:10:26 UTC,See screenshot.
1654877,2017-01-08 18:16:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417703"
1654877,2017-01-16 14:47:31 UTC,"Change abandoned by Felipe Monteiro (<email address hidden>) on branch: master
Review: https://review.openstack.org/417703
Reason: This is a MySQL-specific issue for older versions."
1654880,2017-01-09 09:51:25 UTC,"Reproduced on Windows XP, lp:inkscape/0.92.x rev. 15309."
1654880,2017-01-10 16:43:38 UTC,Reproduced (not fixed) with Inkscape 0.92+devel r15407 (default prefs) on Ubuntu 14.04 with 'Scale test - all'.
1654899,2017-01-10 03:55:35 UTC,"This is not yet working on the snapd side, so we shouldn't document it yet. But thanks for the bug report, we'll document it as soon as it works end-to-end."
1654899,2017-01-16 16:47:05 UTC,Does 2.21 do the trick?
1654899,2017-01-17 15:10:25 UTC,"Yes it does, I am a little confused by the experience though"
1654899,2017-01-17 15:31:54 UTC,This is being fixed. It should say something like:
1654899,2017-05-10 22:19:51 UTC,This follow up should be a new bug since the purpose of the original bug report has been fixed.
1654902,2017-11-28 17:50:31 UTC,Yes @maren. Put it as fix commited.
1654902,2017-11-28 13:18:01 UTC,@jabiertxof: Isn't this Fix commited now?
1654902,2017-01-09 09:27:59 UTC,"Reproduced on Xubuntu 16.04 and Windows XP (32-bit) with Inkscape 0.91 and 0.92, with the default symbols. Not only the symbols are not ordered correctly, but they are (un)ordered differently in Windows and Xubuntu."
1654902,2017-01-09 21:30:28 UTC,Related: see also https://bugs.launchpad.net/inkscape/+bug/1620610 when implementing filtering as discussed in https://github.com/Xaviju/inkscape-open-symbols/issues/39
1654902,2017-01-09 01:51:53 UTC,"<off-topic cont.>
Actually, due to bug #1653184, I better not recommend this for users of Inkscape 0.92 r15299 (the latest stable release) - there are way too many (other, known) warnings at the moment due to that regression (they are gone with latest lp:inkscape 0.92.x luckily (and will be fixed in 0.92.1)).
</off-topic>"
1654902,2017-01-09 01:45:46 UTC,"Not fully reproduced with Inkscape 0.91, 0.92.0 and lp:inkscape/0.92.x r15309 on OS X 10.7.5 (see attached screenshot)."
1654902,2017-01-09 02:38:00 UTC,"Thank you, V, I'm forwarding your 'bug report' to Xaviju's repo! (Should be easy to fix)"
1654903,2017-01-09 00:22:44 UTC,In hindsight this is likely a duplicate of bug #1653236 (same underlying issue: the chained clones offset from the original described there also link to an original (another clone) with a preserved transform attribute).
1654903,2017-01-09 11:37:37 UTC,Reverting duplicate status for now.
1654903,2017-01-10 16:43:52 UTC,Not reproduced with Inkscape 0.92+devel r15407 (default prefs) on Ubuntu 14.04 with 'Scale test - all'.
1654903,2017-01-12 09:38:56 UTC,"Reproduced on Xubuntu 16.04, lp:inkscape/0.92.x rev. 15315."
1654904,2017-01-09 00:18:15 UTC,Attached to this comment is the actual SVG file. It's not the original file from a few years ago because I removed some irrelevant stuff. I opened this file in Inkscape 0.48 under Linux in VirtualBox on my Windows machine and it looks OK except that the Chinese characters don't show up at all because I don't have the fonts installed under Linux. I don't have an older Inkscape under Windows now because I had to remove it to install 0.92.)
1654904,2017-01-09 00:56:03 UTC,Note: the font 'DFKai-SB' is no longer included with latest Windows 10 (see 'Products that supply this font' at https://www.microsoft.com/typography/fonts/font.aspx?FMID=1584 ).
1654904,2017-01-09 01:21:33 UTC,"<off-topic label=""Likely unrelated info"">
Freetype has a list of ""tricky fonts"" which also includes 'DFKai-SB':
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/src/truetype/ttobjs.c#n142
https://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html#FT_FACE_FLAG_TRICKY
</off-topic>"
1654904,2017-01-09 01:33:19 UTC,"That's interesting about the tricky fonts. I wonder if turning off hinting would affect this case. I noticed that MingLiU and PMingLiU are in the tricky list but they both look fine in my test file.
It's also interesting that you saw the problem with Inkscape
My DFKai-SB font is also version 5.00."
1654904,2017-01-09 01:39:49 UTC,"Oops. I pressed 'Post Comment' too soon.
I meant to say that it's also interesting that you saw the problem with Inkscape 0.47. The original file that I saw the problem in is dated 2012 Jan 15, and at that time the file looked fine, with whatever version of Inkscape I was using. Looking at my download directory, I think it was probably 0.48.0."
1654904,2017-01-09 02:17:28 UTC,"I just confirmed that, after copying some of the fonts from Windows into Linux under VirtualBox, I see the problem in Inkscape 0.48.3.1 r9886 under Linux.
By the way, I found instructions at https://answers.microsoft.com/en-us/windows/forum/windows_10-start/some-fonts-are-missing-after-upgrade/95839dfa-0df2-4bc0-875a-fd6b57e61fe4 for installing DFKai-SB and many other fonts that are 'optional features' in Windows 10."
1654907,2017-01-17 17:58:46 UTC,"@Pelle - the extension 'Visualize > Measure' AFAICT is one of the bundled extensions which does support arbitrary document scale:
https://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/15320/share/extensions/measure.py#L214
measure.py does not rely on methods from inkex.py to determine the document scale stored in the 'factor' variable (page dimension / viewBox dimension) - not an ideal solution either, IMvHO. Personally, I still think that the unit conversion methods provided for the Effect() class in inkex.py should support arbitrary document scales, even if I retracted my originally proposed implementation (the issue is not solved)."
1654907,2017-01-17 15:38:35 UTC,Thanks! So it has been known for over a year and I need to learn to search better.
1654907,2017-01-17 14:45:39 UTC,"@Pelle - re «extensions handling user-units and query-all in 0.92», this is probably bug #1508400, now tracked in bug #1525418."
1654907,2017-01-09 08:55:58 UTC,I was the one that had problems with extensions not working properly in 0.92. I asked a Question here on launchpad a few days ago also asking for some clarification on how an extension is expected to properly parse and generate SVG to work properly with user-units for different versions of Inkscape used to create the document or run the extension.
1654907,2017-01-09 12:42:49 UTC,"Pelle, I've subscribed you to this report (this doesn't happen automatically). I hope that was okay :)"
1654908,2017-01-09 02:09:22 UTC,This issue is currently tracked in MacPorts (it seems to only affects macOS 10.12 Sierra):
1654908,2017-01-09 03:04:10 UTC,"Thank you for the information su_v, hopefully we see a fix soon!"
1654908,2017-01-09 03:08:36 UTC,"Changing bug status to 'Confirmed' based on earlier user report on the 'inkscape-devel' mailing-list:
http://inkscape.13.x6.nabble.com/Inkscape-0-92-crashes-on-macOS-Sierra-10-12-2-tt4978382.html#none"
1654908,2017-01-24 18:31:50 UTC,This happens for me on the non-Quartz install as well.
1654908,2017-01-25 01:47:44 UTC,"A suggested workaround in https://trac.macports.org/ticket/53270 is to run ""LANG=en_GB inkscape"""
1654908,2017-02-01 21:42:52 UTC,Had exactly the same experience on OSX 10.12.3 for Inkscape .92 trying both quartz and X11 versions. Example error output in screenshot and pasted here:
1654908,2017-02-12 10:26:26 UTC,Guess I have the same bug https://bugs.launchpad.net/inkscape/+bug/1663977
1654908,2017-02-19 05:47:51 UTC,I built version 0.92.1 with Mavericks ( Xcode 6.1.1 / App bundle  ).
1654908,2017-02-20 09:10:24 UTC,"Same problem, recompiled multiple times with varying port variants, but no success on Sierra."
1654908,2020-08-04 11:40:45 UTC,Fixed with native macOS for Inkscape 1.0.
1654923,2017-11-03 16:29:46 UTC,Syncing task from Mir.
1654929,2019-09-19 14:53:02 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1654939,2018-04-07 10:42:02 UTC,no idea why this is an issue in python3.
1654939,2018-04-07 10:40:43 UTC,idle built from Python2 is gone
1654943,2017-01-09 07:19:12 UTC,"One 'quick fix' is to pass '--connect-timeout X' to specify a number of seconds that curl should wait to connect to download agent binaries. Certainly if we are connecting to the controller in the same network, we would expect it to be quite fast. We may not want to set it for the initial tool download from streams.canonical.com but we should be able to set something much lower than the default (which I think is ~2minutes) for connecting to the controller machine."
1654943,2017-02-14 08:51:47 UTC,"I've made the --connect-timeout change to fix lp:1622531. Will leave this one open for the complete fix, i.e. using knowledge of spaces."
1654943,2017-02-14 10:59:21 UTC,"Andrew, John"
1654945,2017-07-11 10:30:34 UTC,"> and want to increase b1-vol size, Heat need to stop VM, update block volume and then start VM again, but this don't work.
"
1654945,2017-01-12 04:25:32 UTC,So the bdm can also the boot volume. So not sure if we've an easy way to remove it from the existing server. This is not going to be easy.
1654945,2017-07-11 08:33:59 UTC,"Hi, just updating this issue. In the current implementation, there are no ways to change (increase) boot volume size, since it can't be detached from VM because VM is working."
1654945,2017-01-09 08:20:31 UTC,"I think block_device_mapping_v2 property is not update_allowed. Therefore when you change them to add a additional device mapping, it would replace the server. Existing server is deleted only after the new one is created. Thefore the 'in-use' (HTTP 400) error. We could handle it better though by detaching first and reattaching to old server in case of rollback."
1654945,2017-01-09 12:54:15 UTC,"Hi Rabi,"
1654947,2017-01-10 05:03:56 UTC,"More info: I ran nemo from the command line. When it crashed it printed this:
$ nemo
Nemo-Share-Message: Called ""net usershare info"" but it failed: 'net usershare' returned error 255: mkdir failed on directory /var/run/samba/msg.lock: Permission denied
net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing."
1654947,2017-01-10 06:07:08 UTC,"Another iteration of the same problem. Interestingly these errors were reported by the nemo window I was copying to, not the one where I ejected the SD card."
1654949,2017-01-11 14:51:09 UTC,For reference: https://www.hpe.com/h20195/v2/GetPDF.aspx/4AA5-1930ENW.pdf
1654949,2017-01-13 07:35:55 UTC,"I'm afraid it's not a bug. The following paragraph is mentioned in the HPE white paper ""OpenStack HPE 3PAR StoreServ Block Storage Driver Configuration Best Practices"", too."
1654949,2017-01-13 07:43:22 UTC,Another paragraph:
1654949,2017-01-13 10:36:19 UTC,"Nevertheless, the user configured in cinder.conf needs not only the edit role, but must also have a
domain setting of ""all"". As documented in HPE's white paper: ""The drivers username credentials can have an “edit” role and domain set to “all”, the drivers no longer require a “super” role."""
1654949,2017-05-07 15:51:14 UTC,"It should be fixed in the cinder.conf locate in Cinder project first, then we can fix it in openstack-manuals."
1654950,2017-02-27 16:24:46 UTC,This issue was fixed in the openstack/fuel-web 11.0.0.0rc1 release candidate.
1654950,2017-01-26 07:21:14 UTC,Verified on 9.2 snapshot #801.
1654950,2017-01-13 14:44:45 UTC,"Reviewed:  https://review.openstack.org/418907
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=0257e80dfbbcabb32a5778209508d7bf063feedf
Submitter: Jenkins
Branch:    stable/mitaka"
1654950,2017-01-13 13:58:31 UTC,"Reviewed:  https://review.openstack.org/419431
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=68778a404b40c4965441ffd7d5407d84461ea67e
Submitter: Jenkins
Branch:    master"
1654950,2017-01-11 12:17:50 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/418891"
1654950,2017-01-12 11:43:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/419431"
1654950,2017-01-11 12:39:11 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/418907"
1654950,2017-01-11 12:13:30 UTC,"Reviewed:  https://review.openstack.org/417862
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=df106ebc51ab9379e2a3143bbaa459bc63ed0556
Submitter: Jenkins
Branch:    master"
1654950,2017-01-13 13:58:09 UTC,"Reviewed:  https://review.openstack.org/418891
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=af9fcf3ca29c7c07e4d23e08d2100a3ab79d528b
Submitter: Jenkins
Branch:    stable/newton"
1654960,2017-01-21 18:37:54 UTC,The problem with your fix is that rpc.py is also impact other mechanism drivers such as ovs and linuxbridge. I think it won't be accept in the community.
1654960,2017-01-23 06:31:06 UTC,"In my opinion this is not a bug, but you can send a mail in the openstack development mail list about this issue and suggestion on how to fix it."
1654960,2017-01-23 05:58:08 UTC,"Moshe, I'll be glad to see a better solution from other guys :)"
1654960,2017-01-21 15:36:40 UTC,"Well, we built clouds based on Juno release for customers years ago, some one use Mellanox NICs and some one use Intel NICs, and now the customers want to upgrade their clouds to Mitaka release. The key point is the customers have their own orchestration layer above OpenStack, and they do not want to do any API changes for the upgration, compatibility is the basic requirement for a commercial system."
1654960,2017-01-12 06:56:00 UTC,Thanks Moshe for your response.
1654960,2017-01-11 09:09:54 UTC,"port security extension allow you enable/disable  MAC-anti-spoofing check
see http://specs.openstack.org/openstack/neutron-specs/specs/kilo/ml2-ovs-portsecurity.html.
if the extension is not loaded the default is port_security_enabled=True
This is true to all mechanism drivers. see https://github.com/openstack/neutron/blob/9e5a70c47cbed49108c3d7e1cf72530e483cadb9/neutron/plugins/ml2/rpc.py#L126
The reason that it work for you in Liberty or before is because you didn't use the SR-IOV agent to enforce it/or the feature wasn't implemented for SR-IOV.
What you need to do is to change you network/port to port_security_enabled=False and than the agent will disable the MAC-anti-spoofing
looking on the neutron rest api it can be changed for network/ports
https://github.com/openstack/neutron/blob/97af09672735fb9d2742e23f3a6e94331d92e3cc/neutron/extensions/portsecurity.py#L36-L52"
1654960,2017-01-10 20:24:01 UTC,"Since I'm not up to speed on the SRIOV details, I asked Moshe Levi to help triage this one. Expect an update in the next day or few."
1654960,2017-01-21 09:53:01 UTC,"It a problem because the neutron server sends by default port_security=True
so it expect to set it to all VM. Not enabling the port security was a bug in the first place.
see https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/rpc.py#L126."
1654964,2017-01-09 08:46:18 UTC,"1. snap foo is released rev 2 for beta channel, if there are rev 1 and 2.
2. press ""unpublish"" button in the store UI, snap foo would be unpublish.
3. If we want to publish foo again, we can find release button for foo rev 1 or 2.
4. press release for rev 2, there is a dialog to ask which channels for release. If we just selected beta. The snap state is still ""Ready to publish""."
1654964,2017-01-09 09:14:20 UTC,"In clickapp_forms.py, ReleaseUploadForm."
1654964,2017-01-09 12:20:35 UTC,"#1, #2 should be commented on https://bugs.launchpad.net/software-center-agent/+bug/1654961 not this one."
1654967,2017-01-11 13:42:08 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/418937"
1654967,2017-01-12 09:26:30 UTC,"New failures on 9.2 snapshot #748:
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.env_customizations_check/104/testReport/(root)/customizations_check_env/customizations_check_env/
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.bvt_ubuntu_bootstrap/172/testReport/(root)/reset_on_ready_ubuntu_bootstrap/reset_on_ready_ubuntu_bootstrap/
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.bvt_ubuntu_bootstrap/172/testReport/(root)/deploy_with_two_ubuntu_bootstraps/deploy_with_two_ubuntu_bootstraps/
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.services_reconfiguration_thread_2/169/testReport/(root)/two_clusters_reconfiguration/two_clusters_reconfiguration/
Dima Ukov found error in logs:

>>>


2017-01-12 01:44:30 +0000 Scope(Class[Osnailyfacter::Netconfig::Connectivity_tests]) (notice): MODULAR: netconfig/connectivity_tests.pp
2017-01-12 01:45:30 +0000 Puppet (err): ERROR: Unable to fetch url 'http://mirror.seed-cz1.fuel-infra.org/pkgs/snapshots/ubuntu-2017-01-11-030059/', error 'execution expired'. Please verify node connectivity to this URL, or remove it from the settings page if it is invalid. on node node-2.test.domain.local
/etc/puppet/modules/osnailyfacter/lib/puppet/parser/functions/url_available.rb:95:in `rescue in fetch'
/etc/puppet/modules/osnailyfacter/lib/puppet/parser/functions/url_available.rb:83:in `fetch'
/etc/puppet/modules/osnailyfacter/lib/puppet/parser/functions/url_available.rb:106:in `block (4 levels) in <top (required)>'
2017-01-12 01:45:30 +0000 Puppet (err): ERROR: Unable to fetch url 'http://mirror.seed-cz1.fuel-infra.org/pkgs/snapshots/ubuntu-2017-01-11-030059/', error 'execution expired'. Please verify node connectivity to this URL, or remove it from the settings page if it is invalid."
1654967,2017-01-12 12:34:43 UTC,"And again https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.full_cluster_reinstallation/169/console
Test Verify full cluster reinstallation.
Error:AssertionError: Task 'deploy' has incorrect status. error != ready, 'All nodes are finished. Failed tasks: Task[connectivity_tests/1] Stopping the deployment process!'
Verification failed.
Repo availability verification failed on following nodes slave-04_compute_cinder.
Following repos are not available - http://mirror.seed-cz1.fuel-infra.org/pkgs/snapshots/ubuntu-2017-01-11-030059/, http://mirror.fuel-infra.org/mos-repos/ubuntu/9.2, http://mirror.seed-cz1.fuel-infra.org/mos-repos/ubuntu/snapshots/9.0-2017-01-11-172422."
1654967,2017-01-12 13:01:44 UTC,"https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.unlock_settings_tab_states/169/console
Check settings and network tabs is unlocked for a positively
deployed and redeployed cluster
Error: AssertionError: Task 'deploy' has incorrect status. error != ready, 'Deployment has failed. All nodes are finished. Failed tasks: Task[top-role-compute/3], Task[top-role-compute/5] Stopping the deployment process!'
Because in puppet:
Err http://mirror.seed-cz1.fuel-infra.org/pkgs/snapshots/ubuntu-2017-01-11-030059/ trusty/main libasound2-data all 1.0.27.2-3ubuntu7
  Could not connect to mirror.seed-cz1.fuel-infra.org:80 (5.43.231.83), connection timed out"
1654967,2017-01-12 14:32:30 UTC,"Reviewed:  https://review.openstack.org/417969
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=59909bda6c65f0f810fd3f8b76a8e19f1e2d3934
Submitter: Jenkins
Branch:    stable/newton"
1654967,2017-01-12 14:36:43 UTC,"Reviewed:  https://review.openstack.org/417952
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=9f3edd83bb8686c395e4437351c110e2e1e3f511
Submitter: Jenkins
Branch:    master"
1654967,2017-01-12 17:07:24 UTC,"Reviewed:  https://review.openstack.org/418935
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=aea46cf7ba5b99824cc858d30b0b26d3dfbb5ec6
Submitter: Jenkins
Branch:    stable/mitaka"
1654967,2017-03-17 12:37:46 UTC,"Verified on Fuel 10 build# 1483:
https://product-ci.infra.mirantis.net/job/10.0.main.ubuntu.bvt_2/1397"
1654967,2017-01-12 17:07:50 UTC,"Reviewed:  https://review.openstack.org/418937
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=ccd31901ad22ffd52aaaa15b92e678e933ee91e5
Submitter: Jenkins
Branch:    stable/newton"
1654967,2017-01-17 08:03:39 UTC,Verified on 9.2 snapshot #771.
1654967,2017-02-27 16:29:41 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1654967,2017-01-12 17:05:57 UTC,"Reviewed:  https://review.openstack.org/418934
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=066c7e5de99bce37db6b532ca4325e202e544be2
Submitter: Jenkins
Branch:    master"
1654967,2017-01-11 13:41:39 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/418935"
1654967,2017-01-09 11:25:05 UTC,"Moreover, the nodes that have connectivity check failing are controller nodes which actually have br-ex interface"
1654967,2017-01-10 10:34:19 UTC,"Verified on 9.2 snapshot #742.
Latest runs with fix are passed: https://product-ci.infra.mirantis.net/job/9.x.main.ubuntu.bvt_2/745/testReport/"
1654967,2017-01-11 13:41:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/418934"
1654967,2017-01-09 09:04:46 UTC,Repos are available on master and controller nodes.
1654967,2017-01-09 09:47:01 UTC,The reason is that on nodes where there is no br-ex interface default route is setup via br-mgmt for which there is no NAT to the external network.
1654967,2017-01-09 11:22:05 UTC,"This is an expected configuration by default since 6.x releases. The default route for compute nodes is configured through vrouter that is a network namespace called vrouter which is started on one of the controller nodes. NAT is configured within this namespace, so I would look into forwarding or networking config on the host node for tests."
1654967,2017-01-09 13:13:22 UTC,All failing nodes are computes.
1654967,2017-01-09 09:03:56 UTC,Compute nodes do not have connectivity to repos.
1654967,2017-01-09 16:23:53 UTC,"Okay, I found the issue - it was the regression as we flush default route that is set by vip__vrouter_pub resource"
1654967,2017-01-09 16:52:29 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/417968"
1654967,2017-01-09 16:52:42 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/417969"
1654967,2017-01-09 21:54:55 UTC,"Reviewed:  https://review.openstack.org/417968
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=9923c0970f64a7299a5697a9a850e48b4fac8f91
Submitter: Jenkins
Branch:    stable/mitaka"
1654967,2017-01-09 16:23:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/417952"
1654970,2017-01-09 09:04:12 UTC,"Looks to be the apparmor test suite, the kernel regression tests:"
1654970,2017-01-10 04:13:08 UTC,"It looks like this ""FATAL Error"" is a new debug message added to the apparmor test suite. The test ""syscall"" itself still failed anyway."
1654976,2017-01-29 17:19:05 UTC,Thanks for reporting.
1654976,2019-05-11 16:06:40 UTC,Still unfixed on disco dingo
1654976,2019-07-10 17:57:57 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853092
1654985,2017-03-09 06:16:57 UTC,"If compared by logging in to the server, the correct view as expected:
[root@pxc2 ~]# pt-config-diff h=localhost,u=root h=10.0.3.206,u=ptuser,p=ptpass | grep secure_file
secure_file_priv                                    /var/lib/mysql-files/"
1654985,2018-01-24 22:28:47 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1406
1654986,2017-01-09 11:05:34 UTC,The panel-button placement is also weird and unclear.
1655005,2017-01-09 15:03:13 UTC,"Also reproduced on Windows XP (32-bit), lp:inkscape/0.92.x rev. 15309."
1655005,2017-01-10 16:44:05 UTC,"Crashes (preview image in file chooser, or on load) with Inkscape 0.92+devel r15407 (default prefs) on Ubuntu 14.04."
1655007,2019-05-13 07:52:20 UTC,Check if if there any issues in your deployment process. Log in to the master node and debug systemd:
1655007,2017-03-29 09:55:25 UTC,"Hi,
I have encountered this before.
The reason of my situation was because after kube_master launching successfully and starting all service that kubernetes needs,
kube_master will start wc-notify.service to notify Heat that it has finished.
What wc-notify.service does is just curl heat api.
But if you configure endpoint api in host name such as http://hostname:8004/v1/%\(tenant_id\)s,
the curl command in wc-notify.service will also use hostname which kube_master doesn't know what it refers to try to curl heat api.
Thus,  wc-notify.service will failed and kube_master will stay in CREATE_IN_PROGRESS forever."
1655007,2018-07-06 05:42:55 UTC,"I had the same problem with a k8s cluster. In my case, it turned out, this was the problem:
https://bugs.launchpad.net/magnum/+bug/1744362"
1655007,2017-01-12 04:09:13 UTC,"@Murali, can you log into the booted instance and check the following status there:-"
1655007,2017-02-02 17:32:10 UTC,"Hi Yatin,
Here is the things you mentioned (attached few logs files)-"
1655008,2017-01-11 16:47:29 UTC,"@Dalton, I don't quite understand what your source is in this case. It initially says that it's in '.' but then suggests using `git pull` as a solution. Any chance your project is public so we can take a look? Even if you could just paste a snippet of your YAML for the kernel part that would be useful."
1655008,2017-01-11 17:32:41 UTC,"Hello Kyle,"
1655008,2017-01-11 17:45:15 UTC,"Excellent, thank you. All is clear now."
1655016,2017-01-09 15:16:34 UTC,"https://review.openstack.org/#/c/417902/
for mistralclient"
1655016,2017-01-09 15:17:06 UTC,"https://review.openstack.org/#/c/417881/1
for mistral"
1655016,2020-01-01 10:55:09 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/700832"
1655016,2020-01-09 09:14:42 UTC,"Reviewed:  https://review.opendev.org/700832
Committed: https://git.openstack.org/cgit/openstack/python-mistralclient/commit/?id=f5b15b6f6b6cbef11db8e0fe4f50b52dda1efb8b
Submitter: Zuul
Branch:    master"
1655016,2020-02-14 22:39:15 UTC,This issue was fixed in the openstack/python-mistralclient 4.0.0 release.
1655021,2017-01-16 12:07:55 UTC,I'm using Windows 7 64-bit Inkscape 0.92
1655021,2017-01-13 17:55:59 UTC,"@JazzyNico - I don't think this report should be milestoned at all: AFAICT this issue exists since very early on with Inkscape's SVG filter effects implementation, and is not a regression in a recent release."
1655021,2017-01-13 17:54:58 UTC,Also reproduced with Inkscape 0.47 r22583 (Nov 24 2009).
1655021,2017-01-09 16:28:25 UTC,"Possibly related earlier report:
* Bug #403257 “PNG does not export blur when exporting as page (but correct when exporting as drawing)”
  https://bugs.launchpad.net/inkscape/+bug/403257"
1655021,2017-01-10 04:21:37 UTC,"Workaround for the affected drawing in this report: change the 'Base frequency' for both Turbulence filter primitives from 1.000 to 0.999, then export Page area. Works with 0.91 and 0.92."
1655021,2017-01-09 16:19:37 UTC,Inkscape 0.92.0 r15299
1655021,2017-01-09 16:19:04 UTC,Inkscape 0.91 r13725
1655021,2017-01-09 16:17:46 UTC,Reproduced with Inkscape 0.91 r13725 and Inkscape 0.92.0 r15299 on OS X 10.7.5.
1655021,2017-01-09 14:58:35 UTC,Thanks for taking the time to write a report!
1655021,2017-01-09 16:24:52 UTC,"Also reproduced with lp:inkscape/0.48.x r10043 (same OS, same laptop)."
1655034,2017-03-28 09:23:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450672"
1655034,2017-02-20 10:23:59 UTC,Reducing priority as manual testing is done
1655034,2017-02-21 08:19:43 UTC,We have not started writing functional test in ocata. We will write functional test in pike. So we will resolve this bug in pike.
1655034,2017-02-15 05:32:53 UTC,Steps to create multiple compute service on one host
1655034,2017-01-25 09:28:57 UTC,"These scenarios can very well be tested in a unit test setup, by using the mock support of the zhmcclient."
1655034,2017-02-17 05:55:13 UTC,"1. It is working fine when we use
openstack server create --flavor dpm --volume 9c0d379a-c029-466f-9b61-4f2a200316db --nic net-id=71f29e77-c46f-4c35-ab21-f2ac7e39f16f test_server1"
1655041,2017-01-09 18:29:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655041,2017-02-07 18:35:25 UTC,"Hello,"
1655041,2017-02-08 13:16:50 UTC,v4.4.41 through v4.4.44 will be released with Ubuntu-4.4.0-63.84.
1655041,2017-02-20 07:42:07 UTC,This bug was fixed in the package linux - 4.4.0-63.84
1655049,2017-01-09 22:44:10 UTC,Thanks for the test case. Here's what I saw after running `sudo python3 -m netaddr.eui.ieee` on my system:
1655049,2017-01-10 17:53:04 UTC,"The actual source of the issue seems to be that netaddr indexes a file that it doesn't own (from ieee-data package), and then assumes that it won't change underneath it (either because of an ieee-data update, or a netaddr update in the case of a running process), which results in various exceptions and other errors from the code.  I believe that a fresh bug is being filed against python-netaddr on the issue."
1655049,2017-01-10 17:33:53 UTC,"Thanks for quick response, I see you already have the MACs which cause problems, if needed I can print the ones which caused problem at my side"
1655049,2017-01-09 22:40:59 UTC,Interesting point.  Here is what I see:
1655049,2017-01-10 22:14:30 UTC,I filed two additional bugs to track this.
1655049,2017-01-09 16:55:17 UTC,MAAS was incomplete in the workaround for Bug#1628761.
1655049,2017-01-09 16:33:54 UTC,"I found some that exhibit the issue (00-22-59, 00-23-89) for starters."
1655049,2017-01-09 16:22:32 UTC,"Can you provide the first 3 octets of one of the bad MACs?  If you're not sure which one, the following is sure to catch it:"
1655049,2017-01-09 22:26:05 UTC,"Hm. I think the root cause of this might be that the index is not updated often enough (that is, it could be a Debian package mismatch)."
1655051,2017-01-09 15:59:42 UTC,"This is actually a real regression.   2.2.0-0ubuntu1~ubuntu16.04.1~ppa2 from the juju/stable PPA exhibits the bug, but charm 2.1.1-0ubuntu1 does not."
1655051,2017-03-20 04:51:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655053,2017-09-07 21:10:40 UTC,Copying my recent comment from bug #1715442:
1655053,2017-09-06 18:01:54 UTC,"su_v wrote:

> I might have filed other reports at the time with issues related to
> the auto-fixing of baseline spaces, but I haven't checked atm.
"
1655053,2017-09-06 17:37:00 UTC,"Thank you, V!"
1655053,2017-09-06 17:31:11 UTC,The file from mentioned bug #1715442 opens ok in 0.92.2 if inkscape is launched with the command line option '--no-convert-text-baseline-spacing' to prevent auto-fixing legacy (pre-0.92) files' text baseline spacing on opening ... i.e. not directly related to the issue tracked in this report (bug #1655053) which is triggered by one of the DPI change options the user has to explicitly select on opening.
1655053,2017-09-06 17:08:43 UTC,"Oh, I think this could be the same as https://bugs.launchpad.net/inkscape/+bug/1715442"
1655053,2017-01-12 09:48:05 UTC,"Also reproduced on Xubuntu 16.04, lp:inkscape/0.92.x rev. 15315."
1655053,2017-01-10 16:44:18 UTC,Not reproduced with Inkscape 0.92+devel r15407 (default prefs) on Ubuntu 14.04 with 'Scale test - all'.
1655053,2017-01-09 15:14:01 UTC,"Backtrace after a (random) interrupt in the debugger while inkscape attempts to scale elements in the provided test case.
(tested with lp:inkscape/0.92.x r15309 on OS X 10.7.5)"
1655057,2017-02-20 07:46:10 UTC,This bug was fixed in the package linux - 4.8.0-38.41
1655059,2017-01-13 07:29:43 UTC,"I looked into a fix for this:
The problem is in
/lib/systemd/system/ifup@.service"
1655059,2017-01-18 21:23:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655059,2017-05-09 15:26:20 UTC,"Either that, or when calling these units systemd-escape should be run over the names."
1655060,2019-10-15 11:39:29 UTC,Snapd support DBus services so I'm marking this as fix released. Keeping the snapcraft side of the task open.
1655060,2019-10-25 22:21:56 UTC,Likewise
1655060,2017-01-09 16:08:57 UTC,"As mentioned on the mailing list, snapd doesn't fully implement the dbus daemon type: https://lists.ubuntu.com/archives/snapcraft/2016-December/001993.html and I think it is correct that snapcraft not list it as a supported type at this time. The snap wiki (https://github.com/snapcore/snapd/wiki/Snap-format) used to list it as supported, but I removed it last month. Also, because this is not properly implemented and not documented, I removed it from the tools. We have a 'dbus' interface that is supported today (and is documented) and perhaps the future dbus activation and session work will bring 'daemon: dbus' back, but for now I think it is best to not document it."
1655060,2017-01-09 16:38:49 UTC,"Thanks for the info Jamie. I'm adding a task for snapd so they remove it from the valid attributes. If it's not properly supported, snaps with that value in the yaml should fail."
1655065,2017-01-09 16:00:18 UTC,This change was made by a bot.
1655065,2017-01-09 20:52:10 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1655065,2017-01-10 19:09:19 UTC,The bug does not appear in 4.10-rc3
1655065,2017-01-12 18:56:39 UTC,"Kernel 4.8.0-32 introduced changes from the mainline kernels 4.8.7, 4.8.8, 4.8.9, 4.8.10 and 4.8.11 . In my testing, 4.8.8 works fine and suspend is broken starting with 4.8.9. Furthermore, suspend is still broken with the latest 4.8 kernel which is 4.8.17 (therefore the tag kernel-fixed-upstream might not be appropriate)."
1655065,2017-01-12 19:05:07 UTC,Bug reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=192471
1655065,2017-01-19 16:53:53 UTC,"Bug closed upstream since 4.8 is EOL and the bug does not appear in 4.9 and 4.10. I'm willing to do a bisect to find the problematic commit, but only if I can get some guarantee that this will lead to someone taking the time to review the result and do what's needed to get a fix in 16.10. Otherwise I'm personally fine running a mainline kernel."
1655065,2017-07-26 15:49:53 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1655084,2018-08-22 11:02:47 UTC,"""The following packages will be unheld"" should do it."
1655085,2017-01-09 19:12:22 UTC,"Sorry the .iso image of my live-usb key boots actually a Ubuntu 16.10 system.
The bugs are still present in this live session.
Should I let my computer open for further investigation or may I restart it with my Linux Mint system ?"
1655085,2017-01-09 20:51:09 UTC,"Can you see if this issue also happens with the latest daily image?  It can be downloaded from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/"
1655085,2017-01-09 21:42:44 UTC,Unfortunately yes.
1655085,2017-03-11 04:17:45 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1655085,2018-02-05 15:39:18 UTC,"After having found a linux distribution (Linux Mint 17.3 xfce) working on my computer, I unfortunately update my system last month and my system is now bugging again.
I would like so much install a classic ubuntu on my one-year computer.
If you have any hint, please let me know."
1655085,2018-02-08 18:04:55 UTC,"OK. Thanks.
I downloaded ""Build for amd64"" packages and I am going to install them.
I will write another post to share the results."
1655085,2018-02-07 21:16:16 UTC,Thanks for your message Kai-Heng Feng.
1655085,2018-02-08 04:00:30 UTC,"> On Feb 8, 2018, at 5:16 AM, Mehdinefrance <email address hidden> wrote:
>
> Thanks for your message Kai-Heng Feng.
>
> I am puzzled when I click on the link you sent me, even after having
> checked the help section
> (https://wiki.ubuntu.com/Kernel/MainlineBuilds).
>
> Is there any possibility for me to make a live-usb key with a mainline
> kernel so that I can test it on my computer ? If so, is there any iso
> image I could download ?
"
1655085,2018-04-03 16:13:49 UTC,"Hi,"
1655085,2018-02-09 18:13:41 UTC,"Unfortunately, the bug is still here. Even after I install ""linux-headers-4.15.1-041501_4.15.1-041501.201802031831_all.deb"" package."
1655085,2017-01-09 19:03:09 UTC,"OK, I just run the command from a Ubuntu 16.04 live session on my computer."
1655085,2018-02-07 04:36:37 UTC,Try mainline kernel [1].
1655085,2017-01-09 18:59:14 UTC,apport information
1655085,2017-01-09 18:58:55 UTC,apport information
1655085,2017-01-09 18:59:08 UTC,apport information
1655085,2017-01-09 18:59:07 UTC,apport information
1655085,2017-01-09 18:59:06 UTC,apport information
1655085,2017-01-09 18:59:05 UTC,apport information
1655085,2017-01-09 18:59:03 UTC,apport information
1655085,2017-01-09 18:59:02 UTC,apport information
1655085,2017-01-09 18:59:00 UTC,apport information
1655085,2017-01-09 18:58:58 UTC,apport information
1655085,2017-01-09 18:58:56 UTC,apport information
1655085,2017-01-09 18:58:54 UTC,apport information
1655085,2017-01-09 18:00:57 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1655085,2017-01-09 18:59:12 UTC,apport information
1655094,2017-10-25 19:28:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655100,2018-05-16 06:17:55 UTC,Vanilla Ubuntu/Kubuntu install and this still hasn't been fixed.
1655100,2018-04-24 07:35:43 UTC,Please try the kernel for Artful and Bionic:
1655100,2018-04-19 15:09:53 UTC,Any update on this for 18.04?
1655100,2018-02-13 05:09:31 UTC,"The patch has ""Cc: <email address hidden>"" hence Xenial's v4.4 based kernel will automatically pick this patch."
1655100,2018-02-12 11:29:42 UTC,Great news and thank you for posting the information @fireburn :)
1655100,2018-02-12 11:12:53 UTC,"A patch https://patchwork.kernel.org/patch/10212201/ is going to fix this issue properly, it should be backported to older kernels too, so hopefully going forward your NVMe drives won't require any workarounds, it should also fix USB-C detection too"
1655100,2017-11-30 00:38:49 UTC,"Confirm this bug occurs on Ubuntu 16.04 w/Alienware 17R3, i7 6700HQ, HM170 chipset. The workaround to use `acpiphp.disable=1` on kernel command line fixes suspend/resume cycle."
1655100,2018-05-28 09:33:45 UTC,"Please try the kernel:
https://people.canonical.com/~khfeng/lp1655100-2/"
1655100,2017-07-26 15:49:56 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1655100,2017-02-10 15:30:27 UTC,"So, been running with 16.10 using the boot parameter ""acpiphp.disable=1"" and yes suspend/resume works just fine for the NVME devices, no more loss of root partition etc."
1655100,2017-02-09 18:45:05 UTC,"Great find @knopki, will re-install Ubuntu and use the boot parameter and see what else might break during my normal use :)"
1655100,2017-02-09 01:26:14 UTC,"Just for note:
Found this thread with same bug on Mint 18 on Alienware 13 R2: https://forums.linuxmint.com/viewtopic.php?t=234368"
1655100,2017-01-29 18:31:54 UTC,Any update and/or progress on this @jsalisbury?
1655100,2017-02-07 09:05:30 UTC,"@grenangen Just for note.
Maybe related upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=112121"
1655100,2017-02-06 20:41:47 UTC,Thanks for the reply. Since I have had some additional time on my hand I have played around a bit with kernels and firmwares.
1655100,2017-02-06 20:03:01 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1655100,2017-01-14 02:00:28 UTC,"I also tried to enable hibernation, same issue with NVME drives using hibernation as when using suspend. Skylake truly is a mess on Linux :/"
1655100,2017-01-14 01:18:07 UTC,"As I suspected, issue is still present with the 4.10 kernels. Tried it on a separate clean install using 16.10 upgrading the kernel to v4.10-rc3 mainline"
1655100,2017-01-09 21:23:52 UTC,"Tested latest 17.04 daily build from Jan 9th.
Issue is present there as well running kernel version 4.9.0-11. Same symptoms as with 16.10."
1655100,2017-01-09 20:54:19 UTC,"Can do, but it will take some time, getting late in my timezone and I will need to prepare a side install for testing with upstream."
1655100,2017-01-09 20:40:10 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1655100,2017-01-09 18:03:04 UTC,Addendum. Had the same issue with 14.04 and 16.04 as well. And this seems to be same/related to 1568703 as well.
1655100,2017-01-09 18:01:12 UTC,This change was made by a bot.
1655100,2017-02-08 21:07:48 UTC,"@knopki, did you get around to testing Solus? Found something that might help us understand what the difference is? :)"
1655125,2017-10-06 13:16:23 UTC,I believe the solution for these needs are the same of those being discussed to support GTK themes via the content interface. The changes are being discussed here:
1655125,2017-09-28 18:38:54 UTC,See also this thread on the Snapcraft forum:
1655125,2017-09-28 18:32:27 UTC,Me too: I am snapping CUPS so that printer drivers can be provided as snaps (= distro-independent packages) which connect to CUPS as a plugin. So I need exactly the feature requested here.
1655125,2017-09-28 15:47:04 UTC,When can we have this conversation?
1655125,2017-08-18 12:40:17 UTC,I'm marking this as triaged just ack the existence and validity. This needs more research and discussion though.
1655125,2017-01-24 10:27:10 UTC,I've hit this issue in Nextcloud when trying to integrate it with nextant application and Solr server to enable documents search. Having that in other snap would need some kind of communication with nextcloud one which is not now possible until having this fixed.
1655125,2017-02-09 21:12:05 UTC,"This is what I need to do the LightDM snap correctly, for example you might have two greeter provider snaps (Unity greeter, GTK+ greeter)."
1655125,2017-01-24 13:01:28 UTC,"Nextcloud has several default internal applications included in the product when it is deployed/installed. It also accepts other applications created by any user to perform whatever is needed. Nextcloud snap, when installed, sets a path into its common folder for those extra apps. It is supposed to have every extra app in a separated snap from the nextcloud one. So, the requirement should be having ""myapp"" snap be able to deploy the app in the nextcloud snap common folder somehow, so that nextcloud can make use of it.
In the specific case of search support, Solr is the server where the documents index is held and nextant is the application to be deployed in nextcloud common folder path. (or communicated with nextcloud using content interface)"
1655125,2017-01-24 12:42:24 UTC,Hey
1655125,2019-10-29 21:38:20 UTC,We are not currently working on implementing this new feature.
1655125,2017-02-10 08:02:20 UTC,"From my post on the snapcraft ML:
So, I'm in the situation where one snap would need to get configuration
and access to some files from other snaps. It's really similar to our
plugin story: even if in that case, we are talking about optional
configuration and files from one or multiple snaps shared with a single
one collecting them all."
1655125,2017-01-13 11:07:35 UTC,I have a similar use case where a application can be extended with plugins for further functionality. In this case they don't need to be in a particular path but the main snap needs to take a single file from the plugin snap and process it further. It also needs to know when the plugin snap was removed or upgraded so it can either remove or reload the plugin in the application.
1655125,2017-01-10 02:17:56 UTC,Both approaches (existing interface or new interface) are technically feasible and relatively simple to support from where we are today.
1655125,2017-01-12 20:21:52 UTC,"I'm not sure I completely understand the questions, but I'll take a crack at them. Please ask for clarification if needed."
1655125,2017-01-09 19:33:59 UTC,"I think the content interface does solve that. What is harder is to figure out who can connect to who. I think the assertion system should control this, then the content system can do the rest."
1655127,2017-01-10 11:51:42 UTC,"There's a one-hour timeout on network access, counting from the start of the build.  (In theory we could raise this, but it's a useful defence and I don't want to do so indefinitely.)  Even though it's no longer strictly always required, you should try to do all your network access in the pull phase, which in this case should have the effect of doing it before time-consuming build tasks.  Can you arrange to do these git clones in the pull phase?"
1655127,2017-01-10 12:10:51 UTC,Pulling stuff during build() instead of doing it in pull() proper is a workaround for bug 1649620. see: https://git.launchpad.net/~bjoern-michaelsen/df-libreoffice/+git/libreoffice-snap-playground/commit/?id=0237177276bcfc56abfba89626652c9202a271ff
1655127,2017-01-11 15:30:26 UTC,"> I will try to adjust this.
"
1655131,2019-02-07 15:27:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655145,2017-01-09 20:50:18 UTC,"I'd be better if whoopsie was able to send only the core dump again and not the whole report, but I think this behavior is okay for the time being."
1655146,2017-01-12 22:01:33 UTC,Is there any workaround to overcome this issue ?
1655146,2017-01-10 05:23:33 UTC,"The issue here is that the default support in ceilometer will assume that object-storage is swift, rather than a ceph-radosgw which behaves in a slightly different way in terms of URI's."
1655147,2017-01-09 21:07:29 UTC,"I would like to see an additional configuration item added that would allow you to accept a self-signed certificate for the simplestreams mirror url, or some mechanism to allow adding the certificate per the developer's preference."
1655147,2017-01-09 21:14:07 UTC,This limitation makes it impossible for users in isolated environments to use the lxd provider with juju if they do not have a commercial ssl server available for the simplestreams mirror.
1655156,2017-01-13 14:18:58 UTC,"Also reproduced on Xubuntu 16.04, lp:inkscape/0.92.x rev. 15315."
1655156,2017-01-10 00:09:27 UTC,"su_v wrote:

> this change of behavior seems to have been exposed with the changes
> in r14130
"
1655156,2017-01-09 23:55:35 UTC,"Based on tests with archived builds (on OS X 10.7.5):
- not reproduced with Inkscape 0.48.5 r10040,
- not reproduced with Inkscape 0.91 r13725,
- not reproduced with lp:inkscape rev <= 14129,
- reproduced with lp:inkscape rev >= 14130,
- reproduced with Inkscape 0.92.0 r15299,
- reproduced with lp:inkscape/0.92.x r15312;
this change of behavior seems to have been exposed with the changes in r14130:
https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/changes/14130"
1655156,2017-01-09 23:03:45 UTC,Oki. Test case zipped in the attachment.
1655156,2017-01-09 21:53:37 UTC,"Please attach a test case (Inkscape SVG file(s), before and after applying the path operation) to the bug report to allow further investigation, thank you."
1655156,2017-02-04 21:09:41 UTC,fixed in r.15473
1655156,2017-01-09 23:41:49 UTC,"This happens when using the preference setting for Clippaths and masks to not remove the clippath/mask object after applying (not the default), and the clipped object is within a transformed (layer) group or has itself a preserved transform attribute (e.g. a translate() command)."
1655160,2017-02-04 18:27:22 UTC,"Thank you, Jabier! :-D"
1655160,2017-01-10 19:42:32 UTC,"Also reproduced on Windows XP (32-bit), Inkscape 0.91 and lp:inkscape/0.92.x rev. 15313."
1655160,2017-02-04 11:21:48 UTC,Fixed in r.15472
1655160,2017-01-10 12:18:27 UTC,"JFTR - same behavior with Inkscape 0.47, 0.48.5, 0.91, 0.92.0 and 0.92.x r15313 (on OS X 10.7.5)."
1655160,2017-01-10 18:05:36 UTC,Never noticed before :) Thank you for testing and for workaround!
1655164,2019-09-19 15:02:20 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1655164,2017-02-03 14:20:11 UTC,"@Jeff,"
1655167,2017-01-10 16:24:13 UTC,"Yes, that's the case I was afraid to reach. I thought in general not many users would have 2 different CAs though."
1655167,2017-01-10 16:19:22 UTC,"It is not necessarily true.
In general case horizon endpoint may be different from keystone pub endpoing.
Say, Horizon access is provided at ""https://cloud.domain.tld"", while keystone is at ""https://keystone.domain.tld"".
In this case there may be 2 different CA certs issued with the servers certificates."
1655167,2017-01-10 13:31:54 UTC,"That's true.
We could also assume that the cacert is located at {{ horizon_ssl_ca_cert }}, which is uploaded if user provided, from deploy node path {{ horizon_user_ssl_ca_cert }}."
1655167,2017-01-10 16:16:26 UTC,Also I think it's safe to assume we won't check for OSA generated certificates.
1655180,2017-01-10 07:13:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655183,2017-01-10 17:53:40 UTC,Can you give us some more info about this bug?
1655189,2017-01-10 12:42:11 UTC,"Start with Xorg.0.log, glxinfo, vainfo and details on how you record the video."
1655189,2020-02-10 15:32:29 UTC,"Since I'm no longer using Ubuntu, I'm unsubscribing from this report."
1655189,2017-01-10 00:44:00 UTC,And here a video using webm as codec:
1655189,2017-01-10 01:13:15 UTC,The only application that seems to show errors in stderror related with video seems to be guvcview.
1655189,2017-01-10 12:13:11 UTC,Doesn't happen in another computer using AMD graphics.
1655189,2017-01-10 12:35:09 UTC,"HOW TO REPRODUCE:
Record a video using the Theora codec."
1655189,2017-01-10 12:51:25 UTC,"Created attachment 128850
Xorg.0.log"
1655189,2017-01-10 12:53:16 UTC,"Created attachment 128851
glxinfo.txt"
1655189,2017-01-10 12:55:01 UTC,"Created attachment 128852
vainfo.txt"
1655189,2017-01-10 12:57:49 UTC,"What I did to record those videos was mostly to clic on the ""Record"" button from the various applications. Which where a web-cam recorder, a desktop recorder, and a video converter."
1655189,2019-11-27 13:47:09 UTC,-- GitLab Migration Automatic Message --
1655193,2019-04-07 10:32:34 UTC,"Fixed in revision 4a9f82109a09209a9217f646bb571b9ba6252d95
https://git.launchpad.net/kicad/patch/?id=4a9f82109a09209a9217f646bb571b9ba6252d95"
1655193,2018-05-11 16:16:55 UTC,"If we already quote ""when needed"", then the parser already knows how to handle quotes and there's no backwards compatibility issue.  Why not just quote them all?"
1655193,2017-01-14 18:28:31 UTC,"This quoting was breifly discussed on the list, yes, but didn't we agree that we would try to force quoting but still support reading non quoted files?"
1655193,2017-01-14 01:52:32 UTC,"I know we've argued about this before and didn't come to an agreement, but honestly I agree. I know this isn't a use case we intend to support, but it is honestly just *weird* that we're deciding whether or not to quote strings based on whether they ""need"" it. It's error-prone and pointless."
1655193,2017-01-11 22:13:41 UTC,"Wayne,"
1655193,2017-01-11 21:16:34 UTC,I'm trying to understand what you mean by date field.  Are you setting the date field in the kicad_pcb file header (the first line) or the title block date field or something else?
1655224,2017-01-11 14:56:59 UTC,"The following related bug is really the root cause here.  If it didn't exist, we wouldn't have to try to munge the bridges ahead of Juju:"
1655224,2017-02-14 06:36:21 UTC,To address why I think this happens.
1655224,2017-02-14 07:05:45 UTC,Removing 2.1 milestone as we will not be addressing this issue in 2.1.
1655226,2018-09-26 05:02:31 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/399
1655229,2019-05-29 07:19:27 UTC,"Lowering importance - based on discussion in mail thread ...
(As already stated - this depends heavily on LP 1614364.)"
1655229,2017-02-17 11:13:18 UTC,"Since bug # 1614364 is considered Critical for 2.1.1 and it's the root cause as per comment # 1, I am removing this bug from 2.1 milestone."
1655229,2017-01-11 14:57:04 UTC,"The following related bug is really the root cause here.  If it didn't exist, we wouldn't have to try to munge the bridges ahead of Juju:"
1655264,2017-01-17 09:26:11 UTC,"Reviewed:  https://review.openstack.org/418983
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=baa107f31873624e98da76a85dd6a60205899050
Submitter: Jenkins
Branch:    stable/newton"
1655264,2017-01-10 12:07:28 UTC,here is a link to log snapshot https://drive.google.com/file/d/0BzdcP1_NuusEeGdlRndNUE82Ylk/view?usp=sharing
1655264,2017-01-10 16:41:26 UTC,"We are checked the problem env and there was wierd data in the DB. In plugins.roles_metadadata there wasn't 'tags' for roles, but this data is added by migration for existed plugins: https://github.com/openstack/fuel-web/blob/stable/mitaka/nailgun/nailgun/db/migration/alembic_migrations/versions/fuel_9_2.py#L805. I've improved migration test for this case: https://review.openstack.org/#/c/418473/"
1655264,2017-01-11 13:20:17 UTC,"The reason of inconsistent data in the DB - bug in the plugins synchronisation. When plugin is synced, roles_metadata is just rewritten without tags info."
1655264,2017-01-11 14:43:46 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/418982"
1655264,2017-01-11 14:44:24 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/418983"
1655264,2017-01-12 14:01:24 UTC,"Reviewed:  https://review.openstack.org/418473
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=6b4d6acac1b9358c74a2706e9fdedf81b4c50e61
Submitter: Jenkins
Branch:    master"
1655264,2017-01-12 14:14:02 UTC,"Reviewed:  https://review.openstack.org/418982
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=3850bba4832916938419f4d499b023ce6e59e1be
Submitter: Jenkins
Branch:    stable/mitaka"
1655264,2017-01-23 15:04:54 UTC,verified for mos9.2 with contrail plugin 5.0.1
1655264,2017-02-27 16:24:43 UTC,This issue was fixed in the openstack/fuel-web 11.0.0.0rc1 release candidate.
1655273,2018-04-16 15:44:40 UTC,"I actually think the problem here is bigger. The error message from actions needs to be easier for humans and machines to read. The information there is good, and sometimes even useful - but we should make it easier to work with."
1655273,2018-04-16 15:45:24 UTC,I marked this as low-hanging-fruit because I think the implementation should be quite easy - but first we need to discuss it and decide what to change. That bit might take a little longer.
1655275,2018-06-25 09:11:03 UTC,Apport crash is attached
1655275,2018-11-27 00:56:25 UTC,There's a patch which fixes this problem for me at https://src.fedoraproject.org/rpms/disper/blob/7c60c3c00505b9bba9593f0b538ef1b0a72268f5/f/disper_0.3.1-fix-misbehavior-bug-1531704.diff
1655275,2018-06-25 09:03:09 UTC,apport information
1655275,2018-06-25 09:03:12 UTC,apport information
1655275,2020-01-01 11:03:35 UTC,"Notice that the ""Fix Released"" mention here means that the bug is ""fixed"" by removing the package altogether form Debian."
1655275,2018-06-25 09:03:11 UTC,apport information
1655275,2017-01-10 11:49:24 UTC,"Thanks for your bug report, I can confirm this."
1655275,2018-06-25 09:03:08 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-26 (59 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS ""Bionic Beaver"" - Release amd64 (20180426)
Package: disper 0.3.1-2
PackageArchitecture: all
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Tags:  bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True"
1655275,2018-06-25 06:09:21 UTC,I have the same problem with ubuntu 18.04
1655275,2017-10-17 05:34:03 UTC,I have the same problem with ubuntu 17.10.
1655280,2019-05-07 19:12:52 UTC,"------- Comment From <email address hidden> 2019-05-07 15:03 EDT-------
While I initially suggested the udev below rules:"
1655280,2019-05-10 10:50:28 UTC,"------- Comment From <email address hidden> 2019-05-10 06:43 EDT-------
(In reply to comment #53)

> Hi, Hari.
"
1655280,2019-05-09 17:05:41 UTC,"Hi, Hari."
1655280,2019-05-09 09:28:42 UTC,"Ok, in that case this seems like a verification-failed. @cascardo can you follow up on this SRU?"
1655280,2019-05-10 11:20:39 UTC,"------- Comment From <email address hidden> 2019-05-10 07:10 EDT-------
(In reply to comment #53)
[...]

> could proceed with the SRU, and open a new bug to fix the CPU hotplug case,
> if there is one.
"
1655280,2019-04-29 16:20:10 UTC,"Hello bugproxy, or anyone else affected,"
1655280,2019-05-10 12:16:47 UTC,"Hi, Hari."
1655280,2019-04-29 13:44:54 UTC,"Update: LP#1811692 is now ""Fix Released"". makedumpfile was added to the SRU queue on 11th Feb. Waiting on SRU queue approval."
1655280,2019-03-26 17:15:31 UTC,"Hi, Andrew."
1655280,2019-03-08 07:50:58 UTC,"Thx Manoj for updating the SRU template.
@thadeu, does that give everything that's needed?"
1655280,2019-03-07 12:56:20 UTC,"Hi, @manjo."
1655280,2019-03-06 19:45:25 UTC,"@cascardo, the issue was reported in Xenial, now  that the fix is released in Disco does it make it a good candidate for a backport to Xenial and Bionic?"
1655280,2019-04-29 16:09:01 UTC,"Hello bugproxy, or anyone else affected,"
1655280,2019-05-10 15:40:49 UTC,"------- Comment From <email address hidden> 2019-05-10 11:32 EDT-------
(In reply to comment #55)

> (In reply to comment #53)
> [...]
> > could proceed with the SRU, and open a new bug to fix the CPU hotplug case,
> > if there is one.
>
> Raised bug 177551 to follow-up on the problem in CPU hot-add case which
"
1655280,2019-05-20 17:40:35 UTC,"------- Comment From <email address hidden> 2019-05-20 13:34 EDT-------
(In reply to comment #61)

> Issue is now ""Fix Released"" everywhere except Xenial. Should this now be
> backported to Xenial or would that incur too much regression risk?
"
1655280,2019-05-20 08:46:37 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.10.1
1655280,2019-05-20 08:46:46 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1655280,2019-05-20 09:21:33 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.1
1655280,2019-05-20 13:41:08 UTC,"Issue is now ""Fix Released"" everywhere except Xenial. Should this now be backported to Xenial or would that incur too much regression risk?"
1655280,2019-05-21 14:10:09 UTC,"Well, there was a regression when I first uploaded the fix and we noticed that during dump, if there was a hotplug event, it would kill makedumpfile before it completed. When restarting, makedumpfile would find the same file already there, which would prevent the new dump to even start, so the system would reboot with an incomplete dump. That was reported and fixed as LP bug 1811692."
1655280,2019-08-16 17:11:14 UTC,"This has been blocked because we need to get changes on the development release first, and recent changes on testing has caused ppc64el testing failures. Those changes allowed tests to be run on VMs with more memory, which allow the test to run instead of being skipped. So now we are detecting a failure, though I couldn't be able to reproduce it so far, which is what is blocking progress here."
1655280,2019-08-28 17:31:57 UTC,Backport to xenial attached at https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1828596/comments/26. Waiting for sponsorship now. Should get in -proposed by next week.
1655280,2019-10-23 17:56:41 UTC,This is going to be fixed on xenial once we fix #1828596 as well.
1655280,2019-11-11 15:49:47 UTC,Changing to Incomplete until LP 1828596 is fixed.
1655280,2020-01-14 14:17:57 UTC,"Hello bugproxy, or anyone else affected,"
1655280,2020-01-16 17:18:04 UTC,"------- Comment From <email address hidden> 2020-01-16 11:01 EDT-------
Issue resolved on xenial with kdump-tools version
1:1.6.3-2~16.04.2"
1655280,2020-01-29 03:50:17 UTC,This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.2
1655280,2019-02-18 10:08:22 UTC,"Since the required fix is in makedumpfile, marking the linux track as invalid."
1655280,2019-05-10 15:50:56 UTC,"------- Comment From <email address hidden> 2019-05-10 11:40 EDT-------
(In reply to comment #53)
[...]"
1655280,2019-02-18 10:07:43 UTC,Required fix is to makedumpfile package therefore marking the linux track as invalid.
1655280,2017-01-10 18:09:55 UTC,"------- Comment From <email address hidden> 2017-01-10 12:59 EDT-------
Assigning to Hari for some assistance but would like to know if this issue can be recreated consistently and if so how and does this occur on other LPARs running the same level?"
1655280,2019-01-18 10:20:55 UTC,This should be in disco soon.
1655280,2017-01-10 09:29:32 UTC,Default Comment by Bridge
1655280,2017-01-10 09:29:46 UTC,Default Comment by Bridge
1655280,2019-01-18 18:21:25 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1
1655280,2017-01-11 01:29:42 UTC,"------- Comment From <email address hidden> 2017-01-10 20:20 EDT-------
(In reply to comment #7)

> Assigning to Hari for some assistance but would like to know if this issue
> can be recreated consistently and if so how and does this occur on other
> LPARs running the same level?
"
1655280,2017-01-23 17:30:22 UTC,"Steve, could your team please take a look ?"
1655280,2017-07-14 07:59:46 UTC,------- Comment (attachment only) From <email address hidden> 2017-07-14 03:58 EDT-------
1655280,2017-07-14 09:09:50 UTC,"------- Comment From <email address hidden> 2017-07-14 05:02 EDT-------
Issue is observed even on 16.04.03. When crash is triggered after memory remove operation."
1655280,2017-08-22 13:52:44 UTC,"Hi, hbathini."
1655280,2017-08-22 14:39:45 UTC,"------- Comment From <email address hidden> 2017-08-22 10:32 EDT-------
(In reply to comment #20)

> Hi, hbathini.
>
"
1655280,2017-08-30 19:41:10 UTC,"Hi, Hari."
1655280,2017-08-31 08:59:53 UTC,"------- Comment From <email address hidden> 2017-08-31 04:54 EDT-------
(In reply to comment #22)

> Hi, Hari.
"
1655280,2017-09-01 14:24:04 UTC,bug 1664545 may be related.
1655280,2018-02-26 15:24:22 UTC,"IBM, could you please confirm this bug is already fixed using the workaround mentioned here and in bug 1664545"
1655280,2017-01-23 06:49:35 UTC,"------- Comment From <email address hidden> 2017-01-23 01:45 EDT-------
Hi Canonical,"
1655280,2018-03-05 16:01:22 UTC,Default Comment by Bridge
1655280,2018-03-05 16:01:24 UTC,------- Comment (attachment only) From <email address hidden> 2017-07-14 03:58 EDT-------
1655280,2018-03-08 16:03:20 UTC,"So, the workaround would be reloading the dump after DLPAR. In order to do that, run:"
1655280,2018-03-08 16:04:00 UTC,It's not clear what the logs in comments #16 and #17 refer to. Could you please clarify?
1655280,2018-03-08 19:10:57 UTC,"------- Comment From <email address hidden> 2018-03-08 14:01 EDT-------
(In reply to comment #29)

> So, the workaround would be reloading the dump after DLPAR. In order to do
> that, run:
>
> kdump-config unload ; kdump-config load
>
"
1655280,2018-03-19 14:04:33 UTC,Could you please comment as to whether the workaround resolved the issue?
1655280,2018-03-21 13:10:50 UTC,"------- Comment From <email address hidden> 2018-03-21 09:04 EDT-------
(In reply to comment #31)

> Could you please comment as to whether the workaround resolved the issue?
"
1655280,2018-03-22 17:21:10 UTC,"------- Comment From <email address hidden> 2018-03-22 13:18 EDT-------
(In reply to comment #32)

> (In reply to comment #31)
> > Could you please comment as to whether the workaround resolved the issue?
>
> Yes, the workaround resolves the issue. But could we have a udev rule added
> in kdump-tools
> to trigger kdump-tools.service restart after a DLPAR memory/CPU add/remove
> operation
> instead of manually restarting kdump-tools service after a DLPAR operation..
"
1655280,2018-03-05 16:01:02 UTC,Default Comment by Bridge
1655280,2018-07-19 20:17:44 UTC,Can you try the package in ppa:cascardo/ppa?
1655280,2018-08-11 12:50:03 UTC,"------- Comment From <email address hidden> 2018-08-11 08:48 EDT-------
After upgrading to kdump-tools_1.6.4-1~16.04.0cascardo2_ppc64el.deb package,
dump capture succeeds without any complaints:"
1655280,2018-10-17 12:04:29 UTC,"This fix has been uploaded to Debian, and will be synced to 19.04 when it opens. After that, it will be backported to cosmic, bionic and xenial."
1655280,2018-12-18 13:37:28 UTC,I am working on the sync/merge from Debian to Ubuntu.
1655284,2017-01-11 11:37:39 UTC,"Fix here:
https://nav.uninett.no/hg/nav/rev/85f0efc1e4ba"
1655285,2017-05-11 03:04:49 UTC,"Change abandoned by feng.shengqin (<email address hidden>) on branch: master
Review: https://review.openstack.org/418285"
1655285,2017-01-10 09:42:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/418285"
1655289,2017-04-07 10:20:43 UTC,"Verified on Newton.
Passed run:
https://product-ci.infra.mirantis.net/view/10.0_swarm/job/10.0.system_test.ubuntu.fuel_plugin_reboot/233/"
1655289,2017-04-25 14:51:35 UTC,"Reviewed:  https://review.openstack.org/419880
Committed: https://git.openstack.org/cgit/openstack/fuel-plugins/commit/?id=fae06cf5aa86e2d0a1cbc18bee41bfa830b1962f
Submitter: Jenkins
Branch:    master"
1655289,2017-01-13 10:45:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419880"
1655289,2017-01-10 10:55:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/418327"
1655289,2017-01-11 18:45:37 UTC,"Reviewed:  https://review.openstack.org/418327
Committed: https://git.openstack.org/cgit/openstack/fuel-plugins/commit/?id=6a1ae7f5204dadcdc5326c668c09ca5840bd5c7e
Submitter: Jenkins
Branch:    master"
1655289,2017-01-12 08:55:17 UTC,Test is passed on 9.2 snapshot #748. Passed run: https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.fuel_plugin_reboot/169/testReport/
1655295,2017-01-11 09:11:37 UTC,http://lists.gnu.org/archive/html/bug-gnu-emacs/2016-12/msg01268.html
1655295,2017-01-11 10:15:21 UTC,https://github.com/ipython/ipython/issues/9816
1655295,2017-01-12 19:38:19 UTC,https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24223
1655298,2017-01-25 13:25:20 UTC,As commented in Bug #1647204 I believe that this should be fixed with https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=a98951a30a6ae603ffac4ec8c5168aa6d1019933
1655298,2017-01-25 17:30:52 UTC,"On 25/01/17 13:25, Andre Heinecke wrote:

> As commented in Bug #1647204 I believe that this should be fixed with
> https://git.gnupg.org/cgi-
> bin/gitweb.cgi?p=gpgme.git;a=commitdiff;h=a98951a30a6ae603ffac4ec8c5168aa6d1019933
>
"
1655298,2017-01-25 17:50:03 UTC,I'm tempted to dupe this bug over to LP: #1647204 since I think the problem is probably in the gpgme package and not the buildds so much.  Any objections?
1655298,2017-01-25 18:02:31 UTC,"Colin Watson asked me to file this here against launchpad-buildd, so I would rather you did not at least for now."
1655298,2018-01-15 13:48:20 UTC,https://wiki.openstack.org/wiki/LibvirtVirtioRng may be the thing we need to set up here.
1655314,2017-01-20 10:50:20 UTC,Verified on 9.2 SNAPSHOT_ID=#785
1655314,2017-02-09 11:30:00 UTC,"Reviewed:  https://review.openstack.org/422435
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=49d137ab2ebc1b73e2799a11c677abd9c72d06ad
Submitter: Jenkins
Branch:    stable/newton"
1655314,2017-01-19 07:37:33 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/422435"
1655314,2017-04-19 10:27:23 UTC,Verified on Fuel 10 build #1575
1655314,2017-02-27 16:24:26 UTC,This issue was fixed in the openstack/fuel-web 11.0.0.0rc1 release candidate.
1655314,2017-01-18 15:45:17 UTC,"Reviewed:  https://review.openstack.org/421859
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=6810354af1d7bb650eb68a5f9c0156d07e6ff7fd
Submitter: Jenkins
Branch:    stable/mitaka"
1655314,2017-01-10 12:05:10 UTC,"Does not break the functionality, so setting medium priority."
1655314,2017-01-18 09:18:54 UTC,"Reviewed:  https://review.openstack.org/418932
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e8732127dd5c9c6fb8ef0c12c3e1561934bfd296
Submitter: Jenkins
Branch:    master"
1655314,2017-01-11 13:37:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/418932"
1655314,2017-01-11 11:20:57 UTC,"@Dima, I think what it should work by default, priority was changed to High."
1655314,2017-01-18 12:02:40 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/421859"
1655324,2017-01-10 14:02:45 UTC,There is a related problem with the keyboard.
1655324,2017-02-02 13:02:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655324,2017-02-23 19:44:28 UTC,"Affects me on M10 with staging (Ubuntu 16.04, r151)."
1655327,2017-01-11 15:20:01 UTC,"Ironicclient supports local_link_connection field on version 1.19 and above.
Try to use option --ironic-api-version 1.19 and then post here about result please.
Example: http://paste.openstack.org/show/594571/"
1655327,2017-10-23 13:44:40 UTC,"Looking at the comments in #1 the data is there, but you need to use a newer API version; I also checked the ironicclient version in the Newton UCA against the Newton release notes and we're within range so marking this bug a 'Won't Fix'"
1655335,2017-01-10 15:21:15 UTC,"This is related to the latest openstacksdk, falling back to openstacksdk===0.9.10 fixes the issue for me."
1655335,2017-01-10 15:24:41 UTC,"Not sure if is it really a duplicate, but at least closely related to https://launchpad.net/bugs/1654806"
1655348,2018-05-26 15:21:29 UTC,Same here
1655348,2020-09-16 07:24:08 UTC,"I have looked at the problem a bit closer and things is, lightdm works fine for a while, but eventually it has some kernel package problems:"
1655348,2020-09-16 06:56:20 UTC,I have the same issue on ubuntu 20.04 with Ryzen 5 3600 + Nvidia GTX 1050ti. It freezes several times per a day. (kernel: 5.4.0-47). I tried using lightdm instead of gdm3 but it is the same.
1655348,2020-01-16 21:39:04 UTC,"I'm experiencing those hangs too. I have two different machines running different versions of Ubuntu.
One is a Ryzen with a NVIDIA card, using the proprietary drivers. The other is a Intel Coffee Lake, no HT and no discrete GPU."
1655348,2019-08-20 08:04:33 UTC,"@Willem: can you post the output of this command, please?"
1655348,2019-08-19 05:42:56 UTC,for me it stopped happened after changing the PSU (Power Unit)
1655348,2019-08-18 18:20:42 UTC,seeing this on 18.04.3 xubuntu:
1655348,2019-05-31 07:09:36 UTC,"This is on 18.04.2:
Issue solved from my side by not using chromium any longer, since then no system freeze.
The error message in title remains, but obviously causing not a complete system freeze."
1655348,2019-04-24 18:33:51 UTC,the same for me :(
1655348,2018-08-15 18:27:00 UTC,Cf. #1731651.
1655348,2020-09-16 14:01:45 UTC,"Unfortunately ""Error: can't open /lib/modules/"" has nothing to do with any freezes. It is not even  an actual error message. Feel free to file a bug report against the nvidia driver, if that is what you are using."
1655348,2018-01-06 00:38:44 UTC,"I have a similar bug with the same premise, freezes using Google Chrome. They tend to be very random, I only have them during playback."
1655348,2017-09-16 04:21:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655348,2017-07-30 18:03:52 UTC,"I did some more experimentation.  I did not get any system freezes when I shifted down to kernel 4.8 from 4.10, where I got a lot of freezes.  In kernel 4.8 I get the same output when I run sudo systemctl status gpu-manager.service as I reported for kernel 4.10 above.  This might indicate that this output isn't pointing to a system-crashing bug, but I'm not certain.  In 4.8, the game periodically freezes but after a few seconds the screen flashes and suddenly it unfreezes.  My guess is that the same bug that causes the freezing occurs in 4.8 but the system has some code that unfreezes the computer."
1655348,2017-01-24 19:38:12 UTC,"Reopen.
Few minutes ago complete freeze again. Nothing works except hard power off.
Every time there is chromium open and firefox closed.
Firefox freezes only itself, but not the whole system."
1655348,2017-01-26 19:24:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655348,2017-02-04 16:25:38 UTC,Description similar to https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1443364
1655348,2017-05-16 08:42:20 UTC,"I just ran into this critical issue, which has not been solved yet ... Ubuntu16.04"
1655348,2017-01-23 20:38:46 UTC,"Close it for now, reason: Since change of HDMI-cable no freeze."
1655348,2017-06-20 17:31:19 UTC,"Thanks for the advise. There is no kern.0.log, but kern.log.1, maybe you meant xorg.0.log (all attached)"
1655348,2017-07-03 09:06:41 UTC,"Now complete freeze with updated 4.8.0-58-generic, hard shutdown, boot 4.8.0-56-generic, running now 30 minutes without freeze.
It happens so sporadic which makes it almost impossible to find the trigger."
1655348,2017-07-30 03:45:59 UTC,"I may have a similar problem in 17.04 (to which I just upgraded).  When I try to play a video game, the computer completely freezes anywhere from 30 seconds to 40 minutes after I start.  It's done so repeatedly and only when playing this game.  I see very little by way of errors in my logs, but I do get errors about the gpu-manager and dkms like those reported here."
1655348,2017-06-19 15:43:12 UTC,"That error is not really something that could ever cause the system to freeze, as it simply means that we cannot find a dkms module (and therefore gpu-manager can't get information about it). It should be more of a debugging message than an actual error."
1655360,2017-01-10 15:32:54 UTC,All images are has been deployed by https://custom-ci.infra.mirantis.net/job/prepare_env/ job
1655369,2017-01-12 23:34:14 UTC,"I think the key thing to notice is that when ""confinement: classic"" is used we don't process any content interface rules. There is no sharing (no mounting) happening as that would bleed into the host and thus to all the snaps as well (since they share /snap from the host)."
1655369,2018-05-27 18:23:34 UTC,"This doesn't seem to be the case anymore, at least when using classic with plugs in order to reuse content..."
1655369,2017-01-10 15:34:53 UTC,Can you provide a snap/snapcraft.yaml that displays the problem?
1655369,2017-01-11 20:36:25 UTC,"Seeing the same issue, this is the branch im working from:"
1655369,2017-01-11 20:41:25 UTC,"Adam, you are using 'confinement: classic' and therefore have no need for 'plugs'. If you remove your plugs lines, I believe your snap will work. You should only use 'plugs' with 'confinement: devmode' and 'confinement:strict'. (I'll add a check to the review tools to help with this)"
1655369,2017-01-11 20:46:23 UTC,"Florian, the comment to Adam applies to you also, sort of. In general you do not want to use 'plugs' with a 'confinement: classic' snap, but I can see a case of using the 'content' interface with classic in certain situations. For this, the classic apparmor e'x'ec policy needs to make room for the content e'x'ec policy."
1655369,2017-01-11 20:47:08 UTC,"Looking at this more, I think there is enough information to fix this issue, but Florian, please provide a reproducer."
1655369,2017-01-13 15:35:26 UTC,"@Zygmunt, based on this, it sounds like snapd should refuse any interface connections when using classic and it should be documented that if when using 'confinement: classic', you may not use plugs or slots. snapcraft and the review tools can error in this case."
1655374,2017-11-03 16:42:21 UTC,Syncing task from Mir.
1655376,2020-01-15 21:45:34 UTC,"Is this still a priority?
Oliver can you either close this or comment with what features would still be needed to complete this?"
1655376,2020-01-16 09:07:27 UTC,"the idea was to port ubuntu core to an ubuntu touch device and have the whole touch stack living on top. while we do have support for android based kernels and bootloaders, the container providing access to the binary android drivers (graphics, sensors, network etc) via libhybris would still be missing."
1655381,2017-01-10 23:58:14 UTC,"I'm sorry, but even reading the chat log, I'm not sure exactly what's being referred to. Can you be more clear about what needs to be cleaned up?"
1655381,2017-01-11 07:58:54 UTC,We provide documentation for this in step 4 here: http://docs.openstack.org/developer/ironic/deploy/multitenancy.html#configuring-nodes
1655381,2017-01-11 10:18:36 UTC,"Yes, from that description there is absolutely no information whose MAC address it should be. Main unclear thing: where that MAC adddress should be except switch_id? In chassis description? In some obscure option for neutron?"
1655381,2017-01-11 11:08:11 UTC,"That depends on two things the Ironic network driver implementation and the ML2 driver implementation, but in the default Ironic Neutron network driver, local_link_connection is passed to neutron ML2 drivers in the binding_profile to provide information on which switch the baremetal node is plugged into."
1655381,2017-01-11 12:09:12 UTC,"Oh, I see the source of confusion. Some of vendor drivers for ML2 (e.g. Brocade at https://github.com/openstack/networking-brocade) have conception of 'chassis id' and do not use LLDP."
1655381,2017-03-13 04:17:29 UTC,[Expired for Ironic because there has been no activity for 60 days.]
1655381,2017-03-13 15:28:10 UTC,I don't think so.
1655386,2017-01-12 09:37:29 UTC,"I just checked the docs and it should be doable in combination with
module-remap-sink."
1655386,2017-01-10 23:09:17 UTC,"I believe this is possible, but there is no user interface to do this yet. I think module-combine-sink may do what you are after if you are willing to get your hands dirty with pacmd."
1655386,2017-01-12 09:26:20 UTC,"Thanks for the heads-up. I'll give it a try.
GUI interface for that would also be handy, though."
1655387,2017-03-21 13:50:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655387,2017-05-14 16:19:22 UTC,For those who are trying to figure out why this is broken: https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/1633819
1655392,2017-01-18 15:32:32 UTC,"For indicator-network, I mean."
1655392,2017-01-13 01:20:14 UTC,Is there a crash file available?
1655392,2017-01-10 16:33:34 UTC,"This would imply the indicator-network simply crashes or otherwise misbehaves, tentatively adding it to the list of affected projects"
1655392,2017-01-10 16:19:14 UTC,"After a while, the network list is displayed again."
1655395,2018-02-28 00:08:20 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu1
1655398,2019-04-25 17:54:41 UTC,I could reliably trigger the bug in Xubuntu Disco Dingo (xfce4-settings 4.13.4). After installing daily build of xfce4-settings from xubuntu-dev PPA it seems that the bug is gone. Looks like the fix worked. Thanks!
1655398,2019-04-23 23:36:17 UTC,"Happens to me on 1366x768 resolution screenshots, as well as images copied directly from various programs (chromium/firefox right click copy; gimp ctrl+c copy)
Maybe Xorg's max buffer sizes are dependent on memory size?"
1655398,2019-04-24 00:49:58 UTC,"(In reply to Kristian Angelov from comment #10)

> Happens to me on 1366x768 resolution screenshots, as well as images copied
> directly from various programs (chromium/firefox right click copy; gimp
> ctrl+c copy)
> Maybe Xorg's max buffer sizes are dependent on memory size?
"
1655398,2019-04-23 15:07:23 UTC,"(In reply to David Ayers from comment #8)

> I could also only reproduce this with screen shots taken with a sufficiently
> high resolution aka buffer.
"
1655398,2019-04-25 17:55:42 UTC,"(In reply to ondondil from comment #12)

> I could reliably trigger the bug in Xubuntu Disco Dingo (xfce4-settings
> 4.13.4). After installing daily build of xfce4-settings from xubuntu-dev PPA
> it seems that the bug is gone. Looks like the fix worked. Thanks!
"
1655398,2018-12-30 17:20:19 UTC,"Since you read both codebases, are you able to identify what could be cause and perhaps provide a patch?"
1655398,2019-06-23 17:14:57 UTC,"It fails when pasting the clipboard contents into libreoffice Writer too.
Steps to reproduce:"
1655398,2019-06-23 17:18:46 UTC,"I should add that I first reported this bug with the Libreoffice team (https://bugs.documentfoundation.org/show_bug.cgi?id=125785).  Following these steps, 2 responders stated that they were unable to reproduce this anomaly in other desktop environments."
1655398,2019-11-14 04:06:25 UTC,"Affects me, too.  I'm using Linux Lite 4.6.  Been seeing the problem since October 2016.  I use the Select a region option.  Then I select Copy to clipboard, but I cannot paste the result anywhere."
1655398,2019-04-23 10:57:35 UTC,I could also only reproduce this with screen shots taken with a sufficiently high resolution aka buffer.
1655398,2019-04-27 22:56:21 UTC,"I've been seeing this bug for many months (maybe years).  After compiling from source and relaunching xfsettingsd, the bug appears to be fixed!  I'll try it out over the next few days to make sure it's a reliable fix."
1655398,2019-04-23 02:20:26 UTC,For some reason I can't reproduce it now. Old versions of xfce4-settings and xfce4-screenshooter work just fine.
1655398,2018-12-29 16:20:42 UTC,This issue doesnt seem to be limited to just images but generally very large buffers. Copying some very large pieces of text data fails as well.
1655398,2019-04-21 16:51:13 UTC,"Luckily gsd-clipboard code didn't change much since 2011, so finding the fix for this was much easier than I thought."
1655398,2019-04-21 16:47:43 UTC,Andre Miranda referenced this bugreport in commit d7ba62f33965e5ba0601fdb7ee13def9c6e4f1bf
1655398,2019-01-01 12:11:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655398,2018-12-31 17:04:35 UTC,"(In reply to Andre Miranda from comment #2)

> Since you read both codebases, are you able to identify what could be cause
> and perhaps provide a patch?
"
1655398,2018-12-30 20:08:02 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1655398,2018-08-20 22:09:43 UTC,Apparently it is a bug in xfsettingsd (xfce4-settings):
1655398,2017-12-23 18:00:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655398,2017-04-29 00:24:58 UTC,"There are some bugs reported to xfce4-screenshooter about copy to clipboard not working for large resolutions:
https://bugzilla.xfce.org/show_bug.cgi?id=13342
https://bugzilla.xfce.org/show_bug.cgi?id=13395
https://bugzilla.xfce.org/show_bug.cgi?id=10426
https://bugzilla.xfce.org/show_bug.cgi?id=12704"
1655398,2017-01-10 17:01:45 UTC,"This may be a known issue:
https://bugzilla.xfce.org/show_bug.cgi?id=10426"
1655398,2019-04-22 03:18:49 UTC,I'll try to test it today-tomorrow.
1655402,2017-01-16 20:15:50 UTC,I am on OTA-14 and this is what i am seeing
1655402,2017-01-10 17:19:19 UTC,"The current behaviour was implemented according to design. I can see how the fact that exiting fullscreen also brings up the tabs view may be confusing to the user.
However only the bottom edge can be used by apps. The browser wouldn’t have a way of knowing that the top edge has been pulled down. Adding an ubuntu-ux task anyway, in case the design team wants to comment."
1655402,2017-01-10 23:55:26 UTC,Yeah i mean even right now if you pull down it makes the browser exist the fullscreen mode only compared to the pull up gesture.
1655402,2017-01-16 18:30:55 UTC,"I’m not seeing that, at least not on rc-proposed: if I browse to http://blogs.sitepointstatic.com/examples/tech/full-screen/index2.html and tap on the squirrel to make it go fullscreen, then pulling down the indicators bar (partially or completely) doesn't exit fullscreen."
1655402,2017-01-27 16:15:27 UTC,"Right, this is a regression in rc-proposed (most likely introduced with multiple window support), now being tracked by bug #1659884. thanks Adnane!"
1655403,2018-01-25 08:49:39 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1046
1655404,2017-05-16 21:31:00 UTC,The problem is for Linux Mint 18.1 Cinnamon in non-English language.
1655404,2017-05-16 19:52:40 UTC,"I confirmed, too. I have the same problem in Linux Mint Cinnamon 18.1 x64."
1655404,2017-02-01 01:23:56 UTC,confirmed
1655417,2017-01-10 18:24:41 UTC,"An all-machines.log from this deployment, containing logs from all units."
1655417,2017-01-10 18:29:36 UTC,Two problems were found:
1655417,2017-03-16 14:39:53 UTC,Updated worker multiplier to 1.0 and haven't seen this issue since.
1655417,2017-02-11 00:17:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432502"
1655417,2017-01-10 18:22:26 UTC,wsrep data on the master after the restart on mysql/2 that fixed things
1655417,2017-01-17 17:44:25 UTC,the mysql error http://paste.ubuntu.com/23817451/
1655417,2017-01-10 18:20:48 UTC,juju mysql/2 unit log after the mysql restart that fixed things
1655417,2017-02-14 19:25:01 UTC,"Reviewed:  https://review.openstack.org/432502
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=58d3641dee06a553ed4408b47313b18ca1761d2d
Submitter: Jenkins
Branch:    master"
1655417,2017-01-10 18:19:08 UTC,The original hook error
1655417,2017-01-10 18:18:51 UTC,"wsrep data from ""show global status"" on the leader (mysql/0)"
1655417,2017-01-10 18:18:18 UTC,systemctl status
1655417,2017-01-10 18:18:02 UTC,crm status ran on mysql/2
1655417,2017-01-10 18:17:45 UTC,/var/log/* from mysql/2 before the attempts to fix it via service restarts.
1655417,2017-01-10 18:20:03 UTC,"/var/log/mysql/error.log right when issuing the ""service mysql start"" that fixed things"
1655440,2017-11-23 17:00:00 UTC,"Hello Andreas, or anyone else affected,"
1655440,2017-11-28 21:16:14 UTC,"nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the code skipping the test_routes_v6 test in the NetworkManager case. Therefore, it can't possibly pass SRU verification."
1655440,2017-11-29 21:26:33 UTC,"Hello Andreas, or anyone else affected,"
1655440,2017-12-04 14:02:21 UTC,Autopktests still failing for xenial; the test is still not being skipped (we know it won't work on Xenial due to the version of NM shipped there). Marking verification-failed-xenial.
1655440,2017-12-05 09:14:13 UTC,"Hello Andreas, or anyone else affected,"
1655440,2018-01-10 02:35:50 UTC,"The verification of the Stable Release Update for nplan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1655440,2018-01-10 02:34:58 UTC,This bug was fixed in the package nplan - 0.32~16.04.3
1655440,2018-01-10 02:37:12 UTC,This bug was fixed in the package nplan - 0.32~17.04.1
1655440,2019-03-06 01:17:29 UTC,"Curtin will pass the MAAS provided network config to the target.   In netplan format, the accept-ra  configuration is present and this will be passed through to the target system and reflected in the installed system.  I'm marking the curtin portion here invalid.  If curtin does need to do something (for say xenial deployments/ifupdown) then please re-open the task and we'll triage accordingly."
1655440,2019-09-19 14:53:04 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1655440,2017-12-13 20:09:47 UTC,"Verification-done on xenial for nplan 0.32~16.04.3:
Verification-done on zesty for nplan 0.32~17.04.1:"
1655440,2017-11-23 16:10:17 UTC,"Hello Andreas, or anyone else affected,"
1655440,2017-10-06 22:15:28 UTC,"Hello Andreas, or anyone else affected,"
1655440,2017-10-20 18:02:54 UTC,Verification-done on xenial for nplan 0.29~16.04.1:
1655440,2017-10-06 22:07:06 UTC,"Hello Andreas, or anyone else affected,"
1655440,2017-09-15 17:11:05 UTC,"After much thought, I think it's better to keep the default as being as ""open"" as possible, and taking any step we can to provide some working network by default (that is, accepting RAs by default)."
1655440,2017-08-01 13:48:39 UTC,"Uploaded in nplan 0.25 to artful, so it's Fix Released upstream as well..."
1655440,2017-07-17 17:34:57 UTC,This bug was fixed in the package nplan - 0.25
1655440,2017-02-21 04:49:44 UTC,"Indeed, this workaround also breaks the MAAS region itself. ;-)"
1655440,2017-02-20 21:33:55 UTC,"Please avoid disabling IPv6 using ""ipv6.disable=1"". This breaks socket() AF_INET6, which can cripple other software depending on the ability to open sockets() of the AF_INET6 family, even if the system should not use IPv6. It is usually safer to use ""ipv6.disable_ipv6=1"" instead, which will avoid setting addresses to the interfaces but still not break AF_INET6."
1655440,2017-02-16 03:24:52 UTC,"For the record, there is a workaround in MAAS if you want your deployed nodes to be IPv6-free: use the ""ipv6.disable=1"" kernel parameter. This can be done as a tag if you want it to happen on a per-machine basis, or you can use the settings page to create a global default kernel setting."
1655440,2017-01-14 00:09:26 UTC,"Also adding 'netplan'; from what I've seen so far, this is not yet possible to configure."
1655440,2017-01-14 00:08:08 UTC,"This is an Ubuntu default setting, and MAAS does not currently change operating-system-specific settings upon deployment. This could be rendered in a pre-up script for ifupdown, but my understanding is that pre-up scripts will not be available under netplan and networkd."
1655440,2017-11-06 16:56:48 UTC,Verification-done on zesty for nplan 0.29~17.04.1:
1655443,2017-01-17 20:57:49 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1655443,2017-01-17 21:00:16 UTC,This change was made by a bot.
1655447,2017-01-10 20:39:53 UTC,"Note: this is a critical bug for MAAS, since it causes MAAS to crash and become unusable."
1655447,2018-02-07 23:48:48 UTC,"Reopening due to bug #1748031, which was seen when running MAAS with the latest netaddr version in Bionic."
1655450,2017-01-13 08:12:03 UTC,Also confirmed fixed on 4.10.0-041000rc3-generic
1655450,2017-01-13 07:55:09 UTC,This happened after upgrade to 16.10 I believe (unfortunately I am not 100% sure about this). I can confirm that this is fixed using 4.9.2-040902-generic from mainline kernels.
1655450,2017-01-12 15:16:10 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1655450,2017-01-10 21:00:12 UTC,This change was made by a bot.
1655452,2017-01-10 20:55:48 UTC,"Marking 'Opinion' for MAAS, since we may need to patch this in MAAS until a fix lands upstream in `netaddr`. I'd really rather not, if the fix can get into -updates."
1655454,2017-02-06 07:35:39 UTC,Similar problem here:
1655454,2017-02-25 12:31:47 UTC,"Same problem with a Samsung Xpress M2885FW. XSane works without problems by the way, so it seems to be a problem of some backend used by Simple scan (I saw some dependencies on libgusb which is not present in XSane, maybe this is the problem?)."
1655461,2017-01-30 11:08:54 UTC,IIRC the problem is that assertRaisesRegex is not in Python 2..
1655470,2017-01-10 22:16:47 UTC,"Thanks for your feedback :)
Black lines for the cells?"
1655470,2017-01-10 22:36:12 UTC,Yes. Black or other colour you want.
1655472,2017-01-11 02:34:06 UTC,"Currently mobile, but want to make a note that this should probably be a blueprint and we should file separate reports for each tag to accurately track progress here."
1655475,2017-01-10 22:17:08 UTC,"This should probably only be a notification if the window is not focused. If it is focused, a toast might be more appropriate if more feedback is needed"
1655484,2017-01-10 23:16:32 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1655494,2017-02-27 20:29:26 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1655494,2017-01-27 00:51:40 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1655494,2017-01-13 22:17:28 UTC,"Reviewed:  https://review.openstack.org/419217
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=13ba33a57488f5e553dcca7162cc35b58ff0e7f8
Submitter: Jenkins
Branch:    stable/newton"
1655494,2017-01-11 22:13:39 UTC,"Reviewed:  https://review.openstack.org/418590
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bbf9b431ee26e4064278e58bf9c177de48e8719a
Submitter: Jenkins
Branch:    master"
1655494,2017-01-12 00:32:43 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/419217"
1655504,2017-01-11 02:32:30 UTC,"Also noted this affects nova too, pagination works but href links to things like flavours are returned as http links not https"
1655504,2017-01-11 04:02:12 UTC,OK sorry I found the config option for this in cinder:
1655504,2017-03-28 02:32:32 UTC,I believe it's against nova something like following? this is newton version........
1655504,2017-06-27 16:04:34 UTC,"Automatically discovered version mitaka in description. If this is incorrect, please update the description to include 'nova version: ...'"
1655508,2018-01-24 22:33:14 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-838
1655512,2017-01-21 09:56:23 UTC,"Related (and very likely the same root cause): Bug #1555109 ""All font weights are not shown""."
1655512,2020-07-08 07:34:39 UTC,Closing as part of migration to GitLab. Issue is still being tracked in https://gitlab.com/inkscape/inbox/-/issues/283 and https://gitlab.com/inkscape/inbox/-/issues/156
1655512,2018-03-23 03:20:12 UTC,I'm having this problem with the Roboto Font in Inkscape on a Mac. I could choose Roboto thin in Inkscape 0.91 on my Window laptop with no problems. When I choose thin and click Apply it gives me the Light weight.
1655512,2017-01-15 16:06:50 UTC,"Correction: ""Thin"" and ""Normal"" are not in the list."
1655512,2017-01-13 02:38:52 UTC,"Yes, I do. I attached screenshot. I don't know if it matters, but when I manually enter weight variant it works _both_ for ""thin"" and for ""ultra light""."
1655512,2017-01-13 07:49:23 UTC,Thanks for reporting back. I'll try to reproduce on Windows later.
1655512,2017-01-12 08:19:46 UTC,Thanks for taking the time to file a report!
1655512,2017-01-15 15:59:48 UTC,"It's worse on Windows XP (32-bit), with Inkscape 0.92. The thin and medium fonts don't even show in the list."
1655526,2017-01-11 04:03:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/418668"
1655526,2017-03-09 21:29:28 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/418668
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns."
1655526,2017-09-26 22:49:29 UTC,Unassigning due to no activity for > 6 months.
1655528,2017-01-15 16:30:59 UTC,"Reproduced on Windows XP (32-bit), Inkscape 0.92.
While I feel copy-pasting objects should not be affected by layer's opacity (or visibility, see Bug #341995), I'm not sure if it's a bug or a feature. To be investigated."
1655530,2018-06-30 03:09:19 UTC,Fixed in the above commit.
1655530,2018-06-30 03:08:48 UTC,Sean Davis referenced this bugreport in commit 741e4c56d9e88a0a81e681a1e7d3d23bb200cac4
1655530,2018-06-29 09:30:43 UTC,From https://bugs.launchpad.net/catfish-search/+bug/1655530
1655530,2017-01-13 14:26:48 UTC,"Added Python to bug report because of utf-8 decode error.  Someone can correct me if I am wrong.  However, most of the errors I am getting seem to have the .py extension error on them too, so I am wondering if the errors I am getting are extensions of that one error."
1655530,2017-01-14 02:03:35 UTC,"My Catfish doesent search anything from today too.
Im on debian jessie. Catfish 1.2.2
I have a problem with locales, but don't know if that is the problem. all other apps work fine"
1655534,2017-01-23 10:40:23 UTC,"FYI - upstream fix 44f79a0b
Author: Daniel P. Berrange <email address hidden>
lxc: ensure libvirt_lxc and qemu-nbd move into systemd machine slice"
1655546,2017-01-11 08:08:59 UTC,On a very brief glance I can't see an obvious reason why that is not being built.
1655546,2019-11-22 16:39:45 UTC,this bug can be closed.
1655555,2018-04-17 22:22:30 UTC,We see a lot of SIGBUS crashes with Chrome on Linux 4.4.0.*
1655555,2019-06-14 09:13:13 UTC,"Hi,"
1655558,2017-06-27 15:56:50 UTC,"Automatically discovered version mitaka in description. If this is incorrect, please update the description to include 'nova version: ...'"
1655558,2017-01-18 23:08:37 UTC,2016-12-22 07:11:59.884 4011 ERROR nova.virt.vmwareapi.images IOError: [Errno 32] Corrupt image download. Checksum was 4aeaba2179866eb9d9b801d679964dfa expected f28c8836cf65c087e8b43f4c798477f6
1655558,2017-06-27 19:31:04 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1655562,2018-01-24 03:11:51 UTC,thanks for reporting this issue .Not sure os.umask will affect the python process only or the operating system. If the whole operating system. it seems not a good solution.
1655562,2018-01-24 03:12:32 UTC,Do you have any bug link for ironic ?
1655563,2017-12-02 20:44:34 UTC,"It happens even with CLI. http://paste.openstack.org/show/628012/
Looks line a nova bug."
1655563,2018-01-30 23:46:02 UTC,"It looks like this is because the instance 'name' is used as the instance hostname, which is then passed to update the neutron port's dns_name and then that call fails because it is not a valid FQDN. The top-level domain name cannot be all numeric."
1655563,2019-12-29 08:34:32 UTC,"Hi, i assigned this bug to me to contribute for the first time."
1655580,2017-01-13 03:12:11 UTC,Is linux-lts-vivid still supported? I'd expect it to be replaced by linux-lts-xenial by now.
1655584,2018-07-23 10:28:25 UTC,"How did the nvidia package get installed? By default nvidia drivers are not installed, and only pulled in when compatible. Does the metadata on the package claim that it is compatible with your nvidia card - when in fact, it is not? E.g. if you use ubuntu-desktop, and remove the package, is it still offered by additional drivers / ubuntu-drivers?"
1655584,2020-11-24 13:25:18 UTC,I might be experiencing this problem too. I use KVM/QEMU and load vfio-pci driver in place of NVidia driver. nvidia-driver-455 here.
1655584,2019-01-29 23:48:04 UTC,"In case it is not clear, I am using the same VirtualBox raw disk facility as Ross Boylan to use the raw disk partition as a virtual disk."
1655584,2019-01-29 23:38:59 UTC,"I've got the same problem. nvidia-384 was installed (using Software Updater, Settings, Additional Drivers) while booting the partition native (mbr). Natively, all works fine using nvidia-384 but this problem occurs when running in VirtualBox. I had to install nvidia-384 because I could not get a high resolution when booting native using nouveau drivers."
1655584,2018-07-22 21:35:35 UTC,"Something similar happens on a laptop with both an integrated Intel card, and a discrete Nvidia card: systemd-udev keeps loading and unloading the nvidia modules."
1655584,2018-04-29 15:03:38 UTC,Affect me too
1655584,2017-02-01 05:14:52 UTC,"I was able to stop the loop by blacklisting the nvidia modules and restarting the system.
I added /etc/modprobe.d/nvidia-kill.conf, deliberately chose to appear after the existing nvivida conf files in the same directory (not sure if that's essential):"
1655584,2017-02-01 01:45:13 UTC,"I tried
systemctl stop nvidia-persistenced
nvidia-persistenced --no-persistence-mode
nvidia-smi --persistence-mode=Disabled
but none of them helped.  nvidia-smi failed because it couldn't communicate with the nvidia driver."
1655584,2017-01-25 06:00:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655587,2017-04-14 15:33:11 UTC,"This is also fixed in upstream 5.5.5, 5.6.36, 5.7.18 and 8.0.1."
1655587,2018-01-25 08:49:13 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2220
1655591,2017-01-11 12:52:18 UTC,"Vào 11-01-2017 16:55, ""Geert"" <email address hidden> đã viết:"
1655592,2019-05-25 04:17:32 UTC,[Expired for snapd because there has been no activity for 60 days.]
1655592,2019-03-25 14:34:13 UTC,Is there an apparmor denial here? I'll mark this as incomplete for now.
1655594,2017-01-12 19:32:28 UTC,This is the same as https://bugs.launchpad.net/snappy/+bug/1651936 I think?
1655595,2017-04-19 11:03:31 UTC,"Verified on Fuel 10 build #1575
https://product-ci.infra.mirantis.net/view/10.0_swarm/job/10.0.system_test.ubuntu.support_dpdk/213/testReport/(root)/deploy_cluster_with_dpdk_tun/"
1655595,2017-02-27 16:26:11 UTC,This issue was fixed in the openstack/fuel-nailgun-agent 11.0.0.0rc1 release candidate.
1655595,2017-01-17 15:55:03 UTC,"Reviewed:  https://review.openstack.org/421238
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=db0caef9c4db36d8537d0381e83169bf66938d54
Submitter: Jenkins
Branch:    stable/newton"
1655595,2017-01-17 15:54:52 UTC,"Reviewed:  https://review.openstack.org/421237
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=26a7eb39a5105878930502fabd3659b8b4aa66ca
Submitter: Jenkins
Branch:    stable/mitaka"
1655595,2017-01-17 12:06:38 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/421238"
1655595,2017-01-17 12:06:25 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/421237"
1655595,2017-01-17 12:01:37 UTC,"Reviewed:  https://review.openstack.org/418940
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=5ea2e3cc7504eb8386b266ad1227b6d1b4707e42
Submitter: Jenkins
Branch:    master"
1655595,2017-01-11 13:43:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/418940"
1655599,2017-01-18 21:01:02 UTC,Transition work seems to be in progress by mvo
1655599,2017-01-18 23:43:29 UTC,This is in progress at https://github.com/snapcore/snapd/pull/2657
1655599,2017-01-20 14:59:10 UTC,There is also ppa:mvo/ubuntu-core-transition if you want to test a snapd with this feature.
1655605,2017-01-11 13:34:04 UTC,"If there are any relevant log (snippets), please attach them."
1655605,2017-01-11 16:24:08 UTC,I observed the following log fyi.
1655605,2017-01-11 16:38:11 UTC,"The killing metadata process is handled by update_isolated_metadata_proxy. It was added to ensure to spawn metadata proxy process for network with ipv4 subnet added later after ipv6 subnet. However it also kills any metadata proxy process in dhcp namespace for network without isolated network. However the method doesn't get called when network(subnet) is deleted from router. As result, there is no metadata proxy in dhcp namespace to provide VM with metadata service in the scenario described in description. Please correct me if I am wrong. Thanks."
1655605,2017-02-28 15:14:56 UTC,I believe this (Referring to the original bug report) never worked and this is essentially an RFE.
1655608,2019-10-08 07:28:13 UTC,"The problem is very relevant.
How to delete from the console a deleted object from an orphan fragments?"
1655608,2019-10-09 05:42:14 UTC,"Oct  9 05:37:00 proxy4 object-server: 10.0.1.203 - - [09/Oct/2019:05:37:00 +0000] ""GET /cold3/1168/AUTH_ee951409602249bc8d1f2425da8b9635/public/1578/thumbs/thumb_1358327210-img_1458jpg.jpg"" 200 11920 ""-"" ""-"" ""obj-reconstructor
49470"" 0.0007 ""-"" 50176 0
Oct  9 05:37:01 proxy4 account-server: 10.0.1.203 - - [09/Oct/2019:05:37:01 +0000] ""HEAD /md0/848/account%3DAUTH_ee951409602249bc8d1f2425da8b9635"" 404 - ""HEAD http://localhost/v1/account%3DAUTH_ee951409602249bc8d1f2425da8b9635?
format=json"" ""tx987532779b974dcfa9a94-005d9d71fd"" ""proxy-server 46779"" 0.0004 ""-"" 50003 -
Oct  9 05:37:02 proxy4 swift: - - 09/Oct/2019/05/37/02 DELETE /v1/account%253DAUTH_ee951409602249bc8d1f2425da8b9635/container%253Dpublic/object%253D1489/4570836-kdg-_052jpg.jpg HTTP/1.0 499 - internal-terminator - - 70 - tx9875
32779b974dcfa9a94-005d9d71fd - 0.5505 - - 1570599421.745944977 1570599422.296478033 0
Oct  9 05:37:02 proxy4 object-server: 10.0.1.203 - - [09/Oct/2019:05:37:02 +0000] ""DELETE /cold4/543/account%3DAUTH_ee951409602249bc8d1f2425da8b9635/container%3Dpublic/object%3D1489/4570836-kdg-_052jpg.jpg"" 404 70 ""DELETE http:
//localhost/v1/account%3DAUTH_ee951409602249bc8d1f2425da8b9635/container%3Dpublic/object%3D1489/4570836-kdg-_052jpg.jpg"" ""tx987532779b974dcfa9a94-005d9d71fd"" ""proxy-server 46779"" 1.0616 ""-"" 50190 0
Oct  9 05:37:02 proxy4 container-server: 10.0.1.203 - - [09/Oct/2019:05:37:02 +0000] ""DELETE /md0/83/account%3DAUTH_ee951409602249bc8d1f2425da8b9635/container%3Dpublic/object%3D1489/4570836-kdg-_052jpg.jpg"" 404 - ""DELETE http:/
/localhost/cold1/543/account%3DAUTH_ee951409602249bc8d1f2425da8b9635/container%3Dpublic/object%3D1489/4570836-kdg-_052jpg.jpg"" ""tx987532779b974dcfa9a94-005d9d71fd"" ""object-server 50142"" 0.0003 ""-"" 50004 0
Oct  9 05:37:03 proxy4 object-server: 10.0.1.203 - - [09/Oct/2019:05:37:03 +0000] ""DELETE /cold7/543/account%3DAUTH_ee951409602249bc8d1f2425da8b9635/container%3Dpublic/object%3D1489/4570836-kdg-_052jpg.jpg"" 404 70 ""DELETE http:
//localhost/v1/account%3DAUTH_ee951409602249bc8d1f2425da8b9635/container%3Dpublic/object%3D1489/4570836-kdg-_052jpg.jpg"" ""tx987532779b974dcfa9a94-005d9d71fd"" ""proxy-server 46779"" 1.4418 ""-"" 50277 0
Oct  9 05:37:03 proxy4 object-server: 10.0.1.203 - - [09/Oct/2019:05:37:03 +0000] ""DELETE /cold1/543/account%3DAUTH_ee951409602249bc8d1f2425da8b9635/container%3Dpublic/object%3D1489/4570836-kdg-_052jpg.jpg"" 404 70 ""DELETE http:
//localhost/v1/account%3DAUTH_ee951409602249bc8d1f2425da8b9635/container%3Dpublic/object%3D1489/4570836-kdg-_052jpg.jpg"" ""tx987532779b974dcfa9a94-005d9d71fd"" ""proxy-server 46779"" 2.1532 ""-"" 50142 0
Oct  9 05:37:05 proxy4 swift-container: Container sharder cycle starting, auto-sharding False"
1655608,2019-10-09 04:45:19 UTC,"thanks, but does not work
[root@swift bin]# swift-object-info /srv/node/object4/cold0/objects/264/66c/210b9a25e7c9edde5b63e5ca21d0566c/1544188438.18925#12#d.data
Path: /AUTH_ee951409602249bc8d1f2425da8b9635/public/1489/4570836-kdg-_052jpg.jpg
  Account: AUTH_ee951409602249bc8d1f2425da8b9635
  Container: public
  Object: 1489/4570836-kdg-_052jpg.jpg
  Object hash: 210b9a25e7c9edde5b63e5ca21d0566c
Content-Type: image/jpeg
Timestamp: 2018-12-07T13:13:58.189250 (1544188438.18925)
System Metadata:
  X-Object-Sysmeta-Ec-Content-Length: 2883383
  X-Object-Sysmeta-Ec-Etag: 263b0b368ce0278090cd38e77d51778c
  X-Object-Sysmeta-Ec-Frag-Index: 12
  X-Object-Sysmeta-Ec-Scheme: liberasurecode_rs_vand 10+4
  X-Object-Sysmeta-Ec-Segment-Size: 1048576
Transient System Metadata:
  No metadata found
User Metadata:
  No metadata found
Other Metadata:
  No metadata found
ETag: 5f82fe6c740ae5fe0f4392e0618ffeae (valid)
Content-Length: 288580 (valid)
Partition       264
Hash            210b9a25e7c9edde5b63e5ca21d0566c"
1655608,2019-10-08 14:22:27 UTC,if the container is still around you can just issue a normal delete request
1655608,2019-10-09 05:55:42 UTC,"everything works! it I not correctly told arguments, thanks!
[root@cz_swift bin]# kill-obj ""AUTH_ee951409602249bc8d1f2425da8b9635"" ""public"" ""1489/4570836-kdg-_052jpg.jpg"" --config=""/etc/swift/internal-terminator.conf""
('params', 'AUTH_ee951409602249bc8d1f2425da8b9635', 'public', '1489/4570836-kdg-_052jpg.jpg')
('info ', 25, [{'index': 0, u'replication_port': 6201, u'weight': 100.0, u'zone': 4, u'ip': u'10.0.1.203', u'region': 1, u'id': 3, u'replication_ip': u'10.0.1.203', u'meta': u'', u'device': u'md0', u'port': 6201}, {'index': 1, u'replication_port': 6201, u'weight': 100.0, u'zone': 1, u'ip': u'10.0.1.202', u'region': 1, u'id': 2, u'replication_ip': u'10.0.1.202', u'meta': u'', u'device': u'md0', u'port': 6201}, {'index': 2, u'replication_port': 6201, u'weight': 100.0, u'zone': 2, u'ip': u'10.0.1.201', u'region': 1, u'id': 1, u'replication_ip': u'10.0.1.201', u'meta': u'', u'device': u'md0', u'port': 6201}, {'index': 3, u'replication_port': 6201, u'weight': 100.0, u'zone': 3, u'ip': u'10.0.1.200', u'region': 1, u'id': 0, u'replication_ip': u'10.0.1.200', u'meta': u'', u'device': u'md0', u'port': 6201}])
Hasta la vista, baby.
[root@cz_swift bin]# swift-object-info /srv/node/object4/cold0/objects/264/66c/210b9a25e7c9edde5b63e5ca21d0566c/1544188438.18925#12#d.data
Data file doesn't exist"
1655608,2018-08-23 18:03:41 UTC,"the best idea for now is to add some code around where we log that message we would go check handoffs and quarantine if the # of 200's was under some threshold - maybe 1/2 data or 2x parity - like if you have TOO many missing fragments quarantine is safe enough to assume the fragment was dark data instead of hoping ""someday"" the cluster will find enough fragments to rebuild the object to full health."
1655608,2019-11-17 05:31:54 UTC,"hi
After deleting objects, the entire log on all servers is clogged with strings of the form:
Nov 17 05:27:30 cz-swift1 container-server: 10.0.1.201 - - [17/Nov/2019:05:27:30 +0000] ""DELETE /md0/25/AUTH_ee951409602249bc8d1f2425da8b9635/public/1621/546499149-4e4a6521jpg.jpg"" 404 - ""DELETE http://localhost/cold4/1475/AUTH_ee951409602249bc8d1f2425da8b9635/public/1621/546499149-4e4a6521jpg.jpg"" ""tx74d3b1b9219b45ffbd77a-005daa7b87"" ""object-updater 8275"" 0.0004 ""-"" 12690 0
Nov 17 05:27:30 cz-swift1 container-server: 10.0.1.202 - - [17/Nov/2019:05:27:30 +0000] ""DELETE /md0/25/AUTH_ee951409602249bc8d1f2425da8b9635/public/1605/2115067551-pesnyakov---301218---0202jpg.JPG"" 404 - ""DELETE http://localhost/cold2/1650/AUTH_ee951409602249bc8d1f2425da8b9635/public/1605/2115067551-pesnyakov---301218---0202jpg.JPG"" ""txc623d8d14a74438ca88c2-005daaa972"" ""object-updater 19896"" 0.0004 ""-"" 12966 0
Nov 17 05:27:30 cz-swift1 container-server: 10.0.1.202 - - [17/Nov/2019:05:27:30 +0000] ""DELETE /md0/25/AUTH_ee951409602249bc8d1f2425da8b9635/public/417/1478098463-_U5A5686JPG.JPG"" 404 - ""DELETE http://localhost/cold2/904/AUTH_ee951409602249bc8d1f2425da8b9635/public/417/1478098463-_U5A5686JPG.JPG"" ""tx3e62e3ce85ce4d5e93ebd-005daaa8a2"" ""object-updater 19896"" 0.0004 ""-"" 12762 0
Nov 17 05:27:30 cz-swift1 container-server: 10.0.1.200 - - [17/Nov/2019:05:27:30 +0000] ""DELETE /md0/25/AUTH_ee951409602249bc8d1f2425da8b9635/public/1450/1038282845-image00070jpg.jpg"" 404 - ""DELETE http://localhost/cold2/384/AUTH_ee951409602249bc8d1f2425da8b9635/public/1450/1038282845-image00070jpg.jpg"" ""txe403ed28cb6b4d1683182-005dace4d4"" ""object-updater 14943"" 0.0004 ""-"" 12770 0
Nov 17 05:27:30 cz-swift1 container-server: 10.0.1.203 - - [17/Nov/2019:05:27:30 +0000] ""DELETE /md0/25/AUTH_ee951409602249bc8d1f2425da8b9635/public/1488/1670728476-dsc_8754jpg.JPG"" 404 - ""DELETE http://localhost/cold0/1188/AUTH_ee951409602249bc8d1f2425da8b9635/public/1488/1670728476-dsc_8754jpg.JPG"" ""txf225c685707440f5b92a2-005daa2b56"" ""object-updater 31065"" 0.0003 ""-"" 12957 0"
1655608,2017-02-27 19:27:34 UTC,!?  although (2) *would* fix a lot of problems - no one has a time machine?
1655608,2017-02-17 07:40:17 UTC,"I would love (2) to be merged, because I did (1) ;)"
1655608,2017-01-12 06:07:11 UTC,"For (2), I can repro the issue in 2.11.0, so maybe it can be avoid in (1)."
1655608,2017-01-11 20:54:17 UTC,"I knew about this.  I remember chatting with acoles about it (in #openstack-swift on Freenode?) while working on https://review.openstack.org/#/c/385609/ and the other related bugs.  However; I don't remember filing a bug for this, and can't find anything.  So thanks!"
1655608,2017-02-27 19:28:53 UTC,Ideally we can consider this effort as further justification to address lp bug #1655608
1655608,2019-11-18 14:51:36 UTC,"Those messages are from the object-updater, they're coming from async pendings and going to the container layer.  I don't think they're directly related to the issue in this bug report."
1655633,2017-06-06 00:27:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/471174"
1655633,2017-04-25 19:09:27 UTC,"This would be very helpful in development of the Ironic UI. Today, we use patterns in the language used to describe properties to build metadata that is used to control the structure and operation of input forms."
1655633,2017-03-02 15:43:57 UTC,Note that it isn't possible to always have required=True/False because some of them depend on other things. See eg: https://github.com/openstack/ironic/blob/31d889a7c45c63664969c89878e88652697b7949/ironic/drivers/modules/ipmitool.py#L80-L92
1655634,2017-01-13 07:43:12 UTC,"We shouldn't be mentioning the word ""publish"" but instead use the ""push"" and ""release"" primitives as those are the actions exposed to the user. Can we make sure the language is updated in the store errors?"
1655634,2017-01-13 07:43:59 UTC,My comment comes aside from a more specific error code and/or message from the store so a user can figure out what to do.
1655634,2020-03-16 09:42:42 UTC,Just ran into this too. Until I checked my email after building a new snap I didn't realise that it had gone to the queue for review. I tried to use snapcraft to release the build to edge:
1655634,2020-05-26 20:32:17 UTC,"Yeah, that message comes straight from the store, the store is also the entity that knows why it cannot be published."
1655634,2020-05-26 20:38:58 UTC,"This is an InconsistentStateError. Check if that class ships enough state for snapcraft to give more information, or whether we should augment the payload when we raise this error so that the reason is clearer (e.g. is the queue held up by a manual review? what?)"
1655637,2017-01-18 21:00:31 UTC,"The only improvement might be clearer feedback on WHICH checks failed.
For example:"
1655637,2017-01-11 12:28:41 UTC,"For user feedback, it would be more helpful to get the user to try installing the snap locally to confirm it is valid, and escalate to the snapcraft mailing list or bugs.launchpad.net/snapcraft if the snap seems fine."
1655637,2017-01-11 15:39:52 UTC,We've hit the same problem. Local install & testing works fine.
1655637,2017-01-18 19:13:03 UTC,"Hello,"
1655638,2019-09-19 15:03:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1655659,2017-05-06 12:04:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655661,2017-01-12 09:09:16 UTC,"Hi,"
1655661,2017-10-16 12:26:21 UTC,Try to update to version 3.17.10 but the problem is still existing. The update interrupts with a CRC error
1655663,2017-02-27 16:26:58 UTC,This issue was fixed in the openstack/fuel-astute 11.0.0.0rc1 release candidate.
1655663,2017-01-13 17:14:17 UTC,"Reviewed:  https://review.openstack.org/418970
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=1c1578b64a5da7f41e74dee35db9a4d3d4f112ed
Submitter: Jenkins
Branch:    master"
1655663,2017-02-07 17:58:58 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430387"
1655663,2017-02-08 10:08:44 UTC,"Reviewed:  https://review.openstack.org/430387
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=3c087854a5e295e7808ea659dd23136623f01e10
Submitter: Jenkins
Branch:    stable/newton"
1655684,2017-04-26 17:52:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655687,2017-02-16 19:37:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655687,2017-01-11 15:49:13 UTC,"I'm adding Oxide to the bug, as the browser chrome is being rendered ok. I also see these strings in the browser log:"
1655687,2017-01-12 01:50:30 UTC,"Yeah it's a general problem with oxide and friends. Not just because the corruption is confined to the browser area, but also because I've seen exactly the same corruption pattern on some systems with Android-x86."
1655687,2017-01-11 15:31:30 UTC,Attaching output of apport-bug for unity8 and webbrowser-app as well as application-legacy-webbrowser-app-.log from ~/.cache/upstart. Let me know if there's any other useful information I can gather.
1655689,2017-03-18 08:57:33 UTC,Thread Id in general log printed as a signed number:
1655689,2018-01-24 22:28:46 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1407
1655691,2017-01-11 15:59:17 UTC,"Sorry, slight cock-up with my first attachment. I managed not to actually remove the stuff before I started the dump. Second, edited, version attached to make things easier."
1655691,2017-01-16 19:29:13 UTC," I highly recommend you report this on the linux mint github, no one on the dev team reads bugs on launchpad"
1655691,2017-02-15 17:48:19 UTC,"Update: this bug also affects the kernels in the 4.8 branch - I've recently tried 4.8.0-34-generic and 4.8.0-36-generic, with the same problem.
I'll follow calexil's advice and find the github to raise this as well."
1655691,2017-02-17 12:30:20 UTC,Also affects kernel 4.4.0-62. I can't find anything on Github which will allow me to raise a bug against the kernel (perhaps I'm not looking in the right place) so can't do that.
1655703,2017-01-11 18:01:00 UTC,"I agree with everything Donagh said: not a security issue, but something that needs to be fixed."
1655703,2017-01-11 20:48:41 UTC,I don't support having a CVE for it.
1655703,2017-01-11 19:17:49 UTC,"The gist looks good to me, thanks John for the quick patch."
1655703,2017-01-11 19:02:57 UTC,Here's a quick-and-dirty couple of patches that clean this up. The first is just removing the auth token and synk key from logs. The second removes other stuff which doesn't seem too helpful and can fill up logs.
1655703,2017-01-11 18:49:36 UTC,"I forgot to link to our taxonomy in comment #5, but it can be found here: https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1655703,2017-01-11 17:44:34 UTC,"Since this is an SAIO environment, it means that tempauth is being used. Hence, not a security issue for OpenStack (where Keystone is used)."
1655703,2017-01-11 18:09:06 UTC,Thank you all for the comments.
1655703,2017-01-11 17:29:30 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1655703,2017-01-11 18:47:35 UTC,"Based on the above comments, this is clearly Class B3 (A vulnerability in experimental or debugging features not intended for production use) in the VMT's report taxonomy, and so does not require further embargo nor any coordinated advisory. I'm switching the bug to public and marking our OSSA task ""won't fix"" to indicate the lack of need for formal vulnerability handling process."
1655709,2017-01-12 05:00:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655709,2018-03-22 22:31:20 UTC,Still in ubuntu 17.10 with nvidia card.
1655711,2017-01-11 17:22:59 UTC,"Thanks for the report.
The fix is here: https://github.com/CanonicalLtd/ubuntu-core-docs/pull/6"
1655716,2017-03-02 15:59:24 UTC,"It seems like juju should retry API calls when they fail.  I am going to re-open as new, but am convinced this is in ""wishlist"" category."
1655716,2017-03-16 15:02:52 UTC,"This issue has been mitigated in landscape-server by setting the worker-multiplier to 1. Still would be nice to see API retries, but with this change we're not seeing the issue in our testing."
1655716,2017-01-16 22:44:11 UTC,It's possible that the performance was degraded due to the bug tat we have discovered and fixed on 2.1 tip: https://bugs.launchpad.net/juju/+bug/1649719
1655716,2017-04-10 15:05:55 UTC,"@John,"
1655716,2017-01-23 19:07:10 UTC,"Discussion with openstack team also raised the need to tune ""worker-multiplier"" on any api service. This charm config option sets the number of worker process per each service to 2x the number of CPUs by default. This will eat a lot of memory on a 12 cpu machine and create way too many workers on a smooshed deployment."
1655716,2019-07-17 06:19:48 UTC,"Hi, I am seeing the same situation on a customer deployment:"
1655716,2017-04-10 14:09:54 UTC,"I thought we already had code at the go-openstack (goose) level to retry requests. I know we implemented support for openstack telling us ""come back again in 30s"" sort of responses. It may be that there is another failure that we need to handle at a different level."
1655716,2017-01-19 23:12:49 UTC,"More debugging today came up with some additional theories. Openstack uses mysql, which ends up getting deployed across three units. In our case, keystone and nova end up on the same physical machines. Mysql is deployed with a default setting for innodb_buffer_pool_size which causes it to think it can allocate up to 50% of memory for it internal buffer pool. This ends up being 50% of the host machines memory, even though it's smooshed together with 6 other services."
1655716,2017-01-12 19:50:17 UTC,"@Anastasia, yes, the 4975.log example was with juju 2.1beta4."
1655716,2017-01-17 13:16:09 UTC,"Although not really surprising, it's not just bootstrap that can fail. Here is a case where kill-controller failed:
INFO lib.juju.environment . . All hosted models reclaimed, cleaning up controller machines
INFO lib.juju.environment . . WARNING discovered API versions: [{Version:{major:2 minor:0} Links:[{Href:http://10.96.21.108:8774/v2/ Rel:self}] Status:SUPPORTED} {Versio
n:{major:2 minor:1} Links:[{Href:http://10.96.21.108:8774/v2.1/ Rel:self}] Status:CURRENT}]
INFO lib.juju.environment . . WARNING discovered API versions: [{Version:{major:2 minor:0} Links:[{Href:http://10.96.21.116:9696/v2.0 Rel:self}] Status:CURRENT}]
INFO lib.juju.environment . . ERROR destroying controller model: destroying storage: listing volumes: Get http://10.96.21.114:8776/v2/0e0b4ae2e6724f4ea42ebd018991d360/volumes/detail: EOF
INFO lib.juju.environment . ERROR
...
RuntimeError: Command ('juju', 'kill-controller', '-y', 'osa-controller') exited with status 1 ()"
1655716,2017-01-12 22:00:10 UTC,"I did some live debugging and found the EOFs appear to be the result of nova getting timeouts from keystone. One of the keystone units was co-located on the same physical machine as the juju bootstrap unit. We've discovered from lp:1655169 that there is intense memory pressure on the bootstrap unit and it's possible that keystone is slow because of swap thrashing. The bootstrap unit was also co-located with mysql, which also has high memory demands. This isn't likely to help."
1655716,2017-01-18 23:07:14 UTC,"There is evidence that this bug is related to lp:1648677. In every example I have of the EOF problem occurring in a history of test runs, I also found lp:1648677. I haven't figured out what the actual connection is if there is one."
1655716,2017-01-12 05:29:46 UTC,We are seeing failures on 2.1b4
1655716,2017-01-12 01:49:16 UTC,"@Francis Ginther,
Please confirm if you are seeing these with 2.1b4?
It would also be nice to confirm if openstack host units are indeed under heavy load or not."
1655717,2017-10-06 17:53:12 UTC,"Additionally as blackboxsw pointed out to me recently the man page says it will default to the previous value, which actually makes sense."
1655717,2017-10-06 18:00:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655717,2017-01-11 18:05:46 UTC,"I opened this just because I hate that right now 'dch -r' writes 'yakkety'.
I'm running zesty, personally that is a better default."
1655733,2017-01-12 15:41:31 UTC,"Reviewed:  https://review.openstack.org/419087
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=0a306b1dc7021ec41b2947e6efa53be7c4075a9c
Submitter: Jenkins
Branch:    master"
1655733,2017-01-12 17:15:55 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/419567"
1655733,2017-01-12 17:16:06 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/419568"
1655733,2017-01-13 13:30:07 UTC,"Reviewed:  https://review.openstack.org/419567
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=c14c0b208bc6766352afe720c9c5efe3f67a6ba9
Submitter: Jenkins
Branch:    stable/mitaka"
1655733,2017-01-13 13:30:16 UTC,"Reviewed:  https://review.openstack.org/419568
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=5e119e08c3c4d885f0ad8c91919b7818fe15b783
Submitter: Jenkins
Branch:    stable/newton"
1655733,2017-02-01 16:45:40 UTC,Verified on snapshot #822 (RC2)
1655733,2017-02-27 16:26:08 UTC,This issue was fixed in the openstack/fuel-nailgun-agent 11.0.0.0rc1 release candidate.
1655749,2017-04-07 13:00:39 UTC,"So.. With unity 8 dead, what are plans for snapping this app? Is it still on? I certainly hope so."
1655749,2017-01-28 11:28:23 UTC,Created a small bounty to motivate you :)
1655749,2017-01-17 20:57:20 UTC,can't wait! :D
1655749,2017-04-07 15:19:56 UTC,"There is a devmode snap, but it is dependant on services (mediascanner2, thumbnailer etc) that Unity8 provided, these would either need to exist (by being bundled maybe?) or replaced with something else. We'll see what happens :-)"
1655749,2017-01-17 19:42:40 UTC,"Please do! This is an awesome app, also on the desktop!"
1655749,2017-01-17 20:18:05 UTC,"@NeoTheThird: the beginnings of a snap have started and are currently waiting for media-hub to fully work within a snap before work can continue on this. Stay tuned, and I agree this is an awesome app!"
1655752,2017-07-02 11:02:37 UTC,thanks a lot for testing!
1655752,2017-06-29 09:23:06 UTC,"Ok, so I downgraded from 0.19.0-1 which I had manually installed from
yakkety, and installed 0.18.0-1ubuntu0.1 from xenial-proposed.  I tried
one clear test so far, and it did not crash.  It also seemed to log in
from wake up quite a bit faster.  It would usually hang for a while
after I entered my password."
1655752,2017-06-28 08:44:08 UTC,great. now enable proposed and test the update
1655752,2017-06-28 07:03:44 UTC,I now know how to reproduce this everytime:
1655752,2017-06-27 20:02:48 UTC,TJ: ping? this is still unverified..
1655752,2017-06-27 15:26:08 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1655752,2017-05-09 18:33:49 UTC,"I'm getting this same crash on ElementaryOS Loki (based on Ubuntu 16.04) with light-locker 1.7.0-2ubuntu1 and xserver-xorg-input-libinput 0.18.0-1.  It is on a Dell m3800 with dual Intel/nVidia graphics setup with bumblebee and nouveau.  I'm pretty sure it happens when I put the laptop to sleep with the external mouse plugged in, then I wake up the laptop without that mouse plugged in.  I happens right after I log into the lock screen."
1655752,2017-04-25 12:02:10 UTC,@TJ
1655752,2017-02-20 18:04:13 UTC,"@Robie: ""It looks like your backport also pulled in upstream commit 116cddba69b37246db564c1ddf772c0144c589f0. Was this intentional?"""
1655752,2017-02-08 15:24:09 UTC,TJ: this is still unverified
1655752,2017-01-25 23:55:22 UTC,"Hello TJ, or anyone else affected,"
1655752,2017-01-25 15:30:04 UTC,It looks like your backport also pulled in upstream commit 116cddba69b37246db564c1ddf772c0144c589f0. Was this intentional?
1655752,2017-01-19 18:29:37 UTC,debian and zesty already has 0.23 which fixed this
1655752,2017-01-18 12:33:37 UTC,"The attachment ""Debdiff containing backported upstream fix"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1655752,2017-01-18 12:30:54 UTC,"I've backported the upstream fix to the Debian/Ubuntu package; Timo, are you able to update the Ubuntu packages for 16.04 + and also apply it to Debian package (I'll try to recall how to send the debdiff via email into the Debian bug tracker)."
1655752,2017-01-12 17:45:37 UTC,The log file shows the input device(s) being removed upon system idle and the attempt to re-attach it failing.
1655752,2017-01-11 21:35:04 UTC,The NULL device bubbles up from
1655752,2017-01-11 20:56:21 UTC,"StacktraceTop:
 libinput_device_config_tap_get_finger_count () from /tmp/apport_sandbox_E5oWhM/usr/lib/x86_64-linux-gnu/libinput.so.10
 xf86libinput_pre_init () from /tmp/apport_sandbox_E5oWhM/usr/lib/xorg/modules/input/libinput_drv.so
 xf86NewInputDevice ()
 xf86libinput_hotplug_device () from /tmp/apport_sandbox_E5oWhM/usr/lib/xorg/modules/input/libinput_drv.so
 xf86libinput_hotplug_device_cb () from /tmp/apport_sandbox_E5oWhM/usr/lib/xorg/modules/input/libinput_drv.so"
1655752,2017-07-03 07:39:50 UTC,"I've been through the suspend cycle a few more times, still no crashes!"
1655752,2017-07-05 14:49:58 UTC,"The verification of the Stable Release Update for xserver-xorg-input-libinput has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1655752,2017-01-25 23:54:43 UTC,"Hello TJ, or anyone else affected,"
1655752,2017-07-05 14:49:54 UTC,This bug was fixed in the package xserver-xorg-input-libinput - 0.18.0-1ubuntu0.1
1655760,2017-01-16 04:46:35 UTC,"<off-topic>
su_v wrote:

> Note also that GTK+/Quartz is not the officially recommended GTK+
> backend for current stable Inkscape releases which all still use
> GTK2
"
1655760,2017-01-11 22:08:39 UTC,"Sorry, comment 2 has a misleading typo (in a C++ context):
- local builds (C11-based)
+ local builds (X11-based)"
1655760,2017-01-11 22:02:47 UTC,"Pressure sensitivity also works with a ""regular"" local GTK+/Quartz build of Inkscape 0.92 on OS X 10.7.5 using GTK+ 2.24.30 (local port, built last year, not up-to-date with MacPorts) and a Wacom Bamboo CTH-470."
1655760,2017-01-11 21:41:33 UTC,Pasting comment originally written in reply to bug #1655758:
1655760,2017-01-11 21:43:35 UTC,"> (Inkscape 0.91 X11 behaves the same.)
"
1655765,2017-01-12 19:33:25 UTC,That image wouldn't be bootable i'm guessing.
1655765,2017-01-12 21:39:11 UTC,Thank you for your reply.
1655768,2017-05-18 08:54:38 UTC,Is it duplicated with 1596658 ?
1655768,2017-05-31 19:30:33 UTC,I think there is a difference in these.  Supporting existing drivers (1596658) involves a shim layer that makes compatibility interfaces available to the drivers.  This bug is about adding the capability to the v2 API.
1655769,2017-01-12 00:33:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419218"
1655769,2017-02-07 09:13:13 UTC,Could you provider the exception Traceback?
1655769,2017-02-07 09:39:10 UTC,"KeyError at /app-catalog/eccff179c46b45d794cf5caca5b35e51/27be7980-b873-40eb-9d61-5a7a857bea63/
'openstackId'
Request Method:	GET
Request URL:	http://172.16.10.20/dashboard/app-catalog/eccff179c46b45d794cf5caca5b35e51/27be7980-b873-40eb-9d61-5a7a857bea63/
Django Version:	1.8.17
Exception Type:	KeyError
Exception Value:
'openstackId'
Exception Location:	/opt/stack/murano-dashboard/muranodashboard/environments/tabs.py in get_instance_and_stack, line 58
Python Executable:	/usr/bin/python
Python Version:	2.7.12
Python Path:
['/opt/stack/horizon',
 '/opt/stack/horizon',
 '/opt/stack/keystone',
 '/opt/stack/glance',
 '/opt/stack/cinder',
 '/opt/stack/neutron',
 '/opt/stack/nova',
 '/opt/stack/murano',
 '/opt/stack/murano-dashboard',
 '/opt/stack/heat',
 '/opt/stack/horizon',
 '/opt/stack/tempest',
 '/usr/lib/python2.7',
 '/usr/lib/python2.7/plat-x86_64-linux-gnu',
 '/usr/lib/python2.7/lib-tk',
 '/usr/lib/python2.7/lib-old',
 '/usr/lib/python2.7/lib-dynload',
 '/usr/local/lib/python2.7/dist-packages',
 '/usr/lib/python2.7/dist-packages',
 '/opt/stack/horizon/openstack_dashboard']
Server time:	Tue, 7 Feb 2017 09:38:16 +0000"
1655779,2017-02-08 04:29:37 UTC,"Strange... it appears to be something in persistent-storage.rules, but I can not see what... the only thing I can see that it runs is scsi_id, and running that myself does not produce this effect."
1655779,2017-12-01 14:28:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655779,2017-02-08 03:55:09 UTC,"I could not reproduce this at first using a loop device, but then I tried scsi_debug.  This can be reproduced with a simple dd if=/dev/zero count=0 of=/dev/sda.  Parted takes care to not needlessly delete and recreate partition dev nodes when they are not modified, but it appears that there has been a regression in udev/systemd that deletes and recreates all partitions on the disk any time the disk is opened for RW access, thus resetting the RO flag, and also triggering needless update events that cause unity to re-add removed drive icons to the launcher."
1655781,2017-11-07 09:48:40 UTC,CVE-2017-16613
1655781,2017-11-21 11:52:50 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882314
1655781,2017-11-21 11:28:41 UTC,https://github.com/openstack/swauth/commit/70af7986265a3defea054c46efc82d0698917298
1655781,2017-11-06 09:37:31 UTC,Swauth stores tokens directly in swift (in object AUTH_.auth/.token_0/AUTH_tkc9ccde1d34c44c82ac1d260ddbd18df0). I think other auth middlewares are not affected.
1655781,2017-11-21 18:31:45 UTC,"I've gone ahead and marked the OpenStack Security Advisory task to Won't Fix. Since swauth isn't an official OpenStack deliverable, this is probably closest to report class C2 for the OpenStack VMT (A vulnerability, but not in OpenStack supported code, e.g., in a dependency): https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1655781,2017-01-12 00:47:36 UTC,"Minor correction to the bug description: swauth is not a deliverable of any official OpenStack project team, it merely shares our Git namespace because its development is hosted within our community infrastructure. We extend use of our developer community infrastructure to any projects within our ecosystem who wish to make use of the same workflows and hosting provided to official OpenStack software."
1655781,2017-01-12 00:43:01 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1655781,2017-03-20 14:36:54 UTC,"I've added swauth as an affected project on this report, hoping their bug team might have some feedback."
1655783,2017-01-18 20:21:10 UTC,"/var/log/syslog on the MAAS node, with just the entries that cover this failed #5040 deployment. Note this is a shared maas server and it will have log entries about other things happening to this node, not just this failed deployment."
1655783,2017-03-17 03:04:19 UTC,Marking this as Fix Committed in 2.1.1 based on comment # 20.
1655783,2017-03-16 14:49:18 UTC,Have upgraded juju2.1.1 for deployments and haven't seen this in a while. Will reopen if we see this again.
1655783,2017-02-17 12:14:12 UTC,Could you please re-try with Juju 2.1-rc2?
1655783,2017-02-02 15:25:42 UTC,"This bug isn't happening frequently enough that we can have all our deployments done with that extra debugging. The extra debugging increases load, makes the deployment take longer and also makes mongo use up more memory. I was hoping that code inspection around the area that makes the link_subnet call to MAAS could yield some results."
1655783,2017-01-31 11:24:00 UTC,"""I don't know why juju wouldn't make this link_subnet call. Maybe it didn't like the response to the first PUT call?"" is likely that Juju ran into some other error before it got to that point, which leaves us trying to infer it from the log files."
1655783,2017-01-31 03:02:08 UTC,"Juju <=2.1b4 all have an issue where if there is an error we'll end up setting it in a place (agent status) that ends up getting overridden with ""agent is not running"" message. I have a patch in the 2.1 branch already that at least moves the error message into machine-status instead of agent status. These aren't in tabular status by default, but you can do ""juju status --format=yaml""."
1655783,2017-01-18 20:29:36 UTC,"juju status, for completeness."
1655783,2017-01-18 20:18:41 UTC,/etc/* and /var/log/* from the controller node. This also has a ps file in the same location with the process listing.
1655783,2017-01-18 18:07:02 UTC,"@anastasia-macmood, this is because the container didn't get networking setup. For some reason, this container has no static IP entry in /etc/network/interfaces or interfaces.d/*. I'm triaging another failed run now."
1655783,2017-01-18 20:13:30 UTC,/etc/* and /var/log/* from inside of the stuck container 1/lxd/1
1655783,2017-01-18 20:12:00 UTC,I think this 1-lxd-1 container became node gweyff in MAAS:
1655783,2017-01-18 19:57:46 UTC,"We have another fresh run where this happened:
http://ci.lscape.net/job/landscape-system-tests/5040/"
1655783,2017-01-17 00:26:08 UTC,"Interestingly, cloud-init-output.log, attached in comment # 3, is reporting these failures:"
1655783,2017-01-13 18:35:59 UTC,I don't have logs from the host because of bug https://bugs.launchpad.net/juju/+bug/1646329. Our log collector script failed because it uses juju ssh/scp and juju gave it the wrong ip to connect to.
1655783,2017-01-13 18:14:41 UTC,Just had another case of this: http://ci.lscape.net/job/landscape-system-tests/4996/
1655783,2017-01-12 19:09:04 UTC,I've hit this a few times also. In all cases it was only the first LXD container to spawn (first time-wise not necessarily container number). All containers spawning seconds later started ok.
1655783,2017-01-18 20:16:08 UTC,/etc/* and /var/log/* from the host (hendel) of the stuck 1/lxd/1 container. Note there is a base-machine-4/var/log/ps-fauxww.txt file with the process listing generated at log collection time.
1655786,2017-02-01 21:31:17 UTC,This bug tracked only for older early < 4.0 release  multi-cluster/multi-dc support.    Not yet verified new knobs/tests on 4.0 and we will open different bug if required for it..
1655786,2017-01-12 00:02:34 UTC,"nsarath@ubuntu-build04:/auto/cores/1655786$ ls -l
total 17408
-rwxrwxrwx 1 nsarath test 15237120 Jan 11 15:59 Ctrl-A-log.tar
-rwxrwxrwx 1 nsarath test  2508800 Jan 11 15:59 Ctrl-A-Utils.tar
nsarath@ubuntu-build04:/auto/cores/1655786$
nsarath@ubuntu-build04:/auto/cores/1655786$ pwd
/auto/cores/1655786"
1655786,2017-01-19 18:19:28 UTC,Targeted starting 4.0
1655786,2017-01-20 18:48:09 UTC,"Hi Sarath,
    As discussed the failures are not vcenter specific but more of setup issue. Can you rerun and let me know if this is still an issue."
1655786,2017-01-27 01:22:39 UTC,"Hi Sachin,"
1655786,2017-03-30 17:31:38 UTC,Fix for multi-cluster support on mitaka committed through #1646680.
1655787,2017-01-21 04:37:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423580"
1655787,2020-05-28 16:18:13 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: master
Review: https://review.opendev.org/423580
Reason: Project retirement"
1655795,2017-01-15 19:46:50 UTC,Thanks for reporting this Vagrant!
1655795,2017-01-18 07:04:10 UTC,"I've noticed two separate issues, one is that `xtigervncviewer -listen` doesn't accept multiple incoming connections; I reported it in https://github.com/TigerVNC/tigervnc/issues/400."
1655795,2017-01-18 13:26:48 UTC,"I remembered that gtk-vnc doesn't have listen support, so it's a no go for now."
1655795,2017-01-23 17:49:48 UTC,further discussion at:
1655798,2017-01-27 14:19:09 UTC,So it did work after adding virtio-scsi attribute to the controller element as expected:
1655798,2017-01-12 09:45:20 UTC,"Update: the kernel module is, in fact, present. It is under drivers/scsi/virtio_scsi.ko instead of drivers/virtio in the linux source tree and, therefore, is in a different directory:"
1655798,2017-01-26 16:46:11 UTC,"That's interesting -- doesn't modprobe (after a depmod has run) find any module by name, regardless of what directory it is in?"
1655798,2017-01-26 19:21:25 UTC,"kiko,"
1655798,2017-01-27 13:55:59 UTC,"I've uploaded busybox, dropbear and lspci static binaries to the VM to make my life easier via bash and ncat on the remote host as the dracut environment is very limited."
1655802,2017-03-27 13:01:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655805,2017-03-22 09:36:59 UTC,"Sorry, I can't give you any comment, because I've no idea what is going on in my computer.
Kind regards
Hans-Dieter"
1655808,2017-02-07 08:47:09 UTC,"I find the mistake is doc::quickstart said,the resource name is incurrent as doc::quickstart show,the resource name glance-endpoints,nova-create-endpoints,neutron-endpoints,cinder-create-endpoints should be change to glance-create-keystone-endpoint-admin nova-create-keystone-endpoint-admin neutron-create-keystone-endpoint-admin cinder-create-keystone-endpoint-admin cinder-create-keystone-endpoint-adminv2.And should be add create user operator like:"
1655814,2017-01-14 08:11:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655814,2017-01-14 08:17:03 UTC,"My Canon CanoScan LiDE 100 has worked out of the box from Xubuntu 12.04 and 14.04, but upon updating to 16.04, it doesn't work, even after adding ppa:rolfbensch/sane-git to my system."
1655814,2017-01-14 08:42:55 UTC,"CORRECTION: Canon CanoScan LiDE 110, not 100, sorry :("
1655814,2017-06-04 15:00:48 UTC,I tested the Canon LIDE 110 on 17.04 zesty and got an error. It used to work on earlier versions.
1655814,2017-07-24 21:15:01 UTC,Any progress with this bug?
1655827,2017-01-12 13:36:12 UTC,so you're saying that pymongo 3.2.1 or older works?
1655827,2017-01-13 06:14:24 UTC,"nope, did not actually went that far with testing, sorry.
we would have to checked that, but eventually, even if what you said is true, library will be upgraded and the code will fail anyway."
1655830,2018-01-25 09:17:38 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1774
1655832,2017-01-12 06:50:54 UTC,Capitalized app names are not supported at he moment.
1655832,2017-01-12 08:04:05 UTC,random thoughts: does snapcraft output error message as we have capitalized app names if that's not supported ?
1655834,2020-09-29 12:49:24 UTC,I think we can close this bug. Core 20 supports this but the motivation has significantly changed and snapweb is gone.
1655834,2020-02-04 09:55:50 UTC,Assigning to mvo for tracking. This bug is fixed with shared effort.
1655834,2019-09-25 19:58:04 UTC,"This bug was reported a long while ago and while snapweb is no longer an actively developed component, the reset functionality is one of the key elements on the roadmap of Ubuntu Core 20. I'm marking it as in progress and moving to the appropriate project."
1655836,2017-06-02 10:39:45 UTC,"------- Comment From <email address hidden> 2017-06-02 06:33 EDT-------
Hi,"
1655836,2017-03-15 06:09:42 UTC,"------- Comment From <email address hidden> 2017-03-15 02:03 EDT-------
Hello Canonical,"
1655836,2017-02-28 12:00:00 UTC,"------- Comment From <email address hidden> 2017-02-28 06:55 EDT-------
What's status of this bug since it is in triagged state ?"
1655836,2017-02-01 09:19:48 UTC,"------- Comment From <email address hidden> 2017-02-01 04:13 EDT-------
Hi,"
1655836,2017-01-12 06:19:29 UTC,Default Comment by Bridge
1655836,2017-01-12 06:19:27 UTC,Default Comment by Bridge
1655836,2017-01-23 17:25:35 UTC,"Steve, please assign to the developer who is working on resolving this issue ?"
1655842,2017-06-30 10:14:33 UTC,"Chris, can you test if this kernel solves your problem?"
1655842,2017-05-22 09:46:18 UTC,linux-raspi2 version 4.4.0.1055.56 that is.
1655842,2017-06-30 08:57:02 UTC,"The bug is still confirmed and not fixed for linux-raspi2 (Ubuntu), 5 months after getting fixed for the main Ubuntu."
1655842,2017-06-16 23:02:53 UTC,@nicholas-hatch - what file system are your disks formatted as?  I was able to stop the OOM's on my ES hosts by moving from XFS to EXT4.  My belief is that there was a memory fragmentation issue with ES and many small files on XFS formatted volumes.
1655842,2017-06-16 22:38:53 UTC,We're still having issues with higher-order allocations failing and triggering an OOM kill for unexplainable reasons. (on 4.4.0-78-generic).
1655842,2017-05-31 20:59:21 UTC,Also observed with 4.4.0-1054-raspi2. I'm now back on 4.4.0-1038-raspi2. I think that one was ok.
1655842,2017-05-24 06:51:37 UTC,I'm seeing oom-killer being invoked despite having 2GB free swap when using the kernel from linux-image-4.4.0-1055-raspi2 version 4.4.0-1055.62.
1655842,2017-05-22 09:41:09 UTC,This is still an issue in the current linux-raspi2 version. Where those changes ported to that kernel?
1655842,2017-03-22 08:06:04 UTC,"I am seeing this issue as well, on Arch kernel v 4.10.4-1"
1655842,2017-04-11 02:06:36 UTC,I also haven't personally encountered any further OOM issues on my home desktop (used daily) with 4.4.0.63.
1655842,2017-04-10 23:28:50 UTC,"Yes, 4.4.0.63 solved our OOM issues (and we had plenty after 4.4.0.59). Ours were all headless server (bare metal and VMs) related though - no desktop usage."
1655842,2017-04-10 14:39:33 UTC,Anybody having successfully tested 4.4.0.63 for OOM-kill issue...
1655842,2017-04-09 19:25:33 UTC,"I have 4.4.0-59 till 4.4.0-71 and 4.8.0-41 till 4.8.0-46 installed on my system and all are affected by this bug. Firefox, Chrome and Netbeans regularly get killed without a warning and for no reason (since I have something like 10GB+ RAM and all 16GB Swap free at the time the process gets killed). Even KDE has been killed a couple of times while the system still had over 6GB RAM and 16GB Swap free."
1655842,2017-04-09 18:17:36 UTC,I was using 4.4.0-21 as reported by `uname -r` which is default in Kubuntu 16.04. The same bug appears on mainline kernel 4.10 too!
1655842,2017-04-03 18:14:59 UTC,This is plaguing Horizon project Pi2 and Pi3 devices running Xenial 16.04.2 w/ kernel 4.4.0-1050-raspi2. From a pi2:
1655842,2017-07-02 12:08:49 UTC,"Sure.
I undid the workaround, installed and booted the kernel and will test it for a few days. I'll keep you posted on results."
1655842,2017-04-11 06:38:16 UTC,"I'd like to emphasise that the OOM problem only happens with KDE. I have several DE installed including Unity, GNOME3, Cinnamon. But none of them caused a OOM, at least I never noticed. But in KDE, most of the time when chrome is opened, it triggers OOM. dmesg tells that, sometimes kwin_x11 invoked the OOM or plasmashell."
1655842,2017-07-05 14:38:29 UTC,"Update: No sign of Out-of-memory errors or kills, after 3 days of testing the 4.4.0-1062-raspi2 kernel. I'll report back again next week."
1655842,2018-01-03 14:18:12 UTC,"You can potentially use numactl to launch the process and set a policy of interleaving allocations between NUMA nodes to avoid these 1 sided allocations.  Tends to happen with servers that make big allocations from a single thread during startup, as commonly seen on mysqld servers and the innodb_buffer_pool for example."
1655842,2017-07-11 17:46:49 UTC,"Mine's also still stable (no OOMs), after running the patched kernel for 9 days, on a Raspberry pi 2 Model B v1.1."
1655842,2017-03-20 15:25:53 UTC,We have been seeing this issue recently as well.  We are running 4.4.0-66-generic #87-Ubuntu - I can attempt to downgrade to 4.4.0-57 but its a large cluster with a lot of data so it may take some time.  Attached a kern.log from this most recent oom.
1655842,2017-11-27 17:35:06 UTC,In our production environment of ~1800 nodes we've seen oom-kill events that looked similar to this bug's pattern  - oom-kills killing large server processes while resident memory was far lower than available physical memory.
1655842,2017-11-21 17:25:29 UTC,"Side Question... Is there something I can specifically look for on a Ubuntu install that would indicate if that kernel has the fix or not. I assume the ""Fix or Not"" indicates are manually triggered and the fix could be out for AWS but not indicated."
1655842,2017-11-21 01:06:39 UTC,We believe that we are experiencing this issue on kernel 4.4.0-1030-aws as well. We recently move from 14 LTS to 16LTS and are now experience oom kills.
1655842,2017-11-01 14:17:11 UTC,"Not sure if it's the same issue, but we had an unexpected OOM with Ubuntu 16.04.3 LTS, 4.4.0-91."
1655842,2017-09-11 16:49:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655842,2017-09-05 12:37:15 UTC,Attached kern.log
1655842,2017-09-05 12:36:32 UTC,"We have found this issue on 4.4.0-92 too.
But only when the systems were put under stress.
Reverting back to 4.4.0-57 resolved it."
1655842,2017-08-22 17:44:40 UTC,"With the sysctl settings provided by Pete (vm.min_free_kbytes = 1000000 and vm.zone_reclaim_mode = 1), we've been running the linux-aws 4.4.0-1028.37 kernel successfully without an OOM killer invocation for about four days now. Previously we would have seen three or more occurrences of this per day, so it's a positive indication."
1655842,2017-08-17 02:29:53 UTC,Attaching dmesg output
1655842,2017-08-17 02:29:01 UTC,We have another case of OOM at one of the host that we upgraded kernel to 4.4.0-89 a week ago.
1655842,2017-08-16 15:42:59 UTC,"> kthreadd invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=0
"
1655842,2017-08-16 15:29:20 UTC,Apologies - the file was inadvertently split by logrotate. I have concatenated the entire contents of kern.log and kern.log.1 into the attached file; these are the only kern.log files in /var/log on the system.
1655842,2017-08-16 15:26:58 UTC,"I have seemingly solved this issue with linux-aws version 4.4.0-1016-aws at the very least.  The specific issue I was seeing was 2nd order allocations failing when OOMKiller triggered.  At the time I was thinking the issue was due to XFS and memory fragmentation with lots and lots of memory mapped files in Elasticsearch/Lucene.  When we moved to EXT4 the rate of oomkiller firing dropped, but did not stop.  We made the following 2 changes to sysctls which have effectively stopped higher order memory allocaitons from failing and oomkiller firing."
1655842,2017-08-16 14:52:18 UTC,"Please, do not cut the logs. Without the ""invoked oom-killer"" line, for example, it's hard to see the gfp flags and allocation order that failed."
1655842,2017-08-16 13:26:14 UTC,"We are also experiencing this issue running linux-aws 4.4.0-1028.37, which tracks Ubuntu kernel 4.4.0-89.112. Our use case is very similar to comment #86 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/comments/86). In our case ElasticSearch 2.4.5 is running under Java 1.8.0_131 with a ~29GB heap; we downsized from 31GB as a troubleshooting effort with no change to the frequency of OOM. The issue also occurs regardless of vm.overcommit_memory being set to 0, 1 or 2."
1655842,2017-08-08 00:30:55 UTC,Hi
1655842,2017-07-08 04:26:41 UTC,4.4.0-1062-raspi2 is looking good - I've had it running for a week without oom-killer being invoked.
1655842,2017-02-10 01:24:05 UTC,@nick-maynard: Why is such a bug unforgivable? You can just boot a previous kernel instead. If you're concerned about availability then don't reboot in the first place unless there's an important security patch.
1655842,2017-03-03 08:29:17 UTC,"Hi Cascardo,"
1655842,2017-01-27 13:53:52 UTC,"The patchset[1] for bug ""LP #1655842"" has been submitted on Jan 24th 2017 and acked by the kernel team on the same day[2]."
1655842,2017-01-27 13:41:55 UTC,"Hi, I am having the exact same issues on a PC with 18GB ram!! kernel 4.4.0-59-generic"
1655842,2017-01-25 16:42:53 UTC,"Hi I'd like to implement Cascardo kernel since I've been having the same issue, though not on all of
the xenial machines running 4.4.0-59-generic which is strange.
Could someone tell how to implement Cascardo kernel without completely messing up my machine."
1655842,2017-01-24 04:22:45 UTC,"Cascardo: we've tried your test kernel, and it looks good - we've seen no OOM problems."
1655842,2017-01-23 04:45:49 UTC,I've had a few armhf systems running cascardo's kernel and so far no sign of the OOM or any other problem with it.
1655842,2017-01-21 10:29:13 UTC,Using Cascardo's kernel fixes the problem for me.
1655842,2017-01-20 18:43:32 UTC,Patched kernel for armhf available here: http://people.canonical.com/~cascardo/lp1655842/linux-image-4.4.0-62-generic_4.4.0-62.83_armhf.deb
1655842,2017-01-20 17:53:11 UTC,I will upload armhf binaries for those kernels and let you know. It's important to try those because they include an alternative solution that we would rather use instead of the one with the reverted patches.
1655842,2017-01-27 14:08:31 UTC,Additional note :
1655842,2017-01-20 16:55:34 UTC,Just a note that Joe's armhf kernel has been working well for me.
1655842,2017-01-19 16:59:58 UTC,I manage a set of build servers for CPU/IO intensive builds using Yocto/OpenEmbedded. Ubuntu 14.04.5 with the 4.4 Xenial kernel. After updating to 4.4.0-59 the builds started failing because of the OOM killer.
1655842,2017-01-18 05:08:03 UTC,"Thanks jsalisbury. We have deployed using your test kernel (from http://kernel.ubuntu.com/~jsalisbury/lp1655842/), and experienced no OOM issues."
1655842,2017-01-17 12:19:53 UTC,"@f-gruenbichler: I already tried to cherry-pick that patch a while ago and it doesn't work because that patch is based on work that isn't in the 4.4.* kernel branch, not even including Canonical's backports from later branches."
1655842,2017-01-13 10:56:47 UTC,"you could also try cherry-picking https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=6b4e3181d7bd5ca5ab6f45929e4a5ffa7ab4ab7f , but that will probably need some more inbetween patches as well.."
1655842,2017-01-12 15:04:22 UTC,I built a Xenial test kernel with the following two commits reverted:
1655842,2017-01-12 07:00:15 UTC,This change was made by a bot.
1655842,2017-02-10 01:07:55 UTC,"Cascardo: Just to be clear, are you looking for verification from anyone in the world, or from specific kernel testers?"
1655842,2017-01-20 11:58:53 UTC,"Can you try the kernel at [1], which includes the patches that are also at [1]?"
1655842,2017-01-30 15:04:56 UTC,"@Gaudenz Steinlin (gaudenz-debian),"
1655842,2017-01-27 20:14:16 UTC,@slashd It sounds really strange to me that I should wait til 20-Feb for a fix for this bug while this is clearly a regression introduced with the latest kernel upgrade. Is there no way to speed things up to fix this regression.
1655842,2017-02-08 10:53:42 UTC,"Hi, Luk."
1655842,2017-02-09 18:48:46 UTC,Who is the saver 4.4.0-57-generic or 4.4.0-63-generic now.
1655842,2017-02-09 18:27:49 UTC,Testing...
1655842,2017-02-09 14:12:22 UTC,"The fix is now available for testing in kernel version 4.4.0-63.84, if you enable proposed[1]"
1655842,2017-02-09 12:12:03 UTC,"If this kernel is not going to hit -updates shortly (i.e. days), can something be done to pull or downgrade the broken kernel? At least revert linux-image-generic to depend back on linux-image-4.4.0-57-generic which doesn't have the issues and will stop more people from upgrading to a broken kernel."
1655842,2017-02-09 12:03:51 UTC,"LTS Ubuntu with -updates shouldn't have this sort of issue - this is, frankly, unforgivable."
1655842,2017-02-08 17:51:36 UTC,"Just by the way - 4.4.0-62-generic has the exact same problem. Even when uninstalling 4.4.0-59-generic, my system at some point auto-updated to 4.4.0-62-generic . Only 4.4.0-57-generic is safe for now."
1655842,2017-02-02 10:59:49 UTC,This is a severe bug. It should be treated a high-priority bugfix that cannot wait 3 weeks.
1655842,2017-02-09 19:04:15 UTC,"kulwinder singh: Either one, but nothing in between."
1655842,2017-02-08 10:33:17 UTC,This bug also appears to affect linux-image-4.8.0-34-generic in 16.04.1 Xenial.
1655842,2017-02-07 01:42:33 UTC,I've been struggling with this bug for nearly a week and only now found this issue. Thanks for fixing it!
1655842,2017-02-05 21:36:31 UTC,As a note: I believe this also affects the armhf kernel 4.4.0-1040-raspi2 for the Raspberry Pi.
1655842,2017-02-03 16:02:49 UTC,@nate Thank you!  You just saved me a lot of hassle as I was about to unpin the 4.4.0-57 kernel and update a bunch of machines on the assumption the fix was in that version.
1655842,2017-02-03 11:10:30 UTC,"This is fixed in 4.4.0-63.84, which will be available in proposed soon."
1655842,2017-02-03 09:27:16 UTC,I could not reboot my machine and the ugly workaround for this issue was to login as root and clear system caches:
1655842,2017-02-03 04:53:41 UTC,"Just as a note for newcomers reading this, I can confirm the bug is NOT fixed in the officially released 4.4.0-62.83."
1655842,2017-02-08 07:38:46 UTC,When this new kernel will be released? This bug is killing our MySQL Servers. Booting old kernels is only a bad workaround. I think a lot of people with busy servers will have a problem.
1655842,2017-02-09 22:02:34 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1655855,2017-01-12 08:15:58 UTC,fix here: https://nav.uninett.no/hg/nav/rev/55b22df20275
1655859,2017-02-18 18:33:34 UTC,"Please submit the output of lspci, iwconfig and nmcli dev."
1655859,2017-05-17 03:14:33 UTC,This issue has moved to GitHub: https://github.com/elementary/wingpanel-indicator-network/issues/28
1655875,2017-01-12 08:54:23 UTC,Distribution is Linux Mint Serena 18.1 Beta
1655883,2017-04-24 11:50:35 UTC,"Related fix proposed to branch: mcp/ocata
Change author: Ivan Kolodyazhny <email address hidden>
Review: https://review.fuel-infra.org/34759"
1655883,2018-10-24 10:58:59 UTC,"Related fix proposed to branch: mcp/1.0/mitaka
Change author: Ivan Kolodyazhny <email address hidden>
Review: https://review.fuel-infra.org/39534"
1655883,2017-05-10 14:43:06 UTC,"Change abandoned by Michael Dovgal <email address hidden> on branch: mcp/newton
Review: https://review.fuel-infra.org/33432"
1655883,2017-04-26 13:02:54 UTC,"Change abandoned by Roman Podoliaka <email address hidden> on branch: 11.0/ocata
Review: https://review.fuel-infra.org/34119
Reason: we do not need 11.0/ocata anymore - use mcp/ocata instead"
1655883,2017-04-24 15:24:05 UTC,"Change abandoned by Ivan Kolodyazhny <email address hidden> on branch: mcp/ocata
Review: https://review.fuel-infra.org/34759"
1655883,2017-04-20 14:47:49 UTC,"Related fix proposed to branch: 11.0/ocata
Change author: Ivan Kolodyazhny <email address hidden>
Review: https://review.fuel-infra.org/34119"
1655883,2017-04-20 14:42:47 UTC,"Related fix proposed to branch: mcp/newton
Change author: Ivan Kolodyazhny <email address hidden>
Review: https://review.fuel-infra.org/33432"
1655883,2017-02-22 07:51:30 UTC,"Reviewed: https://review.fuel-infra.org/31191
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1655883,2017-02-21 18:01:46 UTC,"Related fix proposed to branch: 9.0/mitaka
Change author: Ivan Kolodyazhny <email address hidden>
Review: https://review.fuel-infra.org/31191"
1655883,2017-02-15 13:43:11 UTC,the problem was fixed via https://review.fuel-infra.org/#/c/30880/
1655883,2017-02-15 10:46:32 UTC,"Reviewed: https://review.fuel-infra.org/30880
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1655883,2017-02-14 16:13:28 UTC,"Related fix proposed to branch: 9.0/mitaka
Change author: Ivan Kolodyazhny <email address hidden>
Review: https://review.fuel-infra.org/30880"
1655883,2017-02-14 12:49:54 UTC,"Reviewed: https://review.fuel-infra.org/30825
Submitter: Roman Vyalov <email address hidden>
Branch: 9.0/mitaka"
1655883,2017-02-14 12:20:51 UTC,"Related fix proposed to branch: 9.0/mitaka
Change author: Roman Vyalov <email address hidden>
Review: https://review.fuel-infra.org/30825"
1655883,2017-02-14 11:16:52 UTC,"Reviewed: https://review.fuel-infra.org/30819
Submitter: Alexander Evseev <email address hidden>
Branch: stable/mitaka"
1655883,2017-02-14 11:16:12 UTC,"Related fix proposed to branch: stable/mitaka
Change author: Roman Vyalov <email address hidden>
Review: https://review.fuel-infra.org/30819"
1655883,2017-01-12 14:57:06 UTC,Reopened - we need to figure out how to run cinder unit test with os-brick from downstream repo or package.
1655883,2017-01-12 09:44:01 UTC,"Unit test jobs are using tox to run tests, tox uses pip to install requirements, pip installs requirements listed in requirements.txt and test-requirements.txt (if exists). If (test-)requirements.txt does not have additional info about module source (like git+https://…), then module is installed from PYPI."
1655883,2017-01-12 09:39:32 UTC,"Roman, if we move this bug to 9.3, we have to move https://bugs.launchpad.net/mos/+bug/1653161 to 9.3 too"
1655903,2017-01-13 09:42:53 UTC,"Thank you for the quick fix Adam, appreciate all the work you put into this project!"
1655904,2017-01-16 21:34:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655922,2017-02-14 11:48:08 UTC,"Reviewed:  https://review.openstack.org/433581
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=3aaacb211d6726700ca18a4b9bc43309ceeb5f2d
Submitter: Jenkins
Branch:    master"
1655922,2017-01-17 09:40:19 UTC,"test run of bvt2 with adjusted versions of keystone and python-keystoneclient:
https://ci.fuel-infra.org/job/9.0-community.main.ubuntu.bvt_2/832/console"
1655922,2017-02-14 10:40:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433581"
1655922,2017-02-14 10:40:26 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433580"
1655922,2017-01-17 15:40:24 UTC,"Reviewed:  https://review.openstack.org/421289
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=642e1c09938c23e349d3d301ae985ba793d91322
Submitter: Jenkins
Branch:    stable/mitaka"
1655922,2017-01-17 14:22:56 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/421289"
1655922,2017-01-17 10:44:23 UTC,"run with same venv (http://paste.openstack.org/show/595166/)
https://ci.fuel-infra.org/job/9.0-community.main.ubuntu.bvt_2/835/console"
1655922,2017-01-17 09:17:07 UTC,"@Vladimir, regarding keystone here's situation on mentioned slaves:"
1655922,2017-02-27 16:26:46 UTC,This issue was fixed in the openstack/fuel-main 11.0.0.0rc1 release candidate.
1655922,2017-01-13 15:10:41 UTC,"The root cause is the following - logrotate can't be installed because kickstart file doesn't use additional repos available on ISO (extra-repos/proposed, mos-centos) where the package is located."
1655922,2017-01-13 14:40:10 UTC,I dont understand why our build process is broken ? and how the new version of logrotate was broke the master node?
1655922,2017-01-13 14:34:11 UTC,May I know the reason it's a task for MOS Linux please?
1655922,2017-01-13 14:33:16 UTC,"the problem not related to CI, because this job did not changed during half an year .
and we found the problem 3 days ago"
1655922,2017-01-13 14:26:58 UTC,If CI is broken this in not a problem of fuel qa
1655922,2017-01-13 13:04:45 UTC,It's not a duplicate of https://bugs.launchpad.net/fuel/+bug/1587411
1655922,2017-02-14 12:04:20 UTC,"Reviewed:  https://review.openstack.org/433580
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=18cc389f57b371a2f57925d2d3dd317eb725930e
Submitter: Jenkins
Branch:    stable/newton"
1655922,2017-01-13 19:16:20 UTC,Looks like the isssue is that version of keystone that we have on jenkins slaves on community CI is incompatible with current fuel-qa. Please compare `pip freeze` output in /home/jenkins/venv-nailgun-tests-2.9 virtualenv on ci-slave01.fuel-infra.org (community-ci where we have problems) and on srv114-bud.infra.mirantis.net (product-ci where everything is ok).
1655925,2017-01-13 14:25:40 UTC,This is easily fixed by 'apt-get install distro-info'
1655930,2017-11-12 12:41:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655931,2017-01-13 10:56:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655931,2017-02-23 20:05:32 UTC,"Affects me on M10 with staging (Ubuntu 16.04, r151)."
1655940,2017-01-12 12:07:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/419437"
1655940,2017-01-12 22:21:35 UTC,Thanks harry for raising this. Just confirmed.
1655940,2017-01-16 17:07:22 UTC,"Reviewed:  https://review.openstack.org/419437
Committed: https://git.openstack.org/cgit/openstack/craton/commit/?id=550bc43baa86498f34d11ee377ef1846609b4738
Submitter: Jenkins
Branch:    master"
1655940,2017-01-25 23:50:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/425463"
1655940,2017-12-18 11:05:33 UTC,"Change abandoned by Syed Ahsan Shamim Zaidi (<email address hidden>) on branch: master
Review: https://review.openstack.org/425463"
1655943,2017-01-12 12:59:52 UTC,"14:57 < mardy> rvr: about the latter bug, are you able to verify whether the system-settings is crashing?
14:58 < rvr> mardy: Nope, I can't see any system-settings crash
14:59 < mardy> rvr: I'll move the bug to unity8 then, they can debug the reboot and find the causes"
1655961,2017-02-17 14:52:21 UTC,"Reviewed:  https://review.openstack.org/430928
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=9741cc4ef434fd677e37b99a0aace10515b04b77
Submitter: Jenkins
Branch:    stable/newton"
1655961,2017-02-08 13:54:30 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430928"
1655961,2017-02-08 13:54:41 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/430929"
1655961,2017-01-12 13:46:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419465"
1655961,2017-02-27 16:29:37 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1655961,2017-01-16 08:48:53 UTC,"Reviewed:  https://review.openstack.org/419465
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=4e37655b4ea33e52ef6fb37e3c9671a9d101b858
Submitter: Jenkins
Branch:    master"
1655961,2017-03-10 16:49:10 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/430929"
1655969,2017-01-14 08:37:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1655969,2017-02-20 07:42:07 UTC,This bug was fixed in the package linux - 4.4.0-63.84
1655979,2017-01-12 14:19:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419479"
1655979,2017-01-24 19:24:11 UTC,"Reviewed:  https://review.openstack.org/419479
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bff2030ecea8a1d21e03c61a7ece02f40dc25c5d
Submitter: Jenkins
Branch:    master"
1655979,2017-01-25 09:49:19 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/425087"
1655979,2017-01-27 00:50:59 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1655979,2017-02-11 02:17:48 UTC,"Reviewed:  https://review.openstack.org/425087
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2927ead260d90c44daeff4a1d4917043e5ed7c9d
Submitter: Jenkins
Branch:    stable/newton"
1655979,2017-02-27 20:29:13 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1655989,2017-01-12 16:43:53 UTC,"While we could get away with specifying the arguments in snapcraft.yaml, I agree that it would be cleaner to specify additional arguments in snap-openstack.yaml, alongside other args that are currently passed to the daemon (ie. log files, config files)."
1655989,2017-01-13 12:19:27 UTC,Found another reason for this to be implemented:
1655989,2017-01-13 12:30:01 UTC,"ceilometer-api needs to be snapped as a wsgi process, using uwsgi as we did in the keystone snap - the ceilometer-api standalone binary is deprecated for removal and does not scale in any way."
1655989,2017-01-13 18:02:11 UTC,"James,"
1655992,2017-01-13 14:41:36 UTC,"From IRC:
08:14 < jdstrand> pmcgowan: someone could submit an inprogress interface to at least cut down on the logging. also, I see things in there with network manager-- the unity8-session snap could 'plugs: [ network-manager ]' and then people could connect that interface (or a snap declaration could auto connect it)
08:14 < jdstrand> pmcgowan: making sure that the interface connections are in place will also cut down on the logging
08:15 < jdstrand> it may feel weird that you need to do interface connections with devmode, but if you remember that devmode is for reporting violations against policy, then it makes more sense
08:16 < jdstrand> for reporting violations against policy so that they can be addressed in policy later*
...
08:25 < jdstrand> pmcgowan: updated the snap declaration to have: http://paste.ubuntu.com/23792402/
08:25 < jdstrand> I don't think that will affect refresh, but it will affect new installs
08:26 < pmcgowan> jdstrand, thanks did you make an MR?
08:26 < jdstrand> pmcgowan: for the snap declaration, that is a store reviewer thing. it is live now
...
08:27 < jdstrand> pmcgowan: I'm preparing a PR for the previous revision bug
...
08:28 < jdstrand> pmcgowan: np. if someone wants to send up a PR for at least the slot side of the unity8 interface, we can get to addressing the other denial
"""
1655992,2017-01-13 14:32:33 UTC,Added snap declarations for the plugs in unity8 which will quiet some of these.
1655992,2017-01-13 14:10:31 UTC,"The first denial is because there isn't a unity8 interface that allows the access. Therefore, the access is a policy violation and it is logged (but allowed)."
1655999,2017-01-12 15:09:53 UTC,This needs patch https://review.openstack.org/#/c/410509/ to land first.
1655999,2017-01-31 13:51:12 UTC,Patch: https://review.openstack.org/#/c/427201/
1655999,2017-09-27 08:11:07 UTC,"Change abandoned by James Page (<email address hidden>) on branch: master
Review: https://review.openstack.org/427201
Reason: Abandoning; feedback provided and no updates > 6 months"
1656014,2017-01-12 16:07:10 UTC,"Ok, found a possible workaround.  After boot screen are whack.  Remove HDMI, replace HDMI, rerun script.  Worked at least once."
1656017,2017-09-04 10:48:15 UTC,"Change abandoned by Thomas Bechtold (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/484801
Reason: To late after Pike was released I guess. Sorry.."
1656017,2017-01-27 00:51:17 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1656017,2017-07-18 13:49:19 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/484801"
1656017,2017-01-13 18:53:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420132"
1656017,2017-01-21 01:24:04 UTC,"Reviewed:  https://review.openstack.org/420132
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aa7b6ebbb254f00fcb548832941ca9dbd3996d9f
Submitter: Jenkins
Branch:    master"
1656020,2017-02-20 07:04:55 UTC,https://product-ci.infra.mirantis.net/job/10.0.acceptance.ubuntu.failover_group_1/2/testReport/(root)/hard_reset_primary_controller/hard_reset_primary_controller/
1656020,2017-03-15 07:27:24 UTC,https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.repetitive_restart/210/artifact/logs/fail_error_ceph_partitions_repetitive_cold_restart-fuel-snapshot-2017-03-15_02-36-51.tar
1656020,2017-03-15 11:32:15 UTC,https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.ha_neutron_destructive/211/artifact/logs/fail_error_ha_neutron_haproxy_termination-fuel-snapshot-2017-03-15_05-47-14.tar
1656020,2017-03-15 11:32:24 UTC,https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.ha_neutron_destructive/211/artifact/logs/fail_error_ha_corosync_stability_check-fuel-snapshot-2017-03-15_01-05-35.tar
1656020,2017-03-16 11:35:32 UTC,"This issue is related to pacemaker, it is out of cluster on failed node with message in logs"
1656020,2017-03-16 12:01:59 UTC,https://product-ci.infra.mirantis.net/job/10.0.acceptance.ubuntu.load/6/testReport/(root)/load_ceph_partitions_cold_reboot/load_ceph_partitions_cold_reboot/
1656020,2017-03-28 13:51:03 UTC,"If we look into last snapshot logs, we will see that there was a server reached:"
1656020,2017-03-28 13:55:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450796"
1656020,2017-03-30 09:33:23 UTC,This bug (doubling ntpd service) and it's consequences (flapping ntp peers) is caused because of issue in the testcases.
1656020,2017-03-30 09:42:11 UTC,"In this case, problem with flapping server will stay but masked by other means. So my fix is related to this bug but testcase problems should be fixed by qa team, so I reassign this bug."
1656020,2017-03-30 11:10:36 UTC,"Reviewed:  https://review.openstack.org/450796
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=4da6c0c1116e97f50bca54db4a687717c782531c
Submitter: Jenkins
Branch:    master"
1656020,2017-03-30 13:04:54 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/451807"
1656020,2017-03-30 13:05:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/451808"
1656020,2017-03-30 14:55:16 UTC,"Reviewed:  https://review.openstack.org/451749
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=6d4b22107efca67d62f14d16776503c3e5b3410f
Submitter: Jenkins
Branch:    master"
1656020,2017-03-30 15:23:27 UTC,"Reviewed:  https://review.openstack.org/451743
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=0c0a9359697afa353840f235577e2f6c696e5a94
Submitter: Jenkins
Branch:    stable/newton"
1656020,2018-06-04 07:01:58 UTC,"Change abandoned by Vladimir Khlyunev (<email address hidden>) on branch: master
Review: https://review.openstack.org/451808
Reason: more than 1 year old"
1656020,2017-02-10 13:27:28 UTC,"One more failure is here:
https://ci.fuel-infra.org/job/10.0-community.main.ubuntu.bvt_2/1173/console"
1656020,2019-12-18 17:34:44 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/451807
Reason: This repo is retired now, no further work will get merged."
1656020,2017-03-30 10:24:14 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/451743"
1656020,2017-01-31 13:06:28 UTC,"Swarm 10
https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.ha_neutron_tun/167/console"
1656020,2017-01-13 16:28:14 UTC,"Upstart script was added to fix a bug [1].
If upstart script doesn't needed - just disable it with .override file."
1656020,2017-01-23 13:27:39 UTC,There are no described fail on snapshot #796 SWARM
1656020,2017-01-13 16:17:45 UTC,"Our ntp package contain ntp upstart and systemV scripts, but original package doesn't contain upstart. This breaks our ntp-pacemaker deployment."
1656020,2017-01-16 06:08:42 UTC,https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.services_reconfiguration_thread_2/171/console
1656020,2017-01-16 16:03:30 UTC,also failure in acceptance suite https://product-ci.infra.mirantis.net/job/9.x.acceptance.ubuntu.failover_group_1/33/testReport/(root)/hard_reset_primary_controller/hard_reset_primary_controller/
1656020,2017-01-16 16:11:17 UTC,https://product-ci.infra.mirantis.net/job/9.x.acceptance.ubuntu.network_outage/34/testReport/(root)/block_net_traffic_ceph/block_net_traffic_ceph/
1656020,2017-01-16 16:11:57 UTC,"Since amount of failed cases tag ""swarm-blocker"" was added."
1656020,2017-01-25 14:51:30 UTC,BVT failure: https://product-ci.infra.mirantis.net/view/10.0/job/10.0.main.ubuntu.smoke_neutron/1189/
1656020,2017-01-17 11:21:56 UTC,https://review.fuel-infra.org/#/c/29865/
1656020,2017-01-17 15:26:12 UTC,"Fix proposed to branch: 9.0
Change author: Vladimir Kuklin <email address hidden>
Review: https://review.fuel-infra.org/29900"
1656020,2017-01-17 10:37:31 UTC,"Got this bug on srv20; there is no ""vr-host-ns@if19"" in ""vrouter"" namespace right after deployment:"
1656020,2017-01-17 15:56:59 UTC,"Fix proposed to branch: 9.0
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/29901"
1656020,2017-01-17 19:16:34 UTC,"Reviewed: https://review.fuel-infra.org/29901
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0"
1656020,2017-01-19 06:25:09 UTC,"The same error on 9.2 snapshot #779:
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.ha_neutron_destructive_vxlan/178/testReport/(root)/neutron_l3_migration_vxlan/neutron_l3_migration_vxlan/"
1656020,2017-01-19 06:25:55 UTC,"@Dmitry take a look
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.cgroup_ha/178/console"
1656020,2017-01-19 06:54:01 UTC,http://paste.openstack.org/show/595547/
1656020,2017-01-19 11:33:33 UTC,"There is no 'vr-host-ns@*' interface in 'vrouter' namespace on node-1 and wasn't created during vip migration.
It was found that 'vr-host-ns' interface in 'vrouter' namespace wasn't created after a reboot and the issues is likely in ocf scripts."
1656020,2017-01-19 16:05:19 UTC,"@Dmitry, I have opened new bug for this - https://bugs.launchpad.net/fuel/+bug/1657745"
1656020,2017-01-17 15:54:44 UTC,"https://review.openstack.org/#/q/I0118a3bf33a7450b7dc92a65efd2977b7d9eebda,n,z"
1656023,2017-01-13 14:29:18 UTC,This patch fixes the issue.
1656023,2017-01-13 16:29:56 UTC,"The attachment ""00_session_parse_fix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1656024,2017-01-12 21:24:38 UTC,"I'm not sure how to use the ""systemctl edit"" command."
1656024,2017-01-12 18:24:34 UTC,"Stéphane, thanks for looking into this. Is there a way I can set that by default for any new lxd containers I create, as a workaround?"
1656024,2017-01-12 16:51:10 UTC,"You should be able to use ""systemctl edit"" to set PrivateNetwork=no as a temporary workaround."
1656024,2017-05-10 06:59:56 UTC,I had the same problem using the varnishncsa service:
1656024,2017-01-12 16:49:22 UTC,"Jan 12 16:47:07 xen systemd[7897]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied
Jan 12 16:47:07 xen systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK
Jan 12 16:47:07 xen systemd[1]: Failed to start Hostname Service.
Jan 12 16:47:07 xen systemd[1]: systemd-hostnamed.service: Unit entered failed state.
Jan 12 16:47:07 xen systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'."
1656024,2017-05-10 06:58:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656024,2017-01-12 16:50:18 UTC,Looks like the problem is to do with systemd and it failing to spawn units that have:
1656030,2017-01-18 11:14:27 UTC,"The VMT doesn't usually issue advisory for bug only exposed in the backend network, unless this can be abused by regular user. I propose we treat this as a class C1 report ( https://security.openstack.org/vmt-process.html#incident-report-taxonomy )."
1656030,2017-01-12 23:04:57 UTC,"For details of xml attacks and possible replacement, this package can be referred which mentions about xml related various attack vectors."
1656030,2017-01-18 16:31:45 UTC,"Probably more of a class E unless it can be demonstrated that there is any actual vulnerability exposed (or could barely be class D if there's interest from Cinder in anyone working on a ""safer"" replacement implementation). Also since it's already public I've gone ahead and marked our security advisory task invalid."
1656030,2017-01-12 18:53:55 UTC,This is 100% just me deferring to higher powers in an attempt to either address or eliminate issues raised by bandit.
1656030,2017-01-12 19:06:22 UTC,I've switched the bug to Public Security now so this discussion can continue as publicly as we like.
1656030,2017-01-12 17:37:50 UTC,"This report doesn't include any useful research, just a copy-and-paste report from a static code analyzer. Can you clarify what actual vulnerabilities you've discovered and provide some realistic exploit scenarios? The recommendation to switch to defusedxml has been debated heavily (and rejected) elsewhere in OpenStack as recently as a few months ago: http://lists.openstack.org/pipermail/openstack-dev/2016-September/104630.html"
1656030,2017-01-12 17:28:35 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1656030,2017-01-12 17:42:01 UTC,I agree with Jeremy.
1656031,2017-03-05 11:18:28 UTC,"Где-то на Багзилле уже был подобный репорт... Не помню, чем кончилось..."
1656031,2018-03-28 12:55:26 UTC,"Fixed in this commit:
https://phabricator.kde.org/R37:19e81dd5fb3fbdd8d76be3af206d1e553c3e9961"
1656040,2017-01-18 10:53:37 UTC,"Reviewed:  https://review.openstack.org/421803
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=a4804569eb88dab54182ddffadc64e90b17c91bf
Submitter: Jenkins
Branch:    stable/mitaka"
1656040,2017-03-06 09:54:56 UTC,"Reviewed:  https://review.openstack.org/441817
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=70a8659bebb3a5b37d79db266c2c0150c515ef2f
Submitter: Jenkins
Branch:    stable/ocata"
1656040,2017-03-06 09:54:49 UTC,"Reviewed:  https://review.openstack.org/441818
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=88acc73a3d0e27dd50c09315d271b321151dac3c
Submitter: Jenkins
Branch:    master"
1656040,2017-03-06 08:57:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441818"
1656040,2017-03-06 08:57:34 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441817"
1656040,2017-03-06 08:57:10 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441816"
1656040,2017-01-18 10:37:25 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/421803"
1656040,2017-03-06 09:58:15 UTC,"Reviewed:  https://review.openstack.org/441816
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=e630d48eec1fc854dab983cf076b49d3513688b6
Submitter: Jenkins
Branch:    stable/newton"
1656040,2017-01-18 10:20:45 UTC,@Sam - probably this one https://bugs.launchpad.net/fuel/+bug/1634691
1656040,2017-01-18 10:18:56 UTC,"Fix proposed to branch: master
Change author: Vladimir Khlyunev <email address hidden>
Review: https://review.fuel-infra.org/29914"
1656040,2017-01-17 21:19:01 UTC,could you link the bug of mcollective in the description?
1656040,2017-01-23 13:14:36 UTC,"Reviewed: https://review.fuel-infra.org/29914
Submitter: Roman Vyalov <email address hidden>
Branch: master"
1656046,2017-08-08 22:25:55 UTC,"If you happen to speak German, please also refer to https://www.tabos.org/topic/fb6490-absturz-beim-einrichten/ - which is the developers' official (and I think also the only) support channel."
1656046,2017-01-12 17:26:22 UTC,This might be related to RogerRouter sometimes reporting not to be online because querying wrong network (wln30s instead enp40s or vice versa).
1656047,2017-11-30 09:18:38 UTC,"Reviewed: https://review.fuel-infra.org/37237
Submitter: Dmitry Burmistrov <email address hidden>
Branch: stable/mitaka"
1656047,2017-11-21 12:00:45 UTC,"Related fix proposed to branch: stable/mitaka
Change author: Vladimir Jigulin <email address hidden>
Review: https://review.fuel-infra.org/37237"
1656047,2017-01-23 12:54:42 UTC,"It's not a configuration problem: the docker rally image downloading url is configured here [1]:
docker.io/rallyforge/rally"
1656047,2017-01-13 13:12:07 UTC,Rally docker image is not part of Fuel distribution. Looks like issue with test configuration.
1656047,2017-01-12 17:31:09 UTC,diagnostic snapshot https://drive.google.com/open?id=0B2ag_Bf-ShtTeGhVMEtXSENiQjQ
1656050,2017-02-01 21:50:43 UTC,Fixed in DC++ 0.865.
1656050,2017-01-31 00:49:01 UTC,this is actually easy to reproduce once one understands the causes. :)
1656050,2017-01-21 10:04:27 UTC,That's one way to do it.
1656050,2017-01-21 09:16:53 UTC,Shouldn't a split like that be done using the preprocessor... unless you are absolutely certain that retaining that condition with the new version has no adverse effects.
1656050,2017-01-20 15:29:51 UTC,"Should the check for ""zs.avail_out == 0"" still be kept in case zlib's error policy is changed again in future and for compatibility with older zlib versions? The code can't really be tied to a specific zlib version on Linux."
1656050,2017-01-19 16:29:21 UTC,No errors with a previously failing folder transfer after applying that patch
1656050,2017-01-20 15:24:09 UTC,No errors getting the same filelist from me which still fails without this patch.
1656050,2017-01-17 18:51:28 UTC,"Yeah, it still happens with files as well. The next stable version AirDC++ will be released with zlib 1.2.8 regardless of what happens with this issue."
1656050,2017-01-17 16:28:32 UTC,Until multiple people tried and failed to get my current filelist today. Which is not working so long as I have the compression enabled (with zlib 1.2.11).
1656050,2017-01-15 19:38:46 UTC,Nor have I so far.
1656050,2017-01-15 17:59:33 UTC,I haven't experienced any errors with zlib 1.2.11 yet
1656050,2017-01-13 20:14:39 UTC,"I can confirm similar problems sporadically appearing during transfers between DC++ 0.864 and clients equipped with both zlib 1.2.10 and older versions.
Tested with downloading filelists, always the same transfers with same clients fail while the rest succeed so it probably depends on the data being compressed."
1656050,2017-01-18 23:09:35 UTC,"patch that might work, cooked up by following the deflateParams doc. please test."
1656051,2017-01-19 15:13:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422686"
1656051,2017-01-19 18:33:58 UTC,"Reviewed:  https://review.openstack.org/422686
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a194157cd9e6cfcf03610c68b86e8bc34545c14d
Submitter: Jenkins
Branch:    master"
1656051,2017-01-27 00:53:41 UTC,This issue was fixed in the openstack/horizon 11.0.0.0b3 development milestone.
1656053,2017-01-19 08:29:04 UTC,"Reviewed:  https://review.openstack.org/420648
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=1474535127b218c41ad470d07657e42a955304ef
Submitter: Jenkins
Branch:    master"
1656053,2017-01-25 09:58:26 UTC,Verified on 9.2 snapshot #801.
1656053,2017-01-18 17:26:46 UTC,"Reviewed:  https://review.openstack.org/420771
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=164d3179dd9ef0d668482e4bf1af6671d9807f71
Submitter: Jenkins
Branch:    stable/mitaka"
1656053,2017-02-27 16:29:18 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1656053,2017-01-16 11:15:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420648"
1656053,2017-01-16 15:44:23 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/420771"
1656055,2017-01-13 09:29:33 UTC,"Other data, It's the other_config field in the open_vswitch table."
1656055,2017-01-12 18:09:35 UTC,that's a legit concern if there's some data from previous deployment
1656055,2017-02-06 19:08:06 UTC,"yes this is an artifact of the db based init.
if you install with ovs-dpdk and then unstack and stack with kernel ovs it fails to delete the entries
in the Open_vSwitch table."
1656061,2017-01-23 00:33:22 UTC,This bug was fixed in the package wicd - 1.7.4+tb2-3
1656061,2017-01-12 19:27:59 UTC,"Hi,"
1656075,2017-01-12 19:17:22 UTC,In this case the keystone stuff was done after nova-compute was started:
1656075,2017-01-19 17:42:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422780"
1656075,2017-01-28 02:16:44 UTC,"Reviewed:  https://review.openstack.org/422780
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4dbc0ddc740881a409085feeca2a1771a9ea95f3
Submitter: Jenkins
Branch:    master"
1656075,2017-02-03 19:08:34 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc1 release candidate.
1656082,2018-08-23 15:47:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656082,2018-08-23 16:58:44 UTC,"A-and after upgrade to Bionic 1.1.15~ds0-11.1.15~ds0-1 exits correctly all the time.
Looks like it had a problem with some library that got updated to handle <whatever it does> better?"
1656096,2019-01-22 13:39:45 UTC,Should we close this? or is this still needed?
1656096,2017-06-27 18:09:29 UTC,"Reviewed:  https://review.openstack.org/419648
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b30bdb6f8ed7a041d53849cd56718afd08f4bb98
Submitter: Jenkins
Branch:    master"
1656096,2019-01-22 14:27:30 UTC,It's up to you and the OOO team. I do not plan to work on it.
1656115,2017-02-22 07:47:27 UTC,"Hi Sachin,"
1656115,2017-02-06 06:56:57 UTC,Hi Sachin
1656115,2017-01-21 01:43:00 UTC,"I logged in to the setup and I found that autorestart is set to false on controller-1, while it is set to true in controller-2 and controller-3. As a result, once the process fails, it is not restarted by supervisord on controller-1. Did someone change this setting on controller-1?"
1656115,2017-01-14 01:12:36 UTC,Observed following trace in schema log
1656115,2017-01-13 00:01:55 UTC,The logs are copied to
1656115,2017-01-21 01:28:36 UTC,"This looks like cassandra issue. Did you check cassandra logs? Also, how do I access sp-ulnx2?"
1656116,2017-01-13 17:34:32 UTC,monitor-count in ceph-mon is set to 3:
1656116,2017-01-13 17:52:48 UTC,"No, this run isn't live anymore. All we have is essentially juju status and /var/log/** and some of /etc/** from all units."
1656116,2017-01-13 17:41:35 UTC,Beisner helped me find that the mon count is indeed 3.  The other thing that would prevent bootstrapping is if the mon relation failed to query the other related mons.  Do you have the relation data showing from each mon's perspective how many other related units it sees?  That would be really helpful in narrowing this down.
1656116,2017-03-30 10:53:07 UTC,"To be honest the mon's won't even try to bootstrap until they can see each other over the relation data, so I suspect this is something network-ish with regards to LXD containers in Juju 2.1.x"
1656116,2017-01-13 13:09:10 UTC,"Fwiw, I get 404 trying:  https://ci.lscape.net/job/landscape-system-tests/4981"
1656116,2017-03-30 10:58:24 UTC,Which is odd:
1656116,2017-03-30 11:01:23 UTC,"So it looks like when the config-changed hook ran on each unit, none of the units where actually the leader - I've never see this behaviour from either the charm or juju."
1656116,2017-01-13 17:25:23 UTC,Was the `monitor-count` setting in ceph-mon's config.yaml set to something other than the default of 3?  I don't see any log messages saying that the monitors were bootstrapping.  The only thing the prevents that is setting the monitor-count.
1656116,2017-03-30 10:57:08 UTC,Might be pertinent:
1656116,2017-01-13 15:55:17 UTC,"Thanks for the added info, I believe that will be enough for the storage charm folks to triage."
1656116,2017-01-12 22:57:33 UTC,Adding autopilot-log-analyser so that we remember to write an analyser issue for this.
1656116,2017-01-13 14:41:37 UTC,"Sorry, can't show you charm config as the deployment isn't live anymore. We want to include that data in our log collection script eventually."
1656116,2017-01-13 13:46:40 UTC,Please also attach the corresponding ceph-osd.tar.gz log archive.  Thanks again.
1656116,2017-01-13 13:43:13 UTC,@ahasenack - in that case can you paste the resultant charm config for ceph-*?  I'm not able to derive exactly what those values are from the code.
1656116,2017-01-13 13:31:52 UTC,"The ceph-* charm config is trickier, as it's indeed code that does that."
1656116,2017-01-13 13:28:02 UTC,"This one in json, so you can parse it with python and print or search whatever you want"
1656116,2017-01-13 13:07:09 UTC,"@fginther - can you please provide a full juju status, including tabular?  Trying to understand the placement, metal vs container, etc."
1656116,2017-03-30 11:01:44 UTC,Was this a one-off error or has this problem been seen multiple times?
1656116,2017-01-13 14:48:03 UTC,"ceph-{mon,osd,radosgw} logs"
1656116,2017-03-30 11:09:16 UTC,Definitely something todo with wonky leadership election:
1656121,2017-02-27 17:15:06 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1656121,2017-02-27 17:16:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1656121,2017-02-23 15:00:17 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1656121,2017-02-02 08:26:22 UTC,"Thanks, I'll check this kernel ASAP"
1656121,2017-03-02 08:46:11 UTC,This bug was fixed in the package linux - 4.8.0-40.43
1656121,2017-01-19 07:00:11 UTC,Hey
1656121,2017-03-28 09:25:49 UTC,Not fixed because we had to revert the commits due to various regressions.
1656121,2017-03-29 23:13:19 UTC,This bug was fixed in the package linux - 4.8.0-45.48
1656121,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1656121,2017-02-02 08:16:33 UTC,I have kernels that fix the complain error from bug #1648903 in
1656121,2017-04-24 14:11:40 UTC,This bug was fixed in the package linux - 4.8.0-49.52
1656121,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1656121,2017-02-01 19:17:18 UTC,"I wonder if the nsenter denial is related to bug #1648903. Ie, complain mode blocked 'ip netns list' (etc). You should be able to workaround that be adjusting the profile to allow nsenter so that it is allowed and not affected by complain mode."
1656121,2017-01-19 00:39:21 UTC,"Incidentally, the pastebins from comment #6 don't show the ""Failed name lookup - disconnected path"" -- based on what's visible there, I'm curious if this is just an incomplete profile?"
1656121,2017-02-01 17:17:17 UTC,This script can be used to reproduce the problem and collect detailed logs.
1656121,2017-01-12 23:14:09 UTC,Please forgive me for making a mistake above:
1656121,2017-01-13 02:57:59 UTC,This looks like the child null profile is not inheriting the control flags from its parent
1656121,2017-01-18 10:39:54 UTC,Alright 2nd kernel to test
1656121,2017-01-18 13:05:48 UTC,Testing in progress. I'm already switching apparmor debugging on as requested before. I should have results in 15-20 minutes.
1656121,2017-01-17 15:25:44 UTC,"I've tested this kernel (in fact, automated testing for this kernel and issue) and I think it would be best if we worked on IRC interactively to figure out what's next. Please ping me on IRC if you can."
1656121,2017-02-01 17:48:35 UTC,The test kernel is not fixing the issue. The actual error seems to be entirely different now (as if we could not execute the test application (nsenter).
1656121,2017-01-19 09:40:22 UTC,Sorry I didn't get spread setup today.
1656121,2017-01-19 11:45:36 UTC,Both of those were set as you instructed. I'll re-investigate to see what we're missing.
1656121,2017-02-01 17:15:48 UTC,I wrote a simple script that reproduces this issue. Atteched to the bug now.
1656121,2017-01-18 13:44:23 UTC,"Tests failed, this is the collected data:"
1656142,2017-11-06 16:28:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656148,2017-01-22 01:20:14 UTC,"Change abandoned by Leehom Li (<email address hidden>) on branch: master
Review: https://review.openstack.org/423720"
1656148,2017-01-22 01:21:02 UTC,"Change abandoned by Leehom Li (<email address hidden>) on branch: master
Review: https://review.openstack.org/423722"
1656148,2017-01-22 01:12:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423722"
1656148,2017-01-22 01:09:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423720"
1656148,2017-01-13 01:35:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419703"
1656150,2017-01-30 05:06:56 UTC,Many thanks Georgy
1656150,2017-01-31 08:56:46 UTC,"Ok, lets start with path issue first. On master node edit /usr/share/fuel_bootstrap_cli/files/xenial/etc/rc.local add"
1656150,2017-02-01 01:40:19 UTC,"So, after rebuilding the bootstrap, the export is correctly in the
/etc/rc.local but still mcollective does not start."
1656150,2017-02-01 06:06:51 UTC,"Aha, so it seems the depending on timings (its different on VMs and the real hardware) rc.local maybe launched without proper PATH variable set. I suspect that something similar happens on one of our test labs.
Thinking about the hard part - systemd ""Connection timeout"""
1656150,2017-02-07 09:15:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430138"
1656150,2017-02-09 09:49:50 UTC,"Reviewed:  https://review.openstack.org/430138
Committed: https://git.openstack.org/cgit/openstack/fuel-agent/commit/?id=5c612875a6881b1c93c4dac04759f9e806a3ee1d
Submitter: Jenkins
Branch:    master"
1656150,2017-01-30 04:31:23 UTC,Sorry I'm a bit busy - we are releasing 9.2. I believe I'll be back to the issue tomorrow.
1656150,2017-03-10 10:03:16 UTC,"Here is the link to the ISO.
http://seed.fuel-infra.org/fuelweb-iso/fuel-10.0-community-1401-2017-03-09_05-14-00.iso.torrent"
1656150,2017-02-15 13:41:50 UTC,"Georgy,"
1656150,2017-02-16 05:24:47 UTC,"Luca,"
1656150,2017-03-08 09:54:25 UTC,I'm having a similar problem with fuel-community-10.0.
1656150,2017-03-08 11:01:24 UTC,I also notice a very high CPU load in the hosts after running /etc/rc.local:
1656150,2017-03-09 06:22:03 UTC,"Burkhard, could you please try the latest ISO from here https://ci.fuel-infra.org/view/BVT/job/10.0-community.all/1401"
1656150,2017-03-10 09:33:05 UTC,"There's no downloadable iso on that site, so I used the corresponding git checkout for building the image myself (second chunk of yumdownloader patch does not apply and isolinux pathes needs to be adopted for ubuntu 16.04, but that's a different story...)."
1656150,2017-02-09 14:15:39 UTC,"Reviewed:  https://review.openstack.org/431414
Committed: https://git.openstack.org/cgit/openstack/fuel-agent/commit/?id=9526f477d81eff85f45e3279bc09778bfe3df930
Submitter: Jenkins
Branch:    stable/newton"
1656150,2017-01-30 00:40:54 UTC,"Is there any news on this or a workaround I can use to make the deployment work?
If I run /etc/rc.local manually it can sometimes fix the problem though after it is run, the deployment fails on each node it has been run."
1656150,2017-02-09 09:51:43 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/431414"
1656150,2017-01-24 03:11:02 UTC,"let me know if you need more logs for this issue, I kept some servers
aside just to investigate on this problem while in bootstrap."
1656150,2017-01-17 01:08:16 UTC,Here the FUEL Snapshot
1656150,2017-01-18 05:42:27 UTC,"From what I see in logs rc.local started but, for some reason mcollective unmasking part wasn't run. So, it looks like it hung somewhere in the middle. To understand where it could have happen I need to more files which are not a part of the snapshot: /etc/ntp.conf and /etc/send2syslog.conf."
1656150,2017-01-18 06:54:27 UTC,"Hm... It looks like it hasn't been executed at all. BTW, what is in /etc/rc.local on failed nodes?
P.S. What ISO are you using - I want to try to reproduce the whole thing."
1656150,2017-01-18 07:02:25 UTC,"[root@fuel ~]# cat /etc/ntp.conf
# ntp.conf: Managed by puppet.
#
# Enable next tinker options:
# panic - keep ntpd from panicking in the event of a large clock skew
# when a VM guest is suspended and resumed;
# stepout - allow ntpd change offset faster
tinker panic 0 stepout 5"
1656150,2017-01-18 07:11:59 UTC,"[root@fuel ~]# ssh 146.118.52.62
root@bootstrap:~# cat /etc/rc.local
#!/bin/sh -e"
1656150,2017-01-18 10:45:57 UTC,"Does running /etc/rc.local manually afterwards fixes the problem?
It must fix mcollective config, unmask mcollective.service and then in ~30 sec. nailgun agent must successfully start mcollective. Also /etc/send2syslog.conf must appear.
To understand where it fails I think it would be usefule to run it as bash -x /etc/rc.local."
1656150,2017-01-18 06:01:06 UTC,"[root@fuel ~]# cat /etc/ntp.conf
# ntp.conf: Managed by puppet.
#
# Enable next tinker options:
# panic - keep ntpd from panicking in the event of a large clock skew
# when a VM guest is suspended and resumed;
# stepout - allow ntpd change offset faster
tinker panic 0 stepout 5"
1656150,2017-01-20 07:54:22 UTC,"Did, at least /etc/send2syslog.conf appear?
Anyway lets figure what are those error messages:"
1656150,2017-01-20 08:05:07 UTC,"It did,"
1656150,2017-01-20 08:21:53 UTC,"sorry, I meant bash -x fix-configs-on-startup. But before that:
1. Is mcollective unmasked now?
2. What is in cat /etc/mcollective/server.cfg ?"
1656150,2017-01-23 00:19:14 UTC,in the /etc/mcollective/server.cfg
1656150,2017-01-23 09:58:39 UTC,"> The script, in the ""problematic boxes"" is not ""linked"" properly and I have to execute it with the absolute path /usr/bin/fix-configs-on-startup
That puzzles me a bit - if /usr/bin is not in PATH, something must be broken badly. Figuring what could have affected that.
"
1656150,2017-01-20 00:42:08 UTC,"This is the output of ""bash -x /etc/rc.local"""
1656150,2017-01-25 03:02:01 UTC,"I actually got a problem even in the nodes from the hardware models that
seemed always ok."
1656152,2017-01-13 02:09:16 UTC,"Based on tests with archived builds (on OS X):
- not reproduced with lp:inkscape 11783 <= rev <= 11878,
- reproduced with lp:inkscape rev >= 11882,
- reproduced with Inkscape 0.91 r13725,
- reproduced with Inkscape 0.92.0 r15299,
- reproduced with lp:inkscape/0.92.x rev 15315;
it seems that this behavior is present as described since the initial implementation of the drag&drop support to insert a symbol into the current document:
https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/changes/11882"
1656152,2017-01-13 04:47:40 UTC,Reproduced with Inkscape 0.92+devel r15415 on Ubuntu 14.04.5 LTS.
1656152,2020-08-07 12:05:43 UTC,Closing as part of bug migration to GitLab. Tracked in https://gitlab.com/inkscape/inkscape/-/issues/1197 and fixed by 58c8b25db30516ad62de19d62a56475cd8ea2345 (1.1-dev) fix #1197 Ignore drag&drop outside canvas
1656155,2017-02-18 22:03:26 UTC,I did fresh install.
1656155,2017-02-26 19:32:43 UTC,"Hi. Installing Ubuntu 16.04, installing INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.4 didn't help. Except one."
1656155,2017-02-23 23:47:39 UTC,"You got some error in the boot log about an unknown stepping function, right? Then an older, faulty version of the Intel driver loaded in its place?"
1656155,2017-02-23 21:31:24 UTC,"Hi, again. That I wrote above didn't help. Super sad..."
1656155,2017-02-22 00:13:31 UTC,"Hi, it seems installing this `intel-graphics-update-tool_2.0.2_amd64.deb` tool helps me (Ubuntu 16.04)"
1656155,2017-02-19 13:27:11 UTC,After I switched off GPU in Chrome there was not freezing in Chrome. But I left laptop for a night and in morning I found that he was `frozen`.
1656155,2017-02-18 03:21:58 UTC,"@V: Did you upgrade to 16.10, or did you do a fresh install? Check what kernel version you ended up with. If less than 4.6, get a fresh install image of 16.10 with kernel 4.8 (or else follow a recipe for upgrading your kernel)."
1656155,2017-02-18 00:58:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656155,2017-01-17 22:17:44 UTC,More info (sort of):
1656155,2017-01-15 22:58:42 UTC,"FindRightPackage suggests ""kernel DRM driver (linux package)"". Since similar bug reports seem to be clustering on Intel CPUs that have on-board GPUs, I can only guess that it means the Intel-specific libdrm. However, I wonder about the i965-va-driver on my Kabylake i5-7200u."
1656155,2017-01-15 22:27:02 UTC,"According to FindRightPackage, ""System freezes completely"" is probably a fault in the kernel DRM driver (linux package). I'll attempt to set that with an update."
1656155,2017-01-13 04:31:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1656155,2017-02-18 01:05:40 UTC,"I have fully the same situation with Lenovo v310-15 IKB and i5-7200u, HD620 graphic on board. I had this bug on fresh installed Ubuntu 16.04.2 and 16.10"
1656167,2018-10-16 21:37:56 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.openstack.org/421159
Reason: This project is no longer maintained."
1656167,2018-01-25 23:50:54 UTC,This issue was fixed in the openstack/trove-dashboard 10.0.0.0b3 development milestone.
1656167,2018-01-11 15:34:27 UTC,"Reviewed:  https://review.openstack.org/419747
Committed: https://git.openstack.org/cgit/openstack/trove-dashboard/commit/?id=c0871b8f9cf63657ebf1e6df48451fb4adae3977
Submitter: Zuul
Branch:    master"
1656167,2017-06-28 15:49:44 UTC,This issue was fixed in the openstack/tacker-horizon 0.9.0 release.
1656167,2017-06-22 12:44:35 UTC,This issue was fixed in the openstack/python-tackerclient 0.10.0 release.
1656167,2017-05-22 11:56:46 UTC,"Change abandoned by yatin (<email address hidden>) on branch: master
Review: https://review.openstack.org/419747
Reason: No update from reviewers, so abandoned."
1656167,2017-03-14 12:24:39 UTC,"Reviewed:  https://review.openstack.org/445316
Committed: https://git.openstack.org/cgit/openstack/python-tackerclient/commit/?id=af2f0f031f12ebdbfe17f2abddc1794d1396fb8c
Submitter: Jenkins
Branch:    master"
1656167,2017-03-14 06:31:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445316"
1656167,2017-02-13 20:56:25 UTC,This issue was fixed in the openstack/python-zaqarclient 1.4.0 release.
1656167,2017-02-02 16:36:33 UTC,This issue was fixed in the openstack/designate-dashboard 4.0.0.0rc1 release candidate.
1656167,2017-01-17 09:36:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421172"
1656167,2017-01-17 09:16:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421159"
1656167,2017-01-17 07:41:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421108"
1656167,2017-01-17 07:31:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421106"
1656167,2017-01-13 03:45:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419747"
1656167,2017-03-13 10:44:22 UTC,venkatamahesh - Is there any work activity on this bug ?
1656177,2017-01-13 18:01:50 UTC,"My apologies if I misread the original report - I'll take a closer look later tonight at how well the (experimental, known to be unstable and unfinished) geometric construction tools support snapping if a parametric shape (rectangle) is selected when the user starts drawing a geometric object."
1656177,2017-01-13 06:31:11 UTC,"Not limited nor related to the (experimental) LPE Tool for geometric construction: this is node snapping to rectangle shapes in general, and reproduces with these steps:"
1656177,2017-01-13 17:19:55 UTC,http://imgur.com/a/NBFlJ
1656177,2017-01-13 22:12:37 UTC,"Based on tests with archived builds, this is not a recent regression:
- reproduced with lp:inkscape/0.92.x r15325 (with LPETOOL),
- reproduced with Inkscape 0.91 (with LPETOOL),
- reproduced with lp:inkscape rev 10795 (with LPETOOL),
- reproduced with lp:inkscape rev 9760 (with LPETOOL)."
1656179,2017-01-13 05:43:17 UTC,"Please note that the geometric construction tools are part of the experimental path effects, and not enabled in the final stable release 0.92.0 r15299 (nor in any stable release before that)."
1656179,2017-01-13 05:52:32 UTC,"Crash reproduced with lp:inkscape/0.92.x r15315 (build explicitly configured to enable experimental path effects: -DLPE_ENABLE_TEST_EFFECTS -DWITH_LPETOOL) on OS X 10.7.5:
The crash occurs when cancelling drawing the line segment by switching tools. If the line segment has been finished (two clicks), there is no crash when switching tools."
1656179,2017-01-13 08:53:54 UTC,"Also reproduced on Xubuntu 16.04, lp:inkscape rev. 15415."
1656179,2017-01-13 06:13:41 UTC,"Based on tests with archived builds, this is not a recent regression:
- reproduced with Inkscape 0.91 (experimental LPEs enabled)
- reproduced with lp:inkscape rev 10795 (oldest archived 64bit trunk build with LPETOOL)
- reproduced with lp:inkscape rev 9760 (oldest archived 32bit trunk build with LPETOOL)"
1656182,2017-03-08 07:24:39 UTC,"Change abandoned by Surya Prakash Singh (<email address hidden>) on branch: master
Review: https://review.openstack.org/419795
Reason: patch not required."
1656182,2017-01-13 07:34:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419795"
1656182,2017-01-17 18:17:21 UTC,"Change abandoned by Surya Prakash Singh (<email address hidden>) on branch: master
Review: https://review.openstack.org/419772
Reason: oslo_log not compatible with fuel-cpp."
1656182,2017-01-13 06:12:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419772"
1656191,2017-01-13 07:11:01 UTC,"Seconded; this is on Xenial, version 2.1.0-0~201701041302~ubuntu16.04.1."
1656191,2017-01-18 14:33:55 UTC,Tracked here: https://github.com/conjure-up/conjure-up/issues/597
1656193,2017-01-18 14:34:25 UTC,Tracked here: https://github.com/conjure-up/conjure-up/issues/598
1656194,2017-01-18 14:34:55 UTC,Tracked here: https://github.com/conjure-up/conjure-up/issues/599
1656195,2017-01-18 14:35:24 UTC,Tracked @ https://github.com/conjure-up/conjure-up/issues/600
1656199,2017-01-18 14:35:53 UTC,Tracked @ https://github.com/conjure-up/conjure-up/issues/601
1656201,2017-01-13 07:29:54 UTC,Attaching the conjure-up.log with the traceback.
1656201,2017-01-13 07:12:34 UTC,"Doing a ^C on conjure-up gave me these 2 tracebacks:
$ conjure-up kubernetes
Exception in ev.run():
Traceback (most recent call last):
  File ""/usr/lib/python3/dist-packages/ubuntui/ev.py"", line 83, in run
    cls.loop.run()
  File ""/usr/lib/python3/dist-packages/urwid/main_loop.py"", line 278, in run
    self._run()
  File ""/usr/lib/python3/dist-packages/urwid/main_loop.py"", line 376, in _run
    self.event_loop.run()
  File ""/usr/lib/python3/dist-packages/urwid/main_loop.py"", line 1326, in run
    self._loop.run_forever()
  File ""/usr/lib/python3.5/asyncio/base_events.py"", line 345, in run_forever
    self._run_once()
  File ""/usr/lib/python3.5/asyncio/base_events.py"", line 1312, in _run_once
    handle._run()
  File ""/usr/lib/python3.5/asyncio/events.py"", line 125, in _run
    self._callback(*self._args)
  File ""/usr/lib/python3/dist-packages/conjureup/ui/views/deploystatus.py"", line 31, in _refresh_nodes_on_main_thread
    status = model_status()
  File ""/usr/lib/python3/dist-packages/conjureup/juju.py"", line 37, in _decorator
    return f(*args, **kwargs)
  File ""/usr/lib/python3/dist-packages/conjureup/api/models.py"", line 42, in model_status
    return juju.CLIENT.Client(request=""FullStatus"")
  File ""/usr/lib/python3/dist-packages/macumba/v2.py"", line 119, in _request
    'Params': params})
  File ""/usr/lib/python3/dist-packages/macumba/v2.py"", line 130, in call
    return self.receive(req_id, timeout)
  File ""/usr/lib/python3/dist-packages/macumba/api.py"", line 131, in receive
    time.sleep(0.1)
KeyboardInterrupt
Traceback (most recent call last):
  File ""/usr/bin/conjure-up"", line 9, in <module>
    load_entry_point('conjure-up==2.1.0', 'console_scripts', 'conjure-up')()
  File ""/usr/lib/python3/dist-packages/conjureup/app.py"", line 321, in main
    EventLoop.run()
  File ""/usr/lib/python3/dist-packages/ubuntui/ev.py"", line 83, in run
    cls.loop.run()
  File ""/usr/lib/python3/dist-packages/urwid/main_loop.py"", line 278, in run
    self._run()
  File ""/usr/lib/python3/dist-packages/urwid/main_loop.py"", line 376, in _run
    self.event_loop.run()
  File ""/usr/lib/python3/dist-packages/urwid/main_loop.py"", line 1326, in run
    self._loop.run_forever()
  File ""/usr/lib/python3.5/asyncio/base_events.py"", line 345, in run_forever
    self._run_once()
  File ""/usr/lib/python3.5/asyncio/base_events.py"", line 1312, in _run_once
    handle._run()
  File ""/usr/lib/python3.5/asyncio/events.py"", line 125, in _run
    self._callback(*self._args)
  File ""/usr/lib/python3/dist-packages/conjureup/ui/views/deploystatus.py"", line 31, in _refresh_nodes_on_main_thread
    status = model_status()
  File ""/usr/lib/python3/dist-packages/conjureup/juju.py"", line 37, in _decorator
    return f(*args, **kwargs)
  File ""/usr/lib/python3/dist-packages/conjureup/api/models.py"", line 42, in model_status
    return juju.CLIENT.Client(request=""FullStatus"")
  File ""/usr/lib/python3/dist-packages/macumba/v2.py"", line 119, in _request
    'Params': params})
  File ""/usr/lib/python3/dist-packages/macumba/v2.py"", line 130, in call
    return self.receive(req_id, timeout)
  File ""/usr/lib/python3/dist-packages/macumba/api.py"", line 131, in receive
    time.sleep(0.1)
K..."
1656201,2017-01-13 07:14:58 UTC,"It didn't return control to Bash, and when I went back and killed the Juju Controller, I then also got:
exception calling callback for <Future at 0x7f37d58136d8 state=finished raised ConnectionClosedError>
Traceback (most recent call last):
  File ""/usr/lib/python3.5/concurrent/futures/thread.py"", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File ""/usr/lib/python3/dist-packages/conjureup/juju.py"", line 37, in _decorator
    return f(*args, **kwargs)
  File ""/usr/lib/python3/dist-packages/conjureup/juju.py"", line 419, in _deploy_async
    params={""url"": service.csid.as_str()})
  File ""/usr/lib/python3/dist-packages/macumba/v2.py"", line 119, in _request
    'Params': params})
  File ""/usr/lib/python3/dist-packages/macumba/v2.py"", line 130, in call
    return self.receive(req_id, timeout)
  File ""/usr/lib/python3/dist-packages/macumba/api.py"", line 129, in receive
    res = self.conn.do_receive(request_id)
  File ""/usr/lib/python3/dist-packages/macumba/ws.py"", line 75, in do_receive
    raise ConnectionClosedError
macumba.errors.ConnectionClosedError"
1656201,2017-01-18 14:37:11 UTC,tracked @ https://github.com/conjure-up/conjure-up/issues/602
1656207,2017-01-18 14:37:35 UTC,https://github.com/conjure-up/conjure-up/issues/603
1656210,2017-01-18 14:38:02 UTC,https://github.com/conjure-up/conjure-up/issues/604
1656210,2017-01-18 19:54:47 UTC,"So it sounds like what you wanted to do is add more units (in two steps, add a machine and then place a unit there), and were expecting to be able to do that in the architecture view, but you can't because num_units is set in the 'config' view."
1656212,2017-01-18 14:38:27 UTC,https://github.com/conjure-up/conjure-up/issues/605
1656213,2017-01-18 14:38:53 UTC,https://github.com/conjure-up/conjure-up/issues/606
1656219,2017-01-18 14:39:25 UTC,https://github.com/conjure-up/conjure-up/issues/607
1656220,2017-01-18 14:39:52 UTC,https://github.com/conjure-up/conjure-up/issues/608
1656223,2017-01-18 14:40:18 UTC,https://github.com/conjure-up/conjure-up/issues/609
1656225,2020-03-05 19:44:45 UTC,some thoughts on the widget implementation:
1656225,2017-01-19 09:22:23 UTC,"Yes, such a effect sync feature would be great.
This is tracked here: https://bugs.launchpad.net/mixxx/+bug/1518185
Would you mind to add you comment there as well, or file a new bug, if it is do-able independently."
1656225,2017-01-19 02:27:06 UTC,Btw: Isn't that the way way some of those fancy (Pioneer?) mixers handle it?
1656225,2017-01-20 16:00:05 UTC,Done. Must have mixed those two up.
1656225,2017-01-13 09:26:55 UTC,"I do not like the idea to have an extra parameter type apart from buttons and knobs.
Since such a parameter is controlled by a knob, it should be one of the knob nature."
1656225,2017-01-19 02:21:32 UTC,"I'll join in to push this idea!
IMO especially the Echo effect is only usable for 'random delay' effect ATM. It's very hard to somehow adjust Echo delay on Pfl first (for a running track) then apply it to Channel and mix it in. Matching the BPM is pure chance...or hard work/time."
1656227,2019-01-03 14:33:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656227,2017-01-13 08:50:20 UTC,I also tested (unsuccessfully) with
1656227,2019-01-03 14:32:47 UTC,WORKAROUND:
1656227,2019-05-17 11:12:34 UTC,"This bug is reproducible in Trusty but not in Xenial neither in Bionic.
It was fixed somewhere between dicomscope 3.6.0-11 and 3.6.0-15build1."
1656229,2017-01-13 09:09:31 UTC,"A hint from a colleague led me to look at /var/log/conjure-up/combined.log, which says:"
1656229,2017-01-17 15:28:30 UTC,This is tracked upstream here: https://github.com/conjure-up/conjure-up/issues/495
1656231,2017-01-18 14:41:47 UTC,https://github.com/conjure-up/conjure-up/issues/610
1656234,2017-01-16 13:36:41 UTC,"On Fri, Jan 13, 2017 at 08:40:22AM -0000, Robert Hu wrote:

> Public bug reported:
>
> System Environment
> =======
> Qemu commit/branch: e92fbc75
> Host OS: RHEL7.2 ia32e
> Host Kernel: 4.9.0
> Guest OS: RHEL7.2 ia32e
> Guest Kernel: 4.9.0
>
> Bug detailed description
> =======
> While create a kvm guest using virtio-net, the qemu will core dump with showing ""Aborted (core dumped)"".
> Reproduce Steps
> ==============
> create a guest:
> qemu-system-x86_64 -enable-kvm -m 4096 -smp 4 -device virtio-net-pci,netdev=nic0,mac=00:16:3e:49:be:24 -netdev tap,id=nic0,script=/etc/kvm/qemu-ifup -drive file=/ia32e_rhel7u2_kvm.qcow2,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0 -serial file:serial.log
>
> Current Result:
> ==============
>
> qemu-system-x86_64: /workspace/ia32e/nightly/kvm-next-20170105-ef85b6-e92fbc/kvm/qemu/hw/virtio/virtio.c:214: virtio_queue_set_notification: Assertion `vq->notification_disabled > 0' failed.
> Aborted (core dumped)
"
1656234,2019-10-23 14:38:50 UTC,"Fix had been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=332fa82d0963409"
1656235,2017-03-01 22:05:34 UTC,"I agree it is confusing, but this seems like a general OpenStack issue: https://blueprints.launchpad.net/nova/+spec/vcpus-in-api"
1656237,2017-08-21 05:29:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656246,2017-01-13 09:45:17 UTC,"I've heard from Rick that 'charm login' actually implements a different login experience, which gives you a simple text UI around getting a macaroon from the store. We should be able to use that to give a better experience for users."
1656248,2017-01-13 12:32:32 UTC,"The attachment ""compiz_fix_monitor_reconfiguration.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1656248,2017-02-13 14:58:10 UTC,"The patch I provided earlier fixed the described problem, but did also create a new problem leading to off-screen windows when two configure notifies were received (first notify was for the actual size change, while the second one was not), and the second configure notify then lead to a change of mPrevSize, while actions for the first configure notify where still being processed."
1656249,2017-01-13 10:15:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/419870"
1656249,2017-01-17 09:38:29 UTC,"Reviewed:  https://review.openstack.org/419870
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=9961a4b1028503e0d28342d31437c9e8b3f6bd28
Submitter: Jenkins
Branch:    master"
1656249,2017-02-08 14:16:20 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430949"
1656249,2017-02-08 14:16:31 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/430950"
1656249,2017-02-17 10:20:39 UTC,"Reviewed:  https://review.openstack.org/430949
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=0e9b4cafec35f2d9c29f3880963e9a1d0074856d
Submitter: Jenkins
Branch:    stable/newton"
1656249,2017-02-27 16:29:33 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1656249,2017-03-10 16:49:05 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/430950"
1656250,2017-01-19 02:25:56 UTC,Sounds like we might want a similar fix in Mir itself.
1656250,2017-02-21 12:36:05 UTC,This bug was fixed in the package qtmir - 0.5.1+17.04.20170215.1-0ubuntu1
1656250,2017-01-19 02:21:12 UTC,Sounds similar to bug 1521403 actually. That is also Unity8 crashing on suspend (but suspend triggered by Xmir).
1656250,2017-01-17 01:31:44 UTC,Thanks. In the next release; Mir 0.26.0 we've added more information about the power mode to the above log messages so it will become more obvious what's changing.
1656250,2017-11-03 15:24:02 UTC,Syncing task from Mir.
1656250,2017-01-16 01:52:25 UTC,It appears Unity8 crashed (in Mir) when changing display configuration (which is probably the setting of the display power mode to standby/suspend/off):
1656250,2017-01-13 15:41:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656250,2017-01-13 09:37:08 UTC,Log files.
1656250,2017-01-16 12:06:04 UTC,After some experimentation I'm able to confirm previous comment and that the dash crashes when the display suspends. I set it to 10 minutes and from unity8.log the crash always happens after 10 minutes without touching the machine.
1656252,2017-03-10 15:31:45 UTC,"The workaround was causing a regression in webbrowser-app: in unity8, opening a link from another app would work if the browser was not running, but it wouldn't do anything if the browser was already running."
1656252,2017-01-13 09:51:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656252,2017-01-13 13:58:03 UTC,We were seeing this on the second launch of any app that has single instance specified in the desktop file. The theory is systemd is confused about it successfully exiting.
1656252,2017-01-13 14:08:13 UTC,Assigning to unity8 because it happened with other apps too like system settings or the gallery.
1656252,2017-01-13 16:15:00 UTC,I can confirm that removing single instance from the desktop file works around it.
1656252,2017-01-16 01:28:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656252,2017-01-27 01:48:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656254,2017-02-06 23:09:58 UTC,There are several other filesystem locations that the virt-aa-helper profile supports. I just checked Ubuntu 16.04 and the virt-aa-helper profile allows you to set instances-path to a location underneath any of these directories:
1656254,2017-01-13 10:10:06 UTC,libvirt bug 1644507
1656254,2017-01-13 10:08:55 UTC,The aa-profile for the nova-compute daemon is managed by the charm; the virt-aa-helper profile provided by packaging currently supports the default nova location and anything under /srv - there is a different bug to make that more generic in approach.
1656266,2017-08-11 09:08:07 UTC,"Only admin knows if the member is valid or not, regular user can not get other tenants and validate the member_id when create member."
1656269,2017-02-01 13:51:50 UTC,"9.2 is not certified with more than 200 nodes. So, set as Fix Released in 9.2."
1656269,2017-01-13 11:04:48 UTC,there are lines in astute.log
1656269,2017-01-13 15:23:50 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/420028"
1656269,2017-01-16 10:18:12 UTC,"Reviewed:  https://review.openstack.org/420028
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=570049ca1fde98ee09952075f72bc4f28b9d8b71
Submitter: Jenkins
Branch:    stable/mitaka"
1656269,2017-01-16 11:25:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420654"
1656269,2017-01-16 11:30:55 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/420660"
1656269,2017-01-16 16:40:48 UTC,"Reviewed:  https://review.openstack.org/420654
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=64d62086e88460e29f5d9117a1f4c69d391d4bd0
Submitter: Jenkins
Branch:    master"
1656269,2017-01-17 11:15:38 UTC,"Reviewed:  https://review.openstack.org/420660
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=e05f66d12ef0fc9cdc71b5955a55978929a7cda8
Submitter: Jenkins
Branch:    stable/newton"
1656269,2017-02-13 13:19:30 UTC,The issue affects provisioning 50 nodes.
1656269,2017-02-27 16:26:55 UTC,This issue was fixed in the openstack/fuel-astute 11.0.0.0rc1 release candidate.
1656271,2017-01-14 07:54:22 UTC,append the patch link:
1656271,2017-02-21 08:00:17 UTC,patch was merged.
1656276,2017-01-14 13:03:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420337"
1656276,2017-01-14 13:05:09 UTC,"Change abandoned by Alan Pevec (<email address hidden>) on branch: master
Review: https://review.openstack.org/420337
Reason: duplicate of Iffc70e22a762f58c3f946e27cd0064f3e33b892d"
1656276,2017-01-14 19:40:56 UTC,"Reviewed:  https://review.openstack.org/420336
Committed: https://git.openstack.org/cgit/openstack/packstack/commit/?id=0ab6d87daed904233e8ba670981e9b468f29ab9d
Submitter: Jenkins
Branch:    master"
1656276,2017-01-15 20:26:01 UTC,"Seems like it doesn't happen in CI jobs anymore, removing alert and promotion-blocker tags meanwhile."
1656276,2017-01-16 20:09:34 UTC,"Reviewed:  https://review.openstack.org/332713
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f7e9f312a064d9809e2093de5b54c18a45a75322
Submitter: Jenkins
Branch:    master"
1656276,2017-01-16 23:28:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420994"
1656276,2017-01-13 17:17:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420079"
1656276,2017-01-18 21:29:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422248"
1656276,2017-01-26 02:29:55 UTC,"Reviewed:  https://review.openstack.org/422248
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=dc2f3a358663c0fb97795666b16dec63cfcc3872
Submitter: Jenkins
Branch:    master"
1656276,2017-01-26 19:06:24 UTC,This issue was fixed in the openstack/puppet-nova 10.2.0 release.
1656276,2017-02-07 10:31:14 UTC,"Change abandoned by Sylvain Bauza (<email address hidden>) on branch: master
Review: https://review.openstack.org/420079
Reason: We now have a better consensus about leaving the simple_cell_setup call for just an easy upgrade, and rather call each nova-manage method for each step (create cell0, then a cell, then discover hosts for each cell) http://docs.openstack.org/developer/nova/cells.html#first-time-setup"
1656276,2017-01-14 12:59:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420336"
1656276,2017-01-18 19:17:22 UTC,"Reviewed:  https://review.openstack.org/420994
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=d2597b32c80c3800d74f360401eb37a69396e0fa
Submitter: Jenkins
Branch:    master"
1656276,2017-01-14 12:51:45 UTC,"Packstack needs same partial revert as in puppet-openstack-integration:
https://review.openstack.org/#/c/420167/2/manifests/nova.pp"
1656276,2017-01-13 16:59:09 UTC,I'm also tracking some of these open questions/issues in the wiki here:
1656276,2017-01-13 20:29:02 UTC,"Reviewed:  https://review.openstack.org/420109
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=3f83f39fc35d95f7bb1252af18a506a3deef8ce0
Submitter: Jenkins
Branch:    master"
1656276,2017-01-13 19:49:30 UTC,"Reviewed:  https://review.openstack.org/420068
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=34f3ab689616517888422582357d0d4a38e0925d
Submitter: Jenkins
Branch:    master"
1656276,2017-01-13 19:21:10 UTC,"Reviewed:  https://review.openstack.org/420063
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=be0ac8f320ef31329a70e3d4c2dfee871872dace
Submitter: Jenkins
Branch:    master"
1656276,2017-01-13 17:55:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420109"
1656276,2017-06-13 21:35:23 UTC,"Hi all,"
1656276,2017-01-13 16:56:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420068"
1656276,2017-01-13 16:50:48 UTC,I think we can look at changing the simple_cell_setup command to not return 1 if there are no compute nodes in the deployment yet. And then we'd change the map_cell_and_hosts command to return 1 if there are no compute nodes because that command is specifically for that part of the setup and can't be incomplete.
1656276,2017-01-13 16:41:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420063"
1656276,2017-01-13 15:55:42 UTC,"Hi Alfredo,"
1656276,2017-01-13 15:08:07 UTC,As per discussion in #openstack-nova:
1656276,2017-01-13 13:15:04 UTC,"IIUC, review https://review.openstack.org/#/c/409890 has just uncovered an issue in how we were adding cells as we were mapping cell0, creating schema but not adding the nodes using either ""nova-manage cell_v2 discover_hosts"" or simple_cell_setup again after adding compute nodes."
1656276,2017-01-13 12:54:30 UTC,"Everything was working a few hours ago, I think it could be related to https://review.openstack.org/#/c/409890"
1656276,2017-01-14 12:49:32 UTC,Packstack fails even with puppet-nova revert http://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=a41d30806d4ae7b772e2276e9b058aa61e742d38
1656279,2017-06-01 02:21:46 UTC,Removing the milestone as we have noone focused on working on this right now.
1656279,2017-01-13 11:24:40 UTC,bootstrap logs with --debug on: http://paste.ubuntu.com/23791852/
1656281,2017-02-16 18:38:07 UTC,"Frederic,"
1656281,2020-10-22 19:09:40 UTC,closing since the package is removed from Ubuntu
1656281,2017-02-14 11:17:50 UTC,"Hi,
here is the packages in a PPA :
https://launchpad.net/~ibmpackages/+archive/ubuntu/kimchi-project/+packages"
1656281,2017-03-07 11:29:29 UTC,Default Comment by Bridge
1656281,2017-01-23 18:30:46 UTC,"Manoj,"
1656281,2017-01-23 17:23:54 UTC,This package would need to be upgraded in Debian so that it can be synced to Ubuntu. This would require a community effort in getting this package upgraded to 2.3.1.
1656281,2017-01-30 17:49:17 UTC,"As discussed on the interlock call, if Fedrico can update the package and may be push the updated packages to his PPA, we can get him some help on getting those updated packages into the Ubuntu archive after review."
1656284,2020-11-18 14:24:03 UTC,"Replicated in 0.92.0 (with adjusted opacity but not fill-opacity), looks fixed with 0.92.3 pdf export of same file. 1.0.1 export is fixed too."
1656289,2017-01-19 20:15:14 UTC,I just tested on a clean system with:
1656289,2017-01-19 17:38:40 UTC,"obviously the snap ships with a pulse library for pulse 9.0 ... since the ubuntu-core/core snap is xenial and teh host os we are seeing this issue on is also xenial there is only pulse 8.0, this might have some effect ... teh snap should really be built either using cleanbuild or launchpad to only ship the xenial versions of libs inside"
1656289,2017-01-19 20:16:59 UTC,Removing the regression-update tag.
1656289,2017-01-19 19:05:58 UTC,"Using 2.20.1, the snap was rebuilt using xenial libraries and now has pulse 8.0. This had no effect. Putting the profile in complain mode also had no effect. It appears the snap is not using pulseaudio and trying to fallback to alsa, but the alsa configuration doesn't exist in the core snap, so that fallback doesn't work."
1656289,2017-01-13 17:12:36 UTC,"""snap list"" doesn't mention devmode. I'm pretty confident I didn't install it with devmode, since that's not what the instructions I followed say to do and I had no other reason to do so. I specifically installed this particular snap because I wanted it confined."
1656289,2017-01-13 14:55:27 UTC,"@Robie, thanks for the bug! Just wanted to mention that as a matter stable series release policy we will not remove rules providing access precisely because we do not want to break applications in the manner described (unless there are extraordinary circumstances that would require communication to developers-- we haven't exercised that and this bug is not an example of that). More specifically, we did not allow /usr/share/alsa/alsa.conf in 2.17 and take it away in 2.20; we only added the alsa interface to allow it in 2.20."
1656289,2017-01-13 15:41:57 UTC,@Robie: 'snap list' will show if it is installed in devmode.
1656289,2017-01-13 14:56:52 UTC,@Robie-- I suspect that the snap in question was installed with --devmode. Can you confirm?
1656289,2017-01-13 15:56:14 UTC,Hi
1656289,2017-01-13 15:19:15 UTC,"On Fri, Jan 13, 2017 at 02:56:52PM -0000, Jamie Strandboge wrote:

> @Robie-- I suspect that the snap in question was installed with
> --devmode. Can you confirm?
"
1656301,2017-01-14 15:16:19 UTC,ALso the keyboard sometimes press random key itself.
1656302,2017-01-15 23:51:31 UTC,"Could you try using it with a 16.04 live image? If it works fine there, perhaps its worth considering updating to 16.04."
1656302,2017-01-19 20:51:11 UTC,"I'll give it a go when I get 5 minutes, having just performed the upgrade to 14.04 and spent several days getting everything fully working again, I'm loathed to do another upgrade so soon."
1656304,2017-06-01 02:26:45 UTC,"Not sure about the actual priority of this. If this continues to be a big problem, let me know."
1656304,2017-01-17 12:37:25 UTC,"* I bootstraped the env from scratch: https://pastebin.canonical.com/176158/
* I deployed a node with a couple of bridges configured from MAAS UI (br0, br1): https://pastebin.canonical.com/176159/
* From ""juju status"" perspective, unit is in ""allocating"" state and machine is ""down"".
* From MAAS UI perspective, node is powered on and in ""Ready"" state, after a short transition to ""allocating"" and back to ""Ready"""
1656304,2017-01-17 12:25:44 UTC,"I suspect that this is now an upgrade-juju issue. I was not able to bootstrap with a bridge in MAAS using 2.0.0, but I was with 2.0.2."
1656304,2017-01-17 12:05:07 UTC,"Hi,"
1656304,2017-01-17 11:33:49 UTC,This looks like a version issue:
1656304,2017-01-17 11:38:01 UTC,"As per comment above, the issue has been fix. I am marking it as such \o/"
1656304,2017-01-17 10:40:43 UTC,"Hi Andrew. Yeah, I'm creating such bridge(s) from MAAS UI.
* I've re-tested it by creating br0 against main interface (the one selected as PXE).
* I've configured br0 as the interface was (untagged, 10.245.88.0/23, (Auto assign))"
1656304,2017-01-17 07:01:49 UTC,Can you also run the deploy with debug:
1656304,2017-01-17 06:51:31 UTC,"When you say ""create a bridge for one or all the interfaces gathered after Commissioning phase"" is this something you are doing in the MAAS UI, or something you are doing in a custom curtin/MAAS install script?"
1656304,2017-01-15 22:51:41 UTC,"We track Juju 2.x issues in ""juju"" project. Re-targeting :)"
1656304,2017-01-17 10:42:38 UTC,"If I leave a node without bridges configured in MAAS, it works fine:"
1656305,2017-04-24 12:19:48 UTC,"Moving to invalid for newton release, as this issue isn't there. This bug is also irrelevant to ocata release."
1656305,2019-05-22 13:47:00 UTC,"Change abandoned by Alexey Stupnikov (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/459391"
1656305,2017-10-03 09:46:45 UTC,Verified on 9.2 + proposed
1656305,2017-08-03 14:24:13 UTC,"Reviewed:  https://review.openstack.org/459387
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=0f27fc81a1cfab49647b09e9ff50f5d7d9f006c9
Submitter: Jenkins
Branch:    stable/mitaka"
1656305,2017-07-19 09:57:46 UTC,mos-maintenance team is unable to merge anything to stable/newton branch. Assigning a bug to fuel-sustaining for 10.x-updates milestone.
1656305,2017-04-24 16:01:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/459391"
1656305,2017-04-24 15:53:55 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/459387"
1656305,2017-03-14 11:56:11 UTC,Opened a bug #1672702
1656305,2017-03-14 11:41:10 UTC,Here is a list of issues I have found:
1656305,2017-03-14 11:35:02 UTC,Let me clarify this bug's description. It turns out that some log locations are mentioned twice in /etc/logrotate.d configuration files: first time in specific file that is shipped with a service's rpm and second time inside fuel.nodaily file.
1656305,2017-03-10 14:35:18 UTC,Bug #1656834 was solved.
1656305,2017-01-16 14:11:57 UTC,This bug's resolutions is locked by the bug #1656834
1656305,2017-01-16 13:48:58 UTC,"It looks like we are fixing medium priority bugs in stable/mitaka, so I will write a patch."
1656305,2017-01-16 13:44:33 UTC,"Setting this bug's importance to medium as it is a 'Failure of a significant feature, with workaround'. WA is to delete duplicate logrotate configuration entries from /etc/logrotate.d/fuel.nodaily file."
1656305,2017-03-14 11:48:38 UTC,"And we have another issue with keystone logrotate configuration on master node: server isn't restarted, files are not rotated with copytruncate option (as in deb package). Will open another bug."
1656317,2017-02-08 13:58:22 UTC,There has already been some work done in this area https://review.openstack.org/#/c/68333/
1656327,2017-02-08 15:00:39 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/430981"
1656327,2017-03-14 11:26:20 UTC,"Reviewed:  https://review.openstack.org/430980
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=2c42f3a63908559b47f23766d7d408b746376326
Submitter: Jenkins
Branch:    stable/newton"
1656327,2017-03-10 16:48:51 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/430981"
1656327,2017-02-27 16:29:19 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1656327,2017-01-20 09:59:16 UTC,"Reviewed:  https://review.openstack.org/420043
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=363a783be2a0a48dfeb7199362d3d1af16a78352
Submitter: Jenkins
Branch:    master"
1656327,2017-01-13 15:51:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420043"
1656327,2017-02-08 15:00:26 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430980"
1656328,2017-01-15 18:25:07 UTC,"Seems like this is not directly a Compiz issue, but rather a X.Org or Radeon driver one. Firstly I disabled the animations plugin but still was getting freezes on animations in applications. So I temporarily replaced Compiz with Marco and during this couple of days did not get X.Org completely frozen but browser windows themselves (Firefox and Chromium) are still sometimes getting frozen. Switching to TTY and back resolves the freeze just like with the full freeze when running Compiz. So I move this issue to X.Org bugtracker."
1656328,2017-10-07 22:21:35 UTC,"I have the same issue. I have Debian Stretch on my laptop and on my desktop, and both have the same problem since I upgraded from Debian Jessie. I am pretty much a newbie and don't have any formal training in computer science. What should I do? Wait for this to be resolved? Move back to Jessie? I have not seen updates in Stretch for a long time. I guess not very many people use it yet."
1656331,2017-01-13 16:15:06 UTC,"Just as a reference point so it isn't forgotten: i18n expects the monolithic fm_IDL.xml right now, and I believe that process happens long before the proposed script to re-make it would run. As such it would likely need to be adjusted to look at the fm_IDL.d directory as well. The fact that it then makes a translatable reporter monolithic fm_IDL.xml makes things a bit harder and needs to be taken into account."
1656331,2017-01-13 16:14:01 UTC,+1.
1656331,2017-01-13 16:53:02 UTC,"Bill, I think naming them after the class id as you suggest would be best, actually.  First, it reinforces class id uniqueness, and second, it makes it easier for local git repos maintain tweaks to core classes."
1656334,2017-02-13 22:26:07 UTC,This issue was fixed in the openstack/bifrost 3.0.0 release.
1656335,2017-02-13 22:26:05 UTC,This issue was fixed in the openstack/bifrost 3.0.0 release.
1656337,2018-10-15 16:21:26 UTC,"Just adding my two cents, since I got curious about this."
1656337,2018-11-08 16:04:44 UTC,I've added a -o0 build (both for complile and link) of the head rev. to the builds archive and Derek has just reported it's still crashing the same way.
1656337,2018-10-14 03:45:10 UTC,Yup i have the same issue windows 10 x 64  and 64 bit ver. dc++ 867 and 868 both affected.
1656337,2017-01-15 12:47:21 UTC,happens only with the 64-bit version; the 32-bit one works fine.
1656340,2017-01-13 16:32:34 UTC,"This bug should definitely be fixed, but note that snaps are allowed to create /run/user/1000/snap.$SNAP_NAME by this rule:"
1656340,2017-12-27 16:54:03 UTC,This functionality was added in https://github.com/snapcore/snapd/commit/1e3735f630f98df315e11b8d8d58d33b61476f59
1656340,2018-02-26 21:07:49 UTC,"Daniel, there are two things here: XDG_RUNTIME_DIR in terms of the user's session and XDG_RUNTIME_DIR in terms of the snap. The one for the user is supposed to be created by the session manager, but it sometimes isn't. The one for the snap should be created by snappy."
1656340,2018-02-26 21:25:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656340,2019-09-26 08:52:24 UTC,"Hi,"
1656340,2019-09-26 09:06:49 UTC,Hi additional output from running obs-studio
1656340,2019-11-14 20:06:58 UTC,"@jdstrand, what is the resolution to this bug and https://bugs.launchpad.net/snap-confine/+bug/1620442?"
1656343,2017-01-30 13:34:53 UTC,"Hi,"
1656343,2017-01-16 09:07:56 UTC,"Hi ,"
1656343,2017-01-16 13:30:55 UTC,"Hi. I've installed 3.16.11 from Zesty (http://packages.ubuntu.com/zesty/hplip , recompiled with debuild) with no luck, the error is the same."
1656348,2017-02-01 09:11:34 UTC,Duplicate of this https://bugs.launchpad.net/hplip/+bug/1498366
1656348,2017-02-01 09:12:34 UTC,Another bug report for this: https://bugs.launchpad.net/hplip/+bug/1656348
1656350,2017-01-18 06:45:24 UTC,"Hello Mike,"
1656350,2017-01-18 01:36:47 UTC,"I just ran across this blog post, which was helpful for me to understand why you might be doing what you're doing:"
1656350,2017-01-17 23:36:39 UTC,"Right now I'm not clear on if we would need to model any additional information about your setup in MAAS to make this work for you, so I'm marking this bug 'Opinion' there."
1656350,2017-01-18 06:49:58 UTC,"Sorry I should add, that IMHO, the most flexible way of implementation would be as described in Scot's blog post [ http://blog.scottlowe.org/2013/05/29/a-quick-introduction-to-linux-policy-routing/ ] as this method provides the widest and most flexible number of options."
1656350,2017-01-16 05:56:11 UTC,"Hi, thanks for the feed back and for looking into this problem."
1656350,2017-01-13 18:24:44 UTC,"This looks like a problem in curtin's rendering of /etc/network/interfaces, but I don't know if it's a problem that has already been addressed. (You are using a MAAS release a couple of minor revisions behind; there is a newer one in xenial-proposed.)"
1656350,2017-01-18 07:51:06 UTC,All right; you've convinced me. ;-) I think we should consider adding source routing as a feature. I'll put it on the wishlist.
1656350,2017-01-16 07:24:30 UTC,"Hello again,"
1656350,2017-01-18 08:27:49 UTC,"Hi Mike,"
1656353,2017-01-17 08:14:15 UTC,This is happening because a non monospace font was selected. Related to #1656853
1656353,2017-01-17 08:26:23 UTC,Can you try to change the font to monospace see if it's fixed? Then can you try to switch back to Inconsolata see if it's still fixed?
1656358,2017-01-13 16:49:54 UTC,"I can confirm this bug on xenial+overlay+silo 2129, however slightly different."
1656358,2017-01-13 17:04:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656369,2017-03-01 00:27:02 UTC,This bug was fixed in the package curtin - 0.1.0~bzr460-0ubuntu1~16.10.1
1656369,2017-02-08 21:11:39 UTC,This bug was fixed in the package curtin - 0.1.0~bzr459-0ubuntu1
1656369,2017-02-17 17:01:41 UTC,"Hello Ryan, or anyone else affected,"
1656369,2017-02-17 17:08:02 UTC,"Hello Ryan, or anyone else affected,"
1656369,2017-02-28 18:43:37 UTC,"I've run curtin's vmtest testsuite with the test provided in the
description by doing the following."
1656369,2017-02-28 18:52:21 UTC,"I've run curtin's vmtest testsuite with the test provided in the
description by doing the following."
1656369,2017-03-01 00:27:26 UTC,"The verification of the Stable Release Update for curtin has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1656369,2017-03-01 00:53:57 UTC,This bug was fixed in the package curtin - 0.1.0~bzr460-0ubuntu1~16.04.1
1656378,2017-03-07 22:42:38 UTC,"Reviewed:  https://review.openstack.org/440667
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=3f5495bb2a5ac0ad613a83d78e79af679f854d69
Submitter: Jenkins
Branch:    master"
1656378,2017-03-08 07:53:21 UTC,"Reviewed:  https://review.openstack.org/441746
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=9e65a7f0389d311b1e9a7150ef621f73cc811537
Submitter: Jenkins
Branch:    master"
1656378,2017-03-21 07:29:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447918"
1656378,2017-03-14 08:16:17 UTC,"Reviewed:  https://review.openstack.org/441753
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=6ad04c6b78da7ea8c0beb19fe74b98468b9e5f2f
Submitter: Jenkins
Branch:    master"
1656378,2017-03-07 22:37:24 UTC,"Reviewed:  https://review.openstack.org/440681
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=448c802d64c82057061b0ccfa60f1e053917c5c5
Submitter: Jenkins
Branch:    master"
1656378,2017-03-10 02:41:20 UTC,"Reviewed:  https://review.openstack.org/441756
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c1b2862642ce594a04a0a671b2e207edb09a2315
Submitter: Jenkins
Branch:    master"
1656378,2017-03-07 10:52:18 UTC,"Reviewed:  https://review.openstack.org/441755
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=685de89d71dd24d7f80b79a27dd4079e27945249
Submitter: Jenkins
Branch:    master"
1656378,2017-03-06 03:36:29 UTC,"Reviewed:  https://review.openstack.org/440709
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=eb8ef66faa56ba08e8b309e9ed0662b3a0f48d3d
Submitter: Jenkins
Branch:    master"
1656378,2017-03-06 06:27:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441759"
1656378,2017-03-06 06:21:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441756"
1656378,2017-03-06 06:16:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441755"
1656378,2017-03-06 06:10:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441753"
1656378,2017-03-06 05:37:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441746"
1656378,2017-03-22 10:29:41 UTC,"Reviewed:  https://review.openstack.org/447918
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=2c87a949e492cb0c02e5981017b102f45b4ddfe3
Submitter: Jenkins
Branch:    master"
1656378,2017-03-07 10:51:30 UTC,"Reviewed:  https://review.openstack.org/441759
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=07662fd223b1a6fea4041de452008e7431ff6c97
Submitter: Jenkins
Branch:    master"
1656378,2017-04-10 10:43:24 UTC,"Reviewed:  https://review.openstack.org/440703
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=538b518ab1ad42fbc1f584a023e616486483e54d
Submitter: Jenkins
Branch:    master"
1656378,2017-05-19 09:43:47 UTC,"Reviewed:  https://review.openstack.org/466135
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=aeb0c2e1e7d8f0b305aa26ac797b29373f30008f
Submitter: Jenkins
Branch:    master"
1656378,2017-05-18 23:07:04 UTC,"I am checking the progress and updating the etherpad linked at the top of bug description.
It is a good progress so far."
1656378,2017-03-06 03:32:11 UTC,"Reviewed:  https://review.openstack.org/440677
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=27f82681a77597f35a57ea7e0dc28fb7fcd4d7af
Submitter: Jenkins
Branch:    master"
1656378,2017-05-19 09:46:08 UTC,"Reviewed:  https://review.openstack.org/466134
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c8b761a2d0e6157b6cdbaf8d861a6606042a805c
Submitter: Jenkins
Branch:    master"
1656378,2017-05-19 09:51:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466245"
1656378,2017-05-19 10:03:12 UTC,"Reviewed:  https://review.openstack.org/466125
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=b937d9582a8876247e47e97fabb8fa2d4080dde8
Submitter: Jenkins
Branch:    master"
1656378,2017-05-19 13:17:09 UTC,The remaining work is to update address information in the figures.
1656378,2017-05-19 14:51:18 UTC,"Reviewed:  https://review.openstack.org/466245
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=fd3ce4f61c305a0f936a825a8cadf9be5d8d0bae
Submitter: Jenkins
Branch:    master"
1656378,2017-04-11 00:39:03 UTC,"Reviewed:  https://review.openstack.org/440695
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c9bfea29efe8e67f557ade8c2824bb3b3023eab6
Submitter: Jenkins
Branch:    master"
1656378,2017-05-23 16:37:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467314"
1656378,2017-09-12 22:03:04 UTC,Moved to the neutron repo :)
1656378,2020-04-26 03:26:02 UTC,stay tuned
1656378,2017-05-19 00:39:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466135"
1656378,2017-05-19 00:33:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466134"
1656378,2017-05-18 23:44:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/466125"
1656378,2017-05-18 23:35:39 UTC,"The remaining are four files (config-dns-int.rst, config-dns-res.rst, intro-nat.rst, intro-basic-networking.rst) and figures.
Good progress :)"
1656378,2017-07-04 08:54:31 UTC,"Change abandoned by Alexandra Settle (<email address hidden>) on branch: master
Review: https://review.openstack.org/467314
Reason: Because of https://review.openstack.org/#/c/477105/"
1656378,2017-03-06 03:32:05 UTC,"Reviewed:  https://review.openstack.org/440687
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=d9acaa833e57a3eb815a1de66201964bf44e741a
Submitter: Jenkins
Branch:    master"
1656378,2017-05-19 03:22:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466164"
1656378,2017-03-06 03:26:32 UTC,"Reviewed:  https://review.openstack.org/440664
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=eb1302e1899691557e8b281ce966335cea35b368
Submitter: Jenkins
Branch:    master"
1656378,2017-02-14 08:37:08 UTC,"Reviewed:  https://review.openstack.org/433138
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=8abf3a9f3efce63cd72931fdc35ceeb53aceaa6f
Submitter: Jenkins
Branch:    master"
1656378,2017-02-14 08:36:45 UTC,"Reviewed:  https://review.openstack.org/433145
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=6662e41e404a5bd2b7a43178dd2dabb0bab8779b
Submitter: Jenkins
Branch:    master"
1656378,2017-02-14 08:36:24 UTC,"Reviewed:  https://review.openstack.org/433153
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=63c7c20842763576b8c2c04968a28a1c5c0f6171
Submitter: Jenkins
Branch:    master"
1656378,2017-05-19 09:39:12 UTC,"Reviewed:  https://review.openstack.org/466164
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=74048f67663a35404f9c2ffe318a11f2f4bd78ef
Submitter: Jenkins
Branch:    master"
1656378,2017-01-16 11:19:39 UTC,"Hey Clint, thanks for pointing this out. I wasn't aware of that RFC at all! I'm going to look into adding this to our doc conventions to avoid future non-compliant additions."
1656378,2017-01-16 11:47:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420670"
1656378,2017-03-02 16:13:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440658"
1656378,2017-01-23 10:20:46 UTC,"Reviewed:  https://review.openstack.org/420670
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=d5c8ea48aed3fc0bd4221311df9b734c4ab9a1e0
Submitter: Jenkins
Branch:    master"
1656378,2017-02-01 15:00:42 UTC,"This bug is still open. The new guideline has merged, but there are still examples of non-compliance to be addressed."
1656378,2017-02-03 14:27:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/428758"
1656378,2017-02-06 22:35:12 UTC,"Reviewed:  https://review.openstack.org/428758
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=eb1ff2a0546fdf9c08554273bb7b5ba64f27c4a8
Submitter: Jenkins
Branch:    master"
1656378,2017-02-13 15:32:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433138"
1656378,2017-02-13 15:44:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433145"
1656378,2017-02-13 16:09:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433153"
1656378,2017-02-01 13:51:48 UTC,"Nice work! I had originally meant to make a patch myself but got
distracted. :)"
1656378,2017-03-02 16:17:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440664"
1656378,2017-03-06 03:27:13 UTC,"Reviewed:  https://review.openstack.org/440684
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=28c8522cc834cb8e8bec07546a6daff82c25fc61
Submitter: Jenkins
Branch:    master"
1656378,2017-03-02 16:37:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440677"
1656378,2017-03-02 16:22:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440667"
1656378,2017-03-03 16:24:33 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.openstack.org/440691"
1656378,2017-03-03 16:23:30 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.openstack.org/440690"
1656378,2017-03-03 16:05:19 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.openstack.org/440712"
1656378,2017-03-03 16:04:51 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.openstack.org/440705"
1656378,2017-03-02 17:13:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440712"
1656378,2017-03-02 17:10:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440709"
1656378,2017-03-02 17:07:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440705"
1656378,2017-03-02 17:05:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440703"
1656378,2017-03-02 16:57:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440695"
1656378,2017-03-02 16:55:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440691"
1656378,2017-03-02 16:53:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440690"
1656378,2017-03-02 16:50:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440687"
1656378,2017-03-02 16:46:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440684"
1656378,2017-03-02 16:42:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440681"
1656378,2017-03-06 03:25:48 UTC,"Reviewed:  https://review.openstack.org/440658
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=9c332c873e0a0135db415d32a2a8cbf383d1df69
Submitter: Jenkins
Branch:    master"
1656383,2017-03-31 08:21:29 UTC,Definitely related to tiling. With trunk one can now visualize the tiles by uncommenting a line in src/desktop.cpp (canvas_debug) to see the tiles. Tile edges align with the discontinuities.
1656383,2017-01-13 18:56:34 UTC,"And another comment by su_v:
Bug #1651915 is not related - the lines described there also reproduce with 14904"
1656383,2017-01-13 18:48:20 UTC,"Some helpful comments from su_v via IRC:
based on tests with archived builds: not seen with 14904, seen with 14914
https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/changes/14914
could have been exposed with the fix for the broken quality settings in
https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/14913
(i.e. the issue could have been there before that (?))
I tested with default (new) prefs for each run.
they seem to go back to early cairo-rendering merges
I do see them with 10578 (before the merge of the renderer caching branch)
I do not see them with 10579 (the merge of the caching branch)
but that's also the commit which disabled the quality prefs (based on my earlier tests)"
1656383,2017-01-13 19:14:36 UTC,Confirming based on my tests as quoted from irc.
1656384,2017-01-13 21:32:49 UTC,development has moved to github: https://github.com/hexmode/mediawiki-el
1656384,2017-01-13 21:34:37 UTC,fixed here: https://github.com/hexmode/mediawiki-el/commit/67783c6385a4ffe64c211a88ffb78e8f007fc479
1656386,2017-02-01 20:05:43 UTC,Same campaign on newton stable changes:
1656386,2017-05-03 22:08:33 UTC,"(5:07:19 PM) clarkb: mriedem: there were a lot of small thinsg we did
(5:07:56 PM) clarkb: mriedem: we enable same page merging or whatever its called so libvirt VMs woudl share memory. We reduced the number of siwft processes. We reduced the number of apache workers
(5:08:11 PM) clarkb: mriedem: I don't think any openstack projects did anything to reduce their memory consumption though"
1656386,2017-03-14 22:32:34 UTC,TripleO is producing a high rate of false positives now because they do this:
1656386,2017-02-17 20:40:17 UTC,Gate runs a failing because towards the end of the test phase the VM runs OOM.
1656386,2017-02-09 18:19:30 UTC,"This bug requires more attention from *all* OpenStack projects and infra folks, IMO. Related thread [0].
I suggest to try those fancy bcc tools [1] for BPF in Linux kernels 4.x. See example [2]. This could realy help to track the RC down."
1656386,2017-02-01 22:27:50 UTC,Running with one API worker per service cuts down the memory footprint quite a bit:
1656386,2017-02-01 20:57:55 UTC,"It'd be good to get an idea of what is taking up the most amount of space, my guess would be versioned objects, but not sure which ones, or what's holding onto them."
1656386,2017-02-01 20:11:24 UTC,RSS being reliable or not as a memory footprint indication has increased since Mitaka.
1656386,2017-02-01 20:08:03 UTC,So in a nutshell neutron has gone from ~1.4G (mitaka) to ~1.6G (newton) and ~1.8GB (ocata).
1656386,2017-02-01 20:02:09 UTC,"I took the liberty of running the above bash commands on [1,2] (which is mitaka) and that's what I got:"
1656386,2017-02-01 19:29:17 UTC,"Either way, I totally agree with the sentiment that we should determine whether we can trim down the neutron system memory footprint if we can :)"
1656386,2017-01-24 15:02:28 UTC,"Kevin, I've plotted couple of dstat outputs when problems started. Every time, I was able to confirm, that consumption of swap arose around the same time.
Now, I see it completely reversed."
1656386,2017-01-16 20:27:40 UTC,Happens also on tempest-neutron-full: http://logs.openstack.org/54/417954/8/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/8f50669/logs/syslog.txt.gz#_Jan_16_17_39_39
1656386,2017-01-24 05:54:20 UTC,"I mentioned on the mailing list, but it looks like we are hardly using any swap space at all. @Darek, where did you see that we are using lots of swap?"
1656386,2017-02-01 19:19:21 UTC,RSS is not quite the same as actual memory used. It overestimates it a lot.
1656386,2017-01-24 16:45:29 UTC,"Another one
http://logs.openstack.org/16/423416/2/gate/gate-tempest-dsvm-neutron-full-ubuntu-xenial/b3afd0e/logs/"
1656386,2017-01-26 22:58:47 UTC,http://eavesdrop.openstack.org/meetings/neutron_drivers/2017/neutron_drivers.2017-01-26-22.04.log.html
1656386,2017-01-17 15:39:38 UTC,e-r-query: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22oom-killer%5C%22%20AND%20tags%3Asyslog%20AND%20build_branch%3Amaster
1656386,2017-01-27 14:28:08 UTC,"From the neutron-drivers meeting, possible causes:"
1656386,2017-01-30 19:05:17 UTC,"We landed [1] on Jan 27th 3pm PST. Regrettably, I still see failures in logstash though [2,3]."
1656386,2017-01-30 19:11:30 UTC,At this point I wonder if something like is worth pursuing. At least that attempts to keep MySql memory footprint smaller.
1656386,2017-01-30 23:51:11 UTC,When OOM killer was invoked there was 186M swap used and 7626M free.
1656386,2017-01-31 22:20:44 UTC,wget http://logs.openstack.org/93/426793/1/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/2b47c1a/logs/ps.txt.gz
1656386,2017-01-27 14:12:02 UTC,Around 17hits/day now.
1656392,2017-05-08 16:34:11 UTC,"at least as of ubuntu 17.04 zesty/kgpg 4:16.08.3-1 there is an ""edit group"" that allows for this sort of thing."
1656394,2017-01-20 18:44:55 UTC,Fix package
1656394,2017-03-02 12:07:11 UTC,"I've got the same problem. LACP with Layer3+4 xmit_hash_policy. Setting up iperf with several parallel streams will use only one interface of the LACP bondX.
While there is not solution available to date, I installed Ubuntu 14.04 LTS were it's working without any problems!"
1656394,2017-10-25 08:26:13 UTC,"Kurt, did you check LACP on a newer Ubuntu Version, e.g. 17.10 already? I'm still on 14.04 LTS"
1656394,2017-10-25 13:30:41 UTC,"Hi Jan, sorry no I didn't check 17.10. I ended up using 10G nics for the time being. At some point I would like to bond those nics, but wont be able to due to this bug."
1656394,2017-01-15 18:31:59 UTC,More data for the report. Testing using a different program shows the same results. In this case I used a python program called getput to test the performance of an openstack swift node. All the source ports are even numbered in the netstat output which prevents LACP xmit_hash_policy layer3+4 to load balance the outgoing connections:
1656396,2017-01-18 14:32:40 UTC,Tracking here: https://github.com/conjure-up/conjure-up/issues/595
1656399,2017-02-20 10:42:37 UTC,"On 2017-02-20 08:27, flocculant wrote:

> really wish people wouldn't fiddle with bug status
"
1656399,2017-02-20 12:14:18 UTC,@Gunnar - thank you
1656399,2017-02-21 18:02:19 UTC,@robert - I've seen reports from xubuntu testers where it was sometimes working. So I tried more on a completely brand new installation.
1656399,2017-02-21 18:05:18 UTC,In my used and abused installation I see similar behaviour.
1656399,2017-02-20 07:27:19 UTC,really wish people wouldn't fiddle with bug status
1656399,2017-02-21 18:27:48 UTC,Same experience on my updated Lubuntu 17.04.
1656399,2017-02-07 23:37:44 UTC,This is effecting me on Xubuntu 17.04
1656399,2017-02-21 23:45:00 UTC,"Robert, any chance we can get this fix in Zesty Archive in debian/patches? I can help with packaging if needed (if you aren't working on it already)."
1656399,2017-02-21 23:51:16 UTC,Uploaded to zesty as 1.21.5-0ubuntu1.
1656399,2017-02-22 07:31:33 UTC,@ Robert - grabbed from -proposed.
1656399,2017-02-22 09:18:47 UTC,Installing 1.21.5-0ubuntu1 has solved the problem coming out from lock screen
1656399,2017-02-22 11:07:18 UTC,This bug was fixed in the package lightdm - 1.21.5-0ubuntu1
1656399,2017-02-27 08:56:19 UTC,The new version has fixed the issue for me!
1656399,2017-02-21 19:49:47 UTC,I'm also finding it to be unreliable. It seems to be a race condition between the greeter quitting and the session starting. I suspect the use of logind has made this race more likely.
1656399,2017-01-28 20:37:56 UTC,"It happens to me, too.
======================
Something (big) cropped up. When I returned to my NetBook, the screen had locked. Typed my password in. System then (visually) unlocked itself, paused briefly and then locked me back out again. You can test this more quickly by using the keyboard shortcut of CTRL+ALT+l"
1656399,2017-02-21 23:52:59 UTC,"The change fixes the issue for me, though of course it may not be the only issue affecting screen locking with light-locker (as per the original bug description). If you continue to have problems please comment here an open a new bug and we'll tackle further issues there. Thanks for all the great feedback in this bug!"
1656399,2017-01-26 16:17:02 UTC,This bug seems to affect Lubuntu Zesty alpha 2. It affects all Lubuntu test cases.
1656399,2017-01-26 22:18:41 UTC,"It turns out I can reproduce this with unity-greeter (on zesty). I get the following:
1. Log into session from greeter
2. Switch to greeter and log in again
(returned to session)
3. Switch to greeter and log in again
Switched to black screen, can manually VT switch back to session but need to unlock it from screen locker.
4. Switch to greeter and log in again
Returned to session, but screen locker shown."
1656399,2017-01-13 21:47:11 UTC,"The same behavior can be replicated by letting the screen lock itself due to idle, or by locking your workstation."
1656399,2017-01-14 08:50:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656399,2017-01-14 08:50:32 UTC,See this on desktop with nvidia.
1656399,2017-01-16 17:15:59 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1656399,2017-01-16 18:43:04 UTC,Downgraded lightdm packages as follows:
1656399,2017-01-16 20:29:04 UTC,however - seems locking fails in vm with 1.21.1-0ubuntu2
1656399,2017-01-13 19:57:39 UTC,Acer S7 - Intel Haswell Laptop with Intel GPU using i915 driver.
1656399,2017-01-16 20:47:40 UTC,attached lightdm.log following failure to unlock
1656399,2017-01-23 15:25:53 UTC,affects lubuntu
1656399,2017-01-23 15:36:04 UTC,Error in comment #7
1656399,2017-01-23 20:31:15 UTC,The change in there is:
1656399,2017-01-23 21:22:08 UTC,Actually the relevant part of the lightdm.log is:
1656399,2017-01-23 22:09:31 UTC,Greeter log
1656399,2017-01-25 20:33:54 UTC,Checked with gnome-screensaver and xscreensaver instead of light-locker.
1656399,2017-01-25 21:47:57 UTC,was going to check the budgie greeter - but that uses lightdm-gtk-greeter and fails the same as with other flavours
1656399,2017-01-21 17:07:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656421,2017-02-08 14:11:32 UTC,"To be quick about it, and to clarify:"
1656421,2017-02-08 14:47:39 UTC,"Thanks for that. I'll switch to the Nouveau driver.
I am considering changing the graphics card from the Nvidia Quadro FX 1400 I currently have if changing to Nouveau doesn't improve things"
1656421,2017-01-13 21:35:39 UTC,So this is my unsupported card now:
1656421,2017-02-08 13:25:44 UTC,"I have far less technical knowledge, only using Linux Mint 18 for a few weeks (after Windows XP) but I suffer exactly the same problem. My old HP XW6200 has an Nvidia NV41GL Quadro FX 1400 card"
1656421,2017-01-13 21:24:28 UTC,"The reason it installs the ""304 legacy"" driver is because my graphics card is not supported by any later driver."
1656422,2017-01-17 03:41:30 UTC,"Reviewed:  https://review.openstack.org/420190
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=57e460242000776eac9886186794d22e664d3fc8
Submitter: Jenkins
Branch:    master"
1656422,2017-01-13 21:21:34 UTC,Same output: http://logs.openstack.org/82/419182/1/check/gate-trove-scenario-dsvm-postgresql-single-ubuntu-xenial/c3b2863/console.html#_2017-01-13_00_04_07_056939
1656422,2017-01-13 21:49:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/420190"
1656428,2017-01-16 23:13:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420992"
1656428,2017-02-09 23:28:54 UTC,"Reviewed:  https://review.openstack.org/420992
Committed: https://git.openstack.org/cgit/openstack/puppet-ceph/commit/?id=108f5500adb38f5e8c2ddf271937ef184f57067a
Submitter: Jenkins
Branch:    master"
1656434,2019-07-08 07:10:03 UTC,"This failure looks to have been fixed as I cannot make this test to fail
locally and under stress."
1656437,2017-01-18 14:33:16 UTC,Tracked here: https://github.com/conjure-up/conjure-up/issues/596
1656437,2020-08-05 10:04:56 UTC,https://github.com/conjure-up/conjure-up/pull/625
1656440,2017-02-16 17:41:37 UTC,I agree that run_srb removes unnecessary code of making lists of args and passing to ringbuilder.main and its usage would help prevent fat-fingering.
1656440,2017-02-16 21:21:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435122"
1656440,2017-02-23 19:54:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437587"
1656440,2017-02-23 20:09:24 UTC,"Change abandoned by Nick Miethe (<email address hidden>) on branch: master
Review: https://review.openstack.org/435122
Reason: Taking a different approach at the fix"
1656440,2017-02-16 23:19:42 UTC,"To be 100% clear, this is not a trivial mechanical textual translation (no valuable refactor ever is).  I need someone to read/understand the test module and put on their thinking cap and *design* a better pattern."
1656441,2017-01-14 20:18:13 UTC,Gtk.Inhibit doesn't seem to work under either pantheon or gnome shell. On both desktop environments the display still turns off :/
1656443,2017-01-15 17:28:33 UTC,"No prob, just save from icon template"
1656443,2018-09-17 13:05:21 UTC,https://github.com/mixxxdj/mixxx/pull/1774
1656450,2017-01-31 23:24:10 UTC,"No, there isn’t. There are others, but nothing about notification-deamon or anything related."
1656450,2017-01-23 14:04:09 UTC,"ok, is there any crash report or log created in /var/crash? (be sure to enable apport)"
1656450,2017-01-21 12:50:49 UTC,I cannot not find this process when notifications stop working.
1656450,2017-01-17 14:10:02 UTC,notification-daemons is running or crash when it stop working?
1656455,2017-01-14 00:32:16 UTC,Topic was raised earlier this week on irc by Mc (see attached irc log excerpts).
1656455,2017-01-14 01:12:33 UTC,"(OT: Thank you, V. That log is impressive, the Inkscape project is so lucky to have y'all on board.)"
1656469,2017-01-14 00:35:42 UTC,"Pref for 17.01, but if required the absence of this data can be considered 'v0' as long as it's added before any backward incompatible format change."
1656469,2019-12-10 15:29:59 UTC,"We still haven't moved off of 'v0' in three years, so this has still not needed a change so far."
1656479,2017-01-16 18:31:08 UTC,"Reviewed:  https://review.openstack.org/420261
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a649311af7d01335aa7cf00fc180ba35ee77f6f3
Submitter: Jenkins
Branch:    master"
1656479,2017-01-27 00:51:32 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1656479,2017-01-14 01:43:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420261"
1656485,2017-06-28 16:38:21 UTC,https://github.com/elementary/scratch/issues/136
1656489,2019-01-07 10:13:01 UTC,Hello
1656489,2017-01-19 18:04:51 UTC,Live cd in chinese: Kylin 20170119.  Same result
1656489,2017-01-19 18:02:51 UTC,apport information
1656489,2017-01-19 18:02:49 UTC,apport information
1656489,2017-01-19 18:02:46 UTC,apport information
1656489,2017-01-19 18:02:44 UTC,apport information
1656489,2017-01-19 18:02:42 UTC,apport information
1656489,2017-01-19 18:02:39 UTC,apport information
1656489,2017-01-19 18:02:37 UTC,apport information
1656489,2017-01-19 18:02:30 UTC,apport information
1656489,2017-01-19 18:02:34 UTC,apport information
1656489,2017-01-19 18:02:32 UTC,apport information
1656489,2017-01-19 18:02:28 UTC,apport information
1656489,2017-01-18 16:19:45 UTC,"There is no relation between custom kernel and Ubiquity or the installer.  The bug is in today's build:  Same message on startup and Kylin opens in try Ubuntu in Chinese(20170117).
 Plus , fans and HDD are too noisy to run Zesty under 4.10, even 4.9.  I tried 4.10-rc4 when it came out and there was too many noises in Zesty or Xenial.  The Ubiquity team introduced this bug a month ago.  I don't have any of these issues under Windows 10."
1656489,2017-01-17 18:59:13 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1656489,2017-01-14 05:57:29 UTC,Journal from admin account.
1656489,2017-01-14 05:55:53 UTC,apport information
1656489,2017-01-14 05:55:51 UTC,apport information
1656489,2017-01-19 18:02:36 UTC,apport information
1656489,2017-01-14 05:39:16 UTC,apport information
1656495,2017-01-21 13:47:28 UTC,Thanks :)
1656495,2017-01-21 09:10:00 UTC,"I've uploaded the main icon/tree-1/tent-1 combination - it looks much better than it did, thanks!"
1656495,2017-01-18 11:41:30 UTC,This is how it looks with all trees green and size changes mentioned before. No changes in tents color yet.
1656495,2017-01-18 08:49:24 UTC,Thanks Michal!
1656495,2017-01-17 15:55:15 UTC,I made 3 images for tents and 3 for trees. I think it could be nice if they show up at random. I also made a new app icon according (more or less) to design guidelines for Ubuntu app icons. The app icon is in png format in few different sizes.
1656495,2017-01-16 12:38:39 UTC,Love the bug description
1656495,2017-01-18 11:05:58 UTC,Thanks for testing. :)
1656495,2017-01-16 09:49:39 UTC,I'll give it a try.
1656501,2017-01-24 13:54:31 UTC,"@Alex, is there something you can do with the PPA?"
1656501,2017-01-16 21:33:53 UTC,"(it's just a minor thing, so probably not worth a recompile, just for info, for 0.92.1)"
1656501,2017-01-16 21:32:27 UTC,Should we ping Alex Valavanis about this?
1656501,2017-01-16 02:28:12 UTC,"@Bart: this is the version from the ppa, right?"
1656501,2017-01-15 16:37:40 UTC,"The ""unknown"" string comes from ""CMakeScripts/inkscape-version.cmake""."
1656501,2017-01-15 15:40:57 UTC,Windows 32-bit build not affected (tested with the 7z version).
1656501,2017-01-16 08:59:34 UTC,"@Hachmann: correct, PPA https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable"
1656502,2017-01-15 15:30:52 UTC,"Reproduced on Windows XP (32-bit), lp:inkscape/0.92.x rev. 15318.
The blend mode adds an SVG filters that applies to a filter effect region which is bigger than the object. But while it's necessary for some filters (blur, displacement map...), I'm not sure we really need it here.
Could a filters expert confirm?"
1656517,2017-01-16 01:59:20 UTC,Sounds related to bug 1404643
1656532,2017-12-16 06:20:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656537,2017-01-16 09:31:15 UTC,"The core.publish_doctree method is provided by the docutils package, which is required by Packstack."
1656552,2017-01-14 22:35:18 UTC,"After running ""apt update"" and installing Ubuntu Software Center, it does not show the ""Install"" button in the already installed applications. But, the Update tab is still empty."
1656561,2017-01-15 21:17:57 UTC,"I updated the title and description from ""first beat"" to ""first downbeat""."
1656561,2017-01-14 20:31:43 UTC,In general a good Idea. The only problem is that we have a ¼ chance to make it right and hit a downbeat. If we implement it without a downbeat detection. It will we hard to distinguish CUEs manual set on a downbeat from automatically set on the first beat. The user cannot rely on his CUEs anymore.
1656571,2017-01-14 19:21:54 UTC,It happends to all LPE.
1656571,2017-01-14 19:39:14 UTC,"OK. Would be handy, though..."
1656571,2017-01-14 19:46:59 UTC,Yes. You undertand my proposal workarround?
1656571,2017-01-14 20:38:48 UTC,"Yes, I think so. First duplicate the path, then apply the LPE to the duplicate, and then snapping to the original is possible?"
1656571,2017-01-14 21:07:24 UTC,Yes!
1656571,2017-01-14 21:08:12 UTC,you can apply the LPE to the duplicate or to the original and snap into other.
1656571,2017-01-14 19:21:21 UTC,"Hi Bart, I try to explain:
The path you see is not a real path because is changed by the effect one so you can't snap with original paths of LPE because realy there isn't this path. Also you can't snap with the result of the LPE in the same item. Anyway you can snap to other paths -duplicating- if you need this snap."
1656581,2017-01-15 21:36:40 UTC,Using lmde betsy I see a similar but different problem. Perhaps this problem and the one I reported last week are related to a transition from python2 to python3? Link https://bugs.launchpad.net/linuxmint/+bug/1655210
1656581,2017-01-16 16:24:35 UTC,Thank you so much for answering this problem for me. I had this exact same issue but your mention of
1656585,2019-12-22 13:40:45 UTC,"I’ve checked the code, and unfortunately I’m unable see how the comments
could possibly have any bearing on the behaviour. In any case I am
unable to reproduce this with opendkim version 2.11.0~alpha-11 (Ubuntu
18.04)."
1656585,2017-03-10 14:31:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656585,2020-02-21 04:17:25 UTC,[Expired for opendkim (Ubuntu) because there has been no activity for 60 days.]
1656590,2020-09-29 15:19:23 UTC,"Yup, it's fixed!"
1656590,2020-09-29 09:26:56 UTC,"The PR  https://github.com/mixxxdj/mixxx/pull/3138 is merged now.
Can we consider this bug as ""Fix Committed"" now?"
1656590,2020-09-28 15:55:34 UTC,@ronso0
1656590,2020-09-28 01:12:21 UTC,"@edwardmillen
Could you set up a PR at https://github.com/mixxxdj/mixxx/pulls against the 2.3 branch?
There we can discuss the code much better."
1656590,2020-08-22 09:16:56 UTC,"I've just had a look into this because I've noticed this too and I was curious. It seems like the behaviour for ""cue_gotoandstop"" has already been fixed at some point, as I can't reproduce the issue with that in the current master branch from GitHub (i.e. it always stops at the cue point)."
1656590,2020-06-06 03:41:23 UTC,resumé 3 years after I noticed this bug:
1656590,2017-01-15 08:12:10 UTC,"To clarify: for a year or so I considered this a feature rather than a bug, because one could instantly play from hotcue when a track finished before the transition was done."
1656590,2018-03-05 12:41:46 UTC,"Still valid, still annoying unexpected behaviour: when triggering hotcues after the track has finished the deck would play on regularly"
1656590,2018-03-05 12:58:17 UTC,"To Preview from a HotCue you hold down the button, entering Play mode is not Previewing. And please don't make it so you have to hit the HotCue twice as then you can't play different phrases by Previewing different HotCues."
1656590,2017-01-16 16:57:43 UTC,"I was also confused, but I don't think hotcue previewing is the problem described (and we wouldn't want to remove it)."
1656590,2017-01-16 18:52:26 UTC,I'm afraid you got me wrong: all the previewing features are perfect!!
1656590,2017-01-16 15:30:52 UTC,Do you mean cue_gotoandstop? So the problem is that CO starts previewing from the cue point? I think previewing from hotcues is a desirable feature.
1656590,2017-01-16 22:25:03 UTC,"If you're not aware, you can press play while previewing to keep playing after releasing the (hot)cue button."
1656590,2017-01-17 13:39:13 UTC,"> you can press play while previewing to keep playing
Jep, I do it like this sometimes and mention it when introducing friends to mixxx :)
"
1656590,2017-01-16 19:02:08 UTC,"Actually, I find it very convenient to instantly start previewing with one button press (and hold).
Imagine you have track with some quotes you'd want to throw in like with a sampler deck: with a second click to play it, it would become harder to do it 'on beat' in a spontaneous way."
1656599,2017-01-17 21:52:30 UTC,The same thing happens with ubuntu-bug sane-backends or ubuntu-bug software-properties.  I think it would happen with any source package without a corresponding binary package name.
1656599,2017-01-17 21:53:58 UTC,"Although I believe a package with an apport package hook, like ubuntu-release-upgrader, works around this issue."
1656605,2017-02-10 17:45:23 UTC,"I built a 3.15.0-0.1 kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1656605/"
1656605,2017-02-06 15:23:27 UTC,Can you test 3.16.0-23.31:
1656605,2017-02-07 12:30:43 UTC,Build 3.16.0-23 has the reported defect. Purged back off.
1656605,2017-02-07 17:40:45 UTC,"I built a 3.16.0-0.1 kernel.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1656605/"
1656605,2017-02-07 23:16:33 UTC,There does not appear to be i386 files in that directory.
1656605,2017-02-08 18:49:30 UTC,I built a 64 bit kernel.  The 32 bit one is there now.
1656605,2017-02-08 20:51:50 UTC,Build 3.16.0-0.1 has the reported defect. Purged back off.
1656605,2017-02-10 19:30:12 UTC,Looks like build 3.15.0-0.1 still has the issue. It also would not boot correctly... landed the server at a busybox type interface.
1656605,2017-04-12 12:14:31 UTC,We have now built brand new servers with Ubuntu Server 16.04 x64. The initial state of the /etc/default/grub file is:
1656605,2017-02-12 21:07:58 UTC,"Correct, 3.13.0-9.29 boots with appropriate ""Ubuntu ...."" text, then lands at a busybox type interface."
1656605,2017-02-16 18:43:01 UTC,"This may have been introduced by commit 4ae5bd9.  However, I'd first like to see if this is expected and not a bug."
1656605,2017-02-17 16:09:09 UTC,"Excellent find, Joseph!"
1656605,2017-04-12 15:20:32 UTC,"@Joseph, Do you mean incomplete based on this bug report needing to morph into an issue against the 14.04 to 16.04 LTS upgrade process?"
1656605,2017-04-12 17:28:50 UTC,"Correct, it doesn't sound like this is a kernel bug, so I added the upgrade package."
1656605,2017-06-02 13:38:34 UTC,"I just tested a Xubuntu 14.04 x64 LTS upgrade to Xubuntu 16.04. The value:
GRUB_CMDLINE_LINUX_DEFAULT=""quiet splash""
is correct for Xubuntu. That is what causes the boot process to have the GUI screen rather than text console messages."
1656605,2017-02-03 22:52:46 UTC,Yes that v3.13.0-108.155 kernel build boots up with the expected Ubuntu .... splashscreen. Though would not boot up all the way cleanly... went into busybox.
1656605,2017-02-10 20:41:41 UTC,"There was never a 3.14 based Ubuntu kernel released, so we may be at the two bisectable versions."
1656605,2017-02-02 22:38:40 UTC,The 3.19.0-80 kernel build still has the defect. I purged it back off our server. Booted back to 4.4.0-59.
1656605,2017-02-03 19:22:02 UTC,"It looks like I'll have to build some kernels in between 3.13 and 3.19.  Just as a confirmation, can you ensure the latest Trusty kernel does not have the bug:"
1656605,2017-02-02 13:26:18 UTC,Sorry... defect is yet persisting with the 4.2.0-16.19 kernel build. I purged it back off our server. Booted back to 4.4.0-59.
1656605,2017-01-15 11:47:33 UTC,"Ah, a notable difference between the hardware spec of the test servers and the real servers:"
1656605,2017-01-17 18:56:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1656605,2017-01-18 13:08:29 UTC,"Yes, working perfectly! Trying to remember how I set tags. Here is the output of applying the test kernel:"
1656605,2017-01-24 12:58:32 UTC,"Question: So is there hope of getting this fixed in the default kernel version for the 16.04 release, or is it going to be addressed only with the ""Ubuntu 16.04.2 LTS Point Release Coming On Feb 2 With Linux Kernel 4.8"" newer kernel?"
1656605,2017-01-25 16:19:28 UTC,"Thanks for the update. We can perform a ""Reverse"" bisect to identify the commit that fixes the bug in v4.10-rc4. We first need to identify the last bad kernel and first good one."
1656605,2017-01-25 23:00:04 UTC,"Excellent, first try lucky. I downloaded all three requested kernel packages. Started with the:"
1656605,2017-01-26 13:19:41 UTC,"Can you also confirm the bug does indeed happen with the upstream 4.4 final kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/"
1656605,2017-01-26 22:59:23 UTC,"OK, I got the first kernel (v4.4-wily) validated that it works properly. I IPL'ed back to the 4.4.0-59 to validate the problem had not suddenly vanished, still there."
1656605,2017-01-15 11:38:48 UTC,A friend advised me to check two more outputs between a 14.04 server and 16.04 impacted server. Attaching the following additional outputs:
1656605,2017-01-27 18:37:15 UTC,"No need to test the 4.5-rc1 kernel.  Because v4.4-wily is good, we can not bisect between 4.4 and 4.5-rc1.  It also means that the bug was introduced by one of the 4.4 stable updates, or by an Ubuntu specific SAUCE patch."
1656605,2017-01-28 18:46:18 UTC,Wowsers... this bug is already present in linux-image-4.4.0-1-generic!
1656605,2017-01-28 20:14:27 UTC,"... and I was not suppose to be booting from a lower entry than the top entry for the particular kernel build I am testing, was I? Top has no suffix text, next one I believe was labeled ""Upstart"" and third was ""Recovery""."
1656605,2017-01-30 15:47:47 UTC,"Yes, the top entry in GRUB is the one to boot."
1656605,2017-01-31 20:34:20 UTC,Same defect with both the https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11923303 and https://launchpad.net/ubuntu/+source/linux/4.3.0-7.18 kernel builds.
1656605,2017-01-31 20:52:15 UTC,"Can you test the 4.2.0-19.23 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/8287821"
1656605,2017-01-31 23:36:38 UTC,"Tested 4.2.0-19.23 kernel, same issue. Purging it off."
1656605,2017-02-01 16:59:39 UTC,"Correct, the v4.4-wily kernel is an upstream version of the kernel with no Ubuntu customization.  That is the reason we need to go back in time and test the older Ubuntu kernels to find the specific version when the bug was introduced.  That will allow us to bisect and find the exact commit that caused the regression."
1656605,2017-01-15 04:00:10 UTC,This change was made by a bot.
1656605,2017-01-27 19:31:18 UTC,Noted you want me to test the Yakkey(16.10) kernel specified.
1656605,2017-02-02 20:02:35 UTC,"Can you test the following 3.19 based kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11849331"
1656606,2017-01-15 14:06:20 UTC,"My suspicion is that there's something wrong with pantheon-greeter, but I'm not completely certain."
1656606,2017-01-15 14:05:21 UTC,This issue affects me on both Elementary OS Loki and Pantheon Desktop on Fedora 25. The frequency of the issue is much higher for me (~35-50% depending on the install) and I have no HiDPI systems. Some of them are even VMs and it still happens.
1656606,2017-01-27 07:42:25 UTC,I'm also having rather high percentage of these hangs as well on several of my computers but on one laptop I'm pretty sure that never happend.
1656618,2017-01-16 21:19:24 UTC,apport information
1656618,2017-01-16 21:19:26 UTC,apport information
1656618,2017-01-16 21:19:29 UTC,apport information
1656618,2017-01-16 21:19:32 UTC,apport information
1656618,2017-01-16 21:19:36 UTC,apport information
1656618,2017-01-17 18:55:22 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1656618,2017-01-18 01:06:47 UTC,"Bug still present in upstream kernel.
""On a sidenode, touchpad and built-in keyboard do not work with 4.10-rc3. on boot dmesg shows the i2c_hid module ""failed to reset device"". When the laptop is finished booting, pressing one key on the built-in keyboard instantly powers off the laptop."""
1656618,2017-01-18 02:37:49 UTC,Some of the folks working on getting the sound to work also noticed that something in kernel 4.9 is also preventing the keyboard and touchpad from working as well.
1656618,2017-01-18 09:58:33 UTC,"Wait, as harryharryharry, I can confirm that mainline kernel 4.9.0-040900.201612111631 works without problems. So the problem is only present in 4.8 ubuntu line and 4.10, so maybe the problem is caused by some backported code from mainstream, maybe security patch.
So, could be this change reported in
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-edge/linux-hwe-edge_4.8.0-34.36~16.04.1/changelog"
1656618,2017-01-18 21:25:19 UTC,"and with dyndbg==pmf enabled while loading the module:
<7>[  857.237099] i2c_hid:i2c_hid_init_irq: i2c_hid i2c-PDEC3393:00: Requesting IRQ: 195
<3>[  868.461393] i2c_hid i2c-PDEC3393:00: failed to reset device.
<3>[  880.840464] i2c_hid i2c-PDEC3393:00: failed to reset device.
<4>[  881.884430] i2c_hid: probe of i2c-PDEC3393:00 failed with error -61"
1656618,2017-01-19 17:03:59 UTC,"adding i2c_hid.debug=1 as a boot parameter gives the following output:
[    4.572059] i2c_hid i2c-PDEC3393:00: Fetching the HID descriptor
[    4.572065] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f1 00
[    4.575576] i2c_hid i2c-PDEC3393:00: HID Descriptor: 1e 00 00 01 b4 00 f2 00 f3 00 0e 00 f4 00 04 00 f5 00 f6 00 05 0b 85 85 01 00 00 00 00 00
[    4.575685] i2c_hid i2c-PDEC3393:00: entering i2c_hid_parse
[    4.575689] i2c_hid i2c-PDEC3393:00: i2c_hid_hwreset
[    4.575692] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[    4.575695] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 08
[    4.581210] i2c_hid i2c-PDEC3393:00: resetting...
[    4.581214] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 01
[    4.581660] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: waiting...
[    9.701087] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: finished.
[    9.701099] i2c_hid i2c-PDEC3393:00: failed to reset device.
[    9.708842] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[    9.708854] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 01 08
[   10.714178] i2c_hid i2c-PDEC3393:00: i2c_hid_hwreset
[   10.714190] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[   10.714201] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 08
[   10.714821] i2c_hid i2c-PDEC3393:00: resetting...
[   10.714833] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 01
[   10.718836] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: waiting...
[   15.887586] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: finished.
[   15.887597] i2c_hid i2c-PDEC3393:00: failed to reset device.
..............
..............
[   29.294255] i2c_hid: probe of i2c-PDEC3393:00 failed with error -61
[   29.465100] i2c_hid i2c-ELAN0100:00: Fetching the HID descriptor
[   29.465104] i2c_hid i2c-ELAN0100:00: __i2c_hid_command: cmd=01 00
[   29.468290] i2c_hid i2c-ELAN0100:00: HID Descriptor: 1e 00 00 01 6a 00 02 00 03 00 1e 00 04 00 00 00 05 00 06 00 f3 04 01 04 0a 00 00 00 00 00
[   29.596520] i2c_designware 80860F41:04: I2C bus managed by PUNIT
[   29.772290] elan_i2c i2c-ELAN0100:00: Elan Touchpad: Module ID: 0x0026, Firmware: 0x000a, Sample: 0x0001, IAP: 0x0000
[   29.773767] input: Elan Touchpad as /devices/platform/80860F41:03/i2c-11/i2c-ELAN0100:00/input/input7
[   31.145688] elan_i2c i2c-ELAN0100:00: Elan Touchpad: Module ID: 0x0026, Firmware: 0x000a, Sample: 0x0001, IAP: 0x0000
[   31.145966] input: Elan Touchpad as /devices/platform/80860F41:03/i2c-11/i2c-ELAN0100:00/input/input11"
1656618,2017-01-24 01:58:17 UTC,"I found the patch that causes the keyboard to malfunction !:
https://www.spinics.net/lists/linux-gpio/msg18340.html"
1656618,2017-04-01 07:43:38 UTC,"Last working kernel for me was 4.8.0-32 (still using it). In addition to any key triggering the shutdown dialog, the system is unstable. Various buttons on onboard causes the cursor to freeze (and keys to repeat indefinitely). I can unfreeze it by pressing something on the keyboard, which brings up the dialog and unfreezes the cursor so I can click cancel on the dialog and resume."
1656618,2017-04-03 14:10:34 UTC,Does blacklist 'i2c-hid' make the issue gone?
1656618,2017-01-16 21:19:23 UTC,apport information
1656618,2017-04-12 15:28:12 UTC,"Looks like there is a keyboard related patch but not upstreamed yet:
https://bugzilla.kernel.org/show_bug.cgi?id=95681#c223"
1656618,2017-01-18 21:22:49 UTC,"the OOB write fix was submitted in march 2016, so I doubt that has anything to do with it."
1656618,2017-01-16 21:19:21 UTC,apport information
1656618,2017-04-12 02:12:19 UTC,Blacklisting 'i2c-hid' does not resolve the issue.
1656618,2017-01-16 21:19:17 UTC,apport information
1656618,2017-01-15 07:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1656618,2017-01-15 18:45:12 UTC,apport information
1656618,2017-01-15 18:45:15 UTC,apport information
1656618,2017-01-15 18:45:18 UTC,apport information
1656618,2017-01-15 18:45:20 UTC,apport information
1656618,2017-01-15 18:45:22 UTC,apport information
1656618,2017-01-15 18:45:25 UTC,apport information
1656618,2017-01-15 18:45:28 UTC,apport information
1656618,2017-01-15 18:45:30 UTC,apport information
1656618,2017-01-16 21:19:19 UTC,apport information
1656618,2017-01-15 18:45:35 UTC,apport information
1656618,2017-01-16 21:19:16 UTC,apport information
1656618,2017-01-16 21:19:14 UTC,apport information
1656618,2017-01-16 21:19:12 UTC,apport information
1656618,2017-01-16 21:16:58 UTC,I performed a fresh install of Xubuntu 16.10 and can confirm that this bug also exists in that installation. It is also using linux-image-4.8.0-34 as its default kernel package.
1656618,2017-01-15 18:45:32 UTC,apport information
1656618,2017-01-15 18:45:42 UTC,apport information
1656618,2017-01-15 18:45:40 UTC,apport information
1656618,2017-01-15 18:45:37 UTC,apport information
1656618,2017-01-15 18:45:45 UTC,apport information
1656626,2017-01-16 18:31:33 UTC,I'll take a screenshot for explanation.
1656626,2017-01-19 12:04:04 UTC,"Please, have a look at this screenshot
http://ibb.co/h8U2aa"
1656626,2017-01-19 22:14:24 UTC,Can't you use a MinimumExpanding spacer to push them to the right?
1656626,2017-01-19 22:17:17 UTC,Nevermind the above comment; I misunderstood.
1656626,2017-01-23 15:54:05 UTC,"Yes, I see what confuses you. But on the other hand, users might expect (and accept) that there's no reasonable way to control an 8-parameter effect with 3 knobs."
1656626,2017-03-09 16:50:45 UTC,"I don't need this feature anymore for the skin, just aligned them normally.
But I still think this could be useful to react on the number of parameters."
1656626,2017-01-16 15:28:06 UTC,I don't understand what value this would add. Can you elaborate on why it would be useful?
1656629,2017-02-07 18:32:38 UTC,"Change abandoned by garyk (<email address hidden>) on branch: master
Review: https://review.openstack.org/420394
Reason: aiafw"
1656629,2017-01-15 09:16:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420394"
1656629,2017-01-18 21:19:45 UTC,"Is this not a duplicate of [1]? Further, hasn't commit 175bfe048283ae930b60b1cea87874d1fa1d10d6 been reverted already by [2]? Seeing as you helped merge 2, I'm guessing you know what you're doing, just trying to understand myself."
1656642,2020-10-11 17:11:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656642,2020-10-11 17:18:06 UTC,"Ubuntu 14.04.5 LTS
Perhaps this should be a new bug if the version is different After doing the ESM changes (A real ridiculous pain in the *), as mine is Package samba 2:4.3.11+dfsg-0ubuntu0.14.04.20+esm9
Samba opens but when connect is clicked it just goes away and nothing happens. NOW I have several units I cannot connect or browse"
1656642,2020-10-12 14:29:54 UTC,"The old bug missed details about the used configuration and the actual crash happening.
Logs, Configs, ... - so it is nearly impossible to decide if it is the same or a different bug."
1656645,2017-02-05 14:23:18 UTC,"Frank, wouldn't it make more sense if you reported this bug? After all I am just a humble end user. I have no idea about the libraries this project uses."
1656645,2017-01-15 17:51:37 UTC,Hmm. There is also the question why this log entry is logged at all. Please report this bug upstream. github.com/nextcloud/server
1656646,2017-01-16 14:47:21 UTC,Such a link would need to be set in the Ghostscript package.
1656646,2017-01-15 12:51:29 UTC,found the solution on https://ubuntuforums.org/archive/index.php/t-2323285.html
1656658,2017-08-11 03:06:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656658,2019-04-21 07:21:03 UTC,same here
1656659,2017-01-17 10:17:50 UTC,"There was a remaining upgrade of some apport packages, and I think this has fixed the issue now."
1656659,2017-02-14 19:29:43 UTC,I have same problem on notebook HP650. But only with HWE kernel and Xorg. Sometimes wakeup of system is crashed (freeze).
1656659,2017-04-18 20:18:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656659,2017-05-08 18:11:41 UTC,"@frail-knight, please stop marking bugs as affecting dell-sputnik unless you are absolutely sure they're relevant"
1656662,2017-01-18 14:42:20 UTC,https://github.com/conjure-up/conjure-up/issues/611
1656663,2017-01-15 17:06:03 UTC,"Please attach a test case (original Inkscape SVG file, optimized SVG saved with Inkscape 0.91) to the bug report to allow further investigation, thank you."
1656663,2017-01-15 19:26:47 UTC,"The attached pair are previous versions of the same drawing, all from
version 0.91."
1656663,2017-01-15 19:33:48 UTC,"As for the Scour part of 4. I just filed
https://github.com/scour-project/scour/issues/127"
1656663,2017-01-15 19:50:42 UTC,"Regarding sample file from comment #4:
- First of all you have to set the document units to ""px"" (otherwise you'll always hit number 1 above)
- Even then Scour will not yet remove width/height attributes as your sample file suffers from rounding errors in Inkscape: Original width=""155.22223mm"" which is 550.00002px (rounded to 8 significant digits) and this is the exact number set in the viewBox attribute. However if you change your document's units back to ""px"" Inkscape will round the 550.00002px down to 550px which differs from the value in the viewbox and therefore will be kept by Scour."
1656663,2017-01-17 05:37:38 UTC,"In view of your comments, I suspect that the present Scour will NEVER unset
width/height in my files. Reason: I don´t usually make original work, but
copy a map or a diagram from an existing illustration, Thus, I begin by
importing into a layer the original (usually a scanned file, more or less
edited with GIMP) AND asking Inkscape to resize to drawing.
As a matter of fact, I never look at dpi or page size (I usually unset
print resolution of pictures from Irfanview, as I never print): thus, the
only dimensions that make sense to me are the screen pixels, and those vary
with each picture.
As the final SVG is intented for an EPUB, the sensible approach (at least
for old people with failing eyesight) is to let maps strech as fully as can
be contrived without losing the proportions. And, if one doesn't want the
image full-screen, a DIV with ""height=50%"" or whatever, does the trick very
nicely for SVGs with viewBox AND height/width 100%.
Of couse, people targetting printers, instead of screens, have very
different needs--I dare say that's why Inkscape always tries to begin in a
page with some standard dimension or other...
Many thanks for your explanation."
1656663,2017-01-15 18:32:18 UTC,"I hsve just installed version 0.92, and--yes: saving as Optimizad SVG,
option ""viewBox"" DOESN'T default width/height to 100%. Result: no
stertching when put into an html <img />, as shown in the atttachments:
HerringsPMap.svg is the Inkscape SVG (made with version 0.91, opened and
re-saved from version 0.92); HerringsPMapO.svg comes from 'save a copy as
Optimized SVG"".
Note: changing from the new version, at document level, default units to
px, has resulted in height/width with no units (px being the html default)
BUT they are set, nevertheless.
Many thanks."
1656663,2017-01-15 19:12:50 UTC,"First of all the option was initially intended to add a viewbox if it was not present. Since Inkscape always adds a viewbox nowadays Scour can not freely rewrite it and additional care has to be taken not to rewrite the ""viewBox"" attribute in a way that might not be expected."
1656669,2017-01-29 08:49:30 UTC,I did not think of stopped buildings while implementing the soldier exchange -> genuine bug.
1656669,2017-01-29 13:54:08 UTC,"I take that back. The soldier exchange happens at program_end(), which should not be repeatedly called when the site is stopped."
1656669,2017-02-02 20:34:13 UTC,"No, no training is happening, but food and helmets required for training are present."
1656669,2019-09-16 14:29:14 UTC,Migrated to https://github.com/widelands/widelands/issues/1663
1656670,2017-01-22 14:43:56 UTC,"I see a crash in dmesg if I do twice “modprobe my_module”. On the terminal I see always the  same error message: “modprobe: ERROR: could not insert 'my_module': Device or resource busy “. ""lsmod | grep my_module"" returns always no results"
1656670,2017-01-21 12:51:42 UTC,Assigned it to package linux-lts-xenial
1656670,2017-01-15 21:34:09 UTC,"Hi Hans Joachim,
Yes, Ubuntu is correct. Sorry, this was my mistake. Thanks,
Best regards"
1656670,2017-01-15 18:59:16 UTC,Hello :)
1656670,2017-01-16 19:04:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656673,2017-01-27 00:51:19 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1656673,2017-02-10 23:40:22 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/420461
Reason: This is turning out to be a mess and our docs on master point out the change here, so I'm just going to drop it."
1656673,2017-05-26 00:22:04 UTC,"Reviewed:  https://review.openstack.org/420461
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9a3c3fcff89828b7df45149c2d0ee188f439e46
Submitter: Jenkins
Branch:    stable/newton"
1656673,2017-05-30 16:05:12 UTC,This issue was fixed in the openstack/nova 14.0.7 release.
1656673,2017-01-16 01:20:43 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/420461"
1656673,2017-01-17 01:50:07 UTC,"Reviewed:  https://review.openstack.org/420439
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5b44737e0c4627b796cfcf09bff5008ae06a95ff
Submitter: Jenkins
Branch:    master"
1656675,2017-01-15 19:11:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420440"
1656675,2017-01-16 21:38:38 UTC,"Reviewed:  https://review.openstack.org/420440
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4bfc5502611d3f04f8b748769e82f37f8477e664
Submitter: Jenkins
Branch:    master"
1656675,2017-01-27 00:51:23 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1656676,2019-10-23 14:34:30 UTC,"This has been fixed here already:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=baf2d5bfbac#patch6"
1656680,2017-01-17 18:53:04 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1656680,2017-01-16 17:01:32 UTC,apport information
1656680,2017-01-16 17:01:30 UTC,apport information
1656680,2017-01-16 17:01:28 UTC,apport information
1656680,2017-01-16 17:01:26 UTC,apport information
1656680,2017-01-16 17:01:25 UTC,apport information
1656680,2017-01-16 17:01:16 UTC,apport information
1656680,2017-01-16 17:01:22 UTC,apport information
1656680,2017-01-16 17:01:21 UTC,apport information
1656680,2017-01-16 17:01:19 UTC,apport information
1656680,2017-01-16 17:01:13 UTC,apport information
1656680,2017-01-16 17:01:11 UTC,apport information
1656680,2017-01-15 18:30:15 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1656680,2017-01-16 17:01:23 UTC,apport information
1656680,2017-01-16 17:01:14 UTC,apport information
1656682,2017-01-15 19:04:40 UTC,"Backtrace with empty stylesheet, using lp:inkscape/0.92.x r15317"
1656693,2017-02-09 15:33:59 UTC,Shouldn't the installer verify that constraint before proceeding through a process that is doomed to fail?
1656693,2017-02-22 14:16:09 UTC,Probably.
1656693,2017-02-09 14:20:27 UTC,"It looks like you did manual partitioning, chose to use encryption, and did not create a /boot partition, which is currently required to boot from an encrypted root."
1656694,2017-01-15 20:33:25 UTC,I can not install; ttf-mscorefonts-installer
1656694,2017-01-20 14:59:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1656695,2017-01-15 20:46:26 UTC,"Please always include information about OS/platform and Inkscape version in the bug description when filing new reports, thank you."
1656695,2017-01-15 20:59:17 UTC,Running Inkscape 0.92 on Windows 7 64x. Attached original SVG.
1656695,2017-01-15 21:46:59 UTC,"You're absolutely right that there is room for improvement and this is actually on the todo-list, see [1] for the relevant code section and the list of attributes Scour currently moves to a parent group."
1656695,2017-01-15 23:06:04 UTC,"I made it with Inkscape 0.91, although I suspect myself of a very
amateurish way to achieve the result:
1. Layer with scanned image to use as pattern (is a book illustration).
2. Layer 'Squares': beginning with a single square, no fill, black stroke,
tile clones 15x1, trial-and-error to pick displacement; group and repeat
with inverse values for 1x15. Then, having forgotten about fill and stroke
left 'unset', un-link the clones, and select the squares to be filled black
and grey.
3. Layer for numbers: put by hand, extensive alignment and distribution;
font for roman numerals selected through NexusFont.
4. Layer for letters, ditto.
5. Remove the layer (1), and convert the groups by color in (2) to paths,
to slim the file--it took out some 20Kb.
I never attempted to vector the image in (1): unless I can manage a very
simple image in very few colors (i.e., a mute map as indexed PNG), the
result of converting to path, either in Inkscape or (by selection) in GIMP,
is not very much to my taste. Of course, we retired persons have time for
hobbies.
Would a slimmer result obtain from converting to vector, for instance, an
exported to PNG copy of layer (2)?
It may be worth trying..."
1656696,2019-10-03 10:32:44 UTC,"This will partly solve the problem, which is actually more complex to make automatic (re)connection work in a nice way. See:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833929#40
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932042"
1656696,2019-10-03 08:43:10 UTC,There is a probable fix in https://bugs.launchpad.net/wicd/+bug/1709593
1656696,2019-10-03 02:00:14 UTC,"Wow, I just went to report this again and launchpad prompted me to take a look at a related bug... turns out it's my exact bug from 2.75yrs ago. This is still an issue and still annoying. If wicd-gtk is open, wicd will not automatically connect to networks upon resume. If wicd-gtk is *not* open, the automatic connection will occur (when that option is marked for the network, obviously)."
1656711,2020-11-08 09:06:27 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1656711,2021-01-08 04:17:19 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1656712,2017-04-05 15:21:00 UTC,This bug was fixed in the package flatpak - 0.8.2-1~ubuntu16.10.1
1656712,2017-04-05 15:20:57 UTC,"The verification of the Stable Release Update for ostree has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1656712,2017-04-05 15:20:51 UTC,This bug was fixed in the package ostree - 2016.15-2ubuntu1~ubuntu16.10.1
1656712,2017-04-04 13:41:14 UTC,"The flatpak autopkgtest is working now for yakkety. Thanks slangasek, who retried using the proposed flatpak."
1656712,2017-02-23 11:08:33 UTC,"Hello. Is there any plan to update also the accompanying xdg-desktop-portal & xdg-desktop-portal-gtk packages? Without these, some functionality of desktop apps might not work properly, e.g. proxy settings, file chooser dialogs and opening URIs."
1656712,2017-03-27 07:18:03 UTC,ostree is showing autopkgtest regressions in Yakkety. Please could you take a look?
1656712,2017-03-18 04:06:28 UTC,"I tried installing Clocks with Flatpak but I got an error because apparently its gsettings schema wasn't installed, so I installed Iagno instead. I then upgraded Flatpak to 0.8.2-1ubuntu16.10.1 (and ostree 2016.15-2ubuntu1~ubuntu16.10.1) and verified that I could still run the Iagno flatpak and that the gnome and gnome-apps remote sources were still set up."
1656712,2017-02-23 14:18:19 UTC,"Jiří, yes it sounds like a good idea. Are you interested in opening the bug for that? Do you have a test case to verify that the functionality works?"
1656712,2017-02-15 00:40:41 UTC,"Hello Jeremy, or anyone else affected,"
1656712,2017-02-15 00:37:26 UTC,"Hello Jeremy, or anyone else affected,"
1656712,2017-03-27 09:17:20 UTC,It's not a real regression.
1656714,2018-07-30 10:22:50 UTC,"I tested this last night on my desktop running 16.04. I've done the quick test on my laptop today, with the same result, after installing Geoclue 2:"
1656714,2018-07-29 23:47:17 UTC,I'm getting this error in Ubuntu 16.04 after applying the patch:
1656714,2018-07-30 08:43:02 UTC,"On Sun, Jul 29, 2018 at 11:47:17PM -0000, David Planella wrote:

> I'm getting this error in Ubuntu 16.04 after applying the patch:
>
> https://pastebin.ubuntu.com/p/MwtMP6PHnd
>
> This is with geoclue-2.0 and gir1.2-geoclue-2.0 installed.
>
> TL;DR
> ImportError: Typelib file
> /usr/lib/x86_64-linux-gnu/girepository-1.0/Geoclue-2.0.typelib for
> namespace 'Geoclue' contains version '1.0' which doesn't match the
> expected version '2.0'
"
1656714,2018-07-30 10:23:13 UTC,(with the laptop also running 16.04)
1656714,2018-07-29 21:40:41 UTC,"Thanks a lot for the patch, I'll look into it shortly."
1656716,2017-01-16 00:03:18 UTC,bug 1656262 is an instance of this.
1656721,2017-01-16 00:23:14 UTC,"Attaching following outputs
cat /proc/bus/input/devices > ~/devices
xinput --list > ~/xinput
cat /var/log/Xorg.0.log > Xorg.0.log"
1656729,2017-02-26 08:34:21 UTC,"Uploaded package to trusty, yakkety and xenial backports. Works without change on xenial atleast when checked"
1656729,2017-01-16 15:57:50 UTC,Call for testing was issued to pump.io community: https://identi.ca/alpacaherder/note/uRdYA0UyQCqk9Nwi6jqZ_w
1656729,2017-04-14 08:28:11 UTC,@Backports team: Kindly request you to approve the upload.
1656729,2017-02-26 08:39:29 UTC,Unsubscribing sponsors for now.
1656744,2017-01-16 06:12:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420509"
1656744,2017-03-10 02:25:21 UTC,"Change abandoned by Nam Nguyen Hoai (<email address hidden>) on branch: master
Review: https://review.openstack.org/420509"
1656749,2017-01-16 18:51:43 UTC,"The actual error seems to be in the parameters passed to mount.nfs, not the fact that a symlink is involved:"
1656749,2017-01-17 02:14:26 UTC,"Here is part of my cinder.conf.
[DEFAULT]
backup_driver = cinder.backup.drivers.nfs
backup_share = 192.168.2.207:/slink/NfsVolumeStorage
backup_mount_point_base = /rhome"
1656749,2017-01-17 02:17:12 UTC,And the version of my openstack environment is newton.
1656749,2017-01-17 02:22:18 UTC,"If we replace  192.168.2.207:/slink/NfsVolumeStorage with  192.168.2.207:/NfsVolumeStorage in cinder.conf, then it works.
It seems that cinder couldn't recognize a path having symbolic link."
1656750,2017-01-17 08:43:43 UTC,Thank you Luo. I see it now. Fixed in 1266b6cd0fdf2320061e59b30b129e60002ad0d9.
1656750,2017-01-16 09:29:22 UTC,I just checked the entire revision history for that file. Never was it marked for DEVID_BLACKLIST for device types. It must have been a copy/paste error at your end.
1656750,2017-01-17 08:13:19 UTC,"Please ref
https://git.launchpad.net/laptop-mode-tools/tree/etc/laptop-mode/conf.d/runtime-pm.conf"
1656750,2017-01-16 09:24:03 UTC,What version of Laptop Mode Tools are you using ? ON what distribution ? Did you install from source ?
1656753,2019-09-12 13:06:00 UTC,We now have a list of unbuildable images.
1656764,2017-01-16 09:00:21 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/420584"
1656764,2017-01-17 09:22:25 UTC,"Reviewed:  https://review.openstack.org/420584
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=2f560f0b463cf32453bc1cb7840defdb3e3424f8
Submitter: Jenkins
Branch:    stable/newton"
1656764,2017-02-01 09:39:02 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/427606"
1656764,2017-02-09 15:34:44 UTC,"Reviewed:  https://review.openstack.org/427606
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=0af65867e4dcfc10d610687a3b18e6947a4f145c
Submitter: Jenkins
Branch:    stable/newton"
1656774,2017-02-03 13:37:30 UTC,"Reviewed:  https://review.openstack.org/420146
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=86b361d9166200db2174be87214190a29e77f98f
Submitter: Jenkins
Branch:    master"
1656774,2017-02-03 14:10:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/428743"
1656774,2017-02-03 19:08:40 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc1 release candidate.
1656774,2017-04-20 12:28:35 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/428743"
1656776,2017-01-17 14:50:56 UTC,"This is a libvirt virtual machine that I've installed with ubuntu-vm-builder on a 16.04 LTS host.  The full command, if you're interested, was"
1656776,2017-01-17 12:43:26 UTC,"You're right indeed, your issue is likely different from bug 1607535, but once you install apt-transport-https you should run into bug 1607535."
1656776,2017-01-17 20:30:47 UTC,"Thanks for the additional information. Even though normal installs have the package already, I personally feel that the apt-transport-https dependency should be added, be it only for consistency's sake. But I am not the package maintainer and I can't help further, sorry. Perhaps ping them directly if they don't weight in."
1656776,2017-01-17 10:46:18 UTC,It's quite possible there's more than one bug here!
1656776,2017-01-16 10:05:38 UTC,"I suspect that SourceForge started redirecting HTTP links to HTTPS lately, and this package is now missing a Depends: apt-transport-https."
1656776,2017-01-17 12:24:20 UTC,"Yep, installing apt-transport-https changes the nightly cron error from the above to a 404 because of a space in the URL."
1656776,2017-01-16 17:40:24 UTC,"More likely to be a manifestation of bug 1607535, fixed in the development release by bug 1651923."
1656779,2017-01-16 10:13:07 UTC,This was filed as #851305 - see bugs.debian.org/851305 for details.
1656779,2017-02-11 08:52:08 UTC,"Thanks for reporting. I believe this is fixed in trunk now. I can see icon and description in mate-session-properties.
Translations of the Comment key will start to trickle in once Francesco updated the translation template for the 1.4.0 release (soon-ish)."
1656784,2017-02-02 08:06:07 UTC,"Feb  2 08:43:51 frode-MacBookPro kernel: [ 5188.344618] nouveau 0000:01:00.0: fifo: read fault at 0012162000 engine 1b [CE2] client 18 [GR_CE] reason 02 [PTE] on channel 2 [003fa63000 Xorg[1753]]
Feb  2 08:43:51 frode-MacBookPro kernel: [ 5188.344624] nouveau 0000:01:00.0: fifo: ce2 engine fault on channel 2, recovering..."
1656784,2017-03-15 11:47:02 UTC,"I'm now getting this on a daily basis, standard Linux PC with GeForce GT 430, causes machine to lock completely."
1656784,2017-03-15 11:48:25 UTC,"Mar 15 00:48:27 darkstar kernel: [429513.960360] nouveau 0000:01:00.0: fifo: read fault at 0000e9a000 engine 15 [PCE0] client 01 [PCOPY0] reason 02 [PAGE_NOT_PRESENT] on channel 0 [001fe74000 DRM]
Mar 15 00:48:27 darkstar kernel: [429513.960367] nouveau 0000:01:00.0: fifo: ce0 engine fault on channel 0, recovering..."
1656784,2017-07-18 09:53:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656784,2017-07-18 09:54:04 UTC,Same here.
1656784,2017-07-18 09:56:08 UTC,"This happens when using my machine, BTW. It's not idle."
1656793,2017-01-16 10:56:06 UTC,Changed Dropping Letters to phone-app
1656794,2017-03-04 12:57:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656795,2018-01-18 19:28:21 UTC,This issue was fixed in the openstack/puppet-vswitch 5.6.0 release.
1656795,2017-02-18 00:43:03 UTC,"Reviewed:  https://review.openstack.org/435290
Committed: https://git.openstack.org/cgit/openstack/puppet-vswitch/commit/?id=fc04875852029e70ebd335a1be14e010d59d3a1c
Submitter: Jenkins
Branch:    stable/newton"
1656795,2017-01-16 11:42:01 UTC,I've reproduced it.
1656795,2017-01-26 19:07:43 UTC,This issue was fixed in the openstack/puppet-vswitch 6.2.0 release.
1656795,2017-01-19 21:18:36 UTC,Fixed in puppet-vswitch in https://review.openstack.org/#/c/421196/
1656795,2017-02-17 07:55:28 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/435290"
1656799,2017-03-30 10:39:32 UTC,This codepath could be improved a bit.
1656804,2017-03-20 13:34:23 UTC,"Verified on Fuel 10 build #1493
https://product-ci.infra.mirantis.net/view/10.0_swarm/job/10.0.system_test.ubuntu.support_hugepages/168/"
1656804,2017-01-19 15:21:24 UTC,"Verified on 9.2 snapshot #779.
Passed run: https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.support_hugepages/180/testReport/"
1656804,2017-02-27 16:24:22 UTC,This issue was fixed in the openstack/fuel-web 11.0.0.0rc1 release candidate.
1656804,2017-01-19 12:05:42 UTC,"Reviewed:  https://review.openstack.org/421432
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=8231cc965fa6dd3dd7746e5d3c37d633fada9f98
Submitter: Jenkins
Branch:    stable/newton"
1656804,2017-01-18 05:22:26 UTC,"Change abandoned by Anastasia Balobashina (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/420726
Reason: bug 1656804 was fixed in 76c29da191db4d58f03494a0498ab140a929a5ca, 83c35a9373c42533f52ab55e096f3c9d6dc1ecfc"
1656804,2017-01-19 12:05:24 UTC,"Reviewed:  https://review.openstack.org/421429
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=75db9b9d2b56fd7361966f3b287a53dac014f622
Submitter: Jenkins
Branch:    master"
1656804,2017-01-19 12:04:50 UTC,"Reviewed:  https://review.openstack.org/421428
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e6a59152059941a60e33b3e792fc3dc267ee93a2
Submitter: Jenkins
Branch:    stable/newton"
1656804,2017-01-17 23:34:31 UTC,Should be fixed in stable/mitaka by reverts: https://review.openstack.org/#/c/421402/ and https://review.openstack.org/#/c/421400/
1656804,2017-01-19 12:05:33 UTC,"Reviewed:  https://review.openstack.org/421433
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=092acaa5623f872929460145720db454b9e05eef
Submitter: Jenkins
Branch:    master"
1656804,2017-01-16 14:00:49 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/420726"
1656806,2017-01-16 12:23:07 UTC,"OA is assuming that if a client has security label other than ""unconfined"", then it's a click and its .application file is only looked for in ~/.local/share/accounts.
We should look in all XDG data dirs."
1656806,2019-01-21 09:15:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656807,2017-01-16 12:24:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420690"
1656807,2019-12-18 16:49:54 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/420690
Reason: This repo is retired now, no further work will get merged."
1656808,2017-01-16 12:32:28 UTC,"see the same behavior in unity7, in u7 it returns to the snaped position fine"
1656808,2017-01-16 14:02:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656808,2017-01-19 10:43:02 UTC,This is down to the window manager -  miral-shell behaves as expected for other applications* that run under it. (E.g. sol)
1656808,2017-02-21 12:57:52 UTC,This bug was fixed in the package unity8 - 8.15+17.04.20170216.1-0ubuntu1
1656818,2017-01-19 09:43:32 UTC,"It's obvious, that Horizon dashboard requires a browser, a browser requires graphic display (X11 on linux). Without X11 display horizon tests can't be launched. If X11 display is present the environment variable `DISPLAY` is defined."
1656820,2017-01-25 07:42:02 UTC,https://github.com/snapcore/snapd/pull/2671
1656824,2017-01-16 14:44:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/420743"
1656824,2017-01-16 17:02:53 UTC,"Reviewed:  https://review.openstack.org/420743
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e6300ed45242bb5b819c1bdcef60bbbaf6d0ae79
Submitter: Jenkins
Branch:    master"
1656824,2017-02-27 16:24:31 UTC,This issue was fixed in the openstack/fuel-web 11.0.0.0rc1 release candidate.
1656824,2017-01-16 13:26:31 UTC,"Do we need this restriction at all? I think its logic should be realized in Alembic migrations (9.0+ envs only have dpdk, sriov features)"
1656832,2017-09-05 12:17:35 UTC,"You are welcome, Alex."
1656832,2017-09-05 11:27:05 UTC,"Hello Alex,"
1656832,2017-09-05 12:01:03 UTC,"Thank leder for your feedback,"
1656832,2017-09-01 07:47:56 UTC,"Hello leder,"
1656832,2017-01-16 23:07:21 UTC,"I cannot test further, now the screenreader does not turn on at all and logging out and in does not change it."
1656832,2017-01-17 19:33:22 UTC,"OK. After reboot speech is back again. F1 key has Ubuntu help, when in settings. and orca-key+F1 has no effect."
1656832,2017-01-17 00:02:10 UTC,"Urm... no. Are you able to create a new user account and try and start Orca there? If so, what happens?"
1656832,2017-01-16 22:03:13 UTC,"Do other Orca keyboard commands work, for example insert + F1 for help? Where were you when starting Orca? Once Orca is started, do things work as expected once you log out, and back in again?"
1656832,2017-01-16 22:02:04 UTC,"Do other Orca keyboard keystrokes work? Where were you when starting Orca? What happens if once you have started orca, you log out and back in again? Do things work then as expected?"
1656832,2017-01-21 10:31:44 UTC,"Hurray, I saw Orca Settings once! But insert+space does not react anymore. Additionally keyboard shortcuts for switching orca on/off is not responding immediately, when screen is read."
1656834,2017-04-18 12:59:18 UTC,Verified on Fuel 10 build #1575:
1656834,2017-03-05 07:33:44 UTC,Verified on 9.2 + MU1 updates.
1656834,2017-03-02 14:02:09 UTC,"Reviewed: https://review.fuel-infra.org/30256
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1656834,2017-03-02 13:09:23 UTC,"Change abandoned by Alexey Stupnikov <email address hidden> on branch: 10.0/newton
Review: https://review.fuel-infra.org/31018
Reason: duplicate"
1656834,2017-02-28 13:53:37 UTC,"Reviewed: https://review.fuel-infra.org/30241
Submitter: Pkgs Jenkins <email address hidden>
Branch: master"
1656834,2017-02-28 10:29:00 UTC,Newton and master patches that should be merged:
1656834,2017-02-17 17:29:09 UTC,There is a blocking bug #1664635 that locks review process. Ivan will push patches to newton and master as soon as blocker will be fixed.
1656834,2017-02-17 16:56:35 UTC,"Fix proposed to branch: 10.0/newton
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/31018"
1656834,2017-02-15 16:54:02 UTC,"Reviewed: https://review.fuel-infra.org/30239
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0"
1656834,2017-02-01 13:14:43 UTC,"Change abandoned by Ivan Suzdal <email address hidden> on branch: 10.0/newton
Review: https://review.fuel-infra.org/30256"
1656834,2017-02-01 13:15:05 UTC,"Change restored by Ivan Suzdal <email address hidden> on branch: 10.0/newton
Review: https://review.fuel-infra.org/30256"
1656834,2017-01-30 14:23:51 UTC,"Change abandoned by Ivan Suzdal <email address hidden> on branch: 10.0/newton
Review: https://review.fuel-infra.org/30240"
1656834,2017-01-30 12:17:47 UTC,"Change restored by Ivan Suzdal <email address hidden> on branch: 9.0
Review: https://review.fuel-infra.org/30239"
1656834,2017-01-30 12:03:28 UTC,"Change abandoned by Ivan Suzdal <email address hidden> on branch: 9.0
Review: https://review.fuel-infra.org/30239"
1656834,2017-01-30 12:03:20 UTC,"Change restored by Ivan Suzdal <email address hidden> on branch: 10.0/newton
Review: https://review.fuel-infra.org/30240"
1656834,2017-01-30 12:03:17 UTC,"Change abandoned by Ivan Suzdal <email address hidden> on branch: 10.0/newton
Review: https://review.fuel-infra.org/30240"
1656834,2017-01-30 12:03:05 UTC,"Fix proposed to branch: master
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/30241"
1656834,2017-01-30 12:02:22 UTC,"Fix proposed to branch: 10.0/newton
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/30240"
1656834,2017-01-30 12:00:46 UTC,"Fix proposed to branch: 9.0
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/30239"
1656834,2017-01-24 17:26:50 UTC,"Moving back to Confirmed, assigning to linux team."
1656834,2017-01-18 13:27:39 UTC,We switched from init scripts to systemd. There is no /etc/init.d/cobblerd file in recent MOS releases. This command doesn't work:
1656834,2017-01-30 14:24:02 UTC,"Fix proposed to branch: 10.0/newton
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/30256"
1656834,2017-01-18 13:05:37 UTC,"Alexey, please provide expected and actual result. Why we need to use another approach?"
1656836,2017-04-07 20:50:53 UTC,"Yes, I am also affected, missing the Ctrl-D shortcut."
1656836,2017-04-07 20:52:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656840,2017-01-16 20:20:20 UTC,Sounds like a duplicate of bug 1521302 (which is already fixed as a Xenial update).
1656841,2018-02-16 01:18:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545184"
1656841,2017-04-12 10:38:02 UTC,"Change abandoned by Miles Gould (<email address hidden>) on branch: master
Review: https://review.openstack.org/420107
Reason: This patch does not work. Sometimes the node hangs, and when you reboot it manually the device has been set to the one you asked for. Sometimes it gets stuck with unfinished BIOS configuration jobs, which have to be cleared out manually. Sometimes it works. I haven't worked out the pattern."
1656841,2018-02-08 23:58:08 UTC,I have a couple of observations about the Bug Description.
1656841,2017-01-16 17:28:59 UTC,"Question: is what I've described above actually the expected behaviour? An alternative would be ""Ironic resets the node's boot mode to match the contents of properties/capabilities/boot_mode, and boots it in that mode""."
1656841,2018-02-09 00:15:16 UTC,"This bug report describes a bug and a new feature. The bug is that the set_boot_device() function in ironic.drivers.modules.drac.management only works when the server's boot mode is configured to be BIOS. That is because the persistent boot mode it understands is hardcoded to be a single mode, BIOS."
1656852,2017-01-16 18:08:58 UTC,"Now it make the same thing with many web site like amazone aliexpress and many other, some pictures on website don't appear, have i a virus ?
Certificate of security not approved ..."
1656853,2017-01-17 08:32:46 UTC,Somehow it has to be caused by the fonts either not being shipped in the ubuntu-app-platform snap or the path to them not being set adequately in the desktop helpers.
1656854,2017-01-25 14:18:47 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/421261
Reason: https://review.openstack.org/#/c/422070/"
1656854,2017-02-27 20:29:21 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1656854,2017-02-11 01:27:02 UTC,"Reviewed:  https://review.openstack.org/422070
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=28e6faecbf460f08f92d7c25876baf1709633e0c
Submitter: Jenkins
Branch:    stable/newton"
1656854,2017-01-27 00:51:01 UTC,This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.
1656854,2017-01-20 19:27:43 UTC,"Reviewed:  https://review.openstack.org/364413
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c7b46c4778acdb05468b6cab4f3111b298609ed4
Submitter: Jenkins
Branch:    master"
1656854,2017-01-16 16:51:31 UTC,"Here is an ugly and upstream-unfriendly fix, but it works for our installation (newton @ ubuntu):"
1656854,2017-01-18 16:11:40 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/422070"
1656854,2017-01-18 16:10:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422068"
1656854,2017-01-17 13:05:09 UTC,"Change abandoned by Sam Betts (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/421254"
1656854,2017-01-17 13:04:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/421261"
1656854,2017-01-17 12:57:13 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/421254"
1656854,2017-01-20 10:06:40 UTC,"Reviewed:  https://review.openstack.org/422068
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b34809dfae862e37b1362b73fd258af8d12adae5
Submitter: Jenkins
Branch:    master"
1656855,2017-01-19 07:03:49 UTC,"The right way to fix it is the following:
1) Check if we have proper teardown method for each test case
2) Update default quotas for new tenant up to 100 volumes."
1656855,2017-01-22 15:22:55 UTC,Review link: https://review.gerrithub.io/#/c/343811/
1656856,2020-01-07 12:18:52 UTC,I posted it as https://github.com/fail2ban/fail2ban/issues/2589
1656856,2020-01-07 11:16:19 UTC,Still present in 18.04LTS. For instance the first postfix jail filter rule catching RBL blacklisted intruders:
1656856,2017-08-14 13:03:38 UTC,Seven months old and no progress on fixing this SECURITY BUG?
1656856,2019-02-28 22:45:55 UTC,"Seems to have been fixed upstream with the package:
 https://github.com/fail2ban/fail2ban/commit/57ea38c342b2caa17b61a8cd17f142c218fd0742"
1656856,2017-03-26 13:46:39 UTC,This may also be related to the following bugs.
1656856,2017-03-26 13:40:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656856,2020-01-07 11:01:01 UTC,on 18.04 LTS this is still an issue. mail.warn just does not include all the intrusion attempts making it complicated to jail them. An example is on of the default filter rules:
1656863,2019-04-30 17:26:09 UTC,"Change abandoned by Nisha Agarwal (<email address hidden>) on branch: master
Review: https://review.opendev.org/343577"
1656863,2018-02-16 15:32:21 UTC,"Yes Ruby, this is still desired to support inband + OOB inspection with ilo
hardware type. But it depends on ""boot management for inspector spec"" and
thats the reason we havent updated this. that other spec is still not
approved, though it was targeted for Queens."
1656863,2017-01-16 16:51:28 UTC,The code patch already exists for this. https://review.openstack.org/343577
1656863,2017-01-23 20:08:00 UTC,"Ironic meeting where this was discussed: starting at 17:30:39, http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-01-23-17.00.log.html"
1656863,2018-02-12 16:45:14 UTC,"Nisha, do you still want this? It hasn't been updated since Jan 2017 :-("
1656863,2017-01-23 17:53:55 UTC,"After discussing this in the meeting, it seems like the best path might be instead of having a config option for this, instead utilizing the new driver composition stuff to expose two new inspection interfaces for ilo hardware: one that does OOB only, and one that does IB+OOB (you could also add the standard agent inspection interface for IB-only, if you'd like)."
1656870,2017-01-16 23:45:41 UTC,"Redefining this to low priority, as nothing breaks when it prints this. So, its cosmetic."
1656870,2017-01-17 00:30:33 UTC,"Actually, I think there is a fix for this in this PS:
https://review.openstack.org/#/c/413193/29"
1656870,2017-01-16 16:18:58 UTC,"Clark Boyan did most of the debugging here:
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-01-16.log.html#t2017-01-16T15:52:17"
1656870,2017-01-16 16:22:16 UTC,"A secondary problem is that wait_for_vm in this particular run didn't report any type of error for visual inspection (other then 255).  wait_for_vm failed, however, there is no visual indication as to what failed.  It would require digging through the logs in more detail which is fine, but a pointer to that in the main gating scripts would be helpful :)"
1656876,2017-02-02 19:49:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656876,2017-02-20 07:42:07 UTC,This bug was fixed in the package linux - 4.4.0-63.84
1656881,2017-01-19 07:04:53 UTC,We need to use configuration file where we will define which network should be used by test cases.
1656881,2017-01-19 09:34:35 UTC,It's already fixed with https://review.gerrithub.io/#/c/343279/
1656885,2017-01-19 11:19:04 UTC,Fixed with https://review.gerrithub.io/#/c/343750/.
1656896,2017-01-26 01:06:54 UTC,This bug was fixed in the package unity8 - 8.15+17.04.20170124-0ubuntu1
1656910,2017-04-20 18:27:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656912,2017-01-16 18:35:40 UTC,Mail does already display the quoted text indented and typically with a line at the start of the quote. Maybe checking for that?
1656912,2017-01-16 18:37:17 UTC,"Sure, but this is inside of a WebKitGTK view, so we'd have to inject some HTML/CSS/JS into the message view. Which makes it technically much more complex than it would appear on the surface."
1656912,2017-01-16 18:34:11 UTC,"Not sure how this would be implemented on a technical level, but I agree it's a handy feature that web clients like Gmail have."
1656923,2017-01-20 06:54:15 UTC,"Hi @ogra,"
1656923,2017-01-20 09:14:17 UTC,"pactl does not provide a ""list-sinks"" command, being able to select the sink does not help much if you do not know which sink to use ;)"
1656923,2017-01-20 14:05:02 UTC,"whoops i take that back, there is ""list"" (which lists the sinks alongside every other option)"
1656924,2017-01-16 19:17:29 UTC,"In case of DPDK enabled the br-aux bridge ain't created on compute nodes
since physical(dpdk) interface is being connected directly to br-prv ovs bridge."
1656924,2017-03-03 09:16:27 UTC,https://review.openstack.org/421907
1656925,2017-01-17 20:45:28 UTC,"I think I would like to see a prompt (with options to capture or not to capture the hold) when the Normal (Forgive)check_in_then_check_out button is hit, in case there is an active hold that can be filled by the copy. In another word, the checkin process follows mostly the regular checkin procedure, except throwing a prompt instead of capturing the hold(sending item in transit) directly. Staff are prompted and given an opportunity to choose how to proceed."
1656925,2017-01-17 17:51:00 UTC,"Thanks, Thomas. It makes sense when thinking of checking out an available copy with pending, but not triggered, holds (no prompt). But this scenario is slightly different. A prompt may be preferred in some situation. The item may not be found on the shelf. Two patrons may request to swap the item from one account to another. If staff use check_in_then_out, she/he may skip someone's hold without knowing it.  Tina"
1656925,2017-01-17 13:52:42 UTC,"I think this is intentional, with the ""Check In"" portion doing a ""don't do any hold/transit related stuff"" checkin, unless you are saying that the ""Check Out Fills Related Hold"" setting is enabled but not working for checking an item out that was still checked out to a different patron?"
1656925,2017-01-17 18:14:54 UTC,"So, if I understand correctly, you want a new feature that would prompt before non-renewal checkout if an active hold with no pull list target (aka, no on-shelf copies) could be filled by the copy in the case of checkout attempt from a non-standard status (more generic than ""checked out"")?"
1656927,2020-01-10 09:38:28 UTC,Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
1656927,2020-03-11 04:17:26 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1656947,2017-03-06 17:09:32 UTC,This issue was fixed in the openstack/oslo.db 4.18.0 release.
1656950,2018-09-08 15:35:07 UTC,Confirmed still happening with test board in #2
1656950,2018-05-18 17:51:59 UTC,"Sorry for not getting back to you sooner; haven't done any differential
routing lately...so I can't say for certain."
1656950,2018-05-02 22:57:38 UTC,It's been over a year and there are no other reports of this.  Was it fixed at some point?
1656950,2017-01-17 21:57:32 UTC,"Yes, here's the layout in question. Using 4.0.4 on my Windows 10 machine, I didn't see the same issue with a completely new layout, though I did check the lengths of those pairs and confirmed that they were not in fact equal to the longest trace."
1656950,2017-01-17 12:24:57 UTC,"Hi Kyle,"
1656950,2018-05-18 17:20:29 UTC,@Tom. (Ping.)
1656952,2019-07-08 07:11:29 UTC,"We can no longer access provided URL and without being able to see what test fails and further details, I cannot verify where we at with this report."
1656970,2017-01-18 09:49:58 UTC,"Same problem on Ubuntu 14.04 with version 0.8.1-0extras16.04.1.
No values displayed (tried Open Weather Map and Yahoo). Problem occured approximatively one week ago.
David."
1656970,2017-01-18 12:34:02 UTC,"Same here, it stopped working a few days ago"
1656973,2017-05-15 08:06:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/464560"
1656973,2020-06-11 21:10:56 UTC,"Change abandoned by Michael Johnson (<email address hidden>) on branch: master
Review: https://review.opendev.org/464560
Reason: There has been no progress on this patch for two years. Abandoning. If you want to continue working on this, please restore it."
1656976,2019-08-22 11:20:12 UTC,"classic is a chroot that re-adds the removed apt/dpkg bits to the core/core18 snaps, it is not intended to be used in production and has intentionally never seen a release to the stable channel.
there is no way to make services work properly without a significant re-design, IMHO the classic snap should be removed from the store as there are more proper ways to use apt on top of an Ubuntu Core install nowadays which did not exist when we started teh classic snap (and classic should definitely not be used on anything else than an Ubuntu Core device)."
1656976,2019-08-22 09:23:30 UTC,This seems like an oversight in the classic snap. I'll see if we can fix this easily.
1656983,2017-03-02 21:28:32 UTC,"I'll need some details on how you set this up, maybe your config files, some specifics around drivers etc.  I've tried restarts of c-vol service and not seeing issues.  Maybe some more detail?"
1656996,2017-03-06 09:32:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1656997,2017-01-17 03:33:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421056"
1656999,2019-04-01 12:14:05 UTC,"with 4.4.0-143 showkey -s returns:
0xe0 0x73 0xe0 0xf3"
1656999,2019-04-01 11:16:56 UTC,The issue in bug 1339456 seems to be fixed by a BIOS upgrade.
1656999,2017-01-17 04:30:16 UTC,This change was made by a bot.
1657010,2017-01-17 12:48:14 UTC,"Instead of having a new CPU model called ""best"", we can simply make ""-cpu host"" available on TCG. I have submitted a patch for this yesterday:"
1657010,2018-01-22 17:43:59 UTC,"I think we've ended up with '-cpu max', present since QEMU 2.9 for x86 and perhaps for some other architectures, but not Arm yet."
1657010,2020-01-10 09:37:25 UTC,"As far as I can see, we have ""-cpu max"" now for x86, arm, ppc and s390x ... is that enough, so that we can close this bug now?"
1657011,2017-11-06 03:27:00 UTC,Developers are  you all solving this bugs or it is fixed
1657011,2017-01-18 06:53:42 UTC,I am not getting openrailslog.txt so what can i do for that please reply me
1657011,2017-01-17 08:48:21 UTC,Please attach the whole OpenRailsLog.txt file that you get on the desktop.
1657011,2017-01-19 05:33:36 UTC,thats the openrailslog.txt please reply me as soon as
1657011,2017-01-24 14:36:28 UTC,"First of all if you look at the openrailslog.txt file you will see that there are many wagons needed that are missing. There are many lines like this one
Warning: Ignored missing wagon E:\open rail\open rail\msts\trains\trainset\ASM - IR Coach\KonarkPantry_TRANS.wag in consist E:\open rail\open rail\msts\TRAINS\CONSISTS\22150_roharn.CON .
You should first install all wagons that OR declares as missing.
Second, I suggest you to download, install and use Open Rails release 1.2, that has just been made public, because release 1.1 won't be supported any more.
After done this, try again, and if you still get the problem attach again the file openrailslog.txt that you obtain."
1657020,2017-07-08 15:28:19 UTC,Looks like a duplicate of https://bugs.launchpad.net/pinta/+bug/1658322
1657021,2017-01-17 08:01:26 UTC,"I believe we will be able to offer operator-controlled access rules when we implement hotplug support. In my mind a privileged snap could offer APIs and command line tools for creating and removing ""filesystem areas"" that can be assigned to assigned to an application via a plug of some sort. This new interface is difficult to implement before we can dynamically create new plugs and slots though."
1657024,2017-04-27 08:33:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657024,2020-06-11 19:43:19 UTC,"Hi, this bug still remains on bionic 18.04 and on the recently released 20.04"
1657024,2020-06-11 20:08:33 UTC,I looked into the history of this.  We used to have a patch in Debian to use gethostbyname to address this issue.  It was dropped because it caused worse problems.  Here's the relevant code snippet from the most recent postfix release:
1657029,2017-01-17 08:24:25 UTC,"note that you can do ""juju show-machine 0"" to get the status message of the container, but
""juju show-machine 0/lxd/0"" fails because we don't support specifying just a container in the syntax (yet)."
1657029,2017-01-17 08:25:23 UTC,"also, if you fix the provisioning error
  juju retry-provisioning 0/lxd/0
also fails because it ""does not support containers"""
1657030,2017-01-17 10:27:58 UTC,"@Nastya, how ever could it be high priority?"
1657030,2017-01-17 10:47:34 UTC,It turned out that these duplicates are brought by python-cliff-tablib which is required by nobody.
1657035,2017-02-09 17:35:37 UTC,"Reviewed:  https://review.openstack.org/421186
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bf3ba76a91e362c0b3b8094964adc06f6a4ec62e
Submitter: Jenkins
Branch:    master"
1657035,2017-03-21 18:56:29 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/448235"
1657035,2017-03-21 19:15:33 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/448241"
1657035,2017-04-10 23:04:14 UTC,"Reviewed:  https://review.openstack.org/448241
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ce513278f15d251bae96b339fca2ffb2a05b28f6
Submitter: Jenkins
Branch:    stable/ocata"
1657035,2017-04-12 18:55:15 UTC,This issue was fixed in the openstack/nova 15.0.3 release.
1657035,2017-04-14 09:24:09 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1657035,2017-04-26 21:28:38 UTC,"Reviewed:  https://review.openstack.org/448235
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=adec640bfa5d560ce86aedea6a678a21b64823aa
Submitter: Jenkins
Branch:    stable/newton"
1657035,2017-05-08 22:25:56 UTC,This issue was fixed in the openstack/nova 14.0.6 release.
1657035,2017-01-17 09:58:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421186"
1657045,2017-02-21 12:57:52 UTC,This bug was fixed in the package unity8 - 8.15+17.04.20170216.1-0ubuntu1
1657071,2017-03-20 07:51:17 UTC,"The RFE[1] intro the who/when/where/what info is just what we want..:)...
[1]https://bugs.launchpad.net/neutron/+bug/1628627."
1657071,2017-02-01 12:32:48 UTC,"Do you want https://bugs.launchpad.net/neutron/+bug/1468366 ? If not so, could you elaborate more?"
1657071,2017-02-16 09:08:54 UTC,"@Hirofumi Ichihara,
Hi , thank  you for comments. I found the spec of that had been delayed into P release. And I saw it will also do the same work towards firewall's LOG. I just show some views about the firewall LOG working here."
1657075,2017-01-19 07:06:42 UTC,"Denis, do you really sure it is a bug in stepler? It looks like a bug in the OpenStack configuration for me."
1657075,2017-01-19 10:05:56 UTC,"This fix was included to this commit:
https://review.gerrithub.io/#/c/343249/"
1657077,2017-11-13 16:14:45 UTC,"Not sure why this was tagged as an RFE. I removed the tag, after asking on irc: http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2017-11-13.log.html, around 16:10."
1657077,2019-04-09 08:54:31 UTC,"Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: master
Review: https://review.openstack.org/502886
Reason: Abandoning due to no activity :("
1657077,2017-10-18 18:07:27 UTC,"Vasyl, is there a fix for this? I'm setting the status to Triaged since I don't see any patch."
1657077,2017-01-25 11:57:31 UTC,This seems duplicated with: https://bugs.launchpad.net/ironic/+bug/1633072
1657077,2017-10-19 07:02:45 UTC,No sure why bot didn't add a comment:
1657081,2017-01-19 10:17:37 UTC,Fixed with https://review.gerrithub.io/#/c/343734/
1657086,2017-01-25 15:21:36 UTC,"I would add that, besides making the user icon clickable, it would be very helpful to show all accounts' names on the login screen, not only the selected account."
1657091,2017-09-07 20:20:21 UTC,Today I had an IRC conversation with johnsonm about this RFE:
1657091,2017-01-17 16:40:13 UTC,Can you provide some use cases as to why you would like UDP and what UDP protocols you would use this for?
1657091,2017-10-25 23:45:08 UTC,"zhaobo Please use the StoryBoard bug: https://storyboard.openstack.org/#!/story/1657091
This bug is no longer used"
1657091,2017-10-24 11:53:49 UTC,I update the RFE decription.
1657091,2017-02-17 07:29:52 UTC,"@Michael Johnson
Hi， michael. Thanks for comments here."
1657091,2017-10-10 11:52:47 UTC,"As Micheal's kind suggestion during PTG, then I test LVS simple driver with amp in my env, it works for the some simple udp loadbalance function in the currently deployment type. But there is a problem now, LVS driver can not meet the most part of Octavia data models. So I think need to extend the amp agent RESTAPI and inject some LVS CLI code to agent(will find some other python library which support LVS operation). Then find a good way to how to advance the LVS part. Also I still need to collect the real requirements from users.."
1657091,2017-09-13 12:00:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503606"
1657091,2017-09-07 20:30:16 UTC,"FYI, this bug has been migrated to Storyboard here: https://storyboard.openstack.org/#!/story/1657091"
1657091,2017-10-24 11:53:13 UTC,"@ALL, please check the use case again. Thank you."
1657092,2017-03-09 21:54:14 UTC,This had been released as a part of Déjà Dup 34.4.
1657092,2017-03-09 21:29:36 UTC,This bug was fixed in the package deja-dup - 34.4-0ubuntu1
1657092,2017-02-22 16:12:42 UTC,"Russ, can you please post the values of the following environment variables in MATE, I'm going to try and implement something and I'm not sure which one to use (probably the last one). You can use printenv var or echo $var to find them out. Thanks."
1657092,2017-03-01 02:03:09 UTC,"I prepared a patch for zesty and seek sponsorship.
Please note that this is my first Ubuntu downstream patch (so please be detailed in your feedback if necessary)."
1657092,2017-02-28 23:35:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657092,2017-02-27 20:24:54 UTC,This text is only visible after a first full backup. I will change the [Test Case] accordingly.
1657092,2017-02-27 17:49:07 UTC,"@Michael: Sweet, thanks for merging!"
1657092,2017-02-27 00:09:16 UTC,Thank you Nathanaël!
1657092,2017-02-22 22:22:45 UTC,"I wish I was knowledgeable enough to fix less trivial bugs. In the meantime, here are two branches. Michael, which one would you like I request a merge of?"
1657092,2017-02-22 16:30:22 UTC,Here you go:
1657092,2017-03-05 12:18:14 UTC,"I'm still not convinced that this is worth a SRU, or qualifies for one. The provision about ""bugs which [...] (1) have an obviously safe patch and (2) affect an application"" in the SRU guidelines applies only to bugs which have ""high potential for improving the user experience"", and I'm just not sure this particular bug has high potential for that (just potential)."
1657092,2017-02-21 17:22:47 UTC,Reproducing what I wrote in the mailing list:
1657092,2017-02-20 23:29:02 UTC,@Naël I see your point and will discuss this on the mailing list.
1657092,2017-01-28 15:27:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657092,2017-02-21 19:55:12 UTC,"I originally posted this bug in Mate, since I thought they maintained a forked version of Nautilus and Deja Dup, and this would be something they'd want to include in that."
1657092,2017-01-30 07:31:09 UTC,"Yes, it works in Caja. I originally filed this against Ubuntu Mate, thinking that it was something to be fixed in Mate, since Files isn't the file manager in Mate :/"
1657092,2017-01-30 12:14:59 UTC,"It could be fixed in Ubuntu MATE if they had their own fork of Déjà-Dup, like they have their own fork of Files, Gedit, Eye of GNOME, Evince, GNOME Terminal, File Roller."
1657092,2017-01-30 12:29:56 UTC,"The attachment ""Change ""Files"" to ""a compatible file manager"" to encompass Nautilus forks e.g. Caja"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1657092,2017-01-28 17:07:36 UTC,Does it work though? In Caja? Do you get the restore/revert options when you right-click?
1657092,2017-02-14 00:15:24 UTC,@Nathanaël: Could you please upload your patch to a (upstream) branch and propose it for merging?
1657092,2017-02-20 21:00:29 UTC,@Russ Phillips (or anyone using MATE):
1657092,2017-02-20 21:33:34 UTC,@Russ Phillips:
1657092,2017-02-20 22:15:45 UTC,Quick work :) I wouldn't have had the chance to check before tomorrow.
1657092,2017-02-11 12:39:58 UTC,"Naëls patch is applicable for the upstream package, I will therefore send this to the upstream and ask for triaging."
1657092,2017-02-20 22:42:38 UTC,@Vej (and @Russ too):
1657093,2017-01-17 11:49:07 UTC,Root cause of that issue is that ansible was installed by someone before mos-playbooks and mos-release.
1657093,2017-01-17 11:51:47 UTC,I've removed mos-playbooks and ansible packages and install the mos-playbooks package again - it's installed newer version of ansible required for playbooks.
1657093,2017-01-17 11:57:20 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Anton Chevychalov <email address hidden>
Review: https://review.fuel-infra.org/29882"
1657093,2017-01-17 16:15:24 UTC,"Reviewed: https://review.fuel-infra.org/29882
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1657095,2017-01-22 13:30:43 UTC,"While trying to figure this out.
I managed to install a Newton build with VMware vc6.
Image upload works."
1657095,2017-02-02 09:32:59 UTC,"Figured it out, my VMware calls for insecure connection."
1657097,2017-01-18 09:59:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421775"
1657097,2017-03-09 21:31:47 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/421775
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1657097,2017-09-26 22:49:36 UTC,Unassigning due to no activity for > 6 months.
1657104,2020-09-29 12:51:47 UTC,"Snapd is now much more aware of disk space constraints, especially around critical operations that rely on additional space, such as refreshes. The feature is still behind several experimental feature flags, and is not enabled by default."
1657104,2019-01-26 04:16:28 UTC,"I discovered I'd run out of disk space when installing a snap ""froze"". Annoying, because it's happening in a privileged space, it actually used 100% of the disk, instead of respecting the root-reserved section, which mean I didn't have enough free disk space to resize my LVM volume to give myself more disk space."
1657104,2020-07-14 08:22:24 UTC,"This is being worked on, it will involve a series of PRs, e.g. https://github.com/snapcore/snapd/pull/9002"
1657104,2020-05-22 11:34:20 UTC,I ran into this in recover mode in uc20 with a small tmpfs mounted for ubuntu-data and got the following snapd log/panic https://pastebin.ubuntu.com/p/6BkjjssQpt/
1657107,2017-08-18 12:48:39 UTC,"I'm marking this as triaged although I filed it myself. John I've assigned this to you for evaluation, if you feel we don't want to do this please close the bug with WONTFIX."
1657107,2017-08-23 10:20:10 UTC,"Note this is easy to do wrong in the client, because TOCTOU."
1657109,2017-01-17 13:50:52 UTC,Why not just run python setup.py sdist on the host prior to ADD and ADD the source distribution in the container rather then a tarball of the git repository?  I think this would work for any type of URI.  It does require host processing when building images (which I think the workaround you suggested already does) but would remove git from the base images entirely which would be another win.
1657109,2017-05-26 10:43:44 UTC,"Change abandoned by Paul Bourke (pbourke) (<email address hidden>) on branch: master
Review: https://review.openstack.org/421252"
1657120,2017-01-17 21:06:44 UTC,Thanks for the report Jorge. How did you install the font?
1657120,2017-01-18 14:12:37 UTC,"The packagename is `fonts-powerline`, upstream is here: https://github.com/Lokaltog/powerline"
1657120,2017-01-18 19:09:03 UTC,Thanks! Did you just apt install it?
1657120,2017-01-18 19:21:53 UTC,Yep.
1657126,2017-01-18 09:52:57 UTC,"Hi,"
1657126,2017-01-18 12:20:10 UTC,"Hi,"
1657127,2017-01-17 14:12:17 UTC,"Hello,"
1657139,2017-05-24 09:20:26 UTC,"Tristan, no objections."
1657139,2017-05-24 04:42:37 UTC,"Amrith, any objections if we switch this to public and close the OSSA task?"
1657139,2017-03-30 12:58:06 UTC,"My suspicion is that this issue was found using some code inspection tool and not actual observation of an issue. As best as I can tell, this should not be an issue in practice but I will check and update."
1657139,2017-01-18 11:19:01 UTC,"trove-coresec, can the XMLDictSerializer be used with user supply data, or is it only processing known/safe xml object?"
1657139,2017-01-17 15:31:23 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1657139,2017-03-31 12:39:43 UTC,"Tristan, as best as I can tell from a quick review of the code, this is not a vulnerability but an opportunity for hardening. I will request additional review (others on trove-coresec) and update in the next day or two."
1657152,2017-01-18 03:46:47 UTC,14.04 LTS didn't use systemd as the init or service management daemon. What's the plan for snapd on such old things? Are we backporting systemd to 14.04 LTS? Or teaching snapd how to manage upstart?
1657152,2017-01-25 12:11:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657152,2017-01-25 20:11:41 UTC,As discussed on IRC: The service unit fails to start up and the snap is not installed. Hence you don't see the unit showing up.
1657163,2017-02-02 12:16:41 UTC,Need to add openstack-origin-git to the config.yaml:
1657163,2017-02-02 12:18:21 UTC,This will also require integration of the deploy from source code into charms.openstack to understand what todo with the option.
1657164,2017-01-17 16:11:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657167,2017-03-22 12:12:49 UTC,"Change abandoned by Steven Hardy (<email address hidden>) on branch: master
Review: https://review.openstack.org/421341"
1657167,2017-02-16 12:57:20 UTC,This issue was fixed in the openstack/tripleo-heat-templates 6.0.0.0rc1 release candidate.
1657167,2017-01-19 15:10:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422682"
1657167,2017-01-17 16:08:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421341"
1657167,2017-01-20 07:30:10 UTC,"Reviewed:  https://review.openstack.org/422682
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=2dee58a85abd3e2e653d52f41ccf155c17681c62
Submitter: Jenkins
Branch:    master"
1657167,2017-01-17 16:01:25 UTC,"https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L730 seems to indicate it should be my manually fixed syntax, so I'll push a patch to puppet-swift and re-test, unsure atm why other folks aren't seeing this tho."
1657168,2017-01-17 16:33:46 UTC,"the ppa is active: https://launchpad.net/~conjure-up/+archive/ubuntu/next
so the script seems failing doing its job (maybe against https)"
1657168,2017-01-17 18:26:52 UTC,"Yes, the bug is that the error message is deceptive if the host network is
down."
1657170,2017-12-04 15:59:48 UTC,"Vifs aren't attached to ports or portgroups they are attached to nodes, attaching them to ports/portgroups is a implementation detail of the neutron/flat network interfaces."
1657170,2017-12-04 19:32:55 UTC,We discussed this in today's ironic meeting [1] and it needs a spec. The API changes need to be described and it should be generalized so it doesn't make assumptions about the network interface being used.
1657170,2017-12-06 09:21:03 UTC,"> The assumption 'in certain implementations a physical port in Ironic might have multiple vifs attached to it to represent a virtual interface card' is not applicable to current ironic port logic as port has only one mac address while virtual ports should have different macs, otherwise you will not able to plug them to the same network.
"
1657182,2017-01-20 11:59:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423229"
1657182,2019-02-20 10:55:04 UTC,"Change abandoned by Yushiro FURUKAWA (<email address hidden>) on branch: master
Review: https://review.openstack.org/423229
Reason: No longer maintained and this patch has already been covered with https://review.openstack.org/#/c/618485/"
1657182,2020-04-28 11:05:13 UTC,Fix is already merged
1657189,2017-01-17 18:26:28 UTC,"Good idea. Things already look much cleaner since r8241, but bottom alignment is still desirable."
1657189,2019-09-17 09:58:10 UTC,Migrated to https://github.com/widelands/widelands/issues/1664
1657190,2017-04-11 15:43:48 UTC,"Change abandoned by Yushiro FURUKAWA (<email address hidden>) on branch: master
Review: https://review.openstack.org/424534
Reason: 'public' has already replaced so this patch is not necessary."
1657190,2017-01-23 06:56:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423947"
1657190,2017-01-24 01:04:06 UTC,"Change abandoned by Yushiro FURUKAWA (<email address hidden>) on branch: master
Review: https://review.openstack.org/423947
Reason: Need to find other way into neutron-fwaas."
1657190,2017-01-24 09:27:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424534"
1657199,2017-05-09 13:09:28 UTC,"Review in progress for https://review.opencontrail.org/31234
Submitter: SHYAM BHOPLE (<email address hidden>)"
1657199,2017-04-21 04:56:19 UTC,"Review in progress for https://review.opencontrail.org/30645
Submitter: SHYAM BHOPLE (<email address hidden>)"
1657199,2017-03-21 13:18:09 UTC,"Review in progress for https://review.opencontrail.org/29760
Submitter: SHYAM BHOPLE (<email address hidden>)"
1657204,2017-01-17 17:39:40 UTC,"Searching further ; I have found an os-level per-program soundcontrol. There, the 1-100 range do work. It's a very useful functionnality, giving a hint it's there with a direct link in the taskbar soundcontrol would be a nice improvement"
1657214,2019-03-26 14:56:27 UTC,Victoria how are we doing with this ?
1657227,2020-10-08 13:29:20 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/756710"
1657227,2017-10-25 12:59:10 UTC,"In comment #3, I was referring this patch -- https://review.openstack.org/#/c/420733/ which was done on Newton timeframe."
1657227,2020-10-08 13:29:08 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/756709"
1657227,2017-09-01 13:58:29 UTC,Using the online copy also leads to problems with deleting the hidden snapshots that are made from the temporary snapshots.  You will eventually have tss-*** volumes that have hidden snapshots that can't ever be deleted.
1657227,2017-08-31 21:21:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499806"
1657227,2017-09-26 13:26:03 UTC,Apologies for the confusion caused here.
1657227,2017-09-27 13:00:58 UTC,"First off, the only time an online copy is used is when the original volume and the new volume are exactly the same size.   This is not the case for nearly every volume cache enabled volume creates, because the cache volume size is the minimum size required for the image.  The volumes will almost always be a larger size."
1657234,2017-01-17 19:46:25 UTC,"Please see also
https://github.com/CastXML/CastXML/issues/84 for context."
1657234,2017-01-17 20:04:16 UTC,"I hand-edited /usr/lib/python2.7/dist-packages/ctypeslib/codegen/cparser.py to replace all references to ""gccxml"" with ""gccxml.real"", and it works again."
1657235,2017-02-09 18:27:48 UTC,"To work around this you can set ""install_method"" option to ""apt""."
1657249,2017-01-17 22:28:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/421563"
1657249,2017-01-18 20:02:07 UTC,"Reviewed:  https://review.openstack.org/421563
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=d936d6775cc78a1daba73db9e4c5733bd389609d
Submitter: Jenkins
Branch:    master"
1657256,2017-01-18 00:02:48 UTC,Possibly upstream related code:
1657256,2017-01-17 21:58:08 UTC,"I was able to reproduce this with percona-xtradb-cluster-server 5.6 from xenial too, on the same architecture (again inside xenial lxc container)."
1657256,2017-10-26 13:07:09 UTC,"After a few rounds of cleanup we made it.
There was enough cleanup to be worth a retest - other than that we are ready IMO."
1657256,2017-10-25 15:02:23 UTC,"@paelzer,"
1657256,2017-10-24 08:01:34 UTC,"FYI:
- Done reviewing branches in general
- Niedbalski and I fixed several things already (whitespace, versions, correct author attribution, rebase to correct base versions, ...)
- X branch looks good and builds/tests fine
- T branch FTBFS on all !x86 in [1]
- Z branch FTBFS on all !x86 in [1]"
1657256,2017-10-20 08:23:15 UTC,"Hi,
I reviewed the MP and it LGTM.
Also I'm ok with the debdiff for trusty given that it was already reviewed before."
1657256,2017-10-19 18:57:40 UTC,"Hello @paelzer,"
1657256,2017-10-19 18:54:23 UTC,"Hello @paelzer,"
1657256,2017-10-19 08:23:19 UTC,This bug was fixed in the package percona-xtradb-cluster-5.6 - 5.6.34-26.19-0ubuntu4
1657256,2017-10-19 07:01:21 UTC,FYI - further work on the FTBFS on bug 1714554 (the one about the FTBFS) - if/once this gets in it will unblock this bug here as well.
1657256,2017-10-17 20:40:11 UTC,"Christian, Robbie:"
1657256,2017-10-17 14:27:09 UTC,I was asked to help with the review and on a first glimpse agree with Robie c#62.
1657256,2017-10-13 22:16:43 UTC,"Jorge: When I installed it manually, the openstack cluster came up fine."
1657256,2017-10-09 16:41:46 UTC,"I found this quite complicated to review, so to break it down I imported the package into git and then split your debdiff up into multiple git commits and then applied the relevant quilt patches as commits at the end so that I could see what was going on. I've pushed this to https://git.launchpad.net/~racb/ubuntu/+source/percona-xtradb-cluster-5.6/log/?h=niedbalski&id=niedbalski.c59 and I'll refer to commits from there in my review as I disect your debdiff."
1657256,2017-10-08 15:43:53 UTC,Jorge: The latest did not install (I am using a juju charm bundle to deploy openstack):
1657256,2017-10-05 18:10:34 UTC,I've built a Xenial PPA with the fix (ppa:niedbalski/xenial-lp1657256) for testing.
1657256,2017-10-04 22:19:15 UTC,"<niedbalski>rbasak, ok, I don't think is going to be possible, I incorporated a small nitpick on the original patch (that prevents a warning), thus the ibuf* patch actually differs from ubuntu3."
1657256,2017-10-04 20:58:23 UTC,"21:57 <rbasak> niedbalski: thanks! Quick glance. 5.6.34-26.19-0ubuntu3 is already taken. Can you prepare a debdiff against the already uploaded 5.6.34-26.19-0ubuntu3 to 5.6.34-26.19-0ubuntu4? I expect that debdiff to include only the FTBFS fix, as I think the other necessary fixes are already present in 5.6.34-26.19-0ubuntu3?"
1657256,2017-10-04 18:45:21 UTC,"Hello Robie,"
1657256,2017-10-26 21:38:06 UTC,"@paelzer,"
1657256,2017-10-27 05:43:33 UTC,"Ok, then we have
- code review and fixups done
- Fixed in latest Dev release
- SRU Template ready
- Tested build from PPAs
- Tested fix from PPAs
=> I'm merging the MPs and sponsoring the fix now for SRU."
1657256,2017-10-31 23:34:17 UTC,"Hello Mario, or anyone else affected,"
1657256,2017-10-31 23:44:12 UTC,"Hello Mario, or anyone else affected,"
1657256,2017-11-16 16:33:21 UTC,This bug was fixed in the package percona-xtradb-cluster-5.6 - 5.6.34-26.19-0ubuntu1.1
1657256,2017-11-16 16:33:00 UTC,This bug was fixed in the package percona-xtradb-cluster-5.6 - 5.6.34-26.19-0ubuntu0.16.04.2
1657256,2017-11-15 19:32:29 UTC,## FOR SRU VERIFICATION TEAM ##
1657256,2017-11-15 09:07:56 UTC,"Note: Xenial would be good already in regard to verification (done), as well as autopkgtests (all good)"
1657256,2017-11-15 00:29:56 UTC,"The verification of the Stable Release Update for percona-xtradb-cluster-5.5 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1657256,2017-11-15 00:29:49 UTC,This bug was fixed in the package percona-xtradb-cluster-5.5 - 5.5.37-25.10+dfsg-0ubuntu0.14.04.5
1657256,2017-11-14 17:13:56 UTC,The autopkgtest still fails after an attempt to restart them.
1657256,2017-11-14 15:44:12 UTC,"By precaution, I have restarted the autopkgtest for the above 4 failures."
1657256,2017-10-04 13:58:42 UTC,Unsubscribing ~ubuntu-sponsors for now as I have declined the current debdiff for artful and so there is nothing left to sponsor.
1657256,2017-11-14 15:39:26 UTC,I have identified 4 autopkgtests failure for Zesty in pending-sru page as follow :
1657256,2017-11-08 20:27:36 UTC,Summary of the verification:
1657256,2017-11-08 15:18:55 UTC,"OK - look liks arm64/amd64 are covered, but it seems to me that we still need test results for xenial-proposed and zesty-proposed on ppc64el."
1657256,2017-11-08 01:46:18 UTC,The regression test failures above were config issues on my end. They've since passed successfully.
1657256,2017-11-07 17:35:00 UTC,"@Jorge what else needs to be tested before this can get a verified tag?
Note: I've tested on arm64, though I was never able to recreate the problem myself w/ the unfixed package and percona."
1657256,2017-11-06 14:58:22 UTC,Verified proposed Xenial with HA in 3 units (http://paste.ubuntu.com/25903553/)
1657256,2017-11-03 15:00:09 UTC,Regression testing for xenial-mitaka-proposed is hitting 2 heat test failures due to authorization failures. I've not yet dug into them but they exist on xenial-proposed and xenial-updates so likely not an issue related to this bug.
1657256,2017-11-03 14:47:32 UTC,Regression test results for zesty-ocata-proposed with stable charms was successful:
1657256,2017-11-01 15:13:11 UTC,"Manoj, can you please verify the package in Proposed by enabling the proposed repo and tag this bug as verification-done-xenial  ?"
1657256,2017-11-09 21:35:56 UTC,"Hello Mario, or anyone else affected,"
1657256,2017-10-04 13:57:04 UTC,There seems to be a ton of confusion here. I have commented to various people on IRC as they have asked me. But the messages don't seem to have been received. I'll try and summarize my opinion here.
1657256,2017-11-14 13:05:52 UTC,"Hello Brian,"
1657256,2017-10-03 16:19:43 UTC,"@racb,"
1657256,2017-06-08 16:38:33 UTC,"It seems I made a mistake by publishing this to -proposed, not sure what happened in my head. This needs to be released *first* to the devel series *at least*. I request this being blocked in the -proposed pocket until all other series don't at least get released to artful (so bug LP: #1693765)."
1657256,2017-06-01 16:49:34 UTC,"I have verified the package from -proposed, and it indeed fixes the bug."
1657256,2017-05-29 14:40:23 UTC,"Hello Mario, or anyone else affected,"
1657256,2017-05-26 10:32:58 UTC,"I have removed percona-xtradb-cluster-5.6 from this bug as in Trusty we have percona-xtradb-cluster-5.5, and in xenial (and above) we have percona-xtradb-cluster-5.6. I've created a separate bug for Percona in xenial (and above): #1693765."
1657256,2017-04-04 11:22:25 UTC,"This needs Zesty fixed before we can upload SRUs, so unsubscribing ~ubuntu-sponsors for now. Please resubscribe ~ubuntu-sponsors once you have a Zesty debdiff ready."
1657256,2017-04-03 09:53:16 UTC,"I've also put the patched package for for trusty into this ppa:
https://launchpad.net/~mariosplivalo/+archive/ubuntu/lp1657256-sru"
1657256,2017-04-03 09:50:59 UTC,I'm attaching a debdiff that fixes the issue for trusty.
1657256,2017-03-31 13:51:11 UTC,Seeing the following with pxc 5.6 xenial ppc64el:
1657256,2017-03-31 13:46:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657256,2017-03-06 10:20:45 UTC,"I have built test packages, for both trusty and xenial:"
1657256,2017-02-03 11:07:16 UTC,Rafael!
1657256,2017-01-31 17:39:32 UTC,Possibly related commits:
1657256,2017-01-27 11:36:46 UTC,I bisected the MariaDB source tree and found out that this commit fixed the issue:
1657256,2017-01-18 16:45:17 UTC,"Hello, Rafael."
1657256,2017-01-18 16:33:30 UTC,"The attachment ""trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu0.14.04.3~fix~1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1657256,2017-10-03 20:13:05 UTC,The existing PPA does not work on ppc64/xenial because of the libevent dependancy? Can we get that resolved?
1657256,2017-01-17 23:36:46 UTC,I could find:
1657256,2017-06-08 17:19:29 UTC,"""I have removed percona-xtradb-cluster-5.6 from this bug as in Trusty we have percona-xtradb-cluster-5.5, and in xenial (and above) we have percona-xtradb-cluster-5.6. I've created a separate bug for Percona in xenial (and above): #1693765."""
1657256,2017-06-13 10:21:37 UTC,"Hi, Brian, Łukasz."
1657256,2017-06-01 17:02:31 UTC,"I have also tested the package under Intel architectures to make sure no regression is introduced and, indeed,  the sysbench test completes without an error."
1657256,2017-08-10 23:42:24 UTC,"Hello Sponsors,"
1657256,2017-09-29 15:58:32 UTC,I hope not Jason. I am running into the same issue on Xenial:
1657256,2017-09-28 23:16:13 UTC,"Jorge,
I tied this install now on Xenial, but am getting the same error about libevent being not installable:"
1657256,2017-09-27 15:12:15 UTC,"@Manoj, https://launchpad.net/~niedbalski/+archive/ubuntu/lp1657256/"
1657256,2017-09-27 14:35:30 UTC,Can you build a PPA for Xenial?
1657256,2017-09-27 13:38:43 UTC,"fyi, looks like the same issue we fixed in MySQL/MariaDB a couple years ago - LP: #1427406"
1657256,2017-09-22 16:07:30 UTC,"Hey Jorge,"
1657256,2017-06-19 13:51:12 UTC,"As per previous discussion on IRC and other places, I have removed the update from trusty-proposed to unblock other fixes to the package. The reason being: SRU postponed until the bug gets fixed in 5.6 versions of the package in the current devel series."
1657256,2017-09-21 20:58:46 UTC,"Which series? the PPA just covers artful. fyi,"
1657256,2017-09-21 20:09:09 UTC,I tried this on ppc64el and see this issue:
1657256,2017-09-22 14:13:02 UTC,"Sorry, xenial is what I need."
1657256,2017-09-07 18:58:22 UTC,This is impacting >= Xenial ppc64el deployments and testing for OpenStack Charms.  Please let us know if there is a PPA with the fixed package available.  Thank you.
1657256,2017-09-21 16:32:04 UTC,"Hello Sean,"
1657256,2017-09-21 16:05:17 UTC,"Deploying Openstack Ocata, w/ Juju on arm64 hosts, the mysql crashed with the following:"
1657256,2017-09-12 19:37:06 UTC,See possibly dup bug @ https://bugs.launchpad.net/bugs/1713778
1657256,2017-09-11 18:22:38 UTC,"Hello Beisner,"
1657256,2017-09-07 19:28:49 UTC,"Hey Ryan,"
1657256,2017-09-07 19:22:48 UTC,"Hi Ryan,"
1657256,2017-09-21 17:35:05 UTC,"Hey Jorge,"
1657256,2017-09-01 16:05:46 UTC,Thanks! Sponsored because I appreciate the delay already. But please file a bug with Percona upstream and link to it here. Then hopefully on future updates we can drop the patch. Otherwise we'll slowly build up patches to this package over time and it'll become an unmaintainable mess.
1657281,2017-01-17 22:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1657281,2017-01-18 13:27:50 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-January/081890.html
1657281,2017-01-19 13:16:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1657281,2017-01-19 17:20:59 UTC,Verified:
1657281,2017-02-02 16:59:00 UTC,This bug was fixed in the package linux - 4.4.0-62.83
1657292,2018-04-19 11:53:45 UTC,"@plamen-mbx: A search timeout, or a timeout that doesn't involve bug creation or modification, is unrelated to this bug.  If you still see it, please provide details in a new bug report, quoting any OOPS ID."
1657292,2020-03-06 08:12:05 UTC,"We're still seeing this from time to time, although it feels less bad.  https://oops.canonical.com/oops/?oopsid=OOPS-94b77a2c900519293c6cf20a0fa96c3d is a sample OOPS."
1657292,2018-04-19 11:51:19 UTC,This is a periodic issue; it typically appears for ten minutes or so and then goes away again.  It seems to be due to some kind of internal PostgreSQL maintenance task that locks the creation of temporary tables; when we've looked into it previously the lock seem to show up in any of the usual status tables.  When we've discussed it in the past we concluded our best hope was to upgrade to a newer version of PostgreSQL (we're currently on 9.3) and hope that either that fixes the problem or at least gives us more information to go on.
1657292,2018-01-19 09:12:45 UTC,"Using ""Search"" gives me ""Timeout error"" every time. Please fix it."
1657292,2020-02-25 13:54:54 UTC,"We've deployed improved database triggers to production, so this should be much better now.  If you still see persistent bug update timeouts, please file a new bug and we'll be interested to look into what's causing it."
1657292,2017-02-25 16:33:07 UTC,"I get ""Timeout error"" like constantly and have to reload the page multiple times to not get ""Timeout error"" and it have been like this for me the last couple of weeks maybe."
1657292,2017-01-25 13:12:28 UTC,seems to be working now
1657292,2017-04-19 23:51:14 UTC,I am getting the same bug today: (Error ID: OOPS-87eaaed9c918b2c2b6b049cd8cc9113a)
1657296,2017-01-18 14:24:16 UTC,affects only xenial
1657296,2017-02-17 10:16:08 UTC,"ca531aeeb120cdd should have been sent to be included in 12.0.6, the other one is there and xenial now has 12.0.6"
1657296,2017-05-26 21:46:48 UTC,17.0.x will be backported to xenial
1657305,2017-10-11 11:46:36 UTC,I'm going to mark this is invalid against nova-compute as nova-compute does not have a relation with percona anymore (Icehouse+ I believe).
1657305,2017-03-14 02:50:20 UTC,"Based on Ryan's assessment and marking of this as 'Invalid' for juju (ubuntu), I am marking this as 'Invalid' for ""juju"" project too."
1657305,2017-01-25 18:16:37 UTC,"Reviewed:  https://review.openstack.org/424911
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=881591871513489a67733d593cdb0721d41b5012
Submitter: Jenkins
Branch:    master"
1657305,2017-01-25 12:15:36 UTC,"In the scope of the percona-charm, we see two problems:"
1657305,2017-01-24 21:54:01 UTC,"Larry - for percona-cluster, you'll need to provide a binding for the shared-db relation to oil as well; no need to use the access-network configuration option (infact that prevents the use of juju network space binding in the charm)."
1657305,2017-01-25 11:09:57 UTC,"I appreciate the need to move charms to the network-get --primary-address charm hook tool to support use of network spaces, but I still feel that there might be a 'undefined behaviour' use case in this code path."
1657305,2017-01-23 20:08:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657305,2017-01-19 17:51:50 UTC,here is the comment from juju team John Meinel:
1657305,2017-01-19 16:28:06 UTC,"According to John Meinel:
'The charms should be updated to use ""network-get <bindname>
--preferred-address"" instead of just ""unit-get private-address"".
unit-get doesn't pass the information to Juju for us to know which bit
of the configuration we're supposed to be reporting.'"
1657305,2017-01-18 17:43:44 UTC,According to John Meinel:
1657305,2017-01-24 18:11:46 UTC,I was able to get the percona-cluster to fetch the correct private-address by using access-network option to specify the correct network where I expected this private-address to be on.
1657310,2017-01-18 06:46:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421692"
1657310,2017-01-18 06:48:44 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/421694"
1657310,2017-01-23 09:39:24 UTC,"Reviewed:  https://review.openstack.org/421692
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=418e60724b22fac983ed354aa3e77884076e7c94
Submitter: Jenkins
Branch:    master"
1657310,2017-01-27 01:17:03 UTC,This issue was fixed in the openstack/congress 5.0.0.0b3 development milestone.
1657310,2017-02-18 00:57:39 UTC,"Reviewed:  https://review.openstack.org/421694
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=e37601f9091b0db21bb2d5430afe647cf56a7539
Submitter: Jenkins
Branch:    stable/newton"
1657310,2017-03-13 19:07:55 UTC,This issue was fixed in the openstack/congress 4.0.1 release.
1657312,2017-02-15 10:18:47 UTC, I've thought about this question and maybe it's not a bug. The List type is just designed for one single element type.
1657315,2017-01-19 01:27:52 UTC,diagnostic snapshot - fuel logs
1657315,2017-01-19 01:28:23 UTC,diagnostic snapshot - node logs (node with virt role)
1657315,2017-01-18 18:46:50 UTC,"bummer, I actually tried with 10.0 and it also fails. Anyway, logs will follow later today."
1657315,2017-01-19 01:27:30 UTC,diagnostic snapshot - configs/outputs
1657315,2017-01-18 11:54:07 UTC,"Dmitry, it would be really useful to have a little bit of logs."
1657315,2017-01-18 18:46:15 UTC,"I'll reproduce once more and attach logs later today. The point is that with VLAN segmentation there is no ""br-mesh"", so obviously there's some hardcoded logic in generate_vms or relevant place which won't work with VLAN segmentation networking. This is 9.0, have not tried on 9.1+"
1657317,2017-01-20 12:50:16 UTC,There's actually as you guessed a divergence between the USFA rules and the FIE rules (http://static.fie.org/uploads/8/44436-book%20t.pdf).
1657322,2020-09-21 17:55:59 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/753105"
1657322,2020-09-24 16:19:29 UTC,"Reviewed:  https://review.opendev.org/753105
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=c4617f4fff7555a47b6f5fc44263cb0ef719e1e0
Submitter: Zuul
Branch:    master"
1657339,2018-06-04 11:09:43 UTC,"Reviewed:  https://review.openstack.org/571748
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=84a7945bca43205ce2c92cdd34b27da12749d24f
Submitter: Zuul
Branch:    master"
1657339,2017-02-09 15:14:48 UTC,"Change abandoned by Paul Hummer (<email address hidden>) on branch: master
Review: https://review.openstack.org/421679"
1657339,2018-06-01 14:42:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571748"
1657339,2017-01-18 06:06:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421679"
1657348,2017-02-21 07:57:46 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/436344"
1657348,2017-02-10 09:02:13 UTC,"Reviewed:  https://review.openstack.org/431521
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=e9d4aa951dc7f0421e42105c404ae687ff1c45cc
Submitter: Jenkins
Branch:    stable/newton"
1657348,2017-02-10 09:12:07 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/432189"
1657348,2017-02-15 12:53:14 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/434258"
1657348,2017-02-15 18:20:24 UTC,"Change abandoned by Dmitry Sutyagin (<email address hidden>) on branch: master
Review: https://review.openstack.org/425483"
1657348,2017-02-20 13:14:23 UTC,"Reviewed:  https://review.openstack.org/424380
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=03aaca2deeb062e962a81d16c2a75fb5fccfc265
Submitter: Jenkins
Branch:    master"
1657348,2017-02-10 08:03:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432164"
1657348,2017-02-20 14:00:39 UTC,"Reviewed:  https://review.openstack.org/432164
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=2044d32c67984e44f27df64d261b3eb6fc8db553
Submitter: Jenkins
Branch:    master"
1657348,2017-02-22 01:08:45 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/436717"
1657348,2017-06-23 13:18:35 UTC,"I'm going to close this as Won't Fix for Mitaka, since the change is pretty big and the pagination is a feature itself. This is not acceptable by maintenance policy."
1657348,2017-02-27 08:48:28 UTC,"Reviewed:  https://review.openstack.org/436341
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=e2a7884484c4c9243ccc2f04ab00c747910b52cb
Submitter: Jenkins
Branch:    stable/newton"
1657348,2017-02-27 09:05:48 UTC,"Reviewed:  https://review.openstack.org/436718
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=c89a8569db3f6bc4e244a8890f150f0b5c70eaea
Submitter: Jenkins
Branch:    stable/newton"
1657348,2017-09-20 07:21:48 UTC,"Change abandoned by Joshua Hesketh (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/436344
Reason: This branch (stable/mitaka) is at End Of Life"
1657348,2019-12-18 16:47:18 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/mitaka
Review: https://review.opendev.org/436717
Reason: This repo is retired now, no further work will get merged."
1657348,2019-12-18 16:47:35 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/mitaka
Review: https://review.opendev.org/432189
Reason: This repo is retired now, no further work will get merged."
1657348,2019-12-18 17:47:19 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/mitaka
Review: https://review.opendev.org/434258
Reason: This repo is retired now, no further work will get merged."
1657348,2019-12-18 17:47:25 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/mitaka
Review: https://review.opendev.org/426179
Reason: This repo is retired now, no further work will get merged."
1657348,2017-02-09 13:29:49 UTC,"Reviewed:  https://review.openstack.org/426691
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=44fa844e613ccaddd65e39ba7ebffe4e53efae06
Submitter: Jenkins
Branch:    master"
1657348,2017-02-22 01:09:39 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/436718"
1657348,2017-02-09 13:27:14 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/431521"
1657348,2017-02-21 07:32:50 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/436341"
1657348,2017-02-09 07:32:24 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/431353"
1657348,2017-02-09 11:38:42 UTC,"Reviewed:  https://review.openstack.org/431353
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=d66a0cdb97505c79babeb798861d43095ea3f465
Submitter: Jenkins
Branch:    stable/newton"
1657348,2017-01-18 07:56:21 UTC,"Looks like the problem is a big amount of notifications in the environment (~10500 items). UI polls notifications every 20sec and gets them all at once every time.
We need to think how to reorganize notifications UX. For example, it can be a separate api endpoint to get total and unread notifications number. And pagination can be supported for notification list."
1657348,2017-01-18 07:57:19 UTC,Workaround is to clear notifications table in nailgun DB.
1657348,2017-01-18 12:46:45 UTC,Mitaka branch doesn't support the scale more than 200 nodes. Will be fixed in Ocata and Newton
1657348,2017-01-23 22:16:28 UTC,"St to Confirmed for Mitaka and we can target it to 9.3 (9.2 MU1).
In case of many notifications - can we show first 1000 and say that there is more? Or paginate?"
1657348,2017-01-24 00:17:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424386"
1657348,2017-01-24 13:01:36 UTC,Issue is not reproducible in Firefox  50.1.0
1657348,2017-01-24 17:01:34 UTC,Issued reproduced in Chrome after 354 notifications.
1657348,2017-01-26 01:02:23 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/425483"
1657348,2017-01-23 23:59:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/424380"
1657348,2017-02-09 07:26:40 UTC,"Change abandoned by Julia Aranovich (<email address hidden>) on branch: master
Review: https://review.openstack.org/424386
Reason: Let me abandon this patch. UI changes for the issue are moved to https://review.openstack.org/#/c/426691/"
1657348,2017-01-27 11:27:21 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/426179"
1657348,2017-01-27 11:27:57 UTC,"Change abandoned by Julia Aranovich (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/426179"
1657348,2017-01-30 09:55:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/426691"
1657348,2017-01-31 10:11:39 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/427082"
1657348,2017-01-31 11:36:42 UTC,"Reviewed:  https://review.openstack.org/425719
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=d4bf85957e13abecc519c84f43122e55df510eec
Submitter: Jenkins
Branch:    master"
1657348,2017-02-08 14:32:37 UTC,"Reviewed:  https://review.openstack.org/427085
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=71fb921dbe2a2cc845a4b48f96fb45dcaae6b4fb
Submitter: Jenkins
Branch:    master"
1657348,2017-02-08 14:34:00 UTC,"Reviewed:  https://review.openstack.org/427082
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=2d50d938112c0dde825dc95aa7311a8798af78ba
Submitter: Jenkins
Branch:    stable/newton"
1657348,2017-01-26 14:31:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/425719"
1657350,2017-01-27 21:07:52 UTC,"Reviewed:  https://review.openstack.org/425684
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e46b57befc0032448e12581dc64458170280d465
Submitter: Jenkins
Branch:    master"
1657350,2017-02-01 09:07:34 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/427593"
1657350,2017-02-08 14:33:50 UTC,"Reviewed:  https://review.openstack.org/426175
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=836061341e636ef70d9ea0d7ad871bfdf1a79e9f
Submitter: Jenkins
Branch:    stable/newton"
1657350,2017-02-27 16:24:17 UTC,This issue was fixed in the openstack/fuel-web 11.0.0.0rc1 release candidate.
1657350,2017-10-25 11:29:55 UTC,"Change abandoned by Alexey Stupnikov <email address hidden> on branch: 9.0/mitaka
Review: https://review.fuel-infra.org/36967
Reason: It looks like the reported issue was fixed with fuel-web patch and there is no need to merge anything to fuel-ui."
1657350,2017-06-29 12:16:54 UTC,It turns out that this patch https://review.openstack.org/#/c/427566/ has to be also merged in order to finally fix the bug. Moving bug to 9.2-mu-3 to fix it properly.
1657350,2017-10-24 12:50:48 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Julia Aranovich <email address hidden>
Review: https://review.fuel-infra.org/36967"
1657350,2017-10-25 06:15:40 UTC,I was unable to reproduce this issue in a lab without fuel-ui fix. I believe that this bug was fixed with fuel-web patch and should be closed as Fix Released.
1657350,2017-01-27 11:27:45 UTC,"Change abandoned by Julia Aranovich (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/426175"
1657350,2017-06-23 15:12:03 UTC,"Reviewed:  https://review.openstack.org/427593
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e6c922a82a7450afdbf7c75f6fbdfe3a9918ea7c
Submitter: Jenkins
Branch:    stable/mitaka"
1657350,2017-01-27 11:19:09 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/426175"
1657350,2017-10-24 19:39:57 UTC,"Fuel-ui patch works bad in our lab: after node removal it shows a dialogue window that hangs up and doesn't show OK button. It is possible to close it by simply clicking near this window, but it is still not ok."
1657350,2017-01-26 15:15:21 UTC,"Reviewed:  https://review.openstack.org/425696
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=17495ac4676b03e5b44a843836bcbe009232fd45
Submitter: Jenkins
Branch:    stable/newton"
1657350,2017-01-18 07:47:23 UTC,"First, the following issue should be fixed:
api call to delete the second node returns error, but this error isn't shown in the error dialog. It happens because of an invalid format of api response. Now it's a simple string (error message), but should be an object of the following format:
{message: 'Error message ...', errors: []}"
1657350,2017-01-18 07:50:35 UTC,Then we should consider UX of a few nodes deletion. We need to get user information that it is possible to remove 1 node only at the same time:
1657350,2017-01-24 13:51:06 UTC,"As far as we have a handler for bulk node removal (https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/api/v1/handlers/node.py#L163), it was decided to move Remove button from a node panel to node management toolbar to support the bulk action. User will be able to remove a group of offline nodes at once."
1657350,2017-01-25 10:06:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/425099"
1657350,2017-01-27 11:02:52 UTC,"Reviewed:  https://review.openstack.org/425743
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=de101edf0338fe70eb445d6f7a9508a142c5ae22
Submitter: Jenkins
Branch:    stable/mitaka"
1657350,2017-01-26 13:20:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/425684"
1657350,2017-01-26 13:42:42 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/425696"
1657350,2017-01-26 13:44:31 UTC,"Reviewed:  https://review.openstack.org/425099
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=be80843f05c64a1258d334b006d3ed638fa7218b
Submitter: Jenkins
Branch:    master"
1657350,2017-01-26 09:55:19 UTC,"Bulk offline node removal added here: https://review.openstack.org/#/c/425099/
The other part of the issue fix is to update a format of error message (which tells that node_deletion task is already running), it should be:
{message: 'Error message ...', errors: []} (it's a single string now)"
1657350,2017-01-26 15:07:31 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/425743"
1657353,2017-02-02 16:59:00 UTC,This bug was fixed in the package linux - 4.4.0-62.83
1657353,2017-02-02 09:37:03 UTC,"co-worked with Timo and verified passed with 4K monitor attached on mDP.
kernel: Linux u-Precision-5520 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1657353,2017-07-26 15:57:03 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1657353,2017-01-19 13:16:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1657354,2017-01-19 09:44:03 UTC,"This is related to fuel-plugin-ovs, so mark as invalid for stock Fuel."
1657366,2017-02-03 19:39:33 UTC,Agree. We end up having wrong mapping for sort_dir when some directions are missed in between. This is handled well in python-novaclient but not in api.
1657366,2017-06-27 19:26:15 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1657367,2017-01-19 15:50:52 UTC,Unfortunately i have no ability to copy mainline kernel boot log from ILOM screen... What additional information should i provide?
1657367,2020-06-16 21:31:06 UTC,I'm having this issue in a fresh install of Ubuntu 20.04 with an Intel NIC and the IGC driver.
1657367,2017-01-19 15:40:09 UTC,Thanks for your help!
1657367,2017-01-18 16:25:49 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1657367,2017-01-18 09:11:04 UTC,apport information
1657367,2017-01-18 09:11:02 UTC,apport information
1657367,2017-01-18 09:11:01 UTC,apport information
1657367,2017-01-18 09:10:59 UTC,apport information
1657367,2017-01-18 09:10:58 UTC,apport information
1657367,2017-01-18 09:10:56 UTC,apport information
1657367,2017-01-18 09:10:54 UTC,apport information
1657367,2017-01-18 09:10:51 UTC,apport information
1657367,2017-01-18 09:10:50 UTC,apport information
1657367,2017-01-18 09:00:12 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1657367,2017-01-18 09:10:57 UTC,apport information
1657372,2018-02-28 00:08:20 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu1
1657374,2017-03-16 22:25:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657374,2017-05-13 14:35:49 UTC,This is related to https://bugs.launchpad.net/ubuntu/+source/assimp/+bug/1589949
1657376,2017-01-27 11:21:32 UTC,"I run connectivity check before started deployment and i have such error , after that i can't start deployment process."
1657376,2017-01-27 11:36:48 UTC,"Sorry, my previous comment was wrong. I can start deployment process."
1657376,2017-01-18 13:21:34 UTC,"It it expected behavior. Astute service was run, but could not connect to RabbitMQ because it is missing or not configured. Astute report about such behavior into log and try to reconnect.
After successful connection Astute done his work without any errors."
1657390,2017-01-18 11:03:25 UTC,What is your setting for include_service_catalog?
1657390,2017-01-18 11:11:26 UTC,FYI: https://review.openstack.org/#/c/59371
1657390,2017-01-18 11:23:50 UTC,">What is your setting for include_service_catalog?
"
1657390,2017-09-28 00:49:55 UTC,"Our sample config makes it seem like that defaults to False [1], but it definitely defaults to True [2] and has for a very long time [3]."
1657390,2017-09-28 00:52:05 UTC,"*Maybe* we could also get away with having swift's keystoneauth middleware drop any x-service-catalog headers it finds? I'm not sure who uses it or where they would be in the pipeline, though."
1657395,2017-01-23 22:28:44 UTC,This bug was fixed in the package u-boot - 2016.01+dfsg1-2ubuntu3
1657395,2017-01-23 22:28:43 UTC,This bug was fixed in the package u-boot - 2016.03+dfsg1-6ubuntu2~1.2
1657395,2017-01-23 22:54:16 UTC,flash-kernel and linux-firmware-raspi2 have been pocket-copied to the xenial and yakkety security pockets by Jamie Strandboge:
1657396,2019-09-17 11:36:28 UTC,I have figured this out https://www.widelands.org/forum/topic/4621/
1657396,2017-01-22 12:12:20 UTC,I have no experience with Blender scipting. I will try to find the error. It may take a few days....
1657396,2017-01-21 16:31:28 UTC,"This is what my render attempts now look like with the fixed file - I can't run the python scripts any more. It refers to an error and advises to look at the console, which then contains no messages at all."
1657397,2018-08-16 19:53:25 UTC,"With the porting to Ayatana indicators underway, it looks like more desktops (Xfce, MATE) have support for indicators. Besides the situation of GNOME 3 support (tracked @ https://github.com/varietywalls/variety/issues/12), is this still an issue?"
1657406,2017-04-10 14:04:41 UTC,"Hey, any progress or decision on this?"
1657406,2018-06-16 19:00:09 UTC,any progress on this?  Appears to affect queens as well.
1657407,2017-03-25 17:31:51 UTC,Fixed by: https://review.openstack.org/#/c/421828/1
1657411,2017-01-21 20:41:10 UTC,"The plugin save-for-web is outdated.
Reason: In Gimp 2.9.x there are changes regarding the image precision, i.e, there are more than 8bit.
Now there are 8, 16, 32 bit integer and 16, and 32 bit floating point precisions."
1657411,2017-01-23 06:19:41 UTC,"I suspect that's the case.
I'll wait for updates.
Thanks for the answer."
1657411,2017-12-29 11:20:12 UTC,"So this turned out to be a rather simple bug in the file-png plug-in:
https://bugzilla.gnome.org/show_bug.cgi?id=777403"
1657411,2018-03-09 21:46:34 UTC,"will it come back, the 'save for web' option?  I dont see it in gimp edge, 8dd8.  just asking."
1657411,2018-03-10 10:37:59 UTC,"Am 09.03.2018 um 22:46 schrieb ROnaldve:

> will it come back, the 'save for web' option?  I dont see it in gimp
> edge, 8dd8.  just asking.
>


Afaik the save for web plugin is outdated due to enormous changes based
on the new colour model, i.e. 8 to 32bit integer, and 16,32bit floating
point as well.
Please ask the GIMP developers regarding your needs. I'm just the
packager. O:-)"
1657415,2021-02-19 15:51:31 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1657415,2019-01-22 14:41:39 UTC,"I don't think so, and in addition to that I feel like this was partially achieved with the wider coverage that we used with the tags. See my comment#4."
1657415,2018-01-26 13:43:56 UTC,"I think we might close this one after this [1] review gets merged. With this in place, we will cover tags on all the primary playbooks, and so we'll give users the ability to make atomic deployments."
1657415,2019-01-22 13:44:12 UTC,Should we keep this open? is this something we want to pursue still?
1657415,2017-02-03 16:07:37 UTC,So I've tried different approaches to accomplish the tags removal:
1657415,2017-01-18 18:56:33 UTC,"Thanks for the write-up Raoul, this has been one of my major annoyances about quickstart for a while."
1657415,2017-06-13 10:20:17 UTC,"After some time and some discussion we came out with the idea of keeping tags inside the main playbooks (like quickstart-extras.yml) and managing all the rest with internal variables.
With this approach we will give users the ability to use an atomic approach on the different phases of the deployment.
A review [1] was created to initiate the discussion, today it just adds the tags to the quickstart-extras.yml playbook, but the aim here is to have documentation of the usage so a user can understand how to use all the stuff."
1657417,2017-01-18 11:16:03 UTC,The parameter binlog_gtid_simple_recovery is set off.
1657417,2018-01-25 09:03:58 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3626
1657436,2017-02-27 16:29:21 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1657436,2017-02-06 17:14:30 UTC,"Reviewed:  https://review.openstack.org/421856
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=3594ac306f5a885b68721c18b396b6aff6cf4017
Submitter: Jenkins
Branch:    stable/newton"
1657436,2017-01-23 08:29:00 UTC,Verified on 9.2 snapshot #782.
1657436,2017-01-19 08:20:10 UTC,"Reviewed:  https://review.openstack.org/421854
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=08f0d29cd9754f25f5c3f41abbade62afcf033dd
Submitter: Jenkins
Branch:    master"
1657436,2017-01-18 12:00:13 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/421856"
1657436,2017-01-18 11:59:58 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/421855"
1657436,2017-01-18 11:59:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/421854"
1657436,2017-01-18 16:33:39 UTC,"Reviewed:  https://review.openstack.org/421855
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=f6cbb7e1caa980033f435715becaf9871b2cc2bf
Submitter: Jenkins
Branch:    stable/mitaka"
1657438,2017-01-27 17:49:40 UTC,i can confirm that bug :(
1657452,2017-03-25 00:59:37 UTC,"Reviewed:  https://review.openstack.org/422234
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=38bce1d869264a6f1ea0e13a0301c8cc4bfc84af
Submitter: Jenkins
Branch:    master"
1657452,2017-01-20 12:58:49 UTC,"I've lowered the importance from critical to low for Ubuntu.  Debian just uploaded python-webob 1:1.6.2-2 to replace 1.7.0-1, which I didn't realize was an option.  We'll get 1:1.6.2-2 synced over to zesty and that should solve our webob problems in Ocata."
1657452,2017-03-29 15:17:11 UTC,"Reviewed:  https://review.openstack.org/423366
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=7a843f7e1fb1bab504fea0b2c59bf7c22121da71
Submitter: Jenkins
Branch:    master"
1657452,2017-04-12 18:49:34 UTC,This issue was fixed in the openstack/keystone 12.0.0.0b1 development milestone.
1657452,2017-01-19 22:58:19 UTC,Appending a few comments that sigmavirus had on bug #1657459:
1657452,2017-10-20 11:45:51 UTC,"Marking all Ubuntu tasks as fix released; Ocata UCA shipped with an earlier webob version anyway, and subsequent releases have the required fix."
1657452,2017-04-11 08:33:43 UTC,This issue was fixed in the openstack/glance 15.0.0.0b1 development milestone.
1657452,2017-01-19 19:07:10 UTC,This appears to also be affecting python-oslo.middleware.  Adding test output from dup bug report:
1657452,2017-03-30 13:47:52 UTC,Here is another related fix that was committed to keystone - https://review.openstack.org/#/c/451559/
1657452,2017-01-18 15:12:06 UTC,This appears to run deeper than just test failures.  See glance bug: https://bugs.launchpad.net/ubuntu/+source/glance/+bug/1657459
1657452,2017-01-18 15:11:23 UTC,Marking this as high at least for ubuntu since this is blocking us from releasing B2 since ubuntu is at webob 1.7.0.
1657452,2017-01-18 14:39:52 UTC,nova failures with webob 1.7.0:
1657452,2017-01-18 14:28:31 UTC,glance failures with webob 1.7.0:
1657452,2017-01-18 20:58:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422234"
1657452,2017-01-18 14:27:04 UTC,I'm going to make some fixes to keystone so that when the upper constraints is eventually bumped up to 1.7 that we won't have an issue.
1657452,2017-01-18 14:26:55 UTC,https://bugs.launchpad.net/keystonemiddleware/+bug/1653646 -- we fixed a similar issue in keystonemiddleware
1657456,2017-01-18 13:33:34 UTC,http://paste.openstack.org/show/595341/
1657459,2017-01-20 12:58:03 UTC,"I've lowered the importance from critical to low for Ubuntu.  Debian just uploaded python-webob 1:1.6.2-2 to replace 1.7.0-1, which I didn't realize was an option.  We'll get 1:1.6.2-2 synced over to zesty and that should solve our webob problems in Ocata."
1657459,2017-04-11 08:33:41 UTC,This issue was fixed in the openstack/glance 15.0.0.0b1 development milestone.
1657459,2017-03-29 15:17:19 UTC,"Reviewed:  https://review.openstack.org/423366
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=7a843f7e1fb1bab504fea0b2c59bf7c22121da71
Submitter: Jenkins
Branch:    master"
1657459,2017-07-05 13:17:15 UTC,"Gurol,"
1657459,2017-02-01 20:56:09 UTC,"Phil, there is a fix for this. The requirements for Ocata are frozen and will not change, and OpenStack also publishes 'upper-constraints.txt' which you can provide to pip using `-c`. For example"
1657459,2017-02-01 20:54:09 UTC,"Hi Phil, I lowered the glance (Ubuntu) package importance to low, which makes sense since we're locked into a single version for ocata in ubuntu (webob 1.6.2). However for the upstream bug I think your're right.  I can't change the importance of the upstream bug, but likely it should be updated."
1657459,2017-02-01 20:32:13 UTC,"Corey,"
1657459,2017-07-04 21:03:25 UTC,"Hello,"
1657459,2017-01-19 22:57:05 UTC,"Alright, in that case I'll copy your comments over to the other bug. :)  Thanks for working on this. Very much appreciate it."
1657459,2017-02-01 21:00:53 UTC,"Phil, if you want to test/review the fix you can find it here: https://review.openstack.org/423366"
1657459,2017-01-19 20:01:20 UTC,I don't think it's appropriate to merge them all into one as the impacts are very different as well as the remediation.
1657459,2017-01-19 19:08:30 UTC,"Ian, would you mind if I mark this as a dup of https://bugs.launchpad.net/nova/+bug/1657452 since we're tracking multiple projects there?"
1657459,2017-01-19 19:05:35 UTC,"I filed https://github.com/Pylons/webob/issues/307 although I doubt anything will come of it upstream. If anything, that might help others."
1657459,2017-01-19 18:51:59 UTC,So the fundamental part of this is that there's a subtle change in webob 1.7.0 in how webob.request.Request.is_body_readable is implemented.
1657459,2017-01-18 15:10:42 UTC,Unfortunately this is blocking us from releasing B2 at the moment.
1657459,2017-01-18 15:07:42 UTC,This is related to issues we're hitting in ubuntu which is at webob 1.7.0 now: https://bugs.launchpad.net/nova/+bug/1657452
1657459,2017-01-18 14:39:40 UTC,"Thanks for the info, I thought it was a singular thing.
In this case, backporting the blacklisting is very important."
1657459,2017-01-18 14:06:50 UTC,"Hi Adrian,"
1657459,2017-01-19 20:33:21 UTC,Another facet of this for Glance seems to be related to the PR in WebOb that broke other projects: http://paste.openstack.org/show/595699/ I suspect this is due to us returning `webob.exc.HTTPNoContent()`. It looks like our gzip middleware expects there to be a content-type but that's no longer auto-generated for us.
1657494,2020-01-06 00:34:11 UTC,"So, might I ask: is this fixed yet?"
1657494,2019-07-23 16:56:46 UTC,"In my case plank was not shooting more than 2,3% of CPU but the total CPU time over all days running would be comparable to Xorg or irq/38-nvidia !!
e.g. the ""TIME+"" column of top after 25 days since last boot is:"
1657494,2019-02-04 07:26:02 UTC,"I have to second what Matt said:
Exactly same behavior here :("
1657494,2018-05-16 21:58:06 UTC,"As a person that leaves their PC running for days and doesn't turn it off, I've been noticing this issue for years, it's very annoying."
1657494,2018-02-16 08:31:27 UTC,Have same problem on Ubuntu 17.10 and plank 0.11.4-1
1657494,2017-07-19 20:43:46 UTC,Is there any progress on this? It's making it pretty much impossible to use without regularly logging in and out (which is not something I would normally do more often than once every week or two).
1657494,2017-06-27 10:39:57 UTC,"strace output of ~30 seconds of running plank, with all threads in the same file."
1657494,2017-06-06 19:34:46 UTC,"that`s what i discovered  after some experiments: when i removed  trashbin, clocks and clippy docklets  CPU usage in idle state goes to less than 1%, but  when any minimal activity is being performed such as typing this text in chromium it`s averaging between 2 and 3%. When I launch new app it temporarily raising to 57% or even more and then reduces  quickly."
1657494,2017-06-17 12:33:13 UTC,"Clippy is a huge cause of CPU usage, as it checks the contents of the clipboard every 500ms (i.e. twice per second). This has been fixed in git."
1657494,2017-06-06 19:22:38 UTC,"apologies, i should have mentioned the versio i use which is 0.11.3 - from the official lubuntu repo."
1657494,2017-06-06 19:20:32 UTC,"I observe ~20% of CPU load when the system is idl, using fresh install of lubuntu 17.04.  When some activity is done, such as apps being opened and closed  it raises up to 60% for a short time and then goes back to ~20. it is never getting below  13%."
1657494,2017-05-13 12:21:20 UTC,I have built the 0.11.4 from sources (Gentoo/Sabayon) and the high CPU usage is still here. As 0.11.4 was released on 2017-03-27 (so after wjmoore's comment) I suspect the bug is still present.
1657494,2017-02-07 23:30:00 UTC,"I was encountering this issue in elementary OS 0.4, which is built on Ubuntu 16.04. I'm now running Arch and have built Plank from source and have had it running for over 4 days now and plank idle CPU usage is < 1%."
1657494,2017-06-27 10:27:36 UTC,"10 days after the last report, plank has accumulated over 860 hours (!) of CPU time for doing nothing."
1657495,2017-01-20 14:53:40 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1657498,2017-02-01 20:21:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/427898"
1657498,2017-01-18 16:12:11 UTC,"Note: I submitted a request to get libdeprecation into global-requirements so that we can use it to carry out these deprecations in an automated way. If that's approved, this will be pretty easy."
1657498,2017-01-19 02:59:06 UTC,"FYI openstack uses debtcollector for that if I'm remembering the name
properly."
1657498,2017-02-15 09:38:27 UTC,"Reviewed:  https://review.openstack.org/427898
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=e97a7550467ccf2bcd69bec57025c2b1d1ce615d
Submitter: Jenkins
Branch:    master"
1657505,2017-01-19 10:32:29 UTC,The libvirt driver knows only a single method for reboot. The input parameter reboot_type specifies if soft or hard reboot should be made.
1657505,2017-01-24 06:07:48 UTC,"Yes, I agree and I feel we should provide a log.warning and add this to documentation. I will figure this out"
1657505,2017-01-19 10:32:51 UTC,And we should state that in the docs!
1657506,2017-01-18 20:12:31 UTC,"Reviewed:  https://review.openstack.org/422071
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=86329c43f1d0b4b3788189196c76220d6635f15a
Submitter: Jenkins
Branch:    master"
1657506,2017-02-27 16:29:16 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1657506,2017-01-18 16:11:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422071"
1657520,2017-01-18 16:55:24 UTC,You can do this via the API but it's a pain. We need to improve the UX.
1657520,2019-09-19 11:55:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1657523,2017-01-18 17:09:40 UTC,"To fix this, I suggest that the defaults be adjusted so the conffile is really just for local overrides rather than distribution-shipped defaults. You could patch upstream to change the defaults to what you want so shipping a contentful conffile becomes unnecessary. Or you could add support to have distribution defaults ship somewhere read-only (eg. /usr/share) and have /etc/waagent.conf available for local overrides. For example, systemd does this with /lib/systemd/system and /etc/systemd/system. Or you could use a conf.d scheme, though I think that would only mitigate the problem rather than solve it."
1657529,2017-01-18 17:38:30 UTC,"List of columns to drop.
https://github.com/openstack/nova/blame/master/nova/db/sqlalchemy/api_models.py#L246"
1657529,2017-01-18 21:50:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422259"
1657529,2017-02-11 01:26:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432511"
1657529,2017-06-27 15:55:28 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'"
1657529,2017-08-01 09:56:09 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/422259
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1657529,2017-08-01 09:59:50 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/432511
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1657532,2017-01-19 13:35:42 UTC,Please provide diagnostic snapshot or env.
1657532,2017-01-19 15:14:24 UTC,Env was provided.
1657532,2017-01-25 13:16:02 UTC,Looks like there is the problem whithin our virtual infrastructure. There was no connectivity between the haproxy netns and b-mgmt. Now I can't reproduce that bug and wait when it reproduces.
1657532,2017-01-27 16:07:29 UTC,Please forget that I told before. The reason of that bug is absence of the route* for the managemnt network in the netns haproxy.
1657532,2017-01-27 17:26:16 UTC,At least we have workaround: # crm resource restart clone_p_haproxy
1657532,2017-01-31 11:41:09 UTC,MOS 9.2 release note: https://review.fuel-infra.org/#/c/30272.
1657537,2017-01-18 18:17:34 UTC,"Reproduced with Inkscape 0.91 r13725, 0.92.9 r15299 and lp:inkscape/0.92.x r15321 on OS X 10.7.5 (the units 'grad' and 'turn' are new in Inkscape 0.91)."
1657538,2017-01-20 11:39:31 UTC,"I can not reproduce this issue. QEMU 2.8 works fine here on a POWER8 big endian host (running RHEL7). Can you still run older versions of QEMU that used to work for you in the past, to check whether it is QEMU or whether it is Ubuntu 16.10 that is causing the trouble here? Could you please also post the full output of the ""configure"" run on your system?"
1657538,2017-01-20 11:41:53 UTC,"Something else to try: Could you please check whether you get any output when you run ""qemu-system-ppc -nographic"" on your system? So we can make sure that it is not related to GTK or something similar..."
1657538,2017-01-20 15:22:18 UTC,"Hi Thomas,
here the configure .. i made a clean one just with the target for have fastest build
will report soon the result with the nographic just the time of build"
1657538,2017-01-20 15:53:19 UTC,"i386-softmmu:
./qemu-system-i386 -nographic
qemu-system-i386: Trying to execute code outside RAM or ROM at 0x000a0000
This usually means one of the following happened: and so and so"
1657538,2017-02-08 14:30:22 UTC,"I can reproduce the same problem on 2.7.0 on a PowerPC G5 for the x86, x86_64 and ppc softmmu targets (minus the Gtk problem, since I use this ported to Cocoa). As with Luigi this seems to be a regression from 2.6.2. There is no change with -nographic."
1657538,2017-02-08 15:19:46 UTC,Oh my gosh the great Cameron Kaiser :)
1657538,2020-02-11 14:11:48 UTC,Looking through old bug tickets ... can you still reproduce the issue with the latest version of QEMU (v4.2) and a more recent Linux distribution?
1657538,2020-05-13 04:17:16 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1657551,2017-01-18 21:05:58 UTC,"Did you enable background-image first (by switching a layer mode to any but 'Normal' and back to 'Normal'), or by manually adding the property to the top-level <svg> element (using the built-in XML Editor, or an external editor)?"
1657551,2017-01-18 21:45:28 UTC,"No.
Somehow overlooked that note in the manual. Thought it was an issue of the editor/filter not updating that I have experienced recently with 0.92, where saving&reopening works."
1657552,2019-10-15 11:58:12 UTC,This was reported against an internal test suite of snapd 2.21 which has seen over 20 subsequent updates. I'm closing this as WONTFIX though perhaps FIX RELEASED is more accurate.
1657558,2018-08-13 17:18:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657560,2017-01-18 22:46:45 UTC,"For completeness, screenshot attached."
1657560,2017-04-06 22:15:46 UTC,https://www.bountysource.com/issues/41119655-notifications-are-half-width-on-hidpi
1657563,2018-01-07 17:47:08 UTC,"As LightDM is now the default login manager in Linux Mint, you can close this bugreport."
1657592,2017-01-18 23:03:52 UTC,Update: It seems that minutes past the half hour are working.
1657593,2017-02-20 18:52:45 UTC,Reproduced with latest devlibs64 and lp:inkscape r15534 on Windows 10.
1657593,2017-02-20 19:24:07 UTC,"Upstream bug:
* 763796 - Excessive runtime warnings from gtk_style_context_get_...()
  https://bugzilla.gnome.org/show_bug.cgi?id=763796"
1657593,2017-10-12 19:05:01 UTC,Fixed in MSYS2 builds.
1657597,2017-01-19 21:41:11 UTC,Sorry all.
1657597,2017-03-16 09:15:16 UTC,It looks like your patch may still be valid for newton. Was it a problem then?
1657597,2017-03-16 00:39:02 UTC,"Change abandoned by Daniel Russell (<email address hidden>) on branch: master
Review: https://review.openstack.org/422309"
1657597,2017-03-16 00:20:55 UTC,Looks like the flow for this doesn't go via this path in Ocata and works fine.  It's probably easiest just to close this off and recommend upgrading to Ocata
1657597,2017-01-20 18:23:21 UTC,No need to apologize :)
1657597,2017-01-18 23:24:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422309"
1657597,2017-01-19 16:04:58 UTC,"Agreed, some exact reproduction steps would be very useful in this bug."
1657597,2017-01-19 08:29:26 UTC,Can you please provide steps how do you get this error?
1657605,2019-05-01 16:28:03 UTC,"Helen, this is another EMC DOCIMPACT bug that jgrosso found doing bug cleanup.  If the doc tasks associated with the review mentioned here have been done please go ahead and close this one out."
1657605,2019-05-02 09:43:39 UTC,"Hi Tom,
Please reassign to Ryan Liang from the VNX/Unity team.  Thank you, Helen"
1657605,2019-10-12 02:42:15 UTC,"Reviewed:  https://review.opendev.org/681381
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=c9d8506f80faa3e9854dadd71305f450f78b0bb2
Submitter: Zuul
Branch:    master"
1657611,2018-01-24 22:28:41 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1409
1657611,2017-04-06 23:53:31 UTC,Thank you for the report.
1657611,2017-01-20 00:31:49 UTC,Note this error has more to do with the 3rd query with html encoding than the Japanese characters. See https://bugs.launchpad.net/percona-toolkit/+bug/1657926.
1657611,2017-04-06 23:53:50 UTC,Tested with versions 2.2.20 and 3.0.2
1657613,2017-01-19 01:14:58 UTC,One way we could do this is check the error logs it could be more generic like: You had 20 error messages for LDAP binding over the last 1 week. check the error log.
1657633,2017-01-19 19:00:12 UTC,"Do you mean the screen with the ""Configuration complete"" header or the one
that starts ""Congratulations! This device is now registered to
{realname}.""? The former would surprise me, the latter not at all really."
1657633,2017-01-20 01:17:42 UTC,"Hi @Michael,"
1657633,2017-01-20 01:31:51 UTC,"It has associated with another AP with a different subnet, but the IP address displayed is still the old one."
1657633,2020-10-14 16:32:49 UTC,console-conf is not meant to be used more than once....
1657633,2020-10-14 17:09:37 UTC,It used to be a pretty common practice in the community in UC16 days to (ab)use console-conf as network-setup GUI when you had a device that needed to be moved between WLANs regulary (note that there wasn't even documentation about netplan in the early days of UC16. netplan was used in Ubuntu Core way before it entered the normal Ubuntu distro as a default tool).
1657633,2020-10-15 02:24:03 UTC,"At that moment, I found console-conf could be used to update the network configuration easily. that was the reason I used console-conf in that way."
1657639,2017-11-03 16:42:24 UTC,Syncing task from Mir.
1657640,2017-05-05 19:55:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657644,2017-01-28 03:53:33 UTC,This also happens on Ubuntu 16.10. I'm running Cinnamon 3.0.7 on x86_64.
1657646,2019-05-02 06:10:05 UTC,"------- Comment From <email address hidden> 2019-05-02 02:06 EDT-------
Canonical , Could you confirm which release this issue could be fixed ?"
1657646,2019-04-09 21:40:04 UTC,"------- Comment From <email address hidden> 2019-04-09 17:29 EDT-------
Per above comment, this is a legitimate problem and needs to be worked. Not sure in which release it should be worked, though. But moving out of DEFERRED."
1657646,2019-09-10 11:24:20 UTC,This bug was fixed in the package lvm2 - 2.03.02-2ubuntu6
1657646,2018-10-24 23:33:56 UTC,This is related to a problem I've encountered today with lvmcache partitions.
1657646,2019-05-08 08:59:55 UTC,"------- Comment From <email address hidden> 2019-05-08 04:56 EDT-------
Canonical , Could you confirm which release this issue could be fixed ?"
1657646,2017-06-29 09:51:34 UTC,"IMHO thin-provisioning is an optional volumes type in LVM2 and is not required for operating LVM. The fact that lvconvert works to convert things to/from optionally supported types, is imho ok. In the same way we ship many tools that can convert formats but not necessarily open those for modification. E.g. i can use qemu-img to convert disk images to e.g. VMWare format but I might not have any hypervisor that knows how to boot such an image and allow to modify it (e.g. upgrade packages)."
1657646,2018-10-24 23:35:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657646,2019-05-08 12:04:21 UTC,We will investigate and update this bug shortly.
1657646,2019-09-10 12:30:59 UTC,Hrm ??
1657646,2019-05-09 07:20:55 UTC,Note that this is likely to require an MIR (https://wiki.ubuntu.com/MainInclusionProcess) for thin-provisioning-tools for 20.04.
1657646,2019-05-13 20:40:54 UTC,I'll prepare an MIR in https://bugs.launchpad.net/ubuntu/+source/thin-provisioning-tools/+bug/1828887
1657646,2017-06-29 09:28:46 UTC,Default Comment by Bridge
1657646,2019-09-10 12:33:50 UTC,The MIR itself (bug 1828887) also got no update.
1657646,2019-09-11 08:01:32 UTC,"Ok, it got spotted and became a component mismatch as expected in the tool run tonight.
All is fine again, sorry for the noise."
1657646,2020-08-07 11:31:06 UTC,"------- Comment From <email address hidden> 2020-08-07 07:20 EDT-------
There is no update for this bug for more than 6 months. Also it is been old bug now."
1657646,2019-05-08 18:27:57 UTC,"I have lowered the priority on this bug to Medium and we are expected to address this in 20.04. The proposed fix is to add  thin-provisioning-tools package to ""recommends"" in lvm2 so that it will be automatically installed when we install lvm2."
1657646,2017-06-29 09:24:26 UTC,"> Canonical, We installed thin-provisioning-tools and have tested and not able to see the issue.
> Our tester need some clarification related to the update done above..
"
1657646,2019-05-08 17:58:01 UTC,"The lvm2 package lists thin-provisioning-tools as a suggested package rather than ""Depends"", this is because thin-provisioning-tools is in the universe archive (Community supported) and lvm2 is in the main archive (Canonical supported). So, when you install lvm2 you should see thin-provisioning-tools under ""suggested packages"", and you have to separately list thin-provisioning-tools on the command line when you install lvm2. This is the case for all architectures not just for Power."
1657646,2017-06-27 13:20:15 UTC,"------- Comment From <email address hidden> 2017-06-27 08:44 EDT-------
I tried again after installing thin-provisioning-tools, after the reboot."
1657646,2017-01-19 05:39:20 UTC,Default Comment by Bridge
1657646,2017-01-19 05:39:21 UTC,Default Comment by Bridge
1657646,2017-01-23 22:19:26 UTC,"------- Comment From <email address hidden> 2017-01-23 17:10 EDT-------
An sosreport would be useful for those looking into the problem. Additionally, setting the log level in /etc/lvm/lvm.conf level= to a high value so we can get some debug output would be great."
1657646,2017-01-25 13:19:39 UTC,"Hi,
as usual bugproxy accumulated a lot of info to go through.
I'll try to summarize - please feel free to correct - ""VG/LV are not available in /dev/mapper/ after reboot"".
Would that be a proper (and simpler) definition of the issue?"
1657646,2017-06-29 07:20:09 UTC,"------- Comment From <email address hidden> 2017-06-29 03:11 EDT-------
(In reply to comment #52)

> I tried again after installing thin-provisioning-tools, after the reboot.
>
> The docker service/daemon was up.
> I don't see the issue
>
> root@bamlp5:~# apt-get install thin-provisioning-tools
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following NEW packages will be installed:
>   thin-provisioning-tools
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 339 kB of archives.
> After this operation, 1,627 kB of additional disk space will be used.
> Get:1 http://gb.ports.ubuntu.com/ubuntu-ports xenial/universe ppc64el
> thin-provisioning-tools ppc64el 0.5.6-1ubuntu1 [339 kB]
> Fetched 339 kB in 0s (429 kB/s)
> Selecting previously unselected package thin-provisioning-tools.
> (Reading database ... 64237 files and directories currently installed.)
> Preparing to unpack .../thin-provisioning-tools_0.5.6-1ubuntu1_ppc64el.deb
> ...
> Unpacking thin-provisioning-tools (0.5.6-1ubuntu1) ...
> Processing triggers for man-db (2.7.5-1) ...
> Setting up thin-provisioning-tools (0.5.6-1ubuntu1) ...
>
> root@bamlp5:~# docker info
> Containers: 0
>  Running: 0
>  Paused: 0
>  Stopped: 0
> Images: 0
> Server Version: 1.12.6
> Storage Driver: devicemapper
>  Pool Name: docker--storage-thinpool
>  Pool Blocksize: 65.54 kB
>  Base Device Size: 10.74 GB
>  Backing Filesystem: xfs
>  Data file:
>  Metadata file:
>  Data Space Used: 11.8 MB
>  Data Space Total: 30.6 GB
>  Data Space Available: 30.59 GB
>  Metadata Space Used: 172 kB
>  Metadata Space Total: 318.8 MB
>  Metadata Space Available: 318.6 MB
>  Thin Pool Minimum Free Space: 3.06 GB
>  Udev Sync Supported: true
>  Deferred Removal Enabled: false
>  Deferred Deletion Enabled: false
>  Deferred Deleted Device Count: 0
>  Library Version: 1.02.110 (2015-10-30)
> Logging Driver: json-file
> Cgroup Driver: cgroupfs
> Plugins:
>  Volume: local
>  Network: null host bridge overlay
> Swarm: inactive
> Runtimes: runc
> Default Runtime: runc
> Security Options: apparmor seccomp
> Kernel Version: 4.4.0-81-generic
> Operating System: Ubuntu 16.04.2 LTS
> OSType: linux
> Architecture: ppc64le
> CPUs: 8
> Total Memory: 967.4 MiB
> Name: bamlp5
> ID: EFRP:SO44:CIMD:TPH5:BBKN:RYBT:QZGE:7U7H:DOYF:OBI6:SKLG:DUCO
> Docker Root Dir: /var/lib/docker
> Debug Mode (client): false
> Debug Mode (server): false
> Registry: https://index.docker.io/v1/
> WARNING: No swap limit support
> Insecure Registries:
>  127.0.0.0/8
>
> root@bamlp5:~# reboot
> Connection to bamlp5 closed by remote host.
> Connection to bamlp5 closed.
>
> [vinutha@kte ~]$ ssh root@bamlp5
> root@bamlp5's password:
> Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-81-generic ppc64le)
>
>  * Documentation:  https://help.ubuntu.com
>  * Management:     https://landscape.canonical.com
>  * Support:        https://ubuntu.com/advantage
>
> *****************************************************************************
> ***
>
>   IBM Business Use Statement
>   --------------------------
>
>     IBM's internal systems must only be used for conducting IBM's business or
>     for purposes aut...
"
1657646,2017-01-25 13:20:47 UTC,"Internal: for anyone else debugging on this, the mentioned test setup is on Diamond in guest ""paelzer-testlvm-xenial"""
1657646,2017-02-22 05:39:26 UTC,"------- Comment From <email address hidden> 2017-02-22 00:29 EDT-------
(In reply to comment #30)

>
> Hi,
> as usual bugproxy accumulated a lot of info to go through.
> I'll try to summarize - please feel free to correct - ""VG/LV are not
> available in /dev/mapper/ after reboot"".
> Would that be a proper (and simpler) definition of the issue?
>
> I tried to recreate.
> Note: as it was reported on power + Xenial this test was done on ppc64el
> Xenial as of today
>
> To do so with as much debugging as possible I created a normal Xenial KVM
> Guest via
> $ uvt-kvm create --cpu 4 --password=ubuntu paelzer-testlvm-xenial
> release=xenial
> Then I added a few more disks to be used as PVs
> $ sudo qemu-img create -f qcow2 test-lvm-disk1.qcow2 8
> And added those to the Guest.
>
> The guest then initially looks like:
> $ lsblk
> NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> vda    253:0    0    8G  0 disk
> vdb    253:16   0    8G  0 disk
> vdc    253:32   0    8G  0 disk
> vdd    253:48   0  366K  0 disk
> vde    253:64   0    8G  0 disk
> |-vde1 253:65   0    8G  0 part /
> `-vde2 253:66   0    8M  0 part
>
> Then the usual flow is
> 1. fdisk, create partition set LVM partition type (8e)
> $ sudo fdisk /dev/vd[abc]
> 2. Full PVs on all the three disks
> $ sudo pvcreate /dev/vd[abc]
> 3. vgcreate a single VG out of all of the PVs
> $ sudo vgcreate vg /dev/vda1 /dev/vdb1 /dev/vdc1
>
> At this point it looks like this:
> $ sudo vgdisplay vg
> --- Volume group ---
> VG Name               vg
> System ID
> Format                lvm2
> Metadata Areas        3
> Metadata Sequence No  1
> VG Access             read/write
> VG Status             resizable
> MAX LV                0
> Cur LV                0
> Open LV               0
> Max PV                0
> Cur PV                3
> Act PV                3
> VG Size               23.99 GiB
> PE Size               4.00 MiB
> Total PE              6141
> Alloc PE / Size       0 / 0
> Free  PE / Size       6141 / 23.99 GiB
> VG UUID               1QMFbn-5DAW-T9IE-Fdfd-9RZK-t8gl-5nte5r
>
> Ok, create normal as well as thin LVs out of that now.
> First of all thin provisioning is not mainstream, the dependency is only a
> suggest, so install the tools
> $ sudo apt-get install thin-provisioning-tools
> Then create the normal LV
> $ sudo lvcreate -L 5G --name lv_normal vg
> And finally a thin LV
> $ sudo lvcreate --size 10G --virtualsize 5G --thinpool mythinpool --name
> lv_thin vg
> Lets go harder and overprovision the thinpool
> $ sudo lvcreate --virtualsize 5G --thinpool mythinpool --name lv_thin2 vg
> $ sudo lvcreate --virtualsize 5G --thinpool mythinpool --name lv_thin3 vg
>
> With that in place my LVs look like:
> $ sudo lvdisplay
> --- Logical volume ---
> LV Path                /dev/vg/lv_normal
> LV Name                lv_normal
> VG Name                vg
> LV UUID                aCtNC0-gbx1-uHoB-3dC8-dfhl-NBxd-Axm879
> LV Write Access        read/write
> LV Creation host, time paelzer-testlvm-xenial, 2017-01-25 12:54:02 +0000
> LV Status              available
> # open                 0
> LV Size                5.00 GiB
> Current LE             1280
> Segments               1
> Allocation             inher...
"
1657646,2017-01-25 13:20:09 UTC,"I tried to recreate.
Note: as it was reported on power + Xenial this test was done on ppc64el Xenial as of today"
1657646,2017-05-04 08:49:45 UTC,Default Comment by Bridge
1657646,2017-05-11 09:49:36 UTC,"------- Comment From <email address hidden> 2017-05-11 05:45 EDT-------
I'm once again updating the steps that were followed to configure a thinpool,"
1657646,2017-05-12 05:29:31 UTC,"------- Comment From <email address hidden> 2017-05-12 01:19 EDT-------
Canonical,"
1657646,2017-05-12 06:11:43 UTC,"Thanks for providing the steps, I have no time to set this up ""right now"" but 'm setting it back to new to mark that we are no more waiting on info from you until further analyzed."
1657646,2017-06-20 20:51:57 UTC,"TL;DR ""sudo apt install thin-provisioning-tools"" fixes it."
1657646,2017-06-20 20:54:15 UTC,@paelzer noted this in his comment #5:
1657646,2017-06-21 14:54:23 UTC,"I'm marking this bug as ""new"" again because of the package change (from docker.io to lvm2), to allow it to be triaged again in this new context."
1657646,2017-02-22 14:40:05 UTC,"Hi,
the proxy did well at hiding your actual reply by quoting my full pust."
1657652,2017-04-10 14:31:24 UTC,"Is this re-using the same token, generating multiple tokens for your user, or?"
1657652,2017-04-11 00:19:13 UTC,"@Cory Jones,"
1657652,2017-06-10 04:17:58 UTC,[Expired for juju because there has been no activity for 60 days.]
1657652,2017-08-15 16:00:43 UTC,"I missed this bug being created.  John: I don't think I realized you could register an arbitrary controller via its DNS name.  That is probably fine for CI applications, since re-using the username and password in that case is acceptable.  Being able to register by IP would be a good feature as well, since the CI system might not always have a resolvable name, but I don't think it's as critical."
1657672,2017-02-13 03:31:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432829"
1657682,2018-05-21 23:58:49 UTC,This bug was fixed in the package linux-oem - 4.15.0-1006.9
1657682,2018-05-21 11:48:23 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1657682,2017-02-20 07:42:07 UTC,This bug was fixed in the package linux - 4.4.0-63.84
1657682,2017-02-09 22:02:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1657682,2017-02-17 11:52:03 UTC,Release notes from Redpine for ver. 0.9.7
1657687,2017-03-21 15:37:55 UTC,Can you provide more information?  It looks like you're using Castellan to interface with Barbican.  Have you written your own code that uses Castellan?  Can you provide example code?
1657709,2017-02-27 16:24:20 UTC,This issue was fixed in the openstack/fuel-web 11.0.0.0rc1 release candidate.
1657709,2017-04-18 09:48:51 UTC,verified on 1575 build
1657709,2017-02-09 11:54:06 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/431464"
1657709,2017-01-20 09:10:11 UTC,Verified on 9.2 snapshot #785.
1657709,2017-02-13 13:57:14 UTC,"Reviewed:  https://review.openstack.org/431464
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=aee06be9b6efcdc9a39d9ba3caf68eef7b012669
Submitter: Jenkins
Branch:    stable/newton"
1657709,2017-01-19 15:03:56 UTC,"Reviewed:  https://review.openstack.org/422567
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=105a069bf6401288a1bcc9e16a2f71f35f76f254
Submitter: Jenkins
Branch:    stable/mitaka"
1657709,2017-01-19 11:38:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422569"
1657709,2017-01-19 11:38:09 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/422567"
1657709,2017-01-19 15:04:30 UTC,"Reviewed:  https://review.openstack.org/422569
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=b315dda52ee2ca9fd514f61803e3726e9deff5b7
Submitter: Jenkins
Branch:    master"
1657712,2017-01-19 16:16:11 UTC,Strict SetInstanceStatus states.
1657712,2017-03-21 01:35:53 UTC,"As this is a tech-debt item, I am lowering its Importance."
1657716,2017-01-27 13:25:27 UTC,The issue is about report for failed task while actually task completed successfully.
1657716,2017-01-30 12:50:28 UTC,Small additional: you need to restart Astute service after config change to apply changes. You can do it using this command:
1657716,2017-01-19 11:44:08 UTC,Fuel logs available on
1657716,2017-01-26 12:20:22 UTC,This is expected behaviour due to fault tolerance settings
1657716,2017-01-26 16:09:08 UTC,"Yep, Vladimir is absolutely right."
1657716,2017-01-30 12:47:13 UTC,It is expected and message is correct. Node has temporary network problem which block normal workflow between master node and deploying node. So task was run without any problem on node but Astute could not read status from node.
1657721,2017-01-26 11:04:26 UTC,"For 10 we should move serizalization to the nodes.
For 9.x we have workaround for scale - set LCM_SERIALIZERS_CONCURRENCY_FACTOR = CPU_NUMBER - 1 to the Nailgun settings. It saves one CPU for handling API requests. For 9.x set status to Won't fix."
1657721,2017-01-26 11:00:42 UTC,"Change abandoned by Alexander Kislitsky (<email address hidden>) on branch: master
Review: https://review.openstack.org/425630
Reason: Should be done in different way."
1657721,2017-01-26 10:58:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/425630"
1657721,2017-01-24 12:56:18 UTC,For encrease speed of nodes API response we need handle list of required fields of node data and use this list in the Fuel CLI.
1657721,2017-01-19 12:02:23 UTC,After 10-20 minutes Fuel start working again
1657721,2017-01-26 10:10:02 UTC,Nailgun is working on data and graph serialization. It takes dozens minutes for hundreds of nodes. As fix we shouldn't acquire all processors for serialization.
1657727,2017-03-30 11:29:10 UTC,"Reviewed:  https://review.openstack.org/450870
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=41d4a11ee73337de2e9a5cf8fe983c6f0a114bc6
Submitter: Jenkins
Branch:    stable/newton"
1657727,2017-02-20 13:32:26 UTC,"Reviewed:  https://review.openstack.org/427733
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=812b15bccf2d49714bcc098f38a4dde13d37890e
Submitter: Jenkins
Branch:    stable/7.0"
1657727,2017-03-28 15:55:05 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/450870"
1657727,2017-02-27 16:29:09 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1657727,2017-04-07 13:08:43 UTC,"Verified by several swarm runs, including both RC1 and RC2"
1657727,2017-01-26 12:26:38 UTC,Feels like fixed - swarm runs on 801 and 804 snapshots does not contains this failure
1657727,2017-01-20 16:28:01 UTC,"Reviewed:  https://review.openstack.org/422684
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=a529033fdcb36ccea8cf0cc76339816ed31418c7
Submitter: Jenkins
Branch:    master"
1657727,2017-01-20 13:16:55 UTC,"Fix is here: https://review.openstack.org/#/q/I8f6bbf77d27f3d8976985241deb8a948984862f5,n,z"
1657727,2017-01-19 12:23:51 UTC,This bug is similar to https://bugs.launchpad.net/mos/+bug/1621541 but for other components
1657727,2017-01-21 20:08:41 UTC,"Reviewed:  https://review.openstack.org/422731
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=96e369880c441bdcf9ab30f196b4aabaafb9b921
Submitter: Jenkins
Branch:    stable/mitaka"
1657728,2017-01-19 12:37:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657728,2017-01-19 12:40:44 UTC,"same here 16.04 + snap session, but only if i snap the webbrowser app to left or right. if not snaped then the orientation is ok"
1657728,2017-01-19 12:42:11 UTC,https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1649276
1657731,2017-01-19 17:12:13 UTC,"Reviewed:  https://review.openstack.org/422589
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=4e4d96c16b9c7d55ec6c1ef7e9b561dcef456d6a
Submitter: Jenkins
Branch:    stable/mitaka"
1657731,2017-02-14 12:49:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433629"
1657731,2017-02-14 12:49:55 UTC,"Reviewed:  https://review.openstack.org/433629
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=00ccb73d2dd693a598b3e8d1ff3481d744a4b9be
Submitter: Jenkins
Branch:    master"
1657731,2017-02-14 12:51:20 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433630"
1657731,2017-02-14 12:53:56 UTC,"Reviewed:  https://review.openstack.org/433630
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=adf5a3c3fa0f83d7cd9ff1814a734e30296c2466
Submitter: Jenkins
Branch:    stable/newton"
1657731,2017-02-27 16:26:43 UTC,This issue was fixed in the openstack/fuel-main 11.0.0.0rc1 release candidate.
1657735,2017-01-19 12:57:31 UTC,So the example to get it working now is:
1657739,2017-01-19 15:12:30 UTC,"As I debug, openstack clients use admin network to communicate:"
1657739,2017-01-19 14:26:12 UTC,"Try run barmetal test use puplicURL OS_AUTH_URL=http://10.109.5.3:5000/v3/.
But when test is starting I got inetrnal admin url"
1657739,2017-01-19 15:28:34 UTC,I try to use console keystone client with next env vars (as in jenkins build):
1657739,2017-01-19 14:00:31 UTC,Does it repeatable with keystone v3?
1657739,2017-01-19 14:19:18 UTC,Yes
1657745,2017-04-18 07:25:07 UTC,Not reproduced at 1575 build; verified
1657745,2017-03-14 12:15:21 UTC,"Reviewed:  https://review.openstack.org/433084
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=89659ee6cbfbefbf76eed8ceab4e3d4cf165b487
Submitter: Jenkins
Branch:    master"
1657745,2017-03-14 11:59:23 UTC,"Reviewed:  https://review.openstack.org/433087
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=9a45cb0e11737e6d3c6d4deca58f39c9ff2c9c8d
Submitter: Jenkins
Branch:    stable/newton"
1657745,2017-02-13 14:31:10 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433087"
1657745,2017-02-13 14:30:04 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: master
Review: https://review.openstack.org/422614
Reason: https://review.openstack.org/#q,Ia39bcdb634ce9c4cd67ecbac44035c0fe7cd1517,n,z"
1657745,2017-02-13 14:28:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433084"
1657745,2017-02-13 14:30:50 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/422727
Reason: https://review.openstack.org/#q,Ia39bcdb634ce9c4cd67ecbac44035c0fe7cd1517,n,z"
1657745,2017-01-23 13:28:30 UTC,There is no described fail on snapshot #796 SWARM
1657745,2017-01-21 20:21:26 UTC,"Reviewed:  https://review.openstack.org/422726
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=78b5796a1298e6dc6ef762e7b590748730699006
Submitter: Jenkins
Branch:    stable/mitaka"
1657745,2017-01-19 16:16:10 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/422727"
1657745,2017-01-19 16:15:05 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/422726"
1657745,2017-01-19 13:26:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422614"
1657745,2017-01-23 13:28:53 UTC,https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.cgroup_ha/182
1657746,2017-01-20 14:53:21 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1657750,2017-01-31 11:57:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/427123"
1657750,2017-05-11 10:02:12 UTC,"Reviewed:  https://review.openstack.org/430174
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=a848384706cdf69e7241ef4f51c9e2534805f586
Submitter: Jenkins
Branch:    stable/mitaka"
1657750,2017-02-07 10:11:26 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/430174"
1657750,2017-02-07 10:11:05 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/430173"
1657750,2017-05-11 10:22:29 UTC,"Reviewed:  https://review.openstack.org/430173
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=dedeaa789c78f8f4a9282e87210468a90eb09b37
Submitter: Jenkins
Branch:    stable/newton"
1657750,2017-02-06 17:07:12 UTC,"Reviewed:  https://review.openstack.org/427123
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=6fde41c44af5ce785053fdf40eddad65a1a1bff4
Submitter: Jenkins
Branch:    master"
1657750,2017-01-26 22:11:47 UTC,dmesg from failed node
1657750,2017-01-23 15:25:58 UTC,Please also provide the following information for the problem node:
1657750,2017-01-23 16:49:31 UTC,"Unfortunately when bond fails rsyslog is not able to send logs to Fuel node anymore, so we can't find anything related to bond0 failure in the archive attached above. Logs from the failed node and the information I asked previously are needed to research this issue further."
1657750,2017-01-20 15:30:48 UTC,Workaround in action
1657750,2017-01-23 10:08:50 UTC,"Workaround is not workaround.
After
for i in eno1 eno2 enp3s0f0 enp3s0f1; do ifdown ${i}; for i in eno1 eno2 enp3s0f0 enp3s0f1; do ifup ${i}; done
and restart deployment  the node with workaround gone offline again"
1657750,2017-01-23 19:25:16 UTC,logs from failed node (Untitled (30:f0) - node-1990 - osscr01r12c31) available on  http://mos-scale-share.mirantis.com/var-log-node-bond-error.tar.gz
1657750,2017-01-23 16:38:38 UTC,"Have found /etc/interfaces.d/ifcfg-bond0 conig:
auto bond0
iface bond0 inet manual
bond-slaves eno1 eno2 enp3s0f0 enp3s0f1
bond-mode 802.3ad
bond-miimon 1000
bond-use-carrier 1
bond-lacp-rate fast
bond-updelay 30000
bond-downdelay 10000
bond-ad-select bandwidth
bond-xmit-hash-policy layer3+4"
1657750,2017-01-23 15:53:43 UTC,"Unfortunately we removed the env with repro, therefore can't provide you with /etc/astute.yaml"
1657751,2017-01-20 14:56:44 UTC,https://github.com/snapcore/snapd/pull/2674
1657764,2017-01-20 07:23:21 UTC,"Reviewed:  https://review.openstack.org/422674
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=b3e5d552287b7a1244cc7b6ab190a93adc69f6bf
Submitter: Jenkins
Branch:    stable/mitaka"
1657764,2017-01-20 14:48:37 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/423311"
1657764,2017-01-20 14:52:34 UTC,"Change abandoned by Vladimir Khlyunev (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/423311
Reason: https://review.openstack.org/423303"
1657764,2017-01-19 15:00:13 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/422674"
1657770,2017-01-19 15:22:55 UTC,It would also be useful if the charm defined some reasonable checks.
1657770,2018-01-31 22:58:43 UTC,"Moving this to the kibana-charm project, maintained by ~elasticsearch-charmers.  As of the latest kibana charm rev (-19), there are still no monitoring interfaces supported:"
1657772,2017-01-19 15:36:40 UTC,ceilometer-agent should get this information from ceilometer (its a bit of an anomaly in that behaviour).
1657774,2019-11-05 20:24:36 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/422696
Reason: This is in merge conflict and has been sitting with -1s for a long time. I'm not sure if it's still an issue and if it is, if this is still an OK fix, but it looks abandoned so I'm going to drop it."
1657774,2017-06-27 16:00:40 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'"
1657774,2017-03-17 15:14:43 UTC,"I hit the same issue on stable/ocata. The ""Neutron client was not able to generate a valid admin token, please verify Neutron admin credential located in nova.conf"" error is intended to be output, and HTTP 400 raised, when the session auth is using the neutron auth parameters from nova.conf. Unfortunately this code is also being hit in one case where the session auth only has a token rather than the admin auth parameters from conf, making it unable to re-authenticate. That case is when nova.network.neutronv2.api.get_client has admin=False, context.is_admin=True, and context.auth_token is set. In that case, admin auth is not used [1] but the ClientWrapper is told that an admin context was used [2]."
1657774,2017-03-03 11:29:04 UTC,example of a nasty traceback in n-cpu that I suspect is related to this bug
1657774,2017-01-19 15:28:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422696"
1657777,2018-03-11 10:22:19 UTC,"Porting was completed as far as I can see.
Documentation is quite poor and the API does not correspond to the latest status (https://developer.openstack.org/api-ref/database/). I think that bringing API and docs to the actual Trove status should be done as part of a separate Bug (I can take care of bug opening and implementation). Do you agree?"
1657779,2017-01-23 06:41:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423943"
1657779,2017-04-27 14:51:27 UTC,"Change abandoned by Brian Curtin (<email address hidden>) on branch: master
Review: https://review.openstack.org/423943
Reason: Hey, sorry I didn't see this change first, but I just fixed it in I95ab21c13bcdc24bf5daadf58f79d0f53c8bd75e"
1657779,2020-04-28 11:06:12 UTC,Already fixed
1657782,2017-08-07 06:06:50 UTC,Unable to allocate time to this
1657788,2017-01-19 15:58:43 UTC,"The error is worse when the mint is run in live usb / cd. When you change to the default terminal, some letters disappear from the cinnamon environment. Mainly vowels."
1657794,2017-01-19 16:10:40 UTC,YES PLEASE :)
1657794,2017-01-26 09:51:54 UTC,Thomas
1657794,2017-02-16 22:14:57 UTC,"The actual problem here is that there are duplicated links at all.  There usually shouldn't be, and this was a byproduct of having two versions there where there shouldn't have been.  I'm correcting this for 16.04 as we speak."
1657794,2017-10-03 16:41:16 UTC,"Adam,"
1657809,2017-01-20 09:28:53 UTC,Patch with fix is on review https://review.fuel-infra.org/#/c/29681/ .
1657825,2018-07-11 23:57:11 UTC,"Before enforcing this on some classic snaps, please fix https://forum.snapcraft.io/t/launchpad-post-build-pre-upload-testing/5545 first. For now I've taken Launchpad builds out of git-ubuntu's publication pipeline since we were hitting non-deterministic bad snap builds which, while detectable, cannot currently be blocked from publication by Launchpad since there currently exists no hook for Launchpad to be able to test produced snaps."
1657825,2017-10-06 18:02:24 UTC,"If I got it right, the constraint would be enforced only on certain ""classic"" apps and not on all of them. Correct? I just wonder if it would be possible to upload an image of a (partially) closed-source ""classic"" app into the store."
1657825,2017-06-15 15:47:34 UTC,Adding a snapstore task. Please adjust it or the software-center-agent task as necessary.
1657825,2017-01-19 18:30:51 UTC,"Note that we need to sort out https://bugs.launchpad.net/launchpad-buildd/+bug/1650946 before ""only LP builds for classic"" constraints can usefully be imposed, although I certainly have no objection to the constraint in principle."
1657825,2017-06-15 15:34:33 UTC,"To save people chasing the link, for the record, there are no remaining blockers to this from the LP side as far as I'm aware, since the bug above was closed in mid-February."
1657835,2017-01-20 12:19:00 UTC,Test was successful after ad-hook changing of timeout to 120 minutes. It can bee considered to increase it permanently.
1657835,2017-01-20 12:32:51 UTC,"I'm moving this to Fuel QA and raising Importance to High, since 8.0 patches are blocked sometimes by this issue. Fuel QA please assist here and give your permission to raise the timeout for the Infra team."
1657837,2017-05-01 16:55:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657837,2017-05-01 17:40:06 UTC,"Nope, it is still a problem in ""systemd 231-9ubuntu4 amd64"".  Actually, it seems like multiple features documented in the Ubuntu Manpages for systemd.network are not functioning.  Below are some error messages (journalctl -a -u systemd-networkd), followed by the configuration files."
1657837,2017-05-01 17:43:59 UTC,And the error messages pertinent to the issue with the VLAN are:
1657837,2017-05-03 10:54:56 UTC,"ahhhhh... never mind.  I was using the systemd netdev, link and network documentation for Ubuntu 17.04, when my system is on 16.10.  My apologies."
1657838,2019-09-17 07:53:37 UTC,"This is done, but we actually did it in britney. So what's happening is that britney now, whenever all tests are finished, will attempt to leave a comment whenever tests are regressing. So I guess we can make this Won't Fix right now."
1657841,2020-01-10 09:30:58 UTC,Which version were you exactly using? Can you still reproduce the problem with the latest version of QEMU?
1657841,2020-03-11 04:17:24 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1657845,2017-02-08 10:15:30 UTC,"Added more logs to autopilot-qt and there's something weird. The dbus registration is successfully completed but right after that a second attempt to load the library takes place and the registration to dbus can't be completed
https://pastebin.ubuntu.com/23953406/"
1657845,2017-02-08 13:10:14 UTC,"Taking a look at unity8 in the phone, where the introspection is actually working, u8 tries to load the library twice and the second attempt gets the registration error. I assumed that the object could not be registered because it was already registered. https://pastebin.ubuntu.com/23954187/"
1657845,2017-02-08 14:22:32 UTC,"So in both the phone and the snap, the libraries get loaded twice.  The first registration succeeds and the second fails."
1657845,2017-02-01 15:14:32 UTC,"OK, good call.  Try current edge store."
1657845,2017-02-08 21:15:36 UTC,I've just tested the autopilot-qt snap with the deb version of unity8 and I was able to introspect it. I think that rules autopilot-qt out of the equation.
1657845,2017-02-14 09:19:46 UTC,"It seems that unity8 is not registered to dbus in the snap version. While loged in the deb version I got this
gdbus introspect --session  --dest=com.canonical.Unity8 --object-path /com/canonical/Autopilot/Introspectionnode /com/canonical/Autopilot/Introspection {
  interface com.canonical.Autopilot.Introspection {
    methods:
      GetState(in  s piece,
               out a(sv) state);
      GetVersion(out s version);
    signals:
    properties:
  };"
1657845,2017-02-07 17:46:34 UTC,The testability libraries seemed to be loaded now and yet the introspection is not working. See the script attached
1657845,2017-02-08 15:00:24 UTC,And it get's even more confusing. Switching to the deb version of unity8 in Zesty also work and the log output is exactly the same as the snap version
1657845,2017-02-03 13:43:09 UTC,"much better, now the libraries are present in the testability folder but I can't still introspect unity8."
1657845,2017-02-01 00:40:40 UTC,"Hi Michael, I gave it a try and it is not working. The problem is that the path added to LD_LIBRARY_PATH does not seem to be ok."
1657845,2017-02-02 12:50:07 UTC,it does look better but I'm not able to start a unity8 session. it seems that it's broken: https://launchpad.net/bugs/1661216
1657845,2017-02-16 13:52:30 UTC,ok. fixes for unity8 and unity8-session-snap are relased (the LD_LIBRARY_PATH and testability interface stuff).
1657845,2017-02-01 00:53:53 UTC,"fyi, here's a great explanation about how this is supposed to work: http://askubuntu.com/questions/841004/cannot-get-basic-content-interface-example-working-with-snapcraft"
1657845,2017-02-14 19:41:36 UTC,Agreed.  I see similar (using desktop u8 snap).  Looking into it...
1657845,2017-01-31 23:39:11 UTC,"The current edge store snap should be setting LD_LIBRARY_PATH (correctly, I hope).  I had a hard time telling if the content interface mount was working as expected, so please let me know if it works as expected."
1657845,2017-01-31 19:01:23 UTC,"Hi Michael, $SNAP/testability/ should be added to LD_LIBRARY_PATH. QT loads the testability libraries if either the -testability command line argument is passed to QCoreApplication, or if the
QT_LOAD_TESTABILITY environment variable is set"
1657845,2017-01-31 18:39:44 UTC,"OK, I've kicked off a snap build/upload for unity8 that adds a plug for this.  But I'm not sure what the expectation is for actually using the content interface."
1657845,2017-02-02 20:52:39 UTC,Should be better now.
1657845,2017-02-16 13:40:59 UTC,"using the autopilot-qt snap from the store, it doesn't work for me, because that snap is missing libqttestability.so."
1657867,2017-01-23 13:28:07 UTC,"The thing is if the logrotate rotates the log file with mysql:adm, it should be the same with default file created in this directory. Especially if we want to use the concept of the group adm in the directory /var/log/mysql for giving privileges to read log files.."
1657867,2017-01-23 10:29:39 UTC,"Looking at the Vcs git that is listed I see that the change came in with Debians 5.6.14+dfsg-1.
(https://anonscm.debian.org/git/pkg-mysql/mysql.git)
That means the individual fix is in the past and can't be found in that repo."
1657867,2017-01-23 13:31:07 UTC,"Without the change message (which was before my time), this just looks like an oversight to me. If we can't find out why this was done, my suggestion is just changing it back."
1657867,2017-01-23 10:20:02 UTC,"Hi,
thank you for your report and your help to make Ubuntu better."
1657872,2017-01-19 19:41:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/422838"
1657872,2017-01-23 14:32:02 UTC,"Change abandoned by Jay Pipes (<email address hidden>) on branch: master
Review: https://review.openstack.org/422838
Reason: Dims took over this effort..."
1657872,2017-04-07 01:45:50 UTC,this has been addressed by https://review.openstack.org/#/c/423718/
1657880,2018-10-24 12:25:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657883,2017-01-19 20:48:27 UTC,Got this error when attempting to login at this event - http://loco.ubuntu.com/events/ubuntu-us-or/3498-salem-ubuntu-hour/
1657897,2017-08-28 14:45:23 UTC,I think we should defer to upstream on this one.
1657897,2017-08-28 14:41:28 UTC,Upstream issue: https://github.com/cyrusimap/cyrus-sasl/issues/346
1657897,2017-01-25 20:51:58 UTC,Yes that is the correct issue occurring effectively pam never sees the rhost data from sendmail which can be seen in the auth log.
1657897,2017-08-28 14:41:19 UTC,Is this log line enough for fail2ban purposes?
1657897,2017-01-23 19:25:20 UTC,"Hi, Thanks for the reply."
1657897,2017-01-23 10:47:44 UTC,"Hi James,
thank your for your report and your help to make Ubuntu better.
These are essentially two issues in one."
1657897,2017-01-25 16:59:43 UTC,"@James, big thanks for the information I think your clarity about the logging of the rhost and the redhat bug helped a bit."
1657902,2017-01-19 23:14:44 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1657902,2018-03-19 21:20:51 UTC,"This is still reproducible with build Bionic 18.04 20180319, slideshow content not totally translated."
1657902,2019-01-02 12:53:32 UTC,"The bug also reproduces in Polish language. Two slides are not fully translated at step 15.
I also checked German to comparison and everything seems fine there."
1657903,2017-01-19 22:35:19 UTC,Screenshot of error window.
1657904,2017-01-22 13:47:11 UTC,See my last response.
1657904,2017-01-22 01:56:16 UTC,"I vaguely recall that this was deliberate to simplify reviewing (no need
to read the same data twice), but I'm not a 100% sure. The relevant code
can be rtaced starting from the __call__() method at line 518 in
metadata/diff.py"
1657904,2017-01-22 02:03:09 UTC,"Yes, it is deliberate, see line 45 onwards in metadata/sources/worker.py"
1657904,2017-01-22 02:04:30 UTC,"And note that it is explicitly undone when doing bulk downloads for the
title and author fields at line 227 in actions/edit_metadata.py --
probably the sa,e could be done for the other fields, although I am
50-50 on whether that is a good idea or not."
1657904,2017-01-22 07:15:37 UTC,"Thank you for your response. What is the ""extra work"" in set_metadata that this optimisation is preventing? Is it just the necessity of checking that the fields have changed and not reapplying identical metadata values in all the set_metadata functions for all the different formats?"
1657907,2017-01-22 03:43:51 UTC,apport information
1657907,2017-01-22 03:43:53 UTC,apport information
1657907,2017-01-22 03:43:45 UTC,apport information
1657907,2017-01-22 13:55:38 UTC,apport information
1657907,2017-01-22 13:55:35 UTC,apport information
1657907,2017-01-22 03:43:42 UTC,apport information
1657907,2017-01-22 03:43:26 UTC,apport information
1657907,2017-01-22 03:43:37 UTC,apport information
1657907,2017-01-22 03:43:35 UTC,apport information
1657907,2017-01-22 03:43:34 UTC,apport information
1657907,2017-01-22 03:43:31 UTC,apport information
1657907,2017-01-22 03:43:29 UTC,apport information
1657907,2017-01-22 13:55:52 UTC,apport information
1657907,2017-01-22 03:43:39 UTC,apport information
1657907,2017-01-22 13:55:55 UTC,apport information
1657907,2017-01-29 01:48:05 UTC,"[ 1373.065220] ath10k_pci 0000:3a:00.0: firmware crashed! (uuid acddb2e9-75f5-4d34-a585-9ea43745955a)
[ 1373.065260] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[ 1373.065270] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 1373.067262] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[ 1373.068193] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7
[ 1373.068215] ath10k_pci 0000:3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 1373.070246] ath10k_pci 0000:3a:00.0: firmware register dump:
[ 1373.070273] ath10k_pci 0000:3a:00.0: [00]: 0x05030000 0x000015B3 0x009860FA 0x00955B31
[ 1373.070286] ath10k_pci 0000:3a:00.0: [04]: 0x009860FA 0x00060730 0x00000004 0x0040E8A0
[ 1373.070297] ath10k_pci 0000:3a:00.0: [08]: 0x00498110 0x00955A00 0x0000000B 0x00400000
[ 1373.070308] ath10k_pci 0000:3a:00.0: [12]: 0x00000009 0x00000000 0x00952CD0 0x00952CE6
[ 1373.070320] ath10k_pci 0000:3a:00.0: [16]: 0x00952CC4 0x00910712 0x00000000 0x0091080D
[ 1373.070331] ath10k_pci 0000:3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x00000000 0x0041E0DC
[ 1373.070347] ath10k_pci 0000:3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000FFFFF 0xC09860FA
[ 1373.070358] ath10k_pci 0000:3a:00.0: [28]: 0x809B3230 0x0040E948 0x00000018 0x004313B8
[ 1373.070368] ath10k_pci 0000:3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9C0 0x00429548
[ 1373.070379] ath10k_pci 0000:3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x00000000 0x00000002
[ 1373.070390] ath10k_pci 0000:3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10
[ 1373.070400] ath10k_pci 0000:3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x00000001
[ 1373.070411] ath10k_pci 0000:3a:00.0: [48]: 0x80911210 0x0040EAD8 0x00000010 0x004041D0
[ 1373.070422] ath10k_pci 0000:3a:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[ 1373.070432] ath10k_pci 0000:3a:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[ 1373.181969] ieee80211 phy0: Hardware restart was requested
[ 1375.509337] ath10k_pci 0000:3a:00.0: failed to set coverage class: expected slot time of 9 or 20us in HW register. It is 0us."
1657907,2017-01-22 13:56:10 UTC,apport information
1657907,2017-01-22 03:43:12 UTC,apport information
1657907,2017-01-29 01:47:57 UTC,"Unfortunately, the new kernel did not bring any improvements."
1657907,2017-01-25 23:33:21 UTC,"Hello Joseph, thanks for looking into this. I've downloaded the .deb files, removed all virtualbox packages, and installed the .deb files. I'll test for a few days and let you know my findings."
1657907,2017-01-23 17:57:19 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1657907,2017-01-22 16:50:17 UTC,"I see, some of my logs came through ;)"
1657907,2017-01-22 13:56:50 UTC,apport information
1657907,2017-01-22 13:56:05 UTC,apport information
1657907,2017-01-22 13:56:45 UTC,apport information
1657907,2017-01-22 13:56:35 UTC,apport information
1657907,2017-01-22 13:56:26 UTC,apport information
1657907,2017-01-22 13:56:22 UTC,apport information
1657907,2017-01-22 13:56:20 UTC,apport information
1657907,2017-01-22 13:56:17 UTC,apport information
1657907,2017-01-22 13:56:14 UTC,apport information
1657907,2017-01-22 13:56:37 UTC,apport information
1657907,2017-01-22 03:43:07 UTC,apport information
1657907,2017-01-22 03:42:54 UTC,apport information
1657907,2017-01-22 03:17:12 UTC,apport information
1657907,2017-01-22 03:42:57 UTC,apport information
1657907,2017-01-19 23:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1657907,2017-01-22 03:16:52 UTC,apport information
1657907,2017-01-22 03:16:53 UTC,apport information
1657907,2017-01-22 03:16:55 UTC,apport information
1657907,2017-01-22 03:16:56 UTC,apport information
1657907,2017-01-22 03:16:59 UTC,apport information
1657907,2017-01-22 03:17:00 UTC,apport information
1657907,2017-01-22 03:17:02 UTC,apport information
1657907,2017-01-22 03:17:06 UTC,apport information
1657907,2017-01-22 03:17:08 UTC,apport information
1657907,2017-01-22 03:17:10 UTC,apport information
1657907,2017-01-22 03:17:16 UTC,apport information
1657907,2017-01-22 03:17:25 UTC,apport information
1657907,2017-01-22 03:17:28 UTC,apport information
1657907,2017-01-22 03:17:18 UTC,apport information
1657907,2017-01-22 03:28:39 UTC,apport information
1657907,2017-01-22 03:29:02 UTC,apport information
1657907,2017-01-22 03:28:59 UTC,apport information
1657907,2017-01-22 03:28:57 UTC,apport information
1657907,2017-01-22 03:28:55 UTC,apport information
1657907,2017-01-22 03:28:54 UTC,apport information
1657907,2017-01-22 03:28:53 UTC,apport information
1657907,2017-01-22 03:28:37 UTC,apport information
1657907,2017-01-22 03:28:51 UTC,apport information
1657907,2017-01-22 03:28:48 UTC,apport information
1657907,2017-01-22 03:28:46 UTC,apport information
1657907,2017-01-22 03:28:44 UTC,apport information
1657907,2017-01-22 03:28:42 UTC,apport information
1657907,2017-01-22 03:28:40 UTC,apport information
1657907,2017-01-22 03:28:49 UTC,apport information
1657910,2017-05-18 05:39:24 UTC,"Take a look at this, but query on '_index' field doesn't play well with alias, so I'm afraid we could not replace indices query right now. Someone has reported this bug to ES community already, see https://github.com/elastic/elasticsearch/issues/23306"
1657915,2017-05-03 15:10:05 UTC,"How much is anyone likely to care? I know this is currently in the design, but perhaps we should re-validate if it makes sense."
1657922,2017-01-20 00:20:54 UTC,Reinstalled the application and now the .desktop file is missing.
1657926,2018-01-24 22:34:18 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1410
1657926,2017-04-06 23:51:30 UTC,Thank you for the report.
1657926,2017-01-20 20:03:33 UTC,"I'm not sure printf is really needed on 6074 (_print_failures), seems to me print should be enough, and I don't get the error if print is used."
1657926,2017-01-20 00:27:27 UTC,"The line breaks did not come through in the paste, but there are line breaks and spaces before each % here:
'http://google.com/6.571073E-3223 %AF0.000000E+003 %AD2.293852E-3173 %830.000000E+003 %AF\',1,2)""]'"
1657937,2017-01-23 03:55:36 UTC,Also it looks like we use GL_NEAREST instead of GL_LINEAR for texturing the shadow. I vaguely recall I left it that way for performance in years gone by. Still should be fine to use GL_NEAREST providing the shadow texture itself is at least 2x the resolution needed for scale 1.0.
1657939,2017-01-20 06:24:32 UTC,"Ok, thanks for your clarifications."
1657939,2017-01-20 03:35:40 UTC,"Gunnar, it references the Ubuntu guide for creating self-signed certificates:"
1657939,2020-04-04 00:27:32 UTC,"I've added the suggested command as an example, and copyedited a bit to clarify use of default vs. custom certificates."
1657939,2017-01-20 02:22:19 UTC,"I just looked at <https://help.ubuntu.com/lts/serverguide/dovecot-server.html>, but can't see that it claims that Dovecot creates the certificates. Rather it provides the ""Certificates"" link to a page where certificate creation is explained."
1657948,2017-10-12 20:32:21 UTC,Continues to affect Aodh driver.
1657952,2017-01-20 10:21:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1657952,2019-05-24 11:07:39 UTC,this works fine now since bionic at least
1657957,2017-01-20 04:02:17 UTC,"Hi, I just update my Mint 18 and the icons work fine."
1657959,2017-02-04 01:00:11 UTC,"I have tested again, the command ""openstack appcontainer show"" has supported these formatters.
BTW ""zun show"" doesn't."
1657959,2017-01-20 07:13:51 UTC,class ShowContainer(command.ShowOne):
1657959,2017-01-28 17:30:40 UTC,"@Fend,"
1657959,2017-03-25 17:34:18 UTC,Fixed by: https://review.openstack.org/#/c/435293/
1657961,2017-12-27 22:21:21 UTC,I have encountered the same (or similar) problem here.
1657961,2017-03-20 22:54:22 UTC,"You can reset the menu by deleting the configuration file of this, although the error causes menulibre"
1657965,2018-09-19 14:12:07 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/373
1657967,2017-01-20 05:23:51 UTC,"what version of OSC are you using for Newton? We had late fixes go in, I believe the recommended version is 3.2.1"
1657967,2017-01-20 05:51:25 UTC,"Upgraded OSC to 3.7.0 and the OSC problem is gone.  Now I could execute the endpoint list and realize that the other reported issue with tacker client and the double colon was my fault.
Will update the bug details to avoid confusions.
Thanks!"
1657967,2017-02-02 18:40:58 UTC,So what issue remains with OSC?
1657967,2017-02-03 06:10:28 UTC,"After upgrading to 3.7.0, bug is solved and no issue remains.
Thanks!"
1657969,2017-01-31 07:16:11 UTC,Are there any filesystems that allow non-ASCII in path names and do not use UTF-8? I'd be surprised if there are.
1657969,2017-01-31 05:57:21 UTC,It looks like bzrlib doesn't handle file names containing non-ASCII characters.
1657969,2017-01-31 07:02:57 UTC,"Hmm, by setting LANG to utf8 you're telling bzr how to interpret the pathname which otherwise cannot be decoded so I can't see what bzr can do there"
1657969,2017-01-31 08:10:57 UTC,"> Are there any filesystems that allow non-ASCII in path names and do not use UTF-8? I'd be surprised if there are.
"
1657969,2017-01-31 08:36:16 UTC,"Yes, OK, I take your point. What this says though is that, unless bzrlib is called with a UTF-8 locale, it won't work. Shouldn't the methods in berlin that manipulate the filesystem specify the UTF-8 locale as a matter of course?"
1657969,2017-01-31 09:26:33 UTC,"In python3 yes, finally !"
1657969,2017-01-31 10:22:14 UTC,"On Tue, Jan 31, 2017 at 07:16:11AM -0000, Michi Henning wrote:

> Are there any filesystems that allow non-ASCII in path names and do not
> use UTF-8? I'd be surprised if there are.
"
1657976,2019-05-12 01:22:48 UTC,"I don't think I would have explicitly select the OTF version---if it was being used, it was being done behind the scenes. But I'm not seeing this issue on 18.04.2. Feel free to close if it's otherwise justified."
1657976,2017-01-20 06:00:20 UTC,"On closer inspection, it looks like all characters except for the 'u' are displayed *too large,* rather than the 'u' being too small. Zoom in on the picture and count the number of pixels for confirmation."
1657976,2019-05-09 20:11:38 UTC,"The report is against the version fonts-hack released with Xenial. Bionic and later include a new major version of the font, and ship only the TrueType files (my bet is that you were using the OTF version, which often renders worse on screen)."
1657994,2017-03-18 09:40:40 UTC,"I had been trying to cherry-pick patches from the working Xenial kernel to mainline, and got bogged down with build issues.  Back to the bisection:"
1657994,2017-02-15 07:10:24 UTC,"I would like to add some information to this bug report, which may or may not be relevant.
There seems to be a general problem with HDMI audio in recent kernel versions.
I am using Debian kernel packages, on an AMD64 system with a Radeon R9-280 video card:"
1657994,2017-03-23 05:46:18 UTC,Do you have any alsa/pulseaudio config?
1657994,2017-01-26 21:16:03 UTC,Both kernels behave like any of the kernels from 4.5:  no sound on HDMI.
1657994,2017-05-23 04:17:34 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1657994,2017-09-20 13:48:19 UTC,"The bug has been fixed with this commit upstream drm-tip repository (with cc to stable):
https://cgit.freedesktop.org/drm-tip/commit/?id=d81fb7fd9436e81fda67e5bc8ed0713aa28d3db2"
1657994,2017-02-02 22:11:29 UTC,We are bisecting between those two kernel versions to identify the commit that introduced this regression.  Some of the test kernels I post will be bad and some will be good.  At the end of the testing the bisect will point to one particular commit.
1657994,2017-05-23 04:17:32 UTC,[Expired for linux (Ubuntu Yakkety) because there has been no activity for 60 days.]
1657994,2017-02-01 05:56:07 UTC,"For this kernel, no audio.  Failure mode is like 4.4 mainline."
1657994,2017-01-20 07:30:12 UTC,This change was made by a bot.
1657994,2017-01-31 20:02:10 UTC,"Yes, 4.4.0-21 is good, just like 4.4.0-59."
1657994,2017-01-31 18:52:31 UTC,"Can you test the 4.4.0-21 kernel next:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168"
1657994,2017-01-31 21:11:20 UTC,I started a kernel bisect between 4.4 final and v4.5-rc1. The kernel bisect will require testing of about 7-10 test kernels.
1657994,2017-01-25 16:35:31 UTC,Can you test the following two early Yakkety kernels:
1657994,2017-01-24 20:07:23 UTC,Kernel behavior summary:
1657994,2017-01-23 17:55:44 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
1657994,2017-01-23 17:50:47 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1658010,2017-01-20 13:26:13 UTC,"magnum master supports fedora-24(has some bug: https://bugzilla.redhat.com/show_bug.cgi?id=1320601) image with some changes in master:-
https://review.openstack.org/#/c/404789"
1658010,2017-05-25 15:30:19 UTC,Newton is update to use fedora 25 we can close this.
1658016,2017-03-11 19:06:16 UTC,Now it works for me too. Thanks!
1658016,2017-02-23 03:55:26 UTC,FYI - these updates arrived today -
1658016,2017-02-17 13:22:47 UTC,Thank you for the workaround. It is definitely more convenient than executing sudo modprobe iwlwifi from the command line after every resume!
1658016,2017-02-17 12:10:46 UTC,"I can confirm the same behaviour
$ uname -a
Linux E7470 4.8.0-36-generic #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1658016,2017-01-23 17:49:00 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1658016,2017-01-20 09:31:02 UTC,This change was made by a bot.
1658016,2017-01-24 13:14:45 UTC,"Just tried the mainstream kernel ""4.10.0-041000rc5-lowlatency"" as mentioned above and I do confirm the very same problem exists there too."
1658025,2017-02-08 10:20:40 UTC,"Reviewed:  https://review.openstack.org/430693
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=4845573f7b24be17a81f19019b441ba0e11646d8
Submitter: Jenkins
Branch:    stable/newton"
1658025,2017-01-20 09:48:59 UTC,Priority decreased to Low because no functionality is broken. User can see a part of a node name and role list isn't hidden.
1658025,2017-02-08 07:09:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430598"
1658025,2017-02-08 09:53:03 UTC,"Reviewed:  https://review.openstack.org/430598
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=f1d21aaac8054cbc8b4c3da8dd22b6b2c54b19b8
Submitter: Jenkins
Branch:    master"
1658025,2017-02-08 09:54:51 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430693"
1658025,2017-02-10 11:53:36 UTC,Verified on Fuel 10 #1338
1658025,2017-02-27 16:27:24 UTC,This issue was fixed in the openstack/fuel-ui 11.0.0.0rc1 release candidate.
1658036,2017-01-24 05:46:17 UTC,"It's trying to identifying possible fuzzing areas in URL right ?
I am attaching the conf and template file."
1658036,2017-01-24 05:46:15 UTC,"It's trying to identifying possible fuzzing areas in URL right ?
I am attaching the conf and template file."
1658036,2017-01-24 05:50:40 UTC,I am using Kali-linux on VM-ware i.e 4.3.0-kali1-amd64.
1658036,2017-01-23 07:30:25 UTC,The regex here i.e:{([\w]*):?([^}]*)}  is expecting URL in {}. That's why it is not working. To make it work for URL do remove {} from regex.
1658036,2017-01-23 22:01:06 UTC,"Anubhav,"
1658036,2017-04-10 05:40:10 UTC,Are you still facing this issue?
1658038,2017-01-20 10:20:20 UTC,"this is a screenshot of the popup. manipulating the file further, the process usually leads to inkscape crash..."
1658038,2017-01-20 10:24:20 UTC,hint: the example file was created by a pdf import...
1658042,2017-02-17 18:14:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658049,2017-01-20 13:27:12 UTC,"magnum master supports fedora-24 image with some changes in master:-
https://review.openstack.org/#/c/405235/"
1658049,2017-01-22 11:42:44 UTC,This bug is fixed for Ocata.
1658050,2017-03-04 02:39:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658057,2017-04-19 05:39:49 UTC,Again:
1658057,2017-02-27 07:21:40 UTC,Again:
1658057,2017-03-01 11:30:07 UTC,Again:
1658057,2017-03-16 05:18:58 UTC,Again:
1658057,2017-03-24 11:59:40 UTC,"https://mir-jenkins.ubuntu.com/job/device-runtests-mir-testflinger/device_type=krillin,slave_type=manager/82/consoleFull"
1658057,2017-11-03 16:35:56 UTC,Syncing task from Mir.
1658057,2017-12-06 14:48:57 UTC,This is an irrelevant scenario: running performance tests on contended CI infrastructure that we no longer support.
1658063,2017-02-10 13:19:34 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/432298"
1658063,2017-02-10 13:19:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432299"
1658063,2017-04-25 12:21:17 UTC,"Change abandoned by Vladimir Kuklin (<email address hidden>) on branch: master
Review: https://review.openstack.org/432299"
1658063,2017-01-21 11:36:52 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/423616"
1658063,2017-04-25 12:22:23 UTC,"Change abandoned by Vladimir Kuklin (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/423622"
1658063,2017-01-21 16:46:54 UTC,"Reviewed: https://review.fuel-infra.org/30020
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1658063,2017-04-25 12:21:22 UTC,"Change abandoned by Vladimir Kuklin (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/432298"
1658063,2017-01-21 16:43:52 UTC,"Related fix proposed to branch: master
Change author: Vladimir Kuklin <email address hidden>
Review: https://review.fuel-infra.org/30020"
1658063,2017-01-20 17:13:31 UTC,Raised to Critical due to blocked CI on stable/mitaka branch
1658063,2017-01-21 12:29:27 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/423622"
1658063,2017-01-20 17:46:58 UTC,"1.  https://review.fuel-infra.org/30004  is is not a fix its workaround.
2. its works for master branch , for stable branch was implemented another workaround https://review.fuel-infra.org/#/c/30016/"
1658063,2017-01-20 17:15:10 UTC,Looks like fix https://review.fuel-infra.org/30004 doesn't work.
1658063,2017-01-20 17:04:25 UTC,"here is another set of jobs which actually have a workaround above merged already, although packages are not updated"
1658063,2017-01-20 11:52:08 UTC,"Reviewed: https://review.fuel-infra.org/30004
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1658063,2017-01-21 13:16:19 UTC,"Reviewed:  https://review.openstack.org/423616
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=d600a302c63b8c9de2b9945a4469abaea2a01ec1
Submitter: Jenkins
Branch:    stable/mitaka"
1658070,2017-06-15 13:08:51 UTC,"Reviewed: https://review.fuel-infra.org/35612
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1658070,2017-06-13 14:43:04 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Denis V. Meltsaykin <email address hidden>
Review: https://review.fuel-infra.org/35612"
1658070,2017-06-12 10:50:42 UTC,"Reviewed:  https://review.openstack.org/468219
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e221784560c71eeab7c5eeeb42e7c6e910d29340
Submitter: Jenkins
Branch:    stable/ocata"
1658070,2017-05-26 16:32:05 UTC,"Reviewed:  https://review.openstack.org/466143
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a2b0824aca5cb4a2ae579f625327c51ed0414d35
Submitter: Jenkins
Branch:    master"
1658070,2017-05-30 13:48:20 UTC,sla1 for 9.0-updates
1658070,2017-05-30 13:48:06 UTC,"A customer has hit the same issue in MOS 9.2
Could you please backport the fix for Mitaka series?"
1658070,2017-06-19 12:45:44 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1658070,2017-06-08 21:51:54 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1658070,2017-06-26 11:12:21 UTC,After applying https://review.fuel-infra.org/#/c/35612/6/ the issue still persists in Mitaka.
1658070,2017-05-26 01:14:46 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/468227"
1658070,2017-06-27 10:40:13 UTC,"Can't reproduce bug on our test environment due to lack of appropriate HW. As I understand, fix was verified, so I move bug to ""Fix released""."
1658070,2017-07-06 17:40:31 UTC,"Reviewed:  https://review.openstack.org/468227
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0f2d87416eff1e96c0fbf0f4b08bf6b6b22246d5
Submitter: Jenkins
Branch:    stable/newton"
1658070,2017-08-28 09:55:25 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1658070,2017-08-30 16:48:19 UTC,"Fix proposed to branch: mcp/1.0/mitaka
Change author: Guang Yee <email address hidden>
Review: https://review.fuel-infra.org/36367"
1658070,2017-08-30 18:37:33 UTC,"Change abandoned by Vladyslav Drok <email address hidden> on branch: mcp/1.0/mitaka
Review: https://review.fuel-infra.org/36367"
1658070,2017-08-31 17:38:27 UTC,"Change restored by Vladyslav Drok <email address hidden> on branch: mcp/1.0/mitaka
Review: https://review.fuel-infra.org/36367"
1658070,2017-09-01 08:26:40 UTC,"Reviewed: https://review.fuel-infra.org/36367
Submitter: Pkgs Jenkins <email address hidden>
Branch: mcp/1.0/mitaka"
1658070,2017-05-26 00:25:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/468219"
1658070,2017-06-27 09:37:59 UTC,"Please disregard the previous comment - I misunderstood the verification status.
The patch has resolved the issue related to evacuation.
Therefore, I'm setting the status back to ""Fix Committed"""
1658070,2017-05-25 20:40:08 UTC,I agree with Guang Yee; via code inspection in the compute manager's rebuild method there is an obvious issue with not doing a rebuild claim during evacuate in certain cases.
1658070,2017-05-17 18:38:58 UTC,Ah gyee pointed out in IRC that if you're using microversion<2.29 then force is passed to the compute API code as None:
1658070,2017-05-19 01:56:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466143"
1658070,2017-01-20 12:31:45 UTC,"Kristina, could you please attach a diagnostic snapshot or at the very least nova-compute logs?"
1658070,2017-01-20 13:01:59 UTC,"The message for error vm:
Port update failed for port cfc947be-1975-42f3-95bd-f261a2eccec0: Unable to correlate PCI slot 0000:81:11.7"
1658070,2017-05-17 00:59:18 UTC,I guess this would be Mitaka?
1658070,2017-05-17 01:03:51 UTC,Could this be related to bug https://bugs.launchpad.net/nova/+bug/1512880 which was fixed in nova in newton?
1658070,2017-05-17 01:06:57 UTC,"It could be that when you're specifying a host and bypassing the scheduler, the target host isn't actually setup properly for the migration (evacuation to the target host) and when you don't specify the host, the scheduler is picking a proper host based on the filters."
1658070,2017-05-17 18:25:17 UTC,"(12:43:57 PM) gyee_: I am curious why we are using NopClaim if host is specified https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2771
(12:44:22 PM) gyee_: does specifying a host implies force evacuate?
(12:49:08 PM) gyee_: meanwhile if SR-IOV is enabled, we are trying to get the PCI mapping via the migration context, which is only populated at rebuild_claim. https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L2462
(12:51:32 PM) mriedem: https://github.com/openstack/nova/commit/dc0221d7240326a2d1b467e2a367bebb7e764e61 added that code in the compute manager about the nop claim, which implies resources were already claimed, but i'd have to dig into that"
1658070,2017-05-17 18:28:39 UTC,The force evacuate to target host change in the API was added in the 2.29 microversion which goes back to newton:
1658070,2017-05-17 18:35:58 UTC,"I'm not totally sure how this happens if the --force option isn't specified with the nova evacuate command, because of this code in the API:"
1658070,2017-05-17 00:58:20 UTC,Which release of nova is this?
1658070,2017-05-17 18:43:37 UTC,The regression was introduced in Newton:
1658070,2017-05-18 06:32:19 UTC,Eli Qiao (taget-9) is looking into this and will push a fix. Assigning to him.
1658070,2017-05-18 17:54:08 UTC,"Eli Qiao, will you be pushing a patch anytime soon? Otherwise, I can handle it. Please let me known."
1658070,2017-05-19 00:58:09 UTC,"@guang-yee, I'v submited the patch already https://review.openstack.org/#/c/465895/
not sure why launch pad doens't link it here."
1658070,2017-05-19 01:28:19 UTC,"The original poster's version of Nova was 13.1.2, which is Mitaka. Therefore all the --force stuff and microversions discussion is irrelevant (since microversion 2.29 was added in Newton)."
1658070,2017-05-19 01:31:45 UTC,"Jay, see comment 7, I think there is also a problem here with evacuate when a host is specified:"
1658070,2017-05-19 01:32:50 UTC,"Change abandoned by Eli Qiao (<email address hidden>) on branch: master
Review: https://review.openstack.org/465895
Reason: Please the comments of the bug which is made by Jay"
1658070,2017-05-25 20:10:12 UTC,I don't understand why this bug is marked as a duplicate of bug 1512880. Evacuation still failed when SR-IOV is enabled and host is specified. I tested my patch on the nodes with SR-IOV enabled and it seem to work fine.
1658071,2017-02-27 16:22:27 UTC,This issue was fixed in the openstack/fuel-qa 11.0.0.0rc1 release candidate.
1658071,2017-02-03 10:14:12 UTC,"Reviewed:  https://review.openstack.org/425595
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=f18e8191451ca2eef38d48554045b0e2c56c423b
Submitter: Jenkins
Branch:    stable/mitaka"
1658071,2017-02-03 10:08:55 UTC,"Reviewed:  https://review.openstack.org/425705
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=a9078b29be0af0a270ed967f932ee24675556e42
Submitter: Jenkins
Branch:    stable/newton"
1658071,2017-02-03 10:07:24 UTC,"Reviewed:  https://review.openstack.org/428644
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=c6a1f7a29d4a083b63d0e6ce5a273de0fd04c923
Submitter: Jenkins
Branch:    master"
1658071,2017-02-03 08:58:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/428644"
1658071,2017-01-24 12:54:00 UTC,"The reason is:
https://github.com/openstack/fuel-qa/blob/stable/mitaka/fuelweb_test/models/fuel_web_client.py#L3100-L3103"
1658071,2017-01-26 09:31:28 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/425595"
1658071,2017-01-24 09:41:26 UTC,"QA, seems you are running commands from the wrong place:"
1658071,2017-01-20 12:07:12 UTC,https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.add_updated_node_to_environment/93/console
1658071,2017-01-26 13:54:42 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/425705"
1658079,2017-03-20 09:43:41 UTC,fixed by https://blueprints.launchpad.net/fuel/+spec/graph-concept-extension
1658091,2017-02-20 07:42:07 UTC,This bug was fixed in the package linux - 4.4.0-63.84
1658091,2017-02-02 19:48:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658112,2017-01-21 00:26:15 UTC,Confirmed.
1658118,2017-01-21 00:27:36 UTC,Confirmed.
1658118,2017-01-21 00:27:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658119,2017-03-15 18:29:14 UTC,https://github.com/Juniper/contrail-ansible/pull/398
1658119,2017-03-15 18:29:45 UTC,Fixed in PR https://github.com/Juniper/contrail-ansible/pull/398
1658125,2017-01-21 03:52:43 UTC,"This is not a problem with elementary OS itself, but with google. Google has a gmail policy that requires all programs to have a super special license in order to access google accounts. An insecure app just means that it can access a google account only through the username and password. Pantheon mail should be secure enough, and as long as you have a good password, you should be ok. You can allow access to ""unsecure"" apps through here: https://support.google.com/accounts/answer/6010255?"
1658125,2017-01-21 07:02:24 UTC,"for end user, this is a problem with the default app shipped with the os and not with google.
thus kindly check if anything can be done to make mail app more secure.
for end users (target audience of this os), fact remains that mail app does not work. it cannot be expected that they do changes in google settings, or decrease the security just to enable access to mail app."
1658125,2017-01-21 07:04:19 UTC,"""thus kindly check if anything can be done to make mail app more secure."" by this, i mean work with google to allow mail app direct access."
1658125,2017-01-27 10:36:38 UTC,please check the below article which i read just now..
1658125,2017-02-07 15:41:15 UTC,Check this loki review.
1658126,2017-03-29 13:24:16 UTC,Might be related https://bugs.launchpad.net/fuel/+bug/1587310
1658126,2017-03-29 11:14:40 UTC,"Ping is successful for latest F10 iso, therefore mark it as incomplete for newton."
1658127,2017-02-02 10:46:36 UTC,Seems to be the same problem on Trusty as well.
1658127,2017-02-02 15:28:25 UTC,"Same on trusty, I had to temporarly patch the failing postinst scripts in /var/lib/dpkg/info/ to just return to get it installed."
1658127,2017-02-02 15:37:23 UTC,Davide: Mind including a diff identifying what you changed?
1658127,2017-02-16 17:22:19 UTC,"I inserted a 'return' at the beginning of the following postinst scripts, but I didn't have time to check why they fail:
/var/lib/dpkg/info/libnginx-mod-http-image-filter.postinst
/var/lib/dpkg/info/libnginx-mod-http-subs-filter.postinst
/var/lib/dpkg/info/libnginx-mod-http-upstream-fair.postinst
/var/lib/dpkg/info/libnginx-mod-http-xslt-filter.postinst
/var/lib/dpkg/info/libnginx-mod-mail.postinst
/var/lib/dpkg/info/libnginx-mod-stream.postinst"
1658136,2019-10-10 11:42:16 UTC,"Thank you for taking the time to report this bug. Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete."
1658136,2019-12-10 04:17:22 UTC,[Expired for sssd (Ubuntu) because there has been no activity for 60 days.]
1658136,2019-10-09 19:29:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658141,2021-01-11 01:53:52 UTC,"This bug is still present.
However the ""ignore_msrs=1"" workaround does not work with QEmu 3.1 anymore. To prevent Windows 10 from crashing one must upgrade QEmu to 5.0.14."
1658141,2021-01-11 01:54:37 UTC,The bug is still present so changing the status back to New.
1658141,2021-01-08 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1658141,2018-03-01 06:16:54 UTC,"It appears this bug affects me too with very similar symptons, but this time, it's while launching the recently released game ""Puyo Poyo Tetris"" using Steam in the guest VM."
1658141,2020-11-08 09:06:41 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1658142,2017-01-20 18:26:01 UTC,"Looks like this will also need a ""mon data"" change in ceph.conf."
1658142,2017-01-20 20:10:13 UTC,"Never mind - looks like keyring is hard-coded, so modifying the mon-data string or the config won't work. e.g."
1658142,2017-02-27 10:51:39 UTC,"yeah,only this local.conf var CEPH_DISK_IMAGE is valid, if other namespace is to be used."
1658144,2017-02-27 16:28:44 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1658144,2017-01-23 08:24:53 UTC,https://review.openstack.org/#/c/423415/
1658144,2017-01-24 08:20:25 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/424498"
1658144,2017-01-24 10:28:18 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/424565"
1658144,2017-02-08 08:36:33 UTC,"Reviewed:  https://review.openstack.org/424498
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=70239cadfef134bdfc45ada59c7c225f6cbfcb5d
Submitter: Jenkins
Branch:    stable/newton"
1658144,2017-02-08 09:03:21 UTC,"Reviewed:  https://review.openstack.org/424565
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=111ed81108c4ab68d2d5e24400a663f94335397d
Submitter: Jenkins
Branch:    stable/mitaka"
1658144,2017-02-08 15:56:34 UTC,"Reviewed:  https://review.openstack.org/423415
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=2326ef963a51379d54d402ab19b9dc98985b1424
Submitter: Jenkins
Branch:    master"
1658144,2017-03-15 16:17:20 UTC,"Verified on 9.2 mu1 updates.
No 'split-brain' observed in logs during writing to db during ~5min."
1658172,2017-01-20 22:24:32 UTC,"Fiddling with monitor positions in the settings for me also produced windows with title-bars off screen. There should be an algorithm that moves windows so their title-bars can be accessed by mouse again.
This may be an upstream issue as well."
1658178,2017-01-23 09:30:19 UTC,"18/01 08:21:03 <pitti> barry: I just ran the systemd ""upstream"" autopkgtest on debian sid, which also recently got kernel 4.9; same problem with the qemu crash apparently"
1658181,2017-03-24 23:37:30 UTC,"My thoughts on this are that it may be acceptable to bundle dependencies in SRUs when the stable Ubuntu release doesn't already have the given dependency packaged. This would be acceptable to me in snapd's case since upstream has a very close relationship with Ubuntu Security, we trust that they'll be helpful in performing any necessary security updates, and they regularly SRU new upstream releases."
1658181,2017-03-29 01:18:43 UTC,"I think Tyler's proposal makes sense. I maintain snapd with unbundled dependencies in Debian sid, and it's really not been very painful."
1658181,2017-02-01 08:01:29 UTC,"Snapd is a complex application that is constantly evolving (new features are being added in nearly every release made) and it is unreasonable to create something like snapd without depending on a new library or new version of a library as the need arises. Bringing each and every dependency back to 14.04, 16.04, 16.10 and 17.04 on an on-going basis is unrealistic as it would easily consume the time of a full-time engineer that we cannot allocate at this time. During the way the Debian and Ubuntu policy is structured this would also delay (possibly each new release) by weeks at a time."
1658197,2017-01-30 09:22:48 UTC,"Hi,"
1658203,2017-01-27 22:45:58 UTC,I tried using diff=none and that didn't help.
1658203,2017-01-27 22:56:42 UTC,I wonder if this has something to do with it:
1658219,2017-03-28 09:24:51 UTC,Not fixed because we had to revert the commits due to various regressions.
1658219,2019-08-27 08:02:42 UTC,"If the kernel team could add the ""assumes"" to the edge kernel relatively soon that would be great. Then we can do some extra testing to double check that devices behave correctly when both core and kernel are refreshed in the same transaction."
1658219,2019-08-27 08:00:59 UTC,Thanks Jamie! I looked into this from the snapd side and I think we should do the following:
1658219,2019-08-27 07:52:05 UTC,Reverting the patch according to comment #20.
1658219,2019-08-26 16:16:28 UTC,"After discussing with Field, snapd, kernel and the security team, this will break existing Ubuntu Core devices that use the 4.4 kernel and the network-manager snap in the default channel (per reporter, the 1.10 channel is unaffected). Therefore, the 4.4 kernels snaps that include this change (ie, 4.4.0-160.188 based) must not be promoted to stable at this time."
1658219,2019-08-21 10:01:07 UTC,The fix causes at least the network-manager fails to work in Ubuntu Core: https://bugs.launchpad.net/snapd/+bug/1840873
1658219,2019-08-20 15:58:33 UTC,Hello.
1658219,2019-04-03 20:29:10 UTC,"On 2019-04-03 03:06:09, thighland wrote:

> I encountered this issue on xenial after updating to Azure's 4.15 kernel
> for testing. We started encountering an apparmor deny which doesn't
> happen on the latest 4.4 kernel. I had missed setting the k flag for a
> policy, and everything worked on the new kerenl once we fixed the
> policy.
>
> Given that this bug leads to incorrect enforcement of policy does it
> make sense to release a fix for xenial?
"
1658219,2019-04-03 03:06:09 UTC,"I encountered this issue on xenial after updating to Azure's 4.15 kernel for testing. We started encountering an apparmor deny which doesn't happen on the latest 4.4 kernel. I had missed setting the k flag for a policy, and everything worked on the new kerenl once we fixed the policy."
1658219,2017-07-26 15:57:06 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1658219,2017-03-31 03:33:19 UTC,Note: this bug affects more than just lock mediation permissions. It at a minimum can also affect the mmap executable (m) permission.
1658219,2017-03-29 23:13:19 UTC,This bug was fixed in the package linux - 4.8.0-45.48
1658219,2017-03-02 08:46:11 UTC,This bug was fixed in the package linux - 4.8.0-40.43
1658219,2019-08-27 13:18:22 UTC,"@mvo I don't understand why we'd add the ""assumes"" to the kernel's snapcraft.yaml now since we're reverting the problematic AppArmor commit. A kernel with the AppArmor commit will never be released to stable (or -updates/-security) so I don't think that the ""assumes"" workaround is needed any longer."
1658219,2017-02-27 19:21:11 UTC,4.4.0-65.86-generic fixes this issue on xenial.
1658219,2017-02-27 19:20:55 UTC,4.8.0-40.43-generic fixes this issue on yakkety.
1658219,2017-02-27 19:17:31 UTC,4.10.0-8.10-generic has the fix for this bug so marking the zesty task as released.
1658219,2017-02-27 17:16:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1658219,2017-02-27 17:15:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1658219,2017-02-23 15:00:26 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1658219,2017-01-24 22:09:54 UTC,This affects utopic-yakkety
1658219,2017-01-24 21:56:54 UTC,"Thanks John, this kernel fixes the issue for me."
1658219,2017-01-24 14:12:13 UTC,There is a test kernel available in
1658219,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1658226,2017-01-20 22:50:02 UTC,possibly related:
1658230,2019-04-17 18:11:58 UTC,"It appears to me that share_migration.rst has been already modified
accordingly. Is zfs-on-linux-driver.rst or any other file needs to be
modified too?"
1658230,2019-04-27 05:47:08 UTC,"Hi Sneha,"
1658230,2020-03-22 07:30:40 UTC,"Hi Sneha,"
1658230,2020-09-23 15:14:06 UTC,"Reviewed:  https://review.opendev.org/715290
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=295adb71bf261bfcbc8ee41ac284901b8b9268d7
Submitter: Zuul
Branch:    master"
1658230,2019-05-03 13:15:04 UTC,"Hi Gautham,"
1658230,2020-03-26 18:18:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/715290"
1658231,2017-01-24 09:27:09 UTC,+1 !
1658233,2019-08-20 12:48:42 UTC,"Tagging server-next mainly because of mysql-8, so we fix this finally, and then SRUs can be considered."
1658233,2019-11-18 12:25:44 UTC,This bug was fixed in the package mysql-5.7 - 5.7.28-0ubuntu0.19.04.2
1658233,2019-11-18 12:25:43 UTC,This bug was fixed in the package mysql-5.7 - 5.7.28-0ubuntu0.18.04.4
1658233,2019-11-18 12:25:42 UTC,This bug was fixed in the package mysql-5.7 - 5.7.28-0ubuntu0.16.04.2
1658233,2019-10-10 13:41:57 UTC,This bug was fixed in the package mysql-8.0 - 8.0.17-0ubuntu2
1658233,2019-10-03 08:05:01 UTC,"I think I have most of these fixed now, but am a bit confused about the org.freedesktop.systemd1 one, as it seems to come from usr/bin/dbus-daemon and not usr/sbin/mysqld?"
1658233,2019-08-19 11:11:15 UTC,"On eoan, we need to add even more lines (I prefer to use /etc/apparmor.d/local/usr.sbin.mysqld):
  dbus send
        bus=system
        path=/org/freedesktop/systemd1
        interface=org.freedesktop.systemd1.Manager
        member=GetDynamicUsers
        peer=(name=org.freedesktop.systemd1),
  capability dac_read_search,
  /proc/*/status r,
  /sys/devices/system/node/ r,
  /sys/devices/system/node/** r,"
1658233,2019-03-16 00:14:50 UTC,"in my case, to have a clean MySQL start, had to do this:"
1658233,2019-03-15 23:58:35 UTC,"also confirming on:
Kernel: 4.15.0-46-generic x86_64 bits: 64 Desktop: Xfce 4.12.3 Distro: Ubuntu 18.04.2 LTS"
1658233,2018-11-20 19:20:50 UTC,"And also still present in disco:
[ter nov 20 15:38:42 2018] audit: type=1400 audit(1542741624.527:358): apparmor=""DENIED"" operation=""open"" namespace=""root//lxd-disco-mysql_<var-lib-lxd>"" profile=""/usr/sbin/mysqld"" name=""/sys/devices/system/node/"" pid=2842 comm=""mysqld"" requested_mask=""r"" denied_mask=""r"" fsuid=165536 ouid=0
[ter nov 20 15:38:42 2018] audit: type=1400 audit(1542741624.535:359): apparmor=""DENIED"" operation=""capable"" namespace=""root//lxd-disco-mysql_<var-lib-lxd>"" profile=""/usr/sbin/mysqld"" pid=2842 comm=""mysqld"" capability=2  capname=""dac_read_search""
[ter nov 20 15:38:42 2018] audit: type=1400 audit(1542741624.547:360): apparmor=""DENIED"" operation=""open"" namespace=""root//lxd-disco-mysql_<var-lib-lxd>"" profile=""/usr/sbin/mysqld"" name=""/sys/devices/system/node/"" pid=2846 comm=""mysqld"" requested_mask=""r"" denied_mask=""r"" fsuid=165646 ouid=0"
1658233,2019-08-20 12:44:23 UTC,"eoan will have mysql-8 soon, so I installed it from proposed to verify.
These are the DENIED messages I got right after installation:
[  580.067210] audit: type=1400 audit(1566304971.013:90): apparmor=""DENIED"" operation=""open"" profile=""/usr/sbin/mysqld"" name=""/sys/devices/system/node/"" pid=8427 comm=""mysqld"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0
[  580.068837] audit: type=1400 audit(1566304971.017:91): apparmor=""DENIED"" operation=""capable"" profile=""/usr/sbin/mysqld"" pid=8427 comm=""mysqld"" capability=2  capname=""dac_read_search""
[  580.088987] audit: type=1107 audit(1566304971.037:92): pid=688 uid=103 auid=4294967295 ses=4294967295 msg='apparmor=""DENIED"" operation=""dbus_method_call""  bus=""system"" path=""/org/freedesktop/systemd1"" interface=""org.freedesktop.systemd1.Manager"" member=""GetDynamicUsers"" mask=""send"" name=""org.freedesktop.systemd1"" pid=8427 label=""/usr/sbin/mysqld"" peer_pid=1 peer_label=""unconfined""
                exe=""/usr/bin/dbus-daemon"" sauid=103 hostname=? addr=? terminal=?'
[  580.091224] audit: type=1400 audit(1566304971.037:93): apparmor=""DENIED"" operation=""open"" profile=""/usr/sbin/mysqld"" name=""/etc/ssl/openssl.cnf"" pid=8427 comm=""mysqld"" requested_mask=""r"" denied_mask=""r"" fsuid=110 ouid=0
[  580.104218] audit: type=1400 audit(1566304971.053:94): apparmor=""DENIED"" operation=""open"" profile=""/usr/sbin/mysqld"" name=""/sys/devices/system/node/"" pid=8428 comm=""mysqld"" requested_mask=""r"" denied_mask=""r"" fsuid=110 ouid=0
[  580.347414] audit: type=1400 audit(1566304971.293:95): apparmor=""DENIED"" operation=""open"" profile=""/usr/sbin/mysqld"" name=""/etc/ssl/openssl.cnf"" pid=8428 comm=""mysqld"" requested_mask=""r"" denied_mask=""r"" fsuid=110 ouid=0
[  580.861280] audit: type=1400 audit(1566304971.809:96): apparmor=""DENIED"" operation=""mknod"" profile=""/usr/sbin/mysqld"" name=""/run/mysqld/mysqlx.sock.lock"" pid=8428 comm=""mysqld"" requested_mask=""c"" denied_mask=""c"" fsuid=110 ouid=110"
1658233,2018-08-01 17:53:57 UTC,"@afunix, was this a fresh xenial 16.04.5 install, or an upgrade from a previous release?"
1658233,2018-11-20 19:17:34 UTC,Confirmed I also see this on bionic.
1658233,2017-01-26 16:39:33 UTC,I'm also noticing those on Xenial systems:
1658233,2017-01-26 17:33:49 UTC,"I added this to the base profile, since other processes tripped over that one. (It's in a separate bug report)"
1658233,2017-01-27 09:45:09 UTC,"Thank you Simon and Kees,
I personally would not want it allowed in my base profile - but I'll leave that for the other bug to decide.
We certainly can consider adding it to mysql together with the others."
1658233,2017-01-23 11:56:32 UTC,"Hi,
thank you for your report and your help to make Ubuntu better!"
1658233,2017-02-28 18:19:32 UTC,"The addition of ""@{PROC}/@{pid}/status r,"" is tracked in LP: #1658239."
1658233,2018-05-01 17:48:18 UTC,Seeing these log entries in Bionic:
1658233,2018-07-30 12:31:44 UTC,"# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.5 LTS
Release:	16.04
Codename:	xenial"
1658248,2017-05-15 22:07:03 UTC,"Sachin Vaidya and I tried with 4.0.0.0-5, and unable to reproduce. We have fixed many issues in flat-subnet and ip allocation since this was observed. Can you try with latest 4.0 or mainline, If we dont see this problem, we can close it"
1658255,2017-01-27 00:28:30 UTC,"I have reproduced this and can confirm it only affects 4.8 kernels. I have a Ubuntu 16.04 system with secure boot enabled, and the 4.4 kernels were enforcing it. Installing and rebooting into the linux-image-generic-hwe-edge kernel (4.8.0-34.36~16.04.1-generic) and everything before the kernel thinks secure boot is enabled, but the kernel does not and freely loads unsigned modules."
1658255,2017-01-27 17:30:48 UTC,"Bah, was missing the linux-signed-generic-hwe-16.04-edge package. Once that was in place, secure boot enforcement works correctly. Not sure if that's the cause of Kees' issue as well."
1658255,2017-01-26 23:54:30 UTC,And it looks like this is specific to the 4.8 kernel. 4.4 thinks secure boot is enabled.
1658255,2017-01-31 19:28:55 UTC,"Kees - there are archive shenanigans involved in getting a signed kernel binary, hence the separate package."
1658255,2017-07-26 15:57:09 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1658255,2017-01-27 19:43:55 UTC,... why aren't all the kernels just signed? Why does this need to be a separate package at all?
1658255,2017-01-26 23:51:26 UTC,"And that must be doing something wrong, since:"
1658255,2017-01-27 17:45:09 UTC,"Also, is there a reason there isn't at least recommends on the corresponding -signed packages for the kernel, to try to avoid this situation? (I realize adding a hard depends would make building/installing test kernels more difficult.)"
1658255,2017-01-26 23:43:03 UTC,"the proc handler does:
        secure_boot_enabled = efi_enabled(EFI_SECURE_BOOT);
this feature flag is set at boot:
#ifdef CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE
        if (boot_params.secure_boot == EFI_SECURE_BOOT) {
                set_bit(EFI_SECURE_BOOT, &efi.flags);
                enforce_signed_modules();
                pr_info(""Secure boot enabled\n"");
        }"
1658255,2017-01-26 20:07:24 UTC,"(Hm, dmesg WARN on IOMMU seems to think I need 910170442944e1f8674fd5ddbeeb8ccd1877ea98, but that's unrelated...)"
1658255,2017-01-24 21:26:47 UTC,"$ cat /proc/sys/kernel/secure_boot
0"
1658255,2017-01-23 13:46:59 UTC,Kees - what is the result of 'cat /proc/sys/kernel/secure_boot' ?
1658255,2017-01-21 02:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1658255,2017-01-26 23:47:37 UTC,"Oh, and that's not set up by the bootloader, it's in arch/x86/boot/compressed/eboot.c:"
1658259,2020-08-07 00:17:42 UTC,"The change https://review.opendev.org/419163 introduced a property on the share instance model called ""cast_rules_to_readonly"". This property is available in the JSON response of APIs:"
1658260,2017-01-22 18:37:42 UTC,I'm going to update the sk1 link soon. Thanks Alvin!
1658260,2017-01-22 20:00:32 UTC,Thanks for the info on standalone and the patch. Seems I can now get a .plt to save and import back into Inkscape.  :)
1658260,2017-01-22 21:24:28 UTC,*Correction: 1066.67*1066.67 (px). I had the stroke unset on the .plt in Inkscape.
1658260,2017-01-22 21:42:40 UTC,"the value 1066.67 happens to be the same as 96/90 which corresponds to the change that was recently made in the Inkscape internal dpi.
Was your original svg file originally created in Inkscape 0.92 or did it come from an earlier version? could you attach the original svg file?"
1658260,2017-01-22 22:03:21 UTC,Made the original svg with 0.92.
1658260,2017-01-22 22:42:53 UTC,"thanks. sorry, I guess I should have asked for this up-front. Could you also attach the plt file you got as well as the svg file you got when you read the plt file back in? Inkscape does not actually get involved in the actual conversion process here, it simply calls uniconverter. So it is not likely that this will be fixable in Inkscape. But it might be worthwhile to see whether the error occurred on output or on input."
1658260,2017-01-22 23:27:13 UTC,Sorry for the delayed reply.
1658260,2019-05-19 13:33:29 UTC,"As noted above, this issue has now been migrated to GitLab, closing."
1658260,2017-01-23 14:37:12 UTC,Thanks for taking a look!
1658260,2017-01-23 22:45:22 UTC,"@jazzynico: maybe unrelated, but I get the same error message when trying to import a .cgm file - so I also don't have that module installed on LM18."
1658260,2017-01-24 09:09:34 UTC,"@Maren - It's related because Inkscape also uses Unicovertor to export to PLT, WMF and SK1, and import from SK1, PLT, CDT, WMF, CMX, CDR, CGM, CCX and AI formats."
1658260,2017-01-22 17:32:31 UTC,"I just tested the plt output from trunk, Windows 10, using the latest version of uniconv_output.py."
1658260,2019-01-28 13:56:03 UTC,"continuing this on gitlab:
https://gitlab.com/inkscape/inbox/issues/48"
1658260,2019-01-28 13:01:55 UTC,Just got word from SK1 devs that an update is issued:
1658260,2017-01-23 00:36:28 UTC,"thanks for the plt file. I'm printing it here just for reference.
IN;PU0,11289;PD11289,11289;PD11289,0;PD0,0;PD0,11289;PU;"
1658260,2017-01-22 17:12:03 UTC,"Ok, maybe I should give UC a second change and try to install the standalone version...
That said, there are *lots* of online or offline PLT<->SVG convertors, so I guess it should not be too hard to implement internally. One possibility could be to give a closer look to the UC code and see what we can extract from it.
Also, we already have extensions that import/export HPGL files and send data to plotters directly. I'm not a plotter format expert at all, but I wonder if we could use one of them to handle PLT files."
1658260,2017-01-21 09:06:36 UTC,"Note to self:
The error message shows that gettext is not loaded correctly. To be fixed.
---
  File ""uniconv-ext.py"", line 54, in <module>
    sys.stderr.write(_('You need to install the UniConvertor software.\n'+\
NameError: name '_' is not defined
---"
1658260,2017-01-22 16:17:37 UTC,"@Eduard, so you needed to update the .inx manually?"
1658260,2017-01-22 16:39:13 UTC,"Yes, after installing the standalone version, there's an updated .inx file in the installation folder. They also offer a VisualBasic script that allows to automatically update an already present Inkscape installation, but that step has still to be done manually."
1658260,2017-01-21 04:37:56 UTC,"Please add information about OS/platform to the bug description, thank you."
1658260,2017-01-22 08:26:27 UTC,"Not better on Xubuntu 16.04. The Uniconvertor package fails to run correctly (even in standalone mode with the uniconvertor command line utility) due to a missing sk1 module.
Could someone else on a GNU/Linux distribution or OS-X operating system confirm?"
1658260,2017-01-22 13:57:47 UTC,"jazzynico wrote:

> Could someone else on a GNU/Linux distribution or OS-X operating
> system confirm?
"
1658260,2017-01-22 13:59:49 UTC,"su_v wrote:

> saving as PLT and opening PLT files (via UniConvertor) works AFAICT
> with 0.92 as before with 0.91.
"
1658260,2017-01-21 09:03:58 UTC,Thanks for taking the time to file a report!
1658260,2017-01-22 14:55:15 UTC,"Just to confirm it's a known issue with the Ubuntu package. See Bug #1597322 ""necessary sk1libs isn't packaged""."
1658260,2017-01-22 15:45:41 UTC,Gettext initialization (see comment #3) fixed in lp:inkscape rev. 15430 and lp:inkscape/0.92.x rev. 15328.
1658260,2017-01-22 15:46:10 UTC,"Back to the original report, I suggest that we remove the Uniconvertor related features in the Windows packages (by removing the inx files from the share/extensions folder) until we find a replacement."
1658260,2017-01-22 15:47:33 UTC,...and add a line in the release notes to warn users that it no longer works on Windows.
1658260,2017-01-22 16:08:07 UTC,"> I suggest that we remove the Uniconvertor related features in the Windows packages
When removing the uniconvertor and sk1libs modules from the devlibs (or rather not re-adding them after updating Python as there's no version for Python 2.7) I considered removing the *.inx, too, or at least updating the dependencies in the .inx to prevent it from showing up on Windows.
"
1658260,2017-01-22 14:39:17 UTC,su_v> Confirm what exactly?
1658266,2017-01-23 03:18:35 UTC,Left the image running for a bit and got this
1658270,2017-02-09 22:02:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1658270,2017-01-25 23:26:16 UTC,Your version.  I don't have any other 107 installed.
1658270,2017-01-26 13:15:48 UTC,Thanks for the update.  I can submit an SRU request for Trusty.  Can you see if this bug also affects Xenial:
1658270,2017-01-29 08:13:37 UTC,Affects Xenial as per comment #2 and also Zesty (17.04 amd64 current liveCD as of 2017-01-28).
1658270,2017-02-09 22:01:35 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1658270,2017-02-09 22:02:22 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1658270,2017-02-10 05:31:54 UTC,"Tested on yakkety, 16.10, kernel 4.8.0-38, SAMO7 windows application which failed to run on previous kernel versions, now runs successfully using wine 1.8.5"
1658270,2017-02-20 07:46:10 UTC,This bug was fixed in the package linux - 4.8.0-38.41
1658270,2017-02-13 06:54:14 UTC,Altium Wine bug resolved with kernel 3.13.0-109 from -proposed on Ubuntu 14.04.5 (Trusty).
1658270,2017-02-17 16:03:16 UTC,Can anyone confirm or deny if this bug exists in Precise?
1658270,2017-02-20 07:36:41 UTC,This bug was fixed in the package linux - 3.13.0-109.156
1658270,2017-02-20 07:42:07 UTC,This bug was fixed in the package linux - 4.4.0-63.84
1658270,2017-01-25 16:03:12 UTC,"The stock 3.13.0-107 from the repository works find, or my -107 kernel posted in comment #15?"
1658270,2017-10-17 14:30:05 UTC,"This bug was nominated against a series that is no longer supported, ie vivid.  The bug task representing the vivid nomination is being closed as Won't Fix."
1658270,2017-02-10 06:08:58 UTC,"Tested on 16.04, 4.4.0-63 SAMO7 windows application now runs successfully"
1658270,2017-01-24 08:30:43 UTC,3.13.0-107 seems to be working.  Was able to get to the login screen of Altium 16 on Trusty using Wine-staging 2.0 RC6.  With 3.13.0-101 it freezes.
1658270,2017-01-22 07:53:54 UTC,apport information
1658270,2017-01-21 05:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1658270,2017-01-23 21:45:06 UTC,"I built a Trusty test kernel with the V2 version of the patch:
https://patchwork.kernel.org/patch/9499897/"
1658270,2017-01-22 07:51:52 UTC,Confirmed in 16.04.1 (Xenial) with 4.4.0-59-generic.
1658270,2017-01-22 07:53:21 UTC,apport information
1658270,2017-01-22 07:53:25 UTC,apport information
1658270,2017-01-22 07:53:28 UTC,apport information
1658270,2017-01-22 07:53:31 UTC,apport information
1658270,2017-01-22 07:53:17 UTC,apport information
1658270,2017-01-22 07:53:37 UTC,apport information
1658270,2017-01-22 07:53:39 UTC,apport information
1658270,2017-01-22 07:53:42 UTC,apport information
1658270,2017-01-22 07:53:46 UTC,apport information
1658270,2017-01-22 07:53:50 UTC,apport information
1658270,2017-01-22 07:53:33 UTC,apport information
1658292,2017-07-16 22:13:38 UTC,I have having this error for several times
1658292,2017-07-16 22:13:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658305,2017-01-23 18:28:56 UTC,"Can you be more specific about what ""looks weird"" means?"
1658305,2017-01-23 21:05:51 UTC,"For example, with the default gnome theme (Adwaita, the panel is 100% transparent (I guess that much is intentional), but with grey-ish text (completely unreadable, depending on the wallpaper), see screenshots attached to https://github.com/decathorpe/elementary-stable-rpms/issues/7. Other themes have similar issues."
1658305,2017-02-03 19:09:37 UTC,I can confirm that Adwaita uses grey text for menubar. I have to investigate what to do that won't hardcode styles into the panel and prevent others from actually styling the panel correctly
1658319,2020-06-10 20:42:49 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1658319,2017-01-21 16:27:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1658319,2020-08-10 04:17:33 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1658322,2017-01-24 13:05:10 UTC,"Too bad this is all sudo apt-get update version from the Raspberr Pi repo (it's Debian 8 based one, not Debian 7 old one).  I even didn't know that's no actual version.
I should admit I'm not very experienced user and so I fail."
1658322,2017-01-24 02:35:37 UTC,Can you try a more recent Pinta version? This looks similar to some issues that have been fixed since v1.3
1658322,2017-01-24 13:07:26 UTC,"Or probably there are a ppa for Debian? I can add ppa, if you are give me a proper ppa name."
1658323,2017-11-11 03:27:00 UTC,Here is the pop-up that I get. It began after upgrading to Ubuntu 17.10 64bit.
1658323,2017-11-11 03:28:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658323,2017-01-24 13:31:43 UTC,"This is a duplicate of many of the ""ttf-mscorefonts-installer"" bugs: 1607535 1651923 1658323 etc..."
1658323,2017-01-23 15:00:00 UTC,I Get additional messages now.
1658325,2017-01-23 18:27:40 UTC,Several of these are icon names covered by the fd.o icon naming spec. It doesn't make sense to ship these icons as they are mandated to be present in all icon sets. Namely the following:
1658325,2017-01-23 21:14:48 UTC,"Yes, I know that some of the icons are considered ""generic"" and are covered by the fd.o spec."
1658325,2017-04-02 10:29:26 UTC,"Since the referenced icon is defined in the fd.o icon name specification, the tooling is responsible for picking up the correct icons."
1658325,2017-04-02 10:47:28 UTC,"Since the tooling should pick up standard icon names correctly, I've removed the cases where the icons are adhering to the fd.o Icon Naming Specification."
1658330,2017-01-21 17:10:01 UTC,Not reproduced on Windows XP (32-bit) with Inkscape 0.91 and 0.92.
1658330,2017-01-21 16:28:32 UTC,"Thanks Lucas for fill report.
here a BT with the crash: https://inkscape.org/en/paste/10610/"
1658330,2017-01-21 16:49:29 UTC,Simplified file with crash.
1658330,2017-01-21 17:17:31 UTC,"Reproduced on Xubuntu 16.04, lp:inkscape/0.92.x rev. 15325.
Not reproduced with 0.91 (same system).
Not reproduced with lp:inkscape/0.92.x rev. 15325 on Windows XP."
1658330,2017-01-21 17:30:43 UTC,Seems to occurs when both Snap to path and Snap cusp nodes are active in the snap toolbar.
1658330,2017-01-21 18:35:18 UTC,"Similar earlier reports (crash on rotational snap):
* Bug #1525498 “Crash when rotating circle with offset rotation ce...”
                (same backtrace in comment 2)
* Bug #1578919 “inkscape crashes when elements are rotated to matc...”
                (same backtrace locally, included in attached log)"
1658336,2017-01-22 09:04:23 UTC,"Edit last comment: I meant the 'place' plugin, not the 'put' plugin."
1658336,2017-01-22 08:54:14 UTC,"While progressively disabling updates, I discovered the crash only happens when the the 'put' plugin is enabled."
1658338,2020-08-04 17:10:58 UTC,I can't reproduce this in 1.7 latest development 1.7+r1134-202008032046~ubuntu18.04.1.
1658340,2017-02-01 16:39:24 UTC,"The new Pi 2B revision came out Nov 2016, just wondering when the firmware will be updated to support?  Thanks."
1658340,2017-02-01 19:24:21 UTC,This issue has been a huge barrier for us and really needs to get resolved.
1658340,2019-07-17 12:23:04 UTC,Is all solved now and can this issue be closed?
1658342,2017-01-21 18:14:58 UTC,"Related:
* Bug #1657906 “About Screen 0.92: get scaling pop-up”
  https://bugs.launchpad.net/inkscape/+bug/1657906
(0.92.x only, for now - there is no updated devel about screen in trunk.)"
1658345,2017-08-11 06:17:43 UTC,"Please try this kernel:
http://people.canonical.com/~khfeng/lp1658345-elan-i2c/"
1658345,2017-08-11 12:59:57 UTC,"ApportVersion: 2.20.3-0ubuntu8.7
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2017-07-12 (29 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS ""Xenial Xerus"" - Release amd64 (20170215.2)
Package: linux (not installed)
Tags:  yakkety
Uname: Linux 4.13.0-041300rc4-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True"
1658345,2017-08-10 09:11:21 UTC,"4.13-rc4 - touchscreen is working. No go on touchpad, does not show up with lsusb, lspci or lshw"
1658345,2017-08-09 04:34:04 UTC,Please try 4.13-rc4 again. Hopefully the touchscreen regression is fixed now.
1658345,2017-07-19 06:42:24 UTC,apport information
1658345,2017-07-19 06:42:23 UTC,apport information
1658345,2017-07-19 06:07:35 UTC,Can you apport-collect under 4.13?
1658345,2017-08-25 06:46:14 UTC,"@Varga,"
1658345,2017-07-18 06:04:58 UTC,It's a regression for your touchscreen - can you find the first bad mainline kernel that fails to make touchscreen work?
1658345,2017-07-18 05:04:38 UTC,Please see attached. The touchscreen does not work. It does not even show up in my device list.
1658345,2017-07-18 04:29:00 UTC,"Okay, so the error in dmesg in #25 should be fixed in -rc3."
1658345,2017-07-17 22:58:47 UTC,"In the Windows 10 device manager, it is listed as ""ELAN pointing device"". In device details it indicates the manufacturer is ""ELAN"" and location indicates ""on I2C HID Device""."
1658345,2017-08-11 12:59:59 UTC,apport information
1658345,2017-07-17 15:27:41 UTC,What's the touchpad ID under Windows 10?
1658345,2017-07-19 01:14:35 UTC,"I couldn't get any of the mainline kernels to recognize my touchscreen or touchpad. I checked between 4.4 and 4.13 with no luck. The touchscreen works on Ubuntu 16.10 (4.8) and 17.04 (4.10.0-20). Since it works on those distributions, I'm not sure why none of the mainline kernels will work. Any recommendations?"
1658345,2017-08-11 13:00:01 UTC,apport information
1658345,2017-08-18 00:08:52 UTC,Here is dmesg for v4.13 rc5
1658345,2017-08-12 13:53:05 UTC,"I was able to get the mousepad working with the last kernel you posted. However, the touchscreen is not working. Mousepad shows up as ""Elan Touchpad"" in xinput. Now missing ""SYNA7300:00 06CB:177C"" device that was the touchscreen."
1658345,2017-08-15 03:34:58 UTC,"Alright, try this:
http://people.canonical.com/~khfeng/linux-image-4.13.0-rc5-elan0602_4.13.0-rc5-elan0602-1_amd64.deb"
1658345,2017-08-15 23:18:03 UTC,apport information
1658345,2017-08-15 23:18:04 UTC,apport information
1658345,2017-08-15 23:20:46 UTC,"No luck with touch screen. Same as before, the touchpad works but no touchsreen. I posted apport info. Also got an error indicating headers were missing b/c you only posted the single deb image. Not sure if that has something to do with it."
1658345,2017-08-16 04:22:59 UTC,"Weird. Does [1] have the touchscreen issue?
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/linux-image-4.13.0-041300rc4-generic_4.13.0-041300rc4.201708062231_amd64.deb"
1658345,2017-08-16 23:55:30 UTC,Neither touch screen nor touchpad works :(
1658345,2017-08-17 05:25:46 UTC,"Okay, so the touchscreen issue is unrelated to touchpad. I'll send a patch to enable the touchpad first."
1658345,2017-08-17 05:46:06 UTC,"Okay, so the touchscreen issue is unrelated to touchpad. I'll send a patch to enable the touchpad."
1658345,2017-08-18 00:07:20 UTC,Here is dmesg for 4.13 rc4
1658345,2017-07-17 11:12:39 UTC,"elantech is the touchpad that Ubuntu cannot recognize. Without it, I do not have a mouse unless I use an external one or touchscreen. Also, I currently use kernel 4.8.0-45 and the touchscreen works. When I tried the kernels you provided, the touchscreen does not show up in xinput -list. In kernel 4.8.0-45 it shows up as ""SYNA7300:00 06CB:177C""."
1658345,2017-08-18 03:30:22 UTC,"When you rollback to old kernel, does the touchscreen work? Which version is it? Do you use DKMS for the touchscreen?"
1658345,2017-08-24 13:33:16 UTC,I *think* I have the same touchpad issue with an IdeaPad 320. How do I find out if I have the same touchpad as in the Flex? I have no Windows to find out running it:(
1658345,2018-07-06 17:06:24 UTC,"Though the symptoms are the same, a lot of time the root cause differs. So please file a new bug."
1658345,2017-08-11 13:00:03 UTC,apport information
1658345,2017-07-17 07:20:55 UTC,Why do you need elantech_x551c at first place?
1658345,2018-07-04 11:42:57 UTC,@kaihengfeng I am having a similar problem with a Lenovo ideapad 330. Could I get access to the custom kernel you posted before? Those links are dead.
1658345,2017-07-15 23:50:18 UTC,"Please see attached. I got an error indicating ""elantech_x551c"" is missing when installing the kernels."
1658345,2017-07-15 23:51:43 UTC,And here is dmesg for the second kernel.
1658345,2017-01-21 18:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1658345,2017-01-21 19:01:31 UTC,apport information
1658345,2017-01-21 19:01:33 UTC,apport information
1658345,2017-01-21 19:01:35 UTC,apport information
1658345,2017-01-21 19:01:36 UTC,apport information
1658345,2017-01-21 19:01:38 UTC,apport information
1658345,2017-01-21 19:01:40 UTC,apport information
1658345,2017-01-21 19:01:42 UTC,apport information
1658345,2017-01-21 19:01:45 UTC,apport information
1658345,2017-01-21 19:01:47 UTC,apport information
1658345,2017-01-21 19:01:50 UTC,apport information
1658345,2017-01-21 19:01:52 UTC,apport information
1658345,2017-01-21 19:06:07 UTC,"Helllo Brad. I ran the command that you provided and posted the log file.
Please let me know if this is sufficient. Thanks."
1658345,2017-01-21 19:01:44 UTC,apport information
1658345,2017-01-23 18:36:02 UTC,"I was never able to get Ubuntu to recognize the touchpad. This is a new
laptop. Last week, I tried the latest upstream version 17.10 with the same
result. Is there a new version this week?"
1658345,2017-07-15 12:25:30 UTC,"Hmm, can you attach both dmesg?"
1658345,2017-01-23 18:01:27 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1658345,2017-07-13 04:28:21 UTC,"Please try kernel in [1] and [2], see which one works."
1658345,2017-07-08 02:54:00 UTC,"I tried the latest kernel v4.12-rc7, bit it still does not recognize my touch pad."
1658345,2017-07-03 08:55:52 UTC,"Both touchpad and touchscreen failed to initialize because of i2c-designware:
[    7.199291] i2c_hid i2c-SYNA7300:00: i2c-SYNA7300:00 supply vdd not found, using dummy regulator
[    8.228444] i2c_designware i2c_designware.1: controller timed out
[    8.228462] i2c_hid i2c-SYNA7300:00: hid_descr_cmd failed
[    8.317098] i2c_hid i2c-ELAN0602:00: i2c-ELAN0602:00 supply vdd not found, using dummy regulator
[    9.348419] i2c_designware i2c_designware.2: controller timed out
[    9.348437] i2c_hid i2c-ELAN0602:00: hid_descr_cmd failed"
1658345,2017-05-27 16:52:59 UTC,"I was able to load release 2 of the mainline kernel released on 5/22/17.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc2/"
1658345,2017-05-20 21:52:23 UTC,"I tried loading the latest mainline kernel and I got this error: ""ACPI Error: No handler for Region [ECRM]"". Please advise. Thanks."
1658345,2017-07-15 00:47:20 UTC,"Neither kernel worked unfortunately. Please see attached. Additionally, my touch screen was not recognized."
1658345,2017-05-09 23:27:54 UTC,"I'm also having this problem.
Touchpad mostly works in the Basic setting in BIOS/UEFI, but when I'm on Advanced, the touchpad doesn't even show up in xinput."
1658345,2017-04-15 12:35:47 UTC,"Hey Just Bob. It may help if you indicate that the bug affects you in the section above. May also help if you send Ubuntu bug info via apport. Hopefully, we can raise the profile on this bug and get it fixed. Thx."
1658345,2017-04-15 03:12:41 UTC,"I am having the same problem. The touchscreen and touchpad both work in Windows 10, but the touchpad won't work in Linux."
1658345,2017-03-03 23:34:39 UTC,Hi. Just following up to see if there are any new touchpad drivers that may help. Thanks.
1658345,2017-01-24 01:23:53 UTC,I tested my laptop with the upstream kernel 4.10 and it does not recognize my touchpad. Please see attached screen shot I captured during the install. It indicates an error with the Elantech ps mouse / touchpad device.
1658345,2017-05-19 07:02:02 UTC,"Looks like i2c-hid wasn't loaded for Elan.
Can you try latest mainline kernel here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/
And boot with `i2c-hid.dyndbg=+p' to kernel parameter.
Attach `dmesg` afterward."
1658353,2017-01-24 15:23:59 UTC,Visual proof of behaviour
1658354,2018-01-25 08:41:23 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1052
1658354,2017-06-01 19:19:10 UTC,Fixed upstream?
1658354,2017-05-24 19:41:47 UTC,"Upstream bugs #84332 (compression of mysql.gtid_executed has been prevented when super_read_only = 1) and #84437 (super-read-only does not allow FLUSH LOGS on 5.7) are not longer happening in Percona Server 5.7.18, these two bugs were related with this hung. So this bug, can't be reproduced in PS 5.7.18."
1658354,2017-05-24 17:19:31 UTC,Should be re-verified and closed?
1658354,2017-01-21 19:06:16 UTC,Tested in PS 5.7.16 and MySQL Community 5.7.17
1658354,2017-05-23 14:41:42 UTC,This should be fixed by commit:
1658357,2017-07-22 20:34:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658357,2017-07-22 20:55:27 UTC,"That seems to be a systemd issue, we don't do anything special with systemd in apt."
1658361,2017-01-23 18:21:53 UTC,Fixing this is dependent on fixing this first: https://bugs.launchpad.net/wingpanel-indicator-notifications/+bug/1487291
1658365,2017-11-21 12:09:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/521830"
1658365,2018-01-05 18:54:18 UTC,This issue was fixed in the openstack/python-zunclient 1.0.0 release.
1658365,2017-09-08 22:58:19 UTC,There is no activity for fixing this bug for a while. I am going to remove assignee so that other contributors can take it.
1658365,2017-11-23 20:28:12 UTC,"Reviewed:  https://review.openstack.org/521830
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=1d1bf668682fe195a7429bae60c8dcf2b27ff74e
Submitter: Zuul
Branch:    master"
1658365,2017-01-27 06:55:16 UTC,"Hi Feng,"
1658365,2017-02-09 11:19:00 UTC,"Hi Feng,
I am reassigning this bug to me after no response from you. Thanks!"
1658369,2020-08-04 17:09:09 UTC,"This is not Pinta fault if Google Chrome is opening files with Pinta. Check Google Chrome setting.
Closing down, because this is not Pinta problem."
1658370,2017-01-23 21:40:06 UTC,..and I'm wondering why I don't get email notifications for new replies.
1658370,2017-02-06 18:30:07 UTC,"Looks like the problem is that 69.195.146.38 (our VPS) does not have a PTR record pointing to mixxx.org. I've asked Garth if his VPS provider supports PTR records. I don't think all email is getting rejected, just some mail servers that check rDNS."
1658370,2017-04-03 03:35:30 UTC,"As of March 12, 2017 we got a PTR record for 69.195.146.38 mapping to mixxx.org. The rate of mail rejects dropped precipitously on that day based on our postfix logs."
1658374,2017-01-28 18:10:14 UTC,Fixed on my system with the following:
1658374,2017-01-22 19:52:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658374,2017-01-23 23:28:23 UTC,+1
1658398,2017-01-22 06:02:14 UTC,"I just executed some iptables commands to block everything, now nmap says my ports are closed. So maybe ufw and firewalld can only write to iptables but cannot read the rules it already has?"
1658398,2017-01-22 05:51:35 UTC,"I experience this, the firewall plug shows as empty but nmap prints the following:"
1658402,2017-01-22 06:16:29 UTC,Significant because its very confusing...
1658402,2017-02-09 16:46:00 UTC,"Not that it helps, but I've got an Intel 7260 wireless/BT card which suffers from a similar problem.  On suspending the computer, after a restart, about 50% of the time, bluetooth will not be detected.  I'm forced to keep suspending/restarting until bluetooth is enabled again."
1658402,2017-02-12 10:26:15 UTC,"Additional info in case it helps: I just discovered that after restarting X with <ctl><alt><bksp> my bluetooth speaker (echo dot) that has been dropping out as the result of this issue, still shows connected in the menu>preferences>bluetooth window, but the speaker device in the preferences>hardware>Choose a device to configure tab is missing the device and the speaker is non-functional. Apparently just reloading X did something to it."
1658402,2017-03-27 19:07:09 UTC,"#service bluetooth restart wont restart it. #service --status-all shows [ + ]  bluetooth.
So is there another service bluetooth depends on???"
1658416,2017-01-22 09:55:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423793"
1658416,2017-02-15 16:36:08 UTC,This issue was fixed in the openstack/kolla-kubernetes 0.5.0 release.
1658448,2017-05-11 13:10:14 UTC,"Well, the computation time is improved but I think this feature may be to better."
1658448,2017-01-22 17:59:43 UTC,"I agree phenomena could be made selectable, and yes, oppositions of moon and planets are hardly relevant for today's observers. Actually, simulating with a computer is not relevant for observers, only the observation in the sky is. ;-) But in context of historical research, even what may appear to be ""only astrologically relevant"" phenomena can be interesting for some users.
The AstroCalc is a rather new feature, so it will likely undergo a few more improvements. For the time being, just don't overuse it, or expect to also wait for 5 minutes."
1658448,2017-02-25 08:44:15 UTC,"Current implementation of phenomena calculator uses iteration to finding a phenomena (with progressive changing of time step). This is better way what I find in the current environment, but I hope he can be improved in the future."
1658448,2018-09-19 14:58:56 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/375
1658452,2017-01-22 13:12:33 UTC,"Change abandoned by Wei Cao (cao.wei@99cloud.net) on branch: master
Review: https://review.openstack.org/423798"
1658452,2017-01-22 11:05:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423798"
1658452,2018-12-07 09:57:07 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.openstack.org/420407"
1658464,2017-01-22 16:55:35 UTC,2. might be a bit difficult - how do you define the last setting if multiple AIs were set to different levels?
1658464,2017-01-22 17:16:58 UTC,Don't know if it's feasible but 2. was meant only for the human player slot. Of course it should not apply for multiplayer games then.
1658464,2017-01-22 21:55:24 UTC,I am against adding options! This is not a text editor and each option is only used by a few percent of players.
1658464,2017-01-23 07:53:49 UTC,"That would definitely make things easier. I already have a branch for pictorial dropdowns, but I'm still struggling with getting things to behave for multiplayer."
1658464,2017-01-26 09:34:51 UTC,"SirVer, i understand your point. But i think making a general rule like ""No options!"" is to restrictive. Can we call it ""No useless options!""? In a wider sentence: ""Do not add options which are useless for players!"""
1658464,2017-01-30 07:00:25 UTC,"> But i think making a general rule like ""No options!"" is to restrictive.
"
1658464,2019-09-17 08:21:58 UTC,Migrated to https://github.com/widelands/widelands/issues/2068
1658466,2017-01-22 12:59:19 UTC,I have no clue why I am getting this ms.
1658473,2017-01-22 13:18:15 UTC,"I'm not sure if my diagnosys is good enough, since I have not been able to replicate it always. I think that this issue may be part of the strange behaviour of the a bit unstable context of the new view pane."
1658476,2018-05-08 18:02:14 UTC,This change was made by a bot.
1658479,2017-12-19 08:01:49 UTC,"Change abandoned by Omer Anson (<email address hidden>) on branch: master
Review: https://review.openstack.org/493537
Reason: Idle for a long time. Also most of the work is done in https://review.openstack.org/#/c/527078/"
1658479,2017-08-14 12:51:59 UTC,"Moved to high. I want to finish it before end of cycle, and it should be a simple search and replace fix."
1658479,2017-08-14 13:00:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/493537"
1658492,2017-07-10 14:11:35 UTC,"scap-workbench is available only in Zesty, which is not LTS."
1658492,2017-07-10 14:26:10 UTC,"cap-workbench is also available in Artful, which is not released."
1658492,2017-07-10 18:18:28 UTC,"For your information:
scap-workbench from https://github.com/OpenSCAP/scap-workbench (for example 1.1.5) works normally on Ubuntu Xenial with libopenscap8 and libopenscap-dev from official repositories."
1658493,2017-01-22 20:38:50 UTC,"Fixed by inserting these into compile.ac
m4_pattern_allow([^AM_])
m4_pattern_allow([^AC_])
m4_pattern_allow([^AS_])"
1658498,2017-05-22 08:04:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658510,2017-08-15 08:31:15 UTC,"An interesting addition is that it seems that the bug is not active in the 'preview' window of ""Text and Font (Shift+Ctrl+T)"""
1658510,2017-08-15 08:27:26 UTC,I can also confirm this bug.
1658510,2017-08-29 18:43:47 UTC,Is there any update to this?
1658510,2017-06-27 18:17:16 UTC,Is there any news about this bug?!
1658510,2017-09-02 07:32:42 UTC,I can confirm this bug with 0.92.
1658510,2017-12-29 06:24:06 UTC,This bug is still present. I downgraded to working with 0.91.
1658510,2017-09-02 09:23:15 UTC,"I'm like
yes, the bug with 0.92."
1658510,2017-12-29 06:40:48 UTC,And to be clear: this bug isn't present in 0.91 that's included in Linux Mint 18.3 (or Ubuntu 16.04). 0.91 had some quirkiness when working with RTL. 0.92 is totally broken...
1658510,2017-06-05 23:12:47 UTC,"Sorry, wrong link on previous message for the SVG file. (I can't edit)
Here is the file:
https://github.com/Deevad/peppercarrot_ep03_translation/blob/c456bc32abf27779e1c0179c48b2418ac61c9beb/ar/Pepper-and-Carrot_by-David-Revoy_E03P07.svg?short_path=e3d2e52"
1658510,2017-01-27 15:46:08 UTC,Thanks for taking the time to file a report!
1658510,2017-04-18 14:39:12 UTC,Also affects other RTL languages (see duplicate). Changing title accordingly.
1658510,2017-01-27 18:16:07 UTC,Thank you for your responsiveness Mr jazzynico!
1658510,2017-01-27 17:55:40 UTC,"Just for the record, Arch Linux 0.91-22 is the last 0.91 version. As Arch didn't backport patches from the 0.91.x branch or from the trunk (Arch versions of the package are mainly recompilations due to dependencies updates and packaging changes), 0.91-22 can be considered equivalent (patch-wise) to the official version."
1658510,2017-01-27 17:46:26 UTC,Thanks for reporting back!
1658510,2017-01-27 16:09:34 UTC,Thank you for your reply Mr. @jazzynico
1658510,2017-01-22 20:00:17 UTC,This is the 0.92 attachement
1658510,2017-06-05 23:09:57 UTC,All Arabian translations of the episode of Pepper&Carrot are also affected by this bug:
1658516,2017-01-26 11:35:26 UTC,"Yes, I bet there are plenty more..."
1658516,2017-01-26 11:18:28 UTC,"Hello Nick,"
1658516,2017-01-26 07:02:53 UTC,"I agree.
It would be best to support the sunf90 compiler as well. I am guessing there will be more problems.
I will try to fix these problems in the coming future. I am not currently easily accessible to different compilers."
1658516,2017-01-25 06:41:37 UTC,Thanks!
1658516,2017-01-25 09:28:32 UTC,"hm. I used sunf95 instead of sunf90 with the same error. I can promise to
try 12.4 at some point. It may seem as an unnecessary work (because the
program can be compiled with ifort and gfortran), but compiling with
different compilers/running is normally helping to elevate the quality of
software."
1658519,2017-01-29 06:28:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658522,2017-01-23 17:38:35 UTC,"Hi Chad,"
1658524,2019-11-22 19:25:55 UTC,apport information
1658524,2019-12-03 00:18:13 UTC,"Different container, but:"
1658524,2020-08-21 08:11:22 UTC,"Happens also on byobu version 5.112 (tmux 2.8), the one that comes with the up-to-date Raspberry Pi OS / Raspbian (tested on both a RPi2 and a RPi4)."
1658524,2019-11-22 20:52:31 UTC,**
1658524,2019-11-22 20:09:00 UTC,If you could provide:
1658524,2019-11-22 19:25:54 UTC,apport information
1658524,2019-11-22 19:25:53 UTC,apport information
1658524,2019-11-22 19:25:51 UTC,apport information
1658524,2019-11-22 19:25:49 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
DistroRelease: Ubuntu 18.04
Package: byobu 5.125-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: User Name 5.0.0-29.31~18.04.1-generic 5.0.21
RelatedPackageVersions:
 byobu                   5.125-0ubuntu1
 screen                  4.6.2-1ubuntu1
 screen-resolution-extra N/A
Tags:  bionic uec-images
Uname: Linux 5.0.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True"
1658524,2019-03-06 21:05:49 UTC,"Can confirm that this happens with a fresh Ubuntu installation, byobu version 5.127, tmux 2.7."
1658524,2018-08-12 15:59:12 UTC,That means that disk_io is crashing.  Need to figure out where/why.
1658528,2017-03-16 18:53:08 UTC,"Okay there's a BIOS setting in the motherboard. Something like ""Enable Onboard Audio"". I had it on ""Enabled"". I set it to ""Auto"" and the sound worked immediately! Ubuntu's drum sound came out. It never ever came out before. Sound used to work after login. Awesome 8)"
1658528,2017-03-14 17:15:17 UTC,Oh no it stopped working again.
1658528,2017-03-02 14:40:11 UTC,Fixed itself somehow. Updates probably
1658528,2017-01-23 05:17:05 UTC,"of course Ii tried that, but after you asked I tried again and again. Doesn't work but the thing is it's totally silent. Not glitching or anything. It seems very unlikely to me to be a hardware thing. It's a desktop. I didn't do anything. I didn't move it at all and it happened after a reboot."
1658528,2017-01-23 04:56:10 UTC,"Ok, do you have a 16.04 image handy? You may want to consider downloading 16.04, and testing with that. If that works, then maybe its worth considering an upgrade."
1658528,2017-01-23 04:28:01 UTC,"What if you unplug and re-plug? If that doesn't work, then its likely something may have happened to your hardware. Do you have other outputs you could test?"
1658528,2017-01-23 04:06:16 UTC,...now typing through a 14.04 live usb & still not working. Also showing Headphones (unplugged) I now remember that when I first installed 14.04 it truely wasn't working.
1658528,2017-01-23 03:46:32 UTC,now typing through a 16.04 live usb. sound doesn't work. It shows Headphones (unplugged)
1658528,2017-01-23 02:54:25 UTC,Yes I always stay up to date. I'll try booting into a live usb and give feedback. Currently I have no other installed distros.
1658528,2017-01-23 00:33:19 UTC,"Had you updated your system that you can remember prior to this problem occurring? If you were to boot 14.04 live media, does the problem exist there? If you have Windows or another distro installed, does the problem occur there?"
1658529,2017-11-14 16:15:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658529,2017-01-23 14:45:26 UTC,"Steps to reproduce on Ubuntu 12.04.5 LTS:
1. sudo apt-get install libopenscap1 # this will install 0.8.0-4build1
2. cd /tmp
3. wget https://people.canonical.com/~ubuntu-security/oval/com.ubuntu.precise.cve.oval.xml
4. oscap oval eval --results /tmp/results-precise.xml --report /tmp/report-precise.html /tmp/com.ubuntu.precise.cve.oval.xml"
1658529,2017-01-23 15:18:10 UTC,"Steps to reproduce on Ubuntu 12.04.5 LTS:
1. sudo apt-get install libopenscap8 # this will install 1.0.2-1
2. cd /tmp
3. wget https://people.canonical.com/~ubuntu-security/oval/com.ubuntu.trusty.cve.oval.xml
4. oscap oval eval --results /tmp/results-trusty.xml --report /tmp/report-trusty.html /tmp/com.ubuntu.trusty.cve.oval.xml"
1658529,2017-01-23 15:21:58 UTC,"In comment 3 I mean of course ""Steps to reproduce on Ubuntu 14.04.5 LTS:"", I'm sorry."
1658529,2017-07-10 14:14:04 UTC,As today Xenial has outdated version of openscap (see my comment 7 on bug 1658759).
1658532,2017-01-29 12:47:26 UTC,But midori 0.4.3 is the latest version available in ubuntu using synsptic package manager
1658532,2017-01-28 03:18:04 UTC,Hello William! I can confirm that what you are trying to achieve works in Midori 0.5.11.
1658536,2017-01-23 00:15:15 UTC,"The provided SVG file was created with Inkscape 0.48.5, and contains non-uniformly scaled bitmap images. Due to changes in Inkscape 0.91 to better conform to the SVG standard, such bitmap images are rendered differently (older Inkscape versions ignored the SVG specification in this regard)."
1658536,2017-01-24 09:58:13 UTC,"thank you!
and sorry for panic...
k."
1658536,2017-01-24 14:36:34 UTC,"Sorry for the inconvenience due to earlier changes in Inkscape 0.91. The workaround to adjust bitmap images is not obvious to users, and barely mentioned in the release notes:"
1658543,2017-01-22 23:22:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/423868"
1658543,2017-02-03 12:01:44 UTC,"Change abandoned by Dan Prince (<email address hidden>) on branch: master
Review: https://review.openstack.org/423868"
1658548,2017-02-05 22:34:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658549,2017-01-29 12:45:01 UTC,"That seems very surprising. Usually the juju tools are installed either via
cloud-init or some other mechanism. Do you have any idea how this file
would have been created without being one of the users."
1658549,2017-01-30 14:49:19 UTC,"Hi John,"
1658549,2017-01-30 06:31:38 UTC,"We track Juju 2.x issues in ""juju"" project. Re-targeting :)"
1658550,2017-03-19 00:10:41 UTC,I uninstalled libgrail6 and libgeis and the problem still persists so the problem is not related to grail or geis.  It's probably related to Qt.
1658550,2017-01-23 04:25:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1658556,2019-12-20 08:57:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658558,2017-01-24 02:34:41 UTC,Does the file open successfully in other applications? A bug report without information on the Pinta version and steps to reproduce is difficult to fix ...
1658565,2017-06-30 22:43:07 UTC,I don't see how this has anything to do with Variety (taskbar icons != wallpaper?). Forwarding it anyway to the Zorin OS bug tracker.
1658565,2020-11-12 14:46:07 UTC,"I have the same issue. Zorin OS 15, Dell XPS 15 9560."
1658617,2017-01-24 12:23:27 UTC,"I should point out, this runtime check does work fine on a standard desktop install."
1658617,2017-01-24 12:11:53 UTC,"Thanks to Santosh and ChrisCoulson's help, we've established that oxide is correct: ENABLE_HYBRIS_CAMERA is set, because the check on whether to use libhybris is done at run-time: oxide dlopens libcamera.so.1 and then invokes hybris_camera_initialize() on it, which should fail but not crash.
Therefore, this is likely an issue in libhybris or lower stack."
1658617,2017-02-16 15:18:36 UTC,"This also happens with the webbrowser-app snap (from edge channel), when creating a chat room in either https://appear.in or https://meet.jit.si, the application crashes with the following logs:"
1658617,2017-01-24 10:48:22 UTC,"cmake options are correct, if _IS_LINUX is true then set ENABLE_HYBRIS to OFF
Also ENABLE_HYBRIS_CAMERA is  set to OFF, These are defaults value."
1658617,2017-03-29 08:05:54 UTC,I could see same crash with attach files in gmail while composing mail.
1658617,2017-01-23 11:07:02 UTC,Correction :
1658617,2017-01-23 11:00:23 UTC,The callstack with few symbols is as :
1658617,2017-03-29 13:06:19 UTC,"Thanks Santosh! I've added this environment variable to our webapp launcher (https://gitlab.com/mardy/snapcraft-webapp-helper/commit/7c22b221ca3e2385a6abb437fc0cc987000c20b6), rebuilt the google-webapp, and now it works."
1658617,2017-02-16 23:52:56 UTC,This happened on my world.taobao.com webapp. It crashed when trying to register/login
1658617,2017-01-24 09:23:17 UTC,"Adding oxide: the ubuntu-app-platform snap is simply using the packages from the stable-phone-overlay PPA, so I doubt that the bug is there."
1658617,2017-03-27 14:04:04 UTC,"So, I've tried implementing one suggestion from Simon (morphis); I'm attaching the modified file. Have a look at the CameraCompatAvailable() method in there, and please bear with me for not just posting a patch. :-)"
1658620,2018-05-17 01:41:51 UTC,"In my experience in bionic, the memory isn't even freed when starting a new document with Ctrl+N.  The memory usage simply keeps ballooning with every additional page scanned."
1658620,2017-01-23 09:33:20 UTC,"Note: If you do ""New Document"" the memory does get freed up as expected, but on deletion it is ""stuck""."
1658621,2017-01-27 22:26:22 UTC,Thanks Joseph.
1658621,2017-02-10 10:39:00 UTC,Updated to 16.10 Yakkety-Yak and touchpad has started working again - no idea what fixed it though!
1658621,2017-01-23 09:31:01 UTC,This change was made by a bot.
1658621,2017-01-23 18:00:14 UTC,Does this bug go away if you boot back into the prior kernel version?
1658623,2017-01-23 09:57:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424036"
1658623,2017-09-01 16:16:30 UTC,Unassigning due to no activity for > 6 months.
1658623,2018-04-18 00:20:56 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/424036
Reason: No updates in quite awhile. Feel free to restore and update if you wish to continue with this."
1658626,2017-01-24 01:54:55 UTC,"By ""not handled"" I guess you mean ""don't work""?"
1658626,2017-01-24 08:53:57 UTC,"No I haven't tried the head of gtk3 branch, I use the dnf version of terminator I'll try soon"
1658626,2017-02-01 13:06:38 UTC,"Please note that it has come to my attention that GTK 3.20+ has introduced changes as to how CSS must be used, meaning that aspects of the window may be rendered badly for you. Revision 1714 is a *partial* fix, but additional fixes will probably be needed in the external css files to get everything perfect... at least till Gnome decide to change everything all over again!"
1658626,2017-02-01 13:07:10 UTC,For more detail: https://code.launchpad.net/~laney/terminator/gtk3.20-embedded-css/+merge/316094
1658627,2017-01-24 01:49:19 UTC,"I've never seen this crop up, and honestly you don't give much to go on. A workaround is to turn off the DBus option in Preferences. That should prevent a previous terminal that hasn't exited from blocking a new one. (I'm assuming the reason you can't launch a new terminal is because the old one hasn't exited, but is stuck before (or whilst) closing the DBus session, and the new terminal send a message to the session that doesn't get acted on.)"
1658627,2017-01-25 21:23:31 UTC,"(Oh wait, the title says FC25, which ships 0.98 (gtk2).)"
1658627,2017-03-04 12:10:32 UTC,"Yeah, that was an unfortunate regression. I fixed something for X11 which then broke under wayland. Once you have the fix (which looks to already be pushed) redo the command and attach (please don't emdeb in comment) the -d output."
1658627,2017-03-03 09:28:34 UTC,dupe of https://bodhi.fedoraproject.org/updates/FEDORA-2017-3e11859cc5
1658627,2017-03-03 09:08:02 UTC,sorry I completely forgot you.
1658627,2017-02-18 13:59:51 UTC,"OK, but you still haven't provided the -d output. (Launch it from another terminal program, with no terminal instances running.)"
1658627,2017-01-26 08:44:56 UTC,Nah it's mostly gtk3
1658627,2017-03-10 16:05:36 UTC,here is the required attachment :)
1658627,2017-03-10 17:37:01 UTC,"That looks like the output from a second window launch. All that does is request a new window from the first launched window over DBus, then exits."
1658627,2017-01-25 21:21:12 UTC,(Would need to clarify the version number too. Could be a gtk2-only issue.)
1658629,2017-01-23 19:36:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424305"
1658629,2017-06-27 19:30:46 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1658629,2017-06-27 15:56:24 UTC,"Automatically discovered version mitaka in description. If this is incorrect, please update the description to include 'nova version: ...'"
1658629,2017-01-29 16:58:10 UTC,"Reviewed:  https://review.openstack.org/424305
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b2a4fcf84633413c322afb4f2c8066358b943d6b
Submitter: Jenkins
Branch:    master"
1658629,2017-01-23 18:41:18 UTC,I can also confirm that changing the prims check like to:
1658629,2017-03-08 17:31:17 UTC,The merged code indicates that it was a partial fix - any update on what is left?
1658629,2017-01-23 18:02:02 UTC,I can confirm that this does indeed appear to be the case in master (as of 20170123): The compute_node in a single node devstack is updated every 61 seconds.
1658629,2017-03-08 18:43:11 UTC,There's some discussion of the other issues in this email thread: http://lists.openstack.org/pipermail/openstack-dev/2017-January/110953.html
1658630,2017-01-23 10:23:50 UTC,"Fuel QA team is responsible for the ""fuel devops"" framework."
1658630,2017-02-27 09:55:02 UTC,"Reviewed:  https://review.openstack.org/436136
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=9d9b495c5b9ced42a69446d0bf18612d7eb43315
Submitter: Jenkins
Branch:    master"
1658630,2017-02-22 13:55:37 UTC,Please take a look https://bugs.launchpad.net/fuel/+bug/1585261
1658630,2017-01-23 14:31:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424147"
1658630,2017-01-24 13:54:52 UTC,The option should be extended to use YAML as a default output format:
1658630,2017-01-24 13:52:06 UTC,"Reviewed:  https://review.openstack.org/424147
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=f774496e5d8a74ef5a1c7de581e6d32473b38887
Submitter: Jenkins
Branch:    master"
1658630,2017-01-24 13:48:11 UTC,"Matthew: merged as-is to unblock you, but the options should be more user-friendly, let's fix it in next patches."
1658630,2017-02-20 18:38:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/436136"
1658632,2017-04-14 21:09:50 UTC,apport information
1658632,2017-04-14 21:15:26 UTC,"Hello guys,"
1658632,2017-04-14 21:10:00 UTC,apport information
1658632,2017-04-14 21:09:58 UTC,apport information
1658632,2017-04-14 21:09:57 UTC,apport information
1658632,2017-04-14 21:09:55 UTC,apport information
1658632,2017-04-14 21:09:53 UTC,apport information
1658632,2017-04-14 21:09:52 UTC,apport information
1658632,2017-04-14 21:09:49 UTC,apport information
1658632,2017-04-14 21:19:22 UTC,"Since the last updates, the UI doesn't crash anymore. However, I still have the following errors in dmesg:"
1658632,2017-04-14 21:09:43 UTC,apport information
1658632,2017-04-14 21:09:41 UTC,apport information
1658632,2017-04-14 21:09:40 UTC,apport information
1658632,2017-04-14 21:09:38 UTC,apport information
1658632,2017-04-14 21:09:37 UTC,apport information
1658632,2017-04-14 21:09:35 UTC,apport information
1658632,2017-01-24 15:14:12 UTC,"Also, do you happen to have an external monitor, or only the built in one?"
1658632,2017-01-24 15:12:43 UTC,"Would it be possible for you to test this latest kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1658632,2017-01-23 10:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1658632,2017-01-23 17:59:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1658632,2017-04-14 21:09:47 UTC,apport information
1658634,2020-08-12 11:58:24 UTC,"Fixed in commit 3ef0c573d37b (""console: fix console resize"", 2017-01-31), released in v2.9.0."
1658634,2017-01-31 15:50:31 UTC,"Only skip surface reallocation in case the old surface was created using
qemu_alloc_display (via qemu_create_displaysurface) too, otherwise we
might end up with a DisplaySurface with the wrong backing storage."
1658634,2017-01-24 22:59:50 UTC,It works well on my side with the patch. Thanks!
1658634,2017-01-24 11:20:52 UTC,"On 01/24/17 11:37, elmarco wrote:

> Hi
>
> On Tue, Jan 24, 2017 at 2:31 PM Gerd Hoffmann <email address hidden>
> wrote:
>
>> Only skip surface reallocation in case the old surface was created using
>> qemu_alloc_display (via qemu_create_displaysurface) too, otherwise we
>> might end up with a DisplaySurface with the wrong backing storage.
>>
>> Cc: <email address hidden>
>> Cc: Marc-André Lureau <email address hidden>
>> Fixes: cd958edb1fae85d0c7d1e1acbff82d22724e8d64
>> Signed-off-by: Gerd Hoffmann <email address hidden>
>> ---
>>  ui/console.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/ui/console.c b/ui/console.c
>> index b9575f2..67c65b7 100644
>> --- a/ui/console.c
>> +++ b/ui/console.c
>> @@ -2121,7 +2121,7 @@ void qemu_console_resize(QemuConsole *s, int width,
>> int height)
>>
>>      assert(s->console_type == GRAPHIC_CONSOLE);
>>
>> -    if (s->surface &&
>> +    if (s->surface && (surface->flags & QEMU_ALLOCATED_FLAG) &&
>>          pixman_image_get_width(s->surface->image) == width &&
>>          pixman_image_get_height(s->surface->image) == height) {
>>          return;
>>
>
> You are missing the 's->' !
>
> with that,
> Reviewed-by: Marc-André Lureau <email address hidden>
"
1658634,2017-01-24 11:10:39 UTC,"Only skip surface reallocation in case the old surface was created using
qemu_alloc_display (via qemu_create_displaysurface) too, otherwise we
might end up with a DisplaySurface with the wrong backing storage."
1658634,2017-01-24 12:18:46 UTC,"On 01/24/17 12:10, Gerd Hoffmann wrote:

> Only skip surface reallocation in case the old surface was created using
> qemu_alloc_display (via qemu_create_displaysurface) too, otherwise we
> might end up with a DisplaySurface with the wrong backing storage.
>
> Cc: <email address hidden>
> Fixes: cd958edb1fae85d0c7d1e1acbff82d22724e8d64
> Signed-off-by: Gerd Hoffmann <email address hidden>
> Reviewed-by: Marc-André Lureau <email address hidden>
> ---
>  ui/console.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ui/console.c b/ui/console.c
> index b9575f2..d573351 100644
> --- a/ui/console.c
> +++ b/ui/console.c
> @@ -2121,7 +2121,7 @@ void qemu_console_resize(QemuConsole *s, int width, int height)
>
>      assert(s->console_type == GRAPHIC_CONSOLE);
>
> -    if (s->surface &&
> +    if (s->surface && (s->surface->flags & QEMU_ALLOCATED_FLAG) &&
>          pixman_image_get_width(s->surface->image) == width &&
>          pixman_image_get_height(s->surface->image) == height) {
>          return;
>
"
1658634,2017-01-24 10:37:26 UTC,Hi
1658634,2017-01-24 10:20:17 UTC,"Only skip surface reallocation in case the old surface was created using
qemu_alloc_display (via qemu_create_displaysurface) too, otherwise we
might end up with a DisplaySurface with the wrong backing storage."
1658634,2017-01-24 09:12:24 UTC,Added Marc-André and Gerd to the CC list.
1658634,2017-01-24 09:09:08 UTC,"For reference, this is my script:"
1658634,2017-01-24 09:06:56 UTC,"I downloaded ""ubuntu-16.04.1-desktop-amd64.iso"" (MD5: 17643c29e3c4609818f26becf76d29a3), and I can reproduce the issue -- the grub2 display is corrupt. (I didn't even look further than that.) I also confirm that it works fine with the same firmware, but using QEMU 2.7."
1658634,2017-01-24 04:04:51 UTC,"Splash screen and UEFI shell were displayed correctly. Grub2 menu and
Ubuntu login screen also appeared, however the display didn't seem right. I
got very blurry output."
1658634,2017-01-24 11:10:25 UTC,"> > -    if (s->surface &&
> > +    if (s->surface && (surface->flags & QEMU_ALLOCATED_FLAG) &&
> >          pixman_image_get_width(s->surface->image) == width &&
> >          pixman_image_get_height(s->surface->image) == height) {
> >          return;
> >
>
> You are missing the 's->' !
"
1658634,2017-01-23 12:50:39 UTC,(1) What phase of the guest do you get invalid video output in? Do you see the TianoCore splash screen? Does the grub2 menu appear?
1658636,2017-01-23 17:23:59 UTC,"Question to the bug reporter: which plugin and configurations where you using?, ML2? ?, are you using DVR?"
1658636,2017-01-23 17:38:58 UTC,Are you sure this isn't a typo?  The argument to python-neutronclient is 'allowed-address-pair' without the 's' on the end.
1658636,2017-03-07 10:25:40 UTC,"I had tried to reproduce the bug on 8.3.1 neutron(mitaka) with ML2 plugin, and it is working."
1658636,2017-05-07 04:17:22 UTC,[Expired for neutron because there has been no activity for 60 days.]
1658636,2018-08-16 12:49:00 UTC,"I met this issue on Ocata version，My openstack environment use provider network, openvswitch, vlan ,the issue appeared when I disable security group, and disappeared when I enable security group."
1658641,2017-07-20 21:16:24 UTC,"It sounds like a possible solution would be to enhance the ``keystone-manage`` tool. What we could do is add a path to it that accepts a user_id, check to make sure it doesn't exist in the identity backend, and then forcibly removes any role assignments that user has."
1658641,2017-07-26 20:44:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/487579"
1658641,2018-02-08 22:59:41 UTC,We're probably going to have to cut queens-rc1 without this fix. If we get a patch landed we can backport and cut an rc2.
1658641,2020-01-15 08:42:52 UTC,"Can someone have another look on this? It is still a problem in stein. While 'mapping_purge' can remove a stale user, it does not remove the role assignments. And; there is no other way to remove role assignments from a stale user, than directly in the database.."
1658641,2018-02-12 20:51:13 UTC,Played around for a bit.
1658641,2018-02-13 03:37:47 UTC,"Sounds like it is a valid return code and message and an error on the part of the client code, then.  Should we refile the bug against OSC?"
1658641,2018-02-13 19:04:36 UTC,"Removing this as a queens rc target based on comment number #18. Kristi, thanks for recreating this."
1658641,2019-03-19 16:38:23 UTC,"Change abandoned by Kristi Nikolla (<email address hidden>) on branch: master
Review: https://review.openstack.org/487579
Reason: Won't have time to work on this."
1658641,2018-02-09 20:45:25 UTC,Thinking about this a bit more and it seems we have two different options when using the mapping purge.
1658641,2017-06-30 22:41:18 UTC,"Thanks for sharing your experiences and tests, @akaris. This is very useful!
Especially the pointers on how to delete the entries manually from the databse and its effect."
1658641,2017-06-30 14:44:46 UTC,The same issue by the way happens when a user's membership is changed and thus removes him from the domain:
1658641,2017-06-30 14:45:10 UTC,I deleted the user to test the mapping_purge ...
1658641,2017-06-30 15:32:20 UTC,"I tested this again against OSP 11 (Ocata):
~~~
[stack@undercloud-8 ~]$ openstack user list --domain redhat
+------------------------------------------------------------------+----------+

| ID                                                               | Name     |


+------------------------------------------------------------------+----------+

| 80fc5502450b25ec0691dccc27307efc65ebb5c7f54db131e120f4a8bb6cecf0 | svc-ldap |
| 3edee38198325e08fd8795862575196802ac7572bc1b00d0f0dade56d674a7e3 | akaris   |
| f612704506d90104aebdc0989f6120a8db166ad0e80b9990262ea32487209d31 | nalmond  |
| 6992dec6afa26e9faac16e0f56748a6b492ada373c21eaad919af87cc89a831e | test     |


+------------------------------------------------------------------+----------+
[stack@undercloud-8 ~]$ openstack role add --project demo --user 6992dec6afa26e9faac16e0f56748a6b492ada373c21eaad919af87cc89a831e _member_
[stack@undercloud-8 ~]$ openstack role assignment list --names
+---------------+------------------------------------+-------+-----------------+------------+-----------+

| Role          | User                               | Group | Project         | Domain     | Inherited |


+---------------+------------------------------------+-------+-----------------+------------+-----------+

| admin         | nova@Default                       |       | service@Default |            | False     |
| admin         | aodh@Default                       |       | service@Default |            | False     |
| admin         | glance@Default                     |       | service@Default |            | False     |
| admin         | heat-cfn@Default                   |       | service@Default |            | False     |
| admin         | swift@Default                      |       | service@Default |            | False     |
| _member_      | test@redhat                        |       | demo@Default    |            | False     |
| ResellerAdmin | ceilometer@Default                 |       | service@Default |            | False     |
| admin         | ceilometer@Default                 |       | service@Default |            | False     |
| admin         | panko@Default                      |       | service@Default |            | False     |
| admin         | gnocchi@Default                    |       | service@Default |            | False     |
| admin         | heat@Default                       |       | service@Default |            | False     |
| admin         | neutron@Default                    |       | service@Default |            | False     |
| admin         | admin@Default                      |       | admin@Default   |            | False     |
| admin         | placement@Default                  |       | service@Default |            | False     |
| admin         | cinder@Default                     |       | service@Default |            | False     |
| admin         | heat_stack_domain_admin@heat_stack |       |                 | heat_stack | False     |
| admin         | admin@Default                      |       |                 | redhat     | False     |


+---------------+------------------------------------+-------+-----------------+------------+-----------+
[stack@undercloud-8 ~]$ ..."
1658641,2017-01-23 20:35:17 UTC,I did some checking with other keystone developers that are a bit more familiar with keystone+LDAP integration [0]. It sounds like the short answer is that keystone doesn't support inspecting group assignment changes on the LDAP side.
1658641,2017-01-24 11:59:11 UTC,"Thank you Lance, that's very helpful and pretty much what I expected."
1658641,2017-01-24 16:57:14 UTC,"I did some digging and this is what I found. The `keystone-manage mapping_populate` command is simply a wrapper that makes a call to list all users [0], since the responsibility to map local and public ID falls within the various layers of the identity API. `keystone-manage` only passes the domain ID of the domain to populate, which in turn is passed to the identity APIs list users method [1]. This is all pretty straight forward, and before we exit that method, we have a list of references [2] from LDAP (in the multi-domain case). This is passed to _set_domain_id_and_mapping() [3], which handles parsing each entity in the list. At the same time, it looks up all current id_mappings (one should exist for every user) and compares them to the list of existing entities. If a reference, recently pulled from LDAP, matches a mapping from the id_mapping table, we pull the public id from the id_mapping and update the reference [4]. At this point, any entity that has already been mapped has its corresponding public ID. Then we make another pass through the list to populate any public ID for entities that haven't been mapped (i.e. these would be the ones that you just explicitly removed using the `keystone-manage mapping_purge`` command) [5][6]. If there isn't a public ID in the entity, we will go ahead and create one from attributes [7]."
1658641,2017-06-30 14:43:12 UTC,"Hi,"
1658641,2017-01-30 13:13:42 UTC,"Didn't realize how unreadable launchpad made the trace, so here's a paste[1] of the `--debug` output instead. Again, everything is normal up to this point (see steps), so I chose to leave that out for now."
1658641,2017-06-30 14:44:27 UTC,Note that I recreated user test in AD:
1658641,2017-01-30 13:04:54 UTC,"Great explaination, and thanks for looking into this."
1658641,2017-06-30 14:43:38 UTC,"Looking at the database, the id_mapping table and the assignment table seem to be the only ones holding references to this user (given the test which I ran, meaning that I assigned a role to the user)
~~~
[root@overcloud-controller-0 domains]# mysql keystone -e 'show tables;' | awk '{print $1}' | while read t;do echo ""XXXXX $t XXXXX"";  mysql keystone -e ""select * from $t \G"" | grep f3f3e1b1c01c79299154f85f0821ceb0f7c149de8d9836f86eceaaa38e9f27c2 -C5 ; done
XXXXX Tables_in_keystone XXXXX
ERROR 1146 (42S02) at line 1: Table 'keystone.Tables_in_keystone' doesn't exist
XXXXX access_token XXXXX
XXXXX assignment XXXXX
target_id: dfc01178c51b4688be78188b5e8c9581
  role_id: 9fe2ff9ee4384b1894a90878d3e92bab
inherited: 0
*************************** 22. row ***************************
     type: UserProject
 actor_id: f3f3e1b1c01c79299154f85f0821ceb0f7c149de8d9836f86eceaaa38e9f27c2
target_id: 1c3e304811d8457a871a6c67f6f63a75
  role_id: 9fe2ff9ee4384b1894a90878d3e92bab
inherited: 0
*************************** 23. row ***************************
     type: UserProject
XXXXX config_register XXXXX
XXXXX consumer XXXXX
XXXXX credential XXXXX
XXXXX domain XXXXX
XXXXX endpoint XXXXX
XXXXX endpoint_group XXXXX
XXXXX federated_user XXXXX
XXXXX federation_protocol XXXXX
XXXXX group XXXXX
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'group' at line 1
XXXXX id_mapping XXXXX
  public_id: 853a331554ea0fb6e938f39256beb9f8096625c29f34bc8d88990b4198205f90
  domain_id: 210bdf7974a14693843ec7f9b1956105
   local_id: svc-ldap
entity_type: user
*************************** 4. row ***************************
  public_id: f3f3e1b1c01c79299154f85f0821ceb0f7c149de8d9836f86eceaaa38e9f27c2
  domain_id: 210bdf7974a14693843ec7f9b1956105
   local_id: test
entity_type: user
XXXXX identity_provider XXXXX
XXXXX idp_remote_ids XXXXX
XXXXX implied_role XXXXX
XXXXX local_user XXXXX
XXXXX mapping XXXXX
XXXXX migrate_version XXXXX
XXXXX password XXXXX
XXXXX policy XXXXX
XXXXX policy_association XXXXX
XXXXX project XXXXX
XXXXX project_endpoint XXXXX
XXXXX project_endpoint_group XXXXX
XXXXX region XXXXX
XXXXX request_token XXXXX
XXXXX revocation_event XXXXX
XXXXX role XXXXX
XXXXX sensitive_config XXXXX
XXXXX service XXXXX
XXXXX service_provider XXXXX
XXXXX token XXXXX
XXXXX trust XXXXX
XXXXX trust_role XXXXX
XXXXX user XXXXX
XXXXX user_group_membership XXXXX
XXXXX whitelisted_config XXXXX
~~~"
1658641,2017-02-07 18:29:28 UTC,"based on the config you have in the description, I believe a user's local_id would be that user's sAMAccountName."
1658655,2017-01-26 17:28:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/425801"
1658655,2017-02-13 16:12:11 UTC,"Reviewed:  https://review.openstack.org/425801
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-ldap/commit/?id=7cf2e0f36ee174796f15d6e0cbcbfdaef55d4fe3
Submitter: Jenkins
Branch:    master"
1658665,2017-02-04 20:02:54 UTC,"StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()"
1658665,2017-02-04 20:03:01 UTC,Thank you for your report!
1658672,2017-01-23 20:37:14 UTC,"bzr8255:
Don't know if this is related, but the attached save game shows some carriers which stuck at the door of the port. One could see them walking but they never come out whereas other carriers go in an out. The debug windows shows a big list of carriers. If this is another bug, please let me know."
1658672,2017-01-24 07:06:36 UTC,Forget my last comment :-)
1658672,2019-09-17 07:03:23 UTC,Migrated to https://github.com/widelands/widelands/issues/3184
1658675,2017-02-27 16:28:59 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1658675,2017-01-23 13:27:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424106"
1658675,2017-01-30 09:29:11 UTC,"Reviewed:  https://review.openstack.org/424106
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=7cc699fbd056b1536b6d5f60d73c1fdd25faeeb8
Submitter: Jenkins
Branch:    master"
1658677,2017-01-23 12:55:46 UTC,"In the case of OSCI, we've had to resort to deploying the remote Jenkins slave applications by-hand, as has been described by others with nearly identical use cases."
1658677,2017-01-23 13:00:24 UTC,"While this impacts s390x, arm64, ppc64el work, it is not specifically an architecture issue.  It is reproducible in an all-amd64 deployment."
1658677,2017-01-23 13:14:45 UTC,"Marking High (not Critical) for OpenStack CI, as we've manually worked around this for one specific use case, but anticipate hitting it again as with additional/upcoming work."
1658677,2017-01-31 01:15:18 UTC,"As there is a workaround, we'll aim to address it in Juju 2.2."
1658677,2017-01-31 02:41:55 UTC,"Is it that you directly added a floating IP and Juju is now unaware of the public address? I believe on other clouds (eg AWS) when the controller has both a public and private then the agents try to connect to both.
Does ""juju show-machine"" not show both addresses for the controller? I would expect ""juju status"" itself to start failing if we weren't ever offering the public address. At one point we had ""use-floating-ip=true"" though I believe that assigned a floating IP to every instanc, which probably isn't what you want, but we should be aware of floating IP if they have been added."
1658677,2017-01-31 15:01:10 UTC,"Indeed, use-floating-ip is not desired in this and most of our cases, as it is generally just the controller, plus one or two applications that need to be addressable outside the tenant network."
1658677,2017-06-01 02:29:28 UTC,"I do believe that the normal use case for manually provisioned machines was to have them in the same space as the model, using the Juju concept of space."
1658679,2017-02-24 19:38:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658680,2017-01-23 13:15:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424104"
1658680,2018-12-07 14:48:19 UTC,"Change abandoned by Antoni Segura Puimedon (<email address hidden>) on branch: master
Review: https://review.openstack.org/424104
Reason: Lack of activity"
1658690,2017-01-24 02:33:26 UTC,I'll have to see if I can set up a test environment for this. Just curious if other GTK# apps like Banshee have similar scaling issues?
1658690,2020-07-16 18:38:23 UTC,"There is in-progress work on resurrecting the port to GtkSharp 3 - https://github.com/PintaProject/Pinta/tree/gtk3-v2, which should address these issues."
1658690,2020-07-16 18:13:36 UTC,Switching to https://www.photopea.com/
1658690,2020-07-16 18:13:21 UTC,"I have same problem ubuntu 20.10, its 2020"
1658690,2020-01-15 18:01:37 UTC,"I have same problem ubuntu 18.04 y5070 , its 2020"
1658690,2017-01-24 08:06:34 UTC,"I went on to install Banshee on my machine just to check how it looks, and it looks fine, but I don't think this is a good comparison example as there are no numerical text boxes and such... Icons are similarly too small like in your application."
1658690,2018-06-16 13:41:31 UTC,"""You can workaround this issue by selecting Override high DPI scaling behavior. Scaling performed by System (Enhanced) under the Settings section of the Compatibility tab of the Pinta.exe Properties."""
1658690,2018-01-11 09:19:02 UTC,"So can you update the gtk library so it scales correctly?
I can't find any settings for pinta whee I can perform scaling."
1658690,2017-08-05 22:33:32 UTC,You can workaround this issue by selecting Override high DPI scaling behavior. Scaling performed by System (Enhanced) under the Settings section of the Compatibility tab of the Pinta.exe Properties.
1658690,2017-01-27 01:12:24 UTC,"It looks like Pinta is using GTK+ 2, which at least according to https://wiki.archlinux.org/index.php/HiDPI#GTK.2B_2 does not support scaling UI components."
1658690,2019-02-24 21:10:21 UTC,It's 2019 and highdpi displays are still a problem. Ubuntu 18. Lenovo yoga 920
1658695,2017-06-12 05:54:16 UTC,Same here. I am so far working with only one display because of this. Let me know if I can help in any way.
1658698,2020-04-13 11:53:19 UTC,Hi - thanks for reporting this bug. Closing this issue as part of the bug migration to GitLab (issue still exists).
1658698,2017-01-25 17:53:08 UTC,"The drawing size (physical length units, like mm) on input is the same on output to EMF, no matter what the input format was.  Output resolution to EMF is always 1200 dpi.  If the input drawing was also 1200 dpi then there will be no change in the size of the drawing in pixels on export to EMF, but if it was some other value, then the output EMF drawing size in pixels will be different than the input size in pixels."
1658698,2017-01-25 08:20:45 UTC,"No, bitmaps wouldn't be the better format, because the zom size is variable... therefore the 70x100 is perfect. I understand the dpi scaling, but nevertheless the output has other pixel dimensions as the inout, hasn't it?"
1658698,2017-01-24 19:18:38 UTC,"One other point.  Inkscape creates EMF output files with a ""device"" of 1200 dpi.  For comparison, the file you created is 94 dpi, which is probably your screen resolution as seen by GDI.  The lower resolution is fine for your application, but in general the loss of resolution for a typical letter size drawing would result in ""inkscape open EMF, inkscape save EMF"" not exactly recreating the original file.  This is due to rounding errors going into and out of SVG.  To approximate the floating point positions in an arbitrary SVG, the EMF needs a high resolution.  Ie, point placement at 96 dpi is only accurate to about 1% per inch, but it is good to .08% per inch at 1200 dpi, a roughly 100 fold improvement.  That resolution is sufficient for typical drawings, as in a presentation.  If the EMF was to hold engineering drawings even higher resolutions would be required - and at present that isn't supported either."
1658698,2017-01-24 07:56:04 UTC,using larger files is not the solution because the results are much larger emf files (vector isn't vector). The results files are uses inside animations (~100 different icons) and the cpu usage rises from 1% up to 35% with larger files that still are painted in small dimensions...
1658698,2017-01-24 07:37:29 UTC,hmm.. okay. But the emf pixel size is also differs from the defined one inside svg. Tus I wrote my own image converter. A simple one. Therefore I draw the svg using an svg lib to my graphic device and after that I generate the emf using the WinApi. Attached the result that offers the same pixel size as defined in the inkscape svg. btw why is emf+ not supported... and believe me: I don't like emfs and I'm happy that even MS does not like them any more (yippie virus ;-) ). But right now there are cases I have to deal with them :-( And the emfs genrated by the libUemf of inkscape looks much better. Because of that I would prefer these ones...
1658698,2017-01-23 20:40:04 UTC,"Sorry, typo in the preceding, that should have been ""two passes"" rather than ""one pass"".  The small de novo test file was stable in EMF->EMF copies from the 1st copy onwards."
1658698,2017-01-23 20:37:41 UTC,"I'm not sure this is a bug, it is probably a limitation in the EMF representation of the drawing, and differences in how EMF does things versus how SVG does.  EMF coordinates are integers placed on a grid defined by the drawing, not floats as in SVG."
1658698,2017-01-23 14:54:24 UTC,"confirmed on Windows 10, Inkscape 0.92+devel 15423"
1658698,2017-01-24 18:48:54 UTC,"I didn't understand what you meant by ""vector isn't vector""."
1658698,2017-01-23 14:57:09 UTC,"possibly different from Bug 1405292 since this bug was apparently fixed in rev 15235
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15235"
1658705,2017-01-23 15:54:26 UTC,"Click the menu icon in the top right of the app (next to the Save button).
Select View>Side Panel"
1658705,2017-01-23 18:16:44 UTC,"Thank you Jeremy, that worked."
1658711,2017-01-31 10:22:09 UTC,MOS 9.2 release notes: https://review.fuel-infra.org/#/c/30270.
1658711,2017-01-23 15:34:04 UTC,Fix for this bug in fuel-infra https://review.fuel-infra.org/#/c/30019/
1658711,2017-01-30 13:07:02 UTC,I'd suggest we add this as known issue to release notes:
1658711,2017-01-23 15:38:13 UTC,"We don't see such behavior for just security groups, we were able two spawn quickly >100 VMs on a single host with more than 60k+ flows in total."
1658724,2017-01-23 16:54:05 UTC,"AFAICT the translation as 'Maskerpad' was added in 2008 (bug #219475):
https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/6728"
1658724,2017-01-23 16:38:36 UTC,"Probably same translation issue as reported earlier in
* Bug #1450468 “Can't find the clip set under object”
  https://bugs.launchpad.net/inkscape/+bug/1450468"
1658734,2021-02-03 15:36:23 UTC,"cloud-init uses this codepath in the EC2, GCE and OpenStack datasources."
1658734,2017-01-23 16:57:14 UTC,Forgot to add to the description that the additional random name queried could make it particularly problematic for an IDS because you cannot easily whitelist the random name.
1658734,2017-01-27 15:38:21 UTC,"Urgency of this is much lower than we originally thought, so it will likely be longer before I propose a patch."
1658734,2017-07-06 09:18:34 UTC,Description of problem:
1658734,2017-01-24 14:25:02 UTC,I've marked this confirmed and wishlist.  There is some background on why this code is doing what it is doing at https://irclogs.ubuntu.com/2017/01/23/%23cloud-init.html#t17:01
1658745,2017-01-23 21:10:07 UTC,Can you include some logs from both zookeeper and kafka in a devstack with this failure?
1658745,2017-01-23 22:32:40 UTC,"@Ryan, I have attached the logs below."
1658748,2017-01-23 17:32:03 UTC,"TripleO seems to be hitting this bug, see https://bugzilla.redhat.com/show_bug.cgi?id=1414976"
1658750,2017-01-23 17:46:39 UTC,"Note that while there is no DOMAINSEARCH, DNSDOMAIN needs to translate into something (domain or search directive), and only one of those will be honored by the resolver (they overwrite each other, per the specification)."
1658750,2017-03-29 17:02:23 UTC,"This would appear to be an issue in d/net-interface-handler, which currently ignores the DNSDOMAIN value."
1658750,2018-06-27 08:48:38 UTC,Revisiting bugs that were triaged but dormant for 6 months I think we have to realize that this wasn't at the top of anyones todo list.
1658753,2017-01-26 22:26:34 UTC,"Reviewed:  https://review.opencontrail.org/28200
Committed: http://github.org/Juniper/contrail-provisioning/commit/76055524ba94690af419420d933ff6eeac79a3b9
Submitter: Zuul (<email address hidden>)
Branch:    R3.1"
1658753,2017-02-01 08:32:46 UTC,"Reviewed:  https://review.opencontrail.org/28201
Committed: http://github.org/Juniper/contrail-provisioning/commit/09fa446d76f34751271d1caefa5352abfd1250ec
Submitter: Zuul (<email address hidden>)
Branch:    R3.1.1.x"
1658753,2017-01-25 22:36:57 UTC,"Review in progress for https://review.opencontrail.org/28201
Submitter: Ignatious Johnson Christopher (<email address hidden>)"
1658753,2017-01-25 22:36:37 UTC,"Review in progress for https://review.opencontrail.org/28200
Submitter: Ignatious Johnson Christopher (<email address hidden>)"
1658753,2017-01-25 22:42:01 UTC,"Workaround:
==========="
1658753,2017-01-25 23:02:19 UTC,"As per dev, the 3.2 scope is not applicable for this bug"
1658754,2017-01-23 17:58:38 UTC,"Attaching GitLab logo SVG file as currently available to the bug report - external links can can get lost, or the SVG source of the linked file might change."
1658754,2017-01-23 18:08:43 UTC,"The fill color of the mask is not 'Unset' - it is 'white', defined by a presentation attribute on the mask definition (the container which holds the <use> reference to the path defining the mask geometry):"
1658754,2017-01-23 18:20:01 UTC,"Thank you, su_v! (it was 'unset' after ungrouping)"
1658754,2017-01-24 15:16:44 UTC,Quoting confirmation from irc (#inkscape-devel):
1658754,2020-01-09 19:19:24 UTC,"Hi, this issue has been reported on GitLab: https://gitlab.com/inkscape/inkscape/issues/635"
1658780,2017-01-23 20:34:12 UTC,"The attachment ""oids.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1658786,2017-01-23 20:34:27 UTC,"The attachment ""mib.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1658789,2017-01-24 14:00:42 UTC,https://github.com/ubuntudesign/developer.ubuntu.com/pull/211
1658794,2017-01-25 16:12:47 UTC,"Sounds good.  I'm fine with low importance, since it obviously took us so long to notice, but be aware that the grafana plugin hits this bug if you aren't using statistics."
1658794,2017-01-25 15:54:28 UTC,"Thanks for the additional data, I will try to test this today. I'm classifying this as low for now, since --merge and --group_by aren't meant to be used together."
1658794,2017-01-24 21:54:41 UTC,Good point.  Yes this is java and vertica.
1658794,2017-01-24 20:40:38 UTC,"I've not had a chance to bring up an environment to check this yet, can you include the result? Also, I presume this was java and vertica, can you confirm?"
1658796,2018-02-28 00:08:20 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu1
1658796,2017-01-25 11:06:08 UTC,"Hmm, I can see this but not when I rm -r .bzr-builddeb. - it doesn't appear to be related to the recent changes (i get the same issue on r929)"
1658796,2017-01-25 13:40:58 UTC,".bzr-builddeb is checked in. I can reproduce the problem by just branching trunk and running make sourcepackage (trusty and xenial, on my host or container). The issue is the conflicting file is checked in and not part of the orig tarball, hence the error."
1658796,2017-01-25 19:21:28 UTC,"I have proposed a branch that moves .bzr-builddeb/default.conf to debian/, which solves this issue and also allows bzr builddeb to work as supposed."
1658797,2017-10-04 21:37:33 UTC,"I believe this issue was addressed by
https://github.com/openstack/charm-swift-proxy/commit/ccaeae4706dc15561dd7fa16c4e4b8fbaa66aec1"
1658804,2017-01-23 22:13:50 UTC,I don't think we need any actual package changes in xenial or yakkety here -- copying to -updates and promoting is probably sufficient.
1658804,2017-01-24 00:58:47 UTC,"I have copied the binaries to -updates and will promote, but per discussion we should also have the test suite enabled in the stable releases as well and this is worth SRUing for."
1658808,2019-09-19 11:55:34 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1658808,2017-01-23 22:32:53 UTC,"Thank you for the quick input on this.  Indeed, there was no subnet.  After I created a subnet, the 'subnet' field for the ipranges CLI was indeed optional as declared.  But I'd say the failure error there should be improved for UX."
1658808,2017-01-23 21:32:52 UTC,"⟫ apt-cache policy maas
maas:
  Installed: 2.1.3+bzr5573-0ubuntu1~16.04.1
  Candidate: 2.1.3+bzr5573-0ubuntu1~16.04.1
  Version table:
 *** 2.1.3+bzr5573-0ubuntu1~16.04.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.1.3+bzr5573-0ubuntu1~16.04.1 500
        500 http://ppa.launchpad.net/maas/stable/ubuntu xenial/main amd64 Packages
     2.0.0~beta3+bzr4941-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages"
1658808,2017-01-23 21:43:44 UTC,Can you provide the output of 'maas session subnets read'? Possible that it is showing because you do not have a subnet created where that IP range would fit.
1658808,2017-01-23 21:38:35 UTC,"FWIW, this appears to be a new behavior, moving from 2.1.2+bzr5555-0ubuntu1~16.04.1 to --> 2.1.3+bzr5573-0ubuntu1~16.04.1."
1658818,2017-01-23 22:19:01 UTC,This appears to be affecting the gate for openstack-ansible currently. It seems to be non-deterministic since we have some patches merging still.
1658818,2017-01-23 22:22:22 UTC,https://github.com/openstack/openstack-ansible-os_gnocchi/blob/095451208f7274a4d5817dfe3fed76552213ac58/tasks/gnocchi_policy_setup.yml#L26
1658818,2017-01-23 22:30:36 UTC,Error log inside the container:
1658825,2017-01-24 06:03:31 UTC,"@danrabbit Can you explain me why you move the issue? wingpanel-indicator-ayatana seemed to work at each point uninstalling it removes all app launchers from wingpanel installing it ads them again. ""Only"" the notifications indicator seems to break all if i install it again"
1658825,2017-01-24 07:28:34 UTC,"Thats the app i tried while i ""lost"" my wingpanel with notification support: https://github.com/standardnotes/desktop/issues/27"
1658836,2017-08-01 07:50:01 UTC,These automated reports aren't helpful.  Please stop.
1658836,2017-08-02 00:36:22 UTC,"Because you cannot access the Error Tracker they may seem like noise to
you, however many people have access to the Error Tracker and to them
this report would be useful. By setting this bug's state to Invalid you
are by default hiding it from everybody which is not helpful."
1658836,2019-07-15 19:55:01 UTC,"This would appear to be a (now resolved) Qt bug, specifically QTBUG-48391[1].  The backtrace here (35 frames of Qt on top of Twinkle's run() method) looks eerily identical to the one in QTBUG-48391 (save for two extra frames at the top in our case).  For the record, the fix[2] seems to have made it in Qt 5.9."
1658836,2019-07-16 06:23:48 UTC,Reassigning to qtdeclarative-opensource-src; I'll let them confirm in which version the fix was introduced.
1658836,2019-07-16 13:58:56 UTC,https://codereview.qt-project.org/c/qt/qtbase/+/188320 says that the fix is included in Qt 5.9.0 and later versions (see the “Included in” button).
1658837,2017-01-25 18:53:19 UTC,This issue is not high if the logout race if fixed.
1658838,2017-01-24 00:33:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1658844,2020-08-30 10:44:59 UTC,"Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'."
1658844,2017-03-29 21:52:40 UTC,Something from the description is confusing me:
1658844,2017-02-17 15:28:17 UTC,"In [1]: import setuptools
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-b6e7bae96787> in <module>()
----> 1 import setuptools"
1658844,2017-01-26 18:46:26 UTC,I believe I figured out the problem.  When spinning up a fresh ubuntu 14.04 vagrant machine and manually installing pip with sudo apt-get install python-pip the dependency pkg_resources is installed with python3-pkg-resources to.  I experience the same results if I use a ubuntu 14.04 image in an oracle VM.  The workaround is to install pip with easy_install via python-setuptools and pip will work.
1658844,2017-01-25 21:03:05 UTC,"The workaround doesn't work for my auto build environments, it would be good if we can get an official fix still."
1658844,2017-01-25 20:49:02 UTC,Found a work-around (https://github.com/pypa/setuptools/issues/937)
1658844,2017-01-25 15:39:52 UTC,Is there a work around for this?
1658844,2017-01-25 20:12:58 UTC,Has anyone figured out a way around this bug? Haven't been able to deploy since.
1658844,2017-01-25 19:59:38 UTC,+1 for experiencing the issue and breaking our builds.
1658844,2017-01-25 18:01:45 UTC,"This issue is breaking our puppet configuration scripts. Breaking pip can lead to some serious problems, I hope this is considered a critical bug."
1658844,2017-01-25 08:53:40 UTC,"I am experiencing the same issue as well. Are there any known workarounds for now, before it's fixed?"
1658844,2017-01-25 00:57:37 UTC,Yes this is also effecting me too and blocking my auto deploy projects across the board.
1658844,2017-01-24 17:33:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658844,2017-01-25 20:30:04 UTC,"This isn't a good workaround for most people I'm sure, but I upgraded to 16.04 which doesn't have the issue. The specific app I'm hitting this bug with is a Python app in a Docker container so it's pretty easy to just rebuild my image against 16.04. I'll be downgrading once this is fixed though."
1658844,2017-01-25 09:06:19 UTC,Same issue here with our Chef builds.
1658847,2017-01-26 06:53:04 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1658856,2017-08-01 15:10:19 UTC,Prioritised because it allows for better problem reports and easier development.  Will require several people to work on it.
1658857,2019-12-10 15:27:25 UTC,Generally recommended at this point to use Telegraf directly.
1658882,2017-01-24 04:58:59 UTC,"Other checksum strings (sha1, sha256) should also be converted if they exist in the request body!"
1658885,2017-04-13 12:04:34 UTC,"In the cinder
https://github.com/openstack/cinder/blob/master/cinder/backup/manager.py#L456-L459
function _attach_device use os-brick create and delete the temporary configuration file
https://github.com/openstack/os-brick/blob/master/os_brick/initiator/connectors/rbd.py#L108-L118"
1658885,2017-04-13 11:50:37 UTC,"Hi,I also met this problem .
https://bugs.launchpad.net/cinder/+bug/1680361"
1658885,2018-01-12 19:02:54 UTC,Unassigning due to no activity for > 6 months.
1658888,2017-09-01 16:16:34 UTC,Unassigning due to no activity for > 6 months.
1658888,2018-04-14 18:53:02 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/424454
Reason: No updates in quite awhile. Feel free to restore and update if this is still needed."
1658888,2017-01-24 06:28:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424454"
1658894,2017-01-24 08:25:29 UTC,"@Eric, Looks like, they never worked with id from prev releases, so its not broken I suppose. Do you think fixing this now would be good idea ?"
1658894,2017-01-24 23:05:21 UTC,"Hey Anusha! I do think it's a good idea to fix, and ideal if we can get it into Ocata, but obviously not the highest priority. I'm personally prioritizing things like datasource driver errors over this because for this there is a simple work around (don't use UUID)."
1658894,2017-01-25 05:13:21 UTC,"@Eric, I agree priority is more important for any broken issues, which worked in prev releases and not working now. This can be postponed for pike I suppose."
1658917,2017-01-24 15:39:56 UTC,"This is a bug in the sysvinit-utils package that provides the 'service' command, not in upstart.  You can still stop the service by running 'stop myservice' instead of 'service myservice stop'."
1658933,2017-02-24 04:57:03 UTC,This also means you lose the window if you minimize it :)
1658935,2017-02-06 09:50:49 UTC,Also blocked by bug 1662126?
1658935,2017-10-31 12:14:24 UTC,This target no longer exists.
1658935,2017-11-03 16:29:53 UTC,Syncing task from Mir.
1658943,2018-02-28 11:43:12 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1658943,2017-01-24 19:16:18 UTC,"And while the current aa-notify behaviour sounds pretty terrible, it at least accurately reflects what might be chewing your poor disk to pieces. Logging all those denials isn't free either. :/"
1658943,2018-02-28 22:06:15 UTC,Reopening for upstream AppArmor - unfortunately nobody worked on this yet :-(
1658943,2017-01-24 12:35:41 UTC,I already have opened separate bugreports for firefox and chromium. Seems as if some problems can not be fixed since the sandbox model of chromium allegedly has a higher complexity than apparmor can deal with and would exceed the capabilities of apparmor.
1658943,2017-01-24 12:07:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1658943,2017-01-24 12:52:26 UTC,"No, the chromium and firefox profiles can be fixed. However the current fixes are not ideal. Basically apparmor currently needs to allow capability sys_admin and a few other dangerous privileges in the base profile."
1658943,2017-01-24 12:08:39 UTC,"Agreed, aa-notify needs some love. Nevertheless, please open separate bugreports for firefox and chromium to get their profiles fixed ;-)"
1658943,2017-01-24 12:09:23 UTC,We need to make it so it can scan ahead and use summary mode if the outstanding number of messages is larger than the threshold when it goes to display the next message.
1658950,2017-09-21 12:45:36 UTC,"For reference, this ""unexpected locale"" problem has been reported to Kali here and has been the basis for my last comment: https://bugs.kali.org/view.php?id=4254"
1658950,2017-09-21 10:11:32 UTC,"Furthermore, when C.UTF-8 is the default locale and the user does nothing, he ends up with the first locale in the list... which is aa_DJ.utf8 on Kali images that have locales-all installed. Not very helpful either."
1658950,2017-01-24 20:20:28 UTC,Is it useful to show the C locale (it's not really a language)?
1658950,2017-01-25 16:15:25 UTC,"I'm here for nearly the same problem that I got when using musl C library and musl locales https://github.com/rilian-la-te/musl-locales which uses uppercase "".UTF-8"" suffixes for the locale names. Despite my very special use case I'm shure we should be generally case independent on locale suffixes. Also, since I was up to propose a patch similar to the one given, I would like to see it applied as well."
1658950,2017-01-25 01:31:13 UTC,Can you explain how the C locale is useful to be shown? I'm wondering if with this change we should filter it out.
1658950,2017-01-26 08:52:50 UTC,C.UTF-8 is a useful fallback when other available locales are unsuitable for user.
1658950,2017-01-24 21:13:13 UTC,If it wasn't useful for me I wouldn't file the bug.
1658952,2017-03-10 08:30:02 UTC,"Verified on 9.2 mu1 updates.
Before we have errors:
root@node-3:~# puppet apply /etc/puppet/modules/openstack_tasks/examples/openstack-network/agents/metadata.pp
Notice: Scope(Class[Openstack_tasks::Openstack_network::Agents::Metadata]): MODULAR: openstack_network/agents/metadata.pp
Error: Could not find resource 'Service[neutron-ovs-metadata]' for relationship from 'Notify[neutron.conf has been changed, going to restart neutron metadata]' on node node-3.test.domain.local
Error: Could not find resource 'Service[neutron-ovs-metadata]' for relationship from 'Notify[neutron.conf has been changed, going to restart neutron metadata]' on node node-3.test.domain.local"
1658952,2017-03-03 12:39:53 UTC,"Reviewed:  https://review.openstack.org/425649
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=15be3f5f130e81b31b6132ab2835ce7d4906cc18
Submitter: Jenkins
Branch:    stable/newton"
1658952,2017-02-27 16:28:56 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1658952,2017-02-06 17:10:37 UTC,"Reviewed:  https://review.openstack.org/425055
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=418b09fc1f9b43f78ff7b40ae31e70784a656524
Submitter: Jenkins
Branch:    master"
1658952,2017-03-07 16:51:41 UTC,"Reviewed:  https://review.openstack.org/425648
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=94a6a10423067051ff3d509774a66aa0ce7303f8
Submitter: Jenkins
Branch:    stable/mitaka"
1658952,2017-02-02 14:04:12 UTC,"Related fix proposed to branch: stable/9.2
Change author: Mariia Zlatkova <email address hidden>
Review: https://review.fuel-infra.org/30423"
1658952,2017-02-02 13:55:35 UTC,"Reviewed: https://review.fuel-infra.org/30303
Submitter: Olena Logvinova <email address hidden>
Branch: master"
1658952,2017-01-26 12:05:01 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/425649"
1658952,2017-01-26 12:04:44 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/425648"
1658952,2017-01-25 11:41:44 UTC,fixed by https://review.openstack.org/425055
1658952,2017-01-25 10:39:38 UTC,Related-bug: https://bugs.launchpad.net/fuel/+bug/1613724
1658952,2017-02-02 14:07:54 UTC,"Reviewed: https://review.fuel-infra.org/30423
Submitter: Mariia Zlatkova <email address hidden>
Branch: stable/9.2"
1658955,2017-01-24 13:09:03 UTC,"Fix proposed to branch: master
Change author: Mykyta Karpin <email address hidden>
Review: https://review.fuel-infra.org/30093"
1658955,2017-01-24 13:58:23 UTC,"Reviewed: https://review.fuel-infra.org/30093
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1658968,2017-01-24 10:59:52 UTC,Default Comment by Bridge
1658968,2017-01-24 10:59:53 UTC,Default Comment by Bridge
1658968,2017-01-30 17:37:27 UTC,"As this is ""for our awareness"", marking as incomplete."
1658968,2017-11-20 09:10:30 UTC,"------- Comment From <email address hidden> 2017-11-20 04:01 EDT-------
*** This bug has been marked as a duplicate of bug 142747 ***"
1658968,2017-11-20 09:44:51 UTC,(IBM Bugzilla duplicate)
1658968,2017-01-24 10:59:40 UTC,Default Comment by Bridge
1658968,2017-01-24 10:59:55 UTC,Default Comment by Bridge
1658970,2017-01-24 11:07:01 UTC,Sort of related is https://bugs.launchpad.net/inkscape/+bug/1658971
1658970,2017-01-24 13:34:08 UTC,"All document properties are managed via templates, not preferences - they are specific to the drawing task (i.e. the file). You can create a custom user default template, and any number of more specific templates for new files with the preferred document properties (specific to the purpose of the template)."
1658970,2017-01-24 14:50:24 UTC,"Actually, there is a section in the preferences file (created by the preferences skeleton) which defines minimal defaults for a basic document template - IIRC it is used e.g. when importing a foreign vector file format (like PDF), or SVG files without editor metadata for Inkscape:"
1658971,2017-01-24 13:27:33 UTC,"Variation of
* Bug #1654383 “Easy UI method to reset/manage preferences”
  https://bugs.launchpad.net/inkscape/+bug/1654383"
1658971,2020-09-15 09:33:23 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1658974,2017-01-24 16:25:41 UTC,I'll investigate this.
1658974,2017-01-26 16:13:56 UTC,"Confirmed
http://paste.openstack.org/show/596613/"
1658974,2017-01-30 06:34:28 UTC,"Hi,"
1658981,2017-01-30 14:54:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/426791"
1658981,2017-02-03 11:37:20 UTC,"Change abandoned by Sergey Vasilenko (<email address hidden>) on branch: master
Review: https://review.openstack.org/426791
Reason: due https://review.openstack.org/#/c/427123/"
1658981,2017-02-06 17:07:16 UTC,"Reviewed:  https://review.openstack.org/427123
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=6fde41c44af5ce785053fdf40eddad65a1a1bff4
Submitter: Jenkins
Branch:    master"
1658981,2017-02-07 10:11:09 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430173"
1658981,2017-02-07 10:11:29 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/430174"
1658981,2017-02-27 16:28:49 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1658981,2017-05-11 10:02:15 UTC,"Reviewed:  https://review.openstack.org/430174
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=a848384706cdf69e7241ef4f51c9e2534805f586
Submitter: Jenkins
Branch:    stable/mitaka"
1658981,2017-05-11 10:22:32 UTC,"Reviewed:  https://review.openstack.org/430173
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=dedeaa789c78f8f4a9282e87210468a90eb09b37
Submitter: Jenkins
Branch:    stable/newton"
1658986,2017-01-25 09:24:29 UTC,Another failure: https://ci.fuel-infra.org/job/10.0-community.main.ubuntu.bvt_2/1120/
1658989,2019-12-18 17:11:02 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/mitaka
Review: https://review.opendev.org/424643
Reason: This repo is retired now, no further work will get merged."
1658989,2019-12-18 17:20:48 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/424644
Reason: This repo is retired now, no further work will get merged."
1658990,2017-01-24 14:48:07 UTC,Note that power_parameters are *not* required if one specifies the 'manual' power type - however there is still room to improve the documentation here
1658990,2017-01-24 14:57:42 UTC,"For future travelers, the power_types_* parameters for the ipmi type can be found here:"
1658990,2019-09-19 11:55:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1658990,2017-01-24 13:01:39 UTC,"Granted, one could say that it's understood that an ipmi power type would need ipmi power parameters.  This is just a scratch, and a UX improvement opportunity."
1658999,2017-01-26 20:27:19 UTC,"So, those patches do not need to be reverted. The actual panic was likely something other than i915_bpo related."
1658999,2017-02-06 03:43:19 UTC,"Tried XPS 15 9550 with kernel 4.4.0-62.83,
cannot see the kernel panic with projector Optoma EP7155 (using HDMI)"
1658999,2017-01-26 13:48:52 UTC,I had Mark test a kernel which jsalisbury built that reverted the following commits:
1658999,2017-01-24 13:43:35 UTC,"Do we know the last working kernel, so we can ""bisect""?"
1658999,2017-01-25 10:33:17 UTC,"I took the xps15 from tai. The kernel is already upgraded to 4.4.0-62.
I tested it with PHILIPS 288PL6 4K monitor and cannot reproduce the issue. Connected the monitor via HDMI and Type-C (to HDMI) ports and both works well. All display modes are available. Checked dmesg and /var/log/syslog, there is no similar warning or kernel panics messages."
1658999,2017-01-25 09:17:37 UTC,"This issue could not reproduce with an AOC E2460SW Widescreen (24"" 1920 x 1080 16:9)."
1658999,2017-01-24 14:03:57 UTC,"This upstream commit removes the warning, and mentions its ""plague""."
1658999,2017-01-25 18:29:58 UTC,I built the attached patch and put the binaries at [1].
1659003,2017-01-25 00:14:11 UTC,"Reviewed: https://review.fuel-infra.org/30112
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-25 12:03:23 UTC,"Reviewed: https://review.fuel-infra.org/30109
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-25 07:19:01 UTC,"Reviewed: https://review.fuel-infra.org/30114
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-25 07:18:56 UTC,"Reviewed: https://review.fuel-infra.org/30106
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-25 00:49:55 UTC,"Reviewed: https://review.fuel-infra.org/30111
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-25 00:15:06 UTC,"Reviewed: https://review.fuel-infra.org/30110
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-25 00:08:54 UTC,"Reviewed: https://review.fuel-infra.org/30108
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-25 00:07:47 UTC,"Reviewed: https://review.fuel-infra.org/30107
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-24 16:14:00 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30100"
1659003,2017-01-25 00:04:05 UTC,"Reviewed: https://review.fuel-infra.org/30100
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1659003,2017-01-24 18:50:22 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30107"
1659003,2017-01-24 19:00:22 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30108"
1659003,2017-01-24 19:03:42 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30109"
1659003,2017-01-24 18:15:59 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30106"
1659003,2017-01-24 19:19:15 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30111"
1659003,2017-01-24 19:41:09 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30112"
1659003,2017-01-24 23:28:05 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30114"
1659003,2017-01-24 19:12:56 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30110"
1659005,2017-02-15 16:42:00 UTC,This bug looks to be isolated to Horizon. In neutron net-list or neutron subnet-list there's no duplicates.
1659020,2017-02-02 18:54:38 UTC,"Please confirm this is still a problem with the current releases, and be specific about what versions are used in testing."
1659020,2017-02-13 11:48:37 UTC,Issue is seen in mitaka openstack client 2.3.0 version.
1659020,2017-02-14 06:32:49 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/433457"
1659020,2017-03-10 05:18:46 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/433457"
1659021,2017-03-11 10:34:29 UTC,"Debian Jessie backports have more recent OpenSSL, why should this not be possible for Ubuntu?"
1659021,2017-04-04 12:51:25 UTC,Is there anything we can do to help backporting openssl?
1659022,2017-02-17 09:43:25 UTC,"it sounds perfectly fine when an action attempts to lock a cluster and that attempt fails, right?"
1659022,2019-01-16 00:27:08 UTC,The health manager implementation was changed so that the node polling does not run cluster check anymore.  Instead it queries nova for server status using nova driver.  That way it will not deadlock for health checks.
1659025,2020-08-07 00:20:55 UTC,Administrative Guide is being added here: https://review.opendev.org/502936/
1659025,2020-09-22 20:16:43 UTC,"Reviewed:  https://review.opendev.org/753063
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=a5112a3f1033e9320048bf535e4845c389dcb80e
Submitter: Zuul
Branch:    master"
1659025,2017-11-22 18:58:35 UTC,"Reviewed:  https://review.openstack.org/499881
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=9495e52f3d442f6701f7addac47a268f2cd38214
Submitter: Zuul
Branch:    master"
1659025,2020-09-21 16:07:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/753063"
1659035,2017-01-30 10:28:47 UTC,"Hi,"
1659035,2017-01-30 13:59:05 UTC,"Yes, I understand they are the same.  If the text that appears in the Icon/List view can't be changed then the Icon/List view needs fixing when you click on a printer."
1659044,2017-01-24 16:45:28 UTC,full debug output
1659044,2018-01-24 22:39:46 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-400
1659047,2017-02-27 18:22:18 UTC,"I just wanted to drop a note that I have not had an issue again since late January 2017.
It did happen twice in January on two separate stacks but never again."
1659047,2017-02-27 20:20:10 UTC,Thanks for the info
1659047,2017-03-03 15:33:05 UTC,I found another possible contributing factor to the problem.
1659047,2018-01-24 22:39:44 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-401
1659056,2017-02-28 19:19:50 UTC,"One important detail I missed is that the CD is rewritable, CD-RW"
1659056,2017-01-24 17:35:04 UTC,I still have the CD if any test on it are needed
1659066,2019-05-01 16:12:14 UTC,Let's assign this to Helen Walsh.  She can close it out if the doc tasks for VMAX driver have already been done.
1659072,2017-03-26 18:45:00 UTC,This bug is related to https://bugs.launchpad.net/pantheon-mail/+bug/1629743
1659084,2018-04-27 03:13:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659087,2017-01-26 22:32:28 UTC,"Trying the fsuid/fsgid workaround, I came across another oddity:"
1659087,2017-01-27 13:02:16 UTC,"On Thu, Jan 26, 2017 at 10:42:44PM -0000, Jonathan Calmels wrote:

> Thinking more about it, this might be due to the lack of
> CAP_DAC_OVERRIDE so I guess I need this too right?
"
1659087,2017-01-26 22:42:44 UTC,"Thinking more about it, this might be due to the lack of CAP_DAC_OVERRIDE so I guess I need this too right?"
1659087,2017-01-26 19:13:48 UTC,"Glad you figured it out, I suspected this had something to do with the may_create/may_o_create code paths but couldn't wrap my head around it. Hopefully this will be addressed upstream in the near future."
1659087,2017-01-24 19:25:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659087,2017-01-26 00:21:53 UTC,"I can't reproduce the issue on Fedora 4.9.5-200.fc25.x86_64 either.
As you pointed out, setting the fsuid/fsgid to a known userns mapping does work."
1659087,2017-01-25 13:22:36 UTC,"On Tue, Jan 24, 2017 at 09:37:18PM -0000, Jonathan Calmels wrote:

> Interesting, I tried to reproduce with a Debian strech 4.8.0-2-amd64
> (Debian 4.8.15-2) and 4.9.0-1-amd64 (Debian 4.9.2-2) and didn't hit the
> error.
"
1659087,2017-01-24 21:37:18 UTC,"Interesting, I tried to reproduce with a Debian strech 4.8.0-2-amd64 (Debian 4.8.15-2) and 4.9.0-1-amd64 (Debian 4.9.2-2) and didn't hit the error."
1659087,2017-01-24 20:04:42 UTC,"Iirc, as of 4.8 what you're seeing is upstream behavior, and yes it did get backported to xenial in the series you referenced."
1659087,2017-01-26 14:08:29 UTC,"I've been in communication with the upstream namespace maintainer, and the intention was certainly that what you're doing should fail. However there was an oversight that missed the O_CREAT case. Due to some differences in 4.4 the backport did cover that case."
1659088,2017-01-27 17:08:50 UTC,Moved from tripleo-quickstart launchpad (Moving bug trackers in progress).
1659090,2017-02-08 11:12:44 UTC,https://review.openstack.org/#/c/426278/
1659094,2017-01-26 23:37:02 UTC,I can confirm this running on Archlinux using the same versions as mentioned above.
1659094,2017-01-26 23:37:44 UTC,It might be related to the following bug I found https://github.com/Flexget/Flexget/issues/1596#issuecomment-271146518
1659094,2017-01-28 04:38:08 UTC,This is caused by a change in the sqlite3 module in Python 3.6. In trying to figure out a way around it.
1659102,2018-02-28 11:17:02 UTC,"Can you confirm that ""juju show-machine 0"", and ""juju status --format=yaml"" are showing both addresses as you would expect?"
1659102,2017-01-30 06:37:07 UTC,"We track Juju 2.x issues in ""juju"" project. Re-targeting and marking as Incomplete since we are awaiting Narinder Gupta's reply."
1659102,2017-01-29 12:22:24 UTC,"I would actually expect ""juju status"" to show a public address if possible,
rather than an internal address. That doesn't mean it is the address that a
given unit should be advertising to its peers (that would be ""juju run
--unit ceph-mon/0 network-get --primary-address BINDING"").
Did you actually deploy the services bound into spaces, or you just
deployed them on a system that has more than one network interface and
hoped it would always pick what is ""right"" for you?"
1659102,2017-01-26 17:18:29 UTC,here is one example where juju machine show different subnet for public address. I have two network 10.200.2.x and 10.200.5.x and bot routable to network. PXE boot network is 10.200.5.x but nodes public address is on 10.200.2.x
1659102,2017-01-30 22:47:07 UTC,"John,
Will you please define a public address here? As i have two networks here 10.200.2.x (eno1) and 10.200.5.x (eno2) and both are routable to outside world through a gateway 10.200.2.254 and 10.200.5.254. I can configure all my servers pxe boot on any of the network. Problem is with insistency as i do configure my script to configure based on juju status of an service. How can i predict juju status will show the ip address from the specific subnet all the time?"
1659111,2017-04-06 18:30:07 UTC,------- Comment on attachment From <email address hidden> 2017-04-06 14:11 EDT-------
1659111,2017-04-07 14:38:45 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-April/083530.html
1659111,2017-05-03 16:55:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1659111,2017-05-16 10:21:44 UTC,"Hello IBM,"
1659111,2017-05-16 11:20:41 UTC,This bug was fixed in the package linux - 4.4.0-78.99
1659111,2017-05-16 11:28:56 UTC,------- Comment on attachment From <email address hidden> 2017-04-06 14:11 EDT-------
1659111,2017-04-06 10:41:53 UTC,Thiago - can you note which patches are backports and which files had conflicts ?
1659111,2017-06-09 20:09:56 UTC,"------- Comment From <email address hidden> 2017-06-09 16:08 EDT-------
Hello Lekshmi,"
1659111,2017-06-13 10:27:39 UTC,"Hi Lekshmi,"
1659111,2017-07-07 21:19:59 UTC,"------- Comment From <email address hidden> 2017-07-07 17:15 EDT-------
(In reply to comment #97)

> Hello Lekshmi,
>
> Do you need this fix in Ubuntu kernels 4.8 and 4.10 too, or just 4.4?
"
1659111,2017-07-07 21:30:21 UTC,Default Comment by Bridge
1659111,2017-07-07 21:30:23 UTC,Default Comment by Bridge
1659111,2017-06-01 14:20:09 UTC,"------- Comment From <email address hidden> 2017-05-31 23:49 EDT-------
Hi"
1659111,2017-04-05 21:49:45 UTC,------- Comment on attachment From <email address hidden> 2017-04-05 12:17 EDT-------
1659111,2017-01-26 14:49:39 UTC,"------- Comment From <email address hidden> 2017-01-26 09:45 EDT-------
Dan Williams responded mentioning that he is planning to address the issues found by the test robot:"
1659111,2017-04-05 21:49:41 UTC,"------- Comment From <email address hidden> 2017-04-05 17:43 EDT-------
Hello Canonical,"
1659111,2017-01-24 20:49:23 UTC,Default Comment by Bridge
1659111,2017-04-05 21:49:43 UTC,Default Comment by Bridge
1659111,2017-01-24 20:49:25 UTC,Default Comment by Bridge
1659111,2017-01-24 21:19:29 UTC,Default Comment by Bridge
1659111,2017-01-24 23:09:31 UTC,"------- Comment From <email address hidden> 2017-01-24 18:04 EDT-------
Hello Canonical,"
1659111,2017-01-30 17:30:11 UTC,"Kernel team is aware of this bug, removing Tasty Taco"
1659111,2017-02-13 14:20:34 UTC,"------- Comment From <email address hidden> 2017-02-13 09:09 EDT-------
Hi"
1659111,2017-01-24 21:19:31 UTC,Default Comment by Bridge
1659111,2017-03-13 18:29:41 UTC,"------- Comment From <email address hidden> 2017-03-13 14:27 EDT-------
Hello Canonical,"
1659111,2017-03-02 10:40:48 UTC,"------- Comment From <email address hidden> 2017-03-02 05:34 EDT-------
*** Bug 146487 has been marked as a duplicate of this bug. ***"
1659111,2017-03-28 10:00:36 UTC,"------- Comment From <email address hidden> 2017-03-28 05:43 EDT-------
Hi"
1659111,2017-04-03 09:49:35 UTC,"------- Comment From <email address hidden> 2017-04-03 05:39 EDT-------
*** Bug 153091 has been marked as a duplicate of this bug. ***"
1659111,2017-04-05 16:19:49 UTC,------- Comment on attachment From <email address hidden> 2017-04-05 12:17 EDT-------
1659111,2017-03-13 19:29:37 UTC,"------- Comment From <email address hidden> 2017-03-13 15:22 EDT-------
Small update:"
1659111,2017-03-20 07:29:48 UTC,"------- Comment From <email address hidden> 2017-03-20 03:23 EDT-------
Hi"
1659124,2017-05-25 14:27:33 UTC,"Can anyone see any adverse affects to adding angle brackets to the whitelist? I have a customer that is using unencoded angle brackets around their session IDs in the URL which they can't change at this point and the CVE fix broke their application. If there aren't any adverse affects I'll add them to the list for my distribution, and to tomcat if anyone else needs them."
1659124,2017-05-25 18:35:43 UTC,You mean '<' and '>' ?
1659124,2017-05-25 19:17:30 UTC,"(In reply to Mark Thomas from comment #22)

> You mean '<' and '>' ?
"
1659124,2017-06-08 07:13:27 UTC,Hi
1659124,2017-06-08 08:32:52 UTC,I'm neutral on adding '<' and '>' as allowed options.
1659124,2017-06-08 09:56:33 UTC,Hi
1659124,2017-06-12 07:48:39 UTC,Hi
1659124,2017-06-21 06:39:31 UTC,Hi
1659124,2017-09-25 20:33:43 UTC,I would like to ask for the ^ character. I'm not sure how to make a case for this. Its kind of important for us because we have been using this to denote financial indexes (similar to yahoo finance) and we have a large number of client installs that would all have to change to enforce uri encoding.
1659124,2018-05-29 09:52:00 UTC,See bug 62273 for further developments.
1659124,2018-07-31 09:09:21 UTC,Is there a reason why the error message does not log the URL? It's pretty hard to fix any calls if you do not know what exactly triggers this error.
1659124,2018-07-31 13:57:21 UTC,URLs can contain sensitive information.
1659124,2018-08-01 12:45:46 UTC,"The point regarding log files is a valid one but if the parsing of the request target fails, the access log will contain null rather than the request target."
1659124,2018-08-01 12:50:28 UTC,Ah. No need. Enable debug logging for org.apache.coyote.http11.Http11InputBuffer and it will log the entire request headers.
1659124,2017-05-18 07:42:52 UTC,Hi
1659124,2017-02-06 16:23:52 UTC,"OK, cool. So unless someone else objects to the patch as-is, I'll commit it to 7.0.x - 8.5.x shortly."
1659124,2017-05-18 08:40:54 UTC,"(In reply to Lulseged Zerfu from comment #19)

> Hi
>
>  We have found that we have problems with some characters that are not
> allowed in request URI and would like to know if any filter or valve can be
> applied to encode until clients get updated instead of responding with 400
> Bad Request.
"
1659124,2017-01-27 19:46:19 UTC,Allowing some of those (e.g. space) is extremely dangerous and should not be allowed under any circumstances.
1659124,2017-01-17 02:33:11 UTC,"Using the protocol=""HTTP/1.1"" connector (Coyote)"
1659124,2017-01-17 22:28:23 UTC,Given that using an unencoded '{' or '}' in a URL is contrary to the RFCs and that the fix that tightened the validation rules was in response to a security vulnerability (CVE-2016-6816) I think it is unlikely that an option will be introduced to make this validation optional.
1659124,2017-01-20 13:21:45 UTC,*** Bug 60616 has been marked as a duplicate of this bug. ***
1659124,2017-01-25 12:57:31 UTC,"Hi, thanks for reporting this issue."
1659124,2017-01-27 18:42:03 UTC,"Created attachment 34684
patch proposal"
1659124,2017-02-06 15:36:15 UTC,-1 as well for any additional characters. People who are that desperate to run into trouble can patch Tomcat easily.
1659124,2017-01-27 20:11:09 UTC,"(In reply to Mark Thomas from comment #4)

> I generally dislike configuration via system property. That said, making
> this per Connector will be significantly more invasive.
"
1659124,2017-01-27 20:36:17 UTC,"Hi, for my use cases I would like to have just a whitelist and let Tomcat handle all the RFC blacklisted chars automatically. In my case I had to whitelist curly braces and pipe."
1659124,2017-02-07 18:33:01 UTC,Fixed in:
1659124,2017-01-27 20:55:49 UTC,"I think I prefer the whitelist option but I'd like to see it limited to - at this point - '{', '}' and '|'. Other characters can be considered on a case by case basis."
1659124,2017-01-30 14:54:33 UTC,"Created attachment 34694
whitelist proposal limiting characters with docs"
1659124,2017-01-31 10:11:54 UTC,"Thanks for the updated patch. I like the overall design. Some detail comments:
- I think a different name is required. We might want to override other restrictions in the future. Maybe requestTargetAllow
- The docs need to state which characters are valid in the allowed list
- What to do if some other invalid character is placed on the allowed list. Log a warning?
- I'm still undecided on whether this should be per connector configuration"
1659124,2017-01-31 10:17:27 UTC,Please fix it in Tomcat 8.5.X too
1659124,2017-01-31 16:53:23 UTC,"Created attachment 34698
Updated patch proposal including a warning message for characters that aren't allowed"
1659124,2017-02-06 15:02:06 UTC,"Coty, the patch looks good to me, can you please add the following chars to the list of allowed characters ?"
1659124,2017-02-06 15:09:06 UTC,"You need to make a case for each of those to added to the potentially allowed list. Without any such justification, I am -1 on expanding it beyond the current three allowed characters."
1659124,2017-02-06 15:16:37 UTC,OK Mark at this moment I'm running a patch in production to make all the characters allowed.
1659124,2017-01-27 20:47:04 UTC,"Created attachment 34687
whitelist patch proposal"
1659132,2017-02-08 17:14:12 UTC,"It seems that somebody fixed the problem as of today, many thanks for this. Two weeks without uRadio is a very long time...Kind Regards"
1659135,2018-01-25 09:17:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1777
1659140,2017-01-26 21:12:42 UTC,"There doesn't seem to be an ""edit"" button, so I'll add details in comments as I discover them."
1659149,2017-01-25 01:01:58 UTC,https://github.com/snapcore/snapd/pull/2701
1659153,2019-10-14 15:34:40 UTC,"So... at this point, what remains to be done is to detect and return an error when 'private' is true and 'name' does not end in a *. That is, just before api.go's searchStore calls out to findOne, it should check for private and bail with a 400."
1659153,2017-01-25 02:36:13 UTC,"I've found the /v2/find to be the hardest part to understand in the REST API due to the interaction between the q, name and select parameters."
1659153,2017-01-25 02:23:38 UTC,The relevant part of the code is (daemon/api.go):
1659153,2017-01-25 00:53:52 UTC,"Actually, now I read the docs more closely:"
1659153,2017-01-25 03:10:30 UTC,"On Wed, Jan 25, 2017 at 02:36:13AM -0000, Robert Ancell wrote:

> The question is, does select=private even need to exist? Since the JSON
> snap object have a private value, shouldn't all searches return private
> snaps if authorization is provided? The client can then filter the
> results if this is required.
"
1659155,2017-01-26 07:50:15 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1659169,2017-06-29 11:46:44 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1659169,2020-01-07 17:43:43 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/424931"
1659169,2017-06-23 12:50:17 UTC,"There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments."
1659169,2017-06-28 15:44:05 UTC,"This only would be an issue with extremely large numbers of ports, marking as Opinion."
1659175,2020-02-28 15:29:21 UTC,This issue was fixed in the openstack/neutron 13.0.7 release.
1659175,2020-02-26 14:08:43 UTC,"Reviewed:  https://review.opendev.org/705199
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3750587833310aafdc0f6948a630ca3afe6bea0a
Submitter: Zuul
Branch:    stable/rocky"
1659175,2020-02-18 14:11:17 UTC,This issue was fixed in the openstack/neutron 14.1.0 release.
1659175,2020-02-05 13:55:33 UTC,"Reviewed:  https://review.opendev.org/705198
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b99298dfad1611294bf6dfa41712388af78c7197
Submitter: Zuul
Branch:    stable/stein"
1659175,2020-01-31 11:48:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705199"
1659175,2020-01-31 11:48:15 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/705198"
1659175,2019-09-19 10:13:31 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1659175,2019-06-02 03:48:44 UTC,"Reviewed:  https://review.opendev.org/653903
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=335ac4e2d95c164d66a3b09d9fd08e9c563edfc2
Submitter: Zuul
Branch:    master"
1659175,2019-05-15 06:53:28 UTC,"Reviewed:  https://review.opendev.org/657913
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=65264a936a6c9d0a8c4eae69acaee2c3ee54b5d6
Submitter: Zuul
Branch:    master"
1659175,2019-04-19 01:31:00 UTC,"... sorry, hava pasted wrong scripts and results."
1659175,2019-04-18 15:36:15 UTC,"(1) Use any invalid sort key and standard attribute of `Port` resource to reproduce this issue:
[root@master ~]# neutron net-list --sort-key fake_key --sort-dir asc
[u'fake_key'] is invalid attribute for sort_keys
Neutron server returns request_ids: ['req-8a0c2434-18fa-44ee-910d-da299c4b4578']
[root@master ~]#
[root@master ~]# neutron net-list --sort-key created_at --sort-dir asc
Request Failed: internal server error while processing your request.
Neutron server returns request_ids: ['req-9b841cd8-82bd-4bc6-9df3-b39e9a892148']"
1659175,2017-06-30 11:35:54 UTC,unassigning current since patches have been abandoned so someone else can pick this up
1659175,2017-06-28 18:39:42 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.openstack.org/424948
Reason: Abandoning this one as it's been idle for more than 4 weeks. Please push an update if it's still active. Thanks"
1659175,2017-03-21 08:27:08 UTC,"Change abandoned by Kevin Benton (<email address hidden>) on branch: master
Review: https://review.openstack.org/424949
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1659175,2017-01-25 02:57:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424949"
1659175,2017-01-25 02:55:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/424948"
1659175,2019-04-19 08:42:30 UTC,Seems duplicated with issue: https://bugs.launchpad.net/neutron/+bug/1804259
1659175,2019-04-19 03:35:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653903"
1659185,2017-01-30 17:25:49 UTC,Systemtap is in universe and is community supported.  Removing Taco Screen team.
1659190,2017-11-03 16:42:27 UTC,Syncing task from Mir.
1659193,2017-01-27 23:10:52 UTC,"LibreOffice (5.2.4.2.0) currently has no problems, and so far I haven't seen the same behaviour with any other GTK programs."
1659193,2017-12-04 11:56:52 UTC,"I see the same on Archlinux as well, without any warning though."
1659193,2019-06-21 13:53:32 UTC,"Does this still occur with Inkscape 0.92.4? If so, is the the Adwaita icon theme installed?"
1659193,2019-11-06 02:32:36 UTC,Closing due to lack of response. Please check for bugs on our new tracker: https://inkscape.org/report. Thank you!
1659193,2017-01-27 14:48:51 UTC,Thanks for taking the time to file a report!
1659195,2017-04-21 20:27:54 UTC,"Unfortunately there is no easy way to reproduce without building a new core. I build a core snap with the ""networkd-allow-networkd-to-start-in-early-boot.patch"" included."
1659195,2017-04-22 06:01:30 UTC,"How do you provision the nodes in linode? Do you use cloud-init?  cloud-init interacts with the network-online.target, so that could be related."
1659195,2017-03-30 15:21:11 UTC,"This is in xenail, more specifically in the ubuntu core system."
1659195,2017-03-13 07:52:45 UTC,Is this with zesty; xenial; or both?
1659195,2017-03-13 02:49:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659195,2017-04-20 21:55:34 UTC,"You say that the resolvconf SRU from #1649931 fixed it /mostly/ but not in all cases.  If you are able to reproduce this problem, can you provide journalctl output from the affected environment so we can see what isn't happening in the right order?  Do you have step-by-step instructions we can follow to reproduce the problem ourselves?"
1659198,2017-02-07 08:41:49 UTC,i resolve this problem by modified method copy_files in file set_configs.py in kolla project.
1659198,2017-02-04 07:41:30 UTC,"I check the file rbdmap, it's owner is root,but the current user is nova,so shutil.rmtree() could not execute as Permission denied."
1659231,2017-02-06 12:15:47 UTC,I just tried linux kernel 4.4.21 from mainline ppa. System settings doesn't hang any more. So I am guessing problem lies in kernel > 4.6. Marking it as affected.
1659231,2017-02-12 08:45:58 UTC,Well there are two problems here
1659231,2017-02-06 19:46:49 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1659231,2017-02-07 17:03:23 UTC,@Joseph
1659231,2017-02-06 12:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1659247,2017-01-25 11:14:42 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1659247,2017-03-14 10:27:21 UTC,Also affect Xubuntu
1659254,2017-01-25 11:14:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1659254,2017-02-21 13:01:04 UTC,"""about this computer"", the version is still 16.10  - fixed."
1659254,2017-03-23 02:51:13 UTC,the plymouth version is also still 16.10 as attached picture showed.
1659255,2017-01-25 15:48:22 UTC,"curious - is this zesty? or xenial+overlay?
also, is this debs or snaps?"
1659255,2017-01-25 16:15:41 UTC,"I observed this with x+o, deb based."
1659255,2017-01-26 03:36:24 UTC,Try a heap profiler. The problem with high memory usage is that it's often just indefinitely bloat and not a permanent 'leak'. This means the program still has enough smarts to free it all on shutdown and no leak checker will tell you what the problem was. But while it's running it's still too big. So use a heap profiler...
1659256,2017-03-15 13:02:24 UTC,"still seems to be an issue in current trunk.
In trunk, the small size is larger than the large size
Windows 10, Inkscape 0.92+devel 15592"
1659256,2018-01-07 19:29:04 UTC,"I implemented what I described in #9 now, see
https://gitlab.com/inkscape/inkscape/merge_requests/180"
1659256,2017-03-15 19:23:20 UTC,"An alternative would be to use the native window size by default, but limit it to the screen size."
1659256,2017-03-15 18:59:59 UTC,"> Has anybody tested how the current ""Small"" window size looks on very small screens (i.e. does it shrink to fit on the monitor)?
"
1659256,2017-03-15 18:55:18 UTC,"OK, just tested with r15598 on Windows 10 and in fact behavior between gtk2 and gtk3 changed when not setting the windows size explicitly:
- gtk2 starts with the smallest possible window size (the window can't be reduced in size any further)
- gtk3 start with the ""natural"" window size (i.e. it tries to adjust the size of the window to make all UI elements fit in."
1659256,2017-03-15 08:49:06 UTC,Patch attached.
1659256,2017-03-15 10:00:34 UTC,"@jazzynico:
Is this issue actually still present in revisions >= r15507 [1] (which fixed all issues for me on Windows 10 x64)?
Changing the code in this way might cause regressions as it bypasses the check at [2] (effectively rendering that conditional useless as w/h will always be > 0)."
1659256,2017-01-25 12:34:09 UTC,"confirmed on Windows 10, Inkscape 0.92+devel 15423."
1659256,2017-03-15 13:06:41 UTC,@Eduard - Yes it's still present with the latest trunk revisions.
1659259,2017-01-25 10:58:45 UTC,"IRC link for the chat:
http://eavesdrop.openstack.org/irclogs/%23openstack-watcher/%23openstack-watcher.2017-01-25.log.html"
1659267,2020-06-06 11:24:49 UTC,"this would be really useful for testing resilliance and auto fall-over systems in a vm, to be able to quickly virtually ""unplug"" a network connection."
1659267,2020-06-08 09:21:53 UTC,"Note that you can start QEMU with the ""-S"" flag which means CPUS are paused. This gives you ability to run the ""set_link"" monitor command above, and then run ""cont"" to actually start the VM. Less convenient that a CLI flag, but functionally it is eqivalent."
1659268,2017-07-26 15:23:00 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1659268,2017-01-26 11:26:24 UTC,"Joseph, regarding what kernel version this panic starts happening in, I know two things:
In 4.8.0-32 it does not.
In 4.9.0-12 it does."
1659268,2017-01-26 17:02:13 UTC,The following package from zesty-proposed does not have this crash:
1659268,2020-04-04 20:16:35 UTC,Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818392
1659268,2017-01-26 15:30:02 UTC,That is good news.
1659268,2017-01-25 12:00:13 UTC,This change was made by a bot.
1659268,2017-01-25 18:32:46 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1659268,2017-01-25 18:32:36 UTC,Do you know what kernel version this panic starts happening in?
1659268,2017-01-26 11:52:10 UTC,Crash does not happen with 4.10.0-041000rc5-generic.
1659272,2017-02-08 08:20:53 UTC,I can't reproduce this on my Ubuntu Core system running on my Pi3.
1659272,2019-09-05 11:38:27 UTC,I think this no longer affects us.
1659272,2017-01-26 15:59:22 UTC,"So the issue might be more generic, and not related to nesting of pythons."
1659272,2017-02-02 13:56:08 UTC,Does that happen after connecting the plugs as well?
1659272,2017-02-02 14:40:56 UTC,"MM connected, dbus still fails
modem-manager:service checkbox-snappy:modem-manager,modem-manager:mmcli,network-manager:modem-manager"
1659272,2017-02-03 13:18:49 UTC,So just for the sake of simple instructions to reproduce:
1659272,2017-02-08 19:46:41 UTC,"Definitely Ubuntu Core systems, but all we've tested on were intel platforms (NUCs and Dells)"
1659272,2017-02-15 17:35:42 UTC,"I'm seeing the same thing as Simon, but when I run it from checkbox-snappy.test-runner, I'm still seeing the same failures:"
1659272,2017-02-17 12:24:33 UTC,After another session with the problem I found that in fact everything works if we start the python (outermost) process with sudo.
1659272,2017-02-17 14:45:59 UTC,This isn't apparmor (you see a different error in the output that reference AppArmor).
1659272,2017-02-17 15:51:37 UTC,"So it doesn't help that the snap is installed in --devmode?
And also I understand, that although later on the is a sudo call from the process, the policy is already set and the access will be denied for all subprocesses, right?"
1659272,2017-04-19 04:17:49 UTC,[Expired for snapd because there has been no activity for 60 days.]
1659282,2017-03-29 20:28:36 UTC,"Reviewed:  https://review.openstack.org/424723
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=b9ad3de19f648c159c371f78b1c7e068fe032a24
Submitter: Jenkins
Branch:    master"
1659282,2017-03-28 18:48:41 UTC,"This hasn't been approved yet but Jim says he's ok with it and Dmitry confirmed it, so I'm going to assume they both approve of it. The nova-virt part will be covered in some other nova-related rfe or bug? I'm good with this as long as the hand-waving 'work that will allow attach/detach VIFs to active Ironic nodes' is simple."
1659282,2017-03-16 13:11:23 UTC,"Change abandoned by Vasyl Saienko (<email address hidden>) on branch: master
Review: https://review.openstack.org/425112
Reason: https://review.openstack.org/#/c/440719/"
1659282,2017-01-25 13:01:01 UTC,[Devstack] Allow add several ports to node: https://review.openstack.org/#/c/425112/
1659282,2017-01-25 13:00:34 UTC,related patch proposed before RFE was created: https://review.openstack.org/#/c/424723/
1659282,2017-02-08 10:59:57 UTC,"This is light on detail, but I'm okay with approving it. The only real change is in the title :P"
1659286,2017-01-30 11:57:45 UTC,Please provide with output of
1659286,2017-01-30 12:50:48 UTC,I haven't that env.
1659293,2017-01-31 16:34:50 UTC,"Sorry, it's reproduced again on #822 (rc2) snapshot"
1659293,2017-03-14 10:43:11 UTC,Please provide full diagnostic snapshot or env with reproduce to debug.
1659293,2017-01-31 08:50:44 UTC,"It seems the issue is related to insufficient resources.
I've rechecked the issue again with doubled resources (ram, cpu) for compute nodes and an murano env created successfully, a murano application deployed properly."
1659306,2017-03-31 19:39:05 UTC,I have the same error in 18.1 cinnamon 64 bit Xreader 1.2.2
1659310,2017-01-25 15:13:16 UTC,The Webbrowser case from the log here: http://pastebin.ubuntu.com/23863224/ describes a segfault in qtmir - According to the log it tries to focus a nullptr surface. So I added qtmir to the report.
1659310,2017-01-25 15:41:14 UTC,"For the webbrowser case:
1) Launched Unity8 with the dash focused
2) Opened the web-browser
3) Open trust session
4) Left trust session open
5) Close browser
6) Do *not* focus dash (note if I did focus the dash first it didn't crash)
7) Open browser, by clicking on dash icon
8) Crashed as browser was launching"
1659310,2017-01-25 16:02:41 UTC,"What I've also noticed is if you close the application without a trust session, the focus is given back to the dash. Whereas if you have a trust session open the focus seems to be lost."
1659310,2017-01-25 16:20:37 UTC,This is the webbrowser case with MIR_SERVER_WINDOW_MANAGEMENT_TRACE: http://pastebin.ubuntu.com/23863966/
1659310,2017-01-25 16:43:29 UTC,"I don't think the focus gets lost: In that trace goes to a window called ""Scopes""."
1659310,2017-01-25 16:49:19 UTC,"For the Kate case:
1) Start unity8 with dash focussed
2) Start terminal
3) Launch kate
4) Two dialogs are shown in the process
- klauncher warning dialog (this dialog is dismissed by pressing OK)
- print dialog (when selecting Print this launches the trust session)
5) Invoke trust session
6) Close kate
7) Shell freezes as kate is closing"
1659310,2017-11-03 16:42:30 UTC,Syncing task from Mir.
1659311,2019-09-19 11:55:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1659317,2017-01-31 16:57:45 UTC,"Hello Lance,"
1659319,2017-01-26 06:50:54 UTC,"This seems to happen, more generally, when you edit any word.
For example:"
1659320,2017-02-23 14:40:44 UTC,"Hi Marco, I'm not sure I understand, where in the UI would you like to see the arch?"
1659320,2017-02-23 23:09:16 UTC,Here: http://i.imgur.com/vFQ3zVD.png
1659322,2017-09-15 15:21:28 UTC,"The reason for this seems to be that it tries to decode the ANSI encoded log file as UTF-8.
Would be great having this fixed soon."
1659323,2017-04-09 18:33:49 UTC,I have the same issue...in fact my mom has the same issue on her laptop.
1659323,2017-01-25 16:30:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1659330,2017-01-25 15:51:48 UTC,PR on github: https://github.com/snapcore/snapcraft/pull/1074
1659330,2017-01-25 15:54:24 UTC,I would advocate for not losing the relationship all-together and have snapd add some header into the desktop file so you can link back to it.
1659330,2017-01-25 15:59:34 UTC,"That would be ideal, indeed. Can that be tracked in a separate bug report? The two approaches are not mutually exclusive (and implementing the easy one (this one) first won’t hurt the other one, either). Should I file a bug at https://bugs.launchpad.net/snappy/+filebug to request the change in snapd?"
1659330,2017-01-25 17:05:20 UTC,I would just add a bug task here
1659331,2017-01-26 15:02:16 UTC,"By reviewing the /etc/lightdm/* files once again I noticed that I had a lightdm-gtk-greeter.conf.dpkg-new file and that lightdm-gtk-greeter.conf was a symlink pointing to somewhere else *).
After renaming the dpkg-new file to lightdm-gtk-greeter.conf the solid blue background was gone. Instead lightdm now showed the greeter background (the ""background"" as set in the .conf file) for a second or so, then the user's background also for a second or so and then the greeter background again.
I then set the user-background to false in the .conf file. Lightdm now only show the greeter background with a flicker after some two seconds."
1659333,2017-01-25 15:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1659333,2017-03-06 10:38:07 UTC,We currently have all if the i386 testing for xenial and later turned off as the rtctest tickles a bad interaction with the HOST xenial kernel and the VM we are running in does not recover.
1659333,2017-03-06 10:38:20 UTC,We should disable the rtctest in the near term.
1659333,2017-03-06 11:53:12 UTC,http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=99c74ff40f564825dd25885e15886d288d8c6bad
1659336,2017-03-08 23:38:25 UTC,"@su_v: For MSYS2 builds we now install the correct index.theme, see
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15581"
1659336,2017-02-20 19:00:28 UTC,Reproduced with latest devlibs64 and lp:inkscape r15534 on Windows 10.
1659336,2017-02-20 21:23:06 UTC,"Fixed in r15535
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15535"
1659336,2017-02-20 21:24:18 UTC,Reincarnation of bug #1635207 btw.
1659336,2017-03-04 00:43:47 UTC,"@Eduard - any specific reason why the real index.theme file from the hicolor icon theme is not installed for GTK3-based trunk builds, and instead a empty one is created?"
1659336,2017-03-04 01:33:13 UTC,">  any specific reason why the real index.theme file from the hicolor icon theme is not installed for GTK3-based trunk builds, and instead a empty one is created?
"
1659336,2017-03-04 01:59:51 UTC,"Eduard Braun wrote:

> Do you know if we have to install all the empty folders too, or can
> we safely omit them and only install the index.theme?
"
1659339,2017-11-14 19:14:54 UTC,"Same problem here, also with mp3 files.  I use Thunar to copy some folder within `mtp://[usb:001,054]/SD-Card/Music/`, and the first few-ish work, then I get the error dialog, and no matter what I do next, thunar is extremely slow or completely unresponsive in *every* operation, even when I kill the process and open an unrelated folder.  My guess is that thunar lists all devices/places/networks, thus accesses libmtp, which locked up.  Only disconnecting the device lets me try it again."
1659339,2017-12-06 00:22:00 UTC,"I just got this error with my Android Nougat phone, trying to transfer files using PCManFM, but the error was resolved when I used Thunar (Lubuntu 14.04 with some xfce components installed)"
1659339,2017-03-22 08:10:18 UTC,"I get this when I copy ripped mp3 files from my pc tp my phone.
Most files will tranfer correctly, but on average one in five won't."
1659339,2018-11-05 19:34:46 UTC,"I had this error while copying a file to my phone. The file name was ""Do You Hear What I Hear?.mp3"""
1659339,2017-01-25 16:11:46 UTC,"Related, but not exactly the same: ""libmtp error: Could not send object info"" when copying content to root MTP folder <https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1369651> (I cannot coy to any folder)."
1659339,2017-03-14 14:25:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659341,2017-01-25 17:15:32 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1659344,2017-01-26 17:44:15 UTC,"I initially suspected that it might be webbrowser-app not handling well the chrome, but I can reliably observe the issue on my desktop with oxide 1.19.7 running the simple QML example attached."
1659344,2017-04-18 10:57:57 UTC,"It appears that the offset is reset only when navigating to a new domain. In the simple reproducer attached to comment #1, if I set all the URLs to belong to the same domain, the offset is never reset."
1659351,2019-12-18 17:23:28 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/443582
Reason: This repo is retired now, no further work will get merged."
1659351,2017-01-30 16:06:59 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/425680"
1659351,2017-04-05 16:51:03 UTC,"Verified on 10.1 #1566.
controller:
root@node-2:~# ulimit -n
102400
compute:
root@node-5:~# ulimit -n
102400
root@node-5:~# cat /etc/init/libvirtd.override | grep limit
limit nofile 102400 102400"
1659351,2017-03-09 11:22:40 UTC,"Reviewed:  https://review.openstack.org/433090
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=3a8a7c0ac8c6557fbea854aecdc7f6e75c40f56b
Submitter: Jenkins
Branch:    stable/newton"
1659351,2017-03-09 11:22:20 UTC,"Reviewed:  https://review.openstack.org/433089
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=e4a035a3d59d6ccf26db1c47abf0a3c9a6b7c19c
Submitter: Jenkins
Branch:    master"
1659351,2017-03-09 11:14:58 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/443582"
1659351,2017-02-13 14:42:02 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433090"
1659351,2017-02-01 08:51:35 UTC,"Verified on snapshot-id #822
controller:
root@node-1:~# ulimit -n
102400"
1659351,2017-01-30 16:06:53 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: master
Review: https://review.openstack.org/425679"
1659351,2017-02-13 14:41:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433089"
1659351,2017-01-30 12:53:44 UTC,"Dev team, could you please update description, original description is absolutely understandable for repro."
1659351,2017-01-26 12:45:13 UTC,This issue seems to be critical as it is a major regression which will lead to severe performance and scale issues for services.
1659351,2017-01-26 13:12:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/425679"
1659351,2017-01-26 13:13:16 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/425680"
1659351,2017-01-30 12:54:19 UTC,"After update of description, I'll remove tag ""dev-to-verify"""
1659351,2017-01-27 13:48:42 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/426234"
1659351,2017-01-27 14:14:01 UTC,"Reviewed:  https://review.openstack.org/425681
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=238127b5b4ee80de1f5ab49cf423cfed3281392d
Submitter: Jenkins
Branch:    stable/mitaka"
1659351,2017-01-26 13:13:31 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/425681"
1659360,2017-01-25 18:08:41 UTC,I thinks this very needed and would also open additional possibilities for doing config validations. i.e catching binding conflicts early when services are collocated.
1659360,2017-04-10 16:03:18 UTC,I believe this is the same as bug #1659376 as mentioned by Larry. (supporting L2 bindings in charms and associating them with unconfigured interfaces in MAAS feels exactly like what this is)
1659360,2017-04-10 16:16:50 UTC,It's not the same.  Larry's bug is supporting that configuration at all - this bug is about being able to change whether an interface is configured in MAAS or not via juju.
1659372,2017-01-25 18:23:01 UTC,PR: https://github.com/snapcore/snapcraft/pull/1011
1659376,2020-06-22 21:36:47 UTC,"This seems like it woudld require re-engineering of a Juju feature/primitive in order to properly address.  I think it would need to be planned development cycle work, not break/fix bug work.  As such, I'm not sure anyone can put a Field SLA on it.  I'll take it to the next Juju/OpenStack engineering cross-team, however, to confirm."
1659376,2018-11-09 08:09:15 UTC,There is an additional security argument for this feature.
1659376,2019-10-16 21:34:17 UTC,"Agree with Trent and Peter, MAAS concept of spaces is L2, but currently juju concept of spaces is L3.  While an L2 space doesn't make sense for charm use in the manner of private_address(binding_relation_name), it does make sense for subordinate use and network interface pass-through to OVS/other L3 management layer plugins."
1659376,2019-04-02 09:25:25 UTC,Subscribing field-high as we have clouds running out of ipaddr
1659376,2018-12-12 08:31:57 UTC,subscribed ~field-medium as we're hitting this again
1659376,2018-10-18 07:36:04 UTC,"As part of the implementation for this, currently charms often need to get the network interface related to an IP. Currently they use the network-get charm command to get the IP of the space, but then have to figure out what interface that IP is on manually. Ideally the charm API would be expanded to specifically give the interface."
1659376,2017-05-05 18:23:02 UTC,"Changing the tag name as this isn't a blocking bug, but instead a requested feature."
1659376,2017-03-30 14:51:25 UTC,@John sorry I had not seen your earlier question. This is for new enablement of bindings in our bundle. So we don't know how the workaround worked prior to hitting this issue.
1659376,2017-03-30 04:12:36 UTC,"As per comment # 5, we most certainly want to implement unconfigured space support. However, with 2.2 timeline and our current capacity, it will not be addressed in 2.2x."
1659376,2017-01-31 04:00:40 UTC,"Supporting unconfigured interfaces is something that we do want to support. I would think we already have a bug about this, but maybe it was only a road map item. The charm had a workaround for it in the past (IIRC white listing MAC Addresses in the charm config), which is absolutely a workaround for us not having the right pieces modeled to expose it properly. Did 2.1b4 break the existing workaround or is it that you were hoping unconfigured space support was already implemented?"
1659376,2017-05-31 13:05:37 UTC,"Just as a data point, I'd need this for a bit diff. usecase; for a cloud that calls for a publicly accessible api which we'd like to put in containers. We only have a small subnet available for that, and to save on ipaddress we have to leave the metal hosts configured with mode=link_up; only giving the actual containers ipaddress in the spaces subnet."
1659377,2017-03-24 23:26:29 UTC,"Are you connecting via wireless?
Can you confirm whether or not you're connected to your local network after you resume from suspend?
Can you reach any hosts via ip instead of hostname (ex. ping 8.8.8.8)?"
1659383,2017-01-25 18:34:04 UTC,"Hi Jason,"
1659383,2017-01-25 18:47:09 UTC,"Hi Andres, that's good to see but it does not tell me what I want to know, which is how old my current images are. That controllers page is a little confusing - it says when the last sync was, but it's not clear what that means. Is that a sync between region and rack, a sync from maas.io to region? Were any new images provided? My question of ""when did this image last get updated"" is not answered."
1659383,2019-09-19 15:03:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1659385,2017-01-30 22:03:14 UTC,"Note, just deleting the files can cause us issues with our CI."
1659385,2017-01-30 22:07:27 UTC,"In fixing this bug, we should somehow monitor if juju violates known_hosts."
1659385,2017-01-31 18:29:32 UTC,"In fixing this bug, we should somehow monitor if juju violates known_hosts. It sounds like using logsave and then doing post-analysis would fit this."
1659392,2019-09-19 11:55:42 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1659396,2017-01-25 20:11:28 UTC,"Constraining to 90deg is weird, yes. The behavior was changed recently, I think, so maybe an accident? I don't need constraint to 90deg, I already have 45 and it's easy enough to just stick to even numbers of 45n :P"
1659396,2019-10-25 07:54:17 UTC,"This got more seriously needed in newer releases of KiCad on Linux.  It seems legacy mode is removed and with that any hope of drawing non-45 degree aligned wires.  Indeed holding control locks to 90, not free reign."
1659396,2017-01-25 20:05:49 UTC,"Some 2D CAD apps constrain lines to the vertical and horizontal axis
when the user holds down a modifier key so it's not that weird.  Whether
or not this makes sense for drawing pcb traces is another issue.  We
could use a different modifier key for completely unconstrained trace
placement and support both."
1659396,2017-01-25 20:20:10 UTC,That is exactly my point.
1659396,2017-01-25 19:54:48 UTC,"@Chris, that would make sense. It seems that for track it is contraining to 90 degrees ... which is weird."
1659396,2017-01-25 19:49:32 UTC,"In OpenGL, holding Ctrl unlocks graphical lines from the 45 degree limit. What do people think about making that do the same for traces?"
1659396,2017-01-25 20:00:12 UTC,"@Chris, I love the idea!"
1659401,2017-01-25 23:56:21 UTC,"We might need a hidden ""notification"" deck for for it.
This can implemented along with the https://bugs.launchpad.net/mixxx/+bug/1019822"
1659401,2017-01-26 00:58:35 UTC,"We probably don't need all the features of a deck though -- it would be a waste to create everything a deck gets (RB/ST instance, tons of controls, etc.)."
1659401,2017-01-26 07:41:30 UTC,"Yes, sure. A least it needs an own namespace like a deck and some if its facilities in the back-end. Gain / Sync and so on ...
So a contributor should have a close look how a deck works and decide how to continue."
1659401,2020-05-10 18:39:11 UTC,I don't think this is a good idea. What if you are trying to find the next track in headphones but can't hear it well because there is this warning sound? Can we change this to Won't Fix?
1659401,2020-05-10 20:23:31 UTC,"It's of course necessary to allow to configure this behaviour, but I'd still appreciate this feature and disapprove the Won't Fix decision of @be.ing ."
1659409,2017-01-26 09:46:28 UTC,The following errors in the log are likely relevant:
1659415,2017-01-27 04:25:50 UTC,Installing bumblebee to support Nvidia Optimus resolved this issue for me.
1659415,2017-01-27 04:27:54 UTC,"I don't know how to close this bug, but as noted in #2 it is resolved from my (submitter) perspective."
1659420,2020-06-10 09:03:16 UTC,Gentle ping again for Jason or Billy to confirm this fix
1659420,2017-12-14 13:25:50 UTC,"Hi Jason or Billy, If the reported bug is fixed in pike-proposed, would one of you be able to tag this bug as verification-pike-done? Thanks."
1659420,2017-10-24 16:52:11 UTC,"Thanks Corey, I subscribed :)"
1659420,2017-10-20 08:25:18 UTC,"Hi Corey,"
1659420,2017-10-19 19:31:45 UTC,"Hello Jason, or anyone else affected,"
1659420,2017-10-24 14:16:08 UTC,"Hi Spyros,"
1659420,2017-10-02 17:55:04 UTC,This bug was fixed in the package python-k8sclient - 0.4.0-0ubuntu1
1659420,2017-10-02 16:45:16 UTC,I'd like to get a feature freeze exception in Ubuntu to upload python-k8sclient 0.4.0 to artful.
1659420,2017-10-02 11:25:31 UTC,"I've had the same problem, upgrading to python-k8sclient does the trick.
Wouldn't it be easier for people to update the requirements.txt pointing to minimum supported version of python-k8sclient?"
1659420,2017-02-01 08:02:00 UTC,The fix requires a fix in the k8sclient too. Check the version of your k8sclient. If you have version 0.3.0 it's expected that you'll have the bug.
1659420,2017-10-02 19:29:40 UTC,Its been reported to me from a 3rd party that an update of the package to the latest 0.4.0 release of the python-k8sclient resolves this issue for them. They've been running for at least 24 hours and have not seen this traceback occur in any of their workloads.
1659424,2017-01-26 14:27:46 UTC,"Given that Evergreen sites can customize the regex in any number of ways, I think it is in their best interest to customize this message in password_reset.tt2 to clearly define what the user needs to use for a password. I don't think there is a way to supply a generic message that covers all cases."
1659424,2017-01-27 22:47:47 UTC,"I'd argue that it is a bug or at the very least needs some refinement.  It looks like if there is no regex then ""check_password_strength_default"" does actually check password strength in a basic way.  It checks for length > 7 among other things.  On the other hand when a regex is provided then ""check_password_strength_custom"" really only checks for valid characters in the password.  In that case maybe it should return a different error."
1659424,2017-05-05 14:26:47 UTC,"I'm adding a note that there is a message in  password_reset_msg.tt2 that is used to inform the user of the password format when they update their password from my account, but it doesn't appear on the password reset page. I don't think it addresses the original bug report, but it does provide some guidance to the user when they try to create a password. I'll create a new bug and post some code to get that message to display on the password reset page."
1659424,2017-05-05 14:43:38 UTC,"Correction: the file is myopac/update_password_msg.tt2, not password_reset_msg.tt2"
1659429,2017-01-31 21:19:33 UTC,Accepting either form will be a lot more user friendly :)
1659429,2017-01-31 14:59:11 UTC,We will update the docs accordingly.
1659429,2017-01-31 03:51:22 UTC,Created docs issue: https://github.com/juju/docs/issues/1618
1659432,2019-12-10 15:26:53 UTC,Document during next release.
1659437,2017-01-26 00:39:04 UTC,Can you give us some details about your installation? Which language are you using? Are you fully up to date? Did this issue appear after installing anything or making any kind of changes to your system?
1659437,2017-01-26 00:56:12 UTC,"I installed elementary OS in default state (nothing special).
I always check for updates every single day (because of application manager check it for me) and update it.
I'm currently using en_US.UTF-8 as my language."
1659438,2017-03-02 19:19:34 UTC,"Ah, we don't have a CSV formatter yet. This is partially implemented. The CSV formatter should be easy to implement though."
1659452,2017-07-05 19:10:25 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1659452,2017-01-26 01:40:22 UTC,"testing a bit of this out in
https://review.openstack.org/#/c/425451/
https://review.openstack.org/#/c/425453/"
1659452,2017-01-27 17:07:25 UTC,Moved from tripleo-quickstart launchpad (Moving bug trackers in progress).
1659453,2018-05-30 19:47:10 UTC,I confirm it also happens in Inkscape 0.92 running on Windows 10
1659453,2017-01-27 14:21:32 UTC,"Reproduced on Windows XP (32-bit), with lp:inkscape/0.92.x rev. 15346."
1659453,2017-01-26 03:06:59 UTC,"I can confirm however that some of the parts of the extreme serifs do appear to be clipped, but I don't have that display artifacts problem."
1659453,2017-01-26 03:03:45 UTC,"cannot reproduce on  r14761 (fedora17) my inkscape release number might not be correct though, but it's definitely pre-0.92"
1659453,2017-01-26 03:55:59 UTC,"Based on tests with archived builds (on OS X 10.7.5):
- not reproduced with Inkscape 0.48.5 r10040,
- not reproduced with lp:inkscape rev <= 12487,
- reproduced with lp:inkscape rev >= 12488,
- reproduced with Inkscape 0.91 r13725, 0.92.0 r15299;
this is likely the same issue as tracked in"
1659455,2017-02-14 23:08:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433971"
1659455,2017-02-15 20:54:42 UTC,"Change abandoned by Joanna Taryma (<email address hidden>) on branch: master
Review: https://review.openstack.org/433971
Reason: this should be fixed in a different way"
1659455,2017-05-22 13:22:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/466729"
1659455,2017-07-09 03:33:41 UTC,"Change abandoned by Yuriy Zveryanskyy (<email address hidden>) on branch: master
Review: https://review.openstack.org/466729"
1659455,2018-03-16 20:46:57 UTC,"Reviewed:  https://review.openstack.org/466729
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=d81d2e7736cde319e5cb9ff8db334df1af264d84
Submitter: Zuul
Branch:    master"
1659459,2017-02-21 14:16:48 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1659462,2017-07-16 23:01:08 UTC,Moved to https://github.com/snapcore/snapd-glib/issues/7
1659466,2017-02-21 14:16:46 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1659467,2017-02-07 03:29:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430026"
1659467,2017-05-07 15:33:24 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/463149"
1659467,2017-06-08 21:52:41 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1659467,2017-08-13 01:56:09 UTC,"Reviewed:  https://review.openstack.org/463149
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a0a9f418e7f03cd497051d83359c297ca0cfb609
Submitter: Jenkins
Branch:    stable/ocata"
1659467,2017-08-22 11:38:59 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1659476,2018-10-03 20:26:37 UTC,"Fixed in master in r.e96c6827, not backport to 0.92.x in mind."
1659476,2017-01-26 23:38:37 UTC,"Also reproduced with oldest trunk build archived on this computer (with OS X 10.7.5) which has (at the time) experimental path effects enabled:
 lp:inkscape r10795"
1659476,2017-01-26 04:29:57 UTC,"Attaching externally linked GIF file to bug report (links tend to expire or otherwise get lost; the reporter's attachment is a html page with lots of javascript, not the GIF itself)."
1659476,2017-01-26 16:53:28 UTC,"Reproduced on Xubuntu 16.04, Inkscape 0.91 and lp:inkscape/0.92.x rev. 15345."
1659489,2017-08-13 00:11:40 UTC,"The dpi change commandline option isn't documented in the Inkscape man page yet (only in the Wiki release notes and here). Should it be?
https://gitlab.com/inkscape/inkscape/blob/0.92.x/man/inkscape.pod.in"
1659489,2017-06-04 23:01:35 UTC,fix ported to trunk r15729.
1659489,2017-02-10 03:54:11 UTC,"Hackmann wrote:

> the new command line command for not fixing baselines is
> missing in trunk
"
1659489,2017-02-10 03:41:07 UTC,"Btw. the new command line command for not fixing baselines is missing in trunk, as far as I can see. New report?"
1659489,2017-02-10 17:56:58 UTC,"Mmh. Thank you, su_v - I didn't try it out, I only compared the files and couldn't find the command... must have overlooked. Sorry!"
1659489,2017-01-30 23:14:12 UTC,"Ok I stand corrected, however it reinforces my point that --do-not-fix-pre-92 needs renamed.  That is too easily confused with what the dpi update is doing (evidenced at least by the fact that I was confused by it.)  I recommend something like --no-convert-text-baseline-spacing that will be exceedingly clear.  I don't think the option itself needs to mention the file version; that is a detail that can be reserved to the help text."
1659489,2017-01-29 09:27:53 UTC,"On 2017-01-29 03:33 (+0100), Bryce Harrington wrote on the 'inkscape-devel' mailing list:

>       Since both --do-not-fix-pre-92 and --dpi-update-method relate to
>       the same underlying issue, I bet they could be sensibly combined
>       into a single commandline option.

https://sourceforge.net/p/inkscape/mailman/message/35632831/"
1659489,2017-01-28 06:16:22 UTC,WIP status for lp:inkscape/0.92.x branch:
1659489,2017-01-30 23:15:22 UTC,"`gimp --help` shows that the ""--no-XXX"" phrasing is an established convention for them."
1659501,2017-01-26 09:04:38 UTC,"I’m seeing that on rc-proposed too. I seem to remember that there was a similar bug in the past, that it was fixed, and then regressed again. Not sure when exactly, probably in the last couple of months."
1659507,2017-01-30 16:24:50 UTC,Were you able to sign the agreement to push the patch?
1659507,2017-01-30 19:18:20 UTC,"Nope, still can't sign the agreement..."
1659507,2018-09-28 11:23:53 UTC,"I have since had to sign the agreement, totally forgot about this..."
1659523,2017-01-27 20:05:21 UTC,"That should work, as it is in the terminfo we ship in core. Just in case, can you try with different, less capable TERMs? Start with vt100 for example (see /lib/terminfo for the ones available -- it's not the full set)"
1659523,2019-10-15 11:41:28 UTC,I'm moving this to the subiquity project. Please report a snapd task if you feel there is something that should be improved in snapd itself.
1659523,2017-01-27 02:24:01 UTC,"Sorry, I missed that screen was doing serial work for you. Thanks."
1659523,2017-01-27 00:59:50 UTC,@seth-arnold
1659523,2017-01-26 23:12:13 UTC,"Just curious, does tmux work better?"
1659523,2017-01-26 14:25:14 UTC,@chipaca @zyga
1659523,2017-01-26 10:51:48 UTC,"Please include the name of the terminal emulator and the version of
OSX/macOS used"
1659523,2017-01-26 10:38:59 UTC,Can you tell us what the environment variable TERM is from screen on Mac?
1659534,2020-06-03 11:28:33 UTC,Big thanks guys!
1659534,2019-10-29 18:37:58 UTC,"I inspected snapd and noticed that we don't invoke ""userdel"" or ""deluser"" in any production code. We have some tests that do use it and we now support --extrausers there."
1659534,2019-06-21 11:18:13 UTC,@mvo This fix raised bionic-update's shadow version above cosmic's. Do you plan fixing that or just wait for Cosmic's EOL?
1659534,2019-04-25 10:04:49 UTC,This bug was fixed in the package shadow - 1:4.2-3.1ubuntu5.4
1659534,2019-04-25 09:52:38 UTC,"The verification of the Stable Release Update for shadow has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1659534,2019-04-25 09:52:28 UTC,This bug was fixed in the package shadow - 1:4.5-1ubuntu2
1659534,2019-04-05 19:30:39 UTC,Thank you for taking the time to verify this stable release fix.  We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE).  Please remove the verification-done tag and add one for the release you have tested the package in.  Thank you!
1659534,2019-03-26 19:26:21 UTC,"Hello Matteo, or anyone else affected,"
1659534,2019-03-26 17:03:50 UTC,"Hello Matteo, or anyone else affected,"
1659534,2019-03-25 08:41:13 UTC,This bug was fixed in the package shadow - 1:4.5-1.1ubuntu2
1659534,2019-03-22 19:12:22 UTC,"SRUs for xenial,bionic are uploaded and in the unapproved queue."
1659534,2019-03-22 18:41:13 UTC,This is the fix for disco
1659534,2018-10-17 19:13:35 UTC,Any updates on this?
1659534,2017-03-20 17:49:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659534,2019-04-05 01:36:58 UTC,Validation done on xenial and bionic
1659544,2017-01-26 13:18:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/425682"
1659544,2017-02-13 10:15:15 UTC,"Change abandoned by Yuriy Zveryanskyy (<email address hidden>) on branch: master
Review: https://review.openstack.org/425682
Reason: I think better solution is ""passive"" conductors mode (requests only from IPA side)."
1659544,2018-02-12 16:46:32 UTC,"I'm going to set the status to 'invalid' based on Yuriy's comment in #2. If this is wanted, please update the status. Thanks."
1659544,2018-02-12 16:47:02 UTC,"Oh, sorry, maybe Yuriy didn't like the solution but still wants this feature; leaving as-is."
1659547,2017-01-26 16:33:46 UTC,Your fonts apparently are larger than mine.
1659547,2017-01-26 15:48:20 UTC,"Not reproduced with Inkscape 0.92.0 r15299 (from Inkscape stable PPA) on Ubuntu 14.04.5 LTS, GNOME desktop. Screenshot taken in guest session to avoid any influence of current user's preferences (e.g. with regard to font size for GUI, and other theme-related settings)."
1659547,2017-01-26 16:39:40 UTC,"Related earlier reports:
Bug #1326883 “Opacity value in the bottom left corner is impossible to read.”
Bug #1055253 “Statusbar opacity widget is too small”
Bug #303527 “GUI glitch on opacity box”"
1659552,2017-02-01 11:57:18 UTC,The downside to purging the xserver-xorg-video-intel is that epiphany tends to freeze more often. When it freezes I am unable to load/reload websites or even close the browser.
1659552,2017-01-29 20:32:14 UTC,I found that running this has fixed most of the full screen video artifacts and website component flickering...
1659556,2018-02-28 11:28:29 UTC,It should be fixed by API Validation blueprint
1659556,2019-05-09 08:56:22 UTC,"Problem still exists, restarting the decision-engine service mitigates the issue."
1659563,2017-03-19 10:22:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659563,2017-03-19 10:23:09 UTC,Exact same error message after running a do-release-upgrade from Trusty to Xerial (inside Virtualbox vm)
1659563,2018-03-18 23:13:46 UTC,"I experienced exactly what is described consistently several times within the last few days. The upgrade was attempted from a copy of 14.04 SP1 factory installed on a Dell Inspiron 15 3000 immediately after this computer was acquired. I used the program 'Software Updater' and the suggested update was the only intermediate step. After the failing upgrade to 16.04, I had to reinstall 14.04 from an USB disk produced from the ISO image generated during the initial installation. I repeated this two or three times to make sure I had overlooked nothing, every time with the same result."
1659567,2017-02-21 13:42:08 UTC,Steps to reproduce:
1659567,2017-02-21 23:48:00 UTC,There is no way that I'm aware of in any current Squid.
1659567,2017-02-21 13:52:23 UTC,"@Amos,"
1659567,2017-01-28 21:55:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659567,2017-01-27 10:18:56 UTC,"Thanks for your report - this seems to be an undying issue.
See
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1005257
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1053682
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1166667
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775545"
1659567,2017-01-27 10:32:35 UTC,"squid-deb-proxy is a separate source package. I can look at it, but I think I can do that after upload of squid3 itself, right?"
1659567,2017-01-27 10:19:50 UTC,@racb - I know you are on the squid merge - have you (or could you) have a look at the packaging/generating of this file on the current version you prepare?
1659567,2017-01-27 18:19:05 UTC,"As stated in some of the other bug reports, making any blacklist entry lets the daily warning email go away. I created a file /etc/squid-deb-proxy/pkg-blacklist.d/01-dummy with the single line:
dummy.package"
1659578,2017-04-06 06:29:47 UTC,I am stuck because of this bug as well. Can not build image -
1659578,2017-05-19 08:43:06 UTC,"Yes , I also meet such problem when use the  grub2 options."
1659578,2017-07-05 15:51:12 UTC,"Facing the same issue.
Seems related to this change: https://github.com/openstack/diskimage-builder/commit/003fc17208e645b453ccb7c7ad27d332bdae490c"
1659586,2017-03-20 23:07:19 UTC,This bug was fixed in the package nvidia-graphics-drivers-340 - 340.102-0ubuntu0.12.04.1
1659586,2017-03-20 23:07:23 UTC,This bug was fixed in the package nvidia-graphics-drivers-340 - 340.102-0ubuntu0.14.04.1
1659586,2017-03-20 23:17:24 UTC,This bug was fixed in the package nvidia-graphics-drivers-304 - 304.135-0ubuntu0.16.04.1
1659586,2017-03-20 23:07:17 UTC,This bug was fixed in the package nvidia-graphics-drivers-304 - 304.135-0ubuntu0.16.10.1
1659586,2017-03-20 22:57:12 UTC,This bug was fixed in the package nvidia-graphics-drivers-304 - 304.135-0ubuntu0.14.04.1
1659586,2017-03-20 22:57:17 UTC,This bug was fixed in the package nvidia-graphics-drivers-340 - 340.102-0ubuntu0.16.10.1
1659586,2017-03-20 22:57:10 UTC,This bug was fixed in the package nvidia-graphics-drivers-304 - 304.135-0ubuntu0.12.04.1
1659586,2017-03-20 22:57:20 UTC,This bug was fixed in the package nvidia-graphics-drivers-340 - 340.102-0ubuntu0.16.04.1
1659590,2017-01-26 16:02:31 UTC,lxc.conf with obfuscated IP addresses.
1659590,2017-01-26 17:29:09 UTC,"This is what I get on a trusty vagrant box with latest kernel, lxc and apparmor from trusty-updates:"
1659590,2017-01-27 13:09:54 UTC,Running as root: strace -f -o lxc-execute.log -- lxc-execute --name test -- echo foobar
1659590,2017-02-04 23:18:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659590,2017-02-04 23:20:30 UTC,fwiw: me too - I'm hitting a related bug; same timeframe I assume similar reasons. Debugging now.
1659590,2020-03-26 03:17:34 UTC,anyone still affected by this?
1659590,2020-03-28 23:14:08 UTC,IIRC the issue was gone after upgrading to xenial.
1659591,2019-06-27 08:39:40 UTC,"Once admin changes their password, they will be in the same boat as all other users as a duplicate bug to this one indicates. So the scenario is not limited to non-admin users only I'll rename the report."
1659591,2017-01-31 23:22:59 UTC,Also agreed about the admin password. We should warn and prompt the user to change it.
1659591,2017-01-31 12:55:17 UTC,I agree with the auto login token. We had that in juju-quickstart and I miss that from the cli when I'm already an authenticated user.
1659591,2017-01-31 03:50:49 UTC,"That would require us to record the password, in plaintext, on the user's filesystem. We specifically avoid doing this."
1659592,2017-01-27 10:31:12 UTC,"Hi N-Ronny,
I have never debugged openvpn/pam in that regard myself.
But I hapened to find https://github.com/Yubico/yubico-pam/issues/26 which made me wonder.
The version is clearly older."
1659595,2017-02-10 17:15:30 UTC,There are a number of problems with connecting to different kinds of servers and there is a branch awaiting review that should fix at least some of these.  It is uncertain whether this bug will be fixed by that branch; it will be reviewed after that branch is merged and released.
1659598,2017-01-26 18:53:54 UTC,Does the bug go away if you boot into the previous kernel version?
1659598,2017-01-27 03:32:59 UTC,"The bug is still there if I boot into the previous kernel version (3.19.0-79.87~14.04.1). However, two weeks ago it did not has this bug with the previous proposed kernel (3.19.0-79.87~14.04.1)."
1659598,2017-02-03 18:35:05 UTC,"@taihsiang,"
1659598,2017-02-06 09:00:08 UTC,@brad
1659604,2017-03-21 15:53:20 UTC,"Ah indeed, this is a bug we fixed a little while back now, marking Fix released."
1659604,2017-03-21 13:49:35 UTC,Agreed - I can reproduce the issue with the constraint being removed on LXD without having nova-lxd in the loop at all.
1659604,2017-05-05 15:13:51 UTC,"Stéphane, is this still planned for 2.0.10 and is there a good way to check up on the progress for the Xenial backport of the fix?"
1659604,2017-03-21 07:16:38 UTC,I think the LXD part of the problem is that is removes constraints when another device is added
1659604,2018-05-16 10:27:32 UTC,It sounds like this is probably fixed.  Just need to schedule a test to check if it has been.
1659604,2018-06-04 14:50:33 UTC,Moving to low as it's most likely been fixed; still need to test it.
1659604,2017-03-21 01:12:13 UTC,Closing the LXD side of this since AFAICT there's no problem with LXD enforcing the limit if it's configured properly.
1659604,2017-05-09 20:40:12 UTC,Looks like it will make for the next xenial-proposed release soon.
1659604,2017-03-17 21:37:40 UTC,To elaborate on Darren's comment - I enabled debugging on both nova-compute and lxd on a host that I'm seeing this issue on.  It appears that any activity that adds a drive after the container is created is removing the zfs quota for the root volume.  The lxd debug log has the best information around this..
1659604,2017-03-20 14:17:37 UTC,"OK so the mix of using config-drive might be related (some of my earlier test results where with config-drive enabled for the instances, so that might explain it)."
1659604,2017-03-17 11:17:27 UTC,Tried re-producing on a xenial-newton proposed deployment - however I still see quota being correctly applied to the root disk volume:
1659604,2017-02-09 21:54:28 UTC,"Looking closer at this, I'm not sure this is a bug.  By design, if you provision a machine with nova-lxd, you should *never* manipulate the container using the lxc command. There are *horrible* issues that can result from doing this."
1659604,2017-02-14 15:40:34 UTC,Hello Paul
1659604,2017-03-16 09:57:28 UTC,Did a quick test - container profile (specific to each container) has
1659604,2017-03-16 10:05:21 UTC,"I also tried by adding a separate disk using lxc config device add, and then restarting the container but no quota was applied to the block device."
1659604,2017-03-17 19:59:05 UTC,"I can reproduce this when using ""force_config_drive = True"" in nova.conf.
It appears to only be an issue when the configdrive portion is added to the profile."
1659604,2017-03-16 10:29:46 UTC,Might be mis-reading the LXD codebase but it looks like the quota should be applied:
1659604,2017-03-17 10:46:08 UTC,OK so this is odd - I happened to be testing a xenial-mitaka deployment and for this one I see quota being applied:
1659604,2017-03-17 10:47:04 UTC,(using 13.3.0-0ubuntu1 from xenial-proposed but I can't see any related fixes for this).
1659604,2017-03-16 10:14:56 UTC,We've always managed a profile per container so that everything is one place (and I swear I remember validating this work myself when it was implemented); I also think a size in a profile should be honoured by LXD as well as when adding a specific device.
1659611,2017-01-28 11:26:49 UTC,Is there any additional info I can provide to help?
1659611,2017-02-09 17:13:36 UTC,"Mike:  If you are able, can you try out the linked branch to see whether it fixes your problem?"
1659611,2017-02-13 16:55:54 UTC,"If anyone experiencing this problem can build and try out the linked branch I would be grateful.  You do not need to install it; look at the HACKING file for information on compiling the source.  Note however there is a mistake in the file - when in the build directory the command to run the program is now ./src/pantheon-files.  Make sure that no installed copy of Files is running in the background first, though.   If you use the command ./src/pantheon-files --debug | grep Sidebar some relevant debugging information will show in the terminal."
1659611,2017-02-13 19:54:18 UTC,"Hi Jeremy,"
1659611,2017-02-14 12:56:23 UTC,"Hi Mike,"
1659611,2017-02-15 18:13:46 UTC,Mike:  I have abandoned the branch as the cause of this bug is not what I thought :(
1659611,2017-02-15 21:59:23 UTC,Thank you for your help anyway. I'm pretty bogged down at work at the moment but might try investigating this once I have some free time. Do you have any pointers on where a good place to start might be?
1659611,2017-02-16 17:15:19 UTC,Mike: Does gparted find the NTFS drive before you have manually mounted it?  Do other filemanagers such as Thunar or Nautilus detect when you have plugged in the drive (but not mounted it)?
1659611,2017-02-16 19:27:40 UTC,"Jeremy: Gparted does pick the drive up without me mounting it manually, but interestingly it thinks it has a single ZFS partition!"
1659611,2017-02-18 10:34:36 UTC,I have a small ntfs partition on my internal SSD (created by gparted) which mounts and unmounts fine in Files.  Was your external drive formatted by Windows?  I have not tried that - appears to be a little odd from gvfs point of view which may be causing this problem.
1659614,2017-02-06 08:32:56 UTC,@brad
1659614,2017-02-03 18:35:15 UTC,"@taihsiang,"
1659614,2017-01-27 03:32:42 UTC,"The bug is still there if I boot into the previous kernel version (3.19.0-79.87~14.04.1). However, two weeks ago it did not has this bug with the previous proposed kernel (3.19.0-79.87~14.04.1)."
1659614,2017-01-26 18:54:53 UTC,Does the bug go away if you boot into the previous kernel version?
1659618,2017-06-09 17:12:41 UTC,Yakkety verification:
1659618,2017-05-31 15:10:24 UTC,"Note that the yakkety SRU for this is still in unapproved, so it can't yet be verified."
1659618,2017-05-30 23:13:27 UTC,"ubuntu@ubuntu:~$ apt policy kexec-tools
kexec-tools:
  Installed: (none)
  Candidate: 1:2.0.10-1ubuntu2.2
  Version table:
     1:2.0.10-1ubuntu2.2 500
        500 http://us.ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 Packages
ubuntu@ubuntu:~$"
1659618,2017-05-25 19:00:41 UTC,"Oh, no it's 1:2.0.10-1ubuntu2.1 that failed to build from source, but 1:2.0.10-1ubuntu2.2 is really in -proposed. This was accepted into -proposed without adding a comment to the bug which caused my confusion.  Regardless the bug will need to be reverified for 16.04 with the new version of the package in -proposed."
1659618,2017-05-25 18:40:57 UTC,Chris's comment is also true for Xenial - the armhf version of the package failed to build.
1659618,2017-05-24 00:15:32 UTC,"While this has passed testing on arm64, it introduces a FTBFS regression in the armhf package on Yakkety: https://launchpad.net/ubuntu/+source/kexec-tools/1:2.0.10-2ubuntu1.1/+build/12076905"
1659618,2018-06-11 12:23:07 UTC,This bug was fixed in the package kexec-tools - 1:2.0.16-1ubuntu1~16.04.1
1659618,2017-03-21 17:26:08 UTC,"test login: [  146.606156] cloud-init[1023]: Cloud-init v. 0.7.9 running 'modules:config' at Tue, 21 Mar 2017 17:23:44 +0000. Up 143.57 seconds.
[  168.868544] cloud-init[1161]: Cloud-init v. 0.7.9 running 'modules:final' at Tue, 21 Mar 2017 17:24:06 +0000. Up 165.37 seconds.
[  168.914038] cloud-init[1161]: Cloud-init v. 0.7.9 finished at Tue, 21 Mar 2017 17:24:10 +0000. Datasource DataSourceNoCloud [seed=/dev/vda][dsmode=net].  Up 168.67 seconds
[  231.987676] kexec_core: Starting new kernel
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.10.0-10-generic (buildd@bos01-arm64-046) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #13~ubunturc2+build.1-Ubuntu SMP Tue Feb 28 23:33:09 UTC 2017 (Ubuntu 4.10.0-10.13~ubunturc2+build.1-generic 4.10.0)
[    0.000000] Boot CPU: AArch64 Processor [411fd070]"
1659618,2017-03-21 16:52:03 UTC,[Yakkety Proposed Testing]
1659618,2017-03-21 14:45:31 UTC,"[Xenial Proposed Testing]
ubuntu@ubuntu:~$ sudo apt policy kexec-tools
kexec-tools:
  Installed: (none)
  Candidate: 1:2.0.10-1ubuntu2.1
  Version table:
     1:2.0.10-1ubuntu2.1 500
        500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 Packages"
1659618,2017-03-02 17:51:37 UTC,"Hello Manoj, or anyone else affected,"
1659618,2017-03-02 17:47:31 UTC,"Hello Manoj, or anyone else affected,"
1659618,2017-02-14 14:52:44 UTC,The attached patch is for:
1659618,2017-02-07 16:17:28 UTC,"[Testing on VM]
== Default kernel on Yakkety ==
ubuntu@test:~$ uname -a
Linux test 4.8.0-37-generic #39-Ubuntu SMP Thu Jan 26 02:26:41 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@test:~$"
1659618,2017-02-10 18:04:46 UTC,"The attached patch has the complete set of patches needed for kexec support on ARM64.
  * kexec: Increase the upper limit for RAM segments [LP: #1663400]
  * Enable compressed kernel support for ARM64 [LP: #1661363]
  * Enable ARM64 support [LP: #1659618]"
1659618,2017-01-26 19:02:00 UTC,Thanks Manoj! A few comments on your prepared package.
1659618,2017-01-26 19:20:10 UTC,Updated changelog to refer to LP: #1659618
1659618,2017-01-26 19:23:48 UTC,[TESTING ON ARM64 HARDWARE]
1659618,2017-02-10 19:19:00 UTC,"The attached patch has the complete set of patches needed for kexec support on ARM64.
* Enable ARM64 support in kexec-tools (LP: #1659618)
* Enable support for compressed kernels on ARM64 (LP: #1661363)
* kexec: Increase the upper limit for RAM segments (LP: #1663400)"
1659618,2017-01-26 20:28:32 UTC,"The attachment ""updated debdiff - changelog referring to LP# 1659618"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1659618,2017-01-26 19:25:48 UTC,The above test was that of the kexec-tools package that includes review comments from dannf.
1659618,2017-02-07 16:41:39 UTC,"[AMD64 regression testing]
[Testing with stock Yakkety kernel & kexec-tools]"
1659618,2017-02-07 19:37:03 UTC,Please note that the previous debdiff patch I attached introduced some spurious changes by accident. Here is a cleaner version of the debdiff patch for Yakkety. I applied this patch to Yakkety kexec-tools and I was able to build and test.
1659618,2017-02-07 19:58:56 UTC,"Please ignore my previous comment, I introduced an err in the changelog. Please use this cleaned up version of the patch."
1659618,2017-02-07 21:59:08 UTC,I was able to apply this patch and build kexec-tools on Xenial. Please see this link for details: https://pastebin.ubuntu.com/23950298/
1659618,2017-02-07 22:19:17 UTC,"[Regression testing on Xenial AMD64]
AMD64 kernel already has kexec support on Xenial. The attached patch applies cleanly and builds on AMD64: https://pastebin.ubuntu.com/23950437/"
1659618,2017-02-01 21:31:08 UTC,This bug was fixed in the package kexec-tools - 1:2.0.14-1ubuntu1
1659620,2019-08-07 19:14:31 UTC,"Running Ubuntu 18.04 with openstack-dashboard 14.0.3-0ubuntu1~cloud0 and having issues with certain modals not working (create object container, create keypair, upload keypair, create server group) all popping up as blank modals. This has been a chronic issue for us for Ubuntu 16.04 and also 18.04 spanning multiple OpenStack releases but when we first upgraded to Rocky these issues were gone. We did not seem to have any issues with openstack-dashboard 14.0.2-0ubuntu4~cloud0 and this was very surprising to see however we recently upgraded to 14.0.3-0ubuntu1~cloud0 and we are now having these issues with broken modals again."
1659620,2018-09-17 07:32:15 UTC,"The dashboard acts weird in Rocky too, Ubuntu 18.04 LTS"
1659620,2018-06-14 13:23:30 UTC,Also broken in queens:
1659620,2018-02-19 15:46:58 UTC,Seems it is broken in Pike.
1659620,2017-09-25 10:00:02 UTC,"Yes, openstack-dashboard is broken with respect to additional dashboard packages in Newton or earlier. This was fixed for Ocata, please try with a newer UCA version whether the issue still exists there. The fix cannot be backported to Newton without breaking existing installations."
1659620,2017-02-06 13:22:16 UTC,I think this is an issue with the Ubuntu package for the main dashboard package - there is wierdness in the manage.py collect and compress steps.
1659620,2017-02-07 16:00:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659620,2017-01-30 17:59:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659623,2017-01-26 18:31:24 UTC,This change was made by a bot.
1659623,2017-01-26 20:16:26 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 stable kernel[0].
1659623,2017-02-02 20:52:07 UTC,"I tested both 4.8.17 and 4.9.6 mainline kernel, shutdown/reboot both works fine there. However 4.8.0-34-generic Ubuntu kernel still has the problem."
1659623,2017-02-06 20:07:23 UTC,"Would it be possible for you to test this latest kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1659623,2017-02-09 20:22:11 UTC,"If I choose the right version, shutdown and reboot went normal on kernel version 4.8.0-38-generic."
1659623,2017-02-11 02:53:09 UTC,"I was experiencing the exact same issue on my Precision 7510 under Xenial, after transitioning to the rolling HWE & Kernel stack. On a hunch I added the Canonical Kernel Team PPA (https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages) so I could upgrade from kernel 4.8.0-36 to 4.8.0-37. Now shutdown and reboot are working perfectly. Not sure if I should file a separate bug report."
1659641,2017-05-31 15:54:35 UTC,"this was merged in requirements, closing"
1659641,2017-07-17 12:04:00 UTC,This issue was fixed in the openstack/requirements 1.1.0 release.
1659641,2017-01-27 15:34:58 UTC,"Change to global requirements (https://review.openstack.org/#/c/425950/) will have to wait until after feature freeze.  In the meantime, we can either pass an empty string as the request body ""-d ''"" or pass the header ""Content-Length: 0""."
1659641,2017-01-26 22:16:35 UTC,It's an upstream bug https://github.com/Pylons/webob/issues/233 fixed by https://github.com/Pylons/webob/pull/283 which is in WebOb>=1.7.0
1659641,2017-01-26 21:20:12 UTC,This is probably a pecan bug.  I've submitted a Github Issue in the pecan project https://github.com/pecan/pecan/issues/87
1659642,2019-09-19 15:03:53 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1659661,2017-01-26 21:45:34 UTC,Additionally an added backtrace of the Error:
1659676,2018-05-04 06:23:50 UTC,"Whoops, just checked the latest xenial systemd source package and mistakenly thought I saw the patch had already been pulled. Please pull this."
1659681,2017-01-27 13:31:05 UTC,"Could you provide rally json settings file, which you used for these tests?"
1659681,2017-01-27 18:09:40 UTC,"---
  CinderVolumes.create_and_extend_volume:
    -
      args:
        size: 1
        new_size: 2
      runner:
        type: ""constant""
        times: {{ compute * 14 }}
        concurrency: {{ concurrency }}
      context:
        users:
          tenants: {{ compute * 2 }}
          users_per_tenant: 3
        quotas:
          cinder:
            volumes: -1
            gigabytes: -1
            snapshots: -1
        api_versions:
          cinder:
            version: 2
            service_name: cinderv2
      sla:
        failure_rate:
          max: 0"
1659681,2017-06-20 11:28:23 UTC,"I'm seeing some cinder db deadlocks which can occur when creating and deleting cinder volumes. Are you sure you have
connection = mysql+pymysql://cinder:<pw>@<host>:<port>/cinder
instead of:
connection = mysql://cinder:<pw>@<host>:<port>/cinder
in your cinder.conf?"
1659684,2017-01-26 23:37:00 UTC,"Just to note, 'mountall' also clears that mtab entry, but it also nukes contents of /tmp in the process, which might not be good if someone is running Passenger, which apparently keeps socket files in there (i.e. /tmp/passenger.1.0.xxx/generation-0/request )"
1659684,2017-03-24 13:23:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659684,2017-09-10 22:49:40 UTC,"Since it seems this bug manifests itself only after certain 'apt upgrade' runs that call ureadahead triggers, would backporting the fix from Vivid ureadahead package ver. 0.100.0-19 be an option to resolve it?
I'm thinking of the fix for https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/777224 and the non-systemd change done to http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/ureadahead/vivid/revision/32#debian/rules"
1659689,2019-09-11 06:08:11 UTC,The workaround does not seem to work on Ubuntu 18.04
1659689,2020-04-29 20:19:19 UTC,The package used to work in GUI mode in 18.04 at least. In 20.04 it has stopped working in any capacity. This has officially become un-usable. I think the priority needs to be raised
1659689,2017-11-25 19:34:58 UTC,"Workaround: add ""-a"" to command line"
1659689,2017-02-10 03:19:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659692,2017-01-27 00:02:00 UTC,MAAS Version 2.1.2+bzr5555-0ubuntu1 (16.04.1) is the current Ubuntu Version I am running.
1659692,2017-01-27 00:55:05 UTC,Thanks for reporting this bug. I see two possibilities here:
1659692,2017-01-27 01:43:15 UTC,"I did rerun commission and even had it marked as Broken and than fixed without luck.
And no it's not a refresh issue either."
1659692,2019-09-19 15:03:56 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1659699,2017-01-27 10:43:28 UTC,"Following the github link that you posted, and another link or two from there, a clear conclusion is presented as for why this bug occurs."
1659699,2017-01-27 10:46:04 UTC,Correction: Ubuntu (and other distributions) should _not_ ship ...
1659699,2017-01-27 10:47:05 UTC,Probably the best solution for Zesty is to update glibc to also use Unicode 9.0.
1659701,2017-01-27 04:27:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1659701,2017-02-26 17:17:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659709,2018-04-24 16:52:38 UTC,This issue persists in 3.1
1659709,2018-01-19 20:56:18 UTC,Confirmed on 3.0 and 3.0.2 web client
1659710,2017-10-03 08:40:37 UTC,"As Boden noted, the patch that triggered this bug included a documentation update in the devref folder.
Should this bug be marked as invalid?"
1659710,2017-01-30 16:18:35 UTC,"Best I can tell, there's nothing needed herein from a neutron doc (devref or apiref) POV. The respective change that generated this bug already contained devref updates [1]."
1659710,2017-09-12 22:15:19 UTC,Moving to neutron as per doc migration.
1659712,2017-01-27 02:27:15 UTC,The log as promised.
1659712,2017-02-03 02:37:25 UTC,I am seeing top level exception being raised occasionally:
1659712,2017-02-09 22:46:04 UTC,I note that the replicator refuses to shutdown via 'service swift-object-replicator stop'. Doings an strace of what it is doing shows:
1659712,2017-02-09 23:03:37 UTC,The attached log is showing a bunch of replication contention - but that's frankly pretty common during a large rebalance.
1659712,2017-02-15 01:31:36 UTC,"To check the concurrency thing I reduced replicator concurrency to 4. It took longer, but I have a hang again."
1659712,2017-02-15 01:35:50 UTC,"...and I should have added:
$ ps auxww|grep 143938
markir   113603  0.0  0.0  10444  2180 pts/0    S+   14:34   0:00 grep 143938
swift    143938  4.8  3.7 3975872 2448772 ?     Ssl  Feb10 362:53 /opt/cat/openstack/swift/bin/python /usr/bin/swift-object-replicator /etc/swift/object-server.conf"
1659712,2017-03-23 21:59:48 UTC,"We have made some changes:
- reducing object replicator and updater concurrency to 4
- increasing rsync and lockup timeouts timeouts"
1659716,2017-01-31 18:48:02 UTC,Thanks again Hans.
1659716,2017-01-31 23:19:45 UTC,Ubuntu 16.04 x86_64 tested OK this afternoon. Thanks again.
1659719,2017-01-27 06:08:11 UTC, /etc/profile.d/apps-bin-path.sh does not fire on noninteractive logins.
1659719,2017-01-27 03:14:58 UTC,Why is the PATH being set via login shells rather than e.g. init's environment variables or PAM environment mechanism? What led to setting the environment variables via shell startup scripts?
1659719,2017-01-27 10:14:51 UTC,@seth because it is dynamically shipped with the snapd package for classic installs so PATH gets automatically extended with install/removal of the snapd package.
1659719,2017-01-27 03:10:31 UTC,This affects the mosh snap: https://github.com/elopio/mosh/blob/snapcraft/snapcraft.yaml
1659719,2017-01-27 03:11:03 UTC,Comment from ogra in the mailing list:
1659719,2017-01-27 12:35:54 UTC,so with todays edge core snap it now looks like:
1659719,2017-09-20 17:00:35 UTC,Yes it obviously works for login shells.
1659719,2017-09-20 16:37:48 UTC,this has been fixed long ago and you should have an /etc/profile.d/apps-bin-path.sh file that adds /snap/bin to your PATH
1659719,2020-07-28 17:45:44 UTC,"Hello Leo, or anyone else affected,"
1659719,2020-07-28 22:12:47 UTC,"All autopkgtests for the newly accepted pam (1.1.8-3.6ubuntu2.18.04.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1659719,2020-08-20 23:01:23 UTC,Verified on focal:
1659719,2020-08-20 23:05:12 UTC,The focal autopkgtest failures are in cyrus-imapd:
1659719,2020-08-20 23:14:57 UTC,And bionic:
1659719,2020-08-25 16:28:44 UTC,This bug was fixed in the package pam - 1.1.8-3.6ubuntu2.18.04.2
1659719,2020-07-23 14:46:28 UTC,"All autopkgtests for the newly accepted pam (1.3.1-5ubuntu4.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:"
1659719,2020-08-25 16:44:22 UTC,If kopanocore is known to be flaky on armhf please add a hint for it to https://code.launchpad.net/~ubuntu-sru/britney/hints-ubuntu-focal/.
1659719,2020-09-29 19:26:37 UTC,The fix for this in the queue for Xenial is help up by the verification of bug 1666203.
1659719,2020-09-30 21:10:04 UTC,"An upload of pam to xenial-proposed has been rejected from the upload queue for the following reason: ""needs sourceful fixes for the version previously in -proposed""."
1659719,2020-10-01 00:32:38 UTC,"Hello Leo, or anyone else affected,"
1659719,2020-10-01 04:12:09 UTC,"All autopkgtests for the newly accepted pam (1.1.8-3.2ubuntu2.3) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:"
1659719,2020-10-01 08:31:48 UTC,And verified on xenial:
1659719,2020-10-12 13:17:34 UTC,This bug was fixed in the package pam - 1.1.8-3.2ubuntu2.3
1659719,2020-08-31 12:55:47 UTC,This bug was fixed in the package pam - 1.3.1-5ubuntu4.1
1659719,2020-07-23 10:44:23 UTC,"Hello Leo, or anyone else affected,"
1659719,2020-08-25 16:28:53 UTC,"The verification of the Stable Release Update for pam has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1659719,2020-07-09 00:28:50 UTC,I've filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964580 about the pam ordering issue.
1659719,2018-06-18 13:20:45 UTC,"Adding a task against the Ubuntu snapd package for the non-interactive shell case (eg. ssh), since this still affects Ubuntu the distribution on this point."
1659719,2018-06-18 13:21:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659719,2018-06-18 16:31:46 UTC,"I'm very reluctant to reconfigure openssh for this; it feels like a layering violation, and a regression of all the work we did way back when to avoid having to change umpteen packages when we want to change the default command search path."
1659719,2019-08-28 01:26:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659719,2020-05-13 14:21:18 UTC,"This is fairly problematic when core functionality that is orchestrated in the cloud moves from deb to snap. In our example, lxc (LXD command line tool) was assumed to be in the path when building the orchestration. Using the full path makes it less portable. It also makes managing multiple releases a pain since some hosts may run the snap, others installed by dpkg."
1659719,2020-05-13 20:56:16 UTC,I know that work was done to ensure /snap/bin was in the default path for systemd itself and that this should be inherited now by all units.  'systemd-path | grep search-binaries:' shows that it's there on my focal system.  'sudo ps axewwww | grep sshd' also shows that it's set in the PATH environment of the sshd parent processes.  So I'm not sure what is still resetting the PATH for noninteractive ssh sessions.
1659719,2017-09-19 21:56:36 UTC,Still hitting this with...
1659719,2020-05-13 21:02:54 UTC,"It looks like the likely cause here is that sshd loads pam, which calls pam_env, which reads /etc/environment, which has a different PATH than the default one provided by systemd."
1659719,2020-05-14 13:32:15 UTC,"+1, tweaking /etc/environment makes it work. It seems that this has to be fixed in the libpam-modules postinst script then."
1659719,2020-07-03 02:44:07 UTC,"It's easy enough to unconditionally add /snap/bin to path, see attached, but I can't really see a clean way to only have it present in the $PATH when snapd is installed (without code changes to pam_env, anyway)."
1659719,2020-07-03 09:31:42 UTC,That won't be too different from /usr/local/sbin and /usr/local/bin being in the PATH but empty I think. I am not aware of any problem or annoyance caused by nonexisting directories being in the PATH.
1659719,2020-07-08 16:01:49 UTC,"Given Colin's comment 12, it doesn't look like there are any plans to change this in openssh packaging so I'll mark this Won't Fix."
1659719,2020-07-08 16:34:46 UTC,The inconsistency between login and openssh session module ordering is still an issue. Reopening.
1659719,2020-07-09 00:09:17 UTC,Here's a better patch that I've tested this time. I dropped the code around adding /usr/local/games to PATH as that was in trusty.
1659719,2020-07-15 05:20:30 UTC,This bug was fixed in the package pam - 1.3.1-5ubuntu5
1659721,2017-01-27 03:28:21 UTC,Although such hysteresis should be time-based too. If the mouse button has been held for a second already then using space-based hysteresis is not helpful.
1659721,2017-01-27 03:13:52 UTC,"Hmm, this is probably just a threshold to avoid accidental flicks when clicking. But the threshold is too high. It's annoying."
1659724,2017-01-27 12:39:28 UTC,Makes sense to me.
1659724,2017-02-01 14:19:27 UTC,I also think this is reasonable.
1659724,2017-02-07 13:55:57 UTC,This is merged in trunk and will be in snapd 2.23.
1659744,2017-01-27 08:16:34 UTC,https://github.com/snapcore/snapd/pull/2710
1659744,2017-01-27 08:17:45 UTC,"That branch isn't the end of the work in this space, but it addresses this immediate issue. The error message still needs picking up by the client and presented to the user better, and some other operations that take --classic need similar work."
1659747,2017-02-14 11:29:13 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433600"
1659747,2017-02-15 16:38:14 UTC,Here again https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.test_ibp/129/console
1659747,2017-03-02 10:05:46 UTC,"The bug is related to non-root access feature which was implemented with ""workaround"" for fuel-devops 2.9.x. And for now the proposed fix unblocks only part of failed tests. The full normal fix requires fuel-devops 3.0.3"
1659747,2017-03-09 08:43:11 UTC,"Reviewed:  https://review.openstack.org/433600
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=e4a2acfc23d8f2ceddd0b2af1f002a0c57ca89e4
Submitter: Jenkins
Branch:    stable/newton"
1659747,2017-03-10 10:37:15 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/444203"
1659747,2017-03-10 10:37:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444204"
1659747,2017-03-23 12:52:24 UTC,"Reviewed:  https://review.openstack.org/444204
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=45e773d9dbd8ac9c85e3f11eb80b85edfcc12692
Submitter: Jenkins
Branch:    master"
1659747,2017-03-23 13:02:31 UTC,"Reviewed:  https://review.openstack.org/444203
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=7e38e370d4a8981c4fa792013f43aeec05a63564
Submitter: Jenkins
Branch:    stable/ocata"
1659750,2017-04-07 11:51:10 UTC,"I think I may have the same problem as this, symptoms are similar."
1659750,2017-02-06 20:04:00 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1659750,2017-01-31 11:11:16 UTC,"By 4.10-rc6 Network Manager tells ""Wi-Fi is disabled"" even if I check ""Enable Wi-Fi""."
1659750,2017-01-30 15:37:54 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1659750,2017-01-31 10:39:14 UTC,"By 4.4.0-22 network manager tells ""Wi-Fi is disabled"" whereas in 4.4.0-51 and later it tells ""device not ready"". I do not remember, if this happened after update, but Wi-Fi used to work by the previous kernels before."
1659750,2017-01-27 09:27:14 UTC,"I also tried to boot from live USB, both 14.04.1 and 16.04.1 and same thing.
I could not switch wireless on by ""Fn + F5"" in Linux
https://support.lenovo.com/fi/en/documents/migr-63140"
1659750,2017-01-27 08:30:16 UTC,This change was made by a bot.
1659775,2017-04-19 08:19:38 UTC,"if it is a bug and can't be fixed, would you provide a solution or a way to remove this package?"
1659779,2017-01-27 19:00:45 UTC,Where it fails on E4.5
1659779,2017-01-27 20:15:59 UTC,What version of Oxide? I've just tried Here Maps on my E4.5 with Oxide 1.19.7 and it's working fine.
1659779,2017-01-27 20:46:54 UTC,OTA 14 has oxide 1.17.9
1659779,2017-01-29 21:22:55 UTC,"Pat: how exactly do you see it fail? I’ve just tried on my MX4, and I’m only getting a blank page, but that’s yet another symptom of bug #1656551. On my E4.5 running oxide 1.19.7, the app works fine."
1659783,2017-01-27 10:33:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659783,2017-01-27 10:46:51 UTC,"Hi Jean-Baptiste, thanks for reporting this bug, the changes are proposed in https://github.com/snapcore/snapd/pull/2734"
1659800,2017-01-30 12:10:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659803,2017-02-02 11:15:41 UTC,We'll probably want to work this into charms.openstack and the base openstack charm layer; that way we can enable it globally across all new reactive charms.
1659803,2017-02-02 11:12:38 UTC,"Steps to do this:
https://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/hardening/README.hardening.md"
1659804,2017-01-27 11:16:42 UTC,P.S.: I am not able to report this bug under https://bugs.launchpad.net/charms/+source/designate-bind/+filebug
1659804,2017-02-02 12:23:31 UTC,Similar to: https://bugs.launchpad.net/charm-designate/+bug/1659803
1659811,2017-01-27 15:01:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/426259"
1659811,2017-02-07 19:41:06 UTC,"Reviewed:  https://review.openstack.org/426259
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f702762934e0a46449091243a39ad5d57108b23f
Submitter: Jenkins
Branch:    master"
1659811,2017-02-08 02:03:44 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/430504"
1659811,2017-03-08 12:33:19 UTC,"Reviewed:  https://review.openstack.org/430504
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c992c7a172af0890c9fea147e018257ee018f2d
Submitter: Jenkins
Branch:    stable/ocata"
1659811,2017-03-15 11:15:53 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1659811,2017-04-14 09:24:27 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1659820,2017-06-11 21:26:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659824,2017-01-28 15:13:22 UTC,"Sorry, I misunderstood the bug description and I see your points now."
1659824,2017-01-27 17:54:05 UTC,"On 2017-01-27 14:03, Chris Perry wrote:

> ""Take Screenshot"" isn't a window, it's a section of a window.
"
1659824,2017-01-28 09:22:06 UTC,"Hi Gunnar, I'm running 16.04. My points simply relate to terminology. The window has the title ""Screenshot"" so surely it doesn't make sense for the page to say ""In the Take Screenshot window ...""?"
1659830,2017-01-27 18:34:20 UTC,"yes I see the same, thanks for reporting it, we are unsure what triggers it since not everyone can reporduce"
1659830,2017-01-27 18:33:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659836,2017-02-06 18:48:13 UTC,"What exactly is Nova doing, that it can't do with the node locked? If nova is telling it to delete, it should be OK with seeing CLEANING or CLEAN WAIT after a delete to indicate it's deleted."
1659836,2017-02-07 10:59:08 UTC,_unplug_vifs which is called inside of _cleanup_deploy requires an unlocked node:
1659836,2017-02-07 10:59:35 UTC,https://review.openstack.org/#/c/422678/
1659836,2017-03-01 13:07:07 UTC,"Moved this to nova, as the fix is actually there."
1659836,2017-03-15 21:47:00 UTC,"Change abandoned by Sam Betts (<email address hidden>) on branch: master
Review: https://review.openstack.org/422678
Reason: Won't work."
1659836,2017-09-05 15:05:50 UTC,"Change abandoned by Sam Betts (<email address hidden>) on branch: master
Review: https://review.openstack.org/422678
Reason: reabandoning"
1659846,2017-05-30 22:33:35 UTC,"This is a false positive in sudo. What's happening is that sudo is taking an error from the program it executed and propagating out to the calling shell. Thus when a called application aborts (i.e. SIGABRT), it also triggers an abort for sudo."
1659846,2017-05-30 22:37:17 UTC,"Durr, wrong copy-pasta, the actual command is:"
1659846,2017-05-30 23:03:35 UTC,And in fact this is covered by bug 1565332.
1659851,2018-01-02 12:29:38 UTC,I got that after installing chrome via GUI
1659851,2018-01-02 12:25:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659853,2017-02-22 11:30:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659855,2018-01-02 12:24:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659858,2017-01-31 02:04:21 UTC,Seems to be the same / similar issue as bug 1648534
1659858,2017-08-30 21:47:24 UTC,Closing as this is better handled in errors.ubuntu.com.
1659858,2018-01-30 09:43:17 UTC,It just happened to me on bionic and the system is apparently not running out of file descriptors.
1659858,2018-04-03 11:46:44 UTC,bug #1760795 could be the fd leak issue
1659861,2017-01-27 14:40:04 UTC,"Also 'conjure-up' not ""conjure-up"". Use double-quote for quoted speech and single quotes for a term or a name, as in this case."
1659861,2017-08-18 09:16:11 UTC,I'm marking this as confirmed since we still (as of snapd 2.27.2) show the full (ugly and long) URL we attempted to get when the network connection fails for some reason.
1659868,2018-01-17 07:37:30 UTC,https://github.com/snapcore/snapd/pull/4498
1659868,2019-10-29 21:57:58 UTC,The referenced pull request was merged into master and this bug is no longer affecting autopkgtest. I'm marking it as fix released.
1659869,2017-01-27 15:42:33 UTC,"Yes, for each panel in a window, focus should go through that panel’s header, then to the panel body (so you can select something in it if it’s a list, or else just scroll through it), then to the panel footer if there is one (such as the “Write a message” field). That should happen without any effort by the app developer."
1659869,2017-01-27 15:11:11 UTC,"I agree about the focus order within a page (not sure which page should have focus first though). But I think this will be valid for all apps, so we don't need to make it configurable, just fix the current focus order."
1659876,2017-08-04 09:44:52 UTC,fixed in https://review.openstack.org/#/c/427376/
1659876,2017-08-15 08:49:56 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1659876,2017-02-01 11:37:50 UTC,Also as part of this change we'd need to move all testing scripts to use the new JSON/YAML format for baremetal inventory as the legacy CSV format that is used now lacks support for setting the IPMI port which we need to have for virtualbmc.
1659883,2017-01-27 17:54:37 UTC,"""mixxx -f"" is your fiend ;-)"
1659883,2017-01-27 22:42:06 UTC,"@daschuer: it's not maximized, it's full screen. I am using Ubuntu and in that case it means to hover the sidebar. I don't want that."
1659883,2017-01-27 23:24:11 UTC,I cannot confirm this using Cinnamon on Ubuntu Trusty. It starts Mixxx how it was closed.
1659883,2017-01-28 05:28:14 UTC,Here how it looks at my PC: http://stunkit.com/data/files/2017-01-28%2007-18-26.flv
1659883,2017-01-28 05:30:41 UTC,"And yes, exit code is 0."
1659883,2020-05-03 21:55:30 UTC,This is fixed now.
1659886,2017-06-03 22:54:14 UTC,"This issue is fixed in 16.10 where the screen is turned on with black background and shows a blurry cursor. Since support for powerpc has been dropped from 17.04 on and will be continued for updates in 16.04 only, it doesn't make sense to pursue this issue any further."
1659890,2018-01-28 13:30:28 UTC,"Having a similar problem on Ubuntu 16.04 LTS. The module ""UnityTweakTool"" being missing seems to be the problem, even after reinstall. Here is my traceback:"
1659893,2017-02-05 18:25:02 UTC,UPDATED INFO:   This is on Linux Mint KDE 18.1
1659893,2017-02-13 18:38:41 UTC,SMALL UPDATE:  First error “GTK-WARNING ... adwaita”. Install package 'gnome-themes-standard' as described above.
1659900,2017-01-27 17:44:58 UTC,Thanks for the feedback Tony.
1659901,2020-03-24 04:17:21 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1659901,2019-03-28 11:59:26 UTC,"Hi -- I believe we fixed the Java crashes as part of work done for the 2.12 release (and perhaps 3.0, I forget). Does this still reproduce with the most recent release of QEMU (eg the 4.0 release candidate) ?"
1659901,2017-02-01 22:17:17 UTC,"Additional investigation reveals the problem has something to do with the Azul ARM32 JIT. If I run Java with -Xint to force interpreter-only mode, this problem doesn't occur."
1659901,2017-10-11 03:36:23 UTC,Similar issue reported in two other places on the net:
1659901,2017-11-15 22:58:48 UTC,"fyi, similar seen for Raspbian9:"
1659903,2017-01-27 17:39:28 UTC,It seems similar to bug 1659758 that I'm experiencing since the beginning of this week.
1659903,2017-01-27 18:01:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659903,2017-02-03 13:50:42 UTC,I'm experiencing a similar issue. in my case I'm running Zesty with unity8-session-snap version 392. The drawer is completely empty: http://picpaste.com/Screenshot_from_2017-02-03_10-44-49-1kuLoaut.png
1659903,2017-02-07 08:52:43 UTC,Still happening with u8-session 414
1659903,2017-03-30 21:19:10 UTC,"So this is ""by design"" in the unity8 snap. It doesn't have information on what is stored on the classic system. It will only have either apps that are in the snap or installed as snaps in the drawer. It can't run or query the others. This makes sense as the unity8-session-snap is only expected to be used on core systems that wouldn't have debs installed."
1659904,2017-01-27 18:28:11 UTC,"You can look for a similar lock file for system settings, also try deleting the QML cache."
1659904,2017-01-27 17:25:22 UTC,Update
1659904,2017-01-27 19:45:26 UTC,Hi Pat
1659905,2017-01-27 17:31:01 UTC,This change was made by a bot.
1659907,2017-01-29 21:29:25 UTC,"I guess this happens because the NIC is down and so you can't scan for
networks. Need to up the NIC first (I already do this when console-conf
starts so it shouldn't be too hard)."
1659909,2017-02-01 19:27:55 UTC,This fix has been merged already.
1659909,2017-03-21 21:26:46 UTC,This issue was fixed in the openstack/python-brick-cinderclient-ext 0.4.0 release.
1659910,2017-01-27 18:01:30 UTC,"Just to quickly add to the above, It seem to have an issue with the device_owner being detected as 'network:router_interface_distributed'"
1659910,2017-08-15 11:52:47 UTC,You are probably using such old version that does not have fix https://github.com/openstack/ospurge/commit/d18f6617b476ca667c468104d76b0c205551d6a1
1659912,2017-01-27 18:06:58 UTC,it's a fuel bug. it should not deploy agents on controllers when contrail is used.
1659915,2020-04-28 04:17:25 UTC,[Expired for ubuntu-dev-tools (Ubuntu) because there has been no activity for 60 days.]
1659915,2019-02-12 21:18:44 UTC,Is this still reproducable for anyone?
1659915,2017-09-13 21:27:41 UTC,The code in python3-ubuntutools seems to do the right thing when we pull a package:
1659915,2017-09-12 23:34:05 UTC,"OK, I think I figured it out (lots of indirection here):"
1659915,2018-03-01 14:16:26 UTC,"Nish, Robie, I've rewritten pull-*-* and much of ubuntutools/archive.py, if this is still a problem for you please test with my build for bug 1453330 and let me know."
1659915,2017-04-10 23:35:26 UTC,afaik we have no dependencies on anything over the network except Launchpad.
1659915,2017-01-27 17:58:54 UTC,Although tracker.debian.org is reachable again.
1659915,2017-01-27 17:58:30 UTC,"It's working again now, so I'm not absolutely confident that this problem actually exists."
1659915,2017-08-02 16:32:21 UTC,"We think it is likely that the library call to ""pull-debian-source"" that the importer uses is causing this, and we'd prefer for the importer to depend and download from Launchpad only. So this needs further investigation."
1659918,2017-01-27 18:30:12 UTC,This change was made by a bot.
1659918,2017-01-31 11:28:19 UTC,"On INIT_TASK(tsk) fuction missing task arg from follow items of structure
    INIT_IDS                                                        \
                                                  \
        INIT_TRACE_IRQFLAGS                                             \
        INIT_LOCKDEP                                                    \
        INIT_FTRACE_GRAPH                                               \
        INIT_TRACE_RECURSION                                            \
                                            \"
1659935,2017-03-13 13:08:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659938,2017-09-03 01:14:30 UTC,"Ok, so now with Fedora 26 the icon has the right size, but the blue icon still gets overwritten by the grey one – could you please take a look into this?"
1659938,2017-02-02 18:21:06 UTC,Thank you for reporting this issue.
1659938,2017-02-09 22:42:23 UTC,"Hi Moritz,"
1659938,2017-02-10 19:59:18 UTC,"Hmm, I don't know why the icon is squeezed."
1659938,2017-02-10 23:34:08 UTC,"I'm sure SVG would be the better solution, but Fedora has several bugs at the moment, I'll wait some time."
1659950,2017-01-30 15:00:19 UTC,"Researching more, I see POSIX has NO way to disable mtime updating while calling write()'s, so there is no way to atomically leave a partial file with an mtime=0 mark while using --inplace."
1659950,2017-01-29 03:58:20 UTC,"rsync version:  rsync  version 3.1.1  protocol version 31
ubuntu version: 3.1.1-3ubuntu1"
1659950,2017-01-27 21:35:00 UTC,A reproducible test:
1659952,2017-01-28 00:32:03 UTC,can you clarify command executing?
1659952,2017-01-28 01:39:23 UTC,The actual command that executes is
1659952,2017-01-28 02:50:42 UTC,can you find in file /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/dapper.py next string:
1659952,2017-01-28 03:35:25 UTC,"Yup, that does it. The VM build successfully with the force-confnew option."
1659952,2017-01-28 04:31:42 UTC,I've created fix: https://code.launchpad.net/~vanzhiganov/vmbuilder/vmbuilder/+merge/315834
1659952,2017-03-24 15:30:45 UTC,I've encountered the same bug and I confirmed that the fix above did resolve my issue.
1659952,2017-09-21 14:44:56 UTC,When will this fix be released? This is very annoying.
1659952,2018-06-14 10:44:42 UTC,You can find the fix there: https://askubuntu.com/a/824159/434621
1659955,2017-01-30 13:11:57 UTC,"settings to critical, it's blocking test automation."
1659958,2017-10-10 10:09:15 UTC,I have tested with network spaces and I am not seeing None in the configuration. Could you please paste the bundle being used for the deploy as I'm suspicious that a binding or two might be missing.
1659958,2017-10-10 10:12:30 UTC,When I say missing I mean missing from the bundle.
1659958,2020-10-03 04:17:24 UTC,[Expired for OpenStack nova-cloud-controller charm because there has been no activity for 60 days.]
1659965,2017-03-23 02:21:20 UTC,Link on #3 is dead now.
1659965,2017-02-04 01:02:40 UTC,This issue was fixed in the openstack/neutron 10.0.0.0rc1 release candidate.
1659965,2017-02-03 00:17:51 UTC,"Reviewed:  https://review.openstack.org/427141
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e5320e764625bfc5b6723c52ec202ebdb926d32f
Submitter: Jenkins
Branch:    master"
1659965,2017-01-31 12:31:47 UTC,pstree got SIGSEGV: http://logs.openstack.org/01/410501/5/check/gate-neutron-dsvm-functional-ubuntu-xenial/8a82bb0/logs/dsvm-functional-logs/neutron.tests.functional.agent.linux.test_utils.TestGetRootHelperChildPid.test_get_root_helper_child_pid_returns_first_child.txt.gz#_2017-01-27_18_49_13_642
1659965,2017-01-30 18:50:26 UTC,"Never mind, the format seems fine[1] on different versions, therefore the problem could be caused by the chosen parent_pid"
1659965,2017-01-30 18:29:08 UTC,Maybe the way that is collected the child processes is not the best one[1].  I'm using pstree (PSmisc) 22.20 and it seems to use a single hyphen for creating the tree.
1659965,2017-01-31 12:34:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/427141"
1659969,2017-01-27 22:24:20 UTC,unity-lens-applications has the same bug by the way.
1659969,2017-11-05 17:02:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659970,2017-08-02 21:14:31 UTC,"Any chance we can get this accepted as a bug. This path /usr/locale/ is very annoying as it creates a new directory in /usr/, that only these packages are using, and interrupts tab-completion for those of us who navigate our filesystem regularly."
1659970,2017-11-05 17:00:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659972,2017-04-02 18:37:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659977,2017-01-30 14:22:30 UTC,"Assuming the creatives would use the gradient mesh to create starting from an more or less irregular closed path or by using the current technique and creating a squared or circular shape, the option of generating a mesh by using its path nodes parameters is a necessary one.
I'd add an option in gradient mesh tool for this, at least.
I would like to select the mesh corners for a squared-shaped mesh of the center for the circular-shaped mesh. I would like to be able to snap to path nodes when selecting the mesh corners for the squared-shaped mesh, in order to choose right from these nodes."
1659984,2017-01-31 12:35:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659984,2017-02-15 04:05:41 UTC,"Came home after being gone for 2 weeks, fired up 'puter, got this error message...  Have not done anything else yet."
1659988,2017-02-06 16:51:46 UTC,"@anoda Today, the maintainers announced a bugfix release which at least is supposed to fix the ""black/white tab issue"": https://bugs.launchpad.net/bugs/1659922"
1659988,2017-02-07 11:13:15 UTC,"@anoda Yes, only the black/white tab issue got fixed with the update which officially got released."
1659988,2017-02-07 10:38:37 UTC,Hi Thomas. This update was available yesterday (at least for 12.04 LTS Release) and there was only one rule added:
1659988,2017-02-06 16:05:49 UTC,"Hi Thomas. Yes, you're right: ""the apparmor profile shipped with ubuntu 12.04 is different from that version"". I'm using 12.04 LTS Release and after Firefox has been updated to the 49/50/51 versions, I've had to add some rules to the existing Firefox profile (please see: <https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659922> and my last comment # 51.) Everything was related to the e10s and a new Firefox versions."
1659988,2017-02-07 11:14:41 UTC,And here's the full version with patch VERSION 8 applied. (see https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988/comments/21 how to use it).
1659988,2017-02-03 07:43:16 UTC,"@Thomas Mayer (thomas303)
Thanks. I don't want to file a new ticket because I think the problem is linked to this one. But I try you patch No. 7, and after that I will see. Thank you once more."
1659988,2017-02-01 09:34:21 UTC,full profile in VERSION 7
1659988,2017-02-01 09:33:04 UTC,Patch VERSION 7
1659988,2017-01-31 20:42:10 UTC,@blantonradford Thanks for reporting back.
1659988,2017-02-03 18:42:25 UTC,@Thomas Mayer (thomas303)
1659988,2017-02-07 15:38:52 UTC,"Hi Thomas. Thanks for a patch, but as I mentioned it earlier; I'm using 12.04 LTS (but preparing to do an update, because of EoL etc.) so I can't use this patch for now in view of, for example:"
1659988,2017-01-31 20:36:34 UTC,"@sziraki.tamas I experienced myself that reading from / writing to files does not always work, depending on the chosen path. Is that your problem?"
1659988,2017-02-08 11:34:29 UTC,"@Thomas
The official firefox package update issued yesterday fixes my problem (on Firefox 51.0.1, Ubuntu 16.10). Anyway, the usr.bin.firefox apparmor file supplied is quite different from the patched one you shared here with us (and which worked as well). Thank you Thomas again, the bug is fixed for me!"
1659988,2017-02-18 06:22:10 UTC,Found another entry in syslog (when starting FF):
1659988,2017-02-18 06:23:20 UTC,Here's the full version of VERSION 9
1659988,2017-05-10 14:13:18 UTC,Hi Thomas.
1659988,2017-05-10 16:11:52 UTC,"@anoda Yes, on every release of Firefox it is possible that it uses something which is new to the apparmor profile. However, Firefox somehow heals itself in most cases."
1659988,2017-05-10 16:12:57 UTC,"[Typo fixed]: I don't get why especially a major browser can't have its apparmor profile enabled by default. I get that there is a reason for that, however."
1659988,2017-05-10 16:17:17 UTC,"@anoda Btw: Apparmor log messages sometimes occur for special tasks. Like playing a youtube video, opening a file on disk, etc. Maybe that explains that you see some of these log entries very seldom."
1659988,2017-05-15 16:56:25 UTC,"Patch attached fixes a lot, could we have it incorporated yet?"
1659988,2017-05-24 20:56:27 UTC,"Hello Thomas. Yes, I think you're right; ""Apparmor log messages sometimes occur for special tasks."" By the way - today I have again an issue (this is happening very often) with the plugin-container (Chrome_ChildThr) segfault. Suddenly, Firefox started to slow down, system also, audio was looping and a mouse moved slowly. After a long while I managed to open terminal and kill Firefox process."
1659988,2017-05-24 22:26:13 UTC,@anoda I wrote back via #1656065.
1659988,2017-06-03 10:39:46 UTC,"Hello Thomas. Today, I noticed next entry - related with Firefox - in a log files. I'm wondering whether to add this rule, because it's related to the ScreenSaver, which seems to be pretty strange. However a log entry looks this way;"
1659988,2017-02-07 17:16:55 UTC,"@anoda Got it. Maybe someone else who also uses 12.04 does the porting. For instance, I don't feel responsible for that (I'm not the package maintainer...)."
1659988,2017-01-31 20:18:42 UTC,"@Thomas Mayer (thomas303)
Using your profile in #21, also, I take FF in enforce mode but partly always fall back to unconfined mode while the apparmor_status shows the complete FF in enforced mode. The download and upload only to and from a special folder does not work."
1659988,2017-02-03 19:09:23 UTC,@wfhammond
1659988,2017-01-31 08:10:00 UTC,"Sorry, probably I wasn't clear enough: as I said, the problem (white rendering of web pages) showed up after the update to Firefox 51.0.1
Excluding it from Apparmor, Firefox became usable. Then, applying your patch, I was able to reenable Apparmor for Firefox and still displaying web pages correctly."
1659988,2017-01-28 01:16:56 UTC,My test was wrong (had another instance open with profile disabled)
1659988,2017-01-28 01:44:32 UTC,I fixed all the issues now.
1659988,2017-01-28 04:25:02 UTC,"The attachment ""usr.bin.firefox.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1659988,2017-01-28 13:36:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1659988,2017-01-28 16:52:38 UTC,"Thanks, will take a look at that after the weekend"
1659988,2017-01-28 22:41:37 UTC,@chrisccoulson
1659988,2017-01-28 22:51:12 UTC,I think this issue is not exactly a duplicate of bug #1659922.
1659988,2017-01-28 23:16:09 UTC,The patch also fixes
1659988,2017-01-28 23:26:01 UTC,Related or duplicate:
1659988,2017-01-30 10:16:33 UTC,Patch VERSION 4.
1659988,2017-01-28 01:09:06 UTC,"In addition, I applied the suggestion from https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1495248."
1659988,2017-01-30 10:48:38 UTC,Patch VERSION 5.
1659988,2017-01-30 13:49:41 UTC,"Just my 2 cents: we had the same problem here after the Firefox 51.0.1 update (just one machine is affected anyway, the others updated with no problem). The error message is NOT related to python, but I get graphics errors like the ones seen in  bug #1643200:
[GFX1]: Failed 2 buffer db=0 dw=0 for 0, 0, 1920, 876
[GFX1]: Failed 2 buffer db=0 dw=0 for 0, 0, 1920, 876
[GFX1]: Failed 2 buffer db=0 dw=0 for 0, 0, 1920, 876
Anyway, excluding Firefox from Apparmor (as with the OP's first suggestion) works around the problem. My suspect is bad interaction with the driver for the videocard of that specific machine on which we have the problem."
1659988,2017-01-30 14:14:50 UTC,@roberto-colnaghi I had similar issues as well. These have all gone in my case after applying my patch.
1659988,2017-01-30 14:18:00 UTC,"@roberto-colnaghi Ah, my error. Thought this was a new issue."
1659988,2017-01-30 14:19:08 UTC,"@roberto-colnaghi Please try out VERSION 6 of the patch. I think it fixes the [GFX1] issues, too."
1659988,2017-01-31 20:16:54 UTC,"Thomas,"
1659988,2017-01-30 14:27:37 UTC,"@thomas303 I can't apply the patch, it's a production machine. Besides, I don't understand which file has to be patched (I figured it was /usr/bin/firefox, but it doesn't contain any of the words found in the patch). Thanks anyway, I just wanted to highlight the fact that Python is probably not the cause, but ratherconflicts with problem drivers."
1659988,2017-01-30 16:07:10 UTC,@roberto-colnaghi Not exactly. The patch is against the apparmor profile of FF only.
1659988,2017-01-30 16:13:51 UTC,"@roberto-colnaghi Indeed, python 3.5 dependency is not the cause for white/black tabs. But the patch fixes that, too. It fixes every apparmor blocking I'm aware of in terms of firefox."
1659988,2017-01-30 16:30:10 UTC,"@thomas303 Thank you very much! The system was not broken, because I disabled apparmor for Firefox as you said in the opening post (altough you intended it just for testing). Anyway, your instructions were very complete, and my doubt was mainly compatibility with Ubuntu update. But as you said, ""Now that the original profile file remains unchanged, apt-get won't complain when the official package gets updated."", so it's fine for me. And it works like a charm, by the way!"
1659988,2017-01-30 17:24:15 UTC,@roberto-colnaghi Thanks for reporting back.
1659988,2017-01-30 12:43:45 UTC,Patch VERSION 6.
1659988,2017-01-28 00:54:04 UTC,"The following patch mitigates the error message, but it's only a partial fix for the issue (which is white tabs). Note that I had python 3.5 installed whereas the apparmor profile only supported 3.0-3.4."
1659989,2020-01-15 04:17:18 UTC,[Expired for eog (Ubuntu) because there has been no activity for 60 days.]
1659989,2019-11-15 05:44:05 UTC,"Thank you for your bug report. The image shows fine on 19.10, could you try in a newer Ubuntu version to see if it's fixed there for you as well?"
1659997,2017-01-28 16:34:11 UTC,"Hi Barrie,
there was a bug that has been corrected with release x.3766. Pls. check that starting from such release you don't get the error any more."
1659997,2018-06-20 16:56:53 UTC,openrail latest version not updating
1659997,2018-06-20 16:57:39 UTC,Openrail player not playing any game
1659999,2017-01-28 02:28:37 UTC,https://mir-jenkins.ubuntu.com/job/device-runtests-mir/2875/device_type=krillin/consoleFull
1659999,2017-01-30 02:05:47 UTC,And here:
1659999,2017-01-30 02:06:16 UTC,And here:
1659999,2017-11-03 16:42:33 UTC,Syncing task from Mir.
1660004,2017-02-07 01:22:26 UTC,++Xenial:
1660004,2017-03-26 20:47:45 UTC,"> It's recommended to use the snap going forward. As we will be removing charm-tools from the archive.
>
> `snap install charm`
"
1660004,2017-01-28 14:19:40 UTC,It's recommended to use the snap going forward. As we will be removing charm-tools from the archive.
1660004,2017-01-28 10:17:49 UTC,"Oh, it's the ""Backward-compatibility"" bit. ""path is deprecated. Use Path instead."""
1660004,2017-01-28 10:07:08 UTC,"Hmm, I saw this as well and even tried this:"
1660004,2017-01-28 04:07:41 UTC,"To be clear, running Ubuntu 17.04 Zesty Zapus on amd64, package version is from the archive, 2.1.2-0ubuntu4."
1660004,2017-01-28 10:30:25 UTC,https://github.com/juju/charm-tools/pull/302
1660006,2017-03-14 01:46:17 UTC,Why can't you just install Evolution after you install Ubuntu GNOME?
1660007,2017-06-21 12:14:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660010,2017-01-28 10:33:46 UTC,Icenowy Zheng <email address hidden> writes:
1660010,2020-03-24 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1660016,2017-01-31 18:44:29 UTC,From the mailing list
1660016,2017-01-31 11:19:37 UTC,But what about that apps that *do* need to ship Qt libraries that aren't within the ubuntu-app-platform? How will these work?
1660016,2017-01-31 18:53:18 UTC,Also
1660016,2017-01-31 10:23:57 UTC,"We need to update apps that are supposed to be using ubuntu-app-platform to not ship their own Qt libraries. Ideally of course somehow it would be autodetected to not ship any of the libraries that exist in ubuntu-app-platform, but that would need feature development in tools."
1660016,2017-02-07 11:13:49 UTC,I can also confirm ubuntu-terminal-app is now fixed with commit http://bazaar.launchpad.net/~ubuntu-terminal-dev/ubuntu-terminal-app/trunk/revision/350 - starts with both stable and edge channel ubuntu-app-platform.
1660016,2017-02-09 08:21:48 UTC,Terminal now fixed too.
1660016,2017-02-09 08:21:59 UTC,(rev 42)
1660016,2017-02-04 09:15:30 UTC,"For reference, snaps using no-system-libraries successfully now:"
1660016,2017-01-31 07:42:04 UTC,"> What snap is ""the"" Dekko snap here?
"
1660016,2017-01-31 13:03:27 UTC,"@Andrew Those apps should not use ubuntu-app-platform since they ship their own. There's no use for ubuntu-app-platform if the app ships its own libraries. But if ubuntu-app-platform is in use, one shouldn't mix a module from different Qt version and a module from ubuntu-app-platform's version."
1660016,2017-01-30 17:30:17 UTC,"On Mon, 2017-01-30 at 15:26 +0000, Timo Jyrinki wrote:

> So I think there is a missing bit somewhere that should be recompiled
> against Qt 5.6.2 still (or simply allow new binaries from overlay PPA
> to
> be staged), after which the #26 platform snap should actually be
> declared stable.
>
> As long as there are multiple sources for QPA modules instead of eg
> ubuntu-app-platform providing them all, there is room for problems if
> not everything is upgraded at the same time.
>


I think that it's not the QPA modules as much as the other libraries
that are pulled into the snap along with building it.
It seems like any update to Qt will require a name change of the snap
so that they can be installed in parallel to allow apps to use the one
they need."
1660016,2017-01-28 16:58:05 UTC,Happened with Dekko as well. Had to revert the ubuntu-app-platform version.
1660016,2017-01-30 13:27:51 UTC,"Added ubuntu-app-platform to the bug, for me this affects many snaps and now requires a rebuild of them:
- mediaplayer-app
- ubuntu-calculator-app
- ubuntu-docviewer-app
- ubuntu-filemanager-app
- ubuntu-terminal-app
- volleyball2d"
1660016,2017-01-30 14:47:12 UTC,Stable channel is now back to #22 (last version with Qt 5.6.1).
1660016,2017-01-31 07:36:49 UTC,"> Could this also be because of Qt libraries being in the application snap?
> and these are taking priority over the Qt libs in the ubuntu-app-platform?
> See the content's of the Dekko snap here http://paste.ubuntu.com/23894123/. lines 364-374
"
1660016,2017-01-30 15:42:08 UTC,Could this also be because of Qt libraries being in the application snap? and these are taking priority over the Qt libs in the ubuntu-app-platform? See the content's of the Dekko snap here http://paste.ubuntu.com/23894123/. lines 364-374
1660016,2017-01-30 15:26:11 UTC,So just to give the summary:
1660016,2017-01-30 15:57:32 UTC,I see vollyball2d is also shiiping a fair amount of 5.6.1 qt libraries in it's snap as well.
1660020,2017-11-03 16:29:59 UTC,Syncing task from Mir.
1660026,2017-01-28 13:13:02 UTC,"Also, I've tried the following from various forum suggestions:"
1660026,2017-01-29 15:18:03 UTC,"After several trials, I found the following pages:"
1660039,2017-11-03 16:42:35 UTC,Syncing task from Mir.
1660045,2018-10-13 06:49:48 UTC,"Hi Alexander,"
1660051,2017-01-28 17:09:41 UTC,"Update: if I switch AppArmor to complain mode, the refresh problems disappear. Here is a syslog excerpt with the AppArmor audit lines (notice the third one about /dev/nvidia-modeset):"
1660051,2017-01-28 17:22:19 UTC,It turns out /dev/nvidia-modeset is a red herring.  If I add the following line to /etc/apparmor.d/local/usr.bin.firefox:
1660051,2017-03-23 09:23:53 UTC,Ping.  Is anyone maintaining the AppArmor profile for Firefox?
1660053,2017-04-06 14:58:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660053,2017-04-06 22:49:45 UTC,Please open a new report about the bug you mentioned in the description
1660053,2017-04-06 22:50:32 UTC,"It was ""a marker instead of cursor comes on my screen now and then""."
1660063,2017-02-24 10:00:21 UTC,Set 'verification-done' as the comment made a few days back in #9 is confirmed for ZZ 64 bits at least.
1660063,2017-03-08 17:56:08 UTC,"The verification of the Stable Release Update for chrome-gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1660063,2017-03-08 13:24:51 UTC,Firefox 52 was pushed yesterday to Ubuntu.
1660063,2017-03-07 19:48:27 UTC,"As for phased-updates, the yakkety rate was already apparently low enough for the first SRU to make it through. But any crash for the trusty and xenial SRUs will stop phased-updates since the baseline there is 0."
1660063,2017-03-07 19:32:48 UTC,"Brian, yes it looks like there is still a crash somewhere in chrome-gnome-shell."
1660063,2017-03-06 20:02:49 UTC,"Brian,"
1660063,2017-03-06 19:35:49 UTC,"Looking at the Errors bucket for the crashes which halted the phased update earlier, I'm still seeing one crash (https://errors.ubuntu.com/problem/59694af66f4208c0851633bc8e29fcdc7f403cda) with crashes from 8-2ubuntu4.  If I understand things correctly it shouldn't be happening with that version in Zesty, right?"
1660063,2017-03-02 19:20:30 UTC,I don't see any error reports on errors.ubuntu.com from chrome-gnome-shell 8.2ubuntu4~ for xenial and above. So I confirm the verification-done.
1660063,2017-03-08 17:56:01 UTC,This bug was fixed in the package chrome-gnome-shell - 8-2ubuntu4~ubuntu16.10.1
1660063,2017-02-24 07:05:07 UTC,"Hello dino99, or anyone else affected,"
1660063,2017-02-14 13:02:11 UTC,"Latest 8.1-0ubuntu5 works well , thanks. Please load it to ZZ archive."
1660063,2017-02-10 03:10:50 UTC,"Good news, thanks ne0sight,"
1660063,2017-02-04 17:27:04 UTC,This is fixed in git master branch [1] and in Debian package version 8-3 [2].
1660063,2017-01-31 13:24:26 UTC,"The comment #5 above is still true when c-g-s is purged then reinstalled with the same session: does not get crash with that opened session.
But the crash happens again with a new session opened after a cold boot."
1660063,2017-01-30 16:14:00 UTC,"Looks like the problem was with the 7.x -> 8.x versions upgrade transition: I've purged the installed package, then reinstalled it, and the crash does not happen anymore.
So i let you decide if that report needs investigation or if it can be closed."
1660063,2017-01-28 18:39:28 UTC,apport information
1660063,2017-01-28 18:39:27 UTC,apport information
1660063,2017-01-28 18:39:01 UTC,apport information
1660063,2017-02-24 04:40:08 UTC,This bug was fixed in the package chrome-gnome-shell - 8-2ubuntu4
1660075,2017-03-29 06:15:28 UTC,Since this is not occurring for me and might be driver dependant I would need a stacktrace of the crash. Are you able to make one?
1660075,2017-03-29 16:07:18 UTC,"Hey Robert,"
1660075,2017-06-05 17:20:37 UTC,I was able to fix this issue by changing the permissions of ~/.cache to [user]:[group] rather than root:root.
1660081,2017-05-23 01:14:42 UTC,I think a good temporary solution would be to link to this bug tracker from repo's README.
1660081,2017-01-29 23:28:50 UTC,"Keeping the launchpad bug numbers in each issue's description or something
would be sufficient, as long as it's searchable. Enabling GitHub issues
immediately would mean having two bug trackers simultaneously (even if it's
one for new bugs and another for old ones). I don't think that's at all
desirable."
1660081,2017-01-29 21:17:42 UTC,"Actually, it's probably worthwhile without preserving the numbering. It might even be worthwhile to enable git issues immediately, prior to migrating existing bugs."
1660081,2017-01-28 22:35:38 UTC,"Maybe. Is it worth the trouble to migrate this bug database to GitHub,
though?"
1660081,2017-01-29 01:21:05 UTC,"Maybe, if they have a straightforward way to import the bugs and preserve the numbering."
1660100,2017-01-29 04:45:38 UTC,"When software-properties-gtk is run from the terminal, the following error is displayed:"
1660100,2017-02-12 15:33:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660100,2017-02-12 15:50:14 UTC,"I'm seeing the exact same problem, on an up-to-date Ubuntu 16.10 amd64 installation. The only oddity to my configuration is that I'm running the 4.9.6-040906-generic mainline kernel, because the stock Ubuntu kernel has stability issues with the ASUS Zenbook UX501VW. Based upon the original submitter's reported kernel, however, I doubt that's significant to this bug."
1660100,2017-02-12 16:06:21 UTC,"Just for fun I tried upgrading software-properties-gtk to version 0.96.24.8 (along with both dependencies) from ""http://us.archive.ubuntu.com/ubuntu/pool/main/s/software-properties/"". Unfortunately that didn't make any apparent difference."
1660100,2017-02-12 16:24:20 UTC,"I've attached a strace of software-properties-gtk, taken with the ""strace -fr -o software-properties-gtk.strace software-properties-gtk"" command. The only thing which stands out to me is that there are a *lot* of EAGAIN entries for file descriptor 3, which appears to be the local ""/tmp/.X11-unix/X0"" socket. The file exists, and has what I'd expect to be usable ownership and permissions."
1660108,2017-01-29 09:03:43 UTC,A little more testing to hopefully confirm.......
1660108,2017-01-30 10:53:24 UTC,Also looks very much like: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72813#c10
1660108,2017-02-08 12:20:20 UTC,Seems that passing -fno-keep-inline-functions to GCC in the acc tests for much of kubuntu's packages.
1660114,2017-01-29 09:46:21 UTC,"StacktraceTop:
 pipe_surface_reference (surf=0x0, ptr=0x1d8) at ../../../../../src/gallium/auxiliary/util/u_inlines.h:109
 dri_destroy_buffer (dPriv=0x55f8a3bb12c0) at ../../../../../src/gallium/state_trackers/dri/dri_drawable.c:171
 dri_put_drawable (pdp=pdp@entry=0x55f8a3bb12c0) at ../../../../../../src/mesa/drivers/dri/common/dri_util.c:615
 dri_put_drawable (pdp=0x55f8a3bb12c0) at ../../../../../../src/mesa/drivers/dri/common/dri_util.c:598
 driUnbindContext (pcp=0x55f8a225ca60) at ../../../../../../src/mesa/drivers/dri/common/dri_util.c:583"
1660119,2020-07-03 05:01:51 UTC,DistroRelease: Kali 2016.2
1660120,2017-01-29 13:53:45 UTC,"A mechanism for checking for erroneously created single pad nets is a very useful feature. It could be available without making the user do all the work to launch ""full"" ERC."
1660120,2017-01-29 14:25:36 UTC,"> Alternatively, just an easily accessible list of inserted labels (not the
> automatic ones) with number of pads, with the option to sort by this
> number, could do the work.
"
1660120,2017-01-29 15:29:45 UTC,"That's what I do, but, for example, it is still easy to fall into this pit when you decide to split a net into a number of nets with new names. Then you have to remember to check the existence of the old label, whether you really assigned the new name etc. For this reason a list of nets seems to be a better option, as it allows to check if the number of new labels is correct. If this would be to be implemented, I suggest to make it accessible also from the netlist generation dialog (to remind the user to use it)."
1660120,2017-01-29 13:13:46 UTC,Can you make a case for why this should be present at netlist generation as well as ERC? I'm not convinced. To me it seems like this *is* an ERC step: it's a validation that things are connected at they should be. That is the purpose of ERC.
1660120,2017-01-29 12:06:07 UTC,"It would be nice if ERC could check for this. It can already report Input pins that aren't driven, but an additional mode to report all unconnected pins would be a good addition. We have an explicit ""no connect"" marker, so to me it's sensible to consider a non-connected pin without a no-connect marker at least a warning condition."
1660120,2017-01-29 12:41:29 UTC,"This is already the case in ERC.
All not connected pins without ""no connect"" marker should be reported."
1660120,2017-01-29 12:40:53 UTC,"Yes, but, please, don't restrict such warning to ERC only. It really should be related primarily to netlist generation."
1660120,2017-01-29 12:57:22 UTC,"""The use of ""no connect"" markers is rather rare"" ?"
1660121,2017-02-17 20:05:53 UTC,"I've found additional info in a Cinnamon bug report (https://github.com/linuxmint/Cinnamon/issues/2379). The issue is in fact with mate-settings-daemon (I've updated the current report to ubuntu-mate, not sure it's the right project)."
1660121,2017-11-03 18:49:35 UTC,"On my system, With Ubuntu 16.04  17.10  and Mint 18.2 (all running MATE) Change background doesn't work on any of them.  (When I click on a background, the highlight moves, but no change to the actual background.  (btw. Themes don't change either)"
1660121,2017-11-03 20:09:37 UTC,"I don't think this is related to the bug report, unless you're talking about the LightDM (login screen) background, but from your description, I understand that you can't change your desktop background at all. Is that correct?"
1660121,2020-04-19 15:11:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660129,2017-01-29 13:03:43 UTC,"Thanks for the report. I fixed this. It will be available in the next release, which will probably be RedNotebook 1.15."
1660148,2017-01-29 16:15:53 UTC,Could be useful. Ideally the silkscreen should be walked back from the mask opening an amount equal to the registration tolerance of the silkscreen layer.
1660164,2017-07-08 15:25:15 UTC,"Same exception as https://bugs.launchpad.net/pinta/+bug/1675742, can't reproduce it myself. Do you have some image that fails on copy-paste that I can try to use to get this?"
1660164,2017-08-10 21:10:55 UTC,"Hi Elvis, it happened days ago, I send you images from screen with errors
given and the last one containing the image that screw the paste operation."
1660176,2017-05-22 18:02:38 UTC,"Hey, I think I get the problem when I actually change the soundcard.
So when I selected pulse, my options change but when reconfiguring I select pulse as well it won't happen but when I select a different soundcard (USB port of school mixer) and reconfigure it at home (to pulse) I will loose some of my settings. I can't say what settings I loose in which case but it happens.
I hope I'll get a fix for it because it is really annoying."
1660176,2020-05-10 14:18:27 UTC,Probably fixed in 2.2.3
1660176,2020-05-10 09:44:12 UTC,Is this still an issue with Mixxx 2.2?
1660176,2018-10-17 20:34:58 UTC,"I have just filed a bug about the pulse issue:
https://bugs.launchpad.net/mixxx/+bug/1798469"
1660176,2018-10-17 15:48:03 UTC,"Hmm, I can only say that I didn't notice the behaviour recently. I'm running 2.1.5-alpha-pre on Debian Stretch, so many things might have changed."
1660176,2018-10-17 04:17:53 UTC,This does seem pretty annoying -- does it still happen with Mixxx 2.1.4 or 2.2.0 beta?
1660176,2020-08-07 04:17:15 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1660176,2017-05-21 12:34:26 UTC,"The bug is still present. At first in ~/.mixxx/mixxx.cfg
[EffectRack]
show 0"
1660176,2020-06-07 11:24:05 UTC,"Well, as I already stated: I didn't notice this behaviour as of Oct 2018 with Mixxx 2.1.5. I didn't notice it in my current Mixxx 2.2.0 either. I think this can be closed, I'll report again if the problem occurs again."
1660176,2017-04-18 20:30:12 UTC,https://bugs.launchpad.net/mixxx/+bug/1683924
1660176,2017-04-18 20:26:41 UTC,"I can confirm this with the default settings. Strange that I have never noticed this.
There must be a bug in input buffer syncing code."
1660176,2017-04-18 19:44:10 UTC,"Ah sure, and the played video. It is a video of my friend, I don't like it very much but I will have no trouble with licensing ;-)"
1660176,2017-04-18 19:42:38 UTC,"Pulse is the best-peforming solution. Your loopback mixxxing sounds terrible. (listen to the attachment)
But I can't reproduce the reset of other settings as well, may be this is another problem. But it still happens from time to time."
1660176,2017-04-18 09:09:25 UTC,I cannot reproduce it.
1660176,2017-01-29 18:57:17 UTC,More examples:
1660176,2017-04-20 20:32:11 UTC,"Yeah, once my input / output devices change, I have to reconfigure them."
1660195,2019-09-01 19:45:18 UTC,"Please see, https://bugs.launchpad.net/juju/+bug/1842254"
1660195,2019-09-01 19:36:41 UTC,I can confirm I am having this problem as well. I'll post a new bug report with all the detailed info.
1660195,2017-03-29 00:43:44 UTC,"@Daniel Chow (simech),
Please file a report for your failure against https://bugs.launchpad.net/juju as a new bug, follow ""Report a Bug"" link on the right hand side."
1660195,2017-03-28 19:54:31 UTC,Ok. Thank you. This is JuJu and LXD related. Can you advise me where to report this to try to get it resolved?
1660195,2017-03-28 07:46:43 UTC,"Daniel,"
1660195,2017-03-28 00:36:56 UTC,"Address already in use. This was the same thing I got when I used the defaults of 10.50.etc.
It's the same DNSMASQ issue. All latest stable binaries.
root@mcnode2:~# lxd --version
2.12
root@mcnode2:~# juju --version
2.1.2-xenial-amd64"
1660195,2017-03-28 00:29:35 UTC,"What's the manual process? I'm still blocked by this as well!
From page: https://jujucharms.com/docs/stable/getting-started"
1660195,2017-02-08 02:52:47 UTC,"Since there is a manual fix that allows you to bootstrap, I'll put this as Medium for now."
1660195,2017-02-07 17:01:41 UTC,"John, can confirm this -- as soon as I kill the initial ssh[mux] process juju retries and the bootstrap succeeds."
1660195,2017-02-05 20:35:42 UTC,"I've narrowed the issue down a bit. On the resp. machine I'm using SSH Multiplexing (cf. [0]), and the behaviour above manifests only with SSH multiplexing enabled. Not sure why, mind you; as noted above manual ssh invocation towards the juju controller works fine."
1660195,2017-02-03 04:12:30 UTC,"@Peter,"
1660195,2017-02-03 04:04:21 UTC,"Original report was against 2.0.x. As we are not planning to release any further 2.0.x, marking this bug as Won't Fix for 2.0.x."
1660195,2017-02-02 21:06:34 UTC,"Sure, pretty much same behaviour. Bootstrap debug log attached"
1660195,2017-01-31 22:12:41 UTC,"@Peter,"
1660195,2017-01-31 21:07:02 UTC,"Sure, I've attached a log w/ --debug (sans ssh pubkey)"
1660195,2017-01-30 18:57:14 UTC,Can you try to bootstrap the controller with --debug?
1660195,2017-02-06 07:27:11 UTC,"This isn't a regression in 2.1, as from what I can tell 2.0 exhibits the same behavior.
My best guess is that we attempt to connect to the LXD machine before the SSH connection is fully available (we see the IP address, but OpenSSH is not running yet).
However, the SSH binary that we ran doesn't go away, because its now the ControlMaster for that host. If it was spawned from the terminal, it would have gone into the background and returned the terminal to your shell. However, Juju just sees the SSH command still hanging around, and its waiting to get STDIN available to run commands on the remote host."
1660202,2017-03-01 08:56:48 UTC,I regularly have exactly the same issue. Not exactly sure what it depends on. Occasionally updates decide to show bu 80-90% of the time not.
1660206,2017-01-29 23:04:10 UTC,Added another possible patch (source: https://forum.kde.org/viewtopic.php?f=309&t=136596).
1660206,2017-01-30 00:28:34 UTC,"The attachment ""casper-http-simple.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1660219,2017-01-30 05:16:26 UTC,"Mmmm, I see I can reduce the search window (e.g. 2062 to 2065) and it does better, but interestingly I'm unable to extract 5 events in that 3-yr period - at most I can extract 2 in one time window. Being interested in long(er)-time prediction or historical searches, the utility unfortunately seems limited :( However, I can see that what I would like to do is  computationally intensive at the least - I can put in on my wishlist anyway."
1660219,2017-01-30 03:53:10 UTC,Please try use not very wide range of dates ;)
1660219,2017-02-25 08:44:41 UTC,"Current implementation of phenomena calculator uses iteration to finding a phenomena (with progressive changing of time step). This is better way what I find in the current environment, but I hope he can be improved in the future."
1660219,2017-01-30 00:22:52 UTC,"This ""bug"" is regarding AstroCalc Phenomena in v15.0 and v15.1"
1660219,2018-09-19 14:12:11 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/372
1660222,2020-03-17 08:00:41 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1660222,2020-05-17 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1660223,2017-02-02 18:23:56 UTC,Thank you for taking the time to report this bug.  It looks like the upstream magnum source doesn't have a MANIFEST file so we don't get these files picked up in the package.  I think we'll need to install these files manually in d/rules.
1660223,2021-01-08 15:53:34 UTC,It looks like this was resolved in the packaging around the time of this bug by including a patch in the package to build the MANIFEST.in:
1660228,2017-01-30 05:34:43 UTC,Confirming for now.
1660228,2017-01-30 06:47:34 UTC,"I should note in the original document, the physical dimension was never a concern.  All I cared about was the pixel size."
1660228,2017-01-30 04:48:22 UTC,"I used File/Open rather than File/Import.  The dialog you mentioned did pop up.  I choose ""Scale Elements."""
1660228,2017-01-30 04:40:26 UTC,"Will Pittenger wrote:

> The demo SVG is a simplified version of the original.
"
1660228,2017-01-30 04:18:54 UTC,"And, yes, I should have said ""imported from an older version of Inkscape"" rather than ""imported from 0.91."""
1660228,2017-01-30 05:32:22 UTC,"With Inkscape 0.92.0 r15299 (on OS X 10.7.5):
1) The core of the report - unexpected stroke-width attribute added to paths with unset stroke - reproduced when opening the legacy file with the option to 'Scale elements' (preserving the physical size). It is not added when using 'Set 'viewBox' (a different method to preserve the physical size), or with 'Ignore'.
2) The stroke width indicator in the status bar and in Fill&Stroke agree about the width of the stroke - the displayed units might differ depending on how the document was opened and what display units it uses (compared to the default template). IIRC there's a more specific report about this. Unrelated to 1)
3) Stroke width unexpected (""But they were 1.06666672 or something similar."") - that's a 1px stroke width in the original 90dpi-based document which was scaled according to the option for DPI change chosen by the user ('Scale elements'). This is in itself not a bug."
1660228,2017-01-30 04:02:26 UTC,Note (for triage): cont.
1660228,2017-01-30 03:23:59 UTC,Note (for triage):
1660228,2017-01-30 02:54:37 UTC,Attaching the original SVG file from the external link to the bug report - links tend to disappear over time or might get replaced with newer versions (content changed).
1660228,2017-01-30 02:10:05 UTC,"Oh, I noticed the inkscape:export-xdpi and inkscape:export-ydpi attributes were still set to 90 rather than 96.  Changing that had no effect, but that did seem to be a bug too."
1660228,2017-01-30 04:17:48 UTC,The demo SVG is a simplified version of the original.  Just the two paths and everything else stripped out.
1660232,2017-02-01 04:48:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660242,2017-01-30 08:54:44 UTC,And yet another version that updates xdg-mime too: http://paste.ubuntu.com/23892565/
1660242,2017-02-03 11:41:12 UTC,"A pull request for a ""thumbnailer"" snappy interface:"
1660242,2017-01-30 04:29:15 UTC,thumbnailer-admin can't talk to thumbnailer-service.  Ideally communication like this between apps from a single snap should be unrestricted:
1660242,2017-01-30 05:10:48 UTC,"Thumbnailer sounds like something that should already be part of other snaps, not something that is potentially stand-alone...?"
1660242,2017-01-30 05:13:44 UTC,Script to temporarily work around the gdk-pixbuf bug: http://paste.ubuntu.com/23891990/
1660242,2017-01-30 05:16:24 UTC,Fixed version of script: http://paste.ubuntu.com/23892004/
1660242,2017-01-30 05:28:53 UTC,"> Thumbnailer sounds like something that should already be part of other snaps, not something that is potentially stand-alone...?
"
1660242,2017-01-30 09:36:22 UTC,"Looks like snapcraft-desktop-helpers has been updated to mostly fix these problems.  Still some rough edges, but the above script should become unnecessary soon."
1660246,2017-01-31 01:23:51 UTC,nvm i found a solution.. install windows10
1660266,2017-01-31 12:56:24 UTC,"(been poking in this area with screencast-to-buffer work lately... Changing this system isn't in that line of work, but worth evaluating)"
1660266,2017-02-01 01:40:11 UTC,"glReadPixels is not problematic if you do it after your swap (which on ES requires an FBO I think). Then the only requirement is that it completes within a few milliseconds to make way for the next frame. That's certainly less CPU intensive than rendering every frame twice, and more accurate too, since you will get the actual pixels that went to screen instead of an estimation of them."
1660266,2017-11-03 16:30:03 UTC,Syncing task from Mir.
1660269,2017-03-13 05:41:51 UTC,"Interestingly, screencasting via linear buffers also lets you select a specific window for casting. That is at screen address (FBO_stride * window_y + window_x), and has stride (window_stride)."
1660269,2017-01-31 12:52:41 UTC,I agree that GL is too entrenched in the screencast code at the current time. Part of the renderer work should be to be able to replace the screencast bits easily.
1660269,2017-02-01 01:36:19 UTC,"I think this is pretty simple in theory. Using desktop GL you could just read the back/front buffers. Using ES you can't do that, but you can render every frame to an FBO and then to the screen. And I believe GLES is happy to read pixels from an FBO (that's how our current casting works)."
1660269,2017-03-13 05:42:29 UTC,"Correction:
That is at screen address (FBO_stride * window_y + window_x), and has stride (FBO_stride), but still window_width and window_height."
1660269,2017-11-03 16:30:08 UTC,Syncing task from Mir.
1660273,2017-02-14 11:23:10 UTC,After installing from mini.iso:
1660273,2017-02-14 16:54:37 UTC,"After speaking with the snappy team on IRC, asking for a change to /etc/environment is a big ask, and the idea of modifying it for existing installs also seems haphazard. It seems like sourcing /etc/profile or manually setting PATH is the next best thing, and is a workaround for the time being."
1660273,2019-05-05 16:13:17 UTC,You can add it in `/etc/profile.d`.
1660273,2017-08-18 10:18:17 UTC,Per https://bugs.launchpad.net/juju/+bug/1660273/comments/11 I've contacted Foundations
1660273,2017-02-14 11:19:35 UTC,"Looking at a xenial server and a zesty desktop/server, I don't think /etc/environment contains /snap/bin anywhere."
1660273,2017-08-18 08:53:58 UTC,I'm marking the snapd task as invalid as we have no way to influence the global environment this way. There is a systemd feature that is not universally available yet that might allows us to do this but I also believe that the current approach of /etc/profile.d is as good as we can do it from the POV of our package.
1660273,2017-02-14 10:19:52 UTC,"/etc/profile is for login shells, which explains how jujud and thus the hook environment fails to pick it up."
1660273,2017-02-14 02:14:38 UTC,From IRC:
1660273,2017-02-14 09:30:14 UTC,"I've looked at a GCE instance and a LXD container; both of these had /snap/bin in the path.  This is configured by /etc/profile.d/apps-bin-path.sh, which is also in the downloadable images for xenial."
1660273,2017-02-14 06:32:08 UTC,"The snap layer has a workaround for reactive charms (it adjusts the path), leaving just traditional non-reactive actions affected."
1660273,2017-02-14 02:45:58 UTC,"Yes, we discovered this today the hard way. It was really weird having to set path."
1660273,2017-02-14 02:32:21 UTC,Yea it may be worthwhile talking to CPC team about getting that into the image builds
1660273,2017-09-26 10:24:02 UTC,Foundations has not responded. How do we target this bug?
1660273,2017-02-14 01:54:36 UTC,Juju does not alter the PATH of the host except to add the tools directory for unit hook executions.
1660273,2017-02-14 09:44:16 UTC,"Just to clarify, I used MAAS provider at that time. It might be MAAS image specific, but I don't have handy MAAS env to confirm atm."
1660273,2017-11-14 06:15:26 UTC,"Reopening this for snapd, as the problem still exists. snapd packages can do the hazardous /etc/environment modification, or can coordinate with foundations for next Ubuntu release and backports."
1660275,2017-04-18 10:10:17 UTC,Verified on MOS 10.0 (RC #2)
1660275,2017-03-13 15:31:35 UTC,Verified on 9.2 + mu1 updates.
1660275,2017-02-27 16:28:39 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1660275,2017-02-17 10:27:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435352"
1660275,2017-02-17 14:03:59 UTC,"Reviewed:  https://review.openstack.org/435352
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=7f81f3aea2412ee703c8d20894b731859b0e5243
Submitter: Jenkins
Branch:    master"
1660275,2017-02-21 08:22:43 UTC,"Reviewed:  https://review.openstack.org/435353
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=aed70b97674f418a1d6509ddee889c34e98ffd2c
Submitter: Jenkins
Branch:    stable/newton"
1660275,2017-02-17 11:03:11 UTC,"Reviewed:  https://review.openstack.org/429787
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=525461a88aa4521485c832e86644953741172980
Submitter: Jenkins
Branch:    stable/mitaka"
1660275,2017-02-17 10:28:00 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/435353"
1660275,2017-02-06 17:01:40 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/429787"
1660287,2017-01-30 10:50:21 UTC,This issue can be mitigated by adding the following lines to FF's apparmor profile:
1660287,2017-01-30 11:54:02 UTC,There's more:
1660287,2017-01-30 12:34:59 UTC,ca.desrt.dconf.Writer also needs receive:
1660287,2017-01-30 12:46:11 UTC,I've uploaded a patch named VERSION 6 at https://bugs.launchpad.net/bugs/1659988 which all changes I suggested in this ticket so far.
1660295,2017-01-30 11:47:17 UTC,Can you provide the command you use to build the linked library using Cheerp?
1660295,2017-01-30 11:24:47 UTC,The crash seems to happen while reading bytecode. Could you verify that all the intermediate bc files are being built using Cheerp with a consistent version?
1660295,2017-01-30 11:33:49 UTC,"Yes, i confirm it. Im using the latest binary installation package for OSX,
as downloaded from Cheerp's website."
1660298,2018-07-30 23:53:47 UTC,"Does this issue still arise with Firefox 60+? I've encountered various DBus VFS-related denials with Firefox under AppArmor, but not this particular one."
1660298,2017-01-30 12:58:45 UTC,"Testing so far happened with FF 51.0.1, ubuntu 16.04."
1660298,2017-01-30 12:57:46 UTC,"I can reproduce this issue with and without FF-extension ""ubuntu modifications"" enabled."
1660298,2017-01-30 11:23:14 UTC,"For changes I made to FF's apparmor profile to reproduce this issue, see https://bugs.launchpad.net/bugs/1660287"
1660298,2017-01-30 11:32:27 UTC,I CAN'T reproduce this issue EVERY time I click on the upload button. Just every 2-3 times I click it.
1660298,2017-01-30 11:29:57 UTC,"When I disable FF's apparmor profile, nothing is logged to syslog."
1660298,2017-01-30 11:27:37 UTC,Please also note that I'm in apparmor's reporting mode (which logs an entry every time apparmor blockes something and which I tested for also complaining).
1660298,2017-01-30 12:34:05 UTC,"I just DID reproduce this issue with FF's apparmor profile disabled. That said, this issue seems to not be related to apparmor profiles."
1660301,2017-01-30 13:32:46 UTC,"Reviewed: https://review.fuel-infra.org/30238
Submitter: Alexander Evseev <email address hidden>
Branch: master"
1660301,2017-01-30 11:48:03 UTC,"Fix proposed to branch: master
Change author: Mykyta Karpin <email address hidden>
Review: https://review.fuel-infra.org/30238"
1660302,2017-04-18 16:32:32 UTC,"given that --target-arch is plugin specific (like the documentation explicitly says) and we only have exactly one plugin supporting this (kernel), i'd say this is no surprise ..."
1660308,2017-03-03 11:16:45 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/441066"
1660308,2017-04-19 10:45:50 UTC,Verified on Fuel 10 build #1575
1660308,2017-03-09 11:11:24 UTC,"Reviewed:  https://review.openstack.org/431415
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=88bfbd924137cd2aa0ed7517029abcfddd48d0c1
Submitter: Jenkins
Branch:    stable/newton"
1660308,2017-03-03 12:09:11 UTC,"Reviewed:  https://review.openstack.org/441066
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=96f000fa5140874ae3da63a264988c6e58db000c
Submitter: Jenkins
Branch:    stable/newton"
1660308,2017-02-09 10:01:21 UTC,"Reviewed:  https://review.openstack.org/366844
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=cfd2588728e855a6b4aee7b1c7516a0aefa26b42
Submitter: Jenkins
Branch:    master"
1660308,2017-02-09 09:59:17 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/431415"
1660308,2017-01-30 12:48:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/426741"
1660308,2017-01-31 10:45:09 UTC,Fuel-library part addressed by https://review.openstack.org/#/c/366844/
1660308,2017-02-27 16:28:46 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1660308,2017-01-31 10:46:51 UTC,Fuel-QA part should be merged as two commits. In first we will introduce workaround for proper reviews testing. In second we'll remove opening of astute.yaml file and only cluster.yaml will stay.
1660308,2017-02-02 11:37:38 UTC,"Reviewed:  https://review.openstack.org/426741
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=62ec18011fbf2ba4428c4f68f45ab8630dd55baf
Submitter: Jenkins
Branch:    master"
1660314,2017-01-30 12:23:30 UTC,FF's apparmor profile shipped with 51.0.1 contains a line
1660314,2017-01-30 22:36:21 UTC,"Thomas, your logs are filled with what looks like errors from the ubuntu-sso-client package. Could you please file  a bug against that package too? ubuntu-bug ubuntu-sso-client  should do the job."
1660314,2017-01-31 03:24:40 UTC,@seth-arnold bug report for ubuntu-sso-client: https://bugs.launchpad.net/bugs/1660508
1660339,2017-02-07 04:11:31 UTC,"     https://github.com/percona/percona-server/pull/1361
     https://github.com/percona/percona-server/pull/1362"
1660339,2017-06-14 08:19:57 UTC,See bug 1697700 for X plugin testsuite bits
1660339,2018-01-25 09:17:37 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1779
1660345,2020-06-18 22:39:07 UTC,This checkbox was deliberately removed from the ubiquity installation process. The test cases should be updated to reflect that.
1660345,2020-04-21 01:18:21 UTC,Also experiencing this on Kubuntu desktop 20.04 Release Candidate ISO 20200420
1660345,2020-04-20 08:11:26 UTC,Ubuntu Desktop 20.04 daily iso 20200417
1660345,2020-03-09 15:16:13 UTC,Xubuntu 20.04 daily iso 20200309
1660345,2020-02-04 00:47:25 UTC,Ubuntu MATE 18.04.4 daily iso 20200203.1
1660345,2017-04-11 18:43:05 UTC,"This also affected me, tested on 3 different laptops - MacbookPro 1,1, Dell Latititude D630 and Dell Latitude E6420."
1660345,2017-01-30 17:58:17 UTC,"Ohhh and sorry, yes I meant to type `ubuntu-bug ubiquity` but failed :/"
1660345,2017-01-30 17:57:39 UTC,"However Ubuntu does recognise when I'm plugged in and when I'm not, the indicator changes accordingly, even in VirtualBox."
1660345,2017-01-30 17:32:46 UTC,"On 30 January 2017 at 17:21, Launchpad Bug Tracker
<email address hidden> wrote:

> You have been subscribed to a public bug:
>
> Testing Ubuntu 17.04 20170130 ISO
>
> Is plugged to a power source checkbox - not displayed on 'Preparing to
> install Ubuntu' screen ('Download updates when installing Ubuntu' and
> 'Installing third-party software' is there) when plugged in or when I
> unplug, or when I go back to the Install/Live Session screen and back
> into the 'Preparing to install Ubuntu' screen. Have we dropped this
> check? If so, tell me and I will close the bug and report an issue with
> the testcase.
>
> Computer info:
> VirtualBox Graphical User Interface Version 5.1.6_Ubuntu r110634
"
1660345,2017-01-30 16:22:04 UTC,Any idea what package the bug could be in? I know I'm not meant to file it as a general bug unless I can do otherwise but I have no choice unless if you have an idea
1660345,2017-01-30 14:50:08 UTC,This is not a duplicity error.  Please redirect to correct project.
1660345,2017-04-11 18:30:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660349,2017-01-30 14:41:14 UTC,"That indicates a corrupted db on the device, the usual fix for it is to
log out and log in again on the Kobo which will cause it to rebuild the
database."
1660349,2017-01-31 09:06:35 UTC,Thanks for the prompt reply.
1660349,2017-01-31 10:33:45 UTC,Changing the component for this bug.
1660350,2017-06-16 13:19:19 UTC,"Can't replicate the bug. Even selecting 300+ files, when I release shift and UP/DOWN, the selection discarded and only one file is selected."
1660350,2017-06-20 20:59:41 UTC,"A little more description of bug:
1. The bug occurs in icon view mode
2. It occurs from time to time(not always)"
1660351,2017-12-06 12:15:42 UTC,"Also if you use Nova as a proxy anyway, why not use the socat serial console?"
1660351,2017-12-04 19:25:54 UTC,"Thanks for submitting this. We discussed it in our ironic meeting today [1] and we'd like a spec that describes the problem in more detail, along with the proposed changes to address it."
1660351,2017-03-01 13:23:22 UTC,"As for the first point, please see the spec https://review.openstack.org/249876, the 2 and 3 points seem like feature requests to me too, so I added the rfe tag to this."
1660351,2017-12-04 19:28:31 UTC,Sorry that link in #2 should have been
1660352,2017-01-30 15:28:46 UTC,"I can't see any of our code that cares about this, and I've tested with https quite a few times.  Can you please tell us exactly what you did (including URLs) and exactly how it failed (including copy-and-paste of the exact error message)?"
1660352,2017-01-30 15:44:45 UTC,"Sure, I was working in bug 511643 and about to indicate that the bug is reported upstream. I had to replace the https-link with http to add the relation."
1660352,2017-04-01 04:17:35 UTC,[Expired for Launchpad itself because there has been no activity for 60 days.]
1660353,2017-01-30 16:19:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1660353,2017-01-30 16:42:56 UTC,This bug has been reported as bugzilla #772597 (https://bugzilla.gnome.org/show_bug.cgi?id=772597).
1660353,2017-01-31 17:57:02 UTC,thanks for the upstream bug report
1660353,2017-08-04 05:43:01 UTC,I still see this with Evince 3.24.0 on Zesty.
1660353,2019-05-27 12:50:48 UTC,"Upstream bug closed ""RESOLVED FIXED"" on 2017-06-05
No further reports for almost two years
Checked working ok with evince 3.32 in Ubuntu 19.10 (dev)
Closing as fixed"
1660358,2017-01-30 16:00:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/426816"
1660358,2017-02-01 10:18:04 UTC,"Reviewed:  https://review.openstack.org/426816
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=a8e22388edcc7d31f1f2a2cfab77b28c49b1288a
Submitter: Jenkins
Branch:    master"
1660366,2017-03-17 16:58:42 UTC,"Another reason to solve this and remove the workaround: by doing separate runs we lose the artifacts of the previous run, see Armando's comments at https://review.openstack.org/#/c/446743"
1660366,2017-02-03 15:05:15 UTC,"To expend on the PortChainFlowClassifierInConflict issue:
tests create a flow classifier with parameters logical source port, source ip prefix, destination ip prefix"
1660370,2019-09-19 12:02:07 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1660380,2017-01-30 16:43:18 UTC,Installing the Firemacs extension doens't help either. Ctrl-N is completely stolen by something in Firefox even after disabling the horrible window creation binding. No problems in other programs.
1660388,2017-01-30 17:04:36 UTC,"Uploading jpg a second time so it's obvious, and not missed in the maas of auto-uploaded logs."
1660389,2017-07-20 12:03:40 UTC,I also have this problem and many others do too because there's plenty of websites telling us how to get them working..
1660389,2017-01-31 21:27:18 UTC,"I did the apport-collect 1660389 but in the meantime I installed the driver manually to get it to work. Do I need to uninstall the driver for this device  for further investigations?
The apport-collect 1660389 was done when I had the driver installed."
1660389,2017-01-31 21:21:47 UTC,apport information
1660389,2017-01-31 21:21:45 UTC,apport information
1660389,2017-01-31 21:21:42 UTC,apport information
1660389,2017-01-31 21:21:38 UTC,apport information
1660389,2017-01-31 21:21:44 UTC,apport information
1660389,2017-01-31 21:21:35 UTC,apport information
1660389,2017-01-31 21:21:36 UTC,apport information
1660389,2017-01-30 17:12:04 UTC,lsusb -v
1660389,2017-01-30 20:28:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1660389,2017-01-31 21:21:41 UTC,apport information
1660389,2017-01-31 16:50:45 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1660389,2017-01-31 16:30:14 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1660389,2017-01-31 21:21:33 UTC,apport information
1660389,2017-01-31 21:21:31 UTC,apport information
1660394,2017-01-31 07:56:59 UTC,Could you please also provide your text_list/textarea_list settings structure which you try to build into a plugin? This will help to investigate the issue.
1660394,2017-01-31 12:39:55 UTC,"----
+/- Buttons dont work, regex wont work either on the ""Other"" Tab of settings for this field
----"
1660394,2017-01-31 13:03:06 UTC,"Alex, I see an error in your config:
for *_list settings their value should be a list:"
1660394,2017-01-31 13:44:14 UTC,"Julia, unfortunately this wont work, FPB will complain because it asks for a string"
1660394,2017-02-01 08:57:13 UTC,"Got it. So, I think we need to backport fix of https://bugs.launchpad.net/fuel/+bug/1616466 to 9.x branch to resolve your issues."
1660394,2017-01-31 07:53:56 UTC,"Alex, thank you for your bug reports.
Could you please specify Fuel version and describe Steps To Reproduce (I mean smth like 1. Click this button, 2. Check this field, etc) and Actual/Expected behavior."
1660409,2017-10-21 10:20:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660409,2017-01-30 18:15:20 UTC,"StacktraceTop:
 ?? ()
 gdk_event_apply_filters (xevent=xevent@entry=0x7fff2531e070, event=event@entry=0x565403fe0330, window=window@entry=0x565403eff000) at /build/gtk+2.0-KsZKkB/gtk+2.0-2.24.30/gdk/x11/gdkevents-x11.c:371
 gdk_event_translate (display=display@entry=0x565403ef6000, event=event@entry=0x565403fe0330, xevent=xevent@entry=0x7fff2531e070, return_exposes=return_exposes@entry=0) at /build/gtk+2.0-KsZKkB/gtk+2.0-2.24.30/gdk/x11/gdkevents-x11.c:1074
 _gdk_events_queue (display=display@entry=0x565403ef6000) at /build/gtk+2.0-KsZKkB/gtk+2.0-2.24.30/gdk/x11/gdkevents-x11.c:2358
 gdk_event_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at /build/gtk+2.0-KsZKkB/gtk+2.0-2.24.30/gdk/x11/gdkevents-x11.c:2419"
1660409,2017-01-30 20:11:12 UTC,"I think it has something to do with the flash plugin. It crashed again while I was browsing duolingo.com in Epiphany, and that website uses flash."
1660418,2018-08-29 06:58:23 UTC,"One important symptom found here:
 - Upload and importing custom images to MAAS server with same filename with different SHA256 will continue grow the `maasserver_largefile` table (and pg_largeobject) but only show one entry on `maasserver_bootresource`"
1660418,2018-09-20 09:34:29 UTC,"I'm currently running something like this every day on our MaaS:
time sudo -u postgres vacuumlo -v maasdb
time sudo maas-region db_vacuum_lobjects
time sudo -u postgres psql maasdb -c 'vacuum full verbose maasserver_largefile'
sudo du -sh /var/lib/postgresql/"
1660418,2018-09-21 12:04:13 UTC,A fix has landed in master for this. We want to test it for a few days in master before backporting it to 2.3 and 2.4.
1660422,2017-01-30 19:12:32 UTC,I think that I should be more clear.
1660432,2017-11-06 14:21:09 UTC,I think we'll need to do something like logging fixture here https://github.com/openstack/cinder/blob/master/cinder/tests/fixtures.py to make things work
1660434,2017-01-30 20:27:41 UTC,except the current one from the install.
1660438,2017-03-28 18:20:05 UTC,"I see some jitter when using the slider but it always corrects.
The hardware key shows no issue.
Samsung laptop, zesty"
1660438,2017-03-14 11:24:51 UTC,"I can't see anything wrong happening with brightness on my laptop. Even playing real hard with the slider, the most I get is some lag and the slider catching up to my moves a second after I release the slider."
1660438,2017-02-22 17:30:04 UTC,"also, just noticed, if i rapidly hit hw key, i get the odd flicker between settings...if i go very slow, i don't get the flicker."
1660438,2017-02-22 15:17:44 UTC,"ok, this bug has evolved
to repro:
reveal the indicator panel for battery/brightness
either select drag element with mouse or choose up/down with hw brightness keys
the slider position will not respond precisely, jump about & at the extremes (max/min) settings there will be flicker between what seems to be 2 different settings"
1660438,2017-02-17 13:27:49 UTC,"Kevin, I can't reproduce this issue on an older dell latitude laptop. When pressing the brightness hardware keys (actually Fn + up/down arrow) the brightness slider moves accordingly, and then moving the slider correctly changes the brightness."
1660438,2017-02-22 17:27:35 UTC,"added a log per request look for ""kg marker"" i made sure to go to the minimum and keep pressing minimum and got the flicker."
1660439,2017-01-30 20:50:01 UTC,We might consider using something like this to avoid the database locking and disk space requirements of the built-in vacuum:
1660439,2019-09-19 11:52:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1660440,2017-04-06 06:56:01 UTC,"> 1. What happens when /var/lib/maas and /var/lib/postgresql are on
>    different partitions?
"
1660440,2017-04-07 07:51:14 UTC,We should also detect/handle the case where the database is running on a remote system (HA).
1660440,2017-07-20 09:11:31 UTC,"FWIW, not only the region, but the rack controller should surface that it is running out of space:"
1660440,2017-07-20 09:11:56 UTC,and we should handle this exception nicely.
1660440,2019-09-19 12:02:10 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1660440,2017-04-05 21:48:08 UTC,Since the rack and region can be run separately we'll need a warning for both. This can be checked as images are being imported on the region and the rack. But what constitutes low disk space? We could check the percentage of free disk space or base the number off the images we currently have.
1660446,2020-04-11 15:27:06 UTC,"In 0.92.4, I have no problems connecting the filters in the way you described, both with your original plan and the proposed workaround. Same in 1.1-dev. Please reopen on http://inkscape.org/report if the problem occurs again."
1660453,2017-01-30 21:36:11 UTC,"This probably should be split into two separate reports:
1) copy&paste n o longer auto-forks filter effects (there might be an existing report about that)
2) regressions in the filter editor which freeze the UI if one of the lists has a scrollbar, and the filter count is updated (disappears e.g. when zooming in/out the canvas view, or scrolling in one of the filter editor dialog's panes). Possibly that's related to earlier reports (e.g. one about the Text&Font dialog freezing in a similar way)."
1660456,2018-02-28 10:26:49 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1660456,2018-02-28 13:42:08 UTC,"Still affects esix-1-3 in 17.10 (Artful Aardvark), so valid. 18.04 not offered for upgrade yet."
1660458,2017-02-02 20:47:08 UTC,"The problem is not related specifically to Grenade, but to a project Grenade is using: devstack-tools. I've submitted a patch to fix this behavior: https://review.openstack.org/#/c/428412/"
1660464,2017-01-31 00:30:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1660464,2017-02-01 00:39:23 UTC,"This is already a project at Canonical, see"
1660480,2017-06-18 21:15:23 UTC,I forgot that I had manually registered OSZL files to open using OpenLP.  It seems the root problem is that the filetype OSZL just isn't registered to OpenLP.
1660480,2019-05-26 20:30:21 UTC,Fix committed
1660488,2018-12-29 05:24:48 UTC,"I looked into this a bit, but I am unsure what the right way to implement this would be. Currently ControllerEngine uses QObject::startTimer/killTimer. I was hoping moving to using QTimer would help because QTimer already supports single shot timers and tracks whether timers are active. However, I'm still not clear how to make ControllerEngine wait for all single shot QTimers to finish executing. I have seen some examples that use a busy-wait loop that calls QCoreApplication::processEvents to avoid blocking the Qt event loop, but IIUC that still uses 100% of the CPU... https://stackoverflow.com/a/11487434"
1660494,2018-05-15 23:53:01 UTC,not tracked part of US sanity tests.
1660498,2019-09-19 11:55:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1660503,2017-01-31 21:02:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660503,2017-11-16 07:21:22 UTC,"Sorry to come by so late Sergei,
but I was clearing some old bug today."
1660503,2018-02-20 16:02:13 UTC,Thank you for the report.
1660503,2018-02-20 16:02:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660503,2020-08-22 11:55:28 UTC,"This is probably something introduced in libmysqlclient.so.20 that is incompatible with older versions of itself (or MariaDB). You could try a newer MariaDB version. Anyway, the libmariadb of mariadb-10.0 in an old Ubuntu release will not be updated at this point in time."
1660508,2017-01-31 03:03:16 UTC,"If I remember correctly, I get the errors since I updated python's ""setuptools"" to work on certbot (development tools), similar to what is demonstrated at https://community.letsencrypt.org/t/cant-install-certbot-on-debian-jessy-unmet-dependencies/19417."
1660508,2017-01-31 03:12:23 UTC,Trying to work around the issue with a
1660529,2020-07-03 14:14:52 UTC,Marking Invalid as no updates in nearly 2.5 years
1660529,2017-10-04 20:44:39 UTC,"Narinder,"
1660536,2017-01-31 18:27:59 UTC,Thank you very much.
1660537,2017-07-20 21:32:27 UTC,"5.4.0 was released 2017-05-01, and release notes are at http://binaries.html-tidy.org/release_notes/5.4.0.html"
1660537,2018-11-14 09:27:09 UTC,FYI there is 2:5.6.0-6 in 19.04 proposed now
1660537,2018-01-23 01:42:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660537,2017-01-31 23:31:05 UTC,"Yes, the current stable version of Debian offers the 2009 tidy. tidy-html5 is a fork. The next stable version of Debian (expected this year) will include the same tidy-html5 5.2.0 currently in Ubuntu 16.10."
1660537,2017-01-31 17:33:39 UTC,Thanks for the quick response Hans.
1660537,2017-01-31 19:01:34 UTC,"> The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software at https://github.com/htacg/tidy-html5/issues .
"
1660537,2017-01-31 18:01:34 UTC,"Just looked a bit more at this, and found that http://www.html-tidy.org/ mentions the latest release is 5.2.0. This seems to be the version available in Ubuntu 16.10 and later, so I'm slightly confused now. Is there a newer version available?"
1660537,2017-01-31 18:00:35 UTC,"It looks like tidy-html5 5.2.0 is the latest stable release available:
https://github.com/htacg/tidy-html5/releases"
1660537,2017-01-31 17:24:22 UTC,"Thanks for reporting. It looks like in 16.10 and later, the package for tidy is tidy-html5. I've taken the liberty of moving this bug report to the right package."
1660537,2017-01-31 19:04:25 UTC,This looks ominous... From Debian:
1660539,2017-08-25 06:55:23 UTC,"Hi i faced exactly same issue. and you should see error in heat-api.log as below:
```
2017-08-25 14:24:48.962 2778 WARNING keystonemiddleware.auth_token [-] Identity response: {""error"": {""message"": ""The request you have made requires authentication."", ""code"": 401, ""title"": ""Unauthorized""}}
```
the issue is credential you configured in heat.conf for keystone_token."
1660539,2020-02-04 08:08:32 UTC,"Just change this :-
    http://controller:35357
to :-
    http://controller:5000"
1660544,2019-09-15 15:53:01 UTC,Migrated to https://github.com/widelands/widelands/issues/1667
1660550,2018-05-07 14:13:58 UTC,Is there more action needed on this bug or can it be closed now?
1660550,2018-06-07 16:45:56 UTC,Setting this to Fix Committed.
1660550,2017-05-19 15:48:06 UTC,Moving this back to New since mvo has addressed all feedback.
1660550,2017-01-31 14:44:15 UTC,Oh yeah this is a weird situation.  :)  I guess it would normally make sense to re-review if the potentially older code was different than what was previously approved.
1660550,2017-03-24 23:25:31 UTC,"In general, the Ubuntu Security team is ok with snapd going into main in 14.04."
1660550,2017-02-01 22:33:08 UTC,"@Seth: We are deploying a deputy or subordinate systemd not running as PID 1 on trusty to support snapd. We isolated systemd on trusty away and minimized its interaction with the system, except for the functionality required by snapd. That is, upstart is still PID 1 and responsible for all system services but snapd."
1660550,2017-01-31 22:17:16 UTC,How are we going to handle snapd's use of systemd on trusty?
1660550,2017-04-05 07:10:32 UTC,"Yes, I can confirm that the snapd upstream developer will be responsive in fixing security issues and we have experience in preparing SRUs for trusty (and the other releases of Ubuntu)."
1660556,2017-04-20 04:17:25 UTC,[Expired for msttcorefonts (Ubuntu) because there has been no activity for 60 days.]
1660556,2017-02-18 15:03:48 UTC,Ralf:
1660556,2017-02-06 04:11:34 UTC,"Wahrscheinlich ein Duplikat von bug 1222654, aber ich bin überrascht, dass dieser bug Fix Released sagt."
1660556,2017-02-18 15:31:17 UTC,Bitte ignoriere meine Kommentare 2 3 5 6 (aber nicht 7 8) und einfach versuch das Paket erneut installieren mit:
1660556,2017-02-06 03:53:38 UTC,"Solch ein Problem hatte ich noch nie gesehen. Ich habe die folgenden potenziellen Lösungen auf Google gefunden (frag ""package is in a very inconsistent state""). Vom weichsten bis zum härtesten:"
1660556,2017-02-06 03:53:07 UTC,"I had never seen such an issue. I found the following potential solutions on Google (look up ""package is in a very bad inconsistent state""). From softest to hardest:"
1660556,2017-02-05 08:50:18 UTC,"Danke! Es funktioniert leider nicht. Ich kann machen was ich will. Die
folgende Fehlermeldung bleibt."
1660556,2017-02-05 01:07:24 UTC,"Wahrscheinlich war ttf-mscorefonts-installer nicht erfolgreich installiert. Leider wird eine neue Installation ttf-mscorefonts-installer wegen bug 1607535 auch scheitern, weil es sieht aus, deine Version apt < 1.2.19 ist. Versuch mal, ttf-mscorefonts-installer zu löschen, deine apt Pakete bis 1.2.19 zu upgraden, und ttf-mscorefonts-installer wiederzuinstallieren:"
1660556,2017-02-05 00:41:34 UTC,"It looks like a previous install of ttf-mscorefonts-installer failed. But reinstalling it may fail because of bug 1607535, since your version of apt is apparently < 1.2.19. Try removing it completely, updating apt packages to 1.2.19, and reinstalling it:"
1660556,2017-02-06 03:58:18 UTC,Probably a duplicate of bug 1222654 but I'm surprised that this bug says Fix Released.
1660568,2018-03-29 09:04:49 UTC,syslog
1660568,2019-01-31 23:47:37 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1660568,2019-02-01 00:13:56 UTC,I raised this a long time ago.  I'm now on 18.04 using gnome and have no urge to return to unity.
1660574,2018-05-04 00:22:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660574,2018-05-04 00:29:16 UTC,"I had this issue yesterday on 17.10.  The IPV4 address for my Ethernet interface vanished.  I could not find any option in the network portion of settings to ask the DHCP for the IP address, and sudo service network-manager restart did not recover, so I rebooted the system.  This is obviously an extremely rare situation and I do not know how to reproduce it.  If there is no notification that the network manager can register for to detect this situation automatically then there should be a reinitialize button in the network settings GUI."
1660579,2017-01-31 14:05:38 UTC,fix merged - https://review.openstack.org/#/c/427106/
1660583,2017-03-10 16:18:31 UTC,"We need env to debug, please provide it as soon as reproduced."
1660586,2020-08-03 13:34:25 UTC,"More germanely,"
1660586,2017-08-18 08:52:18 UTC,This is still an issue as of 2.27.2 though the error message no longer includes the URL vomit. Instead it is like this:
1660586,2020-08-03 09:22:02 UTC,this is fixed since a while:
1660586,2017-04-18 00:00:46 UTC,I also noticed this with 2.23.6.
1660587,2017-09-22 18:44:24 UTC,Any news?
1660587,2017-01-31 13:13:01 UTC,apport information
1660587,2017-01-31 13:13:00 UTC,apport information
1660587,2017-01-31 13:12:58 UTC,apport information
1660587,2017-01-31 13:12:57 UTC,apport information
1660587,2017-01-31 11:18:30 UTC,"https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/1548558
Related bugreport."
1660587,2017-01-31 13:12:55 UTC,apport information
1660587,2017-01-31 13:12:56 UTC,apport information
1660587,2017-01-31 11:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1660587,2017-01-31 13:12:49 UTC,apport information
1660587,2017-04-28 09:46:31 UTC,"I guess this bug is why I can't upgrade my kernel :
( 17.04 + zfs-dracut )"
1660587,2017-01-31 13:12:51 UTC,apport information
1660587,2017-01-31 13:12:54 UTC,apport information
1660587,2017-01-31 13:12:50 UTC,apport information
1660589,2019-09-19 12:02:12 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1660605,2019-01-29 17:28:13 UTC,"Ack, makes sense that this happens — the first caffeination apparently enables the screensaver at its end, leading to a suspend. It should probably do something like a non-binary lock counter, so that only when the last process ends, caffeination ends."
1660605,2019-01-29 21:58:03 UTC,I'm the maintainer of caffeinate.
1660606,2017-02-08 15:46:21 UTC,"Change abandoned by Vasyl Saienko (<email address hidden>) on branch: master
Review: https://review.openstack.org/430245
Reason: moved to parent patch."
1660606,2017-03-15 14:19:02 UTC,Vasyl submitted this patch https://review.openstack.org/#/c/423556/:
1660606,2017-03-16 00:06:29 UTC,"Reviewed:  https://review.openstack.org/423556
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=e48375538c11a988e66fd9eadc944e82cb7f4b57
Submitter: Jenkins
Branch:    master"
1660606,2017-08-02 00:15:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489790"
1660606,2017-08-02 16:26:21 UTC,"Change abandoned by John L. Villalovos (<email address hidden>) on branch: master
Review: https://review.openstack.org/489790
Reason: Will work with infra to do a batch upload."
1660606,2017-10-18 18:12:30 UTC,"there aren't any patches to address this, so I'm changing the status to 'Triaged'."
1660608,2017-02-01 02:01:34 UTC,"This is a distinction that has caught me out several times, and I think it needs fixing.  There are pros & cons for using only a stage-specific file vs. updating collect to behave like deploy."
1660609,2017-02-02 12:29:13 UTC,"Dmitry, please see the advisory here.  https://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=452749&docId=emr_na-c02227387&docLocale=en_US
let us know if the bug is same as that listed in the advisory if yes we can have a check in proliantutils for the same and error out if shared iLO port is sued fro deploy"
1660609,2017-02-01 15:11:37 UTC,"Are there any ironic logs that could be shared for this issue.
The shared network port should not have any impact on Ironic functioning as long as the DHCP server and the bare metal are in the same subnet so that BOOTP requests could be served by the DHCP server. However the communication with the iLO for performing the power operation on the baremetal should not get impacted.
The parent bug suggests that inspection goes through, is it using Ironic-inspector or OOB inspection provided by iLO drivers? Can you also share the hardware and firmware details of the impacted Proliant system."
1660614,2017-01-31 15:17:08 UTC,From Stephen: Consider having the nodejs plugin support per project .npmrc so users can set cache options themselves rather than set via args in the plugin.
1660618,2017-01-31 16:31:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1660620,2017-01-31 14:09:45 UTC,"Fix proposed to branch: master
Change author: Dmitry Kaigarodsev <email address hidden>
Review: https://review.fuel-infra.org/30293"
1660620,2017-01-31 15:03:43 UTC,"Reviewed: https://review.fuel-infra.org/30293
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1660620,2017-02-01 10:30:58 UTC,The problem is still there. See https://plugin-ci.fuel-infra.org/job/master.fuel-plugin.influxdb-grafana.deploy-test/121/console
1660620,2017-02-01 10:31:58 UTC,"AFAICT ""UBUNTU_DIST=trusty"" is injected too late, it should be done before guess-mirror."
1660620,2017-02-01 10:58:35 UTC,"Fix proposed to branch: master
Change author: Dmitry Kaigarodsev <email address hidden>
Review: https://review.fuel-infra.org/30320"
1660620,2017-02-01 11:26:24 UTC,"Reviewed: https://review.fuel-infra.org/30320
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1660622,2017-02-09 15:08:23 UTC,I retested this on 16.04 with clang-3.8 and there exists the same issue.
1660622,2018-03-13 09:37:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660645,2017-01-31 15:19:00 UTC,Forgot to include similar bug reports #59981 and #165004.
1660646,2017-02-07 07:31:04 UTC,This bug also affect all networking-* drivers (neutron extensions). They should be upgraded before neutron. We need to find a permanent fix for this which looks like require building dependency graph between services.
1660646,2017-01-31 16:13:41 UTC,"@Vasyl Saienko, do you mind adding steps to recreate this bug please?"
1660646,2017-01-31 17:11:12 UTC,discussion in irc with perhaps a good/easy fix for this:
1660646,2017-01-31 15:18:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/427248"
1660646,2017-01-31 21:13:47 UTC,"Reviewed:  https://review.openstack.org/427248
Committed: https://git.openstack.org/cgit/openstack-dev/grenade/commit/?id=99c8c9e998ea9a95845958fd6b1f8dbae9fadef1
Submitter: Jenkins
Branch:    master"
1660647,2017-01-31 16:03:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/427267"
1660647,2017-02-03 04:21:52 UTC,"Reviewed:  https://review.openstack.org/427267
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=67aa277b4ef623c9877b97bfd7952f0bb1d80a81
Submitter: Jenkins
Branch:    master"
1660647,2017-02-03 09:53:46 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/428671"
1660647,2017-02-03 19:08:22 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc1 release candidate.
1660647,2017-02-16 04:39:18 UTC,"Reviewed:  https://review.openstack.org/428671
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9f8d15dcc1b4db9b1116d19b6af0f6cac15ff9fe
Submitter: Jenkins
Branch:    stable/newton"
1660647,2017-02-27 20:28:56 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1660652,2020-06-14 10:32:20 UTC,"Hi, Why has this altered to unconfirmed with the linking to the GitHub issue?"
1660652,2017-04-01 20:06:29 UTC,"Hi tkoun, as it affects you too please change its status from New to Confirmed as that might mean it gets some attention."
1660652,2017-04-08 11:18:38 UTC,Changing to confirmed because another commenter also has the problem.
1660652,2017-04-01 17:55:07 UTC,"this one is a real bummer... Fed up having to give my password twice 'cause the first time it gets truncated.
I'll try to downgrade before considering switching to some other login manager."
1660675,2017-04-10 16:11:48 UTC,"@jameinel User based tagging in the form of ""juju add-tags --machine|--model|--application <comma separated list of tags>""."
1660675,2017-04-10 15:03:16 UTC,"Would this be model based, application based, user based tagging? Is it just you want a 'juju tag-machine' command? Or are you looking for some sort of default set of tags/user configurable tags. What is the context of those tags for your use case?"
1660687,2017-01-31 16:36:37 UTC,John?
1660687,2017-02-01 17:09:36 UTC,Looks like [1] needs to be updated to describe the hybrid driver system.
1660687,2017-04-21 15:07:59 UTC,"Had a short chat in IRC. I think as part of the solution here, we need to evolve [1] into a higher-level document describing the firewall driver config option and how its used, including the documentation on how one could configure different firewall drivers on each agent. So, the tasks would be:"
1660687,2017-04-21 15:08:33 UTC,"By ""this document"" I mean [1]."
1660687,2017-04-21 16:25:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458911"
1660687,2017-04-25 05:02:13 UTC,"Reviewed:  https://review.openstack.org/458911
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=ff028f638cb290569624aac2ccfcb82d6c846f29
Submitter: Jenkins
Branch:    master"
1660694,2017-02-03 12:49:56 UTC,"For verification purposes, we should properly maintain test image (e.g. we'd rebuilt Cirros for 9.0 for SR-IOV verification purposes)."
1660694,2017-03-17 12:10:20 UTC,Moving from 9.2-mu-1 since Fuel User Guide is not part of maintenance updates and doesn't follow the timeframe of a MU.
1660694,2017-02-03 15:26:27 UTC,"Change abandoned by Alexander Adamov <email address hidden> on branch: master
Review: https://review.fuel-infra.org/30467
Reason: Moving to Fuel User Guide"
1660694,2017-02-03 15:19:49 UTC,"Related fix proposed to branch: master
Change author: Alexander Adamov <email address hidden>
Review: https://review.fuel-infra.org/30467"
1660694,2017-02-03 15:03:14 UTC,"Reviewed: https://review.fuel-infra.org/30465
Submitter: Olena Logvinova <email address hidden>
Branch: stable/9.2"
1660694,2017-02-03 15:01:04 UTC,"Related fix proposed to branch: stable/9.2
Change author: Mariia Zlatkova <email address hidden>
Review: https://review.fuel-infra.org/30465"
1660694,2017-02-03 15:00:29 UTC,"Reviewed: https://review.fuel-infra.org/30461
Submitter: Olena Logvinova <email address hidden>
Branch: master"
1660694,2017-02-03 13:44:20 UTC,"Related fix proposed to branch: master
Change author: Mariia Zlatkova <email address hidden>
Review: https://review.fuel-infra.org/30461"
1660694,2017-02-02 10:50:27 UTC,"Reviewed: https://review.fuel-infra.org/30364
Submitter: Mariia Zlatkova <email address hidden>
Branch: stable/9.2"
1660694,2017-02-01 16:12:07 UTC,"Reviewed: https://review.fuel-infra.org/30341
Submitter: Olena Logvinova <email address hidden>
Branch: master"
1660694,2017-01-31 17:19:20 UTC,"fuel snapshot:
https://drive.google.com/open?id=0B05EZCZN-hilaVlxZmxoLXZEems"
1660694,2017-02-01 05:24:21 UTC,We don't have proper driver  i40evf in our image. The problem is because of that
1660694,2017-02-01 08:07:19 UTC,"Hi Mikhail, could you please take a look?"
1660694,2017-02-02 10:40:28 UTC,"Related fix proposed to branch: stable/9.2
Change author: Mariia Zlatkova <email address hidden>
Review: https://review.fuel-infra.org/30364"
1660694,2017-02-01 11:13:03 UTC,"If customers have such problems, it is necessary to build image with this driver or make it using trusty image (create vm with trusty image, download and install i40evf driver, make snap from it and boot vm from this snap)"
1660694,2017-02-01 15:06:09 UTC,"Related fix proposed to branch: master
Change author: Mariia Zlatkova <email address hidden>
Review: https://review.fuel-infra.org/30341"
1660694,2017-02-01 10:03:06 UTC,"Hi Timur,"
1660694,2017-02-01 11:19:48 UTC,The driver can be added by installing linux-image-extra packet: sudo apt-get install linux-image-extra-$(uname -r)
1660701,2017-02-03 16:45:51 UTC,Hello Mark - Thanks for the bug report! We are aware of this flaw in cryptsetup and have triaged it in the Ubuntu CVE Tracker:
1660703,2017-01-31 19:36:42 UTC,"Yes, good idea."
1660715,2017-01-31 21:14:08 UTC,"Since the suite does define an exact version of pyflakes, we get inconsistent results. There are also user rules that leak. We need to force the versions of flake8 used by lint and ensure it can be installed on all supported hosts"
1660725,2020-07-02 17:01:17 UTC,"From the error tracker, this crash was seen in apache versions between 2.4.6 (Ubuntu 13.10) and 2.4.27 (Ubuntu 17.10) but there have been no instances of the issue on Ubuntu 18.04 or newer.  It appears to still exhibit itself in the version published for Ubuntu 16.04, apache2 2.4.18-2ubuntu3.14.  There is a .15 in proposed for xenial but it doesn't sound like a fix for this crash.  So the issue is still relevant for xenial at least.  Indeed, the last occurrence reported was Jan 23, 2020."
1660730,2017-02-03 16:33:26 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1660741,2020-04-02 05:21:06 UTC,"Thanks for sharing with us the following update.It is informational and explanatory.I want to include that if any sort of assistance is required for handyman services which includes carpentry,electrical,plumbing,painting,masonry can directly contact with the most reliable https://handyman-dubai.com/maintenance-company-dubai who provides 100% assistance with support across the globe for more than a decade."
1660744,2017-02-03 16:24:39 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Attackers wouldn't typically have the ability to directly influence the command line arguments and, in this case, it doesn't seem to matter if they did since the crash happens early on in the argument parsing code. Please feel free to report any other bugs you may find."
1660745,2017-02-01 04:32:20 UTC,It seems to be an oversight. We agree that read-access should be sufficient.
1660756,2017-01-31 20:13:51 UTC,"Pat, can you please attach the yaml please? I think I've hit this problem when the right side value had a "":"", and then yaml goes crazy."
1660756,2017-03-15 21:53:09 UTC,"I ran into this same error message and it was because I did not have a "":"" after the key name e.g.:"
1660756,2017-03-15 21:53:52 UTC,This was with version 2.27.1 of snapcraft.
1660758,2017-02-07 17:28:35 UTC,"Here is the snapshot from the Fuel Master.
All it took was a reboot of any node and it would end up in bootstrap mode instead of the role it was deployed in."
1660758,2017-02-01 13:35:31 UTC,Could you please provide us a diagnostic snapshot from the Fuel master node? And please also describe the exact sequence of steps that could be used to reproduce the issue.
1660768,2017-02-08 00:02:29 UTC,"Yes, this is a known restriction due coming from heat-translator. We are working with tosca-parser and heat-translator team to remove this (it is a bigger effort on their side). A fix will be available in Pike."
1660807,2017-02-19 03:52:08 UTC,"What keywords should be expected? Comparing the keywords from 0.4 and 0.3, the difference is using plural alongside singular names?"
1660807,2017-02-22 03:35:42 UTC,"In fact the ones wrong are not from the pantheon-photos desktop file but the photo-viewer, however not sure what keywords apply."
1660810,2019-09-19 15:00:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1660812,2019-09-19 12:02:14 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1660820,2017-02-07 17:19:15 UTC,"I don't think revision-results is really to blame here.  The daily builds were only getting built when the the results were blessed, and the results weren't blessed often enough.  I don't think it makes sense to execute a new PPA build for each CI run.  Today, for example, we've had 13 CI runs."
1660820,2017-02-07 18:46:43 UTC,"Until the 'edge' channel replaces this job, I suppose manual runs may be sufficient."
1660821,2017-02-07 17:32:37 UTC,"Sorry, ignore 1."
1660821,2017-02-07 17:32:12 UTC,"Here are the options I see:
- We can manually trigger github-merge-branches on the rare occasion that there is a bless.
- The update-outcome script can trigger github-merge-branches when there is a bless.
  - This will happen before the reports site is updated
  - We may need to work to prevent github-merge-branches from being called multiple times
  - This prevents us from using outcome analyser in determining a bless
- The get-s3-ci-results script can trigger github-merge-branches when there is a bless
  - This will happen roughly simultaneously with updating the report
  - We may need to work to prevent github-merge-branches from being called multiple times
  - This allows us to use outcome analyser in determining a bless
- We can add a REST API to the reports site.
  - github-merge-branches would use the API to determine the last blessed build
  - github-merge-branches would run periodically, and exit early most of the time."
1660821,2017-02-07 18:49:33 UTC,"While manual works for now, I'd like to see something trigger this job as before. It seems like nothing proposed is a trivial fix, so while I don't think this ""feature"" necessitates extra work, I'm guessing we'll want other jobs to key off blessed/cursed builds in the future. Perhaps not."
1660823,2017-02-01 09:17:47 UTC,"Sai, was there an attempt to delete stack? Any logs would be helpful!"
1660825,2019-10-28 17:19:00 UTC,Hey Goutham any update on this one ?
1660825,2020-03-19 15:44:56 UTC,Additional comments http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-03-19-15.00.log.html
1660828,2017-02-01 04:06:44 UTC,"TokuDB PFS is not merged. Roel, can you please test PS and MySQL under Valgrind and/or ASan with this testcase?"
1660828,2017-02-02 07:55:24 UTC,Tested with Valgrind. Discussing w/ Laurynas
1660828,2017-02-02 08:19:43 UTC,"Reproduced Valgrind SIGSEGV on MS also
Now dup of https://bugs.mysql.com/bug.php?id=84786"
1660828,2017-05-03 03:25:10 UTC,https://github.com/percona/percona-server/pull/1678
1660828,2017-05-05 09:23:49 UTC,https://github.com/percona/percona-server/pull/1695
1660828,2018-01-25 08:56:57 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1056
1660829,2017-01-31 22:31:04 UTC,This change was made by a bot.
1660832,2017-04-24 14:11:40 UTC,This bug was fixed in the package linux - 4.8.0-49.52
1660832,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1660832,2017-03-30 09:21:03 UTC,Not fixed because we had to revert the commits due to various regressions.
1660832,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1660832,2017-02-22 04:58:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660832,2017-02-27 17:15:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1660832,2017-02-27 17:14:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1660832,2017-02-24 17:14:53 UTC,"I can confirm this problem was fixed for Xenial on 4.4.0-65.86, thank you."
1660832,2017-01-31 23:00:57 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1660832,2017-03-02 08:46:11 UTC,This bug was fixed in the package linux - 4.8.0-40.43
1660832,2017-02-21 03:06:26 UTC,This bug was fixed in the package linux - 4.10.0-8.10
1660835,2017-02-01 12:21:26 UTC,Does this also work for you e.g. for volume_extension:hosts ?
1660835,2017-02-06 20:29:27 UTC,"I have the same issue with volume_extension:hosts.
I noticed that the volume_extension:volume_host_attribute tempest test is not listed as an admin test. Is this a mistake in tempest?"
1660835,2017-05-08 06:17:39 UTC,"Hi,"
1660842,2017-07-26 15:57:12 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1660842,2017-03-29 23:13:19 UTC,This bug was fixed in the package linux - 4.8.0-45.48
1660842,2017-03-28 09:29:26 UTC,Not fixed because we had to revert the commits due to various regressions.
1660842,2017-01-31 23:31:00 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1660842,2017-03-02 08:46:11 UTC,This bug was fixed in the package linux - 4.8.0-40.43
1660842,2017-02-27 17:16:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1660842,2017-02-27 17:14:27 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1660842,2017-02-21 03:06:26 UTC,This bug was fixed in the package linux - 4.10.0-8.10
1660842,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1660845,2017-07-26 15:57:15 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1660845,2017-03-29 23:13:19 UTC,This bug was fixed in the package linux - 4.8.0-45.48
1660845,2017-03-28 09:28:58 UTC,Not fixed because we had to revert the commits due to various regressions.
1660845,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1660845,2017-03-02 08:46:11 UTC,This bug was fixed in the package linux - 4.8.0-40.43
1660845,2017-02-27 17:16:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1660845,2017-02-27 17:14:35 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1660845,2017-02-21 03:06:26 UTC,This bug was fixed in the package linux - 4.10.0-8.10
1660845,2017-02-01 00:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1660846,2017-03-29 23:13:19 UTC,This bug was fixed in the package linux - 4.8.0-45.48
1660846,2017-03-28 09:28:25 UTC,Not fixed because we had to revert the commits due to various regressions.
1660846,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1660846,2017-07-26 15:57:18 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1660846,2017-02-27 17:16:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1660846,2017-02-27 17:14:32 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1660846,2017-02-21 03:06:26 UTC,This bug was fixed in the package linux - 4.10.0-8.10
1660846,2017-02-01 00:00:19 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1660846,2017-03-02 08:46:11 UTC,This bug was fixed in the package linux - 4.8.0-40.43
1660861,2019-03-11 20:31:26 UTC,Thank you for your report.  Can you still reproduce this?  Do you have the python-paramiko package installed?
1660865,2017-02-07 13:56:10 UTC,This is merged in trunk and will be in snapd 2.23.
1660867,2017-05-12 16:54:53 UTC,"$ pip search kuryr | grep kube
kuryr-kubernetes (0.1.0)  - Kubernetes integration with OpenStack networking"
1660873,2017-03-16 04:19:44 UTC,and reboot compute vm
1660873,2017-03-16 00:09:33 UTC,"def set_vif_host_backend_ethernet_config(conf, tapname):
    """"""Populate a LibvirtConfigGuestInterface instance
    with host backend details for an externally configured
    host device."
1660876,2017-02-15 14:11:17 UTC,I was able to resolve this with:
1660876,2018-07-12 15:16:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660879,2017-02-07 17:03:52 UTC,https://github.com/snapcore/snapd/pull/2805
1660879,2019-10-29 18:38:44 UTC,The referenced pull request was merged a long time ago. I'm marking this bug as fix released.
1660882,2017-02-01 04:30:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1660883,2019-09-19 11:55:49 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1660883,2017-02-01 15:20:35 UTC,"Removed blocker tag - this was happening when we commissioned with trusty, which we don't normally do."
1660885,2017-02-01 04:35:18 UTC,"Maybe, we could use a variable for cwd, the directory where snapcraft is called from."
1660886,2017-02-02 06:33:59 UTC,"@Jason,"
1660886,2017-02-02 14:19:39 UTC,"Anastasia, that's neat!  Yeah, I had no idea because it's not obvious at all, and maybe a little subversive, to ask someone to run a command that will have them talking out over a network without it being obvious. Could also lead to confusion when firewalls are involved."
1660887,2018-05-23 21:12:09 UTC,"Cash App is like Venmo…but better.  I need the cash.  Install the app and send me your $5 if you are charitable lol.  Feel free to uninstall it if you don’t like the app.  But it would help me out.
Thanks!"
1660887,2020-07-03 04:44:50 UTC,"DistroRelease: Kali 2016.2
linux-base (4.5)"
1660887,2017-06-12 12:58:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660889,2017-02-09 17:02:38 UTC,https://mir-jenkins.ubuntu.com/job/device-runtests-mir/device_type=krillin/2980/consoleFull
1660889,2017-03-02 10:43:39 UTC,Again:
1660889,2017-03-14 15:23:04 UTC,https://mir-jenkins.ubuntu.com/job/device-runtests-mir/device_type=krillin/3259/consoleFull
1660889,2017-03-29 05:03:03 UTC,Again:
1660889,2017-04-19 02:54:06 UTC,And here:
1660889,2017-11-03 16:42:38 UTC,Syncing task from Mir.
1660893,2017-02-01 09:02:32 UTC,"Looks like bug need to be in [networking-sfc]. In any case, if the server is deleted after port-chain, there should not be any issue. But this also needs to get handled."
1660893,2017-04-17 05:11:42 UTC,It can't reproduce on recently master branch.
1660902,2017-02-01 16:34:45 UTC,"I agree. Actually, I meant to bring this up in the PR introducing that feature, but forgot. This is a little sticky because the test will then become architecture-dependent. How do we handle that in the suite?"
1660902,2017-02-01 17:16:36 UTC,We have a few tests that ask the current architecture in order to get a different one. That's an option.
1660903,2017-02-01 16:40:31 UTC,"> If you actually go ahead an run that command, dpkg will not complain about the invalid architecture, which leaves you with invalid apt sources.
"
1660903,2017-09-15 09:55:07 UTC,"So, in my PR 31348 [1] to setup the host for multiple architectures, I'm using 'dpkg --print-architecture' followed by 'dpkg --print-foreign-architectures' to tell what's already installed, and if not tell you what's required to add it. The error message will replace the error being discussed here, if I also use 'dpkg-architecture -L' in the error as per Kyle's suggestion.
Although if preferred I can make it two separate PRs."
1660913,2017-02-01 08:36:19 UTC,Diagnostic snapshot: https://drive.google.com/file/d/0B9nJDnRluay9RDNYTGlZUFhsbEE/view?usp=sharing
1660913,2017-03-14 10:41:30 UTC,There is no logs related to murano in attached snapshot. Please provide a env to debug.
1660916,2017-02-01 08:55:49 UTC,"Installation is going on ""from the beginning"".
I've been left with no info at all on what was happening for almost 1 hour!
That cannot be good, some sort of ""Please wait"" would be apreciated."
1660932,2017-02-01 10:20:16 UTC,"This is happening because cluster-upgrade extension creates a new environment with exactly the same parameters, such as mode and net_provider, as an original one has. It seems as a lag in validation of users' data and operator possibilities. Several simple improvements can be made here:"
1660938,2017-07-04 01:08:14 UTC,"Agreed that the templates should be re-jiggered for ports architectures.  To provide some context, while the ubuntu-ports rsync module is open for anyone to mirror, Launchpad does not currently keep track of community ports mirrors like we do with https://launchpad.net/ubuntu/+archivemirrors , nor are there any non-Canonical CCTLD DNS mirrors (AFAIK nobody's volunteered to become one)."
1660941,2017-02-01 12:13:29 UTC,https://github.com/snapcore/snapd/pull/2756
1660949,2017-02-07 17:57:25 UTC,apport information
1660949,2017-02-07 17:57:23 UTC,apport information
1660949,2017-02-07 17:57:21 UTC,apport information
1660949,2017-02-07 17:57:20 UTC,apport information
1660949,2017-02-07 17:57:14 UTC,apport information
1660949,2017-02-07 17:57:12 UTC,apport information
1660949,2017-02-07 17:57:11 UTC,apport information
1660949,2017-02-07 17:57:09 UTC,apport information
1660949,2017-02-07 17:57:06 UTC,apport information
1660949,2017-02-07 17:57:08 UTC,apport information
1660949,2017-02-07 17:57:02 UTC,apport information
1660949,2017-02-07 17:56:59 UTC,apport information
1660949,2017-02-07 17:56:57 UTC,apport information
1660949,2017-02-07 17:56:55 UTC,apport information
1660949,2017-02-03 12:01:59 UTC,"Again:: what logs would you like to see for this?  I am happy to provide them, but you have to tell me which are needed."
1660949,2017-02-01 17:53:55 UTC,That's not possible for me to do; sorry.
1660949,2017-02-01 16:01:46 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1660949,2017-02-01 14:13:26 UTC,Seriously: please tell me *what* logs are needed here if apport-collect cannot — and I will provide them.
1660949,2017-02-01 12:44:15 UTC,"I don't believe that the ""issue I have encountered"" has an effect on this, but running apport-collect as suggested does nothing but initiate an OAuth token loop at the Launchpad site, with me authorizing this machine followed by ... nothing happening on the terminal or on the site."
1660949,2017-02-01 12:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1660949,2017-02-07 17:57:04 UTC,apport information
1660954,2017-02-07 05:35:11 UTC,"Confirming for now as is - the reported issue reproduces in rasterized output based on the same SVG file with Inkscape 0.91 r13725, 0.92.0 r15299, GIMP 2.9.3, and rsvg-convert (librsvg 2.40.13) on OS X 10.7.5, with cairo 1.14.6 and 1.15.5 (git)."
1660954,2017-02-10 00:56:31 UTC,"Made a test image with lowered opacities, fading gradients, lowered alphas, compositing with filters, masking and clipping. All seems affected by the issue in win64 Inkscape 0.92.0 r15299."
1660954,2017-02-06 09:15:14 UTC,"Testing with GIMP layer alpha threshold set to 0 (see bug #882236), it is to be noted that opening the sample SVG file itself in GIMP (2.8.16, 2.9.3) shows the same unexpected colors for the (anti-aliased transparent) pixels as with Inkscape's bitmap export (0.91, 0.92) - it seems that this is not a unique issue to be fixed in Inkscape's own renderer."
1660954,2017-02-06 04:06:16 UTC,"Note to self: investigate whether related to or same as
* Bug #882236 “Antialiasing changes shape color when exported to image file”
  https://bugs.launchpad.net/inkscape/+bug/882236"
1660954,2017-02-07 01:30:19 UTC,"Hi su_v, I just opened the example svg (that were created in Inkscape) in Illustrator CS6 and exported a png. The unexpected colors are not present there, the PNG has only one color. I did the same in GIMP and Inkscape, and both does indeed still create the unexpected colors on the transparent antialiased edge. I wonder why Illustrator is working properly with the PNG export, while Inkscape and GIMP does not?"
1660957,2017-02-06 06:36:36 UTC,"For what it is worth, these are the policy changes I needed to get these APIs working:"
1660958,2017-02-16 22:00:31 UTC,"Same problem on BQ Aquaris E4.5 Ubuntu Edition (OTA-15).
After app start it crashes at once."
1660970,2017-04-20 09:00:23 UTC,"snap info will complete against ""any snap name"", meaning it will complete directories (so you can find .snaps or directories that have a meta/snap.yaml), installed snaps, and remote snaps. This isn't a priority order, but the remote snaps will only complete if you give it at least three characters to search for (this is the only part that is weird I think, but knowing it also allows you to cheat). It seems to work well for me: having the 'http' snap installed, in a directory with a 'httputil' subdirectory, 'snap info ht<tab>' completes to http and a second tab will offer http, httpstat, and httputil/, as expected. Having rocketchat-server installed, ""snap info ro<tab>"" offers rocketchat-server, whereas ""snap info roc<tab>"" only completes as far as rocketchat- because of it now also doing a remote search and finding more stuff."
1660970,2019-10-29 19:42:53 UTC,"Currently snapd completes ""snap info"", ""snap interfaces"" but not ""snap run""."
1660970,2019-11-26 10:15:34 UTC,"for very-infrequent values of ""active"", yes."
1660975,2017-02-03 10:52:59 UTC,Hello
1660975,2017-02-07 09:54:08 UTC,I have seen it on my packstack env:
1660981,2017-03-08 12:21:24 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1660981,2017-03-07 13:06:57 UTC,"Reviewed:  https://review.openstack.org/442434
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=4e9f2dd510ac7e4758ce54be7cd76a8448031e02
Submitter: Jenkins
Branch:    stable/ocata"
1660981,2017-03-07 12:40:10 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442434"
1660981,2017-02-28 14:12:59 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/438971"
1660981,2017-02-28 13:54:57 UTC,"Reviewed:  https://review.openstack.org/433047
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=2c381ff80b52191af5b4085c1fb27a79c220bf1e
Submitter: Jenkins
Branch:    master"
1660981,2017-03-02 15:57:58 UTC,"Reviewed:  https://review.openstack.org/438971
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=0c53d8139ef3e09288cb789acade1d4fded4ef52
Submitter: Jenkins
Branch:    stable/newton"
1660981,2017-02-13 13:14:26 UTC,"Reset to ""confirmed"" since in case with ceilometer on board the nova user shell is being modified by scripts of ceilometer-common package."
1660981,2017-02-27 16:28:54 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1660981,2017-02-02 09:27:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/428044"
1660981,2017-02-13 13:16:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433047"
1660981,2017-02-07 07:27:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430104"
1660981,2017-02-06 17:10:47 UTC,"Reviewed:  https://review.openstack.org/428044
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=8fb8e7f7df9218b91540c56f3e0bab16edc1cb64
Submitter: Jenkins
Branch:    master"
1660981,2017-02-08 09:03:29 UTC,"Reviewed:  https://review.openstack.org/430104
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=7453bb3d23aaf7809e2e7df8067c3caf5d78fd1e
Submitter: Jenkins
Branch:    stable/newton"
1660986,2021-01-07 08:53:52 UTC,Zesty EOL.
1660993,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1660993,2017-02-02 19:47:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660994,2017-02-02 19:47:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1660994,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1660998,2017-02-01 14:53:11 UTC,Here's a recent thread about 7.12 and NEON 2
1660998,2017-02-16 09:33:28 UTC,"Hi,"
1661003,2019-12-18 17:21:59 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/451288
Reason: This repo is retired now, no further work will get merged."
1661003,2017-05-17 07:54:03 UTC,Verified on 9.2 + mu2 updates.
1661003,2017-03-29 09:36:42 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/451288"
1661003,2017-04-06 08:46:26 UTC,"Reviewed:  https://review.openstack.org/450722
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=365c7735e4af7fe34c9a41c380200424870db7d2
Submitter: Jenkins
Branch:    stable/mitaka"
1661003,2017-03-15 09:31:50 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445841"
1661003,2017-03-15 08:44:30 UTC,"Reviewed:  https://review.openstack.org/428140
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=4d18ef0dadedb05e4876b42123a11a0121f5f708
Submitter: Jenkins
Branch:    master"
1661003,2017-02-02 13:27:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/428140"
1661003,2017-03-17 09:10:47 UTC,"Reviewed:  https://review.openstack.org/445841
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=3e67eb00435b0480a285603cc7317389db8b4e17
Submitter: Jenkins
Branch:    stable/newton"
1661003,2017-03-28 11:14:55 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/450722"
1661004,2017-04-07 10:58:22 UTC,I have verified that the latest installation of 10.0 does have the fix https://review.fuel-infra.org/#/c/14563/ . Checked file /usr/lib/ocf/resource.d/pacemaker/SysInfo. Installed pacemaker:
1661004,2017-03-09 12:40:53 UTC,"Reviewed: https://review.fuel-infra.org/31708
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1661004,2017-03-09 09:16:31 UTC,"Fix proposed to branch: 10.0/newton
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/31708"
1661004,2017-03-09 08:57:00 UTC,"Reviewed: https://review.fuel-infra.org/31622
Submitter: Pkgs Jenkins <email address hidden>
Branch: master"
1661004,2017-03-07 13:37:55 UTC,"Fix proposed to branch: master
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/31622"
1661004,2017-03-07 12:17:00 UTC,"Reviewed: https://review.fuel-infra.org/31618
Submitter: Dmitry Burmistrov <email address hidden>
Branch: master"
1661004,2017-03-07 12:13:33 UTC,"Reviewed: https://review.fuel-infra.org/31616
Submitter: Andrey Nikitin <email address hidden>
Branch: master"
1661004,2017-03-07 12:08:26 UTC,"Related fix proposed to branch: master
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/31618"
1661004,2017-03-03 16:15:53 UTC,Dmitry - is there a way that I can manually apply the patch to the pacemaker package? Before or after building a fuel iso? I looked but haven't spent much time looking at the packages in fuel before so I'm not sure where I may find pacemaker/extra/resources. Or is the workaround just editing the Sysinfo scripts on each node after they're pushed onto the slave nodes?
1661004,2017-03-07 12:06:21 UTC,"Related fix proposed to branch: master
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/31616"
1661004,2017-02-01 19:08:15 UTC,"Please attach diagnostic snapshot, marking as Incomplete."
1661004,2017-02-01 21:34:00 UTC,"Uploading diagnostic snapshot in split archive, upload was timing out."
1661004,2017-02-01 21:36:30 UTC,Part 3/3 of snapshot.
1661004,2017-03-06 12:06:30 UTC,"Raymond, if you can repackage the pacemaker deb package, do that. Then put the package in a dedicated mirror and add that mirror to the environment with high priority."
1661004,2017-03-02 08:11:23 UTC,"Failure example (with rabbitmq 3.6.6 on board):
https://build.opnfv.org/ci/job/fuel-deploy-baremetal-daily-master/1776/console"
1661004,2017-03-02 10:22:47 UTC,In the unpacked snapshot unpack logs-node-13-10.130.0.8.tar.gz and do the following grep - http://paste.openstack.org/show/601088/
1661004,2017-03-01 20:30:07 UTC,"Marked as confirmed, because we see same failures in Opnfv, raising priority because without HA release is broken."
1661004,2017-03-02 11:16:23 UTC,"The problem is clear - once we moved to Xenial in 10.0, we stopped packaging our own Pacemaker and use the upstream one. But it is missing fix for bug https://bugs.launchpad.net/fuel/+bug/1524729 which we did not push upstream, and hence the face the problem."
1661012,2017-02-02 15:39:35 UTC,"Fix proposed to branch: master
Change author: Andrey Nikitin <email address hidden>
Review: https://review.fuel-infra.org/30441"
1661012,2017-02-02 16:20:28 UTC,"Reviewed: https://review.fuel-infra.org/30441
Submitter: Andrey Nikitin <email address hidden>
Branch: master"
1661016,2017-04-19 09:54:27 UTC,This issue was fixed in the openstack/tempest 16.0.0 release.
1661016,2017-04-14 09:24:16 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1661016,2017-03-15 11:16:07 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1661016,2017-03-22 10:13:19 UTC,This issue was fixed in the openstack/nova 14.0.5 release.
1661016,2017-02-09 13:44:31 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/431540"
1661016,2017-02-09 13:37:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/431530"
1661016,2017-02-09 12:28:33 UTC,"Reviewed:  https://review.openstack.org/427364
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1bf7ac804808eb0d4a68847e466f5fa7d1dcd55e
Submitter: Jenkins
Branch:    master"
1661016,2017-02-08 06:35:44 UTC,https://review.openstack.org/#/c/427364/
1661016,2017-03-15 04:34:12 UTC,"Reviewed:  https://review.openstack.org/431540
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a714ffe89f1201c2b238284be3a4817b497b161b
Submitter: Jenkins
Branch:    stable/newton"
1661016,2017-03-06 10:55:09 UTC,"Reviewed:  https://review.openstack.org/431530
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4bf211c617814d46d590bb7b11806170f5c19484
Submitter: Jenkins
Branch:    stable/ocata"
1661030,2017-03-02 08:46:11 UTC,This bug was fixed in the package linux - 4.8.0-40.43
1661030,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1661030,2017-03-28 09:22:10 UTC,Not fixed because we had to revert the commits due to various regressions.
1661030,2017-03-29 23:13:19 UTC,This bug was fixed in the package linux - 4.8.0-45.48
1661030,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1661030,2017-04-24 14:11:40 UTC,This bug was fixed in the package linux - 4.8.0-49.52
1661030,2017-02-27 18:11:36 UTC,tested and verified it is fixed on Ubuntu Yakkety with -proposed kernel 4.8.0-39-generic #42
1661030,2017-02-27 18:39:17 UTC,tested and verified it is fixed on Ubuntu Xenial with -proposed kernel 4.4.0-64 #86
1661030,2017-02-01 18:21:23 UTC,"Hi Colin,"
1661030,2017-02-27 17:16:35 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1661030,2017-02-23 15:00:33 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1661030,2017-02-02 09:51:28 UTC,"On Thu, Feb 02, 2017 at 08:13:45AM -0000, John Johansen wrote:

> These kernels are working for me
"
1661030,2017-02-02 08:13:45 UTC,These kernels are working for me
1661030,2017-02-27 17:14:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1661030,2017-02-02 00:00:21 UTC,"I enabled the apparmor kernel debugging, and this is what shows up in dmesg:"
1661030,2017-02-02 03:29:19 UTC,"Alright, so I broke complain mode for execs with
  UBUNTU: SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using stacked namespaces"
1661030,2017-02-01 18:56:08 UTC,4.9.0-12_4.9.0-12.13 + jj latest fixes that landed on the kernel-team mailing list in the last 24 hours.
1661030,2017-02-01 23:31:31 UTC,"Okay, thanks to jj for providing kernels, I've now reproduced this in zesty with his patch set applied."
1661030,2017-02-01 19:44:39 UTC,Okay. Can you attempt to run the environ test individually with VERBOSE=1 set in the environment? e.g.:
1661039,2017-02-06 15:54:29 UTC,I was able to work around this but the subsequent bug I found is critical: 1662216
1661039,2017-02-21 18:33:07 UTC,Fix committed in revision 329
1661066,2017-02-03 08:48:24 UTC,redhat buggilla bug : https://bugzilla.redhat.com/show_bug.cgi?id=1418941
1661066,2017-03-16 00:15:34 UTC,also check IP address in /etc/contrail/contrail-vrouter-agent.conf
1661066,2017-03-23 19:46:54 UTC,Also make this change in new compute node puppet file-  /usr/share/openstack-puppet/modules/contrail/manifests/vrouter/config.pp
1661070,2017-02-07 16:30:40 UTC,"we some interesting things with .pc files as pkg-config does not have a concept of only one sysroot and from the point of view of pkg-config we have at least 3; the current part's install directory, the stage directory and the root file system."
1661070,2017-02-08 20:06:00 UTC,"Example attached. The ""gazebo.pc"" file it's looking for is at $SNAP/usr/lib/x86_64-linux-gnu/pkgconfig/gazebo.pc"
1661073,2017-04-09 15:13:04 UTC,This bug also affected me when trying to use the software center. When trying to install software using apt-get the following message was given:
1661089,2017-02-01 20:38:13 UTC,Note this bug only looks to be in newton
1661089,2017-02-01 21:16:57 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/427929"
1661089,2017-02-16 16:49:16 UTC,"Change abandoned by Tim Rozet (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/427929
Reason: Since we cannot commit a fix directly to a stable branch and v2 is not going to be supported in future releases, there is no resolution to this other than abandoning I think."
1661093,2017-02-16 04:30:54 UTC,"@Pat, Its seems you got to the root of issue.
""short version is that disabling a certain Mesa plugin lets it run without issue (once apparmor is disabled):
MESA_EXTENSION_OVERRIDE=""-GL_EXT_bgra"" webbrowser-app"""
1661093,2017-02-15 20:53:15 UTC,"Glad to know that Oxide is good on the desktop, as I have a cordova-based project riding on it."
1661093,2017-02-15 16:15:39 UTC,"Sorry Pat,"
1661093,2017-02-07 16:21:53 UTC,"You're correct, there are other errors prior to the lttng-ust-wait-7 stuff."
1661093,2017-02-06 22:36:23 UTC,"Hi,"
1661093,2017-02-07 09:28:29 UTC,"The /dev/shm/lttng-ust-wait-7 denial is most likely a red herring (tracked by bug #1606946, but it shouldn’t prevent the app from running). Are there any other denials?"
1661093,2017-02-03 18:15:18 UTC,"Well, if you need any info or tests run to figure out the Apparmor issue, let me know.  As for the rest, I'm looking into the QT side of things which will hopefully resolve everything all the way up to my application."
1661093,2017-02-02 14:22:02 UTC,"Yes, the webview works fine on Ubuntu desktops. Can you run webbrowser-app?"
1661093,2017-02-02 17:46:12 UTC,"Hm, that certainly didn't go very well..."
1661093,2017-02-02 21:07:26 UTC,This crash doesn't involve Oxide at all. Does it run if you disable the confinement for it? You can do this by running:
1661093,2017-02-06 21:10:42 UTC,"When running webbrowser-app under apparmor confinement, you can check for denial messages in either /var/log/syslog or /var/log/audit/audit.log."
1661093,2017-02-03 17:45:11 UTC,"That got the app running, and the web page loads but there are glitches on the display of the controls."
1661093,2017-02-03 17:57:18 UTC,"The good thing is that Oxide seems to work here, but the driver requires a resource that's blocked by Apparmor. I'm not sure about the UI glitches though, or your original problem with cordova. I'm afraid I'm not at all familiar with that."
1661093,2017-02-02 21:08:10 UTC,And this is on 16.04?
1661127,2017-02-02 06:37:19 UTC,It would be definitely of benefit to count the controller model. I believe its omission was not intentional.
1661131,2017-03-10 19:05:09 UTC,"Got it working 2nd try, enabling -proposed in Xenial resolved the issue."
1661131,2017-03-08 21:04:14 UTC,"May have spoken too soon, found server went into a kernel panic after I got back from lunch. There's some complaints about the controller so I am going to try the 4.4.47 kernel again to be sure it's not the hardware."
1661131,2017-03-08 19:15:59 UTC,"Sorry for the delay, had to wait for another issue to be debugged before I could take over the hardware again. I enabled -proposed and performed an apt-get update and fix is working."
1661131,2017-02-24 20:36:58 UTC,The proposed Xenial kernel now has the 4.4.47 updates and is in the -proposed repository.
1661131,2017-02-23 03:06:08 UTC,"v4.4.47 kernel has the fix and is working with the NVMe drive in the ""bad"" slot."
1661131,2017-02-21 23:40:43 UTC,"I was able to git clone the v4.4.47 kernel over to the machine having issues. When trying to apply the patches after 0001, it's unable to locate the file to patch for some. I am seeing this same error on another machine I've previously successfully upgraded to the 4.4.47 kernel with the same files."
1661131,2017-02-07 19:18:53 UTC,"Can you also test the latest upstream 4.4 kernel?  That will tell us if the fix in mainline was already cc'd to stable or if we need to perform a ""Reverse"" bisect."
1661131,2017-02-07 00:33:13 UTC,The mainline kernel seems to have resolved the issue so far. We're running some IO just to make sure it's stable. I will update the tag once we have confirmation.
1661131,2017-02-02 19:59:59 UTC,"I've asked the engineer to try the latest v4.10-rc6 kernel. This is their first test with 16.04.1, so unknown if it works with previous kernel version. I've asked them to check older versions to see if it exists."
1661131,2017-02-02 17:21:29 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1661131,2017-02-02 02:00:38 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1661131,2017-02-18 00:10:40 UTC,"Hi Joseph,"
1661131,2017-02-08 08:28:12 UTC,We tried with the 4.4.47 kernel but when booting it gives up waiting on the root device. We are troubleshooting to try and get it to boot.
1661141,2017-02-02 07:47:16 UTC,Another hit here: https://review.openstack.org/#/c/323398/7
1661141,2020-06-01 11:28:02 UTC,"The mentioned test has 100% success rate over the last 3 months (6236 runs). Whatever was making the test failed, based on the statistics data it seems, the issue here got resolved."
1661145,2017-02-02 07:13:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661145,2017-02-02 07:13:32 UTC,"I would like that also, a bit more options to show specific information of juju status.
Stuff like.
- Show which header(s), Apps, Units, Relations, just one or two like `--headers units,apps` and then in that same order as given.
- Show which columns in the units part, like not showing the ports column for instance."
1661150,2019-06-27 07:36:05 UTC,There are no plans to detect that the client clock is not set correctly and notify the user.
1661150,2017-02-06 06:13:12 UTC,"This error message comes directly from AWS not Juju - Juju could add extra bespoke logic to detect that the time on the client machine is wrong, but that sort of fix is not in scope for the 2.1 release."
1661161,2017-02-02 23:55:04 UTC,*** This is an automated message ***
1661162,2017-02-02 08:11:45 UTC,Removed 'scale' tag because the issue is reproducible and doesn't depend on nodes amount.
1661162,2017-02-06 09:29:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/429592"
1661162,2017-02-06 09:29:47 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/429594"
1661162,2017-02-06 09:30:11 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/429595"
1661162,2017-02-06 12:33:19 UTC,"Reviewed:  https://review.openstack.org/429592
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=9bf605f613559f90206ff68c5229f219614d63f3
Submitter: Jenkins
Branch:    master"
1661162,2017-02-06 12:34:40 UTC,"Reviewed:  https://review.openstack.org/429594
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=f89635b2b910e0c81965403a5a50cf6713252944
Submitter: Jenkins
Branch:    stable/newton"
1661162,2017-02-27 16:27:27 UTC,This issue was fixed in the openstack/fuel-ui 11.0.0.0rc1 release candidate.
1661162,2017-06-26 10:36:32 UTC,"Reviewed:  https://review.openstack.org/429595
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=bcd63f4abdb5b60a857398dbf4333cb8cd55098e
Submitter: Jenkins
Branch:    stable/mitaka"
1661162,2017-06-29 15:44:07 UTC,Verified on 9.2+mu2
1661168,2017-02-03 23:40:19 UTC,This bug was fixed in the package kexec-tools - 1:2.0.14-1ubuntu2
1661168,2017-02-02 18:44:51 UTC,"Louis,"
1661170,2017-02-02 08:00:18 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1661170,2017-02-02 07:33:39 UTC,"For the note, this bug was converted from a question on launchpad."
1661170,2017-02-03 03:26:55 UTC,apport information
1661170,2017-02-03 03:26:52 UTC,apport information
1661170,2017-02-03 03:26:47 UTC,apport information
1661170,2017-02-03 03:26:41 UTC,apport information
1661170,2017-02-03 03:26:39 UTC,apport information
1661170,2017-02-03 03:26:37 UTC,apport information
1661170,2017-02-03 03:26:44 UTC,apport information
1661170,2017-02-03 03:26:33 UTC,apport information
1661170,2017-02-03 03:26:31 UTC,apport information
1661170,2017-02-03 03:26:27 UTC,apport information
1661170,2017-02-03 03:26:24 UTC,apport information
1661170,2017-02-03 03:26:22 UTC,apport information
1661170,2017-02-03 03:26:21 UTC,apport information
1661170,2017-02-03 03:26:19 UTC,"AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-59-generic.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Card1.Amixer.info: Error: [Errno 2] No such file or directory
Card1.Amixer.values: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Hewlett-Packard HP Z640 Workstation
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=abd14d06-7dd1-4652-ab73-598ed50ac0ee ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-59-generic N/A
 linux-backports-modules-4.4.0-59-generic  N/A
 linux-firmware                            1.157.6
RfKill: Error: [Errno 2] No such file or directory
Tags:  xenial xenial
Uname: Linux 4.4.0-59-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:"
1661170,2017-02-03 03:26:35 UTC,apport information
1661176,2020-01-23 06:02:15 UTC,Can you still reproduce your issue with the latest version of QEMU (currently v4.2.0)? Please also always add the way how you launched QEMU (ie. the command line parameters)
1661176,2020-03-24 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1661177,2017-03-07 12:40:39 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442436"
1661177,2019-12-18 16:50:39 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/429786
Reason: This repo is retired now, no further work will get merged."
1661177,2017-04-04 12:10:35 UTC,"Still reproduces - https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.plugins.install_plugin_after_cluster_create/209/testReport/
ISO 1561"
1661177,2017-03-07 16:13:29 UTC,"Reviewed:  https://review.openstack.org/442436
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=fede1d12b2bc1c3ef59502f47b2335dd465fc079
Submitter: Jenkins
Branch:    stable/ocata"
1661177,2017-03-01 16:56:49 UTC,Revert should help. Closing the bug as Fix Committed.
1661177,2017-03-15 10:22:56 UTC,The given fix removes the tasks that not present in the stable/mitaka. So it's invalid for this branch.
1661177,2017-03-01 12:58:45 UTC,"Reviewed:  https://review.openstack.org/436514
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=6ceca619338508479df2a67f33af20353bcb0a4a
Submitter: Jenkins
Branch:    master"
1661177,2017-02-28 10:58:59 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/438911"
1661177,2017-02-02 13:13:26 UTC,https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.numa_cpu_pinning/157/testReport/(root)/change_pinned_cpu_and_redeploy/change_pinned_cpu_and_redeploy/
1661177,2017-02-21 15:56:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436514"
1661177,2017-02-06 16:58:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/429786"
1661177,2017-02-02 14:41:08 UTC,I have checked
1661177,2017-03-01 15:54:38 UTC,"Reviewed:  https://review.openstack.org/438911
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=a87e9264904fbb6111cd137e820cfb935055ec7f
Submitter: Jenkins
Branch:    stable/newton"
1661183,2017-02-02 09:11:22 UTC,A xenial version of this charm would be appreciate ;)
1661184,2017-02-02 09:42:49 UTC,openstack logstash shows 12 hits over the past week
1661184,2017-02-02 09:49:01 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22_int_malloc%3A%20Assertion%5C%22
1661184,2017-04-17 13:00:53 UTC,This is a libvirt bug
1661196,2017-02-15 22:40:29 UTC,"Yeah the bits are known, i just don't remember and would need to dig it up again. Sorry my memory is really hazy on this, need somebody like Rodney or Steve to weigh in on why it is the way it is and what are the consequences of changing it."
1661196,2017-02-06 12:29:37 UTC,"Thanks Robert for the explanations,
I'm totally good on the burned version part of this."
1661196,2021-01-19 18:04:48 UTC,"I think testing against release is intentional and better than testing against proposed, since the same tests would be run for archive uploads, too."
1661196,2017-02-03 05:45:16 UTC,"Burned version number? How did you copy the package? Did you download the source and then reupload the source package? Don't do that. Use copy-package to bincopy the package from the release to the PPA. ""burned version number"" means ""I inspected this package and the package in the destination archive and determined that they have the same version number but the source contents don't match"""
1661196,2017-02-02 11:02:53 UTC,"It won't let me make Diffs/Tests due to the burnt version number (I understand), so +1 without really wanting it :-)"
1661196,2017-02-02 10:56:35 UTC,"I even found that when trying to mitigate the issue by uploading the source of the ""only in proposed"" lib that is missing in the test into the bileto ppa I get warnings like:
""Needs rebuild due to burned version number (zesty/xen). Pending binary packages"""
1661196,2017-02-03 05:46:11 UTC,"If you bincopy the package from proposed, you'll know it worked when the status on the ticket will be 'proposed pocket'"
1661198,2017-02-02 10:38:37 UTC,in the nginx/error_services.log
1661198,2017-02-02 10:55:56 UTC,It seems what http://10.21.0.2:8777/v1/tests/2 request take time more when timeout in UI
1661198,2017-02-02 10:58:56 UTC,"[root@fuel nginx]# time curl -H 'X-Auttime h-Token: 2783b8831def42dea8a88767ea0c85c4'  http://10.21.0.2:8777/v1/tests/2
real	1m13.034s
user	0m0.005s
sys	0m0.007s"
1661198,2017-02-02 11:31:32 UTC,tcpdump for ostf server
1661199,2018-08-24 13:51:09 UTC,Reopening against acng for further consideration and possible discussion.
1661199,2018-08-22 10:52:28 UTC,"Marking this as Won't Fix now, as it's outside the scope for apt to display error messages from remote servers"
1661199,2017-02-04 20:59:04 UTC,Added a task against apt as requested.
1661199,2017-02-04 21:08:35 UTC,"It would be nice to have some more details, but I think it's a bit unrealistic to display a web page in apt's error handling system."
1661199,2017-02-03 07:22:08 UTC,Please reopen this as a bug against APT. There is a detailed HTTP status message and not a mere 403 code. The application should display it.
1661199,2017-02-02 14:22:29 UTC,"@wiredfool, this is the expected behavior and I ran into it as well. Since apt-cacher-ng cannot cache the HTTPS connection so it's refusing to proxy it. A possible workaround is to let it pass through apt-cacher-ng using a regex like that in the config file:"
1661199,2017-02-04 21:15:18 UTC,"Think about that: Your proxy returns 403 and you have 20 repositories, and now get 20 messages, each 100 lines long because your proxy decided to go fancy."
1661200,2017-04-05 15:32:55 UTC,"Verified for 10.1. Puppet4 syntax gate job is working now.
http://logs.openstack.org/11/453111/2/check/gate-fuel-library-puppet-syntax-4-centos-7/6ee84ee/console.html"
1661200,2017-02-27 16:28:52 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1661200,2017-02-06 16:34:04 UTC,"Reviewed:  https://review.openstack.org/428229
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=21e6b1945d50ae06865d9cfa53d9e5fdf6c30bc2
Submitter: Jenkins
Branch:    stable/newton"
1661200,2017-02-02 16:02:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/428229"
1661200,2017-02-02 16:03:17 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/428231"
1661200,2017-02-06 11:43:52 UTC,"Reviewed:  https://review.openstack.org/428231
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=af4d0aa90f0581a32449dc354917fd8d0448780a
Submitter: Jenkins
Branch:    stable/mitaka"
1661200,2017-02-02 10:36:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/428078"
1661200,2017-02-02 15:59:44 UTC,"Reviewed:  https://review.openstack.org/428078
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=49ee82dc151386f5d154e37d1c2f180b10dec7e8
Submitter: Jenkins
Branch:    master"
1661207,2017-02-03 05:39:13 UTC,"Yeah that would be nice for sure, unfortunately what you're describing isn't in bileto at all, it's a generic swift container. I don't have any control over it at all. So there'll be no ""just throw an xslt in there"", it would require developing a whole new endpoint that manually scans the swift container and then provides all links."
1661209,2017-02-22 16:20:15 UTC,It's worth noting that ProcEnviron and UserGroups are both empty.
1661210,2017-02-02 11:13:40 UTC,"Volume listing OSTF test failure:
(fuel_health.tests.sanity.test_sanity_compute.SanityComputeTest.test_list_volumes) Time limit exceeded while waiting for volume listing to finish. Please refer to OpenStack logs for more details.   File ""/usr/lib/python2.7/site-packages/unittest2/case.py"", line 67, in testPartExecutor
    yield
  File ""/usr/lib/python2.7/site-packages/unittest2/case.py"", line 601, in run
    testMethod()
  File ""/usr/lib/python2.7/site-packages/fuel_health/tests/sanity/test_sanity_compute.py"", line 58, in test_list_volumes
    self.volume_client)
  File ""/usr/lib/python2.7/site-packages/fuel_health/common/test_mixins.py"", line 180, in verify
    "" Please refer to OpenStack logs for more details."")
  File ""/usr/lib/python2.7/site-packages/unittest2/case.py"", line 666, in fail
    raise self.failureException(msg)
Step 1 failed: Time limit exceeded while waiting for volume listing to finish. Please refer to OpenStack logs for more details.
-------------------- >> begin captured logging << --------------------
fuel_health.common.test_mixins: INFO: STEP:1, verify action: 'volume listing'
fuel_health.common.test_mixins: INFO: Timeout 20s exceeded for volume listing
fuel_health.common.test_mixins: ERROR: Time limit exceeded while waiting for volume listing to finish.
Traceback (most recent call last):
  File ""/usr/lib/python2.7/site-packages/fuel_health/common/test_mixins.py"", line 174, in verify
    result = func(*args, **kwargs)
  File ""/usr/lib/python2.7/site-packages/fuel_health/common/test_mixins.py"", line 220, in __exit__
    raise AssertionError(msg)
AssertionError: Time limit exceeded while waiting for volume listing to finish.
--------------------- >> end captured logging << ---------------------"
1661210,2017-02-02 11:22:28 UTC,Errors on nova-conductor log looks similar: http://paste.openstack.org/show/597335/
1661210,2017-02-02 11:36:53 UTC,Also mysqld.log looks full of err output: http://paste.openstack.org/show/597336/
1661211,2017-02-02 22:52:49 UTC,"The output of ""gnome-terminal --help"" is probably a bit poorly worded."
1661211,2017-02-02 22:56:03 UTC,"(sorry, accidentally hit ""Post"")"
1661211,2017-02-02 23:33:26 UTC,"It still seems to me than a set of features poorly designed. You can see that by playing around with the two option: ""--window"" e ""--tab"""
1661211,2017-02-03 10:16:30 UTC,I agree that these options are far from ideal.
1661211,2017-02-03 13:38:16 UTC,I met this need working with ROS and its launch files.
1661211,2017-02-03 13:39:39 UTC,"ERRATA: in the workflow maybe some options like -x or --command should be added, sorry, but it doesn't change the use of --tab and --window."
1661218,2017-11-01 07:46:57 UTC,Hello.
1661218,2017-09-27 03:40:10 UTC,Another article on the difference between setup.py and requirements.txt: https://caremad.io/posts/2013/07/setup-vs-requirement/
1661218,2017-04-07 04:17:22 UTC,[Expired for pyLibravatar because there has been no activity for 60 days.]
1661218,2017-02-05 10:24:45 UTC,"Unfortunately I cannot really judge this, so all I can do is report my findings.
And these are 'pip[N] install pylibravatar' does not pull py[3]dns running the pip implementations belonging to Python 3 or 2 on either Arch Linux or Debian stretch. And so far I haven't seen any such problem with any other PyPI package on those platform which is suggesting the problem is in pyLibravatar, IMHO."
1661218,2017-09-12 15:09:41 UTC,A requirements.txt file is probably what's missing here:
1661218,2017-02-05 08:10:49 UTC,The dependency is in there: https://git.launchpad.net/pylibravatar/tree/setup.py#n4
1661237,2017-02-03 10:07:00 UTC,"Illia, can you check this?"
1661237,2017-02-06 07:54:47 UTC,Bug doesn't related with contrail plugin. Bug occurs after execution playbook with restarting all nodes in environments (step 13 in https://docs.mirantis.com/openstack/fuel/fuel-master/release-notes/update-product/update-env-9-2.html)
1661237,2017-02-06 07:57:08 UTC,"@ibumarskov
button appears after Upgrade the Ubuntu kernel to version 4.4 step (step 10)"
1661237,2017-02-06 14:25:28 UTC,"Related fix proposed to branch: master
Change author: Mariia Zlatkova <email address hidden>
Review: https://review.fuel-infra.org/30525"
1661237,2017-02-06 17:52:58 UTC,"Reviewed: https://review.fuel-infra.org/30525
Submitter: Olena Logvinova <email address hidden>
Branch: master"
1661237,2017-02-06 17:53:51 UTC,"Related fix proposed to branch: stable/9.2
Change author: Mariia Zlatkova <email address hidden>
Review: https://review.fuel-infra.org/30539"
1661237,2017-02-06 17:56:39 UTC,"Reviewed: https://review.fuel-infra.org/30539
Submitter: Mariia Zlatkova <email address hidden>
Branch: stable/9.2"
1661253,2017-02-06 10:58:31 UTC,"Hi dharmendra, this feature may need some significant changes in Tacker. It looks like a new feature. I opened a blueprint which targets for Pike.
https://blueprints.launchpad.net/tacker/+spec/ns-lifecycle-mgmt"
1661253,2017-02-07 23:54:46 UTC,"@Tung - thanks for the initiative. The title ""Life-cycle management for E2E Services"" is too broad. I'd recommend to you to give a specific title that automatically scopes / limits the effort, like ..."
1661254,2019-09-19 13:10:05 UTC,"@adam-collard, this is a feature request, not an issue that is should expire after 6 months. If you do not want to implement this feature than that is fine, but please say so."
1661254,2019-09-23 13:58:36 UTC,"Being a feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1661254,2019-09-24 09:50:49 UTC,https://discourse.maas.io/t/auto-assignment-of-network-interface-tag-based-on-lshw-lldp/1017
1661254,2019-09-19 12:02:17 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1661260,2017-09-14 08:37:46 UTC,"Reviewed:  https://review.openstack.org/482084
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=463b97563e2e5e28b1500eb3c80ec4d0477dfea7
Submitter: Jenkins
Branch:    stable/mitaka"
1661260,2017-07-10 10:07:07 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/482084"
1661260,2017-06-30 12:51:03 UTC,"Reviewed: https://review.fuel-infra.org/35728
Submitter: Olena Logvinova <email address hidden>
Branch: stable/9.2"
1661260,2017-06-26 10:55:16 UTC,QA team: please test mos-updates package with https://review.fuel-infra.org/#/c/35728/ mos-docs fix
1661260,2017-06-27 10:07:31 UTC,Done. New procedure works.
1661260,2017-06-21 18:19:07 UTC,"Fix proposed to branch: stable/9.2
Change author: Alexey Stupnikov <email address hidden>
Review: https://review.fuel-infra.org/35728"
1661260,2017-06-21 18:13:32 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Alexey Stupnikov <email address hidden>
Review: https://review.fuel-infra.org/35727"
1661260,2017-06-21 10:27:44 UTC,"New update procedure doesn't work because new ubuntu repositories will not added before step ""Update the environment: fuel2 update --env <ENV_ID> install --repos mos9.2-updates"""
1661260,2017-06-14 17:35:10 UTC,"QA team: this fix doesn't contain code to be released, so please test the instruction on Fuel9.1 deployment with ceph and remove 9.2-mu2 nomination if everything will work as it should."
1661260,2017-06-14 17:32:57 UTC,"Reviewed: https://review.fuel-infra.org/35628
Submitter: Olena Logvinova <email address hidden>
Branch: stable/9.2"
1661260,2017-06-14 16:42:01 UTC,"Fix proposed to branch: stable/9.2
Change author: Alexey Stupnikov <email address hidden>
Review: https://review.fuel-infra.org/35628"
1661260,2017-06-26 10:25:17 UTC,"Reviewed: https://review.fuel-infra.org/35727
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1661289,2017-02-02 16:27:59 UTC,"The attachment ""0001-Fix-infinite-loop-parsing-line-options-on-arm64.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1661289,2017-02-03 08:38:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661295,2018-02-14 14:54:13 UTC,"Problem is that the ""real"" KMS platform is unable to determine the current mode when running on VMware, leaving the current_mode_index at an invalid value of UINTMAX, which is being passed through to the nested platform."
1661295,2018-03-24 09:32:46 UTC,This bug was fixed in the package mir - 0.31.0.1-0ubuntu1
1661295,2018-02-15 11:39:46 UTC,"Ok, VMWare is setting the current crtc mode at a generic 800x600, which isn't in the list of modes for the connected display. Only approach I see is to compare the mode name with ""preferred"", for which I see prior art:
https://github.com/wayland-project/weston/blob/master/compositor/main.c#L1068"
1661295,2017-11-03 15:24:07 UTC,Syncing task from Mir.
1661295,2017-02-03 13:30:02 UTC,This is inside generated code .. looping from zero to size() .. failing in a index < 0 assertion..
1661295,2017-02-02 16:01:21 UTC,http://pastebin.ubuntu.com/23911675/ my packages
1661295,2017-02-07 05:13:24 UTC,Are we not able to support vmware through jenkins as a platform?
1661295,2017-02-02 16:52:44 UTC,Likely a dupe of https://bugs.launchpad.net/mir/+bug/1661163 ?
1661295,2017-02-02 19:44:38 UTC,bug #1661163 is about an incomplete MirDisplayConfig without any cards..
1661295,2017-02-03 01:33:17 UTC,"The display config API got some major work done in Mir 0.26. This and the other bug look like fairly simple array bounds errors. And yes, negative mode indices are expected; it's clearly documented in the client headers. We just need to handle it better..."
1661297,2017-02-21 11:15:12 UTC,Upstream bug: https://github.com/rhinstaller/pyparted/issues/34
1661297,2017-07-14 11:47:42 UTC,"Upstream has prepared a fix for this, it should be part of the next pyparted release."
1661310,2019-07-08 04:17:28 UTC,[Expired for xca (Ubuntu) because there has been no activity for 60 days.]
1661310,2019-05-08 19:08:31 UTC,"Yakkety is no longer supported.  Please test in a current supported release and see if this issue still happens (please also test with the latest available release if possible).  If the issue still exists, please make a comment as such; otherwise this bug will be closed in 60 days as I am marking it ""Incomplete"""
1661322,2017-02-24 09:12:00 UTC,"fix under review:
https://review.openstack.org/#/c/437839/
https://review.openstack.org/#/c/437842/"
1661322,2018-02-07 08:19:33 UTC,"Change abandoned by Joachim Barheine (<email address hidden>) on branch: master
Review: https://review.openstack.org/437842"
1661322,2018-02-07 08:19:51 UTC,"Change abandoned by Joachim Barheine (<email address hidden>) on branch: master
Review: https://review.openstack.org/437839"
1661328,2017-12-20 19:36:05 UTC,"It appears that this is no longer being worked, resetting bug status and abandoning the change that has been sitting outstanding without reply for nearly a year. :("
1661328,2017-10-06 14:45:50 UTC,"Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/444525
Reason: Abandoning per comment above (and because stable/newton goes EOL soon)"
1661328,2017-08-01 13:56:03 UTC,"There seems to be a check in ironic that does the validation that the memory is larger than the image_size + reserved space. For our ironic installation, we used the patch [2] and additionally, we needed a patch to disable the image size check."
1661328,2017-03-12 17:44:02 UTC,Can we get a spec up for this? Thanks!
1661328,2017-08-01 08:33:25 UTC,"Can we enhauce node-validate function in ironic, check if the ram in node is larger than the user-image size"
1661328,2017-02-08 16:13:01 UTC,"Change abandoned by Félix Bouliane (<email address hidden>) on branch: master
Review: https://review.openstack.org/428410
Reason: this will be addressed in change Ibf742198e83ae13f90767b28cc1858f0a17c3a95"
1661328,2017-02-02 21:10:06 UTC,Jay: Yes we indeed have a workaround we are trying to implement. The first step is figuring out there is not enough space for the file.
1661328,2017-02-02 20:46:38 UTC,"This is more of a known limitation than a bug, however, you can use raw images which are streamed to disk."
1661328,2017-02-02 20:34:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/428410"
1661328,2017-02-08 16:31:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430442"
1661328,2017-03-10 22:40:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/444525"
1661329,2017-09-26 23:56:14 UTC,Maybe this bug is a duplicate of LP bug #1650835 (wifi association times out while typing password)?
1661329,2017-09-27 17:08:39 UTC,Maybe ;)… it seems that they also report in bug #1650835 a problem of timing but did not make mistakes typing the password the first time. Maybe not a duplicate… but obviously it seems that the problems might be linked
1661333,2017-02-02 21:11:57 UTC,This is just a duplicate of long-standing (public hardening opportunity) bug 1188189 and corresponding OSSN-0033 ( https://wiki.openstack.org/wiki/OSSN/OSSN-0033 ) right? I'm pretty sure the OpenStack VMT wouldn't issue an advisory in this case nor is there much point in keeping the issue private and embargoed.
1661333,2017-02-03 09:12:19 UTC,"bug 1188189 talks about certificate validation problems with code using HTTPSConnection objects in Python 2.x..This defect talks about a certificate validation skipped specifically in the cinder brocade driver (which uses requests library) . So, this bug would obviously not be a duplicate of the former bug."
1661333,2017-02-03 09:39:24 UTC,I think fungi is specifically referring to comment #10 of bug 1188189 which seems to match this bug report: This certificate validation is skipped for a for serverside node-to-node communication that could be assumed to happen on private networks.
1661333,2017-02-07 16:31:12 UTC,The following related reports were also submitted publicly today as security hardening opportunities:
1661342,2017-02-06 16:21:36 UTC,"Reviewed:  https://review.openstack.org/428305
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=ee2ede88d461fddf0b1a3cba21cfa40997b5c254
Submitter: Jenkins
Branch:    master"
1661342,2017-02-02 18:03:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/428305"
1661345,2017-02-03 02:24:14 UTC,"I can confirm this issue on a Compaq Presario V3000 laptop (AMD Turion X2, Nvidia Geforce GO 6150 Graphics). Clean install of Linux Mint MATE 18.1 32bit. I notice this issue after suspend, but for me all that needs to happen is that the screen turns off and the mouse will disappear. Only way to get it back as far as I'm aware is to reboot, but will fiddle around a little more."
1661345,2017-02-06 07:09:41 UTC,"UPDATE. I believe I have resolved this issue by changing the Window Manager from Marco + Compositing to Marco + Compton. The moment I changed this setting, my mouse re-appeared, and did not disappear again after a reboot and suspending my computer. I'll test it for a few more days, but if I don't post back, it's probably fine."
1661363,2017-02-03 20:34:47 UTC,"ARM64 builds needs build dependency on libz-dev inorder to support compressed kernels. The attached patch adds that support. Note. amd64 and i386 do not have this dependency, I tested the current zesty version of the kexec-tools on amd64 and i386 and it works. The patch only apply to ARM64 build."
1661363,2017-02-03 23:40:19 UTC,This bug was fixed in the package kexec-tools - 1:2.0.14-1ubuntu2
1661363,2017-03-02 17:47:49 UTC,"Hello dann, or anyone else affected,"
1661363,2017-03-02 17:51:51 UTC,"Hello dann, or anyone else affected,"
1661363,2017-05-12 19:50:18 UTC,Ubuntu 16.04.2 LTS kosberg ttyAMA0
1661363,2017-05-12 19:51:11 UTC,"sudo file /boot/vmlinuz-4.10.0-20-generic
/boot/vmlinuz-4.10.0-20-generic: gzip compressed data, max compression, from Unix"
1661363,2017-06-09 16:20:55 UTC,I don't see any mention of 16.10 being tested - switching to 'only xenial tested'.
1661363,2017-06-09 20:39:51 UTC,Testing on Yakkety (16.10)
1661363,2018-06-11 12:23:07 UTC,This bug was fixed in the package kexec-tools - 1:2.0.16-1ubuntu1~16.04.1
1661363,2017-02-02 22:32:25 UTC,"The debian/control file lists gnu-efi and libz-dev only for ia64, since amd64, and arm64 (may be other archs) also need these dependencies for it to support compressed kernel we need something like the following change for it to work on those archs."
1661363,2017-02-02 22:56:42 UTC,"As mentioned on IRC, we shouldn't include amd64 in this unless we know that it actually improves amd64 support. My guess is that this doesn't help x86 - IIRC, those images decompress themselves at runtime."
1661375,2018-09-26 06:13:36 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/436
1661375,2017-10-28 11:49:03 UTC,"News from this issue, see also https://github.com/anholt/mesa/issues/62."
1661375,2017-10-23 17:17:10 UTC,RaspberryPi issues will be followed again as soon as Raspbian includes Mesa17. As of September 2017 it still includes Mesa13 which has an ugly bug.
1661375,2017-09-24 07:57:34 UTC,Any news for this report?
1661375,2017-02-03 14:27:34 UTC,Thank you Eric to go into these depths. I had tried to build apitrace for sending the trace for the whiteout issue but was stuck with a build error.
1661375,2017-02-05 16:31:25 UTC,"Note that we had a change of the internal widget structure recently to replace the deprecated QGLWidget with the newer QOpenGLWidget (which also uses an explicit FBO for rendering). This is not in 0.15, and quite possibly affects this."
1661375,2017-02-05 13:09:28 UTC,"Eric, are you have Scenery3D plugin enabled?"
1661375,2017-02-03 20:18:11 UTC,"I am not sure at the moment, we are doing most drawing ourselves, but maybe Qt does the first glClear() hidden in some function?"
1661375,2017-02-03 17:18:32 UTC,There's no hint telling you what kind of renderer you have.  But not doing that redundant clear in the first case would help all GPUs.
1661375,2017-02-05 19:55:38 UTC,Thank you Florian!
1661375,2017-02-03 08:59:26 UTC,Thank you very much for report and for suggest for an apitrace utilite!
1661378,2017-02-08 09:04:39 UTC,"It waits an hour, how long are you suggesting it waits for?"
1661378,2017-02-08 23:13:24 UTC,"We modified the sequence of events in https://bugs.launchpad.net/landscape/+bug/1654399, maybe we should have bumped up this retry time too."
1661384,2017-02-04 22:12:20 UTC,"after ""sudo systemctl stop thermald"""
1661384,2017-02-02 21:13:45 UTC,Can you do the following and run your loads:
1661384,2017-02-04 23:13:03 UTC,"Jérôme,"
1661384,2017-04-21 22:13:04 UTC,"Please try 1.6 version. If still have problem then
# sudo systemctl stop thermald
# sudo thermald --no-daemon --loglevel=debug
and send logs."
1661384,2017-02-05 00:21:37 UTC,"Ok thermald doesn't work properly for me. However, it is running when my powercord is plugged. Moreover thermald has to be launched at system startup (and thus increases the startup time)."
1661386,2017-02-03 12:57:16 UTC,"Hi Matwey,
  That shouldn't happen!  The patch you've bisected to is just the one that complains if the ioctl fails rather than silently ignoring the failure - it means the failure probably previously existed and was ignored and that causes random other problems."
1661386,2020-02-11 15:43:25 UTC,"Hi,"
1661386,2020-02-11 14:42:47 UTC,"There was a fix for this assertion message wrt PMU registers in December 2017 already:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=0b368a10c71af96f6cf
Thus, can you still reproduce this issue with the latest version of QEMU, or is the problem gone now?"
1661386,2017-07-23 10:24:36 UTC,"2017-07-23 12:54 GMT+03:00 Matwey V. Kornilov <email address hidden>:

> 2017-02-08 11:49 GMT+03:00 Paolo Bonzini <email address hidden>:
>>> Does qemu follow recommendations from section 4.3?
>>
>> All that QEMU does is initialize MSR values and QEMU is talking to KVM,
>> not to the processor; KVM in turn talks to the host kernel's perf
>> subsystem.
>>
>> It's the host kernel's perf subsystem that needs to follow Intel's
>> recommendation.  In particular, QEMU is setting CPUID to the values
>> retrieved by
>>
>>     perf_get_x86_pmu_capability(&cap);
>
> I can not find this function mentioned in qemu master sources.
>
"
1661386,2017-07-23 09:54:29 UTC,"2017-02-08 11:49 GMT+03:00 Paolo Bonzini <email address hidden>:

>> Does qemu follow recommendations from section 4.3?
>
> All that QEMU does is initialize MSR values and QEMU is talking to KVM,
> not to the processor; KVM in turn talks to the host kernel's perf
> subsystem.
>
> It's the host kernel's perf subsystem that needs to follow Intel's
> recommendation.  In particular, QEMU is setting CPUID to the values
> retrieved by
>
>     perf_get_x86_pmu_capability(&cap);
"
1661386,2017-04-07 13:26:08 UTC,"Hi,"
1661386,2017-02-08 08:49:52 UTC,"> Does qemu follow recommendations from section 4.3?
"
1661386,2017-02-06 19:38:56 UTC,"2017-02-06 21:05 GMT+03:00 Dr. David Alan Gilbert <email address hidden>:
>>> So you didn't mention this was running inside VMWare; it looks to me as if that's rejecting the PMU MSR accesses.
>>> For reference which version of VMWare are you using?

>
>>ESXi 6.0.0 Build 2494585
>
>>I also find that enabling perf counters in VMWare configuration also
> helps.
>
> OK, so that suggests the problem is that with PMU disabled in VMWare
> config, it's not giving the right info to the guest to know it's
> disabled.
"
1661386,2017-02-06 18:05:23 UTC,">> So you didn't mention this was running inside VMWare; it looks to me as if that's rejecting the PMU MSR accesses.
>> For reference which version of VMWare are you using?
"
1661386,2017-02-07 15:50:04 UTC,"2017-02-06 22:38 GMT+03:00 Matwey V. Kornilov <email address hidden>:

> 2017-02-06 21:05 GMT+03:00 Dr. David Alan Gilbert <email address hidden>:
>>>> So you didn't mention this was running inside VMWare; it looks to me as if that's rejecting the PMU MSR accesses.
>>>> For reference which version of VMWare are you using?
>>
>>>ESXi 6.0.0 Build 2494585
>>
>>>I also find that enabling perf counters in VMWare configuration also
>> helps.
>>
>> OK, so that suggests the problem is that with PMU disabled in VMWare
>> config, it's not giving the right info to the guest to know it's
>> disabled.
>
> How should it provide info? Can we check it?
>
"
1661386,2017-02-06 17:31:23 UTC,Seems like a VMware bug.
1661386,2017-02-06 17:11:26 UTC,"Ahha!
[    0.000000] DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014
[    0.000000] Hypervisor detected: VMware"
1661386,2017-02-06 16:54:59 UTC,"2017-02-06 13:02 GMT+03:00 Dr. David Alan Gilbert <email address hidden>:

> Hi Matwey,
>   1) Can you provide me with the output of the 'dmesg' command straight after boot on your host.
"
1661386,2017-02-06 10:02:45 UTC,"Hi Matwey,
  1) Can you provide me with the output of the 'dmesg' command straight after boot on your host.
  2) If you look in target/i386/kvm.c in kvm_arch_init_vcpu around line 871 is some code like:"
1661386,2017-02-05 08:58:34 UTC,"2017-02-03 22:51 GMT+03:00 Dr. David Alan Gilbert <email address hidden>:

> Ah well that is a bit better; you see now it's failing in kvm_**get**_msrs rather
> than put; so the question is which of the two changes made it survive kvm_put_msrs
>
> I'd hoped that the flags in (2) would have turned off the CPU flag and
> thus made it go in both of them.
>
> kvm_msr_entry_add: @103 index=20f value=0
> qemu-system-x86_64: /home/matwey/lab/qemu/target/i386/kvm.c:2218:
> kvm_get_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
>
> 1) Was it the steal time or the pmu change that made it flip over to the get_msrs?
"
1661386,2017-02-03 19:51:41 UTC,"Ah well that is a bit better; you see now it's failing in kvm_**get**_msrs rather
than put; so the question is which of the two changes made it survive kvm_put_msrs"
1661386,2017-02-03 18:55:16 UTC,"2017-02-03 21:34 GMT+03:00 Dr. David Alan Gilbert <email address hidden>:

> Hi,
>   OK, lets see:
>
>  kvm_put_msrs: ret=18 expected=105
>
> so I think it's one of the MSRs around 18 that it's upset at:
>
> kvm_msr_entry_add: @17 index=4b564d03 value=0
>
>   41:#define MSR_KVM_STEAL_TIME  0x4b564d03
>
> kvm_msr_entry_add: @18 index=38d value=0
>
>      #define MSR_CORE_PERF_FIXED_CTR_CTRL    0x38d
>
> So my guess is it's the steal time thing.
>
> 1) You didn't say what kernel your host was running - please tell me
>   I think that steal time thing went into the kernel ~3.0
"
1661386,2017-02-03 18:34:49 UTC,"Hi,
  OK, lets see:"
1661386,2017-02-03 16:25:15 UTC,"Hello,"
1661386,2017-02-06 17:45:52 UTC,"2017-02-06 20:11 GMT+03:00 Dr. David Alan Gilbert <email address hidden>:

> Ahha!
> [    0.000000] DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014
> [    0.000000] Hypervisor detected: VMware
>
> So you didn't mention this was running inside VMWare; it looks to me as if that's rejecting the PMU MSR accesses.
> For reference which version of VMWare are you using?
"
1661389,2017-06-28 22:23:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661392,2017-02-14 19:10:52 UTC,We are going to attempt to use cs:~thedac/keystone-0 and ping back if it helps.
1661392,2019-05-30 11:48:33 UTC,I'm marking this invalid against charm-glance-simplestreams-sync as it seems to be resolved in charm-keystone
1661392,2017-02-16 16:36:12 UTC,"Reviewed:  https://review.openstack.org/433391
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=b14c107dc347c31dd8a643a24ab6a7f98b85a7b2
Submitter: Jenkins
Branch:    master"
1661392,2017-02-14 00:09:50 UTC,I'll add one more manual workaround which is to run the following post-deploy:
1661392,2017-02-09 16:57:42 UTC,The juju status from https://ci.lscape.net/job/landscape-system-tests/5238
1661392,2017-02-09 17:30:32 UTC,This appears to be a race where keystone initially hands off its private-address before recognizing it has a VIP.
1661392,2017-02-14 00:07:40 UTC,Spent a little more time on this today. It is a difficult race to solve on the g-s-s side due to the asynchronous nature of the glance-simplestreams-sync.sh run from cron. It can easily race and run with the wrong keystone IP information. This is a long running process that will not learn about changes to the configuration until its subsequent run.
1661392,2017-02-09 16:55:26 UTC,Adding logs from https://ci.lscape.net/job/landscape-system-tests/5238
1661392,2017-02-03 16:59:12 UTC,"Caught a case of this occurring again, but I think it was too late. The glance-simplestreams-sync has already updated things since the cloud was first deployed. I'm now getting a successful juju bootstrap."
1661392,2017-02-09 16:58:33 UTC,The glance-simplestreams-config from from https://ci.lscape.net/job/landscape-system-tests/5238
1661392,2017-02-09 16:58:08 UTC,The keystone config from from https://ci.lscape.net/job/landscape-system-tests/5238
1661394,2017-02-02 21:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1661394,2017-02-06 19:36:06 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1661394,2017-02-07 14:22:36 UTC,"Upstream Kernel fixed Bug very well, I'm exited! Thanks a lot!"
1661396,2017-02-02 21:44:43 UTC,https://review.openstack.org/#/c/428435/
1661396,2017-02-02 22:57:31 UTC,why aren't we opening a bug in Nova that their migrations are overall exceedingly slow?
1661396,2017-02-03 00:39:11 UTC,"Reviewed:  https://review.openstack.org/428435
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=3f7e74ab24bb43f9ad7e24e0efd4206ac6a3dd4e
Submitter: Jenkins
Branch:    master"
1661396,2017-02-03 18:11:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/428843"
1661396,2017-02-05 20:20:59 UTC,Do you have a log file or something that shows us which of the migrations are taking the longest so someone could dig into this?
1661396,2017-02-06 01:41:42 UTC,"Reviewed:  https://review.openstack.org/428843
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=578599f2eed3611b66ed96031a8e6260716b4b79
Submitter: Jenkins
Branch:    master"
1661396,2017-02-07 21:30:03 UTC,I wonder if https://review.openstack.org/#/c/430390/ would indirectly help here in case it makes the base (and biggest) DB schema migration in nova run faster.
1661396,2017-02-16 12:55:28 UTC,This issue was fixed in the openstack/puppet-tripleo 6.2.0 release.
1661396,2017-06-27 15:55:41 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'"
1661396,2017-02-02 23:15:07 UTC,Mike: done.
1661414,2018-03-04 23:46:56 UTC,http://wiki.inkscape.org/wiki/index.php?title=Tracking_Dependencies&oldid=108381
1661414,2017-02-06 16:26:35 UTC,"Thanks, @Alex!"
1661414,2017-02-06 15:58:43 UTC,"Re Comment #1 - mostly because Inkscape *can* still be used without Potrace.  I guess it's feasible that some platforms may not have a convenient Potrace package available, so adding a hard dep would make life difficult for those users/maintainers."
1661414,2017-02-02 22:42:02 UTC,Btw. what's the reason for libpotrace not being a hard dependency? We do 'advertise' the trace bitmap feature.
1661414,2018-03-04 23:46:50 UTC,"Tried to add optional dependencies, hope they can be useful for someone."
1661430,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1661430,2017-03-14 16:12:52 UTC,HWE verified as well.
1661430,2017-03-02 08:46:11 UTC,This bug was fixed in the package linux - 4.8.0-40.43
1661430,2017-02-02 23:30:55 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1661430,2017-02-27 17:14:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1661430,2017-02-02 23:54:25 UTC,"No logs, request to include upstream commits."
1661430,2017-02-27 17:16:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1661430,2017-02-03 13:21:45 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-February/082305.html
1661436,2017-02-08 17:01:51 UTC,"Reason for this is that ""snap downlaod"" doesn't configure any specific store or authentication parameters for its access to the store at https://github.com/snapcore/snapd/blob/master/cmd/snap/cmd_download.go#L117"
1661436,2020-09-29 12:39:39 UTC,The updated URL is https://github.com/snapcore/snapd/pull/7977 but it is closed.
1661436,2019-11-26 09:44:36 UTC,This bug is still in progress. I believe it has lower priority than before due to the current focus on various ubuntu core 20 topics.
1661436,2017-02-03 10:56:23 UTC,"there were connectivity issues with the store yesterday, could that be related ? (did the other snaps download ?)"
1661436,2017-02-09 16:41:52 UTC,@Michael
1661436,2017-02-09 06:11:44 UTC,I've pushed a PR to allow the user specifying a store ID for the snap download command via a --store-id=<ID> argument. See https://github.com/snapcore/snapd/pull/2818
1661436,2019-10-29 18:40:38 UTC,"I believe there's ongoing work on allowing ""snap download"" to take advantage of snapd's cache and configuration, including the branded store."
1661436,2017-02-08 17:08:58 UTC,"there is still a workaround I think, by doing a snap install on an existing system and fetching relevant things from /var/lib/snapd manually, not nice but a workaround"
1661448,2017-02-03 00:21:06 UTC,fingerprint login timeout (no swipe attempted)
1661448,2017-02-03 00:18:50 UTC,Failed swipe then timeout
1661448,2017-02-03 00:18:21 UTC,Failed swipe followed by success
1661448,2017-02-03 00:19:35 UTC,"Two failed swipes, then timeout. The password field is now hidden, but still usable."
1661476,2018-05-08 18:02:27 UTC,This change was made by a bot.
1661481,2017-05-10 05:04:32 UTC,not that high these days
1661481,2019-12-07 03:44:44 UTC,no longer relevant as fwaas v1 was removed
1661486,2017-02-12 14:01:39 UTC,"This crash is now happening daily, ever since the latest plasma upgrade."
1661486,2017-02-24 01:02:37 UTC,"I switched from nouveau to the proprietary nvidia driver (nvidia-375), and the crashes have stopped."
1661486,2017-05-25 17:56:59 UTC,"same problem here. System freezes completely(except, I can move mouse pointer. Just move, no click) and after restart buch of ""nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]"" in syslog. ubuntu 16.04, 4.4.0-78-generic #99-Ubuntu SMP, Lenovo P50.
I cannot switch to nvidia-XXX driver as it is unusable in multiple monitors configuration."
1661486,2017-06-08 19:11:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661486,2017-08-06 15:21:42 UTC,After running the system for a week:
1661486,2018-01-12 22:10:38 UTC,Has anyone managed to solve this?
1661500,2017-02-03 10:38:54 UTC,This seems like a selinux bug in selinux-policy or docker-selinux.
1661500,2017-03-28 09:27:28 UTC,"Kolla does not currently support running containers with selinux enabled.
I will mark this bug as wishlist for future reference"
1661510,2018-07-09 19:51:22 UTC,"One possible approach would be to set the 'mandatory' flag when sending the message.  This should cause the broker to send back the message with a ""NO ROUTE"" error.   Not sure exactly how well this is supported (or if it would even work)."
1661510,2019-12-04 14:33:59 UTC,I have a brief example of how to use TransportOptions in the project update for last cycle: https://docs.google.com/presentation/d/1nFN2qWQJF7sUmUBDnEU66MDl7z5d6aO2AmE8l2zmPJ0/edit#slide=id.g6221d147b8_1_10 (it's slide 5 if the link doesn't take you directly there).
1661510,2019-12-03 23:20:41 UTC,"hi i think on one had this can now be cosed as i think
https://blueprints.launchpad.net/oslo.messaging/+spec/transport-options
has been completed
https://review.opendev.org/#/q/topic:bp/transport-options+(status:open+OR+status:merged)"
1661510,2019-07-03 07:57:50 UTC,Please see also the blueprint: [1]
1661510,2019-06-03 09:38:16 UTC,"We are working on it, it seems that Kombu in-memory transport does not support ""on_return"" function see the issue [1]."
1661510,2019-12-04 15:21:38 UTC,"I wrote something on my repository about the mandatory flag, if you'd like to test it:
https://github.com/Gsantomaggio/rabbitmq-utils/tree/master/openstack/mandatory_test"
1661510,2019-05-21 12:42:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660373"
1661510,2019-05-14 14:31:26 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659078"
1661510,2019-04-08 14:58:26 UTC,"The mandatory is the flag for this kind of situation, but in Kombu is not supported [1].
Check if a queue exists for each single publish dorps the performances drastically."
1661510,2018-10-24 09:30:40 UTC,"For option 2, py-amqp support argument `passive` in queue_declare[1].
And we may rewrite the function `Queue.declare` to accept argument `passive` and pass it to `queue_declare` in kombu[2]."
1661510,2019-05-21 12:43:30 UTC,"Change abandoned by Gabriele Santomaggio (<email address hidden>) on branch: master
Review: https://review.opendev.org/659078
Reason: closed in favor of https://review.opendev.org/#/c/660373/"
1661510,2017-06-08 12:02:53 UTC,"Can neutron agent wait server to start up? Like ""nova compute"" call wait_until_ready until ""conductor service"" is started."
1661513,2017-02-03 07:36:05 UTC,"Regression confirmed on Xubuntu 16.04, lp:inkscape rev. 15467."
1661513,2020-01-11 14:33:35 UTC,This can't be replicated anymore in current master (but was there in 1.0beta2) so I'm closing it.
1661533,2017-02-03 11:03:21 UTC,"The size calculation is quite rich, since you have older versions of
snaps, and backed-up data to deal with as well. Perhaps we want 'snap
size' which shows something like:"
1661533,2017-02-03 11:08:06 UTC,"Gack, LP ate my layout. See http://pastebin.ubuntu.com/23917485/ for suggested text layout of 'snap size' output."
1661533,2019-10-08 13:24:35 UTC,Some information is already reported by 'snap info'; we are aware it's limited and it's been requested by users via other channels as well to report more details. This is going to be addressed after some more discussions / agreements.
1661536,2017-02-03 08:55:56 UTC,And this is the different state screenshot.
1661543,2020-12-19 04:17:24 UTC,[Expired for tempest because there has been no activity for 60 days.]
1661543,2020-10-19 17:33:48 UTC,This bug was reported more than 3 years ago and  considering the significant change of the tempest's source code (also pointed out in the previous comment) I suspect this might not be valid anymore. I'll mark it as Incomplete for now. Please feel free to reopen it if you still experience the issue (with the current steps to reproduce).
1661543,2019-07-26 01:14:35 UTC,Heat is no longer in tempest should this bug be closed?
1661551,2017-05-04 16:08:21 UTC,"I just tried to reproduce this issue, but it works fine here."
1661551,2017-02-03 12:52:45 UTC,"Can you add --debug to the command? Though OSC strives to be as backward compatible as possible, the networking bits were recently added and may need fine tuning for an older cloud."
1661551,2017-04-29 14:46:29 UTC,"It is possible that the version of the openstacksdk used here will have some bearing on compatibility.  All Neutron commands call into the SDK and not neutronclient.  However it is more likely that this is due to some change in the Neutron API that OSC simply does not know about.  Much of the Neutron support is only a year or so old and may not have been written with compatibility with older APIs in mind, it certainly has not been tested against Liberty code in quite some time."
1661551,2017-02-03 15:31:53 UTC,"Hi Steve,"
1661553,2017-02-05 22:01:41 UTC,"The original implementation (for debs) was tech-agnostic, redirecting to ""apps/"", but then clicks were added to the store and unfortunately differentiated from the existing ""apps/"" with the prefix you see. Then snaps were added as extension of clicks (store devs didn't push back hard enough and time constraints won out)."
1661556,2017-04-04 02:53:26 UTC,"Alan, please specify the exact version of the web browser you are using."
1661556,2017-04-04 02:13:09 UTC,"Using: Elementary OS (0.4 Loki)
Dated: April 03, 2017
I'm also having this issue. System and applications are up to date."
1661556,2017-03-31 16:40:05 UTC,Ubuntu 16.04 LTS has epiphany 3.18.11 now. Can you confirm that this fixes this issue?
1661556,2017-03-03 11:56:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661556,2017-02-27 20:20:44 UTC,"Found a workaround by user BradPitcher here:
http://elementaryos.stackexchange.com/questions/10529/ctrl-whatever-and-shift-whatever-require-double-tap"
1661556,2017-03-03 11:53:34 UTC,This bug can be reproduced in Xubuntu 16.04 also
1661556,2017-02-13 05:20:34 UTC,"Sorry for this regression. I messed up backporting the fix for the Facebook issue to 3.18, and didn't notice until right when I was releasing 3.18.11."
1661556,2017-02-13 04:36:41 UTC,"I built 3.18.11 and indeed it is fixed there, so I think the fix is to merge the changes from upstream"
1661556,2017-02-13 02:14:44 UTC,More about the security update https://blogs.gnome.org/mcatanzaro/2017/02/07/on-epiphany-security-updates-and-stable-branches/
1661556,2017-02-13 01:14:34 UTC,"I posted this upstream (https://bugzilla.gnome.org/show_bug.cgi?id=778539). Apparently, it may be fixed in 3.18.11 (which has an important security update anyway) but I'm not sure how to test it."
1661556,2017-02-05 16:43:50 UTC,"Thanks a lot.
Let me known if I can help somehow else..
:)
Cheers"
1661556,2017-02-04 15:04:04 UTC,Verified issue with US keyboard layout as well.
1661556,2017-02-27 13:00:38 UTC,How can one fix it the existing oki install?
1661556,2017-02-27 20:07:19 UTC,"lease, let me know..."
1661561,2017-03-28 00:51:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450492"
1661561,2019-04-02 09:41:23 UTC,"Change abandoned by Kaifeng Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/450492
Reason: abandon for no activity, also the patch needs revision as our doc structure has changed"
1661567,2017-02-06 10:22:17 UTC,"Reviewed: https://review.fuel-infra.org/30455
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1661567,2017-02-03 10:56:20 UTC,"Fix proposed to branch: master
Change author: Mykyta Karpin <email address hidden>
Review: https://review.fuel-infra.org/30455"
1661571,2017-11-13 22:34:36 UTC,"Are you still working on this Hao Li? There isn't any patch link here, so I'm setting it back to triaged."
1661571,2020-02-07 01:24:43 UTC,"Change abandoned by Julia Kreger (<email address hidden>) on branch: master
Review: https://review.opendev.org/441924
Reason: Abandoning spec as it has not been updated in nearly three years. Functionally, the basic idea has been implemented with the conductor_groups functionality and the ability to select groups from the nova-compute."
1661571,2017-03-06 03:26:50 UTC,"In my company, we do a lot of work for make ironic supported aggregate. I will commit the specs and then commit the codes soon."
1661573,2017-02-03 11:21:47 UTC,"not reproduced on Windows 10, Inkscape 0.92.0 r15299
using the command
inkscape \windows\temp\test1.svg \windows\temp\test2.svg"
1661573,2017-02-03 16:16:05 UTC,"Earlier reports about the same issue:
* Bug #1540968 “Buggy export png dialog when opening multiple files”
  https://bugs.launchpad.net/inkscape/+bug/1540968
* Bug #1499980 “Tool dialogs end up all in one window when opening multiple documents”
  https://bugs.launchpad.net/inkscape/+bug/1499980
* Bug #1481719 “Crash when hiding dock with two files open”
  https://bugs.launchpad.net/inkscape/+bug/1481719"
1661573,2019-04-02 01:00:12 UTC,Message still appears about 'unable to add object to hash' but no longer see Inkscape crashing with Inkscape 0.92.4.
1661573,2019-04-02 01:03:50 UTC,"Crash now reproduced after closing the duplicate docks that appear, but that's more like bug 1499980."
1661573,2020-09-14 11:32:02 UTC,Closing because INVALID: Can't replicate.
1661574,2020-10-15 08:56:15 UTC,"Hi Junaid,"
1661576,2017-02-06 08:46:14 UTC,Marking as Won't Fix for 2.0.x as we are not planning another Juju 2.0.x release.
1661576,2017-02-06 06:15:07 UTC,2.0.2-xenial-amd64
1661576,2017-02-06 02:57:04 UTC,"@Stuart,
Please clarify what version of Juju you are running."
1661576,2017-02-06 08:45:29 UTC,"We track Juju 2.x issues in ""juju"" project. Re-targeting :D"
1661583,2019-09-19 12:02:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1661585,2017-02-04 09:53:28 UTC,Examples of apps that still show the animation:
1661585,2017-02-07 06:38:53 UTC,"Dear all,"
1661590,2018-03-30 15:04:06 UTC,Hi!
1661590,2017-03-03 16:29:17 UTC,  https://github.com/snapcore/snapd/pull/2982
1661590,2017-06-30 08:30:50 UTC,I put together a gnome-software patch to use the extra info from mvo's snapd change:
1661590,2017-06-30 09:05:26 UTC,Can you open bugs against GNOME Software upstream and propose patches there? In this case the patch to master will use snapd-glib and be different (I just pushed support for desktop files to snapd-glib master). You can backport changes either to the GNOME stable branch if OK'd by upstream or to the wip/ubuntu-* branches (the former is preferrable and then we can rebase the Ubuntu branches).
1661590,2018-03-29 22:12:26 UTC,"Hello Simos, or anyone else affected,"
1661590,2018-03-30 19:30:39 UTC,Thank you for taking the time to verify this stable release fix.  We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE).  Please remove the verification-done tag and add one for the release you have tested the package in.  Thank you!
1661590,2017-02-12 21:54:31 UTC,Sounds good. We'll add something along those lines to the API.
1661590,2018-05-02 04:04:06 UTC,"I also tried this in a VM which didn't have libreoffice installed - it launched the welcome window, not libreoffice base. I suspect Simos hadn't restarted GNOME Software (which is confusing, but the way is works). Marking as verified."
1661590,2018-05-03 15:59:02 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1661590,2018-05-03 15:59:10 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.10
1661590,2018-05-04 09:46:58 UTC,"I just tried again and now Software launches the correct command from the snap.
I do not remember for certain whether I closed Software with Ctrl+Q.
Sorry for the inconvenience."
1661590,2018-05-04 12:55:21 UTC,"Simos, GNOME Software keeps running in the background. After updating GNOME Software on Ubuntu 16.04 LTS, you either need to log out and log back in or run a command like:"
1661590,2019-10-29 19:09:23 UTC,I just tried to reproduce the bug as outlined in the bug description. I can confirm it is now fixed and working as expected. I'm marking the snappy task as fix released.
1661590,2018-04-13 04:17:17 UTC,"@simosx: I gave this another test on a clean xenial VM with the same gnome-software version as you.  Each time it launched the main ""libreoffice"" command (showing a window asking to open recent files or create a new document in one of the libreoffice applications)."
1661590,2017-02-12 21:08:22 UTC,GNOME Software currently doesn't actually introspect anything from the .snap directly. It uses snapd which I understand it is the desired design of snapd (I like this).
1661590,2017-02-09 03:34:45 UTC,I opened bug 1663103 about not being able to determine which slots each app uses.
1661590,2017-02-10 18:42:56 UTC,"On 10/02/17 16:50, John Lenton wrote:

> I should point out that there isn't a clear 1:1 mapping between desktop
> files and apps, and that some of the things mentioned here would impose
> this.
>
> FWIW IMHO if gnome software needs to choose one app from a snap to run
> because of its own limitations it should choose the default app, the one
> that has the same name as the snap.
"
1661590,2017-02-12 21:03:29 UTC,The solution we ended up implementing to determine if an app is graphical was in bug 1595023.
1661590,2017-02-07 21:01:40 UTC,We see the multiple commands but there's no way to differentiate between them. At the moment we're just launching the first command in the list.
1661590,2017-02-07 21:16:53 UTC,"In the same way that we can provide multiple entries to /snap/bin/ it
makes sense to offer multiple .desktop files. Would that get you closer
to a great desktop experience?"
1661590,2017-02-07 21:31:14 UTC,"snapd currently doesn't (directly) expose the .desktop files, but if we had those we could get a better experience."
1661590,2017-02-07 21:44:23 UTC,"OK, I'm +1 with that unless you have another suggestion. Could we put
the desktop file as an entry under the app command? I.e."
1661590,2017-02-07 23:18:08 UTC,"A note here that when you run ""snap info libreoffice"", the order of the commands actually changes every time you run it. I suppose that snapd does not have the order of the commands as given in snapcraft.yaml. That's what I get with snap 2.12"
1661590,2017-02-08 03:14:34 UTC,"I would hope that snapcraft can be made to automatically populate the apps data by detecting the .desktop files. In this case, the command does seem redundant. If GNOME Software knew the .desktop file it would use that information instead of the command."
1661590,2017-02-07 19:53:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661590,2017-02-10 15:36:54 UTC,Every application may already have an associated desktop file under meta/gui/<app>.desktop today.
1661590,2017-02-10 16:14:25 UTC,"Another side note: there's no special meaning to the order of commands in snap.yaml. We can reorder it, and snapcraft can reorder it, so please don't take it to mean something specific as that'll easily break."
1661590,2017-02-10 16:15:38 UTC,"@Mark: The command is not duplicated. The desktop file will call the actual command defined in the snap.yaml. It may provide additional arguments, but those will indeed be _in addition_ to the ones in snap.yaml."
1661590,2017-02-10 16:16:47 UTC,"More food for thought on the above note: the desktop file cannot call the real underlying command by itself! That would break confinement. It calls the confined binary under /snap/bin instead, which is what the ""command:"" attribute specifies. So, necessarily respected."
1661590,2017-02-10 16:18:20 UTC,"Robert: what do you actually need here?  We already support multiple desktop files, and they already hold metadata. gnome-software can already inspect to see which of these is available, I believe?  What are the missing pieces?"
1661590,2017-02-10 16:50:21 UTC,"I should point out that there isn't a clear 1:1 mapping between desktop files and apps, and that some of the things mentioned here would impose this."
1661590,2017-02-07 11:51:22 UTC,Adding Robert - is there anything you need from snapd to supoprt this? I think provide all the information if there are multiple apps in a single snap now?
1661600,2017-07-25 10:43:19 UTC,"IMO this is only a problem because we haven't yet taken a project-wide decision to bless the importer branches as the default repositories for their corresponding source packages (i.e. lp:ubuntu/+source/PACKAGE).  Once that happens, object sharing will automatically be set up for newly-pushed repositories."
1661600,2017-07-25 11:03:40 UTC,"On Tue, Jul 25, 2017 at 10:43:19AM -0000, Colin Watson wrote:

> IMO this is only a problem because we haven't yet taken a project-wide
> decision to bless the importer branches as the default repositories for
> their corresponding source packages (i.e. lp:ubuntu/+source/PACKAGE).
> Once that happens, object sharing will automatically be set up for
> newly-pushed repositories.
"
1661600,2017-07-25 11:36:24 UTC,"Yes, I see that point."
1661600,2017-07-25 12:02:26 UTC,"Could we perhaps put the importer branches in their ""official"" places, but make it clear that they are experimental and non-fast-forwarding until we declare hash stability at some future 1.0 date? I'm not sure I'm keen on this, but it may be the least worst option."
1661600,2017-10-31 00:01:35 UTC,"@racb: do you have a spec of the default aliases (even pseudocode, or what is necessary where)? I can work on implementing it, if so."
1661615,2017-02-07 03:30:11 UTC,Also valid for Fuel Newton/10.
1661621,2017-02-08 09:42:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661626,2020-01-13 19:04:48 UTC,One guessplanation for why this may work is:
1661626,2020-01-13 17:17:54 UTC,"Sure symlinking ~/.config/dconf/user to $XDG_RUNTIME_DIR/dconf/user doesn't seem like much of a stretch, but unfortunately it just doesn't work. In fact, the output is even worse with the symlink in place (neither get nor set seem to work anymore):"
1661626,2020-01-15 11:35:56 UTC,Snapcraft PR: https://github.com/snapcore/snapcraft/pull/2874
1661626,2019-11-01 13:55:15 UTC,desrt said this:
1661626,2019-10-31 17:29:12 UTC,I think Michael was onto something with his theory of two dconf/user files falling out of sync.
1661626,2019-10-15 12:42:05 UTC,I'm marking this bug as triaged/medium and will ask the desktop team to investigate.
1661626,2017-02-04 16:32:48 UTC,I have a feeling this has to do with the shm file in the xdg runtime directory.  This is how the service signals to clients that the database has changed and needs to be re-opened (otherwise they will continue to use the old copy).  If this is not being shared correctly between the snap and the outside work (different XDG_RUNTIME_DIR setting?) then dconf isn't going to report changes properly.
1661626,2019-11-03 13:04:37 UTC,"This is probably something for snapcraft-desktop-helpers and the gnome extension for Snapcraft.  It is the desktop-launch script that currently symlinks ~/.config/dconf to the location the snap will look for it, so it wouldn't be much of a stretch to do the same for $XDG_RUNTIME_DIR/dconf too.  The ""gsettings"" interface looks like it already grants the required AppArmor permissions, so I don't think there is anything strictly necessary to do on the snapd side."
1661640,2017-02-03 15:16:25 UTC,"using nvidia binary 370.28 driver, but i've been seeing this for years with ubuntu on different computers."
1661640,2017-02-03 16:07:23 UTC,"I've read that odd-numbered versions of Ubuntu (like 'Ubuntu 15.10' which you use) aren't recommended for common users.
It was advised to use an even-numbered versions, like Ubuntu 16.04."
1661648,2017-02-05 10:28:43 UTC,C'est une amélioration qui est prévue dans les plans. Sans doute dans la prochaine série de la V5.
1661654,2017-02-21 12:54:53 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/gonzo__4.4.0-63.84~14.04.2__2017-02-21_12-50-00/results-index.html"
1661654,2017-02-21 12:55:24 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/modoc__4.4.0-63.84~14.04.2__2017-02-21_12-51-00/results-index.html"
1661654,2017-02-21 13:32:21 UTC,"        tests ran:  10, failed: 1;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/pepe__4.4.0-63.84~14.04.2__2017-02-21_12-16-00/results-index.html"
1661654,2017-02-21 13:57:07 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/fozzie__4.4.0-63.84~14.04.2__2017-02-21_13-05-00/results-index.html"
1661654,2017-02-21 14:05:37 UTC,"        tests ran: 141, failed: 2;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/gonzo__4.4.0-63.84~14.04.2__2017-02-21_13-17-00/results-index.html"
1661654,2017-02-21 14:23:45 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/modoc__4.4.0-63.84~14.04.2__2017-02-21_13-19-00/results-index.html"
1661654,2017-02-21 15:13:37 UTC,"        tests ran:   3, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/modoc__4.4.0-63.84~14.04.2__2017-02-21_14-48-00/results-index.html"
1661654,2017-02-21 15:11:44 UTC,"        tests ran: 141, failed: 2;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/gonzo__4.4.0-63.84~14.04.2__2017-02-21_14-28-00/results-index.html"
1661654,2017-02-21 15:12:37 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/fozzie__4.4.0-63.84~14.04.2__2017-02-21_14-19-00/results-index.html"
1661654,2017-02-21 15:35:19 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/fozzie__4.4.0-63.84~14.04.2__2017-02-21_15-33-00/results-index.html"
1661654,2017-02-21 15:40:38 UTC,"        tests ran:   5, failed: 1;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/modoc__4.4.0-63.84~14.04.2__2017-02-21_15-37-00/results-index.html"
1661654,2017-04-25 10:19:11 UTC,Closing this task on this old bug.
1661654,2017-02-21 12:43:04 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/fozzie__4.4.0-63.84~14.04.2__2017-02-21_12-41-00/results-index.html"
1661654,2017-02-21 14:59:20 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/pepe__4.4.0-63.84~14.04.2__2017-02-21_13-53-00/results-index.html"
1661654,2017-02-21 12:27:33 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/gonzo__4.4.0-63.84~14.04.2__2017-02-21_12-24-00/results-index.html"
1661654,2017-02-21 15:50:00 UTC,"        tests ran:  33, failed: 4;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/pepe__4.4.0-63.84~14.04.2__2017-02-21_15-19-00/results-index.html"
1661654,2017-02-21 12:18:40 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/fozzie__4.4.0-63.84~14.04.2__2017-02-21_12-16-00/results-index.html"
1661654,2017-02-21 12:26:30 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84~14.04.2-generic/modoc__4.4.0-63.84~14.04.2__2017-02-21_12-24-00/results-index.html"
1661654,2017-02-20 17:36:17 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/kernel01__4.4.0-63.84__2017-02-20_17-34-00/results-index.html"
1661654,2017-02-20 17:33:15 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/s2lp6g001__4.4.0-63.84__2017-02-20_17-31-00/results-index.html"
1661654,2017-02-21 00:21:18 UTC,The following packages ended up in the wrong component in the -proposed pocket:
1661654,2017-02-21 01:46:36 UTC,The following packages ended up in the wrong component in the -proposed pocket:
1661654,2017-02-21 02:16:03 UTC,The following packages ended up in the wrong component in the -proposed pocket:
1661654,2017-02-21 04:21:15 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/s2lp6g001__4.4.0-63.84__2017-02-21_04-19-00/results-index.html"
1661654,2017-02-20 17:36:25 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/s2lp3__4.4.0-63.84__2017-02-20_17-34-00/results-index.html"
1661654,2017-02-21 04:21:42 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/s2lp3__4.4.0-63.84__2017-02-21_04-20-00/results-index.html"
1661654,2017-02-21 06:29:39 UTC,Hardware Certification have begun testing this -proposed kernel.
1661654,2017-02-21 11:28:53 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/s2lp6g001__4.4.0-63.84__2017-02-21_11-27-00/results-index.html"
1661654,2017-02-21 11:29:57 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.8.0-38.41~16.04.1-generic/s2lp3__4.8.0-38.41~16.04.1__2017-02-21_11-27-00/results-index.html"
1661654,2017-02-21 11:30:02 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/kernel01__4.4.0-63.84__2017-02-21_11-27-00/results-index.html"
1661654,2017-02-21 11:59:04 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/s2lp6g001__4.4.0-63.84__2017-02-21_11-57-00/results-index.html"
1661654,2017-02-21 04:21:38 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/kernel01__4.4.0-63.84__2017-02-21_04-20-00/results-index.html"
1661654,2017-02-21 11:58:55 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-63.84-generic/kernel01__4.4.0-63.84__2017-02-21_11-57-00/results-index.html"
1661663,2017-02-03 16:01:59 UTC,Rally report
1661672,2017-02-03 16:29:20 UTC,"Also, you should be able to access rescue mode from a 'Ready' state."
1661672,2017-02-03 19:04:57 UTC,"Andres,"
1661672,2019-09-19 11:55:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1661675,2017-02-04 10:25:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661675,2017-02-08 10:39:44 UTC,"Thank you for your feedback, your suggestions are all valid points. We have been working on an improved focus state in the switcher and the changes are currently in progress."
1661682,2020-04-11 14:15:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661682,2020-04-11 14:16:39 UTC,I can confirm that for XUbuntu 18.04.
1661682,2020-04-11 14:25:11 UTC,"Workaround: $ sudo apt install python-gi
After installing python-gi the light-locker-settings starts without issues.
I think there is a missing dependency from package light-locker-settings to python-gi.
Adding this dependency should fix this issue."
1661682,2017-02-03 17:04:53 UTC,At least on xenial...
1661684,2017-08-24 18:39:46 UTC,"------- Comment From <email address hidden> 2017-08-24 14:38 EDT-------
As not much info was there in the bug, I tested the kernels (mentioned in comment 57) on ubuntu 16.04 (LTS- 4.4.0-92-generic). When tried IO (Austin,hydepar EN, Shiner, Glacierpar) and CPU dlpar on both the kernel I didnt see any issue. But while removing memory (after adding the to mem to lpar), lpar dropped at xmon."
1661684,2017-08-24 18:49:50 UTC,"------- Comment From <email address hidden> 2017-08-24 14:43 EDT-------
hmc : daan1.isst.aus.stglabs.ibm.com has address 9.3.48.91 (hscroot/abc123)
CEC : rose
lpar : roselp2.isst.aus.stglabs.ibm.com has address 10.33.23.15 (root/don2rry)"
1661684,2017-02-20 05:39:49 UTC,------- Comment (attachment only) From <email address hidden> 2017-02-20 00:34 EDT-------
1661684,2018-08-16 08:49:50 UTC,"------- Comment From <email address hidden> 2018-08-16 04:42 EDT-------
Closing this bug..Its been so long it is kept open.Feel free to reopen if issue recreates.."
1661684,2017-02-03 17:10:09 UTC,Default Comment by Bridge
1661684,2017-02-03 17:10:07 UTC,Default Comment by Bridge
1661684,2017-02-03 17:09:43 UTC,Default Comment by Bridge
1661684,2017-02-03 17:09:40 UTC,Default Comment by Bridge
1661684,2017-02-03 17:10:11 UTC,Default Comment by Bridge
1661695,2017-03-16 00:15:33 UTC,Here are the exact commits that fix this issue for both radeon and amdgpu drivers on 4.10 mainline in case anyone comes across this for SI cards.
1661695,2017-03-08 00:58:30 UTC,@jsalisbur I found the exact commit that fixes this issue for SI cards
1661695,2017-02-28 00:32:21 UTC,I think a fix for this was committed a few days ago. Possibly http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e8fe3bfd306d376c035c754e6c7d36826a0e3f78
1661695,2017-02-06 20:16:06 UTC,similar bug with the same card https://bugs.freedesktop.org/show_bug.cgi?id=73116
1661695,2017-02-03 19:07:44 UTC,"Screen flickering is happening in 4.4.0-53 now as well, but much much less often."
1661695,2017-02-03 18:32:43 UTC,apport information
1661695,2017-02-03 18:32:41 UTC,apport information
1661695,2017-02-03 18:32:39 UTC,apport information
1661695,2017-02-06 19:38:25 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1661695,2017-02-03 18:32:35 UTC,apport information
1661695,2017-02-03 18:32:33 UTC,apport information
1661695,2017-02-03 18:32:31 UTC,apport information
1661695,2017-02-03 18:32:30 UTC,apport information
1661695,2017-02-03 18:32:28 UTC,apport information
1661695,2017-02-03 18:32:25 UTC,apport information
1661695,2017-02-03 18:32:22 UTC,apport information
1661695,2017-02-03 18:32:20 UTC,apport information
1661695,2017-02-03 18:32:18 UTC,apport information
1661695,2017-02-03 18:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1661695,2017-02-03 18:32:36 UTC,apport information
1661698,2017-02-04 00:34:33 UTC,I'm going to confirm just because that should be the future behavior is using GVFS/policykit integration
1661698,2017-02-03 18:07:26 UTC,"well they should probably still use pkexec pantheon-files. But really, I thought the latest glib was supposed to have policykit integration so we shouldn't need this at all. Are we just waiting on a new version?"
1661698,2017-02-03 23:16:07 UTC,I think that will become valid when we will be able to authenticate modifying files with admin permissions with normal Files instance (non-root).
1661705,2018-04-02 22:35:06 UTC,I changed the release version to v6 so we can do a proper evaluation of the problem.
1661705,2018-03-21 01:26:52 UTC,"I'm with Wayne here, I think that since a real fix will involve some kind of warning/migration for existing boards that are too big, and because you have to go out of your way to trigger this bug, I don't think it's critical to 5.0 release."
1661705,2018-03-20 17:08:14 UTC,"On 3/15/2018 5:32 PM, Seth Hillbrand wrote:

> I think that there's still a bug here for 5.
>
> In pcbnew, if I place text at the edge, either by placing it or moving
> it to the maximum value, I get this issue.
>
> Steps:
> 1) Place a text on F.Cu
> 2) Select and choose Move Relative
> 3) Input -2148, -2148 for the X/Y coordinates. Click OK
> 4) Save
> 5) plot to gerber.
>
> pcbnew will write the file like this:
>
>   (gr_text Test (at -2147.483648 -2147.483648) (layer F.Cu)
>     (effects (font (size 1.5 1.5) (thickness 0.3)))
>
> The gerbview output looks like the OP's image.  Just a straight line,
> top to bottom.
>
> Not really a realistic board but nevertheless I think the bug could be
> that we don't limit placing/moving items to the 1m limit.
>
"
1661705,2018-03-15 21:32:22 UTC,I think that there's still a bug here for 5.
1661705,2018-03-15 21:04:20 UTC,Sounds like it to me....
1661705,2018-03-08 17:54:14 UTC,"On 3/8/2018 11:56 AM, jean-pierre charras wrote:

> 1 - The coordinates are from -2147.483648mm to 2147.483648mm.
> But I talked about a board, not coordinates.
> This is a bit different.
> For instance in some calculations, we calculate absolute values, therefore 0 to 2147.483648
> and a diagonal distance limits coordinates to 0 to 2147.483648/1.414 = 1.6m
"
1661705,2018-03-15 01:53:54 UTC,So should we remove this from 5.0RC2 milestone then?
1661705,2018-03-08 19:06:52 UTC,"I agree we should take a look at this in v6 about this.
However:
- Many calculations are already made in 64 bits.
- More or less the working area is already limited.
It is still too big in GAL mode, but it is limited.
But this is also a proof this offending file was modified outside Pcbnew."
1661705,2018-03-08 16:56:45 UTC,"1 - The coordinates are from -2147.483648mm to 2147.483648mm.
But I talked about a board, not coordinates.
This is a bit different.
For instance in some calculations, we calculate absolute values, therefore 0 to 2147.483648
and a diagonal distance limits coordinates to 0 to 2147.483648/1.414 = 1.6m"
1661705,2018-03-08 13:46:11 UTC,"Hmm, how should we fix this for Gerber export?  Warn the user that their board does not fit within the maximum dimensions of a Gerber file?"
1661705,2018-03-08 15:31:45 UTC,"No so simple.
Gerber can handle 9999.99999 mm (internal unit = 10 nanometers)"
1661705,2018-03-08 16:07:46 UTC,"On 3/8/2018 10:31 AM, jean-pierre charras wrote:

> No so simple.
> Gerber can handle 9999.99999 mm (internal unit = 10 nanometers)
>
> But Pcbnew cannot handle this size.
> It is limited to roughly -1m to +1m
"
1661705,2017-02-03 18:23:45 UTC,I should have looked. The original poster also made a bug report here: #1661674
1661705,2017-02-04 02:39:07 UTC,Also replicated under 4.0.5 Stable for Windows 64 bit
1661705,2017-02-04 13:12:31 UTC,"My mistake, spurious lines are present when the the file is used to create Gerber plots under 4.0.5 Win 64 and 4.0.5 Ubuntu 64 bit stable from the PPA"
1661705,2017-02-04 09:04:38 UTC,And after a reload in 4.0.5 no longer visible. Very odd
1661705,2017-02-04 21:31:32 UTC,"Using the ""4.5 (unit mm)"" gerber format does not create the same effect. There the half of the text that generates the overflow is not plotted."
1661705,2018-03-08 13:57:56 UTC,"I'd be more inclined to error-out.  If the board can't be represented in Gerber, then there's no point saving a Gerber."
1661705,2017-02-04 14:26:41 UTC,I have marked #1661674 as a duplicte of this since this bug contains more information.
1661705,2018-03-08 14:43:02 UTC,"Why do you think it is an issue in the file?  I suspect that this might just be in the viewer.  Gerber _should_ handle positions as text with 4.6 format, so up to 9999.999999 mm/in."
1661714,2017-02-07 13:35:44 UTC,"To clarify, how can one expect the resources to be created and in the expected state without either us communicating via our API that the bulk operation is complete (so they'd watch a URL, I guess?) or they'd have to loop over said resources to confirm they're how they want them to be... by the time they're doing that, we might as well have looped over the resources creating them."
1661714,2017-02-10 12:28:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432283"
1661714,2017-02-08 14:28:18 UTC,"> What would the rate limit look like for an API request that can add thousands of devices in one go, plus potentially tens of thousands of variables and labels?
"
1661714,2017-02-08 12:11:28 UTC,"If an operator has to do a one-time import that takes some time to run, I don't necessarily see that as a major blocker."
1661714,2017-02-07 16:02:36 UTC,"> If there is a strong user story, that is solved by bulk imports, what about simply using the client to iterate over the data and make a series of requests? I would prefer us to look at simple solutions using the existing API and only extend it when there is a good justification.
"
1661714,2017-02-07 13:32:29 UTC,"I think that's a fair point. Also, thinking about it, there are some snags when it comes to communicating that the update or import is complete. Depending on the size of the update, it could take a fair amount of time to complete. How does the end-user know it's done and one can expect those variables to be set properly before doing something with those resources? We'd either have to provide this more as a Job concept, or the end-user would have to verify the data (looping over it anyway). Thoughts?"
1661714,2017-02-06 22:00:38 UTC,"Are we considering PATCH because it's the OpenStack API WG standard, or because we think it'll help? I ask because partial-PUTs are generally easier to work with, and the industry as a whole uses them since there's not much use for the HTTP standard use of the PUT verb."
1661714,2017-02-06 22:30:49 UTC,"We can move dev into a companion BP and corresponding spec, that makes the most sense to me."
1661714,2017-02-06 22:05:40 UTC,"Maybe move the ""id"" attribute up one level so you could conceivably place the same request to a PUT on the resource itself in the ""data"" field."
1661714,2017-02-06 22:04:09 UTC,Bulk changes could look like:
1661714,2017-02-06 21:55:35 UTC,Some initial thoughts...
1661714,2017-02-06 21:46:25 UTC,"I think it would make sense to convert this to a BP, especially since we're pursuing a spec for it. Thoughts?"
1661714,2017-02-03 19:05:52 UTC,"We can also use this to remove the existing ansible-inventory endpoint: we can push its functionality for building the Ansible formatting specifics into client code, while retaining its functionality for bulk reads out of the db."
1661714,2017-02-07 11:51:19 UTC,"Based on the description, the priority of this task seems high. What would this be doing that a bash for-loop can't do?"
1661717,2020-02-07 19:03:00 UTC,"Since there is a workaround, and this is only regarding the Linux Bridge agent, which is not actively maintained, I'm closing this since it doesn't seem like it will be fixed."
1661717,2017-03-02 22:09:54 UTC,Temporary workaround is to set arp_responder=false to allow ARP learning.
1661717,2017-02-03 21:15:15 UTC,"Yes we are seeing connectivity issues. Instances on the internal network can not reach external network. We think this is due to the missing arp entry on the compute host. Therefore instances do not have enough information to forward the traffic. Once we manually add the missing arp entry to the arp table, connectivity starts to work."
1661717,2017-02-04 22:16:13 UTC,https://github.com/openstack/neutron/blob/stable/newton/neutron/plugins/ml2/models.py#L86
1661717,2017-02-09 22:47:43 UTC,I believe the missing piece of the puzzle is that this is happening with the Linux Bridge agent.
1661717,2017-02-03 19:22:58 UTC,This is intentional. We don't use l2pop to teach agents about internal networks connected to HA routers. The agent is supposed to learn these addresses via normal switching / MAC learning.
1661720,2017-02-21 19:53:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661733,2018-01-23 15:35:11 UTC,"Change abandoned by Sulochan Acharya (<email address hidden>) on branch: master
Review: https://review.openstack.org/429118"
1661734,2018-01-23 15:34:59 UTC,"Change abandoned by Sulochan Acharya (<email address hidden>) on branch: master
Review: https://review.openstack.org/429110"
1661739,2017-02-03 21:42:17 UTC,"I was unable to get Amarok working again by manually downgrading gstreamer packages, so I resorted to reverting my entire root filesystem to a previous btrfs snapshot."
1661739,2017-02-06 10:03:15 UTC,"Are you sure you have the gstreamer plugins installed for your gstreamer version? Since you need the 1.x versions, make sure your plugins are also for that version, the 0.10.x versions will not work.
FWIW: this is not an Amarok bug, but an installation mismatch of the gstreamer plugins."
1661739,2017-02-06 10:14:41 UTC,see upstream report https://bugs.kde.org/show_bug.cgi?id=335111
1661739,2017-02-06 21:15:35 UTC,"Thanks for the attention. I wasn't sure at all which package I should choose, and Amarok seemed like a decent guess. I don't have a Phonon VLC backend installed at all; only the gstreamer backend."
1661739,2017-02-07 23:03:00 UTC,"Did you check the upstream bug? This is easy to solve...
As a reminder: Amarok is not responsible for the Phonon backends, nor are we in any way responsible for gstreamer plugins.
You have a mismatch of plugins installed, please make sure you have only one gstreamer library version and the appropriate plugins for restricted codecs (which is the case for MP3), the mix is what causes the problem."
1661741,2018-06-07 14:09:43 UTC,"I have a Samsung 960 EVO MZ. So a different SSD, at least. I never thought to update the SSD firmware."
1661741,2018-06-21 20:43:07 UTC,"This has affected me.  I have a latitude e7470, and have found this exact suspend/resume problem with a range of kernels, currently 4.13.0-41-generic"
1661741,2018-08-19 22:52:40 UTC,"Exactly the same for me : E5470, with 4.15.0-30 and 3 month previous kernel
with lvm inside cryptsetup partition"
1661741,2020-03-06 12:57:56 UTC,I created the new bug report/issue #1866343 for the Dell Latitude 5488 [1].
1661741,2020-04-07 21:32:21 UTC,"A similar bug affects several Dell laptop models:
- Dell 5480/5488 :
https://bugs.launchpad.net/dell-sputnik/+bug/1866343
- Dell E5470 :
https://bugs.launchpad.net/dell-sputnik/+bug/1661741
(Note that the bug https://bugs.launchpad.net/dell-sputnik/+bug/1661741 is not fixed; it has been changed, by error, to fixed. Please, it will be nice if somebody can change the status to ""confirmed"")
- Dell 7740 :
https://bugs.launchpad.net/dell-sputnik/+bug/1871491"
1661741,2020-03-30 07:08:11 UTC,"@delluser, where is the fix released?"
1661741,2018-06-07 03:13:54 UTC,Do all affected users use SK Hynix SC300 M.2?
1661741,2020-03-30 10:35:56 UTC,It is an error. Please: Fix Released → Confirmed
1661741,2020-06-11 07:59:39 UTC,"@delluser, on the next day, April 8th, you commented in #1871491 [1], that the issue is fixed."
1661741,2020-07-21 22:36:33 UTC,"I ran into this problem with my Dell Latitude E5470 (6300U/8GB/256GB SanDisk X400 m2), too. suspend and resume used to work just fine with Ubuntu 19.10 and 20.04 until mid of July. With no apparent reason from this time on the computer did not resume after suspend when running on battery. I found this bug report und Jonathan’s solution worked for me, too. My computer even never hibernated but just powered off because there was no swap partition available. Since I switched back to suspend the computer resumes correctly after suspend even running on battery."
1661741,2020-03-28 12:23:25 UTC,"I have a similar problem on DELL Precision 7740 (laptop):
1) suspend
2) unplug the cord
3) try to resume : the computer does not resume, but the keyboard is lighted
4) hard reboot (by pressing the power button during several seconds)
5) at the next boot, the computer hangs just after the GRUB."
1661741,2018-06-05 19:59:15 UTC,"I was able to resolve this by updating the ssd firmware (SK Hynix SC300 M.2) from here: https://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=754Y5
The update page states: **Fixes an issue which can cause the SSD to occasionally not wake up from low power mode**"
1661741,2017-05-29 10:20:54 UTC,"Ok, and like Jan, I managed to fixed things by one hibernation cycle with power plugged in, and one with no power connected."
1661741,2017-11-23 03:14:05 UTC,"Which version of Ubuntu are you using? Did you try the magical incantation I listed in my initial post? I am currently using 16.04. There was a few days (maybe 2 or 3 weeks ago) when the problem reappeared but it disappeared again. I thought it might have been related to a new kernel version but I didn't get a chance to try the newest mainline kernel before it went away.
If my instructions don't help, I'd suggest trying the newest kernel to see if that helps."
1661741,2017-11-23 06:45:25 UTC,"Jonathan,
let me add more info.
The issue could be seen on kernels: 4.4, 4.11, 4.13.
Then I've tested your idea and in fact it heklped i.e. it works now."
1661741,2017-02-03 21:01:06 UTC,This change was made by a bot.
1661741,2017-02-06 19:39:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1661741,2017-02-07 00:33:15 UTC,"So, a strange thing happened. In order to mitigate the problem, I decided to switch to having the computer hibernate instead of suspend (I outline below the steps I did to do that). And then, on a whim, I tried suspending again. And it stopped crashing, even after I switched back to suspend completely. I didn't do any software updates or, as far as I know, anything else in the interim. So right now, I have my computer set to suspend and it seems to work fine. I was waiting a few days to see if the problem reemered but right now, I can't reproduce it at all."
1661741,2017-04-08 04:18:34 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1661741,2017-05-04 01:41:13 UTC,"Weird, right? I'm fairly content with my Dell but I think there are some Linux-related BIOS issues. I'm glad that 1) this fixed your suspend issues, 2) that I'm now sure that I'm not crazy."
1661741,2017-05-03 14:09:36 UTC,"I have received brand new Dell Latitude E7470 with preinstalled Windows. I have reinstalled the system with Ubuntu 16.04.2 from flash, formatting the entire hard drive along the way."
1661741,2017-05-30 02:44:05 UTC,"There are definitely at least *some* BIOS problems with the 5470. For example, it seems to have clock speed issues (where the CPU clock speed will stay between 400 MHz - 800 MHz) which I have to resolve using either `wrmsr -a 0x19a 0x0` or `cpupower frequency-set -g performance` or both."
1661741,2017-05-30 07:42:02 UTC,Can you try mainline kernel in comment #3?
1661741,2017-06-02 02:16:09 UTC,I will try when I get a chance but I am busy for at least a few days and this is my main computer so I can't afford to muck around with it too carelessly.
1661741,2017-06-02 06:50:13 UTC,"So, I have a Dell Lattitude E7470 that had the very same problem."
1661741,2017-05-29 09:57:14 UTC,"Recently, my Dell E7470 started showing the same symptoms: resume works fine, but when waking from resume, it reboots instead of waking up.  pm_trace show only a hah match on ACPI device 0d, quite like it does for the original reporter."
1661741,2017-11-22 22:53:31 UTC,I can confirm that suspend works properly with Bios 1.15.4 but it's again broken with 1.17.3 :(
1661743,2017-02-16 09:17:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661743,2017-02-16 12:12:44 UTC,"FYI, IIRC this would happen on Touch but on Touch we would explicitly deny access to network manager in the networking policy group which suppressed the apparmor denial. Due to the way apparmor works and how snappy builds up interfaces, we use explicit denials extremely sparingly, which is why you may be seeing this only now."
1661743,2017-02-16 12:47:43 UTC,"@jdstrand the issue is not with apparmor but with XmlListModel trying to make a request(or access NM) while i am only using `xml` prop, the content provided as string so no network calls should be made i think."
1661745,2019-06-11 15:25:11 UTC,"Note that this has the potential of breaking existing scripts, so it's probably not a good SRU candidate."
1661745,2019-06-19 16:46:58 UTC,This bug was fixed in the package openssh - 1:8.0p1-2
1661745,2017-02-06 10:58:00 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue.
1661745,2019-06-11 15:23:45 UTC,"Upstream commit in 8.0:
commit c2c18a39683db382a15b438632afab3f551d50ce
Author: <email address hidden> <email address hidden>
Date:   Sat Jan 26 22:35:01 2019 +0000"
1661745,2017-02-06 10:57:52 UTC,"Hi,
I'm not sure ssh-keyscan was ever defined to have bad RC in that case.
The man page is empty, and the bit that I found online says:"
1661753,2017-02-09 14:31:33 UTC,The solution seems to be to add
1661753,2017-10-17 07:51:49 UTC,The warning message has not changed in Pike. It still suggests that the in-process token cache may be removed for Ocata. So we're good at least until Queens.
1661758,2021-01-08 04:17:21 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1661758,2020-11-08 09:07:02 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1661760,2017-03-13 18:18:21 UTC,I can confirm that the bug exists on 16.10 too.
1661760,2017-03-13 20:14:09 UTC,"This is easy to fix:
Remove the file ""~/.config/evince/print-settings"" as pointed out in https://wiki.ubuntu.com/DebuggingPrintingProblems"
1661760,2017-03-14 20:22:01 UTC,"This works, but you have to remove the file every time it is printed."
1661760,2020-07-01 21:24:38 UTC,"Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1661760,2017-03-13 18:00:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661760,2020-08-31 04:17:38 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1661772,2017-02-06 19:13:13 UTC,"For clarity, this issue was found on Mitaka"
1661772,2017-03-30 10:14:45 UTC,"Pretty sure this is not a charm specific issue, so raising bug task against nova."
1661772,2017-03-31 15:34:23 UTC,Could you please provide logs and steps for reproducing?
1661772,2017-05-25 22:53:52 UTC,"Sorry for lag in response.  Logs not handy, but to reproduce:"
1661772,2017-07-25 04:19:08 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1661772,2018-10-12 19:08:08 UTC,"This is unfortunately a known issue in nova for several years now, as nova historically has not had proper support for shared storage (there are many gaps)."
1661774,2017-07-27 19:03:39 UTC,This is still present in 3.18.11
1661776,2017-02-03 23:55:55 UTC,Still effects puppy and linuxmint.
1661779,2017-02-06 10:41:19 UTC,While reported on the Yakkety Version there are also 208 hits on that with the version in Xenial.
1661779,2019-03-15 16:20:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661779,2020-07-02 18:58:37 UTC,"From the error tracker, this appears to have occurred with apache versions from 2.4.6 through 2.4.18-2ubuntu4.2.  On Xenial there was still one report against the current supported apache version, 2.4.18-2ubuntu3.14.  The most recent occurrence on Xenial is from March 31, 2020."
1661788,2017-09-01 16:16:42 UTC,Unassigning due to no activity for > 6 months.
1661794,2017-02-14 11:53:26 UTC,"Also, the close button and zoom button doesn't work well."
1661797,2017-09-23 02:15:12 UTC,"This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New"
1661797,2017-03-22 13:03:49 UTC,nova-lxd changes are now present in both yakkety-proposed (14.2.0-0ubuntu0.16.10.1) and xenial-proposed (13.3.0-0ubuntu1).
1661797,2017-03-16 10:28:16 UTC,"Marking nova-lxd task as Fix Released; changes landed and released, need to work through SRU process."
1661797,2017-03-03 15:03:10 UTC,"Chuck has just uploaded nova-lxd_14.2.0-0ubuntu0.16.10.1.dsc  for yakkety to SRU queue.
This bug is fixed in that release."
1661797,2017-03-03 14:46:56 UTC,"I've marked this as 'In progress' for nova-lxd in ubuntu for xenial.
That is per comment from Chuck that this is included in the SRU that is in the queue (13.3.0-0ubuntu1)."
1661797,2017-03-03 14:41:48 UTC,Marking fix-released in nova-lxd  in zesty.
1661797,2017-02-09 20:31:24 UTC,This bug was fixed in the package cloud-init - 0.7.9-23-g0df21b6-0ubuntu1
1661797,2017-02-09 15:14:14 UTC,"Change abandoned by Paul Hummer (<email address hidden>) on branch: master
Review: https://review.openstack.org/431247
Reason: The actual change occurred in another patch."
1661797,2017-02-09 07:52:38 UTC,I've combined this patch functionality into this patch (the flavor<->profile code was refactored in an already submitted patch). https://review.openstack.org/#/c/411985/
1661797,2017-02-09 02:43:20 UTC,There is a gerrit review at https://review.openstack.org/#/c/431247/1
1661797,2017-02-08 15:30:50 UTC,"You could also potentially be the first users of /dev/lxd, setting some key like user.is-nova-lxd: true for the container, and then querying it over /dev/lxd."
1661797,2017-02-06 15:34:22 UTC,"We could also look at exporting a file/key via lxcfs that we could detect?  Not sure if lxcfs can also emulate sys, but if so, then /sys/hypervisor/lxd would be a good place as well."
1661797,2017-02-28 17:24:52 UTC,"I marked this as fix-released in zesty just by
 pull-lp-source nova-lxd zesty"
1661812,2017-02-07 08:57:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661812,2017-02-07 08:58:36 UTC,"Bug occured for me after kernel has updated.
4.4.0-59-generic works fine, bit with 4.4.0-61-generic it reproduceably crashes."
1661812,2017-03-19 10:56:11 UTC,"Occurs with the 66er Kernel, too. Update just went through and after boot I am in fallback mode w/o graqphis driver."
1661815,2017-02-06 10:26:05 UTC,"The calling function never uses ""->fields"", so I do not see a real vulnerability here, is there? Did you use a code analyser for this, or how did you come across this issue?"
1661815,2017-02-06 12:17:08 UTC,Thanks for your reply.
1661815,2020-01-23 11:11:37 UTC,"I've finally posted a patch for this:
https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg05204.html"
1661815,2020-02-11 14:34:04 UTC,"Fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=344a7f656e8d211cdd6e"
1661819,2017-02-12 09:16:17 UTC,"It seems to me that the module `ngx_set_misc` is not compiled into nginx or bundled with nginx-extras package, and `ngx_http_lua_module.so` depends on it."
1661819,2017-02-24 09:17:14 UTC,"Thank you, it worked for me as well."
1661819,2017-02-23 15:15:15 UTC,"Thank you, it helped."
1661819,2017-02-23 14:37:20 UTC,Try loading the ndk module:
1661819,2017-02-23 12:46:08 UTC,Same issue for me while upgrading from 1.10.1-3 to 1.10.3-0.
1661819,2017-02-12 08:52:38 UTC,"This morning I upgraded nginx-extras with `apt-get dist-upgrade`. The problem persists. nginx configuration now is as follows:
`nginx -V`:
```
nginx version: nginx/1.10.3
built with OpenSSL 1.0.2g  1 Mar 2016
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fdebug-prefix-map=/build/nginx-Mpuecc/nginx-1.10.3=. -fPIE -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -fPIC' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --modules-path=/usr/lib/nginx/modules --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_v2_module --with-http_dav_module --with-http_slice_module --with-threads --with-http_addition_module --with-http_flv_module --with-http_geoip_module=dynamic --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module=dynamic --with-http_mp4_module --with-http_perl_module=dynamic --with-http_random_index_module --with-http_secure_link_module --with-http_sub_module --with-http_xslt_module=dynamic --with-mail=dynamic --with-mail_ssl_module --with-stream=dynamic --with-stream_ssl_module --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/headers-more-nginx-module --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nginx-auth-pam --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nginx-cache-purge --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nginx-dav-ext-module --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nginx-development-kit --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nginx-echo --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/ngx-fancyindex --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nchan --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nginx-lua --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nginx-upload-progress --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/nginx-upstream-fair --add-dynamic-module=/build/nginx-Mpuecc/nginx-1.10.3/debian/modules/ngx_http_substitutions_filter_module
```"
1661819,2017-02-04 17:59:01 UTC,Yes.
1661819,2017-02-10 17:06:41 UTC,I've tested this binary from the PPA on a Yakkety VM and a Yakkety LXC container.  I could not replicate this issue.
1661819,2017-02-09 20:58:34 UTC,Also provide details about your system please.  Including your architecture that your system is (or alternatively just include `uname -a
1661819,2017-02-09 20:57:24 UTC,"I can't confirm this in Xenial, let me test my Yakkety system."
1661819,2017-02-04 18:16:55 UTC,Invalid against Ubuntu as it is from the PPA.  Valid for the Nginx project here on Launchpad though.
1661819,2017-02-04 17:34:08 UTC,Dynamic modules are not in the Ubuntu repositories - are you using a PPA?
1661819,2017-02-11 08:39:55 UTC,"This is the minimal configuration that causes the error:
```
# For Lua balancer:
load_module ""modules/ngx_http_lua_module.so"";"
1661829,2017-03-09 05:09:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661829,2017-03-28 15:07:08 UTC,@ iaksit
1661849,2017-02-16 14:47:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661849,2017-02-16 14:48:31 UTC,Same Problem here with ntp:
1661849,2017-09-01 07:30:50 UTC,Similar issue:
1661851,2017-02-04 15:27:07 UTC,"One more info - after making the journal persistent, this is the end of the journal for the session ending with the hang:"
1661851,2018-03-05 13:43:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661864,2018-03-30 21:21:55 UTC,An update: I now have kernel 4.16rc1 and the situation is exactly as I said in my last comment #19
1661864,2017-12-21 15:01:16 UTC,An update on this issue now that I have kernel 4.14:
1661864,2017-02-07 21:26:20 UTC,"* Forget about the part ""why some keys are now working, others don't"". My mistake"
1661864,2017-02-07 21:24:13 UTC,"Hi,"
1661864,2017-02-06 19:43:01 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1661864,2017-02-04 18:05:22 UTC,apport information
1661864,2017-02-04 18:05:20 UTC,apport information
1661864,2017-02-04 18:05:18 UTC,apport information
1661864,2017-02-04 18:05:16 UTC,apport information
1661864,2017-02-04 18:05:09 UTC,apport information
1661864,2017-02-04 18:05:12 UTC,apport information
1661864,2017-02-04 18:05:11 UTC,apport information
1661864,2017-02-04 18:05:07 UTC,apport information
1661864,2017-02-04 18:05:06 UTC,apport information
1661864,2017-02-04 18:05:03 UTC,apport information
1661864,2017-02-04 18:05:01 UTC,apport information
1661864,2017-02-04 18:04:59 UTC,apport information
1661864,2017-02-04 18:04:57 UTC,apport information
1661864,2017-02-04 17:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1661864,2017-02-04 18:05:14 UTC,apport information
1661878,2017-02-04 18:38:40 UTC,apport information
1661878,2017-02-04 19:00:10 UTC,This change was made by a bot.
1661878,2017-02-06 19:44:22 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1661878,2018-03-30 21:23:03 UTC,An update: I now have kernel 4.16rc1 and the situation is exactly the same.
1661878,2018-01-02 02:52:28 UTC,I think Unity doesn't support screen rotate. Please try latest Ubuntu or Ubuntu-Gnome.
1661878,2018-01-02 11:57:08 UTC,"@Kai-Heng, when the screen is rotated, the keyboard is locked, so that is detected somehow. Also, if you go to the screen display properties, you can rotate whether it is Unity or Gnome or others.
Thus, I guess it should be possible to combine this in some way."
1661878,2017-02-04 18:38:37 UTC,apport information
1661878,2017-12-21 15:00:54 UTC,An update on this issue now that I have kernel 4.14:
1661878,2017-02-04 18:38:35 UTC,apport information
1661878,2017-02-07 21:57:29 UTC,"So, it seems that in the upstream kernel the physical rotation is detected. I say this because when I rotate the 360º the keyboard is blocked (I try to write and I can't)."
1661878,2017-02-04 18:38:32 UTC,apport information
1661878,2017-02-04 18:38:30 UTC,apport information
1661878,2017-02-04 18:38:29 UTC,apport information
1661878,2017-02-04 18:38:26 UTC,apport information
1661878,2017-02-04 18:38:25 UTC,apport information
1661878,2017-02-04 18:38:23 UTC,apport information
1661878,2017-02-04 18:38:21 UTC,apport information
1661878,2017-02-04 18:38:20 UTC,apport information
1661878,2017-02-04 18:38:19 UTC,apport information
1661878,2017-02-04 18:38:18 UTC,apport information
1661878,2017-02-04 18:38:34 UTC,apport information
1661879,2019-09-19 12:02:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1661885,2017-02-04 23:02:41 UTC,Won't fix. This is a bug on the version of doxygen available in 16.04 and I cannot fix it. It also happened on Debian with the very same version of Doxygen. It is already fixed in next versions.
1661885,2017-02-04 23:03:05 UTC,"As a workaround, please check the documentation online"
1661888,2017-02-08 22:30:07 UTC,"The event venue is apparently functional today, however the space for the contact individual is not.  If one is listed and you try to change it, the page will still freeze for about 30 seconds.  If one is not listed and you try to submit without a contact individual, the submitter will get a message that says that the contact individual in a required field."
1661888,2017-02-08 22:57:19 UTC,"Thanks Rex for the report, i'll try to look at this issue ASAP."
1661892,2017-07-04 18:41:50 UTC,"I think that instead of reconnecting if the network is IPv6 only, it could show a message box (with a Don't Show Again option) that will notify the user of this problem."
1661894,2017-02-05 01:56:51 UTC,Attached is the image difference created with archived trunk builds (on OS X 10.7.5) from before and after the merge of the experiment branch in rev 13641: r13638 and r13646
1661894,2017-02-05 02:27:42 UTC,"Lastly, I redid the comparison using PNGs exported via GUI to 4000x4000 px with Inkscape 0.91 and lp:inkscape/0.92.x r15355, with each of the available options for dpi change on load separately: all three comparisons show the same difference as the image attached in comment 2. This indicates AFAIU that the differences are not related to the DPI change (or to overall scaling of the document on load or export)."
1661894,2017-02-05 03:56:46 UTC,"The difference images created with IM attached earlier might be misleading wrt to the exact amount of the differences, my mistake (I definitely need to work on my IM skills)."
1661894,2017-02-05 05:28:12 UTC,"Attached is an alternate test case (SVG created with Inkscape 0.91 r13725), to investigate whether the reported issue relates to certain geometry or path commands:
- left: group of concentric circles converted to path (the paths use arc commands);
  clipped to half of the page
- right: group of concentric circles converted to path, nodes nudged to force conversion to cubic bézier commands;
  clipped to other half of the page."
1661894,2017-02-05 05:32:47 UTC,"The attached image difference (with IM compare, once again) of cli PNG export with 0.91 and 0.92 to 2560x2560 px shows that only the arc path commands (on the left) are affected by the reported issue."
1661894,2017-02-05 05:40:49 UTC,"Perceptualdiff (output attached):
 2545 pixels are different"
1661894,2017-02-05 01:45:46 UTC,Attached is image difference created with IM (compare) based on the command line exports to PNG with Inkscape 0.91 r13725 and Inkscape 0.92.0 r15299 (on OS X 10.7.5).
1661897,2017-02-14 15:23:13 UTC,Potential dupe of https://bugs.launchpad.net/maya/+bug/1443696
1661897,2017-03-13 07:08:26 UTC,"After you've read the elementary OS Stack Exchange link, use the following workaround: enable 2FA in your Google account and use an App Password generated for you."
1661899,2017-02-05 00:05:25 UTC,"After rebooting the sound now works.
No idea why exactly, I had done several previous reboots without effect, but the one after the 'sudo alsa force-reload seems to have worked."
1661899,2017-03-24 09:47:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661904,2017-02-05 02:04:09 UTC,apport information
1661904,2017-02-05 02:04:11 UTC,apport information
1661905,2020-07-05 04:17:30 UTC,[Expired for nvidia-prime (Ubuntu) because there has been no activity for 60 days.]
1661905,2017-08-22 14:22:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661905,2020-05-04 22:04:05 UTC,please specify Ubuntu and nvidia-prime versions if the issue is still reproducible
1661905,2020-05-05 15:41:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:"
1661913,2017-02-06 22:57:07 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1661927,2017-02-07 13:00:56 UTC,"Change abandoned by Davanum Srinivas (dims) (<email address hidden>) on branch: master
Review: https://review.openstack.org/268284
Reason: Retiring nova-docker"
1661927,2017-02-05 07:11:33 UTC,Nova has moved 'arch' to 'fields.Architecture' in https://review.openstack.org/#/c/356067/
1661933,2017-02-28 12:09:41 UTC,I found a workaround at http://askubuntu.com/questions/584922/how-do-i-fix-fonts-not-rendering-and-missing-letters.
1661933,2018-07-19 11:33:42 UTC,"Hello Smihael,
Thank you for submitting this bug and reporting a problem with missing text after suspend in Kubuntu.  You made this bug report some time ago and Kubuntu has been updated since then."
1661933,2019-01-22 07:57:12 UTC,This issues is still a problem for 16.04 with all updates run through 1-20-2019. While I'm running KDE it was also an issue wit Gnome.
1661933,2017-02-05 08:35:55 UTC,See also #1612917
1661943,2017-02-05 23:55:06 UTC,*** This is an automated message ***
1661943,2020-07-04 15:28:05 UTC,Thanks for reporting.
1661954,2017-02-05 13:41:51 UTC,The compilation suceeded.
1661961,2017-02-06 11:41:07 UTC,"Fixed here a while ago:
https://github.com/vzh/geda-gaf/commit/366122fa69785ebc13448e87739f9ad181a39447"
1661961,2019-09-18 12:54:05 UTC,fixed in 331447d2dc013badc6ea15815fd99028efbf7ad9
1661961,2019-10-09 22:15:10 UTC,released in gEDA/gaf 1.10.0
1661963,2017-02-06 23:35:34 UTC,"see discussion at:
https://forum.kicad.info/t/number-of-spokes-in-thermal-relief/5135"
1661966,2017-02-05 19:11:03 UTC,Interesting issue. I will have to discuss this with the team to figure out how to support the use case.
1661969,2019-09-19 15:00:47 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1661969,2017-03-03 12:01:38 UTC,"Dustin,"
1661984,2020-11-20 04:17:22 UTC,[Expired for mozo (Ubuntu) because there has been no activity for 60 days.]
1661987,2017-02-22 20:17:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1661987,2017-02-22 20:34:23 UTC,I think I have the same issue:
1661987,2017-02-22 20:40:15 UTC,There is another commonality: Intel graphics.
1661987,2017-02-23 20:25:54 UTC,"I did a new test with another laptop with Intel graphics and Ubuntu 16.04, but which has an HDMI port, connected to one of the three Samsung TVs, and the colors look fine."
1661987,2017-05-07 20:27:51 UTC,"I have just tried Linux Mint 17.3 on a Dell XPS 13 9350 plus a Samsung TV, no difference as the problem is present there too."
1661987,2017-09-30 15:31:22 UTC,"It affects me too. Dell XPS 9360, tv is a samsung UE32F57000AW
Cable is usb-c to HDMI AUKEY brand (with a sony bravia TV it works).
Active kernel 4.11.0-14-generic, ubuntu version is 16.04.3 LTS."
1661987,2020-10-18 18:31:39 UTC,"I have the same exact problem. I'm running a xps 13 (processor/gpu: intel i7 10510U). I'm using this connector: https://www.dell.com/en-ie/work/shop/dell-adapter-usb-c-to-hdmi-dp-with-power-pass-through/apd/470-aegy/pc-accessories#techspecs_section My monitor is a BenQ EL2870U, I'm using 4K resolution."
1661987,2020-10-18 18:34:04 UTC,I couldn't find a way to edit my comment above. But I should add that I'm running focal fossa (though the same problem was going on in Bionic Beaver):
1661989,2017-02-07 06:18:54 UTC,Note added to the 0.93 release notes (http://wiki.inkscape.org/wiki/index.php/Release_notes/0.93#Important_changes).
1661989,2017-02-07 06:11:16 UTC,"FIxed in lp:inkscape rev. 15487.
Thanks!"
1661989,2017-02-07 02:13:53 UTC,"su_v: No, not at all, cheers for the patch! Was just unassigning myself in case anyone else was getting annoyed by this bug and wanted go ahead with pushing a fix for this while I'm bogged down with working on the Mac 0.92.x builds. :-)"
1661989,2017-02-06 20:11:47 UTC,"@jazzynico - when I noticed the issue a few days ago, I did not know what exact change/commit introduced it, but I ended up with the same conclusion how to have the icons rendered without the solid document background color."
1661989,2017-02-06 19:52:05 UTC,"Patch tested successfully on Xubuntu 16.04, lp:inkscape rev. 15485."
1661989,2017-02-05 17:39:37 UTC,Proposed fix to change opacity of icons.svg page color to 0 confirmed and used independently on Ubuntu 14.04.5 LTS with lp:inkscape (see attached patch; also includes version bump to stop being prompted with dpi change dialog).
1661989,2017-02-07 01:39:22 UTC,"> assignee: 	Tim Sheridan (tghs) → nobody
"
1662003,2017-03-14 12:56:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662003,2017-06-21 12:56:39 UTC,"Hi,
I am being affected too.
REGDOMAIN in /etc/default/crda is manually set to FR, where i'm dwelling !"
1662003,2018-03-26 00:55:53 UTC,This also affects me.
1662003,2018-06-04 11:30:08 UTC,Ubuntu 18.04
1662005,2017-05-22 13:03:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662012,2017-02-15 17:39:05 UTC,"Reviewed:  https://review.openstack.org/429416
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0edc0977aa6e61230655620e9638d4e8e1b85064
Submitter: Jenkins
Branch:    stable/newton"
1662012,2017-04-14 09:24:19 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1662012,2017-02-27 20:28:46 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1662012,2017-02-17 04:57:55 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc2 release candidate.
1662012,2017-02-15 14:38:01 UTC,"Reviewed:  https://review.openstack.org/433932
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b257e5ad45fffbbd90e5e6e9f4b013a9a0b4291b
Submitter: Jenkins
Branch:    stable/ocata"
1662012,2017-02-07 19:32:55 UTC,"Should this stay open, does it need to get merged in all the branches?"
1662012,2017-02-14 21:24:35 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/433932"
1662012,2017-02-07 19:33:31 UTC,"Change abandoned by Sean McCully (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/429416"
1662012,2017-02-07 19:16:47 UTC,This looks like it is very similar to https://bugs.launchpad.net/nova/+bug/1660959 for which the fix https://review.openstack.org/#/c/427667/ was a little less straightforward than we thought (to be complete). I'll comment on the review too.
1662012,2017-02-07 18:52:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430399"
1662012,2017-02-05 21:50:41 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/429416"
1662012,2017-02-15 04:53:22 UTC,"Reviewed:  https://review.openstack.org/430399
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=85c76a7f0827ff8f278d071a0b3f721847079711
Submitter: Jenkins
Branch:    master"
1662022,2017-02-06 12:48:38 UTC,"Not sure how this got tagged as ""Openshot video editor"".  It has nothing to do with Openshot."
1662025,2017-02-09 16:03:59 UTC,"Out of curiosity, I've just tested Disk Image Mounter with ISO's created with Brasero - same issue, all ISO's greater than 2GB produce the 'Value too large for defined data type' error."
1662027,2017-04-18 19:06:37 UTC,"@Paul, because I didn't think of that at the time :) Sorry!"
1662027,2017-04-18 19:14:34 UTC,"Hello Joel, or anyone else affected,"
1662027,2017-04-18 19:15:24 UTC,"Hello Joel, or anyone else affected,"
1662027,2017-09-26 20:01:42 UTC,To all those involved. I am not in the position to test Ubuntu packages as I don't run that myself and my computer doesn't support hardware virtualization.
1662027,2017-09-26 19:29:45 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for zesty for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1662027,2017-04-18 18:50:40 UTC,"@Nish, why didn't you (fake-) synced cacti in Zesty, there were no other delta's?"
1662027,2018-02-20 09:22:21 UTC,The version of cacti in the proposed pocket of Xenial that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1662027,2017-04-22 09:28:24 UTC,This bug was fixed in the package cacti - 0.8.8h+ds1-8ubuntu0.1
1662027,2017-04-18 18:27:19 UTC,"Hello Joel, or anyone else affected,"
1662027,2017-06-27 15:23:16 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1662027,2017-04-17 16:52:54 UTC,"Once we are able to sync the package from Debian in AA, Ubuntu will have the fix and we can SRU."
1662027,2017-04-17 18:03:33 UTC,"I'm uploading the fix for x, y and z now. We can sync in aa once it's open."
1662027,2017-04-11 22:15:30 UTC,"@Paul,"
1662027,2017-04-12 18:58:20 UTC,"Ouch, I forgot about this issue."
1662027,2017-04-12 19:14:25 UTC,"@Paul: I was asking mostly because the upstream changes don't necessarily apply cleanly (the whole commit) because there seems to have been a global move to microtime() in the source. Is that something I should look at SRUing with this change? Or is it sufficient, in your opinion, to just backport the diff in c#2 as a fix for this particular issue?"
1662027,2017-02-06 21:12:37 UTC,Thanks for reporting this issue.
1662027,2017-04-12 19:28:24 UTC,"@Nish, if you want to fix this particular issue, I don't think you need to fix the other uses of explode. I think you could also use explode instead of split."
1662027,2017-04-13 19:33:30 UTC,"Sleeping on it another night makes sense. I understand what I was doing wrong yesterday, I forgot to change the rrd file definition when changing the poller interval."
1662027,2017-04-14 19:15:42 UTC,Bug is now fixed in Debian and unblocked for the upcoming Stretch release.
1662027,2017-04-15 03:30:44 UTC,I will upload the same fix to Ubuntu tonight or tomorrow. Thanks Paul!
1662027,2017-04-12 19:25:14 UTC,"Hmm, I must also admit that I don't fully understand what this feature is for (it doesn't seem to do what I expected)."
1662031,2017-10-06 18:44:30 UTC,Wonder if there is a problem with this code:
1662031,2017-10-10 09:54:07 UTC,I filed https://bugzilla.gnome.org/show_bug.cgi?id=788762 to continue the conversation upstream.
1662031,2017-10-09 07:04:38 UTC,the function has been added to fix https://bugzilla.gnome.org/show_bug.cgi?id=709105
1662031,2017-10-09 04:50:33 UTC,"And I can confirm that the packages in Gunnar's PPA appear to fix the issue here, without any visible regression, from my limited testing."
1662031,2017-10-07 02:03:57 UTC,"Yep, suspicious indeed. I built gdm3 with that function disabled:"
1662031,2017-10-06 23:31:22 UTC,"I added a FOOBAR variable to both ~/.pam_environment and /etc/default/locale, with different values in each file, and after logging in the value is the one from ~/.pam_environment. So I don't think gdm sources /etc/default/locale after ~/.pam_environment. However variables LANG, LANGUAGE and LC_* appear to be overridden by the values in /etc/default/locale, and set_up_session_language() in daemon/gdm-session.c (https://git.gnome.org/browse/gdm/tree/daemon/gdm-session.c#n2488) looks suspicious in that regard."
1662031,2017-10-06 22:15:45 UTC,/usr/share/language-tools/save-to-pam-env is the script that writes to ~/.pam_environment with an incorrect syntax.
1662031,2017-10-06 22:04:01 UTC,"/etc/pam.d/gdm-launch-environment is run as user gdm, so it's not what we're interested in."
1662031,2017-10-06 14:47:44 UTC,In /etc/pam.d/gdm-launch-environment:
1662031,2017-10-06 10:06:23 UTC,"Testing in an up-to-date artful VM, when switching languages in g-c-c, both LANG and LANGUAGE are updated in both ~/.pam_environment and /etc/default/locale."
1662031,2017-10-06 11:23:36 UTC,"To clarify: I used the g-c-c interface to switch language. If I had clicked ""Manage Installed Languages"" to open Language Support and then clicked ""Apply System-Wide"", /etc/default/locale would have been updated too. But that 'does not count'. Language Support is available to work around the fact that installation of new languages from g-c-c does not work currently."
1662031,2017-10-06 11:18:32 UTC,The /etc/default/locale file was not altered when I just tested on an updated artful.
1662031,2017-10-06 10:20:30 UTC,Olivier: Is /etc/default/locale written to also?? That's not what Sebastien and I observed. I'll go to a (relatively) fresh artful install and recheck then.
1662031,2017-09-28 10:48:40 UTC,"If nobody figures out what makes the variables in ~/.pam_environment be overridden by the variables in /etc/default/locale, I'm thinking of an ugly hack which may work."
1662031,2017-07-21 00:34:40 UTC,This issue is present on an artful daily build as well. gdm3 somehow overrides variables set by ~/.pam_environment. (With lightdm it works as expected.)
1662031,2017-02-12 23:00:15 UTC,"Did some testing on zesty. When I had switched to lightdm, language switching between already installed languages worked fine, so gdm3 seems to be the culprit."
1662031,2017-02-07 11:24:10 UTC,(There were some November 2015 commits too but they didn't look important)
1662031,2017-10-11 05:03:13 UTC,"See conversation on the upstream bug report. It turns out calling set_up_session_language() earlier (e.g. in on_setup_complete_cb) doesn't fix the problem: gdm_session_start_session() calls send_environment(), which overrides the environment set up by pam with the values from /etc/default/locale again."
1662031,2017-10-06 11:29:08 UTC,"I didn't click ""Apply System-Wide"". When I changed the language in g-c-c /etc/default/locale was written to (LANG and LANGUAGE were updated). I agree that this is unexpected behaviour though, I wouldn't expect the current user's setting to be applied system-wide unless explicitly requested."
1662031,2017-10-11 15:29:40 UTC,This bug was fixed in the package gdm3 - 3.26.1-3ubuntu2
1662031,2017-02-07 11:22:58 UTC,"Gunnar, thanks for looking into this."
1662034,2017-02-06 05:49:08 UTC,"I disagree with this, for two reasons:"
1662034,2017-02-06 08:49:08 UTC,"In my past experience in designing apps for android and ubuntu phone, all of the templates generate a complete set of files which would generate the final package. In our case, a default ubuntu.png can still be used during the template generation to successfully generate the snap. However, a developer can easily find where to customize and replace the file with his/her own design to make the app's icon unique in the store."
1662035,2017-02-06 00:55:47 UTC,"I suggest to move the actual indentation from each separate ""parameter.cpp"" to extension.cpp instead (there we can indent the whole box consisting of any UI elements a parameter is potentially made of)."
1662035,2017-02-13 23:03:54 UTC,"@Eduard: thank you for doing some code archaeology :)
So documenting them doesn't make sense. Good to know for sure (been looking for gtk calls that involve those variables, but there weren't any I could find)!"
1662035,2017-02-13 21:25:46 UTC,@Maren: Those members date date back to before the beginning of time (i.e. before the bzr repository was created). As far as I can see they're completely unused so we might as well remove them in future...
1662035,2017-02-13 03:21:55 UTC,"@Eduard: in the .cpp files, there are a couple more of those, do you happen to know if they are used at all?"
1662035,2017-02-13 01:55:19 UTC,"I went ahead and pushed an updated version of the patch with the fix for this bug [1].
I also did some more improvements in commits [2-4]."
1662035,2017-02-06 01:01:19 UTC,Adding a quick screenshot of the issue for reference
1662035,2017-02-12 03:08:56 UTC,"(no comment on the patch, but thanks for highlighting the attribute - it's documented now :) )"
1662035,2017-02-11 23:28:53 UTC,Any comments on the patch?
1662035,2017-02-07 22:34:32 UTC,Here's a first version of a patch for this issue.
1662035,2017-02-06 08:53:04 UTC,"No problem, you can work on it. Thanks!"
1662035,2017-02-12 03:45:43 UTC,"Thanks ;)
Had that on my todo list but wanted to wait for the patch to land (as it determines for which elements this parameter is actually valid)."
1662042,2018-01-21 11:53:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662046,2017-02-06 08:58:04 UTC,"Hmm, no seems like a bug. The nested server provides a compositor report during passthrough so it should be possible to reinstate MIR_CLIENT_PERF_REPORT for it too."
1662046,2017-11-03 16:36:03 UTC,Syncing task from Mir.
1662047,2018-01-12 19:03:04 UTC,Unassigning due to no activity for > 6 months.
1662057,2017-02-06 05:34:10 UTC,"I've linked a branch, but note my one concern there in the description. Perhaps this is something specific to my juju2 env, though I don't see from the code how."
1662057,2017-02-06 12:37:13 UTC,"This is the same bug as lp:1572575, bug applied to a different branch."
1662058,2017-02-06 04:16:53 UTC,"The bug is related with https://bugs.launchpad.net/python-openstackclient/+bug/1661814 ,  I will try to fix #2 first."
1662058,2017-02-06 07:20:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/429534"
1662058,2017-02-06 07:48:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/429545"
1662058,2017-02-13 16:50:03 UTC,"Reviewed:  https://review.openstack.org/429545
Committed: https://git.openstack.org/cgit/openstack/python-designateclient/commit/?id=d4cf5d3dd597127d6b38c6ee38b0c9d66faae871
Submitter: Jenkins
Branch:    master"
1662058,2017-02-06 08:21:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/429562"
1662058,2017-02-07 18:32:17 UTC,"Reviewed:  https://review.openstack.org/429548
Committed: https://git.openstack.org/cgit/openstack/python-saharaclient/commit/?id=ec8ff32d24f14acfd634ea1d51c4facd40d8a14e
Submitter: Jenkins
Branch:    master"
1662058,2017-02-08 03:55:50 UTC,"Reviewed:  https://review.openstack.org/429562
Committed: https://git.openstack.org/cgit/openstack/python-zaqarclient/commit/?id=35404c7a741d919afbd74fcd268affccc7df10d2
Submitter: Jenkins
Branch:    master"
1662058,2017-02-08 07:36:24 UTC,"It's not easy thing to fix in openstacksdk, maybe trigger the related bugs [1][2], need to dive deep in code."
1662058,2017-02-06 07:57:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/429548"
1662058,2017-02-22 22:51:31 UTC,"Reviewed:  https://review.openstack.org/436820
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=10f0300f704ca8dd5928d9a8b41ac6c16732f203
Submitter: Jenkins
Branch:    master"
1662058,2017-02-22 08:27:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436820"
1662058,2017-03-28 07:50:17 UTC,"We do a workaround in python-openstackclient side https://review.openstack.org/436820 , python-openstacksdk version had been shown in ""module list"", mark bug status as Opinion."
1662058,2017-02-22 08:29:37 UTC,"Don't find good way to add __version__ for openstacksdk and avoid bug https://bugs.launchpad.net/python-openstacksdk/+bug/1588823 both, so fix the issue in OSC side, patch is https://review.openstack.org/436820"
1662058,2017-03-28 07:44:39 UTC,"Now only cinderclient module can't be shown when we execute ""openstack module list"", it's not easy to fix because of module lazy-loading."
1662058,2017-03-28 07:46:59 UTC,"We can get cinderclient version in openstackclient interactive mode if we run a volume related commands once, like: volume list"
1662058,2017-03-28 03:54:57 UTC,"Reviewed:  https://review.openstack.org/429534
Committed: https://git.openstack.org/cgit/openstack/python-barbicanclient/commit/?id=10209c5e5296ac0222bde4ddd0849a18e1c1155e
Submitter: Jenkins
Branch:    master"
1662066,2017-02-06 22:58:40 UTC,"I'm a little on the fence about this one personally. It seems like a workaround for not setting ""Auto show when editing text"" in Onboard"
1662077,2017-03-13 12:16:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444859"
1662077,2017-03-14 00:43:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445259"
1662077,2017-03-14 00:44:13 UTC,"Change abandoned by haobing (<email address hidden>) on branch: master
Review: https://review.openstack.org/444859"
1662077,2017-03-16 04:29:10 UTC,"Reviewed:  https://review.openstack.org/445259
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=5c8f7c285f6ce335922280b473e16e7c1f6929cb
Submitter: Jenkins
Branch:    master"
1662078,2017-02-10 16:03:44 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1662078,2017-03-12 12:25:38 UTC,Run dmesg and if you see a message:
1662078,2017-02-06 06:30:20 UTC,This change was made by a bot.
1662078,2017-02-06 19:46:02 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1662078,2017-02-07 18:51:07 UTC,"No, the system was new and I installed a fresh copy of lubuntu 16.10 (as ubuntu was too slow - used live boot). I tried different versions of ubuntu and fedora but all had the same problem."
1662079,2017-02-09 18:17:16 UTC,"This issue has not been observed in R3.2-22, so marking as Fix-Committed"
1662079,2017-03-21 19:04:51 UTC,mainline there is different kernel version and it supported differently
1662090,2017-02-06 10:01:52 UTC,Is anyone else having issues?
1662090,2017-02-06 10:05:30 UTC,"I'm also getting ""TLS-fel: error:140E0197:SSL routines:SSL_shutdown:shutdown while in init"""
1662090,2017-02-06 10:08:12 UTC,Could you give more information about the issues? How to reproduce them?
1662090,2017-02-06 11:05:15 UTC,One crash was in the night so i have no idea. One occurred when i added a bundle and after it stated downloading the client crashed.
1662090,2017-02-07 21:01:27 UTC,No one else?
1662090,2017-02-11 12:54:08 UTC,i have the same problem
1662090,2017-02-11 14:07:16 UTC,just get a crash related to SSL
1662090,2017-02-11 16:43:33 UTC,"Ok, I've pushed a new build with an older version of OpenSSL. Maybe Night has ideas about resolving the crashes."
1662094,2017-02-06 23:55:04 UTC,*** This is an automated message ***
1662094,2017-02-06 10:20:23 UTC,Uploaded to zesty new queue
1662109,2018-02-13 09:25:24 UTC,"Since quite long time I can't find such issues in the gate.
If it will happen again we can probably reopen this bug or report new one and work on it again."
1662109,2017-11-04 22:40:25 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/491244
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1662109,2017-09-06 23:21:13 UTC,"Reviewed:  https://review.openstack.org/497928
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9f88a3ab05f472f760b228a0bd7549f38e414e43
Submitter: Jenkins
Branch:    stable/ocata"
1662109,2017-08-25 12:24:27 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/497928"
1662109,2017-08-06 14:09:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491244"
1662109,2017-08-01 20:22:42 UTC,"Reviewed:  https://review.openstack.org/468326
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fe0bb07113a00a4d8a56dc08b004bf758c505e4b
Submitter: Jenkins
Branch:    master"
1662109,2017-08-01 06:56:55 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/488855
Reason: It's duplicate of https://review.openstack.org/#/c/468326"
1662109,2017-06-16 02:57:23 UTC,"Reviewed:  https://review.openstack.org/471620
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1df1508d6b4abb27feda64c5401d5d986f88afd7
Submitter: Jenkins
Branch:    stable/ocata"
1662109,2017-06-07 08:03:50 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/471620"
1662109,2017-06-02 19:22:27 UTC,"Reviewed:  https://review.openstack.org/463268
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8528ea2b0e45379ce29ba6e1cfe17c5ae4197592
Submitter: Jenkins
Branch:    master"
1662109,2017-05-26 09:17:39 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/468326"
1662109,2017-05-08 07:51:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463268"
1662109,2017-02-06 09:54:57 UTC,"Ok, I'm taking this one. The test seems to progress, but the progress is slow and it seems to exceed the total timeout."
1662109,2017-03-27 23:22:10 UTC,"Reviewed:  https://review.openstack.org/448020
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=61183804bf81225f2177277639ed3e8b1d15c27e
Submitter: Jenkins
Branch:    stable/ocata"
1662109,2017-04-14 09:18:00 UTC,This issue was fixed in the openstack/neutron 11.0.0.0b1 development milestone.
1662109,2017-02-07 15:23:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430309"
1662109,2017-02-07 15:41:52 UTC,"2017-02-05 16:46:08,109 12021 DEBUG    [neutron.tests.tempest.scenario.test_qos] time_elapsed =  8,total_bytes_read = 86508,cycle_data_read = 86508
2017-02-05 16:46:08,550 12021 DEBUG    [neutron.tests.tempest.scenario.test_qos] time_elapsed =  0,total_bytes_read = 1048576,cycle_data_read = 962068"
1662109,2017-02-15 06:36:58 UTC,"Reviewed:  https://review.openstack.org/430309
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b7213030fd59c6169b9a2d4cb9680cf5adbfe6d8
Submitter: Jenkins
Branch:    master"
1662109,2017-02-16 14:09:25 UTC,"hmm, there's still something wrong down there
2017-02-16 12:10:11,685 12786 DEBUG    [neutron.tests.tempest.scenario.test_qos] time_elapsed = 0, total_bytes_read = 1048576, bytes_per_second = 1650318"
1662109,2017-02-16 13:40:57 UTC,It seems we still suffer from this issue: http://logs.openstack.org/47/416647/5/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/330522c/logs/testr_results.html.gz
1662109,2017-02-22 14:50:21 UTC,Looking at the logs of the agent here:
1662109,2017-02-22 14:57:15 UTC,The server request for QoS policy association is: http://logs.openstack.org/07/436307/1/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/342948d/logs/screen-q-svc.txt.gz#_2017-02-22_06_31_58_211
1662109,2017-02-22 16:20:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/437011"
1662109,2017-02-23 01:37:30 UTC,"Reviewed:  https://review.openstack.org/437011
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e674034aa1d33ae5aa65ac7b809ca5dd4c2867c5
Submitter: Jenkins
Branch:    master"
1662109,2017-03-21 11:43:33 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/448020"
1662109,2017-02-22 12:58:44 UTC,Still failing: http://logs.openstack.org/07/436307/1/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/342948d/logs/testr_results.html.gz
1662126,2017-11-03 16:30:12 UTC,Syncing task from Mir.
1662131,2018-03-14 14:44:16 UTC,The tap interface is down during a softreboot whereas it is up during an hardreboot.
1662139,2017-02-06 13:07:54 UTC,That exception happens in keystoneauth1.
1662139,2017-02-07 03:48:40 UTC,"I'm not sure what's the root reason, and why regular pip install is ok, I want to debug openstackclient code with the latest openstacksdk in editable mode, but it's not available, in my memory, it worked in mitaka release."
1662139,2017-02-07 13:48:41 UTC,"We haven't touched anything relating to pbr as far as I know in a long time, and if I could I would just remove it entirely. I'm not really sure what the problem could be."
1662139,2017-02-07 14:40:02 UTC,I agree with Brian. I wonder if this is related at all to bug 1662266
1662139,2017-02-08 07:40:49 UTC,"I'm trying to fix bug https://bugs.launchpad.net/python-openstacksdk/+bug/1662058 , worried about the fix might trigger bug https://bugs.launchpad.net/python-openstacksdk/+bug/1588823 , I saw that fix move __version__ out of openstack.__init__.py explicitly."
1662142,2017-03-30 07:45:35 UTC,"Change abandoned by Simon Pasquier (<email address hidden>) on branch: stable/0.9
Review: https://review.openstack.org/433617
Reason: stable/0.9 is EOL."
1662142,2017-02-21 08:31:10 UTC,"Reviewed:  https://review.openstack.org/436074
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-lma-collector/commit/?id=f61071aca603da3c93804d34e8586bd67b3efd76
Submitter: Jenkins
Branch:    stable/1.0"
1662142,2017-02-14 12:21:42 UTC,"Fix proposed to branch: stable/0.9
Review: https://review.openstack.org/433617"
1662142,2017-02-14 11:05:45 UTC,"Reviewed:  https://review.openstack.org/431565
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-lma-collector/commit/?id=bc797dfb4bdb091627226cf058469f0787fa284c
Submitter: Jenkins
Branch:    master"
1662142,2017-02-09 14:13:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/431565"
1662142,2017-02-20 15:43:35 UTC,"Fix proposed to branch: stable/1.0
Review: https://review.openstack.org/436074"
1662145,2017-02-27 02:39:31 UTC,"Further to comment #12, I've noticed in a few other bug reports people are experiencing rendering glitches in Qt apps that should only happen with Xmir. So we seem to have a problem with our own Qt apps incorrectly choosing X(mir) when native Mir is available and should be used instead."
1662145,2017-03-09 10:07:41 UTC,"> Also very important that those apps (toolkits) choose native Mir over
> X when both are available.
Qt isn't designed to make the choice itself, it expects to be told if either X or Mir should be used.
"
1662145,2017-02-28 14:54:54 UTC,"They should add mir, yeah.  No need to replace unity8, necessarily [1]."
1662145,2017-02-28 14:38:31 UTC,"Does that mean that apps that plug to the ""unity8"" iface should be updated to plug to ""mir"" now?"
1662145,2017-02-28 14:04:50 UTC,Agreed.  I was just trying to highlight that an app that used to work as Mir might now be run under XMir because we switched which interface we look at.
1662145,2017-02-28 01:24:34 UTC,"Sure, it's important to offer both X and Mir sockets to all apps."
1662145,2017-02-27 13:37:58 UTC,"Daniel, that may be because now we choose whether to use xmir or not based on the presence of the 'mir' interface (used to be the 'unity8' interface).  Not all apps may plug into that interface."
1662145,2017-02-23 16:08:04 UTC,Seemed to have been fixed with develop rc_proposed but then the wifi broke!
1662145,2017-02-10 14:09:36 UTC,"The log file makes this look like an app that is exporting the unity7 interface as well as the unity8 one. But the snapd in zesty doesn't have a unity8 interface. So we're starting it as a unity7 app. It is not realizing this and trying to connect to Mir, even after we've setup XMir for it."
1662145,2017-02-23 15:53:55 UTC,Is this still happening?
1662145,2017-02-10 01:34:03 UTC,I understand. Unfortunately we're hitting new launch failure bugs every few days now. So the launch failure one logged days ago might not be the same bug experienced today.
1662145,2017-02-09 13:56:23 UTC,"This is not the original issue, but yesterday I switched the unity8 snap to use a different, more standard path (/run/user/xxx/mir_socket) for the socket."
1662145,2017-02-09 09:11:19 UTC,"Also, the problem is not Mir, despite the error message."
1662145,2017-02-09 08:54:36 UTC,This is not a snap or Unity8 bug. The same platform-api apps fail with the same error under Mir demo servers too.
1662145,2017-02-07 08:57:15 UTC,These messages are shown in the journal:
1662145,2017-02-07 08:49:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662145,2017-02-06 11:36:29 UTC,same journalctl without apparmor ALLOWED spam
1662148,2018-02-05 17:56:33 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/430060
Reason: No response for several months. Feel free to restore and address comments if you wish to pursue."
1662148,2017-02-07 05:00:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430060"
1662148,2017-02-06 11:40:43 UTC,"As per the previous bug https://bugs.launchpad.net/cinder/+bug/1658888 filed against HPE 3PAR driver. Cause of failure is, multiple threads are trying to enter in initialize_connection OR terminate_connection method at the same time which leads to an above error."
1662148,2017-09-01 16:16:46 UTC,Unassigning due to no activity for > 6 months.
1662153,2017-02-09 13:46:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662153,2017-08-17 07:31:52 UTC,No installation possible
1662158,2017-02-14 11:11:36 UTC,"Reviewed:  https://review.openstack.org/431600
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=38f91bf47c3528874dc21b89f49ea7a1571d3cdf
Submitter: Jenkins
Branch:    master"
1662158,2017-02-27 16:28:42 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1662158,2017-02-09 15:23:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/431600"
1662158,2017-02-07 11:36:55 UTC,"Reviewed:  https://review.openstack.org/429676
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=3f2d12264350c4a3abac4047376fc730bacf6d60
Submitter: Jenkins
Branch:    master"
1662158,2017-02-07 15:43:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/430319"
1662158,2017-02-06 12:39:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/429676"
1662158,2017-02-08 15:09:50 UTC,"Reviewed:  https://review.openstack.org/430319
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=0852485f3c2b452628d22d16d300903a52260754
Submitter: Jenkins
Branch:    master"
1662159,2017-02-06 15:32:01 UTC,"Hi Janie,"
1662159,2017-02-06 16:45:28 UTC,"It happens with Curl as well (not related to the client side)
The bug appears without slo/dlo.
The socket becomes a zombie and will stay forever in the CLOSE_WAIT state (no reuse)"
1662159,2017-02-07 07:02:40 UTC,"If I artificially add a sleep somewhere in the upload of objects (simulating a slower upload over network), then I see that it can seem like these connections are never going to close.  If I add enough sleep time, it can take too long to wait for all connections to complete.  So I am not convinced that I have been able to reproduce a situation where the connections can be stuck in a CLOSE_WAIT state."
1662159,2017-02-07 16:29:03 UTC,"$ cat proxy-server.conf | grep node_timeout | head -n 1
node_timeout = 10"
1662159,2017-02-27 13:35:29 UTC,"Change abandoned by Jean Caron (<email address hidden>) on branch: master
Review: https://review.openstack.org/429697
Reason: new patch at https://review.openstack.org/#/c/437321"
1662159,2017-02-06 15:11:20 UTC,"Hello Jean.  I have tried to reproduce this against the latest code from master (I made sure to use an EC policy), and I have not yet.  I used the same commands you did.  I see the "" Client disconnected without sending enough data"" in my proxy.error log.  But after the timeout, there were no 'CLOSE_WAIT' connections.  How large was your ./slo file?"
1662164,2017-02-10 00:40:20 UTC,Hi Dan - Thanks so much for attaching the debdiff!
1662164,2017-03-29 15:42:38 UTC,I've unsubscribed ubuntu-security-sponsors.
1662164,2017-02-07 12:33:42 UTC,"The attachment ""ldapscripts_2.0.6-1ubuntu2.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1662164,2017-02-07 00:30:53 UTC,"Thanks Dan, it looks like this was introduced with a switch from cdbs to dh packaging formats in Debian version 2.0.6-1 and fixed in Debian version 2.0.7-2. This patch appears to be sufficient to fix the issue:"
1662164,2017-02-07 00:02:10 UTC,"12.04 LTS:
-rw-r----- 1 root root 6 Jan 30  2012 /etc/ldapscripts/ldapscripts.passwd"
1662164,2017-02-07 10:17:27 UTC,I think this is what is required...
1662166,2017-11-03 18:43:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662168,2019-12-18 16:51:00 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/429762
Reason: This repo is retired now, no further work will get merged."
1662168,2018-07-20 07:33:53 UTC,"As a workaround, I have reverted to jsonschema 2.3.0. Let know once the issue is addressed for 2.6"
1662168,2018-07-20 07:30:19 UTC,"Hi,
I still face this dependency issue after installing latest jsonschema (using pip install jsonschema). On doing import, it complains of missing functools32 dependency. Can you please check the same?"
1662168,2017-03-15 14:39:41 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/445989"
1662168,2017-04-05 13:24:05 UTC,"Verified on 10.0 #1568
Tests are passed, problem is gone.
https://ci.fuel-infra.org/job/gate-fuel-library-tasks/3328/"
1662168,2017-03-20 14:53:28 UTC,"Change abandoned by Mykyta Karpin (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/445989
Reason: this is not needed because tasks job is disabled on ocata branch"
1662168,2017-02-08 09:09:59 UTC,Tasklib related test has been disabled in master. For additional information see https://bugs.launchpad.net/fuel/+bug/1662169
1662168,2017-02-06 16:03:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/429762"
1662168,2017-02-07 14:02:23 UTC,"Reviewed:  https://review.openstack.org/429763
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=6dae4ff79360dccfc63ecb2ed2e9596867a347ce
Submitter: Jenkins
Branch:    stable/8.0"
1662168,2017-02-07 13:57:08 UTC,"Reviewed:  https://review.openstack.org/429686
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=9450c56304a51e65959f5a6687747929aef17a31
Submitter: Jenkins
Branch:    stable/7.0"
1662168,2017-02-07 10:37:30 UTC,"Reviewed:  https://review.openstack.org/429717
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=520ff0ba9291c16283ac59c4f60c504d24551c3c
Submitter: Jenkins
Branch:    stable/mitaka"
1662168,2017-02-06 16:04:45 UTC,"Fix proposed to branch: stable/8.0
Review: https://review.openstack.org/429763"
1662168,2017-02-06 16:02:59 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/429760"
1662168,2017-02-06 14:08:31 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/429717"
1662168,2017-02-06 13:07:26 UTC,"Fix proposed to branch: stable/7.0
Review: https://review.openstack.org/429686"
1662168,2017-02-08 09:00:40 UTC,"Reviewed:  https://review.openstack.org/429760
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=3ce37b120cc0f34b2830190991f4f9755eed1336
Submitter: Jenkins
Branch:    stable/newton"
1662169,2017-02-06 13:13:47 UTC,"Reviewed: https://review.fuel-infra.org/30516
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1662169,2017-02-06 13:10:10 UTC,"Fix proposed to branch: master
Change author: Stanislaw Bogatkin <email address hidden>
Review: https://review.fuel-infra.org/30516"
1662172,2017-02-06 13:32:02 UTC,"I just noticed that kubectl is not present in ~/bin, even though the last step of conjure-up kubernetes claimed to take care of that..."
1662172,2017-02-06 13:59:43 UTC,Please ignore my last comment.
1662172,2017-02-08 15:13:48 UTC,Thanks for the updates Alexander. We'll look into getting this implemented. Also we're switching to a pure snap distribution and a lot of the steps can be omitted. For this article though I approve the changes with a small fix:
1662172,2017-02-08 15:52:24 UTC,"Adam, thanks for the quick response."
1662172,2017-02-09 17:51:06 UTC,"Hi Alexander,"
1662173,2017-08-25 14:36:07 UTC,"Change abandoned by Dmitry Teselkin <email address hidden> on branch: 9.0
Review: https://review.fuel-infra.org/30445"
1662173,2017-08-25 14:35:57 UTC,"Change abandoned by Dmitry Teselkin <email address hidden> on branch: 9.0
Review: https://review.fuel-infra.org/31019"
1662173,2017-03-21 13:44:22 UTC,Fixed by https://review.fuel-infra.org/#/c/32199/
1662173,2017-02-09 13:10:18 UTC,"1. Stderr should be closed in init-script or in mysqld_safe.
2. SaltStack should check for process death."
1662173,2017-02-17 17:11:26 UTC,"Fix proposed to branch: 9.0
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/31019"
1662173,2017-02-09 13:03:28 UTC,I've reproduced it. Mistake both in Salt and init script.
1662173,2017-02-09 12:37:20 UTC,Couldn't reproduce into clean docker image. Need more data.
1662173,2017-03-21 13:44:15 UTC,https://review.fuel-infra.org/#/c/32199/
1662174,2017-02-08 17:06:32 UTC,"The openstack CLI reference link on https://github.com/openstack/designate/blob/stable/mitaka/doc/source/howtos/manage-domains.rst
is indeed broken."
1662174,2017-03-13 17:13:12 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/445019"
1662174,2017-07-05 07:59:32 UTC,"Change abandoned by Joshua Hesketh (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/445019
Reason: This branch (stable/mitaka) is at End Of Life"
1662174,2017-11-06 23:55:32 UTC,This bug seems outdated. In current master I could not find any reference to https://github.com/openstack/designate/blob/stable/mitaka/doc/source/howtos/manage-domains.rst
1662193,2017-02-08 19:53:08 UTC,output from lsusb -v:
1662198,2017-02-06 17:32:25 UTC,"On Ubuntu 14.04.5 LTS:
- not reproduced with Inkscape 0.92+devel r15470
- reproduced with Inkscape 0.92+devel r15481"
1662198,2017-02-06 19:41:43 UTC,"Could you please give details on the disappearing attributes? I'm trying to test with some simple steps, but I don't manage to reproduce the bug on Xubuntu 16.04, with lp:inkscape rev. 15485."
1662198,2017-02-06 20:25:14 UTC,"Steps to reproduce:
1) launch inkscape trunk (default new prefs, default new document)
2) create a simple text
3) select the text, change the fill color to 'red'
4) convert text to path (Shift+Ctrl+C)
5) ungroup"
1662198,2017-02-06 21:14:06 UTC,The svg filters disappeared too
1662198,2017-02-09 08:26:53 UTC,Not reproduced with lp:inkscape r15497 on Ubuntu 14.04 - seems one of the recent commits fixed this. @ivan - can you confirm?
1662211,2019-09-09 04:21:31 UTC,"This is a very old report and I can no longer reproduce this locally
under stress with a few hundreds runs. My guess is that the intermittent
failure was addressed as part of the work that we have done since this
bug was filed."
1662216,2017-02-21 18:30:46 UTC,Fix committed in revision 329
1662216,2017-02-06 15:55:26 UTC,P.P.S. I'm using the latest libecbufr version 0.8.7.
1662219,2017-02-06 15:58:59 UTC,"Fix proposed to branch: master
Change author: Mykyta Karpin <email address hidden>
Review: https://review.fuel-infra.org/30530"
1662219,2017-02-07 09:31:50 UTC,"Reviewed: https://review.fuel-infra.org/30530
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1662220,2017-02-06 16:46:02 UTC,Can it be reproduced with ActionSelectionPopover too? That is the base component of the ListItemPopover.
1662228,2018-03-06 17:19:53 UTC,Hi! Unassigning this bug after nearly 2 months of inactivity.
1662228,2018-03-08 09:35:22 UTC,"The solution is straightforward, but the change will break quite amount of unit tests, I wonder if it worth the efforts, or if there is any decent way to achieve it."
1662228,2018-05-11 10:33:58 UTC,"I'd have thought the unit tests could be fixed by a single sed for the triple backslashes? This is a pain in the ass for any API consumers (clients, UIs) as you end up indefinitely carrying a hack on Ironics error messages."
1662229,2018-10-08 11:40:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662229,2018-10-08 16:41:37 UTC,"I had almost the same apt.log contents, but before the ""Broken"" list there were some lines like the following:"
1662234,2017-04-28 22:02:46 UTC,Was any authentication information set in the environment or via clouds.yaml?
1662234,2017-10-04 06:49:06 UTC,"I have installed python-openstackclient 3.12.0, it is giving me the same error. I used environment variables on macOS to set auth info."
1662239,2019-08-01 17:38:16 UTC,"@Ian, I think ""preview"" is the right term.  It is *not* page settings because it doesn't save them in the WKS file; they're only used to draw the Preview mode (see the icons in the toolbar)."
1662239,2019-08-01 16:51:17 UTC,"@Jeff, is preview really the right word to use in this dialog name? I just spent around 10 minutes trying to understand what ""preview settings"" meant versus the original ""page settings"" name. I think this should still be called page settings for consistency (since that is what the window is called in Eeschema and Pcbnew), but text should be added in the dialog to say that these are not stored in the worksheet file and are display only (like a 1-2 lines of text at the top)."
1662239,2019-07-10 22:16:42 UTC,Moved Page Settings dialog to near the real/preview mode switches and edited the tooltip and headings to make it clearer they were just preview data.
1662239,2019-05-27 14:52:07 UTC,Fair enough.  The page layout format is size-independent.  We should definitely document this clearly in the theory of operations section of Pl_Editor's doc file.
1662239,2018-08-07 23:14:26 UTC,"Huh.  I take back my earlier response.  I can recreate this, so I must have been testing something separate."
1662239,2018-08-08 02:51:10 UTC,"You're right, they are not stored.  However, I think they should be.   As it requires a file format change, I've tentatively targeted it for v6."
1662239,2018-08-08 02:10:58 UTC,"@Seth: Sorry for the noise: Actually I *think* this bug is ""wont'fix"" bcs. none of the page settings [attachment]) are put in the kicad_wks file."
1662239,2018-08-07 22:29:15 UTC,This is still present / reproducible.
1662239,2018-06-09 14:23:24 UTC,I don't observe this with recent master (or with 4.0.7).  Is this issue still occurring for you?
1662239,2019-05-27 11:21:36 UTC,"Page settings and title block info are never stored in .wkas files, because they are living in .kicad_pcb and .sch files."
1662242,2017-06-20 14:42:29 UTC,"I can observe the issue, but I cannot reproduce it consistently. Sometimes it will restart, sometimes it won't. It seems it restarts more often after unchecking the checkbox than after checking it."
1662257,2020-02-19 22:51:34 UTC,This bug is related to loading GTK2+ style assets. MATE Panel was ported to GTK3+ for 1.18 and this issue will not be fixed since MATE 1.12 is no longer supported.
1662258,2017-05-08 18:12:35 UTC,Super annoying and still happening on 16.04.
1662265,2017-03-27 21:12:38 UTC,"I worked around this issue by using ""list-sessions"" to work out if there are any open sessions, then calling the appropriate command:"
1662274,2019-09-19 12:02:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1662275,2020-02-19 22:51:49 UTC,This bug is related to loading GTK2+ style assets. MATE Panel was ported to GTK3+ for 1.18 and this issue will not be fixed since MATE 1.12 is no longer supported.
1662289,2017-04-10 15:25:32 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: master
Review: https://review.openstack.org/435413"
1662289,2017-03-29 16:09:12 UTC,"Reviewed:  https://review.openstack.org/441919
Committed: https://git.openstack.org/cgit/openstack/networking-ovs-dpdk/commit/?id=55691f54c61df5792353091ee7f933e82d7ac080
Submitter: Jenkins
Branch:    master"
1662289,2017-02-06 18:50:36 UTC,this should be completed before the ocata branch is created.
1662289,2017-02-17 14:21:26 UTC,jarek when addressing this make sure it support both forms.
1662289,2017-03-06 09:04:03 UTC,https://review.openstack.org/#/c/435413/
1662291,2017-02-06 18:52:52 UTC,depends on https://bugs.launchpad.net/networking-ovs-dpdk/+bug/1662289
1662291,2017-03-29 16:09:05 UTC,"Reviewed:  https://review.openstack.org/441919
Committed: https://git.openstack.org/cgit/openstack/networking-ovs-dpdk/commit/?id=55691f54c61df5792353091ee7f933e82d7ac080
Submitter: Jenkins
Branch:    master"
1662292,2017-03-03 08:40:51 UTC,The message into journal and messages has been added that indicates that the node is bootstrapped and how to work with it
1662292,2018-01-18 08:30:56 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1950
1662294,2018-02-28 10:17:59 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1662294,2018-03-01 22:40:23 UTC,"Marking as Invalid because the release is EOL is not correct. Marking as Incomplete. Also, 18.04 is (at the time of writing) still in development, and you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29"
1662294,2018-03-25 15:59:04 UTC,Effect also 17.10 as well. It is a shame that bugs are automatically closed with new releases without having actually been fixed.
1662296,2017-09-20 14:37:46 UTC,"That's not something we are going to fix this cycle, updating the tag according"
1662296,2017-04-28 14:15:06 UTC,This is wider than Unity.
1662296,2017-04-11 05:22:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662297,2017-02-06 19:54:50 UTC,"+1 to templates.  As noted in IRC, this may require other changes (build/tools/make_release comes to mind) to ensure Grunt commands execute after ./configure."
1662297,2019-05-14 19:23:52 UTC,"Hard-coded paths exist in Angular as well as AngularJS, see Open-ILS/src/eg2/karma.conf.js."
1662297,2019-08-01 21:51:55 UTC,Working branch user/jeffdavis/lp1662297-no-hardcoded-install-path has a fix:
1662299,2017-02-07 20:46:40 UTC,Les versions MacOs mises à disposition ne sont pas produites comme celles de Windows et Linux pour lesquelles une vraie compilation à destination de ces systèmes est faite.
1662299,2017-02-07 21:20:06 UTC,Merci pour ces informations
1662299,2017-06-08 19:28:08 UTC,"Nous venons d'achever nos travaux pour générer une vraie version de BellePoule pour Mac :
http://betton.escrime.free.fr/documents/BellePoule/bellepoule_4_35_1.zip"
1662299,2017-06-11 16:46:06 UTC,"> Bonjour,
> Je vais regarder mais la saison étant finie, je ne peux trop tester mais je vais faire quelques tests.
> Merci de m’avoir prévenu.
> Le 8 juin 2017 à 21:28, betonniere <email address hidden> a écrit :
>
> Nous venons d'achever nos travaux pour générer une vraie version de BellePoule pour Mac :
> http://betton.escrime.free.fr/documents/BellePoule/bellepoule_4_35_1.zip
>
> Avant de la rendre publique, nous souhaiterions nous assurer qu'elle fonctionne correctement.
> Pouvez-vous l'essayer et nous remonter les anomalies que vous pourriez rencontrer ?
>
> ----- Mail original -----
>
> De: ""Benoit Richard"" <email address hidden>
> À: ""bellepoule dev"" <email address hidden>
> Envoyé: Mardi 7 Février 2017 22:20:06
> Objet: Re: [Bug 1662299] Re: Problème sous Mac OS Sierra
>
> Merci pour ces informations
>
> BR
>> Le 7 févr. 2017 à 21:46, betonniere <email address hidden> a écrit :
>>
>> Les versions MacOs mises à disposition ne sont pas produites comme
>> celles de Windows et Linux pour lesquelles une vraie compilation à
>> destination de ces systèmes est faite.
>>
>> Les versions MacOs ne sont pour le moment qu'une encapsulation des versions Windows pour être exécutées au dessus d'un adaptateur Windows/MacOs (Wine en l'occurence).
>> La version Sierra n'est pas encore proposée pour de simple raisons logistiques. Il faut procéder à cette encapsulation soi même.
>>
>> Pour cela il faut installer WineBottler sur le Mac puis lancer la
>> version Windows de BellePoule à partir de Wine (inclus dans
>> WineBottler).
>>
>> La manip n'est pas très compliquée en soi, mais elle n'est que
>> temporaire. A terme, MacOs aurra également sa propre version sans avoir
>> à faire tout ceci.
>>
>> ** Changed in: bellepoule
>> Importance: Undecided => Medium
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1662299
>>
>> Title:
>> Problème sous Mac OS Sierra
>>
>> Status in BellePoule:
>> Triaged
>>
>> Bug description:
>> Bonjour,
>> Je n'arrive pas à utiliser Belle-Poule (Super Logiciel) sous Mac OS sierra.
>> Lorsque je le lance, il se ferme directement.
>>
>> Je l'utilise régulièrement avec une autre version de l'OS.
>>
>> Cordialement
>> (Merci pour ce logiciel)
>> BR
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/bellepoule/+bug/1662299/+subscriptions
>
> Benoît Richard
> Gestion Licences Haute - Normandie
> 89 Rue de la Marne
> 27200 Vernon
> Tel : 0611376576
>
> --
> You received this bug notification because you are subscribed to
> BellePoule.
> Matching subscriptions: Betonniere
> https://bugs.launchpad.net/bugs/1662299
>
> Title:
> Problème sous Mac OS Sierra
>
> Status in BellePoule:
> Triaged
>
> Bug description:
> Bonjour,
> Je n'arrive pas à utiliser Belle-Poule (Super Logiciel) sous Mac OS sierra.
> Lorsque je le lance, il se ferme directement.
>
> Je l'utilise régulièrement avec une autre version de l'OS.
>
> Cordialement
> (Merci pour ce logiciel)
> BR
>
> To manage notifications about this bug go to:
> https://bugs.la...
"
1662299,2017-06-27 11:42:24 UTC,"Bonjour,
J’ai fait quelques simulations (sans importer de fichiers et noms).
Pas de problèmes apparents."
1662303,2017-02-07 10:12:34 UTC,devstack has a function that re-export HTTP_PROXY variables when calling sudo pip install. Unfortunately it can't be used by Gnocchi since the upper-constraint might break it at any point.
1662303,2017-02-07 10:39:51 UTC,"Ok, thanks, this is better solution."
1662314,2017-02-18 12:49:52 UTC,I've seen the same problem on my system. Calling exit from a dhclient hook causes dhclient to stop processing the other hooks in the directory.
1662314,2017-02-18 12:50:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662316,2017-09-21 05:58:59 UTC,"It's better to send a mail to Chris Chiu <email address hidden> and Carlo Caione <email address hidden>, they wrote the hotkey/brightness part for hid-asus."
1662316,2018-02-02 10:38:31 UTC,Kernel 4.15 enables keyboard backlight control for me (GL553VE). No more kernel patching needed.
1662316,2017-11-16 12:53:50 UTC,"I opened it , thanks!"
1662316,2017-11-14 05:34:59 UTC,"R.Erol, please file a separate bug, thanks!"
1662316,2017-11-13 18:47:10 UTC,"Still not working , Asus FX553VD-DM160."
1662316,2017-09-21 08:26:06 UTC,Maybe this one?
1662316,2017-09-21 08:00:13 UTC,It looks like they already fixed this issue in Kernel 4.12.
1662316,2017-09-14 18:39:50 UTC,"Shoumik Chowdhury (shoumikchow), I'd rather not. This patch is nothing more than a model-dependent hack, which, most likely, will generate problems on non-Asus models. Maybe a good kernel module programmer can have a look there to make it work everywhere."
1662316,2018-03-09 19:41:43 UTC,"Adding 'acpi_osi=' to /etc/default/grub solves it all for me, on an old Dell laptop, an old Compaq nx7400 and a quite new HP G2.  This seem to fool the bios to think its a Windows OS."
1662316,2017-07-10 16:01:46 UTC,"I have prepared a patch to original 4.12 kernel, which enables backlight/F3/F3 keys. It works on my GL553VE machine. All other buttons are working in 4.12."
1662316,2017-09-13 17:51:17 UTC,"Cabalbl4 (i-vohmin), make the changes to the official repository and send a pull request, please!"
1662316,2017-02-06 21:00:14 UTC,This change was made by a bot.
1662316,2017-02-06 21:17:45 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1662316,2017-02-07 13:52:23 UTC,"Bug reported via mail to appropriate mail lists:
http://www.spinics.net/lists/platform-driver-x86/msg10489.html"
1662316,2017-05-16 04:24:11 UTC,Please try 4.12-rc1 mainline kernel:
1662316,2017-05-15 23:55:32 UTC,"Same as above, I am facing same problems and in addition another problem is battery dry in very fast."
1662316,2017-05-23 19:59:43 UTC,"GL753VE laptop, with 4.12-rc1 kernel:
Fn keys working: F1 (sleep), F2 (airplane), F5 (brightness down), F6 (brightness up), F9 (disable touchpad), F10, F11, F12 (sound mute, -, +)
Fn keys not working: F3 (keyboard backlight down), F4 (keyboard backlight up)"
1662316,2017-05-24 03:18:02 UTC,So you need to raise the question to linux-input mailing list.
1662316,2017-02-12 12:49:33 UTC,"As there was no answers from the mailing list created a bug report
https://bugzilla.kernel.org/show_bug.cgi?id=194557"
1662328,2017-06-15 11:44:53 UTC,Switching back to Intel graphics however renders the logout from Plasma functional.
1662328,2017-10-22 09:32:04 UTC,Also affecting Ubuntu artful. The following message is in the xserver logs:
1662328,2017-10-22 09:32:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662328,2018-07-15 23:54:25 UTC,"I can confirm that this bug affects Mint 18.2 Sylvia (KDE edition). Currently using Plasma 5.8.9 , KDE Frameworks 5.36.0 , Qt version 5.6.1, kernel 4.13.0-45-generic, 64 bits OS."
1662328,2017-06-15 11:43:32 UTC,Similar happens with KDE Neon 5.10.2 and nvidia-340. Logout is effectively disabled by crash message. Using 'loginctl terminate-session <id>' closes the session properly.
1662328,2017-09-07 16:20:28 UTC,I have the same problem with Linux Mint 18.2 KDE. It might be affecting the nvidia-prime functionality because even after I manage to logout with 'loginctl terminate-session' the gpu doesn't switch and goes back to intel by default. Very troublesome.
1662336,2019-08-02 16:31:41 UTC,"Deere:
https://github.com/mixxxdj/mixxx/pull/2161"
1662336,2019-02-16 00:37:03 UTC,+1 on this.
1662336,2017-02-07 08:49:09 UTC,"BTW Apple decides to remove the battery indicator from the Finder´s toolbar for macOS Sierra 10.12.2 [1].
Would be nice to have some feedback from users on 10.12.2+ if the widget in Mixxx still works."
1662336,2017-02-07 08:04:25 UTC,"+1
But Users won´t see it until compiled with ``battery=1`` option, which is disabled by default, and in the official builds."
1662341,2017-02-11 08:41:18 UTC,Can't reproduce so far.
1662341,2017-02-11 08:46:46 UTC,"Oops, sorry for duplication."
1662345,2017-02-07 07:42:07 UTC,"Hi Ryan,
just to find if that is totally new or maybe bisect&backport - do you have any extra data on other ""incarnation"" of qemu?:
- new Qemu in Yakkety or Zesty-Proposed
- new Qemu in Debian
- Upstream"
1662345,2017-02-07 07:42:23 UTC,"I also saw that Dannf is subscribed already, are you looking into that?"
1662345,2017-02-07 15:47:42 UTC,"On Tue, Feb 7, 2017 at 1:42 AM, ChristianEhrhardt <
<email address hidden>> wrote:"
1662345,2017-02-07 18:11:41 UTC,"I tested this at Ryan's request, and was using QEMU 1:2.6.1+dfsg-0ubuntu8 instantiated with the following command line:"
1662345,2017-02-08 09:14:09 UTC,"The commit Ryan found is in >=2.5 but the issue is seen in Xenial which is 2.5.
Also Dann tested the Yakkety version which seems to have the issue as well."
1662345,2018-06-27 09:37:02 UTC,"Clearing outdated bugs atm, lets be honest this is on no-ones prio list at all.
I'll set it to wishlist to reflect that."
1662345,2018-07-20 09:00:46 UTC,"Hello,
I have revived this bug and assigned myself to it."
1662347,2017-10-11 21:51:22 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/511072"
1662347,2017-10-10 22:58:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/511072"
1662347,2017-10-10 15:52:41 UTC,"Reviewed:  https://review.openstack.org/509038
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4083d08e863878fe7990556bae72852a019d39e1
Submitter: Jenkins
Branch:    master"
1662347,2017-10-09 02:29:13 UTC,"@Radomir, thanks for the comments. Actually, there is no user experience impacting. Please see See https://ibb.co/kor5Tw and https://ibb.co/kKm8Fb"
1662347,2017-02-07 03:32:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430029"
1662347,2017-10-03 00:51:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509038"
1662347,2017-10-02 23:49:21 UTC,"This is a follow up for this bug but focusing on the instance panel. Based on my test, running Horizon Pike locally and using our public cloud API, I got below result:"
1662347,2017-03-15 10:11:17 UTC,"Change abandoned by Lingxian Kong (<email address hidden>) on branch: master
Review: https://review.openstack.org/430029"
1662347,2017-10-03 13:39:03 UTC,"I'm a bit conflicted about this. On one hand, we shouldn't display to users actions that we know will fail for them — that's just bad feedback. On the other hand, the users should not have to guess why a given option is disabled in a particular situation, and that is what happens when we just disable the button without any extra information."
1662352,2017-03-14 10:25:11 UTC,"Hi Gerald, we plan to provide an option just like force_delete in volume_type, so the user can choose whether to force delete the volume. The way it behaves just like the storwize GUI. If there is host-mapping, flashcoppy and the force-delete is not set, the delete will be fail. If the force-delete is set the volume will be deleted by force.  Hoe do you think about it?"
1662352,2017-03-24 13:49:36 UTC,"Hi Xio Quin, I think if you force delete that would kill the copies instead of waiting for them to complete? We really want the flash copies to complete."
1662352,2017-03-24 13:51:25 UTC,xiaoqin
1662352,2019-01-24 05:14:09 UTC,Is there any update on this bug?
1662352,2019-01-24 10:10:47 UTC,"The volume can not be deleted is due to some other volume is dependent on the volume2.
The workaround for this issue is:
1. If the the users do not care about the flash copies, they can force delete this volumes in the backend storage.
2. If users really want the flash copies to complete, they can do the delete operation sometime later. Since the flash copy relationship will be deleted automatically after data copy finished."
1662353,2017-02-06 22:46:51 UTC,Using the hid_multitouch module with the kernel above.
1662353,2017-02-07 18:31:24 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1662353,2017-02-06 22:46:27 UTC,"Important to note: the keyboard doesn't work at all on 16.04, it does work with the linux-surface kernel in the https://launchpad.net/~tigerite/+archive/ubuntu/kernel PPA."
1662353,2017-02-06 23:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1662354,2017-02-06 22:56:47 UTC,"StacktraceTop:
 g_type_check_instance_cast () from /tmp/apport_sandbox_s19CfB/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 on_source_added (manager=<optimized out>, source=0x56340e3c9460, enabled=<optimized out>, self=0x56340e5424f0) at gcal-quick-add-popover.c:298
 ffi_call_unix64 () from /tmp/apport_sandbox_s19CfB/usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /tmp/apport_sandbox_s19CfB/usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /tmp/apport_sandbox_s19CfB/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1662355,2017-02-07 07:49:40 UTC,"We are not trying to pretend that we are Safari :-)
But it looks like for some reason our User-Agent string is interpreted by Google as being from Safari. This is actually a fault in Google's servers, but I'll keep this bug open because we might want to find another User-Agent string as a workaround."
1662361,2019-08-19 22:26:27 UTC,"Ignore my comment, if I specify the part on the right side of the '/', I can get it to deploy that."
1662361,2019-08-19 22:24:27 UTC,"This may be a similar issue, I have multiple types of distro_series per OS type:"
1662369,2019-04-11 19:25:32 UTC,"@Evan, yes, it's in master, not 5.1.  (You can look in the Milestone field at the top right of the bug report to find what version it's in.)"
1662369,2019-04-11 17:46:07 UTC,This must have been a duplicate as it's already been implemented.
1662369,2019-04-11 19:01:36 UTC,"Hi Jeff,"
1662374,2020-05-10 01:01:33 UTC,Yes this was fixed with the EffectState memory handling refactoring for postfader effects in 2.1 https://github.com/mixxxdj/mixxx/pull/1254
1662374,2020-05-10 00:27:58 UTC,Is this one fixed? I think yes.
1662374,2017-02-07 07:28:00 UTC,"This is because the Group state is instantiated during the first engine call.
https://github.com/mixxxdj/mixxx/blob/8d191bf7ce2d62d24c6e0ffac4b2afd7359afa8a/src/effects/effectprocessor.h#L80
This new() in the engine thread most likely causes the under-run:
https://github.com/mixxxdj/mixxx/blob/8d191bf7ce2d62d24c6e0ffac4b2afd7359afa8a/src/effects/effectprocessor.h#L97"
1662374,2017-02-08 03:41:51 UTC,The system was designed to pre-allocate all group state on the main thread for groups that exist when the effect is instantiated.
1662374,2017-02-08 03:51:03 UTC,Though this won't work for e.g. the P32 MIDI script which creates 32 samplers when the controller script is evaluated. If you enable an effect unit for one of these samplers you'll hit the same memory allocation in the callback.
1662374,2017-02-08 06:01:12 UTC,"> Were you using master or was this using your persistent effects branch?
"
1662374,2017-02-08 07:52:13 UTC,"> Perhaps a better solution would be that when we write an ENABLE_EFFECT_CHAIN_FOR_CHANNEL message from the main thread to the engine, we also send a message for every effect in the chain containing an instance of the group state for that effect. We will also have to write group state for every enabled channel whenever we add a new effect to the chain.
"
1662374,2017-02-08 08:08:48 UTC,"> This Sounds like a good plan. .. and entirely remove the singleton thing from the process call.
"
1662374,2017-06-20 03:48:56 UTC,"I am doubtful that the ""new T()"" in PerChannelEffectProcessor::getOrCreateChannelState is causing this issue. In https://github.com/mixxxdj/mixxx/pull/1254 I have moved the initialization of EffectChains/EngineEffectChains and Effects/EngineEffects after the registration of input & output channels with EffectsManager, but now this issue seems to be occurring more often. Do you have any suggestions for tracking down the source of the issue?"
1662374,2017-02-08 08:50:40 UTC,"Not a real singleton, just this:"
1662377,2017-02-07 01:10:37 UTC,Gonna confirm this since we talked about possibly using a revealer to hide devices instead. This would match with the behavior of the indicator
1662381,2017-02-07 18:27:28 UTC,"Would it be possible for you to test this latest kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1662381,2017-02-07 13:25:02 UTC,"Also, and not sure if this is related, Plymouth does not correctly render the splashscreen on boot up.  Part way through, the screen blanks and only the ""dot icons"" are visible.  Again, this does not occur for earlier kernels."
1662381,2017-02-07 18:17:10 UTC,"Another thought: I'm using the modesetting driver, not the intel driver."
1662381,2017-02-07 18:28:07 UTC,"If -proposed still has the bug, we can peform a kernel bisect to identify the commit(s) that introduced this bug."
1662381,2017-02-07 19:26:26 UTC,I am happy to report that linux-image-4.4.0-63-generic from xenial-proposed _is_ working correctly with the T440s on and off the dock.  So the bug is gone from the -proposed kernel package.
1662381,2017-02-07 01:30:14 UTC,This change was made by a bot.
1662382,2017-02-07 12:14:39 UTC,"Hello jackalsandflames,  I assume you are copying using the Pantheon FileManager?  When you say the files disappear, do you mean they disappear from the Windows partition?  Does this happen with all file types and sizes? Does it always happen? If you copy and then reboot back into Linux rather than Windows do they disappear?  If so then it sounds like they were cached and never actually copied; if not then it sounds like Windows is deleting them for some reason."
1662390,2017-02-15 13:38:25 UTC,"The only step to fix this is to install the python-sahara-dashboard .
I tried to put this packeage in the provision of the initial packages but it does not work. is this by design  since this are just the basic packages or should have worked?"
1662390,2017-02-20 09:46:05 UTC,Sahara and Ceilometer
1662400,2017-03-23 15:50:00 UTC,An actual way to reproduce:
1662400,2017-03-22 22:22:47 UTC,"I was able to hit this issue when U8 crashed while ubuntu-app-test was open. Leaving behind in:
/run/user/1000/systemd/transient/ubuntu-app-launch-application-legacy-ubuntu-app-test-.service"
1662400,2017-02-07 03:38:43 UTC,"If it's relevant, I launch everything and do all development from an ssh login. Until recently ubuntu-app-launch worked fine in this configuration (bug 1654915)."
1662400,2017-03-21 04:14:42 UTC,This WFM with this silo: https://bileto.ubuntu.com/#/ticket/2577
1662400,2017-02-07 08:27:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662400,2017-03-22 17:47:14 UTC,"The silo does not help for me.  Mir applications fail to connect, but not with the error described in this bug.  Instead I get various errors about being unable to connect to the Mir server, which vary depending on the test client used."
1662401,2019-10-07 10:44:42 UTC,Refer attached word doc for detailed output.
1662401,2019-10-07 10:43:36 UTC,"Observed that failure occurs when volume is attached to host.
bug: 1809249 resolves this issue. It is present in Train.
After applying this fix, volume retype happens successfully."
1662401,2018-01-12 19:03:10 UTC,Unassigning due to no activity for > 6 months.
1662401,2017-02-07 13:44:30 UTC,"Manish, can you confirm - are these using the same or different encryption?"
1662401,2017-02-14 08:56:09 UTC,"HI Lee,"
1662401,2017-02-13 04:31:20 UTC,"HI Sean, they are using the same encryption algorithm but different QOS."
1662401,2017-02-07 09:22:06 UTC,Why was this bug created against Nova? AFAICT this behaviour appears correct assuming the two volume types have differing encryption or QoS properties :
1662401,2017-06-28 05:02:35 UTC,"With similar scenario with FC protocol without QOS setting,
Volume type of 3parFC-1 + ""thin"" provisioning type
Volume type of 3parFC-2 + ""full"" provisioning type"
1662407,2017-02-07 04:13:41 UTC,Oddly I get this error that you would this should apply to the failure case:
1662407,2018-12-25 11:24:24 UTC,I can reproduce adding such a cache triggering an OOPS in 18.10:
1662407,2018-12-25 20:22:27 UTC,"[ 2938.649666] bcache: register_bcache() error /dev/nvme0n1p2: Bad block/bucket size
[ 2945.532897] bcache: register_bdev() registered backing device md127
[ 2945.533124] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
[ 2945.533863] PGD 0 P4D 0
[ 2945.535162] Oops: 0000 [#1] SMP NOPTI
[ 2945.536474] CPU: 13 PID: 3773 Comm: bcache-register Not tainted 4.18.0-10-generic #11-Ubuntu
[ 2945.537785] Hardware name: System manufacturer System Product Name/PRIME X399-A, BIOS 0808 10/12/2018
[ 2945.539297] RIP: 0010:create_empty_buffers+0x29/0x110
[ 2945.540623] Code: 90 0f 1f 44 00 00 55 48 89 e5 41 55 49 89 d5 ba 01 00 00 00 41 54 53 48 89 fb e8 92 f5 ff ff 49 89 c4 48 89 c2 eb 03 48 89 ca <48> 8b 4a 08 4c 09 2a 48 85 c9 75 f1 4c 89 62 08 48 8b 43 18 48 8d
[ 2945.542015] RSP: 0018:ffffb90b874777d0 EFLAGS: 00010282
[ 2945.543408] RAX: 0000000000000000 RBX: ffffe1309f8b1140 RCX: 000000000000000d
[ 2945.544793] RDX: 0000000000000000 RSI: 0000000000002000 RDI: ffffe1309f8b1140
[ 2945.546727] RBP: ffffb90b874777e8 R08: dead0000000000ff R09: 0000000000000011
[ 2945.548121] R10: ffffffffffffffff R11: 0000000000000000 R12: 0000000000000000
[ 2945.549515] R13: 0000000000000000 R14: 00000000006200c0 R15: ffffe1309f8b1140
[ 2945.550888] FS:  00007f7d07190540(0000) GS:ffff9e0f5cd40000(0000) knlGS:0000000000000000
[ 2945.552266] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2945.553646] CR2: 0000000000000008 CR3: 00000007e788c000 CR4: 00000000003406e0
[ 2945.555027] Call Trace:
[ 2945.556399]  create_page_buffers+0x51/0x60
[ 2945.557799]  block_read_full_page+0x4d/0x330
[ 2945.559191]  ? check_disk_change+0x70/0x70
[ 2945.560562]  ? __add_to_page_cache_locked+0x1e3/0x240
[ 2945.561935]  blkdev_readpage+0x18/0x20
[ 2945.563304]  do_read_cache_page+0x2b4/0x5b0
[ 2945.564684]  ? blkdev_writepages+0x10/0x10
[ 2945.566052]  read_cache_page+0x15/0x20
[ 2945.567562]  read_dev_sector+0x2d/0xd0
[ 2945.568920]  read_lba+0xcd/0x220
[ 2945.570259]  ? find_valid_gpt+0xd1/0x560
[ 2945.571601]  find_valid_gpt+0xf1/0x560
[ 2945.572939]  ? string+0x61/0x80
[ 2945.574286]  efi_partition+0x89/0x3a3
[ 2945.575608]  ? snprintf+0x49/0x60
[ 2945.576916]  ? find_valid_gpt+0x560/0x560
[ 2945.578224]  check_partition+0x139/0x236
[ 2945.580162]  rescan_partitions+0xaf/0x290
[ 2945.581469]  ? down_write+0x12/0x40
[ 2945.582775]  __blkdev_get+0x367/0x500
[ 2945.584081]  blkdev_get+0x10c/0x330
[ 2945.585380]  ? unlock_new_inode+0x4b/0x60
[ 2945.586706]  ? bdget+0x110/0x130
[ 2945.588005]  __device_add_disk+0x392/0x430
[ 2945.589307]  device_add_disk+0x13/0x20
[ 2945.590616]  bch_cached_dev_run.part.31+0x42/0x1b0 [bcache]
[ 2945.591917]  register_bcache.cold.49+0x20d/0x212 [bcache]
[ 2945.593249]  ? __seccomp_filter+0x49/0x4b0
[ 2945.594571]  kobj_attr_store+0x12/0x20
[ 2945.596000]  ? _cond_resched+0x19/0x30
[ 2945.597279]  ? kobj_attr_store+0x12/0x20
[ 2945.598549]  sysfs_kf_write+0x3b/0x50
[ 2945.599800]  kernfs_fop_write+0x12e/0x1b0
[ 2945.601057]  __vfs_write+0x1b/0x40
[ 2945.602350]  vfs_write+0xab/0x1b0
[ 2945.603610]  ksys_write+0x55/0xc0
[ 2945.604857]  __x64_sys_write+0x1a/0x20
[ 2945.606100]  do_syscall_64+0x5a/0x110
[ 2945.607334]  entry_SYSCALL_6..."
1662407,2018-12-25 20:44:35 UTC,This should perhaps be moved to the kernel; its not clear that userspace is doing anything wrong. I've filed #1809748 for now.
1662407,2018-12-25 21:23:03 UTC,"sb.magic		ok
sb.first_sector		8 [match]
sb.csum			5A3217E583DB5B86 [match]
sb.version		0 [cache device]"
1662407,2018-12-25 21:35:49 UTC,after doing a wipefs on the cache drive the BUG still occured; wipefs's the backing drive corrected that. I haven't yet tried wiping just the backing drive.
1662407,2019-06-25 08:42:46 UTC,"I agree that this looks much more like a kernel bug.
You could have added a task here - but I'll make it a dup so that overall only bug 1809748 to look at."
1662415,2017-09-08 22:59:39 UTC,There is no activity for fixing this bug for a while. I am going to remove assignee so that other contributors can take it.
1662419,2017-02-07 06:01:39 UTC,Perhaps related to https://bugs.launchpad.net/plank/+bug/1516690 ?
1662419,2017-02-07 06:02:36 UTC,"I should’ve mentioned this happens with all the hide options, not just Intellihide."
1662424,2017-02-07 06:30:09 UTC,i have this crash at each boot
1662424,2017-02-07 06:41:16 UTC,"StacktraceTop:
 tevent_debug (ev=0xbe4e18eafae2c1a5, level=level@entry=TEVENT_DEBUG_TRACE, fmt=fmt@entry=0x7f509113ea58 ""Running timer event %p \""%s\""\n"") at ../tevent_debug.c:89
 tevent_common_loop_timer_delay (ev=0x55dae71ac680) at ../tevent_timed.c:358
 run_events_poll () from /tmp/apport_sandbox_fj0ubI/usr/lib/x86_64-linux-gnu/libsmbconf.so.0
 s3_event_loop_once () from /tmp/apport_sandbox_fj0ubI/usr/lib/x86_64-linux-gnu/libsmbconf.so.0
 _tevent_loop_once (ev=ev@entry=0x55dae71ac680, location=location@entry=0x7f509113e2c7 ""../tevent_req.c:264"") at ../tevent.c:721"
1662424,2017-02-07 23:22:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662430,2017-02-07 06:44:29 UTC,Another software where this problem happens is Atom Editor with the package atom-amd64.deb.
1662430,2020-09-22 14:34:26 UTC,This is occurring for me on focal with 3.36.1-0ubuntu0.20.04.0. It seems to affect all deb packages.
1662432,2019-08-15 00:00:14 UTC,"Change abandoned by MarkMielke (<email address hidden>) on branch: master
Review: https://review.opendev.org/430091
Reason: I think his problem may have been solved in a better way with placement, and with changes to how resource tracking is performed."
1662432,2019-06-28 23:17:49 UTC,"I have a feeling this is probably fixed since Pike or at least Rocky because the DiskFilter has been deprecated in favor of using the placement service for filtering hosts based on DISK_GB inventory which accounts for root, ephemeral and swap disk. Furthermore https://review.opendev.org/#/c/580720/ and a series of changes after it cleaned up issues with reporting and claiming disk for volume-backed servers and swap disk."
1662432,2017-02-17 13:29:00 UTC,"I totally agree with you, Matthew. Thanks for looking into this. The original problem is definitely miscalculation of storage usage based upon flavors."
1662432,2017-03-01 04:44:11 UTC,"Thanks, Matthew. I have updated the description to title and description to match my current understanding."
1662432,2017-02-17 12:18:08 UTC,"This issue doesn't relate to over commit, it relates to the miscalculation of disk usage. It is deterministic, and doesn't involve incremental allocation of thin storage by a running instance."
1662432,2017-02-07 06:58:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430091"
1662432,2017-06-27 15:56:04 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1662433,2017-02-07 07:00:20 UTC,Actually I don't think we have a good solution for this yet.
1662433,2017-11-03 16:30:18 UTC,Syncing task from Mir.
1662436,2017-03-23 22:42:44 UTC,Please justify changing this to invalid.
1662436,2017-03-27 06:42:53 UTC,The status has not changed. I saw this bug report just now. The previous commenter posted that status has changed to Invalid. I'm not sure what he means to say.
1662436,2017-11-06 20:23:09 UTC,Cannot install a kernel through ukuu in Ubuntu 17.10 Wayland-session.
1662436,2017-12-18 16:50:06 UTC,"Are there any plans to fix this in the near future, especially since Wayland is default now in Ubuntu?"
1662440,2020-07-11 04:17:22 UTC,[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]
1662440,2020-05-11 11:47:58 UTC,"Thanks for testing this again José Luis, and for the feedback."
1662440,2020-05-09 08:57:46 UTC,In reply to comment #13.
1662440,2020-05-04 14:06:14 UTC,"Just tested in a clean and up-to-date 20.04 VM, fully set up in Spanish.
I was able to successfully import https://www.sede.fnmt.gob.es/documents/10445900/10526749/AC_FNMT_Usuarios.cer without an error."
1662440,2020-04-30 23:13:19 UTC,What I did was giving up on the FNMT and using another certificate authority.
1662440,2020-04-30 22:42:07 UTC,"Hmm, this is weird...one thing that caught my eye when trying to import the intermediate CA certificate by just following the link below is the window that opened had the ""Details"" text in red background...which tends to not be a good sign."
1662440,2020-04-30 22:00:14 UTC,"Forgot to add some information here for reference:
""""""
Chromium	81.0.4044.122 (Build oficial) snap (64 bits)
Revisión	44f4233f08910d83b146130c1938256a2e05b136-refs/branch-heads/4044@{#963}
Sistema operativo	Linux
JavaScript	V8 8.1.307.31
Flash	(disabled)
User-agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/81.0.4044.122 Chrome/81.0.4044.122 Safari/537.36
Línea de comandos	/snap/chromium/1123/usr/lib/chromium-browser/chrome --no-default-browser-check --no-first-run --password-store --flag-switches-begin --flag-switches-end --disable-webrtc-apm-in-audio-service
"""""""
1662440,2017-02-10 15:39:00 UTC,"Bottom-line is this importance is relative to the overall Ubuntu, not specifically to Chromium. The Chromium project could have a different importance, set in the report you have filled upstream."
1662440,2017-02-10 08:34:35 UTC,You're right. You have another browsers... and certificates work on firefox. I ment is not low priority for Chromium developers...Several spanish institutional pages have outdated certificates. Mayte that's also the problem in this page...Kind regards
1662440,2017-02-09 17:42:20 UTC,"When I click on the link it says ""you do not have permission to view the requested page"". Any idea why is that?"
1662440,2017-02-09 07:47:20 UTC,"Reported here:
https://bugs.chromium.org/p/chromium/issues/detail?id=690340"
1662440,2017-02-08 16:49:50 UTC,Please:
1662440,2017-02-08 16:47:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662440,2020-04-30 21:57:35 UTC,"OK, so I just upgraded from 18.04 LTS to 20.04 LTS, and with it came an upgrade from ""standalone"" (apt managed) Chromium to ""snaps"" Chromium, and while trying to do some activities with a public administration in Spain, I was faced with an error for no personal certificates existed (and I have two of them imported in Chromium before upgrading Ubuntu)."
1662440,2017-02-10 20:05:05 UTC,Thank you very much. That has a lot of sense...Kind regards
1662443,2017-02-07 18:22:06 UTC,What do you think should happen?
1662443,2017-02-07 20:39:18 UTC,"If the tender is missing then there will be no coal and fuel to supply the locomotive, so whatever water is in the boiler, and coal in the fire is what the locomotive will run on. This means that both coal and water will be ""exhausted"" very quickly, and the locomotive will loose power. If the game starts without the tender, then there probably should be no coal or water in the locomotive at all."
1662443,2017-02-07 21:58:32 UTC,"Agree with all this. If the driver uncouples his tender and drives off, he should get into trouble fairly quickly. I would prefer that behaviour over some block on driving without a tender."
1662443,2017-02-09 04:54:01 UTC,"#3785 - - fixed steam locomotive code so that if a tender is required, the locomotive must have one connected."
1662451,2017-02-20 03:35:19 UTC,"As this is a tech-debt item, I am lowering its priority and removing from the milestone."
1662452,2019-10-15 11:32:58 UTC,"Hey Ara, long time no see if you are reading this."
1662452,2017-02-07 08:58:44 UTC,I can reproduce this behaviour. However it looks like a faulty snap.
1662452,2017-02-07 08:52:13 UTC,It looks like the core issue is that the CPU Ara tried to run this on some instructions were not available:
1662457,2017-03-08 14:26:29 UTC,"On a related note, Tempest is now going to default to Keystone v3 [1]."
1662457,2017-04-12 17:28:20 UTC,This issue was fixed in the openstack/python-solumclient 2.3.0 release.
1662466,2017-02-15 17:15:00 UTC,"Ok, so looking at this code, I can confirm that this bug describes the current behavior accurately (see https://github.com/openstack/openstack-ansible/blob/master/lib/generate.py#L305-L306, where it iterates over all entries in `container_vars`)."
1662477,2017-03-17 01:58:51 UTC,I could not reproduce the bug
1662477,2017-03-17 06:34:11 UTC,These are the steps needed to reproduce:
1662481,2017-05-16 00:14:50 UTC,Upstream bug tracking: https://github.com/elementary/switchboard-plug-sharing/issues/10
1662483,2019-04-26 17:16:04 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1662483,2019-03-24 23:39:28 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1662483,2019-03-24 23:04:17 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1662483,2019-03-22 03:43:55 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1662483,2019-03-13 10:16:19 UTC,"Reviewed:  https://review.openstack.org/637536
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f0b833a352f8859c7b7e299d90440acfbd42e9db
Submitter: Zuul
Branch:    stable/pike"
1662483,2019-02-19 01:40:07 UTC,"Reviewed:  https://review.openstack.org/637535
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=17b3d5734af9c7b916cfc7007e98f43df975b8e8
Submitter: Zuul
Branch:    stable/queens"
1662483,2017-08-01 10:17:08 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1662483,2019-02-18 12:44:38 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/637536"
1662483,2019-02-18 12:44:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/637535"
1662483,2019-02-18 12:43:54 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/637534"
1662483,2019-02-14 21:47:29 UTC,"Reviewed:  https://review.openstack.org/636701
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2e4e203c1a4c4f91dd1aabae8c8d7b745df99be7
Submitter: Zuul
Branch:    master"
1662483,2019-02-13 18:32:15 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/430213
Reason: Nevermind I just updated https://review.openstack.org/#/c/636701/ to add mdbooth as co-author."
1662483,2017-08-01 09:57:35 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/430213
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1662483,2019-02-18 21:44:33 UTC,"Reviewed:  https://review.openstack.org/637534
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3310c3cbf534f5d75477ed206a8fb68eb53c6c10
Submitter: Zuul
Branch:    stable/rocky"
1662483,2017-02-07 11:42:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430213"
1662493,2017-02-07 20:10:59 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1662495,2017-09-17 09:30:13 UTC,fixed in gcc-7
1662495,2017-02-08 13:34:46 UTC,"Sidenote: we were unable to reproduce that bug on:
1. Ideone (they claim to use GCC 5.1, but do not specify which flavor it is).
2. tdm-gcc 5.1.0 on Windows.
3. gcc version 6.1.0 (Gentoo 6.1.0 p1.0)"
1662495,2017-02-07 13:19:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662501,2017-02-07 12:59:35 UTC,12:54 <rbasak> I believe that's by design.
1662501,2019-08-24 16:07:26 UTC,Could we eventually use xdg-desktop-portal? https://bugzilla.mozilla.org/show_bug.cgi?id=1490186
1662501,2018-07-30 22:35:52 UTC,"On Sun, Jul 29, 2018 at 11:35:58PM -0000, Daniel Richard G. wrote:

> I think we could really use some kind of conditional construct (IF ...
> THEN ...) in AppArmor syntax. Everything being talking about here
"
1662501,2018-07-29 23:35:58 UTC,"I think we could really use some kind of conditional construct (IF ... THEN ...) in AppArmor syntax. Everything being talking about here should, ideally, be adjustable using tunables. With a debconf configuration option, even."
1662501,2018-05-11 17:03:24 UTC,Hello.
1662501,2017-05-16 18:41:44 UTC,I have created simialr bug in https://bugs.launchpad.net/firefox/+bug/1609439 . It's confusing having too (or more?) Firefoxes in launchpad...
1662501,2018-07-31 01:50:21 UTC,"Hmmm, interesting!"
1662501,2017-02-07 14:41:49 UTC,Clarification re snaps and the 'home' interface> the 'home' interface does not grant access to toplevel hidden files and directories.
1662501,2017-02-07 14:37:45 UTC,Thank you for using Ubuntu and filing a bug!
1662501,2017-02-07 14:07:12 UTC,"Jeremy,"
1662501,2017-02-07 13:40:11 UTC,"What about blocking access by default to directories that begin with . (like .config, .cache, etc.) ?"
1662501,2017-02-07 13:19:31 UTC,"Just a comment about snaps. The snaps would have the same kind of problem, if convenience is a factor."
1662501,2017-02-07 15:34:29 UTC,"Jamie,"
1662507,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1662508,2017-08-07 16:26:18 UTC,I wonder if it's an opportunity for some 3rd party CI.
1662512,2017-02-07 14:18:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430268"
1662512,2017-02-08 10:07:53 UTC,"Reviewed:  https://review.openstack.org/430268
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=003a0a0efdbedf51fef943586286e00068175b43
Submitter: Jenkins
Branch:    master"
1662512,2017-02-08 10:34:38 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430713"
1662512,2017-02-08 13:17:39 UTC,"Reviewed:  https://review.openstack.org/430713
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=5b00f6081d116ca11150036c89570cedb1c70d39
Submitter: Jenkins
Branch:    stable/newton"
1662512,2017-02-27 16:26:54 UTC,This issue was fixed in the openstack/fuel-astute 11.0.0.0rc1 release candidate.
1662512,2017-03-10 05:33:10 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/444094"
1662512,2017-03-15 12:27:19 UTC,"Reviewed:  https://review.openstack.org/444094
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=840392eeaebe52fb7bef092eda987a897475763c
Submitter: Jenkins
Branch:    stable/mitaka"
1662512,2017-03-16 09:23:05 UTC,Verified on 9.2 + mu1 updates.
1662513,2017-02-07 20:09:16 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1662513,2017-04-09 04:17:45 UTC,[Expired for libav (Ubuntu) because there has been no activity for 60 days.]
1662522,2017-02-10 10:22:12 UTC,"Gabor, does it break anything? If not, I see no reason to remove it."
1662522,2017-02-10 11:04:48 UTC,"Hi Oleksiy,"
1662522,2017-02-15 10:19:05 UTC,"After doing some testing on this topic, I had to realize that on the donor side this credential is necessary for innobackupex to be able to create the backup. So, in my opinion the Galera documentation is a bit misleading in this aspect. However, due to the file permissions, this sensitive information is currently world readable on the controllers."
1662523,2017-02-09 10:45:58 UTC,"Reviewed: https://review.fuel-infra.org/30610
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1662523,2017-02-08 11:38:34 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30610"
1662523,2017-02-08 11:31:35 UTC,"Reviewed: https://review.fuel-infra.org/30583
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1662523,2017-02-08 07:50:14 UTC,"Reviewed: https://review.fuel-infra.org/30584
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1662523,2017-02-07 22:12:09 UTC,"Reviewed: https://review.fuel-infra.org/30582
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1662523,2017-02-07 22:12:04 UTC,"Reviewed: https://review.fuel-infra.org/30585
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1662523,2017-02-07 22:11:46 UTC,"Reviewed: https://review.fuel-infra.org/30581
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1662523,2017-02-07 17:15:14 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30585"
1662523,2017-02-07 17:10:50 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30584"
1662523,2017-02-07 17:00:31 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30583"
1662523,2017-02-07 16:52:59 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30582"
1662523,2017-02-07 16:44:20 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30581"
1662527,2019-05-11 05:50:12 UTC,Closing this bug as it appears this has now been reported in our new GitLab bug tracker. Please submit all future bug reports here: https://inkscape.org/report. Thank you!
1662529,2017-02-27 16:24:12 UTC,This issue was fixed in the openstack/fuel-web 11.0.0.0rc1 release candidate.
1662529,2017-02-08 11:23:11 UTC,"Reviewed:  https://review.openstack.org/430345
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=7db4214bb5d8b94df6794bc46bcadfc64f819d16
Submitter: Jenkins
Branch:    stable/newton"
1662529,2017-02-09 15:33:05 UTC,"Reviewed:  https://review.openstack.org/430347
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=b6e0406dc070e9c923c43ecf8f7f110ed8dd4ecf
Submitter: Jenkins
Branch:    stable/mitaka"
1662529,2017-02-07 16:28:32 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/430345"
1662529,2017-02-07 16:14:32 UTC,"Reviewed:  https://review.openstack.org/430216
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=5eb41d7bc18b4ac06fdff7099d338736a610abf2
Submitter: Jenkins
Branch:    master"
1662529,2017-02-07 16:32:16 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/430347"
1662530,2017-02-07 20:35:16 UTC,"Agreed, this is ""as designed"".  But, the error message could indeed be clearer."
1662530,2018-02-28 00:08:20 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu1
1662531,2017-02-19 14:17:18 UTC,Dumped environment as seen with trunk on Ubuntu 14.04.5 LTS.
1662531,2017-02-19 13:17:11 UTC,"On 2017-02-19 12:29 (+0100), Alvin Penner wrote:

> would it be possible for you to perform the test in comment 43?
"
1662531,2017-02-19 12:25:29 UTC,"Alvin wrote:

> it is essential that (...)
"
1662531,2017-02-19 12:05:22 UTC,"> would it be possible for you to perform the test in comment 43?
"
1662531,2017-02-19 11:55:56 UTC,"On 2017-02-19 12:29 (+0100), Alvin Penner wrote:

> would it be possible for you to perform the test in comment 43?
"
1662531,2017-02-19 11:52:49 UTC,"the variables LC_ do not even exist in Windows.
see comment 43
if they do not exist, then they cannot be set"
1662531,2017-02-19 11:41:56 UTC,"Comment #46 continued:
If %LANG% (aka $LANG) is not set in the CMD shell, then the first instance has no LANG in the environment (as read by Python), the second inkscape instance launched from within Inkscape does have $LANG set to the system language (tested with en_US as well as with de_CH as current user's default language via Settings dialog)."
1662531,2017-02-19 11:17:37 UTC,"On 2017-02-19 10:09 (+0100), su_v wrote:

> The question AFAIU is why $LANG is unset on some platforms in
> inkscape processes spawned via Popen()?
"
1662531,2017-02-19 11:29:09 UTC,"the variable LANG is not the issue. The issue is variables that begin with the prefix LC_.
would it be possible for you to perform the test in comment 43?"
1662531,2017-02-19 11:07:03 UTC,"would it be possible for you to perform the test mentioned in comment 43?
we need to find out for sure whether there is a distinguishable difference between the environment that exists on a non-Windows platform, in a Python extension, run from Inkscape,  versus a Windows platform, so that we can explain why this is an issue on Windows and is not an issue on other platforms."
1662531,2017-02-19 09:09:14 UTC,"Quick summary of locale-related environment variables:
https://www.gnu.org/software/gettext/manual/html_node/Locale-Environment-Variables.html#Locale-Environment-Variables"
1662531,2017-02-19 03:28:06 UTC,"Thanks. In actual fact, I do not think that the output of that question will have changed recently. I mean, it is not the environment that has changed in trunk, it is the manner in which the environment is being interrogated that has changed.
    So I wonder if you would be willing to do one final test, which is to dump out the entire contents of the environment on your machine, from Python from Inkscape.
    In my case I used the following commands in Python to do this:"
1662531,2017-02-19 02:17:21 UTC,"I don't have a trunk build installed at the moment, Alvin, so probably this will be useless to you.
In 0.91 and 0.92.1, I get only"
1662531,2017-02-18 23:57:58 UTC,"Thanks for testing. I wonder if you would be willing to try this output test in Python.
In a Python extension I add the code at the start:"
1662531,2017-02-19 11:39:23 UTC,"On 2017-02-19 12:29 (+0100), Alvin Penner wrote:

> the variable LANG is not the issue. The issue is variables that begin
> with the prefix LC_.
"
1662531,2017-02-19 14:31:19 UTC,Dumped environment as seen with 0.92.x on Mac OS X 10.7.5 (updated with output of `locale`).
1662531,2017-02-20 17:34:59 UTC,"Well, I am going to have to reverse my position once again. Here is an improved patch which works well for me, on Windows: Rewrite comment 6 to read:"
1662531,2017-02-19 18:12:40 UTC,"    thanks for the output, it will be very helpful. However, I have to confess to a certain amount of confusion. Where did this information come from, did it come from the terminal, or Inkscape, or did it come from Python?
    Ideally what we need is information that comes directly from Python, that is, from a Python instance that was initiated by Inscape and dumped just prior to a Popen command. The dump code should look something like this, in Python:
def effect(self):
     fout = open('\Windows\Temp\save_as_err.txt', 'wt')
     fout.write(str(inkex.os.environ))
     fout.close()"
1662531,2017-10-27 13:51:19 UTC,I made those changes before I found this ticket and did them for myself and others locally. I did a quick scan of the tickets to make sure my work wouldn't run into any issues when I eventually tried to submit it back.
1662531,2017-10-27 13:47:46 UTC,"Hi, as this tangentially affects me I think I have a proposal that may be better (at least for Print Win32 Vector). I've been working the last few days to enhance it and add support for all the elements that were previously not handled as indicated in the first post."
1662531,2017-03-13 12:50:27 UTC,"committed to rev 15591
(without the changes in 'LC_ALL')"
1662531,2017-02-20 18:49:53 UTC,"On 2017-02-20 13:51 (+0100), su_v wrote:

> Oh, one other test you could try: in a new CMD shell, set LANG to the
> same value as happens in localize(), and then launch inkscape (from the
> same shell).
>
> C:\path\to\inkscape> set LANG=en_US
> C:\path\to\inkscape> inkscape
>
> Does that open the GUI of current trunk without crash?
"
1662531,2017-02-20 17:43:48 UTC,"sorry, that should read comment 33, not 6:
https://bugs.launchpad.net/inkscape/+bug/1662531/comments/33"
1662531,2017-02-18 22:53:35 UTC,"On Linux Mint:
$ echo $LC_ALL"
1662531,2017-02-20 15:11:51 UTC,I doubt if this is related to the variable LANG. I monitored the variable LANG in the prepare_file_save_as extension using code like this:
1662531,2017-02-20 12:45:35 UTC,The only difference between the two tests asked for in comment 61 is whether or not inkex.localize() is run before the second Inkscape instance is spawned via Popen().
1662531,2017-02-20 12:10:16 UTC,the localize() code appears to be working on my machine. I insert the following code into inkex.py
1662531,2017-02-20 03:38:10 UTC,"On 2017-02-19 23:21 (+0100), Alvin Penner wrote:

> only the second one crashes
"
1662531,2017-02-19 22:29:20 UTC,"totally by accident, I happened to have some debugging code in the routine desktop-widget.cpp. The debugging code looks like this:
    std::cout << ""sp_dtw_rotation_output before locale()"" << std::endl;
 s.imbue(std::locale(""""));;"
1662531,2017-02-19 22:21:15 UTC,only the second one crashes
1662531,2017-02-19 19:48:07 UTC,"@Alvin - could you please pull the latest changes from the gitlab repo? Then try running
Extensions > Debug > Spawn Inkscape' with these two options:
1) 2nd Inkscape instance: Launch GUI; Use localize(): Off
2) 2nd Inkscape instance: Launch GUI; Use localize(): On"
1662531,2017-02-19 18:24:53 UTC,"Just a quick comment - I'm working on an update for the two extensions in the gitlab repo, to avoid executing affect() from inkex.Effect(): AFAICT it does call localize() now, and changes the environment on Windows. I'll comment later tonight (CET) about the findings."
1662531,2017-02-19 18:15:31 UTC,"okay, scratch that comment, I just checked out your gitlab repository and I think I get it.
So I will investigate to see if I can use some of that info."
1662531,2017-02-19 14:40:20 UTC,"On 2017-02-19 13:25 (+0100), su_v wrote:

> inkscape locally immediately crashes when adding the Measure path
> effect unless I explicitly launch it with LC_ALL=C
"
1662531,2017-02-18 22:07:38 UTC,"The reason that I am obsessing about the variable LC_ALL is because this is the variable that keeps on coming up if you google the error message:
'_S_create_c_locale name not valid'
which was the first error message that actually made any sense in this crash."
1662531,2017-02-17 15:13:46 UTC,and the other one
1662531,2017-02-18 21:13:15 UTC,"Look at the overloaded function call I linked to...
Omitting ""envp"" and using the environment from the parent instead is the intended difference between those two calls."
1662531,2017-02-10 21:32:43 UTC,"On 2017-02-10 22:18 (+0100), su_v wrote:

> (likely the crash is related to mixing without-gui (query-x) and
> with-gui (verbs) command line arguments (?)).
"
1662531,2017-02-10 21:27:29 UTC,"so, if you run the original script with no debugging output, can you tell if the Object to Path has been successfully implemented? If I understand correctly, this does not crash. If you save this new file as normal svg, does it appear that the conversion to path is done?"
1662531,2017-02-18 21:53:09 UTC,"okay, I think I have confirmed that Python indeed does inherit the Windows environment automatically. I ran a Python script from inside Inkscape and used the Python command:
fout.write(str(inkex.os.environ) + ""\n\n"")
to write out the entire environment. The environment was a duplicate of the normal Windows environment except for three new variables, which were 'LANG', 'PYTHONPATH', and 'INKSCAPELOCALE'. All three of these variables had reasonable values, as far as I can tell.
    So my question is, how come the variable 'LC_ALL' was not present?
    Is this variable present in non-Windows systems?
    Setting this variable fixed the crash, for reasons that I do not fully understand."
1662531,2017-02-10 20:13:23 UTC,"wow, thanks for testing!"
1662531,2017-02-10 19:40:36 UTC,"<off-topic>
The SVG file used for the last test (I'm aware that shapes and clones inside groups are not going to get 'prepared' based on the verbs used in the extension, this was just for testing). The mentioned crash can also be reproduced in the GUI following the same steps (select all across all layers, unlink clone, object to path). I'll further investigate and then file a separate report about this particular crash.
</off-topic>"
1662531,2017-02-10 19:33:12 UTC,"With trunk on Ubuntu, the original version of 'Pre-Process File Save As...' failed (spawned inkscape process crashes) with a file which contained a group with a rect and circle, and two clones of that group, one on an additional layer. If all clones are unlinked first, everything ungrouped and moved to a single layer, the extension works as expected. There was no error message returned to the main inkscape process, only the dialog from the second instance notifying about the crash:"
1662531,2017-02-10 19:03:47 UTC,Attached is the output of the extension 'Export > Pre-Process File Save As...' with the (replaced) test version of the script ('prepare_file_save_as - Copy.py') run with lp:inkscape r15500 on Ubuntu 14.04.5.
1662531,2017-02-09 19:30:38 UTC,"attached is a modified version of prepare_file_save_as.py, to be used just for testing purposes. This contains an extra, dummy, command line option, --query-x, which helps to avoid the crash because it operates successfully without a gui. The code also contains some printout of the stderr device."
1662531,2017-02-09 15:32:45 UTC,"the crash in trunk was diagnosed further by printing the output coming from the Popen command. The following code was used to examine the output:
    f = p.communicate()
    err.close()
    inkex.errormsg(str(f))"
1662531,2017-02-08 15:35:01 UTC,"on the 64 bit build, Windows 10, Inkscape 0.92+devel 15458
when I run gdb and run the extension ""Pre-Process File Save As..."", the crash is caused by the following message (popup dialog):"
1662531,2017-02-08 15:05:55 UTC,thanks for testing! apologies in advance for the lengthy response:
1662531,2017-02-08 13:30:56 UTC,"From a user point of view, it would be easier to add an option to the existing dialogs (and create a dialog for the extensions that don't have one), but I understand it would be more difficult to achieve."
1662531,2017-02-07 14:17:40 UTC,"The extensions are posted here for testing purposes. If there is no adverse response within a week or so, then I will commit them.
It is a pleasure to acknowledge helpful discussions with TylerDurden, as well as the code by Ryan Lerch and Moini."
1662531,2017-02-07 14:17:11 UTC,"The extension ""Pre-Process Win32 Vector Print"" will do the same, but will execute ""Win32 Vector Print"" instead of ""Save As..."", to allow printing to a laser."
1662531,2017-02-07 14:16:32 UTC,"Attached is a pair of Python extensions, which will appear on the Extensions->Export menu. The extension ""Pre-Process File Save As..."" will perform the operations:
- save a copy of the file in a temporary location
- open a new instance of Inkscape and load the new file
- perform ""Edit->Select All"" and ""Path->Object to Path""
- load the ""File->Save As..."" dialog to allow saving as .plt, .hpgl, or .dxf
- close the new file silently and return to the original file, which is unchanged."
1662531,2017-02-10 21:39:57 UTC,"On 2017-02-10 22:27 (+0100), Alvin Penner wrote:

> so, if you run the original script with no debugging output, can you
> tell if the Object to Path has been successfully implemented? If I
> understand correctly, this does not crash. If you save this new file as
> normal svg, does it appear that the conversion to path is done?
"
1662531,2017-02-10 21:41:27 UTC,"are you able to successfully execute the original sequence, which was:"
1662531,2017-02-10 21:18:52 UTC,Attached is the output of the extension 'Export > Pre-Process File Save As...' with the (replaced) test version of the script ('prepare_file_save_as - Copy.py') run with lp:inkscape/0.92.x r15365 on OS X 10.7.5 (same crash as with Inkscape trunk on Ubuntu).
1662531,2017-02-10 21:53:58 UTC,"JFTR - the results (with either version of the 'prepare_file_save_as.py' script) with lp:inkscape/0.92.x r15367 on Ubuntu 14.04 are the same as with lp:inkscape r15500 (trunk) on Ubuntu and with lp:inkscape/0.92.x r15365 on OS X. Based on the available platforms I can test on, there is no difference in this regard between stable and trunk."
1662531,2017-02-18 21:12:43 UTC,"okay, scratch that, I see that there are 2 versions, one with 8 args, and one with 9, charming..."
1662531,2017-02-18 20:30:13 UTC,"I am probably going to display my ignorance here, but there appears to be a discrepancy between these two calls.
The glibmm documentation shows 9 arguments, as in:"
1662531,2017-02-18 19:39:27 UTC,"> 4. wrt the question: 'what environment is inherited by inkscape processes spawned via Popen() on Windows'. To the best of my knowledge the answer is 'null'.
"
1662531,2017-02-10 21:51:06 UTC,"sorry, I think our messages crossed each other in the dark, glad to hear it worked!"
1662531,2017-02-18 07:54:14 UTC,"In addition to Hachmann's comment, I would recommend to limit the scope of the change(s) - proposed to avoid the crash of inkscape instances spawned via Popen() in python-based extension scripts - to the affected platform(s), instead of forcing falling back to the C locale entirely on all platforms (even for those not affected by the symptom as exposed with trunk builds for Windows). Changes can be ifdef'd in C/C++ code, and wrapped in a conditional in python (e.g. ""if os.name == 'nt':"" as used elsewhere). If needed, the conditions can be later expanded to include other platforms."
1662531,2017-02-18 03:37:06 UTC,Has there been any feedback (maybe via other channels than this bug report) on the patch proposed for Inkscape proper?
1662531,2017-02-17 15:13:10 UTC,attached are new versions of the extensions 'prepare_file_save_as.py' and 'prepare_print_win32_vector.py'. With these new versions it is not necessary to apply the patch from comment 28. The new versions avoid the crash (on Windows) by passing the environment variable 'LC_ALL' to the spawned version of Inkscape.
1662531,2017-02-18 15:53:09 UTC,"Hi,
    some responses, in no particular order
1. no other feedback, other than this bug report
2. this concerns only those instances of Inkscape that are spawned by Python, not the command line, and also only on Windows
3. with respect to the question of fixing it in Inkscape, versus Python, I think it would be better to do it in Python. The Inkscape code that triggers the issue is: std::locale(""""). This code will cause a crash if triggered from a Python Popen command, but not if Inkscape is called from the command line. As I understand it, this code tells Inkscape to inherit its locale from the parent that called it, which is a reasonable thing to do, and it would not be wise to arbitrarily override it.
4. wrt the question: 'what environment is inherited by inkscape processes spawned via Popen() on Windows'. To the best of my knowledge the answer is 'null'. Any use of the statement std::locale(""""), even in just a print statement, generates an instantaneous crash if triggered by Popen. If triggered by a DOS run command, the answer is 'C'.
5. As far as the impact on Python extensions is concerned: to the best of my knowledge, the only affected extensions would be Synfig output, and the multi-bool extensions, and this current bug report. When I first learned of this problem, I generated output from every single Inkscape output extension I could find, and only Synfig raised a flag. In order for this problem to occur, you need to, first, be on Windows, secondly use Popen from Python, and thirdly use a verb that involves the gui. For example, commands like the commonly-used '--query-x' will not cause a problem because they apparently do not involve the gui. (It is kind of a sad commentary to realize how little these gui verbs are used. Given the potential power of the verb systen, one might have hoped that there would be many more examples of extensions that would be affected, but there are not.)
6. limiting the Python code change to Windows-only seems like a good idea. It could be done with a line of code like this:
if inkex.sys.platform.startswith('win'):
    inkex.os.environ['LC_ALL'] = 'C' # pass this to the spawned Inkscape"
1662531,2017-02-13 14:54:38 UTC,"with respect to the error message obtained in comment 8:
this message comes from libstdc++-6.dll"
1662531,2017-02-16 22:22:40 UTC,"attached is a proposed patch for the crash that occurred in comments 7 and 8. The crash is apparently caused by the fact that the spawned instance of Inkscape does not have a valid locale associated with it. This problem applies only to the spawned instance, not the original.
   The patch uses an alternative definition of the locale, which does exist, and which avoids the crash.
   Any comments would be welcome, since I do not know what the recommended way of defining a locale is."
1662531,2017-02-10 21:56:48 UTC,thanks for testing! I think I am going to try to backtrack in trunk to see if I can find out where the divergence between 0.92.x and trunk started (on Windows)
1662531,2017-02-10 22:00:10 UTC,"Possibly the timing of individual page reloads, and lp's delays in
posting replies via email, causes some confusion in the timeline of the
final posts as seen on the bug report's page? ;)"
1662531,2017-02-20 12:51:31 UTC,"Oh, one other test you could try: in a new CMD shell, set LANG to the same value as happens in localize(), and then launch inkscape (from the same shell)."
1662531,2017-02-11 20:18:43 UTC,"- crash not reproduced in trunk rev 15443
- crash reproduced on Windows in trunk rev 15444
- appears to have been introduced in:
merge lp:~inkscape.dev/inkscape/doc_rotate
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15444"
1662531,2017-02-13 10:10:27 UTC,"Just curious: the prepare script uses '--verb=FileSaveACopy' which opens the file chooser dialog. If your current prefs are set to use GTK open/save dialogs, this would trigger bug #1663884. Could you test the behavior with native file dialogs?"
1662531,2017-02-13 11:10:34 UTC,"I normally use native Windows dialogs, so, yes, these tests were performed with Windows dialogs."
1662531,2017-02-11 13:03:27 UTC,"- the crash mentioned in comment 8, in current trunk, on Windows, is not reproduced on Windows 64 bit build Inkscape 0.92+devel 15113
- both the ""Save As"" and the ""Win32 Vector Print"" work normally with the Pre-Process extensions.
- This is the latest 64 bit trunk build at the website:
http://download.tuxfamily.org/inkscape/win64/"
1662533,2017-02-07 14:29:37 UTC,"Also network templates
https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.network_templates/172/console"
1662533,2017-02-13 09:50:42 UTC,"Change abandoned by Dmitry Belyaninov (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/432268"
1662533,2017-02-13 14:21:09 UTC,"There is param ""intarface"" inside of network generation procedure:"
1662533,2017-02-21 14:02:19 UTC,The bug hasn't been being reproduced during 12 latest runs
1662533,2017-03-28 13:27:11 UTC,"There are no reproduces, thus moving to milestone 11"
1662533,2017-02-10 11:50:52 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/432268"
1662534,2017-02-08 01:08:49 UTC,I'd be curious to see the offending code once it is identified. Thanks.
1662534,2019-09-26 10:54:30 UTC,Chatted with the team a bit. There are two ways forward that we can see:
1662534,2019-09-26 10:13:16 UTC,This is inherited from our use of gpg. There doesn't seem to be a way to have unattended key generation not strip whitespace from the end of the passphrase (or any other option for that matter).
1662536,2020-05-07 07:57:35 UTC,"The issue should be fixed after merging:
https://github.com/mixxxdj/mixxx/pull/2759"
1662544,2019-08-19 21:02:08 UTC,We have first issue with this branch from AUR: https://aur.archlinux.org/packages/terminator-python3-bzr/#comment-704769
1662544,2019-08-19 21:32:23 UTC,Interesting.  I haven't tried using it w wayland.  I know there were some issues with keybinding and wayland but this looks like it can't find the root window.  I'm not sure how to debug that using wayland.
1662544,2019-08-19 21:53:39 UTC,I just came back from Gnome(wayland). Can't reproduce it on my machine. So I'm waiting for futher details from question author.
1662544,2019-08-20 00:22:17 UTC,"OK, so I was able to reproduce this ... kinda."
1662544,2019-08-20 00:38:39 UTC,Hmm.
1662544,2019-08-21 19:19:58 UTC,I just generated PPA on launchpad. There anyone can get python3-version built from my branch. I'll ask some friends to try it.
1662544,2019-08-23 06:45:48 UTC,"Hi,"
1662544,2019-08-19 14:36:51 UTC,"So, we have a deadline of ""mid-November"" before the python2 pkgs are removed from Fedora."
1662544,2019-08-24 18:46:41 UTC,"Just built a new revision. Debian packaging system rules are updated to use newer debianhelper and python3.
Now debianhelper runs tests so most of package dependencies added to build dependencies."
1662544,2019-08-24 19:38:34 UTC,"I'm sorry, Stanislav, but what is the difference between"
1662544,2019-08-25 06:35:52 UTC,"Originally, I was pickimg the layout value from a list that was modified so that all values are lower-cased. But that means if there was a layout that had upper-case characters, non-existent layout would be picked. The newer version fixes that by picking from the original list."
1662544,2019-08-25 08:45:18 UTC,"Oh, now I see. Thank you."
1662544,2019-08-25 09:27:04 UTC,"I'm sorry for holding you on this discussion, but I interested in you opinion about this approach I found:"
1662544,2019-08-25 12:12:28 UTC,"Sure, you can use that"
1662544,2019-08-25 12:42:56 UTC,"Ok, commited it."
1662544,2019-08-25 12:51:18 UTC,Stephen Boddy still didn't answer neither to my e-mail nor to message on Launchpad. I read some threads in other bug reports and see that project looks like almost maintainerless. Do anyone know if projects on launchpad can have several maintainers?
1662544,2019-08-24 18:48:08 UTC,"Debs for Bionic, Disco and Eoan are available in mt PPA: https://code.launchpad.net/~hellodeargrandma/+archive/ubuntu/ppa."
1662544,2019-08-19 13:31:45 UTC,"Whoops, nm.  I just saw it.  Thanks"
1662544,2019-10-21 19:32:33 UTC,"Ugh.  It looks like the API for that call has changed, and the code was mysterious to begin with, as evidenced by this docstring:"
1662544,2019-08-18 22:02:29 UTC,"Yes, thank you for `__next__`. Fixed it."
1662544,2017-02-08 12:10:27 UTC,"Rahmadani, just so I know, are you assigning this to yourself because you intend to work on it? If so, great! I'll set the bug to ""In Progress"". If on the other hand you didn't mean to or didn't realise what you did, let me know and I will unassign this."
1662544,2017-02-12 05:06:23 UTC,"Rahmadani, this project had a user who vandalised translations and changed bug assignee and status for no good reason, and refused to respond when contacted. After I had them banned, they came back and did it again under a new username, which also got banned."
1662544,2017-02-12 05:11:12 UTC,"Oh, and if you ignore me and assign the ticket back to you, I will assume you are the vandal. Then I will ask that you are banned again."
1662544,2018-04-05 16:37:38 UTC,"I have a working branch using Python 3. I need to do some more testing and split the changes into nice commits, and I'll submit it for review / wider testing."
1662544,2018-04-19 18:41:07 UTC,"Here's my work, split in nice, small commits:"
1662544,2018-08-24 15:43:54 UTC,"Hello,"
1662544,2019-01-15 11:54:45 UTC,Ping? Can we get this reviewed / merged? I haven't experienced any issues since I posted it
1662544,2019-02-23 09:41:26 UTC,"Hey,
I only found a small issue while going through your branch as I ran pylint on it. There's one missed usage of cmp() in `terminatorlib/layoutlauncher.py`."
1662544,2019-08-03 15:38:10 UTC,"Hi, I'd also like to see terminator to be ported to Python 3 and since we seemingly have a working patch, I'd like to ask... Is there anything new in this matter? Are we waiting for anything particular? Thanks!"
1662544,2019-08-03 15:47:20 UTC,"Oh, it seems that for the last two years the only commits added to terminator have been automated translation updates, am I right? I had no idea that the upstream is this not-alive. :-/"
1662544,2019-08-03 19:05:51 UTC,"Yes, seems like developing is not so swift. I'd already tried to run this branch on my machine, but something went wrong. May be it's not a problem in project."
1662544,2019-08-18 02:05:38 UTC,"Huh, I've done some work on getting terminator working with python3, prompted by this Fedora (I'm one of the fedora maintainers) bug: https://bugzilla.redhat.com/show_bug.cgi?id=1737872"
1662544,2019-08-18 07:28:33 UTC,"Hi, MattRose!"
1662544,2019-08-18 14:39:16 UTC,I'll branch from pochu's branch and apply the patch
1662544,2019-08-18 15:56:46 UTC,"I just wrote to:
* Stephen Boddy
* Emilio Pozuelo Monfort
* Stanislav Laznicka"
1662544,2019-08-18 17:15:52 UTC,Submitted a package to ArchLinux User Repository (AUR): https://aur.archlinux.org/packages/terminator-python3-bzr/
1662544,2019-08-18 19:02:35 UTC,That looks really good.  It works flawlessly except for one minor change (__next__ needs to be changed to next on line 85 of terminatorlib/searchbar.py).
1662544,2019-10-20 16:14:57 UTC,"Hi Grandma, others,"
1662544,2019-08-19 13:30:14 UTC,Can you push that change back into your branch?  I didn't see it there and I'd like to just keep pulling your changes rather than pushing my own branch and trying to keep it in sync :)
1662544,2019-10-21 01:09:50 UTC,Cool.  I think this was probably caused by one of the manual conversions that Grandma or I did.  I'll see if I can code up a fix
1662544,2019-10-21 22:23:08 UTC,Hi everyone.
1662544,2020-04-09 09:49:42 UTC,"Thanks Markus for taking that step forward and moving the project elsewhere so that we can keep maintaining it. I wanted to do that too, but since you've done it first, I'll just offer my help in maintaining it and reducing the bus factor. My github handle is @epozuelo."
1662544,2020-04-08 14:43:14 UTC,"Unfortunately, nobody with commit access has actually updated the code or released anything in over 3 years now.  This has led to a situation where distro maintainers have had a hard choice."
1662544,2020-04-07 04:18:12 UTC,"What I meant by ""land"" was to commit it into the Terminator bzr repo, since I have commit access to it.  However, it sounds like there's been too much divergence in forks for there to be much value in bringing the bzr tree up to date."
1662544,2020-04-05 12:06:13 UTC,"This issue will be addressed in the new fork of Terminator on GitHub
https://github.com/gnome-terminator/terminator/pull/6"
1662544,2020-03-17 09:03:56 UTC,Python3 porting was mainly Emilio's work.
1662544,2020-03-17 03:08:40 UTC,"I have been using the Ubuntu terminator, that includes Egmont's python3 work, with few problems.    I think having the gtk3 branch moved to python3 would make maintenance simpler.  If no one has an objection I'd like to go ahead and land this work."
1662544,2020-03-16 17:39:07 UTC,"There's another, independent python3 fork of terminator."
1662544,2019-12-18 18:20:22 UTC,"I think there's a few compatibility issues with running on the latest vte, but this is a good start to tracking them down.  I may send you emails if I get stuck with stuff :)"
1662544,2019-12-18 17:32:10 UTC,"> I've been meaning to look at upgrading the python vte library that terminator uses
"
1662544,2019-12-18 17:25:08 UTC,"> [Emilio] Stephen, if you're happy to give me maintainer access, that'd be great.
"
1662544,2019-12-18 09:51:18 UTC,"> On a meta note, this is a lot of duplication of effort. I'll reach out to the maintainers
> of the debian port to see if we can co-ordinate this a little better, as Stephen seems
> to have stopped responding again.
"
1662544,2019-12-18 03:52:25 UTC,"Added Egmont's DND fix to the fedora package.  A fix for the first bug in the list seems fairly easy to reproduce, the other one, well, I've been meaning to look at upgrading the python vte library that terminator uses, but I haven't yet and there's some deep gtk voodoo there..."
1662544,2019-12-17 22:46:06 UTC,"So, I know that I should have taken the debian fixes and applied that, but instead, I took Roman's branch, did a big diff between that and the 1.91 release tarball and submitted that to fedora Rawhide.  It should, if there are no subsequent releases,  land in Fedora 32, which is in time for the big python2 deprecation that is happening in F32."
1662544,2019-11-15 23:29:52 UTC,"Stephen, whenever you come back to this, I recommend that you do some commit-squashing and similar bookkeeping type of work on Roman's branch, rather than merging it as-is. It's some extra work, but results in a much cleaner commit history."
1662544,2019-12-18 14:14:20 UTC,"I would love to be able to do this, but none of us have the proper access to create releases.  I've asked Stephen for maintainer access as well, but he hasn't responded that I'm aware of."
1662544,2019-11-15 18:28:35 UTC,New python3 bug (reincarnation of bug #1518705):
1662544,2019-10-22 03:03:28 UTC,Yay!  r1852 fixes that problem.  Thanks Grandma.  That was a good catch on that.
1662544,2019-10-22 08:03:37 UTC,Thanks!
1662544,2019-11-15 19:57:05 UTC,This patch fixes DND. Should be tested at least from Nautilus and from Firefox (different code paths are executed in those cases).
1662544,2019-10-22 14:27:52 UTC,This has been on my mind for a while now.  I think Terminator is a fantastic program but it is in real danger of being bitrotted away and becoming un-useable.
1662544,2019-10-22 17:26:26 UTC,"Nitpicking: I don't fancy the name ""python3-terminator"". The vast majority of users don't give a damn about which programming language it is written in. IMO the name shouldn't refer to it."
1662544,2019-10-22 17:47:30 UTC,"Whoops.  I didn't mean to send comment 44 to the bug.  I don't want to take over from Stephen and Chris without their blessing, and even if I were to fork it, which is looking more and more likely, I wanted to make the heritage of the project clear.  Another name I had in mind was RoboTerm, as an homage to the ""Robot future of Terminals"" tagline."
1662544,2019-10-22 14:26:41 UTC,"I was going to respond to the bug, but I think it's best if we take this
private for now.  This has been on my mind for a while now.  I think
Terminator is a fantastic program but it is in real danger of being
bitrotted away and becoming un-useable.  I have been seriously thinking
that it would be a good idea if I were to fork the repository into
github and call the new package python3-terminator.  I'm very glad to
see other people have been thinking along the same lines.  I'm a little
wary of taking on the maintainership myself as I don't really know the
gobject api very well, but it seems to have come to that point.  I would
be eternally grateful for a little help in getting the process going and
some ongoing maintainership.   I'm not sure where to start right now."
1662544,2019-10-22 18:55:32 UTC,Creating an issue. Trying to describe the current state of things.
1662544,2019-10-22 19:41:27 UTC,"Placed it here: https://bugs.launchpad.net/terminator/+bug/1849375
Just described the situation and moved there some questions we asked in this thread."
1662544,2019-11-14 10:33:50 UTC,I've just realized that there's been a truly unfortunate lack of information flow here.
1662544,2019-11-15 18:10:12 UTC,1.91 tarball is revision 1749 (according to the bzr tag).
1662544,2019-11-15 18:20:58 UTC,Debian's python3_drag_n_drop.patch might be equivalent to Roman's the latest commit (1852). In that case there's nothing here to do.
1662544,2019-10-22 18:37:35 UTC,"I did think about fork too, but I prefer to do it openly to let others see the history."
1662548,2017-02-07 15:23:40 UTC,This is TROVE-2016-10-001 .
1662548,2017-04-10 12:47:33 UTC,Zesty has 0.2.9.10-1ubuntu1. I think this might mean that this issue is fixed in Zesty? It isn't clear to me.
1662548,2017-08-13 14:05:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662548,2017-08-13 14:08:03 UTC,0.2.7 is also unsupported since August 1: https://blog.torproject.org/blog/tor-0315-alpha-released
1662548,2017-09-19 02:49:30 UTC,"Tor 0.2.9.11 is now in Xenial and Zesty, marking Xenial as fix released."
1662549,2017-02-07 15:34:52 UTC,"Fix proposed to branch: stable/7.0
Review: https://review.openstack.org/430313"
1662549,2017-02-08 13:08:17 UTC,"Reviewed:  https://review.openstack.org/430313
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=832b2c5b0374b92c09002f3ab7384ccfe75340d3
Submitter: Jenkins
Branch:    stable/7.0"
1662565,2020-04-11 09:53:55 UTC,"Reproduced in 0.92.4, not reproduced in Inkscape 1.1-dev (c990a67, 2020-04-09), Windows 10 - neither with SVG1.2 nor SVG2 flowed text. Please reopen on http://inkscape.org/report if the problem occurs again."
1662565,2017-02-08 13:34:45 UTC,Thanks for taking the time to file report!
1662565,2017-02-08 13:41:53 UTC,"Also reproduced with 0.91, 0.48.5 and 0.45.1. Not a recent regression."
1662568,2017-02-08 13:21:16 UTC,"Also note that if you switch from openvswitch firewall driver to iptables firewall driver, then security groups won't work as existing instances won't have qbr but tap is plugged directly to br-int. Maybe we should document that migrations of firewalls are not supported yet."
1662568,2017-02-08 14:52:59 UTC,"@jlibosva, yeah, I'm aware of absence of auto migration yet. I just presumed that ovs flows should be cleared anyway on firewall switch. I'm a bit of a loss tere, as I can't find a way to get a working environment (apart from manually destroying all the vms) when ovs-agent is overloaded."
1662571,2017-11-04 23:02:43 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/456591
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1662571,2017-04-13 12:29:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456591"
1662571,2020-04-28 11:08:41 UTC,"Since I am not active anymore, I would like to remove myself from the assignee. Its open for anyone else to take up."
1662571,2017-04-16 07:48:46 UTC,"To be clear, we don't want to prevent this at the API level because it's convenient for the user. This bug can be used to optimize inside the firewall implementations though."
1662573,2017-02-07 16:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1662573,2017-02-07 18:23:28 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1662573,2017-02-08 09:00:57 UTC,apport information
1662573,2017-02-08 09:00:59 UTC,apport information
1662573,2017-02-08 09:01:00 UTC,apport information
1662573,2017-02-08 09:01:01 UTC,apport information
1662573,2017-02-08 09:01:04 UTC,apport information
1662573,2017-02-08 09:01:08 UTC,apport information
1662573,2017-02-08 09:01:09 UTC,apport information
1662573,2017-02-08 09:01:12 UTC,apport information
1662573,2017-02-08 09:08:18 UTC,apport-collect with edited hostname
1662573,2017-02-08 09:12:02 UTC,"In reply to comment #2, we're using ksplice to patch the kernel, but we haven't upgraded the ubuntu package, lately."
1662573,2017-02-08 09:30:11 UTC,This change was made by a bot.
1662573,2017-02-08 09:01:03 UTC,apport information
1662573,2017-02-08 09:01:06 UTC,apport information
1662586,2017-03-29 19:22:03 UTC,"Even though network-restarts are serialized w/ hooks, this bridge setup will still affect customers who attempt to deploy juju services to containers on the controller machine."
1662586,2017-02-08 15:48:45 UTC,https://github.com/juju/juju/pull/6944
1662586,2017-02-14 23:04:45 UTC,"With juju 2.1 rc1, it now appears that the network reset is serialized with the charm hooks."
1662586,2017-03-16 14:50:22 UTC,Fixed in juju 2.1 final.
1662597,2018-07-25 14:29:29 UTC,Adding a link to technical specs Equinox created for us to fix this bug. https://yeti.esilibrary.com/dev/public/techspecs/metarec-copy-counts.pdf
1662597,2017-02-07 17:09:58 UTC,Also adding Mike Rylander's suggestion from bug 1629108 for addressing this issue:
1662600,2017-02-07 17:26:22 UTC,"Since libibverbs was optional, I uninstalled it.  After doing so, my build seems to have progressed past this error."
1662600,2020-11-08 09:11:13 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1662600,2021-01-08 04:17:22 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1662601,2017-02-16 00:44:58 UTC,I rephrased this issue as a confusing error message bug.
1662601,2017-02-16 00:36:44 UTC,"""bug"" - probably not a bug but more likely a configuration issue like Anastasia suggests."
1662601,2017-02-16 00:36:26 UTC,I'm hitting this bug testing a cloud that otherwise works fine.
1662601,2017-02-15 06:06:55 UTC,@Larry
1662617,2018-09-07 17:54:07 UTC,Switching to ibus solved the problem.
1662617,2018-07-19 22:53:35 UTC,Calculator display showing bionic desktop capture in display area (no longer transparent) with overtyping and gridding in the number display.
1662617,2018-07-19 22:52:32 UTC,Calculator worked flawlessly in Advanced mode in 16.04 (and before). Upgrade to 18.04 and this bug appeared (the bionic desktop visible in the display window). Using the calculator produced overtyped characters and weird gridding between the numbers displayed (see attached). Switching from xim to ibus seems to have solved it.
1662617,2018-04-29 10:43:40 UTC,Switching to ibus solved the problem.
1662617,2017-08-30 08:49:39 UTC,Switching to ibus fixed it
1662617,2017-08-28 15:50:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662617,2017-08-29 15:07:56 UTC,"Yes, I confirm that the existence of the line below:"
1662617,2017-08-29 09:30:48 UTC,do you use xim/have a ~/.xinputrc config? that looks similar to bug #1620806
1662617,2017-08-28 15:50:27 UTC,"Same issue here, screenshot attached."
1662617,2017-06-18 03:39:53 UTC,"I also experienced this issue in 16.10 (also with Intel graphics), as noted in a comment on another bug[1]. But, for what it's worth, I don't experience the issue anymore in 17.04."
1662617,2017-04-14 22:15:23 UTC,"I have similar error, however opening top-left menu fixes it until window closing."
1662617,2017-08-29 17:21:28 UTC,Same here - solved for me.
1662622,2017-03-01 05:42:13 UTC,"Reviewed:  https://review.openstack.org/438696
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-security/commit/?id=83e3c206e8bbd8344a3770f8c2cff2651f528d5c
Submitter: Jenkins
Branch:    stable/newton"
1662622,2017-04-03 15:21:54 UTC,This issue was fixed in the openstack/openstack-ansible-security 14.2.0 release.
1662622,2017-02-27 20:51:37 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/438696"
1662622,2017-03-09 15:46:13 UTC,"Reviewed:  https://review.openstack.org/430900
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-security/commit/?id=2a2b1e619f299b6d408ba36bed4763673caf7634
Submitter: Jenkins
Branch:    stable/newton"
1662622,2017-02-27 13:24:08 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/438491"
1662622,2017-02-08 13:16:29 UTC,Backported for stable/newton with https://review.openstack.org/#/c/430900/.
1662622,2017-02-08 12:25:53 UTC,"There seems to be a workaround for this:
https://github.com/openstack/openstack-ansible-security/commit/23af709fff689518f7443d29bdf8f2ee7287f42d"
1662622,2017-02-08 11:56:03 UTC,"So, the handler is triggered, when auditd oder audisp configuration files are touched."
1662622,2017-02-27 14:24:36 UTC,"Reviewed:  https://review.openstack.org/438491
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-security/commit/?id=86cc1449d4569d879b5195d1a0be13b948268645
Submitter: Jenkins
Branch:    stable/newton"
1662622,2017-02-08 09:08:41 UTC,"Maybe it will be sufficient to tell auditd to reload it's configuration instead of restarting it, since the handler seems to be triggered when auditd.conf is changed."
1662624,2017-02-07 19:08:51 UTC,Thanks for the initial diagnosis Octave!
1662624,2017-02-08 23:47:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/431229"
1662624,2017-08-02 20:21:37 UTC,Automatically unassigning due to inactivity.
1662624,2017-08-02 20:23:18 UTC,Reassigning since this is being worked in review and generating a lot of discussion.
1662624,2018-04-09 20:35:41 UTC,Automatically unassigning due to inactivity.
1662626,2017-07-05 08:38:11 UTC,"Change abandoned by Joshua Hesketh (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/476278
Reason: This branch (stable/mitaka) is at End Of Life"
1662626,2017-08-12 01:22:28 UTC,"Reviewed:  https://review.openstack.org/470387
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=017e853b950ddc10dab4ebab37e64cece40f274f
Submitter: Jenkins
Branch:    stable/newton"
1662626,2017-08-28 09:55:20 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1662626,2018-02-02 10:04:38 UTC,"Reviewed:  https://review.openstack.org/508640
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a0525f650af1fa763eb7e58185644f9e7fe1a3dd
Submitter: Zuul
Branch:    stable/ocata"
1662626,2017-09-30 01:26:11 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/508641"
1662626,2017-10-13 04:41:22 UTC,"Change abandoned by Liping Mao (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/508641"
1662626,2017-06-21 21:55:09 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/476278"
1662626,2017-09-30 01:25:22 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/508640"
1662626,2017-06-02 18:12:16 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/470387"
1662626,2017-10-13 04:41:08 UTC,"Change abandoned by Liping Mao (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/508640"
1662626,2017-04-25 21:21:55 UTC,"Reviewed:  https://review.openstack.org/457023
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=012fa9353ff18d3d52120fd42a2ec25dbc5a02b7
Submitter: Jenkins
Branch:    stable/ocata"
1662626,2017-05-08 22:10:21 UTC,This issue was fixed in the openstack/nova 15.0.4 release.
1662626,2017-02-07 18:40:22 UTC,Still digging on the details with this bug. Looking at if we keep seeing the same thing several times.
1662626,2017-02-07 19:00:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430400"
1662626,2017-02-07 19:15:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/430404"
1662626,2017-02-14 21:17:55 UTC,Is this really an ocata release candidate potential bug? It sounds pretty latent and something we can backport to stable/ocata after 15.0.0 is released. Or was this the result of a regression in Ocata itself?
1662626,2017-02-25 04:09:03 UTC,"Reviewed:  https://review.openstack.org/430400
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b706155888d740841d745c52aae543cf82fab0bc
Submitter: Jenkins
Branch:    master"
1662626,2017-03-27 13:30:32 UTC,"Reviewed:  https://review.openstack.org/430404
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b56f8fc2d1392f4675a5baae0977e4817a362159
Submitter: Jenkins
Branch:    master"
1662626,2017-04-14 09:24:17 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1662626,2017-02-08 11:53:35 UTC,"So there are kind of two problems here, a race in undefine domain that leads to occasional live-migration failures when you run lots and lots of live-migrations."
1662626,2017-04-15 18:58:46 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/457023"
1662628,2017-02-08 13:49:58 UTC,"+1 Hans,"
1662628,2017-02-09 17:32:42 UTC,"No worries guys, I will modify the method on which you will be able to pass the required parameter."
1662634,2017-02-07 20:18:40 UTC,'min-snapcraft-version' perhaps.
1662637,2017-02-08 08:56:35 UTC,"Could we simply get rid of it as Nova already did? API rate limiting seems like something that should be done outside of OpenStack APIs. If I recall correctly, Rackspace had implemented external rate limiting in their cloud."
1662637,2017-02-08 15:19:15 UTC,"That would actually be my preference too. Just has some implications for our API and cinderclient, although those pieces could just stay where they are and just continue to not work."
1662642,2017-02-08 01:36:52 UTC,complete log of failing unit is here http://paste.ubuntu.com/23951608/
1662642,2017-02-08 00:39:04 UTC,ok testing now should have results within an hour.
1662642,2017-02-08 00:16:35 UTC,"Narinder, please take this for a test drive: cs:~thedac/percona-cluster-0"
1662642,2017-02-08 00:00:30 UTC,The issue is the package name that debconf-set-selections uses.
1662642,2017-02-08 01:35:49 UTC,ok original issue of install have been fixed. But hook cluster relation failed.
1662660,2017-02-08 07:08:48 UTC,"Just some general triage:
- can you reproduce the problem from a live CD (xenial or zesty)?
- can you reproduce the problem on your current system with a guest session user?
- anything special about your installation?"
1662660,2017-02-09 09:05:10 UTC,"I was hoping that I could guide someone knowledgeable through some logical steps, and, possibly find a simple error in one of my config files. My reasoning follows:"
1662660,2017-02-09 17:33:19 UTC,you wrote a lot in #4 but did not answer the questions from #3
1662660,2017-02-09 18:10:55 UTC,"1. I don't have a live CD for xenial or zesty. I have one for yakkety, and I know I will spend hours trying to figure out which additional packages I need in order to get to the point of trying to reproduce my problem.
2. I did try the experiment with a different account and got the same result.
3. I did summarize what might be special about my system."
1662660,2020-12-17 18:18:00 UTC,Does this issue still affect cups-pdf 3.0.1 packages?
1662661,2017-02-07 20:38:50 UTC,"-- Didn;t see that there were still 47 packages to update --
After applying upgrade, issue still exists.
New policy info:"
1662661,2017-02-09 13:49:31 UTC,What does ls -l show at the grub prompt?  I noticed that your new volume is a whole disk volume rather than being partitioned.  I wonder if that is the cause?
1662661,2017-02-13 21:04:32 UTC,"Here's the output I get:
grub> ls -l
Device proc: Filesystem type procfs - Sector size 512B - Total size 0KiB
Device hd0: No known filesystem detected - Sector size 512B - Total size 52428800KiB
  Partition hd0,msdos5: No known filesystem detected - Partition start at 500736KiB - Total size 51927040KiB
  Partition hd0,msdos1: Filesystem Type ext* - Last modification time 2017-02-13 20:46:41 Monday, UUID [long-uuid] - Partition start at 1024KiB - Total size 498688KiB
Device hd1: No known filesystem detected - Sector size 512B - Total size 52428800KiB
Device fd0: No known filesystem detected - Sector size 512B - Total size 1440KiB"
1662661,2017-02-13 22:24:36 UTC,"Also, here is the info from fdisk.
=====
# fdisk /dev/sda"
1662661,2020-03-02 12:53:02 UTC,"This warning is still appearing in ubuntu 18.04, it seems indeed to be related to my partitionless PV as the message doesn't appear when i pull it out of the VG"
1662667,2017-02-07 22:15:13 UTC,"And, I should read better. It seems to be a problem with SRU searching in general."
1662667,2017-02-08 18:25:05 UTC,"Jason,"
1662667,2017-02-08 20:11:40 UTC,"Mike,"
1662667,2017-02-09 01:52:36 UTC,"Looks like it fixes it. The log entries are different now, but here's the Mozart search done again:"
1662667,2019-05-15 17:29:51 UTC,I'm setting this old bug to fix released because the fix was released in 2.12-beta with the branch from bug 1005040.
1662667,2017-02-07 21:59:00 UTC,Here are log entries from the Z39.50 search. (Don't mind the timestamp differences. My VM apparently can't decide if it is in EST or UTC.)
1662668,2020-12-29 22:16:16 UTC,"Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1662682,2017-02-10 15:59:43 UTC,"@Egmont OSC (Operating System Command?). I'm not familiar with this but I
can look into it."
1662682,2017-02-25 08:57:37 UTC,"Chris, the list of escape sequences is just part of the vte code base and probably mostly for internal use. I'm not the best (that's Egmont) to explain, but from Egmont's last comment the vte component does not emit any signals for any escape signals other than the two discussed. So Terminator cannot do anything based on all the other signals."
1662682,2017-02-10 18:47:29 UTC,I meant the window-title-changed and cur-dir-uri-changed stuff. There's no generic framework for notifying about unrecognized OSCs.
1662682,2017-02-10 18:25:56 UTC,"@Chris: Not sure we're on the same page. My thought was:
1.Create vte
2.Add callback for the OSC signal* to call function to insert prepared_text, and remove timer
3.Spawn shell
4.Add gtk timer to call function to remove OSC callback
5.Return control to Gtk"
1662682,2017-02-10 16:49:23 UTC,"OSC (yup operating system command) is an escape sequence beginning with ""\e]"" (rather than the much more typical ""\e[""). E.g. ""\e]0;asdf\a"" changes the title, ""\e]7;file:///bin\a"" changes the concept of working directory (so that the terminal emulator can open a new directory there). When such an escape sequence is encountered, Terminator is notified about them."
1662682,2017-02-09 10:01:15 UTC,"@Stephen I guess misusing the first OSC 0 or OSC 7 is okay as an upper limit on the timer, to send the string faster. You should, however, expect that users mess with their bash/zsh settings and one may not emit these at all. You could still have a safeguard cap on the timer, on specify in the docs (maybe on the UI too) that you do rely on OSC 7. In the latter case, it should be OSC 7 (working dir) and not OSC 0 (title) because a user might want to disable the title for good reasons (e.g. I use the title for something more useful), while OSC 7 shouldn't hurt anyone so they should keep it at place."
1662682,2017-02-25 05:08:59 UTC,Hi folks.
1662682,2017-02-09 02:49:35 UTC,"Hmmm. OK, so that's +1 from Egmont."
1662682,2017-02-09 02:03:48 UTC,"I am aiming for the second behaviour that you described which is why I
opted to use feed(). When you press enter, that command will be executed as
if you typed it yourself. I don't get any error messages?"
1662682,2017-02-09 01:07:11 UTC,"I think it'd be a cool new feature. Actually I'm wondering why no terminal emulator implemented this so far. I have also thought of it at some point, but was lazy to file an enhancement request against gnome-terminal (and I _guess_ the maintainer wouldn't have been so keen on this)."
1662682,2017-02-08 17:25:11 UTC,"Hi Stephen,"
1662682,2017-02-08 17:17:16 UTC,My first patch was missing a commit I had made to my repo.
1662682,2017-02-08 13:23:52 UTC,"OK, so a few musings, from a quick visual check (no actual test)"
1662682,2017-02-09 09:58:38 UTC,"Oh, sorry, you're doing a terminal.feed() which actually translates to a Vte.feed_child() and not a Vte.feed(). So it's okay."
1662688,2018-12-13 10:39:48 UTC,"I think a temporary fix could be for it to work like Dash to Panel, which if hovered while dragging, activates the shell overview and hence allows to drop on the chose window."
1662699,2017-04-14 09:24:11 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1662699,2017-02-28 16:00:03 UTC,This issue was fixed in the openstack/nova 13.1.3 release.
1662699,2017-02-27 20:28:52 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1662699,2017-02-17 04:58:01 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc2 release candidate.
1662699,2017-02-10 14:25:36 UTC,"Reviewed:  https://review.openstack.org/431610
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dce8618166d80dc6cf2854920f6275eee73b8d84
Submitter: Jenkins
Branch:    stable/newton"
1662699,2017-02-10 14:26:08 UTC,"Reviewed:  https://review.openstack.org/431628
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9b3c4736a35b0db6ceff38786fb706a6a312a7ab
Submitter: Jenkins
Branch:    stable/mitaka"
1662699,2017-02-09 16:12:29 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/431628"
1662699,2017-02-09 15:41:26 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/431610"
1662699,2017-02-09 15:20:18 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/431595"
1662699,2017-02-09 05:45:51 UTC,"Reviewed:  https://review.openstack.org/430497
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e34f05edb2efc79bfdd8e73cca8fa02ea6ef2d60
Submitter: Jenkins
Branch:    master"
1662699,2017-02-08 21:49:53 UTC,Fix is here: https://review.openstack.org/#/c/430497/
1662699,2017-02-07 22:56:52 UTC,"Changing shade to pass -1, '-1', or to leave the boot_index value out entirely all makes it work. See https://review.openstack.org/430465"
1662699,2017-02-10 14:02:38 UTC,"Reviewed:  https://review.openstack.org/431595
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ff1925ae47245f056690889a6e063ebce1bb7a80
Submitter: Jenkins
Branch:    stable/ocata"
1662725,2018-01-25 08:59:17 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3636
1662725,2017-10-11 09:19:06 UTC,"""Workaround"" from Kenny Gryp helps, but (in our workload) for ~30 minutes, then it fails again, restarting, working for some time, fail, etc. Not an option for us."
1662725,2017-10-09 08:23:23 UTC,Confirming this (or very similar) issue still exists in our production configuration:
1662725,2017-09-27 23:13:06 UTC,The issue was already fixed in 5.7.18 with the following commit:
1662725,2017-08-30 23:19:59 UTC,NOTE FOR PEOPLE HAVING THIS ISSUE:
1662725,2017-08-30 23:19:46 UTC,SHOW ENGINE INNODB TRANSACTIONS output:
1662725,2017-08-30 23:19:51 UTC,Given the fact that this is also a 'supremum pseudo-record' issue. This bug might be very likely related: https://bugs.mysql.com/bug.php?id=86486
1662725,2017-02-24 10:56:34 UTC,I was able to repeat generation of such binary logs on slave using dump of customer's data and entries in their binary log. I cannot repeat same issue with artificial SQL.
1662725,2017-03-08 04:10:23 UTC,Master and slave option file content for the above MTR:
1662725,2017-03-07 13:08:27 UTC,"--source include/have_innodb.inc
--source include/have_binlog_format_row.inc
--source include/master-slave.inc
--source include/count_sessions.inc"
1662725,2017-02-25 10:11:58 UTC,I added smaller test case (requires 4 tables instead of full database) to the ticket.
1662725,2017-08-30 23:19:34 UTC,"This is what you would get in INNODB_LOCKS:
perconaserver mysql> select * from information_schema.INNODB_LOCKS;
+------------------+-------------+-----------+-----------+------------+------------+------------+-----------+----------+------------------------+

| lock_id          | lock_trx_id | lock_mode | lock_type | lock_table | lock_index | lock_space | lock_page | lock_rec | lock_data              |


+------------------+-------------+-----------+-----------+------------+------------+------------+-----------+----------+------------------------+

| 2238925:347:13:1 | 2238925     | X         | RECORD    | `xa`.`t1`  | PRIMARY    |        347 |        13 |        1 | supremum pseudo-record |
| 2238923:347:13:1 | 2238923     | S         | RECORD    | `xa`.`t1`  | PRIMARY    |        347 |        13 |        1 | supremum pseudo-record |


+------------------+-------------+-----------+-----------+------------+------------+------------+-----------+----------+------------------------+"
1662731,2017-03-07 20:23:28 UTC,"I tested this on a virtual machine running 17.3 and ran into the same issue. Although my entire system did not freeze, just the Update manager."
1662733,2017-02-08 09:23:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662733,2017-02-14 07:07:42 UTC,Looks like this is similar to bug 1625846.
1662733,2017-02-28 12:30:09 UTC,"Agreed, this is the same underlying issue with ""focus-loss"" events that manifests in lp:1625846. We should ensure that any plan to resolve addresses both usecases."
1662733,2017-11-03 16:30:25 UTC,Syncing task from Mir.
1662743,2017-02-14 10:22:41 UTC,@fjkong we can discuss this in detail at irc. I'm always online.
1662743,2017-02-14 09:52:17 UTC,"settings for hot key is in fcitx not in sogou IM, you can select the last tab and scroll down, there will be '打开fcitx设置'"
1662743,2017-02-14 10:17:28 UTC,here is what i've done in fcitx settings https://ptpb.pw/anzh.jpg . It cannot be applied.
1662746,2017-03-20 04:04:37 UTC,Upstream made changes to the RPM scripts/configuration in 5.7.14 to facilitate the install of multiple client library versions. Please include the changes in your release of 5.7.14.
1662746,2018-01-25 08:59:16 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3637
1662746,2018-01-18 08:30:55 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1951
1662748,2017-02-08 12:48:23 UTC,"> we are saying that for using source=image dest=local/None(seems None is
> treated as local) we should also provide image ref, but the fact is that if do so,
> we got:
"
1662748,2017-06-27 19:26:08 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1662754,2017-02-08 04:11:16 UTC,"Kernel log is below:
[ 3629.712878] BUG: unable to handle kernel paging request at fffffffffffffff3
[ 3629.796735] IP: [<ffffffff813ffce0>] strlen+0x0/0x20
[ 3629.856430] PGD 1e0d067 PUD 1e0f067 PMD 0
[ 3629.906140] Oops: 0000 [#4] SMP
[ 3629.945243] Modules linked in: xt_nat xt_tcpudp veth xt_comment ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overlay aufs arc4 ath10k_pci ath9k ath10k_core ath9k_common ath9k_hw ath mac80211 kvm_amd kvm uas irqbypass cfg80211 k10temp sp5100_tco r8169 i2c_piix4 mii shpchp mac_hid iptable_filter ip_tables ip6table_filter ip6_tables x_tables autofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci
[ 3630.543640] CPU: 0 PID: 2479 Comm: snap-confine Tainted: G      D         4.4.0-59-generic #80-Ubuntu
[ 3630.654077] Hardware name: PC Engines APU/APU, BIOS 4.0 09/08/2014
[ 3630.728123] task: ffff88007a338000 ti: ffff88007a388000 task.ti: ffff88007a388000
[ 3630.817768] RIP: 0010:[<ffffffff813ffce0>]  [<ffffffff813ffce0>] strlen+0x0/0x20
[ 3630.906581] RSP: 0018:ffff88007a38ba20  EFLAGS: 00010246
[ 3630.970226] RAX: ffff88007a38bb20 RBX: fffffffffffffff3 RCX: 0000000000000000
[ 3631.055710] RDX: 0000000000000151 RSI: fffffffffffffff3 RDI: fffffffffffffff3
[ 3631.141195] RBP: ffff88007a38ba38 R08: ffff880060a4c93b R09: ffff88007a38ba94
[ 3631.226679] R10: 000000000000000e R11: ffff880060a4c934 R12: ffff88007a701240
[ 3631.312163] R13: ffff88007a338000 R14: ffffffff8139b3d0 R15: 00000000fffffff3
[ 3631.397650] FS:  00007f0e8d98b740(0000) GS:ffff88007de00000(0000) knlGS:0000000000000000
[ 3631.494574] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3631.563417] CR2: fffffffffffffff3 CR3: 000000006719a000 CR4: 00000000000006f0
[ 3631.648901] Stack:
[ 3631.673030]  ffffffff8112333a ffff88007a701240 ffff88007a38bb00 ffff88007a38ba60
[ 3631.762464]  ffffffff8139b438 ffff88007a701240 ffff88007a38bb00 ffff88007a338000
[ 3631.851901]  ffff88007a38bad8 ffffffff81370498 ffffffff81229680 ffff88007a38baf0
[ 3631.941337] Call Trace:
[ 3631.970675]  [<ffffffff8112333a>] ? audit_log_untrustedstring+0x1a/0x30
[ 3632.049919]  [<ffffffff8139b438>] audit_cb+0x68/0x3f0
[ 3632.110444]  [<ffffffff81370498>] common_lsm_audit+0x1b8/0x740
[ 3632.180330]  [<ffffffff81229680>] ? alloc_inode+0x50/0x90
[ 3632.245011]  [<ffffffff81227676>] ? prepend_path+0xc6/0x2a0
[ 3632.311779]  [<ffffffff81382a2f>] aa_audit+0x5f/0x170
[ 3632.372300]  [<ffffffff8139b3c2>] audit_mount+0x152/0x160
[ 3632.436988]  [<ffffffff8139ba8d>] match_mnt_path_str+0x1dd/0x490
[ 3632.508951]  [<ffffffff81228978>] ? dentry_path+0x18/0x70
[ 3632.573638]  [<ffffffff8139be1a>] match_mnt+0xda/0x150
[ 3632.635203]  [<ffffffff8139c690>] aa_bind_mount+0x100/0x180
[ 3632.701969]  [<ffffffff813917f0>] wrap_apparmor_sb_mount+0x1c0/0x270
[ 3632.778095]  [<ffffffff813471c7>] security_sb_mount+0x57/0x80
[ 3632.846939]  [<ffffffff8123148b>] do_mount+0xab/0xda0
[ 3632.907468]  [<ffffffff811f0af4>] ? __kmalloc_track_caller+0x1b4/0x250
[ 3632.985668]  [<ffffffff810efa71>] ? hrtimer_try_to_cancel+0xd1/0x130
[ 3633.061798]  [<fff..."
1662754,2017-02-08 04:13:25 UTC,"This bug is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651944, even though the steps to reproduce are different."
1662754,2017-02-08 04:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1662754,2017-02-08 06:30:52 UTC,This is likely https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660840 -- it's possible the kernel in http://people.canonical.com/~jj/linux+jj/ has a fix for this.
1662754,2017-02-08 20:25:07 UTC,"Hi Seth,"
1662759,2018-01-18 08:30:54 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1952
1662760,2017-11-03 16:36:08 UTC,Syncing task from Mir.
1662772,2017-03-30 09:04:31 UTC,I fixed this by adding the following lines to the file below.
1662772,2019-10-15 12:00:16 UTC,This was reported in 2017 against a much older version of the snappy project. I'm sorry we didn't look here earlier but for now I must close this as WONTFIX. The corresponding systemd unit no longer exists.
1662786,2017-08-18 08:34:12 UTC,"Marking as confirmed. This is indeed hard to read in 2.27.2 on a typical ""classic"" terminal size."
1662786,2019-05-26 13:16:00 UTC,"I will work on this. What is the behaviour we are looking for? Do I remove a column, put less space between the columns, an empty space between the rows?"
1662788,2017-02-08 07:57:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/430622"
1662788,2017-02-09 04:49:51 UTC,"Reviewed:  https://review.openstack.org/430622
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=c809cc0408efa7728970a267ce6b52ae0e0a13da
Submitter: Jenkins
Branch:    master"
1662801,2017-02-23 23:37:15 UTC,It would be better decode in meteosclient rather than meteos-ui.
1662811,2017-08-14 16:09:04 UTC,When this is fixed will it be backported to 16.04?
1662811,2017-02-09 09:06:44 UTC,"@pitti, according to the changelog you made the decision to upload the Debian experimental package of sane-backends way back when.  I think it would be only fair if you assumed some responsibility to rectify the multitude of problems this has created.  We need to get back to syncing or at least merging with Debian unstable.  I've started some work on this.  I assume you will pitch in."
1662811,2017-02-08 19:42:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662814,2017-07-11 12:45:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662814,2018-02-16 10:45:50 UTC,ifmetric package will help you and patch is not needed anymore
1662815,2017-02-08 09:17:35 UTC,"For clarity, installing client tools server side is quite common so this should not be a a-typical thing to try todo."
1662815,2017-02-13 11:18:39 UTC,We will rework the alias handling. It will most likely be slightly different than this proposal here.
1662815,2017-02-16 12:13:56 UTC,"The goal of preventing such conflicts is two-fold: of course we can't allow two things to coexist with the same command name because it's impossible to have both first in the path at the same time, thus one of them will overlap the other.  But also, it's a matter of comprehension - having a ""glance"" snap which is supposed to work together with a different snap which has a ""glance"" alias for its own command is unnecessarily confusing. As a user, if I installed both of these snaps, it'd be extremely surprising to find out that ""glance"" was in fact in the ""wrong"" snap."
1662815,2017-03-03 16:10:36 UTC,I guess we could go for specialised snap package names for the daemons - say glance-api and glance-registry instead of 'glance' (which currently provides both).
1662822,2017-02-10 10:42:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662822,2017-02-10 10:45:34 UTC,This is probably a duplicate of  #1365200
1662827,2017-02-09 08:56:58 UTC,That explains everything
1662827,2017-02-24 03:49:51 UTC,qtmir (0.5.1+17.04.20170215.1-0ubuntu1) zesty; urgency=medium
1662827,2017-02-08 13:03:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662827,2017-02-09 01:54:50 UTC,"Worth mentioning that Mir 0.25.0 (released in December) switched the cursor naming scheme to match the CSS spec:
  https://www.w3.org/TR/css-ui-3/#propdef-cursor
  https://developer.mozilla.org/en/docs/Web/CSS/cursor
  http://www.w3schools.com/cssref/pr_class_cursor.asp"
1662833,2017-02-09 06:43:33 UTC,I also noticed that Super+S toggles the same workspace management that Super+Down arrow key does. I can't find this keyboard shortcut in the settings.
1662837,2017-05-17 02:21:58 UTC,Why backup cinder with nova mode?
1662847,2017-02-16 09:13:12 UTC,"It makes sense to me to have the examples in UITK given they always depend on the latest, unstable code: how about adding the snapcraft.yaml for the examples to the UITK instead? There's nothing else that makes sense to snap here and we could automatically build the latest examples as staging changes."
1662858,2019-03-10 08:28:40 UTC,Current status on master:
1662858,2020-08-04 11:13:22 UTC,"LPE logic has been significantly refactored for 1.0, assuming fixed."
1662860,2017-04-09 09:29:14 UTC,"Please fix it!
Thanks"
1662860,2017-04-06 23:30:33 UTC,"Thanks to smaeda, Steffen, Merlin and Dave (thanks guys!), I have resolved my problem last week... But today the driver was upgrade from 375.39 to 375.51 and hey, it's back again!!! The same procedure may resolve the issue AGAIN but it seems that the solution is TEMPORARY until the next upgrade..."
1662860,2017-04-06 19:28:32 UTC,"Still get this today, April 6, 2017, when upgrading from nvidia-367 to nvidia-375 on Kubuntu 14.04."
1662860,2017-04-01 12:25:16 UTC,Tested again with xenial:
1662860,2017-03-30 08:48:42 UTC,"the.emrys (for the benefit of others) as noted before the order for ln needs to be as for cp, i.e.:"
1662860,2017-03-30 04:14:05 UTC," I will edit smaeda (smaeda) a little to make it properly run with remaining cuda installtion
after  running these commands"
1662860,2017-03-22 12:30:47 UTC,"smada's solution worked, but he confused the ln order. This should work:"
1662860,2017-03-22 08:20:38 UTC,"I got this, but cleared. The following was successful with my environment; latest CUDA Toolkit 8.0(including nvidia-375) in Ubuntu 16.10."
1662860,2017-04-10 20:52:36 UTC,/sbin/ldconfig.real: /usr/lib/nvidia-375/libEGL.so.1 is not a symbolic link
1662860,2017-03-22 06:57:41 UTC,"Yes, please make a fix for this, or suggest a workaround."
1662860,2017-03-17 22:54:01 UTC,Is there any solution of this ?
1662860,2017-02-15 11:04:08 UTC,Moved to newest nvidia-378.13 from the graphics-drivers ppa : install & work well
1662860,2017-02-12 19:16:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1662860,2017-02-11 07:54:44 UTC,#4 feedback
1662860,2017-02-10 13:27:23 UTC,"Well, that driver generate too many crashes now & then : lp:1663524 lp:1663528"
1662860,2017-02-08 15:01:51 UTC,"oem@u64:/usr/lib/nvidia-375$ ls -aiF | grep libEGL
292910 libEGL_nvidia.so.0@
269365 libEGL_nvidia.so.375.26
292908 libEGL.so@
269322 libEGL.so.1
269355 libEGL.so.375.26"
1662860,2017-02-08 14:49:51 UTC,"Tested a complete nvidia* removal, then a reinstall, but still get the same error."
1662860,2017-03-22 07:32:45 UTC,"$ ldconfig
/sbin/ldconfig.real: /usr/lib/nvidia-375/libEGL.so.1 is not a symbolic link
/sbin/ldconfig.real: /usr/lib32/nvidia-375/libEGL.so.1 is not a symbolic link"
1662860,2017-02-17 11:57:34 UTC,This also affected me on 16.04.
1662860,2017-03-07 18:05:21 UTC,I get this on Ubuntu 17.04 when installing the NVIDIA BLOB:
1662860,2017-04-26 19:14:18 UTC,"To get rid of this `ldconfig` message, I just tricked it by going into the respective /usr/lib/nvidia-375 and /usr/lib32/nvidia-375 folders and relinking it to itself (manually):"
1662860,2017-11-13 20:15:39 UTC,"The ldconfig problem is fixed with nvidia-384 in Xubuntu 17.10. Unfortunately, the dpkg error is still present."
1662860,2017-04-17 16:41:29 UTC,"The proper solution would be to not install libEGL.so.375.39, as it is the deprecated non-GLVND implementation. The workaround is therefore to delete"
1662860,2017-10-31 16:10:01 UTC,Confirmed with Ubuntu 17.04 with upgrading to libcuda1-384 nvidia-384 nvidia-opencl-icd-384
1662860,2017-10-26 04:02:40 UTC,"Correction to #46, tried with correct folder names (-384) and get same response (sudo mv /usr/lib32/nvidia-384/libEGL.so.1 /usr/lib32/nvidia-384/libEGL.so.1.org)"
1662860,2017-10-24 14:35:56 UTC,"I'm now seeing this on Ubuntu 16.04 with the nvidia-384 drivers, which looks like they were released within the last day or so."
1662860,2017-10-03 14:47:37 UTC,"Also, happens on Ubuntu 17.10 beta 2.
Dell Inspiron 15 Série 7000 - 7560
NNVIDIA(R) GeForce(R) 940MX 4GB GDDR5"
1662860,2017-09-28 15:20:10 UTC,"Can confirm this happens on the daily Ubuntu 17.10 build:
Processing triggers for libc-bin (2.26-0ubuntu1) ...
/sbin/ldconfig.real: /usr/lib/nvidia-375/libEGL.so.1 is not a symbolic link"
1662860,2017-09-07 14:43:40 UTC,@clementlefebvre
1662860,2017-08-31 03:50:02 UTC,Bug is still present
1662860,2017-08-15 21:32:13 UTC,"this has sorted that out:
https://askubuntu.com/questions/900285/libegl-so-1-is-not-a-symbolic-link
and restart..."
1662860,2017-08-10 20:54:13 UTC,@clementlefebvre
1662860,2017-07-28 13:47:27 UTC,Careful is advised when trying to fix theses warnings manually creating links.
1662860,2017-10-31 18:07:42 UTC,"Ubuntu 16.10.3 LTS also confirmed for new Nvidia driver.
Ge force GT 640 PCIe SSE2, Intel core i3-4160, Asrock Z97 Extreme 6"
1662860,2017-07-16 14:21:22 UTC,Seen in Ubuntu 17.04 nvidia-375.66 but has no affect on install or use..
1662860,2017-07-26 21:02:56 UTC,"Still seeing this problem in 16.04, but no affect on install or use."
1662860,2017-05-02 22:41:04 UTC,Impact here was an unbootable system (blank screen) not just an annoying error message.
1662860,2017-05-08 13:36:28 UTC,"Mark, regarding your comment (#25), `Impact here`, impact of what? Impact of doing `sudo mv...`?"
1662860,2017-05-09 00:04:58 UTC,"I'm having the same issue here (xenial)... Quite annoying.
I hesitate to create a symbolic link to libEGL.so.375.39 as many people suggest because that is clearly a different file:"
1662860,2017-05-09 07:32:23 UTC,Confirmed that this issue still happens for 2 LTS: Ubuntu 16.04.2 Server + Nvidia 375.39
1662860,2017-05-19 10:19:22 UTC,Can also confirm that i get this error two separate machines running 16.04.2 with nvidia 375.39.
1662860,2017-04-13 16:05:57 UTC,LibEGL.so.1 isn't a symbolic link but should be.  I had an issue with a program that required EGL and could not find any capabilities with nvidia-375.
1662860,2017-05-31 21:58:17 UTC,Just seen this after an upgrade on 14.04 LTS. I've also seen it previously on 16.04 machines.
1662860,2017-06-01 02:24:37 UTC,Bug still here with latest nvidia-375 (375.66-0ubuntu0.14.04.1)
1662860,2017-06-02 09:00:56 UTC,Bug still here with nvidia-375.66 on Mint 18.1
1662860,2017-06-05 16:21:40 UTC,Same bug on Ubuntu 17.04.
1662860,2017-05-22 18:41:21 UTC,Still present here for Ubuntu 17.04 with nvidia drivers 375.39-0ubuntu5.
1662860,2017-06-10 07:09:32 UTC,"Hi,
Bug still here in Ubuntu 17.04 nvidia-375.66 drivers (GTX 1050 laptop). Everything is updated to last version."
1662861,2017-02-08 17:04:04 UTC,added paste
1662864,2017-02-08 14:39:16 UTC,Upstream bug report:
1662866,2017-02-08 12:42:46 UTC,"root@skyy:~# LANG=C aptitude why libhybris
i   ubuntu-desktop         Recommends unity8-desktop-session
i A unity8-desktop-session Recommends webbrowser-app
iBA webbrowser-app         Depends    liboxideqt-qmlplugin (>= 1.19)
ipA liboxideqt-qmlplugin   Depends    liboxideqtcore0 (= 1.19.6-0ubuntu2)
ipA liboxideqtcore0        Depends    libhybris"
1662866,2017-02-08 12:27:37 UTC,https://github.com/aritger/linux-opengl-abi-proposal/blob/master/linux-opengl-abi-proposal.txt
1662866,2017-02-08 12:27:14 UTC,"rev3 & 4 from https://patchwork.freedesktop.org/series/12354/ are how the mesa EGL vendor lib was implemented, might help here too"
1662867,2018-09-24 14:47:10 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1662867,2018-06-11 15:19:07 UTC,This issue was fixed in the openstack/nova 15.1.3 release.
1662867,2018-06-05 23:01:19 UTC,"Reviewed:  https://review.openstack.org/571432
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e0c7d6c8816d0c21b2913adc7a3d6cbd59604cd0
Submitter: Zuul
Branch:    stable/ocata"
1662867,2018-06-04 14:27:53 UTC,This issue was fixed in the openstack/nova 16.1.4 release.
1662867,2018-06-04 13:52:15 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1662867,2018-06-04 05:31:29 UTC,"Reviewed:  https://review.openstack.org/571426
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d251b95083731829ba104dc5c7f642dd5097d510
Submitter: Zuul
Branch:    stable/pike"
1662867,2018-05-31 18:48:34 UTC,"Reviewed:  https://review.openstack.org/571424
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5a4c6913a37f912489543abd5e12a54feeeb89e2
Submitter: Zuul
Branch:    stable/queens"
1662867,2018-03-14 19:13:17 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22InvalidDiskInfo%5C%22%20AND%20message%3A%5C%22qemu-img%3A%20Could%20not%20open%5C%22%20AND%20message%3A%5C%22No%20such%20file%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d
1662867,2018-05-31 09:50:48 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/571426"
1662867,2018-04-20 13:13:22 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1662867,2018-04-11 13:50:23 UTC,"Reviewed:  https://review.openstack.org/553067
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5f16e714f58336344752305f94451e7c7c55742c
Submitter: Zuul
Branch:    master"
1662867,2018-03-14 20:51:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553067"
1662867,2018-03-14 16:49:05 UTC,We still see this in CI runs periodically:
1662867,2017-10-28 04:17:52 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1662867,2017-08-28 21:42:21 UTC,The logs are gone. What did this actually look like? Can you find a version of it on stable/ocata and paste the actual error in here?
1662867,2018-05-31 10:16:48 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/571432"
1662867,2017-02-24 15:40:24 UTC,Another example on stable/ocata :
1662867,2018-05-31 09:49:58 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/571424"
1662893,2017-02-09 10:17:51 UTC,"Hello Lucas,"
1662893,2017-02-09 14:11:49 UTC,"Hi Rene,"
1662893,2017-02-09 17:30:21 UTC,OK thanks. What about python-redfish ?
1662893,2017-02-10 13:03:15 UTC,"Hi Renne,"
1662896,2017-02-28 10:43:01 UTC,"Until we reached 1.0, it seems appropriate to keep a higher level of verbosity to ease debugging. That default behaviour will be changed for 1.0."
1662896,2017-02-28 20:08:36 UTC,"@Bruno,"
1662921,2017-02-09 12:37:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/431497"
1662925,2017-09-01 16:16:50 UTC,Unassigning due to no activity for > 6 months.
1662933,2019-04-16 16:26:11 UTC,"I believe this information is visible in the action output, but we would need to confirm that."
1662949,2017-02-08 16:44:18 UTC,"Scott,"
1662951,2017-02-08 16:53:14 UTC,"Yes, we definitely want to track license information inside the snap format in a proper location. We want to support both basic cases such as just listing a well known name, custom licenses, and all the way up to requiring an explicit agreement with the provided text."
1662951,2017-02-09 18:30:00 UTC,Thanks Gustavo -- makes sense.
1662951,2018-01-30 09:53:30 UTC,"There is ongoing work on this bug. The relevant snapd APIs will now return the SPDX expression describing one of stock licenses. We are discussing how to represent non-stock licenses, both in the snap itself and in the license expression. The discussions are taking place on the forum."
1662954,2020-03-18 21:25:27 UTC,"@all: if you reproduce this issue with latest Boot-Repair version (installed from PPA), please open a new bug report.
As a workaround, you can disable internet detection in the Advanced Options of Boot-Repair."
1662954,2020-01-09 21:12:21 UTC,Adding one scenario that causes this issue reliably:
1662954,2019-05-29 17:14:42 UTC,Reports there is no Internet even when Firefox is first checked working OK (via a wired connection.)
1662954,2018-02-02 22:42:05 UTC,"I'm having the same problem as Jim and Ivan. I entered the three commands to install boot-repair. Then I clicked ""Recommended repair"" and the program halted because it couldn't connect to the Internet. Which comes as a surprise to me, because I had just downloaded it and have gone to other websites to verify that I am connected."
1662954,2018-01-26 15:30:22 UTC,"I have exactly the same problem. Tried running boot-repair from Ubuntu live cd aswell as the boot-repair ISO.
I also do not completely understand the boot-repair-4ppa42 answer..."
1662954,2018-01-21 23:41:15 UTC,"Same problem, I don't understand the answer. I tried typing boot-repair-4ppa42 but nothing, then I tried to getting the respective repo but failed. What do you mean with ""boot-repair-4ppa42"", what do I have to do to start Ubuntu 17.10 after installing it next to Windows 10?  Thank you."
1662954,2018-02-11 22:41:44 UTC,"@all: if you reproduce this issue with latest Boot-Repair version (installed from PPA), please open a new bug report.
As a workaround, you can disable internet detection in the Advanced Options of Boot-Repair."
1662954,2017-09-18 17:42:35 UTC,Should be fixed in boot-repair-4ppa42
1662962,2017-02-09 21:29:20 UTC,"This is something we discussed, and our current view (which can be
changed) is that snaps which have not yet made it to stable should not
be surfaced through general searches."
1662962,2017-02-09 22:29:10 UTC,"Mark,"
1662962,2017-02-10 07:19:41 UTC,"I guess it might make sense to allow a user to specify --candidate,
--beta, or --edge and search the latest track up to that level of risk.
I.e. for --beta one would search stable, candidate and beta risk levels,
but not edge."
1662962,2017-06-26 14:42:57 UTC,"Hello,"
1662962,2017-06-27 16:33:16 UTC,"I certainly think it's correct to not search non-stable channels without a very explicit user acknowledgement. I'm open to a --beta flag but I don't think it's a grave usability issue. We've taken lots of significant steps towards making it easier for folks to get to stable channels, and I think we want to keep social pressure on projects to get there."
1662962,2019-10-15 12:45:29 UTC,I'm marking this as triaged / wishlist. Please feel free to continue the discussion either here or on the snapcraft forum.
1662969,2017-02-08 22:17:37 UTC,Have you the same behaviour with the online version? With what web browsers?
1662969,2017-02-08 22:47:05 UTC,"No, only on android"
1662971,2017-02-08 22:21:49 UTC,This should be simple! Feel free to submit a merge request.
1662987,2017-04-03 15:15:11 UTC,"I confirm this happens to me in zesty too, I set different lock times but it always locks screen and music keeps playing with the screen off"
1662987,2017-04-03 21:06:25 UTC,"Confirmed. And as a matter of fact, it fails to inhibit screen blanking on unity7 too:"
1662996,2017-02-08 18:51:41 UTC,"Just wanted to add that, doing a ""sudo apt-get update && sudo apt-upgrade"", followed by a system reboot, did not fix the issue."
1663001,2017-02-08 19:09:31 UTC,I think all of those things could be done with a snap and a specific permanent slot.
1663001,2017-02-08 21:04:47 UTC,Drop a oneshot unit in /etc/systemd/system?
1663001,2017-02-08 19:47:38 UTC,"well, the module side of things should be handleable via a ""snap set core ..."" eventually and since you need a custom gadget for the config.txt currently you can actually set it via the upcoming module configuration ..."
1663001,2017-02-10 17:43:38 UTC,"just to give a more detailed hint, creating a file like:
/etc/systemd/system/rtc-addon.service"
1663001,2017-02-09 10:57:57 UTC,"yeah, that should even be possible to easily do from the gadget ..."
1663002,2017-02-08 19:10:46 UTC,Attachment.
1663002,2017-02-13 18:43:55 UTC,"I believe this actually traces back to bug #1628098, where `organize` is happening at the wrong time, so it isn't taken into collision detection correctly. This definitely needs to be fixed, thank you."
1663002,2017-02-13 18:45:10 UTC,(Note that I'm not marking as dupe though-- this bug nicely describes the issue).
1663006,2017-02-08 19:56:31 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1663006,2017-02-08 19:56:37 UTC,These look like the relevant lines from the logs:
1663008,2019-09-19 12:02:30 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1663015,2017-03-17 20:28:15 UTC,https://github.com/snapcore/snapweb/pull/210
1663016,2017-02-10 06:08:04 UTC,in a pinch
1663016,2017-02-27 21:06:15 UTC,I think this is lower priority compared to lp bug #1668399
1663020,2020-02-21 10:03:34 UTC,Les progrees se verrons bien et protégés..
1663020,2017-05-09 08:32:29 UTC,"@spike,"
1663020,2020-02-21 10:00:32 UTC,"Les commentaires  et autres débâcle ou débâclés, se verrons dans la production nouvelle programmation."
1663020,2017-02-10 18:52:45 UTC,"After I submitted this report, I upgraded to kernel 4.6 to see if that helped. It did not, but when I upgraded to Ubuntu 16.10, the bug resolved itself."
1663020,2017-02-10 18:03:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1663020,2017-02-08 21:01:01 UTC,This change was made by a bot.
1663020,2017-04-07 22:49:53 UTC,"I too have a Dell XPS 9360, and I'm still experiencing this issue running the latest 4.10 kernel on 16.04 LTS with HWE-Edge:"
1663025,2017-03-27 13:54:28 UTC,moved to tripleo launchpad with quickstart tag
1663025,2019-02-12 15:54:43 UTC,"How are planning to test edge cases such as Distributed Compute, as well as the Spine-Leaf usecase without it?"
1663025,2019-02-12 13:10:41 UTC,Is this still needed?
1663026,2017-02-08 21:10:53 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fba8a30a3a8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=0x7fba8a53db00 <main_arena>, ptr=<optimized out>, str=0x7fba8a306f1e ""corrupted double-linked list"", action=3) at malloc.c:5046
 malloc_consolidate (av=av@entry=0x7fba8a53db00 <main_arena>) at malloc.c:4218
 _int_malloc (av=av@entry=0x7fba8a53db00 <main_arena>, bytes=bytes@entry=65536) at malloc.c:3485
 __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3271"
1663026,2020-11-20 04:17:18 UTC,[Expired for pluma (Ubuntu) because there has been no activity for 60 days.]
1663029,2017-05-25 14:00:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663029,2018-01-18 13:02:50 UTC,This was just posted to the forum: https://forum.snapcraft.io/t/reusable-alsa-lib-part/3556
1663034,2017-03-27 13:53:24 UTC,moved to tripleo launchpad with quickstart tag
1663034,2018-06-05 15:09:32 UTC,"@Wes,"
1663038,2017-02-08 21:33:29 UTC,"Hi, thank you for your time—please update the URL for MariaDB on this article ""Database (Galera Cluster) for high availability"" to https://mariadb.com rather than https://mariadb.org. Best, MariaDB marketing"
1663044,2017-02-09 20:03:09 UTC,"Hello, after deleting the files in / android / cache / recovery / and reloaded version 7, the problem remains the same."
1663048,2017-02-22 18:35:35 UTC,"mir-libs is only 0.26.0, but xenial overlay has 0.26.1.  I can't fix unity8-session to use mir-libs until that's updated."
1663048,2017-02-10 07:14:49 UTC,There is a build from 2017-02-08 in edge channel that is after the latest Mir landing.
1663048,2017-02-16 19:28:45 UTC,"The conclusion on the email thread seemed to be to enforce the use of mir-libs by any applications that want to run that way, and for unity8 to also use mir-libs."
1663048,2017-02-16 19:29:43 UTC,"The mir debs updated again in the xenial overlay earlier this week, so the latest platform snap published yesterday to edge is again incompatible with the mir-libs snap on edge."
1663048,2017-02-16 20:03:09 UTC,"FYI for now I disabled automatic updates from https://code.launchpad.net/~ubuntu-sdk-team/+snap/ubuntu-app-platform - snaps can still be installed by hand for testing purposes, and we can publish on demand. The latest update was due to adding new API needed by the Ubuntu browser."
1663048,2017-02-17 06:01:40 UTC,"Right. Indeed we used to auto-publish to all channels except stable. We can re-enable auto-uploads later but I now configured it so that it'd be only to edge from now on. Stable promotions via QA as usual, maybe in case of UAP we might need QA team for other channels too, there are so many use cases using different channels."
1663048,2017-02-17 18:59:04 UTC,There was a meeting today with the Mir team and some stakeholders and I believe the outcome was that mir-libs will continue to be the only supported source for Mir libraries.
1663048,2017-02-17 19:16:45 UTC,Adding snapd task to get the mir-libs content interface auto-connected.
1663048,2017-02-17 20:47:05 UTC,Bug 1665775 is the request for mir-libs to be auto-connected.
1663048,2017-02-17 21:08:59 UTC,"I've got a branch up for changing desktop-launch to point at mir-libs [1].  I also adjust LD_LIBRARY_PATH, so apps won't have to manually add that.  They just need to plug into mir-libs."
1663048,2017-02-20 08:35:57 UTC,"I'm not really found of this decision from a pure developer experience perspective.
What would make Mir special compared to other system libraries, like libsystemd, pulseaudio, evolution-data-server, your email service libs, and so on and so on?"
1663048,2017-02-21 14:50:14 UTC,"I still think that this proposal creates a real burden, ABI breakage to developers. This isn't part of the desktop helper for sure as it doesn't follow any of the snappy best practices."
1663048,2017-02-24 13:17:12 UTC,"UAP would be ready, but should an upload without mir-libs to edge be delayed to a later point or could it be done eg in the beginning of next week?"
1663048,2017-02-21 14:40:44 UTC,"Didier, I mostly agree with you, but you are missing the context and meetings that led to this approach.  I'm just the messenger here, and anyone please correct me if I mess something up."
1663048,2017-02-22 15:24:28 UTC,"Didier and I settled on a version of desktop-launch that tries to use mir-libs first, falling back to ubuntu-app-platform (while the libs are in there), and if not, then falling back to an internal copy of the libraries."
1663048,2017-02-22 11:49:59 UTC,This bug was fixed in the package unity8-desktop-session - 1.0.13+17.04.20170221-0ubuntu1
1663048,2017-02-27 14:18:36 UTC,"From my end, I don't know of blockers for the UAP-without-Mir upload."
1663048,2017-02-27 18:09:51 UTC,"Hmm, unity8-session runs into bug 1665123 when trying to use mir-libs.  I'll continue to bundle for now."
1663048,2017-02-27 20:03:49 UTC,"OK, I found a way to work around that with symlinks, so unity8-session is now using mir-libs."
1663048,2017-03-02 14:21:38 UTC,"UAP would probably like to move to the new tracks, like 1/stable, 2/stable etc. At the Hague sprint it was recommended to use what we currently use, ie have ""content"" field with ubuntu-app-platform1, where that 1 could be bumped to 2."
1663048,2017-03-02 19:45:35 UTC,@timo can we go ahead and get tracks allocated for this?
1663048,2017-03-06 10:55:07 UTC,"(requested on Rocket, no answer yet)"
1663048,2017-02-20 12:50:34 UTC,"FWIW, the UAP branch for removing mir libs is available and linked now. Since we agreed not to publish anything new to even edge for now (not to mention beta or candidate), I'm not merging it yet or uploading anything to the store."
1663050,2017-06-09 05:05:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663051,2017-02-09 17:34:56 UTC,I started to report this yesterday but was unsure if it was actually a feature. In my case I deleted almost 1GB. Perhaps snapcraft needs a reset-cache option.
1663051,2017-02-08 23:23:40 UTC,"An easy workaround is to manually remove the cache (~/.cache/snapcraft), so setting to Medium."
1663051,2017-02-09 19:31:41 UTC,Yeah simply exposing an easy way to manually clear the cache (ala apt-get clean) is probably the easiest solution.
1663052,2017-02-08 22:51:12 UTC,https://github.com/snapcore/snapcraft/pull/1123
1663052,2017-02-24 23:15:48 UTC,"Thanks Joseph. However, I should be able to understand what exactly the issue is given the bug without having to look at your PR. How is fish not supported? Are you unable to run snapcraft from within it?"
1663079,2020-02-11 14:14:10 UTC,Works for me with the current QEMU master branch... can you still reproduce the issue with the latest version of QEMU (either v4.2 or the master branch)?
1663079,2020-04-12 04:17:30 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1663087,2017-02-09 01:29:28 UTC,related bug 1428062
1663095,2018-05-10 11:13:34 UTC,"Alvin, yes, I have. It didn't work out though."
1663095,2018-05-10 00:17:46 UTC,have you tried the suggestion in comment 5?
1663095,2018-05-09 17:19:57 UTC,"This bug, as reported above, affects me and dozens of users on the lab I mantain. The lab runs with Debian 9 and with Inkscape installed from official deb rep, 0.92.1 r15371."
1663095,2017-12-05 14:17:50 UTC,"Can't reproduce (LM 18.2, Inkscape 0.92.2) - tried with overlapping stroked circles, with a stroked rectangle,... Perhaps a short gif animation by someone where it doesn't work could help?"
1663095,2017-12-05 21:12:29 UTC,I tried to make a screen shot since I cannot make animated gifs. Here are the steps I made:
1663095,2017-12-05 11:26:29 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1663095,2017-12-05 09:50:14 UTC,I cannot reproduce on Windows 7.  But there's another report of this with 0.92.1 on Debian here:
1663095,2017-07-17 10:39:12 UTC,"Yes, this bug affects Inkscape 0.92, it makes the bucket tool partially unusable."
1663095,2017-04-21 20:55:11 UTC,could you attach the svg file which you are trying to fill?
1663095,2017-04-21 20:09:44 UTC,0.9.1 Also 16.10
1663095,2017-12-05 14:07:07 UTC,I have the same issue on Linux v.92.1. It's very easy to reproduce.
1663103,2019-10-01 13:13:26 UTC,If I understand this correctly you'd like to see allocation of plugs and slots to individual apps and hooks? If so  I don't believe this is supported today. I'm marking this as confirmed/wishlist. Please escalate to get it done faster.
1663112,2017-02-09 05:02:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1663116,2017-02-22 05:48:49 UTC,"That's fine, at the time I wasn't sure where the LDAP keystone driver was going to be, but if we can use the ldap-config-flags on it as seems to be in the charm-keystone-ldap, that should be sufficient to us.  As long as the value gets set for the domains, I'm happy."
1663116,2017-02-09 07:15:08 UTC,"Note our use case for this is for use with multiple ldap domains, I believe there's work to create a subordinate charm in planning for this.  I did notice we can use the ldap-config-flags option to do it, but thats only if the identity_backend is set to ldap, which is not the case for us."
1663116,2017-02-13 14:09:39 UTC,https://github.com/openstack/charm-keystone-ldap
1663116,2017-02-13 14:10:57 UTC,I'm loath to put more feature into the v2 LDAP support directly into the keystone charm as I think its a perfect use case for a domain specific identity driver - as provided by the keystone-ldap charm.
1663121,2018-06-10 03:33:48 UTC,"Change abandoned by Tom Barron (<email address hidden>) on branch: master
Review: https://review.openstack.org/431315
Reason: No activity since August 2017; restore and rebase if appropriate."
1663121,2019-10-28 17:20:06 UTC,Closing for now if you are still seeing this issue please re-open.
1663121,2017-02-09 04:53:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/431315"
1663122,2017-02-09 05:02:25 UTC,The test was introduced in:
1663122,2017-11-03 16:30:30 UTC,Syncing task from Mir.
1663143,2017-02-09 08:02:11 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1663146,2017-02-09 08:02:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1663152,2017-02-12 15:45:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663157,2017-02-24 19:05:25 UTC,"Here's the pstree output for a zesty system. It looks like more things have been moved over to systemd's control and, therefore, more things are unconfined."
1663157,2017-05-11 23:19:06 UTC,I'm making this bug public now that we have security updates published which disable the guest session. My hope is that we can re-enable it after the changes suggested by pitti can be investigated/implemented.
1663157,2017-02-24 19:33:57 UTC,I should mention that the above pstree outputs require some changes to the pstree code to get the AppArmor label included in the output when the -Z option is specified. I've pushed a work-in-progress quality git branch of psmisc to https://code.launchpad.net/~tyhicks/psmisc/+git/psmisc/+ref/apparmor that includes the necessary changes.
1663157,2017-03-22 04:01:52 UTC,Ow. Unfortunately I don't have any information on how to fix this since most of the work on guest sessions and systemd was done by Martin Pitt.
1663157,2017-04-04 21:16:04 UTC,@pitti - I know you don't have any responsibility here but wondering if you have any advice on what direction to solve this?
1663157,2017-04-05 03:38:23 UTC,"The proper way to do this would be to use pam_apparmor, similar to how selinux is doing this, through systemd --user
  /etc/pam.d/systemd-user"
1663157,2017-04-05 03:41:43 UTC,Note: ideally we want to set things up to use a policy namespace stack so that snaps can work from the guest session.
1663157,2017-04-05 23:34:09 UTC,"I spent some time looking into pam_apparmor and understanding how could be used. It seems like it would be extremely risky to introduce in a security update and I'm not sure if it even supports everything that would be needed. IIUC, it requires us to confine all login applications that use PAM and it isn't clear if we can selectively confine only the guest users and leave all other users unconfined. At this point, I'm not comfortable/confident in pam_apparmor as a solution in stable release."
1663157,2017-04-06 01:46:31 UTC,"@tyhicks you are correct that pam_apparmor is NOT a good solution currently. I will restate, it requires either
- a new version of pam_apparmor
or
- confining systemd and setting up hats for the guest session user (which currently means the user name can not have randomization)."
1663157,2017-05-05 13:31:55 UTC,"We need to either find a solution to this issue, or push an update to disable guest sessions."
1663157,2017-02-24 19:01:03 UTC,"After coming back to this bug, I noticed that Robert was not subscribed and couldn't see the bug. He's now subscribed."
1663157,2017-05-08 22:13:45 UTC,Patch to Yakkety that disables guest support by default.
1663157,2017-05-08 22:14:07 UTC,Patch to Zesty that disables guest support by default.
1663157,2017-05-08 22:16:56 UTC,These patches ship LightDM with guest support disabled by default. You can re-enable it by putting a config file with higher priority containing:
1663157,2017-05-10 18:20:01 UTC,@robert-ancell thanks for the debdiffs! Is the addition of debian/99-disable-guest.conf intentional in the zesty debdiff? I suspect that debian/50-disable-guest.conf is sufficient and that 99-disable-guest.conf was meant to be removed.
1663157,2017-05-10 20:46:51 UTC,"> I also did a bit of experimenting with adding ""AppArmorProfile=/usr/lib/lightdm/lightdm-guest-session"" to the bottom of /lib/systemd/system/user@.service
"
1663157,2017-05-11 01:22:59 UTC,"@Tyler - yes, the 99 should have been removed..."
1663157,2017-05-11 04:07:40 UTC,Fixed zesty debdiff
1663157,2017-05-11 17:43:05 UTC,This is CVE-2017-8900.
1663157,2017-05-11 23:00:28 UTC,This bug was fixed in the package lightdm - 1.19.5-0ubuntu1.2
1663157,2017-05-11 23:15:16 UTC,This bug was fixed in the package lightdm - 1.22.0-0ubuntu2.1
1663157,2017-02-24 19:04:18 UTC,The pstree output helps shed some light on this bug. It looks like the portions of the guest session that are spawned upstart are properly confined. The portions spawned by systemd are not confined. I'm attaching the `pstree -Z guest-XXXXXX` output from a running yakkety guest session.
1663157,2017-05-08 07:55:27 UTC,FWIW - Desktop are fine with disabling the guest session while we work out the systemd stuff.
1663157,2017-11-14 08:32:36 UTC,"@Magezi: Please note that this is a bug report, not a support forum. This Ask Ubuntu question may help:"
1663157,2017-06-19 07:16:05 UTC,This bug was fixed in the package lightdm - 1.22.0-0ubuntu4
1663157,2018-01-11 15:50:29 UTC,"Reopening, since the guest session is disabled by default but it is still not confined."
1663157,2018-01-12 07:25:02 UTC,@rbalint can you please open a new bug to track re-enabling the guest session with proper confinement rather than piggy back on this bug?
1663157,2018-01-12 11:06:48 UTC,@tyhicks I just opened LP #1742912 for tracking the confinement fix.
1663157,2017-05-11 23:51:57 UTC,"If you have a use case which requires the guest session, you can manually re-enable it by writing the following contents to /etc/lightdm/lightdm.conf:"
1663157,2017-11-14 06:53:25 UTC,Hey guys I am a newbie to linux and I am coming from windows...I just want to have that button on my login screen or somewhere on the notification zone ...everything you have explained is hard for me to understand can you please elaborate it in steps ..so that I enable guest-session on my computer?
1663157,2017-05-16 18:14:00 UTC,"Balint, could you follow through on this bug?  Martin has provided some good general guidance already about what's required to re-enable secure guest sessions in artful."
1663158,2017-02-09 08:18:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/431370"
1663158,2017-03-25 16:45:39 UTC,It looks this bug has been fixed: https://review.openstack.org/#/c/448967/
1663161,2018-11-22 02:37:15 UTC,"if it can help anyone, I had this problem on normal update/upgrade on 16.04.05 LTS
if you notice the error message:  /usr/local/bin/ckbcomp: not found
my ckbcomp was in BIN not LOCAL/BIN.
I copied it to BIN and rerun update/upgrade and the upgrade completely successfully. sorted."
1663171,2017-02-10 03:25:27 UTC,update docker version to 1.10.3
1663171,2017-02-20 16:45:30 UTC,"If this error happened, it seems to be an internal error on server side (since operators should setup the right docker version with Zun). Zun should return 500 in such case."
1663177,2017-02-10 14:44:14 UTC,https://github.com/snapcore/snapd/pull/2831
1663177,2017-02-13 02:48:07 UTC,The above pull request seems to solve the problem for me.  Thanks!
1663184,2017-02-09 09:56:28 UTC,linux_distribution() is also deprecated under 3.5
1663193,2019-09-25 22:54:34 UTC,This is because the ubuntu-image snap is not published for arm64. Transferring to the ubuntu-image project for them to comment on publishing the ubuntu-image snap for arm64.
1663218,2017-02-09 13:12:45 UTC,Review link: https://review.gerrithub.io/#/c/347883/
1663223,2017-02-09 12:21:05 UTC,"Removing the Rectangle with SlotsLayout.position: SlotsLayout.Trailing; makes things work as excepted, so i think this is a bug with SlotsLayout.Trailing"
1663234,2020-12-03 20:01:18 UTC,"I marked this as a possible duplicate of #1873967 although this one here is older, because this one could not be reproduced and the other one has more information."
1663238,2017-02-28 07:34:27 UTC,"Reviewed:  https://review.openstack.org/438366
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=0795dc8818c21903697137e61796c3eae5c2fcb4
Submitter: Jenkins
Branch:    stable/ocata"
1663238,2017-02-28 10:16:03 UTC,"Reviewed:  https://review.openstack.org/438368
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=21cb88cfc03626d36678714ebd26ea449f1e7fe1
Submitter: Jenkins
Branch:    stable/ocata"
1663238,2017-02-28 10:16:49 UTC,"Reviewed:  https://review.openstack.org/438369
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=e0e92d00995e68a3844ce9e1c71f37f0e7f3b656
Submitter: Jenkins
Branch:    stable/ocata"
1663238,2017-02-27 08:40:28 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/438369"
1663238,2017-02-28 10:17:05 UTC,"Reviewed:  https://review.openstack.org/438371
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=d1803fa4ceb92deb794fff55180ba7f486486c73
Submitter: Jenkins
Branch:    stable/ocata"
1663238,2017-02-27 08:40:50 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/438371"
1663238,2017-02-28 10:16:57 UTC,"Reviewed:  https://review.openstack.org/438370
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=3c7d3b732dc282e92383834ce534802c9da33965
Submitter: Jenkins
Branch:    stable/ocata"
1663238,2017-02-27 08:40:39 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/438370"
1663238,2017-02-27 08:40:17 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/438368"
1663238,2017-02-27 08:35:31 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/438366"
1663238,2017-02-17 10:10:30 UTC,"Reviewed:  https://review.openstack.org/434776
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=d440793e0b074084c7a9604996ee0ee3b07a300b
Submitter: Jenkins
Branch:    master"
1663238,2017-02-16 12:08:48 UTC,"Reviewed:  https://review.openstack.org/434414
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=ac07fcd78b39b9aa1bda1734c774d2a6dc8e2691
Submitter: Jenkins
Branch:    master"
1663238,2017-02-15 19:05:22 UTC,"Reviewed:  https://review.openstack.org/434168
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=a1bc0e3aec4c11fe72804c1b718928cf6a65ef34
Submitter: Jenkins
Branch:    master"
1663238,2017-02-15 19:05:15 UTC,"Reviewed:  https://review.openstack.org/429901
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=6c5d895ba4984464e1e11a4fcd6e83d82a3d6893
Submitter: Jenkins
Branch:    master"
1663238,2017-02-15 12:14:07 UTC,"Reviewed:  https://review.openstack.org/431223
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=133271f250aeff69792e9fba078a99034a1daf4b
Submitter: Jenkins
Branch:    master"
1663241,2017-02-09 17:16:37 UTC,might be fixed in version 2
1663250,2017-02-10 13:09:33 UTC,"Reviewed: https://review.fuel-infra.org/30694
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1663250,2017-02-10 09:08:24 UTC,"Reviewed: https://review.fuel-infra.org/30693
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1663250,2017-02-10 09:08:16 UTC,"Reviewed: https://review.fuel-infra.org/30696
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1663250,2017-02-10 09:08:05 UTC,"Reviewed: https://review.fuel-infra.org/30695
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1663250,2017-02-10 09:08:00 UTC,"Reviewed: https://review.fuel-infra.org/30691
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1663250,2017-02-10 09:07:58 UTC,"Reviewed: https://review.fuel-infra.org/30697
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1663250,2017-02-09 16:54:24 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30694"
1663250,2017-02-09 16:58:37 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30696"
1663250,2017-02-09 16:57:00 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30695"
1663250,2017-02-09 16:48:37 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30693"
1663250,2017-02-09 16:40:31 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30691"
1663250,2017-02-09 17:09:43 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/30697"
1663258,2017-02-15 16:06:26 UTC,Paraphrasing Casey's comments on a workaround for clarity:
1663258,2017-02-14 02:45:15 UTC,"Just so it's clear, this hampers our ability to automatically test creating a budget as we don't want to overload a user with named budgets -- we'd quickly have hundreds. A workaround to avoid this in testing would be appreciated."
1663263,2017-02-09 15:31:00 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1663263,2017-02-09 16:29:18 UTC,"This reporting process doesn't work from a CLI only machine. The text-based browser does not cope with the authorisation steps used to send the info to the site and sits with ""Waiting to hear from Launchpad about your decision.."" when I quit the browser."
1663263,2017-02-10 18:01:23 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1663263,2017-02-16 12:58:24 UTC,I tried an upstream kernel (4.4.48-040448-generic #201702090334). This is still doing the same thing.
1663263,2017-02-16 16:38:03 UTC,"On further investigation this issue appears to be specific to SCSI DVD drives. Hyper-V uses SCSI drives by default in Generation 2 VMs whereas VMware always uses IDE for the DVD drive, so the problem may be the SCSI driver rather than something that is specific to Hyper-V."
1663265,2017-02-09 15:31:12 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1663265,2017-02-10 18:00:06 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1663265,2017-02-15 14:36:48 UTC,Reproduced on latest 4.10 rc8
1663265,2017-02-17 13:08:52 UTC,"Regarding #3, it is a fresh installation of this Ubuntu version. 16.04 works correctly. I have seen similar behavior when I have upgraded 15.10 to newer kernel (for different kernels)."
1663269,2017-02-10 11:48:48 UTC,"Reviewed:  https://review.openstack.org/432151
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=497b9110997979f1d17c40f645cb8df8a9265928
Submitter: Jenkins
Branch:    master"
1663269,2017-02-27 16:27:22 UTC,This issue was fixed in the openstack/fuel-ui 11.0.0.0rc1 release candidate.
1663269,2017-02-14 14:23:36 UTC,Verified on Fuel 10 #1355
1663269,2017-02-10 12:11:00 UTC,"Reviewed:  https://review.openstack.org/432266
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=42837d6e20b0b48aefe11fa0ec0144d2a570e4d0
Submitter: Jenkins
Branch:    stable/newton"
1663269,2017-02-10 07:24:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432151"
1663269,2017-02-10 11:45:26 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/432266"
1663271,2017-02-23 11:44:03 UTC,"Spec is https://review.openstack.org/#/c/431605/, bug number will de added to commit message on the next patch set."
1663271,2017-02-13 15:22:23 UTC,Please provide a link to the specification you're referring to.
1663271,2017-11-14 15:34:40 UTC,"Changed status to Confirmed. Am guessing it was 'Incomplete' cuz the link to the spec was missing, but it has been provided."
1663271,2017-04-25 04:17:22 UTC,[Expired for Ironic because there has been no activity for 60 days.]
1663281,2017-09-01 12:04:30 UTC,With the last patch the segvault are fixed but the connection doesn't work.
1663281,2018-04-27 19:46:54 UTC,For trusty and precise/esm patches worked fine. But for Xenial it didn't fix the issue. Need more info/investigation for xenial.
1663281,2018-04-27 14:17:24 UTC,"For php5 code:
http://git.php.net/?p=pecl/networking/ssh2.git;a=commit;h=093906ec1c065e86ad1cd4dabbc89b1ccae11938"
1663281,2017-09-01 11:41:47 UTC,Under 14.04 i have use this patch for php-ssh2
1663281,2017-08-22 11:46:22 UTC,"After php-common-update from 2017.08-04 this affects ubuntu 14.04 with php5.5, too."
1663281,2017-08-22 11:42:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663281,2017-02-10 12:01:48 UTC,Further testing suggests that cherry-picking this particular commit might be insufficient for our usage scenario. I'll test a bit with the master branch of ssh2.
1663281,2017-02-09 20:24:42 UTC,"The attachment ""Patch against php-ssh2-0.12-39-g3dfe336+0.12"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1663286,2017-02-09 16:27:00 UTC,"Fixed by adding your user into the ""mirantis"" group."
1663287,2020-04-07 20:05:23 UTC,"If my memory is correct, this problem doesn't need qemu to execute the code, it only needs it to translate the code.  In the original test case the invalid instructions were actually dead code but still managed to crash qemu."
1663287,2020-04-07 18:56:26 UTC,"When I reread the thread I see Brian was doing some testing/fuzzing, that's why he found that out."
1663287,2020-04-07 11:16:06 UTC,"Yeah, QEMU crashing is definitely a bug that we should fix. (NB that it's not a 'security' bug, though -- we make no guarantee that malicious code run under QEMU with TCG emulation is unable to escape from it: there's too much unaudited and old code for us to be able to safely make that guarantee.)"
1663287,2020-04-07 10:46:12 UTC,I don't know how Brian go to his state.
1663287,2020-04-06 23:17:48 UTC,"Hi Brian,"
1663287,2020-04-06 21:07:15 UTC,I found the exact same bug. Tested on several hosts and qemu releases. The newest one I tested was on FreeBSD 12.1 host and qemu-4.1.1_1 built from ports.
1663287,2017-04-24 07:42:25 UTC,http://git.qemu.org/?p=qemu.git;a=commitdiff;h=075a1fe788d36b271ec2
1663287,2017-03-20 22:37:53 UTC,"Thanks for reporting this issue.
In fact, branches in a delay slot is ""undefined"" in the pre-Release 6 architecture.
MIPS architectre release 6 defines to signal Reserved Instruction exceptions for such cases.
However as it was undefined, it is better to signal RI and carry on rather than stopping simulation.
Hence I've made a patch for the msa case.
I will have a look into the other case. (sorry I've missed in the first place.)"
1663287,2017-02-13 15:02:25 UTC,"I've just found the same problem with gen_compute_branch1,"
1663287,2017-08-22 10:49:02 UTC,"Thanks for that fix.  I've just noticed that the second part, in gen_compute_branch1, wasn't included, though.  Could you take a look at it?"
1663288,2017-02-09 20:28:02 UTC,Seems like we need to be able to fallback unto software cursor dynamically as a new cursor image is configured.
1663288,2017-02-10 01:29:51 UTC,No problem... I'm working on dynamic cursor fallback right now. And prerequisite branches are up for review.
1663288,2017-11-03 16:42:41 UTC,Syncing task from Mir.
1663295,2018-04-20 17:29:25 UTC,"Just brainstorming, but one possible way of handling this might be to create a pool of barcodes that can be served out as the patron signs up for a card using the existing self-registration feature.  Once the pool gets low, Evergreen could inform the staff that more barcodes need to be added to the pool."
1663295,2018-04-20 18:06:58 UTC,Here is a link to a related discussion on the mailing list:
1663295,2018-04-24 16:00:10 UTC,"Definitely something our library, and possibly consortium, would be interested in. Like Terran the issue of duplication and patrons ""gaming"" the system is an issue we would like to avoid. Each library in our consortium is pretty autonomous and each offers varying levels of online services so account duplication is something we keep an eye out from."
1663295,2018-02-26 19:15:08 UTC,"I saw that Overdrive is using this vendor, Cognito, for their instant access/registration option.
https://cognitohq.com/identity-verification-service"
1663295,2020-04-16 16:38:15 UTC,C/W MARS would be interested in this development as well.
1663295,2017-02-09 16:35:56 UTC,"Hello, We (Lake Agassiz Regional Library) are also interested in this idea."
1663295,2017-02-09 16:07:16 UTC,Also - Pioneer is interested in development partners for this
1663295,2017-02-09 16:42:23 UTC,"We are interested in the possibilities of this idea. One of our key considerations would be online identity and address verification (which should be possible through a third party, such as the parties who verify identities for credit card applications), and another consideration is the prevention of duplicate accounts. In a large consortium like ours, we already have significant issues with individuals finding ways to get duplicate accounts, so we'd need to be sure that this process prevented the problem from getting worse."
1663296,2017-02-09 16:44:03 UTC,apport information
1663296,2017-02-09 16:31:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1663296,2017-02-09 16:44:05 UTC,apport information
1663296,2017-02-09 16:44:08 UTC,apport information
1663296,2017-02-09 16:44:10 UTC,apport information
1663296,2017-02-09 16:44:02 UTC,apport information
1663296,2017-02-09 16:44:17 UTC,apport information
1663296,2017-02-09 16:44:13 UTC,apport information
1663296,2017-02-09 17:00:15 UTC,This change was made by a bot.
1663296,2017-02-09 16:45:42 UTC,Apport information collected from a different kernel version due to wi-fi issues.
1663296,2017-02-09 16:44:29 UTC,apport information
1663296,2017-02-09 16:44:27 UTC,apport information
1663296,2017-02-09 16:44:14 UTC,apport information
1663296,2017-02-09 16:44:23 UTC,apport information
1663296,2017-02-09 16:44:22 UTC,apport information
1663296,2017-02-09 16:44:20 UTC,apport information
1663296,2017-02-09 16:44:12 UTC,apport information
1663296,2017-02-09 16:44:25 UTC,apport information
1663308,2017-02-09 23:21:22 UTC,"In my experience, that's limited to booting in KVM, and I'm not sure why (spurious keypresses being emulated, perhaps?)."
1663308,2017-02-09 17:02:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1663315,2017-05-25 14:30:24 UTC,"Markus,
I removed the s390x tag from this bug and filed one for that at
 https://bugs.launchpad.net/nova/+bug/1693524"
1663315,2017-02-18 22:16:44 UTC,Scott: that sounds reasonable...
1663315,2017-05-25 14:20:15 UTC,"Markus,"
1663315,2017-04-04 12:12:55 UTC,Seems like that libvirts cmdline argument is just for direct kernel boot [1]. So not an option...
1663315,2017-04-03 15:48:56 UTC,"What about appending something to the kernels command line instead of using smbios and/or dmi? For containers the commandline is considered as well (PID_1_PLATFORM), so why not for VMs as well?"
1663315,2017-03-30 12:44:24 UTC,"IBM s390x guy here, `dmi` doesn't work for us either. Nevertheless how to resolve this, did I understand it correctly that the fallback is the ""old"" way, ""polling until something works""?
Bug 1669675 describes this behavior:"
1663315,2017-03-01 19:31:30 UTC,"As an example of one such ""creative"" way to determine that a host is OpenStack:
  wget http://196.254.169.254/openstack/"
1663315,2017-02-17 17:34:18 UTC,"Thierry, you're right.  I'd like the platform to identify itself to the guest.  And openstack already does this in libvirt/kvm and i386/x86_64 (which I suggest is by far the most common deployment path)."
1663315,2017-02-16 18:49:06 UTC,Some observations:
1663315,2017-02-16 17:20:56 UTC,Sorry I was short on background information
1663315,2017-02-15 16:22:00 UTC,"Just to be clear, either way, that wouldn't look like a bug from the Nova perspective, rather a new possibility to inform the guest and that would probably need at least a blueprint for describing the new feature"
1663315,2017-02-15 16:12:04 UTC,"Well, the guest shouldn't know which hypervisor type it's running IMHO. That looks like a security concern at least."
1663315,2017-02-10 17:34:49 UTC,"Matt, maybe from the side of nova there could be an argument added to qemu that would pass the field that cloud-init wants? That is, other than through smbios arguments."
1663315,2017-02-17 09:56:15 UTC,"Beyond the bug vs. feature discussion (or which technical solution would be used to expose that information under ppc64) there is the question of whether exposing to the guest that it is running in a Nova-provided instance is desirable or not. In comment #3 Sylvain hints that it may create security concerns. As all security questions this is likely a trade-off, so we need to know what convenience we gain by leaking that extra information."
1663315,2017-02-09 23:03:32 UTC,Is there something that nova needs to do here? That's not clear to me.
1663316,2017-03-18 14:58:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663316,2020-07-30 19:46:27 UTC,libglib2.0-cil has failed during upgrade of 18.04 to 20.04
1663320,2017-02-09 18:03:14 UTC,"If one of the gradient stops is selected (with a shape- or path-editing tool if gradient-editing is enabled, or with the gradient tool), then the colors in the palette will change the stop color, not the fill (or stroke) color (see also what is displayed in Fill&Stroke for the selected gradient stop). This is intended for on-canvas editing of gradients and not a bug in itself."
1663320,2017-02-09 23:40:02 UTC,"Thanks for the explanation -- I can see how it ended up this way. Note that in that state the status bar also claims Shift-Click does something different than Click, which AFAIK is not true."
1663320,2017-02-10 00:24:16 UTC,Confirming that notification messages from the color palette could be improved to provide more context with regard to current selection (bug summary line updated accordingly).
1663324,2017-02-09 18:49:13 UTC,"Hi Dan,"
1663324,2017-02-10 11:15:00 UTC,"Hi Andres,"
1663324,2019-08-16 19:31:23 UTC,I'm seeing this still occuring when using the FCE tools (cpe-foundation) to build out an HA MAAS cluster with externally clustered postgres DB.
1663327,2017-03-01 17:53:51 UTC,This seems like a general OpenStack issue: bug #1217874
1663327,2017-03-02 12:57:44 UTC,In our cause there is no way to influence the device under which the volume will show up (like it is in libvirt. So my suggestions is to just set nothing there..
1663332,2017-02-10 11:29:17 UTC,"Hi Oleksiy,"
1663332,2017-03-20 08:14:07 UTC,"Reviewed: https://review.fuel-infra.org/32322
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1663332,2017-03-20 07:47:14 UTC,"Reviewed: https://review.fuel-infra.org/30659
Submitter: Pkgs Jenkins <email address hidden>
Branch: master"
1663332,2017-03-20 07:37:51 UTC,"Reviewed: https://review.fuel-infra.org/32321
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1663332,2017-02-10 10:49:17 UTC,"Hi Billey, what version of Fuel do you use?"
1663332,2017-03-17 10:19:02 UTC,"Fix proposed to branch: 10.0/newton
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/32321"
1663332,2017-03-15 10:07:19 UTC,"From unit testing with qemu, ovs & dpdk I found that moving to dpdk 16.11 give much better performance provided that INDIRECT_DESC feature is not disabled in dpdk's vhostuser configuration. There is a patch in review to ensure this feature is enabled in future OVS versions. https://mail.openvswitch.org/pipermail/ovs-dev/2017-March/329228.html"
1663332,2017-03-20 07:14:30 UTC,"Reviewed: https://review.fuel-infra.org/30635
Submitter: Pkgs Jenkins <email address hidden>
Branch: master"
1663339,2017-03-01 18:41:23 UTC,Any plan to address this regression?
1663339,2018-01-25 09:33:29 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3642
1663344,2017-02-09 20:36:26 UTC,This is a realistic feature for certain types of brakes that apply a minimum service reduction when first moved to certain brake positions.
1663344,2017-02-13 14:16:08 UTC,Thanks Peter.  Zig Zag is fantastic bit of modelling.  I'll contact you on ZZ contact page to discuss brakes issue.  I'm in awe of what you have accomplished!
1663346,2017-02-09 20:02:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1663348,2017-10-03 13:13:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663351,2017-09-07 09:35:40 UTC,related question which you asked : https://answers.launchpad.net/hplip/+question/293780
1663351,2017-09-07 09:38:23 UTC,"I believe it may not be due to certs, but that it does not support redirect/https at all"
1663357,2018-04-15 08:03:44 UTC,Thank you for this report. Sorry for the delay to respond.  I shall incorporate it into the next release.  I'll try before bionic.
1663357,2018-10-11 18:07:09 UTC,"Hello,
I installed new distribution Kubuntu 18.10 Beta and there is old init skript. Is it possible to rewrite one line in the init.d sktipt?"
1663357,2020-01-29 19:55:18 UTC,"Hi Rolf,"
1663360,2017-05-29 19:55:36 UTC,"Ok, I re-installed 0.92.1 to check again.
The news is that, at least from what I can tell right now, the vanishing only happens upon undoing an action."
1663360,2017-05-29 19:36:23 UTC,This affects all files as far as I can tell. I've had to go back to 0.91 for now to be able to work but I can try to re-install 0.92 later to check if there are any files that don't suffer from this bug.
1663360,2017-05-29 18:05:04 UTC,"could you attach the original svg file, for testing purposes?"
1663360,2017-05-29 16:45:03 UTC,I have the same problem.
1663369,2017-04-07 10:17:34 UTC,"Reviewed:  https://review.openstack.org/443664
Committed: https://git.openstack.org/cgit/openstack/nova-dpm/commit/?id=cacafd8819cc492995e010dc35f0a8c3729c2915
Submitter: Jenkins
Branch:    master"
1663369,2017-04-07 06:28:03 UTC,"Reviewed:  https://review.openstack.org/443193
Committed: https://git.openstack.org/cgit/openstack/nova-dpm/commit/?id=6f3261499c9d9cad6ec974ac2c354df2f9e77ffd
Submitter: Jenkins
Branch:    master"
1663369,2017-03-24 15:02:41 UTC,"Reviewed:  https://review.openstack.org/443616
Committed: https://git.openstack.org/cgit/openstack/networking-dpm/commit/?id=bac784f9028b72a9cc0b982690df754ba5ebe34b
Submitter: Jenkins
Branch:    master"
1663369,2017-03-23 16:13:59 UTC,"Reviewed:  https://review.openstack.org/443615
Committed: https://git.openstack.org/cgit/openstack/networking-dpm/commit/?id=52b5f3600d9c2c287c3554d954d676325fb64dfb
Submitter: Jenkins
Branch:    master"
1663369,2017-03-15 09:32:16 UTC,"Change abandoned by Andreas Scheuring (<email address hidden>) on branch: master
Review: https://review.openstack.org/445835
Reason: duplicate - I forgot to update the commit message during merge..."
1663369,2017-03-15 09:22:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445835"
1663369,2017-03-09 14:30:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443664"
1663369,2017-03-08 15:56:59 UTC,"Change abandoned by Andreas Scheuring (<email address hidden>) on branch: master
Review: https://review.openstack.org/442509
Reason: will use a customized oslo config option instead.."
1663369,2017-03-09 13:04:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443616"
1663369,2017-03-09 13:04:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443615"
1663369,2017-03-09 13:04:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443614"
1663369,2017-03-08 15:50:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443193"
1663369,2017-03-07 14:08:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442509"
1663369,2017-02-21 15:18:45 UTC,Doesn't block the Ocata release. I'm torn with the importance (low vs medium).
1663369,2017-03-09 13:53:13 UTC,"Reviewed:  https://review.openstack.org/443614
Committed: https://git.openstack.org/cgit/openstack/networking-dpm/commit/?id=fe8bc65fa6de67c67d7895940692a3af749c8e2f
Submitter: Jenkins
Branch:    master"
1663369,2017-07-10 13:46:31 UTC,"Reviewed:  https://review.openstack.org/443022
Committed: https://git.openstack.org/cgit/openstack/os-dpm/commit/?id=5e74551f60115684f24c62fc3695dc48d6d7281e
Submitter: Jenkins
Branch:    master"
1663369,2017-03-08 09:26:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443022"
1663376,2017-02-17 08:13:21 UTC,Thank you for your report Alexis and your help to make Ubuntu better!
1663376,2017-02-18 19:23:52 UTC,"Bug reported to Debian, reference:"
1663376,2017-02-21 22:09:58 UTC,I sent a patch to the Debian maintainers in Bug #855467.
1663376,2017-03-11 03:17:09 UTC,This bug was fixed in the package php7.0 - 7.0.15-1ubuntu4
1663387,2019-09-19 12:02:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1663390,2017-02-11 00:27:52 UTC,"Yup, this is a known issue."
1663393,2017-02-10 16:11:41 UTC,"according to neutron-lbaas README file, to enable a different driver need to use NEUTRON_LBAAS_SERFICE_PROVIDERV2."
1663397,2017-02-16 19:54:52 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1663397,2017-06-27 15:25:30 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1663397,2017-02-09 22:00:55 UTC,This bug is fixed in 3.1.2+dfsg1-1
1663397,2017-02-09 22:11:34 UTC,Uploaded spyder 3.0.2+dfsg1-0ubuntu0.2 to yakkety (patch attached).
1663400,2018-06-11 12:23:07 UTC,This bug was fixed in the package kexec-tools - 1:2.0.16-1ubuntu1~16.04.1
1663400,2017-02-10 19:12:04 UTC,[TEST with yakkety kexec-tools]
1663400,2017-02-14 17:12:52 UTC,The attached patch is for:
1663400,2017-02-14 19:17:31 UTC,This bug was fixed in the package kexec-tools - 1:2.0.14-1ubuntu3
1663400,2017-03-02 17:48:08 UTC,"Hello Manoj, or anyone else affected,"
1663400,2017-03-02 17:52:05 UTC,"Hello Manoj, or anyone else affected,"
1663400,2017-05-12 19:55:35 UTC,"$ sudo cat /proc/iomem | grep ""System RAM""
00d00000-fffecfff : System RAM
100000000-1ff369bfff : System RAM
1ff36b6000-1ff36b9fff : System RAM
1ff36bb000-1ff36c5fff : System RAM
1ff36d7000-1ffa7b8fff : System RAM
1ffac31000-1ffac47fff : System RAM
1ffac49000-1ffc404fff : System RAM
1ffc406000-1ffc588fff : System RAM
1ffcfc2000-1ffeac1fff : System RAM
1ffeae0000-1ffeafcfff : System RAM
1ffebb2000-1fff0fffff : System RAM"
1663400,2017-06-09 16:19:51 UTC,Please mention which versions were tested and re-mark verification-done-RELEASE in the tags.
1663400,2017-06-09 20:54:19 UTC,"$ dpkg -l | grep kexec-tools
ii  kexec-tools                         1:2.0.10-2ubuntu1.2                        arm64        tools to support fast kexec reboots"
1663400,2017-06-09 20:57:10 UTC,"$ dpkg -l | grep kexec-tools
ii  kexec-tools                         1:2.0.10-1ubuntu2.2                        arm64        tools to support fast kexec reboots"
1663413,2017-02-15 15:22:49 UTC,0.7.9 is now in zesty-proposed.
1663453,2017-03-01 06:39:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663453,2017-02-10 03:09:27 UTC,"StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at /build/sudo-av_5yt/sudo-1.8.19p1/src/sudo.c:328"
1663456,2020-01-14 06:30:19 UTC,"Change abandoned by Brin Zhang (<email address hidden>) on branch: master
Review: https://review.opendev.org/702070
Reason: This fix is redundant, in latest version, and base on https://review.opendev.org/#/c/580271/, the aggregare metadata's update_at can be populated automatically."
1663456,2017-06-23 12:52:13 UTC,"There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments."
1663456,2017-10-19 07:49:19 UTC,"Hello,"
1663456,2017-12-25 12:32:25 UTC,Are there any activities regarding this bug? I would like to assign it to myself
1663456,2017-12-25 13:41:53 UTC,"@Omar, you can assign it to yourself."
1663456,2018-01-24 10:08:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/537334"
1663456,2018-07-03 05:13:19 UTC,"Change abandoned by nalini (<email address hidden>) on branch: master
Review: https://review.openstack.org/537334"
1663456,2018-07-05 03:49:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/580271"
1663456,2019-10-30 16:34:25 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/580271
Reason: This is old and in merge conflict. I've marked the bug as wishlist/opinion and if someone wants to pursue this I'd suggest bringing it up on the mailing list. As noted earlier, we've had similar discussions about things like updating the parent instance action when one of it's child events is updated/created. Looks like we moved forward with updating the action record's updated_at when the event was finished (updated):"
1663456,2019-10-30 16:35:08 UTC,This could probably be considered the same as bug 1719561.
1663456,2020-01-11 10:23:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/702070"
1663467,2017-02-12 18:24:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663468,2017-02-10 05:02:11 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1663486,2017-02-10 07:10:26 UTC,"StacktraceTop:
 tracker_db_interface_execute_vquery (db_interface=0x0, error=0x7ff521ffad90, query=<optimized out>, args=args@entry=0x7ff521ffacb0) at tracker-db-interface-sqlite.c:2289
 tracker_db_interface_execute_query (interface=interface@entry=0x0, error=error@entry=0x7ff521ffad90, query=query@entry=0x5632546644b1 ""PRAGMA wal_checkpoint"") at tracker-db-interface.c:41
 tracker_store_wal_checkpoint () at /home/carlos/Source/gnome/tracker/src/tracker-store/tracker-store.vala:256
 tracker_store_checkpoint_dispatch_cb (task=<optimized out>) at /home/carlos/Source/gnome/tracker/src/tracker-store/tracker-store.vala:290
 _tracker_store_checkpoint_dispatch_cb_gfunc (data=<optimized out>, self=<optimized out>) at /home/carlos/Source/gnome/tracker/src/tracker-store/tracker-store.vala:312"
1663486,2017-07-22 16:18:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663504,2018-04-18 00:23:44 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/432184"
1663504,2017-11-07 00:42:00 UTC,This issue was fixed in the openstack/os-brick 2.0.0 release.
1663504,2017-09-01 16:16:54 UTC,Unassigning due to no activity for > 6 months.
1663504,2017-02-18 13:23:32 UTC,"Change abandoned by Zhao Liqiang (<email address hidden>) on branch: master
Review: https://review.openstack.org/432184"
1663504,2017-02-10 15:14:37 UTC,Can you include the relevant logs with error messages so that readers can verify the diagnosis against the perceived behaviour?
1663504,2017-02-10 08:55:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432184"
1663505,2017-03-01 13:47:57 UTC,Is it something that needs fixing on ironic side? Or is it going to be grenade-side only?
1663505,2017-03-03 15:02:40 UTC,"It is grenade-only, removed ironic."
1663505,2018-12-20 08:04:08 UTC,Is this issue still occurring?
1663516,2017-05-09 08:23:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663529,2017-06-13 13:02:54 UTC,Failure rate for the test is 0.06% http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops?duration=P3M&resolutionKey=day
1663529,2017-06-13 13:04:19 UTC,Setting as high since the incidence in logstash is high enough and it seems a good target for at least and E-R query.
1663529,2017-06-13 13:38:55 UTC,https://review.openstack.org/473851
1663529,2019-08-26 16:13:15 UTC,This bug report hasn't been updated in over 2 years and isn't hitting in e-r anymore so I'm marking it invalid:
1663530,2020-04-11 01:58:28 UTC,This has been fixed since the 16.10.1 release of this package.
1663531,2017-02-10 10:02:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1663541,2017-02-10 19:20:38 UTC,"FYI, we are testing the library against real hardware:
- HPE BL460C G9 server using ILO4
- Moonshot server using ILOCM
- m510x cartridge using a ""custom"" ILO4."
1663541,2017-02-10 20:06:17 UTC,"Hi Rene,"
1663541,2017-02-15 17:09:51 UTC,"A better design would be to discover the resource graph lazily; for instance, only populate a connection object's Systems field when the user accesses it. ""Autodiscover all available resources"" is almost always going to make way more requests than necessary."
1663541,2017-02-15 18:21:58 UTC,"I do not disagree with that, but Ironic is no tthe only use case we have in mind with this. We have another consumer, which is a brick interacting with CMDB for which we do want to have an exhaustive parsing of the graph."
1663541,2017-02-11 13:06:28 UTC,"OK thanks, I better understand your point.
Will it be ok with:"
1663542,2017-02-10 10:47:05 UTC,Alex - can you please attach a tarball of /var/log/landscape - it probably doesn't contain any secrets but you can share it on private-fileshare.c.c if you're concerned (because you put secrets in a script it ran)
1663542,2017-02-10 12:52:20 UTC,Here are the log files as requested.
1663552,2017-02-10 20:37:45 UTC,"Thanks for the bug Hadmut; I'm marking this public so that administrators can more quickly learn that using tcpwrappers for access control has the potential for trouble with mysqld, and can switch to iptables or other firewalling as appropriate."
1663552,2017-03-06 11:19:44 UTC,"Hadmut, could you report the package version number of mysql-5.7 in which you are seeing this please? The command ""dpkg-query -W mysql-server-5.7"" will output this."
1663552,2017-03-06 23:22:02 UTC,"Robie,"
1663552,2017-03-28 04:24:51 UTC,upstream bug: https://bugs.mysql.com/bug.php?id=84708
1663552,2017-03-30 13:13:42 UTC,Thank you for the update Daniel.
1663552,2017-04-24 22:05:47 UTC,"The bug #84708 on mysql is fixed. Please have a look to fix this possible fast because all servers with recommended ""ALL: PARANOID"" in hosts.deny can be brought to their knees by a single connection from a misconfigurated ip-address (aka botnet)."
1663552,2017-04-24 22:21:07 UTC,"Affected version:
# dpkg-query -W mysql-server-5.7
mysql-server-5.7        5.7.17-0ubuntu0.16.04.2"
1663552,2018-07-17 11:46:54 UTC,"The bug is fixed in MySQL 5.7.19 - see https://forums.mysql.com/read.php?3,658909,658909"
1663552,2019-01-14 14:39:56 UTC,"If it's indeed fixed in 5.7.19, then bionic and later are fixed. Can someone verify?"
1663555,2017-03-22 08:34:56 UTC,"Do the newer driver versions depend on nvidia-persistenced? That might explain this, since the root partition is not yet mounted."
1663555,2017-02-15 12:03:18 UTC,nvidia more appropriate package
1663561,2017-02-10 16:41:03 UTC,I've seen a number of people ask for something to this affect over the last few days. Definitely worth discussing how something like this would look and how one would trigger it
1663563,2017-02-10 12:47:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432288"
1663563,2017-02-15 12:21:31 UTC,"Reviewed:  https://review.openstack.org/432288
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=11aecb3c84a8eb4ebc0875d0a23006b98a4f38dd
Submitter: Jenkins
Branch:    master"
1663563,2017-02-27 16:28:41 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1663569,2017-02-10 17:35:10 UTC,"As discussed on the mailing list, I think this is a nice idea for usability, so that customers can better match up syslog messages from DHCP with the MAAS network model."
1663569,2019-09-19 11:55:54 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1663583,2017-02-10 13:05:31 UTC,Isn't that https://snapcraft.io/docs/build-snaps/scriptlets ?
1663583,2017-02-10 13:15:40 UTC,"Oh, weird that grepping the sources I wasn't able to find it..."
1663583,2017-02-10 19:36:38 UTC,"We're in the process of migrating all docs to snapcraft.io, so you probably should rely on that more than what's in the docs/ directory."
1663584,2017-03-20 14:31:14 UTC,"collect-metrics runs in a restricted hook context because it can execute concurrently with other ""lifecycle"" hooks. This prevents a long-running hook from interrupting data collection."
1663584,2017-02-10 12:52:00 UTC,Looks like is_leader does not work in the collect-metrics hook in juju 2.1 beta5 at least.
1663584,2017-02-10 16:44:36 UTC,We can fall back on the ceph is_leader() function.  I remember reading that the metrics-collect env is special and many juju functions are not available.  I'll change it and propose the patch again.
1663584,2017-06-01 06:01:58 UTC,"I think that this can be re-worked as Chris suggested earlier with the ceph is_leader() function, rather than relying on Juju's leader semantics to restrict metric collection to a single unit."
1663584,2017-06-01 02:33:13 UTC,"James, if this is a seriously blocking issue, we can put it on the stakeholders board and track from there."
1663590,2017-02-15 13:51:45 UTC,"$ snap list ubuntu-app-platform
Name                 Version  Rev  Developer  Notes
ubuntu-app-platform  1        37   canonical  -"
1663594,2019-08-29 00:02:13 UTC,"Change abandoned by Bruno Cornec (<email address hidden>) on branch: master
Review: https://review.opendev.org/443431
Reason: Sorry too old now to be merged. Please resubmit if still appropriate."
1663594,2017-03-11 15:39:23 UTC,"Change abandoned by ribaudr (<email address hidden>) on branch: master
Review: https://review.openstack.org/436793
Reason: Abandon as requested."
1663594,2017-02-14 16:21:52 UTC,"I am closely following the recent developments in openstack/python-redfish. If you wish, I can start working on this item:"
1663594,2017-02-28 11:07:17 UTC,We are adding tests with the DMTF mockup for version 0.5 using Docker containers Cf: https://review.openstack.org/#/c/430161/
1663594,2017-02-22 07:14:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/436793"
1663594,2017-02-28 20:18:01 UTC,"@Bruno this bug is about unit-tests I think you are talking about functional tests. For unit-tests we should not depend on any mockup server to be running in order to execute it, the APIs should be mocked so they are isolated from the service layer."
1663594,2017-02-10 19:24:29 UTC,"Yes we identified that point in our road map on the <email address hidden> ml.
Here is what was said :
Hello,"
1663595,2019-06-25 11:27:15 UTC,"Fixed in revision fbfcba6e4dadd3b78638ec67bf8a3e30a33b05ea
https://git.launchpad.net/kicad/patch/?id=fbfcba6e4dadd3b78638ec67bf8a3e30a33b05ea"
1663595,2019-06-23 14:10:53 UTC,"Ahh, ok, if you dump your branch name here I may try to monkey test it a bit."
1663595,2019-06-21 10:03:17 UTC,"@joshi-ji, the hotkey architecture has been completely rewritten for 6.0, so your patch no longer applies."
1663595,2019-06-22 21:51:50 UTC,"@Jeff, so doesn't this mean that this bug fixed?"
1663595,2019-06-23 13:53:23 UTC,"@Nick, it's only fixed in my branch.  I haven't merged yet because that branch also contains the new zone fill algorithm, which needed quite a bit of testing.  But I think it's nearly ready...."
1663595,2018-07-04 13:17:15 UTC,I have submitted the patch for it. Hotkey assigned is 'D'. The context menu opens a bit below cursor. Any help or suggestion is welcome.
1663614,2019-09-19 11:52:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1663620,2017-02-10 15:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1663620,2017-02-10 17:53:25 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1663620,2017-02-11 20:44:20 UTC,"Still got the same results, added the tag and marked as confirmed."
1663638,2017-02-12 18:24:06 UTC,"Sorry to have bothered you, but the problem is solved. Before I used your plugin to store the books on the Kobo in the kepub format, the number of pages of the epubs was displayed on a ""per book"" basis. It seems however that when the same books where stored as a kepubs, the default display mode became ""on chapter"" basis (anyway I did not change it and noticed it while checking the settings of the Kobo)). Hence my problem. I changed this in the settings to ""entire book"" now I can see the total number of pages in the book."
1663657,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1663658,2017-02-10 16:34:00 UTC,Similar issues is here:
1663658,2017-02-14 11:29:31 UTC,"So the problem here is that `qemu-img info ...` call takes more than 8 seconds of CPU time (note, that it's not wall clock time, it's the time spent by CPU on execution of the process both in user and kernel spaces). The interesting part here is that in successful runs of the CI job the timings are much lower - this call usually takes <= 0.3s (the same is true for upstream CI). As long as we are using the same image (cirros) and the same qemu-img version across jobs runs the only difference is the environment state (RAM/swap usage, disk load, etc). Unfortunately, atop logs for this period of time are not available, so we can't tell for sure, what exactly causes slowness of qemu-img."
1663658,2017-02-14 11:30:03 UTC,"Note, that we already increased the timeout from 2s to 8s in https://bugs.launchpad.net/mos/10.0.x/+bug/1643609  (a backport from upstream)."
1663666,2017-03-28 15:26:48 UTC,"Hello, is this error still happening?"
1663666,2017-02-13 12:38:37 UTC,"Yes running in zesty, today I could install unity8-session snap."
1663666,2017-04-17 13:59:48 UTC,Hello! The issue title is confusing.
1663666,2017-02-10 17:36:35 UTC,"I changed the nameserver to 8.8.8.8, rebooted the machine and I ran again."
1663666,2017-02-10 17:48:00 UTC,I had the same error earlier this week and name resolution worked fine.
1663666,2017-02-13 10:55:40 UTC,I looked into this a bit and found some theories about leaking fds that can confuse the resolver. I wrote testcode that spawns 50k go routines and never had any issues und 16.10.
1663666,2017-02-10 17:18:17 UTC,This looks like a network error on your side:
1663677,2017-02-14 13:33:08 UTC,"ok as promsied :) I have working mobile data, but mms always fails."
1663677,2017-05-09 16:12:49 UTC,"I was able to send an (extremely compressed) MMS message to myself today. Marking this as ""Fix committed"" until the next stable release."
1663677,2017-02-13 22:32:47 UTC,"Since MMS uses data for sending, i must consider this bug as same a Celular data!"
1663678,2017-02-10 23:39:05 UTC,"Is our namespace more ""protected"" by the fact we have the module on pypi ?"
1663678,2017-02-13 09:56:11 UTC,"Hi Bruno,"
1663678,2017-02-13 22:46:52 UTC,"We are in contact with the team developing the DMTF libbrary, and we would like to coordinate. However, goals are different, and python library used are also different. SO it could be challenging."
1663678,2017-02-17 11:38:31 UTC,FYI it's probably going to be a problem if somebody attempts packaging both libraries. I think the policies may prevent that.
1663679,2017-02-10 20:35:22 UTC,"Hello Benjamin, do you have a reliable way to reproduce this crash?"
1663679,2017-04-12 04:17:43 UTC,[Expired for tracker (Ubuntu) because there has been no activity for 60 days.]
1663679,2017-06-27 11:38:17 UTC,"Package: tracker-miner-fs
Version: 1.12.0-1ubuntu1
Priority: optional
Section: universe/utils
Source: tracker
Origin: Ubuntu
Maintainer: Ubuntu Developers <email address hidden>
Original-Maintainer: Michael Biebl <email address hidden>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 276 kB
Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.44.0), libtracker-miner-1.0-0 (= 1.12.0-1ubuntu1), libtracker-sparql-1.0-0 (= 1.12.0-1ubuntu1), libupower-glib3 (>= 0.99.0), libxml2 (>= 2.7.4), tracker (= 1.12.0-1ubuntu1), tracker-extract (= 1.12.0-1ubuntu1), procps
Homepage: https://wiki.gnome.org/Projects/Tracker
Task: ubuntu-gnome-desktop
Download-Size: 61,9 kB
APT-Manual-Installed: no
APT-Sources: http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages"
1663679,2019-10-24 11:38:33 UTC,is that still an issue and if so could you describe how to trigger it?
1663679,2019-12-24 04:17:32 UTC,[Expired for tracker (Ubuntu) because there has been no activity for 60 days.]
1663679,2017-02-10 17:55:00 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f561dd8c3a8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f561dd8c4b8 ""double free or corruption (out)"", action=3) at malloc.c:5046
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:3902
 __GI___libc_free (mem=<optimized out>) at malloc.c:2982
 g_pattern_match () from /tmp/apport_sandbox_qryQfj/lib/x86_64-linux-gnu/libglib-2.0.so.0"
1663705,2017-02-28 14:51:02 UTC,"From the log:
/var/lib/dpkg/info/mysql-server-5.7.postinst: ligne 143: /usr/share/mysql-common/configure-symlinks: Aucun fichier ou dossier de ce type"
1663705,2017-02-28 14:54:24 UTC,"Yeah, seems to be a 5.7 reoccuring of a 5.6 issue in bug 1455818"
1663705,2017-02-28 14:55:44 UTC,From there we can open a new bug once Robie and Lars looked at it in Detail
1663705,2017-02-28 14:58:42 UTC,Also look at https://bugs.mysql.com/bug.php?id=82198
1663705,2017-02-28 14:55:18 UTC,"I'm closing this as  a dup, could you try the workarounds listed there.
Then eventually please state what worked/or-not and that this applies to 5.7 for you.
There was recent activity there which already reopened it."
1663713,2017-02-10 19:14:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663713,2019-09-04 23:26:27 UTC,"Fixed upstream in 1.6.9 and 1.7.1+, which are part of all Ubuntu releases (at least) since bionic/18.04"
1663718,2017-03-07 10:43:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663718,2017-03-13 11:04:12 UTC,Testing packages for snapd-xdg-open master are in:
1663725,2017-03-28 12:58:14 UTC,There are a lot of custom udev rules
1663725,2017-03-28 15:19:23 UTC,"> Are all of those included in the initramfs as well? (check with e.g. lsinitramfs)
"
1663727,2017-12-21 03:34:02 UTC,"I've recently installed Ubuntu 16.04.2 Server Edition on DELL Poweredge 2950 and the syslog is filling up with,"
1663727,2017-12-21 03:51:04 UTC,"While waiting for any one of you guys to return, I'm going to go ahead and test out the upstream kernel by downloading below files,"
1663727,2017-12-21 07:34:22 UTC,I tried the upstream kernel 4.15 but no luck. Error still exists.
1663727,2017-12-21 07:35:46 UTC,TAG: kernel-bug-exists-upstream
1663727,2018-01-23 07:43:38 UTC,Please try latest mainliner kernel.
1663727,2018-01-03 08:04:55 UTC,"I went ahead and tried to file an upstream bug at bugzilla but apparently this bug has previously been reported and fixed.
Anydoby interested can go and read the link below.
https://bugs.freedesktop.org/show_bug.cgi?id=34457"
1663727,2018-01-11 14:28:51 UTC,"FWIW, I just finished installing Ubuntu Server 16.04.02 and then upgrading it to the latest on Jan 11, 2018.  I have a command line only system (it is just a really basic firewall) and the keynel is logging messages like this:"
1663727,2017-04-18 04:17:30 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1663727,2018-01-02 06:38:44 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/Radeon"
1663727,2017-02-16 18:52:08 UTC,apport information
1663727,2017-02-16 18:52:02 UTC,apport information
1663727,2017-02-16 18:52:04 UTC,apport information
1663727,2017-02-16 18:52:00 UTC,apport information
1663727,2017-02-16 18:51:59 UTC,apport information
1663727,2017-02-16 18:51:57 UTC,apport information
1663727,2017-02-16 18:51:56 UTC,apport information
1663727,2017-02-16 18:51:54 UTC,apport information
1663727,2017-02-16 18:51:52 UTC,apport information
1663727,2017-02-13 16:19:14 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1663727,2017-02-11 06:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1663727,2017-02-10 20:28:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1663727,2017-02-16 18:52:06 UTC,apport information
1663729,2017-02-17 04:57:59 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc2 release candidate.
1663729,2017-04-14 09:24:05 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1663729,2017-02-27 20:28:48 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1663729,2017-02-15 16:43:32 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/433014
Reason: https://review.openstack.org/#/c/433922/"
1663729,2017-02-15 23:15:23 UTC,"Reviewed:  https://review.openstack.org/433922
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2ea55fe953107e0a406c5a934c3a6d8b0bebfd5
Submitter: Jenkins
Branch:    stable/newton"
1663729,2017-02-14 20:45:12 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433922"
1663729,2017-02-15 00:43:29 UTC,"Reviewed:  https://review.openstack.org/432688
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=681e3776187d3ce3f7ccba8da056c007aa570232
Submitter: Jenkins
Branch:    stable/ocata"
1663729,2017-02-11 00:07:48 UTC,"Reviewed:  https://review.openstack.org/432352
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6e5b1d289b68f635d369dc092eff5595fb12c331
Submitter: Jenkins
Branch:    master"
1663729,2017-02-13 11:45:27 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433014"
1663729,2017-02-11 18:55:04 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/432688"
1663731,2017-02-28 11:11:31 UTC,We agree with the above.
1663732,2017-02-10 20:09:27 UTC,Caught during a mojo spec run for xenial-mitaka with juju 2.x:
1663737,2017-02-12 13:12:32 UTC,"Newest gnome-terminal declares the --execute/--command options obsolete, and states that a lone ""--"" followed by the arguments is the desired way to go. That one doesn't suffer for me in newest gnome-terminal (git snapshot). Could you please try this with your version, that is:"
1663737,2017-02-13 16:09:43 UTC,"Egmont,"
1663737,2017-02-13 16:10:20 UTC,"The man page for the version that I have does not mention '--' nor the fact that the --execute
option is obsolete --- BUT!   ... the '--' option *does* work and functions as desired with
the command-line you gave...   the '-h' is echoed properly."
1663737,2017-02-13 17:04:08 UTC,"Official gnome-terminal release does not have a manpage, it's added by Debian or Ubuntu (not sure which), indeed they should fix it."
1663738,2020-01-25 12:02:41 UTC,"Long since fixed, assuming it was related to libexif. Closing."
1663742,2018-05-24 23:45:22 UTC,"Yeah, this should probably be configurable separately."
1663742,2018-05-25 16:47:09 UTC,"no, I think on EC if you hit every primary and find *nothing* you can 404 - we probably don't even need to hit EVERY primary in a 15+3 schema."
1663747,2017-02-10 21:48:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663747,2017-09-20 21:08:54 UTC,Do you plan to release any patch for this issue?
1663750,2017-02-10 21:34:05 UTC,"Hello, I noticed a new thing."
1663755,2017-02-10 21:49:40 UTC,"FYI, this MP added the tempest charm to specs:
https://code.launchpad.net/~gnuoy/openstack-mojo-specs/tempest-stable-spec/+merge/315760"
1663755,2017-02-10 22:04:09 UTC,"FYI, failed on:  specs/full_stack/stable_deploy/liberty"
1663755,2017-02-10 22:06:19 UTC,"The tempest spec MP only added tempest to the xenial collect file, all other series trip on this.  Raising MP."
1663755,2017-02-10 22:10:45 UTC,Triaged crit as multiple specs cannot exercise re: freeze/release testing.
1663755,2017-02-10 22:22:35 UTC,Affects the following non-Xenial specs:
1663756,2017-02-12 07:24:18 UTC,Thanks for taking the time to file a report!
1663770,2017-02-13 13:59:20 UTC,Can you specify what version you reverted back to?
1663771,2017-03-15 09:50:05 UTC,Moving to won't fix due to the Medium priority.
1663771,2017-03-15 09:42:04 UTC,Fixes are proposed:
1663771,2017-02-17 12:02:20 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Jordan Pittier <email address hidden>
Review: https://review.fuel-infra.org/30999"
1663771,2017-02-14 09:34:37 UTC,Does the issue reproduce on the environment with a more powerful controller? I would suggest to setup a similar environment with 16+ GB of RAM and check the same operations.
1663771,2017-02-17 11:18:07 UTC,There are two issues around this bug:
1663771,2017-02-17 11:12:59 UTC,"Related fix proposed to branch: 9.0/mitaka
Change author: Jordan Pittier <email address hidden>
Review: https://review.fuel-infra.org/30996"
1663771,2017-02-10 23:34:41 UTC,Filed upstream bug - https://bugs.launchpad.net/swift/+bug/1663772
1663771,2017-02-17 11:19:06 UTC,"Additional note about 1. In my case, --debug is not required to reproduce issue, actually."
1663778,2017-02-11 22:27:25 UTC,"I don't think the possibility to assign EffectUnits to BusLeft/BusRight/BusMid should be removed from the engine, but I don't think they should be shown in skins. It's not obvious that those buttons in Shade affect the BusLeft/BusRight channels instead of the decks. So, it's not clear that the samplers could be routed through effects by assigning them to a side of the crossfader and pressing one of those BusLeft/BusRight buttons."
1663778,2017-02-11 15:05:11 UTC,Shade needs to conform with other skins to support controller mappings.
1663778,2017-02-11 15:39:00 UTC,"> I think this should be solved by replacing the BusLeft/BusRight switches in Shade with Channel1/Channel2.
"
1663778,2017-02-11 15:03:15 UTC,I think this should be solved by replacing the BusLeft/BusRight switches in Shade with Channel1/Channel2.
1663787,2019-10-01 13:21:05 UTC,Hello
1663794,2017-03-28 05:10:22 UTC,"Can you try again with v4.11-rc4?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc4/"
1663794,2017-03-24 11:27:22 UTC,"Yes, there is.
Also fixed turning off Runtime PM from mei_me controlled device."
1663794,2017-03-24 03:43:28 UTC,Does latest mainline have this issue?
1663794,2017-04-11 05:42:51 UTC,Then the best way is to file a bug at https://bugzilla.kernel.org .
1663794,2017-03-23 22:47:04 UTC,"Hello Kai-heng,"
1663794,2017-02-14 18:11:01 UTC,"The last shutdown just crashed. It's stuck in ""reboot: Power down"" as seen in attached image."
1663794,2017-03-22 17:41:02 UTC,FIXED!
1663794,2017-03-05 15:27:54 UTC,Not so fast.. =(
1663794,2017-03-03 17:10:02 UTC,"I've installed AMDGPU-PRO 16.60 and booted the system with reboot=bios parameter. Now the system is shutting down properly after a few seconds of hang. I am Not sure about which of these 2 modifications has ""fixed"" the issue."
1663794,2017-02-17 13:52:00 UTC,Also tried to boot the system without the following modules:
1663794,2017-02-14 18:26:40 UTC,Log from a shutdown/reboot WITH problems.
1663794,2017-02-14 18:24:37 UTC,Log from a shutdown/reboot WITH problems.
1663794,2017-03-29 13:13:21 UTC,"Yes, there is too.
Also fixed turning off Runtime PM from mei_me controlled device."
1663794,2017-03-23 03:41:43 UTC,"Hi Rene,"
1663794,2017-02-14 12:22:10 UTC,Log from Reboot/Shutdown without hangs.
1663794,2017-02-14 12:06:37 UTC,"Hello, Dimitri,"
1663794,2017-02-13 23:01:30 UTC,apport information
1663794,2017-02-13 23:01:28 UTC,apport information
1663794,2017-02-13 23:01:26 UTC,apport information
1663794,2017-02-13 23:01:25 UTC,apport information
1663794,2017-02-13 23:01:20 UTC,apport information
1663794,2017-02-13 23:01:18 UTC,apport information
1663794,2017-02-13 23:01:16 UTC,apport information
1663794,2017-02-13 23:01:15 UTC,apport information
1663794,2017-02-13 23:01:12 UTC,apport information
1663794,2017-02-13 23:01:10 UTC,apport information
1663794,2017-02-13 23:01:08 UTC,apport information
1663794,2017-02-13 23:01:06 UTC,apport information
1663794,2017-02-11 03:55:38 UTC,Last failed shutdown (With systemd debug mode activated)
1663794,2017-02-14 12:22:50 UTC,Log from Reboot/Shutdown without hangs.
1663794,2017-02-13 23:01:13 UTC,apport information
1663794,2017-02-14 10:15:52 UTC,"To debug shutdown problems we do need persistent journal.
You can enable persistent journal with $ sudo mkdir -p /var/log/journal
Reboot, and reproduce shutdown thereafter and attach /var/log/journal/*"
1663796,2017-02-13 12:18:23 UTC,Thanks for taking the time to file a report!
1663796,2017-02-16 03:40:29 UTC,I seem to have solved it by seeing a similar problem that was tracked to the tablet setting being switched on by default. After switching off the input devices tablet setting it hasn't happened again.
1663796,2017-02-15 19:00:51 UTC,Not sure if Duplicate as I don't use ctl+w to close and he reports it doesn't always happen when mine always happens.
1663801,2019-08-25 06:31:55 UTC,hello -vqmanh
1663801,2020-02-12 20:56:19 UTC,fixed it
1663801,2019-08-25 06:32:25 UTC,Hello
1663803,2017-02-11 06:36:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432562"
1663807,2017-02-11 06:39:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432567"
1663807,2017-02-11 06:43:22 UTC,"Reviewed:  https://review.openstack.org/432567
Committed: https://git.openstack.org/cgit/openstack-dev/sandbox/commit/?id=1cb0fb2eaf2d07799bb4a1df96c7fa2a3523ff29
Submitter: Jenkins
Branch:    master"
1663808,2017-02-11 06:11:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432540"
1663808,2017-02-11 06:24:34 UTC,"Reviewed:  https://review.openstack.org/432540
Committed: https://git.openstack.org/cgit/openstack-dev/sandbox/commit/?id=26e97ca17844d548cd82f176fbfe06bfb42240d9
Submitter: Jenkins
Branch:    master"
1663808,2017-02-11 06:53:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432572"
1663810,2017-02-11 06:14:28 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432545"
1663810,2017-02-11 06:35:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432561"
1663811,2017-02-11 06:10:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432536"
1663814,2017-09-01 16:16:57 UTC,Unassigning due to no activity for > 6 months.
1663814,2017-02-13 19:04:44 UTC,https://review.openstack.org/#/c/432326/
1663814,2018-02-05 19:09:15 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/432326
Reason: No updates for several months. Feel free to restore if you wish to continue with this."
1663817,2017-02-11 06:31:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432556"
1663818,2017-02-11 06:28:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432553"
1663819,2017-02-11 06:22:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432550"
1663819,2020-10-23 16:24:34 UTC,lolz
1663821,2017-02-11 06:46:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432568"
1663822,2017-02-11 06:25:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432551"
1663822,2017-02-11 07:28:15 UTC,"Change abandoned by amy kim (<email address hidden>) on branch: master
Review: https://review.openstack.org/432551
Reason: 버려"
1663824,2017-02-11 06:37:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432564"
1663825,2017-02-11 06:32:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/432557"
1663825,2017-02-11 07:07:57 UTC,"Reviewed:  https://review.openstack.org/432557
Committed: https://git.openstack.org/cgit/openstack-dev/sandbox/commit/?id=82b6f01ebf0d62de7790976d52e2dc874c479781
Submitter: Jenkins
Branch:    master"
1663826,2017-02-11 07:03:44 UTC,"Change abandoned by amy kim (<email address hidden>) on branch: master
Review: https://review.openstack.org/432552
Reason: ggg"
1663826,2017-02-11 06:26:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432552"
1663830,2019-11-03 03:39:47 UTC,fruitful
1663831,2017-02-11 06:28:43 UTC,doit test
1663832,2017-02-11 06:34:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432560"
1663833,2017-02-11 06:33:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432558"
1663841,2017-02-11 08:44:44 UTC,"Oops, I did not mean to file this against the gcc-defaults package.  Can someone please help me move it to the appropriate place?"
1663841,2017-02-18 03:56:49 UTC,"Hi,"
1663841,2017-02-18 06:31:20 UTC,"Okay,"
1663841,2018-03-02 23:00:38 UTC,I can confirm this issue is occurring for me as well. I have run all the latest updates and I still have the issue. The Razerkbd driver doesn't fix it. This is going to be a hard one to trace as it doesn't appear to cause a crash dump or log to be generated.
1663841,2018-03-03 23:16:53 UTC,The red hat bug is the most comprehensive so far: https://bugzilla.redhat.com/show_bug.cgi?id=1412877
1663845,2017-02-11 13:45:26 UTC,Any Ubuntu users?
1663845,2017-02-11 12:40:15 UTC,Not reproduced on Windows 10 x64 with Inkscape 0.92.0 r15299 (64 bit).
1663845,2017-02-11 13:19:21 UTC,"Eduard, it's definitely Inkscape problem, not OS. Because Inkscape 0.91 behave as expected on the same system.
And as you can see on attached screenshot, default Ubuntu open file dialog allow to set filepath manually."
1663845,2017-02-11 13:32:50 UTC,"not reproduced on Windows 10, Inkscape 0.92.0 r15299 (32 bit build) using native Windows open dialog"
1663845,2017-02-11 13:45:08 UTC,"reproduced, I think, when I use the gtk dialog. I click on the upper left symbol to get the Location text box. Then I try to paste the address and it fails. Then I try to manually type the address and the best I can do is the attached picture with 'https'. When I try to type in "":"", it refuses to accept the colon."
1663845,2017-02-11 21:28:45 UTC,"Opening files directly via http/https links in Inkscape uses gnome-vfs (a deprecated library). The dependency on gnome-vfs
1) is a build-time configure option, and
2) has runtime requirements (daemon) if used via GUI (IIRC)"
1663845,2017-02-11 23:00:24 UTC,"It appears that gnome-vfs support was intentionally disabled:
http://bazaar.launchpad.net/~inkscape.dev/inkscape/debian-packaging-stable/revision/60#control"
1663845,2020-09-15 10:55:06 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1663847,2017-02-11 13:51:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663849,2017-02-11 23:26:52 UTC,"Some further experimentation seems to hint that the tools that aren't working are not simply hanging. Instead, they are simply not able to draw anything on the screen. For example, after running HelloWorld.efi, nothing will appear. However, pressing Enter will return to the EFI shell prompt. Similarly, when running KeyTool.efi nothing will appear. However, pressing the down arrow three times to select the ""Exit"" menu option blindly and then pressing enter will return to the EFI shell prompt as well."
1663868,2017-02-11 14:13:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663890,2019-08-11 07:59:54 UTC,"Sorry for looking at this so late, but this probably isn't writing to a file on disk directly, right? Is this writing to an in-memory file-like object in some way?"
1663896,2017-03-08 18:04:18 UTC,"I should probably take ownership of this bug, since the current hotkey editor is my code..."
1663899,2017-02-19 06:17:07 UTC,"Hi Bruno,
The changes are as per below: ( As mentioned before just material property and engine)"
1663899,2017-02-13 17:34:09 UTC,"Hi, I realize that there are plenty differences between your script and the example script, depsite your statement that it is similar to the original.
Please be more accurate on which change caused the crash, and provide us with a way to pinpoint it (e.g. triggering the crash or not by changing just one line).
Bruno"
1663899,2017-02-15 15:05:31 UTC,"Hi Bruno, I just tried to change material to cohesion one consequently added cohesive IP and law, would you please advise me if it is not correct?"
1663899,2017-02-16 15:07:34 UTC,"Hi, what you describe in #2 sounds ok, in principle.
Since there are many other changes compared to the original script I can't tell if this is really the origin of your problem.
You may try to start again from the original script and re-apply each change to see when the problem appears.
B"
1663899,2017-02-19 06:25:21 UTC,"When I am turning on:
[Ip2_CohFrictMat_CohFrictMat_CohFrictPhys(setCohesionNow=True,label=""cohesiveIp"")],"
1663899,2017-02-20 11:01:03 UTC,"Interesting. There is still more than one difference between the two lines. Could you find which change shows the problem?
B"
1663899,2019-02-05 20:31:15 UTC,moved from https://bugs.launchpad.net/yade/+bug/1663899 to https://gitlab.com/yade-dev/trunk/issues/33
1663904,2017-05-28 22:10:09 UTC,"I'm getting this on an admittedly old Toshiba Tecra M9 which supposedly _does_ have an infineon TPM chip. And although tpm_version shows a chip of vendor id IFX to be present and there's a device, trousers or the tpm-tools always claim the device is disabled (after log entries as per OP). /sys/class/tmp/tpm0/device/temp_deactivated has a value of 1 and tpm_infineon is loaded as a module on top of the tpm_tis compiled into the kernel."
1663904,2017-02-16 21:22:27 UTC,"Sounds good. Give me couple more days. I'm on 4.9.8 with Arch and it has the same issue, but I'll try 4.10 to see what happens (on Xenial). Thanks for looking into it and the suggestion."
1663904,2017-02-13 16:23:09 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1663904,2017-02-17 00:29:57 UTC,"Assuming I did everything correctly (installed headers_all, headers_amd64, and linux-generic_amd64 from your link:"
1663904,2017-02-11 17:00:10 UTC,This change was made by a bot.
1663905,2017-02-11 17:53:06 UTC,"one quick and dirty solution:
/run/systemd/generator.late# rm radicale.service
systemctl daemon-reload"
1663905,2018-12-08 12:22:29 UTC,I have a simmilar problem with Ubuntu 18.04 too:
1663905,2017-04-10 17:46:05 UTC,The above trick does not work any more.
1663906,2017-04-13 16:36:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663911,2017-06-27 12:17:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663911,2017-06-28 08:38:18 UTC,"I can reproduce this bug inside LXC container with Ubuntu 16.04. It is related to bug of systemd: ""https://github.com/systemd/systemd/issues/6121"". There is a workaround to disable PrivateDevices for redis-server service. Example:"
1663922,2017-02-11 22:56:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663922,2017-02-11 23:02:43 UTC,"Happens to me since about a month. IDK if xorg or some other desktop subsystem, but the screen suddenly turns unresponsive except for a very laggy mouse cursor. Most of the time it happens with firefox after seeing some video (inside firefox, like in youtube, or outside, like using videos or vlc); the video end, we go to firefox, ans out of nowhere the screen's static and the mouse looks like the machine is slow as hell."
1663922,2020-10-13 07:54:57 UTC,Updating on my side:
1663926,2017-09-02 08:58:52 UTC,"Hi everyone,"
1663926,2017-08-23 23:53:30 UTC,Anything? is this even remotely on the radar?
1663926,2017-10-04 15:16:49 UTC,Changing the kernel parameters as proposed by Elias allowed me to successfully select the intel card using prime-select. This cut my power consumption in half (30 W -> 16 W as reported by powertop).
1663926,2017-10-31 11:14:22 UTC,"Elias comment about adding a parameter to /etc/default/grub solved the issue for me. Awesome dude, thanks!"
1663926,2017-08-02 23:52:07 UTC,I too am also desperate for a fix for this. Any progress?
1663926,2017-05-24 17:27:24 UTC,are there any news or workaround?
1663926,2017-04-05 17:23:46 UTC,looks like we have to wait for new kernel with ACPI calls fixed
1663926,2017-04-05 16:52:12 UTC,"related thread
https://github.com/Bumblebee-Project/Bumblebee/issues/764"
1663926,2017-04-05 15:25:37 UTC,"Ubuntu 16.10
nvidia 375 installed then switched to intel
freeze on lightdm login screen"
1663926,2017-02-23 17:46:47 UTC,I upgraded my 17.04 to kernel 4.10 and gave a try to latest 378 drivers (nvidia-378_378.09-0ubuntu0~gpu17.04.3_amd64) and got the same behaviour as with kernel 4.9. Tried to roll back to previous working version of the drivers (nvidia-378_378.09-0ubuntu0~gpu17.04.3_amd64.deb) but couldn't find the package in the repositories. Anyone knows if its possible to access this version?
1663926,2017-09-02 09:01:51 UTC,"As a side note, you can rescue your system if it is currently not booting."
1663926,2017-02-17 10:37:56 UTC,I rolled back to nvidia-378_378.09-0ubuntu0~gpu17.04.1_amd64.deb and at least I can boot with nvidia selected
1663926,2017-02-16 10:05:11 UTC,After yesterday's last dist-upgrade now it wont boot in any of the cards when nvidia-prime is used :(
1663926,2017-02-15 20:27:20 UTC,"In my case, it is most likely this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=156341"
1663926,2017-02-15 17:13:18 UTC,"I have tested 17.04 preview and without de nvidia-prime I can boot and shutdown with intel gpu. When I install nvidia 378 with prime I can boot with the nvidia and I am able to do prime-select and close and start new session with intel and the same way around. BUt, if I shutdown the laptop with the intel selected then it won't boot again, I have to start a recovery session and do prime-select nvidia (sometimes more than once) to be able to boot again."
1663926,2017-02-15 03:10:12 UTC,"I would like to add that another symptom of probably the same problem is constant freezes when on prime with intel selected. My system (XPS 15 9560, GTX1050M) boots fine, but freezes basically within 1 minute of the start of X."
1663926,2017-02-14 11:55:37 UTC,"Having the same issue on Dell XPS 9550 with GM107M [GeForce GTX 960M] on Ubuntu 16.10.
On the other hand: if you google this people are having these issues for years with nvidia drivers."
1663926,2017-02-13 11:09:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663926,2017-08-31 19:45:07 UTC,I can confirm this issue.
1663926,2017-02-20 20:58:07 UTC,"I'm Using a fresh installed Ubuntu 16.04.2 and tried both nvidia-378 and nvidia-375. A reboot or shutdown while using the Intel card results in a system freeze on a black screen, just after X is shutdown and where I can see the last terminal msg before X started.
I can't switch to a terminal with CTRL+ALT+F1....F6"
1663926,2017-08-24 06:41:11 UTC,"We need fix please. Installed nvidia drivers, selected intel and wont boot."
1663927,2017-02-14 03:04:43 UTC,Can you show the errors received?
1663927,2017-02-14 10:13:47 UTC,"There's no real errors, just juju metadata command doesn't exist."
1663927,2017-02-14 10:20:16 UTC,https://asciinema.org/a/34anw6pox4pgqqeb130ve0jt3
1663929,2017-02-14 10:46:08 UTC,http://asciinema.org/a/3ffewdvoizciql8dc1tbsvdon
1663929,2017-02-14 03:04:05 UTC,Can you show what message (if any) you receive? What does ls -al /usr/share/bash-completion/completions/juju* return?
1663937,2017-02-11 20:53:06 UTC,"For Yakkety, the only missing additional changelog would be 1.10.2's changelog:"
1663937,2017-06-29 17:21:50 UTC,"The verification of the Stable Release Update for nginx has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1663937,2017-06-29 17:21:44 UTC,This bug was fixed in the package nginx - 1.10.3-0ubuntu0.16.04.1
1663937,2017-06-27 15:24:37 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1663937,2017-06-21 19:44:40 UTC,I just tested an upgrade to 1.10.3-0ubuntu0.16.04.1 on Xenial. Works well in general and HTTP/2 keeps working.
1663937,2017-06-21 19:29:38 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for xenial for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1663937,2017-03-22 11:10:41 UTC,"Hello Thomas, or anyone else affected,"
1663937,2017-02-11 20:52:38 UTC,"For Xenial, also take into account the changes done between 1.10.0 and 1.10.3.  Note the CVE issue is already fixed in the Security repository, but other bugfixes should probably be included."
1663937,2017-02-22 15:37:39 UTC,1.10.3 is still stuck in zesty-proposed.
1663937,2017-02-16 19:35:56 UTC,"The Zesty update is still stuck in -proposed, so I'm not accepting the SRU at this point in time."
1663937,2017-02-11 23:11:10 UTC,"I'm unsubscribing ubuntu-sponsors since there's nothing to sponsor here. (Subscribing ubuntu-sponsors is usually done when you don't have upload rights for the proposed change, but that's not the case here since you already uploaded the updates.)"
1663937,2017-02-11 21:32:08 UTC,SRU Debdiff for NGINX in Yakkety
1663937,2017-02-11 21:31:12 UTC,SRU Debdiff for NGINX in Xenial.
1663937,2017-03-22 11:09:36 UTC,"Hello Thomas, or anyone else affected,"
1663937,2017-02-11 21:30:18 UTC,Proposed SRU packages have been uploaded for review in the queues.
1663947,2017-03-01 08:46:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663955,2017-02-12 00:54:54 UTC,I have found an entry in the application log in /var/log
1663965,2017-02-12 17:37:53 UTC,"Cairo/Poppler import has the right colors, but not the right shape."
1663965,2017-02-12 17:35:33 UTC,"Also reproduced on Xubuntu 16.04, Inkscape 0.91 and lp:inkscape/0.92.x rev. 15368."
1663965,2017-02-12 17:36:48 UTC,Default import (internal) is very dark.
1663965,2017-02-12 16:36:51 UTC,"confirmed on Windows 10, Inkscape 0.92.0 r15299
confirmed on Windows 10, Inkscape 0.92+devel 15506"
1663971,2017-02-26 04:56:22 UTC,"An update on this bug - since moving to Ubuntu 16.04.2 (which ships with 4.8), I can no longer seem to reproduce any wireless network downages. This also applies to 4.10."
1663971,2017-02-13 16:23:52 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1663971,2017-02-12 08:00:15 UTC,This change was made by a bot.
1663971,2017-02-13 16:43:20 UTC,"I have submitted this bug on 4.4 as recommended by a colleague, but the issue continued to persist in 4.9 and 4.10 in the same manner and dmesg emitted the same messages I point out here."
1663973,2017-02-23 16:10:39 UTC,Please could you specify what the host system guest system and virtualbox version was?
1663973,2017-02-24 09:58:35 UTC,"host: eOS freya
guest: Windows XP x86
virtualbox 5.1.14"
1663973,2017-04-26 04:17:34 UTC,[Expired for Files because there has been no activity for 60 days.]
1663979,2017-03-03 21:28:16 UTC,"La gestion des arbitres va être complètement revue dans la prochaine version majeure (V5) qui est en cours de développement. Ca fera d'ailleur partie de la grosse inovation de cette version avec une vraie gestion automatisée des resssources (arbitres/pistes).
Cette gestion pourra même être déportée sur un PC dédié à cette tâche et être supervisée par un opérateur affecté à cette tâche.
Il va de soi que ce bug sera traité à cette occasion."
1663984,2017-02-12 10:16:40 UTC,"Dear driger,"
1663984,2017-02-12 10:43:43 UTC,Yeah this does seem unrelated to bigdft... What's the recommended version? I guess I can always downgrade to it for the installation....
1663984,2017-02-12 17:24:16 UTC,"Well, remaking the configuration file with libtoolize and stuff gives a new weird error... Log attached.."
1663984,2017-02-13 06:50:00 UTC,"Dear Rohit,"
1663985,2020-04-28 13:34:33 UTC,I'm affected too
1663985,2020-04-30 01:13:11 UTC,Need more information
1663988,2017-02-12 15:14:25 UTC,...but I can't get in contact with the memory card. Apart from that all seems to work. Some of it even better than before....
1663988,2017-02-12 11:32:22 UTC,Well... Having no other option I've reset and erased the phone. Now it works...
1663988,2017-02-12 10:28:15 UTC,Further tinkering has lead me to believe the phone doesn't unlock the SIM. Hasn't this problem been up earlier ?
1663988,2017-02-12 10:18:27 UTC,I've just found out the phone doesn't see the SIM card nor the memory card. But it doesn't tell anything. I have cleaned the connectors of the SIM but it didn't help.
1663989,2017-02-20 17:06:54 UTC,Confirmed that the bug is fixed in the 4.10 kernel series.
1663989,2017-02-16 10:01:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663989,2017-02-16 16:50:02 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1663989,2017-02-16 23:00:56 UTC,"Dave, don't hijack bugs, this was originally filed on a system with nvidia, your bug is not the same."
1663989,2017-02-16 23:03:34 UTC,"Now that I had another look i-mail-3 has a hybrid system, so test the mainline kernel first and if it does fix the flickering then move back to linux."
1663989,2017-02-17 00:18:52 UTC,"Sorry I should have explained better, I also have a Lenovo Edge E540 which is how I initially found this bug report via Google, but mine does not have the nvidia chipset, only Intel, so I didn't see how this could be caused by the nvidia driver."
1663989,2017-02-20 17:06:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1663989,2017-02-20 17:30:16 UTC,This change was made by a bot.
1663989,2017-02-15 11:14:13 UTC,"Same issue, although I only have Intel graphics. Adding i915.enable_psr=0 to the kernel parameter line fixed the flickering for me."
1663991,2017-03-09 13:36:08 UTC,"To submit your patch, send your patch with the detailed description/changelog and your Signoff (ending with Signed-off-by: your name <email>), to the emails listed from ./scripts/get_maintainer.pl drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel sources). Once you have sent the patch upstream and it's accepted, please drop a note here so that we can cherry-pick/include the patch into Ubuntu kernel."
1663991,2017-03-09 15:46:28 UTC,A link from my first message:
1663991,2017-03-09 16:07:47 UTC,"@Simon I am sorry, if Simons comment has upset you.  It had been triggered by me asking on the IRC channel #ubuntu-kernel for help about finding the best resource to answer comment #12."
1663991,2017-03-10 15:25:02 UTC,"Several hours and a terabyte later, still going strong. I would consider it definitely fixed."
1663991,2017-03-09 19:56:35 UTC,"Vej, I was not upset, I was just feeling sad and looking for a light at the end of the tunnel.
I always loved Ubuntu, converted to this distro a long time ago with all my servers and desktops, but I cannot put my data at risk."
1663991,2017-03-09 19:59:37 UTC,"Hi Vej/Simon,"
1663991,2017-03-09 11:58:27 UTC,Thank you again. I have to say that I am not experienced in the standard Ubuntu or kernel update processes thus I was unsure how to interpret Joseph's message.
1663991,2017-03-09 16:09:00 UTC,@Simon I meant Davids comment of course.
1663991,2017-03-09 11:41:26 UTC,"To my knowledge (which is limited, when it comes to the kernel package with all its extra rules) this falls under:"
1663991,2017-02-13 16:27:50 UTC,The commit that fixes this bug was cc'd to upstream stable.  The fix should make it's way into Ubuntu through the normal stable update process.
1663991,2017-03-08 22:52:23 UTC,"> Can someone please explain me the Ubuntu update process?
Please read this first: https://wiki.ubuntu.com/StableReleaseUpdates.
"
1663991,2017-03-08 09:51:01 UTC,Can someone please explain me the Ubuntu update process? My systems are two kernel updates older now and the bug is still present.
1663991,2017-02-20 09:39:54 UTC,"Since this bug is really ruining my life I have been checking for a kernel update every day. I updated to 4.8.0-38-generic today but, sadly, the bug is still present. May I ask when the bug gets fixed and patched kernel is released as update? Thank you in advance."
1663991,2017-02-13 17:30:26 UTC,"Amazing, thank you very much."
1663991,2017-03-09 20:40:38 UTC,"I built a Yakkety test kernel with the patch.  It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1663991/"
1663991,2017-02-12 13:12:34 UTC,Thank you very much.
1663991,2017-02-12 11:58:44 UTC,"Hello,"
1663991,2017-02-12 11:55:46 UTC,"Sorry, I was unable to make apport-collect working."
1663991,2017-02-12 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1663991,2017-03-09 09:29:53 UTC,"Vej, Thank you very much for posting the links."
1663991,2017-03-10 11:36:35 UTC,"Joseph, I have installed the patched kernel. As of now, I have a USB hub connected with four drives attached to it. It is twice as much as I could connect before. The syslog seems to be perfectly clear and kswapd does not hang with 100% CPU consumption. I am stressing the drives a bit and everything is working fine so far. The problem looks completely fixed."
1663991,2017-04-13 16:15:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1663991,2017-03-10 18:49:32 UTC,"Thanks for testing and the update Simon.  I will submit an SRU request so the patch is included in the next kernel release.  Simon, you would not have to do anything special, the new kernel will just replace your existing kernel."
1663991,2017-03-10 19:11:15 UTC,"In fact, it already offers me to ""update"" to the previous kernel because the system understands this new one as a downgrade. No problem at all, I will not let the system to update the kernel until the new release is out."
1663991,2017-03-16 09:57:07 UTC,"Hello again, the gods must definitely hate me."
1663991,2017-03-16 12:42:44 UTC,@Joseph Do you have an open SRU request for this somewhere?
1663991,2017-03-16 14:39:48 UTC,"Thanks, I will do when I have more info. I will try one more boot and analyze the syslog closely."
1663991,2017-03-16 15:45:52 UTC,@Vej Yes the SRU request can be viewed in this mail thread on the kernel team mailing list:
1663991,2017-04-13 17:10:26 UTC,"Hello, I tested the patch using a testing kernel from Joseph Salisbury and it completely fixed the bug. Later, I was unable to boot to 4.8.0-42 which came with updates. I do not know why. I have never before experienced such a problem."
1663991,2017-04-24 14:11:40 UTC,This bug was fixed in the package linux - 4.8.0-49.52
1663993,2017-02-12 11:17:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/432745"
1663993,2018-04-03 15:19:57 UTC,"Change abandoned by Luka Peschke (<email address hidden>) on branch: master
Review: https://review.openstack.org/432745
Reason: No reply since a month"
1663995,2017-02-12 11:24:37 UTC,"StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 sd_event_wait (e=0x55a182922090, timeout=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2520
 sd_event_run (timeout=18446744073709551615, e=0x55a182922090) at ../src/libsystemd/sd-event/sd-event.c:2678
 sd_event_loop (e=0x55a182922090) at ../src/libsystemd/sd-event/sd-event.c:2705
 run (cgroup=<optimized out>, fd_uevent=<optimized out>, fd_ctrl=<optimized out>) at ../src/udev/udevd.c:1622"
1663995,2017-02-25 19:02:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664003,2017-04-27 04:17:29 UTC,[Expired for widelands because there has been no activity for 60 days.]
1664003,2019-09-17 07:09:33 UTC,Migrated to https://github.com/widelands/widelands/issues/3188
1664003,2017-02-25 11:46:09 UTC,"Sorry for my late reply.
I loaded the game and the ships worked, as you said. After playing a while, another two ships tried to pass through land, so I saved the game, quitted and loaded the savegame - and the ships recalculated their route."
1664003,2017-02-25 16:04:17 UTC,"I played that save game for a few hours, build more ships and ports but couldn't find any ship which sails over land. All looks good to me."
1664003,2017-02-25 20:08:32 UTC,"I just remind you, that there is a DBG window for a ship, that can list the path of ship - or more exactly I prepared new branch that would do it https://code.launchpad.net/~widelands-dev/widelands/ship_path_dbg"
1664003,2017-02-14 08:19:58 UTC,"According to the game loading screen, version is Build 19 ;)"
1664003,2017-02-13 19:06:10 UTC,"Fulgen, can you verify if this happens for you when loading the saved game?"
1664003,2017-02-13 09:14:10 UTC,"I let this run a bit. Yellow player has 1 ship, which shuttles wares back and forth between the 2 ports without any problem. It this the ship that you were talking about?"
1664005,2017-02-12 14:14:32 UTC,works fine after reboot. but this is quite strange that linux has started requiring reboot to get things working.
1664006,2019-10-04 12:22:18 UTC,"Don't know if this has been fixed at some point, but *with the theme I use* on 19.10 the buttons resize correctly. So either it's fixed, or the problem is with the specific theme (Ambient-Dark or whatever) that you're using."
1664009,2020-07-03 05:08:26 UTC,DistroRelease: Kali 2016.2
1664011,2020-07-03 05:07:54 UTC,DistroRelease: Kali 2016.2
1664013,2017-05-23 11:30:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664013,2017-02-13 01:14:52 UTC,"My work around above (described in the section ""code working around the issue"") does not consistently work. I was probably just lucky a few times in a row.
I tried several times, with varying delays between creating the huge file and transferring the snapshot but most of them fail and there seem to be no correlation with the delay."
1664025,2017-02-13 10:12:33 UTC,"Erm that does not look right to me (the fact that the mysql processes are part of the cgroup for the juju unit, resulting in them being terminated by systemd)."
1664025,2017-02-13 10:01:32 UTC,Looks like juju unit agent is tied with mysqld process somehow. That's why agent upgrade (agent stop/start) causes mysql clean shutdown.
1664025,2017-02-12 16:50:11 UTC,"Well, I reproduced it with a single percona-cluster once, but not in the second time. It might be related to some race conditions, so OpenStack deployment with more relation may be necessary to reproduce."
1664025,2017-02-12 16:45:23 UTC,"Ok, this issue is simply reproducible with a single percona-cluster unit. OpenStack deployment is not necessary to reproduce."
1664025,2017-02-12 16:10:09 UTC,"Somehow mysqld ""Normal shutdown"" kicked twice around agent upgrading."
1664025,2017-02-13 10:50:54 UTC,(with juju 2.1 beta5)
1664025,2017-02-13 10:50:41 UTC,Confirmed:
1664025,2017-02-14 13:40:44 UTC,"> However, I would expect the follower units to have been started normally, and not be part of the unit cgroup - so only the lead unit should see this effect.
"
1664025,2017-02-13 10:56:47 UTC,The charm has to init the local instance using:
1664025,2017-02-13 10:52:33 UTC,I think this maybe todo with the way that we have to bootstrap the PXC cluster.
1664025,2017-02-13 10:57:59 UTC,FWIW we might expect the service command to ensure that anything started under it is not part of the systemd cgroup for the calling daemon.
1664025,2017-03-02 17:36:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664025,2017-03-02 15:39:19 UTC,"Reviewed:  https://review.openstack.org/440278
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=189e5377e0b2917cb663eec3611071e5853707b5
Submitter: Jenkins
Branch:    stable/17.02"
1664025,2017-03-02 09:59:22 UTC,"Fix proposed to branch: stable/17.02
Review: https://review.openstack.org/440278"
1664025,2017-02-28 19:37:58 UTC,"Reviewed:  https://review.openstack.org/438917
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=fddc1b78f4251db97129f5246fff92fefb18353f
Submitter: Jenkins
Branch:    master"
1664025,2017-02-28 11:05:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438917"
1664025,2017-02-14 11:27:24 UTC,I am marking this bug as Incomplete for Juju while James investigates further.
1664025,2017-02-28 10:28:20 UTC,Marking Juju task as invalid - the way that pxc is bootstrapped in the primary cause of this issue.
1664025,2017-02-23 15:52:37 UTC,Hit the same issue when upgrading Juju from 2.0.3 to 2.1.0.1 with the percona-cluster charm rev 247.
1664025,2017-02-24 11:28:55 UTC,@anastasia-macmood
1664025,2017-02-24 01:07:24 UTC,"@Sandor Zeestraten (szeestraten),
And did workaround mentioned in comment # 17 - rebooting the leader unit after cluster gets up and running - help?"
1664025,2017-02-24 20:07:38 UTC,Really the bootstrap startup needs to be executed by systemd as well; that's a bit of a packaging change to make that easier to consume (the CentOS packages already provide appropriate systemd units for this).
1664025,2017-02-24 13:21:34 UTC,"You can also just do a stop/start of the mysql service; this issue is that the lead unit is bootstrapped using the service command, not systemctl:"
1664025,2017-02-28 11:01:13 UTC,"I can workaround this problem in the charm by using systemd-run to ensure that the bootstrap-pxc mysqld gets its own cgroup, but this does need a broader fix in packaging as well (raised distro task to cover this)."
1664035,2017-07-23 13:03:57 UTC,This bug is also in Gnome 3 and MATE 1.18. Meanwhile it has been fixed in both desktops on July 8th 2017:
1664035,2017-07-23 18:10:10 UTC,Thanks for the fix. :-)
1664038,2017-02-12 21:40:46 UTC,This is not Grub Customizer specific. Grub Customizer does nothing more than running grub-mkconfig (a tool bundled with grub 2) and parsing its output to generate the list of operating systems.
1664038,2017-02-16 16:26:04 UTC,"Daniel,"
1664038,2017-02-16 19:17:58 UTC,"I saw your screenshot (can't read the french question/answers). There are no modifications done from Grub Customizer. I suppose you get the same naming when running `sudo grub-mkconfig -o /boot/grub/grub.cfg` while watching its output. So, no, I don't believe it's from Grub Customizer."
1664038,2017-02-18 07:47:56 UTC,"Dear Daniel,"
1664038,2017-02-18 19:26:52 UTC,"ok, the output of grub-mkconfig/update-grub isn't really helpful."
1664047,2017-04-01 15:14:43 UTC,https://www.youtube.com/watch?v=A4syY5TGxq0
1664047,2017-05-31 21:36:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664049,2018-06-08 11:30:30 UTC,Looks like this was fixed in Artful onwards but still affects Xenial (but workaround for Xenial available as described).
1664054,2018-03-31 14:25:33 UTC,This is currently still present in Bionic's Shotwell 0.28.1-0ubuntu1.
1664054,2017-02-12 20:48:55 UTC,Upstream known as https://bugzilla.gnome.org/show_bug.cgi?id=738486
1664054,2018-03-31 14:20:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664062,2017-02-12 21:30:12 UTC,This change was made by a bot.
1664062,2017-02-13 16:28:37 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1664062,2017-11-25 22:55:54 UTC,I have the same problem with i7 7th gen. using a fresh Artful installation.
1664071,2017-02-13 19:54:38 UTC,"Neither - I see it when using space > pan, ctrl > change size and general selecting inside of a group although cannot identify the exact sequence.  Can not get back to the selection tool unless I select another tool and then select selection tool again and only then will it work."
1664071,2017-02-12 22:51:58 UTC,"Hi,
Is it https://bugs.launchpad.net/inkscape/+bug/1663952 or https://bugs.launchpad.net/inkscape/+bug/1657874 ?"
1664072,2017-06-21 03:22:51 UTC,I have also came across this error while combing through the logs trying to figure out another issue.
1664072,2017-02-12 22:39:08 UTC,"Open bug in launchpad.net
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664072"
1664072,2020-06-08 01:14:29 UTC,In a machine here it happens in a RTL8188CE 802.11b/g/n WiFi Adapter (rev 01):
1664072,2020-04-08 07:42:41 UTC,In a machine here it happens in a Gigabit Ethernet controller:
1664072,2020-02-20 17:46:51 UTC,I see it Linux 5.5.4 with a OpenVPN(UDP)/tun/VPN tunnel.
1664072,2020-03-28 17:11:04 UTC,I see it
1664072,2018-06-08 15:15:25 UTC,"I went over iwlwifi commits since then and I couldn't find any issue regarding TCP/GSO. That said, I agree that it seems to be harmless in that setup and that backporting 0b9aefea860063bb39e36bd7fe6c7087fed0ba87 should help on identifying if it's a false-positive or not."
1664072,2018-06-05 12:03:22 UTC,This harmless warning should be fixed backporting [0] to 4.9 series.
1664072,2018-06-05 12:00:48 UTC,"I added the following description on the Debian bug.
I close the Ubuntu bug, since you got it on a 4.9 kernel, and no still supported Ubuntu version has such kernel."
1664072,2018-06-08 15:40:05 UTC,"BTW, I had this same warning with vmxnet3 driver with 4.9. I tried a newer kernel and the message didn't appear. I posted my findings here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864642#95 - for reference:"
1664073,2017-02-12 23:01:01 UTC,This change was made by a bot.
1664088,2018-12-11 03:41:26 UTC,This is part of some geometry work along with lp:594060
1664088,2018-12-11 09:18:04 UTC,Should there be a way to disconnect line segments with common points? I imagine this is also a valid use case (e.g. rounding a corner by inserting an arc).
1664088,2018-12-11 14:27:33 UTC,Agreed.  Drag vs move just like tracks.
1664088,2019-05-11 23:08:13 UTC,I implemented a somewhat simplistic version of this for Eeschema line segments.  See EE_POINT_EDITOR's cases for SCH_LINE_T.
1664095,2017-02-13 10:38:39 UTC,"Hi, can you be more specific? What's not working? Which steps did you do? Which is your system configuration?"
1664095,2017-02-15 18:46:31 UTC,"OK anytime my system tries to update it fails that's all that I got off of
the notice, also anytime I try to install a new package form apt-get it
will not I stall I'm running backtrack5 r3, Linux 3.2.6 with KDE SC 4.5.3
Which I'm really new to using. I have also noticed that I don't have
permission to do thing's on here aswell I will try at getting a better
explanation on these bug reports and thank you for writing me back any info
you could give me would really b appreciated"
1664096,2017-03-02 14:13:09 UTC,"Please check, if the ""Indicator applets"" plugin is listed several times in the panel preferences (""Panel applets"" tab)."
1664116,2017-02-14 13:30:31 UTC,There is something wrong in the configuration.  Could you please provide the diagnostic snapshot.
1664116,2017-02-14 15:22:18 UTC,Snapshot
1664116,2017-02-15 09:15:58 UTC,"Anton, from the description above it follows that you took DVS plugin for 9.1 release. Fuel plugin catalog contains the DVS plugin 3.1.1 for 9.2 release. Please use it."
1664116,2017-02-15 10:07:02 UTC,"Im use
[root@fuel ~]# fuel2  fuel-version
api: '1'
auth_required: true
feature_groups: []
openstack_version: mitaka-9.0
release: '9.2'
[root@fuel ~]# fuel plugins list
id | name                   | version | package_version | releases
---+------------------------+---------+-----------------+--------------------
1  | fuel-plugin-vmware-dvs | 3.1.1   | 4.0.0           | ubuntu (mitaka-9.0)"
1664116,2017-02-15 10:41:52 UTC,"Anton, could you please provide a diagnostic shapshot, that made according to this instruction https://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/maintain-environment/create-snapshot.html"
1664116,2017-02-15 11:16:36 UTC,"It's obvious, that the problem is that if you specify only one cluster and one dVSw, the script can not parse the string.
But as soon as you add a semicolon at the end of the cluster description line and dVSw, like so:
Cluster1:ds3; <- here is a semicolon
everything works.
Just don't forget, that  after deploying you need to remove the semicolon
at the and of the line
    network_maps = physnet2:ds3;
in the file
 vmware_dvs-vcenter-sn1.ini"
1664116,2017-02-15 11:49:50 UTC,"I think we had check that. As a guess, do you enumerated all your vmware clusters in the 'cluster to dvswitch' mapping?"
1664116,2017-02-15 13:37:32 UTC,"The problem is that I only have one cluster and only one switch. Deploy stumbles on what could not from the string to make an array of clusters, since the cluster is only one. There in the code, perhaps you have a string list of clusters is not true in the array."
1664126,2017-02-16 01:19:14 UTC,"Change abandoned by yapeng Yang (yang.yapeng@99cloud.net) on branch: master
Review: https://review.openstack.org/432888
Reason: repeat"
1664131,2017-02-15 15:51:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664137,2017-03-25 17:29:05 UTC,"@Pradeep,"
1664137,2017-03-05 19:26:32 UTC,"@Hongbin,"
1664137,2017-03-05 18:26:00 UTC,"@Pradeep,"
1664137,2017-02-23 10:37:29 UTC,"@Wenzhi, How are you uploading the image?"
1664137,2017-02-23 10:20:51 UTC,"@Hongbin, I don't suggest to tag image via zun, i was thinking before uploading the image to glance, do we need to tag it using docker cli during image build?
I am not sure whether it will work or not."
1664137,2017-02-20 16:42:43 UTC,"@Wenzhi,"
1664137,2017-02-20 16:40:54 UTC,"@Pradeep, there is no ""tag"" operation in Zun. Do you suggest to add such command?"
1664137,2017-02-13 15:46:23 UTC,"@Wenzhi, shouldn't we tag the image before uploading it to glance?"
1664137,2017-02-23 10:36:20 UTC,"@Wenzhi, @Hongbin, I did below and it works perfectly fine for me.
vagrant@devstack:~$ cat Dockerfile
FROM nginx:latest
vagrant@devstack:~$ docker build -t test_image .
Sending build context to Docker daemon 87.61 MB
Step 1/1 : FROM nginx:latest
 ---> db079554b4d2
Successfully built db079554b4d2
vagrant@devstack:~$ docker save test_image | openstack image create test_image --public --container-format docker --disk-format raw
+------------------+------------------------------------------------------+

| Field            | Value                                                |


+------------------+------------------------------------------------------+

| checksum         | 989aa944d86b0585df15d08179eef207                     |
| container_format | docker                                               |
| created_at       | 2017-02-23T10:33:52Z                                 |
| disk_format      | raw                                                  |
| file             | /v2/images/beaa3c0b-a728-4ed0-b546-67f526907219/file |
| id               | beaa3c0b-a728-4ed0-b546-67f526907219                 |
| min_disk         | 0                                                    |
| min_ram          | 0                                                    |
| name             | test_image                                           |
| owner            | 8b68fba38c184c97a1115e594b3c7010                     |
| protected        | False                                                |
| schema           | /v2/schemas/image                                    |
| size             | 189803520                                            |
| status           | active                                               |
| tags             |                                                      |
| updated_at       | 2017-02-23T10:33:53Z                                 |
| virtual_size     | None                                                 |
| visibility       | public                                               |


+------------------+------------------------------------------------------+
vagrant@devstack:~$ zun run --name test8 test_image
+-------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| Property          | Value                                                                                                                                                                                                                         |


+-------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| tty               | False                                                                                                                                                                                                                         |
| addresses         |                                          ...
"
1664138,2017-02-13 08:16:31 UTC,"StacktraceTop:
 ResMgr::GetLong (pLong=0x55f1c66dc61b) at ./tools/source/rc/resmgr.cxx:1125
 ResMgr::ReadLong (this=this@entry=0x55f152f82cc0) at ./tools/source/rc/resmgr.cxx:1332
 ImageList::ImageList (this=0x55f152fd48f0, rResId=...) at ./vcl/source/image/ImageList.cxx:73
 GetImageFromList_Impl (nImageId=<optimized out>, bBig=bBig@entry=false) at ./svtools/source/misc/imagemgr.cxx:516
 SvFileInformationManager::GetFileImage (rObject=...) at ./svtools/source/misc/imagemgr.cxx:602"
1664138,2017-02-13 09:15:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664138,2017-02-14 03:50:05 UTC,Your LibreOffice partially updated. Wait for other 5.3.0 packages to get from proposed to release.
1664138,2017-02-16 22:35:15 UTC,"crashed with 2.5 while launching libreoffice
after it ask to recover an old crashed file ""without name.odt""
my answer was yes"
1664138,2017-02-17 08:25:03 UTC,Here is what happens here:
1664138,2018-02-19 20:33:52 UTC,Can the original reporter or anyone affected confirm whether this is actually fixed?
1664144,2019-10-31 04:17:32 UTC,[Expired for usb-creator (Ubuntu) because there has been no activity for 60 days.]
1664144,2019-08-31 11:55:55 UTC,This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu please let us know.
1664144,2017-02-13 08:25:46 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1664144,2017-02-13 09:20:00 UTC,"Can you please attach log from usb-creator-gtk, it's located here: ~/.cache/usb-creator.log"
1664144,2017-02-13 16:12:52 UTC,Here is the lo you asked for
1664149,2020-09-01 14:35:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664150,2017-02-13 09:16:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664150,2017-03-08 13:43:34 UTC,TODO: Check if these are related:
1664150,2017-03-10 06:51:43 UTC,"OK, the issue is not TutorialContent.qml because modifying that makes no difference."
1664150,2017-03-10 07:37:18 UTC,"Strangely iotop is showing unity-system-compositor's ""Mir/Comp"" thread is one of the top disk writers. If that's the problem then USC holding on to bypass frames too long would explain it."
1664150,2017-03-10 07:38:48 UTC,"  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
  265 be/3 root          0.00 K     28.00 K  0.00 %  2.21 % [jbd2/sda2-8]
19799 be/4 dan           0.00 K      8.00 K  0.00 %  0.83 % upstart --user
21082 be/4 root          0.00 K      0.00 K  0.00 %  0.37 % [kworker/u16:5]
16506 be/4 root          0.00 K      0.00 K  0.00 %  0.34 % [kworker/u16:1]
12778 be/4 root          0.00 K      8.00 K  0.00 %  0.00 % unity-syst~[Mir/Comp]"
1664150,2017-03-10 07:51:43 UTC,"  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
  265 be/3 root          0.00 K    440.00 K  0.00 %  2.73 % [jbd2/sda2-8]
12778 be/4 root          0.00 K     56.00 K  0.00 %  1.79 % unity-syst~[Mir/Comp]
21082 be/4 root          0.00 K      0.00 K  0.00 %  0.45 % [kworker/u16:5]
19677 be/4 root          0.00 K      0.00 K  0.00 %  0.20 % [kworker/u16:3]
21111 be/4 root          0.00 K      0.00 K  0.00 %  0.18 % [kworker/u16:0]
 1078 be/4 root          0.00 K      8.00 K  0.00 %  0.08 % accounts-daemon
 1230 be/4 syslog        0.00 K     16.00 K  0.00 %  0.00 % rsyslogd -~ain Q:Reg]
19799 be/4 dan           0.00 K     88.00 K  0.00 %  0.00 % upstart --user
20013 be/4 dan           0.00 K      4.00 K  0.00 %  0.00 % unity8 --m~full-shell"
1664150,2017-03-10 08:30:28 UTC,User error. And truth is stranger than fiction as always...
1664150,2017-11-03 16:36:15 UTC,Syncing task from Mir.
1664152,2017-02-16 10:37:15 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/434802"
1664152,2017-02-16 09:38:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/434770"
1664152,2017-02-15 14:40:44 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/434318"
1664152,2017-02-15 13:54:11 UTC,"Reviewed:  https://review.openstack.org/433071
Committed: https://git.openstack.org/cgit/openstack/fuel-agent/commit/?id=6f6fd2fa428e1ecdaaf36853679be00bd45aa108
Submitter: Jenkins
Branch:    master"
1664152,2017-02-13 14:13:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433071"
1664152,2017-02-13 13:29:00 UTC,This bug is a bug in unattended upgrades package from debian/ubuntu.
1664152,2017-02-13 14:03:59 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/433064"
1664152,2017-02-13 13:48:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433064"
1664152,2017-02-13 13:48:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433063"
1664152,2017-02-13 12:54:13 UTC,Marking as critical because it breaks default configuration
1664152,2017-02-13 14:04:07 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: master
Review: https://review.openstack.org/433063"
1664152,2017-02-16 10:37:29 UTC,"Change abandoned by Aleksey Zvyagintsev (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/434802"
1664152,2017-02-17 12:59:51 UTC,"Reviewed:  https://review.openstack.org/434802
Committed: https://git.openstack.org/cgit/openstack/fuel-agent/commit/?id=99b0cd6b3e46b75b1a9d7810bb81de1f2ff0a866
Submitter: Jenkins
Branch:    stable/newton"
1664152,2017-02-20 13:12:30 UTC,"Reviewed:  https://review.openstack.org/434318
Committed: https://git.openstack.org/cgit/openstack/fuel-agent/commit/?id=a3efbff41f8a0987225a12fc08a962cd3a77228d
Submitter: Jenkins
Branch:    stable/newton"
1664152,2017-02-27 16:23:38 UTC,This issue was fixed in the openstack/fuel-agent 11.0.0.0rc1 release candidate.
1664152,2017-04-06 12:55:19 UTC,Verified on 10.0 #1543. No unattended-upgrades package found.
1664152,2017-02-17 12:47:21 UTC,"Reviewed:  https://review.openstack.org/434770
Committed: https://git.openstack.org/cgit/openstack/fuel-agent/commit/?id=9f40d27bbecbee5ddf55fb69a2fb4cadf205ce25
Submitter: Jenkins
Branch:    master"
1664153,2017-02-13 11:39:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433013"
1664153,2018-04-12 13:02:01 UTC,"It is the same as
https://docs.openstack.org/developer/performance-docs/_downloads/basic_neutron.html#/NeutronNetworks.create_and_list_ports/failures"
1664153,2018-04-13 02:11:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561100"
1664158,2017-02-13 09:57:00 UTC,If I change the following two lines:
1664158,2017-10-13 12:00:39 UTC,"That's probably not the correct fix: `range(...)` in Python 2 is equivalent to `list(range(...))` in Python 3, so those lines should probably be"
1664158,2018-04-02 22:32:15 UTC,Both of the fixes proposed in the comments above are not *quite* right.
1664158,2018-06-26 22:01:45 UTC,"Hi Justin,"
1664158,2020-08-14 05:12:34 UTC,It sounds like there were a few proposals but they were not merged in? IMHO it would be better to have one of these sub-optimal patches rather than no action. Please let me know if I can do something to get this fixed. Thanks!
1664160,2017-04-19 04:17:29 UTC,[Expired for qtmir (Ubuntu) because there has been no activity for 60 days.]
1664160,2017-04-19 04:17:27 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1664160,2017-02-17 09:43:58 UTC,Incomplete - can't reproduce. Just ran mirvanity on zesty with the final Mir 0.26.1 release and Unity8 is within a few milliseconds of the demo servers.
1664160,2017-02-15 06:01:58 UTC,This might be explained by the QSGRenderThread not being ready... bug 1664828
1664160,2017-04-19 04:17:24 UTC,[Expired for Mir because there has been no activity for 60 days.]
1664162,2018-09-10 09:34:26 UTC,"on Cosmic, relevant source code is src/process/do_process.cpp:1064"
1664164,2017-02-21 20:58:21 UTC,Committed fix to the Debian GIT repository of the HPLIP package.
1664170,2017-02-13 10:26:31 UTC,apport information
1664170,2017-02-15 14:34:58 UTC,Reproduced on the latest 4.10 rc8
1664170,2017-02-13 16:33:30 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1664170,2017-02-13 10:26:36 UTC,apport information
1664170,2017-02-13 10:26:35 UTC,apport information
1664170,2017-02-13 10:26:33 UTC,apport information
1664170,2017-02-13 10:26:29 UTC,apport information
1664170,2017-02-13 10:01:00 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1664170,2017-02-13 10:26:25 UTC,apport information
1664170,2017-02-13 10:26:22 UTC,apport information
1664170,2017-02-13 10:26:21 UTC,apport information
1664170,2017-02-13 10:26:18 UTC,apport information
1664170,2017-02-13 10:26:16 UTC,apport information
1664170,2017-02-13 10:26:15 UTC,apport information
1664170,2017-02-13 10:26:12 UTC,apport information
1664170,2017-02-13 10:26:28 UTC,apport information
1664171,2017-08-27 06:55:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664175,2017-02-15 09:03:56 UTC,fix merged https://review.openstack.org/#/c/433033/
1664180,2017-02-14 05:01:00 UTC,I take it back. Simply adding a range check on the array lookup won't really solve this properly. We'll need to find out why the output has no valid current mode when it's being posted to.
1664180,2017-11-03 15:24:11 UTC,Syncing task from Mir.
1664180,2017-02-14 01:19:39 UTC,"I know this one. Looking at the offending source code, I remember previously having a fix written for it but for some reason never ended up needing or committing it."
1664180,2017-02-13 10:28:25 UTC,"== Stacktrace =================================
#0  0x00007effb88ff0b9 in mir::graphics::mesa::RealKMSOutput::max_refresh_rate (this=0x55c4b506e220) at /home/nick/Work/ubuntu/mir/mir-0.26.0+17.04.20170126.3/src/platforms/mesa/server/kms/real_kms_output.cpp:102
        current_mode = <error reading variable>
#1  0x00007effb88de663 in mir::graphics::mesa::DisplayBuffer::post (this=0x55c4b51d0200) at /home/nick/Work/ubuntu/mir/mir-0.26.0+17.04.20170126.3/src/platforms/mesa/server/kms/display_buffer.cpp:355
        output = std::shared_ptr (count 2, weak 0) 0x55c4b506e220
        min_frame_interval = {__r = 139636366146016}
        bufobj = 0x7effa00080e0
        predicted_render_time = {__r = 5}
#2  0x00007effbec63fce in mir::compositor::CompositingFunctor::operator() (this=0x55c4b51f9c30) at /home/nick/Work/ubuntu/mir/mir-0.26.0+17.04.20170126.3/src/server/compositor/multi_threaded_compositor.cpp:143
        delay = {__r = 139636366355200}
        pending = -1095108196
        lock = {_M_device = 0x55c4b51f9c68, _M_owns = false}
        disp_listener = std::shared_ptr (count 6, weak 2) 0x55c4b511b878
        display_registration = {deleter = {__this = 0x55c4b51f9c30, __disp_listener = std::shared_ptr (count 6, weak 2) 0x55c4b511b878}, owner = true}
        compositor_registration = {deleter = {__this = 0x55c4b51f9c30, __compositors = std::vector of length 1, capacity 1 = {std::tuple containing = {[1] = 0x55c4b51d0200, [2] = std::unique_ptr<mir::compositor::DisplayBufferCompositor> containing 0x7effa0009010}}}, owner = true}
        compositors = std::vector of length 1, capacity 1 = {std::tuple containing = {[1] = 0x55c4b51d0200, [2] = std::unique_ptr<mir::compositor::DisplayBufferCompositor> containing 0x7effa0009010}}
#3  0x00007effbec677ae in std::_Function_handler<void (), std::reference_wrapper<mir::compositor::CompositingFunctor> >::_M_invoke(std::_Any_data const&) (__functor=...) at /usr/include/c++/6/functional:1761
No locals.
#4  0x00007effbeb0cf96 in std::function<void ()>::operator()() const (this=0x7effaf7fdd80) at /usr/include/c++/6/functional:2127
No locals.
#5  0x00007effbedb75ef in (anonymous namespace)::Task::execute (this=0x7effaf7fdd80) at /home/nick/Work/ubuntu/mir/mir-0.26.0+17.04.20170126.3/src/server/thread/basic_thread_pool.cpp:40
No locals.
#6  0x00007effbedb7958 in (anonymous namespace)::Worker::operator() (this=0x55c4b528cde0) at /home/nick/Work/ubuntu/mir/mir-0.26.0+17.04.20170126.3/src/server/thread/basic_thread_pool.cpp:91
        task = {task = {<std::_Maybe_unary_or_binary_function<void>> = {<No data fields>}, <std::_Function_base> = {static _M_max_size = 16, static _M_max_align = 8, _M_functor = {_M_unused = {_M_object = 0x55c4b51f9c30, _M_const_object = 0x55c4b51f9c30, _M_function_pointer = 0x55c4b51f9c30, _M_member_pointer = (void (std::_Undefined_class::*)(std::_Undefined_class * const)) 0x55c4b51f9c30}, _M_pod_data = ""0\234\037\265\304U\000\000\000\000\000\000\000\000\000""}, _M_manager = 0x7effbec677b1 <std::_Function_base::_Ref_manager<mir::compositor::CompositingFunctor>::_M_manager(std::_Any_data&, std::_Any_data const&, std::_Manager_operation)>}, _M_invoker = 0x7effbec67783 <std::_Function_handler<void ..."
1664185,2017-02-24 16:09:13 UTC,"I was wondering why this feature was removed. But now I found out, that the real problem is the Mint-Y theme for controls! The font color is white on a white background and thus the information ""This update contains x packages: ..."" is not visible!"
1664186,2017-06-28 07:21:58 UTC,"I tested the issue on newest (pike) devstack with osc 3.11.0, the problem is not reproduced,
please see the result here: http://paste.openstack.org/show/613879/."
1664195,2017-02-13 12:11:04 UTC,"StacktraceTop:
 on_factory_appeared (connection=0x55811f0ea0c0, name=<optimized out>, name_owner=0x55811f515730 "":1.64"", data=0x55811f438e50) at panel-applet-container.c:427
 do_call () from /tmp/apport_sandbox_CiG3B2/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 on_name_owner_changed () from /tmp/apport_sandbox_CiG3B2/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 emit_signal_instance_in_idle_cb () from /tmp/apport_sandbox_CiG3B2/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /tmp/apport_sandbox_CiG3B2/lib/x86_64-linux-gnu/libglib-2.0.so.0"
1664197,2017-02-14 07:35:46 UTC,Decreased priority to Medium as this issue doesn't break not deployed or operational cluster: uploaded workflow will include an empty task list and won't be launched on cluster.
1664199,2017-02-13 13:00:01 UTC,- kmess: MSN messenger for KDE
1664199,2017-02-13 15:18:49 UTC,"New krusader synced to zesty. No longer depends on any part on konqueror, old OR new."
1664204,2017-02-14 08:34:22 UTC,https://review.openstack.org/#/c/433487/
1664218,2017-02-13 13:55:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433066"
1664218,2020-01-08 19:44:55 UTC,"Change abandoned by Clark Boylan (<email address hidden>) on branch: master
Review: https://review.opendev.org/433066
Reason: Fuel projects have been retired."
1664233,2019-07-08 07:29:36 UTC,This failure looks to have been fixed as I cannot make this test to fail locally and under stress.
1664234,2017-02-13 17:34:19 UTC,"Hello,"
1664248,2017-02-16 18:20:15 UTC,"Christian,"
1664248,2017-02-16 17:56:45 UTC,"Tom, Andres is exploring because we're trying to pull apart two issues here."
1664248,2017-02-15 17:19:39 UTC,"Also there does not seem to be any problem when I mirror everything from for xenial and trusty.  So for my use case https://bugs.launchpad.net/maas/+bug/1664384 is really more applicable.  It does not sound like it will never work for trusty, but that is about it."
1664248,2017-02-15 14:36:55 UTC,"@Tom,"
1664248,2017-02-15 17:16:14 UTC,It does not seem to report back properly when it fails to install packages with apt
1664248,2017-02-15 17:10:59 UTC,"Andres,"
1664248,2017-02-15 17:01:37 UTC,"Actually, If you could:"
1664248,2017-02-15 16:24:00 UTC,"Tom,"
1664248,2017-02-15 15:00:39 UTC,"I am getting a 404 now.  I can take another screenshot if you want.  That screenshot was not completely applicable to this specific issue, I found that I concurrently had another issue when I was trying to report it.  I was getting a 403 from the maas server since for some reason it did not add my subnet to the internal proxy.  I need to figure out why maas is not setting the values for that subnet like it should.  I would also like the ability to manually specify values for that config.  It is helpful to set a proxy peer and have a no proxy settings.  Currently I am just stomping over the file with chef and not letting maas update it, and could just set up another server.  But while that works it is not the best of solutions."
1664248,2017-02-13 22:32:36 UTC,Okay.  For my use case this bug will be irreverent if the bug you created is fixed and ideally works for all versions of Ubuntu.  But if it works just for Xenial and onward that would be enough.
1664248,2017-02-13 16:14:54 UTC,"@Tom,"
1664248,2017-02-13 22:04:44 UTC,"@Tom,"
1664248,2017-02-13 20:58:17 UTC,"Yeah we can configure it to mirror back-ports.  Just not multiverse, and we would prefer not to host source either."
1664248,2017-02-13 20:16:39 UTC,Do you know why it is trying to pull down source from the repos?  I don't see why the ephemeral image should ever compile anything so this seems like another useless dependency.
1664248,2017-02-13 20:10:31 UTC,So why does Trusty deploy with an ephemeral image of Trusty?  For example when I deploy centos it uses Xenial to perform the deploy and everything works fine.  It seems like this would be an easy way to insure that all features are available on all or at least more versions.
1664248,2017-02-13 18:39:17 UTC,"So after banging my head a while trying to find out why this wasn't working for you, I realized that you were deploying Ubuntu 14.04."
1664248,2017-02-13 17:05:18 UTC,It is rather hard to get a screenshot of the exact point it errors out since it immediately reboots.  But attached is the closest I got.
1664248,2017-02-13 17:03:58 UTC,Attached are the results of:
1664248,2017-02-13 16:10:12 UTC,"Hi Tom,"
1664248,2017-02-13 15:42:09 UTC,"1. /var/log/maas/*.log
  I attached the logs in the zip file
2. /var/log/maas/rsyslog/<machine-name>/<date>/messages
  No file was generated in this location
3. console log for the said machine.
  How do you propose I get a log of the system's console?"
1664248,2017-02-13 15:10:20 UTC,$ dpkg -l | grep maas
1664248,2017-02-13 22:09:39 UTC,"For the second part of my last comment, I've filed:
https://bugs.launchpad.net/maas/+bug/1664384"
1664248,2017-02-13 14:50:48 UTC,"Hi Tom,"
1664248,2017-02-13 20:46:10 UTC,"@tpmullan, could you configure your mirror to mirror backports, as well?"
1664259,2017-04-26 04:17:48 UTC,[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.]
1664277,2017-02-15 21:10:18 UTC,Suggested fix (expand wildcard using glob() and splice into place: 5 instances):
1664279,2019-03-27 13:19:45 UTC,Hey Chuck is this bug still occurring? Could you also let me know what version of OpenStack you are using?
1664279,2019-05-01 15:27:25 UTC,"closing for inactivity, is this is still occurring in the lastest openstack manila builds please feel free to re-open or create a new defect Thanks!"
1664282,2017-02-13 15:53:55 UTC,I believe this is a duplicate of existing bug: https://bugs.launchpad.net/bugs/1614364.
1664282,2017-02-14 08:11:08 UTC,"I think it kinda looks like the same. But it is more about the containers them selfs.
And if those containers need a fully bridged network without the dhcp solution lxd gives it."
1664287,2018-01-25 08:59:48 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1782
1664292,2017-02-14 12:25:31 UTC,I can confirm that this issue is present in Yakkety and that the package libopenmpi-dev is suggesting an incorrect package.
1664294,2017-02-16 23:40:40 UTC,"Reviewed:  https://review.openstack.org/434504
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=01ae5e7ec0df29bb07a27ae2f0aad1f5b563cf9d
Submitter: Jenkins
Branch:    master"
1664294,2017-02-16 23:41:10 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/435150"
1664294,2017-02-17 02:46:39 UTC,"Reviewed:  https://review.openstack.org/435150
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=0ee81f541fa0445c64e104730ddee97128cde885
Submitter: Jenkins
Branch:    stable/ocata"
1664294,2017-02-28 00:45:34 UTC,"Change abandoned by Ha Van Tu (<email address hidden>) on branch: master
Review: https://review.openstack.org/432183
Reason: This patch is included in the Netlink library patch: https://review.openstack.org/#/c/437311/"
1664294,2017-04-20 10:34:34 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/458436"
1664294,2017-02-28 00:50:33 UTC,"Change abandoned by Ha Van Tu (<email address hidden>) on branch: master
Review: https://review.openstack.org/434136
Reason: This patch is moved to https://review.openstack.org/#/c/438445/"
1664294,2017-03-07 21:57:45 UTC,"Reviewed:  https://review.openstack.org/433633
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=094d2d5f01914fbebd4e16cc2c41390a72b5874d
Submitter: Jenkins
Branch:    master"
1664294,2017-04-05 14:34:24 UTC,"Reviewed:  https://review.openstack.org/433598
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=8f6a1b90af7fdf3b865b700c09fbb415f4647812
Submitter: Jenkins
Branch:    master"
1664294,2017-02-16 03:00:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/434593"
1664294,2017-02-28 00:47:51 UTC,"Change abandoned by Ha Van Tu (<email address hidden>) on branch: master
Review: https://review.openstack.org/434593
Reason: This patch is moved to https://review.openstack.org/438445"
1664294,2017-02-15 20:41:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/434504"
1664294,2017-02-14 12:38:33 UTC,"@Kevin, @tuhv, i am working on the netns context manager"
1664294,2017-02-15 08:27:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/434136"
1664294,2017-02-14 16:16:21 UTC,Not sure if there's time to address this safely within the RC window.
1664294,2017-02-14 12:56:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433633"
1664294,2017-04-13 15:21:36 UTC,"Reviewed:  https://review.openstack.org/437311
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=b03caed15afca5cd372f8af429731069968c881a
Submitter: Jenkins
Branch:    master"
1664294,2017-02-14 11:19:38 UTC,"@tuhv,"
1664294,2017-02-14 11:17:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433598"
1664294,2017-02-14 10:06:38 UTC,"@tuhv,

>> Actually the netns we set is only on the oslo.rootwrap process mode.
> So it doest not affect to rpc calls, remote syslog.
"
1664294,2017-02-14 07:51:38 UTC,"@Cedric,"
1664294,2017-02-14 01:00:28 UTC,"@ Cedric Brandily,
Thank you for pointing out the problem in the Netlink feature.
My planning to improve the Netlink feature as good as possible, and also make the conntrack configurable (we can switch between conntrack-tools and Netlink), make conntrack-tools as default.
In my opinion, keeping the netlink_lib module is necessary because it can be a good reference of improving conntrack performance"
1664294,2017-02-14 00:54:55 UTC,"5) the change uses pyroute2.netns.setns in [3] which moves the current process to a specific netns
** it seems that when we enter the netns, the process seems to never go back in the root netns[9]. Is it an acceptable limitation?
** When the process is in a netns, every network action is done in the netns including rpc calls, remote sylog which won't work because they should be done in the root namespace."
1664294,2017-02-15 09:50:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/434181"
1664294,2017-04-20 09:38:11 UTC,"Reviewed:  https://review.openstack.org/438445
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=ec9d37183a085293f72f4c653e5c67e155c15be8
Submitter: Jenkins
Branch:    master"
1664294,2017-02-28 00:49:22 UTC,"Change abandoned by Ha Van Tu (<email address hidden>) on branch: master
Review: https://review.openstack.org/434181
Reason: This patch is moved to https://review.openstack.org/#/c/433598/"
1664294,2017-08-02 11:27:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/489980"
1664294,2017-04-20 10:34:46 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/458437"
1664294,2017-04-20 10:34:57 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/458438"
1664294,2017-05-19 19:45:38 UTC,"Reviewed:  https://review.openstack.org/458435
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=a08e30539a34f8ec20ab807ea1630d99d7adfb4e
Submitter: Jenkins
Branch:    stable/ocata"
1664294,2017-05-19 19:45:47 UTC,"Reviewed:  https://review.openstack.org/458436
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=86e6857be0258bff4d32b302733b1bef854091eb
Submitter: Jenkins
Branch:    stable/ocata"
1664294,2017-04-20 10:34:23 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/458435"
1664294,2017-05-19 19:45:54 UTC,"Reviewed:  https://review.openstack.org/458437
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=a54e42a3a313f2d89c5d6da6d222555160b8b2ad
Submitter: Jenkins
Branch:    stable/ocata"
1664294,2017-05-19 19:46:03 UTC,"Reviewed:  https://review.openstack.org/458438
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=d80832c2084ec7b70328a603b2bcc4e2776f0123
Submitter: Jenkins
Branch:    stable/ocata"
1664294,2017-05-26 06:30:23 UTC,I think we can close this bug. Though?
1664294,2017-05-26 06:31:46 UTC,"Sorry, I forgot mention reference [1]"
1664294,2017-07-13 08:31:59 UTC,"No one noticed that the step ""_apply_synchronized()"" at neutron/agent/linux/iptables_manager.py was time consuming when there were many firewall rules(>70), especially in function ""changes = _generate_path_between_rules(old_rules, new_rules)"" and ""_generate_chain_diff_iptables_commands()""?
I have test the performance for function ""_generate_path_between_rules()""， it consumed about 30s when generating param ""changes"" for command iptable-restore with 130 firewall rules. So I think this is where we need to improve."
1664294,2017-07-14 06:20:39 UTC,"this ticket is for FWaaS, we track work for neutron sec group here https://bugs.launchpad.net/neutron/+bug/1630832. Pls discuss there, I mark this as Fix Committed."
1664294,2018-01-02 16:56:20 UTC,"Reviewed:  https://review.openstack.org/489980
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=24b25ccfbe541b4699d88a819ecffd4b82b091ef
Submitter: Zuul
Branch:    master"
1664295,2017-04-27 14:16:16 UTC,"An update has been released today to bring chromium to version 58.0.3029.81. It is still behind by one release, but it fixes this particular bug."
1664295,2017-03-10 01:06:14 UTC,No one is taking this seriously? How hard can it be to bump the version to one that gmail supports?
1664295,2017-02-20 02:47:13 UTC,I can confirm that this error has been appearing for the past week with Mint 17.1 (64-bit). My version is also stuck on 53.0.2785.143.
1664295,2017-02-13 19:43:08 UTC,"Version 53.0.2785.143 Built on Ubuntu , running on LinuxMint 17.3 (64-bit)"
1664295,2017-02-13 19:42:11 UTC,"Sorry, meant to say CHROMIUM, not Chrome"
1664300,2017-03-21 01:37:01 UTC,"@Aaron,"
1664300,2017-03-21 14:06:41 UTC,"Yes, but it's on the wrong product."
1664305,2017-02-13 17:37:23 UTC,"One possible approach is to define a content-sharing plug in the 'core' snap for wallpapers, and then each wallpaper snap could provide a slot for it which, when auto-connected, will put that snap's wallpapers into /snap/core/current/usr/share/backgrounds/, and then include that directory in the default background chooser's list of default sources."
1664305,2017-08-18 13:02:28 UTC,I'm very interested in this topic and had extended discussions with jdstrand about how this could work in a safe way. This is not a priority for the snapd team currently but I'm personally interested in implementing this in the next few releases.
1664311,2017-02-13 17:57:47 UTC,"Not sure where exactly in the stack the error is, but it only happens under unity8 (not unity7) so adding Mir + Unity8 to the bug."
1664311,2017-11-03 16:42:45 UTC,Syncing task from Mir.
1664313,2020-05-20 04:17:29 UTC,[Expired for tempest because there has been no activity for 60 days.]
1664313,2020-03-20 19:50:25 UTC,"Due to the long inactivity I'll mark it as Incomplete, please, provide some info if the bug is still valid, otherwise it'll be closed."
1664313,2020-03-20 19:48:51 UTC,Is this still valid as there has been a long inactivity.
1664313,2017-02-14 09:01:25 UTC,"No, I guess its specific to Microsoft CI since we use VHD for images and we need that kind of resize."
1664313,2017-02-14 08:33:24 UTC,"I'm just curious. Is this happened in the upstream gate?
I couldn't find from the logstash log."
1664317,2017-02-13 18:55:47 UTC,"Looking at the ImageTarget class, the error is easily understandable: there is no __setitem__ method defined there. I wonder whether this is on purpose? If not, adding one should be easy :)"
1664317,2017-02-13 18:27:03 UTC,This was on master @ 33f943b2f.
1664320,2017-02-13 18:45:42 UTC,"Hello,"
1664321,2017-02-17 20:43:09 UTC,"I believe this is a related bug report in debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823978"
1664321,2017-02-17 20:27:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664321,2017-02-17 20:41:02 UTC,"I get the same error when compiling on 16.04, it links fine on 16.10"
1664326,2017-04-19 09:53:26 UTC,This issue was fixed in the openstack/python-monascaclient 1.6.0 release.
1664332,2017-02-13 19:07:28 UTC,Package versions: http://paste.ubuntu.com/23990217/
1664332,2017-03-07 11:15:21 UTC,"It looks like this needs a network-manager-strongswan-gnome package, which is not provided by the Mint repositories."
1664332,2017-03-30 17:39:16 UTC,"They reported that bug fixed in version 1.4.0 https://wiki.strongswan.org/issues/1429
Current version in Mint 18.1 is 1.3.1-1ubuntu1"
1664332,2017-03-30 17:42:54 UTC,Package added
1664332,2017-05-18 03:48:14 UTC,Any progress? Where I can download that (correct) package?
1664332,2017-02-13 18:52:29 UTC,Relevant paste: http://paste.ubuntu.com/23990119/
1664334,2017-04-14 09:24:01 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1664334,2017-02-17 04:57:54 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc2 release candidate.
1664334,2017-02-15 14:27:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/434316"
1664334,2017-02-15 17:09:44 UTC,"Reviewed:  https://review.openstack.org/433257
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2c1e1341214356808936c4a812c89d4008cdb284
Submitter: Jenkins
Branch:    master"
1664334,2017-02-13 20:53:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433257"
1664334,2017-02-13 20:24:07 UTC,"The other issue is the choices in the config option are too restrictive. keystoneauth1 doesn't actually validate the interface values, and 'auth' is a valid value meaning, don't lookup the endpoint in the service catalog, use the configured auth_url instead."
1664334,2017-02-15 23:58:49 UTC,"Reviewed:  https://review.openstack.org/434316
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a3089b41f6bfb10ce34581f72bc5fb029c836cd7
Submitter: Jenkins
Branch:    stable/ocata"
1664346,2017-06-29 14:24:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664347,2017-02-14 10:38:18 UTC,e-r-q for master grenade: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22TestVolumeBootPatternV2%3Atest_volume_boot_pattern)%20Server%20%5C%22%20AND%20message%3A%5C%22%20failed%20to%20reach%20ACTIVE%20status%20and%20task%20state%5C%22%20AND%20message%3A%5C%22Current%20status%3A%20BUILD.%20Current%20task%20state%3A%20spawning.%5C%22%20AND%20tags%3Agrenade.sh.txt%20AND%20build_branch%3Amaster%20AND%20build_status%3AFAILURE
1664347,2017-06-27 15:55:34 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'"
1664352,2017-07-07 17:31:47 UTC,"Is there something I can do to help make some progress fixing this bug? This issue is not applicable to the upstream software source however I did notice that it is relevant to Debian's isc-dhcp-client package which I believe is in a sense ""upstream"" for the Ubuntu package. In light of that should I pursue fixing the Debian package first?  (https://wiki.ubuntu.com/Debian/Bugs)"
1664352,2017-03-14 21:32:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664352,2017-02-13 20:29:40 UTC,"The attachment ""Support IF_METRIC for rfc 3442 routes"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1664352,2017-03-14 22:00:36 UTC,In my environment we have some dual-homed Ubuntu hosts that have one network interface with a WAN IP and one on a private network. For proper network connectivity we need to use the configurable metric value to prioritize the default route provided by the WAN connected interface over the default route (a NAT gateway) provided by the private network DHCP server. Unfortunately the current dhclient script ignores the configured metric when adding DHCP provided rfc3442 classless routes to the routing table. This patch from Tom fixes dhclient behavior for my use case.
1664355,2017-02-14 23:07:25 UTC,"Reviewed:  https://review.openstack.org/389081
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=7d315ca68476ef4ffb01a0e66e78d23e49ae5e9c
Submitter: Jenkins
Branch:    master"
1664370,2019-04-04 20:47:41 UTC,This issue was fixed in the openstack/manila-ui 2.18.0 release.
1664370,2019-04-16 18:41:33 UTC,This issue was fixed in the openstack/manila-ui 2.16.1 release.
1664370,2019-04-16 16:28:46 UTC,This issue was fixed in the openstack/manila-ui 2.13.1 release.
1664370,2019-04-15 12:43:41 UTC,"Reviewed:  https://review.openstack.org/651539
Committed: https://git.openstack.org/cgit/openstack/manila-ui/commit/?id=fdbbe8cc9a34faede4416ab9d92a014d1fbb6b44
Submitter: Zuul
Branch:    stable/queens"
1664370,2019-04-10 14:01:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/651539"
1664370,2019-04-04 20:11:44 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650129"
1664370,2019-04-10 06:52:44 UTC,"Reviewed:  https://review.openstack.org/650129
Committed: https://git.openstack.org/cgit/openstack/manila-ui/commit/?id=97441440e098d06166299e811504fe26eb3b16aa
Submitter: Zuul
Branch:    stable/rocky"
1664370,2018-08-10 03:09:16 UTC,"manila-ui currently shows ""Host"" as a field on selecting a share and viewing its detail attributes. The value of this field is empty; so it might confuse users. However, 'host' is entirely meaningless to non-admin users, so we should remove this field altogether; marking the bug low priority."
1664370,2018-12-04 19:25:50 UTC,Tagging this bug as a low-hanging-fruit for the remaining manila-ui implementation.
1664370,2017-02-14 15:31:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433716"
1664370,2017-02-16 23:42:20 UTC,"Reviewed:  https://review.openstack.org/433716
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=15b27e8fbe252328ed6c105942e915c76af23fb4
Submitter: Jenkins
Branch:    master"
1664370,2017-02-17 04:22:02 UTC,"Reviewed:  https://review.openstack.org/435182
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=6f6a31d595eec9d5c2735d91317c4d4742b920d7
Submitter: Jenkins
Branch:    stable/ocata"
1664370,2017-02-17 04:35:17 UTC,This issue was fixed in the openstack/manila 4.0.0.0rc2 release candidate.
1664370,2017-04-13 21:02:52 UTC,This issue was fixed in the openstack/manila 5.0.0.0b1 development milestone.
1664370,2017-02-17 00:59:11 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/435182"
1664373,2017-02-13 22:40:48 UTC,Please attach a test case (Inkscape SVG file) which suddenly fails to print on your system to allow further investigation on other systems/platforms.
1664373,2017-02-14 04:06:47 UTC,"Attached are three files.  The .svg was produced a couple of weeks ago.
With newly downloaded 0.91 32 bit Inkscape it only printed the man/clock
image in top left quadrant.  I then ""Saved as"" the pdf file and all
graphics printed.   I then exported the file as a .png file and all
graphics printed.
This problem also occurred with a newly produced  0.91 and 0.92 versions.
This only occurs with Inkscape and no other programs I use.  I use Excel,
Adobe Photoshop Elements 14, Word, Photoscape and several other programs
with no adverse reactions.
I appreciate your assistance in helping with this problem.  Thank you.
Ron Johnson"
1664382,2017-02-13 21:59:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664382,2017-02-13 23:55:03 UTC,*** This is an automated message ***
1664383,2017-02-13 22:26:10 UTC,"This does indeed feel inconsistent, considering that, when snaps _are_ installed, `snap list foo` (when foo isn't installed) results in ""error: no matching snap installed"" and a non-zero exit code."
1664383,2017-02-17 08:43:25 UTC,https://github.com/snapcore/snapd/pull/2876
1664383,2019-10-29 18:12:21 UTC,The pull request fixing this bug was merged in 2017. I'm marking it as fixed released
1664384,2017-02-14 18:34:36 UTC,The easiest way to do this is to provide the sources_list that should be used as the template to cloud-init.
1664388,2017-02-14 09:03:28 UTC,"For the certified kernels, I am not sure we want an open-ended ""stick
this on the kernel cmdline"" mechanism. We probably DO want a
parameterized ""here are some well-behaved things you can enable or
disable in your gadget snap""."
1664388,2017-02-14 10:17:15 UTC,note that you can easily manage the panic parameter via sysfs ...
1664388,2017-02-14 10:25:37 UTC,"oh, also note that in this specific case you definitely *do not* want to unset panic=-1 before systemd is up to not lose the panic behaviour of kernel and initrd"
1664388,2017-02-15 19:54:21 UTC,@Ogra
1664388,2021-01-26 15:55:44 UTC,"Snapd has for a while now supported gadget asset updates, so the grub.cfg for a gadget can be updated with a gadget snap refresh which would allow one to change the kernel command line used, so I'm marking this bug as Fix Released."
1664391,2017-10-27 03:08:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664392,2017-04-25 15:20:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1664394,2017-02-14 10:43:01 UTC,Please could you give more detail:
1664394,2017-02-15 11:18:50 UTC,"Hi, Jeremy."
1664394,2017-02-23 12:06:58 UTC,"evgniy:  I see you have assigned yourself to this bug - this means that you intend to fix it - is that correct?  If not, please unassign."
1664394,2017-02-18 10:24:51 UTC,Thank you for your appreciation of pantheon-files - it is encouraging.
1664394,2017-02-16 17:21:03 UTC,Hi Evgeniy.  Do you have pantheon-terminal installed on Ubuntu as well as pantheon-files?  It probably will not work with the default Ubuntu terminal.
1664394,2017-02-17 19:26:25 UTC,"It seems there is also a bug when running pantheon-terminal in Ubuntu where the window shrinks to minimum size unless maximized which is not ideal!  There was a fix for this but it introduced regressions in elementaryos so it was reverted.  I'll try to find time to look into it again.  Unfortunately pantheon-files explicitly calls pantheon-terminal for ""Open in Terminal"" at the moment."
1664394,2017-02-17 18:27:14 UTC,"You could try installing and using the elementary theme for gtk rather than the default Ubuntu theme, but I have not tried pantheon-terminal on Ubuntu I must admit.  Obviously the bulk of the limited development resources are focussed on elementaryos at the moment."
1664394,2017-02-16 20:27:48 UTC,Hi Jeremy and thank you!
1664394,2017-02-17 23:13:11 UTC,"I see. I hope what you will find resourses and time to make it better and
adopt it to ubuntu."
1664399,2017-02-14 16:45:16 UTC,Thank you for taking to report this bug and help make Ubuntu better.
1664399,2017-02-16 14:36:26 UTC,"Thanks for the link. I have done some basic testing and it's working all right. The author of the post you've linked to says that it is not enabled by default in Debian because the request to check for connectivity may be tracked and this may be a privacy concern. However, it's enabled by default in Fedora and may also be so in other (at least non-Debian) distributions. There is, of course, the point that GNOME Network Manager is also used in Ubuntu Unity and Xubuntu, and I don't know whether this would cause any difference there."
1664399,2017-02-16 15:58:15 UTC,"Putting it in its own package seems to be a good idea. That way, even other
Ubuntu(-based) distros could opt out of it by not having it installed by
default. It certainly should be enabled by default on Ubuntu GNOME though."
1664399,2017-02-22 13:51:05 UTC,"I tried putting the config snippet in place on a new installation of Ubuntu GNOME 16.10 BEFORE booting into the installation for the first time. I also upgraded it to GNOME 3.22 first (from the gnome3-staging PPA). Then, when I logged in for the first time and tried connecting to a captive portal network from the GNOME initial setup wizard, it showed a tick mark but the NM icon remained a question mark and the Internet was inaccessible from the system until I turned Wi-Fi off and then on. I experienced a similar problem even when installing the snippet on an existing installation (as well as on a fresh one), after the second reboot or so - the icon would remain a question mark and the system did not connect until I rebooted."
1664399,2017-02-22 14:49:37 UTC,"Saurav, Ubuntu 17.04 Beta is currently using systemd-resolved so the dns=dnsmasq line has been removed."
1664399,2017-02-22 14:51:36 UTC,"Sorry, that should have been /etc/NetworkManager/NetworkManager.conf."
1664399,2017-02-22 14:55:40 UTC,"The default response would only work as long as the page given in the uri (http://network-test.debian.org/nm), returns the default response, of course (""NetworkManager is online"", as given in the Network Manager specification)."
1664399,2017-02-22 16:12:39 UTC,"By the way, I think network-manager should be the correct affected project for this, or at least added to the list, and optionally the title can be changed to indicate the missing connectivity check. I have seen that the KDE Plasma Network Manager applet (or plasmoid) can also reflect the connectivity state, so the benefit is cross-desktop."
1664399,2017-02-22 21:29:50 UTC,"Saurav, thanks for the help. I tested this today and it worked pretty well (except I have been having trouble with systemd-resolved (LP: #1666021) )"
1664399,2017-02-16 15:45:09 UTC,Thanks for the feedback.
1664399,2017-03-18 17:46:46 UTC,"I would like to enable this, but I'm not sure it will be possible until 17.10."
1664399,2017-02-22 22:38:22 UTC,Thanks. I have marked bug #997200 as affecting me; confirmed for network-manager (Ubuntu).
1664406,2017-09-12 21:19:28 UTC,"When will this be available i.e. in Kubuntu?
It seems to work already with self build versions. See:
https://forum.ubuntuusers.de/post/8882429/"
1664406,2017-06-29 08:24:40 UTC,Will this be available for Xenial?
1664406,2017-02-22 18:05:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664406,2017-04-15 08:12:05 UTC,"the PIM event plugin is missing in 17.04 final. As this is an advertised feature of KDE, there sould be an update to kdepim-addons."
1664406,2017-02-22 18:14:24 UTC,Please fix this soon. Calendar widget showing events is extremely useful for work.
1664406,2017-04-29 21:27:39 UTC,"Will be coming soon in backports for 17.04, as just missed getting that into Zesty for release day."
1664407,2017-02-13 23:59:02 UTC,"Windows 10, Inkscape 0.92+devel 15517"
1664407,2017-02-14 08:56:26 UTC,"Upstream bug:
* 765858 – file chooser generates a warning about a network path
  https://bugzilla.gnome.org/show_bug.cgi?id=765858"
1664407,2017-02-14 08:59:20 UTC,"On Windows 10:
- not reproduced with Inkscape 0.92.1pre1 (GTK2, 64bit, 7z) from inkscape.org
- reproduced with inkscape_trunk_r15113 (GTK3, 64bit, 7z) from
  http://download.tuxfamily.org/inkscape/win64/"
1664407,2017-02-14 09:01:39 UTC,Clarification:
1664407,2017-10-12 19:29:36 UTC,Fixed in MSYS2 builds.
1664410,2017-02-14 00:29:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1664424,2017-06-20 18:01:33 UTC,errr...stupid mouse accidentally clicked incomplete.  Please disregard.
1664424,2019-09-19 12:02:35 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1664427,2018-04-26 13:29:41 UTC,Is this still an issue?
1664427,2017-03-13 15:48:19 UTC,thanks Stuart!
1664427,2017-03-10 07:28:47 UTC,"Yes, Bug #1669306. I can reproduce the failure, and the following snapcraft.yaml with an altered command: works fine:"
1664427,2017-03-10 07:14:19 UTC,This looks like a dupe of Bug #1669306 to me. If /snap/thefuck/current/command-thefuck.wrapper has no mention of python or python3 then it is.
1664427,2017-03-09 20:46:41 UTC,may I mention that this snap has no built python3 interpreter so the `classic` part might not be as portable as desired until major snapd/core work happens to support this.
1664427,2017-03-09 14:06:52 UTC,I can reproduce this:
1664427,2017-03-09 14:08:26 UTC,And it finally died with:
1664427,2017-02-28 22:45:37 UTC,"I can reproduce the denial, but if I add this rule to /etc/apparmor.d/usr.lib.snapd.snap-confine:"
1664427,2017-02-14 10:03:58 UTC,it surely is:
1664427,2017-02-14 02:46:52 UTC,"Hmm, not sure. I'll consult with the security team. Maybe remote access is a factor here."
1664427,2017-02-14 02:38:28 UTC,"Do you mean, in my machine? I don't think so, it's a xenial machine in canonistack created a few weeks ago."
1664427,2017-02-14 02:28:33 UTC,"This is snap-confine, not the snap getting the denial. Snap-confine itself should not need to access /dev/tty. Do you have something unusual in your setup that might explain this?"
1664427,2017-03-02 00:39:02 UTC,I've attached the snap to reproduce it.
1664427,2017-02-28 22:47:02 UTC,I should mention that I can reproduce the denial outside of ssh (and I see it in ssh). I also think the denial may just be noise....
1664428,2017-02-14 05:45:07 UTC,Diff of proposed change against lp:inkscape/0.92.x r15368 (for easier review).
1664435,2017-02-14 03:39:06 UTC,"I'm marking this as Medium because the logic doesn't work and therefore the timeout never triggers (thankfully). I think the error conditions need to be rethought in this path and what constitutes a viable timeout (or if one even makes sense). On many machines, if a restart is required for any reason during this code path then the reboot alone could take upwards of 10 minutes. If the upgrade path goes to Jewel from Hammer then upgrading the permissions on the OSDs in a production cluster is known to take longer (I've seen 40-60 minutes or more per OSD)."
1664435,2019-07-30 10:00:31 UTC,"I've just stumbled upon this bug, and have to add a slightly connected issue with this:"
1664435,2020-06-17 18:01:30 UTC,This is still happening.
1664435,2020-06-17 18:12:50 UTC,Actually I just resolved a workaround.
1664438,2020-02-12 08:30:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664445,2017-02-14 05:50:58 UTC,"I just noticed that I can also install thumbnailer without ubuntu-app-platform being installed first. There is no error, even though there is no way that thumbnailer will work that way."
1664451,2017-03-10 08:35:25 UTC,"I think that should not be a OSC issue, cinderclient have same behavior."
1664475,2020-01-22 13:10:19 UTC,The OVN driver now lives in the neutron repository. Moving this bug to their tracker.
1664475,2017-02-16 06:56:22 UTC,I agree that it would be nice to expose gateway router scheduling information through the Neutron API.
1664479,2017-02-18 17:48:04 UTC,"OP, please translate your report to English"
1664486,2017-02-14 10:22:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433568"
1664486,2017-05-11 02:20:30 UTC,"Change abandoned by feng.shengqin (<email address hidden>) on branch: master
Review: https://review.openstack.org/433568"
1664486,2017-08-01 08:43:49 UTC,Need more information
1664487,2017-03-23 08:08:05 UTC,"Reviewed:  https://review.openstack.org/448409
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=a5d30fb3af4c0af4be3c0bc055236fb6f8aee65a
Submitter: Jenkins
Branch:    stable/ocata"
1664487,2017-03-23 08:03:59 UTC,"Reviewed:  https://review.openstack.org/448408
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=a4b9403d9084389153e6640de8bc4072b92f7b1d
Submitter: Jenkins
Branch:    master"
1664487,2017-03-22 06:40:20 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/448409"
1664487,2017-03-15 07:01:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445776"
1664487,2017-02-15 16:22:17 UTC,New reproduce here https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.cic_maintenance_mode/181/testReport/(root)/negative_auto_cic_maintenance_mode/negative_auto_cic_maintenance_mode/
1664487,2017-03-22 06:40:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448408"
1664487,2017-03-16 13:55:02 UTC,"Reviewed:  https://review.openstack.org/445776
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=7d0f33365d6a2a915f3484c6dcfe3c40a55bdcff
Submitter: Jenkins
Branch:    stable/newton"
1664491,2017-04-26 06:49:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664493,2017-06-29 07:08:05 UTC,"Change abandoned by Helena (<email address hidden>) on branch: master
Review: https://review.openstack.org/474888
Reason: Duplicate change"
1664493,2017-07-27 20:51:51 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b3 development milestone.
1664493,2017-07-27 20:49:06 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.
1664493,2017-07-21 10:21:25 UTC,"Reviewed:  https://review.openstack.org/461748
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=fb003d66ceb46f35675f7e209b18272717841e4c
Submitter: Jenkins
Branch:    master"
1664493,2017-07-22 12:33:26 UTC,"Reviewed:  https://review.openstack.org/461745
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d4e7dfb3768c3438ea848d4e95a5b1b078d462f6
Submitter: Jenkins
Branch:    master"
1664493,2017-05-02 11:40:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461745"
1664493,2017-05-02 11:43:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461748"
1664493,2017-02-15 01:47:00 UTC,yes. sfc-agent is not implement. there is no config.json at all.
1664493,2017-06-29 07:07:40 UTC,"Change abandoned by Helena (<email address hidden>) on branch: master
Review: https://review.openstack.org/474887
Reason: Duplicate change"
1664493,2017-04-20 13:50:53 UTC,"SFC images are really useless, networking-sfc can be installed as neutron-server and neutron-openvswitch-agent plugins."
1664493,2017-03-04 04:06:43 UTC,seems sfc is not implemented at all.
1664501,2018-05-14 07:11:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664503,2017-02-14 10:36:07 UTC,"Related earlier report:
* Bug #921529 “Nodes have precedence over gradients in node tool”
  https://bugs.launchpad.net/inkscape/+bug/921529"
1664507,2017-02-14 10:31:30 UTC,"Oh yeah, the command was `nova --debug boot --flavor m1.small --image 0aa71b89-2d21-47d5-a52b-e28bc11614f2 --key-name laney --poll'"
1664507,2017-02-14 10:33:50 UTC,Subscribing the two of you for input. :)
1664507,2017-10-26 13:24:52 UTC,Apologies for the lag - reading:
1664507,2017-10-26 13:35:44 UTC,"Right, but can we maybe have a better error message then please?"
1664507,2017-10-26 13:51:45 UTC,Lets ask ;)
1664507,2019-09-10 07:47:30 UTC,"This bug has been open for about 2 years without any activity in python-novaclient.
I'm going to move it to ""Won't Fix"".
This bug can be reopened (set back to ""New"") if someone decides to work on this."
1664508,2017-02-17 17:01:11 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1664515,2017-07-17 12:04:04 UTC,This issue was fixed in the openstack/requirements 1.1.0 release.
1664520,2017-02-16 09:16:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664527,2017-02-14 11:49:31 UTC,oxide::qt::WebView::CreateContextMenu(…) is being called with 3 menu items and oxide::qt::MenuItemBuilder::Build(items) returns a std::vector of size 3.
1664527,2017-02-14 12:01:06 UTC,"Note that I am seeing the same issue in the branch where I'm implementing autofill suggestions, and replacing std::vector<Suggestion> with QVector<Suggestion> ""fixes"" the problem, although I’d rather understand what's going on and address it of course."
1664530,2017-02-14 23:15:53 UTC,"@ev, please report a separate bug for the 2fa."
1664530,2017-02-16 17:19:09 UTC,"@Leo, filed as https://bugs.launchpad.net/software-center-agent/+bug/1665411"
1664535,2017-02-14 12:49:10 UTC,"Hi again,"
1664535,2017-02-14 16:43:29 UTC,"Hello,"
1664535,2017-02-15 06:06:32 UTC,Thanks!
1664535,2017-02-14 22:30:51 UTC,17:18 <jbayfield> rbasak: Bug does not occur in Zesty/Yakkety.
1664540,2017-02-14 12:31:01 UTC,This change was made by a bot.
1664540,2017-02-17 14:39:45 UTC,kernel-fixed-upstream
1664540,2017-02-14 19:53:55 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1664540,2017-02-16 11:36:55 UTC,"Hello,"
1664542,2017-02-24 14:04:07 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1664542,2017-04-26 04:17:43 UTC,[Expired for gnome-boxes (Ubuntu) because there has been no activity for 60 days.]
1664550,2017-02-16 17:37:28 UTC,"I have the same symptoms and I have the Loki build also. AppCenter worked OK until I installed Synaptic Package Manager, I think."
1664550,2017-02-16 17:51:57 UTC,Ahhh.... I have that installed too. Maybe that's the problem. 🤔
1664550,2017-02-17 18:50:14 UTC,"I removed synaptic, did a restart and tried software center again and still have the same problems."
1664550,2017-02-18 17:53:41 UTC,Can anyone confirm this issue can be reproduced from a system that has not had Synaptic? The solution here might be to just make AppCenter conflict with Synaptic in packaging. Synaptic might be making some changes to the system.
1664550,2017-02-25 13:38:46 UTC,"I've had both AppCenter and Synaptic on my Loki build for a long time, they both work perfectly fine. They don't work both at the same time since only one application can have the lock on the package database, but it certainly hasn't broken AppCenter."
1664550,2017-02-25 13:54:38 UTC,Yea I don't think synaptic has anything to do with it. Loki software center has never worked for me. Very annoying.
1664554,2017-02-14 16:32:52 UTC,"More specifically bug #1655619 (which might be related to bug #1659172, though)"
1664554,2017-02-16 07:04:37 UTC,i installed inkskape with Dutch language....
1664554,2018-03-24 16:56:07 UTC,"New install of:
Windows 10 Home
Version 1709
OS build 16299.125"
1664554,2017-07-27 11:06:30 UTC,"reproduced on Windows 10, Inkscape 0.92.2pre0 (973e216, 2017-07-25)
 using the install file inkscape-0.92.2pre0-x86.exe"
1664554,2018-03-24 16:51:24 UTC,"I have the same error in the new 0.92.3 release. I cannot save a Jessyink zip pdf or png file, in Windows 10 in my notebook. I have Debian Stretch in a desktop computer, and I have no problems. So the bug is only in Windows.
I tried to add the command inkex.localize(), as wrote by Alvin Penner and the error changes in ""could not find Inkscape command"""
1664554,2017-02-14 15:03:40 UTC,"Attaching possible minimal fix for both issues. The hard-coded absolute paths which are checked should be removed, but that might affect other jessyInk modules as well, and should be done separately."
1664554,2017-07-08 12:33:28 UTC,Deleting the attached diff - I am revoking my pending patches provided in this bug tracker for issues with python-based extensions distributed with Inkscape.
1664554,2017-02-14 13:59:08 UTC,"Two issues:
1) localize() has not yet been run when the effect class is initialized
This also can be reproduced if the export script is modified e.g. to prompt that the inkscape executable was found (on Ubuntu, or OS X).
2) Apparently, with Inkscape >= 0.92 on Windows, the check for the inkscape binary in findInkscapeCommand() fails always (returns None). This ought to be fixed to support executing inkscape as external process like in other extensions (restack.py for example)."
1664554,2017-02-14 13:17:31 UTC,"Not reproduced with Inkscape 0.92.0 r15299, 0.92.1 r15371, 0.92+devel r15519 on Ubuntu 14.04.5 LTS."
1664554,2017-02-14 13:35:10 UTC,"On Windows 10:
- reproduced with Inkscape 0.92.0 r15299 (32bit, 7z)"
1664554,2017-02-14 13:31:56 UTC,"On Windows 10:
- not reproduced with Inkscape 0.91 r13725 (64bit, 7z)
- reproduced with Inkscape 0.92.0 r15299 (64bit, 7z)
- reproduced with Inkscape 0.92.1pre1 r15355 (64bit, 7z)"
1664554,2017-02-14 13:18:14 UTC,"Sorry previous version was 0,91 must have a brain fart..."
1664554,2018-03-25 11:52:46 UTC,attached is a slightly edited version of jessyink_export.py which works for me on Windows 10
1664554,2017-02-14 13:16:38 UTC,"I use windows 7
previous version is 0,92"
1664554,2017-02-14 13:07:11 UTC,"Not reproduced with Inkscape 0.48.5 r10040, 0.91 r13725, 0.92.0 r15299, 0.92.1 r15371 on OS X 10.7.5."
1664554,2017-02-14 12:55:26 UTC,"confirmed on Windows 10, Inkscape 0.92.0 r15299"
1664554,2017-02-14 12:52:11 UTC,"Please add information about OS/platform and Inkscape version to the bug description, thank you."
1664554,2017-02-14 13:41:05 UTC,"Seems that the export script needs to fix the detection of the inkscape executable (without relying on absolute paths on any platform, this is not necessary)."
1664554,2017-02-14 13:16:55 UTC,"in my case, on Windows, I had to add the command inkex.localize()
as in the attached file"
1664554,2020-02-03 17:45:41 UTC,"I have installed Inkscape 0.92.4 (5da689c313, 2019-01-14) on Windows10 and get the same mesage when trying to save a JessyInk pdf/png zip"
1664558,2017-02-14 13:00:13 UTC,"I think there's already a bug for this, but I can't find it."
1664558,2019-09-19 11:52:49 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1664560,2019-08-29 12:23:27 UTC,"It seems https://manpages.ubuntu.com supports HTTPS now, but it is still not defaulting to HTTPS though."
1664568,2017-02-16 13:57:07 UTC,"Reviewed:  https://review.openstack.org/433649
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=81c403a6073a144300da5c931010e794af22fd9e
Submitter: Jenkins
Branch:    master"
1664568,2017-02-22 15:01:29 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/436965"
1664568,2017-02-25 22:29:43 UTC,"Reviewed:  https://review.openstack.org/436965
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=51eb51eab412dd27281c177bc62a8b6ce4fb3029
Submitter: Jenkins
Branch:    stable/ocata"
1664568,2017-03-06 19:27:18 UTC,This issue was fixed in the openstack/python-tripleoclient 6.1.0 release.
1664568,2017-04-11 08:37:13 UTC,This issue was fixed in the openstack/python-tripleoclient 7.0.0 release.
1664568,2017-02-14 13:37:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433649"
1664575,2017-02-17 15:27:37 UTC,"Using the HMC to change OpenStack managed partitions is an forbidden by-passing IMO. That's equivalent of using ""virsh edit"" on a KVM host to change KVM guest information."
1664575,2017-02-21 15:16:06 UTC,Doesn't block the release. No opinion on possible backports yet.
1664575,2017-02-28 06:31:28 UTC,"Can we add one column in 'instances' table?
i.e. 'partition_uuid'"
1664575,2017-03-02 05:53:59 UTC,That is basically 'instance.device_metadata'. And it will be very easy to use.
1664575,2017-03-02 08:49:36 UTC,"I see - the instance_name is generated along the ""instance_name_template"" config option, where the id is a counter that gets increased by nova -> the name instance000001 is generated by nova and not by virsh)"
1664575,2017-03-02 11:45:47 UTC,According to Preethi we can not modify 'object-id'. Otherwise we would have done it earlier.
1664575,2017-03-02 12:48:35 UTC,My point is if we should Request that feature from the DPM team...
1664575,2017-03-02 16:21:51 UTC,"There is a table 'instance_metadata' in 'nova' database. I think this is the table which is made for such purpose.
https://wiki.openstack.org/wiki/Trove-Instance-Metadata"
1664575,2017-03-03 13:35:04 UTC,Setting to medium along our discussion in the meeting...
1664575,2017-03-02 05:45:01 UTC,"I checked ""OS-EXT-SRV-ATTR:instance_name"" attribute is not storing into the database. It's something like creating at run time probably using id of instance.
1. https://ask.openstack.org/en/question/26295/how-does-nova-maps-the-display-name-of-vm-or-instance-in-openstack-to-instance-name-in-kvmesx-etc/
2. https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/extended_server_attributes.py#L49"
1664575,2017-02-28 07:41:37 UTC,Changing the nova table is not an option I guess. Nova takes care about them including upgrades and so on. Having a new column there might break upgrades for nova on systems where our code is installed.
1664579,2017-02-15 15:47:35 UTC,I did send this in as private but if its been changed to public as long as i can get an answer to what might be causing the repeated issue I would be greatful either way at this point ...
1664579,2017-02-15 02:30:07 UTC,This change was made by a bot.
1664580,2017-02-14 14:18:59 UTC,Example application
1664583,2017-02-24 09:59:54 UTC,fixing this with https://review.openstack.org/#/c/426706/
1664585,2017-02-14 14:48:58 UTC,"I agree that it's a wishlist item and have marked it as such. The use case makes sense to me, but I wonder if we will need to add some switches.  It makes sense to say that since transcendent bibs belong to no particular location, a search that filters on specific locations should exclude them. However, I could also imagine—possibly incorrectly—a view that transcendent bibs belong to *all* locations."
1664585,2017-02-15 14:59:41 UTC,"Just to provide some background, traditionally transcendent bibs show up in all searches that don't include copy-specific filters, such as status.  With regard to copy locations, the thinking is that those are a subset of an org unit and carry the same (lack of) restrictions for transcendent bibs.  We can certainly redefine that, though."
1664596,2017-03-24 20:39:35 UTC,"Bug is related, and probably caused by gedit."
1664597,2017-04-24 17:03:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664604,2017-05-08 14:59:53 UTC,It was reproduced on Fuel 9.2 StacLight 1.0
1664607,2017-02-14 17:40:37 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/433816"
1664607,2017-02-14 17:39:53 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/433815"
1664607,2017-04-14 09:23:55 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1664607,2017-02-28 16:00:01 UTC,This issue was fixed in the openstack/nova 13.1.3 release.
1664607,2017-02-27 20:28:50 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1664607,2017-02-14 15:26:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/433707"
1664607,2017-02-17 16:02:08 UTC,"Reviewed:  https://review.openstack.org/433825
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb1b9f224d6f05674667a7ddf7c8ba77f4f257aa
Submitter: Jenkins
Branch:    stable/mitaka"
1664607,2017-02-15 01:47:58 UTC,"Reviewed:  https://review.openstack.org/433707
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d12535839817c4385986ccaffe52b5903d3088ca
Submitter: Jenkins
Branch:    master"
1664607,2017-02-15 00:43:51 UTC,"Reviewed:  https://review.openstack.org/433816
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=db075faf2a767cf3f62768e85a79c3cff200d3cb
Submitter: Jenkins
Branch:    stable/newton"
1664607,2017-02-15 00:21:28 UTC,"Reviewed:  https://review.openstack.org/433815
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=18fb0a17298dce2b361cc47f16d0d1500484f0d1
Submitter: Jenkins
Branch:    stable/ocata"
1664607,2017-02-14 20:45:58 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22TestStampPattern%5C%22%20AND%20message%3A%5C%22SecurityGroupNotFoundForProject%5C%22%20AND%20tags%3A%5C%22screen-n-cell-child.txt%5C%22&from=7d
1664607,2017-02-14 17:49:37 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/433825"
1664607,2017-02-17 04:57:58 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc2 release candidate.
1664610,2017-07-10 19:53:54 UTC,This bug was fixed in the package mir - 0.27.0+17.10.20170630-0ubuntu1
1664610,2017-02-22 11:05:20 UTC,"Don't think so, Alt+Up/Alt+Down don't have text attached."
1664610,2017-02-17 06:57:55 UTC,"Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 1.0.0"
1664610,2017-02-16 10:53:44 UTC,Went for the second approach key entry text is attached to every press and repeat event.
1664610,2017-02-22 10:42:19 UTC,Alt+Up and Alt+Down to switch between tabs in Kate also doesn't work currently. Could it have the same cause as this Ctrl+C issue?
1664610,2017-02-15 12:56:18 UTC,Mir either has to expose the xkb_state (which we currently do not - and might be only on the server) or provide the keysym text directly with the event.
1664611,2017-02-14 15:38:29 UTC,"I just noticed that 'juju switch' (without arguments) shows this same problem, from the help description: ""Selects or **identifies** the current controller and model"" (emphasis mine), so it would be expected that it prints the controller:model that juju commands will use in the absence of ""-m MODEL"""
1664611,2017-02-14 23:50:41 UTC,"@Felipe,"
1664611,2017-02-15 01:01:44 UTC,"On Tue, Feb 14, 2017 at 11:50:41PM -0000, Anastasia wrote:

> @Felipe,
>
> Could you please clarify what Juju version you are using?
"
1664611,2017-02-15 01:57:22 UTC,"Thanks, Felipe!"
1664611,2017-02-15 02:38:37 UTC,"The fix for this is a little bit complicated, since there's interaction between $JUJU_MODEL, the current-controller value in the controllers.yaml file, and the -c flag."
1664611,2017-02-15 02:54:25 UTC,Removing 2.1 milestone as we will not be addressing this issue in 2.1.
1664617,2017-02-15 08:50:38 UTC,"Following commands will also be acceptes by openstack
openstack quota set --fl 10 Project01
openstack quota set --flo 10 Project01
openstack quota set --floa 10 Project01
openstack quota set --float 10 Project 01
openstack quota set --floati 10 Project 01
openstack quota set --floatin 10 Project 01
openstack quota set --floating 10 Project 01
openstack quota set --floating- 10 Project 01
openstack quota set --floating-i 10 Project 01
openstack quota set --floating-ip 10 Project 01
openstack quota set --floating-ips 10 Project 01"
1664617,2017-04-28 22:00:39 UTC,Is this using nova-network or neutron?
1664617,2017-05-05 08:08:34 UTC,Neutron
1664617,2017-07-21 13:24:02 UTC,"Yep I get this too, other openstack quota set commands work find - but all variants of the openstack quota set command in comment #1 have no effect on the quota for floating ips - no error is returned so the command looks like it executed - but it didn't - I will now return the same courtesy and not bother looking into log files"
1664620,2017-02-14 16:01:57 UTC,"From a quick look at the latest UITK landing, it looks like https://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1000.1100.3 could have introduced that regression."
1664620,2017-02-15 11:40:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664620,2017-03-09 14:03:43 UTC,This bug was fixed in the package ubuntu-ui-toolkit - 1.3.2184+17.04.20170306
1664623,2017-02-14 16:14:00 UTC,"also to elaborate: of the two guis allows change and works, the other one doesn't allow the 1st user to change their own password, but does for other users"
1664632,2017-03-13 18:00:28 UTC,"I just discovered that ""Edit->Clone->Clone original path (LPE)"" can be used to create a filled shape for many paths at once without copying and pasting them separately. Nice feature =)"
1664632,2017-02-21 14:21:28 UTC,This improvemets are in r.15537
1664632,2017-02-21 14:20:50 UTC,"I just commit some improvements to the 0.93 branch (Couldent be backported to 0.92.x). This allow:
Optionaly Separated paths
Optionaly Closed
Optionaly Transforms"
1664632,2017-02-21 09:56:22 UTC,"Realy the tree shapes are independent, you need to:
A: Create a new path and apply fill between strokes LPE
B: copy each previous path and select the fill between strokes Path and add (+ icon) the copied path to it
Limitations:
Separated paths are joined by straight line
Generated path always closed
I can fix for 0.93 the LPE to allow not joined paths and optional close and also a optional transform to allow move result instead move original paths."
1664632,2017-02-20 02:53:35 UTC,"I think I found a workaround to this. Actually, never mind. There's a workaround I just found."
1664632,2017-02-20 21:36:52 UTC,"Fixed path parameter to use LPE shapes. trunk r.15536 and 0.92.x in r.15381. Here are a pic with fill-between-many LPE to archive the effect:
https://inkscape.org/en/~jabiertxof/%E2%98%85fix-bug-1664632"
1664632,2017-02-20 02:47:42 UTC,"**""I think there should be a way to generate a path generated via region selection.""**"
1664632,2017-02-20 02:44:59 UTC,"I think I have a better idea. I think there should be a path generated via region selection. Like, for example, when you make multiple splines or multiple objects with multiple LPEs, you should be able to select shapes within the splines, and then you can generate a result. That result can always be modified by editing splines or objects."
1664632,2017-02-21 03:32:26 UTC,"^^That's definitely what I want to see, nice to see this happening. Does the nodes have to be touching? I mean, as long as there's a closed shape, there'll be a fill, right?"
1664635,2017-02-28 15:26:52 UTC,"Reviewed:  https://review.openstack.org/438914
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=cb4a6873534c8103a43d17209e19b475809d55e4
Submitter: Jenkins
Branch:    stable/ocata"
1664635,2017-02-23 13:21:34 UTC,We found that the reason of puppet being stuck is hanging of sshd while reading output from update-master-node.sh script. There are some logs:
1664635,2017-02-23 15:34:54 UTC,"Change abandoned by Mykyta Karpin (<email address hidden>) on branch: master
Review: https://review.openstack.org/436982
Reason: in favor of https://review.openstack.org/#/c/437373/"
1664635,2017-03-08 12:20:18 UTC,This issue was fixed in the openstack/fuel-qa 11.0.0.0rc2 release candidate.
1664635,2017-02-23 13:29:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437373"
1664635,2017-02-28 15:25:51 UTC,"Reviewed:  https://review.openstack.org/438915
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=b431c985530508ec590d618e4381d5d8dd886dbf
Submitter: Jenkins
Branch:    stable/newton"
1664635,2017-02-28 11:01:22 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/438914"
1664635,2017-02-23 15:39:14 UTC,"Reviewed:  https://review.openstack.org/437373
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=ee0bf1cfa424aca4c2eb65a5d8506661b8e3346a
Submitter: Jenkins
Branch:    master"
1664635,2017-02-22 15:28:36 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/436982"
1664635,2017-02-17 13:20:29 UTC,"trying to strace puppet run, it hangs on"
1664635,2017-02-22 13:55:08 UTC,"the problem is not in manifests or puppet or keystone, it is some magic between fuel-devops/qa + bash + puppet output, because when I redirected puppet logging to syslog, update-master-node.sh didn't get stuck - https://custom-ci.infra.mirantis.net/view/11.0/job/11.0.custom.system_test/128/console"
1664635,2017-02-28 11:02:12 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/438915"
1664636,2017-02-14 16:43:20 UTC,QML file to test
1664636,2017-02-14 16:43:40 UTC,PNG file used by the test
1664636,2017-02-14 16:45:11 UTC,"strace output, see there's multiple blocks of"
1664636,2017-02-16 09:09:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664651,2017-04-17 23:23:39 UTC,"I think there are actually two separate bugs, one regarding name registration (see also my duplicate bug) and another regarding permissions for a name."
1664651,2017-02-15 01:43:28 UTC,So the preflight/dry-run check does ensure that the name of your upload is already registered (the original description was with an older snapcraft before the functionality was added).
1664651,2017-02-14 20:59:24 UTC,"so, not a regression, it just never worked, that's better :)"
1664651,2017-02-14 20:43:31 UTC,"Curiously, I'm seeing the following:"
1664651,2017-02-14 20:17:37 UTC,I've just confirmed it using the latest snapcraft:
1664651,2017-02-14 19:02:19 UTC,"I just did a debug session with snapcraft. on sending dry_run, the store just sends back this in the response object:"
1664651,2017-02-14 18:22:16 UTC,@Ev: that fix was released in 2.25. Can you please update snapcraft and try again?
1664651,2017-02-14 20:55:29 UTC,"Right, so the point of confusion is that the pre-flight check on the store currently on considers snap name registration, not ownership."
1664672,2019-05-17 13:37:25 UTC,This is included in cs:haproxy-49
1664703,2017-02-16 09:23:12 UTC,#3797 - fixed issue with cylinder cock steam effects not displaying
1664704,2017-02-14 21:13:34 UTC,Confirmed.
1664716,2017-02-16 20:41:46 UTC,This message is coming directly from the store.
1664723,2017-02-14 21:34:27 UTC,Attaching plain text version
1664723,2017-02-14 21:38:30 UTC,^disregard text version above. Attached here is the correctly formatted plain text version.
1664723,2017-02-14 22:17:31 UTC,"As far as I know, DEBUG level is the only level this occurs at. The datastores that are related to the logging reported are experimental as well."
1664723,2017-02-14 21:56:39 UTC,The examples only show this happening at DEBUG log level. Does it happen at any non-DEBUG levels as well? Otherwise this is a class B3 report (A vulnerability in experimental or debugging features not intended for production use) and so would not warrant an advisory nor embargo: https://security.openstack.org/vmt-process.html#incident-report-taxonomy
1664723,2017-03-20 14:53:05 UTC,"A little longer than I intended to wait for feedback, but it's been over a month with no objections so I'm triaging as a security hardening opportunity now."
1664723,2017-03-20 14:53:39 UTC,"Agreed on class B3, switching this to public."
1664723,2017-04-06 14:09:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454204"
1664723,2017-10-05 19:51:33 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/454205"
1664723,2017-02-14 23:22:23 UTC,"Thanks, Trevor!"
1664728,2017-03-06 21:14:45 UTC,"maybe as a first step somebody could provide guidance on how I can flesh out this bug report. e.g. right now I cannot suspend my laptop, is there some log I can post here to help narrow down the issue?"
1664728,2017-04-08 19:11:00 UTC,"I noticed that if I close the lid, wait for it to suspend, and then remove the usb ethernet adpater, all is fine.
But if I close the lid and remove the adapted immediately it will auto resume. And if I remove the adapter first and then close the lid, as well.
Does this mean that there is an issue with the driver for that USB adpater? Or network manager? Or NFS (all sorts of weird issues with NFS..)"
1664730,2017-02-15 10:16:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664743,2017-03-27 14:08:55 UTC,moved to tripleo launchpad with quickstart tag
1664743,2019-02-12 13:11:26 UTC,Is anybody planning on working on this? or is this still needed?
1664743,2017-02-16 22:24:27 UTC,We have the following in the tripleo-quickstart-extras repo for a virtual undercloud and baremetal overcloud:
1664745,2017-04-05 12:38:45 UTC,"It can be related like ""nrpe:general-info heat:juju-info"".
But this isn't consistent with other charms provided by openstack-charmers."
1664745,2020-11-13 14:40:00 UTC,Updated PR at https://review.opendev.org/#/c/619219/
1664745,2018-08-10 10:16:52 UTC,"Fix proposed to branch: stable/18.05
Review: https://review.openstack.org/590736"
1664745,2017-09-28 21:06:54 UTC,"Change abandoned by Xav Paice (<email address hidden>) on branch: master
Review: https://review.openstack.org/505052"
1664745,2018-11-21 12:03:14 UTC,"Change abandoned by Alvaro Uría (<email address hidden>) on branch: stable/18.05
Review: https://review.openstack.org/590736
Reason: see https://review.openstack.org/#/c/619219/ for a new version"
1664754,2020-01-28 14:04:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/704572"
1664754,2020-01-28 14:22:28 UTC,"Reviewed:  https://review.opendev.org/704572
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=9f5c39cdcf79a435ded68e57ea6444e86359fc31
Submitter: Zuul
Branch:    master"
1664754,2020-02-18 11:04:17 UTC,This issue was fixed in the openstack/puppet-neutron 16.1.0 release.
1664756,2019-05-28 15:51:23 UTC,This is available in cs:haproxy-50
1664766,2017-04-25 15:06:33 UTC,"The reports are not new and there were only 16 reported since the LTS, setting as low it seems a very uncommon issue"
1664773,2019-09-28 14:08:18 UTC,Xenial is end of life and used GTK2. MATE Menu has long since been ported to GTK3.
1664779,2017-02-15 11:37:21 UTC,"This is a builddeb issue, redirecting.
Short term: disable the plugin."
1664780,2017-02-15 11:27:27 UTC,http://stackoverflow.com/questions/42184792/pip-does-not-work-after-upgrade-to-ubuntu-16-10/42248012#42248012
1664782,2017-05-24 10:20:25 UTC,"Change abandoned by Neil Jerram (<email address hidden>) on branch: master
Review: https://review.openstack.org/428764"
1664782,2017-02-15 01:36:22 UTC,"Hey Armando - I should record that there is already some discussion of this between Kevin and me in https://review.openstack.org/#/c/428764/.  (Unfortunately I did things the wrong way round: patch first, and this bug later.  But from now on that will hopefully be rectified.)"
1664782,2017-02-15 01:20:22 UTC,"That aside, without a level of coordination, it's only natural to expect the neutron agent to wipe unrecognized rules"
1664782,2017-02-15 01:19:05 UTC,If I recall correctly this behavior is considered buggy by neutron. Better to check with Kevin before diving in a fix campaign.
1664782,2017-02-15 02:05:44 UTC,Excellent! I appreciate the feedback.
1664784,2017-02-15 18:54:40 UTC,They were installed with deb packages ? I got both without problems.
1664784,2017-08-12 14:48:13 UTC,"Estou com mesmo problema. Ja fiz instalacao via gdebi e dpkg nos pacotes debs.
tambem tentei via apt-get install.
Fiz variações possiveis e um remove o outro mesmo."
1664784,2017-02-15 20:25:19 UTC,Hey there.
1664788,2017-02-15 20:49:08 UTC,"Change abandoned by Jim Baker (<email address hidden>) on branch: master
Review: https://review.openstack.org/434068
Reason: In favor of https://review.openstack.org/#/c/429040/ , which is more comprehensive in its support of the recent support for pagination."
1664789,2017-03-27 10:20:36 UTC,Marked as implemented by https://review.openstack.org/#/c/449157/
1664792,2017-03-07 19:38:58 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/442753"
1664792,2017-03-07 18:12:27 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/442654"
1664792,2017-03-07 18:10:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442652"
1664792,2017-03-01 02:15:25 UTC,"Reviewed:  https://review.openstack.org/434112
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=1c32b85d54a07ce12cdf9b1703fb3e41657a683d
Submitter: Jenkins
Branch:    master"
1664792,2017-02-15 07:33:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/434112"
1664792,2017-02-15 01:35:16 UTC,"While this is not a security vulnerability, masking sensitive data in log is a good to have security hardening measure."
1664792,2017-04-07 05:54:47 UTC,"Reviewed:  https://review.openstack.org/442654
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=3a08c6d2e2ca9d57bf3016b509ab1f18a78b6dd9
Submitter: Jenkins
Branch:    stable/newton"
1664792,2017-04-14 01:16:02 UTC,"Reviewed:  https://review.openstack.org/442753
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=63b812365ba7a3c8979e279fe3a8b5a766a34e19
Submitter: Jenkins
Branch:    stable/mitaka"
1664792,2017-03-22 02:48:33 UTC,"Reviewed:  https://review.openstack.org/442652
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=ae4fff5fa6ef1b6a51d2e45115dc24eff91ff458
Submitter: Jenkins
Branch:    stable/ocata"
1664793,2017-02-23 13:48:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/437379"
1664793,2017-02-23 14:41:08 UTC,"Change abandoned by Masayuki Igawa (<email address hidden>) on branch: master
Review: https://review.openstack.org/437379
Reason: oops, thanks"
1664793,2019-10-07 14:24:12 UTC,This issue was fixed in the openstack/tempest 22.0.0 release.
1664793,2017-04-11 19:52:34 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/218355"
1664793,2017-03-23 05:17:14 UTC,Related fix https://review.openstack.org/#/c/437216/ to skip this bug until it is fixed.
1664793,2017-02-21 10:23:16 UTC,FYI: Setting volume_device_name explicitly yielded no improvement in my tests with Quobyte.
1664793,2017-02-20 15:55:16 UTC,"IBM PowerKVM CI was affected, with the same signature. We found that it was due to wrong attach device name. After correcting the name, the test no longer times out. In our case we had to set it explicitly to sdb. In tempest.conf:"
1664793,2017-02-20 14:52:10 UTC,"intel-nfv-ci affected as well
e.g. http://intel-openstack-ci-logs.ovh/2017-02-20/433476/2/check/tempest-dsvm-full-nfv-xenial/aee7c58/testr_results.html.gz"
1664793,2019-07-31 12:55:47 UTC,"Reviewed:  https://review.opendev.org/615434
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=ba18426fd990fad19f429e0aa1673f549f2c77e8
Submitter: Zuul
Branch:    master"
1664793,2017-02-17 07:53:02 UTC,"Note: As Matthew pointed out in the duplicate bug #1665053, this seems to be a long going issue."
1664793,2017-02-15 02:05:20 UTC,We can probably pull some debug code out of this older patch I had:
1664793,2017-02-17 08:41:45 UTC,Further note: found this issue in more third party CIs (Tintri): http://openstack-ci.tintri.com/tintri/refs-changes-60-434660-2/
1664793,2017-02-15 08:08:07 UTC,FYI: This issue also hits Quobyte CIs (e.g. http://78.46.57.153:8081/refs-changes-07-433707-1/console.log.out)
1664793,2017-02-23 07:38:30 UTC,"FYI - hint with explicit setting of volume_device_name didn't work for us on intel-nfv-ci. According to my observation volume is in state ""attaching"", then it went into ""in use"" and then it disappears. I didn't find any error/warning in cinder logs, which might be related to that."
1664793,2017-02-15 19:16:56 UTC,This isn't just in ceph jobs.
1664793,2017-02-15 22:48:43 UTC,This might help: https://review.openstack.org/#/c/218355/
1664793,2017-02-15 22:45:19 UTC,I also wonder if we could be hitting something related to bug 1633236 where the detach fails.
1664804,2017-11-03 16:36:21 UTC,Syncing task from Mir.
1664811,2017-02-20 16:36:55 UTC,"@Feng,"
1664811,2017-09-08 23:01:10 UTC,There is no activity for fixing this bug for a while. I am going to remove assignee so that other contributors can take it.
1664814,2020-03-24 21:01:42 UTC,"Regarding to current status of neutron-fwaas project and that there is (almost) no upstream fwaas team anymore, I'm marking this as won't fix for now as probably nobody will step in to work on it."
1664814,2019-05-21 14:08:13 UTC,"Change abandoned by Reedip (<email address hidden>) on branch: master
Review: https://review.opendev.org/491704
Reason: Not able to work on it currently, open to others to continue"
1664814,2017-11-04 22:40:09 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/491704
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1664814,2017-11-04 22:39:55 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1664814,2017-08-08 07:44:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491704"
1664814,2018-05-11 13:55:11 UTC,We should have someone from the FWaaS team weigh in.
1664817,2017-02-15 06:44:43 UTC,Roger that
1664817,2017-02-15 09:58:48 UTC,i fix this in review https://review.openstack.org/434146
1664817,2017-02-15 04:08:34 UTC,The bug exists in stable/newton but as it's trivial it might not be accepted.
1664818,2018-08-09 00:29:10 UTC,"I too have special action rely on these commands, mainly inserting/removing iptables rule and/or creating virtual sub-interfaces. While this most likely able to be achieved by systemd, but learning systemd itself requires time. It will be wise for netplan to incorporate these functionality generate the appropriate drop-in snippets, otherwise I will have to fallback to ifupdown instead."
1664818,2017-05-23 22:32:09 UTC,I'm trying to understand the example you've given here.  Are you saying that you want a post-up script on one interface that monitors *another* interface to watch for the link to be up?  Or that you're wanting to use it to monitor the *present* interface for it to be up?
1664818,2017-05-25 10:55:28 UTC,"Fair point. I feel that asking/requiring that everything that users want to do be supported in networkd is a high bar, and might not provide the level of flexibility that users expect from Ubuntu."
1664818,2017-05-25 19:51:11 UTC,"> The requirement here is, I need to know when ens1 goes up or down, so
> that I can make changes to the bridge interface. The `ifmonitor` script
> will monitor the link status of ens1, and then take appropriate actions,
> such as restarting a DHCP client, adding or removing routes that have
> been programmed via the lan0 bridge to egress on ens1, adding or
> removing IP addresses from the configuration, etc.
"
1664818,2017-05-26 10:44:35 UTC,"I'm kind of concerned about any non-declarative functionality here. For example, DHCP client and receiving/updating routes are all handled by netwokrd already."
1664818,2017-10-27 19:09:44 UTC,"You mention that all the examples can already be done by netplan, yet one, he mentioned was modifying iptables, something I use myself, and have yet to find that anywhere in netplan."
1664818,2018-07-01 08:35:11 UTC,"I need to add routing information to one interface to allow ssh that enters via the non-default gateway. Before metalanguage this was easy. Now it's so difficult! The closest advice was networkd-dispatcher but the advised directory doesn't exist. I can't see why ""legacy"" functionality is jettisoned in such a cavalier fashion"
1664818,2020-12-11 15:17:36 UTC,marking this as invalid for systemd as arbitrary code can be run using networkd-dispatcher and/or suggestions from comment 4.
1664818,2020-12-11 21:00:53 UTC,"To my knowledge, networkd-dispatcher has no way to do 'pre' hooks on systemd-networkd events, so this is still a valid feature request."
1664828,2017-02-15 05:29:24 UTC,Maybe related:
1664828,2017-02-15 05:52:25 UTC,"We do implement this in QtMir, which might also be related:"
1664828,2017-02-15 06:01:24 UTC,Spinning the QSGRenderThread at this frequency could easily explain bug 1664160 too...
1664838,2017-02-15 06:09:38 UTC,"StacktraceTop:
 _dbus_header_cache_check (field=field@entry=5, header=0x7f6043d0b798) at ../../dbus/dbus-marshal-header.c:249
 _dbus_header_get_field_basic (header=0x7f6043d0b798, field=field@entry=5, type=type@entry=117, value=value@entry=0x7ffdb228c53c) at ../../dbus/dbus-marshal-header.c:1363
 dbus_message_get_reply_serial (message=<optimized out>) at ../../dbus/dbus-message.c:1092
 _dbus_connection_peek_for_reply_unlocked (client_serial=1, connection=0x7f603c0b1730) at ../../dbus/dbus-connection.c:2230
 _dbus_connection_do_iteration_unlocked (connection=connection@entry=0x7f603c0b1730, pending=pending@entry=0x7f603c0b1e00, flags=flags@entry=6, timeout_milliseconds=timeout_milliseconds@entry=-1985790869) at ../../dbus/dbus-connection.c:1227"
1664844,2017-10-12 01:39:07 UTC,"I'll let him comment, but I don't think it is. 'optional' doesn't mean ""please know about this config but also don't bring up the interface""."
1664844,2017-02-15 15:21:35 UTC,"IIUC, we're looking for an equivalent of 'manual' control?"
1664844,2017-11-23 08:54:06 UTC,Can we get the description follow https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ? Thank you!
1664844,2017-11-23 16:10:29 UTC,"Hello Mike, or anyone else affected,"
1664844,2017-11-23 17:00:13 UTC,"Hello Mike, or anyone else affected,"
1664844,2017-11-28 21:16:23 UTC,"nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the code skipping the test_routes_v6 test in the NetworkManager case. Therefore, it can't possibly pass SRU verification."
1664844,2017-10-11 20:14:11 UTC,"I think we're conflating two different issues here; marking a device as ""optional"" and not required for boot is different than specifying configuration for it, but expecting a backend to leave the interface down."
1664844,2017-05-26 10:53:33 UTC,"Just to clarify, it's not ever possible to /block/ boot with systemd. Even if all networking is required to complete a boot, but all of them fail, the system will come in ""degraded"" state. But as much as possible, will be configured."
1664844,2017-05-25 20:33:04 UTC,"On Thu, May 25, 2017 at 04:00:16AM -0000, Mike Pontillo wrote:

> Well, to clarify, I guess I'm not 100% happy with that. ;-)
"
1664844,2017-10-11 22:35:36 UTC,"Agreed, these are two separate features, both of which we should support - though optional is the higher priority one, which has bubbled up elsewhere in addition, and having 'optional' is likely a usable workaround for Mike's use case."
1664844,2017-05-25 04:00:16 UTC,"Well, to clarify, I guess I'm not 100% happy with that. ;-)"
1664844,2017-03-10 09:42:30 UTC,"This is a gray area but I want to say it impacts MAAS -- currently, we represent ""link down"" by leaving the interface out of the YAML. This is less than ideal."
1664844,2017-02-20 21:06:17 UTC,"Sounds to me like before we can implement something like this, we'd need a way to specify this to the renderer themselves. There will need bugs opened for NetworkManager and networkd to understand ""administratively down"" states -- ie. we configured this already but we want to keep the device down for now."
1664844,2017-02-15 19:15:14 UTC,"On Wed, Feb 15, 2017 at 12:51 PM, Mike Pontillo <<email address hidden>

> wrote:
"
1664844,2017-02-15 18:51:45 UTC,"I respectfully disagree. Think of deploying a simple router, such as a home NAT gateway. You would likely want wan0 to be in a mode like I described, ""link-up interface with DHCP enabled, but don't block boot if you can't DHCP""."
1664844,2017-02-15 18:30:09 UTC,"On Wed, Feb 15, 2017 at 12:16 PM, Mike Pontillo <<email address hidden>

> wrote:
"
1664844,2017-02-15 18:16:58 UTC,"By the way, to add to (2) above, in order to create a link-down DHCP interface which does not block the boot process if DHCP fails, you also need another workaround involving a post-up/pre-down script to launch the DHCP client and release the address, respectively."
1664844,2017-02-15 15:48:31 UTC,"In ifupdown, 'manual' mode does accomplish this, yes. The side effect of this is that systemd does not block booting if the interface hasn't been enabled yet."
1664844,2017-05-23 23:04:18 UTC,"> - If wan0 is not link up, I wouldn't want that to block
> boot. Maybe my ISP is having trouble. Maybe the dog chewed
> through the cable. I don't know. But I don't to block the
> boot process (and thus the other functions of the router)
> because of it. If I block boot, I can't even SSH into the
> box to figure out what went wrong.
"
1664844,2017-05-25 03:54:17 UTC,This bug was observed with a backport of Netplan running on Xenial with systemd.
1664844,2017-12-20 14:08:11 UTC,I still see the issue on Ubuntu 17.10.
1664844,2017-12-04 14:03:42 UTC,Autopktests still failing for xenial; the test is still not being skipped (we know it won't work on Xenial due to the version of NM shipped there). Marking verification-failed-xenial.
1664844,2017-11-29 21:26:43 UTC,"Hello Mike, or anyone else affected,"
1664844,2020-10-28 19:23:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664844,2020-06-08 16:14:07 UTC,We are actively working on it for the current 20.10 cycle.
1664844,2020-06-06 12:34:45 UTC,Is there an updated target release for the ability to describe configuration for an interface (such as name) but leave the interface down at boot?
1664844,2019-04-10 16:10:37 UTC,I need this too. How do I vote?
1664844,2019-02-28 07:10:36 UTC,"Accidentally pressed ""Fix Release"" for (Ubuntu Xenail)
Didn't even know I had permission to change status to ""Fix Release"""
1664844,2018-08-15 13:56:01 UTC,Repurposing this bug now to track the feature work for a specific activation mode option in netplan to keep interfaces administratively down (or manually configured)
1664844,2018-04-12 08:48:55 UTC,This bug was fixed in the package nplan - 0.32~16.04.4
1664844,2018-04-11 22:45:09 UTC,This bug was fixed in the package nplan - 0.32~17.10.3
1664844,2017-12-13 20:13:35 UTC,"verification-done for xenial 0.32~16.04.3, and zesty 0.32~17.04.1:"
1664844,2018-03-05 13:15:33 UTC,Accepted for xenial-proposed. Please test the package and set the verification-done-xenial on success. Thank you!
1664844,2017-12-05 09:14:22 UTC,"Hello Mike, or anyone else affected,"
1664844,2017-12-21 00:08:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664844,2018-01-10 02:34:58 UTC,This bug was fixed in the package nplan - 0.32~16.04.3
1664844,2018-04-09 16:05:03 UTC,"Verified nplan 0.32~17.10.3 for artful:
Verified nplan 0.32~16.04.4 for xenial:"
1664844,2018-01-10 02:37:12 UTC,This bug was fixed in the package nplan - 0.32~17.04.1
1664844,2018-02-28 00:54:46 UTC,"Hello Mike, or anyone else affected,"
1664844,2018-03-05 12:25:16 UTC,"Hello Mike, or anyone else affected,"
1664844,2018-01-10 02:35:55 UTC,"The verification of the Stable Release Update for nplan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1664846,2017-05-19 15:11:34 UTC,"Is this really supported using MAAS right now? AIUI, there wouldn't be anything in ifupdown to do this."
1664846,2017-05-23 23:10:17 UTC,"I guess lack of ifupdown support is worked around with {pre,post}-{up,down} scripts."
1664846,2017-05-25 03:49:55 UTC,"If we decide to implement this (I think it's still a wishlist item), I would prefer it to be more of a 'preferred driver choice' type of option. That is, model it like a normal bond in the YAML, but have something like a ""preferred-driver: teaming"" or similar, with a way to pass in additional ad-hoc custom parameters for that driver. (Only options very specific to that particular driver should ever be used in this ad-hoc manner. Bonds should be modeled as generically as possible, with industry-standard options exposed in the generalized YAML.)"
1664846,2020-10-20 21:34:20 UTC,I'm curious if there has been any movement on this.  We switched to using the 'team' driver over the 'bonding' driver some time ago.  Having an abstracted network configuration capability through netplan would be very nice.
1664847,2019-05-21 16:34:06 UTC,Wanting to use macvlan to set up docker containers with their own IP addresses on the network.  As a result I have to set up macvlan on the host too for connectivity to the containers.  Really want to use netplan but have to resort to startup scripts to manually reconfigure networking on reboots.
1664847,2020-12-14 21:51:46 UTC,"Building on #18
I got the whole process working using netplan. For anyone needing a little more details"
1664847,2020-11-26 03:38:15 UTC,"Hey guys, here is my workaround with Netplan:"
1664847,2020-05-15 15:05:00 UTC,"Like #10, I stumbled across this bug searching for ""netplan macvlan"".  Hopefully the following helps anyone else that ends up here."
1664847,2019-11-21 00:01:15 UTC,"Hello rodalphoc,"
1664847,2019-10-17 18:09:56 UTC,"Note you do not need to drop netplan entirely, you can run ifupdown for macVLAN (only) at the same time as using netplan for everything else. This is obviously an abomination that should be purified with cleansing fire, but it does work."
1664847,2019-10-07 16:51:26 UTC,"Hey guys, do this for Ubuntu 20.04, pleeeease!  :-P"
1664847,2019-07-02 11:24:19 UTC,"As suggested in the netplan FAQ, since macvlan support doesn't exist, you can switch back to `ifupdown`:"
1664847,2019-05-07 17:15:59 UTC,Please add support for macvlan and ipvlan
1664847,2018-10-26 15:23:22 UTC,This would be very useful when deploying OpenStack Ansible with systemd-nspawn! It uses MACVLAN interfaces.
1664847,2017-02-20 21:08:14 UTC,Is this a current wishlist for MAAS or was it implemented at all? How many users are requesting this feature? How would you use macvlan/macvtap devices?
1664847,2019-02-04 02:17:07 UTC,"This link is 2nd in google search for ""netplan macvlan""
1st link is about someone who gave up. :("
1664847,2017-03-10 09:19:40 UTC,"This is not urgent for MAAS at this time, but I'll let you know if that changes."
1664847,2017-05-23 23:14:10 UTC,"For reference, an explanation of how macvlan differs from other currently supported interface types. https://sreeninet.wordpress.com/2016/05/29/macvlan-and-ipvlan/"
1664847,2018-05-24 22:16:15 UTC,"I use macvlan with LXD, and am expecting to adoption of bionic hosts/containers to begin rollout imminently.  I can work around this with some manual trickery, but it's going to be a mess."
1664847,2018-07-05 08:52:55 UTC,"I'm using macvlan to implement some IP redundancy scheme and while I can workaround the netplan limitation thanks to networkd-dispatch scripts, I would rather be able to create interface directly using netplan."
1664847,2018-08-03 05:15:12 UTC,I rather not have a hack to do this as well. This might force me to utilize another OS.
1664847,2018-09-05 17:27:59 UTC,+1 on this request
1664847,2018-04-12 19:01:15 UTC,"Per internal SF ticket #00175665, customer would also like to see this feature implemented in MaaS"
1664851,2018-06-10 02:54:15 UTC,"Change abandoned by Tom Barron (<email address hidden>) on branch: master
Review: https://review.openstack.org/433559
Reason: No activity since February 2017; restore and rebase if appropriate."
1664851,2019-10-28 17:21:54 UTC,"Closing issue if you are still seeing this, please re-open if necessary."
1664852,2017-05-09 02:07:44 UTC,"Change abandoned by LiChunlin (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/434146
Reason: cancel"
1664852,2017-02-15 08:54:35 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/434146"
1664862,2017-03-16 14:32:33 UTC,"Reviewed:  https://review.openstack.org/444167
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=67d0edc73acc3e398bffbbe474b4b6224db9b250
Submitter: Jenkins
Branch:    stable/newton"
1664862,2017-02-15 08:23:01 UTC,"As a workaround on all the compute nodes run the following:
# update-alternatives --set ovs-vswitchd /usr/lib/openvswitch-switch-dpdk/ovs-vswitchd-dpdk
# sudo service openvswitch-switch restart"
1664862,2017-02-17 13:55:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435454"
1664862,2017-03-03 10:19:29 UTC,"root@node-64:~# lsof -n -p 4501
COMMAND    PID USER   FD      TYPE   DEVICE SIZE/OFF   NODE NAME
ovs-vswit 4501 root  cwd       DIR    252,0     4096      2 /
ovs-vswit 4501 root  rtd       DIR    252,0     4096      2 /
ovs-vswit 4501 root  txt       REG    252,0  2323144 262425 /usr/lib/openvswitch-switch/ovs-vswitchd"
1664862,2017-03-10 08:42:45 UTC,"Reviewed:  https://review.openstack.org/435454
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=e0e195b1e65c8191fadb85b9eabed68ccb35e70d
Submitter: Jenkins
Branch:    master"
1664862,2017-03-10 09:10:06 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/444167"
1664862,2017-03-10 09:10:26 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/444168"
1664862,2017-03-22 15:08:28 UTC,Part of syslog on node-1 at the time it was considering agents as dead: http://paste.openstack.org/show/603776/ - some problem with mysql?
1664862,2019-12-18 17:22:19 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/444168
Reason: This repo is retired now, no further work will get merged."
1664862,2017-03-27 06:28:43 UTC,"Please disregard the last comment, it's for another bug, sorry"
1664880,2017-02-15 08:45:49 UTC,Now in sed-4.4 this issue was fixed by packager. Here is the patch.
1664880,2017-02-15 08:55:38 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281638
1664882,2017-11-15 19:37:28 UTC,"I was thinking exactly the same thing recently, and came here to file a ""wishlist"" bug report, only to find it already existed! This is a common need in server certification, since we often have to ""babysit"" boot processes via the BMC."
1664882,2019-09-19 12:02:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1664882,2019-09-19 13:09:38 UTC,"@adam-collard, this is a feature request, not an issue that is should expire after 6 months. If you do not want to implement this feature than that is fine, but please say so."
1664882,2019-09-19 13:13:44 UTC,The feature still does not exist in MAAS 2.6.0 (7802-g59416a869-0ubuntu1~18.04.1) and would still be useful.
1664882,2019-09-23 13:59:27 UTC,"Being a feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1664882,2019-09-24 08:45:04 UTC,https://discourse.maas.io/t/add-link-to-node-oob-management-address-in-web-ui/1015
1664890,2017-11-03 16:30:35 UTC,Syncing task from Mir.
1664910,2017-02-15 09:43:40 UTC,"22:06:15 ERROR| [stderr] Run kernel regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... FAIL
[...]
22:24:53 ERROR| [stderr] running onexec
22:24:53 ERROR| [stderr] ONEXEC - check current 'unconfined' != expected '/tmp/testlibVNZdG_/source/old_trusty/apparmor-2.8.95~2430/tests/regression/apparmor/onexec'
22:24:53 ERROR| [stderr] Fatal Error (onexec): Unable to run test sub-executable"
1664910,2017-02-15 21:07:18 UTC,"Pushed https://git.launchpad.net/qa-regression-testing/commit/?id=c772fe5c1fd06107459f3d89ef36700e0b1b11d7 to lp:qa-regression-testing which fixes some races in the onexec apparmor tests for the ""old"" 14.04 apparmor regression tests."
1664919,2017-02-15 10:49:28 UTC,Translate.
1664920,2020-07-06 10:02:03 UTC,"This has clearly now been fixed.  Given the age of the bug, I don't think it's worth digging up the detail of how that happened."
1664928,2017-04-10 14:04:58 UTC,"On Windows 10 x64
- reproduced with Inkscape 0.91 r13725
- not reproduced with Inkscape 0.92.1 r15371"
1664928,2017-04-18 09:42:34 UTC,@unfa - could you please confirm that the bug is fixed for you in 0.92.1?
1664928,2017-04-10 14:11:42 UTC,"Probably fixed in r14306, see bug #1434122."
1664928,2017-04-10 13:07:47 UTC,Reopening with new data on the subject.
1664928,2019-12-31 09:08:21 UTC,"Closing because there was no reply.
If the bug still exists, please reopen in the new bugtracker: https://inkscape.org/report/"
1664928,2017-02-17 00:45:41 UTC,"Closing for now - feel free to reopen the report if you have additional information (e.g. which older version of Inkscape to test with, source SVG and renderings (bitmap  exports) done with older Inkscape versions to allow comparison with the new cairo-based renderer in Inkscape >= 0.91)."
1664928,2017-02-16 15:09:58 UTC,Hmm. I'll resurrect this issue if I manage to get some hard data on the subject.
1664928,2017-02-15 11:27:18 UTC,"Attached are the bitmap exports with Inkscape 0.47, 0.48.2, 0.48.5, 0.91, 0.92.0 and 0.92.1 of the provided Inkscape SVG file. AFAICT there is no difference in how opacity is rendered [1]."
1664928,2017-02-15 11:01:11 UTC,"Please (always) add information about OS/platform and Inkscape version to the bug description, thank you."
1664928,2017-02-15 10:26:36 UTC,Here's a PNG rendering of the test SVG file.
1664928,2017-04-10 13:07:04 UTC,I have some hard data for this issue.
1664931,2017-05-24 04:41:16 UTC,"Re comment #13, any progress nova-coresec?"
1664931,2017-10-27 14:15:24 UTC,"There haven't been any updates on this bug. It's a known issue, we just haven't had someone push a fix yet."
1664931,2017-10-27 14:47:54 UTC,"I'd like to point that this bug is already more than half-year old. Is there any meaning to have 'private bug report' when bug wouldn't be fixed for two duration of openstack release cycles? I think if this bug had been disclosed as normal, it would have been fixed in ocata."
1664931,2017-10-27 15:57:43 UTC,"George: I'm in full agreement with you there. I've been suggesting for a while that the OpenStack VMT should set a hard limit on the acceptable duration of report embargoes and switch bugs to public security type for wider assistance if not resolved in that timeframe. There has been pushback on that philosophy in the past, but it's certainly worth bringing up again."
1664931,2017-10-27 17:59:02 UTC,"@Sylvain, your patch won't work because of this in the conductor rebuild_instance method:"
1664931,2017-10-27 17:45:11 UTC,"I'm working on a recreate of the bug in a functional test within the nova repo, then will apply Sylvain's change on top of that to verify it fixes the bug. Then we can make this public."
1664931,2017-10-27 19:40:44 UTC,"I've got a local patch that I'll be posting shortly in here. It adds a functional recreate of the bug and the fix on top. It has a few TODOs in it that need to be resolved, and will require some review from Sylvain, but it's mostly there. Should have it attached by EOD."
1664931,2017-10-27 20:10:11 UTC,Here is the patch with the recreate test and fix.
1664931,2017-10-27 20:24:41 UTC,+2 on the patch from comment #25
1664931,2017-10-27 16:01:17 UTC,"George: It's also worth mentioning that if you, as the reporter of this issue, prefer for it to be made public, that's fine. The OpenStack VMT typically follows the reporter's wishes in such matters."
1664931,2017-03-29 22:41:04 UTC,"Matt, I meant a common use-case to secure hardware repartition against aggressive tenant as described in comment #8."
1664931,2017-03-17 16:22:11 UTC,"Thanks for the review, here is the updated impact description draft:"
1664931,2017-03-29 21:08:55 UTC,"Note that there is another public bug for the same issue, but it doesn't mention a possible security impact:"
1664931,2017-03-17 14:38:36 UTC,"I agree that if these controls are relied on by some deployments as a security measure, then bypass by users does constitute a vulnerability."
1664931,2017-03-15 06:06:25 UTC,"This looks like a class A type of bug according to VMT's taxonomy ( https://security.openstack.org/vmt-process.html#incident-report-taxonomy ), though I'm in favor for fixing this in the open since the impact sounds limited."
1664931,2017-02-21 16:12:47 UTC,"George, that's something optionable by operators : if they disabled ComputeFilter in their nova.conf, then the scheduler stops only accepting active computes, and can return disabled nodes too."
1664931,2017-02-16 16:43:37 UTC,One more thing I thought about: What should nova do during 'nova rebuild' command if this host's nova-compute is marked as 'disabled' by system administrator?
1664931,2017-02-16 13:24:06 UTC,About severity of the issue: I've just imaged scenario where this would lead to compromise.
1664931,2017-02-15 23:31:24 UTC,Here is the possible solution for that bug.
1664931,2017-02-15 22:31:56 UTC,"Yeah, the bug is latent since https://github.com/openstack/nova/commit/d6ca1cc02ab58615a6bb1b337db34dd06525112e"
1664931,2017-02-15 22:00:55 UTC,"I may be naive here, but the fix seems rather trivial. In rebuild_instance in conductor manager, in the rebuild case (where host is not None), we could call _schedule_instances and assert that the provided host must be in the returned list, else we can't rebuild the instance on that host with that image."
1664931,2017-02-15 21:52:05 UTC,I believe the issue is that we bypass the scheduler filters because in the compute API for rebuild we pass the existing host for the instance to conductor here:
1664931,2017-02-15 15:44:33 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1664931,2017-03-29 21:14:52 UTC,"> I'm still on the fence to keep this under embargo if the filter scheduler aren't a common use-case
"
1664931,2017-10-27 20:43:28 UTC,Here is the final version of the patch for master (queens). Will start working on stable branch patches.
1664931,2017-10-28 02:21:50 UTC,"Alright, some of the USE_NEUTRON stuff that I changed in the original master branch patch had a side effect on some other tests, so I'm just going to have to remove that stuff, and thus redo the patches on stable once that's done. So hold off on sending these patches to people. I'll work on it over the weekend and post them all in a single comment when I'm done and sure they are all passing all unit and functional tests."
1664931,2017-12-05 14:45:03 UTC,"Reviewed:  https://review.openstack.org/523649
Committed: https://git.openstack.org/cgit/openstack/ossa/commit/?id=ab54ce232d6db2b3e126ac61ee015d8b180e2ad6
Submitter: Zuul
Branch:    master"
1664931,2017-11-14 20:28:45 UTC,"Reviewed:  https://review.openstack.org/519681
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b72105c1c49fcddc94992af63fc2f8078023491a
Submitter: Zuul
Branch:    stable/ocata"
1664931,2017-11-14 20:50:19 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/519752"
1664931,2017-11-14 20:51:49 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/519753"
1664931,2017-11-14 20:55:42 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/519755"
1664931,2017-11-14 22:20:52 UTC,"Reviewed:  https://review.openstack.org/519752
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3f63d057a64b688b66ff1903c1afc4d97ba6df6d
Submitter: Zuul
Branch:    stable/pike"
1664931,2017-11-14 22:21:04 UTC,"Reviewed:  https://review.openstack.org/519753
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ffd4f72d16dacd6ca1e703f9bab37b8917d253e7
Submitter: Zuul
Branch:    stable/ocata"
1664931,2017-11-14 23:10:14 UTC,"Reviewed:  https://review.openstack.org/519738
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=31d28eef95ab82bdfce2221cd5633bcf4bc13653
Submitter: Zuul
Branch:    master"
1664931,2017-11-15 01:06:40 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1664931,2017-11-15 01:10:25 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1664931,2017-11-16 17:32:11 UTC,"Reviewed:  https://review.openstack.org/519684
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97a51d981bd603b964b04b3568218ce57ac57338
Submitter: Zuul
Branch:    stable/newton"
1664931,2017-10-27 21:36:02 UTC,This is the stable/pike backport patch. Minor changes to the functional test setup to work in Pike with the FilterScheduler.
1664931,2017-11-16 17:53:38 UTC,"Reviewed:  https://review.openstack.org/519755
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=698b261a5a2a6c0f31ef5059046ef7196d5cba30
Submitter: Zuul
Branch:    stable/newton"
1664931,2017-11-16 19:59:19 UTC,This issue was fixed in the openstack/nova 14.0.10 release.
1664931,2017-11-17 18:19:48 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/521153"
1664931,2017-11-27 20:09:06 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/523212"
1664931,2017-11-27 20:09:19 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/523213"
1664931,2017-11-28 03:48:48 UTC,"Reviewed:  https://review.openstack.org/521186
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f7c688b8ef88a7390f5b09719a2b3e80368438c0
Submitter: Zuul
Branch:    master"
1664931,2017-11-28 14:49:18 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/523427"
1664931,2017-11-28 15:04:14 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/523434"
1664931,2017-11-28 18:57:37 UTC,"Reviewed:  https://review.openstack.org/521153
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cacfd372acb4eb056c4391db3c988bfe91c957df
Submitter: Zuul
Branch:    master"
1664931,2017-11-29 01:50:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/523649"
1664931,2017-12-01 19:50:26 UTC,"Reviewed:  https://review.openstack.org/523212
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b29a461a8bc05c9b171c0574abb2e7e5b62a2ed7
Submitter: Zuul
Branch:    stable/pike"
1664931,2017-12-01 19:58:29 UTC,"Reviewed:  https://review.openstack.org/523427
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bbfc4230efe3299fa51f9451f54062f32590ed3d
Submitter: Zuul
Branch:    stable/ocata"
1664931,2017-11-14 20:27:38 UTC,"Reviewed:  https://review.openstack.org/519672
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9e2d63da94db63d97bd02e373bfc53d95808b833
Submitter: Zuul
Branch:    stable/pike"
1664931,2017-12-01 19:58:37 UTC,"Reviewed:  https://review.openstack.org/523434
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4cbfcc590c17134fd14e3aab90ffbb7c17006a95
Submitter: Zuul
Branch:    stable/newton"
1664931,2017-11-14 20:27:17 UTC,"Reviewed:  https://review.openstack.org/519662
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=984dd8ad6add4523d93c7ce5a666a32233e02e34
Submitter: Zuul
Branch:    master"
1664931,2017-11-14 16:27:28 UTC,"Reviewed:  https://review.openstack.org/519686
Committed: https://git.openstack.org/cgit/openstack/ossa/commit/?id=cb43ec59595e9875a179008da346852aee42fd41
Submitter: Zuul
Branch:    master"
1664931,2017-10-28 23:53:37 UTC,Updated master branch patch.
1664931,2017-10-28 23:54:04 UTC,Updated pike patch.
1664931,2017-10-28 23:54:36 UTC,Updated ocata patch.
1664931,2017-10-28 23:54:56 UTC,Updated newton patch.
1664931,2017-10-28 23:55:12 UTC,OK should be good for disclosure.
1664931,2017-10-29 23:56:42 UTC,Backports look good to me.  I'm happy to hold the nova EOL until after this has been merged.  I do worry that a late change like this could be a little disruptive so I wonder if it's worth releasing nova (newton) as is and then again after this has merged that way if we've made a mistake there is a pretty easy work around.
1664931,2017-10-30 17:06:10 UTC,Here's an updated impact description to cover latest releases and EOLs in the time since comment #13 (the lowest affected release may need altering if we follow Tony's recommendation to have a 14.0.9 without the fix and then tag 14.0.10 with it):
1664931,2017-10-30 17:31:34 UTC,"> I need to know, however, how much of a pain it is to delay Newton EOL for two weeks without being able to publicly say why.
"
1664931,2017-10-30 18:24:38 UTC,I like the delay (pre-ossa this week) but the delayed push until post Sydney. I feel like it's best to let folks focus on the summit instead of pushing through an embargoed set of patches.
1664931,2017-10-31 12:19:54 UTC,MITRE has assigned CVE-2017-16239 for this issue.
1664931,2017-10-31 12:30:04 UTC,"Given the feedback so far on the available options, in an effort to avoid surprising our community while it's in the midst of its busiest conference week of the season I'm inclined to send the pre-OSSA (impact description and patches) to the downstream stakeholders on our embargo notice list today indicating Tuesday November 14 as the planned public disclosure for this advisory. That's 10 business days instead of our usual 3-5, but if someone happens to leak it early this is at least a limited enough vulnerability that it won't be too terrible of an emergency."
1664931,2017-10-31 13:03:26 UTC,"That sounds fair enough, thanks fungi!"
1664931,2017-10-31 21:08:33 UTC,Pre-OSSA for this has been sent to the embargo notice mailing list.
1664931,2017-11-01 01:25:20 UTC,We just releases nova 14.0.9 so as discussed the actual OSSA (and perhaps the pre-OSSA) will need to alter the affected versions to show the 14.0.9 is affected
1664931,2017-11-01 12:23:26 UTC,Tristan just sent errata for the affected versions to the embargo notice list reflecting the fact that the new 14.0.9 is also impacted.
1664931,2017-11-09 09:55:12 UTC,"I tested the patch in newton and it works well.
But when nova rejects the rebuild operation, image of the instance is still changed.
For example, if we rebuild an ubuntu instance with a new windows image and it is rejected by the nova scheduler, when we do a ""nova show"" we see that the instance has a windows image."
1664931,2017-11-09 10:10:20 UTC,"@Nolwenn, thanks for testing the patch. The issue you described about the image_ref is a long-standing issue in any case where rebuild fails once we RPC cast from the API to the conductor (or compute) service, and is related to bug 1482040. I think that is a separate, latent issue, worth fixing on it's own, not as part of this security fix."
1664931,2017-11-14 15:11:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519662"
1664931,2017-11-14 15:23:57 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/519672"
1664931,2017-11-14 15:41:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/519681"
1664931,2017-11-14 15:49:22 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/519684"
1664931,2017-11-14 15:52:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/519686"
1664931,2017-11-14 16:21:00 UTC,"The attachment ""0001-Rebuild-should-verify-the-host.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1664931,2017-11-14 20:12:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/519738"
1664931,2017-10-28 01:03:38 UTC,Oh wait the newton patch in comment 30 needs some work.
1664931,2017-10-27 22:59:37 UTC,"Here is the stable/ocata patch, it required a few minor changes to resolve merge conflicts and add some missing stuff that wasn't in ocata."
1664931,2017-12-08 23:44:56 UTC,"Reviewed:  https://review.openstack.org/523213
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=234ade29a39cf2d51e08157e149e0cbd0c5047be
Submitter: Zuul
Branch:    stable/pike"
1664931,2017-12-18 12:51:35 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1664931,2018-01-03 14:37:43 UTC,This issue was fixed in the openstack/nova 15.1.0 release.
1664931,2018-01-10 01:12:31 UTC,This issue was fixed in the openstack/nova 14.1.0 release.
1664931,2018-02-20 17:33:32 UTC,"For anyone keeping track, bug 1750618 was yet another regression introduced by the first change for this bug."
1664931,2017-10-28 00:02:03 UTC,"Here is the stable/newton patch, some more minor changes needed for the test to work."
1664931,2017-12-07 23:55:53 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1664934,2017-02-15 22:13:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Since this change would best be made upstream by the NetworkManager developers, it would be helpful if you could report this wishlist bug on the upstream bug tracker. Can you file a bug at https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager&component=VPN:%20openconnect and paste a link to the report back here?"
1664934,2017-02-15 22:36:20 UTC,I think this is already fixed as part of https://bugzilla.gnome.org/show_bug.cgi?id=770880 isn't it?
1664934,2017-02-15 23:19:08 UTC,"Hi, thanks for your quick feedback."
1664934,2017-02-15 23:23:39 UTC,"Yes, thanks, it looks like the GcrCertificateWidget displays the certificate details in a fixed width font so it's taken care of there. So this will be fixed with a future release."
1664934,2017-02-16 09:00:05 UTC,OK. But should we report the bug somewhere else?
1664934,2017-02-16 18:04:27 UTC,"lbesson - no need to report this elsewhere. As dwmw2 pointed out, this has been fixed upstream, this bug will be marked resolved when the next release containing the fix is packaged."
1664934,2017-02-16 19:43:01 UTC,"OK.
We will have to trust @dwmw2, as I wasn't able to check that the bugfixes (s)he linked to were correcting this bug (wrongly displayed ""Public key's random art"")."
1664953,2017-05-01 18:27:58 UTC,This issue has been fixed already according to the previous irc meeting.
1664953,2017-02-15 15:33:11 UTC,"Thanks - that's what I was looking for.
Marked this as incomplete on Tempest, I doubt it's a problem on Tempest side.
Even though it may be possible to schedule tests to minimise memory usage at any point in time, I'm not sure that's much more than we do already that's worth doing with a reasonable ROI."
1664953,2017-02-15 22:45:47 UTC,See some history of this in https://bugs.launchpad.net/neutron/+bug/1656386
1664953,2017-02-15 15:02:04 UTC,"fwiw, there is the openstack-gate project for random infra things we need to track"
1664953,2017-02-17 20:39:44 UTC,Duplicates of https://bugs.launchpad.net/neutron/+bug/1656386
1664958,2017-03-02 13:49:13 UTC,"Due to necessity to backport a big amount of refactoring changes for fixing non high or critical bug.
Recommend to use workaround to avoid this problem"
1664960,2017-02-15 19:31:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664960,2017-03-02 08:47:54 UTC,This bug was fixed in the package linux - 4.4.0-65.86
1664969,2017-02-15 17:41:11 UTC,"I just played a little on my macOS 10.12.3:
I could reproduce this odd behavior, but do not have any idea currently."
1664969,2017-02-15 18:11:58 UTC,"Ok, also reproduced with Java Robot:
with an opened drawer, the mouse down is not recognized by the widget."
1664969,2017-02-20 07:44:12 UTC,Thank you for your quick investigation!
1664969,2017-02-20 09:32:31 UTC,"Good news (though does not help you currently):
yesterday I implemented the drag/drop feature in version 2:
and oh wonder: it works with your widget :-)"
1664969,2018-09-15 09:44:10 UTC,"Well, I went after it for an hour or so and below code works for me!"
1664974,2017-04-18 08:51:13 UTC,Doesn't reproduced against latest F10 iso.
1664974,2017-03-16 11:30:09 UTC,"I investigate neutron logs and found https://paste.mirantis.net/show/10539/ - seems that MySQL was having problems and that time deamon.log and mysql.log:
https://paste.mirantis.net/show/10538/
https://paste.mirantis.net/show/10537/"
1664974,2017-02-16 19:41:40 UTC,"There are actually problems of dependencies it seems from the puppet logs, this is very weird because apparently I get the same error when trying to use L2 + DVR. One week ago I had a deployment with that enabled and it deployed successfully. Could you check this out?"
1664974,2017-02-22 06:52:17 UTC,"I edited /etc/puppet/newton-10.0/modules/openstack_tasks/manifests/openstack_network/plugins/ml2.pp on the Fuel master and increased the 'waiting-for-neutron-api' exec parameter 'try_sleep' to 20, redeployed (through the Fuel web UI) and it worked. That seems to show that the Neutron API is not ready within two minutes (default is 4 seconds wait, 30 tries). Should it simply be increased, or is it a problem that the API is taking too long to become ready?"
1664974,2017-02-20 07:57:46 UTC,"Further detail from this same environment, here is the error message from the Fuel Dashboard:"
1664974,2017-02-20 01:19:04 UTC,"Snapshot
https://1drv.ms/u/s!AvlKFvlmzy2kgbdbuByHzjW9reTQuQ"
1664974,2017-03-06 16:13:36 UTC,"Very strange, it took 10 minutes to start neutron-server"
1664979,2017-02-15 17:01:32 UTC,"After another reboot, EQ overflowing occurs again, it seems random to me now."
1664979,2017-06-02 09:46:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1664979,2017-06-02 09:56:56 UTC,"Hi! I can reproduce this bug too.
System just going to freeze and does not react to keyboard. After reboot sometimes it happens again (for example while watching youtube video in vivaldi browser).
Here's part of syslog attached."
1664979,2017-09-09 15:22:25 UTC,This bug happens again after I've done a fresh install.
1664979,2017-09-09 15:24:38 UTC,It happened when I unlock the screen.
1664979,2018-04-24 00:54:03 UTC,"The only time this occurs for me, is when I try to close a java application (https://www.interactivebrokers.com/en/index.php?f=16045).  With this particular java application, it appears to happen more often, if I use the window close button instead of the menu close item when closing windows (but always it occurs when attempting to quit, so it appears to be related to releasing memory)."
1664979,2018-07-28 16:12:40 UTC,"This occurs for me when I send inputs via a virtual uinput device i created, which X auto recognizes and starts uses."
1664990,2017-03-03 14:37:27 UTC,"Indeed, my original request was a naive approach, which is why I suggested in comment #1 identifying what in chromium’s implementation we want to replicate."
1664990,2017-03-03 11:31:18 UTC,"I looked into chromium’s implementation, and it’s a bit more complex than what I described in the description. Details are in TabStripModelOrderController::DetermineNewSelectedIndex(…)¹."
1664990,2017-03-03 14:31:00 UTC,"The other thing from that chromium code is that the closing order should be different. In the case you describe of having opened B, C and D background tabs. Closing D should not focus A (which created it) but instead focus C."
1665006,2017-02-15 15:31:28 UTC,Added cmake-extras as we need this support in cmake for the GSettings module provided there.
1665006,2017-02-16 19:08:12 UTC,mmm do you want to open an upstream ticket for this?
1665013,2017-02-20 16:24:38 UTC,"I think this points to a more general authentication UX issue -- charmstore identity is also used in the context of agreeing to terms, or accessing hosted juju controllers."
1665013,2017-02-20 16:30:03 UTC,"If this is just an issue with the behavior of `charm logout`, I recommend opening an issue on github.com/juju/charmstore-client."
1665013,2017-02-22 00:38:43 UTC,Charmstore-client issue: https://github.com/juju/charmstore-client/issues/115
1665013,2017-02-28 14:51:38 UTC,"I believe juju also needs some attention is this area as it's not clear what all is happening when you login. The planned juju login changes may address this, but I think this bug also has juju implications."
1665016,2017-02-15 16:30:13 UTC,This change was made by a bot.
1665016,2017-11-27 06:41:20 UTC,Why does this error message appear? in other forums people mention that its referencing hardware that won't be supported sometime in future yet https://cateee.net/lkddb/web-lkddb/SENSORS_ATK0110.html shows it is supported in Linux Kernel 4.14
1665016,2018-03-31 09:27:41 UTC,The message is now different:
1665029,2017-02-17 08:26:21 UTC,"Closing the snappy task, its fine if this is tracked via snapweb."
1665029,2017-02-16 09:16:01 UTC,"Thanks for the bug report. There is a new design update coming up which
should make things simpler to navigate."
1665036,2020-10-22 19:47:32 UTC,closing since the package is removed from Ubuntu
1665048,2019-07-21 08:59:35 UTC,Bug is still present in Xubuntu 18.04 LTS. For me it gets triggered on a laptop when switching between a 16:9 projector and a 16:10 monitor (since the 16:10 monitor doesn't offer the 1280x720 resolution set up for the projector).
1665048,2019-01-20 17:42:43 UTC,The above commit should resolve this bug (testing in Virtualbox). Please reopen if it does not.
1665048,2019-01-20 17:40:51 UTC,Sean Davis referenced this bugreport in commit 4941ee50071a1ea0080be6586f811333ae624ef9
1665048,2019-01-18 12:33:51 UTC,"Bug still present in Xubuntu 19.04 daily build iso, 20190118-0213"
1665048,2018-10-13 20:44:49 UTC,"StacktraceTop:
 convert_xfce_output_info (output_id=<optimized out>) at main.c:1618
 get_output_for_window (window=<optimized out>) at main.c:2671
 select_current_output_from_dialog_position (app=0x557e3781ee90) at main.c:2708
 dialog_map_event_cb (widget=widget@entry=0x7f366000c580, event=<optimized out>, data=0x557e3781ee90) at main.c:2722
 _gtk_marshal_BOOLEAN__BOXED (closure=0x557e3781f130, return_value=0x7ffe4fdc5840, n_param_values=<optimized out>, param_values=0x7ffe4fdc58a0, invocation_hint=<optimized out>, marshal_data=<optimized out>) at gtkmarshalers.c:86"
1665048,2018-10-13 20:40:57 UTC,Bug #1628250 is now public.
1665048,2018-09-27 13:08:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1665048,2017-10-21 19:10:51 UTC,Confirmed in 17.10 as well.
1665048,2017-02-23 19:23:58 UTC,"One more thing: I can reproduce this crash even when the guest utilities are installed and working correctly, if I resize the virtualbox window and then quickly run display settings before the display is resized to match the new window size (which takes about 2 seconds to happen)."
1665048,2016-05-29 21:18:53 UTC,"l3eta@l3eta-ubuntu:~/Desktop$ gdb xfce4-display-settings
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""i686-linux-gnu"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word""...
Reading symbols from xfce4-display-settings...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/xfce4-display-settings
[Thread debugging using libthread_db enabled]
Using host libthread_db library ""/lib/i386-linux-gnu/libthread_db.so.1"".
[New Thread 0xb6547b40 (LWP 3475)]
[New Thread 0xb5d46b40 (LWP 3476)]"
1665048,2017-02-19 23:20:52 UTC,Attached are the two xrandr outputs from the video.
1665048,2017-02-19 23:17:45 UTC,Here is a video demonstrating the bug:
1665048,2017-02-19 19:45:23 UTC,These warnings are output:
1665048,2017-02-19 19:44:31 UTC,Here is a full backtrace:
1665048,2017-02-18 13:45:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665048,2017-02-17 19:59:50 UTC,Removing duplicate bug report because it is private and cannot be accessed.
1665048,2017-02-17 19:56:10 UTC,I can repro this in virtualbox.
1665048,2017-02-15 17:40:41 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1628250, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1665048,2016-05-31 05:50:50 UTC,"Seems to have to do with the ViewSonic being at 1920x1080_60 can't open Display at all after I have done xrandr --output VGA-0 --mode ""1920x1080_60.00"""
1665048,2017-02-20 08:32:05 UTC,"See the crash - but I get no warnings, just ' Segmentation fault (core dumped)'"
1665048,2017-02-21 03:54:42 UTC,I noticed that the crash doesn't seem to happen if you change the screenmode from within xfce4-display-settings before resizing the window.
1665069,2019-07-18 22:10:14 UTC,"Change abandoned by Michael Johnson (<email address hidden>) on branch: master
Review: https://review.opendev.org/471682
Reason: This is no longer needed as log offloading has replaced this idea."
1665069,2017-06-21 18:25:02 UTC,"I believe in our meeting topic about this, there was general consensus around using a syslog related method to capture logs, for a variety of reasons.
http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-06-14-20.00.log.html#l-181"
1665069,2017-06-01 18:37:09 UTC,"Yes, we also disable DNS inside the amp for performance reasons."
1665069,2017-06-01 18:38:48 UTC,"Also note, there are two sets of logs with HAProxy, the administrative logs and then the connection tracking logs.  This bug is tracking the connection tracking logs and not the administrative logs."
1665069,2017-06-01 10:16:22 UTC,steps did:
1665075,2017-02-19 23:05:57 UTC,I am marking this as Won't Fix for 2.0 as we are not planning another 2.0.x release.
1665078,2017-02-20 21:19:24 UTC,This is expected behavior:
1665078,2017-02-21 15:07:56 UTC,Ensuring that netplan parses the while file is not the same as the order in which netplan parses individual configuration files.
1665078,2017-02-21 15:10:36 UTC,"Ignore my comment above, I was confused."
1665083,2019-09-16 11:00:08 UTC,Migrated to https://github.com/widelands/widelands/issues/3189
1665102,2017-04-03 15:24:29 UTC,"it is also the case that snap refresh --list does not show new updates on the devmode snaps, which is consistent I suppose, but if it did show them one could know to manually do the refresh."
1665102,2017-04-03 15:20:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665102,2017-02-23 17:48:46 UTC,Ha! Of course I only remember my side of the discussion :)
1665102,2017-02-23 17:06:39 UTC,Thanks for the well thought out explanation.
1665102,2017-02-15 21:56:31 UTC,Hmm... my understanding of the intent was different.
1665102,2017-02-15 20:56:04 UTC,Thanks for quick reply. Documentation is ambiguous on this point and therefore confused me.
1665102,2017-02-15 20:30:13 UTC,Marking as invalid according to Pat McGowan's comment.
1665102,2017-02-15 19:54:19 UTC,"With devmode you always need to use the option:
$ snap refresh  juju --devmode
and they are not auto-updated"
1665102,2017-02-15 22:26:04 UTC,reopening to get some confirmation
1665102,2017-02-23 16:32:34 UTC,"The current behavior was the precise outcome of a very long conversation we (Mark and I) had in Heidelberg, about the subtle properties of such updates. We agreed to block devmode => strict refreshes because we could not get a clear agreement on what was the proper way to treat those updates. Specifically, on refreshes that go from a snap that proposes devmode to one that proposes strict should it:"
1665108,2017-06-23 05:29:31 UTC,"This can be trivially fixed by making the snap use classic confinement, which I'm planning to do for the 5.3.3 release."
1665108,2017-06-30 13:53:46 UTC,"Not going to make it a classic snap after all, so this will need to be revisited."
1665108,2017-11-05 12:23:06 UTC,"Is this related to the fact that I can't access disk folders outside of snap folder, I guess due to sandboxing? This is a very undesirable behavior from the office user perspective."
1665116,2017-03-20 17:20:19 UTC,"Not only cinder-specs, also sahara-specs (sorry for the spam with the bug state)"
1665116,2017-11-29 21:34:33 UTC,"The error seen when running this today, on d42c319eb:"
1665123,2017-02-16 10:21:03 UTC,Unity8 is running under a unity-system-compositor sourced from the host image.
1665123,2017-11-03 15:24:17 UTC,Syncing task from Mir.
1665123,2017-02-27 18:09:06 UTC,"This doesn't seem to be version-related at all.  Even when trying to switch unity8-session to use the mir-libs 0.26.1 snap on an up to date xenial+overlay system, I hit this bug."
1665123,2017-02-16 09:59:49 UTC,"Now that's weird. The ""probing"" and ""loading"" are the same codepath."
1665123,2017-02-16 08:44:33 UTC,Where Mir gets looks for libraries is entirely configurable. If you want it from the snap...
1665123,2017-02-16 07:55:14 UTC,So the state yesterday was:
1665123,2017-02-16 07:51:20 UTC,"The snap contains binaries from .debs, we're not (re)building anything there."
1665123,2017-02-16 01:40:38 UTC,"That's correct. We only noticed (a bit late) that Mir 0.26.0 had broken the graphics platform ABI but failed to bump the soname. This has happened before, and leaving it is worse than fixing it late (in Mir 0.26.1). So we have corrected the ABI level in Mir 0.26.1 to be 12 rather than 11."
1665123,2017-02-16 09:34:14 UTC,We already set:
1665140,2017-06-02 10:30:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665140,2017-02-21 21:44:21 UTC,"> I believe it's the distro's responsibility to ship glib, glibc and vim so that all use the same Unicode version.
"
1665140,2018-04-12 19:28:01 UTC,"FYI, Unicode 9 only adds support for some characters (e.g. U+1F920, 🤠, is correctly marked as wide starting from Unicode 9) but others require an update to Unicode 10 (e.g. U+1F92F, 🤯) to be marked as wide."
1665140,2017-02-17 21:01:07 UTC,"Also note that in gnome-terminals' Profile Preferences, under the Compatibility tab you can choose whether you want ambiguous width characters to be narrow or wide."
1665140,2017-02-17 13:25:00 UTC,"You've reported this bug against Ubuntu 16.04, whereas Unicode 9.0 was released in June 2016. The expected behavior in that distro is hence Unicode 8.0's."
1665140,2017-02-21 14:03:54 UTC,Just for the record:
1665143,2017-02-23 14:26:24 UTC,">  Checking that path [/dev/nvme0n1] and is same as link [nvme-nvme.8086-
> 43564d44343334353030424e34303041474e-494e54454c205353445045444d453430304734-00000001]
"
1665143,2020-12-11 15:03:30 UTC,"marking as invalid for systemd as i believe the bug was in maas, per previous comments."
1665143,2017-04-12 15:37:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665143,2017-02-28 06:22:26 UTC,I applied the patch to /usr/lib/python3/dist-packages/provisioningserver/refresh/node_info_scripts.py on our failing maas and restarted maas-regiond.service (sudo systemctl  status maas-regiond.service).
1665143,2017-02-23 21:07:16 UTC,"> This seems a bit inconsistent to me, for example the symlink for sdb's does
> not include Model/Serial, where as they do for nvme's. That alone is a
> format difference on how the symlinks are being created and which is why I
> was asking, as it seems weird to me.
"
1665143,2017-02-23 17:54:48 UTC,"Please mark this bug critical, as it blocks all integration testing."
1665143,2017-02-23 16:55:26 UTC,"On Thu, Feb 23, 2017 at 9:26 AM, Dan Streetman <
<email address hidden>> wrote:"
1665143,2017-02-23 16:51:33 UTC,"Hi Dan,"
1665143,2017-02-22 23:38:41 UTC,"I've attache a work around path in the bug, but it is an ugly work around. That said, I noticed some strange behavior. Links format are completely different to how the links format is handled for scsi devices:"
1665143,2017-02-27 23:10:56 UTC,I've attached a patch that can be applied in 2.1. https://code.launchpad.net/~andreserl/maas/lp1665143 This should fix the issue. I'd request everybody having this issue to please test it.
1665143,2017-02-22 22:50:30 UTC,This is the script that gathers the block devices. I looked into it and it seems that it is doing the right thing as it is getting the by-id link based on the /dev/nvme* path.
1665143,2017-02-22 22:23:18 UTC,When ssh'ing into the commissioning machine I can see that there are two links to nvme0n1. It seems like the first is the one that MAAS really needs to use. Does the commissioning script need to filter?
1665143,2017-02-22 21:24:26 UTC,https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903
1665143,2017-02-22 21:00:23 UTC,We cannot fix this in 2.1 provided that this requires a migration and we cannot backport migrations. It would be interesting to see what created this and how we can address it.
1665143,2017-02-22 20:38:42 UTC,"I'm seeing the same issue in 2.1.3+bzr5573, with both the default or HWE commissioning kernel."
1665143,2017-02-15 22:16:24 UTC,When commissioning with the HWE kernel the ID_PATH is shorter:
1665143,2017-02-15 22:09:29 UTC,In 00-maas-07-block-devices the Intel NVME device has an ID_PATH which is 115 characters long. We use a Django FilePathField on the BlockDevice model to store the device file path. Django limits the FilePathField to 100 characters by default. The result is being rejected because the file path is currently to long for the field.
1665143,2017-02-15 22:01:10 UTC,"Ok, So the reason for this is that MAAS handles a FilePath of maximum 100 characters. The one being found here is way more than that."
1665143,2017-02-15 21:42:09 UTC,Frmo the logs above:
1665143,2017-02-22 22:59:20 UTC,"Here is the output from running that script.
http://paste.ubuntu.com/24049463/"
1665145,2017-02-17 04:57:52 UTC,This issue was fixed in the openstack/nova 15.0.0.0rc2 release candidate.
1665145,2017-02-16 19:21:21 UTC,"Reviewed:  https://review.openstack.org/434552
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7d0c5998cbb3677d619cb14e6ce1631eab297f34
Submitter: Jenkins
Branch:    stable/ocata"
1665145,2017-02-16 16:15:42 UTC,"Reviewed:  https://review.openstack.org/434533
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b276e84103333c91c32b6ccb229104dd87b8167d
Submitter: Jenkins
Branch:    master"
1665145,2017-04-14 09:23:49 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1665145,2017-02-15 21:57:50 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/434531
Reason: Let's fix this on master first. I'm abandoning this since the change ID doesn't match the one on master."
1665145,2017-02-15 21:53:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/434533"
1665145,2017-02-15 21:51:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/434531"
1665145,2017-02-15 23:03:51 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/434552"
1665148,2017-02-15 21:59:55 UTC,"Forgot to mention.
I just click below the closed GtkExpander and the click-event seems to dive down to the listbox. The listbox pops up."
1665148,2017-02-16 08:23:12 UTC,Screen capture vid attached.
1665148,2018-03-02 13:22:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1665149,2017-02-17 13:29:32 UTC,"Reviewed:  https://review.openstack.org/435085
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=1d0406f0c4b9352b0df2a5b3c2abbc65f86cff4a
Submitter: Jenkins
Branch:    master"
1665149,2017-02-16 19:50:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435085"
1665149,2017-02-16 19:49:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435084"
1665149,2017-02-16 19:22:44 UTC,"Reviewed:  https://review.openstack.org/435066
Committed: https://git.openstack.org/cgit/openstack/charms.ceph/commit/?id=e422e65fc98b60417573ce2a6f10e447a9f7d54f
Submitter: Jenkins
Branch:    master"
1665149,2017-02-16 19:02:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435066"
1665149,2017-02-16 12:00:45 UTC,https://github.com/openstack/charm-ceph-osd
1665149,2017-02-16 12:01:26 UTC,https://github.com/openstack/charm-ceph
1665149,2017-02-16 00:10:15 UTC,I might be crazy but it appears this line has never worked: https://github.com/openstack/charms.ceph/blob/master/ceph/__init__.py#L909.  I'm wondering if we called the ceph auth get-or-create like the get_named_keyring file if that would work.
1665149,2017-02-15 23:15:40 UTC,Bundle which produces this:
1665149,2017-02-15 22:09:48 UTC,This was observed on Xenial-Mitaka but appears to be impacting all mojo spec metal tests.
1665149,2017-02-16 12:59:41 UTC,"Quite strange, it looks like ceph-0 successfully ran the command to create that key:"
1665149,2017-02-17 13:30:58 UTC,"Reviewed:  https://review.openstack.org/435084
Committed: https://git.openstack.org/cgit/openstack/charm-ceph/commit/?id=ea87ae4feb2dd673c979b8610848efcd6dd33cfa
Submitter: Jenkins
Branch:    master"
1665151,2019-05-10 07:54:43 UTC,I found something in   /etc/letsencrypt/options-ssl-apache.conf ...
1665151,2019-06-28 12:32:08 UTC,"Many thanks Thomas !
I was searching for hours why apache did not taking into account my SSL config.
It is because the letsencrypt config was applied before my virtualhost config."
1665151,2018-10-16 15:22:47 UTC,"@Stefan Yes. I'm using Certbot to manage my LE Certs, and Certbot makes those configuration changes automatically. All I'm saying is it would be really useful to have a command / flag that would simply state what directives are taking precedence for configuration, because situations like this arise where some mysterious configuration I had forgotten about took precedence over a global httpd.conf directive. If I could just run a command and it says ""SSLProtocol: Inherited from line 20 in .../httpd.conf"" would be the simplest way to be forwardly agnostic about where or how the server get's configured."
1665151,2019-01-04 14:54:02 UTC,"I can confirm this behaviour on 2.4.37 on two servers. I'm using these directives, and TLSv1.0 is still available"
1665151,2019-02-07 07:57:49 UTC,"BUMP.
Seeing this on 2.4.18 on Xenial"
1665151,2019-03-11 10:12:51 UTC,This is not a bucket for all possible improvement ideas about mod_ssl configurations. That is better discussed on the user/dev mailing lists.
1665151,2019-03-19 10:23:43 UTC,"@David: going through this again, this looks like some intermittent issue with changes ported to ubuntu. And it seems to be fixed now?"
1665151,2019-03-19 15:38:13 UTC,I have the ame issue on Debian 9.8 with apache2 2.4.25-3+deb9u6
1665151,2019-04-12 16:08:13 UTC,... same if I add ECDHE-RSA-AES256-SHA (c014 instead if c013).
1665151,2019-04-12 18:34:36 UTC,"... and two more ciphers which ""break the TLS 1.2-only"" syntax for me:"
1665151,2019-04-15 12:17:59 UTC,"Upstream has closed this bug as Incomplete, so I'm doing the same for Ubuntu. I think part of the problem here is that different people are reporting different underlying causes that lead to similar symptoms. See https://bz.apache.org/bugzilla/show_bug.cgi?id=60739#c25."
1665151,2019-05-10 07:54:57 UTC,I found something in   /etc/letsencrypt/options-ssl-apache.conf ...
1665151,2019-12-04 07:03:54 UTC,I had the same problem - had!
1665151,2019-12-10 08:10:18 UTC,I can confirm I also experienced this issue on the same versions as reported using Ubuntu 18.04 Server (Bionic)
1665151,2019-12-12 22:35:31 UTC,"Confirmed, many thanks Robin!"
1665151,2019-12-17 10:02:46 UTC,"This all sounds interesting.
But since recently the openssl 1.1.1 bump has impacted a lot of things lets re-test with that.
BTW TLSv1.3 might come up in bug 1845263 soon.
I installed apache2 on 18.04 and 20.04 and will test on those which means:"
1665151,2019-12-17 10:04:25 UTC,"I found that on the Debian bug nmap was used, for the sake of being different I tried like:
$ nmap --script ssl-enum-ciphers -p 444 10.253.194.57 | grep TLSv
But the results match what I have seen with testssl.sh"
1665151,2019-12-17 10:07:36 UTC,"And as asked there this might help as well:
$ a2enmod info
$ systemctl restart apache2
$ apache2ctl -t -D DUMP_CONFIG|grep -i ssl
$ a2dismod info # if it hasn't been enabled before"
1665151,2019-12-29 11:39:54 UTC,"So when will a ""solution"" come or is there already one? if so, how? I'm just having a hard time to wrap my head around this.
I didnt have this issue before i did a yearly reset on my server ~3 weeks ago.
The support for TLSv1 & TLSv1.1 seems to end in 3 days and i need help get this solved asap."
1665151,2020-02-16 02:35:09 UTC,This solved my problem - through SSL Labs I was getting B with all the attempts in putting anything - as soon as I updated the options-ssl-apache.conf file BOOM! we got A+ Rating
1665151,2020-02-16 02:35:57 UTC,Comment # 20 fixed my problem - people who disqualified it immediately need to pay attention!
1665151,2020-02-16 02:37:08 UTC,comment # 20 fixed the issue by updating the LetsEncrypt options file.
1665151,2020-02-16 02:38:02 UTC,Comment # 20 below fixed the issue - review the letsencrypt changes to the ssl.conf file and apache2 startup.
1665151,2020-08-17 22:21:32 UTC,I could disable TLS 1.0 and 1.1 and only enable TLS 1.2 + 1.3 by doing this
1665151,2020-11-07 07:56:16 UTC,Apache + Debian here. I just run grep -rnw '/etc' -e 'SSLCipherSuite' and found that /etc/apache2/mods-available/ssl.conf was overriding even the /etc/letsencrypt/options-ssl-apache.conf file.
1665151,2018-10-04 07:58:25 UTC,"@Aaron C: Let's Encrypt has nothing to do with your server configuration. You probably meant a config addition by an LE client, such as certbot?"
1665151,2018-10-02 01:22:04 UTC,"While not relating to the discussion of certain SSLProtocol and SSLCipherSuite combinations halting desired SSLProtocols, I did want to add that I had an issue where Let's Encrypt was holding my desired changes back."
1665151,2019-04-12 14:59:44 UTC,I have a similar problem with Ubuntu 18.04 (Apache 2.4.39 + openssl 1.1.0g) and it maybe sheds some light into this.
1665151,2018-08-24 08:58:52 UTC,"Hi, unfortunately i cannot provide a minimal configuration."
1665151,2017-02-16 15:15:34 UTC,Changes in SSLProtocol seem to be ignored.
1665151,2017-02-16 15:16:07 UTC,Upstream bug opened...
1665151,2017-02-16 15:41:44 UTC,"Setting SSLProtocols to -all produces expected behavior, which is an error about no protocols."
1665151,2017-02-16 15:43:48 UTC,The following also works oddly.
1665151,2017-02-17 09:20:19 UTC,"Thanks for your report David, I added the upstream bug to the tracker so that this bug automatically gets updates on its status."
1665151,2018-08-30 11:34:56 UTC,Somehow this has been fixed. Maybe a side effect of other fixes.
1665151,2017-02-26 15:56:08 UTC,This seem to have changed somewhere between 2.4.18 + 2.4.23 as setting SSLProtocol use to be honored.
1665151,2017-02-27 15:04:56 UTC,https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1665151 - related Ubuntu bug ticket.
1665151,2017-02-27 15:05:40 UTC,"Be great if someone from Ubuntu could verify this problem + update the upstream bug, so this problem can be resolved."
1665151,2017-03-14 17:23:49 UTC,"I have tested this with Apache 2.4.25 and OpenSSL 1.0.2k, with global settings and also with virtual host settings."
1665151,2017-03-16 11:36:54 UTC,The problem seems to be an interaction between the Cipher List + SSLProtocol.
1665151,2017-03-16 12:48:42 UTC,"(In reply to David Favor from comment #6)

> The problem seems to be an interaction between the Cipher List + SSLProtocol.
>
> Depending on setting of Cipher List SSLProtocol seems to work or be ignored.
>
> These settings disable TLSv1.0
>
> # support old Android phones
> SSLProtocol All -SSLv2 -SSLv3 -TLSv1
>
> # Force using custom cipher list
> SSLHonorCipherOrder on
>
> Define sslCiphers
> -ALL:!ADH:!aNULL:!EXP:!EXPORT40:!EXPORT56:!3DES:!eNULL:!NULL:!RC4:!DES:!MD5:!
> LOW
> Define sslCiphers
> ${sslCiphers}:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-
> AES256-SHA:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-
> SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA
> SSLCipherSuite ${sslCiphers}
>
> Other sslCiphers settings cause SSLProtocol to be ignored.
>
"
1665151,2017-04-03 16:22:30 UTC,I have similar issue. Whatever I set in SSLProtocol it's ignored.
1665151,2017-02-26 15:44:39 UTC,You're welcome.
1665151,2017-04-03 16:39:18 UTC,"Fix:

> I CANNOT find a way to activate TLSv1.1, with or without TLSv1. All the time, only TLSv1.2 (I tried a lot of different ciphers suite).
"
1665151,2017-04-03 16:52:57 UTC,"Per my other comment above, it appears SSLProtocol is strongly effected by SSLCipherSuite list."
1665151,2017-04-03 17:06:44 UTC,"The SSLCipherSuite seems has no effect on the protocol my side.
Whatever I put :"
1665151,2017-04-03 18:46:54 UTC,"I'm also unable to reproduce. httpd 2.4.25, OpenSSL 1.0.2g -- the protocols are honored correctly with the example ciphersuite lines that have been given in this bug."
1665151,2017-04-04 17:35:31 UTC,"Well, my bad... After trying to reproduce it on a dockerized version, I found I add a false config hidden....."
1665151,2018-04-18 16:08:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665151,2018-05-15 15:10:00 UTC,"The letsencrypt setup process adds the following line, which
includes SSLProtocol and SSLCipherSuite setup.
Quite annoying as a grep for SSLProtocol will not find it."
1665151,2018-05-15 17:09:49 UTC,The ASF HTTP Server project has nothing to do with letencrypt distributed solutions. Comment #14 does not enhance this report.
1665151,2018-05-16 14:38:06 UTC,"I was not entirely clear.
The letsencrypt configuration that gets installed will override any
SSLProtocol and SSLCipherSuite commands with their config."
1665151,2018-08-23 07:36:35 UTC,"Hi, i can confirm the issue.
I have searched all configs and VHosts no overides are made it should work but
nmap --script ssl-enum-ciphers -p 443 IP | grep TLSv
returns TLS1.0,  TLSv1.1"
1665151,2018-08-23 11:39:29 UTC,"(In reply to A.Sklepas from comment #17)

> Hi, i can confirm the issue.
> I have searched all configs and VHosts no overides are made it should work
> but
> nmap --script ssl-enum-ciphers -p 443 IP | grep TLSv
> returns TLS1.0,  TLSv1.1
>
> I also investigated the claims about letsencrypt:
> Read this topic:
> https://community.letsencrypt.org/t/how-to-disable-tlsv1/49117/4
> On some systems the options-ssl-apache.conf seems to be included in the
> virtual hosts.
> ""Include /etc/letsencrypt/options-ssl-apache.conf""
>
> Anyway not in my case plus i have disabled the options in that file to be
> certain.
> PS. Why are we waiting to fix this one? I do see servers that have disabled
> TLS1 btw...
>
>
> My info: Apache/2.4.33
"
1665152,2017-02-16 00:28:30 UTC,"The attachment ""unescaped-left-brace-warning-fix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1665152,2017-06-30 03:09:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665152,2017-02-15 22:17:50 UTC,"Appearently it's still working, but it always prints this message."
1665153,2017-02-15 22:58:36 UTC,"N.B., this is also related to:
https://bugs.launchpad.net/juju/+bug/1444066"
1665153,2017-02-15 23:18:53 UTC,It prints out a big warning.
1665153,2017-02-16 00:49:28 UTC,"@Ian myself, I agree that it shouldn't be an error per what you described. However, I don't really think that having a warning then proceeding with adding the attributes anyway is really useful. I would preferred to be given the ability to abort or continue. Plus it is a bit misleading that it gives this warning then proceeds to add anyway which was surprise to me. User could easily think that they set agent-stream when in fact they created a new field agen-stream. That doesn't mean it's not their error, but seems like a good option to provide."
1665153,2017-02-20 00:16:44 UTC,I think a prompt is a good idea
1665153,2017-02-20 00:17:53 UTC,"Prompting user to confirm unknown configuration keys would be very user-friendly.
Thank you, Larry!"
1665158,2017-02-15 22:59:31 UTC,"Just found a workaround: If I copy and paste the entire schematic into a new file, the problem goes away. The marker list goes back to the default set without duplicates. Copy-pasting is smooth again. Interestingly, the file size drops from 3 MB to ~250 KB, indicating that some sort of memory build up is an issue (or can become one)."
1665158,2017-02-15 23:45:14 UTC,"You can also do ""file->cleanup document"""
1665158,2017-02-16 00:35:54 UTC,touché. That works better. Thanks!
1665158,2017-07-31 19:33:11 UTC,File > Cleanup does NOT work for me to solve the issue!
1665158,2019-01-18 17:57:28 UTC,I'm hit by this bug when I *clone* a simple Bézier line with an end marker.
1665160,2017-04-17 22:11:14 UTC,I should also note that the test runs as the ubuntu user whish does has sudo access to the whole machine.
1665160,2019-07-07 22:29:00 UTC,"This failure has not been due to Juju but rather the setup of the CI environment. We have not seen any consecutive failures of this nature, so the issue has been resolved."
1665160,2017-04-20 04:14:44 UTC,With Chris's help we got the tests to get past the D-Bus errors on Zesty by creating a file /etc/polkit-1/localauthority/50-local.d/manage-units.pkla on the test system with the following contents:
1665160,2017-04-20 02:00:43 UTC,"Anastasia asked me to take a look at this.  I'm still not sure what the underlying cause is, but here is some of what I've discovered so far."
1665160,2017-03-22 19:13:40 UTC,Is the unit test messing with the services on the host system? I hope not.
1665160,2017-04-17 21:58:24 UTC,These tests are run across different archs using the same script (the same user etc.). Nothing has changed in how it's run but we're only seeing this failure on Zesty.
1665160,2017-02-27 23:09:14 UTC,Marking as Won't Fix for 2.1.1 as it requires a bit more investigation and we are focused on 2.2.
1665160,2017-02-27 12:22:13 UTC,"@Curtis,
According to comment # 1, dbus on zesty seem to want to run interactive authentication. This does not seem to be Juju's responsibility."
1665160,2017-02-23 22:09:39 UTC,The cause of the worker failing is this:
1665160,2017-03-02 17:00:35 UTC,It is not dbus which is asking for authentication here. That's not really a thing that happens.
1665166,2017-02-16 06:53:03 UTC,"Based on the description, this is likely one of the symptoms of
* Bug #1450675 “Text is displayed cut in half (rev >= 12488)”
* Bug #1283194 “Text rendering cuts off trailing character (depending on zoom level) (rev >= 12488)”
See e.g. the tearing documented in the video attached in comment 11 of bug #1450675."
1665187,2017-08-28 08:15:54 UTC,"Change abandoned by Liu Yang (<email address hidden>) on branch: master
Review: https://review.openstack.org/434598"
1665194,2017-06-08 11:58:21 UTC,working on this
1665194,2018-01-12 19:03:16 UTC,Unassigning due to no activity for > 6 months.
1665196,2017-02-16 03:02:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1665196,2017-02-16 05:04:04 UTC,"I retested to make sure this bug is valid on my hardware. Apparently it would seem there is a time limit for entering the Wi-Fi password, if the Wi-Fi password is entered within the time limit the Wi-Fi password is accepted otherwise password must be entered and saved from the Edit Connections GUI."
1665201,2017-02-24 11:41:41 UTC,some guys told me it due to bugs in qt.He told me I could use this script to launch Octave-gui without crash.
1665201,2018-08-29 09:42:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665203,2017-09-01 16:17:00 UTC,Unassigning due to no activity for > 6 months.
1665216,2020-06-29 09:52:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665248,2018-01-25 09:33:31 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3643
1665254,2019-09-16 18:01:06 UTC,Migrated to https://github.com/widelands/widelands/issues/1668
1665263,2017-02-23 02:47:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437222"
1665263,2017-03-03 15:04:19 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441171"
1665263,2017-03-10 19:29:53 UTC,"Reviewed:  https://review.openstack.org/437222
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9ac9531fb3259fe83642dce92d0d1901d0f067e
Submitter: Jenkins
Branch:    master"
1665263,2017-03-14 12:29:41 UTC,"Reviewed:  https://review.openstack.org/441171
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0adc5bf0a4209657180df778ea6b95597fdc9ac0
Submitter: Jenkins
Branch:    stable/ocata"
1665263,2017-03-15 11:15:34 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1665263,2017-04-14 09:23:10 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1665264,2017-03-23 17:01:15 UTC,I can confirm the bug description.
1665264,2017-04-19 15:53:49 UTC,Can confirm this with DHCP instead of BOOTP as well:
1665264,2017-03-24 09:07:31 UTC,"I have tried this, too. I added the option ""ignore-client-uids on;"" and deleted the lease file.
After restarting the server I could boot several targets. I also don't know if this is a bug or not."
1665264,2017-03-23 16:24:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665264,2017-03-23 19:51:29 UTC,"I dug a little deeper and could see that in our case the devices all use the same uid in the boot request, thus receiving the same ip address via dhcp.
I guess the failing bootreply comes from the still memorized mac address of the device before."
1665281,2017-02-20 10:22:52 UTC,"Note to reproducers, at least on kate it only happens on second drag, cause is:
 a) qtubuntu doesn't implement drag&drop
 b) default drag&drop implementation uses a QRasterWindow that crashes https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1665705"
1665284,2020-03-22 14:10:03 UTC,I was working on this a little bit. It looks like it is shuffling only certain tracks in the playlist - why it is necessary to skip certain ones?
1665284,2017-03-03 17:05:53 UTC,"I take this bug, this bug seems to be an easy for me, I feel it interesting, i will try to solve it."
1665284,2017-03-09 03:21:53 UTC,Pull requested at https://github.com/mixxxdj/mixxx/pull/1205
1665284,2018-09-20 18:04:12 UTC,"Due to lack of progress, marking Triaged and clearing assignee. Feel
free to revert if it is in fact still in progress :)."
1665284,2019-10-01 19:13:11 UTC,"Is this still open? I'm new to mixxx, but it seems like the old PR could be fixed up to work."
1665284,2019-10-01 19:32:27 UTC,"It is currently closed, mainly because it has stalled.
If you like to continue the work I think it is a good idea to open a new one from the scratch and use the old one and the comments for inspiration.
Thank you in advance."
1665284,2019-10-01 19:35:27 UTC,The old PR didn't meet our quality requirements and was unfinished. I recommend starting a new approach at the current version.
1665284,2019-10-01 20:05:35 UTC,"Ah I hadn't seen that page before, thank you! I'll check it all out"
1665284,2020-03-22 15:36:30 UTC,"The shuffling is started here:
https://github.com/mixxxdj/mixxx/blob/9ea985dd613b4b34679888820f7367dd258f5447/src/library/autodj/autodjprocessor.cpp#L213"
1665289,2017-06-13 00:02:36 UTC,Unity 8 is discontinued.
1665290,2017-02-17 02:07:55 UTC,Sounds like you're using Unity8 rather than Unity7. Is that correct?
1665292,2017-02-16 14:11:06 UTC,"Thanks Amos. This is very helpful. Erik, I think my requests comment 2 still stand, except that instead of doing a bisection you could just try applying that patch to the squid version in Xenial instead to see if that fixes it. Or if you want to try things in a different order, that's fine. I just want to identify exactly what is the minimal change that is confirmed to fix your problem."
1665292,2017-02-16 13:52:53 UTC,"FYI: If it was upstream then I suspect it is most likely this upstream change, none of the others had much performance gain in upstream tests:
 http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-14061.patch"
1665292,2017-02-16 10:28:32 UTC,Thank you for your report and helping to make Ubuntu better.
1665296,2017-02-17 01:54:36 UTC,Looks like a bug in the ubuntu-terminal-app snap. It's running Xmir instead of rendering to Mir natively...
1665296,2017-03-21 14:48:46 UTC,dinamic: is that resolved for you now?
1665297,2017-02-16 11:13:36 UTC,You've taken over gnomeradio?
1665297,2017-02-16 11:40:12 UTC,"Yes, I took gnomeradio but new application gnome-radio is almost totally rewritten.
I'm going to talk to GNOME about this, but I do not know which is the best way to do this.
Now gnomeradio is moved in archive in GNOME git: https://git.gnome.org//browse/archive/gnomeradio"
1665297,2017-02-16 12:06:32 UTC,I recommend introducing yourself on https://mail.gnome.org/mailman/listinfo/desktop-devel-list
1665297,2017-02-16 23:55:05 UTC,*** This is an automated message ***
1665311,2017-02-28 11:52:49 UTC,fuel-nailgun specs now do not contain any fuel-nailgun library. moving state back to Confirmed
1665311,2017-03-21 09:44:57 UTC,"Change abandoned by Alexander Kislitsky (<email address hidden>) on branch: master
Review: https://review.openstack.org/438938
Reason: We don't need to distribute nailgun as package to the slave nodes."
1665311,2017-02-28 12:12:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438938"
1665311,2017-02-22 12:39:05 UTC,Fuel package is already built but placed here: http://mirror.fuel-infra.org/mos-repos/ubuntu/10.0/pool/main/f/fuel-web/. Moving state to Invalid.
1665311,2017-03-24 16:36:38 UTC,"Reviewed:  https://review.openstack.org/448092
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=746fae6e0a6b6625da6f548f0d168c742497b558
Submitter: Jenkins
Branch:    stable/newton"
1665311,2017-02-17 13:42:48 UTC,"Moreover, fuel-nailgun debian packages are already in our repos."
1665311,2017-02-17 13:03:50 UTC,This is not a bug but feature request. Please file Jira epic and have it through product mgmt process.
1665311,2017-03-21 13:32:02 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/448092"
1665311,2017-02-22 11:50:29 UTC,This change should be done in scope of working on the epic PROD-8683
1665311,2017-03-21 13:53:24 UTC,"Reviewed:  https://review.openstack.org/438938
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=2f522172ce2a7eaa251a742079dadb67aa0ec900
Submitter: Jenkins
Branch:    master"
1665312,2017-03-13 17:48:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665312,2017-03-13 15:15:28 UTC,It does seem to be a gtk bug. A workaround is here: https://launchpad.net/~attente/+archive/ubuntu/gtk-mir
1665312,2017-02-28 14:30:31 UTC,"Cannot reproduce with miral-app: so probably not miral, mir or gtk"
1665312,2017-02-28 10:17:30 UTC,"Confirmed, although I'm not sure if this is GTK or Mir/MirAL at fault."
1665312,2017-02-17 07:44:50 UTC,"the apps are running native, i can tell just by resizing the window :("
1665312,2017-02-17 01:39:23 UTC,Are you able to tell if the apps are running native GTK-on-Mir and not using Xmir?
1665313,2017-02-16 11:53:36 UTC,Will it get removed if you type /handlechanges ?
1665316,2019-09-19 12:02:41 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1665321,2017-02-17 03:41:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435213"
1665322,2017-04-20 15:28:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665322,2017-06-01 08:41:13 UTC,"I reported the same problem in #1682104, another way to work around this is to use the sudo version in the release version of 16.04, 1.8.16-0ubuntu1. Would be very nice to get this resolved since we cannot patch the sudo package right now in our systems."
1665327,2017-02-16 12:54:12 UTC,What version of duplicity?  Which OS?  Do you run clean automatically?
1665327,2017-02-16 16:55:18 UTC,duplicity 0.7.06-2ubuntu2 / Ubuntu 16.04
1665329,2017-02-16 12:32:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1665329,2017-02-16 18:21:00 UTC,Confirming this occurs on Ubuntu 16.04 and 16.10.
1665329,2017-02-28 14:05:56 UTC,So this is a proposed workaround for virtual machines that don't correctly implement EFI variables?
1665329,2017-02-28 14:52:57 UTC,@Phillip Susi
1665329,2017-03-03 19:53:22 UTC,"AFAIK, startup.nsh is entirely up to the user and optional -- not something that OS installers are normally supposed to mess with.  The OS is supposed to make calls to the EFI firmware to register its boot loader in the EFI variables and that tells the firmware what to boot, but virtual machines have no persistent flash memory to save those variables, so that is where that breaks down."
1665329,2017-03-03 19:54:32 UTC,"For that matter, even having an EFI shell installed that would have the ability to interpret startup.nsh is optional and not something that any real hardware I have seen comes with."
1665329,2017-03-04 11:39:18 UTC,@Phillip Susi
1665329,2017-05-20 15:33:08 UTC,I too have issue with this. HP elitebook 745 g3 installation with customer partitioning and luks (kubuntu 16.04.2). after installation i get dropped to initramfs and error about not able to reach root volume. it didn't ask for luks password.
1665329,2017-05-22 13:26:35 UTC,That is not related to this bug report Djordje.
1665338,2017-02-17 01:45:36 UTC,I think what you're asking for is a GTK theme that makes GTK apps look more like Unity8?
1665341,2017-09-01 16:17:04 UTC,Unassigning due to no activity for > 6 months.
1665341,2017-09-01 19:45:17 UTC,"scope checks should be done in code, not by adding project_id:%(project_id)s in policy files. That said, there are at least a couple things that need to happen here:
1) we need to start doing proper scope checks in the code
2) target data needs to be filled to enable other types of checks from policy"
1665352,2017-02-16 14:00:06 UTC,This change was made by a bot.
1665353,2017-02-20 11:14:41 UTC,"Marking as Incomplete, please attach diagnostic snapshot."
1665353,2017-02-27 08:31:02 UTC,"Problem is that there is not enough to just include ssl-related tasks to the plugins. All the ssl-related tasks have running scope with role tags, like (excerpt from ssl-keys-saving):"
1665353,2017-03-22 07:27:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448422"
1665353,2017-03-22 07:29:52 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/448423"
1665353,2017-03-23 08:57:40 UTC,"Reviewed:  https://review.openstack.org/448422
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=22d5c26b3b48fd051c553b0d2b55b9d28d96e0d1
Submitter: Jenkins
Branch:    master"
1665353,2017-03-23 09:19:34 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/449017"
1665353,2017-05-16 01:30:22 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/449017
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1665353,2019-12-18 17:22:56 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/448423
Reason: This repo is retired now, no further work will get merged."
1665355,2019-09-16 07:57:59 UTC,"Finally, I think I found the cause (as the problem appeared on Debian as well): The object file pythongdl.cpp.o was empty, and all functions (including initGDL and PyInit) were called from the library (libgnudatalanguage0) linked to. On gcc-9 (and probably on Ubuntu's gcc), the ""as-needed"" flag is implicite in the linking step, which prevents unneded libraries from being linked. Therefore, the symbols can't befound anymore."
1665355,2018-02-28 20:25:32 UTC,"I must say that this is mystic to me. When I do check the shared library, it looks weird:"
1665355,2018-02-28 17:44:41 UTC,"dino99: 17.04 might have reached end of life, but this issue is still present and reproducible. I was just able to verify it with gnudatalanguage 0.9.7-6 on Ubuntu bionic, so setting this back to Confirmed."
1665355,2017-02-24 21:36:40 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1665355,2018-02-28 09:35:23 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1665359,2017-02-16 14:03:45 UTC,"Stacktrace:
 #0  0xf778cc89 in ?? ()
 No symbol table info available.
 #1  0x00000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0  0xf778cc89 in ?? ()
 #1  0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()"
1665359,2017-03-22 18:36:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665359,2017-04-11 17:30:27 UTC,"StacktraceTop:
 raise () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/lib/i386-linux-gnu/libc.so.6
 abort () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/lib/i386-linux-gnu/libc.so.6
 g_test_trap_subprocess (test_path=0x83 <error: Cannot access memory at address 0x83>, usec_timeout=17794492649015600712, test_flags=(G_TEST_SUBPROCESS_INHERIT_STDERR | unknown: 4288713752)) at ../../../../glib/gtestutils.c:2965
 syscall () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/lib/i386-linux-gnu/libc.so.6
 ?? () at ../../../../glib/gthread-posix.c:1380 from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/lib/i386-linux-gnu/libglib-2.0.so.0"
1665363,2017-02-16 14:26:05 UTC,"StacktraceTop:
 panel_indicator_entry_accessible_ref_child (accessible=0x5559f7e3b0d0, i=<optimized out>) at ./services/panel-indicator-entry-accessible.c:296
 append_children (traversal=0x5559f7a0e2a0, accessible=0x5559f7e3b0d0) at accessible-cache.c:233
 add_pending_items (data=<optimized out>) at accessible-cache.c:285
 ?? ()
 ?? ()"
1665363,2017-03-10 13:59:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665371,2017-03-02 01:28:14 UTC,gnome-terminal is an unusual app with a server and a client. I think it might be easiest if the Relaunch button would not show for crashes related to gnome-terminal.
1665375,2017-04-13 13:46:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665384,2020-10-14 17:57:30 UTC,This bug was fixed in the package ubiquity - 20.10.11
1665384,2017-02-16 16:02:12 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1665384,2017-02-16 18:56:14 UTC,This is most likely a ubiquity bug; where the connection is created with the wrong permission settings.
1665385,2017-02-16 16:02:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1665389,2020-02-11 14:45:33 UTC,Can you still reproduce this issue with the latest version of QEMU (v4.2)?
1665389,2017-02-18 08:17:06 UTC,Nested is currently supported only with -cpu host. Kernel 4.9 has the necessary support but QEMU doesn't.
1665389,2017-02-20 15:00:13 UTC,"> Yes, I mean '-cpu host' in the bare metal. There is no workaround; it worked by chance and it triggered other hard to find bugs.
"
1665389,2020-04-12 04:17:31 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1665389,2017-02-20 14:28:06 UTC,"Yes, I mean '-cpu host' in the bare metal.  There is no workaround; it worked by chance and it triggered other hard to find bugs."
1665389,2017-02-16 22:10:11 UTC,"Hi Dave, thanks for looking into this."
1665389,2017-02-17 20:31:34 UTC,"   kvm_msr_entry_add: @8 index=9e value=30000
   kvm_msr_entry_add: @9 index=d90 value=0
   kvm_msr_entry_add: @10 index=c0000083 value=0"
1665389,2017-02-16 18:58:49 UTC,"Hi Nadav,
  Can you clarify what the host and L1 kernels are please?"
1665389,2017-02-19 07:42:29 UTC,"> Nested is currently supported only with -cpu host. Kernel 4.9 has the necessary support but QEMU doesn't.
"
1665395,2019-05-16 14:34:14 UTC,"Bug 1829295 may be a duplicate of this, but I'm not certain."
1665395,2019-05-16 16:35:38 UTC,"Hello Jeff,"
1665395,2019-05-16 18:18:50 UTC,"Thanks for the example, Josh.  Just wanted to note the code I shared in bug 1829295 would address this use case."
1665396,2017-04-28 06:29:29 UTC,"Paul, that is correct. As long as there is a version of DPDK checked out in the third_party/dpdk directory, the vrouter-dpdk binary will get built. For juniperopenstack, we use DPDK 2.1 (soon 17.02)."
1665396,2017-02-16 16:28:52 UTC,"Review in progress for https://review.opencontrail.org/28860
Submitter: Cedric Hnyda (<email address hidden>)"
1665396,2017-02-16 16:41:27 UTC,"Review in progress for https://review.opencontrail.org/28861
Submitter: Cedric Hnyda (<email address hidden>)"
1665396,2017-04-26 20:47:46 UTC,Is the Won't Fix status because juniperopenstack is the wrong project but this will be fixed in the opencontrail project?
1665397,2017-02-27 11:01:22 UTC,"Change abandoned by Andreas Scheuring (<email address hidden>) on branch: master
Review: https://review.openstack.org/435000
Reason: Andy talked to the Docs team and for the current release we go with the RTD approach"
1665397,2017-02-22 16:52:38 UTC,"Change abandoned by Andreas Scheuring (<email address hidden>) on branch: master
Review: https://review.openstack.org/434992
Reason: Will not follow up that path for now - keep things as is on RTD"
1665397,2017-02-16 16:34:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435000"
1665397,2017-02-21 13:03:51 UTC,Andy discussed this with Anne Gentle and Alexandra Settle - we keep the RTD openstack design including the logo.
1665399,2017-02-16 22:01:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665400,2017-02-16 17:22:13 UTC,Confirming and adding a link to a recent IRC discussion:
1665401,2017-04-28 08:56:10 UTC,"Also, the zhmcclient has always had support for automatic initial logon and re-logon upon expiration of an HMC session. We did not test whether the re-logon works across an HMC reboot, though."
1665401,2017-07-04 11:46:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480158"
1665401,2017-02-21 15:14:57 UTC,"Doesn't block the release, but we might want to backport it when it's done in Pike."
1665401,2017-02-21 15:22:40 UTC,That's a design we haven't talked about at the beginning. We need to do that early in Pike.
1665401,2017-04-28 08:53:44 UTC,"zhmcclient v0.11.0 introduced connection retries. So if the zhmcclient now raises a ConnectionError, that means these retries are exhausted. The connect retries and connect timeouts can be configured using a new RetryTimeoutConfig class. See http://python-zhmcclient.readthedocs.io/en/latest/general.html#session"
1665401,2017-07-04 09:40:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/480097"
1665402,2017-04-03 08:36:43 UTC,"@Gunnar: You are right. Clicking on ""Disabled"" opens the window to record the shortcut."
1665402,2017-03-28 15:57:10 UTC,"On 2017-02-23 21:34, Vej wrote:

>  * Select your new entry
>
> What happens: The edit menu opens to edit the name and command
>
> What should happen: The design changes indicating that the shortcut
> is recorded.
"
1665402,2017-04-03 10:23:19 UTC,"I agree that there is room for improvement of the design. More intuitive (IMO) would be that it was just highlighted when you click it, as for the predefined shortcuts, and that the window for editing is opened when you double click or right click."
1665402,2017-02-23 20:34:39 UTC,I can reproduce this using xenial 16.04 with the german translation.
1665408,2017-02-17 14:27:37 UTC,Yes.
1665408,2017-02-17 14:16:23 UTC,Did you use exactly the same command at that time?
1665408,2017-02-17 15:28:04 UTC,"So you created a new prefix with
  WINEARCH=win32 WINEPREFIX=/home/john/.wine32-test wine wineboot"
1665408,2017-02-16 18:13:53 UTC,"With these commands you were still using ~/.wine.  You have to either export WINEPREFIX or specify it for every command.
Further I think I've seen Wine complaining about ""~"" in the past, so maybe either use $HOME or the path directly."
1665408,2017-02-17 12:37:29 UTC,"No problem with your suggestion. However, 2 hours later it did the same
again!"
1665411,2017-03-04 03:42:05 UTC,"Note here that we probably shouldn't be showing the suggestion at all, until 2FA is enabled for non-canonicalers: https://bugs.launchpad.net/canonical-identity-provider/+bug/1636645"
1665411,2017-03-04 19:11:05 UTC,I agree that we shouldn't be showing the suggestion at all in Snapcraft until it's possible for people to actually do what it suggests. It just causes confusion otherwise.
1665411,2017-03-05 20:19:22 UTC,"snapcraft is following the UX guidelines drafted in Heidelberg with sabdfl, store and snapcraft folks. This is a store bug or in any case we can remove the messaging from snapcraft itself."
1665416,2017-09-11 10:20:40 UTC,"This will become slightly more important once the classic builder support is added, which is planned for 1.2."
1665416,2018-07-20 11:39:12 UTC,This is slightly lower priority now since we do have those covered more or less in the manpage of ubuntu-image.
1665424,2017-02-16 19:31:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665424,2017-02-16 21:01:55 UTC,do you want to proposed a patch for this? I'm mostly sure there is already an LP bug open for this...
1665445,2017-02-21 08:26:40 UTC,I can't view the screenshots (I get 401 errors). Can you attach the Fuel diagnostic snaphot?
1665445,2017-03-01 11:50:32 UTC,"Hello, I haven't timmy diag snapshot. Pictures above are all that I've stored."
1665447,2017-02-16 20:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1665447,2017-02-16 20:31:59 UTC,"Leann,"
1665447,2017-02-17 14:11:32 UTC,"This is a known problem with cross compiling. Mainline packages are ""best"" effort. Fortunately this does not happen on builders native to the architecture."
1665447,2017-02-23 21:48:39 UTC,[ Installing debs on ppc64el works ]
1665447,2017-02-23 21:51:21 UTC,[ Fixing fixdep - from x86_64 to ppc64el ]
1665447,2018-11-05 12:06:36 UTC,This continues to be a issue on recent kernel:
1665447,2018-11-05 19:41:15 UTC,"The mainline builds are all cross-built rather than native
built. Binaries like fixdep etc are used by the build process, and since its a
build on amd64 those binaries are complied for amd64. It is very resource
intensive to build these unsupported kernels native for each architecture."
1665447,2019-07-06 14:45:21 UTC,"I know that these mainline builds are unsupported in any way, but there have been some efforts to quickly patch this problem for cross-compiling."
1665449,2018-01-31 05:23:02 UTC,"this track the versioned notification transformation task of all projects: https://etherpad.openstack.org/p/community-goals
see the part: 'Convert from legacy to versioned notifications'"
1665449,2019-06-05 13:42:53 UTC,Matt is correct in #9
1665449,2018-05-03 22:29:45 UTC,"Just deployed a fresh cloud with charms 18.02, Ceilometer and Gnocchi.  Nothing is listening to versioned_notifications.info and so the queue keeps growing."
1665449,2019-06-05 13:32:31 UTC,"Correction for comment 8, there is no notification_format value of ""legacy"", I think gibi meant ""unversioned""."
1665449,2018-01-31 05:18:39 UTC,thanks gordc for this track in ML.
1665449,2018-05-04 10:56:32 UTC,If the deployment only consumes nova legacy notifications then I suggest to set notification_format to 'legacy' in the nova.conf [1]. This will make sure nova only emits the legacy notifications and not the new versioned ones.
1665449,2017-12-14 23:20:27 UTC,I can confirm the problem:
1665449,2017-06-19 15:00:21 UTC,this is the point of this entry. it's a placeholder that anyone can work on.
1665449,2017-03-20 14:00:25 UTC,is ceilometer going to support this? seems there is no consumer for versioned_notfication pushed by nova.
1665449,2018-01-30 16:27:13 UTC,we can track coverage here: http://burndown.peermore.com/nova-notification/
1665452,2017-02-16 21:02:51 UTC,If that's anymore help ....
1665452,2017-12-07 08:15:46 UTC,I also have the same problem.
1665452,2017-12-18 21:38:04 UTC,"I'm having a similar issue, but I don't get any error messages.
See Nautilus bug 1738868: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1738868"
1665453,2020-11-09 08:47:46 UTC,"Hello,
both 4.8 and Yakkety have all reached their EOL, thus I am closing this bug.
Thanks"
1665462,2017-02-16 23:01:56 UTC,"Likely related to or duplicate of earlier report
* Bug #1416008 “Surface Pro 3 pen not recognized as having pressure (Win10 Tech Preview)”
  https://bugs.launchpad.net/inkscape/+bug/1416008"
1665462,2017-02-17 10:34:50 UTC,"Maybe related, I saw it, still the Pen could be different and the system sure is, it is an old report. If mine is redundant I can delete it."
1665462,2017-06-24 09:47:06 UTC,I had the same problem with my 2 in 1 using the microsoft pen
1665467,2018-07-31 19:02:28 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1665470,2017-02-17 21:06:47 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1665470,2017-02-24 22:09:26 UTC,"Hi,"
1665470,2017-02-16 22:00:12 UTC,This change was made by a bot.
1665472,2017-02-16 22:50:28 UTC,This issue appears due to the conflict between packages Percona-Server-shared-56 and mysql-community-server-5.7.17-1.el7.x86_64 as Percona-Server-shared tries to replace it.
1665472,2017-02-16 23:12:28 UTC,If that is the solution then it should be added in the manual? Otherwise a regular mysql user wouldn't have any idea how to work around it unless they stumble upon this bug report :)
1665472,2017-02-17 00:35:50 UTC,"By default, cent7 ships with mariadb-libs-5.5.52-1.el7.x86_64"
1665472,2017-02-17 07:02:23 UTC,"Ok, I just tested this on a clean CentOS 7 VM, there is no mariadb/percona or mysql packages:"
1665472,2018-01-20 07:50:37 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1425
1665485,2017-02-19 23:08:34 UTC,Error bubbling up to the user would indeed be very helpful \o/
1665495,2017-02-23 18:56:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437558"
1665495,2017-02-23 02:22:01 UTC,"Reviewed:  https://review.openstack.org/437053
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=96dc965381c4ba7915c66d6939ad4140cebfa06c
Submitter: Jenkins
Branch:    master"
1665495,2017-02-25 16:17:25 UTC,"Reviewed:  https://review.openstack.org/437558
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=20ba3174bbf33f0a33d934d432401cb0136a50fc
Submitter: Jenkins
Branch:    master"
1665495,2017-02-22 16:24:49 UTC,"Reviewed:  https://review.openstack.org/436538
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=d56535d4d349cd85965c6035904c5b059ca0685c
Submitter: Jenkins
Branch:    master"
1665495,2017-02-21 20:41:41 UTC,"Reviewed:  https://review.openstack.org/436561
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=e5068ec46aa7bb6b1738b8a64c29e44307f4ba98
Submitter: Jenkins
Branch:    master"
1665495,2017-02-22 18:25:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437053"
1665495,2017-03-09 18:42:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443931"
1665495,2017-03-11 15:17:16 UTC,"Reviewed:  https://review.openstack.org/444438
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=e840a8e7cc8b9727461cd21432b55dc5c927559f
Submitter: Jenkins
Branch:    master"
1665495,2017-03-09 22:31:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443989"
1665495,2017-03-10 03:15:27 UTC,"Reviewed:  https://review.openstack.org/443989
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=f22cabf494f13535cdbb489f12e98c7358a29f74
Submitter: Jenkins
Branch:    master"
1665495,2017-03-10 15:51:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444365"
1665495,2017-03-10 17:56:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444438"
1665495,2017-03-11 15:16:07 UTC,"Reviewed:  https://review.openstack.org/444365
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=4f4c3fabe1ccb91ca8f510a6ab81b6f2eb588c17
Submitter: Jenkins
Branch:    master"
1665495,2017-02-21 18:11:38 UTC,"Reviewed:  https://review.openstack.org/436564
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=e50853dc4b05410748bfe8535c72d2d7935d6ac7
Submitter: Jenkins
Branch:    master"
1665495,2017-03-09 22:18:24 UTC,"Reviewed:  https://review.openstack.org/443931
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=189353e4eb110facbabf9882e0af1ef16ced600f
Submitter: Jenkins
Branch:    master"
1665495,2017-02-21 17:34:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436564"
1665495,2017-02-21 17:19:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436561"
1665495,2017-02-20 02:43:48 UTC,"Reviewed:  https://review.openstack.org/435720
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=93f21be04ab9462481e5ebd4f42d97a1a2630a69
Submitter: Jenkins
Branch:    master"
1665495,2017-02-21 16:25:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436538"
1665495,2017-02-17 19:47:17 UTC,"Reviewed:  https://review.openstack.org/435478
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=78d1a2400d0cf923cfa737cff59d6c9951dbe314
Submitter: Jenkins
Branch:    master"
1665495,2017-02-18 15:39:30 UTC,"Reviewed:  https://review.openstack.org/435656
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=52bd73e45dfe9436daef3237a2f4fa969344cff4
Submitter: Jenkins
Branch:    master"
1665495,2017-02-18 16:46:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435720"
1665495,2017-02-18 18:11:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435723"
1665495,2017-02-18 21:47:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435734"
1665495,2017-02-19 00:11:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435740"
1665495,2017-02-18 04:56:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435656"
1665495,2017-02-19 16:08:35 UTC,"Reviewed:  https://review.openstack.org/435734
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=7bfae5d76be175a743631dea74613813ceba4df9
Submitter: Jenkins
Branch:    master"
1665495,2017-02-19 17:00:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435795"
1665495,2017-02-19 17:13:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435798"
1665495,2017-02-20 02:28:40 UTC,"Reviewed:  https://review.openstack.org/435795
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=eadf481f352e4277001f3b9e83c7ffbbd58c789c
Submitter: Jenkins
Branch:    master"
1665495,2017-02-20 02:30:54 UTC,"Reviewed:  https://review.openstack.org/435740
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=f5e77c6be9b3c33b8031c310526bbebbfbd7aee8
Submitter: Jenkins
Branch:    master"
1665495,2017-02-20 02:30:48 UTC,"Reviewed:  https://review.openstack.org/435798
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=04430af53366795c47c52920864334d4220f4214
Submitter: Jenkins
Branch:    master"
1665495,2017-02-19 16:06:07 UTC,"Reviewed:  https://review.openstack.org/435723
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=e5a07834f8c6d7e15bb63d711d58b345663b33cc
Submitter: Jenkins
Branch:    master"
1665530,2018-03-22 16:03:10 UTC,"I too am facing the same issue with my camera not working (not appearing
to be physically connected to the laptop) and I think that a solution
lies in the fn+F12 functionality. I have not looked into it due to time
constraints but I am not aware of any fix."
1665530,2018-03-22 15:12:22 UTC,Any news regarding this bug? I'm facing the same problems. The most troublesome for is the Fn+ F12 to enable camera. My web cam is not working.
1665530,2017-08-14 17:25:49 UTC,"Install and boot [1], press the hotkeys, then attach dmesg."
1665530,2017-08-16 02:26:27 UTC,"I wrote a simple WMI driver for the laptop - but maybe GIGABYTE hotkey doesn't use WMI at all?
You probably need to ask Gigabyte to share more information."
1665530,2017-08-15 16:24:03 UTC,"Also, now that I am back to kernel 4.10, wireless is back but the volume keys still do not work. Some other updates were performed as well so that might be a coincidence."
1665530,2017-08-15 16:22:06 UTC,It was never set in the first place
1665530,2017-08-15 03:19:41 UTC,Can you remove apci_osi=Linux?
1665530,2017-08-14 18:50:11 UTC,"I seem to have lost my wireless and the use of the few fn buttons that were
working after the upgrading to this kernel but here is what you asked for.
I don't think pressing the buttons gives any dmesg output. Another thing I
noticed is that fn+print screen (SysRq) acts as if just print screen was
pressed (the others just do nothing)."
1665530,2017-08-14 04:37:46 UTC,"Please attach output of `lsmod`, thanks!"
1665530,2017-02-17 04:40:02 UTC,apport information
1665530,2017-08-11 03:21:44 UTC,Please provide dmesg and acpidump.
1665530,2017-05-09 04:17:20 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1665530,2017-03-09 07:20:51 UTC,quick edit:
1665530,2017-03-09 07:08:03 UTC,"I have a gigabyte P57X v6-CF3, with the latest bios installed. I can confirm this bug is present in ubuntu 16.10 with kernel 4.10.1-041001-generic."
1665530,2017-02-17 21:06:24 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1665530,2017-02-17 04:40:04 UTC,apport information
1665530,2017-02-17 04:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1665530,2017-08-14 01:08:38 UTC,There is nothing logged in dmesg log. So I have attached kern log
1665537,2017-02-17 05:00:02 UTC,"Actually, I think there was something else going on here to cause this problem. I'll test further and report back."
1665542,2017-02-19 18:58:08 UTC,r564 will report error for not implemented methods. gnome-screenshot will handle this properly and fallback to internals.
1665543,2017-06-10 12:53:09 UTC,Same issue with newton 9.1.2.
1665543,2017-05-22 08:53:45 UTC,Retype in-use volume also triggers the same issue. This has been verified with Canonical Ocata release.
1665543,2017-09-09 09:07:01 UTC,"Looks like something is broken badly in authentication schema of cinder in this case.
I dug into a bit and i see:"
1665543,2017-09-09 09:09:24 UTC,"Well,  then tried to set nova_endpoint_admin_template to http://controller00.ostack.fresh:35357/v3 just to see what will happen and it was very close :) The only problem (hmm... at least I think it is) I see my uuid in authentication request instead of name of user:
Member Key: identity
    Object
       Member Key: password
          Object
             Member Key: user
                 Object
..................
                     Member Key: name
                     String value: d........c30494 <- uuid
                     Key: name"
1665551,2017-02-17 10:29:00 UTC,ICE should be set to open all new windows as tabs not as a new Firefox instance .. can you give me an example of the youtube page with the external link that's attempting to open a new firefox instance.
1665552,2017-02-17 10:15:10 UTC,"Ice is not meant to toolbars and show tabs, that's kinda the whole point .. for hidden tab navigation please see here:
https://forum.peppermintos.com/index.php/topic,4314.msg42956.html#msg42956"
1665555,2017-03-17 08:49:06 UTC,"Hi All,"
1665555,2017-03-31 14:02:28 UTC,"Senario 1 should be consistent with scenario 2.  If volumes are already part of the group that they are being added to, it should return success.  A INFO message in the log will be helpful if a volume to be added to a group is already in the group."
1665555,2017-04-04 11:13:19 UTC,"Hi Xing,"
1665555,2017-04-04 14:51:56 UTC,"Hi Pooja,"
1665555,2017-05-05 02:25:08 UTC,"Hi all,"
1665555,2018-01-12 19:01:15 UTC,Unassigning due to no activity for > 6 months.
1665559,2017-02-17 07:38:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665559,2017-03-01 19:31:00 UTC,Seeing this here https://code.launchpad.net/~josharenson/unity8/dashboard-manager as well.
1665567,2017-02-17 10:22:23 UTC,It seems I used command incorrectly. Right way:
1665567,2017-02-28 12:09:51 UTC,"@Ilya,"
1665581,2017-03-09 10:28:11 UTC,"Confirm the problem with a nv117 (gtx750) card, both with 365 & 367 drivers (package from graphics-drivers ppa works well)"
1665581,2017-03-09 10:25:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665581,2017-03-07 18:13:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665581,2017-03-08 20:06:05 UTC,I analyzed the problem and found the culprit
1665581,2017-03-09 08:38:45 UTC,"let me add that the commands
# update-alternatives --auto i386-linux-gnu_egl_conf
# update-alternatives --auto i386-linux-gnu_gl_conf
are more straightforward, and that
# ldconfig
is needed afterwards"
1665583,2018-04-01 18:42:33 UTC,"I'm on a Retina mac, yeah."
1665583,2018-03-31 11:41:59 UTC,"I have been looking at this also, though I'm still getting to grips with debugging etc. As it doesn't happen when the app doesn't have focus it's a bit difficult to interrogate, because as soon as you go back to your debugging window the issue goes away. So I've been getting around this by pasting a sleep command followed by an interrupt command into the debug prompt, so that I have time to switch back to the app. Don't know if this is necessary or not but any tips are welcome."
1665583,2018-04-01 12:04:17 UTC,"""the waveforms became choppy after the inline editing of metadata in the track table was activated. When focus was switched to another window, the waveforms were smooth. The waveform choppiness persisted until Mixxx was restarted and happened every time after activating the metadata editing in the track table."""
1665583,2018-04-01 14:58:16 UTC,"Ben, if you want to debug this, I suggest using Git bisect to figure out which commit introduced the problem."
1665583,2018-04-01 15:06:39 UTC,"Thanks, I will have a look at that."
1665583,2018-04-01 15:33:00 UTC,"I tested the last available release of 2.0 with the Tango skin and didn't get the issue, but the first available release of 2.1 has it. Is that sufficient evidence that the issue was introduced from the beginning with 2.1? Obviously 2.0 didn't support HiDPI."
1665583,2018-04-01 16:37:50 UTC,Interesting:
1665583,2018-04-01 16:40:01 UTC,Ben are you using a retina mac? I am running a vintage mac from 2011 with no retina display ;)
1665583,2018-04-01 19:12:31 UTC,This is just weird.
1665583,2018-11-17 16:34:53 UTC,On Ubuntu Trusty 64 bit.
1665583,2018-06-24 03:51:10 UTC,I am deprioritizing this since 2.1 was released with the workaround of disabling inline editing of metadata in the track table by default.
1665583,2018-09-17 20:29:17 UTC,Is this fixed with Qt5?
1665583,2018-09-18 18:13:17 UTC,I want to say yes.
1665583,2018-09-18 20:15:46 UTC,"To clarify the above, there was also previously a pretty stark contrast between things before editing any metadata and after. As I said performance seems generally sluggish but there is no discernible difference between before and after editing metadata, which is another point in favor of saying it's gone with Qt5."
1665583,2018-09-18 22:28:18 UTC,"Great, thanks for following up on this."
1665583,2018-11-17 16:34:35 UTC,"Today I was able could reproduce the issue with 2.1.6.
The update rate of the whole GUI was reduced to 300 ms or such.
The trigger was opening the preferences window."
1665583,2018-03-31 01:23:32 UTC,"Since you have hardware access right now, it would be really nice to know."
1665583,2018-11-17 16:56:06 UTC,That's not the same as this bug.
1665583,2018-04-02 20:20:12 UTC,"The CPU spikes still happen with the waveform off and with the same intensity, for the record. You can still see the effect on the track time counters, though it's more subtle."
1665583,2018-03-30 23:46:00 UTC,"So https://github.com/mixxxdj/mixxx/pull/1566 does not make any difference?
Could you identify a build that introduces the issue?
How about the versions linked in #18?"
1665583,2018-03-31 01:08:23 UTC,I have not tested any builds from before https://github.com/mixxxdj/mixxx/pull/1566 was merged. But this is still an issue. This has been an issue for a long time now and I'm not going to bother figuring out when the bug was introduced right now. For 2.1 we can work around it by simply turning off metadata editing in the track table by default.
1665583,2018-03-30 21:39:47 UTC,What can exactly can you reproduce? That r6592 fixes the issue?
1665583,2017-02-17 17:16:28 UTC,Does this happen with Mixxx 2.0 using the same waveform renderer?
1665583,2017-02-17 18:46:59 UTC,Not happening on 2.0 so regression.
1665583,2017-02-22 11:15:50 UTC,no longer happening with latest master build. please close as worksforme.
1665583,2017-03-07 15:22:27 UTC,"Reported as not working again by the original poster and another user in the forums:
http://mixxx.org/forums/viewtopic.php?f=3&p=32395"
1665583,2017-05-11 10:20:52 UTC, (again) no longer happening with latest master build. please close as worksforme.
1665583,2017-05-12 08:32:58 UTC,"Setting status to OPINION, so it will show up in the default search. Status INVALID would not. Just in case it returns."
1665583,2018-03-30 23:33:22 UTC,"Sorry, I am not sure where the ""r6549"" came from in my last comment. I have tried build r6592 on three Macbooks now:
#1: MacBook Air (11-inch, Early 2015): 1.6 GHz Intel Core i5, 4 GB 1600 MHz DDR3, Intel HD Graphics 6000 1536 MB"
1665583,2017-11-23 21:28:05 UTC,"This is the most annoying bug I'd assume using mixxx on macOS since during regular usage, by accident you can run into the editing mode of some text in the playlist when using the trackpad of the laptop. The user then ends up with the unusable waveforms. Depending on the situation this can be a serious problem."
1665583,2017-12-03 21:53:04 UTC,Hopefully we find a mac OS contributor during the beta phase.
1665583,2018-03-05 18:04:35 UTC,"I have the exact same issue, running macOS 10.13.3 - happy to help if I can, have just set up Eclipse etc. and have been taking a look at the code."
1665583,2017-10-16 10:57:32 UTC,And it does return. See attached screencast.
1665583,2018-03-19 13:32:40 UTC,"I would be surprised if this actually fixes the issue, but the impact of this should be alleviated by https://github.com/mixxxdj/mixxx/pull/1550"
1665583,2018-03-18 14:32:26 UTC,"Benis is this issue something you would want to work on? As Daniel pointed out, it seems the core devs are having a hard time debugging this since no one is using macOS."
1665583,2018-03-30 21:12:07 UTC,I tested build r6549 on another Macbook with build r6592 and did reproduce this. Hardware info:
1665583,2018-03-30 18:19:43 UTC,I cannot reproduce this with build r6592.
1665583,2018-03-29 23:01:16 UTC,"Can we identify a version where this was introduced?
Can one test Mixxx 2.0 again?"
1665583,2018-03-20 19:58:35 UTC,"Oops, managed to submit that comment prematurely. For the short track I mentioned above it's more like 300-400 a minute. I've checked some tracks in between to make sure the pattern is consistent, which it is."
1665583,2018-03-20 19:51:49 UTC,Some pretty weird observations from my initial look at this:
1665583,2018-03-20 17:41:40 UTC,"I'd be happy to do what I can, I mean I'm new to C++ and debugging multi-thread applications so it won't be a quick turnaround, but if you give me some pointers as to what kind of thing I should be looking for I'll take a look."
1665583,2018-03-23 23:26:03 UTC,Pushing this back to 2.2 since it doesn't seem we have any ideas what is going on and the impact of this has been reduced by https://github.com/mixxxdj/mixxx/pull/1550
1665584,2017-03-10 13:54:32 UTC,"I have used strace to find out what is the reason of 'udevadm settle' timeouts. It turns out that it is a known udev issue described here [1] and kernel developers are fine with it. On the other hand, even if they will solve this issue, the patch they will write will be non-backportable for us, so there is no way to fix this issue directly. I think that the best WA will be calling 'udevadm settle' with reasonable timeout, say 15 seconds, that will allow us to fix the original bug with mpath devices being not ready at agent's startup, but will also allow us to use current agent's timeouts without flaps."
1665584,2017-03-10 14:05:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444310"
1665584,2017-03-13 15:46:56 UTC,"As per azvyagintsev comment in review [1], proposed timeout may not be big enough to allow OS to initialize mpath devices. As a result, it will break a previous fix [2]. I think that proposed change [1] is still a good WA for reported issue, but some solid solution is needed to close the bug in a right way. Assigning the bug to fuel-sustaining group and will wait for the fix to backport."
1665584,2017-03-13 15:48:13 UTC,"Change abandoned by Alexey Stupnikov (<email address hidden>) on branch: master
Review: https://review.openstack.org/444310
Reason: Can break mpath device initialization."
1665584,2018-07-13 13:15:52 UTC,sla1 for 9.0-updates
1665584,2018-07-17 12:34:38 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Oleksiy Molchanov <email address hidden>
Review: https://review.fuel-infra.org/38899"
1665584,2018-07-20 15:15:06 UTC,"Reviewed: https://review.fuel-infra.org/38899
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1665595,2017-02-18 16:58:41 UTC,"Thank you very much, Jabier and su_v!"
1665595,2020-05-09 12:23:42 UTC,Thank you for fixing. I'll check the latest version.
1665595,2017-02-18 16:35:56 UTC,Fixed in 0.92.x r.15379
1665595,2017-02-17 10:36:28 UTC,Also reproduced with lp:inkscape r15524 on Ubuntu 14.04.5 LTS.
1665595,2017-02-17 10:26:23 UTC,"Reproduced with Inkscape 0.92.0 r15299 and lp:inkscape/0.92.x r15378 on OS X 10.7.5.
(the backtraces pasted inline by the reporter were done with lp:inkscape/0.92.x r15378 on OS X 10.7.5)"
1665595,2017-02-18 12:11:08 UTC,Fixed in trunk r.15530
1665609,2020-03-21 15:42:08 UTC,https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/20170801.1-3
1665612,2017-03-13 08:44:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665621,2017-02-25 12:37:54 UTC,"Actually, the content does shift, but that probably isn't the correct behaviour"
1665629,2017-02-17 16:31:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1665632,2019-07-08 08:29:04 UTC,Watcher is the area that has seen a lot of changes and improvements since this report has been filed.
1665643,2017-02-17 16:26:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665643,2017-02-17 16:28:49 UTC,Marked this bug to be an regression introduced in an update.
1665643,2017-02-17 16:29:25 UTC,"Same problem.  Guessing it's related to python-paramiko crypto bug here:
https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/1665565"
1665643,2017-02-17 23:44:58 UTC,@vej not sure what version I had before but just ran another update which only changed python-crypto:
1665643,2017-02-17 23:50:33 UTC,"Possible duplicate of #1665598 or maybe just a dependency, depends on point of view."
1665643,2017-08-07 12:51:45 UTC,There is a workaround that fixed the problem for me. It was obviously related to `python-paramiko`.
1665658,2017-02-18 23:11:56 UTC,https://github.com/elopio/snapcraft-de-noche/pull/25
1665658,2017-02-19 20:41:54 UTC,"Hey Simon, it seems that ofono, captive-redirect, udisks2 and wireless-tools are private. I could put a user and password encrypted in travis, but then the build log would expose most of the things this snaps are doing. So for now I've just added the public ones."
1665662,2019-09-19 14:54:21 UTC,Hey is there any progress on NidhiMittalHada ?
1665662,2019-09-28 08:29:16 UTC,"I popped out the assignee, and lowered the priority to ""Wishlist"" - there's no rush in getting this bug fixed; but contributions will be encouraged.."
1665662,2019-10-03 14:54:32 UTC,Thanks Goutham!
1665664,2017-08-17 13:58:35 UTC,This issue was fixed in the openstack/ironic-inspector 6.0.0 release.
1665664,2017-03-27 20:32:34 UTC,patch in ironic-inspector: https://review.openstack.org/#/c/436415/
1665664,2017-04-27 13:32:24 UTC,"Reviewed:  https://review.openstack.org/436415
Committed: https://git.openstack.org/cgit/openstack/ironic-inspector/commit/?id=fc2e029fa6318384f840bdc8bc54894396308299
Submitter: Jenkins
Branch:    master"
1665664,2017-02-21 01:31:39 UTC,"it should be a issue, but we can get the introspection state via ironic API implicitly."
1665664,2017-02-27 15:36:51 UTC,"Seems it will require some changes in client, at least docs update"
1665671,2017-02-21 18:29:22 UTC,Fixed in https://review.openstack.org/#/c/435487/.
1665671,2017-08-15 08:50:01 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1665680,2017-02-17 16:09:17 UTC,@Mateusz
1665680,2017-02-17 17:28:49 UTC,@Andreas
1665680,2017-02-17 17:54:01 UTC,I would recommend using loose-mode reverse path filtering on the MAAS server for now.
1665680,2019-09-19 12:02:44 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1665681,2017-06-21 11:08:19 UTC,Merged to master: https://review.openstack.org/#/c/435503/
1665681,2017-08-15 08:50:00 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1665683,2019-10-15 12:47:32 UTC,"This has been implemented for a long time now. For reference it is the ""autostart"" part of https://snapcraft.io/docs/snap-format"
1665684,2017-07-07 22:26:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665693,2017-03-15 11:15:48 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1665693,2017-04-14 09:23:25 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1665693,2017-03-08 12:31:01 UTC,"Reviewed:  https://review.openstack.org/441224
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c40d4f37d4e245713902c61456a3bfdcf3ef93c3
Submitter: Jenkins
Branch:    stable/ocata"
1665693,2017-03-03 16:14:43 UTC,"Reviewed:  https://review.openstack.org/435563
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97e14fa3f39839491ff6c7de9572d277bec8f885
Submitter: Jenkins
Branch:    master"
1665693,2017-02-17 18:33:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435563"
1665693,2017-02-17 16:40:29 UTC,sdague pointed out that dynamic vendordata is optional so we might not want to be logging this at all. Maybe we can tell from the config if we should care.
1665693,2017-03-03 16:53:42 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441224"
1665695,2019-06-19 16:46:58 UTC,This bug was fixed in the package openssh - 1:8.0p1-2
1665695,2018-07-28 18:58:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665695,2018-07-28 18:59:24 UTC,Still present in Ubuntu 18.04.1. Updated upstream patch for 7.6p1 at https://bugzilla.mindrot.org/attachment.cgi?id=3107.
1665695,2018-08-01 18:24:39 UTC,"I doubt the patch will be added to a linux distribution before it's applied upstream, since it's of a very security sensitive nature."
1665695,2018-08-09 02:42:52 UTC,"Unfortunately, this bug has been open upstream for years, with no real indication of if or when it will ever be merged."
1665695,2019-04-16 09:15:46 UTC,"As mentioned in the upstream bug, they plan to add support in openssh 8.0."
1665698,2017-03-21 19:15:51 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/448242"
1665698,2017-03-21 19:35:56 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/448253"
1665698,2017-03-22 01:05:51 UTC,"Reviewed:  https://review.openstack.org/448203
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a41d265a19b7bcb1af8fc179bf864e00023c6cc6
Submitter: Jenkins
Branch:    master"
1665698,2017-03-20 14:55:31 UTC,"newton and ocata are both:
MIN_LIBVIRT_VERSION = (1, 2, 1)
MIN_QEMU_VERSION = (1, 5, 3)"
1665698,2017-03-22 09:19:59 UTC,Ubuntu SRU Information
1665698,2017-03-22 11:12:16 UTC,"Hello Logan, or anyone else affected,"
1665698,2017-03-21 17:27:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448203"
1665698,2017-03-22 09:12:25 UTC,Due to libvirt/nova combinations this bug does not impact either zesty or the ocata UCA (marking tasks Invalid).
1665698,2017-03-21 16:41:20 UTC,"On Tue, Mar 21, 2017 at 5:19 PM, Matt Riedemann <email address hidden>
wrote:"
1665698,2017-03-20 15:29:08 UTC,(FTR we'll hold bug 1664306 - Newton stable point releases - until this is resolved one way or the other).
1665698,2017-03-21 16:19:51 UTC,"To clarify my understanding of this, per comment 50 and the release note that went with the change:"
1665698,2017-03-21 13:05:54 UTC,"The former SRU was waiting in unapproved still while this SRU was already prepared here.
I checked with SRU Team and so we rejected the current upload to bundle it with the next one."
1665698,2017-03-20 15:56:24 UTC,"FYI on the delay for yakkety: To fix the issue of """" being a nop in yakkety as well requires the former SRU to complete first. But that is totally orthogonal to any of the Openstack considerations we did in the last few comments."
1665698,2017-03-20 15:13:02 UTC,To summarize:
1665698,2017-03-22 12:13:06 UTC,"Hello Logan, or anyone else affected,"
1665698,2017-03-20 15:01:59 UTC,Adding bug task for Nova as its not currently compatible in stable/newton with the documented minimum libvirt version of 1.2.1.
1665698,2017-03-20 15:01:02 UTC,Marking Cloud Archive task as Invalid (as the Newton UCA does not have any libvirt/qemu packages).
1665698,2017-03-21 16:36:07 UTC,@mriedem
1665698,2017-03-22 15:58:57 UTC,"Hello Logan, or anyone else affected,"
1665698,2017-03-20 15:05:48 UTC,"I believe the fixes for bug 1649527 fixed things for libvirt >= 1.3.3, but broke compatibility with the documented baseline version of libvirt for Nova breaking drivers that use the 'tap' vif type on Ubuntu Xenial."
1665698,2017-03-24 07:53:32 UTC,"For the libvirt portion:
- testing of the issue of this bug itself - done
- in & cross version migration tests - done
- upgrade tests - done
- general QA regression testing - done"
1665698,2017-03-20 14:54:51 UTC,Looks like that is defined here: https://github.com/openstack/nova/blob/stable/newton/nova/virt/libvirt/driver.py#L190-L208
1665698,2017-05-08 22:25:52 UTC,This issue was fixed in the openstack/nova 14.0.6 release.
1665698,2017-04-26 21:29:32 UTC,"Reviewed:  https://review.openstack.org/448253
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8142d526dfd6f4a56dbe382d25cf4110abf57f44
Submitter: Jenkins
Branch:    stable/newton"
1665698,2017-04-21 04:34:30 UTC,This bug was fixed in the package libvirt - 2.1.0-1ubuntu9.4
1665698,2017-04-14 09:22:36 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1665698,2017-04-12 18:55:11 UTC,This issue was fixed in the openstack/nova 15.0.3 release.
1665698,2017-04-10 23:12:37 UTC,"Reviewed:  https://review.openstack.org/448242
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cc495a24656893c94031f491a3fed2bc94fe1850
Submitter: Jenkins
Branch:    stable/ocata"
1665698,2017-04-06 14:06:37 UTC,"@Matt, nova: Can we get some eyes on the Newton and Ocata fix you have up? It is a pretty severe bug for me since I'm running a vif_type=ethernet plugin with regular Ubuntu distro libvirt, so I haven't been able to use any nova sha since early Feb due to this bug."
1665698,2017-03-23 09:40:12 UTC,"Hello Logan, or anyone else affected,"
1665698,2017-04-05 15:01:53 UTC,This bug was fixed in the package nova - 2:14.0.4-0ubuntu1.2
1665698,2017-04-04 07:37:51 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1665698,2017-04-04 05:57:08 UTC,"The automated proposed regression check on qemu/libvirt passed and confirmed that there should be no regression.
Also I was able to test the explicit fix of this vs proposed.
That said - verification-done (libvirt)"
1665698,2017-03-31 06:29:34 UTC,"Hello Logan, or anyone else affected,"
1665698,2017-03-31 06:01:26 UTC,Uploaded a no change rebuild as version 2.1.0-1ubuntu9.4 to help properly linking the other linked SRU bug as well.
1665698,2017-03-31 05:47:12 UTC,"Since we have one ""issue"" but two related fixes we had two SRU Templates, one in the bug description and one in comment #62 - I copied the one in the comment up and marked them as libvirt/nova so that an SRU Team member finds this information more easily."
1665698,2017-03-24 13:44:48 UTC,yakkety-newton test failure was the:
1665698,2017-03-24 10:02:50 UTC,Xenial newton verification testing:
1665698,2017-03-24 10:01:27 UTC,Yakkety newton verification testing:
1665698,2017-04-04 07:37:53 UTC,"This bug was fixed in the package nova - 2:14.0.4-0ubuntu1.2~cloud0
---------------"
1665698,2017-03-20 14:21:28 UTC,Add what's the baseline libvirt version compatibility that nova documents?
1665698,2017-03-20 15:00:17 UTC,OK so reading the code and reading:
1665698,2017-03-20 13:54:25 UTC,"Yes it only affects the ""tap"" vif type."
1665698,2017-02-20 13:52:47 UTC,"Hi Christian,"
1665698,2017-02-20 13:48:41 UTC,"I have checked with our support people, but they somewhat calmed me down that this is not lighting up everywhere (?yet?). So keeping the state as is for now."
1665698,2017-02-20 11:56:13 UTC,Summarizing open questions to stop referring back:
1665698,2017-02-20 11:56:10 UTC,"Just wanted to make one more thing clear, the libvirt in Xenial (and here in the bug) is 1.3.1.
That means it is pre http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=9c17d66
So the prereq to need https://review.openstack.org/#/c/425637/ is not given.
Maybe those two bite each other, but I still need some way to reproduce to fully understand."
1665698,2017-02-20 11:50:07 UTC,"FYI - while not confirmed I marked it regression-update for now until we know for sure it is not (to get the right attention).
I also pinged some Cloud Archive people on IRC to take a look."
1665698,2017-02-20 11:49:20 UTC,"Even with that things are still working correctly for me:
Here the ""no"" case re-ran with the device being set up externally."
1665698,2017-02-20 11:12:18 UTC,"I think I found the guest definition in the attached raw log, analyzing ..."
1665698,2017-02-20 11:00:03 UTC,I was testing various type=ethernet XML configurations.
1665698,2017-02-20 14:24:50 UTC,"Just found that the report was for 1.3.1-1ubuntu10.6~cloud0 and only stated to ""also apply"" to 1.3.1-1ubuntu10.8. By that dropping the regression-update tag."
1665698,2017-02-20 09:59:22 UTC,I'm going off some more testing with that in mind what I documented on the bug already.
1665698,2017-02-20 09:43:37 UTC,"Let me outline on the /etc/qemu-ifup a bit - or at least my understanding of it.
If you happen to run ""type=ethernet"" networking the script gets to be important.
See https://libvirt.org/formatdomain.html#elementsNICSEthernet
In general this is not recommended for various security reasons (you have to give libvirt/qemu more permissions/capabilities to get this working).
Now if you have type=ethernet and no script set, then the default is /etc/qemu-ifup, maybe that is how it gets this ""config"" in your case."
1665698,2017-02-20 09:42:38 UTC,Marking Critical as it is a potential SRU-regression
1665698,2017-02-20 09:40:59 UTC,"Hi Logan, thank you for your report.
And also tanks Jamie to already provide a workaround for thew apparmor case."
1665698,2017-02-17 20:13:45 UTC,Thank you for responding. Marking back to New so a member of the cloud team can take a further look.
1665698,2017-02-17 18:06:46 UTC,"I wonder if https://review.openstack.org/#/c/425637/ has broken this on my version of libvirt by removing the script='' entry, which is maybe causing qemu to revert to its default of calling /etc/qemu-ifup, which as we know is not allowed by apparmor."
1665698,2017-02-17 17:55:32 UTC,Also thanks for the workaround suggestion. I was looking at adding a workaround like that to the abstraction earlier but wasn't sure on the syntax :)
1665698,2017-02-17 17:52:29 UTC,"That has been my challenge this morning in figuring this out. As far as I know, I don't use it or need what it provides. I can't find anything in /etc/libvirt or even /etc or my Openstack venv that is calling toward qemu-ifup. I grepped thru /usr looking for 'qemu-ifup' and the only hits were from the /usr/share/doc/qemu-system-*/common/qemu-doc.html mentions."
1665698,2017-02-17 17:36:34 UTC,/etc/qemu-ifup is a non-standard command. Can you give details of how you setup your system to use this?
1665698,2017-02-20 09:58:00 UTC,"The function the upstream fix relates to in Openstack is:
def set_vif_host_backend_ethernet_config(conf, tapname):
    """"""Populate a LibvirtConfigGuestInterface instance
    with host backend details for an externally configured
    host device."
1665698,2017-02-20 14:51:58 UTC,"I tried to puzzle together the timeline on this.
Thanks rbasask for discussing with me to refocus on this issue."
1665698,2017-03-20 13:58:26 UTC,http://lists.openstack.org/pipermail/openstack-dev/2016-December/109080.html and https://bugs.launchpad.net/nova/+bug/1649527 contain additional info about the bug and nova fix.
1665698,2017-02-24 16:00:20 UTC,"I also tested hacking in conf.script = ""/bin/true"" to nova. You suspected it might fail with apparmor preventing /bin/true execution, I can confirm that it did indeed fail."
1665698,2017-02-24 15:50:11 UTC,"I'm having a hard time testing the workaround in #1 -- is there an additional step necessary after modifying the abstractions/libvirt-qemu file with the additional rule? Ie. some command to reload the file? I restarted apparmor, libvirt-bin, and nova-compute services and it is still failing with the same message despite the line being added to the apparmor abstraction file."
1665698,2017-03-20 12:32:47 UTC,"The change in Openstack is in Ocata only, if you run Ocata on Zesty or Xenial+UCA-Ocata you should be good already with the fix above."
1665698,2017-03-17 23:57:23 UTC,Will the libvirt fix be back-ported? We can't effectively use noscript in OpenStack with any versions missing the fix.
1665698,2017-03-17 13:35:02 UTC,This bug was fixed in the package libvirt - 2.5.0-3ubuntu4
1665698,2017-03-17 08:49:42 UTC,"It is still right to fix the empty script execution (#4 in my timeline post) in the version that is in Zesty. Tests are mostly good, should hit zesty-proposed soon."
1665698,2017-03-17 08:42:55 UTC,"Ok, that confirms my theory of new Openstack vs (too) old libvirt.
But IIRC UCA Newton should be Newton form openstack and virtualization bits from Yakkety Ubuntu release.
That would be libvirt 2.1.0-1ubuntu9.1"
1665698,2017-03-17 03:39:37 UTC,"Also in regard to: ""Reading your Deny log again comm=""qemu-system-x86"".
Hmm, could it be that you run the ""new"" openstack against the ""old"" libvirt?
I see you said ""with libvirt and non-openstack bits sourced from cloud-archive"", but then I'd have expected the apparmor fail against libvirt - if any."""
1665698,2017-03-17 03:34:37 UTC,Sorry for the delay on getting this info.
1665698,2017-03-13 08:09:54 UTC,"Hi Neil,"
1665698,2017-03-12 14:25:57 UTC,@Christian: what does the default /etc/qemu-ifup do?
1665698,2017-03-10 08:26:10 UTC,"Note: a backport of the upstream libvirt fix is building here - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2559
Feel free to test, but I really think we need to understand the dependencies to consider the apparmor change at the right place first."
1665698,2017-03-10 08:25:15 UTC,"So we have:
- old openstack: sets script=''
- new openstack: sets nothing
- old libvirt: passes to qemu, which does nothing on ''
- new libvirt: executes script, but can't handle ''
- any libvirt: if nothing is set defaults to /etc/qemu-ifup"
1665698,2017-03-10 08:02:14 UTC,"Thank you so much for confirming that Logan!
That kind of reset my sanity on understanding the issue."
1665698,2017-03-09 18:49:11 UTC,"I must've done something wrong when originally testing the abstraction fix. I re-tested based on your advice and it does indeed fix the problem. The abstraction file that I just tested, which worked, is http://cdn.pasteraw.com/9u16uk9938mp5t3x530ok0w791nkooc."
1665698,2017-03-07 07:52:07 UTC,Thanks to you already listing an example of a full profile from your system in the description and a libvirt xml in http://cdn.pasteraw.com/b3tw4cjefomfi3e9k09hvodrfun85z both seem pretty standard and includes the abstractions/libvirt-qemu.
1665698,2017-03-06 20:37:31 UTC,"Yep, just to confirm with the suggested workaround applied and restarting apparmor + rebooting the system it did not work."
1665698,2017-02-27 10:12:40 UTC,"On Fri, Feb 24, 2017 at 4:50 PM, Logan V <email address hidden> wrote:"
1665698,2017-03-20 12:43:48 UTC,The OpenStack change is not just in Ocata. It was also backported to Newton. Please note the merged OpenStack patch in #4 is on branch stable/newton. We need this fix in Newton UCA as well please.
1665698,2017-03-20 13:39:24 UTC,"Having read through the history on this bug I'm a little confused; Newton UCA does not contain any version of libvirt - Newton deployments on Xenial will use the libvirt version shipped in Xenial itself, which I think is the same version that will be used in all gates for OpenStack so I'm not clear on exactly what needs 'fixing' for the Newton UCA."
1665714,2017-02-17 17:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1665719,2017-02-17 17:31:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435546"
1665719,2017-03-15 11:16:02 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1665719,2017-02-27 20:28:44 UTC,This issue was fixed in the openstack/nova 14.0.4 release.
1665719,2017-02-20 07:12:05 UTC,"Reviewed:  https://review.openstack.org/435619
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=10a32ddcf85076266c3ede6e8ca2e9776d64d32e
Submitter: Jenkins
Branch:    stable/ocata"
1665719,2017-04-14 09:23:45 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1665719,2017-02-18 03:05:05 UTC,"Reviewed:  https://review.openstack.org/435546
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6d64b7274410ae45b95bd7ac7f702c16daaa0fcd
Submitter: Jenkins
Branch:    master"
1665719,2017-02-17 22:49:10 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/435620"
1665719,2017-02-17 22:42:41 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/435619"
1665719,2017-02-18 03:08:26 UTC,"Reviewed:  https://review.openstack.org/435620
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=642caf0c58ed0a0e0c06103d2e3ef001c1ae142f
Submitter: Jenkins
Branch:    stable/newton"
1665735,2017-02-18 16:17:14 UTC,apport information
1665735,2017-02-18 16:17:39 UTC,apport information
1665735,2017-02-18 16:17:34 UTC,apport information
1665735,2017-02-18 16:17:28 UTC,apport information
1665735,2017-02-18 16:17:25 UTC,apport information
1665735,2017-02-18 16:17:21 UTC,apport information
1665735,2017-02-18 16:17:16 UTC,apport information
1665735,2017-02-18 16:17:12 UTC,apport information
1665735,2017-02-18 16:17:18 UTC,apport information
1665735,2017-02-18 16:17:08 UTC,apport information
1665735,2017-02-18 16:17:10 UTC,apport information
1665735,2017-02-17 18:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1665735,2017-02-18 16:16:53 UTC,apport information
1665735,2017-02-17 21:00:15 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1665735,2017-02-18 16:17:01 UTC,apport information
1665735,2017-02-18 16:16:56 UTC,apport information
1665735,2017-02-18 16:17:06 UTC,apport information
1665739,2018-03-29 15:50:50 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.openstack.org/444036"
1665739,2017-03-09 23:12:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444036"
1665739,2017-04-25 13:11:43 UTC,This extends an existing API that already has granular control though? I am not understanding why all these extra policy rules would be useful here.
1665739,2017-02-21 16:40:20 UTC,I would compare to flavor extra specs policy:
1665739,2017-02-21 20:07:48 UTC,"So then instead, in order to fix this bug, would the idea be to create policies associated with different operations (similar to what flavor extra specs has)?"
1665742,2017-02-22 05:24:23 UTC,"it is weird. there is nothing in ceilometer, which related to mongo. and it still try to connect localhost. Seems there are some default value in ceilometer.conf. But i failed to find it."
1665742,2017-09-22 12:16:38 UTC,Stil remains in ocata series ( kolla 4.0.2)
1665742,2018-12-13 10:18:43 UTC,Is it still a problem in queens/rocky? If yes please reproduce and provide logs.
1665742,2019-11-12 04:17:21 UTC,[Expired for kolla because there has been no activity for 60 days.]
1665742,2017-02-22 12:25:39 UTC,Thanks for taking a look.
1665755,2019-11-02 21:13:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER"
1665755,2020-01-02 04:17:29 UTC,[Expired for guake (Ubuntu) because there has been no activity for 60 days.]
1665756,2017-03-15 21:40:51 UTC,While the $SNAP and $SNAP_DATA variables are now expanded there is something else special going on.
1665756,2017-05-02 23:08:19 UTC,This is fixed for me now (APPORT_CRASHDB_CONF=/snap/apport/x5/lib/python3.5/site-packages/etc/apport/crashdb.conf) with the following versions:
1665756,2017-03-29 12:52:03 UTC,"I'm seeing the same issues in xenial (+ stable phone overlay PPA), where I've snap 2.23 installed."
1665756,2017-03-17 13:13:45 UTC,"I think this might be the problem I'm having with ubuntu-image classic snap.  It uses the environment key to set $PATH and $PYTHONPATH.  It works in Zesty but not Xenial or Yakkety, and that's probably because 2.23 is in Zesty but still sitting in {xenial,yakkety}-proposed."
1665756,2017-02-23 18:47:11 UTC,"> I was running 2.27 of snapcraft, is it fixed in 2.23 of something else?
"
1665756,2017-02-21 22:25:48 UTC,"I was running 2.27 of snapcraft, is it fixed in 2.23 of something else?"
1665756,2017-02-22 08:42:50 UTC,Probably snap/snapd. It's a runtime issue aiui not a build-time issue.
1665756,2017-02-17 19:50:15 UTC,The \n is fixed in master and will be released as 2.23 shortly.
1665765,2017-02-20 08:35:49 UTC,collectd uses the management endpoints to poll the OpenStack APIs and those endpoints are HTTP-based for Fuel MOS.
1665765,2017-02-21 23:16:01 UTC,"Simon,"
1665765,2017-02-22 08:32:31 UTC,"Vlad, until I see your plugin's code, I'm not sure how we can implement a fix."
1665773,2017-04-20 19:35:54 UTC,This bug was fixed in the package cloud-init - 0.7.9-90-g61eb03fe-0ubuntu1~16.04.1
1665773,2017-09-23 02:29:21 UTC,"This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New"
1665773,2017-04-20 19:33:34 UTC,This bug was fixed in the package cloud-init - 0.7.9-90-g61eb03fe-0ubuntu1~16.10.1
1665773,2017-04-20 19:34:30 UTC,"The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1665773,2017-04-10 22:46:17 UTC,"Hello Serg, or anyone else affected,"
1665773,2017-04-10 22:23:13 UTC,"Hello Serg, or anyone else affected,"
1665773,2017-04-13 18:32:56 UTC,"$ for r in xenial-proposed yakkety-proposed; do
  ( mkdir -p $r && cd $r && pull-lp-source cloud-init $r ); done"
1665782,2018-10-16 00:05:14 UTC,This still happens with hplip 3.17.10 (ubuntu 18.04). Any chance to to upstream the changes? :)
1665785,2017-05-22 21:21:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665789,2020-11-17 09:43:37 UTC,I noticed that we have multiple tickets for more resolutions opened. Let's consolidate all in https://bugs.launchpad.net/qemu/+bug/1022023 and close this one here as duplicate.
1665802,2017-02-23 02:28:05 UTC,"My concern is not that such a workaround increases latency again, but that it requires more work to get right than a potential proper fix might :)"
1665802,2017-02-23 04:08:13 UTC,"OK, I think we just about understand the problem now."
1665802,2017-02-23 08:57:14 UTC,I've just spent more time analysing the similar bug 1211700 that radeon experiences and found the common factor is the Mesa gallium code -- and that's also where the server process is hung in my case.
1665802,2017-02-23 09:27:12 UTC,WORKAROUND (1):
1665802,2017-02-23 12:00:35 UTC,"-Freedreno chip
+Adreno chip"
1665802,2017-02-24 03:22:13 UTC,Workaround 1:
1665802,2017-02-28 05:08:40 UTC,Dropped priority.
1665802,2017-02-24 09:25:39 UTC,"I've now tried some additional ideas like overscheduling the compositor and giving the server higher priority than the client. Neither works, which is not entirely surprising if the GPU is independent of CPU scheduling."
1665802,2017-03-01 10:49:06 UTC,"Alberto,"
1665802,2017-03-07 11:17:12 UTC,"Fix committed into lp:mir at revision 4072, scheduled for release in mir, milestone 1.0.0"
1665802,2017-03-10 04:14:44 UTC,"OK, I am done with this for now. Here are two relevant branches to try:"
1665802,2017-10-13 01:45:33 UTC,Alberto:
1665802,2017-10-13 01:52:49 UTC,"P.S. client-side vsync isn't just a good idea that improves performance on non-buggy drivers [2], but apparently also the norm. It is the design used by gtk and clutter too. I had no idea it was so common till recently."
1665802,2017-02-24 03:58:10 UTC,Workaround 2 might work for egltriangle but not eglplasma because eglplasma is more of a GPU hog (also not a realistic shader you would use in production).
1665802,2017-02-23 02:11:02 UTC,"3. Not sure. This is snap world, so it's cumbersome to bring profiler + deps to do the job."
1665802,2017-02-23 01:37:38 UTC,That analysis might be incorrect. This is not the same as bug 1211700 unless we show that vsync has somehow gone missing (sleeps into the future spin or are never requested). The thing about bug 1211700 is that it's solved by any sleep of 10ms or so. And that's essentially what client-side vsync does.
1665802,2017-02-22 17:45:28 UTC,I tried --composite-delay=0 yesterday but didn't help.
1665802,2017-02-19 06:06:07 UTC,"Sounds like it's spinning (experiencing swap interval 0 behaviour by accident), similar to bug 1661072 and bug 1661128."
1665802,2017-02-19 06:19:17 UTC,Actually this could also be bug 1639725 ... The present workaround for that is to remove all vsync and render unthrottled:
1665802,2017-02-19 06:39:34 UTC,"Also note ""frames hardly update"" is a common consequence of compositing swap interval 0 on some drivers (if they have inadequate GPU time sharing between processes). See bug 1211700."
1665802,2017-02-21 16:06:55 UTC,The rate is 60 (confirmed on client) and here's the server spew on dragonboard:
1665802,2017-02-23 01:40:04 UTC,  6. What driver does the dragonboard use? Is it mesa-kms based or android?
1665802,2017-02-21 16:56:03 UTC,Output of mirout:
1665802,2017-02-21 16:49:56 UTC,I confirmed this bug is caused by client side vsync by making
1665802,2017-02-21 23:34:53 UTC,"When the fps drops down to 27fps from the report above, that's when high cpu usage starts."
1665802,2017-02-22 03:25:37 UTC,"That's correct, and not a bug in itself. The timestamps are meant to be in the past if the client has fallen behind (its render time jumped from almost zero to 33ms). That's a feature and it has test cases :)"
1665802,2017-02-22 03:32:23 UTC,Another concerning aspect is that we appear to have lost a buffer (dropped from 4 to 3). Where did it go?
1665802,2017-02-22 03:34:41 UTC,  4. Do other demos like egltriangle and flicker suffer this bug at all?
1665802,2017-02-22 03:39:09 UTC,  5. Does using a small window below 480x480 avoid the problem? (that's the threshold for nested passthrough)
1665802,2017-02-21 23:21:06 UTC,"[2017-02-21 23:20:08.433959] perf: mir_demo_client_eglplasma.bin: 57.65 FPS, render time 1.75ms, buffer lag 54.37ms (4 buffers)
[2017-02-21 23:20:09.433867] perf: mir_demo_client_eglplasma.bin: 60.00 FPS, render time 0.47ms, buffer lag 60.64ms (4 buffers)
[2017-02-21 23:20:10.450471] perf: mir_demo_client_eglplasma.bin: 60.03 FPS, render time 0.55ms, buffer lag 73.48ms (4 buffers)
[2017-02-21 23:20:11.467188] perf: mir_demo_client_eglplasma.bin: 60.03 FPS, render time 0.53ms, buffer lag 49.46ms (4 buffers)
[2017-02-21 23:20:12.467195] perf: mir_demo_client_eglplasma.bin: 60.00 FPS, render time 0.53ms, buffer lag 49.46ms (3 buffers)
[2017-02-21 23:20:13.483590] perf: mir_demo_client_eglplasma.bin: 60.03 FPS, render time 0.66ms, buffer lag 48.52ms (4 buffers)
[2017-02-21 23:20:14.483623] perf: mir_demo_client_eglplasma.bin: 60.00 FPS, render time 0.49ms, buffer lag 49.51ms (4 buffers)
[2017-02-21 23:20:15.500524] perf: mir_demo_client_eglplasma.bin: 60.03 FPS, render time 0.40ms, buffer lag 49.59ms (3 buffers)
[2017-02-21 23:20:16.500635] perf: mir_demo_client_eglplasma.bin: 60.00 FPS, render time 0.46ms, buffer lag 49.54ms (3 buffers)
[2017-02-21 23:20:17.517178] perf: mir_demo_client_eglplasma.bin: 60.03 FPS, render time 0.46ms, buffer lag 49.53ms (3 buffers)
[2017-02-21 23:20:18.533536] perf: mir_demo_client_eglplasma.bin: 60.03 FPS, render time 0.45ms, buffer lag 49.52ms (3 buffers)
[2017-02-21 23:20:19.550187] perf: mir_demo_client_eglplasma.bin: 60.03 FPS, render time 0.55ms, buffer lag 49.44ms (3 buffers)
[2017-02-21 23:20:20.582459] perf: mir_demo_client_eglplasma.bin: 45.54 FPS, render time 9.19ms, buffer lag 53.94ms (4 buffers)
[2017-02-21 23:20:21.585826] perf: mir_demo_client_eglplasma.bin: 27.91 FPS, render time 32.85ms, buffer lag 74.65ms (4 buffers)
[2017-02-21 23:20:22.589183] perf: mir_demo_client_eglplasma.bin: 27.91 FPS, render time 33.43ms, buffer lag 74.07ms (3 buffers)
[2017-02-21 23:20:23.592578] perf: mir_demo_client_eglplasma.bin: 27.91 FPS, render time 33.47ms, buffer lag 74.02ms (3 buffers)
[2017-02-21 23:20:24.595900] perf: mir_demo_client_eglplasma.bin: 27.91 FPS, render time 33.41ms, buffer lag 74.08ms (3 buffers)
[2017-02-21 23:20:25.599285] perf: mir_demo_client_eglplasma.bin: 27.91 FPS, render time 33.43ms, buffer lag 74.07ms (3 buffers)
[2017-02-21 23:20:26.602642] perf: mir_demo_client_eglplasma.bin: 27.91 FPS, render time 32.88ms, buffer lag 74.61ms (3 buffers)
[2017-02-21 23:20:27.605998] perf: mir_demo_client_eglplasma.bin: 27.91 FPS, render time 33.44ms, buffer lag 74.05ms (3 buffers)
[2017-02-21 23:20:28.609350] perf: mir_demo_client_eglplasma.bin: 27.91 FPS, render time 33.49ms, buffer lag 74.00ms (3 buffers)"
1665808,2017-03-29 21:47:59 UTC,"We have observed snapd working with aufs on zesty, which is a functionally similar environment -- but is the difference the use of aufs or the use of zesty (most likely the kernel)?"
1665808,2017-02-24 07:01:53 UTC,"Forgive my ignorance, but isn't aa-notify how we figured out via syslog that AppArmor was causing the problem? Or was that some other mechanism?"
1665808,2017-02-22 17:57:44 UTC,The following steps allowed me to work around the issue:
1665808,2017-02-23 07:09:00 UTC,UX wise something that might help is running aa-notify from  apparmor-notify package that will provide notifications for apparmor denials.
1665808,2017-02-22 08:21:59 UTC,"> Wiadomość napisana przez Mike Pontillo <email address hidden> w dniu 22.02.2017, o godz. 08:57:
>
> Well, that's interesting. The behavior has changed slightly, and I'm not
> sure why. Now when I install the core snap, I get:
>
>    core 16-2 from 'canonical’ installed
This is most likely caused by the removal of the configure hook.
"
1665808,2017-02-22 07:57:48 UTC,"Well, that's interesting. The behavior has changed slightly, and I'm not sure why. Now when I install the core snap, I get:"
1665808,2017-02-22 07:10:01 UTC,Could you please attach the syslog file after the error happens? The strace is nice but unfortunately we would need the strace of the server (snapd) side of the operation. If you want to do that please make sure to use strace -f as go will spawn a lot of processes - and its going to be very chatty :) The syslog is probably sufficient to get a first idea.
1665808,2017-02-22 08:47:00 UTC,Thanks for the reply.
1665809,2017-02-18 00:12:52 UTC,"StacktraceTop:
 unity::QuicklistView::CheckAndEmitItemSignal (this=this@entry=0x56056ed86000, x=123, y=y@entry=79) at ./launcher/QuicklistView.cpp:619
 unity::QuicklistView::RecvItemMouseRelease (this=0x56056ed86000, item=0x56056ff62a60, x=80, y=<optimized out>) at ./launcher/QuicklistView.cpp:649
 emit (_A_a3=@0x7fff24b5add8: 14, _A_a2=@0x7fff24b5addc: 80, _A_a1=@0x7fff24b5ade8: 0x56056ff62a60, impl=0x56056ed77360) at /usr/include/sigc++-2.0/sigc++/signal.h:1562
 emit (this=<optimized out>, _A_a3=@0x7fff24b5add8: 14, _A_a2=@0x7fff24b5addc: 80, _A_a1=@0x7fff24b5ade8: 0x56056ff62a60) at /usr/include/sigc++-2.0/sigc++/signal.h:3263
 unity::QuicklistMenuItem::RecvMouseUp (this=<optimized out>, x=<optimized out>, y=<optimized out>, button_flags=<optimized out>, key_flags=<optimized out>) at ./launcher/QuicklistMenuItem.cpp:178"
1665809,2017-02-19 12:30:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665809,2017-02-19 16:24:14 UTC,"The attachment ""ProcCpuinfo.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1665812,2018-06-10 13:07:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665818,2017-03-14 14:37:19 UTC,Check /etc/hosts on all nodes or update DNS records in DNS and then flush DNS cache on all nodes. Ansible has problem with hostname resolving.
1665818,2019-11-12 04:17:32 UTC,[Expired for kolla because there has been no activity for 60 days.]
1665818,2017-02-18 00:54:03 UTC,"Sorry, I am using centos 7.1 as the host environment to using kolla.
[root@localhost ~]# uname -a
Linux localhost 3.10.0-229.el7.x86_64 #1 SMP Fri Mar 6 11:36:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux"
1665822,2017-02-18 01:47:43 UTC,"StacktraceTop:
 __GI__IO_wfile_xsputn (f=0xb751cd60 <_IO_2_1_stdout_>, data=0x8019b1b0, n=4) at wfileops.c:1027
 _IO_vfwprintf (s=<optimized out>, format=0x8164d888 L""%ls: %ls'%ls' terminated by signal %ls (%ls)"", ap=0xbfe89650 ""\304\226\350\277\200\336k\201\314\202\033\200@\346h\201\244f\033\200\003"") at vfprintf.c:1637
 __fwprintf_chk (fp=0xb751cd60 <_IO_2_1_stdout_>, flag=1, format=0x8164d888 L""%ls: %ls'%ls' terminated by signal %ls (%ls)"") at fwprintf_chk.c:35
 job_reap(bool) ()
 parse_execution_context_t::run_1_job(parse_node_t const&, block_t const*) ()"
1665822,2017-02-24 14:03:19 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1665822,2017-02-25 04:10:47 UTC,"I am a fish developer. What version of fish are you using? What does `locale` report? Steps to reproduce? Can you set `ulimit -c unlimited` and reproduce the problem to get a core dump for analysis? Note that we recently made several changes to avoid mixing narrow and wide stdio calls which can lead to unpredictable behavior so the fish version you're using is important. Also, since it is more likely this is a fish bug than a Ubuntu specific bug it will probably be more fruitful to open an issue against the fish project: https://github.com/fish-shell/fish-shell/issues/new"
1665822,2020-04-26 17:25:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665822,2020-04-26 17:27:41 UTC,I think I'm affected by the same bug. The weird thing is: I think I only get this when starting Atom but I'm not sure.
1665822,2020-04-26 17:28:22 UTC,"(um, I'm on 18.04.4 amd64)"
1665833,2017-02-18 03:00:59 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1665833,2017-02-18 03:16:19 UTC,"Sorry, I can't collect the report: apport isn't installed on the server, and the whole problem is that, having run out of inodes, I can't install anything (nor save files). Cleaning up and rebooting will destroy the logfiles of interest."
1665850,2017-09-05 18:03:57 UTC,"Yes, I still observed it under current HWE server 1.19 with modesetting driver.  (I intentionally switched back from Intel to modesetting to test it). I did not see it recently though (without any X related updates), but what I see currently is - screen goes blank, I move mouse, screen unblanks and then after second or so quickly blanks/unblanks again. It looks as if some hardware re-probing happens."
1665850,2017-09-11 16:33:07 UTC,"> I did not see it recently though
"
1665850,2017-08-23 07:10:27 UTC,"does it happen with current hwe xserver, which is based on 1.19.x?"
1665850,2017-11-10 16:49:02 UTC,"I tried to install mesa 17.2.4 (which should include this commit) from ppa ubuntu-x-swat, but still the same - as soon as I attempt to enable DRI3 I get screen corruption and tearing."
1665850,2017-03-05 06:34:37 UTC,I noticed that Xorg is now using modesetting driver while in the past I think it was using Intel driver. How can I easily switch back to Intel for testing?
1665850,2017-03-02 06:38:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665850,2017-03-10 03:41:59 UTC,After I observed visible tearing when watching video on external HDMI screen I switched back to Intel driver.
1665850,2017-11-02 03:24:03 UTC,Update: recently one of programs I use started to complain that screen was not DRI3 capable. I am using Intel driver which apparently defaults to DRI2. I forced it to DRI3 using
1665853,2017-02-18 19:05:04 UTC,The path was wrong in #6 (I forgot the /.config/
1665853,2017-02-18 07:16:58 UTC,"As it turned out, the leftern part of the right screen is already part of the right screen (not a overstretched part of the left screen."
1665853,2017-02-18 19:41:19 UTC,I still get syslog entries
1665853,2017-02-18 18:51:10 UTC,@mitya57 @muktupavels thanks for reporting back.
1665853,2017-02-18 06:59:03 UTC,That got scrambled. Should be:
1665853,2017-02-18 13:37:00 UTC,"This definitely is not problem with gnome-flashback, at login screen gnome-flashback is not started."
1665853,2017-02-18 08:29:01 UTC,"Your photo shows the lightdm login screen, and you tell that after login everything is fine. Maybe reassign this to lightdm?"
1665856,2017-02-18 08:02:08 UTC,https://review.openstack.org/#/c/435665/
1665856,2017-02-22 16:35:13 UTC,Also trying this temporary workaround in networking-ovn: https://review.openstack.org/#/c/437026/
1665856,2018-03-08 09:45:27 UTC,The patches mentioned in here are now merged. Should we mark this as fixed ?
1665862,2017-02-18 08:17:19 UTC,For those who do not want to patch/build the PCB offline method of TinyCAD import is available.
1665862,2017-02-18 10:49:54 UTC,Quick review...
1665862,2017-02-18 10:55:25 UTC,I noticed you use strcasecmp...
1665862,2017-02-18 11:34:00 UTC,"On 18.02.2017 11:49, Peter Clifton wrote:

> Quick review...
>
> static bool netlist_loaded; should ideally not be added to action.c
>
> Can we ignore if the netlist load failed?
> If not, ideally we need a mechanism with API to check this without adding global state to a specific source file.
>
> This is primarily coming from the thought that ""at some point we should
> stop adding all new actions to ""action.c"", it is getting a little
> large!"". This change as stand ties the new action to living in action.c,
> due to relying on that file-scope global variable being set here.
"
1665862,2017-02-18 11:41:20 UTC,"On 18.02.2017 11:55, Peter Clifton wrote:

> I noticed you use strcasecmp...
>
> Unless the tiny cad file format is defined to be case insensitive, I
> think strcmp would be better (matching whatever they actually output).
"
1665871,2017-02-18 11:23:18 UTC,"I have experienced this after suspending (and closing the lid) when logged out, but not after suspending while logged in. Cleared by rebooting."
1665874,2017-02-18 10:58:00 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1682
 QMessageLogger::fatal (this=this@entry=0x7ffecedf80d0, msg=msg@entry=0x7f174f099bf7 ""%s"") at global/qlogging.cpp:793
 QSGRenderLoop::handleContextCreationFailure (this=this@entry=0x556018879560, window=0x5560188771a0, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:264
 QSGThreadedRenderLoop::handleExposure (this=this@entry=0x556018879560, window=window@entry=0x5560188771a0) at scenegraph/qsgthreadedrenderloop.cpp:952
 QSGThreadedRenderLoop::exposureChanged (this=0x556018879560, window=0x5560188771a0) at scenegraph/qsgthreadedrenderloop.cpp:890"
1665874,2017-03-29 12:48:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665877,2017-02-21 20:48:07 UTC,This bug is also present in 16.04.2 and 16.10.
1665901,2017-02-24 14:02:00 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1665904,2017-02-20 13:59:29 UTC,The problem continues with kernel 4.10 !!
1665904,2017-03-02 13:24:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665904,2017-04-14 18:52:40 UTC,The problem is still unresolved.
1665907,2017-02-20 05:57:05 UTC,"Im not ready to remove the old sharing interface, if that's what you mean.
Saving changes instantly I have nothing against."
1665907,2017-02-20 10:07:41 UTC,"No, that's not what I meant. This report was about whether it's possible to manage share directories with a single interface that works properly, since that's what other clients and the Web UI are able to do."
1665911,2020-01-09 07:17:45 UTC,"Zesty EOL,
please feel free to open a new bug if you're still encounter this issue with newer releases."
1665911,2017-07-26 15:23:03 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1665911,2017-02-22 17:17:10 UTC,I have tested with 4.10 (linux-image-4.10.0-041000-generic_4.10.0-041000.201702191831_amd64) and can confirm that the lockup can be reproduced in this kernel as well.
1665911,2017-02-21 18:01:41 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1665911,2017-02-20 15:57:48 UTC,Further update: It appears that the lockup happens only when streaming video and not when playing local files. There is a possibility that could be network related. Definitely does not happen with the 4.4x kernel.
1665911,2017-02-18 18:48:40 UTC,"I downgraded the nvidia driver to nvidia-current-updates (304). The system locked-up again while playing videos but this time around it came back for a few seconds. While the mouse and keyboard were not responsive, I was able to see the video move rapidly and my conky scripts were updating for the same period. The logs above are from the session immediately following the hard reset. The only interesting info in the logs is reproproduced below:"
1665911,2017-02-18 18:41:15 UTC,apport information
1665911,2017-02-18 18:41:13 UTC,apport information
1665911,2017-02-18 18:41:10 UTC,apport information
1665911,2017-02-18 18:41:08 UTC,apport information
1665911,2017-02-18 18:40:54 UTC,apport information
1665911,2017-02-18 18:41:02 UTC,apport information
1665911,2017-02-18 18:41:04 UTC,apport information
1665911,2017-02-18 18:30:49 UTC,Changing status to confirmed per instructions received in email. The system crash does not permit apport bug reporting as apport simply doesn't detect a crash. The hard freeze of the system is preventing logs from being written to disk.
1665911,2017-02-18 18:40:48 UTC,apport information
1665911,2017-02-18 18:40:50 UTC,apport information
1665911,2017-02-18 18:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1665911,2017-02-18 18:40:56 UTC,apport information
1665911,2017-02-18 18:40:58 UTC,apport information
1665911,2017-02-18 18:41:00 UTC,apport information
1665911,2017-02-18 18:40:53 UTC,apport information
1665914,2017-02-19 05:44:36 UTC,I have just encountered this same problem. I don't have the stylus but the system does freeze when I touch the screen.
1665914,2017-02-19 21:38:08 UTC,"This issue is probably related to the Wacom driver w8001 (see [1] and [2], thanks [3])."
1665914,2017-02-22 19:48:00 UTC,After installing newer Kernel and X the freezing disappeared and the stylus is working!
1665914,2017-02-25 06:14:37 UTC,Applying those updates fixed it for me as well! Thank you!
1665916,2020-09-15 11:27:42 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1665920,2018-04-27 09:16:58 UTC,I've marked this as wishlist - this is a missing feature.
1665920,2019-11-04 16:28:11 UTC,No longer causes a crash with modern GetDevInfo.
1665920,2019-08-28 09:41:36 UTC,"Note: Since this bug was reported, error handling has been improved significantly both in GetDevInfo and in the dependent programs - this should not cause a crash any more."
1665920,2018-12-06 16:08:22 UTC,"NB: As of newer versions of DDRescue-GUI, this is an issue with the GetDevInfo module. It may not cause crashes anymore, but I will need to check."
1665920,2017-02-27 12:23:29 UTC,This will be fixed in version 1.7.1/1.8
1665920,2017-02-20 12:20:34 UTC,Oh! Which version of DDRescue-GUI are you running?
1665920,2017-02-20 21:30:37 UTC,"^ If so, could you tell me what encryption system this is, because it doesn't look like LUKS to me? I understand if you don't want to say :)"
1665920,2017-02-20 20:50:04 UTC,Thanks!
1665920,2017-02-20 18:06:26 UTC,I can't believe I forgot to type the version number:p.
1665920,2017-02-22 12:16:56 UTC,"Hi,"
1665920,2017-02-20 12:20:02 UTC,"Hi,"
1665922,2020-03-17 12:29:32 UTC,Do you see same warnings with 18.04?
1665936,2017-08-12 21:51:07 UTC,"Could be considered a bug, but it might not be all that easy to fix, given the way fragment_fromstring() is supposed to work."
1665943,2019-02-19 14:33:55 UTC,I've just been able to reproduce this by following these steps:
1665943,2019-02-19 14:35:54 UTC,"(I've added lxd to the bug, as it's also a component in the issue.)"
1665943,2019-02-19 16:57:58 UTC,"Yeah, not much LXD can do about this unfortunately. We do create any missing intermediate directories as can be seen in this case, but there's no good way to know what the owner of every one of those intermediate directories should be, nor would it help here as skel still wouldn't get applied."
1665950,2017-02-24 12:09:45 UTC,"I've added a size2 function that uses IEC units in trunk, but at the moment, I'm not going to change the default menu entries, as reasoning about anything in base-2 units gets really complicated really fast."
1665950,2017-02-24 12:10:53 UTC,"The size2 function will be in the next release, but the default menu entries will not be changed"
1665951,2020-08-04 02:41:02 UTC,"Original bug fixed in 1.0 (still present in 0.92.x); however marking as Fix committed because ""Nicely arrange connectors"" wasn't working until 1.1-dev (see https://gitlab.com/inkscape/inkscape/-/issues/1708), so you still couldn't nicely arrange connectors after opening file."
1665951,2017-02-21 15:52:07 UTC,"Based on tests with archived builds (on OS X 10.7.5):
- not reproduced with Inkscape 0.91 r13725,
- not reproduced with lp:inkscape rev <= 14244,
- reproduced with lp:inkscape rev >= 14245,
- reproduced with Inkscape 0.92.0 r15299, 0.92.1 r15371;
it seems likely that this regression was exposed in the changes of r14245:"
1665952,2017-03-27 07:47:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665952,2017-03-27 08:01:38 UTC,See in file ~/.config/katerc
1665960,2017-02-21 20:09:00 UTC,Does this bug apply if an encapsulation is used? I think the problem is specifically due to the need to apply a flow classifier at every hop of the chain because there is no encapsulation used to uniquely identify traffic that belongs to a chain.
1665960,2017-02-21 21:02:40 UTC,"1.
If the entity is a router created by neutron, then there is no issue
since the commit takes care of this scenario.
E.g."
1665962,2017-02-21 15:29:41 UTC,Indeed.
1665962,2017-02-21 18:34:10 UTC,"Even without the in-target hooks I have been able to get a run in using cloud-init from my ppa by adding it with the apt_config. The config entry I'm using is:
system_upgrade:
    enabled: true
apt:
    preserve_sources_list: false
    sources:
        cloud-init-test-repo.list:
            source: ""deb http://ppa.launchpad.net/wesley-wiedenmeier/test/ubuntu xenial main""
            keyid: 2B91B36D"
1665976,2018-01-16 22:14:06 UTC,"Change abandoned by Michael Glaser (<email address hidden>) on branch: master
Review: https://review.openstack.org/436061
Reason: No reviews after almost a year so will abandon and let someone else give it a go."
1665976,2019-12-18 17:09:53 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/436977
Reason: This repo is retired now, no further work will get merged."
1665976,2018-01-16 22:13:24 UTC,"There have been no reviews for this commit to fix this.
I'll abandon the commit and release the bug to someone else."
1665976,2017-10-23 15:25:49 UTC,"Alexander,"
1665976,2017-10-23 07:29:23 UTC,"Another customer has hit this issue.
Could you please correct the documentation for Mitaka?"
1665976,2017-09-20 06:51:53 UTC,"Change abandoned by Joshua Hesketh (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/436976
Reason: This branch (stable/mitaka) is at End Of Life"
1665976,2017-02-20 15:21:58 UTC,"Michael,"
1665976,2017-02-22 15:14:09 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/436976"
1665976,2017-02-20 16:28:02 UTC,Will unassign myself from the Mitaka change since I'm getting a error when I do a git review for Mitaka and Newton changes:
1665976,2017-02-20 15:26:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436061"
1665976,2017-02-20 14:46:24 UTC,"Alexander, Doesn't this also need to be changed in Newton?"
1665976,2017-02-22 15:14:20 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/436977"
1665979,2017-02-19 08:17:35 UTC,"StacktraceTop:
 __strncmp_ia32 (s1=0x2 <error: Cannot access memory at address 0x2>, s2=0xffab828d ""help"", n=4) at ../string/strncmp.c:42
 _getopt_internal_r (argc=2, argv=0xffab6544, optstring=0x80491e7 ""d:c:"", longopts=0xffab63dc, longind=0xffab63d8, long_only=0, d=<optimized out>, posixly_correct=0) at getopt.c:546
 _getopt_internal (argc=2, argv=0xffab6544, optstring=0x80491e7 ""d:c:"", longopts=0xffab63dc, longind=0xffab63d8, long_only=0, posixly_correct=0) at getopt.c:1175
 getopt_long (argc=2, argv=0xffab6544, options=0x80491e7 ""d:c:"", long_options=0xffab63dc, opt_index=0xffab63d8) at getopt1.c:65
 main (argc=<optimized out>, argv=<optimized out>) at server_control.c:156"
1665979,2017-03-02 19:30:15 UTC,"This is an upstream bug.  I read in a source repository (mirror?)
https://github.com/jackaudio/example-clients/blob/master/server_control.c#L151-L154"
1665986,2017-03-17 19:10:37 UTC,"As I understand now, it disappears only when I reopen switchboard. If I don't close switchboard, it works good."
1665990,2017-02-27 08:14:33 UTC,"Hi,"
1665994,2017-03-14 11:36:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1665994,2018-04-15 01:38:47 UTC,"There are indeed a number of reports of kodi crashing here in launchpad, some of them after the computer was suspended."
1665999,2017-03-08 14:22:51 UTC,"In the bugs.kde.org bugreport, they also report data loss due to this issue."
1665999,2017-03-09 15:25:21 UTC,Am I the only one who uses kate for editing more than 1 file at once?
1666010,2017-02-20 19:46:07 UTC,gnome-panel only calls gmenu_tree_load_sync when it get changed signal. Everything else in stacktrace after that call is in gnome-menus library.
1666010,2017-02-20 19:27:59 UTC,"The library was loaded on the gnome-panel process's behalf, so might as
well be the way that gnome-panel is using it."
1666010,2017-02-19 14:11:41 UTC,"StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f37fe9e6b20 <main_arena>) at malloc.c:4181
 _int_malloc (av=av@entry=0x7f37fe9e6b20 <main_arena>, bytes=bytes@entry=4096) at malloc.c:3448
 __GI___libc_malloc (bytes=4096) at malloc.c:2911
 g_malloc () from /tmp/apport_sandbox_T_V4KC/lib/x86_64-linux-gnu/libglib-2.0.so.0
 menu_realpath.constprop () from /tmp/apport_sandbox_T_V4KC/usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0"
1666010,2017-02-20 15:11:42 UTC,It seems that crash is in gnome-menus library not in panel...
1666018,2017-02-24 14:01:46 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1666018,2017-04-06 00:20:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666055,2017-04-27 23:26:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666055,2017-04-27 23:32:24 UTC,"Hi!
I have just upgraded to ubuntu 17.04. Normal unity works, but unity 8 shows a black screen only.
Video driver data:
* Nvidia binary driver (340.102)
* X.Org X server - Nouveau"
1666056,2017-02-20 22:07:52 UTC,"@Dave Cramer,"
1666056,2017-02-20 22:30:38 UTC,"@Mario,"
1666056,2017-02-20 22:51:51 UTC,Thanks.  A few things stand out here to me.
1666056,2017-02-20 23:05:25 UTC,"On 20 February 2017 at 17:51, Mario Limonciello <email address hidden> wrote:"
1666056,2017-02-20 23:59:58 UTC,Here's the new output after running sudo update-grub
1666073,2017-02-19 23:12:22 UTC,"@Saverio Proto,
Please clarify what version of Juju you are using."
1666073,2017-02-20 06:58:29 UTC,Juju version 2.0.3-xenial-amd64
1666073,2017-03-16 05:21:50 UTC,This will not be addressed in 2.2 due to time and capacity constraints.
1666082,2017-03-02 15:31:39 UTC,"Booting the installer in bios mode uses LILO rather than GRUB, but this isn't a problem with LILO either... it's just a default setting on the cd image."
1666085,2017-02-23 03:33:46 UTC,  Fixed   Linux MInt Mate 32 bit 18.1
1666091,2017-02-25 02:49:13 UTC,My problem is probably with the way my partitions are set up. I have 132gig flash drive that has ubuntu on it my only operating sytem right now. If I take out the flash drive I can't log on to my computer.
1666091,2017-02-20 04:26:42 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1666094,2017-02-26 03:48:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438225"
1666094,2017-03-08 20:56:02 UTC,"Change abandoned by Tin Lam (<email address hidden>) on branch: master
Review: https://review.openstack.org/438225
Reason: going with: https://review.openstack.org/#/c/443303/"
1666095,2020-05-10 09:35:55 UTC,"We have reworked the syncing in Mixxx 2.3 alpha.
I am closing this as won't fix.
Please file a new bug if the new syncing does not work for you."
1666098,2017-02-20 23:09:30 UTC,"nevermind, the tooltip is already there ;-)"
1666098,2017-03-31 22:18:01 UTC,"Hi su_v sorry dont view your reply :(.
Thanks for the feedback I retain the patcvh and add rolando improvement in bug #1510831 and put here the new patch soon. I hope we can close this bug for 0.92 soon and focus on it for 0.93"
1666098,2017-02-20 22:52:47 UTC,"@Jabiertxof - could the warning message be displayed as tooltip somewhere in the expanded 'Viewbox' section, or maybe even better for the (insensitive) 'Scale y:' widget (the tooltip would explain why the option is inactive)?"
1666098,2017-02-20 18:34:33 UTC,"You're not really missing half the dialog, but only the last 3 or 4 lines."
1666098,2017-02-20 22:15:08 UTC,I want to do a simple thing not backported from trunk as a 0.92LTS fix. I also want in the future work over this dialog but for 0.93 and GTK3.
1666098,2017-02-20 22:11:26 UTC,This patch remove the warning message and put it on the disabled Scale Y widget as tooltip
1666098,2017-02-20 22:38:32 UTC,"Earlier reports about the same issue (this report is a duplicate):
* Bug #1510831 “UI: Compact layout for Document Properties (0.92)”
* Bug #1655321 “undocked Document Properties dialog too tall, not resizable”"
1666108,2017-02-20 14:30:38 UTC,"Why is it necessary to change $LANG in the environment on Windows at all? A quick test with 0.92.1 r15371 (64bit, 7z) on Windows 10 shows translated error messages from extensions even if line 57 is commented out:"
1666108,2017-02-20 16:12:52 UTC,Is $LANG set on Windows at all? I don't think so...
1666108,2017-02-20 16:13:37 UTC,P.S. That's probably also the reason why Python ignores the variable on Windows.
1666109,2018-05-19 09:48:42 UTC,apport information
1666109,2018-05-19 09:48:44 UTC,apport information
1666109,2018-05-19 09:48:47 UTC,apport information
1666109,2018-05-19 09:48:49 UTC,apport information
1666109,2018-05-19 09:48:45 UTC,apport information
1666109,2018-05-19 09:48:54 UTC,apport information
1666109,2018-05-19 09:48:58 UTC,apport information
1666109,2018-05-19 09:50:49 UTC,I've just sent apport-collect information.
1666109,2018-06-08 18:37:44 UTC,"Have you tried ""usb-storage.quirks="" [1] ?"
1666109,2018-05-19 09:48:39 UTC,apport information
1666109,2018-05-19 09:48:50 UTC,apport information
1666109,2018-05-19 09:48:36 UTC,apport information
1666109,2018-05-19 09:48:41 UTC,apport information
1666109,2018-05-08 18:02:47 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1666109,2017-02-09 22:28:47 UTC,"Description of problem:
I connect a second USB-UAS drive to the single USB interface card,
the second drive is failed to probe.
When I connect it to another USB interface card, it works fine."
1666109,2017-02-20 04:29:24 UTC,It is not a Fedora specific bug.
1666109,2017-03-07 07:16:22 UTC,"I updated kernel to 4.9.13-200.fc25.x86_64, then more than three uas devices can
be attached. But because of the bug about uas and scsi like:
  https://<email address hidden>/msg60170.html ,
I can't use uas drives properly, furthermore, the USB buses is unstable,
such as keyboard and mouse hung up."
1666109,2017-04-11 14:51:48 UTC,*********** MASS BUG UPDATE **************
1666109,2017-04-12 09:52:50 UTC,"I couldn't find 4.10.9-200.fc25 kernel on the update and dnf repository, but I found 4.10.8-200.fc25, so I test it on 4.10.8-200.fc25 kernel."
1666109,2017-02-10 03:59:54 UTC,"I've changed title.
When I connected 3rd USB-UAS device, uas module fails to probe it.
And when I connected 2 drives on the same USB interface card, it was OK."
1666109,2017-04-12 11:43:58 UTC,This problem occurs in Fedora 26 Alpha 4.11.0-0.rc5.git0.1.fc26.x86_64 kernel.
1666109,2017-04-12 10:16:20 UTC,This problem occurs both 512 bytes sector and 4KB sector disks.
1666109,2017-04-17 12:17:52 UTC,I made a mistake.
1666109,2018-05-19 09:48:34 UTC,apport information
1666109,2017-04-17 12:16:13 UTC,"This bug is still alive.
(1) I *can* attach more than three uas devices, but
(2) I/O information, which I can get from /sys/block/sd*/queue, is strange,
(3) parted and LVM can't calculate optimal disk geometries."
1666109,2017-04-17 11:59:36 UTC,Updated in accord with RedHat bugzilla.
1666125,2017-03-01 18:06:11 UTC,"Weird:
a"
1666138,2017-02-20 23:06:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666151,2017-02-21 16:38:34 UTC,1) A Totem does not recognise it *.m4a file
1666151,2017-02-23 14:03:56 UTC,"2017-02-21 14:51 keltezéssel, GautierPortet írta:

> Can you please try to read the file with totem (they use the same
> libraries) ?
>
> ** Changed in: soundconverter (Ubuntu)
>      Assignee: (unassigned) => GautierPortet (kassoulet)
>


Today new (gstreamer1.0-libav) libav plugin for GStreamer and *.m4a
converting working in the Soundconverter!!!"
1666151,2017-02-21 13:51:27 UTC,Can you please try to read the file with totem (they use the same libraries) ?
1666151,2017-02-20 16:15:44 UTC,Debug info:
1666151,2017-02-20 16:52:39 UTC,Newest debug info:
1666160,2017-04-19 09:19:05 UTC,Perhaps different error codes depending on the exception would be the obvious option.
1666160,2017-09-15 14:57:58 UTC,This can actually be implemented now by adding get_exit_code to error subclasses in snapcraft/internal/errors.py
1666161,2017-02-20 19:14:47 UTC,"> [A] ""dry run"" build that does everything involving the snapcraft.yaml but does not perform the actual build.
"
1666161,2017-04-22 04:17:33 UTC,[Expired for Snapcraft because there has been no activity for 60 days.]
1666161,2017-04-24 12:20:18 UTC,"Hi Kyle,"
1666166,2017-03-13 18:41:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666166,2017-11-13 11:14:06 UTC,"A possible workaround that worked for me is to use the packages from openafs directly:
sudo add-apt-repository ppa:openafs/stable
sudo apt-get update
as described in https://launchpad.net/~openafs/+archive/ubuntu/stable"
1666166,2018-02-03 08:24:57 UTC,The ppa:openafs/stable workaround restored AFS client service to my machine (which had been lost after I switched to the HWE kernel in early January 2018).  Currently running openafs-client 1.6.22-3~ppa0~ubuntu16.04.1.
1666168,2017-05-10 04:17:32 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1666168,2017-03-10 12:41:46 UTC,i mean.. i can't test if it crashes unity8 because the snaps don't start :o)
1666168,2017-03-10 12:39:30 UTC,"oh sorry, i forgot about this bug. so now the snaps just don't run, it doesn't crash unity8 anymore"
1666168,2017-03-10 12:01:31 UTC,"Do you have a .crash file, @dinamic?"
1666168,2017-02-21 20:11:52 UTC,"same with ubuntu filemanager app snap, closing the app crashes/restarts unity8"
1666168,2017-03-10 10:56:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666170,2017-02-20 10:12:39 UTC,maximized
1666176,2017-03-09 12:21:35 UTC,Several latest 10.0.main.ubuntu.bvt_2 builds were successful (https://product-ci.infra.mirantis.net/job/10.0.main.ubuntu.bvt_2/1364/).
1666176,2017-02-20 10:39:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/435928"
1666176,2017-02-21 13:44:55 UTC,"Reviewed:  https://review.openstack.org/435928
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=b2024b95e1c765e789bb3412672ff219ed7e0a5e
Submitter: Jenkins
Branch:    master"
1666176,2017-02-22 10:01:55 UTC,"Many jobs failed without apparmor installed
* https://product-ci.infra.mirantis.net/job/10.0.main.ubuntu.bvt_2/1301/
* https://product-ci.infra.mirantis.net/job/10.0.main.ubuntu.bvt_2/1300/
* https://product-ci.infra.mirantis.net/job/10.0.main.ubuntu.bvt_2/1299/"
1666176,2017-02-22 10:08:31 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/436853"
1666176,2017-02-22 14:48:36 UTC,"Reviewed:  https://review.openstack.org/436853
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=03ccb82d38b014caa86585e28bbb72b3f156221e
Submitter: Jenkins
Branch:    stable/newton"
1666176,2017-02-27 16:28:35 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc1 release candidate.
1666178,2017-02-23 03:11:12 UTC,"OK, from the duplicate bug I can see the common theme. We either have buggy toolkits, or just some legacy apps expect to create ""modal"" dialogs without a parent window. I'm not sure if that's an app bug, but Mir will certainly abort() if you ask for that."
1666178,2017-02-28 02:24:51 UTC,another crash with terminix https://bugs.launchpad.net/ubuntu/+source/terminix/+bug/1668473
1666178,2017-02-20 10:43:17 UTC,"StacktraceTop:
 require () at ./src/include/common/mir/require.h:28
 mir_create_modal_dialog_window_spec (connection=0x55a59cc97960, width=539, height=164, parent=0x0) at ./src/client/mir_surface_api.cpp:108
 mir_connection_create_spec_for_modal_dialog (connection=<optimized out>, width=<optimized out>, height=<optimized out>, format=mir_pixel_format_argb_8888, parent=<optimized out>) at ./src/client/mir_surface_api.cpp:931
 create_window_type_spec (buffer_usage=<optimized out>, type=<optimized out>, modal=<optimized out>, height=<optimized out>, width=<optimized out>, y=0, x=0, parent=0x0, display=0x55a59cc9a040) at ././gdk/mir/gdkmirwindowimpl.c:385
 create_spec (window=window@entry=0x55a59dcdeaf0, impl=impl@entry=0x55a59d6d9e70) at ././gdk/mir/gdkmirwindowimpl.c:431"
1666178,2017-02-21 01:26:39 UTC,"It's apparently a GTK bug, failing to pass a parent pointer:"
1666178,2017-02-24 05:36:54 UTC,Seems like the right answer in some cases might be:
1666181,2017-02-20 10:55:40 UTC,"StacktraceTop:
 ?? ()
 make_protobuf_object () at ./src/client/rpc/../make_protobuf_object.h:29
 mir::client::rpc::MirProtobufRpcChannel::on_data_available() (this=0x55f332d2c410) at ./src/client/rpc/mir_protobuf_rpc_channel.cpp:457
 operator() () at ./src/client/rpc/stream_socket_transport.cpp:40
 _ZNSt17_Function_handlerIFvRKSt10shared_ptrIN3mir6client3rpc15StreamTransport8ObserverEEEZNS3_18TransportObservers17on_data_availableEvEUlT_E_E9_M_invokeERKSt9_Any_dataS8_.lto_priv.368 (__functor=..., __args#0=...) at /usr/include/c++/6/functional:1731"
1666181,2017-08-21 08:52:18 UTC,Probably the same cause as lp:1675749 (but not marking as dup yet as need to confirm the problem isn't gtk-mir/qtubuntu)
1666181,2017-11-03 15:24:23 UTC,Syncing task from Mir.
1666187,2017-03-25 09:48:42 UTC,"My bad, I mixed up bug reports :-) Filed to many lately!!
Please ignore my comment above. Thanks!"
1666187,2017-03-25 09:37:00 UTC,"I tested with InnoDB, same as Oracle bug. While bug #1671152 is about TokuDB."
1666187,2017-03-25 08:42:47 UTC,This should be the same bug fixed in https://bugs.launchpad.net/percona-server/+bug/1671152
1666187,2017-03-24 22:50:09 UTC,On the attached dump run following queries to repeat with 5.6:
1666187,2017-03-24 22:47:13 UTC,Not repeatable with 5.7
1666187,2017-02-22 18:14:18 UTC,"This is actually an optimizer bug, see upstream bug report."
1666187,2017-02-22 10:42:59 UTC,Upstream bug: https://bugs.mysql.com/bug.php?id=85126
1666187,2017-02-22 10:07:23 UTC,"Looks like an upstream bug, except in Oracle MySQL, it is *much* worse, as the optimizer *always* prefers the index on EXPIRE_DATE, even if cardinality of that index is almost zero:"
1666187,2017-02-21 20:58:05 UTC,"Please note - output of processlist is truncated, but all the DELETEs are of this type:"
1666187,2018-01-25 08:36:12 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1063
1666187,2017-02-21 20:56:01 UTC,"From further testing, it seems that the problem is due to one of the DELETEs not using the index on HASH_ID and performing a full table scan, locking all encountered rows in the process."
1666187,2017-02-21 20:20:10 UTC,It also looks to be tied to the presence of partitioning.
1666187,2017-02-21 14:39:06 UTC,I confirm that this problem only hits when there is no primary key in the table.
1666187,2017-02-21 09:36:41 UTC,"Updated bug title to the above effect.
This is a table without an explicit primary key.
Will try now to add a primary key and see if the problem persists."
1666187,2017-02-21 09:34:09 UTC,"We just tested this using InnoDB and guess what, the problem is not inside Toku, it is at the upper layer (MySQL)!"
1666187,2017-02-20 11:06:40 UTC,"Forget to mention...
Server version:		5.6.35-80.0-log Percona Server (GPL), Release 80.0, Revision f113994f31"
1666187,2017-02-21 21:04:08 UTC,"Wait, just found that the optimizer *randomly* seems to prefer the index on EXPIRE_DATE instead of the one on HASH_ID for the DELETEs......"
1666192,2017-04-10 10:12:13 UTC,Verified on 10.0 build #1569.
1666192,2017-03-29 17:26:25 UTC,"Reviewed:  https://review.openstack.org/450814
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e4290053d9623c332831e6b546355dccb5731c5b
Submitter: Jenkins
Branch:    stable/newton"
1666192,2017-03-27 16:46:11 UTC,"We set node progress to 1 when we start the deployment, but we do not set it to 100 if the node has no tasks to run. We do not now which particular node have 0 tasks as graph serialization runs right before casting the message to Astute. This should be fixed on Astute size by sending node progress set to 100 for the nodes that do not have any tasks to run."
1666192,2017-03-28 14:26:55 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/450814"
1666194,2017-02-27 14:05:43 UTC,"Why the change back to in progress?  The fix was merged, fixed, and committed."
1666200,2017-02-21 12:12:30 UTC,Can't reproduce.
1666201,2020-04-27 22:24:35 UTC,"I have the same issue on Debian 10.3 with MATE.
Strangely enough, I have another laptop with the same setup, and I have never seen it there, I didn't even know this issue exists. Not sure if any of the apps I have installed make the difference (I don't have the above mentioned libremenu installed, i don't even see it in repos)."
1666201,2018-04-03 21:41:24 UTC,"Also see this post on Fedora questions:
https://ask.fedoraproject.org/en/question/102314/removing-mate-panel-dock-icon-from-plank/"
1666201,2018-02-12 10:14:06 UTC,This problem it's in 18.04 daily
1666201,2017-04-20 19:50:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666201,2017-02-21 13:40:40 UTC,"OS: Ubuntu 16.04.2
Interface : Mate 1.12.1 (default) and Mate 1.16.1 (ppa)"
1666201,2017-03-18 22:49:47 UTC,Please also raise the issue upstream:
1666203,2019-03-01 01:49:44 UTC,"[VERIFICATION BIONIC]
It has been brought to my attention the following (by an impacted user):"
1666203,2019-03-01 09:59:45 UTC,Sorry for the delay and thanks for the feedback and effort Eric!
1666203,2019-03-01 10:17:42 UTC,[VERIFICATION COSMIC]
1666203,2019-03-05 21:39:43 UTC,"@Donvdh,"
1666203,2019-03-07 17:32:23 UTC,This bug was fixed in the package pam - 1.1.8-3.6ubuntu3
1666203,2019-03-07 17:32:30 UTC,"The verification of the Stable Release Update for pam has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1666203,2019-03-07 17:32:52 UTC,This bug was fixed in the package pam - 1.1.8-3.6ubuntu2.18.04.1
1666203,2019-04-20 19:00:53 UTC,Uploaded to Xenial.
1666203,2019-05-01 13:30:27 UTC,"Hello Toru, or anyone else affected,"
1666203,2019-02-05 10:23:36 UTC,"Don, I've looked closer at the code and I agree with you."
1666203,2019-05-10 10:16:28 UTC,Hi Don-san.
1666203,2020-04-10 01:47:18 UTC,"All autopkgtests for the newly accepted pam (1.1.8-3.2ubuntu2.2) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:"
1666203,2020-05-19 18:01:43 UTC,Hello!
1666203,2020-07-28 17:51:27 UTC,@David have you tested the version of the package in -proposed and does it work for you? If so could you please provide testing details so that we can release the package.
1666203,2020-09-30 21:11:53 UTC,The version of pam in the proposed pocket of Xenial that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1666203,2020-10-01 00:32:53 UTC,"Hello Toru, or anyone else affected,"
1666203,2020-10-01 04:12:09 UTC,"All autopkgtests for the newly accepted pam (1.1.8-3.2ubuntu2.3) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:"
1666203,2020-10-01 08:22:44 UTC,Verified the new upload on xenial:
1666203,2020-10-12 13:17:34 UTC,This bug was fixed in the package pam - 1.1.8-3.2ubuntu2.3
1666203,2019-02-28 13:32:52 UTC,"Hello Toru, or anyone else affected,"
1666203,2019-05-06 20:58:46 UTC,Thanks!
1666203,2019-02-28 13:30:49 UTC,"Hello Toru, or anyone else affected,"
1666203,2019-02-05 02:23:11 UTC,"Hello Don, probably an SRU sponsor would like the debdiff to include references where to find the patch that you applied in upstream sources or other bug reports. The usual way to do so is via a Description: and Origin: header in the patch, see https://dep-team.pages.debian.net/deps/dep3/ for more information."
1666203,2019-02-28 01:37:11 UTC,"Don,"
1666203,2017-04-21 14:49:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666203,2019-01-13 14:58:52 UTC,Please see https://wiki.ubuntu.com/SponsorshipProcess and https://wiki.ubuntu.com/StableReleaseUpdates#Procedure if you can volunteer to get the fix landed. Note that I don't expect anyone to work on this any time soon. It needs volunteers.
1666203,2019-02-03 01:07:30 UTC,"Attached patch (which is based on pam_1.1.8-3.6ubuntu2) fixes the issue for Ubuntu 18.04/Bionic
Following fix was implemented as mentioned by the reporter of the LP bug: https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee"
1666203,2019-02-28 01:59:24 UTC,Uploaded for Bionic and Cosmic.
1666203,2019-02-03 09:53:25 UTC,"I am unable to reproduce this issue on Ubuntu 16.04/Xenial with:
libpam-modules 1.1.8-3.2ubuntu2.1
kernel 4.4.0-112-generic"
1666203,2019-02-04 06:57:03 UTC,Thank you for your response.
1666203,2019-02-04 14:20:20 UTC,I also tested with commit https://github.com/linux-pam/linux-pam/commit/05a1ccc0df92d0ca031699124ddf7ec3ce12f78f#diff-c5b734a338a8a0460af7f0c08a7b138a which fixes yet another uninitialized use.
1666203,2019-02-04 20:46:08 UTC,Thank you both very much for the responses.
1666203,2019-02-05 09:28:57 UTC,Hi Don-san.
1666203,2019-02-03 04:18:29 UTC,"The attachment ""bionic-fix-for-lp-1666203.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1666203,2019-02-05 21:53:56 UTC,"Please see attached patch for Ubuntu 16.04/Xenial.
I have tested and verified that the patch works as intended."
1666203,2019-02-13 06:24:00 UTC,This has been fixed for disco with the upload of pam 1.3.1-2ubuntu1.
1666203,2019-02-15 08:13:07 UTC,Thanks Steve!
1666203,2019-02-15 15:54:29 UTC,I have opened bug tasks for the bionic and xenial releases.  Your patches are in the queue for the ubuntu-sponsors team to review.
1666203,2019-02-19 15:11:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666203,2019-02-26 18:00:41 UTC,"Don van der Haghen (donvdh),"
1666203,2019-02-26 18:05:19 UTC,"and could you please fill the SRU template ?
https://wiki.ubuntu.com/StableReleaseUpdates"
1666203,2019-02-28 00:55:14 UTC,I have provided a test package to an impacted user for Bionic/18.04LTS.
1666203,2019-02-05 21:14:19 UTC,Thank you all very much for the responses.
1666205,2017-03-05 20:01:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666205,2017-03-26 21:19:32 UTC,I subsequently ran it from the terminal. The application started faultlessly. It seems to do now including from the dash or the application overview.
1666205,2017-02-20 13:15:25 UTC,"StacktraceTop:
 get_start_of_week (date=0x0) at gcal-utils.c:534
 gcal_week_header_add_event (self=0x5610786fa140, event=0x561078987dc0) at views/gcal-week-header.c:1580
 cal_data_model_add_to_subscriber (data_model=data_model@entry=0x56107617c1c0, client=<optimized out>, id=<optimized out>, component=<optimized out>, instance_start=<optimized out>, instance_end=<optimized out>, user_data=0x56107634d350) at e-cal-data-model.c:1740
 cal_data_model_foreach_component (data_model=data_model@entry=0x56107617c1c0, in_range_start=in_range_start@entry=1486940400, in_range_end=in_range_end@entry=1487545200, func=func@entry=0x561074b1cd40 <cal_data_model_add_to_subscriber>, user_data=user_data@entry=0x56107634d350, include_lost_components=include_lost_components@entry=1) at e-cal-data-model.c:2565
 e_cal_data_model_subscribe (data_model=0x56107617c1c0, subscriber=0x56107634d350, range_start=1486940400, range_end=1487545200) at e-cal-data-model.c:2761"
1666209,2017-02-20 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1666209,2017-02-20 15:27:22 UTC,Can you test the latest upstream stable kernel to see if this regression is already fixed?  It can be downloaded from:
1666209,2017-02-21 10:00:14 UTC,"Sorry for a long time to answer and no logs. We've been testing the problem on irc channel. It turns out that the new kernel assigns new names to the network interfaces i.e. the original name (in kernel 62) was enP3168p5s3 and the new kernel assigned the same card and the same interface a new name - enP64624p5s3, therefore - no network obviously, as the /network/interfaces file contained old names. After submitting new names to the config file, the network is up and stable."
1666209,2017-03-05 21:31:14 UTC,"I am having exactly the same problem as reported as Bug #1666209, ever since I updated from 4.4.0-62. The last working kernel is 4.4.0-62. May I expect that the problem will be solved by an automatic update of the kernel? Or can I do something to repair it myself?"
1666209,2017-03-05 22:15:47 UTC,"I am not sure anyone is actually looking into it. Updating to kernel version 64 resulted it system assigning yet another new name for the interfaces, which in turn screwed up the networking. In my case, as I was ready for that, I just listed what the system now called the interfaces, edited the /etc/network/interfaces file to include the new names and, after a reboot, the system got connected. It is a workaround, but that's
 all I can do for now."
1666209,2017-03-16 12:22:01 UTC,"Additional bump - on kernel version 67 now and the issue still exists. Every time a new kernel installs, after a reboot the network interface names are changed (mostly digits inside the enP--->p5s3 mask in my case)"
1666209,2017-03-16 16:14:21 UTC,Can you test the latest upstream stable kernel to see if this regression is already fixed? It can be downloaded from:
1666209,2017-03-16 16:54:06 UTC,Hard to say at the moment. The machine is on 24/7 and is serving a rather large company. I might be able to try to shut it down for sometime late Friday. But can't promise anything. If I do should expect the mainline kernel NOT to change the interfaces names ?
1666210,2015-04-28 13:37:10 UTC,"Copying or moving files will be interrupted when there's a user interaction required, for example to decide whether a file should overwritten etc."
1666211,2017-05-25 19:44:51 UTC,"Change abandoned by Andre Aranha (<email address hidden>) on branch: master
Review: https://review.openstack.org/377106
Reason: python-oneviewclient will be migrated to hponeview, and this modification will be implemented there"
1666211,2017-03-01 12:50:58 UTC,The patch is here - https://review.openstack.org/377106.
1666211,2017-04-04 21:15:02 UTC,"OK, so the issue here is, the oneview ml2 driver relies on the information stored in switch_info, and you need a way to validate it. Maybe a thin wrapper around neutron network interface that would do the validation you need while not giving the impression that this is now required for all network interfaces is an option for you? I don't see other way to solve it ATM, so confirming."
1666212,2018-08-12 16:02:35 UTC,Is this fix still need as of byobu 5.127?  The current code says this:
1666212,2018-05-14 07:05:57 UTC,Same here on Ubuntu 16.04. eviweb's suggestion fixed the issue.
1666212,2017-07-27 09:11:52 UTC,"Hi,
I just encountered this issue, and I can confirm that the fix works.
For me it had to be inserted in the tmux call of the attach_session function, like below :"
1666212,2017-08-02 18:22:00 UTC,"That fix works for me, too. I've had that problem for years on new installations. Please introduce the patch."
1666212,2017-08-04 12:43:55 UTC,"Hi,"
1666214,2017-02-22 09:10:33 UTC,"        tests ran:  10, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/s2lp6g003__4.10.0-9.11__2017-02-22_08-33-00/results-index.html"
1666214,2017-02-22 08:36:47 UTC,"        tests ran:  37, failed: 37;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-34-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_08-33-00/results-index.html"
1666214,2017-02-22 08:20:19 UTC,"        tests ran:  19, failed: 16;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/kernel03__4.10.0-9.11__2017-02-22_08-12-00/results-index.html"
1666214,2017-02-22 08:03:57 UTC,"        tests ran:  16, failed: 4;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-34-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_07-44-00/results-index.html"
1666214,2017-02-22 07:58:55 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/modoc__4.10.0-9.11__2017-02-22_07-28-00/results-index.html"
1666214,2017-02-22 07:58:32 UTC,"        tests ran:  64, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-22_07-16-00/results-index.html"
1666214,2017-02-22 07:58:11 UTC,"        tests ran:  37, failed: 37;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-35-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_07-54-00/results-index.html"
1666214,2017-02-22 07:46:31 UTC,"        tests ran:   5, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/kernel03__4.10.0-9.11__2017-02-22_05-32-00/results-index.html"
1666214,2017-02-22 07:26:20 UTC,"        tests ran:  16, failed: 4;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-35-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_07-05-00/results-index.html"
1666214,2017-02-22 07:15:42 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-34-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_06-21-00/results-index.html"
1666214,2017-02-22 06:44:57 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/modoc__4.10.0-9.11__2017-02-22_06-38-00/results-index.html"
1666214,2017-02-22 06:36:03 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-35-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_05-43-00/results-index.html"
1666214,2017-02-22 06:33:40 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-22_06-25-00/results-index.html"
1666214,2017-02-22 05:52:20 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-34-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_05-47-00/results-index.html"
1666214,2017-02-22 05:34:10 UTC,"        tests ran:  16, failed: 3;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/modoc__4.10.0-9.11__2017-02-22_05-07-00/results-index.html"
1666214,2017-02-22 05:31:02 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/naumann__4.10.0-9.11__2017-02-22_04-58-00/results-index.html"
1666214,2017-02-22 09:44:10 UTC,"        tests ran: 141, failed: 90;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/modoc__4.10.0-9.11__2017-02-22_09-08-00/results-index.html"
1666214,2017-02-22 05:18:24 UTC,"        tests ran:  64, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-34-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_04-44-00/results-index.html"
1666214,2017-02-22 09:46:17 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/secchi__4.10.0-9.11__2017-02-22_08-58-00/results-index.html"
1666214,2017-02-22 10:49:04 UTC,"        tests ran:  37, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-22_09-11-00/results-index.html"
1666214,2017-03-02 13:53:46 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/amaura__4.10.0-9.11__2017-03-02_13-24-00/results-index.html"
1666214,2017-03-02 03:04:10 UTC,"        tests ran:   3, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-03-02_02-47-00/results-index.html"
1666214,2017-03-02 00:15:42 UTC,The package has been published and the bug is being set to Fix Released
1666214,2017-03-01 22:33:45 UTC,This bug was fixed in the package linux - 4.10.0-9.11
1666214,2017-03-01 07:54:16 UTC,"        tests ran:  10, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/kernel03__4.10.0-10.12__2017-03-01_07-14-00/results-index.html"
1666214,2017-02-24 14:12:54 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/amaura__4.10.0-9.11__2017-02-24_14-07-00/results-index.html"
1666214,2017-02-24 13:06:52 UTC,"        tests ran:  10, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-02-24_12-27-00/results-index.html"
1666214,2017-02-24 12:27:02 UTC,"        tests ran:  20, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-02-24_11-47-00/results-index.html"
1666214,2017-02-24 11:47:31 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-02-24_11-34-00/results-index.html"
1666214,2017-02-24 08:05:31 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-02-24_08-02-00/results-index.html"
1666214,2017-02-24 08:02:44 UTC,"        tests ran: 141, failed: 28;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-02-24_07-39-00/results-index.html"
1666214,2017-02-24 07:39:35 UTC,"        tests ran:  38, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-02-24_06-35-00/results-index.html"
1666214,2017-02-24 06:35:51 UTC,"        tests ran:  16, failed: 4;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-02-24_06-22-00/results-index.html"
1666214,2017-02-24 06:22:49 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-10.12-generic/s2lp6g003__4.10.0-10.12__2017-02-24_06-20-00/results-index.html"
1666214,2017-02-23 05:12:00 UTC,"        tests ran:  10, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-35-mcdivittB0-kernel__4.10.0-9.11__2017-02-23_04-10-00/results-index.html"
1666214,2017-02-22 12:15:21 UTC,"        tests ran:  64, failed: 64;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/gonzo__4.10.0-9.11__2017-02-22_09-00-00/results-index.html"
1666214,2017-02-22 12:11:36 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-22_11-26-00/results-index.html"
1666214,2017-02-22 10:39:09 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/secchi__4.10.0-9.11__2017-02-22_10-08-00/results-index.html"
1666214,2017-02-22 05:13:33 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-35-mcdivittB0-kernel__4.10.0-9.11__2017-02-22_05-08-00/results-index.html"
1666214,2017-02-22 05:31:40 UTC,"        tests ran:  37, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/kernel03__4.10.0-9.11__2017-02-22_04-10-00/results-index.html"
1666214,2017-02-22 00:10:00 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/gonzo__4.10.0-9.11__2017-02-21_23-19-00/results-index.html"
1666214,2017-02-21 20:01:35 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/naumann__4.10.0-9.11__2017-02-21_19-59-00/results-index.html"
1666214,2017-02-22 00:12:53 UTC,"        tests ran:  10, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-34-mcdivittB0-kernel__4.10.0-9.11__2017-02-21_23-05-00/results-index.html"
1666214,2017-02-21 19:58:35 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/secchi__4.10.0-9.11__2017-02-21_19-56-00/results-index.html"
1666214,2017-02-21 15:50:29 UTC,"        tests ran:  19, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-21_14-49-00/results-index.html"
1666214,2017-02-21 14:12:40 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-21_14-10-00/results-index.html"
1666214,2017-02-21 11:31:06 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/fozzie__4.10.0-9.11__2017-02-21_11-28-00/results-index.html"
1666214,2017-02-21 10:12:13 UTC,"        tests ran: 141, failed: 28;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/kernel03__4.10.0-9.11__2017-02-21_09-35-00/results-index.html"
1666214,2017-02-21 20:01:40 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/gonzo__4.10.0-9.11__2017-02-21_19-59-00/results-index.html"
1666214,2017-02-21 10:00:41 UTC,"        tests ran: 141, failed: 28;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/s2lp6g003__4.10.0-9.11__2017-02-21_09-36-00/results-index.html"
1666214,2017-02-21 09:35:55 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/kernel03__4.10.0-9.11__2017-02-21_09-33-00/results-index.html"
1666214,2017-02-21 09:33:25 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/s2lp6g003__4.10.0-9.11__2017-02-21_09-20-00/results-index.html"
1666214,2017-02-21 09:33:10 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/kernel03__4.10.0-9.11__2017-02-21_09-20-00/results-index.html"
1666214,2017-02-21 09:20:51 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/s2lp6g003__4.10.0-9.11__2017-02-21_09-19-00/results-index.html"
1666214,2017-02-21 09:20:36 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/kernel03__4.10.0-9.11__2017-02-21_09-18-00/results-index.html"
1666214,2017-02-21 09:06:11 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/kernel03__4.10.0-8.10__2017-02-21_09-04-00/results-index.html"
1666214,2017-02-21 09:05:54 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-8.10-generic/s2lp6g003__4.10.0-8.10__2017-02-21_09-03-00/results-index.html"
1666214,2017-02-21 09:36:07 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/s2lp6g003__4.10.0-9.11__2017-02-21_09-33-00/results-index.html"
1666214,2017-02-21 20:11:12 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/modoc__4.10.0-9.11__2017-02-21_20-09-00/results-index.html"
1666214,2017-02-21 19:59:37 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/fozzie__4.10.0-9.11__2017-02-21_19-57-00/results-index.html"
1666214,2017-02-21 20:25:15 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/fozzie__4.10.0-9.11__2017-02-21_20-23-00/results-index.html"
1666214,2017-02-21 23:33:58 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-21_22-20-00/results-index.html"
1666214,2017-02-21 22:59:03 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/secchi__4.10.0-9.11__2017-02-21_21-39-00/results-index.html"
1666214,2017-02-21 22:55:32 UTC,"        tests ran:   6, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/gonzo__4.10.0-9.11__2017-02-21_22-04-00/results-index.html"
1666214,2017-02-21 22:52:52 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/modoc__4.10.0-9.11__2017-02-21_21-59-00/results-index.html"
1666214,2017-02-21 20:12:12 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-21_20-10-00/results-index.html"
1666214,2017-02-21 22:47:17 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/naumann__4.10.0-9.11__2017-02-21_21-28-00/results-index.html"
1666214,2017-02-21 22:36:51 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-35-mcdivittB0-kernel__4.10.0-9.11__2017-02-21_22-34-00/results-index.html"
1666214,2017-02-21 22:36:35 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/ms10-34-mcdivittB0-kernel__4.10.0-9.11__2017-02-21_22-34-00/results-index.html"
1666214,2017-02-21 22:49:24 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/fozzie__4.10.0-9.11__2017-02-21_21-59-00/results-index.html"
1666214,2017-02-21 21:44:08 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/rumford__4.10.0-9.11__2017-02-21_20-48-00/results-index.html"
1666214,2017-02-21 21:41:28 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/gonzo__4.10.0-9.11__2017-02-21_20-50-00/results-index.html"
1666214,2017-02-21 21:36:09 UTC,"        tests ran:  19, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/fozzie__4.10.0-9.11__2017-02-21_20-47-00/results-index.html"
1666214,2017-02-21 21:25:46 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/modoc__4.10.0-9.11__2017-02-21_20-43-00/results-index.html"
1666214,2017-02-21 21:17:24 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/secchi__4.10.0-9.11__2017-02-21_20-20-00/results-index.html"
1666214,2017-02-21 21:04:12 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/naumann__4.10.0-9.11__2017-02-21_20-26-00/results-index.html"
1666214,2017-02-21 20:53:10 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/pepe__4.10.0-9.11__2017-02-21_20-01-00/results-index.html"
1666214,2017-02-21 20:27:00 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/gonzo__4.10.0-9.11__2017-02-21_20-25-00/results-index.html"
1666214,2017-02-21 22:07:47 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-9.11-generic/pepe__4.10.0-9.11__2017-02-21_21-18-00/results-index.html"
1666215,2017-02-21 14:02:11 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/436468"
1666215,2017-03-03 07:54:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440969"
1666215,2017-03-23 08:15:48 UTC,"Reviewed:  https://review.openstack.org/436468
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=a9df5d62083a5ab6ce9ea24d20c8ce430d856f12
Submitter: Jenkins
Branch:    stable/newton"
1666215,2019-12-18 17:30:16 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/440969
Reason: This repo is retired now, no further work will get merged."
1666216,2019-08-09 10:12:39 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016."
1666223,2017-03-01 13:59:26 UTC,What do you mean by ipv4 address? The node does not have an ip address field. Please add more information about the issue.
1666223,2017-03-10 18:16:42 UTC,Hello m-nitesh:
1666223,2017-03-14 05:03:04 UTC,Hi Michael Turek:
1666223,2017-05-18 08:05:32 UTC,"hello MVPN, just as we talked in IRC, i'll assign this bug to me, thanks!"
1666223,2017-05-18 08:30:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465866"
1666230,2017-02-20 14:49:28 UTC,https://github.com/matplotlib/matplotlib/issues/8107
1666235,2019-04-24 20:38:04 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/452251
Reason: role retired"
1666235,2017-03-31 15:47:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452251"
1666251,2017-02-27 08:03:23 UTC,"Hi,"
1666253,2017-02-22 20:41:34 UTC,"snapd-xdg-open ftbfs on trusty, https://github.com/snapcore/snapd-xdg-open/pull/20 fixes the build and will allow us to SRU snapd-xdg-open."
1666257,2017-02-20 16:33:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1666257,2017-02-20 16:47:35 UTC,Could not find a right source package. Chose the closest one 'wireless-crda'. Please assign it to the right component.
1666259,2017-02-20 18:15:37 UTC,"Checking on real hardware, I cannot reproduce this."
1666259,2017-02-20 18:27:27 UTC,Interestingly QtUbuntu doesn't call mir_buffer_is_valid or mir_buffer_release itself. I don't see any evidence that is Qt is destroying/recreating its surface either. Odd
1666259,2017-02-21 01:21:41 UTC,What is your KVM/Qemu configuration?
1666259,2017-02-21 10:25:02 UTC,I used whatever virtual machine manager chose as default:
1666259,2017-11-03 15:24:30 UTC,Syncing task from Mir.
1666260,2017-03-21 08:19:29 UTC,I can confirm hitting this on 4.8.41 as well.
1666260,2017-03-21 18:37:35 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1666260,2017-03-25 03:14:11 UTC,I've tried setting vm.vfs_cache_pressure = 300 per the top post and still seeing regular (daily) oom's on 4.4.0-66-generic
1666260,2017-02-23 10:29:36 UTC,And again on 4.8.0-36.  Upgraded server to 4.8.0-39.
1666260,2017-12-16 11:38:16 UTC,"As original poster, if I didn't continue to post oom dumps, perhaps things started to peter out on 4.8.0-39 or later."
1666260,2017-12-16 11:39:42 UTC,"Servers are now running on 4.10 kernels, so I guess no one cares about 4.8 anymore."
1666260,2017-02-27 11:16:07 UTC,Another 4 servers OOM'd on 4.8.0-36 over the weekend.  Upgraded to 4.8.0-39
1666260,2017-03-25 05:32:04 UTC,"I have only been able to reproduce this on our production workloads, and we've recently downgraded from HWE (4.8.0-X) to GA (4.4.0-66), where we currently aren't seeing any issues."
1666260,2017-02-24 13:39:24 UTC,And again on 4.8.0-36. Upgraded server to 4.8.0-39. (How many times must I keep on doing this?)
1666260,2017-02-20 16:30:12 UTC,This change was made by a bot.
1666260,2017-02-21 16:20:15 UTC,"No OOM on servers running 4.4.0-63 just yet, but the memory usage on them is weird to say the least.  The Buffer/SLAB ratio is completely different from 4.4.0-57."
1666260,2017-02-21 16:16:54 UTC,And 4.8.0-36 is affected by bug also.
1666260,2017-02-20 18:41:22 UTC,Attaching current slabtop
1666260,2017-02-20 18:34:06 UTC,SLAB is still dropping.
1666260,2017-02-20 18:16:45 UTC,I think this is currently in the middle of happening right now on one of the servers running 4.4.0-63.
1666260,2017-02-20 16:33:14 UTC,"Attaching the call trace for 4.8.0-34, this is from Feb 19th."
1666260,2017-02-20 16:32:02 UTC,"Attaching the call trace for 4.4.0-59, this is from Jan 16th."
1666267,2017-02-28 18:17:03 UTC,"Will beta channel remain? If folks are like myself, edge is just tip and really unversioned -- it will never release. Beta and up we'd seek to roll builds down for releasing."
1666267,2017-02-27 20:37:25 UTC,"No, not at all.  The intent is that LP releases to edge automatically, and that developers then promote those builds to more stable channels once they've been tested; that doesn't require reuploading, just ""snapcraft release""."
1666267,2017-02-27 19:14:45 UTC,"If this occurs, it will make snap package releases more difficult for users of lp builders. I imagine folks will build the snaps with launchpad, then have to download each one, and then upload themselves? What is the intended practice for using lp builders?"
1666269,2017-02-20 17:20:48 UTC,"System powers off if booted from Debian testing, Knoppix 7.7.1 or FreeBSD 11.0. It also powers off if booted from Ubuntu 14.04.5. But not if booted from Ubuntu 16.04.2 (on HD) or Ubuntu 16.10 (life-DVD)."
1666285,2017-05-11 13:35:31 UTC,I have been seeing this bug since the past few days on 16.04.2.
1666285,2020-11-12 17:41:26 UTC,"I'm on 20.04 and a variant of this problem occurs to me.  Randomly and without warning, about twice a week, I'm prompted to re-authorized my Google account from Evolution.  I'll just be sitting at my my computer, not even using Evolution, and suddenly the authorization window will pop up.  It doesn't even remember my Google password so I have to re-enter it manually."
1666292,2020-04-04 15:15:03 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1666305,2017-02-20 19:43:50 UTC,Example Variant Call Format file
1666311,2017-04-06 16:15:50 UTC,"One more information:
I have a user that is member of an institution with NO public pages allowed.
The user can not share a page to the public. So this works correct.
But the user can share his profilpage to the public."
1666316,2017-02-20 21:01:04 UTC,This change was made by a bot.
1666316,2017-02-20 20:42:01 UTC,"This bug appeared for months on different (previous) kernels, just I have reported it for the first time."
1666324,2017-02-21 15:15:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666324,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1666328,2017-05-17 13:36:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666328,2017-05-17 13:39:35 UTC,Works for me:
1666329,2017-02-20 22:29:13 UTC,See also https://bugs.launchpad.net/inkscape/+bug/1464270
1666332,2017-02-26 16:38:54 UTC,"StacktraceTop:
 real_assign_crtcs (screen=screen@entry=0x2108260, outputs=outputs@entry=0x2423330, assignment=assignment@entry=0x2448c30, error=error@entry=0x7ffde435a100) at gnome-rr-config.c:941
 crtc_assignment_new (screen=0x2108260, outputs=outputs@entry=0x2423330, error=error@entry=0x7ffde435a100) at gnome-rr-config.c:1068
 gnome_rr_config_apply_helper (config=config@entry=0x7f18940253d0, screen=<optimized out>, persistent=persistent@entry=0, error=error@entry=0x7ffde435a100) at gnome-rr-config.c:628
 gnome_rr_config_apply (config=config@entry=0x7f18940253d0, screen=<optimized out>, error=error@entry=0x7ffde435a100) at gnome-rr-config.c:650
 apply_configuration (manager=manager@entry=0x20dd230, config=0x7f18940253d0, timestamp=timestamp@entry=26805428) at gsd-xrandr-manager.c:347"
1666343,2017-02-21 03:32:02 UTC,"To support a feature like this, it would require MAAS to store all logs from all regions/racks in the database."
1666343,2019-09-19 12:02:47 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1666346,2017-02-24 13:59:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1666346,2017-03-05 15:27:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666365,2017-02-27 03:13:58 UTC,'kernel-bug-exists-upstream'.
1666365,2017-02-28 19:39:51 UTC,Nope Same result
1666365,2017-02-27 15:55:13 UTC,Does this bug go away if you boot back into the kernel prior to the kernel update?
1666365,2017-03-01 18:21:20 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1666365,2017-02-27 03:12:35 UTC,"Testing of Upstream kernel completed now, Bug is reproduced also in latest upstream kernel version:"
1666365,2017-02-21 03:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1666365,2017-02-21 17:52:03 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1666365,2017-02-21 04:21:40 UTC,"Changed in linux (Ubuntu):
status: 	New → Confirmed"
1666365,2017-02-25 17:58:18 UTC,"@ Joseph Salisbury I am afraid to do so,since it is my personal desktop machine,Will there are any consequences while installing latest upstream kernel. How can i go back to current kernel after testing it with latest one if there are any issues. is it like we can uninstall upstream kernal after testing as per the section ""Uninstalling upstream kernels""."
1666366,2017-02-23 17:59:43 UTC,We had an excellent discussion in the mailing list back in December about exactly this:
1666366,2017-02-24 01:39:29 UTC,"Yes, I'm in camp 2. I don't have a problem with the current behavior as long as I can override and it and say ""do what needs doing and don't bother me with the details."""
1666366,2017-02-24 16:53:09 UTC,"Yeah I'm on board with that. Another question: from your perspective, with your workflow, would it also be handy to add some sort of `--ignore` flag that leaves parts out-of-date?"
1666366,2017-02-27 01:41:30 UTC,"I guess a --ignore option would be useful for remote parts. When I'm trying to get my own code working, I don't necessarily care whether I have the latest and greatest remote part for the time being. With slow pull steps, --ignore might be useful."
1666369,2018-10-04 15:24:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666377,2017-11-03 16:36:29 UTC,Syncing task from Mir.
1666412,2017-03-22 16:19:48 UTC,This bug was fixed in the package lsvpd - 1.7.7-1ubuntu2
1666412,2017-03-22 03:49:20 UTC,"------- Comment From <email address hidden> 2017-03-21 23:43 EDT-------
(In reply to comment #14)

> Where is the ""upstream"" for this package?  The only source listed in
> debian/copyright of the package is
> http://sourceforge.net/projects/linux-diag/files/libvpd/, which points to
> https://git.code.sf.net/p/linux-diag/libvpd linux-diag-libvpd for the git
> repository.  The listed commit is not present in that repository.
"
1666412,2017-03-21 21:50:14 UTC,"Where is the ""upstream"" for this package?  The only source listed in debian/copyright of the package is http://sourceforge.net/projects/linux-diag/files/libvpd/, which points to https://git.code.sf.net/p/linux-diag/libvpd linux-diag-libvpd for the git repository.  The listed commit is not present in that repository."
1666412,2017-02-21 17:56:29 UTC,"Steve,"
1666415,2017-02-21 12:22:38 UTC,What is your kernel version?
1666415,2017-02-21 12:46:15 UTC,4.4.0-63-generic
1666421,2017-04-11 13:13:49 UTC,Confirm 4.4.0-73.94 from proposed works. No freeze and good WiFi connection.
1666421,2017-04-07 23:38:11 UTC,"Confirm 4.8.0-47.50 from proposed works. There is no freeze/kernel crash, and my rtl8192cu based wifi dongle works again."
1666421,2017-04-11 17:01:34 UTC,"Xenial's 4.4.0-73.94 works for me too, after a reinstall."
1666421,2017-04-07 21:24:02 UTC,I can confirm that 4.8.0-47.50 from proposed does not freeze in Yakkety.
1666421,2017-04-07 20:42:19 UTC,4.4.0-73 boots and logs in with no freeze in Xenial.
1666421,2017-04-07 17:17:31 UTC,The kernel versions to test are (afaik) 4.4.0-73.94 and 4.8.0-47.50
1666421,2017-04-07 15:14:05 UTC,@jsalisbury
1666421,2017-04-07 11:01:40 UTC,"Well, alright, I tested kernel 4.4.0-72. Didn't really work for me. It's actually not really helping, because with it Unity is broken, not all icons are loading (workspace switcher is gone), no mouse at all. Something utterly wrong with USB support. At least the system doesn't freeze, so I could recover by switching to a virtual console.
Enabling Xenial proposed didn't really help with the package management either. Got a red alert symbol from the update manager. I had to revert everything, actually took two reboots with 4.4.0-62 until the network was working again. Now I'm back on 4.4.0-62 with Xenial proposed diabled and it will stay that way."
1666421,2017-04-07 10:31:00 UTC,"Sorry, Joseph, a bit more information please: Which proposed kernel version specifically? I thought this had been done before. Anyway: I activated the Xenial proposed repository, but I can't see any kernel newer than 4.4.0-72 -- is this the version supposed to fix this issue?
To be honest, after six weeks I would have hoped you have already fixed this issue. I mean, it isn't really expensive to buy a WiFi with RTL8188 chipset, right?"
1666421,2017-04-05 18:30:49 UTC,Yakkety 4.8.0-46 is broken.
1666421,2017-04-07 09:31:23 UTC,Possible duplicate: bug #1667160
1666421,2017-04-07 09:14:35 UTC,I refresh this page every couple of hours. I'm desperately waiting for a fix.
1666421,2017-04-07 07:24:57 UTC,@Alexandru: Thank you for that suggestion. I'm not willing to add a PPA for something as important as the kernel. The whole point of having a LTS release is that it receives updates for five years. Bugs like this can not happen in 2017! Or at least they need to be fixed ASAP. We're six weeks in and no fix.
1666421,2017-04-06 18:20:14 UTC,"As an alternative to 4.4.0-62, I've been running 4.4.52 from"
1666421,2017-04-06 09:16:45 UTC,"Is someone still working on this issue? It doesn't look like it given the status ""Fix Committed"". Correct me if I'm wrong but the WiFi chipsets affected by this bug are in widespread use and I think it is a shame that it seems to be impossible to fix something which was demonstrably working in a previous version.
Can the dev working on it please comment? Greatly appreciated."
1666421,2017-04-05 09:52:23 UTC,Confirming that xenial with kernel 4.4.0-72 is broken.
1666421,2017-04-12 13:36:35 UTC,"Works for me.
Thanks
Grant"
1666421,2017-04-05 09:17:15 UTC,"I'm confused. I'm hitting this bug with 4.4.0-70.  I see that newer versions exist. But this bug report does not seem to indicate which version should introduce the fix.
What version is supposed to be working?"
1666421,2017-04-07 09:40:56 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1666421,2017-04-12 14:17:23 UTC,Works for me
1666421,2017-04-14 14:07:22 UTC,Perhaps you forgot to install the corresponding linux-image-extra ?
1666421,2017-04-14 12:37:12 UTC,"The reason might be that in ""/lib/modules/4.4.0-73-generic/kernel/drivers/net"" there is no folder ""wireless"" at all."
1666421,2017-04-04 11:21:01 UTC,"Hi, unfortunately 4.4.0-69 has been withdrawn from the 16.04 repository. (See here: https://launchpad.net/ubuntu/xenial/+package/linux-tools-4.4.0-69-generic )"
1666421,2017-04-25 17:48:28 UTC,Kernel 4.4.0-75.96 works for me on xenial 16.04.02 LTS
1666421,2017-04-25 07:48:52 UTC,Kernel 4.4.0-75.96 on 16.04.02 LTS also confirmed fixed
1666421,2017-04-24 21:26:37 UTC,4.4.0-75.96 works for me too with x64 .
1666421,2017-04-24 21:24:39 UTC,"Just updated to 4.8.0-49.61 from yakkety-updates. The issue is solved, there.
Thank you all!"
1666421,2017-04-24 19:42:18 UTC,Seconded: 4.4.0-75.96 from the main xenial repository fixes the problem.
1666421,2017-04-24 19:07:24 UTC,Confirm: Released fix resolves the issue.
1666421,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1666421,2017-04-24 10:23:13 UTC,I just installed Kernel 4.10.0-19 (Linux Mint 18.1)
1666421,2017-04-19 02:22:58 UTC,"Hi,"
1666421,2017-04-19 02:00:04 UTC,"Hi,"
1666421,2017-04-18 22:45:06 UTC,"Hi,"
1666421,2017-04-18 09:34:39 UTC,When is the fix out of 'proposed'? I don't want 'proposed' updates. If I'd want that I'd install 16.10
1666421,2017-04-16 19:23:18 UTC,"For these kernel version you need to enable the proposed repository.
See here: https://wiki.ubuntu.com/Testing/EnableProposed how it's done."
1666421,2017-04-16 18:54:30 UTC,"I tried to update to 4.4.0-74.95 from xenial but the ""Aktualisierungsverwaltung"" installed only 4.4.0.72. Trying to install from terminal I obtained (not found)"
1666421,2017-04-15 18:53:19 UTC,4.8.0-48.51 -proposed works also. No regression this time.
1666421,2017-04-14 22:08:46 UTC,Seconding #71: 4.4.0-74.95 from xenial-proposed works on i386 (both lowlatency and generic).
1666421,2017-04-14 18:07:11 UTC,Confirm 4.4.0-74.95 from xenial-proposed works.
1666421,2017-04-14 16:26:13 UTC,"Hi Frans, thanx for your comment."
1666421,2017-04-14 11:59:37 UTC,Xenial's 4.4.0-73.94 does NOT work for me.
1666421,2017-04-03 21:03:06 UTC,"Checked just now for 4.4.0-71-generic on xenial, still broken. So to summarize (xenial):"
1666421,2017-03-14 18:47:17 UTC,"Freeze still occurs after installed linux-image-4.4.0-67-generic and linux-image-extra-4.4.0-67-generic from proposed.
Are they correct packages to test?"
1666421,2017-03-29 18:06:24 UTC,"Since the 4.4.0-63-generic update until the current 4.4.0-70-generic I have stopped working the network with the wifi adpator rtl8192cu and not only the network but the system was frozen and did not start with the adapter Market Stall.
However with the adapter removed, the system boots smoothly. And it re-freezes the moment I insert usb_wifi.
Well I have overcome this error by loading the additional drivers as follows:
From the terminal
Git clone https://github.com/pvaret/rtl8192cu-fixes.git
Sudo dkms add ./rtl8192cu-fixes
Sudo dkms install 8192cu / 1.10
Then we edit the file"
1666421,2017-03-12 17:27:27 UTC,"I fixed this problem with this link:
https://github.com/pvaret/rtl8192cu-fixes"
1666421,2017-03-12 15:15:34 UTC,"this problem still remain in 4.4.0-66.
I have this problem .when I connect to Internet ubuntu is friezed."
1666421,2017-03-10 16:20:21 UTC,"Maybe the only required change in the kernel source is
https://patchwork.kernel.org/patch/9483577/"
1666421,2017-03-10 12:38:07 UTC,"Hello,"
1666421,2017-03-08 08:52:28 UTC,Still broken in 4.4.0-66 in 16.04(xenial)
1666421,2017-03-02 21:48:14 UTC,Still exists with 4.4.0-65 in Ubuntu 16.04 here as well
1666421,2017-03-02 15:10:41 UTC,Updated my kubuntu 16.04 with today's new linux-headers-4.4.0-65 and the problem persists.
1666421,2017-02-25 18:57:59 UTC,"same bug with Ubuntu 16.04 kernel 4.8.0-39
but 4.8.0-36 is OK.
Thanks."
1666421,2017-02-24 07:04:05 UTC,"apt update/upgrade installed a new kernel version 4.4.0-64-generic which has the same problem as mentioned in my first post (kernel 4.4.0-63-generic).
magic sysrq is also affected - the only way to restart the PC is a hard reset. (complete kernel crash?)"
1666421,2017-02-23 10:49:38 UTC,"@jsalisbury
test kernel works"
1666421,2017-02-23 05:12:03 UTC,"I have the same (or VERY similar) with Yakkety. Will said patch make it to Yakkety, or should I file another bug?"
1666421,2017-02-22 22:01:33 UTC,"I built a Xenial test kernel with a pick of commit 60f59ce02785.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1666421/"
1666421,2017-02-21 09:28:55 UTC,Kernel 4.10 from https://wiki.ubuntu.com/Kernel/MainlineBuilds also works fine (and despite the warnings about missing -extra VirtualBox is OK so I don't have too choose between that and WiFi)
1666421,2017-02-21 09:13:29 UTC,Probably this patch (from 4.10) needs applying ?
1666421,2017-03-30 08:01:59 UTC,4.8.0-45-generic = broken.
1666421,2017-02-21 09:01:13 UTC,I can confirm a kernel crash on 4.4.0-63 in the rtlwifi module that does not occur in -62
1666421,2017-02-21 07:30:14 UTC,This change was made by a bot.
1666421,2017-03-14 11:08:30 UTC,I can confirm this issue and the workaround at comment 18.
1666421,2017-03-14 17:06:31 UTC,"Would it be possible for you to test this latest kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1666421,2017-02-21 09:11:26 UTC,According to the stack trace (which I only have as the attached image) it's a Nnull pointer at 000048 from rtl_lps_leave+0x17/0x50
1666421,2017-03-25 01:16:26 UTC,"I have installed kernel 4.4.0-70 and can boot Xenial but when the Asus
USB-N13 wireless
adapter is installed the system crashes per previous descriptions. Booting
with
4.4.0-62 works.
Thanks
Grant"
1666421,2017-03-28 13:01:48 UTC,"Also affects me. Xenial, linux-headers-4.4.0-62+-generic (63 through 70)"
1666421,2017-03-28 08:03:22 UTC,So the backported patch was dropped from -70 and -44. Great.
1666421,2017-03-25 18:54:55 UTC,"Confirm, broken again with 4.8.0-44. So as I assume 4.4.0-70 was also fetched from xenial-proposed I set the tags back to verification-needed-yakkety."
1666421,2017-03-24 21:25:34 UTC,"Tom: yes that's true, recompiling stuff is out of the focus for me and most ""user"" people, Ubuntu is not ArchLinux and it should ""just work"". Why can't we just trace back when this bug was introduced by whom and revert the change?"
1666421,2017-03-24 13:01:58 UTC,...and now broken again with 4.8.0-44 from proposed.
1666421,2017-03-22 18:36:08 UTC,Ditto what Bernhard said; Confirm Kernel 4.8.0-43 from proposed works on Yakkety.
1666421,2017-03-22 08:58:28 UTC,"If you are on the 4.4.0-66 then you have not applied the fixes from proposed, instructions above."
1666421,2017-03-29 05:39:40 UTC,Confim:
1666421,2017-03-21 23:30:05 UTC,"I'm using Ubuntu 16.04.2 LTS \n \l with 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 and have all updates installed and my wifi does not work for over one month, upon connecting to any network the machine will freeze, unplugging does not help, I have to hard-reset."
1666421,2017-03-21 20:19:21 UTC,Same here for xenial: 4.4.0-69 from xenial-proposed fixed it.
1666421,2017-03-21 20:10:10 UTC,Proposed fix works for xenial
1666421,2017-03-21 15:42:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1666421,2017-03-21 15:28:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1666421,2017-03-15 18:07:49 UTC,Commit 60f59ce0278557f7896d5158ae6d12a4855a72cc has been commited to Yakkety and Xenial and will be in the next kernel release.
1666421,2017-03-15 07:53:48 UTC,"I can confirm that the test kernel posted in comment #7 solved the issue for me.
See comment 5 of bug #1669815 (duplicate of this one)."
1666421,2017-03-14 19:58:15 UTC,It looks like commit 60f59ce0278557f7896d5158ae6d12a4855a72cc will be in 4.4.0-68.  Can those that resolve the bug with dkms try the test kernel posted in comment #7?
1666421,2017-03-14 21:43:04 UTC,Confirm it still crashes with 4.8.0-42 from proposed in Yakkety.
1666421,2017-03-21 20:33:04 UTC,Confirm fix works for yakkety. At least kernel does not panic anymore.
1666421,2017-03-29 05:54:34 UTC,"Same for me: worked briefly with 4.4.0-69, bug came back with 4.4.0-70 (Xenial)."
1666423,2017-10-22 21:54:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666423,2020-07-03 05:07:26 UTC,DistroRelease: Kali 2016.2
1666424,2017-04-17 09:11:30 UTC,"Reviewed:  https://review.openstack.org/454832
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1eab4b445a534fa968b240c00333646081f9501c
Submitter: Jenkins
Branch:    stable/ocata"
1666424,2017-04-07 20:18:58 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/454877"
1666424,2017-04-16 05:09:20 UTC,"Reviewed:  https://review.openstack.org/454839
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4a96b962b560733a90b24ae10290e3d835d448e3
Submitter: Jenkins
Branch:    stable/newton"
1666424,2017-04-12 23:06:16 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/454877
Reason: I got my results, thanks."
1666424,2017-04-17 23:35:50 UTC,"Reviewed:  https://review.openstack.org/435601
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b9b598040da1b8d3e860b39d9027c10f8576ee33
Submitter: Jenkins
Branch:    master"
1666424,2017-04-07 18:09:46 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/454839"
1666424,2017-03-07 12:48:18 UTC,"Reviewed:  https://review.openstack.org/423584
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1f5ee0e8942e4b77a89a00ee0249de5d5014e2bc
Submitter: Jenkins
Branch:    master"
1666424,2017-03-09 01:12:12 UTC,"Reviewed:  https://review.openstack.org/428774
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=31fa23d84c9054fb4cfebccef953bf6839698a1d
Submitter: Jenkins
Branch:    master"
1666424,2017-02-21 08:27:30 UTC,I mean for a list of patches.
1666424,2017-02-21 08:27:09 UTC,See https://review.openstack.org/#/q/topic:bug/1666424 for list of bugs
1666424,2017-04-07 18:00:56 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/454832"
1666425,2020-07-03 04:54:10 UTC,"DistroRelease: Kali 2016.2
adwaita-icon-theme (3.22.0-1)"
1666432,2019-01-16 12:32:50 UTC,Persists on a freshly reinstalled system.
1666432,2018-11-08 01:54:52 UTC,This started happening for me within the last week or so.  A recent update may have triggered it?
1666432,2018-12-02 20:23:28 UTC,I'm also seeing it right now on XUbuntu 18.10 with a Dell XPS 15 9570 (also Killer WiFI chip).
1666432,2018-12-16 22:13:15 UTC,I experienced the same problem (wired AND wireless both down) on KDE Neon 18.04
1666432,2018-12-23 17:17:16 UTC,"I too have similar problem on ubuntu 18.04. I never tried with wire connection, but my wifi connection repeatedly failing after few minutes. I tried several solutions. I installed  driver=r8168 driverversion=8.046.00-NAPI after downloading from realtek software download but no good result."
1666432,2019-01-03 04:14:31 UTC,"Same here ! Fresh Dell inspiron 5570, this bug occurs with both ubuntu 16.04 and 18.04"
1666432,2019-01-11 16:48:08 UTC,"I can't add to much, apart from saying that this bug affects me too.  Wired and wireless internet connectivity fails about 2 or 3 times per hour.  Sometimes it comes back after a couple of minutes, particularly if I diconnect and reconnect the wirelss connection. I use Lubuntu 18.04 on an Asus X99 Deluxe II motherboard. It's annoying !"
1666432,2019-01-14 16:40:34 UTC,"I'm experiencing what may be the same thing in bug #1804280.  I can't duplicate the issue on wireless networks, only Ethernet (but the issue is the same whether I use the onboard Ethernet or a USB Ethernet interface)."
1666432,2019-02-01 10:07:24 UTC,"I am facing the same problem with 2 wired connections. No matter what I do, if I connect with 1st ethernet or switch to 2nd wired, the problem persists. After boot up, when the problem starts, I switch the cable of ethernet and temporally the problem finishes."
1666432,2018-09-09 20:27:54 UTC,Have same RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller and r8169 driver.
1666432,2019-02-19 18:34:17 UTC,Happens on my system too (18.04 with latest updates). Works fine in Windows 7. Motherboard is a Z370P D3. I've also tried a USB wifi adapter which had the same problem. A laptop also running Ubuntu 18.04 has no problem.
1666432,2019-04-04 02:57:18 UTC,My Ubuntu 18.04 randomly drops ethernet connection once per hour while in use. Reboot clears this issue.
1666432,2019-04-11 11:59:55 UTC,"I'm on ubuntu 18.10 and I get random drops but if I disconnect and reconnect from the UI, it works. This isn't happening on my laptop which runs 18.04 also on cable connection."
1666432,2019-07-14 16:02:04 UTC,Hi.
1666432,2019-08-20 20:19:41 UTC,Manually entering the dns servers in the /etc/netplan yaml file worked for me. Perhaps a workaround would be to have the netplan file pull the dns servers from dhcp and then populate the yaml file?
1666432,2019-12-18 15:17:09 UTC,"Perhaps this can help: The symptoms I experience started sometime during the past year after an update (sudo apt update && sudo apt upgrade && sudo apt autoremove) are that some indefinite time (usually less than ½ hour) after I log on, the network disconnects without warning or error. Clicking on the up/down arrows of the indicator plugin and selecting the interface reconnects; however, I recently discovered that if, as soon as I log on, I select ""Disconnect"" and then select the adapter to reconnect, my session will be fine until I log out and back in again. So perhaps the bug is not with network-manager, samba or ifupdown, but with the logon process(es). My version is 18.04 and I'm using LiteDM GTK+. I haven't the faintest idea where to look for a cause that might be related to the logon process(s), but none of the very many ""solutions"" offered on various web pages I found on the problem have fixed it for me."
1666432,2020-04-27 20:57:51 UTC,"I uninstalled the network-manager, and started using the traditional Linux networking service with wpa_supplicant, but the problem continues."
1666432,2020-05-02 20:42:43 UTC,"I fixed in my network, but the problem was in router security settings."
1666432,2020-10-01 15:04:57 UTC,"I have the same problem. On wired connection it constantly disconnects and connects.
I am running Ubuntu VM inside vmware with NAT network adapter setting.
It had been stable for a long time, but this last week has been incredible horrible."
1666432,2019-02-01 10:09:30 UTC,I forgot... I'm using Ubuntu 18.04 LTS with all updates up to date.
1666432,2018-09-02 15:10:35 UTC,I had (fingers crossed that I fixed it) this same thing with my brand new Dell 3567 laptop that came with Ubuntu 16.04 LTS.
1666432,2018-03-15 23:28:09 UTC,Same symptoms on a Dell XPS13
1666432,2018-08-16 16:31:59 UTC,"I am also having a similar issue in Ubuntu 18.04.
This happens right after opening some tabs and streams. The network icon stays there, but internet drops. Restarting the wifi doesn't solve the problem most times.
The laptop is ASUS Vivobook S14.
  *-network
       description: Wireless interface
       product: QCA9377 802.11ac Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 31
       serial: 40:9f:38:db:ca:0b
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath10k_pci driverversion=4.15.0-30-generic firmware=WLAN.TF.1.0-00002-QCATFSWPZ-5 ip=192.168.1.157 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:129 memory:ef200000-ef3fffff"
1666432,2018-09-02 14:39:16 UTC,I had the same problem on 17.04 with an ASUS USB-N13 wireless adapter. I hoped upgrading the OS to 18.04 would solve it. I did that a few days ago and the problem persists.
1666432,2017-03-07 07:40:52 UTC,"Hello, as you mentioned that this can be reproduced with LiveCD, do you mind to give 16.04.2 (which is using 4.8 kernel, or even test it with 17.04 daylive) a try?
Thanks"
1666432,2017-04-20 00:46:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666432,2017-04-20 01:07:16 UTC,"Sorry, just now saw your comment, Po-Hsu Lin. I will try with 17.04 LiveCD when I have a spare moment. It's the beginning of the school year here, so I have my hands full teaching at the moment."
1666432,2017-04-21 01:01:27 UTC,"I'm having the same problem since when I fresh installed Ubuntu (Budgie) 17.04.
I then reinstalled Ubuntu (Unity) 16.04 LTS and having the same problem, LIVE versions included."
1666432,2017-04-24 12:10:01 UTC,"Same problem here after a fresh install the day after the release date. This is really annoying. I already changed the ipv4 method to Automatic (DHCP) addresses only and added DNS servers 8.8.8.8, 8.8.4.4, but the problem is still there. Under 16.10 no such problem here.
I hope there will be a fix soon."
1666432,2017-05-12 11:51:12 UTC,"Must say, since my post of April 24th, the problem has not reoccurred. Settings still as mentioned above. So with these settings it was a one-off incident."
1666432,2017-05-12 13:50:57 UTC,"Having said that, it just happened again. An hour after my previous post."
1666432,2017-06-10 17:11:36 UTC,I have the same problem under Ubuntu 17.04. Wifi connection is dropped randomly after a couple of minutes.
1666432,2017-06-12 10:19:30 UTC,I have the same problem on both wired and wireless. Today already four times just randomly wired connection stopped working...
1666432,2017-06-15 07:58:32 UTC,"wow, I removed the ethernet cable and used wi-fi only for two days. Everything worked perfectly. This morning I plugged the ethernet cable in and the problem came back in about two hours!"
1666432,2017-09-23 15:22:24 UTC,"I too am having this issue, and at times now it will not reconnect."
1666432,2017-10-26 15:30:35 UTC,Hi
1666432,2017-11-16 22:43:07 UTC,Same here on Ubuntu 17.10
1666432,2018-01-18 21:57:42 UTC,I am also getting this in 17.10 on a Dell Optiplex 9020. It works fine for about 20-30 minutes and then I can't ping the network and all network connected jobs stop responding. It stays that way for 2-5 minutes and then it comes back up. Network status shows connected and never indicates that the network connection itself stopped working. It is driving me batty.
1666432,2018-03-29 15:16:32 UTC,"I am also having the same issue on my Thinkpad E460 under Ubuntu 17.10. It started a couple of week ago and got really annoying. Sometimes the connection is just gone for a few seconds up to 2 or 3 minutes and sometimes it seems turning the WiFi module off and on again helps. The same problem occurs via Ethernet too, but less frequently."
1666432,2018-04-04 07:38:37 UTC,Same issue here on my laptop computer ACER Aspire ES1-433 after upgrading to 17.10 from 16.04.3
1666432,2018-07-10 05:29:31 UTC,i also having same problem with wired connection!! ubuntu 16.04.4
1666432,2017-06-12 20:15:13 UTC,"I did as described by Tokyobadger https://ubuntuforums.org/archive/index.php/t-2347827.html on 18may2017, and the problem has vanished unti now (12jun2017)."
1666435,2017-04-01 05:59:25 UTC,Committed as 01b73072961f8c62255cf2b66dba4e55d36fd646
1666435,2017-04-06 09:53:46 UTC,This bug was fixed in the package gtk+3.0 - 3.22.11-0ubuntu3
1666435,2017-03-24 14:29:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666435,2017-02-28 10:28:39 UTC,Is GTK really responsible for setting up the session settings? It's the default hinting setting that's wrong and that might simply be because there is no gnome-settings-daemon to read the Ubuntu default settings for hinting.
1666435,2017-02-28 12:57:50 UTC,"the gtk wayland backend reads the value directly from gsettings, the mir backend should probably do the same?
https://git.gnome.org/browse/gtk+/tree/gdk/wayland/gdkscreen-wayland.c#n169"
1666435,2017-03-01 01:53:17 UTC,Sounds like the right answer. The GDK-Mir backend could copy that implementation (mostly)...
1666436,2017-03-29 08:58:01 UTC,"Related fix proposed to branch: master
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/32607"
1666436,2017-03-29 09:47:15 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/32611"
1666436,2017-03-30 14:35:43 UTC,"Reviewed: https://review.fuel-infra.org/32607
Submitter: Pkgs Jenkins <email address hidden>
Branch: master"
1666436,2017-03-30 14:37:26 UTC,"Reviewed: https://review.fuel-infra.org/32611
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1666436,2017-04-03 18:49:10 UTC,Reverted by https://review.fuel-infra.org/#/c/32721/ due to https://bugs.launchpad.net/mos/+bug/1678044
1666439,2017-02-28 07:56:50 UTC,A new version of the patch has just been released and testers are requested:
1666439,2017-02-22 15:24:02 UTC,"The subject is the same, except that v2 has been changed to v3. Normally that means a new revision of the same patch. Multiple patches in the same series are typically denoted as [PATCH 1/N], [PATCH 2/N], etc."
1666439,2017-02-22 13:59:11 UTC,"It doesn't appear to be a newer revision, but a two-part patch."
1666439,2017-02-21 08:42:14 UTC,"Brad, this is a feature request that doesn't require a log. Thank you."
1666439,2017-02-21 08:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1666439,2017-02-22 13:41:45 UTC,"It doesn't look like the maintainers have accepted the patch yet, in fact there's even a newer revision."
1666445,2017-02-24 08:00:48 UTC,"This issue is seen when there are more than one ""contrail-compute"" nodes in the inventory.
Need to add ""  ignore_errors: yes"" to the task."
1666445,2017-02-24 13:11:12 UTC,"We should avoid this method of changing the file which are part of anisble
from ansible itself, rather we have to implement an optional temp location
for vars to be used in situations where one need to use fresh vars every
time."
1666448,2019-09-19 15:00:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1666455,2017-03-06 12:46:21 UTC,This ticket would be obsoleted by the example service file in https://bugs.launchpad.net/ubuntu/+source/coturn/+bug/1666456.
1666455,2017-02-21 09:38:25 UTC,Related: https://bugs.launchpad.net/ubuntu/+source/coturn/+bug/1666456
1666456,2017-12-29 22:02:58 UTC,"Hm, I don't actually remember where I based that file on, sorry... The difference are not deliberate, or at least not by me."
1666456,2017-12-22 13:11:10 UTC,"Yes, it is possible to manually add a systemd unit file to the package, but it would be good if this were supported natively by the Ubuntu package."
1666456,2017-12-29 21:25:36 UTC,"Why does this unit file have differences compared to the rpm unit file?
https://github.com/coturn/coturn/blob/master/rpm/turnserver.service.fc"
1666456,2017-03-06 12:45:22 UTC,Here is an example file that seems to work fine:
1666456,2017-12-22 11:09:34 UTC,"Danilo, is it possible to install the package, disable the init script and manually add this service file?
Maybe leaving TURNSERVER_ENABLED=0 in /etc/default/coturn is enough?"
1666461,2017-02-21 20:30:43 UTC,I think you don't have the version of Xtracks or Ytracks required for this route.
1666461,2017-02-22 15:25:07 UTC,"I believe I did have the correct version of Xtracks ie 3.20, however, in case I did not I have re-installed Xtracks 3.20.  Unfotunately it has not changed the situation."
1666461,2017-02-24 16:32:15 UTC,"Hi Alan,
I tried the route and got the same problem. After many checks I found out that the route uses an unregular release 38 of tsection.dat. It has some additional trackshapes added to its end. You, as I did, probably used your standard tsection.dat and so you get the error.
It's a problem of the route. I will contact the route builder, because this is a misleading situation.
Pls also take note that this route has a patch, that you can download from here http://www.trainsimhobby.net/infusions/pro_download_panel/download.php?did=1887 . This patch contains also the fiddled tsection.dat. To solve the problem I took the last part of the fiddled tsection.dat (starting from TrackShape 20000, which is not put in the correct order, and located after TrackShape 39998) and copied it at the end of my tsection.dat release 46. This way the route opened. But it's not nice."
1666467,2017-02-21 10:16:38 UTC,"- Logs begin at Tue 2017-02-21 11:22:38 EET, end at Tue 2017-02-21 12:15:34 EET. --
Feb 21 11:47:06 pixel-desktop systemd[2813]: Starting ubuntu-app-launch-application-legacy-mypaint-1487670426783113.service...
Feb 21 11:47:06 pixel-desktop mypaint[6358]: INFO: mypaint: Installation layout: conventional POSIX-like structure with prefix u'/usr'
Feb 21 11:47:08 pixel-desktop mypaint[6358]: INFO: lib.i18n: POSIX: LANG='en_US.UTF-8'
Feb 21 11:47:08 pixel-desktop mypaint[6358]: INFO: lib.i18n: POSIX: LANGUAGE='en_US'
Feb 21 11:47:08 pixel-desktop mypaint[6358]: g_application_get_application_id: assertion 'G_IS_APPLICATION (application)' failed
Feb 21 11:47:08 pixel-desktop mypaint[6358]: /usr/lib/python2.7/dist-packages/gi/overrides/Gdk.py:441: Warning: g_variant_new_string: assertion 'string != NULL' failed
Feb 21 11:47:08 pixel-desktop mypaint[6358]:   initialized, argv = Gdk.init_check(sys.argv)
Feb 21 11:47:08 pixel-desktop mypaint[6358]: g_application_get_application_id: assertion 'G_IS_APPLICATION (application)' failed
Feb 21 11:47:08 pixel-desktop mypaint[6358]: Could not open X display
Feb 21 11:47:09 pixel-desktop mypaint[6358]: INFO: gui.application: Created basedir u'/home/pixel/.config/mypaint'
Feb 21 11:47:09 pixel-desktop mypaint[6358]: INFO: gui.application: Created basedir u'/home/pixel/.local/share/mypaint'
Feb 21 11:47:09 pixel-desktop mypaint[6358]: INFO: gui.application: Created data subdir u'/home/pixel/.local/share/mypaint/backgrounds'
Feb 21 11:47:09 pixel-desktop mypaint[6358]: INFO: gui.application: Created data subdir u'/home/pixel/.local/share/mypaint/brushes'
Feb 21 11:47:10 pixel-desktop mypaint[6358]: INFO: gui.application: Created data subdir u'/home/pixel/.local/share/mypaint/scratchpads'
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-fallback-icon-theme
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-icon-sizes
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-alternative-button-order
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-show-input-method-menu
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-show-unicode-menu
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-timeout-initial
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-timeout-repeat
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-timeout-expand
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-color-scheme
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-touchscreen-mode
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-tooltip-timeout
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-tooltip-browse-timeout
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-tooltip-browse-mode-timeout
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-keynav-cursor-only
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-keynav-wrap-around
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property color-hash
Feb 21 11:47:10 pixel-desktop mypaint[6358]: unknown property gtk-file-chooser-backend
Feb 21 11:47:10 pixel-deskt..."
1666469,2017-02-23 10:50:19 UTC,I meant the child windows of those apps.
1666469,2017-02-22 18:19:43 UTC,"yep the main calculator app seems to resize as it should, i think. the problem is with child windows, ""About"", ""Preferences"" etc, they don't seem to have at least a minimum size, you can make them as small as you like"
1666469,2017-02-22 17:52:32 UTC,Just tried with calculator. It does set seem to be setting a minimum and a maximum width with the same value since I cannot resize it horizontally.
1666469,2017-02-22 17:49:00 UTC,"I guess the bug is really that those child dialogs shouldn't be resizable in the first place, like in Unity 7, right?"
1666469,2017-02-22 07:41:00 UTC,"all the apps are running native here, no Xmir"
1666469,2017-02-22 03:03:58 UTC,"Sorry again, this is also not a GTK bug. The windows you mention correctly implement resize constraints and I can confirm this on Unity8 17.04."
1666469,2017-02-22 02:55:32 UTC,"Oops, sorry, this is only a duplicate of bug 1511604 if it's using Xmir. It looks like the above apps will be native GTK instead."
1666469,2017-02-22 02:50:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1511604, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1666475,2017-02-21 11:10:49 UTC,I wanted to fill in a bug upstream but I can't seem to be able to find the official upstream bugtracker...
1666478,2019-09-19 12:02:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1666487,2020-08-11 15:15:53 UTC,"This is expected behavior for most charms, as machines configured by juju charms should remain configured to use NTP until they are unbuilt.  This allows for management of charm configurations and ability to remove one ntp charm and install another ntp charm without having ntp stop functioning in the middle of the process."
1666490,2017-03-08 05:06:13 UTC,"Hi,
  Can you try using the --charset option to specify the default character set of pt-table-sync?"
1666490,2017-03-08 05:07:18 UTC,Oops. I meant:
1666490,2017-03-08 05:08:11 UTC,I'll set the status of this case to invalid because I think this can be resolved by setting --charset
1666490,2017-03-08 07:56:44 UTC,"Hi Jaime,"
1666490,2018-01-24 22:34:21 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1412
1666494,2017-02-21 12:00:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436425"
1666494,2017-02-21 15:20:18 UTC,"Reviewed:  https://review.openstack.org/436425
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-lma-collector/commit/?id=9016e64bb48bb0a7028d0c524a498df3d0f9e144
Submitter: Jenkins
Branch:    master"
1666503,2017-02-21 14:28:56 UTC,Maybe related to bug #1646346 ?
1666516,2017-02-22 12:30:42 UTC,"Confirmed on Windows XP (32-bit), Inkscape 0.92 and 0.48.5 with the example file from Bug #1666522."
1666521,2017-06-27 17:54:21 UTC,"Hi Mischa,"
1666521,2020-06-25 09:04:22 UTC,"I confirm the bug is present on 2.6.2-7841 and I had to modify the postgres table mentioned above.
Ignazio"
1666521,2019-09-19 11:55:56 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1666521,2018-06-14 14:27:42 UTC,"I want to note that the fix that mlschouten posted ( https://bugs.launchpad.net/maas/+bug/1666521/comments/3 ) does work, but you need to use MiB's instead of bytes!
Bytes result in a to large integer for the database, and all is stored using MiB's."
1666521,2018-06-13 11:45:02 UTC,I have the same issue with the latest MAAS 2.3.3 version and using VMWare 6.7.
1666521,2017-02-21 13:47:47 UTC,">In addition:
>lshw output excerpt from hardware node RAM that IS correctly detected by MAAS
>
    *-memory
          description: System Memory
          physical id: 1000
          slot: System board or motherboard
          size: 128GiB
        *-bank:0
             description: DIMM Synchronous 2133 MHz (0.5 ns)
             product: M393A2G40DB0-CPB
             vendor: 00CE04B300CE
             physical id: 0
             serial: 40AD3081
             slot: A1
             size: 16GiB
             width: 64 bits
             clock: 2133MHz (0.5ns)
        *-bank:1
             description: DIMM Synchronous 2133 MHz (0.5 ns)
             product: M393A2G40DB0-CPB
             vendor: 00CE04B300CE
             physical id: 1
             serial: 40AD308A
             slot: A2
             size: 16GiB
             width: 64 bits
             clock: 2133MHz (0.5ns)
        *-bank:2
             description: DIMM Synchronous 2133 MHz (0.5 ns)
             product: M393A2G40DB0-CPB
             vendor: 00CE04B300CE
             physical id: 2
             serial: 40AD30A2
             slot: A3
             size: 16GiB
             width: 64 bits
             clock: 2133MHz (0.5ns)
        *-bank:3
             description: DIMM Synchronous 2133 MHz (0.5 ns)
             product: M393A2G40DB0-CPB
             vendor: 00CE04B300CE
             physical id: 3
             serial: 40AD30A1
             slot: A4
             size: 16GiB
             width: 64 bits
             clock: 2133MHz (0.5ns)
"
1666521,2017-02-22 15:34:50 UTC,"Happy workaround :
using credentials found in /etc/maas/regiond.conf"
1666521,2017-07-04 15:13:24 UTC,same error here with
1666522,2017-02-22 12:25:50 UTC,Thanks for taking the time to file a report!
1666527,2017-02-22 12:19:04 UTC,"Confirmed on Windows XP (32-bit) and Xubuntu 16.04. Inkscape 0.91 and 0.92.1.
The same action was faster with 0.48.5."
1666528,2017-05-22 20:38:37 UTC,"Change abandoned by Thomas Bachman (<email address hidden>) on branch: master
Review: https://review.openstack.org/436504
Reason: Abandon for now."
1666531,2018-01-24 22:34:22 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1413
1666531,2017-02-22 12:40:02 UTC,"Hi,"
1666534,2017-03-23 15:13:27 UTC,"Reviewed:  https://review.openstack.org/436003
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=7359c360e5b1d45b627d213a11f937f4ed860583
Submitter: Jenkins
Branch:    master"
1666534,2017-08-02 16:27:13 UTC,"Change abandoned by John L. Villalovos (<email address hidden>) on branch: master
Review: https://review.openstack.org/489796
Reason: Will work with infra to do a batch upload."
1666534,2017-03-02 18:31:15 UTC,I agree with vdrok
1666534,2017-08-02 00:16:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489796"
1666534,2017-02-23 16:20:39 UTC,"Positive tests: https://review.openstack.org/#/c/436003/
Negative tests: https://review.openstack.org/#/c/435952/"
1666534,2017-03-01 14:41:37 UTC,"I'd prefer using the bug which was describing the actual feature instead of introducing new ones, but well, they're here already..."
1666537,2017-02-22 00:33:33 UTC,Juju does not currently support IPv6. This may be provided in 2.2 and will possibly be addressed this cycle.
1666537,2017-03-16 05:21:31 UTC,This will not be addressed in 2.2 due to time and capacity constraints.
1666547,2020-06-11 15:40:46 UTC,Additional comments  http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-06-11-15.00.log.html
1666547,2019-04-25 16:07:12 UTC,I downgraded this one to Medium importance because we don't have active manila users reporting this issue.  If it affects you please say so in this bug and we can talk about how to get a fix.
1666547,2018-06-10 02:48:08 UTC,"Change abandoned by Tom Barron (<email address hidden>) on branch: master
Review: https://review.openstack.org/437346
Reason: No activity on this one since March 2017; restore and rebase if appropriate."
1666547,2017-06-08 11:44:13 UTC,This issue was fixed in the openstack/cinder 11.0.0.0b2 development milestone.
1666547,2017-05-02 17:33:24 UTC,"Reviewed:  https://review.openstack.org/437313
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=c72f5ef8e32c4b036fd8c25da9d502bd16b61fc6
Submitter: Jenkins
Branch:    master"
1666547,2020-06-11 15:34:34 UTC,"One index for manila was added via https://bugs.launchpad.net/manila/+bug/1776495, adding similar ones for other tables should be possible"
1666547,2017-02-22 15:25:29 UTC,"Also Manila is effected. There are no indexes created for postgres, e.g.:"
1666547,2017-02-21 21:58:58 UTC,Did a fresh installation with mysql to query the indexes:
1666547,2017-02-21 17:07:22 UTC,Doing a tox -esmoke results in these metrics on the cinder database:
1666547,2017-02-23 12:00:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437346"
1666552,2018-09-04 12:50:46 UTC,"This is standalone bug with different behaviour. Unmark duplicate.
Mentioned behaviour in description considered having VIP created and FIP assigned on it with VRRP group(AAP) having active interfaces. Bug is still presents. Steps to reproduce:"
1666552,2018-09-12 10:18:55 UTC,"Looking on https://review.opencontrail.org/gitweb?p=Juniper%2Fcontrail-test.git;a=commitdiff;h=f9f91b2beddcd37be0ad9459fad1af2bb6ea4fbb
I have slight question: does this expected to have same FIP associated on different ports? And this FIP has to be propagated with floating_ip_fixed_ip of VIP? Many thanks in advance"
1666553,2017-03-01 18:00:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666553,2017-03-01 18:02:23 UTC,If you instead try to run the same from a non-tmp dir you get an error such as
1666554,2017-02-23 15:12:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666560,2017-03-24 12:10:42 UTC,"Reviewed:  https://review.openstack.org/443534
Committed: https://git.openstack.org/cgit/openstack/python-watcherclient/commit/?id=7250886d149a02f9a3cd0542e8b327f405d75f08
Submitter: Jenkins
Branch:    master"
1666560,2017-04-14 09:12:51 UTC,This issue was fixed in the openstack/networking-bgpvpn 7.0.0.0b1 development milestone.
1666560,2018-08-17 20:09:51 UTC,This issue was fixed in the openstack/karbor 1.1.0 release.
1666560,2017-04-13 15:17:12 UTC,This issue was fixed in the openstack/python-watcherclient 1.1.0 release.
1666560,2017-04-13 10:10:41 UTC,This issue was fixed in the openstack/senlin 4.0.0.0b1 development milestone.
1666560,2017-04-12 18:34:55 UTC,This issue was fixed in the openstack/sahara-dashboard 7.0.0.0b1 development milestone.
1666560,2017-04-06 12:59:01 UTC,This issue was fixed in the openstack/keystonemiddleware 4.15.0 release.
1666560,2017-04-14 09:41:38 UTC,This issue was fixed in the openstack/mistral-dashboard 5.0.0.0b1 development milestone.
1666560,2017-04-05 16:01:19 UTC,This issue was fixed in the openstack/os-win 2.0.0 release.
1666560,2017-04-05 12:39:07 UTC,"Reviewed:  https://review.openstack.org/444398
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=eb664f9d6c25b355b87bbdbb512d5949dff2b771
Submitter: Jenkins
Branch:    master"
1666560,2017-03-31 01:17:48 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/443508"
1666560,2017-03-30 14:07:07 UTC,"Reviewed:  https://review.openstack.org/443515
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=66a0da64a83fbf57deaa3adf2057a5ce75e4fad6
Submitter: Jenkins
Branch:    master"
1666560,2017-04-12 18:34:38 UTC,This issue was fixed in the openstack/sahara 7.0.0.0b1 development milestone.
1666560,2017-04-19 10:08:41 UTC,This issue was fixed in the openstack/kolla-kubernetes 0.6.0 release.
1666560,2017-06-08 17:00:41 UTC,This issue was fixed in the openstack/solum 5.3.0 release.
1666560,2018-03-05 02:27:37 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/443456"
1666560,2017-06-09 15:35:54 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1666560,2017-07-26 18:44:38 UTC,This issue was fixed in the openstack/python-brick-cinderclient-ext 0.5.0 release.
1666560,2017-08-15 08:49:52 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1666560,2017-08-23 16:08:50 UTC,This issue was fixed in the openstack/magnum 5.0.0 release.
1666560,2017-09-25 05:30:51 UTC,"Reviewed:  https://review.openstack.org/443484
Committed: https://git.openstack.org/cgit/openstack/karbor/commit/?id=9a4c7400a987503aa9cec33ce313fd3305de33b7
Submitter: Jenkins
Branch:    master"
1666560,2017-11-27 09:12:45 UTC,"Reviewed:  https://review.openstack.org/520622
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=6f6db4f4bcd8e9b2627d75c8de42631325d23b33
Submitter: Zuul
Branch:    master"
1666560,2017-12-06 18:10:19 UTC,This issue was fixed in the openstack/karbor 0.6.0 release.
1666560,2017-12-07 20:22:06 UTC,This issue was fixed in the openstack/networking-ovn 4.0.0.0b2 development milestone.
1666560,2017-12-10 23:15:49 UTC,"Reviewed:  https://review.openstack.org/443537
Committed: https://git.openstack.org/cgit/openstack/searchlight-ui/commit/?id=9a1476a8be154dd38f2af7b26e0a774b75d75b44
Submitter: Zuul
Branch:    master"
1666560,2018-01-26 14:21:46 UTC,This issue was fixed in the openstack/karbor 1.0.0 release.
1666560,2018-01-30 23:20:59 UTC,This issue was fixed in the openstack/searchlight-ui 4.0.0.0b3 development milestone.
1666560,2017-06-08 11:39:16 UTC,This issue was fixed in the openstack/python-watcherclient 1.2.0 release.
1666560,2017-03-23 18:40:07 UTC,"Reviewed:  https://review.openstack.org/448876
Committed: https://git.openstack.org/cgit/openstack/patrole/commit/?id=ae9db6fd2b99c2645ce41dfd7d227f8778828cbd
Submitter: Jenkins
Branch:    master"
1666560,2017-03-14 13:44:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445496"
1666560,2017-03-21 04:59:50 UTC,"Change abandoned by iswarya vakati (<email address hidden>) on branch: master
Review: https://review.openstack.org/444789"
1666560,2017-02-21 16:10:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436523"
1666560,2017-03-03 10:14:17 UTC,"Reviewed:  https://review.openstack.org/436523
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=1fd2101fa8067546722afa0041e3df55d180792e
Submitter: Jenkins
Branch:    master"
1666560,2017-03-04 03:16:00 UTC,"Reviewed:  https://review.openstack.org/439478
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=a0d2e379a8c6c1e5667efc92fd32f168d2241268
Submitter: Jenkins
Branch:    master"
1666560,2017-03-07 07:15:15 UTC,"Reviewed:  https://review.openstack.org/441672
Committed: https://git.openstack.org/cgit/openstack/python-karborclient/commit/?id=5b122a89bce676237b9a0814bb6c7de73db700b1
Submitter: Jenkins
Branch:    master"
1666560,2017-03-07 08:41:26 UTC,"Reviewed:  https://review.openstack.org/441671
Committed: https://git.openstack.org/cgit/openstack/mistral-dashboard/commit/?id=24852cd0b3d7c407f358011bb65eb52004599cb9
Submitter: Jenkins
Branch:    master"
1666560,2017-03-07 10:13:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442361"
1666560,2017-03-10 23:44:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444542"
1666560,2017-03-13 09:33:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444782"
1666560,2017-03-23 03:29:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448876"
1666560,2017-03-13 09:47:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444789"
1666560,2017-03-13 10:04:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444795"
1666560,2017-03-13 16:47:40 UTC,"Reviewed:  https://review.openstack.org/444795
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=04052686af1f2c437095f5a2aa210256e126e0d9
Submitter: Jenkins
Branch:    master"
1666560,2017-03-14 02:51:37 UTC,"Reviewed:  https://review.openstack.org/443543
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=8aae0867d1f0a8dd827689cc8b8a9761512b39cd
Submitter: Jenkins
Branch:    master"
1666560,2017-03-13 09:38:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444787"
1666560,2017-03-14 05:00:48 UTC,refer https://review.openstack.org/#/c/444811/
1666560,2017-03-14 04:59:04 UTC,"Change abandoned by iswarya vakati (<email address hidden>) on branch: master
Review: https://review.openstack.org/444787
Reason: refer https://review.openstack.org/#/c/443495/"
1666560,2017-03-20 17:32:11 UTC,This issue was fixed in the openstack/kuryr 0.4.0 release.
1666560,2017-03-16 19:37:01 UTC,This issue was fixed in the openstack/neutron-lib 1.3.0 release.
1666560,2017-03-15 09:55:18 UTC,"Reviewed:  https://review.openstack.org/442361
Committed: https://git.openstack.org/cgit/openstack/mistral-lib/commit/?id=bfd79c07117619de0376dc0b5457f7041b2cf126
Submitter: Jenkins
Branch:    master"
1666560,2017-03-15 01:26:12 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/443495"
1666560,2017-03-21 04:58:48 UTC,"Change abandoned by iswarya vakati (<email address hidden>) on branch: master
Review: https://review.openstack.org/444782
Reason: Duplicate of https://review.openstack.org/#/c/443484/2"
1666560,2017-03-15 01:25:43 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/443460"
1666560,2017-03-15 01:25:22 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/443464"
1666560,2017-03-15 01:10:03 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/443490"
1666560,2017-03-15 00:46:41 UTC,"Reviewed:  https://review.openstack.org/444542
Committed: https://git.openstack.org/cgit/openstack/kolla-kubernetes/commit/?id=a5ea314f58cbc0e6dd3543bd7daa7f85bc818291
Submitter: Jenkins
Branch:    master"
1666560,2017-03-14 09:38:02 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/443487"
1666560,2017-03-15 01:25:58 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/443488"
1666561,2017-02-22 15:11:06 UTC,apport information
1666561,2017-02-22 15:47:50 UTC,"Already tested with the latest upstream kernel but still the bug exists. Right now i am using internet via sharing through LAN from my desktop. Its very serious bug it needs to be fixed. whenever i installed newer ubuntu version with support of kernel 4x my wifi card doesn't work. And also i have noticed that when my wifi is disable the airplane mode is also enabled by default and i am unable to disable it...So, i need to revert back to windows and i have done it more than 5-6 times."
1666561,2017-02-22 15:12:00 UTC,apport information
1666561,2017-02-22 15:11:41 UTC,apport information
1666561,2017-02-22 15:11:31 UTC,apport information
1666561,2017-02-22 15:11:25 UTC,apport information
1666561,2017-02-22 15:11:16 UTC,apport information
1666561,2017-02-22 15:11:09 UTC,apport information
1666561,2017-02-22 15:11:08 UTC,apport information
1666561,2017-02-22 15:11:03 UTC,apport information
1666561,2017-02-22 15:10:50 UTC,apport information
1666561,2017-02-22 15:10:58 UTC,apport information
1666561,2017-02-21 16:25:48 UTC,apport information
1666561,2017-02-21 16:25:51 UTC,apport information
1666561,2017-02-21 16:28:20 UTC,apport information
1666561,2017-02-21 17:47:12 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1666561,2017-02-22 15:11:00 UTC,apport information
1666561,2017-02-22 15:10:52 UTC,apport information
1666561,2017-02-22 15:10:56 UTC,apport information
1666561,2017-02-21 18:00:56 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1666570,2017-05-25 16:42:13 UTC,This bug was fixed in the package tomcat8 - 8.0.32-1ubuntu1.4
1666570,2017-05-18 20:02:49 UTC,Tested and verified tomcat7 7.0.52-1ubuntu0.11 and tomcat8 8.0.32-1ubuntu1.4 on Trusty and Xenial.
1666570,2017-06-16 11:34:39 UTC,Could someone please test the tomcat8 yakkety package so I can follow it with a security update? Thanks!
1666570,2017-05-11 22:18:59 UTC,"Hello Andy, or anyone else affected,"
1666570,2017-05-11 22:16:31 UTC,I've clicked the rebuild button on Launchpad for tomcat7 for yakkety and xenial to see if it was a temporary failure.
1666570,2017-05-11 23:13:41 UTC,"Well, clicking rebuild didn't fix anything - sorry!"
1666570,2017-06-16 16:33:34 UTC,Tomcat8 in proposed (8.0.37-1ubuntu0.2) verified per instructions under test case.
1666570,2017-05-11 22:14:51 UTC,"Hello Andy, or anyone else affected,"
1666570,2017-06-19 10:59:25 UTC,This bug was fixed in the package tomcat8 - 8.0.37-1ubuntu0.2
1666570,2017-06-23 02:22:05 UTC,tomcat7 on Xenial and Yakkety failed to build.
1666570,2017-08-17 16:11:32 UTC,Marking yakkety as won't fix due to EOL status.
1666570,2017-08-17 16:29:32 UTC,"Removing verification-needed, as all verification is complete on this bug. Working on LP: #1664179 next."
1666570,2018-11-29 08:49:11 UTC,"Note: as implied by Mathew Hodson, the tomcat7 package for Xenial has _not_ yet been updated (because the package failed to build.)"
1666570,2018-12-03 07:44:03 UTC,"This bug causes tomcat7 postinst to fail if GC logging with rotation is enabled in /etc/default/tomcat7, e.g. like this:"
1666570,2017-04-24 22:11:47 UTC,This bug was fixed in the package tomcat7 - 7.0.52-1ubuntu0.11
1666570,2018-12-03 08:42:48 UTC,One way to work around this until the package gets fixed in xenial is to escape the % sign in the JAVA_OPTS string:
1666570,2017-06-16 16:34:04 UTC,"Sorry, hit post too soon... Tomcat8 in yakkety proposed (8.0.37-1ubuntu0.2) verified per instructions under test case."
1666570,2017-04-19 15:38:34 UTC,"@racb,"
1666570,2017-04-19 15:34:08 UTC,@sru-team
1666570,2017-04-13 10:04:12 UTC,"I think everything is in -proposed or in the unapproved queues pending SRU review now, so unsubscribing ~ubuntu-sponsors (I forgot to do this when I uploaded)."
1666570,2017-02-22 18:45:19 UTC,Thank you for taking the time to file a bug report and try to solve it!
1666570,2017-02-22 18:48:22 UTC,Can you get the output of the following:
1666570,2017-02-22 19:44:09 UTC,"You are indeed correct, the culprit is a `%` in the java options of our affected servers, one example being:
JAVA_OPTS=""-Djava.awt.headless=true -XX:ErrorFile=/var/log/tomcat7/java_error%p.log -Xms15025m -Xmx15025m -XX:+DisableExplicitGC -XX:+UseG1GC -XX:+UseStringDeduplication"""
1666570,2017-03-02 18:52:36 UTC,Let me know if there is anything further I can do to move this forward.
1666570,2017-03-02 20:08:21 UTC,Thanks for the ping.
1666570,2017-03-07 16:05:16 UTC,"That is an elegant solution, thanks for staying on top of this!"
1666570,2017-03-08 23:59:19 UTC,"Created PPA with fix for Trusty here:
https://launchpad.net/~powersj/+archive/ubuntu/tomcat7-1666570"
1666570,2017-03-07 15:38:11 UTC,This is how upstream has fixed this:
1666570,2017-03-09 20:49:46 UTC,"Only source package, binary is not present in zesty"
1666570,2017-03-09 21:59:15 UTC,"@Andy I have committed fixes for all changes to our importer. They will be reviewed and accepted, unless I need to make any changes :) Once accepted, the new packages will enter the proposed pocket for final testing and acceptance and after a minimum of 7 days released. I believe I have that right, but open to correction from anyone ;)"
1666570,2017-04-05 18:14:34 UTC,"Hello Andy, or anyone else affected,"
1666570,2017-04-05 18:16:15 UTC,"Hello Andy, or anyone else affected,"
1666570,2017-04-05 18:24:48 UTC,"Hello Andy, or anyone else affected,"
1666570,2017-04-10 19:22:44 UTC,"I've reviewed and uploaded Josh's MPs for tomcat8. Since there are three and some review comments are shared, I'm writing them up here to avoid confusion between the multiple MPs."
1666570,2017-04-11 04:04:37 UTC,This bug was fixed in the package tomcat8 - 8.0.38-2ubuntu2
1666570,2017-03-09 00:35:18 UTC,"The attachment ""debdiff for trusty"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1666571,2017-07-08 14:30:30 UTC,"Thanks, seems I forgot to update the bug status back then...
So far nobody complained about those folders not being created anymore ;-)"
1666571,2017-02-21 22:15:45 UTC,"I wondered about those folders, too (their creation was already part of the initial efforts to support CMake on Windows (r15011). Sadly Sebastian Faubel stopped working on it after it was somewhat working but did not fix the remaining issues (they're on my todo list though, should I find the time)."
1666571,2017-02-21 23:54:29 UTC,"On 2017-02-21 23:15 (+0100), Eduard Braun wrote:

> Do we need those folders at all (i.e. does it make sense to create
> them seeing they're all empty with the exception of the /doc
> folder)?
"
1666571,2017-07-08 12:29:02 UTC,"The issue as originally reported no longer reproduces with current git master, probably fixed with
https://gitlab.com/inkscape/inkscape/commit/a42c31431619e71e4da2166fdb28ac49f5ffc365"
1666571,2017-07-08 14:34:00 UTC,"Regarding comment #1: I currently have no idea how to fix this without a considerable (in my opinion unreasonable) amount of effort, so I'd just drop it for the time being...
Our translations all rely on the structure of the source tree, and decoupling that would only create new issues..."
1666592,2017-03-13 18:26:09 UTC,"This issue was fixed:
https://github.com/aepifanov/mos_mu/commit/6ebd78414b45162a274578f17b6bb7987a79a989
Now we are working with packaging.
Later I will update how it will be released (as a part of MU or just by upgrading the only this package)"
1666600,2017-02-21 19:24:50 UTC,"I'm not sure we'd want it to skip the empty file would we? I agree the stacktrace is a bit unfriendly, but I think it should error out telling you you're trying to pass it an empty file (which presumably you didn't want to do)."
1666602,2017-11-23 12:40:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666621,2017-02-21 19:09:01 UTC,"This document is auto-generated. So, volumes_type parameter exists, and it will be taken into account if volumes-per-node is present. Otherwise there is no sense to set that up."
1666621,2017-02-21 20:44:43 UTC,"The example was abbreviated.
I am setting up volumes for my worker nodes."
1666621,2017-02-21 20:49:25 UTC,"My example in the inital bug report shows that the openstack client think so as well.
create() got an unexpected keyword argument 'volumes_type'"
1666621,2017-02-21 21:19:03 UTC,When you use json to create node group you should use the following:
1666622,2017-03-03 21:46:47 UTC,"Hi Tina,"
1666622,2017-03-06 16:31:01 UTC,Two test cases:
1666623,2017-02-21 19:19:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666623,2017-02-21 19:20:28 UTC,"I have seen similar behavior on a Lenovo X1 Carbon (4th Gen) running Ubuntu 16.04, both directly attached, and through the OneLink+ dock."
1666624,2017-04-26 07:05:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666649,2018-01-25 09:01:01 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3649
1666657,2017-09-09 12:07:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666665,2017-09-11 02:44:59 UTC,"Thanks, Dylan.  I will look into this."
1666665,2018-01-28 08:51:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666671,2017-03-01 17:07:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439720"
1666671,2017-03-08 16:37:55 UTC,"Change abandoned by Jorge Niedbalski R. (<email address hidden>) on branch: master
Review: https://review.openstack.org/439720
Reason: I will abandon this change in favor of the service-discovery topic. Thanks."
1666680,2019-03-28 10:35:35 UTC,What is this bug about? Is it still valid? If yes - please update.
1666680,2019-05-28 04:17:33 UTC,[Expired for kolla because there has been no activity for 60 days.]
1666683,2017-03-01 16:41:46 UTC,After a few days of uptime I still saw issues with the ratio set to 100. I'll give 0 a try.
1666683,2017-03-01 15:38:49 UTC,"Keep in mind, overcommit considers *committed* address space, not used. So a process which creates a large anonymous mapping but doesn't touch any of that memory (so the address space is committed but no actual pages of RAM are assigned to the address space) will count against overcommit even though it consumes no RAM. Therefore overcommit_ratio=100 is actually pretty conservative, as it's common for processes to have some mappings which don't aren't backed by RAM (but could be)."
1666683,2017-02-22 17:29:12 UTC,"Hm. Oddly enough, pulseaudio seemed to have problems for me until I set the overcommit ratio higher (to 150)."
1666683,2017-03-01 17:05:53 UTC,"Sorry, I mean overcommit_memory=0. overcommit_ratio=0 is likely to be a disaster."
1666683,2017-02-21 21:31:01 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1666683,2017-02-22 01:02:18 UTC,"Changing status to ""Confirmed"". I don't think there are any relevant logs for this issue. Here's some anecdotal evidence, though:"
1666690,2017-02-23 18:50:36 UTC,"> The mechanism for sharing only compatible content is already in place.
> It is the „content” attribute of the interface. Unless it matches snapd
> will not attempt to make the connection. On other words, in the circle
> of snaps a given entity maintains the content attribute of the content
> interface can be used to indicate compatibility.
"
1666690,2019-10-15 12:12:15 UTC,Thank you for the suggestions:
1666690,2017-02-22 17:12:57 UTC,"""don’t do things that break."" is simple to suggest, but harder to police when multiple projects are involved (even from a single publisher)."
1666690,2017-02-21 22:31:32 UTC,Simple: don’t do things that break.
1666705,2019-06-09 16:49:08 UTC,"A rm-fix has been released.  btrfs-debug-tree has been deprecated in -progs 4.4, removed in 4.16, we're on 5.1 now."
1666709,2017-03-29 23:00:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666714,2017-02-21 23:05:27 UTC,Test files.
1666714,2017-02-21 23:12:42 UTC,Proposed patch by Mc (shared on irc as http://paste.debian.net/914822/ ).
1666714,2017-02-22 08:38:27 UTC,"Reproduced on Xubuntu 16.04, lp:inkscape rev. 15537."
1666714,2017-02-22 09:37:08 UTC,Patch tested successfully on Xubuntu 16.04.
1666714,2017-02-28 22:08:02 UTC,Committed to r15556
1666739,2017-02-23 18:20:04 UTC,This is a section of the YAML that snapcraft silently passes through to snapd (it doesn't process it whatsoever). Actually validating it would require one of two things:
1666739,2017-02-24 01:36:05 UTC,"I hear you on the difficulty of fixing this, but I think it needs to be fixed regardless. It sucks if I make an innocent mistake and nothing alerts me to the fact that I've just written nonsense. (How would I feel if the C compiler simply would say nothing for an incorrect statement and silently not generate code for it?)"
1666739,2017-02-24 16:59:50 UTC,"I agree, I'm just not sure what the best solution might be. I'll bring this up at standup to discuss."
1666751,2017-02-22 07:05:34 UTC,"-> status = kwargs.get('phase') or entity.status
(Pdb) l
 32             ctx = action.context
 33             entity = action.entity
 34             if entity is None:
 35                 import pdb
 36                 pdb.set_trace()
 37  ->         status = kwargs.get('phase') or entity.status
 38             reason = kwargs.get('reason') or entity.status_reason
 39             otype = cls._check_entity(entity)
 40             cluster_id = entity.id if otype == 'CLUSTER' else entity.cluster_id
 41             # use provided timestamp if any
 42             timestamp = kwargs.get('timestamp') or timeutils.utcnow(True)
(Pdb) bt
  /usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py(214)main()
-> result = function(*args, **kwargs)
  /opt/stack/senlin/senlin/engine/scheduler.py(77)_start_with_trace()
-> return func(*args, **kwargs)
  /opt/stack/senlin/senlin/engine/actions/base.py(470)ActionProc()
-> EVENT.info(action, consts.PHASE_START)
  /opt/stack/senlin/senlin/engine/event.py(95)info()
-> _dump(logging.INFO, action, phase, reason, timestamp)
  /opt/stack/senlin/senlin/engine/event.py(73)_dump()
-> phase=phase, reason=reason, timestamp=timestamp)
  /usr/local/lib/python2.7/dist-packages/stevedore/extension.py(259)map_method()
-> method_name, *args, **kwds)
  /usr/local/lib/python2.7/dist-packages/stevedore/extension.py(232)map()
-> self._invoke_one_plugin(response.append, func, e, args, kwds)
  /usr/local/lib/python2.7/dist-packages/stevedore/extension.py(263)_invoke_one_plugin()
-> response_callback(func(e, *args, **kwds))
  /usr/local/lib/python2.7/dist-packages/stevedore/extension.py(237)_call_extension_method()
-> return getattr(extension.obj, method_name)(*args, **kwds)

> /opt/stack/senlin/senlin/events/database.py(37)dump()


-> status = kwargs.get('phase') or entity.status
(Pdb) p action
<senlin.engine.actions.cluster_action.ClusterAction object at 0x7fbde66f3850>
(Pdb) p action.entity
None
(Pdb) p action.__dict__
{'domain': None, 'updated_at': None, 'entity': None, 'owner': '0d2e9936-3ec7-4733-8344-e69097980895', 'id': '75d01266-35bd-46a0-b2cf-1d83e539bac6', 'data': {}, 'cause': u'RPC Request', 'status': u'RUNNING', 'inputs': {}, 'context': <senlin.common.context.RequestContext object at 0x7fbde6b087d0>, 'outputs': {}, 'start_time': 1487743104.0, 'user': u'3c4d64baadcd437d8dd49054899e73dd', 'status_reason': u'The action is being processed.', 'target': 'fe35b2b7-1e90-4c17-8fcf-4ef1890f2ebd', 'name': u'cluster_check_fe35b2b7', 'created_at': datetime.datetime(2017, 2, 22, 5, 58, 31, tzinfo=<UTC>), 'interval': -1, 'project': u'cf7a6ae28dde4f46aa8fe55d318a608f', 'end_time': None, 'timeout': 3600, 'action': u'CLUSTER_CHECK'}
(Pdb)"
1666767,2017-02-22 06:30:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436779"
1666767,2018-08-06 11:34:10 UTC,"Change abandoned by Witold Bedyk (<email address hidden>) on branch: master
Review: https://review.openstack.org/436779"
1666776,2017-02-22 07:01:06 UTC,This change was made by a bot.
1666776,2017-02-22 15:51:15 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1666776,2017-02-23 18:47:43 UTC,"Thank you for the tip! Actually the CPU/GPU is pretty new, so the support definitely improved since kernel 4.4 (I think that the support for this GPU has been added in 4.3; kernel 4.4 had artifacts of hiding mouse cursor, 4.8 works pretty decently, apart from the abovementioned reported issue)."
1666779,2017-04-20 05:53:21 UTC,"Reviewed:  https://review.openstack.org/409351
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=429703a9a8781c38c709551a3cfed35ca3d2c574
Submitter: Jenkins
Branch:    master"
1666779,2017-02-22 06:38:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436783"
1666779,2017-02-22 18:41:59 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: master
Review: https://review.openstack.org/436783
Reason: I was not aware of the existing patch. Will proceed there."
1666779,2017-06-07 22:17:42 UTC,"Change abandoned by Sam Yaple (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/468134"
1666779,2017-05-25 19:00:10 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/468134"
1666781,2017-09-17 17:45:53 UTC,ok thx Aaron.
1666781,2017-09-24 17:22:09 UTC,should be fixed in 4ppa48
1666781,2017-09-17 03:15:59 UTC,"At the time, I was either running KXStudio 14.04 which is just a derivative of Ubuntu or was running KDE Neon (which I use now). Either way, it's basically plain Ubuntu on the kernel level. I had simply installed the low-latency variant and removed the generic. That was probably something I did and not default for those systems."
1666781,2017-02-22 06:44:24 UTC,"I should add that the command seemed to work, and everything said it was fine until the final end that said there were errors but I could try to reboot anyway. I think that it said there were errors when I used the linux-lowlatency substitute also, except then I booted successfully. So, I had to reboot a couple times and redo the whole process before I determined this problem and solution."
1666781,2017-09-16 22:09:38 UTC,"hi Aaron, thx for the report and sorry for the late answer.
Which OS did you try to repair ?"
1666802,2017-02-22 09:08:13 UTC,"What do you mean with ""other desktop environments""?"
1666802,2017-02-22 14:57:32 UTC,I tested gnome-shell and cinnamon.
1666809,2019-07-06 22:11:04 UTC,Fixed in https://git.launchpad.net/kicad/commit/?id=562ab0bdeaaf19f414cf0e711c7a3e4d1ada94f8
1666809,2018-07-24 19:19:46 UTC,Two DRC settings:
1666809,2018-07-24 18:16:29 UTC,"Hi Jeff,
What do you mean by ""courtyard settings"" ?"
1666809,2018-07-24 17:48:56 UTC,While we're there we should also add the two courtyard settings.
1666809,2018-07-24 19:44:37 UTC,"Before we add more DRC stuff to the board file, there is currently a
proposal to create a separate constraints file which seems like a
possible candidate to place DRC settings rather than making a change to
the board file format only to remove it later on."
1666809,2018-07-17 22:36:35 UTC,"I would like to co-relate this implementation with this possibly feature
https://bugs.launchpad.net/kicad/+bug/1767349"
1666809,2018-05-19 20:06:10 UTC,I added this to v6 milestone because I think we need to consider this in v6.
1666809,2018-07-22 21:59:22 UTC,"I left TODOs in the code for these, but it will have to wait for 6.0 when (if?) we update the board file format."
1666811,2017-03-21 20:39:33 UTC,"This is not a problem in PyFlakes but in the formatted literals implementation in the core of CPython itself. The AST child Name node for the formatting variables reports 1 as both line and column as the nodes are generated by PyParser_ASTFromString ""automagically"" in fstring_find_expr  (Python/pythoinrun.c and Python/ast.c respectively)."
1666811,2017-03-22 00:08:42 UTC,"Sadly this is true, the Name elements of an fstring carry an useless lineno, as the following script demonstrates:"
1666811,2017-10-04 08:39:41 UTC,"FYI, this is solved in Python 3.6.3, yay!"
1666824,2017-02-22 10:23:29 UTC,Reported upstream: https://github.com/cnc-club/gcodetools/issues/8
1666824,2017-02-23 05:20:12 UTC,"1) While drawing in ""node mode"" in 'View/display mode/toggal' 'ctrl+5'""outline mode"" the Vector lines of
   display goes IN and OUT. The nodes are still visible, if you nug page up/down or to the side display
   comes back temporarily."
1666829,2017-02-27 10:30:46 UTC,No problem with Python 3
1666829,2017-02-27 13:16:09 UTC,"Annoyingly it appears to be impossible to use `locale.setlocale()` on MS Windows: it raises an error for all locales, including `None` which ought to be supported.
The result is that getdefaultlocale() returns ('None', 'None') just like it does on my Mac set-up."
1666829,2017-02-27 12:52:23 UTC,This patch selects UTF-8 encoding at the application level.
1666829,2017-02-27 11:17:20 UTC,"As I thought, this is a locale issue; I'm getting"
1666829,2017-02-26 08:52:34 UTC,"An additional thought: if my understanding of the documentation is correct, the default encoding used for the operations that fail for me is based on the user's current locale settings. That could mean they can also occur on Linux for users who use a more or less exotic locale."
1666829,2017-02-25 17:45:53 UTC,"Ok, I'm not getting tracebacks because most places where the encoding error occurs are protected with a try/except construct."
1666829,2017-02-24 09:26:08 UTC,"No, that's with the original code."
1666829,2017-02-24 08:30:47 UTC,UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in position 368: ordinal not in range(128)
1666829,2017-02-22 15:00:10 UTC,"I don't get tracebacks (not sure why), just errors like this on the terminal:"
1666829,2017-02-22 10:39:28 UTC,"I don't understand, the filename is always an unicode string."
1666831,2018-05-10 20:43:59 UTC,"Reviewed:  https://review.openstack.org/566367
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e3385707cb1ced55cd12b1314d8c0b68d354c38
Submitter: Zuul
Branch:    master"
1666831,2018-05-10 16:17:55 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/567630"
1666831,2018-05-10 16:01:03 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/567625"
1666831,2018-05-10 15:39:32 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/567623"
1666831,2018-05-04 17:12:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/566367"
1666831,2017-10-30 14:01:33 UTC,"Turns out that the fix for this bug accidentally broke boot-from-volume setups that use NFS. In particular, this line:"
1666831,2017-05-08 17:54:23 UTC,Newton [1] is currently under phase II support [2] so a low priority bugfix like this isn't appropriate for stable/newton unfortunatley.
1666831,2017-04-14 09:23:39 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1666831,2018-05-11 02:52:07 UTC,"Reviewed:  https://review.openstack.org/567623
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=174764340d3c965d31143b39af4ab2e8ecefe594
Submitter: Zuul
Branch:    stable/queens"
1666831,2017-03-15 11:15:51 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1666831,2017-03-13 16:30:33 UTC,"Reviewed:  https://review.openstack.org/441037
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97752d9c54db13a1317620270c2c443e5702cc89
Submitter: Jenkins
Branch:    stable/ocata"
1666831,2017-03-03 10:18:32 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441037"
1666831,2017-02-24 12:01:01 UTC,"Reviewed:  https://review.openstack.org/437356
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6347baf3d09036525b7f6df991ae440d558f9cc3
Submitter: Jenkins
Branch:    master"
1666831,2017-02-23 12:28:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437356"
1666831,2018-05-12 04:46:26 UTC,"Reviewed:  https://review.openstack.org/567630
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a16fa14ce47bd2d3a5189047e9bd330a607ef3cc
Submitter: Zuul
Branch:    stable/ocata"
1666831,2017-05-01 00:02:54 UTC,"We're experiencing this issue with Nova 14.0.2 in Newton. As the fix appears small, could we see it back ported to Newton?"
1666831,2018-05-11 22:01:19 UTC,"Reviewed:  https://review.openstack.org/567625
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c72a0a7665e96219f0301525edc513dda07b320b
Submitter: Zuul
Branch:    stable/pike"
1666834,2017-02-22 09:35:41 UTC,"Possibly related to the changes for
* Bug #967416 “inkscape crashed with SIGSEGV in file_save()”
  https://bugs.launchpad.net/inkscape/+bug/967416"
1666835,2017-02-22 14:30:05 UTC,"Reviewed:  https://review.openstack.org/436843
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=0efc1357e5c76439ad32b13cbf1a230787af6b19
Submitter: Jenkins
Branch:    master"
1666835,2017-02-22 10:12:34 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/436854"
1666835,2017-02-22 17:22:12 UTC,"Reviewed:  https://review.openstack.org/436854
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=d95727ce0cdc571434a03d599728d391ad990083
Submitter: Jenkins
Branch:    stable/newton"
1666835,2017-02-22 09:33:03 UTC,OSTF tests failure is caused by removing vmware attributes from nailgun:
1666835,2017-04-05 15:47:51 UTC,"Verified 10.1 #1512
Latest runs are passed:
https://ci.fuel-infra.org/view/BVT/job/10.0-community.main.ubuntu.bvt_2/1398/"
1666835,2017-02-22 09:37:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436843"
1666835,2017-02-27 16:26:24 UTC,This issue was fixed in the openstack/fuel-ostf 11.0.0.0rc1 release candidate.
1666836,2017-02-22 09:34:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666837,2017-03-30 11:29:15 UTC,"Reviewed:  https://review.openstack.org/450870
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=41d4a11ee73337de2e9a5cf8fe983c6f0a114bc6
Submitter: Jenkins
Branch:    stable/newton"
1666837,2017-03-02 12:51:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440529"
1666837,2017-03-06 12:11:29 UTC,"Reviewed:  https://review.openstack.org/440529
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=f7e609e612a9fd95a2f44399315a73d744c1ef7c
Submitter: Jenkins
Branch:    master"
1666837,2017-03-07 09:56:43 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/442349"
1666837,2017-03-07 12:41:17 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442439"
1666837,2017-03-07 16:16:25 UTC,"Reviewed:  https://review.openstack.org/442439
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=54135a5d0bbc70de63678b71131dc5e773b13f5b
Submitter: Jenkins
Branch:    stable/ocata"
1666837,2017-03-08 12:21:14 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1666837,2017-03-09 13:15:11 UTC,"Reviewed:  https://review.openstack.org/442349
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=ae92db53ad1344dc26026e612bb7cfa47aa4023b
Submitter: Jenkins
Branch:    stable/mitaka"
1666837,2017-03-14 10:32:50 UTC,Verified on 9.2 + mu1 updates.
1666838,2017-02-22 12:01:01 UTC,"You are speaking of the non-periodic case, aren't you?
It seems it is using the pre-processor ""TriaxialTest"", I can imagine that this old lady is not giving exactly what it was years ago, then maybe the bad results you get.
It should not be too difficult to test what the curretn code is doing, and fix or replace by a more recent one inspired by some triaxial simulations from example folders.
Bruno"
1666838,2019-02-05 20:28:23 UTC,moved from https://bugs.launchpad.net/yade/+bug/1666838 to https://gitlab.com/yade-dev/trunk/issues/34
1666845,2017-02-22 12:34:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1666848,2017-02-22 19:36:35 UTC,"For simplicity, the same error can be seen with /dev/null used as an input."
1666850,2017-02-22 14:27:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436945"
1666850,2019-04-09 08:58:53 UTC,"Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: master
Review: https://review.openstack.org/436945
Reason: abandoning due to no activity"
1666851,2017-06-04 15:15:43 UTC,This also affects me.
1666851,2017-06-04 15:15:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666853,2019-01-18 20:08:26 UTC,"Possibly related bugs:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1812411
https://bugs.launchpad.net/cloud-utils/+bug/1762748"
1666853,2017-09-18 16:25:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666853,2017-02-22 11:55:40 UTC,verbose grub-probe
1666853,2017-02-22 10:56:54 UTC,here is the manual reproduction
1666863,2017-02-22 11:20:31 UTC,"i think the focus is somehow still in the Authors tab or something like that, i see this with tiled even if i open a child window and click in a random box with scrollbars it still scrolls the previous focused in the main window o_O"
1666875,2018-10-28 11:26:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666875,2018-10-28 11:28:49 UTC,Believe this is occurring on my 18.10 system running anacron 2.3-24.
1666875,2018-10-30 18:17:28 UTC,Don't fully understand the interaction between systemd-anacron-cron but in my system at boot systemd starts multi-user.target-wants/anacron.service calling anacron -dsq which should kick off a job to rotate the logs.  This doesn't get started because of the ConditionACPower=true in the anacron.service file.  Since always start my laptop on battery the condition is never met.  Unsure of what event/process is supposed call anacron.service when the power cable is plugged or after it is plugged other than a reboot.  Going to remove this condition from the anacron.service file.
1666875,2018-10-31 13:06:49 UTC,Removing the ConditionACPower didn't help.  Still believe that systemd starting the anacron job is the only way to get logrotate to run.  If the anacron.service runs the only thing it appears to do is to run 0anacron which runs anacron -u.  This only sets the date in /var/spool/anacron/cron.daily to the current date.  systemd will start anacron after the first boot of the day and the system has AC power. Rebooting the system after the first boot fail to have systemd start anacron.  Don't yet understand that.  Going to run logrotate manually for now.
1666875,2020-07-23 23:18:46 UTC,"The original systemd service file may be restored on system update. Rather, make an override file /etc/systemd/system/anacron.service.d/on-ac.conf with"
1666875,2020-07-24 04:05:40 UTC,"Sorry for my misleading earlier post. Both parts were wrong.
1. ConditionACPower=no means to run on battery only; to ignore AC, it must be empty.
2. The ANACRON_RUN_ON_BATTERY_POWER flag has no effect when anacron is launched via systemd."
1666884,2019-01-08 00:12:26 UTC,Re-subscribed ubuntu-security-sponsors - the attached patch fixes the CVEs.
1666884,2018-11-09 15:09:18 UTC,"Someone needs to attach updated debdiffs to fix the CVEs, including the regression fix and the latest round of CVE fixes."
1666884,2018-09-14 09:05:32 UTC,Pretty sure this also affects bionic and cosmic
1666884,2019-01-22 06:52:21 UTC,"Marc, anything else needed to be done here?"
1666884,2019-01-23 19:55:50 UTC,"I can't actually see the patch in comment #20, I'm getting an encoding error. Are you seeing something similar?"
1666884,2019-01-24 03:08:52 UTC,I've got some concerns about this:
1666884,2019-02-02 04:13:55 UTC,"Seth, no I didn't, it's just the debdiff taken from the dingo source package: https://launchpad.net/ubuntu/+source/libytnef/1.9.3-1"
1666884,2019-04-20 18:41:42 UTC,"Unsubscribing the Security Sponsors team, please resubscribe when Seth's comments have been addressed."
1666884,2018-08-17 11:28:07 UTC,"Apologies for the late reply, I neglected to enable notifications..."
1666884,2019-01-24 02:54:30 UTC,"Ah, my bad. Here it is again."
1666884,2018-07-23 18:53:28 UTC,"Hi Oliver,"
1666884,2019-01-08 00:09:16 UTC,Attached patch updates from from 1.9.2 to 1.9.3
1666884,2018-07-12 08:13:57 UTC,"Hey Leonidas,"
1666884,2017-05-25 22:39:48 UTC,Thanks for the debdiffs! The only change that I made was to the version used in the Zesty debdiff. I changed 1.9.2-1ubuntu0.17.04 to 1.9.2-1ubuntu0.1 as suggested here:
1666884,2018-07-21 10:10:58 UTC,"Hi, I implemented those fixes to libytnef. Yeraze has just released 1.9.3 so I'm interested to see if/when it will make it to Ubuntu, and to which releases."
1666884,2017-08-03 21:34:43 UTC,Unsubscribing ubuntu-security-sponsors. Please subscribe the team if new debdiffs are available.
1666884,2018-06-15 15:36:03 UTC,"The remaining CVE's have recently been fixed (or will be once the last MR lands) in the library's repo. Also, importantly, the one CVE fix that Ubuntu did ship last year broke the library's normal operation, making it less than useful for decoding"
1666884,2018-06-16 02:11:08 UTC,"Hello Michael, do you have a bug report for the regression?"
1666884,2017-05-26 23:39:17 UTC,The testing for the Trusty update did not go as expected. The test case linked to from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862556#5 crashes Evolution the same way with and without the updated libytnef0 package.
1666884,2018-06-28 17:54:57 UTC,"Hi Michael,"
1666884,2018-06-30 03:38:05 UTC,"Hey Leonidas,"
1666884,2018-07-02 12:52:48 UTC,"Hey Michael,"
1666884,2018-06-17 05:02:09 UTC,"Hey Seth, have a look at the last two comments in the original ticket for the first CVE that was reported: https://github.com/Yeraze/ytnef/issues/45#issuecomment-393044169 . The PR with the proper fix for the CVE mentioned there (https://github.com/Yeraze/ytnef/pull/58) has already been merged by the maintainer. Note it depends on at least one other PR as well."
1666892,2017-02-22 15:36:11 UTC,"In my machine dolphin doesn't quite work in a unity8 session.
It complains about klauncher, so doesn't show any files in its main area. But, most importantly, ""New Window"" has no effect."
1666892,2017-02-22 18:36:49 UTC,you are probably affected by this bug https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1604260
1666893,2017-04-11 09:19:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666893,2017-05-30 07:24:21 UTC,"May be another Bug, but I found multiple empty devices in the panel. There are also some system-devices listed like ""Prozessor"" or ""USB-PS 2 Optical Mouse. See attached Screenshot."
1666893,2018-01-02 11:25:03 UTC,"Related KDE upstream bug
https://bugs.kde.org/show_bug.cgi?id=369434"
1666897,2017-03-27 15:37:51 UTC,This bug was fixed in the package linux - 4.4.0-70.91
1666897,2017-03-27 15:45:01 UTC,This bug was fixed in the package linux - 4.8.0-44.47
1666897,2017-03-20 08:50:46 UTC,@Denis -- your issue was caused by an attempt to back out the snapd update to 2.23.1 in the archive without also backing out the linux updates that depended on it.  These have now been rolled back also pending a fix for the underlying issue (a dpkg bug trigging upgrade failures).
1666897,2017-03-17 11:58:45 UTC,"This fix breaks Ubuntu 16.04: update-manager did a partial update. It elected to keep snapd (2.22.6) and remove linux-generic and linux-image-generic. This plus a kernel update (4.4.0.67), I ended up with kernel 4.4.0.67 without linux-image-extras of the same version. After reboot, no network, no sound, and so on."
1666897,2017-03-14 16:42:44 UTC,We need to Breaks: snapd (<< 2.23.1~) to ensure this is upgraded before the new breaking kernels can hit.
1666897,2017-02-24 17:16:26 UTC,This is fixed by https://github.com/snapcore/snapd/pull/2935 (2.22) and https://github.com/snapcore/snapd/pull/2936 (master)
1666897,2017-02-25 00:30:19 UTC,This was released in snapd 2.22.7 although only for new installs. Fix for existing installation will come in a 2.2x release (either 23 or 24)
1666897,2017-02-24 10:33:47 UTC,Thank you for confirming this. I will make it happen.
1666897,2017-02-24 10:13:23 UTC,I'll right I have chased this down
1666897,2017-02-23 22:43:31 UTC,@John -- i have accepted the same snapd into yakkety to allow some comparative testing.
1666897,2017-02-22 19:26:23 UTC,"AppArmor wise the zesty kernel has a set of fixes on that have not been released yet for xenial, or yakkety. However I wouldn't expect that set of patches to result in a change around file_mmap (at least not directly)."
1666897,2017-02-22 15:21:28 UTC,"This appears related to the recent zesty kernel update. If I use a xenial VM and update to the zesty kernel, I can reproduce. Eg:"
1666897,2017-02-24 11:05:40 UTC,"Note: this same fix will be landing in xenial, yakkety, and trusty-hwe kernels. So the template will need to be updated everywhere."
1666900,2017-03-01 10:09:50 UTC,"Happened to connect my Pi Zero through a hub today. The interface name on the PC becomes ""enp0s26u1u3u3i1"" which itself is already 15 characters, so no room at all to append a label."
1666900,2017-03-05 01:38:33 UTC,"Paul: Could you file this in the upstream bug tracker here?
https://github.com/lathiat/avahi/issues/new"
1666902,2017-02-22 13:53:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666902,2017-02-22 13:58:14 UTC,"One thing that has come up on the related Wayland discussion is the fact, that Peek uses the window positioning to obtain the recording coordinates. This is very different from e.g. the more traditional approach of"
1666902,2017-02-23 03:32:40 UTC,"See also:
https://bugs.launchpad.net/mir/+bugs?field.tag=screencast"
1666904,2018-04-11 01:19:43 UTC,At least with Juju 2.3.5 you can do a charm upgrade from a charmstore charm to a local charm by doing:
1666904,2018-04-09 21:34:50 UTC,I want to switch a deployed application from the charmstore to a local branch and I'm getting this problem. here is a copy of my terminal
1666904,2018-01-15 06:07:33 UTC,"We need --switch because:
""The --switch flag allows you to replace the charm with an entirely different one.
The new charm's URL and revision are inferred as they would be when running a
deploy command."""
1666904,2018-01-12 10:29:44 UTC,"Hi,"
1666904,2018-01-14 23:56:39 UTC,"Hmm, don't we need '--path' instead for local charms?"
1666912,2017-02-22 17:29:16 UTC,A backport of an upstream-merged workaround for this issue.
1666912,2017-02-22 20:16:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666912,2017-02-27 08:35:43 UTC,"For people suffering from this, a clean workaround is to change the VPN configuration as follows:"
1666912,2017-02-27 09:56:29 UTC,"An even better fix for your configuration is to change the dropdown to ""verify name exactly"", and then remove the ""CN="" part of the field if you previously had one in your subject match."
1666912,2017-03-29 09:19:36 UTC,"Aron, could you look if that change is right?"
1666912,2017-04-03 15:14:37 UTC,"This patch should not be applied as-is; as Chris mentions, the correct thing to do is to modify the settings in the VPN connection."
1666912,2017-09-01 16:21:23 UTC,This bug was fixed in the package network-manager-openvpn - 1.2.10-0ubuntu1
1666913,2017-04-13 11:46:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/456582"
1666913,2017-04-25 14:01:02 UTC,"Reviewed:  https://review.openstack.org/456579
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=8f094044f9fc3a4de5451872c5c7914a5e18a02c
Submitter: Jenkins
Branch:    stable/newton"
1666913,2017-04-13 11:42:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/456579"
1666913,2019-12-18 17:38:52 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/mitaka
Review: https://review.opendev.org/456578
Reason: This repo is retired now, no further work will get merged."
1666913,2017-04-13 11:32:26 UTC,"Reviewed:  https://review.openstack.org/454574
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=b8e2606dafeaff409f9cef22af18b4262f07f8fb
Submitter: Jenkins
Branch:    master"
1666913,2017-04-07 07:26:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454574"
1666913,2019-12-18 17:38:41 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/456582
Reason: This repo is retired now, no further work will get merged."
1666913,2017-04-13 11:42:26 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/456578"
1666914,2017-02-25 13:01:43 UTC,seems to work fine with silo 2481
1666914,2017-02-22 14:17:35 UTC,"-- Logs begin at Wed 2017-02-22 15:04:18 EET, end at Wed 2017-02-22 16:16:58 EET. --
Feb 22 16:11:32 pixel-desktop systemd[3063]: Starting ubuntu-app-launch-application-legacy-quassel-1487772692606362.service...
Feb 22 16:11:35 pixel-desktop quassel[19784]: Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
Feb 22 16:11:37 pixel-desktop quassel[19784]: QMetaMethod::invoke: Unable to handle unregistered datatype 'QPlatformWindow*'
Feb 22 16:11:37 pixel-desktop quassel[19784]: Quassel IRC:  ""0.12.4""   ""90183eeb030dd4dda32e4f107e8bcf13f393388d""
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  0 quassel              0x0000563f1f9b082c Quassel::logBacktrace(QString const&)
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  1 quassel              0x0000563f1f988239 Quassel::handleSignal(int)
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  2 libc.so.6            0x00007f3356a5d860 0x0000000000000000
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  3 libQt5DBus.so.5      0x00007f3359790ae5 QDBusAbstractAdaptor::setAutoRelaySignals(bool)
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  4 libubuntuappmenu.so  0x00007f3331a2ef32 0x0000000000000000
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  5 quassel              0x0000563f1f78af93 StatusNotifierItem::init()
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  6 quassel              0x0000563f1f76d5a2 MainWin::init()
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  7 quassel              0x0000563f1f7717f4 QtUi::init()
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  8 quassel              0x0000563f1f71995d 0x0000000000000000
Feb 22 16:11:37 pixel-desktop quassel[19784]: #  9 quassel              0x0000563f1f718a74 MonolithicApplication::init()
Feb 22 16:11:37 pixel-desktop quassel[19784]: # 10 quassel              0x0000563f1f716348 main
Feb 22 16:11:37 pixel-desktop quassel[19784]: # 11 libc.so.6            0x00007f3356a483f1 __libc_start_main
Feb 22 16:11:37 pixel-desktop quassel[19784]: # 12 quassel              0x0000563f1f717f69 _start
Feb 22 16:11:38 pixel-desktop systemd[3063]: ubuntu-app-launch-application-legacy-quassel-1487772692606362.service: Main process exited, code=exited, status=1/FAILURE
Feb 22 16:11:38 pixel-desktop systemd[3063]: Failed to start ubuntu-app-launch-application-legacy-quassel-1487772692606362.service.
Feb 22 16:11:38 pixel-desktop systemd[3063]: ubuntu-app-launch-application-legacy-quassel-1487772692606362.service: Unit entered failed state.
Feb 22 16:11:38 pixel-desktop systemd[3063]: ubuntu-app-launch-application-legacy-quassel-1487772692606362.service: Failed with result 'exit-code'."
1666915,2017-02-22 14:43:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/436953"
1666915,2017-12-19 08:47:08 UTC,"Change abandoned by Daniel Pawlik (<email address hidden>) on branch: master
Review: https://review.openstack.org/436953"
1666916,2020-10-28 15:59:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/760174"
1666916,2020-11-11 14:46:04 UTC,"Reviewed:  https://review.opendev.org/760174
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=a8ff5de91c6e9e315afe5ebc2de108069e0e8f42
Submitter: Zuul
Branch:    master"
1666920,2017-07-26 08:01:44 UTC,"This bug is related to:
  https://bugs.launchpad.net/os-vif/+bug/1677238: ""Convert Linux Bridge os-vif driver to use native Python bindings"""
1666921,2017-02-22 19:38:12 UTC,sudo apt-get install -f
1666921,2017-02-22 15:00:08 UTC,This change was made by a bot.
1666921,2017-02-22 16:14:56 UTC,You may need to run the following from a terminal:
1666923,2018-01-25 08:59:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1784
1666923,2017-03-03 11:45:13 UTC,"Sorry, wrong binary log format with 5.6: affected as well."
1666923,2017-03-03 11:18:09 UTC,Version 5.6 is not affected.
1666923,2017-03-03 10:02:08 UTC,Is there an upstream bug report?
1666923,2017-03-03 09:29:40 UTC,Thank you for the report.
1666926,2017-07-28 07:56:46 UTC,(same answer as in 1666927)
1666926,2017-07-18 11:25:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484726"
1666926,2017-07-27 17:39:20 UTC,"As per description: until it's clear what request for enhancement is sought after on the neutron side, marking incomplete. That said, shouldn't this effort be more widely captured as 'adoption of os-vif in neutron', rather than tracking the individual vif types?"
1666926,2017-11-06 08:40:59 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/484726"
1666927,2017-07-27 17:38:55 UTC,"As per description: until it's clear what request for enhancement is sought after on the neutron side, marking incomplete. That said, shouldn't this effort be more widely captured as 'adoption of os-vif in neutron', rather than tracking the individual vif types?"
1666927,2017-11-06 08:41:05 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/485228"
1666927,2017-07-28 07:56:40 UTC,@Armando: you are right. The adoption of os-vif in Neutron should be tracked in a common place.
1666927,2017-07-19 14:57:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/485228"
1666931,2018-02-22 12:15:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546961"
1666931,2018-10-24 15:20:03 UTC,"Change abandoned by Carlos Goncalves (<email address hidden>) on branch: master
Review: https://review.openstack.org/546961
Reason: Sorry folks, I don't have the cycles to work on this anymore hence I'm abandoning it. Anyone interested in taking on this effort, please feel free to!"
1666936,2017-03-15 11:15:58 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1666936,2017-02-22 19:03:18 UTC,Patch is up https://review.openstack.org/#/c/436475/
1666936,2017-02-22 20:27:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/437123"
1666936,2017-02-22 21:44:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437156"
1666936,2017-02-22 21:45:57 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/437157"
1666936,2017-02-23 02:21:20 UTC,"Reviewed:  https://review.openstack.org/436475
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a377fc5988e9a6057bd14617879a7cbcc3c8bb81
Submitter: Jenkins
Branch:    master"
1666936,2017-02-23 15:41:41 UTC,"Reviewed:  https://review.openstack.org/437156
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=adbf28f8194f901cd99a49da0376475986993f88
Submitter: Jenkins
Branch:    master"
1666936,2017-02-23 16:06:11 UTC,"Reviewed:  https://review.openstack.org/437123
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2bb632ac888703e0a91e14abcede31dc6e46b84e
Submitter: Jenkins
Branch:    stable/ocata"
1666936,2017-02-24 17:38:25 UTC,"Reviewed:  https://review.openstack.org/437157
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9335a49e6386ff338cbc80b8e05d0c296284e85
Submitter: Jenkins
Branch:    stable/ocata"
1666936,2017-04-14 09:23:41 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1666936,2017-04-26 13:36:29 UTC,Is it possible to get this patch backported to Newton?
1666943,2017-02-22 16:44:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437031"
1666943,2017-02-22 16:46:33 UTC,The reason i didn't find it in pecan is because we use werkzeug in Magnum
1666943,2017-06-20 16:18:29 UTC,"Change abandoned by Ricardo Rocha (<email address hidden>) on branch: master
Review: https://review.openstack.org/437031
Reason: Probably better to simply move to apache later."
1666951,2017-03-22 11:43:09 UTC,For 17.04 I've found this problem affecting Lubuntu and Xubuntu but not Ubuntu or Ubuntu MATE. Other flavours not (yet) tested.
1666951,2017-02-23 19:50:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1666951,2017-03-28 09:04:32 UTC,"Re Xubuntu, with ISO of 20170328 I'm still not seeing this bug - good!"
1666951,2017-03-26 10:49:45 UTC,No longer seeing this issue with Xubuntu 64 and 32-bit ISOs as of 20170326
1666951,2017-02-22 16:16:51 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1666959,2017-03-03 16:20:25 UTC,"Thanks for digging into this. Looks like we can treat it as a public report of a potential security hardening opportunity (there are at least some in the community who would eventually like to see every service able to operate over untrusted backend/admin networks, but it should certainly not be an expectation as things stand today)."
1666959,2017-02-24 15:59:11 UTC,"@Tristan Sure, it's not visible from the instance network, but it still requires you to trust the physical network on which the VRRP traffic resides.  As I said in the original report, if the VRRP network is untrusted, there are probably already bigger problems to worry about, but presumably that does not make this problem go away; it just makes it less of a priority at the moment."
1666959,2017-03-02 15:48:24 UTC,"Thanks Kevin for confirming what I wrote in the original report and in comment #4, i.e. that if the VRRP network is untrusted, there are already bigger problems to worry about."
1666959,2017-07-12 16:34:57 UTC,"If the config option is worthless, it's a mild usability issue, and we should drop it. Marking with the corresponding tag."
1666959,2017-03-02 14:30:01 UTC,I don't think this is a security vulnerability. The tenant's HA network is not visible to anyone except for the operator so the risk here is that someone with access to the datacenter network itself could possibly hijack an L3 HA instance. But if they have that level of access they could do all sorts of other things (e.g. interfere with regular tenant network traffic directly rather than trying to interfere with L3HA leader election).
1666959,2017-02-22 16:47:28 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1666959,2017-02-24 05:54:35 UTC,"It seems like the l3-high-availability spec define a dedicated ha network per tenant so that the keepalived traffic isn't visible from instance network. If so, then the authentication shouldn't really matter."
1666959,2017-02-22 16:35:31 UTC,Looks like this was introduced in https://review.openstack.org/70700 back in 2014.4 so affects all currently supported branches.
1666987,2019-04-08 18:25:21 UTC,Just dealt with this again... for the last time!
1666987,2018-10-24 23:32:16 UTC,"Seeing as we typically only do this during the .0 release, should this be targeted at 3.1 and 3.2 and not 3.next? I understand that some could run this script on their own if they're doing an installation, but doing so is not part of the typical install steps, nor is it documented anywhere other than the release steps as far as I know."
1666987,2018-05-13 15:06:45 UTC,"To get this working in the short term, I pushed a two-line fix that adds an ""Evergreen/3.1"" user agent to the script to http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/lp1666987_build_relator_map_ua"
1666987,2018-11-19 03:20:04 UTC,I agree with Jason's comment and recommend that we only target this towards the next future major series.  It's not typically checked during maintenance releases as far as I know.
1666987,2017-03-03 19:29:03 UTC,"I noticed this also during the 2.11 cycle, and reached the same conclusions, so marking as confirmed."
1666987,2017-02-22 16:24:43 UTC,Note that I've verified for the purpose of building 2.12-beta that there have been no relator code changes since the last time Evergreen's copy was updated in 2015.
1666987,2018-02-21 20:50:26 UTC,Taking a look at this.  Initially planning to fix the current approach of downloading the HTML file and using a parser like HTML::TableExtract to grab the codes.
1666993,2017-02-22 17:48:07 UTC,This sounds more like a UITK issue than unity8.
1666993,2017-02-22 18:33:01 UTC,"That's a fair point, for languages at least. On the other hand most people do speak English and a search mask that only accepts Latin letters (I haven't seen a keyboard without Latin letters yet) is better than none at all."
1666993,2017-02-28 10:06:40 UTC,While it may be up for debate whether most of the Chinese speakers who easily outnumber native English speakers have access to and know how to handle English input...
1666998,2017-02-22 17:37:55 UTC,I am on OpenRails X3797 version
1666998,2017-05-01 12:44:25 UTC,"Set superelevation to 0 and the texture should appear. If you don't use the standard track profile, you must create one or find one for dbTracks if you want the track texture appearing also on superelevated track."
1667001,2017-02-23 16:53:08 UTC,"Ok, with Alexandros' help I've dug a bit more."
1667001,2017-02-24 01:37:28 UTC,That warning might indeed correlate with some flicker:
1667001,2017-02-23 15:15:54 UTC,"@alf:
http://pastebin.ubuntu.com/24053520/"
1667001,2017-02-23 19:33:12 UTC,"One small warning message is printed during display on flicker:
http://pastebin.ubuntu.com/24053776/"
1667001,2017-02-23 03:23:31 UTC,"Oops, sorry Gerry. Didn't realize it was you :)"
1667001,2017-02-23 03:22:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1667001"
1667001,2017-02-23 08:59:38 UTC,Could you please attach /var/log/repowerd.log at the time of the issue.
1667006,2019-12-18 17:47:30 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/438505
Reason: This repo is retired now, no further work will get merged."
1667006,2017-03-23 10:55:48 UTC,The bug is about cobbler and we removed cobbler in Newton.
1667006,2017-03-17 08:03:24 UTC,We got something similar in several swarm threads: https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.bonding_ha/212/testReport/(root)/deploy_bonding_neutron_tun/deploy_bonding_neutron_tun/
1667006,2017-03-07 16:20:15 UTC,"Reviewed:  https://review.openstack.org/442442
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=1d68d74cb0fe462ca3050a4d2854b6718e236ec1
Submitter: Jenkins
Branch:    stable/ocata"
1667006,2017-03-07 12:41:48 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442442"
1667006,2017-03-21 13:08:23 UTC,"Change abandoned by Vladimir Kozhukalov (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/441957
Reason: this is superseeded by https://review.openstack.org/#/c/435561/"
1667006,2017-03-06 12:02:01 UTC,"Reviewed:  https://review.openstack.org/441695
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=6b3d03b1677623ba2a9cc284e3346eec3cbea805
Submitter: Jenkins
Branch:    master"
1667006,2017-02-27 14:18:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438505"
1667006,2017-02-22 18:44:46 UTC,"3) move_to_bootstrap and disable cobbler netboot should happen one by one on the master node
4) move_to_boostrap should fire nailgun agent to generate identity config or we will get into the situation when the node does not have mco id - we need to exit from move_to_bootstrap only when the identity is generated properly, e.g. when nailgun-agent write date to nailgun_uid and fix-configs-on-startup changes the mcollective config and restarts it."
1667006,2017-03-06 14:19:01 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441957"
1667017,2017-02-24 08:31:14 UTC,App icon added in revision 177. Thanks.
1667017,2017-02-24 09:38:16 UTC,"Yeah, I understood you fixed the maximum, and why, so I preserved your default. The cache mechanism still works, so even with my tweak you only have to wait a bit longer (or less long if you shorten the period!) the 1st time the new search is executed. Afterwards startup is just as fast as with the default 14 days setting."
1667017,2017-02-26 09:55:17 UTC,"Re: the app icon: icons are expected to be rectangular. I didn't realise this myself, but you may find that the icon renders better in all situations if you create a rectangular version and use that. I've attached an example, made by adding margins (1 pixel to the left, 34 top and bottom)."
1667040,2017-02-22 18:44:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437061"
1667040,2017-03-03 17:58:24 UTC,"Reviewed:  https://review.openstack.org/437061
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=434a953190647c398160ca815e7ce3c0796fc5a4
Submitter: Jenkins
Branch:    master"
1667040,2017-03-03 20:27:35 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441458"
1667040,2017-03-06 23:57:09 UTC,"Reviewed:  https://review.openstack.org/441458
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a71833131bf513a2c410254e4173f10922a29471
Submitter: Jenkins
Branch:    stable/ocata"
1667067,2017-02-22 19:14:28 UTC,The problem is that we can't do real lexical sorting on simple strings. Our current sorting is just by character code point.
1667067,2019-09-17 10:38:51 UTC,Migrated to https://github.com/widelands/widelands/issues/1669
1667070,2017-02-22 21:09:25 UTC,If you have a group mapping then you would get a combined set of roles (concrete and group membership).
1667070,2017-03-30 00:19:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/451604"
1667070,2017-02-22 19:57:55 UTC,What happens if the mapping also contains group membership (and hence roles) based on your federation assertions? Do you get the superset of all the roles? Only the local ones? Is this an error situation?
1667070,2017-08-02 20:20:43 UTC,Automatically unassigning due to inactivity.
1667076,2017-02-26 15:57:05 UTC,Wrote more details on intermittent screenshots in bug #1668074
1667080,2018-01-24 20:19:26 UTC,"We started using this today to send out hold pickup sms messages.  So far so good.  I haven't started processing the delivery reports yet, to look for clear failures that action can be taken on.  There are like 50 different status codes to evaluate, and I'm not sure how long it takes for some of the errors to get reported back to flowroute.  https://support.flowroute.com/Messaging/Common_Issues/Delivery_Receipt_Response_Codes"
1667080,2018-01-22 21:28:25 UTC,I updated my gist with a version that stores the message id in an async_output event_output.
1667080,2018-01-22 17:30:30 UTC,"Something we will also need is a way to hide all the UI options for sms_provider after we start using this.  So probably another org unit setting, sms.hideprovider."
1667080,2018-01-22 16:54:30 UTC,"After seeing bug 1744358 I took another look at this and got something working.  I stuck the code at https://gist.github.com/stompro/1cd3008785995517e0305fb280a0d8ef for now.  As mentioned by Miker, this doesn't need to be included in evergreen to be used, the SendSMSFlowRoute.pm just need to be in the perl module path."
1667085,2017-03-13 09:30:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667120,2017-02-23 06:56:26 UTC,refer https://review.openstack.org/#/c/437255/
1667120,2017-02-24 04:35:05 UTC,I think the link should be updated to https://docs.openstack.org/developer/kolla/newton/quickstart.html.
1667120,2017-02-27 00:31:16 UTC,not affect to openstack-manuals
1667120,2017-03-07 05:08:45 UTC,"Change abandoned by iswarya vakati (<email address hidden>) on branch: master
Review: https://review.openstack.org/437255
Reason: Merge conflict"
1667133,2017-02-26 22:36:37 UTC,I know for sure now that the touchscreen is the culprit:
1667146,2017-03-08 09:17:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667146,2017-03-08 09:23:40 UTC,"I see this on an Lenovo X1 Gen1.
$ uname -a
Linux lt0972 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:47:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1667146,2017-03-08 09:24:13 UTC,"and part II:
Mar  8 10:11:47 lt0972 kernel: [   18.997522] ------------[ cut here ]------------
Mar  8 10:11:47 lt0972 kernel: [   18.997536] WARNING: CPU: 2 PID: 513 at /build/linux-xIyolH/linux-4.10.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1891 iwl_trans_pcie_grab_nic_access+0xeb/0x
f0 [iwlwifi]
Mar  8 10:11:47 lt0972 kernel: [   18.997537] Timeout waiting for hardware access (CSR_GP_CNTRL 0x080003d8)
Mar  8 10:11:47 lt0972 kernel: [   18.997538] Modules linked in: msr cmac bnep btusb btrtl btbcm btintel uvcvideo bluetooth videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media cdc_mbim cdc_ncm usbnet cdc_acm mii cdc_wdm dm_crypt nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass arc4 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc iwldvm snd_hda_codec_hdmi mac80211 snd_hda_codec_realtek snd_hda_codec_generic aesni_intel aes_x86_64 snd_hda_intel crypto_simd glue_helper cryptd snd_seq_midi intel_cstate snd_hda_codec intel_rapl_perf snd_seq_midi_event snd_hda_core snd_hwdep snd_rawmidi joydev iwlwifi input_leds snd_seq serio_raw snd_pcm thinkpad_acpi cfg80211 nvram lpc_ich mei_me shpchp mei snd_seq_device snd_timer snd soundcore soc_button_array mac_hid
Mar  8 10:11:47 lt0972 kernel: [   18.997586]  intel_smartconnect parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 psmouse i2c_algo_bit drm_kms_helper ahci syscopyarea sysfillrect libahci sysimgblt sdhci_pci fb_sys_fops sdhci drm wmi fjes video
Mar  8 10:11:47 lt0972 kernel: [   18.997603] CPU: 2 PID: 513 Comm: irq/30-iwlwifi Not tainted 4.10.0-9-generic #11-Ubuntu
Mar  8 10:11:47 lt0972 kernel: [   18.997604] Hardware name: LENOVO 3460CJG/3460CJG, BIOS G6ETB5WW (2.75 ) 09/01/2016
Mar  8 10:11:47 lt0972 kernel: [   18.997606] Call Trace:
Mar  8 10:11:47 lt0972 kernel: [   18.997613]  dump_stack+0x63/0x81
Mar  8 10:11:47 lt0972 kernel: [   18.997615]  __warn+0xcb/0xf0
Mar  8 10:11:47 lt0972 kernel: [   18.997617]  warn_slowpath_fmt+0x5f/0x80
Mar  8 10:11:47 lt0972 kernel: [   18.997623]  ? iwl_read32+0x1f/0x80 [iwlwifi]
Mar  8 10:11:47 lt0972 kernel: [   18.997630]  iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi]
Mar  8 10:11:47 lt0972 kernel: [   18.997636]  iwl_read_direct32+0x32/0x80 [iwlwifi]
Mar  8 10:11:47 lt0972 kernel: [   18.997642]  iwl_dump_fh+0x268/0x390 [iwlwifi]
Mar  8 10:11:47 lt0972 kernel: [   18.997649]  iwl_pcie_irq_handle_error+0x39/0x160 [iwlwifi]
Mar  8 10:11:47 lt0972 kernel: [   18.997656]  iwl_pcie_irq_handler+0x3ae/0xa90 [iwlwifi]
Mar  8 10:11:47 lt0972 kernel: [   18.997659]  ? irq_finalize_oneshot.part.35+0xf0/0xf0
Mar  8 10:11:47 lt0972 kernel: [   18.997661]  irq_thread_fn+0x20/0x50
Mar  8 10:11:47 lt0972 kernel: [   18.997663]  irq_thread+0x12f/0x1c0
Mar  8 10:11:47 lt0972 kernel: [   18.997667]  ? __schedule+0x23b/0x6f0
Mar  8 10:11:47 lt0972 kernel: [   18.997669]  ? irq_forced_thread_fn+0x70/0x70
Mar  8 10:11:47 lt0972 kernel: [   18.997671]  kthread+0x101/0x140
Mar  8 10:11:47 lt0972 kernel: [   18.997673]  ? irq_affinity_notify+0x130/0x130
Mar  8 10:11:47 lt0972 kernel: [   18.997676]  ? kthread_create_on_node+0x60/0x60
Mar  8 10:11:47 lt0972 kernel: [   18.9976..."
1667146,2020-03-11 10:53:33 UTC,"https://bugzilla.redhat.com/show_bug.cgi?id=1802472, and https://bugzilla.kernel.org/show_bug.cgi?id=190281"
1667151,2020-11-20 04:17:37 UTC,[Expired for mate-settings-daemon (Ubuntu) because there has been no activity for 60 days.]
1667157,2017-07-26 11:43:32 UTC,"Should also be applied to Hebrew, Urdu and Farsi (Persian)."
1667160,2017-03-27 16:24:25 UTC,We have another confirmed encounter with a an EDUP wifi adapter http://edupwireless.com/product-1-2-6-wireless-11n-usb-adapter-en/137263 . See attached panic output generated during boot.
1667160,2017-03-28 09:12:59 UTC,I just got the update to kernel 4.8.0-1031.35 ... will test later today.
1667160,2017-03-28 19:34:51 UTC,Still no worky with kernel 4.8.0-1031.
1667160,2017-03-30 23:44:45 UTC,Same problem with 4.8.0-1032.
1667160,2017-04-07 17:41:42 UTC,Problem still exists with 4.8.0-1033.37.
1667160,2017-04-30 17:48:43 UTC,"Having similar issues (kernel panic, not being able to connect to wireless networks both from network manager and nmtui) with RTL8188CUS wifi adapter on Ubuntu Mate 16.04 and now on 17.04."
1667160,2017-04-26 23:18:16 UTC,4.8.0-1035 seems to fix the problem. (Didn't check -1034.) Thank you!
1667160,2017-04-27 14:52:34 UTC,"For the record: I upgraded to zesty and with kernel 4.10.0-1004 everything works fine, too."
1667160,2017-03-23 21:17:18 UTC,Looks like the same issue as reported in https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1669802
1667160,2017-06-14 09:25:00 UTC,I'm unable to reproduce this bug:
1667160,2017-04-11 13:29:31 UTC,"Did anybody check the current kernel from zesty? I'm thinking about upgrading, but don't want to render the thing unbootable because there's no working kernel left."
1667160,2017-03-23 03:39:42 UTC,"I encounter a similar panic w/ a pi2, kernel 4.4.0-1046-raspi2, and an edimax wifi adapter (ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] using module rtl8192cu).  See attached panic output."
1667160,2017-04-06 11:47:41 UTC,A workaround seems to be using https://github.com/dz0ny/rt8192cu instead of the rtlwifi driver.
1667160,2017-02-23 10:37:01 UTC,NOTE: The apport I sent was created with the WORKING 1024 kernel. IT IS NOT from the here mentioned -1025 or -1026 kernel as there I can barely login until the kernel panics.
1667160,2017-02-23 10:35:44 UTC,apport information
1667160,2017-02-23 10:35:38 UTC,apport information
1667160,2017-02-23 10:35:35 UTC,apport information
1667160,2017-02-23 10:35:33 UTC,apport information
1667160,2017-02-23 10:35:30 UTC,apport information
1667160,2017-03-09 22:38:56 UTC,Tested today with the -1028 kernel. The problem IS STILL THERE.
1667160,2017-02-23 10:35:28 UTC,apport information
1667160,2017-02-23 10:35:26 UTC,apport information
1667160,2017-02-23 10:35:24 UTC,apport information
1667160,2017-02-23 10:35:19 UTC,apport information
1667160,2017-02-23 00:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1667169,2017-02-23 00:48:07 UTC,Shutter hangs after deleting snapped image from file browser
1667169,2017-02-24 11:33:14 UTC,Can you provide some terminal output (only the lines which appear during deleting the image)? I cannot reproduce this problem on 0.93.1.
1667170,2017-02-23 01:00:26 UTC,This was fixed with in heat 6.1.0 and later release
1667170,2017-02-23 03:15:44 UTC,"I think we fixed this bug already:
https://bugs.launchpad.net/heat/+bug/1569273"
1667187,2017-06-01 05:49:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667206,2017-02-24 14:56:03 UTC,"Further testing confirms that this occurs on CentOS 5, 32-bits. Googling the error message suggests that this is an intermittent bug in an old OpenSSL version there. Thus the easiest way to proceed seems to skip this test for that particular platform."
1667206,2017-04-10 13:06:28 UTC,"CentOS 5 is EOL, closing without fixing."
1667206,2018-01-25 09:29:02 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3650
1667220,2017-02-23 17:38:06 UTC,Power related kernel patches for the Kernel Team to consider.
1667220,2017-03-01 17:12:33 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-February/082719.html
1667220,2017-03-01 17:13:10 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-February/082724.html
1667220,2017-07-26 15:57:23 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1667222,2017-03-14 10:41:53 UTC,"I can't reproduce this on 16.04 because I can't find the combobox from 1.4.  I wonder if this is an OEM specific feature?
Screenshot attached showing what I see."
1667222,2017-03-15 01:28:23 UTC,"@willcooke, can you confirm if you did step 1.2 to unlock ?"
1667222,2017-03-15 09:28:39 UTC,"Yup, you're right.  I could swear I was unlocking it."
1667231,2017-03-02 14:12:48 UTC,It's trying to execute the 'conntrack' binary. Do you have it on your system?
1667231,2017-03-03 02:20:24 UTC,Appreciated.
1667241,2017-09-04 22:05:23 UTC,Could you please check if the version from https://launchpad.net/~diesch/+archive/ubuntu/experimental works for you? Thank you! :-)
1667244,2018-02-16 08:48:14 UTC,"I solved this problem by installing PHP5.6 parallel with PHP7:
===============================================================
sudo add-apt-repository ppa:ondrej/php
sudo apt-get update
sudo apt-get install php5.6 php5.6-mysql php5.6-pgsql php-gettext php5.6-mbstring php-mbstring php-xdebug libapache2-mod-php5.6"
1667244,2018-02-16 12:19:03 UTC,"Hi, Dariosh,"
1667258,2017-02-23 15:47:33 UTC,"Hi helix84,"
1667274,2017-02-23 10:49:50 UTC,This report refers to the Getting Started with Ubuntu 1604
1667274,2017-02-23 16:42:40 UTC,Great! Thanks for the report. We will look into this in the coming version 18.04.
1667284,2017-04-26 04:17:32 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1667284,2017-02-24 09:15:41 UTC,"testing with silo 2481, deatached tabs are not dragable with ALT drag, ALT draging other child windows works fine"
1667284,2017-02-24 01:34:47 UTC,If the child window is draggable without using Alt in Unity7 then this is a duplicate of bug 1420334.
1667284,2017-02-23 11:37:06 UTC,"looks like in u8 it's missing the ""custom?"" title bar?"
1667284,2017-02-23 11:35:51 UTC,"in unity7 the child window is dragable and i can put the window back, see attached screenshot on unity7"
1667284,2017-02-24 01:32:45 UTC,Try Alt+drag with the mouse?
1667287,2017-02-23 17:01:24 UTC,"@LucaDC: Please, don't throw around accusations without knowing what you're talking about!"
1667287,2019-02-12 12:45:33 UTC,fixed using comment 11
1667287,2017-02-23 19:01:06 UTC,"Well, you answered explicitly to my statement:"
1667287,2017-02-23 18:32:57 UTC,@Eduard: sorry but actually it's you that throw around accusations.
1667287,2017-02-23 18:32:29 UTC,"@su_v: Thanks. I was wondering why the srollbars were so wide, especially as the active area (i.e. where the scrollbar can be grabbed) is tiny.
I'll keep it in mind, but at this point I'm not even sure if using Adwaita on Windows is the right way to go or if we should switch to the native ""win32"" theme eventually. Right now Adwaita is just much more usable as ""win32"" would need some adjustments."
1667287,2017-02-23 18:27:19 UTC,As final comment I'll add wrt GTK3 themeing:
1667287,2017-02-23 18:11:17 UTC,"@Eduard Braun - for your trunk builds with more recent GTK+ 3.22, you can reduce the width of the canvas scrollbars with this snippet in %APPDATA%\inkscape\ui\style.css :"
1667287,2017-02-23 18:02:36 UTC,"feel free to mark this as Invalid if you like, now that we know there is a fix available."
1667287,2017-02-23 17:59:06 UTC,"@Alvin - the example user stylesheet was attached just to demonstrate that themeing in GTK3 is not “set in stone”, and can be modified for the runtime (overriding the compiled-in default style)."
1667287,2017-02-23 16:10:52 UTC,Minimalistic Inkscape user stylesheet to enable the steppers (arrows) of the canvas scrollbars attached.
1667287,2017-02-23 17:57:35 UTC,"@su_v - thanks very much for the tip, that is working perfectly!"
1667287,2017-02-23 15:13:08 UTC,"I agree with Alvin that this kind of decisions are disconcerting.
I also agree that this is not the right place to discuss about GTK people's decisions so I won't."
1667287,2017-02-23 14:43:32 UTC,"You're absolutely right, but in my opinion it's way too early to think about GUI details."
1667287,2017-02-23 14:15:44 UTC,"sorry, I should not try to shoot the messenger. But I find changes of this sort to be incomprehensible; however, this is not the right place to vent, so I'll stop.
Would be nice, however, if we could force the arrows to be included back in by default, just in our Inkscape build. I have never yet seen, on Windows, any piece of software that uses this kind of scrollbar with no arrows."
1667287,2017-02-23 13:31:26 UTC,Other (proprietary) platforms dropped the arrows from scrollbars earlier that GNOME/GTK+ - the redesigned scrollbars in GTK+ AFAICT date back to very early GTK+ 3.0 releases (probably 5 or more years ago).
1667287,2017-02-23 13:20:54 UTC,"> this was built from scratch using CMake.
"
1667287,2017-02-23 13:08:38 UTC,"this was built from scratch using CMake. but yes, it uses Adwaita, I think. I have a folder called Adwaita which has 5373 files in it. (53.6 MBytes) (seems a bit excessive to me)"
1667287,2017-02-23 12:37:58 UTC,"> as I suspect this is simply how Adwaita looks
"
1667287,2017-02-23 12:26:23 UTC,"That's the MSYS2 build, right?"
1667287,2017-02-23 15:54:20 UTC,">> evaluating if we can use MSYS2 for building Inkscape in future
[1] http://download.tuxfamily.org/inkscape/win64/
"
1667288,2019-09-26 10:16:09 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1667297,2019-07-08 22:36:20 UTC,There is no longer this race in worker/peergrouper. It must have been fixed as part of other work.
1667310,2018-03-20 23:32:07 UTC,Reading the PBR packaging code I believe the issue is with the regex at https://git.openstack.org/cgit/openstack-dev/pbr/tree/pbr/packaging.py#n145 assuming git is the only system going to be used here. Just a few lines above the -e (editable install basically setup.py develop) has a more generous regex and could possibly operate as a workaround until the non -e url regex is fixed.
1667313,2017-02-23 14:22:13 UTC,"This also makes me wonder if maybe sector size should be configurable through the gadget.yaml, since in theory the builder machine can be different than the machine we want to target in the end. But that would be super low priority I guess."
1667313,2017-02-23 14:51:20 UTC,There are a couple of places (not including the tests) where 512 is hard coded:
1667313,2017-03-22 16:08:28 UTC,"Originally I wanted to switch all the places where we hard-code the 512 bytes sector to using the values we get from pyparted (the .sectorSize() bit), but looking at the code now I guess it wouldn't make much sense. From what I see it's just doing an ioctl BLKSSZGET for the given block-device handle - and since we're calling it for an image file, it's not really that useful."
1667317,2017-03-01 21:09:36 UTC,I test bitmap2component but result is not good. At moment I prefer to used old logo.
1667317,2018-07-17 12:25:41 UTC,Ok will do.
1667317,2018-07-17 06:48:35 UTC,"Please, do not change anything to the DXF import and the S_CURVE support."
1667317,2018-06-18 22:07:14 UTC,The silent aspect of this bug report will need to wait until we are out of string freeze.
1667317,2017-03-02 13:50:38 UTC,"This is what I expected.  Saving to an older file format resolved the
issue which would indicate that the kicad dxf code failed to parse the
newer file format.  That being said, our dxf imported should not have
silently failed.  It should have displayed some kind of error message.
Please leave this bug report open so we can at least fix that part."
1667317,2017-03-02 11:32:01 UTC,"News.
I did more tests and I arrived at a solution: I exported the DXF files from AutoCAD LT2014 to the format for Autocad R12 / LT12. This format is imported from Kicad smoothly. I attach the file."
1667317,2018-07-17 14:44:16 UTC,"Many of S_CURVE implementation was already in code.
Some missing code was missing (Hit test, BBox calculation, point edition, move and rotation transforms)), but it was not a complicated code.
I also fixed bugs and optimized some calculations (in drawings)"
1667317,2017-02-27 16:49:01 UTC,"Ok. At the moment I try with bitmap2component. For import logo is possible, for import Mecanichal design this is not the maximun"
1667317,2017-02-27 16:18:30 UTC,"Use the bitmap2component too convert bitmaps to schematic or board
objects to import into your schematics and boards."
1667317,2017-02-27 14:59:55 UTC,"Excuse me, but why not implement the import of bitmap?"
1667317,2017-02-27 14:48:00 UTC,"So there is no solution?
Or you are working to solve the problem?"
1667317,2017-02-27 14:21:26 UTC,"The dxf file format has changed many times over the years resulting in
different file format versions.  DXF file format version 14 is the
latest version that KiCad supports if you DXF file is saved as a DXF
version later that 14, KiCad will not be able to import it."
1667317,2017-02-27 14:07:47 UTC,Sorry I did not understand.
1667317,2017-02-27 13:41:20 UTC,"I did mean Corel 14.  I meant DXF version 14.  That being said, I
converted your file_new.dxf to dxf version 14 and I still could not
import it so there is something amiss with the dxf importer.  Even if
there is something in your file that the dxf importer is choking on it
should still give you and error rather than just silently do nothing."
1667317,2017-02-27 09:02:23 UTC,"I no longer have the Corel version 14 !!!
I tried to save the DXF file with Autocad, but also does not work. If you can tell me in what format to save the DXF file can do the tests."
1667317,2017-02-26 17:18:29 UTC,Most likely the new dxf file is saved in a file version that kicad does not support.  I opened you new dxf file without any issues on DraftSight 2017.  Try saving your new dxf file as a version 14 dxf file using Corel.  I believe only supports dxf versions 14 and below.
1667317,2017-02-27 16:17:27 UTC,"It will be a long while before I will have any time to look at it.
Maybe someone else who is more familiar with the dxf import code can
look at it before I get a chance."
1667318,2017-03-10 15:21:15 UTC,https://github.com/snapcore/snapcraft/pull/1161
1667329,2019-07-03 01:48:48 UTC,"See https://review.opendev.org/#/c/486450/ for design details that are being hashed out. I'm in the process of proposing an initial patch for this, look for it shortly. This initial patch will demonstrate what I'm proposing in the design spec. Reviews on https://review.opendev.org/#/c/486450/ would be greatly appreciated."
1667329,2020-08-24 13:17:14 UTC,"Reviewed:  https://review.opendev.org/486450
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=3f584dc9b72fb883d82296dad7c413e51fd45b15
Submitter: Zuul
Branch:    master"
1667329,2020-08-05 10:34:34 UTC,"Reviewed:  https://review.opendev.org/741607
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=b64d4e2423da8b1664ec632a849b4d8c0892e20e
Submitter: Zuul
Branch:    master"
1667329,2020-07-17 09:08:01 UTC,"Change abandoned by Thomas Goirand (<email address hidden>) on branch: master
Review: https://review.opendev.org/741429"
1667329,2020-07-16 10:42:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/741429"
1667329,2017-04-06 23:04:11 UTC,"As discussed today in the drivers meeting, next step is a spec and a blue print (e.g. https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch)"
1667329,2019-07-05 16:45:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669395"
1667329,2019-07-02 21:57:39 UTC,Any progress or ETAs on this RFE?
1667329,2019-11-28 08:22:34 UTC,"Are there any blockers around the RFE?
I evaluated the configuration by using devstack with PoC code. It seems work well and should be a little impact for upstream code."
1667332,2017-03-10 16:03:23 UTC,"Reviewed:  https://review.openstack.org/437438
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=c69bf9e291928d9c8b8ad45c7be94c0e45df11ec
Submitter: Jenkins
Branch:    master"
1667332,2017-02-23 15:33:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437438"
1667344,2019-12-31 00:10:21 UTC,"The package was deleted on 2017-08-24 by Steve Langasek
obsoleted product, incompatible with Qt5.9; LP: #1712874"
1667356,2017-03-17 08:33:51 UTC,"Fix proposed to branch: stable/1.0
Review: https://review.openstack.org/446885"
1667356,2017-03-17 08:33:40 UTC,"Fix proposed to branch: stable/1.0
Review: https://review.openstack.org/446884"
1667356,2017-03-17 13:58:58 UTC,"Reviewed:  https://review.openstack.org/446885
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-influxdb-grafana/commit/?id=a97e97381eb2e58e13aa78554fa0c52c1a238ab6
Submitter: Jenkins
Branch:    stable/1.0"
1667356,2017-03-17 08:32:49 UTC,"Reviewed:  https://review.openstack.org/445362
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-elasticsearch-kibana/commit/?id=2ed538655f0b8386a0401b653a10f2fe364193c1
Submitter: Jenkins
Branch:    master"
1667356,2017-03-17 10:56:04 UTC,"Reviewed:  https://review.openstack.org/446884
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-elasticsearch-kibana/commit/?id=981ba273f3b583bfb284ef771932d695c0280248
Submitter: Jenkins
Branch:    stable/1.0"
1667356,2017-03-14 08:43:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445363"
1667356,2017-03-14 08:43:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445362"
1667356,2017-03-17 08:32:35 UTC,"Reviewed:  https://review.openstack.org/445363
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-influxdb-grafana/commit/?id=e0b6b025f74721add77f894b8559b2598d666b5b
Submitter: Jenkins
Branch:    master"
1667358,2017-02-23 16:53:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667358,2017-02-23 18:36:42 UTC,the latest version is   edge:    16.04 (450) 401MB devmode
1667358,2017-02-23 18:59:53 UTC,"the terminal looks ok on 450.. ok in the sense that is how it always been... it's ubuntu-terminal-app snaps running on Xmir (not sure why it doesn't native o_O ). if the terminal app is black try resizing the window, does the trick here."
1667358,2017-02-23 19:02:55 UTC,"interesting, taking a screenshot locks unity (attached is the unity8 log if anyone is interested, it's too spammy for me)"
1667358,2017-02-24 01:27:36 UTC,"The ""black or blinking"" is Xmir GLX bug 1510025."
1667358,2017-02-24 01:29:28 UTC,"Or rather, if Xmir is present in a snap then native apps should default to ignore it and use Mir instead of GLX."
1667370,2017-02-23 16:55:39 UTC,http://marc.info/?l=linux-usb&m=148786778921138&w=2
1667370,2017-02-23 17:00:14 UTC,This change was made by a bot.
1667371,2017-02-24 08:53:12 UTC,"Yes, I ran change-user-password. I didn't specify a controller."
1667371,2017-02-24 01:10:15 UTC,"@Merlijn Sebrechts,"
1667373,2017-02-23 16:39:54 UTC,"With 3 roots on 3 disks
One with ubuntu 16/10
One with xubuntu 16.10
The last with linuxmint 16.04
it apair on the last root directory
Grub Customizer is install on the 3 systems
Olivier"
1667373,2017-02-25 18:29:32 UTC,The error message says that the grubcfg_proxy is missing. This is a small part of grub customizer used to filter the original configuration when running grub-mkconfig or update-grub. Usually it is copied from /usr/lib/grub-customizer/grubcfg_proxy to /etc/grub.d/bin/grubcfg_proxy if the modifications done with grub customizer are requiring that filter (this is the case for most of the menuentry changes).
1667373,2019-07-23 20:36:48 UTC,"I'm running into this issue today. I just installed grub-customizer, the ""About"" screen shows v5.1.0."
1667373,2019-07-23 20:56:12 UTC,The error message says that /etc/grub.d/bin/grubcfg_proxy was not found. However it may be just not executable from your live environment because of incompatible executable formats (you cannot operate on a 64 bit system when using 32 bit live distro)
1667373,2019-07-25 15:42:36 UTC,"I'm doing it the other way around; the USB stick (which has a full 32-bit Debian install, not just a live distro) is what I'm trying to edit, and I'm running from my Ubuntu 64-bit install on my laptop. Would that still cause a problem?"
1667421,2017-03-03 14:19:22 UTC,Ubiquity is the desktop installer.  d-i is the alternate.
1667461,2019-05-25 04:32:17 UTC,The default text was changed.
1667482,2017-03-22 21:07:06 UTC,"Hi,"
1667489,2017-04-01 16:27:08 UTC,"Regarding neutron CLI, we won't fix this as long as the API change is discoverable."
1667489,2017-08-29 23:21:43 UTC,"What backend driver are you using?  There should have been no API changes here, so trying to track down what happened here."
1667489,2017-03-24 16:45:03 UTC,"The easiest fix is to drop redirct_url from ListL7Policy.list_columns.
Is it okay with LBaaS/Octavia team?"
1667489,2017-03-24 16:36:50 UTC,"In neutron CLI side, we already release neutron-lbaas with the reported behavior, so it looks better to fix it.
Neutron CLI is deprecated now but it is a bug worth fixed."
1667489,2017-04-01 16:26:13 UTC,"According to the bug report, this happens only for master (pike) and does not happen for ocata. This means neutron-lbaas and octavia changed the behavior. It looks like API change. How can users detect the API change? Is this an intended change of octavia?"
1667489,2017-03-01 15:51:23 UTC,workaround: provide the columns to be displayed to avoid  redirect_url attribute being checked.
1667489,2017-02-23 21:57:09 UTC," 98             if not hasattr(item, field_name) and isinstance(item, dict):
 99                 data = item[field_name]
100             else:
101                 data = getattr(item, field_name, '')
102             if data is None:
103                 data = ''"
1667489,2017-03-24 16:35:56 UTC,"I added octavia to the affected project.
The bug says that 'redirect_url' is not included in a response body for ""REDIRECT_TO_POOL"" action. I am not sure it is the expected behavior of neutron-lbaas and octavia. Looks better to loop octavia folks in."
1667503,2017-02-24 13:56:58 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1667503,2019-05-27 03:59:36 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016."
1667506,2017-02-24 21:30:23 UTC,Seb dixit:
1667506,2017-04-08 02:06:22 UTC,This also occasionally but not reproducibly occurs when mpg123 exits by itself.
1667514,2017-04-28 21:55:16 UTC,"No external plugins are automatically installed with python-openstackclient.  There are the following APIs supported in the box: compute, identity, image, network, object-store, volume.  All others must be individually installed for OSC to find them."
1667518,2017-11-13 06:37:08 UTC,Still broken in version 9.1.1. Having a look into the code
1667520,2017-05-10 13:18:10 UTC,"audacity (Audacity 2.1.2) hangs on 3-hour MP3-file with such messages (or maybe these messages is not connected to the hangups):
""""""
ALSA lib pcm.c:7963:(snd_pcm_recover) underrun occurred
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
ALSA lib pcm.c:7963:(snd_pcm_recover) underrun occurred
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
ALSA lib pcm.c:7963:(snd_pcm_recover) underrun occurred
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
ALSA lib pcm.c:7963:(snd_pcm_recover) underrun occurred
"""""""
1667520,2017-05-10 13:06:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667522,2018-01-28 11:51:45 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/8478"
1667522,2018-02-25 20:16:43 UTC,What I think we need for this patch is for it to be able to do the following:
1667522,2018-02-25 20:48:31 UTC,"Actually, we don't have to change anything for the ""Confirm registration"" switch. That governs the ""Pending registration"" page under ""Institutions""."
1667522,2018-05-08 02:03:23 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/8834"
1667522,2018-05-08 22:06:00 UTC,I've added patch 8834 to deal with what is mentioned in #3 from Kristina
1667522,2019-02-24 21:30:50 UTC,"Environment tested: Master
Browser tested: Chrome"
1667522,2019-02-24 22:04:49 UTC,Bug Fixed Label is now displaying correctly
1667522,2019-08-27 21:09:17 UTC,"Steven, please also write test cases for going through the individual settings checking that the functionality does what it promises."
1667522,2019-08-27 21:37:38 UTC,Comments from testing patch set 8 of https://reviews.mahara.org/#/c/8478/ and patch set 10 of https://reviews.mahara.org/#/c/8834 together as the latter one builds on top of the former one:
1667523,2018-01-31 00:43:30 UTC,I'm sorry I lost track of this. Does anyone have any suggestions on where this line ought to go? In ubuntu-helpers? X? Somewhere else?
1667523,2017-02-24 01:12:51 UTC,"Hello, thanks for the bug report. Funny, I'd noticed similar with gvim
started via pentadactyl but never noticed AppArmor DENIED messages. Go
figure.."
1667523,2017-02-25 20:57:00 UTC,"Adding the ""unix..."" line to ubuntu-helpers as you suggested fixed the search problem in Evince, thanks. What does that line do? I don't know much about AppArmor."
1667523,2018-01-30 20:20:12 UTC,"Hi Seth, I'd like to get this bug closed one way or another. Can we make a permanent update to the default AppArmor configuration files that Ubuntu provides, or is manually editing /etc/apparmor.d/abstractions/ubuntu-helpers the best fix I can expect for this problem?"
1667536,2017-03-17 17:26:29 UTC,I built another test kernel.  It can be downloaded from:
1667536,2017-02-25 00:26:02 UTC,"So I tried this kernel and it dumped me to the (initramfs) prompt, and complained about some sort of PKCS#7 error? Is this because the kernel isn't signed?  How do I proceed?"
1667536,2017-02-24 02:00:13 UTC,This change was made by a bot.
1667536,2017-02-24 18:53:22 UTC,I built a test kernel with a pick of commit a810007afe239.  The test kernel can be downloaded from:
1667552,2017-02-24 04:34:57 UTC,my.cnf
1667552,2017-03-02 20:49:21 UTC,Thank you for the report.
1667552,2017-03-02 21:16:07 UTC,Yes we did run mysql_upgrade. It completed successfully without any issue.
1667552,2017-03-15 11:45:22 UTC,"Just adding here that the backtrace is pretty similar to the upstream bug that is still not verified - https://bugs.mysql.com/bug.php?id=79243. checking the upstream bug, we'll need a repeatable test case before this can be confirmed."
1667552,2017-03-15 15:40:41 UTC,We can reproduce this issue in one of our database though we have multiple database running on 5.7 but we see this issue in only one database.
1667552,2018-01-25 09:29:04 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3652
1667566,2017-02-24 05:33:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667573,2017-10-23 20:39:45 UTC,This also has just happened on juju-gui rev 142 from latest charmstore on a juju 2.2.4.1 model on a different site.
1667579,2019-09-19 21:52:53 UTC,"As of Swift 2.22.0, we have support for py3 across all services and daemons."
1667579,2018-04-06 10:15:59 UTC,"Seems that this is an issue that only swift can solve. Hopefully this gets done well before py2 is EOL so there can be a reasonable transition period. IMO it would have to be at least a year, so swift should be making it a critical effort to support Python 3 by the end of 2018. The clock is ticking: https://pythonclock.org/"
1667579,2017-06-27 19:35:39 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1667579,2017-02-24 14:10:13 UTC,"Swift doesn't support py3, and thee will be a *lot* of work to make it do so. It's being worked on in general, but it won't be done any time soon."
1667579,2017-02-24 06:30:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437802"
1667579,2017-02-27 20:44:48 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: master
Review: https://review.openstack.org/437802
Reason: Seems like https://review.openstack.org/#/c/438135/ is the way forward, and it's not pressing neutron gate anymore since it's non-voting."
1667582,2017-12-23 00:29:11 UTC,Machine Dell XPS13 MLK (9360) Ububtu 16.04 4.4.0-104-generic
1667582,2017-12-23 00:38:49 UTC,Ububtu 16.04 4.4.0-105-generic all fixed now for me.
1667585,2017-02-24 07:30:47 UTC,"Yes, sorry."
1667585,2017-02-24 07:14:05 UTC,If not a bug in the app then that's likely to be a bug in the Mir code path for GTK.
1667585,2017-02-24 07:16:17 UTC,"@daniel i think it's a qt app, dolphin is the file manager for KDE"
1667588,2018-10-16 10:33:28 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/437826
Reason: Cleaning up changes that seem to be abandoned or are older than two months. If you think this was an error and the change is still relevant, please be free to restore it. Sorry for any inconvenience that I might have caused by this."
1667588,2017-07-25 21:56:55 UTC,See:
1667588,2017-11-04 23:03:33 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/437826
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1667588,2017-02-24 08:03:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437826"
1667593,2017-12-11 14:34:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667593,2017-12-11 17:58:39 UTC,"I have the exact same problem. In addition, for me the display also turns black when I open or switch to Thunderbird. Have you found a way to fix the problem or which workaround do you use?"
1667593,2017-12-11 18:00:55 UTC,"Another data point: The issue persists with the newest HWE kernel (4.10) and also if ""low graphics mode"" is enabled in CCSM."
1667593,2017-12-12 08:48:08 UTC,"@Jendrik,"
1667594,2017-02-24 08:12:49 UTC,Reported upstream. https://bugzilla.gnome.org/show_bug.cgi?id=779162
1667594,2017-02-26 09:08:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667594,2017-03-22 09:17:46 UTC,Still reproducible woth 3.24.
1667598,2019-04-28 20:54:29 UTC,"check_bug_free changed, please undo"
1667602,2017-04-10 19:10:06 UTC,"I don't think security should be a big concern here. Operators shouldn't, and in my experience won't, use Juju client on a machine they don't trust completely."
1667602,2017-04-10 14:34:10 UTC,"what would the expected behavior be if you were on a new machine and ran 'juju' there with a different public key. I certainly don't expect to be able to ""ssh remote-host"" to any machine where I haven't registered my local key, and for people concerned about security that would be more surprising than comforting."
1667602,2017-02-24 16:06:53 UTC,This bit us in python-libjuju.
1667605,2017-02-24 12:32:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1667605,2017-02-24 13:21:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667609,2017-02-24 09:24:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667611,2017-02-24 14:15:30 UTC,"I believe this is related to several snapd bugs on content interface handling which are currently being worked. See lp:11645731 for example.
There are workarounds in that bug. You can also disable, enable the app snap, connect again and it generally works."
1667613,2020-08-08 10:03:52 UTC,Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays?
1667613,2020-10-08 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1667626,2017-03-07 12:41:05 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442438"
1667626,2017-03-08 12:21:16 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1667626,2017-02-24 11:04:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437873"
1667626,2017-03-02 09:39:45 UTC,"Reviewed:  https://review.openstack.org/437873
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=4d111c2190a108c7f9532d6452ee23cb74a76379
Submitter: Jenkins
Branch:    master"
1667626,2017-03-07 16:16:17 UTC,"Reviewed:  https://review.openstack.org/442438
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=5c4cac506225ce94d24727f229b78daaf25aeb1e
Submitter: Jenkins
Branch:    stable/ocata"
1667647,2017-03-07 18:59:48 UTC,"@hubert, please try to attach the board in the launchpad bug tracker webinterface instead. I don't see the attachment."
1667647,2019-10-30 22:13:32 UTC,Marking as incomplete as the example PCB file was never uploaded to the bug tracker.
1667647,2017-03-06 13:28:02 UTC,"please find an example Project as an attachment.
I hope this will help you to clarify the Problem talking about."
1667647,2017-03-05 23:31:19 UTC,Can you create a simple dummy project to demonstrate the problem?
1667647,2017-02-24 11:41:28 UTC,Platform: W7
1667647,2017-02-24 11:26:30 UTC,The used version is: r7722.d3cb23b7d
1667655,2017-02-24 12:11:55 UTC,FWIW there's nothing preventing the user at the keyboard from going Ctrl+Alt+F1 and pressing Ctrl+Alt+Del or the power button...
1667655,2017-02-27 15:06:02 UTC,i actually thot this was a feature
1667658,2017-02-24 12:13:22 UTC,"StacktraceTop:
 QWindow::show (this=0x0) at kernel/qwindow.cpp:1851
 SignOnUi::RequestPrivate::setWindow (this=this@entry=0x562069ae0f40, window=0x0) at request.cpp:139
 SignOnUi::Request::setWidget (this=<optimized out>, widget=0x562069a65d60) at request.cpp:308
 SignOnUi::DialogRequestPrivate::start (this=0x562069a057c0) at dialog-request.cpp:217
 SignOnUi::ServicePrivate::runQueue (this=this@entry=0x562069900cf0, queue=...) at service.cpp:141"
1667658,2017-02-26 08:15:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667661,2017-02-24 12:30:02 UTC,"Please attach the original SVG file which was used to make the screenshot to the bug report to allow further investigation, thank you."
1667661,2017-02-24 12:34:51 UTC,"to the best of my knowledge this behavior is deliberate. The angle that is reported in the gui is the angle that you would see if you rescaled the ellipse to be a circle. So for example if you draw a circle and set the angle at 45 degree, then it will show up as 45 degrees as expected. But if you now expand the x axis by a factor of two, the angle will no longer be 45 degrees. Instead you will see that the tangent of the angle is precisely 2 as a result of the rescaling."
1667661,2017-02-24 12:50:59 UTC,"Test case not really needed, see Alvin's explanation (this is expected behavior)."
1667661,2017-02-24 12:52:34 UTC,SVG file attached.
1667661,2017-02-24 13:05:33 UTC,Thanks for your help. This intended behavior wasn't clear to me from the documentation and hover text.
1667661,2018-03-04 20:35:50 UTC,"Philip, do you have a suggestion how to improve the hover text? (and which one?)"
1667661,2018-03-07 15:19:13 UTC,"The hover text over 'Start' and 'End' in the screenshot, i.e., when the circle tool is selected. Perhaps they could be improved by adding a sentence to say 'Angles are only correct for circular arcs and segments.'?"
1667667,2017-02-27 14:54:03 UTC,"The issue appears in also in reverse direction:
from image with 'hw_disk_bus; property  to image without properties."
1667667,2017-05-16 08:51:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/464991"
1667677,2017-02-24 13:28:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/437895"
1667677,2017-03-10 16:08:13 UTC,"Reviewed:  https://review.openstack.org/437895
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=02eca86504053f11edb98293a03dd65486dbd568
Submitter: Jenkins
Branch:    master"
1667679,2017-02-28 10:40:01 UTC,"Reviewed:  https://review.openstack.org/438620
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=40a50031f37df0f0cde53e3f3c15ffe407fbdcbd
Submitter: Jenkins
Branch:    master"
1667679,2017-03-22 14:41:52 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/448614"
1667679,2017-03-24 18:43:05 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/448614"
1667679,2017-03-26 14:10:41 UTC,"Reviewed:  https://review.openstack.org/448614
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=803da62a305a31101e5d408af26a243f43fa33ef
Submitter: Jenkins
Branch:    stable/ocata"
1667679,2017-03-27 14:54:39 UTC,"I'm also hitting this issue using kolla-ansible on stable/ocata. I'll raise a bug in that project but thought it would be worth commenting here. My question is though, is this a bug in Nova? Are Keystone endpoints with explicit versions supported?"
1667679,2017-05-11 22:27:26 UTC,"Reviewed:  https://review.openstack.org/463500
Committed: https://git.openstack.org/cgit/openstack/kolla-kubernetes/commit/?id=04c44218662e70911ee66b4ac709def924d3e764
Submitter: Jenkins
Branch:    master"
1667679,2017-05-09 09:18:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/463500"
1667679,2017-06-05 18:12:42 UTC,"Reviewed:  https://review.openstack.org/438049
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4a2009a6fa2017013102d3d43e670334ebc60d9f
Submitter: Jenkins
Branch:    master"
1667679,2017-06-05 18:31:02 UTC,I'm going to remove ocata from nova for this bug. I'm not sure why anyone would be hitting this in Ocata since this code didn't exist in Nova until Pike.
1667679,2017-04-09 10:39:48 UTC,"@mgoddard: I was facing the same issue with kolla-ansible. Manually updating the endpoints corrected the issue for me. My symptom initially was ""Unable to retrieve default quota list"" until I dug deeper and found the ""Project ID <UUID> is not a valid project"". The project in question was indeed the admin project as I as logged in as admin at the time to create a new project."
1667679,2017-02-27 16:55:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/438620"
1667679,2017-02-24 14:13:14 UTC,"Keystone v2 has been deprecated since Mitaka, I'm actually kind of confused the Tripleo Pike has not deployed keystone v3."
1667679,2017-02-24 21:43:02 UTC,"Reviewed:  https://review.openstack.org/438017
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=6777a24d19ed407a709a424def0919a672d22917
Submitter: Jenkins
Branch:    master"
1667679,2017-02-24 20:06:26 UTC,On the Nova side we'll make a log error more explicit so that it's easier to understand what is needed.
1667679,2017-02-24 17:41:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/438017"
1667679,2017-02-24 17:07:26 UTC,http://logs.openstack.org/15/359215/63/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha/3465882/logs/undercloud/var/log/httpd/keystone_wsgi_main_access.txt.gz
1667679,2017-02-24 14:50:21 UTC,"Keystone specified that a 404 means the project does not exist, not that you by policy can't see that. We need to get keystone folks engaged on this I think."
1667679,2017-02-24 14:49:26 UTC,In looking at the logs (to the best that I can)
1667679,2017-02-24 13:28:18 UTC,"This is because checking for the validity of the project_id was recently added to nova  with this patch https://github.com/openstack/nova/commit/f6fbfc7ff07b790ef052a759552c69429b3d79c7  However, it seems that it's tied to using keystone v3, while it should be using the keystoneclient's functions and attempt to be version agnostic."
1667679,2017-02-27 16:14:58 UTC,"This fix the issue in overcloud, however, undercloud still failing in tempest tests [1]"
1667679,2017-02-24 19:04:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/438049"
1667690,2017-11-03 16:30:40 UTC,Syncing task from Mir.
1667690,2017-02-24 14:47:50 UTC,"+1 I think this is unexpected behaviour, and makes a window manager's job harder"
1667690,2017-02-27 02:06:20 UTC,This bug was totally expected...
1667690,2017-02-27 02:22:57 UTC,"Perhaps the solution is simpler than that. Seems I already solved this in mir_proving_server if you look at how it clips the title string texture:
      if (text_right > inright)  // Title too long for window"
1667690,2017-03-03 09:52:28 UTC,"I forgot: The answer is glScissor(), which also exists in ES."
1667694,2017-05-03 17:11:47 UTC,"UPDATE:
tl;dr - If you select the 'viewBox' option when opening a pre-0.92 drawing then the issue of inability to adjust display units does not present itself."
1667694,2017-12-07 01:32:37 UTC,I used the 'viewbox' option all the time in 92.1 but it is no longer offered in the 92.2 conversion dialog.
1667694,2017-05-03 16:13:51 UTC,Regarding old Inkscape documents (pre 0.92) that cannot properly set display units:
1667694,2017-02-24 20:40:50 UTC,"Ponny, can you please attach an example file and also tell us which operating system you are using?"
1667694,2017-03-11 18:52:13 UTC,There are two other posts that address the same problem: #1671691 and #1671059.
1667709,2017-02-24 19:45:23 UTC,You mean you don't want kittens peeping through bits of your window? You monster! :-D
1667709,2017-03-01 10:49:28 UTC,@stephen-j-boddy you should be able to repeat this out of the box with an Ubuntu 17.04 vm.
1667709,2017-03-01 18:15:19 UTC,"Or, you know, you could test a newer version of Terminator which I already stated has a fix for all the transparency issues... like I mentioned in comment #3. That's a lot easier than me upgrading my system to a non-LTS release so I can confirm something you can do in 5 minutes. If you don't want switch to nightly, you can run a quick test without affecting the current install."
1667709,2017-03-01 18:42:59 UTC,"stephen-j-boddy yup, looks like it's fixed in latest dev."
1667709,2017-03-01 18:58:29 UTC,"Marking as Invalid as the fix was already released, and no action to be taken."
1667709,2017-03-05 10:44:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667709,2017-04-19 06:45:38 UTC,"I'm also running 17.04 and am having the same issue.
I've also done what stephen-j-boddy suggested to get the dev version and problem solved!"
1667709,2017-04-24 14:47:17 UTC,Still have this problem with latest terminator version
1667709,2017-04-26 07:39:26 UTC,"Have the same issue, all packages are current (as of today):"
1667709,2017-04-26 08:01:46 UTC,"OK, not sure why I thought setting the Ubuntu package to Invalid was a good idea. Not my call, as I don't deal with the official Ubuntu packaging myself. (There are nightly builds I produce, but they're not Ubuntu official.)"
1667709,2017-04-28 01:19:09 UTC,Same issue with terminator 1.90.
1667735,2018-04-19 10:34:27 UTC,This bug was fixed in the package cloud-init - 18.2-14-g6d48d265-0ubuntu1
1667735,2018-04-18 17:58:26 UTC,An upstream commit landed for this bug.
1667735,2017-03-02 13:07:34 UTC,"Thanks for clarifying.
Note there is also a socket client for your container service there. we'd ideally fix that too."
1667735,2018-06-20 18:06:54 UTC,"This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New"
1667735,2017-02-24 18:24:45 UTC,"""Once this is resolved, it should be possible to start a VM with cloud-init and metadata disabled, and then enable metadata some time later and have the boot process complete at that time."""
1667735,2017-03-01 23:26:25 UTC,"""That doesn't really make sense. And re-trying timing out in 10 seconds and re-trying wouldn't really change anything."""
1667742,2017-11-27 19:33:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667746,2017-02-24 17:25:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667750,2018-08-08 14:17:44 UTC,"ubuntu 18.04
kernel : 4.15.0-29-generic"
1667750,2018-08-08 14:16:42 UTC,"I have no issue with my ethernet adapter, but I see the same logs :"
1667750,2018-08-07 13:52:56 UTC,Our bug report from Launchpad:
1667750,2018-06-18 16:05:06 UTC,"Hi Mario, thanks for the pointer. Fedora stable releases are currently on 4.16.15 so that fix should be in place. I've got a TB16 at home so I can also try to reproduce this on Fedora 28 this evening."
1667750,2018-06-18 15:53:00 UTC,FYI this commit ended up landing related to this.  I would recommend to backport it.
1667750,2018-06-18 15:47:32 UTC,"I think I have the same issue with my laptop and dock (Dell TB16).
Laptop is new and installed in Fedora 28. All firmware are up-to-date."
1667750,2018-03-29 21:09:35 UTC,"Looks like this is more of a firmware issue with these docks and/or a driver issue with the 8152, so I'm throwing this back onto the queue where it was."
1667750,2017-11-14 23:00:22 UTC,"And just to illustrate my point, on 4.14.0 vanilla:"
1667750,2018-02-21 14:56:01 UTC,On 4.15.4 I see a lot of:
1667750,2018-02-20 17:49:40 UTC,"As an informative note: it was observed that adapter ""ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]"" has a similar bug, but seems the quirk (from kernel commit 9da5a1092b13), even if applied to right PCI_ID, doesn't fix the issue.
I guess this was the case from the user imperia above (comment #61)."
1667750,2018-02-16 11:05:33 UTC,It's another bug. Please refer to LP: #1729674.
1667750,2018-02-16 10:25:02 UTC,Update to my October post:
1667750,2018-02-06 15:42:53 UTC,"If this helps, this is happening in Ubuntu 17.10 with the 4.13 and 4.15 Kernels. I am using a Logitech G930"
1667750,2018-01-19 18:52:06 UTC,Applied to 4.14.14. Offload:
1667750,2018-08-20 06:25:38 UTC,https://lkml.org/lkml/2018/8/20/42 There is a patch in upstream. Turn off the checksum offloading.
1667750,2018-01-16 08:50:49 UTC,"Please try this patch:
https://lkml.org/lkml/2018/1/16/102"
1667750,2018-02-22 12:58:14 UTC,@kaihengfeng
1667750,2018-09-12 14:36:19 UTC,The issue is not unique to the integrated NIC in the dock (so the current workaround in r8152 is not sufficient). I have a r8152-based TP-LINK UE300 USB3-to-GigE dongle connected to my TB16 dock and I'm getting the same packet corruption when I don't turn off rx checksum offloading.
1667750,2020-05-13 12:25:40 UTC,Bugstill exists in 20.04
1667750,2018-09-12 15:32:46 UTC,"Indeed, I found the mention of the pass-through only applying to the USB-C like a minute after I wrote my previous comment. Sorry for the noise."
1667750,2017-11-14 22:42:02 UTC,"This is happening even on my 9560 with 4.13.9 vanilla; when running a background rsync backup job, packages downloaded in a Debian docker build frequently do not match their checksum and need multiple runs to succeed."
1667750,2020-08-10 07:54:23 UTC,"Thanks for the info (I own a WD19TB dock too) but that hardly helps with the TB16 problem. The WD19 series docks have working USB controllers, unlike TB16."
1667750,2020-08-10 02:34:02 UTC,Install via: sudo fwupdmgr install ~/Downloads/WD19FirmwareUpdateLinux_01.00.14.cab
1667750,2020-08-10 02:33:21 UTC,There is Dell TB19 firmware available that is installable via fwupdmgr on Linux: https://www.dell.com/support/home/en-bm/drivers/driversdetails?driverid=cwcf9&oscode=rhl80&productcode=dell-wd19tb-dock
1667750,2020-07-08 15:44:49 UTC,The issue was raised to ASMedia and they confirm this can only be fixed by firmware upgrade. Please push the hardware/motherboard vendor to roll out firmware update for your device.
1667750,2020-07-05 19:27:22 UTC,I've got this problem with a shiny new TB3 docking/eGPU (razer core x chroma) on 20.04. it has 3 ASM1142 controllers.
1667750,2020-06-19 17:07:23 UTC,Seeing a similar issue on a Dell XPS 9300 (2020) with Linux 5.4:
1667750,2020-06-19 16:53:24 UTC,I'm also seeing this in 20.04:
1667750,2020-06-04 14:39:35 UTC,"This seems to help for me (Dell XPS13 2-in-1 7390 , kernel 5.6.15-300.fc32.x86_64) when switching (exact chain of events undetermined) between Dell DA300 (r8152 : Tx status -71) and Dell WD19TB ThunderBolt docking adapters :"
1667750,2020-03-02 12:11:42 UTC,"The same issue still happens to me on kernel 5.5.6-201.fc31.x86_64
Hardware is a Dell XPS 13 9370 with a Lenovo Thunderbolt 3 dock. My dmesg is full of these messages:"
1667750,2020-02-12 21:31:42 UTC,"ccollart@pop-os:~$ uname -a
Linux pop-os 5.3.0-7625-generic #27~1576774560~19.10~f432cd8-Ubuntu SMP Thu Dec 19 20:35:37 UTC  x86_64 x86_64 x86_64 GNU/Linux"
1667750,2019-09-28 23:06:46 UTC,Bus 002 Device 004: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb
1667750,2019-09-28 23:05:44 UTC,same problem witn 19.04 and usb 3.1 pci and some 10 usb icy box 10 drives.
1667750,2019-03-02 13:21:55 UTC,Ref. bug # 1600126
1667750,2019-02-28 14:23:36 UTC,cc
1667750,2018-11-05 19:29:19 UTC,"Hello I am running in to a similar error using the 18.10 cuttlefish with the usb 3.1 driver.
What kernel has this code change
[  719.522273] xhci_hcd 0000:02:00.0: Looking for event-dma 0000000463f2bdf0 trb-start 00000004650cbfb0 trb-end 00000004650cbfe0 seg-start 00000004650cb000 seg-end 00000004650cbff0
[  719.522452] xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
[  719.522454] xhci_hcd 0000:02:00.0: Looking for event-dma 0000000463f2be30 trb-start 00000004650cbfb0 trb-end 00000004650cbfe0 seg-start 00000004650cb000 seg-end 00000004650cbff0
[  719.522602] xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
[  719.522604] xhci_hcd 0000:02:00.0: Looking for event-dma 0000000463f2be70 trb-start 00000004650cbfb0 trb-end 00000004650cbfe0 seg-start 00000004650cb000 seg-end 00000004650cbff0
[  719.522768] xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
[  719.522770] xhci_hcd 0000:02:00.0: Looking for event-dma 0000000463f2beb0 trb-start 00000004650cbfb0 trb-end 00000004650cbfe0 seg-start 00000004650cb000 seg-end 00000004650cbff0
[  719.522938] xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
[  719.522940] xhci_hcd 0000:02:00.0: Looking for event-dma 0000000463f2bef0 trb-start 00000004650cbfb0 trb-end 00000004650cbfe0 seg-start 00000004650cb000 seg-end 00000004650cbff0
[  719.523102] xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
[  719.523104] xhci_hcd 0000:02:00.0: Looking for event-dma 0000000463f2bf30 trb-start 00000004650cbfb0 trb-end 00000004650cbfe0 seg-start 00000004650cb000 seg-end 00000004650cbff0
tnl@tnl-NUC8i7HNK:~$ uname -a
Linux tnl-NUC8i7HNK 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1667750,2018-09-13 05:04:18 UTC,"IIRC, I tested this scenario, and I didn't observe the issue on external r8152 dongle over the ASMedia xHC host."
1667750,2018-09-12 14:38:51 UTC,"@Tomas,"
1667750,2017-10-28 21:20:56 UTC,This bugs still present in the following kernels I have tested:
1667750,2020-09-11 11:25:22 UTC,@arcadiy
1667750,2017-06-12 08:13:26 UTC,"Hi Kai-Heng,"
1667750,2017-03-24 10:32:00 UTC,"By the way, removing and reinserting the r8152 module as suggested above does not seem to prevent or work around this issue."
1667750,2017-03-24 10:14:18 UTC,"Also, I wonder if this could somehow be a thunderbolt 3 bandwidth allocation issue.
This is pure uneducated speculation though ;-)"
1667750,2017-03-24 09:54:03 UTC,Can confirm same issue on Dell Precision 5520 + TB16 running pre-installed Ubuntu 16.04 LTS.
1667750,2017-03-24 09:28:11 UTC,I'm starting to think this issue stems not from our Realtek RTL8153 Ethernet chip but rather from something upstream of it.
1667750,2017-03-23 20:19:04 UTC,"I can confirm that I have the same issue being reported here.   I have a Dell XPS13 Developer Edition (9360) with Ubuntu 16.04, TB16 Dock and an upgraded Ubuntu Mainline build kernel of 4.10.4."
1667750,2017-03-21 09:46:01 UTC,"+1, Dell Precision M5510 + Dell TB16 + Ubuntu 16.10 + 4.8.0-41-generic #44~16.04.1-Ubuntu SMP"
1667750,2017-03-16 17:50:01 UTC,"Seems related to Bug #1663975. Same problem, I'd think..."
1667750,2017-06-12 08:36:10 UTC,Sounds like another issue. Can you file another bug?
1667750,2017-03-10 11:30:28 UTC,"reloading the Realtek kernel module r8152 and restarting the network-manager also fixes the problem temporary:
sudo rmmod r8152.ko
sudo modprobe r8152.ko
sudo service network-manager restart"
1667750,2017-03-08 17:52:59 UTC,"Hey all, just +1'ing this- seeing this on ubuntu 16.10, and Fedora 25 (kernel 4.9). TB16 dock and Dell Precision 5510."
1667750,2017-03-06 18:48:47 UTC,"A bit more info, as I've gotten hold of a separate usb network card with the same chip in it (Realtek 8153).  Plugging it into the ASMedia ASM1042A USB controller found in the TB16 docking station gives the same result as reported here.  But plugging it directly into the computer (Intel Sunrise Point-H USB controller) works without problems."
1667750,2017-03-01 21:13:26 UTC,"+1, same configuration, same behavior, 16.10."
1667750,2017-02-25 18:10:35 UTC,"Here are some more bug reports that might be related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542246
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574041
https://bugzilla.redhat.com/show_bug.cgi?id=1299252
https://bugzilla.redhat.com/show_bug.cgi?id=1246953"
1667750,2017-02-24 18:48:29 UTC,Hi Joseph. Are you a robot?
1667750,2017-02-24 18:00:54 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1667750,2017-02-24 17:30:12 UTC,This change was made by a bot.
1667750,2017-03-10 11:19:48 UTC,"+1, Dell XPS15 9550 + Dell TB16 + Ubuntu 16.10."
1667750,2017-03-27 17:33:57 UTC,I've attached a trace for the 4.11 kernel.
1667750,2017-03-24 10:38:52 UTC,Higher transfer rates seem to have some impact here:
1667750,2017-03-29 21:27:45 UTC,"+1 here Precision 5510 + TB16 + 16.10 4.8.0-41
However I think this is not a r8152 bug too. When I plug in Dell USB-C Ethernet adapter into TB16 it works fine at the full speed with the same r8152 module."
1667750,2017-06-12 07:36:50 UTC,"I can confirm the patch works on the TB15 at my hand, can you guys try patched 4.11 kernel [1] on TB16?"
1667750,2017-06-09 14:36:24 UTC,"This is an issue with the host controller. The vendor (ASMedia) has submitted a patch here that fixes the issue:
http://www.spinics.net/lists/linux-usb/msg157958.html"
1667750,2017-05-31 16:17:26 UTC,"the same issue, xps9360 + ubuntu 16.04 with kernel 4.4.78 + tb16"
1667750,2017-05-18 19:45:23 UTC,"I have the same issue.  I'm using a Dell Precision 5510 with the Dell TB16 Dock.  I'm running Ubuntu 17.04 with kernel version 4.10.0-21-generic.  What I first noticed is that some SSL-enabled websites failed to load with errors like, ""SSL_ERROR_BAD_MAC_READ.""  Setting the speed of the r8152 fixes the issue."
1667750,2017-05-04 14:00:11 UTC,"Ah, cool, didn't know that, thanks!"
1667750,2017-05-04 11:03:31 UTC,"Ohh okay, thanks for this advise I will order an adapter and try it out."
1667750,2017-03-27 17:34:29 UTC,4.11.dmesg.txt
1667750,2017-05-04 10:40:07 UTC,"André,"
1667750,2017-05-04 10:58:16 UTC,"Bram,"
1667750,2017-04-19 08:43:24 UTC,"sorry, attached wrong file in last comment. here is the right one"
1667750,2017-04-19 08:39:30 UTC,"Since I upgraded to Ubuntu 17.04 (fresh install), I can confirm that this bug also affects the (now) current release and therefore kernel version 4.10.0-19-generic."
1667750,2017-04-07 05:52:17 UTC,"I've tried:
ethtool --offload <eth interface> tx off
ethtool --offload <eth interface> rx off"
1667750,2017-04-06 23:22:21 UTC,"Could someone try:
ethtool --offload <eth interface> tx off
ethtool --offload <eth interface> rx off"
1667750,2017-04-04 20:40:05 UTC,"I have the same problem with my USB 3.1 controller:
ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller."
1667750,2017-03-30 17:02:40 UTC,I can confirm that the issue remains with the latest 4.10.7 mainline kernel build for Ubuntu.
1667750,2017-03-30 08:34:51 UTC,"@l3iggs Nothing is written on it, but it seems to be 470-ABQJ. It came with my Precision."
1667750,2017-03-30 08:06:34 UTC,"Alex, What's model number of that Dell USB-C Ethernet adapter?"
1667750,2017-05-04 09:42:29 UTC,"I need to correct me: Having issues during high load on the USB3 Ethernet adapter, too."
1667751,2019-12-17 19:39:41 UTC,"John, what do you think about Seth's question in https://bugs.launchpad.net/apparmor/+bug/1667751/comments/5?"
1667751,2017-02-24 23:59:18 UTC,That's an excellent question. In general we can't solve all cases but perhaps we can find a middle-ground.
1667751,2017-02-25 16:41:34 UTC,"Thanks Seth. A general solution covering most cases would be great as
tweaking existing profiles would involve many SRUs and inevitably, new
profiles not working inside containers would show up."
1667751,2017-02-24 22:17:01 UTC,"On 2017-02-24 04:04 PM, Seth Arnold wrote:

> I'm surprised that the denials you're seeing now
> weren't generated earlier, due to this change.
"
1667751,2017-02-24 18:18:58 UTC,It doesn't seem to only affect rsyslog as I have for example a shell script contained by an Apparmor profile and inside the container it doesn't work as it wants to read /bin/dash:
1667751,2017-02-24 21:04:32 UTC,"Thanks Simon,"
1667756,2017-03-01 22:25:01 UTC,On what version of Neutron have this behavior been seen?
1667756,2017-08-28 01:14:13 UTC,This issue was fixed in the openstack/neutron 10.0.3 release.
1667756,2017-08-28 01:12:23 UTC,This issue was fixed in the openstack/neutron 9.4.1 release.
1667756,2017-08-18 07:45:42 UTC,"Reviewed:  https://review.openstack.org/482847
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8f866dea74774801175d739dc9c2d1a7c245b18e
Submitter: Jenkins
Branch:    stable/newton"
1667756,2017-07-21 04:32:36 UTC,"Reviewed:  https://review.openstack.org/460924
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1495453768c3d37057575167d1be634cdee206d8
Submitter: Jenkins
Branch:    stable/newton"
1667756,2017-07-12 08:29:48 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/482847"
1667756,2017-06-30 13:08:31 UTC,"Reviewed:  https://review.openstack.org/464512
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a0cf9c285970cc7e419db4dda1e070cb2d23ab36
Submitter: Jenkins
Branch:    stable/ocata"
1667756,2017-06-30 13:06:57 UTC,"Reviewed:  https://review.openstack.org/460918
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4529630e2746e2ed8d3c7cf96f589b8b5236463e
Submitter: Jenkins
Branch:    stable/ocata"
1667756,2017-05-15 01:11:03 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/464512"
1667756,2017-05-12 16:23:24 UTC,"Reviewed:  https://review.openstack.org/461073
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=507cdde679613e85b54e3d86c6ae50a73e28e494
Submitter: Jenkins
Branch:    master"
1667756,2017-04-28 14:58:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/461073"
1667756,2017-03-02 14:32:11 UTC,"Hi Ann,"
1667756,2017-04-28 10:11:39 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/460918"
1667756,2017-03-02 14:32:41 UTC,"[root@overcloud-controller-2 ~]# rpm -qa | grep neut
openstack-neutron-lbaas-9.1.0-1.el7ost.noarch
openstack-neutron-ml2-9.1.0-8.el7ost.noarch
python-neutronclient-6.0.0-2.el7ost.noarch
python-neutron-lib-0.4.0-1.el7ost.noarch
openstack-neutron-bigswitch-lldp-9.40.0-1.1.el7ost.noarch
openstack-neutron-metering-agent-9.1.0-8.el7ost.noarch
puppet-neutron-9.4.2-1.el7ost.noarch
python-neutron-9.1.0-8.el7ost.noarch
python-neutron-tests-9.1.0-8.el7ost.noarch
python-neutron-lbaas-9.1.0-1.el7ost.noarch
openstack-neutron-openvswitch-9.1.0-8.el7ost.noarch
openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch
openstack-neutron-sriov-nic-agent-9.1.0-8.el7ost.noarch
openstack-neutron-common-9.1.0-8.el7ost.noarch
openstack-neutron-9.1.0-8.el7ost.noarch"
1667756,2017-03-02 14:33:20 UTC,"Hi here is a packet capture of an occurrence..
This packet capture is in the netns of the qrouter...."
1667756,2017-03-02 14:33:46 UTC,"My apologies, I copied the wrong controller window...."
1667756,2017-03-02 14:34:13 UTC,Here is the accept_ra setting on the back controllers...
1667756,2017-04-28 10:26:52 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/460924"
1667756,2017-03-07 14:23:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442518"
1667756,2017-03-30 19:16:02 UTC,"Reviewed:  https://review.openstack.org/442518
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=676a3ebe2f5b62f0ce7a3f7f434526931d5504a5
Submitter: Jenkins
Branch:    master"
1667756,2017-04-14 09:16:47 UTC,This issue was fixed in the openstack/neutron 11.0.0.0b1 development milestone.
1667756,2017-03-07 10:29:37 UTC,This bug is related to this other one [0].
1667764,2017-02-27 19:28:24 UTC,This work will help a lot with lp bug #1655608
1667773,2017-02-24 19:24:58 UTC,"This crash has the same stack trace characteristics as bug #1415309. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package."
1667773,2017-02-24 20:12:29 UTC,"Please install one of the following packages and verify if the bug still appears:
xfonts-100dpi or xfonts-75dpi or xfonts-100dpi-transcoded or xfonts-75dpi-transcoded"
1667773,2017-02-24 20:31:49 UTC,"Sorry, I installed those font packages and I still get the Segfault."
1667773,2017-02-24 20:48:00 UTC,"Debian provides a patch for this in their nedit 5.6a-5 package called ""improve_no_X_font_handling.patch""."
1667773,2017-02-25 00:29:02 UTC,"The attachment ""Patch from Debian nedit 5.6a-5 package"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1667779,2017-02-24 19:41:46 UTC,"StacktraceTop:
 __libc_message (do_abort=2, fmt=fmt@entry=0x7f2c379dd3a8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=0x7f2c37c10b00 <main_arena>, ptr=0x563c399d2b80, str=0x7f2c379d9f1e ""corrupted double-linked list"", action=<optimized out>) at malloc.c:5046
 _int_free (av=0x7f2c37c10b00 <main_arena>, p=0x563c399d2b80, have_lock=0) at malloc.c:4040
 __GI___libc_free (mem=<optimized out>) at malloc.c:2982
 ?? ()"
1667789,2017-12-15 10:54:59 UTC,"Reviewed:  https://review.openstack.org/528065
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_tacker/commit/?id=edc9c555b3df43a6fc85e932ebc07bdd71fe4388
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 00:15:38 UTC,"Change abandoned by Jimmy McCrory (<email address hidden>) on branch: master
Review: https://review.openstack.org/441721
Reason: superseded by https://review.openstack.org/#/c/527827/"
1667789,2017-12-15 00:15:06 UTC,"Change abandoned by Jimmy McCrory (<email address hidden>) on branch: master
Review: https://review.openstack.org/440925
Reason: superseded by https://review.openstack.org/#/c/527829/"
1667789,2017-12-14 20:47:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528079"
1667789,2017-12-14 19:52:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528068"
1667789,2017-12-14 19:16:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528044"
1667789,2017-12-14 19:37:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528062"
1667789,2017-12-14 19:32:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528057"
1667789,2017-12-14 19:28:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528051"
1667789,2017-12-14 19:22:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528047"
1667789,2017-12-15 10:59:21 UTC,"Reviewed:  https://review.openstack.org/528018
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=d9b49661282f89f33158d34299f89db3a0b3bfb6
Submitter: Zuul
Branch:    master"
1667789,2017-12-14 19:43:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528065"
1667789,2017-12-15 11:03:22 UTC,"Reviewed:  https://review.openstack.org/528068
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_aodh/commit/?id=9f8713e5c0214a32d0f21ba089f7d27d078a50b7
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 11:19:44 UTC,"Reviewed:  https://review.openstack.org/528031
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_horizon/commit/?id=b775123f54f3839965f9801d295330582265dd3f
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 11:12:23 UTC,"Reviewed:  https://review.openstack.org/528007
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_neutron/commit/?id=7dce3277b04a1bacb015c7885bdb8db24f4d766f
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 11:16:06 UTC,"Reviewed:  https://review.openstack.org/527827
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_glance/commit/?id=e5ac2f07e3ad01e56d4d9756629746dbae9702c1
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 11:17:57 UTC,"Reviewed:  https://review.openstack.org/527814
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_barbican/commit/?id=5141c182095338e5e655e7558355ef53d61e4fb2
Submitter: Zuul
Branch:    master"
1667789,2017-12-14 19:06:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528041"
1667789,2017-12-15 11:21:28 UTC,"Reviewed:  https://review.openstack.org/527798
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=7a466a85cb79f04a1c6f11526a1bf66f10192165
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 11:28:52 UTC,"Reviewed:  https://review.openstack.org/528044
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_ironic/commit/?id=3ecdde11291c8dcada164b53abb20fa253829cad
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 11:31:24 UTC,"Reviewed:  https://review.openstack.org/528047
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_magnum/commit/?id=e2c5cc2cee53000b9e7de911cd2c9be975e4bae3
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 13:53:39 UTC,"Reviewed:  https://review.openstack.org/528057
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_sahara/commit/?id=3603257d29821f19a2e83145d3dce7607b25f74e
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 23:03:03 UTC,"Reviewed:  https://review.openstack.org/528041
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_gnocchi/commit/?id=554a6df961d29becad0d421c10695bc967a276e1
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 23:11:38 UTC,"Reviewed:  https://review.openstack.org/528040
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_designate/commit/?id=270a8f8d73ab453f115d20a3643c4d8b3e52fefe
Submitter: Zuul
Branch:    master"
1667789,2017-12-17 01:20:15 UTC,"Reviewed:  https://review.openstack.org/528062
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_octavia/commit/?id=8cc05a3d00291aafc6a9d3fd4f430f2bf78c0c14
Submitter: Zuul
Branch:    master"
1667789,2017-12-17 01:27:48 UTC,"Reviewed:  https://review.openstack.org/528001
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=70c663391be81446d458b4a9f2dc509b27e72777
Submitter: Zuul
Branch:    master"
1667789,2017-12-19 10:45:13 UTC,"Reviewed:  https://review.openstack.org/527829
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_cinder/commit/?id=198acc08aa2924892dbee9adf5c949a6f940c016
Submitter: Zuul
Branch:    master"
1667789,2017-12-15 11:10:20 UTC,"Reviewed:  https://review.openstack.org/528051
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_trove/commit/?id=8be124b8c713e788a69201810ffb99a6e4162e0a
Submitter: Zuul
Branch:    master"
1667789,2017-12-14 18:55:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528040"
1667789,2017-12-14 16:08:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528001"
1667789,2017-12-14 17:38:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528018"
1667789,2017-02-24 20:36:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438068"
1667789,2017-02-24 21:56:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438095"
1667789,2017-03-04 16:23:02 UTC,"Reviewed:  https://review.openstack.org/438095
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=57e283fdfa4954d0cfd2d2ccf5ac67d83dd461f2
Submitter: Jenkins
Branch:    master"
1667789,2017-03-05 22:41:00 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441715"
1667789,2017-03-05 22:41:37 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441716"
1667789,2017-03-05 22:49:41 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441717"
1667789,2017-03-05 22:49:57 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441718"
1667789,2017-03-05 23:05:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441721"
1667789,2017-03-10 20:11:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444491"
1667789,2017-03-22 18:29:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448743"
1667789,2017-03-30 22:11:47 UTC,"Reviewed:  https://review.openstack.org/425997
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_server/commit/?id=eb5fc9c1e852866bc5e332a697bfeb86dfc44047
Submitter: Jenkins
Branch:    master"
1667789,2017-03-31 12:08:01 UTC,"Reviewed:  https://review.openstack.org/444491
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=15131c7649c41e496bd746015dcf35013eebcd04
Submitter: Jenkins
Branch:    master"
1667789,2017-12-14 18:27:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528031"
1667789,2017-03-31 15:01:00 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/452238"
1667789,2017-03-31 14:59:50 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/452237"
1667789,2017-03-31 18:19:16 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/452282"
1667789,2017-12-14 16:22:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528007"
1667789,2017-12-14 01:23:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527829"
1667789,2017-12-14 01:14:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527827"
1667789,2017-03-31 15:39:45 UTC,"Reviewed:  https://review.openstack.org/448743
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_client/commit/?id=c093c13e01826da545bf9a0259e0be441bc1b5e1
Submitter: Jenkins
Branch:    master"
1667789,2017-09-27 11:24:31 UTC,"Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/441716"
1667789,2017-12-13 22:23:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527798"
1667789,2017-09-27 10:57:29 UTC,"Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/441717
Reason: this change seems to be abandoned at this time however feel free to reopen it at any should the need arise."
1667789,2017-09-27 10:56:55 UTC,"Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/441715
Reason: this change seems to be abandoned for now. as such im closing it however feel free to repopen if we decide to pick this back up."
1667789,2017-04-06 13:22:23 UTC,"Reviewed:  https://review.openstack.org/452238
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_server/commit/?id=fffeb4bb6639ae231b899f439128565b2ad887b7
Submitter: Jenkins
Branch:    stable/newton"
1667789,2017-04-06 13:22:15 UTC,"Reviewed:  https://review.openstack.org/452237
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_server/commit/?id=6389811beff38a9ab7dd7e7b126e83faf3e91c7c
Submitter: Jenkins
Branch:    stable/ocata"
1667789,2017-04-06 12:48:43 UTC,"Reviewed:  https://review.openstack.org/452282
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_client/commit/?id=d2c8ca9db71e2689a83d94889bf21a319aae617b
Submitter: Jenkins
Branch:    stable/newton"
1667789,2017-09-27 11:24:26 UTC,"Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/441718"
1667789,2017-12-14 00:03:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527814"
1667790,2020-03-30 15:30:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667790,2017-02-24 20:30:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1667790,2017-03-01 07:21:49 UTC,"Hi Brian,"
1667790,2017-03-02 07:17:36 UTC,"Hi,"
1667792,2019-10-12 15:54:04 UTC,Fixed by I3f54303779dbce705ad63d47243127dc49c87937
1667814,2017-02-28 16:23:27 UTC,"Can confirm this - the loading uses the `load_from_json` common function which takes the user argument. Writing after clearing IPs and removal uses only the filename returned from `load_from_json`, which may not match the CLI argument."
1667825,2017-02-25 00:18:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667825,2017-03-30 01:54:56 UTC,"I tried applying the patch in the version of network-manager that comes in Ubuntu 17.04 (1.4.4), and it didn't seem to work. In this version, the file nm-dns-systemd-resolved.c is in src/dns-manager instead of src/dns, but I assume it is the same.
Daniel, did it work for you?"
1667825,2017-03-30 02:18:27 UTC,"Well actually I'm lost now. The code I obtain with apt-get source network-manager is different from the one I obtain with bzr branch lp:network-manager. The latter is supposed to be the most current way of getting sources, but it doesn't have the file nm-dns-systemd-resolved.c. Any ideas?"
1667825,2017-06-15 00:27:43 UTC,The problem persists in 17.10 as of today.
1667833,2017-06-02 21:14:12 UTC,New RFC [1] definitely advises against it:
1667843,2017-02-24 23:46:22 UTC,Here's the Stacktrace:
1667847,2017-02-25 01:42:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438132"
1667847,2017-08-30 18:05:58 UTC,"Change abandoned by Eric Harney (<email address hidden>) on branch: master
Review: https://review.openstack.org/438132
Reason: In merge conflict since March."
1667853,2017-03-06 23:38:25 UTC,"The text item that appears next to the graphs changed a couple of days ago, and is now ""Load"" instead of ""Disk."
1667853,2017-03-08 10:32:18 UTC,"you can use the scroll wheel when hovering above the indicator to change the text, the user interface for this feature sucks :-("
1667853,2017-03-09 00:45:21 UTC,Many thanks for pointing that out @mh21. I had never noticed.
1667853,2017-03-09 10:15:55 UTC,"Normally that is what the empty line is good for. If you just remove everything in 'Preferences > Indicator items...', the text will go away, too."
1667853,2017-03-10 04:09:04 UTC,Thanks @mh21.
1667853,2017-03-10 04:38:59 UTC,Hooray. That worked.
1667853,2017-06-23 08:33:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667853,2017-06-23 08:43:17 UTC,"I propose that the scroll behavior that changes or removes the text to the right of the graphs (comment #3) is a bug.  I'm been trying to get rid of this ""extra text"" for a couple of days now and it took me locating this bug report to find the fix."
1667853,2017-10-02 11:58:14 UTC,"I had this problem too. It is completely impossible to self-discover the solution to this problem, due to the poor UI design."
1667865,2018-11-06 16:11:31 UTC,FYI @mvo and others that there are commercial systems in the field experiencing this issue.
1667865,2018-11-05 17:09:24 UTC,"As expected, this also happens on RPi3."
1667865,2018-01-05 00:16:20 UTC,@mvo
1667865,2018-11-14 16:57:33 UTC,This is fixed via https://github.com/snapcore/snapd/pull/6093 and is part of the 2.36.1 release (currently in candidate).
1667865,2017-12-15 14:42:13 UTC,@ogra
1667865,2017-08-22 09:16:46 UTC,the simplestz solution would be to make the unpacking happen in /var/tmp instead of /tmp... /var/tmp is a writable dir on disk (turning /tmp away from tmpfs will come with a performance penalty that we should avoid)
1667865,2017-08-21 20:21:56 UTC,Confirming after discussing this is still an issue with ogra.
1667865,2017-02-27 21:15:57 UTC,"My current workaround is to unmount /tmp, create a directory in /writable, and bind-mount it to /tmp."
1667865,2018-01-02 09:15:26 UTC,@awe this is only a problem for sideloading via /tmp - store snaps are fine.
1667873,2017-09-01 16:17:08 UTC,Unassigning due to no activity for > 6 months.
1667873,2017-09-26 21:44:46 UTC,Is this still an issue? I know some of how the driver works internally has changed.
1667878,2017-05-18 20:35:20 UTC,"I don't know if it was present before or not, but there is now x-systemd.after"
1667882,2017-07-12 22:40:32 UTC,"Oh, I guess I read the output wrong, +12ms isn't bad."
1667882,2018-07-19 05:48:22 UTC,This all is still happening:
1667882,2019-09-25 22:52:45 UTC,"Multiple speedups for snapd seeding have been implemented since this was first filed, can you confirm that you still see slow snapd seeding on boot without any snaps installed on the system?"
1667882,2019-11-25 04:17:37 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1667882,2017-07-12 22:36:18 UTC,I don't even have any snaps installed but snapd appears to delay my boot by 93 seconds.
1667892,2017-08-29 20:55:18 UTC,It already existed: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600
1667892,2017-08-28 22:51:09 UTC,Andreas - could you open a bug report of apport-unpack failing to work with the .crash file you provided?  Thanks in advance.
1667892,2017-08-25 21:10:31 UTC,"I tried apport-unpack on this file, but it crashed ;)"
1667892,2017-08-24 11:08:33 UTC,"Thanks Brian for the extra stacktrace,
I found two more reports that seem to be the same to me - I dupped them here to focus efforts."
1667892,2017-06-11 05:16:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667892,2017-08-25 21:00:34 UTC,"Hmm, I'm getting crash reports, let's see what they are about:
ubuntu@zesty-apache-segfault:~$ l /var/crash/
total 2.0K
drwxrwxrwt  2 root root  2 Aug 11 01:18 .
drwxr-xr-x 14 root root 16 Aug 25 20:55 ..
ubuntu@zesty-apache-segfault:~$ sudo su -
root@zesty-apache-segfault:~# service apache2 restart
root@zesty-apache-segfault:~# l /var/crash/
total 704K
drwxrwxrwt  2 root root    4 Aug 25 20:59 .
drwxr-xr-x 14 root root   16 Aug 25 20:55 ..
-rwxr-xr-x  1 root root    0 Aug 25 20:59 .lock
-rw-r-----  1 root root 699K Aug 25 20:59 _usr_sbin_apache2.0.crash"
1667892,2017-04-11 22:14:00 UTC,"StacktraceTop:
 ?? ()
 <signal handler called>
 __do_global_dtors_aux () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/amd64/report-sandbox/lib/x86_64-linux-gnu/libnss_nis.so.2
 ?? () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/amd64/report-sandbox/lib64/ld-linux-x86-64.so.2
 __run_exit_handlers (status=0, listp=0x7ff66fb545d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83"
1667892,2017-02-25 06:24:35 UTC,"StacktraceTop:
 ?? ()
 <signal handler called>
 __do_global_dtors_aux () from /tmp/apport_sandbox_RntTSy/lib/x86_64-linux-gnu/libnss_nis.so.2
 ?? ()
 ?? ()"
1667892,2017-02-27 14:19:06 UTC,"Hi Stephan,
I was trying to reproduce today."
1667892,2017-04-11 22:21:21 UTC,"I got a better stacktrace, so I'm flipping this back to New."
1667892,2017-02-28 14:26:48 UTC,"Ok, thanks Stephan.
If you'd be ok please mark it non-private to allow others to search for it - just in case we will get more hits by others to the same issue."
1667892,2017-03-15 15:34:28 UTC,This happened just after bootup.
1667892,2017-02-28 14:08:21 UTC,Happened one time right after the install.  Your steps matched.  I tried to recreate this today.  And it was not reproducable.  I was able to recreate it before reinstalling the VM.  However my host windows install had some driver corruption that may have impacted the VM install.  This can be closed as no longer reproducable.
1667894,2017-02-25 12:29:43 UTC,"Hi Onno, thanks for filing a bug. Yes I think you're right: the documentation could be improved. I see that on Ubuntu 16.04 Remmina is installed by default."
1667894,2017-07-12 22:20:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667894,2017-07-12 22:39:32 UTC,Ubuntu 16.04 is using Vino for a server and Remmina can access it using the IP of the server and VNC protocol. I have just checked it myself.
1667901,2017-02-25 09:38:12 UTC,"...some additional information...
http://www.inkscapeforum.com/viewtopic.php?f=5&t=31883"
1667904,2017-02-25 23:55:03 UTC,*** This is an automated message ***
1667904,2020-01-25 19:59:44 UTC,"https://launchpad.net/ubuntu/+source/grub-customizer
shows that grub-customizer included in Ubuntu since disco release"
1667905,2017-02-25 09:33:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438166"
1667905,2018-06-20 05:06:12 UTC,"Change abandoned by Yan Xing an (<email address hidden>) on branch: master
Review: https://review.openstack.org/438166"
1667907,2017-02-25 13:09:19 UTC,"15 paths identified as triggers for rendering issues (black bars), each wrapped into separate sub-layer."
1667907,2017-02-25 12:11:47 UTC,"A reduced test case of a (random) path which renders with the bounding box rendered as solid black fill in 0.92.x, instead of the brownish fill area defined by the path geometry (as shown in the node tool)."
1667907,2017-02-25 12:00:52 UTC,"Note that the rendering of the test case with Inkscape 0.91 - while not showing black bars - is incorrect too (many filled areas seem to be missing or only partially rendered, and outline view mode shows missing paths (or path segments) compared to 0.92.x)."
1667907,2020-03-12 16:39:27 UTC,"The isolated paths all have an arc with rx or ry=0, so it's the same issue as https://gitlab.com/inkscape/inkscape/-/issues/692. On editing with the node tool, the arcs are replaced by cubic bezier segments which don't have that problem."
1667907,2017-02-25 11:38:10 UTC,"- confirmed on Windows 10, Inkscape 0.92.1 r15371 (32 bit)
- confirmed on Windows 10, Inkscape 0.92+devel 15536"
1667907,2017-02-25 10:10:10 UTC,Outer zoom level showing no black bars but some missing elements.
1667907,2017-02-25 10:08:41 UTC,Reference good render from Safari.
1667907,2017-02-25 11:55:22 UTC,"Based on tests with archived builds (on OS X 10.7.5):
- not reproduced with Inkscape 0.91 r13725,
- not reproduced with lp:inkscape rev <= 13638,
- reproduced with lp:inkscape rev >= 13646,
the rendering regression was likely exposed with changes in the experimental branch which was merged into trunk (after lp:inkscape/0.91.x was branched) in rev 13641:"
1667907,2017-02-25 10:04:21 UTC,Example of the black bars
1667908,2017-09-29 10:38:22 UTC,Can someone approve this in cinder as it is being changed from openstack-mannuals
1667908,2017-07-21 09:49:26 UTC,"Change abandoned by Alexandra Settle (<email address hidden>) on branch: master
Review: https://review.openstack.org/477811
Reason: Hi Pravin, this has now moved to the /cinder/ project and the content is available for update in their repo: https://github.com/openstack/cinder/tree/master/doc/source/configuration/block-storage"
1667908,2017-06-15 17:59:59 UTC,I have made the doc changes. As mentioned above you should I commit those.
1667908,2017-06-15 15:42:42 UTC,"Adding the glance liaison. Brian, could you confirm that the fix in the bug description is valid?"
1667908,2017-06-27 08:12:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477811"
1667917,2017-02-26 14:31:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667925,2019-09-16 14:06:30 UTC,Migrated to https://github.com/widelands/widelands/issues/2070
1667928,2017-02-25 13:22:28 UTC,"interesting, the menu is not in the screenshot, but it was there (on the screen), the screenshot just doesn't see the menu, probably a layer above what screenshots cares"
1667929,2017-06-26 16:25:04 UTC,"Jerome, for some reason I didn't see the message that said you posted the file."
1667929,2017-02-25 19:54:51 UTC,"As requested
/var/lib/dpkg/alternatives/pico"
1667929,2017-02-25 14:08:59 UTC,Please attach the file /var/lib/dpkg/alternatives/pico .
1667931,2017-02-27 02:08:50 UTC,Also the GTK System Settings dialog is missing icons (if you can find the dialog).
1667931,2017-02-27 02:08:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667932,2018-02-09 20:32:28 UTC,Fixed in the fork at https://github.com/subdownloader/subdownloader
1667938,2017-04-30 20:22:46 UTC,Also affects me. Will post this in case it may help troubleshooting.
1667938,2018-08-23 04:55:04 UTC,I have the same problem with version 0.17.4
1667946,2017-02-25 17:05:15 UTC,"I think that makes sense. If you're in ""private mode"", then I expect that you don't want to default to sharing data with applications, right?"
1667946,2017-02-25 17:46:38 UTC,"Agree with this, although do we need to change the wording or have some common theming that makes it clear that it's asking because you're in privacy mode?"
1667954,2017-02-28 15:29:40 UTC,"I have found the solution to this
sudo nano /etc/default/grub
and by changing the line
GRUB_CMDLINE_LINUX=""""
to
GRUB_CMDLINE_LINUX=""acpi-backlight=vendor""
then save and run
sudo update-grub"
1667958,2018-01-24 14:33:15 UTC,"Hello,"
1667963,2017-09-29 17:50:10 UTC,"Yes, no problem. But since I uploaded the profile to launchpad I made a slight modification. See attached profile."
1667963,2017-09-29 17:53:57 UTC,"Uh, sorry. This is the modification patch (see attachment)."
1667963,2017-09-29 17:15:03 UTC,Thanks for contributing this profile to help make apparmor better! Would you be willing to submit this profile as a merge request against the upstream AppArmor project at https://launchpad.net/apparmor ? New profiles should go into the profiles/apparmor/profiles/extras directory. Thanks!
1667963,2017-09-29 20:20:48 UTC,"The attachment ""usr.bin.quiterss.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1667963,2017-09-30 13:15:50 UTC,"I have removed the proposal for merging, as I want to check the profile with KDE 5 on Kubuntu 17.04. I am removing also the patch tag as suggested by the bot, because it is not a patch to anything available already in the repository."
1667964,2017-05-28 18:41:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667964,2017-06-02 11:49:32 UTC,Any progress?
1667969,2017-02-25 20:30:10 UTC,This change was made by a bot.
1667975,2017-03-07 10:08:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1667975,2017-02-27 16:26:04 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1667992,2020-11-02 19:58:35 UTC,I also noticed this behavior.
1667992,2020-11-03 19:51:35 UTC,"Is anyone still, is anyone still seeing that issue in recent Ubuntu versions? If so could you add your 'journalctl -b 0' log after seeing the issue?"
1667992,2021-01-03 04:17:27 UTC,[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.]
1667992,2017-03-24 09:35:11 UTC,"Ubuntu 16.10: gnome-session 3.20.4-0ubuntu2; Gnome on Wayland; nvidia 375.39-0ubuntu0.16.10.1. Same thing here. Logs don't seem to show anything, either. It's completely random but seems to do it early (once I've first started the computer) and then doesn't do it again the rest of the day."
1668000,2018-03-21 16:20:15 UTC,"I believe I encountered this bug yesterday will a newly-unboxed
OfficeJet 8710.  When I attached the all-in-one via USB for the first
time, it identified itself (in its USB device descriptor) as an
OfficeJet 8500 A909g. (At least, that's what `lsusb -v` said.)  At that
point, neither scanning nor printing worked over USB, but I was able to
get both to work by using Ethernet instead."
1668000,2017-05-08 12:06:10 UTC,"Just got this new printer too. I can print but scanning no way. Not sure if this is the same bug, when trying to scan I get always error prompt ""Error opening device hpaio....Invalid Argument"". I am running HPlip 3.17.4-1."
1668000,2018-11-22 13:33:22 UTC,"I think this bug can be closed. I followed all the steps including hp-setup among others and installed the missing dependencies  I also rebooted the computer a few times along the way. What I didn't do was to reboot the printer/scanner, but once I did it updated the firmware and all was well."
1668000,2017-03-05 06:33:16 UTC,"Firmware: WBP2CN1619BR
 Celita Palacios"
1668000,2017-03-02 07:28:59 UTC,"Hi,"
1668000,2017-03-05 06:34:37 UTC,Firmware: WBP2CN1619BR
1668007,2018-02-14 03:28:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668013,2017-02-26 08:37:39 UTC,"StacktraceTop:
 _xcb_conn_wait () from /tmp/apport_sandbox_Q4yo3t/usr/lib/x86_64-linux-gnu/libxcb.so.1
 _xcb_out_send () from /tmp/apport_sandbox_Q4yo3t/usr/lib/x86_64-linux-gnu/libxcb.so.1
 xcb_writev () from /tmp/apport_sandbox_Q4yo3t/usr/lib/x86_64-linux-gnu/libxcb.so.1
 _XSend (dpy=0x562be8f8ad40, data=data@entry=0x0, size=size@entry=0) at ../../src/xcb_io.c:495
 _XReply (dpy=dpy@entry=0x562be8f8ad40, rep=rep@entry=0x7ffc6bb0a1d0, extra=extra@entry=0, discard=discard@entry=1) at ../../src/xcb_io.c:581"
1668020,2017-02-27 13:26:50 UTC,Can't the footprint designer just use a calculator to get the right radius?
1668020,2017-02-27 13:50:27 UTC,"Well ... yes ... footprint designer certainly can use the calculator to calculate the right radius. In fact, this is the workaround I was talking about. But it would also be helpful to be able to specify the radius in mm."
1668020,2018-08-31 07:19:26 UTC,This doesn't really need a file format change either. Kicad outputs the current radius next to the radius ratio. If the radius field would also be editable kicad could calculate the required ratio from whatever is entered there. (would not be the perfect solution but something that can be added earlier)
1668020,2018-08-31 15:01:58 UTC,"@Rene- That make sense.  You edit one or the other but not both.  The other fields becomes driven.  We still only write the roundrect_rratio value, regardless if it is driven or driving.  I think we could do something like that for 5.1 in the dialog re-work if it's important to the librarians."
1668020,2018-09-17 23:02:06 UTC,"Fixed in revision 9cafe65e841786fce91720de9a5d212d7876b75f
https://git.launchpad.net/kicad/patch/?id=9cafe65e841786fce91720de9a5d212d7876b75f"
1668027,2017-02-26 10:14:26 UTC,This is related to bug#1593358
1668027,2017-10-23 16:34:30 UTC,Fixed for Files by lp:~jeremywootten/pantheon-files/fix-1643526-block-focus-out-during-rename
1668027,2017-02-26 10:03:16 UTC,"I'm sure this isn't a duplicate. Problem not in renaming files/directories, but in renaming bookmarks."
1668027,2017-02-26 10:10:43 UTC,Apologies - duplicate flag removed.
1668029,2017-02-26 09:58:52 UTC,The same issue is present when in CvPCB.
1668029,2017-02-26 09:59:46 UTC,It used to update the 3D viewer instantly. Both in pcbnew and cvpcb.
1668029,2017-03-07 19:07:42 UTC,When did this work?
1668029,2017-03-07 19:10:20 UTC,"On archlinux for me, it will update when I hover the mouse over the 3D viewer windows. I use the i3 window manager if."
1668029,2017-03-07 21:07:08 UTC,"Hovering doesn;t do it for me. 3d-viewer must take focus, or zooming in-out above it, even without focus."
1668029,2017-03-07 21:28:30 UTC,"Yeah, it may be more correct to say that it needs focus. Hovering over a window in i3 makes it focus."
1668029,2018-03-15 20:21:08 UTC,Works fine on Mac.  GTK-specific?
1668029,2018-03-15 20:39:52 UTC,I cannot reproduce on debian.
1668030,2017-09-21 20:19:41 UTC,"The attachment ""arp-scan_2.0-1_amd64.deb"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1668030,2017-09-21 16:24:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668030,2017-09-21 16:22:56 UTC,Hey I included the debdiff file too. Hope you guys will take a look soon. Thanks
1668030,2017-09-21 13:53:19 UTC,Hey! this can simply be fixed by pulling the source from the github project. I would recommend the ubuntu team to update the package in the ubuntu repo for anyone who downloads it from the ubuntu repo. The github repo for arp-scan is https://github.com/royhills/arp-scan. Thank you.
1668030,2017-09-21 15:10:50 UTC,Hey I created a deb file with the patch. I will soon update and comment with the debdiff too.
1668031,2017-02-26 10:31:02 UTC,This change was made by a bot.
1668031,2017-02-27 22:37:20 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1668031,2017-03-05 19:07:04 UTC,"Hello Joseph,"
1668031,2017-03-14 04:27:03 UTC,"Gerardus,"
1668031,2017-05-14 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1668031,2017-05-16 13:57:04 UTC,"Hey Kai-Heng,"
1668031,2017-05-17 05:44:26 UTC,"Can you use latest mainline list and latest linux-firmware? If this issue still happens, please attach output of `journalctl -b`."
1668033,2017-02-28 08:54:24 UTC,Good catch! This should be changed in our manual 18.04.
1668035,2018-11-16 20:12:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668041,2020-11-08 09:14:48 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1668041,2020-06-21 01:43:29 UTC,"Hi,"
1668041,2020-11-21 23:15:05 UTC,Bug still present as of commit 7fbd7e710323c8f4c (just before 5.2 release); tested with a Linux guest in system emulation and with Linux usermode.
1668042,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1668042,2017-04-24 14:07:40 UTC,This bug was fixed in the package linux - 3.13.0-117.164
1668042,2017-04-13 16:14:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1668042,2017-04-13 16:13:06 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1668042,2017-03-29 14:14:20 UTC,"Thanks,
Tested and the fix is working properly."
1668042,2017-02-26 12:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1668042,2017-03-21 15:28:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1668042,2017-02-28 09:46:38 UTC,"Thank you, the fix works as expected in Xenial."
1668042,2017-02-28 07:56:28 UTC,Could you please add this fix also to trusty?
1668042,2017-02-28 07:44:03 UTC,"Thank you, will test and update.
By the way, i sent the patch to <email address hidden>."
1668042,2017-02-27 22:58:12 UTC,I built a Xenial test kernel with a pick of commit 1533e77315220dc1d5ec3bd6d9fe32e2aa0a74c0.  The test kernel can be downloaded from:
1668042,2017-03-22 20:21:26 UTC,I backported commit 1533e77315220 to Trusty and built a test kernel.  The test kernel can be downloaded from:
1668042,2017-04-18 07:22:52 UTC,Changing tags as per comment #5 and #8
1668043,2017-02-26 13:12:10 UTC,New gradient stops can be added in the gradient tool context by double-clicking (LMB) the gradient line. This is a known interaction - it is the same to insert a new node into a path segment when using the node tool (which also supports the alternative 'Ctrl+Alt' LMB single click action to insert a new node).
1668045,2018-01-25 09:22:01 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2493
1668047,2019-09-17 10:33:25 UTC,Migrated to https://github.com/widelands/widelands/issues/3190
1668049,2017-02-27 12:40:27 UTC,"Sorry for the long message, I did reply from email and forgot to delete the old message (actually assumed that only new text would be uploaded to launchpad)."
1668049,2020-06-02 15:06:46 UTC," I have no idea.
I changed jobs and have no more access to the infrastructure where this issue showed up."
1668049,2020-06-01 16:23:21 UTC,Is this still an issue?
1668049,2017-02-27 12:27:57 UTC,"Hi,
""shutdown --halt now"" stops the container as does ""shutdown now""
If I omit the now part and just do shutdown --halt
I get:"
1668049,2017-02-26 15:49:21 UTC,I don't think systemd changed its shutdown signal as I have other 1604 based containers that stop as expected. To me it seems that systemd wants to stop a process and hangs waiting for it (whereas shutdown now does stop the system)
1668049,2017-02-27 11:34:58 UTC,"`shutdown now` executes poweroff command which in systemd signals manpage documented as:
SIGRTMIN+4 Powers off the machine, starts the poweroff.target unit. This is mostly equivalent to systemctl start poweroff.target."
1668049,2017-02-26 12:28:06 UTC,"Note, that since a while LXC is sending SIGRTMIN+3 to systemd. So unless systemd has changed it's shutdown/halt signal again LXC should send the right signal."
1668051,2017-02-27 02:55:39 UTC,Looks like the kind of problem that grabs are meant to solve. Unfortunately the Unity8/Mir architecture does not support grabs right now.
1668053,2017-04-06 19:10:04 UTC,This bug was fixed in the package unity8 - 8.15+17.04.20170404.7-0ubuntu2
1668053,2017-03-23 02:40:34 UTC,"I know, but we've been confused by thinking that's a Mir/Unity8 design document. The parts about good dialog design really describe how to build a good toolkit (qtubuntu), and how to build a good shell assuming that's the only toolkit you need to support."
1668053,2017-03-22 09:17:09 UTC,That's not what the Mir Surfaces document dictates.
1668053,2017-03-22 02:15:49 UTC,"Window types generally have nothing to do with which window buttons should be visible. Window type dictates if there is a titlebar, and if so then..."
1668053,2017-03-21 15:10:36 UTC,"Assuming that maximizing it will not exceed max size, yes."
1668053,2017-03-21 14:55:12 UTC,"No, I really mean every dialog (e.g. Open File dialog), those that are resizable should get a maximize button imho, just like under u7"
1668053,2017-03-21 14:45:24 UTC,"Sure, when this window stops being a dialog, it will get it."
1668053,2017-03-20 15:43:22 UTC,"From my perspective it is incorrect to say 'impossible to close ""Print Preview"" window' I can run kate in miral-shell, open the print-preview and close it (Alt-F4) fine."
1668053,2017-03-07 16:54:55 UTC,"We might need to change what we map a surface like that to. Maybe in Mir case it needs to be a normal window, not a dialog?"
1668053,2017-03-07 16:37:22 UTC,"Qt apps are not required to have any Close button as part of the dialog UI, even the standard builtin ones like Print Preview (http://doc.qt.io/qt-5/qprintpreviewdialog.html)."
1668053,2017-02-28 01:28:34 UTC,Incomplete for Mir. I'm not sure but we may still be lacking sufficient client API in Mir to specify what buttons to show (and to grey out)
1668053,2017-02-27 05:45:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668053,2017-02-27 02:58:17 UTC,I'm not sure but AFAIK Mir does not yet have the sufficient client API for child windows to specify whether they support close/minimize/maximize (which is independent information from the window type). It's possible we're trying to guess the right feature set right now.
1668053,2017-03-21 14:34:36 UTC,"Just realized we have the same issue with the maximize button. If the window/dialog is resizeable (and it is in this specific case), we should display that in the decoration too."
1668067,2019-10-05 12:43:35 UTC,Duplicate of https://bugs.launchpad.net/pantheon-photos/+bug/1357959
1668068,2019-07-17 12:40:09 UTC,Eventually an optimized build for Raspbian was made available in stretch. The problem is recurring in buster now https://bugs.launchpad.net/raspbian/+bug/1834970 unfortunately
1668068,2018-04-16 11:12:19 UTC,Thanks Rolf!
1668068,2017-08-06 17:43:09 UTC,I reinstalled the latest raspbian and added the kodi using apt-get one week ago and the problem is still there.
1668068,2018-04-15 01:40:15 UTC,Just wanted to say thank you for your work!
1668069,2017-02-26 15:15:21 UTC,Also discussed on http://forum.kodi.tv/showthread.php?tid=305952
1668069,2017-03-05 12:38:58 UTC,Also discussed on https://www.raspberrypi.org/forums//viewtopic.php?f=108&t=173731
1668073,2017-02-26 16:43:09 UTC,BleachBit version 0.9.1 cameo out in 2011 and is now very old. Since then there have been many bug fixes and other changes. Would you please update to a newer version from https://www.bleachbit.org/download/linux and please try again?
1668073,2017-02-27 12:26:03 UTC,"Hi Andrew. I've installed a new Bleachbit version - 1.12 via dpkg(1) utility. There was some problem with dependencies (Bleachbit depends on python:any (>= 2.7.5-5~) but there is 2.7.3-0ubuntu2.2 version installed etc.) Anyway, everything went okay - I mean that I could open and use Bleachbit. New Bleachbit was installed; I confirmed it with 'dpkg -l' command and Bleachbit menu."
1668073,2019-11-30 16:47:49 UTC,"Hi Daniel,"
1668079,2017-02-26 16:56:32 UTC,"StacktraceTop:
 XSync (dpy=0x55dfc0ad2a80, discard=discard@entry=0) at ../../src/Sync.c:44
 apply_settings (settings=<optimized out>, key=0x55dfc0ca92c6 ""numlock-state"", manager=0x7f473c004140) at msd-keyboard-manager.c:305
 g_closure_invoke () from /tmp/apport_sandbox_yVPGE_/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 signal_emit_unlocked_R () from /tmp/apport_sandbox_yVPGE_/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /tmp/apport_sandbox_yVPGE_/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1668079,2017-10-25 17:54:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668080,2018-05-09 19:48:55 UTC,apport information
1668080,2018-05-09 19:48:51 UTC,apport information
1668080,2018-05-09 19:48:49 UTC,apport information
1668080,2018-05-09 19:48:47 UTC,apport information
1668080,2018-05-09 19:48:42 UTC,apport information
1668080,2018-05-09 19:48:40 UTC,apport information
1668080,2018-05-09 19:48:38 UTC,apport information
1668080,2018-05-09 19:48:29 UTC,apport information
1668080,2018-05-09 19:48:33 UTC,apport information
1668080,2018-05-09 19:48:28 UTC,apport information
1668080,2018-05-09 19:48:25 UTC,apport information
1668080,2018-05-09 19:48:22 UTC,apport information
1668080,2018-05-09 19:48:10 UTC,apport information
1668080,2018-05-09 19:48:07 UTC,apport information
1668080,2018-05-08 18:02:58 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1668080,2018-05-09 19:48:36 UTC,apport information
1668081,2017-03-06 17:41:55 UTC,Should be fixed by https://review.openstack.org/#/c/441644/
1668081,2017-03-06 17:43:03 UTC,"Therefore it suggests some additional testing for the Alembic script change, specifically functional tests. This can be done within that change, or in a fast follow."
1668085,2017-03-16 11:23:16 UTC,"made a walkaround
https://github.com/p12tic/cppreference-doc_debian/pull/3/files
and made ppa with modified package
https://launchpad.net/~sagrer/+archive/ubuntu/cppreference-doc"
1668090,2018-09-26 06:05:30 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/432
1668090,2017-05-14 10:42:20 UTC,"I am aware that pixels are not always square. Square pixels were taken as an example to make the differences in the computed scales obvious.
As pointed out sensor data can be interpreted in various ways. I still believe that published pixel size data should be the best starting point for calculations. But I can easily live with the counterproposal as long as the results are rounded to 0,1 µm."
1668090,2017-02-27 16:10:27 UTC,"Counterproposal: Indicate pixel size calculated from Chip size (these are standardized like APS-C) and resolution, round displayed pixel size to 0.1µm. (So Pixel size is not editable.)"
1668092,2017-03-01 07:00:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668102,2017-02-27 21:16:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668102,2017-02-27 21:21:48 UTC,I experience this problem in Ubuntu 16.04 LTS.
1668105,2017-03-04 19:04:39 UTC,apport information
1668105,2017-03-04 19:04:40 UTC,apport information
1668105,2017-03-04 19:04:42 UTC,apport information
1668105,2017-03-04 19:04:43 UTC,apport information
1668105,2017-03-04 19:04:45 UTC,apport information
1668105,2017-03-04 19:04:46 UTC,apport information
1668105,2017-03-04 19:04:51 UTC,apport information
1668105,2017-03-04 19:04:56 UTC,apport information
1668105,2017-03-15 05:53:43 UTC,"Get exactly the same as described here on a Macbook Pro 12,1."
1668105,2017-03-15 06:08:14 UTC,"This seems to be the correlated upstream kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=115741"
1668105,2017-03-24 10:09:25 UTC,"A small update, the new MacBookPro12,1 has even become worse then before. (I still have the older one, which also still has the issue)."
1668105,2017-03-04 19:04:38 UTC,apport information
1668105,2017-03-24 10:10:45 UTC,"and since i can't edit, I'm running debian's 4.9.0-1 kernel at the moment, nothing special, no special options."
1668105,2017-07-21 14:04:01 UTC,"I updated to kernel 4.12 and the kernel recover usb failures on boot
( the clue was that the usb live cd booted , recovering usb failures, with ubuntu 17.04 kernel 4.10 )"
1668105,2017-08-14 23:38:09 UTC,"this xhci_hcd still bad
it keeps turning off usb and with that the console keyboard"
1668105,2017-08-15 07:50:08 UTC,"Just to confirm, I also still have issues with usb3/xhci on the macbook. Most of the time i don't notice it much. Suspend-resume fails once a week maybe due to xhci."
1668105,2017-10-18 19:21:33 UTC,"+1
Having the same problems here :-("
1668105,2017-12-15 19:26:52 UTC,"I'm also using a MacBook Pro 2015, but with Ubuntu 17.10. I'm not seeing exactly the same symptoms. Specifically, I do not get 'Assuming host is dying, halting host.'"
1668105,2018-01-04 14:32:30 UTC,"Update: I've compiled the 4.13.19 kernel without USB 3 support (in the hope that it would fall back to the USB 2 module - it doesn't - you end up with no keyboard or trackpad). If you're running a system that has a BIOS, and it allows you to turn off USB 3.0 support, that seems to be the only option. Otherwise it appears that you're stuck with intermittent USB. It sucks that MacBooks don't have ethernet... I'm using a shared wifi AP even though I have a gigabit cable on my desk :("
1668105,2018-04-25 03:45:35 UTC,"I also have a MacbookPro 11,1, and even with the latest firmware, the problem is still here, unfortunately."
1668105,2019-10-29 15:07:54 UTC,"I experiencing the same problem as comment 4,7,9, and 12.
The MacOS hardware test reports the SD card reader as not working."
1668105,2020-09-07 19:17:39 UTC,Maybe you could try some more recent kernel. I'm currently running 5.7.19 without having the timeouts.
1668105,2017-03-24 07:51:06 UTC,"Similar issue (too slow to boot, error messages with XHCI) on a Macbook pro 12,1 with openSUSE Tumbleweed (linux 4.10.1). Apple's diagnostic test indicates no hardware issue."
1668105,2017-03-04 19:04:36 UTC,apport information
1668105,2017-02-27 04:22:32 UTC,No logs are available.
1668105,2017-03-04 19:04:29 UTC,apport information
1668105,2016-04-01 11:29:19 UTC,"Created attachment 211371
Dmesg output with broken usb"
1668105,2016-04-01 11:29:52 UTC,"Created attachment 211381
lots of xhci spewing with usb debug output enabled"
1668105,2016-04-01 11:31:29 UTC,"Created attachment 211391
dmesg on 4.4.0-rc2 with broken usb output"
1668105,2016-04-01 14:52:53 UTC,"On Fri, Apr 01, 2016 at 11:29:19AM +0000, <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=115741
>
>             Bug ID: 115741
>            Summary: XHCI is slow during boot (bios/efi) and leaves many
>                     dmesg messages
"
1668105,2016-05-26 05:17:46 UTC,"Hi I have a very similar issue I use Debian with kernel 4.5 in a macbook pro 12.1
boot take a long time before show grub, but when it appear the keyboard is almost useless... you have a ""windows time"" where the keyboard respond this ""windows"" are random, they come and go, the best opportunity is press enter key before grub pops up (with this boot with default entry) this erratic behavior is present in all ""special boot options"" of the macbook pro (see https://support.apple.com/en-us/HT201255) the touch pad have the same problems. One of this special boot options (pressing ""D"") is a hardware diagnostics in this test my card reader show an error VDC001. On OSX the card reader work fine, but Debian cannot see it."
1668105,2016-05-26 08:46:15 UTC,"I have run the diagnostic mode a few times before, but never found an issue there. I'll run it again tonight and report if there is a problem. E.g. no news means diagnostic thinks everything is okay :)"
1668105,2016-06-06 15:31:39 UTC,"I ran the diagnostic mode a few times since, and as expected, no problems whatsoever."
1668105,2016-07-22 02:40:19 UTC,"I have the same problems with long wait from chime to bootmanager (refind) and then long waits between keypresses.  Occasionally after a reboot it works normally,  but never cold.  Did any of you find a solution to this?"
1668105,2017-03-04 19:04:33 UTC,apport information
1668105,2016-08-22 22:57:28 UTC,"I am experiencing the same exact behavior as comments 4 and 7.
It's a MacbookPro12,1 and it does this everytime on cold boot and on reboots from Mac OS X. It does not show this behavior when rebooting from Linux.
It seems that neither my SD card reader is working from Linux nor from Mac OS X anymore.
I am really willing to help finding the root cause of this. Should you need something to help troubleshoot, please let me know.
I am starting to wonder if this is a software issue or an hardware issue."
1668105,2017-01-17 09:28:14 UTC,"I also experience the same issue on a MacBookPro12,1 with Fedora 25 workstation (kernel 4.9.3-200)."
1668105,2016-07-26 08:11:03 UTC,"Problem persists. Meanwhile I now also have a MacBookPro12,1 and so far I don't have the issue."
1668105,2017-02-27 04:31:08 UTC,I guess what's next is that break= kernel command line parameter but it's not going to be doable when each keypress is 8 s
1668105,2017-03-04 19:04:26 UTC,apport information
1668105,2017-02-26 21:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1668105,2017-03-04 19:04:19 UTC,apport information
1668105,2017-03-04 18:38:46 UTC,The kernel 4.8 also prevents UEFI Startup Manager from booting external usb devices such as fobs or hard drives.
1668105,2017-03-04 18:35:48 UTC,Correction: Booting to Apple rescue mode is done by pressing command+R during boot
1668105,2017-03-04 19:04:21 UTC,apport information
1668105,2017-03-04 18:23:54 UTC,Causes:
1668105,2017-03-04 18:08:11 UTC,A get-around has been found allowing the system to boot:
1668105,2017-02-27 22:23:03 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1668105,2017-02-27 04:38:01 UTC,The only thing that makes Linux UEFI run usb well is a gracefully shutdown Linux installation.
1668105,2017-03-04 18:25:59 UTC,"It has also been shown in Startup Manager and bad mode, plugging in an external keyboard and waiting a minute or so enables the external keyboard functioning normally."
1668106,2017-02-26 21:35:50 UTC,"After looking around in my BIOS I found an option for either ""advanced"" or ""basic"" touch pad. If I'm on advanced, the touch pad does not work in Ubuntu, but it will if I'm in basic mode. I've install Ubuntu alongside Windows 10, and unfortunately basic mode removes all multi-touch capabilities for the touch pad in Windows (they are present in Ubuntu however). So I can only really use the touch pad in either Windows or Ubuntu, unless I change the BIOS's touch pad setting before booting to a different OS."
1668106,2017-04-01 22:14:40 UTC,"So im using an Acer Aspire as well. I wanted to upgrade from Windows 8.1 to Windows 10. Long story short, it didnt happen and I was left with no bootable drives. Figured Id download Ubuntu 14 LTS. First time around, I couldn't use my touchpad. I tried playing around with BIOS as well as playing around with the settings from the Ubuntu LTS. But, I could not for the life of me figure out why it wasnt working. Post-installation of Ubuntu 14, my computer takes about 2 hours to boot, only for the terminal to show a ton of Red errors. I try again, only this time using UEFI. The touchpad works, only problem is that Ubuntu is a pain in the ass to install using UEFI when going from Windows 8, 8.1 or Windows 10 to Ubuntu theres a ton of extra steps you have to do. The problem that I think you're looking at is the same thing I went through, try booting your computer using UEFI and then if needed you can return to Legacy BIOS."
1668106,2017-06-20 16:48:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668106,2018-02-14 13:16:59 UTC,"I reported this bug first here:
https://bugs.freedesktop.org/show_bug.cgi?id=103551"
1668116,2017-03-14 15:49:00 UTC,"^^^ It works as a workaround. Only issue is that it isn't efficient. Also, that method works for masking layer as well. It seem like one has to wait for a more efficient workaround to this, and one should be able to directly edit clipping/masking mask like one can do in photoshop. And this gives me a new idea for this, but that is for another time."
1668116,2017-03-14 15:49:33 UTC,"I mean, more efficient tool**"
1668116,2017-03-13 16:58:21 UTC,"You can do this, actually."
1668116,2017-02-27 10:35:01 UTC,"Earlier requests for layer-related clipping/masking:
* Bug #171047 “Mask layer to hide like in Macromedia Flash”
* Bug #172123 “Layer mask/clip”
* Bug #299250 “Inkscape should allow “bounded rectangle” layers”
* Bug #1083566 “feature request: more intuitive clipping/masking”"
1668116,2017-02-27 01:25:47 UTC,"Similar to this, maybe: https://inkscape.org/de/~jabiertxof/%E2%98%85eraser-layer"
1668116,2017-02-27 01:59:51 UTC,"Yes, something like that, but for this one, I only want to see it go under C/M. Also, I think I have another idea. If that can't be done, but if it can be done with the way eraser layer works, I think it would be really nice to be able to hide container layers. Furthermore, I think one should be able to click the clipping/masking icon on the object dialog, and be able to edit the clipping/masking path, but that's for another time unless it can be done right now."
1668116,2017-02-27 08:52:24 UTC,Maybe a inverse option to the effect?
1668116,2017-02-27 12:34:02 UTC,"Inverse clipping is like the erase layer tool, so that's welcomed."
1668116,2017-03-02 03:02:58 UTC,I found a existing tool to support layer clipping - http://pernsteiner.org/inkscape/layerclip/
1668123,2017-02-28 06:25:56 UTC,"It's uploading slowly to https://private-fileshare.canonical.com/~bradm/lp1668123/, once you see the .md5 file in place and the sosreport is 7.7G, it'll be done."
1668123,2017-02-27 11:05:39 UTC,Could you please attach a complete sosreport from the affected system?
1668123,2017-04-05 05:56:38 UTC,"I've had this occur on another system, and this time I could debug it a little more freely.  This is an interesting output:"
1668123,2017-03-09 18:49:17 UTC,"FYI because of other maintenance I had to do on the affected nodes,
after upgrading to linux-generic-lts-xenial 4.4.0-66-generic this
issue didn't show anymore."
1668123,2017-03-03 06:38:44 UTC,"> Sidenote) the 18GB of /var/lib/juju/db (with backups, of backups, of backups)
> was not helpful, I'll need to talk to sosreport people about that. This is
> what made the report so huge.
"
1668123,2017-06-19 05:08:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668123,2017-02-28 01:37:12 UTC,private-fileshare.c.c? or e.g. people.c.c? Or just give me ssh access into the machine?
1668123,2017-02-28 00:46:31 UTC,"I've generated a sosreport, but its 7.7G.  How would you like me to get this to you?"
1668123,2017-03-02 11:23:29 UTC,"Sidenote) the 18GB of /var/lib/juju/db (with backups, of backups, of backups) was not helpful, I'll need to talk to sosreport people about that. This is what made the report so huge."
1668124,2017-02-28 09:21:21 UTC,"Change abandoned by Nguyen Van Trung (<email address hidden>) on branch: master
Review: https://review.openstack.org/438314"
1668134,2017-03-03 15:52:53 UTC,In addition it would be good for juju-check-wait to print what parts of model are not ready when it times out
1668147,2017-11-03 16:42:52 UTC,Syncing task from Mir.
1668148,2018-06-12 19:06:34 UTC,The question allowed a user who is also a mind reader and knew what the options meant (since the actual text of the message was useless for understanding this) to switch to a bios mode install.
1668148,2018-06-20 17:28:44 UTC,I linked the wrong bug; sorry.
1668148,2018-06-13 16:00:11 UTC,Please pay attention:
1668148,2018-06-13 19:54:07 UTC,See bug #1770966 for someone complaining that they are no longer able to install Ubuntu because this question was removed ( and the automatic choice made to stick with an efi mode install instead of switching to bios mode ).
1668148,2018-06-20 17:13:31 UTC,"I spent days trying unsuccessfully to do a clean install of 18.04 onto a system with an existing version of Linux. Each time the installer would appear to be working properly, only to bomb out with an error after half an hour."
1668148,2018-07-08 21:58:23 UTC,I have this problem to and my setup is a bit different and i do not see a similar setup mentioned here.
1668148,2018-11-16 16:57:11 UTC,"Ok, Debian 9 works out-of-box - it detects Win 10 as Win Vista during install and Grub is successfully installed with working dual-boot. It took one try and about 1 hour (Nvidia install included)."
1668148,2018-07-11 10:27:44 UTC,"Re comment 23, Thank you Steve."
1668148,2018-07-27 13:16:54 UTC,"I just fall myself in this case and I think this example and my reflection can help this discussion ...
(Why do I think that you need not only a message, but also a choice box (legacy / efi) when installing ...)"
1668148,2018-08-19 08:08:00 UTC,"Same problem here with a Samsung laptop, with the 18.04.1 Kubuntu image.
A good fix should offer the choice between efi and non efi install like in 16.04, but with a text that is more clear.
Just cary on with the install in efi mode that only leads to install failure is no fix, it will just turn people away"
1668148,2018-06-12 17:11:51 UTC,"The message allowed the user to switch to a bios mode install of grub instead of trying to continue with EFI mode, which would fail, and crash the install.  Now there is no way to avoid the installation failure and it 100% crashes."
1668148,2019-05-17 20:31:28 UTC,"I believe we've addressed the crashes in installer with this bug:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1803031"
1668148,2018-07-09 19:58:38 UTC,"On Sun, Jul 08, 2018 at 09:58:23PM -0000, Chris Chambers wrote:

> I have this problem to and my setup is a bit different and i do not see
> a similar setup mentioned here.
"
1668148,2018-06-06 18:30:40 UTC,We are absolutely not reverting this.  The message was dropped because it was USELESS to an end user.
1668148,2018-11-16 15:27:24 UTC,"Same issue, built my desktop PC using Asus Deluxe Z170 motherboard in *2017* and installed Win 10 from then bought Win 10 Home DVD. My PC turned out as MBR/BIOS system. I don't know why, that was Microsoft."
1668148,2018-03-28 23:17:31 UTC,This bug was fixed in the package partman-efi - 71ubuntu2
1668148,2018-06-06 17:01:10 UTC,"No, no no.  This change is a bad release regression and must be reverted and bionic respun."
1668148,2017-03-03 18:31:53 UTC,"Your disk is currently partitioned to boot in bios mode, but you booted the installer in EFI mode. A warning message prompted you that this could be a problem and recommended performing a bios mode install instead, but you chose not to. You either need to perform the bios mode install, or partition the disk using GPT and set up an EFI system partition to install in EFI mode. This will be done for you if you choose the ""use entire disk"" guided install option."
1668148,2017-03-06 15:29:35 UTC,"I could have sworn there was already a bug about the poorly worded message, but can't find it now, so I'll reassign this one."
1668148,2017-10-05 16:12:55 UTC,Looks like the string is translated. Is that a concern?
1668148,2017-10-06 04:24:06 UTC,"If we're going to break string freeze and diverge from Debian, could we at least drop the word ""Debian"" here? s/install Debian/install/"
1668148,2017-03-04 04:33:06 UTC,"Actually, the disk was completely blank when I started. I wanted to have a btrfs partition instead of a ext4 partition, so I chose to set it up manually."
1668148,2018-02-26 18:25:08 UTC,That's not the point; the system is also warning you that proceeding with the install is potentially breaking your setup if there is a pre-existing partition.
1668148,2018-03-23 20:24:26 UTC,Here is the current message:
1668148,2018-03-23 20:37:02 UTC,"It should be understood that when fixed, this message also needs to stand alone.  The user has two choices before them, ""yes, force"" and ""no, don't force"".  The system must not assume that the user remembers anything about what was done before in the installer, or knows what will come next when picking either of those two options, except what the message tells them."
1668148,2018-03-28 13:57:42 UTC,"After experimenting with possible scenarios with the current partman-efi (2 systems on kvm - first one installed in BIOS mode, second in UEFI), I currently propose two courses of action:"
1668148,2018-03-28 16:04:15 UTC,Go for it; the confusion from this message is greater than the benefit to the very tiny set of users who might run into issues this is meant to catch.
1668148,2017-10-09 15:26:18 UTC,"I'll reject this from the queue given Steve's concern. You can talk about it out of band and accept that if appropriate, or upload a new version."
1668159,2017-11-03 16:30:44 UTC,Syncing task from Mir.
1668166,2017-02-27 17:19:10 UTC,"Hi James -- Is changing the PPA post deploy a regular part of the bootstack process, or something that you noticed as a one-off?"
1668166,2017-02-28 02:22:41 UTC,"Hi David,"
1668166,2017-02-28 10:03:43 UTC,"Is it enough if we handle upgrades only? Adding new PPAs and upgrading landscape-client we can do reasonably easily. But downgrading to a lower version is a bit tricky, so I'd like to not care about downgrading for now."
1668166,2017-03-14 10:10:53 UTC,The fix is now available in the edge channel as cs:landscape-client-29.
1668182,2017-06-19 07:24:56 UTC,"Hi,"
1668182,2018-01-25 09:29:04 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3653
1668182,2017-04-24 06:57:36 UTC,Dear support
1668182,2017-08-24 12:27:43 UTC,"Dear support, any news on this support request ?"
1668182,2017-03-02 20:39:50 UTC,Thank you for the report.
1668182,2017-03-03 08:05:40 UTC,"Dear Sveta,"
1668183,2020-12-29 22:16:44 UTC,"Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1668193,2017-02-27 09:46:26 UTC,"Hi Alan, can you check which snap package(s) you had the issue with ?"
1668193,2017-02-27 09:59:43 UTC,"ok, i see the issue now"
1668193,2017-02-27 10:49:33 UTC,I tried with a few. Including nextcloud and openhab
1668193,2017-02-28 03:18:13 UTC,This PR fixes some of the issues
1668201,2017-02-27 15:22:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/438554"
1668201,2017-03-30 13:28:45 UTC,"Reviewed:  https://review.openstack.org/438554
Committed: https://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin/commit/?id=ab32d09587923cdbeaa2c5a4137545e13e42e2a9
Submitter: Jenkins
Branch:    master"
1668224,2018-01-20 07:54:19 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1428
1668224,2017-03-24 08:37:28 UTC,"> Dynamic linking against OpenSSL is a complex topic.
"
1668224,2017-02-28 22:02:23 UTC,"Dynamic linking against OpenSSL is a complex topic.
For example Fedora says
https://fedoraproject.org/wiki/Licensing:FAQ?rd=Licensing/FAQ#What.27s_the_deal_with_the_OpenSSL_license.3F
""However, we consider that the OpenSSL library is a system library, as defined by the GPL, on Fedora and therefore we are allowed to ship GPL software that links to the OpenSSL library."""
1668224,2017-02-27 13:52:07 UTC,"""MySQL Community Edition binary distributions are compiled using yaSSL""
Source: https://dev.mysql.com/doc/refman/5.7/en/openssl-versus-yassl.html"
1668224,2017-02-27 11:01:50 UTC,Looks to be introduced by https://github.com/percona/percona-xtrabackup/commit/3766cd5eb307a9601c4803159430bd088c1da120
1668224,2017-02-27 12:06:37 UTC,Percona Server is linked with GPL as well and I believe MySQL is linked with OpenSSL too
1668225,2017-02-27 11:01:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438437"
1668225,2017-03-15 14:14:05 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445978"
1668225,2017-03-16 19:07:05 UTC,"Reviewed:  https://review.openstack.org/438437
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=b1da39ccbf1993fbbecdedaf3d5b2a3dc9855b52
Submitter: Jenkins
Branch:    master"
1668225,2017-04-05 09:14:00 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/453538"
1668225,2017-04-06 08:47:46 UTC,"Reviewed:  https://review.openstack.org/453538
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=ebf31fca19b9efab61e26ffd056d0ec6f40ff894
Submitter: Jenkins
Branch:    stable/mitaka"
1668225,2017-06-08 07:39:51 UTC,"Verified on 9.2 MU2 (UBUNTU_MIRROR_ID = 9.0-2017-05-30-154422)
root@node-1:~# pcs status resources --full"
1668225,2019-12-18 17:21:49 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/445978
Reason: This repo is retired now, no further work will get merged."
1668230,2017-02-27 22:16:39 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1668230,2017-02-27 11:31:00 UTC,This change was made by a bot.
1668230,2017-02-28 11:20:21 UTC,I tested with the latest kernel of branch 4.4 available on kernel.org which is 4.4.52.
1668239,2017-02-27 11:45:37 UTC,"$ juju --version
2.1.0-xenial-amd64"
1668239,2017-03-14 03:01:08 UTC,"When running ""-set"" hooks, we should really check unit life and not try to set versions when tearing down."
1668249,2017-02-27 12:34:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438473"
1668249,2017-03-20 15:13:18 UTC,"Reviewed:  https://review.openstack.org/438473
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=a8ac320d8f3f386ce6e29dd3207c92db9e17ddf7
Submitter: Jenkins
Branch:    master"
1668249,2017-03-20 16:14:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/447574"
1668249,2017-03-20 16:15:06 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/447575"
1668249,2017-03-23 09:45:47 UTC,"Reviewed:  https://review.openstack.org/447575
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=94b19f4edf893e07092b4291049377214b12813c
Submitter: Jenkins
Branch:    stable/newton"
1668249,2017-04-18 01:30:22 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/447574
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1668250,2017-05-31 11:20:11 UTC,Test still failing on swarm 05/31/17
1668253,2017-03-29 09:47:42 UTC,"Reviewed:  https://review.openstack.org/442320
Committed: https://git.openstack.org/cgit/openstack/python-fuelclient/commit/?id=b765ac3814eee9ef7d0d2077b6d89ccb97eb745a
Submitter: Jenkins
Branch:    master"
1668253,2017-03-07 08:50:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442320"
1668253,2017-03-27 11:41:57 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/450174"
1668253,2017-03-29 16:43:42 UTC,"Reviewed:  https://review.openstack.org/450174
Committed: https://git.openstack.org/cgit/openstack/python-fuelclient/commit/?id=85035fbd18193dd3f7c638f5d6f6d4e99fedf5ed
Submitter: Jenkins
Branch:    stable/newton"
1668253,2017-04-18 08:07:18 UTC,verified at 1575 build
1668258,2017-04-25 01:30:27 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/449145
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1668258,2017-03-28 09:19:20 UTC,"Reviewed:  https://review.openstack.org/449144
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=6aae44d79c72906227250378a20671004a1126da
Submitter: Jenkins
Branch:    stable/newton"
1668258,2017-03-23 13:25:00 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/449145"
1668258,2017-03-23 13:18:55 UTC,"Reviewed:  https://review.openstack.org/438487
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=cb8529a84ab25d7942c26766417fa7e37744c7b9
Submitter: Jenkins
Branch:    master"
1668258,2017-02-27 13:16:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438487"
1668258,2017-03-23 13:24:24 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/449144"
1668262,2017-03-02 13:11:50 UTC,"Reviewed:  https://review.openstack.org/439745
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4f237819cf20e83e738fbe5f66f9d87d8932cfd0
Submitter: Jenkins
Branch:    master"
1668262,2017-03-03 23:10:06 UTC,"Reviewed:  https://review.openstack.org/438718
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=374de0ad49986b2f80a0bf3e16d16c48c3f8f7c0
Submitter: Jenkins
Branch:    master"
1668262,2017-03-02 13:21:16 UTC,"Reviewed:  https://review.openstack.org/439741
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2f4a5f8f37286b09d74ed18f562d09b37095a448
Submitter: Jenkins
Branch:    master"
1668262,2017-03-03 23:11:18 UTC,"Reviewed:  https://review.openstack.org/439076
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e3cd8e9bdf7f5571517e87bb9d681e9a234c682c
Submitter: Jenkins
Branch:    master"
1668262,2017-03-20 01:54:50 UTC,"Reviewed:  https://review.openstack.org/439750
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e4495bfe0a4fe97c206d279cd7fb49460e1254b8
Submitter: Jenkins
Branch:    master"
1668262,2017-03-15 06:27:07 UTC,"Reviewed:  https://review.openstack.org/439738
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a5e04fbd84b96e306db3d3ed6140fa82e7441495
Submitter: Jenkins
Branch:    master"
1668262,2017-04-16 05:15:32 UTC,"Reviewed:  https://review.openstack.org/439062
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cd39505f89ccbd8ca22cfbd3f8fd6ccaffab186f
Submitter: Jenkins
Branch:    master"
1668262,2017-04-17 06:56:22 UTC,"Reviewed:  https://review.openstack.org/442354
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=67f39774546d3edddbccfa226a823a8a292f5a2d
Submitter: Jenkins
Branch:    master"
1668262,2017-03-02 06:30:11 UTC,"Reviewed:  https://review.openstack.org/438724
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e1edf6f276736db9f2f8607d63ce68a761678ddd
Submitter: Jenkins
Branch:    master"
1668262,2017-03-15 06:26:52 UTC,"Reviewed:  https://review.openstack.org/439918
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=20097d44bf686c74c3dea236b730af51162f9408
Submitter: Jenkins
Branch:    master"
1668262,2017-03-01 23:48:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439918"
1668262,2017-03-07 10:02:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442354"
1668262,2017-03-01 17:50:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439745"
1668262,2017-02-27 22:11:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438718"
1668262,2017-02-27 22:28:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438724"
1668262,2017-02-28 17:09:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439062"
1668262,2017-02-27 22:20:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438721"
1668262,2017-03-01 14:18:10 UTC,"Reviewed:  https://review.openstack.org/438721
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f448fd2229a5e6cdc92dd215b8e499e85984511f
Submitter: Jenkins
Branch:    master"
1668262,2017-03-01 17:34:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439738"
1668262,2017-03-01 17:45:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439741"
1668262,2017-02-28 17:47:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439076"
1668262,2017-03-01 18:02:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439750"
1668264,2017-02-27 13:28:33 UTC,Juju 2.1.0
1668264,2017-03-01 02:18:02 UTC,So what's the issue exactly?
1668264,2017-03-01 05:50:31 UTC,"On 1 March 2017 at 09:18, Stéphane Graber <email address hidden> wrote:

> So what's the issue exactly?
"
1668264,2017-03-01 06:03:37 UTC,Renaming the bug as this is not necessarily LXD specific. We want to expose more information to the user when trying/re-trying provisioning.
1668270,2017-04-18 03:47:31 UTC,"Thank you for your mail, getting back home to my computer to try it tonight. I'll let you know how it goes!"
1668270,2017-03-03 08:35:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668270,2017-03-03 08:43:38 UTC,"Just to confirm, this driver pacjage is continually being offered as upgrade and fails to install with the errors below on every occasion."
1668270,2017-04-17 21:40:22 UTC,"Still same in Zesty 17.04
Any workaround to stop this daily update request and failure?
Can I blacklist this upgrade?"
1668273,2017-02-27 15:42:08 UTC,"Unless I'm mis-understanding what you're saying you have an app which opens 100's of TCP conenctions in the guest, and this causes QEMU to have 100's of file descriptors open in the host."
1668273,2017-02-27 15:58:11 UTC,But lsof shows that all connections are stuck at FIN_WAIT2 for an indefinite amount of time. Is that expected?
1668273,2017-02-27 16:21:36 UTC,"IIUC, a socket staying around in FIN_WAIT2 state means that a socket has been closed in one direction, but not the other direction. Assuming SLIRP is just mirroring what the guest OS has done with the socket shutdown process, this would be expected."
1668273,2017-02-27 16:53:26 UTC,Responding to comment #1:
1668273,2020-11-12 13:15:58 UTC,"Slirp has been moved to an external project now. If this is still an issue, please report the problem there instead:
https://gitlab.freedesktop.org/slirp/libslirp"
1668274,2017-02-27 19:12:05 UTC,"Incorrect temporary rendering (wrong position, wrong scale if current zoom level ≠ 100%) of selected object after drag (move) was cancelled via canvas context menu also reproduced on Ubuntu 14.04.5 LTS with lp:inkscape/0.92.x r15394 and lp:inkscape r15551."
1668274,2017-02-27 20:30:15 UTC,Thanks su_v for get into. I give a look to the bug this weekend.
1668274,2017-02-27 16:19:55 UTC,"Unexpected temporary rendering error reproduced on OS X 10.7.5 (0.92.0, 0.92.1, 0.92.x r15394) and Windows 10 (0.92.0, 0.92.1, trunk r15551); note though that this affects various types of elements (tested with shapes (rect, ellipse), regular paths, paths with path effects (Spiro, PaP, Perspective on a group), groups)."
1668274,2017-02-27 16:08:25 UTC,AFAICT the selected object which was dragged when the move was canceled by opening the canvas context menu is temporarily rendered at the size it has at 100% zoom level - despite the canvas e.g. being zoomed out to 50% - and at the position offset relative to the page origin (bottom-left page corner) instead of the SVG origin (top-left page corner) at 100% (again ignoring current canvas zoom level).
1668278,2017-03-07 09:52:51 UTC,"We need a reproduce here, please reopen and contact me as soon as this happens again."
1668278,2017-03-20 12:09:14 UTC,"Reproduced by https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.filling_root/215/
diagnostic snapshot: https://drive.google.com/file/d/0B29AewS4dQJoUlgzQkhmVHJMZlU/view?usp=sharing"
1668284,2017-02-28 09:46:37 UTC,Do you have ways to do it in openstack env?
1668286,2017-02-28 09:51:09 UTC,I cannot imagine what the target third-party vnfm or nfvo interface looks like.
1668288,2017-02-27 15:04:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438538"
1668288,2017-03-10 16:08:45 UTC,"Reviewed:  https://review.openstack.org/438538
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=e7decc25db08a2ad1ddf8dcc6e8274a39a6b3f72
Submitter: Jenkins
Branch:    master"
1668293,2017-03-20 14:26:58 UTC,"Hello Vitaly,"
1668293,2017-03-15 13:26:31 UTC,"ps -ef | grep http
root     15806 15778  0 13:24 pts/0    00:00:00 grep --color=auto http"
1668293,2017-03-27 14:51:04 UTC,Could you please show the output of
1668293,2017-03-27 16:21:20 UTC,Sure I will update shortly with the requested.
1668293,2017-03-15 09:50:56 UTC,"Seems that for some reason you have zombie http process. Could you please issue ""ps -ef | grep http"" and send logs from /var/log/httpd"
1668293,2017-03-28 23:02:23 UTC,"So I had to rebuilt this environment, but still fail when I attempt to
run ansible-playbook
playbooks/update_fuel.yml -e '{""rebuild_bootstrap"":false}"
1668293,2017-03-28 23:04:31 UTC,I can provide access to the environment if needed.
1668293,2017-03-30 10:54:19 UTC,Could you please check apache config by running command below?
1668293,2017-03-30 20:12:34 UTC,"[root@fuel mos_mu]# /usr/sbin/apachectl configtest
[Thu Mar 30 20:12:22.052001 2017] [so:warn] [pid 24593] AH01574: module
ssl_module is already loaded, skipping
Syntax OK
[root@fuel mos_mu]#"
1668293,2017-03-28 19:59:01 UTC,Please find attached.
1668293,2017-03-14 17:19:59 UTC,"[root@fuel ~]# /usr/bin/systemctl start httpd
Job for httpd.service failed because the control process exited with error
code. See ""systemctl status httpd.service"" and ""journalctl -xe"" for details.
[root@fuel ~]#
[root@fuel ~]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor
preset: disabled)
  Drop-In: /etc/systemd/system/httpd.service.d
           └─restart.conf
   Active: activating (auto-restart) (Result: exit-code) since Tue
2017-03-14 17:19:41 UTC; 2s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 7854 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited,
status=1/FAILURE)
  Process: 7852 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
(code=exited, status=1/FAILURE)
 Main PID: 7852 (code=exited, status=1/FAILURE)"
1668293,2017-03-14 15:21:19 UTC,"Hello Anton,"
1668293,2017-03-14 15:56:21 UTC,They have been attached.
1668293,2017-03-14 15:56:00 UTC,Cobbler logs
1668293,2017-03-14 15:37:02 UTC,Ok. In that case please provide cobbler logs.
1668293,2017-03-14 16:23:42 UTC,"Something goes wrong with httpd. Could you please issue ""/usr/bin/systemctl start httpd"" on master?"
1668293,2017-03-14 14:01:04 UTC,Please provide  /var/log/puppet-error.log /var/log/puppet.log from master node.
1668293,2017-03-14 13:35:59 UTC,"Hello Anton,"
1668293,2017-03-14 13:34:37 UTC,Puppet Logs
1668293,2017-03-14 09:23:36 UTC,Could you please provide us a puppet logs from master node.
1668293,2017-03-01 14:30:44 UTC,"Hello Vitaly,"
1668296,2018-01-27 18:02:46 UTC,www.fidelityrewards.com fixed their broken DNS (now AAAA returns NOERROR instead SERVFAIL). I don't believe this bug is fixed.
1668296,2018-01-26 20:59:13 UTC,"I cannot reproduce this with the libnss-resolve in Ubuntu 17.04 or 17.10.  The original problem was reported with systemd 231; 17.04 shipped with 232.  It is possible that this has been fixed in systemd upstream (the linked upstream bug has been closed), or it's possible that the DNS configuration for www.fidelityrewards.com has changed.  I'm closing this fix-released, but if you know of another DNS name that is still broken because of this, please reopen."
1668296,2017-03-07 17:17:03 UTC,possibly upstream issue as well
1668297,2017-03-15 16:40:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668297,2017-03-15 17:43:44 UTC,We are seeing this same issue in AWS with 16.04 Xenial and 4.8.0-39-generic on g2.8xlarge instances:
1668309,2021-01-27 10:22:30 UTC,"Hi, while we wait for a fix, does anyone know how to reliably toggle between 3840x2160+gnome-scaling and 1920x1080-gnome-scaling? I've tried SSHing in a using xrandr before starting the session, but turning ON/OFF the GNOME scaling doesn't seem to work (xrandr controls DPI which is different, and i didn't find a simple gsettings to toggle that worksed). My current work around is manually changing this before I leave the computer just in case I need to VNC in, then setting it back which is not ideal..."
1668309,2021-01-23 02:37:11 UTC,I confirm the problem on my PC with 4k screen:
1668309,2020-11-12 13:45:03 UTC,"Yes, the problem seems to be that Ubuntu bundles an abandonware remote desktop package. I think the solution must be either to switch to a package that's supported, or to start maintaining vino."
1668309,2020-10-31 10:00:28 UTC,"There is no activity upstream, it looks like vino is abandonware. There is a patch made by a user on the vino issue if you want to rebuild the server yourself... But considering this is a fairly important feature in Ubuntu that is utterly broken on more and more systems as HiDPI becomes common, perhaps an ubuntu developer can help the upstream project?"
1668309,2020-06-06 08:28:09 UTC,"I can confirm this bug continues with Ubuntu 20.04, and thank you Dmitry for filing the upstream issue."
1668309,2020-01-29 13:25:10 UTC,I have filled an issue in upstream: https://gitlab.gnome.org/GNOME/vino/issues/9
1668309,2020-01-29 13:20:42 UTC,Any progress here? Affects me on 18.04 LTS.
1668309,2017-02-27 15:46:01 UTC,apport information
1668309,2019-06-09 13:15:03 UTC,"This bug also affects Screen Sharing with vino on Ubuntu 18.04 in exactly the same way as described in the original report, and renders Screen Sharing practically unusable with increasingly more common HiDPI screens."
1668309,2019-06-09 13:12:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668309,2017-02-27 15:46:03 UTC,apport information
1668309,2017-02-27 15:46:00 UTC,apport information
1668309,2019-06-27 02:30:26 UTC,Can confirm comment #5. Fails as described on a Macbook Pro with Retina display (2560x1600) in Ubuntu 18.04.
1668310,2017-02-27 20:53:18 UTC,"Reviewed:  https://review.openstack.org/438632
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2e05c82b807624b8420df4c94d68b75563b230d2
Submitter: Jenkins
Branch:    stable/mitaka"
1668310,2017-04-14 09:23:30 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1668310,2017-03-22 10:13:14 UTC,This issue was fixed in the openstack/nova 14.0.5 release.
1668310,2017-03-15 11:15:55 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1668310,2017-02-28 15:59:59 UTC,This issue was fixed in the openstack/nova 13.1.3 release.
1668310,2017-02-28 13:50:35 UTC,"Reviewed:  https://review.openstack.org/438628
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a1dd547d3ba7d9cf5b73da1ce9668e412501ace1
Submitter: Jenkins
Branch:    stable/ocata"
1668310,2017-02-27 20:52:56 UTC,"Reviewed:  https://review.openstack.org/438630
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1ad5c7305c37079ced24bf623810e63d5eac2661
Submitter: Jenkins
Branch:    stable/newton"
1668310,2017-02-27 19:12:36 UTC,"Reviewed:  https://review.openstack.org/438578
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c79770e615799cd4457ac603dcad4fb3452fe2bc
Submitter: Jenkins
Branch:    master"
1668310,2017-02-27 17:18:28 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/438632"
1668310,2017-02-27 17:13:07 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/438630"
1668310,2017-02-27 17:10:33 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/438628"
1668310,2017-02-27 16:58:16 UTC,I was able to workaround the problem like this:
1668310,2017-02-27 16:17:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438578"
1668311,2017-03-01 14:30:00 UTC,puppet manifest was adding rabbit users right at the moment when pacemaker decided to restart some rabbits. Funny thing is that adding users in puppet is a useless operation in presence of pacemaker: those created users will be lost during resets/joins performed by OCF script.
1668311,2017-03-22 10:54:29 UTC,Should be fixed by https://review.openstack.org/#/c/447420/
1668311,2017-03-22 10:55:40 UTC,I've deployed an env manually with this patch and there were no traces of spurious rabbitmq restarts
1668311,2017-03-22 10:57:21 UTC,To check whether patching had an effect you need to run the following command on any controller:
1668315,2019-09-19 11:55:58 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1668315,2017-02-27 17:26:42 UTC,Agreed.
1668315,2017-02-27 16:29:45 UTC,This is the Dev documentation. The Doc/Web team is discussing how/when to publish it (for all versions of MAAS). Note that the Doc team does not curate the Dev (and API) docs; the MAAS team is responsible for them.
1668315,2017-02-27 17:08:43 UTC,I think this should be upgraded from dev documentation to actual documentation. This is a feature of MAAS not only a development feature.
1668316,2017-11-03 16:36:35 UTC,Syncing task from Mir.
1668323,2016-11-11 12:15:42 UTC,"Created attachment 1219762
File: namespaces"
1668323,2017-07-25 23:51:04 UTC,"This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'."
1668323,2016-11-12 02:37:23 UTC,What were you doing when this crash happened?
1668323,2016-11-11 12:15:50 UTC,"Created attachment 1219766
File: exploitable"
1668323,2016-11-11 12:15:48 UTC,"Created attachment 1219765
File: var_log_messages"
1668323,2016-11-11 12:15:46 UTC,"Created attachment 1219764
File: proc_pid_status"
1668323,2016-11-11 12:15:44 UTC,"Created attachment 1219763
File: open_fds"
1668323,2016-11-11 12:15:40 UTC,"Created attachment 1219761
File: mountinfo"
1668323,2016-11-11 12:15:26 UTC,"Created attachment 1219754
File: backtrace"
1668323,2016-11-11 12:15:36 UTC,"Created attachment 1219759
File: limits"
1668323,2016-11-11 12:15:34 UTC,"Created attachment 1219758
File: environ"
1668323,2016-11-11 12:15:31 UTC,"Created attachment 1219757
File: dso_list"
1668323,2016-11-11 12:15:30 UTC,"Created attachment 1219756
File: core_backtrace"
1668323,2016-11-11 12:15:28 UTC,"Created attachment 1219755
File: cgroup"
1668323,2017-08-08 19:13:57 UTC,"Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1668323,2016-11-11 12:15:20 UTC,"Version-Release number of selected component:
xfce4-session-4.12.1-9.fc24"
1668323,2016-11-11 12:15:38 UTC,"Created attachment 1219760
File: maps"
1668329,2017-07-17 21:20:22 UTC,"The curtin error message was non-fatal but as mentioned in comment #4, curtin has fixed the utf8 handling and it's already fixed-released.  Please re-open if you believe there is a new curtin issue."
1668329,2017-04-27 14:35:10 UTC,I've retested this with 2.2.0~rc3+bzr6016-0ubuntu1~16.04.1.  There are a few things here.
1668329,2019-09-19 11:52:53 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1668329,2017-02-28 03:41:26 UTC,"Sigh. It's 2017. Any time we encode text, in the absence of knowledge to the contrary, we should assume it's UTF-8. There are far too many occurrences of ""ascii"" in the MAAS code."
1668329,2017-04-04 09:42:50 UTC,"RIGHT SINGLE QUOTATION MARK encodes to hex e2 80 99 in UTF-8 in Python
by default, so the traceback:"
1668335,2017-08-14 19:17:02 UTC,Wanted to add that this is also occurring in version 2.2.2. Currently creating a new username as a workaround.
1668335,2017-02-28 10:49:16 UTC,Generation of new secret token is on the Wishlist.
1668335,2017-02-28 10:47:49 UTC,"@Sandor Zeestraten (szeestraten),
There is an internal discussion taking place on how to proceed."
1668335,2019-12-05 06:57:24 UTC,"This should probably be marked a duplicate of this bug, though newer it has more concrete information r.e. the fix plan:
https://bugs.launchpad.net/juju/+bug/1770370"
1668335,2017-02-27 21:32:24 UTC,"Please see bug # 1630728 for more details of limitations around remove user. Currently, user disable/enable is the best way to manipulate the user."
1668335,2017-02-28 10:34:25 UTC,@anastasia-macmood Is there a followup bug for 1) on reactivating users?
1668349,2017-02-27 22:20:08 UTC,"Hey popey, are you running from ssh into a remote machine?
This sounds like bug #1664427, and they are blaming ssh in the comments there."
1668349,2017-02-28 11:38:53 UTC,"Jamie I assigned this to you while I'm on holidays, it looks like a simple profile change for snap-confine so that it can work when invoked remotely over ssh. Feel free to re-assign this with clear instructions as to how to proceed wrt security."
1668349,2017-02-28 13:00:04 UTC,No. I did this hands on to the physical machine.
1668349,2017-02-28 22:23:02 UTC,"I'm unable to reproduce this with snapd 2.22.6 (not sure where you got 2.22.7) on series 16 with kernel 4.4.0-64.85-generic. It works fine logged into a console, in unity7 in a gnome terminal (under the terminal, screen, tmux and byobu) and in ssh. Are you able to reproduce reliably? If so, can you add this to /etc/apparmor.d/usr.lib.snapd.snap-confine:"
1668349,2020-01-15 22:01:20 UTC,"I tried building and running this snap and it doesn't display anything in the terminal for me on bionic desktop through a X11 session. It just hangs without any output, but I also don't see any denials in the journal."
1668350,2021-01-14 23:32:15 UTC,When an AppImage is launched its icon appears on the Plank as a simple gear. Right clicking on the icon does not reveal an option to add it to the Plank. Nor can you drag an AppImage from the file manager onto the Plank.
1668352,2020-02-22 16:14:12 UTC,"Thanks, Mike, Dawn, and Terran.  Pushed to master, rel_3_4, and rel_3_3."
1668352,2020-02-21 15:21:10 UTC,"I have tested and consent to signoff on this with my name, Dawn Dale and my email <email address hidden>"
1668352,2020-02-21 15:29:54 UTC,"Thanks, Mike! Works like a charm. My sign off is at:"
1668352,2020-02-13 21:06:10 UTC,A branch has been pushed with this change. By default barcode is showing up and it's hyperlinked.
1668352,2020-02-11 19:15:32 UTC,Please clarify the desired fix:
1668352,2018-05-29 16:07:00 UTC,Still missing in 3.1
1668352,2017-03-01 21:09:27 UTC,Confirmed in 2.11 & 2.12
1668352,2020-02-11 21:16:24 UTC,"Now that right-clicking to retrieve patron(s) is available, this interface works better than it did when I initially reported the bug."
1668353,2017-02-27 18:14:19 UTC,Can you please share a log file that exhibits this problem?
1668353,2017-02-27 18:27:56 UTC,"I have run into this problem in the past when doing automated bare-metal testing. My ""solutions"" are:"
1668353,2017-02-27 18:36:16 UTC,"I don't have a log, sorry, slangasek asked me to file this on his behalf."
1668353,2017-02-27 20:12:14 UTC,"Please do share a log file. Our production cloud/LXC runnners all use ftpmaster.internal just like britney, there should not be any mirror lag between those."
1668353,2017-02-27 21:38:19 UTC,"On Mon, Feb 27, 2017 at 08:12:14PM -0000, Martin Pitt wrote:

> Please do share a log file. Our production cloud/LXC runnners all use
> ftpmaster.internal just like britney, there should not be any mirror lag
> between those.
"
1668353,2017-02-27 22:30:39 UTC,"On Mon, Feb 27, 2017 at 09:38:19PM -0000, Steve Langasek wrote:

> On Mon, Feb 27, 2017 at 08:12:14PM -0000, Martin Pitt wrote:
> > Please do share a log file. Our production cloud/LXC runnners all use
> > ftpmaster.internal just like britney, there should not be any mirror lag
> > between those.
>
> The point is not mirror lag, but that AIUI if there is a newer kernel in
> -proposed than the one we've booted on the instance, the tests fail due to
> the mismatch.
>
> http://autopkgtest.ubuntu.com/packages/l/linux/zesty/amd64 actually shows
> no successful test runs except the first.
"
1668353,2017-02-27 23:05:27 UTC,"On Mon, Feb 27, 2017 at 10:30:39PM -0000, Iain Lane wrote:

> I was under the impression that these are 'real' failures that need to
> be investigated. Let's take the latest one at the time of writing, which
> I suggest you download rather than opening in your browser
"
1668353,2017-02-28 08:25:50 UTC,"> The point is not mirror lag, but that AIUI if there is a newer kernel in -proposed than the one we've booted on the instance, the tests fail due to the mismatch.
"
1668353,2017-02-28 09:29:25 UTC,"> > this looks to me like the *wrong* version of Linux is being tested. Why are we testing a proposed-only version of the kernel to validate the new upload of gcc-6 in proposed?
"
1668353,2017-03-29 23:08:31 UTC,"This issue also affects autopkgtests of all kernel sources other than the generic flavor, from what I can see. E.g.:"
1668356,2017-02-27 22:06:51 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1668356,2017-12-13 14:41:12 UTC,"Hi,"
1668356,2017-02-27 22:06:38 UTC,"The lkml tread you referenced in the bug description was for commit 37b12910dd11d9ab969f2c310dc9160b7f3e3405.  That commit landed upstream in v4.3.rc1, so it is already in the 4.4 based Xenial kernel."
1668356,2017-02-28 10:10:22 UTC,"Hard to tell regarding updates, I'd say it started early january (but we did not really pay attention at first). Our players have unattended security upgrades so I'd say some kernel upgrade landing in january might have introduced a regression. As far as I know we never encountered this issue in 2016."
1668356,2017-02-27 18:10:19 UTC,"DHCPREQUEST of 10.34.242.77 on eth0 to 10.32.65.65 port 67 (xid=0x30fdf923)
BUG: unable to handle kernel NULL pointer dereference at           (null)
IP: [<ffffffff810fa7e3>] timecounter_read+0x13/0x60
PGD 0
Oops: 0000 [#1] SMP
Modules linked in: rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_multiport xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc aufs pl2303 usbserial bnep arc4 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_sst_dsp snd_hda_codec_generic nls_iso8859_1 snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel iwlmvm snd_hda_codec snd_hda_core intel_rapl 8250_dw snd_hwdep mac80211 x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm kvm_intel kvm snd_seq_midi snd_seq_midi_event irqbypass crct10dif_pclmul crc32_pclmul iwlwifi ghash_clmulni_intel snd_rawmidi aesni_intel snd_seq aes_x86_64 lrw gf128mul glue_helper cfg80211 snd_seq_device ablk_helper cryptd snd_timer snd soundcore idma64
 virt_dma shpchp ir_lirc_codec ir_xmp_decoder lirc_dev ir_mce_kbd_decoder ir_sharp_decoder intel_lpss_pci ir_sanyo_decoder btusb ir_sony_decoder hci_uart btrtl ir_jvc_decoder ir_rc6_decoder btbcm btqca ir_rc5_decoder btintel ir_nec_decoder bluetooth mei_me rc_rc6_mce ite_cir rc_core intel_lpss_acpi intel_lpss mei acpi_pad mac_hid acpi_als kfifo_buf industrialio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables parport_pc ppdev sunrpc lp parport autofs4 i915_bpo intel_ips
 i2c_algo_bit drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops ptp sdhci_pci ahci drm pps_core sdhci libahci video pinctrl_sunrisepoint i2c_hid pinctrl_intel hid fjes
CPU: 3 PID: 15471 Comm: kworker/3:0 Not tainted 4.4.0-64-generic #85-Ubuntu
Hardware name:                  /NUC6i5SYB, BIOS SYSKLi35.86A.0051.2016.0804.1114 08/04/2016
Workqueue: events e1000e_systim_overflow_work [e1000e]
task: ffff880031f32d00 ti: ffff8800350e8000 task.ti: ffff8800350e8000
RIP: 0010:[<ffffffff810fa7e3>]  [<ffffffff810fa7e3>] timecounter_read+0x13/0x60
RSP: 0018:ffff8800350ebdb0  EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffff8800353ab7a0 RCX: 0000000000000001
RDX: 0000000000000001 RSI: ffff8800350ebdf8 RDI: 0000000000000000
RBP: ffff8800350ebdb8 R08: ffff88016ed965c0 R09: 0000000000000000
R10: 000000010035ffff R11: 0000000000000001 R12: ffff8800353ab780
R13: ffff8800350ebdf8 R14: 0000000000000246 R15: ffff8800353ab6d0
FS:  0000000000000000(0000) GS:ffff88016ed80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000002e0a000 CR4: 00000000003406e0
Stack:
 ffff8800353ab7d0 ffff8800350ebde8 ffffffffc014d36e ffff8800353ab6d0
 ffff88016ed965c0 ffff88016ed9af00 00000000000000c0 ffff8800350ebe18
 ffffffffc014d521 ffffffff81837e26 ffff88016ed9af00 00000000a91221c0
Call Trace:
 [<ffffffffc01..."
1668356,2017-02-27 19:00:59 UTC,This change was made by a bot.
1668377,2018-04-03 00:11:36 UTC,octavia/load balancer link isn't showing up horizon after installing it successfully.
1668377,2020-06-02 13:42:11 UTC,The kolla-ansible certificates command is not for use in production. Please follow the Octavia docs to generate certificates.
1668377,2017-08-30 12:18:26 UTC,"kolla-ansible certficates is not meant to create ocatavia certificates, however I think is a good feature to have.
marked as wishlist if someone wants to take over the job."
1668392,2017-02-28 06:36:15 UTC,This is a omission in maxima's documentation: Gnuplot expects labels in a more TeX-like syntax.
1668405,2019-12-26 17:39:50 UTC,"Some indication of the fact it actually saved some thing, would be good.  Also a way to go back to the list of Surveys with out using the browser back button."
1668405,2020-05-27 23:29:39 UTC,These issues appear to be fixed with this work for 3.5: https://bugs.launchpad.net/evergreen/+bug/1845240
1668407,2017-02-27 23:10:16 UTC,"Bug refers to https://developer.openstack.org/api-ref/compute/?expanded=#assisted-volume-snapshots-os-assisted-volume-snapshots
And as noted it is not implemented in the tempest library"
1668407,2017-03-01 00:04:07 UTC,it will be here - https://review.openstack.org/#/c/430587/
1668407,2017-05-22 21:03:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466902"
1668407,2020-03-20 19:45:26 UTC,"Assigning to no one, as there have been no activity for a long time and Moving to Confirmed as it seems it's still valid. Btw, there are 2 reviews proposed, it might be useful to try rebase one of them."
1668407,2021-01-15 15:38:24 UTC,I've rebased https://review.opendev.org/c/openstack/tempest/+/466902
1668407,2021-02-10 14:20:26 UTC,"As it turned out in the comments of https://review.opendev.org/c/openstack/tempest/+/466902 ,the documentation mentions that the API is meant to be used by Cinder:
https://docs.openstack.org/api-ref/compute/#assisted-volume-snapshots-os-assisted-volume-snapshots"
1668409,2017-03-28 18:31:21 UTC,Is this still an issue? it just spins forever on startup here
1668409,2017-03-29 02:37:52 UTC,"or ""to not try to use X11 when it's using pure GTK""."
1668409,2017-02-28 05:29:19 UTC,Understandably we may not want to invest the time in fixing Firefox to run with pure GTK (pure Mir) right now. A quicker fix should be just to resolve Unity8 launching bug 1668429.
1668409,2017-03-29 02:36:51 UTC,"or ""try to use X11 when it's using pure GTK"" :)"
1668409,2017-02-28 04:52:38 UTC,"Oh, it seems Firefox/GTK needs fixing. It's trying to use both X11 (bug 1668429) and native Mir:"
1668409,2017-03-28 19:49:59 UTC,It's going to be an issue until Firefox gets fixed upstream to not try to use X11 when it's using Mir.
1668409,2017-02-28 03:13:24 UTC,"fwiw, this isn't a libertine app. this is a preinstalled pkg that just comes as part of the image."
1668409,2017-02-28 02:41:35 UTC,Here's a terminal command for working Firefox:
1668409,2017-02-28 02:36:52 UTC,Firefox works fine (almost - bug 1625846) when run manually. This is just a U8/Libertine launching/permissions problem.
1668409,2017-02-28 03:21:59 UTC,In that case Unity8 needs to come with Xmir already running (and accessible to apps). It's not right now.
1668409,2017-02-27 21:55:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668410,2017-09-19 14:00:02 UTC,"This bug was fixed in the package neutron - 2:8.4.0-0ubuntu5~cloud0
---------------"
1668410,2017-09-19 14:00:00 UTC,The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1668410,2017-09-18 17:47:02 UTC,"Hello Ann, or anyone else affected,"
1668410,2017-09-18 15:32:12 UTC,This bug was fixed in the package neutron - 2:8.4.0-0ubuntu5
1668410,2017-09-18 15:22:12 UTC,"The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1668410,2017-09-12 11:09:47 UTC,xenial-proposed has been verified successfully - http://paste.ubuntu.com/25520417/
1668410,2017-09-07 20:26:23 UTC,"Hello Ann, or anyone else affected,"
1668410,2017-09-01 16:52:34 UTC,"Hi Hua,"
1668410,2017-08-30 04:20:10 UTC,"The attachment ""mitaka.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1668410,2017-09-19 13:53:39 UTC,I've verified this successfully on cloud-archive:trusty-proposed with neutron 2:8.4.0-0ubuntu5~cloud0 using http://paste.ubuntu.com/25520417/ as well as verifying there are no tempest smoke test regressions.
1668410,2017-08-04 15:33:11 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1668410,2017-08-04 14:01:37 UTC,may cause dos
1668410,2017-03-04 02:09:38 UTC,"Reviewed:  https://review.openstack.org/440799
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8c77ee6b20dd38cc0246e854711cb91cffe3a069
Submitter: Jenkins
Branch:    stable/mitaka"
1668410,2017-03-02 20:38:43 UTC,Should be fixed with https://review.openstack.org/#/c/440799/
1668410,2017-03-02 20:35:11 UTC,"Change abandoned by Ann Taraday (<email address hidden>) on branch: master
Review: https://review.openstack.org/439185
Reason: can be fixed with https://review.openstack.org/#/c/365653/"
1668410,2017-03-01 21:09:51 UTC,"In the logs http://paste.openstack.org/show/601001/ for router 2fcdef4e-83fe-48b5-be0f-f45a631c1482 we get notification for router deletion, cleanup network, removing port and then started loop where router is trying to be deleted, but failed as HA port is already None."
1668410,2017-02-28 22:06:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439185"
1668410,2017-08-10 12:44:09 UTC,a single infinite loop message has filled up disk space by logs in 6 hours. 50 such messages within 10 minutes (still not many enough to be throttled by a regular configuration of a rate-limiting proxy) could have filled up the disk a lot faster leaving no time for operators to react.
1668415,2017-02-28 11:55:48 UTC,"This seems to be gnome-calculator. So, not Xmir."
1668415,2017-02-28 12:01:32 UTC,Could be racy window management in QtMir
1668415,2017-03-23 15:14:03 UTC,Is this bug still happening? Then the problem is most likely gtk since the popover is rendered on the same surface as the window (unless the window isn't responding to any clicks at all).
1668420,2017-03-11 21:12:42 UTC,https://bugs.launchpad.net/linuxmint/+bug/1668421
1668422,2017-02-28 02:46:00 UTC,"Low severity? Might be a ""feature"" :)"
1668422,2017-02-28 01:28:49 UTC,"you can also have the indicator menu opened, see screenshot"
1668422,2017-02-28 01:12:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668424,2017-02-28 22:36:54 UTC,"What's going on here is that you are feeding an object file built with the toolchain on xenial to the system linker on trusty. Unfortunately the assembler on xenial by default spits out some relocations -- in this case R_X86_64_REX_GOTPCRELX -- that the system linker on trusty does not understand.  It looks like you can fix this problem by passing ""-Wa,-mrelax-relocations=no"" to gcc when building the object file you want to include in the snap."
1668424,2017-03-01 21:32:45 UTC,Hi Michael -- thanks very much for the detailed insight.  I'll try the GCC flags you suggest and see where it goes.
1668427,2017-03-10 20:14:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668427,2017-03-10 20:49:44 UTC,It also make impossible to rebuild the yakkety gradle and groovy package.
1668427,2017-03-10 22:45:33 UTC,"To circumvent this problem I backport jarjar 1.4+svn142-6  from zesty.
This fix the FTBS problem."
1668432,2017-03-06 18:41:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442105"
1668432,2017-06-27 15:56:16 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1668432,2018-07-06 13:43:16 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.openstack.org/442105"
1668432,2020-08-20 15:30:32 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.opendev.org/442105"
1668445,2017-10-24 04:22:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668449,2017-02-28 01:19:54 UTC,"Similarly see bug 1512609, but I think that's a different interface."
1668449,2017-02-28 00:26:44 UTC,screenshot
1668450,2017-03-08 01:12:32 UTC,This is reported upstream now: https://rt.perl.org/Public/Bug/Display.html?id=130949
1668450,2017-02-28 00:43:20 UTC,"I can't close this, but it turns out this also happens on newer versions of debian like stretch (with perl 5.24).  I had tried stable but that only has 5.20, so it seems this may be new in the 5.22ish area."
1668453,2017-02-28 00:46:30 UTC,This is on 10.1.21. Tested on two separate machines.
1668457,2017-03-07 17:13:51 UTC,There's a partial fix for this in the PPA here: https://launchpad.net/~attente/+archive/ubuntu/gtk-mir
1668465,2017-03-24 18:20:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668465,2017-03-24 18:31:00 UTC,"This week, I started getting 1 cm boarders around windows after a suspend.  The boarders are white with colored speckles and lines. Hardware is Nvidia Quadro 1000m, with the nvidia 375.39 driver.  This driver must have just been updated from the 367.57 driver which never had any problems.  Restarting lightdm or logging out then in again fixes the problem. The software updater/additional drivers tab only offers the 375.39 (tested), the 340.102 and the 304.135 Nvidia drivers, not the 367... version."
1668465,2017-04-11 00:12:35 UTC,"I found the same bug.
This is my graphic card (but I'm not sure how to check the driver version):
Video Card:     NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)
OS version:	Ubuntu 16.04.2 LTS"
1668466,2017-03-07 09:33:39 UTC,"No, in bug 1656727 the exception was thrown by libmiral code [miral::BasicWindowManager::info_for()] and caused by synchronisation issues in QtMir code."
1668466,2017-11-03 16:36:40 UTC,Syncing task from Mir.
1668466,2017-03-07 01:41:48 UTC,See also bug 1656727 (?)
1668466,2017-03-01 09:17:22 UTC,"OK, sorry, I didn't see the mention of Unity8 (or kgunn) in the description. I should follow all the links in comments."
1668466,2017-03-01 01:25:36 UTC,It's not low priority. kgunn reported it (and I confirmed it) on Unity8 in zesty.
1668466,2017-02-28 10:36:15 UTC,It took several attempts to reproduce a problem with mir_demo_server. It is easy to reproduce in mir_proving_server.
1668466,2017-02-28 10:16:19 UTC,I was testing both 0.26.1 zesty and lp:mir trunk. Both crashed.
1668466,2017-02-28 09:20:06 UTC,Might be a side-effect of the client having crashed:
1668466,2017-02-28 09:18:53 UTC,And here's a full stack trace of the server crash. The only map-related part I can see is:
1668466,2017-02-28 09:17:48 UTC,"Here's a reliable way to trigger the crash:
  1. Run nautilus under Mir.
  2. Select some icons.
  3. Right click on the selection.
  4. Click away to close the menu.
  5. Try to drag the selected icons."
1668466,2017-02-28 08:17:26 UTC,"This crash was first discovered in Unity8 this morning (bug 1668435), but then also found by me in Mir demo servers (I forget which ones)."
1668466,2017-02-28 02:03:13 UTC,"It seems we have tried to fix this crash previously as bug 1497128, and declared it fixed."
1668466,2017-02-28 01:54:31 UTC,I wonder if bug 1667645 is related?
1668466,2017-02-28 09:57:05 UTC,"Hmm, testing with miral-app (zesty, mir 0.26.1, miral 1.2) this ""just"" crashes the client."
1668467,2017-02-28 15:31:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668467,2017-03-22 02:08:31 UTC,"Actually, this could easily be a side-effect of bug 1671424. Let's fix that first."
1668467,2017-02-28 15:20:07 UTC,I *think* this is gtk-mir.
1668467,2017-03-21 11:15:17 UTC,Not happening in miral-shell with the latest gtk to land in Zesty
1668467,2017-02-28 02:24:21 UTC,I can't reproduce the bug in Mir demo servers so assigning to Unity8.
1668467,2017-02-28 12:14:01 UTC,"Can reproduce in miral-app, so probably gtk-mir, miral or mir"
1668469,2017-05-25 04:00:13 UTC,I think this is just better provisioning retries and provisioning awareness.
1668469,2019-09-09 04:09:55 UTC,"Since this report has been filed, we have added a functionality to re-direct users to a new location (controller/model) after a migration. I wonder if this failure has been addressed as part of that work."
1668474,2017-03-29 07:47:42 UTC,"On Wed, Mar 29, 2017 at 01:36:17AM -0000, Brian Morton wrote:

>                   The only thing I would think it could affect would be
> external modules built against mod_proxy.h
"
1668474,2018-02-07 15:44:00 UTC,Fixed and released in v2.4.12.
1668474,2017-03-29 13:01:51 UTC,"I don't think it is an actual incompatibility since the util function for copying those values takes into consideration the size of the dst buffer. As long as it is being lengthened, I think it's OK. It would be a problem if we were reducing it and src were larger than dst."
1668474,2017-03-29 13:41:23 UTC,"OK, but why can't that argument be accepted by upstream in their 2.4 branch first?"
1668474,2017-03-29 20:45:24 UTC,An excellent question/point. That should probably get hashed out on the upstream BZ first. The discussion about it was very minimal. I'll get on there and poke at that issue.
1668474,2017-03-30 13:10:45 UTC,"Thanks! So I think our position for the time being is to hold this pending upstream's acceptance of the patch into their 2.4 branch. If something changes so we should reconsider, further discussion is welcome."
1668474,2018-02-06 02:52:48 UTC,AH02808: Alert! worker name ....too long; truncated to:96 characters
1668474,2018-02-07 15:39:00 UTC,This was worked around in v2.4.12 by supporting truncation of the balancer name:
1668474,2018-02-07 15:58:00 UTC,"Sorry but no, the situation is even now worsier than before."
1668474,2017-03-29 01:36:17 UTC,"Hi Robie,"
1668474,2018-02-07 16:55:21 UTC,"(In reply to Jim Jagielski from comment #20)

> But it is NOT silently. It is logged at APLOG_ERR to allow the admin to know
> that it happened and to decide if it is, or is NOT, a problem.
"
1668474,2018-02-07 17:07:26 UTC,"Of course exposing resources unintentionally is EVIL. That is why when there is the possibility, it is logged so allow the admin, who is the final arbitrator, to determine if they are exposed or not."
1668474,2018-02-07 18:35:47 UTC,"The proxypassed ressources, from a security point of view have not to be exposed in another location, if there is a mismatch, it is a fatal configuration error."
1668474,2018-02-07 22:26:02 UTC,"Is there some very sensitive internal structure which cannot be expanded to include some larger, arbitrary number of characters/bytes for the worker-name? If not, can we just get a higher limit on the URL length? Most URL limits in httpd are around 8k characters/bytes, no?"
1668474,2018-02-08 08:39:52 UTC,">
> (In reply to Jim Jagielski from comment #22)
> > Of course exposing resources unintentionally is EVIL. That is why when there
> > is the possibility, it is logged so allow the admin, who is the final
> > arbitrator, to determine if they are exposed or not.
>
> Unfortunately, the log is only advisory. httpd continues to start up in what
> I would describe generously as a ""degraded"" condition... one where a
> (likely) larger URL space will be proxied than initially intended.
"
1668474,2018-02-08 15:01:32 UTC,"(In reply to Ruediger Pluem from comment #25)

> >
> > (In reply to Jim Jagielski from comment #22)
> > > Of course exposing resources unintentionally is EVIL. That is why when there
> > > is the possibility, it is logged so allow the admin, who is the final
> > > arbitrator, to determine if they are exposed or not.
> >
> > Unfortunately, the log is only advisory. httpd continues to start up in what
> > I would describe generously as a ""degraded"" condition... one where a
> > (likely) larger URL space will be proxied than initially intended.
>
> I would completely agree if this would be the case, but it isn't. The error
> messages tells you that the worker name was truncated. This is unrelated to
> the request URL that is forwarded. The truncated worker name only means that
> if you have multiple ProxyPass directives and if the truncation of the
> worker name leads to the same worker name they use the same connection pool
> for the backend connections. This is no issue at all, contrawise: It saves
> resources on the backend.
"
1668474,2018-02-13 06:39:28 UTC,"(In reply to Christopher Schultz from comment #26)

> (In reply to Ruediger Pluem from comment #25)
> > >
> > > (In reply to Jim Jagielski from comment #22)
> > > > Of course exposing resources unintentionally is EVIL. That is why when there
> > > > is the possibility, it is logged so allow the admin, who is the final
> > > > arbitrator, to determine if they are exposed or not.
> > >
> > > Unfortunately, the log is only advisory. httpd continues to start up in what
> > > I would describe generously as a ""degraded"" condition... one where a
> > > (likely) larger URL space will be proxied than initially intended.
> >
> > I would completely agree if this would be the case, but it isn't. The error
> > messages tells you that the worker name was truncated. This is unrelated to
> > the request URL that is forwarded. The truncated worker name only means that
> > if you have multiple ProxyPass directives and if the truncation of the
> > worker name leads to the same worker name they use the same connection pool
> > for the backend connections. This is no issue at all, contrawise: It saves
> > resources on the backend.
>
> Thanks for that clarification. To re-phrase, the worker name is being
> truncated, but incoming URLs will not be truncated for comparison, yes?
"
1668474,2018-02-14 13:58:59 UTC,"(In reply to Ruediger Pluem from comment #27)

> (In reply to Christopher Schultz from comment #26)
> > Could this become a problem is if the hostname of the origin server is
> > something insanely long? For example, if I want two workers like
> > http://super-long-hostname:80/ and http://super-long-hostname:81/ and those
> > ""super-long-hostname"" names exceed the worker-name limit, they will be
> > considered the same worker, yes? That means that requests that should go to
> > e.g. port 81 might end up instead going to port 80.
>
> Yes, this would be a problem. There is a similar PR (PR62085) on this.
> But due to ABI constraints this is not easy to fix in a stable version.
"
1668474,2019-09-20 21:36:17 UTC,*** This bug has been confirmed by popular vote. ***
1668474,2018-02-07 16:46:34 UTC,"But it is NOT silently. It is logged at APLOG_ERR to allow the admin to know that it happened and to decide if it is, or is NOT, a problem."
1668474,2017-03-28 13:43:01 UTC,"Hi Brian,"
1668474,2014-02-25 23:58:22 UTC,I can also confirm the bug. This version is completely useless have to downgrade. Even the hack does not work. Just changing the #define PROXY_WORKER_MAX_NAME_SIZE      96   by itself does nothing at least on my side even if you place a number beyond what is needed it still says too long.
1668474,2017-03-06 18:06:28 UTC,"Brian, thank you for the patch."
1668474,2012-05-11 01:32:29 UTC,Hi.
1668474,2014-02-13 17:29:52 UTC,I confirm the bug and second the importance of this bug to be solved.
1668474,2017-03-09 02:16:17 UTC,"Hi Robie, this fix is in Apache SVN trunk but isn't in upstream stable 2.4 release branch yet so all Ubuntu versions will be affected. In addition, no such patch exists in Debian source. https://anonscm.debian.org/cgit/pkg-apache/apache2.git/tree/modules/proxy/mod_proxy.h#n350 and https://anonscm.debian.org/cgit/pkg-apache/apache2.git/tree/debian/patches"
1668474,2014-02-26 07:02:44 UTC,"We got our way using PT rewrites, eg"
1668474,2014-07-02 22:50:43 UTC,"I can confirm this bug as well on Kubuntu 14.04 LTS 64-bit running Apache 2.4.7.  Unfortunately, it is making it impossible for me to serve Plone pages through Apache, which is preventing me from upgrading my production servers to 14.04 LTS.  It would be great if this issue could be addressed soon.  Thanks."
1668474,2014-07-03 07:43:12 UTC,"Alan, you can use rewrites instead of proxypass, even if it is a bug, this workaround which is more another way to do that  workaround will let you upgrade."
1668474,2014-08-29 18:35:06 UTC,"I am looking into whether or not that should be a fatal error... we may be able to get around just reporting it, and still using/accepting a truncated copy."
1668474,2014-09-04 09:21:38 UTC,"Maximum worker name length increased by jim to 256 in trunk (and some other limits increased as well). Revisions r1540318, r1621367, r1621372, r1621373, r1621382.
Proposed for backport to 2.4.x."
1668474,2014-07-27 18:40:51 UTC,I second that. Especially with unix domain sockets allowed in mod_proxy the names can get quite long.
1668474,2014-09-04 19:06:18 UTC,256 is not enougth !
1668474,2014-09-08 10:53:46 UTC,There's a workaround available that should be applicable to many situations: combined ProxyPass with RewriteRule [P] flag:
1668474,2014-09-08 10:56:42 UTC,"if you had read the bug report, you would notice that i posted myself this workaround."
1668474,2014-09-08 18:10:44 UTC,Sorry. I read much more than this bug report (there's also other discussion going on) and overlooked your workaround in comment #3 above.
1668474,2014-09-08 18:58:32 UTC,Even easier: Create a
1668474,2014-12-02 14:20:48 UTC,+1 for increasing the URL length limit for proxy targets.
1668474,2017-02-28 03:08:27 UTC,Patch attached for trusty. Unsure how to generate a debdiff in this case.
1668474,2017-02-28 04:28:51 UTC,"The attachment ""Patch for trusty"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1668474,2014-09-04 11:24:01 UTC,There's an API compatibility problem with a straight backport proposal. Backport on hold.
1668476,2019-06-25 02:45:42 UTC,I am pretty sure that veebers is not working on this bug.
1668477,2019-06-25 02:45:52 UTC,I am pretty sure that veebers is not working on this bug.
1668478,2019-06-25 02:46:04 UTC,I am pretty sure that veebers is not working on this bug.
1668486,2017-03-26 08:48:23 UTC,@irenab
1668486,2017-04-16 02:22:37 UTC,"Currently Kuryr-libnetwork will not work with swarm mode:
https://github.com/docker/docker/issues/32604"
1668486,2017-03-23 10:07:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449038"
1668486,2017-05-05 09:51:03 UTC,"Reviewed:  https://review.openstack.org/449038
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=0dd2ad15af4fa7fd9e3ef1803f2e1bfe2a787d7a
Submitter: Jenkins
Branch:    master"
1668486,2017-03-22 10:20:11 UTC,"Based on the comments is https://github.com/docker/docker/issues/24569, kuryr must be implemented as managed plugin"
1668486,2017-03-22 13:46:27 UTC,"Hi Irena,"
1668487,2017-02-28 06:36:16 UTC,"Hi Nisha,"
1668487,2017-03-01 07:24:02 UTC,"Madhuri, We already started working on this. Thanks for extending helping hand. you can always help with the code."
1668487,2017-11-20 16:53:08 UTC,The spec is https://review.openstack.org/#/c/438859/
1668487,2018-01-28 10:31:13 UTC,"Reviewed:  https://review.openstack.org/438859
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=a82a8f644e1e4d319ad84ca225c80ef930bd747c
Submitter: Zuul
Branch:    master"
1668494,2017-02-28 05:07:57 UTC,"Update:
1. Default is TRUE，support root account.
2. Support qt binding."
1668495,2017-03-01 15:09:26 UTC,I have just observed this happening in YouTube on Firefox as well. The browser debugger says the missing fonts are indeed Roboto. Looks as though it may be a problem with the Roboto font as packaged.
1668495,2017-03-01 20:39:42 UTC,Workaround is to install Roboto from here: https://fonts.google.com/specimen/Roboto?selection.family=Roboto
1668495,2020-05-09 15:50:03 UTC,"Tried Guitarix on 20.04 and it looks like this is no longer an issue. If you're still seeing the problem on a supported version of Ubuntu, do re-open this bug and we can investigate further."
1668495,2020-07-09 04:17:20 UTC,[Expired for guitarix (Ubuntu) because there has been no activity for 60 days.]
1668498,2017-09-25 05:08:20 UTC,Same result with Landscape 17.03~bzr940-0~941~ubuntu16.04.1
1668516,2017-03-01 13:18:38 UTC,"Unfortunately, this is more like a feature request than a bug, as the behavior of rebuild is undefined for volume-backed instances: in current master of Nova this will cause a re-attach of a volume, but it's not going to be rebuilt from a new image."
1668519,2017-03-17 07:00:19 UTC,https://product-ci.infra.mirantis.net/job/10.0.acceptance.ubuntu.failover_group_2/6/testReport/(root)/shutdown_non_primary_controller_ceph/shutdown_non_primary_controller_ceph/
1668522,2017-03-03 01:27:16 UTC,This has gone away as a consequence of fixing the unbind bug - it was an unbind/cleanup issue.
1668524,2017-02-28 10:21:17 UTC,"""The currently open folder or the folder where the last operation was performed is deemed to be the active directory."""
1668529,2017-06-20 14:28:06 UTC,seems you want a bulk enable/disable endpoint?
1668532,2017-03-14 10:39:40 UTC,"It will be good to see the backport of this commit from master to the stable/mitaka branch, because our customer is using 9.x isos. This changes should not affect other customers, because during the upgrading procedure bootstrap_admin_node.sh don't use."
1668532,2017-03-22 11:12:15 UTC,Before getting rid of Docker on the master node we need to do something with tests which expect docker on master node. Probably these test must install it before run.
1668532,2017-03-16 14:34:41 UTC,"This solution is neither acceptable nor desirable, at least for the following reasons:"
1668532,2017-03-14 11:00:15 UTC,"BTW, something is wrong with this bug's nominations. Georgy pushed a patch for master branch, but there is no such kind of milestone in bug's nominations."
1668532,2019-12-18 17:28:10 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/444793
Reason: This repo is retired now, no further work will get merged."
1668532,2017-03-14 10:47:22 UTC,"It is not a backport, Docker is already on 9.0 ISO. In order to get rid of it we need to add line to update scripts to remove the package."
1668532,2017-03-14 09:15:18 UTC,In order to get rid of docker in 9x we need to change update scripts so that it deletes docker package.
1668532,2017-03-14 10:55:33 UTC,I think that Valeriy is talking about  E/// builds.
1668532,2017-03-13 09:47:43 UTC,"Invalid for 9.x
We use 9.0 ISO which already contains docker and upgrade it."
1668532,2017-03-02 14:41:30 UTC,sla2 for 9.0-updates
1668532,2017-03-01 15:04:56 UTC,Let's remove docker installation for 9.x updates too.
1668532,2017-03-01 14:43:22 UTC,We don't use docker so we shouldn't install it the first place. However we cannot delete in during update because some customers are use it. So let's stop installing it in new versions and not backport the fix.
1668532,2017-02-28 08:51:49 UTC,sla1 for 9.0-updates
1668532,2017-03-13 09:57:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444793"
1668534,2017-04-06 19:24:11 UTC,Thank you for the report.
1668534,2018-01-24 22:34:23 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1414
1668538,2021-01-08 01:25:51 UTC,"Closing this one off. For Azure, we're now using persistent storage volumes and fstab also mounts the devices using 'nofail'. e.g.:"
1668538,2019-10-14 13:32:03 UTC,See also https://bugs.launchpad.net/ubuntu-repository-cache/+bug/1835319
1668540,2017-02-28 09:43:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668549,2017-03-06 05:55:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441750"
1668549,2017-03-10 15:10:46 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/444343"
1668549,2017-03-10 15:42:31 UTC,"Reviewed:  https://review.openstack.org/441750
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=72a0ec9adcd19a96644638e8324566fcc4af8799
Submitter: Jenkins
Branch:    master"
1668549,2017-04-06 12:46:22 UTC,This issue was fixed in the openstack/python-novaclient 8.0.0 release.
1668549,2017-04-30 12:42:14 UTC,"Reviewed:  https://review.openstack.org/444343
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=b535bbd6831a9747b0b71a9031b1149b48292a94
Submitter: Jenkins
Branch:    stable/ocata"
1668549,2017-05-08 21:46:39 UTC,This issue was fixed in the openstack/python-novaclient 7.1.1 release.
1668550,2017-04-17 10:51:45 UTC,Verified by swarm at 1575
1668550,2017-03-10 12:25:34 UTC,"Reviewed:  https://review.openstack.org/436412
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=535d8fdbefe7afd9ac3e4405c16999285f5e3369
Submitter: Jenkins
Branch:    stable/newton"
1668550,2017-03-08 12:21:21 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1668550,2017-03-01 16:09:12 UTC,"Reviewed:  https://review.openstack.org/367942
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=90376da9f48748ca2b41b23554112999159f28fc
Submitter: Jenkins
Branch:    master"
1668550,2017-03-07 12:40:54 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442437"
1668550,2017-03-07 16:15:46 UTC,"Reviewed:  https://review.openstack.org/442437
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=6e4eebd5f3f5e34c5134030ff45fcff7eb8ac217
Submitter: Jenkins
Branch:    stable/ocata"
1668552,2017-04-06 11:13:26 UTC,"Since there is nothing left to sponsor, I am unsubscribing ubuntu-security-sponsors. Please re-subscribe the group when attaching another debdiff. Thanks!"
1668552,2017-03-31 21:27:56 UTC,This bug was fixed in the package ktnef - 4:15.12.3-0ubuntu1.1
1668552,2017-03-02 15:39:22 UTC,I cannot make debdiffs' for kdepim as I am not sure if the patch is compatible. Someone familiar with the code should patch it.
1668552,2017-03-02 15:34:29 UTC,debdiff for ktnef in xenial is attached.
1668552,2017-03-01 15:48:00 UTC,"Ktnef exists in xenial and should be affected the same. As for kdepim, I made a mistake when looking at the contents. The code is rather different, so if the old ktnef from kdepim is affected then this is relevant for trusty *and* xenial, not just trusty."
1668552,2017-03-02 13:18:15 UTC,This bug was fixed in the package ktnef - 4:16.04.3-0ubuntu1.1
1668552,2017-03-01 13:19:17 UTC,"ACK on the debdiff in comment #1, I've uploaded packages for building to yakkety and zesty with a slight changelog whitespace and pocket change. The yakkety package will be published as a security update as soon as it's built. Thanks!"
1668552,2017-03-01 08:49:07 UTC,Xenial is in kdepim not ktnef.
1668552,2017-03-01 08:39:31 UTC,debdiff for yakkety is included in the attachment.
1668552,2017-03-01 15:19:07 UTC,This bug was fixed in the package ktnef - 4:16.04.3-0ubuntu2
1668555,2017-09-20 08:41:54 UTC,"I've just hit this bug when snapping a project. Part1 works fine, but part2 fails with RecursionError."
1668564,2017-06-14 13:17:57 UTC,I can confirm this bug on my Ubuntu-GNOME 16.04 system with Numix theme:
1668564,2017-02-28 10:23:53 UTC,"I must add: ""That happens with Numix theme"""
1668564,2017-07-02 13:36:51 UTC,Same happens on Ubuntu-GNOME 17.04 with PDF Chain 0.4.4
1668565,2017-02-28 20:32:01 UTC,"The attachment ""egl_create_destroy_image.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1668565,2017-02-28 17:44:30 UTC,"This patch allows building the package (v1.2.4) against libegl1-mesa-lts-xenial 11.2.0 (after also disabling opencv support because one of the required dependencies wouldn't install).
See also ppa:rjvbertin/misc ."
1668565,2017-02-28 12:02:58 UTC,Or not:
1668569,2017-02-28 11:04:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/438916"
1668569,2019-10-07 21:04:37 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.opendev.org/438916
Reason: I'm going to abandon this, please feel free to reopen if you would like to pick it up. Thanks."
1668574,2017-02-28 10:43:42 UTC,this will made bvt red when it will be merged - so preventive marking it as blocker
1668575,2020-05-09 08:52:40 UTC,"PPAs are currently pretty stale, and not connected to the new source on GitHub."
1668575,2019-08-21 21:10:25 UTC,"Hi, @Stephen Boddy, seems like it can be closed."
1668575,2020-03-17 02:52:23 UTC,Verified fix is available in the released version included in Ubuntu.
1668575,2017-02-28 16:16:35 UTC,Committed revision 1751.
1668575,2019-08-16 17:41:15 UTC,@Stephen Boddy
1668593,2017-03-21 14:12:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668593,2017-04-19 18:35:15 UTC,"The two adapters you've listed are both using the rtl8192cu driver that is bug #1666421 , this is a possible duplicate."
1668594,2017-03-09 16:42:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1668594,2017-03-15 10:36:19 UTC,This bug was fixed in the package linux - 4.4.0-67.88
1668594,2017-02-28 13:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1668594,2017-02-28 19:38:20 UTC,"Do you plan on sending an SRU request to the kernel team mailing list?
 <email address hidden>"
1668594,2017-03-01 20:28:40 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-February/082734.html
1668594,2017-03-10 07:22:19 UTC,"works as expected, thanks."
1668595,2017-03-19 21:03:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668606,2017-02-28 13:40:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668606,2017-02-28 14:01:15 UTC,"this is known, has not been implemented yet"
1668623,2017-02-28 14:26:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/438976"
1668623,2017-03-10 08:26:57 UTC,"Reviewed:  https://review.openstack.org/438976
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=6bb1ac1857ddf9d5959db3a7b24d3fe5a33cae95
Submitter: Jenkins
Branch:    master"
1668623,2017-04-04 09:17:48 UTC,workaround deletion will be tracked in https://bugs.launchpad.net/fuel/+bug/1679585
1668626,2017-02-28 16:33:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1668626,2017-02-28 19:11:34 UTC,I wanted to add that I experience no matter if I am using Unity or KDE or any other WM.
1668626,2017-03-01 15:53:58 UTC,"I'm not sure if this constitutes a fix or not, but I was able to get GTK applications looking normal again by going into System Settings and changing the theme to Adwaita or Ambience. I don't think there was any theme set (or a different theme not listed)... and it wasn't easy to select a theme since separators were gone and clicking in the right area was more of a guess. Eventually I got it selected though and everything looked correct again."
1668627,2017-03-01 11:19:12 UTC,"(assigning you bob, since you volunteered yesterday)"
1668627,2017-03-01 11:18:42 UTC,see https://review.openstack.org/#/q/status:open++branch:master+topic:tempest-manager
1668627,2017-03-02 08:33:19 UTC,being addressed by https://review.openstack.org/#/c/439900/
1668627,2017-09-27 20:18:33 UTC,see https://review.openstack.org/#/c/506874/
1668628,2017-03-01 10:20:03 UTC,"Reviewed: https://review.fuel-infra.org/31368
Submitter: Olga Gusarenko <email address hidden>
Branch: master"
1668628,2017-03-01 11:09:21 UTC,"Fix proposed to branch: stable/9.2
Change author: Olena Logvinova <email address hidden>
Review: https://review.fuel-infra.org/31370"
1668628,2017-03-01 11:25:38 UTC,"Reviewed: https://review.fuel-infra.org/31370
Submitter: Olga Gusarenko <email address hidden>
Branch: stable/9.2"
1668637,2017-12-18 09:16:08 UTC,"Change abandoned by Joachim Barheine (<email address hidden>) on branch: master
Review: https://review.openstack.org/445027"
1668637,2017-02-28 16:09:23 UTC,"fix is available, change request will follow later"
1668639,2019-05-16 20:50:49 UTC,"It is fixed in Ubuntu Bionic and late but this LP bug have never been mentioned in the changelog, which explains why the status didn't change until now (after a manual status change from my part)"
1668639,2017-08-07 11:50:00 UTC,@slashd Thank you! I will start work on debdiffs for the SRU's ASAP.
1668639,2017-08-07 11:49:19 UTC,@cyphermox Thank you!
1668639,2017-08-31 12:51:05 UTC,Marking Won't fix for Yakkety as it is EOL.
1668639,2017-08-30 08:53:07 UTC,Unsubscribing ~ubuntu-sponsors as there's nothing left to do. Please feel free to resubscribe once patches are ready to upload (or mark your diff as a patch and let the bot do it for you) or if this was done in error.
1668639,2017-08-05 21:25:52 UTC,This bug was fixed in the package rsyslog - 8.16.0-1ubuntu7
1668639,2017-04-04 13:11:11 UTC,"Too late now for sponsorship to Zesty. Since it will come with the next rsyslog merge in 8.24.0-1, well go forward with the SRU post-merge of the next rsyslog"
1668639,2017-08-04 14:17:25 UTC,Looks like this is still missing one additional commit from when it was included in Debian; namely the addition of init-system-helpers in the Depends: field for rsyslog (this makes sure we have a new-enough init-system-helpers so try-restart works).
1668639,2017-02-28 22:33:18 UTC,"This doesn't yet seem to be fixed in Zesty, although debian fixed it in package version 8.24.0-1."
1668639,2017-02-28 16:31:44 UTC,"The attachment ""rsyslog-yakkety.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1668639,2017-08-04 16:57:10 UTC,"Hi Frode,"
1668647,2017-02-28 15:07:10 UTC,"No idea how I managed to blame the wrong package, the package installing this plugin is actually libkf5khtml-bin 5.26.0-0ubuntu1."
1668647,2017-04-15 11:04:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668647,2017-04-15 11:14:55 UTC,"The effects of this bug are seen when compiling and using Krusader (for example using Ubuntu 16.04), and also, for example, when using the Krusader package of Ubuntu 17.04:
If a user utilizes F3 to see an image... that image is not seen. If the preview of Krusader is used, the user can't see the image."
1668647,2017-04-22 18:51:22 UTC,"For me the issue is gone with Ubuntu 17.04, Krusader can show images in the viewer via khtmlimage (okularkimgio option exists as well now but that's irrelevant here)."
1668650,2017-02-28 15:16:27 UTC,"We can't make one go away. Ubuntu has changed the whole concept of HWE kernels and now we need to support both. See https://docs.ubuntu.com/maas/2.1/en/release-notes#important-changes ""New HWE and GA kernel naming convention""."
1668650,2019-09-19 11:56:01 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1668652,2017-11-09 18:47:05 UTC,"It is registered but theSongUsagePlugin is deactivated so the register has not been called.
It registers a song has been used."
1668652,2017-11-09 17:16:05 UTC,"Oh, no, it's still there in trunk:"
1668652,2017-11-09 17:02:55 UTC,"I saw this in the code the other day. For some reason, we try to call ""slidecontroller_live_started"" from the Registry without ever having actually registered the function call. The settings files won't reveal anything because it's a code issue."
1668652,2017-11-09 14:31:18 UTC,"Hi Simon,"
1668652,2017-11-09 16:23:25 UTC,Hi Phill
1668655,2017-02-28 15:37:19 UTC,"StacktraceTop:
 add<WTF::IdentityHashTranslator<WTF::HashTraits<JSC::MarkedArgumentBuffer*>, WTF::PtrHash<JSC::MarkedArgumentBuffer*> >, JSC::MarkedArgumentBuffer* const&, JSC::MarkedArgumentBuffer*> (extra=<optimized out>, key=<optimized out>, this=0x1) at ./Source/WTF/wtf/HashTable.h:868
 add (value=<optimized out>, this=0x1) at ./Source/WTF/wtf/HashTable.h:387
 add (value=<optimized out>, this=<optimized out>) at ./Source/WTF/wtf/HashSet.h:223
 JSC::MarkedArgumentBuffer::addMarkSet (this=this@entry=0x7ffd38414e68, v=...) at ./Source/JavaScriptCore/runtime/ArgList.cpp:42
 JSC::MarkedArgumentBuffer::expandCapacity (this=this@entry=0x7ffd38414e68, newCapacity=newCapacity@entry=9) at ./Source/JavaScriptCore/runtime/ArgList.cpp:85"
1668660,2017-03-15 22:55:35 UTC,Same problem here...
1668660,2017-03-16 09:59:33 UTC,"ppa-purge does not always use aptitude, only in certain problem cases. My branch does not require aptitude at all. Please test, if your purging task can be done by the script in the proposed branch."
1668661,2017-03-16 18:16:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668661,2017-03-21 17:45:25 UTC,"Currently various aspects of unity8 and related services are based around upstart, which isn't accessible to system-settings (without a bit of hacking) due to it being started by systemd. So our current plan is to hold off on this until the unity8 migration to systemd is completed."
1668664,2017-03-29 16:15:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668664,2017-03-29 16:16:02 UTC,Related bug that can be closed simultaneously: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1653734
1668664,2017-10-03 23:11:02 UTC,I updated the bug description and this patch since the other issues mentioned earlier have been fixed in Ubuntu's Firefox 56.
1668669,2017-03-02 01:54:28 UTC,Hi Raoul
1668669,2017-03-02 16:15:07 UTC,Hi Raoul
1668669,2017-03-01 23:36:27 UTC,"Hey Simon,"
1668669,2017-03-01 16:57:09 UTC,"Is the configuration window that tall on all your computers? On mine it doesn't look as tall as yours, and my font appears to be bigger than yours."
1668669,2017-03-01 17:22:01 UTC,"I tried Windows 10 Home on 2 computers and Pro on a third. In two of those
it was a newly installed Windows 10 and as a consequence an out of the box
OpenLP with a copied data folder. I got the same size configuration window
and same behaviour."
1668669,2017-03-01 20:31:40 UTC,Hi Raoul
1668686,2017-02-28 16:43:31 UTC,"StacktraceTop:
 malloc_consolidate (av=av@entry=0x7fb575022b00 <main_arena>) at malloc.c:4204
 _int_free (av=0x7fb575022b00 <main_arena>, p=0x55f793a4f210, have_lock=0) at malloc.c:4110
 __GI___libc_free (mem=<optimized out>) at malloc.c:2982
 da_free (d=0x55f7937c9ad0) at darray.c:275
 trie_free (trie=0x55f7913bf370) at trie.c:229"
1668686,2018-01-09 20:00:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668690,2020-10-26 10:52:07 UTC,Unassigning due to a long inactivity.
1668701,2017-02-28 17:15:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668701,2017-03-17 19:19:40 UTC,This bug was fixed in the package unity8-desktop-session - 1.0.13+17.04.20170307-0ubuntu1
1668724,2017-03-06 21:43:55 UTC,LGTM
1668724,2017-03-06 22:11:12 UTC,Thanks for looking. I'll push that tonight.
1668724,2017-03-08 07:06:05 UTC,"Hello Cam, or anyone else affected,"
1668724,2017-03-08 07:06:46 UTC,"Hello Cam, or anyone else affected,"
1668724,2017-03-08 07:07:11 UTC,I see tasks for Trusty and Yakkety but they aren't in the queue?
1668724,2017-03-08 07:07:38 UTC,Unsubscribing ~ubuntu-sponsors as I don't see any debdiffs or similar here.
1668724,2017-03-08 07:10:20 UTC,Ah. I see cgroup-lite in the backports queue for Trusty. Was this intentional?
1668724,2017-03-08 07:19:51 UTC,"My script can't see the Yakkety upload because it's in unapproved in the updates pocket, not the proposed pocket. I've never seen that before. How did you upload it?"
1668724,2017-06-21 19:29:13 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for precise for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1668724,2017-03-22 12:15:29 UTC,"Hello Cam, or anyone else affected,"
1668724,2017-06-27 15:22:56 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1668724,2017-08-31 10:04:19 UTC,The version of cgroup-lite in the proposed pocket of Precise that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1668724,2017-10-25 14:04:03 UTC,"This was removed from Xenial-Proposed as well.
It is still in Y-proposed but that is EOL."
1668724,2017-10-25 15:03:34 UTC,I'll still aim to push this for trusty and xenial.
1668724,2017-10-25 15:02:35 UTC,Drat.  I do think this should still be pushed.  I don't know when I'll have time to do it though.  Please keep it open.
1668724,2017-03-06 09:48:13 UTC,This bug was fixed in the package cgroup-lite - 1.13
1668724,2017-03-17 20:26:44 UTC,"Sorry, this got lost in my inbox.  I used dput.  I seemed to recall that in some recent cycle the it became either ok or preferred to use $release-updates instead of $release-proposed in SRUs.  I can trivially change it ack to yakkety-proposed if preferred."
1668724,2017-03-04 05:54:32 UTC,(s@/tmp/2@/proc/cgroups@ of course)
1668724,2017-02-28 19:51:32 UTC,Patch for cgroup-lite 1.1.5
1668724,2017-03-04 04:48:38 UTC,"There is a bug (which is fixed in newer versions) in lxc in that it does not ignore cgroups which are not used by the container.  So in your particular case, if you're not using the co-mounted controllers, then indeed fixing the lxc bug should work for you as well."
1668724,2017-02-28 19:52:22 UTC,Patch for 1.12
1668724,2017-02-28 20:14:16 UTC,"It looks like there were fixes in the latest version of cgroup-lite that would still be applicable/useful for earlier ubuntu releases, but I tried to minimize the diffs to have the functionality that I need. Let me know if you need a patch for trusty as well."
1668724,2017-02-28 20:15:31 UTC,"Thanks for the patches.  Note that you've changed the loop variable from d to c, but the loop is still using d, so nothing gets mounted with that patch verbatim.  Switching the variable back to d fixes the issue for me."
1668724,2017-02-28 20:26:58 UTC,"Whoops, didn't notice I changed that part in my local copy. Should have been more careful with my patch."
1668724,2017-02-28 20:27:23 UTC,Patch for 1.1.5
1668724,2017-02-28 20:27:46 UTC,Patch for 1.12
1668724,2017-03-04 05:53:29 UTC,FWIW something like:
1668724,2017-02-28 20:31:24 UTC,"The attachment ""cgroup-lite_1.1.5.patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1668724,2017-03-01 01:48:30 UTC,"Edit: re: the systemd hierarchy, it's actually not mentioned in /proc/cgroups, it's /proc/self/cgroups"
1668724,2017-03-04 00:24:38 UTC,I assume /sys/fs/cgroup/systemd was used because that's where systemd expected to see it.  I can't find any version which mounts it at /sys/fs/cgroup/name=systemd - do you have a version that does that?
1668724,2017-03-04 01:17:21 UTC,"Hm, I found a bug in my last version of this patch. Freshly booted machines which had not mounted the cgroupfs had all the hierarchies as 0, causing all cgroups to get mounted onto a single directory. I can work around this by detecting this scenario.
However, I wonder if I am actually seeing a bug in LXC. On my 12.04 hosts spawning 12.04 containers with the nesting.conf include, the cgroupfs gets automounted inside the container even without this package. This is not the case on 16.04 hosts. I'm currently using LXC 2.0.6."
1668724,2017-03-04 03:41:05 UTC,"Hm, yes i see (hierarchy 0).  I do worry that means that systems with the unified hierarchy will be still more of a problem, since it is mounted as hierarchy 0.  But then it's probably fine to just say that cgroup-lite doesn't support unified hierarchy."
1668724,2017-03-04 03:49:15 UTC,"(Note - this means the patch I just pushed to zesty is in fact wrong.  Since zesty requires systemd this doesn't really matter, but we must get a working patch before pushing SRU patches)"
1668724,2017-03-04 04:05:30 UTC,This bug incidentally also affects the cgroupfs-mount package.
1668724,2017-03-04 04:34:24 UTC,"I'm happy to provide a patch, but if the root cause of my issue is in lxc
it may be easier to patch that than worrying about backwards compatibility
for cgroups on older distro releases."
1668724,2017-02-28 22:59:15 UTC,"Also, is there a reason the name=systemd cgroup controller gets mounted at /sys/fs/cgroup/systemd instead of /sys/fs/cgroup/name=systemd in newer versions of cgroups-mount? It means my applications have to special-case stripping off the name= when they try to work with cgroups based upon /proc/cgroups."
1668727,2017-03-01 11:01:16 UTC,"Behaviour has changed, it seems, between 2.0.3 and 2.1.0"
1668727,2017-03-01 09:54:01 UTC,"@John A Meinel on linux, the env vars are"
1668727,2017-03-01 09:48:32 UTC,"Sorry, I forgot the version:"
1668727,2017-03-01 01:19:12 UTC,"@Frank Rosquin,
Please clarify what version of Juju you are using?"
1668727,2017-03-01 02:41:58 UTC,"socks5 is not the same as a regular http proxy. It uses different verbs, etc.
It is entirely true that we don't support socks.
http://www.jguru.com/faq/view.jsp?EID=227532"
1668727,2017-03-01 02:47:37 UTC,"Here are the golang docs around using a SOCKS5 proxy
https://godoc.org/golang.org/x/net/proxy#SOCKS5"
1668729,2019-09-16 14:07:02 UTC,Migrated to https://github.com/widelands/widelands/issues/2071
1668730,2017-03-09 19:49:05 UTC,"Ugh, translations."
1668730,2017-03-09 20:07:09 UTC,I could email the ubuntu-translators list when this is merged if that would help.
1668741,2017-03-04 07:26:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668744,2017-10-24 00:17:48 UTC,"I added trusty, xenial, and zesty tasks for this bug without verifying which releases need work."
1668744,2017-03-10 01:20:54 UTC,"Hi Erno - The firejail package is in universe and is, therefore, community supported. Could you please report this issue to the upstream project? Thank you!"
1668744,2017-04-06 04:19:29 UTC,"I reported it upstream and the author replied that it has already been fixed in the latest version, apparently there has been a rewrite of the command line handling. It didn't seem like there was going to be a security advisory on his part or anything."
1668744,2017-05-05 13:30:47 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1668744,2017-09-08 12:58:10 UTC,"Is the ""Fix Released"" status correct for this bug? In https://wiki.ubuntu.com/Bugs/Bug%20statuses it says this indicates the bug is fixed in Ubuntu, but this does not seem to be the case?"
1668744,2017-10-20 23:58:46 UTC,"Tested with latest upstream version (0.9.50) and can't reproduce the bug.
This is included in Ubuntu 17.10."
1668744,2017-10-22 10:11:52 UTC,"It's good that there is a fix in 17.10, but this remote vulnerability remains unfixed in other versions, including LTS releases.  I reported this as a xenial bug (like you can see from tags) and there it remains unfixed. I'm not well versed in launchpad usage, how should this be marked in the bug status info?"
1668748,2017-03-10 10:00:01 UTC,Need more info to look at this. Can you tell how to replicate this problem.
1668771,2019-11-25 10:55:23 UTC,This bug was fixed in the package systemd - 242-7ubuntu3.2
1668771,2019-11-13 22:14:38 UTC,autopkgtest analysis for eoan:
1668771,2019-11-12 18:07:55 UTC,"ubuntu@lp1668771:~$ dpkg -l systemd|grep ii
ii  systemd        242-7ubuntu3 amd64        system and service manager
ubuntu@lp1668771:~$ host www.montemar.cl
Host www.montemar.cl not found: 2(SERVFAIL)"
1668771,2019-11-07 21:45:07 UTC,"All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1668771,2019-11-07 13:29:36 UTC,"Hello jowfdoijdfdwfwdf, or anyone else affected,"
1668771,2019-10-17 19:38:39 UTC,this did not make it into Eoan.
1668771,2019-08-29 12:04:36 UTC,There is discussion to push systemd 241 to Eoan: https://launchpad.net/bugs/1841790
1668771,2019-08-26 23:40:43 UTC,This bug was fixed in the package systemd - 240-6ubuntu13
1668771,2019-08-21 19:48:30 UTC,"The systemd in eoan-proposed was version 243-rc1, which contained this, but that has been reverted and the current version is back to 240, which doesn't contain this.  Discussion in #ubuntu-devel indicates eoan should eventually have at least version 241, so I'm going to wait for that, and then upload this fix if eoan doesn't already contain it."
1668771,2019-08-07 20:18:27 UTC,This bug was fixed in the package systemd - 240-6ubuntu5.3
1668771,2019-08-06 18:36:43 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1668771,2019-08-06 18:36:25 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.25
1668771,2019-08-06 16:17:36 UTC,"this is included in the systemd in eoan-proposed, https://launchpad.net/ubuntu/+source/systemd/243~rc1-0ubuntu1"
1668771,2019-05-23 21:24:03 UTC,"This affects bionic openstack cloud environments when os-*-hostname is configured for keystone, and the keystone entry is deleted temporarily from upstream dns, or the upstream dns fails providing no record for the lookup of keystone.endpoint.domain.com."
1668771,2019-07-26 17:19:17 UTC,Without the patch for LP: #1668771 resolved caches the SERVFAIL answer on disco.
1668771,2017-03-07 15:48:39 UTC,I believe this should be filed upstream instead.
1668771,2019-07-31 13:10:47 UTC,autopkgtest analysis for this upload in bug 1835581
1668771,2019-05-23 21:23:08 UTC,"This is especially upsetting in an OpenStack and server environment where external DNS is being used to reach/resolve API endpoints and other systems such as database servers. A small outage to DNS becomes a potentially unbounded outage when the SERVFAIL responses are cached indefinitely, requiring manual intervention on each host in addition to fixing the cause of the SERVFAIL."
1668771,2019-07-12 19:59:34 UTC,"I've made a proposal to change the resolved.conf Cache option to a tri-state ""no, no-negative, yes"" values. [0]"
1668771,2019-07-17 22:18:58 UTC,The proposal to extend the 'cache' option with 'no-negative' has been merged upstream. I will proceed with the backports to Ubuntu on the affected LTS releases.
1668771,2017-03-13 02:50:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668771,2019-07-25 16:17:55 UTC,"Hello jowfdoijdfdwfwdf, or anyone else affected,"
1668771,2019-07-25 16:20:26 UTC,"I have accepted this to disco-proposed conditionally without the fix landing in eoan yet as per the ongoing 242 systemd merge, mostly because the proposed changes are already merged and accepted upstream. But to make sure eoan is not left without this fix, please be sure to push the changes to eoan-proposed as soon as the systemd merge is done, uploaded and migrated."
1668771,2019-07-25 21:24:08 UTC,"Hello jowfdoijdfdwfwdf, or anyone else affected,"
1668771,2019-07-26 17:15:05 UTC,Without the patch for LP: #1668771 resolved caches the SERVFAIL answer.
1668771,2019-07-20 04:19:10 UTC,"The attachment ""lp1668771-eoan.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1668780,2019-09-03 10:37:43 UTC,Currently on master/HEAD/tip (https://github.com/neovim/libvterm/archive/1aa95e24d8f07a396aa80b7cd52f93e2b5bcca79.tar.gz):
1668780,2019-10-03 04:44:56 UTC,It looks like the code has drifted quite a lot since the above patch was submitted. This patch will apply cleanly on recent code:
1668827,2017-05-16 08:06:33 UTC,"I would like to implement this, but I think we would need microversions in OSC first."
1668827,2017-03-10 08:22:07 UTC,Hi yong sheng:
1668827,2017-11-01 15:38:47 UTC,"Any update about this ?
Octavia needs a SSH key in the service tenant."
1668838,2018-03-17 02:42:57 UTC,Is there any update on this?
1668838,2017-03-15 01:34:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445707"
1668842,2017-03-14 23:02:32 UTC,pls check it in the mainline build 3047.
1668848,2017-03-07 03:51:31 UTC,"Change abandoned by Rico Lin (<email address hidden>) on branch: master
Review: https://review.openstack.org/440472"
1668848,2017-03-15 10:54:06 UTC,"Reviewed:  https://review.openstack.org/440586
Committed: https://git.openstack.org/cgit/openstack/cloudkitty/commit/?id=45e2ccfdfdc6650fe2b13be6dd6d10273be4580d
Submitter: Jenkins
Branch:    master"
1668848,2017-03-09 01:29:26 UTC,"Reviewed:  https://review.openstack.org/440234
Committed: https://git.openstack.org/cgit/openstack/python-barbicanclient/commit/?id=4ad8cfcd83383c5f59eeac4687c765d6d9b01690
Submitter: Jenkins
Branch:    master"
1668848,2017-03-09 01:06:26 UTC,"Reviewed:  https://review.openstack.org/440231
Committed: https://git.openstack.org/cgit/openstack/castellan/commit/?id=a076657518b70deda12ec8c7e82504629d7e0c48
Submitter: Jenkins
Branch:    master"
1668848,2017-05-31 15:31:38 UTC,"I think this is fixed in most places, just waiting on a couple of projects to make pike releases."
1668848,2017-03-07 03:51:26 UTC,"Change abandoned by Rico Lin (<email address hidden>) on branch: master
Review: https://review.openstack.org/440470"
1668848,2017-03-01 06:09:05 UTC,"logstash:
 http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ContextualVersionConflict%3A%20(pbr%202.0.0%5C%22"
1668848,2017-03-04 05:20:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441572"
1668848,2017-03-02 05:57:34 UTC,better logstash:
1668848,2017-03-01 06:04:38 UTC,"See:
 https://review.openstack.org/#/q/topic:bug/1668848
 https://github.com/powervm/pypowervm/pull/1
 https://github.com/sileht/python-jsonpath-rw-ext/pull/13"
1668848,2017-03-07 02:02:09 UTC,"Reviewed:  https://review.openstack.org/441572
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=13f4ff41d1d185509e33f74cd7fa8b2e41d72b82
Submitter: Jenkins
Branch:    master"
1668849,2018-01-16 14:52:58 UTC,This issue was fixed in the openstack/python-openstacksdk 0.10.0 release.
1668880,2019-09-19 12:02:52 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1668883,2017-03-09 04:20:33 UTC,"I recommend using the ubuntu-touch/staging/ubuntu channel instead. It suffers from the same boot problem as staging/meizu.en, but it has fewer deficiencies and Chinese language apps. I think it was also missing the terminal app last time I checked. The ""custom"" files are more up to date for staging/ubuntu as well."
1668883,2017-03-09 07:15:52 UTC,Thank you for your reply!
1668891,2017-03-01 09:40:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668891,2017-03-02 07:05:54 UTC,Good catch!
1668891,2017-03-12 12:48:24 UTC,🏑
1668891,2017-03-22 09:04:24 UTC,Something weird is definitely going on in here.
1668891,2020-09-21 12:59:39 UTC,"@didrocks: installing a non-classic snap with --classic with current snapd issues the following warning. (Using --classic shouldn't override the package confinement, the flag is still ignored but not silently.)"
1668901,2017-06-26 08:37:50 UTC,"This question has occurred to me independently as well. I've looked at the ceph's source code and found no reference for this extra binding to be present, see a description for this PR:"
1668901,2017-09-06 08:41:21 UTC,Technically it does not require them; marking 'Triaged' and 'Low' as this has minimal impact.
1668901,2017-09-06 08:41:43 UTC,(this is a hangover from the ceph -> ceph-mon rewrite from a few cycles back).
1668901,2018-01-07 08:07:54 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: master
Review: https://review.openstack.org/477433"
1668903,2017-03-07 07:14:25 UTC,"@nacc peculiar, this is the only change you've made to the arguments?"
1668903,2017-03-07 17:58:06 UTC,"Yes, that's right. Alternatively, you can just pass -p and it will prompt for the password."
1668903,2017-03-22 19:18:02 UTC,I don't know that we will fix this in 16.04 -- it's a low priority issue with a pretty easy workaround. Just an FYI.
1668903,2017-03-07 01:27:46 UTC,Note that skipping the space between -p and the password seems to work here. I don't know why yet.
1668903,2017-03-07 19:19:53 UTC,"Alternatively, we can at least update the help and manpage to document the behavior."
1668903,2017-03-06 20:35:10 UTC,"Ok, I have reproduced the issue on 16.10 and it does seem fixed on 17.04. While, I agree you can upgrade, 17.04 is beta still and we should fix it properly (especially if 16.04 is also affected). Let me debug it a bit further and see if we can't get a fix out soon."
1668903,2017-03-06 19:31:30 UTC,16.10.
1668903,2017-03-06 18:52:20 UTC,Hello and thank you for filing this bug report.
1668903,2017-03-06 20:56:41 UTC,"It does seem that mongodump has been rewritten in the first in 17.04 in go. So I think both 16.04 and 16.10 are affected, but not 17.04. I am working on testing a fix to the source still."
1668914,2017-05-15 18:21:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1668916,2017-03-03 09:05:08 UTC,"Another instance, with Kilo on Ubuntu:"
1668916,2017-03-03 17:02:15 UTC,And another occurrence (again with Kilo on Ubuntu Trusty):
1668917,2017-03-01 10:28:16 UTC,"StacktraceTop:
 gx.terminix.customtitle.CustomTitle.onButtonPress() (this=0x7f4d1b5be000, event=0x7f4d1b5bd320, widget=<optimized out>) at /build/terminix-XVLUcN/terminix-1.4.2/source/gx/terminix/customtitle.d:107
 gtk.Widget.Widget.callBackButtonPressEventGeneric() (widgetStruct=<optimized out>, widgetStruct@entry=0x557f858fe410, event=0x557f85b54830, wrapper=0x7f4d1b5d1b40) at Widget.d:6184
 _gtk_marshal_BOOLEAN__BOXED (closure=0x557f8590c560, return_value=0x7fff0e5e4a50, n_param_values=<optimized out>, param_values=0x7fff0e5e4ab0, invocation_hint=<optimized out>, marshal_data=<optimized out>) at ././gtk/gtkmarshalers.c:86
 g_closure_invoke () from /tmp/apport_sandbox_zAbG47/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 signal_emit_unlocked_R () from /tmp/apport_sandbox_zAbG47/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1668917,2017-03-07 18:49:56 UTC,"Resolved in 1.5.2, the package just needs to be synced to Ubuntu."
1668940,2020-07-29 13:56:58 UTC,"Sorry for the delay to reply to this bug, the fix should have been backported to Xenial some years ago but now seems too late for that. If you really need it, you are better off upgrading to Bionic, or explain why you really need it in Xenial and we may reconsider."
1668940,2017-03-16 22:42:09 UTC,This bug was fixed in the package samba - 2:4.5.4+dfsg-1ubuntu2
1668940,2017-03-16 21:06:53 UTC,"Agreed, on the SRU position, 100%. I also did send this to Debian, but it didn't make Stretch."
1668940,2017-03-16 20:05:07 UTC,Considered ACKed by comment #4.
1668940,2017-05-06 06:15:38 UTC,Will this be backported to Xenial?
1668940,2017-03-16 02:17:31 UTC,"resetting to 'new' state to correspond to FFe protocol: The bug should be set to status of ""New"" when requesting a freeze exception, to ensure the release team sees the request."
1668940,2017-03-06 23:29:16 UTC,"Note that adding the build-dep did fix the issue, but since we are in Feature Freeze, I will need to file a FFe to get the fix into 17.04 before SRU'ing back to Xenial & Yakkety."
1668940,2017-03-06 19:16:40 UTC,Hello and thank you for this report! It does seem like what is missing is a build-dependency on libcephfs-dev (also needed on Debian):
1668940,2017-03-16 19:50:37 UTC,"I'm entirely fine with this happening for 17.04, however please do hammer on it a bit in 17.04 (with enough time to revert if we find it's broken, or causes regressions for non-ceph users) before we consider backporting the change as an SRU."
1668943,2017-03-01 11:30:17 UTC,This change was made by a bot.
1668943,2017-03-01 18:23:52 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1668952,2017-03-07 09:14:30 UTC,Is this supported / well tested?
1668954,2018-05-16 13:58:11 UTC,"Change abandoned by Felipe Reyes (<email address hidden>) on branch: stable/18.02
Review: https://review.openstack.org/567968
Reason: backport not needed since https://review.openstack.org/568299 was merged into stable/18.02"
1668954,2018-05-12 02:31:59 UTC,"Fix proposed to branch: stable/18.02
Review: https://review.openstack.org/567968"
1668954,2018-05-11 21:47:38 UTC,"Reviewed:  https://review.openstack.org/567658
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=0e9020bd2a90ec301d9666195faeb7e2cbe4d089
Submitter: Zuul
Branch:    master"
1668954,2018-05-10 20:22:31 UTC,Syncing the fix into charm-keystone -> https://review.openstack.org/#/c/567658/
1668954,2018-05-10 20:21:14 UTC,wrapped keystone_wait_for_propagation() with @retry_on_exception()
1668954,2018-05-09 12:36:23 UTC,Another occurrence of this bug: https://review.openstack.org/#/c/566763/1
1668954,2018-05-09 12:47:22 UTC,The attached MP was attempting to address the error while the message is being formatted which it's already fixed by https://github.com/freyes/charm-helpers/commit/1117ba6d00c3ae1d54835f17e42cef106a416f4c
1668955,2020-09-03 15:16:45 UTC,"Change abandoned by Bhagyashri Shewale (<email address hidden>) on branch: master
Review: https://review.opendev.org/447442"
1668955,2020-09-03 16:04:30 UTC,It got invalidated by the move to py3 with full unicode support.
1668959,2017-03-01 12:29:05 UTC,"Apologies for the inconvenience, translation support is in the roadmap.
Not sure though if it will make it to the click version or in the snap version.
Thank you for your time though :-)"
1668964,2017-03-01 12:29:12 UTC,ie the window about sign up to ubuntu one does not open up.
1668967,2017-03-02 10:27:55 UTC,The Utf16 support is marked as experimental.
1668967,2017-03-01 23:24:49 UTC,    http://lame.cvs.sourceforge.net/viewvc/lame/lame/include/lame.h?view=markup
1668972,2019-03-14 10:36:39 UTC,This issue was fixed in the openstack/tripleo-validations 10.3.0 release.
1668975,2017-07-17 12:04:02 UTC,This issue was fixed in the openstack/requirements 1.1.0 release.
1668982,2017-04-11 11:41:39 UTC,"This was not done as there two other very big landings before this, and now the work has ended."
1668995,2017-03-03 16:05:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/441197"
1668995,2017-03-14 08:35:39 UTC,"Reviewed:  https://review.openstack.org/441197
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=25bda8d2da8ce9785464c899024b88bba0017000
Submitter: Jenkins
Branch:    master"
1669000,2018-11-12 09:24:27 UTC,"bobthevirus, sorry you're having trouble with that tutorial! What part of it tells you to use ""classic"", though?"
1669000,2017-03-04 23:22:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669000,2018-11-11 08:51:46 UTC,Following the snap tutorial at https://tutorials.ubuntu.com/tutorial/build-a-nodejs-service#3  has the same issue on ubuntu 18.04
1669012,2020-05-26 19:38:15 UTC,snap refresh doesn't work either:
1669015,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1669016,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1669025,2017-03-03 13:13:13 UTC,"Alexander, could you please be so kind and provide us with the first 4 steps?"
1669025,2017-03-28 15:39:41 UTC,"Snapshot doesn't contains proper journals and there is not enough information how to reproduce it.
Also, I couldn't revert env due to it not longer exists .
Moving to Incomplete.
Move to ""confirmed"" if you have necessary information or affected environment and ping me PM, please."
1669030,2017-03-01 16:57:59 UTC,But SBCL has no compilation environment.
1669030,2017-09-18 14:08:23 UTC,"I've run into this myself. The problem isn't that find-class ignores the compilation environment, which is fine as stassats said, but that defclass doesn't have compile-time effects that it ought to. CLHS says"
1669033,2017-03-02 16:39:06 UTC,"So, this is a solution for the current problem, but we may want to consider fixing the problem correctly/appropriately."
1669033,2017-03-02 16:16:12 UTC,"Disabling GSSAPI Key Exchange in the client config makes it proceed as expected, so that is a workaround."
1669033,2017-03-02 14:23:51 UTC,"Can I get you to try turning off GssapiKeyExchange but leaving on
GssapiAuthentication?"
1669033,2017-03-02 16:35:53 UTC,"Confirmed at Bath, it works without GSSAPIKeyExchange"
1669033,2017-03-01 16:14:19 UTC,"#0  0x00007ffff5b66f38 in _exit (status=255)
   at ../sysdeps/unix/sysv/linux/_exit.c:33
       resultvar = 18446744073709551578
#1  0x00007ffff7fa2f5c in cleanup_exit (i=255) at clientloop.c:2183
No locals.
#2  0x00007ffff7fc1e1f in fatal (fmt=<value optimized out>) at fatal.c:44
       args = {{gp_offset = 8, fp_offset = 48,
           overflow_arg_area = 0x7fffffffc4f0,
           reg_save_area = 0x7fffffffc430}}
#3  0x00007ffff7fdc036 in kexgss_client (kex=0x7ffff824db40) at kexgssc.c:142
       send_tok = {length = 0, value = 0x0}
       recv_tok = {length = 186, value = 0x7ffff825a3b0}
       gssbuf = {length = 140737356520720, value = 0x1}
       msg_tok = {length = 140737356553360, value = 0x7ffff8258890}
       token_ptr = 0x7fffffffc600
       ctxt = 0x7ffff8257210
       maj_status = 851968
       min_status = <value optimized out>
       ret_flags = 0
       klen = <value optimized out>
       kout = <value optimized out>
       slen = 0
       hashlen = <value optimized out>
       strlen = 186
       dh = 0x7ffff8258770
       dh_server_pub = 0x7ffff8257500
       shared_secret = 0x0
       p = <value optimized out>
       g = <value optimized out>
       kbuf = <value optimized out>
       hash = <value optimized out>
       serverhostkey = 0x0
       empty = 0x7ffff7ff1e72 """"
       msg = <value optimized out>
       type = 31
       first = 0
       nbits = 0
       __func__ = ""kexgss_client""
#4  0x00007ffff7fd1bd8 in kex_kexinit_finish (type=<value optimized out>,
   seq=<value optimized out>, ctxt=0x7ffff824db40) at kex.c:320
No locals.
#5  kex_input_kexinit (type=<value optimized out>, seq=<value optimized out>,
   ctxt=0x7ffff824db40) at kex.c:290
       ptr = <value optimized out>
       i = <value optimized out>
       dlen = 1308
       kex = 0x7ffff824db40
#6  0x00007ffff7fd0c83 in dispatch_run (mode=0, done=0x7ffff824dba8,
   ctxt=0x7ffff824db40) at dispatch.c:98
       type = <value optimized out>
       seqnr = 0
#7  0x00007ffff7fadf58 in ssh_kex2 (host=<value optimized out>,
   hostaddr=<value optimized out>) at sshconnect2.c:230
       kex = 0x7ffff824db40
       orig = <value optimized out>
       gss = <value optimized out>
       gss_host = 0x7ffff822a290 ""ms-ssh-rp.dev.ja.net""
#8  0x00007ffff7fa96eb in ssh_login (sensitive=0x7ffff82033a0,
   orighost=<value optimized out>, hostaddr=0x7ffff82033c0,
   pw=<value optimized out>, timeout_ms=-1000) at sshconnect.c:1137
       host = 0x7ffff822a290 ""ms-ssh-rp.dev.ja.net""
       cp = <value optimized out>
       server_user = 0x7ffff82251f0 ""adamb""
       local_user = 0x7ffff8225260 ""adamb""
#9  0x00007ffff7f9f7de in main (ac=<value optimized out>,
   av=<value optimized out>) at ssh.c:904
       i = <value optimized out>
       r = <value optimized out>
       opt = <value optimized out>
       exit_status = <value optimized out>
       use_syslog = -131968416
       p = <value optimized out>
       cp = <value optimized out>
       line = <value optimized out>
       argv0 = <value optimized out>
       buf = ""/home/DEV/adamb/.ssh\000config\000\000\000\000\000\300\320\377\377\377\177\000\000\037\310\345\365\377\177\000\000\310\064\370\367\377\177\000\000\000\000 \2..."
1669033,2017-03-01 16:14:34 UTC,"[adamb@ms-ssh-rp ~]$ ssh -vv ms-ssh-rp.dev.ja.net
OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to ms-ssh-rp.dev.ja.net [212.219.210.74] port 22.
debug1: Connection established.
debug1: identity file /home/DEV/adamb/.ssh/identity type -1
debug1: identity file /home/DEV/adamb/.ssh/identity-cert type -1
debug1: identity file /home/DEV/adamb/.ssh/id_rsa type -1
debug1: identity file /home/DEV/adamb/.ssh/id_rsa-cert type -1
debug1: identity file /home/DEV/adamb/.ssh/id_dsa type -1
debug1: identity file /home/DEV/adamb/.ssh/id_dsa-cert type -1
debug1: identity file /home/DEV/adamb/.ssh/id_ecdsa type -1
debug1: identity file /home/DEV/adamb/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug2: fd 4 setting O_NONBLOCK
debug1: Unspecified GSS failure.  Minor code may provide more information
Server <email address hidden> not found in Kerberos database"
1669052,2017-03-16 08:43:36 UTC,"again. so i see there are more bugs with the launcher. better test to maybe catch more, have a lot of apps pinned (more than a screen so you can scroll the launcher) and then just play with it, resize the launcher, change the icon positions, unpinned apps, pinn apps, it will eventually fail in different ways"
1669054,2019-04-02 18:25:25 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649419"
1669054,2019-04-02 18:25:50 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649420"
1669054,2019-04-10 20:24:28 UTC,"Reviewed:  https://review.openstack.org/649319
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=20c1414945db633ed00c1f19f1f0d163028454d9
Submitter: Zuul
Branch:    stable/stein"
1669054,2019-04-11 04:16:20 UTC,"Reviewed:  https://review.openstack.org/649320
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=76dfb9d0b6cee1bbb553d3ec11139ca99a6f9474
Submitter: Zuul
Branch:    stable/stein"
1669054,2019-04-11 19:21:58 UTC,"Reviewed:  https://review.openstack.org/649325
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=77164128bf5eef53b49547658be2ef902c020207
Submitter: Zuul
Branch:    stable/rocky"
1669054,2019-04-12 05:48:19 UTC,"Reviewed:  https://review.openstack.org/649326
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=31c08d0c7dc73bb2eefc69fa0f014b6478f3d149
Submitter: Zuul
Branch:    stable/rocky"
1669054,2019-04-12 23:21:01 UTC,"Reviewed:  https://review.openstack.org/649362
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9fd4082d7c076146ec314b86e0e4772d0a021712
Submitter: Zuul
Branch:    stable/queens"
1669054,2019-04-17 01:54:38 UTC,"Reviewed:  https://review.openstack.org/649386
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fcd718dcdd3cb7ba46f16ff97ecee068d55c8801
Submitter: Zuul
Branch:    stable/pike"
1669054,2019-04-17 02:06:19 UTC,"Reviewed:  https://review.openstack.org/649387
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=efab235f88ac040ef9654c782236b83ffcb473e3
Submitter: Zuul
Branch:    stable/pike"
1669054,2019-04-26 17:15:44 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1669054,2019-06-06 06:24:40 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1669054,2019-06-18 03:41:34 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1669054,2019-07-10 21:40:22 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1669054,2019-04-02 18:16:35 UTC,"Reviewed:  https://review.openstack.org/647512
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e4c998e57390c15891131205f7443fee98dde4ee
Submitter: Zuul
Branch:    master"
1669054,2019-09-27 09:05:06 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1669054,2019-04-12 23:21:11 UTC,"Reviewed:  https://review.openstack.org/649363
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8f1773a7af273e2739843a804fb4fe718c0a242d
Submitter: Zuul
Branch:    stable/queens"
1669054,2019-04-02 16:23:06 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/649387"
1669054,2019-10-31 20:10:57 UTC,"Reviewed:  https://review.opendev.org/649420
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4b4484f78d967ff6de5c61d0ac66ef62d0a89a89
Submitter: Zuul
Branch:    stable/ocata"
1669054,2019-04-02 15:11:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/649363"
1669054,2019-10-31 20:10:46 UTC,"Reviewed:  https://review.opendev.org/649419
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=730e0e99d274a60f73e0892e9fc41dfb132d9a99
Submitter: Zuul
Branch:    stable/ocata"
1669054,2017-07-28 12:30:16 UTC,This is really a note to self. Moving to Opinion as there are a lot of mights here. :)
1669054,2017-07-28 17:24:08 UTC,"I don't think this is opinion, since if CONF.allow_resize_to_same_host is False and we do a resize then a subsequent rebuild/evacuate, it *will* continue to ignore the original host."
1669054,2019-03-22 20:44:50 UTC,Heh yeah same thing I noticed here:
1669054,2019-03-23 15:34:23 UTC,This has been regressed since Newton:
1669054,2019-03-23 16:05:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/646006"
1669054,2019-03-25 15:37:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647512"
1669054,2019-03-25 15:37:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647513"
1669054,2019-03-25 15:53:48 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/647513
Reason: Squashed into https://review.openstack.org/#/c/647512/."
1669054,2019-03-26 11:11:25 UTC,"Reviewed:  https://review.openstack.org/646006
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=556cf103b22ab6bebecc9d824d6f918cda38fe3e
Submitter: Zuul
Branch:    master"
1669054,2019-04-02 13:25:21 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/649319"
1669054,2019-04-02 13:25:42 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/649320"
1669054,2019-04-02 13:37:37 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649325"
1669054,2019-04-02 13:37:53 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649326"
1669054,2019-04-02 15:10:58 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/649362"
1669054,2019-04-02 16:22:49 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/649386"
1669056,2019-10-07 21:14:38 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.opendev.org/439724
Reason: Hi, I'm going to abandon this by doing an overall project cleanup. Please feel free to reopen this. Thanks."
1669056,2017-03-01 17:18:41 UTC,Example of how to address the problem: https://review.openstack.org/439724
1669060,2017-10-06 14:17:42 UTC,"Hi,"
1669062,2017-03-01 17:43:26 UTC,TODO: Still need to circle back to UOSCI and use tox instead of run_tempest.sh.
1669062,2018-05-03 18:21:40 UTC,"Ryan, has this since been fixed? I know openstack-charm-testing has at least been updated to clone tempest from master for profiles/keystonev3, and use of tox is documented in the o-c-t README."
1669065,2017-03-02 21:40:53 UTC,Is it the reason why 4.4.0.65.69 has disappeared from repository?
1669069,2017-03-02 09:49:49 UTC,"I reported a fix to Debian, linking as soon as I have a bug #."
1669069,2017-03-02 08:10:35 UTC,"I found that this is size dependent, but not in the gigabytes.
This is the first that fails:
$ rm file.lrz; dd if=/dev/zero of=file bs=1 count=64; lrzip -z file
While this still works
$ rm file.lrz; dd if=/dev/zero of=file bs=1 count=63; lrzip -z file"
1669069,2017-03-02 08:19:21 UTC,"Thread 3 ""lrzip"" received signal SIGILL, Illegal instruction.
[Switching to Thread 0x3fffb312f180 (LWP 130922)]
0x00003fffb7f70000 in ?? ()
(gdb) bt
#0  0x00003fffb7f70000 in ?? ()
#1  0x00000000100363f8 in libzpaq::Predictor::predict (this=0x3fffb3113430) at libzpaq/libzpaq.cpp:3140
#2  0x000000001003792c in libzpaq::Encoder::compress (this=0x3fffb3113420, c=<optimized out>)
    at libzpaq/libzpaq.cpp:1409
#3  0x0000000010037c9c in libzpaq::Compressor::postProcess (this=0x3fffb3113360, pcomp=0x0, len=<optimized out>)
    at libzpaq/libzpaq.cpp:1548
#4  0x000000001003826c in libzpaq::compress (in=0x3fffb312e508, out=0x3fffb312e4f0, level=<optimized out>)
    at libzpaq/libzpaq.cpp:1597
#5  0x0000000010038424 in zpaq_compress (c_buf=0x3fffac0008c0 ""zPQ\001\001E"", c_len=0x3fffb312e708,
    s_buf=0x100a3270 """", s_len=<optimized out>, level=<optimized out>, msgout=<optimized out>,
    progress=<optimized out>, thread=<optimized out>) at libzpaq/libzpaq.h:526
#6  0x0000000010014a98 in zpaq_compress_buf (thread=<optimized out>, cthread=0x10092a68,
    control=0x10070c50 <local_control>) at stream.c:184
#7  compthread (data=0x0) at stream.c:1296
#8  0x00003fffb7e58070 in start_thread (arg=0x3fffb312f180) at pthread_create.c:335
#9  0x00003fffb7a73230 in clone () at ../sysdeps/unix/sysv/linux/powerpc/powerpc64/clone.S:96"
1669069,2017-03-02 08:21:41 UTC,"They really do JIT in there with a ""A ZPAQL virtual machine"""
1669069,2017-03-02 08:24:52 UTC,"Found in the code:
const int S=sizeof(char*);      // 4 = x86, 8 = x86-64
if (*(char*)&t!=0x78 || (S!=4 && S!=8))
    error(""JIT supported only for x86-32 and x86-64"");"
1669069,2017-03-02 08:28:13 UTC,Here from the header libzpaq/libzpaq.h
1669069,2017-03-02 08:37:35 UTC,"Even guaranteeing SSE2 is not sure on old machines or some virtual machines.
Usually runtime detection has to be used on those."
1669069,2017-03-02 09:19:48 UTC,"Hmm a simple override of this did not pass down.
So the following did not help."
1669069,2017-03-02 09:22:04 UTC,Well that is CPP
1669069,2017-03-02 09:34:58 UTC,"This is working now just fine:
--- lrzip-0.631/debian/rules    2014-03-28 19:08:25.000000000 +0100
+++ lrzip-0.631/debian/rules    2017-03-02 10:23:30.000000000 +0100
@@ -10,8 +10,13 @@"
1669077,2017-04-28 21:57:33 UTC,os-client-config has its own mind sometimes.  The reason discovery is not performed is because OSC thinks the version was supplied by the user and honors that selection over doing discovery.  We need to get os-client-config to not do it that way...
1669077,2017-09-28 06:58:29 UTC,"Hello Troyer, can we update the os_client_config default.json file or provide a (or DEFAULT_API_VERSION) default value in openstackclient to fix it?"
1669080,2017-06-30 14:06:02 UTC,"This sounds reasonable from a CLI point of view, but I don't recall if keystone roles have a description attribute for both v2 and v3. Adding keystone as a related project."
1669080,2017-07-13 03:00:40 UTC,"In order to implement this in keystone, we'd need a migration to add a new column to the role table. Right now only id, name, domain_id, and extras are persisted in the role table [0]."
1669080,2017-07-13 03:01:59 UTC,"Since we're getting close the Pike release this might be a good thing to fix as soon as Queens opens for development, especially since it requires a database migration."
1669080,2017-07-14 13:35:56 UTC,"Hi m-nitesh,"
1669080,2017-07-17 12:22:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484348"
1669080,2017-07-17 12:38:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484355"
1669080,2017-07-25 17:23:30 UTC,"Targeting this to pike-3, which is this week. If we don't land it by the end of the week, we'll wait for Queens to open for development."
1669080,2017-08-08 16:19:27 UTC,Removing this from pike-3 (which has passed) since it is unlikely to land by the time we have to cut the rc candidate. We'll re-target this work for Queens.
1669080,2018-04-09 20:36:02 UTC,Automatically unassigning due to inactivity.
1669080,2018-09-12 17:56:39 UTC,"Reviewed:  https://review.openstack.org/484348
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=430d7f765a75830ae377545bc57195d38e44e172
Submitter: Zuul
Branch:    master"
1669080,2019-03-21 14:56:32 UTC,This issue was fixed in the openstack/keystone 15.0.0.0rc1 release candidate.
1669080,2020-03-25 11:08:19 UTC,This issue was fixed in the openstack/python-openstackclient 5.1.0 release.
1669086,2017-03-03 00:00:39 UTC,https://review.openstack.org/#/c/439892/
1669086,2017-03-01 22:56:50 UTC,jenkins job builder 2.0.0.0b1 still has the cap but master branch removed it. anyway python-jenkins need to remove the cap too.
1669086,2017-03-08 23:23:50 UTC,"jjb 1.6.2 has been released to include the change.
https://pypi.python.org/pypi/jenkins-job-builder/1.6.2"
1669086,2017-03-08 11:42:08 UTC,pip package of jenkins-job-builder 2.0.0.0b1 on pypi repo is still containing old requirement.txt :
1669086,2017-03-01 19:17:09 UTC,updating jenkins-job-builder to 2.0.0.0b1 seems to fix the issue but the version is not the default latest to install.
1669096,2017-06-29 01:39:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669096,2021-01-07 04:11:42 UTC,4.8 EOL
1669113,2017-03-01 20:26:46 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f4a167ef2e0 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f4a167ec0b2 ""free(): invalid pointer"", action=3) at malloc.c:5004
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3865
 __GI___libc_free (mem=<optimized out>) at malloc.c:2966
 g_hash_table_unref () from /tmp/apport_sandbox_TWrmsK/lib/x86_64-linux-gnu/libglib-2.0.so.0"
1669114,2017-03-01 20:28:55 UTC,"since 1 week i am not able to update my ubuntu 16.04, and it is affecting my work. sometime, when i am working, i need to open a file or a folder, but it is not opening. i need to restart my laptop. i have faced these kind of problems before. i think before 2 years it happened to me, after i upgarded from ubuntu 14 to 16. i waited for a month or 2, i don't really remember, and after that i have received a package to update from ubuntu. after installing the new package and updating ubuntu, everything was amazing.
so now i think i will wait for a month or 2, until someone from ubuntu send me a suitable update package to install it and get rid from the error.
this is my experience with this kind of errors."
1669114,2017-03-06 21:54:18 UTC,"ok here is what i have notice and done:
today and after 3 or 4 days from checking the problem, i have notice that there is a python package installed on my system and were doing a conflict between the linux packages. that is why my ubuntu was not taking any update and everything was failing even the security update.
it was the path of python 2.7 that was changed while installing the python 3.6 package for ubuntu. so after downloading and installing the python 3.6, the ubuntu was not knowing where to install the updates or actually was not knowing where are the packages to be updated.
so when i have returned the path to python 2.7 again as it was by default inside linux (because linux use the python 2.7 for it is packages), the update gone well and i am not facing any errors any more.
thank you guys for everything, i hope i explained the idea for the others is they have similar problem like me."
1669114,2019-04-03 12:14:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669114,2020-07-16 15:41:20 UTC,"(invalid, you changed your /usr/bin/python symlink to point to python3)"
1669120,2019-05-20 18:10:45 UTC,"+1 to general plan.  (I had applied a similar change locally).  Patch tested and merged to 3.2 and above.  Thanks, Remington."
1669120,2019-05-24 18:04:52 UTC,"I have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>"
1669120,2019-04-12 13:04:31 UTC,"And regarding Eva's comment in #7 about the Reporter, there's a separate bug for menus that go off the bottom of the screen: bug 1706415."
1669120,2019-04-11 21:03:38 UTC,"It looks like the height of many of these dropdowns is controlled by ""max-height"" in this CSS class:"
1669120,2019-04-12 13:29:07 UTC,"Here's a branch for the simplest improvement (increase max-height to 400px to match column picker).  I also think this is the best choice, since it matches the frequently used column picker.  If the column picker ever does anything fancier for its height or position, then we should probably match it for other dropdowns.  But until then, this seems a good solution."
1669120,2017-03-01 22:12:46 UTC,"See also related bug 1464767, which started out as another bug, but also addressed some of the points Michele raises here."
1669120,2018-09-14 11:12:19 UTC,"I have confirmed the problem still exists in 3.2 beta sandbox (I have checked e.g. in the Item Status and Copy Buckets interfaces).
I also came across the same problem in the  reporter templates creator interface (see the attached image)."
1669120,2017-03-01 20:39:43 UTC,Actions on the Patron Holds screen would also benefit from more height.
1669128,2019-08-16 02:13:07 UTC,"Reviewed:  https://reviews.mahara.org/10231
Committed: https://git.mahara.org/mahara/mahara/commit/75388eea64ff582695e31555c45985684287d21b
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1669128,2017-03-12 23:18:43 UTC,"Hi,
Just wanted to say that I've been looking at this issue. Can I claim this bug?"
1669128,2019-07-31 00:36:06 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10231"
1669128,2019-08-09 02:44:53 UTC,"Commit hash: b1f1935c1f9a632f7d2bcb04d8b6d184296e076a
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw"
1669135,2017-03-02 17:32:03 UTC,"I guess this could be done as an action on the charm to perform the restart and clearup log files; the replication failure should be detected in the update-status calls, (Unit is out of sync message), which would be a potential call to action to investigate and run the action."
1669137,2017-03-01 22:35:21 UTC,I tried several window managers and none displayed the behaviour you described. The second window always opened on the current workspace/desktop.
1669138,2017-03-02 18:53:27 UTC,This bug was fixed in the package aisleriot - 1:3.22.1-1ubuntu1
1669140,2020-02-26 19:15:28 UTC,"Reviewed:  https://review.opendev.org/708850
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=03dca4bc823c82054869dfaf6925d5e1e068ac51
Submitter: Zuul
Branch:    master"
1669140,2017-03-01 23:04:14 UTC,"You didn't mention what command you're using, but if it's 'nova show' I think you can pass the --wrap option to make it wrap all of the fields. --wrap defaults to 0, or no wrap."
1669140,2017-03-01 23:30:56 UTC,"Ah whoops, yeah it is a `nova show`."
1669140,2017-03-02 19:17:00 UTC,"Yeah, sorry, I was thinking to workaround until other changes are made, --wrap might help you."
1669140,2020-02-20 11:07:12 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/708850"
1669140,2020-04-11 10:48:31 UTC,This issue was fixed in the openstack/python-novaclient 17.0.0 release.
1669141,2017-03-02 04:14:49 UTC,"Reviewed:  https://review.opencontrail.org/29230
Committed: http://github.org/Juniper/contrail-fabric-utils/commit/38258c8de3c81acfe92d6b80c8f8372d7147c246
Submitter: Zuul (<email address hidden>)
Branch:    master"
1669149,2017-03-08 19:16:11 UTC,"On Fri, 3 Mar 2017 18:27:40 +0000
Joseph Salisbury <email address hidden> wrote:"
1669149,2017-03-01 22:00:11 UTC,This change was made by a bot.
1669149,2017-03-03 18:27:40 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1669151,2017-03-03 12:58:27 UTC,"For context, as mentioned the appID in Touch was <pkgname>.<appname>.<revision>. The concept of appID lives on in snappy as snap.$SNAP.<command>. If the goal is to construct anything yourself, the new env var probably shouldn't be SNAP_APP or SNAP_COMMAND since both imply (to me anyway) '<command>' or '$SNAP.<command>'."
1669151,2019-10-01 13:35:16 UTC,"Can you please clarify what is the intended use case of ""appID"". Internally we have the so-called security-tag, which looks like snap.foo.bar. It would be easy for us to convey the new ""id"" but please explain how this would be useful for you in practice."
1669153,2017-03-21 15:42:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1669153,2017-03-21 15:28:19 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1669153,2017-04-24 14:11:40 UTC,This bug was fixed in the package linux - 4.8.0-49.52
1669153,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1669153,2017-03-02 12:51:34 UTC,"> If, due to the nature of the issue you have encountered, you are unable
> to run this command, please add a comment stating that fact and change
> the bug status to 'Confirmed'.
"
1669153,2017-03-01 22:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1669153,2017-03-01 22:08:56 UTC,Posted patch to <email address hidden> .
1669153,2017-03-02 12:52:15 UTC,"The patch in the kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2017-March/082822.html"
1669154,2017-11-30 09:09:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669155,2017-03-02 13:24:06 UTC,Related docs issue: https://github.com/juju/docs/issues/1690
1669156,2020-05-24 16:58:36 UTC,"This is not a shadow bug.  It's either a bug in the graphical login manager, or X, or a terminal driver.  Please re-open if it is still relevant."
1669156,2020-05-24 17:56:14 UTC,Please run the terminal command
1669156,2020-08-03 04:17:23 UTC,[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.]
1669160,2017-04-03 18:28:42 UTC,"Moving to ubuntu-17.05 so it remains on my todo list, I'll get to it immediately after the zesty release."
1669171,2017-03-23 21:36:57 UTC,Looks like we need to add install guides for openSUSE/SLES and Centos/RHEL in addition to Ubuntu in order to get this tag.
1669176,2017-03-14 07:04:49 UTC,"Interestingly running with Juju 2.1, I got ""no model in focus"" error. With Juju 2.2, I get ""permission denied"" as described."
1669176,2017-03-14 04:36:43 UTC,I am not sure what you are trying to do :)
1669176,2017-03-14 14:42:33 UTC,Sure. This was run with the juju 2.1.1 release version (1001 snap rev).
1669176,2017-03-14 03:56:38 UTC,"@Greg Lutostanski (lutostag),"
1669176,2017-03-14 04:28:51 UTC,"Also, according to 'juju help register', once password was prompted for and set, the registration string is voided:"
1669177,2017-11-03 15:24:36 UTC,Syncing task from Mir.
1669177,2017-03-29 02:31:59 UTC,Not invalid for Mir. On second thoughts I'm not convinced that any SDL toolkit bug should ever be able to crash in Mir like this. Mir should stop such crashes from occurring regardless.
1669177,2017-03-20 07:18:22 UTC,To test you can comment out either the SetKeyboadFocus in SDL_mirevents.c or avoid setting pointer confinement in SDL_mirwindow.c.
1669177,2017-03-20 07:14:10 UTC,a mir::protobuf::Void extends from the MessageLite.
1669177,2017-03-20 07:35:42 UTC,Duplicate of bug 1194384 then?
1669177,2017-03-02 01:40:26 UTC,"Nice work, thanks."
1669177,2017-03-01 23:42:22 UTC,Server side stack trace:
1669177,2017-03-01 23:40:52 UTC,"I have found that the problem is caused by line:
result_message->ParseFromString(result->response());
in void mclr::MirProtobufRpcChannel::on_data_available()"
1669177,2017-03-14 20:31:44 UTC,I added additional logs to figure out what happened and here is the output:
1669204,2017-03-02 01:52:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669204,2017-03-02 01:58:33 UTC,"As there a few more forks (but without releases on pypi) keep the original package name without the -ext, please. Once this fork fest is over, and other forks have kept the name, it will probably be the original name again. This particular fork has the -ext at the end of the name presumably in order to publish on pypi."
1669204,2017-03-02 23:55:04 UTC,*** This is an automated message ***
1669204,2017-03-03 09:04:12 UTC,"Brian, this is not a new package and should get a higher priority as it is in Ubuntu now and old and unmaintained software in an existing package."
1669227,2017-10-20 15:01:12 UTC,"Based on the upstream comments, I'm making this fix released for Xenial (which shipped with Jewel); so I think this only impacts trusty (firefly) and UCA hammer releases in kilo."
1669233,2017-03-17 16:59:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669238,2017-03-02 03:33:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/439974"
1669238,2017-03-03 18:31:12 UTC,"Reviewed:  https://review.openstack.org/439974
Committed: https://git.openstack.org/cgit/openstack/cloudpulse/commit/?id=3ae07695e4f9d6db22eeb83b894c49ce3b03de6a
Submitter: Jenkins
Branch:    master"
1669238,2017-03-03 18:42:41 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441289"
1669238,2017-03-07 01:49:05 UTC,"Reviewed:  https://review.openstack.org/441289
Committed: https://git.openstack.org/cgit/openstack/cloudpulse/commit/?id=5c892f075aa437b60f5649af94b949b9230341ba
Submitter: Jenkins
Branch:    stable/newton"
1669240,2017-03-02 03:39:02 UTC,"DISTRIB_ID=""elementary""
DISTRIB_RELEASE=0.4
DISTRIB_CODENAME=loki
DISTRIB_DESCRIPTION=""elementary OS 0.4 Loki"""
1669243,2017-12-04 19:22:16 UTC,Thanks for submitting this. We discussed this in today's ironic meeting [1]. There are enough questions that we would like to see a spec describing the problem and the proposed change.
1669243,2017-04-03 17:34:51 UTC,"Galyna, if this needs an RPC bump, please ping me. I'd like to get the rolling upgrades in first :)"
1669243,2017-03-23 13:14:04 UTC,"Investigating this more, I am not sure about bumping, IMO we could proceed without it"
1669243,2017-03-14 16:04:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445550"
1669243,2017-03-14 11:20:22 UTC,"The reason of failures is the wrong topic (hostname should be passed to server parameter in rpc context, but not to the topic)
So then to resolve this bug RPC API version will need to be bumped (adding new parameter server to be passed to context)"
1669243,2017-11-01 18:16:09 UTC,Not in progress anymore.
1669243,2017-03-03 08:44:16 UTC,[1]: https://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L427
1669243,2017-03-03 08:42:49 UTC,"To fix this problem , one available choice is change the rpc usage like nova[1].
While, according to the discusstion in irc, ironic make heavy use of topic. Maybe, it`s better to not to change it."
1669243,2017-03-02 03:58:25 UTC,"I changed my devstack to using rabbitmq. After deploying, i changed the rpc_backend to zmq, then, most of ironic api were broken. And most of them return the 500 error:"
1669243,2017-03-06 09:28:13 UTC,Checked and met the same error. Thank you for addressing this
1669254,2017-03-02 07:10:37 UTC,Hi sles; thanks for the bug report.
1669254,2017-03-02 21:44:52 UTC,"openSUSE still has /var/log/messages - at least if you install one of the ""normal"" syslog deamons (syslogd, syslog-ng or rsyslog) instead of relying on journald ;-)"
1669257,2018-11-04 21:23:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669257,2020-01-03 00:19:42 UTC,"18.04 still uses Snort 2.9.7.
Current community rules (https://snort.org/downloads/community/community-rules.tar.gz) are incompatible with this version."
1669257,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1669270,2018-02-27 16:20:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669270,2017-05-23 15:58:53 UTC,"ok, the output of 'debconf-show ucf' looks reasonable, so the problem doesn't appear to be with debconf database corruption."
1669270,2017-05-23 11:25:02 UTC,"On Mon, May 22, 2017 at 11:12 PM, Steve Langasek <
<email address hidden>> wrote:"
1669270,2017-05-22 17:42:26 UTC,An error code of '10' from debconf generically means that wrong arguments have been passed.
1669270,2017-05-22 13:04:30 UTC,"Please run sudo nano /var/lib/dpkg/info/grub-pc.postinst, and on the second line that reads ""set -e"", change it to ""set -ex"", then save and exit the editor.  Then run sudo apt-get install -f, and post the output."
1669270,2017-05-22 14:49:48 UTC,"On Mon, May 22, 2017 at 6:34 PM, Phillip Susi <email address hidden> wrote:"
1669270,2017-05-20 07:08:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669270,2017-05-22 15:22:18 UTC,It looks like ucf is failing instead of prompting to update the config file.  I'm not sure why that would fail.
1669276,2017-03-02 15:44:58 UTC,"Reviewed:  https://review.openstack.org/440166
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=9ab31e0d03ff1ed534f6bd757741987a8696e5c8
Submitter: Jenkins
Branch:    master"
1669276,2017-04-12 08:22:04 UTC,This issue was fixed in the openstack/heat 9.0.0.0b1 development milestone.
1669276,2017-03-03 16:19:44 UTC,It seems fix was merged https://review.openstack.org/440166 so marking it as 'Fix Committed'
1669276,2017-03-02 07:25:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440166"
1669276,2017-03-02 10:55:26 UTC,"Reviewed:  https://review.openstack.org/440136
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=42b581486416d50fcb59d192db61660bd71dd1ba
Submitter: Jenkins
Branch:    master"
1669276,2017-03-02 07:05:15 UTC,https://review.openstack.org/#/c/440146/
1669276,2017-03-02 06:54:59 UTC,https://review.openstack.org/#/c/440136/
1669276,2017-03-02 07:08:20 UTC,https://review.openstack.org/#/c/440143
1669276,2017-03-02 06:55:48 UTC,https://review.openstack.org/#/c/440141
1669278,2017-03-02 06:52:09 UTC,"As far as I can tell, this only affects older images, though those images are still published and so their records should be valid."
1669278,2017-07-27 22:07:07 UTC,"This exists in the .qindex.json files for releases that have already been archived to S3.  We've never had to modify content there, so we don't have any tooling to handle it."
1669285,2017-03-06 06:50:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441766"
1669285,2017-05-27 20:41:49 UTC,"Change abandoned by Steven Dake (<email address hidden>) on branch: master
Review: https://review.openstack.org/441766
Reason: Cleaning up the review queue - this work has merged under a different review.  As a result, abandoning this review.  Thanks for the contribution."
1669306,2017-03-06 06:22:04 UTC,"https://code.launchpad.net/~stub/+snap/juju-act has the Launchpad built snaps, which also demonstrate this behaviour."
1669306,2017-03-07 14:36:43 UTC,"I didn't read `confinement: classic` before, this changes everything. The behavior of `classic` is marked as experimental to give us some space to allow changes until we find a common denominator that works for all projects."
1669306,2017-03-02 20:40:45 UTC,"No, its all the same execution environment. Install snap a, works. Install snap b, hangs. Install snap a, works again."
1669306,2017-03-06 06:12:10 UTC,"Per comment #6, there is no environment configuration at all in the wrapper:"
1669306,2017-03-08 13:51:20 UTC,"On Tue, 7 Mar 2017 16:40:06 +0000, Stuart Bishop wrote:

> The apps section of prime/meta/snap.yaml does not mention python3 at
> all:
>
> apps:
>   juju-act:
>     command: command-juju-act.wrapper
>
>
> Setting the command in snapcraft.yaml per above fails to build:
>
> [Errno 2] No such file or directory: '/home/stub/src/juju-
> act/prime/$SNAP/usr/bin/python3'
"
1669306,2017-03-07 16:40:06 UTC,The apps section of prime/meta/snap.yaml does not mention python3 at all:
1669306,2017-03-05 22:14:42 UTC,"Stuart, to get the correct `which python3` result please open the command wrapper that was created for this app entry and export all those entries into the environment."
1669306,2017-03-02 09:08:16 UTC,"This is a snap built from the same source that now fails. I don't know if this is a snapcraft issue, or if one of the python dependencies pulled in by the python plugin is now failing. The only dependency in this Python app is PyYAML."
1669306,2017-03-02 21:04:57 UTC,"The snaps are quite different: http://paste.ubuntu.com/24098150/.
juju_act.py not being in the broken snap certainly doesn't look good?"
1669306,2017-03-02 19:33:19 UTC,Are there differences in the execution environment of the two snaps in question? Was one executed via tmux or screen and the other not? via xterms on the host or ssh -X forwarded terminals? Or console vs terminals?
1669306,2017-03-02 09:05:48 UTC,Here is a working snap. This is the same as the 'juju-act' snap published in the store.
1669306,2017-03-03 05:58:39 UTC,"Sorry, I must have uploaded the wrong fail snap in the confusion."
1669323,2018-01-20 08:03:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1430
1669323,2018-01-18 08:30:48 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1958
1669323,2017-03-02 17:45:57 UTC,"Hello,"
1669323,2017-03-03 13:40:55 UTC,node1:
1669323,2017-03-02 11:48:27 UTC,"Hi there,"
1669323,2017-03-02 11:31:28 UTC,Please attach my.cnf from the 2 nodes (non-garbd). Can you confirm that there is no network issues between the nodes?
1669323,2017-03-02 14:56:48 UTC,It really looks like connection timed out though:
1669329,2017-03-02 20:40:17 UTC,"Why not have it note that it's waiting, and have it queued?"
1669329,2017-03-02 22:42:46 UTC,"As in have snap install queue?  Yeah that would be nicer; I was imagining parity with apt, but the nicer option would be to queue."
1669331,2017-03-03 15:20:13 UTC,"It is controlled via policy as of now -- https://github.com/openstack/ironic/blob/stable/ocata/etc/ironic/policy.json.sample#L6, do you mean it completely on-demand?"
1669331,2017-03-03 15:21:17 UTC,"err, s/do you mean it/do you mean you want it to be/"
1669331,2017-03-03 22:14:46 UTC,"Oh, cool. I didn't know it can be controlled by policy."
1669331,2017-03-06 10:31:29 UTC,"I'm making it a usual bug then, thanks!"
1669337,2017-03-08 12:20:51 UTC,This issue was fixed in the openstack/fuel-ui 11.0.0.0rc2 release candidate.
1669337,2017-03-09 08:48:58 UTC,"Reviewed:  https://review.openstack.org/441762
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=e5df777d2d72dda494a963ae5d9bf02b0575f031
Submitter: Jenkins
Branch:    stable/newton"
1669337,2017-03-07 13:09:46 UTC,"Reviewed:  https://review.openstack.org/442431
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=1befa52126fc94305643f5772d6123271e3b6ccb
Submitter: Jenkins
Branch:    stable/ocata"
1669337,2017-03-06 06:27:41 UTC,"Reviewed:  https://review.openstack.org/434351
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=5eadafc910df612c38e3e8705e4b86d158678e50
Submitter: Jenkins
Branch:    master"
1669337,2017-03-06 06:34:51 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441762"
1669337,2017-03-07 12:39:05 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442431"
1669360,2017-03-13 17:23:16 UTC,"I found that when you change display unis in the Document Properties dialog, the scale factor also changes. Set the scale factor in the same dialog to 1 when you change mm to px and you should be able to change ""inkscape:radius"" in proper units."
1669360,2017-03-14 13:38:10 UTC,"Like a charm!
Thank you for the clue."
1669360,2017-03-20 20:42:16 UTC,I thinks this behavior is result of how Sodipodi treated the coordinate system. Inkscape inherited this 'cartesian coordinates' where the Y axis is upward in contrast to SVG standard and other software where Y axis is downward.
1669369,2017-03-08 12:20:15 UTC,This issue was fixed in the openstack/fuel-qa 11.0.0.0rc2 release candidate.
1669369,2017-03-03 12:51:45 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441105"
1669369,2017-03-03 14:00:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441138"
1669369,2017-03-03 14:00:50 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441139"
1669369,2017-03-03 14:11:06 UTC,"Reviewed:  https://review.openstack.org/441105
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=a769b13698dff2c78d66aa199d29937e0f294c56
Submitter: Jenkins
Branch:    stable/newton"
1669369,2017-03-07 10:08:32 UTC,"Reviewed:  https://review.openstack.org/441139
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=0ae0e11f8c01419003fcb4da7d7a4c2ab23a868c
Submitter: Jenkins
Branch:    stable/ocata"
1669369,2017-03-07 10:08:40 UTC,"Reviewed:  https://review.openstack.org/441138
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=f672044bc6f0789d56f93417ded8c57af1654756
Submitter: Jenkins
Branch:    master"
1669369,2017-04-10 09:44:15 UTC,Verified on Newton #1556 iso.
1669371,2020-08-12 21:20:34 UTC,This bug was fixed in the package xprintidle - 0.2-12
1669371,2018-05-09 20:00:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669377,2017-03-02 11:50:45 UTC,"# systemctl cat pdns-recursor.service
# /lib/systemd/system/pdns-recursor.service
[Unit]
Description=PowerDNS Recursor
Documentation=man:pdns_recursor(1) man:rec_control(1)
Wants=network-online.target
After=network-online.target"
1669392,2017-03-02 12:26:03 UTC,"The same problem is for modal, which is opened when you try run this workflow without tasks."
1669400,2017-03-02 13:04:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440536"
1669400,2020-03-18 07:53:28 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/440536
Reason: This is a pretty old patch with negative review. Feel free to restore it (or ask gibi on irc to restore it) if you still working on it."
1669415,2017-03-02 13:16:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440545"
1669415,2017-03-07 12:04:29 UTC,"Fix proposed to branch: stable/1.0
Review: https://review.openstack.org/442410"
1669415,2017-03-07 12:04:38 UTC,"Reviewed:  https://review.openstack.org/440545
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-influxdb-grafana/commit/?id=4b5174789dc9e63038e3db04465250db39f40cd2
Submitter: Jenkins
Branch:    master"
1669415,2017-03-07 12:04:56 UTC,"Reviewed:  https://review.openstack.org/442410
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-influxdb-grafana/commit/?id=8b0f534fd2e5ae2db08234b1e8892791c55e1c51
Submitter: Jenkins
Branch:    stable/1.0"
1669427,2017-03-02 13:47:06 UTC,I forgot that I'd copied the .toc & .bin files to another directory. I then used the .toc file in that directory as the Image file to Brasero. Silly me! What confused me was the default creation of a .toc file where Brasero used to create a .cue file by default.
1669431,2017-03-03 14:31:05 UTC,According to Marco it should be https://github.com/marcoceppi/wordpress-demo
1669432,2017-03-06 15:20:47 UTC,The second issue is bug 1670390.
1669432,2017-03-06 10:47:40 UTC,Looks like you have multiple bugs in a single report. Not good.
1669432,2017-03-06 10:50:06 UTC,"Anyway, will investigate the one about kate toolbar buttons."
1669432,2017-03-06 13:51:40 UTC,This is the first bug: Bug 1670361
1669432,2017-03-06 13:56:00 UTC,thanks Daniel :D subscribed
1669437,2017-03-02 16:44:04 UTC,"This is mentioned in item one of the release notes:
https://peppermintos.com/release-notes/"
1669445,2020-11-09 21:30:45 UTC,"+1 to functionality for ""Removal"" of available payment types by disabling their use; this is a common request from libraries"
1669445,2019-12-11 20:51:02 UTC,"PINES would like to add a payment type of ""Unrecoverable Debt"" or something like this. When libraries write off debt after X number of years, they want to be able to run reports on what was written off."
1669445,2019-02-05 23:23:13 UTC,"We would like to add a new payment type ""Debit"""
1669445,2018-10-09 17:40:40 UTC,Chris-
1669445,2017-03-02 14:40:43 UTC,"For clarification about the database layer, the different payment types are not views but child tables.  The reason to use table inheritance is to provide for the differing fields of different payment types."
1669450,2017-03-02 14:37:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440603"
1669450,2017-03-21 05:02:56 UTC,"Reviewed:  https://review.openstack.org/440603
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8be1ec5e706b07b47f13b8c97c70327b25b09552
Submitter: Jenkins
Branch:    master"
1669450,2017-03-28 23:46:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/451117"
1669450,2017-03-29 00:47:43 UTC,Resetting the status to New due to the revert.
1669450,2017-03-29 00:50:16 UTC,"Reviewed:  https://review.openstack.org/451117
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=343cbd19b5e4c17c4c4e86fb6ae86cfde95cb84b
Submitter: Jenkins
Branch:    master"
1669450,2017-04-13 16:56:10 UTC,This issue was fixed in the openstack/horizon 12.0.0.0b1 development milestone.
1669455,2019-07-10 21:35:14 UTC,This issue was fixed in the openstack/os-testr 1.1.0 release.
1669455,2017-03-02 14:43:00 UTC,https://review.openstack.org/#/c/373428/
1669455,2017-03-02 19:23:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/440771"
1669455,2017-03-06 23:11:19 UTC,"Change abandoned by Ken'ichi Ohmichi (<email address hidden>) on branch: master
Review: https://review.openstack.org/440771"
1669455,2017-11-25 19:52:51 UTC,I proposed a patchset that fixes the issue in os-testr library: https://review.openstack.org/#/c/522768/
1669455,2020-02-25 10:21:12 UTC,The issue got fixed in os-testr
1669456,2017-03-02 14:59:59 UTC,"Here are the trimmed down logs from https://ci.lscape.net/job/landscape-system-tests/5413/. The entire logs are available at:
https://private-fileshare.canonical.com/~fginther/landscape/lp-1669456/lst-5413/all-logs.tar.gz"
1669456,2017-03-02 23:24:29 UTC,"Francis,"
1669456,2017-03-06 17:49:37 UTC,"David,"
1669456,2018-11-13 02:49:08 UTC,Same issue. Is there a solution to this? @Francis
1669458,2017-03-03 06:37:14 UTC,That's probably the best way to do it with the current code - but that's only because i've never had to use requests with chunks so i'm not sure what it is supposed to look like. Unfortunately you also have to inherit that closed hack.
1669463,2017-03-02 15:25:43 UTC,(note: this is using simple-scan-3.22.0.1-1.fc25.x86_64 / gtk3-3.22.8-1.fc25.x86_64)
1669466,2017-03-03 11:58:14 UTC,"Reviewed:  https://review.openstack.org/440604
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=9666454132d66fdcf916b8c578fae138a6b2aefe
Submitter: Jenkins
Branch:    master"
1669466,2017-03-03 14:08:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441141"
1669466,2017-03-08 16:17:54 UTC,"Reviewed:  https://review.openstack.org/441141
Committed: https://git.openstack.org/cgit/openstack/ironic-inspector-specs/commit/?id=2c937330a86d8f29dcd2723de00d6c6f79aea9db
Submitter: Jenkins
Branch:    master"
1669468,2017-05-02 19:38:17 UTC,Yeah still showing up:
1669468,2019-08-12 14:50:09 UTC,"Change looks good, I will work on a client side logging patch set aimed to make debugging this easier in the future. I feel like this could have been an easier debug with some better logs."
1669468,2019-08-10 05:46:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675721"
1669468,2019-08-09 16:04:13 UTC,Patch here: https://review.opendev.org/#/c/675652/
1669468,2019-08-09 15:46:17 UTC,This might have been the regression:
1669468,2019-08-09 15:30:46 UTC,Yeah I agree with the conclusion in comment #18.
1669468,2019-08-09 10:44:50 UTC,"Not sure whether this is really the same issue still or if we should rather have a new bug for that, but the novnc config in tempest-multinode-full looks wrong to me."
1669468,2019-08-08 18:00:20 UTC,It looks like the request that fails is not supported in all microversions.
1669468,2019-08-08 16:25:45 UTC,"This bug is still prevalent in most Zuul checks and is a burden to developing teams. I will try to do some debugging and logging in Devstack to get some more information. If this is a Nova defect, I hope that the data I get from these logs will help us all work towards a solution."
1669468,2019-08-06 21:31:49 UTC,Still seeing this:
1669468,2017-05-03 06:42:32 UTC,Hmm... that piece stands out:
1669468,2017-05-02 19:25:49 UTC,"It's still hitting master and stable, including non-multinode jobs. Example: http://logs.openstack.org/27/461827/1/check/gate-tempest-dsvm-py35-ubuntu-xenial/6805498/logs/testr_results.html.gz"
1669468,2017-03-22 08:53:20 UTC,No hits in logstash after https://review.openstack.org/#/c/448078/1 merged. => resolved
1669468,2017-03-21 13:02:43 UTC,An attempt to fix the order of localrc variables for the subnode: https://review.openstack.org/#/c/448078/1
1669468,2017-03-21 12:38:24 UTC,"Change https://review.openstack.org/#/c/444164/6 didn't solve it completely.
The VNC settings are not complete. The controller node (with compute service)
is set up correctly:"
1669468,2017-03-10 09:08:29 UTC,Fix: https://review.openstack.org/#/c/444164/
1669468,2017-03-09 09:39:05 UTC,"Ah, good find, I was just about to start looking into this myself."
1669468,2017-03-09 09:08:07 UTC,"Michelle Mandel figured it out, all credits to her, I'm only summarizing things here:"
1669468,2017-03-07 11:57:08 UTC,I tried to brute force it on a single node system:
1669468,2017-03-02 15:28:37 UTC,The failing tempest test got added with https://github.com/openstack/tempest/commit/1f87a5611a983acac2208c3e0ba07eee75fe9a51 and merged 2017-02-03 16:39:00
1669468,2017-03-02 15:19:37 UTC,http://logs.openstack.org/38/431038/3/check/gate-tempest-dsvm-neutron-multinode-full-ubuntu-xenial-nv/5e1d485/console.html#_2017-02-21_06_42_10_010507
1669468,2017-03-02 15:17:52 UTC,"This might have started before 2/21, logstash only goes back 10 days."
1669468,2017-03-02 15:16:33 UTC,The only novnc related merge I found in that timeframe is https://github.com/openstack/nova/commit/b726f2553c3eebdc4ab5753a45a99724e952b4ac but that merged a few hours after the first hit.
1669468,2019-08-12 16:49:45 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/675652
Reason: https://review.opendev.org/#/c/675721/ works."
1669468,2019-08-12 22:00:04 UTC,"Reviewed:  https://review.opendev.org/675721
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=0a3288c1b40a4338df351a3fef9a346e78e12191
Submitter: Zuul
Branch:    master"
1669469,2017-03-02 19:46:59 UTC,I'd like to add this log:
1669469,2017-03-02 19:46:00 UTC,apport information
1669469,2017-03-03 18:18:39 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1669469,2017-03-02 19:46:02 UTC,apport information
1669469,2017-03-04 15:41:26 UTC,"Good afternoon Joseph,"
1669469,2017-03-02 19:45:45 UTC,apport information
1669469,2017-03-04 16:08:54 UTC,"Here is what I've done:
- Installed the 4.10 mainline kernel.
- Completelly removed any nvidia-related packages, removed the graphic-drivers ppa.
- Rebooted, installed the nvidia 367 driver.
- Rebooted."
1669469,2017-03-04 16:22:35 UTC,Very sorry for the noise. I've tried something else:
1669469,2017-03-05 23:20:27 UTC,Small update: installing 16.10 fresh but without the `yakkety-proposed` repo seems to be functional along with the nvidia drivers.
1669469,2017-03-02 19:45:58 UTC,apport information
1669469,2017-03-04 15:46:09 UTC,Re: I'm installing the 4.10 one with the most recent upload timestamp. Will report back ASAP. Thanks for your help!
1669469,2017-03-02 19:45:56 UTC,apport information
1669469,2017-03-02 19:45:39 UTC,apport information
1669469,2017-03-02 19:45:53 UTC,apport information
1669469,2017-03-02 16:00:56 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1669469,2017-03-02 19:45:35 UTC,apport information
1669469,2017-03-02 19:45:37 UTC,apport information
1669469,2017-03-02 19:45:41 UTC,apport information
1669469,2017-03-02 19:45:54 UTC,apport information
1669469,2017-03-02 19:45:48 UTC,apport information
1669469,2017-03-02 19:45:50 UTC,apport information
1669469,2017-03-02 19:45:51 UTC,apport information
1669469,2017-03-02 19:45:43 UTC,apport information
1669470,2019-05-22 12:03:22 UTC,"The problem described in the bug is XUL specific and does not apply to web staff client.
Both downloading CSV  list and printing the full grid in the web staff client grid interfaces resulted with no encoding problems (Confirmed in Evergreen 3.1.4 and 3.3.0, Czech localization)."
1669471,2017-03-02 18:05:08 UTC,"I added snapcraft because the revoke-key command should be added. I think this should be high priority.
On the store side, the email should not mention revoke-key until it is implemented."
1669476,2017-03-02 15:34:42 UTC,"the spec says ""if no content is provided, content will match the plug"". I guess changing this and making it mandatory is a backward compatibility breakage and isn't desired."
1669476,2019-10-01 21:21:40 UTC,"I'm marking this as fix released. There was a brief moment, IIRC, when this was broken but that has been fixed quickly."
1669488,2017-04-27 00:28:10 UTC,"I fix commenting the line vt_handoff=""1"" in the file /etc/grub.d/10_linux"
1669490,2017-03-07 16:59:35 UTC,From DpkgTerminalLog.txt:
1669499,2019-12-18 17:17:39 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/mitaka
Review: https://review.opendev.org/442524
Reason: This repo is retired now, no further work will get merged."
1669499,2017-03-20 15:39:59 UTC,"Reviewed:  https://review.openstack.org/445418
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=fcb333bb5b97c2b3098fdba22677c3a5ebd562d2
Submitter: Jenkins
Branch:    stable/ocata"
1669499,2017-03-14 10:37:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/445418"
1669499,2017-03-09 12:03:51 UTC,"Reviewed:  https://review.openstack.org/442526
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=29988c78e98b6026b1315ea710938298d0d93b0f
Submitter: Jenkins
Branch:    stable/newton"
1669499,2017-03-07 14:27:14 UTC,"Reviewed:  https://review.openstack.org/440666
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=892894bfb534277642d91ad130515ca8465de582
Submitter: Jenkins
Branch:    master"
1669499,2017-03-07 14:33:08 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/442524"
1669499,2017-03-02 16:20:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440666"
1669499,2017-03-07 14:33:34 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/442526"
1669502,2017-03-02 18:51:02 UTC,"Confirmed in 2.12 in Item Buckets, both in Pending Copies and Bucket View."
1669502,2018-01-04 21:05:10 UTC,Also confirmed in 3.0.2
1669502,2018-04-25 22:25:50 UTC,Also confirmed in 3.1
1669502,2018-09-10 19:04:24 UTC,"Quick question here: should the Call Number/Volume column just be removed, since there is already a Call Number column?"
1669517,2017-03-02 17:31:55 UTC,"First of all, This is extremely wrong:"
1669517,2018-03-17 03:38:06 UTC,In package 'apt' 1.6~beta1 from Kubuntu Bionic Beaver Beta1 (18.04) :
1669517,2020-06-25 16:00:04 UTC,"We will not be changing the behavior here. apt-key del working if they key was not present in the keyring is important to maintain, so that we do not break the maintainer scripts using it (which should be tested, and should be the only users of this)."
1669519,2017-11-17 00:13:07 UTC,"Bill,"
1669519,2017-11-17 22:00:58 UTC,"Hi Kathy, bug #1694058 is close (and will come in handy regardless), but it doesn't cover part of the desired use case, specifically tying the feature to recipient groups instead of having a blanket permission.  The goal is for staff who traditionally have minimal permissions to have this ability but only for select recipient groups."
1669519,2017-11-17 22:26:29 UTC,"Bill,"
1669519,2017-11-20 16:13:05 UTC,"Mike, yes I think using a permission to anoint the recipient would work fine."
1669524,2017-11-03 15:24:39 UTC,Syncing task from Mir.
1669524,2017-03-23 17:47:35 UTC,"I don't see us respecting requests like ""Always on top"" coming from the apps, better to handle that internally in the shell, allowing to keep consistency between apps."
1669524,2017-03-24 11:56:34 UTC,I think there are distinct cases here:
1669524,2017-04-06 17:38:38 UTC,"Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.28.0"
1669524,2017-07-10 19:53:54 UTC,This bug was fixed in the package mir - 0.27.0+17.10.20170630-0ubuntu1
1669524,2017-03-03 17:37:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669524,2017-03-03 01:32:28 UTC,The 'Move' part is bug 1420334.
1669524,2017-07-18 04:39:14 UTC,The fix released in Mir 0.27 covers the API for only one of the three functions mentioned.
1669524,2017-03-30 08:26:20 UTC,The branch that landed was only part of the solution to one of the problems
1669524,2017-03-23 17:43:18 UTC,Should these even be managed by GTK? Shouldn't Unity8 react to Alt+RightClick / Alt+Space instead?
1669524,2017-03-30 06:58:13 UTC,"Fix committed into lp:mir at revision 4129, scheduled for release in mir, milestone 0.27.0"
1669524,2017-03-23 17:45:15 UTC,"Right click on client-side decoration should be similar to dragging on client-side decoration, an event forwarded from the app back to the shell?"
1669525,2017-03-03 02:38:51 UTC,I think it all went south here:
1669527,2017-03-28 00:12:51 UTC,"@nega, is there a reason you submitted a tracker request (it seems mostly dead, tbh) rather than a normal Debian bug?"
1669527,2017-03-24 18:01:21 UTC,Upstream report: https://alioth.debian.org/tracker/index.php?func=detail&aid=315677&group_id=30018&atid=100031
1669527,2017-03-02 20:30:37 UTC,"The attachment ""minicom_runscript.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1669527,2017-03-03 08:47:03 UTC,"Hi nega,
Thank you so muhc for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue."
1669560,2017-04-19 20:51:40 UTC,This has been fixed in the latest 3056 build.
1669563,2017-05-23 17:58:10 UTC,Adding link to related bug 1679309.
1669565,2017-03-02 19:44:59 UTC,"Typo in the title, sorry I didn't see it"
1669578,2017-03-02 20:34:22 UTC,"I'm building a patched glibc now with the two patches we'd like included in Ubuntu.
Once that's built and tested, I'll attach the debdiff."
1669578,2017-05-05 08:11:00 UTC,"I had to tweak the upstream commits, because they weren't applying on top of Debian changes, and uploaded  the following in my ppa.
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/7773744/+listing-archive-extra"
1669578,2017-05-05 10:40:03 UTC,This version of screen doesn't work in containers for me anymore.
1669578,2017-05-05 11:34:49 UTC,"On Fri, May 5, 2017 at 12:40 PM, Christian Brauner
<email address hidden> wrote:

> This version of screen doesn't work in containers for me anymore.
"
1669578,2017-05-05 14:57:49 UTC,I don't think we should upload without having retro-compatibility with older and still supported Ubuntu releases.
1669578,2017-03-02 20:29:04 UTC,Upstream threads: https://sourceware.org/cgi-bin/search.cgi?q=ttyname+and+ttyname_r&cmd=Search%21&form=extended&m=all&ps=10&fmt=long&wm=wrd&sp=1&sy=1&wf=2221&type=&GroupBySite=no&ul=%2Fml%2Flibc-alpha%2F%25
1669578,2017-05-05 17:04:18 UTC,">If you're referring to screen . The screen version right now with my
>compat-layer patch applied
>should be fully backwards compatible.
"
1669578,2017-05-05 17:41:53 UTC,"On Fri, May 05, 2017 at 05:04:18PM -0000, LocutusOfBorg wrote:

> >If you're referring to screen . The screen version right now with my
> >compat-layer patch applied
> >should be fully backwards compatible.
>
> so, you mean, it didn't work before and still doesn't work with older
> glibc?
"
1669578,2017-05-09 16:28:44 UTC,"@Christian, I sponsored it, but it fails the testsuite
http://autopkgtest.ubuntu.com/packages/screen"
1669578,2017-05-09 18:51:35 UTC,"@LocutusOfBorg, thanks for sponsoring I'm looking into it."
1669578,2017-05-09 21:57:35 UTC,"Hm, the test all pass locally for me"
1669578,2017-05-02 14:54:18 UTC,"@LocutusOfBorg, can you please tell me exactly what you need? From looking at"
1669578,2017-05-10 07:56:12 UTC,"I did get the same result (pbuilder artful clean environment)
I also did try to reproduce autopkgtestsuite in an lxc container and the test has failed"
1669578,2017-05-10 14:37:10 UTC,"@LocutusOfBorg, the patch I appended is applicable directly to the deb source used in the package."
1669578,2017-05-10 14:45:27 UTC,Patch send to upstream as well.
1669578,2017-05-10 15:00:49 UTC,lets see if now this bug gets closed :)
1669578,2017-05-10 15:48:17 UTC,This bug was fixed in the package screen - 4.5.1-3ubuntu2
1669578,2017-05-10 18:06:11 UTC,yeah :)
1669578,2017-05-10 20:06:27 UTC,So the screen testsuite I wrote 2.5 years ago actually found a bug? Cool! :-)
1669578,2017-05-10 21:11:44 UTC,"Wohoo, great job gentleman. :)"
1669578,2018-02-23 18:31:00 UTC,"Hello,"
1669578,2018-02-23 20:58:36 UTC,Here's a possible fix. I tested it on bionic and it seems it works. For my xenial machines I had to workaround it disabling completely the check because the glibc there doesn't behave the same way.
1669578,2018-02-27 10:14:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669578,2018-05-14 12:34:05 UTC,@Jose Manuel Santamaria Lema (panfaust)
1669578,2017-05-10 14:36:42 UTC,"@LocutusOfBorg, thanks for taking a close look at this. Found the bug. I'm appending a patch that fixes it and makes the autopkgtestsuite pass for me!"
1669578,2017-05-02 14:43:19 UTC,"@LocutusOfBorg, I can give you a screen 4-5.1-3 compatible patch based on the Debian package.
One thing to note is that even my compat-layer patch will be of no help once {Debian,Ubuntu} breaks the message protocol which they eventually *will* have to do. Upstream screen uses at least message version 5 whereas {Debian,Ubuntu} use message version 2. Once you bump the message version previous screen versions will break. But updating the message protocol will be unavoidable in the long run. So you should consider warning users and start breaking backward compatibility at some point in the near future. :)"
1669578,2017-05-05 15:20:03 UTC,"On Fri, May 5, 2017 at 4:57 PM, LocutusOfBorg
<email address hidden> wrote:

> I don't think we should upload without having retro-compatibility with
> older and still supported Ubuntu releases.
"
1669578,2017-04-23 12:24:03 UTC,I sent a patch to musl upstream to align them with glibc. The patch is merged: https://git.musl-libc.org/cgit/musl/commit/?id=e1232f5b5185e8f337806841018369407e32e77d .
1669578,2017-03-02 23:05:24 UTC,"stgraber@dakara:~$ lxc exec zesty bash
root@zesty:~# tmux
lost server
root@zesty:~# tty
not a tty
root@zesty:~# echo $?
0
root@zesty:~# dpkg -i *.deb
(Reading database ... 26464 files and directories currently installed.)
Preparing to unpack libc-bin_2.24-7ubuntu3_amd64.deb ...
Unpacking libc-bin (2.24-7ubuntu3) over (2.24-7ubuntu2) ...
Preparing to unpack libc6_2.24-7ubuntu3_amd64.deb ...
Unpacking libc6:amd64 (2.24-7ubuntu3) over (2.24-7ubuntu2) ...
Setting up libc6:amd64 (2.24-7ubuntu3) ...
Setting up libc-bin (2.24-7ubuntu3) ...
Processing triggers for man-db (2.7.6.1-1) ...
root@zesty:~# tty
/proc/self/fd/0
root@zesty:~# echo $?
0
root@zesty:~# tmux
[exited]
root@zesty:~#"
1669578,2017-03-02 23:08:24 UTC,"For screen, we'll need to fix their own checking logic a bit but we'll work on that patch and send it upstream (and have it also deal with just getting ENODEV while we're at it)."
1669578,2017-03-20 16:31:40 UTC,"After discussing this on IRC with Adam, Ubuntu will only include the upstreamed patch and we'll instead resort on patching all affected downstream pieces of software to deal with the unfortunate new glibc behavior."
1669578,2017-03-20 16:34:02 UTC,Adam will take care of doing an upload for Ubuntu 17.04 with 5e9a4f378c8607c2ae1aa465436af4321db0e23 included.
1669578,2017-05-02 10:22:27 UTC,"@cbrauner, do you have a patch that needs sponsoring?
We are discussing merging 4.5.1-3 from Debian experimental, but your patch can't apply"
1669578,2017-03-22 18:11:48 UTC,"Upstream screen patch:
https://lists.gnu.org/archive/html/screen-devel/2017-03/msg00013.html"
1669578,2017-03-24 13:40:34 UTC,"Fix for screen merged upstream:
https://lists.gnu.org/archive/html/screen-devel/2017-03/msg00014.html"
1669578,2017-03-25 11:26:47 UTC,This bug was fixed in the package screen - 4.5.0-3ubuntu1
1669578,2017-03-28 17:56:46 UTC,"The fix does not seem to work, it just changes the error message to ""Cannot open your terminal '' - please check."" for me.
The reason seems to be that the patch relies on attach_fd to be set by code that's inside an ifndef NAMEDPIPE block, which isn't being compiled for the ubuntu package.
That ifndef has been removed from upstream code in http://git.savannah.gnu.org/cgit/screen.git/commit/?id=d965ff1d92e2bd57d24b68cfbd6990486024baa3 almost 2 years ago, but that apparently hasn't landed in the ubuntu package yet."
1669578,2017-03-28 20:10:27 UTC,"Hi Michael,"
1669578,2017-03-28 20:44:20 UTC,"So aside from the Ubuntu package being outdated (The codebase has indeed changed massively.) the patch we need to get screen working properly is way more intrusive then originally thought and there might even be the case that we have to do some additional lower-level plumbing in the kernel or glibc to get this working. In short, screen tries to perform various operations on the corresponding /dev/pts/<n> paths that the symbolic links under /proc/self/fd/<n> point to and it is not clear whether we can support all of that by just using the symlinks themselves."
1669578,2017-03-31 19:30:59 UTC,"Here's a patch for screen that got things working for me. I've tested screen startup and various ways of attach (screen -r, screen -rx, and screen -rxD). Would be nice if people are able to test this. So if we could get it into proposed that be +1. The patch in its current form is directly applicable to the screen-4.5.0 Ubuntu sources. Once we consider it to be fine I will prepare a patch for master and sent it out to upstream."
1669578,2017-03-20 16:35:15 UTC,And my team will take care of distro patching screen and tmux to work with this.
1669578,2017-04-02 20:38:06 UTC,Here's an updated version of the patch and a comment explaining in a little more detail what is happening:
1669578,2017-04-01 13:06:46 UTC,I'll likely add another patch to this soon to handle some more corner-cases.
1669578,2017-04-18 15:33:49 UTC,An upstream-compatible version of 0001-add-compat-layer-to-handle-both-fifos-and-sockets.patch is now merged upstream into screen v4. See https://lists.gnu.org/archive/html/screen-devel/2017-04/msg00023.html .
1669578,2017-04-08 01:48:16 UTC,This bug was fixed in the package glibc - 2.24-9ubuntu2
1669578,2017-04-07 17:19:58 UTC,Updated version of fifo-socket-compat patch that removes left-behind debugging statement.
1669578,2017-04-07 11:41:32 UTC,I tested the screen-fifo-socket compatibility patch here https://asciinema.org/a/111692 .
1669578,2017-04-07 11:40:21 UTC,"So, Stéphane brought to my attention that we're not including the patch because it switches screen to use sockets instead of fifos and thus makes it impossible to switch to existing fifo-based screen sessions. I've written a patch that adds a compatibility layer to support both fifo-based and socket-based screen sessions. The idea is to only re-use existing fifo-sessions but never create new ones. All new screen sessions will be socket-based."
1669578,2017-05-05 11:37:28 UTC,"On Fri, May 5, 2017 at 1:34 PM, Christian Brauner
<email address hidden> wrote:

> On Fri, May 5, 2017 at 12:40 PM, Christian Brauner
> <email address hidden> wrote:
>> This version of screen doesn't work in containers for me anymore.
>
> @LocutusOfBorg, nevermind I tested this on Xenial which doesn't seem
> to come with a version of glibc the path that Serge and I wrote. The
> screen version you built with my patches included work on patched
> glibc versions inside containers. From my testing with the version you
> build including my patches attaching to older fifo-based screen
> sessions works and new ones are all socket-based. Thanks!
"
1669578,2017-04-06 08:32:05 UTC,The tmux patch is now also upstream.
1669578,2017-04-05 12:41:05 UTC,Since the Ubuntu screen package was synced with Debian yesterday the attached patch does not apply cleanly anymore. So here's a new version of it that also is much closer to what I've pushed upstream.
1669578,2017-04-04 19:02:54 UTC,This bug was fixed in the package screen - 4.5.0-5ubuntu1
1669578,2017-04-04 14:16:28 UTC,About the tmux patch. Nicholas plans to merge a patch that is nearly identical into tmux master sometime next week but this might be too late for final freeze.
1669578,2017-04-06 08:33:46 UTC,"The screen patch is now also upstream http://git.savannah.gnu.org/cgit/screen.git/commit/?id=565b8901cad828d921038cd6235501c42d1c9a32 . @stgraber, did you get around to pushing to to the archive as well so that we can land this in zesty?"
1669578,2017-04-04 14:15:07 UTC,Here's a patch for the current tmux version of Ubuntu. We should get this sorted before this Thursday.
1669582,2018-04-09 17:15:28 UTC,"this is still present in linux mint 18.3 sylvia out of the box. one thing i do not have is a swap file/partition but have 16gb ram, amd radeon hd6670"
1669594,2017-04-14 22:00:14 UTC,"@Harald, possibly, but we already have this behavior that we should fix before we figure out if it should be represented in the API."
1669594,2017-03-08 09:54:24 UTC,I wonder if the DHCP agent is the correct place to implement them. Hidden from the end user. I don't like it.
1669594,2017-06-05 11:21:38 UTC,This change closes this issue.
1669596,2017-03-03 10:28:02 UTC,Пипетка никак не должна мешять Ctrl+Z. Она не поглощает ивенты. У меня все работает :(
1669596,2017-03-03 19:24:35 UTC,"Конечно не должна мешять Ctrl+Z...  но она появляется раньше, чем сработает
что-то другое, пока заметил это только в режиме кисти. В целом не смог
добиться выполнения ни одной задачи с использованием контролов (прав/лев).
У меня на сочетаниях LCTR+META, CTR+MENU , были назначены 1я и 2 я
раскладки, специально отключил и перегрузился. Заметил так же, что
установленное META+Я так же не срабатывает если перед этим переключиться на
Колемак и иногда на другие.. никакой строгой закономерности я не обнаружил.
Повторяемость тоже не стабильная. В системе и других программах на Ctrl+*
много чего висит, всё работает.
Удалил,qwerty (была третьей) из системы (в манджаро-дипин так решалось неск
проблем) - получил отказ undo в обоих раскладках.(не надолго)  Похоже
как-то связано с ними. Настройки xmodmap, через стандартное окно с галками
в MATE."
1669596,2017-03-03 22:25:23 UTC,Добрый вечер!
1669601,2017-03-02 22:39:57 UTC,"StacktraceTop:
 tracker_db_interface_lock (iface=0x0) at tracker-db-interface-sqlite.c:1436
 tracker_db_interface_execute_vquery (db_interface=0x0, error=0x7f294142ad50, query=0x55b81700b789 ""PRAGMA wal_checkpoint"", args=0x7f294142ac70) at tracker-db-interface-sqlite.c:2304
 tracker_db_interface_execute_query (interface=interface@entry=0x0, error=error@entry=0x7f294142ad50, query=query@entry=0x55b81700b789 ""PRAGMA wal_checkpoint"") at tracker-db-interface.c:41
 tracker_store_wal_checkpoint () at /home/carlos/Source/gnome/tracker/src/tracker-store/tracker-store.vala:254
 tracker_store_checkpoint_dispatch_cb (task=<optimized out>) at /home/carlos/Source/gnome/tracker/src/tracker-store/tracker-store.vala:288"
1669601,2017-05-14 23:06:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669608,2017-07-05 13:24:28 UTC,"delete_stack used to always use cast, and now it looks in the code like it always uses call."
1669608,2017-07-05 14:42:29 UTC,"No, it needs to return some data in a similar format to what handle_update() does:"
1669608,2017-09-29 08:50:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/508443"
1669608,2017-10-05 13:10:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509769"
1669608,2017-10-08 17:04:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/510359"
1669608,2018-04-11 09:30:36 UTC,Met this exactly problem at my env. Wondering is there a way to fix it?
1669610,2017-04-28 21:51:22 UTC,(assuming this refers to a Neutron cloud)
1669610,2017-06-06 09:40:31 UTC,"This is as per design . Please see the help of the same CLI [1].
Besides, it is not that the user cannot change or provide their own options."
1669610,2017-08-06 04:17:32 UTC,[Expired for neutron because there has been no activity for 60 days.]
1669615,2017-11-27 22:20:10 UTC,"Change abandoned by Adrian Turjak (<email address hidden>) on branch: master
Review: https://review.openstack.org/388232"
1669620,2017-06-03 20:13:58 UTC,"Apologises, I think I'm conflating a resume from hibernate issue vs a resume from suspend issue, so the previous comment is probably not that relevant."
1669620,2017-06-03 20:11:44 UTC,"No sure if this will help, but there are plenty of debian bugs related to this to check"
1669620,2017-03-12 05:27:17 UTC,"Can you make persistent log by
$ sudo mkdir -p /var/log/journal
$ sudo systemd-tmpfiles --create --prefix /var/log/journal"
1669620,2017-03-11 02:03:42 UTC,"I tested with another video card (GeForce 8400 GS), and suspend works normally."
1669620,2017-03-10 16:26:09 UTC,"Oops, I misread 9800 as 980. Sorry."
1669620,2017-03-10 07:35:43 UTC,"I'd say nvidia driver is somewhat necessary for new cards, this can be done by"
1669620,2017-03-07 23:41:41 UTC,"I tested with 4.10.0, and I have the same problem."
1669620,2017-03-06 17:04:28 UTC,I believe I have the same issue.
1669620,2017-03-04 19:50:19 UTC,"Yes, with  kernel 4.10.1-041001-generic there is the same problem."
1669620,2017-03-03 18:17:20 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].
1669620,2017-03-03 00:30:13 UTC,This change was made by a bot.
1669620,2017-03-10 14:12:10 UTC,"I'll try, but on Ubuntu 14.04 suspend works with 340. It's not new card, it's about 10 years old. And there wasn't this problem with this card on previous Ubuntu versions."
1669630,2017-04-06 22:51:24 UTC,"A proposal here is to introduce a new API (new resource) for new approvable RBACs, then maintain both options for some time (allowing admins to opt out of the former via policy.json), then dropping the old API after some time (leaving the old api definition in api-ref for out of tree plugins to implement)."
1669630,2017-04-06 23:14:41 UTC,"After checking the glance API model, I start to think a new API sounds appropriate."
1669630,2017-04-06 23:36:21 UTC,"Given that the RBAC API as is currently in Neutron can be made admin only, a new API which users can then safely use would work for me and our use cases."
1669630,2017-06-22 22:40:45 UTC,"@Adrian,"
1669630,2017-06-23 00:37:25 UTC,"I don't have the bandwidth right now, but I might be able to fit it in among other work over the next while. Plus this would be a good reason to actually get into the Neutron code base a bit as it isn't one I've dug through before much."
1669630,2017-07-06 22:41:57 UTC,"This was discussed during today's drivers meeting [1]. The RFE is a sensible request, though for the complexity of the request involved, a neutron spec is required to outline CLI, API changes etc. For all intents and purposes, this can be marked approved (if ready to be worked ASAP) or postponed if no resources are available."
1669630,2017-07-27 22:34:44 UTC,"Marking as postponed until someone has the bandwidth to implement. @Adrian, reach out on IRC when you have some time."
1669631,2017-08-10 02:07:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669634,2017-03-03 11:39:04 UTC,"Dmitriy, would not https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/network_template_90.json be an example ?"
1669634,2017-03-08 17:45:06 UTC,"Vladimir, there are a few issue with this json:
- it's not linked to anywhere in documentation (I filed https://bugs.launchpad.net/fuel/+bug/1669633)
- It's far from the ""default"" template, making it's use as a ""base"" inconvenient.
- It's not complete - deployment with Ceilometer will fail with this template even if everything else matches, because there is no aodh/api role."
1669639,2017-04-17 05:29:53 UTC,Dock Applet 0.77 on 17.04 still the same...
1669639,2017-03-24 20:55:22 UTC,This bug was fixed in the package mate-dock-applet - 0.77-0ubuntu1
1669651,2017-03-03 03:11:53 UTC,"Sometimes I have this bug, I work fine with many programs running but sometimes, I don't know why, but the session is closed instantly, and the system show me the screen to log in session, like a new session."
1669654,2018-05-03 03:56:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669663,2017-04-25 12:21:18 UTC,I found the icon names!
1669663,2017-04-25 12:07:26 UTC,"Hey guys! This bug also applies to Cheese, Calendar, Books, Documents, Maps, Photos, Software, Videos and Weather."
1669663,2017-03-05 17:30:25 UTC,"Fixed upstream here: https://github.com/shimmerproject/elementary-xfce/commit/82a150cac0b39b74694545df0842a7f689931add
Still needs sync to xubuntu-artwork."
1669663,2017-03-15 11:31:43 UTC,This bug was fixed in the package ubuntu-mate-artwork - 17.04.2
1669663,2017-03-07 01:53:31 UTC,This bug was fixed in the package xubuntu-artwork - 17.04
1669663,2017-04-06 16:52:41 UTC,This bug was fixed in the package ubuntukylin-theme - 1.7.0
1669667,2017-03-06 03:57:50 UTC,"After talking with Bartosz Kupidura, this behaviour is by design.
It would be nice though to implement something to correct this, in a way to avoid a network template creation only because I have to spun up two virtual machines and the VLAN is double tagged, both in hypervisor and in the VM."
1669683,2017-03-03 07:01:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440949"
1669683,2017-03-05 17:12:17 UTC,"Reviewed:  https://review.openstack.org/440949
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=07971152413c3aa94e87b16f562acf686b9c5f48
Submitter: Jenkins
Branch:    master"
1669683,2017-03-05 17:17:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441693"
1669683,2017-04-06 12:46:23 UTC,This issue was fixed in the openstack/python-novaclient 8.0.0 release.
1669683,2017-05-01 13:33:12 UTC,"Reviewed:  https://review.openstack.org/441693
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=50e571c23d7cdee527826d9eaa70d467b3e63d25
Submitter: Jenkins
Branch:    stable/ocata"
1669683,2017-05-08 21:46:40 UTC,This issue was fixed in the openstack/python-novaclient 7.1.1 release.
1669686,2017-03-03 06:56:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/440948"
1669686,2018-06-07 09:34:52 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/440948"
1669695,2017-03-13 09:33:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444781"
1669700,2019-12-18 17:30:06 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/445446
Reason: This repo is retired now, no further work will get merged."
1669700,2019-12-18 17:29:57 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/443526
Reason: This repo is retired now, no further work will get merged."
1669700,2017-03-21 12:03:27 UTC,"Reviewed:  https://review.openstack.org/446021
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=2f2e94c46126562959a49f61791e98d879b65a44
Submitter: Jenkins
Branch:    stable/ocata"
1669700,2017-03-21 11:59:30 UTC,"Reviewed:  https://review.openstack.org/446019
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=54580c0ff948b21a63f923566bc4409cb833b328
Submitter: Jenkins
Branch:    master"
1669700,2017-03-16 10:15:39 UTC,"Reviewed:  https://review.openstack.org/445406
Committed: https://git.openstack.org/cgit/openstack/fuel-ostf/commit/?id=0bf90a7a097e9a5b1a0ddeadefb29035ab30bcf6
Submitter: Jenkins
Branch:    stable/newton"
1669700,2017-03-15 15:58:57 UTC,"Reviewed:  https://review.openstack.org/445820
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=f3ab5de2130934e2c150d2efce69ca701ee0f959
Submitter: Jenkins
Branch:    stable/newton"
1669700,2017-03-15 15:49:38 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/446021"
1669700,2017-03-15 15:49:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446019"
1669700,2017-03-15 08:39:11 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445820"
1669700,2017-03-14 11:44:09 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/445446"
1669700,2017-03-09 12:22:20 UTC,"Reviewed:  https://review.openstack.org/443479
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=bcdd3ab02418eb1f4d7b522bb4f4964aa466eb12
Submitter: Jenkins
Branch:    stable/ocata"
1669700,2017-03-09 12:22:03 UTC,"Reviewed:  https://review.openstack.org/443478
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=cc41e591ad767224dc4436c82d9ac1983800dbae
Submitter: Jenkins
Branch:    master"
1669700,2017-03-14 10:22:43 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445406"
1669700,2017-03-09 09:44:17 UTC,"Reviewed:  https://review.openstack.org/443481
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=3c91aa5ae6757545df8c026c4d7e5fea1e654a52
Submitter: Jenkins
Branch:    stable/ocata"
1669700,2017-03-06 09:55:46 UTC,"Related fix proposed to branch: master
Change author: Ilya Bumarskov <email address hidden>
Review: https://review.fuel-infra.org/31580"
1669700,2017-03-06 10:10:46 UTC,"Reviewed: https://review.fuel-infra.org/31580
Submitter: Roman Vyalov <email address hidden>
Branch: master"
1669700,2017-03-06 14:15:45 UTC,"Reviewed:  https://review.openstack.org/439653
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=fd7138c42163f389ddcab64f8430bbf54ea30c04
Submitter: Jenkins
Branch:    stable/newton"
1669700,2017-03-03 07:51:16 UTC,https://review.openstack.org/#/c/439653/
1669700,2017-03-07 11:44:31 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/442407"
1669700,2017-03-07 12:20:20 UTC,"Reviewed:  https://review.openstack.org/442407
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=b13f30013736d93c5f0de7fe99f5b364163b92ee
Submitter: Jenkins
Branch:    stable/newton"
1669700,2017-03-07 11:35:55 UTC,"Fix proposed to branch: master
Change author: Ilya Bumarskov <email address hidden>
Review: https://review.fuel-infra.org/31614"
1669700,2017-03-09 08:21:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443478"
1669700,2017-03-09 08:22:02 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/443479"
1669700,2017-03-09 08:22:30 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/443481"
1669700,2017-03-09 08:22:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443482"
1669700,2017-03-09 09:23:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443526"
1669700,2017-03-07 13:40:18 UTC,"Reviewed: https://review.fuel-infra.org/31614
Submitter: Roman Vyalov <email address hidden>
Branch: master"
1669700,2017-03-09 09:44:41 UTC,"Reviewed:  https://review.openstack.org/443482
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=93d7ddf21a32a35978c31499c065d1a0be3e3848
Submitter: Jenkins
Branch:    master"
1669707,2017-03-03 08:30:16 UTC,This change was made by a bot.
1669707,2017-03-03 18:11:54 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1669707,2017-03-06 09:00:46 UTC,This issue occurs when an OOM kill is triggered (see [0]). This was observed for the first time on kernel version 4.4.0-59-generic #80-Ubuntu.
1669721,2017-03-06 14:33:40 UTC,This is not a Juju bug. I have added hadoop in.
1669722,2017-03-03 09:46:01 UTC,Actually I believe this issue has already been addressed in networking-calico master by https://review.openstack.org/#/c/433702/.
1669729,2017-03-13 21:42:02 UTC,"Re-targeting to ""juju"" project for tracking for Juju 2.x. Putting it on wishlist."
1669729,2021-01-06 14:55:21 UTC,This has come up with a customer
1669734,2017-06-12 03:05:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669734,2017-06-12 03:14:35 UTC,I had the same issue when using imagecopyresampled() to resize PNG images with transparent background. It introduced subtle noise to the transparent background in the resulting image. It looks like some kind of rounding issue within the resampling algorithm.
1669734,2017-06-13 09:06:57 UTC,Since the last upgrade of the php7.0-gd package the workaround with the old version doesn't work perfectly anymore.
1669734,2020-10-30 17:51:50 UTC,"Hi, I've been digging for this bug for a few weeks now."
1669734,2020-11-02 11:02:26 UTC,"For reference, bug referred is
«Fixed bug #45030 (Destination image alpha channel noise when using imagecopyresampled). (Pierre)» from php-5.3.0beta1 release notes."
1669734,2020-11-02 11:30:25 UTC,"That commit is for when PHP is built with the embedded libgd.
But in Ubuntu, PHP is using the system libgd instead of the one built in with PHP."
1669737,2017-03-03 14:56:42 UTC,"Set it to triaged, as I don't see any patches related to it yet. The proposal itself makes sense to me, tho not sure should we send the logs after each clean step of after the whole cleaning completes."
1669737,2017-03-06 09:10:19 UTC,Related patch is https://review.openstack.org/#/c/440495/
1669737,2017-03-07 06:05:58 UTC,"Related Patches: https://review.openstack.org/440495
                 https://review.openstack.org/440502"
1669737,2017-04-24 04:17:17 UTC,"Change abandoned by Aparna (<email address hidden>) on branch: master
Review: https://review.openstack.org/440502"
1669737,2017-08-07 16:45:20 UTC,"Hi! All patches are abandoned, so I unassign this bug."
1669737,2017-11-14 00:59:25 UTC,"Thanks for the rfe. It isn't clear to me where the log files will be put and what the connection is between a clean step and its log file. I'd probably be fine with a more detailed description in the bug, but tagging this with needs-spec to indicate that there isn't enough information for me."
1669740,2017-03-09 09:14:09 UTC,"Reviewed:  https://review.openstack.org/442329
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=4e97471ccc4cfb9047c8ffbc55ebec7090cfee45
Submitter: Jenkins
Branch:    master"
1669740,2017-03-08 12:20:13 UTC,This issue was fixed in the openstack/fuel-qa 11.0.0.0rc2 release candidate.
1669740,2017-03-07 12:56:12 UTC,"Reviewed:  https://review.openstack.org/442328
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=dc8845bbf1024d07df71c0006b625905729c943b
Submitter: Jenkins
Branch:    stable/ocata"
1669740,2017-03-07 10:00:56 UTC,"Reviewed:  https://review.openstack.org/441925
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=b21ba27544fbf605d250b6a7629e6e8025d640e1
Submitter: Jenkins
Branch:    stable/newton"
1669740,2017-03-07 09:15:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442329"
1669740,2017-03-07 09:15:16 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442328"
1669740,2017-03-06 12:43:50 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441925"
1669741,2019-09-17 08:26:52 UTC,Migrated to https://github.com/widelands/widelands/issues/1672
1669741,2017-05-24 07:02:35 UTC,Maybe we should have a look at the Ancient Sun of Fire map then and redesign the terrain a bit?
1669741,2017-05-23 17:58:51 UTC,The problem has been identified and it isn't walkability of stones; I wouldn't like it as well.
1669741,2017-05-22 10:17:45 UTC,"We should be able to solve this by adding an attribute ""walkable"" to certain immovables, like fields."
1669741,2017-03-10 12:54:36 UTC,I dug up the function - it is implemented in Map::calc_nodecaps_pass1()
1669741,2017-05-22 15:23:31 UTC,"I have attached a branch that will allow the farmers to walk through standing stones. The problem that I see with it though is that they visually walk through them as well, so I am not happy with it."
1669741,2017-03-06 10:36:12 UTC,Documentation:
1669741,2017-03-06 07:29:28 UTC,"Explanations offered are not extensively satisfying. First, farmers can walk through corn fields, so they shouldn't block a path."
1669741,2017-03-04 07:10:12 UTC,"I mixed them up with some other eye candy then. If they have size, they will block movement anyway, so no bug there."
1669741,2017-03-03 18:18:48 UTC,"> The standing stones have no size.
"
1669741,2017-03-03 17:53:56 UTC,"The standing stones have no size, but they are still an immovable, so I guess that this makes the search algorithm fail. If you build something that will destroy the standing stone, the space should be cleared for fields afterwards."
1669741,2017-03-03 17:10:40 UTC,Looking at the save game it seems to me that the mentioned farmers couldn't reach the available fields.
1669741,2017-03-10 12:32:29 UTC,"@GunChleoc
You are seeing this from the perspective of a triangle. Viewing the NODE instead, which seems more relevant to economy algorithms, things look less obvious. We have to note there sadly that because of a single out of six fields of a node being not walkable, the entire node is unpassable."
1669743,2017-03-20 08:59:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447417"
1669743,2017-04-05 11:56:18 UTC,Verified on Newton #1566 iso.
1669743,2017-03-24 14:59:04 UTC,"Reviewed:  https://review.openstack.org/449594
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=72eaa18921a5dce874eeca0003b100311a552f50
Submitter: Jenkins
Branch:    stable/newton"
1669743,2017-03-24 12:04:11 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/449594"
1669743,2017-03-24 11:48:51 UTC,"Reviewed:  https://review.openstack.org/447417
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=fba3bc344523da0d43f94e130b4944efe0d32529
Submitter: Jenkins
Branch:    master"
1669743,2017-03-16 10:21:26 UTC,"So, by now the workaround is ""do not rename controller role"" :)"
1669743,2017-03-15 13:54:41 UTC,"After further investigation we found out that in this env haproxy is not deployed, because there is no haproxy_vip."
1669743,2017-03-16 09:35:36 UTC,"Aha, here it is
https://github.com/openstack/fuel-qa/blob/stable/newton/fuelweb_test/tests/tests_lcm/test_tags.py#L196"
1669743,2017-03-16 09:29:19 UTC,"Here is where it is from:
2017-03-14 21:46:28.309 DEBUG [7f6e5d038880] (logger) Request POST /api/releases/2/roles from 10.109.10.1:59052 {""meta"": {""group"": ""base"", ""description"": ""New controller role"", ""weight"": 10, ""tags"": [""controller"", ""database"", ""keystone"", ""neutron"", ""new_tag""], ""conflicts"": [""compute""], ""public_for_dvr_required"": true, ""name"": ""Controller_new"", ""update_required"": [""compute"", ""cinder""], ""public_ip_required"": true}, ""name"": ""controller_new"", ""volumes_roles_mapping"": [{""id"": ""os"", ""allocate_size"": ""min""}, {""id"": ""logs"", ""allocate_size"": ""min""}, {""id"": ""image"", ""allocate_size"": ""all""}, {""id"": ""mysql"", ""allocate_size"": ""min""}, {""id"": ""horizon"", ""allocate_size"": ""min""}]}
2017-03-14 21:46:28.360 DEBUG [7f6e5d038880] (logger) Response code '201 Created' for POST /api/releases/2/roles from 10.109.10.1:59052"
1669743,2017-03-16 09:21:46 UTC,"[root@nailgun ~]# fuel nodes
id | status | name                    | cluster | ip          | mac               | roles          | pending_roles | online | group_id
---+--------+-------------------------+---------+-------------+-------------------+----------------+---------------+--------+---------
 1 | error  | slave-01_controller_new |       1 | 10.109.10.4 | 64:2a:3e:e5:a3:88 | controller_new |               |      1 |        1"
1669743,2017-03-15 15:24:38 UTC,Actually there is no vips in network metadata
1669743,2017-03-07 11:00:03 UTC,"Seems like some issue with host settings in .my.cnf. Please, set it to localhost."
1669743,2017-03-07 09:50:45 UTC,"root@node-1:~# mysql --protocol=SOCKET
ERROR 2047 (HY000): Wrong or unknown protocol"
1669743,2017-03-16 10:16:39 UTC,"The reason is that
https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/objects/cluster.py#L1009
uses hardcoded role name rather than tags."
1669745,2017-03-03 11:46:21 UTC,"I forgot to mention. I granted access to the model _after_ the new user registered, otherwise it would've specified the correct way to switch. But since the model-access was granted afterwards that part was never shown."
1669747,2017-03-27 12:38:09 UTC,"Reviewed:  https://review.openstack.org/448996
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=fad31f80a6ae51b4f600275426cf83431f3e0d56
Submitter: Jenkins
Branch:    master"
1669747,2017-03-28 12:08:01 UTC,"Reviewed:  https://review.openstack.org/450161
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=280a29e51822e531126435ec3487b6a17e5532af
Submitter: Jenkins
Branch:    stable/newton"
1669747,2017-03-27 12:52:49 UTC,"Reviewed:  https://review.openstack.org/450190
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=3a904cf197e7fd8c4ead802a4ed355c4c9d019f7
Submitter: Jenkins
Branch:    stable/newton"
1669747,2017-03-27 12:28:22 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/450190"
1669747,2017-03-27 12:50:35 UTC,"Reviewed:  https://review.openstack.org/450189
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=5ef7be5dce7cddd4e4f145eabda0793216ae7cde
Submitter: Jenkins
Branch:    stable/ocata"
1669747,2017-03-27 11:02:37 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/450161"
1669747,2017-03-27 10:59:56 UTC,"Reviewed:  https://review.openstack.org/443556
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=4f33d4aabb859894167728ec347ee36b2c17d19d
Submitter: Jenkins
Branch:    master"
1669747,2017-03-23 08:32:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/448996"
1669747,2017-03-09 10:35:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443556"
1669747,2017-03-27 12:28:09 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/450189"
1669747,2017-03-03 11:59:29 UTC,"Sustaining team, please reassign it if needed"
1669748,2017-03-03 11:28:19 UTC,"StacktraceTop:
 data (this=0x735f4252415f4c3f) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:141
 qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:980
 d_func (this=0x735f4252415f4c37) at kernel/qwindow.h:94
 QWindow::geometry (this=0x735f4252415f4c37) at kernel/qwindow.cpp:1533
 UbuntuSurface::updateGeometry (this=0x735f4252415f4c37, newGeometry=...) at ../../../src/ubuntumirclient/qmirclientwindow.cpp:549"
1669748,2017-03-27 07:46:58 UTC,this crash happens when you save the project(File\Save Project)
1669749,2017-03-17 15:38:37 UTC,"Hello,"
1669749,2017-03-17 15:50:56 UTC,"It is not so much about importing. It is about shared data (in memory), cached in the other plugins. Also, importing the logging module does not help, because COM1: cannot be shared. If the ""main"" cloudbase-init already uses COM1. then I cannot open COM1: again from within my plugin. The correct way ist to share the *Instance* of the logger."
1669749,2017-03-17 15:52:37 UTC,"BTW, look at cloud-init. They do it correctly (apart from the logging problem which they do not have)."
1669751,2017-05-03 12:46:29 UTC,"Reviewed:  https://review.openstack.org/461145
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=2ba8d872e8d38bacdbda42c04276be6c56d263cc
Submitter: Jenkins
Branch:    stable/ocata"
1669751,2017-05-03 12:46:17 UTC,"Reviewed:  https://review.openstack.org/461146
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=c8b04173d932cb57891117b96f19d9257c91057d
Submitter: Jenkins
Branch:    stable/newton"
1669751,2019-12-18 17:38:35 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/449494
Reason: This repo is retired now, no further work will get merged."
1669751,2017-04-28 20:27:30 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/461146"
1669751,2017-04-28 20:27:14 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/461145"
1669751,2017-03-24 08:50:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/449494"
1669751,2017-04-28 20:34:37 UTC,"Reviewed:  https://review.openstack.org/441101
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=ae1c80f8fbd1d7156075a1dbf61e832b00852bb7
Submitter: Jenkins
Branch:    master"
1669751,2017-03-03 12:43:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441101"
1669753,2017-03-14 14:23:45 UTC,"Your build configuration is broken - the compiler flags show that the build is including headers from the system Qt (5.5.1). AFAIK, nobody has tried compiling against Qt provided by the qt.io installer, it's not something that's supported and I'm not sure what would be required to make it work."
1669753,2017-03-15 12:17:39 UTC,"Thanks for your answer.

> Your build configuration is broken - the compiler flags show that the build is including headers
> from the system Qt (5.5.1)


Oh, okay.

> AFAIK, nobody has tried compiling against Qt provided by the qt.io installer, it's not something
> that's supported and I'm not sure what would be required to make it work.


I don't know either, but I once successfully built it against 5.7 (iirc) provided by the online installer from qt.io. I know it's not supported officially."
1669755,2017-03-03 12:16:39 UTC,"I'd vote for the ""DefaultDependencies=no"" option as per experience with this RAX issue:
https://bugs.launchpad.net/cpc-rax/+bug/1657223"
1669755,2017-03-03 12:30:55 UTC,"I am advised that if one wants to communicate with xenstore from cloud-init modules, one needs xe-daemon runnning, hence xe-daemon should be brought up asap."
1669755,2017-03-03 13:17:47 UTC,This bug was fixed in the package xe-guest-utilities - 6.2.0-1120+dsf1-0ubuntu4
1669758,2017-03-27 11:28:34 UTC,apport information
1669758,2017-03-27 11:28:35 UTC,apport information
1669758,2017-03-27 11:36:18 UTC,To complete 'apport-collect 1669758' I had to run while connected using network cable. Hope that doesnt change the values in the report.
1669758,2017-05-31 06:32:14 UTC,"Please follow instruction in comment #19, but use 4.12-rc2 instead."
1669758,2017-05-27 04:17:53 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1669758,2017-05-27 05:55:27 UTC,I am using the latest Ubuntu 17.04 and the problem is still happening.
1669758,2017-03-27 11:28:32 UTC,apport information
1669758,2017-03-27 20:44:41 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1669758,2017-03-27 11:28:31 UTC,apport information
1669758,2017-03-27 11:28:37 UTC,apport information
1669758,2017-03-27 11:28:29 UTC,apport information
1669758,2017-03-03 12:31:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1669758,2017-03-26 12:00:57 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1669758,2017-03-27 11:28:17 UTC,apport information
1669758,2017-03-27 11:28:19 UTC,apport information
1669758,2017-03-27 11:28:20 UTC,apport information
1669758,2017-03-27 11:28:30 UTC,apport information
1669758,2017-03-27 11:28:23 UTC,apport information
1669758,2017-03-27 11:28:24 UTC,apport information
1669758,2017-03-27 11:28:25 UTC,apport information
1669758,2017-03-27 11:28:28 UTC,apport information
1669758,2017-03-27 11:28:21 UTC,apport information
1669765,2020-02-07 19:34:26 UTC,"I think we've addressed all of the issues with the sysctl knobs in HA routers over the past few cycles as part of other bugs, so I'll close this bug."
1669775,2017-03-31 16:52:22 UTC,I'm a KeePass2 user and my two cents on researching this is that this is a bug in Mono library (which KeePass2 uses in Linux port).
1669782,2017-03-03 13:22:27 UTC,Old Related patch https://review.openstack.org/#/c/130228/
1669782,2017-11-14 01:05:53 UTC,"I tagged this as 'needs-spec' because I looked at the old patch (see comment #1) that was abandoned, and if we implement this, it needs to be spelled out what this PUT would do, and what the 'openstack baremetal' CLI command would be (if any)."
1669788,2017-03-03 14:17:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441145"
1669788,2018-06-07 09:34:44 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/441145"
1669796,2017-03-03 15:36:07 UTC,seems like it should be mos11.0?
1669796,2017-03-03 15:37:38 UTC,"one more
https://github.com/openstack/fuel-main/blob/stable/ocata/config.mk#L27"
1669796,2017-03-06 12:00:58 UTC,"we do not have versions bumped, so we have 10.0 in release configuration. version bumps are handled with different commits, so we just need to build ISO with mos10.0 until these commits are merged"
1669800,2018-02-28 09:59:11 UTC,"Hi Raúl,"
1669800,2018-02-28 08:16:13 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1669800,2017-03-03 16:49:39 UTC,Updated AppArmor Liferea profile with an additional member for the MountTracker.
1669804,2017-03-03 14:44:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669804,2017-03-03 14:46:26 UTC,also if you jump to a VT (CTRL ALT F1) and then get back (ALT F8) you'll see strange behaviour with the keyboard and the context menu not working (right click) with some apps
1669816,2017-03-03 16:15:52 UTC,"Yeah, your solution seems like the way to go, with the only exception is that I think the message about the ERROR state actually means that the node is in NOSTATE power state, it is printed in that case too."
1669824,2017-09-27 13:24:50 UTC,Any of the relations can be bound; so
1669829,2017-03-14 05:19:14 UTC,"Putting on the Wishlist, as this is a current behavior and you are requesting a change."
1669829,2017-03-14 14:29:25 UTC,"Actually, this is a regression.  With Juju 1.25.10 + MAAS 1.9.4, the ssh keys of the MAAS user do survive to exist on the Juju unit."
1669829,2017-03-21 04:59:05 UTC,I am re-triaging this since Juju 2.0 and 2.1 exhibit this behavior. It is not a regression for Juju 2 nor for 2.2.
1669829,2017-03-21 05:00:25 UTC,Marking this report as Won't Fix for 2.0 and 2.1 series as we are not planning any further releases 2.0x/2.1x releases.
1669829,2017-04-10 14:43:33 UTC,"Juju 2.0 has support for directly registering user's ssh keys which it will apply to all machines. (you can add keys, remove them, etc.)
It is possible that we should be looking up a user's set of keys from MAAS at some point, but the set-of-keys that can access the machine are intentionally controlled by Juju. (multi-user, etc means the set of keys that can access a machine could be entirely separate from the set of keys that deployed the machine.)"
1669832,2017-03-08 22:28:34 UTC,"I guess if this change is made, it should be made not only for the colors but for all the config options (at least all that are applied currently when the prefs dialog is closed, that is, doesn't require a terminator restart)."
1669834,2019-09-09 04:18:56 UTC,"Based on previous comments, I am closing this report."
1669834,2017-06-01 02:51:42 UTC,The error message isn't great.
1669834,2017-10-23 22:07:26 UTC,Today I received a nagios alert which seems to have been caused by nrpe getting restarted while it got polled (that's the best explanation I can rationalize it with).
1669834,2017-06-01 03:30:22 UTC,"We have actually started working on the solution in December 2016. Essentially, the plan was to have model have a state which could be something more descriptive like ""updating"", ""coming up, ""migrating"", etc... The api calls and user commands will be blocked until the model reports active state but the error message that user will see during ""busy"" stage will be indicative of why the model is actually un-usable yet."
1669834,2017-10-25 06:26:14 UTC,"Until juju has finished initialization and determined that there isn't an
upgrade, we reject connections with ""upgrade in progress"". So that isn't an
actual upgrade vs just taking a while to initialize. Looking at the
timestamps, I'm a little surprised for it to take a full minute for it to
be available, but otherwise it isn't too surprising."
1669835,2017-03-06 16:09:51 UTC,"Logs show that instance was spawned successfully, l3 agent also configured floating ip with no issues: http://paste.openstack.org/show/601599/"
1669848,2017-03-08 09:11:31 UTC,"maybe also add verbose flags to other remote tools, such as curl etc."
1669853,2017-03-03 18:29:03 UTC,"I've checked previous revisions of unity8-session snap, and the testability slot was last working in revision 450."
1669854,2017-04-26 20:48:56 UTC,"This is affecting rocket chat, which has to add .node_version.txt to the stage keyword in order to get the dot file in the resulting snap."
1669864,2017-03-03 20:55:27 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1669864,2017-03-04 18:08:00 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=194787
1669864,2017-03-03 19:58:55 UTC,"this is a new install , and I have the issue since the beginning.
I have found a discussion about this trouble here :
https://ubuntuforums.org/showthread.php?t=2121339"
1669864,2017-03-03 19:00:08 UTC,This change was made by a bot.
1669864,2017-03-03 20:11:20 UTC,Same problem with
1669864,2017-03-03 19:38:47 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1669866,2017-10-09 20:37:45 UTC,Note that this is also problematic on the patron search results column picker: https://bugs.launchpad.net/evergreen/+bug/1722387
1669866,2017-03-06 19:26:44 UTC,"I'm in general agreement that we should remove options that are unlikely to be used. In this case, it seems like the user fields would be unnecessary since you are already in the patron record. I'm not quite sure about the requester information. I wonder how often staff need to view that information and whether it warrants including column pickers when they may be confused about what information is displaying."
1669866,2017-03-06 14:52:33 UTC,Okay... but why are either one of those sets of fields on that particular menu? It makes the menu so long as to be practically unusable and most options related to user and requester are irrelevant for that screen.
1669866,2017-03-03 21:25:20 UTC,"Terran,"
1669874,2017-03-03 19:03:48 UTC,I was able to get traction on this by using the src files from the rpm:
1669875,2019-10-01 14:56:49 UTC,Because we've had a some folks stumble across this bug and ask about it recently I thought I'd document this here for posterity:
1669875,2019-06-03 15:37:46 UTC,"This bug is fixed with commit deaeb714 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=deaeb714"
1669875,2019-07-17 17:12:19 UTC,"This bug is believed to be fixed in cloud-init in version 19.2. If this is still a problem for you, please make a comment and set the state back to New"
1669875,2019-03-14 17:38:00 UTC,"Mark,"
1669875,2017-03-03 18:44:45 UTC,"Some info:
$ ( cd /sys/class/dmi/id && sudo grep -r . * )
bios_date:09/21/2015
bios_vendor:Phoenix Technologies LTD
bios_version:6.00
board_name:440BX Desktop Reference Platform
board_serial:None
board_vendor:Intel Corporation
board_version:None
chassis_asset_tag:No Asset Tag
chassis_serial:None
chassis_type:1
chassis_vendor:No Enclosure
chassis_version:N/A
modalias:dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
power/control:auto
power/async:disabled
power/runtime_enabled:disabled
power/runtime_active_kids:0
power/runtime_active_time:0
grep: power/autosuspend_delay_ms: Input/output error
power/runtime_status:unsupported
power/runtime_usage:0
power/runtime_suspended_time:0
product_name:VMware Virtual Platform
product_serial:VMware-42 06 94 a2 6c e8 2b 6e-f0 c7 e7 5c cb c5 36 c9
product_uuid:420694A2-6CE8-2B6E-F0C7-E75CCBC536C9
product_version:None
sys_vendor:VMware, Inc.
uevent:MODALIAS=dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:"
1669875,2019-03-14 03:55:44 UTC,"I ran into this recently and had a quick sniff around for a solution.  I noticed that in https://bugs.launchpad.net/cloud-init/+bug/1756471 the Open Telekom Cloud folks made use of the chassis asset tag field to ensure proper detection.  Scott, is there any reason we couldn't use the same approach for VMware as well (and potentially others who have DMI/SMBios support)?  As it happens, asset tag is a field we can set.  E.g. you can create a flavor with a property like this:"
1669875,2019-03-15 13:59:09 UTC,Sure thing.  I'll have a look at a patch that includes both values soon; it looks pretty straightforward.  We're also prototyping a driver patch that would introduce a new strOpt config option for Nova that would allow admins specify a string which would be set as the assetTag on all new instances (unless overridden by an extra spec).
1669894,2017-03-13 18:14:06 UTC,This bug was fixed in the package libzip-ruby - 0.9.4-1+deb7u1build0.12.04.1
1669894,2017-03-13 17:38:34 UTC,This bug was fixed in the package ruby-zip - 1.2.0-1.1
1669894,2017-03-08 16:24:29 UTC,"Thanks for the report, Phillip. We are aware of this issue and are tracking it here:"
1669894,2017-03-13 16:02:49 UTC,"Hello again, Phillip. I made a mistake while triaging this bug last week because I mistakenly thought that ruby-zip was in main. It turns out that ruby-zip is in universe and, therefore, it is community supported. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures."
1669902,2017-03-03 20:58:21 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/441472"
1669902,2017-03-03 21:03:04 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441473"
1669902,2017-03-09 19:40:32 UTC,"Reviewed:  https://review.openstack.org/441473
Committed: https://git.openstack.org/cgit/openstack/searchlight-ui/commit/?id=f609596a785daea6a94a9fd20a5263d667104ba7
Submitter: Jenkins
Branch:    stable/newton"
1669902,2017-10-08 21:18:02 UTC,"Reviewed:  https://review.openstack.org/441472
Committed: https://git.openstack.org/cgit/openstack/searchlight-ui/commit/?id=1b6dd1521a71cb931b93677404486db9d3924fea
Submitter: Jenkins
Branch:    stable/ocata"
1669911,2017-03-06 16:54:08 UTC,"Fix committed into lp:libertine at revision 430, scheduled for release in libertine, milestone Unknown"
1669913,2017-03-08 15:09:56 UTC,"Hmm, after some further testing, some other app icons still aren't found after the attached branch is applied."
1669913,2017-03-14 21:18:22 UTC,This bug was fixed in the package ubuntu-app-launch - 0.10+17.04.20170310-0ubuntu1
1669917,2018-01-05 14:00:50 UTC,"Same here with 2 HDD 2TB Hitachi.
The disks are OK with everything except Timeshift and Clonezilla."
1669917,2018-01-05 14:14:15 UTC,"Just reformatted with standard parameters and same problem.
Tried chmod 777 on its root just to exclude permission problems. Same problem."
1669917,2018-01-05 14:49:16 UTC,"Found! The way I formatted the disks,
sudo mkfs.ext4 /dev/sdc -L etichetta -O sparse_super,large_file -m 0 -T largefile4 -E lazy_itable_init=0,lazy_journal_init=0"
1669917,2018-04-15 16:25:05 UTC,"I also had the same problem with my 500GB hard drive that is leftover from my old computer that I use externally.  When I want to gparted->view->information, it already said msdos.  Even if it eats 100GB, it's still be worth it for me right now, as I don't have that much to back up.  How do you add a partition table?"
1669917,2018-04-15 17:13:59 UTC,"Never mind, I figured it out on gparted.  It backed up to the HD now."
1669922,2017-03-19 13:17:40 UTC,"Upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=780258"
1669922,2017-04-08 08:26:44 UTC,"The attachment ""Dependencies.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1669930,2017-08-22 00:16:39 UTC,"I've seen this also appear on ESXi 6.5 U1, but I thought it was related to errors of the floppy image not mounting properly."
1669930,2017-04-14 14:41:22 UTC,"`console= tty1 console=ttyS0` boot options cause this result.
If you remove the options from `grub.cfg` and `/etc/default/grub.d/50-cloudimg-settings.cfg`
All will be fine."
1669930,2019-03-18 16:45:52 UTC,Have the same issue with cloudstack running on the top of esxi 6.5.
1669931,2019-12-19 03:55:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1669950,2017-04-05 20:21:53 UTC,I've started on the blueprint
1669956,2017-03-30 18:18:45 UTC,"RFE bug is usually reviewed based on its status (Triaged, Confirmed).
""In Progress"" bug tends to get less interest. Is there any reason of In Progress status?"
1669956,2017-03-30 18:19:42 UTC,"As a start, input from FWaaS team would be appreciated, though the request itself looks reasonable."
1669956,2017-04-04 10:33:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453110"
1669956,2017-04-10 18:39:12 UTC,"Change abandoned by Reedip (<email address hidden>) on branch: master
Review: https://review.openstack.org/453110"
1669956,2017-04-10 18:41:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/455422"
1669956,2017-04-25 02:25:48 UTC,"Reviewed:  https://review.openstack.org/455422
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=d136fd4c62c1db4ac5760f1693dcd0fc38dae6fc
Submitter: Jenkins
Branch:    master"
1669956,2017-08-01 07:10:10 UTC,"it might be easy for iptables based implementation but i guess we should not assume it.
do you plan to introduce some way for api users to discover which protocol can be used?"
1669956,2017-08-21 06:47:19 UTC,"I have added a Release Note in FWaaS for the IPTables based implementation. Other than that, let me know if we can propose the supported protocols to the users"
1669956,2019-05-16 11:04:38 UTC,"Change abandoned by Reedip (<email address hidden>) on branch: master
Review: https://review.opendev.org/440331
Reason: Cannot work on it right now... anyone else can take it up"
1669956,2020-03-24 21:04:05 UTC,Regarding current status of neutron-fwaas project I'm marking this RFE as won't fix for now.
1669957,2017-03-07 00:46:07 UTC,Thank you for the prompt response. I assume this is reproducible easily.
1669957,2017-03-07 00:24:23 UTC,I've noticed the bug on Xenial.
1669957,2017-03-07 00:09:02 UTC,"I apologize, my search was incomplete and I do see the file after install autofs on trusty. However, afaict, there is on get_krb5_cache method at all in /etc/auto.smb in Trusty. It is there in Zesty."
1669957,2017-03-07 00:05:53 UTC,"Hello,"
1669962,2017-10-14 21:49:57 UTC,"thx for the report.
fixed in glade2script_3.2.3~ppa4"
1669964,2017-03-04 05:47:12 UTC,"StacktraceTop:
 XInternAtom (dpy=dpy@entry=0x562d2ef56fb0, name=name@entry=0x7f274db582d0 ""ConnectorType"", onlyIfExists=onlyIfExists@entry=0) at ../../src/IntAtom.c:174
 gsd_rr_screen_initable_init (initable=<optimized out>, canc=<optimized out>, error=0x7ffc2b2dc958) at gsd-rr.c:735
 g_initable_new_valist () from /tmp/apport_sandbox_iTLPUl/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_initable_new () from /tmp/apport_sandbox_iTLPUl/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 gsd_rr_screen_new (screen=0x562d2ef53400, error=error@entry=0x7ffc2b2dc958) at gsd-rr.c:973"
1669982,2017-03-24 02:25:13 UTC,"Hi,"
1669982,2017-03-24 05:08:59 UTC,A test you can do to confirm what was reported.
1669982,2017-03-24 05:13:18 UTC,"Correction in step 4 above,the ""su"" command should be ""su - -c""."
1669983,2017-03-04 09:40:52 UTC,"StacktraceTop:
 logsuck_getline (buf=0x7ffe9fa12eb0 ""Mar  3 21:54:30 K73BR sshd[1381]: Received signal 15; terminating.\n"", buflen=1000, from_previous_source=<optimized out>, whichsource=0x7ffe9fa12e24) at sshguard_logsuck.c:183
 read_log_line (buflen=<optimized out>, from_last_source=<optimized out>, source_id=<optimized out>, buf=<optimized out>) at sshguard.c:247
 main (argc=-1616826768, argv=0x7ffe9fa12e30) at sshguard.c:213"
1669996,2017-05-06 19:30:47 UTC,Probably better to fix this by always opening scripts for editing and only executing from the right click menu. I don't think we need yet another dialog in the mix
1669996,2017-05-17 23:13:54 UTC,"This happens to me if I dclick on python scripts even I choose Sublime as default app.
If I run them, something odd happens:
Cursor becomes ""+"" (I think capture screen like)
Home folder got populated by files which names are the python's imports names (files like traceback, socket, time, struct etc.).
Every file is a ps file with windows screenshots inside."
1669996,2017-05-20 10:33:38 UTC,This will be revisited once Files has been transferred to GitHub.
1670002,2017-04-03 13:08:33 UTC,I don't get an internal server error with openstackclient:
1670002,2017-03-23 15:24:32 UTC,"Thanks for reporting this,"
1670002,2017-03-24 06:50:47 UTC,"When we keep type_drivers and tenant_network_types as vlan in ml2_conf.ini, we are able to create net with segmentation_id 0 which shouldnot be the case."
1670002,2017-03-06 22:21:30 UTC,Can you please provide more details?
1670002,2017-03-27 19:36:10 UTC,At least that's a bug that you get InternalError. I am not sure if we should consider it an invalid case to have 0-vlan tag though.
1670009,2017-03-04 14:47:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670009,2017-03-08 04:59:30 UTC,"Asked Unity developers to check when that happened:
(https://answers.launchpad.net/unity/+question/536832)"
1670009,2017-03-08 05:06:03 UTC,This is intentional and it is not easily split out into a separate package.
1670009,2017-03-08 12:36:55 UTC,Thanks for the analysis. See also more background in https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1669997 So a nautilus-unity packages could host the Unity specific part.
1670009,2020-07-18 09:41:15 UTC,"Further to comment #9, closing Papercuts task"
1670018,2019-12-08 20:21:59 UTC,Please notice that this very annoying bug is still present in hplip 3.18.10 and also in 3.19.11. I did the procedure described here a number of times but it is very annoying to have to repeat it at every software upgrade.
1670018,2018-10-28 11:27:14 UTC,I observe this defect with hplip-3.18.6 on Ubuntu 16.04.5 LTS.
1670018,2017-03-06 10:07:38 UTC,"Hi,"
1670018,2017-05-30 22:26:14 UTC,"Hello,"
1670027,2017-04-13 21:13:55 UTC,Thanks for your bug report.
1670031,2017-03-13 19:58:49 UTC,Open a terminal and enter
1670031,2018-04-23 00:11:46 UTC,">sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
"
1670041,2017-10-12 07:08:27 UTC,The number from iperf3 does show big difference between Windows 10 and Linux.
1670041,2017-09-09 17:45:36 UTC,4.13 without modifications:
1670041,2017-08-01 20:42:47 UTC,"Eric,"
1670041,2017-08-01 13:34:30 UTC,"Disabling Powersave in NetworkManager did it for me. I was barely getting 300kB/s on certain workloads on my 2.4GHz network whereas I could get full speed on my 5GHz one. By disabling the power management in NetworkManager, I got full speed all the time and I haven't really noticed any decrease in power consumption."
1670041,2017-07-29 21:23:52 UTC,"Eric,"
1670041,2017-07-26 01:37:37 UTC,"2,8 cubic"
1670041,2017-07-26 00:10:55 UTC,4.13-rc2 + tcp_output.c
1670041,2017-07-25 16:27:18 UTC,"Sorry if I was not clear, but I would like to combine #42 and #44 experiments."
1670041,2017-07-24 19:04:56 UTC,"Eric, the UDP measurement was to provide a rough estimate of what the AP is capable of sustaining without congestion control and flow control."
1670041,2017-07-24 16:53:16 UTC,"Hi Eric,"
1670041,2017-07-24 14:40:33 UTC,"Please do not compare UDP and TCP, this is absolutely useless."
1670041,2017-07-23 10:49:59 UTC,"Likewise, on a non-congested network (802.11ac), directly from the laptop to the AP:"
1670041,2017-07-21 10:44:38 UTC,"I've built a 4.13-rc1 (5771a8c08880) kernel and have done some laptop (4.13, bbr) <-> AP <-> laptop (4.4 cubic) tests. Not sure about the AP and there is a fair amount of wireless devices on the network I was connected to. Most of them have Cubic congestion control but I am not sure how fair they shared bandwidth."
1670041,2017-07-18 06:13:42 UTC,"Kirill, would it be possible to run again your experiments, but using bbr congestion control ?"
1670041,2017-10-18 19:07:35 UTC,"anyone tried this from dell.com?
https://www.dell.com/support/article/uk/en/ukbsdt1/sln306440/killer-n1535-wireless-firmware-manual-update-guide-for-ubuntu-systems?lang=en"
1670041,2017-10-19 04:57:43 UTC,I tried that in comment #58. It's already in linux-firmware.git.
1670041,2018-07-24 09:32:33 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1670041,2017-11-07 01:34:41 UTC,Hello s.illes79;
1670041,2021-01-01 18:17:26 UTC,Can confirm that this bug still exists in groovy.
1670041,2020-12-07 07:53:14 UTC,I also confirm this bug on Focal.
1670041,2020-09-20 14:46:54 UTC,"Can confirm. Still present here on Ubuntu Focal, too."
1670041,2020-06-02 02:16:36 UTC,this bug is still not solved in 20.04
1670041,2020-04-07 22:16:35 UTC,Is there anything a Ubuntu 18.04 user (upgraded from the preinstalled Dell XPS Ubuntu 16.04) can do without manually replacing kernels and possibly compromising laptop bootability?
1670041,2018-08-15 14:52:26 UTC,I believe this issue has been fixed in newer kernel.
1670041,2017-07-18 05:58:53 UTC,"Thanks to all of you for the tests, sorry for the delay, I have been on vacation last week."
1670041,2018-05-17 14:00:24 UTC,"Yes, confirmed. It's the patch: 109.12Mbs on 5GHz with the stock kernel."
1670041,2018-05-17 13:51:50 UTC,"Joseph,"
1670041,2018-05-02 18:33:31 UTC,"I built a Bionic test kernel with commits 36148c2bbfbe and c9f1f58dc2eb.  Commit 3a9b76fd0db9 is not needed in Bionic, since it is 3.15 based."
1670041,2018-04-30 13:46:47 UTC,And original commit adding the infrastructure linked to this thread ;)
1670041,2018-04-30 12:37:33 UTC,The low throughput with transmit TCP streams on ath10k should be fixed with this mac80211 commit:
1670041,2018-02-03 13:44:38 UTC,"I encountered this issue while trying to stream from a Tobii Pro Glasses 2, i.e. ~5Mbit/sec streaming, UDP or TCP recv would freeze for 3-10 seconds once every 30 to 100 seconds. Sometimes recv would block for over 5 seconds before returning with a packet send by the host. I used a python script to compare received datarate between windows and all the linux boxes. The host is streaming ~5Mbit h264 stream, and my client is simply receiving and then discarding the packets. Windows box never reported datarate average per second beneath 600kbyte/sec, but linux would drop to 250kbyte/sec once every 30 to 100 seconds (and then jump up to 2000kbyte/sec to compensate). So it seems like it sleeping or something. Note this is UDP connection, although I also tried TCP."
1670041,2017-11-11 19:52:08 UTC,"So, going back to question in #60, the Dell link just says to get the latest stuff from kvalo's firmware repo."
1670041,2017-11-11 19:40:13 UTC,There's also Intel 9260 coming up (wave 2):
1670041,2017-11-11 12:04:29 UTC,"FWIW, I replaced the Atheros card with Intel 8265, which I bought for $20 on amazon (https://www.amazon.com/gp/product/B0721MLM8B) and haven't had any problems since. iperf results are way more stable than with Atheros. I suggest everyone to do the same thing."
1670041,2017-11-07 03:10:12 UTC,The disconnecting problem is not the same as this issue.
1670041,2017-11-06 10:10:07 UTC,Using this guide https://www.dell.com/support/article/ng/en/ngdhs1/sln306440/killer-n1535-wireless-firmware-manual-update-guide-for-ubuntu-systems?lang=en and upgrading to latest firmware for Dell XPS 15 on Ubuntu 17.10 for the following below solved my wifi frequent connection drop while NetworkManager was still showing the Wifi was connected.
1670041,2017-07-14 06:52:11 UTC,"Eric, thank you for looking at it! I have measured all four variants that you have suggested, as well as the default ones, using linux-4.12.1 as a base."
1670041,2017-10-13 15:16:08 UTC,"Using ubuntu 17.10, kernel 4.13-0.15-generic on XPS 13 9360 QCA6174 rev 32.
Connection on 5Ghz band AC Freebox router."
1670041,2017-07-12 16:59:58 UTC,I noticed strange behavior.
1670041,2017-05-20 10:55:48 UTC,"Tested the patched kernel - the results are consistent now across laptop -> server, server -> laptop tests for both TCP and UDP."
1670041,2017-05-12 04:27:01 UTC,"Hi, just a quick update: I have not forgotten about trying out the new kernel. I am currently geographically far away from the access point that I used for testing and it is hard to find 802.11ac Wi-Fi in the wild."
1670041,2017-05-05 19:00:40 UTC,Thanks Joseph! I will try it out.
1670041,2017-05-05 18:48:16 UTC,I built a Zesty test kernel with the patch posted in comment 11.  The test kernel can be downloaded from:
1670041,2017-05-05 14:53:38 UTC,"Kalle,"
1670041,2017-05-05 10:45:12 UTC,My observations are mostly just significantly lower signal strength than another laptop I have with intel wireless during side by side test.  I'm receiving an intel AC 8265 (Model 8265NGW) in the coming days to do a comparison in the same chassis for a fair test (in case of antenna performance issues).
1670041,2017-05-05 06:30:49 UTC,"I'm having a hard time understanding this bug report, so I have some extra questions:"
1670041,2017-05-04 18:28:21 UTC,"KalleValo, I added you in the hopes for some insight."
1670041,2017-05-04 18:23:44 UTC,"Thank AceLan, I gave it a try, but it seems that those files are the same or older than the ones available on github.com/kvalo/ath10k-firmware/tree/master/QCA6174 and the poor performance remains."
1670041,2017-05-04 06:31:07 UTC,"Try to get the firmware from the linux-firmware git tree
   git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
copy the firmwares in ath10k/QCA6174/hw3.0/ to /lib/firmware/
It should help."
1670041,2017-05-03 20:09:37 UTC,"I'm also experience abysmal Wi-Fi performance with QCA6174 on a new Lenovo Yoga 910 - dropping connection every few minutes, reporting very low network strength coverage."
1670041,2017-03-06 17:40:43 UTC,"dima@blade:~$ uname -r
4.11.0-041100rc1-generic"
1670041,2017-03-06 15:17:48 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1670041,2017-03-05 17:05:04 UTC,Confirmed *NFA364xp.bin and qca61x4_2_2.bin usage by Windows. linux-firmware's version is definitely not up-to-date for this card as it refers to NFA324i (see the paste link).
1670041,2017-03-04 20:05:22 UTC,"Just to rule out the case of bad compatibility between the STA on the router (Quantenna QSR1000 chipset, QT3840BC SoC in case of my RT-87U) and the client WNIC I also checked with a different STA."
1670041,2017-03-04 20:00:11 UTC,This change was made by a bot.
1670041,2017-07-14 00:31:21 UTC,4.12 + the first change from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/33 + 802.11ac network => looks better.
1670041,2017-06-04 13:05:42 UTC,Just adding that I have the same problem on a Dell XPS13 9630 with the same wifi card.  Interesting though that iperf will show poor performance (10Mbit/s) but web based speedtest pages show 150Mbps.  Windows will also show about 100Mbit/s with iperf running while Ubuntu will show just 10Mbit/s.
1670041,2017-06-05 13:23:55 UTC,It doesn't look like the specific patch posted in #11 ever made it into mainline.  Can you test the v4.12-rc4 kernel to see if the bug was fixed in a different way?  It can be downloaded from:
1670041,2017-08-01 22:46:29 UTC,This is with cubic:
1670041,2017-06-10 21:36:21 UTC,"Joseph,"
1670041,2017-07-12 04:54:03 UTC,"FYI, I'm using an XPS 15 9560, from this page: https://wiki.archlinux.org/index.php/Dell_XPS_13_(9360)#Wireless
It says:
""The Killer 1535 Wirless Adapter is functional and the ath10k firmware is included in recent linux kernel versions. The connection speed reported by iw is limited to 1-6Mbits/s. However this is just the output being wrong. The real connection speed is not limited to this value.
Some users are experiencing issues, where the connection is dropped under heavy load but reconnects within a brief moment. This might not be noticed during browsing at all but becomes apparent in online games. There is no know solution so far."""
1670041,2017-07-10 20:21:13 UTC,"Eric,"
1670041,2017-07-10 07:36:35 UTC,Tested with http://kernel.ubuntu.com/~jsalisbury/lp1670041/ on a 2.4 GHz network.
1670041,2017-06-06 10:25:17 UTC,"I'm having the same problem. Using Dell XPS13 9360. I'm a developer but doesn't know about kernel or modules. But any kind of test, I can try to help if I have some instruction how to do it."
1670041,2017-07-07 16:00:08 UTC,"For those who want to test it, I built a test kernel with the patch posted in comment #31.  It can be downloaded from:"
1670041,2017-07-07 15:08:21 UTC,Yesterday something went wrong o_O
1670041,2017-07-07 09:26:35 UTC,"Thanks, can you now try :"
1670041,2017-07-06 22:43:04 UTC,"edumazet, i try out your path."
1670041,2017-07-06 14:33:43 UTC,skb_orphan() is not the way to go.
1670041,2017-07-08 10:25:55 UTC,"Eric,"
1670041,2017-07-06 03:13:42 UTC,"Should be the same as bug 1692836 , and there should be a fix in kernel 4.4.0-83.106"
1670041,2017-07-06 00:01:17 UTC,Also confirmed this bug on Dell XPS 15 (9560) with gnome ubuntu 17.04 and 4.10/4.12 kernels.
1670041,2017-06-30 08:02:29 UTC,"Dell XPS owner, I would also suggest you hassle Dell.. selling a laptop
with Ubuntu installed, where one of the devices doesn't even work properly
is a bit of a d1ck move. I've reported the issue with them which they
promised would be relayed to their hw team. More reports can't hurt!
Not that it helps but the card swap I mentioned earlier was effective
(better range, throughput and speed reporting now correct (I failed to
gather useful data for comparison before the card swap though)."
1670041,2017-06-29 22:38:09 UTC,"I also suffer from the same bug on dell xps 13 9360, tcp wi-fi is 5-10x slower than on other devices."
1670041,2017-06-13 18:50:24 UTC,"@kalle valeo, your patch appears to resolve this bug, but it still exists in mainline.  Do you have plans to submit this patch upstream?"
1670041,2017-06-13 12:48:10 UTC,"I have the same problemi with dell XPS 13 9360.
Here the wifi info (https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info) results, hope they are useful: http://paste.ubuntu.com/24848753/"
1670041,2017-06-12 12:30:20 UTC,"I see the same behavior as mikewiz38: via a webtest 104 Mbps download and in the graphical interface it lists as 6Mbps.
So speed is not bad - it just looks bad (on 16.04.1 with hwe kernel 4.8.0-53)"
1670041,2017-07-06 10:00:22 UTC,"acelankao,"
1670041,2017-06-11 16:18:26 UTC,"Same here, #21. I have the same poor performance on 4.12-rc4."
1670042,2017-03-04 20:11:36 UTC,"Realized that Unity might be more ""high level"" and thus might be more likely the source"
1670042,2017-03-15 19:55:25 UTC,"Might be a problem in unity or compiz. because it is a ""user facing functionality"" I target Ayatana Design instead of Unity (see https://wiki.ubuntu.com/Unity/FilingBugs)."
1670044,2020-08-11 07:25:35 UTC,libindi1:amd64 (1.4.1+r2877~201703041847~ubuntu16.04.1)
1670056,2017-03-06 04:01:23 UTC,"Ok, I think you can go ahead and make this change. The Unity file is clearly an error and it is not used in unity-control-center."
1670056,2017-03-06 04:15:00 UTC,I filed LP: #1670246 against Unity.
1670056,2017-03-06 01:46:41 UTC,"OK, I will delete the diversion in /usr/share/unity/icons/.
But searchingthedashlegalnotice.html file in /usr/share/unity/icons/ and /usr/share/unity-control-center are same in Ubuntu 14.10."
1670056,2017-03-06 03:57:16 UTC,"Wait, there actually is this file but it does not make sense."
1670059,2017-04-22 00:44:13 UTC,"Headphones also stop working after logging out and back in, until they are unplugged and plugged in again."
1670059,2017-05-25 21:10:16 UTC,"I also have this issue. Running ""alsactl restore"" will allow sound to come through the headphones without rebooting, but this is suboptimal. I have attached my alsa-info output."
1670059,2017-05-26 17:19:41 UTC,See also https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801
1670060,2019-09-25 22:47:58 UTC,"This is now handled properly, in the case where the snap is classic it is shown as such, and in the case where the snap is not classic, it cannot be installed in classic confinement. See for example a classic snap installed:"
1670060,2017-03-05 08:24:43 UTC,Mark Shuttleworth <email address hidden> writes:
1670060,2017-03-05 08:06:31 UTC,"It's in the 'Notes' column in 2.23, not sure if it was there in previous
versions."
1670060,2017-03-05 09:46:28 UTC,"Ah, I wonder if this is an interaction between a snap that asks for
classic mode, and a snap that gets TOLD to be in classic mode."
1670070,2017-03-05 03:30:46 UTC,I'm sorry!  I have the source and destination labels reversed.  gdm
1670077,2017-03-08 20:11:05 UTC,The current image is a beta release -- as of this date it is beta4. Features are still in daily flux and under development.  Once final release we will have the appropriate packaging and support structure.
1670077,2017-04-09 14:09:03 UTC,"Ok great! I'd really like the source to be able to build this, and I'm not alone:"
1670077,2017-04-30 12:02:38 UTC,Any news on this?
1670077,2017-05-24 12:43:13 UTC,"Hi Trevor,"
1670077,2017-07-25 03:57:41 UTC,"Hi Anthony,"
1670078,2017-08-11 09:48:09 UTC,Same behavior in my sandbox (Mint 17.1)
1670091,2019-06-12 10:04:13 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017."
1670098,2017-04-04 15:18:56 UTC,"I think that this is a problem with your X configuration (or maybe some interplay between the X configuration and Shutter). At least I cannot reproduce this issue on my machine... Since Shutter's development seems dead, I'd recommend to attack the problem from the X side and try to get some support from the Mint community."
1670099,2017-04-06 17:52:29 UTC,I have just updated from 18 to 18.1 and am experiencing this same issue when effects are disabled. The culprit is specifically when 'Effects on menus' is turned off.
1670099,2017-05-12 09:35:32 UTC,"I am running Mint 18.1 on a relatively old Dell PC with only 2GB of RAM. Mint runs relatively well, but quite slowly, so, I naturally decided to disable the Effects."
1670102,2018-01-03 14:45:14 UTC,This issue was fixed in the openstack/designate-dashboard 5.0.1 release.
1670102,2017-03-05 18:36:06 UTC,https://review.openstack.org/#/c/441700/
1670102,2017-10-27 21:15:23 UTC,This issue was fixed in the openstack/designate-dashboard 6.0.0.0b1 development milestone.
1670118,2017-03-05 12:46:40 UTC,"Yo estoy editando normal y de la nada se me cierra el proyecto y no se guarda, me encanta este editor y quiero que arreglen esto,tambien me gustaría que se guardara el proyecto en formato mp4 de vídeo, todo esto lo digo enserio, espero noticias."
1670122,2017-04-04 14:58:58 UTC,Can you please post a screenshot of the problem? Do you have the corresponding setting (hiding the main window during the screenshot) enabled?
1670123,2017-05-11 06:58:26 UTC,Can i work on this ?
1670123,2018-07-17 21:40:40 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/444882
Reason: See discussion on https://review.openstack.org/#/c/444591/. Feel free to restore and update if you find otherwise."
1670123,2017-12-05 14:06:51 UTC,This issue was fixed in the openstack/python-karborclient 0.7.0 release.
1670123,2017-09-21 06:49:04 UTC,"Reviewed:  https://review.openstack.org/496521
Committed: https://git.openstack.org/cgit/openstack/python-karborclient/commit/?id=1bfd6d0ee49aa501d40e8f6a9e1d882a4c92d4f1
Submitter: Jenkins
Branch:    master"
1670123,2017-08-23 06:57:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496521"
1670123,2017-08-23 06:44:34 UTC,Can I work on this ? Thanks~
1670123,2017-06-07 14:52:35 UTC,This issue was fixed in the openstack/python-muranoclient 0.13.0 release.
1670123,2017-05-23 10:26:42 UTC,"Change abandoned by NidhiMittalHada (<email address hidden>) on branch: master
Review: https://review.openstack.org/463920
Reason: Abandoned, as its not a valid bug."
1670123,2017-05-11 06:57:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463920"
1670123,2017-06-12 13:23:48 UTC,This issue was fixed in the openstack/python-ceilometerclient 2.9.0 release.
1670123,2017-05-01 02:36:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461334"
1670123,2017-04-24 17:27:06 UTC,"Reviewed:  https://review.openstack.org/444616
Committed: https://git.openstack.org/cgit/openstack/python-muranoclient/commit/?id=0b63a8d6a771bd66d3b8544ac11b34bfda84ad6c
Submitter: Jenkins
Branch:    master"
1670123,2017-04-13 11:33:48 UTC,This issue was fixed in the openstack/python-senlinclient 1.3.0 release.
1670123,2017-04-13 01:58:08 UTC,"Reviewed:  https://review.openstack.org/444617
Committed: https://git.openstack.org/cgit/openstack/python-senlinclient/commit/?id=5aada5194e4a101c1daf38f67a49370597700969
Submitter: Jenkins
Branch:    master"
1670123,2017-03-13 12:48:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444882"
1670123,2017-03-12 02:15:17 UTC,"This doesn't materially improve trove, we're moving to osc anyway. this strikes me as being of little value."
1670123,2017-03-12 01:48:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444617"
1670123,2017-03-12 01:30:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444616"
1670123,2017-03-11 15:45:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444591"
1670123,2017-05-01 03:08:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461337"
1670123,2017-03-05 14:10:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441675"
1670137,2020-03-16 19:08:45 UTC,I'm closing this bug due to inactivity for over a year.
1670137,2018-04-12 17:11:15 UTC,"@mahmoh, does Joseph's workaround script help?"
1670137,2017-09-21 02:07:48 UTC,I've attached my workaround script. To use:
1670137,2017-09-19 09:58:31 UTC,"@Joseph, out of interest for users seeing the same issue, can you supply the script so others can use this as a temporary workaround?"
1670137,2017-07-07 14:32:05 UTC,"That info is from:
zpool status -v"
1670137,2017-05-05 14:58:37 UTC,"I am also seeing this issue with zfs and l2arc cache on an NVMe and 4.10.14 on zesty. I've seen it in the past with btrfs, and a bcache cache on NVMe as well, but not with the bcache cache on a SATA SSD. I will move my zfs l2arc cache to a SATA SSD to see if that fixes suspend. This is probably an issue in the NVMe kernel stack."
1670137,2017-06-06 16:57:42 UTC,I can confirm that the problem does not happen when cache is on SATA vs. NVME.  I assume this needs to get pushed to the kernel then?  Please advise.
1670137,2017-03-10 14:27:12 UTC,I think this is more of an symptom of the cache being located on an NVMe drive which are notorious for causing power problems.  I'm closing this until I can validate on a non-NVMe drive.
1670137,2017-03-05 15:59:26 UTC,Same results with 4.8 kernel & pm_trace as above:
1670137,2017-03-05 15:28:23 UTC,"Occurs while suspend to ram, attempted pm_trace (sudo sh -c ""sync && echo 1 > /sys/power/pm_trace && pm-suspend""):
...
[    1.196689] Key type encrypted registered
[    1.196712] AppArmor: AppArmor sha1 policy hashing enabled
[    1.442937] evm: HMAC attrs: 0x1
[    1.444273]   Magic number: 12:578:178
[    1.444323] acpi device:0e: hash matches
[    1.444345]  platform: hash matches
[    1.444671] rtc_cmos 00:02: setting system clock to 2016-12-22 12:09:40 UTC (1482408580)
[    1.444925] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    1.444927] EDD information not available.
[    1.445014] PM: Hibernation image not present or could not be loaded.
[    1.445962] Freeing unused kernel memory: 1480K (ffffffff81f42000 - ffffffff820b4000)
..."
1670137,2017-03-05 15:00:41 UTC,Precision 5510 BIOS version: 1.2.19 (latest)
1670137,2017-07-06 12:15:33 UTC,"Hi mahmoh,"
1670146,2017-03-08 18:13:13 UTC,"Where is the newer version of Qt coming from? [1] seems to have it as a part, [2] seems to just assume it's on the system somewhere. If the `qt-version` option was made a string instead of an enum, and validated against `qtchooser -list-version`, would that work? It would then set QT_SELECT to the right thing. I'm not certain that this would work if the newer Qt is a part though, it would require some experimentation."
1670146,2017-03-10 08:51:26 UTC,"Based on a chat with Tim my understanding is that this is about building against a Qt version that's in a part but not in the archives. The Liri Calculator uses the LiriOS platform snap¹ which is based on Qt 5.8 which isn't in the archive, and apps must be built against the same headers. The platform snap doesn't provide any header files. The same problem exists with the upstream Qt 5.8 snap² that Timo made."
1670146,2017-03-11 09:24:19 UTC,"As Christian said. Additionally there's also a possible use case for standalone apps
(not using any sort of platform snap) but still wanting to build against a Qt installation
not provided by the system archives but somewhere on the filesystem (e.g.
~/Qt/5.9/...)."
1670149,2017-03-15 15:54:37 UTC,"Marking as Incomplete, no diagnostic snapshot. Please reopen if reproduced."
1670149,2017-04-18 10:36:27 UTC,"Here there is a similar error
https://ci.fuel-infra.org/job/10.0-community.main.ubuntu.bvt_2/1446"
1670162,2017-03-05 20:22:05 UTC,This is not a snapcraft error but a store/click-review thing.
1670162,2017-03-05 20:24:36 UTC,Oh and the publish comment was not directed at you bug reporter! :-)
1670162,2017-03-05 20:25:13 UTC,This needs to be fixed in snapcraft: snapcraft/storeapi/errors.py:        'Publishing checks failed.\n'
1670162,2017-03-06 15:03:52 UTC,I'll figure out a way to make this per-snap overrideable. The test is important due to bug #1643910.
1670162,2017-03-20 18:07:32 UTC,This is now fixed in the review tools in the store so marking that task Fix Released.
1670173,2018-03-14 14:46:30 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1670175,2017-04-07 14:14:14 UTC,Looks like tribblix is an OpenSolaris variant from the above output (I normally tend to test with Milax but it's good to have another reference around).
1670175,2017-04-07 22:45:48 UTC,"Hi Mark, thank you for your effort on SPARC64 emulation in QEMU!"
1670175,2017-12-19 11:16:15 UTC,With QEMU 2.11 there are two new warnings I haven't seen before (execution was still the same):
1670175,2019-12-06 02:52:48 UTC,qemu sparc64 also failed to boot Oracle Linux
1670175,2020-11-08 09:15:28 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1670175,2020-11-10 14:25:42 UTC,"This is still valid, setting to Confirmed.  With the latest qemu as of today, it fails in a slightly different way, but still does not accept any keyboard input:"
1670175,2017-03-09 08:00:49 UTC,This is how it ends with 2048 MB of memory instead of 1024:
1670175,2017-03-21 14:18:04 UTC,QEMU 2.8.90 gets a bit further with Tribblix:
1670179,2017-10-26 04:56:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670181,2017-03-06 07:12:24 UTC,"Hi,"
1670182,2017-03-08 12:21:13 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1670182,2017-03-07 16:20:06 UTC,"Reviewed:  https://review.openstack.org/442441
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=21a29ebbede160a78aca96fa3fa0432f209ba17e
Submitter: Jenkins
Branch:    stable/ocata"
1670182,2017-03-05 20:52:39 UTC,"Yeah, I can confirm that - we create 'modules' symlink in /etc/puppet/modules which points to /etc/puppet/modules/ thus, we have 2 copies of tasks being uploaded at the same time to the API"
1670182,2017-03-06 11:58:18 UTC,"Reviewed:  https://review.openstack.org/441704
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=a646ae6a131fa15fc77b6497f1b7f918656fee8b
Submitter: Jenkins
Branch:    master"
1670182,2017-03-07 12:41:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442441"
1670182,2017-03-05 20:10:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441704"
1670183,2017-03-06 04:11:21 UTC,"Are you using an intel processor? I have experienced this, when i switch the graphics to CPU, try switching it to GPU."
1670183,2017-03-11 14:50:15 UTC,"Yes, i use a Intel processor."
1670201,2017-08-08 18:15:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670206,2017-03-27 18:00:59 UTC,"Change abandoned by Vladimir Kuklin (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/441714"
1670206,2017-03-08 12:21:10 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1670206,2017-03-05 22:37:32 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/441714"
1670206,2017-03-07 12:42:09 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442444"
1670206,2017-03-06 20:45:10 UTC,"Reviewed:  https://review.openstack.org/441713
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=8df6ddde303da0dfc43569de55d0f07d196024c2
Submitter: Jenkins
Branch:    master"
1670206,2017-03-07 16:20:56 UTC,"Reviewed:  https://review.openstack.org/442444
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=3b1a9be42bc20fcbf51c1ec788b7a9d98b840da3
Submitter: Jenkins
Branch:    stable/ocata"
1670206,2017-03-05 22:36:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441713"
1670208,2017-03-05 22:59:59 UTC,"Gunnar, do you want to try just duplicating line 31 and changing .png to .svg ?"
1670208,2017-03-06 11:31:24 UTC,"Yep, that works. So does changing line 31 to:"
1670208,2017-03-06 12:36:13 UTC,"Gunnar, great. Could you submit a patch against
https://anonscm.debian.org/cgit/collab-maint/python-distutils-extra.git"
1670208,2017-03-06 13:08:10 UTC,"Hi Martin,"
1670208,2017-03-06 13:24:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670212,2020-06-02 09:16:26 UTC,Fixed in https://review.opendev.org/#/c/586392/
1670212,2019-04-12 14:32:11 UTC,"Change abandoned by zhulingjie (<email address hidden>) on branch: master
Review: https://review.openstack.org/570389"
1670212,2017-03-06 11:33:06 UTC,ansible version
1670212,2017-03-06 11:29:36 UTC,"Docker version 1.12.3, build 6b644ec (this version i got through automatic host bootstrap script)"
1670212,2018-05-24 11:23:04 UTC,"I am also experiencing the same error on Ubuntu 16.04 deploying queens
It's simply because keystone cannot bind to port 5000, it's already bound by the insecure registry."
1670212,2017-03-06 03:17:29 UTC,"Can you give more information about your system? which version of Ansible, docker,..."
1670213,2017-03-08 12:21:12 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1670213,2017-03-07 12:41:58 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442443"
1670213,2017-03-07 11:00:43 UTC,"Reviewed:  https://review.openstack.org/441722
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=c06bbe8263f4cadf3716e14c30eab3f85348a70c
Submitter: Jenkins
Branch:    master"
1670213,2017-03-05 23:18:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441722"
1670213,2017-03-07 16:20:38 UTC,"Reviewed:  https://review.openstack.org/442443
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=8affd9d25f180eb7d2ed4959a79827016749c699
Submitter: Jenkins
Branch:    stable/ocata"
1670214,2019-03-02 02:31:43 UTC,This will be fixed in Hitori 3.31.92 (because of the app icon redesign).
1670220,2017-03-06 00:41:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441724"
1670220,2017-03-07 11:03:14 UTC,"Reviewed:  https://review.openstack.org/441724
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=bd3584fb17c91699c2ba786e0e27dc04ebf3cf00
Submitter: Jenkins
Branch:    master"
1670220,2017-03-07 16:21:14 UTC,"Reviewed:  https://review.openstack.org/442445
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=08f311f1fac666cde0bde9ab09b80712b73a7f3d
Submitter: Jenkins
Branch:    stable/ocata"
1670220,2017-03-08 12:21:09 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1670220,2017-03-07 12:42:20 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442445"
1670229,2017-03-06 04:26:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1670230,2018-09-05 08:51:51 UTC,Comments moved to storyboard
1670230,2017-03-06 10:45:49 UTC,"The version is python-openstacksdk==0.9.14, python-openstackclient==3.8.2"
1670230,2017-04-24 06:40:58 UTC,"actually, i have read the part of codes of update_subnetpool(), and subnetpool do not support ""openstack subnet pool unset"" command. subnetpool just support to enlarge prefies operation:"
1670230,2018-09-04 11:13:26 UTC,"Confirmed on stable rocky release, the subnet pool update only allows to expand the existing prefixes:
https://github.com/openstack/neutron/blob/13.0.0/neutron/db/db_base_plugin_v2.py#L89"
1670230,2018-09-04 15:51:48 UTC,"For reference, fix to get actual error is https://review.openstack.org/#/c/571101/ (Rocky and newer)"
1670230,2017-03-06 06:04:00 UTC,Can you provide info on which sdk version and OSC version you were using.
1670232,2020-01-31 19:51:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670239,2017-03-09 12:29:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443604"
1670239,2017-03-10 01:52:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444061"
1670239,2017-03-10 02:14:36 UTC,"Change abandoned by Hao Li (<email address hidden>) on branch: master
Review: https://review.openstack.org/444061
Reason: Repeat commit"
1670239,2017-03-10 06:10:54 UTC,"We should change ./etc/ironic/rootwrap.d/ironic-lib.filters in ironic project.
add
udevadm: CommandFilter, udevadm, root
Because we still need it to avoid gate breakage and preserve compatibily with existing installation."
1670239,2017-03-10 06:24:28 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/444109"
1670239,2017-04-03 14:51:42 UTC,"So it seems like this should be fixed in the ironic_lib. IPA should move to using ironic_lib scripts. So, on IPA side, I think the bug can be closed as duplicate of https://bugs.launchpad.net/ironic-python-agent/+bug/1557542. On ironic side there should be no changes, so I'm closing it on ironic project."
1670239,2017-04-03 14:52:59 UTC,"Hrm, I see you 're adding new rules in ironic, so leaving it open there for now."
1670239,2017-08-24 15:14:59 UTC,"hit this bug too, fixed by using master CoreOS images"
1670239,2020-06-22 10:10:15 UTC,"Change abandoned by Riccardo Pittau (<email address hidden>) on branch: master
Review: https://review.opendev.org/444109
Reason: inactivity"
1670239,2020-07-02 13:22:31 UTC,"Change abandoned by Riccardo Pittau (<email address hidden>) on branch: master
Review: https://review.opendev.org/443604
Reason: obsolete"
1670243,2017-12-03 12:20:23 UTC,"I'm pushing back because I'm not convinced this is solving an actual problem, and it's not a trivial change. Do you actually have digitized documents from before 1901 that you want to import into Bazaar/Breezy."
1670243,2017-12-03 23:54:01 UTC,Do you plan to support Python 2.7 ? There will be not fix in Python 2.7
1670243,2017-12-03 02:26:22 UTC,"Anything before 1900 gives an error on 64-bit as well, even with your fixes. Practically speaking, why do you need to set timestamps after 2039 ? Can't we just error when timestamps after 2039 are specified?"
1670243,2017-12-03 02:10:16 UTC,"Jelmer it's an issue because you can set the date you want, and it will works on some systems and fail on windows and 32-bit ones."
1670243,2017-12-03 03:19:13 UTC,Jelmer you are clearly blocking on this clean and simple fix for no reason.
1670243,2017-12-21 16:41:16 UTC,That's still not clear to me.
1670243,2017-12-04 14:53:41 UTC,"> Yes, we're planning to support Python 2.7.
"
1670243,2017-12-03 01:00:58 UTC,Why is this actually an issue? No revisions in the wild should have been created before 2004 and nothing should currently exist beyond 2017; it will take another 22 years (when these Windows versions are long deprecated) before revisions with those timestamps will be created.
1670243,2017-12-04 11:30:15 UTC,"On Sun, Dec 03, 2017 at 11:54:01PM -0000, Florent Gallaire wrote:

> Do you plan to support Python 2.7 ? There will be not fix in Python 2.7


Yes, we're planning to support Python 2.7."
1670251,2017-03-09 11:21:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443588"
1670255,2017-08-03 13:52:36 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/490484"
1670255,2017-08-03 12:05:20 UTC,https://review.openstack.org/490447
1670255,2017-08-08 02:13:49 UTC,"Reviewed:  https://review.openstack.org/490484
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=bcb338f8b30eee144edbd21be5e54e9d80f7549f
Submitter: Jenkins
Branch:    master"
1670264,2017-03-06 06:25:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441758"
1670264,2017-03-06 06:26:13 UTC,"I just make a shotcut fix. If someone wants to take this, please let me know. thanks"
1670268,2020-04-04 14:49:47 UTC,I think the sentence should be change to
1670268,2020-04-04 14:34:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670268,2017-03-17 12:47:03 UTC,Oh certainly; you've just gotten me very curious about this mass noun concept now.
1670268,2017-03-16 21:00:00 UTC,"dictionary.com is an American site, so I doubt that this is specific to British English.  It's possible that you might need to talk to linguistics majors rather than English majors, though, since in many places English courses don't have the same focus on syntax and grammar that you often find in linguistics courses."
1670268,2017-03-15 13:47:10 UTC,So what makes it a mass noun rather than an irregular noun like fish?
1670268,2017-03-14 17:35:20 UTC,"Yeah, I was reading the second sentence as a reference to the ""license terms"" from the previous sentence. That's why the ""is"" threw me off. A rewording may be the best option."
1670268,2017-03-14 14:25:57 UTC,"Strange... 5 years of college prep school and 2 years of studying Latin and I never heard the terms ""mass noun"" and ""count noun"".  Neither have my friends who were English majors."
1670268,2017-03-08 00:07:40 UTC,"Software is a mass noun, not a count noun, so ""These software are ..."" is ungrammatical no matter which way you slice it."
1670268,2017-03-06 20:40:38 UTC,"I guess the contrary view is that ""some"" refers to ""license terms"", in which case it would indeed be grammatical to use plural agreement.  Again, it's probably best to reword so that it's clear what the quantifier is actually referring to."
1670268,2017-03-06 20:28:28 UTC,"I disagree.  This is an elided version of ""Some [of this software] is proprietary"", which is perfectly grammatical.  While ""Some are proprietary"" would be a grammatical sentence in isolation, it would be incorrect in this context, because ""software"" is not a count noun and so there is no plural referent available."
1670268,2017-03-14 16:59:43 UTC,"It's a pretty standard grammatical term, though local names for the concept may of course vary."
1670268,2017-03-07 14:07:46 UTC,"Shouldn't the whole thing be plural since it is referring to multiple different software packages, each of which has its own license?  So:"
1670269,2017-06-28 06:48:53 UTC,Any news on this?
1670269,2017-07-03 05:19:00 UTC,I can reproduce this with artful
1670269,2017-08-21 18:38:21 UTC,"I believe latest usb-gtk-creator doesn't use this function at all instead open the whole gui with pkexec, and hence not compatible with wayland."
1670271,2017-09-26 22:50:08 UTC,Unassigning due to no activity for > 6 months.
1670271,2017-03-24 10:23:11 UTC,This issue was fixed in the openstack/openstack-manuals 15.0.0 release.
1670277,2017-03-06 08:07:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441785"
1670277,2017-03-06 07:45:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441777"
1670291,2018-12-07 09:21:23 UTC,"An upload of landscape-client to bionic-proposed has been rejected from the upload queue for the following reason: ""Includes a change without an SRU bug attached to it""."
1670291,2018-10-04 18:04:39 UTC,"I have still have two machines that need upgrading from 14.04 -> 16.04 -> 18.04. I want to replace them and test the upgrade in the lab.
The upgrade from 16.04->18.04 also fails. I'll report it in a new ticket."
1670291,2018-10-10 15:49:07 UTC,"Hello Damiön, or anyone else affected,"
1670291,2018-10-22 14:50:05 UTC,"root@subtle-cobra:~# dpkg-query -W systemd
systemd	229-4ubuntu21.4
root@subtle-cobra:~# systemctl mask systemd-logind
Created symlink from /etc/systemd/system/systemd-logind.service to /dev/null.
root@subtle-cobra:~# systemctl stop systemd-logind
root@subtle-cobra:~# shutdown +1
Failed to set wall message, ignoring: Unit systemd-logind.service is masked.
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Unit systemd-logind.service is masked.
root@subtle-cobra:~# echo $?
1
root@subtle-cobra:~# sleep 60"
1670291,2018-10-24 19:44:13 UTC,This bug was fixed in the package systemd - 229-4ubuntu21.5
1670291,2018-10-24 19:44:39 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1670291,2018-10-26 18:25:19 UTC,I'm going to upgrade a system from 14.04.5 to 16.04.x tomorrow at 10:00AM CEST so I'll let you know the results.
1670291,2018-10-28 06:04:22 UTC,Ok so this is still FUBAR but then on a higher level.
1670291,2018-10-28 06:07:34 UTC,One quick little rant.
1670291,2018-09-17 16:22:16 UTC,This bug was fixed in the package systemd - 239-7ubuntu8
1670291,2018-11-19 14:02:46 UTC,"Hello Damiön, or anyone else affected,"
1670291,2018-11-20 12:05:08 UTC,"Hello Damiön, or anyone else affected,"
1670291,2018-11-27 21:40:30 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu6
1670291,2018-12-07 09:23:13 UTC,"An upload of landscape-client to trusty-proposed has been rejected from the upload queue for the following reason: ""Includes a change without an SRU bug attached to it""."
1670291,2018-12-04 11:04:45 UTC,"Testing systemd 237-3ubuntu10.10, with masked and stopped systemd-logind, `sudo shutdown +1` command proceeds to shutdown in a VM."
1670291,2018-12-07 09:19:37 UTC,"An upload of landscape-client to cosmic-proposed has been rejected from the upload queue for the following reason: ""Includes a change without an SRU bug attached to it""."
1670291,2018-12-07 09:22:42 UTC,"An upload of landscape-client to xenial-proposed has been rejected from the upload queue for the following reason: ""Includes a change without an SRU bug attached to it""."
1670291,2018-10-28 10:49:44 UTC,So physically at the machine it was only possible to log into the command prompt. There is no graphical interface available.
1670291,2018-09-10 17:05:09 UTC,"Yeah, this is all still broken upstream. If dbus call to schedule shutdown, fails, immediate shutdown is not actually in fact attempted."
1670291,2018-09-10 16:42:08 UTC,"Reading modern systemctl code, if the scheduling fails, the intention is to immediately shutdown."
1670291,2017-03-06 09:21:57 UTC,Was able to reboot by sshing into the machine and rebooting with error message but it still went through with the reboot.
1670291,2017-03-15 21:33:36 UTC,This does not require landscape-client. It can be reproduced via:
1670291,2017-03-15 21:37:13 UTC,Here's the bug report (from ubuntu-bug /sbin/shutdown):
1670291,2017-03-22 20:45:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670291,2017-05-22 10:04:57 UTC,Remove zesty task; added xenial task.
1670291,2017-09-04 15:56:39 UTC,"Hello, I've looked more into this."
1670291,2018-02-20 15:24:57 UTC,"Ping, has above been implemented in landscape? to attempt poweroff, then -f poweroff, then -ff poweroff?"
1670291,2018-02-20 22:20:31 UTC,"@xnox: not as of yet, no.  it's still in our backlog."
1670291,2018-09-10 16:43:19 UTC,https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c#L8548
1670291,2018-02-26 20:50:19 UTC,Could we please use
1670291,2018-08-20 10:11:20 UTC,Seems like there's two issues here which I'll address in separate PRs to the landscape-client:
1670291,2018-08-24 11:44:46 UTC,"I've now pushed a PR which should alleviate the reboot issue *partially*. The complexity in fixing this arises from the differing behaviours of implementations of the shutdown, poweroff, and reboot commands; upstart's poweroff & reboot commands for example, immediately return (briefly) permitting the caller to query their exit codes. In contrast, systemd's don't return at all unless the poweroff or reboot fails. None of the reboot or poweroff implementations provide a scheduling facility like the /sbin/shutdown implementation (unsurprisingly), but systemd's poweroff and reboot commands *do* work even in the post-trusty upgrade environment (even though systemd's shutdown command doesn't)."
1670291,2018-09-03 10:47:59 UTC,"In general, scheduling with shutdown command should work. E.g. tested in lxd container that `$ sudo shutdown +4` works correctly."
1670291,2018-09-03 15:19:00 UTC,"@xnox Scheduling with /sbin/shutdown normally does work ... however, what we're dealing with here is the anomalous situation of an instance which starts off as trusty and is upgraded to xenial. During the upgrade process, the /sbin/shutdown implementation is changed from the upstart one to the systemd one. At the end of the process, /sbin/shutdown is (unsurprisingly) a link to systemctl ... but it doesn't work because it's expecting to be able to talk to systemd which isn't fully operational until a reboot. As Landscape is expecting to be able to reboot via /sbin/shutdown the user relying on Landscape in such a scenario finds themselves in a bit of a bind (having to have some other means of dealing with the server, like SSH)."
1670291,2018-09-03 16:40:54 UTC,"/sbin/shutdown, post upgrade not working, imho is a severe bug. I'll investigate that. I suspect that because we cannot restart dbus things don't show up there, but /sbin/shutdown should be smart enough to do something. I guess the scheduling of timeout is failing, but /sbin/shutdown now works?"
1670291,2018-09-04 10:35:57 UTC,"> /sbin/shutdown, post upgrade not working, imho is a severe bug
"
1670291,2018-09-10 16:26:48 UTC,"Note to self, I wonder if:
https://github.com/systemd/systemd/commit/c68867da320de296917820e5a76e902a8a86be5a
https://github.com/systemd/systemd/commit/7f96539d45028650f2ba9452095473a9c455d84b"
1670291,2018-09-10 16:37:13 UTC,"Heh, I believe there are historical options re -H -h. As a wild guess, i looked at the sysvinit implementation in Debian (we have removed the package in Ubuntu) it has this:"
1670291,2018-06-07 19:24:36 UTC,"For landscape, we will try systemctl reboot, and systemctl -f reboot, this warning in the manpage:"
1670291,2018-12-14 11:49:24 UTC,"Hello Damiön, or anyone else affected,"
1670291,2018-12-14 12:09:43 UTC,"Hello Damiön, or anyone else affected,"
1670291,2018-12-14 11:56:39 UTC,"Hello Damiön, or anyone else affected,"
1670291,2018-12-14 11:52:16 UTC,"Hello Damiön, or anyone else affected,"
1670291,2019-10-10 02:41:46 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.31
1670291,2019-10-08 12:25:25 UTC,verified with 237-3ubuntu10.31:
1670291,2019-10-03 23:27:51 UTC,@kat-amsterdam
1670291,2019-10-03 18:01:09 UTC,"I saved one 14.04.5 machine for this purpose.
Will I be able to enabled -proposed for 14.04.5 even though it's now out of support?"
1670291,2019-10-01 02:59:52 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1670291,2019-09-30 20:32:32 UTC,"Hello Damiön, or anyone else affected,"
1670291,2019-02-07 19:43:51 UTC,This bug was fixed in the package landscape-client - 14.12-0ubuntu6.14.04.4
1670291,2019-09-30 21:32:26 UTC,"Hello Damiön, or anyone else affected,"
1670291,2019-02-07 19:36:27 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu4.1
1670291,2019-02-05 23:11:40 UTC,"I tested successfully landscape-client and landscape-common packages from {trusty,xenial,bionic,cosmic}-proposed. As in the test case, masked systemd-logind."
1670291,2019-02-07 19:42:54 UTC,This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.5
1670291,2019-02-07 19:38:16 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu3.2
1670294,2017-03-06 09:16:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441825"
1670294,2017-03-08 02:09:32 UTC,"Change abandoned by Michael Davies (<email address hidden>) on branch: master
Review: https://review.openstack.org/441825"
1670296,2017-03-06 12:46:05 UTC,This ticket would be obsoleted by https://bugs.launchpad.net/ubuntu/+source/coturn/+bug/1666456.
1670298,2017-03-08 11:11:02 UTC,"Use driver Intel on Sandybridge Graphics.
I update driver with ""Intel Graphics Update Tool v.2.0.2"".
Updating solved problem.
Old driver have random bug, with gnome-shell.
Ty for attention."
1670300,2017-03-06 09:39:57 UTC,This is a tracking bug for redhat issue. Solution waiting from redhat
1670300,2017-03-07 00:12:33 UTC,"Bug 1428826 - undercloud fails to deploy due to docker-registry service not found
https://bugzilla.redhat.com/show_bug.cgi?id=1428826"
1670300,2017-03-11 01:17:42 UTC,Redhat bug. Fix verified.
1670300,2017-03-20 23:21:47 UTC,When the new release comes with the Fixed?  Is there any workaround ?
1670300,2017-03-21 03:04:37 UTC,Got the workaround .. able to install successful.
1670300,2017-04-26 15:08:38 UTC,"Hello Balihar,"
1670303,2018-06-29 17:07:39 UTC,"Has this ever been fixed? This is pretty nasty, and brings down the whole Docker swarm cluster."
1670303,2017-05-10 06:05:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670303,2017-03-06 14:14:33 UTC,"WORKAROUND: if the other application which needs to bind to a UDP port can be configured to bind to a specific interface, then you can make isc-dhcp-server bind to a different interface in dhcpd.conf. e.g."
1670303,2017-05-10 06:40:22 UTC,IMHO this is an important bug because it randomly interferes with other applications - lots of which use  defined ports above 1024.
1670303,2017-03-06 10:24:50 UTC,strace shows that dhcpd is binding to explicit ports which it has chosen itself:
1670307,2017-03-06 10:08:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441860"
1670307,2017-09-11 06:52:43 UTC,"Change abandoned by Madhuri Kumari (<email address hidden>) on branch: master
Review: https://review.openstack.org/441860"
1670313,2020-07-26 18:15:56 UTC,Thank you for the advice!
1670313,2020-07-26 18:25:55 UTC,Now I fixed my gaming site https://wageringadvisors.co.uk/best-5-deposit-casinos/ and all work good!
1670318,2017-03-06 10:55:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441875"
1670318,2018-06-07 09:35:27 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/441875"
1670323,2017-03-11 13:35:11 UTC,Ok this seems to be being triggered by the name= parameter in the setup.py matching the name of a module in the requirements.txt.  This likely should trigger a warning at least.
1670323,2017-03-15 15:57:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670336,2017-03-06 20:30:25 UTC,"The attachment ""ecryptfs-setup-swap_patch_to_work_with_swapfiles.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1670336,2017-11-18 10:48:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670336,2017-11-12 13:28:29 UTC,"Since ubiquity does not run ecryptfs-setup-swap as chroot, there is also another problem: unencrypted swapfile entry in /etc/fstab is not commented out as it should, so you get"
1670336,2017-11-11 09:50:39 UTC,"This is because Ubiquity has not been patched yet.
I had already pointed out the problem in this thread:"
1670336,2017-11-10 21:24:42 UTC,Problem still exists in17.10/Artful:
1670336,2017-03-06 18:04:59 UTC,"I patched ecryptfs-setup-swap and now it works.
The first modification is to avoid to run udevadm on a file (you get a ""device node not found"" error, harmless but annoying)
The second modification is to put filename instead of UUID in /etc/crypttab if you have a swap file and not a swap partition.
The third modification is to actually restart cryptdisk, since ""/etc/init.d/cryptdisks restart"" does nothing (see http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/cryptsetup/vivid/view/head:/debian/cryptdisks.init ), the right command is ""systemctl restart cryptsetup.target"""
1670336,2017-09-27 15:59:37 UTC,This bug was fixed in the package ecryptfs-utils - 111-0ubuntu5
1670336,2017-09-01 13:09:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1670336,2017-09-01 10:15:06 UTC,"The latest Artful daily (3108) also suffers from slow boot times after installation with an encrypted home folder. Please, if I can provide developers with any debug info about this, I'm happy to help - just tell me what to provide."
1670336,2017-06-20 13:22:07 UTC,"Confirming that changing the cryptsetup line to:
cryptswap1 /swapfile /dev/urandom swap,offset=1024,cipher=aes-xts-plain64
solved the boot time."
1670336,2017-06-16 19:15:18 UTC,"I've been looking at this issue. The linked merge proposal for ecryptfs-utils almost gets us there. I've got a cleaned up version that I've been testing with. Unfortunately, I run into an issue in the systemd generated swap unit for the swapfile. It does something a little different for swap files than it does for swap partitions and my testing VM sometimes hangs (infinitely) during boot waiting on the swap unit to start. I still need to do more investigation to understand the problem and come up with the correct solution there."
1670336,2017-09-29 16:54:59 UTC,The fix works! :)
1670336,2017-05-15 10:17:42 UTC,Can confirm that Alberto Pianon's workaround of changing a line in /etc/crypttab fixes the problem (system no longer hangs on boot). Confirmed on Kubuntu and Ubuntu 17.04 on systems that had their home folders encrypted upon install.
1670336,2017-06-16 18:59:39 UTC,"I can confirm this bug on a fresh install of Ubuntu, Ubuntu MATE and Xubuntu.
The workaround of changing the crypttab to point to /target/swapfile fixes the problem."
1670336,2017-03-06 23:26:44 UTC,Dimitri - Could you have a look at this? I believe you worked on the encrypted swap changes.
1670336,2017-03-07 15:00:17 UTC,"I have run again the Ubuntu 17.04 installer on a virtual machine, with the ""encrypted home folder"" option.
I confirm that in such case even the unencrypted swap is not activated after boot.
In particular:"
1670336,2017-03-11 15:48:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670336,2017-03-07 08:26:02 UTC,"Maybe also Ubiquity needs to be patched, I am not sure since I did not have time to test it yet."
1670336,2017-03-14 14:55:39 UTC,This looks pretty similar to bug #1668535.  Should one of these be marked as a duplicate?
1670336,2017-03-14 15:41:23 UTC,It seems that they are two different things.
1670336,2017-03-14 16:27:42 UTC,"Aha.  Alberto, thanks for the helpful explanation!"
1670336,2017-03-19 08:42:58 UTC,"Dimitri,"
1670336,2017-03-11 15:50:15 UTC,I just tried to install Ubuntu 17.04 from a daily build and ran into this too.
1670343,2017-05-01 18:42:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670343,2017-09-21 10:58:48 UTC,"I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive"
1670348,2017-03-06 14:29:39 UTC,"workaround is adding
  db:
    tls:
       enabled: false
into the .ccp.yaml"
1670352,2017-03-10 06:03:19 UTC,"Document the cron-format backup schedule in the config, and the new wal-e-backup action while I'm there (assuming it is landed)"
1670354,2017-03-07 12:42:31 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442446"
1670354,2017-03-07 16:21:37 UTC,"Reviewed:  https://review.openstack.org/442446
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=7d31faff6f7ced4d5419c03073a838c427ae2dcf
Submitter: Jenkins
Branch:    stable/ocata"
1670354,2017-03-08 12:21:07 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1670354,2017-03-06 14:06:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/441951"
1670354,2017-03-07 11:01:28 UTC,"Reviewed:  https://review.openstack.org/441951
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=1bbe3869f7257d3a6291fb0b11d4b5b8efa79530
Submitter: Jenkins
Branch:    master"
1670356,2017-03-10 08:43:26 UTC,"From you description, I'd argue that we can't do much here, that's EC's job."
1670356,2017-03-10 08:55:06 UTC,Thanks; I had been looking at the hid-multitouch and i2c-hid source and was increasingly wondering if it was a BIOS/hardware issue. I'll raise the issue with Dell.
1670356,2017-03-10 07:40:00 UTC,"IIUC, the laptop wakes up because the screen somehow touched the touchpad when lid closed, right?"
1670356,2017-03-06 20:35:06 UTC,"Thank you. Testing on 4.11.0-041100rc1-generic yields exactly the same result, testing with various values of /proc/acpi/wakeup and removed/inserted i2c-hid and hid-multitouch modules: the laptop wakes from suspend upon touching the touchpad unless the touchpad was manipulated between removing the modules and suspending, or during the suspend process."
1670356,2017-03-06 13:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1670356,2017-03-10 08:15:07 UTC,That's correct; the screen presumably touches the touchpad when closing the lid. I've been testing by simply suspending and then touching the touchpad to wake the laptop (it doesn't require pressing the touchpad button; simply registering a touch works).
1670356,2017-03-06 14:00:00 UTC,apport information
1670356,2017-03-06 13:59:57 UTC,apport information
1670356,2017-03-06 13:59:54 UTC,apport information
1670356,2017-03-06 13:59:52 UTC,apport information
1670356,2017-03-06 13:59:50 UTC,apport information
1670356,2017-03-06 13:59:48 UTC,apport information
1670356,2017-03-06 13:59:46 UTC,apport information
1670356,2017-03-06 15:15:05 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1670356,2017-03-06 13:59:43 UTC,apport information
1670356,2017-03-06 13:59:41 UTC,apport information
1670356,2017-03-06 13:59:39 UTC,apport information
1670356,2017-03-06 13:59:37 UTC,apport information
1670356,2017-03-06 13:59:35 UTC,apport information
1670356,2017-03-06 13:59:33 UTC,apport information
1670356,2017-03-06 13:59:45 UTC,apport information
1670356,2017-03-06 13:59:31 UTC,apport information
1670360,2017-03-14 10:51:28 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445426"
1670360,2017-03-14 11:47:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/445450"
1670360,2017-03-14 11:47:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445451"
1670360,2017-03-14 12:50:03 UTC,"@snovikov, you are right, networks assignment is wrong here. The network should be assigned to bond itself, not to its slaves. And every network can be assigned just once on each node."
1670360,2017-03-15 11:37:55 UTC,"Reviewed:  https://review.openstack.org/445426
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=199bcb1be6655711bdc68b7b431f8e4035e1d5e0
Submitter: Jenkins
Branch:    stable/newton"
1670360,2017-03-15 11:38:04 UTC,"Reviewed:  https://review.openstack.org/445451
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=682675c33e08377c1333fb33c80875865121c694
Submitter: Jenkins
Branch:    master"
1670360,2017-03-15 11:38:30 UTC,"Reviewed:  https://review.openstack.org/445450
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=e02a4c0435d5ce6e503896e3540c4f776462b22a
Submitter: Jenkins
Branch:    stable/ocata"
1670371,2017-03-06 18:44:12 UTC,Running sudo /usr/lib/snapd/snap-discard-ns  <snap> fixes it. Sounds related to lp:1645731
1670371,2017-03-06 18:49:43 UTC,Confirmed. This is particularly weird considering a few things:
1670384,2017-03-06 15:15:48 UTC,I'm pretty sure we have tests for exactly this. I'll dig a little.
1670384,2017-03-06 16:23:54 UTC,"To be clear, there's several things going on which need fixing:
1. It's letting you refresh to the same revision as you currently have, and having allowed it, then proceeds to try to do something other than saying ""done!"".
2. it's failing to do the install
3. having failed, it's not cleaning up after itself"
1670384,2017-03-06 18:01:50 UTC,"Thanks, John. If this is not the way to toggle devmode/jailmode, then maybe
that is a #4. The right way isn't possible or isn't more obvious."
1670388,2017-03-07 14:00:33 UTC,"These are the constraints of a classic snap. The developer of such snap would need to setup environment variables if needed to not accidentally pollute the environment. If execution is the problem, the use the relative path in prime to the command."
1670388,2017-03-07 14:01:54 UTC,we can make the error message clearer about this though.
1670388,2017-03-07 14:30:57 UTC,"If there is an error message about it (Note that there is none presently, only at runtime), yeah, I guess that's okish."
1670388,2017-03-10 01:17:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670390,2017-03-24 01:58:38 UTC,This bug was fixed in the package unity8 - 8.15+17.04.20170321-0ubuntu1
1670390,2017-04-06 09:53:46 UTC,This bug was fixed in the package gtk+3.0 - 3.22.11-0ubuntu3
1670390,2017-03-24 01:58:37 UTC,This bug was fixed in the package qtmir - 0.5.1+17.04.20170320.1-0ubuntu1
1670390,2017-03-08 08:50:15 UTC,@vanvugt
1670390,2017-03-08 15:31:15 UTC,"Based on my logs, GTK isn't receiving any resize events when the window appears. Is the expectation that Mir should be sending this? Or should GTK explicitly request the size on appearance?"
1670390,2017-03-08 09:08:13 UTC,(trying to remember)
1670390,2017-03-07 02:13:41 UTC,This sounds like bug 1655804. It may require the same kind of fix: The toolkit needs to register its Mir event callback in the spec prior to window creation to support Unity8 behaviour.
1670390,2017-03-07 14:47:27 UTC,"With gtk+ apps, when they get launched the ask for a resize. If in tablet/phone mode unity8 will deny/ignore it, but gtk thinks the resize was successful and renders as if its window had the size it requested (that's with the qtmir and unity8 branches attached to this bug)"
1670390,2017-03-22 03:10:44 UTC,This should be fixed under U8 with the gtk just released in zesty.
1670392,2018-01-12 21:05:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670394,2017-03-06 15:40:13 UTC,"If you add options snd-hda-intel model=inv-dmic  option to /etc/modprobe.d/alsa-base.conf, works."
1670400,2017-03-06 23:39:40 UTC,Hello and thank you for filing this bug report. Someone will need to investigate where that message is coming from and why it's being sent for pids that no longer exist.
1670405,2017-03-08 12:20:05 UTC,This issue was fixed in the openstack/fuel-qa 11.0.0.0rc2 release candidate.
1670405,2017-03-07 16:36:33 UTC,"Reviewed:  https://review.openstack.org/442575
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=75444050a6549ad411f252d90648268ac79a6ab6
Submitter: Jenkins
Branch:    stable/ocata"
1670405,2017-03-07 17:17:46 UTC,"Reviewed:  https://review.openstack.org/442576
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=5d0931c8d030b5e4b32ced8ecd5ae22aab87a478
Submitter: Jenkins
Branch:    master"
1670405,2017-03-07 15:58:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442576"
1670405,2017-03-07 15:57:50 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442575"
1670405,2017-03-07 15:57:34 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/442574"
1670405,2017-03-07 16:22:04 UTC,"Reviewed:  https://review.openstack.org/442574
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=a29b1f530e19bf201934d8ee295d0c6b1d843df1
Submitter: Jenkins
Branch:    stable/newton"
1670419,2018-02-07 11:58:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541691"
1670419,2018-02-14 15:42:49 UTC,This issue was fixed in the openstack/openstack-ansible-os_nova 17.0.0.0rc1 release candidate.
1670419,2018-02-14 15:40:21 UTC,This issue was fixed in the openstack/openstack-ansible 17.0.0.0rc1 release candidate.
1670419,2018-02-08 22:06:00 UTC,"Reviewed:  https://review.openstack.org/541691
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=604e8217a9c875889377ea03d1fae154d5f5aa5c
Submitter: Zuul
Branch:    master"
1670419,2018-02-08 21:07:33 UTC,"Reviewed:  https://review.openstack.org/541692
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-tests/commit/?id=e33000f1bcfaf0d23149cf5ffd7c88a812f0cd6a
Submitter: Zuul
Branch:    master"
1670419,2018-02-08 19:29:53 UTC,"Reviewed:  https://review.openstack.org/541685
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=023c4f27fc22845d25254cd2debaa566c070d0ea
Submitter: Zuul
Branch:    master"
1670419,2018-02-07 12:02:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541692"
1670419,2018-02-07 11:39:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541685"
1670419,2017-10-24 14:09:21 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/514685"
1670419,2017-10-26 02:41:19 UTC,"Reviewed:  https://review.openstack.org/514685
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=02586e698b005ed10f78dbd1cf35bdef2013fab2
Submitter: Zuul
Branch:    stable/newton"
1670419,2017-03-07 20:05:28 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442762"
1670419,2017-03-07 20:10:58 UTC,"Reviewed:  https://review.openstack.org/442035
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7439e9473617a871c032107ab85b1b623369975f
Submitter: Jenkins
Branch:    master"
1670419,2017-03-08 09:38:09 UTC,"Reviewed:  https://review.openstack.org/442762
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9b695d494444289d82a01547fd56ad8f9a50eab5
Submitter: Jenkins
Branch:    stable/ocata"
1670419,2017-11-01 00:20:08 UTC,This issue was fixed in the openstack/nova 14.0.9 release.
1670419,2017-04-14 09:23:18 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1670419,2017-10-24 14:00:46 UTC,"CERN ran into this when upgrading from newton to ocata and were confused because the placement_database option still existed in the newton code and made it sound like that's what they would want to use when deploying placement, but since the code was all reverted that wouldn't work."
1670419,2017-03-15 11:15:37 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1670419,2017-03-06 16:53:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442035"
1670421,2017-03-06 16:48:05 UTC,"Ironic edited a note on master because it was in the ""upgrades"" section instead of ""upgrade""."
1670421,2018-03-14 14:46:20 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1670427,2017-03-07 17:48:37 UTC,Pushed a collab branch that migrates the patron editor progress indicator.  It also displays the progress dialog during patron save.
1670428,2017-03-17 17:48:04 UTC,Now it is possible to do in 'High contrast display mode'
1670428,2017-03-11 13:04:06 UTC,"Eldar, I proposed the same to your #1671568 report. It's considered an important wish, but I think it requires serious modifications, so it only may be seen in the far future."
1670430,2017-03-08 17:35:02 UTC,retargeting to the mysql charm
1670431,2017-03-08 17:36:32 UTC,retargeting to the mysql charm
1670439,2017-03-06 17:48:02 UTC,"Apologies if I've missed this in the info already provided, but I'm not able to see what charm revision was deployed, and what config options were set on the Juju application.  Can you please also attach that?  Thank you."
1670439,2017-03-07 09:19:51 UTC,My apologies... I filed this and forgot to add the charm details:
1670439,2017-03-06 17:32:12 UTC,Attaching log files from all of the rabbitmq-server units from the CI run [1] and base-machine-2 (which contains var/log/ps-fauxww.txt and var/log/ps_mem.txt with processes listings and memory usage).
1670440,2017-12-22 11:33:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670440,2020-06-25 13:22:20 UTC,"Ubuntu 20.04, xmlcopyeditor 1.2.1.3
Most of my folders are synchronized with Nextcloud and I cannot open a HTML file.
A copy of the same file in ~/temp (not synchronized) opens perfectly."
1670441,2017-03-06 17:34:04 UTC,"Link to log file:
http://logs.openstack.org/57/436957/15/experimental/gate-tempest-dsvm-ironic-ipa-partition-pxe_ipmitool-tinyipa-python3-ubuntu-xenial-nv/781d77a/logs/devstacklog.txt.gz#_2017-03-06_12_45_43_818"
1670441,2017-03-06 17:44:48 UTC,Link to a job failing like that: http://logs.openstack.org/57/436957/15/experimental/gate-tempest-dsvm-ironic-ipa-partition-pxe_ipmitool-tinyipa-python3-ubuntu-xenial-nv/781d77a/logs/devstacklog.txt.gz#_2017-03-06_12_45_43_818
1670441,2017-03-08 04:40:56 UTC,This issue was fixed in the openstack/virtualbmc 1.1.0 release.
1670442,2017-03-06 18:48:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670442,2017-03-06 18:47:33 UTC,"The biggest problem with splash screens is on desktop: the first time an application is launched Unity8 has no idea of its window constraints (minimum, maximum and preferred sizes) so that it can choose an adequate size for the splash screen."
1670442,2017-03-06 19:35:03 UTC,"Sure, but it will resize to the right size once it knows it (even before the application draws)."
1670450,2017-03-06 20:30:40 UTC,"The attachment ""dlz_bind9_rndc_reload.patch (see univention bug report credits for it)"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1670450,2019-11-01 19:19:07 UTC,This bug is still in our queue.
1670450,2019-05-01 20:51:45 UTC,"We would really prefer if upstream could comment on that patch, maybe its author could send it to samba-technical@? That's where discussions happen most often. Although, it would also be good if we could determine if this problem still happens in the latest samba, currently the 4.10 series, which is available in Ubuntu Disco."
1670450,2018-10-31 18:07:02 UTC,"Is it also present in cosmic, which has samba 4.8.x?"
1670450,2017-07-24 10:35:10 UTC,Reported upstream (univention is 3rd party)
1670450,2017-07-18 09:43:27 UTC,"Yes please, that would be very helpful"
1670450,2018-04-18 14:38:24 UTC,"Hello,"
1670450,2017-07-17 18:00:00 UTC,Do you know if this patch or bug report was ever submitted upstream?
1670450,2017-07-17 08:52:19 UTC,Sorry to bump again but there have been 6 minor updates to samba package in 16.04 LTS and since this patch is not included we still have the same problem (fixed since 2015 on Univention bug tracker ...)
1670450,2017-03-20 09:37:20 UTC,"Any news on this bug ? Since it affects all versions and a tested patch exists I thought it would have been integrated sooner (at least -proposed)
It affects production (LTS) servers running Samba + Bind which is a quite rather common scenario on ""real"" environments for AD replacement. We also have identified indirect impact on integrated Ubuntu clients (with winbind and joined on AD domain) since it triggers sometimes DNS updates on server (along with dynamic DHCP updates to DNS Zone)
Restarting bind completely many times a day is not really a production-level solution to me ..."
1670450,2017-03-07 11:49:52 UTC,Hello and thanks for taking time to look at this bug.
1670450,2017-03-07 00:32:14 UTC,"Hello and thank you for filing this bug report and going through the effort of finding a solution. Before we can pursue a SRU (https://wiki.ubuntu.com/StableReleaseUpdates), we will first need to ensure it is fixed in 17.04. Can you help verify if this is or is not the case?"
1670450,2017-03-06 23:23:20 UTC,This patch does not seem to exist in the source code of the zesty version of samba.
1670450,2017-07-18 07:49:02 UTC,"Hm I looked at current samba git and bugtracker and did not find anything related to this bug. It seems noone ever submitted this upstream...
This is quite strange, I wonder how other people do. Maybe I missed something but this is reproducible and blocking for ""real"" production environements unless you never update your local DNS content ..."
1670451,2017-03-06 18:16:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442101"
1670451,2017-04-21 08:47:13 UTC,"Change abandoned by Alin Balutoiu (<email address hidden>) on branch: master
Review: https://review.openstack.org/442101
Reason: Abandoned since this patch merged https://review.openstack.org/#/c/453014/
 and idlutils is in ovsdbapp."
1670457,2020-08-17 16:03:22 UTC,There was a merge conflict when applying this to current master - can you please rebase?
1670457,2020-08-21 00:06:34 UTC,I like it!
1670457,2020-08-18 17:36:44 UTC,I've rebased to the latest master and pushed here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/khuckins/lp1670457-action-menu-grid-selection
1670457,2020-03-05 16:23:03 UTC,"Here's the updated branch
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/zbanks/lp1670457-action-menu-grid-selection"
1670457,2021-02-15 20:15:15 UTC,"Pushed to master, rel_3_5 and rel_3_6. Thanks Zavier, Kyle, and Terran!"
1670457,2017-08-23 18:39:38 UTC,I prefer for #3 since it keeps all the actions together and doesn't add clutter to the screen. It also seems to be more consistent with traditional user interface practices.
1670457,2017-05-26 21:00:38 UTC,"(Obviously, my previous comment is specifically about the vol/copy transfer destination selection...)"
1670457,2017-05-26 20:59:48 UTC,"I think there's enough room that we could make it a button, like the checkboxes (just needs the standalone attribute).  Or, as an alternative, we could make the library selection an interstitial modal that comes up whenever you try to transfer volumes and copies."
1670457,2017-05-26 20:02:13 UTC,"For what it's worth, the grid was designed with #4 in mind.  It supports <eg-grid-menu-item/> entries for global actions (the buttons along the top left) and <eg-grid-action/> entries for row-specific actions (in the Actions selector)."
1670457,2017-05-26 19:00:53 UTC,"I'm going to update the title and description of this bug because the problem extends beyond the original actions reported. When a user needs to perform an action that does not really require a selection, it can be frustrating to perform the action of selecting just to get the Actions menu to work."
1670457,2018-04-09 16:36:32 UTC,I like option 3 also.
1670457,2017-05-26 19:25:40 UTC,"I agree that 3 and 4 are the best choices, and I also have a preference for 3 so you always know to look for the Actions menu vs sometimes Actions and sometimes that other thing, etc."
1670462,2017-03-07 16:21:55 UTC,"Reviewed:  https://review.openstack.org/442447
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=bd1dc7fb770d2486e514fb96137ad26aff4dde3c
Submitter: Jenkins
Branch:    stable/ocata"
1670462,2017-03-08 12:21:04 UTC,This issue was fixed in the openstack/fuel-library 11.0.0.0rc2 release candidate.
1670462,2017-03-07 11:01:38 UTC,"Reviewed:  https://review.openstack.org/442109
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=b3787ca38af92ec7401294080cbbc8d7c0c49360
Submitter: Jenkins
Branch:    master"
1670462,2017-03-06 18:48:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442109"
1670462,2017-03-07 12:42:42 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442447"
1670463,2017-03-06 18:42:16 UTC,"StacktraceTop:
 XGetWindowProperty (dpy=0x558c63e2aec0, w=6291469, property=321, offset=offset@entry=0, length=length@entry=9223372036854775807, delete=delete@entry=0, req_type=6, actual_type=0x7ffd110d3058, actual_format=0x7ffd110d3054, nitems=0x7ffd110d3060, bytesafter=0x7ffd110d3068, prop=0x7ffd110d3070) at ../../src/GetProp.c:69
 gdk_check_wm_desktop_changed (window=window@entry=0x558c63e46660) at ././gdk/x11/gdkdisplay-x11.c:300
 gdk_x11_display_translate_event (translator=<optimized out>, display=0x558c63e3a060, event=0x558c64159c60, xevent=0x7ffd110d31b0) at ././gdk/x11/gdkdisplay-x11.c:881
 _gdk_x11_event_translator_translate (translator=0x558c63e3a060, display=0x558c63e3a060, xevent=xevent@entry=0x7ffd110d31b0) at ././gdk/x11/gdkeventtranslator.c:51
 gdk_event_source_translate_event (xevent=0x7ffd110d31b0, event_source=0x558c63e5f580) at ././gdk/x11/gdkeventsource.c:243"
1670468,2017-03-08 20:24:15 UTC,I believe this was fixed here https://github.com/PyCQA/pyflakes/pull/88
1670474,2017-03-23 23:15:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670476,2017-06-08 22:22:16 UTC,Fix committed to lp:ecryptfs as r890
1670476,2017-06-04 19:47:34 UTC,"The patch for upstream got improved significantly.
This FTBFS is fixed in rawhide."
1670476,2017-06-03 05:35:53 UTC,We have version 111 (what should be the same as trunk in current case).
1670476,2017-06-02 14:45:34 UTC,"What version of ecryptfs did you test(i.e. trunk,108...)?"
1670476,2017-06-02 13:01:58 UTC,Your patch fixes ecryptfs_key_mod_openssl.c but not ecryptfs_key_mod_pkcs11_helper.c
1670476,2017-05-06 07:07:13 UTC,Your patch does not work in current Fedora rawhide.
1670476,2017-04-01 06:05:39 UTC,"Unfortunately, the patch provided to upstream does not work with current sources in rawhide."
1670476,2017-03-13 20:43:21 UTC,PR made https://code.launchpad.net/~jelle-vdwaa/ecryptfs/ecryptfs/+merge/319746
1670476,2017-04-01 05:59:21 UTC,"Created attachment 1268032
patch for openssl 1.1.x"
1670476,2017-03-13 20:27:46 UTC,The following patch fixes the build with openssl 1.1.X
1670476,2017-03-06 19:59:31 UTC,Reported to upstream.
1670476,2017-03-03 17:47:13 UTC,Thanks! I'll update the package.
1670476,2017-03-03 12:38:35 UTC,"> I'm interested to become a co-maintainer and I'm the maintainer of
> ecryptfs-simple and zulucrypt. Can you give me commit access?
"
1670476,2017-03-03 06:39:42 UTC,"(In reply to Michal Hlavinka from comment #1)
…

> tldr: I'm going to leave it for upstream or anyone who wants to work on this
> patch.
"
1670476,2017-03-03 06:12:48 UTC,*** Bug 1428554 has been marked as a duplicate of this bug. ***
1670476,2017-02-28 10:26:21 UTC,"This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'."
1670476,2017-02-21 15:20:27 UTC,*** Bug 1423510 has been marked as a duplicate of this bug. ***
1670476,2016-10-19 15:19:59 UTC,"Migration guide is non-existent, api changes document covers only a few things. Changes from other packages do not cover much of openssl usage in ecryptfs-utils, so we can't take inspiration from there."
1670476,2016-10-12 11:39:06 UTC,"Description of problem:
Package ecryptfs-utils fails to build from source in Fedora Rawhide."
1670476,2017-03-13 20:28:18 UTC,"I'd like to make a PR for it, but I'm not sure how I am supposed to do that."
1670492,2018-01-04 17:36:53 UTC,I still cant use middle button scrolling I even have installed the DKMS package and still it is not working.
1670492,2017-11-10 08:06:52 UTC,I just found this in the apt-get upgrade output:
1670492,2017-08-05 09:58:07 UTC,Thanks @anthonywong! I can confirm that after installing oem-touchpad-psmouse-1615937-dkms_1.0sutton1_all.deb package the middle button is detected in my E470 and Trackpad scrolling works now like any standard mouse wheel scroll.
1670492,2017-08-04 09:52:26 UTC,"If you have Thinkpad E470, please try this DKMS package, E570 may need another solution, you are welcome to try but it may not work. If it works, we will try to upstream it."
1670492,2017-07-01 13:32:55 UTC,"The same on 17.04 and ThinkPad E570. After this ""sudo modprobe -r psmouse && sudo modprobe psmouse proto=imps"" the touchpas works but with libinput the middle button is dead."
1670492,2017-04-13 17:25:32 UTC,Some more debug info:
1670492,2017-04-14 12:43:13 UTC,"Can confirm that reloading psmouse module enables middle button, but for me after reloading psmouse module xinput only shows ""PS/2 Synaptics TouchPad"" and no ""TPPS/2 IBM TrackPoint"". Passing ""proto=imps"" as an option to psmouse in /etc/modules makes no change, after rebooting no middle button is detected."
1670492,2017-04-13 17:47:41 UTC,dmesg also tells us that psmouse failed to retrieve extended button data:
1670492,2017-04-11 21:20:57 UTC,Same for proto=exps and proto=bare.
1670492,2017-04-11 21:16:51 UTC,I found that
1670492,2017-04-08 17:10:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670492,2017-03-06 22:16:02 UTC,Tried with xserver-xorg-input-libinput-hwe-16.04 0.19.0-1ubuntu0.1. No middle button either.
1670492,2017-04-15 10:47:41 UTC,"As described here [1] installing xserver-xorg-input-libinput-hwe-16.04 and reloading psmouse with proto=imps enables the middle button. Also scrolling with middle button + trackpoint works, but two-finger scrolling using the touchpad does not work. It would be nice to be able to use touchpad and trackpoint."
1670494,2017-10-25 15:00:45 UTC,I understand this bug will be fixed when Marc rebased Ubuntu wpa package on top of the Debian's.
1670494,2018-06-20 15:12:24 UTC,"This is still broken in Artful, but is fixed in Bionic."
1670501,2019-09-26 12:29:47 UTC,"Thanks for the report and I apologize for late reply... The problem was reported by others as well and fixed long time ago, we just forgot to update this one. Thank you!"
1670506,2017-03-20 00:23:17 UTC,torbrowser-launcher (0.2.6-3.1) solved for me
1670506,2017-03-08 05:22:55 UTC,This bug was fixed in the package torbrowser-launcher - 0.2.6-3.1
1670506,2017-03-08 09:33:08 UTC,"Thanks.  I hope that fix gets backported to 16.04 LTS.  Until then, I have documented the work-around that worked for me in the Ubuntu Answers mentioned above:
    https://answers.launchpad.net/ubuntu/+question/526440"
1670506,2017-03-20 00:15:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670507,2020-04-24 04:57:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670507,2020-04-26 23:03:09 UTC,"|   PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
| 59333 hloeung   20   0 1187352 891992   1500 S   0.3  11.1   3:40.03 hud-service
"
1670509,2017-03-09 00:36:34 UTC,"The attachment ""0001-SGABIOS-fix-wrong-video-attrs-for-int-10h-ah-13h.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1670509,2017-03-08 23:43:09 UTC,"I don't think my e-mailed patch got through...  I'm going to keep trying, but in case anyone needs the patch in the interim..."
1670509,2017-12-13 15:53:12 UTC,I believe QEMU has handed ownership of this off to coreboot.  Which makes sense.
1670509,2017-12-12 20:10:09 UTC,"Fixed in qemu, yes. But not Ubuntu. Ubuntu strips prebuilt files from qemu and builds them from source. For sgabios, using the abandoned source from Google code."
1670509,2017-03-07 16:54:21 UTC,"I think I have submitted the fix to the qemu development list, but have no way to be sure it made it past Stratus' corporate firewall.  If it didn't make it (or if that was the wrong place to send it), please let me know."
1670509,2017-12-06 01:58:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670509,2017-12-06 01:57:57 UTC,"Any chance of getting this patch included?
I've deleted the incorrect patch and attached the correct one (taken from QEMU's sgabios repo)."
1670509,2017-12-06 08:04:55 UTC,Looks like the fix has been included in QEMU's sgabios repository here:
1670509,2017-04-10 16:09:54 UTC,That patch is wrong.  The correct patch has been submitted and checked on the QEMU mailing lists
1670511,2017-04-13 10:09:11 UTC,This issue was fixed in the openstack/murano 4.0.0.0b1 development milestone.
1670511,2017-03-09 21:12:00 UTC,"Reviewed:  https://review.openstack.org/443449
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=ee7772c2f91337f201ca18777390e2467909a05c
Submitter: Jenkins
Branch:    stable/ocata"
1670511,2017-03-09 22:43:29 UTC,"Reviewed:  https://review.openstack.org/442196
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=78ffcfbab4bf09cce9f0d0a46bf8da39beaea3d9
Submitter: Jenkins
Branch:    master"
1670511,2017-03-07 10:31:25 UTC,"Reviewed:  https://review.openstack.org/442198
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=46df6dda54f4ad62b0a71951a6091620ac6d004f
Submitter: Jenkins
Branch:    stable/newton"
1670511,2017-03-06 23:06:30 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/442198"
1670511,2017-03-06 23:05:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442196"
1670511,2017-03-09 07:28:45 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/443449"
1670522,2017-03-07 00:05:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442209"
1670522,2017-03-07 15:12:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/442550"
1670522,2017-03-07 16:16:47 UTC,"Reviewed:  https://review.openstack.org/442209
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ac61abb7c74f1a8e3e9134bc045455fd9fdac0fa
Submitter: Jenkins
Branch:    master"
1670522,2017-03-08 12:30:19 UTC,"Reviewed:  https://review.openstack.org/442550
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=30e604f57faa8321679881bdf6113f9389e80271
Submitter: Jenkins
Branch:    stable/ocata"
1670522,2017-03-15 11:15:41 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1670522,2017-04-14 09:23:20 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1670522,2017-03-06 23:39:54 UTC,By the way we didn't catch this in xenproject CI because it's running an older libvirt (1.3.1):
1670525,2017-03-07 00:13:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442211"
1670525,2017-08-01 09:59:29 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/442211
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1670531,2017-06-29 18:17:37 UTC,Thanks for the update Bryan!
1670531,2017-03-22 23:14:46 UTC,"I sent a request to the RedHat team on OPNFV to see if this is possible. Currently TryStack is Liberty-based with no support for Congress, and no clear support for adding any OpenStack services."
1670532,2017-04-26 12:23:00 UTC,Please share exact steps to reproduce this.
1670536,2017-03-24 16:02:12 UTC,It seems that it has already been asked for https://www.airdcpp.net/forum/viewtopic.php?f=6&t=4477 and here https://www.airdcpp.net/forum/viewtopic.php?f=6&t=4581
1670536,2017-03-24 16:07:26 UTC,One thing i need to correct. It seems that qBittorrent need to be restarted after the IP address has been changed even if it is bind to the interface. I don't even know if it is possible to do or the authors of qBittorrent have made something wrong?
1670536,2017-04-03 17:59:56 UTC,"Today i got a new IP address from my ISP and i could see this message in every hub 'The requested address is not valid in its context.' I then open the connection settings in Airdc and i could read 'unknown and my old ip address'. So i selected the same network name 'bb2 and my new ip address' and from the menu windows i did a 'Reconnect disconnected' and i got connected again.
It worked without any restart of Airdc too."
1670537,2017-03-07 04:25:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1670537,2017-03-07 18:54:57 UTC,"Thanks for your help, Brian."
1670546,2017-03-07 02:02:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1670546,2020-03-07 12:23:24 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1670546,2020-03-07 12:26:34 UTC,"Oops, above comment should have included:"
1670549,2017-08-07 15:50:48 UTC,Hi Sai! Please provide the ramdisk logs from the failed nodes?
1670549,2017-03-15 12:21:31 UTC,"hello Sai, would you please add more debug code in plugins/standard.py:_validate_interfaces()"
1670549,2017-03-14 09:47:16 UTC,thanks for providing so much info!
1670549,2017-03-13 13:17:05 UTC,https://gist.github.com/smalleni/d44367e8440eb5e5e75320d236ca3eca
1670549,2017-03-08 20:01:05 UTC,https://gist.github.com/smalleni/d43304be84aa67cf3a17a1222ee0d74b
1670549,2017-03-08 02:57:14 UTC,"pls paste your inspector.conf file, thx!"
1670549,2017-03-08 02:18:44 UTC,"I'm working on baremetal introspection recently, i've found some problems during simultaneous introspection. I'll investigate this issue as well."
1670549,2017-03-13 22:42:33 UTC,"Now trying to introspect a 120 nodes with bulk introspection, see this frequently"
1670549,2017-03-09 11:58:21 UTC,"i've gone through your config, within add_ports = pxe."
1670551,2017-03-07 02:06:25 UTC,should I do apport-collect here too?
1670565,2017-04-12 00:38:16 UTC,One side effect of this is that after the object-updater stopped counting 404 as success [1] - there's a higher risk an object DELETE to a previously deleted container will result in an unprocessable async_pending file.
1670581,2017-03-07 22:01:08 UTC,"I have created this activity: path has a reversal point before a signal, which stays at red.
Train starts, passes the signal and goes into TCSEmergency Braking. I pass to manual and reverse until I have again the red signal in front of me. At this point I pass to auto mode and stop the train. The train correctly catches the reversal point. No crash.
Also if I first stop the train and pass to auto mode I get no crash and the train catches the reversal point.
Is there some difference with your activity and your operation? Is the reversal point after the signal? Is there also a waiting point?"
1670581,2017-03-08 08:34:43 UTC,more than welcome for your support
1670581,2017-03-08 08:01:09 UTC,"I'm not able to replicate the issue either.
However I'll leave it open, because it's still an unresolved bug, even if not systematic.
Thanks for support."
1670581,2017-03-08 07:21:22 UTC,"The reverse point is before the signal.
When I go very slow, the reverse point disappears before the red signal.
I have tried to replicate the issue, but cannot."
1670581,2017-03-07 21:52:06 UTC,auto mode
1670581,2017-03-07 19:36:00 UTC,I don't know how to tell them apart.
1670581,2017-03-07 21:45:25 UTC,"So there wasn't a waiting point, but a reversal point. I'll try to reproduce the issue."
1670581,2017-03-07 17:52:36 UTC,"Hm, OR believes you passed also a reversal point. Is it so? Were you on manual or on auto mode when you braked to the final stop?"
1670581,2017-03-07 19:35:12 UTC,"My bad wording,"
1670581,2017-03-07 17:53:27 UTC,Was it an absolute or a standard waiting point?
1670587,2017-03-07 12:38:28 UTC,"Thanks for the report, but we've decamped to github (https://github.com/Brewtarget/brewtarget/issues). I will reopen the ticket there tonight and look into this."
1670587,2017-03-07 22:55:04 UTC,"Thanks, I've created a report on Github."
1670602,2017-03-07 09:02:27 UTC,I think you are hitting https://review.openstack.org/#/c/431370/.
1670602,2017-03-07 09:03:26 UTC,https://bugs.launchpad.net/zun/+bug/1663158
1670602,2017-03-07 09:21:53 UTC,So it's a duplicate bug. It's great that you have fixed it.
1670602,2017-03-25 16:48:51 UTC,It looks this bug has been fixed by: https://review.openstack.org/#/c/448967/
1670608,2017-04-07 18:17:53 UTC,We are re-implementing the version check API so this will be improved in forthcoming releases for all the tools.
1670608,2018-01-24 22:34:25 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1416
1670610,2017-05-03 08:30:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670610,2017-05-03 09:11:38 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1670619,2017-03-07 10:08:15 UTC,"Bug seems to be fixed in newer version of git, see chat
http://colabti.org/irclogger/irclogger_log/git?date=2017-03-07"
1670621,2017-03-14 13:16:29 UTC,"Thanks for your help, Michael!
Yes, I can confirm that for now saving of networks data requires valid cluster setting configuration. In other words, enabling a plugin requires setting up its settings to proceed further."
1670621,2017-03-14 13:46:22 UTC,"Hi Julia,"
1670621,2017-03-09 08:26:48 UTC,"Hi Michael,"
1670621,2017-03-13 14:08:17 UTC,"Hey Guys,"
1670624,2017-03-07 10:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1670624,2017-03-07 12:24:20 UTC,"@brad-figg The kernel does not complete boot. I can't boot into the system, can you tell me how can I run apport-collect?"
1670624,2017-03-07 17:58:39 UTC,"Can you see if the 4.11-rc1 kernel will boot?  It is available from:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1/"
1670624,2017-03-07 21:43:21 UTC,"When I was installing the kernel it complained about possibly missing firmware files for amdgpu.
Then it failed first but I blacklisted amdgpu module and it booted."
1670624,2017-07-26 15:23:06 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1670624,2020-01-09 07:28:27 UTC,"4.8 EOL,
please feel free to open a new bug if you're still encounter this issue with newer releases."
1670625,2017-03-09 19:00:44 UTC,"Yes, with the l2pop operations currently inside of the device retrieval, this can become slow. I would like to revisit this after we have switched to push notifications for the l2 agent because it will change these interactions quite a bit."
1670628,2018-03-21 23:18:27 UTC,This issue was fixed in the openstack/os-vif 1.10.0 release.
1670628,2018-12-10 04:49:20 UTC,This issue was fixed in the openstack/os-vif 1.7.1 release.
1670628,2018-04-03 09:10:55 UTC,"Reviewed:  https://review.openstack.org/550080
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=89b0bea3f32260fc1032729e7a75c3250aed8494
Submitter: Zuul
Branch:    stable/pike"
1670628,2018-03-21 15:22:53 UTC,"Reviewed:  https://review.openstack.org/550079
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=3be52b9e650db643827b8b97b28799407f30926f
Submitter: Zuul
Branch:    stable/queens"
1670628,2018-03-26 18:36:39 UTC,This issue was fixed in the openstack/os-vif 1.9.1 release.
1670628,2018-03-05 15:16:36 UTC,"As noted in the review [0], the bug that this was working around was fixed in OVS 2.6.0 [1], meaning that commit 33cc64fb817 mentioned above is not only causing issues with some patches but it should also no longer be necessary. IMO, we should likely revert it in it's entirety, which is what [0] is pretty much doing."
1670628,2018-03-05 14:12:07 UTC,"Not sure if this is the same issue but you can reproduce this by simply restarting nova-compute. With a DevStack-based deployment, run:"
1670628,2017-06-27 15:56:46 UTC,"Automatically discovered version mitaka in description. If this is incorrect, please update the description to include 'nova version: ...'"
1670628,2018-02-21 08:40:47 UTC,"This issue is valid for mitaka and newton which are both using OVS dpdkvhostuser port, deleting the port is going to make instance losing connectivity."
1670628,2017-07-28 12:28:31 UTC,"What real world scenario would you expect to expose a situation where the neutron environment is turned off and nova-compute is restarted? This seems pretty synthetic, and the fact that it recovers ones the neutron agent restarts seems like most of the environment is working as expected."
1670628,2017-06-27 19:30:54 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1670628,2018-03-15 18:43:00 UTC,The os-vif change https://review.openstack.org/#/c/546588 merged on 2018-03-06.
1670629,2017-03-08 17:06:30 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1670629,2017-03-08 18:41:58 UTC,Thanks for the quick reply and attention.
1670629,2017-03-08 19:14:06 UTC,"On Wed, Mar 08, 2017 at 06:41:58PM -0000, Pas wrote:

> Feel free to close this, I mainly reported this so maybe others will
> find the workaround useful.
"
1670629,2017-03-10 13:27:16 UTC,"Yeah, the fix for the policy-rc.d issue should fix this as well."
1670629,2017-03-10 13:51:07 UTC,"I tried it about 2-3 times, before confirming that it won't go away by itself."
1670629,2017-04-28 08:39:13 UTC,I've seen some of these kind of issues as well.
1670629,2017-08-24 19:14:25 UTC,"At first a was trying update my  password becouse I have problem in authenticate phpmyadmin, and after with mysql workbench.
as I am learnig use linux ubuntu, maybe this related problem was my fault."
1670642,2017-03-21 06:34:41 UTC,"Reviewed:  https://review.openstack.org/447626
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=914aa032f2031625512e1bcebf312fe9fff4d3fa
Submitter: Jenkins
Branch:    stable/ocata"
1670642,2017-03-21 14:59:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/448142"
1670642,2017-03-22 10:15:10 UTC,This issue was fixed in the openstack/nova 15.0.2 release.
1670642,2017-04-14 09:23:16 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1670642,2017-05-30 19:07:14 UTC,"Reviewed:  https://review.openstack.org/448142
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e289fe9eb66a4984c7bb9dc72f5aff83003fe390
Submitter: Jenkins
Branch:    master"
1670642,2017-03-20 13:33:45 UTC,"Reviewed:  https://review.openstack.org/441989
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d629d4e42c04756444a79e9ac15f3f2192c47b52
Submitter: Jenkins
Branch:    master"
1670642,2017-03-20 17:59:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/447626"
1670643,2017-04-06 09:31:04 UTC,sysdig 0.13.0-2ubuntu1 from -proposed on aarch64:
1670643,2017-04-06 10:09:39 UTC,"Seems like CONFIG_ARM64 is not defined for the syscall table start, so this is one reason for a build failure:"
1670643,2017-03-07 20:30:14 UTC,"Thanks Tim, I'll see if we can/should have them in Debian soon toon."
1670643,2017-03-07 11:21:18 UTC,http://kernel.ubuntu.com/testing/4.10.0-11.13-generic/hainzel__4.10.0-11.13__2017-03-06_16-26-00/ubuntu_sysdig_smoke_test/results/ubuntu_sysdig_smoke_test.sysdig-smoke-test/debug/ubuntu_sysdig_smoke_test.sysdig-smoke-test.DEBUG.html
1670643,2017-03-07 16:36:43 UTC,That's fixed in Debian since sysdig/0.13.0-2.
1670643,2017-03-07 13:48:17 UTC,And for aarch64 with 4.10.0-11:
1670643,2017-03-07 13:38:55 UTC,s390 build with 4.10.0-11:
1670643,2017-03-07 13:20:53 UTC,Aarch64: start of log:
1670643,2017-03-07 17:20:41 UTC,Evgeni - I just synced 0.13.0-2 from Debian and added some v4.10 compatibility patches from upstream dev tip
1670644,2017-03-13 17:53:30 UTC,"Wow, this is also a cool feature related to this feature request: https://bugs.launchpad.net/inkscape/+bug/1664632"
1670644,2017-09-09 02:02:24 UTC,"Is the effect we want to make for example powerstroke with linked fills, the original idea of this feature.
Also @Eman Modnar (eman-mod) I just commit this and more improvements to fill between many LPE to trunk."
1670644,2017-10-13 17:37:12 UTC,"Hi, it also happens on Windows 10 (64 bits). I've tested on last stable version and also on +devel version. Both of them apply a wrong LPE."
1670644,2017-10-14 01:11:08 UTC,"Hi Gonzalo.
Is the spected beabiour, the original idea of this menu is allow fills linked to on power stroke shapes."
1670645,2017-03-07 13:12:43 UTC,Let me guess: you are using an ancient MySQL version.
1670651,2017-06-27 08:50:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670652,2017-05-08 04:17:54 UTC,[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]
1670652,2017-03-09 02:21:50 UTC,Doesn't 'qemu -usbdevice mouse' constrain the pointer correctly already? I assume we're talking about the behaviour of 'qemu -usbdevice tablet' here...
1670652,2017-03-09 02:33:38 UTC,I can't see an option for it in virt-manager so can't fully confirm (because I have no time to create a VM to verify for you).
1670652,2017-03-08 10:43:42 UTC,"Well, for example when you run fullscreen, your pointer *is* locked to the edges. Unfortunately I can't test this works in those cases, as the VM screen resolution doesn't match the aspect ratio of the real screen 4:3 instead of 16:10 (due to a different bug), so there are black bars down the sides."
1670652,2017-05-08 04:17:52 UTC,[Expired for virt-manager (Ubuntu) because there has been no activity for 60 days.]
1670652,2017-03-08 02:22:26 UTC,Comments #1 and #4 answer it all. Although comment #1 is half wrong as #4 points out.
1670652,2017-03-08 08:45:58 UTC,"Don't get me wrong, I know not containing the pointer is preferable in some cases, what I'm saying is lacking, is an *option* to contain it."
1670652,2017-03-07 14:09:40 UTC,"isn't this really a specific instance of this bug 1670670 ?
if so, please dup this one"
1670652,2017-03-07 12:22:05 UTC,"I'd say this isn't a unity8 bug... More like a qemu one, because it doesn't let you confine the cursor to the VM."
1670652,2017-03-07 16:58:59 UTC,"Well, for one it is a bug for others a feature :-)"
1670652,2017-03-07 15:08:51 UTC,"Not really, because even if it gets in sync, you won't get to push against the edge unless the VM locks you in. You'll just go past the edge and out of the VM."
1670658,2017-03-29 18:12:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670666,2021-02-03 13:31:07 UTC,"Hello, is anything happening with this bug? I have the same problem - on networks without router - DHCP does not work."
1670666,2020-09-25 15:40:51 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/708011
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1670666,2020-09-25 15:39:52 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1670666,2020-02-16 10:48:50 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/708011"
1670666,2020-01-21 10:45:04 UTC,The OVN driver now lives in the neutron repository. Moving this bug to their tracker.
1670666,2019-10-29 02:20:11 UTC,"i think When a subnet enable_dhcp is true and metadata-agent service is disabled,  we should create a reserved dhcp port for DHCP service"
1670666,2018-02-01 10:52:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/539901"
1670666,2018-02-02 23:17:37 UTC,"Reviewed:  https://review.openstack.org/539901
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=e7fc4edc9412c1ef489f578feeb3dd39fedd4fd7
Submitter: Zuul
Branch:    stable/pike"
1670666,2017-04-27 12:23:34 UTC,"I applied that patch to master, so we can now make networking-ovn look for an OVN northbound schema version >= 5.5.1 to check for this."
1670666,2017-04-19 16:42:05 UTC,https://patchwork.ozlabs.org/patch/752346/
1670666,2017-04-19 12:42:56 UTC,The ovs-appctl approach may not work as neutron-server will not always be running on the same server as the OVN databases.
1670666,2017-04-18 13:01:33 UTC,One approach I could think of is networking-ovn can get the version of ovsdb-server (hosting NB DB) by using it's control socket and handle the code accordingly.
1670666,2017-04-06 06:18:51 UTC,"This feature is nearly completed, but there is an issue need to be resolved.
""Modify the DHCPv4 router option to optional""[1] was merged only to master, Networking-ovn should support both master and release, I haven't found the approach to verify the precise version of OVN DB. A single manner in networking-ovn will cause many logs using OVS/OVN 2.7 as backend.
Later other features will meet the same issue, e.g. supporting gratuitous ARP."
1670666,2017-04-03 15:50:51 UTC,I think creating a port to reserve the IP is fine.  We'll need to create a port for the metadata API proxy as well.  I think we can just use the same port for both purposes.  I'll be posting a proposed metadata API design doc shortly.
1670666,2017-03-10 07:25:14 UTC,"A DHCP port will be created to obtain the server IP without the gateway IP, maybe we can think of a better idea."
1670666,2017-03-10 06:38:17 UTC,"When gateway ip is not set, what should be the value of DHCP option - ""server_id"" ?"
1670666,2018-01-31 18:01:41 UTC,"Reviewed:  https://review.openstack.org/534741
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=48c3fbb8b830b4fb33fa63b1e7628c8d364509c2
Submitter: Zuul
Branch:    master"
1670679,2017-03-07 14:05:12 UTC,"@Pete, can you please give exact steps to repro? It might be different depending on whether you hit the greeter or the lock screen (which today look identical)."
1670679,2017-03-07 14:35:23 UTC,"Definitely the lock screen, not greeter. For me, it's leaving the virt-manager window up, and doing nothing until the lock timeout happens. Then once you're sure it's happened move the pointer over the virt-manager window. Only at this point does the screen redraw and show the lock screen."
1670685,2017-03-07 13:59:49 UTC,"StacktraceTop:
 webkit_uri_scheme_request_finish (request=0x56235afff4a0, inputStream=inputStream@entry=0x56235b171ad0, streamLength=streamLength@entry=56095, mimeType=mimeType@entry=0x56235b01ac90 ""application/xhtml+xml"") at ./Source/WebKit2/UIProcess/API/gtk/WebKitURISchemeRequest.cpp:225
 document_callback (document=0x56235b203100, signal=<optimized out>, data=0x56235afff120, error=<optimized out>) at libyelp/yelp-view.c:786
 request_idle_contents (request=0x56235b23ec00) at libyelp/yelp-document.c:1417
 g_main_context_dispatch () from /tmp/apport_sandbox_EymS30/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iterate.isra () from /tmp/apport_sandbox_EymS30/lib/x86_64-linux-gnu/libglib-2.0.so.0"
1670693,2018-05-15 09:19:13 UTC,I think other than the test_routers file there are other files too where we can use the cleanup.
1670693,2019-07-23 03:02:45 UTC,https://review.openstack.org/#/c/572015/ fixed and the bug should be placed into a final state.
1670693,2018-08-16 14:16:24 UTC,This issue was fixed in the openstack/tempest 19.0.0 release.
1670693,2018-07-02 08:17:06 UTC,https://review.openstack.org/#/c/572015/
1670693,2017-05-26 21:26:14 UTC,"Change abandoned by Duc (<email address hidden>) on branch: master
Review: https://review.openstack.org/468547
Reason: Incorrect Topic.  Will resubmit with correct topic."
1670693,2017-05-26 21:26:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468551"
1670693,2017-05-26 21:17:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468547"
1670693,2017-03-22 14:03:07 UTC,Indeed. The correct fix is to remove all the class fixture with per-test-resource and use self.addCleanup(...)
1670693,2017-08-02 23:18:53 UTC,"Change abandoned by Duc Truong (<email address hidden>) on branch: master
Review: https://review.openstack.org/468551"
1670704,2017-03-07 14:35:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670706,2017-09-09 17:58:47 UTC,I will try 2 things:
1670706,2017-09-10 08:34:15 UTC,You mean both ax88179_178a and hid-rmi work?
1670706,2017-09-05 07:31:21 UTC,"I did get a lot of corrected PCIe errors previously which is why I set pcie_aspm=off (otherwise it flooded my kernel log instantly) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714
https://launchpadlibrarian.net/318000853/dmesg_pcie_aspm_rc8.log"
1670706,2017-09-10 20:41:27 UTC,Gathering more evidence in support of a faulty motherboard theory.
1670706,2018-08-19 19:09:53 UTC,I have the same issue with Linux Mint 19 (Ubuntu 18.04 based) using kernel 4.15 but for QCA9377 chipset.
1670706,2017-09-10 10:51:38 UTC,"Sorry, I should have mentioned that before: in the original test I also had a device plugged in via usb type-c (thunderbolt 3) - that device had an ethernet interface which you can see in the logs. It's another problem that I need to debug because type-c hot-plug of that device worked once but successive attempts did not (no devices were attached) - will try that on 4.13 but not in the scope of this thread."
1670706,2017-09-05 05:27:49 UTC,I don't have a special wireless off/on button on my keyboard but I'm assuming rfkill <block|unblock> <id> will do (soft kill switch).
1670706,2017-09-09 12:11:16 UTC,This is the most heavily loaded configuration I use with this device and I don't have issues with either an NVMe SSD or GPU. No hardware-related issues with any USB devices (data goes through PCIe in the end).
1670706,2017-09-02 13:06:32 UTC,Got a repro on 4.13.0-041300rc7 with the debug mask above set.
1670706,2017-03-07 15:00:14 UTC,This change was made by a bot.
1670706,2017-09-04 06:37:05 UTC,"Seems like the PCI device no longer responds, so there are lots of -ETIMEDOUT."
1670706,2017-03-07 17:52:48 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1670706,2017-03-07 18:26:33 UTC,Cannot reliably reproduce it even on the same kernel - will keep trying.
1670706,2017-03-15 20:27:46 UTC,Reproduced on 4.10.0-11-generic after a long period of laptop inactivity (see traces at the bottom).
1670706,2017-09-05 06:58:46 UTC,Seems like it's a PCI bus issue? Tons of errors happened before the ath10k_pci errors:
1670706,2017-07-16 13:07:58 UTC,Still getting the same on the released 4.12 kernel.
1670706,2017-05-15 04:17:31 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1670706,2017-07-17 07:15:02 UTC,"Add ""ath10k_core.debug_mask=0x4041"" to kernel parameter and attach dmesg when the issue happens."
1670706,2017-07-16 13:30:07 UTC,This change was made by a bot.
1670715,2017-03-31 13:32:53 UTC,"I can confirm this issue, when restoring 9 tabs at startup."
1670715,2017-03-07 14:56:04 UTC,"This might be an issue in ubuntu-ui-extras, tentatively adding a task for the project."
1670721,2017-03-07 15:28:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670721,2017-03-07 20:45:21 UTC,"Some research...  So normally, gnome-terminal seems to start a systemd unit for a server process.  Which UAL doesn't associate with the launching process, so doesn't allow a connection to Mir."
1670721,2017-03-16 14:14:44 UTC,"With the switch to XMir by default, this is fixed."
1670721,2017-03-17 02:51:34 UTC,"That's an accidental workaround (bug 1672931), which will go away in time. Not a permanent fix."
1670722,2017-03-28 12:11:58 UTC,Work around :
1670722,2017-04-20 19:29:55 UTC,Proposed solution:
1670722,2017-03-07 18:36:14 UTC,"Reviewed:  https://review.openstack.org/442642
Committed: https://git.openstack.org/cgit/openstack/python-redfish/commit/?id=ea995f722a5b8e1804afdd9e8314f5615a04087f
Submitter: Jenkins
Branch:    master"
1670722,2017-03-07 16:16:58 UTC,"Thanks for reporting the bug.
We did a mistake pushing the sources to pypi."
1670722,2017-03-28 12:11:15 UTC,"Re opening this bug as it appears that this is not fixed unlike what we thought.
Reason is pip not running the setup.py. Pip is building a wheel package if the cache is available."
1670724,2017-03-07 15:49:59 UTC,This means the snap does not include the mir QPA and/or doesn't connect to mir-libs?
1670724,2017-03-07 15:51:09 UTC,"Sorry, wrong bug I commented on, however, we'll need the output from unity8.log to try and see why the app was rejected."
1670724,2017-03-07 15:53:10 UTC,"Are you launching it from the terminal? That's not supported, you need to run it from the app drawer or via ubuntu-app-launch."
1670724,2017-03-07 16:11:51 UTC,"It does not work from the app drawer either, that's the 1rst thing I tried. I'll attach more logs."
1670724,2017-03-09 10:04:09 UTC,"It ""starts"" from the app drawer here, but you get an empty translucent window"
1670724,2017-05-09 04:17:24 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1670729,2017-06-11 04:17:30 UTC,[Expired for juju because there has been no activity for 60 days.]
1670729,2017-04-11 16:29:28 UTC,@jameinel My bundle file has the exact series I want it to deploy on.  It's the charms that don't list support for that specific series that I want to override.
1670729,2017-03-14 13:00:58 UTC,"@Anastasia
It's a full openstack deployment, I'm just using https://code.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk
Specifically I'm telling bundles/2.x/gen-bundle.sh to generate one for zesty."
1670729,2017-04-10 15:06:33 UTC,"Is this for some of the entries in the bundle, all of them? What granularity of overrides are you looking for?"
1670729,2017-03-14 08:17:59 UTC,"In general, I think we'd create more problems by allowing bundles to specify series that charms explicitly do not support."
1670731,2018-07-23 00:33:57 UTC,Test some event orderings to characterise bug and see if we still have it:
1670731,2017-08-01 15:04:59 UTC,Seems to cause agent hangs should VPP crash.
1670731,2017-03-07 17:18:56 UTC,"Looping on connect/disconnect for a stress test has been raised to VPP team
Ungracefull disconnect has also been raised to VPP team"
1670731,2017-03-08 00:17:15 UTC,"Note frequency - seen once so far, to my knowledge."
1670749,2017-03-09 16:35:11 UTC,"Oh, this might be my problem with switching ubuntu-image to classic confinement.  It's a Python 3 application, but suffers what looks like to be exactly this problem (my post to the snapcraft list is probably being held for moderator approval)."
1670749,2017-03-09 18:20:37 UTC,"After discussing with snappy team, this is working as designed."
1670749,2017-03-09 20:22:14 UTC,"Thanks for the information, however I'm reopening this because with 2.27.1 on Zesty, while snapping up ubuntu-image in classic confinement, I still had to add PYTHONPATH, and I had to make sure that $SNAP/bin comes before $PATH in the $PATH environment.  u-i is a Python 3 application, so that's another difference from what you report."
1670749,2017-04-19 18:26:32 UTC,I an facing same issue with `strict` confinement. Ubuntu 16.04 snapcraft 2.28. My current snapcraft.yaml file:
1670749,2019-07-31 16:01:12 UTC,"This is also affecting me still in snapcraft 3.7:
When snap is run in classic mode root is the same as the host system so paths need to be specified in the environment. This will also affect dynamic link library search (I've seen this happen in a different project), at compile time the path for the library is set relative to the prime directory and, as root is not the prime directory in classic mode, search fails."
1670751,2017-03-07 16:28:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670751,2017-03-07 16:32:50 UTC,"I'd actually like to see less environment provided by unity8-desktop-session itself in this case, and more by UAL."
1670751,2017-03-10 17:44:08 UTC,"a note based on recent conversation.
ltinkl confirmed that QT_QPA_PLATFORM for Qt5
so with the current state of things, it would be ideal for u-a-l not to remove this env var - and it won't effect Qt4 apps."
1670751,2017-03-10 17:57:22 UTC,"This bug is about something different, actually... UAL doesn't modify environment today (hence the bug)"
1670755,2017-03-07 19:09:59 UTC,"Bug confirmed, attached are some screenshots of the untranslated strings."
1670755,2017-03-07 20:50:56 UTC,"It seems the strings from the screenshots (among others) are coming from this file:
~/plank/docklets/Trash/TrashDockItem.vala
But I do not know how to modify a program in Vala to enable the internationalization."
1670768,2017-03-07 16:54:11 UTC,Workaround:
1670775,2017-03-09 21:59:38 UTC,"Anton, we hit another failure today:"
1670780,2021-01-10 18:00:27 UTC,"Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1273027, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find."
1670791,2017-03-09 08:36:54 UTC,Tested and confirmed!
1670792,2017-03-07 18:47:35 UTC,Nova Compute log.
1670792,2017-03-09 09:53:58 UTC,"Hi Paul,"
1670792,2017-03-10 17:26:48 UTC,"I have a multiple backed configuration, below is an excerpt of the enabled backend configuration in the ""default"" section of the cinder.conf file. The live migration operation is failing/hanging indefinitely for the Cinder based backends."
1670807,2020-03-07 19:08:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670808,2017-03-07 20:58:55 UTC,ok: found the steps to reproduce - first here are my python versions:
1670813,2017-04-30 14:16:58 UTC,This is another one where the default python is to blame
1670826,2018-01-25 08:59:49 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1789
1670828,2019-12-11 03:07:03 UTC,"Since I happen to know there's a new feature request for improvements to Connector tool, I willd decline to migrate this."
1670830,2017-03-07 21:14:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442792"
1670830,2017-03-09 12:02:49 UTC,"Reviewed:  https://review.openstack.org/442792
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=1a477ca8e5a22e0408aaef545e57b2366ab13272
Submitter: Jenkins
Branch:    master"
1670836,2017-08-03 09:55:12 UTC,"Hi, Corey, can you give an example of this scenario?
Can you please tell me steps to reproduce?"
1670836,2017-08-03 11:56:50 UTC,"Hi, I'm not working on Magnum anymore, so I can't give you exact commands, but there are two examples to work with in the original bug description.  Here's my rough guess at the commands from docs."
1670838,2020-10-27 14:16:32 UTC,"We just had our biannual no holds barred roadmap derby at the beginning of this month, and we're pretty solidly booked for this cycle, so I'd say that there isn't a good chance of adding it to the roadmap for 21.04."
1670838,2020-10-27 12:45:21 UTC,"This also affects Operations teams that don't have ssh access but need limited privileges to collect e.g. backups. When running a ""backup"" action, the action will tell the ""juju scp"" command needed to retrieved the backup file."
1670838,2017-04-17 12:12:24 UTC,"+1, another example is the Tempest charm:  An action executes an OpenStack functional test suite. The user then scps the results blob out of the unit."
1670860,2017-03-14 04:30:41 UTC,"Mixin support should in itself will not cause side effects/bugs, so long as the modeling constraints are maintained. Now that users are only constructed via model code, this is no longer a problem. However, we are missing the ability to use this support."
1670865,2019-09-26 10:29:47 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1670871,2017-03-08 17:40:51 UTC,"Just for clarity, by ""comment"" he means the comment line in the .desktop file"
1670874,2017-03-21 16:32:01 UTC,Please see our triage conversation:
1670879,2017-03-07 23:19:55 UTC,"AFAICS this is a duplicate of https://bugs.launchpad.net/cinder/+bug/1660870.
The 'fix' for which is to de-escalate the log level, or just log it once."
1670879,2017-03-08 00:06:03 UTC,Wafl counts can be gathered with no diag mode?
1670879,2017-03-08 00:50:19 UTC,"Yes, and as you mentioned, you do need the cluster-scoped administrator account for this."
1670882,2017-06-23 15:13:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670886,2019-09-19 11:52:56 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1670886,2017-11-04 16:54:13 UTC,Cool. Is the plan for maas to provide a way for admins to specify which RFC 1918 networks are in use at our organization and for which DNS forwarding should occur?
1670886,2017-06-27 19:14:40 UTC,"Yes, I have upgraded to maas version 2.2.0+bzr6054-0ubuntu1~16.04.1 and
yes, this is still needed: I had added the aforementioned directive to my
/etc/bind/named.conf.options --- if I comment that out, the problem
returns. This is with bind9 version 1:9.10.3.dfsg.P4-8ubuntu1.6"
1670886,2017-06-27 19:17:48 UTC,This seems the same as: https://bugs.launchpad.net/maas/+bug/1688644
1670886,2017-06-27 17:17:52 UTC,"Hi Nathaniel,"
1670886,2017-06-27 17:21:12 UTC,"Also, the version of bind would be good to have."
1670886,2017-06-29 17:07:36 UTC,"When this issue is addressed, let's keep in mind that ISC does not recommend this workaround[1]:"
1670889,2017-03-08 01:04:57 UTC,"removed package zlib1g:i386, Autoremoved all dependents. Reinstalled package zlib1g:i386."
1670889,2017-06-15 10:02:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670893,2017-03-13 14:47:23 UTC,"This will require refactoring of IPA API, hence it will need a spec."
1670901,2017-03-08 11:54:23 UTC,"Looks like the ""default"" hat in your /bin/su profile was not initialized."
1670901,2017-03-10 01:31:14 UTC,"Unfortunately the instance with the original log and profile has been terminated.
I think that I have reproduced the bug."
1670901,2017-03-10 21:22:13 UTC,"Hmm, that's half an answer ;-)"
1670905,2018-11-07 17:08:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670905,2017-10-18 09:17:59 UTC,"Was there a bug filed upstream and if so, can you please share the ticket number/link to ticket?
Couldn't really find a corresponding bug at https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=qemu-user-static."
1670905,2017-03-09 06:46:54 UTC,"Hi Alistair,
yes that matches 100% what I have found and is the reason I added a bug task for debootstrap.
Sorry if I didn't sum it up so well, but yeah - I agree that the root cause is the lack of an ability to pass such info to second stage (or alternatively that second stage knows how to handle better what it finds from first stage in such cases)."
1670905,2017-03-08 17:41:18 UTC,"Yes, I expected the chroot to end up with the mirror I asked for in the sources.list. This is the behaviour with a normal debbotstrap invocation."
1670905,2017-03-08 13:08:14 UTC,"I tried several combinations:
$ sudo qemu-debootstrap --no-check-gpg --arch=armhf jessie ./test-root-jessie-raspian http://mirrordirector.raspbian.org/raspbian
$ sudo qemu-debootstrap --no-check-gpg --arch=armhf jessie ./test-root-jessie
$ sudo qemu-debootstrap --no-check-gpg --arch=armhf jessie ./test-root-jessie-mirrorset http://httpredir.debian.org/debian/
$ sudo qemu-debootstrap --no-check-gpg --arch=armhf trusty ./test-root-trusty"
1670905,2017-03-09 06:48:16 UTC,"Thinking about it, it actually wouldn't make too much sense to fix that in the Ubuntu Delta of the two packages."
1670913,2018-01-12 04:20:52 UTC,This issue seems to also affect the stroke style modified by percentage:
1670913,2017-04-01 15:57:33 UTC,Attached example of correct glyph size with units=px and scale=1.
1670913,2017-03-18 20:42:58 UTC,"Also likely cause of Bug #1673924
""Outset (and inset) fails to offset by amount set in preferences"""
1670913,2017-03-18 00:19:41 UTC,"It appears that symbols created in documents with scale that doesn't directly correlate to 96dpi are at the root of these issues whether used in a browser, other programs, or even Inkscape itself. So, I don't think browsers should be divorced from this report."
1670913,2017-03-17 19:46:14 UTC,"I think the browser issue should be reported separately because it is not related to the behavior of symbols.
   With browsers the problem that will be encountered is the fact that Inkscape sometimes uses variables that are not part of the svg spec. For example the variable:
<svg viewBox=""0 0 397.95275 397.95278""> is part of the svg spec while the variable:
<sodipodi:namedview inkscape:document-units=""cm""> is not part of the svg spec.
Therefore any Inkscape file that uses both of these variables, set to non-default values, is more or less guaranteed to differ from a browser at some point. However, it is reasonable to expect that the symbols would still scale correctly independently of that since they are entirely internal to Inkscape."
1670913,2017-03-17 18:33:25 UTC,"Duplicated browser issue in IE v11, Safari 5.1.7, and Firefox v52."
1670913,2017-05-07 11:30:41 UTC,"Likely related to new report:
https://bugs.launchpad.net/inkscape/+bug/1688997
""Scale issues on cli export"""
1670913,2017-03-16 20:20:04 UTC,"While the new dxf_outlines.py resolves the output to plotter filetypes workflow, the issue of symbols, browsers and other programs remains."
1670913,2017-03-17 13:33:35 UTC,"I cannot comment on the browser issue because I don't have Chrome installed, but I can confirm the scaling issue with symbols. The file 100mmSq_CM_scale_1 is too small when used as a symbol."
1670913,2017-03-08 02:06:56 UTC,"svg file, symbol library"
1670913,2017-03-08 02:08:26 UTC,dxf file generated from 254mmSq-Scale_set_to_1perMM.svg
1670913,2017-04-01 15:55:56 UTC,Issue also seems to affect creation of fonts.
1670913,2017-03-08 04:03:51 UTC,"Hi Alvin, thank you for your comment."
1670913,2017-03-08 04:12:47 UTC,Typo correction:
1670913,2017-03-08 03:08:00 UTC,"There was recently a change made in the scaling of the dxf output. This will have an effect on the output when using units that are not px. The change was made in:
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15469
in response to Bug 166097
https://bugs.launchpad.net/inkscape/+bug/1660967
There is also some discussion of the base unit at:
https://bugs.launchpad.net/inkscape/+bug/1643383/comments/8"
1670913,2017-03-08 10:06:26 UTC,"as far as I can tell, this report is a duplicate of Bug 1660967"
1670915,2017-03-21 14:23:35 UTC,"Reviewed:  https://review.openstack.org/442859
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=cd39778824970a696c221f394e70bcee6a9d0001
Submitter: Jenkins
Branch:    master"
1670915,2017-03-08 04:48:02 UTC,The correct behaviour is definitely exposed.
1670915,2017-03-08 04:27:24 UTC,I think https://review.openstack.org/#/c/442859 is on the right track for the swift end
1670915,2017-03-08 07:27:21 UTC,I agree migration and interop concerns are the major issue here and quite frustrating.  It was certainly discussed when the issue was originally raised [1] - perhaps better foresight could have caused the maintainers at the time to push back harder?
1670917,2017-03-08 04:17:04 UTC,Context and timing lead me to believe this is related to lp bug #1670915
1670917,2017-03-08 04:59:03 UTC,"You likely have more insight into the inner workings of Swift, so please feel free to ignore if I'm off base here, but this was slightly different from lp bug #1670915:"
1670917,2017-03-08 17:31:37 UTC,Hmm… that is _very_ weird.
1670917,2017-03-08 06:43:28 UTC,Interesting...
1670918,2017-03-08 03:03:32 UTC,"There is a further side-effect: Installing snapd on trusty installs systemd, which tricks charmhelpers into thinking the systems's default init system is systemd, which causes it to (pointlessly) use ""systemctl"" to manipulate services instead of ""service"" (which works on all releases).  So the charm won't deploy on trusty as is."
1670918,2017-03-08 03:06:14 UTC,"""So the charm won't deploy on trusty as is.""  Michael Nelson reminds me that it deploys, but doesn't upgrade-charm successfully."
1670918,2017-03-08 05:57:33 UTC,Time to drop trusty support? Effort may be better spent moving forward to xenial+snap deploys.
1670918,2017-03-08 06:13:55 UTC,I've opened https://bugs.launchpad.net/charm-helpers/+bug/1670944 on charmhelpers vs snapd vs systemd.
1670918,2017-04-10 09:10:25 UTC,I think it would be the best to check whether deb/snap is installed and block hooks until config option is set to match current state.
1670935,2020-07-04 12:07:16 UTC,libpng12-0:i386 1.2.49-1+deb7u2
1670935,2018-05-03 20:25:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670937,2017-03-11 10:44:03 UTC,"Change abandoned by Madhuri Kumari (<email address hidden>) on branch: master
Review: https://review.openstack.org/442942
Reason: Fix has already been merged. https://review.openstack.org/#/c/441633/"
1670937,2017-03-08 05:15:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/442942"
1670945,2017-03-09 05:38:15 UTC,"Also broken: rendercheck -t composite -o add -f a8r8g8b8,a8"
1670946,2017-03-08 14:43:03 UTC,"@Nam, thank you very much for taking on this important feature."
1670946,2017-03-14 15:49:23 UTC,"@Nam, here are some instructions from @dane-fitcher. https://etherpad.openstack.org/p/tempest-plugin-testing"
1670946,2017-03-15 03:42:19 UTC,"@Dave, I saw your question on the path set. Thank you for your help"
1670946,2017-03-20 02:50:11 UTC,I already tested upgrade from Newton to Ocata. And there are not problems with all commands and tempest test:
1670959,2018-07-26 17:38:25 UTC,"This solution works, but it's not persistent. /etc/resolv.conf is a symlink to /run/resolvconf/resolv.conf, which is ephemeral. It'll be recreated as 127.0.0.1.
Any news on an actual fix for this, rather than just a workaround?
Thanks!"
1670959,2018-07-25 18:09:35 UTC,"I just started noticing this issue on my machine today. Ubuntu 18.04. I also had nameserver 127.0.0.1 in /etc/resolv.conf. Changed to 127.0.0.53, per diepes' comment and CPU calmed down for me as well."
1670959,2018-07-12 18:33:07 UTC,"This happened on my machine, and diepes's fix worked for me as well."
1670959,2018-07-10 19:17:58 UTC,"@diepes, interesting. Looks like there was a loop going on there."
1670959,2018-01-29 17:46:57 UTC,"same issue with 17.10, takes a complete core,
DNSMASQ_EXCEPT=lo is not working, also after reboot, it still takes a core"
1670959,2018-06-19 13:40:54 UTC,"I also trying confront with this problem, but there is no solution at all. I tried to disable the systemd-resolved service but after that my domain resolver stop working and I lost access to webpages. I also have dnsmasq. I don't know why but I think this service is come from Ubuntu 16.04.
I upgraded my Ubuntu from 16.04 to Ubuntu 17.10 and then upgrade it to 18.04. Maybe this is why the problem is created."
1670959,2018-03-19 08:34:22 UTC,"Just to chime in:  Noticed slow machine and systemd-resolved taking 100% cpu.  Edited /etc/systemd/resolved.conf to DNSSEC=no (not off, as ""no"" was commented out in the file).  Tried systemctl restart systemd-resolved, but nothing changed.  Tried killall systemd-resolved, nothing.  Tried killall -9, and it respawned a well-behaved process.  I recently installed dnsmasq when my computer failed to resolve anything.  This is a fairly up-to-date Ubuntu 17.10."
1670959,2018-07-27 13:30:50 UTC,"What do you guys have inside /etc/resolvconf? In terms of directories, files, and their contents."
1670959,2018-01-17 06:45:10 UTC,Adding
1670959,2017-11-28 08:38:11 UTC,Christian: I've tried as I believe you have asked.
1670959,2018-07-09 22:36:27 UTC,Ubuntu 18.04.
1670959,2018-07-27 14:25:04 UTC,"And looks like we need to find out what is adding 127.0.0.1 to resolv.conf. It could come from many different sources, like a nameserver configuration in some /etc/network/interfaces carried over from xenial, or something in network-manager, etc. I guess you could start with a brute-force grep -r on /etc for 127.0.0.1?"
1670959,2018-07-31 21:44:02 UTC,"I also think it's an upgrade artifact. It happened on my upgraded laptop but not in the freshly installed desktop machine.
The problem in the laptop now (I think) hostapd that requires dnsmasq.
The workaround cited by @ahasenack in #49 seems to work."
1670959,2018-07-31 13:22:29 UTC,I don't know what is the use case you guys have that you have to have dnsmasq and resolvconf installed. Maybe there is none and this is just an artifact from a release upgrade.
1670959,2018-08-07 06:36:23 UTC,"I also had this issue after upgrading to 18.04. During the upgrade, I got asked if I wanted to keep or replace my /etc/dnsmasq.conf, I opted to replace with the package maintainer's version. The old config file had the option interface=enp0s25, the new one does not. I don't know/remember where this option came from. Could this be related?"
1670959,2018-09-28 09:08:07 UTC,I have this on Ubuntu 18.04. In my case I use dnsmasq with a custom configuration providing DHCP and DNS to multiple bridges (Virtual Machines and containers). So I need them both (in so far as I need dnsmasq and am being forced to use systemd).
1670959,2017-11-10 09:19:32 UTC,"Interesting James,
so there is a little twist that might be related and lead to a resolution."
1670959,2018-10-19 09:04:27 UTC,This annoying bug affected all upgrades to Bionic and Cosmic Cuttlefish I did so far and also effects Cosmic Cuttlefish. systemd-resolv and dnsmasq consume each 100% CPU and internet access becomes extremely slow.
1670959,2018-10-22 23:24:32 UTC,"There is some configuration that leads to a loop between these two resolvers, and that is what causes the cpu usage. If we could get a step by step way to reproduce it, it could probably be addressed."
1670959,2019-01-23 22:19:16 UTC,Also happening to me after 16.04 -> 18.04 LTS upgrade (via do-release-upgrade)
1670959,2019-01-25 13:38:41 UTC,"From the above comments I think it's clear that the problem is caused by some kind of misconfiguration resulting in a loop. It isn't clear if that misconfiguration is coming from a user error or from some bug in an upgrade path somewhere. If the latter, then it's a valid bug. However, since we don't have steps to reproduce the problem, I'm marking this bug as Incomplete in dnsmasq, to make it clear that developers aren't expected to be able to make any progress on this problem until someone can provide steps to reproduce."
1670959,2019-01-31 02:33:10 UTC,"For other souls facing this ""Medium"" issue,
a hammer-ish workaround that works for me:"
1670959,2019-05-24 17:45:10 UTC,"I'm affected by this bug, but using dnsmasq-base employed by NetworkManager and not dnsmasq package. The dnsmasq is what is consuming one core of the CPU 100% after a few minutes, not systemd-resolved. After heating the CPU for a few minutes, it drops again and the cycle repeats after a while. I keep seeing these errors:"
1670959,2019-05-27 13:04:27 UTC,"Hi Jasem,
it seems you are hitting a similar but not the necessarily same issue.
As outlined before all discussions here ended as incomplete unable to be actioned and needs clear steps to reproduce to continue."
1670959,2019-06-13 09:22:54 UTC,"Same issue on Ubuntu 18.4, that occurred after system startup."
1670959,2018-07-31 08:17:43 UTC,It seems to be dnsmasq itself:
1670959,2017-11-09 02:06:00 UTC,Also seeing this issue in Ubuntu 17.10 (artful) with:
1670959,2017-11-28 08:41:54 UTC,Maybe interesting things to note:
1670959,2017-10-15 22:51:10 UTC,@ Michael Roth (mdroth)
1670959,2017-10-24 18:09:29 UTC,Is there an official solution yet? BTW https://askubuntu.com/a/968309/ seemed to help me out.
1670959,2017-03-13 02:49:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670959,2017-04-14 14:52:54 UTC,It also happens when you are connected by wire. XPS13 9350 affected after upgrading from 16.10(yaketti) to 17.04(zetsy(.
1670959,2017-04-14 15:14:17 UTC,"Also had 100% CPU after upgrade, together with failing DNS resolution and dnsmasq complaining about having reached the max number of simultaneous requests.
Removing dnsmasq has fixed it for me."
1670959,2017-04-14 17:21:53 UTC,"Remove dnsmasq is not an option when you are using lxd/lxc.
You may reassign this bug to dnsmasq."
1670959,2017-04-14 17:33:46 UTC,lxc and lxd do not depend on dnsmasq in Ubuntu 17.04.
1670959,2017-04-16 05:27:26 UTC,"1. top
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
19147 systemd+  20   0   50848   6232   4572 R  99.0  0.1   5:43.81 systemd-resolve
 1472 dnsmasq   20   0   57020   3084   2620 R  63.1  0.0  44:03.49 dnsmasq"
1670959,2017-04-17 07:35:26 UTC,Does put 'DNSSEC=off' to /etc/systemd/resolved.conf help?
1670959,2017-04-17 13:04:29 UTC,"Kai-Heng, At least for me, it's working now. Btw, before changing DNSSEC=off, I tested removing dnsmasq to keep only systemd-resolved(as someone mentioned above), and systemd-resolved didn't resolve any domain. I had to install dnsmasq again to have some sort of connection."
1670959,2017-04-20 00:45:06 UTC,"@clvx: I think the other bug is unrelated, although maybe that's what you're running into instead of this one."
1670959,2017-04-20 01:00:30 UTC,"Weird, I can reproduce the issue again after about 1-2 weeks of silence...
I can test the DNSSEC=off setting."
1670959,2017-04-20 02:06:16 UTC,"> This is a good workaround, but perhaps the actual fix should be to remove the package on upgrade to 17.04?
"
1670959,2017-04-25 16:36:25 UTC,Recently I can definitely reproduce the issue anytime.
1670959,2017-04-17 15:24:28 UTC,"I cannot reproduce the issue very recently, for about ~1 week."
1670959,2017-05-04 22:01:09 UTC,"I see it all the time after an upgrade to 17.04. Medium priority seems an euphemism. This is a true showstopper. It is not just systemd-resolved taking a whole core. Dnsmasq takes half of another. The cpu runs hot. In a laptop, batteries drain in a snap."
1670959,2017-05-14 08:12:56 UTC,"On a fresh 17.04 install systemd-resolved didn't give me any grief until I've manually installed dnsmasq, because I wanted NetworkManager to share my connection from desktop to a laptop and without dnsmasq it fails to do so.
Now I'm hitting this CPU hog problem."
1670959,2017-05-14 08:28:42 UTC,"On another not, it seems that dnsmasq was dropped intentionally in regards to NM (https://launchpad.net/ubuntu/zesty/+source/network-manager/+changelog), in favor of systemd-resolved. But when I tried to NAT my desktop's connection to a laptop initially it didn't work out, so I looked into journalctl and found out that NM explicitly wants 'dnsmasq' executable... Another bug probably?"
1670959,2017-06-12 18:49:55 UTC,"I've also run into this CPU problem on 17.04.  Like tlk, I had to install dnsmasq because I'm running a hotspot on a USB wifi device, and the system log indicated that it wouldn't work unless dnsmasq is installed."
1670959,2017-06-12 19:05:42 UTC,"I just tried the workaround Kai-Heng mentioned in #9 above: I added 'DNSSEC=off' to /etc/systemd/resolved.conf, then rebooted.  Unfortunately I'm still seeing this CPU problem."
1670959,2017-06-12 21:30:49 UTC,"It seems that the problem is that dnsmasq is forwarding DNS queries to the systemd-resolved stub server, but they are incompatible in some way:.  From /var/log/syslog:"
1670959,2017-06-14 06:59:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1670959,2017-06-30 21:23:17 UTC,Have the same issue with 17.04. Especially then qBittorent starting. Also huge lag with apt update resolve servers.
1670959,2017-07-03 05:28:45 UTC,"Hmm I knew I remembered something related ...
In bug 1694156 we have had a - what appears to me as - similar case.
There we could track it down to a config issue, but maybe you here are affected by the same issue yet without a simple config issue to fix."
1670959,2017-07-14 02:02:39 UTC,"""if dnsmasq's option ""--dns-loop-detect"" via DNSMASQ_OPTS in /etc/default/dnsmasq.""
this does not help."
1670959,2017-09-19 11:46:29 UTC,"@ChristianEhrhardt: I'm not sure how to determine whether systemd-resolver is forwarding back to dnsmasq, hopefully it's clear from the output:"
1670959,2017-09-19 12:31:49 UTC,"Hi Michael,
I'm certainly the least expert in this case - I was just trying to help mapping that other case I have seen."
1670959,2017-10-15 18:23:23 UTC,"hi All,"
1670959,2017-04-25 21:52:13 UTC,"Actually it's happening continuously, it does not even require a wakup, of wifi reconnection or anything..."
1670964,2017-03-08 09:17:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443017"
1670964,2017-03-08 17:24:50 UTC,"Reviewed:  https://review.openstack.org/443017
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=f5c2f0da75afa155ee70e1dbb022281d0c1d8ea1
Submitter: Jenkins
Branch:    master"
1670978,2017-03-14 08:02:45 UTC,"And, I believe we need microversion if we want to add those items to non-admin user?"
1670978,2017-06-28 10:12:49 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1670978,2017-06-29 11:43:31 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1670978,2017-08-01 10:00:22 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/445844
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1670978,2017-03-14 08:01:32 UTC,"OS-EXT-SERV-ATTR:reservation_id
  OS-EXT-SERV-ATTR:launch_index
  OS-EXT-SERV-ATTR:root_device_name
  OS-EXT-SERV-ATTR:user_data"
1670979,2017-03-08 08:54:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443006"
1670979,2017-03-17 16:42:09 UTC,"The problem is, the packages have no way to know what the external VIP should be for your system. The user must specify them."
1670979,2018-06-07 09:35:18 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/443006"
1671004,2017-10-31 19:24:50 UTC,"As Radomir indicated in the review of https://review.openstack.org/443025, this fix belongs in the upstream project rather than in horizon"
1671004,2017-05-10 21:21:13 UTC,There is https://review.openstack.org/#/c/443025/ for this but for some reason did not get linked ...
1671004,2017-05-10 21:37:06 UTC,Looks like you've already got this well underway.
1671004,2017-07-07 06:55:32 UTC,"Change abandoned by Mateusz Kowalski (<email address hidden>) on branch: master
Review: https://review.openstack.org/443025"
1671004,2017-03-08 09:26:18 UTC,s/patch/path in the bug title...
1671010,2017-09-20 00:28:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671011,2018-03-27 09:56:36 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.openstack.org/444517
Reason: This has been here for some time with no updates. Abandoning to clean up the review queue"
1671011,2017-03-10 22:17:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444517"
1671018,2017-03-08 09:49:58 UTC,I wait for your answer
1671024,2018-05-12 22:14:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671031,2017-03-10 12:32:52 UTC,The affected package is murano-cfapi 1:3.2.0-0ubuntu1~cloud0 (Ocata)
1671031,2017-05-18 00:21:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671034,2017-03-22 14:29:04 UTC,The root of the issue is in fact a bug in the toolkit [1] that was fixed recently but has not hit ubuntu-app-platform yet. Because of that bug the popup prompting for the user password is not shown.
1671038,2017-03-08 14:38:59 UTC,Works for me :-)
1671042,2017-03-08 12:02:12 UTC,"One approach that, I believe, was originally considered for Unity7, was to move the functionality into the launcher ""quicklists"" - right-click context menus on launcher icons."
1671053,2019-03-22 16:18:18 UTC,Hey Zhang I know its been a while and thanks for the info about the bug.. Mitaka has been End of Life for a while now. Please let us now if  this defect still occurring in newer builds of OpenStack Manila?
1671053,2019-10-28 17:29:33 UTC,"closing, for now, feel free to re-open if necessary"
1671057,2017-03-08 12:01:22 UTC,This change was made by a bot.
1671062,2019-12-01 04:17:28 UTC,[Expired for Snappy because there has been no activity for 60 days.]
1671062,2019-10-01 16:21:14 UTC,"This bug was reported a long time ago and there have been many releases of snapd since. I'd like to ask the reporter, if possible, to re-check if the problem still occurs and provide feedback here as a comment."
1671062,2017-03-08 11:50:44 UTC,"Try using the hostname of the VM in the URL, for example http://myVM.local:3000"
1671062,2017-03-10 11:35:22 UTC,"I installed the snap in --devmode and that fixed it, I can now access rocketchat from inside the VM using localhost:3000"
1671064,2017-03-12 21:22:10 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1671070,2017-03-08 21:41:15 UTC,"Seems to be a problem with live TV streaming from BBC. I do have a licence and all was fine until this morning 8th March 2017. YouTube clips are fine, cached BBC iPlayer video is fine."
1671070,2017-03-09 22:19:55 UTC,"Isolated the problem to NoScript. 'Allow scripts globally' in NoScript allows BBC video content, live and cached."
1671070,2017-03-11 10:48:00 UTC,"Further isolated to llnwd.net
When this is allowed in NoScript BBC video content works fine. When blocked, the above error occurs. Fully repeatable. I no longer consider this a bug but leave the posting up in case anybody else has experienced this updating problem."
1671090,2017-03-08 13:42:09 UTC,"Hence it runs fine on Ubuntu 10.4 LSB: If the build was compiled from identical source, maybe it could be that this error is resulting from using different compiler/-version/-flags at building process, where there happened too aggressive code optimization."
1671090,2017-05-03 20:19:41 UTC,"this version is buggy and affects me on my debian 9 distrobution, so I am thinking this is a dosbox issue..."
1671090,2017-03-08 13:52:49 UTC,post correction: I mean of course Ubuntu 16.4 LSB.
1671093,2017-03-09 09:08:54 UTC,"Hi Alonso,
thank you for taking the time to report the bug and make Ubuntu better.
The reason this showed up on ""I just starting up the computer"" is that you had an issue to update these packages (might have been done in background, there likely also was a popup) in the past.
Now on reboot the system is notifying you if you are aware or if you want to submit a report."
1671093,2017-03-09 09:09:30 UTC,"From the log:
onfigurando qemu-system-common (1:2.5+dfsg-5ubuntu10.9) ...
insserv: warning: script 'K10runmbbservice' missing LSB tags and overrides
insserv: warning: script 'runmbbservice' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service runmbbservice and udev if started
insserv:  loop involving service udev at depth 1
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: Max recursions depth 99 reached
insserv:  loop involving service cups-browsed at depth 2
insserv: There is a loop at service runmbbservice if started
insserv:  loop involving service networking at depth 6
insserv:  loop involving service mountdevsubfs at depth 3
insserv:  loop involving service mountkernfs at depth 1
insserv:  loop involving service runmbbservice at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header"
1671093,2017-03-09 09:18:22 UTC,"No the ""weird"" one in that list to me seems to be ""runmbbservice"" I coudn't find that to be part of the distribution."
1671093,2017-03-09 09:19:04 UTC,"I'd consider this a local config error, and thereby set it to incomplete - don't hesitate to set it back to new if you think this is an Ubuntu bug (and explain why you think so)."
1671095,2017-03-10 15:10:41 UTC,"Fair enough. /me has a look what OSX does, given our indicators are very similar to those."
1671095,2017-03-10 15:17:25 UTC,Ha. It just hides the left-most stuff. Clearly Apple think this scenario is so unlikely they don't try and handle it too cleverly.
1671095,2017-03-08 14:52:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671095,2017-03-08 15:32:52 UTC,I actually believe we have most of what we need in here:
1671095,2017-03-10 10:28:51 UTC,I like those designs :)
1671095,2017-03-10 10:47:59 UTC,"I don't think Unity designs like clickable arrows, see launcher, at least :)"
1671110,2017-03-09 07:28:23 UTC,I too having the same problem with ubuntu-mate 16.04.2 distro for my raspberry pi 3.
1671110,2017-03-09 07:57:54 UTC,I could not get HDMI resolution with Ubuntu 16.04.2
1671110,2017-06-09 01:29:03 UTC,"Well... I am having this same issue, so not sure why you say this is not effecting ubuntu-mate. Same 48.2M free space on disk '/boot error OP stated."
1671113,2017-03-10 15:44:58 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/naumann__4.4.0-67.88__2017-03-10_15-14-00/results-index.html"
1671113,2017-03-10 15:36:04 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/archytas__4.4.0-67.88__2017-03-10_15-29-00/results-index.html"
1671113,2017-03-10 15:13:55 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/hainzel__4.4.0-67.88__2017-03-10_14-31-00/results-index.html"
1671113,2017-03-10 15:12:36 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/secchi__4.4.0-67.88__2017-03-10_14-37-00/results-index.html"
1671113,2017-03-10 14:58:23 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/archytas__4.4.0-67.88__2017-03-10_14-19-00/results-index.html"
1671113,2017-03-10 14:48:36 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/naumann__4.4.0-67.88__2017-03-10_14-42-00/results-index.html"
1671113,2017-03-10 14:17:31 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/naumann__4.4.0-67.88__2017-03-10_13-49-00/results-index.html"
1671113,2017-03-10 14:15:18 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/secchi__4.4.0-67.88__2017-03-10_14-09-00/results-index.html"
1671113,2017-03-10 14:04:29 UTC,"        tests ran:  19, failed: 1;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/hainzel__4.4.0-67.88__2017-03-10_13-14-00/results-index.html"
1671113,2017-03-10 14:13:12 UTC,"        tests ran:   7, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/alkaid__4.4.0-67.88__2017-03-10_13-25-00/results-index.html"
1671113,2017-03-10 15:49:04 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/hainzel__4.4.0-67.88__2017-03-10_15-43-00/results-index.html"
1671113,2017-03-10 13:51:40 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/archytas__4.4.0-67.88__2017-03-10_13-01-00/results-index.html"
1671113,2017-03-10 13:47:59 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/secchi__4.4.0-67.88__2017-03-10_13-19-00/results-index.html"
1671113,2017-03-10 13:44:44 UTC,"        tests ran:   4, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/onibi__4.4.0-67.88__2017-03-10_13-40-00/results-index.html"
1671113,2017-03-10 13:24:38 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/naumann__4.4.0-67.88__2017-03-10_12-35-00/results-index.html"
1671113,2017-03-10 13:13:54 UTC,"        tests ran:   4, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/onibi__4.4.0-67.88__2017-03-10_13-09-00/results-index.html"
1671113,2017-03-10 14:14:47 UTC,"        tests ran:  20, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/rumford__4.4.0-67.88__2017-03-10_13-10-00/results-index.html"
1671113,2017-03-10 15:58:35 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/alkaid__4.4.0-67.88__2017-03-10_14-48-00/results-index.html"
1671113,2017-03-10 21:32:13 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-10_21-30-00/results-index.html"
1671113,2017-03-10 16:38:42 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/archytas__4.4.0-67.88__2017-03-10_16-03-00/results-index.html"
1671113,2017-03-15 11:04:56 UTC,The package has been published and the bug is being set to Fix Released
1671113,2017-03-13 15:51:23 UTC,"        tests ran:   7, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-13_14-59-00/results-index.html"
1671113,2017-03-11 11:39:22 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-11_11-05-00/results-index.html"
1671113,2017-03-11 10:00:57 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-11_09-54-00/results-index.html"
1671113,2017-03-11 09:23:54 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-11_08-45-00/results-index.html"
1671113,2017-03-11 08:14:14 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-11_07-35-00/results-index.html"
1671113,2017-03-11 07:04:07 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-11_06-13-00/results-index.html"
1671113,2017-03-11 05:42:13 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-11_04-51-00/results-index.html"
1671113,2017-03-11 04:33:29 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-11_03-59-00/results-index.html"
1671113,2017-03-11 04:20:15 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-11_03-31-00/results-index.html"
1671113,2017-03-11 02:40:01 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-11_01-49-00/results-index.html"
1671113,2017-03-11 01:30:26 UTC,"        tests ran:   4, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-11_00-48-00/results-index.html"
1671113,2017-03-11 01:26:50 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-11_00-36-00/results-index.html"
1671113,2017-03-10 23:49:24 UTC,"        tests ran:  20, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-10_22-48-00/results-index.html"
1671113,2017-03-10 22:55:02 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/rumford__4.4.0-67.88__2017-03-10_21-56-00/results-index.html"
1671113,2017-03-10 12:58:09 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/secchi__4.4.0-67.88__2017-03-10_12-09-00/results-index.html"
1671113,2017-03-10 17:11:14 UTC,I've reviewed all the bugs that have not yet been verified and concluded we are not going to be reverting any of those changes and the bugs are not likely to be verified.
1671113,2017-03-10 16:13:33 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/rumford__4.4.0-67.88__2017-03-10_14-55-00/results-index.html"
1671113,2017-03-10 12:50:25 UTC,"        tests ran:  20, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/alkaid__4.4.0-67.88__2017-03-10_12-00-00/results-index.html"
1671113,2017-03-10 12:47:34 UTC,"        tests ran:  16, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/hainzel__4.4.0-67.88__2017-03-10_11-58-00/results-index.html"
1671113,2017-03-09 08:11:08 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/gonzo__4.4.0-67.88__2017-03-09_08-09-00/results-index.html"
1671113,2017-03-09 08:29:39 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/alkaid__4.4.0-67.88__2017-03-09_08-27-00/results-index.html"
1671113,2017-03-09 17:33:37 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/fozzie__4.4.0-67.88__2017-03-09_16-28-00/results-index.html"
1671113,2017-03-09 08:07:34 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/fozzie__4.4.0-67.88__2017-03-09_08-05-00/results-index.html"
1671113,2017-03-09 07:55:26 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/rumford__4.4.0-67.88__2017-03-09_07-53-00/results-index.html"
1671113,2017-03-09 07:52:05 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/alkaid__4.4.0-67.88__2017-03-09_07-50-00/results-index.html"
1671113,2017-03-09 07:47:14 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/modoc__4.4.0-67.88__2017-03-09_07-45-00/results-index.html"
1671113,2017-03-09 07:45:35 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/archytas__4.4.0-67.88__2017-03-09_07-42-00/results-index.html"
1671113,2017-03-09 07:45:24 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/hainzel__4.4.0-67.88__2017-03-09_07-42-00/results-index.html"
1671113,2017-03-09 07:44:32 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/onibi__4.4.0-67.88__2017-03-09_07-41-00/results-index.html"
1671113,2017-03-09 07:43:29 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/gonzo__4.4.0-67.88__2017-03-09_07-40-00/results-index.html"
1671113,2017-03-09 07:43:20 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/naumann__4.4.0-67.88__2017-03-09_07-40-00/results-index.html"
1671113,2017-03-09 07:42:27 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/fozzie__4.4.0-67.88__2017-03-09_07-38-00/results-index.html"
1671113,2017-03-09 07:41:15 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/ms10-35-mcdivittB0-kernel__4.4.0-67.88__2017-03-09_07-38-00/results-index.html"
1671113,2017-03-09 07:40:21 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/ms10-34-mcdivittB0-kernel__4.4.0-67.88__2017-03-09_07-37-00/results-index.html"
1671113,2017-03-09 07:40:13 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/secchi__4.4.0-67.88__2017-03-09_07-36-00/results-index.html"
1671113,2017-03-09 07:35:07 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/amaura__4.4.0-67.88__2017-03-09_07-33-00/results-index.html"
1671113,2017-03-08 16:38:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671113,2017-03-09 08:54:37 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/amaura__4.4.0-67.88__2017-03-09_08-52-00/results-index.html"
1671113,2017-03-09 09:00:03 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/secchi__4.4.0-67.88__2017-03-09_08-58-00/results-index.html"
1671113,2017-03-09 08:14:15 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-generic/onibi__4.4.0-67.88__2017-03-09_08-12-00/results-index.html"
1671113,2017-03-09 09:20:56 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/archytas__4.4.0-67.88__2017-03-09_09-18-00/results-index.html"
1671113,2017-03-09 16:50:50 UTC,"        tests ran:  10, failed: 1;
  http://kernel.ubuntu.com/testing/4.4.0-66.87-generic/s2lp3__4.4.0-66.87__2017-03-09_14-56-00/results-index.html"
1671113,2017-03-09 16:10:03 UTC,"        tests ran:  20, failed: 2;
  http://kernel.ubuntu.com/testing/4.4.0-66.87-generic/s2lp3__4.4.0-66.87__2017-03-09_14-11-00/results-index.html"
1671113,2017-03-09 16:02:00 UTC,"        tests ran:  20, failed: 2;
  http://kernel.ubuntu.com/testing/4.4.0-66.87-generic/s2lp6g001__4.4.0-66.87__2017-03-09_14-13-00/results-index.html"
1671113,2017-03-09 15:44:52 UTC,"        tests ran:  20, failed: 4;
  http://kernel.ubuntu.com/testing/4.4.0-66.87-generic/kernel01__4.4.0-66.87__2017-03-09_14-17-00/results-index.html"
1671113,2017-03-09 14:27:15 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-66.87-generic/kernel01__4.4.0-66.87__2017-03-09_13-28-00/results-index.html"
1671113,2017-03-09 14:26:06 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-66.87-generic/s2lp6g001__4.4.0-66.87__2017-03-09_13-28-00/results-index.html"
1671113,2017-03-09 09:10:28 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/naumann__4.4.0-67.88__2017-03-09_09-08-00/results-index.html"
1671113,2017-03-09 12:24:55 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-09_12-22-00/results-index.html"
1671113,2017-03-09 11:46:51 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/alkaid__4.4.0-67.88__2017-03-09_11-45-00/results-index.html"
1671113,2017-03-09 14:18:59 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-66.87-generic/s2lp3__4.4.0-66.87__2017-03-09_13-27-00/results-index.html"
1671113,2017-03-09 11:04:42 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-09_11-02-00/results-index.html"
1671113,2017-03-09 10:57:31 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/onibi__4.4.0-67.88__2017-03-09_10-55-00/results-index.html"
1671113,2017-03-09 10:55:19 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/fozzie__4.4.0-67.88__2017-03-09_10-53-00/results-index.html"
1671113,2017-03-09 10:38:20 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-09_10-36-00/results-index.html"
1671113,2017-03-09 10:29:28 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/fozzie__4.4.0-67.88__2017-03-09_10-27-00/results-index.html"
1671113,2017-03-09 10:06:55 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/rumford__4.4.0-67.88__2017-03-09_10-05-00/results-index.html"
1671113,2017-03-09 09:22:31 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/hainzel__4.4.0-67.88__2017-03-09_09-20-00/results-index.html"
1671113,2017-03-09 11:28:46 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/onibi__4.4.0-67.88__2017-03-09_11-26-00/results-index.html"
1671118,2018-07-27 09:52:17 UTC,"Any progress on this? Nobody can confirm the issue. Have you tried anything, upgrading, other fixes?"
1671118,2020-04-17 07:00:19 UTC,No answers in 2 years. I cannot reproduce it. Marking as incomplete.
1671118,2020-04-17 10:16:09 UTC, status expired
1671121,2017-03-29 09:20:43 UTC,"> 1) try to use the ListItem action to delete it
"
1671121,2017-03-22 20:41:11 UTC,"This appears to be a UITK bug. I can easily reproduce with the attached standalone example on desktop. The list view can be scrolled using the mouse wheel, and items can be clicked. After right-clicking on an item and deleting it, scrolling the view with the mouse wheel doesn't work any longer, and clicking items does nothing."
1671121,2017-03-23 06:26:03 UTC,"Let's try to rule out few things:
1) try to use the ListItem action to delete it
2) try to use a different delegate to delete the item."
1671121,2017-03-30 04:59:01 UTC,"I explained 2) badly :) I was about to mean that use other component for delegate and put a button on it, so when you click it that button deletes the delegate. Just to rule out the ListItem itself. But the 1) already rules it out, so it is indeed the popover which does something bad. And probably it is related to the focus handling, as I do not see anything else the popover would affect the ListView functionalities."
1671130,2017-03-09 10:05:18 UTC,I've tested a few times and cannot reproduce this error now.
1671130,2020-10-02 09:27:46 UTC,"Python 2.7 isn't supported anymore, closing."
1671136,2017-03-08 15:02:27 UTC,Forgot to mention Im using NFS Volume
1671143,2017-03-09 16:15:25 UTC,"Reviewed:  https://review.openstack.org/443291
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=34b3bcf89d02b039367b9bf1212c7ce0e3b5742b
Submitter: Jenkins
Branch:    master"
1671143,2017-05-31 10:55:19 UTC,"After changing the openstack_release by setting empty string """", still seen the same issue."
1671143,2017-05-31 11:09:19 UTC,Can you share you globals and group_vars config. What is the error? Maybe is a different one
1671143,2017-06-09 15:32:58 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.
1671143,2017-07-12 10:22:39 UTC,It's working now. Thanks.
1671155,2017-03-13 15:25:21 UTC,"Fix committed into lp:autopilot at revision None, scheduled for release in autopilot, milestone 1.4"
1671155,2017-03-08 18:02:46 UTC,"Replacing 'Ctrl+plus' with 'Ctrl+equal' does the trick, although it’s not semantically equivalent."
1671155,2017-03-08 17:53:30 UTC,And I haven’t yet found a working replacement for the 'Ctrl+plus' key combination ('Ctrl+minus' seems to be working fine).
1671155,2017-03-08 17:48:59 UTC,"I’m observing that references to 'Ctrl+Page_Down' don’t work any longer, changing them to 'Ctrl+PageDown' fix the issue (had to remove the underscore from 'Page_Down', and same for 'Page_Up')."
1671155,2017-03-08 19:44:32 UTC,https://code.launchpad.net/~sbaldassin/autopilot/fix_1671155/+merge/319367
1671155,2017-03-08 16:40:39 UTC,And changing references to function keys such as 'F11' to 'f11' fixes that case too.
1671155,2017-03-08 16:21:24 UTC,"This also occurs for me on xenial+overlay, but i have found changing the key from ""Escape"" to ""Esc"" fixes the problem."
1671155,2017-03-08 16:13:02 UTC,And the same tests also fail in a virtualbox xenial+overlay guest. I’m pretty sure they used to pass in that same guest when the host was running xenial+overlay.
1671155,2017-03-08 17:40:42 UTC,"References to Ctrl+<key> function as expected when I switch my keyboard layout to qwerty before running the tests. I think this is bug #1108742, which had disappeared, but is back."
1671161,2018-07-03 10:18:18 UTC,Is this fixed?
1671164,2019-02-20 05:18:47 UTC,is that also with version 2.0 of flowblade?
1671164,2019-09-02 07:44:24 UTC,or 2.2?
1671164,2019-10-10 07:22:34 UTC,try the python3 version at http://phd-sid.ethz.ch/debian/flowblade/2.4pre/
1671164,2019-10-10 23:51:03 UTC,Thank you. Let me try
1671164,2019-10-29 07:17:28 UTC,Could you provide the font you use and the text you type?
1671164,2019-11-10 05:51:25 UTC,"its. manjari font, which can be downloaded from"
1671164,2019-12-23 06:51:53 UTC,"Athul, can you check on 20.04 (focal) if it is still an issue with 2.4 of flowblade?"
1671173,2021-01-08 04:17:23 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1671173,2020-11-08 09:16:03 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1671184,2017-03-08 18:44:56 UTC,This would mean separating config items in the settings dialog also. I cant think of any nice way of doing this without always manually handling them separate in code and that seems even more messy.
1671184,2017-03-08 19:15:08 UTC,This is also related to extensions as they would be quite limited without the ability to add configurable settings in the UI. I've been thinking of the following format:
1671186,2017-03-08 18:38:10 UTC,"For translations i would like to be able to get rid of stringdefs, if the translation files then get separate during compiling instead of having to define them separately in code im all open for change like that."
1671194,2017-03-08 18:37:06 UTC,"it seems the quickstart panel is *also* out of date.  Just walking through the EC2 web UI to launch an instance, I get suggested for ubuntu
 us-east-1 ami-f4cc1de2 ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20170221
 us-east-2 ami-fcc19b99 ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20161221"
1671194,2017-03-08 21:47:05 UTC,"So it seems this wasn't as bad as I originally thought.
Juju can find an image in that region, as there *is* an image."
1671194,2020-10-09 20:19:05 UTC,"Scott, I am going to go ahead and close this as it was about an image many years ago. If it is still an issue feel free to re-open. Thanks!"
1671197,2017-03-08 18:55:30 UTC,Gist is: try and not opacify warning pop-ups.
1671197,2017-03-08 19:04:31 UTC,"I realized modals are picked on outset, they shouldn't be."
1671201,2019-09-19 14:50:15 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1671201,2017-03-08 20:05:39 UTC,"The MAAS portion of this is not that it isn't able to find machines correctly, just that i've seen several people not understand ""No available machine"". I'm not sure if it is something about the UI that isn't clear why the machines aren't available, or if it is something about the word ""available"". You could potentially say something like ""all machines that match the constraints are currently in use"". I really don't know if there is anything we could do to make it clearer, but this isn't the first person to stumble over not understanding what is wrong."
1671201,2017-03-08 23:34:57 UTC,"Okay, I realised what I've done.  It appears that the nodes need to be unprovisioned in MaaS, whereas I'd already provisioned them with Xenial.  As you say, this is really confusing because it the error sounds like ""I can't find anything that's got enough memory"" rather than ""I need an unprovisioned node to install the controller""."
1671201,2017-03-08 20:01:01 UTC,maas-slave-1.maas | Deployed Ubuntu 16.04 LTS
1671201,2017-03-08 20:02:40 UTC,"I think the message we are giving is ""correct"" (there aren't any unused machines that match constraints). I saw someone else confused by this as well, so potentially the wording of the message could be better.
The error message we are giving is the one MAAS is giving us, so if that needs to be tweaked, it would be a MAAS bug, but I don't think there is a bug in Juju itself."
1671203,2017-03-08 19:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1671203,2017-03-09 02:04:46 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-March/082900.html
1671212,2017-03-09 12:23:38 UTC,"On Wed, 8 Mar 2017 19:26:04 +0000, Evan wrote:

> Public bug reported:
>
> If you try to:
>
> organize:
>  /usr/bin/python3.5: ""/usr/bin/python""
>
> You'll get:
>
> Trying to organize file '/usr/bin/python3.5' to
> '../../../../../../../../../usr/bin/python', but
> '../../../../../../../../../usr/bin/python' already exists
>
> If instead you try:
>
> organize:
>  /usr/bin/python3.5: ""python""
>
> You'll get:
>
> [Errno 13] Permission denied: '/usr/bin/python3.5'
>
> The correct approach is to use relative paths:
>
> organize:
>   usr/bin/python3.5: ""usr/bin/python""
>
> I can't imagine why you'd want to organise absolute paths. Maybe we
> should disallow it altogether? Failing that, can we warn?
"
1671240,2017-03-09 06:36:05 UTC,"It sounds like by choosing the replace option, you have set Baobab to be the application that starts when inserting USB media. I am not 100% sure how to change it back to Nemo. I would post this issue on https://forums.linuxmint.com if you haven't already."
1671242,2019-09-19 12:02:54 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1671250,2017-05-08 19:41:46 UTC,Thanks for the help and all the efforts by everyone to get this fixed!
1671250,2017-03-11 08:57:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671251,2017-03-08 21:10:58 UTC,"StacktraceTop:
 construct<float, float const&> (this=<optimized out>, __p=<optimized out>) at /usr/include/c++/6/ext/new_allocator.h:120
 construct<float, float const&> (__a=..., __p=<optimized out>) at /usr/include/c++/6/bits/alloc_traits.h:455
 push_back (__x=@0x20: <error reading variable>, this=0x5611fccf5e68) at /usr/include/c++/6/bits/stl_vector.h:918
 GLVertexBuffer::addTexCoords (this=this@entry=0x5611fccf5e00, texture=texture@entry=0, nTexcoords=nTexcoords@entry=4, texcoords=texcoords@entry=0x20) at ./plugins/opengl/src/vertexbuffer.cpp:240
 drawPolygonClipIntersection (skewMat=..., decelerates=false, newOpacity=0.370828092, output=..., forwardProgress=0.888751566, pass=1, vertexTexCoords=0x0, c=..., p=0x5611ff4c9d10, transform=..., texture=0x5612013e2180, this=0x5612009c30e0) at ./plugins/animationaddon/src/polygon.cpp:1500"
1671254,2017-05-04 20:48:54 UTC,Still exists with python-openstackclient (3.11.0)
1671254,2017-06-28 07:13:26 UTC,"I tested the issue on newest (pike) devstack with osc 3.11.0, the problem is not reproduced,
please see the result here: http://paste.openstack.org/show/613878/."
1671255,2018-05-08 18:03:37 UTC,This change was made by a bot.
1671255,2021-01-07 04:11:48 UTC,4.8 EOL
1671257,2017-03-08 21:58:20 UTC,"Ok, confirmed -rootless mode is breaking this.  Now to figure out if pasted needs to do something different or if -rootless mode is broken in Xmir."
1671257,2017-03-09 15:35:42 UTC,"After some more investigation, in the non-rootless mode, Xmir sets the _MIR_WM_PERSISTENT_ID atom on the root window, and since pasted just queries the default root window, this works fine."
1671257,2017-03-09 15:57:12 UTC,"I don't doing it in xmir is the right place now, especially for rootless, because a new window that is opened from the app will get it's own unique persistent surface id.  pasted will definitely need to be modified to account for the rootless scenario."
1671257,2017-03-20 21:00:59 UTC,"Fix committed into lp:libertine at revision 444, scheduled for release in libertine, milestone Unknown"
1671257,2017-04-03 22:32:28 UTC,This bug was fixed in the package libertine - 1.7.1+17.04.20170331-0ubuntu1
1671266,2019-11-02 11:17:59 UTC,does systemd-rfkill ship the rfkill binary that some users use from existing snap packages via the network-control interface ?
1671266,2019-11-01 01:49:35 UTC,"Why does one need rfkill, when systemd-rfkill exists?
I see that currently core snap ships both, which is suboptimal."
1671269,2017-03-09 06:04:06 UTC,"Ahhh, i think I know what's happening. In my case, my remote system is actually a lxd container on the host machine (nested LXDs). This ""remote"" is configured to launch additional containers and so has its own lxd socket/certs."
1671269,2017-03-09 10:14:28 UTC,"Kevin, thanks for diagnosing the issue. I think it would be reasonable to have a unique name for the credentials. Perhaps incorporating the server's fingerprint would be best, since they are tied to that server after all."
1671269,2019-06-27 07:42:03 UTC,This is an old issue and since it was reported there was a lot of re-work of Juju-LXD integration including LXD credential management.
1671269,2019-08-27 04:17:20 UTC,[Expired for juju because there has been no activity for 60 days.]
1671270,2017-03-17 07:00:52 UTC,I do not believe it is broken :) I don't think we have ever supported tab completion in 'juju switch'.
1671270,2017-03-17 13:18:31 UTC,Categorize this issue as creatively as you wish. Juju prints an ERROR when you hit tab on the switch command.  Some of those controller names are quite long and not convenient for users to type. Tab completion works on other commands and it is reasonable to expect Juju to not error when tab is used on the switch subcommand.
1671270,2017-03-17 15:56:40 UTC,Could we split this issue into two different bugs? One bug for the tab completion that can be on a wishlist. One bug for the ERROR printed to the end user when they are using the juju switch command?
1671270,2017-03-21 01:56:41 UTC,"@Matt Bruzek (mbruzek),"
1671272,2017-03-11 19:07:55 UTC,"Adding a text file named ""deja-dup-restore-missing.contract"" to ~/.local/share/contracts containing the following:"
1671272,2017-03-10 16:59:09 UTC,Depending on what commandline parameters deja-dup needs it may be possible to do this more simply with a .contractor file.  I am not sure how this should be distributed for a non-elementaryos application.
1671272,2017-03-12 01:20:23 UTC,Ah. I did not know that I can just make contracts for applications like that. I will keep that in mind next time I find a missing menu entry.
1671277,2017-12-29 16:18:18 UTC,i cant get it upgrade i have red circle with minus in it something about cant be read meliform ????
1671278,2017-04-12 17:22:26 UTC,"I'm getting the same thing, and I think I can help with some more information."
1671278,2017-04-12 17:37:35 UTC,This may be related:
1671278,2017-04-12 17:39:46 UTC,and this:
1671278,2017-04-12 18:00:11 UTC,This change was made by a bot.
1671278,2017-04-13 04:47:57 UTC,"Patch is set to be included in 4.11-rc7 now, it should follow in a stable update not long after"
1671278,2017-04-14 04:06:54 UTC,You guys work fast!
1671287,2017-03-09 01:01:04 UTC,This change was made by a bot.
1671287,2017-04-04 21:28:02 UTC,"The upstream link is no good, and I haven't been able to find it on bugzilla.kernel.org by searching.
It is unclear to me why this bug report was set to incomplete."
1671287,2017-04-04 21:31:48 UTC,The correct upstream link is: https://bugzilla.kernel.org/show_bug.cgi?id=194835
1671287,2017-04-05 22:43:09 UTC,"For me these messages were a side effect of unattended upgrades, and the os-prober running as some auto-removal thing. All stuff that I do not want, and did not use to be the default. Having either disabled or uninstalled that stuff, I now expect these message to go away."
1671288,2017-04-13 09:50:48 UTC,"@loganv hmm, indeed. We need new options for user and port."
1671288,2017-03-31 14:27:32 UTC,"@Oliver theres a big problem with that, live_migration_inbound_addr is not templated afaik so any time you would like to specify a non standard user or port for your migration config, you lose the ability to dynamically populate the host for each specific nova-compute instance. You'll have to statically populate it on every single config based on some other discovery mechanism."
1671288,2017-03-31 10:41:42 UTC,s/live_migration_schema/live_migration_scheme/
1671288,2017-03-31 10:41:02 UTC,"Something like this may work:
    virt_type=qemu
    live_migration_schema=ssh
    live_migration_inbound_addr=user@host:port"
1671288,2017-03-31 10:10:53 UTC,"Due to the URI config being hard to used due to bugs like this:
https://bugs.launchpad.net/nova/+bug/1677913"
1671288,2017-03-13 14:46:01 UTC,The point I have is less about the documentation not being updated.
1671288,2017-03-30 23:36:28 UTC,^H^H^H didn't spot the previous like to https://libvirt.org/remote.html#Remote_URI_reference which appears to be more complete list of options
1671288,2017-03-30 23:17:46 UTC,Expect we will need an option for each component documented here: https://libvirt.org/guide/html/Application_Development_Guide-Architecture-Remote_URIs.html
1671288,2017-03-14 12:07:28 UTC,"I agree, we're using
live_migration_uri = qemu+ssh://nova@%s/system?keyfile=/var/lib/nova/.ssh/id_rsa&no_tty=1&no_verify=1"
1671288,2017-04-13 11:36:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456571"
1671288,2017-03-10 11:33:43 UTC,"live_migration_uri is deprecated for removal in favor of two other options that
allow to change live migration scheme and target URI: ``live_migration_scheme``
and ``live_migration_inbound_addr`` respectively."
1671288,2017-03-31 09:53:31 UTC,The real need here is having a single key setup for migration and live-migration. The problem is the current configuration options (if you ignore the deprecated ones) don't seem to help do that.
1671288,2019-05-29 09:33:59 UTC,openssh8.0p1 can not support.
1671288,2017-03-17 07:36:50 UTC,"@loganv, @gyurco the change was made in that patch series https://review.openstack.org/#/c/410817
and first started with adding live_migration_inbound_addr in https://review.openstack.org/#/c/245005/."
1671291,2017-03-09 01:30:13 UTC,This change was made by a bot.
1671291,2017-03-09 19:48:10 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1671291,2017-03-25 15:52:19 UTC,I tested the latest mainline 4.4 kernel (4.4.56) as requested.  It exhibits the same behavior.  I also tried the 4.8.17 mainline kernel with the same results.  I still have to fall back to kernel 4.8.0-30.
1671291,2017-04-22 20:28:21 UTC,"I have continued to research this issue. In the meantime, I have also upgraded to Ubuntu 17.10 and the issue persists with kernel 4.10.0-19."
1671291,2017-05-03 05:41:36 UTC,"Can you try these Linux versions:
4.8.6
4.8.7
4.8.8"
1671291,2017-05-21 20:11:01 UTC,Thank you.  I tried 4.8.6 and it seems to work fine.  Hopefully the radeon fixes will make their way into the Ubuntu 17.04 4.10 kernel soon.  I think this bug can be closed.
1671311,2017-03-13 03:59:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444703"
1671315,2017-04-12 18:42:44 UTC,This issue was fixed in the openstack/freezer-web-ui 5.0.0.0b1 development milestone.
1671316,2017-03-09 02:56:10 UTC,"StacktraceTop:
 sn_xcb_display_new (xconnection=0x5649820e5ac0, push_trap_func=push_trap_func@entry=0x0, pop_trap_func=pop_trap_func@entry=0x0) at sn-common.c:149
 sn_display_new (xdisplay=xdisplay@entry=0x5649820e4870, push_trap_func=push_trap_func@entry=0x7f94ec0978e0 <sn_error_trap_push>, pop_trap_func=pop_trap_func@entry=0x7f94ec0978d0 <sn_error_trap_pop>) at sn-common.c:77
 wnck_screen_construct (number=0, screen=0x564982118640, display=0x5649820e4870) at screen.c:543
 wnck_screen_get (index=0) at screen.c:601
 bamf_legacy_screen_get_default ()"
1671316,2017-03-14 15:40:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671320,2017-03-09 14:34:58 UTC,"""some things may require that environment file to be filled in to work properly"""
1671320,2019-09-19 12:02:57 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1671329,2017-09-07 02:11:23 UTC,"The first one is odd. Cannot cleanup failed restore because a restore is in
process."
1671329,2017-09-07 20:46:51 UTC,"Would be interested to compare the shared secrets. Anyways, the test is running the following commands. Probably need to dig in with a manual test to see what's happening:"
1671333,2017-03-10 01:29:37 UTC,"I am not sure what do you want, we can set 'fixed_ip' for server, like this:
.....
resources:
  my_server:
    type: OS::Nova::Server
    properties:
      ...
      networks:
        - network: {get_param: net}
          fixed_ip: {get_param: fixed_ip}
          floating_ip: {get_param: floating_ip}"
1671333,2017-03-10 01:52:48 UTC,"Sorry for misunderstand, about the param 'accessIPv4' is an old one in nova, afaik, it's not used now, and not sure what's the user case of it, if you have to set this, please let me know the user case, then we can support this."
1671338,2017-04-12 18:29:36 UTC,This issue was fixed in the openstack/python-neutronclient 6.2.0 release.
1671338,2017-03-09 08:30:29 UTC,Sorrym wrong line number: https://github.com/openstack/python-neutronclient/blob/master/neutronclient/osc/v2/fwaas/firewallpolicy.py#L60
1671338,2017-03-09 10:31:56 UTC,"Hi zhaobo ,
I pushed a patch https://review.openstack.org/#/c/443518/1.
Didnt know you also created a patch yesterday."
1671338,2017-08-22 11:36:57 UTC,This issue was fixed in the openstack/python-neutronclient 6.1.1 release.
1671338,2017-03-09 08:55:54 UTC,"@reedip, Thank you very much. :)"
1671338,2017-03-09 08:27:43 UTC,"Hi zhaobo :
Please check the paste information : http://paste.openstack.org/show/602045/"
1671338,2017-03-09 08:54:56 UTC,I had introduced a patch to neutron-client.
1671338,2017-03-09 06:13:52 UTC,"@reedip, I traced the issue from server side to client..hah..The server side is OK, it will process the ordered fw_rules according to the input fw_rule list. But it is OK that you could check the server side more careful if I miss something. :)"
1671338,2017-03-09 05:00:33 UTC,"Hi zhaobo: The data is coming as an ordered list. I do not think this is an issue with OSC, will look into from the FWaaS side as well."
1671339,2017-03-09 06:38:29 UTC,"I am not familiar to directly work on the debian/patches, here's the ""raw"" patch that can solve this issue."
1671339,2017-03-09 08:32:19 UTC,"The attachment ""resume-update-bg.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1671339,2017-07-08 05:07:13 UTC,This creates other issues with lightdm with xorg.
1671339,2018-11-12 22:40:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671339,2018-11-13 08:54:34 UTC,"Thank you for your bug report/patch, could you give some details about the issue/on what video card/driver is it happening exactly? If that was impacting all nvidia users we would have more reports about it which is not the case."
1671340,2017-04-05 18:44:10 UTC,"I'm getting the same thing. This is my version.
It might have to do with NVidia drivers that are installed.
Do you happen to be using an NVidia card for your computer?"
1671340,2017-04-06 02:48:40 UTC,Yes that's correct Eric! Even my machine has NVidia graphics and I'm using its proprietary drivers.
1671355,2017-06-07 07:37:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671356,2018-01-25 09:04:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1791
1671357,2018-01-25 08:32:54 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3658
1671357,2017-03-09 06:23:25 UTC,I built Percona Server different ways and the dialog.so failed to find the symbols
1671357,2017-03-09 06:25:40 UTC,brew install percona-server
1671357,2017-03-09 06:26:06 UTC,percona-server-5.7.17-11
1671357,2017-03-10 00:12:09 UTC,"$ nm -gu dialog.so
___stack_chk_fail
___stack_chk_guard
___stdinp
_dlsym
_fgets
_free
_getpass
_my_stpnmov
_strcmp
_strdup
_strlen
_strncpy
dyld_stub_binder"
1671357,2017-03-10 09:16:14 UTC,There appears to be an issue with the build and enabling dialog.so to find my_stpnmov in libperconaserverclient.dylib.
1671357,2017-03-15 15:47:14 UTC,An additional incompatibility is the moving of the plugins to a different directory.
1671357,2017-03-20 04:19:33 UTC,The library should be named libmysqlclient instead of libperconaserverclient on OS X.
1671359,2017-03-09 08:38:31 UTC,"Reviewed:  https://review.openstack.org/443447
Committed: https://git.openstack.org/cgit/openstack/mogan/commit/?id=95765c53d3c736041c5ef8e0b6b84724751952a1
Submitter: Jenkins
Branch:    master"
1671359,2017-03-09 07:10:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443447"
1671364,2018-01-31 07:50:13 UTC,"I try to reproduce the bug but everything work fine.
Environment
===========
1. OS
# cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core)
2. libvirt && qemu-kvm
libvirtd (libvirt) 3.2.0"
1671364,2017-04-03 11:51:56 UTC,"Yeah, seems like changing the template is a way to fix this."
1671364,2017-04-03 11:43:05 UTC,"Oh, there is a note about permissions issue -
 https://github.com/openstack/ironic/commit/959689e30d71e4f10493bc2c62f6e90c8875b961"
1671364,2017-04-03 11:41:13 UTC,"Right, I remember having trouble with setting a custom log dir due to selinux permissions. I remember we did change this in the docs at some point."
1671364,2017-03-09 06:51:10 UTC,"I found 'machine' type in template file
<type arch='{{ arch }}' machine='pc-1.0'>hvm</type>"
1671364,2017-03-09 10:49:11 UTC,"It works OK on ubuntu 14.04.
# qemu-system-x86_64 -machine help
Supported machines are:
pc-0.13              Standard PC (i440FX + PIIX, 1996)
pc-i440fx-2.0        Standard PC (i440FX + PIIX, 1996)
pc-1.0               Standard PC (i440FX + PIIX, 1996)"
1671364,2017-03-13 17:24:35 UTC,I just tried this and can confirm it. Though I get a permissions error on my logs:
1671368,2017-03-09 07:29:17 UTC,Default Comment by Bridge
1671368,2017-03-23 07:09:26 UTC,------- Comment on attachment From <email address hidden> 2017-03-23 03:01 EDT-------
1671368,2017-03-27 12:20:44 UTC,"------- Comment From <email address hidden> 2017-03-21 00:46 EDT-------
The commit which adds generic/404 test indicates two kernel commits which fixes this issue,"
1671368,2017-08-23 13:20:36 UTC,"------- Comment From <email address hidden> 2017-08-23 09:14 EDT-------
Distro team, Any update on cherry pick of the above patches ?"
1671368,2018-03-12 13:20:24 UTC,"------- Comment From <email address hidden> 2018-03-12 09:13 EDT-------
(In reply to comment #19)

> Distro team, Any update on cherry pick of the above patches ?
"
1671368,2018-05-21 09:00:31 UTC,"------- Comment From <email address hidden> 2018-05-21 04:55 EDT-------
(In reply to comment #20)

> (In reply to comment #19)
> > Distro team, Any update on cherry pick of the above patches ?
>
> This needs to be tested on Ubuntu 17.04 or 18.04? If so, which kernel
> includes the patch mentioned?
>
> Thanks,
> Harish
"
1671368,2018-07-02 04:19:24 UTC,"------- Comment From <email address hidden> 2018-07-02 00:12 EDT-------
Hi"
1671376,2017-06-28 07:01:53 UTC,"I tested the issue on newest (pike) devstack with osc 3.11.0, the problem is not reproduced:"
1671378,2019-07-17 13:25:50 UTC,"/boot is a FAT filesystem meaning it doesn't natively have the concept of inode numbers. Presumablly the kernel is making up inode numbers on the fly to satisfy the unix APIs, resulting in different inode numbers each time."
1671378,2019-07-17 13:38:52 UTC,"Silly me! I should've thought of the FAT-partition...
Thanks for the clarification, @plugwash!"
1671378,2019-07-17 13:03:09 UTC,What is the report when you run it on stretch or buster?
1671379,2017-03-09 19:15:57 UTC,This sounds like something that wouldn't be resolved until we have the multiple port bindings spec in place to get the switch mech driver to wire up the additional vlan.
1671379,2017-03-09 19:17:49 UTC,Can you see if the solution in https://bugs.launchpad.net/neutron/+bug/1414559 would have helped?
1671379,2017-03-13 06:26:40 UTC,https://bugs.launchpad.net/neutron/+bug/1414559
1671379,2017-03-27 15:20:38 UTC,It might be related to this https://bugs.launchpad.net/nova/+bug/1605016. Have patch for it where port binding in done based on libvirt events instead if happening in 3 rd step as mentioned above. https://review.openstack.org/#/c/434870/. Will try to replicate this issue on top of my patch and see what happens.
1671379,2017-03-28 08:48:32 UTC,"Hello, Zhipeng Shen, have you tested the patch mentioned in comment #4?"
1671379,2017-04-06 07:39:14 UTC,"Hello, Timofey Durakov. I'm sorry to reply so late."
1671379,2017-04-30 10:34:55 UTC,"Hello, Timofey Durakov, Sivasathurappan Radhakrishnan
I don't test the patch mentioned in comment #4 yet.
The libvirt version of the bug (https://bugs.launchpad.net/nova/+bug/1671379)  environment is 1.2.17， it is less than the lowest version of the post-copy bug ( https://bugs.launchpad.net/neutron/+bug/1414559)."
1671379,2017-06-27 15:57:56 UTC,"Automatically discovered version kilo in description. If this is incorrect, please update the description to include 'nova version: ...'"
1671381,2017-03-28 09:53:19 UTC,"Reviewed:  https://review.openstack.org/446355
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=abf8711d9b07577e191b1de918b1b2af9d8bde2f
Submitter: Jenkins
Branch:    stable/ocata"
1671381,2017-03-28 08:46:51 UTC,"Reviewed:  https://review.openstack.org/448412
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=cb42526455e4ec2684ff36c04ba64c5bcb595a29
Submitter: Jenkins
Branch:    stable/ocata"
1671381,2017-03-28 09:51:56 UTC,"Reviewed:  https://review.openstack.org/444133
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=04882ff2506c05abe1107fc46e7eab467103a696
Submitter: Jenkins
Branch:    stable/newton"
1671381,2017-03-28 09:53:49 UTC,"Reviewed:  https://review.openstack.org/448411
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=396a3d534f22e7d88b4f521c4e484ad468d1846d
Submitter: Jenkins
Branch:    master"
1671381,2017-03-28 08:47:57 UTC,"Reviewed:  https://review.openstack.org/446353
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=0d50a07e59dd87bf7b825ab69f06ac5e5f4b52b8
Submitter: Jenkins
Branch:    master"
1671381,2017-03-22 06:43:38 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/448412"
1671381,2017-03-10 07:51:14 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/444133"
1671381,2017-03-16 08:37:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/446355"
1671381,2017-03-16 08:37:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446353"
1671381,2017-03-15 07:28:17 UTC,"Reviewed:  https://review.openstack.org/443532
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=3eb1db490779fde1a9c0375ca170e489d78208de
Submitter: Jenkins
Branch:    stable/newton"
1671381,2017-03-09 09:54:00 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/443532"
1671381,2017-03-22 06:42:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448411"
1671385,2017-08-09 09:24:27 UTC,"Change abandoned by Dave Chen (<email address hidden>) on branch: master
Review: https://review.openstack.org/443509
Reason: This has been duplicated with https://review.openstack.org/#/c/401009/"
1671385,2017-03-09 08:59:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/443509"
1671385,2017-03-29 00:05:47 UTC,This is one seems to be a duplicate of this bug https://bugs.launchpad.net/nova/+bug/1643623
1671392,2017-03-13 08:29:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671397,2017-03-27 08:30:14 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1671397,2017-03-10 10:07:14 UTC,"Hi,
thank you for your report.
Lacking a VNX I can't right away try to reproduce, but I quickly checked the BIM DS8K I had.
One thing I wondered is that I thought the produce/vendor data there displayed by multipath is only what it got back on a scsi inquiry.
AFAIK - multipath-tools make no decision there ""what"" it should be.
It certainly has rules that filter/handle different types differently - but as I said I thought it is just the reply to the scsi inquiry to the device that populates the data."
1671397,2017-03-10 12:50:02 UTC,I really think it is a multipath-tools issue. Here are the comparisons:
1671397,2017-03-13 08:30:00 UTC,"Just to clarify - two logins for was what you call ""Provision 2x LUNs from VNX"".
AFAIK the LUNZ is a representation of ""what could be"" and once provisioned that is replaced by ""the real thing"". Since in my example that matches an FCP SAN login I might have named it badly for you to realize what I meant - sorry."
1671397,2017-03-13 08:41:51 UTC,"1. rescan-scsi-bus.sh is used to rescan SCSI buses;
2. Restart the services won't solve the problem, but a reboot will."
1671397,2017-03-13 10:48:26 UTC,"​Thanks KC,
that makes it interesting."
1671397,2017-03-13 11:19:07 UTC,"While I think restarting the service is bigger than that another thing
worth at least to try is if it has an effect is reloading the devmap.
$ multipath -r"
1671397,2017-03-20 05:38:51 UTC,"My setup was being used for some other tasks for quite some time. Now, it can be used again. But unfortunately, multipath -r still won't fix the problem."
1671397,2017-03-27 08:00:57 UTC,"Nobody else with the same HW showed up, so I'm afraid you have to debug that on your own :-/
If you have support on your storage server those might be able to help - try to loop them in?"
1671398,2017-10-20 16:45:48 UTC,"Change abandoned by Mike Perez (<email address hidden>) on branch: master
Review: https://review.openstack.org/445372
Reason: Feel free to rebase and open again when you have time. Thank you."
1671398,2017-09-26 22:50:25 UTC,Unassigning due to no activity for > 6 months.
1671398,2017-03-14 09:15:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445372"
1671413,2017-03-09 14:40:51 UTC,"Hey Joseph,"
1671415,2019-09-19 12:03:00 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1671421,2017-07-19 08:28:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671421,2017-07-19 08:31:52 UTC,I confirm this issue also on Artful. I tried installing fcole90-hexgl-webapp and it keeps asking me about this.
1671421,2017-07-19 08:37:32 UTC,Using the command sudo /usr/lib/snapd/snap-discard-ns $APP_NAME fixes the issue.
1671421,2018-01-02 15:47:16 UTC,The discard-ns will happen automatically once https://github.com/snapcore/snapd/pull/4329 lands.
1671421,2018-01-30 09:59:31 UTC,This is now handled automatically. It will be a part of the 2.31 release.
1671424,2017-03-21 19:09:25 UTC,qtmir always destroys a window if it doesn't do so itself after being requested to close.
1671424,2017-03-22 02:07:02 UTC,Indeed the close button and Alt+F4 should never ever destroy a window.
1671424,2017-03-15 03:30:58 UTC,See also bug 1672751
1671424,2017-03-09 10:57:27 UTC,"Part of the answer is ""that's bad design, kate should store the state and restore it later""."
1671424,2017-03-10 02:38:11 UTC,The test case with kate works correctly in mir_proving_server (Alt+F4 brings up a Save Documents dialog). It's only failing in Unity8.
1671424,2017-03-10 06:03:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671445,2017-03-10 10:33:49 UTC,A more detailed bug description was supplied as a debian bug report:
1671445,2017-05-31 14:02:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671445,2017-05-31 14:04:27 UTC,"Considering that cifs+kerberos mounting is completely broken, please either upgrade cifs-utils to 6.6 or drop 6.6 and provide 6.4 instead (which works just fine even in a 17.04 system).
For anyone needing a workaround, add xenial to /etc/apt/sources.list and downgrade cifs-utils to 6.4."
1671445,2017-05-31 14:05:33 UTC,"I obviously meant ""upgrade to 6.7"". If there are concerns with that, at least putting it into -proposed or similar would provide a nicer fix for anyone needing it than having to install the xenial package."
1671448,2020-08-18 16:57:51 UTC,"Reviewed:  https://review.opendev.org/507446
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c9242f9a889f4d69653de4d21bec6060f549ee7b
Submitter: Zuul
Branch:    master"
1671448,2020-07-17 15:32:56 UTC,I added some basic tempest tests which should ensure that the new rbac code doesn't cause a regression.  Would love a review of either patch.
1671448,2020-07-14 16:27:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/740999"
1671448,2020-07-14 15:46:47 UTC,"That last patch is mine.  It was my understaning that https://review.opendev.org/#/c/507446 is awaiting review -- is that incorrect?  We had discussed adding tests to that patch, but given that equivalent policy code doesn't currently have tests I wouldn't expect lack of tests to be a blocker."
1671448,2020-07-06 19:53:05 UTC,"Hi David,"
1671448,2020-06-29 20:30:40 UTC,I see https://review.openstack.org/505155 has been abandoned in favor of https://review.opendev.org/#/c/507446 but there hasn't been activity on it for many months.
1671448,2018-12-11 05:37:32 UTC,"Change abandoned by Reedip (<email address hidden>) on branch: master
Review: https://review.openstack.org/505155"
1671448,2018-12-10 19:00:37 UTC,I also need this fixed :) I want to make quota usage publicly visible to my users for reporting &c. and it's weird that read-only APIs are behind an admin check.
1671448,2017-09-19 13:02:08 UTC,"Sorry for delay. It's look like quota API don't use pecan, but legacy controller instead. It was introduced in this commit https://github.com/openstack/neutron/commit/5cb73f5f4694e077c9bb0a3bf65f04d4c32fe3b5#diff-350062450daf0d63ec1c37a60c552f32"
1671448,2017-09-19 10:31:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505155"
1671448,2017-09-19 09:46:52 UTC,"I have a patch , but test cases remain.
Maybe you can assist me in the same, or maybe add up in the current patch impelementation which I have prepared ?"
1671448,2017-09-19 09:34:16 UTC,"@reedip: Hi, thanks for response. OK, I start working on this. I just want to make sure, that I don't screw up with someone else work.
OK I use pecan implementation and see what I can do."
1671448,2017-09-26 09:32:41 UTC,"Hi,
I sent alternative patchset. I edit both controllers. Legacy which is actually used and new pecan which is not used at this moment but in future can be again.
It add new policy:
- update_quota
- get_quota
- delete_quota
- default_quota"
1671448,2017-09-19 08:17:37 UTC,"Hi,
lets presume following scenario. I need to create user with rights to define quotas for others. Quotas like max number of networks, routers etc. And also I don't want to give this user full access (for security reasons). So he doesn't see all objects from all projects."
1671448,2017-09-19 09:14:23 UTC,"@Viktor: Hi,
Sorry , I skipped this issue for sometime.
But your fix seems to be correct, but the implementation can be changed to the pecan_wsgi/controllers/quota.py"
1671448,2017-03-30 12:04:44 UTC,"Reedip , I have updated the description of the defect with more details on the problem reported here."
1671448,2017-03-31 16:58:37 UTC,It sounds like a good isolated request. The starting point would be: https://github.com/openstack/neutron/blob/master/neutron/pecan_wsgi/controllers/quota.py#L60
1671448,2017-03-31 17:01:16 UTC,Would like to take it up once Driver's meetup has finalized this
1671448,2017-04-20 01:02:44 UTC,"Reedip, What are finalized in the driver's meetup on this defect ?"
1671448,2017-04-20 03:57:46 UTC,"Hi Divya,
This is still pending the proper driver team approval."
1671448,2017-03-13 20:58:35 UTC,Please describe exactly what you try to achieve here. Do you want to limit the number of RBAC policy resources per tenant? Or do you want to be able to expose some API requests that are currently not exposable? Which of them then?
1671448,2017-06-22 22:46:23 UTC,"This is good to go. @reedip, please proceed directly with an implementation, this doesn't need a spec."
1671448,2017-05-18 21:52:15 UTC,"I agree with the proposal, seems like a well isolated and reasonable thing to do. I would even say that's a bug and not a RFE."
1671448,2017-09-15 17:11:37 UTC,"The lack of rules in policy.json means 'either the tenant or the admin'. I am not sure this is as simple as adding entries in the policy.json, especially when I read [1]. That said, can you elaborate why you would want to make this configurable?"
1671448,2017-09-26 09:25:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507446"
1671448,2017-09-15 12:05:52 UTC,"Hi guys,
it there some progress with this issue? It's kind of blocker for me so I offer help.
It looks like simple isolated change, so I could write this whole patch if needed. But I don't want to cause problems if someone is nearly done with this."
1671449,2017-03-09 12:17:19 UTC,something changed after this update
1671449,2017-03-09 12:26:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671449,2017-03-09 12:30:23 UTC,Hey dinamic! Thanks for the bug!
1671449,2017-03-09 12:43:07 UTC,https://pastebin.ubuntu.com/24145807/
1671449,2017-03-09 12:51:25 UTC,"Thanks for that. Can confirm it is nothing gpu/graphics related, it is a bug in our UITK. Fix on the way..."
1671449,2017-03-10 01:53:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671449,2017-03-28 21:58:16 UTC,This in QA queue now: https://bileto.ubuntu.com/#/ticket/2647
1671449,2017-04-03 14:46:45 UTC,This bug was fixed in the package ubuntu-ui-toolkit - 1.3.2190+17.04.20170327
1671449,2017-03-09 12:35:09 UTC,"suddenly after the last update. using intel gpu (sandy bridge something). worked great before the last update.
ok, i'll remove the logs and restart."
1671453,2019-09-19 11:56:04 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1671453,2017-03-10 09:16:40 UTC,I need to look deeper to see if this has a large impact on MAAS or not. My gut feeling is that this is potentially low to medium impact.
1671453,2018-10-24 03:52:04 UTC,"FWIW, the kernel treats grat-arp and unsolicited-na as the same variable, so setting one sets the other."
1671464,2017-03-11 12:07:49 UTC,Same bug in 16.04.2 as well.
1671464,2017-03-11 12:07:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671468,2017-03-09 16:09:40 UTC,"I thought this was the whole point of having a dynamic max_age. We can't inspect TEMPORARY vs PERMANENTLY directly, but if it's is_valid we wait until 5 days before sending a mail, that gives more time for long-running autopkgtests."
1671468,2017-03-09 16:29:47 UTC,"Right, the idea was to replace excuse.is_valid with something like excuse.current_verdict. britney already has the policy_verdict local variable in should_upgrade_src() which contains what we need, it just needs to move into the Excuse object. Preferrably it should replace excuse.is_valid to avoid redundancy, or is_valid could maybe become a property which is true iff self.policy_verdict not in [PolicyVerdict.REJECTED_PERMANENTLY, PolicyVerdict.REJECTED_TEMPORARILY]"
1671468,2017-03-09 16:31:44 UTC,Nah. The point of that is that valid excuses that are being held up at update_output stage often legitimately take a long time to resolve.
1671468,2017-03-09 17:01:15 UTC,Hey pitti! Nice to see you on britney bugs still. :-)
1671468,2017-03-09 17:04:10 UTC,"@Iain: We are talking about two different things. My comment #2 was about replacing the existing Excuse.is_valid variable with a property that looks at the new Excuse.current_verdict variable, and thus provides backwards compatibility (unless it's easier to just port the existing users of Excuse.is_valid directly to it -- can't be that many)."
1671468,2017-03-09 17:42:54 UTC,"On Thu, Mar 09, 2017 at 05:04:10PM -0000, Martin Pitt wrote:

> @Iain: We are talking about two different things. My comment #2 was
> about replacing the existing Excuse.is_valid variable with a property
> that looks at the new Excuse.current_verdict variable, and thus provides
> backwards compatibility (unless it's easier to just port the existing
> users of Excuse.is_valid directly to it -- can't be that many).
>
> Of course is_valid is not the right field to look at for the email
> notification policy -- that should be Excuse.current_verdict, and of
> course it should only fire if the verdict is
> PolicyVerdict.REJECTED_PERMANENTLY.
"
1671468,2017-03-09 21:53:02 UTC,"Oh right, I missed that uninstallability etc. also sets is_valid to False."
1671468,2020-09-18 08:37:24 UTC,"I think we've fixed this already, going to close the bug. Thanks 2017-us!"
1671472,2017-03-10 00:26:48 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1671474,2017-03-12 20:44:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444667"
1671474,2017-03-17 14:49:35 UTC,"Reviewed:  https://review.openstack.org/444667
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=99b3203923f12ba4d17f4c20b010978fa813d53b
Submitter: Jenkins
Branch:    master"
1671474,2017-03-21 17:04:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448197"
1671474,2020-01-14 07:55:09 UTC,"Change abandoned by Szymon Datko (<email address hidden>) on branch: master
Review: https://review.opendev.org/448197
Reason: No time for further work on this topic right now :-("
1671475,2017-03-10 02:05:10 UTC,Incomplete. Running kmines under Xmir on zesty does not exhibit the bug for me. Tried Mir demo servers as well as Unity8.
1671475,2017-05-09 04:17:48 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1671491,2017-03-17 15:31:00 UTC,"Hello,"
1671494,2017-03-17 15:36:03 UTC,"Hello,"
1671505,2017-03-28 10:27:45 UTC,We haven't hit this error after 17-march so i think it has been fixed by some of the commits merged between 14-march (last hit) and 17-march (firs success).
1671505,2017-03-28 10:50:14 UTC,This bug is no more valid as per the reporter.
1671505,2017-03-28 12:00:38 UTC,I'm reopening this. We haven't seen this in master branch as stated in previous message but i just found we are still hitting it in jobs running with ocata stable.
1671505,2017-04-04 11:14:23 UTC,Is the rdo ci using a TZ other than UTC?
1671505,2017-04-04 11:17:53 UTC,Never mind. I was thinking of a different error.
1671506,2018-09-12 22:16:50 UTC,I did some work for 18.05 to support federated identity in Keystone and OpenStack dashboard charms.
1671506,2017-11-08 15:37:24 UTC,"Thanks a lot Bryan, appreciate that!
    I was doing other things these days, but hopefully I may try to get
back to work on this some time coming week.
  We'll keep in touch, thanks again!"
1671506,2017-11-08 15:02:16 UTC,Hi Fulvio
1671506,2017-06-28 10:09:26 UTC,"Hallo James,
    sorry for being so ignorant with Git... I'd like to commit my changes
for review."
1671506,2017-05-31 08:08:55 UTC,Hi Fulvio
1671506,2017-05-19 13:51:02 UTC,"Hallo James, I just made a commit of my work. This time I commited from my
working directory, which is the same I used to push an apparently
functional charm to our jujucharms area, and also tried to write a
meaningful commit message."
1671506,2017-05-15 13:02:27 UTC,"Hallo James! I have been very silent for a long while, my apologies:
however, last week I was back on this task and I think I have completed at
least the configuration part. Now I am playing with keystone_hooks to add
calls to activate the relevant pieces of code. I hope I will be ready for
another commit in a few days.
Thanks for following this up!"
1671506,2017-03-10 17:01:57 UTC,Hi Fulvio
1671506,2017-03-10 13:39:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/444299"
1671506,2017-05-30 06:54:25 UTC,"Hallo James, sorry to bug you but I am a bit afraid I may have done
something not properly, as after my last commit nothing happened, as far as
the automated machinery for testing is involved. Last time I was notified
within 24 hours that my package had been compiled, whereas this time...
silence.
Did I do something wrong, or may be as the modificiations are scheduled for
17.08, the relevant testing has been automatically postponed?
Thanks for your help"
1671509,2017-03-09 21:28:20 UTC,"Hi Chris, thanks for reporting this.  I'm uploading a fix right now."
1671509,2017-03-09 21:33:01 UTC,Updated packages for keystone and nova have been uploaded to zesty and will work their way back to the ocata cloud archive.
1671509,2017-03-09 22:35:55 UTC,This bug was fixed in the package nova - 2:15.0.0-0ubuntu1.1
1671509,2017-03-09 22:35:59 UTC,This bug was fixed in the package keystone - 2:11.0.0-0ubuntu1.1
1671509,2020-06-18 08:47:09 UTC,"Given that these went fix-committed three years ago, I'm marking the Cloud Archive task as fix-released as well"
1671520,2017-03-09 18:31:01 UTC,"This bug made me realize that if you delete a machine or device from MAAS, it will show back up in the list of discoveries. The UI only shows things that MAAS does not know about. (And the API I mentioned, too.)"
1671520,2017-03-09 17:36:50 UTC,Does the UI work the same way? Either way I think this is really wierd. Discoveries should only be for machines MAAS does not know about. I was under the impression that is how it worked.
1671520,2019-09-19 12:03:02 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1671520,2017-03-09 15:34:03 UTC,"I think it's actually useful that MAAS ""discover"" things that it manages. It's like double-entry accounting that, yes, the machine is using the IP and MAC we thought it would use."
1671520,2017-03-09 16:39:38 UTC,Forgot to note: I think it would be good to clear discoveries matching something that gets deleted from MAAS.
1671524,2017-03-09 16:32:30 UTC,"Currently our devstack configuration uses the in-process task workers, so orders are processed synchronously instead of using the message queue for asynchronous processing."
1671524,2017-03-10 10:04:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444190"
1671524,2017-05-16 01:26:13 UTC,"Change abandoned by Nam Nguyen Hoai (<email address hidden>) on branch: master
Review: https://review.openstack.org/444190"
1671526,2017-03-13 02:20:52 UTC,"Addressed by: https://review.openstack.org/#/c/443753/
https://review.openstack.org/#/c/444062/"
1671526,2017-04-20 10:02:41 UTC,This issue was fixed in the openstack/kolla-ansible 4.0.1 release.
1671526,2017-06-09 15:32:54 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.
1671528,2017-03-27 14:10:56 UTC,Updating the Kernel seem to have fixed the issue. More than a week has been tested and no freeze happened.
1671528,2017-03-13 12:36:02 UTC,I just installed the latest upstream kernel but since I cannot reproduce this issue manually I need some time (1-5 days) of full testing in order to update this bug report.
1671528,2017-03-09 19:46:28 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1671528,2017-03-09 16:00:12 UTC,This change was made by a bot.
1671536,2017-03-09 16:12:52 UTC,"This is strange.  I just booted an older image and then installed a
kernel:"
1671540,2017-11-21 04:58:28 UTC,"After upgrading to 17.10 I haven't had this problem. Since this is a Gnome based software version, maybe the problem was in Unity."
1671540,2017-10-21 19:40:38 UTC,Latest:
1671540,2017-10-10 19:56:16 UTC,"On 17.04 I have a very similar problem.  The Software Updater icon in the Unity launch bar has turned green to indicate that updates are available.  When I click on that icon it gains an orange ""halo"" indicating that the system knows that it has been selected, but no window opens.  I cannot manually start the Software Updater.  I have to reboot in order to run the Software Updater.  xwininfo knows the window is there but nobody else does.  I have had this problem for over a month and I would really appreciate some guidance."
1671540,2017-08-19 18:16:37 UTC,Latest:
1671540,2017-07-18 03:08:46 UTC,Latest:
1671540,2017-07-06 21:08:56 UTC,Latest:
1671540,2017-07-02 19:03:18 UTC,Latest:
1671540,2017-06-24 22:40:40 UTC,Another occurrence:
1671540,2017-06-17 19:23:25 UTC,Another occurrence:
1671540,2017-06-05 00:05:58 UTC,Sorry comment 11 should refer to comment 10.
1671540,2017-05-27 03:55:34 UTC,File: 20170526-softupd.log
1671540,2017-06-05 00:03:50 UTC,See attachment 20170604-softupd-bad.log for full log.
1671540,2017-06-05 00:05:00 UTC,Log referenced by comment #9
1671540,2017-03-10 16:58:10 UTC,What??
1671540,2017-03-22 15:44:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671540,2017-03-22 15:52:48 UTC,"Software Uodate window disappears frequently in my system too. I'm running Ubuntu 16.04.02, Unit-7.4.0 in Zbook-G3 laptop with Nvidia-372.13 binary driver. No matter what you the icon only occasionally flickes in the menu, but no window appears."
1671540,2017-05-27 03:49:54 UTC,"I'm using this script to collect info. I'll post the results in the next message. It makes to files, a before and after calling wmctrl so they can be diff'ed easily"
1671540,2017-03-22 16:01:07 UTC,Or this: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/925260
1671540,2017-05-25 05:23:25 UTC,"Happens to me at least 4 out of 5 times.
Ubuntu 17.04
System76 Meerkat"
1671540,2017-03-22 15:58:01 UTC,Might be related to this: https://bugs.launchpad.net/xenial-backports/+bug/1003950
1671544,2017-03-09 16:34:43 UTC,"On Thu, Mar 9, 2017 at 10:18 AM, Mike Pontillo <email address hidden>
wrote:"
1671544,2017-03-09 17:07:13 UTC,"On Thu, Mar 9, 2017 at 10:48 AM, Mike Pontillo <email address hidden>
wrote:"
1671544,2017-03-10 09:14:28 UTC,"OK, thanks."
1671544,2017-03-09 16:48:17 UTC,Thanks for the reply.
1671549,2017-03-09 18:18:59 UTC,See musings in Dmitry's etherpad: https://etherpad.openstack.org/p/ironic-driver-properties-reform
1671549,2017-04-19 16:40:11 UTC,Set the importance to wishlist as per our rfe process. I'm +1 on this.
1671549,2017-05-23 16:40:54 UTC,wrt the tags; sorry -- was looking at the wrong rfe :-(
1671549,2017-06-06 00:27:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/471174"
1671562,2017-03-24 14:47:30 UTC,"Hmm... that might be it, I have a 1680x1050 monitor right now.  It's actually ridiculous that they would change it like that, considering it worked fine before (at least for me)."
1671562,2017-03-09 17:07:11 UTC,"Oh, full screen resize (dragging to top of monitor) does still work."
1671562,2017-03-24 07:27:04 UTC,"Hello,"
1671562,2017-03-24 07:31:54 UTC,"I mean, not twice 910, but 1366/2 = 683 < 910"
1671565,2018-02-07 08:20:25 UTC,"Change abandoned by Joachim Barheine (<email address hidden>) on branch: master
Review: https://review.openstack.org/444754"
1671565,2017-03-10 18:12:51 UTC,"Now I found also the second reason and could provide a fix: the update-alarm-definition events contained """" instead of the ID of the changed sub-alarm. The thus could not find the sub-alarm to update."
1671565,2017-03-09 17:14:49 UTC,"After looking at the event queue in Kafka, a first explanation is that the alarm-definition-update messages are invalid. Instead of the actual metric dimensions, a single element dimension set {'uname': 'notification'} is reported in the metricDefinition."
1671571,2017-03-09 17:35:21 UTC,https://pastebin.ubuntu.com/24147089/
1671571,2017-03-10 01:49:10 UTC,Related to bug 1656727?
1671571,2017-03-10 01:55:39 UTC,I can't seem to reproduce the crash. Unity8 keeps running.
1671571,2017-03-10 08:15:41 UTC,"@dinamic, do you get a .crash file? Could you please share it somewhere?"
1671571,2017-03-10 08:26:53 UTC,hmm.. the newest sol crash i can find is this https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1669798
1671571,2017-03-10 08:29:08 UTC,so it does look like bug https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1656727
1671571,2017-05-10 04:17:27 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1671586,2017-03-09 18:00:35 UTC,"StacktraceTop:
 ?? ()
 XInternAtom (dpy=dpy@entry=0x5605705076f0, name=name@entry=0x7f0c67e9f2d0 ""ConnectorType"", onlyIfExists=onlyIfExists@entry=0) at ../../src/IntAtom.c:174
 gsd_rr_screen_initable_init (initable=<optimized out>, canc=<optimized out>, error=0x7ffec0078c08) at gsd-rr.c:735
 g_initable_new_valist () from /tmp/apport_sandbox_HFuq07/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_initable_new () from /tmp/apport_sandbox_HFuq07/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0"
1671609,2017-06-01 10:08:34 UTC,"Hi Jared,"
1671610,2017-03-31 13:35:47 UTC,"This is still not working in the latest release.  And it actually seems to be worse.  I can never get an x app surface to get ""True"" returned once it looses focus.  isSurfaceFocused just keeps returning false even when it's focused."
1671611,2017-03-09 23:39:32 UTC,apport information
1671611,2017-03-09 23:39:33 UTC,apport information
1671611,2017-03-09 23:39:35 UTC,apport information
1671611,2017-03-09 23:39:38 UTC,apport information
1671611,2017-03-09 23:39:39 UTC,apport information
1671611,2017-03-09 23:43:36 UTC,I stand corrected... 4.4.0-63 was the first one in update manager to have this issue
1671611,2017-03-09 23:50:37 UTC,screenshot of stack trace that remained on screen.
1671611,2017-03-09 23:39:27 UTC,apport information
1671611,2017-04-19 18:33:18 UTC,"So with that rtl8192 dongle, it crashes/freezes/locks up?
See bug #1666421 , this is a possible duplicate."
1671611,2017-04-20 16:07:58 UTC,"I have this problem in Xubuntu 17.04 i386 and amd64 versions, in fresh install and live usb too, with my 2 different dongles (a rtl8187b and a Buffalo Nintendo WiFi). I tested the i386 iso on 2 computers (one of them is a 64 bit capable laptop). Ethernet and integrated rtl8188ce wifi adapter are working.
nm-applet and nmcli show the APs but fail at connecting to them.
No freeze while trying to connect to an AP."
1671611,2017-04-28 10:12:01 UTC,I subscribed to this bug and clicked the 'Yes this bug affects me' before. But with the kernel version 4.4.0-75-generic (with Ubunut 16.04 LTS) I no longer have this bug.
1671611,2017-03-09 23:39:31 UTC,apport information
1671611,2017-05-04 04:06:06 UTC,^- LinuxMint 18.1 w/ 4.4.0-75
1671611,2017-05-06 16:43:34 UTC,"At the time of my last comment (2017-04-20), it was already working well in Xubuntu 16.04, it is still not working in Xubuntu 17.04, i have to use wicd instead for the moment."
1671611,2017-03-10 22:42:37 UTC,"I also have this problem. At first when I trying connect to wi-fi it seems fine, after reconnecting it's suddenly unable connected to network."
1671611,2017-05-04 04:05:31 UTC,I second Bazz's statement. All is working normally again.
1671611,2017-03-09 23:39:26 UTC,apport information
1671611,2017-03-09 23:09:51 UTC,kernel 4.4.0-66-generic does have this issue
1671611,2017-03-09 19:49:41 UTC,also worth mentioning - my RJ-45->USB dongle does not suffer this problem and neither does mobile phone -> laptop USB tethering.
1671611,2017-03-09 22:58:35 UTC,No longer think this is a network-manager issue. On a fresh install I changed over to kernel 4.8.0-41 but did not perform any other updates and had the same issue. If I boot with the default 4.4.0-53 kernel I do not have this issue.
1671611,2017-03-09 23:07:47 UTC,don't know how to capture a kernel crash / stack trace so i'm typing based on what my phone camera captured as it scrolled by...
1671611,2017-03-09 23:39:29 UTC,apport information
1671611,2017-03-09 23:27:13 UTC,4.4.0-64-generic does have this issue. So it would seem whatever the problem is was introduced with 4.4.0-66.generic
1671611,2017-03-09 23:39:11 UTC,apport information
1671611,2017-03-09 23:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1671611,2017-03-09 23:39:16 UTC,apport information
1671611,2017-03-09 23:39:18 UTC,apport information
1671611,2017-03-09 23:39:20 UTC,apport information
1671611,2017-03-09 23:39:22 UTC,apport information
1671611,2017-03-09 23:39:23 UTC,apport information
1671611,2017-03-09 23:39:25 UTC,apport information
1671611,2017-03-09 23:39:13 UTC,apport information
1671636,2019-09-12 18:33:33 UTC,"Reviewed:  https://review.opendev.org/680567
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=bcaf9fd149e36c437b65220de64a7a195301a337
Submitter: Zuul
Branch:    master"
1671636,2017-06-09 09:38:32 UTC,"Hi, I went through the code and I see that it logs for every attempt in sending DNS message(be it notify or SOA). Based on the description I assume that logs shouldn't happen for SOA. Am I correct?"
1671636,2017-11-25 06:43:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522915"
1671636,2019-09-06 03:59:09 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680567"
1671636,2019-09-27 09:35:03 UTC,This issue was fixed in the openstack/designate 9.0.0.0rc1 release candidate.
1671652,2019-03-26 17:27:30 UTC,"This has been enabled for LVM here https://review.openstack.org/#/c/444479/. The bug report is more generic, need to revisit if we actually want to extend this to other drivers."
1671652,2019-03-22 16:12:35 UTC,Hey Victoria any update on this? Any help or assistance on this one let us know :)
1671652,2020-03-12 16:02:46 UTC,Additional comments http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-03-12-15.01.log.html
1671667,2017-06-09 15:35:01 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1671667,2017-06-04 16:04:32 UTC,"Reviewed:  https://review.openstack.org/465018
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=85cdb0b89494963615d542b7bbf86bc905539cf9
Submitter: Jenkins
Branch:    master"
1671667,2017-05-16 10:16:03 UTC,Releases fix https://review.openstack.org/#/c/393386/
1671667,2017-05-16 10:17:01 UTC,"Sorry, previous change does not fix the issue, will work on it"
1671677,2020-11-08 09:17:15 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1671677,2020-11-09 17:34:49 UTC,"I don't use this setup anymore so I don't know if it's still an issue, it would have been nice if someone had responded to my report when I filed it over 3 years ago. Go ahead and close it."
1671677,2020-11-10 03:19:15 UTC,"Thanks for your answer, and sorry that nobody replied to your original report - sometimes there is just no expert around, or nobody has a clue about the right answer... anyway, let's close this ticket now."
1671680,2019-01-30 02:56:15 UTC,I've subscribed field-medium here.
1671680,2017-10-06 09:25:22 UTC,"After investigation, solution does not really require creating CA."
1671680,2017-09-26 03:36:13 UTC,"What I had to do in this instance, though I didn't test your approach:"
1671680,2019-01-11 22:09:35 UTC,"I concur that Nobuto's approach is best.  I've been struggling with any other method of making this relation work and what I've found is that relating landscape-client to landscape-server:registration is that if you have landscape-server in HA mode, the registration code pins you to one of the landscape-servers and half of them work great and half die on the vine."
1671680,2017-09-25 05:05:40 UTC,Note that according to https://help.landscape.canonical.com/LDS/SSL we CANNOT use a self signed cert - we have to use a self signed CA and then make a cert from that.  The charm does none of this and so when we want to make a fresh environment we wind up ditching the cert created by the charm.
1671680,2017-04-05 07:11:50 UTC,"Totally agree. In fact I already started working on this, so expect some patches soon."
1671680,2017-09-25 08:02:03 UTC,"@Xav,"
1671684,2017-03-10 09:10:36 UTC,"Change abandoned by Zhenyu Zheng (<email address hidden>) on branch: master
Review: https://review.openstack.org/444137"
1671684,2017-03-28 07:22:26 UTC,"Reviewed:  https://review.openstack.org/444068
Committed: https://git.openstack.org/cgit/openstack/python-searchlightclient/commit/?id=dd523b7d5c5dda356ac30ff98099a9f6f26d9ea8
Submitter: Jenkins
Branch:    master"
1671684,2017-07-27 07:49:25 UTC,This issue was fixed in the openstack/python-searchlightclient 1.2.0 release.
1671688,2017-03-10 03:36:29 UTC,Looks like it came from here:
1671688,2017-11-03 16:36:44 UTC,Syncing task from Mir.
1671691,2018-02-07 13:06:08 UTC,Workaround:
1671691,2018-02-07 13:49:17 UTC,"I was requested to add this attachment to the bug report. This dialog box appears when opening an older Inkscape .svg file in Inkscape 0.92.2. Regarding my issue, I selected the default option which reads ""This file contains artwork for screen display. (Choose if unsure.)""."
1671691,2018-02-07 13:10:40 UTC,Also happens for documents created with inches as unit.
1671691,2017-12-07 01:54:33 UTC,"The 'viewbox' option is not available in the 92.2 dialog.  Win 7, X64."
1671691,2019-07-16 15:27:46 UTC,"I seem to have the same problem, and it is quite annoying. I currently have 0.92.4 installed:"
1671691,2017-05-03 17:11:08 UTC,"UPDATE:
tl;dr - If you select the 'viewBox' option when opening a pre-0.92 drawing then the issue of inability to adjust display units does not present itself."
1671691,2017-05-03 16:14:44 UTC,Regarding old Inkscape documents (pre 0.92) that cannot properly set display units:
1671691,2017-04-01 13:46:38 UTC,"Problem occurred after upgrading from .91 to 0.92.1r1573. When loading old (0.91) files rulers now stuck in units of px. When I change properties to inch it changes back to px on file save. SVG file shows units of inches. New drawings are OK.
O/S is windows 10 64bit Anniversary"
1671691,2017-03-10 11:10:18 UTC,This is the same as #1671059
1671691,2017-09-01 15:54:17 UTC,I have the same issue in 0.92 on Xubuntu 16.04
1671703,2017-03-24 04:16:43 UTC,"Hi Frode,
Thank you your comment."
1671703,2017-03-23 08:59:26 UTC,"Actually, if you update your cinder_dev.yaml to contain 'release: mitaka' and not 'release: stable/mitaka' this will work as it should. branch: should still be 'stable/mitaka'"
1671703,2017-03-23 08:51:51 UTC,"os_release in charm-helpers return the wrong value when deploying from Git:
2017-03-23 08:48:01 INFO juju-log [cinder] DEBUG: os_release >= ocata: 'True' os_release = 'stable/mitaka'"
1671703,2017-03-16 18:36:11 UTC,"Hi Yuki,"
1671703,2017-03-16 08:37:22 UTC,Thank you for your bug report.
1671703,2017-03-23 00:52:08 UTC,"Hi Corey and Frode.
Thank you for your reply."
1671707,2017-03-10 06:26:43 UTC,Setting nagios_hostname_type to host and back to unit is a workaround.
1671707,2017-06-02 03:23:29 UTC,Potential fix released to candidate channel as cs:~nrpe-charmers/nrpe-14
1671709,2017-03-10 11:04:11 UTC,"Legacy router will also be scheduled on interface adding, so I assume same issue applies to legacy routers as well. I believe the test should be updated to first list agents of the router and then do remove/add based on this info."
1671713,2017-03-16 01:27:22 UTC,"@Pradeep Kumar Singh, good catch. You reproduced it finally."
1671713,2017-03-16 04:03:06 UTC,"@Shunli,"
1671713,2017-03-16 08:45:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446358"
1671713,2017-03-15 17:18:55 UTC,I am concerned about below case exception
1671713,2017-03-10 08:45:29 UTC,"@shunliz,"
1671713,2017-03-13 01:18:59 UTC,"@Pradeep, @hongbin, it's good to see there are a BPs to cover my concern.Let's discuss at the meeting to find out how to implement the status sync and in which BP is better."
1671713,2017-03-12 05:18:50 UTC,"I registered a BP for periodically task: https://blueprints.launchpad.net/zun/+spec/periodic-task , but I don't think periodical task can completely resolve the problem. I think what Pradeep suggested might directly fix this problem."
1671713,2017-03-10 06:42:09 UTC,"I prefer to log a blueprint to add a periodic task to sync the container status from docker to db.
Any suggestion?"
1671713,2017-03-15 06:44:45 UTC,Reinstall the devstack and cannot reproduce this bug. Mark as invalid.
1671718,2018-05-08 18:03:50 UTC,This change was made by a bot.
1671718,2021-01-07 04:11:53 UTC,4.8 EOL
1671719,2017-03-10 08:18:53 UTC,"When considering the phone, we didn't need to ""completely"" hide no indicators, only not show some in the default list."
1671720,2017-03-21 01:05:30 UTC,"As this is a tech-debt item, I am lowering its Importance."
1671720,2017-03-21 03:32:48 UTC,This would have revealed issues that caused numerous outages (some more than a day long!) on production systems. Is it really low priority?
1671720,2017-03-21 04:55:09 UTC,"No, it's not low priority if it affected production. The only indication of it's severity I had was it was tagged as ""tech-debt"". Consider tagging it as ""canonical-is"", please!"
1671726,2018-01-02 18:30:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671731,2017-03-21 01:46:30 UTC,I spent a little time on this bug last week.
1671731,2017-03-10 08:20:40 UTC,"Sorry, wrong bug..."
1671731,2017-03-21 00:31:46 UTC,This is simple to reproduce.  The application has disappeared from the screen but continues to run.
1671733,2019-05-09 02:49:14 UTC,"Actually, I am seeing the same behavior with 'remove-machine --force'.. At least from the command line, when the removal is forced, the machine on the model with provisioner-harvest-mode=none is untouched on the cloud but is terminated when its model is destroyed. I'll dig into model destruction exclusively."
1671733,2020-03-12 03:10:04 UTC,"Due to current priorities, I am not currently working on this bug, so I am un-assigning myself from it."
1671733,2019-05-09 04:51:08 UTC,"The same would apply to if a controller has models with harvest mode set to leave cloud instances alone. When Juju destroys it, harvest mode will not be respected... Need to fix this too."
1671733,2019-05-09 03:19:17 UTC,"I think the problem is that the models cloud machines are terminated by the undertaker when a model is destroyed, not a provisioner unlike in remove-machine case. And the undertaker is not harvest-mode savvy."
1671733,2019-05-09 00:48:10 UTC,"After some discussions, we'll keep the model destruction to always force remove non-manual machines - there is no benefit in going through a normal, lengthy removal if we are destroying a model anyway. However, we will ensure that force removing a machine respects harvest mode."
1671733,2019-05-07 04:14:47 UTC,"Unfortunately, with 2.6 this is still the case. I'll add it to 2.6.1 milestone."
1671733,2017-03-16 19:45:35 UTC,"Yes, that or just remove it from the database altogether."
1671733,2019-05-08 23:51:01 UTC,This is a very interesting case and is highlighting a few issues with the implementation.
1671733,2017-03-14 12:07:12 UTC,"On Mon, Mar 13, 2017 at 10:00:45PM -0000, Anastasia wrote:

> I am removing this from ""juju-core"" as we do not track Juju 2.x bugs
> there. Also, this is not a bug but is an intended behavior. So, I am
> marking this as Invalid for ""juju"" in agreement with comment # 1.
"
1671733,2017-03-14 09:09:10 UTC,"Anastasia, thank you for removing juju-core from the bug. Adding that was my mistake."
1671733,2017-03-13 23:51:37 UTC,"I'm not as sure. If ""juju remove-machine"" really does leave the machine
running, then I would expect ""juju destroy-model"" to not touch the machine."
1671733,2017-03-13 22:00:45 UTC,"I am removing this from ""juju-core"" as we do not track Juju 2.x bugs there. Also, this is not a bug but is an intended behavior. So, I am marking this as Invalid for ""juju"" in agreement with comment # 1."
1671733,2017-03-10 21:38:57 UTC,"Hi John,"
1671733,2017-03-10 17:00:21 UTC,"The lifetimes of machines deployed by Juju are intentionally tied to the
lifetime of the model. We don't support identifying already running
machines which means that those machines would just become orphaned and it
would not be possible to control them under Juju again."
1671733,2017-03-16 16:29:57 UTC,I have a feeling that implementation wise we need to remove whatever tag on the machine that indicates it is in the model which is evaluated during model tearsown.
1671739,2017-03-15 11:01:47 UTC,"Reviewed:  https://review.openstack.org/444154
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=a290e83d63888bb4ade7364f9234feef2aa3d4d7
Submitter: Jenkins
Branch:    master"
1671739,2017-06-09 15:32:52 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.
1671744,2017-03-10 10:04:36 UTC,"Added a nicer workaround:
https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=c1a41c3e2fca342bb77ccf204d54051303d15e73"
1671744,2017-03-10 10:11:03 UTC,Blocked on bug 1671771 now.
1671746,2017-03-10 09:05:30 UTC,"just so i don't open another bug report, it also has a strange behaviour when you have lots of pinned apps but you do the other way arround, scroll down until you reach to the last icon, then open the menu, then scroll up, the menu gest broken along the way and then it just jumps from the buttom of the screen up to the first icon under the ubuntu logo"
1671749,2017-04-22 16:46:35 UTC,Fixed by: https://review.openstack.org/#/c/450043/
1671749,2017-03-13 02:54:28 UTC,"Hi Kevin,
    The image is builded by myself.
    ""zun attach"" needs special images?
    I will pull a image from dockerhub and try it first."
1671749,2017-03-25 16:39:58 UTC,"I can somehow reproduced this bug. It looks the option ""--os-project-name"" works for other commands (i.e. list, show), but doesn't work for attach since the attach command doesn't read this option. I will take care of this bug."
1671749,2017-04-24 13:27:48 UTC,This issue was fixed in the openstack/python-zunclient 0.2.0 release.
1671749,2017-03-20 03:37:44 UTC,"@Feng,
   Sorry I just see your comment.
   I will check now"
1671749,2017-03-13 02:36:41 UTC,"Hi Feng,
   What's your image name?
   Could you use a normal image, such as ubuntu to reproduce the error?"
1671749,2017-03-13 09:45:10 UTC,"@Hi Feng,
    zun attach doesn't need a special images. Just attach with websocket client. You can try an image from dockerhub  first.
    If confirmed, I will try to figure out the problem."
1671749,2017-03-13 02:50:29 UTC,"Hi Kevin,"
1671749,2017-03-14 05:39:24 UTC,"@Kevin,
I use a ubuntu image to create a container. But I still get this problem."
1671751,2017-03-13 13:22:38 UTC,Likely that an update enabled wifi power management.  In terminal enter
1671753,2017-03-10 09:30:11 UTC,This change was made by a bot.
1671753,2017-07-26 15:49:58 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1671755,2018-11-06 21:20:15 UTC,https://code.launchpad.net/~mcuelenaere/duplicity/duplicity/+merge/358411 should fix this issue.
1671755,2017-03-13 14:53:54 UTC,"Yes, that should reduce the sigtar volsize."
1671755,2017-03-13 06:49:10 UTC,I tried first solution.
1671755,2017-03-11 13:43:50 UTC,"You've hit this bug:
https://bugs.launchpad.net/duplicity/+bug/385495https://bugs.launchpad.net/duplicity/+bug/385495"
1671755,2017-03-10 13:03:05 UTC,"What version of duplicity?  What OS and version?  Please rerun with -v9 and paste the log as an attachment to this bug report.  If it's too long, please paste the first 200 lines and the last 200 lines."
1671755,2017-03-11 11:43:11 UTC,"Good day Kenneth,"
1671756,2018-08-08 04:57:49 UTC,We don't need to fix this in MAAS until we start sending the v2 (netplan) YAML. We already have a fix for this in the v1 YAML.
1671756,2019-09-19 11:56:07 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1671761,2017-03-10 12:59:59 UTC,"Another collateral issue related with this, seems to be that in the old version, when you were doing a Broadcast All, the broadcast was only for the terminals in the current instance (or window), now affects to all the instances you have open."
1671761,2017-03-10 12:56:30 UTC,"I have seen that in a previous version there were different process for each instance, while with the new version there is only one process for all the instances, and the instances seems to be threads. I think that unless it is done on purpose, the problem is that is counting all the terminals as belonging to only one instance."
1671761,2017-03-10 17:19:19 UTC,"As per the other broadcast use case, this can temporarily be worked around by disabling the DBus in the preferences. You lose some things as a result (higher resource usage, no remotinator, no other application can make DBus calls to Terminator). It is fair to say that at some point I'm going to have to do some kind of reworking to make some of the features work a bit better with the DBus active."
1671764,2017-04-10 15:21:18 UTC,"Agreed about SSL, I said ""allow unrestricted and unencrypted"" in the bug report which covers that."
1671764,2017-04-10 14:59:14 UTC,wouldn't it also have to be exposed without SSL as well as without username + password? I would think the weirdest part of the setup is grabbing the Certificate so that prometheus doesn't complain about 'self-signed certificate' or 'unknown-certificate-authority' issues.
1671771,2017-11-03 15:24:44 UTC,Syncing task from Mir.
1671778,2019-10-15 12:05:23 UTC,This bug was reported against the internal snapd test suite over two years ago. I'm closing it as WONTFIX although similarly to another report about internal test suite it might as well be FIX RELEASED since those tests gate each release now.
1671781,2017-08-09 21:43:19 UTC,Same spam can be found in nova-conductor logs
1671789,2017-03-10 11:33:35 UTC,"File: Source SVG object without grouping, printing OK (in white)."
1671789,2017-03-10 11:34:41 UTC,File: Inkscape converted PDF in my PC (bug).
1671789,2017-03-10 11:35:03 UTC,File: Inkscape converted PDF in my PC (printing OK).
1671790,2017-03-27 18:22:46 UTC,"It seems to work in some of the windows but not in these: RSS Feed, Auto search, Finished uploads, Search, Search spy, User list, File list.
It is called autoscrolling in Firefox https://www.youtube.com/watch?v=6_8tbkfrHRQ"
1671793,2017-03-16 08:41:33 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/446357"
1671793,2017-04-05 16:20:46 UTC,"Verified for 10.0 #1512.
Latest runs are passed, problem is fixed.
https://ci.fuel-infra.org/job/10.0-community.main.ubuntu.bvt_2/1398/"
1671793,2017-03-23 10:52:35 UTC,"Please check this, it looks it is also subject for this bug: https://ci.fuel-infra.org/job/11.0-community.main.ubuntu.bvt_2/580/"
1671793,2017-03-14 12:39:29 UTC,"The same for F10:
https://build.opnfv.org/ci/job/fuel-deploy-baremetal-daily-master/1960/console"
1671793,2017-03-14 04:02:51 UTC,"I found how to sync changes:
fuel2 graph upload -r {releaseID} -t provision -f /etc/fuel/graphs/provision/tasks.yaml
or, for enviroment:
fuel2 graph upload -e {envID} -t provision -f /etc/fuel/graphs/provision/tasks.yaml"
1671793,2017-03-15 13:49:32 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445962"
1671793,2017-03-13 11:15:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444826"
1671793,2017-03-16 08:52:07 UTC,"Reviewed:  https://review.openstack.org/444826
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=12e9b93a9d123f56c1500714fd97bdd35cf4bca0
Submitter: Jenkins
Branch:    master"
1671793,2017-03-16 08:52:57 UTC,"Reviewed:  https://review.openstack.org/445962
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=74acfc23f3bd69f93903fe257eb6c43bcbc2167d
Submitter: Jenkins
Branch:    stable/newton"
1671793,2017-03-13 16:12:56 UTC,"Hello, I have the same problem.
I already try to change timeout in graphs/provision/tasks.yaml, but I can`t find how to sync this changes.
For plugins I usualy use ""fuel2 plugins sync"". But it not work for graph/provision."
1671793,2017-03-23 08:52:44 UTC,"Reviewed:  https://review.openstack.org/446357
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=f4eda96d45469a42b3cc2f69466ef24eae0f4008
Submitter: Jenkins
Branch:    stable/ocata"
1671793,2017-03-22 11:04:41 UTC,"It looks that this bug also affects 10.0 community build BVT:
https://ci.fuel-infra.org/job/10.0-community.main.ubuntu.bvt_2/1337/"
1671802,2018-02-25 07:53:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671804,2017-03-17 10:42:49 UTC,"Change abandoned by Ivan Udovichenko <email address hidden> on branch: 9.0/mitaka
Review: https://review.fuel-infra.org/32263
Reason: Wrong branch."
1671804,2017-03-17 10:49:27 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32323"
1671804,2017-03-17 15:37:07 UTC,"Reviewed: https://review.fuel-infra.org/32323
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1671804,2017-03-17 16:08:49 UTC,"By merging the above fix we assured that openvswitch-switch service is running before Neutron agent.
But during the test I've faced issues:
http://paste.openstack.org/raw/603134/"
1671804,2017-03-17 16:09:06 UTC,MOS Neutron team could you please take a look?
1671804,2017-03-15 13:16:13 UTC,"Ivan, could you take a look please?
Seems like neutron-openvswitch-agent's systemd unit hasn't openvswitch-switch dependency in the 'After' section.
Perhaps, script which generates unit from sysv init script doing it in the wrong way."
1671804,2017-03-20 14:34:50 UTC,"After conversation with Oleg the fix was found. These values should be set in the configuration file during deployment:
[agent]
root_helper_daemon = sudo /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf
root_helper = sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
In [agent] section.
And then restart the service."
1671804,2017-03-15 16:02:21 UTC,"Related fix proposed to branch: 9.0/mitaka
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32263"
1671804,2017-03-20 11:48:47 UTC,"In the diff http://paste.openstack.org/raw/603161/ you can see the last line says: ""run_as_root=True"" which should eventually prefix the command with rootwrap helper or daemon."
1671808,2017-03-15 13:08:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445946"
1671808,2017-03-21 12:58:03 UTC,"Reviewed:  https://review.openstack.org/445946
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=d38e1a399cb0793690781d95f688ce7061f9072d
Submitter: Jenkins
Branch:    master"
1671808,2017-03-21 13:32:20 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/448093"
1671808,2017-03-29 09:01:23 UTC,"Reviewed:  https://review.openstack.org/448093
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=d1136773baeb8fd81370fb547e3bd6d0a95e7185
Submitter: Jenkins
Branch:    stable/newton"
1671808,2017-05-05 06:54:55 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/462833"
1671808,2019-12-18 16:47:52 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/462833
Reason: This repo is retired now, no further work will get merged."
1671810,2020-01-28 07:37:53 UTC,"This was fixed already in July 2017:
https://git.launchpad.net/nagios-charm/commit/?id=92c692dcf02fa75e79cf67c54969c1654f1ffbf6"
1671812,2017-07-07 12:51:52 UTC,I believe this has been fixed in https://git.launchpad.net/nrpe-charm/commit/?id=00cf472fb45b8f23e6e49956c1b7709d9b692e5e
1671819,2019-03-06 23:14:35 UTC,confirmed on https://packages.debian.org/sid/wicd-daemon
1671819,2017-12-30 00:43:58 UTC,Same on Debian9 with Edgerouter X handling DHCP and DNS...
1671834,2017-03-10 14:50:23 UTC,"so right now, it searches for the application's name and keywords (from the .desktop file) to contain the search string... This seems to make sense to me..."
1671834,2017-03-10 15:01:01 UTC,I suppose we could prioritize the results that *begin* with the search string.
1671834,2017-03-10 15:35:24 UTC,"also if i search for a substring it doesn't seem to find anything, search ""imple"""
1671834,2017-03-13 02:16:18 UTC,"It appears that we match word prefixes only (which is arguably a good choice): ""ath"" does not find ""LibreOffice Math"", but ""math"" does. However there are some cases where U8's implementation is annoying."
1671838,2017-03-10 15:21:47 UTC,"This seems to happen with window-manager marco but not with openbox, for example."
1671838,2017-03-10 16:41:10 UTC,I did some tests on Ubuntu 16.04:
1671840,2017-03-13 09:46:22 UTC,You shouls update package building spec (package version must match latest git tag)
1671840,2017-03-13 10:33:03 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32183"
1671840,2017-03-14 13:25:54 UTC,"Reviewed: https://review.fuel-infra.org/32183
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1671844,2019-05-02 09:43:52 UTC,"When I looked, it was possible. But it seems that I was looking at on old version of MAAS, that we still using YUI."
1671844,2019-04-30 14:37:35 UTC,The wireframes have a button to save the name of an api key. Is this possible? and if so how?
1671844,2019-04-17 09:47:21 UTC,Sorry - misnamed the wireframes! Here are some updated ones: https://zpl.io/aNm0J1N
1671844,2019-04-16 10:47:24 UTC,Proposed design to add comment field: https://zpl.io/aNm0J1N
1671844,2019-04-17 09:26:27 UTC,"To clarify, this is about the API keys, and they have names, not comments. This is not about the SSH keys."
1671844,2019-04-17 09:33:39 UTC,"FWIW, this is NOT about the comment in the SSH key field. This is about the
*name* of the API KEY."
1671844,2017-03-10 15:14:08 UTC,"Hi Sandor,"
1671844,2019-04-16 10:29:26 UTC,I can't see any evidence of comments relating to SSH keys in the data supplied through the websocket or in the python handler. How can this be exposed to the UI?
1671844,2019-04-17 08:42:42 UTC,The comment is always the last part of public key. The websocket returns a short version of the public key separated by a ; with for the comment. The comment may be cropped see [1]
1671845,2017-03-10 15:14:11 UTC,"A total of 17 error / warning messages are generated by yaz-marcdump when attempting to parse the two records in the above scenario, and the errors appear to begin AFTER the first occurrence of a character such as é or ©."
1671845,2017-03-13 16:21:39 UTC,Confirmed same symptoms with a set of sample records loaded with --load-all-sample
1671845,2017-03-13 16:32:36 UTC,Attaching lp1671845.tar.gz containing sample marc_export output for comparison.
1671845,2018-11-16 15:32:28 UTC,"Hello, I just ran into this issue."
1671847,2017-03-15 11:15:36 UTC,This issue was fixed in the openstack/nova 15.0.1 release.
1671847,2017-03-13 12:58:23 UTC,"Reviewed:  https://review.openstack.org/444357
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=abd18a12e3e6b571d35499857a005a7bfd7237a4
Submitter: Jenkins
Branch:    master"
1671847,2017-04-14 09:23:07 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1671847,2017-03-10 15:41:52 UTC,"Change abandoned by Ionuț Bîru (<email address hidden>) on branch: master
Review: https://review.openstack.org/444350"
1671847,2017-03-10 15:41:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444357"
1671847,2017-03-10 15:25:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444350"
1671847,2017-03-10 15:18:38 UTC,"Yeah we confirmed that the code is setting deprecated_group='default' which doesn't error but doesn't do the passthrough for DEFAULT. This is a bug on a few options that were moved between groups in ocata, so we should fix all of them in the same patch."
1671847,2017-03-10 15:59:31 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/444374"
1671847,2017-03-14 19:41:30 UTC,"Reviewed:  https://review.openstack.org/444374
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=59123a18767567438d8388730750f9c8eb377d1f
Submitter: Jenkins
Branch:    stable/ocata"
1671849,2017-03-10 16:51:54 UTC,"The delay doesn't seem to be due to Mir, but because GTK+ tries to D-Bus activate the accessibility bus, and waits for it to timeout."
1671850,2017-03-19 07:24:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671850,2017-12-17 02:27:12 UTC,Still a problem in artful release.
1671853,2017-03-13 08:20:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671853,2017-03-23 07:53:55 UTC,"""Backporting"" the QDesktopWidget::screenNumber(QWidget*) function from qtbase HEAD helped for this particular problem. Packages with an extra patch (debian/patches/multiscreen-MET.diff) are available on launchpad: ppa:met-norway/updates-met"
1671856,2018-01-25 21:22:36 UTC,"Hi everyone, I am going hope that I am not causing anybody heartburn by chiming in again. :) We have had another help ticket today from a library director regarding the understandable misinterpretation caused by account adjustments being calculated as payments and displayed in the Total Paid column in the patron account. On the main billing screen, it appears to staff that these are payments made by the patron unless they take the time to go to the Full Details screen for each and every line item, see whether account adjustment is the payment type, and understand what that means (the patron hasn't paid that amount). I am wondering if, in the discussion of the laudable intent of account adjustments, whether there is room to discuss an alternate option, such as displaying account adjustments in their own separate column? Perhaps it would even make sense to calculate Forgive, Goods, and Work ""payments"" in the Adjustments column, as those also cause staff to think patrons have paid something when no money has actually changed hands."
1671856,2018-02-07 17:19:28 UTC,Just popping in for a belated Thanks Dan for the reply to my questions.
1671856,2018-01-29 15:38:09 UTC,"Hi All,"
1671856,2018-01-26 15:20:39 UTC,"Thanks, Dan, and I am sorry for the heartburn. I wish you much coding success. Anything you are able to achieve that allows staff to easily distinguish non-monetary offsets/adjustments from monetary payments (actually made by patrons) will be a huge UX win!"
1671856,2018-01-26 14:37:26 UTC,"April, thank you for chiming in again.  It does cause me a little heartburn to see this come up again, but I deserve it :)"
1671856,2017-11-29 16:46:22 UTC,"These automated voids still seem to be functioning in addition to the account adjustment feature, which means that patrons are credited too much when fines are voided in addition to the account adjustments for a double credit, causing an incorrect reduced amount owed or a negative balance on the patron account. The account adjustments have the addition drawback of being mischaracterized as payments."
1671856,2017-08-04 18:02:05 UTC,"I wanted to bring attention back to this bug to see if we can reach a decision on Bill's proposal. Although our libraries are all using the Prohibit Negative Balance settings, I can see where libraries that continue to use voiding would want the behavior to be consistent whenever a fine or fee is removed. With that in mind, I support the idea behind Bill's proposed change."
1671856,2017-03-10 16:01:45 UTC,Code for option #1 above:
1671856,2017-12-13 19:51:53 UTC,"Quoting Bill:
""1. Back-dated checkin overdues are voided.
2. Claims-returned overdues are adjusted.
3. Amnesty checkin overdues are voided.
4. Mark-Lost overdues are adjusted."
1671856,2017-03-10 16:24:15 UTC,"Thanks Bill! I like providing a more consistent experience for staff. I think #1 is the path that probably would cause the least disruption at this point, even though I was in favor of #2 way back when the new code was first introduced as it provides a consistent experience across all libraries, no matter how they adjusted their negative balance settings."
1671856,2017-03-13 20:36:10 UTC,"Thanks, Dan!  I'm not exactly sure how to answer your undo question.  My concern for now is only that when an overdue fine needs to be, er, disabled by the system, sometimes it's voided, sometimes it's adjusted."
1671856,2017-03-13 18:24:47 UTC,"I remain open-minded about it, but at this point would not want see this behavior reverted.  The goal has always been for adjustments and voids to usefully coexist (now and into the future), and our library successfully uses both even though it *does* allow negative balances / refunds.  If an ""adjustment"" better models what we are doing when we make these overdues ""go away"", then the issue isn't really with the underlying structures, so reverting this doesn't really address the problem."
1671856,2017-06-16 13:41:03 UTC,"Adding my comments here and in bug 1593815 to say that Bill's argument seems sound to me that the behavior for all the different ""void"" scenarios should be consistent, either always use void or always use account adjustment."
1671858,2018-01-17 07:38:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671865,2017-12-04 21:52:23 UTC,"Update to use lp:~thedac/mongodb
https://review.openstack.org/520836"
1671877,2020-04-11 10:14:58 UTC,"Hi, I've created a follow-up issue that deals with the unreasonably high values created using this feature: https://gitlab.com/inkscape/inbox/-/issues/2280. Your patch works fine, thanks again, the behavior is now identical with all units."
1671877,2017-04-17 13:32:13 UTC,"Mc, the corrections are available at `lp:~eman-mod/inkscape/inkscape` branch under revision 12625. Also you can see them at http://bazaar.launchpad.net/~eman-mod/inkscape/inkscape/revision/15625"
1671877,2020-04-11 10:13:39 UTC,"I've created a follow-up issue on Gitlab, which deals with the unreasonably high values that are created by this feature, see https://gitlab.com/inkscape/inbox/-/issues/2280. Thanks for your patch, it works fine! The behavior is now identical with all units."
1671877,2017-04-15 12:01:08 UTC,"pushed to r15622, thanks for the fix!"
1671877,2017-03-11 06:00:43 UTC,"In the new patch, line 16, the expression
    newval = current * (std::exp(std::log(max_f-1) * (by+1)) - 1) / (max_f-2);"
1671877,2017-03-10 19:33:49 UTC,"Patch updated. In 'gesture', exponential function for stroke width is more smooth and natural than mixture of linear and quadratic. Also I decided to increase the multiplication factor to 50x."
1671877,2017-04-16 06:46:04 UTC,"Thank you very much, Mc!"
1671885,2017-03-10 17:25:33 UTC,"StacktraceTop:
 __GI___libc_free (mem=0x3fb0101010101010) at malloc.c:2963
 zeitgeist_symbol_info_register () from /tmp/apport_sandbox_lYIZks/usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0
 zeitgeist_symbol_initialize_symbols () from /tmp/apport_sandbox_lYIZks/usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0
 zeitgeist_symbol_get_all_children () from /tmp/apport_sandbox_lYIZks/usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0
 zeitgeist_db_reader_get_where_clause_for_symbol () from /tmp/apport_sandbox_lYIZks/usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0"
1671885,2017-04-04 14:59:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671885,2017-03-13 20:48:03 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1671887,2017-03-30 08:22:13 UTC,"Reviewed:  https://review.openstack.org/447573
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b4cef3de502cd13cf44b7fc005003d7297706990
Submitter: Jenkins
Branch:    master"
1671887,2017-03-30 05:42:46 UTC,"Reviewed:  https://review.openstack.org/448615
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=14ff6e467ec0701da2800edd423d42d226020745
Submitter: Jenkins
Branch:    master"
1671887,2017-03-30 06:26:56 UTC,"Reviewed:  https://review.openstack.org/447564
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5da9d11e46d5e75b11b3c3cda25ce72f23eb798c
Submitter: Jenkins
Branch:    master"
1671887,2018-09-13 03:02:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/602216"
1671887,2018-09-19 20:40:20 UTC,"Reviewed:  https://review.openstack.org/602216
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4b2c4566977b1d810daa4a002a93058353f8b190
Submitter: Zuul
Branch:    master"
1671887,2017-03-30 05:40:49 UTC,"Reviewed:  https://review.openstack.org/448613
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=259d4d4179f708969c200e00729b4b15e741ed73
Submitter: Jenkins
Branch:    master"
1671887,2017-08-02 20:20:58 UTC,Automatically unassigning due to inactivity.
1671887,2017-03-29 17:02:39 UTC,"Reviewed:  https://review.openstack.org/448192
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=07966bbee4e2e3062303c7fa25510e43ab091490
Submitter: Jenkins
Branch:    master"
1671887,2017-04-10 20:50:58 UTC,"Reviewed:  https://review.openstack.org/451452
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5323ee7802e4913f1bcac9e3d77d45a1734dd690
Submitter: Jenkins
Branch:    master"
1671887,2017-03-29 17:01:31 UTC,"Reviewed:  https://review.openstack.org/447562
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6ed141a57cb75a3b22f8b47809203e6cae09da10
Submitter: Jenkins
Branch:    master"
1671887,2017-03-10 17:22:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444424"
1671887,2017-03-20 15:54:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447562"
1671887,2017-03-20 15:57:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447564"
1671887,2017-03-20 16:07:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447573"
1671887,2017-03-29 17:02:30 UTC,"Reviewed:  https://review.openstack.org/448186
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=890b1d43251302e7ad65a1c2171d76a67dff01f0
Submitter: Jenkins
Branch:    master"
1671887,2017-03-22 21:07:27 UTC,"Reviewed:  https://review.openstack.org/447549
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9f8e412e49e469c84d098cd012e1e6f62c4a2f17
Submitter: Jenkins
Branch:    master"
1671887,2017-03-23 14:28:25 UTC,"Reviewed:  https://review.openstack.org/444424
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=939881b77fa1ad8546101dc5b8aed126e0127179
Submitter: Jenkins
Branch:    master"
1671887,2017-03-29 15:13:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/451452"
1671887,2017-03-22 14:47:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448615"
1671901,2017-03-10 18:25:26 UTC,"StacktraceTop:
 scm_internal_hash_fold (fn=0x7f8cd8d48680 <collect_keys>, closure=0x0, init=0x304, table=0x92f0e0) at hashtab.c:1435
 scm_c_port_for_each (proc=0x7f8cd8d48a88 <flush_output_port>, data=0x0) at ports.c:974
 scm_flush_all_ports () at ports.c:1110
 really_cleanup_for_exit (unused=0x0) at init.c:362
 c_body (d=0x7fff48d06f10) at continuations.c:517"
1671909,2017-03-10 19:42:25 UTC,Upgrade PackageKit to 1.1.5-2 - does that fix this issue?
1671909,2017-03-10 20:06:03 UTC,"PackageKit isn't installed at all, not by default."
1671916,2017-06-14 11:18:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671916,2017-04-28 15:26:45 UTC,In the meantime I upgraded to Ubuntu 17.04. Fusion-icon seems to be the same version and still exhibits the same problem.
1671916,2017-06-14 11:19:49 UTC,"I am using Xubuntu 17.04. fusion-icon does not start and shows the following:
 * Detected Session: xubuntu
 * Searching for installed applications...
compizconfig - Error: Unable to find interface type 2 on 0x7f3b3b5474e8
This is either a programmer error or more than one static library
defining this interface has been linked in
Unable to continue, please file a bug about this
Aborted (core dumped)"
1671922,2017-04-21 00:10:14 UTC,This problem still exists in 17.04.
1671922,2017-04-21 01:48:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671922,2017-06-29 21:05:12 UTC,"OK, I dug into this a bit.  I added the line"
1671922,2017-06-29 23:00:04 UTC,This might be related to http://git.net/ml/general/2016-09/msg13810.html
1671922,2017-06-30 00:20:52 UTC,"Tied that last link to the Debian bug, linked above.  That includes a patch, or since apticron seems to have fixed this in 1.1.59, 1.1.61 (which is in artful) could be backported."
1671926,2017-05-10 14:23:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671926,2019-05-14 13:09:13 UTC,I submitted a bug report and patch upstream to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928980
1671929,2019-11-08 20:18:35 UTC,This was fixed:
1671929,2018-05-16 12:39:45 UTC,"This looks pretty much complete.  i.e. reading the docs at https://jujucharms.com/openstack-base/ seems to show all the steps.  The only thing that might be missing is that there is no ""explicit"" mention to download the zip file to get the novarc_auto."
1671929,2017-03-11 09:35:25 UTC,"Hi James,"
1671929,2018-02-07 18:16:17 UTC,https://github.com/openstack-charmers/openstack-bundles/pull/54
1671929,2017-03-12 04:43:32 UTC,"Hello,"
1671929,2017-03-10 21:18:28 UTC,I posted a response on your askubuntu question - we'll also look to make that a bit clearer in the README as well.
1671929,2018-02-07 18:16:43 UTC,"Sorry, ignore comment #4, wrong bug."
1671930,2017-03-13 07:25:17 UTC,"Thanks for noticing this. Actually, that shebang wasn't really needed at all. I just removed it."
1671930,2017-03-13 09:27:44 UTC,"Hello,"
1671931,2017-03-10 22:03:41 UTC,Please reply and copy/paste the device list (pactl list...) and Gstreamer-pipeline here.
1671931,2017-03-12 04:01:41 UTC,"pactl list | grep -A3 'Source #'Source #0
State: IDLE
Name: alsa_output.pci-0000_00_01.1.hdmi-surround.monitor
Description: Monitor of Built-in Audio Digital Surround 5.1 (HDMI)
--
Source #1
State: SUSPENDED
Name: alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo
Description: USBTV007 Video Grabber [EasyCAP] Analog Stereo
--
Source #2
State: SUSPENDED
Name: alsa_output.pci-0000_00_14.2.analog-stereo.monitor
Description: Monitor of Built-in Audio Analog Stereo
--
Source #3
State: SUSPENDED
Name: alsa_input.pci-0000_00_14.2.analog-stereo
Description: Built-in Audio Analog Stereo"
1671931,2017-03-10 21:50:17 UTC,"Hello,
Would you like to test the recording in a terminal window (command line).
It is easy to do."
1671931,2017-03-12 11:12:34 UTC,"Sorry for double posting, but I am repeating the last reply without the `*`s."
1671931,2017-03-12 08:23:54 UTC,"Hello,
Very good. Now you have the recording command. Let us test  it in a
terminal window (command line)."
1671931,2017-03-12 08:34:31 UTC,"Looks like the commands are surrounded by a *.
Please remove the * (from beginning and tail) before testing the commands."
1671931,2017-03-12 04:03:17 UTC,"gst-launch-1.0  -e pulsesrc
device=alsa_input.pci-0000_00_12.2-usb-0_3.analog-stereo ! queue !
audioresample ! audioconvert ! audio/x-raw,rate=44100,channels=2 !
lamemp3enc name=enc target=0 quality=2 ! xingmux ! id3mux ! filesink
location=test.mp3"
1671931,2017-03-12 08:37:55 UTC,"Launchpad.net also added some ** the other recording pipeline with the ""volume"" element. Please check the command carefully. Take an original copy from the audio-recorder program (as you did earlier)."
1671933,2020-03-24 14:40:19 UTC,"The tests were passing 100% times over the last 3 months:
http://status.openstack.org/openstack-health/#/test/tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_attach_detach_volume?duration=P3M
http://status.openstack.org/openstack-health/#/test/tempest.api.volume.test_volumes_actions.VolumesActionsTest.test_attach_detach_volume_to_instance?duration=P3M"
1671945,2017-07-26 17:01:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671947,2019-05-17 13:29:46 UTC,On a Swedish keyboard (with an English installation of Inkscape 0.92 on Windows10) I cannot get a clone with Alt+D but I can get a clone with Ctrl+d (no Shift to make the d into D) Is this a keyboard issue (bug) or a typo in the menu?
1671947,2019-06-10 13:59:51 UTC,"I can't get a clone with ALT+d or ALT+D.
Using windows 10 and Inkscape 0.92.4 (5da689c313, 2019-01-14)
Very slow to use clones with no hotkeys.
Been like this for a few releases now."
1671947,2017-04-30 15:33:20 UTC,"@Michael - Could you please confirm your issue is a duplicate of one of the bugs listed comment #2?
Thanks!"
1671947,2017-03-10 23:58:01 UTC,"Depending on currently opened dialogs docked in the main window, or current interface language, likely a duplicate of one of these earlier reports:"
1671947,2017-03-10 22:19:33 UTC,Just updated to current build (Inkscape 0.92.1 r15371) and the bug us still there.
1671947,2017-04-30 20:53:09 UTC,I am using US English and I didn't have the Export dialog docked or undocked.
1671947,2017-05-01 15:07:16 UTC,"Thanks for the details, Michael!"
1671949,2017-03-14 22:47:54 UTC,"In addition to documentation, python-swiftclient should probably expose the pool_connections option (and the max_pool_size) of the HTTPAdapter used by default in requests (http://docs.python-requests.org/en/master/user/advanced/)."
1671949,2017-11-28 17:27:04 UTC,swiftclient should replace all its custom HTTPConnection by the keystoneauth1 session object.
1671951,2019-10-28 16:43:47 UTC,"@Balint, after further testing, here's where things are:"
1671951,2019-11-01 13:30:52 UTC,"I have not tested first boot, @raharper could you please test that?"
1671951,2019-11-01 13:30:06 UTC,"@ddstreet You systemd builds in the PPA fix the issue for me on Bionic and Disco, IPv6 MTU is applied after reboot with the configuration."
1671951,2019-10-31 19:25:38 UTC,In my test I modified a multipass launched VM's netplan config to:
1671951,2019-10-31 08:21:39 UTC,"> cloud-init is not doing anything special here, we render the config and call netplan generate
"
1671951,2019-10-30 21:20:38 UTC,"@Dan,"
1671951,2019-10-30 21:08:27 UTC,"@raharper could you give the systemd in this ppa a test:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd"
1671951,2019-10-10 02:41:46 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.31
1671951,2019-10-25 17:23:21 UTC,"Thanks. Let's put both tasks as Triaged again then, since it's obviously not fixed in disco and bionic."
1671951,2019-10-24 18:54:20 UTC,"In the Eoan version of systemd, I can see in the logs these messages:"
1671951,2019-10-24 18:52:03 UTC,"I did some more testing today.  I upgraded systemd and netplan.io to disco level, rebooted and tested the MTU  settings; disco packages fail as well.  I then upgraded to eoan systemd/netplan.io rebooted and the MTU settings are correct."
1671951,2019-10-23 21:44:55 UTC,"The original netplan yaml I was testing was simpler, but also failed so I tried to see if additional settings would make a difference, but it did not."
1671951,2019-10-23 21:33:34 UTC,I cannot verify this is working on bionic with ipv6 static addresses.
1671951,2019-11-01 14:27:12 UTC,"Testing with @ddstreet's systemd ppa, I can confirm that bionic, disco and eoan correctly set MTU on first boot, no systemd-restart needed."
1671951,2019-10-25 18:34:29 UTC,"On Fri, Oct 25, 2019 at 1:31 PM Dan Streetman <email address hidden>
wrote:"
1671951,2019-11-01 15:32:01 UTC,"I opened this upstream
https://github.com/systemd/systemd/pull/13915"
1671951,2020-02-05 14:33:39 UTC,Curtin vmtest verification for eoan using systemd from -proposed has run successfully.
1671951,2020-01-23 16:26:02 UTC,This bug was fixed in the package systemd - 244.1-0ubuntu2
1671951,2020-07-13 16:27:32 UTC,I'm trying to understand if there is any work still required on this bug for cloud-init.  I've tested two network configurations (in lxd containers).  The first:
1671951,2020-02-17 10:07:54 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.39
1671951,2020-02-17 09:35:40 UTC,This bug was fixed in the package systemd - 242-7ubuntu3.7
1671951,2020-02-07 22:30:42 UTC,"Verified Eoan systemd 242-7ubuntu3.7 correctly sets IPv6 MTU
Verified Bionic systemd 237-3ubuntu10.39 correctly sets IPv6 MTU"
1671951,2020-02-07 07:06:28 UTC,"All autopkgtests for the newly accepted systemd (242-7ubuntu3.7) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1671951,2020-02-07 04:59:41 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.39) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1671951,2020-02-06 21:46:16 UTC,"Hello Ryan, or anyone else affected,"
1671951,2020-01-14 13:06:00 UTC,"as disco is EOL next week, marking this won't fix for disco."
1671951,2020-02-06 21:42:10 UTC,"Hello Ryan, or anyone else affected,"
1671951,2020-02-05 16:29:38 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.38
1671951,2019-10-02 21:55:29 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1671951,2020-02-05 14:30:42 UTC,Curtin vmtest verification for bionic using systemd from -proposed has run successfully.
1671951,2020-02-04 05:48:11 UTC,"All autopkgtests for the newly accepted systemd (242-7ubuntu3.3) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1671951,2020-02-04 05:31:58 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.34) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1671951,2020-02-03 21:52:53 UTC,"Hello Ryan, or anyone else affected,"
1671951,2020-02-03 21:40:51 UTC,"Hello Ryan, or anyone else affected,"
1671951,2020-02-06 15:22:59 UTC,"This SRU needs to be reuploaded, due to security update that trumped this in progress SRU."
1671951,2019-10-02 21:55:08 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1~18.04.1
1671951,2019-10-28 10:50:26 UTC,"@raharper, do I understand correctly that this occurs only on first boot and is fixed when installing eoan's netplan.io on bionic?
Also a full Disco systemd works or not? (Disco system, Disco netplan.io, Disco systemd)"
1671951,2019-10-02 17:58:50 UTC,Verification-done on disco:
1671951,2018-09-28 14:28:25 UTC,Actually there needs to be changes to netplan to emit the correct IPV6BytesMtu setting to networkd; and then cloud-init can emit the correct netplan yaml for that.  This feature is on the netplan roadmap here:
1671951,2018-09-28 14:16:03 UTC,"This may now be a cloud-init bug if the support is there since this is
a network-config v1 -> cloud-init  renders netplan.
On Fri, Sep 28, 2018 at 9:12 AM Scott Moser <email address hidden> wrote:

>
> Hm...
>
> Our tests show that this is not fixed in cosmic or bionic.
>
> https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/533/console
> shows curtin's vmtest failing.  Partial output shows:
>
> ======================================================================
> ERROR: test_ipv6_mtu_smaller_than_ipv4_v6_iface_first (vmtests.test_network_mtu.CosmicTestNetworkMtu)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File ""/var/lib/jenkins/slaves/torkoal/workspace/curtin-vmtest-devel-amd64/curtin-533/tests/vmtests/__init__.py"", line 468, in wrapper
>     raise RuntimeError(msg)
> RuntimeError: skip_by_date(CosmicTestNetworkMtu.test_ipv6_mtu_smaller_than_ipv4_v6_iface_first) LP: #1671951 fixby=2018-09-26 removeby=2018-10-17: (PAST_FIXBY) Failed: 1480 != 1500
> -------------------- >> begin captured stdout << ---------------------
> iface=interface4 subnets=[{'address': '2001:4800:78ff:1b:be76:4eff:fe06:5000', 'netmask': 64, 'type': 'static', 'mtu': 1480}, {'address': '192.168.5.2/24', 'type': 'static', 'mtu': 1501}]
> subnet:{'address': '2001:4800:78ff:1b:be76:4eff:fe06:5000', 'netmask': 64, 'type': 'static', 'mtu': 1480}
> mtu_data:{'device': 1500, 'ipv6': 1500}
> subnet_mtu=1480 ipv6_mtu=1500
>
> --------------------- >> end captured stdout << ----------------------
>
>
> ** Attachment added: ""console log of curtin vmtest amd64 533""
>    https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/5194078/+files/curtin-vmtest-devel-amd64-533-console.log
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671951
>
> Title:
>   networkd should allow configuring IPV6 MTU
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+subscriptions
"
1671951,2018-09-28 13:59:17 UTC,Hm...
1671951,2018-08-29 14:28:23 UTC,"On Wed, Aug 29, 2018 at 8:41 AM Dimitri John Ledkov
<email address hidden> wrote:

>
> Do we need this in bionic?
"
1671951,2018-08-29 13:33:53 UTC,Do we need this in bionic?
1671951,2018-08-29 13:33:34 UTC,This is now in cosmic.
1671951,2018-06-25 16:17:00 UTC,The v239 merge for cosmic is in progress at the moment. There are a few regressions that need to be worked around.
1671951,2018-11-19 14:03:01 UTC,"Hello Ryan, or anyone else affected,"
1671951,2018-06-25 15:16:13 UTC,I've just seen that upstream systemd v239 claims to support IPV6MtuBytes
1671951,2017-05-17 18:36:53 UTC,"On Wed, May 17, 2017 at 1:14 PM, Dimitri John Ledkov <<email address hidden>

> wrote:
"
1671951,2017-05-17 18:14:29 UTC,"I'm very naive, so please bear with me if this is a silly question. As far as I can tell the existing MTU setting in networkd will apply to both ipv4 and ipv6 simultaniously. Are you arguing that you want specific control of MTU and use different values for ipv4 and ipv6? Would it not be sufficient to set the appropriatly-lowest/highest common denominator value for MTU?"
1671951,2017-03-28 14:16:17 UTC,This also needs some discussion w.r.t how to handle IPV6-only devices; namely if you want to set the IPV6 MTU to something higher than the underlying device's current setting then the device MTU would need to be raised as well.  That needs to be implemented and added to the patch.
1671951,2017-03-28 12:44:34 UTC,Please submit this as a pullrequest upstream.
1671951,2017-03-11 00:29:56 UTC,"The attachment ""ipv6_mtu.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1671951,2017-03-10 22:11:30 UTC,I've a build of this fix here:
1671951,2019-10-02 21:54:51 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1~19.04.1
1671951,2017-08-09 18:12:33 UTC,Unsubscribing sponsors based upon IRC discussion with rharper:
1671951,2018-11-20 12:05:18 UTC,"Hello Ryan, or anyone else affected,"
1671951,2019-10-25 18:20:19 UTC,"I looked at this for a few minutes, and it seems strange that it works at all (at boot) since networkd sets the ipv6 mtu before bringing the link up, but the kernel resets the ipv6 mtu to the device mtu on link up.  I must be missing something."
1671951,2018-11-27 05:03:33 UTC,Regarding #2 from comment #19:
1671951,2019-10-01 02:59:52 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1671951,2019-09-30 21:32:39 UTC,"Hello Ryan, or anyone else affected,"
1671951,2019-09-30 20:32:47 UTC,"Hello Ryan, or anyone else affected,"
1671951,2019-08-28 17:01:51 UTC,"err, on Eoan, I used ipv6-mtu 6000."
1671951,2019-08-28 17:01:24 UTC,See comment #20;  ipv6 mtu is 1280 -> DEVICE_MTU.
1671951,2019-08-28 16:28:49 UTC,I thought custom ipv6 MTU may not be lower than ipv4 one.
1671951,2019-08-28 16:18:47 UTC,"I tested with your single-file approach and that also fails.  Note that bionic now has systemd 237, so maybe something is missing (or regressed) ?"
1671951,2019-10-02 16:24:36 UTC,Verification-done on bionic:
1671951,2019-08-28 16:05:25 UTC,"Followup on my comments, are any changes required in networkd to support this in bionic?"
1671951,2019-08-27 22:47:49 UTC,"Hello Ryan, or anyone else affected,"
1671951,2019-08-22 01:13:47 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1
1671951,2018-12-04 17:31:31 UTC,"This was done inside a VM.
This was all done in a single /etc/systemd/network/10-netplan-ens3.network file. Note that [Link] is a valid section in a .network file. Note that i took netplan generated .network file as a base, and then modified it with above shown options. Disabled netplan. Rebooted."
1671951,2018-12-04 17:22:37 UTC,"On Tue, Dec 4, 2018 at 9:31 AM Ryan Harper <email address hidden>
wrote:"
1671951,2018-12-04 15:31:18 UTC,"On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov <email address hidden>
wrote:"
1671951,2018-12-04 12:16:32 UTC,Using systemd 237-3ubuntu10.10
1671951,2018-11-27 16:44:33 UTC,"On Mon, Nov 26, 2018 at 11:11 PM Jay Vosburgh
<email address hidden> wrote:

>
> Regarding #2 from comment #19:
>
> As the defined range for the ipv6.mtu is from IPV6_MIN_MTU to the
> device's MTU, and the existing API returns an error if the ipv6.mtu is
> out of range, I think it's reasonable for a configuration with the
> ipv6.mtu > device MTU to fail.
"
1671951,2019-08-28 14:34:40 UTC,"I launched a bionic image on serverstack, updated the netplan.io to proposed, modified the network config to set ipv6-mtu to 6000 and rebooted."
1671951,2018-11-26 19:22:52 UTC,It seems there are some limitations to what systemd will do with IPv6BytesMTU.
1671953,2017-07-27 20:58:33 UTC,"I got the code for the wingpanel-indicator-bluetooth from GitHub to see if I could fix it, but it appears it is already fixed."
1671954,2017-04-03 13:57:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671954,2017-04-03 22:06:51 UTC,"The fix was just applied to sdl mainline:
https://hg.libsdl.org/SDL/rev/f931db466859
Would be very nice if ubuntu can take this
up as this is a real show-stopper for the
full-screen apps."
1671954,2017-04-04 01:26:40 UTC,"https://bugzilla-attachments.libsdl.org/attachment.cgi?id=1715 does not fix the issue I reported. I still can't get full screen mode to work properly. Normally I still get the large scrolling virtual desktop issue, and with SDL_VIDEO_X11_XRANDR=0 set in the environment things are even worse."
1671954,2017-04-04 08:47:40 UTC,"OK, sorry then.
I just have the same problem and didn't want
to create a duplicate ticket...
Will do now."
1671954,2018-02-28 07:50:21 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1671954,2018-03-01 22:22:25 UTC,"Marking as Invalid because the release is EOL is not correct. Marking as Incomplete. Also, 18.04 is (at the time of writing) still in development, and you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29"
1671954,2017-03-11 01:23:16 UTC,"SDL 2 is able to go back to the proper desktop resolution when exiting full screen if and only if the top left corner of the current viewport is at the top left of the displayed area. In other words, if I don't scroll the viewport right or down by going to those edges with the mouse, or if I scroll it and then scroll back to the left and top limits, only then do I go back to the proper resolution in desktop mode."
1671954,2017-04-03 13:15:24 UTC,"Fullscreen switching in sdl2 is currently broken:
https://bugzilla.libsdl.org/show_bug.cgi?id=1859
This ticket has the patch that fixes it:
https://bugzilla-attachments.libsdl.org/attachment.cgi?id=1715
I tested the patch and it works for me.
Would be nice if ubuntu can apply it, as
it seems sdl devs are ignoring the bugzilla
completely."
1671960,2017-03-11 17:00:35 UTC,If the change in structure is due to a file being dropped or pasted into the view this is due to the intended behaviour that such files are selected (at the expense of any existing selection).  I believe there was a bug requesting this.
1671974,2019-02-12 13:37:38 UTC,"I have just found the following message in syslog:
Feb 12 13:25:56 samsung5-ubuntu colord-sane: message repeated 2 times: [ [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address]
that matches:
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled)
   Active: active (running) since Tue 2019-02-12 02:30:41 CET; 11h ago
 Main PID: 2098 (colord)
    Tasks: 3 (limit: 4915)
   Memory: 14.9M
   CGroup: /system.slice/colord.service
           └─2098 /usr/lib/colord/colord"
1671974,2019-02-12 12:41:47 UTC,I ha
1671974,2019-02-07 03:42:57 UTC,See if you have any *cups* packages installed
1671974,2019-02-07 00:48:14 UTC,"If anyone knows a way to pinpoint some process which sends some specific packets, I'd be glad to investigate further."
1671974,2019-02-07 00:41:15 UTC,"I experience the same symptoms on Ubuntu 19.04 disco, but there is no cups* packages installed:"
1671974,2018-06-14 01:17:55 UTC,"Still seeing CUPS related IPv6 multicast requests from my machine on 18.04 bionic, right after plugging in a USB device:
[11593.578868] usb 2-1.1: new high-speed USB device number 4 using ehci-pci
[11593.693173] usb 2-1.1: New USB device found, idVendor=0e8d, idProduct=1807
[11593.693182] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11593.693187] usb 2-1.1: Product: MT1807
[11593.693192] usb 2-1.1: Manufacturer: MediaTek Inc
[11593.693196] usb 2-1.1: SerialNumber:
[11594.085831] usb-storage 2-1.1:1.0: USB Mass Storage device detected
[11594.086113] scsi host6: usb-storage 2-1.1:1.0
[11594.086272] usbcore: registered new interface driver usb-storage
[11594.257746] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=<Ubuntu machine IPv6> DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=659619 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[11594.257765] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=<Ubuntu machine IPv6> DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=952340 PROTO=UDP SPT=8612 DPT=8610 LEN=24
[11594.268122] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=<Ubuntu machine IPv6> DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=659619 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[11594.268197] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=<Ubuntu machine IPv6> DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=952340 PROTO=UDP SPT=8612 DPT=8610 LEN=24"
1671974,2019-02-02 02:41:31 UTC,I also see the IPv6 requests when a USB device is plugged in.  In this case it is a Z-Wave device.  I don't have any cannon stuff.  I'm running 18.04.1 LTS.
1671974,2017-09-11 01:40:25 UTC,Please check with a live system (or on a virtual machine) Artful (Ubuntu 17.10) to check whether the problem is not present any more there.
1671974,2017-11-27 04:17:49 UTC,[Expired for cups (Ubuntu) because there has been no activity for 60 days.]
1671974,2017-08-04 20:06:59 UTC,"cups-browsed does not directly interact with USB printers and is not triggered by USB events. Do you have any special software to support Canon printers (Canon MFNP, Canon BJNP) installed? Does this software mirror USB printers to emulated network printers? Does it do this mirroring also if no supported printer is present?"
1671974,2017-08-04 20:29:27 UTC,"Do you have the cups-bjnp package installed? It provides the ""bjnp"" CUPS backend to use Canon BJNP network printers (not USB printers). It communicates with the printer on port 8611 in both directions."
1671974,2017-08-04 07:41:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1671974,2017-08-07 21:05:01 UTC,"cups-browsed does for sure not send anything to the given ports, and it also does not directly send anything to the multicast addresses. It communicates with avahi-daemon via D-Bus to get informed about network printers appearing or disappearing, updates its internal printer list accordingly and creates CUPS queues or removes them, communicating with CUPS via localhost:631 (using the IPP protocol) or domain socket. It also subscribes to CUPS notifications via D-Bus."
1671974,2017-08-09 03:42:21 UTC,"Understood.
Judging by some other reports such as https://discussions.apple.com/thread/6477200, it sounds like this is an upstream behaviour in the core CUPS that may have since been fixed (I'm testing with newer versions to see if I can reproduce)."
1671974,2017-09-08 21:15:49 UTC,Moving this bug under cups package.
1671974,2017-08-06 17:56:09 UTC,"cups-browsed conf attached.
I do not have a /var/log/cups/cups-browsed_log"
1671976,2017-03-13 20:49:00 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1671976,2020-08-09 23:09:26 UTC,grafana 2.5.0
1671991,2017-03-29 03:15:51 UTC,"Debian stretch has the opposite issue: there, rescue only works if no desktop session is active. Otherwise, whether systemctl is run from within that session or not, the console is left completely unusable; not even Ctrl+Alt+Del works."
1671991,2017-03-11 05:58:46 UTC,"Oops, I ran ubuntu-bug on 'init' instead of '/bin/init'. If I need to redo it to get more detailed logs, please let me know and I will."
1671999,2017-06-19 16:14:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672003,2017-03-11 08:52:26 UTC,"StacktraceTop:
 XQueryPointer (dpy=0x560e13ea0fc0, w=1276, root=root@entry=0x7ffd9688a0b0, child=child@entry=0x7ffd9688a0b8, root_x=root_x@entry=0x7ffd9688a094, root_y=root_y@entry=0x7ffd9688a098, win_x=0x7ffd9688a09c, win_y=0x7ffd9688a0a0, mask=0x7ffd9688a0a4) at ../../src/QuPntr.c:42
 X11SalFrame::Init (this=this@entry=0x560e1b242f50, nSalFrameStyle=nSalFrameStyle@entry=NONE, nXScreen=..., pParentData=pParentData@entry=0x0, bUseGeometry=bUseGeometry@entry=false) at ./vcl/unx/generic/window/salframe.cxx:513
 X11SalFrame::X11SalFrame (this=0x560e1b242f50, pParent=<optimized out>, nSalFrameStyle=NONE, pSystemParent=0x0) at ./vcl/unx/generic/window/salframe.cxx:829
 KDESalFrame::KDESalFrame (this=0x560e1b242f50, pParent=<optimized out>, nState=<optimized out>) at ./vcl/unx/kde4/KDESalFrame.cxx:52
 KDESalInstance::CreateFrame (this=<optimized out>, pParent=0x0, nState=NONE) at ./vcl/unx/kde4/KDESalInstance.cxx:42"
1672010,2017-03-30 23:38:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672012,2017-07-18 05:41:02 UTC,Is the client crashing? See bug 1668466
1672012,2017-07-18 08:11:40 UTC,"Actually, I seem to be seeing a new bug: lp:1704949"
1672012,2017-10-31 12:02:00 UTC,"We'll never see a fix in Unity8, so we'll never know if it also requires any change to Mir."
1672012,2017-07-18 05:15:44 UTC,I can now see something like this with miral-shell:
1672012,2017-03-20 17:55:11 UTC,Don't know what's different in my system but here vlc won't launch. I can launch firefox though which displays the same bug (menus immediately disappearing) but it doesn't cause unity8 to crash.
1672012,2017-03-13 02:37:13 UTC,Alan recently said this was either fixed already (bug 1656727) or not relevant to U8 (bug 1668466). See also older bug 1497128.
1672012,2017-03-13 02:39:02 UTC,"dinamic: That ""debug spam"" has a fix on the way; bug 1664151."
1672012,2017-03-14 05:37:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672012,2017-03-14 09:43:41 UTC,"Another /possible/ cause of ""'std::out_of_range' what(): map::at]"" is bug 1667645. That would imply that vlc is crashing and the server dies in closing the session."
1672012,2017-03-14 10:09:50 UTC,It would be good to get a log with MIR_SERVER_WINDOW_MANAGEMENT_TRACE=on as that ought to log the operation that propagates the exception.
1672012,2017-03-14 10:19:31 UTC,"MIR_SERVER_WINDOW_MANAGEMENT_TRACE shows that miral-shell doesn't provoke ""'std::out_of_range' what(): map::at]"" - but that doesn't explain the failure to exit. We either have two problems or two symptoms of one underlying issue."
1672012,2017-03-14 10:23:31 UTC,"Finally, mir_demo_server doesn't crash and exits successfully. (The menus don't display correctly, they disappear as soon as they get focus. But that's another issue.)"
1672012,2017-03-15 11:08:13 UTC,"I've split off the miral-shell ""hang on exit"" as lp:1673038  since it looks entirely separate to the Unity8 crash."
1672012,2017-03-11 10:07:50 UTC,from unity8.log (it's pretty hard to read the log :( too much debug spam)
1672012,2017-03-15 11:32:01 UTC,"It *is* also possible to crash miral-shell this way - after numerous runs where it ""merely"" hung on exit I have a crash."
1672012,2017-03-15 12:26:18 UTC,"Correction to #14 - the miral-shell crash (and the hang on exit) seems to be entirely down to racy decorations code. Both the ""tiling"" window manage and miral-kiosk are entirely stable."
1672013,2017-03-11 11:43:21 UTC,"Trying to proceed with the installation on the same machine and settings using ""ubuntu-16.04-desktop-amd64.iso"" and that one works correctly."
1672013,2017-03-18 21:51:02 UTC,Tested again with zesty-desktop-amd64.iso from 2017-03-16. The same problem with btrfs installation.
1672018,2017-03-11 10:40:54 UTC,"Ubuntu 16.04, 0.8.1-0extras16.04.1"
1672018,2017-03-13 12:17:21 UTC,"It seems that the data from Yahoo comes with a big delay and changes only a few times a day. Although the Yahoo site is updated much more often.
Also, when you select Yahoo, there is no weather status icon (an icon with a question mark is displayed)."
1672024,2017-03-11 11:10:20 UTC,"StacktraceTop:
 require () at ./src/include/common/mir/require.h:28
 (anonymous namespace)::mir_window_request_persistent_id_helper(MirSurface*, void (*)(MirSurface*, MirPersistentId*, void*), void*) [clone .lto_priv.662] (window=0x7f4e780b6fd0, callback=callback@entry=0x7f4e84af47d0 <assign_surface_id_result>, context=context@entry=0x7ffd582145a0) at ./src/client/mir_surface_api.cpp:538
 mir_surface_request_persistent_id_sync (surface=<optimized out>) at ./src/client/mir_surface_api.cpp:1267
 ?? ()
 ?? ()"
1672024,2017-04-05 09:10:44 UTC,https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=2f797f2d42106c81860b106475b6d095c0ba3d08
1672024,2017-03-15 02:37:17 UTC,It's this one:
1672027,2017-09-24 15:14:01 UTC,"Same issue, Kubuntu 17.04"
1672033,2017-03-22 07:12:45 UTC,"The following line is a bit suspicious

>Mär 21 20:10:20 arvlin /usr/lib/gdm3/gdm-x-session[3618]: (II) systemd-logind: releasing fd for 226:0
"
1672033,2017-09-26 09:20:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672033,2017-04-14 08:01:24 UTC,"[  163.975845] Call Trace:
[  163.975854]  dump_stack+0x63/0x81
[  163.975858]  __warn+0xcb/0xf0
[  163.975860]  warn_slowpath_null+0x1d/0x20
[  163.975866]  drm_atomic_helper_commit_hw_done+0xab/0xb0 [drm_kms_helper]
[  163.975869]  nvidia_drm_atomic_helper_commit_tail+0x128/0x1d0 [nvidia_drm]
[  163.975875]  commit_tail+0x3f/0x80 [drm_kms_helper]
[  163.975879]  commit_work+0x12/0x20 [drm_kms_helper]
[  163.975881]  process_one_work+0x1fc/0x4b0
[  163.975883]  worker_thread+0x4b/0x500
[  163.975886]  kthread+0x101/0x140
[  163.975888]  ? process_one_work+0x4b0/0x4b0
[  163.975890]  ? kthread_create_on_node+0x60/0x60
[  163.975893]  ret_from_fork+0x2c/0x40
[  163.975895] ---[ end trace 341cfa538776d33d ]---"
1672033,2017-04-09 20:27:40 UTC,"Jeremy, it's not related."
1672033,2017-04-09 12:26:29 UTC,https://bugzilla.gnome.org/781075
1672033,2017-03-22 15:09:07 UTC,"Hm, this makes sense."
1672033,2017-03-21 19:27:31 UTC,Here you go:
1672033,2017-03-19 02:54:04 UTC,A little bit of debugging and investigating confirm what is in log above:
1672033,2017-03-21 08:53:11 UTC,"Igor, can you post full logs from Xorg, and also any systemd-logind logs from journalctl."
1672033,2017-03-20 14:56:20 UTC,xrandr output in rootless session:
1672033,2017-03-20 14:45:16 UTC,I don't have hybrid graphics. It's a normal desktop.
1672033,2017-03-20 08:31:08 UTC,Also does lightdm work with KMS enabled for logging into gnome-shell session?
1672033,2017-03-20 08:29:36 UTC,"what hardware are you running? I recall  some hybrid laptops fail to advertise a ""primary"" display. what is the output of ""xrandr -q"" in a working root-less X session?"
1672033,2017-03-19 13:29:30 UTC,"Asked on nvidia forum, maybe they'll be able to give some advise:"
1672033,2017-03-15 19:12:25 UTC,Here is another observation (my old workaround):
1672033,2017-03-15 12:26:16 UTC,"Tim,"
1672033,2017-03-14 08:57:41 UTC,"I don't currently have access to my nvidia hardware and to be honest not even sure if rootless Xorg is supported yet on nvidia drivers, however I would have assumed that if wayland is mostly working then the KMS support would have been in good enough shape for this to work."
1672033,2017-03-21 08:53:55 UTC,(before your workaround)
1672035,2017-12-09 09:31:48 UTC,I've installed all the missing plugins and now it works fine. Thanks a lot.
1672035,2017-12-08 13:15:05 UTC,"""gstreamer1.0-fluendo-mp3"" might also be required. But, make sure the following packages listed below are installed in the system."
1672035,2017-12-08 12:03:37 UTC,"# apt-get install gstreamer1.0-plugins-ugly
Reading package lists... Done
Building dependency tree
Reading state information... Done
gstreamer1.0-plugins-ugly is already the newest version (1.8.3-1ubuntu0.1).
The following packages were automatically installed and are no longer required:
  libgles1-mesa linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic
  linux-image-4.4.0-21-generic linux-image-extra-4.4.0-21-generic snap-confine
  thermald
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded."
1672035,2017-12-07 16:26:51 UTC,"I meant gstreamer plugins, not rhythmbox plugins."
1672035,2017-12-06 16:18:57 UTC,you need to install the necessary plugins.
1672035,2017-12-07 14:53:49 UTC,These are the plugins I have:
1672035,2017-12-07 15:00:52 UTC,"It works with ogg Vorbis, but not with mp3 oder mp4 audio. ogg Opus don't know. Extracting now is running."
1672037,2017-06-06 02:21:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672044,2020-06-02 13:20:02 UTC,kolla-kubernetes has been discontinued long time ago - marking as invalid.
1672044,2017-03-11 16:16:55 UTC,"The kolla-kubernetes core reviewers are not entirely sure if this is necessary, however, to cut down on flakiness of the gate, it seems to make sense.  Perhaps there is another technique we can use."
1672044,2017-03-11 22:40:09 UTC,"There is a different way to cache the containers in infra to prevent failures that I've been working on:
https://review.openstack.org/#/c/426598/"
1672047,2017-03-19 13:48:42 UTC,Seems this error is user-caused (at least in my case) since I was able to perform a full in-vm release upgrade and solving this bug/error by:
1672052,2017-06-06 12:20:51 UTC,"I strongly agree. I just finished a big Illustration Project: I had a lot of elements on a page that I wanted to move/tweak. And I had to do it in a different app, because it was impossible to select only the object/element I needed to move..."
1672053,2017-03-11 17:35:05 UTC,"hmm.. same if you just move a shortcut in a diff position in the launcher, so click and drag a shortcut in the launcher and then press ALT TAB, now you are just selecting diff shortcuts in the launcher, the focus? is like there? not exactly what i was expecting, but maybe it's just me :D"
1672053,2017-03-11 19:15:41 UTC,"if it doesn't work the first time, try again (open the app drawer and close it)"
1672053,2017-04-06 19:10:04 UTC,This bug was fixed in the package unity8 - 8.15+17.04.20170404.7-0ubuntu2
1672053,2017-03-11 20:26:23 UTC,"better test, open the app drawer and then click outside on the background to close it, not on any opened apps."
1672057,2019-05-22 06:18:50 UTC,Fixed in Disco!
1672064,2017-03-11 22:18:54 UTC,"This is set in ubuntu-gnome-default-settings, do you have that package installed?"
1672064,2017-03-13 00:17:09 UTC,"I did not.  Installing that package does allow gdm to start up correctly.  Should the gdm package depend on ubuntu-gnome-default-settings, then, since it flat doesn't work without it?"
1672067,2017-03-11 18:19:20 UTC,techdebt remove ansible patch after decomission 2.0.0 images
1672068,2017-03-13 22:36:29 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1672070,2017-03-13 02:27:55 UTC,We first need to check that the menu window is being managed by Unity8 at all and not composited internally to the app. It's hard to tell right now due to bug 1671449.
1672082,2017-03-13 09:55:23 UTC,"Hmm... I don't think it's worth making sure the scrolling stops when the drawer is closed... However, I think the kinetic scrolling QML is much too strong when operated with a mouse. This is something that affects all lists throughout the platform."
1672082,2017-03-13 01:51:32 UTC,This may not be costing us anything if it's just remembering the scroll state. So possibly not even a performance bug.
1672085,2017-03-13 13:51:58 UTC,"Please check out revision ba3e20d0947b:
    http://hg.code.sf.net/p/enblend/code/rev/ba3e20d0947b
whether it solves the problem and the bug
description is accurate enough."
1672087,2017-03-31 16:57:38 UTC,"Ubuntu personal store will need to be seeded. (see lp:1678249)
It will be a bit confusing to have this and the gnome-software store available but not equally represented. Perhaps some UI design could help that."
1672087,2017-03-13 09:57:02 UTC,"On Xenial, this will open the apps store scope if it is installed (which might not be true by default) and on zesty this is supposed to open the snappy store, which at this point is not fully completed yet..."
1672088,2017-08-28 18:16:11 UTC,"Hi Nobuto,"
1672088,2019-09-19 11:56:10 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1672091,2019-01-22 23:07:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672091,2019-12-20 21:04:30 UTC,Zesty and Yakkety no longer supported
1672091,2020-09-02 18:22:49 UTC,"@ddstreet,"
1672091,2020-09-04 14:44:44 UTC,"> would you like to ask Debian project about it or you want me to
"
1672091,2020-09-08 12:35:47 UTC,For sure! I'm adding this to my own backlog as this is bigger priority for next cycle once we are in FF for this cycle. Thanks!
1672099,2017-03-21 19:02:38 UTC,Where does the dnsmasq package come from that is listening on 127.0.0.1? dnsmasq should normally not be listening on that address if it was spawned by NetworkManager.
1672099,2018-08-07 09:39:23 UTC,Fixed my dnsmasq systemd-resolve race with dnsmasq config.
1672099,2017-04-08 10:06:23 UTC,"The same problem arises, only when in dnsmasq I register local addresses on the virtual local server"
1672099,2017-03-21 23:30:55 UTC,"You're right, it turns out dnsmasq was only installed because I had installed polipo, which depends on the dnsmasq package. Purging polipo removes dnsmasq."
1672099,2017-03-21 18:48:25 UTC,What are the contents of /etc/resolv.conf when this happens?
1672099,2017-03-13 07:56:10 UTC,"Whenever the set of servers to which dnsmasq is forwarding queries
changes, the whole set is logged to syslog. It would be useful to have
that information."
1672099,2017-03-14 22:40:17 UTC,"I just found that I can reproduce this loop state by reconnecting to my Wi-Fi access point. The storm starts right after this line, 5 seconds after the link comes up:"
1672099,2017-03-13 08:46:39 UTC,"There aren't any such entries in syslog, presumably because I had hardcoded two upstream servers (208.67.222.222 and 208.67.220.220) using the GUI Wi-Fi settings dialog in 16.10 and they're not changing. Oddly, I can't see that setting in the 17.04 dialog, even though ""systemd-resolve --status"" correctly reports them:"
1672099,2017-03-21 18:27:29 UTC,I asked on IRC:
1672099,2017-03-13 22:15:07 UTC,"Are we clear that this is a dnsmasq problem, and not a systemd-resolved
one? Can you add --log-queries to the dnsmasq configuration and see what
dnsmasq is doing? That should demonstrate if the loop is dnsmasq
forwarding to itself, of if the problem is something else."
1672099,2017-03-13 00:01:14 UTC,Restarting dnsmasq immediately stops an ongoing DNS storm.
1672099,2017-03-14 12:05:41 UTC,"Ok, so the amplification is arising from dnsmasq looping queries around
127.0.0.1 -> 127.0.0.53 -> 127.0.0.1 -> ........."
1672099,2017-03-14 11:15:44 UTC,"I have cpulimit(1) watching dnsmasq now, so it only goes berserk for a second before being killed, but the attached syslog extract captures the moments before and during the DNS storm. These particular lookups are mostly originated by Transmission, but previously the storms have happened when there were no Transmission processes running, with queries from Firefox or perhaps some unidentified Gnome weather applet."
1672099,2017-03-14 12:09:00 UTC,"Looking again. the loop probably involves systemd-resolverd too, dnsmasq
forwards to 127.0.0.53 which is systemd-resolverd, and systemd-resolverd
then returns it to dnsmasq at 127.0.0.1"
1672105,2017-04-19 20:41:29 UTC,"Thanks for this, it looks like my fault! :-(
You can get back to a usable program with:"
1672105,2017-06-04 10:32:07 UTC,"fixed on branch 0.8.3, tag 0.8.3beta1"
1672105,2017-04-19 20:54:05 UTC,"The fix is trivial. I have committed it on branch bug1672105.
If you check it out, let me know whether it solves the problem for you."
1672110,2017-04-04 12:51:19 UTC,"Hello and thank you for sending your problem.
I am very sorry for the late reply."
1672111,2017-03-26 01:40:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672139,2017-11-24 13:20:31 UTC,*** Bug 1207486 has been marked as a duplicate of this bug. ***
1672139,2017-11-28 01:46:28 UTC,anybody know another workaround?
1672139,2017-11-28 21:35:05 UTC,"Only other workaround that I'm aware of to find the parent folder of a bookmark from the search results is to change the browser to Offline mode (Alt > File > Work Offline) and then open up the bookmark in question.  Once the bookmark is open, you can click the Star icon in the address bar to edit the bookmark and see what folder it's in."
1672139,2017-11-29 19:43:46 UTC,Thanks at least that will get me by. Clearly the browser knows which folder a bookmark is in... not sure why it's so hard to perform that process in a search result.
1672139,2018-01-16 23:31:38 UTC,"(In reply to Thomas D. (currently busy elsewhere) from comment #10)

> FTR (supporting the need for this bug):
> Go Parent Folder Addon (1): 45,991 downloads; 4,707 users (this bug)
> Show Parent Folder Addon (2): 42,583 downloads; 4,156 users (Bug 469421)
>
> (1): https://addons.mozilla.org/en-US/firefox/addon/go-parent-folder/
> (2): https://addons.mozilla.org/en-US/firefox/addon/show-parent-folder/
"
1672139,2018-01-16 23:46:02 UTC,"(In reply to public from comment #32)

> (In reply to Thomas D. (currently busy elsewhere) from comment #10)
> > FTR (supporting the need for this bug):
> > Go Parent Folder Addon (1): 45,991 downloads; 4,707 users (this bug)
> > Show Parent Folder Addon (2): 42,583 downloads; 4,156 users (Bug 469421)
> >
> > (1): https://addons.mozilla.org/en-US/firefox/addon/go-parent-folder/
> > (2): https://addons.mozilla.org/en-US/firefox/addon/show-parent-folder/
>
> This was a great solution before. These add-ons has unfortunate not been
> developed into WebExtensions.
"
1672139,2018-02-09 10:07:03 UTC,*** Bug 1436910 has been marked as a duplicate of this bug. ***
1672139,2018-03-28 14:06:03 UTC,*** Bug 1272891 has been marked as a duplicate of this bug. ***
1672139,2018-03-28 15:00:08 UTC,"(In reply to Kestrel from comment #17)

> ""Bookmarks Manager and Viewer"" can do it if you are prepared to use their
> popup for searching and managing bookmarks.
>
> https://addons.mozilla.org/en-US/firefox/addon/bookmarks-manager-and-viewer/
"
1672139,2018-08-02 20:52:45 UTC,*** Bug 1480413 has been marked as a duplicate of this bug. ***
1672139,2018-09-14 09:17:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672139,2017-10-17 16:23:54 UTC,[Tracking Requested - why for this release]:
1672139,2019-08-04 19:48:37 UTC,"(In reply to geos651 from comment #11)

> This capability should be built in Firefox, without any extension. If you
> find any bookmarks during search, there is no clue in which folder/subfolder
> they are located. The user should be able to access them upon finding them
> during search!
"
1672139,2019-10-01 11:55:20 UTC,"(In reply to fluks from comment #39)

> In a bug related to this, someone was thinking about efficiency. Does it matter if you add a button or a context menu item, then finding the path needs to be done only for that one bookmark when the user requests it. SQLite has had `WITH RECURSIVE` since 3.8.3, so you don't have to do recursion in code anymore.
"
1672139,2019-10-01 18:01:19 UTC,"(In reply to Marco Bonardo [::mak] from comment #41)

> I'd be ok extending PlacesUtils.bookmarks.fetch to also fetch the path of a bookmark if a specific option is passed into it (so, on demand).
"
1672139,2019-10-01 19:35:41 UTC,"Such ""feature"" of tracing the containing folder is felt by many to be an almost trivial necessity for people managing their bookmarks ..."
1672139,2019-10-02 07:42:40 UTC,"(In reply to fluks from comment #42)

> (In reply to Marco Bonardo [::mak] from comment #41)
> > I'd be ok extending PlacesUtils.bookmarks.fetch to also fetch the path of a bookmark if a specific option is passed into it (so, on demand).
>
> Do you mean having an about:config entry?
"
1672139,2020-06-26 20:46:22 UTC,*** Bug 1648135 has been marked as a duplicate of this bug. ***
1672139,2020-06-26 21:19:32 UTC,"Mark Banner,"
1672139,2020-06-26 22:11:23 UTC,"(In reply to Robert Townley from comment #46)

> why change the status from ""affected""?  Maybe I not remembering what ""---"" means in this context.
"
1672139,2018-03-31 01:29:37 UTC,"That web extension is great work, but because it is a web extension, we would not be able to manipulate tags.
“No management / display of bookmark tags, keywords, description field .. as Firefox does not expose those fields through its Web Extension API's.“"
1672139,2019-07-03 09:53:24 UTC,"I would like this feature too, it would be useful when you search bookmarks and you wonder in what folder a bookmark is."
1672139,2017-10-17 20:35:27 UTC,"Clearing tracking for 57 based on the rationale in bug 196509, comment 104."
1672139,2017-09-20 19:58:48 UTC,*** Bug 1393960 has been marked as a duplicate of this bug. ***
1672139,2008-12-13 02:54:51 UTC,"When viewing search results of bookmarks in the library window, it would be nice if we had an ""open enclosing folder"" contextual command when the user right clicks on a bookmark.  This would navigate the Library window to that folder, and they could hit the back button on the library window to return to the search results."
1672139,2008-12-13 02:57:46 UTC,"Need to check on the correct terms to use on Windows, and Linux."
1672139,2009-01-08 21:20:24 UTC,"i suppose on Windows is ""Open Containing Folder"", it's like that in the file search"
1672139,2009-03-18 04:55:29 UTC,Mentioned just to make sure this will apply to the bookmarks sidebar as well.
1672139,2009-08-01 01:42:11 UTC,"In bug 469416 (Add ""Folder"" to the properties pane of bookmarks when viewing
search results), I attached a sample UI (attachment 392021 [details]) which includes the ""View containing folder"" button"" proposed by this bug. It also includes
- ""Folder column"" for results table (bug 469421; SM bug 56418)"
1672139,2009-08-01 11:46:51 UTC,"Have a look at bug 405795, attachment 392075, where I am proposing the same UI concept for the ""Add/Edit this bookmark"" properties popup (yellow star), but with an *icon-size* ""Open Containing Folder"" button next to the folder widget."
1672139,2017-09-26 17:45:32 UTC,"Actually, I believe all issues related to not having an ability to locate a bookmark's parent folder are reiterations of Firefox Bug 196509 which is now 15 years old. And if we include SeaMonkey, it's Bug 56418 is 17 years old. That said, Drew Willcoxon's Comment 86 on Bug 196509 does bring up a point about nuance differences and the request to argue them separately."
1672139,2009-11-26 14:38:13 UTC,"Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string ""places-to-b-and-h""."
1672139,2010-05-22 13:40:32 UTC,"This bug still has not been fixed in Firefox 3.6.4. There no way to find the found bookmark's parent folder.
Moreover, the bookmarks search is extremely slow."
1672139,2011-11-24 10:43:22 UTC,"Alex, I still think this idea which you filed 3 years ago would be great to have (or in fact: crucial), with an excellent cost-benefit ratio...
Would it be very difficult for you to implement this?"
1672139,2011-11-24 15:16:55 UTC,"FTR (supporting the need for this bug):
Go Parent Folder Addon (1): 45,991 downloads; 4,707 users (this bug)
Show Parent Folder Addon (2): 42,583 downloads; 4,156 users (Bug 469421)"
1672139,2009-08-06 08:58:31 UTC,"Created attachment 392894
Windows and OS X file system"
1672139,2012-07-18 18:46:16 UTC,@Alex Faaborg [:faaborg]:
1672139,2017-09-11 19:21:47 UTC,"(In reply to Kestrel from comment #17)

> (In reply to Florian Berger from comment #16)
> > So Firefox currently has no way to jump to the containing folder from a bookmark search
>
> ""Bookmarks Manager and Viewer"" can do it if you are prepared to use their
> popup for searching and managing bookmarks.
>
> https://addons.mozilla.org/en-US/firefox/addon/bookmarks-manager-and-viewer/
"
1672139,2012-01-03 13:08:25 UTC,"This capability should be built in Firefox, without any extension. If you find any bookmarks during search, there is no clue in which folder/subfolder they are located. The user should be able to access them upon finding them during search!"
1672139,2017-09-08 18:19:11 UTC,"Created attachment 8906051
Go Parent Folder 2.9.1.1-signed.1-signed for interested users"
1672139,2017-08-31 21:41:09 UTC,"(In reply to Norbert from comment #15)

> Firefox 52 is great. It has bookmarks.
> But it is impossible to open bookmark's folder in search results.
>
> Steps to reproduce:
> 1. Open Firefox
> 2. Open its Bookmark Manager (<Ctrl+Shift+O>)
> 3. Search for bookmark
> 4. Try to find its folder with right-click menu.
> 5. It is impossible to find bookmark's folder.
>
> Expected results:
> Firefox is mature, so it is expected that user can find bookmark's folder.
> For example Google Chrome has ""Show in folder"" menu option.
>
> I reported bug to launchpad
> (https://bugs.launchpad.net/firefox/+bug/1672139). You may add this link to
> ""See also"".
"
1672139,2017-08-31 21:28:35 UTC,"(In reply to Kestrel from comment #17)

> (In reply to Florian Berger from comment #16)
> > So Firefox currently has no way to jump to the containing folder from a bookmark search
>
> ""Bookmarks Manager and Viewer"" can do it if you are prepared to use their
> popup for searching and managing bookmarks.
>
> https://addons.mozilla.org/en-US/firefox/addon/bookmarks-manager-and-viewer/
"
1672139,2017-10-09 14:56:28 UTC,*** Bug 1406282 has been marked as a duplicate of this bug. ***
1672139,2017-08-29 09:20:01 UTC,"(In reply to Florian Berger from comment #16)

> So Firefox currently has no way to jump to the containing folder from a bookmark search
"
1672139,2017-08-07 13:32:27 UTC,We're at Firefox 54 and this feature is still missing.
1672139,2017-03-12 11:09:35 UTC,"Firefox 52 is great. It has bookmarks.
But it is impossible to open bookmark's folder in search results."
1672139,2014-10-18 10:43:22 UTC,"I can reproduce this bug in Firefox 33.
As a temporary fix I use Go Parent Folder Add-on (https://addons.mozilla.org/en-US/firefox/addon/go-parent-folder/)."
1672139,2013-10-18 22:45:06 UTC,*** Bug 927927 has been marked as a duplicate of this bug. ***
1672139,2017-08-31 21:26:37 UTC,"(In reply to Kestrel from comment #17)

> (In reply to Florian Berger from comment #16)
> > So Firefox currently has no way to jump to the containing folder from a bookmark search
>
> ""Bookmarks Manager and Viewer"" can do it if you are prepared to use their
> popup for searching and managing bookmarks.
>
> https://addons.mozilla.org/en-US/firefox/addon/bookmarks-manager-and-viewer/
"
1672145,2017-03-13 12:15:16 UTC,"Is the device being recognised by Windows properly? Has Windows given it a drive letter? I don't think so. There is no Kobo device listed in the list following ""USB devices on system"". There is a Kobo device after ""List of WPD PNP ids"", but, it isn't being seen properly. The equivalent line for my Aura H2O is:"
1672145,2017-03-12 12:56:26 UTC,Changing the component for this bug.
1672146,2017-03-12 12:52:40 UTC,It affects in 17.04 only. Older versions of Ubuntu aren't affected.
1672147,2018-02-28 07:46:52 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1672147,2018-03-01 22:20:11 UTC,"Marking as Invalid because the release is EOL is not correct. Marking as Incomplete. Also, 18.04 is (at the time of writing) still in development, and you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29"
1672147,2018-03-02 22:41:20 UTC,"Hello, the bug is still present as reported in 17.10 with aptitude package 0.8.3-1ubuntu4."
1672149,2017-03-12 13:30:06 UTC,"See also: https://bugs.launchpad.net/inkscape/+bug/170757
Limited measuring functionality available under: Effects -> Visualise path -> Measure path"
1672149,2017-03-12 13:30:34 UTC,http://www.inkscapeforum.com/viewtopic.php?f=22&t=3822
1672149,2017-03-12 13:58:18 UTC,More people are clearly looking for this:
1672151,2017-03-12 13:51:00 UTC,"StacktraceTop:
 sipSubClass_QWebView () from /tmp/apport_sandbox_21o1fG/usr/lib/python3/dist-packages/PyQt5/QtWebKitWidgets.cpython-35m-i386-linux-gnu.so
 convertPass () from /tmp/apport_sandbox_21o1fG/usr/lib/python3/dist-packages/sip.cpython-35m-i386-linux-gnu.so
 sip_api_convert_from_new_type () from /tmp/apport_sandbox_21o1fG/usr/lib/python3/dist-packages/sip.cpython-35m-i386-linux-gnu.so
 ?? () from /tmp/apport_sandbox_21o1fG/usr/lib/python3/dist-packages/popplerqt5.cpython-35m-i386-linux-gnu.so
 PyCFunction_Call ()"
1672151,2017-04-03 19:11:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672151,2017-04-03 19:11:33 UTC,"This happens to me on opening certain files. Some seem to be fine, others not. This is a critical bug for me."
1672152,2017-04-05 19:06:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672152,2017-03-12 13:40:30 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1682
 QMessageLogger::fatal (this=this@entry=0x7ffda77b0b80, msg=msg@entry=0x7fcc37190920 ""QXcbConnection: Could not connect to display %s"") at global/qlogging.cpp:793
 QXcbConnection::QXcbConnection (this=0x55ebdcb964d0, nativeInterface=0x55ebdcb71f20, canGrabServer=<optimized out>, defaultVisualId=<optimized out>, displayName=<optimized out>) at qxcbconnection.cpp:595
 QXcbIntegration::QXcbIntegration (this=<optimized out>, parameters=..., argc=@0x7ffda77b11ac: 1, argv=0x7ffda77b13e8) at qxcbintegration.cpp:186
 QXcbIntegrationPlugin::create (this=<optimized out>, system=..., parameters=..., argc=@0x7ffda77b11ac: 1, argv=0x7ffda77b13e8) at qxcbmain.cpp:56"
1672157,2018-10-14 20:05:59 UTC,"Is there a workaround, perhaps an older version or downgrade some other package?"
1672157,2019-02-02 13:02:48 UTC,"The fix is to install the makedev package first, which provides the MAKEDEV script that's required as part of the package setup."
1672157,2019-02-09 11:51:23 UTC,Attaching patch.
1672157,2019-02-09 12:22:23 UTC,"The attachment ""mouseemu_makedev_depends.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1672157,2017-11-24 10:23:01 UTC,Thanks for reporting.
1672157,2017-05-03 07:10:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672157,2017-11-24 16:06:04 UTC,"bumping to triaged/low. At the moment, Bionic has the same version as 16.10."
1672161,2017-03-12 15:32:38 UTC,You're using Nautilus 3.22 which isn't in Ubuntu yet.
1672163,2017-10-21 19:30:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672166,2017-03-19 10:29:57 UTC,"I am sorry for inconvenience I give rise to.
I use standard Ubuntu 16.04 repositories.
cat /etc/apt/sources.list
deb http://security.ubuntu.com/ubuntu/ xenial-security main universe restricted multiverse
deb http://archive.ubuntu.com/ubuntu xenial-updates main universe restricted multiverse
deb http://archive.ubuntu.com/ubuntu xenial main universe restricted multiverse
deb http://archive.ubuntu.com/ubuntu xenial-backports universe restricted main multiverse"
1672166,2017-03-18 20:42:12 UTC,"As you said ""I won't exclude anything at this point"", I am also getting curious, I don't think it has not something to do with it but I should mention: I am using a chroot environment, so to speak I boot into a chroot environment in my external disk by means of this script https://github.com/lemonsqueeze/boot_chroot I have multiple distros that I created by means of debootstrap http://www.thegeekstuff.com/2010/01/debootstrap-minimal-debian-ubuntu-installation/"
1672166,2017-03-19 01:21:26 UTC,Your special setup is probably part of the puzzle. It might just be that you get newer versions of packages with problems that haven't made it to other distributions yet. What's your version of libatspi2?
1672166,2017-03-19 01:30:51 UTC,"Let's see what happens if we only listen to object:text-changed events, rather than the insert and delete variants. I remember AtspiEventListener being picky when registering multiple events, seemingly ignoring some for unclear reasons. Maybe your version of AT-SPI has become even more picky."
1672166,2017-03-20 13:07:37 UTC,"Thank you marmuta , frafu and all those who contributed to this project. Thanks to you I can use a computer easily."
1672166,2017-03-19 12:10:41 UTC,I just uploaded revision 2271 of trunk to the Snapshots PPA; it should be available in several minutes.
1672166,2017-03-19 12:55:39 UTC,"For the first time it suggested the word ""hello"" , I upload the debug log with ""hello"". I just tried another word ""thanks"" which it didn't recognize previously but it has just registered it."
1672166,2017-03-19 13:13:16 UTC,"Very strange, it seems to be running very well now. I upload another debug output which I typed ""greetings"", it remembered it after first typing. Have we come across a version of Heisenbug https://en.wikipedia.org/wiki/Heisenbug ?"
1672166,2017-03-19 20:31:56 UTC,"> Onboard.WPEngine      learn_text: tokens=[['<bot:term>', 'hello', 'bello', 'hello', 'hello']]
> Onboard.WPEngine      learn_text: tokens=[['<bot:term>', 'greetings', 'greetings', 'greetings', 'greetings']]
Yep, seems to work. It just means we found a fix, eventually:
http://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2271
"
1672166,2017-03-18 20:31:51 UTC,"No, I haven't customized the prompt."
1672166,2017-03-19 10:40:09 UTC,"I checked out the modification time of ""tr_TR.lm"" , it shows about 20 minutes ago."
1672166,2017-03-18 19:52:00 UTC,Trunk revision 2270 is now available in our Snapshots PPA.
1672166,2017-03-19 10:37:02 UTC,I just noticed that a few more words added to `tr_TR.lm` but it's intermittent and stopped again.
1672166,2017-03-18 10:15:57 UTC,"I won't exclude anything at this point, but this seems unlikely, as Onboard doesn't depend on any particular input method."
1672166,2017-03-12 22:08:30 UTC,I forgot to mention that I already checked that setting in preferences menu. Can it be related to accessibility  or dbus daemon?
1672166,2017-03-12 21:26:42 UTC,There are settings in the Onboard Preferences to not have it learn new words. You can find it in the Advanced tab of the Typing Assistance section of the Preferences dialog.
1672166,2017-03-13 08:04:14 UTC,"If you see any suggestions at all, then AT-SPI is available/accessibility and dbus daemon are working."
1672166,2017-03-13 09:38:36 UTC,"@marmuta I just tried your instruction, in debug terminal no `Onboard.WPEngine learn_text: tokens=[['<bot:txt>', 'hello']]` prints, it doesn't print anything with `learn_text: tokens` when I enter a word in another terminal,  gedit, pluma etc. or any other accessibility compliant text editors."
1672166,2017-03-18 13:03:47 UTC,"OK, one more snapshot please, Francesco, thanks in advance."
1672166,2017-03-13 21:38:03 UTC,"PYTHONPATH changes would more likely result in tracebacks, rather than subtle changes to word suggestions, in particular since this mixes Python 2 with Python 3 packages. Not saying it's impossible, but I doubt that's the reason."
1672166,2017-03-14 11:34:51 UTC,"I added the debug info. I noticed that it completely stopped learning for a few weeks, it only suggests learned words from a few weeks ago."
1672166,2017-03-13 10:44:41 UTC,I purged `onboard` and `onboard-data` then added `sudo add-apt-repository ppa:onboard/stable` and did `sudo apt-get update && sudo apt-get update` but it didn`t work. I checked out language model path at `/home/kenn/.local/share/onboard/models/en_US.lm` then I removed `/home/kenn/.local/share/onboard` thinking that it might be a permission issue but after removing that folder it doesn`t recreate it in spite of reinstalling `onboard` and `onboard-data` . It might be a python path issue? Becaused I added `export PYTHONPATH=$PYTHONPATH:/usr/lib/python2.7/site-packages/` to .bashrc last week.
1672166,2017-03-16 01:14:14 UTC,"Done testing trunk on 16.04 and it did learn as it should. No obvious regression there with Onboard 1.4. All unit tests pass too. It was the 64 bit version, though. If we get stuck I'll try the 32 bit version too."
1672166,2017-03-16 13:22:42 UTC,"Revision 2261 containing the additional debug output is now available in our Snapshots PPA for xenial, yakkety and zesty:
https://launchpad.net/~onboard/+archive/ubuntu/snapshots"
1672166,2017-03-17 10:47:34 UTC,"Thank you guys, I am grateful to you. I added the ppa and did an upgrade. I used my own locale, some info printed in Turkish in the debug output,  If you have a difficulty at understanding it, I  can switch my locale to US."
1672166,2017-03-17 10:54:31 UTC,Here it is ~/.local/share/onboard/models/tr_TR.lm
1672166,2017-03-17 22:30:01 UTC,"> 13:33:13.881 DEBUG   Onboard.WordSuggestions commit_changes(): has_changes=False
and
> 13:33:57.891 DEBUG   Onboard.WordSuggestions commit_changes(): has_changes=True
> 13:33:57.891 DEBUG   Onboard.WordSuggestions LearnStrategyLRU.commit_changes():
> changes=TextChanges([""TextSpan(14, 0, '', 0, None)""])
"
1672166,2017-03-18 09:28:44 UTC,just an intuitive suggestion; may it be related to `system settings > language support > language tab > keyboard input method` ? In the dropdown list I have only XIM and None options. IIRC in 14.04 I had ibus and xinput?
1672166,2017-03-15 02:14:57 UTC,"Hmm, everything appears to work as expected but when it's time to learn, there is no attempt being made. It's as if learning was turned off or paused, but looking at your settings, that clearly isn't the case."
1672169,2017-03-12 18:10:25 UTC,did you already set the password via ssh ?
1672169,2019-10-01 16:22:22 UTC,I'm marking this as incomplete under suspicion that the reporter did not configure his ssh keys on the launchpad / ubuntu one sso account.
1672175,2018-03-09 10:52:19 UTC,"Daniel, it was Fix Released until we needed to promote gnome-shell to main. chrome-gnome-shell's MIR is blocked (LP: #1695565)."
1672175,2018-03-09 09:43:27 UTC,Should this bug be fully closed yet?
1672175,2017-06-15 21:37:01 UTC,This bug was fixed in the package gnome-shell - 3.20.4-0ubuntu3
1672175,2017-05-31 13:26:41 UTC,"From Ubuntu (Unity) 16.04, 16.10 and 17.04, I enabled -proposed updated and installed gnome-shell and verified that chrome-gnome-shell was automatically installed as expected."
1672175,2017-06-15 21:36:08 UTC,This bug was fixed in the package gnome-shell - 3.18.5-0ubuntu0.3
1672175,2017-05-29 14:31:24 UTC,"Hello Jeremy, or anyone else affected,"
1672175,2017-05-29 14:18:02 UTC,"Hello Jeremy, or anyone else affected,"
1672175,2017-06-15 21:36:22 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1672175,2017-05-29 10:15:57 UTC,"Thanks for preparing the SRU! This doesn't seem to be the case for artful though, is it? Checking the packaging for gnome-shell (3.24.2-0ubuntu4) I don't see the same Recommends as proposed here - is it not needed there? Or is it a bug that only affects gnome users below 3.24? Same for zesty."
1672175,2017-05-29 12:42:00 UTC,"Łukasz, the last paragraph of the bug's description explains why 17.10 artful does not currently recommend chrome-gnome-shell (it's to make the gnome-shell MIR easier but I think chrome-gnome-shell will be in main and that recommends will be re-added before 17.10 is released)."
1672176,2017-03-14 16:42:04 UTC,"After windows sleep/wake, hibernate/resume [edit] THEN restart or full shutdown I can mount the NTFS partition."
1672181,2017-03-12 21:45:58 UTC,"This is a semi-non-bug because the names appear to actually *be* the names padded to 16 chars with null bytes. So if you need to get a sensor with get_sensor_reading, you need the null bytes."
1672182,2017-03-13 03:13:54 UTC,"Heat delete the resources of stack and check whether they were deleted complete, in above user case, heat will delete pool first and then delete listener and last delete lb, so in your test, all the listeners were deleted, but three pools
remained, so seems there is something wrong in neutron, could you look into the neutron log to find out the reason?"
1672182,2017-03-13 10:09:38 UTC,"Only see (several times), which isn't very revealing:"
1672182,2017-03-13 10:11:17 UTC,"But because there ARE pools left, Heat shouldn't continue with trying to delete the LB, so error is ""irrelevant"" (from Heats point of view)."
1672189,2020-02-06 21:31:17 UTC,"@ Ciro Santilli,"
1672189,2020-02-07 12:18:14 UTC,Thanks for the followup sudodus!
1672198,2021-01-20 15:24:58 UTC,Works since 2019
1672198,2017-03-17 02:54:23 UTC,"In addition, please attach the output of `rfkill list`, thanks."
1672198,2017-05-25 19:19:01 UTC,Same issue  here. Please checkout my posted bug report  for details.
1672198,2017-03-17 02:49:22 UTC,"Can you boot with ""rtl8xxxu.debug=0xffff"" and attach the dmesg?"
1672198,2017-03-13 17:05:09 UTC,Because I do not have access to the machine running Ubuntu now i ran apport from my machine which is identical and has the identical problem with RTL8723 just it runs Linux Mint. As you can see I tried various Kernel up to 4.9 and the problem is the same with any kernel.
1672198,2017-03-13 22:58:49 UTC,It did start as I had to use kernel 4.8 in order to get my multimedia keys and suspend to ram working on that machine. With Kernel 4.4 I had to compile the the driver from lwfinger in order to use wifi.
1672198,2017-03-13 15:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1672198,2017-03-12 20:33:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1672198,2017-03-15 14:16:29 UTC,Bug still present with Kernel 4.11 Rc2.
1672198,2017-03-13 17:00:36 UTC,apport information
1672198,2017-03-13 19:24:14 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1672206,2017-03-13 10:58:04 UTC,"Hi,"
1672206,2017-03-13 20:37:16 UTC,ok. The window border and the close button work!
1672206,2017-03-14 08:29:25 UTC,"Courtesy to Saviq, he points out that the workspace preview widget is Compiz's Display Wall plugin."
1672206,2017-03-13 03:17:24 UTC,"Hi, can you try the ppa in https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1292830/comments/90?"
1672224,2017-03-12 23:00:14 UTC,This change was made by a bot.
1672224,2017-03-13 19:15:13 UTC,Does the bug go away if you boot back into the prior kernel version?
1672224,2017-03-14 21:23:04 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1672224,2017-03-14 21:34:13 UTC,"I installed the new kernel and it appears to be working.   Some issues with
nVidia drivers but that's not exactly news for linux."
1672224,2017-03-14 22:28:17 UTC,"Quick question.
Due to lack of time and resources to investigate this bug, I reinstalled de novo, Ubuntu 16.04.2.
The new kernel  4.8.0-41 was installed but the fact that I now am seeing a functional system doesn't really impact this bug.  This bug was about very serious issues with the upgrade of the kernel of a system that started life as 16.04 LTS-original."
1672224,2017-03-14 22:37:14 UTC,"Given the new kernel, this bug should remain open as long as the 4.4.0-66 is available for installation as it appears to be directly relevant to upgrading to this kernel."
1672224,2017-03-14 22:45:57 UTC,Might I suggest a bug be created for the behavior I saw regarding removing other kernels.
1672224,2017-03-25 11:25:48 UTC,"I'm having significant problems with LibreOffice Write with kernel 4.4.0-66, but not with 64.  The program won't allow text to be highlighted and locks up one core of my CPU.  A graceful shutdown of Write is not allowed and even Ubuntu won't shut down without a manual switch off."
1672224,2017-03-13 20:07:45 UTC,"Yes, booting an old kernel gives a good system."
1672227,2017-05-07 14:18:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672229,2017-06-15 22:17:10 UTC,"Here is a log with the issue.
I had to rename it because you have to exit and re-run it to see the issue.
The name should help with the order. I just discovered I can only do one file, so I added them to a zip."
1672229,2017-06-15 21:26:23 UTC,Couple of notes.
1672229,2017-06-15 21:44:44 UTC,"After posting the previous comment about dragging the slides, I went back and tested the same process only using the disk icon (Load new media). My first pass did NOT reproduce the issue.
So maybe it has to do with adding media by dragging from folder to media window and the number of entries when adding."
1672229,2017-06-15 22:26:30 UTC,"Here is a set of logs doing the same steps except with using icon (Load new media).
The issue was NOT reproduced.
Again this was successful.
I am sending this log so you can see the difference."
1672231,2017-03-13 13:27:21 UTC,This is a known issue (#1649649) because proot is broken on that version of the linux kernel and lxc/lxd are not supported on that kernel. See proot bug: https://github.com/proot-me/PRoot/issues/106
1672231,2017-03-21 16:07:52 UTC,"Certainly, I'll have a go when I get home from work."
1672231,2017-03-13 16:45:05 UTC,There won't be much I can do about then will there? Oh well. I'll have to wait until they update things.
1672231,2017-03-13 16:26:53 UTC,I'd recommend you *don't* use Terminal App for container creation.
1672231,2017-03-21 15:44:32 UTC,"Yeah, that output indicates a transient issue with the debootstrap archive and I have seen issues like this from time to time.  Nothing we can in Libertine to address this, but could you try again to see if it's working now?"
1672231,2017-03-13 14:44:47 UTC,Are you creating the container using the Terminal App?  There is a known bug in the terminal app https://bugs.launchpad.net/libertine/+bug/1605354 you may be running in to.  Try using ssh (even from the terminal app) to get around confinement.
1672231,2017-03-13 14:37:41 UTC,"That's interesting - we haven't seen container creation failures on vivid before, and we haven't released a new version of libertine on vivid in many months. Maybe there were some changes to the archives over the weekend?"
1672231,2017-03-13 14:23:41 UTC,Ubuntu 15.04 (OTA-15)
1672231,2017-03-13 14:06:19 UTC,Right - my previous comment assumes you are attempting to run the xenial image on the m10. vivid should still be working fine.
1672231,2017-03-13 13:53:59 UTC,Basic creation of a container on the M10 should just work on shipped images.  Is this a custom Xenial image or a supported Ubuntu Touch image?
1672231,2017-03-13 15:29:32 UTC,I'm using phablet-tools with ssh via a usb cable from my ubuntu 16.04 laptop
1672235,2017-03-13 01:37:33 UTC,apport information
1672235,2017-04-20 12:03:12 UTC,"A note on severity - I'm seeing this error or the one in bug #1650877 for every single non-gov domain in the .il root, including google.co.il, all major universities under .ac.il, and every newspaper I can think of under .co.il. Might also indicate some common thread in the DNS roots affected."
1672235,2017-03-13 02:20:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672235,2017-03-13 01:37:34 UTC,apport information
1672235,2017-03-13 01:37:31 UTC,apport information
1672235,2017-03-13 01:37:20 UTC,apport information
1672235,2017-03-13 01:37:28 UTC,apport information
1672235,2017-03-13 01:37:26 UTC,apport information
1672235,2017-03-13 01:37:24 UTC,apport information
1672235,2017-03-13 01:37:23 UTC,apport information
1672235,2017-03-13 01:37:21 UTC,apport information
1672235,2017-03-13 01:37:29 UTC,apport information
1672235,2017-03-13 01:37:17 UTC,apport information
1672235,2017-03-13 01:37:18 UTC,apport information
1672236,2017-03-17 13:51:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672238,2017-03-13 14:50:52 UTC,"We've had a bunch of problems with this but I'm not really sure what to do. PBR has always caused more problems than it's solved so I'd rather we just not use it at all, if that's possible."
1672238,2017-03-17 03:03:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/446823"
1672238,2017-03-21 15:19:15 UTC,"Reviewed:  https://review.openstack.org/446823
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=ca292847ef5cc3e6be0ef3e0ea3bfa35905fa65d
Submitter: Jenkins
Branch:    master"
1672241,2017-06-19 12:43:16 UTC,This issue was fixed in the openstack/kolla-ansible 4.0.2 release.
1672241,2017-06-09 15:36:26 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1672241,2017-04-19 15:09:55 UTC,"Reviewed:  https://review.openstack.org/444719
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=0defa3b3ea37c7ba1113ea953a72f1e847877059
Submitter: Jenkins
Branch:    master"
1672241,2017-04-20 10:18:51 UTC,"Reviewed:  https://review.openstack.org/444720
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=cb325b9565d9ad2a2262045df1f6ddde7efd562a
Submitter: Jenkins
Branch:    stable/ocata"
1672241,2017-04-20 10:01:18 UTC,This issue was fixed in the openstack/kolla 4.0.1 release.
1672241,2017-04-17 15:40:53 UTC,"Reviewed:  https://review.openstack.org/444681
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=c69c3e5fecad8b737834f5714dc36d29b8e3f077
Submitter: Jenkins
Branch:    stable/ocata"
1672241,2017-04-12 11:28:38 UTC,"Reviewed:  https://review.openstack.org/444680
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=5558bd53fb6e8771534664580e814b4b8fa4ef3e
Submitter: Jenkins
Branch:    master"
1672241,2017-06-09 15:30:35 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.
1672245,2017-06-09 15:32:38 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.
1672245,2017-06-09 15:36:24 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1672245,2017-04-20 10:02:32 UTC,This issue was fixed in the openstack/kolla-ansible 4.0.1 release.
1672245,2017-03-22 14:21:17 UTC,"Reviewed:  https://review.openstack.org/447300
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=39575109269c2eed30cce533479b9a8d818fe549
Submitter: Jenkins
Branch:    stable/ocata"
1672245,2017-03-19 14:30:48 UTC,"Reviewed:  https://review.openstack.org/444708
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=411fdb90d187aec4ada97dd8405315f4323c62db
Submitter: Jenkins
Branch:    master"
1672245,2017-03-19 05:44:28 UTC,"Reviewed:  https://review.openstack.org/446331
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=790e313a05aaa452143e077192c0b7dc6a0d77f1
Submitter: Jenkins
Branch:    stable/ocata"
1672245,2017-03-13 03:32:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444699"
1672245,2017-03-13 04:23:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444708"
1672245,2017-04-20 10:01:28 UTC,This issue was fixed in the openstack/kolla 4.0.1 release.
1672245,2017-03-16 04:05:44 UTC,"Reviewed:  https://review.openstack.org/444699
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=05c0d6998bdda155c925d563b75ac353303f93ff
Submitter: Jenkins
Branch:    master"
1672256,2018-06-26 03:33:15 UTC,Pinging again...
1672256,2019-04-30 02:25:55 UTC,Pinging again...
1672256,2020-11-30 13:28:52 UTC,"Hello,"
1672261,2017-04-28 01:51:08 UTC,"Hi Hari/Arun,"
1672261,2017-03-16 08:26:57 UTC,"When there is active-backup tor-agent configuration, when local MAC is deleted, that doesnt get propagated immediately. The backup tor-agent exports a route with a lower preference and that still remains (for 5 minutes). This is done to avoid traffic loss upon OVSDB connection switchover. Please check that the entry is removed after 5 minutes."
1672261,2017-05-12 23:14:49 UTC,"Hi Arun,"
1672261,2017-03-16 21:09:44 UTC,"We even waited for more than 5 minutes and even for a day .Still the switch was showing remotely learnt mac through vtep.Even though the mac was not seen locally in the remote switch .
The OVSDB database still had Remote MAC in the current TOR ."
1672263,2017-03-15 07:09:03 UTC,review at: https://review.openstack.org/#/c/445780/
1672263,2017-03-15 06:21:56 UTC,review at: https://review.openstack.org/#/c/445768/
1672276,2020-04-03 12:16:31 UTC,"It's been like 2 years, any news on this?
Also affects bionic."
1672276,2018-10-08 10:59:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672276,2020-04-30 17:04:53 UTC,"This seems to be fixed in Focal, where all the tooling is based on nftables:"
1672276,2018-04-30 20:00:09 UTC,Some sort of initialization is missing:
1672276,2017-10-18 16:44:06 UTC,"I don't believe there was an upstream report, however it looks like ebtables-restore was removed from the upstream repo here:"
1672276,2017-10-17 12:09:18 UTC,"@Nish / @Josh - you worked on this before, was there any upstream report already that might be missing or is this waiting for someone to actually report it first (also pinging on IRC about it)?"
1672276,2017-03-14 16:43:13 UTC,"This appears to exist on Xenial, Yakkety, and Zesty. Brought up a quick LXD using the ubuntu-daily images and reproduced it in each."
1672276,2017-03-28 08:53:37 UTC,"Is there a workaround or a way to make a file that ebtables-restore does accept, by hand for example?"
1672276,2017-03-14 16:36:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672276,2017-04-25 00:21:00 UTC,"# ebtables-restore < txt1.txt
Bad table name 'filter'.
# ebtables -t filter -L
Bridge table: filter"
1672276,2017-10-13 07:42:40 UTC,any news on this
1672276,2017-03-29 16:24:52 UTC,"@ktf the only other report of this I could find was someone doing the restore manually here:
http://knoffhoff.tumblr.com/post/59967875099/how-to-save-and-load-ebtables-rules"
1672297,2018-04-18 18:39:13 UTC,This bug was fixed in the package gjs - 1.52.1-1ubuntu1
1672297,2018-06-26 08:11:48 UTC,I think the cleanest first step will be -> bug 1778660
1672297,2018-06-26 07:21:12 UTC,"It appears the only gjs fixes we are missing are:
  https://gitlab.gnome.org/GNOME/gjs/merge_requests/121
  https://gitlab.gnome.org/GNOME/gjs/merge_requests/122"
1672297,2018-06-04 06:33:01 UTC,It's on the (backlog) queue: https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle
1672297,2018-06-01 09:28:18 UTC,"https://gitlab.gnome.org/GNOME/gjs/merge_requests/122 is now merged, all the other merge requests linked to in https://gitlab.gnome.org/GNOME/gnome-shell/issues/64 are now merged. Daniel could we have soon have a -proposed package of backports of these fixes up for testing? :)"
1672297,2018-05-17 20:09:59 UTC,"After some minutes I logged in (Ubuntu 18.04, gnome-shell) something used a lot of memory (approx. 1GB). I checked gnome-system-monitor, but there was not any process which used more memory as usual (neither user nor system). Nothing was opened or launched. Only one thing helped: logout and login again.
I have no idea what was that, and I can not repeat it again.
(gnome shell is extremely laggy :-( )"
1672297,2018-05-03 07:08:02 UTC,"Looks like we're still waiting for upstream to land:
https://gitlab.gnome.org/GNOME/gjs/merge_requests/122"
1672297,2018-04-23 22:39:30 UTC,I am unsubscribing ubuntu-sponsors since I don't see anything here now that is ready for sponsoring. Please feel free to resubscribe when you have something else that needs sponsoring.
1672297,2018-04-20 11:21:01 UTC,"Let's keep this open till we have the full set up upstream fixes in Ubuntu:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64"
1672297,2018-07-04 09:07:26 UTC,This bug was fixed in the package gjs - 1.53.3-1
1672297,2018-04-20 11:20:54 UTC,"And you should... SEE THIS LINK
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773 which is the most important memory leak and I posted it 3 years ago, could be possible that just ONE developer take this seriously?"
1672297,2018-04-20 08:32:20 UTC,"Yep, that's about ignorant gnome-shell team and really outdated toolkit. Ubuntu should use KDE."
1672297,2018-04-19 12:30:28 UTC,"Guys, i am not programmer, but i`m wander why gnome have so many memory leaks? Most of them have been known for years and nobody cares till Ubuntu LTS 18.04 release. Bad code, bad programming, or other reason?!"
1672297,2018-04-19 11:34:31 UTC,If you really want to close this bug PLEASE WATCH THIS https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773
1672297,2018-04-19 04:30:49 UTC,I wonder if we should keep using this bug as the additional leak fixes land in future?
1672297,2018-05-03 06:29:37 UTC,Any news on this?
1672297,2018-07-04 09:30:05 UTC,"Technically, being in cosmic-proposed only makes it Fix Committed. Not yet Fix Released."
1672297,2018-07-04 11:09:03 UTC,"OK, in this instance Simon had quoted this bug reference in the changelog for a previous version:"
1672297,2018-07-04 10:50:27 UTC,This bug was fixed in the package gjs - 1.53.3-1
1672297,2018-11-14 04:28:42 UTC,I don't know what I was thinking... This bug is clearly declared fixed in 18.04 already:
1672297,2018-11-01 03:00:02 UTC,"This bug is fixed in Ubuntu 18.10, but beware 18.10 also brings a new separate leak: bug 1800165."
1672297,2018-10-08 20:20:26 UTC,I switched from nvidia driver to nouveau driver and the huge memory usage disappeared. Small jumps (increase) in memory usage stayed with us.
1672297,2018-09-19 09:48:32 UTC,No comment...
1672297,2018-09-11 17:56:31 UTC,Gnome 3.30 is out. Are there any ETA or plan to fix this Critical issue?
1672297,2018-09-02 21:55:14 UTC,"I installed Ubuntu 18.10 gjs and libgjs0g 1.53.3-1 (of  Ubuntu 18.10) to
Ubuntu 18.04. It seems that the memory leak lives forever...
Memory usage started from 170MB, and after two hours is over 360MB.
[image: Képernyőkép erről: 2018-09-02 23-46-44.png]"
1672297,2018-08-20 14:38:01 UTC,"This is:
 apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.28.2-0ubuntu0.18.04.1
  Candidate: 3.28.2-0ubuntu0.18.04.1"
1672297,2018-07-31 20:20:02 UTC,"Yesterday I discovered another Gnome software bug, (another) one of Files (Nautilus). Without any reason, Files was running 4+% of the CPU for a long time, without even touching it. Might be some interaction, if I see that again, will file a separate bug report."
1672297,2018-07-31 13:54:59 UTC,Will all these memory bleed issues be patched in the upcoming 18.04.1 LTS release?
1672297,2018-07-27 18:23:31 UTC,"Can we PLEASE get some kind of coherent update on this for bionic. Most distros (debian unstable, arch) already incorporated this fix. Is this fix coming? Is any part of it coming? This is issues is serious enough that it needs addressing, please respond!"
1672297,2018-07-25 16:23:39 UTC,Ubuntu 18.04.1 is coming soon (tomorrow?). What about the bug fixes?
1672297,2018-07-16 02:53:10 UTC,"Well for this bug I need to install Xubuntu and lightdm, run very fast with no issues, BUT looks like Firefox is eating a lot of RAM in both desktops, for my job I need FF to be opened all the time, so the time to time I need to close it and relaunch it, if not FF freezing my desktop, now even Chrome eats a lower portion of RAM than FF... are you have similar problems with FF + ubuntu?"
1672297,2018-07-15 23:23:56 UTC,"I recently changed my Ubuntu 18.04 installation to use i3 window manager due to this issue, but alas, it's not enough, as GNOME is used for my login screen. After 3 days away from my desk, the memory is 38.2G/39.2G and swap is 14.6/22.4G and the /usr/bin/gnome-shell process owned by gdm has taken 78.7% of my memory with 45.1G VIRT and 30.8G RES in htop."
1672297,2018-07-15 21:37:34 UTC,"@ Nick Timkovich
The 'fix released' for 18.04 (1.52.1-1ubuntu1)  is to the extent as seen in comment 78 which may not be as developed as the 'fix released' for 18.10 , i.e comment 96
The bionic task for gjs as shown at top still says 'In progress' which *may* mean there are further gjs patches under consideration for 18.04.."
1672297,2018-07-10 15:48:00 UTC,"For us end-users, does ""Fix Released"" just mean released to a nightly/unstable/private package repo? Because https://packages.ubuntu.com/bionic/gjs still lists the version at 1.52.1, that means this still unreleased in stable?"
1672297,2018-07-05 03:40:48 UTC,"Laney,"
1672297,2018-04-18 13:08:57 UTC,"Rocko,"
1672297,2018-07-04 10:17:36 UTC,"On Wed, Jul 04, 2018 at 09:30:05AM -0000, Daniel van Vugt wrote:

> Technically, being in cosmic-proposed only makes it Fix Committed. Not
> yet Fix Released.
"
1672297,2018-04-18 13:03:42 UTC,Seems not committed anywhere yet.
1672297,2018-02-02 20:10:19 UTC,"Regarding #32, The total shown is 16,293,840 and used is 1,781,036, which is about 11% of the total, not more than total. (With that many digits, commas help.)"
1672297,2018-04-18 10:05:04 UTC,I managed to build and install a patched gjs last night thanks to a helpful hint from a fellow user (ie to use debuild -us -uc -b to build it instead of make and make install).
1672297,2017-11-06 09:32:36 UTC,Thanks Paul. The only slightly conclusive information I got from that so far is:
1672297,2017-11-03 10:07:03 UTC,"I've installed most of the debug symbol packages, and the attached Massif profile has far fewer unknowns. However, this isn't a proper run, because when I try to log in now, gnome-shell grinds for a minute or so and then quits. Works fine without Valgrind, of course. I suspect it has some form of watchdog timer and is killing itself."
1672297,2017-11-03 09:12:00 UTC,"Actually it's not the ""top"" of the output that's interesting. The snapshot #1 just shows where memory went initially on start-up (to loading images). That doesn't represent the ongoing growth problem though. You need to scroll down to later snapshots in the ms_print output to see where the growth is coming from, like snapshot 51:"
1672297,2017-11-03 08:54:13 UTC,"Next, please try to find and install debug symbol packages for those libraries near the top of the output listed with ""???"":"
1672297,2017-11-03 08:51:26 UTC,Thanks Paul.
1672297,2017-11-03 07:46:09 UTC,"Ah yep, that would do it. Just be sure to have the script check the username, because even if you're on a single-user system the gdm user also runs a gnome-shell:"
1672297,2017-11-03 04:59:56 UTC,It's often easier to replace the binary itself with a debug script. For example:
1672297,2017-11-06 09:38:13 UTC,"P.S. To start gnome-shell manually, this seems to do the trick:"
1672297,2017-11-03 04:33:13 UTC,"Tried to get a Massif profile, starting a new gnome-shell with --replace, but it fails before it can replace the running process due to bug #1700465:"
1672297,2017-10-22 22:51:31 UTC,"As of now this still persists in Ubuntu 17.10 with the gnome-shell for 3.26, 8 hours of uptime and the shell is at nearly 1 GB size."
1672297,2017-03-17 21:05:19 UTC,"Cliff, thank you. Could you please forward that to GNOME instead?"
1672297,2017-03-17 20:53:37 UTC,Saw what appeared to be a memory leak in gnome-shell so set up a pidstat trace to see the memory activity.  Added this trace text the monitored thought the day.  The increase in memory usage appears to be consistent and not related to what activity being done on the system.  Most of the morning and early afternoon the system was unused.
1672297,2017-03-17 00:35:51 UTC,"Thanks for the suggestion; my symptoms are an exact match for this existing bug, including memory leaked each time a different window gets focus (especially with Alt+Tab):"
1672297,2017-03-17 00:02:00 UTC,Thank you for taking the time to report this bug. Could you report this issue to GNOME?
1672297,2018-04-18 13:03:10 UTC,"Yes, we know that is only one of the leak fixes. The other fixes (upstream, not reviewed yet) are less mature and have not been included in the Ubuntu patch."
1672297,2017-03-16 14:17:43 UTC,Can you reproduce this now? There have been several 3.23.92 updates this week (in particular gjs) that might have helped with this bug.
1672297,2017-11-03 03:56:57 UTC,"Confirmed. Seems I can make gnome-shell grow by about 1MB per second if I move the mouse over the dock continuously, or scrub across the panel menus continuously. That might not be the only problem but the rate of growth is quite significant."
1672297,2017-11-08 09:34:26 UTC,"Looks like upstream has had the same idea this week:
https://git.gnome.org/browse/mutter/log/?h=gnome-3-26&qt=grep&q=leak"
1672297,2017-03-16 22:39:12 UTC,"Yes, I upgraded to 3.23.92-0ubuntu1 yesterday and it's at 459 MiB after about 15 hours' runtime and growing at a similar rate."
1672297,2017-12-09 05:19:07 UTC,"ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 17.10
InstallationDate: Installed on 2017-11-02 (36 days ago)
InstallationMedia: Ubuntu 17.10 ""Artful Aardvark"" - Release amd64 (20171018)
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: mutter
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Tags:  artful
Uname: Linux 4.13.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True"
1672297,2017-11-29 16:15:08 UTC,I'm also having huge memory usage for gnome-shell. I noted that after have watched a movie using another display (my smart-tv) the memory used by it are on 3.4Gb !!!
1672297,2018-02-11 00:27:35 UTC,Just noticed it in updated Bionic. After boot uses around 450MB of VRAM and then suddenly jumps to 1200MB and more when only Chrome is running. When Chrome is closed it does not change. Using Geforce 960 GTX with 390 drivers. Freezes and also black streak flashes on one of monitors sometimes. When the process is killed it restarts and drops back to less then 500MB.
1672297,2018-02-09 07:45:26 UTC,"Yes, I got some freezes, too, even longer than 10 seconds. One time I restarted the laptop as I did not know what is going on, another time at some point Gnome crashed and started by itself. This did not happen in Unity."
1672297,2018-02-09 04:20:07 UTC,"The entire UI lags far behind as well. When gnome-shell using around 500 MB RAM, middle clicking Nautilus freezes the entire system UI for up to 10 seconds. No mouse, no keyboard, no clicking."
1672297,2018-02-08 00:16:49 UTC,"VmData:	  636560 kB     10:30
VmData:	  848276 kB     15:45"
1672297,2018-02-05 02:03:01 UTC,It's important to remember that RSS increases is no indication of a leak - it will rise and fall according to how busy the machine is and not how much new memory the process has allocated. Please ignore all RSS values as they are going to be unpredictable and misleading.
1672297,2018-02-02 20:33:30 UTC,"If I press the Ubuntu key over and over, showing the overview of all the desktops, and then again to return to the normal view of the current desktop, RSS for gnome-desktop increases rapidly (measurements taken at 15-second intervals."
1672297,2018-02-02 20:25:08 UTC,"I'm trying to track down something that makes system performance degrade in less than an hour. Whenever I switch desktops, move my cursor to a place where a tooltip is displayed, open a pull-down menu, the display freezes for 5-15 seconds before, for example, the menu or tooltip is released."
1672297,2018-01-29 17:46:32 UTC,Also seen on AskUbuntu - https://askubuntu.com/q/1001069/66509 .
1672297,2017-11-03 08:17:37 UTC,"I see the same leak you do when interacting with the panel. In fact, just pressing the Meta key twice to bring up and hide the overview leaks 1 MiB of RAM each time. Even switching workspaces leaks memory. These are all things that jank once gnome-session's footprint has grown to unreasonable sizes, so presumably that jank is a symptom of bloated datastructures taking more cycles to negotiate."
1672297,2018-01-09 11:31:14 UTC,"Hi, I'm running ubuntu 17.10 with gnome 3.26.2"
1672297,2017-12-09 05:19:08 UTC,apport information
1672297,2017-12-09 05:19:10 UTC,apport information
1672297,2017-12-09 05:19:13 UTC,apport information
1672297,2018-01-09 11:34:11 UTC,more info: my current setup has 4 monitors running with 2560x1440
1672297,2017-12-09 15:31:25 UTC,"At any given time: immediately after reboot, immediately after restarting gnome-shell (alt+F2 --> ""r""), and during regular use gnome-shell is consuming at least 4GB RAM. I'm happy to provide a memory profile but I don't know how to do that so I need help."
1672297,2017-12-31 15:11:22 UTC,"No matter what you do, gnome-shell eats up RAM slowly. In case you shutdown your machine after every use, you will not notice it, however, if you keep it running or tend to suspend/hibernate, it will reach a point when it will swap."
1672297,2018-01-02 04:11:23 UTC,"Also note we're still waiting for mutter and gnome-shell v3.26.3 to reach Ubuntu 18.04. Some leak fixes have gone into 3.26.3 but it's not yet released. It will be interesting to see what, if any, improvement v3.26.3 makes for people here."
1672297,2017-12-09 05:19:14 UTC,apport information
1672304,2017-03-13 09:36:01 UTC,I'd say the problem is actually that the package hasn't picked up and installed the binary
1672304,2017-03-14 21:00:01 UTC,"setup.py creates the ""disk-image-create"" script; this is the way just about every other project works."
1672304,2017-03-13 09:53:35 UTC,"There is a problem: current git for 2.0.0 does not contains any bash-scripts with name 'disk-image-create'. Only python script (through entry points), which, in turn, calls actual program which tries to run non-existing bash-script."
1672309,2017-03-13 11:09:35 UTC,It seems to be related to host's network.
1672309,2017-03-13 11:39:42 UTC,"@Oleksiy if it is related to host's network, should we assign this one to infra team?"
1672309,2017-03-13 16:33:40 UTC,Could you please provide more additional information about where that job or installation was running? Also you can provide a link to the job.
1672309,2017-03-14 09:06:18 UTC,"Please provide more information about the problem with network.

>It seems to be related to host's network.


what the problem ? with internet , network between VM's etc"
1672309,2017-03-14 10:35:30 UTC,https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.thread_3/208/testReport/(root)/ceph_ha/
1672318,2017-03-13 10:00:07 UTC,This change was made by a bot.
1672318,2017-03-13 19:24:53 UTC,You may need to run the following from a terminal:
1672323,2017-03-13 11:34:42 UTC,"terminate called after throwing an instance of 'std::runtime_error'
  what():  Application is not shown in 'Unity:Unity8'"
1672323,2017-03-13 15:52:07 UTC,Fuller backtrace http://paste.ubuntu.com/24171199/
1672323,2017-04-05 13:13:05 UTC,"I can't seem to reproduce this anymore, paste seems to do ""nothing"""
1672323,2017-03-13 11:07:18 UTC,Got output from unity8.log? It should say what the exception was.
1672334,2017-03-16 09:11:58 UTC,"Change abandoned by zhubingbing (zhu.bingbing@99cloud.net) on branch: master
Review: https://review.openstack.org/444807"
1672334,2017-06-08 13:50:34 UTC,Removing kolla newton as possible backport since this change is not a security fix
1672334,2017-06-08 13:48:42 UTC,Fixed by https://review.openstack.org/#/c/447359/ and bug https://bugs.launchpad.net/kolla-ansible/+bug/1674207
1672335,2017-03-13 11:05:25 UTC,"There's a chance XMir plays a role in this, too."
1672335,2018-07-19 11:42:00 UTC,"Hello Dave,
Thank you for submitting this bug and reporting a problem with screen layout in Ubuntu.  You made this bug report some time ago and Ubuntu has been updated since then."
1672335,2018-09-18 04:17:37 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1672335,2018-09-18 04:17:39 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1672336,2017-03-13 10:50:03 UTC,"Thank you for help, I repeat I'll check again more carefully what happens after a new booting of the O.S. just installed (release 16.04)"
1672337,2017-03-31 01:11:12 UTC,This bug was fixed in the package qtmir - 0.5.1+17.04.20170328-0ubuntu1
1672337,2017-03-24 18:46:49 UTC,"Looking at the logs, when the top-level surface is minimized its child still keeps focused and in the same state. Not sure if the child should also go to minimized state (probably yes) but I'm sure it should not be kept focused."
1672337,2017-03-31 06:48:52 UTC,Is there work in miral needed still?
1672340,2017-03-13 14:30:45 UTC,"Hi Jakub,"
1672340,2017-04-27 05:08:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/460394"
1672340,2017-04-27 05:08:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/460395"
1672340,2017-04-27 05:25:13 UTC,"Hi Jakub,"
1672340,2017-04-27 06:08:06 UTC,"Hi Iwamoto, I think if we plan to deprecate of_interface it would be a useless effort to make ovs firewall working with both interfaces. What you have seems good and reasonable to me :)"
1672340,2017-07-27 06:45:15 UTC,"Reviewed:  https://review.openstack.org/460394
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3f4bceecaa67a1f20c7ec6243d0c883ff815f531
Submitter: Jenkins
Branch:    master"
1672340,2018-08-31 07:41:37 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1672340,2018-08-31 07:41:48 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/460395
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1672340,2017-03-13 14:49:38 UTC,"Hi Anindita,"
1672340,2019-04-16 08:52:14 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/460395
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1672340,2019-04-16 08:52:04 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1672340,2019-12-04 08:52:34 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1672340,2019-12-04 08:52:43 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/460395
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1672342,2017-03-13 11:46:37 UTC,It should be mentioned that cluster died after Docker restart on all nodes.
1672342,2017-03-14 11:08:38 UTC,Yes. Docker was restarted node by node
1672346,2018-03-01 14:30:58 UTC,"Chris, thanks for the context, especially the other bug.  Now that I understand that that file is all views, I can see the logic in not creating an upgrade script, but we do need some other mechanism then to keep folks at least aware of changes.  This would have similarities to the latent plans to improve in-DB function changes by reapplying those en masse at upgrade time (or whenever needed)."
1672346,2018-03-01 11:34:09 UTC,"Dan,"
1672346,2020-09-23 19:07:13 UTC,"I have tested this code and consent to signing off on it with my name, rfrasur and my email address, <email address hidden>."
1672346,2017-10-08 02:53:31 UTC,Sorry for the delay.  Branch here:
1672346,2017-07-14 19:01:49 UTC,"Chris, are you still working on this?"
1672346,2018-03-01 00:16:33 UTC,"Gave this a quick look, and just noting the provided branch still needs an upgrade script."
1672348,2017-03-13 15:00:19 UTC,"ok, so looks like i didn't have fonts-emojione installed
apt install fonts-emojione
much better now"
1672352,2019-07-08 23:11:39 UTC,This must have been fixed as part of some work since I cannot no longer reproduce locally under stress.
1672370,2017-03-24 20:35:23 UTC,Discussed in standup that this will be for a future cycle.
1672370,2019-09-19 12:03:06 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1672390,2019-07-08 23:15:52 UTC,"Presence is the area that has received a lot of attention since this report was first filed. The test, that is now named TestTwoModels, no longer fails intermittently, not even under stress."
1672391,2019-07-09 00:00:58 UTC,This must have been fixed as part of other work as I can not make the test fail locally under stress.
1672392,2017-03-13 14:28:33 UTC,u-a-l doesn't emit the required signals yet.
1672392,2017-03-13 14:35:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672392,2017-03-31 18:47:06 UTC,"Bumped milestone as its a major usability issue, in case it can land"
1672392,2017-04-06 17:59:23 UTC,This bug was fixed in the package ubuntu-app-launch - 0.12+17.04.20170404.2-0ubuntu1
1672394,2017-03-14 01:50:20 UTC,Please attach your ~/.cache/upstart/unity8.log from right after the crash occurred.
1672394,2017-05-13 04:18:04 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1672398,2017-03-13 14:28:30 UTC,"I think the problem is in the app, in touch mode it doesn't give focus to the console to not trigger the OSK straight away."
1672398,2017-03-13 14:18:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672398,2017-03-13 18:44:27 UTC,Quite annoying
1672401,2017-03-14 01:47:10 UTC,"""several seconds"" isn't 25 seconds is it? A fix for that long login delay landed in the past few days."
1672401,2017-11-03 16:30:51 UTC,Syncing task from Mir.
1672401,2017-03-30 02:34:26 UTC,"As a prerequisite to removing Mir's initial black frame, we would want to modify mir-demos to ensure they (the demo servers) actively paint something on start-up. Otherwise you get the situation where you're looking at an old frame (VT?) indefinitely until a client is started."
1672401,2017-03-15 03:06:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672401,2017-03-30 02:30:52 UTC,"I was thinking about this bug last night. It occurred to me the black screen is probably Mir's mesa-kms driver's first frame that it flips on start-up. As far as Mir is concerned this is a very low-severity issue since the shell should then render a proper frame 16ms later. However since Unity8 is taking several seconds to render a ""proper"" frame perhaps we need to change the start-up order..."
1672401,2017-03-14 09:37:42 UTC,I'm not convinced this is a duplicate of that other bug. It takes about 13 seconds for the login here. Which is not the 25 second DBus timeout you mention.
1672401,2017-03-14 09:36:32 UTC,"I'm calling this a dupe of the DBus timeout, just tried here and when you log in, the greeter stays on screen for maybe 4s, then unity8 is shown within a second."
1672401,2017-03-14 09:29:48 UTC,Just to be clear. I don't expect the login to be instantaneous - it never will be on a slow machine. It just looks bad for the screen to be black for the whole process.
1672401,2017-03-14 01:48:07 UTC,Please attach your ~/.cache/upstart/unity8.log from immediately after login completes.
1672401,2017-03-15 03:04:28 UTC,"OK, I see a couple of seconds of blackness on a Xeon desktop still (even after the dbus fix landed) so it's easy to extrapolate that a VM will have even more noticeable blackness."
1672401,2017-03-29 14:02:30 UTC,"@saviq: I'm not convinced the unity8-greeter should be the ""real"" login experience for unity8 on classic."
1672407,2017-10-13 19:19:11 UTC,Fix here: https://github.com/snapcore/snapcraft/pull/1618
1672407,2017-10-13 21:05:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672414,2019-08-28 17:30:29 UTC,Closing this as MAAS 2.5+ has CentOS/RHEL storage support.
1672414,2017-06-27 12:40:11 UTC,Using CentOS7.3
1672414,2018-04-04 00:40:00 UTC,Please either allow either:
1672415,2017-03-13 14:46:03 UTC,"Not sure if this applies to one or both projects, so I added both.  I have a feeling this is best fixed in the resource job to just avoid generating these at all, but it may be necessary to adjust the network script as well."
1672415,2018-01-30 13:31:46 UTC,A follow-up of https://bugs.launchpad.net/checkbox-support/+bug/1308702 ?
1672419,2017-03-14 09:38:45 UTC,"Confirmed, apart from that we should probably be using the Levenshtein distance here, to permit typos."
1672422,2020-03-17 20:29:27 UTC,"We need this. Not only for reverse engineering and archeological preservation, but also for simply drawing/estimating PCB size for incomplete mechanical drawings like these: https://evatron.com/wp-content/uploads/evatron_tech_RX2008.png)"
1672422,2019-10-12 14:21:51 UTC,You should be able to use the bitmap2component and get that graphic onto the eco layers and get a similar effect for the time being.
1672422,2019-09-28 17:13:41 UTC,"Yes, agreed. This would be a great feature for reverse engineering old/retro computer PCBs and related electronics."
1672422,2020-04-07 15:27:20 UTC,"KiCad has migrated to Gitlab, this issue is available here: https://gitlab.com/kicad/code/kicad/-/issues/2054"
1672422,2019-07-11 19:55:33 UTC,Images can't go on pcbnew layers as we currently define them to be physical objects on a board (which an image isn't)
1672422,2019-07-11 15:20:12 UTC,"Maybe instead of adding a ""background"" image, this image could be loaded in it's own ""layer""? This would also allow quickly switching between layers (back/front) or multiple pictures."
1672422,2018-12-27 22:28:41 UTC,this will sure help people keep old electronics alive
1672422,2019-07-11 20:34:37 UTC,"Yes please!
I think that would fit our needs..."
1672426,2017-03-14 08:13:47 UTC,"Hi Max, thanks a lot for your report."
1672429,2017-03-13 15:43:36 UTC,"Nothing to do with LXD, targeting to nova-lxd."
1672429,2017-03-24 11:10:01 UTC,"As the nova-lxd driver is largely untested with anything other than ML2/OVS, I'd not be surprised if this does not work in the context of Calico."
1672429,2017-03-24 11:12:47 UTC,That said we did get a contribution via tigera to support Calico:
1672429,2017-03-24 11:13:15 UTC,"Would it be possible for you to try to reproduce this with OpenStack >= Newton, rather than Mitaka which we know does not have this support."
1672429,2017-03-24 11:35:56 UTC,"Sorry James - this was fixed in 14.0.0 by the a patch from the calico guys.
I backpacked the patch to the 13.2 mitaka packages, and it works."
1672429,2017-03-24 11:37:46 UTC,For info:  http://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=c9b2950723e45850ba915f8b96389818177d41c7
1672429,2017-03-24 13:04:22 UTC,I'd be happy to consider including this fix into the stable/mitaka branch; we're still maintaining that atm as it was the first GA release so quite a few people are using it still.
1672429,2017-03-24 13:21:00 UTC,"For what it's worth, here's the debian patch I've applied."
1672431,2017-03-13 15:36:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/444953"
1672431,2017-06-04 15:03:20 UTC,"Reviewed:  https://review.openstack.org/444953
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=de31cdc77b9f339f2876df2864503f9b708d4b7d
Submitter: Jenkins
Branch:    master"
1672431,2017-06-09 15:29:59 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.
1672433,2017-03-14 11:03:19 UTC,"Just in case, I think linux behavior here is not correct, I send bug to the Kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=194879"
1672433,2017-12-22 08:19:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529807"
1672433,2018-08-31 07:44:59 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1672433,2018-08-31 07:45:09 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/529807
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1672434,2017-03-15 13:10:18 UTC,"Adding a note that sample actor.usr records also need to be part of this discussion as the same problem occurs when they are added to the test dataset. At this time, there only appears to be one PgTAP live test that depends on this data, but this may change over time."
1672434,2017-04-06 17:20:25 UTC,"To summarize the idea I mentioned during the hackfest, we could consider adjusting the test bib data so that biblio.record_entry.last_xact_id is used (abused?) as a stable identifier for sample bib record.  Each distinct file of bib records could have last_xact_id set to a per-file prefix + a sequentially-assigned number; e.g., 'concerto-1', 'concert-2'. last_xact_id would then be used for the purpose of"
1672438,2017-04-27 06:22:52 UTC,"Fine for me. Maybe we should also update the release docs - after creating the new stable branch, such a commit should be made (if the base project already branched out). But let's make this a separate patch..."
1672438,2017-04-28 15:00:52 UTC,"Reviewed:  https://review.openstack.org/460413
Committed: https://git.openstack.org/cgit/openstack/nova-dpm/commit/?id=a77c6cc800cb79705f07a2950ee68c8b05567053
Submitter: Jenkins
Branch:    stable/ocata"
1672438,2017-04-27 06:34:58 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/460413"
1672438,2017-04-27 05:27:24 UTC,"nova-powervm did in this way
https://github.com/openstack/nova-powervm/blob/stable/ocata/tox.ini#L14"
1672438,2017-04-26 09:43:59 UTC,"The point is, that [1] clones nova master. But for our stable/ocata branch it should clone nova stable/ocata - but it still clones master [2]."
1672438,2017-03-13 16:02:17 UTC,Due to that the following patch fails in networking-dpm: https://review.openstack.org/#/c/443829/
1672438,2017-03-13 16:41:06 UTC,Lowering prio for Neutron as stable/ocata is fixed - however it would be great to come to a general solution where no manual interactions are required....
1672438,2017-03-13 16:32:10 UTC,"Reviewed:  https://review.openstack.org/444960
Committed: https://git.openstack.org/cgit/openstack/networking-dpm/commit/?id=433e44d7cccc494609995ad606ea36718afd0e86
Submitter: Jenkins
Branch:    stable/ocata"
1672438,2017-03-13 15:57:22 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/444960"
1672438,2017-04-26 06:26:56 UTC,Andreas
1672441,2017-04-12 19:47:48 UTC,"I ran into this with the ISO 20170412 spin on both
 - amd64 on a Dell Latitude E6420: Intel i5 2540M   +  Intel Sandybridge Mobile graphics and
 - i386  on a Dell Latitude D630:  Intel Core 2 Duo +  Intel 965GM graphicsc"
1672441,2017-04-13 08:29:11 UTC,This is a recurring issue that gets solved breaks and solved and breaks and ....
1672441,2017-04-12 20:05:12 UTC,This is probably a duplicate of bug 966480. I believe it is a long-standing issue and not new to Ubuntu 17.04. It's been part of the Ubuntu GNOME Release Notes for multiple releases in a row now.
1672441,2017-03-29 16:39:23 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1672441,2017-07-26 19:22:40 UTC,"Just seen this during an Autoresize install test for Artful, But in a subsequent installation on the same hardware the bug did not occur. I think this might be due to a timing issue: on the first test I wasn't watching the machine closely so the ""Installation Complete"" dialog stayed on for a while without anything happening. On the second install I passed that dialog quickly."
1672441,2017-03-15 01:43:39 UTC,"I can't reproduce this at all on my hardware. Are there any common details about where this is reproducible? All on VMs, or all on a particular video hardware that might not be Intel?"
1672441,2017-03-14 12:30:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672441,2017-03-13 20:53:10 UTC,Tried 3 times to replicate this with Xubuntu - other than once instance of it being a bit 'slow' to get to the remove and hit enter dialogue - all worked as expected.
1672441,2017-03-21 11:22:01 UTC,Issue Occurs on XPS13 reliably it happens on kvm with ovmf and secureboot enabled (not sure if that is the difference) Will try on i386 later today again.
1672442,2017-03-13 16:08:54 UTC,Log file
1672442,2017-03-13 17:23:28 UTC,"To be specific: I don't really know if the combined throttle / train break is the reason, but I guess it. I just can't get the train to drive, but in MSTS it is working."
1672442,2017-03-14 14:23:25 UTC,"I could not find a package from Open Rails in Ubuntu. If you know one, please mark it via ""Also affects distribution/package""."
1672444,2017-03-29 09:49:33 UTC,"I think I remember seeing this once, although I haven’t been able to reproduce either.
Let’s keep the bug open for now."
1672444,2017-03-29 14:16:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672444,2017-03-30 15:03:49 UTC,"yes, it's easy to reproduce, just resize the window a couple of times (make it as small as you can and then large), it's the same with ubuntu-terminal-app"
1672444,2017-03-30 15:04:58 UTC,"screenshot attached, i can reproduce it every time"
1672444,2017-03-30 15:16:42 UTC,"Indeed I can reproduce by resizing the window to its minimum width then back to its original width.
Thanks dinamic for the tip!"
1672444,2017-03-30 19:14:25 UTC,"Oh, cool. Thanks, dinamic!"
1672455,2017-03-14 18:34:33 UTC,"Running apport-collect 1672455 doesn't make any sense, since the ppa-webserver is of concern here."
1672455,2017-03-14 18:34:08 UTC,"Running apport-collect 1672455 doesn't make any sense, since the ppa-webserver is of concern here."
1672455,2017-03-13 20:34:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1672455,2017-03-14 18:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1672459,2019-07-21 12:04:10 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1672459,2019-07-21 16:04:01 UTC,"On 07/21/2019 07:04 AM, Paul White wrote:

> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
>
> Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
>
> Do you still see a problem related to the one that you reported when
> using a currently supported version of Ubuntu? Please let us know if you
> do otherwise this report can be left to expire in approximately 60 days
> time.
>
>


WOW, I don't even remember reporting this bug! The link I
gave in the bug report doesn't work anymore, but if you
enter FODM121 in the search box and then click on the pdf
link that comes up, it STILL does the same thing, on evince
3.4.0
And, it may just be a badly formatted document, too.  The
URL is :
https://www.onsemi.com/pub/Collateral/FODM2705-D.pdf"
1672459,2019-07-22 12:10:31 UTC,Thanks for the reply.
1672459,2019-07-22 15:54:30 UTC,"On 07/22/2019 07:10 AM, Paul White wrote:

> I cannot reproduce the problem using either evince 3.28 in Xubuntu
> 18.04, or evince 3.32 in Ubuntu 19.10 (dev). I've also viewed the same
> file downloaded from other sources. There have been several reports of
> this problem in the past but they seem to have been fixed before this
> bug report was raised.
>


OK, that is fine.  Eventually, this system will get creaky
enough that I will have to update.
Just a case of inertia!"
1672465,2018-12-05 13:10:05 UTC,"I don't know if I'm running Wayland, but it is the most recent version of Kubuntu as it comes out of the box.  Unfortunately Onboard crashes the entire desktop.  If you try to type one Onboard french character, the desktop turns black and you eventually are brought to the login screen and have to login with a password.  I hope this can be fixed as Onboard is very important to me."
1672465,2017-08-20 11:01:39 UTC,"> We'll very likely make the 18.10 release
I meant to write:
We'll very likely make the 18.04 release
"
1672465,2017-08-20 10:43:22 UTC,Let me give you an update on the current state of Onboard in gnome-shell.
1672465,2017-07-05 10:20:30 UTC,"Personally, I would vote for Onboard to be integrated into GNOME upstream instead of Caribou."
1672465,2017-07-05 09:28:45 UTC,"> Did anyone try to replace caribou with onboard in gnome-shell, is that doable/easy?
I did, and came to the conclusion that fully replacing caribou with the existing Onboard is close to impossible. That's mainly because applications don't have access to the activities and authentication views. Can't search applications or enter passwords with Onboard. In Wayland there was the additional problem of gdk_wayland_window_set_accept_focus not being implemented and Onboard uselessly sending key-strokes to itself.
"
1672465,2017-04-11 21:35:19 UTC,There is some interest from Canonical in making GNOME on Wayland the default for 18.04 LTS but there will need to more investigation of what won't work right if that happens.
1672465,2017-07-04 14:45:32 UTC,Could somebody from the onboard team gives a status update there of how onboard work with gnome-shell and under wayland?
1672465,2017-04-12 07:17:01 UTC,"Yes, thanks for the reminder, we heard the news and already shifted focus to GNOME Shell. I think we can be ready in time for 18.04 LTS, I'm actually cautiously aiming for 17.10."
1672465,2017-04-11 21:33:48 UTC,Have you tried talking to GNOME Shell developers directly about this or other Onboard integration issues?
1672465,2017-03-15 02:50:37 UTC,"Yes, that's still an open issue. The last I wrote about it was here:
https://bugs.launchpad.net/onboard/+bug/1366421/comments/22"
1672465,2017-07-04 20:00:03 UTC,"Hi Sebastien,"
1672467,2018-06-28 12:04:12 UTC,"Change abandoned by Alistair Coles (<email address hidden>) on branch: master
Review: https://review.openstack.org/445033"
1672467,2017-03-13 17:59:32 UTC,https://review.openstack.org/445033 fixes and the test therein illustrates the inconsistency when run against master
1672469,2017-03-20 19:00:57 UTC,You'll want to sort out why those packages are unauthenticated.
1672469,2017-03-20 19:00:14 UTC,"From the log file:
ERROR:root:failed to mark 'ubuntu-desktop' for install (E:Unable to correct problems, you have held broken packages.)
ERROR:root:Unauthenticated packages found: 'aptdaemon gir1.2-packagekitglib-1.0 libpackagekit-glib2-18 libqt4-dbus libqt4-declarative libqt4-network libqt4-opengl libqt4-script libqt4-sql libqt4-sql-sqlite libqt4-xml libqt4-xmlpatterns libqt5core5a libqt5dbus5 libqt5gui5 libqt5multimedia5 libqt5network5 libqt5opengl5 libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5quicktest5 libqt5sql5 libqt5sql5-sqlite libqt5svg5 libqt5test5 libqt5webkit5 libqt5widgets5 libqt5xml5 libqtcore4 libqtdbus4 libqtgui4 python3-aptdaemon python3-aptdaemon.gtk3widgets qdbus qml-module-qtgraphicaleffects qml-module-qtquick-window2 qml-module-qtquick2 qml-module-qttest qmlscene qtchooser qtdeclarative5-dev-tools'"
1672484,2017-03-28 06:17:44 UTC,I don't think it's a bug. You need to decode it.
1672484,2017-03-29 20:53:14 UTC,Please consider this as an enhancement request : to honor this standard HTTP header (Accept/Accept-Charset) as is commonly honored by other applications
1672497,2017-03-22 19:14:28 UTC,"Hi Dmitry. Please provide more context as to where this bug can be found. Also, please utilize the bug reporting template. The more information you provide, the easier it is for the documentation team to help. Links to the content would be a first step."
1672497,2017-03-23 01:16:35 UTC,"page - https://docs.openstack.org/mitaka/config-reference/compute/config-options.html
row with ""images_type = default"""
1672497,2017-05-14 01:14:41 UTC,This line can be filled in with a good description: https://github.com/openstack/nova/blob/ef2203f36fc0bde2635e0d1f39a4b8dce5654ffb/nova/conf/libvirt.py#L635
1672497,2017-05-14 15:23:24 UTC,"Whoops, I mean line 615 not 635 in my comment above."
1672497,2017-09-22 03:49:04 UTC,Means in description field of images_type need to add this choices only?
1672497,2019-05-07 01:45:51 UTC,out of support
1672501,2017-03-13 19:57:04 UTC,"As of now I couldn't find any assertion that provide this, I am therefore updating the default & hiding the line if nothing meaningful is returned by the go side,"
1672514,2017-03-13 19:52:30 UTC,From lspci:
1672521,2017-03-14 18:19:09 UTC,"Hi,
I tried out 4.11-rc1 a few days ago. Unfortunately, I did not get the board to boot properly from the start, since ThunderX networking drivers failed to allocate MSI-X/MSI interrupts, and polling on some registers also failed ..."
1672521,2017-03-14 19:19:39 UTC,"Hi,"
1672521,2017-03-14 19:29:42 UTC,"Just one addition, the log before contains dmesg output too. The task that hanged was systemd, it might be related with some VMs from the previous boot record being restarted automatically, but it still doesn't explain the crash."
1672521,2017-07-26 15:23:12 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1672521,2017-03-21 21:48:10 UTC,"Hi, Dann,
First of all, I think the bug title is misleading, as this issue happens on all kernels we tested (4.4.0-45..66, 4.8.0-x, 4.10.0-x etc)."
1672521,2017-03-14 18:03:17 UTC,"If the mainline kernel still exhibits the bug, we can perform a kernel bisect to identify what commit introduced the regression."
1672521,2017-03-14 19:50:34 UTC,"4.11-rc1 console log attached.
Board firmware is latest available on Gigabyte's site (T31)."
1672521,2017-03-14 18:02:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1672521,2017-03-21 17:18:08 UTC,"@Alexandru: do you have a console log of a system hitting the issue w/ the VM use case? Soft lockups are a fairly generic failure mode, and it would not surprise me if stress-ng was triggering a different issue than the VM case, but both emitting soft lockups."
1672521,2017-03-13 20:22:13 UTC,apport information
1672521,2017-03-13 20:30:12 UTC,This change was made by a bot.
1672521,2017-03-13 20:21:55 UTC,apport information
1672521,2017-03-13 20:21:58 UTC,apport information
1672521,2017-03-13 20:22:01 UTC,apport information
1672521,2017-03-13 20:21:57 UTC,apport information
1672521,2017-03-13 20:22:05 UTC,apport information
1672521,2017-03-13 20:22:06 UTC,apport information
1672521,2017-03-13 20:22:08 UTC,apport information
1672521,2017-03-13 20:22:11 UTC,apport information
1672521,2017-03-13 20:22:03 UTC,apport information
1672528,2017-03-13 21:30:40 UTC,"After manually remove with:
click uninstall --all-users com.U.ubuntu.telegram
And remove settings folder in /userdata/user-data/phablet/.config/com.ubuntu.telegram."
1672541,2018-06-17 22:40:14 UTC,pypolicyd-spf is in maintenance only mode.  Transferring to spf-engine for future consideration.
1672545,2017-04-21 08:14:43 UTC,"On Thu, Apr 20, 2017 at 05:52:21PM -0000, Balint Reczey wrote:

> Having PTS and tracker in Debian helps greatly in getting an overview
> per source package, but are not, and I think can't really be used for
> visualizing queues, like the migration queue.
>
> update_excuses.yaml can already be useful for example I used it to
> create re-run links for failed autopkgtests due to missing versioned
> dependencies [1], but making such features globally available would be
> better than running private helper scripts.
>
> [1] http://pastebin.ubuntu.com/24356986/
"
1672545,2017-04-20 17:52:21 UTC,"Having PTS and tracker in Debian helps greatly in getting an overview per source package, but are not, and I think can't really be used for visualizing queues, like the migration queue."
1672545,2017-04-18 11:31:26 UTC,"On Tue, Apr 18, 2017 at 11:11:18AM -0000, Balint Reczey wrote:

> What I'm aiming at is having fewer packages stuck in migration but with
> more helpful information available for unblocking them.
"
1672545,2017-04-18 11:11:18 UTC,What I'm aiming at is having fewer packages stuck in migration but with more helpful information available for unblocking them.
1672545,2017-04-18 11:02:10 UTC,"I think showing ""ftbfs"" bugs could be beneficial for Debian as well thus it does not have to be part of the delta. Debian's script would collect the FTBFS buts from Debian's BTS, that is not a huge difference IMO."
1672545,2017-04-18 10:31:27 UTC,I'm a bit worried about maintaining extra code in (makes rebasing harder) and around (needs to be maintained) proposed-migration.
1672545,2017-04-18 10:09:34 UTC,"One improvement in this case would be automatically listing bugs with ""ftbfs"" tag on update_excuses."
1672545,2017-03-13 21:25:40 UTC,"Attached screenshot of the orthanc-webviewer containing ""Note: Some binary packages for this source are not yet published in the repository."" and ""Pending publication"" messages."
1672545,2017-03-13 21:23:52 UTC,"Attached screenshot of the ""has no binaries on any arch"" from update_excuses."
1672545,2017-04-18 11:09:11 UTC,"A good example of collecting the ""ftbfs"" bugs is here:
http://qa.ubuntuwire.org/ftbfs/"
1672552,2020-09-05 21:01:59 UTC,"+1 Google File Stream was the issue on my PC.  I uninstalled and it worked.  Thanks for posting this, it was the only place I found that had this discussion regarding veracrypt and Google File Strea."
1672552,2020-06-28 12:30:02 UTC,"Same problem here - the cause was ""Google File Stream"" that mounts your Google Drive as a ""physical drive"" into the explorer."
1672552,2020-04-19 12:14:48 UTC,Same problem here with VeraCrypt!
1672552,2020-01-14 03:37:04 UTC,"I am experiencing the exact same behavior. Win32DiskImager doesn't start properly (no gui) when I have a VeraCrypt volume mounted. With no VeraCrypt volumes mounted, it seems to work normally. Any more ideas why this would be? It's a bit annoying. Anyway, thanks for discovering this incompatibility."
1672552,2020-01-10 02:25:36 UTC,I just installed Win32DiskImager on my Windows 10 machine.
1672552,2018-09-04 18:33:24 UTC,"The problem is understood and has been fully debugged.  I jut haven't had time to work on this project in a while, but will before the end of the year (fingers crossed)."
1672552,2018-09-04 17:53:12 UTC,I had the same issue.
1672552,2019-08-08 10:36:13 UTC,"Check if you have done any recent change like installed new apps then uninstall it. Despite, this also update the drivers installed in your system.
Source: http://www.pcerror-fix.com/how-to-repair-ntdll-dll-error-messages-in-windows-8-1"
1672552,2017-05-07 17:44:44 UTC,"I am seeing the same behavior, it starts, but crashes.  Event log entry:"
1672552,2017-08-08 22:23:38 UTC,"Is this by any chance related to other issues people are seeing, like ramdisk or other drive letters assigned?  I think I may have found the issue, but not sure based on the information here.  If you are running a ramdisk, or mapping a drive letter to something other than basic drives, this may be the issue."
1672552,2017-03-14 00:45:45 UTC,"Can you give me some more details?  Here are a few things to try:
1. Make sure it tries to run in Administrator Mode only.
2. Open a command prompt (Windows key/Start menu, search for cmd, right click and Run as Administrator then ce to the installation directory (C:\Program Files (x86)\Image Writer and run Win32DiskImager.exe and see what errors it gives you."
1672552,2017-03-14 02:07:40 UTC,"Steps:
1. Installed v1.0.0.0 using installer
2. Started elevated cmd.exe (as Administrator)
3. Launched Win32DiskImager.exe"
1672552,2017-03-14 17:38:22 UTC,"It sounds like you are missing a MSFT runtime library.  I have tested this on several fresh installs of Windows 10 Premium, no issues."
1672552,2017-03-14 18:21:17 UTC,"Can you also read this forum message and follow to see if this may be the issue?
https://windowsforum.com/threads/how-to-fix-msvcp110-dll-is-missing-in-windows-10.212064/"
1672552,2017-04-02 22:39:08 UTC,Using: Windows version 1607 (14393.953)
1672552,2017-04-02 22:40:17 UTC,"Well, obviously the source code is available. Ignore that part."
1672552,2017-04-03 23:41:50 UTC,Heh.  Consider it ignored.  :P
1672552,2017-03-23 18:41:49 UTC,"Another thing to try, check out this list of possible issues:  http://windowsreport.com/windows-10-apps-wont-open/.  See if any of that helps and please update your results here.  Thanks."
1672562,2017-03-17 18:33:18 UTC,"This turned out to be a problem with the user not being in the audio and pulse-access groups. Also  the back panel speaker out only has one channel working, however the front panel headphone connector works fine. So I just use the front panel headphone jack."
1672563,2017-03-13 23:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1672563,2017-03-14 17:15:03 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1672563,2017-03-15 04:58:34 UTC,"Does kernel parameter ""acpi_rev_override"" work?"
1672563,2017-03-16 20:55:57 UTC,no..it doesn't work :/
1672563,2017-03-26 05:30:02 UTC,"any new idea...?
please help me..."
1672563,2017-03-26 06:34:38 UTC,At what stage you installed your nvidia driver?
1672563,2017-03-26 08:11:38 UTC,i'm not sure after setting acpi_rev_override or before...does it differ?
1672563,2017-03-14 20:54:09 UTC,"Thanks for your help. I tested v4.11 kernel and it didn't help
actually in 16.04 there wasn't any prior kernel which works well. at least i havn't seen.
but I already use ubuntu 14.04 with kernel 4.2.0-42-generic, and it works well without setting any 'nomodeset' or 'acpi=off'!"
1672565,2017-03-14 16:29:10 UTC,Are you talking about this template? [1]
1672565,2017-08-29 13:57:42 UTC,See related bug #1713663.
1672569,2017-03-14 00:12:50 UTC,"My bad for the bug report, I noticed the other ones just now. I initially searched in another bugtracker (Ubuntu-terminator?) and just realized now..."
1672585,2020-03-23 17:38:08 UTC,"This issue is still observed in Ubuntu 18.04 LTS at least, while not present in any Debian version tested."
1672587,2017-03-14 21:24:00 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1672592,2017-04-19 17:05:32 UTC,"IIANM Nova does not require is_public parameter to get private flavors. But this parameter is exists for admin purposes, i.e. only admin can specify it, to get all flavors within all project, not only current admin's one."
1672598,2017-03-14 13:16:08 UTC,Can't reproduce with 0.92.1 on Linux. I successfully exported a 3.8M world map (https://goo.gl/C3o5Ly) at 300DPI. Make sure the width is updated before you click 'Export'. 12 x 12 is absolutely wrong.
1672598,2017-03-15 02:35:45 UTC,"For the document units and snap settings, you could create a custom template."
1672598,2017-03-15 03:06:28 UTC,"No problem here exporting a 17MB bitmap @ 1200dpi. Win8.1, 0.92.1"
1672598,2017-03-15 10:46:59 UTC,@Rosemary: Any chance you could attach an SVG file that does not export properly for you (plus the export settings chosen)?
1672598,2017-06-15 13:50:04 UTC,"Same Problem with .svg to .pdf export, .svg attached
Who killed the bird? :-)"
1672598,2017-06-15 19:21:53 UTC,"@twosnitza - it seems that the problem you are having with the pdf output is not related to the original bug report. It is somehow related to the presence of clip paths and masks in the image.
When I edit the svg file to remove the one clip path and also the mask, I get the attached svg file, which will show the bird image if you save it as pdf."
1672602,2017-05-31 17:11:32 UTC,"Got a slightly different traceback, but can confirm:"
1672602,2017-06-07 11:58:23 UTC,Updated: https://review.openstack.org/#/c/471416/
1672602,2019-09-17 14:57:08 UTC,We have removed support for this tool in favour of the oslo.config sphinx extensions. Closing this as wontfix.
1672604,2017-03-26 06:40:15 UTC,Looks like it's been like this since at least Juno
1672604,2017-03-14 16:17:22 UTC,On master.
1672604,2017-03-14 16:26:43 UTC,Confirmed - from an AIO inventory right now:
1672604,2017-03-14 17:46:30 UTC,I was expecting the children of compute-infra_containers to be all the groups under the container_skel that say belongs_to compute-infra_containers.
1672605,2017-05-31 17:17:01 UTC,"For me, it fails due to a missing openstack.common.apiclient, but can confirm it's broken."
1672607,2017-03-14 04:41:39 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22AttributeError%3A%20'NoneType'%20object%20has%20no%20attribute%20'splitlines'%5C%22
1672607,2017-11-04 23:02:32 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/482996
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1672607,2017-07-12 15:01:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/482996"
1672607,2017-04-26 20:39:43 UTC,The bug is to make the code failing more gracefully on a similar ovs crash.
1672607,2017-03-14 04:41:31 UTC,7 hits in 7 days.
1672607,2017-03-14 04:48:40 UTC,The segfault is tracked in https://bugs.launchpad.net/neutron/+bug/1669900
1672607,2017-03-14 04:45:10 UTC,The root cause is a segmentation fault in ovs itself:
1672607,2017-04-26 20:39:17 UTC,"The segfault is tracked in other place, removing gate-failure tag."
1672610,2017-03-14 05:44:00 UTC,somewhat related bugs:
1672610,2017-11-04 23:03:27 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/445308
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1672610,2017-03-14 05:55:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445308"
1672613,2020-04-02 12:27:23 UTC,Part of tempest since 20.0.0 release.
1672613,2017-03-14 06:00:23 UTC,"In https://docs.openstack.org/developer/swift/overview_acl.html
'Note Keystone project (tenant) or user names (i.e., <project-name>:<user-name) must no longer be used because with the introduction of domains in Keystone, names are not globally unique. You should use user and project ids instead.'"
1672613,2017-09-12 10:31:19 UTC,"Change abandoned by Eric Xie (eric_xiett@163.com) on branch: master
Review: https://review.openstack.org/445358"
1672613,2018-10-11 06:21:24 UTC,"Hi Eric,"
1672613,2018-12-06 09:34:19 UTC,This seems fixed by https://review.openstack.org/#/c/605017/1
1672613,2019-08-02 01:08:28 UTC,should this be changed to fix released?
1672613,2017-03-14 08:31:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445358"
1672619,2017-05-26 09:55:26 UTC,"I try to have good touchpad experience when enable ""tap to click"".
Here is my properties that I feel the touchpad would not annoy me when I typping."
1672619,2017-06-27 18:09:06 UTC,"Peter, what is the best way to distinguish (in the code) whether a touchpad is external or not?"
1672619,2017-06-27 05:41:12 UTC,The attached file is the xinput output of XPS13.
1672619,2017-06-26 15:02:47 UTC,"YC, can you post the output from xinput?"
1672619,2017-06-22 23:24:42 UTC,"No, sorry. That's simply not good enough, if we have to change the code anyway we might as well try to make it work properly instead of hoping that it maybe works. There's no guarantee about the device node ordering and just because that's current kernel behaviour doesn't mean we should rely on it."
1672619,2017-06-22 21:58:23 UTC,"Yeah, I see on 1.9 that the max touches doesn't show up for this TP."
1672619,2017-06-22 03:22:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672619,2017-06-20 22:49:25 UTC,"synaptics 1.8 I suspect, it was dropped with 1.9 which has been out since november"
1672619,2017-06-20 16:19:45 UTC,Oh where did that max touches information come from in the --long output (see attachment)?
1672619,2017-06-20 00:07:55 UTC,"Mario: the synaptics driver doesn't export the number of touches, so that's a no-go. It'll have to be heuristics or a user-supplied argument."
1672619,2017-06-19 13:10:06 UTC,"@Peter:
Yeah an xorg.conf.d snippet can workaround and ignore the PS/2 device, but it's not a very general solution."
1672619,2017-06-19 07:36:24 UTC,"I think most Dell laptops are using hid-rmi, not SMBus.
And there is currently no way from i2c-hid to remove the PS/2 node. I don't see any simple way to achieve that, so I think we will have to deal with it in user space."
1672619,2017-06-18 22:30:29 UTC,"Quick workaround here would be to add an xorg.conf snippet to ignore the mute serial device. Unless you're rebuilding kernels a lot and expect the i2c driver to fail frequently, this won't be a problem otherwise."
1672619,2017-06-16 16:05:21 UTC,"Created attachment 132004
# xinput list --long"
1672619,2017-06-15 06:39:30 UTC,"More information:
The two touchpad input devices causes the ""disable 'tap to click' while typing"" function fail.
During booting, the psmouse will register a PS/2 touchpad input device and the hid-multitouch will register another i2c touchpad input device."
1672619,2017-05-31 07:16:08 UTC,"Another solution: disable the ""tap to click"" while typing.
On Xenial, this function should be enabled automatically.
But, when the machine have two touchpad devices, this function will fail."
1672619,2017-05-29 07:06:05 UTC,"Below is my conclusion after surveying the palm detect function on XPS13 9360.
The palm detect function is a hardware limitation in xserver-xorg-input-synaptic in XPS13 9360.
 The touchpad does not support ""pressure"" and ""finger width"" information.
 These two values are important information in palm detect function.
 Palm detect function would not detect a palm precisely without these values.
 In Xorg.0.log:
[     7.688] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: invalid pressure range.  defaulting to 0 - 255
[     7.688] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: invalid finger width range.  defaulting to 0 - 15"
1672619,2017-05-25 07:26:28 UTC,"Current investigation state:
The behavior of the BTN_TOOL_FINGER is correct. We should not ignore this event."
1672619,2017-05-24 08:07:08 UTC,"More information about the BTN_TOOL_FINGER event.
I found the BTN_TOOL_FINGER definition in https://www.kernel.org/doc/Documentation/input/event-codes.txt."
1672619,2017-05-24 07:29:07 UTC,"I tried the solution in the comment #4.
I feel it is not good enough.
I often lost my windows focus when my palm touched the touchpad."
1672619,2017-05-23 07:14:20 UTC,The attached file is the patch to ignore the BTN_TOOL_FINGER.
1672619,2017-05-23 06:51:59 UTC,I built a xserver-xorg-input-synaptics package for improving the user experience of the touchpad.
1672619,2017-04-19 17:53:01 UTC,/usr/share/X11/xorg.conf.d/50-synaptics.conf has this:
1672619,2017-04-19 17:35:10 UTC,This is indeed a quite annoying bug.  I've disabled the touchpad on my Dell XPS 13 9360 because it is way too sensitive and registering false clicks.
1672619,2017-03-14 06:41:05 UTC,"To clarify, I carried out the package install and didn't carry out the modification*"
1672619,2017-03-14 06:35:47 UTC,"Owning a XPS13 myself I have experienced this issue ""first hand"" and can confirm from making the change myself over the last 24 hours that the improvement is very noticeable."
1672619,2017-06-27 22:01:54 UTC,"dp_get_device() already does that, it checks for the XI_TOUCHPAD type and the ""Synaptics Off"" property. Look for the ""Yay, device is suitable"" comment, clearly there was some enthusiasm to spare when I wrote that code :)
That 'break' there is the first hurdle - because of it we don't look at anything but the first touchpad. Start there, and off into the rabbithole it goes..."
1672619,2018-08-10 20:59:49 UTC,-- GitLab Migration Automatic Message --
1672619,2018-12-05 11:02:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672620,2017-03-23 08:50:45 UTC,More clarity on use case
1672620,2017-03-23 08:53:46 UTC,"I had discusion with tempest guy, he suggested one of the approach is to run each tempest test case individsually and run pre and post hook scripts. It can have a huge maintaince cost, as more test cases get's added or some of them deleted etc, we have to keep track of all of them. For other approaches stay tuned for the updates on this bug :)"
1672620,2017-10-12 09:16:25 UTC,"yea from Tempest side, it is very costly to provide pre/post hook. To catch the info i feel debug logs should be there. is there any other information you want to capture than that can be presented in logs?"
1672620,2017-10-12 10:08:55 UTC,"Got to know we have pause cleanup feature
- second last bullet in New Features"
1672620,2017-10-12 10:15:43 UTC,If you are writing your own tests you can use setUp and tearDown to collect more information.
1672620,2019-08-02 00:49:49 UTC,If tempest logging is at debug level the restclient will log all api req- id an you can gather them and look at the server logs to see what is happening.  We have a subunit tool that gather them and creates an html report the link in to our kibana instance. Just a suggestion to help to debug when tempest test fails.
1672620,2020-10-05 09:41:48 UTC,removing assignee as there has been no activity for more than a year
1672620,2021-01-08 16:01:22 UTC,"This has been in Incomplete state for several years, it's time to mark this as Invalid."
1672622,2017-04-04 10:12:34 UTC,"Hey Eric, yes, I mean the exporting of the env var. I don't see any other reason why you may end up with nodes in enroll state."
1672622,2017-04-03 13:04:12 UTC,"Thanks vdrok, do you mean the IRONIC_API_VERSION environment not in local.conf file? I forgot whether i exported the environment or not. Maybe i will try next time."
1672622,2017-03-18 05:28:59 UTC,"Ramamani Yeleswarapu, thank you, I need to reproduce this to address it."
1672622,2017-03-14 23:38:38 UTC,"Tao Li, I see the same error. My local.conf is same as what's in the inspector docs."
1672622,2017-04-03 10:38:33 UTC,"Is it possible that you've set the IRONIC_API_VERSION environment varaible? If not, ironic client should default to version 1.9, which did not have enroll state yet."
1672624,2017-03-15 12:43:57 UTC,"To be clear, the issue here is that the domain is still active on the compute node and accessing the rbd volume so any attempt to delete the rbd volume itself fails."
1672624,2017-03-16 03:13:40 UTC,"This may also affect ""evacuate"" operation."
1672624,2017-03-15 17:36:43 UTC,"This behavior is expected in the scenario where nova-compute is brought down but the instance domain is still running and keeping the volume busy. Usually in practice, nova-compute should only be down in the case of a failed compute host or one that has been properly fenced by the operator. However, if nova-compute goes down temporarily and an instance is local deleted, the instance domain will be reaped by the nova-compute periodic task after nova-compute comes back up. After the domain is reaped, the volume can be successfully deleted from cinder."
1672624,2017-03-15 17:30:31 UTC,"Confirmed that the default cleanup periodic task in compute will destroy local deleted domains when nova-compute is brought back up. The default action is ""reap"" which will delete orphaned domains and the periodic task runs every 30 minutes by default. It doesn't run immediately when nova-compute starts, so it takes 30 minutes after nova-compute comes back up for the local deleted instance to be reaped."
1672624,2017-03-15 15:47:40 UTC,"Well, the operator hasn't done a local delete, they've just done a delete. Nova did a local delete because nova compute wasn't running. We also wouldn't want to fence in this case because, in general, we don't want to kill running instances unless we really have to. Nova compute being down isn't 'really have to' under most circumstances because it can just be restarted: an HA response should focus on trying to get it back up again. I don't think we can reasonably blame the operator here."
1672624,2017-03-15 07:24:20 UTC,LVM works well because  LVM removes export and remove the iscsi target by itself:
1672624,2017-03-14 14:05:21 UTC,"Add the cells tag, as the work has added lots of new code paths for local delete cases. Seeing errors around inconsistent handling of quotas, notifications and other things that hit this code path."
1672624,2017-03-15 04:49:22 UTC,"@melanie witt, Hi, thanks for the test, but I think you might not doing it correctly,
LVM volume can be correctly handled, but CEPH volume can't, and by looking at the code
it is likely that only LVM driver can be correctly handled. I will ask my colleague update
our test log to the report."
1672624,2017-03-15 04:46:58 UTC,"Just tried another case with shutdown=preserve and found I couldn't delete the volume from cinder, as you described. So far, it looks like a problem in cinder? The volume showed as ""available"" and not attached to anything in cinder, then the ""cinder delete"" failed to complete."
1672624,2017-03-15 04:35:37 UTC,"I couldn't reproduce this issue, I found that the volumes were correctly detached for the local delete."
1672624,2017-03-15 05:14:57 UTC,"@melanie witt, Ah, looks like you are doing with CEPH backend, and yes, what we tried is
create a volume first and then attach it to an instance, it should be equal with the
shutdown=preserve scenario?"
1672636,2017-04-10 04:07:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672645,2017-05-06 12:15:55 UTC,"Hello All,"
1672649,2018-04-14 18:06:45 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/445390
Reason: No response to last comments. Feel free to restore and update if you wish to continue with this."
1672649,2017-03-14 09:56:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445390"
1672649,2017-09-26 22:50:33 UTC,Unassigning due to no activity for > 6 months.
1672651,2017-03-14 10:14:53 UTC,I guess that's possible. The shell was totally non-responsive.
1672651,2017-03-14 10:12:26 UTC,"Can't reproduce, it logged me out just fine."
1672651,2017-05-14 04:17:58 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1672651,2017-05-14 04:17:56 UTC,[Expired for ubuntu-app-launch (Ubuntu) because there has been no activity for 60 days.]
1672651,2017-03-14 10:16:34 UTC,The weird thing is that the terminal looked like it had actually closed.
1672652,2017-03-14 09:16:38 UTC,"Another option would be to support org.freedesktop.portal.OpenURI from https://github.com/flatpak/xdg-desktop-portal . This might even be more secure, since it will show the user a selection dialog for which app to use prio to launching anything."
1672652,2018-01-04 12:40:29 UTC,Adding jdstrand for his opinion what the best course of action is here.
1672652,2018-01-04 14:06:30 UTC,James Henstridge is working on this from a portals perspective: https://forum.snapcraft.io/t/ubuntu-desktop-team-priorities/1397/17
1672655,2017-09-26 22:50:39 UTC,Unassigning due to no activity for > 6 months.
1672658,2017-04-17 10:03:04 UTC,"Reviewed:  https://review.openstack.org/456832
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e40c36f09e394f1ddd4af092f537e60687b4f455
Submitter: Jenkins
Branch:    stable/mitaka"
1672658,2017-04-14 05:51:22 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/456832"
1672658,2017-03-30 12:26:31 UTC,"Reviewed:  https://review.openstack.org/451771
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=8461fc5a10d21bc9606be5fcaa7be8e16ea2c3d0
Submitter: Jenkins
Branch:    stable/ocata"
1672658,2017-05-12 07:59:10 UTC,Verified on 9.2 + mu2 updates.
1672658,2017-03-15 11:10:15 UTC,"Reviewed:  https://review.openstack.org/445804
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=b232c9f9e79900ea5390a6cc4434a5c25ffbf781
Submitter: Jenkins
Branch:    master"
1672658,2017-03-15 07:58:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445804"
1672658,2017-03-14 10:15:11 UTC,"Reviewed:  https://review.openstack.org/445379
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=ed41575d09a6e0b4a560c5e16d8008dd3b365272
Submitter: Jenkins
Branch:    stable/newton"
1672658,2017-03-14 09:37:54 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445379"
1672658,2017-03-30 11:36:38 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/451771"
1672658,2017-03-14 09:35:51 UTC,see for example http://logs.openstack.org/99/436399/7/gate/gate-fuel-web-python27-ubuntu-xenial/8b68e71/console.html
1672659,2017-05-13 21:36:07 UTC,"In above comment 3. in Result should say ""system doesn't boot"" not ""systemd doesn't boot"" :)"
1672659,2017-05-13 21:30:16 UTC,Bug is more generic. Basically if some device listed in /etc/fstab is not available mountall job will hang forever. Example:
1672668,2017-08-12 03:23:28 UTC,I don't think this a valid bug. Changing the milestone to next for the time being.
1672668,2019-12-03 18:53:16 UTC,"Change abandoned by Zane Bitter (<email address hidden>) on branch: master
Review: https://review.opendev.org/445741
Reason: Bug is invalid according to Rabi."
1672668,2017-03-15 04:47:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445741"
1672671,2017-03-14 10:38:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445420"
1672671,2017-03-15 08:25:35 UTC,"Reviewed:  https://review.openstack.org/445420
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=b906f0e73219c46f4f2d2f26d935ea4fb9e091b6
Submitter: Jenkins
Branch:    master"
1672671,2017-03-15 08:27:20 UTC,"Reviewed:  https://review.openstack.org/445438
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=c0c37ba4da691260024f123b8fd2b57d9a44199f
Submitter: Jenkins
Branch:    stable/newton"
1672671,2017-03-14 11:26:31 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445438"
1672680,2017-03-20 06:21:48 UTC,"The bug status is ""In Progress"", so do we have patch that is ready for review? please append the url, thank you."
1672680,2017-03-20 08:28:43 UTC,I have proposed a fix : https://review.openstack.org/#/c/444810/
1672686,2017-03-14 11:24:55 UTC,I think that only polarssl 1.3.* is affected because polarssl <= 1.2 does not support elliptic curve crypto.
1672686,2017-03-18 13:47:21 UTC,Added patches for mbedtls.
1672686,2017-03-24 05:18:12 UTC,This bug was fixed in the package mbedtls - 2.3.0-1ubuntu0.1
1672686,2017-03-24 05:18:13 UTC,This bug was fixed in the package mbedtls - 2.2.1-2ubuntu0.1
1672686,2017-04-06 11:12:24 UTC,"Since there is nothing left to sponsor, I am unsubscribing ubuntu-security-sponsors. Please re-subscribe the group when attaching another debdiff. Thanks!"
1672686,2017-03-14 23:38:15 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1672693,2017-03-15 03:10:15 UTC,Because they are widgets. :)
1672693,2017-03-15 03:10:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672693,2017-03-31 02:01:49 UTC,Are you sure ubuntu-app-launch doesn't/shouldn't play a role in providing some kind of session/settings for GTK apps to get?
1672695,2017-06-27 10:57:00 UTC,Verified on Fuel 9.2MU2 - https://patching-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.support_dpdk/22/testReport/(root)/deploy_cluster_with_dpdk_tun/
1672695,2017-06-26 10:46:56 UTC,"Reviewed:  https://review.openstack.org/449059
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=effd8366281934c6256d776fcef1f29fe4118901
Submitter: Jenkins
Branch:    stable/mitaka"
1672695,2017-03-23 10:46:38 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/449059"
1672695,2017-03-17 08:14:09 UTC,"Verified on Fuel 10 build #1481:
https://product-ci.infra.mirantis.net/view/10.0_swarm/job/10.0.system_test.ubuntu.support_dpdk_bond/171/"
1672695,2017-03-16 10:27:35 UTC,"Reviewed:  https://review.openstack.org/445907
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=f2e124344d577853e1feff95199b1014f139cca3
Submitter: Jenkins
Branch:    stable/newton"
1672695,2017-03-15 12:17:45 UTC,"Reviewed:  https://review.openstack.org/445421
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=221dba959294faa8935ff8918811afdf35f49006
Submitter: Jenkins
Branch:    master"
1672695,2017-03-15 12:24:33 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/445907"
1672695,2017-03-15 07:01:45 UTC," Scenario:
        1. Create new environment with VXLAN segmentation for Neutron
        2. Set KVM as Hypervisor
        3. Add controller and compute nodes
        4. Configure private network in DPDK mode
        5. Configure HugePages for compute nodes
        6. Run network verification
        7. Deploy environment
        8. Run network verification
        9. Run OSTF
        10. Reboot compute
        11. Run OSTF
        12. Check option ""firewall_driver"" in config files
        13. Run instance on compute with DPDK and check its availability
            via floating IP"
1672695,2017-03-15 08:28:43 UTC,"Why 10.0 only? Graph sequences were proposed in 9.x stable branches, so current mitaka codebase has the same code but disabled by default. I suppose we should deliver this patch to current stable mitaka."
1672698,2017-04-13 19:33:55 UTC,"I am adding lists of installed packages of my local machine, which has no font problem and my workstation (remote). There are differences in the list of installed fonts, but they are all supplemental fonts. Anyway, maybe it has to do with something else."
1672698,2017-04-17 21:03:06 UTC,"Hey folks,"
1672698,2017-04-17 21:06:18 UTC,"Sorry, I should add: Other places suggest that you should disallow site-specific fonts in your preferences (preferences -> content -> advanced). That solves the issue too, but I'd find that solution unsatisfactory."
1672698,2017-04-18 08:05:50 UTC,"Hi folks,"
1672698,2017-09-21 16:13:58 UTC,I have had the same issue on 16.04 and Firefox 55. Fixed installing fonts-roboto-hinted
1672698,2017-09-22 11:27:02 UTC,"Hi,
still have some issue with some pages.
Here for example"
1672698,2017-04-14 19:40:30 UTC,I will try that on Tuesday after the easter holidays.
1672698,2017-04-14 07:19:42 UTC,"Ok, I fixed it. I did a huge bulk install of fonts using your ""in home but not in workstation"" list, and it fixed the issue, at least for Youtube anyway. Here is the list of what did install. I do know that Youtube use the roboto font, which is on this list, but I did not test a separate install, though. Can you try it ?"
1672698,2017-04-13 20:04:44 UTC,I opened firefox remotely on my workstation and exported the display to my machine at home. The fonts where still missing. This makes this less an xserver issue.
1672698,2017-04-13 20:03:25 UTC,"List of fonts which are available on my machine at home but not on my workstation.
fonts-3270
fonts-aoyagi-kouzan-t 20051011-14
fonts-aoyagi-soseki 20070207-12
fonts-arabeyes 2.1-3
fonts-arphic-bkai00mp 2.10-15
fonts-arphic-bsmi00lp 2.10-17
fonts-arphic-gbsn00lp 2.11-15
fonts-arphic-gkai00mp 2.11-15
fonts-arphic-ukai 0.2.20080216.2-4ubuntu2
fonts-arphic-uming 0.2.20080216.2-7ubuntu2
fonts-baekmuk 2.2-12
fonts-beng 2:1.2
fonts-beng-extra
fonts-cabinsketch
fonts-century-catalogue 001.001-6
fonts-circos-symbols 0.69.4+dfsg-1
fonts-cmu 0.7.0-3
fonts-cns11643-kai 98.1+20150923-2
fonts-cns11643-sung
fonts-cwtex-docs 1.0-3
fonts-cwtex-fs 1.0-3
fonts-cwtex-heib 1.0-3
fonts-cwtex-kai 1.0-3
fonts-cwtex-ming 1.0-3
fonts-cwtex-yen 1.0-3
fonts-dancingscript
fonts-dejima-mincho 227-14
fonts-deva 2:1.2
fonts-deva-extra 3.0-3
fonts-dosis 1.7-2
fonts-droid
fonts-farsiweb
fonts-freefarsi
fonts-gargi
fonts-gfs-baskerville 1.1-5
fonts-gfs-bodoni-classic
fonts-gfs-porson
fonts-gfs-theokritos
fonts-gubbi 1.3-3
fonts-gujr 2:1.2
fonts-gujr-extra
fonts-hack-otf 2.020-1
fonts-hack-ttf 2.020-1
fonts-hack-web 2.020-1
fonts-humor-sans
fonts-indic 2:1.2
fonts-ipaexfont 00301-3ubuntu1
fonts-ipaexfont-gothic 00301-3ubuntu1
fonts-ipaexfont-mincho 00301-3ubuntu1
fonts-ipafont 00303-16ubuntu1
fonts-ipafont-gothic 00303-16ubuntu1
fonts-ipafont-mincho
fonts-johnsmith-induni
fonts-junction
fonts-kalapi
fonts-knda
fonts-lohit-beng-assamese 2.5.3-1
fonts-lohit-beng-bengali 2.5.3-1
fonts-lohit-deva 2.5.3-1
fonts-lohit-gujr 2.92.2-2
fonts-lohit-knda 2.5.3-2
fonts-lohit-mlym 2.5.4-1
fonts-lohit-orya 2.5.4.1-1
fonts-lohit-taml 2.5.3-1
fonts-lohit-taml-classical 2.5.3-2
fonts-lohit-telu 2.5.4-2
fonts-maitreya 7.0.7-1
fonts-mikachan 9.1-9
fonts-mlym 2:1.2
fonts-moe-standard-kai 20120530-2
fonts-moe-standard-song 20120530-2
fonts-mononoki 1.2-1
fonts-nakula 1.0-3
fonts-nanum-extra 20161025-1
fonts-navilu
fonts-orya 2:1.2
fonts-orya-extra 2.0-4
fonts-pagul
fonts-roboto
fonts-rufscript 010-5
fonts-sahadeva 1.0-4
fonts-samyak-deva 1.2.2-4
fonts-samyak-gujr 1.2.2-4
fonts-samyak-mlym 1.2.2-4
fonts-samyak-taml 1.2.2-4
fonts-sarai
fonts-smc
fonts-taml 2:1.3
fonts-telu 2:1.2
fonts-telu-extra
fonts-ubuntu-font-family-console
fonts-ukij-uyghur
fonts-unfonts-extra 1:1.0.2-080608+dfsg-8
fonts-vlgothic 20141206-3ubuntu1
fonts-vollkorn
fonts-wqy-zenhei"
1672698,2017-04-13 19:48:43 UTC,"List of fonts which are available on my machine at home but not on my workstation.
fonts-3270
fonts-aoyagi-kouzan-t 20051011-14
fonts-aoyagi-soseki 20070207-12
fonts-arabeyes 2.1-3
fonts-arphic-bkai00mp 2.10-15
fonts-arphic-bsmi00lp 2.10-17
fonts-arphic-gbsn00lp 2.11-15
fonts-arphic-gkai00mp 2.11-15
fonts-arphic-ukai 0.2.20080216.2-4ubuntu2
fonts-arphic-uming 0.2.20080216.2-7ubuntu2
fonts-baekmuk 2.2-12
fonts-beng 2:1.2
fonts-beng-extra
fonts-cabinsketch
fonts-century-catalogue 001.001-6
fonts-circos-symbols 0.69.4+dfsg-1
fonts-cmu 0.7.0-3
fonts-cns11643-kai 98.1+20150923-2
fonts-cns11643-sung
fonts-cwtex-docs 1.0-3
fonts-cwtex-fs 1.0-3
fonts-cwtex-heib 1.0-3
fonts-cwtex-kai 1.0-3
fonts-cwtex-ming 1.0-3
fonts-cwtex-yen 1.0-3
fonts-dancingscript
fonts-dejima-mincho 227-14
fonts-deva 2:1.2
fonts-deva-extra 3.0-3
fonts-dosis 1.7-2
fonts-droid
fonts-farsiweb
fonts-freefarsi
fonts-gargi
fonts-gfs-baskerville 1.1-5
fonts-gfs-bodoni-classic
fonts-gfs-porson
fonts-gfs-theokritos
fonts-gubbi 1.3-3
fonts-gujr 2:1.2
fonts-gujr-extra
fonts-hack-otf 2.020-1
fonts-hack-ttf 2.020-1
fonts-hack-web 2.020-1
fonts-humor-sans
fonts-indic 2:1.2
fonts-ipaexfont 00301-3ubuntu1
fonts-ipaexfont-gothic 00301-3ubuntu1
fonts-ipaexfont-mincho 00301-3ubuntu1
fonts-ipafont 00303-16ubuntu1
fonts-ipafont-gothic 00303-16ubuntu1
fonts-ipafont-mincho
fonts-johnsmith-induni
fonts-junction
fonts-kalapi
fonts-knda
fonts-lohit-beng-assamese 2.5.3-1
fonts-lohit-beng-bengali 2.5.3-1
fonts-lohit-deva 2.5.3-1
fonts-lohit-gujr 2.92.2-2
fonts-lohit-knda 2.5.3-2
fonts-lohit-mlym 2.5.4-1
fonts-lohit-orya 2.5.4.1-1
fonts-lohit-taml 2.5.3-1
fonts-lohit-taml-classical 2.5.3-2
fonts-lohit-telu 2.5.4-2
fonts-maitreya 7.0.7-1
fonts-mikachan 9.1-9
fonts-mlym 2:1.2
fonts-moe-standard-kai 20120530-2
fonts-moe-standard-song 20120530-2
fonts-mononoki 1.2-1
fonts-nakula 1.0-3
fonts-nanum-extra 20161025-1
fonts-navilu
fonts-orya 2:1.2
fonts-orya-extra 2.0-4
fonts-pagul
fonts-roboto
fonts-rufscript 010-5
fonts-sahadeva 1.0-4
fonts-samyak-deva 1.2.2-4
fonts-samyak-gujr 1.2.2-4
fonts-samyak-mlym 1.2.2-4
fonts-samyak-taml 1.2.2-4
fonts-sarai
fonts-smc
fonts-taml 2:1.3
fonts-telu 2:1.2
fonts-telu-extra
fonts-ubuntu-font-family-console
fonts-ukij-uyghur
fonts-unfonts-extra 1:1.0.2-080608+dfsg-8
fonts-vlgothic 20141206-3ubuntu1
fonts-vollkorn
fonts-wqy-zenhei"
1672698,2017-04-13 14:28:17 UTC,"Hi mike, I have tried that with Firefox 50.1 with the same result. Even stranger on my other machine at home, I use the same setup and it works perfectly."
1672698,2017-03-14 11:47:39 UTC,"The screenshots seem to have the red and blue channels switched, but that is another bug."
1672698,2017-04-13 12:02:12 UTC,Have you tried running with no add-ons or from a new Firefox profile?
1672698,2017-04-13 11:12:04 UTC,"Same here. Upgraded to Ubuntu 17.04, and no fonts displayed on youtube and others (google.com/fonts show all fonts fine… except for the general page and search…). Reinstalling FF did not help, neither using a new profile. Chromium is working well in that regard."
1672698,2017-04-13 11:09:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672698,2017-03-14 15:04:22 UTC,"I don't have any ideas for you about this bug, but just wondering how you got firefox 52 with zesty, as only 50.1 is in the zesty release and 51 is in proposed (see https://launchpad.net/ubuntu/+source/firefox)."
1672698,2019-06-06 09:34:27 UTC,"This is a fairly serious bug that affects so many websites with uncommon fonts, most notably Google services like Gmail using the Roboto font. Refreshing the page has a chance of loading the missing symbols but it's not guaranteed."
1672698,2017-03-14 11:43:35 UTC,"The screenshots seem to have the red and blue channels switched, but that is another bug."
1672698,2017-04-13 13:49:44 UTC,"Yes. Tried a brand new profile, same."
1672702,2017-03-16 13:22:48 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32282"
1672702,2017-03-16 15:25:48 UTC,"Reviewed: https://review.fuel-infra.org/32282
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1672702,2017-03-17 10:57:29 UTC,Verified on 9.2 + mu1 updates.
1672702,2017-04-18 11:21:51 UTC,"Related fix proposed to branch: 11.0/ocata
Change author: Andrii Kroshchenko <email address hidden>
Review: https://review.fuel-infra.org/33176"
1672702,2017-04-25 14:13:59 UTC,"Reviewed: https://review.fuel-infra.org/33176
Submitter: Pkgs Jenkins <email address hidden>
Branch: 11.0/ocata"
1672702,2017-03-16 13:17:33 UTC,"Related fix proposed to branch: 9.0/mitaka
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32281"
1672702,2017-03-16 15:48:00 UTC,"Reviewed: https://review.fuel-infra.org/32281
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1672702,2017-03-15 13:31:01 UTC,"Assigned a bug to Ivan as it is packaging, not OS issue."
1672706,2017-03-15 01:50:47 UTC,"Thanks, I had fixed that one in trunk already. The current snapshot should be able to start.
https://launchpad.net/%7Eonboard/+archive/snapshots"
1672713,2017-03-14 13:56:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445505"
1672713,2017-04-18 13:42:25 UTC,"Change abandoned by Rodrigo Duarte (<email address hidden>) on branch: master
Review: https://review.openstack.org/445505
Reason: abandoning for now..."
1672713,2017-07-25 16:41:49 UTC,"Is this the only place where we have foreign key relationships between the identity backend and something else? If so, maybe this isn't as big of a deal since it's all required for a federated deployment. If you're deploying keystone with federation, you'll need to have a sql backend of some kind to store information required for federation. With the development of shadow users, it is also expected that a separate identity backend (e.g. sql) is available to persist the local (federated) user references."
1672713,2018-04-09 20:30:29 UTC,Unassigning due to inactivity.
1672713,2019-05-20 21:40:18 UTC,"This is also an issue with the resource backend and the identity backend, which causes us to drop the pluggability of the resource backend."
1672713,2019-11-12 20:42:28 UTC,"Reviewed:  https://review.opendev.org/687753
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c4d60977881ac2f014dc6e2eaaba37892f075266
Submitter: Zuul
Branch:    master"
1672716,2017-06-12 19:06:41 UTC,"+1 Ubuntu 17.04, Gnome shell, GTX 960 (nvidia-375.66). Appears to only affect screen shots of windows. Full desktop and area screenshot not affected."
1672716,2018-02-15 16:03:27 UTC,Note: This is not only an Ubuntu bug as this is broken also on other distros with Gnome
1672716,2017-10-24 17:34:04 UTC,I'm having the same issue on Ubuntu 17.10 running wayland on Virtualbox.
1672716,2017-05-09 13:59:25 UTC,"Exact same issue here. Desktop PC with GeForce GTX 970 graphics card, NVidia 381.09 drivers. Ubuntu Gnome 17.04, 64-bit."
1672716,2017-08-28 14:05:14 UTC,I'm having the same issue.
1672716,2017-08-26 11:25:36 UTC,I have this problem on a Radeon HD 7970.
1672716,2017-07-28 23:10:12 UTC,"This also affects me, and can verify it doesn't happen when doing a 'full' screenshot. I have NVidia binary, with dual monitor, if that helps."
1672716,2017-07-11 02:24:22 UTC,"+1 colours are inverted when selected ""grab the current window""
I'm using Ubuntu Gnome 17.04, 64-bit, GeForce GTX 960M, and nvidia-375.66."
1672716,2017-09-22 08:51:25 UTC,"Hi,"
1672716,2017-03-15 15:14:13 UTC,I face the same problem!
1672716,2017-04-23 18:41:22 UTC,This issue exhibits itself on both Nvidia GPU and Intel GPU desktops running Ubuntu Gnome 17.04
1672716,2017-06-09 06:39:24 UTC,"I'm having the same problem as stated in the previous comment. My computer has a Intel i7 4790K, GeForce GTX 1070, Ubuntu Gnome 17.04 64-bit, and using Nvidia driver 381.22."
1672716,2017-06-06 20:52:46 UTC,"I also experience this problem.  Desktop PC, Intel i7-4790K CPU, GeForce GTX 760 GPU, Ubuntu Gnome 17.04, 64-bit,  Nvidia driver 375.66."
1672716,2017-05-01 14:49:25 UTC,"Also an issue for me. Ubuntu Gnome 17.04, ""Haswell-ULT Integrated Graphics Controller"" (Lenovo X1 Carbon 2nd / 20A7004CRT). Hope it'll be resolved soon - it's a really essential functionality for me."
1672716,2017-05-15 21:20:49 UTC,"Same issue here
Intel HD 3000 ([8086:0126] rev 9) , Ubuntu Gnome 17.04, 64-bit"
1672716,2017-03-15 15:08:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672716,2017-05-15 22:17:38 UTC,Swapping red and blue fixes the file:
1672717,2017-03-14 17:17:33 UTC,This happens when you have two GPUs. It goes away when you disable one.
1672717,2017-03-14 17:25:34 UTC,Let's change to confirmed/wishlist. Would be nice to warn users of this if dual gpus are around.
1672717,2017-11-03 16:38:49 UTC,Syncing task from Mir.
1672720,2017-03-15 08:22:45 UTC,I am working on it currently.
1672734,2017-03-15 18:05:24 UTC,"""Why not just request the featured section if that's what the design wants? If we don't know what the store will reply with, we cannot add a descriptive title."""
1672734,2017-03-15 18:29:55 UTC,Which landed yesterday and is in the 0.26b2 release in the beta channel.
1672734,2017-03-14 17:31:49 UTC,"The store used to send back the featured snaps by default for empty searches (we made sure to format the search args appropriately), but it might have recently changed. This PR make sure that we have what we expect:"
1672734,2017-03-14 17:54:48 UTC,"Why not just request the featured section if that's what the design wants? If we don't know what the store will reply with, we cannot add a descriptive title."
1672734,2017-03-15 18:17:18 UTC,ok I saw code to check the length of results and was unclear why
1672736,2017-03-14 14:57:25 UTC,"> When I start Mail after resuming from sleep, I see only old messages in my inbox. About five minutes later, new messages appear.
"
1672736,2017-03-14 15:14:13 UTC,"If you close Mail before putting the laptop to sleep and start mail after resuming from sleep, do you get the same behavior?"
1672736,2017-03-14 15:20:18 UTC,"Also, if it helps, I often notice this problem with read messages in my inbox. That is, I've read the messages on my phone but not my elementary OS computer. I don't get a notification when the messages do arrive, which I think is normal behavior."
1672738,2017-03-14 16:19:41 UTC,"Thank you,"
1672738,2017-03-16 14:32:25 UTC,"This is still not nearly correct, its just finding names that match starting at the beginning.
We need to search the complete snap names and description, whatever metadata snap find searches. Why not just copy the snap find logic."
1672738,2017-03-16 17:27:20 UTC,This PR fixes a few remaining issues:
1672740,2017-03-14 19:36:26 UTC,"In Progress/High. I'm preparing a new release, so I'll include this."
1672740,2017-04-27 18:07:41 UTC,"Applied locally, I'll upload this shortly to 17.10, then we can work on the SRUs."
1672740,2017-05-03 18:59:34 UTC,nplan (0.21) artful; urgency=medium
1672740,2017-05-13 17:21:04 UTC,"ubuntu core 16, then 16.04 release"
1672740,2017-05-03 19:00:31 UTC,What release do we need to backport this fix to?
1672740,2017-06-27 15:50:56 UTC,This bug was fixed in the package nplan - 0.23~17.04.1
1672740,2017-06-27 15:46:26 UTC,This bug was fixed in the package nplan - 0.23~16.10.1
1672740,2017-06-27 14:46:07 UTC,"The verification of the Stable Release Update for nplan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1672740,2017-06-27 14:45:29 UTC,This bug was fixed in the package nplan - 0.23~16.04.1
1672740,2017-06-21 13:39:41 UTC,Here is the information I got:
1672740,2017-06-21 02:15:19 UTC,"Not as far as I know, but I'll try to notify people again to make sure this doesn't get forgotten."
1672740,2017-06-19 14:42:15 UTC,"Hi there,
I test https://launchpad.net/ubuntu/+source/nplan/0.23~16.04.1 in xenial on armhf.
It's work fine.
I can't test on  yakkety and zetsy for armhf.
I see the bug on Snappy is in New state even now.
Any problem?"
1672740,2019-10-01 18:39:46 UTC,The fix to this bug was released across the sack. Marking the snappy task as fix released as well.
1672740,2017-06-13 18:39:14 UTC,"Hello Domotz, or anyone else affected,"
1672740,2017-06-13 18:32:28 UTC,"Hello Domotz, or anyone else affected,"
1672740,2017-06-13 15:30:44 UTC,"Hello Domotz, or anyone else affected,"
1672740,2017-05-29 17:14:56 UTC,Added a task for snappy for the core snap to be recreated. Adding 'verification-done' tag since this fix has been tested.
1672740,2017-05-26 20:55:13 UTC,"Hm, that's a good question. I'll track down the right people to update the core snap."
1672740,2017-05-26 08:18:06 UTC,"Hi Brian,
we tested on ubuntu server 16.04. with package version 0.21~16.04.1.
It works fine.
It is not present on core snap for stable and candidate channel.
How can I know about the availability on snappy platform?"
1672740,2017-05-18 22:00:17 UTC,"Hello Domotz, or anyone else affected,"
1672740,2017-06-16 18:40:34 UTC,"Verification done for xenial, yakkety, and zesty:"
1672747,2017-03-20 10:33:51 UTC,and i cant find it anymore :/
1672747,2018-01-30 10:04:19 UTC,"I think the situation is slowly improving with new hooks (pre-refresh, post-refresh, install and remove hooks). Let's keep this bug open and close it when we've complete set of hooks."
1672747,2017-03-14 15:51:47 UTC,This is a dupe of a bug reported by ogra.
1672751,2017-03-15 03:29:12 UTC,"Yeah, it works correctly in Mir demo servers. Just not in Unity8."
1672751,2017-03-15 03:30:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672751,2017-03-15 03:30:51 UTC,See also bug 1671424
1672764,2017-03-14 15:32:48 UTC,"Stacktrace:
 #0  0xb77cacf9 in ?? ()
 No symbol table info available.
 #1  0x00000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0  0xb77cacf9 in ?? ()
 #1  0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()"
1672764,2017-04-11 18:14:51 UTC,"StacktraceTop:
 raise () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/lib/i386-linux-gnu/libc.so.6
 abort () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/lib/i386-linux-gnu/libc.so.6
 __gnu_cxx::__verbose_terminate_handler() () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/usr/lib/i386-linux-gnu/libstdc++.so.6
 ?? () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/usr/lib/i386-linux-gnu/libstdc++.so.6
 std::terminate() () from /mnt/sec-machines/apport-sandbox-dir/Ubuntu 17.04/i386/report-sandbox/usr/lib/i386-linux-gnu/libstdc++.so.6"
1672773,2017-04-26 13:19:06 UTC,https://review.openstack.org/#/c/450115/
1672778,2017-08-31 11:41:44 UTC,"So, this is the similar bug like this https://bugs.launchpad.net/glance/+bug/1695299
You can try to use this https://review.openstack.org/#/c/498427/3
Or this https://review.openstack.org/#/c/499410/
As i understand we can't use special symbols in user entered password, proof you can find here https://review.openstack.org/#/c/2682/
In future pay attention for this. I think we need to notice developers in documentation."
1672778,2017-03-14 16:23:41 UTC,"OS: CentOS 7.3.1611
OpenStack Serie: Ocata
rpm package: python-glance-14.0.0"
1672791,2017-03-22 01:50:00 UTC,works fine in ubuntu 14.04 (I was attempting this in OS X homebrew)
1672798,2018-04-25 05:42:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672803,2017-03-14 19:59:53 UTC,I wanted to provide better feedback about this sort of thing but it's surprisingly difficult.
1672803,2019-10-01 18:47:40 UTC,I'm marking the snappy task as fix released now.
1672803,2017-03-31 07:23:04 UTC,I can confirm this is working now with latest image from candidate on dragonboard. I went through all the console-conf tests regarding misstyped SSIDs/passwords and everything is ok.
1672803,2017-03-15 08:39:55 UTC,Hi @mwhudson!
1672803,2017-03-21 01:21:21 UTC,"So what was going on here was that the configuration was supposed to time out after 30s, but it wasn't thanks to a bug. Canceling the configuration after that 30s had expired led to the crash."
1672803,2017-03-29 00:55:15 UTC,This bug was fixed in the package subiquity - 0.0.29
1672803,2017-03-15 12:12:06 UTC,Just tried to apply wlan credentials with a wrong password and correct SSID and console-conf also restarted
1672803,2017-03-15 12:35:48 UTC,"Pressing done in network connections page without applying any wlan config, and then trying to cancel it also reboots console-conf"
1672811,2017-03-14 21:30:04 UTC,"I found that there are many shortcuts for certain tools just hardcoded and cannot be overridden, e.g. relative to your report: http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/src/ui/tools/select-tool.cpp#L998"
1672811,2017-03-14 22:52:41 UTC,I guess then this is the main cause of the issue and the main issue itself. They shouldn't be hardcoded or hardcoded in a way that they can be overriden/unset by the key preferences. Even though I guess this contradicts to the term hardcoded.
1672811,2017-03-14 23:16:17 UTC,In this case I don't know whether I should close this bug and open a feature request to have no hardcoded key shortcuts or what :D
1672811,2017-03-14 18:09:23 UTC,I confirm on Linux with r15592.
1672817,2017-03-23 05:27:08 UTC,"@Adnan, Please add some link related to rbac roles for mapping actions"
1672817,2017-03-23 19:38:51 UTC,OS-FEDERATION API are to be comsumed when keystone is configured to run as a service provider (with federation support enabled). Below link should provides enough description on the topic:
1672817,2017-04-05 02:14:44 UTC,"yea, not sure we have devstack with federation support enabled."
1672817,2021-01-08 16:41:23 UTC,Should be fixed by https://review.opendev.org/c/openstack/tempest/+/763148/ which is tracked under https://bugs.launchpad.net/tempest/+bug/1697429 ... therefore I'm gonna mark this as duplicate of https://bugs.launchpad.net/tempest/+bug/1697429
1672822,2018-06-03 21:06:38 UTC,"I have a brand new Acer Predator 17x and I just installed Ubuntu 18.04.  I also only get sound out of the left speaker. When I do the sound test, both the Right and Left channel sounds come out of the left speaker.  This laptop actually has a subwoofer as well as a right speaker.  Neither the right speaker nor the subwoofer working.  With Windows it sounds pretty good.  Under Linux is sort of sounds like my cell phone."
1672822,2020-01-10 20:48:03 UTC,"Hi, I have the same problem I think (2.1 speakers and sounds only the left, if i remove the two little ones (L & R), the subwoofer can sound)"
1672822,2018-08-22 03:30:24 UTC,This bug is open already. It was reopened on 10 July 2018.
1672822,2018-08-22 03:03:15 UTC,"This is still an issue for my hardware. The workaround in the comments does seem to work, but honestly it took finally googling the right phrase after months of trying to find a solution on and off."
1672822,2018-07-10 01:40:02 UTC,"Having said that, this sounds like very specific hardware with a very specific problem. So in this case I'm happy to reopen this bug."
1672822,2018-07-10 01:39:02 UTC,This bug has been closed for 5 months due to no response from the original reporter.
1672822,2018-06-03 21:34:10 UTC,I found a work-around here:  https://ubuntuforums.org/showthread.php?t=2357875
1672822,2018-07-10 00:06:17 UTC,@rotten hdajackretask worked for me.  Confirmed.
1672822,2017-09-09 13:33:20 UTC,(I run Ubuntu 17.04 by the way)
1672822,2018-01-27 15:51:30 UTC,I am also one of the affected users. I want to contribute towards fixing this / writing enhancements in the ALSA / pulseaudio. How do I get started with audio driver development?
1672822,2017-03-15 15:20:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672822,2017-03-15 15:24:33 UTC,"Btw it might sounds not serious but in fact on my laptop it's essentially make sound system useless - sound from subwoofer comes very distorted making almost impossible to distinguish any voice, so no skype, no movies, no youtube or podcast on ubuntu."
1672822,2017-03-31 09:22:27 UTC,I have the same problem with a Predator g9 593 and Ubuntu 16.04 (only the sub is working...).
1672822,2018-02-13 09:47:07 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1672822,2017-06-24 19:50:01 UTC,I am also affected.
1672822,2017-07-27 17:29:19 UTC,"I have the same issue with Acer Predator 15 G9-593-72VT
15.6"" Gaming Laptop Computer - Black;
Intel Core i7-6700HQ Processor 2.6GHz;
NVIDIA GeForce GTX 1060 6GB GDDR5;
16GB DDR4-2133 RAM;
256GB SSD + 1TB HDD"
1672822,2017-09-09 13:24:48 UTC,"I have the same problem with Acer Predator X34A monitor. The sound-control panel says, the controller is GP104 High Definition Audio Controller."
1672822,2017-05-16 07:38:07 UTC,This could be distantly related to bug 608069.
1672827,2019-06-11 19:03:57 UTC,"In bionic, now fails with:"
1672839,2017-03-15 13:40:42 UTC,The action is not stuck at the action panel the action is currently in progress and if it fails then the listing is updated with the failure information.
1672839,2017-03-16 07:31:52 UTC,So the problem of this is:
1672839,2019-09-19 14:50:20 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1672852,2017-07-13 22:17:18 UTC,"This is in general a good idea, but it doesn't fit plans of existing upgrades team contributors. We may get back to it later in the life of neutron after we close gaps in database layer. In the meantime, there are some solutions that resolve some potential issues with rolling upgrades, like sticky load balancers."
1672852,2017-04-21 20:10:49 UTC,"With late OSIC flip-offs, I am not sure it's the best use for my time right now. I am going to unassign myself and suggest that we don't move with approving the proposal."
1672852,2017-04-21 20:10:05 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: master
Review: https://review.openstack.org/451993
Reason: I am not going to pursue it this cycle. I will focus on OVO transition and neutron-db-manage CLI."
1672852,2017-03-22 17:47:45 UTC,"> Disregarding the other upsides and downsides of sticky sessions, that choice may mitigate the impact of this issue.
"
1672852,2017-03-30 21:49:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/451993"
1672852,2017-03-20 16:21:23 UTC,"As an aside, many of the rolling upgrade conversations with deployers have involved abandoning round-robin (which is currently the typical load balancing strategy) in favor of sticky sessions, which (in the base case, at least) prevents clients from seeing API extensions appear and disappear ""randomly."" Disregarding the other upsides and downsides of sticky sessions, that choice may mitigate the impact of this issue."
1672862,2017-03-16 00:17:57 UTC,"Maybe this should be done in casper instead?
See scripts/casper-bottom/"
1672862,2017-03-16 09:24:42 UTC,currently we have a work-around that has just been uploaded as part of 0.7.4 of budgie-desktop-environment.
1672862,2018-02-15 23:08:15 UTC,Relevant chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=807880
1672874,2018-04-06 01:36:39 UTC,Good to know:
1672874,2018-04-23 17:08:56 UTC,"Since the pep was withdrawn, I don't think it makes sense to implement this.  If the pip feature is ipmlemented and doesn't work in PBR, please feel free to open a new bug for adding support."
1672877,2017-10-03 11:58:50 UTC,"This bug seems less about the power state, and more about the node holding onto an IP address in the flat network that it shouldn't have because the neutron port get's deleted so from neutron's perspective the IP is ""free"". Perhaps the solution should be that in the case of cleaning failed, ironic doesn't delete the neutron port for that node, keeping the IP assignment and preventing it from being assigned to a different server and then conflicting."
1672877,2017-03-17 15:26:38 UTC,dtantsur++ Can we triage this and set priority at your convenience please.
1672877,2017-03-17 12:36:20 UTC,"I'd rather set power state to None on entering maintenance, and keep it this way, until the node gets out of it. Then we won't lie to users if any power actions are done to the node."
1672877,2017-03-15 15:32:09 UTC,"It would be helpful to alteast have the clast known power state show up before putting it in maintenance, instead of showing power off."
1672877,2017-03-15 13:28:27 UTC,"What if we checked power state immediately when cleaning fails, so the database is up to date?"
1672877,2017-03-15 12:41:12 UTC,Hi! This bug cannot be fixed for two reasons:
1672878,2017-03-23 14:42:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672879,2017-04-20 21:14:39 UTC,I tried again with agent-stream: released and image-stream: daily (with Juju 2.1.2 from the stable ppa) on a fresh controller and observed the same:
1672879,2017-11-21 22:28:12 UTC,"I believe this is fixed now in 2.3-rc2, with the other upgrade changes."
1672879,2017-04-20 22:22:35 UTC,"@Ryan, in our case, the workaround I used for changing agent_stream was to bootstrap a new controller with the right settings. That seemed to be the only way to make the switch."
1672879,2017-04-20 21:12:13 UTC,"I've just noticed that  I'm getting 'released' images for my model instances, despite setting image-stream to daily.  The controller instances, however, do use a daily image as expected.  This is Juju 2.1.2 + OpenStack Provider against an Ocata undercloud."
1672879,2017-03-21 17:06:00 UTC,"Just commenting that bug 1674755 is very similar. I wonder what other settings may be ""fixed"" at bootstrap."
1672879,2017-03-24 07:30:44 UTC,"Referring to the original bug description, when adding a model and deploying machines to that model, the running Juju agent version influences the stream used. If the running Juju version is a development version, (which it is in this case going by the version number) then I think the stream used for subsequent tools selection will be ""develop"", regardless of what any model agent stream is set to. Not saying this is correct but it explains the observed behaviour."
1672879,2017-03-16 19:55:24 UTC,"@Aaron yes, 2.1.1 is released. The location of the agents is not what this bug covers. The bug is that the controller is not seeing or honoring the model setting for agent-stream. It appears to be permanently set to what it was when the controller was bootstrapped. I had to destroy the controller and re-bootstrap to get this to work."
1672879,2017-03-16 16:48:57 UTC,The devel streams don't contain any agents for 2.1.1.
1672879,2017-03-16 15:29:16 UTC,@abentley I have previously confirmed through test and speaking with Curtis and Nicholas that the devel streams don't have the arm agents.
1672879,2017-03-16 15:03:10 UTC,The version number 2.1.1.1 suggests that the devel streams were not used for the original bootstrap.  x.x.x.1 numbers are created when juju uploads the agent itself.
1672879,2017-03-17 04:01:58 UTC,This is interesting because it will put Juju controller in an unknown state - I do not believe we have encountered situations where models would be created with different agent streams.
1672881,2017-08-14 01:56:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672891,2017-03-14 23:30:58 UTC,"Thanks for the bug report.  I am traveling at the moment without my development machine, but I will take a look at it in a week and a half when I return!"
1672903,2017-03-15 21:07:01 UTC,"Today (03/15/2017) we have faced same db-relation issue in openstack mitaka deployment, this time with neutron-api. David Ames was with us online to debug the issue. Logs ara attached."
1672904,2017-03-31 19:47:55 UTC,The brasero session log file is attached.
1672910,2018-05-08 18:04:21 UTC,This change was made by a bot.
1672912,2017-11-03 16:36:48 UTC,Syncing task from Mir.
1672913,2017-11-03 16:36:51 UTC,Syncing task from Mir.
1672931,2017-03-22 14:10:54 UTC,This will be solved basically in two parts:
1672931,2017-04-05 01:51:07 UTC,https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=e8435ece23017fb4153487f6157eb11cac985697
1672931,2017-03-23 15:03:08 UTC,We switched the order in gtk here:
1672931,2017-04-05 13:31:10 UTC,"Hey Daniel,"
1672931,2017-03-17 06:16:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672931,2017-03-23 02:34:03 UTC,Try this:
1672931,2017-03-15 13:35:18 UTC,*can do
1672931,2017-03-15 03:19:26 UTC,So if you find your Qt apps are flickering that's just bug 1510025.
1672931,2017-03-15 05:56:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672931,2017-03-16 01:32:58 UTC,"Some toolkits should be able to avoid the problem trivially, regardless of what UAL does, if the toolkit just goes:"
1672931,2017-03-24 01:58:50 UTC,I love the simplicity of that diff. Exactly what we want.
1672931,2017-03-15 13:35:09 UTC,"I don't think unity8, qtubuntu or gtk-3.0 can't do anything about it."
1672931,2017-03-15 08:25:48 UTC,"It's not a regression, it's a conscious decision :("
1672939,2017-03-15 04:03:35 UTC,"Fixed with patch:
https://review.openstack.org/#/c/445665/"
1672940,2017-03-15 21:32:24 UTC,This same failure mode occurs if the u-r-c leader tries to update from a slow mirror and the rsync times out.
1672940,2017-03-16 17:25:15 UTC,"Yeah, I believe this is the first time we've deployed a relatively recent version of the charm, I'm not sure when the last time we turned up a new region in one of the clouds was, but I know the AWS mirrors are running older versions of the charm."
1672940,2017-03-15 22:25:20 UTC,"Hey deej,"
1672946,2017-03-15 04:41:48 UTC,Build - fuel 11 stable - 9th of March
1672949,2017-03-15 04:53:46 UTC,Although Unity8 should not be choosing Xmir at all. So this is a consequence of bug 1672931.
1672949,2017-03-15 06:02:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1672949,2017-04-05 08:20:56 UTC,"Fix/workaround committed in:
https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=ba2d104b9cdfeaf03260fd8022ce0178516f5806"
1672950,2019-01-31 23:39:46 UTC,"the desktop view has been removed from nautilus, the usecase described here is also not currently maintained"
1672960,2017-04-04 12:28:38 UTC,This problem appears to be exlcusively in the Mir libraries and not in U-S-C.
1672960,2017-08-07 09:28:26 UTC,Looking at src/server/frontend/protobuf_message_processor.cpp LL105..154
1672960,2017-10-12 13:47:44 UTC,This bug was fixed in the package mir - 0.28.0+17.10.20171011.1-0ubuntu1
1672960,2017-08-09 10:13:55 UTC,"Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 1.0.0"
1672964,2019-12-18 17:38:46 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/460132
Reason: This repo is retired now, no further work will get merged."
1672964,2017-09-20 06:48:32 UTC,"Change abandoned by Joshua Hesketh (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/447483
Reason: This branch (stable/mitaka) is at End Of Life"
1672964,2017-05-02 11:41:17 UTC,"Reviewed:  https://review.openstack.org/460134
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=d60e2ac26753ef3130ee8b68199016d7c7b8dec6
Submitter: Jenkins
Branch:    stable/newton"
1672964,2017-04-26 15:00:36 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/460134"
1672964,2017-04-26 14:59:35 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/460132"
1672964,2017-04-26 13:23:42 UTC,"Reviewed:  https://review.openstack.org/449247
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=3fb3b83f4ad1254a9a54d6d81f5c58f33c92c601
Submitter: Jenkins
Branch:    master"
1672964,2017-04-25 15:40:19 UTC,"Reviewed:  https://review.openstack.org/450882
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=445a16aac208c7b65b82ba66a5a083a882568c2e
Submitter: Jenkins
Branch:    stable/ocata"
1672964,2017-03-30 09:37:57 UTC,"Passed on Newton:
https://product-ci.infra.mirantis.net/view/10.0_swarm/job/10.0.system_test.ubuntu.bvt_ubuntu_bootstrap/224/
https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.error_node_reinstallation/225/"
1672964,2017-03-28 17:39:22 UTC,"Reviewed:  https://review.openstack.org/450875
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=ee2d95de33842187bf99929af321207011c3284f
Submitter: Jenkins
Branch:    stable/newton"
1672964,2017-03-28 16:40:26 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/450882"
1672964,2017-03-28 16:30:01 UTC,"Reviewed:  https://review.openstack.org/450788
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=039ce9e0b82a9e24b0f598fbe528b80feb3fdf3c
Submitter: Jenkins
Branch:    master"
1672964,2017-03-28 16:24:07 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/450875"
1672964,2017-03-28 13:41:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450788"
1672964,2017-03-28 10:27:29 UTC,https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.error_node_reinstallation/224/
1672964,2017-03-22 07:25:10 UTC,"Fix didn't help:
https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.bvt_ubuntu_bootstrap/216/testReport/(root)/deploy_stop_on_deploying_ubuntu_bootstrap/deploy_stop_on_deploying_ubuntu_bootstrap/
Fuel 10 build #1501"
1672964,2017-03-20 15:39:42 UTC,"Reviewed:  https://review.openstack.org/447482
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=8213652e49f0f2c28721dfb9da81ecb69d07f9c9
Submitter: Jenkins
Branch:    stable/newton"
1672964,2017-03-20 15:39:25 UTC,"Reviewed:  https://review.openstack.org/447481
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=56ca061009d419a0866d58d5d1aecef45349bdc5
Submitter: Jenkins
Branch:    stable/ocata"
1672964,2017-03-20 13:05:14 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/447483"
1672964,2017-03-20 13:05:02 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/447482"
1672964,2017-03-20 13:04:48 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/447481"
1672964,2017-03-20 12:52:49 UTC,"Reviewed:  https://review.openstack.org/447083
Committed: https://git.openstack.org/cgit/openstack/fuel-astute/commit/?id=496212798efa9f167de20a3ea0c2146658b2b466
Submitter: Jenkins
Branch:    master"
1672964,2017-03-17 17:55:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447083"
1672964,2017-03-17 07:39:38 UTC,Raising to critical - it affects big amount of swarm threads
1672964,2017-03-16 15:28:06 UTC,"Okay, the RC is different:"
1672964,2017-03-16 11:04:50 UTC,"So the root cause is that when we run a transaction we do not filter nodes per-graph, but rather per-transaction."
1672964,2017-03-15 06:22:02 UTC,"Another failure, scenario
            1. Check mcollective version on bootstrap
            2. Create cluster
            3. Add one node to cluster
            4. Provision nodes <<< failed here
Version: 10.0 ISO #1472"
1672964,2017-03-15 06:20:40 UTC,"Another failure
Scenario:
            1. Check mcollective version on bootstrap
            2. Create cluster
            3. Add one node to cluster
            4. Provision nodes
            5. Check mcollective version on node"
1672964,2017-03-23 17:45:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449247"
1672964,2017-03-28 09:45:22 UTC,We reverted this feature. So the bug should disappear.
1672967,2018-04-02 13:38:57 UTC,See also https://bugs.launchpad.net/juju/+bug/1760390
1672969,2017-03-27 11:17:54 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/450172"
1672969,2017-03-27 11:02:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/450160"
1672969,2017-03-27 11:03:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450162"
1672969,2017-03-28 10:10:44 UTC,"Reviewed:  https://review.openstack.org/450160
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=262c244e17d79b0595118f2c2ace8129c5969363
Submitter: Jenkins
Branch:    stable/newton"
1672969,2017-03-28 10:10:53 UTC,"Reviewed:  https://review.openstack.org/450162
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=dc2a892a0298de0a4406eb447393d82be9735345
Submitter: Jenkins
Branch:    master"
1672969,2017-03-28 10:11:25 UTC,"Reviewed:  https://review.openstack.org/450172
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=fdf355307b6bad93d72d238d0e4be347907d2f17
Submitter: Jenkins
Branch:    stable/ocata"
1672969,2017-04-11 16:19:38 UTC,Verified on 10.0 build #1591.
1672983,2017-03-15 08:09:03 UTC,qt apps native ^^
1672983,2017-03-15 07:55:47 UTC,GTK apps are accidentally using Xmir today (bug 1672931).
1672983,2017-03-15 08:02:42 UTC,"i tested with terminix and gedit native (without Xmir) and it doesn't bring up the keyboard. qt5 apps seems to work fine though, tested with kate, tiled, qupzilla, also seems to work fine in app drawer, system settings"
1672983,2017-03-22 02:03:28 UTC,"AFAIK input methods like the OSK require a third-party process to mediate between the toolkit and the shell, telling the shell when to pop up/down the OSK. So not having that intermediary running (and/or with sufficient privileges) is the problem."
1672986,2017-03-15 09:05:27 UTC,"I agree that IDs only in ACLs is unwieldy but when we made that change it was based on advice from the keystone community that names should never be persisted in ACLs. Apart from the challenge of guaranteeing a unique interpretation of names, the binding between names and IDs can, if I understand correctly, also change over time."
1672986,2017-03-15 17:10:58 UTC,@Attila Fazekas
1672990,2017-03-23 12:41:47 UTC,Upstream fix: https://review.openstack.org/449113
1672990,2017-03-27 17:09:14 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/450343"
1672990,2017-03-29 09:10:20 UTC,"Reviewed:  https://review.openstack.org/450343
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=d74fd2942f36fcaf1aef38befd64b35d9dcb05a7
Submitter: Jenkins
Branch:    stable/ocata"
1672997,2018-03-08 15:39:07 UTC,"I checked a Juju 2.3.2 environment and ""juju status --format yaml ceilometer"" didn't show the bindings it has. ""juju status --format yaml"", either."
1672997,2019-01-30 13:17:09 UTC,This is landed in 2.6 edge snap currently with the new juju show-application command that lists bindings especially.
1672998,2020-10-22 19:47:45 UTC,closing since the package is removed from Ubuntu
1673004,2019-02-27 08:44:31 UTC,"As there seems to be no real ""action"" related to this bug, I post ""a workaround"":"
1673011,2019-06-07 09:30:39 UTC,Fixed in https://code.launchpad.net/~tcuthbert/charm-haproxy/trunk/+merge/368527
1673011,2018-09-19 08:15:57 UTC,Oh hahaha - the posted config file from the deb package has a semantic inconsistency.
1673012,2017-03-22 00:38:18 UTC,"Reviewed:  https://review.openstack.org/445848
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=cb4e713ae646fb3b3c8d5f6945fa0a0577db32e8
Submitter: Jenkins
Branch:    master"
1673012,2017-03-16 06:01:24 UTC,"Reviewed:  https://review.openstack.org/445846
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=e3f4d33f48bbbff6ef56440ef8101086338c4e8f
Submitter: Jenkins
Branch:    master"
1673012,2017-03-15 09:53:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445848"
1673012,2017-03-15 09:48:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/445846"
1673014,2017-09-26 22:50:46 UTC,Unassigning due to no activity for > 6 months.
1673016,2019-03-11 17:33:08 UTC,"I'm also not familiar with dpkg-statoverride, but the pattern seems to be something along those lines:
- if there is no override for path /foo/bar, call dpkg-statoverride with --update"
1673016,2017-09-20 08:36:07 UTC,"As it seems just none around tomcat is very experienced with dpkg-statoverride.
Also while correct it is close to a nice-to have."
1673016,2017-09-19 12:32:31 UTC,Reported and Linked.
1673016,2017-09-19 12:05:12 UTC,"No update for a long time, severity is low (actually undecided so far) and a report to Debian would still be the right thing to do."
1673016,2017-03-20 21:42:51 UTC,Hello and thank you for filing this bug report!
1673018,2017-04-21 07:23:53 UTC,"1) unfortunately StackLight 1.1 will probably never happen, given the current priorities of the project.
2) it should be feasible but see 1)
3) I can't think of any workaround right now that wouldn't involve rebuilding the plugin from modified source."
1673024,2018-01-14 14:06:06 UTC,"This is not just about Arabic glyphs. It may be about the way Google presents the fonts as when you download from the website the default is to only download Latin characters. This is definitely a problem for Typecatcher with Thai as well. I noticed a font with a Thai name and added some custom Thai text, but it only shows in an installed font, not the selected Google font (Sriracha in this case)."
1673028,2017-03-15 12:26:48 UTC,"That looks like you don't have an abstractions/base file (actually you don't seem to have any abstractions/* file), which would be very unusual."
1673028,2017-03-16 00:15:46 UTC,It might be nice to modify the tools to only #include <abstractions/base> if it actually exists. We should aim to keep the tools entirely separate from the policy for those who need to replace the policy entirely.
1673028,2017-03-16 08:46:47 UTC,"It is awkward, but it was my fault.
I an on Gentoo and I did not have installed 'sec-policy/apparmor-profiles'.
I saw 'sec-policy' and subconsciously associated it with selinux.
That is why I omitted it.
Beats me why."
1673028,2017-03-17 01:02:02 UTC,"Hi John, that's expected behaviour. Sort of. Most of the python-based tools will read all the profiles in /etc/apparmor.d/ in order to learn which profiles are stored in which files. Thus there's no way to avoid errors in one profile causing annoyances when trying to profile something else."
1673036,2017-03-21 03:04:23 UTC,A root cause of this issue is that meteos tries to delete a template before deletion of experiment does not complete.
1673040,2019-12-01 14:38:11 UTC,"Newer versions of wsjt-x don't show this problem, seems to be fixed upstream."
1673041,2017-03-20 21:30:36 UTC,Hello and thank you for filing this bug report.
1673041,2020-05-12 13:03:29 UTC,"the debian fix trickled down in ubuntu already.  and in the meantime the ""celeryd"" binary package has been removed."
1673049,2018-01-25 09:25:18 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3663
1673056,2017-03-22 02:00:07 UTC,"A version of this is currently test building in my own local builders, before I upload to Launchpad.  I had tried building yesterday but my build environments decided to die on me, so I had to rebuild my chroots for building, which took a while."
1673056,2017-04-28 18:31:32 UTC,This bug was fixed in the package nginx - 1.12.0-0ubuntu1
1673061,2017-03-15 23:12:01 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1673072,2017-03-16 01:26:18 UTC,"By a strange coincidence, I just found a fourth bug, and I'm sure I've never seen this before. I started /usr/bin/mplayer from commandline, which opened a window (with default -vo setting), and it became listed as a window of /usr/bin/firefox in both Alt+Tab and Dock. It didn't happen again. You will probably not be able to reproduce it easily (I've never seen this despite doing this over 1000 times since I first installed Unity), but that's normal, that's the case of many race-conditions, and this looks like one. There is often no other solution than just reading source code to make sure it does no mistake about locking or atomicity (whatever happens to be needed in that area of the code)."
1673072,2017-03-15 13:35:54 UTC,I had actually chosen a more general title than that (something like « Dock and Alt+tab can still have discrepancies about open apps (even basic system ones) »).
1673078,2017-03-15 16:34:30 UTC,"Hi Vikash, I can't reproduce this issue, can you more details about the port chain being created?
Non-portpair portpairdetails should be removed from the db when the chain is deleted."
1673078,2017-03-15 17:20:03 UTC,"Hi Igor,"
1673078,2017-03-20 10:25:58 UTC,"Hi Vikash,"
1673078,2017-11-05 11:18:48 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/445979
Reason: This review is > 3 months without comment and currently blocked by a core reviewer with a -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -1 on this review to ensure you address their concerns."
1673083,2017-03-15 18:41:29 UTC,Your /boot partition is full. Try running 'sudo apt-get autoremove' in a terminal to remove old kernels.
1673083,2017-05-30 15:42:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673084,2017-05-30 01:30:27 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/446034
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1673084,2017-05-30 01:30:22 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/446035
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1673084,2017-03-15 15:57:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446035"
1673084,2017-03-15 15:57:41 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/446034"
1673084,2017-03-15 15:28:45 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/446013"
1673084,2017-03-15 14:19:51 UTC,See example of failed test https://ci.fuel-infra.org/job/newton.fuel-library.pkgs.ubuntu.neutron_vlan_ha/795/consoleFull
1673084,2017-03-15 16:02:10 UTC,"Reviewed:  https://review.openstack.org/446013
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=72c75e8ec1f152b2ea3891bf44a5dc0d01ccfa1a
Submitter: Jenkins
Branch:    stable/newton"
1673085,2017-03-23 16:55:50 UTC,"Its looking like this cannot be resolved with an OSSN. I will give this another week, and unless shown otherwise will mark it as wont' fix only under OpenStack Security Notes."
1673085,2017-05-08 18:32:42 UTC,Older related ML thread:
1673085,2017-03-23 18:25:13 UTC,"OSSA are specific to issues fixed in supported stable branches. If they can only be fixed in master (and so future major releases), we don't issue advisories because there is no fix for operators to apply."
1673085,2017-03-23 17:17:06 UTC,Looks to me like like B1 + OSSA (public) is the most appropriate path?
1673085,2017-03-16 16:57:44 UTC,"Thanks Matt, so would I be right in saying there is no mitigation / recommended actions? For an OSSN we need to outline the problem, and more importantly provide recommended actions to take?"
1673085,2017-03-15 20:09:00 UTC,"Given comment #4 and the public nature of the issue, I'm going to go ahead and triage this report as Class B1 (A vulnerability that can only be fixed in master, security note for stable branches, e.g., default config value is insecure): https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1673085,2017-03-15 22:12:36 UTC,"So if a backport is not possible, what would the full mitigation steps be for ocata and previous?"
1673085,2017-03-15 20:13:53 UTC,I've added an OSSN task so the security note editors can decide if this is one they want to cover with some sort of warning for stable branches.
1673085,2017-03-15 18:08:43 UTC,The fixes would be:
1673085,2017-03-15 14:32:44 UTC,"If I know that scheduler hints are stored in the request_specs.specs table and the size on that column is 65,535, then I could reasonably do something like:"
1673085,2017-03-15 14:22:18 UTC,"For reference, here is the nova API subteam meeting log where this came up:"
1673085,2017-03-15 22:32:08 UTC,"@lhinds, no you can't set additionalProperties=False in the jsonschema because that changes the API in a backward incompatible way without a microversion, so it could break deployments/users."
1673085,2017-03-15 15:41:49 UTC,"To start, we can almost certainly switch this report to Public Security and skip the embargo since the potential risk is already mentioned in the meeting log (and even called out as a possible security vulnerability). There doesn't seem to be much novel in this report which an interested attacker couldn't easily work out from the public discussion and a quick skim through the source code."
1673087,2017-03-15 14:29:01 UTC,"Hi Tom,"
1673087,2019-09-19 12:03:08 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1673089,2017-03-29 16:20:32 UTC,We actually tried the workaround before posting the problem to Sikuli forum. It does not seems to work well.
1673089,2017-03-29 16:38:39 UTC,Not sure what you want to tell me.
1673098,2020-04-23 22:13:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673098,2020-04-23 22:14:09 UTC,Is this still a problem in bionic or later?
1673098,2020-06-23 04:17:29 UTC,[Expired for gammu (Ubuntu) because there has been no activity for 60 days.]
1673102,2019-09-12 14:34:28 UTC,There is a custom log rules section (fluentd) in master documentation - closing this.
1673106,2020-06-24 00:29:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673108,2017-11-09 18:09:35 UTC,It is for text items and most useful for bible verses as it allows them to the tailored for special treatments.
1673108,2017-11-09 14:27:16 UTC,"How about ""Copy to custom slides""? We could then flash the tab bar for custom slides to indicate that an action has taken place. I did think we could switch to the custom slide tab, but that might be a bit disjointed if a user wants to convert multiple songs."
1673108,2019-07-31 19:26:46 UTC,I cannot seem to find this menu item. Is it still there in 3.0?
1673110,2018-05-09 01:14:08 UTC,"This is more than a wishlist concern: Azure bandwidth is expensive, and so is the bandwidth on our archive servers.  When metadata sync fails due to another bug, this means that it keeps using bandwidth for files which are already synced."
1673110,2020-09-30 03:51:50 UTC,This is a non-issue since the metadata sync's rsync uses --link-dest=ubuntu_active/
1673112,2017-03-16 12:47:20 UTC,Confirmed as described. Running tests on upstream MySQL 5.7.17.
1673112,2017-03-16 12:48:44 UTC,"Sorry actually, tested this on upstream MySQL 5.7.17 Community Server so will open a bug there and will refer to this as original bug report."
1673112,2017-10-09 03:10:47 UTC,"Upstream fixed in 5.7.21, 8.0.4"
1673112,2018-01-25 09:39:25 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1075
1673113,2017-11-09 14:23:37 UTC,"Simon,"
1673113,2017-11-09 18:12:32 UTC,"NO do not remove the code it does work.
It saves the song and reloads the preview but allows the edit to continue.
It is for trial and error formatting so you do not need to keep reopening the editor."
1673113,2017-11-09 18:51:44 UTC,Maybe rename the button then?
1673142,2017-05-25 22:06:53 UTC,"Drivers team is good with this. Bob, feel free to proceed with a spec."
1673142,2017-03-15 21:00:12 UTC,"Armando, yes, this RFE is intended to at least partially supersede/address that bug report. But examples from that bug such as whether a deployment should expose the agent scheduler extension may not yet be addressed in this RFE."
1673142,2017-03-15 21:41:11 UTC,"Hello,"
1673142,2017-03-15 20:47:02 UTC,I wonder if this overlap with bug 1583096
1673142,2017-03-22 20:31:58 UTC,"Yes Slawek, it is related. We need QoS and Ml2 to converge on single mechanism (and keep it agnostic to specific service plugin)."
1673156,2017-03-15 19:51:51 UTC,This bug was fixed in the package ubuntu-mate-settings - 17.04.2
1673163,2017-03-21 15:19:54 UTC,"Reviewed:  https://review.openstack.org/446061
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=fbf712b68f90d69300dbb5b2df844ea1a6c6ed89
Submitter: Jenkins
Branch:    master"
1673163,2017-05-26 15:07:15 UTC,"Change abandoned by Eduardo Gonzalez (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/448452
Reason: already backported"
1673163,2017-06-09 15:32:23 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.
1673186,2017-08-10 00:02:24 UTC,"With bin/ in the command, gox works and I could propose it upstream:
https://github.com/mitchellh/gox/pull/89"
1673186,2017-08-09 20:51:17 UTC,"This is known issue, generating no wrappers is a no go as we will loose functionality such as creating commands of the type"
1673186,2017-08-09 17:11:43 UTC,This is caused by snapcraft and the fact that this snap is using classic confinement.
1673186,2017-08-09 16:04:31 UTC,I can confirm this issue.  I'm having the same problem with my gnome-calendar and gnome-contacts classic snaps.
1673186,2017-08-09 18:25:05 UTC,"oh, nice finding. Thanks zyga."
1673186,2017-03-22 22:42:49 UTC,This affects also the gopass snap:
1673191,2017-03-24 14:22:36 UTC,"@Leo, looking at this more, fusermount will do:"
1673191,2017-03-27 22:28:53 UTC,"Thanks for the info Jaime. I think IPFS is not ready to be run as root because it has no authentication per user in the system, but I will ask. Does it change something if the mount point is in $SNAP_USER_DATA instead of / ?"
1673191,2017-08-03 13:07:11 UTC,"This seems like it is what I described in https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1598309/comments/5. Can you check? If it is, might want to comment in https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1663029 for ways on making the alsa interface easier to use."
1673191,2017-08-03 13:07:42 UTC,"I'm sorry, I commented in the wrong bug. Please ignore comment #5."
1673191,2017-08-03 13:14:07 UTC,"""Does it change something if the mount point is in $SNAP_USER_DATA instead of / ?"""
1673191,2017-03-20 18:03:05 UTC,This should simply be a matter of adding setfsuid to the fuse-support interface.
1673191,2017-03-20 18:20:52 UTC,Thanks Jamie!
1673191,2018-01-30 10:02:47 UTC,"@jdstrand - no, not yet, sorry. I'm crawling from under my pile now so I can explore it in the next cycle but no promises on if I can fix it."
1673194,2017-03-15 17:25:20 UTC,You'll notice nvidia-drm.modeset=1 added on the command line Linux line
1673196,2018-01-20 16:57:15 UTC,Description updated.
1673196,2018-05-16 21:40:31 UTC,"What would be better is if the [Library],Move* COs always responded regardless of what part of Mixxx had focus."
1673196,2018-05-16 21:48:48 UTC,"FWIW, [Playlist],SelectPlaylist  and [Playlist],SelectTrackKnob already work exactly how I expect, even if another part of Mixxx or another application has focus."
1673196,2019-02-16 11:53:21 UTC,I know but I also use ScrollVertical a lot.
1673196,2019-02-25 18:59:11 UTC,"I sometimes have to hit the library library MoveFocus button to get the highlight to move back to the library window.  I agree this could be done better: if focus is anywhere NOT in the library, MoveVertical should focus and affect the library view.  (So it would only scroll the left pane if that pane explicitly has focus)"
1673196,2019-03-04 14:43:20 UTC,https://github.com/mixxxdj/mixxx/pull/2047
1673196,2019-07-20 20:58:10 UTC,"emitKeyEvent() function should actually take care of re-focussing the library table, but was broken because it set focus to any focusWidget which could be WOverview or a QSpinbox.
fixed."
1673215,2017-03-15 18:53:31 UTC,I was able to log into two different users with unity8 simultaneously.
1673215,2017-03-16 01:40:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673215,2017-03-27 13:02:48 UTC,"> That said, if we're going to support an arbitrary number of users then giving each one a different VT does not scale. USC should have a switch-session key combo of its own (similar to the existing Ctrl-Alt-Fn).
"
1673215,2017-03-27 03:01:07 UTC,We could theoretically make the one USC instance appear (differently) on multiple VTs. In tinkering with Mir's VT code I came to realize that VTs are truly a virtual concept. If you ignore the existence of VTs then you can still forcefully start up your system compositor on the screen. Cooperating with the notion of a current VT is just being a good citizen.
1673215,2017-03-24 15:06:38 UTC,"I filed the linked upstream bug.  Lennart is on vacation for a couple more weeks, so this won't see quick action.  pitti pointed me at old bug 1192842 which is basically an old dupe."
1673215,2017-03-23 00:32:03 UTC,I don't know of any other method other than to make logind allow this case as you've suggested. We cannot make Mir sessions runs on different VTs as that would make USC not work anymore.
1673215,2017-03-20 14:33:14 UTC,"Robert, can you comment on this?  Got a recommendation?"
1673215,2017-03-15 19:16:11 UTC,"I have a samsung also with Intel graphics.
When I get a console login I see a number of upstart jobs running, the top one at around 16% cpu. Unity8-dash and dbus-daemon are also running as the second user.
Unity8 is running as the first user only.
I see crashes for url-dispatcher and unity8-policykit-agent"
1673215,2017-03-17 19:52:26 UTC,Some research -- this is because XDG_RUNTIME_DIR is empty for the second user...  Not sure why yet.
1673215,2017-03-20 14:32:22 UTC,"OK, more research.  This looks to be a mismatch between what logind expects lightdm to do and what we actually do."
1673215,2017-03-16 01:45:36 UTC,Confirmed.
1673215,2017-03-15 18:12:15 UTC,setting on u8c-1 if possible
1673215,2017-03-16 14:38:56 UTC,Aha!  My testing was accidentally done on my xenial+overlay laptop (hard to tell environments apart sometimes).  I can confirm on zesty.
1673215,2017-03-16 14:52:44 UTC,"Ah...  If you use unity8-greeter, you don't see this bug.  I think this is due to each session trying to create a USC for itself and they are conflicting.  I believe we were trying to stop doing that, instead always using a global USC, but that must not have been prioritized yet."
1673215,2017-03-16 01:49:21 UTC,Maybe wait for bug 1644237 to be fixed. That might do the trick.
1673225,2017-04-04 15:39:52 UTC,"Confirmed bug. The proximate cause is that the oncomplete callback in line 123 of Open-ILS/web/js/ui/default/conify/global/acq/provider.js never gets run, as it gets dojo.mixin'ed away around line 629 of Open-ILS/web/js/dojo/openils/widget/AutoGrid.js.  Thus, the contact address grid never gets populated."
1673225,2017-04-30 14:43:22 UTC,In starting to look at some other provider related bugs I'm seeing spinning in quite a few other places and I'm wondering if the scope of the issue is wider than the narrow scope I originally reported it in.
1673227,2017-03-15 18:43:04 UTC,"""* reserved and total need a minimum, probably of 0 and 1 respectively"""
1673227,2017-03-15 18:43:27 UTC,"Oh nevermind, 0 and 1, *respectively*."
1673227,2017-03-22 02:52:39 UTC,"Reviewed:  https://review.openstack.org/428800
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b2d7c4d028104d3a2a0d5851b194eface707ec3
Submitter: Jenkins
Branch:    master"
1673227,2017-03-24 11:00:39 UTC,"The commits for this have merged, I guess the automation won't automate on partials (which makes sense)."
1673227,2018-10-02 17:00:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/607320"
1673227,2018-10-02 17:00:22 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/607321"
1673227,2018-10-05 12:50:15 UTC,"Reviewed:  https://review.openstack.org/607320
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=43ae6df96b85c0e008f575193511ebf28b195edd
Submitter: Zuul
Branch:    stable/ocata"
1673227,2018-10-05 12:50:25 UTC,"Reviewed:  https://review.openstack.org/607321
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3eb967784bbe1c1668d22fdb8cee65dc2417103c
Submitter: Zuul
Branch:    stable/ocata"
1673227,2018-10-05 13:22:26 UTC,"The two partial fix (that together solve the bug) got merged. (automation only works for ""closes-bug"" according to previous comment)"
1673227,2017-03-22 02:52:03 UTC,"Reviewed:  https://review.openstack.org/416752
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6a6d021f818d6145bd2cdc6431f95f40d8372d59
Submitter: Jenkins
Branch:    master"
1673232,2018-08-12 16:03:23 UTC,"Great, thanks.  Please send a patch!"
1673232,2017-03-16 21:23:41 UTC,"Sorry, Here are the actual commands:"
1673232,2017-03-16 22:03:47 UTC,"I've been able to install, but the install documentation in the source README file could likely benefit from some additional information."
1673233,2017-03-16 01:08:48 UTC,"Sorry, ignore that duplicate message."
1673234,2019-02-06 18:08:13 UTC,"This bug is solved in 18.04 LTS.
Can be closed."
1673242,2017-03-15 20:31:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446167"
1673242,2017-08-07 16:57:46 UTC,"Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: master
Review: https://review.openstack.org/446167
Reason: This has not been updated for 4 months, and Jim no longer works on ironic. Abandoning for now."
1673248,2018-03-29 13:45:01 UTC,This issue is still present in latest nemo (3.6)?
1673248,2017-05-23 04:16:09 UTC,I have the same problem but on Ubuntu 16.04
1673248,2017-03-15 20:25:47 UTC,"StacktraceTop:
 ?? () from /tmp/apport_sandbox_Nmf6wb/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /tmp/apport_sandbox_Nmf6wb/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_content_type_is_a () from /tmp/apport_sandbox_Nmf6wb/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 nemo_file_is_mime_type (file=<optimized out>, mime_type=<optimized out>) at nemo-file.c:6597
 nemo_action_get_visibility (action=<optimized out>, selection=selection@entry=0x56295b714d40, parent=parent@entry=0x56295beae730) at nemo-action.c:1467"
1673248,2017-05-23 04:15:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673249,2017-03-16 08:06:05 UTC,"Reviewed:  https://review.openstack.org/445631
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4f7fc8435f9340aae293bdcfef99201956ec2838
Submitter: Jenkins
Branch:    master"
1673251,2017-03-15 21:09:10 UTC,"What did you have in the list and what was added after the list was saved.
If the service was an osz then you cannot change it to a oszl.
Can you try out some combinations as the file type should be preserved."
1673251,2017-03-15 21:39:48 UTC,I mostly was testing with an OSZL file (marked Read Only) that I use as a template for Sunday services.  List options are OSZ & OSZL in that order.  Doesn't matter if click File->Save or File->SaveAs or click the Save icon - it always defaults to OSZ type for the OSZL and I have to remember to select OSZL or else our service file is much larger than it needs to be.
1673251,2017-03-15 21:42:05 UTC,"I just tested a non-Read Only OSZL file.  File->SaveAs still defaults the new file type to OSZ, with OSZL as the 2nd option."
1673251,2017-03-17 06:27:46 UTC,"This is not a bug, I've marked it as wishlist."
1673255,2018-05-29 15:31:41 UTC,This bug was fixed in the package drbd-utils - 8.9.10-2ubuntu1
1673255,2018-05-25 16:27:59 UTC,"No fix needed in trusty; the drbd rules file is different in that older version and will not be affected by the udev behavior change (the rules file contains the space directly in its string value, not in a substituted variable, so udev will process the space correctly and the behavior change only affects whitespace inside substituted variables inside SYMLINK assignment in rules files)."
1673255,2018-05-25 16:28:27 UTC,"upstream commit is
https://github.com/LINBIT/drbd-utils/commit/05c0797248af6f4e3b5b04545fe068dba41e3d81"
1673255,2017-03-15 20:57:00 UTC,"Alternately, the drbd udev rule could be refactored, so it didn't place multiple symlinks into an env variable; for example, it could do this:"
1673255,2018-05-29 14:08:50 UTC,"Sponsored for Cosmic, please keep an eye at the ""excuses..."" page to make sure the package is not stuck in cosmic-proposed."
1673258,2019-04-18 11:00:36 UTC,"It's worth mentioning that while PackageKit will likely not receive much feature development unless someone steps up to do that, it is in solid maintenance mode and likely will remain like that for quite some time."
1673258,2019-04-18 08:59:10 UTC,a software-properties using PackageKit is in:
1673258,2019-04-17 19:00:02 UTC,"In the time it took to try to port from aptdaemon to packagekit, packagekit has gone dead upstream, and we have been recommended not to port further work to it."
1673258,2018-02-28 03:05:52 UTC,This bug was fixed in the package ubuntu-mate-meta - 1.216
1673258,2018-01-25 23:11:30 UTC,gnome-software landed
1673258,2018-01-25 23:11:00 UTC,"bionic has dell-recovery 1.54, marking as fixed"
1673258,2017-11-03 16:18:29 UTC,mythbuntu-control-center Deleted on 2017-03-31 by Steve Langasek discontinued flavor; LP: #1639445
1673258,2017-11-03 15:57:38 UTC,"Removing packages from bionic:
 lubuntu-software-center 0.0.10-0ubuntu2 in bionic
  lubuntu-software-center 0.0.10-0ubuntu2 in bionic amd64
  lubuntu-software-center 0.0.10-0ubuntu2 in bionic arm64
  lubuntu-software-center 0.0.10-0ubuntu2 in bionic armhf
  lubuntu-software-center 0.0.10-0ubuntu2 in bionic i386
  lubuntu-software-center 0.0.10-0ubuntu2 in bionic ppc64el
  lubuntu-software-center 0.0.10-0ubuntu2 in bionic s390x
Comment: Obsolete and unused; LP: #1673258
Remove [y|N]? y
1 package successfully removed."
1673258,2017-09-02 03:16:21 UTC,The Lubuntu Software Center has not been updated for several cycles and we don't even ship with it by default any more.
1673258,2019-04-26 12:04:36 UTC,This bug was fixed in the package software-properties - 0.98.0
1673258,2017-07-27 19:14:11 UTC,"dell-recovery has dropped the code related to aptdaemon.
https://github.com/dell/dell-recovery/commit/df1e943cd111c24e1cf3357701caace177f46de8"
1673258,2017-08-03 15:18:43 UTC,"gnome-software in artful-proposed uses PackageKit instead of aptdaemon
https://launchpad.net/ubuntu/+source/gnome-software/3.25.4-1ubuntu1"
1673258,2017-03-15 21:15:23 UTC,Bugtasks added for revdep source packages.  Hopefully I got them all.
1673258,2017-03-17 20:34:29 UTC,"Barry Warsaw wrote:

> language-selector-gnome is similar[2], and should be easy to port
> out to PackageKit, assuming this is even needed anymore. It doesn't
> look like it's maintained either...
"
1673258,2017-03-17 21:58:32 UTC,"Would be quite cool to make the language-selector use ""localization"" AppStream components to detect missing locale... That would also make it work easily with PackageKit.
=> https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Localization.html"
1673258,2017-03-15 21:05:44 UTC,Here are a few more relevant comments from IRC and email:
1673258,2017-03-20 02:11:05 UTC,fails to build :(
1673258,2017-03-20 10:46:17 UTC,"On 20 March 2017 at 02:11, Jeremy Bicha <email address hidden> wrote:

> fails to build :(
>
> ** Changed in: zeroinstall-injector (Ubuntu)
>        Status: Fix Released => Triaged
"
1673258,2017-03-21 19:47:47 UTC,I've now uploaded zeroinstall-injector 2.12-4 to Debian. That should fix the build problem here.
1673258,2017-04-12 20:37:34 UTC,"Thomas, thanks, the updated version worked."
1673258,2017-03-20 02:06:28 UTC,This bug was fixed in the package zeroinstall-injector - 2.12-3
1673260,2020-12-16 20:14:50 UTC,"I am totally new to Home Bank, looking to migrate from an obsolete money manager. What I have tried up to now is to import old files but I can't set the correct currency to each account because of the internal transfers between accounts with different currencies. The proper management of multi currency is putting me off for now."
1673260,2020-11-21 11:12:22 UTC,"@LB: yes indeed, the way mmex implement this is just
- a checkbox that break the link that share the same amount between the from and to txn, and enables store 2 amount.
I will review the patch when working on this."
1673260,2020-11-19 18:34:06 UTC,"I put together a basic proof of concept patch against 5.4.3 source. This allows entering and saving cross-currency transactions. For a cross-currency transaction, the user needs to enter amounts for both sides. I.e. +500 EUR / -600 USD to convert USD into EUR."
1673260,2020-10-21 10:13:28 UTC,"I think the easiest way to implement this is to allow different amounts for the two sides of the transfer transaction when the transaction is between accounts in different currencies. This would imply the transaction FX rate, but would avoid the issues with precision and rounding associated with the FX calc. I.e. if user transfers 100 EUR into a USD account, the transaction screen would ask to enter a USD amount as well. If the FX rate was 1.2345, the user would then enter 123.45 USD."
1673260,2020-08-19 19:07:07 UTC,+1 from me for an idea:)
1673260,2020-04-26 16:58:35 UTC,"I am for this feature!
So that we can edit the internal translation (as it is done in MMEX)"
1673260,2019-12-29 16:15:35 UTC,"I do not know how to upvote for this wish, but I would like to upvote for it."
1673260,2019-12-04 05:59:11 UTC,Having this feature even with manual entry would be very good.
1673260,2019-08-03 16:38:54 UTC,This feature would be neat!
1673260,2019-05-18 16:36:29 UTC,@rugk: this is obvious that the amount would be prefilled in that case
1673260,2019-04-28 09:18:36 UTC,"Don't exactly understand it, but instead of manually entering a different value for the currency, it can, of course, (by default) take the currency conversion one you entered in the currencies window of HomeBank."
1673260,2019-04-23 07:24:47 UTC,What maybe a compromise is to implement this the way it is in mmex (money manager ex).
1673260,2019-02-21 12:54:58 UTC,"Hi! Just wanted to say that I really need it feature in HomeBank!
Without option to transfer money between accounts in different currencies, the statistics shows wrong things..."
1673260,2018-02-14 14:48:44 UTC,"So in times of *very* volatile cryptocurrencies, I think this is really important. :D"
1673260,2017-11-03 20:29:50 UTC,"I'm not 100% sure what you mean by ""enable a transfer that keeps/seals the exchange rate from source to target"", but here's what I want in other words:"
1673260,2017-11-03 19:59:35 UTC,"So the need is to enable a xfer that keep (sealed) the exchange rate from source to target ?
Or is that more complex?"
1673260,2017-10-10 14:28:27 UTC,"Hello @kiddo,"
1673260,2019-08-15 20:31:15 UTC,I Am voting for this feature. The different currencies in internal transactions with entering values manually should be enough for the start. HomeBank is best.
1673260,2019-04-27 21:23:21 UTC,"That could work I guess, especially if there's a way, when exporting to CSV with homebank, for Homebank to automatically calculate the exchange rates based on the two (source and destination) amounts of the ""advanced"" transaction (since the ""accounts"" have the notion of currency anyway)"
1673261,2018-10-08 21:49:01 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1673261,2017-03-15 21:15:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446177"
1673261,2018-10-03 12:08:45 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/607537"
1673261,2017-04-14 09:22:52 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1673261,2018-10-04 03:11:32 UTC,"Reviewed:  https://review.openstack.org/607537
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7ed672715a5edae74a3b348b9e41a85b00a8d50e
Submitter: Zuul
Branch:    stable/ocata"
1673261,2017-03-16 11:33:16 UTC,"Reviewed:  https://review.openstack.org/446177
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3397c7582e3f6e1a7030e29e0d7df5ef26ed0c4f
Submitter: Jenkins
Branch:    master"
1673269,2017-03-15 22:05:26 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Could%20not%20resolve%20host%5C%22%20AND%20tags%3A%5C%22console%5C%22
1673273,2017-03-17 16:51:07 UTC,I took the version of Ubuntu 17.04 which has a dependency on libgnutls28-dev (>= 3.4.15). There is only version 3.4.10-4ubuntu1.2 in Ubuntu 16.04. This is why it fails to build there.
1673273,2017-03-17 17:38:47 UTC,Thanks for explaining the reason.
1673280,2018-07-09 10:34:24 UTC,"Is this still occurring?  We haven't heard about it from anyone else, and have not seen it ourselves.  Have been able to upload 2GB images in recent devstack with swift backend."
1673280,2020-12-23 15:02:57 UTC,"I keep getting this error irrespective image sizes, logs are similar as well. Any suggestions on how to fix this ?"
1673281,2017-03-20 21:49:14 UTC,Hello and thank you for filing this bug report.
1673281,2017-04-08 18:11:49 UTC,"Forwarded to OpenVPN: https://community.openvpn.net/openvpn/ticket/873
Looking through the code, there shouldn't be any issues (other than a small memory usage increase)."
1673288,2017-03-15 23:40:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446227"
1673288,2017-03-15 23:50:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446231"
1673288,2017-03-28 05:28:05 UTC,"Reviewed:  https://review.openstack.org/446231
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=ad1324c7acd4afa937ce41b6339e3dc817d0de25
Submitter: Jenkins
Branch:    master"
1673288,2017-04-07 10:05:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/454650"
1673288,2017-04-11 08:36:43 UTC,This issue was fixed in the openstack/puppet-tripleo 7.0.0 release.
1673288,2017-09-12 20:21:41 UTC,"Change abandoned by Giulio Fidente (<email address hidden>) on branch: master
Review: https://review.openstack.org/454650
Reason: not valid from pike with ceph-ansible, we might reprise it for the older releases should it become an issue"
1673288,2017-09-12 20:22:07 UTC,"Change abandoned by Giulio Fidente (<email address hidden>) on branch: master
Review: https://review.openstack.org/446227"
1673298,2017-11-13 18:07:10 UTC,Am going to mark this as confirmed since this seems useful.
1673298,2017-11-13 18:02:52 UTC,"Thanks for the bug report. I brought it up in today's ironic meeting [1] and clarified that for (small) changes to improving our testing environment, there is no need for an RFE."
1673298,2017-03-20 14:28:44 UTC,Not sure if this needs a spec or not. Personally I think it does not but would like others to weigh in.
1673305,2017-03-24 06:51:25 UTC,"https://docs.openstack.org/developer/nova/cells.html we had similar issue in multinode env, we referred to that document and fixed the problem, so no target to nova I guess"
1673305,2017-03-16 09:55:04 UTC,Could you run nova-manage cell_v2 discover_hosts and try again?
1673305,2017-03-17 20:20:32 UTC,"Not sure if adding ""affects nova"" is entirely appropriate, but we encountered this when testing this patch with the PowerVM driver: https://review.openstack.org/443189 which is currently based on commit 80af8a9dacf6fbd853b5b0e07ffb8bffac3aa8fa of the nova tree."
1673309,2018-08-26 17:21:08 UTC,From DpkgTerminalLog.txt:
1673325,2017-03-16 04:57:00 UTC,https://pastebin.canonical.com/182519/ has non-wrapped version of above
1673325,2021-02-15 22:48:44 UTC,Still seeing this:
1673325,2021-02-15 22:55:43 UTC,"Looks to be unison.ssh_authorized_peers() not updating the known_hosts file used. The charm definitely calls unison.ssh_authorized_peers() on cluster-relation-{joined,changed,departed}."
1673325,2021-02-15 22:56:55 UTC,"Oh, maybe different problem."
1673325,2021-02-15 22:59:25 UTC,Filed LP:1915765
1673326,2017-03-21 20:25:50 UTC,I'm not quite sure what happened here but I suspect a local configuration error given that the DuplicateSignature contains the following:
1673326,2017-03-18 22:03:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673326,2017-03-18 22:07:08 UTC,Caused by manual `sudo apt-get upgrade`
1673344,2017-10-20 13:34:08 UTC,I do understand that apparently I can't use the mainline kernels because I'm using the nVidia blob...
1673344,2017-10-20 13:32:45 UTC,"I'm sorry, but I really don't understand. I understand about kernels...but that page just baffles me completely."
1673344,2017-09-25 05:45:04 UTC,"Try latest mainline kernel here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/"
1673344,2017-09-24 17:39:07 UTC,apport information
1673344,2017-09-24 17:39:20 UTC,apport information
1673344,2017-09-24 17:39:11 UTC,apport information
1673344,2017-10-20 14:37:27 UTC,Then try Artful's 4.13 kernel. It's compatible with Nvidia blob.
1673344,2017-09-24 17:39:35 UTC,"Sorry...I found another USB wifi adapter that used a non-Intel chipset, so I plugged it in after the Intel one failed and ran apport as requested."
1673344,2017-10-20 14:50:20 UTC,Sorry...but I really don't know what you're talking about. Who or what is Artful?
1673344,2017-09-24 17:38:36 UTC,apport information
1673344,2017-10-25 10:52:19 UTC,Observing exactly the same as described by Paul after upgrade to 17.10
1673344,2017-10-25 20:35:57 UTC,"I'm sorry, but this new kernel is much, much MUCH worse than the old one as now my system is completely unusable."
1673344,2018-01-29 17:16:43 UTC,"Also now experiencing this bug after 17.10 upgrade - never had a problem before. Wifi still works fine on the Windows side of dual boot so probably software issue. Messing with swcrypto, rfkill, power management off, WOL off doesn't seem to have any effect. I tried different older ucode versions from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git but the problem still exists, although the oldest 7260-17 ucode version on the git tree doesn't continually spam errors to dmesg after the initial failure, just once for the initial failure."
1673344,2018-03-20 05:11:37 UTC,"Final update on this. It turned out that using the 2.4 Ghz band was much more stable than 5 Ghz, which got wedged within minutes, but conditions eventually worsened until even on 2.4 Ghz without much internet usage it would get wedged every few hours. I then tried out various kernel versions on 16.04 LTS going all the way back to 4.4.9 and different versions of iwlwifi ucode with no success and different variations of dmesg output, even though I recalled the wifi working just fine back before upgrading to 17.10."
1673344,2019-10-29 02:40:43 UTC,Here's a script that will get the wifi back up and running again without a reboot:
1673344,2020-07-26 11:11:46 UTC,"RyanNerd, this is script is a great remedy, thanks for sharing it!
I have been looking for fixing this problem for some time!"
1673344,2021-01-26 22:30:04 UTC,Similar bug: bug 1913350
1673344,2017-09-24 17:39:05 UTC,apport information
1673344,2017-10-24 20:40:34 UTC,Against my wishes I've updated to 17.10 along with the kernel and drivers that come with it.
1673344,2017-09-24 17:39:01 UTC,apport information
1673344,2017-06-16 20:28:23 UTC,My wifi info script output information
1673344,2017-09-24 17:38:57 UTC,apport information
1673344,2017-06-16 20:10:13 UTC,"Have the same issue, so subscribing for updates."
1673344,2017-06-16 20:23:05 UTC,"Also this looks like the same problem:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1684213"
1673344,2017-06-16 20:26:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673344,2017-06-16 20:28:21 UTC,My wifi info script output information
1673344,2017-09-24 17:38:59 UTC,apport information
1673344,2017-09-19 01:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1673344,2017-09-20 21:40:54 UTC,"Apport-collect won't work as this is a network related bug. By the time the bug has manifested, networking is no longer available"
1673344,2017-09-24 17:38:30 UTC,"ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  hamakei    1667 F.... pulseaudio
 /dev/snd/controlC0:  hamakei    1667 F.... pulseaudio
CurrentDesktop: LXDE
Dependencies:"
1673344,2017-09-17 16:50:12 UTC,Affects me too. I also get the iwl_pcie_txq_stuck_timer errors in dmesg at the point of failure
1673344,2017-09-24 17:38:41 UTC,apport information
1673344,2017-09-24 17:38:44 UTC,apport information
1673344,2017-09-24 17:38:47 UTC,apport information
1673344,2017-09-24 17:38:50 UTC,apport information
1673344,2017-09-24 17:38:52 UTC,apport information
1673344,2017-09-24 17:38:54 UTC,apport information
1673344,2017-09-24 17:38:33 UTC,apport information
1673350,2017-03-29 12:18:31 UTC,Default Comment by Bridge
1673350,2017-04-24 14:11:40 UTC,This bug was fixed in the package linux - 4.8.0-49.52
1673350,2017-03-30 23:08:01 UTC,"Hello bugproxy, or anyone else affected,"
1673350,2017-03-30 23:11:39 UTC,"Hello bugproxy, or anyone else affected,"
1673350,2017-04-13 16:13:46 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1673350,2017-04-13 16:15:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1673350,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1673350,2017-06-14 20:43:38 UTC,Verification done for yakkety's multipath-tools SRU:
1673350,2017-03-17 10:12:24 UTC,Prepared a patch and sent to the kernel-team mailing list.
1673350,2017-06-27 15:29:29 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1673350,2017-07-04 14:52:38 UTC,"Hello bugproxy, or anyone else affected,"
1673350,2017-07-04 14:54:02 UTC,"Hello bugproxy, or anyone else affected,"
1673350,2017-07-11 20:30:07 UTC,"------- Comment From <email address hidden> 2017-07-11 16:24 EDT-------
Verified on 16.04 with the daily ISO (2017/07/11)."
1673350,2017-07-13 09:44:10 UTC,This bug was fixed in the package multipath-tools - 0.5.0+git1.656f8865-5ubuntu2.5
1673350,2017-07-13 09:44:17 UTC,"The verification of the Stable Release Update for multipath-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1673350,2017-07-13 09:50:41 UTC,This bug was fixed in the package hw-detect - 1.117ubuntu2.2
1673350,2017-03-28 08:23:19 UTC,This bug was fixed in the package hw-detect - 1.117ubuntu4
1673350,2017-06-15 21:53:25 UTC,This bug was fixed in the package multipath-tools - 0.5.0+git1.656f8865-5ubuntu7.3
1673350,2017-03-28 01:41:19 UTC,"The hw-detect change is uploaded, so once it's in the archive, installs on hardware requiring dm-queue-length should work without issues."
1673350,2017-03-16 12:36:38 UTC,"It's possible to reproduce this problem in a qemu-kvm guest,
with an emulated disk: force the queue-length path selector."
1673350,2017-03-21 15:50:40 UTC,"------- Comment From <email address hidden> 2017-03-21 11:39 EDT-------

> AFAICT there wouldn't really be any change required to initramfs-tools --
> everything is contained in multipath-tools-boot.
"
1673350,2017-03-16 07:09:27 UTC,Default Comment by Bridge
1673350,2017-03-16 07:09:29 UTC,Default Comment by Bridge
1673350,2017-03-16 07:09:30 UTC,Default Comment by Bridge
1673350,2017-03-16 12:35:02 UTC,"For easier reading, I'll break the description field apart,
to split the comments that got merged there, into actual comments at Launchpad."
1673350,2017-03-16 12:35:28 UTC,"Error logs:
----------"
1673350,2017-03-16 12:35:55 UTC,"Patch verification on 16.04:
---------------------------"
1673350,2017-03-16 12:36:10 UTC,"Patch verification on 17.04:
---------------------------"
1673350,2017-03-16 07:09:26 UTC,Default Comment by Bridge
1673350,2017-03-24 21:46:58 UTC,This bug was fixed in the package linux - 4.10.0-14.16
1673350,2017-03-16 15:46:13 UTC,"Steve,"
1673350,2017-03-17 01:44:14 UTC,"This goes without saying, thanks for filing this bug report."
1673350,2017-03-17 01:59:32 UTC,Triaged and assigned to me for the multipath-tools and d-i work. I've notified the kernel team on IRC as well since I'll need to have multipath-modules-udeb containing dm-queue-length before I can apply the changes there. Then we can SRU the whole thing as well.
1673350,2017-03-17 12:50:08 UTC,"Thanks, @cyphermox and @smb."
1673350,2017-03-18 07:29:43 UTC,This bug was fixed in the package multipath-tools - 0.6.4-3ubuntu2
1673350,2017-03-21 14:39:06 UTC,AFAICT there wouldn't really be any change required to initramfs-tools -- everything is contained in multipath-tools-boot.
1673350,2017-03-16 12:38:15 UTC,@taco-screen-team
1673351,2017-03-16 07:20:13 UTC,i also see some launcher drag errors in unity8.log
1673351,2017-03-16 07:21:15 UTC,"[2017-03-16:09:11:19.477] qml: ItemGrabber: Saving image to /home/pixel/Pictures/Screenshots/screenshot20170316_091119477.png
[2017-03-16:09:11:21.842] file:///usr/share/unity8//Launcher/LauncherPanel.qml:557: TypeError: Cannot read property 'dragging' of undefined
[2017-03-16:09:11:21.858] file:///usr/share/unity8//Launcher/LauncherPanel.qml:557: TypeError: Cannot read property 'dragging' of undefined
[2017-03-16:09:11:21.859] file:///usr/share/unity8//Launcher/LauncherPanel.qml:557: TypeError: Cannot read property 'dragging' of undefined
[2017-03-16:09:11:21.879] file:///usr/share/unity8//Launcher/LauncherPanel.qml:557: TypeError: Cannot read property 'dragging' of undefined
[2017-03-16:09:11:23.277] file:///usr/share/unity8//Launcher/LauncherPanel.qml:557: TypeError: Cannot read property 'dragging' of undefined"
1673353,2017-03-16 10:53:30 UTC,"Confirmed for terminal, it's fine for system settings."
1673357,2020-09-08 20:52:48 UTC,"Hello vvhk, or anyone else affected,"
1673357,2020-12-09 20:29:18 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for xenial for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1673357,2020-12-10 10:42:51 UTC,This bug was fixed in the package munin - 2.0.25-2ubuntu0.16.04.4
1673357,2020-09-08 20:52:34 UTC,I'm accepting this because its a fine SRU and I don't think a Launchpad bug report (that doesn't show up in default searches) is a good way to find out if anybody would benefit from this fix.
1673357,2020-12-10 10:42:57 UTC,"The verification of the Stable Release Update for munin has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1673357,2020-12-09 20:56:23 UTC,Sorry for the delay. I verified the package in proposed and it works as expected:
1673357,2020-07-29 11:54:58 UTC,"Thank you Lucas and Andreas for working on this, and sorry vvhk that a fix to 16.04 got delayed."
1673357,2017-03-17 10:07:15 UTC,"Hi,
thank you for your report and your help to make Ubuntu better.
The eventual fix needed is:"
1673357,2020-01-10 17:34:13 UTC,Passing by ack'ing that this bug is still valid and in our queue.
1673357,2019-11-07 13:40:33 UTC,Looks like this bug fell through the cracks.
1673357,2017-03-17 12:42:40 UTC,Thanks for responding so fast.
1673357,2017-03-16 07:47:22 UTC,"Ubuntu 16.04, server."
1673357,2020-07-20 20:55:15 UTC,I prepared a PPA with a package containing the upstream fix linked in comment #2 by Christian:
1673360,2017-11-28 07:02:51 UTC,"Unfortunatelly latest Ubuntu Mate development release affected too this issue related.
I now installed with Ubuntu Mate Bionic code named development release my KVM virtual machine."
1673361,2017-03-16 12:59:31 UTC,"Measure need to be in the middle of the measure segment you need to go far away from the draw and maybe go to hidden areas or finaly overlap. Also the calculation can reduce significaly the speed of the measure, what is worst."
1673361,2017-03-16 09:11:47 UTC,">>> Jabiertxof <email address hidden> schrieb am 16.03.2017 um 09:43 in
Nachricht <email address hidden>:

> Hi Ulrich-windl. Thanks for fill the bug!
> Two questions:
> How to handle if some lavels are overalping in one position and others
> labels overlap in the other?
> How handle label overlap in both positions?
"
1673361,2017-03-16 08:43:43 UTC,"Hi Ulrich-windl. Thanks for fill the bug!
Two questions:
How to handle if some lavels are overalping in one position and others labels overlap in the other?
How handle label overlap in both positions?"
1673362,2017-03-16 13:59:06 UTC,We've been trying to encourage projects relying on sqlalchemy-migrate to move to alembic instead. Is that an option for buildbot?
1673363,2017-03-16 08:32:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673363,2017-03-28 01:31:05 UTC,See also bug 1671458
1673368,2017-03-16 08:45:32 UTC,not only at maximum size :D it happens at any size but it's a bit more obvious at maximum size :P
1673368,2017-03-16 10:59:14 UTC,"Confirmed, our design forces a 8x7.5 ratio - if we want to maintain that, we'd have to clip those with background and fit those without..."
1673372,2017-03-16 09:37:24 UTC,"This was fixed long ago in yakkety or zesty, and should work with the  xenial-backports version?"
1673372,2017-03-16 09:45:44 UTC,"There is way more than just that if you want to run autopkgtests for zesty on xenial -- I recommend to always use the backport, there's just too much that needs to be updated for changes in newer releases."
1673379,2017-04-10 12:15:41 UTC,On another system upgraded to zesty I get different error messages:
1673379,2017-04-15 15:50:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673379,2017-04-15 16:38:34 UTC,"For the record, this is also ramdomly happening with swap partition not encrypted.
Kind of race i suppose, but cant determine what exactly.
So cryptsetup seems not the main reason of that problem.
Note that cryptsetup is installed due to some packages's dependency."
1673379,2017-04-15 19:17:52 UTC,"Dino99, this bug report clearly references a device which has ""cryptswap"" in its name. Saying that it happens on systems without crypted swap enabled, without defining what ""it"" is, is not helpful. Please file a separate bug report for your issue."
1673381,2017-03-16 09:15:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446377"
1673381,2017-07-13 00:36:49 UTC,"Change abandoned by zhangdaolong (<email address hidden>) on branch: master
Review: https://review.openstack.org/446377"
1673381,2018-01-12 19:03:26 UTC,Unassigning due to no activity for > 6 months.
1673385,2017-03-20 19:04:46 UTC,This sounds like an issue with the software with which you used to install Ubuntu.
1673391,2017-03-16 09:32:29 UTC,"[2017-03-16:11:21:16.723] qtmir.surfaces: MirSurface[0x560fb494dd30,""qupzilla""]::updateState(hidden)
[2017-03-16:11:21:16.724] qtmir.surfaces: MirSurface[0x560fb494dd30,""qupzilla""]::setFocused(false)
[2017-03-16:11:21:16.725] qtmir.surfaces: MirSurface[0x560fb4273a60,""qupzilla""]::setFocused(true)
[2017-03-16:11:21:16.727] toplevelwindowmodel: setFocusedWindow(Window[0x560fb3ec5930, id=24, MirSurface[0x560fb4273a60,""Speed Dial - QupZilla""]])
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
  what():  Failure sending input event : Unknown channel provided
()
[2017-03-16:11:21:32.519] qtmir.screens: ScreensModel::ScreensModel"
1673398,2017-05-17 20:53:03 UTC,"I can confirm this.
I have fresh install of Ubuntu 17.04 and nVidia card with 2 monitors, one rotated. I can configure it correctly in gnome-flashback and generate correct xorg.conf in nvidia-settings, but the rotated secondary monitor is selected as primary on login screen and is not rotated.
I ""fixed"" the annoyance by autologin..."
1673398,2017-05-18 09:59:23 UTC,not sure gnome-control-center is the correct package here - either lightdm or lightdm-gtk-greeter is probably the correct packages to report against.
1673399,2018-01-24 22:34:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1417
1673404,2017-03-16 12:01:17 UTC,"Yeah, that's because QML MouseArea isn't very smart wrt mouseEnter/Leave/Move events; it works only as long as you move the mouse alone and breaks when the MouseArea itself moves under the cursor :/"
1673404,2017-03-20 09:20:16 UTC,Update to a better Qt ^_^
1673404,2017-03-20 09:23:36 UTC,"And by better Qt I mean one that contains the bugfix forhttps://bugreports.qt.io/browse/QTBUG-42578
i.e."
1673412,2018-08-28 22:05:37 UTC,I feel like this bug is going to require more information to fix.  Can you include your relevant configuration files and logs?
1673414,2017-03-21 14:03:08 UTC,"After testing on real hardware and full-virt based on kvm_hv and a clarification with Colin I wanted to make it more clear in the bug that this affects emulation via qemu-system-ppc64le, but not real virtualization."
1673414,2017-03-18 08:21:27 UTC,"Hi Colin, what system is this on?"
1673414,2017-03-20 18:01:05 UTC,At least in zesty:
1673414,2017-03-20 18:14:53 UTC,"Yep, assign back, I'll look at it."
1673414,2017-03-20 18:41:13 UTC,@Anton:
1673414,2017-03-20 18:56:01 UTC,"This issue also appears in Ubuntu...
  Xenial 4.4.0-66-generic + libc 2.23-0ubuntu5
  Yakkety 4.8.0-41-generic + libc 2.24-3ubuntu2
  Zesty  4.10.0-11-generic + libc 2.27-7ubuntu2"
1673414,2017-03-21 00:33:17 UTC,"Thanks Colin, I can confirm that this reproduces in upstream QEMU. It looks like none of the user readable SPRGs are implemented. I'm surprised we haven't hit this before!"
1673414,2017-03-21 09:27:50 UTC,I only found this bug with stress-ng; this is a tool that exercises all the system calls.
1673415,2017-03-31 11:57:27 UTC,Latest landings improved the situation but this bug is not completely fixed yet.
1673415,2017-03-31 01:11:04 UTC,This bug was fixed in the package qtubuntu - 0.64+17.04.20170328.1-0ubuntu1
1673415,2017-03-23 12:33:16 UTC,One of the prerequisite fixes is bug 1671424
1673415,2017-03-31 01:11:02 UTC,This bug was fixed in the package unity8 - 8.15+17.04.20170328.3-0ubuntu1
1673415,2017-03-17 14:54:17 UTC,This actually goes deeper than simply supporting satellite window types.
1673415,2017-03-16 15:00:08 UTC,We are missing support for satellite windows.
1673415,2017-03-17 14:59:43 UTC,"Other issues being:
1 - we are forcibly killing windows that are closed. it's perfectly ok for an application to simply hide a window whose close button was clicked."
1673417,2018-09-07 07:17:46 UTC,tracked on story board - https://storyboard.openstack.org/#!/story/1673417
1673420,2019-09-19 16:49:47 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.opendev.org/446609
Reason: Very old"
1673420,2017-03-16 12:05:14 UTC,Image history:
1673420,2017-03-16 14:41:38 UTC,"There is already a bug open for the issue:
https://bugs.launchpad.net/kolla-ansible/+bug/1658840"
1673420,2017-03-16 15:58:08 UTC,I've also submitted a fix: https://review.openstack.org/446609
1673422,2017-03-16 13:10:00 UTC,Thanks for the report!
1673423,2017-03-17 08:43:48 UTC,Notably we just got this message regarding 32-bit powerpc:
1673426,2017-03-17 02:43:06 UTC,That's strange. It's running perfectly for me (also under Unity8 with Xmir).
1673429,2017-06-13 15:05:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/473873"
1673429,2017-06-27 16:00:18 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'"
1673429,2017-11-15 12:37:07 UTC,"This fix should not be merged until ironic bug https://bugs.launchpad.net/ironic/+bug/1732412 has been resolved. Turns out ironic is not very diligent in cleaning up provisioning ports, and until now this has been masked by nova cleaning up after it."
1673429,2018-01-31 11:55:08 UTC,The above fix in ironic was released in ironic 10.0.0. The fix for this issue in nova can now be unblocked.
1673431,2017-05-09 16:33:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673433,2017-03-31 14:49:55 UTC,Same issue is observed with maas 2.2.0~beta4+bzr5856-0ubuntu1~16.04.1
1673433,2018-04-10 20:31:27 UTC,I have been trying to reproduce this with latest master that includes https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/342811 which I believe was the actual cause of this issue.
1673433,2019-09-19 11:53:00 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1673434,2017-03-18 08:50:53 UTC,Reduced test case:
1673434,2017-03-18 08:52:49 UTC,Build with gcc -g -O2
1673434,2017-08-22 10:39:03 UTC,work around is to build with -O1
1673452,2017-03-20 16:59:58 UTC,"This issue is fixed by
export GOCOOKIES=$WORKSPACE/gocookies
in the affected job"
1673453,2017-06-19 15:50:04 UTC,"At System76, we would like to help with this. I am working on patches for encrypted home. I would also like the option of setting a weaker user password, if the user confirms that is what they want."
1673453,2017-06-19 22:20:56 UTC,Ideally it would be best to see new features land in a loadable plug-in system for Ubuntu gnome rather than patching each individual feature.
1673457,2017-03-17 12:54:30 UTC,"FWIW, I installed php-horde-css-parser_1.0.11-1_all.deb from Debian and it fixes this issue."
1673457,2017-03-17 12:49:57 UTC,Would it be possible to sync this package with the latest Debian version? AFAICT its reverse deps will still match version 1.0.11-1.
1673466,2017-03-19 08:49:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673471,2017-03-16 15:29:27 UTC,"I actually think this should be handled in the notification-center-to-be, so that the queued notifications are there once the session is unlocked."
1673471,2017-03-16 19:55:48 UTC,"I won't disagree with that, but it's an unscheduled thing. I filed against notify-osd as it's what is providing the org.freedesktop.Notifications interface currently. There is no way in the spec to specify how private something is, so we'd need to add some custom X-property for that I think. It would also need to detect when the screen is locked and obscure or avoid showing the notifications."
1673479,2017-03-16 15:15:00 UTC,Can be worked around by manually installing with
1673483,2017-08-16 01:43:29 UTC,"Reviewed:  https://review.openstack.org/472344
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=58e7f8c3253d6f22a60ed567d95bdd4de64da5f1
Submitter: Jenkins
Branch:    stable/newton"
1673483,2017-06-08 16:08:04 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/472308"
1673483,2017-04-04 15:44:12 UTC,"The scope of ""seems potentially related"" are these bugs:
- bug 1646779
- bug 1643911
- bug 1638982
- bug 1673483 (= this one)"
1673483,2017-04-04 15:43:38 UTC,I updated the other potentially related bug to encourage considering ways to test the PPAs mentioned in comment #5
1673483,2017-03-29 17:02:32 UTC,(9:46:30 AM) clarkb: jamespage: fwiw we also have http://status.openstack.org/elastic-recheck/index.html#1643911 http://status.openstack.org/elastic-recheck/index.html#1638982 http://status.openstack.org/elastic-recheck/index.html#1646779 which are our top failures according to elastic-recheck
1673483,2017-03-29 17:02:24 UTC,"(9:56:32 AM) mriedem: clarkb: sorry if you guys already talked about this, but in https://bugs.launchpad.net/nova/+bug/1673483 there are comments from ubuntu devs that backports have been made to some packages and are available for testing,
(9:56:34 AM) openstack: Launchpad bug 1673483 in libvirt (Ubuntu) ""libvirt: test_attach_volume_shelved_or_offload_server times out waiting for device detach (which fails)"" [Medium,Triaged]
(9:56:45 AM) mriedem: clarkb: it's not clear to me if we have a way to hook testing packages in our CI?
(9:56:48 AM) clarkb: mriedem: yes but that bug isn't a problem
(9:56:57 AM) clarkb: mriedem: we have 3 other libvirt bugs that are actually major issues
(9:57:12 AM) clarkb: mriedem: and I mentioned it would be simple to modify devstack to use a ppa or just wget and dpkg -i
(9:57:47 AM) mriedem: ok, and we don't have fixes identified to backport for 1.3.3 in xenial LTS for testing yet
(9:58:06 AM) jamespage: clarkb: can I get context please on those three bugs
(9:58:16 AM) jamespage: refs would be ok for now
jamespage jamespd
(9:58:30 AM) jamespage: guessing one is bug 1643911
(9:58:30 AM) mriedem: jamespage: https://bugs.launchpad.net/nova/+bug/1643911/
(9:58:31 AM) openstack: bug 1643911 in OpenStack Compute (nova) ""libvirt randomly crashes on xenial nodes with ""*** Error in `/usr/sbin/libvirtd': malloc(): memory corruption:"""" [Medium,Confirmed] https://launchpad.net/bugs/1643911
(9:58:47 AM) clarkb: jamespage: its the three elastic recheck links I gave you above
(9:58:52 AM) clarkb: jamespage: they have links to launchpad
(9:58:56 AM) jamespage: clarkb: ta"
1673483,2017-03-22 06:47:39 UTC,"Ok, basic verifications were all good, I faced no issues on automated tests on all sort of libvirt interactions as well as migrations from/to/in-between xenial. I also have not seen any arch difference."
1673483,2017-06-08 17:00:52 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/472344"
1673483,2017-03-21 13:28:26 UTC,"Hi Kashyap,
I appreciate your check with Dan."
1673483,2017-03-17 10:17:39 UTC,"(From an IRC interaction with Dan Berrangé [danpb] and Matthew Booth
[mdbooth].)"
1673483,2017-03-16 15:36:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/446601"
1673483,2017-03-16 15:02:59 UTC,This isn't a very common failure:
1673483,2017-03-27 13:58:11 UTC,"Reviewed:  https://review.openstack.org/446601
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=33d0b029f1927a455b6b00f41b4d83ed19a694ff
Submitter: Jenkins
Branch:    master"
1673483,2017-08-11 20:13:13 UTC,"Reviewed:  https://review.openstack.org/472308
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=527834dea884d0663c1cf5f075c850e6f4a4eeaa
Submitter: Jenkins
Branch:    stable/ocata"
1673489,2017-03-16 20:30:01 UTC,"An error message appears at the top of the page
Error: Sorry, something went wrong :( Dismiss"
1673489,2017-03-17 20:27:54 UTC,Addressed by
1673489,2017-03-16 20:00:09 UTC,Could you paste the content of the error & possibly the snap you were trying to install?
1673489,2017-03-16 18:48:23 UTC,"I tested with a locally installed snap, with a store snap it switches to install as expected.
With the local snap it gets an error which I didn't see earlier.
Lowering priority"
1673489,2017-03-16 18:11:13 UTC,"I cannot reproduce it, a few questions to :"
1673498,2017-04-13 16:15:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1673498,2017-03-16 16:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1673498,2017-03-21 10:32:16 UTC,"Ok, will let this one in, but there's one thing that worries me. This change has no mention in the changelog:"
1673498,2017-03-21 16:55:08 UTC,"...ignore my last comment, it was supposed to go to the linux-gke release bug."
1673498,2017-03-24 21:46:58 UTC,This bug was fixed in the package linux - 4.10.0-14.16
1673498,2017-03-27 15:39:00 UTC,This bug was fixed in the package linux-gke - 4.4.0-1008.8
1673498,2017-04-13 16:13:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1673498,2017-04-13 16:14:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1673498,2018-07-24 09:35:24 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1673498,2017-04-24 14:07:40 UTC,This bug was fixed in the package linux - 3.13.0-117.164
1673498,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1673498,2017-04-24 14:11:40 UTC,This bug was fixed in the package linux - 4.8.0-49.52
1673498,2017-08-10 21:00:35 UTC,This bug was fixed in the package linux - 3.19.0-91.99
1673502,2017-03-16 16:27:05 UTC,"Reviewed:  https://review.openstack.org/446330
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=2b4e69740c83e2be6dd36184c9ef988a05347e27
Submitter: Jenkins
Branch:    stable/newton"
1673508,2019-07-21 10:05:40 UTC,"Hi, this appears to be the same as bug 1675825."
1673524,2017-03-25 09:26:01 UTC,this issue happened in Indian routes as well and also the positioning system has wrong cordinates these are the main bugs of OR actually
1673524,2017-03-25 09:27:07 UTC,they dont know yet how to fix coordinates issue but i presume they could fix at least the issue tiles
1673524,2017-03-25 09:24:24 UTC,Hi carlo yes it use little tiles i presume 4x4 and i know there isnt any support for these yet !
1673524,2017-03-18 08:49:27 UTC,How big is the black zone? Does this route use 4x4 tiles? They aren't supported by OR.
1673524,2017-03-16 16:59:10 UTC,"I tryed to set different options above all, use only ace texture, use msts environment but nothing came out..
the owner of this route disappeared, this route is very well done its a sin"
1673524,2017-03-16 17:00:51 UTC,scshot
1673524,2017-03-16 17:02:19 UTC,"I tryed to fix the issue with many version of the route editor TSRE5 but all of them crash before to open the route .
Thanks"
1673538,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1673539,2017-03-16 21:04:10 UTC,Could you share the output of “sudo du -sh /var/lib/snapd/assertions/” on a system where you consider this to be sizeable?
1673541,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1673547,2017-09-27 09:05:20 UTC,"It would be nice if OpenStack could figure this out across a deployment, and do something sane."
1673547,2018-04-17 11:30:05 UTC,"I even see this behavior when live migrating instances from a HPE G9 to another HPE G9 with the same CPU model, but different CPU flags. After applying HPE SPP 2018.3 there seems to be one additional CPU flag on the upgraded G9: spec_ctrl."
1673548,2019-02-14 11:58:42 UTC,"The error looks like https://bugzilla.gnome.org/show_bug.cgi?id=770754 which should be fixed on newer versions, can you try on Ubuntu 18.04 if that's still a problem?"
1673548,2017-09-12 03:59:11 UTC,Ubuntu 16.04.3 here.
1673548,2017-09-12 04:01:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673553,2018-01-04 18:36:50 UTC,Can I don't use lynx somehow? I'd like to view a source code for the HTML files.
1673553,2017-03-16 18:40:24 UTC,So how about apt-get install lynx?
1673553,2018-01-04 18:37:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673553,2017-03-16 18:19:22 UTC,Version 4.7.0.9 of mc works correctly on a html file running on Debian 6.0.10!
1673553,2018-02-25 13:51:01 UTC,"I has same problem. You can change it in mc config file: /etc/mc/mc.ext
Comment the Open and View settings and use
Include=editor"
1673554,2019-07-09 00:09:56 UTC,This test no longer fails locally nor under stress. The functionality must have been fixed since the report was filed.
1673555,2017-10-11 14:06:29 UTC,The percona-cluster charm does seem to validate that mysql is running:
1673555,2019-11-08 12:57:46 UTC,According to comment #3 this is now fixed as the associated patchset has been merged.
1673555,2019-07-10 18:58:49 UTC,"This hacluster change added more robust status:
https://github.com/openstack/charm-hacluster/commit/93644400756170bb8e37d5a5f995a54a4a3bd8dd"
1673555,2017-03-24 15:17:08 UTC,Hacluster msyql monitor:
1673556,2017-03-16 18:10:57 UTC,Version 4.7.0.9 pf mc works correctly on a html file running on Debian 6.0.10!
1673556,2017-03-16 18:15:46 UTC,"Running the command
  $ ubuntu-bug ubuntu-bug
resulted in a waring message:
   'Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.'"
1673556,2017-03-16 18:20:11 UTC,"Ignore comment # 2, it  belongs on bug #1673553!"
1673566,2017-03-16 18:54:39 UTC,https://launchpad.net/ubuntu/+source/avidemux/1%3A2.5.4-0ubuntu17/+publishinghistory
1673566,2018-02-22 23:06:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673567,2017-03-16 19:18:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673569,2017-06-05 09:47:15 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1673569,2017-03-21 22:11:02 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/448298"
1673569,2017-03-21 22:13:47 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/448299"
1673569,2017-03-21 23:28:18 UTC,"Reviewed:  https://review.openstack.org/448295
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3f985f1eda6f29180878a3d21c20c5057179486a
Submitter: Jenkins
Branch:    master"
1673569,2017-03-22 01:06:26 UTC,"Reviewed:  https://review.openstack.org/448297
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=acb19160d4d348e29a21ad57c61c7369352c4d1c
Submitter: Jenkins
Branch:    stable/ocata"
1673569,2017-03-22 01:06:50 UTC,"Reviewed:  https://review.openstack.org/448298
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c2c91ce44592fc5dc2aacee1cf7f5b5cfd2e9a0a
Submitter: Jenkins
Branch:    stable/newton"
1673569,2017-03-22 01:07:10 UTC,"Reviewed:  https://review.openstack.org/448299
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e193201fa1de5b08b29adefd8c149935c5529598
Submitter: Jenkins
Branch:    stable/mitaka"
1673569,2017-05-30 17:33:21 UTC,SRU regression testing has completed successfully for yakkety-newton and xenial-newton. Tempest results are below:
1673569,2017-05-16 14:26:14 UTC,"Hello Matt, or anyone else affected,"
1673569,2017-03-21 22:04:57 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/448297"
1673569,2017-06-01 18:28:19 UTC,This bug was fixed in the package nova - 2:14.0.5-0ubuntu1
1673569,2017-06-01 18:28:33 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1673569,2017-06-05 09:47:19 UTC,"This bug was fixed in the package nova - 2:14.0.5-0ubuntu1~cloud0
---------------"
1673569,2017-03-23 01:36:37 UTC,"Reviewed:  https://review.openstack.org/448610
Committed: https://git.openstack.org/cgit/openstack/ossa/commit/?id=c54ed705df6588194d134abe1762aae5e0e5a39b
Submitter: Jenkins
Branch:    master"
1673569,2017-03-21 22:01:28 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/448295"
1673569,2017-05-15 17:16:38 UTC,"Hello Matt, or anyone else affected,"
1673569,2017-03-21 15:08:07 UTC,"Thanks Matt, I've switched this to Public Security and am moving forward with the CVE assignment request using the impact statement from comment #10."
1673569,2017-03-21 17:34:10 UTC,"Removed unneeded security tag, as the bug type is already security (we use the former for hardening opportunities and the latter for vulnerabilities)."
1673569,2017-03-16 18:51:58 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1673569,2017-03-16 20:09:47 UTC,"Hmm, so the problem is that the notifier is hooked directly into the logger, and when it sends the notification it tries to include all of the args to the logger.  In this case that includes the Nova context, which contains sensitive data."
1673569,2017-03-16 20:29:01 UTC,"I'm pretty sure notifications aren't considered a secure channel. If you're sending over rpc you should have ssl configured. But it's not required, and I remember long ago when the IBM product I was working on was using QEMU we were getting internal security audit flags because QEMU was logging credentials that were sent over the wire."
1673569,2017-03-17 17:16:46 UTC,Looks like the original change to strip the context out of the notification payload happened in Grizzly:
1673569,2017-03-17 17:22:12 UTC,The actual Tempest aggregate negative tests are very old:
1673569,2017-03-17 16:58:09 UTC,We have a fix here:
1673569,2017-03-17 17:24:25 UTC,All of the backports are up too:
1673569,2017-03-17 19:09:48 UTC,"Maybe there was a change to the context that caused the circular reference error?  I see a comment added in https://github.com/openstack/oslo.context/commit/f25543fcc792ebf155728a91fde06e8dc4e96cea that refers to avoiding circular references, but maybe it's not working in this case."
1673569,2017-03-20 19:32:33 UTC,"It looks like the backports are starting to get approved and merge now as well. Once they're all merged, I propose switching this bug to Public Security and following our lighter-weight our public report disclosure process from that point instead of continuing to maintain an embargo (the risk posed by this bug seems pretty minimal)."
1673569,2017-03-20 19:39:47 UTC,impact statement looks good to me and +1 making it public for the reasons fungi described.
1673569,2017-03-21 00:03:24 UTC,Impact statement looks good to me too.
1673569,2017-03-21 15:02:54 UTC,The nova fixes are merged on all branches for this now. Can we make it public security and then I can call it out in the release notes for the nova changes on stable and do a release?
1673569,2017-03-17 17:24:04 UTC,"https://review.openstack.org/#/c/309679/ in oslo.messaging might have started logging the failure, but that's been around since Newton so it's very odd that we'd just start noticing this now."
1673578,2017-03-16 19:11:51 UTC,added /tmp/provision.json
1673605,2017-03-21 15:10:57 UTC,"I watched an installation with today's iso (20170321) and it was indicating that it was creating the btrfs filesystem for / when ubiquity stopped and the system rebooted. We're not getting as far as the success_command, so I don't think I can use that to copy logs out. Is there something I can do in an early_command that would work to help get logs out of the installer environment? The automation system we're using (https://code.launchpad.net/utah) uses rsyslog on the system under test after the install completes, I can look into whether it's possible to get it running during the installation. Any other suggestions would be welcome. I can also send the repacked iso or the initrd (with preseed) that we're using to anyone else who might be able to recreate the issue."
1673605,2017-03-20 19:00:41 UTC,"Did you not understand that /@ is a directory, not a file?  Look in /@/var/log/installer."
1673605,2017-03-21 14:08:57 UTC,I'm running these on a fast VM host. Is there any chance that the filesystem doesn't finish syncing before the qemu/kvm/libvirt VM restarts? That could explain the difference in contents between the different installs.
1673605,2017-03-21 13:49:56 UTC,"It looks like the installation never finished, but you say it appeared to finish, and prompt to restart?  Strange..."
1673605,2017-03-20 20:08:23 UTC,"I ran the test again. This time, I did get a /var directory under @ on the partition, but it's empty. /usr and /lib are populated; I can get a full file list if necessary, but it's very long, unlike the previous install. The preseed in use is here:
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/desktop/view/head:/preseeds/default_btrfs.cfg
The only difference between that and the preseed here that works:
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/desktop/view/head:/preseeds/default.cfg
is this line:
d-i partman/default_filesystem string btrfs"
1673605,2017-03-20 19:39:09 UTC,"As I previously attempted to convey, that is an exhaustive list of files on the partition. This is the output of ls -lR:
.:
total 0
drwxr-xr-x 1 root root 40 Mar  9 15:57 @
drwxr-xr-x 1 root root  0 Mar  9 15:56 @home"
1673605,2017-03-20 15:41:44 UTC,The list I gave before comprised all of the files on the drive. The log files do not appear to be available after the installations I've seen complete. That was after mounting the only partition on the drive as well.
1673605,2017-03-17 18:59:31 UTC,"It used to be that you would see /@, which is normally mounted in /, and /@home, which is normally mounted in /home, thus the log files would be under /@/var/log/installer.  I am not sure where these other directories came from."
1673605,2017-03-17 19:20:46 UTC,"Is there a convenient way to access the installer environment on a preseeded install? I recall being able to ctrl-alt-f1, etc. in the past, but I think that's restricted on more recent builds. I can put a delay in the ubiquity success command to give myself the opportunity to get in and grab the installer logs, but I'm not sure how to get in to do so."
1673605,2017-03-17 15:16:02 UTC,"When I mount the disk image leftover after the install, I get a single btrfs partition containing the following files:
.
./@
./@/home
./@/swapfile
./@/etc
./@/etc/fstab
./@/media
./@home"
1673605,2017-03-17 12:42:26 UTC,Please attach /var/log/syslog and /var/log/partman after the install finishes.  They are copied to the hard drive under /var/log/installer/ if you have already left the live environment.
1673605,2017-03-16 20:52:58 UTC,Last successful install was 2016-12-08
1673605,2017-03-20 14:42:26 UTC,"As I have been saying, they are copied to the hard drive at the end of the installation process, so you can just get them off of there."
1673608,2017-03-16 22:23:34 UTC,"I currently tell my students to save a new default.svg document to the user profile templates folder, that way they know more about where persistent custom templates, symbols, etc, can be placed."
1673608,2019-07-29 22:13:27 UTC,I guess this can be considerd fixed;
1673613,2017-05-30 15:54:25 UTC,This issue was fixed in the openstack/nova 15.0.5 release.
1673613,2017-05-26 00:28:17 UTC,"Reviewed:  https://review.openstack.org/466808
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e3076f5ff6fea598dc4ad2de9b5cb88eb083688b
Submitter: Jenkins
Branch:    stable/newton"
1673613,2017-05-23 23:55:50 UTC,"Reviewed:  https://review.openstack.org/466774
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b501fa7a926943238ff5b88ef94aaaf642765e73
Submitter: Jenkins
Branch:    stable/ocata"
1673613,2017-05-22 16:45:26 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/466808"
1673613,2017-05-22 16:40:23 UTC,"Reviewed:  https://review.openstack.org/464088
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a9a620ea2d06e51c01b0864d7275b57d7203e5a
Submitter: Jenkins
Branch:    master"
1673613,2017-05-22 15:34:16 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/466774"
1673613,2017-05-11 22:30:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/464088"
1673613,2017-05-11 21:53:51 UTC,"Dropping this from critical to high since you can work around it by passing the database connection URL in on the command line, which I know people don't necessarily want to do, but it's an option to get around this for now while working on a fix."
1673613,2017-05-30 16:05:10 UTC,This issue was fixed in the openstack/nova 14.0.7 release.
1673613,2017-05-11 19:01:26 UTC,This is an upgrade failure so marking it as critical.
1673613,2017-05-10 23:24:36 UTC,/subscribe
1673613,2017-03-20 08:50:42 UTC,"> it is no longer possible that passwords for the nova, nova_api db contain reserved characters for URL/URI
"
1673613,2017-03-18 14:58:08 UTC,I believe I found the reason behind:
1673613,2017-03-17 16:44:30 UTC,"And to the placement database: There is some misleading information in the docs wrt to 'database term' for placement in Ocata. Was corrected in another bug. However, extra installation for placement (wsgi) were required with apt install nova-placement-api and subsequent config as an extension for the nova-api."
1673613,2017-03-17 16:41:07 UTC,Apologies - here my nova-api.log
1673613,2017-03-17 08:27:08 UTC,'openstack --debug server list' outputs a lot )
1673613,2017-05-11 21:37:55 UTC,"Ah I see, the ? in the password is throwing off urlparse so you get something like this:"
1673613,2017-06-08 21:52:27 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1673624,2017-03-16 23:08:53 UTC,"Hi James, if you're in a position to be able to prepare updates it could be released via the SRU process. For more information please see https://wiki.ubuntu.com/StableReleaseUpdates ."
1673624,2017-03-16 23:21:54 UTC,"I don't know enough about fail2ban to prepare an upgrade. My altered line works, but it may have edge cases that cause issues for other users. I was looking for feedback from experienced developers familiar with this package."
1673631,2020-09-21 03:02:26 UTC,Thank you for reporting this bug to Ubuntu.
1673631,2020-11-20 04:19:24 UTC,[Expired for lxpanel (Ubuntu) because there has been no activity for 60 days.]
1673636,2017-03-17 06:27:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673638,2017-03-17 00:52:33 UTC,I looked at the inheritance of swift3's ErrorResponse [1] and the implementation of swob's HTTPException [2] - I think we can do better than just log the str of the exception in swift3 [3]
1673645,2017-07-16 05:25:09 UTC,"May or may not be the same as the icons disappearing bug that happens in 4.4. I updated again hoping that it would be fixed but it isn't!!
https://askubuntu.com/questions/582980/missing-letters-in-menus-and-folder-names/606583#comment1399040_606583"
1673647,2017-03-17 02:10:31 UTC,"StacktraceTop:
 __strftime_internal (s=0x7ffe59b29f80 """", maxsize=64, format=0x6d61726170207478 <error: Cannot access memory at address 0x6d61726170207478>, tp=0x7f2c770924a0 <_tmbuf>, tzset_called=tzset_called@entry=0x7ffe59b29f5f, loc=0x7f2c7708e400 <_nl_global_locale>) at strftime_l.c:549
 __GI___strftime_l (s=<optimized out>, maxsize=<optimized out>, format=<optimized out>, tp=<optimized out>, loc=<optimized out>) at strftime_l.c:459
 dclock_update_display ()
 ?? ()
 ?? ()"
1673647,2020-09-20 23:32:10 UTC,Thank you for reporting this bug to Ubuntu.
1673647,2020-11-20 04:17:47 UTC,[Expired for lxpanel (Ubuntu) because there has been no activity for 60 days.]
1673649,2017-03-17 02:24:50 UTC,"StacktraceTop:
 OsAbort ()
 AbortServer ()
 FatalError ()
 xf86PostProbe ()
 InitOutput ()"
1673649,2017-04-06 10:10:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1673649,2017-10-25 06:47:10 UTC,"I unfortunately installed Beignet after invoking the nvidia driver, then I had problems vith Nvidia so I reverted to nuevo graphics, but the problem persist!"
1673649,2018-04-10 01:57:11 UTC,"I've been getting this when waking from sleep.   I have a weird experience before with sleep on this computer, where I was running linux mint 18.something, and I noticed that it wasn't going to sleep all the time.  It was a weird thing where opening the laptop when a sleep was already initiated would pause the sleep from happening even if the laptop was closed again.  I was playing with this, opening and closing the laptop when I noticed some errors.  It wasn't recovering, and things were getting weird, so I decided to reboot...  I never did boot off that ssd again.  Luckily, I was able to read ALL the data off the drive, just couldn't write to it, or boot off it."
1673649,2018-11-10 09:10:04 UTC,I'm not sure but I think in my case this happens after starting up from standby.
1673649,2019-01-31 08:40:39 UTC,I have been facing this issue for a couple of months and still couldn't find any solution.
1673649,2017-10-27 06:58:07 UTC,"This usually happens for me when I login and the X session is started, which sends me back to the login. I have made the observation that this doesn't happen if a stable network connection is already present."
1673654,2017-03-17 10:39:01 UTC,get sikulix by sikulixsetup-1.1.1-20170314.122945-86-forsetup.jar
1673654,2017-03-17 11:33:23 UTC,"ok, thanks. Have to check."
1673654,2017-03-17 10:04:24 UTC,latest version of 1.1.1 nightly ? (Latest available Build: 1.1.1 2017-03-16_01:00nightly)
1673654,2017-03-17 15:35:59 UTC,"first impression:
the new VNC implementation does not seem to be compatible with the defined usage of the class Key.
This needs to be repaired."
1673654,2017-03-17 18:09:22 UTC,"fixed.
nightly build is running."
1673654,2017-03-18 03:16:00 UTC,well done！
1673658,2017-03-19 21:25:56 UTC,Thanks for teh report Thomi.
1673658,2017-03-20 21:37:09 UTC,"Hi Leo,"
1673658,2017-03-20 22:28:24 UTC,Further information:
1673658,2017-03-20 23:17:03 UTC,"We discovered that this is not a regression. And I'm inclined to say that snapcraft shouldn't remove any directories from the source, even if they cause python to go crazy."
1673667,2017-03-17 20:47:44 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1673667,2017-03-17 20:48:02 UTC,"Preparing to unpack .../python-libxml2_2.9.1+dfsg1-3ubuntu4.9_amd64.deb ...
  File ""/usr/bin/pyclean"", line 63
    except (IOError, OSError), e:
                             ^
SyntaxError: invalid syntax
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
  File ""/usr/bin/pyclean"", line 63
    except (IOError, OSError), e:
                             ^
SyntaxError: invalid syntax
dpkg: error processing archive /var/cache/apt/archives/python-libxml2_2.9.1+dfsg1-3ubuntu4.9_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1"
1673670,2017-03-17 06:47:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/446860"
1673670,2017-06-24 06:56:45 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/446860
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1673670,2018-01-12 19:07:39 UTC,Unassigning due to no activity for > 6 months.
1673674,2017-03-17 20:50:30 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1673674,2017-03-18 01:45:02 UTC,"hi MR.SETH ARNOLD,  thank you for you response. Now Ubuntu is going fine and sound problem was solved. Now all ok."
1673708,2017-03-28 05:49:58 UTC,Won't Fix for 9.2: the bugs of low importance/impact are not accepted for the maintenance updates.
1673708,2017-03-21 15:09:22 UTC,"It does not affect anything, actually, but needed many efforts to migrate onto new libraries. Moved to low."
1673708,2017-03-17 09:09:33 UTC,sla2 for 9.0-updates
1673710,2017-04-07 17:49:06 UTC,I would be hesitant to have any mappings in the repository -- it's too likely to go out of date.
1673710,2017-04-14 22:26:13 UTC,I think I'm coming around to this for well-defined cases.
1673710,2017-04-18 07:23:06 UTC,"Qemu might be a better candidate to get the rich history from anonscm.
And yes I see the point in not generally adding that to all things."
1673710,2017-05-18 13:48:40 UTC,"While replying I just realized that auto-adding the Alioth git if parsable might be nice as well. But still as before, people can just do so on their own - so this stays wishlist."
1673712,2018-01-25 09:04:28 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1796
1673712,2017-05-19 20:40:23 UTC,"Oops :) I think I messed up, since the URL changed to mysql-server. I have undone the change, and will check how to edit it correctly. Sorry!"
1673712,2017-09-05 11:24:48 UTC,Further investigation showed what this change happened when mysql.init script from MySQL 5.7 was merged into  build-ps/debian/percona-server-server-5.7.mysql.init
1673712,2017-09-04 12:44:09 UTC,Reason for this behavior change is how mysqld_safe is invoked by the startup script.
1673712,2017-05-19 20:38:41 UTC,Added upstream bug related to this.
1673712,2017-03-30 14:44:59 UTC,I just setup a 14.04 box yesterday with PS 5.7.17.
1673712,2017-05-16 22:58:28 UTC,"I have confirmed this issue:
When we try to increase the open_files_limit on 5.6 it's enough to change /etc/security/limits.conf, but for 5.7 it only gets applied if we change /etc/pam.d/common-session"
1673712,2017-05-17 06:06:10 UTC,"fwiw, mysqld honors the limits as indicated in /etc/security/limits.conf but ignores its own limits:"
1673712,2017-04-07 17:02:57 UTC,"I confirm that workaround (adding ""session required pam_limits.so"" to /etc/pam.d/common-session)  worked."
1673714,2020-04-23 15:23:31 UTC,"FYI this is what I use as of today (not perfect but works for me):
https://git.launchpad.net/~ubuntu-server/ubuntu-helpers/tree/cpaelzer/git-to-dquilt.sh"
1673714,2018-05-31 16:21:51 UTC,"To be clear, I don't intend on working on this soon. I was just driving past and I like to have features defined. Then anybody can implement :)"
1673714,2018-05-31 16:21:21 UTC,I like the idea of making it clear what the heuristic proposes and telling the user exactly what option to override.
1673714,2018-05-31 16:06:54 UTC,"I totally like the suggestion, but I'd want to add one thing - please let the default be a ""this is what I'd do - Y/N"""
1673714,2018-06-01 04:24:35 UTC,"While I'd prefer the default to be prompting I'm not on a mission to zealously convince you.
I think I could live with Report what has been done + ""if you want to modify use git reset ..."".
BTW - The actual diff content can be shortened on this btw, mostly interested on headers and lets say one hunk."
1673714,2017-04-18 11:55:12 UTC,"dquilt info https://www.debian.org/doc/manuals/maint-guide/modify.en.html
Feel free to ping for discussion as needed."
1673714,2017-04-07 17:39:11 UTC,What is 'dquilt'?
1673714,2018-05-31 12:38:35 UTC,How about something like this:
1673722,2017-03-20 14:20:57 UTC,"On Fri, Mar 17, 2017 at 09:47:14AM -0000, Julien Duponchelle wrote:

> Hi,
>
> Since this commit:
> https://github.com/qemu/qemu/commit/bc0f0674f037a01f2ce0870ad6270a356a7a8347
>
> We can no longer use the IOSvL2 image from Cisco. The problem is we got a lot of warning message saying:
> e1000: Reading register at offset: 0x00002410. It is not fully implemented.
>
> User got so much of this warning that they can't use the VM.
"
1673722,2017-03-20 14:58:56 UTC,"On 20 March 2017 at 14:20, Stefan Hajnoczi <email address hidden> wrote:

> On Fri, Mar 17, 2017 at 09:47:14AM -0000, Julien Duponchelle wrote:
>> Hi,
>>
>> Since this commit:
>> https://github.com/qemu/qemu/commit/bc0f0674f037a01f2ce0870ad6270a356a7a8347
>>
>> We can no longer use the IOSvL2 image from Cisco. The problem is we got a lot of warning message saying:
>> e1000: Reading register at offset: 0x00002410. It is not fully implemented.
>>
>> User got so much of this warning that they can't use the VM.
>
> CCing the author and maintainers.
>
> DBGOUT() is compiled in by default.  Warnings that can be triggered at a
> high rate by the guest should be off by default or use a
> printf_once()-style macro so they are only printed once and not again.
>
> Leonid: do you want to adjust e1000 DBGOUT() usage to avoid printing
> guest-triggerable messages by default?
"
1673722,2017-03-21 05:18:57 UTC,"On 2017年03月20日 22:58, Peter Maydell wrote:

> On 20 March 2017 at 14:20, Stefan Hajnoczi <email address hidden> wrote:
>> On Fri, Mar 17, 2017 at 09:47:14AM -0000, Julien Duponchelle wrote:
>>> Hi,
>>>
>>> Since this commit:
>>> https://github.com/qemu/qemu/commit/bc0f0674f037a01f2ce0870ad6270a356a7a8347
>>>
>>> We can no longer use the IOSvL2 image from Cisco. The problem is we got a lot of warning message saying:
>>> e1000: Reading register at offset: 0x00002410. It is not fully implemented.
>>>
>>> User got so much of this warning that they can't use the VM.
>> CCing the author and maintainers.
>>
>> DBGOUT() is compiled in by default.  Warnings that can be triggered at a
>> high rate by the guest should be off by default or use a
>> printf_once()-style macro so they are only printed once and not again.
>>
>> Leonid: do you want to adjust e1000 DBGOUT() usage to avoid printing
>> guest-triggerable messages by default?
> If we want to report ""whoops, we don't implement this yet"" messages then
> the recommended way to do that is
>   qemu_log_mask(LOG_UNIMP, ""...."");
>
> (these are not reported by default but only if the user asks for them.)
>
> thanks
> -- PMM
>
"
1673722,2017-05-05 13:08:22 UTC,"I sent a patch to the mailing list:
http://lists.nongnu.org/archive/html/qemu-devel/2017-05/msg01294.html"
1673722,2020-11-08 09:21:56 UTC,"I think this has been fixed by:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=b4053c64833"
1673725,2017-03-20 15:10:32 UTC,What about moving between main and side stage?
1673727,2017-03-20 10:20:34 UTC,"Hi Rick,
thank you for taking the time to report this bug and helping to make Ubuntu better."
1673732,2017-03-17 12:28:20 UTC,"The attachment ""corrected .desktop entry"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1673741,2017-03-17 11:00:10 UTC,This change was made by a bot.
1673744,2017-03-17 15:15:04 UTC,"Yes, old versions of fwupd verified the contents of the .inf file, and new ones do not. This was done to avoid subtle incompatibilities with files submitted into Windows Update. If you want it to work with 16.04, I think you can safely omit the .inf file in the cab file."
1673744,2017-03-21 08:22:52 UTC,"@Richard,
Do you mean that *.cab only needs to include firmware.bin and firmware.metainfo.xml?
For old and new version can both support by removing firmware.inf from *.cab?"
1673749,2017-03-18 06:15:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447188"
1673749,2017-04-25 14:51:03 UTC,"Reviewed:  https://review.openstack.org/447188
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=5d52d3af8a37782aa3bc0f47e9c3c68276c27545
Submitter: Jenkins
Branch:    master"
1673749,2017-04-26 23:01:49 UTC,"https://review.openstack.org/447188 has implements the API tests, so I think this bug should be close."
1673749,2020-04-02 12:26:08 UTC,Part of tempest since 16.1.0 release.
1673750,2018-06-04 07:01:42 UTC,"Change abandoned by Vladimir Khlyunev (<email address hidden>) on branch: master
Review: https://review.openstack.org/450695
Reason: more than 1 year old"
1673754,2017-03-18 03:30:00 UTC,"Should this be taken up in Octavia/OSC plugin ?
This seems more of a client issue than an API issue ( IIUC )"
1673754,2017-03-24 18:07:23 UTC,"I think it is a neutron-lbaas bug, it should just put them into ERROR if there are no agents to service the request.  They can then be deleted from ERROR."
1673755,2017-03-17 11:39:03 UTC,"Note that the edit_account permission can be requested in addition to whatever permissions snapcraft currently requests (package_upload, I imagine)."
1673757,2018-01-24 07:50:54 UTC,Opened a PR addressing the issue: https://github.com/snapcore/snapd/pull/4528
1673758,2017-03-22 14:10:03 UTC,"Šią klaidą jau ir pats kiek anksčiau vėl pastebėjau (commit pending)
Buvau tikras, kad seniai pataisyta (kiek pamenu, tai mažne prieš 5+ metus šią klaidą pastebėjau pirmą kartą ir turėjau netgi pataisyti, bet matyt mane vis apgaudavo mano persdict.dat, kuris prieš 1-2 metus nusinulino). Klaida sena, atkeliavusi kartu su lietuviu.ivpk (nuo ispell v1.0, 2003)"
1673768,2018-01-31 11:46:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/539502"
1673768,2018-01-31 15:04:04 UTC,"Reviewed:  https://review.openstack.org/539500
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=8db78cb36a6973057e52930d3944f5b66ae597f4
Submitter: Zuul
Branch:    master"
1673768,2018-01-31 11:44:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/539500"
1673768,2018-01-31 15:03:53 UTC,"Reviewed:  https://review.openstack.org/539502
Committed: https://git.openstack.org/cgit/openstack/ironic-inspector/commit/?id=34324112e085ebba8977730f11950fd5787705fd
Submitter: Zuul
Branch:    master"
1673768,2017-05-30 06:19:03 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/466200"
1673768,2017-05-23 17:48:40 UTC,"Reviewed:  https://review.openstack.org/466175
Committed: https://git.openstack.org/cgit/openstack/python-ironicclient/commit/?id=dcbe8d550bde0ae9ebb400780a4636327084d491
Submitter: Jenkins
Branch:    master"
1673768,2017-05-19 09:14:06 UTC,"Reviewed:  https://review.openstack.org/466155
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=1dc033f6b3b376162c78c6a1152acd0b2e057c10
Submitter: Jenkins
Branch:    master"
1673768,2017-05-19 06:26:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/466200"
1673768,2017-05-19 04:21:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/466175"
1673768,2017-05-19 02:36:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/466155"
1673768,2017-05-20 16:05:35 UTC,"Reviewed:  https://review.openstack.org/466198
Committed: https://git.openstack.org/cgit/openstack/ironic-python-agent/commit/?id=efe739f039f4bcdbf79e29d0c5cbf4302f5fa8af
Submitter: Jenkins
Branch:    master"
1673773,2017-03-29 08:12:09 UTC,"v_netconfig task has been removed, please re-check it out against latest iso."
1673773,2017-09-12 07:01:14 UTC,"I get the message: ""All nodes are finished. Failed tasks: Task[v_netconfig/1]"" v_netconfig seems to be still in use. I used the fuel 11 version from fuel-infra.org."
1673775,2017-03-20 07:15:42 UTC,"Workaround, based on Michael's comment and guidance over IRC:"
1673775,2017-03-17 20:21:11 UTC,From a recent email thread
1673775,2017-03-17 12:59:22 UTC,The unity8-session snap does provide that interface.  But it is not installed by default.
1673776,2017-03-17 13:01:50 UTC,http://logs.openstack.org/45/446645/3/check/gate-kolla-dsvm-build-ubuntu-source-ubuntu-xenial/491986d/console.html#_2017-03-17_12_14_44_932837
1673776,2017-03-18 14:30:52 UTC,"Reviewed:  https://review.openstack.org/447053
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=b96334db89fa1bf4f64a22b59a87acf1f5e98090
Submitter: Jenkins
Branch:    master"
1673776,2017-03-22 16:21:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/448666"
1673776,2017-03-23 02:39:26 UTC,"Reviewed:  https://review.openstack.org/448666
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=f5a9c8c71c7b663ea286fd6779997053713a05fb
Submitter: Jenkins
Branch:    master"
1673776,2017-06-09 15:36:21 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1673777,2017-03-22 07:38:31 UTC,@Eman - Could you please give details on your operating system?
1673777,2017-03-17 18:05:29 UTC,I forgot to mention that I've tested it on r15598.
1673777,2017-07-02 15:28:50 UTC,https://bugs.launchpad.net/inkscape/+bug/1701930/+attachment/4907943/+files/crash.svg is also another very simple reproducer for this bug.
1673777,2017-03-22 22:50:02 UTC,Under archlinux this bug happens.
1673777,2017-03-17 18:02:54 UTC,I confirm. Also noticed that crash happens only when snapping is enabled. Backtrace attached.
1673777,2019-04-16 12:54:37 UTC,"Hi - thanks for reporting this bug, as part of the migration to Inkscape's new
bug tracker on GitLab, I have closed it here. That's all Invalid means."
1673778,2019-07-09 00:23:23 UTC,The functionality must have been fixed as part of other work since I cannot reproduce this failure locally under stress.
1673779,2019-07-09 00:29:22 UTC,Watchers is the area that got a lot of attention and wonderful fixes since this report was filed. I cannot get this test to fail locally under stress.
1673789,2017-10-03 23:32:19 UTC,"Reviewed:  https://review.openstack.org/507816
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=41aeb89cae68a0e2ce03a248226488d4ba2ea8af
Submitter: Jenkins
Branch:    stable/newton"
1673789,2017-03-17 14:13:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447009"
1673789,2017-03-17 17:52:38 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/447082"
1673789,2017-03-20 02:57:47 UTC,"Reviewed:  https://review.openstack.org/447009
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=20f00553d0d8ed791105d5f7fc8798b9ac6a6a53
Submitter: Jenkins
Branch:    master"
1673789,2017-03-21 23:48:07 UTC,"Reviewed:  https://review.openstack.org/447082
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=983f7211a872a5be9698d7c57fda41020765a64a
Submitter: Jenkins
Branch:    stable/ocata"
1673789,2017-04-06 12:46:20 UTC,This issue was fixed in the openstack/python-novaclient 8.0.0 release.
1673789,2017-05-08 21:46:37 UTC,This issue was fixed in the openstack/python-novaclient 7.1.1 release.
1673789,2017-09-27 10:52:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/507816"
1673789,2017-10-05 10:37:06 UTC,This issue was fixed in the openstack/python-novaclient 6.0.2 release.
1673793,2017-03-17 14:41:32 UTC,"The ""-P"" option to mysql client could automatically imply ""--protocol=TCP"", by the way, or give an error if it is using socket. Since it makes no sense at all to give -P option when connecting through socket."
1673793,2017-03-17 15:03:12 UTC,Some details from mysql log file below.
1673793,2018-01-17 08:19:28 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1962
1673796,2017-03-18 19:32:11 UTC,"Just tried kernel 4.11.0-041100rc2-generic one. Looks like that the bug is happening (had some issues compiling the DKMS nvidia-357 and virtualbox, but still could boot up that kernel)."
1673796,2017-03-17 18:45:16 UTC,It started happening after upgrade from Ubuntu 16.04 to 16.10. Kernels affected are: 4.8.0-42 and 4.8.0-41 AFAIK.
1673796,2017-05-07 21:41:44 UTC,Looks like this problem is not happening on suspend/resume for my 17.04 - Dell XPS 15 9550.
1673796,2017-03-17 15:01:03 UTC,This change was made by a bot.
1673796,2017-03-25 23:37:27 UTC,I believe it happens prior to 4.8.0-41. Since I upgraded the kernel from 4.6.4 to 4.8.0-32 i started having this exact same problem. I'm on a desktop running mint 18 (ubuntu 16.10 based).
1673796,2017-03-17 15:01:14 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1673796,2017-04-12 11:57:55 UTC,I recently purchased a Dell XPS 13 and installed 16.10 on it. I'm experiencing the same issue where I must restart my wifi service after the computer sleeps. I'll be upgrading to 17.04 as soon as it's released and will let you know if the issue still exists.
1673819,2017-03-17 15:40:32 UTC,"StacktraceTop:
 brw_upload_state_base_address (brw=brw@entry=0x7fd96437e038) at ../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:1055
 brw_upload_pipeline_state (pipeline=BRW_RENDER_PIPELINE, brw=0x7fd96437e038) at ../../../../../../src/mesa/drivers/dri/i965/brw_state_upload.c:847
 brw_upload_render_state (brw=brw@entry=0x7fd96437e038) at ../../../../../../src/mesa/drivers/dri/i965/brw_state_upload.c:905
 brw_try_draw_prims (indirect=0x0, stream=0, xfb_obj=0x0, max_index=<optimized out>, min_index=<optimized out>, index_bounds_valid=<optimized out>, ib=<optimized out>, nr_prims=1, prims=<optimized out>, arrays=0x56207d8f5208, ctx=0x7fd96437e038) at ../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:597
 brw_draw_prims (ctx=0x7fd96437e038, prims=<optimized out>, nr_prims=1, ib=<optimized out>, index_bounds_valid=<optimized out>, min_index=<optimized out>, max_index=<optimized out>, gl_xfb_obj=0x0, stream=0, indirect=0x0) at ../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:688"
1673821,2017-06-01 08:04:51 UTC,"Change abandoned by Bence Romsics (<email address hidden>) on branch: master
Review: https://review.openstack.org/447035"
1673821,2017-03-20 02:09:07 UTC,Hi Bence:
1673825,2017-11-10 15:14:34 UTC,"Debian Stretch (9.2) too, very annoying,
 why i can choose every package ..."
1673825,2018-07-02 11:15:31 UTC,"Well, ""supported by DevStack"" is a term of questionable quality. As long as there is no CI testing, we cannot do much more than accept patches if people find issues."
1673825,2018-07-14 21:08:10 UTC,"Hi! I have just pushed a change for this to Gerrit, but it's my first change that goes through the official development cycle. So please have a look here:"
1673832,2017-03-21 09:25:34 UTC,"The following was logged while running on Xenial:
2017-03-20 09:03:39.063 31121 DEBUG os_vif [-] Plugging vif VIFBridge(active=True,address=fa:16:3e:09:e0:2d,bridge_name='qbr3e519fd3-c6',has_traffic_filtering=True,id=3e519fd3-c671-4627-ba39-f9fcebf3d2f3,network=Network(483f2685-846c-4a46-83fc-9e5cc4243451),plugin='ovs',port_profile=VIFPortProfileOpenVSwitch,preserve_on_delete=False,vif_name='tap3e519fd3-c6') plug /usr/local/lib/python2.7/dist-packages/os_vif/__init__.py:79
2017-03-20 09:03:39.065 31121 INFO oslo.privsep.daemon [-] Running privsep helper: ['sudo', 'privsep-helper', '--config-file', u'/etc/kuryr/kuryr.conf', '--privsep_context', 'vif_plug_ovs.privsep.vif_plug', '--privsep_sock_path', '/tmp/tmpw_hQ_9/privsep.sock']
2017-03-20 09:03:39.480 31121 INFO oslo.privsep.daemon [-] Spawned new privsep daemon via rootwrap
2017-03-20 09:03:39.481 31121 DEBUG oslo.privsep.daemon [-] Accepted privsep connection to /tmp/tmpw_hQ_9/privsep.sock __init__ /usr/local/lib/python2.7/dist-packages/oslo_privsep/daemon.py:332
Traceback (most recent call last):
  File ""/usr/lib/python2.7/logging/__init__.py"", line 861, in emit
    msg = self.format(record)
  File ""/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py"", line 100, in format
    return logging.StreamHandler.format(self, record)
  File ""/usr/lib/python2.7/logging/__init__.py"", line 734, in format
    return fmt.format(record)
  File ""/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py"", line 273, in format
    for arg in record.args:
TypeError: 'NoneType' object is not iterable
Logged from file daemon.py, line 506
Traceback (most recent call last):
  File ""/usr/lib/python2.7/logging/__init__.py"", line 861, in emit
    msg = self.format(record)
  File ""/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py"", line 100, in format
    return logging.StreamHandler.format(self, record)
  File ""/usr/lib/python2.7/logging/__init__.py"", line 734, in format
    return fmt.format(record)
  File ""/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py"", line 273, in format
    for arg in record.args:
TypeError: 'NoneType' object is not iterable
Logged from file daemon.py, line 395
Traceback (most recent call last):
  File ""/usr/lib/python2.7/logging/__init__.py"", line 861, in emit
    msg = self.format(record)
  File ""/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py"", line 100, in format
    return logging.StreamHandler.format(self, record)
  File ""/usr/lib/python2.7/logging/__init__.py"", line 734, in format
    return fmt.format(record)
  File ""/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py"", line 273, in format
    for arg in record.args:
TypeError: 'NoneType' object is not iterable
Logged from file daemon.py, line 414
Traceback (most recent call last):
  File ""/usr/lib/python2.7/logging/__init__.py"", line 861, in emit
    msg = self.format(record)
  File ""/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py"", line 100, in format
    return logging.StreamHandler.format(self, record)
  File ""/usr/lib/python2.7/logging/__init__.py"", line 734, in format
    return fmt.format(record)
  File ""/usr/local/lib/python2.7/dist-packages/oslo_log/format..."
1673832,2017-03-24 10:15:07 UTC,"Here's another bit of logs, that look interesting:"
1673832,2017-04-26 11:02:12 UTC,"The issue is that privsep, as it is used from os-vif, tries to use sudo to run things as root. However, CNI is already run as root. So this makes little sense. The privsep mode that should be used is Method.FORK."
1673836,2017-03-17 20:59:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1673836,2017-03-17 20:58:54 UTC,"Hello, I suggest trying sudo apt-get install --reinstall libevent-2.0-5"
1673838,2017-03-23 16:26:21 UTC,The same exact thing is true for `resource2.Body('OS-EXT-SRV-ATTR:host')`.
1673838,2017-12-22 16:41:58 UTC,In d37805e18f510113e2377377cb970f9154d47631 this was fixed. However the part of `'OS-EXT-SRV-ATTR:host'` was not added there and should probably still be added.
1673842,2017-04-04 12:45:37 UTC,Hello and thank you for sending your problem.
1673842,2017-06-13 11:06:52 UTC,"quickfix would be to change the installation settings on your offline system:
 1. Go To Settings
  2. Change the Default Installer to dpkg
   3. Hit the green Save button"
1673855,2017-03-17 21:00:27 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1673877,2017-04-05 23:45:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/453926"
1673886,2017-03-17 22:54:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447162"
1673886,2017-03-20 04:36:59 UTC,"The document as specified in the description portion describes Node as another resource in addition to System (page 9 - RSAServiceRoot) as opposed to substituting System altogether. Hence, do you see it as a possible scenario to propose this change? Isn't it better to have a separate resource from code side to represent /redfish/v1/Nodes ? I can also understand that the schema properties of these 2 resources (Systems and Nodes) could be very similar.. but what if there is any single mismatch or deviation? The whole new designing ball game may pop up then, like :class:`Node` inheriting from :class:`System` and overwriting suitable properties (just for example purpose)"
1673886,2017-03-22 22:10:21 UTC,"Change abandoned by Lin Yang (<email address hidden>) on branch: master
Review: https://review.openstack.org/447162
Reason: No needed anymore after patch https://review.openstack.org/#/c/448539/"
1673886,2017-06-07 05:34:32 UTC,"Hi Lin, Just wondering if this bug can be used an associative one for addition of other resources apart from ``ComposedNode``, like Managers, SessionService etc. I need a bug to be associated with this patch: https://review.openstack.org/#/c/441236 . The topic of this bug seems apt. Could you add ""support for addition of Manager resource"" to this bug description? In the meanwhile I am associating this with the patch. Let me also know if you want me to submit a fresh bug (rfe) for Manager resource instead. Thanks in advance."
1673886,2017-06-28 17:26:18 UTC,"Reviewed:  https://review.openstack.org/441236
Committed: https://git.openstack.org/cgit/openstack/sushy/commit/?id=bdce45aa43a52d6fc6dc78204592ac3e9b5b43e9
Submitter: Jenkins
Branch:    master"
1673893,2017-03-17 22:22:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447156"
1673893,2017-03-20 17:04:40 UTC,"Reviewed:  https://review.openstack.org/447156
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=b9d23caf895ec070976ea6d222b7f6f3f48939c8
Submitter: Jenkins
Branch:    master"
1673902,2019-10-14 19:19:22 UTC,Thank you for implementing it!
1673902,2017-09-18 16:34:47 UTC,"Hi,"
1673902,2017-05-01 12:30:18 UTC,"2 comments:
- YNAB has fixed color theme, which is not the case for GTK+ where user can use theme and/or change everything theirself, so a warning icon with tooltips might be safer and still accurate"
1673902,2017-05-08 14:42:59 UTC,"Yes, thanks. I can live with the filter Status with uncategorised for now."
1673902,2019-08-11 16:36:57 UTC,"I have just did this, see screenshot
When the account is part of the budget this is displayed, otherwise: not"
1673904,2017-07-22 01:56:38 UTC,"Specifically, https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1696599"
1673904,2017-07-24 19:42:47 UTC,"Verification-done on zesty, using shim-signed 1.32~17.04.1:"
1673904,2017-07-28 00:46:31 UTC,This bug was fixed in the package shim-signed - 1.32~16.04.1
1673904,2017-07-22 01:20:43 UTC,"I'm talking about the backports of SecureBoot patches as in Xenial, Yakkety and Zesty; those are not yet on Trusty (but I'm working on it)."
1673904,2017-07-28 00:47:07 UTC,This bug was fixed in the package shim-signed - 1.32~17.04.1
1673904,2017-08-28 15:31:54 UTC,Verification-done for trusty:
1673904,2017-08-28 15:29:46 UTC,This bug was fixed in the package shim-signed - 1.32~14.04.2
1673904,2017-07-28 00:46:39 UTC,"The verification of the Stable Release Update for shim-signed has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1673904,2017-07-21 08:53:05 UTC,"> but would work as soon as the updated grub patches for SecureBoot are available in proposed.
"
1673904,2017-06-23 19:55:20 UTC,This bug was fixed in the package shim-signed - 1.30
1673904,2017-07-19 20:05:43 UTC,"This currently doesn't work on trusty, but would work as soon as the updated grub patches for SecureBoot are available in proposed. Not changing state for now -- this is essentially ""verification-done"" since I can reproduce the correct behavior by making sure moksbstate_disabled has the right value, but broken by the missing grub patches."
1673904,2017-07-18 04:56:07 UTC,"Hello Steve, or anyone else affected,"
1673904,2017-07-17 14:51:40 UTC,"Hello Steve, or anyone else affected,"
1673904,2017-07-13 21:14:14 UTC,"An upload of shim-signed to trusty-proposed has been rejected from the upload queue for the following reason: ""needs adjusted versioned dep on grub2-common; drop ref to LP: #1624096 from changelog""."
1673904,2017-07-13 21:06:40 UTC,"Hello Steve, or anyone else affected,"
1673904,2017-07-13 21:02:47 UTC,"Hello Steve, or anyone else affected,"
1673904,2017-07-13 20:53:58 UTC,"Hello Steve, or anyone else affected,"
1673904,2017-07-20 19:05:28 UTC,"Verification-done on xenial, using shim-signed 1.32~16.04.1:"
1673908,2017-03-18 00:43:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447172"
1673923,2017-06-09 15:53:39 UTC,As bug is filed for the documentation of telegraf and it is not affecting any primary or secondary functionality of but still keeping this importance as medium :)
1673926,2019-07-10 02:53:39 UTC,"What appears to be happening is that after a minute Juju, requests details from the API a second time using a different code path and different parameters - an empty user, rather than a nil one. That second attempt fails to parse."
1673926,2019-07-10 03:39:10 UTC,Partial fix https://github.com/juju/juju/pull/10434
1673934,2017-03-29 11:04:48 UTC,"Font causing issue for me:
fonts-emojione"
1673934,2017-03-20 09:56:52 UTC,"Thanks for the report ET.
Would you mind attaching a screenshot (or picture) of the wrong rendering?
Thanks!"
1673934,2017-03-20 17:43:15 UTC,"Sure, here you go. The first picture is with gsfonts package installed, the second (in which you can actually read the page) is with gsfonts package removed."
1673934,2017-03-20 17:43:59 UTC,This is the second good render with the gsfonst package uninstalled.
1673934,2017-03-22 22:17:27 UTC,"I can reliably observe the issue on my MX4 running rc-proposed.
Note that I’m not seeing that on desktop, even after installing gsfonts-x11."
1673944,2017-03-29 13:53:39 UTC,Fix in kolla-ansible https://review.openstack.org/#/c/447650/
1673944,2017-03-20 19:16:00 UTC,Sorry - my bad - first patch and didn't quite follow the full process.
1673944,2017-03-20 16:11:22 UTC,Cannot find any recent change in gerrit related to this. Can you point out what is the change_id?
1673944,2017-03-19 10:50:55 UTC,Added to gerrit.
1673952,2017-03-18 12:10:38 UTC,For now this is the case with FreeBSD which is what FreeNAS is based upon.  It would take a bit of restructuring to move to multitasking instead of multithreading and we don't have the resources at the moment.
1673952,2020-08-21 20:43:03 UTC,I am seeing this issue to with:
1673952,2020-08-21 20:44:48 UTC,Related https://bugs.launchpad.net/duplicity/+bug/387102
1673956,2017-03-18 12:29:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1673956,2017-06-06 17:19:45 UTC,Would it be possible to receive some clarification regarding plans to support a variable number of static TLS libraries in Ubuntu?  Ideally the glibc fix mentioned in the bug description would be incorporated into Ubuntu.  Thanks!
1673957,2020-11-10 03:21:11 UTC,"Thanks for your answer! ... since this is not reproducible anymore, I'm closing the ticket now."
1673957,2020-11-08 11:42:26 UTC,Independent of the planned tracker transition: this issue would require more information by original reporter anyway.
1673957,2020-11-09 17:42:31 UTC,"Hmm… so this dates back quite long ago unfortunately, I had basically forgotten about this bug report as I had opened it while just experimenting with qemu."
1673957,2020-11-08 09:22:55 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1673961,2017-03-18 13:30:11 UTC,This change was made by a bot.
1673961,2017-03-20 13:37:21 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1673961,2017-03-20 23:43:07 UTC,The bug seems to be fixed with the kernel upstream (v4.11-rc3).
1673961,2017-03-21 21:12:29 UTC,Tested with the latest v4.11 kernel ( http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3 )
1673962,2017-03-28 22:34:42 UTC,"Additionally, this ""telemetry"" aka SPYING! Should be disabled by in future builds as well! And mozilla should be notified of this so they quit relying on this big brother data collection! I don't care if it is ""anonymous!"" NYET COMRADE!"
1673962,2017-03-18 15:08:28 UTC,https://bugzilla.mozilla.org/show_bug.cgi?id=1348569
1673962,2017-03-28 22:32:25 UTC,From the mozilla discussion can/will this resolve this???
1673970,2019-11-12 04:17:36 UTC,[Expired for kolla because there has been no activity for 60 days.]
1673970,2017-08-30 10:44:21 UTC,Any update about this bug?
1673971,2017-04-08 03:24:07 UTC,"And, done!"
1673973,2017-04-05 14:03:45 UTC,"And, done!"
1673976,2018-02-28 15:16:34 UTC,"Ok, thank you for clearing that up."
1673976,2020-12-04 22:05:51 UTC,any solution? trying to emulate a closed source amd64 app on my raspberry and i'm getting this error with qemu 5.2.0-rc4 and glibc 2.27.
1673976,2018-03-23 19:07:38 UTC,"> Actually, you only need the parent to get the status from the child, which can be passed in other way than through common memory.
"
1673976,2018-03-23 18:37:01 UTC,Hello
1673976,2018-03-05 14:02:57 UTC,"That way round the child doesn't have the shared memory with the parent, so it can't update the parent's status variable. There's no easy way to say ""fork, and then share the guest memory mappings and only the guest memory mappings with the child"", because QEMU doesn't currently track what memory the guest has mapped at all."
1673976,2018-03-05 13:35:04 UTC,"Ok, I taught that could be an issue, but as I said, I don't really know all the internals of QEMU."
1673976,2018-03-03 11:56:04 UTC,"Unfortunately that won't work, because if we do a clone(CLONE_VM) in QEMU that will mean that parent and child share not just the guest address space, but also all the QEMU data structures for the emulated CPUs and also the host libc data structures. Then actions done by the child will update those data structures and break execution of the parent when it resumes."
1673976,2018-03-02 20:59:15 UTC,"Ok, yes you are right..."
1673976,2018-02-28 15:39:46 UTC,"Commit fe05e1cb6d64db changed that, so args.err is initialized to zero."
1673976,2018-02-27 21:19:30 UTC,"That glibc change has caused the assert to go away, but QEMU's spawn(CLONE_VFORK) still does not have the ""always waits for child"" semantics that glibc has assumed since glibc commit 4b4d4056bb154. The child and the parent will end up racing each other, and the child will never be able to write to the parent's address space. I think that the effect of that race will be that if the child fails (for instance if a bad filename is passed and exec() fails) the parent will never notice and will return a success code from the spawn function when it should not."
1673976,2018-02-27 20:09:38 UTC,"This should probably be put under 'glibc', since this is really an issue with that package, which is fixed by the way since Oct 2017."
1673976,2017-11-26 20:38:05 UTC,"Interestingly, this also affects Microsoft Windows Services For Linux, i.e. Microsoft's Linux emulation layer."
1673976,2017-11-22 16:52:45 UTC,Thanks for tracking down the glibc change; I will try to set up a chroot with a more recent glibc to see whether we can do something that fixes that posix_spawn implementation...
1673976,2017-12-01 12:03:17 UTC,I have verified that this patch [1] in glibc_2.25 and glibc_2.26 fixes the assert.
1673976,2017-11-22 15:26:39 UTC,"I think I see the problem. This glibc commit rewrote the posix_spawn implementation on Linux:
https://sourceware.org/git/?p=glibc.git;a=commit;h=9ff72da471a509a8c19791efe469f47fa6977410"
1673976,2017-09-20 20:10:51 UTC,I can confirm this. The ninja build system is also affected.
1673976,2017-09-21 03:38:52 UTC,Could you please check whether the problem also occurs with QEMU v2.10?
1673976,2017-10-02 18:36:44 UTC,"Hi,"
1673976,2017-10-02 18:37:49 UTC,"# uname -a && locale-gen
Linux **** 4.13.4-gentoo #1 SMP PREEMPT Thu Sep 28 09:41:30 CEST 2017 armv7l Intel(R) Celeron(R) 2957U @ 1.40GHz GNU/Linux
 * Generating 8 locales (this might take a while) with 2 jobs
 *  (2/8) Generating en_US.UTF-8 ...
localedef: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped                                                                                                                                                                                  [ !! ]
 *  (1/8) Generating en_US.ISO-8859-1 ...
localedef: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped                                                                                                                                                                                  [ !! ]
 *  (3/8) Generating fr_BE.ISO-8859-15@euro ...
localedef: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped                                                                                                                                                                                  [ !! ]
 *  (4/8) Generating fr_BE.ISO-8859-1 ...
localedef: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped                                                                                                                                                                                  [ !! ]
 *  (5/8) Generating fr_BE.UTF-8 ...
localedef: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped                                                                                                                                                                                  [ !! ]
 *  (6/8) Generating fr_FR.ISO-8859-15@euro ...
localedef: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped                                                                                                                                                                                  [ !! ]
 *  (7/8) Generating fr_FR.ISO-8859-1 ...
localedef: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped                                                                                                                                                                                  [ !! ]
 *  (8/8) Generating fr_FR.UTF-8 ...
localedef: ../sysdeps/unix/sysv/linux/spawni.c:366: __spawnix: Assertion `ec >= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped                                                                                                                                                                                  [ !! ]
 * Generation co..."
1673976,2017-11-22 15:30:10 UTC,"Sorry, this is probably the commit that broke things (not the one above). I was added in glibc 2.25:
https://sourceware.org/git/?p=glibc.git;a=commit;h=4b4d4056bb154603f36c6f8845757c1012758158"
1673976,2017-10-16 19:23:12 UTC,It is possible to reproduce the issue with a simple clone example taken from
1673976,2017-10-16 18:04:16 UTC,Looks like the __clone() call is failing for some reason:
1673976,2017-11-20 17:33:23 UTC,Is there a way I can ask QEMU to not do this strict checking so that my stuff stops breaking?
1673976,2017-11-20 18:00:39 UTC,"Not without messing with the QEMU source, no."
1673976,2017-11-20 18:36:40 UTC,"OK, this can't be as simple as ""posix_spawn() fails"", because I've just tried the test program from the posix_spawn manpage (http://man7.org/linux/man-pages/man3/posix_spawn.3.html) and that works fine for x86-64 guest, aarch64 guest and armhf guest. In the x86 and armhf cases the libc I have seems to use the NR_vfork syscall, but for aarch64 it uses clone(CLONE_VM | CLONE_VFORK | SIGCHLD, ...) which is what the glibc sources linked in comment #5 do, and that all works fine."
1673976,2017-11-22 15:01:37 UTC,I can reproduce the bug in a mips64el chroot running current Debian unstable - the posix_spawn example you mention fails there. I have tested v2.11.0-rc2 and it fails there as well. I think you need glibc >= 2.25 to trigger the bug (artful / bionic chroot). I only noticed it due to Debian updating to a newer glibc recently.
1673976,2017-11-07 15:30:52 UTC,"This happens because QEMU is now stricter about its checking of the flags passed to clone() -- previously we would silently allow flags we couldn't support and create new threads with the wrong behaviour. Now we check and fail the clone() syscall if the requested behaviour is something we can't implement. Unfortunately we don't have any way to distinguish ""guest program is asking for something odd that it doesn't really need"" from ""guest program is asking for something odd that it does need"". So we err on the safe side and tell the guest we can't do it."
1673982,2017-03-18 15:49:19 UTC,I have the same problem and this bug is a duplicate. Try to search the bug tracker.
1673982,2017-03-19 14:58:29 UTC,"Thank you for the info, as it worked fine before my kernel update , I thought it was related and wanted to let know other users that unplug the Wifi cards can be a workaround to boot .What should I do now about my duplicate entry ?"
1673982,2017-03-19 15:07:28 UTC,"I don't know if you refer to https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1666421 taht you create but I can't find a similar bug in bugtracker ( it's my first time here ) .
The problem I have is  abit different I think , because I a m stuck at boot logo , I never go until desktop .
Another point is that I also can't change kernel version in recovery mode because USB devices ( including keyboard) are no more available from that moment , and that make finding a workaround a bit harder for me."
1673984,2017-03-24 22:40:29 UTC,This bug was fixed in the package signon-ui - 0.17+17.04.20170320-0ubuntu1
1673984,2017-03-24 09:40:02 UTC,Yes. It fixes the bug.
1673984,2017-03-24 16:12:24 UTC,I installed the packages from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2608 and can confirm that it fixes the issue.
1673984,2017-03-24 01:51:29 UTC,I installed the packages and the problem was solved.
1673984,2017-06-21 09:18:03 UTC,Ubuntu-session is now unity-session. This again breaks the code.
1673984,2017-03-23 10:17:32 UTC,"Fix available here, waiting for QA:
https://bileto.ubuntu.com/#/ticket/2608"
1673984,2017-03-20 08:24:03 UTC,"Thanks for the report, Alam!
I can confirm this. Here's the stack trace:"
1673984,2017-03-18 17:11:00 UTC,Note : I can also reproduce on 64 bit os.
1673984,2017-03-23 14:07:05 UTC,I installed the zesty packages from <https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2608> and can confirm that it fixes this bug.
1673984,2017-09-08 15:09:12 UTC,Having this same issue with 16.04 xenial. signon-ui is at version 0.17+16.04.20151125-0ubuntu1 but apt-get tells me I'm as up to date as I can be for this LTS. Does this fix need pushing to 16.04 also?
1673986,2017-03-18 17:28:31 UTC,"Mike, you probably wanted to comment here?"
1673986,2018-01-07 15:11:16 UTC,"This is a problem that we find every time we use the software (every other week).  Do you know whether and when an optional (or permanent) ""live"" button might be added?"
1673986,2017-03-18 16:42:10 UTC,"Adding/Creating tests seems rather complicated.  I am not really familiar with Python, so my venture into the code was limited to minor code changes.  If someone wants to take the burden of completing the necessary tests, please feel free."
1673998,2017-03-18 17:51:40 UTC,What does
1674033,2017-03-19 01:11:17 UTC,"""Convert symbol to group to edit"" message in the status bar actually means ""click the Cut clones' links to original button"" to edit. Symbols are like clones, but the original is hidden in the Defs section of the XML. Symbols can be accessed using the Symbols dialog: Menu: Objects>Symbols."
1674033,2017-03-19 09:19:21 UTC,"Thanks a lot for the accurate and quick reply.
Then the ""Convert symbol to group to edit"" is not very clear for new users."
1674037,2017-03-20 20:40:50 UTC,"Experienced the same thing with 4.8.0-42-generic. Followed manual method at this link and it worked, substituting 4.8.0-42 for 3.16...
http://linuxbsdos.com/2014/12/06/how-to-upgrade-the-linux-mint-17-1-kernel-from-version-3-13-to-3-16/
I first tried other methods that removed lock files, but using ""update manager"" and ""sudo apt-get install [-f]"" always failed."
1674037,2017-06-08 06:02:51 UTC,"I had ""Operation not permitted"" errors installing Linux kernels too. I am running Sophos Anti-Virus, which has a known bug. ""30s delay of file create and ""Operation not permitted"" errors with fanotify and cifs – This is a kernel issue and Sophos is working with the Linux community to fix this issue"" https://community.sophos.com/kb/en-us/118216"
1674037,2017-06-08 06:03:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674037,2021-01-07 04:11:58 UTC,4.8 EOL
1674051,2017-03-19 03:43:53 UTC,"I reported the bug above.
I just noticed the xedit also writes 218 bytes and breaks ""recently used"" for Leafpad. And so does MousePad."
1674056,2020-11-10 14:57:20 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1674056,2021-01-10 04:17:28 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1674072,2017-03-19 09:17:45 UTC,"StacktraceTop:
 jack_port_get_buffer (port=0x0, nframes=1024) at port.c:581
 fluid_jack_driver_process (nframes=1024, arg=0x5706e400) at ./src/drivers/fluid_jack.c:522
 jack_process_thread_work (arg=0x5706e4d0) at client.c:2214
 start_thread (arg=0xf6809b40) at pthread_create.c:333
 clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113"
1674075,2018-04-03 09:46:19 UTC,Could you try this: https://gist.github.com/RyanMillerC/c48d9f63f8fe386b22a7da18cf6913d2
1674081,2018-01-07 17:44:39 UTC,"As LightDM is now the default login manager in Linux Mint, you can close this bugreport."
1674093,2017-03-20 10:01:26 UTC,"When you originally downloaded the snap, if you did it with “snap download”, you will have had a .snap and a corresponding .assertion file; you can then add the assertions with “snap ack foo_NN.assertion” (*before* doing “snap install ./foo_NN.snap”; doing it after will not do what you want), and everything will be happy."
1674093,2017-03-20 16:18:15 UTC,"chipaca or zyga, could you please reply http://askubuntu.com/questions/894608/how-to-add-corresponding-assertion-for-offline-snaps-to-update ?"
1674093,2017-03-19 12:47:14 UTC,You can install snaps offline but you must also add the corresponding assrtions. A snap with matchin assertions is the same as installed from the store. In addition snapd supports delta downloads to minimize the cost of the traffic.
1674093,2017-03-21 18:18:40 UTC,Downlaoded from uAppExplorer I think the assertion file is not available.
1674093,2017-03-19 15:00:40 UTC,Thank you. I will be waiting for your feedback
1674093,2017-03-20 16:53:17 UTC,"same person also filed a bug, I responded there
https://bugs.launchpad.net/snappy/+bug/1674093"
1674093,2017-03-19 14:29:45 UTC,Hey.
1674093,2017-03-19 12:44:09 UTC,"So every snap app MUST be Installed online for being able to updated later?....  If yes, this is not good for someone with limited data plan. Some snaps are very big and downloading file.snap allow users to not have to download same files over and over"
1674093,2017-03-19 12:31:57 UTC,Unless you install the corresponding assertions you cannot update a snap that was installed from a file. What were you expecting to see?
1674093,2017-03-19 12:28:35 UTC,I've installed libreoffice offline from a local libreoffice.snap package
1674093,2017-03-19 12:24:02 UTC,"Can you please tell us how you installed libreoffice originally, which version of snapd are you running and which OS are you running it on?"
1674093,2017-03-19 12:56:27 UTC,"""You can install snaps offline but you must also add the corresponding assrtions"". How is that made? Sorry I'm not an advanced linux user"
1674114,2017-03-19 22:47:21 UTC,"It is working now without the parameters ""-machine isapc"" and ""-cpu 486""."
1674114,2020-11-10 14:57:55 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1674114,2020-12-07 11:48:38 UTC,The issue is resolved in the current release
1674116,2017-03-21 13:39:29 UTC,Possibly related report: https://bugs.launchpad.net/inkscape/+bug/743987.
1674117,2017-03-20 17:38:53 UTC,"I stumbled across this bug: https://bugs.launchpad.net/ubuntu/+source/linux-rt/+bug/367671
Im not sure if that bug relates to this one, but after disabling realtime scheduling, pulseaudio does not crash anymore.
However, the lag when starting the VM got significantly worse, the system is pretty much unusable the first ~20-30 seconds."
1674117,2017-03-25 00:39:24 UTC,"After switching from SeaBios to OVMF the issue seems to be gone, indicating a problem with the former."
1674117,2020-06-10 14:57:48 UTC,Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
1674117,2020-08-10 04:17:29 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1674122,2018-02-26 21:43:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674130,2019-07-31 20:30:51 UTC,There are quite a few instances of this bug in the support system all appear to be on MacOS
1674131,2017-03-21 17:04:33 UTC,If you right click and use copy file name/bundle it picks up the proper name.
1674131,2020-07-18 00:17:57 UTC,It seems that if i right click on a file i download and try to browse file list it will open in the root of the users file list instead of in the folder where the file is.
1674132,2019-09-20 19:25:18 UTC,Please attach a project that shows this issue and include your KiCad version information
1674132,2019-09-20 19:13:36 UTC,"The incorrect zoom behaviour still exist and it's quite annoying. I changed to confirmed. When I try to zoom any waveform I mark the area I want to see with a mouse - the rectangle outline appears and I expect to see the marked area. Instead, different part of waveform is displayed, shifted up."
1674132,2019-09-20 19:47:45 UTC,"Attached example: simple sinusoidal source, 1V, bipolar, 50Hz. Transient simulation 100ms. Try to zoom to see one period. Bottom of the waveform will be cropped (similar as in the picture attached in my previous post."
1674132,2019-06-04 21:27:35 UTC,Please attach a test project.
1674132,2019-08-04 04:17:26 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1674137,2017-03-20 02:17:00 UTC,"UPDATE:
To reverify, ifdown command fails always. net-tools is broken after the update."
1674137,2017-03-20 02:26:42 UTC,"UPDATE:
Rewrote my scripts to set enp3s0 AFTER the bridge creation and deletion.
Issue with that part over."
1674139,2019-06-04 21:28:52 UTC,Please provide a demo project that shows this behavior.
1674139,2019-08-04 04:17:27 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1674155,2020-10-20 03:33:47 UTC,"Not replicated in Inkscape 1.0.1 (0767f8302a, 2020-10-17) or Inkscape 1.0 (4035a4fb49, 2020-05-01) Linux Mint 20"
1674164,2017-04-12 09:38:40 UTC,"In my view this is not invalid: ""differently correct"" recorders and also printed DVDs are common in the wild and they work on Windows, osX and ""dumb"" readers. And as the average user is not able to figure out a workaround, he will assume that ubuntu is broken and switch to something else."
1674164,2017-04-12 14:06:03 UTC,"""differently correct"" is no less a lie than ""alternative facts"".  Your recorder is broken, period.  Complain to the manufacturer to fix their firmware or see if they already have an update.  Printed DVDs use the correct permissions.  UDF also goes on rewritable media, optical or flash or otherwise, and the correct permissions need to be retained or you end up with either files that are never executable or always executable, and no ability to write protect files."
1674164,2017-04-16 06:48:47 UTC,"""differently correct"" was meant to be a joke :)"
1674164,2017-03-21 14:12:29 UTC,"This is correct; if the disc specifies permissions, they are used.  You appear to have a brain dead recorder that specifies the wrong permissions.  As you noted, you will need to override the permissions to work around this, but it is not intended that permissions never be used by default."
1674171,2017-08-09 12:32:14 UTC,"With a new version of our test server (2.12.4) we tried to localize the server environment to Czech (we used English environment until recently). It seems that the problem has been solved by server environment localization.  So far we didn´t came across any evidence that the Czech environment would have a negative impact on any other Evergreen  feature or the English localization.
I would recommend to add piece of information to the documentation about Evergreen installation, that for some languages it necessary to use localized server environment to prevent crashes of some parts of Evergreen interfaces.
I'm not sure which particular languages are relevant for this - definitely the languages with extended ASCII characters (probably the Czech is one the worst when it comes to extended ASCII)."
1674171,2019-01-21 16:17:14 UTC,"Thanks for all your research on this, Eva.  I know that this was from years ago, but are you able to share any documentation/procedures you have on how to successfully localize the server environment?"
1674171,2019-01-29 20:29:57 UTC,The server environment localization  just means adding Czech (or other) locale to Debian configuration - as root run:
1674174,2017-03-20 14:11:30 UTC,"When one clicks the button for the endless game type, one expects the game to not end.  Unfortunately it does."
1674174,2017-03-20 14:21:32 UTC,Here is a video demonstrating the issue.
1674174,2017-03-20 11:13:22 UTC,Thank you for reporting this bug.
1674175,2017-03-20 19:44:13 UTC,"Hallo, genau dass; ich glaube, man braucht PAE-CPU fuer diese kernel. Fuer solche rechner, glaube ich, Sie mussen eine eigenene kernel bauen, from kernel.org."
1674175,2017-03-20 20:00:08 UTC,This change was made by a bot.
1674188,2018-11-30 08:29:49 UTC,"Hi from Greece,
I need desperately the same thing.
I am using the app for noting down my expenses & Income but the preview of the current status is wrong since I am getting pay the 24th of every month."
1674188,2018-12-23 15:04:00 UTC,@Tasos: so for you the current month should range from 24th to 23rd of the next month ?
1674188,2018-12-23 21:53:19 UTC,"@Maxim: Very funny :)
My reports are faulty since I am not paid my salary every 1st of the month. I have to run my own custom reports every time.
I think it is a logical request as many other requests. But ""configurable time frame of Budgeting"" was an easy to make configuration.
I REALLY NEED IT."
1674189,2019-06-03 22:31:20 UTC,This script already exists
1674191,2017-03-20 07:59:34 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1674191,2017-03-20 17:52:42 UTC,"This is a known fact of operating Swift clusters, documented in the security guide Tristan linked and also as a proposal for improvement upstream (documented publicly at https://wiki.openstack.org/wiki/Swift/ideas/network_security)."
1674191,2017-03-20 18:06:43 UTC,"Based on John's input above, this is more a class D report (security hardening opportunity) with no need for embargo nor advisory. Triaging accordingly."
1674191,2017-03-20 18:13:24 UTC,I agree with John's analysis i.e. this is publically known. Marking as a wishlist bug for swift.
1674193,2017-04-03 12:36:31 UTC,Using a core snap from beta/candidate (snapd 2.23.6) fixes the problem on debian.
1674193,2017-04-03 12:25:57 UTC,Confirmed that debian is affected by this change too.
1674193,2019-03-25 14:36:35 UTC,"The Debian testing package has been updated to 2.37.4 as seen on https://tracker.debian.org/pkg/snapd
The version in Debian stable is 2.21-2 and we have no plans to update it at this time."
1674193,2017-03-29 20:08:53 UTC,"Just to confirm, I won't need to patch the version of the snapd package in Debian to get that fix, just wait for a version of the core snap with 2.23.6+ in it?"
1674193,2017-03-31 05:18:17 UTC,@Michael: That is my guess but would good if we can check this quickly. Do you have a Debian system up and running you can quickly check on if there are any problems with updating to a newer core snap from candidate/beta/edge?
1674193,2017-04-02 23:49:44 UTC,"""snap install --edge core"" works fine in my VM, but then ""snap install
core"" has always worked for me, it's only implicit installations of the
core snap that hang."
1674193,2018-09-20 02:47:02 UTC,Bumping this since it's been over a year.
1674193,2017-03-29 14:22:26 UTC,This will be fixed for everyone with https://github.com/snapcore/snapd/pull/3101 which will be part of 2.23.6
1674193,2017-08-27 19:39:14 UTC,"sorry, but I just installed a fresh new clean debian 9.1, installed snap:"
1674193,2017-08-18 11:33:56 UTC,"I just tested this on Debian sid on with 2.27.2-2 and the bug is now fixed, installing a core snap alongside a random snap (hello snap in my case) works correctly and no longer hangs."
1674193,2017-08-17 18:54:04 UTC,"i worked around this issue by purging and reinstalling snapd, then running `snap install --edge core` before installing any snaps."
1674193,2017-08-03 08:56:15 UTC,"Note that this is *still* occurring if you install core and any snap at the same time. For example ""snap install hello"" on a system with no other snaps installed will still reproduce this issue."
1674193,2017-07-25 09:51:00 UTC,"I think the error you are seeing is caused by the following:
- snap install/refresh core
- new core gets installed, re-execs into 2.26.{9,14}
- install/refresh fails (most likely in the configure hook)
- the install/refresh in undone
- *however* the snapd is not restarted into the old version
- next time snapd runs its the 2.26.x version that assumes things like the snap-seccomp compiler are available which are not anymore"
1674193,2017-07-24 19:38:53 UTC,Additional confirm on Debian 9:
1674193,2017-07-17 12:28:10 UTC,"root@dev1:/home/petanb# snap install --edge core
error: cannot perform the following tasks:
- Setup snap ""core"" (2422) security profiles (cannot setup seccomp for snap ""core"": fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory)
- Setup snap ""core"" (2422) security profiles (fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory)"
1674193,2017-09-05 09:35:43 UTC,"Had the same on debian 9.1 but solution below somehow fixed the issue, differences from the first time install are: 1.apt instead of apt-get 2.first of all install core and then apps"
1674193,2017-03-25 09:26:27 UTC,"So… in the meantime, is there a fix for users like me who just set up an Ubuntu VPS to use a specific snap?"
1674193,2017-03-23 19:28:49 UTC,It was reported that this also happens on vanilla upstream kernel.
1674193,2017-03-24 15:23:18 UTC,I went ahead and filed https://bugs.launchpad.net/snapd/+bug/1675812 for the noisy /run/snapd.socket denial.
1674193,2017-03-23 09:10:47 UTC,We've release snapd 2.23.5-1 into openSUSE now which disables seccomp.
1674193,2017-03-23 07:35:44 UTC,Let's try snap-confine with SNAP_CONFINE_DEBUG=yes and perhaps patch it with extra logging around the established seccomp profile.
1674193,2017-03-23 05:58:54 UTC,On OpenSuse the network-bind plug of the core snap was connected too but the bind problem still appeared.
1674193,2017-03-22 20:20:58 UTC,"I couldn't reproduce this yesterday with core snap 1512 which does have the network-bind plug. So maybe that fixed it. It was added in https://github.com/snapcore/core/commit/6de4becf8a3f7af69f665b7452a93a97a50c0547 which has the commit message 'add network-bind to core-support as it appears to be required on the ""Boundary Devices Nitrogen""', so if it fixed this bug I'm pretty sure it was by accident."
1674193,2017-03-22 18:45:56 UTC,"I see problems with Ubuntu Core 16 in a VM (ie, with apparmor enabled). There the core snap is trying to access /run/snapd.socket:"
1674193,2017-03-22 17:44:20 UTC,I've investigated this a bit and found that snapctl is hanging up because it receives a seccomp denial (we build snap-confine on OpenSuse with --enable-seccomp and --disable-apparmor).
1674193,2017-03-24 16:12:28 UTC,"For completeness I booted into http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.44/ (ie, the corresponding upstream kernel for the Ubuntu release I tested on):"
1674193,2017-03-22 14:41:41 UTC,I had a look at this and it's puzzling. What is going on is that dash running the configure hook hangs on a read (presumably from a pipe) from snapctl get ... which is in a curious state. There are three processes (because golang clones) one zombie and two children. The children are sleeping and I was unable to procure a backtrace of where they were (missing symbols).
1674193,2017-03-23 19:54:30 UTC,"You can run the configure hook (or just snapctl) under confinement of
the configure hook snap-confine (or via snap run --shell --hook)"
1674193,2017-03-23 19:21:32 UTC,core snap 1512 got unreleased so this bug came back.
1674193,2017-03-23 20:42:47 UTC,"It fails the way with an upline kernel 4.10.5, config is attached"
1674193,2017-03-24 11:20:07 UTC,With snapd 2.23 now building on Fedora 25 I can reproduce the same problem without specifying --disable-seccomp for the snap-confine build.
1674193,2017-03-24 13:12:35 UTC,I'm also seeing this on Ubuntu Xenial with apparmor-enabled kernel(?) (i.e. apparmor bootscript from scaleway).
1674193,2017-03-24 13:27:07 UTC,"@lukas, well, this is also a non-ubuntu kernel ... same as mainline builds i'd guess"
1674193,2017-03-24 15:07:20 UTC,"This doesn't seem to have anything to do with upstream vs Ubuntu kernels. For example, on Ubuntu 16.04 LTS classic I see:"
1674193,2017-03-22 07:59:36 UTC,Can reproduced on openSUSE Tumbleweed and Leap 42.2 too.
1674195,2017-12-03 01:01:58 UTC,"On Sat, Dec 02, 2017 at 04:46:26PM -0000, Florent Gallaire wrote:

> > If 'local' doesn't work for some reason, we should tell the user and
> suggest they use ""--timezone original"" rather than silently ignoring
> their (explicit) preference.
>
> In theory, but not practically. Do you really want an error message for
> 1 commit /1000 of your history and be forced to switch to 'original' for
> the 999 commits that you can show as 'local' without problem ?
>
> > I don't follow why this causes out of range errors. What is the value
> of the t variable when you hit this issue?
>
> http://bazaar.launchpad.net/~bzr-
> pqm/bzr/bzr.dev/revision/6622#bzrlib/tests/blackbox/test_commit.py


I'm not sure I understand what this is actually trying to fix; I've
followed up to https://bugs.launchpad.net/bzr/+bug/1670243"
1674195,2017-12-02 15:51:09 UTC,I don't follow why this causes out of range errors. What is the value of the t variable when you hit this issue?
1674195,2017-12-02 16:46:26 UTC,"> If 'local' doesn't work for some reason, we should tell the user and suggest they use ""--timezone original"" rather than silently ignoring their (explicit) preference.
"
1674195,2017-11-24 02:59:08 UTC,bzr log --timezone local
1674195,2017-11-23 11:43:33 UTC,Can you provide some more context on what is actually going wrong here? How can we reproduce this bug?
1674195,2017-12-02 15:45:34 UTC,"If 'local' doesn't work for some reason, we should tell the user and suggest they use ""--timezone original"" rather than silently ignoring their (explicit) preference."
1674205,2017-03-27 17:30:20 UTC,"Agreed, reproduced using a LXD using ubuntu-daily:zesty. It does look like clamav-daemon, a suggests package, produces the files when it is installed as a part of its post-inst."
1674206,2017-03-22 16:08:39 UTC,"command ""vnstati -v"" print:
vnStat image output 1.14 by Teemu Toivola <tst at iki dot fi>"
1674206,2017-03-27 19:41:04 UTC,"As far as I know, this problem is caused by the internal fonts of libgd used by vnstati not supporting UTF-8."
1674206,2017-04-02 12:24:02 UTC,And on what version of libgd is vnstati based?
1674213,2018-12-28 21:02:01 UTC,Suggested fix - https://review.openstack.org/#/c/627734/1
1674213,2017-03-20 06:41:25 UTC,"In most scenario ""-f json"" output format is used for machine readable, the program or shell consume the result, not read it directly in console for human, the use case like:"
1674213,2017-04-28 21:40:14 UTC,"Most tools that handle text files are able to deal with no trailing newline at the end of the file, and in some places it is considered unnecessary.  For shell output obviously it would be nice to have, and is probably safe to add."
1674213,2019-01-23 18:33:24 UTC,Can i get +2 from someone please?  Thanks :)
1674223,2017-05-12 18:42:00 UTC,Perhaps this is a duplicate of #1662374.
1674250,2017-03-20 10:33:58 UTC,"This is like entering a bug saying something in trove doesn't work so I will fix it. It is hard to tell what is wrong, and to make a reasonable assessment as to whether it is wrong or not."
1674250,2017-03-20 11:03:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447451"
1674250,2017-11-06 19:42:13 UTC,"Change abandoned by Samuel Matzek (<email address hidden>) on branch: master
Review: https://review.openstack.org/447451
Reason: Abandoning because there has been an unanswered -1 review for 5 months and no update from the author in 6 months.  If you want to continue this review please restore it and address the comments."
1674251,2017-03-20 08:29:42 UTC,"I should add, I also do not have the nvidia drivers installed:"
1674252,2018-02-28 00:08:20 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu1
1674256,2017-03-21 07:16:54 UTC,"Created attachment 130337
Xorg.0.log from 1.18.4 on kvm/cirrus with corrupted image"
1674256,2017-03-21 07:30:48 UTC,"It seems like a regression between xserver-xorg-core 1.18.3 and 1.18.4.
I've reported it upstream in https://bugs.freedesktop.org/show_bug.cgi?id=100295, let's see how it goes..."
1674256,2017-03-21 08:54:35 UTC,"Another test that just verifies again that the regression is in modesetting, between 1.18.3 and 1.18.4."
1674256,2017-03-21 09:35:36 UTC,"I believe the problem was caused by:
https://cgit.freedesktop.org/xorg/xserver/commit/?id=21217d02168d1883b2d1f64399aec494f96a8b9d
modesetting: Implement 32->24 bpp conversion in shadow update"
1674256,2017-03-21 09:46:43 UTC,"That commit also caused the crashes that I experienced on broadwell + modeset + 16bpp:
https://bugs.freedesktop.org/show_bug.cgi?id=100246"
1674256,2017-03-23 09:23:20 UTC,"I tried this recent patch proposal:
https://lists.x.org/archives/xorg-devel/2017-March/053133.html"
1674256,2018-12-13 18:13:24 UTC,-- GitLab Migration Automatic Message --
1674263,2017-03-21 08:21:46 UTC,"Yes, float gu. The reason for that is restoring windows on a display with different density. If we recall a window from GU=8 on a GU=16 screen, it will not be what you wanted."
1674263,2017-03-21 01:53:29 UTC,"I'm not sure about this one. Legacy apps (actually all apps) that size themselves by pixels might get their sizes rounded to something inappropriate if you used 'int gu'. Or do you mean 'float gu'? The latter would avoid the problem (despite lack of precision), but even better would be to not fix this bug at all."
1674266,2017-03-20 09:31:08 UTC,"$ ~/build/percona-toolkit/bin/pt-table-checksum --version
pt-table-checksum 2.2.20"
1674266,2017-03-21 11:11:35 UTC,Also affects pt-3.0.1
1674266,2018-01-24 22:42:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-729
1674273,2017-03-20 19:58:18 UTC,apport information
1674273,2017-03-29 16:01:01 UTC,"For some strange reason, nslookup seems to respect ndots whereas ping does not."
1674273,2017-03-22 13:44:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674273,2017-03-22 13:42:27 UTC,Yaketty has either broken ndots or enforced it to 1.
1674273,2017-03-22 13:21:55 UTC,"It seems like the behaviour has changed in yaketty.
- queries with fewer than ndots are only tried with search list appended, never tried as fqdn
- queries with ndots ore more are tried as fqdn directly and search list is never tried"
1674273,2017-03-22 12:44:06 UTC,Yeah the man is quite unclear on how local domain / search list is managed when resolving.
1674273,2017-03-21 01:27:41 UTC,Interesting. At the very least then the man page is inconsistent since
1674273,2017-03-21 00:52:31 UTC,"I think you are not hitting any bug at all ?
According to the man, ndots has nothing to do with adding or not adding search list to the query, it only determines if you need to try absolute request first OR with search list first. The first non-error result is returned to the client."
1674273,2017-03-20 19:58:21 UTC,apport information
1674273,2017-03-20 19:58:13 UTC,apport information
1674273,2017-03-20 19:58:11 UTC,apport information
1674273,2017-03-20 19:58:08 UTC,apport information
1674273,2017-03-20 19:58:06 UTC,apport information
1674273,2017-03-20 19:58:04 UTC,apport information
1674273,2017-03-20 19:58:01 UTC,apport information
1674273,2017-03-20 19:57:59 UTC,apport information
1674273,2017-03-20 19:57:56 UTC,apport information
1674273,2017-03-20 19:57:54 UTC,apport information
1674273,2017-03-20 19:52:18 UTC,I don't think this is a recent regression. I have seen the symptoms for a while and have only gotten around to investigating it yesterday. Also see the linked bug which describes exactly this issue and which was raised in 2009.
1674273,2017-03-20 13:26:55 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1674273,2017-03-20 10:30:22 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1674273,2017-03-20 19:58:10 UTC,apport information
1674279,2017-03-20 10:56:08 UTC,"StacktraceTop:
 wxSocket_Input () from /tmp/apport_sandbox_YYCEem/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
 g_main_context_dispatch () from /tmp/apport_sandbox_YYCEem/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /tmp/apport_sandbox_YYCEem/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /tmp/apport_sandbox_YYCEem/lib/x86_64-linux-gnu/libglib-2.0.so.0
 IA__gtk_main () at ./gtk/gtkmain.c:1282"
1674287,2017-03-20 11:23:18 UTC,Partly fixed by commit: https://review.openstack.org/#/c/446972/
1674287,2017-03-22 14:08:54 UTC,"Reviewed:  https://review.openstack.org/446972
Committed: https://git.openstack.org/cgit/openstack/craton/commit/?id=5f0e8d762214618b05b54a3f1594c697bf304d86
Submitter: Jenkins
Branch:    master"
1674289,2017-03-28 22:17:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674292,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1674294,2017-03-22 13:06:52 UTC,"Fix committed into lp:ubuntu-terminal-app at revision 359, scheduled for release in ubuntu-terminal-app, milestone Unknown"
1674296,2017-03-21 15:23:52 UTC,Neither QWindow::raise nor QWindow::requestActivate seem to raise the settings window.
1674296,2017-03-21 15:26:42 UTC,"Could you log separate bug about QWindow::raise/QWindow::requestActivate against qtubuntu. Mir has an api for that, but we've not implemented it."
1674296,2017-03-21 15:40:32 UTC,"Ok, no need for separate bug, the updated description shows me what you want."
1674296,2017-03-21 15:41:25 UTC,Test app is a QML app that reproduces the behaviour. Click on the content of the root window and observe that the child window is not raised.
1674296,2017-03-21 15:51:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674302,2017-03-20 12:07:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447462"
1674302,2017-03-21 14:57:29 UTC,"Change abandoned by Michal Ptacek (<email address hidden>) on branch: master
Review: https://review.openstack.org/447462"
1674313,2017-04-02 02:16:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674313,2017-03-20 12:43:38 UTC,"StacktraceTop:
 IA__gdk_display_open (display_name=<optimized out>) at ./gdk/x11/gdkdisplay-x11.c:173
 IA__gdk_display_open_default_libgtk_only () at ./gdk/gdk.c:324
 IA__gtk_init_check (argv=<optimized out>, argc=<optimized out>) at ./gtk/gtkmain.c:1020
 IA__gtk_init (argc=<optimized out>, argv=<optimized out>) at ./gtk/gtkmain.c:1067
 QGtkStylePrivate::initGtkWidgets (this=0x558c3be587a0) at qgtkstyle_p.cpp:276"
1674314,2017-04-02 09:14:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452527"
1674314,2019-08-25 19:58:31 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.opendev.org/452527
Reason: Hi, magnum team is trying to clean up these old pending patches. Please feel free to reopen this if you're still working on. Thanks."
1674320,2019-07-09 00:39:54 UTC,This has been fixed by other work since the report was filed. The test set up no longer fails locally under stress.
1674342,2017-03-22 13:06:56 UTC,"Fix committed into lp:ubuntu-terminal-app at revision 359, scheduled for release in ubuntu-terminal-app, milestone Unknown"
1674343,2017-03-22 13:07:01 UTC,"Fix committed into lp:ubuntu-terminal-app at revision 359, scheduled for release in ubuntu-terminal-app, milestone Unknown"
1674347,2017-03-21 15:47:44 UTC,"Need to address duplicate user creation in a given project, so returns 409 instead of 500. However same user name in different projects is allowed (but not yet tested)."
1674349,2017-04-04 19:33:32 UTC,"Reviewed:  https://review.openstack.org/448538
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=75c34838ef7132352a34b0c224c2536a5283b1d5
Submitter: Jenkins
Branch:    master"
1674349,2017-04-06 22:24:44 UTC,There is agreement it's a nice isolated enhancement. We don't need a blueprint or a spec for that.
1674349,2017-03-27 11:59:53 UTC,"Yes, we can add a policy rule like:"
1674349,2017-03-30 18:30:50 UTC,"Set the status to Triaged as it is not approved as RFE.
IMO this can be handled as a normal bug."
1674349,2017-03-22 13:07:44 UTC,"To support this we need:
- Retrieve more attributes when constructing context object (use oslo_context.context.Context.from_environ())
- Update the default policy file to lookup service_roles."
1674349,2017-03-22 12:13:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448538"
1674349,2017-03-21 15:28:17 UTC,"It is mainly up to what parameters are passed to neutron context.
oslo.context supports parameters more than neutron(.auth) supports.
This RFE is completely worth supported."
1674349,2017-03-22 17:35:56 UTC,- Update the default policy file to lookup service_roles.
1674353,2017-03-21 15:25:12 UTC,"Error appear due wrong
mos_version = mos10.0"
1674355,2017-03-20 14:21:56 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/447517"
1674355,2017-03-24 09:07:07 UTC,"Change abandoned by JeffreyGuan (double12gzh@163.com) on branch: stable/mitaka
Review: https://review.openstack.org/447517"
1674360,2017-03-20 14:34:26 UTC,"  After wake up, the connection is stablished, but not work.
The network adapter is:
Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC"
1674363,2017-03-21 14:58:31 UTC,"I've thought about this more, especially after Raoul said ""...we'd basically have to intercept all mouse events, and then selectively ignore or engage them..."" (see the linked Q&A above).  That's a lot of work to code & test, and that introduces more work that OpenLP does constantly, and it's only to resolve a really minor corner case on one platform (may or may not happen on others) - and let's not forget that some folks are still running on WinXP with much older machines."
1674363,2017-05-29 14:40:57 UTC,"I've marked it as low, as somebody have a look at this."
1674364,2020-08-03 21:58:41 UTC,"Tested and pushed to master, rel_3_5, and rel_3_4. Thanks, Josh and Terran!"
1674364,2020-02-20 20:38:29 UTC,"I was unable to create a record in Concerto that has different 001 and 901c values, but I WAS able to confirm that this change does indeed put the ID into the image url instead of having a blank ID in the url, so I'm happy to sign off on it!"
1674364,2020-01-15 20:34:32 UTC,"Terran, I think that I should be seeing the BIBID value in the atom output, but I'm not seeing that."
1674364,2020-01-16 15:34:06 UTC,I'm not sure - I'll try to get this tested again on my own test server after we get through our upcoming upgrade.
1674364,2019-03-04 17:30:06 UTC,"I think we should not use the TCN, 001 for pulling the data.  Some sites do use TCN values that are not the same as the database bib id number.  I think we need to use the 901c value to pull the cover art."
1674364,2018-02-05 15:02:35 UTC,"Yes, the ISBN method of lookup just isn't reliable. The code should be changed to use TCN like the catalog pages do."
1674364,2018-02-02 18:53:31 UTC,"I got the RSS link one of my catalog lists viewed it on an RSS reader (feedly) and noticed that it only had one image (out of 4 total records).
The Fifth Season did not have an image despite having only one 13-digit ISBN 9780316229296
Mr. Penumbra's 24 hour bookstore did have an image--and also had one 13-digit ISBN"
1674364,2020-01-15 18:38:20 UTC,"This patch is loaded on a 3.4.2 sandbox with concerto data but I'm not seeing the ID number from the 901c field coming through. In the attached screenshot, the value that is in the associated MARC record is 245."
1674369,2017-04-05 03:39:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674375,2017-08-09 21:20:44 UTC,It looks like this was fixed in TripleO.  Feel free to reopen if I'm mistaken.
1674375,2017-07-05 19:01:54 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1674375,2017-03-25 20:54:28 UTC,"Reviewed:  https://review.openstack.org/447531
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=b8789f1db3942437aef13e35d00b42ff85c7eaee
Submitter: Jenkins
Branch:    master"
1674375,2017-03-24 18:41:14 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/447531"
1674375,2017-03-22 02:47:11 UTC,"Reviewed:  https://review.openstack.org/447533
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=1063de82f6ba7dfaadc25abd4c0feebcd8b4a0ff
Submitter: Jenkins
Branch:    master"
1674375,2017-03-20 15:53:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447561"
1674375,2017-03-21 09:25:25 UTC,"Reviewed:  https://review.openstack.org/447561
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=c25dbe92487225e1209734ecaba2ff93aec42320
Submitter: Jenkins
Branch:    master"
1674375,2017-03-20 15:04:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/447535"
1674375,2017-03-20 14:59:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/447533"
1674375,2017-03-20 14:52:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/447531"
1674375,2017-03-21 12:20:39 UTC,"Reviewed:  https://review.openstack.org/447535
Committed: https://git.openstack.org/cgit/openstack/packstack/commit/?id=88200b5f7592336fbb3d9d6213a7175a92643f0d
Submitter: Jenkins
Branch:    master"
1674375,2017-08-10 12:43:39 UTC,This was fixed for Packstack in https://github.com/openstack/packstack/commit/88200b5f7592336fbb3d9d6213a7175a92643f0d
1674378,2018-01-04 12:44:22 UTC,"Adding Sergio for his opinion, he is running the tests on the dragonboard and pi2/3 regularly."
1674378,2017-05-11 14:44:59 UTC,This also seems to be a problem on rpi (unsurprisingly)
1674381,2017-03-22 13:57:09 UTC,From neutron logs:
1674381,2017-03-29 07:31:44 UTC,"Node-1 started to report dead agents starting from 2017-03-20 01:29:40, while other nodes didn't: ""found 14 active agents"" on both nodes 2 and 4."
1674381,2017-03-29 07:52:22 UTC,node-1 has this time jump (same ~40 sec) a bit earlier at 01:28:41.161:
1674381,2017-03-29 08:02:17 UTC,Looking at fuel master node logs can also see this time jump clearly; node-1 nova-api log:
1674381,2017-03-29 08:06:27 UTC,Given above seems it's time desynchronisation issue on nodes.
1674382,2019-05-14 14:44:49 UTC,This issue was fixed in the openstack/tripleo-quickstart-extras 2.1.1 release.
1674382,2019-01-22 13:42:33 UTC,Is this still an issue?
1674382,2018-03-30 20:30:53 UTC,"Reviewed:  https://review.openstack.org/557455
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=b5e349bc478a5b3bf4bd896224a888843a2fc21b
Submitter: Zuul
Branch:    master"
1674382,2018-03-31 03:33:35 UTC,"The commit landed doesn't include dstat being launched during libvirt provisioning, but it does cover the other cases (UC install, OC nodes)"
1674384,2017-07-05 17:56:45 UTC,This also appears to be affecting 16.04.2 as well.
1674384,2017-07-05 17:57:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674384,2017-07-05 18:50:20 UTC,Please ignore my previous comment. I had a CPAN version of mhonarc installed as well as the Ubuntu package. The Ubuntu packaged version of mhonarc works fine in xenial.
1674386,2017-03-20 18:39:44 UTC,"Hello Antti,"
1674386,2017-03-30 04:44:05 UTC,I'm using XFCE.
1674387,2017-05-29 14:32:57 UTC,Something like a verse order override?
1674387,2017-06-18 21:27:57 UTC,"Yes, I think so.  Ultimately, I just want a way to quickly access all of a song's slides when we're live."
1674389,2017-03-22 02:41:41 UTC,Might be a two-parter bug.
1674389,2017-03-22 13:42:33 UTC,adding repowerd because it suspiciously sounds a lot like bug 1668596
1674389,2017-03-29 09:24:52 UTC,"repowerd, or some other process that acquires logind suspend inhibitions, could be involved in this. It's easy to find out if this is the case by running:"
1674389,2017-04-06 11:46:30 UTC,This bug was fixed in the package indicator-session - 17.3.20+17.04.20170403-0ubuntu1
1674397,2020-05-09 11:52:01 UTC,Assuming fixed there was no response. Please retest with the newest Inkscape version and report new issues in the new bug tracker: https://inkscape.org/report
1674397,2017-06-18 23:54:43 UTC,"I would think not, since the report covers 0.91, which was before the Objects dialog was added."
1674397,2017-04-19 15:15:37 UTC,I'll add my anecdote that I have seen the same pattern as the OP. 0.91 or 0.92 is just obviously sluggish in many cases compared to how 0.48 was.
1674397,2017-03-26 17:42:41 UTC,"I'm not a programmer, so I can't provide any constructive troubleshooting info.  But I just wanted to add a couple more comments or thoughts."
1674397,2017-06-16 05:39:23 UTC,"Could this be related to https://bugs.launchpad.net/inkscape/+bug/1431274 ?
Note that simply closing the Objects dialog does not help. You have to restart Inkscape."
1674398,2019-07-09 00:45:33 UTC,"This file, suite and, hence, test are no longer in codebase."
1674401,2017-03-20 16:03:32 UTC,"I did some more googling and finally guessed the right phrase.
Some reports of similar (the same?) problem (all unresolved):"
1674401,2017-03-24 11:41:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674401,2018-11-07 08:40:06 UTC,Any plans on fixing this? Anything I can provide you for analysis?
1674401,2018-11-07 08:40:40 UTC,I use KDE Plasma on Ubuntu Bionic and the problem still exists
1674401,2018-11-07 08:42:31 UTC,"For me, the problem does not occur when using the default task-switcher. It occurs only when I try to install additional task switcher styles in the system settings dialog"
1674402,2017-03-22 07:56:59 UTC,"Ok, so what seems to be at the root of this is that ""grub-install"" for ieee-1275 is trying to find a companion prep partition (type 0x41) to the root partition which it will copy the openfirmware binaries into"
1674402,2017-06-09 14:24:38 UTC,The fix https://review.openstack.org/#/c/471525/
1674402,2017-06-07 06:46:23 UTC,"Change abandoned by Ian Wienand (<email address hidden>) on branch: master
Review: https://review.openstack.org/447739
Reason: See I0918e8df8797d6dbabf7af618989ab7f79ee9580"
1674402,2017-03-21 18:12:57 UTC,">I've applied [1] which seems pretty good, but unfortunately, it seems like qemu doesn't like working with ppc64le binaries and fails with an invalid exception [2]
>
> This might be worth a bug, Mikhail?
"
1674402,2017-03-20 23:38:47 UTC,Adding builder log for a successful build with dib 1.28.0
1674402,2017-03-21 00:21:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447739"
1674402,2017-03-20 23:41:49 UTC,I think I see the broad strokes of what's gone wrong here.  In vm/block-device.d/10-partition we had a branch for ppc which sets up two partitions; this PReP boot partition and the main one.  I don't see that we've migrated this correctly to the new bootloader.
1674402,2017-03-21 05:00:04 UTC,I haven't had much luck with a local replication of this.
1674415,2017-05-08 21:39:00 UTC,This issue was fixed in the openstack/keystone 11.0.1 release.
1674415,2017-03-28 18:09:14 UTC,"Reviewed:  https://review.openstack.org/450027
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c541e1ec5c2a3937e9d90cc106a4727c6c2b47db
Submitter: Jenkins
Branch:    stable/ocata"
1674415,2017-04-12 18:49:37 UTC,This issue was fixed in the openstack/keystone 12.0.0.0b1 development milestone.
1674415,2017-03-24 22:52:19 UTC,"Reviewed:  https://review.openstack.org/449769
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=2126bd576550a68284e05fc8eadedce072531563
Submitter: Jenkins
Branch:    master"
1674415,2017-03-24 18:11:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449769"
1674415,2017-03-26 17:53:58 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/450027"
1674417,2017-06-14 07:57:27 UTC,"I've run into this as well, using both the list of form values givrn by Robie in the Bug Description, and one w/ Visibility switched to Private."
1674420,2017-06-26 17:07:16 UTC,We have made improvements to the upload service and believe this is resolved now.
1674420,2017-06-06 21:00:53 UTC,Kyle is getting this quite a bit for the Nextcloud snap pushing from Launchpad:
1674420,2017-04-19 02:09:55 UTC,I've been getting this for the last 8 hours.  1PM to 9PM CT.
1674420,2017-04-26 15:05:30 UTC,i saw this as well occasionally since easter for the daily builds of the core and ubuntu-core snaps ... since today i see it for all upload attempts for all arches of both these snaps
1674423,2017-03-20 18:52:00 UTC,"Please rerun one of the commands with -v9 and capture the log in a file.  Below each comment in the bug display is a link to ""Add attachment or patch"".  Please use that to attach the file to the bug report.  Do not copy & paste into the comment box, it screws up the formatting."
1674423,2017-03-21 09:59:33 UTC,Many thanks for considering my case ; about your questions :
1674423,2017-03-21 15:22:33 UTC,"If you have the original CentOS6/duplicity setup, please try the list-current-files on that.  Same drill as above with the log file.  It may be something as simple as EOL char differences."
1674423,2017-03-21 15:54:22 UTC,Hi again
1674423,2017-03-22 13:24:44 UTC,"As a followup, I was able to restore a backup, both on CentOS6 and on my Mac ; the md5sum hashes are ok, nice ! Just still stuck on the 'list-current-files' error."
1674423,2017-03-26 11:51:25 UTC,Does the list-current files problem occur on CentOS6 as well?
1674423,2017-03-26 19:15:03 UTC,Yes it does as shown by my last attachment
1674439,2017-03-20 17:55:27 UTC,"StacktraceTop:
 XChangeProperty (dpy=0x55faeb7cf400, w=39845891, property=310, type=type@entry=6, format=format@entry=32, mode=mode@entry=0, data=0x55faebb5da90 ""\026"", nelements=4654) at ../../src/ChProp.c:83
 gdk_x11_window_set_icon_list (window=0x55faeb7f54c0, pixbufs=0x7f0080009f20) at ././gdk/x11/gdkwindow-x11.c:3931
 gtk_window_realize_icon (window=0x55faebaae2e0) at ././gtk/gtkwindow.c:4668
 g_closure_invoke () from /tmp/apport_sandbox_3BLDyG/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /tmp/apport_sandbox_3BLDyG/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1674441,2017-03-20 18:13:34 UTC,See https://launchpad.net/~angelsl/+archive/ubuntu/trusty-crypto-backports for test
1674442,2017-03-20 18:13:50 UTC,See https://launchpad.net/~angelsl/+archive/ubuntu/trusty-crypto-backports for attempt at building (failed)
1674442,2017-03-20 18:01:43 UTC,N.B. package doesn't build without modification due to a too-new debhelper being required.
1674460,2017-03-30 15:27:36 UTC,UPDATE: it's only with xfwm4 window manager. Other WMs work properly.
1674468,2019-10-01 22:24:23 UTC,I've assigned this to snapd but I think the real overhead is in the kernel apparmor stack.
1674468,2019-10-02 10:22:05 UTC,"this is very typical and has been seen before (i cant find the other older bugs though, but we had a few)"
1674475,2017-03-20 21:42:04 UTC,"That is a peculiar error, and is not part of Open Rails' own code - it is entirely inside the XNA graphics library we use. I don't think I've seen that error happen before."
1674475,2017-03-21 10:40:59 UTC,"That fixed my problem, thanks."
1674475,2020-06-06 06:25:18 UTC,I am facing this problem suggest to fix it
1674477,2017-03-22 03:58:48 UTC,That all said... why don't we just declare gnome-screenshot unsupported if it's really just a client of gnome-shell. Doesn't Unity8 have other adequate screenshotting mechanisms?
1674477,2017-03-23 14:57:56 UTC,"> On the other hand, persisting with an architecture where apps don't work unless processes other than the shell happen to be running is a bit nasty in my opinion. And similarly anything that depends on a bus is ugly IMHO. I've lost count of the number of times in recent months where GTK apps refused to start because they were timing out waiting for some process or bus to become available that didn't exist in Mir.
"
1674477,2017-03-22 03:55:42 UTC,"""Is there some mir client api for scraping the screen?"""
1674477,2017-03-22 03:48:23 UTC,On one hand asking the shell to own screenshotting is nice and secure.
1674477,2017-03-22 03:33:46 UTC,"I don't know if that would be the easiest approach. It sounds to me like having U8 implement that dbus interface would be the easiest and least invasive solution, but then again, I'm not the one volunteering for that :)"
1674477,2017-03-21 02:50:23 UTC,"If we really want to support gnome-screenshot at all, it might be easier to implement a Mir backend right inside it (perhaps after fixing bug 1660269)."
1674481,2020-11-09 18:02:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674481,2019-07-03 10:56:42 UTC,This issue may be resolved in later ceph releases present in Ubuntu.
1674481,2019-07-03 10:55:38 UTC,The original bug report lacks a ceph/openstack/qemu version - was this prior to the releases details in #10?
1674481,2019-07-03 10:54:52 UTC,Upstream bug: http://tracker.ceph.com/issues/36192
1674481,2018-10-01 19:23:01 UTC,"Looks like #1701449 is a duplicate of this one, or the other way around."
1674481,2017-11-29 04:17:17 UTC,[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]
1674481,2017-11-29 04:17:21 UTC,[Expired for ceph (Ubuntu) because there has been no activity for 60 days.]
1674481,2017-09-29 08:51:09 UTC,"Marking charm bug as invalid as this is an issue with librbd or qemu, not the charm itself."
1674481,2017-09-29 08:49:33 UTC,Raising bug tasks for distro packages alongside the charm bug.
1674481,2017-09-29 08:48:13 UTC,Qemu bug report - bug 1701449
1674481,2017-09-29 08:46:08 UTC,Just to confirm what I think I see in the qemu params - is this instances booted from ceph using the nova-compute support for ephemeral storage on ceph?
1674481,2017-06-21 23:58:25 UTC,"I am not using openstack, but have the same problem with QEMU/KVM virtual machines that have Ceph RBD disks attached.  There is an issue on the Ceph tracker (http://tracker.ceph.com/issues/20054#change-93573) but it isn't clear if the bug is on their side or if it is in QEMU."
1674481,2017-09-29 08:52:28 UTC,Marking this as  'Medium' for now - we may want to bump that to 'High';  right now we have a reproducer in the context of qemu/librbd but not directory with librbd which indicates this is a qemu specific issue.
1674492,2017-03-20 22:53:34 UTC,This bug is related to two other bugs:
1674492,2018-10-02 10:34:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674497,2017-03-20 23:10:27 UTC,"$ uname -a
Linux uhop 4.8.0-42-generic #45-Ubuntu SMP Wed Mar 8 20:06:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1674506,2017-03-29 16:19:52 UTC,I put a initial version forward: https://github.com/snapcore/snapd/pull/3111
1674509,2017-04-04 14:11:10 UTC,"@ogra, yes I will include"
1674509,2017-04-04 12:29:16 UTC,"@Nikolay: this bug is about generally making BT work on the pi images by default, your problem is very specific, would you file a new bug for it instead (so we can close this one once the driver works at all)"
1674509,2017-04-04 14:27:45 UTC,"@ogra, changes pushed to snappy-hwe-snaps/+git/bluez"
1674509,2017-04-04 10:23:16 UTC,"And I experiences quite similar issue, that I fill here - https://bugs.launchpad.net/snappy/+bug/1679432"
1674509,2017-04-04 09:06:44 UTC,@ogra
1674509,2017-04-04 10:01:34 UTC,"I did the same patch - modify firmware patch and speed initialization patch... and I got bluetooth working on RPi!
I used my own app to test it - https://github.com/Nikolay-Kha/BluetoothAudio
hcitool scan
also works fine. bluetoothctl starts, but I cannot type anything there, don't know why."
1674509,2017-04-04 09:46:49 UTC,"note: this is without any overlay dtb loaded, using the standard Ubuntu Core config.txt"
1674509,2017-04-04 15:55:19 UTC,"@ogra, yes, sure, I created report here - https://bugs.launchpad.net/snappy/+bug/1679747"
1674509,2017-04-04 09:39:23 UTC,WHEEE !
1674509,2017-04-04 10:02:17 UTC,"oops, I forget the attachment that I promised. It's here.?field.comment=oops, I forget the attachment that I promised. It's here."
1674509,2017-04-05 10:18:40 UTC,@konrad: 5.44-1-dev from the edge channel works fine now as long as i use --devmode ... not using devmode gets me a denial:
1674509,2017-05-09 09:28:12 UTC,"well, the btattach tool would still have to be shipped and executed by bluez."
1674509,2017-04-07 05:52:53 UTC,@jdstrand @ogra
1674509,2017-04-07 10:00:29 UTC,"@korad, well, i would assume that 90% of the IoT boards we will support will have such a UART based setup, so i would lean towards having generic serial tty support in the BT rules without having to define it for each single board in the gadget... i.e. simply by adding rw support for /dev/tty[A-Z]*[0-9] to the apparmor rules ..."
1674509,2017-04-07 10:10:16 UTC,"also ... keep in mind that we will additionally need to ship a systemd unit caring for the hciattach call that will be equally specific and will likely live where the hciattach tool lives (in the bluez package), we can not ship this in the gadget without having the tool available. i think we need to generalize on both levels here (systemd/apparmor) to make the bluez package work OOTB on such HW."
1674509,2017-04-07 14:15:02 UTC,"Jamie's suggestion seems spot on for the time being. This is really something for the gadget to expose, and it should be made in an explicit way. It can be a regular expression as suggested because then you cannot assign a particular snap plug to a particular serial port anymore."
1674509,2017-04-07 14:15:25 UTC,"Sorry, it CANNOT be a regular expression. I wish Launchpad allowed edits."
1674509,2017-04-19 11:08:16 UTC,"@ogra going back to this after a while, what is the status - is it being included in the gadget snap?"
1674509,2017-05-06 15:16:27 UTC,"with todays edge image the interface is available on the pi3 ... we now need a device specific hciattach systemd unit in the bluez snap (since that ships the hciattach binary, we cant ship this in the image)"
1674509,2017-05-08 16:32:59 UTC,"here is a proof of concept script+systemd unit ... http://paste.ubuntu.com/24537569/
using this setup i have properly working BT after boot *if* the bluez snap is in --devmode"
1674509,2017-05-09 05:03:36 UTC,@ogra
1674509,2017-05-09 05:19:25 UTC,Btw. you guys should see if the more modern btattach utility does the job instead of hciattach too. See http://manpages.ubuntu.com/manpages/xenial/man1/btattach.1.html for a few details. Sooner or later btattach will replace hciattach as the way to attach serial lines to the kernel bluetooth stack.
1674509,2017-04-04 08:12:06 UTC,Can you try with hcitool?
1674509,2017-04-06 13:41:52 UTC,"For the slot Permanent policy I think it is fine to allow the bluez interface access to /dev/ttyAMA0. ofono, ppp, et al are in similar situations."
1674509,2017-04-03 15:46:49 UTC,the respective lines from dmesg:
1674509,2017-05-09 08:30:49 UTC,I like @morphis idea
1674509,2017-04-03 12:54:52 UTC,seems the /etc/firmware dir is actually hardcoded in
1674509,2017-03-21 10:03:03 UTC,can you try:
1674509,2017-03-22 06:38:59 UTC,"@ogra,"
1674509,2017-03-23 15:53:16 UTC,"this is weird, i clearly see:"
1674509,2017-03-23 16:07:59 UTC,@ogra: have to tried connecting a BT device to the BT controller?
1674509,2017-03-25 14:20:51 UTC,"looking around i stumbled over the patch below, that avoids to set the speed before loading the firmware in hciattach. we dont seem to carry this patch in:"
1674509,2017-03-25 14:22:32 UTC,"@jim, i see the same issues chungsang sees, even with the bluez package from edge that actually had teh bluetooth-control imterface (which we need connected on the pi to access /dev/vhci)"
1674509,2017-03-27 15:05:04 UTC,"@ogra, anything we could do to help you debug this issue?"
1674509,2017-03-27 15:14:38 UTC,"@konrad, well, that patch looks like it could be relevant, could we include it for a test ?"
1674509,2017-03-28 07:04:21 UTC,"@ogra, The hciattach is not used on RPi at all therefore this patch will not affect anything. Could it be that we are missing a proper driver or DT entry?"
1674509,2017-03-28 09:19:19 UTC,"@konrad, so i talked to paolo on IRC, seems we have a slight prob here with BT and serial sharing the UART (and we default to have a serial console enabled for IoT use cases). so this needs a bit more research on the gadget and kernel side."
1674509,2017-03-28 13:24:30 UTC,"@ogra,"
1674509,2017-03-28 13:39:32 UTC,we do set core_freq=250 and enable_uart=1 in our config.txt today and afaik the serial console doesnt work if i drop enable_uart=1....
1674509,2017-04-03 15:45:03 UTC,using a patched hciattch (with the speed setting patch from above as well as a fixed FIRMWARE_DIR pointing to /lib/firmware):
1674509,2017-03-28 16:14:16 UTC,"so digging deeper there are dtoverlay=pi3-miniuart-bt and dtoverlay=pi3-disable-bt overlays but no matter which combo of enable_uart, core_freq and either overlay i use, as soon as i enable them no boot is possible at all anymore. (note that we use other overlays successfully in teh default setup). i fear i have to defer to paolo, perhaps we are missing a kernel config option here ..."
1674509,2017-03-28 13:44:03 UTC,just verified ... keeping core_freq=250 and dropping enable_uart=1 completely kills all output on serial
1674509,2017-04-03 10:34:38 UTC,now i see bluetooth in lsmod right after boot when not changing anything in config.txt ...
1674509,2017-04-03 08:20:32 UTC,"@ogra: done, and i kicked a new build of the rpi2 kernel snap."
1674509,2017-03-31 15:48:54 UTC,@paolo:
1674509,2017-03-31 15:27:39 UTC,Makes sense to include the bluetooth firmware files in the kernel snap.
1674509,2017-04-03 12:51:26 UTC,"ok, i got a little further, seems the bluez snap doesnt really have access to ttyAMA0 so i had to re-install it in --devmode ... now i get (still without the dtoverlay though, since this does not boot at all):"
1674509,2017-03-31 15:10:21 UTC,@paolo: this is all ancient bluez 4 stuff i fear ...
1674509,2017-03-31 15:10:11 UTC,Here is the bluez package i tested:
1674509,2017-03-31 15:08:35 UTC,"The kernel is fine, i've tested it on a xenial image:"
1674509,2017-03-29 10:33:31 UTC,@ogra thanks for following up
1674509,2017-03-31 15:15:19 UTC,"could we just ship the fw files in the pi2-kernel snap ?
i'll happily push the deb to the image PPA where the kernel snap Makefile could pull it from ...
iirc there is already some special casing for pi2 in the Makefile code that installs the raspberrypi-wireless-firmware deb from the PPA."
1674510,2017-03-21 00:37:45 UTC,attachment-1.txt
1674522,2017-03-21 02:15:59 UTC,"Hello,"
1674522,2018-02-09 13:59:13 UTC,"FYI, we no longer use launchpad, all bugs have been migrated to Storyboard.
This one in particular was previously resolved and closed."
1674524,2018-03-02 16:22:25 UTC,"Based on the discussion in the Dublin PTG, host API will support PATCH update."
1674524,2017-09-01 08:16:14 UTC,"Partial bug fix, supporting update extra capacity, was released in Pike.  The concrete bug fix or discussions about supporting update/delete or not is targeted to Queens release."
1674524,2017-11-15 08:44:59 UTC,"Updating or deleting of extra capabilities can break a lease. For example, the following scenario can happen:"
1674524,2017-08-21 04:43:29 UTC,"Reviewed:  https://review.openstack.org/491583
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=03e005993262357eb955601fb8acef38654eadf8
Submitter: Jenkins
Branch:    master"
1674525,2018-12-25 19:18:03 UTC,"This now compiles just fine, I guess we can close this one!"
1674525,2018-04-20 14:47:28 UTC,This appears to be fixed in our 7-2017Q4 release. Can you confirm Andrey?
1674525,2018-04-20 14:48:11 UTC,Note you'll need 2 more -Wno-* for the compilation to work with GCC 7.
1674525,2017-03-21 21:11:37 UTC,"I know it's not the best way to reproduce an issue but can you download my whole project? It embedds Chibios 2.6, I believe ChibiOS prior to 3.0 is affected. While yes this is an order version of ChibiOS I would assume gcc should not fail with internal error regardless?"
1674525,2017-03-21 13:21:27 UTC,"Hi there,"
1674525,2017-03-21 03:18:23 UTC,"Apprantly chibios people are aware of this as ""there is a bug with gcc-arm-none-eabi-4_8-2014q1 which prevent to use -flto and -gddb together."""
1674525,2017-03-22 10:16:54 UTC,"Hi Andrey,"
1674525,2017-03-21 02:41:48 UTC,"cs-make all
Building target: rusefi.elf
Invoking: Cross ARM C++ Linker
arm-none-eabi-g++ -mcpu=cortex-m4 -mthumb -mfloat-abi=softfp -mfpu=fpv4-sp-d16 -O0 -fmessage-length=0 -ffunction-sections -fdata-sections  -g -T ""..\config\stm32f4ems\STM32F407xG_CCM.ld"" -Xlinker --gc-sections -Wl,-Map,""rusefi.map"" -Wl,-Map,""rusefi.map"" -o ""rusefi.elf""  ./util/LocalVersionHolder.o ./util/cli_registry.o ./util/crc.o ./util/cyclic_buffer.o ./util/data_buffer.o ./util/datalogging.o ./util/efilib.o ./util/efilib2.o ./util/histogram.o ./util/listener_array.o ./util/loggingcentral.o ./util/rfiutil.o  ./hw_layer/stm32f4/mpu_util.o ./hw_layer/stm32f4/stm32f4xx_hal_flash.o ./hw_layer/stm32f4/stm32f4xx_hal_flash_ex.o  ./hw_layer/serial_over_usb/usbcfg.o ./hw_layer/serial_over_usb/usbconsole.o  ./hw_layer/sensors/CJ125.o  ./hw_layer/mass_storage/usb_msd.o ./hw_layer/mass_storage/usb_msd_cfg.o  ./hw_layer/lcd/lcd_HD44780.o  ./hw_layer/HIP9011.o ./hw_layer/accelerometer.o ./hw_layer/adc_inputs.o ./hw_layer/board_test.o ./hw_layer/can_hw.o ./hw_layer/digital_input_hw.o ./hw_layer/flash.o ./hw_layer/gpio_helper.o ./hw_layer/hardware.o ./hw_layer/io_pins.o ./hw_layer/joystick.o ./hw_layer/max31855.o ./hw_layer/mcp3208.o ./hw_layer/microsecond_timer.o ./hw_layer/mmc_card.o ./hw_layer/neo6m.o ./hw_layer/pin_repository.o ./hw_layer/pwm_generator.o ./hw_layer/rtc_helper.o ./hw_layer/servo.o ./hw_layer/stepper.o ./hw_layer/trigger_input.o ./hw_layer/vehicle_speed.o  ./development/test/test.o ./development/test/testbmk.o  ./development/hw_layer/poten.o  ./development/engine_emulator.o ./development/engine_sniffer.o ./development/rfi_perftest.o ./development/sensor_chart.o ./development/trigger_emulator.o ./development/wave_analyzer.o  ./controllers/trigger/decoders/trigger_bmw.o ./controllers/trigger/decoders/trigger_chrysler.o ./controllers/trigger/decoders/trigger_gm.o ./controllers/trigger/decoders/trigger_honda.o ./controllers/trigger/decoders/trigger_mazda.o ./controllers/trigger/decoders/trigger_mitsubishi.o ./controllers/trigger/decoders/trigger_nissan.o ./controllers/trigger/decoders/trigger_rover.o ./controllers/trigger/decoders/trigger_subaru.o ./controllers/trigger/decoders/trigger_toyota.o ./controllers/trigger/decoders/trigger_universal.o  ./controllers/trigger/main_trigger_callback.o ./controllers/trigger/rpm_calculator.o ./controllers/trigger/spark_logic.o ./controllers/trigger/trigger_central.o ./controllers/trigger/trigger_decoder.o ./controllers/trigger/trigger_emulator_algo.o ./controllers/trigger/trigger_simulator.o ./controllers/trigger/trigger_structure.o  ./controllers/system/SingleTimerExecutor.o ./controllers/system/efiGpio.o ./controllers/system/event_queue.o ./controllers/system/pwm_generator_logic.o ./controllers/system/signal_executor_sleep.o  ./controllers/sensors/allsensors.o ./controllers/sensors/ego.o ./controllers/sensors/hip9011_lookup.o ./controllers/sensors/maf.o ./controllers/sensors/map.o ./controllers/sensors/thermistors.o ./controllers/sensors/tps.o ./controllers/sensors/voltage.o  ./controllers/math/biquad.o ./controllers/math/engine_math.o ./controllers/math/pid.o ./controllers/math/speed_density.o  ./controllers/core/EfiWave.o ./cont..."
1674543,2018-06-22 00:55:25 UTC,"Reviewed:  https://review.openstack.org/504341
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=f192f51d371e489f74f2bd71c811a4ce8d53afa1
Submitter: Zuul
Branch:    master"
1674543,2019-03-20 01:05:17 UTC,"Reviewed:  https://review.openstack.org/611686
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=baf18edc00851f6749a40794587ca14a52135bf3
Submitter: Zuul
Branch:    master"
1674543,2019-03-27 21:11:17 UTC,"Fix proposed to branch: feature/losf
Review: https://review.openstack.org/648245"
1674543,2019-03-28 21:12:58 UTC,"Reviewed:  https://review.openstack.org/648245
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=6afc1130fd753306d64745c9bee7712182b273d3
Submitter: Zuul
Branch:    feature/losf"
1674543,2020-07-23 08:11:33 UTC,"Reviewed:  https://review.opendev.org/742549
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=0dbf3d0a954522e5f6cc529c6da961ef2f87991d
Submitter: Zuul
Branch:    master"
1674553,2017-09-12 17:32:27 UTC,"There are two aspect, port binding and agent liveness report.
Regarding to port binding, in networking-odl, there is websocket logic and prepopulate logic. with them we don't use polling loop to update agentdb."
1674553,2017-04-03 07:54:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452625"
1674553,2017-11-04 23:12:05 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/452625
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1674565,2017-03-22 16:58:49 UTC,Could you re-run that command with verbose logging on the openstackclient and post those logs? -vvv should do it. Thanks!
1674565,2017-03-22 17:28:25 UTC,Also for your clarification. DNS TTLs are different than IP Packet TTLs. They can be and often are very large. https://en.wikipedia.org/wiki/Time_to_live#DNS_records
1674565,2017-03-23 10:54:57 UTC,"Hi Tim,"
1674565,2017-03-23 12:07:06 UTC,OpenStack Pastebin link
1674565,2017-03-23 12:58:41 UTC,"Looks like the client is treating 0 as null, which means it is not sending the data. need to force the data type of the ttl variable in the client"
1674566,2017-08-04 01:08:04 UTC,"Change abandoned by yfzhao (dsware@126.com) on branch: master
Review: https://review.openstack.org/447839"
1674566,2017-03-21 05:59:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447839"
1674577,2017-03-27 12:01:44 UTC,"Reviewed:  https://review.openstack.org/447832
Committed: https://git.openstack.org/cgit/openstack/oslo.config/commit/?id=4624e9694b796a181d57b7dc6d65df0a3d642183
Submitter: Jenkins
Branch:    master"
1674577,2018-01-15 16:34:28 UTC,This issue was fixed in the openstack/oslo.versionedobjects 1.31.1 release.
1674577,2018-01-08 16:17:36 UTC,"Reviewed:  https://review.openstack.org/449428
Committed: https://git.openstack.org/cgit/openstack/oslo.versionedobjects/commit/?id=2c9258b4edd12f05230f2abe5ce145bfaed3a378
Submitter: Zuul
Branch:    master"
1674577,2017-04-03 10:42:43 UTC,This issue was fixed in the openstack/oslo.config 3.24.0 release.
1674577,2017-04-03 10:43:04 UTC,This issue was fixed in the openstack/oslo.reports 1.19.0 release.
1674577,2017-04-03 10:43:09 UTC,This issue was fixed in the openstack/oslo.utils 3.25.0 release.
1674577,2017-04-03 10:42:49 UTC,This issue was fixed in the openstack/oslo.db 4.20.0 release.
1674581,2017-03-21 06:26:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/447871"
1674581,2017-08-04 01:07:05 UTC,"Change abandoned by yfzhao (dsware@126.com) on branch: master
Review: https://review.openstack.org/447871
Reason: Abandon"
1674583,2017-05-10 10:15:09 UTC,"Reviewed:  https://review.openstack.org/451327
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=eaef60512a2c40c9d9773e9882340a7c52ad1bcb
Submitter: Jenkins
Branch:    stable/newton"
1674583,2017-04-04 09:15:29 UTC,"Reviewed:  https://review.openstack.org/451328
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=262dcc96b48cd6d459600061f135060fda83bef8
Submitter: Jenkins
Branch:    stable/ocata"
1674583,2017-03-29 14:52:25 UTC,"Verified in scope of 9.2 mu1 updates.
Iso was generated using fuel-main stable/mitaka branch.
Gcc package isn't installed on master node:
[root@nailgun ~]# rpm -qa | grep gcc
libgcc-4.8.5-11.el7.x86_64"
1674583,2017-03-29 10:50:35 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/451328"
1674583,2017-04-07 13:05:40 UTC,Verified for master node
1674583,2017-03-24 10:51:18 UTC,"Reviewed:  https://review.openstack.org/448079
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=c1a3e2a1538344901c81caa1dccb2b0d02c90309
Submitter: Jenkins
Branch:    stable/mitaka"
1674583,2017-03-29 10:49:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/451327"
1674583,2017-03-21 06:39:10 UTC,sla1 for 9.0-updates
1674583,2017-04-04 09:11:21 UTC,"Reviewed:  https://review.openstack.org/449228
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=07a98dfa881b548fdae819dda22370a0d930e330
Submitter: Jenkins
Branch:    master"
1674583,2017-03-21 17:24:14 UTC,"I agree that we can easily remove GCC package from Fuel Master. But can't do the same on slave nodes, because GCC is needed in order to support DKMS. Here is the output of 'apt-cache showpkg dkms' command: http://paste.openstack.org/show/603643/
From that output we can see that gcc package mentioned in the dependencies for dkms package."
1674583,2017-03-23 17:11:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449228"
1674583,2017-03-21 12:57:40 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/448079"
1674605,2017-05-11 09:30:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674605,2018-06-25 11:35:45 UTC,I assume I'm affected by the same issue.
1674614,2017-03-21 08:58:57 UTC,I suspect this was already handled by https://bugs.launchpad.net/octavia/+bug/1565511
1674614,2017-03-22 02:41:18 UTC,Sometimes we need to reschedule loadbalancers manually when we need to maintain network nodes.
1674614,2017-06-15 07:44:32 UTC,"Change abandoned by Zhi Chang (<email address hidden>) on branch: master
Review: https://review.openstack.org/447177"
1674614,2017-03-21 09:14:46 UTC,"In our real production, we need to turn off the networks nodes where LBaaS agents run. In such scenario, we need to migrate LBaaS instance from one network node to another, just like L3 routers. In https://bugs.launchpad.net/octavia/+bug/1565511 , loadbalancers will be rescheduled from one network node to another when network node goes offline. I think that this is a passive method. We need a positive method, isn't it?"
1674616,2017-03-21 08:46:42 UTC,Here is the Inkscape screen shot.
1674616,2017-03-21 08:47:27 UTC,Here is the SVG file used.
1674616,2017-03-21 13:32:59 UTC,Possibly related report: https://bugs.launchpad.net/inkscape/+bug/743987.
1674616,2017-03-21 13:39:06 UTC,Forgive me. Pasted in wrong thread. :(
1674616,2020-03-25 08:48:57 UTC,This is a bug in Illustrator's SVG import. Please report it with Adobe.
1674623,2017-04-28 21:38:08 UTC,"The interactive mode currently has no ability to process global options, which is what all of the authentication arguments are, including --os-cloud.  This would be a good thing to have, I've marked this for the wishlist."
1674623,2017-03-29 12:02:07 UTC,"Hi Rui,
Thanks for your replay, Yes this configuration can work for me.
But I could not make it work.
I have edit the file (see attached) and run the command:
'openstack --os-cloud overcloud server list'
The output I got is:
'token'"
1674623,2017-03-27 06:51:35 UTC,"openstackclient use option ""--os-cloud"" and clouds.yaml to mange multiple cloud deployments, please check document[1], helpful for you?"
1674626,2017-03-22 15:21:22 UTC,"We've not done a release of snap.openstack to pypi, but it is installable directly from the git repo."
1674626,2017-03-22 17:37:41 UTC,"Yep, that's what I did.  I raised this because it's referenced in https://github.com/openstack/snap.openstack/blob/master/doc/source/installation.rst"
1674629,2017-03-21 10:00:13 UTC,This change was made by a bot.
1674629,2017-03-21 10:52:04 UTC,"When I am adding the next rule to iptables it all works magically
iptables -I FORWARD -j ACCEPT"
1674629,2017-03-21 18:44:52 UTC,Does this bug go away if you boot back into the prior kernel version?
1674629,2017-03-21 19:48:23 UTC,"@joseph, I found out the coulprit after getting to the same possition with a CentOS system and trying couple kernels.
The issue is being caused by a docker package from the ""official"" repository.
The issue was resolved with the 4.6 kernel since it didn't had the aufs module and there for the docker could not start and do harm.
Once I disable the docker service and reboot the system is back up and running.
But the issue accured with both 4.4.0-x 4.6.x 4.8.0-x when I managed to make the docker start up.
It happen only after upgrading the system so I cannot find the exact version of docker it started."
1674631,2017-03-22 10:54:02 UTC,Same issue with Cairo SVG provided by yourself.
1674631,2017-03-22 10:38:06 UTC,The issue appears really after insertion within Framemaker document and PDF rendering.
1674631,2017-03-22 10:36:59 UTC,I have generated MS40076V2_CAIRO.svg by importing PDF from GUI:
1674631,2017-03-21 13:52:21 UTC,"In order to illustrate clearly the issue, I have attached one PDF generated from single FM source and including all kind of sources:"
1674631,2017-03-21 13:56:37 UTC,More infos
1674631,2017-03-21 09:54:56 UTC,SVG generated with Inkscape (PFDCairo option)
1674631,2017-03-21 09:53:00 UTC,Original PDF
1674631,2017-03-21 09:51:02 UTC,SVG generated with Adobe Illustrator
1674631,2017-03-22 07:27:58 UTC,Thanks for taking the time to file a report!
1674634,2019-12-01 04:17:29 UTC,[Expired for snapd because there has been no activity for 60 days.]
1674634,2019-10-01 22:25:46 UTC,"Dear reporter, please provide the information requested in comment 5"
1674634,2017-03-21 10:23:12 UTC,"Still the same issue:
$ sudo systemctl start snapd.service
$ snap refresh
error: cannot communicate with server: Post http://localhost/v2/snaps: EOF"
1674634,2017-03-21 10:36:48 UTC,http://cdimage.ubuntu.com/ubuntu-core/16/stable/current/ubuntu-core-16-pi3.img.xz
1674634,2017-03-21 10:23:54 UTC,what image did you use exactly ?
1674634,2017-03-21 10:01:39 UTC,"Can you start snapd manually? ""sudo systemctl start snapd.service"""
1674634,2017-03-21 10:47:56 UTC,"after starting snapd, what does systemctl status snapd.service say?"
1674637,2017-03-21 15:34:26 UTC,http://paste.openstack.org/show/603626/
1674637,2017-03-21 15:43:13 UTC,Seems that https://review.openstack.org/#/c/447420/ should help
1674637,2017-04-03 11:12:19 UTC,Verified on 9.x swarms
1674637,2017-04-03 11:18:55 UTC,Seems like test do not fail with this issue anymore
1674637,2017-04-04 09:50:49 UTC,"Failed again on ""9.2 MU-1 iso #04/03/17 13:54"" with same issue"
1674638,2017-04-07 10:50:24 UTC,It seems that there is another rootcause.
1674638,2017-04-07 10:51:39 UTC,"Custom test with https://review.openstack.org/#/c/447990/ (and 50%, 75% too) failed."
1674641,2019-06-15 00:10:11 UTC,"Hi Steve,"
1674642,2018-07-13 04:40:06 UTC,can you tell us which version of tap-as-a-service are you using?
1674649,2017-03-23 12:52:18 UTC,"I've found the root cause (actually my bad :) ), fix is on review https://review.openstack.org/#/c/449125/"
1674649,2017-05-05 06:31:15 UTC,"The patch is merged to master(Pike) [0], backport to stable/ocata which is also affected is also proposed [1]"
1674649,2017-08-15 08:49:51 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1674649,2018-02-09 03:02:58 UTC,This issue was fixed in the openstack/bifrost 3.1.1 release.
1674649,2017-03-21 12:19:06 UTC,This isn't an issue with commit 7164cbfbd85b93e89fc0036a2d7c6428bcf4311e which is just prior to https://review.openstack.org/#/c/444820
1674649,2017-03-21 11:24:12 UTC,Also ran it with the command-line specified in the docs (using -K instead of -e ansible_become=true) and hitting the same error.
1674656,2017-03-30 19:47:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674657,2019-12-11 03:23:22 UTC,Migrated to:  https://gitlab.com/inkscape/inbox/issues/1354
1674667,2017-03-21 12:39:22 UTC,The following shows up when running gnome-maps:
1674667,2017-03-21 12:48:10 UTC,I confirm in zesty.
1674667,2017-03-21 17:12:51 UTC,Which app was that?
1674667,2017-03-21 18:29:08 UTC,"The node will get the style classes .image-button or .text-button, if the content is ""just"" an ""image"" or ""label"", respectively."
1674669,2017-03-30 14:11:16 UTC,"sorry folks, ci-team cannot help here"
1674669,2017-03-29 15:23:15 UTC,In this case - https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.ha_neutron_destructive_vxlan/220/
1674669,2017-03-22 13:33:41 UTC,"StaleDataError has nothing to do with the state of haproxy backends on controllers.
in fact StaleDataError doesn't affect functionality even. It's a minor bug in neutron."
1674669,2017-03-22 12:22:55 UTC,StaleDataError: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched.
1674669,2017-03-29 15:06:46 UTC,"Looks like it was some environment related connectivity issue, all the resources were fine, except rabbitmq on one of the nodes:"
1674669,2017-03-22 13:38:50 UTC,"--------------------- >> end captured logging << ---------------------
2017-03-21 01:38:19 FAILURE Check network connectivity from instance via floating IP (fuel_health.tests.smoke.test_neutron_actions.TestNeutron.test_check_neutron_objects_creation) Time limit exceeded while waiting for removing floating IP to finish. Please refer to OpenStack logs for more details.   File ""/usr/lib/python2.7/site-packages/unittest2/case.py"", line 67, in testPartExecutor
   yield
 File ""/usr/lib/python2.7/site-packages/unittest2/case.py"", line 601, in run
   testMethod()
 File ""/usr/lib/python2.7/site-packages/fuel_health/tests/smoke/test_neutron_actions.py"", line 128, in test_check_neutron_objects_creation
   ""removing floating IP"", server, floating_ip)
 File ""/usr/lib/python2.7/site-packages/fuel_health/common/test_mixins.py"", line 180, in verify
   "" Please refer to OpenStack logs for more details."")
 File ""/usr/lib/python2.7/site-packages/unittest2/case.py"", line 666, in fail
   raise self.failureException(msg)
Step 11 failed: Time limit exceeded while waiting for removing floating IP to finish. Please refer to OpenStack logs for more details."
1674677,2017-03-21 13:34:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674677,2017-03-21 13:48:13 UTC,"EGL seems to be completely broken in both the current version of the nvidia-367 package (which installs 375.39) on Ubuntu 16.04, and also the nvidia-375 package on Ubuntu 16.10. I can't get past the initialisation using eglGetDisplay, same as show in the testcase in the bug description."
1674677,2017-03-21 15:51:03 UTC,"Seems the EGL linking is broken, libEGL.so.1 doesn't link to anything (in both /usr/lib/nvidia-375 and /usr/lib32/nvidia-375)."
1674677,2017-03-22 12:01:13 UTC,"I came to this issue from another route: ever since installing package nvidia-375, I have the following warnings every time APT runs the libc-bin trigger:"
1674677,2017-03-23 00:26:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674677,2017-03-23 00:37:49 UTC,"I have the same problem. Attempting to link against /usr/lib/nvidia-375/libEGL.so.375.39, /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0, and /usr/lib/nvidia-375/libEGL_nvidia.so.375.39  instead of -lEGL does not fix it. It does not fix it as in eglGetDisplay() still returns EGL_NO_DISPLAY."
1674677,2017-03-24 11:10:30 UTC,"My understanding is that libEGL.so.1 is GLVND-based, where libEGL.375.39 is
non-GLVND.  I think both of them are at some level wrappers around
libEGL_nvidia.so, which is much larger than either of the libEGL.so and I guess
contains the meat of Nvidia's EGL implementation."
1674677,2017-03-24 11:25:39 UTC,"This suggests a change to the source package to copy 10_nvidia.json from the upstream package to /usr/share/glvnd/egl_vendor.d/.  I think that libEGL.so.375.39 is vestigial and could be omitted, but that's optional; it doesn't seem to be doing any harm."
1674677,2017-03-25 16:51:27 UTC,Pull request here: https://github.com/tseliot/nvidia-graphics-drivers/pull/9
1674677,2017-03-28 11:46:11 UTC,"Beware my fix comment had a mistake, the linking is the other way round
(you'll have to reinstall nvidia if you already did the wrong linking: sudo apt-get reinstall nvidia-375)"
1674677,2017-04-05 12:14:47 UTC,This bug was fixed in the package nvidia-graphics-drivers-375 - 375.39-0ubuntu3
1674678,2017-03-21 13:20:53 UTC,"@Krzysztof Klimonda,
Please provide controller logs :D"
1674678,2017-03-22 00:40:33 UTC,"I can reproduce this with Juju 2.2-beta1 and I am seeing this in the log:
/
6a9668b3-12f8-46fc-8a71-9c72aef52216: machine-0 2017-03-22 00:36:41 DEBUG juju.apiserver request_notifier.go:69 [10] API connection from 124.186.109.239:39018
6a9668b3-12f8-46fc-8a71-9c72aef52216: machine-0 2017-03-22 00:36:41 DEBUG juju.apiserver request_notifier.go:79 [10]  API connection terminated after 305.06021ms
6a9668b3-12f8-46fc-8a71-9c72aef52216: machine-0 2017-03-22 00:36:42 DEBUG juju.apiserver httpcontext.go:310 sending error: 500 setting new password: cannot set password of user ""xyZ"": transaction aborted"
1674678,2017-03-21 13:34:41 UTC,machine-0.log.gz
1674679,2017-03-21 15:52:23 UTC,"Packaging branches updated, will be in the next round of bugfix releases."
1674680,2017-03-21 14:19:00 UTC,Patch proposal for Zesty.
1674680,2017-03-21 16:28:59 UTC,"The attachment ""zesty_bluez_5.43-0ubuntu2.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1674680,2017-04-06 20:06:08 UTC,Just so you know I'm waiting for zesty release before uploading this.  I don't want to risk causing issues on the release media.  Additionally policy is to only push high priority bug fixes for the few weeks leading up to release.
1674680,2017-08-04 17:59:30 UTC,"Hi Dariusz,"
1674680,2017-08-07 11:31:49 UTC,Artful patch proposal.
1674680,2017-08-07 15:01:46 UTC,Patch proposal for Artful.
1674680,2017-08-07 17:16:43 UTC,Sponsored artful.
1674680,2017-08-07 19:58:18 UTC,This bug was fixed in the package bluez - 5.45-0ubuntu4
1674684,2019-06-06 09:56:40 UTC,Setting to Fix Released as the related MP has been merged a while ago. Please re-open if this bug is still a problem.
1674696,2017-03-21 15:00:43 UTC,Stack trace: http://pastebin.ubuntu.com/24222048/
1674696,2017-03-22 13:07:57 UTC,"Fix committed into lp:ubuntu-terminal-app at revision 359, scheduled for release in ubuntu-terminal-app, milestone Unknown"
1674702,2017-03-23 18:10:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674704,2019-06-12 10:00:21 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017."
1674712,2017-04-23 14:54:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674714,2019-09-19 14:50:23 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1674718,2017-03-24 10:37:58 UTC,"Also found yesterday `lshw` issue in 10.0-community.main.ubuntu.bvt_2 job:
https://ci.fuel-infra.org/job/10.0-community.main.ubuntu.bvt_2/1344"
1674718,2017-03-29 09:33:40 UTC,"Reviewed:  https://review.openstack.org/451284
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=48917f9856f81ca59f591d24e71ef5279bc2e9b7
Submitter: Jenkins
Branch:    stable/ocata"
1674718,2017-03-29 09:33:32 UTC,"Reviewed:  https://review.openstack.org/451285
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=01f57377de57e2ea8f1030d9675a2261ed348770
Submitter: Jenkins
Branch:    stable/newton"
1674718,2017-03-29 09:32:03 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/451285"
1674718,2017-03-29 09:31:53 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/451284"
1674718,2017-03-29 09:31:42 UTC,"Reviewed:  https://review.openstack.org/451274
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=a18d20f7a06cf0f13a92517363248a917d0abc28
Submitter: Jenkins
Branch:    master"
1674718,2017-03-29 09:29:23 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/451274"
1674718,2017-03-29 09:11:54 UTC,"Reviewed:  https://review.openstack.org/449089
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=3d6763a67defaf197c8bc641eefe89c39af3857e
Submitter: Jenkins
Branch:    stable/ocata"
1674718,2017-03-29 09:11:39 UTC,"Reviewed:  https://review.openstack.org/449088
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=c1cc807c30b95897ccac8bfff681a364f6f5672b
Submitter: Jenkins
Branch:    stable/newton"
1674718,2017-03-24 10:39:17 UTC,"In nailgun-agent.log on controller, i mean."
1674718,2017-03-23 11:38:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/449089"
1674718,2017-03-22 10:57:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448505"
1674718,2017-03-23 10:38:29 UTC,"Reviewed:  https://review.openstack.org/448505
Committed: https://git.openstack.org/cgit/openstack/fuel-nailgun-agent/commit/?id=058b0c852f6af10999ad29b747530c3f6c5c15b6
Submitter: Jenkins
Branch:    master"
1674718,2017-03-21 15:04:44 UTC,"I see in messages.log of nodes a message:
Can't find lshw. Reason: 'which lshw' returned exit status 1"
1674718,2017-03-22 10:23:09 UTC,Today build also failed by the same way: https://packaging-ci.infra.mirantis.net/job/10.0-pkg-mos-systest-ubuntu-xenial/744/
1674718,2017-03-22 10:31:56 UTC,"2017-03-22T01:35:10Z notice nailgun-agent:  W, [2017-03-22T01:35:10.023848 #4414]  WARN -- : Can't find lshw. Reason: 'which lshw' returned exit status 1"
1674718,2017-03-22 10:52:51 UTC,"Shouldn’t it be patch into into bootstrap req :
https://github.com/openstack/fuel-agent/blob/master/contrib/fuel_bootstrap/fuel_bootstrap_cli/fuel_bootstrap/settings.yaml.sample#L22 ?"
1674718,2017-03-23 11:38:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/449088"
1674718,2017-03-21 15:34:34 UTC,"Reviewed: https://review.fuel-infra.org/32406
Submitter: Pawel Brzozowski <email address hidden>
Branch: master"
1674718,2017-03-22 11:02:46 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/448507"
1674718,2017-03-23 09:34:14 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: master
Review: https://review.openstack.org/448506
Reason: https://review.openstack.org/#/c/448505/"
1674718,2017-03-23 09:34:28 UTC,"Change abandoned by Oleksiy Molchanov (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/448507
Reason: https://review.openstack.org/#/c/448505/"
1674718,2017-03-23 09:34:58 UTC,https://review.openstack.org/#/c/448505/
1674718,2017-03-22 11:02:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448506"
1674724,2017-04-25 11:42:25 UTC,"Reviewed:  https://review.openstack.org/448264
Committed: https://git.openstack.org/cgit/openstack/network-checker/commit/?id=68fee5e55b880a8e67ddc2b013569ecb496b480a
Submitter: Jenkins
Branch:    stable/newton"
1674724,2017-04-25 11:42:17 UTC,"Reviewed:  https://review.openstack.org/448263
Committed: https://git.openstack.org/cgit/openstack/network-checker/commit/?id=02a5532172927bbc94ef963ccac45d57ebb89d07
Submitter: Jenkins
Branch:    stable/ocata"
1674724,2017-04-25 11:41:25 UTC,"Reviewed:  https://review.openstack.org/448265
Committed: https://git.openstack.org/cgit/openstack/network-checker/commit/?id=be897a171faba0b8769b676816ad4979eb0beabd
Submitter: Jenkins
Branch:    stable/mitaka"
1674724,2017-03-21 20:07:09 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/448265"
1674724,2017-03-21 20:06:52 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/448264"
1674724,2017-03-21 20:06:34 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/448263"
1674724,2017-03-21 18:50:01 UTC,"Reviewed:  https://review.openstack.org/448222
Committed: https://git.openstack.org/cgit/openstack/network-checker/commit/?id=e5debec9fe2d8f1a99521594ca3bb10de3bb6d13
Submitter: Jenkins
Branch:    master"
1674724,2017-03-21 18:16:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448222"
1674734,2017-03-21 15:40:47 UTC,"For reference, i started some work on that at https://code.launchpad.net/~smoser/curtin/trunk.lp1604962 .  I've attached the diff versus revno curtin revno426 (bytes2human: fix for values larger than 32 bit int on 32 bit python2.)."
1674735,2019-09-26 10:32:54 UTC,"Oh dear, sorry we didn't reply to this in a timely manner."
1674741,2017-03-21 16:25:27 UTC,"Hi Rick,"
1674747,2017-04-03 12:49:24 UTC,Could you try using the `fudge` command?
1674747,2017-04-04 02:23:30 UTC,"ntpd[27062]: inappropriate address 10.201.X.Y for the fudge command, line ignored"
1674747,2017-04-04 06:23:19 UTC,"Ah, shame. Thanks for trying that. I suspect we need to make the stratum configurable then."
1674747,2019-09-19 12:03:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1674754,2017-03-21 17:00:11 UTC,This change was made by a bot.
1674759,2017-05-31 03:17:26 UTC,"@Frank, what is your setup like?"
1674759,2017-05-31 03:16:39 UTC,We should ensure our CI tests around proxies also upgrade to confirm behaviour.
1674759,2017-03-23 15:56:46 UTC,"the client can see them fine, i can run juju sync-tools successfully."
1674759,2017-03-22 21:51:32 UTC,"For upgrade-juju, the CLI is attempting to look for what tools are available."
1674759,2017-03-22 14:20:53 UTC,"$ ./juju --version
2.2-alpha1-sierra-amd64
$ ./juju upgrade-juju --debug
15:20:07 INFO  juju.cmd supercommand.go:63 running juju [2.2-alpha1 gc go1.6]
15:20:07 DEBUG juju.cmd supercommand.go:64   args: []string{""./juju"", ""upgrade-juju"", ""--debug""}
15:20:07 INFO  juju.juju api.go:72 connecting to API addresses: [172.20.20.2:17070]
15:20:07 DEBUG juju.api apiclient.go:678 dialing ""wss://172.20.20.2:17070/model/e96f3258-18ba-4b0e-8db0-1753ed2bfe47/api""
15:20:07 DEBUG juju.api apiclient.go:682 successfully dialed ""wss://172.20.20.2:17070/model/e96f3258-18ba-4b0e-8db0-1753ed2bfe47/api""
15:20:07 INFO  juju.api apiclient.go:589 connection established to ""wss://172.20.20.2:17070/model/e96f3258-18ba-4b0e-8db0-1753ed2bfe47/api""
15:20:07 DEBUG juju.juju api.go:263 API hostnames unchanged - not resolving
15:20:07 INFO  juju.juju api.go:72 connecting to API addresses: [172.20.20.2:17070]
15:20:07 DEBUG juju.api apiclient.go:678 dialing ""wss://172.20.20.2:17070/model/e96f3258-18ba-4b0e-8db0-1753ed2bfe47/api""
15:20:08 DEBUG juju.api apiclient.go:682 successfully dialed ""wss://172.20.20.2:17070/model/e96f3258-18ba-4b0e-8db0-1753ed2bfe47/api""
15:20:08 INFO  juju.api apiclient.go:589 connection established to ""wss://172.20.20.2:17070/model/e96f3258-18ba-4b0e-8db0-1753ed2bfe47/api""
15:20:08 DEBUG juju.juju api.go:263 API hostnames unchanged - not resolving
15:20:08 INFO  juju.juju api.go:72 connecting to API addresses: [172.20.20.2:17070]
15:20:08 DEBUG juju.api apiclient.go:678 dialing ""wss://172.20.20.2:17070/api""
15:20:08 DEBUG juju.api apiclient.go:682 successfully dialed ""wss://172.20.20.2:17070/api""
15:20:08 INFO  juju.api apiclient.go:589 connection established to ""wss://172.20.20.2:17070/api""
15:20:08 DEBUG juju.juju api.go:263 API hostnames unchanged - not resolving
15:20:08 DEBUG juju.cmd.juju.commands upgradejuju.go:426 searching for tools with major: 2
15:20:09 DEBUG juju.environs.sync sync.go:302 Making agent binary tarball
15:20:09 DEBUG juju.environs.tools build.go:126 looking for: ./juju
15:20:09 DEBUG juju.environs.tools build.go:165 checking: /Users/cnf/Clients/Telenet/OpenStack/juju/jujud
15:20:09 INFO  juju.environs.tools build.go:168 couldn't find existing jujud
no prepackaged tools available, using local agent binary 2.2-alpha1.1
15:20:09 DEBUG juju.api monitor.go:35 RPC connection died
15:20:09 ERROR cmd supercommand.go:458 no matching tools available
15:20:09 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/tools/list.go:19: no matching tools available}])
[1]    1427 exit 1     ./juju upgrade-juju --debug"
1674759,2017-03-21 23:51:44 UTC,This may have been fixed on 2.2 as part of the fix for bug # 1654591.
1674759,2017-05-31 03:15:54 UTC,Upgrade juju doesn't use apt to get the tools. What is the http-proxy set to?
1674760,2017-03-21 17:42:25 UTC,"StacktraceTop:
 ?? ()
 ?? ()
 QQuickScrollBarAttached::qt_metacall (this=0x564bfec814e0, _c=QMetaObject::WriteProperty, _id=<optimized out>, _a=0x7fffda9a8090) at .moc/moc_qquickscrollbar_p.cpp:446
 Direct (property=..., n=0x0, output=0x7fffda9a8070, object=0x564bfec814e0) at jsruntime/qv4qobjectwrapper.cpp:135
 LoadProperty<ReadAccessor::Direct> (v4=0x564bfe874b70, object=0x564bfec814e0, property=..., notifier=0x0) at jsruntime/qv4qobjectwrapper.cpp:160"
1674760,2017-03-30 13:34:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674760,2017-04-22 04:50:19 UTC,"plasma-discover crashes every time I try to close it.
This is a fresh install of Kubuntu 17.04 64 bit in a virtualbox."
1674760,2017-05-21 20:04:29 UTC,Have you solved this yet because I have seen it several times. I think it may have messed up my shiny new Kubuntu 17.04 system.
1674760,2017-07-24 16:36:56 UTC,"Just installed on a new system, and like everyone else is saying, it crashes.."
1674760,2017-07-25 07:28:36 UTC,"It's still the same with using Kubuntu Backports which gives you Plasma 5.4.10, Frameworks 5.36 and QT 5.7.1"
1674760,2017-07-26 12:52:11 UTC,I can confirm that Discover has (nearly) always crashed for me upon closing. Kubuntu 17.04.
1674760,2017-08-29 11:49:08 UTC,"I also confirm this bug. I am affected by it. But not only does Plasma Discover crash upon closing.
SMPlayer also crashes.
I am running Kubuntu 17.04 with the backported packages."
1674760,2017-09-22 08:29:25 UTC,"Confirmed! plasma-discover crashes upon closing.
Kubuntu 17.04
KDE Plasma Version: 5.9.5"
1674760,2018-08-21 15:00:16 UTC,"I added flatpak, added a couple of apps and now, no apps, no discover. Discover won't open but shows the update icon but won't open updater. Discover also won't open at all from icon or usr/bin/plams-discover. Synaptic still works, stills shows plasma-discover in list. Can find Plasma-discover in usr/bin but not the apps anywhere. Tried reinstalling, no change. Ultimate Edition 5.7 x64. KDE Plasma Version 5.10.5, KDE Frameworks 5.38.0, QT 5.9.1, Kernal 4.13.0-46.   Everything else works fine."
1674763,2017-03-21 17:30:13 UTC,This change was made by a bot.
1674763,2018-08-23 19:45:08 UTC,"I experience this, too, in bionic."
1674775,2017-04-20 11:57:51 UTC,"Hi Madhuri, sure, it is all yours. Thanks!"
1674775,2017-11-14 01:24:28 UTC,"I was going to ask for a spec because API changes require a spec, but there should really be minimal changes for this. The API and osc CLI should be similar/consistent with how this is handled for the other ironic resources. Will see what others think, I'm good w/o one."
1674775,2017-11-14 14:30:33 UTC,"Julia is also good with approving this w/o a spec: around 14:27, http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2017-11-14.log.html"
1674775,2017-03-31 09:42:18 UTC,"Hi Ruby,"
1674778,2017-05-04 09:22:56 UTC,"Hi all,"
1674778,2017-04-10 07:36:58 UTC,"Hi, guys!"
1674778,2017-03-28 15:00:20 UTC,"So, this OOMing is definitely a bug we need to address, and it's the reason you're not being able to debug this issue"
1674778,2017-03-28 09:19:39 UTC,"(setting back to ""new"" while we work on reproducing it)"
1674778,2017-03-28 07:15:03 UTC,"Sorry, John, I just wanted to do final tests. Sent you a download link in a personal message."
1674778,2017-03-27 10:47:04 UTC,"Renat, have you sent me this? I can't find it in my email (but I get a lot)."
1674778,2017-04-14 06:59:35 UTC,"Hi all,"
1674778,2017-03-24 08:51:08 UTC,"I am not sure that I am allowed to send you the image/snap, sorry for this=("
1674778,2017-03-22 20:07:46 UTC,"Renat, any chance we can look at the snap itself? Hoping to reproduce this."
1674778,2017-03-22 18:27:41 UTC,"Hi, John!"
1674778,2017-03-22 18:23:34 UTC,"Hi, Kyle!"
1674778,2017-03-21 19:14:46 UTC,"Can you please check/confirm that you get the same problem when you first download your custom gadget snap from the store manually and then build it into your image using the ubuntu-image command with the --extra-snaps YOURDOWLOADEDSNAP.snap arg.  Note that the "".snap"" file extension is needed to ensure the local filesys snap is used."
1674778,2017-03-22 14:26:56 UTC,Hello!
1674778,2017-03-24 09:15:13 UTC,"Okay, I am allowed to send you an image."
1674785,2017-04-13 05:54:21 UTC,"I'm open to the idea, but looking for a bit more design on the input fields for the old and new page names."
1674785,2017-04-13 14:30:38 UTC,"Hmm... yes, I'm not sure I fully considered those points originally."
1674785,2017-04-14 00:19:32 UTC,"Thanks for the new mock-up. I think you are right, combining in a single
dialog is an improvement already. Better widgets is a next step that can be
independent."
1674809,2017-06-27 15:58:06 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'"
1674809,2017-03-21 20:13:31 UTC,"The test is waiting for the server to go to from BUILD status and then once it does, it asserts that it's status is ACTIVE."
1674809,2017-03-21 19:59:32 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=(message%3A%5C%22nova.tests.functional.api.client.OpenStackApiNotFoundException%3A%20Item%20not%20found%5C%22%20OR%20message%3A%5C%22b'nova.tests.functional.api.client.OpenStackApiNotFoundException%3A%20Item%20not%20found'%5C%22)%20AND%20tags%3A%5C%22console%5C%22&from=7d
1674809,2017-05-03 13:25:03 UTC,Similar one show up at here http://logs.openstack.org/32/461732/2/check/gate-nova-tox-functional-ubuntu-xenial/83038b5/testr_results.html.gz
1674817,2017-03-24 20:41:00 UTC,https://github.com/pvaret/rtl8192cu-fixes
1674817,2017-03-29 14:38:58 UTC,"Thanks for hints but I don't understand how to use it. I would need
a ready made solution, like a new driver to install. My wireless is very common and the solution should useful for many users."
1674817,2017-07-27 16:10:34 UTC,Updated to Mint 18.2 Sonya KDE version. Bug still present and wireless still unusable.
1674818,2019-09-19 11:56:13 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1674833,2017-03-28 15:09:40 UTC,What boto version are you using?
1674833,2017-03-30 15:09:51 UTC,"My Boto is from EPEL, versions are:"
1674833,2017-03-27 15:42:09 UTC,Try removing the .part file.  That should solve the problem.
1674833,2017-03-27 19:42:54 UTC,"Thanks, but it does not really solve my problem."
1674833,2017-03-22 11:35:33 UTC,"Could you do an 'ls -l' on /root/.cache/duplicity/
652b29dc986d2c5850695bd80bf5261a/?"
1674833,2017-03-21 22:25:42 UTC,Last 200 lines of output
1674833,2017-03-22 19:22:47 UTC,"Upgraded it to 0.7.12, but it did not fix error, last backup is done with version 0.7.12 (.manifest.part is left behind):"
1674833,2017-03-21 22:24:54 UTC,First 200 lines of output
1674837,2017-03-21 22:09:24 UTC,"Let me know if I should attach any logs, although there are *no* traces anywhere, at least with default log levels (without recompiling)."
1674837,2017-03-21 22:30:45 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1674837,2017-07-26 15:23:20 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1674840,2018-02-22 00:43:23 UTC,"Change abandoned by sunzuohua (<email address hidden>) on branch: master
Review: https://review.openstack.org/518461"
1674840,2017-03-22 19:12:38 UTC,"I think it is because the current network deletion code doesn't follow the sequence as the network creation, the deletion should follow the reverse sequence(like the operations push and pop in a stack) to release related resources."
1674840,2017-03-22 23:08:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448822"
1674840,2017-03-24 20:06:29 UTC,"Segments can be deleted independently of networks. If you always need segmentation IDs of them, I think you will need to subscribe to segment AFTER/BEFORE delete events."
1674840,2017-11-05 11:18:32 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/448822
Reason: This review is > 3 months without comment and currently blocked by a core reviewer with a -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -1 on this review to ensure you address their concerns."
1674840,2017-11-07 07:29:33 UTC,"Hi,Sam su：
    This bug also affects me.
    Will you continue to fix it?
    If not,I will try to fix it."
1674840,2017-11-07 16:37:11 UTC,"Yes, feel free to fix it. Just FYI, before submitting your code, you'd better to discuss your solution with Kevin Benton first."
1674840,2017-11-08 06:54:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518461"
1674847,2019-12-16 04:17:13 UTC,[Expired for Snappy because there has been no activity for 60 days.]
1674847,2019-10-15 12:48:26 UTC,Is this effort still under way? Can you please come to us to work together on this issue?
1674847,2017-03-22 09:43:21 UTC,"the manifest exists on the launchpad build page, but we have no way to actually bind it to a snap revision because that matching only happens after store upload ..."
1674847,2019-10-16 05:04:00 UTC,"Manifests are also produced by the launchpad builds, e.g.:"
1674860,2017-03-22 02:39:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448350"
1674860,2017-03-23 01:31:19 UTC,"Change abandoned by zhangdaolong (<email address hidden>) on branch: master
Review: https://review.openstack.org/448350"
1674860,2017-09-26 22:51:01 UTC,Unassigning due to no activity for > 6 months.
1674862,2017-05-11 09:50:50 UTC,"Fix proposed to branch: 9.0
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/35264"
1674862,2017-06-26 12:45:15 UTC,"Can't reproduce the error on a test environment due to lack of appropriate HW. In accordance with our policy, fix should be verified on the customer side."
1674862,2017-05-30 15:39:52 UTC,"Reviewed: https://review.fuel-infra.org/35264
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0"
1674862,2017-05-11 09:54:45 UTC,"Change abandoned by Dmitry Teselkin <email address hidden> on branch: 9.0
Review: https://review.fuel-infra.org/35258"
1674862,2017-05-11 08:24:35 UTC,"Fix proposed to branch: 9.0
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/35258"
1674862,2017-03-24 15:44:14 UTC,"Fix proposed to branch: 10.0/newton
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/32519"
1674862,2017-03-24 15:47:05 UTC,"Reviewed: https://review.fuel-infra.org/32488
Submitter: Pkgs Jenkins <email address hidden>
Branch: master"
1674862,2017-03-23 16:29:17 UTC,"Fix proposed to branch: master
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/32488"
1674862,2017-03-23 17:56:02 UTC,"Hi Ivan,"
1674862,2017-03-23 17:02:49 UTC,It's a little bit confusing me when people from Intel sends me to sourceforge for intel drivers.
1674862,2017-03-27 12:21:50 UTC,CR 32519 was merged
1674866,2019-09-19 12:03:13 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1674866,2020-04-08 10:12:40 UTC,"I've come across this -- we have two subnets in spaces, each with a gw. This results in two default routes like these:"
1674866,2020-04-10 10:21:10 UTC,This is a valid feature request.
1674871,2017-06-20 19:55:09 UTC,"This is getting really expensive.  Any update on a smarter cost/constraint algorithm?  This doesn't just affect ""mem=7G"" as initially reported.  It also affects plain 'ol bootstrap."
1674871,2017-03-29 17:33:51 UTC,The stinker here is that our big data bundles use a least-common-denom for constraints across all clouds.  This means mem and cores instead of instance-type.  Here's where it hurts:
1674871,2017-03-29 05:49:17 UTC,"As there is a workaround of asking for specific instance type, I'll re-triage it back as Medium."
1674871,2017-03-29 05:45:41 UTC,"If you *really* want n1-standard-2 you can do ""juju deploy --constraints instance-type=n1-standard-2"""
1674871,2017-03-22 14:17:00 UTC,"Anastasia, with this issue ff you want 7g ram and juju selects n1-highcpu-8 that means a customer pays $145 a month just on the VM w/o storage whereas if it would select n1-standard-2 it would be only $49 a month.  I would think this is higher than an medium priority."
1674871,2017-03-29 05:46:46 UTC,"It would be possible to try and use some other metric, like N-CPU * Memory, or some sort of Weighted CPU cost + Memory Cost, etc, but all of them are likely to have weird failure modes if we aren't using real pricing info."
1674883,2017-03-22 05:34:41 UTC,"You can avoid this by renaming your XML file that you are working on and loading from that file in the preferences instead of the autogenerated one. If you would like to contribute your mapping to be included in Mixxx, please follow the naming convention:
http://mixxx.org/wiki/doku.php/contributing_mappings#file_naming_convention"
1674883,2017-03-24 02:36:15 UTC,"I noticed this again lately when implementing components-js.
Sometimes its just quicker to adjust the mapping directly in the xml than in the mapping window."
1674886,2017-03-22 20:27:26 UTC,It's not a glance server problem. And I don't think it's a bug but an enhancement for the client.
1674886,2017-07-26 11:33:06 UTC,"Operation image upload is performed in below three steps:
STEP 1) Chunking of the image : The large size image file is divided into smaller size chunks.
STEP 2) Validation of image ID. If image ID is valid then proceed to Step 3 else EXIT.
STEP 3) Uploading of the chunks to the empty container."
1674896,2017-08-05 06:47:29 UTC,"Should check the vnfs' status after ns_create in ns_db.create_ns_post,like this:"
1674900,2017-03-22 07:47:35 UTC,"workaround - following.
add experimental in FEATURE_GROUPS and run:
puppet apply /etc/puppet/modules/fuel/examples/nailgun.pp"
1674917,2019-12-18 17:10:47 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/450632
Reason: This repo is retired now, no further work will get merged."
1674917,2017-04-05 06:51:00 UTC,"Reviewed:  https://review.openstack.org/450638
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=152f029f38d53382b54ae4e0f2ee58ec48530fef
Submitter: Jenkins
Branch:    master"
1674917,2017-03-22 08:56:43 UTC,Snapshots can be found by link: https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.network_templates/216/
1674917,2017-03-24 09:13:26 UTC,"2017-03-24 03:33:21 - ERROR test_net_templates_base.py:421 -- Service ""ceph-radosgw"" (port 6780/tcp) is listening on wrong IP address(es) on ""node-1"": expected ""set(['10.200.254.1'])"", got ""set(['0.0.0.0'])""!
2017-03-24 03:33:25 - ERROR test_net_templates_base.py:421 -- Service ""ceph-radosgw"" (port 6780/tcp) is listening on wrong IP address(es) on ""node-3"": expected ""set(['10.200.254.3'])"", got ""set(['0.0.0.0'])""!
2017-03-24 03:33:27 - ERROR test_net_templates_base.py:421 -- Service ""ceph-radosgw"" (port 6780/tcp) is listening on wrong IP address(es) on ""node-2"": expected ""set(['10.200.254.2'])"", got ""set(['0.0.0.0'])""!"
1674917,2017-03-28 08:46:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/450638"
1674917,2017-03-22 09:00:28 UTC,"Firstly necessary to investigate where is problem (Test or Prod), so I have assigned it on QA team."
1674922,2017-03-22 09:53:40 UTC,Thanks for reporting this issue.
1674925,2021-01-20 04:17:21 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1674925,2020-11-20 19:31:47 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1674925,2017-03-30 18:26:10 UTC,"sorry for the extra comment on g5 quad i use this options
gigi@gigi-desktop:~/qemu-2.9.0-rc1/ppc64-softmmu$ sudo ./qemu-system-ppc64 -enable-kvm -m 1024 -display sdl,gl=on -device virtio-gpu-pci,virgl  --nodefaults -vga none  -M pseries-2.5 -smp 2 -serial stdio"
1674925,2017-03-30 18:22:12 UTC,"Hi thomas,
this is the quad G5 shot on ubuntu mate 17.04 with last stable kernel 4.10.7 with xics builded inside
you can see i have the same result i have on Qoriq on fedora ppc64 . the only way for see something is use -serial stdio option"
1674925,2017-03-30 16:29:06 UTC,"attched the booted mate 16.10 Qemu system ppc64 --kvm on Qoriq without video initialized
only way i have to see something is with --serial stdio"
1674925,2017-03-30 16:25:28 UTC,"hi thomas on Qoriq Xics isnt present and cant be selected and i dont have video output too
this is a shot of the kernel config.
On G5 Quad i will made a shoot too i thinks screenshots is better then may english knowledge :P"
1674925,2017-03-30 14:12:21 UTC,"When you use ""-vga none"" or ""-nodefaults"" with that kernel where you've enabled xics, do you now get some output in the windows once Linux has booted?"
1674925,2017-03-24 11:31:03 UTC,"Hi Cèdric,"
1674925,2017-03-22 19:15:29 UTC,"Hello Cédric,"
1674925,2017-03-22 17:49:59 UTC,"Hi Cédric,"
1674925,2017-03-22 14:25:25 UTC,"Hi Thomas,"
1674925,2017-03-22 13:35:09 UTC,Hi Thomas with 2.9 rc1 i have this with --enable-kvm
1674925,2017-03-22 11:40:26 UTC,"Hi Thomas, thanks for your reply i will test and report my experience ASAP"
1674925,2017-03-22 10:11:54 UTC,"Hi! I think unless you use ""-vga none"" or ""-nodefaults"", QEMU will always start your guest with a VGA card by default, so if you add an additional ""--device virtio-gpu-pci"", you'll end up with a guest that has two video cards, one VGA and one virtio-gpu.
Also there is a known bug in the SLOF version that has been shipped with QEMU 2.8, which causes trouble with virtio-gpu:
http://git.qemu-project.org/?p=SLOF.git;a=commitdiff;h=38bf852e73ce6f0ac801dfe8ef1545c4cd0b5ddb
Please try again with the latest release candidate of QEMU 2.9, it should be fixed there.
(But please note that SLOF does not contain a driver for virtio-gpu, so you won't see any output from the firmware when starting your guest ... i.e. you'll just see some output once Linux has been started)"
1674925,2017-03-24 17:14:55 UTC,"Hi Cèdric,"
1674925,2017-03-24 21:27:00 UTC,"Hi,"
1674926,2017-10-23 16:48:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674930,2017-04-09 04:40:12 UTC,nvidia-367 was removed as part of the CVE-2016-8826 & CVE-2017-0318 fix in #1659586
1674930,2017-04-21 01:14:16 UTC,It would be good if the legacy drivers (nvidia-367) were reinstated and not made transitional. Maybe they should be named appropriately to reflect that they should only be used for grid GPUs or that they are legacy - `nvidia-grid`/`nvidia-grid-legacy`.
1674930,2017-04-07 17:19:00 UTC,"That workaround doesn't work for me because of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1655584, which loads the nvidia kernel module repeatedly."
1674930,2017-03-22 14:45:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674930,2017-04-06 18:19:37 UTC,"as a temporary workaround I installed the drivers manually
`
apt-get install build-essential -y
curl -O http://us.download.nvidia.com/XFree86/Linux-x86_64/367.57/NVIDIA-Linux-x86_64-367.57.run
chmod +x ./NVIDIA-Linux-x86_64-*.run
./NVIDIA-Linux-x86_64-*.run -q -a -n -X -s
`"
1674931,2017-03-22 10:58:47 UTC,The problem is we're not seeding the right language packs...
1674931,2017-03-23 15:57:38 UTC,"After a bit of discourse:
* whatever language packs are preinstalled on ISOs need to include .mos for whatever's on the ISO (unity8, ubuntu-system-settings etc.)
* system settings app needs to list all languages and install language packs (and OSK layouts, if ubuntu-keyboard itself is installed?) on demand
* <dobey> seems to me it would be easier/better to just get rid of langpacks :)"
1674931,2017-03-23 16:06:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674931,2017-03-23 19:57:37 UTC,"As a workaround, you need to install ""language-package-gnome-XX"" for the language you want (or use the language-selector-gtk tool to do it for you). Then the language should be available in Unity8 system-settings."
1674965,2017-03-22 12:40:34 UTC,is there any need to have the versioned files at all ?
1674965,2017-03-22 14:34:59 UTC,"we are currently creating hardlinks, the PR switches that to symlinks. I am not sure what the gain is"
1674965,2017-03-22 14:35:43 UTC,PR https://github.com/snapcore/snapcraft/pull/1207
1674971,2017-03-24 10:24:45 UTC,The patch is merged: https://review.openstack.org/#/c/448520/
1674977,2017-03-23 02:28:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1674977,2017-03-23 02:28:32 UTC,"Oh, you're right."
1674977,2017-03-23 02:26:39 UTC,Are you really sure there is no 'Xmir' process automatically running in the background? --> bug 1672931
1674996,2020-01-25 22:05:20 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1674998,2017-05-02 11:55:57 UTC,"Confirmed on Xubuntu 16.04, Inkscape 0.91, lp:inkscape/0.92.x rev. 15420 and lp:inkscape rev. 15658."
1674998,2017-05-02 17:55:44 UTC,"Thank you, jazzynico, for having a look!"
1674998,2020-11-27 11:47:08 UTC,"Any news? With the font options being sticky on the side panel, now this bug hits me every single time I try to tweak a font, because I no longer ""open the font dialog"". It's not even a dialog now.
I'd like to suggest a higher priority, because it's extremely frustrating."
1674998,2020-11-27 12:10:42 UTC,"You're looking at the wrong bug tracker, Ruben (this one is being moved to https://inkscape.org/report) - and I cannot follow the observations you are describing."
1674998,2020-11-27 14:29:45 UTC,"Thanks! I downloaded 1.0.1 and you are right, it's fixed in that version already."
1674998,2020-11-27 23:28:58 UTC,"Thanks, I'll take the Spanish translation offline until some Spanish translator comes along to fix it."
1674998,2020-11-27 23:45:52 UTC,"Done. Unfortunately, the website auto-redirection to show English as a fallback if a translation does not exist does not kick in, so the link yields a 'page not found' error."
1675000,2017-03-23 09:08:30 UTC,"On 22/03/17 14:15, AlainKnaff wrote:
[...]

> N.B. It does work if Swiss German is chosen, rather than Swiss French.
"
1675002,2017-03-31 12:36:56 UTC,This is also confirmed on my new Dell XPS 13 (9360)
1675012,2017-03-22 13:41:07 UTC,I'm seeing browser not even launch if it's requested in picking mode and it's not currently running. Testing on unity8
1675012,2017-03-22 22:53:50 UTC,"I’m seeing that on my krillin running the latest rc-proposed.
I’ve also seen this once on my desktop (unity7) where attaching a file in the telegram app would open the browser app (not previously running) on the downloads page, but not in picking mode."
1675013,2017-03-22 13:30:57 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1675013,2017-03-23 11:33:48 UTC,apport information
1675013,2017-03-23 11:33:50 UTC,apport information
1675013,2017-03-23 11:33:51 UTC,apport information
1675013,2017-03-23 11:39:29 UTC,"Added bug report with apport, but as this bug is not always triggered, it is difficult to tell if apport collected useful info. Anyway, here is a bug confirmation: https://github.com/OpenSC/OpenSC/issues/683#issuecomment-187950478"
1675014,2019-12-18 17:18:50 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/448636
Reason: This repo is retired now, no further work will get merged."
1675014,2017-04-07 06:43:37 UTC,The patch (https://review.openstack.org/448636) was not merged to newton branch - moving to correct milestone and status
1675014,2017-03-22 15:21:11 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/448636"
1675014,2017-03-22 15:20:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/448635"
1675014,2017-03-23 08:57:31 UTC,"Reviewed:  https://review.openstack.org/448635
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=27137a5dbd50210781edaf9a0a5d1fc56d64fc0e
Submitter: Jenkins
Branch:    master"
1675020,2017-03-23 21:31:00 UTC,bug 1657029 is possibly related.
1675023,2017-03-23 17:25:33 UTC,"> it consistently produces the same hash which doesn't match with the ones to be found at the second or third sites listed above.
"
1675023,2017-03-23 17:25:49 UTC,"Hi,"
1675024,2017-07-04 14:50:02 UTC,Have you tried 17.04 if it boots up?
1675024,2017-07-05 04:51:57 UTC,"> Have you tried 17.04 if it boots up?
"
1675024,2017-09-04 04:17:25 UTC,[Expired for xserver-xorg-video-nouveau (Ubuntu) because there has been no activity for 60 days.]
1675034,2017-03-29 10:29:59 UTC,Unable to confirm problem on lab. Besides it is green now on SWARM. Looks like we have issue with timeout on pacemaker or incorrect detection on step 8.
1675034,2017-04-03 09:23:37 UTC,"All 3 ""Controller Maintenance Mode"" jobs catch this bug in 04/01/17 run"
1675048,2017-03-23 01:29:59 UTC,Well... interesting.
1675048,2017-03-23 13:16:41 UTC,"@thumper I noticed they were set up the same, and was puzzled by the difference in behaviour.  I suspect juju is wrong to exit nonzero when SIGTERMed.  It may make sense to set both to restart=always, or maybe we're only worried about ""non-clean"" signals, i.e. those excluding ""SIGHUP, SIGINT, SIGTERM or SIGPIPE"""
1675048,2017-03-24 02:27:54 UTC,"Aaron, I think you are right in that Juju should not exit with a non-zero when dealing with SIGTERM."
1675054,2017-04-05 07:18:54 UTC,"Work has started, but some open questions needs to be resolved first, I started a discussion in https://forum.snapcraft.io/t/channels-2-0-implementation/156"
1675054,2017-04-05 18:37:44 UTC,Thanks Michael!
1675083,2017-04-20 14:57:19 UTC,"Reviewed:  https://review.opencontrail.org/30577
Committed: http://github.com/Juniper/contrail-web-controller/commit/71ace073ad4f4e57f0b0dfc9686471c2b2c46de4
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1675083,2017-04-21 23:56:38 UTC,It was fixed in mainline with https://github.com/Juniper/contrail-web-controller/commit/abac8ca7ee43084fdd21d0ad6746dc730f24e40c
1675083,2017-04-18 15:37:33 UTC,"The issue is replicated with 3.2.1.0-29.
Please take a look at doc screenshots.
Any change in network (add policy) will cause setting the first IPAM object in the list."
1675083,2017-04-19 11:10:40 UTC,"Review in progress for https://review.opencontrail.org/30577
Submitter: Siva Bavanasi (<email address hidden>)"
1675091,2017-03-22 17:00:14 UTC,This change was made by a bot.
1675091,2017-03-22 18:07:13 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1675091,2017-03-23 16:12:17 UTC,kernel 4.11.0-041100rc3-generic failed with the same symptoms.
1675091,2017-03-23 16:26:17 UTC,The important bits of udev seem to be these:
1675091,2017-03-23 17:04:16 UTC,"I've been looking at this (on and off), and it seems to reach close to the end of UdevadmParser.run() (in udevadm.py) with the data intact, but it gets lost in the last line or in transferring control out, in the main() function of the udev_resource script."
1675097,2017-03-22 17:28:57 UTC,We don't explicitly give version because we are currently forcing the deployers to re-install ansible with our bootstrap script. (See https://docs.openstack.org/project-deploy-guide/openstack-ansible/ocata/deploymenthost.html)
1675117,2017-03-27 23:18:16 UTC,"On 27.03.2017 [22:00:47 -0000], Kelvin Middleton wrote:

> Hi Nish, so still have the same problem with 7.0.17.  Have logged a bug
> with PHP here... https://bugs.php.net/bug.php?id=74320
"
1675117,2017-03-27 22:00:47 UTC,"Hi Nish, so still have the same problem with 7.0.17.  Have logged a bug with PHP here... https://bugs.php.net/bug.php?id=74320"
1675117,2017-03-27 19:30:06 UTC,Hello and thank you for filing this report.
1675125,2017-03-22 18:56:48 UTC,"The same problem occurs with the others Print Screen shortcuts (Alt + Print, Shift + Print, Ctrl + Print)"
1675127,2017-03-22 22:28:13 UTC,I can only reproduce this particular laptop and this bug does not occur if I plug into ethernet on the same laptop.
1675127,2017-03-23 09:09:20 UTC,"Mar 22 18:33:22 lubuntu ubiquity[1674]: switched to page wireless
Mar 22 18:33:27 lubuntu systemd-resolved[1384]: Switching to fallback DNS server 8.8.8.8.
Mar 22 18:33:46 lubuntu ubiquity[1674]: Exception in GTK frontend (invoking crash handler):
Mar 22 18:33:46 lubuntu ubiquity[1674]: Traceback (most recent call last):
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py"", line 1497, in on_next_clicked
Mar 22 18:33:46 lubuntu ubiquity[1674]:     if ui.plugin_on_next_clicked():
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/ubiquity/plugins/ubi-wireless.py"", line 163, in plugin_on_next_clicked
Mar 22 18:33:46 lubuntu ubiquity[1674]:     self.nmwidget.connect_to_ap()
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py"", line 333, in connect_to_ap
Mar 22 18:33:46 lubuntu ubiquity[1674]:     self.view.connect_to_selection(passphrase)
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py"", line 249, in connect_to_selection
Mar 22 18:33:46 lubuntu ubiquity[1674]:     ssid = model[iterator][0]
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/python3/dist-packages/gi/overrides/Gtk.py"", line 801, in __getitem__
Mar 22 18:33:46 lubuntu ubiquity[1674]:     aiter = self._getiter(key)
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/python3/dist-packages/gi/overrides/Gtk.py"", line 789, in _getiter
Mar 22 18:33:46 lubuntu ubiquity[1674]:     aiter = self.get_iter(key)
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/python3/dist-packages/gi/overrides/Gtk.py"", line 823, in get_iter
Mar 22 18:33:46 lubuntu ubiquity[1674]:     path = self._coerce_path(path)
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/python3/dist-packages/gi/overrides/Gtk.py"", line 798, in _coerce_path
Mar 22 18:33:46 lubuntu ubiquity[1674]:     return TreePath(path)
Mar 22 18:33:46 lubuntu ubiquity[1674]:   File ""/usr/lib/python3/dist-packages/gi/overrides/Gtk.py"", line 1157, in __new__
Mar 22 18:33:46 lubuntu ubiquity[1674]:     path = "":"".join(str(val) for val in path)
Mar 22 18:33:46 lubuntu ubiquity[1674]: TypeError: 'NoneType' object is not iterable
Mar 22 18:33:46 lubuntu ubiquity[1674]:"
1675127,2017-03-23 09:19:40 UTC,From syslog
1675127,2017-03-23 10:36:16 UTC,"STEPS:
1. Copy latest iso to pendrive
2. Have a laptop with broadcom wifi
3. Have a usb wifi stick
4. Insert the usb wifi stick and pendrive, fire up the laptop and boot from usb
5. Select live desktop mode
6. Try and connect to the wifi ap via the usb wifi chip"
1675127,2017-03-29 16:39:16 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1675133,2017-03-24 00:52:51 UTC,"Hi, Thanks for the report."
1675133,2017-03-24 12:19:41 UTC,"My issue is a little different all though it is good to understand the ordering issue. In the call that I'm mocking, I'm using the params keyword to specify the query parameters. I have been unable to match on these query parameters. In addition, they do not show up in the request history. This is important for my use case as the function being tested fills in the params based on passed in parameters. Below is an example of the function I'm trying to test using the mock_requests:"
1675133,2017-03-27 03:01:07 UTC,"How are you looking them up in request history? params={} is a helper that requests provides that constructs a query string, by the time request_mock gets to work with it they will be part of the request so I can't see how that should affect it."
1675133,2017-03-27 15:21:06 UTC,"Jammie,"
1675133,2017-03-27 15:48:51 UTC,"I found something that might be bug. If I'm mocking a request where the query string value has uppercase, the m.last_request.query returns lower all lower case. If I change your example from above a little bit, you can see what happens."
1675133,2017-03-28 04:18:55 UTC,"Oh! I definitely should have thought of that bug [1]. Yes, that's one that I unfortunately can't change without a major version bump because I know some people rely on it. That's a pure bug that something that was used for simply case insensitive matching ended up getting exposed to users."
1675141,2017-06-30 12:27:56 UTC,"corrado@corrado-art3:~/Documents$ ./inxi -Fx
System:    Host: corrado-art3 Kernel: 4.11.0-9-generic x86_64 (64 bit gcc: 6.3.0)
           Desktop: Gnome 3.24.2 (Gtk 3.22.15-0ubuntu2) Distro: Ubuntu Artful Aardvark (development branch)
Machine:   Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x UEFI: American Megatrends v: F3 date: 04/24/2013
CPU:       Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13567
           clock speeds: max: 3400 MHz 1: 3400 MHz 2: 2720 MHz 3: 1712 MHz 4: 3400 MHz
Graphics:  Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.3) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.88hz
           OpenGL: renderer: Mesa DRI Intel Haswell version: 4.5 Mesa 17.1.2 Direct Render: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.11.0-9-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 94:de:80:7e:90:a7
Drives:    HDD Total Size: 1000.2GB (1.5% used)
           ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 32G used: 6.1G (21%) fs: ext4 dev: /dev/sda8
           ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 225 Uptime: 1:52 Memory: 1020.8/7861.1MB Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.121) inxi: 2.3.22
corrado@corrado-art3:~/Documents$"
1675141,2018-08-06 17:00:05 UTC,"Five identical bugs have been autoduplicated to here:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1700391
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1720474
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1744450
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1756632
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1761702
All are ""lightdm crashed with SIGSEGV in _dl_fini()"" rather than munmap()
If these are not the same bug then those 5 should be merged and unduplicated from this bug."
1675141,2017-03-27 12:32:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675141,2017-03-22 19:24:37 UTC,"StacktraceTop:
 munmap () at ../sysdeps/unix/syscall-template.S:84
 _dl_unmap_segments (l=l@entry=0x55eb13fedb40) at ./dl-unmap-segments.h:32
 _dl_unmap (map=map@entry=0x55eb13fedb40) at ../sysdeps/x86_64/tlsdesc.c:140
 _dl_close_worker (map=map@entry=0x55eb13fedb40, force=force@entry=false) at dl-close.c:678
 _dl_close_worker (force=false, map=0x55eb13fedb40) at dl-close.c:125"
1675153,2017-03-22 20:48:27 UTC,This is relevant for someone implementing this https://stackoverflow.com/questions/11024344/python-name-mangling-function
1675156,2017-03-22 20:16:32 UTC,"StacktraceTop:
 malloc_consolidate (av=av@entry=0x7fe094f2db00 <main_arena>) at malloc.c:4202
 _int_free (av=0x7fe094f2db00 <main_arena>, p=0x55ff322a5f30, have_lock=0) at malloc.c:4110
 __GI___libc_free (mem=mem@entry=0x55ff322b5f50) at malloc.c:2982
 _asn1_remove_node (node=node@entry=0x55ff322b5f50, flags=flags@entry=0) at parser_aux.c:487
 asn1_delete_structure2 (structure=structure@entry=0x7fe078b766e0 <_gnutls_pkix1_asn>, flags=flags@entry=0) at structure.c:328"
1675156,2017-06-26 12:29:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675166,2017-03-23 20:36:36 UTC,"It seems that the ""fix"" of adding log_debug($USER->get('sessionid')); to auth/lip.php only affected the admin account.  When I tried creating other users, they found they had to sign in again after every page.  Not that that was a real fix anyway."
1675174,2017-03-24 08:16:32 UTC,"> If heat-engine OOM'd, is it possible that the stack timeout would not take effect?
"
1675174,2017-03-22 21:20:17 UTC,"If heat-engine OOM'd, is it possible that the stack timeout would not take effect?  I've heard reports that 8 GB underclouds are no longer sufficient in some developer environments, so it's possible we're hitting the same problem in ci now."
1675174,2017-03-23 09:29:42 UTC,Please take a look at my old patch that can save logs in case of timeout: https://review.openstack.org/#/c/410470/
1675174,2017-03-23 13:41:23 UTC,We have logs from job with timeout: http://logs.openstack.org/23/449023/2/check/gate-tripleo-ci-centos-7-nonha-multinode-oooq/25d26eb/
1675174,2017-03-24 08:18:39 UTC,"2017-03-22 16:55:52.355958 | 2017-03-22 16:55:49.839462 [overcloud.ControllerServiceChain.ServiceChain.3.CephBase]: CREATE_IN_PROGRESS  state changed
2017-03-22 16:55:52.409300 | 2017-03-22 16:55:50.186774 [overcloud.ControllerServiceChain.ServiceChain.83]: CREATE_IN_PROGRESS  state changed
2017-03-22 16:55:52.532207 | 2017-03-22 16:55:50.178450 [overcloud.ControllerServiceChain.ServiceChain.44]: CREATE_IN_PROGRESS  Stack CREATE started
2017-03-22 16:55:52.536552 | 2017-03-22 16:55:50.258160 [overcloud.ControllerServiceChain.ServiceChain.3.CephBase]: CREATE_IN_PROGRESS  Stack CREATE started
2017-03-22 18:39:59.020136 | /home/jenkins/workspace/gate-tripleo-ci-centos-7-ovb-updates/devstack-gate/functions.sh: line 1074: 15643 Killed                  timeout -s 9 ${REMAINING_TIME}m bash -c ""source $WORKSPACE/devstack-gate/functions.sh && $cmd""
2017-03-22 18:39:59.020649 |"
1675174,2017-03-24 14:04:21 UTC,I did a quick sanity test to prove the heat timestamp is respected on recent heat master (3d4547f):
1675174,2017-06-13 16:47:06 UTC,"I don't know that we can call this fixed, but we have enough workarounds in ci now that this isn't blocking work from proceeding.  Dropping importance accordingly."
1675174,2019-01-22 13:44:57 UTC,Is this still an issue?
1675189,2017-03-22 21:40:15 UTC,+1
1675189,2017-04-01 18:24:59 UTC,"Hello
We are proud to see that even a 12 years old can help us. Coding is awesome."
1675192,2017-03-30 10:17:07 UTC,A good environment to test this is actually AWS where I noticed this :-)
1675192,2017-03-30 10:16:22 UTC,"Thanks for triaging.  I think you are right, restarts loose the forwarders as well.  At least most the time, I think I saw one instance where it didn't happen but maybe the DHCP lease happened to be renewed at the same time or I just imagined it."
1675192,2017-03-27 19:53:53 UTC,"Hello,"
1675192,2017-03-28 19:06:27 UTC,"Also, I note that in 17.04 (unlike 16.04), there is a unbound-resolvconf.service which has:"
1675192,2017-03-28 21:09:49 UTC,"I must be missing something obvious, as well."
1675196,2017-03-31 14:21:55 UTC,This may be legitimately considered a duplicate of a bug I opened just after the 2015 Hack-A-Way: https://bugs.launchpad.net/evergreen/+bug/1514085
1675196,2019-09-11 19:57:35 UTC,This continues to be an issue in the web client in 3.1
1675196,2021-01-14 00:17:30 UTC,This continues to be an issue in acquisitions in 3.5
1675197,2019-09-09 17:25:44 UTC,"Thanks calexil, closing as fixed."
1675197,2019-09-09 17:11:48 UTC,no longer happening
1675197,2019-09-05 12:08:58 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time.
1675197,2017-03-22 22:15:48 UTC,I just confirmed that the lockup does not replicate with --temp-profile
1675197,2017-03-22 22:08:20 UTC,apport information
1675197,2017-03-22 22:08:19 UTC,apport information
1675197,2017-03-22 22:08:17 UTC,apport information
1675197,2017-03-22 22:08:14 UTC,apport information
1675197,2017-03-22 22:08:12 UTC,apport information
1675197,2017-03-22 22:08:11 UTC,apport information
1675197,2017-03-22 22:08:15 UTC,apport information
1675197,2017-03-22 22:08:09 UTC,apport information
1675197,2017-03-22 22:08:07 UTC,apport information
1675197,2017-03-22 22:07:55 UTC,apport information
1675197,2017-03-22 22:08:06 UTC,apport information
1675197,2017-03-22 22:08:04 UTC,apport information
1675197,2017-03-22 22:08:03 UTC,apport information
1675197,2017-03-22 22:08:01 UTC,apport information
1675197,2017-03-22 22:08:00 UTC,apport information
1675197,2017-03-22 22:07:58 UTC,apport information
1675197,2017-03-22 22:07:57 UTC,apport information
1675197,2017-03-22 22:08:10 UTC,apport information
1675199,2017-03-29 18:21:38 UTC,"Hello,"
1675199,2017-03-28 04:13:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675199,2017-03-28 04:40:58 UTC,"Hello,"
1675201,2017-03-23 03:58:45 UTC,The assert was adjusted for compressed columns
1675201,2018-01-25 09:39:33 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1078
1675202,2019-09-25 04:17:20 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1675202,2019-07-26 09:51:39 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu and Firefox since that time.
1675202,2017-06-30 01:24:35 UTC,"I am also having this issue. I disabled all add-ons, refreshed Firefox (version 54.0, 32 bit), cleared the Netflix cookie, cleared my cached content and offline web content/user data, restarted Firefox, and am still getting the same error."
1675202,2018-01-03 15:19:05 UTC,I am also having the error code on ubuntu 17.04 using FireFox 52.0.1 (32 bit) for ubuntu canonical 1.0
1675202,2017-06-22 15:45:42 UTC,I keep getting error code F7363-1260 when trying to use netflix
1675202,2017-03-28 20:26:14 UTC,It did work. Thank You Alberto :)
1675202,2017-05-12 18:31:23 UTC,"I'm seeing this again as well, on 53.0.2 32-bit and on Firefox Developer
Edition 54.0a2 (2017-04-19) (32-bit)."
1675202,2017-05-12 17:43:46 UTC,Seeing this again on 53.0.2 32 bit.
1675202,2017-03-29 18:14:48 UTC,"I had tried https://help.netflix.com/en/node/57681 first before confirming the bug, but it had not worked."
1675202,2017-03-28 14:19:05 UTC,Please:
1675202,2017-03-23 19:16:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675202,2017-06-18 22:14:16 UTC,I'm seeing this as well on Firefox 54.0.
1675216,2017-11-08 15:43:59 UTC,"So, using pofilter here seems to potentially be a good detection for problems."
1675244,2017-09-29 13:13:44 UTC,"This is not specific to the dashboard, one can see the TTL not being set for the NS+SOA recordsets via the CLI, too. I'm not sure though whether this is intended behaviour or a bug."
1675256,2018-01-25 09:39:32 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1079
1675256,2017-07-13 02:45:48 UTC,Not necessarily - we'd still like to review these patches for 5.5-5.7 merge even given the upstream decision.
1675256,2017-07-12 10:43:08 UTC,"They reported ""Won't fix"" in upstream because they are switching to a new regexp library in upcoming release of MySQL where this bug is not present. Should we change our status to ""Won't fix"" accordingly?"
1675256,2017-06-02 15:24:10 UTC,Suggested fix for 5.6: https://github.com/percona/percona-server/pull/1778
1675256,2017-06-01 16:03:57 UTC,Suggested fix: https://github.com/percona/percona-server/pull/1770
1675256,2017-03-23 09:49:48 UTC,Thank you for the report.
1675256,2017-06-07 14:55:58 UTC,Suggested fix for 5.5: https://github.com/percona/percona-server/pull/1787
1675274,2017-03-23 06:30:59 UTC,"StacktraceTop:
 QLayout::addChildWidget(QWidget*) () from /tmp/apport_sandbox_vEAaRJ/usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QLayout::addWidget(QWidget*) () from /tmp/apport_sandbox_vEAaRJ/usr/lib/x86_64-linux-gnu/libQtGui.so.4
 Tomahawk::Accounts::TelepathyConfigStorage::execConfigDialog(QWidget*) () from /tmp/apport_sandbox_vEAaRJ/usr/lib/x86_64-linux-gnu/libtomahawk_configstorage_telepathy.so
 Tomahawk::Accounts::XmppConfigWidget::launchExternalConfigDialog() () from /tmp/apport_sandbox_vEAaRJ/usr/lib/x86_64-linux-gnu/libtomahawk_account_xmpp.so
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /tmp/apport_sandbox_vEAaRJ/usr/lib/x86_64-linux-gnu/libQtCore.so.4"
1675282,2017-03-23 07:10:03 UTC,"StacktraceTop:
 Tp::Account::protocolName() const () from /tmp/apport_sandbox_hAgHOD/usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
 HistoryDaemon::onTextChannelAvailable (this=0x564f4a1aec80, channel=...) at ./daemon/historydaemon.cpp:656
 HistoryDaemon::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./obj-x86_64-linux-gnu/daemon/history-daemon_automoc.dir/moc_historydaemon_S7H74OZQHD43Q6.cpp:132
 QMetaObject::activate (sender=sender@entry=0x564f4a1aeca8, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcd796e1e0) at kernel/qobject.cpp:3740
 QMetaObject::activate (sender=sender@entry=0x564f4a1aeca8, m=m@entry=0x564f486a4200 <TextChannelObserver::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcd796e1e0) at kernel/qobject.cpp:3602"
1675283,2017-11-03 16:36:56 UTC,Syncing task from Mir.
1675286,2017-04-12 10:54:54 UTC,"Reviewed:  https://review.openstack.org/449286
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=8d7e3e41e8f02726dca33b5ec2f6d5b6b6b07a31
Submitter: Jenkins
Branch:    master"
1675286,2017-10-24 22:56:57 UTC,"Change abandoned by Tony Breeds (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/459828
Reason: This branch (stable/newton) is at End Of Life"
1675286,2017-08-21 09:59:40 UTC,"Reviewed:  https://review.openstack.org/459795
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=6894be453c52083756c6bae0f01dbab53cc3b6e1
Submitter: Jenkins
Branch:    stable/ocata"
1675286,2017-05-05 00:06:16 UTC,"Reviewed:  https://review.openstack.org/451917
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=78abe866dda984921be0ef616c6b9a0b1f8c253e
Submitter: Jenkins
Branch:    master"
1675286,2017-05-04 02:42:57 UTC,"Reviewed:  https://review.openstack.org/449351
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=2ec2d5a973927f9a2cc2a62f70712afc5cb30f4c
Submitter: Jenkins
Branch:    master"
1675286,2017-04-25 18:25:51 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/459828"
1675286,2017-04-25 17:45:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/459795"
1675286,2017-04-10 06:26:13 UTC,"> Except the code currently is in . If it's wrong, write a standalone patch to remove it from scaling_policy.py?
"
1675286,2017-03-24 03:21:09 UTC,This sounds like https://bugs.launchpad.net/heat/+bug/1607814. atomic_key is updated by metadata_update when an action with resource lock is in progress. I thought we decided to implement a separate table for resource metadata to avoid these race scenarios.
1675286,2017-03-24 06:30:22 UTC,"> the db_res could still get updated by the time you actually go to write the resource's metadata...
"
1675286,2017-03-24 06:04:14 UTC,"Tactically speaking, I'm motivated to get fixes in the existing code base without refactoring metadata too much so that [A] can land without the [B] test workaround."
1675286,2017-03-24 04:48:24 UTC,"> I'm not sure moving metadata to another table solves race issues.
"
1675286,2017-03-24 03:50:36 UTC,"I'm not sure moving metadata to another table solves race issues -- potentially we just have to address the race issues in a different place. Either way, I think we need to deal with cases where resource signals and traversing over a resource concurrently attempt to update metadata."
1675286,2017-03-23 23:44:29 UTC,The above addresses the issue:
1675286,2017-03-23 22:59:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449351"
1675286,2017-03-23 22:51:23 UTC,Note the above fix prevents the scenario that was detailed in the bug description:
1675286,2017-03-23 19:06:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449286"
1675286,2017-03-24 15:54:20 UTC,"> That's because we don't set metadata for cooldown/scaling_in_progress in scaling policy. We do that only in ASG.
"
1675287,2018-01-19 16:42:40 UTC,I too have this problem from time to time :-( so it is not just you it IS a bug
1675289,2017-05-02 22:55:45 UTC,"I will add ""selection_method='hash' in add_group method."
1675289,2017-05-03 01:56:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461953"
1675289,2017-05-03 13:32:16 UTC,"Pasting my comment from the review:
From what I just checked, setting selection_method requires OpenFlow1.5.
You can check by manually running ovs-ofctl commands, the selection_method will not appear in a later dump-groups call."
1675289,2017-05-12 11:17:01 UTC,Some additional research
1675289,2017-06-12 13:10:22 UTC,"@chingsun are you still working on this? If not I can take over, as I'd like to see this properly and completely fixed for Pike.
Outline plan in #4 looks like the way to go for this"
1675289,2017-11-04 23:08:25 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/461953
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1675291,2017-03-23 07:41:35 UTC,tanks alat
1675294,2017-06-27 08:06:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675299,2017-03-23 08:18:13 UTC,Fixed
1675300,2017-03-23 08:14:35 UTC,Deployment one
1675300,2017-03-23 08:14:55 UTC,Deployment two
1675300,2017-03-23 08:22:16 UTC,fuel-ccp HEAD is
1675300,2017-03-27 14:27:07 UTC,"It seems this is a consequence of rescheduling
On example:
1. Create server with
openstack --insecure server create --flavor m1.tiny --nic net-id=ed2745e3-61fb-4fe5-a7f4-ae76404d7ff3 --image cirros test5
2. Port list for this server
(openstack) port list --server 329a6205-be97-4e20-a82b-033c143428cf
+--------------------------------------+------+-------------------+---------------------------------------------------------------------------+--------+

| ID                                   | Name | MAC Address       | Fixed IP Addresses                                                        | Status |


+--------------------------------------+------+-------------------+---------------------------------------------------------------------------+--------+

| 5b9c52af-68c5-47f1-8c3d-08694b7a868f |      | fa:16:3e:ff:5f:13 | ip_address='10.50.0.40', subnet_id='5bdb31ff-6924-4dfd-af5e-90356a2e1aa8' | ACTIVE |
| 66186e03-90a2-45ff-8f06-0b7162eaca58 |      | fa:16:3e:19:89:f0 | ip_address='10.50.0.38', subnet_id='5bdb31ff-6924-4dfd-af5e-90356a2e1aa8' | DOWN   |
| ae3256bb-e4d7-40c6-8c1e-c6ea2bf60a82 |      | fa:16:3e:8c:50:b3 | ip_address='10.50.0.37', subnet_id='5bdb31ff-6924-4dfd-af5e-90356a2e1aa8' | DOWN   |
| bdad6ddc-1460-4abb-8f34-e22c5a97acf0 |      | fa:16:3e:3c:dd:1e | ip_address='10.50.0.39', subnet_id='5bdb31ff-6924-4dfd-af5e-90356a2e1aa8' | DOWN   |


+--------------------------------------+------+-------------------+---------------------------------------------------------------------------+--------+"
1675301,2017-03-23 08:19:31 UTC,"I find the following similar problem in stackoverflow:
http://stackoverflow.com/questions/3724900/python-ssl-problem-with-multiprocessing"
1675301,2017-03-23 08:39:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449002"
1675301,2017-03-27 14:32:36 UTC,"Reviewed:  https://review.openstack.org/449002
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=95e22ab2b64ea88770527f70989614058ff6fd4f
Submitter: Jenkins
Branch:    master"
1675303,2017-03-24 03:49:54 UTC,Is dhcpd running in a chroot? Is the AppArmor profile using 'attach_disconnected'? (I'm guessing perhaps these aren't being created in the real root; these two combined could give the appearance of creating files in the root.)
1675303,2017-03-24 19:16:02 UTC,"No chroot.
No attach_disconnected for the usr.sbin.dhcpd profile."
1675328,2017-11-20 02:56:38 UTC,We've just encountered this too. I'm building my own image and am using PostgreSQL 9.6 on Ubuntu Xenial.
1675328,2017-03-23 09:27:26 UTC,"Clearly there has to be some reason why this isn't working for you given that postgres does in fact work (in the gate, for example). Absent any steps to repro this problem, or a description of why it is happening, I'm marking this incomplete for now."
1675328,2017-03-24 07:09:43 UTC,It's not working because there is a function to delete the postgres superuser - https://github.com/openstack/trove/blob/stable/newton/trove/guestagent/datastore/experimental/postgresql/manager.py#L126-L134
1675328,2017-05-24 04:17:27 UTC,[Expired for OpenStack DBaaS (Trove) because there has been no activity for 60 days.]
1675333,2017-03-31 05:36:36 UTC,"why this bug is Invalid?
U can view my upload file and qemu/block/sheepdog.c differences."
1675333,2017-03-31 06:38:06 UTC,"Sorry, but if I read a bug description that says ""already solved"", without any proper description how you ran qemu, which version you were using, etc., then the bug ticket does not make much sense.
So please provide a proper description, and if you've already got a fix, send a patch (diff!) to the qemu-devel mailing list instead of attaching a .c file to the bug tracker. See http://wiki.qemu-project.org/Contribute/SubmitAPatch for details. Thanks."
1675333,2020-11-10 15:01:10 UTC,Have you ever sent a patch to the qemu-devel mailing list?
1675333,2021-01-10 04:17:29 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1675340,2017-11-04 10:38:59 UTC,"This was fixed in debhelper/10.9 (per https://bugs.debian.org/840913), which is available in Bionic."
1675340,2017-11-04 10:47:51 UTC,"Sorry, misread the bug and unfortunately it seems I cannot undo the fact that bug is closed."
1675340,2017-11-04 11:34:56 UTC,reopened.
1675352,2017-03-24 16:33:39 UTC,Or possibly the product name: HP Pavilion x2 Detachable
1675352,2017-03-24 16:32:37 UTC,Translation: The hp x2 sound detectable does not work
1675355,2017-03-27 10:33:36 UTC,Neutron code is missing netns_cleanup script improvements https://review.fuel-infra.org/#/c/18773/.
1675355,2017-03-27 09:46:52 UTC,"Fix proposed to branch: 10.0/newton
Change author: Sergey Belous <email address hidden>
Review: https://review.fuel-infra.org/32539"
1675357,2017-06-07 07:51:12 UTC,"Hello Michał, or anyone else affected,"
1675357,2017-06-15 14:25:31 UTC,This bug was fixed in the package mir - 0.26.3+17.04.20170605-0ubuntu1
1675357,2017-06-15 14:16:33 UTC,This bug was fixed in the package mir - 0.26.3+16.04.20170605-0ubuntu1
1675357,2017-06-15 14:16:11 UTC,This bug was fixed in the package mir - 0.26.3+16.10.20170605-0ubuntu1
1675357,2017-06-15 14:15:26 UTC,"The verification of the Stable Release Update for mir has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1675357,2017-06-07 15:44:56 UTC,"Tested:
xenial: 0.26.3+16.04.20170605-0ubuntu1
yakkety: 0.26.3+16.10.20170605-0ubuntu1
zesty: 0.26.3+17.04.20170605-0ubuntu1"
1675357,2017-06-07 09:47:07 UTC,"Hello Michał, or anyone else affected,"
1675357,2017-06-07 07:48:44 UTC,"Hello Michał, or anyone else affected,"
1675357,2017-03-23 11:12:13 UTC,This is a `perf report` from just 3-4s around reactivating a unity8 vt:
1675357,2017-05-18 09:04:39 UTC,Tested version 0.26.3+16.04.20170510-0ubuntu1
1675357,2017-03-23 12:39:49 UTC,"Turning on input event printing[1], when using Ctrl+Alt+F1 switching away from unity8, I see a continuous stream of input events being sent from Mir to Unity8, while on VT1:"
1675357,2017-03-23 15:47:06 UTC,Was suspecting this is bug 1536279 but they don't quite match either
1675357,2017-03-24 01:51:38 UTC,AFAIK the same Mir Input Reader thread is causing high CPU bug 1671731 also. Might be related.
1675357,2017-05-28 13:18:03 UTC,This bug was fixed in the package mir - 0.26.3+17.10.20170526.3-0ubuntu1
1675357,2017-03-27 07:27:05 UTC,"Fix committed to lp:mir/0.26 at revision 4050, scheduled for release in Mir 0.26.3 (if that gets released at all)"
1675357,2017-03-27 12:41:30 UTC,This should not be set to Fix Committed on system images until it's available on System Images.
1675357,2017-05-17 10:43:37 UTC,"Hello Michał, or anyone else affected,"
1675357,2017-03-27 07:06:23 UTC,"Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 1.0.0"
1675360,2017-03-23 12:25:27 UTC,Logs Snapshot
1675360,2017-03-23 12:33:09 UTC,"Not sure it is  reason of failure, but in neutron log from controller i can see errors of neutron-openvswitch-agent:
http://paste.openstack.org/show/603903/"
1675368,2017-03-23 11:54:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449098"
1675368,2019-12-03 18:54:48 UTC,"Change abandoned by Zane Bitter (<email address hidden>) on branch: master
Review: https://review.opendev.org/449098"
1675371,2017-03-23 11:37:19 UTC,"Print screen from 2 target machines, one with time correct is from local domain the second with incorrect time is from a remote domain"
1675371,2017-03-23 11:37:48 UTC,second prinscreen
1675372,2017-03-24 15:45:35 UTC,"Kyrylo, please provide more information why it failed and what MOS Packaging team can do to fix it."
1675372,2017-03-27 11:00:47 UTC,Next builds passed successfully.
1675386,2018-11-13 18:49:07 UTC,Thank you for taking the time to verify this stable release fix.  We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE).  Please remove the verification-done tag and add one for the release you have tested the package in.  Thank you!
1675386,2018-11-20 17:23:45 UTC,The verification of the Stable Release Update for nova-lxd has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1675386,2018-11-20 16:35:43 UTC,"The verification of the Stable Release Update for nova-lxd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1675386,2018-11-20 16:35:38 UTC,This bug was fixed in the package nova-lxd - 13.3.0-0ubuntu2
1675386,2018-11-14 10:16:06 UTC,Thanks Brian for the help with this; apologies for getting the tags wrong!  I'll fix them now.
1675386,2018-11-13 16:11:51 UTC,I've confirmed that this function with mitaka/xenial using the amulet test associated with lxd.
1675386,2018-11-20 17:23:46 UTC,"This bug was fixed in the package nova-lxd - 13.3.0-0ubuntu2~cloud0
---------------"
1675386,2018-06-01 19:27:42 UTC,"Hello todd, or anyone else affected,"
1675386,2018-05-31 23:10:42 UTC,"Hello todd, or anyone else affected,"
1675386,2018-05-31 16:57:42 UTC,Thanks Alex. I've uploaded the new version of the package to the xenial unapproved queue [1] where it is awaiting review by the SRU team.
1675386,2018-05-31 16:39:26 UTC,Updated stable/mitaka patch which includes changelog update.
1675386,2018-05-31 14:23:31 UTC,stable/mitaka patch as a diff file that fixes the bug.
1675386,2018-05-30 16:28:47 UTC,"Newton is now eol; however, it still needs a fix for mitaka."
1675386,2017-10-20 10:59:22 UTC,"@todd  we'll get this fixed for mitaka and newton releases, however I would recommend using newer openstack releases for nova-lxd based deployments; they incorporate numerous improvements and new features such as the ability to be able to present ceph based cinder volumes to lxd containers @ pike."
1675386,2018-10-03 19:56:06 UTC,"Alex, would you be able to verify this bug is fixed? Thanks."
1675386,2017-10-20 10:57:48 UTC,This bug impacts mitaka and newton branches only; the code was refactored @ ocata and now does the right thing with regards to building the entire dict of network data.
1675387,2018-12-16 20:43:19 UTC,"Change abandoned by Xav Paice (<email address hidden>) on branch: master
Review: https://review.openstack.org/459234
Reason: this action increases the total workload on the cluster which is the opposite of the intent."
1675387,2017-03-24 23:01:22 UTC,Yeah I agree with point 2.  The juju action yaml file is expressive enough that we could lock down what is/isn't allowed to be passed to the command.
1675387,2017-03-24 19:08:32 UTC,"So, the reason I think an action is better than juju run:"
1675387,2017-03-23 15:11:20 UTC,I've been trying to avoid creating actions on the ceph-mon charm that are a 1:1 mapping to the underlying ceph command.  Any of the commands you mentioned could easily be run with a juju run command without having the additional overhead of the juju run-action interface.  Anything that requires multiple steps is a great candidate for an action.
1675387,2017-04-27 01:47:54 UTC,Note https://review.openstack.org/#/c/459234/ and https://review.openstack.org/#/c/460000/ partially implement this.
1675394,2017-03-23 12:42:32 UTC,"The issue appears for OSC version 3.8.1 in Ubuntu Ocata UCA, after pip-installing OSC 3.9.0 I get the correct error message:"
1675394,2017-04-28 21:33:57 UTC,"Is this still a problem?  Also, knowing which version of openstacksdk is installed may be helpful as all of the network commands use it rather than neutronclient."
1675394,2017-04-28 21:35:34 UTC,"So ignore that bit about the SDK, I found it in the debug output, 0.9.13, and I see the same result with that version."
1675394,2017-06-19 08:28:10 UTC,So will there be a patch for the stable/ocata branch that fixes this issue? Or would you expect distros to update to a newer release?
1675394,2017-06-22 09:37:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675397,2017-04-25 15:15:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1675410,2017-03-23 17:33:55 UTC,From what was discussed I like to see the following information on the host-list command:
1675410,2017-03-23 17:01:44 UTC,"For what it's worth, feel free to liberally steal from: https://gitlab.com/pycqa/flake8/blob/733a4f053b093d0d061ce780963e936861327c95/src/flake8/utils.py#L15"
1675410,2017-03-23 17:00:12 UTC,"Don't we already support the --fields argument? For example, http://git.openstack.org/cgit/openstack/python-cratonclient/tree/cratonclient/shell/v1/hosts_shell.py#n81"
1675410,2017-03-30 18:03:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/451932"
1675410,2017-03-24 19:48:14 UTC,"Bjoern, thanks for the feedback. We're talking through some implications of what's suggested here."
1675410,2017-03-27 20:52:29 UTC,Things discussed in IRC:
1675413,2020-01-15 21:42:54 UTC,"Hi,"
1675415,2017-03-23 13:34:53 UTC,logs
1675422,2017-03-23 15:05:31 UTC,sla2 for 9.0-updates
1675422,2017-03-24 13:22:32 UTC,The fix is present in the sync from stable/newton: https://review.fuel-infra.org/#/c/28324/
1675422,2017-04-06 08:40:34 UTC,"Reviewed: https://review.fuel-infra.org/32520
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1675422,2017-06-14 11:45:52 UTC,"Can't reproduce this bug on our side. In accordance to our policy, I will move bug to ""Fix released"". Please check the fix on customer side."
1675422,2017-08-30 16:48:03 UTC,"Fix proposed to branch: mcp/1.0/mitaka
Change author: Esha Seth <email address hidden>
Review: https://review.fuel-infra.org/36360"
1675422,2017-08-30 18:37:13 UTC,"Change abandoned by Vladyslav Drok <email address hidden> on branch: mcp/1.0/mitaka
Review: https://review.fuel-infra.org/36360"
1675422,2017-08-31 17:37:44 UTC,"Change restored by Vladyslav Drok <email address hidden> on branch: mcp/1.0/mitaka
Review: https://review.fuel-infra.org/36360"
1675422,2017-09-01 08:13:25 UTC,"Reviewed: https://review.fuel-infra.org/36360
Submitter: Pkgs Jenkins <email address hidden>
Branch: mcp/1.0/mitaka"
1675422,2017-03-24 16:30:26 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Esha Seth <email address hidden>
Review: https://review.fuel-infra.org/32520"
1675438,2017-03-23 20:32:36 UTC,Thank you for reporting the bug.Unfortunately the video is not that self explanatory because I cannot see when you click and when the lag happens.
1675438,2017-03-25 18:20:10 UTC,I have noticed this too. I presume it has something to do with how X and/or Qt handle OpenGL widgets that are off screen.
1675438,2017-03-24 00:39:30 UTC,I click all the time only one button Play. Look at the waveform when the window moved aside. It looks and feels like mixxx FPS drastically fall down. But mouse cursor speed is o.k.
1675440,2017-05-30 04:17:29 UTC,[Expired for juju because there has been no activity for 60 days.]
1675440,2017-03-29 02:19:53 UTC,"From the attached log, LXD version is 2.0.9"
1675440,2017-03-29 06:15:00 UTC,Can you give the steps that were necessary to reproduce this?
1675440,2017-03-29 06:17:05 UTC,"I feel like we should have CI test cases around this, so if we are missing the functionality, then we do have an issue. The question is why we wouldn't have caught this internally if it really is a problem. If it isn't, then clearly we made it possible to misconfigure things."
1675441,2017-03-23 15:23:24 UTC,"I don't think it should be unity8 itself, more like a recommendation of unity8-desktop-session."
1675451,2017-03-24 08:25:50 UTC,According to the strace the packstack was stuck on wait_for_puppet. The issue has gone after resetting CONFIG_NEUTRON_OVS_TUNNEL_SUBNETS to empty value.
1675451,2017-03-24 11:42:22 UTC,"I have run a local test and could not reproduce the issue, even setting CONFIG_NEUTRON_OVS_TUNNEL_SUBNETS with a subnet value."
1675451,2017-03-24 17:35:45 UTC,"> Could you try to reproduce the issue (using packstack --debug answer-file.txt), and then upload the
> log files from /var/tmp/packstack/<uuid>/manifests/ somewhere?
"
1675451,2017-12-26 18:13:51 UTC,"Hi,"
1675451,2018-06-20 11:31:57 UTC,"hi, have you been able to solve the problem??? If so, please let us know..."
1675451,2018-07-02 07:31:00 UTC,"i have this problem too.. it's solved by checking the /etc/hosts file. make sure ur IP address is there and set the packstack file CONFIG_KEYSTONE_ADMIN_PW=<fill ur password>
also make sure u have good internet connection. because it depends on your internet connection too."
1675453,2018-01-26 23:27:50 UTC,This bug was fixed in the package grub2 - 2.02-2ubuntu4
1675453,2018-01-26 23:27:49 UTC,This bug was fixed in the package grub2-signed - 1.89
1675453,2018-01-22 12:23:18 UTC,"I agree that's something worth considering, but I'd say it's a separate story. The vt.handoff patches are not only needed for the d-i netboot install of server case, but in overall for the splash boot experience being smooth. Without vt.handoff all desktops will regress in how the splash screen looks like, with a black screen flashing before plymouth starts, text messages (even with quiet) appearing on screen."
1675453,2018-01-20 07:56:01 UTC,"On Thu, Jan 18, 2018 at 04:56:33PM -0000, Łukasz Zemczak wrote:

> Ok, so it seems a few of my previous tests were a bit flawed. It looks
> like vt.handoff=1 does the trick completely for this particular bug. So
> once we switch grub2 to vt.handoff=1 this bug here will be fixed.
> Another thing that needs to be still considered is somehow tweaking
> netboot installs to have 'splash quiet' removed - but that's a separate
> story.
"
1675453,2018-01-18 16:56:33 UTC,"Ok, so it seems a few of my previous tests were a bit flawed. It looks like vt.handoff=1 does the trick completely for this particular bug. So once we switch grub2 to vt.handoff=1 this bug here will be fixed. Another thing that needs to be still considered is somehow tweaking netboot installs to have 'splash quiet' removed - but that's a separate story."
1675453,2018-01-15 19:38:59 UTC,I'm learning all those bits slowly piece by piece here...
1675453,2017-11-17 09:51:14 UTC,"I see that by default our ubuntu-server images boot without ""quiet splash"", maybe this is what we'd prefer in case of the mini.iso ubuntu-server image as well?"
1675453,2018-01-12 20:18:52 UTC,What I'll do is remove the vt.handoff patch from grub2 and switch plymouth to use vt1 as well (if xnox doesn't beat me to the latter).
1675453,2017-11-20 23:51:20 UTC,"On Fri, Nov 17, 2017 at 09:20:09AM -0000, Łukasz Zemczak wrote:

> The reason for this happening is that apparently this ubuntu-server
> image is booting with vt.handoff=7 while in systemd's logind we're only
> using the default number of configured tty's (i.e. 6). So plymouth is
> running, doing it's thing and then switches to tty7 which is not
> enabled. This can be confirmed by either increasing logind's number of
> tty's or by enforcing vt.handoff=1.
"
1675453,2017-11-17 09:20:09 UTC,"The reason for this happening is that apparently this ubuntu-server image is booting with vt.handoff=7 while in systemd's logind we're only using the default number of configured tty's (i.e. 6). So plymouth is running, doing it's thing and then switches to tty7 which is not enabled. This can be confirmed by either increasing logind's number of tty's or by enforcing vt.handoff=1."
1675453,2017-03-29 16:39:14 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1675453,2017-03-23 15:49:40 UTC,Look like mini.iso/netboot will use plymouth in text mode where the server.iso does not.  So I think that plymouth is not being taken down and therefore utilising tty1 which is why we see no login adding plymouth to the bug.
1675453,2018-01-15 18:16:53 UTC,"So plymouth is by default using tty1 already, but there seem to be some other problems here. Looks like with the 'quiet splash' option, when plymouth is running there still seems to be some output printed out to the screen on top of the splash-screen (from the looks of it it's systemd output + a few single kernel messages on the kvm). This looks terrible. The old FRAMEBUFFER=y initramfs trick works partially, but the few single kernel messages are still being printed. By 'quiet' I would expect completely silent boot. When running with just 'quiet' without plymouth, I actually only see the kernel messages (which is still something I wouldn't expect seeing)."
1675453,2017-04-12 19:30:14 UTC,"In a fresh install, it hangs for five minutes, while it waits for the network interfaces to go up. After login prompt, if you try to restart networking, it complains about policykit-1 not found. Does this happen to you? If so, it is related to bug #1682201"
1675455,2017-09-02 02:40:04 UTC,"Not a proper fix, but it's possible to work around this by setting the file name to a relative file path, eg ""../screencapture/kazam_capture"" will create a file in the folder ""../screencapture/screencapture"" with the prefix ""kazam_capture"". This crashes if the folder does not exist, however."
1675458,2020-11-10 15:15:20 UTC,Looking through old bug tickets ... Have you tried to discuss this issue with the libvirt people? They might need to have a look at your virsh commands first before one could decide whether this is a libvirt or a qemu problem...
1675458,2021-01-10 04:17:31 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1675459,2020-07-02 20:47:59 UTC,"I am hitting this, too. I see this has been open since 2017 with no response."
1675477,2017-03-23 16:28:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1675477,2019-10-04 12:30:07 UTC,"Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1675477,2019-12-04 04:17:29 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1675479,2017-04-06 13:58:36 UTC,"I don't see that error, but I had to make modifications to your snapcraft.yaml -> http://paste.ubuntu.com/24327782/"
1675479,2017-04-07 14:46:14 UTC,"Hey Sergio, so something must be different in our environments but I'm not sure what."
1675479,2017-04-07 19:56:57 UTC,As a work around I've added the following to the keystone section:
1675480,2017-03-23 16:42:29 UTC,May want to borrow some bits of what RHEL does for their packaging: https://raw.githubusercontent.com/lukehinds/bagpipe-bgp-packaging/master/bagpipe-bgp.spec
1675481,2017-03-24 03:36:25 UTC,"I'm not familiar with the -fd option myself, but confirm it can be made to crash:"
1675481,2017-03-24 09:38:02 UTC,I was wrong. What I was reproducing is a different crash with large FDs not specific to Xmir.
1675481,2017-03-24 19:39:09 UTC,The following diff seems to fix the crash: http://pastebin.ubuntu.com/24242549/
1675481,2017-03-27 03:41:48 UTC,Your diff appears to be what I was suggesting in comment #2.
1675481,2017-03-27 07:41:34 UTC,"... and if moving the block is insufficient and the timer is your only option, I pre-approve of that landing too. Makes sense either of those should fix it."
1675481,2017-04-04 02:28:13 UTC,https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=e8435ece23017fb4153487f6157eb11cac985697
1675482,2018-03-11 13:51:53 UTC,"root@unassigned:/etc/neutron# cat /usr/etc/neutron/networking_bgpvpn.conf
[service_providers]
# both cannot be default, please choose:
service_provider=BGPVPN:Dummy:networking_bgpvpn.neutron.services.service_drivers.driver_api.BGPVPNDriver:default
#service_provider=BGPVPN:BaGPipe:networking_bgpvpn.neutron.services.service_drivers.bagpipe.bagpipe.BaGPipeBGPVPNDriver:default"
1675482,2018-03-11 13:51:43 UTC,This is still an issue
1675485,2017-03-28 12:35:28 UTC,"I think we could just try the URL as is. Ideally we wouldn't introspect the URL too much. (so try URL, URL+/api/2.0 and URL+/api/1.0)."
1675485,2017-04-03 11:56:02 UTC,Gomaasapi PR: https://github.com/juju/gomaasapi/pull/65
1675485,2017-04-03 23:39:27 UTC,gomaasapi PR: https://github.com/juju/gomaasapi/pull/65
1675485,2017-04-04 22:16:41 UTC,juju PR: https://github.com/juju/juju/pull/7201
1675485,2017-03-23 21:27:36 UTC,"Yes, this is right. The current gomaasapi will automatically attempt the known API versions, starting with the most recent it understands, which is 2.0."
1675486,2017-03-24 12:18:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449598"
1675486,2017-08-01 09:58:33 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/449598
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1675486,2017-08-01 10:17:44 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1675486,2021-02-17 03:39:07 UTC,"One idea for addressing this is to remove the 'network:attach_external_network' policy check entirely and let neutron reject the request to create the port. This way, if an operator enables a tenant to attach to an external network, it will Just Work without the operator needing to push a policy config update to all nova-compute services."
1675494,2020-08-25 05:56:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675496,2018-04-18 14:28:49 UTC,"Most probably the Firefox snap package is built with the GTK3 version (3.18.9) found in Xenial, regardless where the snap is run, because also the deb package of Firefox in Xenial has normal scrollbars. So I think the problem is with the GTK3 version newer than 3.18.9."
1675496,2018-05-05 18:15:13 UTC,still an issue with Ubuntu 18.04/FF 59.2
1675496,2018-04-18 16:41:50 UTC,"I am seeing the same scrollbars in other apps but not all other apps.
I get the same small scrollbars in Firefox, Thunderbird, LibreOffice, and Evince, as a few examples. There are others."
1675496,2018-04-18 10:08:42 UTC,"The snap package works fine. Both, current ubuntu 17.10 and snap,  are the same ff version: 59.0.2 !!!"
1675496,2017-04-23 08:21:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675496,2018-02-27 17:10:12 UTC,The described issue with the scrollbar size still exists on Bionic (and all newer Firefox versions).
1675496,2018-02-27 15:15:46 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1675496,2017-03-26 13:51:12 UTC,"@madbiologist
Yes, this would be an acceptable solution, but on my system (Yakkety) the scrollbars in Firefox always stay slim and never broaden, regardless if I move the mouse over the slider or some other place on the scrollbar. Is this different on your installation?"
1675496,2018-04-12 09:28:49 UTC,The Snap package of Firefox 59 has wider scrollbars for me on Ubuntu 17.10. Might be worth checking out if you struggle to interact with the narrow scrollbars.
1675496,2017-03-24 15:35:03 UTC,"In Gedit the scrollbars broaden automatically when you move the mouse over any part of them.  In Firefox they only broaden if you move the mouse over the slider.  Inconsistency is not good, but this is probably an acceptable solution.  What do you think?"
1675501,2017-03-29 09:41:43 UTC,"webbrowser-app uses a standard TextField component with no specific handling of the context menu, so that would be a bug in the UITK.
I am not seeing that issue, however I am seeing one that might be related: in my testing, the paste option in the context menu is always greyed out, regardless of the contents of the clipboard. Pasting with the Ctrl+V keyboard shortcut works, but cannot be done from the context menu."
1675501,2017-03-29 09:47:49 UTC,I filed bug #1677181 to track the issue I’m describing above.
1675513,2017-04-03 08:10:41 UTC,"I was away last week, but I'm happy to find that the builds are now working."
1675513,2017-03-28 12:42:38 UTC,"IS provided a fix to speed up DNS lookups and the build now completes in around 16 mins (vs original 7 mins)
https://code.launchpad.net/~ubuntu-sdk-team/+snap/ubuntu-app-platform/+build/30005"
1675513,2017-03-28 12:10:48 UTC,"Pat you are indeed correct, this indeed creates a new connection per package to download https://github.com/snapcore/snapcraft/blob/master/snapcraft/internal/repo/_deb.py#L303"
1675513,2017-03-28 04:41:20 UTC,"I disabled my apt-cacher-ng and configured my sources to use the archive from the UK.
I built Pat's snap locally without the code to handle the stage packages cache, and it took 10 minutes. Then I got the caching code, and it took 20 minutes. My connection is not really stable, so the measurements are not very useful, but taking twice the time is too much. I've marked this bug as confirmed."
1675513,2017-03-28 03:22:46 UTC,"Thanks wgrant, that's good to hear. While this is of course still an issue, Pat can you verify that your builds are succeeding once again?"
1675513,2017-03-28 01:48:56 UTC,"The majority of the slowdown was a combination of snapcraft's lack of connection preservation and slow DNS resolution of the builder proxy due to a possible BIND bug. IS has applied a workaround for the BIND problem, fixing much of the latency and most of the build slowdown."
1675513,2017-03-24 07:20:58 UTC,This was probably a temporary network problem. Is it still reproducible?
1675513,2017-03-27 14:23:27 UTC,"This seems related to the change at
https://github.com/snapcore/snapcraft/commit/20b422459119000640fa4103fe097eca5440f920"
1675513,2017-03-26 00:27:37 UTC,"No, this isn't a code bug."
1675513,2017-03-24 11:52:47 UTC,(it seems the status is reflected in the question so better to keep the bug open)
1675513,2017-03-24 07:44:08 UTC,Continuing in the question instead.
1675513,2017-03-24 07:42:22 UTC,It has happened since February and continues to happen.
1675513,2017-03-27 14:47:56 UTC,specifically https://github.com/snapcore/snapcraft/commit/20b422459119000640fa4103fe097eca5440f920#diff-e8d25d56f5ed513cad7c55002a709f32R316
1675513,2017-03-24 05:52:13 UTC,"The last successful build of ubuntu-app-platform was on 2017-02-08, and started failing with the 2 hour timeout by ~2017-02-20."
1675523,2017-08-02 20:49:25 UTC,Automatically unassigning due to inactivity.
1675525,2017-03-23 18:40:12 UTC,Use http://releases.ubuntu.com/16.04.2/ubuntu-16.04.2-desktop-amd64.iso to test on a 16G USB Drive.
1675525,2017-03-23 18:43:23 UTC,"Well, that didn't take long.  I got the same issue immediately on a different brand USB drive.  Will deep dive into it to see what the issue is."
1675526,2017-03-23 23:24:05 UTC,"Reviewed:  https://review.openstack.org/449211
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=79fd13f0000498d4cf415f7e60e40037689b7276
Submitter: Jenkins
Branch:    master"
1675526,2017-03-23 22:02:40 UTC,https://review.openstack.org/#/c/449211/ was updated to skip the trigger crash dump tests until we can sort out what's causing the timeout.
1675526,2019-09-10 02:06:13 UTC,"This bug has been open about 2 and a half years without any activity.
So I'm going to move it to ""Opinion / Wishlist"", which is an easily-obtainable queue of older requests that have come on.
This bug can be reopened (set back to ""New"") if someone decides to work on this."
1675528,2017-04-28 16:17:25 UTC,Confirmed this was previously fixed. Closing as not a bug.
1675528,2017-04-28 16:18:36 UTC,"Argh, please ignore previous comment, I was in the wrong bug report, sorry."
1675528,2017-08-02 20:49:32 UTC,Automatically unassigning due to inactivity.
1675539,2019-05-30 01:28:20 UTC,"Hi, would you like to submit this as a merge request on GitLab? It'll be quicker and easier for us to merge in. Here's the repo: https://gitlab.com/inkscape/inkscape"
1675562,2017-05-03 20:43:30 UTC,"For some reason, the last month it was executed only two Fridays with one week apart."
1675571,2017-03-28 15:07:36 UTC,I've withdrawn my PR for the DigitalOcean specific fix after an offline conversation.
1675571,2017-03-27 21:40:14 UTC,"So while my patch for the DigitalOcean datasource fixes this usecase, the rendering of additional addresses actually breaks all the ""if*"" tools for secondary addresses and even IPv6. Consider:"
1675571,2017-03-27 17:56:03 UTC,"I would like to nominate this bug for the Xenial, Yakkety and Zesty branches as well."
1675571,2017-03-27 21:42:07 UTC,"Additionally, ""ifconfig"" no longer shows secondary addresses. Notice that `10.17.0.6/16` in #7 above is not defined:"
1675571,2017-03-25 04:11:03 UTC,"Patch submitted to Cloud-init via:
https://code.launchpad.net/~utlemming/cloud-init/+git/cloud-init-1/+merge/321001"
1675571,2017-03-24 17:29:33 UTC,"Changing the cloud-metadata won't work in this case, since the the code for the DigitalOcean metadata source is assigning the Nameservers to the primary interface. Also, adding the DNS resolvers to the loopback interfaces doesn't work because the loopback interface is already up before the definition is added."
1675571,2017-03-23 21:54:32 UTC,The network config in the previous bug used DHCP on v4 and v6; it appears this instance has a different network config injected.  Can you attach the network configuration?
1675571,2017-03-26 04:02:22 UTC,The patch in comment #4 moves the revolvers to the loopback interface; resolve conf picks it up.
1675571,2017-03-23 22:27:18 UTC,"The following is the network_config:
'_network_config': {'config': [{'mac_address': 'ca:22:2d:f4:1a:5e',
                                 'name': 'eth0',
                                 'subnets': [{'address': '138.197.98.102',
                                              'control': 'auto',
                                              'dns_nameservers': ['8.8.8.8',
                                                                  '8.8.4.4'],
                                              'gateway': '138.197.96.1',
                                              'netmask': '255.255.240.0',
                                              'type': 'static'},
                                             {'address': '10.17.0.11',
                                              'control': 'auto',
                                              'netmask': '255.255.0.0',
                                              'type': 'static'}],
                                 'type': 'physical'}],
                     'version': 1},"
1675577,2017-09-18 17:44:16 UTC,fixed in boot-repair-4ppa42
1675577,2017-09-30 23:54:12 UTC,Appears it wasn't completely fixed in 4ppa42. Should be solved in 4ppa51.
1675594,2017-03-28 13:23:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675602,2017-03-24 02:08:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449397"
1675602,2017-03-30 03:21:24 UTC,"Reviewed:  https://review.openstack.org/449397
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9910bade6fe7ffde1b11170f894e2876ed8ccdb4
Submitter: Jenkins
Branch:    master"
1675602,2017-03-30 05:11:55 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/451649"
1675602,2017-04-13 22:53:38 UTC,"Reviewed:  https://review.openstack.org/451649
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e1ba6153ba066169f66d2c339b2b6e333e1b2122
Submitter: Jenkins
Branch:    stable/ocata"
1675602,2017-04-14 09:22:29 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1675602,2017-05-08 22:10:25 UTC,This issue was fixed in the openstack/nova 15.0.4 release.
1675602,2017-07-13 11:20:11 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/483304"
1675602,2017-10-17 18:39:45 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/483304
Reason: Agree with Tony, don't think we need to get this in for newton, which is EOL tomorrow."
1675603,2017-03-24 01:41:14 UTC,To reproduce:
1675604,2017-03-24 12:44:44 UTC,Feel free to patch via pull request at https://github.com/libLAS/libLAS/
1675604,2017-04-10 22:11:26 UTC,https://github.com/libLAS/libLAS/pull/120
1675610,2020-08-03 22:10:55 UTC,This happened again over the weekend.
1675624,2017-08-23 13:32:13 UTC,Default Comment by Bridge
1675624,2017-03-27 14:08:03 UTC,This fix has already been applied as part of upstream stable release 4.10.4. It is included in the 4.10.0-15.17 kernel for zesty which is currently in the canonical-kernel-team PPA.
1675624,2017-03-24 04:10:30 UTC,Default Comment by Bridge
1675624,2017-03-24 04:10:27 UTC,Default Comment by Bridge
1675624,2017-03-24 15:27:27 UTC,"Leann,"
1675626,2017-03-24 15:35:12 UTC,"Rudra,"
1675626,2017-03-24 19:07:36 UTC,Update From Harish
1675635,2017-03-29 07:09:02 UTC,"If I want to run two cloudkitty-processor daemons in one same node, when the second daemon starting , it reports below information:"
1675635,2017-03-29 09:29:11 UTC,"In the same node, I set the coordination_url=file:///var/lib/cloudkitty/locks in orchestrator configure section and run two cloudkitty-processor daemons, the total rating is correct and the cloudkitty-process daemons have the high availability characteristic."
1675635,2017-04-19 08:28:49 UTC,"Hi Guoqing,"
1675635,2018-06-12 05:59:14 UTC,"Hi,"
1675659,2017-03-24 20:25:10 UTC,The error seems correct to me. If you had
1675659,2017-03-24 21:49:25 UTC,"Well, I don't agree with your argument, but if that's instead valid, then I would
expect that a very similar case, that is"
1675659,2017-03-24 23:31:19 UTC,"I think pyflakes automatically assumes functions and module level variables are ""used"" because they could just be defined to be importable from other modules."
1675659,2017-03-29 02:15:10 UTC,Report seems legit to me. In the example:
1675666,2017-03-24 13:16:07 UTC,This is supposed behavior https://github.com/openstack/fuel-library/blob/master/deployment/puppet/openstack_tasks/manifests/glance/glance.pp#L86
1675670,2019-10-29 01:09:37 UTC,hi jgrosso   there isn't any update on this.
1675670,2019-10-28 17:57:06 UTC,hey Zhongjun any updates on this? Where you able to improve performance on a new version of manila
1675670,2018-06-10 02:34:03 UTC,"Change abandoned by Tom Barron (<email address hidden>) on branch: master
Review: https://review.openstack.org/458771
Reason: No activity since September last year; feel free to restore, rebase, etc."
1675670,2018-08-16 02:20:44 UTC,"Change abandoned by zhongjun (<email address hidden>) on branch: master
Review: https://review.openstack.org/458771
Reason: Actually, this fix isn't high priority to pursue.
Because this does not affect the function. This is just improving performance. If your don't have a lot of shares, it cloud not improve mach performance.  And this patch based on very old version cold. I will just abandon it first."
1675674,2017-03-24 08:30:59 UTC,This change was made by a bot.
1675674,2017-03-27 20:34:21 UTC,You may need to run the following from a terminal:
1675674,2017-03-28 08:10:14 UTC,I have the exact same problem (Ubuntu Gnome 16.10). The sudo apt-get install -f did not resolve it in my case. The process freezes just like in the description from the original reporter.
1675674,2017-03-28 10:01:27 UTC,I can confirm the same problem.
1675674,2017-03-28 14:58:11 UTC,I let the hung process sit for some hours (2-4) and when I came back I found the following logged to the console:
1675674,2017-03-31 07:57:26 UTC,Sorry to answer so late.
1675674,2021-01-07 04:02:36 UTC,4.8 EOL
1675679,2017-04-11 08:02:01 UTC,"To give further details, this only happens on vanilla 4.10 kernel.
A 4.10 kernel with apparmor 3.6 backport doesn't not have this issue."
1675679,2017-10-02 20:40:34 UTC,"Does this still happen with the latest vanilla kernel? (Lots of patches were upstreamed, including some fixes for reloading profiles.)"
1675684,2017-03-24 09:12:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449511"
1675684,2017-03-27 15:30:37 UTC,"Reviewed:  https://review.openstack.org/449511
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=b5a316b5d629e36761afb8745a00396b7a4bd0e1
Submitter: Jenkins
Branch:    master"
1675685,2017-03-25 10:01:40 UTC,"I agree that this is an unfortunate situation.  I did as much as I realistically could to mitigate it in versions 0.4.41+16.04.20151211-0ubuntu1 and 0.4.43+16.04.20160203-0ubuntu1.  click is end-of-life, is now lacking a regular maintainer, is due to be replaced by snapd/snapcraft/etc., and will be removed once the migration has been complete; so the (non-trivial) effort to rename it wouldn't pay off."
1675692,2017-03-27 01:48:06 UTC,"Because:
  (1) My desktop does not have a touch screen and dragging with a mouse should(?) exhibit the same issues that touch users will experience when dragging with a finger; and
  (2) Mouse wheel scrolling is very poor right right: bug 1556795"
1675692,2017-03-27 04:00:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675692,2017-03-24 09:56:36 UTC,"Why are you dragging the drawer with mouse? You can invoke it with pressing against the left edge, dismiss it with clicking outside it or on any item inside, or Esc. Scroll with scroll wheel."
1675692,2017-03-27 01:48:28 UTC,"*""very poor right now"""
1675696,2017-03-24 09:25:13 UTC,"We could increase the titlebar height, but I have a hunch that just fixing bug 1583092 would also make the appearance adequate."
1675696,2017-03-27 03:23:44 UTC,I think a good rule of thumb is to ensure for any text label/area the text height is only 50% of the area's height.
1675705,2018-02-20 14:15:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675718,2019-12-18 17:17:33 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/455674
Reason: This repo is retired now, no further work will get merged."
1675718,2017-04-06 12:51:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454166"
1675718,2017-04-06 12:55:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454168"
1675718,2017-04-11 11:58:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/455674"
1675718,2017-04-11 12:42:35 UTC,"Change abandoned by Michael Polenchuk (<email address hidden>) on branch: master
Review: https://review.openstack.org/454166
Reason: because of https://review.openstack.org/455674"
1675718,2019-12-18 17:20:56 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/454168
Reason: This repo is retired now, no further work will get merged."
1675727,2017-04-07 09:48:53 UTC,"Verified on on 10.0 #1575.
Problem is gone:
https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.plugins.fuel_plugin_example/234/"
1675727,2019-12-18 17:39:06 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/451324
Reason: This repo is retired now, no further work will get merged."
1675727,2017-03-29 17:34:55 UTC,"Reviewed:  https://review.openstack.org/451323
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=ae0e7340bdbff583f76c72a51ead5768b690c59e
Submitter: Jenkins
Branch:    stable/newton"
1675727,2019-12-18 17:39:27 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/451319
Reason: This repo is retired now, no further work will get merged."
1675727,2017-03-29 10:44:51 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/451323"
1675727,2017-03-29 10:23:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/451319"
1675727,2017-03-29 10:45:07 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/451324"
1675728,2017-03-24 15:16:04 UTC,"Have just purged everything, including ZFS pool and bridge interface.  Then installed lxd and juju via snappy and still get the exact same error."
1675728,2017-03-24 15:16:54 UTC,I can curl that URL and get a sane response:
1675728,2017-03-24 15:42:31 UTC,And this is the log from lxd.log:
1675728,2017-03-24 16:13:39 UTC,"Just found the problem after using '--keep-broken', then sshing into the controller container.  I could ping 10.201.51.1 from the controller but port 8443 was not open.  Turning my firewall (ufw) off fixed this, but it always used to work so does juju not open that port by default anymore?"
1675728,2017-03-29 05:53:36 UTC,"Juju doesn't interact with UFW at all. So if you've firewalled off ports from being accessible from containers, it is going to stay inaccessible."
1675728,2017-03-29 06:55:23 UTC,"Based on comment # 5, the best we can do is to improve messaging around this failure. I am triaging this as a Medium, usability bug."
1675729,2017-03-24 11:45:17 UTC,"ok, so if it doesn't work the first time, next time do the same thing but enter spread, select the loading app from the spread and then close."
1675729,2017-03-24 11:41:34 UTC,"hm.. can't alaways reproduce the bug, there is probably more to it"
1675733,2017-03-28 13:39:26 UTC,"Reviewed:  https://review.openstack.org/448515
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=21c3b2070af0635486f66e0b864533952760738e
Submitter: Jenkins
Branch:    master"
1675733,2017-06-09 15:36:08 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1675734,2017-03-27 14:26:46 UTC,The bug shouldn't be reproducible any more because we reverted this code.
1675734,2017-03-28 10:21:30 UTC,"https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.deploy_multipath/178/
it reproduces..."
1675734,2017-03-29 17:41:46 UTC,"Reviewed:  https://review.openstack.org/451437
Committed: https://git.openstack.org/cgit/openstack/fuel-agent/commit/?id=9b15d47ad5763dda28d667eebe1516459270a099
Submitter: Jenkins
Branch:    stable/newton"
1675734,2017-04-03 10:24:03 UTC,the issue was reproduced by https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.deploy_multipath/184/
1675736,2017-03-24 14:00:11 UTC,"2017-03-24 01:49:23 +0000 Scope(Class[Osnailyfacter::Openstack_haproxy::Openstack_haproxy_stats]) (notice): MODULAR: openstack_haproxy/openstack_haproxy_stats.pp
2017-03-24 01:49:23 +0000 Puppet (warning): You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 8 in file /etc/puppet/modules/haproxy/manifests/balancermember/collect_exported.pp
2017-03-24 01:49:24 +0000 Puppet (warning): Not collecting exported resources without storeconfigs
2017-03-24 01:49:24 +0000 Puppet (notice): Compiled catalog for node-1.test.domain.local in environment production in 0.85 seconds
2017-03-24 01:49:26 +0000 Puppet (notice): Finished catalog run in 1.08 seconds"
1675741,2017-03-28 11:47:10 UTC,"Reviewed:  https://review.openstack.org/450705
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=ed05fa417c4a78970dd5bdcdd3e1922f3c07f0ac
Submitter: Jenkins
Branch:    stable/ocata"
1675741,2017-03-28 11:46:47 UTC,"Reviewed:  https://review.openstack.org/450706
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=8105b3ca18497440a960c266bd44e0979ec5159e
Submitter: Jenkins
Branch:    stable/newton"
1675741,2017-03-24 13:57:17 UTC,"Reviewed:  https://review.openstack.org/449618
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=c3f55e797ec4cbb34b9238c352b6bf70f975c1b0
Submitter: Jenkins
Branch:    master"
1675742,2017-07-08 15:19:24 UTC,"It would be very helpful if you could provide the image together with information about the modifications you made to it before saving. Saving works for my uses cases here, so you must be hitting some corner case."
1675742,2017-07-08 15:24:02 UTC,Same exception as bug https://bugs.launchpad.net/pinta/+bug/1660164
1675749,2017-03-24 12:12:28 UTC,"StacktraceTop:
 ?? ()
 make_protobuf_object () at ./src/client/rpc/../make_protobuf_object.h:29
 mir::client::rpc::MirProtobufRpcChannel::on_data_available() (this=0x55bace40b1d0) at ./src/client/rpc/mir_protobuf_rpc_channel.cpp:457
 operator() () at ./src/client/rpc/stream_socket_transport.cpp:40
 _ZNSt17_Function_handlerIFvRKSt10shared_ptrIN3mir6client3rpc15StreamTransport8ObserverEEEZNS3_18TransportObservers17on_data_availableEvEUlT_E_E9_M_invokeERKSt9_Any_dataS8_.lto_priv.368 (__functor=..., __args#0=...) at /usr/include/c++/6/functional:1731"
1675749,2017-08-21 08:52:15 UTC,Probably the same cause as lp:1666181 (but not marking as dup yet as need to confirm the problem isn't gtk-mir/qtubuntu)
1675767,2017-03-28 06:48:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675767,2017-04-10 16:54:23 UTC,Crashes when network cable is unplugged.
1675773,2017-03-24 13:29:25 UTC,"StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 get_device_description (upower=0x5619581684e0, device=device@entry=0x5619581df740) at xfpm-power-common.c:358
 power_manager_button_update_device_icon_and_details (button=0x5619581dd0d0, device=0x5619581df740) at ../panel-plugins/power-manager-plugin/power-manager-button.c:382
 g_closure_invoke () from /tmp/apport_sandbox_R6_Xcq/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /tmp/apport_sandbox_R6_Xcq/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1675773,2018-08-18 17:28:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675774,2017-03-24 13:45:09 UTC,"StacktraceTop:
 _int_free (av=0x7ff208000020, p=0x7ff208013ba0, have_lock=0) at malloc.c:4049
 __GI___libc_free (mem=<optimized out>) at malloc.c:2982
 CRYPTO_free () from /tmp/apport_sandbox_N6JOLT/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
 EVP_CIPHER_CTX_cleanup () from /tmp/apport_sandbox_N6JOLT/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
 ssl_clear_cipher_ctx () from /tmp/apport_sandbox_N6JOLT/lib/x86_64-linux-gnu/libssl.so.1.0.0"
1675775,2017-03-24 14:34:33 UTC,"looks like it's the same behavior as on unity7 except that on u7 you can still snap the window, but in unit8 you can't"
1675775,2017-03-24 15:08:46 UTC,Or maybe we could ignore alt+tab while dragging.
1675778,2017-04-17 06:07:27 UTC,"Upstream Newton patch was merged: https://review.openstack.org/#/c/453511/
Need to sync or backport manually"
1675778,2017-04-05 08:28:39 UTC,Newton backport: https://review.openstack.org/#/c/453511/
1675778,2017-04-17 12:59:17 UTC,"Fix proposed to branch: 10.0/newton
Change author: Oleg Bondarev <email address hidden>
Review: https://review.fuel-infra.org/33148"
1675778,2017-03-31 13:04:20 UTC,"Upstream bug filed: https://bugs.launchpad.net/neutron/+bug/1678104
Upstream patch: https://review.openstack.org/#/c/452195"
1675778,2017-03-31 13:03:31 UTC,"Change abandoned by Oleg Bondarev <email address hidden> on branch: 10.0/newton
Review: https://review.fuel-infra.org/32680
Reason: Upstream patch to track https://review.openstack.org/#/c/452195/"
1675778,2017-03-30 16:35:24 UTC,Decreased the priority to High since workaround was found and verified. Suggest to go with this issue as Known Issue.
1675778,2017-03-30 16:06:39 UTC,Verified: dhcp port deletion fixes dhcp issue - agent recreates port and things get back to normal. Additionally need to reboot VMs so they issue DHCP requests and get back online.
1675778,2017-03-30 15:56:22 UTC,"Possible workarounds (to be checked):
 - delete dhcp port of a network with the issue
 - add a delay between ipv4 and ipv6 subnets creation"
1675778,2017-03-27 19:11:18 UTC,"It looks like that IPv6 address was not created for DHCP-port for net1: see port-list in snapshot or below, then previously mentioned code was triggered."
1675778,2017-03-30 15:43:03 UTC,Looks like a race between ipv6 subnet create and network dhcp port create.
1675778,2017-03-30 12:01:45 UTC,So the difference between nets 1 and 2 is that for net 1 dhcp port is first created for one ipv4 subnet:
1675778,2017-03-29 17:38:47 UTC,Raised to Critical because there is no workaround
1675778,2017-03-27 19:22:45 UTC,"Removing area-library, since second VM is set up and fully running. Adding area-mos since race conditions was mentioned around spotted code."
1675778,2017-03-27 18:59:29 UTC,"It was initially failed with next debug http://paste.openstack.org/show/604364/, which is leading to https://github.com/openstack/neutron/commit/571af6bc37315ff023981904bd2592aa8ec0ec14 by kevinbenton. Summoned."
1675778,2017-03-27 18:30:07 UTC,"Possible cause:
2017-03-24 01:51:17.610 28865 DEBUG neutron.agent.linux.dhcp [req-b8e5325a-451e-414d-bff3-bc34fabca323 - - - - -] Unable to access /var/lib/neutron/dhcp/560fd076-9a6b-4edc-85be-1083db94c931/interface _get_value_from_conf_file /usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py:261
2017-03-24 01:51:17.611 28865 DEBUG neutron.agent.linux.dhcp [req-b8e5325a-451e-414d-bff3-bc34fabca323 - - - - -] Agent does not have an interface on this network anymore, skipping reload: 560fd076-9a6b-4edc-85be-1083db94c931 reload_allocations /usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py:501"
1675778,2017-03-30 15:53:59 UTC,"Fix proposed to branch: 10.0/newton
Change author: Oleg Bondarev <email address hidden>
Review: https://review.fuel-infra.org/32680"
1675779,2019-05-13 08:00:39 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1675779,2017-12-22 15:24:20 UTC,Have you tried reproducing the issue on master?
1675779,2017-12-22 10:23:18 UTC,"Reproduced on Ubuntu 16.04, Inkscape 0.92.2+68~ubuntu16.04.1"
1675779,2017-12-26 16:10:32 UTC,"Hi,"
1675779,2017-03-27 12:26:59 UTC,Reproduced (after many tries) on Windows 7 (64-bit) with lp:inkscape/0.92.x rev. 15407 (32-bit version). Same backtrace.
1675779,2017-03-25 14:01:55 UTC,You're welcome.
1675779,2017-03-24 19:48:33 UTC,Thanks for taking the time to file a report!
1675779,2017-03-27 12:55:43 UTC,"The best option would be to update our local copy of libavoid, as explained in bug #1353833 ""Update libavoid, libcola and libvpsc code"" (https://bugs.launchpad.net/inkscape/+bug/1353833). Our version is 8 years old, and the upstream code is still updated regularly."
1675786,2017-03-27 16:01:58 UTC,Upstream bug: https://bugs.launchpad.net/horizon/+bug/1676486
1675789,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1675791,2019-01-14 20:36:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630769"
1675791,2019-03-12 18:43:24 UTC,"Reviewed:  https://review.openstack.org/630769
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=35cc0f5e943642dd8d9dacbf0dac6e260f708d7d
Submitter: Zuul
Branch:    master"
1675791,2019-03-22 03:44:14 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1675791,2019-04-03 20:04:47 UTC,This issue was fixed in the openstack/nova-powervm 8.0.0.0rc2 release candidate.
1675791,2019-08-12 21:11:47 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1675791,2019-06-28 19:18:00 UTC,"Reviewed:  https://review.opendev.org/643853
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ca6f6fce691863901b01d37b8f6e3eadb2bcec4
Submitter: Zuul
Branch:    stable/rocky"
1675791,2019-09-26 09:30:49 UTC,This issue was fixed in the openstack/nova-powervm 9.0.0.0rc1 release candidate.
1675791,2019-12-17 21:07:17 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/661667
Reason: Queens is now in extended maintenance mode upstream [1] so I don't think this is something we need to keep around in the review dashboard, especially because it looks abandoned at this point. If someone wants it downstream they can cherry-pick it from here."
1675791,2017-06-27 16:02:44 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1675791,2019-05-28 03:10:36 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/661667"
1675791,2017-06-23 12:53:46 UTC,"There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments."
1675791,2019-03-18 05:32:50 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/643853"
1675791,2017-04-06 14:04:17 UTC,"Hey! I just thought - do we even need to share an image ? Basically, demo user doesn't need to manage image itself, right? All he needs is to boot an instance from that image, as I understand.
Or is it better to make it more explicit and share it among ""consumer"" and ""producer""?"
1675791,2017-03-24 19:26:08 UTC,"When Nova creates a snapshot image it passes is_public=False to the nova.image.glance client wrapper, which translates that to visibility=private in glance v2 parlance.  This is legacy behavior from when nova only worked with glance v1."
1675791,2017-03-24 19:16:00 UTC,Maybe demo user just shouldn't have permission to unshelve it once admin shelved it? I guess it make sense
1675791,2017-04-12 14:53:33 UTC,The producer in this case is the admin that created the snapshot via the shelve operation. The consumer is the user (owner of the instance) that wants to unshelve the instance and needs access to the image snapshot to unshelve the instance.
1675791,2017-03-24 19:07:57 UTC,"Yeah so I think the problem is what you described in the bug description. The instance is owned by the demo project, but when the admin shelves the instances, the resulting snapshot image is owned by the admin project. The shelve_image_id is stored on the instance, and when we go to unshelve we try to build the instance using that image, which is owned by the admin, so the demo user that is trying to unshelve does not have access to the snapshot image and we get the 404 from Glance, and we fail."
1675791,2017-03-24 19:02:49 UTC,"-bash-4.2$ openstack server create --image 6b77c526-b408-43c9-8f90-d9fecaba55f3 --flavor m1.tiny test1
+--------------------------------------+----------------------------------------------------------------+

| Field                                | Value                                                          |


+--------------------------------------+----------------------------------------------------------------+

| OS-DCF:diskConfig                    | MANUAL                                                         |
| OS-EXT-AZ:availability_zone          |                                                                |
| OS-EXT-STS:power_state               | NOSTATE                                                        |
| OS-EXT-STS:task_state                | scheduling                                                     |
| OS-EXT-STS:vm_state                  | building                                                       |
| OS-SRV-USG:launched_at               | None                                                           |
| OS-SRV-USG:terminated_at             | None                                                           |
| accessIPv4                           |                                                                |
| accessIPv6                           |                                                                |
| addresses                            |                                                                |
| adminPass                            | N25cs5PC6Cm3                                                   |
| config_drive                         |                                                                |
| created                              | 2017-03-24T17:41:01Z                                           |
| flavor                               | m1.tiny (1)                                                    |
| hostId                               |                                                                |
| id                                   | c5e2b76d-46f3-40db-80d3-b0771f7609f9                           |
| image                                | cirros-0.3.4-x86_64-uec (6b77c526-b408-43c9-8f90-d9fecaba55f3) |
| key_name                             | None                                                           |
| name                                 | test1                                                          |
| os-extended-volumes:volumes_attached | []                                                             |
| progress                             | 0                                                              |
| project_id                           | 967dab08b95048f9bbc1a42579245c39                               |
| properties                           |                                                                |
| security_groups                      | [{u'name': u'default'}]                                        |
| status                               | BUILD                                                          |
| updated                              | 2017-03-24T17:41:02Z                                           |
| user_id              ...
"
1675791,2017-03-24 19:02:22 UTC,And these
1675791,2017-03-24 17:59:57 UTC,These are commands which produced the errors (logs attached above)
1675791,2017-03-24 17:57:16 UTC,"Here are logs that I see from nova conductor, during the unshelving"
1675791,2017-03-24 14:33:33 UTC,"The fact the instance went into error state on unshelve is not likely related to the tenant doing the unshelve, but rather the instance probably failed to spawn on the compute node during unshelve. Check your nova-conductor, nova-scheduler and/or nova-compute logs for errors."
1675791,2017-03-24 14:28:18 UTC,"Please, say what you think about this? What is the valid workflow for this scenario?"
1675792,2019-12-18 17:22:44 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/449649
Reason: This repo is retired now, no further work will get merged."
1675792,2019-12-18 17:22:38 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/449648
Reason: This repo is retired now, no further work will get merged."
1675792,2017-04-05 16:16:13 UTC,Verified on 10.1. Sequence is renamed.
1675792,2017-03-24 20:14:23 UTC,"Reviewed:  https://review.openstack.org/449650
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=2513d177135f1addd6b0d0ea5d4168aea8b42280
Submitter: Jenkins
Branch:    stable/newton"
1675792,2017-03-24 14:24:59 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/449650"
1675792,2017-03-24 14:24:47 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/449649"
1675792,2017-03-24 14:24:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/449648"
1675796,2017-03-27 10:58:15 UTC,"Hi Vikash, how are both port-chains and port-pair-groups specifically defined?"
1675796,2017-03-27 12:37:57 UTC,"Hi Igor,"
1675796,2017-04-06 17:57:40 UTC,"The issue is that for a single arm SF, the OVS agent (packet re-classifier in SFC Proxy) needs to distinguish forward traffic from reverse traffic that is returned from the SF."
1675796,2017-04-07 11:05:36 UTC,I see here few things to address:
1675800,2017-03-24 14:51:24 UTC,"Note, this was found while testing for bug 1672804."
1675800,2017-03-29 09:34:56 UTC,Very likely a caching issue indeed.
1675800,2017-03-29 09:35:49 UTC,"I’m marking the bug incomplete so that it will auto-expire in 60 days.
That should give us some time to confirm the issue if it does exist indeed."
1675807,2017-08-13 12:39:46 UTC,"This is now fixed in:
 - trunk - rev 11146
 - release-16.xx - rev 11147"
1675807,2017-08-13 12:39:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675807,2017-09-02 06:12:56 UTC,"Hi,"
1675807,2017-09-22 09:44:16 UTC,"Same issue in Ubuntu 17.04, maybe even more important."
1675808,2018-02-02 21:57:41 UTC,Posted a change to attempt to address this: https://review.openstack.org/540538
1675808,2018-02-08 13:21:12 UTC,This issue was fixed in the openstack/bifrost 5.0.0 release.
1675808,2017-07-27 13:27:28 UTC,Making a note that pysnmp 4.3.9 and pyasn1 0.3.1 are out (presumably fixing the above regression) also reflected in the updated openstack/requirements constraints.
1675811,2017-04-19 02:05:28 UTC,"I'm a Linux noob, and I want to get into mint, but I'm also having this same issue (I think). I also have a 980 and mint 18.1.what did you do to fix this? Please try to be as specific as possible because I might not know what you're talking about. Thanks!"
1675811,2017-04-19 02:36:07 UTC,"Having seen this same issue repeatedly over the years in both Linuxes and BSDs, I think the single most robust solution is to keep an older Nvidia card around... it pretty much always works, regardless of bootloader issues, screen size issues... whatever. As someone who uses Linux daily but doesn't ""follow"" it, if you know what I mean, this is just easiest, because the same solution worked a decade ago, too. I wound up putting an Nvidia GT 730 into my Linux box, which worked well out of the box with both Mint and Ubuntu. An even older card would work too. For information on what is (probably) supported by Nouveau, you can look here:"
1675811,2017-04-19 21:14:42 UTC,"Thanks, it doesn't make sense to buy another gpu, and I couldn't get the vga boot option to work."
1675816,2017-03-24 16:17:11 UTC,"Not sure if it matters, but I have the same issue with some wine applications like FastStone Image Viewer."
1675817,2020-10-04 09:18:06 UTC,Can you still reproduce the error with 7.0 in 20.04 LTS?
1675825,2017-12-18 20:52:56 UTC,Lines can most certainly overlap.
1675825,2018-12-17 05:52:51 UTC,You're on the right track idovecer.  The real trick is to ensure that the size of the outer (container) text element is the same size or smaller than the inner text.
1675825,2018-12-03 13:01:27 UTC,"This is the real solution for this BUG, Inkscape version 0.92.3:"
1675825,2018-06-28 18:25:51 UTC,"I think I figured it out after reading about line spacing here: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92#Line_Spacing, but didn't really find anyone clearly answering online so I thought I would share."
1675825,2018-02-20 17:02:17 UTC,"I am experiencing this bug, too. (Kubuntu 17.10, Inkscape 0.92.2 (5c3e80d, 2017-08-06))"
1675825,2018-01-09 14:45:17 UTC,"When I start Inkscape from the terminal, select a text and try to set its line-height, I see the following output in the terminal:"
1675825,2018-01-09 14:40:14 UTC,"Affected by this in 0.92 on Debian Stretch too. The problem seems to bit a bit erratic, I've seen line-height work in approx. 5% of cases, but only using centimeters."
1675825,2017-12-25 00:45:59 UTC,"I have this problem as well on Mac. Starting with a brand new document, I'm unable to text with a reasonable line spacing or (apparently) adjust the line spacing. This works perfectly fine on Windows."
1675825,2017-05-24 06:11:19 UTC,"Pity I can't edit the last comment.  ""a bug change"" should be ""a big change"""
1675825,2017-08-31 07:24:44 UTC,"Actually, after more work with .92, it seems like there's no bug here.  It's the interaction between the outer element and inner element line spacings that's doing this.  I can't say I've totally grokked it, but it's getting easier."
1675825,2017-05-24 06:08:46 UTC,"I think I am also experiencing this bug, but it's also mixed up with #1663075 https://bugs.launchpad.net/inkscape/+bug/1663075."
1675825,2017-03-26 22:06:27 UTC,"Thanks for your reply Eman, (random name, that, btw ;-) but that does not work for me. In a fresh new document, I did as you suggested and set line spacing to 125%. Then I drew a text frame and pasted text. This looked okay at the default font size of 30pt, and I thought the problem might be solved, but no. When I then selected the text and changed the font size to 10pt, the line spacing did not follow with it proportionally but instead remained at the massive line space from the 30pt setting. Changing the line spacing - even down to the crazy 0% - did not help at all."
1675825,2017-03-26 04:36:46 UTC,"Mark, this really sounds like a bug, but I personally cannot reproduce it on Linux with 0.92.1 nor with trunk version. What happens with units when you change font size to 10pt? Does they remain 'percents' or maybe change to something else? Have you tried to paste a text from another source?"
1675825,2017-03-26 01:36:08 UTC,Perhaps you can share an example file.
1675825,2017-03-25 20:49:04 UTC,"Thanks for your reply Eman, (random name, that, btw ;-) but that does not work for me. In a fresh new document, I did as you suggested and set line spacing to 125%. Then I drew a text frame and pasted text. This looked okay at the default font size of 30pt, and I thought the problem might be solved, but no. When I then selected the text and changed the font size to 10pt, the line spacing did not follow with it proportionally but instead remained at the massive line space from the 30pt setting. Changing the line spacing - even down to the crazy 0% - did not help at all."
1675825,2017-03-24 20:26:18 UTC,I set default line spacing units to percents and this works for me. Click on the Text tool when nothing is selected and then set line spacing to e.g. 150%. After that when you'll create a new text your line spacing will be dependent on font size you select.
1675825,2017-12-18 19:51:25 UTC,I'm getting issues with this as well... it seems like there's some kind of internal constraint that doesn't allow leading below 1.0 to be applied.
1675830,2017-03-25 18:04:35 UTC,"Yes, I know."
1675830,2017-03-25 17:42:57 UTC,"Okay, I was hoping that I'd be able to suggest, as a simple fix, trying a newer driver.  But I see that v304 is, indeed, the most recent Linux driver available for your GPU."
1675830,2017-03-25 18:12:25 UTC," I suspect you will have the same issue with gnome-shell.  budgie and
gnome-shell use the same window manager."
1675830,2017-03-25 15:06:09 UTC,My GPU is Nvidia GeForce 6150SE nForce 430
1675830,2017-09-18 14:51:16 UTC,Mutter has now been updated to GNOME 3.26 on 17.10.  Please can you retest.
1675830,2017-08-05 20:52:05 UTC,"I am having the same problem with ubuntu 17.10 and 6800TX graphics card. Everything was working. After some updates, I can not log in anymore."
1675830,2017-08-06 00:21:48 UTC,"The attachment ""journal -ae --full"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1675830,2017-03-25 19:21:01 UTC,"Okay, I'm in. I replace the window manager installing compiz and now I can login with nvidia 304."
1675830,2017-03-25 13:39:26 UTC,"Sorry if I missed this in your bug report, but what model Nvidia GPU are you testing?"
1675830,2017-07-18 21:55:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675830,2017-03-24 23:10:37 UTC,False positive.
1675830,2017-03-24 22:52:46 UTC,It's stable for now.
1675830,2017-03-24 20:00:58 UTC,yep - looks like the nvidia driver is killing the budgie-window manager
1675830,2017-03-24 18:26:54 UTC,I tried again with nvidia-304 drivers and I can't login.
1675830,2017-03-24 17:29:27 UTC,I can't see that bug report - but yeah - I suspect it is due to the recent xorg upgrade that has occurred in the last week or so.
1675830,2017-03-24 17:23:44 UTC,I think the bug is bigger than I expected.
1675830,2017-03-24 17:06:07 UTC,I install it yesterday in real desktop.
1675830,2017-03-24 16:21:52 UTC,I saw this a while back but only using Virtualbox.  Have not seen is in a week or so.
1675830,2017-03-24 16:20:28 UTC,when did you install?
1675830,2017-03-25 12:12:32 UTC,I would recommend you try this staging PPA - https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
1675840,2017-04-10 22:21:17 UTC,"Reviewed:  https://review.openstack.org/454584
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=348c0c0e9aeeed861160150ad33b440c1c8c9df9
Submitter: Jenkins
Branch:    master"
1675840,2017-04-07 16:55:02 UTC,Hopefully the Networking commands in CLI reference will cover networking commands provided as OSC plugin via python-neutronclient.
1675840,2017-04-07 16:48:49 UTC,Reset the score to New.
1675840,2017-10-16 21:29:12 UTC,"We probably can keep this open to track the fact that we need to update CLI ref, but as we know we can't remove support for neutronclient without addressing our current gaps: http://lists.openstack.org/pipermail/openstack-dev/2017-October/123133.html"
1675840,2017-04-07 07:47:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/454584"
1675840,2017-03-30 10:05:50 UTC,"Reviewed:  https://review.openstack.org/449505
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=bb51fc3b98950be45c1218df4dd4ca648aaba757
Submitter: Jenkins
Branch:    master"
1675840,2017-04-07 16:48:08 UTC,My original intention is that openstack-manuals should mention that neutron CLI is deprecated and it is recommended to use OSC CLI.
1675845,2017-06-24 18:09:47 UTC,"I can't reproduce- the flag works for me. Are you still seeing this? Can you tell me a bit about your system? Desktop, Wayland/X11? Versions, etc."
1675845,2017-06-29 20:19:24 UTC,"Yep, still happening. Just tested & confirmed with the latest ""terminator_1.91-0~1769~ubuntu17.04.1_all"" from PPA."
1675845,2018-06-25 19:40:40 UTC,"Just installed Ubuntu 18.04 with Gnome and a clean setup of terminator. None of the hide functions appear to be working (hide on start, hide on keypress, hide on focus lost). The terminator window always appears and does not hide."
1675845,2018-06-25 19:42:18 UTC,I should also add that I was running Ubuntu 16.04 with Gnome and all the hide functions worked as expected.
1675851,2017-03-24 18:24:14 UTC,"Sorry, should have made that clear. Indeed, it only affects the manual trigger of metric collection using juju collect-metrics"
1675851,2017-03-29 11:03:31 UTC,"As there is a  workaround, and since we are anticipating small number of charms to be affected by this, I will triage this a Medium bug for now."
1675851,2017-03-24 16:55:33 UTC,"I think this only affects the `juju collect-metrics` command for development, not metric collection in general."
1675853,2017-03-24 16:57:15 UTC,"StacktraceTop:
 _int_malloc (av=av@entry=0x7f22d80a0b00 <main_arena>, bytes=bytes@entry=16) at malloc.c:3413
 __GI___libc_malloc (bytes=16) at malloc.c:2925
 _xcb_in_read () from /tmp/apport_sandbox_JId4XJ/usr/lib/x86_64-linux-gnu/libxcb.so.1
 _xcb_conn_wait () from /tmp/apport_sandbox_JId4XJ/usr/lib/x86_64-linux-gnu/libxcb.so.1
 _xcb_out_send () from /tmp/apport_sandbox_JId4XJ/usr/lib/x86_64-linux-gnu/libxcb.so.1"
1675857,2017-03-27 07:35:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450104"
1675857,2020-06-22 09:59:58 UTC,"Change abandoned by Riccardo Pittau (<email address hidden>) on branch: master
Review: https://review.opendev.org/450104
Reason: seems obsolete but please re-open if needed"
1675859,2019-05-21 08:55:42 UTC,created: https://storyboard.openstack.org/#!/story/2005742
1675883,2018-02-20 22:18:33 UTC,"As a workaround, you can open GIFs with Epiphany."
1675884,2017-03-24 18:32:56 UTC,apport information
1675884,2017-03-24 18:33:04 UTC,apport information
1675884,2017-03-24 18:33:08 UTC,apport information
1675884,2017-03-24 18:32:58 UTC,apport information
1675884,2017-03-24 18:32:02 UTC,apport information
1675884,2017-03-24 18:33:01 UTC,apport information
1675884,2017-03-24 18:31:57 UTC,apport information
1675884,2017-03-24 18:31:46 UTC,apport information
1675884,2017-03-24 18:31:48 UTC,apport information
1675884,2017-03-24 18:31:59 UTC,apport information
1675884,2017-03-24 18:31:54 UTC,apport information
1675884,2017-03-24 18:31:51 UTC,apport information
1675900,2018-01-17 07:45:11 UTC,https://github.com/snapcore/snapd/pull/4499
1675900,2019-10-29 21:51:49 UTC,The referenced pull request was merged and released long ago. Marking the bug as fix released.
1675910,2017-04-14 09:16:20 UTC,This issue was fixed in the openstack/neutron 11.0.0.0b1 development milestone.
1675910,2017-12-07 17:55:30 UTC,Reopened since we reverted the fix.
1675910,2017-03-25 00:23:51 UTC,"Reviewed:  https://review.openstack.org/429441
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=12d24abba75ab3b926edbac389437bacc23914dd
Submitter: Jenkins
Branch:    master"
1675910,2017-03-27 20:09:34 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/450443"
1675910,2017-04-12 23:11:49 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/450443
Reason: Not sure I want to backport all those changes for a semantics fix that doesn't immidiately hits someone."
1675925,2017-03-24 20:49:05 UTC,"My first attempt to fix this involved trying to move gpg-agent invocation from upstart to systemd --user. I got that to work by creating:
~/.config/upstart/gpg-agent.override (manual)
~/.config/systemd/user/default.target.wants/gpg-agent.service -> /usr/lib/systemd/user/gpg-agent.service
~/.config/systemd/user/gpg-agent.service.d/override.conf ([Unit]
Before=graphical-session-pre.target)"
1675925,2017-03-25 00:28:42 UTC,"The attachment ""Fix for SSH_AUTH_SOCK path"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1675925,2017-03-28 20:08:17 UTC,Hello Dimitri and thank you for taking up this issue. Does the milestone ubuntu-17.04 mean that there will not be an SRU for this one-line patch?
1675925,2017-04-05 16:00:31 UTC,This bug was fixed in the package gnupg2 - 2.1.15-1ubuntu7
1675929,2017-06-22 15:35:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675946,2018-02-13 22:39:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675947,2017-03-25 16:53:24 UTC,"Hi, Tyler:
So I converted all the text to paths and then joined the individual words.  I attempted to print it directly from Inskape (9.92.1) and received this error"
1675947,2017-03-26 01:07:54 UTC,"Hi Bob,"
1675947,2017-03-25 01:07:10 UTC,Here is the result of trying to print the attached file using Inkscape version 0.92.1
1675947,2017-03-25 00:20:22 UTC,Can you please try with 0.92.1? Thanks.
1675947,2017-03-25 12:16:35 UTC,"Printing ( Green Harbor Logo.svg ) directly to HP LJ400 crashed Inkscape, with recovery file generated. Inkscape 0.92.1 r15371, Win 8.1 64 bit."
1675949,2019-01-21 14:57:35 UTC,On a fresh Xenial/arm64 installation:
1675949,2018-11-29 15:47:35 UTC,"This issue fell off my radar, and I never followed up on it. I'll see if we can get someone to take a look."
1675949,2017-05-27 04:17:57 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1675949,2017-03-27 18:59:11 UTC,"Everything continues to work fine for me, but I see now that you are on aarch64."
1675949,2018-11-28 23:33:34 UTC,Have we fixed this issue for aarch64?
1675949,2017-03-27 16:11:01 UTC,I'm going to need more information. Can you give me the output of these commands?
1675949,2017-03-27 15:01:00 UTC,"Hi Seth,"
1675949,2017-03-27 14:01:24 UTC,I tried this with 4.10.0-14-generic and could not reproduce your issue. Please try updating and see if you still experience this issue.
1675949,2017-03-24 23:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1675949,2017-03-27 17:03:06 UTC,"root@host1:~/fio# uname -a
Linux host1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:20:17 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux"
1675951,2017-07-26 15:57:25 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1675962,2017-04-18 14:29:59 UTC,"Thanks for your patch!
Does it also work with IM6?"
1675962,2017-04-19 22:49:36 UTC,"Currently not, with this patch Inkscape will work with IM7 only."
1675962,2018-08-18 19:47:49 UTC,I tried it on gentoo with V 0.92.3 and found patch errors:
1675962,2018-08-19 06:13:57 UTC,Shouldn't this be a bug since recent Distros switch to imagemagick 7 in stable trees?
1675962,2019-11-11 11:17:10 UTC,any plan to work on this before final release of inkscape 1.0?
1675975,2018-01-12 19:03:30 UTC,Unassigning due to no activity for > 6 months.
1675975,2017-05-25 19:37:52 UTC,This issue was fixed in the openstack/python-cinderclient 2.1.0 release.
1675979,2018-01-12 19:07:43 UTC,Unassigning due to no activity for > 6 months.
1675979,2017-03-27 16:42:00 UTC,This is being tracked here already:  https://blueprints.launchpad.net/cinder/+spec/client-reset-state-improvements
1675979,2017-03-27 23:43:48 UTC,"Change abandoned by lihaijing (<email address hidden>) on branch: master
Review: https://review.openstack.org/450058
Reason: duplicate with https://review.openstack.org/#/c/446356/"
1675979,2017-03-27 02:22:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450058"
1675979,2017-03-27 23:42:23 UTC,"Yes, I see. I missed it, my bad."
1675981,2019-04-08 16:01:09 UTC,Proposed solution to improve the experience: https://zpl.io/2Gyxqpj
1675981,2017-03-27 19:46:05 UTC,Wow ok! Time to update the documentation.
1675981,2017-03-27 18:45:17 UTC,I am correct you did not set the rack controller as the secondary rack controller if you did you would have another field:
1675981,2017-03-27 16:47:25 UTC,"Did you set the secondary rack controller as the ""secondary_rack"" on the VLAN that is providing DHCP. Setting up the HA is a manual process, once setup it allows one of those two racks on that VLAN to go down that is it."
1675981,2017-03-27 17:28:11 UTC,Please provide a screenshot of the WebUI. I do not believe that is the case.
1675981,2017-03-27 18:33:55 UTC,I had unregistered the second rackd (pmatulis-imp-rack) to allow me to continue with other testing. Simply rebooting it brought me back to where I was before. The original rackd is on pmatulis-imp-maas:
1675981,2017-03-27 17:11:05 UTC,"When a second rack controller is added, when the initial rack controller is already providing DHCP, it is automatically added as a secondary for the VLAN (that has DHCP enabled). I confirmed this (in the web UI) before submitting this issue. Apologies for not having included that information."
1675986,2017-03-25 05:08:41 UTC,Sorry for bad speaking
1675986,2017-12-13 16:41:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1675996,2017-03-27 20:46:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1675996,2017-03-27 21:24:51 UTC,"Hello Joseph,"
1676000,2017-03-25 07:51:47 UTC,unity8 log before crash
1676000,2017-03-25 07:53:19 UTC,"there are more bugs in this bug report,
1. the black window
2. neverball window is transparent
3. if you resize the window it doesn't resize well
4. if you resize/close the black window it crashes unity8"
1676000,2017-03-27 03:30:12 UTC,"The unity8 crash in ""what(): map::at"" is pretty common but I'm not sure if we have one or more remaining causes of that. See bug 1668466, bug 1672012"
1676000,2017-03-27 03:34:56 UTC,"Also, bug confirmed. Unity8 fails to launch Neverball from the app drawer but I can get it running from ssh:
   neverball -- --desktop_file_hint=unity8
and now I can see this bug."
1676000,2017-03-27 03:36:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676000,2017-03-27 03:49:19 UTC,Same bug in neverputt. Looks like the SDL/Unity8 issues mentioned in comment #5.
1676013,2017-10-15 15:06:22 UTC,"ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: MATE
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2014-02-07 (1345 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS ""Precise Pangolin"" - Release amd64 (20140204)
Package: caja 1.12.7-1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Tags: third-party-packages xenial
Uname: Linux 4.4.0-97-generic x86_64
UpgradeStatus: Upgraded to xenial on 2017-04-15 (182 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video wireshark
_MarkForUpload: True"
1676013,2017-10-15 15:06:24 UTC,apport information
1676013,2017-10-15 15:06:25 UTC,apport information
1676013,2017-10-15 15:06:26 UTC,apport information
1676013,2017-10-15 15:06:27 UTC,apport information
1676013,2020-11-28 16:29:04 UTC,"Still happens using caja 1.24.0-1 on Ubuntu 20.04.1.
Caja was apparently trying to generate a thumbnail for an odt (LibreOffice text document) file on the Desktop: when I disabled the thumbnail generation for text files, the high CPU usage stopped."
1676013,2017-10-15 15:05:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676021,2017-08-27 05:50:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676035,2017-07-21 14:24:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676047,2017-03-31 14:35:33 UTC,"Yup, can confirm: FP_LOADER_THREAD::ProcessEntry indirectly calls PCB_IO::FootprintLoad which creates a LOCALE_IO."
1676057,2017-03-27 20:40:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676057,2017-03-25 15:40:00 UTC,"StacktraceTop:
 browse_callback (b=<optimized out>, interface=<optimized out>, protocol=0, event=<optimized out>, name=0x5605c7e76ddc ""Canon MX490 series"", type=0x5605c7e76df4 ""_ipp._tcp"", domain=0x5605c7e76e04 ""local"", flags=AVAHI_LOOKUP_RESULT_MULTICAST, userdata=0x5605c7e77680) at utils/cups-browsed.c:4974
 avahi_service_browser_event (client=client@entry=0x5605c7e77680, event=event@entry=AVAHI_BROWSER_REMOVE, message=message@entry=0x5605c7e77d60) at browser.c:775
 filter_func (bus=<optimized out>, message=0x5605c7e77d60, userdata=0x5605c7e77680) at client.c:247
 dbus_connection_dispatch () from /tmp/apport_sandbox_ZolcvN/lib/x86_64-linux-gnu/libdbus-1.so.3
 dispatch_timeout_callback (t=<optimized out>, userdata=0x5605c7e761d0) at ../avahi-common/dbus-watch-glue.c:105"
1676059,2017-03-27 15:49:10 UTC,Confirmed on Linux Mint 18.1 / Inkscape 0.92.1
1676060,2017-03-26 15:53:35 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1676068,2017-03-25 16:41:30 UTC,I have un-installed and re-installed and still have the same problem....please help...anyone!! Thanks :)
1676069,2017-05-03 08:16:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676069,2018-01-16 02:18:25 UTC,"It is about time this get fixed, please."
1676075,2017-12-04 06:53:18 UTC,"Hi team,"
1676077,2017-03-26 06:41:02 UTC,"Thank you. Yes, that check always succeeded. It's || now."
1676092,2017-10-30 13:26:00 UTC,"I just ran into the exact same error message trying to install ""gresolver"":"
1676092,2017-03-26 14:54:25 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1676092,2017-10-30 13:14:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676095,2017-03-26 19:47:10 UTC,I confirm. The two spans have different x-coordinates:
1676095,2017-03-27 11:50:23 UTC,"Reproduced on Windows 7, Inkscape 0.92.1 and lp:inkscape rev. 15608.
Batik 1.7 shows the second line correctly positioned."
1676095,2017-03-26 16:51:32 UTC,Tested/uncovered  in Inkscape 0.92.1 r15371 (on Windows)
1676097,2017-03-25 23:45:29 UTC,"StacktraceTop:
 _cogl_check_extension (name=0x555fb85f6250 ""GLX_EXT_texture_from_pixmap"", ext=ext@entry=0x0) at cogl.c:75
 _cogl_feature_check (renderer=renderer@entry=0x555fb85f5a80, driver_prefix=driver_prefix@entry=0x7fb573c04c1b ""GLX"", data=data@entry=0x7fb573e26d18 <winsys_feature_data+56>, gl_major=<optimized out>, gl_minor=<optimized out>, driver=driver@entry=COGL_DRIVER_GL, extensions=0x0, function_table=0x555fb85f7000) at cogl-feature-private.c:128
 update_base_winsys_features (renderer=0x555fb85f5a80) at winsys/cogl-winsys-glx.c:692
 _cogl_winsys_renderer_connect (renderer=0x555fb85f5a80, error=<optimized out>) at winsys/cogl-winsys-glx.c:794
 cogl_renderer_connect (renderer=0x555fb85f5a80, error=0x7ffea3b07f60) at cogl-renderer.c:687"
1676097,2017-05-18 16:33:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676099,2017-03-26 18:52:29 UTC,"I am not sure if this is related but I notice that to change the default app you have to use the ""Open with other application"" dialog  -  just using a non-default app from amongst those offered in the submenu does not change the default app."
1676099,2017-03-26 19:05:08 UTC,"Also, as .dat files are generic,  different files might appear to be different mime-types under Linux?"
1676102,2017-03-26 12:05:19 UTC,"I used the nvidia drivers from graphics-drivers/ppa repository (correction to my earlier post). However, the bad window borders arising from waking up from suspend mode still persist (not fixed yet). Fortunately, the temporary solution mentioned in https://bugs.launchpad.net/linuxmint/+bug/1667158/comments/13 still works for now."
1676102,2017-03-26 02:04:14 UTC,Below is a section of the dpkg.log. I noticed that the installation is talking about using linux-image-4.4.0-66-generic:amd64 4.4.0-66.87 and linux-image-generic:amd64 4.4.0.66.70. But they aren't the 4.8.0-41-generic kernel that came with Ubuntu. Is this conflict preventing the installation?
1676102,2017-03-26 11:23:45 UTC,"I found a way to fix my issue. I ran the following commands to remove pre-existing nvidia drivers and downloaded and installed the drivers from your repository. After rebooting, Xsession became visible. Finally a success."
1676104,2017-07-17 19:02:09 UTC,"Ran into a wx issue, so this one isn't as quick as I hoped - taking back off the immediate todo list to re-prioritize. If anyone knows why wxHtmlWindow doesn't fire events on right-click on windows, let me know."
1676104,2019-03-05 19:26:59 UTC,"This works on macOS (cmd+C, not right-click)."
1676127,2017-03-26 23:55:05 UTC,*** This is an automated message ***
1676127,2017-07-21 14:23:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676128,2017-03-26 07:37:24 UTC,"The building doesn't do a check if the economy needs wine before producing any, so the Winery is defined correctly in the Lua init file. We need to investiagte where this goes wrong on the C++ side of things."
1676128,2019-09-17 09:44:20 UTC,Migrated to https://github.com/widelands/widelands/issues/1674
1676132,2018-05-08 18:04:41 UTC,This change was made by a bot.
1676132,2021-01-07 04:12:02 UTC,4.8 EOL
1676137,2017-11-05 16:20:42 UTC,"True, I was hoping it would keep information about changes pertaining to at least the last 3 or so versions still on the machine."
1676137,2017-11-05 15:55:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676137,2017-03-27 09:11:52 UTC,"I woke my laptop this morning and now I see one change:-
alan@gort:~$ snap changes
ID   Status  Spawn                 Ready                 Summary
959  Done    2017-03-27T09:08:27Z  2017-03-27T09:08:36Z"
1676138,2017-03-26 16:53:26 UTC,Tested/uncovered  in Inkscape 0.92.1 r15371 (on Windows)
1676144,2017-03-26 13:01:05 UTC,"We're using ""libvisio"" [1,2] for importing VSS files, not the one you mentioned."
1676144,2017-03-31 21:40:37 UTC,"Hello,"
1676144,2017-04-01 00:35:35 UTC,"Wow, great, thanks for the input! I figured we'd need to do some additional work, good to know you already took care of it. :-)"
1676144,2017-04-05 20:26:39 UTC,"I just committed a fix in
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15615"
1676146,2017-06-14 09:25:01 UTC,Cinder sets the type of new volume the same with source volume.
1676148,2017-05-28 15:15:05 UTC,"Hi,"
1676148,2017-05-28 04:17:31 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1676148,2017-06-08 06:32:05 UTC,You need to file an upstream bug at https://bugzilla.kernel.org/
1676148,2017-03-27 20:44:59 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1676148,2017-03-26 11:30:14 UTC,This change was made by a bot.
1676148,2017-03-28 07:28:21 UTC,"I'm not able to remember when it started, it was a few month ago."
1676149,2017-03-26 11:25:45 UTC,"StacktraceTop:
 ?? () from /tmp/apport_sandbox_fZzBsK/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_build_filename () from /tmp/apport_sandbox_fZzBsK/lib/x86_64-linux-gnu/libglib-2.0.so.0
 build_uri (job=0x5609eb747f80) at mate-screenshot.c:926
 try_check_file (io_job=0x7f5d7c003a40, cancellable=0x0, data=0x5609eb747f80) at mate-screenshot.c:946
 ?? () from /tmp/apport_sandbox_fZzBsK/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0"
1676149,2019-05-08 00:26:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676163,2017-07-07 16:53:21 UTC,"This is fixed, isn't it? Can we close the bug?"
1676164,2018-03-29 18:43:16 UTC,"Recently upgraded Firefox, and it wants Pulseaudio. This sucks, found ESR packege working with ALSA. PLease add ESR to official repo, I use only LTS, and want ESR for me and my users."
1676164,2017-12-15 12:25:31 UTC,"OT, but I agree, this is bad... I blame Mozilla first, but on this issue, Ubuntu is even more to blame. I am more and more running software outside of the repos, binaries or compiled here. At this rate I might go to something like Slackware... Or back to Gentoo or something based on it where you don't need to compile absolutely everything."
1676164,2017-12-15 11:08:53 UTC,"Unbelievable: Canonical has released Firefox 57, which no longer supports XUL extensions (i.e. the ones in use since Firefox was created, and when Trusty was released), in 14.04 Trusty.  This is breaking users' Firefox installations in a ""Long Term Support"" release.  And still no official ESR package."
1676164,2017-11-29 21:03:13 UTC,It seems there is an official Canonical ppa for this now.
1676164,2017-11-19 10:52:40 UTC,"Some days ago Mozilla released Firefox 57 which completely disable classic (""LEGACY"") extensions. I think that real enterprise users are not happy with this new feature. Users do not need bells and whistles, they need to do their work with stable user experience and without security vulnerabilities. Firefox users can’t repair car while driving it."
1676164,2017-10-11 21:30:59 UTC,"Firefox 52 ESR packages for all supported Ubuntu versions are available here:
https://launchpad.net/~mozillateam/+archive/ubuntu/ppa"
1676164,2017-09-15 18:42:46 UTC,Do you have any news about packaging Firefox ESR in supported Ubuntu?
1676164,2017-09-09 21:00:34 UTC,"I'll send an email to the Ubuntu Developers list on Monday. With my Lubuntu Release Manager hat on, this is desirable for Lubuntu."
1676164,2017-09-09 20:59:45 UTC,This isn't a Debian issue.
1676164,2017-09-09 20:48:16 UTC,"This problem is very actual.
It was discussed at least twice on AskUbuntu (see https://askubuntu.com/questions/305199/is-there-a-deb-package-to-install-firefox-esr and https://askubuntu.com/questions/505895/how-can-i-install-an-older-version-of-firefox-in-ubuntu-14-04 )."
1676164,2017-08-19 07:03:51 UTC,"Not because of the enterprise argument, but because Xul support will be dropped in 57.x. This means a large number of vital extensions will cease to work."
1676164,2017-08-19 06:59:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676164,2017-09-09 21:13:52 UTC,"Or, I guess this is a thing :)"
1676169,2017-10-03 00:34:35 UTC,This bug appears to have been fixed in Ubuntu Zesty by a recent update:
1676169,2017-07-26 09:10:19 UTC,Can you try it with 1.18.0+dfsg1-4 from Debian unstable?
1676169,2017-07-26 06:39:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676169,2017-07-26 06:42:39 UTC,Same issue is happening to me. Here are minimal steps to reproduce:
1676169,2017-05-20 09:55:44 UTC,"I was the same not too long ago. :) Anyway, if anyone wants to help, the first step is to figure out the differences between Debian unstable's LLVM 3.9 and the version of LLVM that rust was using for 1.17.0, then see if any of these might be responsible for the armhf and ppc64el failures - similar to what I did in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842956."
1676169,2017-04-25 16:05:29 UTC,"Can you give us exact commands to reproduce it? The example in the original post looks like you're running cargo, not rustc directly. Does it still occur if you move ~/.cargo away somewhere else?"
1676169,2017-05-19 10:22:07 UTC,Thanks for the update. Unfortunately it will be a while before I can upload 1.17.0 to Debian unstable because we have some extra test failures: https://buildd.debian.org/status/package.php?p=rustc&suite=experimental
1676169,2017-05-19 12:24:03 UTC,"Thanks for sharing, unfortunately I am not able to help. I have literally zero experience with rust itself, just using it for that librespot project as end-user."
1676169,2017-03-27 14:10:37 UTC,"Apparently it is caused by the upgrade from rustc 1.15 to 1.16, not by cargo"
1676169,2017-04-25 14:15:53 UTC,The same applies to Debian upstream 1.16.0+dfsg1-1
1676169,2017-04-25 16:31:36 UTC,It happens when compiling this project: https://github.com/plietar/librespot
1676169,2017-05-18 12:53:02 UTC,I can add that rustc 1.17.0+dfsg2-1 from Debian experimental has this issue resolved
1676180,2017-04-04 14:00:24 UTC,forgot the url :D
1676180,2017-04-04 14:10:36 UTC,"The following packages have unmet dependencies:
 phonon4qt5-backend-null : Conflicts: phonon4qt5-backend"
1676180,2017-04-13 10:22:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676180,2017-04-04 14:00:15 UTC,"output with -o debug::pkgproblemresolver=1 (of the reverse problem, i.e. installing phonon4qt5-backend-gstreamer wants to remove libphonon4qt5-dev)"
1676183,2017-03-26 16:26:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1676183,2017-03-27 16:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1676183,2017-03-28 09:52:32 UTC,It could update to 3.13.0-114.161 now.
1676183,2021-01-07 08:40:09 UTC,Closing this as per comment #3
1676186,2017-11-20 22:34:12 UTC,"Yes, I agree."
1676199,2020-06-30 05:00:06 UTC,"Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!"
1676203,2017-04-01 20:01:34 UTC,Solution: http://askubuntu.com/questions/896221/strange-artifacts-along-window-borders-after-waking-computer-from-sleep-mode
1676207,2020-08-06 18:04:12 UTC,We are still hitting this problem in the Neutron CI. E.g.: https://dbb1efe932f0b2b3035c-3cbc7219eb26ae41c7e2906584519ee8.ssl.cf5.rackcdn.com/744210/5/check/neutron-tempest-dvr-ha-multinode-full/b481054/testr_results.html
1676207,2020-05-21 12:57:49 UTC,"Reviewed:  https://review.opendev.org/713151
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=7ac89c977b02fce4d85bd200943a6b179935ae5c
Submitter: Zuul
Branch:    master"
1676207,2020-03-24 09:23:09 UTC,"Increasing the priority as there is already a working fix for the issue, so let's get it prioritized and merged asap."
1676207,2020-03-17 00:00:29 UTC,"Hi Martin,"
1676207,2020-03-16 23:19:12 UTC,Changing the priority to Low as it seems it's not affecting anyone at the moment.
1676207,2020-03-16 00:09:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/713151"
1676207,2020-03-15 23:37:43 UTC,"Hi Guys,"
1676207,2020-12-17 12:54:05 UTC,This issue was fixed in the openstack/tempest 25.0.1 release.
1676207,2020-03-12 13:14:50 UTC,Let me try and see if I can reproduce this issue in my environment
1676207,2018-10-11 06:04:02 UTC,Any update so far on this issue?
1676207,2018-12-06 09:26:41 UTC,I think the proper fix would be to create a dedicated network in this test and use that as gateway instead of the public network. That will avoid any races.
1676207,2018-03-01 06:54:25 UTC,"""because there's a fraction of time when the IP is again available"", it seems the fraction is very small, so I also don't understand why this testcases will fail so often. I guess, maybe ip is not released immediately after delete_port?"
1676207,2018-02-26 18:40:23 UTC,"The test is being skipped, but I don't think that this counts as a fix. Can we unskip it an see whether we still are hitting this issue?"
1676207,2017-03-30 19:14:17 UTC,"Reviewed:  https://review.openstack.org/450032
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=7252ce0789d6eaaa14474d853a50f25ef5c9878a
Submitter: Jenkins
Branch:    master"
1676207,2017-03-27 13:28:15 UTC,I did not change the test. I've seen that failure in our Gate:
1676207,2017-03-27 13:16:26 UTC,Hi Jordan
1676207,2017-03-26 18:50:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/450032"
1676207,2020-02-10 14:31:24 UTC,The current code might be flaky. There are a few reasonable suggestions in the comments above on how to deal with the race here.
1676207,2018-06-14 10:36:36 UTC,"I agree with Jens, maybe we can revert this skip and check Neutron logs when this issue happens again to check what is the root cause of this already allocated IP address"
1676208,2017-03-27 09:31:48 UTC,"Hi Serguei,
I thank you for your report, but must admit you lost me at the description."
1676208,2017-03-27 11:43:51 UTC,"Apologies for creating confusion. It is kind of complicated setup :) It is docker containers environment. Everything runs on the same physical host. libvirtd runs inside of a docker container and is fine (it is part of kola-kubernetes openstack). What I need to do it and the same works with centos, is to define VM manually on the host and then be able to start it. I would like to use the socket and PID of already existing libvirtd process running inside of a docker container. Since libvirtd container runs in the same namespace as the host, both host and container share the same PID namespaces and network namespaces.
I cannot run any virsh commands as every time it fails to connect to the hypervisor. On the next run I will collect dpkg output you requested. Please let me know if you need further clarification."
1676208,2017-03-27 13:42:26 UTC,"2017-03-27 13:28:41.779585 | + sudo virsh capabilities
2017-03-27 13:28:44.447707 | <capabilities>
2017-03-27 13:28:44.447812 |
2017-03-27 13:28:44.447854 |   <host>
2017-03-27 13:28:44.447910 |     <uuid>df3da4c3-707b-4573-ac97-fceb53dc262b</uuid>
2017-03-27 13:28:44.447948 |     <cpu>
2017-03-27 13:28:44.447993 |       <arch>x86_64</arch>
2017-03-27 13:28:44.448041 |       <model>SandyBridge</model>
2017-03-27 13:28:44.448087 |       <vendor>Intel</vendor>
2017-03-27 13:28:44.448141 |       <topology sockets='8' cores='1' threads='1'/>
2017-03-27 13:28:44.448190 |       <feature name='osxsave'/>
2017-03-27 13:28:44.448240 |       <feature name='hypervisor'/>
2017-03-27 13:28:44.448287 |       <feature name='xsaveopt'/>
2017-03-27 13:28:44.448335 |       <pages unit='KiB' size='4'/>
2017-03-27 13:28:44.448384 |       <pages unit='KiB' size='2048'/>
2017-03-27 13:28:44.448424 |     </cpu>
2017-03-27 13:28:44.448467 |     <power_management/>
2017-03-27 13:28:44.448512 |     <migration_features>
2017-03-27 13:28:44.448555 |       <live/>
2017-03-27 13:28:44.448598 |       <uri_transports>
2017-03-27 13:28:44.448648 |         <uri_transport>tcp</uri_transport>
2017-03-27 13:28:44.448698 |         <uri_transport>rdma</uri_transport>
2017-03-27 13:28:44.448741 |       </uri_transports>
2017-03-27 13:28:44.448786 |     </migration_features>
2017-03-27 13:28:44.448826 |     <topology>
2017-03-27 13:28:44.448869 |       <cells num='1'>
2017-03-27 13:28:44.448913 |         <cell id='0'>
2017-03-27 13:28:44.448965 |           <memory unit='KiB'>8174408</memory>
2017-03-27 13:28:44.449020 |           <pages unit='KiB' size='4'>2043602</pages>
2017-03-27 13:28:44.449074 |           <pages unit='KiB' size='2048'>0</pages>
2017-03-27 13:28:44.449117 |           <distances>
2017-03-27 13:28:44.449166 |             <sibling id='0' value='10'/>
2017-03-27 13:28:44.449211 |           </distances>
2017-03-27 13:28:44.449257 |           <cpus num='8'>
2017-03-27 13:28:44.449315 |             <cpu id='0' socket_id='0' core_id='0' siblings='0'/>
2017-03-27 13:28:44.449376 |             <cpu id='1' socket_id='1' core_id='0' siblings='1'/>
2017-03-27 13:28:44.449434 |             <cpu id='2' socket_id='2' core_id='0' siblings='2'/>
2017-03-27 13:28:44.449493 |             <cpu id='3' socket_id='3' core_id='0' siblings='3'/>
2017-03-27 13:28:44.449554 |             <cpu id='4' socket_id='4' core_id='0' siblings='4'/>
2017-03-27 13:28:44.449615 |             <cpu id='5' socket_id='5' core_id='0' siblings='5'/>
2017-03-27 13:28:44.449673 |             <cpu id='6' socket_id='6' core_id='0' siblings='6'/>
2017-03-27 13:28:44.449733 |             <cpu id='7' socket_id='7' core_id='0' siblings='7'/>
2017-03-27 13:28:44.449776 |           </cpus>
2017-03-27 13:28:44.449815 |         </cell>
2017-03-27 13:28:44.449897 |       </cells>
2017-03-27 13:28:44.449940 |     </topology>
2017-03-27 13:28:44.449980 |     <secmodel>
2017-03-27 13:28:44.450025 |       <model>none</model>
2017-03-27 13:28:44.450090 |       <doi>0</doi>
2017-03-27 13:28:44.450132 |     </secmodel>
2017-03-27 13:28:44.450171 |     <secmodel>
2017-03-27 13:28:44.450215 |       <model>dac</model>
2017-03-27..."
1676215,2017-04-06 18:29:43 UTC,"This also happens for:
unity-webapps-runner --amazon --app-id=ubuntu-amazon-default"
1676216,2017-03-27 00:17:16 UTC,That fixed it in Kubuntu 16.04.02 so it's probable it's the solution in default Ubuntu 16.04.02.
1676216,2017-03-26 23:54:59 UTC,"I've now tested Ubuntu 16.04.2 also and it results in the same:
 /cow format specified as overlay and no support found"
1676224,2017-03-26 21:31:55 UTC,https://git.launchpad.net/~oxide-developers/oxide/+git/chromium/commit/?id=50514e920a8bb44c86e081b1411bc2100f424b1a
1676224,2017-03-26 21:33:20 UTC,https://git.launchpad.net/oxide/commit/?id=9c598ddf7966b436f1fe03fccb30e5f374496b0b
1676228,2017-08-21 14:18:38 UTC,This also affects the other distro's install guides. It has been patched in master but still affects the Ocata versions.
1676228,2019-09-30 07:01:48 UTC,This has been fixed for many releases now.
1676229,2018-02-18 23:06:16 UTC,not intresting anymore
1676229,2018-02-18 23:06:43 UTC,one can consider juffed dead
1676232,2017-03-27 21:30:27 UTC,"Could you please get a log from PulseAudio, as outlined here: https://wiki.ubuntu.com/PulseAudio/Log? Thanks."
1676232,2017-03-27 22:05:10 UTC,Here's the log
1676232,2017-03-27 22:08:43 UTC,Here's a link to the alsa script upload. I reinstalled a fresh copy so it may vary from the attached pulseverbose log attached. Let me know what else you might need.
1676232,2017-03-27 22:09:17 UTC,http://www.alsa-project.org/db/?f=7c404c2e361439e9b0aed22e70cfea35cf97e3d2
1676232,2017-03-27 22:15:36 UTC,Here's the bootup log created.
1676239,2017-03-27 13:53:45 UTC,I'd check the preferences settings for bitmaps: default export resolution. Maybe set for =>300dpi
1676241,2017-11-20 22:33:05 UTC,"Agreed, checking for setup/gui instead of just setup/ sounds like the right solution."
1676242,2018-06-06 20:39:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676242,2018-10-06 12:42:27 UTC,"In varnish 5.2.0-1, the ""reload-vcl"" script was replaced with a ""varnishreload"" script from upstream.  This should take care of this issue."
1676243,2017-11-20 22:26:08 UTC,"This for me actually causes the `go` part to be fetched and go through the lifecycle. However, removing the `after` keyword completely does skip everything, which means it indeed isn't included in the dirty calculation."
1676244,2017-04-04 08:03:30 UTC,Thanks for your bugreport.
1676247,2018-11-14 13:57:30 UTC,"Also affects me on 18.04 on one machine only. The machine that I upgraded to 18.04 from 16.04. A fresh install on another machine is not affected. Can temporally be fixed by deleting the config file and re-configuring. Only works then for a couple of reboots. I can also remove the item from startup apps reboot then add it back in and upon reboot I have the indicator in the top panel. Can also remove the app from startup apps and upon reboot manually start the app with the panel indicator present. Popup notifications always work, it's just the panel temperature indicator that goes missing."
1676247,2018-11-14 14:01:29 UTC,Misspoke above. Panel temperature indicator does not start if I manually start the program.
1676251,2017-03-27 05:00:15 UTC,"Also, I just noticed that some of the metadata keys don't use the symbolic constants from common.h. At least DESCRIPTION and CONTENT_TYPE could be used; there might be others."
1676260,2017-03-27 04:39:15 UTC,last comment: actually I'm not sure the root cause is the tainted kernel for the wifi driver .. because I see this comment also when I boot with the 4-4-0.65 kernel.
1676260,2017-03-27 04:33:51 UTC,"here is a list of the loaded modules, the issue is coming from the ath10k"
1676260,2017-03-27 04:36:02 UTC,"[    3.210121] wl: module license 'MIXED/Proprietary' taints kernel.
[    3.210123] Disabling lock debugging due to kernel taint
[    3.211824] wl: module verification failed: signature and/or required key missing - tainting kernel
[    3.222630] audit: type=1400 audit(1490588218.991:2): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/bin/freshclam"" pid=877 comm=""apparmor_parser""
[    3.223332] audit: type=1400 audit(1490588218.995:3): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/sbin/dhclient"" pid=874 comm=""apparmor_parser""
[    3.223352] audit: type=1400 audit(1490588218.995:4): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/NetworkManager/nm-dhcp-client.action"" pid=874 comm=""apparmor_parser""
[    3.223355] audit: type=1400 audit(1490588218.995:5): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/NetworkManager/nm-dhcp-helper"" pid=874 comm=""apparmor_parser""
[    3.223357] audit: type=1400 audit(1490588218.995:6): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/connman/scripts/dhclient-script"" pid=874 comm=""apparmor_parser""
[    3.223835] audit: type=1400 audit(1490588218.995:7): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/lightdm/lightdm-guest-session"" pid=873 comm=""apparmor_parser""
[    3.223839] audit: type=1400 audit(1490588218.995:8): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/lightdm/lightdm-guest-session//chromium"" pid=873 comm=""apparmor_parser""
[    3.223929] audit: type=1400 audit(1490588218.995:9): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/sbin/clamd"" pid=878 comm=""apparmor_parser""
[    3.224943] audit: type=1400 audit(1490588218.995:10): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/sbin/ippusbxd"" pid=881 comm=""apparmor_parser""
[    3.322305] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[    3.339673] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[    3.339692] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2"
1676261,2017-03-27 05:03:58 UTC,this bug is verified in newton release.
1676261,2017-03-27 06:32:38 UTC,refer openstack document
1676261,2017-05-08 08:52:25 UTC,working on this
1676261,2018-01-12 19:07:46 UTC,Unassigning due to no activity for > 6 months.
1676269,2017-03-27 06:56:27 UTC,"StacktraceTop:
 __malloc_assert (assertion=assertion@entry=0x7f86e8b41348 ""((size + offset) & (GLRO (dl_pagesize) - 1)) == 0"", file=file@entry=0x7f86e8b3de6e ""malloc.c"", line=line@entry=2880, function=function@entry=0x7f86e8b41e68 <__func__.11331> ""mremap_chunk"") at malloc.c:301
 mremap_chunk (p=p@entry=0x7f86e9e10230 <initial>, new_size=new_size@entry=64) at malloc.c:2880
 __GI___libc_realloc (oldmem=0x7f86e9e10240 <empty>, bytes=52) at malloc.c:3060
 g_realloc () from /tmp/apport_sandbox_GLUOvA/lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_css_node_declaration_make_writable_resize (decl=<optimized out>, offset=48, bytes_added=4, bytes_removed=0) at ././gtk/gtkcssnodedeclaration.c:98"
1676272,2017-03-31 11:58:53 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1676274,2017-03-27 07:25:15 UTC,this crash https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1676288
1676294,2017-03-27 07:55:57 UTC,"StacktraceTop:
 pango_font_find_shaper (font=0x560960f33a80, language=0x56095e8f4be8, ch=72) at fonts.c:1564
 get_shaper_and_font (state=state@entry=0x7fff3905ca40, wc=wc@entry=72, shape_engine=shape_engine@entry=0x7fff3905c9e8, font=font@entry=0x7fff3905c9f0) at pango-context.c:1228
 itemize_state_process_run (state=state@entry=0x7fff3905ca40) at pango-context.c:1410
 pango_itemize_with_base_dir (context=<optimized out>, base_dir=base_dir@entry=PANGO_DIRECTION_LTR, text=<optimized out>, start_index=<optimized out>, length=<optimized out>, attrs=attrs@entry=0x7f23740049a0, cached_iter=0x7f23580075a0) at pango-context.c:1516
 pango_layout_check_lines (layout=<optimized out>) at pango-layout.c:4011"
1676298,2017-10-04 20:41:16 UTC,This has been addressed with https://blueprints.launchpad.net/horizon/+spec/drop-nova-network in Horizon.
1676298,2017-03-29 20:02:19 UTC,"This really can not be removed as unlike Horizon, we support clouds going back quite a ways (officially only those not EOL but OSC works back past kilo for many things)"
1676298,2017-03-28 15:32:00 UTC,"Question to nova team from horizon side.
From nova team perspective, what is the recommended way if horizon supports Nova security group?
If horizon needs to talk nova micro-versioning API directly, it makes nova-network support difficult. Is it time to drop nova-network support in horizon?"
1676298,2017-03-28 08:27:00 UTC,"This also affects Horizon, which uses novaclient.v2.security_group_rules in https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/nova.py#L36"
1676298,2017-03-28 16:12:34 UTC,"I sent a mail to -dev ML regarding nova-network deprecation policy.
http://lists.openstack.org/pipermail/openstack-dev/2017-March/114674.html"
1676302,2017-03-27 08:40:19 UTC,"StacktraceTop:
 g_assertion_message () from /tmp/apport_sandbox_CZ00Kb/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /tmp/apport_sandbox_CZ00Kb/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ensure_surface_for_gicon (self=self@entry=0x556dd77aa250, style=0x556dd79899d0, dir=dir@entry=GTK_TEXT_DIR_LTR, scale=scale@entry=1, gicon=gicon@entry=0x7f219c00b160) at ././gtk/gtkiconhelper.c:493
 gtk_icon_helper_load_surface (self=self@entry=0x556dd77aa250, scale=1) at ././gtk/gtkiconhelper.c:573
 gtk_icon_helper_ensure_surface (self=self@entry=0x556dd77aa250) at ././gtk/gtkiconhelper.c:601"
1676302,2017-03-31 11:58:42 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1676304,2017-04-05 06:20:59 UTC,"Now using 5.3.2-2 LO version on ZZ (which had a memory leak fix)
As i can see there is less 'freezing' botleneck, but still some regularly."
1676304,2017-03-28 05:58:07 UTC,I am using the on-board graphics on an Intel D277GA-70K motherboard using the standard driver.
1676304,2017-03-27 11:52:13 UTC,"For the record, my system have a nvidia gtx750 card and nvidia-378 driver is used.
Could this be also related to the graphic/kernel config ?
For a deeper test i will run calc via valgrind with/without the libreoffice tweaks
http://www.openoffice.org/qa/wwwstaging/docs/valgrind.html
http://www.kegel.com/openoffice/valgrindingOOo.html"
1676304,2017-03-27 11:12:31 UTC,"Hi dino99,
Thanks for the advice :-)
I tried setting the LibreOffice settings as you suggested followed by a reboot (just to be sure!) the ran LibOffice calc.
So far, no instances of the error and greping the /var/log/syslog shows no similar errors."
1676304,2017-03-27 10:39:44 UTC,"When searching about 'soffice freezes', there are lot of posts, like https://forums.linuxmint.com/viewtopic.php?t=77851"
1676304,2017-03-27 10:12:00 UTC,"oem@u64:~$ journalctl  | grep gnome-session
Mar 27 06:45:23 u64 gnome-session[2728]: gnome-session-binary[2728]: WARNING: Could not parse desktop file gnome-settings-daemon.desktop or it references a not found TryExec binary
Mar 27 06:45:23 u64 gnome-session-binary[2728]: WARNING: Could not parse desktop file gnome-settings-daemon.desktop or it references a not found TryExec binary
Mar 27 06:45:39 u64 gnome-session-binary[2728]: Entering running state"
1676304,2017-03-27 10:18:05 UTC,"Some further information from some investigations:
Firstly, following up on the ""time theory"" above.  It seems to occur at times xx:03:07, xx:08:07, xx:13:07, ...  Ie, every five minutes at seven seconds past.  This seems very regular."
1676304,2017-03-27 10:05:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676304,2017-03-27 10:05:05 UTC,Post too my experience which seems similar to yours. I only see such 'minute' freeze when i'm working with libreoffice-calc (5.3.1 actually); here it is with a more recent version on Zesty 64 bits. (gnome-session 3.24.0-0ubuntu1)
1676312,2017-03-27 11:07:13 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/450166"
1676312,2017-04-05 06:46:46 UTC,"Reviewed:  https://review.openstack.org/450166
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=7218a36805f4d9e6bbbae7221ca9f46a8fe718e3
Submitter: Jenkins
Branch:    stable/mitaka"
1676313,2017-03-27 08:51:53 UTC,It's possible server-mesa-x11.so.13 isn't quite as ready for unthrottled input introduced in Mir 0.26.0. But that's not an uncommon mistake people make in client development. Just need to make sure the code can deal with more input events than frames produced.
1676313,2017-11-03 16:42:54 UTC,Syncing task from Mir.
1676315,2017-03-27 09:06:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450133"
1676328,2020-09-22 23:44:24 UTC,Is this git release https://github.com/SSSD/sssd/releases/tag/sssd-1_13_91 can be upgradable from `1.13.4-1ubuntu1.15` on ubuntu Xenial 16.04 LTS . I am facing memory leaks with this version on multiple servers. Thanks
1676328,2018-07-27 17:08:32 UTC,"hi, any update?"
1676328,2018-06-05 18:35:16 UTC,Thanks for trying it out.
1676328,2018-06-05 18:24:45 UTC,"I have given the package in comment #13 a try. it takes a couple weeks for the problem to get bad enough to trip the monitor we have set up for it, but today is that day:"
1676328,2018-05-18 17:32:50 UTC,Can you give the packages from comment #13 a try please?
1676328,2018-05-18 17:18:25 UTC,"I too have this problem. If it's a matter people reporting it as a problem, count me in. It's taken out production services multiple times. We've had to create monitors and alerts for it, it is a huge problem."
1676328,2018-02-26 23:59:46 UTC,"If you want to give it a try, this PPA (https://launchpad.net/~ahasenack/+archive/ubuntu/sssd-memleak-1676328) has a xenial build with this patch:"
1676328,2018-02-26 20:40:04 UTC,"Sean, could you please share your sssd.conf file?"
1676328,2018-02-22 20:33:19 UTC,"I feel that sssd_be spiraling out of control (spawning hundreds to thousands of processes) and consuming all of the available RAM would be considered a ""High-impact"" bug, when that same behavior is not observed in 14.04."
1676328,2018-02-21 23:56:52 UTC,"> I am still confused by the reasoning behind being unwilling to backport versions of this package in a ""Long Term Support"" release of Ubuntu.
"
1676328,2018-02-21 19:58:09 UTC,"I have backported it myself and multiple issues (including this one) have been resolved as a result. I am still confused by the reasoning behind being unwilling to backport versions of this package in a ""Long Term Support"" release of Ubuntu. This bug is not fixed until a newer version is backported (as mentioned in the original Fedora ticket)."
1676328,2018-01-03 01:56:07 UTC,"No, both group and user enumeration is explicitly turned off in our config. 1.13.4-1ubuntu1.9 seems to start spawning a bunch of sssd_be processes which slows auth to a crawl"
1676328,2018-01-02 11:42:44 UTC,"There is no upstream release for 1.13.5 yet, and a major version dump to 1.14 or 1.15 is not recommended for an LTS release."
1676328,2017-12-20 22:24:35 UTC,I am seeing this is in 1.13.4-1ubuntu1.9. Can we get a version bump in Xenial?
1676328,2017-12-20 22:23:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676328,2017-03-28 16:35:43 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1676328,2017-03-27 10:19:49 UTC,I have this bug in Ubuntu 16.04.
1676328,2018-02-22 23:14:06 UTC,"On Thu, Feb 22, 2018 at 08:33:19PM -0000, sean wrote:

> I feel that sssd_be spiraling out of control (spawning hundreds to
> thousands of processes) and consuming all of the available RAM would be
> considered a ""High-impact"" bug, when that same behavior is not observed
> in 14.04.
"
1676329,2017-03-31 07:19:00 UTC,"Vladimir, your comment here https://review.openstack.org/418821
<quote>
right now we dont use systemctl neither for ovs nor dpdk
</quote>"
1676329,2017-04-28 10:03:18 UTC,"Reviewed: https://review.fuel-infra.org/32689
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1676329,2017-04-28 09:55:36 UTC,"Reviewed: https://review.fuel-infra.org/32688
Submitter: Pkgs Jenkins <email address hidden>
Branch: master"
1676329,2017-03-30 17:29:51 UTC,"Fix proposed to branch: 10.0/newton
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/32689"
1676329,2017-03-27 11:32:02 UTC,Please attach diagnostic snapshot.
1676329,2017-03-30 17:25:44 UTC,Could you please commit it tomorrow.
1676329,2017-03-30 17:24:37 UTC,"--- dpdk.service.bak	2017-03-30 17:23:58.113055992 +0000
+++ /lib/systemd/system/dpdk.service	2017-03-30 17:19:46.886305041 +0000
@@ -2,6 +2,7 @@
 Description=DPDK runtime environment
 DefaultDependencies=false
 After=network-pre.target local-fs.target
+Before=openvswitch-nonetwork.service"
1676329,2017-03-27 12:42:41 UTC,Added snapshot
1676329,2017-03-30 17:29:30 UTC,"Fix proposed to branch: master
Change author: Ivan Suzdal <email address hidden>
Review: https://review.fuel-infra.org/32688"
1676330,2017-03-28 01:27:20 UTC,"This is a good idea. As a workaround, you can do this today by querying the database directly, such as the following:"
1676330,2019-09-19 12:03:15 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1676330,2019-09-19 13:07:57 UTC,"@adam-collard, this is a feature request, not an issue that is should expire after 6 months. If you do not want to implement this feature than that is fine, but please say so."
1676330,2019-09-23 13:58:58 UTC,"Being a feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1676330,2019-09-24 08:51:40 UTC,https://discourse.maas.io/t/query-system-id-from-machines-power-address/1016
1676362,2020-08-05 04:17:39 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1676362,2017-03-27 12:37:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1676362,2020-06-05 15:42:12 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1676363,2017-07-19 22:40:55 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/336293
Reason: This hasn't been updated since May, has a -1 on it and is in merge conflict. If we need to discuss the -1 then I'd suggest bringing this up in the weekly nova meeting or the mailing list. Note that Thursday July 27 is feature freeze for Pike, so if this is going to get done this release it needs to move fast."
1676363,2017-08-01 10:17:15 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1676363,2017-08-01 09:57:51 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/450211
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1676363,2017-08-01 09:57:46 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/450212
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1676363,2017-07-24 14:47:14 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1676363,2017-04-15 12:11:54 UTC,"Reviewed:  https://review.openstack.org/450297
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ccebded0cbb654be18db5b4e0e7f8b8a3a7cacdb
Submitter: Jenkins
Branch:    master"
1676363,2017-03-27 13:04:54 UTC,"Hi Jens, I think you possibly make the case for splitting this into two bugs. One for the status IP addressing information and the other for the IPv6 specifics."
1676363,2017-03-28 08:56:43 UTC,"For reference, here is the sample output before and after my patch series, for an instance with three interfaces (dual-stack slaac, dhcpv6-stateless, dhcpv6-stateful):"
1676363,2017-03-27 15:40:11 UTC,"@Jay: During developing the patch series, I found even a third issue. As the patches stack quite nicely on top of each other, I would prefer keeping this together, though."
1676363,2017-03-27 15:38:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450297"
1676363,2017-03-27 13:15:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450212"
1676363,2017-03-27 13:14:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450211"
1676363,2017-03-28 11:45:52 UTC,"Looking at how the subnet type is being parsed by cloud-init here[1] it seems that ""ipv6_slaac"" and ""ipv6_dhcpv6-stateful"" will both work fine - at least in that regard -, but ""ipv6_dhcpv6-stateless"" will be interpreted as dhcpv6 instead of slaac."
1676371,2018-05-16 14:49:15 UTC,"Hi,"
1676371,2017-09-15 18:16:42 UTC,I'm seeing this as well. Anything I can do to help with the fix? :)
1676371,2017-09-18 05:52:38 UTC,"Hi Manuel,
we currently wait for myself or someone in the community to find the cycles to do the extended backport. The fix was backported before, but that implies changes to the tests (not just disabling but making them correctly matching the changes of the backport)."
1676371,2017-06-23 09:53:03 UTC,"Hi Ezra,
this bug was dormant for a while and I beg your pardon.
I finally got aware of this and also found some time to work on it. Furthermore at the moment it seems no other dovecot SRU is in flight that would block it."
1676371,2017-06-23 04:45:27 UTC,"Appears fixed in Zesty on.  2.2.25-1 was pulled into debian/sid, in July/2016 and into Zesty later that year.  Nominated for SRU back to Yakkety and Xenial."
1676371,2017-06-23 09:59:56 UTC,"[1] seems to be the related change to the tests that make them working again.
But this one applies much less as-is than the actual fix.
OTOH I'm not really tempted to disable the test, so one will need to backport the (required part of) test adaptions properly."
1676390,2017-03-27 11:19:31 UTC,log but probably unreleated
1676390,2017-03-27 17:47:23 UTC,"ok, this seems to be fixed in silo 2626"
1676394,2017-03-29 07:32:43 UTC,same  dkms issue but that is part of my zfs install
1676394,2017-06-15 01:00:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676398,2017-03-29 07:32:53 UTC,This is an oversight.
1676399,2017-04-10 08:10:08 UTC,Added doc issue for online manual: https://github.com/juju/docs/issues/1788
1676399,2017-04-10 08:06:39 UTC,"Re-triaging to Medium usability bug: we should consider how to communicate that command supports both hooks and actions, including help docs as well as potential command rename."
1676399,2017-04-01 05:18:26 UTC,'juju debug-hooks' works for both hooks and actions
1676399,2017-04-03 07:03:08 UTC,@stub : excellent ! What is the name of the hook that should be used to debug an action then ? The name of the action ?
1676399,2017-04-02 20:48:58 UTC,Maybe the comand needs to be renamed to make it more obvious that both hooks and actions are supported?
1676399,2017-04-10 07:35:22 UTC,"actions/nameofaction , similar to hooks/nameofhook."
1676410,2017-03-28 16:54:10 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1676410,2017-03-29 09:09:15 UTC,"On Tue, 28 Mar 2017 16:54:10 -0000
Robie Basak <email address hidden> wrote:"
1676410,2017-03-30 13:03:49 UTC,Thanks Norvald!
1676410,2017-03-30 13:05:07 UTC,"""Low"" because this isn't something that we originally shipped in Xenial, so is effectively a feature enhancement. In fact, it should probably be Wishlist, not Low even."
1676410,2017-03-30 15:19:23 UTC,"I pushed a commit for adding it, but referencing #1633485 rather than this bug"
1676422,2018-01-10 18:18:49 UTC,looks like this has been fixed :)
1676422,2017-10-23 13:00:12 UTC,Relates to newton UCA.
1676422,2017-03-29 13:55:58 UTC,Hello Ubuntu guys. Can you please upload proper version of ironic-lib into cloud-archive?
1676422,2017-03-29 10:44:38 UTC,From the provided trace I'm wondered what version of ironic-lib you are using? In newton the code looks like [1]
1676422,2017-03-29 10:56:41 UTC,My version:
1676422,2017-03-28 13:01:59 UTC,"There is no related dmesg errors, only messages from iscsi:"
1676422,2017-03-29 12:44:34 UTC,"so indeed in version 2.1.0 there is a buggy code that was fixed by:
https://github.com/openstack/ironic-lib/commit/33af42c96556ec66087954f115697d79967efe91
and it was fixed in ironic-lib 2.2.0"
1676422,2017-03-28 12:21:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450754"
1676422,2017-03-28 12:23:00 UTC,"Please give https://review.openstack.org/450754 a try in your ironic-lib, and see if the clears this issue up for you."
1676422,2017-03-27 12:57:02 UTC,This trace is ugly. Better version:
1676422,2017-03-27 12:58:31 UTC,Update: I set up instance creation with --config-drive=True option.
1676422,2017-03-29 12:39:02 UTC,"Looks like you should ideally have 2.1.3, which is where this issue should have been fixed, and would have been the latest tag for newton deployments."
1676422,2017-03-28 08:16:09 UTC,Hello.
1676422,2017-03-27 16:36:34 UTC,Thanks for the report George!
1676422,2017-03-28 12:13:44 UTC,"This looks like a bug in ironic-lib as it has to do with handling command output.  That being said, the call could still be failing with the bug in the command output being fixed.  You may wish to check your kernel log to see if you see any errors there.  In the mean time, I'm working on a patch for the basic issue in ironic-lib."
1676424,2017-03-27 13:24:12 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-March/083184.html
1676424,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1676435,2017-06-13 11:28:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/473790"
1676435,2017-06-16 15:37:27 UTC,"Reviewed:  https://review.openstack.org/473790
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=0ac6a2ec0abe85c94a08a47b242e1374aad74fa6
Submitter: Jenkins
Branch:    master"
1676435,2017-06-19 17:10:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/475462"
1676435,2017-07-01 00:59:47 UTC,"Reviewed:  https://review.openstack.org/475462
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=46261c24e607e6b1fbb17049f2706706853345ff
Submitter: Jenkins
Branch:    master"
1676435,2017-07-05 12:48:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480565"
1676435,2017-07-18 14:54:46 UTC,"Reviewed:  https://review.openstack.org/480565
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=22ca4a276d8644f10d4bc3c4a005d2a6c0fa5bc4
Submitter: Jenkins
Branch:    master"
1676439,2017-07-16 12:10:38 UTC,"Change abandoned by yatin (<email address hidden>) on branch: master
Review: https://review.openstack.org/450240
Reason: Can pickup later if required."
1676439,2017-03-28 04:24:05 UTC,"The ironic image don't contain python?
Yes python2 is not there. I used: https://fedorapeople.org/groups/magnum/fedora-25-kubernetes-ironic.tar.gz"
1676439,2017-03-27 13:55:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450240"
1676439,2017-03-27 15:50:44 UTC,We need a ci for this image.
1676439,2017-03-27 15:48:16 UTC,The ironic image don't contain python?
1676439,2017-03-27 15:59:49 UTC,"There, I missed it https://review.openstack.org/#/c/417457/3/magnum/drivers/k8s_fedora_ironic_v1/image/kubernetes/package-installs.yaml"
1676443,2017-03-28 09:13:02 UTC,Please report the problem upstream so we can keep track of it. https://phabricator.freedesktop.org/tag/pitivi/
1676454,2017-03-27 14:16:37 UTC,Note that the issue is only reproduceable by some people on some systems. We were not able to figure out what the difference was between those systems
1676464,2018-01-18 08:27:16 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-826
1676464,2017-08-15 23:17:01 UTC,"This is due to a bug in the startup code.  The two slave threads are waiting on a condition variable for wsrep_ready.  However, when wsrep_ready is changed, it uses mysql_cond_signal() which wakes up a SINGLE thread.  So one of the slave threads is signalled and continues, the other thread is waiting on the condition variable, which will not be signalled again."
1676464,2017-05-12 23:15:12 UTC,Tried to repro this on 5.7.16 and it looks ok.  Are the repl users on the channels the same or different?
1676464,2017-05-16 08:52:38 UTC,"I've noticed that a possible workaround may be to
(1) Start the node with 'skip-slave-start' in the config
(2) run ""start slave""
This appears to start the slave threads with no issues."
1676464,2017-06-20 04:48:26 UTC,"Przemek,"
1676476,2017-03-27 15:08:26 UTC,"Note that this bug report should be filed against package avahi-daemon, and not avahi, since avahi, itself, isn't even a package, but the Launcpad form wouldn't let me submit it as such."
1676484,2017-12-28 14:40:58 UTC,"QtAV has now made it into Ubuntu, currently in bionic only.
https://packages.ubuntu.com/search?keywords=qtav&searchon=names&suite=all&section=all"
1676484,2019-08-24 05:30:22 UTC,"I believe this is still a problem for Digikam, and with video because so integral to photo apps, it's really demoting the value of Digikam. Any hope for a fix still? Thanks, Joe"
1676484,2019-09-06 08:43:16 UTC,digikam in bionic onwards is built with qtav on supported architectures
1676492,2017-03-30 21:00:14 UTC,Issue being discussed here:
1676492,2017-03-30 21:30:29 UTC,Topic was split out to cover the independent issues properly:
1676492,2019-11-19 10:56:08 UTC,"There are two PRs that tackle both sides of the experience:
- for users: https://github.com/snapcore/snapd/pull/7740 for showing warnings on snap install if there are invalid interfaces.
- for developers: https://github.com/snapcore/snapd/pull/7320 for validating interfaces when creating snaps."
1676492,2019-12-03 11:21:00 UTC,The first of these PRs has landed in master. 2nd still needs some tweaks.
1676492,2019-12-17 12:22:19 UTC,Both PRs landed.
1676493,2017-04-06 16:49:10 UTC,"Hello,"
1676493,2017-04-07 08:54:29 UTC,"Update: after rebooting today the touchpad worked for a few minutes. Then, in the middle of using FIREFOX, the pointer got stuck. I was forced to connect the mouse."
1676493,2017-05-16 05:46:07 UTC,Since upgrade to KUBUNTU 17.04 trouble vitually gone
1676504,2018-09-30 10:08:24 UTC,"Hi all,
Issue is solved after changing the blow lines in the network.sh
line 70
  local found_iface=(`execute VBoxManage list hostonlyifs | sed 's/\r$//'| egrep ""Name: + $name\$"" | awk '/Name/ { $1 = """"; print substr($0, 2) }'`)
line 100
  local new_name=(`execute VBoxManage list hostonlyifs | sed 's/\r$//' | egrep -A9 ""Name: + $name\$"" | awk '/Name/ { $1 = """"; print substr($0, 2) }'`)
line 109 to 111
  local new_ip=(`execute VBoxManage list hostonlyifs | sed 's/\r$//'| egrep -A9 ""Name: + $name\$"" | awk '/IPAddress:/ { print $2 }'`)
  local new_mask=(`execute VBoxManage list hostonlyifs | sed 's/\r$//'| egrep -A9 ""Name: + $name\$"" | awk '/NetworkMask:/ { print $2 }'`)
  local new_dhcp=(`execute VBoxManage list hostonlyifs | sed 's/\r$//'| egrep -A9 ""Name: + $name\$"" | awk '/DHCP:/ { print $2 }'`)
line 137"
1676504,2017-09-22 14:38:34 UTC,"Hi again,"
1676504,2017-09-11 08:01:37 UTC,"Any update on this?
I'm getting the exact same error with cygwin on Windows 10 x64, but still unable to find a workaround."
1676504,2017-04-08 09:10:03 UTC,Even i am also facing the same issue. Any work around available ?
1676504,2017-04-17 06:48:27 UTC,Version of Sed and grep in my environment which fixed the issue without any change of script.
1676504,2017-04-16 12:28:59 UTC,"Hello, i faced the same issue even re install win 8.1 pro. by chance, i did update the vension of sed to 4.4-1 and grep version to 3.0-1, the issue fixed on my PC:"
1676504,2017-06-01 23:43:30 UTC,"Hi, I'm also getting the same error with cygwin on Windows 10 x64"
1676506,2019-10-27 09:54:29 UTC,Thanks for reporting.
1676516,2019-09-17 09:53:29 UTC,Migrated to https://github.com/widelands/widelands/issues/2072
1676529,2017-04-04 11:49:33 UTC,This was due to a switch in the default transport from multicast to unicast in the hacluster charm made for the 16.10 charm release:
1676536,2017-03-28 07:21:38 UTC,Interesting thought. Other Linux terminals I tested do not behave like gnome-terminal in that regard.
1676540,2017-03-27 19:08:07 UTC,"It's Docker.  Docker sets net.ipv4.conf.default.forwarding=1 when it starts the first time, then creates docker0.  If you restart docker, it doesn't set this default."
1676565,2018-07-06 19:46:43 UTC,Note: this is not related to Bug 1750594 which was due to the profile dedup features that were added in the 4.13 kernels.
1676565,2018-06-29 16:55:25 UTC,"There have been several more bug fixes, since I commented on this last. I am going to work on updating the 4.4 kernel, and build a test kernel."
1676565,2018-02-24 02:14:17 UTC,Sadly some leaks remains in all 4.x kernels. I have fixed several reference count bugs and we still have a leak happening. I am actively working on this again so hopefully we can finially get this closed.
1676565,2018-02-23 23:42:55 UTC,any update on this?  i can still crash any 4.x kernel by reloading app armor for half an hour.  3.13 remains unaffected.
1676565,2017-05-19 03:29:48 UTC,"ooops, yeah sorry. It doesn't make much of a difference here as the same version of apparmor was SRUed back to 4.4, but I should still get the versioning right in the bug."
1676565,2017-05-19 01:20:38 UTC,"FWIW, the out of memory condition was actually tested on a 4.8.0-52 kernel from linux-virtual-hwe-16.04"
1676565,2017-05-18 23:01:52 UTC,"thanks,"
1676565,2017-05-18 22:40:12 UTC,"I'm attaching a tarball of an example apparmor directory, sanitized a bit for environment-specific things."
1676565,2017-05-18 01:12:07 UTC,"attaching to this bug would work as well, if you are comfortable doing that"
1676565,2017-05-18 01:09:18 UTC,That is worse than ludicrously slow. Something is definitely broken
1676565,2017-05-17 18:42:23 UTC,"As of this writing, I've been able to load a 341Kb cache file into a 3.13.0-116 kernel over 80,000 times, for a grand total of 27 gigabytes without issue."
1676565,2017-05-17 17:31:09 UTC,We've now seen this issue affect both 4.8 and 4.10 series as well.
1676565,2017-04-25 18:29:11 UTC,Update: 4.4.0-57 is also affected.
1676565,2017-04-18 13:31:07 UTC,"We've been testing on 67 as well as 70, 71, 72, and have only seen one instance of this issue on 67 so far.  The last kernel to work without issue was 4.4.0-57."
1676565,2017-04-03 17:07:44 UTC,"I would guess the 67 kernel should fix this for them. Those patches are being replied but I am currently unsure if they will land in the 71 kernel, as they have not been committed to it yet."
1676565,2017-03-28 14:27:23 UTC,"This may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1645037. If the 67 kernel fixes this for you, I think we can mark this a dupe of 1645037."
1676565,2017-03-27 20:05:19 UTC,"Curious if https://launchpad.net/ubuntu/+source/linux/4.4.0-67.88 or https://launchpad.net/ubuntu/+source/linux/4.4.0-69.90 resolves the issue for you? IIRC, I was seeing some slowness that looked like hangs in the 4.10 kernel until the patches in 67 and 69 were in there. Note: https://launchpad.net/ubuntu/+source/linux/4.4.0-70.91 reverted these patches for unrelated reasons."
1676565,2017-05-18 01:11:28 UTC,"@Jason,"
1676581,2017-03-28 07:24:14 UTC,"Mouse movement by the user should be blocked while the scenario moves the mouse and then immediately released again. Currently, it results in the user and the scenario fighting for the mouse."
1676581,2019-09-17 09:41:59 UTC,Migrated to https://github.com/widelands/widelands/issues/1675
1676583,2018-03-29 10:58:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676587,2019-08-22 20:57:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676592,2017-03-27 20:10:37 UTC,"StacktraceTop:
 synapse_utils_async_once_construct ()
 synapse_desktop_file_service_constructor ()
 ?? () from /tmp/apport_sandbox_iquL81/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /tmp/apport_sandbox_iquL81/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /tmp/apport_sandbox_iquL81/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1676592,2017-10-23 14:52:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676600,2018-02-27 16:46:08 UTC,Tested on EG 3.0.2.
1676611,2017-03-27 20:50:07 UTC,"Also, changing the path fill fixes the problem."
1676611,2020-03-02 12:13:37 UTC,I could not replicate this issue in 0.92.0 r15299 (Windows 10) with the given file.
1676614,2019-10-01 22:30:35 UTC,I believe this issue has been addressed now. I remember there was a case when the missing GL directories were not created automatically but this has been long fixed.
1676640,2017-03-28 03:24:20 UTC,Tested an install on another machine that did have python-pip installed before I installed 1.91. Same issue.
1676640,2017-03-29 08:58:25 UTC,"We use distutils for setup.py, which does not do dependancy resolution. If you're using setup.py you're expected to be able to figure these out yourself. Perhaps a list of expected dependancies can be added to the INSTALL file."
1676642,2018-02-21 15:42:53 UTC,"I encountered the same problem: no release file, impossible to install FreeFileSync via ppa."
1676655,2017-04-11 18:42:39 UTC,https://review.opencontrail.org/#/c/30296/ will fix this issue as well.
1676655,2017-03-27 22:15:09 UTC,"-rwxrwxrwx 1 chhandak epbg 2564010 Mar 27 15:13 contrail-kube-manager.log
-rwxrwxrwx 1 chhandak epbg  188727 Mar 27 15:13 contrail-kube-manager-stdout.log
ubuntu-build04:/auto/cores/1676655> pwd
/auto/cores/1676655"
1676666,2018-05-08 18:04:56 UTC,This change was made by a bot.
1676666,2021-01-07 04:12:08 UTC,4.8 EOL
1676672,2017-03-28 22:18:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/451095"
1676672,2017-06-19 16:38:40 UTC,"Change abandoned by Felipe Monteiro (<email address hidden>) on branch: master
Review: https://review.openstack.org/451095"
1676672,2018-01-12 19:03:36 UTC,Unassigning due to no activity for > 6 months.
1676672,2018-09-11 16:58:04 UTC,Looks like accept_transfer is documented now?
1676675,2020-05-22 13:41:47 UTC,Fixed in bionic and later.
1676684,2018-01-13 00:02:38 UTC,Me too. As above.
1676684,2018-01-12 20:58:25 UTC,I am experiencing this bug too [0].
1676684,2018-01-12 09:48:53 UTC,"As discussed in the Snapcraft forum thread that @cratliff referred to above, here's a very simple snapcraft.yaml which leads to something similar to the above-mentioned permission error. Namely, during snap creation the install script attempts to chmod /lib/x86_64-linux-gnu/libnss_compat.so.2, via a symlink from <buildpath>/parts/my-part/install/usr/lib/x86_64-linux-gnu/libnss_compat.so."
1676684,2018-01-11 19:24:50 UTC,"Thank you Chris, I'll take a look."
1676684,2017-11-09 12:16:36 UTC,"Just run into the same problem when including ""portaudio19-dev"" as a stage-package:"
1676684,2018-01-11 18:40:43 UTC,"I'll set back to invalid, then."
1676684,2017-12-08 09:52:02 UTC,"Upon further reflection (& searching), it turns out my issue was that I was trying to build a snap in 17.10 instead of 16.04. See here for the ""why"": https://forum.snapcraft.io/t/troubles-with-running-iproute2-inside-a-snap/2987 for more info. This is no longer an issue for me when using 16.04."
1676684,2017-12-05 20:34:44 UTC,"I seem to have this same issue.
My snapcraft.yaml, relevant portion:"
1676684,2017-11-20 22:30:37 UTC,"I cannot duplicate with the YAML provided in the description, so I suspect this is no longer an issue. Please change the status if you run into it again."
1676684,2018-01-11 19:10:02 UTC,"I was mistaken in the related forum post. https://forum.snapcraft.io/t/use-of-sudo-when-building-snaps/3478/13  The issue is with the apt package it was just an apt package required for a python part.  This is requiring me to run snapcraft with sudo, but otherwise doesn't seem to cause any issues."
1676692,2017-04-17 23:32:04 UTC,Additional information
1676695,2017-04-03 11:46:31 UTC,Please provide diagnostic snapshot.
1676702,2020-05-27 20:57:32 UTC,"I have the same problem. Take a Break starts up correctly, runs for the work period plus about a minute, then does a 180 on the screen but never returns from the break. Same deal on Dim Screen."
1676709,2020-05-21 06:57:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676712,2017-03-28 04:18:04 UTC,I've also seen the same issue (but less frequently) with neutron.
1676712,2017-10-03 18:33:20 UTC,"We see this frequently with neutron, any update on root cause?"
1676712,2018-09-05 09:10:18 UTC,Meets the same issue in our jenkins CI ut job.
1676712,2018-10-05 14:30:27 UTC,This seems to be occurring more frequently and is getting painful. We might consider running tests sequentially.
1676731,2017-05-01 17:04:40 UTC,This bug has been fixed already with https://review.openstack.org/#/c/436400
1676731,2020-04-02 12:29:02 UTC,Part of tempest since 16.1.0 release.
1676731,2017-04-12 07:47:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456101"
1676731,2017-05-01 01:48:06 UTC,"Change abandoned by Maho Koshiya (<email address hidden>) on branch: master
Review: https://review.openstack.org/456101"
1676736,2017-07-24 08:17:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676738,2017-03-28 07:26:10 UTC,Can you please attach th screenshots?
1676745,2018-02-13 11:24:07 UTC,This bug should be opened against https://bugs.launchpad.net/networking-generic-switch.
1676755,2017-03-28 14:34:25 UTC,"Reviewed:  https://review.openstack.org/450602
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-lma-collector/commit/?id=b5a12ffbfa4ce1c482969c2d8f2948e416263d32
Submitter: Jenkins
Branch:    master"
1676755,2017-03-28 15:24:54 UTC,"Fix proposed to branch: stable/1.0
Review: https://review.openstack.org/450850"
1676755,2017-03-29 07:47:20 UTC,"Reviewed:  https://review.openstack.org/450850
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-lma-collector/commit/?id=02f862ad499098c2a71106e78eba337460f12693
Submitter: Jenkins
Branch:    stable/1.0"
1676760,2017-03-28 23:07:20 UTC,Finally home.
1676760,2017-03-28 14:26:35 UTC,"Très bien je regarde avec le terminal, merci pour les réponses, à très vite."
1676760,2017-03-28 08:39:49 UTC,Il nous faut alors le résultat des commandes ci-dessus pour déterminer la cause du crash.
1676760,2017-03-28 08:36:26 UTC,"J'imagine que vous utilisez la dernière version : elementary OS Loki.
lorsque ceci se produit, pouvez-vous garder un terminal ouvert et entrer la commande ""wingpanel"".
Si celui-ci crash, alors pouvez-vous entrer ""gdb wingpanel"" puis ""run"" puis ""backtrace"".
Si celui-ci est gelé, alors appuyez sur ""Ctrl + C"" puis entrez la commande ""wingpanel -g"""
1676760,2017-03-28 09:26:11 UTC,"My French kinda sucks, but from what I can understand I have the same issue. Wingpanel seems to crash when I try to open its calendar
Interestingly, maya also crashes when I try to open it. When I get home I'll try to get some sort of log or back trace from it."
1676763,2020-01-08 15:33:25 UTC,"Thanks Jakub for the debugging work you put there and the fixes! I've upload now those changes to the current 'focal' Ubuntu serie (tweaking a bit the packaging, I merged the fixes in the patch doing the rewrite in C rather than stacking patches)"
1676763,2019-12-29 22:05:38 UTC,"This is a debdiff for Bionic applicable to usb-modeswitch_2.5.2+repack0-2ubuntu1. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended."
1676763,2019-12-29 23:21:57 UTC,The two patches inside the debdiff fix these bugs:
1676763,2020-01-08 17:30:39 UTC,This bug was fixed in the package usb-modeswitch - 2.5.2+repack0-2ubuntu2
1676763,2020-07-10 18:08:27 UTC,"As a reminder, the file"
1676763,2020-07-05 13:32:42 UTC,I've made an attempt to fix the problem of interfaces missing in the original Tcl wrapper. I intend to release 2.6.1 soon.
1676763,2020-07-05 20:04:39 UTC,"FTR, uploaded 2.6.0-3 to Debian/unstable with the patch mentionned by @digidietze."
1676763,2020-07-09 09:14:57 UTC,"Thank you, I've tested the fix and it mostly works. However, a minor fixup is needed for flawless switching of this particular modem, see https://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=2&t=2915#p19606"
1676763,2020-07-10 18:04:51 UTC,I have released upstream version 2.6.1 which includes the fixes for recently reported problems.
1676763,2019-12-29 20:23:21 UTC,"The attachment ""debian patch against usb-modeswitch_2.5.2+repack0-2ubuntu1"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1676763,2020-07-02 12:43:31 UTC,"@Jakub, the change you proposed while fixing the segfault is creating issues for other users as description there"
1676763,2019-12-29 20:17:59 UTC,The patch for bionic should be applicable to focal as well (current development branch; currently reading https://wiki.ubuntu.com/StableReleaseUpdates ).
1676763,2019-12-29 15:04:16 UTC,I have realized that these are two different issues.
1676763,2019-12-29 18:21:06 UTC,Thanks!
1676763,2017-03-28 07:54:22 UTC,"StacktraceTop:
 strrchr () at ../sysdeps/x86_64/strrchr.S:32
 main (argc=<optimized out>, argv=<optimized out>) at usb_modeswitch_dispatcher.c:769"
1676763,2017-03-29 10:54:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676763,2019-12-29 20:12:53 UTC,"I am sorry for uploading the patches multiple times, I wanted them to be clean (i.e. patches ending with .patch, having consistent directory versions, etc)"
1676763,2019-12-25 14:00:20 UTC,"Ah, it starts to make sense. usb_modeswitch_dispatcher is called correctly, but it cannot find interface 0 on the device to be switched. However, dmesg contains warning about the same thing:"
1676763,2019-12-25 14:14:47 UTC,"I think that upgrading the modem firmware (I have Sierra Wireless EM7305) might help, but that does not fix the underlying bug / broken assumptions."
1676763,2019-12-25 12:39:49 UTC,Very similar crash happens to me on Bionic as well. So far it seems to me that usb_modeswitch_dispatcher is called incorrectly and therefore it crashes when it eventually encounters a NULL pointer.
1676763,2019-12-25 15:25:42 UTC,"EDIT: the null-pointer bug only exists in Ubuntu, the interface error bug may exist in upstream as well."
1676763,2019-12-25 15:47:56 UTC,I have tried installing the package from Buster. That has resolved the crash - the program ended gracefully. However the underlying problem is still there - devices without interface 0 will not work. I think this is present in upstream as well.
1676763,2019-12-25 16:34:39 UTC,Upstream bugreport: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=2&t=2915
1676763,2019-12-29 16:52:49 UTC,Thanks for the thorough analysis!
1676763,2019-12-25 15:15:05 UTC,"Hmmm, it seems that this bug exists *only* in Ubuntu and not in Debian. Ubuntu source package contains a patch that rewrites the usb_modeswitch_dispatcher program from Tcl to C. While there must have been good reasons to do this, there is at least one more bug in the rewritten version."
1676770,2018-08-12 15:41:14 UTC,Good idea.  I think this would be better added by users who want this by installing the tmux-resurrect plugin.
1676771,2017-06-30 10:17:13 UTC,Thank you for the report.
1676771,2018-01-18 08:35:35 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1189
1676781,2017-03-28 09:21:09 UTC,"Epilogue: Eventually I took my courage in my 2 hands, and did a  syncevolution -s refresh-from-remote AEV aev"
1676784,2017-04-01 02:06:08 UTC,"@Ryan Chen (yiheqilin):
hi, there is an option 'observe_on_update', I think the problem wont happen if we set the option observe_on_update=True."
1676784,2018-02-07 22:54:00 UTC,"You can do ""stack resource mark unhealthy"" to tell Heat that the resource needs to be removed, or you can do ""stack check"" to get Heat to check for this itself. Also, even if you hit this problem a subsequent update will succeed (i.e. the FAILED resource will be replaced)."
1676784,2017-03-31 06:18:01 UTC,"No matter if enable convergence, we also have this problem in legacy.
The error instance not found raised when resize, so let's think of a way to fix this case."
1676784,2017-03-28 09:06:26 UTC,the openstack release is: newton
1676805,2017-11-22 16:33:59 UTC,"Try this patch:
https://lists.amavis.org/pipermail/amavis-users/2017-November/005115.html"
1676805,2017-03-29 05:42:19 UTC,"OK, this is not real fix, but it fixes things for me, because I use utf8..."
1676805,2017-11-25 16:27:31 UTC,I see this as upstream bug too.
1676805,2017-11-25 16:20:30 UTC,"Serge, thank you!"
1676805,2017-11-24 10:35:47 UTC,"Note: I just meregd 2.11.0 for the next Ubuntu release, so patches against that are fine to get things started - but should have some sort of upstream backing to not end up as maintenance dept."
1676805,2017-11-27 06:44:57 UTC,"Thank you both, let us know if there is any response."
1676805,2017-11-23 17:11:09 UTC,"Sure it is correct.
Sorry, the patch is for the current latest stable amavisd-new-2.11.0."
1676805,2017-11-23 04:51:09 UTC,"Serge, in this procedure I have
 $s = safe_encode_utf8($s)  if $n eq 'log_templ' || 'log_recip_templ';
i.e. not safe_encode_utf8_inplace
is it correct to change it to
safe_encode_utf8($s) if $n eq 'log_templ' || $n eq 'log_recip_templ';"
1676805,2017-11-22 18:53:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676805,2017-11-24 10:32:40 UTC,"Hi sles,
as with your other bug (so mostly the same answer) I appreciate taking the time to report this bug and helping to make Ubuntu better. I like the pre-debug and change suggestions and I'm sure it'll be helpful to others experiencing the same issue."
1676810,2017-04-03 22:01:59 UTC,Please note that bug 1666318 has relevant information. It appears that editing
1676810,2017-04-03 22:11:05 UTC,And the bug #1676081 also has relevant information toward VPN connections:
1676810,2017-04-03 21:44:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676814,2017-03-28 10:05:31 UTC,"To keep these on the canvas should be relatively straightforward, as they /are/ EDA_ITEMS at heart. Hower saving into files would have to be a format bump. The item description should be pretty simple, perhaps just:"
1676814,2017-03-28 14:14:01 UTC,"There already is a ""persistent ruler"" object, dimensions. It would be nice if those could be improved/replaced. Their implementation right now is pretty wonky, numbers don't update automatically unless you move the endpoints, units and numerical precision cant be forced and there is only one style (parallel linear). Also, in GAL, the text can't be moved away from the dimension and there is no way to make it use external arrows for small dimensions."
1676814,2017-03-28 15:33:35 UTC,"I guess the question here is how much overlap there should be between the dimension items (permanent ""drawing"" items that can go on real layers) and ruler overlays that are on the special GAL overlay layer, and aren't really part of the PCB."
1676814,2017-03-31 14:52:47 UTC,"Technically, rulers are not really part of the board.  They have no meaningful output required for fabrication.  It might be worth exploring saving them as properties which would (should?) not require a change in the board file format.  I would like to keep board file objects confined to board fab requirements if possible."
1676814,2019-04-27 13:34:07 UTC,"Something very difficult. Just make sure that the measuring tool works in the same way as Highlight Net. You can add the ability when you can draw several roulettes instead of one. The first pressing of the Esc key disables the measuring tool, the second pressing clears the canvas on the drawn rulers. Pretty simple and practical. I also opened a similar report #1826637 with the proposal of such a simpler implementation and quite convenient to use."
1676818,2017-11-02 16:01:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676826,2017-03-28 10:53:55 UTC,"Media-hub shouldn't be required for stutter-less playback, we can't preinstall the codec anyway."
1676827,2017-04-05 17:13:21 UTC,"This is correct, the string is a little bit confusing, even though it's deprecated because we don't want to need this thing soon, it's still needed. Maybe update the string to be more clear?"
1676827,2019-09-17 07:09:46 UTC,"This was fixed in Stein when the worker was enabled by default. It will however still log the deprecated warning if enabled is set in the configuration, but that is no longer required for the worker to function."
1676829,2017-05-30 19:48:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676829,2017-06-19 05:54:12 UTC,Same thing happens to me everytime I am on a conference call on any videochat app on/off any browser.
1676829,2017-12-01 08:41:09 UTC,"Confirmed, except for me it always resets to 100%. That's far too high, I need it to be around 50% or so. Either way, the resetting is very annoying."
1676829,2017-12-01 08:44:10 UTC," properties:
  alsa.card = ""0""
  alsa.card_name = ""HDA Intel PCH""
  alsa.long_card_name = ""HDA Intel PCH at 0xf4340000 irq 142""
  alsa.driver_name = ""snd_hda_intel""
  device.bus_path = ""pci-0000:00:1f.3""
  sysfs.path = ""/devices/pci0000:00/0000:00:1f.3/sound/card0""
  device.bus = ""pci""
  device.vendor.id = ""8086""
  device.vendor.name = ""Intel Corporation""
  device.product.id = ""a171""
  device.form_factor = ""internal""
  device.string = ""0""
  device.description = ""Built-in Audio""
  module-udev-detect.discovered = ""1""
  device.icon_name = ""audio-card-pci"""
1676839,2020-11-20 04:17:19 UTC,[Expired for pluma (Ubuntu) because there has been no activity for 60 days.]
1676839,2017-03-28 11:41:33 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f4cc07c23a8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=0x3, ptr=<optimized out>, str=0x7f4cc07c27d8 ""malloc(): smallbin double linked list corrupted"", action=3) at malloc.c:5046
 _int_malloc (av=av@entry=0x7f4cc09f5b00 <main_arena>, bytes=bytes@entry=32) at malloc.c:3421
 __GI___libc_malloc (bytes=32) at malloc.c:2925
 __GI___libc_realloc (oldmem=0x0, bytes=32) at malloc.c:3008"
1676842,2017-03-28 11:36:50 UTC,I have included both the ElementaryOS and Linux Mint teams in this bug report because the Checkbox app affects them as well.
1676842,2018-11-04 15:55:58 UTC,Can you provide the versions of the checkbox packages by posting the output of the following:
1676845,2017-06-27 15:24:48 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1676845,2017-05-10 15:17:57 UTC,This bug was fixed in the package opentk - 1.1.4c+dfsg-2ubuntu0.16.04.1
1676845,2017-05-10 15:17:55 UTC,This bug was fixed in the package vlc - 2.2.2-5ubuntu0.16.04.2
1676845,2017-05-10 15:17:11 UTC,16:16 <tjaalton> rbasak: it works
1676845,2017-05-10 15:15:06 UTC,"16:13 <rbasak> tjaalton: for bug 1676845, wouldn't it be appropriate to check that vlc still actually works?
16:13 <rbasak> Similarly opentk.
16:14 <rbasak> arges, bdmurray: ^"
1676845,2017-05-04 21:07:57 UTC,"Hello Timo, or anyone else affected,"
1676845,2017-04-27 16:29:36 UTC,xenial was
1676845,2017-04-26 08:43:08 UTC,"vlc and libopentk1.1-cil can now be installed with ppa:ubuntu-x-swat/updates enabled, thanks"
1676845,2017-04-05 13:29:39 UTC,"Hello Timo, or anyone else affected,"
1676845,2017-03-28 11:36:53 UTC,fixed in zesty
1676845,2017-03-28 11:40:33 UTC,opentk fixed in zesty
1676845,2017-04-27 16:09:14 UTC,Flipped the tag back to v-needed since its not clear what release was tested.
1676845,2017-04-05 13:27:33 UTC,"For the yakkety upload I see an ffmpeg-2-8-10 directory was added, can you fix and reupload?"
1676845,2017-04-05 13:29:06 UTC,"Hello Timo, or anyone else affected,"
1676845,2017-04-05 13:26:13 UTC,"Hello Timo, or anyone else affected,"
1676849,2017-03-28 12:01:32 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/450741"
1676849,2017-03-28 15:46:34 UTC,"Reviewed:  https://review.openstack.org/450741
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=e3acbeea4110e2c6c6198b9d8d5851a9cd8f745e
Submitter: Jenkins
Branch:    stable/newton"
1676850,2017-04-02 19:14:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676851,2017-04-22 05:37:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676854,2017-03-28 14:04:45 UTC,"works after restart, probably something broke along the way but restarting seems to fix it"
1676854,2017-05-28 04:18:22 UTC,[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]
1676860,2017-03-28 14:19:39 UTC,"sometimes the About window shows in Launcher list even when the app is closed, see attached screenshot (sol). but not always (random behaviour)"
1676864,2019-09-23 13:59:11 UTC,"Being a feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1676864,2017-03-28 12:52:32 UTC,"Power parameters are accessed via the system id so given that you have the machine description, I'm not really sure this would speed things up."
1676864,2017-03-28 13:27:06 UTC,"I'm sorry, I forgot to add the use case part."
1676864,2019-09-19 12:03:17 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1676864,2019-09-19 13:07:17 UTC,"@adam-collard, this is a feature request, not an issue that is should expire after 6 months. If you do not want to implement this feature than that is fine, but please say so."
1676871,2017-04-06 09:31:06 UTC,"Hello, mentioned fix blocked by spec patch for oslo.messaging.kafka https://review.fuel-infra.org/#/c/32761/ and will be commited after specs merge."
1676871,2017-04-03 14:43:45 UTC,https://review.fuel-infra.org/#/c/32646/1
1676874,2017-03-31 05:20:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676879,2017-04-04 06:40:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676879,2017-04-04 06:44:56 UTC,"same with kmines when you change dificulty level, see attached"
1676879,2017-04-04 09:18:43 UTC,"hmm.. in Qupzilla the Preferences window si broken, Edit \ Preferences, also it opens beneath  the launcher/top bar at [0,0]"
1676879,2017-04-05 08:03:48 UTC,"There's no clear steps to reproduce, so I may have missed something. But I can't get these symptoms with miral-app."
1676880,2017-03-28 13:58:10 UTC,It might be better to display them but disabled since there would be no effect if you do change them.  We'll discuss this.
1676880,2017-03-30 15:53:10 UTC,"The design guidelines I wrote for disabling vs. hiding controls <https://goo.gl/1ZnLyk> (Canonical-only link, sorry):
————————————
In general, you should *disable* a control if it is unusable or irrelevant to the current situation, but there is something the user could reasonably do to make it usable/relevant — for example, changing the value of another control, selecting something, or connecting to the Internet."
1676889,2017-03-29 16:25:52 UTC,"After further investigation the root cause has been determined. Juju is failing to spin up LXD containers on the machines, resulting in a timeout. This has been reported against Juju: https://bugs.launchpad.net/juju/+bug/1677265"
1676902,2017-04-06 13:36:06 UTC,"Thanks gordon! I still think that those parameters should be mandatory or if you use needed_overlap 0 it should return all the points. And yes, this needs to be documented."
1676902,2017-03-28 20:24:15 UTC,It is not clear which is the expected result when start and stop are not specified. I though all results should be included because not filter is applied but it was not the case.
1676902,2017-03-28 19:59:39 UTC,"not sure if this matters to your use case, but you can backfill values so it doesn't omit results."
1676902,2017-03-28 22:45:29 UTC,"tbh, it's not obvious. i think this needs to be documented"
1676904,2017-04-04 13:37:35 UTC,"Another scenario:
            1. Create new environment with VLAN segmentation for Neutron
            2. Add controller and compute nodes"
1676905,2017-03-28 16:03:54 UTC,"This is almost certainly not a Mailman bug per se. Hostgator (or you if you have access) needs to examine the web server logs to see what's logged for the 500 error. Since it affects every Mailman CGI, it is probably related to permissions or possibly a group mismatch error <https://wiki.list.org/x/4030645>."
1676907,2017-08-19 16:24:05 UTC,"Not going to create a new history item for every variant, that would get messy very quickly, and using double-height items makes for a very ugly UI regardless of any wxDV_VARIABLE_LINE_HEIGHT slowness. Think I'll just make each history item remember the last modifications made to it. Should be able to implement that pretty quickly, so I'll do that and post a patch for testing so I can get people's opinions on it."
1676911,2019-09-19 12:03:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1676911,2019-09-19 16:03:40 UTC,I agree this would be nice to have.
1676911,2020-04-02 12:48:44 UTC,"This is a valid request, but we now track feature requests at https://discourse.maas.io/c/features, and not in the LP bug tracker."
1676912,2018-03-13 02:55:03 UTC,I haven't tried 4.16 but it is present in mainline 4.15.8
1676912,2018-02-13 16:27:19 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1676912,2019-10-03 10:39:53 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1676912,2019-05-02 20:20:30 UTC,Exact same problem here with Ubuntu 18.04 and kernel Linux 4.18.0-16-generic.
1676912,2017-09-06 21:56:45 UTC,"fwiw, this has been happening to my laptop for a couple months (i just now had the time to look into the logs). i've had the laptop for a year (samsung ativ book 9) without problems before this."
1676912,2018-02-15 12:39:50 UTC,"Also v4.16-rc1? If it still happens to latest mainline kernel, then we need to bisect to the bad commit and report the issue upstream."
1676912,2017-08-03 14:45:56 UTC,"Same issue with kernel 4.9+ on a Macbook Pro on suspend from resume, either with lid or suspend from shutdown menu."
1676912,2017-09-06 03:41:16 UTC,I have the same issue on an MSI GS70 running kernel 4.10.0-33.
1676912,2017-03-29 06:00:11 UTC,This change was made by a bot.
1676912,2017-03-29 16:38:09 UTC,This problem also appears whenn using Kernel 4.11 from the mainline ppa.
1676912,2018-02-14 02:17:34 UTC,"Yea except ""4.9+"" meant it was still present in 4.10 (and 13 as well)"
1676912,2017-05-19 05:45:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676912,2017-03-30 04:49:24 UTC,"I had some similar suspend/resume issues when trying mainline Kernels in 16.04. Every Kernel since 4.9 would cause terribly slow system after resuming.
I will test Kernel 4.8 in next days to see if this problem is present there too."
1676914,2017-03-28 15:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1676916,2019-05-23 16:21:21 UTC,chris i think this is fixed or did i understand the report wrongly?
1676916,2019-07-14 22:19:45 UTC,"I'm setting this to ""Won't Fix"" since the blocking issue has been set to ""Won't Fix""."
1676931,2017-04-03 12:31:02 UTC,"Fix committed into lp:unity-system-compositor at revision 311, scheduled for release in unity-system-compositor, milestone Unknown"
1676947,2018-08-08 23:12:54 UTC,"This could work as the video, allowing that the line extremes not be necessary align
https://www.youtube.com/watch?v=yb9Z4ZsZm5M"
1676953,2017-03-30 16:55:29 UTC,I attached the last one. Encountered just before the finish installing updates with Software Updater.
1676953,2017-04-04 17:27:31 UTC,Once again after kernel update.
1676953,2017-06-29 15:33:24 UTC,Again after kernel update.
1676954,2017-03-28 16:55:49 UTC,"StacktraceTop:
 atspi_accessible_get_parent (obj=obj@entry=0x55b91d134ab0, error=error@entry=0x0) at atspi-accessible.c:276
 atspi_accessible_get_application (obj=0x55b91d134ab0, error=<optimized out>) at atspi-accessible.c:687
 ffi_call_unix64 () from /tmp/apport_sandbox_ktBAiQ/usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /tmp/apport_sandbox_ktBAiQ/usr/lib/x86_64-linux-gnu/libffi.so.6
 pygi_invoke_c_callable () from /tmp/apport_sandbox_ktBAiQ/usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so"
1676954,2017-03-31 11:54:51 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1676964,2017-05-22 09:25:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676967,2017-12-15 05:21:12 UTC,"I met the same question in Pike. If config to store raw info, and contain '.' in raw, mongodb will raise exception."
1676967,2017-03-30 13:21:21 UTC,are you storing raw events?
1676967,2017-06-29 19:02:32 UTC,changing this to panko as it's more related to storage...
1676975,2017-03-28 21:48:03 UTC,"Yep, there's a daily cron job that's sometimes timing out on earlier exports and thus crashing.  I'm trying to get its debug level cranked up so that we can get a better handle on exactly what we need to optimise."
1676975,2017-06-26 20:51:14 UTC,I believe we have the same problem with https://translations.launchpad.net/josm
1676977,2018-02-27 12:36:02 UTC,"Hummm, apparently Canonical is using the let's-wait-until-the-Ubuntu-version-mentioned-in-the-bug-report-gets-EOL-so-we-can-close-the-bug-without-fixing-anything"" method for closing bug reports..."
1676977,2018-03-02 14:37:23 UTC,I'll try to get 17.04 up somewhere and test that as well.
1676977,2018-03-02 14:36:43 UTC,"The ldapi:/// worked just fine, as did ldap:// with an IP or a name. And I don't have an entry in /etc/hosts for the ldap server, I'm really using DNS. Reboot works just fine, login prompt, and I can login at the console (and via ssh) with an ldap user."
1676977,2018-03-02 13:27:40 UTC,"ldapi:/// is a unix socket connection, it shouldn't have a ""name"" or IP component. It can optionally take a path component, but usually should just be left blank."
1676977,2018-03-02 12:49:31 UTC,I'm taking a look.
1676977,2018-02-27 13:15:08 UTC,Re-opening. This issue is apparently not version specific.
1676977,2018-02-27 08:02:59 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1676977,2017-04-25 22:28:30 UTC,"For what it's worth, the same version of libpam-ldap has been present in Ubuntu since (at least) 15.04. So I don't think the bug is in libpam-ldap."
1676977,2017-04-26 15:01:24 UTC,I have just tested 17.04. The issue remains unchanged. It's not fixed.
1676977,2017-04-26 14:37:14 UTC,I also believe that this issue is related to systemd. I filed this issue on libpam-ldap because I don't know exactly which systemd service might be wrong and so don't know exactly what package exactly should be changed.
1676977,2017-04-25 22:35:59 UTC,"If you are dropped to an emergency shell on failure to boot, does name resolution period work?"
1676977,2017-04-25 22:32:54 UTC,"Finally, is this reproducible with 17.04? Note that 16.10 goes eol in about 3 months so there is some non-zero cost to trying to fix it there, if it's already fixed in 16.10."
1676977,2017-04-25 22:30:51 UTC,"Almost certainly the issue is that login.service is not waiting for networking before starting, when ldap is configured."
1676977,2017-03-29 19:38:44 UTC,"""Would it be possible for you to give an example configuration to help us
reproduce this issue?"""
1676977,2017-03-29 16:32:35 UTC,Thank you for taking the time to file a bug report.
1676977,2017-04-26 15:17:04 UTC,Thank you for the prompt testing. I'm marking a few potential src packages where the actual issue might lie.
1676980,2017-03-28 18:23:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1676980,2017-05-16 15:37:46 UTC,"For what it's worth, I installed libepoxy0 (1.3.1-1ubuntu1) from zesty manually by downloading the right deb for my architecture (https://packages.ubuntu.com/zesty/libs/libepoxy0), and then installing with ""dpkg -i"". It seems that the newer package in zesty has a fix for the bug you referenced."
1676989,2019-12-20 10:29:54 UTC,"Reviewed:  https://review.opendev.org/451933
Committed: https://git.openstack.org/cgit/openstack/oslo.config/commit/?id=ec84eeda526adc20dcabdf6e704958cc06773dd3
Submitter: Zuul
Branch:    master"
1676989,2019-12-20 10:33:00 UTC,"Reviewed:  https://review.opendev.org/451947
Committed: https://git.openstack.org/cgit/openstack/oslo.config/commit/?id=18d1617caa5a7380e2298b1e647ef110c9d574be
Submitter: Zuul
Branch:    master"
1676989,2017-03-30 18:52:00 UTC,"Change abandoned by Dolph Mathews (<email address hidden>) on branch: master
Review: https://review.openstack.org/450928
Reason: Superceded by https://review.openstack.org/#/c/451947/"
1676989,2018-10-12 17:54:13 UTC,"Reviewed:  https://review.openstack.org/450956
Committed: https://git.openstack.org/cgit/openstack/oslo.config/commit/?id=b5f76a2ce8323ae89e85b599c2aec5a89a49eabd
Submitter: Zuul
Branch:    master"
1676989,2017-03-30 18:51:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/451947"
1676989,2017-03-28 19:51:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/450956"
1676989,2017-03-28 18:55:31 UTC,There's two issues with that one StrOpt that I've identified.
1676989,2017-03-28 18:52:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/450928"
1676996,2017-03-28 21:45:16 UTC,The actual dependency is:
1676996,2017-03-29 13:39:44 UTC,"Great, thanks for looking into this!"
1677006,2017-03-28 19:30:26 UTC,Unfortunately (?) I don't see this doing the same thing on my xenial host.  is it repeatable?  that would help a lot ... please don't destroy the state if it is!
1677006,2017-03-29 05:59:18 UTC,It is repeatable.
1677006,2017-03-29 06:17:06 UTC,Closer!
1677006,2017-04-01 05:47:18 UTC,And definitiv a bug in DIB:
1677014,2017-05-05 22:11:06 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1677014,2017-03-28 19:55:54 UTC,"StacktraceTop:
 g_sequence_iter_get_sequence () from /tmp/apport_sandbox_v0EX7z/lib/x86_64-linux-gnu/libglib-2.0.so.0
 iter_is_valid (iter=0x55992003f2e0 <iter>, list_store=0x559921645640) at ././gtk/gtkliststore.c:396
 append_metadata_array (messageIter=messageIter@entry=0x7ffcf4d01a00) at mpris-interface.c:59
 mpris_send_signal_Updated_Metadata () at mpris-interface.c:1222
 g_closure_invoke () from /tmp/apport_sandbox_v0EX7z/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1677015,2017-03-30 20:55:18 UTC,"Yes, that feature is definitely coming somehow."
1677015,2017-03-30 21:31:05 UTC,Issue being discussed here:
1677015,2019-06-28 18:59:37 UTC,"If I understand correctly, this bug can probably closed now with the introduction of `connections` stanza in the gadget.yaml which does exactly this"
1677019,2017-04-14 19:08:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677019,2017-04-14 19:10:53 UTC,This affects me to having just upgraded 16.10 to the released version of 17.04.
1677024,2017-12-06 22:46:30 UTC,I have the same issue running elementary OS 0.4.1 Loki using dual external monitors via display port connected to a hp docking station.
1677031,2017-03-29 00:37:19 UTC,It looks like the ssl's problem. And I have no this site-package of `/usr/local/lib/python2.7/dist-packages/OpenSSL` in my local.
1677034,2017-03-28 20:32:51 UTC,"Forgot to mention, this was observed with the 16.04.1 and .2 desktop amd64 isos."
1677037,2018-03-07 22:14:07 UTC,Alternatively base the hash on:
1677037,2018-03-07 22:18:46 UTC,"Sorry, hash was meant to be <file name without the path>, so given the ppt: c:\temp\test.ppt is 23456 bytes in size and last edited on the first second of 1 Jan 2018 the hash would be:"
1677040,2020-03-22 23:22:40 UTC,"Exposing that config also implies we need to ensure the org exist.
To make the logic simple, can we just ensure Main Org exists?
As I known, there are also other functions assume the Main org exist in charm."
1677058,2017-12-19 10:29:53 UTC,I see this with lightdm-gtk-greeter 2.0.3 on Gentoo. It appears that this crash happens when the hostname changes between lightdm start and login.
1677058,2017-12-19 10:34:42 UTC,"I hit ""post"" a bit too soon."
1677066,2017-03-29 01:32:48 UTC,Invalid for Xmir. Libertine depends on Xmir and not vice-versa.
1677072,2017-03-29 01:04:50 UTC,"The same issue can be triggered if you hold the super key to reveal the launcher and then click on an application icon, or if you use any of the super+1/2/3/etc. short cuts to launch an application."
1677072,2017-03-29 01:37:48 UTC,"Could be related to Mir bug 1536279, which has not been Fix Released yet."
1677077,2017-03-29 01:42:25 UTC,Just found out what is going on (immediately after posting this bug -- figures).
1677077,2018-03-25 08:53:58 UTC,No response in nearly a year. This is extremely frustrating.
1677079,2017-03-29 01:25:39 UTC,Potential fix here: https://github.com/snapcore/dragonboard-gadget/pull/4
1677082,2017-10-19 10:21:42 UTC,Fixed in upstream versions 5.4+ and debian-testing
1677126,2017-04-13 21:02:13 UTC,"The verification of the Stable Release Update for lttng-modules has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1677126,2017-04-13 21:12:13 UTC,This bug was fixed in the package lttng-modules - 2.8.0-1ubuntu1~16.04.2
1677126,2017-04-06 07:42:56 UTC,Tested lttng-modules 2.8.0-1ubuntu1~16.04.2 on xenial with kernel 4.4.0-72-generic #93 with the kernel team autotest client tests ubuntu_lttng_smoke tests and it passed.
1677126,2017-05-15 09:00:24 UTC,"For comment #13 and #14, Colin had a look on this, and it can't be reproduced."
1677126,2017-05-08 08:22:02 UTC,"Hello Colin,"
1677126,2017-04-05 22:46:11 UTC,"Hello Po-Hsu, or anyone else affected,"
1677126,2017-05-10 12:24:41 UTC,I believe this is a different issue. Can you create a new bug report and assign that to me. Thanks.
1677126,2017-04-05 14:20:40 UTC,Tested with 4.10.0-15 on Zesty zKVM
1677126,2017-04-05 13:14:25 UTC,"Colin,
Can you confirm that lttng-modules in zesty (2.9.0-1ubuntu1) works with the 4.10 kernel?
Thanks"
1677126,2017-03-29 08:59:06 UTC,"$ cat /var/lib/dkms/lttng-modules/2.8.0/build/make.log
DKMS make.log for lttng-modules-2.8.0 for kernel 4.10.0-14-generic (x86_64)
Wed Mar 29 08:57:24 UTC 2017
make: Entering directory '/usr/src/linux-headers-4.10.0-14-generic'
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-ring-buffer-client-discard.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-ring-buffer-client-overwrite.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-ring-buffer-metadata-client.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-ring-buffer-client-mmap-discard.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-ring-buffer-client-mmap-overwrite.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-ring-buffer-metadata-mmap-client.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-clock.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-events.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-abi.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-probes.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-pid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-procname.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-prio.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-nice.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-vpid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-tid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-vtid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-ppid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-vppid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-cpu-id.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-interruptible.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-need-reschedule.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-calibrate.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-hostname.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/wrapper/random.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/probes/lttng.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/wrapper/trace-clock.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/wrapper/page_alloc.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-tracker-pid.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-filter.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-filter-interpreter.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-filter-specialize.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-filter-validator.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/probes/lttng-probe-user.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-syscalls.o
  CC [M]  /var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-perf-counters.o
/var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-perf-counters.c: In function ‘lttng_destroy_perf_counter_field’:
/var/lib/dkms/lttng-modules/2.8.0/build/lttng-context-perf-counters.c:102:2: error: implicit declaration of function ‘..."
1677126,2017-03-29 08:56:43 UTC,"Oops, wrong log. Here is what I meant to paste:"
1677126,2017-04-05 14:55:07 UTC,Tested Zesty lttng-modules 2.9.0-1ubuntu1 on 4.10.0-15-generic #17 with ubuntu_lttng_smoke_test from the ubuntu autotest client tests. Passed OK. Looks good to me.
1677126,2017-03-29 08:55:53 UTC,sudo /usr/bin/lttng-sessiond -vvv shows us the cause:
1677126,2017-03-29 08:38:52 UTC,For references: http://kernel.ubuntu.com/testing/4.10.0-14.16~16.04.1-generic/ubuntu_lttng_smoke_test-4.10.0-14.16~16.04.1-amd64-index.html
1677128,2017-03-29 06:40:40 UTC,"At a guess, it would appear moving the hardware cursor on nouveau is synchronous. At least much more synchronous than it is on intel with the same displays connected."
1677128,2017-11-03 15:24:49 UTC,Syncing task from Mir.
1677129,2018-01-11 00:24:37 UTC,"I added /**.[pP][cC][aA][pP]* rw, to /etc/apparmor.d/local/usr.sbin.tcpdump to allow for rotated pcap files."
1677136,2017-03-30 13:06:15 UTC,"I didn't get any such exception when I ran the test.
Can you please paste any such exception when you run the test ?"
1677136,2017-04-10 02:04:21 UTC,"==============================
Failed 1 tests - output below:
=============================="
1677136,2017-04-10 12:58:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/455310"
1677136,2017-06-13 01:22:15 UTC,Details of the external network and the its tenant are as below. Please reference it. The network being deleted was created before running the testcase and  owned by a pre-defined tenant.
1677136,2020-05-11 15:49:10 UTC,"This has been fixed already by the following patch:
https://review.opendev.org/#/c/474987/"
1677137,2017-03-29 11:13:15 UTC,"confirmed on Windows 10, Inkscape 0.92+devel 15610"
1677137,2017-03-29 11:54:35 UTC,Crash also occurs when you try to convert a symbol to path (see attached svg).
1677137,2020-01-25 11:12:08 UTC,"Not replicated in Inkscape 1.1-dev (2a5d477, 2020-01-18), Windows 10. Closing as part of Inkscape's bug migration to gitlab. If the issue occurs again, feel free to reopen at http://inkscape.org/report."
1677139,2017-09-22 05:22:58 UTC,"yes, artful is fixed, perhaps won't fix it in zesty but we'll see"
1677139,2017-09-17 18:04:41 UTC,"I see 4.4.4-1 in artful proposed, and ""looked"" like that has the necessary fixes on the changelog?
Is there any update on this on Zesty, or likelihood that the proposed package will make it to stable for Artful?"
1677139,2017-06-10 20:59:42 UTC,I'll deal with this
1677139,2017-04-21 23:20:48 UTC,yes that's another bug:
1677139,2017-04-19 06:08:51 UTC,the patch for freeipa works
1677139,2017-04-21 08:00:29 UTC,"looks like this will allow you to finish the installation, but with bind9-pkcs11 in failed status:"
1677139,2017-04-20 07:38:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677139,2017-03-29 10:38:15 UTC,looks like there will be a patch to freeipa instead
1677139,2017-04-21 10:56:46 UTC,"Found the reason for this failure, installer uses a library on the following path: /usr/lib/x86_64-linux-gnu/softhsm/libsofthsm2.so"
1677148,2018-03-31 17:04:47 UTC,"That sounds like the ""Window Aperture"" desktop effect triggered by displaying the desktop. (I find it confusing, too. But it can of course be disabled.)"
1677149,2018-10-29 16:40:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677150,2017-06-20 11:50:16 UTC,There is a solution. Please see comment #5 and comment #18 in bug #891029
1677150,2017-03-29 08:11:44 UTC,chose keepass2 package
1677150,2017-03-29 08:44:24 UTC,to resolve this issue myself I tried the following:
1677150,2017-06-20 11:22:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677171,2018-02-20 09:27:34 UTC,"I see the empty lines, but I don't reproduce the behavior. In my case calling ""man xvkbd"" just starts with text (as makes sense, as man formats the text."
1677172,2017-11-08 02:55:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677172,2017-11-08 02:59:35 UTC,"Also tracking here:
https://errors.ubuntu.com/problem/39159170a2e2c3917e96a46300ae2e12b7ef57c2"
1677175,2017-03-29 10:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1677175,2017-03-30 00:32:09 UTC,apport information
1677175,2017-03-30 00:32:11 UTC,apport information
1677175,2017-03-30 00:32:12 UTC,apport information
1677180,2017-03-29 09:42:51 UTC,https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.repeatable_image_based/222/
1677187,2017-03-30 08:34:13 UTC,"No, this is different, not only about the terminal."
1677187,2017-03-29 10:06:54 UTC,"This may have security implications, since in this example case it can result in the user unknowingly typing their password into a plain text input field which may not be revealed again until much later."
1677187,2017-03-29 11:12:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677187,2017-03-30 02:14:25 UTC,Florian marked it fixed two days ago...(?) See bug 1605327
1677189,2017-03-29 18:52:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677193,2017-03-29 10:43:10 UTC,This bug is similar to this one:
1677194,2017-03-29 11:15:10 UTC,"Hi vijay,
while the report lacks the logs usually auto-added by apport this kind of issues is rather common and likely not specific to qemu."
1677197,2017-03-29 10:41:55 UTC,"ozzie@ozzie-R780-R778:~$ sudo apt-get install libaudiofile1:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
libaudiofile1 is already the newest version (0.3.6-2ubuntu0.16.04.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/105 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
dpkg: error processing package libaudiofile1:i386 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
Errors were encountered while processing:
 libaudiofile1:i386
E: Sub-process /usr/bin/dpkg returned an error code (1)
ozzie@ozzie-R780-R778:~$"
1677197,2017-03-29 10:43:31 UTC,"ozzie@ozzie-R780-R778:~$ sudo apt-get purge libaudiofile1:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  libaudiofile1*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 305 kB disk space will be freed.
Do you want to continue? [Y/n] y
dpkg: error processing package libaudiofile1:i386 (--purge):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting a removal
Errors were encountered while processing:
 libaudiofile1:i386
E: Sub-process /usr/bin/dpkg returned an error code (1)
ozzie@ozzie-R780-R778:~$"
1677197,2017-03-29 10:44:36 UTC,"ozzie@ozzie-R780-R778:~$ sudo apt autoremove
[sudo] password for ozzie:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/105 kB of archives.
After this operation, 0 B of additional disk space will be used.
dpkg: error processing package libaudiofile1:i386 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
Errors were encountered while processing:
 libaudiofile1:i386
E: Sub-process /usr/bin/dpkg returned an error code (1)
ozzie@ozzie-R780-R778:~$"
1677198,2018-01-23 22:53:28 UTC,Removing deprecated items from the ovpn configuration file does not help in my case. I still need the patched packages.
1677198,2017-11-12 05:57:45 UTC,"Hi again,"
1677198,2017-11-12 03:23:17 UTC,I forgot to mention in my previous post (#18) that I use Ubuntu 17.10.
1677198,2017-11-12 03:16:22 UTC,"Hello,
I had a problem importing configuration files to create a VPN connection. Nothing would happen after clicking on ""Import from file.."".
After countless attempts (and only after turning my 2nd monitor on) I realized that the ""Select file to import"" window opens on the 2nd monitor and can't be moved to the main monitor.
After selecting the file to import and clicking ""Open"" on the 2nd monitor, the rest of the procedure to add a VPN worked fine and I was able to set a VPN connection.
I hope this helps."
1677198,2017-08-28 16:24:00 UTC,"Hello,
I had my share of issues with network-manager-openvpn, especially with profiles exported from pfsense appliances, as those tend to inline some configurations.
I remember I had issues with Ubuntu 17.04 and 16.04 but as I am testing now, it seems all profiles I have can be imported and used."
1677198,2017-06-06 21:16:54 UTC,"I mean, same error as in #10"
1677198,2017-06-06 21:15:59 UTC,Same failure as in #9
1677198,2017-06-06 20:54:37 UTC,"No, still disconnects, but much longer intervals."
1677198,2017-10-11 11:20:42 UTC,"Hi,"
1677198,2017-06-05 17:21:06 UTC,"I understand this is an upstream bug. I'll just write this here anyway, will post bug upstream later if nobody beats me to it."
1677198,2017-06-06 20:14:44 UTC,"Okay, the GNOME bug seems to be https://bugzilla.gnome.org/show_bug.cgi?id=782584"
1677198,2017-04-06 12:15:10 UTC,Can someone please confirm this? 17.04 is about to be released.
1677198,2017-04-12 08:10:34 UTC,"Ubuntu (Gnome DE) 17.04, cannot use OpenVPN. Every time I try to connect, nothing, but once it’s deactivated I get back my internet access. I don’t know if it’s the same issue though…"
1677198,2017-04-12 08:15:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677198,2017-04-15 21:58:01 UTC,Installed Ubuntu Mate 17.04 today. Tried also Ubuntu 17.04. OpenVPN created by importing *.ovpn file. Does not work with the same error reported by others. Did not try on 16.10 or 16.04LTS.
1677198,2017-06-08 19:05:02 UTC,After I fixed the certificate file access (making them world-readable) I have a stable OpenVPN connection.
1677198,2017-04-18 14:28:16 UTC,"I confirm the issue. I cannot login through VPN anymore since I updated from 16.10 to 17.04. I will also add to that it is impossible now to configure the VPN connections. The ""Configure VPN..."" option in the menu is grayed out and cannot be selected anymore from the NetworkManager."
1677198,2017-04-17 18:14:29 UTC,Can we raise the importance of this confirmed bug?
1677198,2017-04-18 16:31:16 UTC,"Okay, nevermind, in my case it was enough to delete the VPN connections and then add them again with the ""Edit Connection..."" option in the nm-applet menu (somehow ""VPN Connections -> Configure VPN..."" is grayed out and cannot be called). Once created again, the VPN connection work just fine as they used to. Maybe mine is a completely different problem."
1677198,2017-04-21 11:02:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1677200,2017-03-30 00:45:54 UTC,Can you include in the repository of ubuntu 16.04 latest version of amule? Thank you
1677200,2017-05-17 11:47:09 UTC,I also see this on 16.10. Getting:
1677200,2017-06-06 11:08:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677202,2017-12-19 02:29:53 UTC,"Stuart, can we assume you're using wired audio and not Bluetooth?"
1677202,2017-12-19 08:57:58 UTC,"Yup; wired audio, on a normal 3.5mm jack headphone cable (not HDMI or similar)."
1677203,2019-09-19 11:53:02 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1677204,2017-04-04 10:10:44 UTC,New failure https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.support_dpdk/210/testReport/(root)/deploy_cluster_with_dpdk_tun/
1677204,2017-03-30 12:28:45 UTC,Cannot reproduce the bug using 1532 and 1542 ISOs. Please reopen it if it will be reproduced again.
1677217,2017-06-07 04:35:13 UTC,There is the following blueprint.
1677217,2018-11-29 15:22:13 UTC,https://blueprints.launchpad.net/nova/+spec/placement-req-filter-forbidden-aggregates is related.
1677219,2017-04-12 12:39:28 UTC,Unmarking this as duplicate since this bug is actually older than the bug it was marked as duplicate of.
1677219,2017-03-31 03:20:18 UTC,Could you provide logs? You can reach the debug mode of AppCenter by running this in your favorite terminal emulator:
1677219,2017-04-11 14:11:43 UTC,"Hi, I have the same issue on my desktop built from an iso (elementary OS 0.4 Loki) which I had also used on my laptop where AppCenter works fine.  If started from the gui or terminal without admin privileges it's exactly the same issue.  If started as an administrator (sudo) it's 'waiting', but still fails:"
1677219,2017-04-11 14:27:48 UTC,"sorry, I had forgotten and basically I get the same:"
1677219,2017-04-11 14:28:39 UTC,"I also tried a remove and install again, no luck.  eventually always times out:"
1677219,2017-04-11 16:59:48 UTC,Can you please report this issue on Github: https://github.com/elementary/appcenter/issues
1677223,2021-02-02 13:48:18 UTC,We should pick this back up again. Brett can you please update your patch and resubmit so we can work on the review again?
1677223,2020-04-14 02:07:54 UTC,fix submitted: https://review.opendev.org/#/c/717888/
1677227,2017-03-29 12:44:41 UTC,"It appears the PS driver has handling for the case where the volume does not exist, but the returned error from executing the SSH command is a little different so it is getting missed."
1677227,2017-09-26 22:44:16 UTC,Unassigning due to no activity for > 6 months.
1677228,2018-11-26 08:37:35 UTC,Need more information on this bug.
1677235,2017-04-01 23:34:32 UTC,"When removing from automatic startup, the blueman saved the files normally."
1677240,2017-03-29 13:31:28 UTC,"Your off today, right? :-)"
1677240,2017-04-03 17:33:37 UTC,I will start working on this bug. Thanks
1677240,2017-04-04 09:19:28 UTC,Juju doesn't provide any command to destroy or delete the storage that was created during charm/unit creation or any added storage using juju 'add-storage' command. Juju deletes storage automatically that were bounded to the charm/unit on running 'remove-unit' or 'remove-application' or 'remove-machine'.
1677242,2017-04-04 15:21:11 UTC,"As far as I can see this will mean that you have a ""File Manager"" in Unity 7's dash, in addition to ""Files"" (nautilus). Is that right?"
1677242,2017-04-04 15:57:30 UTC,"We need to add to the desktop file
OnlyShowIn=Unity8"
1677242,2017-04-04 16:12:14 UTC,we'll make that fix and push a new silo with the fix
1677242,2017-04-05 16:02:49 UTC,"@laney
We made the fix to hide the ubuntu-filemanager-app in unity7. It's published from
https://bileto.ubuntu.com/#/active?search=2695 and sitting in the Zesty NEW queue awaiting approval."
1677242,2018-04-05 17:00:45 UTC,(cleaning up ~ubuntu-release bugs)
1677244,2017-08-16 21:23:44 UTC,Your test program works in artful with python 3.6 for me; I guess something got updated to fix it but am not going to dig into why unless you really want me to...
1677245,2017-08-15 19:42:02 UTC,"Can someone confirm these assumptions?  More than one authority.control_set_bib_field can be used to control a given MARC tag?  The control set in question, when checking to see if a given bib field is under authority control, is an attribute of the bib field itself?  Would that be indicator 2?"
1677245,2017-08-16 15:09:03 UTC,"Bill,"
1677245,2017-09-05 19:50:30 UTC,Removing myself as assigned as this task is starting to seem like it'll be a much larger task  than initially expected.
1677245,2017-09-05 20:48:30 UTC,"As an update to my earlier comment, we can, of course, assume a control set when only one exists for the instance.  And, as a step toward fixing the general situation of context-less (heh) uses that we may want to prompt the user to resolve, we could globally load the list of context sets and if there's one and only one, do the right thing and use it."
1677247,2020-11-10 15:27:23 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1677247,2021-01-10 04:17:32 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1677268,2019-01-16 00:48:02 UTC,"This was probably due to other actions running and waiting for the cluster or node locks to be released.  Previously if a lot of actions for the same cluster or node were started, they would all wait for the locks to become available.  This slowed down the engine a lot."
1677276,2018-06-06 02:20:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677280,2017-03-29 15:18:10 UTC,"We don't issue update event on transition to ACTIVE because it's guarded by provisioning blocks, and the status is updated via a custom endpoint. We may want to make the API layer to trigger the update event for that custom endpoint."
1677280,2017-03-30 07:06:00 UTC,"Vitrage as a user of neutron (and I guess other internal and external systems) needs to know about any status change of neutron port and network.
I think each system / project should provide via notification any status change of each one of its elements because the status of an element is the most important thing.
Right?"
1677297,2017-06-06 13:13:53 UTC,This bug was fixed in the package linux - 4.10.0-22.24
1677297,2017-06-05 14:34:02 UTC,"~ # uname -a
Linux (none) 4.10.0-22-generic #24~lp1677297+test.1-Ubuntu SMP Fri Jun 2 18:09:55 UTC 2017 aarch64 GNU/Linux
~ #"
1677297,2017-06-05 14:33:14 UTC,I built DI and booted the netboot image on an SDP. DI works as expected with the patch.
1677297,2017-06-02 16:33:46 UTC,"kleber-souza,"
1677297,2017-06-02 14:42:30 UTC,"Hi @manjo,"
1677297,2017-06-01 20:49:51 UTC,This bug was fixed in the package linux - 4.10.0-22.24
1677297,2017-04-11 17:22:22 UTC,"I did a D-I install on the qdf 2400 server with zesty + the patchset, using the Mellanox adapter (Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]). The qcom_emac driver is installed but the port (eth0) does not get an IP address without running dhclient -v.  An IP address is assigned but not seen with the ifconfig command.  I am able to ssh into that system using the assigned IP address, that I can only see from the output of the dhclient command."
1677297,2017-05-31 19:56:53 UTC,"Downloaded the netboot installer from
http://ports.ubuntu.com/dists/zesty-proposed/main/installer-arm64/current/images/netboot/"
1677297,2017-05-26 02:57:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1677297,2017-04-26 19:11:52 UTC,"qcom_emac works fine with the generic phy driver, either the at803x driver needs to be fixed or the underlying userspace utils like dhclient needs to retry bringing up the link when it is reported as down. This should not be a blocker for switching from msm_emac to qcom_emac for d-i."
1677297,2017-04-24 16:25:40 UTC,"Timur found that the at803x module (needed for an erratum) is the reason we are unable to get a dhcp lease on the emac interface. He is exploring his options on fixing the issue, ie have a an option to pass in a phy driver if the erratum is encountered. We found that on my SDP we did not need the at803x module, and that the qcom_emac was able to use the generic phy to come up and get dhcp leases."
1677297,2017-04-12 20:13:35 UTC,on my qdf2400 server. Looks like dhclient is able to get a lease and ifconfig displays the ip address.
1677297,2017-04-11 17:36:57 UTC,Also we tried the workaround in comment #16 and blacklisting the mlx5_core module during the install and eth0 was not available.
1677297,2017-06-01 15:03:45 UTC,"The fix was included on Zesty kernel 4.10.0-22.24, the netboot installer is loading 4.10.0-19, which is probably the GA kernel. I'm trying to find some sort of daily netboot build so it can be tested with the latest kernel."
1677297,2017-04-04 04:34:15 UTC,"Timur,"
1677297,2017-04-01 16:04:14 UTC,How about the ifconfig command to bring the interface up?  This just shows that the drivers have loaded.
1677297,2017-03-29 16:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1677297,2017-03-29 20:50:50 UTC,qcom_emac driver that is in Zesty (4.10) kernel is able to bring up the interface but fails to get a DHCP address. This bug is currently blocked until upstream fixes the qcom_emac driver.
1677297,2017-03-29 20:53:17 UTC,You need to back-port some patches from 4.11 if you want the driver to work.  Look at our 4.10 rebase for details.
1677297,2017-03-29 21:22:49 UTC,"Also, you may need to load the at803x driver before bringing up the interface.  I've noticed in some kernels, the link doesn't come up unless you load this driver first.  I don't know why it's a requirement only on some kernels."
1677297,2017-03-30 03:11:55 UTC,"That is hard to SRU, we don't want to be adding unrelated modules to DI."
1677297,2017-03-30 03:48:18 UTC,"Sorry, I'm not sure what happened there.  I meant to say that that is the
*actual* PHY on the SDP board.  It's an Atheros 8031 PHY.  I was hoping
that we could get away with the genphy driver that's built-in, but
apparently not."
1677297,2017-03-30 03:22:19 UTC,"It's not unrelated. That is the actusl phy on the SDP.
________________________________________
From: Manoj Iyer [<email address hidden>]
Sent: Wednesday, March 29, 2017 10:11 PM
To: Timur Tabi
Cc: Manoj Iyer; Andrew Cloke; David Douglas; <email address hidden>
Subject: Re: Zesty use qcom_emac instead of msm_emac."
1677297,2017-03-30 13:57:04 UTC,"Yes, the REP has the Atheros 8033, which uses the same driver."
1677297,2017-04-01 01:45:48 UTC,With the PHY module and the qcom-emac driver enabled in D-I  I am able to see the interface in the installer configure network screen.
1677297,2017-04-01 03:18:09 UTC,"I built a DI where the initrd has both the PHY and the qcom_emac driver. The d-i installer now loads both at803x and qcom_emac, but dhclient fails to get a DHCP address. So, I am not sure what is going on with qcom_emac.. is there another module dependency I am missing ?"
1677297,2017-04-01 03:42:34 UTC,"Can you try bringing up the interface manually, with ifconfig and a static IP address?  The driver that's already in 4.10 should work as-is.  I need to see the console output as the driver tries to bring the interface up, and dhclient hides all that."
1677297,2017-04-01 15:44:52 UTC,"~ # rmmod qcom_emac
~ # modprobe qcom_emac
~ # dmesg | tail -n 15"
1677297,2017-03-30 13:46:03 UTC,"> It's not unrelated. That is the actusl phy on the SDP.
"
1677297,2017-04-04 14:12:04 UTC,The qcom_emac driver in the installer is able to get a DHCP lease once I blacklisted the mlx5_core module.
1677304,2017-04-04 14:29:34 UTC,"Recommendation: confirmed, wishlist."
1677305,2017-11-03 10:33:39 UTC,The problem shows up again. I am not able to tell the cause that made it to come back.
1677305,2017-04-06 06:59:30 UTC,"The problem has now disappeared after the last reboot. Before it, I did this upgrade:"
1677305,2017-03-30 20:35:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677316,2017-07-13 00:33:11 UTC,"Hyunsun Moon hit similiar problem, and here is the docker version:
Docker version 17.06.0-ce, build 02c1d87"
1677316,2017-07-21 09:28:55 UTC,"Looks like RequestAddressType options is set correctly now with the latest Docker version.
See the log below."
1677323,2017-03-30 09:21:42 UTC,"I don't know if ""Ctrl-Enter"" for newline and ""Enter"" to escape or the reverse is better."
1677323,2017-03-30 09:55:18 UTC,Apparently this works on windows: Enter and Tab both leave the box. But so does Ctrl-Enter.
1677323,2017-03-30 10:09:12 UTC,"I'm going to won't-fix this report, because there's really not much we can do about it - this is IIRC a limitation of wxWidgets. There are some hackish ways it could be implemented, most involving EVT_CHAR_HOOK; I don't think it's worth the hackishness."
1677323,2017-03-30 10:27:42 UTC,This does appear to be a problem with WX on GTK.
1677326,2017-11-30 18:38:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677338,2017-03-31 11:52:42 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1677342,2017-04-21 18:19:20 UTC,"Mihaela, you could tweak this value using the config-flags config option as a workaround."
1677342,2017-04-21 19:29:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458950"
1677342,2017-09-06 15:52:26 UTC,"Change abandoned by Felipe Reyes (<email address hidden>) on branch: master
Review: https://review.openstack.org/458950"
1677343,2017-03-29 18:25:44 UTC,related / linked bug - https://bugs.launchpad.net/evergreen/+bug/1677340
1677343,2017-03-29 18:37:11 UTC,EG 2.10 & EG 2.12
1677351,2017-03-30 16:17:40 UTC,"We should be sure that the JSON is well formed even if the content contains
fields that 2.1 doesn't expect. Traditionally status has been something
that we rarely break between releases (up until the very last 1.X could
status across a very large range)."
1677351,2017-03-29 23:20:36 UTC,I am pretty sure that our new clients are backward compatible.
1677351,2017-03-29 18:56:15 UTC,"Also, when I removed the failed machines from the model, 'juju status' worked again with 2.1.2. The error content appears to be the source of the problem."
1677366,2017-04-06 17:00:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677369,2019-09-19 11:53:05 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1677372,2017-03-31 07:14:24 UTC,"In most use cases it should be ok when we interpret '2' as novaclient.API_MAX_VERSION, because novaclient api microversion match with nova service microversion."
1677392,2017-03-29 22:29:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/451592"
1677392,2017-07-28 09:49:41 UTC,"Change abandoned by Spyros Trigazis (strigazi) (<email address hidden>) on branch: master
Review: https://review.openstack.org/451592
Reason: You can restore it if you want to continue work on this."
1677397,2017-03-29 22:33:23 UTC,Similar failure occurs with kylin-greeter.
1677398,2020-02-04 04:29:19 UTC,"The attachment ""virt-aa-helper-support-pools.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1677398,2020-05-26 08:12:30 UTC,"Hi Garry,
why thanks for the patch - I was missing that update earlier in the year and beg your pardon."
1677398,2020-05-26 08:13:30 UTC,I have subscribed Garry to increase the chance he is seeing and replying to my questions?
1677398,2020-05-26 10:42:04 UTC,Indeed the read to /etc/libvirt/libvirt.conf is from the call to virDomainDiskTranslateSourcePool as I have assumed above.
1677398,2020-05-26 11:07:53 UTC,"Iterating over the usual disks into the pools.
(gdb) p *disk->src->srcpool
$9 = {pool = 0x565040c0a590 ""internal"", volume = 0x565040c09ad0 ""foo"", voltype = 0, pooltype = 0, actualtype = 0, mode = 0}
(gdb) p *disk->src->srcpool
$11 = {pool = 0x565040c093d0 ""testvg"", volume = 0x565040c09650 ""guest1"", voltype = 0, pooltype = 0, actualtype = 0, mode = 0}"
1677398,2020-05-26 12:41:24 UTC,FYI after some debugging I was chatting with libvirt upstream and setting up a new storage context inside virt-aa-helper really won't work architecturally.
1677398,2020-05-26 20:19:59 UTC,Thanks for subscribing me; I'm a launchpad newbie and didn't realize that wasn't automatic when I posted here. I'll try to answer your questions to the best of my recollection.
1677398,2020-05-27 06:35:23 UTC,"Hi Garry,
thanks for your reply."
1677398,2020-09-06 20:42:24 UTC,"I stumbled upon the same issue but with dir based pools. I have all relevant information posted on a SO question, do you want me to paste them here too? The question is here: https://stackoverflow.com/questions/63767647/virt-aa-helper-doesnt-add-path-for-storage-pool-in-apparmor-generated-rules"
1677398,2020-02-04 01:24:13 UTC,"I've written a quick patch that seems to fix the storage pool side of this issue, at least for dir/fs like pool types. It does connect to the libvirtd socket; I saw that there was some concern with that approach earlier, but this solution didn't require any changes to virt-aa-helper's calling conventions. Are we still opposed to having virt-aa-helper connect to libvirtd?"
1677398,2020-09-07 04:12:54 UTC,"> I stumbled upon the same issue but with dir based pools. I have all
> relevant information posted on a SO question, do you want me to paste
> them here too?
"
1677398,2020-09-07 08:29:46 UTC,"There is a comment in this bug that says that dir based pools aren't affected, but it seems they are. Here's the disk definition in XML using a ""default"" named pool that resides in /var/lib/libvirt/images."
1677398,2020-09-07 10:52:30 UTC,"> There is a comment in this bug that says that dir based pools aren't
> affected, but it seems they are.
"
1677398,2020-11-17 02:02:02 UTC,"Hey guys,"
1677398,2020-11-17 02:25:52 UTC,"I found the quick ""fix""..."
1677398,2020-11-21 15:18:35 UTC,I hit this issue today when trying `terraform-provider-libvirt`. So I spent some time debugging it. Below are my findings.
1677398,2020-11-23 13:42:16 UTC,"Hi Yury,
until implemented for real adding apparmor rules for the uncommon paths are the way to go.
The difference I'd suggest to your solution is to use local overrides since they will neither prompt you nor be overwritten on updates."
1677398,2021-02-23 09:49:12 UTC,This now has a related upstream issue https://gitlab.com/libvirt/libvirt/-/issues/135
1677398,2020-07-29 21:42:52 UTC,"I finally had time to revisit this. It appears that not only did my patch not connect to the remote libvirtd storage driver (as Christian pointed out), but that the storage driver does not establish remote connections at all. As such, I agree with Christian that my patch is a dead-end and would also advise anyone finding this now to avoid applying it, even temporarily."
1677398,2019-03-25 08:39:03 UTC,"Hi Nicolas,
yeah that isn't easy to fix and at least I didn't find the time to develop something completely new to cover this yet."
1677398,2020-05-26 10:40:33 UTC,"I was giving this a try
PPA: https://launchpad.net/~paelzer/+archive/ubuntu/lp-1677398-pool-experiment-groovy"
1677398,2019-01-10 20:46:24 UTC,"Up, causing issues with terraform libvirt provider :/"
1677398,2017-03-30 08:38:31 UTC,"Hi Simon,
thanks for your report - so we did not get far enough with bug 1641618 which only solved things for direct zvols, but not for disks from a pool."
1677398,2019-03-24 18:36:38 UTC,The linked/original bug is quite old. Looks not like there is a quick solutions.
1677398,2017-03-30 10:17:32 UTC,"These are mostly notes to remember later:
In such a setup the pool definition has the base pool path"
1677398,2017-03-30 10:18:10 UTC,"Apparmor can't by design follow symlinks (https://bugs.launchpad.net/apparmor/+bug/1485055).
So test-inserting into /etc/apparmor.d/abstractions/libvirt-qemu:
- /dev/zvol/internal/foo rw, => still fails
- /dev/zd0 rw, => works (guest sees disk as expected)
So does any generic rule."
1677398,2017-03-30 13:22:56 UTC,"Hello Christian,"
1677398,2017-03-31 09:06:18 UTC,"FYI - I haven't forgotten, just flooded with other load"
1677398,2017-04-05 07:33:22 UTC,"Damn it seems I can't find the hours yet - I really beg your pardon Simon as I like you as an active community member! But I also have PTO next week and I'm not sure I get to it before that.
I'll assign to myself to not forget about it."
1677398,2017-04-05 13:03:26 UTC,"No worries, I have a good feeling of how busy you are from the bug
notifications I get. Knowing that you will look into it is already a
great deal, so thanks again."
1677398,2017-06-13 13:55:08 UTC,"I don't seem to find time shortly, so I drop server-next tag.
But I ensured it is tracked to remind me and make me feel bad :-/"
1677398,2017-09-18 12:58:32 UTC,"Back on this, currently trying to build up a case where this can be tested from git (had some obstacles):
- In the dev system (from local dir) not all apparmor rules apply
- In a container the zfs actions are not all possible
- So we need a KVM driving a 2nd-level KVM for all of this."
1677398,2017-03-30 09:59:11 UTC,Extending your already good testcase description:
1677398,2017-09-18 14:28:29 UTC,"When the guest gets parsed all that virt-aa-helper initially has is the disk element.
This has in our case only:
p *(disk->src->srcpool)
$10 = {pool = 0x100236b90 ""internal"", volume = 0x100236440 ""foo"", voltype = 0, pooltype = 0, actualtype = 0, mode = 0}"
1677398,2017-09-18 13:50:42 UTC,"Initially this can be run locally just with virt-aa-helper as any virt-aa-helper dev.
This mostly is like c#3, but with a service from local build and with libvtool wrapper to gdb the virt-aa-helper."
1677398,2018-03-19 19:08:29 UTC,"Hi Ultrabit, can you please include the DENIED lines from your dmesg or auditd logs?"
1677398,2018-03-17 12:43:38 UTC,"I have the same problem using raw lvm logical volumes as disk on Ubuntu 18.04.
When i try to start a vm with virt-manager qemu says Permission denied on device."
1677398,2018-01-10 15:59:07 UTC,"TODO: retest these with the domain label callbacks implemented, maybe some of the devices/images might trigger that"
1677398,2020-05-26 08:41:07 UTC,"FYI - dir based pools already work if they are in a common and expected path like seen in
/etc/apparmor.d/usr.lib.libvirt.virt-aa-helper"
1677398,2017-09-19 09:38:54 UTC,"I found that bug 1343245 is about the same general issue.
The descriptions in there were great, but since I started to document the debug and potential coding and more here I dupp'ed it onto here.
The thoughts there also already were around ""how to get the translation done""."
1677398,2017-09-19 06:31:50 UTC,"After having slept on that for a night I consider that not a good way.
The current lifecycle of virt-aa-helper just doesn't match to create a local virConnectPtr context, yet OTOH without one we can't translate the pool as the code that spawns the guest would."
1677398,2017-09-18 15:31:49 UTC,"I'm not sure if upstream likes that virt-aa-helper now needs to talk to the socket, but they can suggest otherwise if they don't.
I now have something that calls the lookup correctly.
It then fails to find the pool:
  libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'internal'"
1677398,2017-09-18 15:12:55 UTC,"virConnectOpenReadOnly and co would initialize the connection, but they would be env specific.
Also as it seems the header is meant for users of libvirt, but not the local tools.
I'll report back when I found the proper initialization (e.g. the empty one via virGetConnect works but is obviously uninitialized and rejects the lookup method)."
1677398,2018-01-10 15:58:31 UTC,"In the same scope of required ""out of context information"" fall cases of vfio devices for hostdevs.
Those work fine if defined in the guest or added to the guest."
1677402,2017-09-26 22:51:09 UTC,Unassigning due to no activity for > 6 months.
1677402,2019-02-05 21:58:05 UTC,It doesn't appear that any documentation has been put in place for this driver.  Is there any plan to correct this?
1677404,2019-08-02 11:39:23 UTC,A fix for this bug is included in the bundle improvement changes (bundles supporting per-charm channel attributes) that are expected to land on develop via https://github.com/juju/juju/pull/10480
1677404,2019-07-08 14:10:52 UTC,The team is currently working on some bundle improvements and this is on the docket for part of these changes this cycle.
1677404,2017-09-26 16:25:15 UTC,Can we get a status update on this? There still seems to be no way to refer to charms in different channels in bundles.
1677404,2017-04-12 03:57:50 UTC,My preference would be the following:
1677404,2017-04-11 08:46:59 UTC,I think this must be fixed at three levels:
1677404,2017-03-31 04:31:08 UTC,"David Britton (davidpbritton),"
1677404,2017-03-30 23:27:22 UTC,"Taking a step back -- as a user, the most expected thing to me by running this command was to download the bundle in the edge channel, as is, and deploy it, as is:"
1677404,2017-03-30 22:57:33 UTC,Should there be fall backs though?
1677404,2017-03-30 02:24:50 UTC,"Don't think it's related.  And no, no resources in the haproxy charm that I know of."
1677404,2017-03-29 23:15:09 UTC,"@David Britton,
I wonder if this is related to Cory's findings in bug # 1627127..."
1677404,2017-03-31 18:09:07 UTC,"Hi Anastasia,"
1677404,2017-03-30 16:09:28 UTC,"Just to summarize, deploying an ""--channel=edge"" is asking to deploy some
charms which are *not* in channel=edge."
1677405,2017-04-14 23:46:56 UTC,The documentation actually indicates that this should only be done on the system which experienced the crash:
1677411,2018-05-30 18:00:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677415,2019-05-08 13:06:33 UTC,"Was going to upgrade to 18.04 LTS and received the following messages during the prep and the attempt of the upgrade.  I have had issues with this same package in the past (see above...package linux-headers-4.4.0-70-generic 4.4.0-70.91 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration). Someone suggested a bot made a change to this. Why would there not be an archive for it? Might the file(s) be misplaced?  I did a search of the directories and it appears there are folders for linux-headers-4.4.0-70-generic, linux-headers-4.4.0-70, linux-headers-4.4.0-145, linux-headers-4.4.0-145-generic, linux-headers-4.4.0-146 and linux-headers-4.4.0-146-generic residing under usr in folder src.  How do I reconcile so I can upgrade to 18.04 LTS?"
1677415,2017-03-30 01:00:11 UTC,This change was made by a bot.
1677415,2017-04-03 10:11:57 UTC,You may need to run the following from a terminal:
1677419,2017-03-31 18:42:07 UTC,We have done some testing and we are able to handle a flow entry setting of 4M and still update the flow statistics fast enough to keep the flows from timing out.
1677419,2017-04-06 15:09:24 UTC,As we increase vr_flow_entries support with a higher value the problem becomes that we are not able to fit the Mirroring metadata table in without re-writing the mechanism of accessing the entries and controlling to a maximum TBD value of entries. Presently Mirroring metadata is referenced via the flow id so tables are 1 for 1.
1677419,2017-04-06 14:30:48 UTC,We have modified our flow entries to safely run with 512K flow entries.
1677423,2018-01-20 07:43:02 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1035
1677423,2017-04-11 15:03:37 UTC,"Thanks. I do understand that we have instructions for compiling from source, but should we not have ""complete"" instructions for also building packages for our supported operating systems as well?"
1677423,2017-04-11 14:53:50 UTC,yes it is possible but it is more time consuming procedure. So I will try to create the doc as soon as possible. and after that I will create such script.
1677423,2017-04-11 08:07:40 UTC,Lets keep it as feature request to describe package build process in our docs
1677423,2017-04-11 14:31:30 UTC,"Mattew B,"
1677423,2017-04-11 14:11:49 UTC,I will prepare the instruction a bit later is it ok?
1677423,2017-04-11 13:54:19 UTC,"Seriously? Instructions for how to build our product is a ""feature request""? What if MySQL said that? or Docker? or AWS had no docs on their website because it was just a feature request and they expected everyone to be able to figure it out on their own?"
1677423,2017-04-11 14:44:39 UTC,"Evgeniy,"
1677430,2017-03-30 02:02:44 UTC,Please use bold for all the window titles. It would fix a couple of bugs! :)
1677430,2017-03-30 13:52:49 UTC,"FWIW, it's like that per design."
1677430,2017-03-31 02:07:19 UTC,No problem. Designs can have bugs too. Let's fix it :)
1677431,2017-09-21 14:44:58 UTC,Juju 2.0's default behaviour would paper over this problem with automatic hook retries as well :-)
1677433,2019-03-26 08:18:37 UTC,*It's not just colors which differ.
1677433,2019-03-26 08:17:20 UTC,See https://bugs.launchpad.net/inkscape/+bug/1781887
1677433,2017-06-19 12:08:54 UTC,"@Hachmann
Thanks for the workaround/fix, shall I report to KDE upstream about this issue, or it is already reported?"
1677433,2017-06-19 01:09:53 UTC,See also: https://answers.launchpad.net/inkscape/+question/608567
1677433,2017-06-18 06:41:13 UTC,I investigated the Breeze theme and noticed that it has the following `gtkrc` settings:
1677433,2017-06-16 18:09:51 UTC,I noticed that after I switch GTK2 theme to non-Breeze-* the issue is no longer produced.
1677433,2017-06-16 18:04:47 UTC,"Reproduced on KDE neon 5.10, I wonder if this is a KDE-specific bug?"
1677444,2019-09-19 12:03:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1677445,2017-03-30 04:24:40 UTC,"@Chad Smith (chad.smith),"
1677445,2017-03-30 14:57:11 UTC,Apologies for the lack of details I was trying to file a simple bug. Here are the details:
1677450,2017-04-05 08:35:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677462,2017-06-27 05:17:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677465,2017-03-30 06:22:59 UTC,Attaching a screenshot of the error
1677465,2017-03-30 06:37:06 UTC,"During testing, I also discovered that the RAF files work great with the latest DarkTable(AppImage). This might mean that we just need to have a new version of whatever RAW parsing library we use."
1677467,2017-04-22 17:44:39 UTC,I have linked a second experimental branch that you may like to try out.
1677467,2017-04-22 17:47:16 UTC,"I do recommend, however, that you do not mount, in fstab, remote folders at as a child of your home folder.  You should use /mnt or another folder you do not normally display directly and use the bookmark to view the folder."
1677467,2017-04-19 10:39:18 UTC,It has been reported that this bug is not fixed by the linked branch so it is being re-opened.
1677467,2017-04-06 10:03:12 UTC,"OK, thanks Max.  It looks as if I have not reproduced the bug exactly in that case.  Could you let me know the relevant lines in fstab that refer to the mounts (with any personal info redacted)? Also whether when Files closes, which mounts (if any) are being displayed in tabs."
1677467,2017-04-22 14:33:07 UTC,"Part of the problem seems to be that a location mounted this way does not appear to Files to need a network connection to be accessed - it is just part of the local file system.  Moreover the location remains mounted by the system when the network connection is broken. So Files will attempt to load it. I find that the tab eventually times out and Files interface is not blocked meanwhile (which is the expected behaviour).  However, I also find that trying to load a home folder tab is also blocked until the mount tab times out and then the home folder tab also times out, which is unexpected.  Other locations, not below the home folder can be displayed normally."
1677467,2017-04-05 01:18:20 UTC,"No, it doesn't, I just tried it."
1677467,2017-04-01 10:46:00 UTC,Does Files start eventually if you wait?  I find that when a remote samba mount is established (as the only tab) then Files closed then the network connection broken then Files will eventually open after a wait of about 60 seconds.
1677468,2017-03-30 07:10:22 UTC,"On 30/03/17 07:49, Dominic Raferd wrote:

> my apt-cache policy shows snapd 2.22.6 (see original post) but:
"
1677468,2017-03-30 07:44:18 UTC,"Thanks Mark, how clever is that! But it still leaves my original issue
though..."
1677468,2018-01-17 08:20:27 UTC,Thanks for your bugreport. AIUI the report the message is confusing. I pushed a better one into: https://github.com/snapcore/snapd/pull/4500
1677468,2019-10-29 21:58:54 UTC,The referenced pull request was merged into snapd and the package was released since. I'm marking this issue as fix released.
1677468,2017-03-30 06:49:40 UTC,my apt-cache policy shows snapd 2.22.6 (see original post) but:
1677469,2017-03-30 17:47:55 UTC,Please post details of port-chain usage
1677469,2017-04-05 13:17:27 UTC,"Current tacker CI look OK, I think you had sfc failures because https://review.openstack.org/#/c/450463/ was not merged yet (it was merged the day after this launchpad report)."
1677469,2017-05-22 13:04:30 UTC,I think we can close this one
1677469,2017-09-11 16:03:25 UTC,Fix released in Pike
1677472,2017-04-07 14:15:14 UTC,"Upgraded grub 2.02~beta2-36ubuntu3.9 on 4/5/17. Same problem. It overwrote my EFI partition grub.cfg to hd0,gpt4 instead of (hd0,gpt4)."
1677478,2017-04-15 12:43:51 UTC,precision: only occurs on outgoing calls
1677486,2019-03-10 02:53:49 UTC,Cannot reproduce this bug with Inkscape 0.92.4 on openSUSE Tumbleweed 20190301.
1677486,2017-05-01 20:22:37 UTC,"Reproduced on Windows XP (32-bit), Inkscape 0.92 and lp:inkscape/0.92.x rev. 15420.
Not reproduced with 0.91."
1677486,2018-12-13 17:35:47 UTC,"Reproduced on Debian GNU/Linux amd64 stable release (9.6/stretch), with Inkscape 0.92.1 r15371."
1677490,2017-03-30 07:13:55 UTC,"(Since I didn't find an option to attach another file, here's the other one, after trying to adjust manually)"
1677490,2017-03-30 14:25:30 UTC,"At first it wouldn't click (I had all the text selected and the button wouldn't work), but then after I unselected it it let me do it, though I'm not able to redo it now. Still, even after that when I try to adjust the height it just does it to the first line."
1677490,2017-03-30 20:02:45 UTC,Thanks for the picture.
1677490,2019-02-05 23:42:10 UTC,"This bug is also present in the version of Inkscape shipped with Linux Mint 19.1 (not tested in 19.0, but it was fine in 18.3). I can confirm that both changing the line spacing settings (the interface for that has been changed since the version in Mint 18.3) and clicking the question mark button only affects the first line."
1677490,2019-03-11 12:55:12 UTC,"If you select the lines or characters individually, they will adjust properly. It's only if multiple lines are selected that the first selected line is used."
1677490,2017-03-30 11:44:57 UTC,"You might try clicking on the question mark button when typing new text. If that doesn't help, chime back."
1677499,2017-03-30 08:10:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677503,2017-08-16 12:03:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677505,2020-07-16 15:54:30 UTC,"invalid, you changed your /usr/bin/python symlink to point to python3"
1677519,2017-03-30 08:51:49 UTC,Note that one workaround is to juju set the nagios_master to the IPv6 address of the master.
1677519,2017-06-02 01:30:14 UTC,I think we'd be better off getting https://github.com/NagiosEnterprises/nrpe/commit/1ac990954b7806d9cc92fa340808b29219e872a1 SRUed into trusty & xenial.  The fixed version is already available in zesty & later: https://packages.ubuntu.com/search?keywords=nagios-nrpe-server
1677528,2017-03-30 10:33:13 UTC,"Fix proposed to branch: master
Change author: Valeriy Saharov <email address hidden>
Review: https://review.fuel-infra.org/32650"
1677528,2017-03-30 10:58:55 UTC,"Reviewed: https://review.fuel-infra.org/32650
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1677533,2017-03-30 10:13:07 UTC,It looks like the following ImportError is primary reason of failure: ::
1677533,2017-03-30 10:29:01 UTC,I have checked the code of fuel-qa and fuel-devops projects and it looks like there is no fuel-devops installed on the executor.
1677533,2017-04-04 10:59:33 UTC,"Reviewed: https://review.fuel-infra.org/32751
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master"
1677540,2017-03-30 11:54:17 UTC,"side effects, some strings corruption is some apps (note: i can't reliably reproduce this bug, but i see it happen occasionally when running apps with Xmir, video players, games)"
1677540,2017-03-31 02:17:37 UTC,It looks like a corrupt texture cache/atlas in Unity8 itself...
1677540,2017-04-20 21:16:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677540,2017-05-10 14:04:05 UTC,See also https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240
1677540,2017-05-10 20:20:23 UTC,Do you use nvidia?
1677540,2017-05-10 20:32:56 UTC,1684240 seems to be the same issue. In my case this can be reproduced under Kubuntu with Nvidia.
1677540,2017-05-11 01:29:15 UTC,This bug is for Mir/Unity8. So if you have issues in Kubuntu or Unity7 please use a different bug.
1677541,2017-03-31 11:51:43 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1677541,2017-04-03 14:45:46 UTC,"Hi,
Thank you for taking the time to report this bug and helping to make Ubuntu better."
1677543,2020-08-04 00:53:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/744578"
1677543,2019-11-08 17:27:17 UTC,This was fixed and released in manila in July 2017
1677543,2017-08-10 20:42:07 UTC,"Reviewed:  https://review.openstack.org/492491
Committed: https://git.openstack.org/cgit/openstack/charm-manila/commit/?id=df96346eb9ce729a58a57a96f756551c398068e0
Submitter: Jenkins
Branch:    master"
1677543,2020-09-17 09:06:38 UTC,"Reviewed:  https://review.opendev.org/744578
Committed: https://git.openstack.org/cgit/openstack/charm-barbican/commit/?id=3ba2652b10f85bdf351bceeb45d49845baf6f380
Submitter: Zuul
Branch:    master"
1677543,2017-08-04 18:58:04 UTC,"Reviewed:  https://review.openstack.org/487133
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=d950502c9c5055e117df1f7fa782a3ea261e5043
Submitter: Jenkins
Branch:    master"
1677543,2017-08-04 18:00:07 UTC,"Reviewed:  https://review.openstack.org/487055
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=a9667261067b32639262b5ef8e71923afc4889fb
Submitter: Jenkins
Branch:    master"
1677543,2017-07-25 16:19:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/487133"
1677543,2017-04-03 13:35:02 UTC,+1 to the general need for this in the reactive charms. :)
1677543,2017-08-10 12:02:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/492491"
1677543,2017-07-25 13:23:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/487055"
1677549,2017-03-30 12:08:29 UTC,"Related fix proposed to branch: master
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/32654"
1677549,2017-03-30 12:15:43 UTC,"Related fix proposed to branch: master
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/32655"
1677549,2017-03-30 12:53:04 UTC,"Reviewed: https://review.fuel-infra.org/32655
Submitter: Alexander Evseev <email address hidden>
Branch: master"
1677549,2017-03-30 13:14:32 UTC,"Related fix proposed to branch: master
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/32661"
1677549,2017-03-30 13:18:42 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/32662"
1677556,2017-03-30 13:43:35 UTC,Bug in upstream: http://tracker.ceph.com/issues/18977.
1677558,2017-03-31 14:13:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software. Unfortunately, I cannot find any references to the project having a bug tracker. Therefore the only contact information I can find is a direct email address for the author from their homepage at http://midas.psi.ch/elog/. The email address is for Stefan Ritt at <email address hidden>."
1677558,2018-12-21 13:19:03 UTC,The issue has been fixed upstream.
1677560,2017-09-26 22:51:16 UTC,Unassigning due to no activity for > 6 months.
1677575,2017-04-04 12:50:42 UTC,"Thanks for the feedback.  Since it's fixed in mainline, we can perform a ""Reverse"" bisect to identify the commit that fixes the bug."
1677575,2017-04-03 10:14:15 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1677575,2017-03-30 12:00:12 UTC,This change was made by a bot.
1677575,2017-04-04 09:13:29 UTC,"The bug itself is fixed in the 4.11.0-041100rc5-generic kernel. But I encounter regular freezes with this version of the kernel, and I have ACPI related error messages."
1677578,2017-04-05 15:59:26 UTC,I appreciate your help but you are missing the point. Christian was so concerned about script going beyond memory_limit so he just discarded everything else I researched about the memory leak issue I was reporting in the first place. The memory leak issue is still there. It is still an issue and it still has to be fixed.
1677578,2017-04-05 12:16:27 UTC,"Why are you trying to create image despite I provided a real image that can be used instead? Also, I don't see how can it be tested with php-cli, because php-cli dies along with the script. Can you please read comments #19 and #20?"
1677578,2017-04-05 12:21:42 UTC,"Also your test is not correct because it's not about how big is the image, but how long it takes for thumbnailImage method to process it. The idea is to get php into killing a script while thumbnailImage is processing image. On a relatively slow computer it may happen even with a lot smaller images."
1677578,2017-04-05 12:41:45 UTC,Just when I wanted to report to PHP I found [1] which also led me to [2].
1677578,2017-04-05 14:32:44 UTC,"Seriously. Can you test and see that regardless of what limits are, there is a memory leak issue and I already stated many times how to trigger it and what exactly is the cause?"
1677578,2017-04-05 15:42:17 UTC,"@shadowlmd, after reviewing paelzer's comment #26 it is very clear that he made a significant effort to help resolve your report. Looking at paelzer's explanation, he reproduced the root issue in a variety of ways, investigated if this was a known upstream issue, or if known upstream work around existed. In this case this situation should be avoided and corrected via a configurable option."
1677578,2017-04-05 16:06:12 UTC,"Vasya - sorry to unintentionally ignore your posts in between.
I worked on this straight this morning on without refreshing the page in between - so I just didn't see them at all.
I was made aware now - I really beg your pardon!"
1677578,2017-04-06 16:30:01 UTC,For Nish the minumum is really only:
1677578,2017-04-05 18:49:59 UTC,"Yep. But at least this particular bug can and should be fixed. I'm pretty much sure that Imagick has some shutdown handler that frees allocated memory, and it works when script is killed after newImage created a huge image, for example. Memory is only leaked when script is killed while thumbnailImage is processing image, so it probably allocates memory using pure malloc, so Imagick's memory manager and/or handler doesn't know anything about it."
1677578,2017-04-06 08:01:04 UTC,"After better understanding I was easily able to confirm the actual issue.
Sorry once more for the useless noise Vasya."
1677578,2017-04-06 08:05:01 UTC,"The next I tried was checking newer versions from [1].
There currently is the more recent combination:
- php-imagick 3.4.3~rc2-2
- php* 7.1.3+-3"
1677578,2017-04-06 16:44:31 UTC,"Vasya,"
1677578,2017-04-06 17:12:23 UTC,Done.
1677578,2017-04-25 22:40:47 UTC,"Upstream considers (as of right now) this to be a bug in imagick (php-imagick, I believe). I'm marking it as such and we'll see what resolution occurs from upstream."
1677578,2017-04-05 11:25:23 UTC,"On the ImageMagick Side there seems to be
  /etc/ImageMagick-6/policy.xml
Which has:
  <policy domain=""resource"" name=""width"" value=""16KP""/>
That is not the case on Xenial where the rule seems to have no effect (older version).
But all that is only masking the real problem, which is why php-cgi is allowed to grow out of bounds."
1677578,2017-04-05 18:33:00 UTC,"Realistically the only way that a persistent php 'controller' process can avoid this is to fork() a new process for every script execution that it can kill via OS controls afterwards, or better yet just use the OS-provided rlimits to control memory use, CPU use, etc."
1677578,2017-04-05 11:00:33 UTC,For the time being - until clarified otherwise - I think this could be used to DOS a server so I'll mark it security.
1677578,2017-04-05 11:51:38 UTC,"According to [1] I should be able to set that limit for cli scripts as well.
If possible that would take a lot of things (lighthttpd/cgi) out of the equation so lets try this."
1677578,2017-04-05 10:36:15 UTC,I'm not sure you ran into something I am reporting. Looks like you are missing my comments or something. Here's a summary:
1677578,2017-03-31 11:36:51 UTC,"Why didn't you try my example instead? I believe it doesn't free memory used by objects or something like that. I noticed an issue when php processes ate up all free memory on server, being about 500 MB each and growing."
1677578,2017-03-31 11:40:04 UTC,"And yes, the system went a bit unresponsive at this point with 100% swap usage."
1677578,2017-03-31 11:50:46 UTC,"> How many cgi-bin processes do you have and what memory do they consume?
"
1677578,2017-04-03 14:49:42 UTC,"I didn't try your example as ""Just put many big JPGs to images directory."" was too unsure to reproduce for each trying to help on this bug the same way."
1677578,2017-04-03 18:42:08 UTC,I tried with this script:
1677578,2017-04-05 08:26:48 UTC,"""Never"" is too much of an extreme, it does not consume execution time and is thereby not killed by the max_execution_time limit as I outlined before.
But that is works-as-designed and not a bug, at some point later on the request itself will timeout - I don't know what the limits are thou."
1677578,2017-04-05 08:27:17 UTC,Also thanks Vasya for your active participation!
1677578,2017-04-05 10:41:54 UTC,"And yes, Imagick easily allocates far more memory than memory-limit allows. And memory_get_usage() doesn't report this memory. Probably that is the reason why php can't free this memory when it kills the script. It's absolutely up to Imagick class to free up memory and if php kills the script before it happens, memory gets leaked."
1677578,2017-04-05 08:40:35 UTC,"If I try to get ""too much"" via the var alloc I hit:
""Allowed memory size of 134217728 bytes exhausted (tried to allocate 528384 bytes)"""
1677578,2017-04-05 09:10:49 UTC,"This example, however, works perfect:"
1677578,2017-04-05 10:02:57 UTC,As I said I was trying to get closer to your case.
1677578,2017-04-05 10:08:40 UTC,Can you please try my example above with single big enough image?
1677578,2017-04-05 10:14:27 UTC,Here's what I get. Memory usage before running tests:
1677578,2017-04-05 10:18:38 UTC,You can use this image: http://home.bsrealm.net/IMG_2466.JPG
1677578,2017-04-05 10:22:17 UTC,"The only thing left that came to my mind would be a single super-huge image.
char=""x""; sz=8192; convert -size ${sz}x${sz} xc:white ${char}.png; ll -h ${char}.png
char=""y""; sz=16384; convert -size ${sz}x${sz} xc:white ${char}.png; ll -h ${char}.png"
1677578,2017-04-05 10:23:19 UTC,"That was done on Xenial
On Zesty I run into an issue loading the image.
Uncaught ImagickException: Invalid IHDR data `/usr/share/backgrounds/y.png' @ error/png.c/MagickPNGErrorHandler/1630 in /var/www/html/index.php:18"
1677578,2017-04-05 08:54:08 UTC,"Yep, it's at 128M. But it's per-script limit so php process can eat more as long as it gets new scripts to execute, I believe."
1677578,2017-03-31 11:05:08 UTC,"apt-get install lighttpd php7.0-cgi
sudo lighttpd-enable-mod fastcgi fastcgi-php"
1677582,2017-05-06 12:15:03 UTC,"Hello All,"
1677582,2017-04-01 09:23:50 UTC,Would be great!
1677582,2017-04-03 10:55:36 UTC,"I believe Telegram is the second most important app on the Ubuntu Phone after the Phone app. The voice call feature, if implemented, would make that ranking arguable ;-)"
1677582,2017-03-31 17:01:44 UTC,I agree it is an important feature to every smartphone user.
1677587,2017-03-30 12:57:21 UTC,This snap is doing:
1677587,2017-03-30 15:09:55 UTC,"Sergio, I've opted to fix this in snapd while AppArmor upstream discusses the issue (note, there are valid arguments for not fixing it in the base abstraction). Here is the PR: https://github.com/snapcore/snapd/pull/3116"
1677587,2017-03-30 15:10:39 UTC,"From irc:
10:05 < jdstrand> tyhicks: I think a strong point in favor of not fixing it is that
                  the upstream policy doesn't do anything with ldd, so there is far
                  less need for ix on ld.so
10:05 < jdstrand> and therefore if you add ldd ix to your policy, you get to add an
                  extra ix rule for ld.so
10:05 < jdstrand> (ie, exactly what snapd is going to start doing)"
1677587,2017-03-30 20:45:07 UTC,"ldd(1)'s behaviour is often unsuitable for forensics use. It sets a flag interpreted by the glibc loader and then executes the program in question. If a program has selected a different loader, or is statically compiled, the program will just execute."
1677587,2017-04-03 18:55:20 UTC,"@Seth, note that 'ldd' isn't used by snapd or its tooling, it is simply allowed by policy for snaps to use if they choose to do so. In this case, a snap developer running ldd on something controlled by the developer is fine because it is only happening within the security context of the snap and the developer (presumably) knows what she is doing. This isn't to say that readelf isn't a better tool, but a developer can choose to use readelf or ldd based on the needs of the snap. This bug is about making sure ldd simply works within the context of the snap."
1677599,2017-03-30 13:08:06 UTC,sometimes it even crashes the terminal
1677600,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1677621,2018-08-08 23:33:52 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/590062"
1677621,2018-08-09 02:13:50 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/590070"
1677621,2018-08-09 12:06:17 UTC,"Reviewed:  https://review.openstack.org/382853
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e052c7fe9262c38da9d8b5f9a0ee889d9c1c6be
Submitter: Zuul
Branch:    master"
1677621,2018-08-09 20:03:42 UTC,"Reviewed:  https://review.openstack.org/590062
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=559de0d0a3df92ef9dca21edfaa754a2848013c3
Submitter: Zuul
Branch:    stable/queens"
1677621,2018-10-02 20:01:04 UTC,"Reviewed:  https://review.openstack.org/605881
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8b3b8e5657ffe0f12e1ccfbe6d978e62a2bfdc89
Submitter: Zuul
Branch:    stable/ocata"
1677621,2018-09-27 23:21:13 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/605882"
1677621,2018-10-01 21:59:26 UTC,"Reviewed:  https://review.openstack.org/590059
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9c1a58dd033fa8feeb1175956d57dc90aa55acd
Submitter: Zuul
Branch:    stable/pike"
1677621,2018-10-01 22:04:25 UTC,"Reviewed:  https://review.openstack.org/590070
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c5d8594cb62c1397183888133bef68fe28c62c7a
Submitter: Zuul
Branch:    stable/pike"
1677621,2018-10-02 20:01:22 UTC,"Reviewed:  https://review.openstack.org/605882
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9e146072b6ab5c614cc4502170cc686cc8cc7bce
Submitter: Zuul
Branch:    stable/ocata"
1677621,2018-09-27 23:13:39 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/605881"
1677621,2018-08-08 23:18:13 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/590059"
1677621,2017-05-08 22:10:10 UTC,This issue was fixed in the openstack/nova 15.0.4 release.
1677621,2017-07-17 13:56:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/484381"
1677621,2017-04-25 17:29:49 UTC,"Reviewed:  https://review.openstack.org/453938
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c2ff276c841934ff147aab836a4bd099297fb46b
Submitter: Jenkins
Branch:    master"
1677621,2018-01-22 05:38:31 UTC,"Reviewed:  https://review.openstack.org/484381
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b930336854bffec1bb81b6d67079a4df59e0af19
Submitter: Zuul
Branch:    master"
1677621,2017-04-26 15:35:55 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/460173"
1677621,2017-04-26 17:44:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/460233"
1677621,2017-04-25 19:20:47 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/459840"
1677621,2017-04-28 17:26:35 UTC,"Reviewed:  https://review.openstack.org/460173
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=70c1eb689ad174b61ad915ae5384778bd536c16c
Submitter: Jenkins
Branch:    stable/newton"
1677621,2017-05-08 17:51:51 UTC,"Reviewed:  https://review.openstack.org/460233
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=44a55d65e2aecdaa8fbcd32b2cde1b81a6fe74d8
Submitter: Jenkins
Branch:    master"
1677621,2017-05-08 22:25:44 UTC,This issue was fixed in the openstack/nova 14.0.6 release.
1677621,2017-06-08 21:53:11 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1677621,2017-04-27 20:47:44 UTC,"Reviewed:  https://review.openstack.org/459840
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f281c18ba9aea1b2e8a36d5ae91a7acc5324ac5e
Submitter: Jenkins
Branch:    stable/ocata"
1677621,2017-04-06 01:01:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453938"
1677625,2017-03-30 19:14:17 UTC,"Can you elaborate further? It seems to me that the settings dialog opens as a new page within the terminal window, rather than as separate windows."
1677625,2017-03-31 02:26:31 UTC,"Oh it's a new terminal app ""from overlay PPA""."
1677625,2017-03-31 17:44:55 UTC,":D yep, so terminal is installed from here https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/?field.series_filter=zesty"
1677627,2017-04-05 12:54:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453623"
1677627,2019-12-18 17:39:16 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/453623
Reason: This repo is retired now, no further work will get merged."
1677643,2017-03-30 14:35:35 UTC,"terminix seems to safegurad against this case, see attached (you can't resize the columns past a certain width)"
1677647,2017-04-25 22:49:33 UTC,"Reviewed:  https://review.openstack.org/457757
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=e94f7882cb7603723f993600b044cf9dcf544760
Submitter: Jenkins
Branch:    master"
1677647,2017-07-19 17:40:56 UTC,"Change abandoned by David Ames (<email address hidden>) on branch: master
Review: https://review.openstack.org/451603
Reason: Test only"
1677647,2020-02-03 11:38:49 UTC,Closing as it has been overtaken by events.
1677647,2017-03-30 14:46:33 UTC,Currently testing using http checks for backend services.
1677647,2017-04-18 18:15:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457757"
1677648,2017-03-30 14:51:39 UTC,same with horizontal
1677660,2017-04-05 09:02:00 UTC,"Original reporter cannot reproduce the issue on Zesty. Tested with deb, snap and from source.
Same here on Xenial."
1677660,2017-04-05 09:06:24 UTC,"I can’t reproduce this issue any longer. Neither with installed deb packages, nor with the app built from source, nor with a snap package. Marking invalid."
1677667,2017-08-16 09:30:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677668,2017-05-29 09:26:56 UTC,First of all thanks Jay for the great in depth extra-insight!
1677668,2017-05-24 14:53:47 UTC,"In our case, we don't need GARP on every boot.  Only during MaaS Deploy stage, where MaaS ephemeral boot image is trying to communicate with MaaS region controller (in a different VLAN)."
1677668,2017-04-04 19:50:05 UTC,"Hi Chris, Yes you are correct, and attached updated pic."
1677668,2017-04-03 06:11:49 UTC,"Hi Sam,
so in your picture we should add a RACK controller on Switch A and DHCP/TFTP goes there right?"
1677668,2017-05-23 01:00:21 UTC,"Sam / Christian,"
1677668,2017-03-31 19:56:54 UTC,attached pic
1677668,2017-03-30 15:59:21 UTC,"Forgot to mention that we didn't want to ""Static assign"" IPs in MaaS.  We prefer using ""Auto assign"" but observed that MaaS will sometimes reuse a previously used IP from a different MaaS machine.  But using ""Static assign"" we can reliably workaround the issue (or in this ticket case, force a failure on demand)"
1677668,2017-03-31 09:19:56 UTC,"Hi Sam,
to get this right it correctly PXE boots and starts the ephemeral with cloud-init to eventually produce the message."
1677668,2017-03-31 20:00:51 UTC,"I forgot to mention, Region and Rack Controllers are in separate VLANs.  So the TFTP conversation is happening between the RACK Controller (DHCP/TFTP) and the Machine which both live on the same subnet, so the router's ARP Cache is not a factor."
1677668,2017-03-31 19:47:13 UTC,"Hi Chris,"
1677668,2017-03-31 19:47:57 UTC,yikes! that did not format well...and I can't edit my own comment.  Let me try again...
1677677,2017-04-04 11:02:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453124"
1677677,2017-05-09 01:30:26 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/453124
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1677677,2017-05-17 18:31:38 UTC,Is there any known workaround for getting a Fuel deployed cluster with working Horizon? I have been wrestling with this issue for days. Changing the keystone endpoints to be versionless does not remediate.
1677677,2017-05-18 00:15:52 UTC,"Derek,"
1677677,2017-07-17 07:04:20 UTC,I deleted the endpoints as per:
1677684,2020-08-18 17:02:24 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1677684,2020-04-09 14:50:27 UTC,This bug was fixed in the package corosync - 3.0.3-2ubuntu2
1677684,2020-03-19 21:37:44 UTC,This issue still exists and should be fixed. I'm putting together with some other SRUs so all of them are done at once. Thanks @niedbalski for bringing up this issue. I'll fix Ubuntu Focal for now and try to get along with the needed SRUs.
1677684,2017-08-30 09:24:25 UTC,"Reflecting Eric's comment in #16, there is nothing left to do for ~ubuntu-sponsors (a follow-up is needed) so I am unsubscribing ~ubuntu-sponsors. If this was done in error, please feel free to resubscribe ~ubuntu-sponsors."
1677684,2020-03-30 01:16:12 UTC,"BUG: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1869622
PPA: https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging"
1677684,2017-04-05 19:53:23 UTC,"Hello Christian,"
1677684,2017-08-04 14:41:38 UTC,"Hi Jorge,"
1677684,2017-03-31 09:30:40 UTC,"This is a bit too much ""nobody cares on yakkety"" as after the fix it will appear as regression X->Y upgrades. Yet the fix should be just the same, but sponsors should mind that.
Jorge would you ack that the same should go to Yakkety or are there reasons not to be seen too obviously that speaks against that?"
1677684,2017-03-31 09:32:01 UTC,"Just checked that it applies to Yakkety as I assumed, nominating for that as well."
1677684,2018-06-27 09:42:37 UTC,"Clearing dormant bugs and efforts on this seem to have died, I'm setting incomplete to all tasks for now."
1677684,2017-03-31 12:30:17 UTC,"Hello Christian,"
1677684,2017-04-03 09:23:17 UTC,"Thanks already Jorge,
still would you mind explaining why it is (>= 0.12) ?"
1677684,2017-03-31 09:34:15 UTC,"Checked that libqb-dev is in main back to Trusty and it is, so it would not be an unexpected component mismatch."
1677685,2017-05-12 20:12:21 UTC,SRU submitted.
1677685,2017-05-10 20:20:04 UTC,"------- Comment From <email address hidden> 2017-05-10 16:12 EDT-------
Works fine"
1677685,2017-05-09 21:40:15 UTC,Can you please test the kernel in https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/test/ and report back here?
1677685,2017-05-09 18:19:13 UTC,Default Comment by Bridge
1677685,2017-05-08 17:10:06 UTC,"------- Comment From <email address hidden> 2017-05-08 13:02 EDT-------
target: Avoid mappedlun symlink creation during lun shutdown
https://patchwork.kernel.org/patch/9653217/"
1677685,2017-03-30 17:49:36 UTC,"------- Comment From <email address hidden> 2017-03-30 13:48 EDT-------
They are targeted for Yakkety, and the last one was submitted by the maintainer, so essentially it's pretty much accepted."
1677685,2017-03-30 17:23:44 UTC,The first 6 patches are already merged upstream and are present in Zesty. The 7th has yet to be accepted by a maintainer. To what releases are these patches targeted ?
1677685,2017-03-30 16:49:39 UTC,Default Comment by Bridge
1677685,2017-03-30 16:49:36 UTC,Default Comment by Bridge
1677685,2017-03-30 16:49:35 UTC,Default Comment by Bridge
1677685,2017-03-30 16:49:33 UTC,Default Comment by Bridge
1677685,2017-03-30 16:49:32 UTC,Default Comment by Bridge
1677685,2017-03-30 16:49:41 UTC,Default Comment by Bridge
1677685,2017-03-30 16:49:37 UTC,Default Comment by Bridge
1677687,2017-03-30 17:02:35 UTC,https://github.com/openstack/openstack-manuals/blob/master/doc/ha-guide-draft/source/intro-ha-key-concepts.rst
1677687,2019-05-16 13:26:00 UTC,created: https://storyboard.openstack.org/#!/story/2005721
1677689,2017-03-31 06:37:25 UTC,versions prior to SikuliX version 1.1.1 (http://sikulix.com) are no longer supported.
1677690,2019-05-21 09:31:57 UTC,created https://storyboard.openstack.org/#!/story/2005743
1677692,2019-05-21 09:53:55 UTC,created: https://storyboard.openstack.org/#!/story/2005744
1677719,2017-03-30 20:56:46 UTC,"Hi Olivier,"
1677719,2018-12-21 21:03:32 UTC,"Hi Tathagata,"
1677719,2017-07-24 18:31:14 UTC,"Thanks Olivier for the message! Please take your time in addressing the
problem."
1677719,2017-07-24 13:38:46 UTC,"Hi,"
1677719,2017-06-26 03:52:50 UTC,"Thanks Olivier for your detailed answer. Following your lead I double
checked the results for P1 and P2. In fact, all the errors are coming from
P2 process indeed with no errors from P1."
1677719,2017-06-19 21:20:40 UTC,"Hi,"
1677719,2017-03-30 20:41:54 UTC,"Hi,"
1677719,2017-06-08 06:22:44 UTC,"Hi Tathagata,"
1677719,2017-06-05 20:36:52 UTC,"Hi Tathagata,"
1677719,2017-06-19 19:31:31 UTC,"Hi Benjamin,"
1677719,2017-04-03 09:29:38 UTC,"Hi Tathagata,"
1677719,2017-06-05 06:52:20 UTC,"Hi Olivier,"
1677719,2017-04-01 04:40:37 UTC,"Hi Olivier,"
1677719,2017-04-01 04:42:40 UTC,"The error message I received was ""No handler matched request to /register"".
Sorry I misprinted the error message in my previous email."
1677719,2017-04-01 05:26:48 UTC,One of the FR author is active on Launchpad as well. So I'm assigning this question to him.
1677719,2017-03-30 21:51:35 UTC,"Hi,"
1677719,2017-04-03 05:53:43 UTC,"Hi Benjamin,"
1677719,2017-04-03 08:03:00 UTC,"Hi Tathagata,"
1677719,2017-04-03 08:17:11 UTC,Thanks Benjamin!
1677719,2017-04-01 09:26:04 UTC,"Hi Tathagata,"
1677719,2017-06-08 00:51:02 UTC,"Hi Benjamin,"
1677721,2017-04-03 12:54:02 UTC,"Fix committed into lp:unity-system-compositor at revision 312, scheduled for release in unity-system-compositor, milestone Unknown"
1677722,2017-04-08 23:23:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677727,2017-04-03 17:35:48 UTC,"After further research issue is not with lightdm, there still were some xorg and lxde packages missing."
1677727,2019-07-17 12:51:13 UTC,Can you reproduce this with stretch or buster?
1677727,2019-09-16 04:17:33 UTC,[Expired for Raspbian because there has been no activity for 60 days.]
1677733,2017-03-31 11:51:29 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1677733,2020-07-03 05:06:46 UTC,DistroRelease: Kali 2016.2
1677734,2017-04-03 12:22:18 UTC,"Fix committed into lp:unity-system-compositor at revision 310, scheduled for release in unity-system-compositor, milestone Unknown"
1677743,2017-04-03 12:14:19 UTC,"Fix committed into lp:unity-system-compositor at revision 309, scheduled for release in unity-system-compositor, milestone Unknown"
1677745,2017-05-20 14:51:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677745,2017-04-04 21:30:58 UTC,"More information: as the bug report in Debian says, changing the driver to ""intel"" seems to fix the problem."
1677745,2017-05-20 17:25:21 UTC,Can confirm that this problem exists. Ubuntu 17.04 (stable)
1677746,2017-03-31 21:09:04 UTC,So I was running it with --config-file but there is no [ovs] section in any of the config files I was using.
1677746,2017-03-31 21:25:14 UTC,"Ok, so using --config-file must cause cfg.CONF to get created, and the default is ovsdb_interface=native, which triggers that check.  Someone will have to figure out how to change this since you specified the --no* arguments.  Thanks."
1677746,2017-03-31 20:53:24 UTC,I can't seem to reproduce this unless I use '--config-file ...' with a filename that has an [ovs] section.  Can you give the command-line you ran it with?
1677752,2017-03-30 21:25:54 UTC,"A good start would be RDO packaging:
https://review.rdoproject.org/r/gitweb?p=openstack/neutron-distgit.git;a=blob;f=openstack-neutron.spec;h=0e93478bf6987141800e8b0919076b58cc33d619;hb=refs/heads/rpm-master"
1677752,2017-03-30 21:27:07 UTC,"Or devstack:
https://github.com/openstack-dev/devstack/tree/master/files/rpms/neutron*"
1677818,2019-06-20 23:12:41 UTC,"As fetchmail is a service, it should have (at least) three types of tests:"
1677818,2019-07-05 22:46:56 UTC,This bug was fixed in the package fetchmail - 6.4.0~beta4-3ubuntu1
1677818,2019-07-08 15:29:11 UTC,"Looks like the upload closed the bug, but as mentioned there's at least one more test needing written before we can consider this complete."
1677824,2019-01-29 11:43:06 UTC,"This package has no build time self tests either, so lets bump severity a bit."
1677841,2019-08-16 14:24:09 UTC,This bug was fixed in the package elinks - 0.13~20190125-3ubuntu1
1677847,2017-03-30 22:00:57 UTC,Cleaning the StacktraceTop a bit to make it readable in launchpad:
1677853,2017-03-31 17:05:23 UTC,"All right, I assumed (in error) you already knew this issue was related to swatches (which I'm starting to doubt now)."
1677853,2017-03-31 23:32:43 UTC,"@Eduard: Thanks for your great advisement.
Here is the BT:"
1677853,2017-03-30 23:05:41 UTC,"Could you please post steps how to actually produce the crash, i.e. how to actually create swatches with illegal characters? Inkscape does not even allow me to create swatches with problematic names..."
1677853,2017-03-30 23:18:49 UTC,"Maybe related:
https://bugs.launchpad.net/inkscape/+bug/1508928
""Program crashed after adding new Chinese fonts"""
1677853,2017-03-31 11:08:56 UTC,"Since I haven't built full code in my environment, I try to debug the code in x84-64 ASM."
1677859,2018-05-07 10:16:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677862,2017-03-30 23:10:05 UTC,"On old Kubuntu 8.04 with OpenOffice 2.4, the problem could NOT be reproduced."
1677869,2017-12-11 12:25:10 UTC,"Hi,
I missed to realize this was an open bug in our overall dep8-missing-campaign.
I added it in [1] which is about to migrate soon."
1677896,2017-09-25 21:09:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677896,2017-09-25 21:10:47 UTC,Exactly the same here using Glade 3.18.3-1 under Ubuntu 16.04.3 LTS
1677896,2019-07-20 22:57:17 UTC,Still experiencing the same with Glade 3.22.1 on Ubuntu 18.04
1677901,2017-08-01 15:51:48 UTC,"Not sure why the bot missed it, but the patch is https://review.openstack.org/#/c/354621/"
1677903,2017-03-31 22:26:59 UTC,"on a second thought, please don't actually send mails."
1677903,2018-08-27 23:43:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1677913,2020-03-27 13:13:19 UTC,"as noted in https://review.opendev.org/#/c/456571/12
i am not sure this bug was ever valid.
i think the real issue was ooo url encoding extra params incorrectly."
1677913,2020-03-27 14:20:32 UTC,"FWIW https://libvirt.org/uri.html says it's RFC 2396 URIs, so ooo was correctly encoding it."
1677913,2017-03-31 10:04:49 UTC,"To be clear, this is needed because we get the destination host, and then substitute that into the locally configured URL pattern."
1677913,2017-03-31 10:31:43 UTC,"Yes, doc fix is the only option I can see. I raised this mostly just to highlight the issue. Fixing this would break any workarounds in place so it's best to continue with the deprecation of this config param."
1677913,2017-06-29 11:45:41 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1677913,2017-03-30 23:36:59 UTC,More complete list of options: https://libvirt.org/remote.html#Remote_URI_reference
1677917,2020-07-03 05:09:25 UTC,DistroRelease: Kali 2016.2
1677918,2017-03-31 00:01:13 UTC,"I first noticed this behavior in Mitaka, and am also seeing it in my Newton test cluster."
1677918,2017-03-31 03:00:20 UTC,Do you have a config drive?
1677918,2017-04-03 03:52:58 UTC,"No, the instances don't have a config drive - instance configuration is done through the metadata service."
1677918,2017-04-05 07:13:23 UTC,"Hi Patrick,"
1677918,2017-04-05 14:11:28 UTC,"[pvinas@cloud1 ~]$ openstack volume list
+-------------+----------------+-----------+------+-------------------------------------------+

| ID          | Display Name   | Status    | Size | Attached to                               |


+-------------+----------------+-----------+------+-------------------------------------------+

| <UUID>      | testvol        | available |    5 |                                           |
| <UUID>      | scanner-root   | in-use    |   12 | Attached to scanner on /dev/vda           |


+-------------+----------------+-----------+------+-------------------------------------------+"
1677918,2017-04-06 11:52:13 UTC,Thanks for your reply. working on this
1677918,2017-04-13 11:12:29 UTC,I have the same issue. When I try to add a cinder volume to a cinder based instance via the CLI I get the following debug output:
1677918,2018-01-12 19:03:41 UTC,Unassigning due to no activity for > 6 months.
1677937,2017-08-22 11:39:38 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1677937,2017-07-28 07:41:47 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1677937,2017-08-11 18:24:19 UTC,"Reviewed:  https://review.openstack.org/475902
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e74c207676db55edf44e70174cebfa48c7f5be48
Submitter: Jenkins
Branch:    stable/ocata"
1677937,2017-06-20 19:16:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/475902"
1677937,2017-06-20 01:13:28 UTC,"I have made another patch to fix this bug https://review.openstack.org/#/c/462017/, so abandon the previous https://review.openstack.org/451657"
1677937,2017-06-19 23:56:29 UTC,"Change abandoned by Huan Xie (<email address hidden>) on branch: master
Review: https://review.openstack.org/451657"
1677937,2017-06-21 06:32:43 UTC,"Reviewed:  https://review.openstack.org/462017
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d89fe544bd5b119ab6fe24d6a353240efbf5a491
Submitter: Jenkins
Branch:    master"
1677940,2017-03-31 12:33:40 UTC,"fwiw, it is the same case in the old design. XML/YAML output has always been expanded by default and has always been available."
1677940,2017-04-04 21:26:17 UTC,"I think it's strange that deployment output appears on the Commissioning tab; it seems like the current ""Machine output"" is a detail of commissioning, and deployment output should be called out separately somehow, either on a separate tab or collapsed by default as suggested."
1677940,2018-03-26 23:46:58 UTC,In 2.4 logs are only sent over the websocket when on the logs tab. This should help with the performance on all other pages. We could improve upon it some more by implementing paging with text files and caching results on the client. This effects commissioning and testing results as well.
1677940,2019-09-19 11:56:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1677941,2017-03-31 09:47:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452119"
1677947,2017-03-31 18:33:25 UTC,"Can you share more information on this, such as the tool you used for static analysis or more detailed output? Ideal would be the code path that your tool believes exhibits the behaviour."
1677947,2017-04-01 06:46:54 UTC,"According to OpenSSL document, a correct certificate chain validation
pattern is like this:"
1677947,2017-04-01 13:53:11 UTC,SSL_CTX_set_verify() is used to modify the default value in an SSL_CTX instance and that will apply to every SSL instance created from that SSL_CTX. SSL_set_verify() is used to set the parameter for each SSL instance. Either call can be used in general to do the same.
1677954,2019-11-13 21:10:51 UTC,"subiquity makes crash reports now, but there is no UI for reporting them yet."
1677958,2017-05-18 16:08:51 UTC,"Ruan, it's ok! Thank you for your detailed analyses. It sounds like this is still a potential security issue in 16.04, at least."
1677958,2017-05-17 15:54:15 UTC,"Hello Ruan,"
1677958,2017-05-18 03:07:06 UTC,"This problem can be closed .Sorry for disturbing you.For some reasons ,we do analysis on Ubuntu 16.04.,where the nghttp2 version is 1.7.1, NO SSL_set_verify(ssl, SSL_VERIFY_PEER, verify_cb) exists,so we can do MITM attack.
 We find in the lastest version 1.22.0,this bug has fixed.Thank for you timely reply and patience.Also apologize for my carelessness."
1677958,2017-05-03 14:19:30 UTC,The code maintainer have confirm the bug and  add a large text inside the source code to implement that is insecure for production use.
1677958,2017-05-16 17:48:45 UTC,"To be clear, this bug is in example code to demonstrate how one uses libnghttp2, not in any actual libnghttp2 code."
1677958,2017-05-17 05:18:22 UTC,"Nowadays We find in nghttp2-client  there exists other  bug .
In @src/nghttp.cc:
int HttpClient::initiate_connection()"
1677958,2017-05-01 17:45:18 UTC,Has this been reported upstream to nghttp2?
1677958,2017-05-01 17:46:02 UTC,"Also, 1.7.1 is only present in 16.04, there have been many updates to the package since then -- can you verify if it was fixed upstream already and at what version?"
1677959,2017-03-31 04:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1677959,2017-04-08 01:48:20 UTC,This bug was fixed in the package linux - 4.10.0-19.21
1677959,2017-07-26 15:57:30 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1677987,2017-04-21 07:51:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458755"
1677987,2017-04-30 12:09:33 UTC,"Reviewed:  https://review.openstack.org/458755
Committed: https://git.openstack.org/cgit/openstack/octavia/commit/?id=7100872ddb56397e4e9414ffeb17663ca54dc5d0
Submitter: Jenkins
Branch:    master"
1677987,2017-05-05 08:53:58 UTC,"Hey,"
1677987,2017-07-31 23:49:43 UTC,"@Marco,
I'm not sure if I understand the issues you're mentioning..."
1677989,2017-03-31 06:55:54 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/452064"
1677989,2017-04-04 11:54:38 UTC,"Reviewed:  https://review.openstack.org/452064
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=1bbd8cc067d440e08f36d546ee4adbaa298e1801
Submitter: Jenkins
Branch:    stable/newton"
1677995,2019-12-18 17:21:18 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/453108
Reason: This repo is retired now, no further work will get merged."
1677995,2017-03-31 08:00:16 UTC,"I believe it's issue of environment settings.
Timeout of cgroup task is 2 min (could be increased) for install packages and set cgroups settings."
1677995,2017-03-31 08:02:43 UTC,There is custom test: https://custom-ci.infra.mirantis.net/job/10.0.custom.system_test/1558/
1677995,2017-04-04 10:31:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453108"
1677996,2017-03-31 08:58:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452106"
1678022,2019-03-28 21:12:45 UTC,"Reviewed:  https://review.openstack.org/648245
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=6afc1130fd753306d64745c9bee7712182b273d3
Submitter: Zuul
Branch:    feature/losf"
1678022,2019-03-25 17:07:14 UTC,This issue was fixed in the openstack/swift 2.21.0 release.
1678022,2019-03-27 21:11:09 UTC,"Fix proposed to branch: feature/losf
Review: https://review.openstack.org/648245"
1678022,2019-03-21 16:41:57 UTC,"Reviewed:  https://review.openstack.org/571905
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=fa678949ae310aa0499938fef788ec04409625d9
Submitter: Zuul
Branch:    master"
1678022,2017-03-31 12:52:25 UTC,"> but the content of the manifest file is in my initial report.
"
1678022,2017-04-20 18:36:03 UTC,"Hi Janie,"
1678022,2017-04-20 18:25:23 UTC,"Oh, I see the comment now about the double-encoded brackets.  I tested using the same problem sub-directory, and I reproduced your issue if I use the decoded versions in the manifest.  But if you use the encoded versions in your manifest, with:
""/OpenOffice.org%203.3%20%2528en-GB%2529%20Installation%20Files/""
then the GET on the large object will be successful.  Does that solution work for you?  I am actually not sure if swift claims to handle the double-encoding example.  I will have to research that to see if this is a bug.  But I am interested in solving your problem."
1678022,2017-04-19 21:32:28 UTC,"I have created an SLO manifest with a name that uses ( and ).  The segments inside the manifest had names with these characters as well.  This, alone, did not reproduce an error.  I see that there are psuedo directories in the names here, so I will test that as a next step.  I am trying to gradually add the layers of complexity in the name to see what exactly is causing your error."
1678022,2017-03-31 11:18:36 UTC,"@donagh-mccabe it's a little difficult to read, but the content of the manifest file is in my initial report. I've prettified it for readability:"
1678022,2017-07-20 22:11:47 UTC,"Including python-swiftclient, too, since I'm not sure yet whether this should be considered a client or server issue."
1678022,2017-03-31 11:04:03 UTC,"You don't show us the contents of your manifest file, but at a guess, you have put the URL-encoded version of the object name in the manifest - not the actual object name."
1678023,2017-03-31 09:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678023,2017-04-08 01:48:20 UTC,This bug was fixed in the package linux - 4.10.0-19.21
1678023,2017-07-26 15:57:32 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1678024,2017-04-01 02:05:59 UTC,"An error volume is still a volume. IMO, it should be counted by quota.
Quota is a db record resource, so it is only related to db change. It doesn't care about the driver's status."
1678024,2017-04-06 05:26:41 UTC,"You made some good points.I got your point.
Could you please explain one things to me."
1678024,2017-04-06 05:48:38 UTC,"yes wangxiyuan is right, error volume must occupy some quota. however, in such cases a notification must be send to admin regarding such volumes which are in error state. so that necessary action can be taken."
1678030,2017-03-31 10:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678030,2017-07-26 15:57:35 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1678030,2017-04-08 01:48:20 UTC,This bug was fixed in the package linux - 4.10.0-19.21
1678032,2017-03-31 10:00:22 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678032,2017-04-08 01:48:20 UTC,This bug was fixed in the package linux - 4.10.0-19.21
1678032,2017-07-26 15:57:37 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1678036,2017-06-14 09:04:32 UTC,We'd have to be quite careful about this to avoid LP's standard linkification code doing more than we want and making it difficult to see the raw text of diffs.
1678036,2017-06-14 10:36:21 UTC,"> I would note that this would have been much easier for you if the commit message had simply quoted the bug numbers in the proper style...
"
1678043,2020-12-02 00:03:42 UTC,This bug was fixed in the package ceres-solver - 1.11.0~dfsg0-2ubuntu0.1
1678043,2020-12-01 23:55:34 UTC,"The verification of the Stable Release Update for ceres-solver has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1678043,2020-12-01 16:31:15 UTC,This package fixes the bug for me.
1678043,2020-11-24 19:27:56 UTC,"Hello Christian, or anyone else affected,"
1678043,2017-04-17 12:08:04 UTC,"Well, I have no idea why cmake does not find Ceres in /usr/include/ceres/."
1678043,2017-06-02 23:54:20 UTC,"Hi,"
1678043,2017-04-04 07:12:10 UTC,"Ah, sorry. I posted the cmake version..."
1678043,2017-04-04 06:33:26 UTC,"That can't be right.
The version is one of"
1678043,2017-04-03 08:24:32 UTC,3.5.2-2ubuntu1
1678043,2017-03-31 18:39:53 UTC,Please state the package version.
1678043,2020-11-19 11:26:11 UTC,ACK on the updated debdiff. I've uploaded it for processing by the SRU team after fixing the LP bug tags in the changelog.
1678048,2017-07-26 15:57:39 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1678048,2017-03-31 11:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678048,2017-04-08 01:48:20 UTC,This bug was fixed in the package linux - 4.10.0-19.21
1678048,2017-03-31 10:36:31 UTC,This is because boot params are processed before apparmor is fully initialized and policy_view_capable() will oops because the rootns is not setup.
1678052,2019-10-30 15:37:37 UTC,"Same feature request for Nautilus:
https://gitlab.gnome.org/GNOME/nautilus/issues/817"
1678052,2019-03-22 20:24:38 UTC,"@Kirill Afonin
Your bug was about the ""color of a folder"", not about emblems.
Emblems work fine for me .. they dont work for you ? If so, please open a separate bug for it."
1678052,2019-03-22 13:50:22 UTC,"alexxcons  editbugs 2019-03-22 13:47:55 CET
Well, if you dont want to use the workaround, I am sorry."
1678052,2017-03-31 10:35:20 UTC,"Hi,"
1678052,2019-03-22 12:44:35 UTC,"reopened, since there seems to be some demand. Even if there is no manpower to implement such a feature curently, duplicates can be closed against this bug"
1678052,2018-01-24 14:41:27 UTC,Sorry for the late reply!
1678052,2019-03-22 12:47:55 UTC,*** Bug 15208 has been marked as a duplicate of this bug. ***
1678052,2017-03-31 10:45:25 UTC,"Or maybe, I should delete it here as it is an enhancement and not a bug..."
1678056,2019-04-30 20:54:16 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/391060
Reason: We purge request specs when archiving deleted instances now so let's drop this."
1678056,2018-09-24 14:46:49 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1678056,2018-07-06 21:52:55 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580775"
1678056,2017-12-07 23:56:05 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1678056,2019-10-07 14:19:59 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/484694"
1678056,2017-11-08 14:54:35 UTC,Update : The latest revision of the fix for this is https://review.openstack.org/515034 (looks like gerrit hooking didn't work).
1678056,2017-11-21 19:04:39 UTC,"Reviewed:  https://review.openstack.org/515034
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=32fd58813f8247641a6b574b5f01528b29d48b76
Submitter: Zuul
Branch:    master"
1678056,2017-06-23 12:55:23 UTC,"There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments."
1678056,2017-06-23 13:15:45 UTC,Seems like the gerrit hook didn't work https://review.openstack.org/391060
1678056,2018-07-26 01:14:29 UTC,"Reviewed:  https://review.openstack.org/580775
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=70de423255fd01822188bb9082a0c0cc1c8ec2d0
Submitter: Zuul
Branch:    stable/pike"
1678056,2017-07-21 09:20:51 UTC,Last revision is https://review.openstack.org/391060
1678056,2017-08-01 14:03:36 UTC,"This is not a pike-rc-potential bug in my opinion, it's a latent issue."
1678056,2017-07-18 09:38:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484694"
1678068,2017-06-26 03:57:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678099,2017-03-31 15:53:14 UTC,"Leann,"
1678099,2017-04-03 15:57:21 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-April/083452.html
1678099,2017-04-03 16:08:42 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-April/083454.html
1678099,2017-04-13 16:16:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1678099,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1678099,2017-04-24 14:11:40 UTC,This bug was fixed in the package linux - 4.8.0-49.52
1678099,2017-04-13 16:14:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1678112,2017-04-20 21:01:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678112,2019-04-03 21:16:55 UTC,This bug is still present in ubuntu 18.04.2
1678112,2019-06-23 08:30:26 UTC,This bug is still present in ubuntu 19.04
1678112,2020-05-18 22:13:22 UTC,Still happening in 20.04.
1678112,2020-06-25 15:40:39 UTC,"grub2 used to support lvm2 cache partitions, in a buggy way, corrupting them on boot/grubenv read or write."
1678119,2017-04-17 09:55:54 UTC,"Even after copying the missing header to /usr/include/linux/ on my system, I’m getting build failures:"
1678119,2017-04-17 08:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678119,2017-04-17 07:24:46 UTC,"This is a bug in the kernel package, fixed by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2220fc1ab363e6fab1f321430d69be17a8b92bd7."
1678119,2017-04-17 09:41:23 UTC,"apport-collect won’t let me share more info because I’m not the one who filed the bug.
But in that case the version signature should be enough information:"
1678130,2017-03-31 15:01:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452239"
1678130,2017-03-31 15:02:57 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/452240"
1678130,2017-04-03 06:32:01 UTC,Since all branches are affected modify the title and description. Don't mention only newton.
1678130,2017-04-03 13:32:49 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.openstack.org/452239
Reason: Will be handled by https://review.openstack.org/#/c/451710/"
1678130,2017-04-03 13:32:54 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/452240
Reason: Will be handled by https://review.openstack.org/#/c/451710/"
1678130,2017-05-22 14:28:43 UTC,Commit merged for newton https://review.openstack.org/#/c/464078/
1678131,2017-04-03 11:15:22 UTC,"These changes went into 2.4.17-1 which is >=Xenial.
So as requested only Trusty is needed."
1678131,2017-04-03 11:17:22 UTC,If you could find the time to prepare all that is needed for an SRU process here by adding a SRU Template [1] that will help a lot.
1678131,2017-04-05 14:45:31 UTC,"I'd be thankful if you could help creating a verification testcase.
You said you see it ""on trusty on every upgrade of libapache2-mod-php5, when ITK is used.""
Could you outline the minimum config changes from a clean trusty system that you need to do to run into this?
I'd guess you need to install the fixed apache version and then upgrade libapache2-mod packages right to be able to confirm a fix?
I can create fake libapache2-mod-php5 version bumps if needed to trigger, but I want to make sure I match your setup to actually cause the issue."
1678131,2017-04-05 14:50:31 UTC,It seems I screwed up the versioning - let me double check and re-push to the PPA if needed.
1678131,2017-04-05 14:51:33 UTC,"No was a false-positive warning on the tooling against trusty-backports, should be fine as-is."
1678131,2017-05-09 16:51:54 UTC,"Adding bitesize to make it more likely to be picked up soon.
FYI - another update is out so the ppa we had so far has its version number burned."
1678131,2020-05-05 20:32:16 UTC,Trusty ended standard support April 2019
1678134,2017-04-17 10:29:40 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/452228
Reason: Abandoning as it was decided to write a spec around this during an ironic meeting: http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-04-03-17.00.log.html#l-250."
1678134,2017-03-31 14:43:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452228"
1678155,2017-03-31 16:45:37 UTC,Note that credit card info is encrypted and relies on storing a key in the session secret service by default.
1678160,2017-03-31 15:03:23 UTC,"Maybe a callback property on the webview: if unset (default), no extra item is displayed in the suggestions popup, and if set the extra item is shown and clicking it invokes the callback."
1678177,2017-04-03 02:15:15 UTC,We might have to clarify or split this bug:
1678177,2017-04-04 05:21:35 UTC,"same with the gtk menus, test with sol
see screenshot"
1678177,2017-03-31 15:06:01 UTC,"also now qupzilla is acting funny even without moving the window, the search list is now paces in random weird places, see screenshot"
1678179,2017-03-31 15:05:58 UTC,"Err, that last sentence isn't actually true - the built in login DB is encrypted, but it uses the system password storage (eg, libsecret) for storing a key"
1678181,2017-04-04 10:51:07 UTC,duplicated with https://bugs.launchpad.net/python-openstackclient/+bug/1657956
1678181,2017-04-10 10:46:21 UTC,"Sorry, I can't reproduce the bug in my latest devstack env, I used the current master openstackclient, what's your osc and cinderclient version?"
1678181,2017-04-10 11:05:01 UTC,"I didn't noticed the bug created by you. You have fixed this bug, right?"
1678181,2017-04-24 10:09:09 UTC,"Weird, I didn't fix anything about the bug."
1678181,2017-04-24 13:03:51 UTC,I think this patch can fix the bug. https://review.openstack.org/#/c/423081/
1678187,2017-09-29 21:38:49 UTC,"I think source of the problem here is bug 1501844 and removing a linux-image-extra package causes update-initramfs to be run. If the kernel package maintainer scripts were written differently then removing linux-image and linux-image-extra would not have a problem if /boot was full, but removing linux-image-extra by itself would still be an issue as update-initramfs would be run."
1678187,2017-09-26 16:32:00 UTC,"I've recreated this on Ubuntu 16.04 now, it seems that the missing bit was creating a sufficiently small enough amount of free space on my /boot partition."
1678187,2017-09-26 16:51:11 UTC,Then not incomplete anymore?
1678187,2017-09-22 21:41:45 UTC,Tested in 16.04
1678187,2017-10-14 11:19:47 UTC,"As for the patch, the following test shows that a file stored in /boot may require significantly more available space than the same file in /var/tmp, even if blocksize in (partition containing) /var/tmp is bigger. I don't know what is the best way to estimate how much available space is needed for storing a file in /boot."
1678187,2017-10-14 12:03:46 UTC,A new attempt to estimate required space in /boot.
1678187,2019-01-12 04:53:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678187,2017-10-10 19:57:21 UTC,"For some reason with my patch mv may fail even if I try to make sure mv will not be run, if there is not enough space on /boot:"
1678187,2017-09-21 22:55:10 UTC,Using the same procedure I was unable to recreate this on Ubuntu 16.04.
1678187,2017-09-30 06:52:30 UTC,There is no bug with that number.
1678187,2017-09-19 18:54:45 UTC,"patch version 2 is also against (then) current
https://git.launchpad.net/~usd-import-team/ubuntu/+source/initramfs-tools/tree/update-initramfs"
1678187,2017-09-21 22:44:56 UTC,"I tried recreating this in Ubuntu 17.04 by having three kernels installed on a /boot partition with only 11M of free space left. I then used 'sudo apt autoremove' which removed my oldest kernel, including linux-image-extra-4.10.0-19-generic, and did not run into any issues. Is this issue specific to only removing the linux-image-extra package or does it only affect Ubuntu 16.04.?"
1678187,2017-04-24 12:10:57 UTC,What triggers a postinst script when removing a linux-image-extra package by dpkg?
1678187,2017-04-25 09:36:22 UTC,"dpkg may also fail to install a linux-image-extra package, because ""update-initramfs -c"" needs more space for initrd.img in /boot temporarily, even if the new initrd.img would fit when the old one has been removed."
1678187,2017-05-09 15:12:31 UTC,I managed to change update-initramfs in my computer so that it uses a temporary location (temporarily) for new initrd.img file thus behaving better in case of separate /boot partition and low disk space there.
1678187,2017-08-03 22:09:44 UTC,Patch against current https://git.launchpad.net/~usd-import-team/ubuntu/+source/initramfs-tools/tree/update-initramfs
1678187,2017-07-01 22:11:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678187,2017-08-12 14:16:14 UTC,"This patch is better, because it takes into account the size of possible existing initramfs file  when calculating the needed available free space."
1678187,2017-05-20 07:57:34 UTC,Maybe also dkms may need more space on /boot when updating and backing up initrd.img?
1678187,2017-08-04 00:23:22 UTC,"The attachment ""patch concerning generate_initramfs function in update_initramfs"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1678187,2017-07-01 22:12:54 UTC,"Not sure if using dkms, but if so may be related to bug 1515513"
1678190,2017-04-14 17:08:07 UTC,This is being tested now.
1678199,2017-03-31 15:16:17 UTC,"Woops, I thought I was reporting on http://hplipopensource.com, not on launchpad.net.
It a duplicate of https://bugs.launchpad.net/hplip/+bug/307152."
1678200,2017-04-03 09:08:55 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1678200,2017-04-03 14:32:01 UTC,https://github.com/torvalds/linux/blob/v4.11-rc5/drivers/platform/x86/intel-vbtn.c#L38
1678200,2017-03-31 15:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678202,2017-04-03 13:02:26 UTC,"Fix committed into lp:unity-system-compositor at revision 313, scheduled for release in unity-system-compositor, milestone Unknown"
1678204,2017-04-23 18:30:20 UTC,"we received a similar feedback several time. I think it is time to revisit the current behavior.
If a log-in form is displayed, many users feel they need to log-in again even though there is a message that you can click the link shown to go back to the project page (or something)."
1678204,2017-04-23 18:34:17 UTC,I also see more tricky behavior.
1678204,2017-10-25 20:36:54 UTC,"This
""Other admin tabs affected differently. For example, switching projects from the Admin->System->Hypervisors tab will show the page template with no data."
1678204,2017-10-25 21:11:14 UTC,"The main issue has been fixed, so I am setting a lower priority for this."
1678204,2018-09-06 07:50:51 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/465811
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1678204,2017-10-25 18:57:28 UTC,Is it a duplicate of https://bugs.launchpad.net/horizon/+bug/1709077?
1678208,2017-03-31 16:00:10 UTC,This change was made by a bot.
1678212,2017-03-31 15:57:13 UTC,"Description:    Ubuntu 16.10
Release:        16.10"
1678212,2017-03-31 19:30:14 UTC,"By the way, the problem is the same with a Cambridge Silicon Radio bluettoth USB dongle or with the integrated BCM2046 integrated bluetooth chipset of my laptop."
1678215,2019-09-19 12:03:25 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1678215,2017-03-31 16:19:43 UTC,"Hi There,"
1678262,2017-04-01 02:43:30 UTC,"On 31/03/17 10:19, Rufus Laggren wrote:

> Public bug reported:
>
> When dealing with 100k++ number of files it would GREATLY, HUGELY help
> if one could build, on the fly, a list of ""preferred dirs"". When
> activated (various ways possible) the ""preferred dirs"" feature would,
> when a ""preferred dir"" existed in a group, automatically select dupes
> (lines) within each group which did NOT contain the ""preferred dir"".
> When the ""preferred dirs"" feature left more than ""n"" line(s) unselected
> in a group (multiple files w/same ""preferred dir"", or multiple
> ""preferred dirs"" in same group) those groups would (optionally, set in
> preferences) be highlighted for easy identification for further
> selections; alternatively, groups with n unselected lines or less (see
> below), based on ""preferred dirs"", could be hidden or auto-collapsed
> which would leave normal groups, or those w/too many unselected lines,
> visible for normal editing. Thinking about it, the second options seems
> cleaner, less ""busy"", an easier interface to work with. A group could
> not be highlighted, hidden or collapsed unless it contained ""preferred
> dirs"".
>
> There are probably other useful perversions of this idea possible but I
> only can visualize the above at this point. The ""n"" number maybe could
> be made part of processing each group and serve additional functions but
> I have not tried to evaluate that, especially not knowing the logic flow
> you use.
>
> The preferences setting could:
>
> 1) Enable/disable the feature.
>
> 2) Spec n where ""number of unselected lines"" > n either causes
> highlighting, or disable hide/collapse for that group. Default n=1.
>
> 3) Select highlighting, hide/collapse, or ""no special display"" for
> groups altered by this feature.
>
> Usage: On the fly, when working with a group, one could rt-click on the
> _unselected_ line(s) and add the dir on that line to a ""new preferred""
> list; when satisfied, the ""new preferred(s"" would be posted to the
> active ""preferred dirs"" list. (The rt-clk context menu could have the
> top choice ""add single dir"" and the second choice ""add multiple dirs"" so
> that the common(?) case where there is only one ""preferred dir"" would be
> quick and easy.) The new items would be active immediately in the
> current session. If no ""preferred dirs had been defined yet for this
> session or if a list had not been loaded, the ""add dir"" click would open
> a ""new list"" dialog. Once defined or loaded for a session, that
> ""preferrred dirs"" list would be used automatically for all succeeding
> processing (dupe selection) until the ""preferred dirs"" context menu or
> dialog was invoked again (by rt-clicking on an unselected line). Ideally
> a config file containing this list and other options defined for this
> session could be automatically associated with a saved search and
> loaded, eg. from the ""File"" menu.
>
> It would be greatly helpful if the auto-selections would be immediately
> applied. This instant clutter reduction would greatly speed and simply
> subsequent selection process resulting in a huge time savings.
>
> Fslint is a fine, Fine tool. It's just that wading into gigabytes of
> overgrown data direct...
"
1678262,2018-04-22 02:48:46 UTC,It sure sounds awfully complicated.  Please don't overengineer this.  It absolutely sounds like this could already be achieved by bind-mounting.
1678262,2018-05-10 14:38:31 UTC,"> accomplished with ""bind-mounting""...
"
1678268,2017-03-31 17:51:19 UTC,Update:  Running with logging.DEBUG I see what may be helpful:
1678268,2017-04-04 17:00:47 UTC,Correction:  No OS_CLOUD_NAME and OS_* env. vars. are set
1678268,2017-04-04 16:59:21 UTC,"Update: After some experimenting, I found that using os_client_config.OpenStackConfig().get_one_cloud(NAME) works around this problem.  If I do not specify a NAME, and there is no OS_CLOUD_NAME env var set, the bug reproduces."
1678270,2017-03-31 17:54:31 UTC,also probably related https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1678251
1678270,2017-03-31 18:17:06 UTC,maybe the detached windows are clip/project monitor
1678292,2017-04-01 07:45:17 UTC,"I would disagree that this is a bug. It works the same way as other auto completers do, just try few examples in OpenLP and Google. I think its best to emulate the way others do it from a usability point of view."
1678292,2017-04-01 09:55:58 UTC,"The added space is expected by the user because if
they use the auto completion they expect to be able
to just type in the numbers after that. It’s also faster."
1678299,2017-04-03 06:01:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678308,2017-04-01 11:40:18 UTC,"I solved the problem, when I replaced inside of
  ~/.config/libfm/libfm.conf
the line
  terminal=lxsession-default-terminal %s
by
  terminal=lxterminal %s
."
1678308,2017-04-01 11:04:01 UTC,"After I tried ""lubuntu"" instead of 'lxde"" as desktop manager, all worked like expected."
1678308,2017-03-31 20:45:32 UTC,"What if you navigate to the path in terminal and then try to open a new terminal? Which path is this and which USB device? The output of `lsusb` and assuming this is a block device, `lsblk` might be useful.
--
       @wxl | polka.bike
C563 CAC5 8BE1 2F22 A49D
68F6 8B57 A48B C4F2 051A"
1678308,2017-04-01 10:36:06 UTC,"I started ""lxterminal &"" from the terminal in the USB path
  /media/dirk/32GB_USB3_Dirk
successfully, and this works from everywhere."
1678308,2017-03-31 20:24:57 UTC,"StacktraceSource:
 #0  0x000055940afcca54 in terminal_new.constprop ()
 #1  0x000055940afcd958 in lxterminal_initialize ()
 #2  0x000055940afc8a02 in main ()
StacktraceTop:
 terminal_new.constprop ()
 lxterminal_initialize ()
 main ()"
1678314,2019-03-22 16:11:34 UTC,"Hey Rodrigo I was wondering if there was any new updates on this issue. It has not been updated in two years, is this no longer an issue or possibly a wish list item? Setting to low until we have more of a feel of what is going on here..."
1678320,2017-05-03 01:07:53 UTC,Same thing here! Help!
1678320,2017-05-03 01:21:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678320,2017-09-21 09:40:01 UTC,"openarena
ioq3 1.36+u20161101+dfsg1-1/Ubuntu linux-x86_64 Nov  5 2016
Have SSE support
----- FS_Startup -----
We are looking in the current search path:
/home/gsl/.openarena/baseoa
/usr/lib/openarena/baseoa
/usr/lib/openarena/baseoa/z_oacmp-volume1-v3.pk3 (370 files)
/usr/lib/openarena/baseoa/pak6-patch088.pk3 (711 files)
/usr/lib/openarena/baseoa/pak6-patch085.pk3 (559 files)
/usr/lib/openarena/baseoa/pak6-misc.pk3 (229 files)
/usr/lib/openarena/baseoa/pak5-TA.pk3 (139 files)
/usr/lib/openarena/baseoa/pak4-textures.pk3 (1753 files)
/usr/lib/openarena/baseoa/pak2-players.pk3 (669 files)
/usr/lib/openarena/baseoa/pak2-players-mature.pk3 (231 files)
/usr/lib/openarena/baseoa/pak1-maps.pk3 (100 files)
/usr/lib/openarena/baseoa/pak0.pk3 (1042 files)"
1678320,2017-12-09 20:04:28 UTC,"7 years ago, pulseaudio did this to OpenArena. I tried that solution and it didn't solve this case. However, this has been reported repeatedly since 2010 - I'd almost go so far to say ""on every incarnation of Ubuntu""."
1678320,2018-10-27 14:38:47 UTC,"Got the same error ""openal capture device closed"" in Kubuntu on KDE, so the issue is not Gnome specific."
1678320,2019-02-17 18:14:30 UTC,Ive got the same error under linux mint 19 xfce edition
1678320,2017-04-01 20:58:14 UTC,"This bug also affects me. I'm using an inspiron b120 laptop, and this is the last bit of the log that I get when I start a match."
1678326,2017-06-15 15:40:23 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/452346"
1678326,2017-04-14 09:22:12 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1678326,2017-04-12 18:55:05 UTC,This issue was fixed in the openstack/nova 15.0.3 release.
1678326,2017-04-12 17:14:29 UTC,"For anyone confused, Ie2063f621618c1d90aeb59f0f1d7da351862ea9f was targeting the wrong bug, it doesn't fix this one, it fixes bug 1675570."
1678326,2017-04-10 13:31:28 UTC,"Reviewed:  https://review.openstack.org/454414
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6384e935be147d3f454c264703136c5e82eebafd
Submitter: Jenkins
Branch:    stable/ocata"
1678326,2017-04-07 01:56:34 UTC,"Reviewed:  https://review.openstack.org/453859
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9245bbf79ddbfd8a2e2310af654711f9d3a547b1
Submitter: Jenkins
Branch:    master"
1678326,2017-04-10 13:30:32 UTC,"Reviewed:  https://review.openstack.org/452364
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=361b88383130be8da9d474d02a9f62136239d506
Submitter: Jenkins
Branch:    stable/ocata"
1678326,2017-04-05 21:55:12 UTC,"Reviewed:  https://review.openstack.org/452359
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=42d4ea0b6289b1f26a44a95dcfadfc75587d7c2c
Submitter: Jenkins
Branch:    master"
1678326,2017-04-07 01:39:03 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/454414"
1678326,2017-03-31 23:00:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/452346"
1678326,2017-03-31 23:59:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452351"
1678326,2017-04-01 01:30:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452359"
1678326,2017-04-10 13:30:16 UTC,"Reviewed:  https://review.openstack.org/452363
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=01fa555b36055c1042e342d9f332f38e106d5d0d
Submitter: Jenkins
Branch:    stable/ocata"
1678326,2017-04-01 02:27:08 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/452364"
1678326,2017-04-05 20:32:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453859"
1678326,2017-04-05 21:54:34 UTC,"Reviewed:  https://review.openstack.org/452351
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=032937ce51c64e0f5292ca3149e3b244863fffca
Submitter: Jenkins
Branch:    master"
1678326,2017-04-01 02:26:57 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/452363"
1678327,2017-05-24 07:14:35 UTC,"sridhar, do you have time on it?
since it is marked as critical, we need to merge it as soon as possible."
1678345,2019-01-10 16:57:45 UTC,I made a repo with some example color schemes: https://github.com/pointhi/kicad-color-schemes
1678345,2019-01-20 23:22:35 UTC,"Hi
Here is my final solution:"
1678355,2017-05-24 00:31:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678355,2017-08-03 15:01:19 UTC,This issue is present in the Third Point release of Ubuntu 16.04 (Witnessed just now in Ubuntu MATE 16.04.3)
1678355,2017-08-03 17:24:50 UTC,"Looks like it's known upstream.
https://github.com/micahflee/torbrowser-launcher/issues/282"
1678385,2017-04-01 07:01:53 UTC,"I cannot find report of such a bug on the net, so I am expecting this to be a packaging bug, but really I have no idea..."
1678385,2017-04-01 12:18:49 UTC,"Hi Olivier,"
1678385,2017-04-01 13:58:05 UTC,"I will. I see now that qt5 on Wayland also crashes, etc. I thought Wayland
was supported..."
1678385,2017-04-01 15:50:01 UTC,"Wayland is supported, although maybe we (the maintainers in Ubuntu) do not have much time to test it."
1678389,2017-04-01 07:10:23 UTC,"1 - names of the renamed bookmarks from nautilus should be used
2 - order from nautilus bookmarks should be used
3 a faster way to scroll down or recent documents folder should be moved to the top or all places / bookmarks should be in its own folder next to recent documents so that you can choose bookmarks / places or recent files easily on the same page without having to scroll down"
1678389,2017-04-01 07:50:14 UTC,"Hi Lili,
Thanks for the report. I am however not sure what you mean:
- If I rename a bookmark, its name is immediately updated in the drop-down list.
- For clarity reasons, recent files are sorted in chronological order. I am not sure why scrolling is slow for you, possibly a GTK issue on your system. The application creates a straightforward GTK menu. On the scrolling speed, I have no influence in any way.
- I will look into the sorting order of the bookmarks.Looking in the code, it should be sorted, but I will experiment a little."
1678389,2017-04-01 07:08:17 UTC,thank you - I am using it in 14.04
1678389,2017-04-03 18:31:19 UTC,"Thank you. Where do you rename the bookmarks? I have Ubuntu 14.04 and I
went to Nautilus. on the side there are bookmarks. I right press on them
and press rename and change their names do not change in the Places & Files
indicator 0.5.8
it shows the original name of the directory not the renamed name of the
bookmark."
1678389,2017-04-03 18:34:14 UTC,"it would be good to sort the bookmarks in the same way they are sorted in
Nautilus"
1678389,2017-05-22 16:40:33 UTC,Jacob have you had a chance to address this? It would be so much more convenient on Ubuntu 14.04 if the Files and Places bookmarks appeared exactly in the same way as the way they are organized on Nautilus. Does it now draw the organization from one of the other file browsers?
1678389,2017-05-22 17:13:23 UTC,This is what is listed in my .congif.gtk3 bookmarks file
1678397,2017-04-01 08:25:45 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1678440,2019-01-10 12:56:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678456,2017-04-01 15:24:50 UTC,"Honestly, I don't think there's any intention to not have XWayland installed by default. It could be useful if XWayland is only started when needed, which is what GNOME #759538 is about."
1678456,2017-04-01 17:13:36 UTC,"But not everyone have the need to run legacy X11 applications.
Some people are fine with just Wayland and don't need to run legacy applications."
1678456,2017-04-01 17:29:35 UTC,"My understanding is that neither Firefox nor Google Chrome/Chromium are native Wayland apps, so unless you're using something like Epiphany for your web browsing, yes you do need XWayland."
1678456,2018-03-21 12:41:30 UTC,@Jeremy Bicha: In the meantime Firefox wayland support has arrived (still not enabled by default. callable with --enable-default-toolkit=cairo-gtk3-wayland) and Chromium wayland ozone builds are quite stable.
1678456,2018-08-15 04:50:25 UTC,I think this is implemented starting in Ubuntu 18.10.
1678458,2017-10-25 02:32:56 UTC,I have resolved this problem.The instance create fail because it must use Distributed Switch for the vCenter to launch the instance from OpenStacn Mitaka version.So it must use the vmware-nsx network plugin for VMware hypervisor.You can use the following link to install and configure vmware-nsx network plugin.
1678458,2018-02-23 01:05:21 UTC,"Hello,"
1678458,2018-02-22 03:12:45 UTC,"This is nova-compute log
2018-02-22 07:19:42.899 5 DEBUG oslo_service.periodic_task [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Running periodic task ComputeManager._check_instance_build_time run_periodic_tasks /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_service/periodic_task.py:215
2018-02-22 07:19:42.901 5 DEBUG oslo_service.periodic_task [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Running periodic task ComputeManager.update_available_resource run_periodic_tasks /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_service/periodic_task.py:215
2018-02-22 07:19:42.948 5 DEBUG nova.compute.resource_tracker [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Auditing locally available compute resources for kolla (node: domain-c7.A9A92EE9-9488-4840-9F21-57E5EFC9B133) update_available_resource /var/lib/kolla/venv/lib/python2.7/site-packages/nova/compute/resource_tracker.py:640
2018-02-22 07:19:42.960 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-26019f35-1067-4fdc-b728-48979804b0b5 request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:42.991 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-ff16a8b0-3c64-4223-a827-529c0001c246 request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:43.026 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-72206dab-5421-411b-9c7f-9e8576c95a2e request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:43.065 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-ffa55cf0-bed9-4ffd-99aa-1fa56c616590 request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:43.619 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-c3c5fd57-dc15-421a-97bd-f8021fa3aa96 request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:43.660 5 DEBUG nova.compute.resource_tracker [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Hypervisor/Node resource view: name=domain-c7.A9A92EE9-9488-4840-9F21-57E5EFC9B133 free_ram=1374MB free_disk=39GB free_vcpus=2 pci_devices=None _report_hypervisor_resource_view /var/lib/kolla/venv/lib/python2.7/site-packages/nova/compute/resource_tracker.py:776
2018-02-22 07:19:43.661 5 DEBUG oslo_concurrency.lockutils [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Lock ""compute_resources"" acquired by ""nova.compute.resource_tracker._update_available_resource"" :: waited 0.000s inner /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:270
2018-02-22 07:19:43.749 5 DEBUG nova.scheduler.client.report [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Refreshing aggregate associations for resource provider 838382f7-e055-4b4d-9ae5-45ffcdde2ffd _ensure_resource_provider /var/lib/kolla/venv/lib/python2.7/site-packages/nova/scheduler/client/report.py:498
2018-02-2..."
1678458,2018-02-22 01:51:19 UTC,I had the same mistake. How did you solve it?
1678458,2017-10-16 02:21:19 UTC,"Hi,"
1678458,2017-04-05 12:12:31 UTC,So anybody can tell me what's wrong with the config spec?  Thanks a lot.
1678458,2017-09-30 16:12:03 UTC,"Hi,I meet the same error,did you solve it?
Thanks."
1678458,2017-10-13 07:52:13 UTC,"Could you please provide the vpxd.log from vCenter when this error occurs?
Do you get the same error when using the cirros image?
Are you using Neutron with DVS or NSX plugin?"
1678458,2017-04-05 12:11:06 UTC,"And I found: vmops.build_virtual_machine() --> vm_util.create_vm() failed
The error is:  oslo_vmware.exceptions [-] Fault InvalidDeviceSpec not matched.
So I dump the config_spec:"
1678458,2017-04-05 12:02:56 UTC,"updates:
   I use neutron networking, but I don't have vmware NSX.  Dose Neutron networking work without NSX?"
1678458,2017-04-05 07:11:07 UTC,"Hi, I have some updates.
From my understanding,  VCDriver will download vmdk image from glance, then upload the image to vmware datastore via vcenter.  But I did not see the vmdk image in local nova cache, and remote datastore!
Why??"
1678472,2017-07-26 15:29:45 UTC,Will be tracked here https://jira.percona.com/browse/DOC-565
1678472,2018-01-17 08:19:34 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1966
1678474,2017-07-26 15:36:56 UTC,"Krunal, can you confirm? MASTER disregards some of the validations...
Also, will be tracked as part of https://jira.percona.com/browse/DOC-565"
1678474,2018-01-17 08:19:35 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1967
1678483,2017-04-01 14:35:04 UTC,You need to get a application password (or something like this) on your Google profile security options. It's a single use password for applications that don't support 2fa.
1678485,2020-06-21 08:39:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678492,2017-07-15 07:12:10 UTC,This will affect all installation testcases if using wireless I think. Mass testcase fix ...
1678495,2018-10-02 13:23:49 UTC,This problem persists in 18.04.x?
1678495,2018-01-19 18:16:19 UTC,The font rendering bug is still existing!!! Solution:
1678495,2017-09-15 10:45:05 UTC,"Same here, too - Ubuntu-Mate 17.10 beta 1"
1678495,2017-08-30 07:30:12 UTC,"Hi Martin,"
1678495,2017-08-23 01:33:32 UTC,I can't reproduce on Ubuntu MATE 17.10 daily. What GPU and drivers do you have?
1678495,2017-07-02 04:17:29 UTC,[Expired for ubuntu-mate because there has been no activity for 60 days.]
1678495,2017-07-02 04:17:27 UTC,[Expired for ubuntu-mate-artwork (Ubuntu) because there has been no activity for 60 days.]
1678495,2017-08-07 16:26:15 UTC,Still a problem on Ubuntu MATE 17.10 Alpha 2. Attaching a screenshot.
1678495,2017-05-02 08:53:39 UTC,I have just made this observation when resizing a window.
1678495,2017-04-19 06:14:58 UTC,I was advised on the Ubuntu MATE forum it might be helpful to add the following information about my graphics card:
1678495,2017-04-18 11:37:45 UTC,I just noticed that this problem only occurs for unmaximized windows.
1678495,2017-04-15 17:10:00 UTC,"Hello all,"
1678495,2017-04-10 12:52:30 UTC,"Sure, so when in the terminal you cd to a deeply nested folder (longer than the width of the terminal), the title of the window is displayed wrong. The highlight effect in the screenshot seems to have disappeared following an update, however the first letter of the username is not currently displayed."
1678495,2017-04-10 11:34:50 UTC,Can you elaborate on what you're describing please?
1678495,2017-07-02 04:17:23 UTC,[Expired for mate-terminal (Ubuntu) because there has been no activity for 60 days.]
1678510,2019-03-11 14:54:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678510,2018-05-31 01:35:36 UTC,"Oops, this problem still occurs with glibc 2.27, my mistake."
1678510,2018-05-31 01:31:17 UTC,"Looks like this is fixed in glibc 2.27.
https://sourceware.org/bugzilla/show_bug.cgi?id=22284"
1678510,2017-07-30 13:05:15 UTC,@eldar unfortunately I can't use gcc 4.9 because I'm using C++ language features that are not supported in that version. If anybody has a workaround using a newer compiler that would be nice.
1678510,2017-08-14 00:26:02 UTC,You can use gcc -no-pie option as a workaround.
1678510,2017-07-28 01:59:33 UTC,Is there a workaround?
1678510,2017-05-01 10:29:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678510,2017-04-02 06:12:33 UTC,"Affected:
gcc-5 (Ubuntu 5.4.1-2ubuntu2) 5.4.1 20160929
gcc (Ubuntu 6.2.0-5ubuntu12) 6.2.0 20161005"
1678510,2017-07-28 15:57:14 UTC,@max-staff As workarount use gcc 4.9 for profilling. I don't know another ways yet.
1678515,2017-04-01 19:00:08 UTC,This change was made by a bot.
1678516,2017-07-08 15:15:39 UTC,I can't reproduce this on Ubuntu 16.04 or Windows 10 with Pinta 1.7 daily build. Is this happening with an empty new image or a particular image? Are there any more details you can share about how to reproduce this issue?
1678521,2019-05-17 09:50:32 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016."
1678524,2019-11-12 11:39:38 UTC,This issue was fixed in the openstack/manila 7.4.0 release.
1678524,2019-11-12 11:32:51 UTC,This issue was fixed in the openstack/manila 8.1.0 release.
1678524,2019-10-25 12:53:34 UTC,This issue was fixed in the openstack/manila 6.3.2 release.
1678524,2019-10-10 23:16:27 UTC,"Reviewed:  https://review.opendev.org/687958
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=f581e987a5bf0bbdaa2154233d8a94240b6f8da1
Submitter: Zuul
Branch:    stable/queens"
1678524,2019-10-10 17:32:18 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/687958"
1678524,2019-10-09 14:41:21 UTC,"Reviewed:  https://review.opendev.org/686231
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=62996ad8f663e45758227b927058d80bab3758df
Submitter: Zuul
Branch:    stable/rocky"
1678524,2019-07-12 18:33:22 UTC,"Reviewed:  https://review.opendev.org/669759
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=9e39a138fbe8c0546898543de8c007238caf0ef0
Submitter: Zuul
Branch:    stable/stein"
1678524,2019-09-26 19:50:19 UTC,This issue was fixed in the openstack/manila 9.0.0.0rc1 release candidate.
1678524,2019-07-08 21:30:50 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/669759"
1678524,2019-07-01 14:03:45 UTC,"Reviewed:  https://review.opendev.org/665142
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=f333b88e2521c8a1fecb88206cfb08046957346f
Submitter: Zuul
Branch:    master"
1678524,2019-06-13 13:55:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665142"
1678524,2019-03-22 16:09:05 UTC,"Hey Naresh any updates for this defect, or any help need from the upstream community?"
1678524,2019-10-02 18:12:33 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/686231"
1678526,2017-04-02 09:39:10 UTC,Fixed in trunk revision 2039. Please retest.
1678526,2017-04-02 16:35:07 UTC,Thank you for fixing. How can I install a new version on my system? I have no experience in bazaar and development of programms.
1678526,2017-04-02 17:43:30 UTC,"Sorry, the previous comment was accidentally committed in an incomplete state..."
1678526,2017-04-04 15:45:45 UTC,"Dear Adam,"
1678556,2020-07-03 04:42:10 UTC,DistroRelease: Kali 2016.2
1678559,2017-10-02 22:34:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678563,2018-10-24 18:57:33 UTC,We should totally merge the flattener to oslo.policy.
1678563,2018-12-13 02:54:56 UTC,"It's not totally related to this issue, but I think GenericCheck also can be enhanced by interpreting right-hand side."
1678565,2017-04-03 11:33:42 UTC,"So you mean the case where you have dhcp provider = neutron and some nodes having noop net interface, and some having neutron? Yeah, neutron net interface requires dhcp provider to be neutron too, and I'm not sure how to deal with this, apart from deprecation of dhcp providers. So let's do this as a fix :)"
1678569,2017-04-03 09:59:26 UTC,That would be because the Ubuntu family lacks the RATIO character (U+2236).
1678569,2017-04-03 10:15:29 UTC,I’m glad you love the Ubuntu font! Unfortunately this problem is a bit complicated and probably can’t be fixed in the font.
1678569,2017-04-04 16:05:04 UTC,"Ah, it seems Adolfo posted that comment while I was writing mine. It should be possible to test whether U+2236 is indeed the codepoint being used, by copying the colon character into that slot in a font editor."
1678569,2017-04-05 01:35:33 UTC,Note that GNOME Shell also uses U+2236 for its clock…
1678583,2017-04-07 14:55:32 UTC,I am still concerned at Canonical's inability/unwillingness to engage with me about the above reported bug.
1678583,2017-04-07 14:54:05 UTC,Please read this to understand what the REAL underlying problem was and how to solve it manually.
1678583,2017-04-02 11:44:39 UTC,Reporting back after doing the purge and install instructions.
1678583,2017-04-03 15:43:05 UTC,I'm getting rather frustrated because I'm not getting any response from Canonical about this problem.
1678583,2017-04-02 10:02:54 UTC,Searching on the web I have found things that look similar :
1678585,2017-04-20 16:17:21 UTC,I'd like to perform a kernel bisect to figure out which commit caused this regression. We need to identify the earliest kernel that did not exhibit the bug and the first kernel that did exhibit the bug.
1678585,2017-04-19 06:04:13 UTC,It is working with Ubuntu 16.10 .
1678585,2017-04-18 22:54:30 UTC,Do you recall in which previous releases?  That will help narrow down the kernel version that introduced this.  Then we can perform a kernel bisect.
1678585,2017-04-06 12:33:18 UTC,Can you test the following kernels to see if the bug existed in them:
1678585,2017-04-06 11:49:20 UTC,"Unfortunately, No."
1678585,2017-04-18 08:55:02 UTC,"Hi,
This test work properly in the previous releases."
1678585,2017-04-03 13:27:47 UTC,"The bug is exist also in kernel that mentioned in commit#2
4.11.0-041100rc5-generic"
1678585,2017-04-03 08:53:40 UTC,"Also, does this bug go away if you boot with a Yakkety or earlier kernel?"
1678585,2017-04-03 08:52:38 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1678585,2017-04-02 09:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678585,2017-04-03 14:04:09 UTC,"Do you know if this is a regression?  If it is, we can bisect down to the commit that introduced the bug."
1678594,2017-04-07 23:17:59 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1678606,2017-05-29 08:57:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678606,2017-07-26 19:11:51 UTC,This bug was fixed in the package network-manager - 1.8.2-1ubuntu2
1678626,2017-04-25 15:24:55 UTC,I forgot: you can move the image content with the cursor keys. This works also when you are in the process of creating a mask. (The default branch contains a fix which adapts the scroll rate to the image size. This should be more appropriate than a fixed scroll rate.)
1678626,2017-04-02 15:28:51 UTC,"The mask editor was not written for handling arbitrary mask. It was written to create simple mask.
I would recommend to first create a rough mask in the overview and then refine the mask in higher zoom level (add more points, move points, remove points)."
1678626,2017-04-03 08:53:19 UTC,"OK, thanks for the clarification. The workflow you recommend is what I'm already doing."
1678634,2017-04-07 23:19:30 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1678634,2017-06-12 13:59:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678634,2017-04-02 16:26:04 UTC,"StacktraceTop:
 setup_button (launcher=0x556857eba3c0) at launcher.c:539
 g_closure_invoke () from /tmp/apport_sandbox_oefGqK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /tmp/apport_sandbox_oefGqK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /tmp/apport_sandbox_oefGqK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /tmp/apport_sandbox_oefGqK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1678635,2017-04-02 16:28:39 UTC,"Here's the output of the ""lsb_release"" and ""apt-cache policy"" commands, which I forgot in the previous zip file. My apologies."
1678635,2019-06-12 10:04:30 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017."
1678645,2017-04-02 17:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678645,2017-04-02 22:04:31 UTC,"There's nothing missing, all necessary information is there."
1678645,2017-04-02 22:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1678645,2017-04-03 08:26:16 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1678645,2018-04-10 01:33:11 UTC,"FWIW, this affects for example the latest www.system-rescue-cd.org as well dated 2nd of April. It boots by default into an amd64 kernel but the btrfs tools are i386. Very much looks like an upstream issue to me and possibly more relevant than one might be tempted to think initially."
1678646,2017-04-02 18:03:54 UTC,ubuntu 16.04.2 with stable phone overlay
1678650,2017-04-02 18:03:46 UTC,ubuntu 16.04.2 with stable phone overlay
1678656,2020-01-30 06:52:42 UTC,ipa now does not support python2 so this problem becamse worse since ipa does not initialized at all
1678656,2017-11-20 15:12:31 UTC,To change the python version we need to modify https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/ironic-agent/pkg-map. But I'm not sure how to make the services created by that element to pick the right python.. I'm moving this to DIB as the element still lives there.
1678660,2017-04-16 20:11:39 UTC,This seems to be the same bug like this one https://bugs.launchpad.net/or/+bug/1674475 . Pls. read what has been suggested there.
1678665,2018-07-04 21:57:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678665,2018-07-04 22:07:21 UTC,"After the 4.15.0-124 kernel update, I started noticing the mei_me error messages at the initial startup screen (which usually only had tpm errors), although othing fails to work.
$ dmesg |fgrep mei
[ 2022.278241] mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND
[ 2022.278246] mei_me 0000:00:16.0: mei_irq_read_handler ret = -71.
[ 2022.278281] mei_me 0000:00:16.0: unexpected reset: dev_state = INIT_CLIENTS fw status = 1E000245 60000006
[ 6477.968336] mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND
[ 6477.968342] mei_me 0000:00:16.0: mei_irq_read_handler ret = -71.
[ 6477.968374] mei_me 0000:00:16.0: unexpected reset: dev_state = INIT_CLIENTS fw status = 1E000245 60000006
[42278.652813] mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND
[42278.652818] mei_me 0000:00:16.0: mei_irq_read_handler ret = -71.
[42278.652852] mei_me 0000:00:16.0: unexpected reset: dev_state = INIT_CLIENTS fw status = 1E000245 60000006
$ uname -a
Linux leno 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04 LTS
Release:	18.04
Codename:	bionic
 BIOS Revision: 1.42
 Firmware Revision: 1.36
 Vendor: LENOVO
 Version: 8BET62WW (1.42 )
 Release Date: 07/26/2013
System Information
 Manufacturer: LENOVO
 Product Name: 42763JU
 Version: ThinkPad W520"
1678665,2018-07-22 23:46:06 UTC,"Two weeks of running kernel 4.0.15-23 did not produce the error when returning from suspend.  After the kernel update to 4.0.15-29, the error appears nearly every return from suspend, much more frequent than with the 4.0.15-24 kernel.  Again, no adverse effects are seen from the error."
1678665,2018-08-28 15:11:48 UTC,"On a Lenovo W520, kernel 4.15.0-33, changing the UEFI Settings for the Security Chip to ""disabled"" from ""ignore"" eliminated both this mei-me error, and the tpm error , both of which were appearing on the black screen which appeared briefly after a resume.BIOS revision 8BET62WW (1.42 ), Firmware revision 1.36, SMBIOS 2.6."
1678665,2018-09-11 19:12:21 UTC,"After a few weeks running the 4.15.0-33 kernel, I have seen the hbm... message twice, much less frequently than before turning off the security chip, but it's not totally gone."
1678665,2019-02-24 09:42:32 UTC,"Linux eule 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Xubuntu 18.04, problem still exists, system seems to fail to suspend once the message shows."
1678667,2019-02-08 02:35:42 UTC,I didn't want to raise a duplicate but this is still the case. Windows 10 (on 2 machines). There is advice on this issue stretching back 2 years but I only just thought maybe there is a ticket for it and this is the closest one.
1678667,2020-01-25 11:17:13 UTC,"Hi, we're tracking this issue over at Gitlab in this ticket: https://gitlab.com/inkscape/inbox/issues/1149"
1678667,2018-09-05 18:47:10 UTC,"Same for me, Windows 7."
1678667,2018-08-04 18:34:31 UTC,"I also have this problem, or similar - the document properties window opens in different locations on screen each time I open it. Sometimes the whole windows is visible, sometimes half way outside screen on the right side, sometimes almost fully outside screen on theright side."
1678667,2017-04-02 23:00:54 UTC,You might check this:
1678667,2017-04-02 21:29:01 UTC,"forgot to add, this is Mac OS Sierra , Inkscape 0.91 r13725"
1678667,2018-09-05 11:58:55 UTC,"I've been having the same issue myself with the newest version of Inkscape.  It's very annoying.  99% of the time when I first open it on a file, it will be about ~95% off the screen leaving barely a little bit to drag back (& no, I only have a single monitor).  So, you can see how bad this could be if it randomly decided to completely open off my screen & I didn't have any part that could be dragged back."
1678670,2017-04-02 22:11:44 UTC,The basic idea of AppStream language packs is that you can drop in as many as you want.
1678670,2017-04-02 22:13:53 UTC,"Oh, btw: If ""extends"" is missing, the SC is expected to always install the language and assume the langpack effects the whole system. This should be mentioned in the spec (I'll add it soon, I just noticed that this particular bit is missing)."
1678674,2017-04-14 08:52:43 UTC,"Hi,
Same issue here (ubuntu 16.10 x64) on a Lenovo x1 Carbon.
my xinput list:
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ ELAN Touchscreen                        	id=11	[slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                   	id=15	[slave  pointer  (2)]
⎜   ↳ Logitech M315/M235                      	id=9	[slave  pointer  (2)]
⎜   ↳ Logitech M510                           	id=10	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=14	[slave  pointer  (2)]"
1678674,2017-11-20 09:42:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678675,2017-04-07 23:20:41 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1678677,2017-04-03 22:33:35 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1678677,2017-04-04 12:40:30 UTC,"I resolved this issue by removing a script by which I tried, in vain, to restart the network-manager at reboot time."
1678678,2017-04-03 22:35:59 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1678680,2017-04-03 00:26:22 UTC,This seem to be specific to the feature branch only. Please fix before merging \o/
1678680,2017-04-03 00:58:57 UTC,"The only difference between the feature branch and develop at the moment is the removal of the persistent-storage feature branch, and that has zero impact on bootstrap. This has happened only once, so I'm not going to look into it right now."
1678682,2017-04-03 20:55:30 UTC,This looks to happen if you upload files and then proceed to edit a file's metadata before refreshing the page.
1678682,2017-04-10 22:35:12 UTC,Happens on older versions of Mahara as well.
1678686,2018-05-16 16:26:00 UTC,"Change abandoned by Monty Taylor (<email address hidden>) on branch: master
Review: https://review.openstack.org/452585
Reason: This is fairly old at this point. Feel free to restore if it's still relevant."
1678686,2017-04-09 17:09:11 UTC,"Juan et al,"
1678686,2017-08-02 20:49:34 UTC,Automatically unassigning due to inactivity.
1678686,2017-04-03 14:53:17 UTC,Is it worthwhile to consider finding openssl's default paths if the current proposed method not available?
1678686,2017-04-03 02:22:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/452585"
1678686,2017-04-06 06:37:41 UTC,"Sean, well, you could get them with:"
1678687,2017-04-03 12:59:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1678689,2017-05-23 12:50:20 UTC,Did someone see this bug report and relating patch? Do you all need more information like reproduce case and test case?
1678689,2017-05-23 12:53:15 UTC,This bug has been fixed I think and I proposed the 2-line patch to be reviewed by eCryptfs developers.
1678689,2017-05-25 21:42:51 UTC,Applied to lp:ecryptfs as r886
1678694,2018-02-06 02:59:04 UTC,seems #1686116 fixed this issue.
1678694,2017-07-28 04:03:19 UTC,Encounter this problem with
1678694,2017-06-27 16:04:01 UTC,"Automatically discovered version mitaka in description. If this is incorrect, please update the description to include 'nova version: ...'"
1678694,2017-06-07 20:30:17 UTC,"Actually, seems like Nova may be blamed for that. Changing dev=""sda"" to dev=""sdb"" in the XML fixes the issue."
1678694,2017-05-11 19:54:18 UTC,It's an issue in Ocata.
1678694,2017-04-03 12:51:15 UTC,"I filed the same bug with cinder, and their maintainers suggested it was a nova issue"
1678694,2017-06-07 20:25:55 UTC,It looks like it's not an issue in nova nor cinder.
1678833,2017-04-03 16:29:59 UTC,"(I certainly don't see how this could be a regression, either)"
1678833,2017-04-03 07:47:51 UTC,"This is related to io.reader and has not been change in juju, so it cannot be a regression."
1678833,2017-04-03 16:29:45 UTC,"Are there actual endpoints that need to be >4k characters? We could warn or
something if we found one that long.
  https://www.google.com/search?q=max+url+length
says that 2,083 is the only number of characters that you can actually
expect to put into a URL. We're well over that at 4096."
1678833,2017-04-03 23:56:43 UTC,"Since valid URL length is 2,083, from comment # 2, we should have a validation check for it."
1678947,2018-01-17 14:13:18 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1968
1678947,2017-04-24 09:33:23 UTC,"Quick fix for xtrabackup (to be replaced with upstream once it released) is pushed
https://github.com/percona/percona-xtrabackup/pull/360
https://github.com/percona/percona-xtrabackup/pull/361"
1678947,2018-01-25 09:21:22 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3676
1678947,2018-01-20 07:46:24 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-501
1678960,2017-04-24 14:09:16 UTC,This bug was fixed in the package linux - 4.4.0-75.96
1678985,2019-09-16 14:07:30 UTC,Migrated to https://github.com/widelands/widelands/issues/2073
1678994,2019-07-29 14:54:30 UTC,"This looks like a local issue on the machine, inserv is failing due to a boggus initscript (CNNetAgent_d?)"
1678995,2017-04-03 10:52:19 UTC,I would also consider enforcing mac_address for portgroup object as mandatory field as possible option.
1679041,2020-04-24 00:51:15 UTC,"The problem with this issue, that we have multiple clouds (from different customers) where we have to change the 'flavor' of machines on a more or less regular basis."
1679047,2017-04-03 12:12:04 UTC,All repositories are checked and fixed by using the following commands:
1679064,2017-06-02 19:33:33 UTC,"Reproduced again on ""9.2 MU-2 02/06/17 iso #06/02/17 11:58"" run
Snapshot attached"
1679082,2017-05-12 10:47:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679120,2017-04-03 14:32:14 UTC,Found misconfiguration. Redeploying.
1679161,2017-05-23 22:47:41 UTC,"Realistically, this probably should be reported upstream, as the URLs are in the upstream source not our packaging."
1679181,2017-04-03 13:29:56 UTC,Attached transport stream file that demonstrates the bug when PCR values wrap.
1679181,2017-04-03 13:30:42 UTC,Attached transport stream file that demonstrates incorrect PCR decoding by tsvbr2cbr
1679181,2017-04-03 13:33:39 UTC,Patch to correct the wrapping problem in tspcrmeasure
1679181,2017-04-03 13:34:25 UTC,Patch to correct both problems in tsvbr2cbr
1679181,2017-04-03 16:25:59 UTC,"The attachment ""Patch for tools/tspcrmeasure/tspcrmeasure.c"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1679185,2017-04-03 19:43:30 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1679185,2017-04-04 13:24:15 UTC,"Don't mention it, Id really like to learn about commands of Linux/Ubuntu,
Meanwhile, goodbye to windows.
Thank you and more power"
1679185,2017-10-01 12:23:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679208,2020-02-25 15:51:33 UTC,"Christian, was this ever resolved?"
1679208,2017-09-15 19:22:34 UTC,I have subscribed to HPE Eddie and Ganesh to this bug whether they have tested this with old kernel or some parameter needs to be added.
1679208,2017-04-18 13:52:08 UTC,Subscribing Narinder to map that to HPE if possible.
1679208,2017-04-06 15:57:27 UTC,"Hi Joseph,
no regression IMHO.
Only the frequency or signature of the issue changed by Kernel upgrades.
I did not yet go back further than Xenial but that is worth a try as soon as I find time for it again."
1679208,2017-04-06 15:39:41 UTC,Is this bug a regression?  Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1679208,2017-04-04 14:32:32 UTC,"After reboot it only took like 10 minutes this time to hit me again :-/
There seems no reliable way to be sure anymore."
1679208,2017-04-04 14:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1679208,2017-04-06 15:07:16 UTC,"Hard to install when the system is so broken :-/
I installed the latest Mainline which is 4.11.0-041100rc5.201704022131 and enabled the intel_iommu on it."
1679208,2017-04-04 10:38:58 UTC,"From there I ran some I/O as on the other system we had the impression tp trigger it by further I/O.
But the system is still fine - so the bug might be good documentation for the next one hitting it, but TL;DR is: ""FW bug - FW update""."
1679208,2017-04-04 14:14:53 UTC,"Seems I was happy about the FW being the fix too early, it turns out to still pop up.
Just not on boot.
About 6 hours working I ran into it again."
1679208,2017-04-03 15:06:27 UTC,"Please note that on the ""good"" system nobody ever used iommu device assignment, I'll do so after the next days. That way we should also learn if the can bring a good system into the failing mode."
1679208,2017-04-03 15:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1679208,2017-04-03 15:49:41 UTC,"In what appeared similar https://bugzilla.redhat.com/show_bug.cgi?id=649766
it was recommended to set iommu=pt, but in our case that does not help."
1679208,2017-04-06 11:06:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1679208,2017-04-03 18:30:23 UTC,"Unassigning myself as ""broken HW"" no more seems an option, so for the kernel Team to re-asssign."
1679208,2017-04-03 18:35:38 UTC,"This was brought to my attention:
http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565"
1679208,2017-04-03 18:28:55 UTC,We just found that the second box we tested just needed some time (or I/O) to run into the same.
1679208,2017-04-04 10:15:17 UTC,"Updated the System to latest FW for the storage controller 4.52 (and iLO to 2.50).
With that updated to Zesty again all till working fine."
1679209,2017-04-03 16:50:24 UTC,This bug was fixed in the package onscripter - 20161102-1ubuntu1
1679210,2019-10-15 11:47:37 UTC,I don't believe there is a way to do what you want right now. There's no way to not follow any channel or any track in the store.
1679218,2017-04-04 06:53:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679218,2017-04-04 06:54:35 UTC,"tested rhythmbox, silent mode doesn't work"
1679218,2017-04-04 08:43:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679218,2017-04-04 08:44:17 UTC,"We're just asking the indicator to do The Right Thing™, apparently it doesn't, yet."
1679220,2018-08-22 10:50:28 UTC,"I might accept patches for it, but I'm not likely to work on it myself. It sounds fairly complicated to handle, especially if users actually want to use a different release."
1679220,2018-08-28 15:47:33 UTC,"I'm not sure there is any legitimate case for booting $RELEASE1 and trying to have the installer install $RELEASE2.  And even if there were, you can't do that now anyhow.  It should be as simple as having apt-cdrom check lsb_release, and only look in that pool directory instead of searching them all."
1679220,2017-09-26 18:23:38 UTC,To install the system in the first place of course.
1679220,2017-08-17 18:05:22 UTC,"I don't understand the problem, sorry. Can you expand on that? I don't use anything other than http(s) repositories. How are the USB sticks used?"
1679226,2017-08-15 10:22:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679226,2017-08-15 10:26:29 UTC,"I am running Ubuntu 16.04.3 LTS with gedit 3.18.3-0ubuntu4 and have exactly the same problem.
This makes gedit unusable for me."
1679251,2017-04-03 17:56:29 UTC,"StacktraceTop:
 nautilus_path_bar_size_allocate (widget=0x5604c311a3b0, allocation=0x7ffd834087b0) at nautilus-pathbar.c:682
 gtk_widget_size_allocate_with_baseline (widget=0x5604c311a3b0, allocation=allocation@entry=0x7ffd834088e0, baseline=<optimized out>, baseline@entry=-1) at ././gtk/gtkwidget.c:6116
 gtk_box_size_allocate_no_center (widget=0x5604c30fb570, allocation=<optimized out>) at ././gtk/gtkbox.c:811
 gtk_box_allocate_contents (gadget=<optimized out>, allocation=0x7ffd834089a0, baseline=<optimized out>, out_clip=0x7ffd834089c0, unused=<optimized out>) at ././gtk/gtkbox.c:1205
 gtk_css_gadget_allocate (gadget=0x5604c310c0f0, allocation=allocation@entry=0x7ffd83408ac0, baseline=-1, out_clip=out_clip@entry=0x7ffd83408a20) at ././gtk/gtkcssgadget.c:782"
1679251,2017-10-15 18:42:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679251,2019-01-15 17:05:00 UTC,"That's still an issue in 18.10
https://errors.ubuntu.com/problem/00dc9cddf551a06041fc17b5e0d7b745973c0e56"
1679253,2017-05-13 03:05:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679253,2020-07-23 15:35:43 UTC,looks like you tweaked /usr/bin/python symlink point to python3
1679281,2019-06-21 15:35:41 UTC,A full re-ingest using pingest.pl allowed my new formats to appear.
1679281,2017-04-03 19:36:41 UTC,"If you reingest the bib records that you would expect to see in the search results, do they subsequently turn up?"
1679281,2019-03-19 14:36:27 UTC,I have a similar issue on Webby 3.1.5.
1679288,2018-01-12 19:03:45 UTC,Unassigning due to no activity for > 6 months.
1679295,2017-04-03 20:53:00 UTC,"Thank you for the suggestion.  That is a good point, and we will keep it in mind.  Just to be clear, we tried connecting all of the currently available interfaces and still have problems."
1679295,2017-12-12 15:58:46 UTC,"This bug reported several issues and I was working on the network-control parts. All that remains is an interface for debug/ieee80211, which needs research. I'm not actively working on this, so marking back to Triaged and unassigning myself. Anyone interested in this interface should feel free to send a pull request to upstream snapd if you need this sooner than later. Thanks!"
1679295,2017-08-11 18:26:04 UTC,"FYI, https://github.com/snapcore/snapd/pull/3715"
1679295,2017-04-03 20:19:48 UTC,Note that in devmode you can (and should!) connect your interfaces to reduce the number of logged (but allowed) policy violations.
1679295,2017-08-03 14:09:25 UTC,"The bug title is very general while the bug description is specific. I'm going to change the bug title to reflect debug/ieee80211. In that light, I think we can just add those accesses to network-control."
1679295,2017-08-03 16:29:01 UTC,That sounds good.  Thank you!
1679301,2017-05-22 11:52:52 UTC,Mitaka is not updated for the latest fedora atomic.
1679301,2017-05-22 11:55:56 UTC,"The FLANNEL variable name you propose are fixed in:
newton https://review.openstack.org/#/c/464078/"
1679301,2017-05-22 14:27:01 UTC,Please NOTE: this bug affects only mitaka.
1679301,2017-05-24 15:54:51 UTC,I believe this means I should remove this bug. We are working on K8s-hosted OpenStack with Ocata so I can verify this fix further on in my testing.
1679301,2017-05-24 15:55:36 UTC,I will verify this fix on Ocata as part of a stackanetes deployment.
1679301,2017-05-25 13:44:37 UTC,Thanks!
1679301,2017-05-25 13:55:29 UTC,No I do not - I'm working on integrating Kolla-Kubernetes which is at Ocata so I can verify the process with Ocata.
1679301,2017-08-21 11:45:13 UTC,"Hi, this bugs still afects swarm clusters (Ocata and Master trunks)"
1679301,2017-09-27 11:14:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507822"
1679301,2017-10-26 15:33:38 UTC,"Reviewed:  https://review.openstack.org/507822
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=010a2673d4424358199878f717dcec6159276701
Submitter: Zuul
Branch:    master"
1679301,2018-02-08 17:36:05 UTC,This issue was fixed in the openstack/magnum 6.0.0 release.
1679308,2017-04-20 18:20:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458609"
1679308,2017-04-12 10:41:06 UTC,This appears to be a configuration issue.
1679308,2017-04-03 21:28:39 UTC,"Workaround:
In guest:
/etc/trove/conf.d/trove-guestagent.conf"
1679308,2017-04-12 14:44:26 UTC,"Although you can adapt the configuration since MariaDB and MySQL are similar databases, the default implementation (MariaDBInnoBackupExIncremental) doesnt inherits the incremental implementation from InnoBackupExIncremental as attached diagram."
1679311,2017-04-03 21:14:40 UTC,"In addition to the loft tool, it would be nice for the loft tool to generate how much rows/column should be generated. The more rows and column generated, the better it will fit the curves."
1679322,2017-04-03 21:44:17 UTC,"Hi There,"
1679322,2017-06-03 04:18:03 UTC,[Expired for maas (Ubuntu) because there has been no activity for 60 days.]
1679322,2018-01-17 19:57:03 UTC,Here are the logs from the last occurrence.
1679322,2018-01-17 20:01:21 UTC,Please att h logs from apt both the term and the history.
1679322,2018-01-18 02:44:51 UTC,"Sure, here's term.log:"
1679327,2019-03-04 16:34:16 UTC,This bug was fixed in the package libpam-mount - 2.16-3ubuntu0.1
1679327,2019-02-26 13:34:49 UTC,"Test executed fine on the SRU from proposed:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/libp/libpam-mount/20190225_143346_e53d2@/log.gz"
1679327,2019-02-25 13:54:46 UTC,"Hello Joshua, or anyone else affected,"
1679327,2019-02-14 15:20:01 UTC,The tests are defined and running now as seen on https://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html
1679327,2019-02-25 11:10:24 UTC,"The verification of the Stable Release Update for libpam-mount has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1679327,2019-02-25 11:20:24 UTC,This bug was fixed in the package libpam-mount - 2.16-5ubuntu0.1
1679327,2019-02-07 16:02:03 UTC,will be fixed as part of bug 1804408 for SRUs and hopefully via [1] in Debian to then sync into Ubuntu (otherwise we add a Delta for a short while).
1679327,2019-02-13 23:54:53 UTC,"Hello Joshua, or anyone else affected,"
1679329,2021-02-24 21:01:45 UTC,"I'm not sure there's a whole lot of value to gain from a dep8 test of this package, it's basically just a collection of perl scripts."
1679342,2021-01-11 11:37:49 UTC,This bug was fixed in the package mtx - 1.3.12-14
1679356,2018-07-09 13:10:03 UTC,Feel free to provide some test data…
1679356,2018-07-10 19:50:11 UTC,"This is a wishlist bug and serves as a placeholder and reminder that this package, and many others, could benefit from DEP8 tests."
1679358,2017-04-04 08:32:56 UTC,"On 3 April 2017 at 23:17, Yifan <email address hidden> wrote:

> There are fields in SCTLR that are RAO/SBOP or WI or in the case of the
> RR field, accessible only in secure mode. Currently it seems that qemu
> just propagates any write to SCTLR to the register and this screwed up
> in a bootloader that I am debugging.
"
1679358,2017-04-04 14:59:22 UTC,So there won't be a fix in the future? I'm working with debugging a proprietary bootloader that I do not have the source code for. I wonder if this becomes an issue for any other platform targets.
1679358,2017-04-04 15:14:49 UTC,"Well, I wouldn't object to a patch to fix it (it would have to correctly handle the various different versions of the CPU architecture we implement, etc), but I'm not planning on writing one today myself."
1679366,2017-04-29 03:02:39 UTC,This issue sounds similar to bug 1679784.
1679366,2017-04-27 20:48:09 UTC,Had the crash on first update. Before that default installed nouveau driver is changed with nvidia-driver.
1679366,2017-04-18 04:29:39 UTC,"On Tue, Apr 18, 2017 at 01:44:03AM -0000, Austin Dempewolff wrote:

> I had the same crash while using the additional drivers GUI to switch
> the the proprietary nvidia drivers.
"
1679366,2017-04-18 01:44:03 UTC,I had the same crash while using the additional drivers GUI to switch the the proprietary nvidia drivers.
1679366,2017-04-13 22:47:45 UTC,"On Tue, Apr 11, 2017 at 11:42:18AM -0000, Jaime Cruz wrote:

> I don't know when it was installed, but I apparently already have
> libgtk2-perl Version 2:1.2498-1 on my system.
"
1679366,2017-04-11 01:05:42 UTC,"Thanks, Jaime.  Can you also tell us how you did this upgrade?  Was it an automatic, unattended upgrade, or did you use a graphical frontend - and if so, which one?"
1679366,2017-04-11 06:31:41 UTC,should be fixable by update-manager pulling in libgtk2-perl for the debconf frontend.
1679366,2017-04-11 01:30:06 UTC,I ran the default Ubuntu Software Updater and selected the choice to upgrade my system.  It wasn't unattended as it did pause at several points to ask questions before proceeding.
1679366,2017-04-03 23:50:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679366,2017-04-03 23:33:27 UTC,The error in the logs is:
1679366,2017-04-11 11:42:18 UTC,"I don't know when it was installed, but I apparently already have libgtk2-perl Version 2:1.2498-1 on my system."
1679366,2017-04-04 02:06:59 UTC,"Yes, I have VirtualBox installed on this system which has DKMS modules installed."
1679367,2017-04-03 23:10:55 UTC,"I noticed that once I made ONE shortcut change successfully, I no longer need to hold down the mouse button anymore, and I'm able to edit shortcuts normally."
1679369,2020-07-21 08:39:02 UTC,This package only contains support files for the python-cryptography tests and has no testable functionality of its own.
1679392,2019-06-21 08:03:12 UTC,"We have made other tests work using scsi_debug module [1] which usually is available and would work at least in ""isolation-machine"" environments.
One could check if/what sg tools can query from that."
1679392,2019-06-20 21:54:32 UTC,"This is a collection of binary cli tools and bash scripts that do hardware-specific operations.  There have only ever been 10 bugs filed against this package, and nearly all are packaging-related (e.g. sync requests.)  Thus, this package may see limited benefit of having dep8 tests."
1679403,2017-04-08 10:01:15 UTC,"The basic test that Squid application will start is already done by the squid package DEP-8 tests. Though that could be repeated as a test for this package with the simpler installation of only squid, squidclient and squid-langpack packages."
1679403,2017-04-10 15:48:50 UTC,"@yadi, thanks for looking at this! When I filed a number of bugs around missing dep8 tests I did my best to catch source packages that did not contain binaries/source-only."
1679405,2020-12-31 22:08:17 UTC,This bug was fixed in the package ssl-cert - 1.1.0
1679406,2021-01-31 09:33:36 UTC,This bug was fixed in the package sysstat - 12.5.2-1
1679425,2017-04-03 22:49:46 UTC,"The ""-b"" option is described as:"
1679425,2020-10-23 13:48:06 UTC,"Marking as won't fix given the age of the bug, and that native juju bundles would be used for this now."
1679426,2017-04-03 23:42:02 UTC,Not a bug: There is no “**” in POSIX shell or C either.
1679426,2017-04-03 23:59:08 UTC,"yeah, i don't have a use for this. (spotted it running a test.) just wanted to file this difference from bash for reference."
1679428,2017-08-18 11:20:11 UTC,"- unfortunately, I am no longer able to compile trunk on Windows, so I cannot test to see if the behavior has regressed. However I can confirm that the code that was part of this fix is still present in trunk, so if the behavior has regressed, then perhaps this is a new issue?"
1679428,2017-08-18 10:08:43 UTC,Behaviour seems to have regressed in trunk.
1679428,2017-04-22 18:27:34 UTC,fix committed to rev 15631
1679428,2017-04-03 23:59:31 UTC,"Reproduced in Inkscape 0.92.1 r15371, win 8.1 64 bit."
1679428,2017-04-03 23:27:06 UTC,"interrogation of the clipboard immediately after the two copy operations indicates that the error is probably happening during the copy. Below is the highly edited version of the clipboard after copying the original and the clone.
There are two significant differences:"
1679428,2017-04-03 23:03:30 UTC,"- load the file dest_px.svg, which has document units of px"
1679432,2017-04-03 23:59:43 UTC,"I found this line in syslog:
Mar 29 20:18:42 localhost kernel: [   13.829651]  remoteproc1: Direct firmware load for wcnss.mdt failed with error -2"
1679432,2019-10-15 12:04:09 UTC,"This seems like an issue with the kernel or with a specific snap (bluez), not snapd. I'm closing this bug as invalid but please feel free to re-open it and re-assign to another project as appropriate."
1679433,2017-04-03 23:38:44 UTC,This bug was fixed in the package flatpak - 0.8.5-1
1679440,2017-04-11 18:45:14 UTC,https://review.opencontrail.org/#/c/30296/ will fix this issue as well.
1679442,2019-12-31 05:47:47 UTC,Closing as part of migration to GitLab (see https://alpha.inkscape.org/bug-migration/)
1679442,2019-10-18 19:08:52 UTC,I had the same issue importing .jpg images taken from my mobile phone. The GIMP trick worked elegantly!
1679442,2019-03-15 14:43:47 UTC,"Also happens with all images from my Pentax camera.
It seems to be the embedded thumbnail."
1679442,2017-04-06 06:22:15 UTC,"Not reproduced on Windows 7 (64-bit) with lp:inkscape/0.92.x rev. 15413 (32-bit).
Somewhat reproduced with lp:inkscape rev. 15616 (MSYS2 devlibs, 64-bit). The imported image is empty, and the console shows a bunch of GdkPixbuf errors (see attachments). No error dialog."
1679442,2018-11-26 10:33:59 UTC,"reproduced on Windows 10, Inkscape 0.92+devel (e1eae41, 2018-11-16)"
1679442,2018-11-26 00:05:40 UTC,Same error with photos taken with a Moto G3 cel.
1679442,2019-03-09 00:05:44 UTC,Issue continues. Thank you for Gimp workaround. i had trouble with photos downloaded from my photos.google.com account or drive.google.com backups.
1679444,2017-04-04 02:57:57 UTC,"Aha.  The hook error occurs because a Xenial series unit was deployed when a Trusty one was expected.
 There is a known issue on this."
1679450,2017-06-28 05:22:24 UTC,"This looks strange, the postinst should only be triggered when you upgrade from an really old version, but the logs suggest that it's a fresh install. Is there anything else uncommon on your setup (like upgraded from an other version, third party repos like PPAs)?"
1679450,2017-06-28 05:33:58 UTC,"Nothing uncommon really. Just a usual setup with no third party repos. I'll
try to reproduce the problem and let you know if I could."
1679450,2017-07-05 11:00:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679450,2017-10-13 01:09:07 UTC,"Probably triggered by installing ROS, which pulls in vast amounts of stuff with pinned versions."
1679450,2018-10-28 13:34:20 UTC,"I have the same problem, and happened after installing the new ros2."
1679450,2019-03-21 01:05:59 UTC,"I agree that it's probably ROS related. That's a common element to my computer. Somewhere, I thought I saw something about ROS support for OPENNI being discontinued.  ROS used openni to communicate with the Microsoft Kinect 3D camera."
1679469,2017-08-07 11:26:27 UTC,"10:39:02 11: [ RUN ] NestedInput.pressed_keys_on_vt_switch_are_forgotten
10:39:02 11: [2017-08-07 10:39:02.461375] mirserver: Starting
10:39:02 11: [2017-08-07 10:39:02.462598] mirserver: Selected driver: mir:stub-graphics (version 0.27.0)
10:39:02 11: [2017-08-07 10:39:02.646267] mirserver: Using software cursor
10:39:02 11: [2017-08-07 10:39:02.654592] mirserver: Selected input driver: mir:stub-input (version: 0.27.0)
10:39:02 11: [2017-08-07 10:39:02.661740] mirserver: Mir version 0.27.0
10:39:02 11: [2017-08-07 10:39:02.817684] mirserver: Initial display configuration:
10:39:02 11: [2017-08-07 10:39:02.817972] mirserver: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed Output 1: VGA connected, used
10:39:02 11: [2017-08-07 10:39:02.818144] mirserver: . |_ Physical size 0.0"" 0x0mm
10:39:02 11: [2017-08-07 10:39:02.818280] mirserver: . |_ Power is on
10:39:02 11: [2017-08-07 10:39:02.818455] mirserver: . |_ Current mode 1920x1080 60.00Hz
10:39:02 11: [2017-08-07 10:39:02.818627] mirserver: . |_ Preferred mode 1920x1080 60.00Hz
10:39:02 11: [2017-08-07 10:39:02.818772] mirserver: . |_ Orientation normal
10:39:02 11: [2017-08-07 10:39:02.818951] mirserver: . |_ Logical size 1920x1080
10:39:02 11: [2017-08-07 10:39:02.819101] mirserver: . |_ Logical position +0+0
10:39:02 11: [2017-08-07 10:39:02.819257] mirserver: . |_ Scaling factor: 1.00
10:39:02 11: [2017-08-07 10:39:02.834017] mirserver: Starting
10:39:03 11: [2017-08-07 10:39:03.314596] mirserver: Using nested cursor
10:39:03 11: [2017-08-07 10:39:03.361471] mirserver: Mir version 0.27.0
10:39:03 11: [2017-08-07 10:39:03.501342] mirserver: Initial display configuration:
10:39:03 11: [2017-08-07 10:39:03.501724] mirserver: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed Output 1: VGA connected, used
10:39:03 11: [2017-08-07 10:39:03.501933] mirserver: . |_ Physical size 0.0"" 0x0mm
10:39:03 11: [2017-08-07 10:39:03.502100] mirserver: . |_ Power is on
10:39:03 11: [2017-08-07 10:39:03.502298] mirserver: . |_ Current mode 1920x1080 60.00Hz
10:39:03 11: [2017-08-07 10:39:03.502498] mirserver: . |_ Preferred mode 1920x1080 60.00Hz
10:39:03 11: [2017-08-07 10:39:03.502861] mirserver: . |_ Orientation normal
10:39:03 11: [2017-08-07 10:39:03.503068] mirserver: . |_ Logical size 1920x1080
10:39:03 11: [2017-08-07 10:39:03.503269] mirserver: . |_ Logical position +0+0
10:39:03 11: [2017-08-07 10:39:03.503421] mirserver: . |_ Scaling factor: 1.00
10:39:03 11:
10:39:03 11: GMOCK WARNING:
10:39:03 11: Uninteresting mock function call - returning directly.
10:39:03 11: Function call: handle_device_state(input_device_state(ts=17865731579909971, window_id=1, mod=none, btns=0, x=0, y=0 [1 btns=0 pressed=()])
10:39:03 11: NOTE: You can safely ignore the above warning unless this call should not happen. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to enforce the call. See https://github.com/google/googletest/blob/master/googlemock/docs/CookBo..."
1679469,2017-11-03 16:30:55 UTC,Syncing task from Mir.
1679478,2018-01-25 09:21:14 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3678
1679478,2018-01-18 08:27:21 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-802
1679479,2019-10-08 15:36:55 UTC,pr https://github.com/juju/juju/pull/10699
1679479,2019-10-23 00:24:13 UTC,Was released in beta1.
1679487,2017-04-04 06:24:23 UTC,PDF export
1679487,2017-04-04 06:24:58 UTC,pdf_tex export
1679487,2017-04-04 06:26:40 UTC,pdf_tex export from a previous Inkscape version (retrieve from my archives)
1679487,2017-04-04 06:31:49 UTC,Note: this SVG file also exhibits the following export error:
1679517,2017-05-17 17:01:29 UTC,How do you get this error? What steps should one follow in order to see this error message?
1679528,2017-07-12 14:01:47 UTC,"It's probably worth noting that at least Chrome seems to have been fixed to work with the system default of ""XDG_CURRENT_DESKTOP=Unity:Unity7"". That is, the original complaint of not being able to see Chrome/Hangouts icons in the notification tray is not an issue (don't know about Skype). However, I suspect there are still a lot of packages out there that have not been updated (and hence only work when the value is ""Unity"")."
1679528,2017-06-29 09:06:00 UTC,"As a temporary fix, one could also edit /usr/bin/skypeforlinux and add ""XDG_CURRENT_DESKTOP=Unity"" line.
But yeah, the edits to that script will be wiped out with package update or reinstall, since it is part of package space."
1679528,2017-05-01 20:03:48 UTC,"High importance but no updates for already one week?.. Hilarious! This bug is so annoying, I already regret upgrading my 16.10 to 17.04..."
1679528,2017-05-16 20:39:17 UTC,Take note that doing what is proposed in #10 will break some of unity-control-center apps
1679528,2017-05-09 17:51:48 UTC,"This is a pretty annoying bug, but I'm using another fix that's a lot easier than editing the `.desktop` shortcuts for all afflicted applications."
1679528,2017-04-27 09:02:37 UTC,Any update on this one? If tray notifications are deprecated then you should update the release notes.
1679528,2017-04-14 10:04:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679528,2017-04-20 10:52:26 UTC,"The problem seems to be that in 17.04, the XDG_CURRENT_DESKTOP variable changed from ""Unity"" to ""Unity:Unity7"" for some reason. I see no point in this change now, since both Unity 7 and Unity 8 are now dead, so maybe the simplest solution would be to revert this for the remaining lifetime of the this DE? This way all existing applications would still work."
1679528,2017-04-23 18:22:15 UTC,It seems the indicator is not displayed at all in Ubuntu 17.04 Zesty Zapus under Unity for *all* Electron-based applications. For me it's Discord that doesn't work.
1679528,2017-04-05 04:56:23 UTC,I applied the workaround described here [1].
1679528,2017-04-14 09:39:13 UTC,"Other applications also affected. For example, Slack."
1679528,2017-04-14 10:15:41 UTC,This might be related: http://www.webupd8.org/2017/04/fix-appindicator-not-working-for.html
1679528,2017-04-19 09:40:33 UTC,"The PIA icon also no longer appears, which is problematic as the application can only be controlled via the icon."
1679540,2017-04-04 09:38:34 UTC,Please attach diagnostic snapshot
1679540,2017-04-04 15:49:36 UTC,"The reverted environment has cluster-vrouter running. The task itself timed out, but after the revert everything was fine. We saw similar issues with other tests on this slave. Apparently, the jenkins slave running those tests is a possible culprit."
1679540,2017-04-07 08:41:40 UTC,"I reproduced this bug on another server. As workaround we can run redeploy environment. Thus, I can confirm the bug and decrease severity to high."
1679540,2017-04-10 10:53:58 UTC,For some reason it took almost 4 minutes for p_vrouter to start.
1679550,2017-04-04 09:01:51 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/453067"
1679550,2017-04-04 10:51:25 UTC,"Reviewed:  https://review.openstack.org/453067
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=55627d3e5cd16cc6ab4d92df6c3f4a9363003faf
Submitter: Jenkins
Branch:    stable/newton"
1679570,2018-07-12 09:23:23 UTC,"To extend this, when I duplicate an image file 'myImage.jpg' I would typically get something like 'myImage.jpg (2)'. This also results in an unrecognised file type for I assume the same reason."
1679570,2020-08-04 16:54:06 UTC,I tested with Pinta-1.7 latest build 1.7+r1134-202008032046~ubuntu18.04.1 and Pinta only checks file extension.
1679574,2017-04-04 10:31:28 UTC,"After doing some blind experimenting, trying a build with an attached DISPLAY=:0.0 before the actual test command the build still fails with: ""what():  Unable to connect to user bus: Failed to execute child process “dbus-launch” (No such file or directory)"". Installing dbus-x11 (which has dbus-launch) makes it go forward but then I get some test failures that fail the build. Besides, I don't think built-time unit tests should really depend on having a graphical stack - certainly I wouldn't want to add the dbus-x11 build-dep without a really good reason."
1679580,2017-04-04 09:57:15 UTC,"Hi,"
1679583,2017-04-25 07:31:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679583,2017-04-25 07:29:46 UTC,exactly same problem here. ~/.config/katemetainfos contains data about my recent files. there's no katerc in ~/.kde/share/config/.
1679583,2017-04-04 13:15:33 UTC,"More detail: this happens upon re-starting kate application. While kate is running, the list of recent files is available."
1679583,2017-04-04 11:33:25 UTC,Unable to replicate this using kate 4:16.12.3-0ubuntu1 here. My list of recently opened file is being populated as it should.
1679583,2017-04-04 13:27:23 UTC,"All the files recently opened by me are listed in the file .config/katemetainfos , including those opened long ago (kate launched and exited several times since)."
1679598,2017-04-04 10:12:19 UTC,Here's an example with the test passing for the same kernel/systemd versions as fail later (4.10.0-15/232-19):
1679599,2017-04-04 10:32:24 UTC,I'm not sure we really want to allow overriding all those components (IIUC they are not overridable by design).
1679599,2017-04-04 16:11:29 UTC,I don't think this is desired. UbuntuWebView deprecates the legacy API points for providing UI components and making them unavailable in the new webview is deliberate.
1679601,2017-04-04 10:19:54 UTC,"Is there a solution or do I have to format the computer?
If I have to format the computer I would like to have a boot disk so I do not have to go through windows first, is it possible?"
1679609,2017-04-04 11:00:33 UTC,another video
1679618,2017-06-28 13:44:59 UTC,"I managed to fool this BUG in a practical way, in version v0.91 and v0.92 Inkscape
Using 5 steps, which are these:"
1679618,2017-07-08 12:34:06 UTC,Deleting the attached diff - I am revoking my pending patches provided in this bug tracker for issues with python-based extensions distributed with Inkscape.
1679618,2017-04-27 03:05:30 UTC,"Proposed patch (per bug summary) attached:
Use cubicsuperpath.parsePath() to convert elliptical arc curve commands to cubic bézier curve commands which are then processed (after being converted from 'cubicsuperpath' to 'simplepath' syntax) as expected by the extension's effect() method."
1679618,2017-04-04 13:13:20 UTC,"Sorry for long posts, I hope this can be helpful in debugging.
 I've found and a 4'th BUG, but I don't know if is different from previous 3.1Bug, because have some similarity :"
1679618,2017-04-04 12:35:52 UTC,"Also I've found a 3'rd BUG that I think is related with previous:
3a) First create an circle like in attached file : BUG3.svg
- Make sure fill color is #000000 and doesn't have Stroke
3b) Then Convert shape to Path
3c) Select all nodes after Convert shape to path
3d) Press Arrow UP key (Will move object with some pixels in up dirrection)
3e) Press Arrow DOWN key (Will return object to first/original location)
3f) Save file as... --> Optimized SVG (*.svg)
*) in Options tab CHECK only : Convert CSS attributes to XML attributes; Collapse groups and Work around renderer bugs
*) in SVG Output tab make sure that ALL check boxes are SELECTED
*) in IDs tab -> select only Remove unused IDs
3g) After save is complete close all Inkscape windows and open only saved file
3h) Now select that circle aready created, and you will notice somethig strange in status bar :"
1679618,2017-04-04 11:44:43 UTC,"I've found some workarounds, unfortunately I CAN'T do this from Inkscape verbs, and icons doesn't have only circles or only rectangles to be able to see only broken shadows :"
1679618,2017-04-04 10:53:34 UTC,"My script do :
- First i optimize all files with scour
- Get objects ID's from : inkscape -f ""$file_name"" -z --query-all IGNORIG first id (starting with svg'Number', I don't why this is displayed, maybe is svg ID)
- If exists any groups in file, founded id's isn't corect, so it will open ""$file_name"" in Inkscape, UnGroup N (where N is number of groups) times, save and get again ID's.
- Now i have all ID's into array
- An extra step to verif ID's is to make a copy of $file_name"" select all founded id's, delete them and save. Then i check for nr. of id to be 0
- If ID isn't start with path*, it's mean that object with that id is not a path and need to be converted (ex: circle, ellipse, text). Because .svg file was optimized there's no any manual ID name, so NO mistakes were made.
- Now i open file in file in Inkscape, select ID's, convert them to path if needed, then using verb : --verb=org.ekips.filter.motion.noprefs it will generate long shadow for selected objects.
- After that I Ungroup ALL, delete ONLY objects with founded ID's, select all remaining objects and union them"
1679625,2017-04-18 08:07:31 UTC,"We ran all tests with Dell support and they tell us, there is definitely no hardware problem. Any ideas on how to proceed? Thanks"
1679625,2017-04-25 11:05:43 UTC,The error was triggered by a subcommand of the backup script.
1679626,2017-04-05 01:58:56 UTC,Hot plugging works perfectly in Mir (demo servers). However Unity8 has its own policies and I know for a fact they're not implemented yet :)
1679634,2017-07-07 11:30:42 UTC,I have the same problem in debian 9 with optimus laptop with:
1679634,2017-04-04 13:30:43 UTC,"Ref to your comment#2 i confirm the same error message being printed during bootup, for latest 4.11.RC5 kernel and 4.10.7-041007-generic."
1679634,2017-04-04 12:47:42 UTC,#2 sure i will give both kernels a try and report back. let me install them and get back.
1679634,2017-05-20 13:46:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679634,2017-04-04 12:45:25 UTC,apport information
1679634,2017-04-04 12:26:51 UTC,Does the bug not happen with 4.10.7?
1679634,2017-04-04 11:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1679634,2017-04-04 12:45:26 UTC,apport information
1679634,2017-05-20 13:46:30 UTC,I confirm the bug exists on kernel 4.11.1 and Dell precision 5520 with Nvidia Quadro 1200M:
1679636,2017-11-20 18:07:56 UTC,What virtual env are you using?
1679647,2017-04-05 19:29:40 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1679659,2017-04-04 16:02:45 UTC,"For some context, this is linked to https://code.launchpad.net/~santoshbit2007/oxide/+git/oxide/+ref/UITK_FilePicker_Impl where the new Oxide.Ubuntu WebView provides a default file picker implementation. This default implementation cannot replace that of the browser as it is today, because the browser has a specific code path for when the browser itself is selected as the content provider."
1679671,2017-04-05 10:16:17 UTC,"Thanks for reporting the issue. The failed test was because the version of spl-dkms and zfs-dkms in Xenial aren't compatible to Linux 4.9/4.10. But this shouldn't bother most use cases a lot since we have those ko files prebuilt in linux-image-* packages, and only userland utilities like zfsutils-linux are required."
1679671,2017-11-17 11:22:58 UTC,"Hi @happyaron,"
1679671,2018-01-11 10:19:48 UTC,"Actually, no, the .ko files are NOT there in linux-image-extra-4.13.0-26-generic for example."
1679688,2017-04-04 15:01:51 UTC,"+1, the test names/summary should list both IMHO. That being said you can easily toggle the test names and test ids by pressing 'i' on the test selection screen. HTH till we fix that preperly"
1679692,2017-04-05 12:56:21 UTC,"Oleksiy,"
1679692,2017-04-05 08:53:45 UTC,"Hi Luca, please attach diagnostic snapshot."
1679711,2017-08-15 08:49:49 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1679715,2019-03-22 15:55:57 UTC,"Valeriy is this still happening in current manila releases?  The log link is older and not working, can you send a new link so someone can take a look?"
1679715,2019-08-08 16:19:12 UTC,"This bug is a duplicate of #1762900 and not just a problem with the Container driver. Use of dynamic credentials with multi-tenancy mode drivers (driver_handles_share_servers=True) is not supported within manila_tempest_plugin; the alternative is to use pre-provisied tempest credentials to run the tests, see: https://docs.openstack.org/tempest/latest/configuration.html#pre-provisioned-credentials"
1679725,2017-04-04 14:55:26 UTC,"An update: apparently it can be upgraded to zesty's version. But by default apt and aptitude don't find the correct upgrade path, probably because it concerns i386 on amd64."
1679725,2021-01-10 23:20:42 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1679727,2017-04-04 15:38:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679727,2017-04-04 15:44:03 UTC,Also related: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1129402
1679727,2017-04-19 15:00:17 UTC,Same issue in machined containers.
1679727,2017-05-05 05:50:00 UTC,I published fixed package: https://yadi.sk/d/_vXq0WdR3HgbTJ
1679727,2017-06-02 09:08:31 UTC,Joyent lx-brand user here with Ubuntu 14.04 image. Any guidance on how to work around this please?
1679727,2017-06-02 16:38:31 UTC,Check comment #4
1679739,2019-10-15 11:44:58 UTC,I'm moving this to the snapd project and triaging as high importance.
1679739,2017-08-10 15:17:06 UTC,i know there was a discussion about simply dropping the date checks from assertion verification but i can not find it on https://forum.snapcraft.io now ...
1679739,2017-08-10 15:09:47 UTC,if fixrtc works the date can not be 1970 ... (it can surely be off by some margin but never be the epoch)
1679739,2017-08-10 14:26:07 UTC,"Including the patch from LP: #1696981 would be an improvement on the current fixrtc, as it looks into the date of some files in the system. I have found that some times the mount date is 1970 on first boot."
1679739,2017-08-10 08:55:41 UTC,"The fixrtc solution feels like a bit of a workaround and not a solution. Even with the date/time set by fixrtc we've seen valid system-user assertions fail. The problem is that when a system-user assertion fails, you cannot login to the device to check the logs. From what I remember, it's a silent fail so you have no idea why the system-user is not created."
1679739,2017-04-04 15:43:47 UTC,Some observations that people have made:
1679739,2017-04-04 15:43:08 UTC,systems defaulting to a 1970 date should not be possible if they are ported correctly.
1679744,2017-04-04 15:55:12 UTC,"StacktraceTop:
 pa_hashmap_get (h=h@entry=0x180, key=key@entry=0x7f1d4a9c6d28) at pulsecore/hashmap.c:182
 pa_proplist_gets (p=0x180, key=key@entry=0x7f1d4a9c6d28 ""device.description"") at pulse/proplist.c:283
 publish_service (api=<optimized out>, service=0x55e4d289b910) at modules/module-zeroconf-publish.c:318
 once_callback (m=0x55e4d2740688, e=0x55e4d2752780, userdata=<optimized out>) at pulse/mainloop-api.c:45
 dispatch_defer (m=0x55e4d2740630) at pulse/mainloop.c:680"
1679744,2017-05-16 07:27:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679744,2017-05-16 07:29:49 UTC,"Now being tracked in:
https://errors.ubuntu.com/problem/81f2b8597aa91cc904dafb7f0ea2b38a8755f27d"
1679747,2019-10-15 12:02:50 UTC,"This seems like an issue with the kernel or with a specific snap (bluez), not snapd. I'm closing this bug as invalid but please feel free to re-open it and re-assign to another project as appropriate."
1679750,2018-04-12 01:38:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/560706"
1679750,2018-04-20 17:06:02 UTC,"Reviewed:  https://review.openstack.org/560706
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ea9d0af31395fbe1686fa681cd91226ee580796e
Submitter: Zuul
Branch:    master"
1679750,2018-04-20 19:00:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/563236"
1679750,2018-05-16 18:31:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/568925"
1679750,2018-05-19 01:55:47 UTC,"Reviewed:  https://review.openstack.org/568925
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3abd5f5797737b54c10ea85d4b833aff054d1bee
Submitter: Zuul
Branch:    master"
1679750,2018-05-22 08:20:12 UTC,"Reviewed:  https://review.openstack.org/563236
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cba1a3e2c1b161204a3662a0d9fbf33da38aa7d3
Submitter: Zuul
Branch:    stable/queens"
1679750,2018-07-05 18:45:45 UTC,Someone else reported this biting them in Pike today:
1679750,2018-06-08 12:25:46 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1679750,2018-06-28 13:14:30 UTC,"It looks like we may be affected by this issue on pike, is it possible to backport the fixes there?"
1679750,2018-06-28 17:31:23 UTC,"Well, we backported it to stable/queens and it's marked for pike as well, so I'm not sure I intended on backporting it to pike and just forgot, or if there was a good reason to avoid backporting it to pike - note it's not just a single change though and there is another related bug fix tied up in this series:"
1679750,2018-07-05 20:35:23 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580498"
1679750,2018-07-09 19:31:55 UTC,"Reviewed:  https://review.openstack.org/580498
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd50dcaf3e51722c9510d417c1724d8cdafe450b
Submitter: Zuul
Branch:    stable/pike"
1679750,2018-03-26 15:08:13 UTC,"@Matt, I already made some scripts that check if the records in the placement API match the nova instances and if not it prints a SQL command that corrects the issue."
1679750,2018-06-04 13:52:33 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1679750,2018-03-26 14:49:24 UTC,"@Henry, if you need to cleanup placement, there is the osc-placement CLI plugin available for some of this:"
1679750,2017-08-09 03:01:25 UTC,"Reviewed:  https://review.openstack.org/470578
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4ba7baf451512d72b14f51cefe762642fabeda3e
Submitter: Jenkins
Branch:    master"
1679750,2018-02-19 14:22:58 UTC,"@henryspanka: could you provide some more information about your setup, please? Does the hypervisor report 123 **free vCPUs** and placement is reporting 146 **total** vCPUs? Because that would be an expected result."
1679750,2017-04-04 16:09:57 UTC,"There might be something in the periodic resource tracker updates that fixes the allocations once host A comes back up, but I'm not sure."
1679750,2017-04-04 19:12:33 UTC,"Another thing to note here is the nova-api service does not currently use the placement API for anything. If we fixed this by doing allocation cleanup from nova-api, we'd have to make nova-api dependent on placement, which is something we might not want to do since only nova-scheduler and nova-compute depend on placement today. We might be able to just fix this by doing a cleanup during init_host in the compute service."
1679750,2017-04-10 14:46:34 UTC,"To move forward on this, we should write a functional test which does the following:"
1679750,2017-06-02 23:15:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/470578"
1679750,2018-09-24 14:46:53 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1679750,2018-02-19 14:45:35 UTC,@jaypipes: The hypervisor reports 123 **in use** vCPUs while the placement API reports 146 **in use** vCPUs.
1679750,2017-08-15 13:52:49 UTC,Is this still a valid bug? It seems that the related functional test asserts the expected behavior and it is passing.
1679750,2017-09-07 13:48:21 UTC,Alex also raised a good question in this conductor code during a build:
1679750,2017-11-06 02:16:38 UTC,Related patch: https://review.openstack.org/#/c/517836/
1679750,2017-11-06 05:34:52 UTC,"Reviewed:  https://review.openstack.org/517836
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=57a3af6921dea72b3b2972f66e089578331dbb63
Submitter: Zuul
Branch:    master"
1679750,2017-11-06 07:41:22 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/517876"
1679750,2017-11-07 03:10:06 UTC,"Reviewed:  https://review.openstack.org/517876
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2cd20613e3237754df7c4e73995ac5fdc10a1298
Submitter: Zuul
Branch:    stable/pike"
1679750,2018-01-21 19:41:49 UTC,"Hello,
I currently have the same issue. Is there any way to remove stale resources and clean up the placement api?"
1679750,2017-08-22 19:27:03 UTC,As the commit message in Mel's test patch points out:
1679764,2017-04-04 16:44:26 UTC,"Note that the ""error: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found."" is reported in bug #1672499."
1679764,2017-04-04 16:42:44 UTC,"autopkgtest [17:28:29]: test boot-smoke: [-----------------------
reboot #0
bash: line 1: 32362 Killed                  /tmp/autopkgtest.eXsKq9/build.l7Q/systemd-232/debian/tests/boot-smoke 2> >(tee -a /tmp/autopkgtest.eXsKq9/boot-smoke-stderr >&2) > >(tee -a /tmp/autopkgtest.eXsKq9/boot-smoke-stdout)
autopkgtest [17:28:35]: test process requested reboot with marker 1
checking for failed unmounts for user systemd
checking for connection timeouts
checking that polkitd runs
219
checking that there are no running jobs
running jobs after remaining timeout -1:   2 dev-vda2.device start running
autopkgtest [17:29:33]: test boot-smoke: -----------------------]"
1679765,2020-05-20 01:26:57 UTC,Extrausers is a concept introduced by the libnss-extrausers package.  shadow and passwd simply know nothing about it.
1679816,2017-07-18 13:23:16 UTC,https://review.openstack.org/#/c/469838/
1679823,2017-06-06 14:58:17 UTC,This bug was fixed in the package linux-hwe - 4.8.0-54.57~16.04.1
1679823,2017-05-25 08:59:31 UTC,This bug was fixed in the package linux-hwe - 4.8.0-53.56~16.04.1
1679823,2017-05-25 08:58:59 UTC,This bug was fixed in the package linux - 4.8.0-53.56
1679823,2017-05-23 16:55:17 UTC,"So for me the situation with 4.8.0-53 is that in contradiction to 4.8.0-49 the system is working again and doesn't suffer from broken network configuration.
So it isn't a blocker any more."
1679823,2017-05-23 16:31:00 UTC,Linux odie 4.8.0-53-generic #56~16.04.1-Ubuntu SMP Tue May 16 01:18:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1679823,2017-05-23 14:33:02 UTC,Works inside a virtual machine
1679823,2017-05-23 14:20:04 UTC,"With 4.8.0-53 in -proposed, e1000e works without any problem."
1679823,2017-05-23 11:49:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1679823,2017-06-08 06:17:35 UTC,Any progress on Zesty?
1679823,2017-05-23 09:43:23 UTC,The fixes for this issue are also included on Xenial linux-hwe 4.8.0-53.56~16.04.1 which is currently on -proposed.
1679823,2017-05-23 08:56:21 UTC,"These patches are in 4.8.0-53, which is in -proposed right now. It will be available in -updates with next SRU release if everything goes well."
1679823,2017-05-23 08:35:54 UTC,"I am running Ubuntu 16.04.2 LTS with 4.8.0-52-generic (#55~16.04.1-Ubuntu) and still have the problem as reported in [#6](https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1679823/comments/6). Everything should be up to date on my side, linux-generic-hwe-16.04 is of version 4.8.0.52.23."
1679823,2017-05-23 08:11:20 UTC,"Hi,"
1679823,2017-05-23 07:29:39 UTC,"I second question #56. However, Xenial is not present in the list at the top so maybe it is being overlooked right now? I could not find out how to add it, though."
1679823,2017-05-23 01:16:54 UTC,Just a question - is there any progress to fix this showstopper in xenial ?
1679823,2017-05-12 21:52:06 UTC,"We really need to get xenial added for its HWE kernels:
we have several BootStacks running with them, mainly for
latest needed drivers while keeping LTS (mellanox for
VNFs as an example)- all these are  now obviously at
risk on the next reboot."
1679823,2017-05-11 08:02:26 UTC,Re-open zesty task because some patches are still missing (for example the fix for openvswitch).
1679823,2017-05-10 15:58:08 UTC,"@Thiago, same for us. Hope it will be fixed soon !"
1679823,2017-05-23 09:14:58 UTC,Sorry about the confusion: the commits are tagged with -53 and I mentioned -52 in the apt output.
1679823,2017-06-08 06:39:14 UTC,@vaaend:
1679823,2017-06-08 13:55:23 UTC,"4.10 series (hwe-edge) kernel doesn't seem to have gotten these fixes yet, as 4.10.0-22-generic #24~16.04.1-Ubuntu still fails to set openvswitch MTU correctly. When can we expect a fix to be released for -edge?"
1679823,2017-06-08 17:23:23 UTC,"Ok, so the fix is rather trivial. I've verified that building 4.10.0-22 kernel from Ubuntu sources with the following patch fixes the OpenvSwitch MTU issue:"
1679823,2018-02-23 13:41:45 UTC,"> I have the same problem with my DELL server. Can't set MTU > 1500 with current kernel.
"
1679823,2018-02-23 10:52:06 UTC,I have the same problem with my DELL server. Can't set MTU > 1500 with current kernel.
1679823,2018-02-23 10:50:54 UTC,apport information
1679823,2018-02-23 10:50:53 UTC,apport information
1679823,2018-02-23 10:50:50 UTC,apport information
1679823,2018-02-23 10:50:48 UTC,apport information
1679823,2018-02-23 10:50:46 UTC,apport information
1679823,2018-02-23 10:50:45 UTC,apport information
1679823,2018-02-23 10:50:43 UTC,apport information
1679823,2018-02-23 10:50:42 UTC,apport information
1679823,2018-02-23 10:50:40 UTC,apport information
1679823,2018-02-23 10:50:38 UTC,"AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116,  1 Feb 16 13:45 seq
 crw-rw---- 1 root audio 116, 33 Feb 16 13:45 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=7d50a0ab-30df-4053-8e22-891d5d2a1aa3
InstallationDate: Installed on 2018-02-14 (8 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS ""Xenial Xerus"" - Release amd64 (20170215.8)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge T110 II
Package: linux-hwe-edge (not installed)
PciMultimedia:"
1679823,2017-06-21 09:16:57 UTC,"It happens when test for kernel in -proposed (in this case 4.10.0-23) is not yet completed, and an important security issue must be addressed. In this case 4.10.0-24 is based on a fully tested 4.10.0-22, and changes in 4.10.0-23 will be included in later release instead."
1679823,2017-06-20 16:51:44 UTC,"# apt update
[...]
# apt install linux-image-4.10.0-23-generic
N: Unable to locate package linux-image-4.10.0-23-generic"
1679823,2017-06-20 16:19:25 UTC,"4.10.0-24 is a 4.10.0-22 with CVE fix applied, that's why it doesn't have the fix for openvswitch which is in 4.10.0-23."
1679823,2017-06-20 16:02:20 UTC,The MTU problem affecting OpenvSwitch bridges still exists (or resurfaced) in linux-generic-hwe-16.04-edge (4.10.0.24.17).
1679823,2017-06-16 10:03:28 UTC,linux-generic-hwe-16.04-edge from xenial-proposed repo fixes the problem.
1679823,2017-06-09 10:01:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679823,2017-06-09 02:46:53 UTC,@shapemaker:
1679823,2017-05-10 13:55:15 UTC,I'm also expecting this on Xenial ASAP!
1679823,2017-05-10 12:26:51 UTC,"Any chance, that xenial will be fixed anytime soon? :-)"
1679823,2017-05-02 13:47:28 UTC,"Success.
#38 works with bnx2x
Thanks a lot."
1679823,2017-05-04 16:48:41 UTC,"@Thiago, yes I confirm."
1679823,2017-04-29 11:47:20 UTC,"Can confirm, this bug, is present in 4.8.0-49"
1679823,2017-04-28 18:33:12 UTC,I was experiencing issues with OpenStack deployed with Networking OVN and just saw this message in my dmesg:
1679823,2017-04-28 13:52:06 UTC,Any progress in fixing this issue for xenial hwe kernel ?
1679823,2017-04-26 04:49:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679823,2017-04-26 02:35:23 UTC,"It affects Neutron, qr-* and ha-* interfaces can be set with a MTU higher than 1500.
Look the output in #13 comment."
1679823,2017-04-25 22:04:42 UTC,"1. xenial is missing in linux-hwe distributions
2. @jsalisbury: The systems here running xenial with hwe kernel."
1679823,2017-04-25 21:09:41 UTC,"@Joseph, I tried with 4.10.0-20-generic"
1679823,2017-04-25 20:10:42 UTC,"@goldyfruit, your still having an issue with the test kernel I posted in comment #12?"
1679823,2017-05-01 14:04:06 UTC,Can folks affected by this bug see if it is fixed with the kernel posted in comment #12?  To test that kernel you would need to install both the linux-image and linux-image-extra .deb packages.  You should see this bug number in the output of uname -a if it the kernel is installed and booted.
1679823,2017-04-25 19:56:36 UTC,"Still having and issue, for the physical interface it's working as expected but for virtual interfaces I got the same error."
1679823,2017-04-25 18:01:30 UTC,"@Joseph, 4.10.0-20-generic works for me.
Thanks !"
1679823,2017-04-25 17:03:07 UTC,The fix to this bug is in the Ubuntu-4.10.0-15.17 kernel.
1679823,2017-04-25 15:18:21 UTC,"This bug is a serious blocker, because after kernel update (4.8.0-49) it renders the system unusable if in a link file jumbo frames are specified."
1679823,2017-05-05 14:05:15 UTC,"Nice goldyfruit, thank you!"
1679823,2017-04-25 14:31:35 UTC,I had a kernel upgrade 4.8.0-46 to 4.8.0.49 and I had the same issue.
1679823,2017-04-23 01:38:05 UTC,This fix was merged and landed in 4.10.5
1679823,2017-04-05 13:47:58 UTC,The upstream bug report says the fix will be send to v4.10 stable.  Do you happen to know the mainline SHA1?
1679823,2017-04-04 19:46:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1679823,2017-04-25 19:51:36 UTC,I built a Yakkety test kernel with a pick of commit 3331aa378e9bcbd0d16de9034b0c20f4050e26b4.  The test kernel can be downloaded from:
1679823,2017-05-01 15:14:16 UTC,@jsalisbury: I can still reproduce this issue with the kernel in #12...
1679823,2017-04-25 15:11:26 UTC,As above the same issue degraded my system after reboot from 4.8.0-46 to 4.8.0-49.
1679823,2017-05-01 20:47:46 UTC,Thanks for the testing feedback on my test kernel.  I suspect more than just commit 3331aa378e9bcbd0d16de9034b0c20f4050e26b4 is needed.   dev->max_mtu being set to ETH_MAX_MTU must be needed in other spots.  I'll investigate and post another test kernel shortly.
1679823,2017-05-04 16:20:31 UTC,"@goldyfruit, can you confirm if it also fixes the BUG: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742 ?"
1679823,2017-05-04 14:43:39 UTC,Downgraded to 4.4 series. :(
1679823,2017-05-04 12:53:13 UTC,@martinx - To mitigate the problem I've dropped temporally jumbo frames from the configuration of my servers.
1679823,2017-05-03 16:20:18 UTC,The kernel in #38 does fix this for Zerotier TAP interfaces as well.
1679823,2017-05-02 21:54:02 UTC,I also have a production environment running into network issues... Planning to downgrade the kernel to 4.4 series...    =(
1679823,2017-05-02 15:51:32 UTC,"Sorry, I can't do experiments on production server :-("
1679823,2017-05-02 15:25:45 UTC,@michal did you try this kernel: https://people.canonical.com/~jesse/lp1679823v2/ ?
1679823,2017-05-02 14:58:07 UTC,"Success.
#38 works with ixgbe"
1679823,2017-05-02 15:13:31 UTC,"mlx4_en ( Mellanox Technologies MT26448 )
4.8.0-49-generic"
1679823,2017-05-02 13:11:51 UTC,"Hi Jesse,"
1679823,2017-05-02 10:08:35 UTC,"Another commit is required for bnx2x, let me build a test kernel with it."
1679823,2017-05-02 09:55:25 UTC,Unfortunately still failing for me with kernel from #34
1679823,2017-05-02 06:27:48 UTC,@jsalisbury: I figured it out...
1679823,2017-05-02 02:03:31 UTC,"Thanks, Jesse.  I'll investigate further.  I'll probably try to reproduce the bug to make debugging faster."
1679823,2017-05-02 01:07:34 UTC,It still fails with the kernel in #31.
1679823,2017-05-01 23:54:09 UTC,"After a review, Yakkety did get the following commits via other bug reports:"
1679823,2017-05-01 21:06:25 UTC,"It appears commit 3331aa378e9 fixes commit 91572088e3fd.  However, commit 91572088e3fd was introduced in v4.10-rc1 and not cc'd to stable.  The Yakkety 4.8 kernel never had commit 91572088e3fd applied.  That explains why my test kernel did not fix this bug."
1679823,2017-05-02 13:30:04 UTC,"Hi @narurien and @gaetan-trellu,"
1679823,2017-05-01 16:49:49 UTC,any news about kernel 4.10.0-20 to fix also openvswitch interfaces (bug 1685742) ?
1679828,2017-04-04 20:39:55 UTC,"Just as a side note, I tried getting the source code of Terminator to see if I could figure out how to implement this myself. I'm not getting very far with getting things up and running (on Ubuntu)."
1679828,2017-04-04 21:27:53 UTC,See: https://gnometerminator.blogspot.com/2015/09/so-you-want-to-try-terminator-gtk3.html
1679829,2017-04-05 08:13:16 UTC,Needs a resync of charm-helpers.
1679833,2018-02-05 15:39:10 UTC,"On Mon, Feb 5, 2018 at 9:03 AM, Rod Smith <email address hidden> wrote:

> We're still doing disk/smart tests, so removing that would not be an
> option. (Unless Jeff is thinking of dropping those tests...?)
"
1679833,2018-02-05 14:03:25 UTC,"We're still doing disk/smart tests, so removing that would not be an option. (Unless Jeff is thinking of dropping those tests...?)"
1679833,2018-02-05 12:33:35 UTC,"IIRC we dropped disk/smart tests from client test plans. If you don't need them as well in server cert, we could remove smartmontools from the provider recommended packages."
1679833,2017-04-04 21:30:21 UTC,"As Rod's MR in the summary indicates, you can work around this superficially by forcing the install of sendmail."
1679833,2017-04-04 20:52:00 UTC,So the issue appears to be due to smartmontools:
1679833,2017-04-04 22:17:51 UTC,"I tried something similar to your example of setting Postfix options via debconf in our preseed, but it didn't work. There may well have been an error in the way I was doing it, but I gave up on it quickly because it took about two dozen lines. (I extracted the debconf settings from an install of Postfix, and there were a couple dozen settings.) It was therefore much simpler, from a scripting point of view, to just add ""sendmail"" to the already-short list of packages to be installed."
1679834,2017-05-22 17:16:07 UTC,"I'm not sure I think this a good idea, or the correct understanding of Ironic's architecture."
1679834,2017-05-22 18:04:27 UTC,"Right, that's one opinion. My thought on this is, deploy interface should only implement the things that are defined in base deploy interface. There is no easy way to define that e.g. in reboot_and_finish_deploy method you need to do remove_provisioning_network, add_tenant_network, attach_storage etc. If it was all done by the conductor, the deploy interface could concentrate solely on the thing it was created for - writing the image on the node's disk, either via iscsi, or agent commands, or like in case of ansible deploy driver running ansible playbooks there. This would also mean that implementing cinder storage interface enables it for all deploy interfaces, not just the two that we currently have in tree."
1679834,2017-05-23 13:36:54 UTC,"dtantsur wanted a spec, added a tag"
1679834,2017-05-25 11:30:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/468000"
1679834,2017-06-22 15:29:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/476601"
1679834,2018-05-03 11:02:35 UTC,"Change abandoned by Vladyslav Drok (<email address hidden>) on branch: master
Review: https://review.openstack.org/468000"
1679834,2018-05-03 11:02:50 UTC,"Change abandoned by Vladyslav Drok (<email address hidden>) on branch: master
Review: https://review.openstack.org/453139"
1679844,2019-09-19 11:56:18 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1679867,2017-04-20 05:46:33 UTC,"I am no expert here, but systemctl_redirect() simply returns the exit code of '/bin/systemctl --no-pager $sctl_args $command ""$service""'."
1679871,2017-04-05 00:03:40 UTC,"I've added four screenshots to show everything I see when running
   DEJA_DUP_DEBUG=1 deja-dup --backup
from the command line."
1679871,2017-04-05 01:40:09 UTC,"One additional observation: clicking ""remember password"" does not result in the password being remembered."
1679873,2017-04-05 00:30:56 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1679873,2017-04-06 09:34:21 UTC,Added task for linux-firmware to add the firmware. Will the firmware also be wanted in xenial for the hwe kernel?
1679873,2017-07-26 15:50:04 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1679883,2018-12-17 01:00:02 UTC,Me too. Arch Linux with Arc Dark theme.
1679902,2017-04-05 05:02:11 UTC,"How do cerbere, plank, and wingpanel handle SIGHUP?
https://bbs.archlinux.org/viewtopic.php?pid=1617469#p1617469"
1679902,2017-04-05 05:12:31 UTC,Workaround from that github discussion:
1679902,2017-04-06 00:36:50 UTC,Note that above workaround will start dumping cores (core.$pid) into ~/
1679908,2017-04-05 05:05:30 UTC,Bisected. The problem started in r4103:
1679908,2017-11-03 16:31:01 UTC,Syncing task from Mir.
1679921,2017-04-07 23:02:43 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1679926,2017-04-06 02:32:09 UTC,Agreed that the current state of HA isn't ideal and that this would be good to fix. I can't guarantee when we can get to this though.
1679926,2018-03-09 14:04:20 UTC,https://github.com/juju/juju/pull/8456
1679926,2020-08-02 01:56:00 UTC,"""juju remove-machine -m controller 1 2"" (as an example) has been working for a while now[0], the machines are removed from the replica set and all the cleaning up allows to run a single controller. I believe this bug can be declared as ""fix released""."
1679939,2017-04-07 23:06:56 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1679955,2017-09-21 12:53:59 UTC,"For the cinder and cinder-ceph charms, please bind the 'ceph' relation to the ceph public network space so that the units deployment will have the correct network connectivity."
1679955,2017-09-21 12:55:15 UTC,"The 'Network Space support' section in the Cinder charm is not fully comprehensive; adding a doc tag and Triaging as 'Low' as this is a documentation gap, not a functional problem."
1679955,2017-09-21 12:56:21 UTC,From docs:
1679957,2017-04-05 08:30:09 UTC,This change was made by a bot.
1679962,2017-05-05 18:26:40 UTC,"Hmm, I enabled all psmouse protocol detection in that one, apparently it didn't work."
1679962,2017-05-06 11:37:05 UTC,"Sorry, Kai_heng, I upload attached details on my previous post as ""files.tar.xz""
What need you?"
1679962,2017-05-08 08:04:47 UTC,Probably. Is it an HID devices in Windows 10?
1679962,2017-05-08 14:56:46 UTC,Hello
1679962,2017-05-17 07:38:38 UTC,"Hmm, try this:"
1679962,2019-01-10 16:23:03 UTC,I have a Lenovo W530 and I am having the same problem as others describe.  I found these messages from dmesg:
1679962,2017-05-24 22:48:59 UTC,"I think I observe a very similar issue on ubuntu 16.04, only in my case mouse reaction to touchpad is very laggy and jumpy/choppy. It started after one of the recent kernel updates. For me linux-image-4.4.0-72-generic seems to work fine with default kernel options, linux-image-4.4.0-78-generic is broken, so it must be one of the changes between these two version which breaks this."
1679962,2017-05-25 04:53:52 UTC,"@slimbook,"
1679962,2018-11-28 13:55:46 UTC,"I had similar problem after upgrading from Ubuntu 14.04 to 18.04 (Ubuntu 4.15.0-42.45-generic 4.15.18). I noticied that when I shut down wifi the touchpad lag is gone. Also when I turn wifi on again, the lag doesn't re-appear. After restarting my laptop the lag is back again.
Dmesg shows (after the turning wifi off and on again) an extra piece of information (although I don't know what it means):"
1679962,2017-05-05 07:30:00 UTC,A quick google shows that Hantick sells rebranded Elan touchpad (in Chinese though) - that's why I asked this question.
1679962,2017-05-19 08:12:40 UTC,"Hello Kay-Heng,
We do it, and the pointer is crazy, not work correctly."
1679962,2017-05-04 12:26:30 UTC,"Sorry, ""Hantick"""
1679962,2017-05-05 12:27:10 UTC,"Hello,
Nothing has changed.
Attached information.
Thank you very much."
1679962,2017-05-04 08:12:01 UTC,"Hi Slimbook,"
1679962,2017-05-03 11:46:38 UTC,"Hello, thanks jesulinico."
1679962,2017-05-04 08:36:03 UTC,"Hello Kai-Heng,
I wrote the manufacturer at the beginning of the bug: Hantik
We can temporarily give one up for testing.
Thanks"
1679962,2017-04-29 19:39:17 UTC,"It's a serious trouble, slimbook the user who reported the bug, represents a whole brand that is making great efforts to spread free software."
1679962,2017-04-07 16:14:29 UTC,"Hello
Attached dmesg file complete of today."
1679962,2017-04-07 09:52:26 UTC,"Yes, sorry:
You turn on the computer, you use it normal, and the tocuhpad works.
After 10 minutes or sometimes 1 hour, while touching the touchpad with your finger, the pointer jumps top of the screen and does not obey finger movements, until you remove your finger from the touchpad and wait for 1 second, then it works again.
The touchpad continues to work properly until after some time it does the same again.
Thank you!"
1679962,2017-04-07 09:22:09 UTC,"Hmm, can you explain the situation more explicitly?
Does the touchpad keeps working after the kernel message?
At what situation it doesn't work?
At waht situation it works?"
1679962,2017-04-07 09:03:48 UTC,Unfortunately the problem continues.
1679962,2017-04-06 18:48:14 UTC,"Hello,
Thanks Kai-Heng, with ""imps"" and ""bare"" the touchpad is crazy."
1679962,2017-04-06 15:34:55 UTC,"Please try 'psmouse.proto=bare', 'psmouse.proto=imps' or 'psmouse.proto=exps', without any other kernel parameters."
1679962,2017-04-06 10:24:31 UTC,"Hello Joseph,
I installed the kernel you told me.
The error has taken more time to reappear, but has appeared:"
1679962,2017-04-05 13:49:38 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1679962,2017-04-05 08:00:13 UTC,This change was made by a bot.
1679967,2017-04-05 10:40:53 UTC,"Hi Thomas,"
1679967,2017-04-05 09:39:29 UTC,"Hi Christian,"
1679968,2017-04-09 05:45:26 UTC,After some days of working under the old core and installing updates that followed thereon everything's returned to normal work.
1679970,2020-12-29 22:17:02 UTC,"Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1679993,2017-04-06 01:33:01 UTC,https://review.openstack.org/#/c/453494/
1679993,2020-06-23 17:23:58 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/453494"
1679997,2017-07-09 21:08:29 UTC,The following was a workaround for me:
1680008,2017-04-05 10:03:08 UTC,"not needed for zesty, but could fix for zesty+1"
1680008,2017-08-30 09:39:24 UTC,"This fix might not be needed due to the switch to GNOME in Ubuntu 17.10. Also, the patch provided is not in debdiff format. If this fix is relevant for Ubuntu 17.10, please attach a debdiff and resubscribe ~ubuntu-sponsors."
1680011,2017-04-05 10:37:56 UTC,Thanks for bringing this up!
1680011,2018-01-23 08:49:45 UTC,This is being discussed here: https://forum.snapcraft.io/t/snapd-support-for-xdg-desktop-portal/161
1680011,2019-10-01 22:33:41 UTC,"GTK and Qt snaps packaged with recent enough versions of the toolkit as well as running on recent-enough desktop stacks will now use portals automatically, Snapd exposes access to the document portal, and work on integration with other portals is in progress."
1680016,2017-04-10 05:36:50 UTC,Can you please provide any stack trace for the same?
1680019,2017-04-16 11:24:23 UTC,This bug only applies to Ubuntu up to trusty (14.04LTS). xenial (16.04LTS) and later releases use GnuTLS 3.x with nettle as crypto backend.
1680019,2017-05-23 17:49:20 UTC,Thank you for filing this bug report! I have subscribed the server team and put it on our backlog.
1680019,2020-04-22 18:56:36 UTC,"Standard support has ended for Trusty.  Extended security maintenance options are available, but as described this is a cosmetic issue rather than security, so closing out for now.  Upgrading would be recommended if you've not done so already."
1680025,2017-04-06 06:08:45 UTC,sla2 for 9.0-updates
1680025,2017-04-06 10:33:57 UTC,"Reviewed:  https://review.openstack.org/453555
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=c7cd3071235b59efb9d4cfaf4f70ada3886a444b
Submitter: Jenkins
Branch:    stable/mitaka"
1680025,2017-05-19 08:02:43 UTC,Verified on 9.2 mu2 updates.
1680039,2017-04-06 17:30:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680044,2017-04-05 12:03:26 UTC,This is caused by an upstream gdbus issue tracked here: https://bugzilla.gnome.org/show_bug.cgi?id=780924
1680044,2017-04-13 17:54:42 UTC,Fixed upstream.
1680062,2017-04-05 12:30:01 UTC,"Browser versions in the above tests are:
Safari Version 10.0.3 (12602.4.8)"
1680062,2017-04-05 15:48:19 UTC,This hits the exceptions in https://github.com/openstack/oslo.middleware/blob/master/oslo_middleware/cors.py#L382
1680062,2017-04-05 15:55:22 UTC,Yes adding allow_headers for Origin fixes it.
1680062,2018-04-25 20:26:05 UTC,It looks to me like this is set on a per-project basis.  oslo.middleware doesn't have any default headers: https://github.com/openstack/oslo.middleware/blob/2c557312519cd368c50eaaa5448049da19cc6281/oslo_middleware/cors.py#L50
1680069,2017-11-03 16:43:00 UTC,Syncing task from Mir.
1680072,2017-04-27 17:37:34 UTC,This bug was fixed in the package python-os-brick - 1.12.0-0ubuntu1
1680083,2017-07-07 11:41:25 UTC,"I'm confused what this bug is about, or what do we intend to fix here? Are we proposing that SLO should be automatically added to the pipeline like DLO is or something else?"
1680083,2017-06-14 22:11:59 UTC,N.B. swiftclient will no longer send the (essentially private sysmeta) x-static-large-object header https://review.openstack.org/#/c/455470/
1680083,2017-04-08 18:43:55 UTC,@Archana thank you for reporting this bug.
1680083,2017-04-08 10:30:17 UTC,DLO - MD5 of the manifest file
1680083,2017-04-08 10:28:37 UTC,Does etag computation for DLO and SLO differs ?
1680083,2017-04-06 16:05:39 UTC,I feel this as a minor bug. Swift configuration should add both the middlewares in pipeline by default
1680083,2017-04-06 09:19:10 UTC,"Archana - correct, I intended to refer to the parameters like ?multipart-manifest=put"
1680083,2017-04-06 09:03:11 UTC,For SLO no header is required is what I understand from the doc. X-Static-Large-Object is internal header.
1680083,2017-04-06 09:00:05 UTC,"Like what Clay says - I think it makes sense to send a warning when X-Static-Large-Object is used on PUT and there is no SLO in pipeline. Not sure of the implications of inserting it automatically from a certain version though. On the face of it, it seems not an issue."
1680083,2017-04-06 04:25:30 UTC,python-swiftclient 3.1.0
1680083,2017-04-06 08:32:42 UTC,Adding SLO to the pipeline worked.
1680083,2017-04-06 08:17:09 UTC,pipeline = healthcheck cache authtoken keystone proxy-server
1680083,2017-04-06 08:09:30 UTC,oh wow!  You can set X-Static-Large-Object on PUT even if SLO is not in the pipeline!?
1680083,2017-04-06 07:53:47 UTC,proxy-server.conf
1680083,2017-04-06 07:14:29 UTC,Is there any way to add SLO to pipeline ?
1680083,2017-04-06 06:48:42 UTC,this is fascinating - it's like the SLO middleware isn't in the pipeline:
1680083,2017-04-06 05:01:36 UTC,"# swift --debug download 1423Apr6 sample
DEBUG:keystoneclient.auth.identity.v2:Making authentication request to http://x.xx.xx.x:5000/v2.0/tokens
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): x.xx.x.xx
DEBUG:requests.packages.urllib3.connectionpool:""POST /v2.0/tokens HTTP/1.1"" 200 3898
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): x.xx.xx.xx
DEBUG:requests.packages.urllib3.connectionpool:""GET /v1/AUTH_f9d7c1cf6500469b80f0906f5f9b1791/1423Apr6/sample HTTP/1.1"" 200 311
DEBUG:swiftclient:REQ: curl -i http://x.xx.xx.xxx:8091/v1/AUTH_f9d7c1cf6500469b80f0906f5f9b1791/1423Apr6/sample -X GET -H ""X-Auth-Token: d48b7e179dc345a19c11b6294134b0f3""
DEBUG:swiftclient:RESP STATUS: 200 OK
DEBUG:swiftclient:RESP HEADERS: {u'Content-Length': u'311', u'X-Object-Meta-Mtime': u'1491452737.363976', u'Accept-Ranges': u'bytes', u'Last-Modified': u'Thu, 06 Apr 2017 04:27:34 GMT', u'Etag': u'e7e1f14de9e622549dd51b000eec09a3', u'X-Timestamp': u'1491452853.50530', u'X-Trans-Id': u'txf195f0fbbda1485ca03c9-0058e5cc1f', u'Date': u'Thu, 06 Apr 2017 05:03:27 GMT', u'X-Static-Large-Object': u'true', u'Content-Type': u'application/octet-stream'}
sample [auth 0.371s, headers 0.516s, total 0.516s, 0.002 MB/s]
# ls
sample
# ls -l sample
-rw-r--r-- 1 root root 311 Apr  6 00:25 sample"
1680083,2017-04-06 03:12:43 UTC,What version of both swift and python-swiftclient are you using?  What is the body returned if you download testt - is it still the 35MB you expected to get?  Can you reproduce this content-length error when using a curl GET or HEAD command to swift directly?
1680083,2017-04-06 08:55:07 UTC,"Archana, it is triggered by the headers you pass for slo.. In case you missed it, this reference link has description with examples of how dlo slo differ and how they work: https://docs.openstack.org/developer/swift/overview_large_objects.html"
1680088,2017-04-11 17:02:11 UTC,thanks guys
1680088,2017-04-10 14:06:34 UTC,"depends which one will be released, hard to tell a version number in advance.
it is now in the edge core snap and will be in the next stable release of the core snap."
1680088,2017-04-11 16:52:00 UTC,This is now in the beta core snap and should enter candidate this week.
1680088,2017-04-10 14:16:23 UTC,Another way to ask the question: is there a deb build manifest for core builds and if so where? For example I don't see one here: http://cdimage.ubuntu.com/ubuntu-core/16/candidate/pending/
1680088,2017-04-10 13:45:39 UTC,"Which core release will this be in? (I see ubuntu-core-meta 1.7.11 package in the ppa [1]), but I don't see how to know the version of core that will contain it.)"
1680088,2017-04-05 13:28:12 UTC,"we need to make sure the actual gawk is used in the core snap, the shipped mawk does not support --sandbox"
1680088,2017-04-05 14:52:22 UTC,"indeed, my comment was meant independent from the py3 move, people might expect awk on the OS to work like any other awk on any other ubuntu ... (specifically since it is one of the commands we give unrestricted access to for every snap)"
1680088,2017-04-06 14:42:10 UTC,ubuntu-core-meta (1.7.11) xenial; urgency=medium
1680088,2017-04-05 13:38:15 UTC,Alternatively we can go to python3: https://github.com/snapcore/core/pull/24 which also will fix this. Still confused why this happend :/
1680109,2017-07-07 18:56:36 UTC,"So, i've run into this same issue myself."
1680109,2018-09-07 11:41:08 UTC,"I have already done this in another project with variables generated from Jinja2. Basically, what we could do is:
- extract all of the variables inside the YAQL code
- generate a dependency graph using the variable names, it is possible to detect dependency loops at the same time. Raise an error if there's a loop (it could be possible to support loops, but I don't think it's good idea).
- compute the variables in the order of the dependency graph, recursively"
1680109,2018-09-07 11:48:52 UTC,nmaludy:
1680111,2017-07-11 10:44:53 UTC,"Jeremy, the fix for this is the cause of https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1681523
Can it please get another look at?"
1680115,2020-04-30 15:18:08 UTC,"Dear Paride,"
1680115,2020-04-30 14:23:19 UTC,"Hello Henri, thanks for taking the time to file a bug report. What you describe is certainly not happening in the latest versions of Ubuntu. Could you please specify which release of Ubuntu and which exact version of the mysql-server you are using?"
1680115,2020-04-03 22:02:15 UTC,There is no reference to this script in the mysql section of the server guide.  Presuming this bug was mis-filed maybe?
1680119,2017-04-05 15:21:12 UTC,This seems neat.
1680119,2017-04-05 15:38:00 UTC,"@allenap - agree that we should create a reciever and forward it to the region. But I wonder if placing all this into the database is the best idea. Maybe some other open-source software would be better at holding this data. But that also adds more pieces to MAAS which doesn't make it easy to setup, install, and manage."
1680119,2017-04-05 20:18:34 UTC,"I have long favoured more decentralisation of MAAS, and the distinction between region and rack as the way to achieve that, i.e. move more stuff to the racks, make them semi-autonomous. In that vein these logs could be held on the racks where they're received. The region would be a consumer of the racks' log archival service."
1680119,2018-02-16 00:11:49 UTC,If possible MAAS should also have netcosnoles available for deployed nodes to provide us with additional debugging information if those nodes experience problems during operation.
1680120,2017-04-05 14:44:42 UTC,"on unity7 when you click outside and the context menu closes, the hover state changes to normal"
1680124,2017-04-06 18:27:23 UTC,I can confirm that UA overrides are not being loaded in a virtualbox VM running zesty+unity8. However they are loaded in the same VM in unity7.
1680124,2017-04-06 17:27:17 UTC,"Just tested webbrowser-app natively on zesty in unity8, and overrides are being loaded correctly.
Having issues with virtualbox atm, but will try to confirm that the issue happens only in VMs."
1680130,2018-01-19 07:45:05 UTC,"i am getting ""error:No volume with a name or ID  exists "" in case of both wrong volume id or  ""--""(double hyphen) by using openstackclient"
1680130,2018-01-25 07:13:50 UTC,i am not able to  reproduce the error from the master branch now . please guide me to reproduce the same
1680130,2017-06-23 12:53:37 UTC,"There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments."
1680133,2017-04-06 02:34:32 UTC,Daniel.. don't bother https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/
1680133,2017-04-06 02:37:05 UTC,i'm really really sorry ;( unity8/mir was such a nice project
1680153,2017-04-05 16:11:36 UTC,Related bug: https://bugs.launchpad.net/ubuntu/+source/googletest/+bug/1644062
1680154,2017-04-05 16:19:42 UTC,When Photos fails to group the jpg and the raw files the embedded.jpg file is the one being displayed for the raw-file.
1680154,2017-04-05 16:35:05 UTC,"So I checked a bit in the code, the problem here is that Photos fails to group the raw + jpg and then extracts the embedded one to display the raw.
So the question is why does the grouping fail, should this be a separate bugreport?"
1680160,2017-11-20 18:06:18 UTC,This was discussed in the ironic meeting [1] and we agreed that this should be deprecated.
1680160,2017-04-11 16:54:35 UTC,I'm +2 to this being approved.
1680160,2017-11-13 22:21:06 UTC,"I'm good with approving this too. Since it is deprecating, I'll bring it up in our meeting if I remember..."
1680176,2017-04-06 14:18:38 UTC,"Reviewed: https://review.fuel-infra.org/32877
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680176,2017-04-06 14:18:51 UTC,"Reviewed: https://review.fuel-infra.org/32878
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680176,2017-04-06 14:18:53 UTC,"Reviewed: https://review.fuel-infra.org/32876
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680176,2017-04-06 14:18:27 UTC,"Reviewed: https://review.fuel-infra.org/32879
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680176,2017-04-06 14:18:58 UTC,"Reviewed: https://review.fuel-infra.org/32882
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680176,2017-04-11 13:16:03 UTC,"As was discussed with Dmitry Burmistrov and Roman Vyalov, tag appeared in the tree after the packages were published. So we need additional checks to overcome such issues."
1680176,2017-04-06 17:43:14 UTC,"Reviewed: https://review.fuel-infra.org/32881
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680176,2017-04-06 14:18:56 UTC,"Reviewed: https://review.fuel-infra.org/32880
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680176,2017-04-06 10:03:33 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/32883"
1680176,2017-04-06 15:04:14 UTC,"Reviewed: https://review.fuel-infra.org/32883
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680176,2017-04-06 10:01:14 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/32881"
1680176,2017-04-06 10:00:56 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32880"
1680176,2017-04-06 09:58:34 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Dmitry Teselkin <email address hidden>
Review: https://review.fuel-infra.org/32879"
1680176,2017-04-06 09:56:25 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32878"
1680176,2017-04-06 09:54:18 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32877"
1680176,2017-04-06 09:46:46 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32876"
1680176,2017-04-06 09:39:00 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32875"
1680176,2017-04-06 10:02:32 UTC,"Related fix proposed to branch: 10.0/newton
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/32882"
1680176,2017-04-06 08:25:20 UTC,"cinder has outdated spec - `Latest version from Gerrit tag: 9.1.3, and from changelog: 9.1.2.`"
1680176,2017-04-06 16:50:14 UTC,"Reviewed: https://review.fuel-infra.org/32875
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1680179,2017-04-06 19:00:15 UTC,"Also reproduced on Xubuntu 16.04, Inkscape 0.91 and lp:inkscape/0.92.x rev. 15413."
1680179,2017-04-20 16:33:37 UTC,fix committed to rev 15626
1680179,2017-04-05 20:40:47 UTC,"- confirmed on Windows 10, Inkscape 0.92+devel 15614
- the behavior of the round cap case is unexpected, should be the same as the square cap"
1680179,2017-04-05 22:29:13 UTC,"reproduced on Windows XP, Inkscape 0.91 r13725 (Jan 30 2015)"
1680181,2017-04-05 17:56:37 UTC,I just saw that the Google HTTP issue is already tracked here #1207489
1680182,2019-02-13 01:18:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680183,2019-05-22 09:11:53 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/660611"
1680183,2020-04-17 09:31:14 UTC,"Reviewed:  https://review.opendev.org/717804
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=478e20a61f7356739b7e01efb955c83bc512f428
Submitter: Zuul
Branch:    stable/train"
1680183,2020-04-06 17:00:25 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/717804"
1680183,2019-12-13 15:15:59 UTC,Hello:
1680183,2019-12-12 01:59:12 UTC,"Reviewed:  https://review.opendev.org/660722
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3437572906e38ec05caf141e634025941d887c50
Submitter: Zuul
Branch:    master"
1680183,2019-06-07 13:36:26 UTC,"Reviewed:  https://review.opendev.org/660611
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a477c31a23049407b010e2eadbc93d0a2ed42e9d
Submitter: Zuul
Branch:    master"
1680183,2019-06-06 14:48:31 UTC,"Reviewed:  https://review.opendev.org/661257
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6ea01444dd75d2d15658c808e052143deaf66543
Submitter: Zuul
Branch:    master"
1680183,2019-05-24 11:24:32 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/661257"
1680183,2019-05-22 14:08:41 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/660722"
1680183,2017-11-08 19:13:51 UTC,"Was this ""Fix"" ever merged for production release?  I""m running Openstack-Ansible Pike (16.0.1) and I'm still getting this error.  Based on your number / release cycle, this error has probably been floating around for 2 years.  Embarrassing."
1680183,2017-04-27 21:17:47 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/460751"
1680183,2017-07-31 16:57:43 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/460751
Reason: Not of help for the issue in question."
1680183,2017-04-05 17:59:39 UTC,"Actually, this comes from functional tests."
1680183,2017-10-17 12:19:22 UTC,"The issue is not only testing, also hit by customers."
1680183,2017-04-05 19:10:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453838"
1680183,2017-04-05 20:23:23 UTC,"Probably doesn't affect data plane, just an ugly log message (that is not seen without syslog logging enabled)."
1680183,2017-04-06 09:53:36 UTC,"We had issues with syslog in the past where they didn't play nice with multiple workers (API, RPC) due to opening a socket too early - before fork. Just leaving this here if it could be related."
1680183,2017-04-05 18:13:09 UTC,"No, it happens in fullstack too. I suspect it's more than just tests."
1680183,2017-04-13 02:07:23 UTC,"Reviewed:  https://review.openstack.org/453838
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=757476983ca0832099f04b9f029617ab270de9fe
Submitter: Jenkins
Branch:    master"
1680183,2017-04-28 20:46:26 UTC,"We still hit the issue, though the trace is a bit different now:"
1680183,2017-06-09 21:35:45 UTC,This issue was fixed in the openstack/neutron 11.0.0.0b2 development milestone.
1680183,2017-04-06 09:56:54 UTC,"I addressed it at some point here [0] but later in this patch I removed it because I couldn't reproduce it anymore. Your solution of calling time.sleep instead is better and I didn't realize, thanks for handling this Ihar :)"
1680197,2017-04-06 15:18:16 UTC,Something I'm looking further into is:
1680197,2020-01-13 20:59:23 UTC,"Going to close this as fix released for now on the assumption that A: the SRU smoser mentioned did fix this, and the fact that B: we really haven't seen this occur on releases after Zesty (All the way up to Eoan and Focal)."
1680197,2017-12-08 18:39:14 UTC,Long story short: I believe that SRU of bug 1723183 will fix this.
1680197,2017-05-11 15:01:22 UTC,"Strike that comment.
The bug number i think is 1666573."
1680197,2017-05-11 15:00:25 UTC,"I think this is related to bug 1689557, which i think root cause is systemd and overlayroot."
1680197,2017-05-11 14:56:06 UTC,I can confirm this happens to me. The storage config looks like:
1680197,2017-04-10 14:55:02 UTC,"OK,"
1680197,2017-04-06 14:30:37 UTC,"FWIW, I've discovered that some nodes seem to be more susceptible than others to this bug. I've encountered it on at least four nodes, but some fail only once every several deployments, whereas others succeed in deploying only once every several tries (or maybe never). The worst seems to be an HP ProBook 6470b, which is an AMT-enabled laptop on my home network. (That's the system whose logs I've provided.) The next worse seems to be either a new Dell PowerEdge C6320p or an older Dell PowerEdge T610, both IPMI-enabled servers in 1SS. I've also encountered it, but with much less frequency, on an AMT-enabled Intel NUC on my home network. Of possible relevance: The NUC uses an SSD, whereas the other systems all have conventional spinning hard disks."
1680197,2017-04-05 19:07:55 UTC,Curtin version information:
1680197,2017-04-06 02:08:03 UTC,"Rod,"
1680197,2017-04-05 18:32:34 UTC,This seems like a curtin bug (and may even be an issue with zesty itself).
1680197,2017-04-05 18:37:44 UTC,"Hi Rod,"
1680197,2017-04-05 18:54:04 UTC,"The lack of exclusive access on open suggests that the device has been claimed by some other block service (Like md or lvm, or bcache)."
1680197,2017-04-06 13:32:55 UTC,Here's the entire /var/log directory tree from the ephemeral on a failed deployment.
1680197,2017-04-05 20:06:24 UTC,"Can you provide me with pointers on how to get the information you want? I know there used to be some hackish way to gain access to MAAS ephemerals, but that was several versions ago and I don't know what the current method is."
1680197,2017-04-05 20:30:07 UTC,"On Wed, Apr 5, 2017 at 3:06 PM, Rod Smith <email address hidden> wrote:"
1680197,2017-04-05 19:30:33 UTC,"Device mounts: ['/dev/sda1 /media/root-ro ext4 ro,relatime,data=ordered 0
0']"
1680211,2017-04-05 19:20:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453840"
1680211,2017-04-05 21:54:09 UTC,"Reviewed:  https://review.openstack.org/453840
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5a9cc2fb7af3e3a9db44646bbd23cfcfb16891f5
Submitter: Jenkins
Branch:    master"
1680211,2017-04-06 01:10:32 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/453939"
1680211,2017-04-10 13:29:54 UTC,"Reviewed:  https://review.openstack.org/453939
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eaa38bc973d65f897078157e2008653ef47e3d47
Submitter: Jenkins
Branch:    stable/ocata"
1680211,2017-04-12 18:55:09 UTC,This issue was fixed in the openstack/nova 15.0.3 release.
1680211,2017-04-14 09:22:17 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1680224,2020-06-01 20:25:20 UTC,"Ah, and I added an ubuntu user:  sudo smbpasswd -a ubuntu"
1680224,2020-06-01 21:09:28 UTC,"Upstream just removed the \$$ gsub() handling in auto.smb:
commit a557e6261afc87d3849b557257185ff72be15a82 (HEAD -> upstream-master, upstream/master)
Author: Ian Kent <email address hidden>
Date:   Sun May 31 08:47:29 2020 +0800"
1680224,2020-06-03 13:47:41 UTC,Here is a script for the test case:
1680224,2020-06-03 14:36:36 UTC,"The ""C$"" case is working with the patch, but ""&"" is still problematic. I tried with groovy, which has autofs 5.1.6, and a share defined like the below doesn't get mounted:"
1680224,2020-06-03 17:06:53 UTC,"Here is the new test script, with a case for ""&"":
#!/bin/bash"
1680224,2020-06-24 02:45:23 UTC,I have uploaded fixes for:
1680224,2020-06-24 04:23:40 UTC,This bug was fixed in the package autofs - 5.1.6-2ubuntu1
1680224,2020-06-30 18:07:37 UTC,"Hello Mark, or anyone else affected,"
1680224,2020-06-30 18:02:11 UTC,"Hello Mark, or anyone else affected,"
1680224,2020-06-30 18:03:54 UTC,"Hello Mark, or anyone else affected,"
1680224,2020-06-01 20:25:06 UTC,"To simplify testing next time, these are the configs I used:"
1680224,2020-07-02 23:25:28 UTC,VERIFICATION
1680224,2020-07-07 21:27:49 UTC,This bug was fixed in the package autofs - 5.1.6-2ubuntu0.1
1680224,2020-07-07 21:27:55 UTC,"The verification of the Stable Release Update for autofs has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1680224,2020-07-07 21:29:02 UTC,This bug was fixed in the package autofs - 5.1.5-1ubuntu2
1680224,2020-07-07 21:29:33 UTC,This bug was fixed in the package autofs - 5.1.2-1ubuntu3.2
1680224,2020-06-30 18:02:06 UTC,Talking to @bdmurray there was a concern about SRU'ing the:
1680224,2020-06-01 20:22:56 UTC,"I commented in the MP, but let me add something here too."
1680224,2020-06-03 17:07:10 UTC,Let's also attach it
1680224,2019-10-17 17:30:09 UTC,"I've retested this with autofs 5.1.5 (eoan), and @ahasenack's suggested change to auto.smb is definitely required. With the $ escaped, mount fails as it's given a literal \$ in the path."
1680224,2020-04-15 22:27:23 UTC,"Based on case history, to fully address this to all still supported Ubuntu releases:"
1680224,2017-04-07 18:23:43 UTC,"Experimenting with this a bit, shares with spaces in their names work fine, but anything with $ or & fails. Ampersands are particularly troublesome, crashing the automounter if not escaped properly."
1680224,2017-04-10 20:10:59 UTC,"@mark-fox, thanks for filing this report!"
1680224,2017-04-10 20:37:21 UTC,"Thanks Josh. I actually tried using ASCII codes for the characters the day I filed the report. No dice. I've managed to make contact with Ian, an (the?) autofs maintainer. He thinks he's narrowed the problem down to a particular commit. If we make any progress, I'll share it here."
1680224,2017-04-10 21:16:00 UTC,Hi Mark! Thanks for following up and even reaching out to the maintainer. Please do share what you find. I'm going to mark this triaged for now.
1680224,2017-04-12 15:35:59 UTC,"Ian produced a patch that addresses the problem, at least as far as I've tested it. Whether the target is properly escaped or quoted, it works as expected."
1680224,2017-04-12 15:36:44 UTC,And the second part of the patch.
1680224,2017-04-12 16:24:58 UTC,"The attachment ""Patch 0 of 1"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1680224,2017-04-14 01:52:35 UTC,"The two autofs patches Mark has attached aren't yet available on kernel.org
but I will (eventually) commit them to the autofs repo. and upload them.
The change will be included in autofs-5.1.3."
1680224,2020-06-03 14:54:58 UTC,Same fix works for bionic's autofs 5.1.2.
1680224,2017-04-24 00:41:29 UTC,"In reviewing the first patch I've found another problem with
mapent_len possibly not being initialized."
1680224,2018-06-04 23:40:01 UTC,I believe these are the upstream patches:
1680224,2018-06-04 23:41:15 UTC,"And https://mirrors.edge.kernel.org/pub/linux/daemons/autofs/v5/patches-5.1.3/autofs-5.1.2-fix-offset-mount-location-multiple-expansion.patch, mentioned in comment #10 too"
1680224,2018-06-05 19:02:48 UTC,"ok, the worker-thread patch I think was just a case of an incorrect patch description in lp."
1680224,2017-04-24 00:35:48 UTC,"I have made a small change to the patch of comment #6.
I've added initialization of the malloc()ed pmapent variable.
While that wasn't a problem it can be on some architectures."
1680224,2018-06-06 15:14:36 UTC,"@mark-fox, were those two patches the only changes you needed, or was the change to the awk script (removing the quoting of $) also needed?"
1680224,2018-06-06 15:56:10 UTC,"I honestly don't know. The initial patches from April 12th of 2017 were all
I needed and I haven't messed with it since."
1680224,2018-06-06 17:20:13 UTC,"I can't get it to work without also removing the quoting in the awk script in /etc/auto.smb, i.e.:
@@ -76,7 +76,7 @@
     loc = $2
     # Enclose mount dir and location in quotes
     # Double quote ""$"" in location as it is special
-		  gsub(/\$$/, ""\\$"", loc);
+		  #gsub(/\$$/, ""\\$"", loc);
     gsub(/\&/,""\\\\&"",loc)
     print "" \\\n\t \""/"" dir ""\"""", ""\""://"" key ""/"" loc ""\"""""
1680224,2018-12-06 01:09:28 UTC,"I haven't revisited this yet due to lack of time. Whoever gets to this next should check the current version of autofs, and also the list of available patches for the version shipped in older ubuntu releases."
1680229,2018-08-21 15:02:33 UTC,"The dll.a files are used by the mingw linker when linking dynamic libraries.  I don't think we need to package them since we are not installing the headers for users to compile and link against these libraries.  If we did, the correct install path would be lib/ not bin/.  Would our windows package developer please remove them from the installer?"
1680229,2018-07-27 11:17:13 UTC,Is this still an issue?
1680229,2018-08-02 14:57:21 UTC,"Well, from the build log on windows the dll.a seems to be installed to bin together with the .dll, but so is the dll.a for libeeschema. I don't really think this is a error as such."
1680239,2017-09-18 22:56:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680243,2017-04-05 21:36:08 UTC,There doesn't seem to be any curtin error here;  grub was installed (and upgraded) but the disk failed to boot.
1680243,2017-04-06 00:50:09 UTC,"@Ryan, it does have a single physical disk. That disk as a RAID0 on it and it's the virtual disk that's presented to the OS."
1680243,2017-04-06 00:51:18 UTC,That disk has* a RAID0.
1680243,2017-04-06 03:10:30 UTC,"Has it ever booted before?  Can you deploy trusty instead to see if there's
an issue with the grub currently installed in Xenial?"
1680245,2019-07-12 03:55:49 UTC,"So the status of this is that it is landed in subiquity master and is being included in the eoan images (but not yet the bionic ones). If you are one of the people waiting for this feature, please grab yourself an ISO from http://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/ and try it out (on systems with backed up data only at this stage please!)."
1680245,2019-05-23 15:35:50 UTC,This work is currently in progress.
1680245,2019-05-17 20:48:20 UTC,"Hi Michael,"
1680245,2019-01-08 20:27:22 UTC,It's on the roadmap for 19.04. I'll make sure to update this bug when there is stuff to test via snap refresh!
1680245,2019-01-06 11:48:32 UTC,This does seem like a significant shortcoming in the current 18.04 install experience. Let's fix it in 19.04 and it will be available for 18.04 existing install media with a straightforward snap refresh.
1680245,2018-12-17 01:08:30 UTC,Why it's not fixed yet?
1680245,2018-08-10 01:52:08 UTC,"You can use the 18.04(.1) alternate server installer if you run into this situation. Also, I think this situation has improved in the 18.04.1 'server-live' (subiquity) installer."
1680245,2018-05-25 23:12:28 UTC,"Seems the ""workaround"" is to install normal desktop ubuntu instead of ubuntu server, as that's the only installer that actually works correctly."
1680245,2018-05-25 23:03:18 UTC,Confirmed; just ran in to this brick wall while trying to install on top of a bcache.  This is a fundamental installer feature that is completely missing.
1680245,2018-04-19 19:02:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680245,2018-04-15 06:37:36 UTC,This is a showstopper bug for anyone who has existing data partitions. I'm unable to install ubuntu server without destroying my data.
1680245,2018-11-13 15:17:58 UTC,I was wrong. the 18.04.1 server-live installer (as well as daily ISOs until today) have not improved upon this (tested on an UEFI booted system only). The alternative (debian-installer based) server installer works fine.
1680245,2017-05-03 15:06:48 UTC,We should display existing partitions. I think this should be a high priority item.
1680248,2017-08-18 03:09:05 UTC,I have seen this bug since mid 2014 and it still is not fixed. I can workaround it by re plugging the wireless USB adaptor but it is annoying. Mine is a Belkin N300. lsusb command shows: Bus 001 Device 004: ID 050d:845a Belkin Components F7D2101 802.11n Surf & Share Wireless Adapter v1000 [Realtek RTL8192SU]
1680266,2019-09-19 11:56:21 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1680266,2017-04-06 23:23:36 UTC,I think this should be targeted for a later MAAS release. To do this correctly and consistently would mean re-examining the entire MAAS API.
1680267,2018-01-25 08:44:47 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3681
1680267,2017-04-05 22:24:42 UTC,OS is Linux - Kernel version 2.6 and mysql version is
1680276,2017-04-05 23:30:10 UTC,This change was made by a bot.
1680276,2017-04-06 08:52:37 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1680276,2017-04-06 12:54:38 UTC,"Also, is this a regression?  Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?"
1680276,2017-04-07 09:29:42 UTC,"This and a handful of other DRM drivers got disabled because they present insecure APIs to userspace. The recommendation provided from upstream developers is ""to use the safe modeset-only drivers instead, and perform 3D emulation in user-space."" If that isn't practical for some reason we might be able to re-enable the drivers. However we probably need at minimum to exclude these from module signing, and perhaps even blacklist those modules by default."
1680276,2017-04-07 18:08:44 UTC,@sforshee:  Is this something new to Zesty or was it done in previous releases?  It's been years since I've tried a Via Chrome system so it's new to me at least.
1680276,2017-04-07 20:16:50 UTC,@jsalisbury: The via DRM is still missing with 4.11-rc5.
1680276,2017-04-10 13:13:48 UTC,The changes to disable the modules happened in zesty. These are the ones that are no longer enabled:
1680276,2017-04-11 21:25:24 UTC,@sforshee Something should be in release notes and/or a text box in the installer.
1680279,2017-07-19 18:44:48 UTC,Verification done for trusty: I've used shim-signed 1.32~14.04.2 and verified that the update apport hook is included and working as expected.
1680279,2017-07-20 19:07:13 UTC,Verification-done for xenial; using shim-signed 1.32~16.04.1:
1680279,2017-07-24 17:19:22 UTC,Verification-done for xenial; using shim-signed 1.32~17.04.1:
1680279,2017-08-28 15:29:46 UTC,This bug was fixed in the package shim-signed - 1.32~14.04.2
1680279,2017-07-28 00:47:07 UTC,This bug was fixed in the package shim-signed - 1.32~17.04.1
1680279,2017-07-18 04:56:13 UTC,"Hello Steve, or anyone else affected,"
1680279,2017-07-28 00:46:31 UTC,This bug was fixed in the package shim-signed - 1.32~16.04.1
1680279,2017-07-17 14:51:49 UTC,"Hello Steve, or anyone else affected,"
1680279,2017-07-28 00:46:42 UTC,"The verification of the Stable Release Update for shim-signed has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1680279,2017-07-13 21:02:57 UTC,"Hello Steve, or anyone else affected,"
1680279,2017-04-25 10:11:42 UTC,"Hello Steve, or anyone else affected,"
1680279,2017-04-25 10:14:16 UTC,"Hello Steve, or anyone else affected,"
1680279,2017-05-05 18:25:03 UTC,Verified shim-signed 1.28~16.04.1 in xenial.
1680279,2017-07-13 21:14:16 UTC,"An upload of shim-signed to trusty-proposed has been rejected from the upload queue for the following reason: ""needs adjusted versioned dep on grub2-common; drop ref to LP: #1624096 from changelog""."
1680279,2017-05-25 18:24:01 UTC,This bug was fixed in the package shim-signed - 1.28~16.04.1
1680279,2017-06-27 15:25:20 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1680279,2017-07-13 20:54:11 UTC,"Hello Steve, or anyone else affected,"
1680279,2017-05-15 15:38:40 UTC,I changed my mind; this is a verification-done: just knowing whether the files are there even if they're not mapping to proper data is already a plus.
1680281,2017-04-06 00:14:52 UTC,Marking as confirmed because this has been an issue for well over a year across multiple installs of gnome-do on multiple computers.
1680281,2017-04-06 02:43:46 UTC,These might be related and have fixes:
1680300,2018-01-16 16:19:52 UTC,typing on search bar freezes AppCenter.
1680302,2019-08-03 18:40:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680302,2020-07-03 05:05:34 UTC,DistroRelease: Kali 2017.1
1680307,2017-07-27 20:49:14 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.
1680307,2017-07-18 01:43:50 UTC,"Reviewed:  https://review.openstack.org/453966
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=63314ad6dd181a0e975438de2e99409238f1b775
Submitter: Jenkins
Branch:    master"
1680307,2017-04-06 03:37:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/453966"
1680311,2017-05-15 09:04:04 UTC,I've got this issue as well. Running M-Release and NSX 6.3.1.5124716
1680316,2017-04-06 09:04:49 UTC,Why do you consider the CPU usage to be abnormal?
1680316,2017-04-06 17:54:06 UTC,"Hi Nikolov,"
1680316,2017-04-06 22:59:31 UTC,"Hi,"
1680316,2017-04-07 00:23:11 UTC,"Hi Deepak,"
1680316,2017-04-10 09:16:38 UTC,"Thanks guys for response, will be working on below suggestion to mitigate
the issue along with version upgrade:"
1680321,2017-04-06 08:32:22 UTC,"The attachment ""trivial.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1680326,2017-04-06 05:48:33 UTC,"And I found: vmops.build_virtual_machine() --> vm_util.create_vm() failed
The error is: oslo_vmware.exceptions [-] Fault InvalidDeviceSpec not matched.
So I dump the config_spec:"
1680326,2017-04-06 05:48:51 UTC,So anybody can tell me what's wrong with the config spec? Thanks a lot
1680331,2020-02-20 10:57:50 UTC,"I appreciate where this is coming from, but this is an issue with argparse that we're not going to be able to easily fix, unfortunately. I'm marking this as wontfix just to avoid giving false promises."
1680333,2017-04-06 11:33:10 UTC,"Thanks, @Mc for that info.
Maybe another example which might help to identify the detailed origin:"
1680333,2017-04-06 06:41:49 UTC,see https://www.w3.org/TR/SVG/types.html#Precision
1680350,2017-04-15 16:59:34 UTC,"Hello Avner,"
1680355,2017-04-17 09:38:23 UTC,"This annoying bug presents from Luna. It came from .Xauthority file, that change it's owner to root."
1680360,2017-04-18 15:43:10 UTC,I have also seen this.
1680360,2017-10-26 07:42:53 UTC,"A new version of `nvidia-375` and a bunch of unrequired packages after `apt upgrade`:
```
The following NEW packages will be installed:
  apg aptdaemon avahi-daemon avahi-utils bbswitch-dkms bluez bluez-obexd cheese-common cracklib-runtime cups-pk-helper dconf-cli diffstat evolution-data-server evolution-data-server-common evolution-data-server-online-accounts geoclue
  geoclue-ubuntu-geoip gettext gir1.2-gnomekeyring-1.0 gir1.2-ibus-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gkbd-capplet gnome-bluetooth gnome-desktop3-data gnome-screensaver gnome-session-bin gnome-settings-daemon-schemas
  gnome-user-share gsettings-ubuntu-schemas gstreamer1.0-clutter-3.0 gstreamer1.0-plugins-good gstreamer1.0-x hardening-includes hwdata ibus im-config indicator-applet indicator-application indicator-bluetooth indicator-datetime
  indicator-keyboard indicator-messages indicator-power indicator-session indicator-sound intltool-debian ippusbxd libaccount-plugin-1.0-0 libaccount-plugin-generic-oauth libaccount-plugin-google libaccounts-glib0 libaccounts-qt5-1
  libapt-pkg-perl libarchive-zip-perl libasprintf-dev libauthen-sasl-perl libavahi-core7 libcamel-1.2-54 libcanberra-pulse libcgmanager0 libcheese-gtk25 libcheese8 libclass-accessor-perl libclone-perl libclutter-gst-3.0-0 libcrack2
  libcuda1-384 libdaemon0 libdata-alias-perl libdigest-hmac-perl libdouble-conversion1v5 libdv4 libebackend-1.2-10 libebook-1.2-16 libebook-contacts-1.2-2 libecal-1.2-19 libedata-book-1.2-25 libedata-cal-1.2-28 libedataserver-1.2-21
  libemail-valid-perl libexporter-tiny-perl libfcitx-config4 libfcitx-gclient0 libfcitx-utils0 libgee-0.8-2 libgeocode-glib0 libgeonames0 libgettextpo-dev libgettextpo0 libglib2.0-bin libgnome-bluetooth13 libgnome-desktop-3-12
  libgnomekbd-common libgnomekbd8 libgstreamer-plugins-good1.0-0 libgweather-3-6 libgweather-common libibus-1.0-5 libical1a libido3-0.1-0 libio-pty-perl libio-socket-inet6-perl libio-string-perl libipc-run-perl liblightdm-gobject-1-0
  liblist-moreutils-perl libmailtools-perl libnautilus-extension1a libnet-dns-perl libnet-domain-tld-perl libnet-ip-perl libnet-smtp-ssl-perl libnih-dbus1 libnm-glib4 libnm-gtk-common libnm-gtk0 libnm-util2 libnss-mdns
  libpackagekit-glib2-16 libpanel-applet0 libparse-debianchangelog-perl libperlio-gzip-perl libpwquality-common libpwquality1 libqt5opengl5 libqt5qml5 libqt5quick5 libqt5sql5 libqt5sql5-sqlite libqt5webkit5 libsignon-extension1
  libsignon-glib1 libsignon-plugins-common1 libsignon-qt5-1 libsocket6-perl libsub-name-perl libtext-levenshtein-perl libtimezonemap-data libtimezonemap1 libunistring0 libunity-control-center1 libunity-settings-daemon1 liburl-dispatcher1
  libv4l-0 libv4lconvert0 libxklavier16 libyaml-libyaml-perl lightdm lintian mountall mousetweaks nautilus-data nvidia-384 nvidia-opencl-icd-384 nvidia-prime ocl-icd-libopencl1 patchutils python-asn1crypto python-certifi
  python3-aptdaemon python3-aptdaemon.pkcompat python3-bs4 python3-cairo python3-certifi python3-cups python3-cupshelpers python3-defer python3-html5lib python3-idna python3-lxml python3-xdg session-migration signon-keyring-extension
  signon-plugin-oauth2 signon-plugin-password signon-ui signon-ui-servic..."
1680364,2017-04-07 22:02:36 UTC,The problem seems resolved after i manually installed Python 3 `six` package with
1680364,2017-04-08 09:00:09 UTC,I recall now that i had had some problem with some Python package before and i did
1680364,2018-03-15 10:41:32 UTC,Slightly different way of going about the same thing as comment #2:
1680377,2017-09-11 07:16:06 UTC,As this can be done using the below set of commands:
1680377,2017-09-11 15:47:50 UTC,"yes, I think the bug is specifically for adding the method to the inernal client module - for parity with other methods like delete_container [1] and delete_object [2]"
1680377,2019-11-08 02:05:49 UTC,"Reviewed:  https://review.opendev.org/693305
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=7f6b09dc930706d63a943dc239dff84ddae52014
Submitter: Zuul
Branch:    master"
1680377,2020-02-03 11:00:12 UTC,This issue was fixed in the openstack/swift 2.24.0 release.
1680377,2020-03-18 11:57:34 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/713632"
1680377,2020-03-18 16:18:33 UTC,"Reviewed:  https://review.opendev.org/713632
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=79bd2e59e5c15ee84814ec1c4f0893176ba79412
Submitter: Zuul
Branch:    feature/losf"
1680378,2017-04-06 09:36:06 UTC,https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=0254dc74125999f9375bbe63e2b5295eceaae2b5
1680378,2017-11-03 16:43:03 UTC,Syncing task from Mir.
1680384,2017-12-07 08:18:30 UTC,"Hi Martin,
my particular fix on proc/*/cmdline (the one you hit atm) I didn't upstream yet [1] for the potential security risk (I wanted to wait for an idea how to do it even better, but had no better idea in my discussions with smb yet).
But it was just recently discussed as someone else was not so shy and brought it up [2]."
1680384,2017-12-06 22:10:57 UTC,"Christian: This bug now hit debian-testing (see http://209.132.184.41/logs/pull-8219-20171206-214646-d2e9e141-verify-debian-testing/log.html#2). Is there an upstream bug/patch mail for reference, or are these Debian/Ubuntu downstream rules?"
1680384,2017-05-24 01:42:33 UTC,This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.10
1680384,2017-05-22 16:08:49 UTC,FYI - Xenial was re-rolled so it waits a few days longer to be the right time in -proposed without reports. The SRU Team will likely pick it up in a few days.
1680384,2017-05-22 15:12:08 UTC,This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.1
1680384,2017-05-22 15:02:40 UTC,This bug was fixed in the package libvirt - 2.1.0-1ubuntu9.5
1680384,2017-05-22 15:02:09 UTC,"The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1680384,2017-05-16 12:32:10 UTC,With so much back and forth going on I double checked that this is against the right package from proposed.
1680384,2017-05-16 11:41:46 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1680384,2017-05-16 11:30:39 UTC,"Ok, with the fixup for Xenial (https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2769/+packages) it is also good there now.
Now contacting the release Team to help me replace that in proposed and do a final test from there."
1680384,2017-05-16 10:59:30 UTC,"Verification is ok for Yakkety and Zesty.
On Xenial there is an issue (nothing that breaks, but it doesn't fix it due to the apparmor packaging structure there being different)."
1680384,2017-05-11 19:02:32 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1680384,2017-05-11 19:00:44 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1680384,2017-05-11 19:03:28 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1680384,2017-04-06 14:00:05 UTC,"Prepared a Test PPA at
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2708/"
1680384,2017-04-06 14:19:24 UTC,"There is a section the ppc changes should go to:
# kvm.powerpc executes this
[...]"
1680384,2017-04-06 14:22:59 UTC,"The shutdown and vfio changes are actually already good, but the ppc kvm wrapper needs more.
Not only rearrange as outlined above, but also ppc64_cpu accesses more down the road, so we need to add this and check for more:"
1680384,2017-04-06 14:01:24 UTC,"Final Freeze today and this is not blocking install, so assume to reroll for AA once open and then SRU back.
But Tests on the PPA are fine for now."
1680384,2017-04-19 12:19:35 UTC,Somewhat refurbished way to solve this in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2724
1680384,2017-04-26 15:42:24 UTC,This bug was fixed in the package libvirt - 2.5.0-3ubuntu6
1680384,2017-05-09 10:12:06 UTC,"- Added and filled associated SRU Template
- checked once more the dep8 tests on the test bileto ppa
- checked regression tests
- added tasks for affected releases"
1680384,2017-04-20 06:12:26 UTC,Updated the ppa with an extended fix to cover follow on access of ppc64_cpu in the apparmor profile as well now.
1680384,2017-04-14 04:59:24 UTC,"------- Comment From <email address hidden> 2017-04-13 21:08 EDT-------
Please, reverse mirror LP1680384 (libvirt-qemu apparmor profiles misses several important entries)."
1680386,2017-04-14 05:29:19 UTC,"------- Comment From <email address hidden> 2017-04-13 21:09 EDT-------
Please, reverse mirror LP1680386 (virt-aa-helper to learn about VF devspec paths)."
1680386,2017-09-15 05:20:51 UTC,"------- Comment From <email address hidden> 2017-09-15 01:12 EDT-------
When passing through a pci-device, seeing these messages in guest, though pass-through is successful."
1680386,2017-09-15 06:11:11 UTC,"Hi,
in this cae guest message are not important.
Also I already said that it is non fatal - so yes it works, still it is wrong."
1680386,2017-10-30 04:19:23 UTC,"------- Comment From <email address hidden> 2017-10-30 00:15 EDT-------
I moved out of Ubuntu 17.10 squad and assigning this to Rodrigo after discussion with him.
Rodrigo please re-assign it to the appropriate person if you can't work on it."
1680386,2017-11-07 14:24:27 UTC,"thanks, will you also look at the related changes to virt-aa-helper in lbivirt once accepted?
In any way ping me once it got into qemu."
1680386,2017-11-08 08:49:29 UTC,"------- Comment From <email address hidden> 2017-11-08 03:43 EDT-------
(In reply to comment #12)

> thanks, will you also look at the related changes to virt-aa-helper in
> lbivirt once accepted?
> In any way ping me once it got into qemu.
"
1680386,2017-11-13 07:00:02 UTC,"------- Comment From <email address hidden> 2017-11-13 01:53 EDT-------
(In reply to comment #13)

> (In reply to comment #12)
> > thanks, will you also look at the related changes to virt-aa-helper in
> > lbivirt once accepted?
> > In any way ping me once it got into qemu.
>
> I will check with libvirt team about related changes in virt-aa-helper.
> .
> The patch of adding extra '/' in /proc/device-tree%s/ibm,loc-code will not
> work for the following reason.
> .
> The machine will have leading '/' in devspec as follows.
>
> garrison2:~$ cat /sys/bus/pci/devices/0009:03:00.0/devspec && echo -e '\n'
> /pciex@3fffe40500000/pci@0/pci@0/pci@1/usb-xhci@0
>
> So we will no more need this patch.
"
1680386,2018-06-27 13:16:16 UTC,"There are two ways to allow qemu to access something.
1. globally through the abstraction in /etc7apparmor.d/abstractions/libvirt-qemu
   That is for paths ALL qemu/geusts are supposed to use like /dev/kvm
2. per guest files generated based on the XML description in /etc/apparmor.d/libvirt/libvirt-<uuid>.files
   If you need paths like /sys/bus/pci/devices/0009:03:00.0/devspec to be accessible you should consider if you can derive the path from the XML and then let virt-aa-helper write a rule for it so that the guest can do so."
1680386,2019-01-21 15:49:44 UTC,"------- Comment From <email address hidden> 2019-01-21 10:45 EDT-------
(In reply to comment #21)

> There are two ways to allow qemu to access something.
> 1. globally through the abstraction in
> /etc7apparmor.d/abstractions/libvirt-qemu
> That is for paths ALL qemu/geusts are supposed to use like /dev/kvm
> 2. per guest files generated based on the XML description in
> /etc/apparmor.d/libvirt/libvirt-<uuid>.files
> If you need paths like /sys/bus/pci/devices/0009:03:00.0/devspec to be
> accessible you should consider if you can derive the path from the XML and
> then let virt-aa-helper write a rule for it so that the guest can do so.
>
> Finally later in the guest lifecycle further rules will be added via the
> labeling calls in the security code. E.g. if you add a device libvirt calls
> a set label function and this will add the new ruls (like for hotplug).
> For the latter see virAppArmorSecurityDriver in
> src/security/security_apparmor.c
"
1680386,2019-04-29 21:39:59 UTC,"------- Comment From <email address hidden> 2019-04-29 17:34 EDT-------
Both 17.04 and 17.10 reached EOL a while ago. Closing..."
1680386,2017-11-07 13:59:59 UTC,"------- Comment From <email address hidden> 2017-11-07 08:52 EDT-------
(In reply to comment #7)

> Hi,
> in this cae guest message are not important.
> Also I already said that it is non fatal - so yes it works, still it is
> wrong.
>
> Either fix or remove the code whatever is more appropriate.
> Please check the code that I referred to in qemu.
>
> hw/ppc/spapr_pci.c:775
> 774     /* Construct and read from host device tree the loc-code */
> 775     path = g_strdup_printf(""/proc/device-tree%s/ibm,loc-code"", buf);
> 776     g_free(buf);
>
> I'm rather convinced there should be an extra ""/"" in there.
"
1680388,2017-04-06 10:09:25 UTC,"If it helps, here is what alsa-info-script shows: http://www.alsa-project.org/db/?f=1cd134d088cfd005462ef4147330d3727b2d2387"
1680396,2017-04-07 02:09:03 UTC,"@tung doan,"
1680396,2017-04-07 01:57:18 UTC,"again, could you confirm the issue you met before?"
1680396,2017-04-07 01:04:39 UTC,"@tung doan,"
1680396,2017-04-06 12:36:05 UTC,Could you check it again? Heat stack need some time to realize that the minimum of VNFs is reached.
1680396,2017-04-07 01:56:07 UTC,"Hi Jeremy,"
1680398,2019-09-19 11:53:08 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1680398,2017-06-06 14:00:43 UTC,I believe this issue should not be set to Expired nor Incomplete.
1680398,2017-04-06 14:19:55 UTC,"One of our software engineers was looking for a way to integrate MAAS and our internal systems. He approached me when he stucked using Restful MAAS API with ""HTTP/1.0 401 UNAUTHORIZED""."
1680398,2017-04-06 12:57:40 UTC,"Hi Marius,"
1680398,2017-06-06 04:17:43 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1680407,2020-11-09 08:50:02 UTC,"4.10 EOL, closing this bug."
1680408,2017-04-29 00:35:09 UTC,Applies to Ocata too
1680408,2017-10-23 14:21:17 UTC,And pike
1680408,2019-10-06 08:42:45 UTC,This seems to be stale and old. Octavia is in current UCA OpenStack Stein release
1680412,2017-05-24 10:54:08 UTC,"I've got some time to further investigate the problem, and I created a patch fixing it too."
1680417,2017-04-06 11:53:37 UTC,I agree it would be good to try to create a DVR router at the test_dvr class level and skip the class tests if that failed. The skip check that looks at the tempest.conf dvr_enabled value is not sufficient.
1680417,2017-04-06 13:16:47 UTC,sounds like a great solution.
1680417,2017-04-06 13:39:24 UTC,"Actually the creation of router with distributed argument set to True succeeds even on non-DVR setup, so this solution will not work"
1680430,2017-04-11 11:44:31 UTC,I've investigated this issue and here's what I've found.
1680435,2017-08-07 09:36:43 UTC,Tested a CentOS based amp again (with current master branch):
1680435,2017-04-06 15:30:00 UTC,"If I got it correctly, this is how we end with python2:
* DIB setups dib-python element as a dependency on pip-and-virtualenv-source-install element
* this element installs/reinstalls pip and virtualenv with forced /usr/local/bin/dib-python
* new pip now is ""configured"" for /usr/local/bin/dib-python
* pip install in /opt/amphora creates the amphora-agent console_script entry point with this interpreter
* systemd unit just uses this script"
1680438,2017-05-03 17:57:35 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1680438,2017-05-03 19:10:40 UTC,"Okay, I think I've found the reason for the issue, and you're right; it is a duplicate.  Basically, the calculator is viewing the *new input* and the *last answer* as separate numbers.  Since no operator is specified, it is assumed to be multiplication between the two numbers.  On this bug, for instance, I type"
1680438,2017-07-26 12:26:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1680438,2017-08-19 12:49:38 UTC,Raise the same: https://bugzilla.gnome.org/show_bug.cgi?id=786510
1680438,2018-06-27 20:20:12 UTC,gnome has moved to gitlab.  Corresponding bug is now
1680442,2017-04-07 17:49:01 UTC,From log (translated as best as I could find):
1680442,2020-08-12 05:08:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680442,2017-04-07 17:55:16 UTC,"It appears that the file:
'/usr/share/gocode/src/github.com/juju/loggo/formatter_test.go'
Is provided by both 'golang-github-juju-loggo-dev' and
'golang-juju-loggo-dev' [1]."
1680445,2017-04-06 12:39:18 UTC,Fixed in r1005
1680445,2017-04-06 12:39:43 UTC,Free fixed it with this trivial against trunk: https://pastebin.canonical.com/185058/
1680446,2017-04-06 12:41:18 UTC,Yeah we just went through a change to be able to list existing role assignments and it was quite involved. I'll try to take a look at this soon.
1680446,2017-04-06 12:59:33 UTC,I have just also realized that some of the code already exists. In identity/v3/projects.py you can find methods like `Project.assign_role_to_user` which probably does the job but is not available in _proxy.py. I would maybe use/refactor these functions to implement what I wrote about above.
1680446,2017-07-06 08:36:06 UTC,"Hi, @Dave, I have met the same issue as you, and the Project.assign_role_to_user method need also a `session` parameter ,did you solve this by using this function or refactoring ?"
1680446,2017-07-06 10:44:33 UTC,@feyman I actually ended up using the keystone client instead for this example. In general my approach at the moment is mixing the client (which is only the case because I'm missing certain functionality from the openstacksdk).
1680446,2017-07-06 12:06:34 UTC,"@Dave , do you mean that you use the RESTful API for the missing functions? As far as I can see, it actually the only way if using python. Now maybe I should consider to use the java client openstack4j~"
1680446,2017-07-06 21:10:02 UTC,"No, I'm using the keystone client. It's deprecated, but still functional https://pypi.python.org/pypi/python-keystoneclient/3.6.0"
1680446,2017-07-07 02:37:10 UTC,"Thanks,@Dave ,I'm gonna give it a shot, :)"
1680448,2017-04-06 12:33:32 UTC,Adding a screenshot for the RAID configuration I used during the installation. First I created a RAID manually. Then I used the guided partitioning to set up an encrypted LVM.
1680448,2017-05-13 03:42:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680457,2017-05-04 13:34:19 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/462561"
1680457,2017-05-04 11:10:10 UTC,"Reviewed:  https://review.openstack.org/460305
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=510371d526bd45195be806fb153646abdc269b70
Submitter: Jenkins
Branch:    master"
1680457,2017-05-04 04:15:06 UTC,"Change abandoned by Abhishek Sharma M (<email address hidden>) on branch: master
Review: https://review.openstack.org/460293
Reason: Fixed as part of https://review.openstack.org/#/c/460305/"
1680457,2017-04-27 04:33:59 UTC,"Change abandoned by Abhishek Sharma M (<email address hidden>) on branch: master
Review: https://review.openstack.org/455118
Reason: I have added fresh changes (https://review.openstack.org/#/c/460305/1) to resolve https://bugs.launchpad.net/nova/+bug/1680457. SO I am abandoning this change set."
1680457,2017-04-11 10:03:52 UTC,"Please could we get the log you are seeing relating to this bit of the code:
https://github.com/openstack/nova/blob/3092d2adcb6bab0bf39b01ea0561ec7e6a3990fd/nova/compute/manager.py#L2111"
1680457,2017-04-26 20:01:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/460293"
1680457,2017-06-08 21:52:44 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1680457,2017-04-10 05:01:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/455118"
1680457,2017-05-16 12:09:27 UTC,"Reviewed:  https://review.openstack.org/462561
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f5a17d9ed312509e51fea154a17c4c5fe118c66b
Submitter: Jenkins
Branch:    stable/ocata"
1680457,2017-04-26 20:41:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/460305"
1680457,2017-05-30 15:54:34 UTC,This issue was fixed in the openstack/nova 15.0.5 release.
1680460,2018-01-25 08:42:31 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3682
1680464,2017-04-06 13:41:34 UTC,Uninstall the module
1680467,2018-01-24 22:34:11 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1420
1680468,2017-04-07 15:42:08 UTC,Looks like aptdaemon acting up again.
1680468,2017-04-07 15:42:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680481,2017-04-13 08:38:31 UTC,ping @maintainers: any word on this?
1680481,2017-04-18 15:00:11 UTC,ping @maintainers: anybody here? Is this project still alive?
1680484,2017-04-06 19:11:37 UTC,VPNaaS team needs to triage this.
1680484,2017-04-07 06:03:20 UTC,the driver doesn't have a particular maintainer right now. [1]
1680484,2019-10-15 14:16:27 UTC,I'd say that this should be kinda resolved by that rootwrap filter https://review.opendev.org/#/c/547347/18/etc/neutron/rootwrap.d/vpnaas.filters
1680507,2018-03-12 19:00:29 UTC,glibc upstream bug:
1680507,2017-04-06 15:30:34 UTC,This change was made by a bot.
1680507,2017-06-22 10:39:07 UTC,"Issue found in Artful, series nominated."
1680507,2017-10-06 12:04:03 UTC,"This is because that glibc is missing several of the TRAP_* constants in the userspace
definitions. Specifically TRAP_BRANCH and TRAP_HWBKPT.
See https://sourceware.org/bugzilla/show_bug.cgi?id=21286"
1680507,2018-03-12 19:00:57 UTC,Will fix for now by disabling the test on our selftest suite.
1680507,2018-06-28 10:20:20 UTC,"Test disabled.
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=bd5f0644889aa654532f8bac7b531c6bd3a362a2"
1680507,2018-07-24 09:35:33 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1680523,2017-05-05 21:05:35 UTC,"Andrew,"
1680523,2017-05-05 10:02:07 UTC,"Tommy, I neglected to ask you before: my PR (mentioned in comment #21) has landed. Would you mind seeing if this resolves the issues you have seen with interactive add-credential?"
1680523,2017-05-07 04:23:05 UTC,"> Did you want me to test and build off of the master branch?
"
1680523,2017-04-26 14:56:46 UTC,"@axwalk, I think your intuition regarding async application creation and service principal creation is correct. In Azure CLI we do a bit of retrying to ensure creation of the service principal [0]."
1680523,2017-04-26 04:02:54 UTC,Re comment #17:
1680523,2017-04-27 06:34:27 UTC,https://github.com/juju/juju/pull/7288
1680523,2017-05-08 05:26:18 UTC,"Andrew,"
1680523,2017-06-19 01:32:05 UTC,"Hi Ali,"
1680523,2017-05-09 05:31:31 UTC,"I made the change, re-ran ""go install github.com/juju/juju/cmd/juju"" and
still experienced the same issue:"
1680523,2017-05-09 06:05:27 UTC,"Thanks Tommy. I'll see if I can get some more help from the Azure devs, because it's not clear what we're doing wrong now."
1680523,2017-06-18 16:52:30 UTC,Hi Any movement on this? I am getting same error:
1680523,2019-06-25 01:29:23 UTC,"Having spent some time in credential validation area, I am stating to wonder if this is because we need to have a particular region (not just azure default)."
1680523,2019-07-09 04:22:34 UTC,"As of 2019-07, this looks to be resolved. It's still possible to run into hiccups, but it works when one avoids edge cases."
1680523,2019-07-28 08:14:26 UTC,"hi, im still having issues with the new release 2.6.5.
ERROR finalizing credential: service principal not found
when using interactive authentication."
1680523,2017-04-26 03:25:55 UTC,I also tried using an SP and got a different error:
1680523,2017-05-08 05:57:53 UTC,"Tommy, the log says 26 Apr. Looks like it didn't get updated."
1680523,2017-04-26 03:24:28 UTC,"Andrew,"
1680523,2017-04-11 02:41:42 UTC,"Andrew,"
1680523,2017-04-25 16:19:08 UTC,"Andrew,"
1680523,2017-04-11 02:26:31 UTC,"Tommy, can you please try again? The AAD application had an unnecessary permission which required admin consent. I've removed that, so you shouldn't get that error any more."
1680523,2017-04-26 02:10:45 UTC,"My change has landed on the ""develop"" branch, which is the main branch we all work off. We're expecting to release 2.2-beta3 in the next couple of days, so you can either wait for that, or follow the instructions below to build:"
1680523,2017-04-11 03:16:36 UTC,"Sorry, it looks like the the Azure Portal got a bit confused. Removing the permissions in the UI didn't take effect, and the manifest *grew* permissions somehow. Anyway, I've just removed them and confirmed that the manifest got updated this time. Please try again and see how you go."
1680523,2017-04-11 03:35:19 UTC,Removing Juju milestone to avoid confusion :D
1680523,2017-04-11 03:36:06 UTC,Also Marking as Fix Released as the change is independent from Juju codebase.
1680523,2017-04-11 03:40:44 UTC,"Closer!  I was able to login and it then asked me for permissions to grant
juju access.  I approved, but I'm now getting a different error:"
1680523,2017-04-11 02:55:48 UTC,"FYI, I've tried with two different subscriptions and am still getting the same error."
1680523,2017-04-13 02:09:23 UTC,"Here's the logs.  I removed anything that might be sensitive, so let me
know if there's anything I left out that is vital to solving the problem."
1680523,2017-04-13 04:16:04 UTC,"Thanks Tommy. Can you please provide a couple of those GUIDs, which aren't sensitive:"
1680523,2017-04-13 15:30:40 UTC,"Try again now.  http://lastcoolnameleft.com/mini/azure.log
(might need a hard refresh of the page)"
1680523,2017-04-18 04:03:21 UTC,"Thanks Tommy. I've not made any progress on this so far. We're in contact with Azure AD people, trying to sort this and other issues out now. I'll report back as soon as I know what the issue is."
1680523,2017-04-19 05:23:52 UTC,I have a code change in progress that should fix this.
1680523,2017-04-19 05:29:07 UTC,https://github.com/juju/juju/pull/7252
1680523,2017-04-11 04:03:10 UTC,"I can't see your logins (I imagine only your tenant admin could), so I'll need some more detailed logging to diagnose further. Can you please run with client-side logging turned right up?"
1680526,2017-07-21 17:02:51 UTC,"Andrei,"
1680526,2017-07-21 03:29:45 UTC,Today on 16.04 HWE kernel was updated to 4.10.0-27.30~16.04.2 and nvidia 340.102-0ubuntu0.16.04.1 kernel module failed to build. Is this bug going to be fixed?
1680526,2017-04-12 20:24:41 UTC,"The attachment ""buildfix_kernel_4.9.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1680526,2017-04-12 17:41:40 UTC,"I have on my stystem 'Ubuntu 16.04.2 arch x86_64'
The kernel modules nvidia-340.ko & nvidia_340_uvm.ko (DKMS).
With kernel 4.10.0-14-generic."
1680526,2017-04-06 21:27:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680527,2017-04-06 17:20:39 UTC,"> 1. the pattern is too coarse
"
1680527,2017-04-06 18:34:31 UTC,"Yes, Altium does it too but it looks much better and they do not apply it to copper. I don't believe that applying the texture to copper is correct, from every PCB I've looked at, I do not see fiber board textured impression in the exposed copper pour, either way even if there is a tiny texture in the copper <5% of original, what should be shown to the user is a plated copper pad, ENIG, ENEPIG, HASL, etc and those definitely would not have that texture.
http://i.imgur.com/zNo1y65.png
http://i.imgur.com/QYkp3oW.png"
1680527,2017-04-07 11:13:10 UTC,"I agree that the plated copper should look different.
When I implemented it I didn't thought about the plated copper but only on raw copper."
1680527,2017-04-08 18:28:15 UTC,"Did you look at this picture and think everything should look the same, the copper, the pcb, etc?
https://s-media-cache-ak0.pinimg.com/originals/1f/8c/a1/1f8ca1e108fb9513c283ac32e6c0215f.jpg"
1680527,2017-04-08 19:02:34 UTC,"> Did you look at this picture and think everything should look the same, the copper, the pcb, etc?
"
1680531,2019-11-29 18:51:11 UTC,"Fix proposed to branch: stable/19.10
Review: https://review.opendev.org/696754"
1680531,2020-01-10 12:23:41 UTC,"Reviewed:  https://review.opendev.org/696754
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=124070f8c53d03e123155c458161bebdb6048626
Submitter: Zuul
Branch:    stable/19.10"
1680531,2019-11-14 01:30:54 UTC,"I don't see metadata.yaml update in the patch to support network spaces. Looks like it was discussed in the review, but what happened in the end?
https://review.opendev.org/#/c/675450/"
1680531,2019-11-13 18:23:54 UTC,"Reviewed:  https://review.opendev.org/675450
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=0905a447ad66e553beff1ec3f12a984494ce7785
Submitter: Zuul
Branch:    master"
1680531,2019-08-08 19:21:20 UTC,### Testing done with the patch applied (https://review.opendev.org/#/c/675450/) ####
1680531,2019-08-08 19:20:38 UTC,https://review.opendev.org/#/c/675450/ has been submitted to address this.
1680537,2017-04-06 18:59:45 UTC,Please provide steps to reproduce and more in depth information of what/how you are trying to achieve it.
1680537,2017-04-06 19:10:07 UTC,"One question that comes up from time to time is ""how do I specify a secondary nameserver for a MAAS controlled domain?"" -- The answer is to add an NS RR to the domain [maas SESSION dnsresource-records create name=""@"" domain=""maas"" rrtype=ns rrdata=""fqdn.of.secondary.""].  While this works for any so-called forward zone (those with a Domain object), there is no way to do this for the reverse zones (which are synthesized from the Subnet object)."
1680537,2019-09-19 12:03:28 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1680541,2017-08-02 14:26:30 UTC,"With latest -git version it works for me, could you check it? [1]"
1680553,2017-04-11 19:42:54 UTC,"Data request by Mark Wenning from R640 at Dell
Please find attached the /var/log output and rdmsr output in txt file
regards,
Jerry Clement"
1680553,2017-04-11 19:45:40 UTC,"rdmsr-output.txt attached
Can only attach one file per comment? ok.
--Jerry"
1680553,2017-04-06 21:38:25 UTC,"Customer posted their debug output:
We get an error during:"
1680562,2018-01-11 18:57:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680566,2017-11-07 19:06:02 UTC,"Here's a branch to remove the offending code, but I have not yet tested the code paths where open-ils.permacrud was replaced with open-ils.pcrud.  In theory, it should just work -- confirmation pending."
1680566,2017-11-07 20:22:39 UTC,Branch here for testing and signoff: user/jeff/lp1680566_remove_permacrud
1680566,2017-11-07 20:46:13 UTC,"Thanks, Jeff.  You caught a few things I missed (and added release, notes, yay).  We still need to merge my .js file changes (migrating to open-ils.pcrud) into the final branch."
1680566,2017-11-07 21:38:09 UTC,"Scratch my previous comment, I missed one of Jeff's commit.  +1 to Jeff's branch."
1680566,2018-02-28 20:45:23 UTC,"Unfortunately, this isn't ready for 3.1. For create, update, and delete actions, open-ils.pcrud turns out to not be a drop-in replacement for open-ils.permacrud, as the former wants an explicit client session and a transaction opened before doing CUD, whereas open-ils.permacrud did not."
1680571,2017-04-07 00:10:24 UTC,"The URL is not working yet, but this is the expected one for the tutorial: https://tutorials.ubuntu.com/tutorial/continuous-delivery-from-travis-ci"
1680576,2017-09-01 17:13:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680576,2018-05-03 00:04:34 UTC,Problem still exists on Ubuntu 16.04:
1680578,2017-04-06 21:26:13 UTC,Please attach ~/.cache/simple-scan/simple-scan.log after doing this (or run simple-scan -d from the command line).
1680578,2017-04-14 21:34:46 UTC,Thanks for responding - sorry it took so long to get back to you. Scanned the log here and found:
1680602,2017-09-21 13:03:27 UTC,"As this is a usability issue, Triaging as Low."
1680608,2017-04-09 14:12:24 UTC,"I've noticed this as well. It even happens on reboot, which is really troublesome :("
1680616,2017-04-06 22:02:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454368"
1680616,2017-04-12 11:49:31 UTC,"Reviewed:  https://review.openstack.org/454368
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d52bcc616f2d1c0df7bad8a6f5a00adc7ad1fb27
Submitter: Jenkins
Branch:    master"
1680616,2017-04-14 09:22:02 UTC,This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
1680616,2017-10-13 02:44:05 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/511682"
1680616,2018-03-21 08:33:31 UTC,"Reviewed:  https://review.openstack.org/511682
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e2c2b1d586f4e24f0e4f3fc760c687e03c501ec7
Submitter: Zuul
Branch:    stable/ocata"
1680616,2018-05-02 12:05:45 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1680630,2017-06-07 01:28:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680630,2021-01-07 04:16:54 UTC,4.8 EOL
1680633,2017-04-10 22:33:31 UTC,Hi Kenneth
1680671,2017-05-11 07:26:04 UTC,Marking as confirmed.
1680671,2018-01-20 08:03:27 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1437
1680680,2017-04-12 23:08:32 UTC,apport information
1680680,2017-04-12 23:08:35 UTC,apport information
1680680,2017-04-12 23:08:37 UTC,apport information
1680680,2017-04-12 23:08:19 UTC,apport information
1680680,2017-04-12 23:08:40 UTC,apport information
1680680,2017-04-12 23:08:30 UTC,apport information
1680680,2017-04-12 23:08:38 UTC,apport information
1680680,2017-04-12 23:08:29 UTC,apport information
1680680,2017-04-12 23:34:06 UTC,"I've uploaded the requested logs. As mentioned in comment #1, I do have the the UWB wireless setting disabled in the BIOS, so the laptop can suspend. If you need it re-enabled in order to gather additional information, just let me know. Thanks."
1680680,2017-04-12 23:08:26 UTC,apport information
1680680,2017-04-12 23:08:24 UTC,apport information
1680680,2017-04-12 23:08:23 UTC,apport information
1680680,2017-04-12 23:08:21 UTC,apport information
1680680,2017-04-12 23:08:43 UTC,apport information
1680680,2017-04-11 22:01:01 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1680680,2017-04-07 04:22:30 UTC,"As a work around, I found if I disable UWB (USB Wireless Bluetooth?) in the BIOS under Wireless, then the laptop will suspend when suspend is selected."
1680680,2017-04-12 23:08:27 UTC,apport information
1680681,2017-06-06 11:11:52 UTC,I would like to help out with this one can you guide me on this
1680681,2019-05-16 08:54:27 UTC,created: https://storyboard.openstack.org/#!/story/2005714
1680683,2017-04-08 09:37:02 UTC,"Do you have numbers on where the time is spent? (And what version the
controller is running.) I wonder if you're running into extra data from
some of the collections that aren't being cleaned up. Or whether it is just
that you have lots of large charms or if it is logs/statuseshistory/etc."
1680683,2017-04-10 04:07:53 UTC,@jameinel: I'm not sure how I would go about determining where the time was spent - juju create-backup is a black box from the user perspective: we ask for a backup and get a tarball.
1680683,2017-04-10 11:26:44 UTC,you should be able to run the attached script as an admin user and find the sizes of various collections that are involved:
1680683,2017-04-11 00:09:53 UTC,"sizes.js output for the environment in question: https://pastebin.canonical.com/185462/
(Note for future travelers: the above script must run on the primary node in an HA environment.)"
1680683,2017-04-11 03:39:30 UTC,"I think this change would let you run it on a secondary:
$ diff -u sizes.js sizes2.js
--- sizes.js	2017-04-11 07:34:48.000000000 +0400
+++ sizes2.js	2017-04-11 07:34:37.000000000 +0400
@@ -17,7 +17,7 @@
 var collStats = [];
 for (i = 0; i < collectionNames.length; i++) {
   coll = collectionNames[i];
-  s = db[coll].stats();
+  s = db[coll].stats({""slaveOk"": 1});
   var storageSizeMB = s['storageSize'] / bytesInMB;
   var indexSizeMB = s['totalIndexSize'] / bytesInMB;
   var totalSizeMB = storageSizeMB + indexSizeMB;"
1680683,2017-04-12 01:12:01 UTC,@jameinel: The updated sizes script didn't work on a slave; the problem is earlier in the code than your change - it fails on calling db.getCollectionNames().
1680683,2017-04-12 03:32:33 UTC,"So the bulk of the backup is just that you have a large 'blobstore' which
is all of the charms, resources, etc that you have deployed."
1680683,2017-04-12 03:57:32 UTC,"On 12 April 2017 at 13:32, John A Meinel <email address hidden> wrote:"
1680683,2017-04-12 04:39:45 UTC,"@jameinel: This is a JAAS instance, and the charms in the models are entirely opaque to us."
1680683,2017-04-26 00:42:16 UTC,I think that one thing that could be done here is to look at fixing the backup/restore process to not exclusively use the mongo dump.
1680685,2019-05-16 08:56:02 UTC,created: https://storyboard.openstack.org/#!/story/2005715
1680690,2019-05-16 09:23:35 UTC,created: https://storyboard.openstack.org/#!/story/2005716
1680692,2019-05-16 09:33:03 UTC,created: https://storyboard.openstack.org/#!/story/2005717
1680692,2017-04-10 09:44:39 UTC,"So, this is currently in an ethercalc and needs to be transferred to RST (preferably). We (Adam and myself) want to find out a way to do this using the colour coded system already in place."
1680693,2019-05-16 09:35:49 UTC,created https://storyboard.openstack.org/#!/story/2005718
1680695,2019-05-16 09:40:44 UTC,created: https://storyboard.openstack.org/#!/story/2005720
1680697,2017-04-07 05:29:15 UTC,"I have do some change to it, see https://review.openstack.org/#/c/454455/"
1680726,2017-04-07 07:28:47 UTC,"Sorry, a typo... ""switcht go VT"" means ""switch to"""
1680727,2017-04-12 10:05:44 UTC,"No diagnostic snapshot, marking as Incomplete."
1680741,2017-05-17 12:36:09 UTC,For MOS 9 patch placed here -- https://review.fuel-infra.org/gitweb?p=openstack/horizon.git;a=commit;h=ce80bb6fec3cb0262728e7ae8b9d695cf832e5bf
1680741,2017-06-26 09:00:22 UTC,"This bug is Invalid for 8.0, because federation mappings in Horizon was implemented since Mitaka release."
1680741,2017-05-17 12:47:01 UTC,Commit merged for MOS 10 -- https://review.fuel-infra.org/gitweb?p=openstack/horizon.git;a=commit;h=8553409c2728b2ef851bdf7161fece820c13a662
1680744,2017-04-13 12:01:28 UTC,"Reviewed:  https://review.openstack.org/454608
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=d29333b7a8b24615397141958a6c7b5603d82efe
Submitter: Jenkins
Branch:    master"
1680744,2017-06-09 15:35:50 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1680744,2017-04-07 08:38:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454608"
1680750,2017-04-10 19:38:04 UTC,"@teo8976, thanks for reporting this."
1680750,2017-06-10 04:17:48 UTC,[Expired for pm-utils (Ubuntu) because there has been no activity for 60 days.]
1680750,2017-12-01 14:20:20 UTC,"> 1. It sounds like this used to work? Was it working on 16.04 and only recently broke?
"
1680751,2017-04-22 16:41:39 UTC,Fixed by: https://review.openstack.org/#/c/454640/
1680751,2017-04-24 13:27:50 UTC,This issue was fixed in the openstack/python-zunclient 0.2.0 release.
1680753,2017-04-10 11:34:27 UTC,"we had some issues with re-installing slaves
for now we have re-installed one of two slaves and expecting positive result of a test run below:
https://ci.fuel-infra.org/job/8.0.fuel-library.pkgs.ubuntu.smoke_neutron/1485/console"
1680753,2017-04-10 13:51:58 UTC,closing the bug since we have successfully finished tests
1680760,2017-04-18 11:03:24 UTC,Reported upstream: https://github.com/cnc-club/gcodetools/issues/9
1680760,2018-02-11 01:04:07 UTC,Upstream unfortunately never reacted. The issue has been fixed by Shockster at https://forum.inkscapecommunity.com/index.php?topic=486.msg3889#msg3889
1680760,2018-11-04 17:07:59 UTC,It's actually fix released by now.
1680763,2017-04-07 09:11:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454625"
1680778,2017-04-18 10:07:22 UTC,Thanks for taking the time to file a report!
1680799,2017-04-07 12:48:12 UTC,"I would suggest the ""test"" database (at least) is set as the default value for the --ignore-databases option so that it can be overridden if necessary, rather than having the databases hardcoded in the tool."
1680799,2017-04-11 09:17:36 UTC,"In my opinion, --databases option should allow checksum of database for test database so by default it ignore but If --databases option explicitly specify ""test"" database then it should go for the checksum process."
1680799,2018-01-24 22:26:54 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1421
1680803,2017-04-18 10:03:43 UTC,I see no problem like that with 10.2.6 (on Fedora 25) or 10.2.5 (on Ubuntu 14.04) built from source:
1680803,2017-04-18 10:06:42 UTC,My 10.2.5 is older than April 7:
1680803,2017-04-18 21:33:02 UTC,"To reproduce, the 10.2 server should be started with InnoDB, and even then I imagine it can be system- or luck-dependent."
1680803,2018-01-24 22:40:43 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1422
1680806,2017-04-07 11:07:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454675"
1680806,2017-07-04 03:57:59 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/454675
Reason: Let's hold this a while."
1680811,2019-09-21 20:55:39 UTC,"I hace openresolv installed, do not have resolvconf installed, and I still see the above error. I see the error even after deleting /etc/resolv.conf."
1680811,2017-04-07 23:55:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680811,2017-04-08 08:12:17 UTC,Tanks. I'll make this change upstream in Debian too.
1680811,2017-04-15 17:09:40 UTC,"It might make more sense to simply switch to using openresolv, which is a proper resolvconf implementation, which doesn't rely on this silly hard-coded list. Alternatively, you could just backport features one by one from openresolv, such as '-m 0 and '-x'."
1680812,2019-09-19 12:03:30 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1680812,2017-06-28 09:51:42 UTC,@Andres
1680812,2017-06-27 17:56:40 UTC,"@Maria,"
1680826,2017-04-08 08:26:30 UTC,"The attachment ""Dependencies.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1680826,2017-04-08 11:53:05 UTC,"Not a member of the Ubuntu review team, sorry and I didn't notice that I've clicked the flag. I apologize about that as well."
1680826,2017-04-25 10:58:44 UTC,"This is weird but for some reason, having some of the kde-telepathy package installed (not on my machine atm so can't really tell which two were), breaks my apt but makes gdm3 to work (while making me somehow break lightdm and sddm). Now I can't login to the previous ones, but can to gdm3. Also removing the package package with synaptic, makes gdm3 unusable again.
This does not make any sense to me."
1680826,2017-05-23 15:25:24 UTC,I recently fixed a bug which prevented GDM from working (LP: #1686257) for people who had GDM installed but not Ubuntu GNOME. Could you give it a try and let us know if that fixes your issue?
1680826,2019-03-07 17:23:06 UTC,"I can confirm their is a bug. I've also reported something similar on reddit.
GPU: GeoForce GTX 390
:Drivers: 390."
1680826,2019-03-08 01:43:07 UTC,"Gork,"
1680826,2020-11-17 05:39:32 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life in April 2019."
1680830,2017-04-08 02:56:18 UTC,Attached. Zoom to see inconsistent stroke thickness if required.
1680830,2017-04-07 13:31:33 UTC,"As a workaround, you could convert the object to path before skew."
1680830,2017-04-08 00:37:01 UTC,"Thanks fir the reply. Yes I realised that. I just wanted to report a bug
which shouldn't happen."
1680830,2017-04-08 01:53:09 UTC,could you attach the original svg file?
1680830,2020-02-01 01:26:52 UTC,Closing as part of bug migration to GitLab. Was reported here https://gitlab.com/inkscape/inbox/issues/451
1680842,2018-02-28 00:08:20 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu1
1680842,2017-04-07 18:22:14 UTC,"This boils down to missing directories in the landscape-common3 package:
- /etc/landscape
- /var/log/landscape
- /var/lib/landscape"
1680843,2019-09-11 15:34:22 UTC,"I don't think a record should ever be excluded from staff search results, especially  if the item is available and on the shelf. To do so could lead to the title being unnecessarily ordered. It also would mean that a patron would not be provided a title they needed even though it is on the shelf."
1680846,2017-04-07 13:13:31 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f4b41aa93a8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f4b41aa94d8 ""double free or corruption (!prev)"", action=3) at malloc.c:5046
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:3902
 __GI___libc_free (mem=<optimized out>) at malloc.c:2982
 g_list_foreach (list=<optimized out>, list@entry=0x55da7039b180, func=0x7f4b42db5a80 <g_free>, user_data=user_data@entry=0x0) at ../../../../glib/glist.c:1005"
1680846,2018-08-01 16:54:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680846,2018-08-01 16:57:13 UTC,"I'm having the same in 18.04. Might be unrelated but the apport window popped up, after my PC froze which apparently resulted in some disturbance with font rendering. In certain applications (Caja, QuodLibet but not Firefox, for example) some characters are rendered incorrectly. The letter looks a bit like MISSINGNO. ^_^"
1680847,2017-04-10 16:40:59 UTC,Thank you for taking the time to file a bug report.
1680847,2017-04-08 22:38:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680847,2017-04-08 22:41:00 UTC,As a workaround:
1680847,2017-04-10 16:40:24 UTC,From log:
1680849,2017-04-11 11:04:32 UTC,This change was made during the fix of https://bugs.launchpad.net/fuel/+bug/1668553. Please change tests accordingly. Assiginig but to the QA team.
1680852,2017-05-10 14:50:04 UTC,"Yeah, the truth is that ceph can't create pool dynamically here. So in Cinder side, for some backends like ceph, it's better to ignore the ""container""  parameter autolly by code logic IMO."
1680852,2018-01-12 19:03:52 UTC,Unassigning due to no activity for > 6 months.
1680852,2017-04-27 14:01:45 UTC,"This is precisely why I disabled the test for ceph - it can never adhere to this API.  Pools cannot be created dynamically in this way, the API was created with Swift in mind and there are certain features that we cannot mimic.  We can either not run the test, or accept the request and perform the standard logic that we would otherwise while ignoring the container name - this seems misleading at best."
1680852,2017-04-27 01:56:41 UTC,Is there any way to create a new ceph pool by Cinder?
1680852,2017-04-26 22:49:38 UTC,"I feel this bug report says Cinder abstraction API layer doesn't work for Ceph backend at the place.
So it would be great to get feedback from Cinder team."
1680852,2017-04-26 23:15:38 UTC,"I think it may make more sense to update the backup drivers to handle this rather than changing the test. It would be better if the driver is robust enough to handle or skip input that is not relevant for it. So the API and usage is the same, but some of the internal behavior is dependent on the configured backup driver."
1680852,2017-04-13 11:02:49 UTC,"Change abandoned by Andrea Frittoli (<email address hidden>) on branch: master
Review: https://review.openstack.org/454722"
1680852,2017-04-07 13:28:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/454722"
1680853,2017-04-10 14:23:43 UTC,"Additionally tested Xenial/16.04 and Yakkety/16.10 isos and while Xenial will ask for the timezone after declining auto-detection, Yakkety does not. So not a new regression in Zesty but one between Xenial and Yakkety."
1680860,2017-04-10 16:33:57 UTC,"The initial metadata sync is done within the context of a charm hook with nothing to modify the user performing the rsync call. As result, the rsync is performed by root, and the metadata files synced are owned by root."
1680862,2017-04-30 14:44:52 UTC,"Note, this is related to lp1687125 and inclusion of that patch will at least help where the dojo widgets autopopulate from the field mapper.  At least until we can give dojo it's last right in acq."
1680862,2017-06-29 15:54:27 UTC,"As a side note, the patch for bug 1687125 by itself changes nothing for this bug, as acqpron would also need to be exposed via open-ils.pcrud."
1680864,2017-04-11 18:50:52 UTC,"We would like to see better filtering in the Funds admin interface too. In addition to it being case insensitive, it would be great if the 'contains' option didn't require the use of wildcard (%) to find the string."
1680864,2020-10-22 14:11:14 UTC,This is fixed in the Angular Providers work done in 3.6. You can both search by a portion of the name/code as well as filter the list.
1680865,2017-04-11 19:12:18 UTC,"A subsidiary (not division) can have a separate tax ID but I can't imagine
a circumstance where they would be listed as a single provider when they
are so distinct from a parent company (and each other) as to become
subsidiaries.  This is all in regards to US tax and incorporation, I don't
know about other countries."
1680865,2017-04-11 17:50:54 UTC,Thanks for the information. Another question: can a provider have more than one tax ID? (I'm thinking of large ones like B&T.)
1680865,2017-04-11 18:39:11 UTC,"I double-checked with the acquisitions staff, but we've only ever seen one tax ID number per company, even when they have multiple different addresses for different functions, like firm orders versus standing orders."
1680865,2017-04-07 14:35:05 UTC,"Would such a field be used just for reporting purposes, or would it need to be be output on POs, invoices, or EDI messages?"
1680865,2017-04-11 16:51:08 UTC,"Our use for this field is primarily for tracking.  We need to know what the vendor's tax ID number is so that we can report it to our budget office.  It would be useful to have the tax ID number print on invoices, however.  (We don't use EDI, so I can't speak to that.)"
1680868,2017-04-19 07:21:45 UTC,"Hi Martins,"
1680868,2017-04-21 09:40:51 UTC,"Hello Maxime,"
1680879,2017-06-22 11:13:45 UTC,"Hi, thank you for the time spent in test UPnP Router Control."
1680879,2017-06-22 12:03:47 UTC,"Hello,"
1680882,2017-04-07 15:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1680885,2019-07-09 01:37:59 UTC,Must have been fixed as part of other work since I cannot reproduce locally under stress.
1680891,2017-04-25 17:32:55 UTC,"Sorry, I think I misunderstood what the issue was. I'll take another look when I get chance, as I'll need to get to my dev environment, and pull down your script to take a look."
1680891,2017-04-25 05:41:42 UTC,"Hi Dan. First, a big props picking this up and getting it to date."
1680891,2017-04-25 08:56:17 UTC,Hi Stephen
1680891,2017-04-25 14:44:13 UTC,"The simplest thing to do is to call the save function whenever you make a change (add/edit/del). This would update Terminators internal state, and the menu should be immediately updated. It's not particularly elegant, but it should work. The disadvantage is that the Cancel button stops having an effect. Better would be to add an Apply button to the OK/Cancel area that calls the save function."
1680891,2017-04-25 16:41:09 UTC,No such luck.
1680891,2017-04-09 13:58:36 UTC,"Thanks for your tips Stephen, although I still haven't quite figured how to debug/test Term plugins. When I use the -d flag to start terminator, I get some debug output but I can't see anything relating to SSHMenu or plugins. If I use `--debug-classes SSHMenu`, with or without -d, I get no output at all."
1680891,2017-04-26 06:46:49 UTC,"Actually I just realized that the models are probably constructed differently, and would need to be aligned for this to work."
1680891,2017-04-26 07:23:02 UTC,I just noticed something else. You removed the GPL v2 only notice from the source file. You probably shouldn't do that. Your modifications are automatically GPL v2 anyway.
1680891,2017-04-26 09:27:49 UTC,Hi Stephen
1680891,2017-04-24 22:44:35 UTC,Hi Stephen
1680891,2017-04-26 11:16:50 UTC,Hi Stephen
1680891,2017-04-26 06:44:42 UTC,"OK, yeah, I totally misunderstood :-)"
1680891,2017-04-22 08:58:46 UTC,Hi Stephen
1680891,2017-04-08 18:00:06 UTC,Hi Stephen
1680891,2017-04-12 16:10:40 UTC,Hi Stephen
1680891,2017-04-12 14:55:15 UTC,Hi Stephen
1680891,2017-04-12 14:10:38 UTC,Hi Dan. Sorry I haven't got back to you. Just busy.
1680891,2017-04-12 13:57:25 UTC,The arch site is back. Here's what arch does to the term 1.91 source before installation:
1680891,2017-04-12 13:45:51 UTC,"I think I've spotted a big clue to the cause my probs. When I start term with -dd (or -d -d), I don't get an extra 'Open Debug tab' under the term context menu and nor do I see a 'Listening:' line in the term debug startup log."
1680891,2017-04-12 12:29:17 UTC,Sorry - ignore my last comment. ssh-menu does load if I copy it to /usr/lib/python2.7/site-packages/terminatorlib/plugins but that makes no difference to me on my quest to see plugin errors/debug stuff. Using one or two -d switches (and --debug-classes SSHMenu) isn't providing me the info I seek.
1680891,2017-04-12 12:21:48 UTC,I only see debug info relating to term plugins if I start terminator with:
1680891,2017-04-11 10:25:25 UTC,Hi Stephen
1680891,2017-04-08 22:51:18 UTC,"The doc you link to is old, but it is current as far as I'm aware. A manual is available now too, although the section covering plugins is a copy and paste from the tenshu one: http://terminator-gtk3.readthedocs.io/en/latest/plugins.html#creating-your-own-plugins"
1680891,2017-04-26 11:42:22 UTC,"Certainly not a waste. Yes, I had noticed the similarity in the windows and realized the code was derivative. First solution is unfortunately not a one liner. The shortest way would be to factor out the loading of config for the menu window out into a separate function, then after saving the new config, call that separate function to reload config."
1680891,2017-04-07 20:23:09 UTC,"You can use layouts to create presets and save the set of logins, editing the command to perform the ssh login. I know some people don't like this method, but I used it for a long time with great success."
1680891,2017-04-12 20:32:24 UTC,"As for rough edges, the main issue with the SSH Menu plugin as it stands is that you currently need to close and re-open the SSH Menu window before newly added commands are displayed and deleted commands get removed."
1680894,2017-08-22 14:23:52 UTC,"@Wes, the openstack healthcheck commands seem covering #1 and #2, isn't it?"
1680894,2017-08-22 13:18:59 UTC,Looking for some simple sanity checks for the containers.
1680894,2017-11-10 21:23:30 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.openstack.org/454884"
1680894,2017-07-05 18:58:03 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1680894,2019-01-22 13:47:13 UTC,Any updates on this?
1680900,2018-01-17 10:26:04 UTC,"Reviewed:  https://review.openstack.org/533092
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=9aacda8f8315e69fd67f173a6460259f847bad2c
Submitter: Zuul
Branch:    stable/pike"
1680900,2018-01-12 06:39:41 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/533092"
1680900,2018-02-23 00:43:47 UTC,"Reviewed:  https://review.openstack.org/547096
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=49822b0b3d120a69052fedca26f47b467d881386
Submitter: Zuul
Branch:    stable/queens"
1680900,2018-02-23 00:43:19 UTC,"Reviewed:  https://review.openstack.org/507465
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=30785acd3cd90594cb5d9913ae3830d6faeee0b6
Submitter: Zuul
Branch:    master"
1680900,2017-12-18 10:00:19 UTC,"Reviewed:  https://review.openstack.org/468816
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=273405cb5a8cdbcec816f646cfe82f13784b3bf1
Submitter: Zuul
Branch:    master"
1680900,2018-02-22 18:28:18 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/547096"
1680900,2017-05-15 14:40:27 UTC,"Change abandoned by Kevin Lefevre (<email address hidden>) on branch: master
Review: https://review.openstack.org/464618"
1680900,2017-05-15 11:39:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/464618"
1680900,2017-05-10 05:12:13 UTC,"Reviewed:  https://review.openstack.org/454778
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=58d1fc552377d9295e6200a2c9acd8cbf44cca43
Submitter: Jenkins
Branch:    master"
1680900,2017-08-23 16:08:29 UTC,This issue was fixed in the openstack/magnum 5.0.0 release.
1680900,2017-04-07 16:02:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/454778"
1680916,2017-04-07 17:50:38 UTC,A workaround I found is to fall back to totem-video-thumbnailer:
1680916,2017-08-23 02:05:44 UTC, What does invalid mean and why do all my bugs sit out there for six months and then get changed to that? This is a real problem and all you're going to do is say that it's invalid and not tell me any reason why or any other information I just have to continue to deal with it? Why do I even bother?
1680918,2017-06-08 21:53:09 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1680918,2017-05-08 22:25:45 UTC,This issue was fixed in the openstack/nova 14.0.6 release.
1680918,2017-04-25 19:33:39 UTC,"Reviewed:  https://review.openstack.org/458667
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c23c5e9f747e7127497dfd77ca0b33df2be74a2d
Submitter: Jenkins
Branch:    stable/ocata"
1680918,2017-04-21 17:41:30 UTC,"Reviewed:  https://review.openstack.org/458668
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad12fa65f5cc06bdee52be49b7370d703855d618
Submitter: Jenkins
Branch:    stable/newton"
1680918,2017-05-08 22:10:14 UTC,This issue was fixed in the openstack/nova 15.0.4 release.
1680918,2017-04-20 21:48:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/458667"
1680918,2017-04-20 18:49:56 UTC,"Reviewed:  https://review.openstack.org/456397
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7f3f0ef1fbb51f6f17d2c13840e0f98d17fa9093
Submitter: Jenkins
Branch:    master"
1680918,2017-04-20 21:49:38 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/458668"
1680918,2017-04-12 21:23:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456397"
1680927,2017-12-01 13:15:24 UTC,"Sorry to be a killjoy, but this fix shouldn't be SRUed to Xenial."
1680927,2017-11-30 20:49:24 UTC,"Hello Marco, or anyone else affected,"
1680927,2018-02-09 01:41:02 UTC,"Readded tags not to block SRU release, but this fix isn't included in unity 7.4.5+16.04.20171201.3"
1680927,2017-04-08 16:19:30 UTC,This bug was fixed in the package unity - 7.5.0+17.04.20170407.1-0ubuntu1
1680929,2017-04-07 20:24:49 UTC,"This was just fixed in
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15617"
1680929,2017-04-08 19:21:46 UTC,"Thanks Eduard for fast response
Is this fix is applicable for the next image?"
1680929,2017-04-08 19:48:08 UTC,Rendering in trunk r15618.
1680931,2017-04-07 20:06:17 UTC,"This was just fixed in
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15617"
1680931,2017-04-07 20:24:34 UTC,"Ah, sorry, replied to the wrong bug..."
1680935,2017-04-07 20:29:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1680936,2019-05-07 04:48:17 UTC,I can no longer reproduce this scenario on Juju 2.6 - there have been a considerable number of changes in both provisioning and lxd and entity destruction/removal areas.
1680936,2017-04-10 13:24:22 UTC,I do not necessarily think that remove-unit should destroy machines.  I just think that its behaviour should be consistent.
1680936,2017-04-08 08:29:03 UTC,"So it doesn't seem surprising that if you have a container on a machine
removing a unit from the machine should not destroy the machine. It also
seems to follow that if you deployed just a container and then remove that
container you don't want to destroy that machine (you're quite likely to
want to create another container on it). Really the only time remove unit
seems very good for removing the machine is if the machine was provisioned
explicitly for that unit and only that unit."
1680936,2017-04-10 13:24:52 UTC,"Doh.  *remove-unit* appears to be consulting the current state when determining whether to remove the machine. I believe that instead, it should be consulting the target state."
1680937,2017-04-29 16:34:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680938,2017-04-07 19:10:06 UTC,This needs more dicussion and might be focussed more on Octaviaclient
1680938,2017-08-08 06:23:51 UTC,Releaving for now due to lack of efforts
1680941,2017-04-09 15:22:06 UTC,It seems to occur only if you put the transition near the cursor line when it gets automatically adjusted.
1680957,2017-05-16 09:30:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680958,2017-10-27 22:37:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1680975,2017-04-10 16:18:58 UTC,"Confirmed, steps to reproduce:"
1680975,2017-04-10 16:26:28 UTC,"Looks like this is not an issue upstream [1] and Ubuntu does not carry a delta from debian right now, so would need to see what is in the debian packaging."
1680977,2018-09-08 17:07:37 UTC,I can't confirm that bigger buffer sizes make the gap larger.
1680990,2019-09-19 12:03:33 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1680991,2020-11-18 11:14:41 UTC,"The timer has been implemented, see commits:
d05be883fc9 (""hw/timer/bcm2835: Add the BCM2835 SYS_timer"")
0e5bbd74064 (""hw/arm/bcm2835_peripherals: Use the SYS_timer"")
722bde6789c (""hw/arm/bcm2835_peripherals: Correctly wire the SYS_timer IRQs"")"
1680991,2017-04-08 00:17:39 UTC,The command lines are:
1680991,2017-11-07 15:07:55 UTC,"The raspi2 board model is only partial, and is missing various devices that weren't used by the test images that it was tested with (mostly Windows-for-Arm, I think). The ""system timer"" is one of the devices that hasn't been implemented, which is why the memory locations where it should be just read-as-zero."
1680991,2020-11-18 10:51:04 UTC,"Is anybody still working on the raspi2 model? If not, shall we close this as WontFix?"
1680991,2020-12-10 09:16:40 UTC,Released with QEMU v5.2.0.
1680992,2017-05-29 05:50:55 UTC,@Greg: Sounds reasonable. The only thing we need to figure out now is how we implement this the right way.
1680992,2017-04-08 00:17:54 UTC,More swiss-army like could be a dns.extra_lines option? What do you all think?
1680997,2017-04-10 21:14:26 UTC,"Hi,"
1680997,2017-04-10 22:30:51 UTC,"The steps outlined in the initial bug report reliably (100%) reproduce the problem for me on Ubuntu 16.04, it is tested in different Environments (1xAMD, ca. 10xIntel).
Here's the short way to get there:"
1680997,2017-04-18 13:39:11 UTC,"[...]

> Migrating to lxd is not feasable in many environments, in addition to that i am totally aware >
> (and not critisizing!), that libvirt-lxc was/is unsupported.
"
1680997,2017-04-18 13:41:47 UTC,Yet given that upstream deprecated it even their interest might diminish :-/
1680997,2017-04-18 13:56:09 UTC,"Note, the last I heard it was not deprecated by *upstream*, but by redhat."
1680997,2017-05-19 22:09:03 UTC,Upstream bug report is at https://bugzilla.redhat.com/show_bug.cgi?id=1452701
1680997,2018-06-26 14:57:13 UTC,"Closed by upstream for insufficient data :-/
Setting incomplete here as well"
1680999,2017-04-08 11:21:35 UTC,"works fine now, thanks:)"
1680999,2017-04-08 08:39:52 UTC,"Hello,
Pulsesrc element comes from the gstreamer1.0-plugins-good package.
Have you installed it?"
1681005,2017-04-12 04:05:35 UTC,"Looking at the cloud init log on xenial, I can't see that's it's importing /usr/lib/python3/dist-packages/cloudinit/config/cc_package_update_upgrade_install.py"
1681005,2017-04-12 09:56:57 UTC,This was tested on AWS and vSphere and apt-get update/upgrade run as expected.
1681005,2019-02-22 10:32:33 UTC,"It's not entirely clear to me what the bug being reported against cloud-init here is.  Given the age of the bug, I assume it no longer applies, but please do give us reproduction steps and move it back to New if I am mistaken."
1681005,2017-04-12 22:44:50 UTC,Marking as Invalid for Juju - nothing that we can fix in our codebase.
1681005,2017-04-12 03:53:55 UTC,I've targetted to cloud-init to see if those folks can give some feedback as to what might be happening.
1681005,2017-04-12 14:01:30 UTC,"The ""charms tests"" section in any test results (http://reports.vapour.ws/releases/5121) show we have comprehensive testing across substrates. We know know joyent is problematic at this time."
1681005,2017-04-12 03:52:34 UTC,The xenial machine which doesn't run apt-get update/upgrade appears to have the correct config as shown in cloud-init.log
1681005,2017-04-12 01:30:16 UTC,"Looking at machines run up in Joyent, the cloud init log clearly shows the package update/upgrade attributes are being correctly set:"
1681005,2017-04-12 03:29:15 UTC,"I can also see the expected apt-get output in the cloud init logs showing the package indices being updated from the expected sources, and the result of the dist-upgrade. So from what I can see:"
1681005,2017-04-12 03:21:51 UTC,I've checked the cloud init logs further and the correct apt-get commands are running.
1681005,2017-04-12 03:45:46 UTC,This looks like an issue between cloud-init 0.7.5 on trusty vs 0.7.9 on xenial.
1681005,2017-04-11 15:04:02 UTC,"Yes I know update and upgrade are enabled be default, which is why it took so long to discover this bug. We have never seen an issue with bootstrap. In fact, I think bootstrap has always worked. When health checks and tests cannot bootstrap, We know the cloud is ill or mirrors are stale. Apt issues in the log are brought to IS who control the mirrors. We occasionally see a mirror has OOMed."
1681005,2017-04-11 14:30:13 UTC,Both enable-os-refresh-update and enable-os-upgrade are true by default.
1681022,2017-09-29 14:51:24 UTC,Committed fix for jpeg file extension.
1681025,2017-04-08 04:55:44 UTC,"Please find the attached wireshark trace of the BOOTP messages for problem usecase, whereby the system was rebooted."
1681025,2017-04-08 05:02:58 UTC,Please find the attached patch service that was used to delay the network initialization so that it is not affected by the time-change by systemd-timesyncd.service. This may not exactly be an acceptable solution but demonstrates how equivalent changes can be performed to arrive at the solution.
1681028,2017-05-24 16:02:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681028,2017-05-24 16:08:58 UTC,I have the same Ubuntu and Glade versions and am seeing the exact same problem.  I will also add that in addition to the memory usage growing I also see the CPU utilization maxing out for the process.
1681038,2017-04-19 01:20:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681046,2017-07-05 11:39:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681046,2017-08-03 06:13:30 UTC,ma perchè non parlate in italiano?? non siamo tutti inglesi a questo mondo
1681068,2019-10-09 20:42:48 UTC,"I tried building your snaps with snapcraft to reproduce the issue, but unfortunately the vault-snap is missing a consul binary from the consul-dir part. Can you update the snapcraft.yaml sources and try this with a more recent snapd? I suspect this bug has been fixed as a number of mount namespace bugs have been fixed since this was filed, but without a complete reproducer we are unable to continue."
1681068,2019-12-09 04:17:38 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1681070,2017-04-10 11:31:19 UTC,"What do you mean by ""does not migrate existing user accounts""?"
1681070,2017-04-10 13:52:27 UTC,"When you attempt to install from the live environment over an existing installation, the installer will detect that installation and allow you to perform an upgrade. It works just like the upgrade process in Ubuntu -- except the MATE installer clobbers the existing /etc/passwd file and creates and prompts you to create a new user account. When performing the same process in Ubuntu in both current and previous releases, the installer skips the user account creation prompts and retains the existing user accounts."
1681077,2017-09-18 15:05:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681077,2017-10-13 19:50:14 UTC,This bug was fixed in the package libimobiledevice - 1.2.0+dfsg-3.1ubuntu3
1681099,2019-10-09 20:42:49 UTC,"I tried building your snaps with snapcraft to reproduce the issue, but unfortunately the vault-snap is missing a consul binary from the consul-dir part. Can you update the snapcraft.yaml sources and try this with a more recent snapd? I suspect this bug has been fixed as a number of mount namespace bugs have been fixed since this was filed, but without a complete reproducer we are unable to continue."
1681099,2019-12-09 04:17:37 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1681101,2018-01-18 03:57:54 UTC,confirmed
1681101,2017-10-24 23:31:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681102,2017-12-02 23:51:48 UTC,I have a similar issue.  Only work around I know is toggling on and off secure boot in my bios.
1681104,2017-04-30 16:56:58 UTC,It seems a recent update has fixed this.
1681104,2017-04-08 14:44:09 UTC,"Sorry, wrong hardware model comment.  The correct one is"
1681107,2017-04-10 09:13:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681107,2017-04-10 09:18:33 UTC,I discovered this problem when trying to use the new BBC Concert Sound Taster. Their page says:
1681110,2017-04-10 20:52:19 UTC,You might be able to get the command-line interface you wish by removing or otherwise configuring the pinentry-gnome3 package.
1681110,2017-04-18 15:50:21 UTC,"Thanks for the suggestion. 'dpkg-reconfigure pinentry-gnome3' didn't do anything, so I installed looked through the documentation and couldn't find any relevant configuration options."
1681110,2017-04-19 01:26:20 UTC,Macho reported this upstream at https://dev.gnupg.org/T3084
1681125,2017-04-10 12:05:51 UTC,"The fix is to get rid of the ,0) argument in that line 176. I've committed that fix to the development trunk and it will be in 2.5."
1681138,2017-04-09 03:48:33 UTC,">What's the nature of the corruption
"
1681138,2017-04-09 03:07:04 UTC,"What's the nature of the corruption? For example is there too little data?
How do you mean ""flush of the write buffer""?
3 seconds sounds way too short to actually write the data.
I presume you're unmounting the device before ejecting it?
Note cp is just doing read/write so unlikely to be the issue.
Note also cp reads/writes 128KiB at a time,
whereas dd defaults to only 512B at a time and so may avoid async issues."
1681144,2017-08-30 18:35:19 UTC,"This bug also applies to Lubuntu Next (LXQt).
Clicking the link to visit our website on both the:
 - Need Help; and
 - Thank you for Choosing Lubuntu Slides
does nothing."
1681144,2017-04-11 04:19:21 UTC,"Wait, wrong bug. This is still an issue and needs a fix in ubiquity directly to start up a browser when slideshow links are clicked."
1681144,2017-10-16 21:25:09 UTC,"As far as I can tell all the code is there to start a browser when a link is clicked. In this case, I think the issues come from bad config somewhere in the installer environment for QT: XDG or something else is missing to associate clicking a link with the application that should open it."
1681144,2017-04-08 21:13:19 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681144,2017-04-11 04:00:41 UTC,ubiquity-slideshow-ubuntu (124) zesty; urgency=medium
1681144,2017-10-19 01:36:13 UTC,Just encountered this bug in my test of Kubuntu i386.
1681155,2017-05-04 14:55:32 UTC,"While we could ""validate"" (basically re.compile()) a regular expression both on the client side before making a request and on the server side before executing a DB query, that would only give us so much - the problem is that we pass this regular expression to MySQL as is and we can't guarantee that something valid in Python RE is going to be valid in MySQL as well."
1681155,2017-04-15 13:10:51 UTC,"Roman, could you please take a look? It looks like a general issue of all the versions of novaclient. Though, I'm not sure if it is even possible to ""validate"" a regular expression, but may be some sort of sanitizing of inputs..."
1681170,2018-05-08 18:05:32 UTC,This change was made by a bot.
1681173,2017-04-17 09:00:13 UTC,"Weird, I tried to reproduce this by setting my keyboard layout to Lithuanian, but everything worked correctly. See the attached screenshot."
1681173,2017-04-17 09:17:38 UTC,I suspect this depends on your _default_ (main) keyboard layout. Try setting it to Lithuanian and then logging in anew.
1681173,2017-08-10 19:46:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681173,2017-08-10 19:47:11 UTC,I am having the same issue with Xubuntu and a default French BÉPO layout.
1681176,2017-04-09 07:23:50 UTC,added screenshot
1681176,2017-04-09 08:12:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681190,2017-04-17 03:08:47 UTC,Does this happen on systemd git?
1681190,2017-06-22 15:59:41 UTC,I assume I shall do this if this issue appears again with a damaged disc. If I have one again in the future I'm attaching the output in case I don't forget it then.
1681190,2017-04-17 17:35:09 UTC,Difficult to tell as I'm normally always using the packaged systemd from the official Ubuntu repository but as I'm on the development version of Ubuntu it should be more or less recent. Otherwise I have to wait until a version >= the current git lands into the repository to test it.
1681190,2017-06-22 12:52:29 UTC,"Use kernel parameter ""systemd.log_level=debug"", then attach output of `journalctl -b` here."
1681195,2017-09-26 02:22:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681200,2017-04-24 15:02:45 UTC,revno: 863
1681200,2017-04-23 11:46:04 UTC,Just did a few tests with the new revision and haven't experienced any crashes. Thanks!
1681200,2017-04-23 05:52:01 UTC,"Haven't been able to pinpoint the initial crashes, but did patch the application startup to be more robust after a crash. This means the ""--standalone"" option should no longer be needed when restarting."
1681200,2017-04-20 08:23:20 UTC,"'Zim -D' output of a crash, attempted restart and error dialog attached:"
1681200,2017-04-19 22:55:40 UTC,"Hi Jaap,"
1681200,2017-04-09 11:48:56 UTC,"Hi, just to inform that after a full system restart, Zim is not crashing at startup anymore."
1681200,2017-04-19 03:08:55 UTC,"I'm experiencing this same bug in r847 (also had it in r842) on Xubuntu 14.04.5. The scenario that seems to trigger it for me is that if I click on a link that opens a file in another program (usually PDFs in Evince, spreadsheets in LibreOffice), Zim will crash while I'm looking at the other file. So, I think it might be something to do with Zim being pushed into the background."
1681200,2017-04-18 18:45:33 UTC,Will look into making startup more robust.
1681200,2017-04-10 08:46:32 UTC,"Another update. After system restart Zim works, but as soon as it crashes, it cannot start any longer (same error as above)."
1681200,2017-05-02 13:22:18 UTC,"Hi, Jaap"
1681200,2017-04-28 11:57:18 UTC,"revno: 868
Now can re-open closed notebook - OK.
BUT:
Zim is very unstable during start, takes a lot of CUP. I can't do anything till CUP will be down - otherwise Zim crashes.
Still have crashes when a file opened with another app from the Attachment Browser."
1681200,2017-04-19 04:54:53 UTC,"Could you run zim with the -D option and check the output in the terminal
when it crashes?"
1681200,2017-05-02 08:08:33 UTC,See also https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/7
1681210,2017-12-20 08:16:05 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/f29dd1e48e0d4c79dde7164f395c849006dcb066"
1681210,2017-10-30 16:03:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1681210,2017-07-28 19:41:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681210,2017-04-09 11:40:59 UTC,"StacktraceTop:
 _cogl_check_extension (name=0x562119985d90 ""GLX_EXT_texture_from_pixmap"", ext=ext@entry=0x0) at cogl.c:75
 _cogl_feature_check (renderer=renderer@entry=0x562119a08450, driver_prefix=driver_prefix@entry=0x7ff19daaec1b ""GLX"", data=data@entry=0x7ff19dcd0d18 <winsys_feature_data+56>, gl_major=<optimized out>, gl_minor=<optimized out>, driver=driver@entry=COGL_DRIVER_GL, extensions=0x0, function_table=0x562119afe000) at cogl-feature-private.c:128
 update_base_winsys_features (renderer=0x562119a08450) at winsys/cogl-winsys-glx.c:692
 _cogl_winsys_renderer_connect (renderer=0x562119a08450, error=<optimized out>) at winsys/cogl-winsys-glx.c:794
 cogl_renderer_connect (renderer=0x562119a08450, error=0x7ffffcbb1430) at cogl-renderer.c:687"
1681235,2017-04-09 17:03:24 UTC,"sudo apt-get install linux-generic-hwe-16.04-edge
wget http://mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.161.1_all.deb
sudo dpkg -i linux-firmware_1.161.1_all.deb"
1681235,2019-03-27 03:02:44 UTC,"Seeing this Ubuntu Bluetooth 'Bastien's Computer' Bug in my latest Zorin install...
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1571262"
1681244,2017-07-08 01:33:27 UTC,I can confirm bug still present in Ubuntu 17.04 (mdadm version unchanged)
1681248,2017-04-09 20:03:41 UTC,"Lubuntu control center just calls external tools.
So in this case it is calling ""nm-connection-editor""
So can you check if that is executing for you at all?
Just type it in a terminal. If it does not start for you then it might be a bug in that component (network-manager-gnome)"
1681249,2017-10-20 18:50:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681249,2018-09-24 16:32:05 UTC,It is happening for me in Ubuntu 18.10.
1681252,2017-04-09 19:55:21 UTC,Certaines distributions fournissent PyQt5 en paquets séparés.
1681252,2017-04-09 23:37:10 UTC,"merci pour la réponse.
Sous arch, j'ai l'ensemble de ces paquets d'installés :"
1681252,2018-09-28 18:54:51 UTC,On peut fermer ?
1681262,2017-04-10 15:08:32 UTC,"Yes, that's the kind of email we are constantly receiving."
1681262,2017-04-10 08:46:12 UTC,Searching launchpad.net/people for the first part of the e-mail address reveals that this person has had a Launchpad account since 2006.
1681262,2017-04-10 01:41:06 UTC,"Gunnar Hjalmarsson:

> An example of such a message (the full source) might be helpful.
"
1681262,2017-04-09 23:00:21 UTC,Maybe I misunderstood the nature of the problem. An example of such a message (the full source) might be helpful.
1681262,2017-04-09 21:20:16 UTC,"Gunnar Hjalmarsson:

> Bouncing spam is a very bad idea.
"
1681262,2017-04-09 19:42:45 UTC,"On 2017-04-09 21:25, Alberto Salvia Novella wrote:

> I have opened the following request, in case you wanted to join the
> conversation:
>
> (https://bugs.launchpad.net/launchpad/+bug/1681262)
"
1681294,2017-04-11 09:00:54 UTC,"It's a rather big change for a non-functional issue - by big I mean this change *could* potentially affect all the places where pthread_create was normally called. But seeing that the change had some testing time already and considering how this affects the snappy user experience, I'll be accepting the packages to the stable releases."
1681294,2017-04-11 09:05:57 UTC,"Hello Michael, or anyone else affected,"
1681294,2017-04-11 11:00:49 UTC,Waiting with the xenial upload as the yakkety one seems to have FTBFS on some archs. Michael said he'll fix that - don't want to risk the xenial upload in this case.
1681294,2017-04-12 02:55:22 UTC,I've fixed that and uploaded new versions.
1681294,2017-04-13 15:19:23 UTC,"Hello Michael, or anyone else affected,"
1681294,2017-04-13 15:37:55 UTC,"Hello Michael, or anyone else affected,"
1681294,2017-04-18 00:29:35 UTC,"It turns out that the new golang-1.6 breaks ABI (thanks to an upstream bug I've now fixed, but that's no help here) and so would require rebuilding a chain of dependencies to make yakkety-proposed installable again. This doesn't seem worth the effort for this bug, so we've removed the package from yakkety-proposed."
1681294,2017-04-18 01:06:14 UTC,"That said, the package from xenial-proposed does work fine (the test case program produces no output when run 100000 times). I also used the proposed package to rebuild lxd and gave the rebuilt packages a quick test and they worked fine too."
1681294,2017-04-25 13:04:47 UTC,This bug was fixed in the package golang-1.6 - 1.6.2-0ubuntu5~16.04.2
1681294,2017-04-25 13:04:52 UTC,"The verification of the Stable Release Update for golang-1.6 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1681295,2018-02-08 01:13:09 UTC,"@nstommel  thanks for this, this was the single thing preventing me from Ubuntu ... thank you again :)"
1681295,2017-09-01 12:30:20 UTC,The issue was reported upstream and they commented
1681295,2017-09-20 02:26:16 UTC,Debian package for network-manager-openvpn-gnome built for Ubuntu 17.04 attached.
1681295,2017-04-28 22:19:28 UTC,"Thanks for the confirmation Will, glad to see that it works. And yeah I think this bug should be marked urgent because without the patch, my vpn connection drops in the same manner every ten minutes or so. The rationale behind not passing auth-nocache seems pretty clear to me based on the openvpn man pages."
1681295,2017-09-20 02:25:36 UTC,Debian package for network-manager-openvpn built for Ubuntu 17.04 attached.
1681295,2017-04-28 07:00:04 UTC,Patch fixes the problem entirely.
1681295,2017-04-10 04:26:35 UTC,"The attachment ""The following patch removes the single offending line which causes this issue."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1681295,2017-04-28 06:59:23 UTC,Can this be marked as urgent? This is a *huge* problem! I can confirm the attached patch resolves disconnects every 10 minutes for me completely (been up 24 hours so far).
1681295,2017-04-10 01:42:06 UTC,Additional generated built patched package network-manager-openvpn-gnome
1681295,2017-04-10 01:40:15 UTC,Built patched package.
1681295,2017-04-28 06:59:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681302,2017-04-10 11:22:24 UTC,could you attach the relevant svg files and/or images for testing purposes?
1681302,2017-04-10 17:13:07 UTC,"Thanks again for looking in to this as well, I attached a file where I just
clipped an item and this happened.  In fact it happens on every clip I've
done so far.  On this file I clipped my background group to fit my page
size.  My process was as follows"
1681304,2017-04-10 11:26:07 UTC,thank you for taking the time to file a report!
1681304,2017-04-10 16:59:08 UTC,"Thanks for looking at this.  I attached a file with (invisible) flowed text
high at the top.  The only way to find it on screen is to 1) Zoom to page
view 2) Lasso all of the empty white space you should be seeing above the
color bar.  3) Info bar should read that you have 9 objects of flowed text
in layer 1."
1681304,2017-04-10 23:31:43 UTC,"The file 1530-Lavender-Micellar-Water-Wavy.svg  already has the misplaced objects, when opened in 0.91."
1681304,2017-04-18 15:42:30 UTC,"Hi,"
1681320,2017-06-20 04:59:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/475648"
1681320,2017-06-13 07:52:33 UTC,"IMO a spec is required to discuss how ironic vs inspector PCI-alias mapping should be shared.
So far 2 options were suggested that deserve more detailed description:
* extend the API of the inspector to contain the mapping
* let the ironic's inspector inspection interface post-process the mapping"
1681320,2017-06-13 07:45:14 UTC,Adding transcripts from the meeting: http://eavesdrop.openstack.org/irclogs/%23openstack-meeting-3/%23openstack-meeting-3.2017-06-12.log.html#t2017-06-12T17:54:31
1681320,2017-06-06 02:37:09 UTC,"Since inspector already adds it in capabilities field, it should be fine for OOB inspection to add the pci data to capabilities insted of any other field. It will essentially follow the same spec as implemented in inspector. https://github.com/openstack/ironic-inspector-specs/blob/master/specs/generic-pci-resource.rst"
1681320,2017-04-13 20:22:27 UTC,Inspector already discovers PCI devices so this RFE is to allow OOB inspection to discover the same.
1681320,2017-04-11 17:16:28 UTC,I might suggest you combine this with 1680780 and address it in a single spec.
1681320,2017-04-20 07:33:05 UTC,"To add on Wanyen's comment, Inspector has the spec implemented https://github.com/openstack/ironic-inspector-specs/blob/master/specs/generic-pci-resource.rst for the PCI devices discovery. The solution now will sit in ironic instead of ironic-inspector to allow OOB inspection to do the same."
1681330,2018-12-31 11:29:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681331,2017-04-10 11:18:53 UTC,"You are right, now I tested myself and it indeed doesn't work."
1681331,2017-04-10 08:57:23 UTC,"This is possible with a corresponding setting, see attached screenshot."
1681331,2017-04-10 09:45:05 UTC,This setting does not work for me. Try:
1681331,2017-04-10 09:45:30 UTC,s/Moving is pasted/Nothing is pasted
1681331,2017-04-10 10:13:13 UTC,Sounds like this bug: https://bugs.launchpad.net/shutter/+bug/1592871 Could you check if copying to clipboard works if autosaving is on?
1681331,2017-04-10 10:45:57 UTC,"No, still doesn't work for me."
1681338,2019-11-29 06:26:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/696639"
1681338,2019-11-13 05:18:48 UTC,"We also face this issue, when kuryr is used along with multus, and a vif might not be requested from kuryr for some pods."
1681338,2017-08-01 16:09:43 UTC,I like the 2 option more.
1681338,2017-06-23 03:16:06 UTC,"Yes, we also have this requirement.
In a kubernetes ready environment, if we deploy kuryr later when needed, then some existing pods/LB would cause a lot
of error , kuryr controller get incorrect pod/LB info from those already existing pods/LB, then some times we can find kuryr-k8s crashed at last."
1681338,2017-08-01 15:55:38 UTC,@longfei.zhang @kzaitsev
1681340,2017-04-10 08:08:52 UTC,"Forgot to mention that the error log does not display anything, it only displays the duplicate transaction when the slave was restarted manually after the crash."
1681340,2018-01-25 08:42:31 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3683
1681345,2017-06-09 15:35:08 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1681345,2017-06-27 15:14:14 UTC,"Reviewed:  https://review.openstack.org/455167
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=41dc35dc3145ad8933a9bf6a5f0580a85810a317
Submitter: Jenkins
Branch:    master"
1681345,2017-06-02 10:10:45 UTC,"Reviewed:  https://review.openstack.org/455166
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=15543949b118ec30fcc1bbfc4c2f6d9188ef7664
Submitter: Jenkins
Branch:    master"
1681345,2017-04-10 08:57:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/455166"
1681345,2017-04-10 08:57:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/455167"
1681358,2017-04-10 12:28:31 UTC,"Exception during installation:
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py: Traceback (most recent call last):
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 1770, in <module>
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:     install.run()
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 78, in wrapper
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:     func(self)
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 192, in run
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:     self.configure_python()
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 336, in configure_python
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:     cache = Cache()
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:   File ""/usr/lib/python3/dist-packages/apt/cache.py"", line 107, in __init__
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:     self.open(progress)
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:   File ""/usr/lib/python3/dist-packages/apt/cache.py"", line 151, in open
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:     self._cache = apt_pkg.Cache(progress)
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py: SystemError: W:Unable to read /target/etc/apt/sources.list.d/ - DirectoryExists (2: No such file or directory), W:Unable to read /target/etc/apt/sources.list - RealFileExists (2: No such file or directory), E:Could not open file /target/var/lib/dpkg/status - open (2: No such file or directory), E:The package lists or status file could not be parsed or opened.
Apr 10 10:56:48 soukaina-System-Product-Name /plugininstall.py:"
1681372,2019-02-13 19:00:08 UTC,Also Newton is EOL.
1681372,2017-04-10 09:47:06 UTC,"Fair point, I think we should have (at least best effort) a way for users to have their own ansible."
1681372,2017-04-10 09:49:57 UTC,"However, if the deployer is using its own ansible, we should also assume that (s)he will make sure the roles are available, and the proper variables are used. So the bootstrap ansible shouldn't be used in that case IMO."
1681372,2017-04-10 09:51:04 UTC,"Also the link of your bug is, I think, incomplete."
1681372,2017-04-10 10:11:39 UTC,How is it incomplete?
1681372,2017-04-11 16:08:54 UTC,"The bug is not incomplete, I meant the first link is just a link to ARA, not a link to a bug there :)"
1681372,2017-04-11 16:21:31 UTC,"Ok we need to adapt our bootstrap ansible script to be more resilient for that case, and add a  test of the minimum ansible version required for our builds."
1681372,2019-02-13 18:03:24 UTC,"I just tested this against master and Queens, seems this issue has been resolved. Please re-open if you are seeing this again."
1681381,2017-04-10 10:52:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/455242"
1681404,2018-02-28 16:35:56 UTC,This is addressed by commit:
1681404,2019-09-23 13:58:21 UTC,"As noted in the previous comment, this bug was fixed in the 2.11 release."
1681421,2017-04-10 21:34:40 UTC,The apparmor denial fix is committed in master and should be in 2.24.
1681421,2017-04-10 13:16:48 UTC,"this super simple rust program also fails, but only in classic mode: https://is.gd/wDGfHt"
1681421,2017-04-10 15:40:50 UTC,https://github.com/snapcore/snapd/pull/3161#pullrequestreview-31879751
1681421,2017-04-10 12:55:24 UTC,"This particular denial is typically caused by debugging output. I'll add this to the snap-confine profile, but in the meantime, can you add to /etc/apparmor.d/usr.lib.snapd.snap-confine:"
1681421,2017-04-10 13:05:18 UTC,"Adding this line removes the dmesg error, the snap still is unresponsive though"
1681428,2017-05-18 16:53:13 UTC,"Hi, Ubuntu will close the Store soon. Please, migrate to the openstore for
receiving updates for the phone and apps.
A hug.
open.uappexplorer.com"
1681428,2017-04-16 15:05:12 UTC,"Alright. Thanks a lot
Best regards"
1681428,2017-04-13 08:22:38 UTC,"Hi, I am waiting for a response from the OSM tile server admin. If not, we
don't have an OSM alternative.
Best regards."
1681428,2017-04-13 08:08:56 UTC,"Is there a chance to get the OpenStreetMaps back? They look better compared to the mapbox ones.
If not, it's ok anyway:)"
1681428,2017-05-18 16:28:16 UTC,"I can find an address using uNav, but the map OpenStreetMaps does NOT load. It stays Gray. When I switch to Stamen (or some other source), it works fine. See attached screenshot."
1681428,2017-04-10 13:49:44 UTC,"Thanks, choosing another map provider works! (but they don't look as nice as Open Street Map)."
1681428,2017-04-10 13:35:28 UTC,"Thanks for the feedback Tomas!
It's not the version of uNav, the map provider is down from yesterday.
Please, choose another map in the Settings.
Best regards."
1681428,2017-04-10 13:56:26 UTC,Try mapbox ;)
1681461,2020-06-14 11:05:17 UTC,On CentOS 7 the file is /lib/udev/rules.d/80-kvm.rules provided by qemu-kvm(-ev) package but it sets permissions to 0666 so that everyone can use /dev/kvm.
1681461,2020-06-13 18:23:39 UTC,"OK, I triaged this issue."
1681461,2020-06-13 18:26:07 UTC,"Oh, it seems we can actually tell systemd to mask this service despite it not being installed. So we can workaround both issues in fact. Ugly but works."
1681461,2020-06-13 18:36:42 UTC,This package seems to have identical structure in both xenial (16.04) and bionic (18.04) so we would handle both this way. The package in focal seems different and lacks the udev rule part (it could be somewhere else now - to check [maybe they changed the default perms... or figured out too much magic at once is bad]).
1681461,2020-06-13 19:06:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/735441"
1681461,2020-06-13 19:09:18 UTC,"Please let me (us) know whether the above fix works for you. That said, it might be a little tricky to backport to something older than Train."
1681461,2020-06-01 16:20:23 UTC,going to triage this
1681461,2020-06-13 19:24:13 UTC,It seems this patch fixes centos analogically as it too can have an udev rule making /dev/kvm usable by host-level libvirt instead of kolla one.
1681461,2020-06-14 13:22:30 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/735463"
1681461,2020-07-22 15:58:12 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/742471"
1681461,2020-07-22 12:32:46 UTC,"Reviewed:  https://review.opendev.org/735441
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=202365e70213fe7f23d1d618789e356e24ed0679
Submitter: Zuul
Branch:    master"
1681461,2020-07-22 15:54:18 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/742466"
1681461,2020-07-22 15:54:33 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/742467"
1681461,2020-07-23 10:21:40 UTC,"Reviewed:  https://review.opendev.org/742466
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=6a6ee3df294f38cbba98f4a34a7ac182e8abce71
Submitter: Zuul
Branch:    stable/ussuri"
1681461,2020-07-24 10:25:09 UTC,"Reviewed:  https://review.opendev.org/742467
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=574257dc2eb5a0fe9031e7aa0bb79ff0851526c6
Submitter: Zuul
Branch:    stable/train"
1681461,2020-07-24 16:14:47 UTC,"Reviewed:  https://review.opendev.org/742471
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=b0667666262ccb60efddf66126284e2f24e98ccd
Submitter: Zuul
Branch:    stable/stein"
1681461,2020-11-24 21:43:37 UTC,This issue was fixed in the openstack/kolla-ansible 8.3.0 release.
1681461,2021-01-07 17:11:58 UTC,This issue was fixed in the openstack/kolla-ansible 10.2.0 release.
1681461,2021-01-07 17:15:19 UTC,This issue was fixed in the openstack/kolla-ansible 9.3.0 release.
1681461,2020-06-14 16:28:13 UTC,"Change abandoned by Radosław Piliszek (<email address hidden>) on branch: master
Review: https://review.opendev.org/735463
Reason: and thus the fix is confirmed to work"
1681461,2020-05-18 22:48:43 UTC,I realized what the problem is.
1681461,2020-04-15 15:04:21 UTC,It seems to be reproducible roulette-style. ;-)
1681461,2020-04-16 13:45:03 UTC,"I rebooted and applied a fix above, worked for me."
1681461,2017-04-10 14:33:59 UTC,This seems to have caused the issue:
1681461,2017-05-16 09:38:43 UTC,"Mohammed, still working in this issue? This is causing Ubuntu KVM to be broken? If so let me know to change Importance to Critical. No other user reported such issue.
Regards"
1681461,2017-06-14 09:37:47 UTC,"I had this exact issue. After few hours of debugging, it seems that the problem wasn't a use/group issue, but rather a nested environment issue."
1681461,2017-07-17 15:27:23 UTC,"I ran a multinode deployment (ocata 4.0.0) on baremetal, and I ran into this issue again. To solve the problem, I had to change the permissions to /dev/kvm on one of the compute nodes where the VMs are failing to boot:"
1681461,2017-09-01 22:41:51 UTC,Same issue here. Running this command on the hypervisor solved this issue (not in the container)
1681461,2020-05-18 20:47:42 UTC,I've been running OpenStack Kolla since beginning of April on the same hosts without this problem.
1681461,2019-05-06 09:33:54 UTC,"Hi Team,"
1681461,2019-05-07 17:57:45 UTC,"It's odd that only some people are seeing this. Perhaps only some people are using KVM on ubuntu? Surprising though, given that's the default."
1681461,2019-06-25 13:30:13 UTC,This issue is on both ubuntu 16.04 and 18.04 . Its a critical bug.please give any solution.
1681461,2018-09-07 19:47:48 UTC,There is similar issue on Ubuntu 18.04.  /dev/kvm is owned by root:kvm.  Doing the chgrp on /dev/kvm only provides a temporary fix.  Something in the system reverts the group back to kvm.  Plus the kvm group on the hypervisor host is gid:113 and the kvm gid in the nova_libvirt container is gid:106.
1681461,2019-07-09 13:17:16 UTC,"I tried an ubuntu/binary deploy using kolla/kolla-ansible master branch, with virt_type KVM. I was able to boot an instance. I have the following perms on /dev/kvm:"
1681461,2019-07-09 13:49:44 UTC,I rebooted the openstack all-in-one controller/compute node and after starting the nova instance again it's back up.
1681461,2019-07-17 14:23:45 UTC,"I'm also running on this issue.
In our case compute node a virtual instance based on Ubuntu 18.04 with nested virtualization enabled."
1681461,2019-08-01 05:02:50 UTC,In that environment:
1681461,2019-08-01 05:10:49 UTC,About my post above OS on compute hosts is Ubuntu 18.04.
1681461,2019-08-09 03:36:14 UTC,I would add a doc section to troubleshooting this bug as a tempory fix.
1681461,2019-10-02 22:51:12 UTC,This also reproducible in OpenStack Rocky on Centos7.6 as host.
1681461,2020-04-15 09:15:57 UTC,Its also up to Train reproductible.
1681461,2019-06-25 13:33:37 UTC,please assign this bug to anyone else @Eduardo Gonzalez. It needs to be resolved early
1681469,2017-05-16 10:43:17 UTC,This bug was fixed in the package linux - 4.8.0-52.55
1681469,2017-04-10 16:05:16 UTC,"Leann,"
1681469,2017-04-12 11:58:19 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-April/083582.html
1681469,2017-04-13 13:47:04 UTC,Actually 4.4.60 upstream included this for Xenial.
1681469,2017-05-03 16:56:06 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1681474,2017-04-11 19:35:51 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1681477,2020-02-25 08:25:38 UTC,"Marking this as Invalid, considering Lilyana said it wasn't an issue anymore."
1681477,2019-04-03 13:45:22 UTC,not an issue anymore
1681494,2018-05-08 18:05:55 UTC,This change was made by a bot.
1681494,2021-01-07 04:17:00 UTC,4.8 EOL
1681495,2017-04-10 16:13:31 UTC,"is it just a matter of setting no-proxy appropriately instead of explicitly
a different proxy?"
1681495,2017-04-10 16:32:33 UTC,"As is being tracked here https://bugs.launchpad.net/juju/+bug/1488139 that's a separate issue, and would require juju to add ALL IP's it is managing to the no_proxy."
1681495,2017-04-12 08:27:40 UTC,"As an added note, it seems openstack ignores no_proxy, so I have a setup where I need to set http-proxy for lxd to get images, and then remove it for openstack to come up."
1681504,2017-06-05 05:22:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681519,2019-07-03 17:34:11 UTC,This can go into the capacity tracking spreadsheet if we want to track it.
1681519,2017-04-10 17:34:40 UTC,There is also https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer
1681544,2019-04-23 19:39:48 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1681544,2019-06-23 04:18:57 UTC,[Expired for totem (Ubuntu) because there has been no activity for 60 days.]
1681552,2017-04-10 20:26:58 UTC,Minimal code and sample image to reproduce error.
1681552,2017-07-04 13:07:05 UTC,Same here... Also with 16.04.02
1681562,2017-04-10 22:48:28 UTC,It seems like the use of the cache @ https://github.com/openstack/mistral/blob/master/mistral/workflow/lookup_utils.py#L62 to get upstream task executions leads to getting the wrong in_context.
1681570,2017-07-23 13:25:47 UTC,Please install the corresponding -dbgsym packages and provide a backtrace of the crash.
1681570,2017-07-25 02:23:48 UTC,"it doesn't ""crash"".  play aborts, behaving as if the video played to the end.  if a backtrace would be useful at that point, please drop a pointer how to trigger it."
1681571,2017-09-18 22:15:53 UTC,To handle this we will need to recognise the .svg as an 'image' file but will need to handle slightly  differently as we won't need to make thumbnails of it as we can just supply it with dimensions to achieve that.
1681571,2019-11-03 03:24:19 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10554"
1681571,2019-11-03 03:29:57 UTC,For things to translate/scale one needs to have the svg markup like so:
1681571,2020-05-12 20:45:16 UTC,"Hi Robert - a couple of smaller things that may or not be issues:
1. When image block created/edited:
1.1 filename is displayed when Description is selected (instead of entered description)
1.2. file preview is not displayed in the Details & comments sidebar.
2. Should animated SVGs still display as animated ?  I have not had one display as expected and a couple cause errors.
And one bigger one:
3. Deleting svg files (maybe just animated ones) via the File Manager cause errors to display on both the Files home page and also sometimes on page/s that used to use a deleted file.  I'm investigating this further and have pasted this comment into the launchpad ticket with a zip file containing a screenshot of the Files error and several test svg files (different types: plain, with transforms & animated).  Will add further detail when I have it."
1681571,2020-09-05 06:28:09 UTC,We decided not to implement this after all because it is too dangerous securitywise to allow anybody to upload a SVG file because malicious code can be embedded.
1681573,2018-08-31 04:33:03 UTC,"This is an extension of bug #1681571, allowing the upload of SVG."
1681600,2017-08-06 11:14:02 UTC,"I think this problem is because of this line:
https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/debootstrap/install.d/10-debian-networking#L25"
1681609,2019-09-09 05:43:09 UTC,"It's a pity that this link no longer works, pasting offending stack trace would have been so much more lasting."
1681620,2017-11-07 02:30:24 UTC,"I'm using with Senlin version Pike/4.0.0, and still get the same issue when trying to test this guide:
https://docs.openstack.org/senlin/ocata/scenarios/autoscaling_heat.html"
1681620,2018-02-07 01:24:28 UTC,"Reviewed:  https://review.openstack.org/532641
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=957d77a0a9a5e6904011ecc38eac99192b66f31d
Submitter: Zuul
Branch:    master"
1681620,2018-02-04 02:25:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/540625"
1681620,2017-11-20 03:29:48 UTC,"@tengqim: I tried removing the ""bindings"" property of lb_policy definition in Heat template, and Senlin Cluster would be created successfully. So, it seems likely that the issue is about LB policy attachment."
1681620,2017-11-14 11:15:21 UTC,"@manthang, I'm suspecting that there are bugs when attaching a LB policy to your cluster.
Can you help check if things work when we avoid LB policy?"
1681620,2018-02-07 01:32:07 UTC,"Change abandoned by Qiming Teng (<email address hidden>) on branch: master
Review: https://review.openstack.org/540625
Reason: All covered by #532641"
1681620,2017-07-08 15:16:09 UTC,"Yes, Thiago. I think what you met have two bugs:
1.The first one is the problem about schedule: https://bugs.launchpad.net/senlin/+bug/1682002
2.And the second is about cluster/node lock problem. Which is cause when you restart you senlin engine.
The second problem need to be solved by a patch."
1681620,2017-07-06 02:28:18 UTC,"@Thiago, which version are you using?"
1681620,2017-07-07 15:43:31 UTC,"I applied the above patch but it still can't lock the cluster, so, it is not detaching the policies."
1681620,2017-07-07 15:25:44 UTC,"This bug is the same with under:
https://bugs.launchpad.net/senlin/+bug/1682002"
1681620,2017-07-07 15:23:52 UTC,https://review.openstack.org/#/c/456048/
1681620,2017-07-07 15:01:15 UTC,"@Qiming,"
1681620,2017-07-05 20:18:37 UTC,"Guys,"
1681620,2017-07-07 19:00:48 UTC,"I cleaned up the Senlin SQL database, something like:"
1681627,2019-01-09 03:28:38 UTC,"In fact, backporting two primitive patches [1][2] into Ocata will not be able to work, because:"
1681627,2019-04-29 18:01:33 UTC,@zhhuabj it looks like upstream stable/ocata is still in extended maintenance mode. Would you be able to submit the patch to stable/ocata?
1681627,2019-01-09 03:51:04 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/629373"
1681627,2019-01-09 03:57:02 UTC,Submit two dependent submissions as below:
1681627,2019-03-20 21:49:58 UTC,"Reviewed:  https://review.openstack.org/629373
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f557a8dd34e91b60de2f4a192aad3a0861b4b5ac
Submitter: Zuul
Branch:    stable/ocata"
1681627,2019-04-02 08:45:11 UTC,Pike patch will be included in PR done in bug 1822192
1681627,2019-04-15 13:48:35 UTC,"@zhhuabj my apologies, the PR i mentioned above is for Cinder not Horizon so we will need to submit an SRU for Pike as well."
1681627,2019-04-22 08:09:03 UTC,"@Ed, the branch 12.0.3 has included those two fixed patches, so horizon pike 3:12.0.3-0ubuntu1~cloud1 released on Apr 2 has included them."
1681627,2019-04-29 12:15:42 UTC,"@zhhuabj ack thanks, lets get the ocata sru underway then"
1681627,2019-05-06 10:06:11 UTC,"@corey, yeah, I have submitted the patch to stable/ocata before, see https://bugs.launchpad.net/horizon/+bug/1681627/comments/27, and they have already been merged by upstream as well now. thanks."
1681627,2017-08-11 20:48:48 UTC,This issue was fixed in the openstack/zun-ui 0.2.0 release.
1681627,2019-05-13 20:57:52 UTC,"@Hua, sorry I'm confused on what's needed for Ocata."
1681627,2019-05-14 10:07:47 UTC,"@corey,"
1681627,2019-06-03 17:41:14 UTC,"I was confused by the bug description because it sounded like there were 3 patches required, but it looks like just the 2 are required. Also for pike I was confused because the ""# add URL for ngdetails"" bits were missing but they are removed by the other patch so pike looks ok."
1681627,2019-06-03 17:45:57 UTC,s/missing/moved/
1681627,2019-06-03 18:34:31 UTC,"Hello hongbin, or anyone else affected,"
1681627,2019-06-10 06:12:44 UTC,"Successfully verified ocata-proposed openstack-dashboard=3:11.0.4-0ubuntu1~cloud2.6, it works, thanks."
1681627,2019-06-10 14:44:03 UTC,The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1681627,2019-06-10 14:44:06 UTC,"This bug was fixed in the package horizon - 3:11.0.4-0ubuntu1~cloud2.6
---------------"
1681627,2018-12-12 14:23:00 UTC,I added ocata-backport-potential tag so that anyone who is interested in stable/ocata can verify a fix in stable/ocata and propose a backport.
1681627,2019-05-13 20:40:54 UTC,"@Hua, thanks I somehow missed that last time. By the way I don't think this fix landed in our pike package. At least I did a quick grep for ""ngdetails"" and didn't find the first LOC from the stable/pike upstream patch. Anyway Pike is EOL now but we should at least change the status above from Fix released to won't fix."
1681627,2018-12-01 22:47:27 UTC,"Everyone can propose a backport to stable branches. Feel free to propose a backport to ocata.
Ocata is entering the extended maintenance phase, so we are looking for volunteers to maintain stable/ocata branch."
1681627,2017-08-04 06:42:12 UTC,This could be reopened because of the revert under review: https://review.openstack.org/490131. Or do we open a new bug after a revert?
1681627,2018-05-08 13:17:18 UTC,This issue was fixed in the openstack/horizon 12.0.3 release.
1681627,2017-06-26 08:32:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477447"
1681627,2017-06-26 09:06:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477461"
1681627,2017-07-29 06:59:23 UTC,"Reviewed:  https://review.openstack.org/477447
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=fe0df4579cd091caa49a5a0a14bc3b3d93bcd1a4
Submitter: Jenkins
Branch:    master"
1681627,2017-07-29 11:29:33 UTC,"Reviewed:  https://review.openstack.org/477461
Committed: https://git.openstack.org/cgit/openstack/zun-ui/commit/?id=7bee55d9258c67de922c656e2428522c6f9b36da
Submitter: Jenkins
Branch:    master"
1681627,2018-11-30 15:00:22 UTC,"This issue is affecting also openstack/horizon 11.0.4 release (Ocata)
We need a backport of the bug fix."
1681627,2017-08-07 05:48:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491346"
1681627,2017-08-10 20:52:47 UTC,This issue was fixed in the openstack/horizon 12.0.0.0rc1 release candidate.
1681627,2017-08-23 06:37:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496511"
1681627,2017-09-01 08:42:35 UTC,"Change abandoned by Shu Muto (<email address hidden>) on branch: master
Review: https://review.openstack.org/496511
Reason: Due to another idea, I will implement in original patch: https://review.openstack.org/#/c/491346/"
1681627,2017-08-07 06:00:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491349"
1681627,2018-02-01 10:51:05 UTC,"We discussed the plan on this bug in the horizon team meeting. The conclusion is we will land only https://review.openstack.org/#/c/520340/ (which just allows refresh) in Queens and discuss how to recover navigation in Rocky.
Based on this, this bug will be closed by https://review.openstack.org/#/c/520340/ and the latter will be tackled as a separate bug."
1681627,2017-11-16 08:19:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520340"
1681627,2018-02-15 05:59:34 UTC,"Reviewed:  https://review.openstack.org/541676
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a0fc40b4e85d3090e657cca9824de719b33a7ba2
Submitter: Zuul
Branch:    stable/pike"
1681627,2018-02-09 07:19:28 UTC,This issue was fixed in the openstack/horizon 13.0.0.0rc1 release candidate.
1681627,2018-02-07 11:21:24 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/541676"
1681627,2018-03-12 20:45:31 UTC,the fixes cause problem at https://bugs.launchpad.net/horizon/+bug/1754133
1681627,2018-02-01 11:02:20 UTC,there is another issue (bug 1746709) too. This also needs to be tackled later.
1681627,2018-02-01 10:51:22 UTC,bug 1746706 is filed on the navigation issue.
1681627,2018-02-05 11:36:54 UTC,"Reviewed:  https://review.openstack.org/520340
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=077163a03c9aea08efd56251e49d69eb1cc4d093
Submitter: Zuul
Branch:    master"
1681654,2018-07-12 14:02:37 UTC,I just did a fresh install of 18.04 today and I can confirm this still happens after I establish a successfully connection to an OpenVPN server.
1681654,2019-05-10 01:21:20 UTC,The required icons are available from this commit:
1681654,2019-05-29 20:06:53 UTC,This bug was fixed in the package ubuntu-mate-artwork - 19.10.2
1681676,2017-05-05 00:56:16 UTC,"Yep, agreed Bernd. Thanks for logging (and noting that Identity v2 is logged in another bug)."
1681676,2017-04-11 07:21:51 UTC,"I just notice that the third point, Keystone v2, is already addressed by https://bugs.launchpad.net/openstack-api-site/+bug/1681121."
1681686,2017-04-25 12:40:13 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/459664"
1681686,2017-04-20 13:19:27 UTC,"Reviewed:  https://review.openstack.org/455721
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=402e66aca9e871e4c5b9c9d669c58db5bcd960f8
Submitter: Jenkins
Branch:    master"
1681686,2019-12-18 17:10:53 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/459664
Reason: This repo is retired now, no further work will get merged."
1681686,2017-04-11 14:08:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/455721"
1681688,2020-11-17 11:52:41 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1681688,2021-01-17 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1681688,2017-04-11 13:57:00 UTC,"Am 11.04.2017 um 15:35 hat 858585 jemmy geschrieben:

> Hi Kevin:
>    Can you provide some information about the original bug which you want fix?
>
>    the original comment:
>    Usually guest devices don't like other writers to the same image, so
>    they use blk_set_perm() to prevent this from happening.
>
>    i don't find where the dest qemu will use blk_set_perm during migration.
>    but after apply this patch, blkconf_apply_backend_options don't update the
>    blk->root->perm.
"
1681688,2017-04-11 08:21:40 UTC,blk->root->perm is 1 when blk_new_open.
1681688,2017-04-11 13:35:14 UTC,"Hi Kevin:
   Can you provide some information about the original bug which you want fix?"
1681692,2017-11-06 00:36:09 UTC,@elopio how are things on this design request? Perhaps we could work on this one some time soon?
1681692,2017-06-27 18:58:59 UTC,Thank you both :)
1681692,2017-06-27 12:57:05 UTC,https://github.com/snapcore/snapcraft/pull/1345
1681692,2017-06-28 15:46:42 UTC,"Whoops, sorry guys, looks like I jumped the gun there. Let's please be clear in the PR if the buglink isn't completely fixed by it."
1681692,2017-09-18 06:11:52 UTC,"@Carla, sorry for the late response."
1681692,2017-06-27 20:43:55 UTC,"Wait wait, with Gustavo we only made one change to send the percentage from the backend to the UI. The text is still not what Mark suggested. It currently says:"
1681692,2017-06-28 10:23:07 UTC,"Hi Leo, as far as I can tell your proposal looks sensible."
1681712,2017-04-11 10:12:23 UTC,"Turns out it isn't invalid after all.
""juju add-unit"" returns an error, but the unit ends up getting created and stays in ""allocating"" forever:
  peer-xplod/14   waiting   allocating                                     waiting for machine"
1681712,2017-04-11 10:00:43 UTC,"$ juju add-unit peer-xplod --to 2
ERROR adding new machine to host unit ""peer-xplod/9"": cannot assign unit ""peer-xplod/9"" to machine 2: series does not match"
1681712,2017-04-11 10:13:36 UTC,"$ juju retry-provisioning peer-xplod/14
error: invalid machine ""peer-xplod/14"""
1681714,2019-02-13 20:45:59 UTC,"OSA can deploy ceph via ceph-ansible, and any config overrides for ceph can be passed across as user_variables. Is there something specific preventing this happening via user_variables instead of a specific change to OSA?"
1681738,2018-05-04 13:26:55 UTC,The string that needs to change is in src/maasserver/models/node.py
1681743,2017-04-12 10:04:44 UTC,"Please attach diagnostic snapshot, marking as Incomplete."
1681743,2017-04-12 16:09:34 UTC,"Alright, here is the diagnostic snapshot. Thanks for looking into it!"
1681743,2017-04-19 13:04:35 UTC,Did you get anywhere with this bug? I'm happy to provide anything else you need to help this to be tracked down.
1681746,2017-04-11 22:52:23 UTC,Thanks for catching this Florian.  I've put a PR in to update the readme here: https://review.openstack.org/#/c/455846/.  If you'd like to jump onto the review I'd appreciate the feedback.
1681753,2017-04-11 12:02:15 UTC,"in neutron logs some traces with
UnboundLocalError: local variable 'routers' referenced before assignment
error probably caused by
https://review.fuel-infra.org/gitweb?p=openstack/neutron.git;a=commitdiff;h=4eb0437b8f52eba6b68152986801838756a0763e;hp=-c"
1681753,2017-04-15 20:05:05 UTC,"Fix proposed to branch: openstack-ci/fuel-8.0/liberty
Change author: Denis V. Meltsaykin <email address hidden>
Review: https://review.fuel-infra.org/33137"
1681753,2017-04-18 11:38:43 UTC,"Reviewed: https://review.fuel-infra.org/33137
Submitter: Pkgs Jenkins <email address hidden>
Branch: openstack-ci/fuel-8.0/liberty"
1681753,2017-04-25 09:07:40 UTC,"Checked latest runs. Test is not stable now, sometimes failed with the same error even with fix:
https://patching-ci.infra.mirantis.net/view/8.0.swarm/job/8.0.system_test.ubuntu.partition_preservation/66/testReport/(root)/cinder_nova_partition_preservation/cinder_nova_partition_preservation/"
1681753,2017-04-25 10:41:08 UTC,VM sometimes cannot obtain an IP-address. This is not persistent and needs more time to investigate. Moving to 8.0-mu-5
1681753,2017-07-11 10:56:15 UTC,So far all the subsequent tests were successful and I didn't have a chance to troubleshoot them. Moving to Incomplete until it occurs again.
1681768,2020-01-24 01:55:40 UTC,"The upstream bug (link just fixed) was rejected so ""Won't Fix""."
1681768,2020-01-24 01:54:19 UTC,"Categories don't exist anymore, unless I am mistaken?"
1681768,2017-03-11 18:43:28 UTC,You mean grouping icons in the Dash? it doesn't sound so much as a core feature but a extension.
1681768,2016-04-01 19:05:23 UTC,I think that being able to put folders on the favorite bar could be a great idea.
1681768,2017-12-19 19:02:05 UTC,"The overview (and the app launcher in particular) were discussed at the UX hackfest in London last month. The design isn't quite final yet, but there are some fixtures:"
1681768,2017-04-11 10:27:22 UTC,*** Bug 781174 has been marked as a duplicate of this bug. ***
1681769,2017-04-12 06:25:25 UTC,"May be this is something distribution-specific? I'm using Ubuntu and
their Openstack:"
1681769,2017-04-11 10:31:01 UTC,"IMO this is a neutronclient bug - we can probably work around it in heat, but all clients should always treat None values the same as not passing any value."
1681769,2017-04-11 10:39:53 UTC,"Hi Steven, if this isn't Heat's issue, nothing to be fixed. Do you suggest to reopen this bug in Neutron?"
1681769,2017-04-11 11:21:31 UTC,I think you're changing(removing) the device_owner property of Port resource when doing a stack update. So actually you are removing the device_owner from the existing port. Neutron's handling of None values is weird. Actually neutron is expecting  'None'(quoted). We've done number of these hacks for other resources and can probably do one more.
1681769,2017-04-11 11:46:07 UTC,"Hi Rabi,"
1681769,2017-04-11 12:17:30 UTC,The snippet you've pasted and the changes for update should work fine.
1681769,2017-04-11 12:33:55 UTC,"Rabi,"
1681769,2017-04-11 12:46:13 UTC,FYI there is an answer from Neutron team re this case - https://bugs.launchpad.net/neutron/+bug/1681784/ .
1681769,2017-04-11 13:24:43 UTC,"I just checked. The snippets and steps (adding ssh rule before update)you provided in comment #4 seem to work fine on master. AFAICT, there has not been any change to these resources since ocata. Please provide your template and the heat engine log."
1681769,2017-04-11 15:14:55 UTC,"Hi Rabi,"
1681769,2017-04-12 03:50:03 UTC,Actually heat should not be calling update_security_group if there is nothing else changed other than the rules for SecurityGroup resource. The fact that it's calling it with None value for 'description' is absurd. I don't know why it's happening in your setup.
1681769,2017-04-11 15:47:48 UTC,"Hi Rabi, if for some reasons you will need access to my lab - just drop an e-mail at doka@<email address hidden> and I will provide you with access credentials."
1681769,2017-04-21 10:39:53 UTC,"Dear colleagues,"
1681769,2017-04-18 09:07:38 UTC,"Hi,"
1681769,2017-04-21 19:21:38 UTC,"Thank you, Rabi. I highly appreciate."
1681769,2017-04-21 15:44:01 UTC,I checked your setup. You had the 'observe_on_update' flag set to true in your heat.conf. I reset it to false and the update works fine now.
1681769,2017-04-12 08:28:27 UTC,"Hi Rabi,"
1681769,2017-04-21 13:49:59 UTC,"Hi Rabi,"
1681769,2017-04-21 15:10:14 UTC,Here is what I see in the logs:
1681769,2017-04-21 11:25:43 UTC,"Volodymor,"
1681770,2020-01-24 01:58:10 UTC,The latest Ubuntu releases now have this feature.
1681770,2017-04-11 10:50:43 UTC,*** Bug 781176 has been marked as a duplicate of this bug. ***
1681770,2017-03-17 14:11:05 UTC,"Please, don't add any possible keywords to a bug, just to raise attention for something you are passionate about."
1681770,2017-03-17 13:54:40 UTC,I cannot believe this was never implemented in Gnome 3.x.  If I have 200 programs installed I could create and manage a folder structure to quickly locate any program in the app menu.  For some reason Gnome decided to implement a search box to find programs.
1681770,2020-01-24 01:57:18 UTC,Close this? The feature seems to exist now.
1681770,2016-05-31 20:13:30 UTC,"(In reply to Florian Müllner from comment #1)

> (In reply to Erwan Georget from comment #0)
> > As an user, I would really like to be able to more easily make application
> > folders from the overview. My idea, would be to automatically creating them
> > by drag and drop, if the app is dropped on top of another app, or add the
> > dropped app to a folder if it is dropped on it..
>
> This has been discussed several times before - the main issue is that
> drag-and-drop is awkward with pagination (and in particular when taking
> multiple monitors into account).
"
1681770,2016-05-31 13:10:21 UTC,*** Bug 767041 has been marked as a duplicate of this bug. ***
1681770,2016-04-03 11:59:29 UTC,In what ways?
1681770,2016-04-01 19:18:07 UTC,"(In reply to Erwan Georget from comment #0)

> As an user, I would really like to be able to more easily make application
> folders from the overview. My idea, would be to automatically creating them
> by drag and drop, if the app is dropped on top of another app, or add the
> dropped app to a folder if it is dropped on it..
"
1681770,2016-04-01 18:59:23 UTC,Hi
1681770,2016-05-31 21:37:51 UTC,"(In reply to Luis Henrique Mello from comment #4)

> Perhaps a right-click action could work. You can right-click on a
> application icon and select ""Add to favorites""... is an ""Add to folder""
> option viable?
"
1681776,2017-04-11 11:30:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/455667"
1681776,2017-04-13 11:31:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/456569"
1681776,2017-05-08 00:17:27 UTC,"Reviewed:  https://review.openstack.org/456569
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=c9d87b855180aa44abd9d62b2a55ced6d0fc4ea4
Submitter: Jenkins
Branch:    stable/ocata"
1681776,2017-06-09 15:35:48 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b2 development milestone.
1681776,2017-06-19 12:48:19 UTC,This issue was fixed in the openstack/kolla 4.0.2 release.
1681776,2017-04-13 11:13:11 UTC,"Reviewed:  https://review.openstack.org/455667
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=921cc029c5abd134df57c0ae706a67544d2e5fbc
Submitter: Jenkins
Branch:    master"
1681777,2019-09-19 11:56:24 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1681779,2017-04-11 11:04:42 UTC,See also https://www.percona.com/blog/2016/12/14/percona-xtradb-cluster-5-6-34-26-19-now-available/#comment-10967649
1681779,2017-04-11 11:01:09 UTC,This issue first occurred with percona-xtradb-cluster-galera-3.x 3.19-1.trusty.
1681779,2019-01-10 00:48:18 UTC,"Was just hit by this bug. Only whilst upgrading from:
percona-xtradb-cluster-galera-3.x 3.17-1.trusty > 3.28-1.trusty"
1681779,2017-04-11 16:24:10 UTC,"Hi,"
1681779,2017-04-20 08:18:09 UTC,Thanks for the update and the workaround. I'll give it a try in our testing environment. Any chance this get resolved with the percona-xtradb-cluster-galera-3.x package?
1681779,2017-04-11 13:34:31 UTC,some package mis-match issue.
1681779,2018-01-17 14:13:21 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1969
1681780,2019-09-19 11:59:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1681787,2018-01-18 08:32:34 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1970
1681788,2017-04-12 14:12:38 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681788,2017-07-02 22:18:18 UTC,This bug was fixed in the package ukui-indicators - 1.0.3-0ubuntu1
1681789,2019-09-19 11:56:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1681789,2017-06-27 18:54:24 UTC,"Since older images were never created to support python3, this is what would happen. That said, newer created images should work in both, python2/python3. As such. I'll mark this as a doc improvement to notify users."
1681790,2019-05-08 08:49:23 UTC,"I think for this we'd need a consistent format for errors from the backend. Sometimes it's a string, sometimes it's an object and the keys in that object can be different depending on the error."
1681791,2017-04-12 14:12:37 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681795,2017-07-02 22:18:13 UTC,This bug was fixed in the package ukui-menu - 1.0.2-0ubuntu1
1681795,2017-04-12 14:12:33 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681796,2017-04-12 14:12:31 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681796,2017-07-02 22:18:13 UTC,This bug was fixed in the package ukui-menu - 1.0.2-0ubuntu1
1681807,2017-04-12 14:12:25 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681813,2017-04-12 15:12:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681816,2019-03-18 10:52:09 UTC,"How is that a n-m-applet issue, what does it needs to do? (the .desktop entry has a description entry)"
1681816,2017-04-12 14:12:21 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681818,2017-06-08 11:38:18 UTC,This issue was fixed in the openstack/watcher-dashboard 1.2.0 release.
1681821,2017-04-11 12:06:04 UTC,"P.S. Feel free to call me a cheater because I ""have changed the wallpaper to the white screen"", but I didn't."
1681823,2017-04-12 14:12:19 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681823,2019-10-08 13:10:26 UTC,This bug was fixed in the package ukui-indicators - 1.1.7-0ubuntu1
1681830,2017-04-11 13:11:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681830,2018-06-04 15:11:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681830,2019-09-20 19:41:07 UTC,"The bug is still there in kubuntu 18.04.2 and it confusing.  I needed to encrypt the disk so I selected that option, but there was no indication what those boxes were for.  It was obvious they were required however since the Continue button was grayed out when selecting that option.  I finally decided it must be for passphrase entered twice, and that proved correct."
1681830,2019-10-13 14:14:23 UTC,Still here in eoan (19.10 Beta). No label for LVM Encryption passwords.
1681830,2019-10-19 20:41:00 UTC,"I face this bug in kubuntu 18.04 and 18.10
Very disappoint not encrypt the os parition because of this"
1681837,2017-04-11 12:55:59 UTC,"There are some difficulties:
- there is no registration relation between the client and the server (so it's not mandatory to have the client in the same model/environment as the server)
- to register a client with the server, configuration settings are needed, and the bundle can't know beforehand what the address of the server will be, nor what certificate it will be using
- a client can only be registered after the first admin is created in the server: before that, there is no server ""account"" yet, and no computers can be registered"
1681838,2017-04-11 16:09:14 UTC,apport information
1681838,2017-04-11 16:09:12 UTC,apport information
1681838,2017-04-11 16:09:11 UTC,apport information
1681838,2017-04-11 16:09:08 UTC,apport information
1681838,2017-04-11 16:09:09 UTC,apport information
1681838,2017-04-11 15:50:09 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1681838,2017-04-11 15:49:55 UTC,Does this issue go away if you boot back into the prior 3.13 kernel?
1681838,2017-04-11 13:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1681838,2017-04-11 16:09:15 UTC,apport information
1681838,2017-04-11 16:09:07 UTC,apport information
1681838,2017-04-11 16:09:17 UTC,apport information
1681838,2017-04-11 16:09:20 UTC,apport information
1681838,2020-03-19 20:35:49 UTC,Unrelated to kernel-package that contains tools for building a custom kernel.
1681838,2017-04-11 16:09:18 UTC,apport information
1681838,2017-04-30 21:24:09 UTC,"Re-assigning to kernel packagem possiblye the wrong one.,"
1681838,2017-04-30 15:58:24 UTC,"For the sake of order, this bug should be re-assigned to the kernel package instead of the user-space lirc package."
1681838,2017-04-11 16:46:00 UTC,"Apport for 3.13 kernel, where lirc-sir works very well."
1681838,2017-04-11 16:34:50 UTC,apport information
1681838,2017-04-11 16:15:44 UTC,This issue goes away if I boot back into 3.13 kernel.
1681838,2017-04-11 16:09:33 UTC,apport information
1681838,2017-04-11 16:34:49 UTC,apport information
1681838,2017-04-11 16:09:30 UTC,apport information
1681838,2017-04-11 16:09:29 UTC,apport information
1681838,2017-04-11 16:09:27 UTC,apport information
1681838,2017-04-11 16:09:24 UTC,apport information
1681838,2017-04-11 16:09:22 UTC,apport information
1681838,2017-04-11 16:09:21 UTC,apport information
1681838,2017-04-11 16:09:32 UTC,apport information
1681842,2017-04-18 09:21:11 UTC,failures continue on 8.0 MU-4 iso #04/17/17 14:36
1681847,2017-04-11 13:45:02 UTC,apport information
1681847,2017-04-12 13:29:34 UTC,"I've attempted to patch this out by adding checks where snat_handler and dnat_handler are called (ip_vs_core.c and ip_vs_xmit.c), with no success.  I have to surmise that either:
- My patches aren't being built correctly
- My checks don't work
- This isn't the code that's mangling the packets
- The connection table entries are being marked as MASQ connections even though they're DROUTE"
1681847,2017-04-12 10:05:57 UTC,"I think I may have tracked this down, but I haven't had a go at patching it yet."
1681847,2017-04-12 08:34:48 UTC,"I've tested this with the latest upstream kernel (4.11.0-041100rc6), and the problem is still present."
1681847,2017-04-12 08:05:17 UTC,"It's hard to tell whether this was the result of an upgrade - I think this behaviour has always been present in the 14.04 stock kernels, but we noticed it less until recently."
1681847,2017-04-11 15:48:41 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1681847,2017-04-11 13:45:00 UTC,apport information
1681847,2017-04-11 13:44:55 UTC,apport information
1681847,2017-04-11 13:44:57 UTC,apport information
1681847,2017-04-11 13:44:56 UTC,apport information
1681847,2017-04-11 13:44:51 UTC,apport information
1681847,2017-04-11 13:44:50 UTC,apport information
1681847,2017-04-11 13:30:17 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1681847,2017-04-11 13:44:54 UTC,apport information
1681847,2017-04-11 13:44:59 UTC,apport information
1681847,2017-04-11 13:44:52 UTC,apport information
1681847,2017-04-24 11:04:10 UTC,"This was reported as an upstream kernel bug:
http://archive.linuxvirtualserver.org/html/lvs-devel/2017-04/msg00014.html"
1681847,2017-04-12 13:49:35 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1681855,2017-04-11 14:11:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681855,2017-04-11 23:55:07 UTC,*** This is an automated message ***
1681901,2017-04-11 18:12:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681904,2017-04-11 18:00:00 UTC,Does this regression happen with the Ubuntu 4.8.0-45 and newer kernels? If so we can bisect between 4.8.0-44 and 4.8.0-45.
1681904,2017-05-03 15:49:41 UTC,apport information
1681904,2017-05-03 15:49:40 UTC,apport information
1681904,2017-05-03 15:49:38 UTC,apport information
1681904,2017-05-03 14:29:33 UTC,"We would like to collect some additional information about your system. From a terminal, please run the following:"
1681904,2017-05-03 13:47:14 UTC,"When testing 4.10.0-20-generic, can you confirm that you installed both the linux-image and the linux-image-extra .deb packages?"
1681904,2017-05-03 07:51:21 UTC,Thanks.
1681904,2017-05-02 21:28:03 UTC,Sorry for the delay.  Can you see if this bug is still happening with the Artful kernel?  It is available from:
1681904,2017-04-28 12:38:41 UTC,How is it going on?
1681904,2017-04-19 15:02:24 UTC,I can reproduce the issue with Linux kernel 4.8.0-45-generic #48~lp1681904Commit3105082594OntopOfStock44.
1681904,2017-04-19 13:52:12 UTC,"Can you test the following kernel next?  It is -44 with a pick of 3105082594e on top:
http://kernel.ubuntu.com/~jsalisbury/lp1681904"
1681904,2017-04-18 16:06:56 UTC,"That commit is in the Yakkety repo:
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety"
1681904,2017-04-12 20:20:07 UTC,Kernel 4.8.0-44-generic #47~lp1681904StockKernel don't have the issue.
1681904,2017-05-03 15:49:42 UTC,apport information
1681904,2017-04-12 16:34:38 UTC,The issue also appear with the kernel 4.8.0-45-generic #48~lp1681904Commit3105082594ea.
1681904,2017-04-12 14:49:09 UTC,"I built the next test kernel, up to the following commit:
3105082594ea260feb8c95893a0597b87c7cfe30"
1681904,2017-04-11 20:54:50 UTC,That version has the bug.
1681904,2017-04-11 20:04:55 UTC,I started a kernel bisect between v4.8.0-44 and v4.8.0-45.
1681904,2017-04-11 19:27:37 UTC,">Does this regression happen with the Ubuntu 4.8.0-45 and newer kernels?
"
1681904,2017-04-11 18:01:34 UTC,"There are not may commits between 4.8.0-44 and 4.8.0-45, so knowing the exact kernel when the regression started would be very helpful."
1681904,2017-04-11 18:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1681904,2017-04-19 00:42:28 UTC,I can reproduce the issue with Linux kernel 4.10.0-19-generic.
1681904,2017-04-12 19:51:04 UTC,"The bisect reported that commit 3105082594 introduced the regression, which is strange since that commit is just the ""Start new release""."
1681904,2017-05-03 15:49:43 UTC,I can confirm that i installed both packages.
1681904,2017-05-03 15:49:44 UTC,apport information
1681904,2021-01-06 17:03:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681904,2017-08-14 08:50:59 UTC,"Maybe there was ""no space left on device"" on /boot once, but i don't know exactly."
1681904,2017-08-14 06:54:28 UTC,No idea why the header package is not installed - it should be automatically pulled by meta package.
1681904,2017-08-11 10:49:19 UTC,"davidak@unibook:~$ sudo dkms install bcmwl/6.30.223.271+bdcom -k `uname -r`
[sudo] Passwort für davidak:
Error! echo
Your kernel headers for kernel 4.10.0-20-generic cannot be found at
/lib/modules/4.10.0-20-generic/build or /lib/modules/4.10.0-20-generic/source."
1681904,2017-08-11 03:28:25 UTC,"Please boot using kernel 4.10.0-20, and run
""sudo dkms install bcmwl/6.30.223.271+bdcom -k `uname -r`""
And see what really happens."
1681904,2017-08-10 12:46:31 UTC,the install seams to be succesfull.
1681904,2017-08-10 09:45:20 UTC,I think your chip needs to use bcmwl.
1681904,2017-08-10 09:26:05 UTC,I have done the latest updates.
1681904,2017-08-09 14:52:51 UTC,Sure. I think the current HWE stack is tracking 4.10 series.
1681904,2017-05-03 15:49:43 UTC,apport information
1681904,2017-07-26 15:23:24 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1681904,2017-08-09 14:31:01 UTC,"root@unibook:/home/davidak# dkms status
bcmwl, 6.30.223.271+bdcom, 4.8.0-44-generic, x86_64: installed
virtualbox, 5.0.40, 4.8.0-44-generic, x86_64: installed
root@unibook:/home/davidak# uname -a
Linux unibook 4.8.0-44-generic #47~lp1681904StockKernel SMP Wed Apr 12 17:28:21 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1681904,2017-07-04 17:11:09 UTC,I can still reproduce the issue after an update to the latest kernel 4.10.0-20-generic #22-Ubuntu.
1681904,2017-06-30 16:10:15 UTC,Any progress?
1681904,2017-05-04 08:27:20 UTC,I can reproduce the issue with Linux kernel 4.8.0-51-generic #54~lp1681904CommitsReverted.
1681904,2017-05-03 19:03:53 UTC,I built a test kernel with the two commits that came in with -45.
1681904,2017-05-03 15:49:51 UTC,apport information
1681904,2017-05-03 15:49:50 UTC,apport information
1681904,2017-05-03 15:49:49 UTC,apport information
1681904,2017-05-03 15:49:48 UTC,apport information
1681904,2017-05-03 15:49:46 UTC,apport information
1681904,2017-05-03 15:49:46 UTC,apport information
1681904,2017-07-07 06:01:22 UTC,I think 4331 should be supported by wl driver.
1681909,2019-07-05 00:20:57 UTC,"The attachment ""lp1681909_eoan.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1681909,2019-11-11 15:56:26 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1.3
1681909,2019-07-23 14:15:48 UTC,Thanks Eric for sponsoring this LP!
1681909,2019-07-23 19:41:38 UTC,Quick update
1681909,2019-07-31 14:56:21 UTC,Quick update:
1681909,2019-08-05 16:08:11 UTC,"Eric, thanks for looking into the testing failure."
1681909,2019-08-06 19:37:00 UTC,"makedumpfile merge to ""1:1.6.6-2ubuntu1"" sponsored in Eoan."
1681909,2019-08-16 19:21:17 UTC,"After updating the package for eaon-proposed with the fix for ppc64 (thanks Eric!), I've manually tested that version and it's working fine, being able to collect the kernel crash dump.
The version I've tested is:"
1681909,2019-08-19 19:45:28 UTC,"Merge proposal to britney/hints-ubuntu submitted, to mark this test as ""badtest"" for ppc64el: https://code.launchpad.net/~gpiccoli/britney/hints-ubuntu/+merge/371479"
1681909,2019-08-20 16:24:14 UTC,This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu1
1681909,2019-08-27 13:58:31 UTC,Next step is to consider backport feasibility for disco and bionic.
1681909,2019-08-27 14:31:23 UTC,"Hi Andrew Cloke,"
1681909,2019-08-27 14:48:39 UTC,Excellent news! Thanks Eric :-)
1681909,2019-08-28 13:43:07 UTC,"Hello bugproxy, or anyone else affected,"
1681909,2019-08-28 13:50:19 UTC,"Hello bugproxy, or anyone else affected,"
1681909,2019-08-29 13:00:47 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1681909,2019-08-30 18:56:20 UTC,"Tested with Bionic-proposed version (1:1.6.5-1ubuntu1~18.04.2) and Disco-proposed (1:1.6.5-1ubuntu1.1), both including the fix for this bug.
All working fine. I've used the ""droppkt"" hack (see comment #24) in the Bionic version, to simulate the problem, and it's fixed in the -proposed version."
1681909,2019-09-30 14:02:39 UTC,"Even though the bionic and disco verifications were successful (thanks for verifying), these patches were bundled in a single submission with other patches (from other bugs) which could not be successfully verified. As a result, all patches have had to be removed."
1681909,2019-10-14 01:37:07 UTC,"Just a quick update, the package got a respin without the offending patch, soon (after it got sponsored) it'll land into -proposed pocket."
1681909,2019-10-23 13:56:23 UTC,"Hello bugproxy, or anyone else affected,"
1681909,2019-10-23 13:59:41 UTC,"Hello bugproxy, or anyone else affected,"
1681909,2019-10-23 15:31:47 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1681909,2019-10-25 13:01:58 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.3) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1681909,2019-10-31 20:12:47 UTC,"Retested with Bionic-proposed version (1:1.6.5-1ubuntu1~18.04.3) and Disco-proposed (1:1.6.5-1ubuntu1.3), both including the fix for this bug."
1681909,2019-11-11 15:57:55 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.3
1681909,2019-07-23 13:59:02 UTC,Sponsored for 'Eoan'.
1681909,2019-07-22 16:34:04 UTC,Marking Cosmic as 'Won't fix'.
1681909,2019-07-20 19:19:22 UTC,Fix for eoan at my ppa. ppa:cascardo/kdump2.
1681909,2019-07-04 20:37:25 UTC,"This is the debdiff with the retry/delay mechanism, for Eoan. I've discussed with Cascardo and we agreed he will do the SRU to old releases (X/B/C/D) after applying some other SRUs he's working now."
1681909,2017-04-11 18:40:02 UTC,Default Comment by Bridge
1681909,2017-04-11 18:40:05 UTC,Default Comment by Bridge
1681909,2017-04-11 18:40:22 UTC,Default Comment by Bridge
1681909,2017-04-11 18:40:25 UTC,Default Comment by Bridge
1681909,2017-06-21 14:30:01 UTC,"------- Comment From <email address hidden> 2017-06-21 10:28 EDT-------
Canonical, any take on introducing NET_WAIT_TIME in /etc/default/kdump-tools file
to deal with timing issues on some NICs?"
1681909,2017-07-10 10:49:43 UTC,"------- Comment From <email address hidden> 2017-07-10 06:45 EDT-------
Issue is observed even on Briggs machine on Ubuntu 16.04.03"
1681909,2017-07-31 17:24:15 UTC,"I don't see any fundamental issue with providing a NET_WAIT_TIME variable (probably should be namespaced to KDUMP_) in the kdump config file, but:"
1681909,2017-07-31 18:19:48 UTC,"------- Comment From <email address hidden> 2017-07-31 14:14 EDT-------
(In reply to comment #30)

> I don't see any fundamental issue with providing a NET_WAIT_TIME variable
> (probably should be namespaced to KDUMP_) in the kdump config file, but:
"
1681909,2017-11-07 13:13:02 UTC,"Hi, I am a little eager to add this without trying to resort to other solutions first."
1681909,2017-11-17 08:30:15 UTC,"------- Comment From <email address hidden> 2017-11-17 03:21 EDT-------
(In reply to comment #32)

> Hi, I am a little eager to add this without trying to resort to other
> solutions first.
>
> So, options are:
>
> 1) For some reason, this driver is not behaving correctly. Can you add the
> PowerIO folks to this bug on IBM side and let them do some investigation?
"
1681909,2018-02-26 14:51:17 UTC,"From comment #8 and #10, is there any result from the PowerIO team's investigation into the NIC and related KDUMP_NET_WAIT_TIME config option?"
1681909,2019-11-11 15:56:39 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1681909,2018-03-05 13:20:29 UTC,"------- Comment From <email address hidden> 2018-02-26 13:57 EDT-------
I tried reproducing this issue in a Firestone system our team owns with Ubuntu 18.04 and I couldn't reproduce the issue."
1681909,2018-03-05 13:50:24 UTC,"------- Comment From <email address hidden> 2018-03-05 08:49 EDT-------
(In reply to comment #40)

> Can you try 16.04?
>
> Thanks.
> Cascardo.
"
1681909,2018-03-05 15:55:06 UTC,Default Comment by Bridge
1681909,2018-03-06 14:40:43 UTC,"------- Comment From <email address hidden> 2018-03-06 09:38 EDT-------
Cascardo, I gave a try with kdump in Ubuntu 16.04 and it seems to occasionally fail."
1681909,2018-03-06 14:40:44 UTC,------- Comment (attachment only) From <email address hidden> 2018-03-06 09:39 EDT-------
1681909,2018-03-06 15:09:35 UTC,"Hi, Murilo."
1681909,2018-03-06 15:20:59 UTC,"Looking at the log, I noticed the EEH is frozen right after finding the Broadcom card. Is that one the tg3?"
1681909,2018-03-06 16:31:41 UTC,"------- Comment From <email address hidden> 2018-03-06 11:15 EDT-------
(In reply to comment #45)

> Hi, Murilo.
>
> Can you test it on 16.04 using kdump-tools from xenial-proposed? Maybe the
> noirqdistrib option might be related to the EEH issues.
>
"
1681909,2018-03-06 16:31:43 UTC,------- Comment (attachment only) From <email address hidden> 2018-03-06 11:18 EDT-------
1681909,2018-03-08 16:12:31 UTC,"The kdump network timeout feature is a new feature request, that we will investigate for possible inclusion in 18.10."
1681909,2019-06-12 19:21:39 UTC,"It came to my attention that this issue still exists; an user report on x84-64 machine confirms that it's not only a ppc64 issue, it's a generic problem due to some NICs behavior; even with link up, they are really not ready to xmit packets. So, I could reproduce this by modifying virtio to mimic this scenario, and I'm working in a solution/quirk on kdump-tools (makedumpfile) package."
1681909,2019-07-04 20:02:11 UTC,This is a mock reproducer of this issue by faking a 20s delay in virtio-net after its link is up.
1681909,2018-03-05 13:37:37 UTC,Can you try 16.04?
1681909,2019-10-31 20:14:51 UTC,"There is some reported regressions in autopkgtests for ppc64el and s390x, I'm investigating.
Cheers,"
1681914,2017-04-11 19:03:12 UTC,apport information
1681914,2017-04-11 19:00:58 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1681914,2017-04-11 19:37:16 UTC,It looks like your kernel is behind.  The current lts-vivid kernel is: 3.19.0-82.  You might want to apply the latest updates.  Do you have a way to reproduce the bug?
1681914,2017-04-11 19:30:59 UTC,This change was made by a bot.
1681914,2017-04-11 19:03:24 UTC,apport information
1681914,2017-04-11 19:03:19 UTC,apport information
1681914,2017-04-11 19:03:16 UTC,apport information
1681914,2017-04-11 19:03:22 UTC,apport information
1681914,2017-04-11 19:03:10 UTC,apport information
1681914,2017-04-11 19:03:09 UTC,apport information
1681914,2017-04-11 19:03:07 UTC,apport information
1681914,2017-04-11 19:03:06 UTC,apport information
1681914,2017-04-11 19:03:04 UTC,apport information
1681914,2017-04-11 19:03:15 UTC,apport information
1681918,2017-04-11 23:22:47 UTC,Thank you for taking the time to report this bug and help make Ubuntu better. This bug has been reported to the developers of the software. You can track it and make comments at https://bugzilla.gnome.org/show_bug.cgi?id=781199
1681918,2017-04-14 10:58:08 UTC,This might possibly need to be the highest priority.
1681922,2017-04-11 23:55:05 UTC,*** This is an automated message ***
1681923,2017-07-09 04:36:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681930,2019-08-01 14:42:50 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Geoff and Rogan!"
1681930,2019-05-20 19:28:15 UTC,worked for me.  sign off at: user/rogan/lp1681930_signoff
1681930,2019-03-07 03:04:02 UTC,"While looking into this, I found that xact_paid_total also had the incorrect type of int for unvoided amount, and corrected it as well."
1681931,2017-04-14 11:13:52 UTC,"Reviewed:  https://review.openstack.org/456735
Committed: https://git.openstack.org/cgit/openstack/freezer-api/commit/?id=e0976af072badf78b335fea606b1efb2c24cc32a
Submitter: Jenkins
Branch:    master"
1681931,2017-06-08 18:21:52 UTC,This issue was fixed in the openstack/freezer-api 5.0.0.0b2 development milestone.
1681932,2017-04-11 21:13:31 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1681932,2017-04-11 21:25:42 UTC,This bug was fixed in the package grub-installer - 1.128ubuntu8
1681932,2017-06-14 20:33:32 UTC,"Looks like grub also fails, for the same reason (grub carries its own copy of prep-bootdev)."
1681932,2017-06-14 20:34:43 UTC,Checking artful correctly to make sure this behaves as expected. This may well be a direct side-effect of using VMs to do the testing.
1681932,2017-07-12 14:43:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681941,2017-04-12 18:21:55 UTC,"This was observed after update from 16.10. However I have managed to find source of this 'bug'. I have some additional breeze icons in ~/.local/share/icons/breeze. For some reasons (probably because this was needed at some point in the past) I also had corresponding 'index.theme' file placed in this directory. File from previous version of Breeze icon theme, which is a little different than current one. After removing this file everything works as expected."
1681941,2017-04-11 22:04:29 UTC,Cannot reproduce here on a fresh install: http://i.imgur.com/KYuAWxA.png
1681942,2017-04-12 14:28:35 UTC,"A freeze in changing fan speed is proper of some models of Dell notebooks
when a function call takes too much time in change fan speed. Up to now,
there is no solution to this problem."
1681945,2017-04-12 14:45:53 UTC,screen-q-agt.txt
1681945,2017-04-18 16:09:14 UTC,"Terry Wilson said it's contained (we check_error=False), so it's just a ERROR that should be transformed into something lower log level. And not a gate issue."
1681956,2017-07-19 18:54:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681956,2017-07-20 17:47:43 UTC,I found a workaround for Artful 17.10:
1681956,2018-06-09 12:53:23 UTC,workaround from #4 does no longer seem to work in bionic.  How can this be so screwed up in an LTS?
1681956,2017-07-19 17:18:25 UTC,"Hello Karl-Philipp,"
1681957,2017-06-18 17:47:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1681962,2020-08-19 21:47:54 UTC,I saw this assert too and reported it upstream
1681970,2019-08-08 09:22:10 UTC,"Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018
Bug did not expire due to bug watch
Upstream report suggests issue may have been fixed in version 3.24
Works ok with version 3.28.2 in Ubuntu 18.04
No further information provided by reporter so closing"
1681970,2017-04-16 03:07:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER"
1681970,2017-04-16 03:07:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1681970"
1681979,2018-08-13 14:37:37 UTC,This seems to be a duplicate of #1773286
1681979,2017-04-12 01:21:38 UTC,Here 4 networks. A VM from each network on both 2 compute nodes. This was OVS agent restart on network node (legacy deployment here). Tunnel 0x75b34 missing unicast flows. Tunnel 0x75b1d missing both.
1681979,2017-04-12 15:36:28 UTC,"Can you provide the configuration you have for ovs agent and l2pop driver? I suspect the agent_boot_time configuration option for the l2pop driver is sensitive to this bug. ""Delay within which agent is expected to update existing ports when it restarts"""
1681979,2017-04-12 18:46:34 UTC,"The agent_boot_time is untouched, so default of 180. This is well more than the duration of OVS agent boot to stabilize/all ports to be re-updated."
1681979,2017-04-12 18:59:18 UTC,"We have touched minimal config. Basic testbed w/ VXLAN tenant networks only, VLAN external network."
1681979,2018-08-13 14:38:36 UTC,"See this patch.
https://review.openstack.org/#/c/571920/"
1681979,2018-07-12 07:32:55 UTC,"Hi, Arjun Baindur. Has this problem been solved?"
1681979,2017-11-29 03:18:47 UTC,"I also encountered the similar problem.
I found a logic error after browse neutron code:"
1681986,2017-04-12 02:43:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/455887"
1681989,2017-05-07 15:32:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/463148"
1681989,2017-05-06 03:41:32 UTC,"Reviewed:  https://review.openstack.org/456050
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2d03bf92db3615693b62f4f3274b867f00c0967
Submitter: Jenkins
Branch:    master"
1681989,2017-04-12 05:13:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456050"
1681989,2017-04-19 11:38:32 UTC,This bug still exists in the master branch
1681989,2017-06-08 21:52:38 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1681989,2017-06-09 16:11:06 UTC,"Reviewed:  https://review.openstack.org/463148
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=87989c5a37d0894e104ccfebeb05115d593291f4
Submitter: Jenkins
Branch:    stable/ocata"
1681989,2017-06-19 12:45:38 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1681989,2017-07-12 23:56:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/483133"
1681989,2017-07-14 15:34:10 UTC,"Reviewed:  https://review.openstack.org/483133
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9eea8869eabf12d3e1a078bd48fa96f0badb1ed
Submitter: Jenkins
Branch:    master"
1681993,2017-04-12 04:26:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1681998,2017-04-12 14:00:03 UTC,Yeah we did attempt to fix this with [2] but couldn't find a reasonable way to handle >1 bdm with the same instance_uuid and volume_id.
1681998,2017-04-13 00:20:17 UTC,"Hi Lee,"
1682006,2017-04-22 15:51:15 UTC,"Hi, @Himani,"
1682006,2017-04-22 15:52:38 UTC,I am going to mark this bug as 'Imcompleted'. Will revisit it after getting further clarifications from @Himani.
1682011,2017-04-18 04:05:56 UTC,"If the sandbox container is stopped, the real container will lose the network but it will be still running. I am not sure what are the prefect way to represent this state. Perhaps leave the container as 'running' state makes sense because the container is actually running. However, I would let others to comment on it."
1682011,2017-09-26 18:55:34 UTC,"There is no activity for fixing this bug for a while. I am going to remove assignee so that other contributors can take it, but please feel free to re-assign it to yourself if you want to continue to work on this bug."
1682017,2017-10-18 09:22:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682017,2017-10-18 09:27:04 UTC,See this from cron whenever flash updates are available on my amd64 17.04 box.
1682017,2017-10-18 09:40:07 UTC,In /var/lib/dpkg/info/apt.postinst there is a comment that says:
1682017,2017-10-18 09:43:11 UTC,"I should also mention that the aforementioned _apt user does exist on my system, it's just that the directory is not owned by them."
1682020,2018-02-26 12:31:31 UTC,"Reviewed:  https://review.openstack.org/547985
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ed7af4c8f4d72ed0a1c15daf1c700b07fbeed635
Submitter: Zuul
Branch:    master"
1682020,2019-02-28 10:20:02 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.openstack.org/550173
Reason: Realistically, this shouldn't merge until Ubuntu 20.04 is out and Fedora 28 symlinks the path [1] making this unnecessary. Let's abandon this for now."
1682020,2018-04-20 13:13:52 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1682020,2018-03-12 23:00:19 UTC,"Reviewed:  https://review.openstack.org/483994
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cab8139498c7ea6b05cfdc8b4997276051b943fc
Submitter: Zuul
Branch:    master"
1682020,2018-03-06 17:23:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/550173"
1682020,2018-03-06 15:58:37 UTC,"Reviewed:  https://review.openstack.org/548057
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=733b61527da7e1961548966360a9241b2a304014
Submitter: Zuul
Branch:    stable/queens"
1682020,2018-02-26 15:45:56 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/548057"
1682020,2018-02-26 10:56:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/547985"
1682020,2017-09-15 22:24:36 UTC,"Reviewed:  https://review.openstack.org/498509
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ccfb46420d6ee186d6ec777ce6167bd138f2a285
Submitter: Jenkins
Branch:    stable/pike"
1682020,2017-05-11 05:43:19 UTC,"is there any guideline or links you mentioned above for the deprecation?
And the patch you showed seems only remove the default value, so we need totally deprecate the whole option and don't use it in the future?"
1682020,2017-08-28 15:45:05 UTC,"Reviewed:  https://review.openstack.org/496605
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d983234288728427235ef2c1f355ec135119b865
Submitter: Jenkins
Branch:    master"
1682020,2017-08-23 10:30:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/496605"
1682020,2017-08-23 09:17:01 UTC,"Hi Daniel,"
1682020,2017-07-14 17:01:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/483994"
1682020,2017-07-14 15:40:31 UTC,It is more subtle than suggested by that quote IRC conversation.
1682020,2017-06-27 12:38:57 UTC,"In the Dinesh #3 comment above, 'pjp' is 'Prasad J Pandit'.
He has committed many patches to the Qemu project so we assume he has basic knowledge to tell if any parameter is deprecated or not."
1682020,2017-06-27 07:35:45 UTC,"Hi all,"
1682020,2017-08-28 16:01:23 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/498509"
1682023,2019-10-29 22:13:35 UTC,I believe this pull request is relevant https://github.com/snapcore/snapd/pulls/mvo5
1682023,2019-10-29 22:12:01 UTC,"Please forgive me, I misread the bug description."
1682023,2019-10-29 22:01:56 UTC,I believe a part of this issue was fixed but the fix only works when a package is purged. Not when the package is removed but the conffiles stay behind.
1682023,2018-05-22 05:40:48 UTC,apparmor failed to start.
1682023,2017-04-12 07:49:00 UTC,"Managed to reproduce by purging the current snapd, installing a 2.22.x version, purging just snapd, and finally installing the latest snapd.  See attached transcript."
1682023,2019-11-26 09:32:06 UTC,I realised my last comment used incorrect link. The URL I meant to share was https://github.com/snapcore/snapd/pull/7661
1682023,2017-04-12 11:49:09 UTC,https://github.com/snapcore/snapd/pull/3181
1682023,2020-06-23 11:19:50 UTC,Snapd 2.43 has been released a while ago. Marking as released.
1682030,2017-05-07 02:47:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682039,2017-04-12 16:18:30 UTC,"> I try this weekend to make a extension
"
1682039,2017-04-12 19:24:15 UTC,"It works perfect, thank you very much!"
1682039,2017-04-12 17:15:36 UTC,"here are the extension it only unlink the LPE of all the selected objects. you need to do the work first.
https://inkscape.org/en/~jabiertxof/%E2%98%85unlink-lpe"
1682039,2018-10-04 23:06:12 UTC,in 0.92+devel LPE are autoforked
1682039,2017-04-12 15:55:55 UTC,I try this weekend to make a extension
1682039,2017-04-12 08:14:34 UTC,"In this case yes, anyway we need a decision about this, options:
2 options: copy path effect and clone path effect in the menu.
Directly change to copy path effect, forking path parameter."
1682039,2017-04-12 14:37:22 UTC,"And by the way, there is a forum topic about problem:
http://www.inkscapeforum.com/viewtopic.php?t=30908
Unfortunately, there is no good solution. The question (or bug-report) is still relevant."
1682039,2017-04-12 11:14:49 UTC,"By the way, is it any quick way for now to unlink path effect?"
1682039,2017-04-12 08:50:23 UTC,"Well, it will be even better if the user has a choice between these two options (copy or clone path effect)."
1682039,2017-04-12 15:43:49 UTC,"no quick, maybe the better is a extension for 0.92"
1682044,2017-04-12 08:26:59 UTC,"The attachment ""0001-Fix-memory-leaks.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1682046,2017-04-12 11:18:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/456171"
1682046,2019-12-18 17:34:35 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/456171
Reason: This repo is retired now, no further work will get merged."
1682050,2017-04-12 10:59:59 UTC,"Where are those constraints listed? You can always deploy applications with
their own constraints (juju deploy app --constraints mem=X)."
1682050,2017-04-12 11:48:09 UTC,"When uploading a new OpenStack image you can specify two 'constraints' - minimum disk size and minimum memory size required to boot the image. You can then query OpenStack to retrieve the values, see https://docs.openstack.org/developer/glance/glanceapi.html#list-available-images-in-more-detail (the min_disk and min_ram properties). When manually launching a new OpenStack instance, after the image is selected, OpenStack disables all flavors that do not fulfill those two requirements and I expected that Juju does the same, but it does not."
1682055,2017-04-12 16:41:16 UTC,I don't care too much about dh_apparmor (EWRONGDISTRO ;-) - but still:
1682055,2019-12-17 19:37:50 UTC,"Keeping the profiles in the running kernel is by design since there might be processes that are still running under the profile on package removal. dpkg doesn't do anything to guarantee that executables that the package ships aren't running, so we can't reasonably unload the profiles. Marking Won't Fix. If you feel strongly this is in error, please reopen with reasoning why."
1682059,2017-04-12 09:22:00 UTC,"I have personally confirmed this with a keystone + Swift dev environment, while reviewing patch https://review.openstack.org/#/c/454386:"
1682059,2017-04-12 11:02:37 UTC,Related bug https://bugs.launchpad.net/swift/+bug/1604674
1682059,2017-05-02 10:27:35 UTC,"Somehow we failed to have a Closes-Bug patch on the patch. This is fixed by:
 https://review.openstack.org/#/c/454386"
1682068,2017-04-12 11:50:50 UTC,Fixed in stable r18347 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18347>.
1682077,2017-12-05 23:21:18 UTC,The last time something like this was fixed was https://bugs.launchpad.net/bugs/1329434. The fix was to disable APIC virtualization in nested guests. Did it suddenly get turned on again? Any patches we could test? Thanks.
1682077,2019-01-23 04:23:27 UTC,Reproduced in Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz
1682077,2018-11-17 09:36:46 UTC,"I am sorry if this bug is to old, but i have this problem and cannot find the solution until now."
1682077,2018-01-27 03:26:17 UTC,"Running into the same as well.
Is there any workaround on this?"
1682077,2018-01-08 10:27:15 UTC,Changing the script to be used with xenial instead of trusty: https://gist.github.com/kmindi/4fb1332509a39b6214b0e8b39611f5ad
1682077,2017-12-05 14:55:09 UTC,Facing the same issue with KVM enabled L2 VM  on following setup
1682077,2019-02-24 21:20:48 UTC,This happens in about half of the xenial semaphoreci.com instances as well:
1682077,2017-04-24 22:23:15 UTC,Maybe IS happens to have a box that's not provisioned yet and you can borrow? Or you can borrow that one for a bit if lgw01 has some spare capacity? Or they'll upgrade to the current lts-xenial kernel so we maybe get lucky. :)
1682077,2017-04-13 17:08:22 UTC,Adding some miscellaneous data points.
1682077,2017-04-12 14:00:00 UTC,"For me it's enough to boot an instance on an affected lgw01 compute node, install qemu-system-x86, download a cloud image and run ""/usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -drive format=raw,cache=unsafe,file=zesty-server-cloudimg-amd64.img -machine accel=kvm -enable-kvm -cpu host"""
1682077,2017-04-12 12:31:40 UTC,"We hit this late last week too, I'm having difficulty reproducing it though. smb thinks there could be some issue with checks failing for feature bits not passed into the guest because they were new and thus perhaps a problem when using pretty recent hardware."
1682077,2017-04-12 10:41:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682077,2017-04-12 10:19:40 UTC,"Hmm, that's a non current kernel - I wonder if someone can test with the current lts-xenial?"
1682077,2017-04-12 10:14:33 UTC,"arges wrote a script in bug #1329434 which might be enough to repro this, but I don't have access to the hw myself to test"
1682077,2017-04-24 20:36:24 UTC,Stefan Bader and I have continued trying to reproduce this. Here's what we've done:
1682081,2017-05-17 11:50:56 UTC,Observed the same issue while managing volume from HPE VSA (Virtual Store Appliance) storage system.
1682083,2017-06-27 18:08:07 UTC,"Hi there,"
1682083,2018-07-13 05:35:18 UTC,"@Richard Harding, John A Meinel,"
1682083,2019-01-11 09:17:02 UTC,I'm closing this bug for MAAS since we haven't gotten any reply for 1.5 years.
1682085,2018-03-28 21:01:32 UTC,"I know this is old, but just in case someone comes looking for an answer.
I ran into this problem because my hugepages were setup wrong:
if you follow this instructions you can get more info.
in my case my pages were setup wrong because the page setup talks bout bytes. i.e. 2048=2M and the pages are expresed in M, once I made those two match i.e. 2pages = 2048*2 Bytes or 2MB then it worked.
hope it helps someone."
1682094,2019-05-22 12:06:43 UTC,"Reviewed:  https://review.opendev.org/647484
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1916bc5c0627ca24e312ca55ea62c8df7eb8f158
Submitter: Zuul
Branch:    master"
1682094,2019-03-25 14:31:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647484"
1682094,2017-05-04 11:23:48 UTC,"Sorry, after reading ""Should you use it? Probably not."" about implementing RFC 4291, i thought it would be more important to talk about the aims of OpenStack than about some technical details.
I never saw that as a Question."
1682094,2017-04-18 14:08:03 UTC,And just to follow-on with more data...
1682094,2019-05-22 14:13:42 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660729"
1682094,2017-04-14 09:07:34 UTC,"I recognized, that there are many people who want to carry-over all that dump IPv4 behaviors to IPv6. That it becomes at least the same crippled as IPv4 was.
Giving /128 to customers is a other of that bad ideas or make TCP-Connection-Tracking (And breaking all non TCP-Protocols) in some middleboxes is an other. (Both used in the official Tutorials of OpenStack.)"
1682094,2017-04-13 15:22:13 UTC,"I am not going to engage in a discussion regarding Openstack not being ""modern"" wrt 1995."
1682094,2017-04-13 12:19:40 UTC,"2001:db8::1 would be the second adress in the subnet 2001:db8::/64. This works perfectly fine.
2001:db8::0 wich can be shortend to 2001:db8:: is the first one.
And of course this is a complete IPv6 address."
1682094,2017-04-12 14:48:52 UTC,"Can you try with gateway 2001:db8::1 ?  You didn't specify a complete IPv6 address in your example, not sure if it was just a typo."
1682094,2017-04-17 18:58:09 UTC,"You did not even respond to my comment - both RFC 4291 and IANA define the zero address of an IPv6 subnet to be reserved for the Subnet-Router anycast address.  If you have information that I'm wrong about that please let me know, I've been wrong before."
1682094,2019-05-22 14:21:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/660734"
1682094,2019-05-22 14:13:56 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/660730"
1682094,2019-05-28 03:11:23 UTC,"Reviewed:  https://review.opendev.org/660734
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0cd42257aaced0b6da0f43bc5da660b6a664141f
Submitter: Zuul
Branch:    stable/queens"
1682094,2019-05-29 06:35:37 UTC,"Reviewed:  https://review.opendev.org/660730
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=663c727f993106f654f8087f9d5122cee94bf466
Submitter: Zuul
Branch:    stable/rocky"
1682094,2019-08-20 18:36:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/677539"
1682094,2019-08-27 12:27:02 UTC,"Reviewed:  https://review.opendev.org/677539
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e37e714b0816a0b95902fdd384cf884643d260d7
Submitter: Zuul
Branch:    stable/pike"
1682094,2019-05-24 02:19:45 UTC,"Reviewed:  https://review.opendev.org/660729
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=49af575efff80f7648842cd7b530a05e1ee7d171
Submitter: Zuul
Branch:    stable/stein"
1682100,2017-04-13 09:46:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456536"
1682100,2019-12-18 17:21:07 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/456536
Reason: This repo is retired now, no further work will get merged."
1682104,2017-06-01 08:34:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682104,2017-06-08 11:46:28 UTC,The problem persists in the most recent 1.8.16-0ubuntu1.4
1682105,2019-03-25 11:35:02 UTC,"Er... the workaround should be to manually edit /etc/environment, not /opt/canonical/landscape/scripts/landscape-env.sh"
1682105,2021-02-12 21:21:30 UTC,"We tried to the same thing with root-url today, as we had issues with SSL certs and such."
1682105,2020-07-14 00:43:58 UTC,"Setting in the GUI is most definitely not a workaround to the script errors, due to #1523950 ."
1682105,2019-04-15 07:58:19 UTC,"Another workaround is to set the proxy in the web GUI, under Settings -> Proxy for HTTP and HTTPS traffic (and restart)"
1682105,2019-03-25 11:32:44 UTC,"Also to be considered: proxy variables can be set in either the legacy http-proxy / https-proxy variables or the charm-specific juju-http-proxy / juju-https-proxy. (at least) The latter set should be supported.
The workaround is to manually hack proxy variables in /opt/canonical/landscape/scripts/landscape-env.sh"
1682105,2017-04-12 12:14:17 UTC,"Related, if not a duplicate: https://bugs.launchpad.net/landscape/+bug/1523950"
1682105,2020-03-10 12:33:03 UTC,"I edited the /etc/enviroment and added the Proxy entries as I need them.
also I added the Proxy Information in the Web GUI. Restarted everything..."
1682110,2017-04-12 15:12:23 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1682116,2017-04-17 14:13:39 UTC,You must use the query parameter ?multipart-manifest=delete as described in : https://docs.openstack.org/developer/swift/overview_large_objects.html#deleting-a-large-object
1682116,2017-09-27 19:49:29 UTC,"Only works for SLO, not DLO:"
1682116,2017-12-13 17:01:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527744"
1682116,2019-03-17 14:50:13 UTC,"+1, Any expectations when this fix also will be merged to master, there is no activity during one year (("
1682118,2017-04-12 15:12:19 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1682118,2017-07-02 22:18:15 UTC,This bug was fixed in the package ukui-control-center - 1.0.3-0ubuntu1
1682124,2017-04-12 15:12:18 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1682124,2017-04-20 00:29:20 UTC,I have uploaded pull request on github and waiting for merge.
1682124,2017-07-02 22:18:15 UTC,This bug was fixed in the package ukui-control-center - 1.0.3-0ubuntu1
1682126,2017-04-12 15:12:16 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1682126,2017-04-12 19:01:39 UTC,Could you please confirm this is an issue with setting the time on the system?
1682126,2017-04-13 02:51:09 UTC,"cyphermox, this maybe the problem of translation. We will confirm it later after the release.
Thanks:)"
1682126,2017-07-02 22:18:15 UTC,This bug was fixed in the package ukui-control-center - 1.0.3-0ubuntu1
1682129,2017-05-19 14:58:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682131,2017-04-12 15:12:12 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1682131,2017-04-12 18:57:28 UTC,Can you please confirm; this is a bug about the fact that fonts can't be changed?
1682133,2017-04-17 13:19:59 UTC,"No update were made, and my screen is back... oO"
1682134,2017-04-12 18:59:20 UTC,This appears to be an issue in the control-center application. Can you confirm that this is about changing date and time for the system?
1682134,2017-04-12 15:12:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1682134,2018-04-06 12:13:15 UTC,This bug was fixed in the package ukui-control-center - 1.1.1-0ubuntu1
1682139,2017-04-21 16:42:48 UTC,"Hello Andres, or anyone else affected,"
1682139,2017-04-22 09:28:33 UTC,This bug was fixed in the package python-tx-tftp - 0.1~bzr47-0ubuntu1
1682139,2017-06-27 15:34:33 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1682139,2017-09-26 19:29:33 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for zesty for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1682148,2017-04-12 14:23:33 UTC,The machine interfaces table has not been updated to the new patterns. This is a wishlist.
1682148,2017-10-11 21:13:32 UTC,"@Andres
We have fixed this bug (although the error message is duplicated in the footer, which is not part of the pattern). Shall I open an other bug or edit this one?"
1682149,2017-04-12 14:23:20 UTC,"If anyone is interested, a failed autopkgtest log link can be found below - but as mentioned already, the original error message doesn't say much as it was not meant to handle 404 errors (and breaks during printing the error log)."
1682149,2017-04-12 14:23:53 UTC,For now Adam decided to remove the -proposed resteasy version.
1682149,2017-04-13 08:34:48 UTC,"yep, well known:"
1682149,2018-04-23 06:26:19 UTC,"It's clear that even dogtag 10.6.0 doesn't work with resteasy 3.1, so either resteasy3.0 needs to stay in bionic, or src:resteasy will be reverted to 3.0.19."
1682149,2020-12-23 08:13:22 UTC,and upstream probably won't move to a newer resteasy base
1682149,2020-12-23 08:12:45 UTC,this was resolved by packaging a separate resteasy3.0
1682154,2017-09-07 18:04:48 UTC,"Hello slodki, or anyone else affected,"
1682154,2017-05-22 10:02:23 UTC,Just did a release to artful; I will do this one in the next update after this one.
1682154,2017-05-02 16:54:46 UTC,This is not yet fixed in artful yet.
1682154,2017-05-02 16:49:35 UTC,The patch has been accepted upstream:
1682154,2017-04-14 18:51:15 UTC,Ubuntu 16.10 seems unaffected.
1682154,2017-10-02 14:48:49 UTC,"systemd 232-21ubuntu5
# loginctl show-session 2227 c1 | grep -e Id= -e Leader
Id=2227
Leader=723
Id=2227
Leader=723"
1682154,2017-10-05 17:31:20 UTC,"Hello slodki, or anyone else affected,"
1682154,2017-10-10 07:17:36 UTC,"ubuntu@sruz:~$ dpkg-query -W systemd
systemd	232-21ubuntu5
ubuntu@sruz:~$ loginctl show-session 3 1 | grep -e Id= -e Leader
Id=3
Leader=1290
Id=3
Leader=1290"
1682154,2017-10-26 14:28:26 UTC,This bug was fixed in the package systemd - 232-21ubuntu7
1682154,2017-10-26 14:28:50 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1682154,2017-06-22 17:42:06 UTC,This bug was fixed in the package systemd - 233-8ubuntu1
1682163,2019-09-19 11:59:13 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1682167,2017-04-19 12:02:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682167,2017-05-06 18:38:46 UTC,I can confirm this still happens with gnome-shell 3.24.1-0ubuntu1.
1682167,2017-05-06 18:51:46 UTC,Did you restart your computer after updating gnome-shell?
1682167,2017-05-06 19:09:17 UTC,Yes; I also reverted geoclue.conf back to the packaged version before checking.
1682167,2017-05-06 20:08:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1682167,2017-07-28 14:23:14 UTC,"The issue should be fixed in artful, can you try if that works for you?"
1682167,2017-07-29 06:41:59 UTC,Seems to be fixed.
1682167,2017-05-06 14:49:31 UTC,Please confirm whether you still experience this issue with gnome-shell 3.24.1-0ubuntu1
1682171,2017-04-13 18:56:42 UTC,I've also tried to workaround this with synclient without any success so far :/
1682171,2017-04-14 13:26:01 UTC,Just registered to spread the solution to this annyoing problem. By the way - most annoying registration process I have ever seen. Lame.
1682171,2017-04-19 09:10:39 UTC,"Thanks man! I was afraid it would be a feature, you never know :-)"
1682171,2017-05-08 19:36:49 UTC,"Status changed, this issue STILL affects those running the HWE stack on Ubuntu 16.04 with Gnome. ( sudo apt-get install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 ) will result in outdated version of xserver-xorg-core ( <2:1.17.99.902) being installed which results in an unmet dependency for xserver-xorg-input-libinput and still breaks the tap to click dialogue. Removing the interfering xserver-xorg-input-synaptics obviously breaks things even more..."
1682171,2017-09-19 05:13:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682171,2017-04-13 07:17:42 UTC,/org/gnome/desktop/peripherals/touchpad/tap-to-click does not seem to have any effect.
1682171,2017-04-13 18:17:57 UTC,I disabled /org/gnome/desktop/peripherals/touchpad/tap-to-click before reporting here. I can confirm that it has no effect.
1682181,2019-05-31 06:15:10 UTC,"As per LSB and FHS (https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) /usr/local/ directory structure is used for locally (manually) installed files (which you might do, for instance, if you install postgres from source)."
1682181,2019-05-31 14:19:06 UTC,"How about /usr/bin/pgsql/, could that be considered?"
1682182,2017-09-21 13:09:31 UTC,"agents should probably be removed automatically, however I don't think the neutron-openvswitch charm or the neutron-gateway charms have direct access credentials for the Neutron API so we need to come up with a neat way to make that actually happen."
1682189,2019-09-19 14:58:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1682193,2017-08-10 15:11:34 UTC,Waiting for solution... :(
1682193,2017-04-30 15:01:21 UTC,@clel oh in case you decided to remove libinput and install evdev you need to reboot for the driver change to take effect.
1682193,2017-04-30 20:08:17 UTC,"@POP Ok, I only have the speed slider."
1682193,2017-05-04 04:14:39 UTC,"I had a similar problem. After upgrading to Xubuntu 17.04, the mouse was too fast but settings had no effects. I solved this problem with xinput. See comments in this bug report (may be a duplicate):"
1682193,2017-06-26 09:09:14 UTC,"As for the severity of the bug: the slower your mouse, the more you have to move your wrist and arm to move the pointer. Moving your arm and wrist instead of leaving your hand still on your wrist pad increases the risk of carpal tunnel syndrome."
1682193,2017-07-04 14:06:56 UTC,"Hello, same problem here with 17.04 and MX Master 2S. Slider doesn't work and also xinput doesnt seem to do the trick."
1682193,2017-07-09 16:14:08 UTC,I solved it: I downgraded to 16.04.
1682193,2017-07-13 12:42:52 UTC,This is the second time a rather serious bug was introduced with an Ubuntu upgrade. And it is very sad to see again how slow this kind of bugs are treated.
1682193,2017-08-10 20:12:11 UTC,"#27, just to add to my previous post a few months ago, removing xserver-xorg-input-libinput AND installing xserver-xorg-input-evdev fixed it for me in several machines. What I additionally found is that the latter package does not come preinstalled and just removing libinput will leave you mouse/keyboardless in X."
1682193,2017-04-30 14:57:06 UTC,"@clel yes under pointer speed I have two sliders Acceleration and Sensitivity. Neither has any effect.
BUT I was able to fix it today by removing libinput and installing evdev! Now both sliders work like before and I can increase acceleration. I don't see any problems with the system so you can try that if your system is used for educational purposes non critical daily use.
I heard that they are going to switch to Wayland in the next release so this is probably all that we needed to do until the next release. Problem solved!"
1682193,2017-08-11 02:07:15 UTC,This way above helps me too.
1682193,2018-04-28 03:51:21 UTC,"@28 Good thinking on the MATE solution. This package is called ""mate-mouse-properties"""
1682193,2018-09-28 05:24:44 UTC,This workaround can be used also:
1682193,2019-03-28 09:59:20 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1682193,2019-07-25 09:11:22 UTC,"This bug report expired because 17.04 is not supported anymore.  Did anyone recreate a corresponding bug report for a more recent version of Ubuntu?  If so, can you please publish the link so we can subscribe to it?"
1682193,2017-08-10 18:17:24 UTC,"I have found a solution to this matter. By installing Mouse Setting of Mate, the slider setting makes affect to mouse speed. Launch Software Center and search with keyword ""Mouse"", then find the icon of Mouse which belong to Mate DE (read description). After install it, you can launch it right from the Software Center as you won't find it through DASH. Once it launched, lock it to the Panel as the setting of mouse speed is reseted every rebooting. I'm sorry if my English is not good enough."
1682193,2017-04-30 09:03:32 UTC,@POP So acceleration is not working for you either? Because for me changing of speed or sensitivity (amount of pointer movement for a constant mouse movement) is not working and I think that is even worse.
1682193,2017-06-02 19:55:39 UTC,"xinput didn't work for me at all. Neither was changing the sensitivity in the default mouse application or in gpointing-device-settings. What DID work for me was change the value in ""/sys/devices/platform/i8042/serio1/sensitivity"" to 200. It worked immediately."
1682193,2017-04-29 10:29:10 UTC,Just to confirm that removing xserver-xorg-input-libinput solved the issue without [immediately evident] side effects. I had to reconfigure the mouse speed in the GUI.
1682193,2017-04-12 20:25:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1682193,2017-04-29 14:13:38 UTC,"My only experience is with xfce desktop and I can confirm that from version 16 at least, mouse sensitivity and acceleration settings didn't work correctly. Generally it was either too slow or too fast. I was happy with too much acception so I didn't complain. But they have updated the xorg server so something may have gone wrong. And I don't think we are going to hear a lot of complaints about this.
Neither sensitivity nor acceleration do anything at all in this version. Everything is just constant. And certainly I am not going to mess with system packages to solve this.
@clel Geschwindigkeit is just velocity or speed. For acceleration they should have used Beschleunigung. The sensitivity adjusts the relationship between physical mouse movement and the pointer movement. How precise it is. The acceleration increases the ratio between pointer movement and mouse movement depending on the speed or Geschwindigkeit of the mouse itself. In other words it translates mouse speed into pointer acceleration or Beschleunigung. So you can call it speed if you mean mouse movement, but acceleration if you mean pointer movement. Sensitivity and acceleration settings are distinct and I cannot see how they can combine them unless they just discard one, probably the sensitivity, and keep accelerate and rename it to speed or Geschwindigkeit."
1682193,2017-04-17 20:09:06 UTC,Xubuntu 17.04 here. For me it seems like the acceleration setting is not having any effect at all. It's just too slow and not usable. This needs urget fix. Logitech mouse. Worked perfectly with Xubuntu 16.09.
1682193,2017-04-22 07:59:27 UTC,The same exact problem on 17.04 after upgrading from 16.10.
1682193,2017-04-25 10:28:00 UTC,"Same for me. Mouse is Logitech MX master. Mouse speed slider have no effect on my mouse.
The only way I was able to increase mouse speed is using xinput utility as described in this link:
https://askubuntu.com/questions/794185/how-to-disable-mouse-acceleration-in-ubuntu-16-04"
1682193,2017-04-25 16:58:57 UTC,I'll add that I've got the same issue; the settings slider has no effect on the mouse speed (ThinkPad USB Laser Mouse).
1682193,2017-04-27 12:32:17 UTC,"This is caused by xserver-xorg-input-all pulling -libinput instead of -evdev. Too bad -evdev is in universe now, and reverting the change in zesty probably wouldn't help much because -libinput would not get uninstalled on upgrade."
1682193,2017-04-13 14:41:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682193,2017-04-28 18:24:59 UTC,"There is no such thing as ""mouse speed"". There is mouse ""sensitivity"" and ""acceleration""."
1682193,2017-04-28 18:48:44 UTC,This is the exact discription of who my trackpoint works on Ubuntu now:
1682193,2017-04-28 16:06:06 UTC,Are we really talking about acceleration or about mouse speed? Also see https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1683145
1682193,2017-04-29 09:35:33 UTC,"@loplop, surprisingly in my default installation the only mouse option related to our problem in settings is labeled as ""Mouse Speed"" (Below System Settings -> Mouse & Touchpad). Whatever it does behind the scenes I can't but guess; in my duplicate bug #1683435 I reported seeing ""Accel Speed"" in the capabilities listed by xinput. I too am used to being able to differentiate between acceleration and precision somehow in other desktops/OSs."
1682193,2017-04-29 09:39:54 UTC,"@POP I don't know the correct term. For me there is a slider named ""Zeigergeschwindigkeit"" in the system settings, which translated means ""pointer speed"". But maybe sensitivity is the correct term in English."
1682193,2017-04-29 09:50:35 UTC,"Before upgrading to 17.04, I can run ""xset m 1 1"" to change my mouse
constant speed and acceleration."
1682193,2017-04-29 09:56:03 UTC,"Maybe the problem is that since the upgrade xinput does not offer the corresponding option for setting speed/sensitivity resulting in a not working slider. Don't know whether there was such option before, though."
1682200,2017-04-12 20:20:25 UTC,The image objects seem to have a number of unneeded clips and masks that interfere with output to PDF.
1682201,2017-04-12 19:11:34 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1682204,2020-11-09 18:03:17 UTC,"I did a fresh install from ubuntu-20.04-live-server-amd64.iso and see the same problem.
The LVM partition was assigned the generic Linux GUID instead of the LVM GUID.
This broke my custom disk extraction utility. I manually corrected the GUID."
1682204,2017-04-12 19:07:43 UTC,"I've discovered that, when using a ""flat"" layout, swap partitions are similarly misidentified as type 0x83 (on MBR) or 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (on GPT), when they should be 0x82 (on MBR) or 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F (on GPT; 8200 in gdisk)."
1682204,2017-04-12 18:45:52 UTC,This is an issue with curtin not MAAS.
1682215,2017-04-12 19:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1682215,2017-04-12 20:12:26 UTC,"I built a test kernel with commit 729204ef49.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1682215/"
1682215,2017-04-12 22:20:37 UTC,"Hi,"
1682215,2017-04-13 10:46:17 UTC,"SRU request submitted for Xenial and Yakkety:
https://lists.ubuntu.com/archives/kernel-team/2017-April/083605.html"
1682215,2017-05-03 16:55:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1682215,2017-05-03 16:56:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1682215,2017-05-03 17:53:54 UTC,Test case from comment #3 passed using the -proposed kernel for Xenial and Yakkey.
1682215,2017-05-16 10:43:17 UTC,This bug was fixed in the package linux - 4.8.0-52.55
1682215,2017-05-16 11:20:41 UTC,This bug was fixed in the package linux - 4.4.0-78.99
1682229,2017-04-12 21:25:54 UTC,That's a good idea. It should be easy to update a photo on both Gravatar and Libravatar since that's a very common use case.
1682230,2017-04-13 07:20:43 UTC,apport information
1682230,2017-04-13 07:20:36 UTC,apport information
1682230,2017-04-13 07:20:39 UTC,apport information
1682230,2017-04-13 07:20:40 UTC,apport information
1682230,2017-04-13 07:20:42 UTC,apport information
1682230,2017-04-13 07:20:45 UTC,apport information
1682230,2017-04-13 07:20:38 UTC,apport information
1682230,2017-04-13 07:20:50 UTC,apport information
1682230,2017-04-13 07:20:29 UTC,apport information
1682230,2017-04-13 07:20:48 UTC,apport information
1682230,2017-04-13 07:20:31 UTC,apport information
1682230,2017-04-13 07:20:33 UTC,apport information
1682230,2017-04-13 07:20:34 UTC,apport information
1682230,2017-04-12 22:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1682230,2017-04-12 20:25:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1682230,2017-07-07 12:45:08 UTC,"With the  4.8.0-58-generic kernel (x86_64), no problem detected."
1682230,2017-06-17 04:17:50 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1682230,2017-04-13 07:20:35 UTC,apport information
1682230,2017-04-17 18:16:30 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1682230,2017-04-15 14:30:12 UTC,This change was made by a bot.
1682230,2017-04-13 07:28:53 UTC,"Hey,
This complement is under the kernel that has no problem.
Should I try with the conflicting one ?
Sorry, this is the first time I report bugs.
Amicalement (french in the text !)"
1682230,2017-07-07 12:39:56 UTC,"Hello,
I am back to the far, far machine.
With the 4.8.0-58-generic #63~16.04.1-Ubuntu SMP, all is running fine.
Yours
Alain"
1682233,2018-03-17 03:57:55 UTC,"In fact, Linux kernel 4.14.0-041400rc7 caused Xorg to crash :  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1732574"
1682233,2017-04-12 21:00:23 UTC,"$ xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x46 cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 4 associated providers: 0 name:modesetting"
1682233,2017-05-29 23:04:42 UTC,The test was performed with Linux kernel 4.12.0-041200rc3 from http://kernel.ubuntu.com/~kernel-ppa/mainline
1682233,2017-05-29 23:03:06 UTC,I have downloaded 'linux-firmware_1.165_all.deb' from 'artful'.
1682233,2017-05-28 13:52:38 UTC,"Sorry, I forgot that you also need the signed firmware files that were releases by NVIDIA."
1682233,2017-05-14 23:19:10 UTC,The issue is still exactly the same with Linux kernel 4.12.0-041200rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline :
1682233,2017-04-13 15:01:33 UTC,If you are feeling adventurous you could try the DRM-Next kernel PPA available at http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/ - choose the most recent one.  The instructions to install and uninstall it are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds
1682233,2017-04-13 14:51:21 UTC,"Although the kernel modesetting support for the GTX 1050 was introduced in the 4.8 kernel, the 3D acceleration support (required by Ubuntu's Unity desktop) has only recently arrived in DRM-Next and won't be available until the 4.12 kernel.  See http://www.phoronix.com/scan.php?page=news_item&px=Nouveau-Pascal-Accel-Linux-4.12 I'm guessing XORG is looking for this and you won't need to force XORG to load its 'nouveau' module with the 4.12 kernel."
1682233,2017-06-01 15:35:06 UTC,:(
1682233,2017-11-03 01:40:38 UTC,Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10 (Artful)' :
1682240,2017-05-19 22:52:49 UTC,The RSD PODM fix for this bug is expected to be in 1.2.6 release.
1682240,2017-04-18 10:02:41 UTC,"Hi Newell,"
1682240,2017-04-18 13:24:56 UTC,"Tomasz,"
1682240,2017-04-18 16:31:31 UTC,"Blake,"
1682247,2017-07-27 22:37:25 UTC,"@Monty,"
1682247,2017-04-12 21:31:48 UTC,"Also, I wrote an initial spec before I learned about the RFE process (whoops):"
1682247,2017-06-22 22:48:47 UTC,"@Monty,"
1682247,2017-04-13 22:23:33 UTC,Just to be clear. From what I understand this will mean that we need a component sitting in the tenant's dataplane that will scan the VM on a given TCP port to get the SSH key. Is that right?
1682291,2017-04-18 09:02:58 UTC,"Yes, the file hasn't been updated in a while. Thanks for reminding me."
1682291,2019-01-15 18:02:00 UTC,"Ah, I did make that change to the build process."
1682291,2017-07-12 20:58:15 UTC,"From what I can tell DistUpgradeCache.py calls NvidiaDetection, provided by nvidiadetector.py from , and passes the ubuntu-drivers-obsolete.pkgs as an argument. It looks like the obsolete packages path argument is required by NvidiaDetector so I don't think we can yank it without modify ubuntu-drivers-common."
1682291,2017-06-09 20:58:18 UTC,We should investigate ubuntu-release-upgrader to see if the code which utilizes the obsolete driver list can be removed from it.
1682291,2017-05-10 14:27:16 UTC,Could you add some information about what leads you to believe that so I can make an informed decision about ripping the list and code which checks it out of ubuntu-release-upgrader?
1682291,2017-05-10 09:33:04 UTC,"After a second look, I think that hack was only needed for very old releases, upgrades should go smoothly without the entries in that file now."
1682291,2019-04-09 14:40:29 UTC,I wrote an explanation of the current state of this in LP: #1808874
1682297,2017-04-13 11:37:47 UTC,kali linux packages and repositories are not supported by ubuntu. installation and upgrade issues with their packages to be reported to kali.
1682306,2017-04-13 00:08:53 UTC,Update: I have put together a patch:
1682306,2018-01-25 08:44:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3684
1682309,2017-04-13 00:45:29 UTC,"To provide additional context, I do not use Neutron dnsmasq, but, DHCP server."
1682309,2017-06-12 04:17:46 UTC,[Expired for Ironic because there has been no activity for 60 days.]
1682309,2018-03-13 09:56:48 UTC,Is'nt this bug already addressed by https://review.openstack.org/506173 ?
1682309,2017-04-13 00:25:22 UTC,"Additionally, I noticed ""tftp-server"" should be ""tftp-server-name"".
The best solution to make it vendor agnostic is to not use the names of the options, but, the option numbers should be used."
1682309,2017-04-13 00:29:26 UTC,I discussed this with Sukhdev in IRC.  Pasting context from IRC.
1682309,2017-08-23 18:51:42 UTC,"Judging by https://manpages.debian.org/stretch/dnsmasq-base/dnsmasq.8.en.html, server-ip-address is a valid option for it, but I really wonder if we should use numbers indeed.. Leaving this open, as it seems valid to me."
1682317,2019-09-19 12:03:35 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1682322,2020-02-18 02:14:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682323,2018-11-20 14:38:56 UTC,"I verified the same issue with both 2.4.1 and 2.4.3.
Output format ok : 1280x720  24FPS
Output format ko : 1920x1080 50FPS (faded video segments completely black).
Since my video standard is 1920x1080 50FPS, I would sadly use another editor if no fix is available..."
1682324,2017-04-13 04:11:08 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1682331,2017-04-13 22:53:19 UTC,apport information
1682331,2017-04-28 16:09:04 UTC,"I've changed the subject to be more accurate with the first kernel version affected by this issue.
Please let me know any other thing you need, I will be pleased t"
1682331,2017-04-23 23:32:50 UTC,"Ok, I can confirm that the latest mainline kernel does not fix this bug."
1682331,2017-04-21 13:21:07 UTC,I can confirm that the issue can be experienced also in any ClassmatePC by Intel.
1682331,2017-04-21 12:30:32 UTC,"Yes, It would be possible for me, but these days I'm on holiday and I'm in a place with very poor Internet connection, so I think I'm gonna be able to test the last kernel in a couple of days."
1682331,2017-04-17 17:41:30 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1682331,2017-04-13 22:53:15 UTC,apport information
1682331,2017-04-13 22:53:01 UTC,apport information
1682331,2017-04-13 22:53:09 UTC,apport information
1682331,2017-04-13 22:53:07 UTC,apport information
1682331,2017-04-13 22:53:05 UTC,apport information
1682331,2017-04-13 22:53:03 UTC,apport information
1682331,2017-04-28 16:09:36 UTC,"to help you guys,"
1682331,2017-04-13 22:52:58 UTC,apport information
1682331,2017-04-13 22:52:59 UTC,apport information
1682331,2017-04-13 22:53:12 UTC,apport information
1682331,2017-08-10 13:49:38 UTC,"Well I figured out that this issue is present in any laptop I was able to test, I tried with several laptops with new and not so new hardware and it is always the same. Asus, MSI, Lenovo, HP and Compaq, Dell, Toshiba, Intel Classmate Netbooks have the same problem after kernel 3.17.
Is there anything else that I could try?"
1682331,2017-04-13 22:52:56 UTC,apport information
1682331,2017-04-13 13:00:43 UTC,Can you find which kernel this first occurred in?  Ubuntu mainline kernel PPA's are available at http://kernel.ubuntu.com/~kernel-ppa/mainline/ and instructions on how to install and uninstall them are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds
1682331,2017-04-13 22:52:53 UTC,apport information
1682331,2017-04-13 22:52:51 UTC,apport information
1682331,2017-04-13 22:52:49 UTC,apport information
1682331,2017-04-13 22:52:47 UTC,apport information
1682331,2017-04-13 20:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1682331,2017-04-13 18:55:23 UTC,"To my surprise I have found that the last kernel working fine from mainline is:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.43/"
1682331,2017-04-13 17:15:18 UTC,"Ok, I'm testing one by one and as soon as I get results I'm posting it here.
Thank you!!"
1682348,2017-04-13 14:43:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682349,2017-04-18 22:13:17 UTC,It might be possible to send the picture through. There is an optional parameter for a user image URL in  htdocs/module/lti/webservice/functions/module_lti_launch.php
1682350,2018-08-01 15:19:01 UTC,"Hi Abhishek,
I tried to reproduce the issue but my second instance created successfully and in active state.
can you provide more details about reporducing the same ?"
1682357,2017-04-13 08:26:30 UTC,"The attachment ""unicode-fixes.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1682360,2017-04-13 09:53:10 UTC,"To track the documents we found, we issued this command:
 db.txns.stash.update({""txn-queue"": {$exists: 0}}, { $currentDate: {""observed-on"": true}}, {multi: true})"
1682369,2017-04-13 08:44:22 UTC,Sorry - I did try to add that this is during testing for 17.04 :)
1682369,2017-04-18 22:05:48 UTC,"Hi Sam. Can you please give more information, i.e. what operating system you use? My Chrome prints it without problems (see attached)."
1682369,2017-04-18 22:06:02 UTC,"Hi Sam. Can you please give more information, i.e. what operating system you use? My Chrome prints it without problems (see attached)."
1682369,2017-07-11 04:19:16 UTC,[Expired for Mahara 17.04 because there has been no activity for 60 days.]
1682378,2019-12-18 17:17:23 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/457249
Reason: This repo is retired now, no further work will get merged."
1682378,2017-04-17 13:18:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457249"
1682378,2017-04-13 11:20:58 UTC,Workaround:
1682380,2017-08-30 01:54:20 UTC,This is still an issue in 17.04
1682386,2017-04-30 23:13:47 UTC,"Most places, including BWI airport, I can not access sites with the coop domain."
1682386,2017-04-24 08:02:19 UTC,It seems to work again with systemd 232-1ubuntu3 which disable DNSSEC.
1682386,2017-04-30 23:12:22 UTC,"I was just traveling and could access the coop domain, then got back home and used our house internet and no longer had access. Strange. I thought there had been a fix."
1682386,2017-04-19 15:17:26 UTC,I just updated to Zesty 17.04 and I am having trouble accessing .coop sites using Chromium and Firefox.
1682386,2017-04-30 23:23:50 UTC,I just ran the updater and the issue appears solved (for the moment anyway)
1682386,2017-04-18 14:39:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682386,2017-04-13 09:54:51 UTC,"This is the output of ""systemd-resolve --status"":"
1682386,2017-04-18 14:45:17 UTC,Same problem after upgrading my two computers from Xubuntu 16.10 and from Kubuntu 16.10 to X/Kubuntu 17.04 today.
1682388,2017-04-13 10:05:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456542"
1682388,2017-04-18 10:04:40 UTC,"Change abandoned by zhanggang (<email address hidden>) on branch: master
Review: https://review.openstack.org/456542"
1682388,2017-04-18 12:02:56 UTC,"TroveExtensionMiddleware.__init__() and ExtensionMiddleware.__init__() almost has the same code except the difference below:
ExtensionMiddleware:
        for resource_ext in ext_mgr.get_resources():
            LOG.debug('Extended resource: %s', resource_ext.collection)
            controller_resource = wsgi.Resource(resource_ext.controller,
                                                resource_ext.deserializer,
                                                resource_ext.serializer)"
1682402,2017-04-18 15:35:37 UTC,"I just tested the latest upstream 4.11-rc7 which works fine. I didn't test a previous version of Ubuntu, since I just switched to 17.04 from Fedora 25."
1682402,2017-04-18 23:11:38 UTC,I'd like to perform a reverse bisect to figure out which commit upstream fixes this regression.  It would be very helpful to know the last kernel that had this issue and the first kernel that did not.
1682402,2017-04-13 11:10:12 UTC,Just to rule out hardware issues:
1682402,2017-04-13 11:30:12 UTC,This change was made by a bot.
1682402,2017-04-13 12:33:00 UTC,Some additional info:
1682402,2017-04-17 18:14:08 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1682402,2017-04-18 19:18:11 UTC,"I did some more testing with upstream kernel. The upstream kernel similarly has the occasional freeze where the entire desktop stops responding or updating (while the hardware mouse cursor is usually still movable but clicking doesn't do anything), however unlike the Ubuntu 17.04 kernel it always recovers immediately after 1-3 seconds and responds again. Ubuntu's kernel just gets stuck for me forever - one time I waited over a minute to see if something would wake up again, but the image just remained frozen forever and that's it."
1682408,2017-08-29 23:27:24 UTC,"Personally I think this in an undesirable behavior as today the member does not have a relationship to a neutron port, so there is not way to make a direct one-to-one relationship currently. If the user is just rebuilding the host they would have to re-add the member to the pool(s), so it has a flip side too."
1682408,2017-08-31 08:35:03 UTC,"Dear Micheal,"
1682410,2017-07-20 22:15:12 UTC,"Latest I tried was linux 4.10.0-26.30 through the hwe-edge package.
ecryptfs still didn't mount properly."
1682410,2017-04-13 11:46:56 UTC,Additional info.
1682410,2017-04-13 12:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1682410,2017-04-17 18:12:02 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1682410,2017-04-18 09:08:32 UTC,"Hi @jsalisbury, absolutely. Please wait until I have access to said laptop. I will get back to this."
1682410,2017-04-18 16:06:13 UTC,@jsalisbury is there a packaged way that takes into account drivers and virtualbox dkms builds?
1682410,2017-04-18 16:39:14 UTC,(Update: 4.10.0.14.11 does not fix the problem)
1682410,2017-06-18 04:17:54 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1682410,2017-09-01 20:07:30 UTC,"INTERESTING: In the new kernels, you can still write new files and read them. You cannot read files written in 'old' kernels."
1682410,2017-09-01 20:04:17 UTC,@jsalisbury I tried kernel 4.12.0 and the problem exists.
1682410,2017-09-01 21:13:27 UTC,I think the problem only exists for unencrypted filenames that would previously pass (by default or) by passing the ecryptfs_passthrough option.
1682410,2017-09-01 21:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1682410,2017-09-02 20:08:32 UTC,"I have tried 3 different laptops with 3 different distro's.
Ubuntu 16.04.1, Ubuntu 16.04.3 and Linux Mint 17.
Also I've tried about 8 different kernels."
1682417,2017-04-13 12:01:39 UTC,Please find the part of a cinder-volume.log file attached
1682417,2017-04-19 14:50:25 UTC,"Patch link
https://review.fuel-infra.org/#/c/33322/"
1682424,2019-09-02 04:17:25 UTC,[Expired for ceph (Ubuntu) because there has been no activity for 60 days.]
1682424,2017-04-13 13:03:36 UTC,related ceph bug: http://tracker.ceph.com/issues/19606
1682424,2017-04-26 14:38:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682424,2019-07-03 10:44:55 UTC,The upstream ceph bug was marked as can't reproduce.
1682424,2019-07-03 10:58:22 UTC,If only you've asked me about this one year earlier. Just 6 months ago I've abandoned any hopes for this bug to proceed and I dropped the laboratory installation with this crash I specifically kept for those purposes.
1682430,2017-04-14 09:59:47 UTC,UCA indeed doesn't contain murano-rabbitmq package.
1682430,2017-04-19 13:03:26 UTC,Is it missing deliberately or by mistake?
1682434,2020-12-28 04:06:37 UTC,"I suspect this is an issue with the GTK# or mono.addins installation and I'd suggest trying the latest versions of those.
Regardless, for the question about porting to WPF - this would be an enormous undertaking"
1682449,2020-11-23 04:17:20 UTC,[Expired for openjfx (Ubuntu) because there has been no activity for 60 days.]
1682449,2020-09-23 17:37:27 UTC, Thank you for reporting this bug to Ubuntu.
1682449,2017-04-14 07:22:48 UTC,"BTW: Mine is a fresh install of final Zesty release, not an upgraded system."
1682449,2017-04-14 07:13:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682449,2017-04-13 14:32:35 UTC,The java crash report
1682449,2017-04-14 07:19:56 UTC,This seems to be a general problem with JavaFX on 17.04.
1682455,2018-12-19 17:52:41 UTC,"I can confirm what hbchoong is describing: after uninstalling the firefox deb, when searching for ""firefox"" in gnome-software, only the snap version is found. This affects both 18.04 and 18.10."
1682455,2019-11-04 17:40:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682455,2019-02-05 07:42:59 UTC,"Can I please try to understand what the next steps are, if this is being attended to or just simply going to be ignored due to the lack of resources or coordination at Canonical et al?"
1682455,2018-12-18 11:33:14 UTC,"Also affecting latest 18.04.1 LTS, where Firefox is not installed OR when removed. No option to re-install non-snap version of Firefox."
1682455,2018-04-14 20:32:00 UTC,I noticed that yelp was also complaining about missing help-browser icon until today when it started using native AppStream metadata instead of letting appstream-generator create the basic metadata from its .desktop. So maybe we could fix this bug sooner by creating that metadata file and including it in the firefox and thunderbird binary packages.
1682455,2018-03-19 12:49:40 UTC,Well our first try for Firefox didn't work. We had a 128x128 app icon in the appropriate hicolor folder. It's a symlink and the appstream issues page warns against using symlinks.
1682455,2017-08-02 10:24:22 UTC,"Okay, changed it back to confirmed, since you requested that and confirmed its existence at the same time. It is up to someone else to decide if the real problem lies with thunderbird or gnome-software. Thanks!"
1682455,2017-07-31 15:37:10 UTC,"This bug should not be classified as invalid, in every Ubuntu 17.04 installation that I do on several computers, thunderbird is not in Gnome-Software, and yet the workaround shown above did not work."
1682455,2017-04-14 16:49:51 UTC,Solved it by removing the local cache of GNOME Software and forcing it to re-download its data
1682456,2017-04-17 05:57:46 UTC,"Uh I pasted the commits in reverse order, but you get the idea..."
1682456,2017-04-17 15:21:50 UTC,"I tested with the updated kernel and unfortunately, it does not resolve the issue.  Since these are recently uncovered issues upstream, could you cherry pick those against the Zesty kernel?  Once we know it's resolved in the latest kernel we can track down what changes needed for Xenial."
1682456,2017-04-13 16:03:41 UTC,To recreate:
1682456,2017-04-17 05:57:11 UTC,Please try Linux kernel at http://people.canonical.com/~khfeng/lp1682456/
1682456,2017-04-13 15:46:41 UTC,"After partitioning two disks with two 1G partitions each, then this script will create two RAID1 devices (md0, md1) to test mdadm --stop commands"
1682456,2017-04-13 15:00:10 UTC,This change was made by a bot.
1682456,2017-04-13 15:47:41 UTC,I run this script to watch whether the sysfs md structure goes away after stopping the device.
1682477,2018-03-26 13:40:23 UTC,"This is more important now, given the recent changes in OpenStack's PTI [1]. Adjusting as necessary."
1682496,2019-09-03 18:25:17 UTC,Related: https://bugs.launchpad.net/kicad/+bug/1841523
1682496,2017-08-23 19:57:33 UTC,"For single unit symbols the auto place algorithm is not needed. (As long as the symbol is not rotated.)
But for multi unit symbols (with differently sized units) it is needed because one can not define the text field positions for each unit separately."
1682496,2017-04-26 00:36:46 UTC,Wouldn't it be easier to just disable the autoplace feature and accept the default field positions?  I'm not sure changing the autoplace routine is necessary.  It doesn't always get it exactly right but overall it does a pretty good job.
1682496,2017-04-13 21:16:56 UTC,"The KLC proposes that power pins are placed at the top and bottom of schematic components. When the library item is imported into eeschema,the RefDes and Value field are moved from the location set in the library and are autoplaced above and centred over the component."
1682533,2019-02-05 22:39:36 UTC,regression in bionic though.
1682533,2017-10-20 18:21:06 UTC,"this didn't work in zesty, but does seem to in artful for me."
1682542,2020-11-13 02:36:09 UTC,"actually, the shell extension(in ubuntu software) Multi Monitors Add-On works, although it is not perfect"
1682542,2017-12-07 17:13:23 UTC,"What keeps me bothering: why should a desktop environment distinguish between ""primary"" and ""additional"" monitors at all? In Unity land, all the monitors are first-class citizens, and this approach works perfectly."
1682542,2017-04-19 17:31:40 UTC,"I have been using dual monitor system for a while now, and I can hopefully add a few use cases that I think are missing from the Shell."
1682542,2017-04-21 14:02:30 UTC,"I'd like to add that the idea for a top bar that clones to each monitor isn't a strange request. Using 2 large, widescreen, monitors means that without the ability to have the same bar on each monitor a user is switching focus more often than is necessary, add another monitor and you've got a huge amount of eye travel for some very basic tasks."
1682542,2017-04-28 14:33:03 UTC,"Users switching from Unity to GNOME... or from almost any other environment to GNOME... are going to find the current panel arrangement inconvenient. I am not used to moving the mouse all the way to the far edge of the other monitor when I want to log out, or suspend, or adjust volume... and I shouldn't have to."
1682542,2017-05-16 21:23:35 UTC,"Hi. I am really missing top-bar cloning on multiple monitor, because I am using dual-head setup as a separate & independent displays, mostly."
1682542,2017-05-16 22:22:48 UTC,"(In reply to marcin.j.nowak from comment #27)

> 2. Both displays are used for work. This mode is best known from the latest
> macOS, where user can just enable separate workspaces (topbar is cloned,
> workspaces are separate). It would be nice to have such possibility with
> Gnome3.
"
1682542,2017-05-17 09:44:48 UTC,Thank you for a reply.
1682542,2017-06-03 18:57:26 UTC,"I think to be possible do that, is necessary:"
1682542,2017-06-04 08:41:08 UTC,"(In reply to Lester Carballo from comment #30)

> I think to be possible do that, is necessary:
>
> 1- Split extensions by categories (this will handled in a good way the
> interaction of an extension with all panels, as the extensions will extends
> for a control class that limited the possibility of the extensions making it
> more controllable).
>    - General extensions.
>    - Panel extensions.
> All panel extensions will have one and only one actor inside the panel, they
> can add more actors inside this actor and this one actor will be provided by
> gnome shell controlled class.
>
> Then it's easy move the actor between panels, as is one actor per extensions.
>
> 2- Allow the possibility of create more than one instance per extension. We
> the can have one extension in one panel and another in another panel or both
> running in the same panel.
>
> 3- Create a panel manager class with a list of available panels. To be
> possible set the actor of the extension in an specific panel.
>
> 4- Allow drag and drop the actor between panel and also set it in a panel
> position, to re-layout the desktop as a user request.
>
> 5- Finally, please considered take a look to the cinnamon implementation,
> where all this and more is possible.
>
> The only real way that this could be possible is if this come from
> gnome-shell. Non official extensions can not defined general desktop
> protocols. So, the desktop is who need to create the general abilities to
> organized functionalists that will not conflicted then all together.
"
1682542,2017-06-04 10:22:26 UTC,"Nikita Goncharuk(In reply to Nikita Goncharuk from comment #31)
I just mention how is implemented in cinnamon. This is one way that is proved. Is not the only one way. Drag and drop extension to some position as a user request just is mentions as one of the possibility that this way will provided.
Clone the actors (is make another instance of the actor only). If you do not clone the extension on deep (and just you clone the actor), you sure will have a lot of problems. For example, where will be displayed the menu of the actor that only have one instances? You can not prevent all possibilities that a third-party extension could introduced."
1682542,2017-11-09 07:15:47 UTC,I agree with comment #2. Just upgraded to Ubuntu 17.10 from 17.04 and the new behavior drives me crazy. Is it upstream that needs to do something or can it be fixed by Ubuntu devs?
1682542,2018-01-08 01:22:40 UTC,"(In reply to Florian Müllner from comment #28)

> Per-monitor workspaces would either require changes to the EWMH spec, or
> GNOME dropping compliance with the spec (see [0] and the
> _NET_CURRENT_DESKTOP/_NET_WM_DESKTOP properties)
"
1682542,2018-01-08 11:31:56 UTC,"This is going very off-topic from the per-monitor top bar request that this issue is about, but well ..."
1682542,2018-10-05 14:06:29 UTC,"I switched from unity to gnome with Ubuntu 18.04, it's quite annoying to have to go to the other monitor just to adjust the audio volume. I think all monitors should have the top bar by default. I agree that login out of the session is not very frequent but adjusting the volume is a very frequent action on the other hand ..."
1682542,2018-10-12 07:35:42 UTC,I second the notion that adding support for multiple top bars would be a step in the right direction for multi-monitor support.
1682542,2018-12-26 09:12:30 UTC,I have same issue as Timothée Jeannin describes. Did you every try to works with 3+ monitors? You want same behavior on all monitors. Yo do not want primary monitor. Primary monitor is history...
1682542,2019-01-11 15:19:58 UTC,I would like to see this implemented too.
1682542,2019-04-29 07:31:26 UTC,"I have upgraded from 16.04 to 18.04 and I am missing the top bar on multiple monitors.
I would like to have this feature by default."
1682542,2019-12-01 11:45:36 UTC,Any update on this?
1682542,2020-08-24 07:50:04 UTC,Also tracking in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3091
1682542,2020-10-26 23:37:39 UTC,I would like to see the time in the top bar or my notifications while playing full screen on the primary screen from steam. Is it too much to ask?
1682542,2020-11-13 02:18:10 UTC,"When I am in the full-screen on the primary monitor, the top bar is blocked, so it is necessary for me to show the top bar in another monitor. It is truely a bug to be fixed, but the Linux seems not to be aware of it."
1682542,2017-04-14 10:43:51 UTC,"I think in general GNOME3 does quite well on multiple monitors, atleast in GNOME shell (don't think I have ever run Classic on my 3 monitor setup). I know a lot of work has gone into the mechanics of supporting multiple monitors over the years. Overview shows your windows grouped on the monitor that they are on. you can move windows between monitors with keyboard shortcuts (or context-menu) etc and lots of other little details have been worked on, like configuration etc."
1682542,2017-04-10 21:07:25 UTC,"I second the need for this. Unity supports tracking the active monitor and shows notifications, opens apps and let me use the dash and HUD on the one currently active. Gnome however forces me to always move back to the primary which requires far more mouse motion."
1682542,2018-04-23 05:41:13 UTC,"Agreed. Distinguishing between monitors serves no purpose. Like everyone else I have strong muscle memory to look to the top right of my screen when I want to see status indicators, or to look to the top to see the time, or to move my mouse to the top right to change the volume. This muscle memory has no concept of whether I am looking at my 'primary' monitor or not, and feels a half second of confusion each time I try to do one of these things on a second monitor, which is the hallmark of bad interface design. I think I'm subconsciously adapting to just not use the second monitor much, and that's a stupid outcome too."
1682542,2017-04-09 05:53:32 UTC,"Created attachment 349547
XFCE"
1682542,2017-03-15 06:39:00 UTC,"Created attachment 347984
Gnome 2"
1682542,2017-03-15 06:39:20 UTC,"Created attachment 347985
Windows 8"
1682542,2017-03-15 06:39:38 UTC,"Created attachment 347986
Windows 10"
1682542,2017-03-15 06:59:12 UTC,"Created attachment 347988
Mate 1.18.0"
1682542,2017-03-16 10:21:47 UTC,"I'm sorry, but I don't understand this."
1682542,2017-03-16 10:40:09 UTC,"(In reply to Allan Day from comment #5)

> > supported
> > multi-monitor similar to how the bottom bar 'window-list' currently does.
>
> Can you be more specific? What feature do you want, exactly?
"
1682542,2017-03-16 14:41:55 UTC,"Presumably the extensions that Gnome itself ships as opposed to ones that 3rd parties supply on http://extensions.gnome.org/ , which would be the responsibility of those 3rd party developers."
1682542,2017-03-16 14:51:33 UTC,"Created attachment 348094
Gnome 3"
1682542,2017-04-09 06:04:41 UTC,Apparently Budgie is planning to fix #436 in part by dropping GTK/Gnome entirely and switching to Qt.
1682542,2017-03-16 14:53:09 UTC,"Compare the MATE 1.18.0 to Gnome 3 picture. It does not appear to be possible currently to make a Gnome 3 desktop look similar to the MATE 1.18.0 (Gnome 2) desktop for multiple monitors. However, it works fine for a single monitor."
1682542,2017-03-15 06:22:25 UTC,"It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3."
1682542,2017-03-16 14:54:58 UTC,"(In reply to Florian Müllner from comment #6)
...

> > Can you be more specific? What feature do you want, exactly?
>
> Probably something like
> https://extensions.gnome.org/extension/323/multiple-monitor-panels/
"
1682542,2017-03-16 16:29:30 UTC,"(In reply to Florian Müllner from comment #11)

> (In reply to Chris Cheney from comment #7)
> > Presumably the extensions that Gnome itself ships as opposed to ones that
> > 3rd parties supply on http://extensions.gnome.org/
>
> No, you don't want that in the extensions. Each extension is separate, so
> what you are asking for here is that apps-menu and places-menu *both* add
> top bars to non-primary monitors. We are definitely not going to add two or
> more stacked panels at the top.
>
> What you probably want instead is an option in gnome-shell to put top bars
> on non-primary monitors, and the aforementioned extensions to handle that
> case.
"
1682542,2017-03-23 06:17:21 UTC,"Is there anything else needed, I noticed the BZ is still set to NEEDINFO"
1682542,2017-03-30 19:11:13 UTC,"(In reply to Chris Cheney from comment #13)

> Is there anything else needed, I noticed the BZ is still set to NEEDINFO
"
1682542,2017-04-03 18:28:35 UTC,"Well, don't know if you are going to do that, but it would be nice to have to have this kind of thing."
1682542,2017-04-09 02:00:30 UTC,"""we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?)"""
1682542,2017-04-09 05:51:30 UTC,"Someone pointed out to me that Gnome Shell is actually the only major desktop environment that doesn't work well with multi monitor setup, so I took a look to see if that was actually true. The only one I found that doesn't is Budgie which is based on Gnome Shell and they are intending to fix the issue in their next release, with an open approved issue #436."
1682542,2017-04-09 05:51:52 UTC,"Created attachment 349543
Cinnamon Desktop"
1682542,2017-04-09 05:52:25 UTC,"Created attachment 349544
KDE"
1682542,2017-04-09 05:52:48 UTC,"Created attachment 349545
LXDE"
1682542,2017-04-09 05:53:15 UTC,"Created attachment 349546
Ubuntu Unity"
1682542,2017-03-16 16:00:28 UTC,"(In reply to Chris Cheney from comment #7)

> Presumably the extensions that Gnome itself ships as opposed to ones that
> 3rd parties supply on http://extensions.gnome.org/
"
1682544,2017-08-21 12:35:05 UTC,Thanks for your report.
1682544,2018-04-30 06:38:03 UTC,"This seems to be working properly as of bionic
x11-utils: 7.7+3build1
gnome: 3.28.1"
1682544,2017-04-13 21:50:58 UTC,Still works fine in XFCE4
1682544,2017-07-02 08:16:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682615,2017-05-16 09:33:42 UTC,"ATM we do not have support for PostgreSQL, also community is discussing to remove PostgreSQL support for OpenStack. Will leave as wish-list but maybe at some point in time get as Invalid due support removal."
1682622,2017-04-14 04:38:20 UTC,This broke my Docker images. :-(
1682622,2017-04-21 14:07:27 UTC,"My docker builds is also broken.
Can anyone else tell me why this package was removed?"
1682622,2017-08-04 15:57:53 UTC,"This is also broke my image based on Ubuntu, which will set `TZ=Asia/Shanghai`, they used to work, but not anymore. It's a behavior change, which affect a lot people, so it shouldn't be changed quitely."
1682622,2017-11-10 16:48:31 UTC,It's concerning that the sister bug https://bugs.launchpad.net/cloud-images/+bug/1682305 was marked as Wont Fix.
1682624,2017-04-13 20:11:29 UTC,"If a bad record is created in Designate, an error message like this will show up in the bind logs

> bad_name-1234.my-domain.net/A: bad owner name (check-names)
"
1682624,2017-09-26 21:12:11 UTC,"Even worse, if a empty record manages to get created in the Sink, it will break DNS replication all together."
1682625,2017-07-17 23:45:17 UTC,"On CMUCL 21b I can't load this on Linux, either, but with a different failure.  If I try"
1682625,2017-07-18 18:44:43 UTC,"I get the same named-readtables error as Elias, which seems to be a CMUCL bug, and/or a named-readtables bug. Indeed, the error happens in a #-sbcl block inside define-api, on a topic where cmucl is similar to sbcl. I have only given a cursory look, but this doesn't seem to be an ASDF failure."
1682625,2017-09-21 15:07:01 UTC,"This issue doesn't seem to be going anywhere. I grabbed a master-checkout of asdf, ran `make; make ext` on it and tried to get"
1682625,2017-09-21 20:35:34 UTC,"I suspect that the way forward is to fix named-readtables for cmucl (or cmucl for named-readtables, depending on whose bug it is)."
1682635,2017-04-17 15:50:50 UTC,"I confirm the crash, r15624 on 64-bit Linux."
1682636,2020-09-22 09:49:09 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1682636,2017-07-29 01:39:56 UTC,"I think I have some ideas for this thing. Inkscape should convert group into group layer when it comes to Krita export. If a Inkscape layer or group contains an image. It should be converted as a separate paint layer on export. For example, group/layer contains something like this."
1682636,2017-07-29 01:41:14 UTC,"Ok, when it comes to filtered vector objects in Inkscape, Krita can't read filters, so by default only filtered vector objects should be converted into paint layer upon export."
1682638,2017-05-14 16:47:50 UTC,same problem but with app icon
1682638,2018-01-05 06:38:13 UTC,"This affect me too. When I install Skype for Linux on Elementary OS Loki, the notifications appear with the title ""Android Studio"" when some one sends me a message."
1682639,2017-04-14 15:53:56 UTC,I would recommend doing an on-line resize.  That code path should work for you.
1682644,2017-09-18 10:11:08 UTC,This bug was fixed in the package linux - 4.4.0-96.119
1682644,2017-08-14 17:19:17 UTC,"------- Comment From <email address hidden> 2017-08-14 13:12 EDT-------
This one hasn't been touched in months... We need to get this fix into a 16.04 SRU..."
1682644,2017-08-18 16:31:29 UTC,Bug description updated w/ SRU template.
1682644,2017-09-01 08:26:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1682644,2017-09-01 08:27:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1682644,2017-09-01 23:59:21 UTC,"------- Comment From <email address hidden> 2017-09-01 19:50 EDT-------
Marking as verification done on Zesty."
1682644,2017-09-02 00:39:21 UTC,"------- Comment From <email address hidden> 2017-09-01 20:30 EDT-------
Likewise for Xenial."
1682644,2017-09-18 09:21:44 UTC,This bug was fixed in the package linux - 4.10.0-35.39
1682647,2017-04-13 21:17:48 UTC,"Note that this in an issue with Kubuntu 17.04 (KDE), but on in Ubuntu 17.04 (gnome)."
1682647,2017-04-14 01:53:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682647,2017-05-23 15:46:12 UTC,VMWare Workstation 12.5.6 Pro running a Kubuntu 17.04 vm. Bug confirmed.
1682653,2017-04-13 21:48:05 UTC,creating a separate post regarding exporter as it seems like it's an entirely separate issue.
1682665,2017-04-13 22:30:53 UTC,"These should all apply to 4.4, 4.8, and 4.10"
1682665,2017-04-13 22:33:01 UTC,"Facebook customer service 1-(850)-366-6203 Facebook Customer Service 1-850-366-6203 Number!!@,New York,USA Facebook customer service 1-850-366-6203 Facebook Customer Service Number!!@ Facebook customer service 1-850-366-6203 Facebook Customer Service Number!!@ Facebook customer service 1-850-366-6203 Facebook Customer Service Number!!@ Facebook customer service Facebook Customer Service Number Facebook Number Facebook customer service Facebook customer service Facebook customer service FACEBOOK 24 hour contact number, FACEBOOK customer support contact number, FACEBOOK customer service contact number, FACEBOOK official number, FACEBOOK official contact number, FACEBOOK 850 contact number, FACEBOOK toll free number, 850 number for FACEBOOK support, FACEBOOK 24/7 support phone number FACEBOOK support phone number,FACEBOOK support phone number,FACEBOOK help phone number, FACEBOOK technical support number.FACEBOOK support number, Facebook customer service, FACEBOOK tech support number, FACEBOOK customer support number, FACEBOOK customer support phone number, FACEBOOK customer service phone number, FACEBOOK customer service phone number, FACEBOOK support phone number.Help@Call 1-850-366-6203/.FACEBOOK 24/7 support phone number,FACEBOOK telephone number for support? call 1850-366-6203@./FACEBOOK contact number, FACEBOOK contact phone number, FACEBOOK contact telephone number telephone number for FACEBOOK online support,FACEBOOK official support number,FACEBOOK official number,FACEBOOK official phone number,phone number for FACEBOOK support FACEBOOK 24/7 support phone number FACEBOOK support number,FACEBOOK telephone number for support "" = FACEBOOK Contact Number 1 850 366 6203 = FACEBOOK Customer Service phone number,FACEBOOK helpline phone number here. Describe FACEBOOK help desk phone number,FACEBOOK helpline phone number here. FACEBOOK Payroll support phone number, 1-850-366-6203 FACEBOOK tech support number Call, 1-850-366-6203 for all type help by FACEBOOK tech support phone number, 1850-366-6203 Intuit FACEBOOK Tech Support Phone Number, 1850-366-6203 FACEBOOK Help Desk Phone Number, 1850-366-6203 FACEBOOK tech support number, FACEBOOK technical support phone number, 1850-366-6203 @ Facebook customer service, 1850-366-6203 FACEBOOK technical support number, 1850-366-6203 FACEBOOK support phone number, 1850-366-6203 FACEBOOK technical support, FACEBOOK Customer Service Phone Number, FACEBOOK Customer Service Number, FACEBOOK Customer Support Phone Number, FACEBOOK Customer Support Number, FACEBOOK Customer Service Helpline Number, FACEBOOK Customer Care Number, FACEBOOK support team phone number, FACEBOOK help number-FACEBOOK Helpline Number; FACEBOOK help phone number-FACEBOOK Helpline Number, FACEBOOK Tech Support Toll free Number, FACEBOOK Support Telephone Number, FACEBOOK Tech Support Telephone number, FACEBOOK Tech Support contact number, FACEBOOK support contact number, FACEBOOK technical support contact number. Call, FACEBOOK tech support phone number, Intuit FACEBOOK Tech Support Phone Number, FACEBOOK Help Desk Phone Number, FACEBOOK tech support number, FACEBOOK technical support phone number, Facebook customer service, FACEBOOK tech..."
1682665,2017-04-17 19:16:42 UTC,"I built X, Y and Z test kernels with the requested commits.  The test kernels can be downloaded from:"
1682665,2017-07-26 15:50:07 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1682674,2017-04-17 14:36:18 UTC,"I just sort of solved it manually.
I set the Media keys to super + the matching key.
I then edited the following setting using dconf-editor.
gsettings get org.gnome.settings-daemon.plugins.media-keys
Where I removed the the <super> leaving just AudioRaiseVolume for example. (So <super>AudioRaiseVolume became AudioRaiseVolume)."
1682684,2017-04-14 01:19:50 UTC,"Seem that since packagekit was found during build, the libqapt backend that provides distupgrade check and offering was not built."
1682684,2017-04-27 12:47:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682686,2017-04-19 15:28:38 UTC,I confirmed I have this problem as well ...
1682686,2017-05-09 14:21:01 UTC,Wanted to report it too. But saw that it has been already reported.
1682686,2017-05-14 12:56:25 UTC,This was fixed in Ubuntu MATE 17.10 recently with the release of mate-menu 17.10.0.
1682686,2017-10-23 13:10:06 UTC,I'm on Ubuntu 17.10 and I can't find the Advanced Menu option in MATE tweak. Has this option been removed?
1682692,2017-04-14 09:13:47 UTC,It turns out to be some issue with local cached libvirt-python.
1682692,2017-04-14 09:22:48 UTC,https://review.openstack.org/#/c/456868/
1682692,2018-02-07 16:38:13 UTC,"This solved the problem for me
pip install libvirt-python==3.2.0"
1682693,2017-04-20 14:38:35 UTC,"Reviewed:  https://review.openstack.org/457335
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c9620d57c84378c6187485d571e60e9da3eb9737
Submitter: Jenkins
Branch:    stable/ocata"
1682693,2017-06-08 21:53:16 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1682693,2017-05-08 22:25:49 UTC,This issue was fixed in the openstack/nova 14.0.6 release.
1682693,2017-05-08 22:10:18 UTC,This issue was fixed in the openstack/nova 15.0.4 release.
1682693,2017-04-26 21:29:05 UTC,"Reviewed:  https://review.openstack.org/457353
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6d1ce4cf5cfa9525dfde14bd55b94e86f5e548c1
Submitter: Jenkins
Branch:    stable/newton"
1682693,2017-04-25 03:50:52 UTC,"Reviewed:  https://review.openstack.org/457336
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=01ffbdf8be1cec567ccebb1d9dcb1b390cfaa31a
Submitter: Jenkins
Branch:    stable/ocata"
1682693,2017-04-18 03:49:52 UTC,"Reviewed:  https://review.openstack.org/456872
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c4820305d2f9ee8d62bcc708baf3fa6dfe7ca960
Submitter: Jenkins
Branch:    master"
1682693,2017-04-18 01:46:12 UTC,"Reviewed:  https://review.openstack.org/457103
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=01dd1a05a213c0cbd0097188418cabe915291c8d
Submitter: Jenkins
Branch:    master"
1682693,2017-04-17 19:19:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/457336"
1682693,2017-04-17 19:19:11 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/457335"
1682693,2017-04-17 15:49:35 UTC,"Kevin, would it be possible to post the actual error message from the logs instead of the returned 500 error? Thanks!"
1682693,2017-04-17 00:51:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/457103"
1682693,2017-04-14 09:25:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456872"
1682693,2017-04-14 03:57:58 UTC,"In http://git.openstack.org/cgit/openstack/nova/tree/nova/db/sqlalchemy/api.py#n2150
we did copied the filters dict
in http://git.openstack.org/cgit/openstack/nova/tree/nova/db/sqlalchemy/api.py#n2188 and
http://git.openstack.org/cgit/openstack/nova/tree/nova/db/sqlalchemy/api.py#n2209
we pop the first tag in tags to do SQL query, as we didn't do deep copy, the
""tags"" or ""not-tags"" key will be still in filters dict but the value has been removed,
as we loop through every cell, Error will happen, and also, the result is incorrect."
1682693,2017-04-17 20:31:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/457353"
1682694,2019-03-22 15:52:50 UTC,Junboli has this been added to the upstream manila docs?
1682694,2020-09-23 22:45:22 UTC,This bug has been addressed by https://review.opendev.org/#/c/630776/ and https://review.opendev.org/#/c/522429/.
1682701,2017-04-15 13:22:38 UTC,Have just upgraded from 16.10 to 17.04 and can no longer connect to the router using my D-Link EDUP 802.11N wireless usb adapter. It worked fine with 16.10.
1682701,2017-04-15 01:21:51 UTC,"I upgraded a 16.10 system with working wireless, to 17.04, and after reboot, the wireless no longer connects."
1682701,2017-04-15 13:17:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682708,2017-04-17 16:31:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682711,2017-04-14 04:44:04 UTC,Talking to Matthew Garrett on irc he said that he thinks this may only be fixable via an UEFI change.
1682711,2017-04-14 04:30:17 UTC,This change was made by a bot.
1682711,2017-04-17 07:54:42 UTC,Is cooling the NVMe is your goal? 4.10.0-19 already has NVMe APST support. No sure if PCIe ASPM matters though.
1682711,2017-04-14 05:24:38 UTC,I sent a follow up email to Lenovo but don't expect to hear back from them until sometime after next Monday.
1682711,2017-04-14 04:25:40 UTC,The setpci commands I used modified the LnkCtl option but not the LnkCap values. I'm not sure but suspect that the LnkCap values are what are causing the problem.
1682711,2017-04-21 01:28:37 UTC,"Kai-Heng,"
1682712,2017-04-19 03:40:47 UTC,"# uname -r
4.11.0-041100rc7-generic"
1682712,2017-04-14 04:30:34 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1682712,2017-04-14 06:07:24 UTC,apport information
1682712,2017-04-14 06:07:25 UTC,apport information
1682712,2017-04-14 06:07:27 UTC,apport information
1682712,2017-04-14 06:07:29 UTC,apport information
1682712,2017-04-14 06:07:30 UTC,apport information
1682712,2017-04-14 06:07:31 UTC,apport information
1682712,2017-04-14 06:07:22 UTC,apport information
1682712,2017-04-14 06:07:32 UTC,apport information
1682712,2017-04-14 06:07:35 UTC,apport information
1682712,2017-04-14 06:07:36 UTC,apport information
1682712,2017-04-14 06:07:38 UTC,apport information
1682712,2017-04-14 06:07:40 UTC,apport information
1682712,2017-04-14 06:07:41 UTC,apport information
1682712,2017-04-18 15:09:07 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1682712,2017-04-14 06:07:34 UTC,apport information
1682712,2017-04-14 06:07:21 UTC,apport information
1682712,2017-04-14 06:07:19 UTC,apport information
1682712,2017-04-14 06:04:00 UTC,apport information
1682712,2017-04-14 06:03:37 UTC,apport information
1682712,2017-04-14 06:03:38 UTC,apport information
1682712,2017-04-19 15:50:26 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1682712,2017-04-14 06:03:42 UTC,apport information
1682712,2017-04-14 06:03:44 UTC,apport information
1682712,2017-04-14 06:03:45 UTC,apport information
1682712,2017-04-14 06:03:47 UTC,apport information
1682712,2017-04-14 06:03:49 UTC,apport information
1682712,2017-04-14 06:03:50 UTC,apport information
1682712,2017-04-14 06:03:51 UTC,apport information
1682712,2017-04-14 06:03:53 UTC,apport information
1682712,2017-04-14 06:03:54 UTC,apport information
1682712,2017-04-14 06:03:55 UTC,apport information
1682712,2017-04-14 06:03:57 UTC,apport information
1682712,2017-04-14 06:03:58 UTC,apport information
1682712,2017-04-19 15:50:06 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1682712,2017-04-14 06:03:40 UTC,apport information
1682744,2017-05-07 00:02:55 UTC,Also affected with on ubuntu 17.04 on a Asus UX305
1682744,2017-11-30 10:31:41 UTC,"Complete newbie here. But also wanted to report this affects 17.10 on a HP Spectre 13"" Intel® Core™ i7-7500U CPU @ 2.70GHz × 4"
1682744,2018-01-19 19:24:04 UTC,"I believe I am having the same issue on Ubuntu 17.10. Using Lenovo Yoga 11e, w/ Intel 7265 wireless."
1682744,2017-10-18 10:54:23 UTC,"> PIOTR from comment 6! You've got it working on 16.04!? Get at me, bro!
"
1682744,2017-10-12 22:42:47 UTC,Experiencing this bug using 7265
1682744,2017-07-26 13:18:14 UTC,Is this gonna be fixed in official Ubuntu 17.04 repos ?
1682744,2017-07-17 19:29:41 UTC,"> Seth, please push the new iw to Ubuntu  ;)
"
1682744,2017-07-17 17:37:09 UTC,The patches are included in our backport tree.
1682744,2017-07-17 17:11:13 UTC,"I haven't tested them as I don't feel capable of doing so. I'm just subscribing the bug report and noticed there is a fix. If you need a confirmation it fixes the problem, I could check it, but will need some tips."
1682744,2017-07-17 13:54:41 UTC,"Changing to affect linux since the fix is in the driver, not in the firmware."
1682744,2017-04-14 09:06:56 UTC,"On the same wifi 5GHz network another linux machine (with Intel® Centrino® Advanced-N 6235 adapter) running Zesty works fine.
Other mobile devices (including windows computers) work well with this network."
1682744,2017-06-16 04:27:19 UTC,Does Linux 4.11 fix the issue?
1682744,2017-06-13 12:10:17 UTC,"Seriously this is still open, undecided and unassigned?
This bug is a serious one, it is a blocking one for my laptop (Asus UX305) to install ubuntu 17.04 while ubuntu 16.10 is working fine."
1682744,2017-05-15 08:50:42 UTC,"Not exactly the same problem, but also a firmware bug that happens every time the machine wakes up from suspend (the network is 2.5GHz)"
1682744,2017-04-16 00:31:46 UTC,Related: https://bugzilla.kernel.org/show_bug.cgi?id=195299
1682744,2017-04-15 23:31:14 UTC,"Connecting to 5GHz network also causes driver error on Intel(R) Dual Band Wireless AC 7265, REV=0x210 (on Asus UX305FA). It seems like only Ubuntu 17.04 is affected. I've tried the same on Ubuntu 16.10, Ubuntu 16.04 and Windows 10 - the problem does not occur on any of these."
1682744,2017-04-15 23:15:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682744,2017-04-14 09:35:22 UTC,"Related: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1673344
Related: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1674159"
1682744,2017-07-15 15:41:10 UTC,There is a fix in iwlwifi: https://bugzilla.kernel.org/show_bug.cgi?id=195299. Any chances we'll receive it in linux-firmware soon?
1682744,2017-04-14 09:21:25 UTC,Same machine booted into Widows 10 works well with this wireless 5GHz network
1682753,2017-04-17 16:18:28 UTC,"Reviewed:  https://review.openstack.org/456853
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=70e5fc997dc6c3f2e3faabd9b502c55e4a27524e
Submitter: Jenkins
Branch:    stable/8.0"
1682753,2017-04-18 09:08:07 UTC,"Fix proposed to branch: stable-mu/8.0
Review: https://review.openstack.org/457531"
1682753,2017-04-18 10:05:32 UTC,"Reviewed:  https://review.openstack.org/457531
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=090ed896773f57b943bcecff4d108dda91d8d573
Submitter: Jenkins
Branch:    stable-mu/8.0"
1682773,2017-04-14 09:42:06 UTC,"All lab environment has been realised using Ubuntu 16.04 LTS on VMware Esx. I'm testing Ubuntu Openstack Autopilot via conjure-up, the VM has been created on hypervisor in this way:"
1682779,2017-05-16 17:00:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682779,2017-07-28 15:19:11 UTC,"Hi,"
1682779,2017-07-29 14:36:40 UTC,"I had quite big problems, because my disk crashed and I installed a new system and now I cannot open solutions. It was strange for me, that in another computer with the same version of monodevelop I can open projects."
1682779,2017-07-29 14:48:23 UTC,Another workaround is also to create a project/solution some other way. Then open it by calling and adding the solution filename as command line parameter:
1682779,2017-08-05 15:07:36 UTC,this bug appears to be with the nuget interface trying to fill missing dependencies.
1682779,2017-08-25 19:43:46 UTC,"I have the same problem.
I installed monodevelop with this command:
$ sudo apt-get install -y monodevelop mono-complete gtk-sharp3 libmono-cairo4.0-cil"
1682779,2017-12-11 15:45:16 UTC,"I had the same problem this morning, and was close to changing to some other development environment, until an memory came to me."
1682779,2018-01-31 22:16:08 UTC,i had the same problem
1682779,2018-05-18 09:38:50 UTC,"I tried to change the ""Default solution location"" and I'm not getting the crash anymore. Good catch Selmi!"
1682791,2020-08-24 13:45:19 UTC,"I wonder how it was tested. Did you check the protocol communication or confirm that the connection was actually rejected (instead of having an unrelated connectivity issue, possibly because of the modifications)?"
1682791,2020-08-22 18:31:30 UTC,"I cannot confirm this with the current version of DC++ running all encryption disabled.
Both encrypted and unencrypted CCPM connection attempts to a DC++ with TLS disabled just hang indefinitely. Similarly the other way round, unencrypted CCPM connection attempts from a DC++ with TLS disabled to an unmodified one behave the same.
However, I think some of the safeguards added to AirDC++ in https://github.com/airdcpp/airgit/commit/39a331ad1ec183373b92334dbcbe822f75ae8bf6 should not hurt to have in DC++ as well."
1682796,2017-11-09 03:37:55 UTC,"Do we need to remove ""The Hyper-V Neutron Agent has been fully decomposed from Neutron."" line from hyperv-neutron-agent-decomposition-ae6a052aeb48c6ac.yaml of neutron stable/ocata ?
As i am new contributer please correct me.
Thanks"
1682796,2017-11-09 03:59:44 UTC,"Sapana,"
1682796,2017-11-13 10:43:03 UTC,"Reviewed:  https://review.openstack.org/518961
Committed: https://git.openstack.org/cgit/openstack/reno/commit/?id=bcc65c9e846c829158671ccfbcd0308284f2092a
Submitter: Zuul
Branch:    master"
1682796,2017-11-12 12:10:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519073"
1682798,2020-08-21 12:57:13 UTC,"<eMTee> A missing safeguard but it means here we rely on hubs to distribute the CCPM flag correctly to both sides and according to a comment in AirDC++'s source, some hubs don't do this. Also hubs can remove this feature bit to maliciously force users to unencrypted chat through the hub. Question is here what's best to do, stick to the protocol, accept the hubs' ability to change the advertised features as they wish (which is the common practice on other protocol elements) or leave as is and ignore the missing feature flag for safety reasons."
1682799,2017-04-14 11:00:23 UTC,"After setting scale to 1x1 and back to 0.75x0.75 just now, my music stopped playing[1] and the screen turned yellow ¯\_(ツ)_/¯:"
1682799,2017-04-14 12:45:20 UTC,lspci:
1682799,2019-02-09 15:32:06 UTC,Is this still an issue now that Chromium 71.0 is the currently supported version?
1682799,2019-03-02 11:20:40 UTC,"Yes, that's still the case."
1682806,2017-04-14 17:22:39 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1682806,2019-06-21 16:51:41 UTC,hebcal 4.18-1 https://bugs.launchpad.net/ubuntu/+source/hebcal/4.18-1 was synced from Debian and will be part of Ubuntu 19.10.
1682821,2018-01-20 07:38:24 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-787
1682822,2017-04-14 15:46:29 UTC,Confirmed.
1682823,2019-09-19 12:03:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1682825,2017-04-14 14:27:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/456913"
1682835,2019-12-18 16:47:45 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/465602
Reason: This repo is retired now, no further work will get merged."
1682835,2019-12-18 16:47:40 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/465601
Reason: This repo is retired now, no further work will get merged."
1682835,2017-06-15 13:38:11 UTC,"Reviewed:  https://review.openstack.org/465591
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=22e7dcb5396b503636c0a2f4ba14f100fd2850d1
Submitter: Jenkins
Branch:    stable/mitaka"
1682835,2017-05-17 14:22:47 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/465602"
1682835,2017-05-17 14:22:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465601"
1682835,2019-12-18 17:17:12 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/458879
Reason: This repo is retired now, no further work will get merged."
1682835,2017-05-17 14:09:21 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/465591"
1682835,2017-05-11 10:05:20 UTC,"Reviewed:  https://review.openstack.org/458851
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=e6907520ae67ad35105ecbf609161c4bf0901f10
Submitter: Jenkins
Branch:    stable/mitaka"
1682835,2017-04-28 15:02:29 UTC,"Change abandoned by Sergey Vasilenko (<email address hidden>) on branch: master
Review: https://review.openstack.org/458881"
1682835,2017-05-03 12:45:36 UTC,"Reviewed:  https://review.openstack.org/458881
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=d096bfe121cba47ae27f5f803d3d65b239910c1e
Submitter: Jenkins
Branch:    master"
1682835,2017-04-28 15:02:36 UTC,"Change abandoned by Sergey Vasilenko (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/458880"
1682835,2017-04-28 15:02:21 UTC,"Change abandoned by Sergey Vasilenko (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/458879"
1682835,2017-04-21 15:18:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458881"
1682835,2017-04-21 15:17:49 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/458880"
1682835,2017-04-21 15:17:37 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/458879"
1682835,2017-04-21 13:59:04 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/458851"
1682835,2017-05-03 12:56:38 UTC,"Reviewed:  https://review.openstack.org/458880
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=f7466d00c406e0fac03d0e012b21107933574bdd
Submitter: Jenkins
Branch:    stable/ocata"
1682841,2017-04-14 16:04:25 UTC,"Fix proposed to branch: openstack-ci/fuel-6.1/2014.2
Change author: Dmitry Mescheryakov <email address hidden>
Review: https://review.fuel-infra.org/33131"
1682841,2017-04-18 10:18:41 UTC,The issue could be reproduced with the following patch into pyamqp: http://paste.openstack.org/show/606989/
1682842,2017-04-15 04:43:06 UTC,Solution:
1682853,2018-01-25 09:13:28 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1803
1682874,2018-05-20 17:36:57 UTC,">Reporter, is this still present on 17.10?
I believe it was.
"
1682874,2018-05-20 18:03:40 UTC,"Thanks Scott, please do so."
1682874,2018-03-01 21:37:54 UTC,"No, marking as Invalid because the release is EOL is not correct. Please don't do this, dino99."
1682874,2017-05-10 13:00:00 UTC,I assume synaptic has a problem with packages like wine32 which are not available on the native architecture:
1682874,2017-08-08 20:57:04 UTC,">>Yes, wine32 is installed at your computer. But if it was not installed,
>>then you would get the above mentioned message.
>But it IS installed and I DID get the above-mentioned message...!
"
1682874,2018-05-20 18:08:01 UTC,"Besides that, bug triaging work is of course hugely appreciated!"
1682874,2017-06-30 02:38:39 UTC,">Yes, wine32 is installed at your computer. But if it was not installed,
>then you would get the above mentioned message.
But it IS installed and I DID get the above-mentioned message...!
"
1682874,2018-02-27 08:35:39 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1682874,2017-05-10 13:01:55 UTC,(see my last comment in the bug tracker)
1682874,2017-06-22 21:42:04 UTC,"Sorry, for the long delay."
1682874,2017-05-02 00:37:56 UTC,"As of Lubuntu 17.04, the situation is the same.
------------------------------------------
scott@scott-ASUS-M2N68-AMPLUS:~$ uname -a
Linux scott-ASUS-M2N68-AMPLUS 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
scott@scott-ASUS-M2N68-AMPLUS:~$ lsb_release -dsc
Ubuntu 17.04
zesty
scott@scott-ASUS-M2N68-AMPLUS:~$ echo $DESKTOP_SESSION
Lubuntu"
1682874,2017-05-11 02:08:03 UTC,I don't quite understand your answer...
1682893,2017-04-14 18:16:26 UTC,"Testing again I ran do-release-upgrade, exited and immediately checked updates-available."
1682896,2017-04-14 18:25:49 UTC,"Dan confirmed for me that this is wrong.
The user of stream data just has to know the prefix (or '--image-family')."
1682896,2017-10-18 16:55:57 UTC,"My above comment incorrectly stated '--image-family',
it should have been '--image-project'."
1682899,2017-04-14 23:46:39 UTC,I'd try using a circular path with eight nodes for the PaP... 4 bezier nodes is not very accurate.
1682899,2017-04-15 01:44:27 UTC,"PS: An 8 sided polygon converted to path, with nodes set to smooth works well."
1682899,2017-04-15 07:50:35 UTC,"Thanks Tyler, great Tip, works perfectly!
Just noticed simply adding Pattern along Path already deforms the circle without pasting/linking anything."
1682899,2017-04-15 08:17:33 UTC,"The Deformation is because the Circle only has 4 Nodes, adding 4 further Nodes to the Circle resolves the Problem."
1682899,2020-08-12 17:27:55 UTC,"Hi - thanks for reporting this bug, as part of the bug migration to GitLab, I've closed this issue here. You can still track the issue at https://gitlab.com/inkscape/inkscape/-/issues/1389"
1682913,2017-04-20 11:08:16 UTC,"It does; in fact, the login screen is pretty much all black. So does Payday 2 (loading/credits screens are black apart from the text) and probably other games I haven't checked."
1682913,2017-04-26 14:17:19 UTC,"I can reproduce the black screen thing with Faerie on radeon hw, but installing libgles1-mesa doesn't help. So it's just a bug in the radeon DRI driver."
1682913,2017-04-21 14:38:55 UTC,"Just made another test: I installed Steam and Faeria on my old laptop which has a nVidia GPU. I haven't installed the proprietary driver yet, so I'm on Mesa with Nouveau. Faeria works. I haven't tried Payday 2, as the required config is far too high for this PC."
1682913,2017-04-21 13:59:13 UTC,"After adding Oibaf's (Mesa devel 17.1.x) and/or Padoka's (Mesa stable 17.0.4) PPA, I still had to manually install libgles1-mesa (which they package) to fix the issues in both games."
1682913,2017-04-20 11:13:15 UTC,"For the record, Faeria looks just fine on my Intel without libgles1-mesa, which btw should not be used by anything provided by Steam. Also, Fedora never packaged it so surely there should be more upset users?"
1682913,2017-04-18 21:01:24 UTC,"GLESv1 support will be removed upstream soon, so it's not coming back"
1682913,2017-04-20 08:02:33 UTC,Depends. Should Faeria show this issue already on the login screen?
1682913,2017-04-19 11:58:20 UTC,"So, what will be the solution for games that need it?"
1682914,2017-04-14 19:40:26 UTC,"(12:19:29 PM) cboltz: just tested - if I remove peer_addr= and addr= it gets parsed as A_RECORD_DENIED
(12:21:22 PM) cboltz: so sbeattie's guess is half the answer ;-)
(12:24:19 PM) sbeattie: cboltz: sort of, in that I don't think libapparmor knows the ""peer_addr"" keyword, but does know the ""addr"" keyword, but the grammer doesn't expect an ""addr"" entry for that type of denial either, I guess.
(12:25:00 PM) sbeattie: (good luck to your own grammer parser in parsing that last sentence)
(12:25:35 PM) cboltz: oh, your sentence is easy to parse ;-)
(12:26:13 PM) cboltz: it's not the typical short english sentence
(12:26:27 PM) cboltz: but germans are used to long and nested sentences ;-)
(12:26:39 PM) ydev left the room (quit: Remote host closed the connection).
(12:32:36 PM) sbeattie: ah, the issue with addr is the grammer expects the right hand side to be a quoted string (or a hexstring) and 'none' is neither.
(12:33:27 PM) sbeattie: at least, based on a cursory exploration
(12:34:20 PM) cboltz: hmm, changing it to   addr=""addr"" peer_addr=""peeraddr""   still leads to AA_RECORD_INVALID
(12:35:42 PM) sbeattie: cboltz: like I said, peer_addr is an unknown keyword to libapparmor, so it will always fail that. try adding just addr=""whatever""
(12:36:54 PM) cboltz: indeed, that works"
1682914,2017-04-15 05:11:47 UTC,"John,"
1682919,2017-04-23 19:23:48 UTC,PS: this is my output when running from terminal:
1682919,2017-04-25 08:40:54 UTC,"GOURY, i'm not lyer
i had take time to make a full installation ..... phatch is not working!"
1682919,2017-11-13 10:54:04 UTC,@florin 's solution of 2017-05-06 worked for me also  - for the benefit of people who might be a bit stuck with implementing it - as I would have been a few years ago:
1682919,2017-04-23 19:22:55 UTC,It says Fix Released. It is to be available soon? This is probably the last thing that stops me from switching from Ubuntu 16.10. Thanks!
1682919,2017-05-06 20:02:55 UTC,I tried something and for me it seems to be working now.
1682919,2017-04-16 20:58:07 UTC,"No it's not, stop lying, there was no updates for years"
1682919,2017-04-16 08:21:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682919,2017-05-06 20:06:07 UTC,"PS: I hope my fix is just temporary, I would not like to have to edit a file (and maybe also get some secondary bugs because of the edit).
PS2: skip the ` sign from the above code, you only need the 3 double quotes to open/close commenting area (to disable code between)."
1682919,2017-04-17 08:00:04 UTC,thanks for your answer.
1682919,2017-05-16 07:50:49 UTC,"This ""temporary fix"" worked for me: http://forums.debian.net/viewtopic.php?f=10&t=130880#p633146"
1682920,2017-05-18 21:25:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682923,2017-04-17 13:12:04 UTC,"Noting after some searching of Twitter that at least one other (non-Evergreen) library, some patrons also actively tweet out public lists they've created, so that might be another place to add share buttons."
1682923,2017-04-17 13:16:33 UTC,I do think we should avoid any approaches that require loading JavaScript or images from a social media site; that would turn the share links from a voluntary action to potential involuntary surveillance of patron's catalog use.  This is just a note of caution; I don't know of any major social media sites that require that for a simple share function.
1682923,2017-04-17 13:31:48 UTC,I like the lists idea and agree on your points in the last comment. Thanks for the feedback Galen!
1682923,2017-04-18 14:13:44 UTC,Love this idea!
1682923,2017-04-20 16:45:43 UTC,"I looked into the sharing methods in a little more detail for the above-mentioned social networking sites. Although all try hard to get people to use their javascript, they all offer a method to share through a simple link. The problem is with the use of branded icons from Facebook and Pinterest. I've read through their guidelines, and in both cases, the use of their icons requires that the web site use the image to link to a Facebook business page or a Pinterest for Business URL. I don't see any language regarding the use of a Facebook Share or Pinterest Save button on a web site, outside of using images loaded from the site. The Twitter guidelines do allow for the use of its icon to share content."
1682923,2018-01-17 15:47:02 UTC,"+1 to Kathy's suggestion of hiding all the button-like text links behind a single icon.  In cases where a library has enabled only one network to display (e.g. they've only turned on Pinterest), perhaps then it could present the button-like text link directly, rather than hiding it?"
1682923,2018-11-05 21:46:52 UTC,"I never got very far with this feature, but I do have a work-in-progress branch at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/kmlussier/lp1682923-social-networking-links that puts the links in the record."
1682924,2017-04-14 22:14:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682927,2018-02-27 08:29:59 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1682927,2018-03-31 04:29:44 UTC,I would if I had the expertise. :-) Thanks for the attention to it!
1682927,2018-03-31 03:09:11 UTC,"This likely won't be completed before 18.04 is released (unless you can contribute a patch before ~ Monday, I won't have the time) but I'll certainly get it fixed for the 18.10 release."
1682927,2018-03-31 03:00:24 UTC,"Just updated -- yes, the bug is still present in 17.10."
1682927,2018-03-07 06:42:59 UTC,"Sorry, I've been lost in GRUB hell for months... haven't updated... will report on current status ASAP. Thanks!"
1682927,2017-04-18 04:21:41 UTC,This is a default setting for lubuntu which is the correct thing for lubuntu.
1682927,2017-04-20 02:48:50 UTC,"Thanks -- regardless of the usefulness of the setting, the bigger issue is that if you go to Preferences -> Openbox Configuration Manager -> Windows and uncheck ""Focus new windows when they appear"" it has no effect, because of this <application> section."
1682927,2018-03-01 21:38:53 UTC,"No, marking as Invalid because the release is EOL is not correct. Please don't do this, dino99."
1682929,2018-01-24 22:40:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1423
1682930,2017-04-14 20:44:19 UTC,"The current solution is using Ubuntu^s App_indicator library. This worked until recently on my GNOME-desk, but not anymore. It is best to revert to GtkStatusIcon.  AppIndicator is dying anyway because official development of Ubuntu^s Unity stopped?"
1682930,2017-04-14 21:28:51 UTC,"GNOME-desktop has an extension that displays and supports AppIndicator icons.
Ref: https://extensions.gnome.org/extension/615/appindicator-support/"
1682934,2017-12-04 15:43:40 UTC,"Hello Brian, or anyone else affected,"
1682934,2017-12-05 08:51:07 UTC,verified the python2.7 uploads for xenial and zesty
1682934,2017-10-06 21:27:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682934,2017-12-04 16:45:20 UTC,"Hello Brian, or anyone else affected,"
1682934,2017-09-28 21:29:56 UTC,This bug was fixed in the package python3.5 - 3.5.2-2ubuntu0~16.04.3
1682934,2017-04-20 13:57:12 UTC,Hopefully I've attached the right files you need.
1682934,2017-09-28 21:29:06 UTC,This bug was fixed in the package python3.5 - 3.5.3-1ubuntu0~17.04.1
1682934,2017-09-18 20:04:17 UTC,I followed the test case in the bug description and installed python version 3.5.1 in /usr/local/bin and did receive the traceback from the description when reinstalling python3.5.  I then modified my /etc/apt/sources.list file to enable -proposed ran 'apt-get update' and then installed python3.5 from zesty-proposed.
1682934,2017-09-18 18:55:37 UTC,"I tried recreating the bug as described in the description and py_compile.py in the version of python3.5 on Xenial does not import _remove_dead_weakref so there is not Traceback when trying to reinstall python3.5 after installing python3.5 in /usr/local/bin.  However, its still possible to verify the fix by confirming that the file /var/lib/dpkg/python3.5.postinst and other postinst scripts now use the full path to python3.5 when calling py_compile.py e.g.:"
1682934,2017-09-18 15:27:46 UTC,"Hello Brian, or anyone else affected,"
1682934,2018-01-18 09:03:19 UTC,This bug was fixed in the package python2.7 - 2.7.12-1ubuntu0~16.04.3
1682934,2017-09-28 21:29:15 UTC,"The verification of the Stable Release Update for python3.5 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1682934,2017-09-06 02:30:42 UTC,"An upload of python3.5 to xenial-proposed has been rejected from the upload queue for the following reason: ""Bug# 1682934 is missing SRU testcase/impact/regresison potential; all bugs are missing a Zesty upload which is requried before we could release the Xenial update.""."
1682934,2017-09-14 16:52:45 UTC,This bug was fixed in the package python2.7 - 2.7.14~rc1-3ubuntu1
1682934,2017-06-10 14:47:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682934,2017-04-15 00:47:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682934,2017-04-18 18:53:39 UTC,"I attempted to upgrade to Ubuntu 17.04 zesty.  That seems to have failed.  Now, when I do `sudo aptitude full-upgrade`, I get the following error messages:"
1682934,2017-04-18 20:48:38 UTC,How did you go about upgrading from 16.10 to 17.04? If you used ubuntu-release-upgrader please include the logs in /var/log/dist-upgrade/ so I can better sort out how things went awry.
1682934,2017-04-19 15:09:41 UTC,"On 18/04/2017 21:48, Brian Murray wrote:

> How did you go about upgrading from 16.10 to 17.04? If you used ubuntu-
> release-upgrader please include the logs in /var/log/dist-upgrade/ so I
> can better sort out how things went awry.
>
"
1682934,2017-04-19 15:37:28 UTC,"On Wed, Apr 19, 2017 at 03:09:41PM -0000, Brian Kelly wrote:

> On 18/04/2017 21:48, Brian Murray wrote:
> > How did you go about upgrading from 16.10 to 17.04? If you used ubuntu-
> > release-upgrader please include the logs in /var/log/dist-upgrade/ so I
> > can better sort out how things went awry.
> >
>
> The upgrade was from the GUI following a regular update. I followed the
> 'new version is available' route and accepted the defaults at each stage
> of warnings about removing old packages.
>
> There are 5.8Mb of files under /var/log/dist-upgrade on my machine, do
> you need them all?  I ask because 'broadband' here means 0.1Mb/s so it's
> a long upload for me!
"
1682934,2017-04-19 18:12:22 UTC,"This comment pertains to the bug report/comment by my above, and *not* to the bug originally reported by Brian Kelly, I believe."
1682934,2017-09-18 15:27:01 UTC,"Hello Brian, or anyone else affected,"
1682934,2017-04-25 23:07:49 UTC,In Brian Kelley's report we can see the following in main.log:
1682934,2017-04-25 23:31:45 UTC,I tested installing python3 using the instructions at https://passingcuriosity.com/2015/installing-python-from-source/ and sure enough I received the same Traceback.
1682934,2017-04-26 07:14:35 UTC,"I too removed the references from /usr/local/lib and also from
/usr/local/bin and ran the 'sudo apt-get -f install' and it fixed
everything, including re-installing and configuring Python 3.5."
1682934,2017-04-26 19:01:00 UTC,The problem here is that python's postinst scripts call python without a qualified path:
1682934,2017-06-08 10:35:18 UTC,This bug was fixed in the package python3.5 - 3.5.3-3
1682969,2017-04-14 22:18:19 UTC,I see versão 16.04.2
1682991,2017-04-15 15:43:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1682991,2017-04-20 09:24:32 UTC,Same problem.
1682991,2017-10-07 17:31:35 UTC,same problem here
1683005,2017-04-15 08:38:37 UTC,"The problem is caused by the document size being defined in ""ex"" (relative to the outer font size); so the whole document is like 0x0 for inkscape. Document appears when you change the document unit."
1683005,2017-04-15 09:11:02 UTC,"I'm using inkscape to render SVGs on the server-side from clients. I do not want to interfere in XMLs to work around the problem. I really need a fix, thank you."
1683014,2017-04-18 22:16:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683033,2017-04-15 13:21:34 UTC,"Here is some more details: I select US as region, and in keyboard - I selected Bangla. Instantly, installer crashed and this was produced:"
1683038,2017-05-18 14:07:52 UTC,I wonder why an openstack project would not configure images built to run on openstack to use the openstack metadata service.  Is there a reason?  Generally speaking I think it should perform much better as the openstack metadata service is often quite slow.  Cloud-init crawls the metadata service and on openstack that will take probably 6 requests while EC2 will take several more.  (Openstack provides lots of data in json format in a single payload while Ec2 provides individual bits in individual urls).
1683038,2017-04-15 17:02:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457015"
1683038,2017-05-01 08:04:57 UTC,"Reviewed:  https://review.openstack.org/457015
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=0ff40cf63ca84346b3d7f254a69368e214928a18
Submitter: Jenkins
Branch:    master"
1683047,2017-05-05 14:47:01 UTC,MAAS doesn't support overlapping subnets. In order for us to fix this we would need to explore what is possible but at the moment is not supported.
1683047,2020-06-08 09:32:40 UTC,"Hello,"
1683047,2019-11-20 04:17:34 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1683047,2019-09-20 12:13:52 UTC,"Could you please do a ""subnets read"" via the MAAS CLI when the issue happens to check what's the network model in maas?"
1683047,2019-09-09 03:56:13 UTC,"I've subscribed field-medium, and reset the status to 'new' as this issue is one that we've seen on multiple production sites. I'd therefore like to get the priority re-evaluated since this is causing production downtime to DNS."
1683047,2019-09-09 03:54:16 UTC,A note here:
1683047,2020-06-01 07:54:25 UTC,"Hello,"
1683047,2019-06-24 14:36:44 UTC,@dmitriis can you please post any update here?
1683047,2019-06-24 02:24:44 UTC,can anyone pls help?
1683047,2019-06-20 04:47:26 UTC,See this https://stackoverflow.com/questions/56678949/maas-dhcpd-is-not-on-because-bind9-127-0-0-1954-connection-refused for details...
1683047,2019-06-20 04:43:58 UTC,is there any updates to this issue? I am also experiencing the same problem and I can't reinstall MaaS for this
1683047,2019-01-15 18:06:27 UTC,"I had to reinstall. I manage to find the duplicated subnet but, this thing triggered many other problems, like ""IP already in use"" when it wasn't... Deployments started to fail... Geez..."
1683047,2019-01-15 16:16:53 UTC,"Hey guys,"
1683047,2019-09-09 03:44:28 UTC,Just a me-too on 2.3.6.
1683052,2017-06-18 22:50:51 UTC,"OK. I have a suspicion about what is causing this. In rearranging files, this happens on a regular basis. I deal with lots of graphics. Both large and small graphics. I suspect that memory is topping out with the number of files. I also suspect that the thumbnail cache is involved with this, along with the main memory cache. I've noticed that nemo crashes just as the system shows an error with the thumbnail cache. Then there is the issue of the desktop background being replaced."
1683052,2017-05-24 15:57:22 UTC,I just added a 2nd internal hard drive. I now have one 1 TB hard drive and one 2 TB internal hard drive. Nemo continues to crash at various times. It doesn't matter if I have external hard drives connected or not.
1683052,2017-04-24 16:17:13 UTC,"White this repeats often, it does not repeat on demand."
1683052,2017-05-24 00:00:51 UTC,from Lloyd Hayes post:
1683054,2017-05-31 10:04:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683061,2017-04-16 10:32:40 UTC,"the ubuntu-app-platform package on core devices uses the mir-kiosk snap to display something, so before doing such a switch i guess we'd need to have a wayland-kiosk snap first..."
1683061,2019-10-01 22:36:14 UTC,I'm closing this as Won't Fix since this is not a part of the snappy project. Please report the issue on the upstream project instead. You can also try the snapcraft forum (https://forum.snapcraft.io) for broad discussions on snap packages.
1683063,2017-04-21 18:59:08 UTC,"Well ... instead bailing out, I implemented the missing POLYLINE/VERTEX stuff"
1683063,2017-08-02 14:42:25 UTC,"I tried opening a dxf file (AC1009) exported by Eagle 7.7 and found this bug report via
http://www.inkscapeforum.com/viewtopic.php?t=32212"
1683063,2017-08-02 16:57:00 UTC,"Hi Helge,"
1683075,2017-04-21 17:40:33 UTC,"We have had this same version of rsyslog on trusty on this node since Feb 17, 2016."
1683075,2017-04-20 02:30:44 UTC,I'm downloading the SOS report (taking a long time).
1683075,2018-03-08 06:04:57 UTC,Can you test with the latest version of rsyslog which has a fix for a similar issue as noted in Comment #7?
1683075,2018-02-16 18:01:02 UTC,"Sorry, ignore above comment #14, I meant to post it in the *1683076 bug."
1683075,2018-02-16 17:59:40 UTC,"Was the behavior of rsyslog as described in Bug #1683075, by any chance?
I'm assuming not, as after the resolution of this bug no other problems
were reported(?)."
1683075,2017-04-26 00:37:46 UTC,I cannot find anything obvious related to rsyslog behavior described between 1.25.6 and 1.25.11. I had a look at milestones and the code differences.
1683075,2017-04-21 17:42:20 UTC,"sorry, mild confusion there.  jujud upgrade, not charm upgrade."
1683075,2017-04-21 12:14:11 UTC,"@Gareth,"
1683075,2017-04-21 12:10:11 UTC,"rsyslog:
  Installed: 7.4.4-1ubuntu2.6
  Candidate: 7.4.4-1ubuntu2.6"
1683075,2018-03-06 04:35:14 UTC,"Another instance, no upgrades have happened recently (in fact, I'm trying to prep the site for one)."
1683075,2017-04-21 11:34:49 UTC,"I wonder if it is pure rsyslog failure. At this stage, I am not convinced that we can do much on Juju side either way..."
1683075,2017-04-21 10:48:00 UTC,With the errors and apparently corrupt queues in place we get rsyslogd restarts every minute.
1683075,2017-04-21 06:24:36 UTC,"It was marked Incomplete because we had a question. As you've answered it, you could flip it back to New or Confirmed."
1683075,2017-04-21 05:51:33 UTC,"Marked back as 'confirmed' because 'incomplete' implies waiting on more info - if that's the case, could you please clarify what's needed?"
1683075,2017-04-20 04:38:57 UTC,"We've done that on multiple occasions, and unfortunately the errors just return.  The dir mentioned contains multiple spool files plus .qi files."
1683075,2017-04-21 11:49:04 UTC,"As requested I also checked for any sign of rsyslog being updated on the underlying OS around the timeframe, and can find no evidence of rsyslog package updated in apt history logs across the 3 HA state servers exhibiting this behaviour."
1683075,2017-04-20 03:52:40 UTC,I've now got the SOS report and I can see that rsyslog has corrupt data files as indicated by these messages:
1683082,2017-09-27 07:31:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683094,2017-04-16 12:47:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683097,2017-04-20 15:06:58 UTC,"yes, that’s the place."
1683097,2017-04-19 16:52:31 UTC,You mean this section right? https://docs.openstack.org/project-install-guide/baremetal/draft/install-ubuntu.html#configuring-ironic-api-behind-mod-wsgi
1683101,2017-04-30 08:48:46 UTC,"I am experiencing this bug as well.
I saw this bug with Version 57 and 58 of Chrome."
1683105,2019-04-20 20:24:57 UTC,"Well, the issue is that creating an array differs from machine to machine, from controller card to controller card."
1683105,2019-04-20 18:03:31 UTC,"The way you could be more verbose is by detailing more precise steps on how to reproduce it. I, for example, don't know how to configure hardware fakeraid with RAID 5. Steps on doing that, with an expected result, should be in the bug report."
1683105,2018-08-21 19:57:50 UTC,I'm not sure how I could be more verbose.  It is as simple as install Ubuntu on a computer that has a hardware fakeraid configured for raid5.
1683105,2018-08-17 04:43:49 UTC,Sorry for the delay here.
1683105,2017-12-05 17:46:18 UTC,"Oops, that was artful.  This is bionic."
1683105,2017-12-05 17:43:47 UTC,Attaching debdiff for bionic
1683105,2017-12-01 15:54:30 UTC,"I took a look and yes, it appears to fix the issue."
1683105,2017-12-01 14:45:03 UTC,"I have uploaded a patched dmraid to my ppa, could you please test it and verify that it works and then I will have someone upload it to the main archive:"
1683105,2017-05-02 17:59:22 UTC,"Yes, for raid5 you need the dm-raid module, but iirc, not for a raid0."
1683105,2017-04-28 15:51:29 UTC,"Well, I did more tests and I guess it's okay if we just add the dm-raid module load to the dmraid hook. I just did some more testing and it works out. I withdraw my two patches and upload a new patch that will just add dm-raid force load to the dmraid hook."
1683105,2017-05-12 15:30:40 UTC,"Well, tbh, I am having similar issues on another machine running RAID-0 (striped), so I do think that dm-raid is required on that too. Maybe it's RAID-1 (mirror) that doesn't need it but instead needs the dm-mirror module?"
1683105,2017-04-27 20:16:23 UTC,"Hrm... actually dm-mod is the core device mapper support itself and is still needed.  You just don't see the module anymore because Ubuntu started building it into the kernel instead of as a module, but if you are running a kernel where it is built as a module, it still needs loaded.  Are you running a raid5 or a mirror?"
1683105,2017-04-20 17:24:09 UTC,"The modules file is for the user to manually add modules.  Packages add them via their hook script.  The dmraid hook script currently adds dm-mod and dm-mirror, but I believe the kernel has changed and now the correct modules are dm-raid and dm-mirror.  Can you try editing your dmraid hook script and changing the force_load dm-mod line to dm-raid and see if that fixes it?"
1683105,2017-04-21 16:18:50 UTC,I have confirmed the bug is indeed caused by the hooks calling a module that no longer exists.
1683105,2017-04-21 16:24:58 UTC,"PS: I am aware that dmsetup is a separate package, however I cannot find it on launchpad. I'd be grateful if someone can please redirect this to the correct package."
1683105,2017-04-21 16:30:40 UTC,"The attachment ""Patch to fix issue (change dm_mod to dm_raid)"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1683105,2017-04-21 04:45:28 UTC,"Phillip Susi I will give it a look tonight. I suspect you may be right- I have never seen the dm-mod module even since when I started using RAID, nor has it ever shown up when I do a 'lsmod' on my RAID-enabled systems. I will investigate tonight, and if it is indeed the case, I will try to submit a patch."
1683105,2017-04-25 13:06:52 UTC,"That's part of the dmsetup package; you want the one from the dmraid package, but I suppose I can apply it to the right place."
1683105,2017-04-25 17:02:42 UTC,"Well, if that's the case, then I propose patching both. After all, dm-mod.ko has been renamed to dm-raid.ko and dmsetup's hook is improper for calling it."
1683105,2017-04-21 16:36:57 UTC,"Additional notes:
- I removed all the modules pertaining to raid from /etc/initramfs-tools/modules before patching the dmsetup hook and rebuilding the initramfs image. The system boots, so that means the additional modules are added automatically when dm_raid was added.
- There are two ""modules"" file, one in /etc/initramfs-tools and one in /usr/share/initramfs-tools . It seems that initramfs-tools will only honor the former and ignore the latter.
- The reiserfsprogs package still installs it's initramfs hooks to /etc/initramfs-tools. That one has been filed as a separate bug."
1683105,2017-04-27 23:23:26 UTC,"Well, I'm running RAID5 on my media storage build and RAID0 on my gaming build."
1683110,2017-04-16 07:31:00 UTC,This change was made by a bot.
1683110,2017-04-17 18:50:06 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1683110,2017-04-18 11:05:53 UTC,Tested with linux v4.11-rc7. Still the same.
1683110,2017-04-18 21:17:03 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1683133,2017-04-19 00:32:59 UTC,"Hello Hamza, I suggest asking a question on https://askubuntu.com/ about your booting problem."
1683134,2019-09-29 01:46:26 UTC,"Still the same in:
4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Crashes with memory segmentation fault."
1683134,2018-02-11 18:19:08 UTC,dino99: You're right that 17.04 has reached end of life.
1683134,2018-11-26 01:20:37 UTC,"According to the Red Hat bug report for their Swami package, the Swami segfault is caused by an invalid pointer cast (with GPOINTER_TO_INT) on 64-bit systems. Link here: https://bugzilla.redhat.com/show_bug.cgi?id=1541394#c2"
1683134,2018-02-11 16:31:15 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1683134,2017-04-16 12:13:33 UTC,swami crashed crashed with SIGSEGV in g_type_fundamental()
1683134,2017-04-16 17:28:20 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1683144,2017-04-16 14:17:36 UTC,"Hi, thanks for reporting this issue and help to make Ubuntu better."
1683144,2017-04-16 14:18:59 UTC,The right link for the other bug is: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1327002
1683144,2017-04-16 14:22:23 UTC,Correction!:
1683144,2017-04-16 14:52:59 UTC,"Hi Torsten,"
1683149,2017-04-16 14:43:28 UTC,"If you see the attached images in the bug, the in-built wifi card is inferior to the usb adapter, and with both on the wifi quality suffers. I use Unity, simply because otherwise I cannot connect to the net."
1683161,2017-04-16 16:35:07 UTC,"Also, this is my first bug report. Please feel free to correct me if I did anything wrong in regards to my report, etc. Cheers"
1683162,2017-04-21 11:32:04 UTC,thanks
1683162,2017-04-18 16:12:59 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=781457
1683162,2017-04-18 14:48:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1683162,2019-02-07 23:17:34 UTC,Reported on https://gitlab.gnome.org/GNOME/nautilus/issues/307
1683164,2019-09-29 14:17:20 UTC,"Indeed, thank you! Fixed in master."
1683164,2019-10-01 05:38:06 UTC,Fixed in https://launchpad.net/fatrace/trunk/0.14
1683167,2019-08-15 17:01:11 UTC,"After switching to 19.04, we found this change breaks alert functionality in our servers. We use beep to identify machines that have failing hardware or need to be located."
1683167,2019-08-15 16:58:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683174,2017-06-08 18:19:35 UTC,This issue was fixed in the openstack/freezer-web-ui 5.0.0.0b2 development milestone.
1683179,2017-04-16 20:20:31 UTC,Hmm. I see this in the output of perl -V:
1683179,2017-04-16 20:42:33 UTC,"Hello, I'm one of the perl maintainers in Debian. In Debian we're still finalising the release notes for this issue for our next release; I suspect noone thought about communicating this change for Ubuntu :( A couple of observations that might be helpful to you and others:"
1683182,2017-04-25 10:22:51 UTC,HP 2740P tablet waked away and returned to upside down screen while in standard laptop orientation and no clear way to reset
1683185,2019-09-15 16:54:19 UTC,Migrated to https://github.com/widelands/widelands/issues/528
1683185,2017-04-20 08:14:17 UTC,Disabling the button is a good idea.
1683212,2017-05-10 14:32:47 UTC,"Hmm, this is weird as CPU timeout of 2s is still used despite the fact Ocata contains https://review.openstack.org/#/q/I1f4549b787fd3b458e2c48a90bf80025987f08c4 from the very beginning (timeout was bumped from 2 to 8s)."
1683217,2017-04-17 02:47:18 UTC,"Ahah! One part UI miscue, and two parts user error!"
1683225,2017-04-17 14:30:56 UTC,"I think it may be related to UEFI and secure boot being enabled. Over the weekend I installed one of the updates, I believe it came from the Zorin OS ppa and I enabled UEFI/secure boot. That's when I noticed the problem really starting. As of last night, I disabled secure boot and gnome-shell is barely registering on htop. Laptop is running cool as a cucumber again. BTW, sorry for not making it clear but Zorin OS is fantastic. I do wish it borrowed some of the Elementary OS aesthetics as opposed to so many Windows 8/10 but otherwise it's killer."
1683229,2018-01-09 13:59:56 UTC,"The DpkgHistoryLog.txt shows you installed MySQL Server 5.7, and then MariaDB Server 10.1. This migration path is not supported. From Oracle MySQL 5.7 you need to upgrade to MariaDB 10.2 or newer."
1683229,2018-01-09 13:52:49 UTC,Did you pay attention to the error messages in your terminal?
1683229,2018-05-04 23:18:23 UTC,I am getting the same error whether I try to install MySql or MariaDB on Ubuntu 18.04.  Do I have to throw away two days work and start the entire migration to Ubuntu 18.04 over again? Why after I manually removed the MySQL packages did the MariaDB package still see them?
1683229,2017-04-20 14:33:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683229,2020-08-22 11:59:30 UTC,As I wrote on 2018-01-09:
1683229,2018-12-02 18:13:03 UTC,"Note that purging MySQL 5.7 server prior Installing MariaDB 10.1 won't work neither due to apparmor profile. At least, MariaDB server won't start."
1683231,2017-04-17 05:40:23 UTC,https://review.openstack.org/#/c/453429/
1683245,2017-12-11 13:01:51 UTC,"Does not happen on heat template version 2017-09-01. When I apply the same scenario as in the description, the user gets created in the domain specified (d_test), even though the default project name (p_test) exists in more than one domain."
1683255,2019-05-27 03:59:21 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016."
1683256,2017-08-22 15:50:13 UTC,"We don't execute the job in gate, removing gate-failure tag."
1683256,2017-04-26 18:54:16 UTC,It's not critical in that it doesn't affect a voting job. Lowering to High.
1683260,2018-10-05 08:25:46 UTC,Some LPE (this in particular) work on groups -but not on images.
1683265,2019-05-10 02:23:09 UTC,"It would be nice to get this into a release and deployed to is-mojo-ci. ""charm show"" seems to fail fairly often during CI runs and we don't know why."
1683268,2017-04-18 14:34:21 UTC,"Thank you for your bug report, could you maybe attach an example pdf to the bug?"
1683268,2017-04-18 23:43:22 UTC,This is a small pdf (2x1 cm^2) with 1 um (u = greek symbol) created in Origin on Windows.
1683268,2017-04-19 00:28:49 UTC,Update: Tried opening the test file with different programs. Here is a summary.
1683277,2017-05-16 09:22:43 UTC,Please try the kernel [1]. Note that this will only works on Envy.
1683277,2017-04-17 09:30:12 UTC,This change was made by a bot.
1683277,2017-04-17 18:46:55 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1683277,2017-05-10 07:33:40 UTC,"How can I ensure that this bug is also known to upstream? Will it get reported automatically, or will this bug just sit here and should I report it elsewhere myself?"
1683277,2017-04-17 20:16:10 UTC,Just tested under: 4.11.0-041100rc7-generic
1683277,2020-03-15 15:18:34 UTC,"Andrei,"
1683277,2018-08-31 05:23:11 UTC,"A person necessarily lend a hand to make severely posts I would state. This is the very first time I frequented your website page and thus far? I surprised with the analysis you made to create this.
we provide teh support related to it then you can visit the site https://www.hptechnicalsupportphonenumbersusa.com/hp-customer-care/"
1683277,2017-07-18 04:34:48 UTC,"Benjamin,"
1683277,2017-07-15 22:39:08 UTC,"I do have the same problem on a ProBook 440 G4.
There is a slider for the LED in alsamixer but it doesn't change anything."
1683277,2017-05-17 06:15:04 UTC,"I added this quirk
""SND_PCI_QUIRK(0x103c, 0x81cc, ""HP Envy"", CXT_FIXUP_MUTE_LED_GPIO),""
... based on commit [1]."
1683277,2017-05-16 15:44:45 UTC,"Hi Kai-Heng,"
1683277,2020-03-14 22:49:22 UTC,I found solution which was working for me on HP Probook 450 G4: https://forums.gentoo.org/viewtopic-t-1086606-start-0.html
1683285,2017-04-17 11:58:59 UTC,"""yade compiled fine, but
crashed just after the start. It means that each package should
not only be recompiled but also started to be sure we don`t break
many installations."""
1683285,2017-08-30 09:47:03 UTC,"This should be done in Debian, not Ubuntu. Please continue your work in the linked bug report."
1683288,2017-04-18 02:32:05 UTC,See the fixing patch: https://review.openstack.org/#/c/457100/
1683289,2020-04-23 11:51:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683289,2020-05-10 12:56:52 UTC,This bug also effects me.  Comparing two folders on separate hard disk drives.  Unable to delete files.  Attempting to delete via right-click menu or delete key results in:  g-io-error-quark: Unable to find or create trash directory for [foldername]
1683289,2017-11-07 15:07:54 UTC,Got this bug again on Xenial while comparing of two SSHFS folders mounted as normal user.
1683298,2017-04-17 12:35:06 UTC,"Hi Madhur,"
1683298,2017-04-21 03:37:36 UTC,"Hi Bharath,"
1683298,2020-10-29 20:51:02 UTC,"Hi Madhur, I'm facing a similar scenario with this behavior, have you had success solving it?"
1683301,2020-11-19 20:12:16 UTC,We test with 3.6 and 3.8 now. This bug is no longer valid.
1683301,2017-04-17 21:12:50 UTC,We are going to use this etherpad to track neutron bits: https://etherpad.openstack.org/p/py3-neutron-pike
1683322,2017-08-30 09:02:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683332,2017-04-18 14:09:05 UTC,"I had tried it both ways. It wasn't until I told the installer to erase and
install that I had no issues. I used efi on that install attempt."
1683332,2017-04-18 14:18:00 UTC,"Could be that I was forcing UEFI while still trying to keep the data from
the previous installation that caused the anomaly?"
1683332,2017-04-18 01:06:55 UTC,"On Mon, Apr 17, 2017 at 11:29:37PM -0000, Cindy wrote:

> When I tried to manually install it I got an error (same as above) on that
> file and an efi signed file as well. Im not sure why it wanted to load it.
> My guess is maybe because I initially wanted to preserve data going from
> raring to 17.4? When I tried a reinstallation, forcing UEFI but telling it
> to erase and install, I got no errors.
"
1683332,2017-04-17 23:29:37 UTC,"When I tried to manually install it I got an error (same as above) on that
file and an efi signed file as well. Im not sure why it wanted to load it.
My guess is maybe because I initially wanted to preserve data going from
raring to 17.4? When I tried a reinstallation, forcing UEFI but telling it
to erase and install, I got no errors."
1683332,2017-04-17 22:45:22 UTC,"You say you have successfully installed the shim-signed package?  Were you trying to manually install it, or do you recall any information from the system installer that explained why it was being installed on your system?"
1683332,2017-04-17 21:02:36 UTC,"Yes, it was. I have since been able to successfully install it but not as
an upgrade or a boot option."
1683332,2017-04-17 20:16:11 UTC,"Thanks for reporting.  This appears to be an install made with an Ubuntu 17.04 desktop image, is that correct?"
1683332,2017-04-18 12:25:13 UTC,"If the system boots in EFI mode, it will have a different behavior than if it's booted in other BIOS modes: in EFI, you would see a text-based menu, with a black background when booting from the install CD (or USB). If you're not booting the installer in EFI mode, you would see a graphical menu with the Ubuntu logo."
1683332,2017-04-18 10:20:53 UTC,"I think it was referring to a bios option I have on my system for booting
capabilities between different partitions. It's a Zotac."
1683345,2017-04-19 08:57:44 UTC,"initial situation: Ubuntu 16.04 with 7 Package updates en 7 security updates waiting
After clean boot Ubuntu suggests to update to 16.04.2 with do-release-upgrade"
1683355,2017-04-17 18:29:02 UTC,"Hi Norbert. I'm sorry, but development of Popper is discontinued and only works until Ubuntu 12.04. (https://launchpad.net/popper/+announcement/12042) You may wanna give ""mailnotify"" (http://savannah.nongnu.org/projects/mailnotify) or ""mailnag"" (https://launchpad.net/~pulb/+archive/ubuntu/mailnag) a try? Regards, Patrick"
1683355,2017-04-17 23:41:36 UTC,"Thank you for reply, Patrick!
I know about mail-notification. I used it on my old Gentoo system. It seems to be very outdated and ugly."
1683355,2017-10-15 16:38:26 UTC,For everyone interested - I made it working:
1683359,2017-11-03 13:23:42 UTC,Same problem here with 17.10
1683359,2017-05-02 02:14:02 UTC,Same problem after upgrade to zesty 17.04
1683359,2017-10-27 14:20:45 UTC,At 17.10 same problem
1683359,2017-10-28 07:29:12 UTC,"Well, bug is still not even assigned, so looks like canonical will not fix this."
1683359,2017-04-28 15:24:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683359,2017-04-27 21:55:18 UTC,"Hi,"
1683359,2018-05-03 13:06:01 UTC,">The old (v1.8.3) version still works fine.
"
1683359,2018-05-03 07:15:59 UTC,"If this only happens on Windows 2003, I don't see it getting fixed given
that it's an end of life product. I have no issues with rdesktop to
Windows 2008 upwards with rdesktop 1.8.3."
1683359,2018-05-02 19:56:05 UTC,I have just upgraded to Ubuntu 18.04 with rdesktop 1.8.3-2build1 and it does the same thing. The old (v1.8.3) version still works fine.
1683359,2017-12-07 07:58:07 UTC,After downloading the newest version of rdesktop from https://github.com/rdesktop/rdesktop and recompiling it works fine. Could you please generate a new package?
1683363,2017-11-26 18:44:14 UTC,"Hi Max,"
1683363,2017-04-21 18:31:37 UTC,"I can now confirm, that the workaround with the Fuel Master on MOS 9.0 works:
* you need a 9.0 fuel master
* boot the systems while on MOS 9.0 and wait, until they are recognised by the fuel-master.
* shut down only the 9.0 master
* boot up the 9.2 master and wait until the nodes report to that master.
* create an environment and proceed on MOS 9.2"
1683363,2017-11-20 16:57:53 UTC,"Unfortunatelly, I was not able to reproduce this issue."
1683368,2018-01-23 12:48:53 UTC,Hi Maciej!
1683368,2018-01-23 12:58:01 UTC,It was only half added. I tried using it with snapd 2.30 and it didn't work. The PR adds a missing plug apparmor rule and allows DBus method calls to Introspectable interface.
1683368,2018-01-23 12:35:27 UTC,I've opened a PR addressing the problem: https://github.com/snapcore/snapd/pull/4523
1683378,2020-12-07 04:17:46 UTC,[Expired for pcsc-lite (Ubuntu) because there has been no activity for 60 days.]
1683378,2020-10-07 21:38:04 UTC,"Hi, Is this still an issue? Changing the status to incomplete."
1683383,2019-01-30 08:51:05 UTC,Thanks for providing here attachments of Linux given and Assignee by Xorg Project Team.
1683383,2018-12-13 18:36:31 UTC,-- GitLab Migration Automatic Message --
1683383,2018-09-27 12:36:43 UTC,"@Norbert
Update:
After cleaning up changes and applying your ppa:nrbrtx/xorg-hotkeys it fixes the issue partially - it still change input language on key press, but allow to use shortcuts <Ctrl+Shift+...> (with changing language in the process)."
1683383,2018-09-27 11:09:18 UTC,"@Norbert
I have the same problem on Ubuntu 18.04 LTS with GNOME.
I tried your instruction from #40 without any success. Do you have an idea how to make it work?"
1683383,2018-07-31 12:33:06 UTC,"FYI the bug may be temporarily fixed on Ubuntu 16.04 LTS (with HWE), Ubuntu 18.04 LTS (and Mint 19) using packages from my PPA ( https://launchpad.net/~nrbrtx/+archive/ubuntu/xorg-hotkeys or "" ppa:nrbrtx/xorg-hotkeys "" ). It contains patched Xorg (with patch from kyak - https://aur.archlinux.org/packages/xorg-server-bug865/ ). Thank you very much again, kyak!"
1683383,2019-03-12 12:25:51 UTC,"Yes, I confirm the bug."
1683383,2018-06-30 10:39:12 UTC,"@Norbert
Is there a way to apply this patch to debian stretch (xorg 1.19.2)?"
1683383,2018-03-03 10:27:47 UTC,https://gist.github.com/zorn-v/df0dccd14af81e017fbe8a4e1523ddf5
1683383,2018-04-04 14:28:29 UTC,@Norbert
1683383,2018-03-12 05:42:13 UTC,This helped me:
1683383,2018-03-08 00:20:28 UTC,"The attachment ""Patch for Bionic Beaver 18.04 LTS, it fixes the problem"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1683383,2018-03-07 21:34:59 UTC,"I attached patch from ArchLinux AUR (https://aur.archlinux.org/packages/xorg-server-bug865/, https://aur.archlinux.org/cgit/aur.git/tree/freedesktop-bug-865.patch?h=xorg-server-bug865 ). This patch is stable and reliable. ArchLinux users are happy with it."
1683383,2018-03-05 06:33:38 UTC,"Viktor, could you please elaborate how exactly that may be useful here?"
1683383,2018-03-05 05:53:26 UTC,"Did somebody tested Russian rulemak keyboard layout? It is between the extra layouts. It is based on russian layout with latin letters. I' m not a russian man, but I think, just testing first is a good idea!"
1683383,2019-05-20 06:37:56 UTC,I like the helpful info you supply to your articles. I’ll bookmark your blog and take a look at once more here frequently. I am somewhat sure I will be told plenty of new stuff right right here! Good luck for the following!
1683383,2018-04-07 10:29:15 UTC,@khurshid-alam
1683383,2019-05-22 11:14:47 UTC,"An extensive yet tactical take on your Career Episodes can help represent everything that makes you an asset to the Engineers Australia. Career Episodes can open those closed doors comfortably. They demonstrate the key skills, the experience, and the expertise you bring along in your engineering domain. Every one of the three episodes is required to touch base on unique projects and experiences, and your role, and strategies. At CDRReport, we have that expertise to make your Career Episodes sound valid and convincing.
https://www.cdrreport.org/cpd-examples-samples/
https://www.cdrreport.org/how-to-create-a-perfect-resume-for-engineers-australia/"
1683383,2019-07-23 20:29:16 UTC,"Just a silent reminder: I have created a PPA ( https://launchpad.net/~nrbrtx/+archive/ubuntu/xorg-hotkeys ) with patched packages for Ubuntu 16.04 LTS (xenial, with HWE) and upwards (including upcoming 19.10), use its description for instructions."
1683383,2019-06-18 13:38:46 UTC,<email address hidden>: Why did you reopen this task without any comment explaining the reason? See comment 201?
1683383,2018-03-02 20:45:21 UTC,From duplicate bug 1720364 report.
1683383,2020-08-24 02:05:59 UTC,"Please propose any fixes on the Gitlab site and link them to:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/258"
1683383,2020-08-22 07:54:09 UTC,"To whom it may concern, I have uploaded xorg-server 1.20.8 packages for Ubuntu 18.04.5 amd64 (with the patch from https://bugs.freedesktop.org/show_bug.cgi?id=865 applied) to https://drive.google.com/drive/folders/1s4NavrQ4LBrafbTBd3ASRZ22vK7Nblvc?usp=sharing"
1683383,2020-04-15 06:19:35 UTC,Is there a reason this bug is open when bug 36812 is also reopened?
1683383,2019-12-05 10:06:19 UTC,Found your post interesting to read. I cant wait to see your post soon. Good Luck with the upcoming update. This article is really very interesting and effective. take a look at the link here for Best Places to Order Personal and Business Checks Online - https://the-balance-54.webself.net/blog/2019/12/03/best-places-to-order-personal-and-business-checks-online
1683383,2019-12-05 09:55:56 UTC,"Found your post interesting to read. I cant wait to see your post soon. Good Luck for the upcoming update. This article is really very interesting and effective.
Best Places to Order Personal and Business Checks Online - https://the-balance-54.webself.net/blog/2019/12/03/best-places-to-order-personal-and-business-checks-online"
1683383,2019-11-16 04:44:59 UTC,this is informative
1683383,2019-10-13 07:14:15 UTC,"At Best CDR Writing, we are providing you the best CDR and RPL reports atan affordablr cost. We will deliver you 100% pilagarism free and best quality work.
https://bestcdrwriting.com/"
1683383,2019-07-24 06:08:02 UTC,Norbert: and it is working great! I wish Canonical would just pick it up.
1683383,2019-07-23 18:49:16 UTC,"Cosmic is EOL since July 18, therefore the tag is removed"
1683383,2019-07-23 15:37:46 UTC,"Its not a bug, its a feature... of X server ))"
1683383,2019-07-23 12:24:25 UTC,"Daniel, I understand from your change that you think this bug does not affect cosmic?"
1683383,2019-07-22 04:00:11 UTC,"very good post.
http://www.winmilliongame.com
http://www.gtagame100.com
http://www.subway-game.com
http://www.zumagame100.com"
1683383,2019-07-07 21:36:08 UTC,Need some additional help with your essays Barely manage to complete all assignments in time? Stop worrying and contact the team of professional writers of the great essays and get rid of all tasks! https://great-essays.com/article/classification-and-division-essays/
1683383,2019-07-05 09:39:43 UTC,"Looking for a great sample of the philosophical essay? Try reading the Epiphenomenal Qualia Essay sample. Epiphenomenalism and the knowledge argument are distinctly consistent. However, the knowledge-gained argument negates the principle of epiphenomenalism: https://primeessays.com/samples/philosophy/epiphenomenal-qualia.html"
1683383,2019-06-18 11:29:03 UTC,Hi! I have the same issue i would like to know the solution
1683383,2018-03-02 14:40:56 UTC,"Just tested simple idea on Ubuntu 16.04.4 LTS with MATE DE.
Out-the-box it has Xorg 1.18.4 which perfectly allow user to set for example <Ctrl+Shift> keyboard shortcut for keyboard layout switching.
But when I install HWE on 16.04 LTS I get newer Xorg 1.19.5."
1683383,2017-08-16 19:40:40 UTC,Please return the patch back!
1683383,2018-02-24 16:19:05 UTC,All current Ubuntu versions are affected and RHEL too. And nobody cares.
1683383,2017-04-17 18:16:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683383,2017-08-16 16:54:11 UTC,"Пересобрать таки помогло) Аж выдохнул. Жаль, что мейнтейнеры ppa не обновляют оперативно билды для свежих релизов."
1683383,2017-05-28 13:55:53 UTC,сАлюшн пересобрать руками с патчем? хабра такая хабра.
1683383,2017-05-27 15:00:55 UTC,btw
1683383,2017-05-17 15:45:33 UTC,well yeah more than a couple. I actually remember when I got fed up with this and went looking on the net what can be done and later found out that Ubuntu would accept the patch - I was on another distro then. just don't remember when exactly.
1683383,2017-05-17 15:05:58 UTC,That patch that fixes the problem has been applied in Ubuntu for way more than 'couple of years'
1683383,2017-05-17 14:33:27 UTC,"Not exactly a bug, it's just how it works by default and that is what the xkb specs supposedly say. So this behavior dates way back certainly more that 15 yrs ))
And the fix was incorporated by Ubuntu only a couple of yrs ago certainly not in 2002 )))"
1683383,2017-05-17 08:55:03 UTC,"Meanwhile I can suggest a partial workaround for the problem:
You can map layout switching to LEFT Ctrl+Shift and right keys will be available for using with shortcuts."
1683383,2017-05-16 22:54:20 UTC,This annoying bug takes my linux user experience 15 years back to 2002. Is there a way to make Ubuntu great again? Are there any known workarounds for this bug?
1683383,2017-05-06 15:38:30 UTC,"I have it since yesterday, when i decided to update x-server packages"
1683383,2017-04-19 15:14:49 UTC,"I have arch linux installed on another PC and Xorg server from https://aur.archlinux.org/packages/xorg-server-bug865/ works fine for me. Sources of applied patch are attached, is it possible to get it from there?"
1683383,2017-04-19 14:53:42 UTC,Thats the problem - the old patch doesn't work for the newer Xorg server.
1683383,2017-04-19 12:30:17 UTC,please apply the old patch. Let the 17.04 work as the 16.10. Screw the upstream because it could take ages for them to decide
1683383,2018-02-26 10:49:54 UTC,"(In reply to Daniel Stone from comment #191)

> Another, probably better, way to do it would be to define a new flag like
> XkbSA_HasGroupFlags inside the XkbModAction flags field when group_flags and
> group_XXX are valid rather than potentially garbage. That would avoid the
> whole version-negotiation nightmare, as nothing appears to be too picky
> about extra flags being defined.
>
> Five years later, it would also be good to have support inside libxkbcommon
> (which has a pretty decent test suite) and xcb-proto for the flags.
"
1683383,2017-04-18 05:11:20 UTC,And if you had a look at the upstream bug you'd see that the patch doesn't work. It needs to get upstream first anyway.
1683383,2017-04-18 07:52:22 UTC,I had the same problem.
1683383,2017-04-18 15:56:38 UTC,Timo Aaltonen (tjaalton) wrote 10 hours ago: 	#3
1683383,2017-08-23 05:59:01 UTC,manual patching recipe (thx Artem Kovalov) for Ubuntu 16.04.3
1683383,2017-08-24 17:48:37 UTC,I uploaded xorg-server 1.19.3 packages for 17.04 with included patch from https://bugs.freedesktop.org/show_bug.cgi?id=865 to PPA ppa:spvkgn/xorg-patches
1683383,2017-08-24 17:52:00 UTC,Also .deb files are available for download here https://launchpad.net/~spvkgn/+archive/ubuntu/xorg-patches/+sourcepub/8200875/+listing-archive-extra
1683383,2017-09-22 07:23:26 UTC,I uploaded xorg-server 1.19.3 packages for 16.04.3 i386 with included patch from https://bugs.freedesktop.org/show_bug.cgi?id=865 to https://drive.google.com/open?id=0B_avx7RnFL6Ub1hESFZLT21iaG8
1683383,2018-02-24 16:17:00 UTC,Did you changed your opinion after for years of not fixing this bug?
1683383,2018-02-16 12:17:53 UTC,Another user here voting for this bug to get patched OFFICIALLY from upstream.
1683383,2017-12-15 19:51:24 UTC,"(In reply to Alex Efros from comment #184)

> There is a patch, working good enough for years without creating any new
> (practical) issues. In comment #161 is was proposed to make it configurable
> option to make everyone happy and let users choose between using compliant
> protocol or working hotkeys.
"
1683383,2017-12-11 10:02:27 UTC,"I patched my Lubuntu 16.04 with the mentioned upward patch few hours ago and everything starts working perfectly. I also tested Linux Mint 18.3 with Cinnamon and everything works as expected without any patches. The problem exists in Ubuntu MATE 16.04 too. All these are 64 bit versions. The patch is created correctly: when I released first button from the sequence, the sequence is executed. This way when I switching locales and keep Shift pressed (I'm using Alt+Shift) I can start writing with capital letter. I hope this information is helpful."
1683383,2017-12-11 09:59:25 UTC,"(In reply to Andreas Wettstein from comment #190)

> No news since.  Apart from the formal proposal, there are some old patches
> for its implementation:
> https://lists.x.org/archives/xorg-devel/2012-November/034427.html
> https://lists.x.org/archives/xorg-devel/2012-November/034430.html
> https://lists.x.org/archives/xorg-devel/2012-November/034429.html
> https://lists.x.org/archives/xorg-devel/2012-November/034431.html
> https://lists.x.org/archives/xorg-devel/2012-November/034428.html
"
1683383,2017-12-10 10:07:26 UTC,"(In reply to Zebediah Figura from comment #189)

> Can anyone shed light, for the outside user, as to the current status of
> this proposal? Thanks.


No news since.  Apart from the formal proposal, there are some old patches for its implementation:
https://lists.x.org/archives/xorg-devel/2012-November/034427.html
https://lists.x.org/archives/xorg-devel/2012-November/034430.html
https://lists.x.org/archives/xorg-devel/2012-November/034429.html
https://lists.x.org/archives/xorg-devel/2012-November/034431.html
https://lists.x.org/archives/xorg-devel/2012-November/034428.html"
1683383,2017-12-07 02:37:53 UTC,"There seems to have been a proposed protocol extension (comment #159 etc.) Can anyone shed light, for the outside user, as to the current status of this proposal? Thanks."
1683383,2017-12-07 00:30:55 UTC,"(In reply to Alex Efros from comment #186)

> (In reply to k0fe from comment #185)
> > (In reply to Alex Efros from comment #184)
> > > There is a patch, working good enough for years without creating any new
> > > (practical) issues. In comment #161 is was proposed to make it configurable
> > > option to make everyone happy and let users choose between using compliant
> > > protocol or working hotkeys.
> >
> > Where is the link to the patch? Where is the instruction like how to apply
> > this patch? And how can this comment be used by an ordinary user (without
> > knowledge of programming) to solve this problem?
>
> As an ordinary Gentoo Linux user, I:
> - download patch attached to this issue named ""The same patch, but based on
> 1.19.1 (fixed)"" into directory /etc/portage/patches/x11-base/xorg-server/
> - run `emerge xorg-server` to reinstall Xorg with this patch applied
> - restart X to enjoy working hotkeys :)
>
> If users of other Linux distributions have issues with this - probably they
> just didn't use ""newer Linux"". </sarcasm>


I'd like to thank you! And great thanks to kyak for the patch!
I confirm that it works for me on ""older"" Gentoo and xorg-server 1.9.5."
1683383,2017-04-18 16:59:45 UTC,"> And if you had a look at the upstream bug you'd see that the patch doesn't work.
"
1683383,2017-11-29 14:54:14 UTC,"(In reply to Kovács Viktor from comment #181)

> Sorry, on newer Linux you can set up hot key combination for that problem as
> graphical UI settings, older Linux versions will not be updated. May I close
> It?
"
1683383,2017-11-13 10:03:16 UTC,"In case you don't need to switch between keyboard layouts, you can get some shortcuts working again if you use the ""Tweaks"" tool for Gnome."
1683383,2017-11-04 20:54:43 UTC,This bug is a duplicate of well known bug 1245473 .
1683383,2017-10-31 14:36:01 UTC,"How to make it works on 17.10?
There is no package xserver-xorg-core-hwe-xxx.
I did this:
1. sudo apt install devscripts
2. apt-get build-dep xorg-server
3. apt source xserver-xorg-core
4. wget https://bugs.freedesktop.org/attachment.cgi?id=129861
5  cd xkb
6. patch < attachment.cgi?id=129861
7. debuild -us -uc"
1683383,2017-10-05 18:36:00 UTC,"Now I understand why ""libs"" like wayland appears. X.org SUCKS."
1683383,2017-10-05 18:06:09 UTC,Also works on 17.10 BTW.
1683383,2017-10-05 15:47:19 UTC,"My script based on Jacob's one.
https://gist.github.com/zorn-v/df0dccd14af81e017fbe8a4e1523ddf5"
1683383,2017-10-05 11:12:02 UTC,"I had the same problem.
Ubuntu Mate 16.04.3 LTS"
1683383,2017-09-25 14:54:01 UTC,"Here's my script based on the gist mentioned on comment #21
https://github.com/plastikat/patch-xkb-layout-switch"
1683383,2017-11-28 22:57:38 UTC,"(In reply to k0fe from comment #185)

> (In reply to Alex Efros from comment #184)
> > There is a patch, working good enough for years without creating any new
> > (practical) issues. In comment #161 is was proposed to make it configurable
> > option to make everyone happy and let users choose between using compliant
> > protocol or working hotkeys.
>
> Where is the link to the patch? Where is the instruction like how to apply
> this patch? And how can this comment be used by an ordinary user (without
> knowledge of programming) to solve this problem?
"
1683383,2017-04-19 10:38:58 UTC,"Same problem, waiting for fix."
1683385,2017-10-31 12:31:27 UTC,"As I look at bug 1669866, bug 1722387 and bug 1705133, it might be a good idea to consider whether it is indeed a good thing to configure columns based on a named IDL class. Is this the reasons why we are getting very long column pickers in some interfaces that include data that will rarely be used? Would it be better to explicitly add all columns rather than adding an entire class at one time?"
1683385,2019-04-17 14:50:40 UTC,Original issue confirmed.
1683385,2019-03-07 18:00:08 UTC,"I'd like to revive discussion on this bug because I'm interested in what others think, and based on Kathy's comment maybe this is the best place. Explicitly adding columns is what I've done here: https://bugs.launchpad.net/evergreen/+bug/1724965 but I don't know if that's the best path forward."
1683385,2019-04-17 14:52:39 UTC,Fix pushed:
1683385,2019-05-23 18:20:00 UTC,Signoff pushed to:
1683385,2019-07-30 16:21:17 UTC,"Given the time that has passed, I've gone ahead and pushed this to master, rel_3_3, and rel_3_2. Thanks, Bill!"
1683389,2017-04-17 16:17:18 UTC,"this change will make things using the shell look not so nice, like asciinema."
1683389,2018-01-23 10:15:19 UTC,"@sergio, we _could_ do it just for 'snap run --shell'."
1683396,2020-05-11 20:01:52 UTC,Is this still an issue? It feels like this was resolved in a later update to maniacs-setup.
1683396,2017-04-17 16:05:00 UTC,Here's a link to merge #59:
1683415,2017-04-17 19:30:45 UTC,"Ahh, if one PPA can break the updater then it does make sense to disable them all during the upgrade process. Like you say an additional step to enable them again once the upgrade is complete would be the solution in this case."
1683415,2017-04-17 19:02:56 UTC,"It seems that in the past it was the case that if one package source failed, then no updates would be executed by the update manager.  I'm not certain if this issue has been fixed."
1683415,2017-04-17 17:48:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683415,2017-04-17 20:50:58 UTC,"The ability of one broken PPA to break the entire process must be addressed, using the command line will ignore a 404 error, but the update manager simply stops at ""Failed to download repository information"", and will not proceed..."
1683442,2017-04-17 18:06:12 UTC,My complete dmesg output from boot earlier today.
1683442,2017-06-07 01:24:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683442,2017-06-07 01:26:05 UTC,I have the same issue with Dell XPS13 9360 and Dell DS1000 docking station (it's a WD-15 in different form-factor). I've tried all possible kernels including 4.12-rc1 and still have to reconnect dock few times per day (some day more often than another - I can't find a pattern too)
1683442,2017-06-07 01:34:49 UTC,I've heard that there is some issue with Wi-Fi power level on Dell laptops. I'll try to disable Wi-Fi when connected to docking station and see if it helps.
1683442,2017-12-05 05:09:26 UTC,Looks like 4.14 kernel fixes issue for me
1683445,2018-06-26 01:39:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683445,2018-06-28 03:35:50 UTC,need fix in xenial.
1683445,2018-07-03 10:46:34 UTC,This bug was fixed in the package unity-settings-daemon - 15.04.1+18.04.20180413-0ubuntu2
1683445,2017-05-29 15:25:49 UTC,"The verification of the Stable Release Update for gnome-settings-daemon has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1683445,2018-07-09 12:24:48 UTC,"Hello Vincent, or anyone else affected,"
1683445,2018-10-17 11:37:36 UTC,This bug was fixed in the package unity-settings-daemon - 15.04.1+18.04.20180413-0ubuntu1.1
1683445,2018-07-09 15:45:07 UTC,"Hi,"
1683445,2018-10-02 08:07:21 UTC,"I've asked our OEM team to look for the hardware to test this on, but they haven't got any.
We're in the position that as far as we can tell nothing is made *worse* by this change, but we can't be sure if it actually fixes the problem or not.  I think this is safe to land now, but if anyone has hardware to test this on, please help."
1683445,2018-10-15 11:32:21 UTC,"After install unity-settings-daemon from proposed on Ubuntu Bionic with Dell Latitude E6430, brightness is working correctly.
Verification done."
1683445,2018-11-22 06:25:57 UTC,The 15.04.1+16.04.20160701-0ubuntu2 xenial update works without visible problem. We don't have people with the right laptop to verify the change at the moment but since the same code change got verified with success on bionic and that we didn't see any regression/problem on other configurations let's mark it as verified (especially that we want to clear the SRU line for another update)
1683445,2018-11-22 16:46:38 UTC,This bug was fixed in the package unity-settings-daemon - 15.04.1+16.04.20160701-0ubuntu2
1683445,2018-07-09 15:31:26 UTC,"Hello Vincent, or anyone else affected,"
1683445,2017-05-29 15:25:39 UTC,This bug was fixed in the package gnome-settings-daemon - 3.24.2-0ubuntu0.1
1683445,2017-05-09 17:09:46 UTC,I am closing the 'linux' portion of this bug because this apparently can be fixed in gnome-settings-daemon and unity-settings-daemon.
1683445,2017-05-16 21:04:46 UTC,"Vincent, is it at all possible for you to test Ubuntu GNOME 17.04 before and after this proposed fix? I don't have the hardware to verify your fix and the Ubuntu Stable Release Update team really likes for bugfixes to be verified."
1683445,2017-04-17 18:12:21 UTC,So as a wokraround:
1683445,2017-04-17 18:31:19 UTC,This change was made by a bot.
1683445,2017-04-17 18:43:35 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1683445,2017-04-17 20:35:57 UTC,"Hi Joseph,"
1683445,2017-05-23 06:02:00 UTC,I believe @Vicent uses Unity instead of Gnome - but I don't know when will they handle my PR tough.
1683445,2017-04-19 09:19:30 UTC,"This issue can be reproduced on another E6430 here, with the same A18 BIOS / 4.10.0-19 kernel. (But the interesting thing is that it cannot be reproduced with its variant, E6430ATG, even if they're all I+N config, and using the same BIOS)"
1683445,2017-04-19 09:57:07 UTC,"The brightness hotkey will change the ""brightness"" level from /sys/class/backlight/nv_backlight/, but it seems that it's actually using the Intel one."
1683445,2017-04-21 07:01:37 UTC,"Verified with Kubuntu / Gnome Ubuntu 17.04 LiveUSB, brightness adjustment still not working on them."
1683445,2017-05-04 07:47:40 UTC,"Okay, didn't know the ""enabled"" part. Originally I was thinking get the value from vgaswitheroo - but ""enabled"" here will do."
1683445,2017-05-04 07:22:24 UTC,"Hi,"
1683445,2017-05-09 19:07:45 UTC,This bug was fixed in the package gnome-settings-daemon - 3.24.2-0ubuntu1
1683445,2017-05-16 15:13:40 UTC,"Hello Vincent, or anyone else affected,"
1683445,2017-05-16 18:55:39 UTC,"Hi,"
1683445,2017-05-05 09:16:00 UTC,Please try USD here: http://people.canonical.com/~khfeng/lp1683445/
1683445,2017-05-05 10:00:33 UTC,BGO: https://bugzilla.gnome.org/show_bug.cgi?id=782211
1683445,2017-05-03 09:45:32 UTC,"nvidia_backlight.c thinks the graphics chip is connected to LVDS, hence create a backlight interface, 'nv_backlight'."
1683445,2017-05-04 08:46:15 UTC,"Hi,"
1683447,2017-04-17 18:15:47 UTC,apport information
1683447,2017-04-17 18:15:35 UTC,apport information
1683447,2017-04-17 18:15:37 UTC,apport information
1683447,2017-04-17 18:15:45 UTC,apport information
1683447,2017-04-17 18:15:41 UTC,apport information
1683447,2017-05-25 12:03:05 UTC,"I have the same problem with a Dell XPS. On 16.04 was ok, and initially on 17.04 after a upgrade also was right (sometimes failed after suspend). But after an update, 3 and 4-finger gestures stopped working definitely."
1683447,2017-04-18 03:49:46 UTC,"This worked fine for me from a live 17.04 usb, but not on a system upgraded from 16.10. (Because of this, it seems unlikely that using an upstream kernel will make any difference."
1683447,2017-04-17 18:43:16 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1683447,2017-04-17 18:31:36 UTC,This change was made by a bot.
1683447,2017-04-22 19:16:59 UTC,I have just upgraded from 16.10 to 17.04 and 3- and 4-finger taps stopped working.  Two finger tap and scrolling works as previously. I’m on ASUS Zenbook.
1683447,2017-04-17 18:15:59 UTC,apport information
1683447,2017-04-17 18:15:57 UTC,apport information
1683447,2017-04-17 18:15:55 UTC,apport information
1683447,2017-04-17 18:15:54 UTC,apport information
1683447,2017-04-17 18:15:52 UTC,apport information
1683447,2017-04-17 18:15:51 UTC,apport information
1683447,2017-04-17 18:15:49 UTC,apport information
1683447,2017-04-17 18:15:48 UTC,apport information
1683447,2017-04-17 18:16:04 UTC,apport information
1683447,2017-04-17 18:15:43 UTC,apport information
1683460,2017-04-17 19:21:19 UTC,"actually this is possible to save again using the ""save as"" in the application menu."
1683460,2017-07-06 11:44:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683460,2017-07-06 14:13:48 UTC,"so it would be more of a feature request than a bug, but could we have a ""save as"" button next to ""save""?
The minimal interface is nice but I was scanning three photos at a time with a flatbed, and couldn't save each picture separately. Never thought of looking into the application menu and ended up downloading xsane and cropping with gimp."
1683468,2020-05-11 20:02:49 UTC,"Is this still an issue, or was this resolved by updates to MAAS or Maniacs-setup?"
1683468,2020-05-11 20:16:15 UTC,"It's been resolved, but I don't recall by what."
1683479,2020-07-03 05:04:12 UTC,DistroRelease: Kali 2017.1
1683491,2017-05-31 17:49:57 UTC,"I reported this also here: https://bugzilla.gnome.org/show_bug.cgi?id=782787
I will further provide updates and attachments in the GNOME Bugzilla issue mentioned above."
1683505,2017-05-05 14:58:17 UTC,"Xenial doesn't have CONFIG_HARDENED_USERCOPY and CONFIG_SLAB_FREELIST_RANDOM, while CONFIG_DEBUG_LIST and CONFIG_DEBUG_CREDENTIALS are off in -generic (so i'm not taking these into consideration) - the only eligible options there is CPU_SW_DOMAIN_PAN."
1683505,2017-06-06 15:06:27 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1057.64
1683508,2017-12-01 03:08:50 UTC,"@vasilj-davidovic,
Yours seems to be the same one as LP: #1732056."
1683508,2017-11-30 20:00:58 UTC,"I can confirm that this bug affects kernels up to 4.13.0-17 but it is a little better on that one.
Tested it on Ubuntu 16.04.3, Ubuntu Mate 17.10 and Linux Mint 18.3."
1683508,2017-10-21 18:33:55 UTC,"Hi, can you add ""elan_i2c.dyndbg=+p"" to kernel parameter, and attach dmesg here?"
1683508,2017-10-26 22:23:56 UTC,"correction info for workaround, it doesn't work every time
output of product name is
80XS
(it is lenovo 320-15ABR notebook with AMD FX-9800P, and 8 GBram)
Can you help me how to replace kernel on live usb disk (created with startap disk creator from 17.10 iso image)"
1683508,2017-04-18 15:34:55 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1683508,2017-06-18 04:17:51 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1683508,2017-10-20 20:48:42 UTC,"Same thing with 17.10
 elan_i2c i2c-ELAN060B:00: invalid report id data (ff)
same fix"
1683508,2017-10-21 20:33:28 UTC,"used livecd (usb stick) of 17.10 this time
edited command before boot"
1683508,2017-10-27 03:34:48 UTC,I don't know. Maybe just install Ubuntu to local disk and install the kernel?
1683508,2017-04-17 21:31:00 UTC,This change was made by a bot.
1683508,2017-10-22 08:47:41 UTC,What's the output of `cat /sys/class/dmi/id/product_name`?
1683509,2017-04-17 22:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1683509,2017-04-18 05:58:30 UTC,Unable to run apport-collect.
1683509,2017-04-18 15:34:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1683510,2017-04-18 15:34:02 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1683510,2017-04-17 22:00:14 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1683510,2017-04-18 05:59:08 UTC,Unable to run apport-collect.
1683512,2017-04-17 23:42:17 UTC,"There are similar files to those which I am expecting to see at the target install location.
I want `libcuda.so.1`, but there are some like `libcudata.so.8`"
1683512,2017-04-28 09:04:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683512,2017-10-21 15:26:42 UTC,"The Nvidia driver 375.66 fixed the window artifact problems, so use that version to avoid the missing link problem.  You can use apt-file search libcuda.so.1   to find which nvidia driver packages contain the file."
1683512,2018-05-06 16:38:31 UTC,('invalid' as in 'not our (theano's) bug')
1683514,2018-08-14 16:25:37 UTC,I'm new to neutron. I want to use this as part of my introduction to neutron development. I've been going over this. Do you know what the possible workflow should be to achieve this? It looks like this can be accomplished by making changes to neutron/neutron/tests/functional/db/test_migrations.py?
1683514,2019-11-04 01:17:20 UTC,"Hi, is this issue still exist?"
1683524,2017-06-17 16:19:24 UTC,A bit more information ...  It seems that logging out of the GUI will also force kill ANY sessions for that userid.  Including any that are logged into console tty1 and tty2 for example.
1683524,2017-06-19 23:40:07 UTC,Best start would be to start removing packages and see which ones stop this bug from taking place? OR start with a clean ubuntu install and start installing elementary packages (perhaps in a manner similar to this one https://elementaryos.stackexchange.com/questions/241/can-i-convert-a-ubuntu-installation-to-an-elementary-installation) until you can see the problem again?
1683524,2017-04-28 21:16:23 UTC,"Is there any idea what is causing the behavior ?  Would be nice to be able to patch it after install, at least for now.  Until a patch update comes out."
1683524,2017-04-19 16:05:22 UTC,"The following occurs whether or not I log in after or before SSH, as soon as I log out in the GUI."
1683524,2017-04-17 23:25:22 UTC,"Discussing this with Nukie, it seems the SSH session gets cut off by a refused connection."
1683536,2017-11-13 23:07:25 UTC,"Snapcraft isn't the one telling you this, it's the store. The store doesn't know the hash of the snap until it's been uploaded, which is why you had to upload it first. In order for this to happen sooner, the store will need to grow an API for it."
1683546,2020-02-21 16:48:14 UTC,"It is hard to confirm that what I've found is actually the cause of this problem, but looking at the traceback and my tests to port turnip to python3, maybe the cause of this bug could be simpler than we thought."
1683546,2017-04-18 15:26:31 UTC,In the past we've guessed that a libgit2 upgrade should help.  I've been working on that today.
1683546,2018-10-05 19:11:16 UTC,I'm obviously not working on this right now ... although I think a libgit2 upgrade is still worthwhile and the next thing to try.
1683552,2017-04-18 02:44:58 UTC,This is a critical/crash level bug as it frequently results in the system being unusable and causes reboots to hang or take a long time to complete (multiple minutes).
1683552,2017-04-18 03:08:42 UTC,More logs;
1683552,2020-03-17 08:00:47 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1683552,2020-05-17 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1683553,2017-04-18 03:13:43 UTC,"Hi Brian,"
1683553,2017-04-23 00:38:07 UTC,"Hi Brian, were you able to complete your upload at a later date? I believe this may have unfortunately been a case of bad timing during a maintenance window."
1683553,2017-04-24 16:55:41 UTC,"Yes, a couple of hours later I was able to complete the upload."
1683572,2017-07-02 22:18:15 UTC,This bug was fixed in the package ukui-control-center - 1.0.3-0ubuntu1
1683576,2018-01-04 11:40:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683576,2018-01-04 11:43:33 UTC,"Seen on AskUbuntu during discussion of the problem ""Command cd behavior"" (https://askubuntu.com/q/992192/66509)."
1683576,2018-01-04 11:48:36 UTC,"Also on ""Ubuntu 17.04 — bash: cd: too many arguments"" (https://askubuntu.com/q/905832/66509)."
1683577,2017-04-19 11:41:25 UTC,apport information
1683577,2017-04-19 11:41:27 UTC,apport information
1683577,2017-04-19 11:41:28 UTC,apport information
1683577,2017-04-19 11:41:29 UTC,apport information
1683577,2017-04-19 11:41:31 UTC,apport information
1683577,2017-04-19 11:41:33 UTC,apport information
1683577,2017-04-19 12:03:18 UTC,apport information
1683577,2017-04-19 11:41:38 UTC,apport information
1683577,2017-04-19 11:48:38 UTC,"More info on the system log:
At 12.xx secs, system boots into desktop with wifi automatically connected and works find.
At 118, 145,225 seconds, three attempts are made to re-connect to the same wifi ssid. First two are successful. The wifi adapter disappears from the network-manager after the third.
At 330 seconds ethernet cable is connected to submit the system log."
1683577,2017-04-19 11:41:23 UTC,apport information
1683577,2017-04-19 12:03:19 UTC,apport information
1683577,2017-04-19 12:03:21 UTC,apport information
1683577,2017-04-19 12:08:29 UTC,"Comments on the latest apport info:
System boots into 4.11rc7 kernel.
After boot, both QCA9377 and USB WIFI are detected by network-manager but both are ""device not ready"" status.
No wifi connections."
1683577,2017-04-19 12:35:04 UTC,"With 4.11rc7 kernel:
1) Ubuntu boots with wifi in ""device not ready"" status.
2) Restarting network-manager recovers both adapters.
3) After sleep/wakeup cycle, both wifi adapters enters ""device not ready"" again."
1683577,2017-04-19 11:41:36 UTC,apport information
1683577,2017-04-19 11:41:21 UTC,apport information
1683577,2017-04-19 11:53:55 UTC,"Hi,Joseph,"
1683577,2017-04-19 11:41:17 UTC,apport information
1683577,2017-04-18 04:26:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1683577,2017-04-18 15:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1683577,2017-04-18 15:30:42 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1683577,2017-04-19 11:39:21 UTC,apport information
1683577,2017-04-19 11:41:19 UTC,apport information
1683577,2017-04-19 11:39:23 UTC,apport information
1683577,2017-04-19 11:39:25 UTC,apport information
1683577,2017-04-19 11:39:27 UTC,apport information
1683577,2017-04-19 11:39:28 UTC,apport information
1683577,2017-04-19 11:39:29 UTC,apport information
1683577,2017-04-19 11:41:35 UTC,apport information
1683577,2017-04-19 11:39:32 UTC,apport information
1683577,2017-04-19 11:39:39 UTC,apport information
1683577,2017-04-19 11:39:41 UTC,apport information
1683577,2017-04-19 11:41:13 UTC,apport information
1683577,2017-04-19 11:41:16 UTC,apport information
1683577,2017-04-19 11:39:43 UTC,apport information
1683577,2017-04-19 11:39:38 UTC,apport information
1683577,2017-04-19 11:39:36 UTC,apport information
1683577,2017-04-19 11:39:35 UTC,apport information
1683577,2017-04-19 11:39:34 UTC,apport information
1683577,2017-04-19 11:39:31 UTC,apport information
1683578,2020-05-17 04:17:29 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1683578,2020-03-17 08:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1683580,2017-05-17 07:23:54 UTC,"Reviewed:  https://review.openstack.org/458358
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=53e6a4d196c084160bbf19ca79c9c6a8880ded3d
Submitter: Jenkins
Branch:    master"
1683580,2017-08-17 19:05:38 UTC,"No worries, thanks for looking out for us! I just wasn't sure what to even look for to see if swift *is* affected. I think I'll close it out for now, and keep this in mind if I ever see failures that mention API extensions :-)"
1683580,2017-08-17 05:30:58 UTC,"I saw DEFAULT_SWIFT_EXT was changed in https://review.openstack.org/#/c/438705/2/lib/tempest.
So I thought swift also may be affected. I am sorry if it was irrelevant."
1683580,2017-07-19 21:43:26 UTC,"This has swift marked as affected, but it seems like there was mainly a problem for neutron... is there anything swift needs to do here? FWIW, I know that swift has had stable patches land in both Newton and Ocata since this was reported..."
1683580,2017-05-24 18:02:10 UTC,"Reviewed:  https://review.openstack.org/459167
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=4f5b809fb2b51daa72e05438ebde394ca83aa904
Submitter: Jenkins
Branch:    stable/newton"
1683580,2017-05-17 07:25:37 UTC,"Reviewed:  https://review.openstack.org/458359
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=f4ebc5a44352daf982b8e91fa335a67f006821f1
Submitter: Jenkins
Branch:    stable/ocata"
1683580,2017-05-15 05:26:01 UTC,"Reviewed:  https://review.openstack.org/459136
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=a22d08f2a4365de103584d3dc3c704ca78d64378
Submitter: Jenkins
Branch:    master"
1683580,2017-04-24 00:05:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459136"
1683580,2017-04-18 03:45:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457452"
1683580,2017-04-18 03:46:14 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/457453"
1683580,2017-04-18 04:19:14 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/457457"
1683580,2017-04-18 04:27:58 UTC,neutron-vpnaas also seems to have same cause.
1683580,2017-04-24 05:37:33 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/459167"
1683580,2017-04-18 06:19:54 UTC,"Reviewed:  https://review.openstack.org/457457
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=29cb04c5e14de3f56ee2a7f842ff4617b4fe3bc1
Submitter: Jenkins
Branch:    stable/newton"
1683580,2017-04-18 06:19:33 UTC,"Reviewed:  https://review.openstack.org/457452
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=5d86e9d1fa9f78356b654c9f4597b4057266bebf
Submitter: Jenkins
Branch:    master"
1683580,2017-04-18 06:19:46 UTC,"Reviewed:  https://review.openstack.org/457453
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=2341f61a1f67962a2c79b6b04840e31c7b5ec79f
Submitter: Jenkins
Branch:    stable/ocata"
1683580,2017-04-18 10:37:46 UTC,DEFAULT_SWIFT_OPT and DEFAULT_VOL_EXT also are changed. But I don't check whether it has the same bug.
1683580,2017-04-20 07:02:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458358"
1683580,2017-04-20 07:03:17 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/458359"
1683588,2017-04-21 13:53:02 UTC,"Hi Alberto,"
1683590,2020-02-09 04:17:34 UTC,[Expired for networking-vpp because there has been no activity for 60 days.]
1683594,2017-04-19 10:46:10 UTC,"We've already added an error message to Horizon and are in the process of backporting it, so there's no point in Docs carrying a workaround for a known error. See https://review.openstack.org/#/c/451318/"
1683594,2017-07-10 12:17:15 UTC,"@robcresswell - The bug / fix you make mention of in [1] deals with the message logged with the file in question has the wrong permissions (as I read it, it needs to be 0600)."
1683594,2017-04-19 22:45:11 UTC,"Good to know it's being taken care of, thank you.
:D"
1683597,2017-06-29 02:09:54 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1683600,2017-09-26 15:38:05 UTC,This bug was fixed in the package ukui-screensaver - 1.0.3-0ubuntu1
1683600,2017-09-04 08:54:01 UTC,NOTE: This bug has been obsolete because all features in screensaver-preferences have been integrated to ukui-control-center.
1683601,2017-09-04 08:46:35 UTC,"So, what is ""a white version"". I think you mean ""vision"" not ""version"". Though I can still figure out the meaning of the title, it would be better to rename it to ""ukui-screensaver-preferences doesn't show black screen when previewing ""Blank Screen"" theme""."
1683601,2017-09-26 15:38:05 UTC,This bug was fixed in the package ukui-screensaver - 1.0.3-0ubuntu1
1683620,2017-04-18 08:28:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457514"
1683620,2017-04-26 05:11:47 UTC,"i'm curious why we need 'image_base_image_ref' in the system_metadata, i didn't found it is very useful."
1683620,2017-11-19 13:33:32 UTC,"Change abandoned by Chaolei Li (<email address hidden>) on branch: master
Review: https://review.openstack.org/457514"
1683647,2019-12-18 17:21:02 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/457520
Reason: This repo is retired now, no further work will get merged."
1683647,2017-04-18 08:42:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457520"
1683647,2017-05-22 13:00:03 UTC,"Hello team,"
1683647,2018-01-16 01:30:06 UTC,"Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/430931
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1683651,2017-10-03 10:11:31 UTC,"I consider this resolved with change I274fb6b7ea0bb2ea81faaa68d783edbaa8ed06c3, which linked to the policy documents for more information on this statement."
1683651,2017-06-27 15:13:43 UTC,"Change abandoned by Njira Perci (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/474706
Reason: I am abandoning this and going to sync with the docs migration project team."
1683651,2017-06-15 16:48:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/474706"
1683651,2017-04-19 16:32:23 UTC,"As far as I can tell it was only the default policy.json file that was removed, but the functionality is still there. I'll research this a bit more to make sure."
1683651,2017-04-19 01:39:02 UTC,"Thanks Pramod, I have contacted the Nova docs liaisons to find out where Administrators can change the flavor access controls following the Ocata release. In case any reviewers know the location and can change the documentation, I have triaged the bug."
1683654,2019-09-26 10:36:03 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1683656,2019-12-18 17:09:59 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/458409
Reason: This repo is retired now, no further work will get merged."
1683663,2018-04-27 00:29:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683699,2017-04-18 09:39:16 UTC,Default Comment by Bridge
1683699,2018-08-01 10:29:44 UTC,"------- Comment From <email address hidden> 2018-08-01 06:20 EDT-------
Ubuntu 16.10 is supported only for 9 months upto July 2017. So closing the issue."
1683740,2017-04-18 11:12:21 UTC,"Already fixed in:
https://github.com/mhass86/cookbook-openstack-network
https://github.com/mhass86/cookbook-openstack-common"
1683740,2017-04-18 12:19:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457598"
1683740,2017-04-18 12:25:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457602"
1683740,2017-09-27 15:49:50 UTC,"Change abandoned by Jan Klare (<email address hidden>) on branch: master
Review: https://review.openstack.org/457598
Reason: there has been no progress on this in the last few months"
1683740,2017-12-22 09:20:12 UTC,"Change abandoned by Jan Klare (<email address hidden>) on branch: master
Review: https://review.openstack.org/457602"
1683741,2019-09-19 11:59:15 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683749,2018-03-18 22:01:31 UTC,This is something I wish I could do; especially when I get the nag emails. :)
1683749,2019-09-17 09:57:01 UTC,"@tsimonq2 I'm not absolutely sure if not nagging should be set, but linking to the bugs is probably already handy."
1683752,2017-06-08 21:53:13 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1683752,2017-05-08 22:25:41 UTC,This issue was fixed in the openstack/nova 14.0.6 release.
1683752,2017-05-08 22:10:17 UTC,This issue was fixed in the openstack/nova 15.0.4 release.
1683752,2017-04-28 17:26:08 UTC,"Reviewed:  https://review.openstack.org/460161
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=41aef64b79e0a1654f237b2783c0ba0ec681c42c
Submitter: Jenkins
Branch:    stable/newton"
1683752,2017-04-28 05:54:18 UTC,"Reviewed:  https://review.openstack.org/458548
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4cd77a28bc5e51f73cff2c1876e5c78159a93207
Submitter: Jenkins
Branch:    stable/ocata"
1683752,2017-04-26 15:22:44 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/460161"
1683752,2017-04-20 15:10:21 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/458548"
1683752,2017-04-18 16:23:09 UTC,"Reviewed:  https://review.openstack.org/457577
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c97c44cdfb35ecbf473ac5c98c2d3a4e9871ee8c
Submitter: Jenkins
Branch:    master"
1683758,2019-09-19 11:59:17 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683760,2017-05-19 13:16:33 UTC,"@kaihengfeng - This has certainly improved the situation. The ""resync failed, issuing reconnect request"" issue has gone away. Multitouch is still not working though. I will try reconfiguring the X server settings to see if I can get it to detect as a multi-touch capable device."
1683760,2018-01-18 04:19:15 UTC,"Not reliably. Sometimes it will fix things when they go wrong, but not more than about 60%."
1683760,2018-01-18 04:03:12 UTC,"Does
$ sudo sh -c 'echo -n ""elantech"" > /sys/bus/serio/devices/serio1/protocol'
still work for you?"
1683760,2018-01-17 14:06:53 UTC,"This is still an ongoing issue even after upgrading to Artful and latest kernel releases. The  kernel still intermittently detects the mouse differently. Even when it DOES detect it as an ETPS/2 Touchpad, using the device caused the cursor to jump around and click without pressing to click."
1683760,2017-06-02 08:36:27 UTC,"I suppose you use Zesty? Please try udev packages here:
http://people.canonical.com/~khfeng/lp1683760/"
1683760,2017-05-19 14:48:44 UTC,"For userspace driver, you probably need to ask it on <email address hidden>."
1683760,2017-05-19 13:47:28 UTC,Does anyone know which input driver should be used with the elantech? synaptics/evdev/libinput?
1683760,2018-01-18 04:44:38 UTC,Sounds like you run the command after the touchpad doesn't work.
1683760,2017-05-19 07:05:41 UTC,Please use latest mainline kernel here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/
1683760,2017-04-18 15:32:33 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1683760,2017-05-07 08:27:39 UTC,"DevenPhillips, to clarify, did this issue happen prior to Ubuntu 15.10?"
1683760,2017-04-18 16:08:47 UTC,"BTW, here's the new kernel info:"
1683760,2017-04-18 15:59:15 UTC,No joy... Same result
1683760,2017-04-18 12:00:59 UTC,This change was made by a bot.
1683760,2017-04-18 11:46:52 UTC,Entry as currently listed from /proc/bus/input/devices:
1683760,2017-04-18 11:45:21 UTC,"FYI, things that I have tried:"
1683760,2017-05-07 08:53:51 UTC,I do not believe I owned this laptop far enough back to have installed 15.10. I believe the first installation I put on it was 16.04.
1683761,2017-12-04 16:44:55 UTC,(Fixed it by sudo apt-get remove gradle then re-installing it with sdk)
1683761,2017-12-19 10:22:53 UTC,"Running Artful, I have the same problem. Installing latest from SID (i.e. 0.14 instead of Ubuntu's 0.11) causes ""Unexpected native library version loaded. Expected 21, was 25."""
1683761,2018-01-11 01:47:09 UTC,"As noted by above, reproducible in Artful"
1683761,2018-01-16 07:00:34 UTC,I have the same issue in Artful.
1683761,2018-03-07 18:03:15 UTC,"Sadly, Gradle in the current beta of upcoming 18.04 LTS is broken in the same way, too."
1683761,2018-03-09 13:27:18 UTC,"Hi,"
1683761,2018-03-10 01:41:19 UTC,"Laurent, thanks a lot for looking into this!"
1683761,2018-03-10 21:30:24 UTC,"I've requested a sync, see https://bugs.launchpad.net/ubuntu/+source/libnative-platform-java/+bug/1754896"
1683761,2018-03-10 14:05:51 UTC,"FWIW, Debian import freeze for bionic was already on March 1."
1683761,2018-03-13 22:28:26 UTC,"With todays update of libnative-platform-java/jni, this issue is fixed in 18.04. Thanks again!"
1683761,2018-03-14 16:52:50 UTC,The fix I pushed for Artful is still not accepted for SRU
1683761,2018-03-15 17:52:20 UTC,"The patch is really minimal, just move the linker (-l) flag at the end of the line."
1683761,2017-12-04 15:43:35 UTC,"Hello. I also downloaded and installed the package (https://packages.debian.org/sid/amd64/libnative-platform-jni/download), but when checking my gradle version (gradle -v), I got :"
1683761,2018-03-15 20:07:27 UTC,Solution in #20 worked partially but lead to a new problem (Build failed in my case).
1683761,2018-03-10 13:38:25 UTC,The debian package was wrong but not broken due to difference in the linker default options.
1683761,2017-11-19 22:05:53 UTC,same issue on Ubuntu 17.10 ... solution works as noted above ... download deb and install
1683761,2018-04-16 17:04:13 UTC,Just ran into this. pretty surprised we're still having issues with a bug that was first identified in 2013. Does anyone have workaround suggestions in the mean time?
1683761,2017-09-23 18:26:15 UTC,Downloading https://packages.debian.org/sid/libnative-platform-jni and installing it with `dpkg --install libnative-platform-jni_0.11-5_amd64.deb` fixed the issue for me too on Xubuntu 17.04
1683761,2018-03-21 14:26:49 UTC,SRU got rejected because I didn't follow the SRU procedure strictly enough.
1683761,2017-04-21 11:40:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683761,2017-04-21 15:17:27 UTC,I've ran into the same issue.
1683761,2017-05-08 03:57:14 UTC,"I can confirm. Downloading https://packages.debian.org/sid/libnative-platform-jni and installing it with `dpkg --install libnative-platform-jni_0.11-5_amd64.deb` fixed the issue
I'm using lubuntu 17.04"
1683761,2017-05-11 02:17:42 UTC,"Installing https://packages.debian.org/sid/libnative-platform-jni (0.11-5_amd64) fixed this problem for me, too."
1683761,2017-05-24 15:25:38 UTC,"I encountered this problem too, and like the others, installing https://packages.debian.org/sid/libnative-platform-jni (0.11-5_amd64) fixes it for myself."
1683761,2017-10-12 02:19:48 UTC,"In case of this helps: I installed the libnative-platform-jni_0.11-5_amd64.deb package 1+ month ago because I was getting the same problem in kubuntu 17.04. I remember there have been software upgrades since then. Today, I have tried to compile and the error was back. So that, to fix the problem, I had to reinstall the libnative-platform-jni_0.11-5_amd64.deb package."
1683761,2017-06-02 17:00:38 UTC,"I encountered this problem too, and after installing the libnative-platform-jni from debian, it went away."
1683761,2017-06-05 15:04:53 UTC,"Thanks Mateusz, I added an ""update request"" issue to the Gradle package: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1695919"
1683761,2017-06-05 15:15:38 UTC,It is still weird that this problem doesn't appear with the Debian package. They are both the same version.
1683761,2017-06-05 16:04:48 UTC,"I compared Ubuntu sources and Debian sources, they are exactly the same.
The only difference I've found is related to dynamic relocations in /usr/lib/jni/libnative-platform-curses.so, adding screenshot."
1683761,2017-07-18 20:58:39 UTC,"I followed Hilikus (hilikus) instructions, and works for me.
Thanks a lot"
1683761,2017-08-17 19:13:47 UTC,In https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1238322 Eric writes it is a bug in the makefile. So the sources are the same.
1683761,2017-09-14 21:45:05 UTC,+1 for the fix of downloading the debian package
1683761,2017-06-05 14:43:47 UTC,"Updating gradle to 3.5 also solves issue.
Upstream bugreport: https://github.com/gradle/gradle/issues/1493
Commit with fix: https://github.com/gradle/gradle/commit/4c78b4c85db2f02a98e5fb022d68c33a7cb06f2f"
1683761,2018-04-17 13:08:54 UTC,"Yes, there's a workaround.
You can install the package (with the same version) from Debian: https://packages.debian.org/stretch/libnative-platform-jni"
1683767,2017-09-22 08:16:48 UTC,This bug was fixed in the package peony - 1.0.4-0ubuntu1
1683776,2018-05-04 13:12:33 UTC,Confirmed as still valid on current master.
1683776,2019-05-16 09:45:49 UTC,This doesn't appear to be an issue anymore. I'll close it and we can reopen if the issue returns.
1683777,2017-04-19 17:33:58 UTC,Patch is at https://review.openstack.org/456127
1683777,2017-04-19 17:34:30 UTC,I'm +1 to deprecate them.
1683777,2017-04-24 17:51:24 UTC,Please make sure to communicate the future deprecation on the ML for operators/other 3rd parties visibility.
1683777,2017-04-24 18:41:00 UTC,"fwiw, brought up in ironic meeting today and no one disagreed to this: http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-04-24-17.00.log.html#l-116"
1683777,2017-08-30 22:31:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/499376"
1683786,2019-09-19 14:58:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683800,2017-06-30 13:42:43 UTC,I have same problem!
1683800,2017-04-19 17:32:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683804,2017-04-18 19:29:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683804,2017-04-18 16:32:34 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1683804,2017-04-18 16:27:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1683811,2019-09-19 14:58:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683823,2017-04-18 14:52:28 UTC,"[{'channels': ['stable', 'edge', 'edge', 'edge'], 'current_channels': ['stable', 'edge'], 'series': ['16'], 'version': '0.11', 'timestamp': '2017-04-18T14:04:59Z', 'release_map': [{'series': '16', 'architecture': 'i386', 'channel': 'stable'}, {'series': '16', 'architecture': 'i386', 'channel': 'edge'}], 'arch': 'i386', 'revision': 49}, {'channels': ['edge', 'stable', 'edge', 'edge'], 'current_channels': ['stable', 'edge'], 'series': ['16'], 'version': '0.11', 'timestamp': '2017-04-18T14:03:19Z', 'release_map': [{'series': '16', 'architecture': 'amd64', 'channel': 'stable'}, {'series': '16', 'architecture': 'amd64', 'channel': 'edge'}], 'arch': 'amd64', 'revision': 48}, {'channels': ['edge'], 'current_channels': [], 'series': ['16'], 'version': '0.10', 'timestamp': '2017-04-18T11:49:17Z', 'release_map': [], 'arch': 'amd64', 'revision': 47}, {'channels': ['edge'], 'current_channels': [], 'series': ['16'], 'version': '0.10', 'timestamp': '2017-04-18T11:49:18Z', 'release_map': [], 'arch': 'i386', 'revision': 46}, {'channels': ['edge', 'stable'], 'current_channels': [], 'series': ['16'], 'version': '0.1', 'timestamp': '2017-04-12T17:49:25Z', 'release_map': [], 'arch': 'i386', 'revision': 45}, {'channels': ['edge', 'stable'], 'current_channels': [], 'series': ['16'], 'version': '0.1', 'timestamp': '2017-04-12T17:49:15Z', 'release_map': [], 'arch': 'amd64', 'revision': 44}, {'channels': ['edge', 'beta', 'candidate', 'stable'], 'current_channels': ['candidate', 'beta'], 'series': ['16'], 'version': '0.9', 'timestamp': '2017-04-11T15:05:38Z', 'release_map': [{'series': '16', 'architecture': 'amd64', 'channel': 'candidate'}, {'series': '16', 'architecture': 'amd64', 'channel': 'beta'}], 'arch': 'amd64', 'revision': 43}, {'channels': ['edge', 'beta', 'candidate', 'stable'], 'current_channels': ['candidate', 'beta'], 'series': ['16'], 'version': '0.9', 'timestamp': '2017-04-11T15:05:34Z', 'release_map': [{'series': '16', 'architecture': 'i386', 'channel': 'candidate'}, {'series': '16', 'architecture': 'i386', 'channel': 'beta'}], 'arch': 'i386', 'revision': 42}, {'channels': ['edge', 'beta'], 'current_channels': [], 'series': ['16'], 'version': '0.8', 'timestamp': '2017-03-13T22:06:14Z', 'release_map': [], 'arch': 'i386', 'revision': 41}, {'channels': ['edge', 'beta'], 'current_channels': [], 'series': ['16'], 'version': '0.8', 'timestamp': '2017-03-13T22:04:29Z', 'release_map': [], 'arch': 'amd64', 'revision': 40}, {'channels': ['edge'], 'current_channels': [], 'series': ['16'], 'version': '0.7', 'timestamp': '2017-03-12T09:04:15Z', 'release_map': [], 'arch': 'i386', 'revision': 39}, {'channels': ['edge'], 'current_channels': [], 'series': ['16'], 'version': '0.7', 'timestamp': '2017-03-12T09:04:14Z', 'release_map': [], 'arch': 'amd64', 'revision': 38}, {'channels': ['edge'], 'current_channels': [], 'series': ['16'], 'version': '0.6', 'timestamp': '2017-03-12T07:48:16Z', 'release_map': [], 'arch': 'i386', 'revision': 37}, {'channels': ['edge'], 'current_channels': [], 'series': ['16'], 'version': '0.6', 'timestamp': '2017-03-12T07:48:15Z', 'release_map': [], 'arch': 'amd64', 'revision': 36}, {'channels': ['edge'], 'current_channels': [], 'series': ['16'..."
1683823,2017-04-18 14:52:50 UTC,I am told that that tells me that the store is listing 3 publications in the channel.
1683823,2019-10-15 11:43:31 UTC,I'm not entirely sure but based on the description of the bug it seems to be an issue in snapcraft or its interaction with the snap store. Please feel free to open a snapd task if you feel there is something to improve there.
1683826,2019-09-19 11:59:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683827,2017-09-18 06:09:24 UTC,"disable_numparse is not available in the tabulate version in the ubuntu archives. We could get it into the archives for b, and we could also fix it for the snap. But to fix this into xenial, zesty and artful is not going to be so easy."
1683827,2017-04-18 14:56:54 UTC,"The ""'channels': ['stable', 'edge', 'edge', 'edge'],"" in the response is wacky."
1683827,2017-04-18 14:53:05 UTC,https://pastebin.canonical.com/186107/
1683827,2017-04-18 16:43:16 UTC,MP fixing the channel names duplication ready.
1683828,2017-04-18 16:27:01 UTC,Please provide more description in the bug report. We have CI systems deploying Ceph Rados GW on Centos systems and it works fine. Please give us some details at how you deployed and the repositories that you used.
1683828,2017-04-19 08:58:27 UTC,"Hi Emilien,"
1683836,2017-06-10 09:05:06 UTC,"It also does not work in 17.10. He tries three times, but without success."
1683836,2017-04-20 13:30:37 UTC,Possible dup of bug 1676547 ??
1683836,2017-04-25 06:01:41 UTC,Possible dub of bug #1681513
1683836,2017-04-20 13:28:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683838,2017-05-11 13:06:33 UTC,Can't reproduce right now on environments. Will reopen this bug if problem occurs.
1683838,2017-05-12 13:32:59 UTC,"As well as with Horizon button that is not disabled after hitting ""Launch"" (bug description), this bug was reproduced also via CLI."
1683844,2017-10-11 19:38:49 UTC,@Andres
1683844,2019-09-19 11:59:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683849,2017-10-11 16:28:15 UTC,"@Andres
I think this bug has been solved but could you double-check before closing?"
1683849,2019-09-19 11:59:24 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683856,2018-05-10 08:20:23 UTC,Confirmed in master.
1683856,2019-09-19 11:59:26 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683857,2018-11-24 11:03:14 UTC,https://github.com/shimmerproject/Greybird/releases/tag/v3.22.4
1683857,2017-05-03 09:11:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1683857,2017-04-18 15:55:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683860,2017-05-10 18:28:59 UTC,I have reported the bug upstream: https://bugzilla.gnome.org/show_bug.cgi?id=782469.
1683863,2019-09-19 11:59:28 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683864,2017-04-18 16:27:42 UTC,"Design work on accessible forms can be found here:
https://github.com/CanonicalLtd/MAAS-design/issues/91"
1683864,2019-09-19 14:58:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1683865,2017-04-19 17:20:30 UTC,apport information
1683865,2017-04-19 17:20:26 UTC,apport information
1683865,2017-04-19 17:20:32 UTC,apport information
1683865,2017-04-19 17:20:29 UTC,apport information
1683865,2017-04-19 17:20:33 UTC,apport information
1683865,2017-04-19 16:38:55 UTC,"I have several kdump crash logs that I can share. They are $100MB each so I don't know what the best way might be, and the traces are similar to the trace I already uploaded."
1683865,2017-04-23 01:16:54 UTC,"After two days of testing, I am happy to report that the upstream rc7 version indeed fixes the freezing issue. It still hangs up on suspend/resume, but that's likely unrelated. As I am now using the upstream kernel I'm not sure whether I should report that as ubuntu bug. Any advice would be appreciated. In the mean time I will tag this bug report appropriately."
1683865,2017-04-23 01:25:07 UTC,"Of course, seconds after I posted my previous message, the OS froze again, so the upstream does *not* fix the issue. I can't readily find how I can tag the bug as kernel-bug-exists-upstream, but I'll keep looking. The frequency of freezes seems to have reduced substantially, but since they are intermittent, it might have been a fluke that it hadn't frozen for two days."
1683865,2017-04-25 15:10:08 UTC,"After further testing I can report that the parent issue has indeed been resolved upstream. The subsequent lockups are related to the nvidia module, not the reported issue. Thus, upgrading the kernel will solve the issue."
1683865,2017-04-19 17:20:25 UTC,apport information
1683865,2017-04-20 15:41:23 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1683865,2017-04-19 17:20:23 UTC,apport information
1683865,2017-04-18 20:28:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1683865,2017-04-19 17:20:19 UTC,apport information
1683865,2017-04-19 17:20:18 UTC,apport information
1683865,2017-04-19 17:20:16 UTC,apport information
1683865,2017-04-19 17:20:15 UTC,apport information
1683865,2017-04-19 17:20:13 UTC,apport information
1683865,2017-04-19 17:20:11 UTC,apport information
1683865,2017-04-19 17:20:08 UTC,apport information
1683865,2017-04-19 17:20:07 UTC,apport information
1683865,2017-04-19 17:01:01 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1683865,2017-04-19 17:20:20 UTC,apport information
1683871,2017-04-18 18:11:42 UTC,"you cannot use that option, with dasd drives. as dasd drives only support maximum three partitions..... and separate /home /var /tmp and / need 4."
1683871,2017-04-19 20:30:07 UTC,"I did change debconf to medium, due to the system being on a vlan and bug 1635024."
1683876,2019-05-28 11:27:38 UTC,"This particular problem has been addressed and fixed in bug #1830226, marking this one as a duplicate."
1683876,2017-04-19 20:33:04 UTC,Trusty is also broken for HWE kernels:
1683876,2017-10-12 14:02:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683876,2017-04-19 16:48:27 UTC,"In my case, for a simple process trace (from utrace/uprobe):"
1683876,2017-04-19 16:53:53 UTC,Similar (cause/effect) to this:
1683878,2017-04-18 17:57:10 UTC,linux-aws test kernel with the patch applied: http://kernel.ubuntu.com/~kamal/lp1683878/
1683878,2017-04-18 21:07:02 UTC,I performed this test in EC2:
1683878,2017-04-24 14:29:27 UTC,This bug was fixed in the package linux-aws - 4.4.0-1016.25
1683884,2017-04-19 16:51:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683885,2017-06-11 09:02:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683885,2017-04-19 01:28:52 UTC,"Hello, I suggest trying a command like:"
1683886,2017-10-02 17:04:30 UTC,This is still the case with 17.10
1683898,2017-04-18 20:53:40 UTC,"Please note that the Ubuntu Desktop Guide, i.e."
1683898,2017-04-18 21:54:45 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1683898,2017-04-18 23:47:32 UTC,Thank's a lot for the answers :)
1683898,2018-03-17 21:53:56 UTC,A suggestion to install Tweaks is included in the desktop guide as from 17.10.
1683907,2017-04-18 19:58:58 UTC,"Again, none of these are shown by default, you are not using the default priority for the installer?"
1683907,2017-04-18 19:59:36 UTC,"The two questions are valid - one is asking for absolute size maximum, the other is asking for relative (percentage) maximum."
1683907,2017-04-19 20:31:22 UTC,"I did change debconf to medium, due to the system being on a vlan and bug 1635024."
1683913,2017-04-18 19:45:15 UTC,The workaround to this is to manually change HEAD to point to the branch I'm using. This can be done via the web UI or an API call.
1683913,2019-06-27 09:01:07 UTC,"Fixed in git-build-recipe 0.3.6, also now on Launchpad production."
1683914,2017-05-19 09:58:46 UTC,"Sorry, I am not very acquinted with git-build-recipe, but is this issue the same cause as the problem I experience when trying to build a debian upstream git with a recipe: https://code.launchpad.net/~maarten-fonville/+recipe/cargo-daily"
1683923,2017-06-19 14:20:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1683923,2017-04-18 20:28:57 UTC,"Also, I built the vanilla bash 4.3 and 4.4 sources and they do not appear to be affected by this bug."
1683924,2017-05-22 18:23:35 UTC,"It is distorted as well when I select ""Experimental (no delay)"". I hear crackles in the sound.
With Rubberband instead of Soundtouch it sounds better but it isn't gone. Additionally I get a delay of more than 2 seconds and when turning the sound up in pulseaudio (Mixxx is directly connected to ALSA) I hear a heavily distortion again."
1683924,2020-11-19 22:41:59 UTC,"I can confirm this issue isn't fixed yet in recent 2.3.0 Beta of Mixxx.
I was curious about the quality of the built-in RIAA preamp in my Denon MC7000, so I did a quick test and connected a turntable directly to it. In Mixxx I selected the Denon device as AUX1 in settings, so I can do recordings also from the analogue inputs of the Denon MC7000.
It worked but with crackling sound in the recordings as described above. If I pick ""Experimental"" and raise the audio buffer to 92,9 ms, the recording seems quite OK."
1683924,2018-10-17 04:14:55 UTC,friendly ping @Daniel
1683924,2018-09-20 17:02:34 UTC,Looks like this bug got lost in the shuffle. Does it still occur with Mixxx 2.1.4?
1683924,2017-05-22 18:32:49 UTC,"Switching to 41kHz as sample rate using the maximum audio buffer of 92.9 ms and using default (not Experimental!) sounds better.
But sometimes (and when changing the pulseaudio volume) I think it skips or repeats a part of the last played sound, I think there is a problem with buffering? Additionally a 100% pulseaudio output will result in clipping in Mixxx."
1683947,2017-04-18 22:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1683947,2017-04-24 17:32:32 UTC,"Hey Jay,"
1683947,2017-04-25 19:50:41 UTC,"Jason,"
1683947,2017-05-01 18:19:59 UTC,This bug was fixed in the package linux - 4.8.0-51.54
1683965,2017-05-27 06:43:03 UTC,This bug was fixed in the package virtualbox-guest-additions-iso - 5.1.22-1~17.04.1
1683965,2017-05-27 06:42:11 UTC,This bug was fixed in the package virtualbox-ext-pack - 5.1.22-2~17.04.1
1683965,2017-05-25 22:33:42 UTC,This bug was fixed in the package virtualbox - 5.1.22-dfsg-0ubuntu1.17.04.1
1683965,2017-05-10 16:47:56 UTC,This bug was fixed in the package virtualbox-ext-pack - 5.0.40-0ubuntu1.16.04.1
1683965,2017-05-10 16:37:54 UTC,This bug was fixed in the package virtualbox-guest-additions-iso - 5.0.40-0ubuntu1.16.04.1
1683965,2017-05-06 19:37:46 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of virtualbox-ext-pack from zesty-proposed was performed and bug 1688729 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1688729 (not this bug). Thanks!"
1683965,2017-05-05 16:32:44 UTC,"Zesty is good!
(same testing, clean VM, create and install virtualbox-{host, guest} packages"
1683965,2017-05-05 13:02:49 UTC,"Hello alperyilmaz, or anyone else affected,"
1683965,2017-05-05 13:01:23 UTC,"Hello alperyilmaz, or anyone else affected,"
1683965,2017-05-10 16:47:58 UTC,This bug was fixed in the package virtualbox - 5.0.40-dfsg-0ubuntu1.16.04.1
1683965,2017-05-05 10:03:07 UTC,"An upload of virtualbox-ext-pack to zesty-proposed has been rejected from the upload queue for the following reason: ""Version number is newer than that in arful will cause upgrade issues.  Perhaps: 5.1.22-2~ubuntu0.17.04.1""."
1683965,2017-05-05 10:06:31 UTC,"An upload of virtualbox-guest-additions-iso to zesty-proposed has been rejected from the upload queue for the following reason: ""Version number is newer than that in arful will cause upgrade issues.""."
1683965,2017-04-20 06:48:34 UTC,please don't use virtualbox 5.0.38
1683965,2017-05-03 14:32:18 UTC,"Hello alperyilmaz, or anyone else affected,"
1683965,2017-05-03 14:34:56 UTC,"Hello alperyilmaz, or anyone else affected,"
1683965,2017-04-20 09:33:34 UTC,"Please use my ppa:costamagnagianfranco/locutusofborg-ppa.
I tested the solution and it works"
1683965,2017-05-03 15:14:32 UTC,"I would like to update also virtualbox 5.1 on yakkety/zesty, changelog is following:"
1683965,2017-05-04 08:44:59 UTC,"Testing performed:
install virtualbox on my xenial machine
every VM started up correctly (windows xp, windows 8.1 and so on)."
1683965,2017-05-05 09:59:01 UTC,"Hello alperyilmaz, or anyone else affected,"
1683965,2017-05-03 14:36:28 UTC,"Hello alperyilmaz, or anyone else affected,"
1684003,2017-04-19 08:46:52 UTC,The .desktop file for this application is in the wrong package: http://appstream.ubuntu.com/zesty/universe/metainfo/criticalmass-data.html
1684010,2017-05-04 17:43:40 UTC,"Can you next test 4.10.0-17:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/12396981"
1684010,2017-05-10 00:45:38 UTC,"Just had kind of a freeze with -17 after about two hours of operation. While other freezes so far manifested in the cursor vanishing and everything becoming unresponsive, this freeze resulted in single applications freezing on input attempts. Like freezing after opening a menu and selecting ""Quit"". Eventually all applications were frozen, starting new ones or switching console wasn't possible."
1684010,2017-05-05 13:53:07 UTC,"4.10.0-17 should be OK too- my colleague tests all kernels- we run the same hardware except video- I have nvidia card. I forgot to ask him about results, but he didn't complain, so it should be fine.
Really, it looks very strange, because I don't see any video related changes from 17 to 20 in changelog.
Anyway, next 4 days are holidays here, so we can test only after May 9."
1684010,2017-05-06 19:10:40 UTC,"I just booted 4.10.0-18 and graphics apparently fell back to software rendering. Only one screen size (1600x1200) available, animations run very slow, CPU fan spins up when moving windows, such things."
1684010,2017-05-07 11:52:05 UTC,"Right. Missing video hardware acceleration (and missing audio, ACPI) was due to the kernel extras package not installed. Corrected this situation and now giving 4.10.0-18 another try."
1684010,2017-05-09 22:48:26 UTC,Just had a kernel freeze after some 20 hours of operation with -18:
1684010,2017-05-10 07:39:47 UTC,I'm also experiencing freezes on Ubuntu Gnome 17.04 (x64). I'm on dell Latitude E5470 with the following specs:
1684010,2017-05-15 12:36:41 UTC,"Running kernel -21 from the general repo I managed to grab the attached output of 'top'. khugepaged going 100%, staying there forever. System load eventually went up to 8 or more. System didn't freeze entirely, just slowed down a lot."
1684010,2017-05-10 16:29:31 UTC,"Congratulations for managing to get a backtrace, @Jonas Slivka!"
1684010,2017-05-11 08:32:29 UTC,"@Traumflug, no, I just installed the following two .debs from https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/12033595 and booted into that kernel:"
1684010,2017-05-12 12:15:36 UTC,"Well, looks like problem is memory management, which can be related to video, because intel uses system RAM.
During last freeze we logged-in to my colleague computer and seen khugepages eating cpu-
there was no swap on this computer, so we added it and today there was no freezes ,
4.10.0-20-generic ..."
1684010,2017-05-14 12:44:32 UTC,"Had a freeze with -14, too, after 3 days of operations (hibernating at night)"
1684010,2017-05-15 12:55:51 UTC,"Here's a similar, older bug: https://bugzilla.redhat.com/show_bug.cgi?id=879801 , workarounds included there, see comments 13, 14, 15."
1684010,2017-05-22 11:27:40 UTC,It's possible that this bug is related to (or a duplicate of) this bug:
1684010,2017-05-04 13:10:54 UTC,"There is no problem in 4.10.0-14 .
What should we test now?
Thank you!"
1684010,2017-05-10 14:28:00 UTC,Got freeze on -9 as well:
1684010,2017-05-03 09:18:20 UTC,4.10.0-9 works without problems for several hours here.
1684010,2017-05-03 11:44:44 UTC,"I'll give -9 an additional day to be sure. If you want to continue, 4.10.0-14 is the next candidate."
1684010,2017-05-02 18:56:22 UTC,"If upstream 4.10 works, but Ubuntu 4.10.0-19 does not, then that indicates the bug was introduced by an Ubuntu specific SAUCE patch."
1684010,2017-04-19 05:45:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684010,2017-04-19 12:08:24 UTC,"using kernel from 16.10 while using 17.04 userspace solves problem.
i.e. this is kernel bug."
1684010,2017-04-19 14:07:50 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1684010,2017-04-20 05:55:09 UTC,"Yes, right after upgrade to 17.04 from 16.10.
We'll test mainline kernel and report.
Thank you!"
1684010,2017-04-20 11:24:18 UTC,I'm running 16.04 with xenial-proposed enabled and I'm experiencing random freezes like this a few times a day since kernel upgrade about two weeks ago.
1684010,2017-04-20 12:31:20 UTC,"Tested kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7
Runs fine, at least no freezes for 6 hours."
1684010,2017-04-21 04:24:21 UTC,"Yes, sure, but , most probably next week, sorry.
If rc1 hangs then we'll try rc2, etc..
Thank you!"
1684010,2017-04-24 11:36:57 UTC,Hello!
1684010,2017-04-20 16:03:27 UTC,I'd like to perform a reverse bisect to figure out which commit upstream fixes this regression. It would be very helpful to know the last kernel that had this issue and the first kernel that did not.
1684010,2017-04-26 00:19:32 UTC,A few additional debugging bits:
1684010,2017-04-26 21:07:54 UTC,"Kernel 4.10.0.19 from the regular 17.04 repo appears to work fine, working for some 12 hours now. It's slightly different than the one @Vaclav Rehak reported above as not working:"
1684010,2017-04-27 13:18:23 UTC,Hello!
1684010,2017-04-27 16:58:22 UTC,"> Kernel 4.10.0.19 from the regular 17.04 repo appears to work fine
"
1684010,2017-04-29 14:47:45 UTC,">Continuing with the bisect is much appreciated!
"
1684010,2017-04-30 23:06:23 UTC,4.10.0 from mainline works fine here. Running it for two days now without flaws.
1684010,2017-04-25 16:53:27 UTC,"Can you test 4.10 final?  If it has the bug, we can bisect between v4.10 and v4.11-rc1."
1684010,2017-05-02 21:26:11 UTC,"Thanks for the hint, 4.10.0-9 now running."
1684037,2017-11-10 21:15:29 UTC,I agree it's not a duplicate.
1684037,2020-05-05 23:59:04 UTC,This was fixed in 3.3.2-1.
1684037,2017-11-09 11:07:50 UTC,Anyone alive here?
1684037,2017-04-19 08:00:17 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1531299, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1684037,2017-04-19 08:31:59 UTC,"I don't see what these bugs have in common, except for a similar error message."
1684041,2019-03-25 11:02:05 UTC,I agree that the directory should be writable. Perhaps that's something that needs to be added to writable-paths (as a quick solution)?
1684042,2017-04-19 08:53:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/457928"
1684042,2017-04-20 08:11:49 UTC,"Reviewed:  https://review.openstack.org/457928
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=a0fe5a91dfe813a5c89d559db5aaf4a37af21ec6
Submitter: Jenkins
Branch:    master"
1684047,2017-04-22 02:51:26 UTC,Please update if there is any plan in future to support alerts.
1684047,2017-05-18 22:01:09 UTC,Reported to https://github.com/gnocchixyz/grafana-gnocchi-datasource/issues/14
1684047,2017-05-19 05:44:44 UTC,Thanks Julien for the updates.!
1684069,2017-06-17 11:06:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/475123"
1684069,2017-11-14 20:28:30 UTC,"Reviewed:  https://review.openstack.org/475123
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e774b8842800ae9f1935b582579e45721a4f43fc
Submitter: Zuul
Branch:    master"
1684070,2019-09-19 14:58:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1684081,2017-08-28 22:00:42 UTC,I don't have a proper fix to suggest. I however managed to workaround the issue by exporting the following environment variables in a custom DIB element:
1684087,2017-11-05 18:24:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684091,2017-11-13 23:11:00 UTC,"Agreed, this should be a quick fix."
1684093,2017-04-19 11:38:48 UTC,This was fixed upstream in mdadm 3.3.1
1684100,2017-04-26 20:31:45 UTC,"The workaround fixes it for me too. Other wifi adapters I have (one using rt73usb, the other rtl8812au) don't need it, so maybe the bug lies in athk9_htc.
How did you find the workaround? (just curious, apart from this bug my google searches only gave me outdated or irrelevant information)."
1684100,2017-07-02 19:37:27 UTC,Worked for me:
1684100,2017-06-10 08:52:29 UTC,"It also does not work in 17.10. He tries three times, but without success. I have tried the solutions suggested above, but they have had no effect."
1684100,2017-05-01 16:40:32 UTC,"I tried to boot into the previouse kernel and downgrading wpa_supplicant first, which did not help. So I suspected some change in NetworkManager to be responsible. After trying some other configuration changes I compared the log output from a machine that was not yet upgraded to that of an upgraded one, and the difference was that the latter changed the mac address between scanning and connecting. So I tried to disable this behaviour, and it worked after that.
My other wifi devices too work with mac address randomization turned on, just this one does not. Maybe it has to do with the timing between chaning mac addresses and initiating a connection, I really have no idea what the root cause could exactly be."
1684100,2017-04-23 14:29:07 UTC,"Thanks Sutupud, fixed as well."
1684100,2017-04-26 20:26:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684100,2017-04-20 16:09:47 UTC,Excellent Sutupud. This fixed it. THANK YOU!!
1684100,2017-04-21 03:40:54 UTC,Thank you very much Sutupud - You solved my problem too.
1684100,2017-04-20 13:11:09 UTC,"The suffix of the [device-XXX] section is irrelevant, that is only to distinguish different device sections, match-device is what is important here. match-device=wlxf81a6721bb82 should be correct for your device. In my case it's wlan3 because I still have an old udev persistent net rule that renaming the device to the old scheme."
1684100,2017-04-20 12:05:51 UTC,"Hmm,
with usb card plugin I get:
~$ iwconfig
enp4s0    no wireless extensions."
1684100,2017-04-20 06:37:35 UTC,"@Sutupud- Thanks, it helped me with RT5370 wifi adapter on 17.04. But on the downside it won't do real-time scan for available wireless networks any more."
1684100,2017-04-19 22:13:56 UTC,"I had the same problem, for me disabling MAC address randomization while scanning resolved it, by adding a .conf file to /etc/NetworkManager/conf.d/ containing:"
1684103,2017-04-19 11:58:12 UTC,"Interestingly, noticing a lot of the related bug reports I'm seeing seem to be all lenovo."
1684113,2019-03-27 20:18:39 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/648233"
1684113,2019-03-27 15:35:49 UTC,"Reviewed:  https://review.openstack.org/644419
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=ca21ac81164a7a1d371111f501a6a0c79c637f67
Submitter: Zuul
Branch:    master"
1684113,2017-09-21 13:13:29 UTC,Triaging cinder task as 'wishlist' as enabling consistency group support for cinder is a new feature; Triaging openstack-dashboard task as 'Medium' as we really should conditionally enable/disable this part of the dashboard.
1684113,2017-09-21 13:11:42 UTC,"Rather than add yet-another-config-toggle to the openstack dashboard charm, I'd prefer to deal with this via the service-discovery spec we have in-flight for the queens development cycle; cinder can use this feature to expose whether consistency-groups are supported to any service in the cloud, including the dashboard, which can then enable/disable features accordingly."
1684113,2019-03-20 16:26:26 UTC,Openstack dashboard charm patch - https://review.openstack.org/#/c/644419
1684117,2017-04-19 13:07:42 UTC,Are you sure that this is the complete invocation? Can you please attach a standalone reproducer?
1684117,2017-04-19 13:08:39 UTC,"Nevermind, you do pass uninstalled=True, just not by name."
1684118,2017-06-07 09:10:37 UTC,"According to the code for now we only support ClusterIP service type
https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/handlers/lbaas.py#L51-L54"
1684118,2017-06-01 12:21:01 UTC,"I'm also facing this issue, any suggestion?
Here is my log output:"
1684118,2017-06-14 14:07:54 UTC,I would like to understand the case for supporting Nodeports. I am not sure that we need it at all.
1684122,2018-01-24 22:40:38 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1424
1684123,2019-09-08 08:46:24 UTC,"This is concerning that after all this time (2,5 year) this issue is still here."
1684123,2018-02-25 21:06:24 UTC,"Still exists in 4.16.0-rc2:
nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
Machine is HP ZBook 17 G3, the rest (bootlogs, etc) can be found in BUG 100213 report."
1684123,2018-03-23 08:47:16 UTC,"still there with 4.13.0-37 ubuntu on HP Spectre, Core i7 7500U, intel HD Graphics 620, GM108M (GeForce 940MX) :"
1684123,2018-03-23 13:52:22 UTC,"(In reply to Mikael T from comment #17)

> still there with 4.13.0-37 ubuntu on HP Spectre, Core i7 7500U, intel HD
> Graphics 620, GM108M (GeForce 940MX) :
>
> nouveau 0000:01:00.0: NVIDIA GM108 (1180d0a2)
> nouveau 0000:01:00.0: bios: version 82.08.62.00.15
> nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
> nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
> nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
"
1684123,2018-09-19 19:16:06 UTC,"nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 3e6684 [ IBUS ]"
1684123,2018-10-03 16:07:42 UTC,Ubuntu 18.04
1684123,2018-10-29 07:22:15 UTC,"I think I'm also seeing this with Fedora 29 Beta, I was also seeing errors with updated Fedora 28."
1684123,2018-10-29 12:16:51 UTC,"(In reply to boldingd from comment #19)

> I think I'm also seeing this with Fedora 29 Beta, I was also seeing errors
> with updated Fedora 28.
"
1684123,2018-02-08 23:55:14 UTC,"Ubuntu 16.04, Kernel 4.14.18, nVidia GTX 970M, AW17R3 with i7 6700-HQ, Using Intel HD 530 graphics on built-in display and external HDMI via Thunderbolt 3 USB C adapter."
1684123,2019-12-04 09:25:51 UTC,-- GitLab Migration Automatic Message --
1684123,2018-12-05 15:40:00 UTC,"openSUSE Tumbleweed
Kernel 4.19.5-1-default"
1684123,2018-12-07 11:26:38 UTC,I'm getting one of these too on Fedora 28 KDE Plasma spin.
1684123,2018-12-08 16:27:22 UTC,"(In reply to Bruno Pagani from comment #4)

> @gene, Johnny B. Goode: From what I know, the “at” value matters, because
> they have meanings. Though from one generation to another this could be
> different values for the same register.
>
> Also, @Johnny, in your case it’s a write instead of a read, so I would
> definitively open another issue.
"
1684123,2018-12-29 18:43:05 UTC,"I have a similar issue with my NP900X5N laptop with Kaby Lake and 940MX card, on 4.20.0 and Kali Linux."
1684123,2019-01-01 13:20:23 UTC,"(In reply to Jan from comment #26)

> I have a similar issue with my NP900X5N laptop with Kaby Lake and 940MX
> card, on 4.20.0 and Kali Linux.
>
> [   35.984104] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
"
1684123,2019-01-01 22:01:08 UTC,"Tonight I tried to see what happens if I generate a xorg.conf file and place it in /etc/X11/xorg.conf, as described here:
https://askubuntu.com/questions/4662/where-is-the-x-org-config-file-how-do-i-configure-x-there"
1684123,2019-04-29 14:58:00 UTC,"FWIW, I also get this one (022554), along with two others (10ac08 and 6013d4)."
1684123,2018-12-05 15:12:05 UTC,"(In reply to Cameron from comment #21)

> From my dmesg.
>
> [   12.189523] ax88179_178a 2-2:1.0 enp0s20f0u2: ax88179 - Link status is: 0
> [   15.645518] ax88179_178a 2-2:1.0 enp0s20f0u2: ax88179 - Link status is: 1
> [   29.886049] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at
> 6013d4 [ IBUS ]
> [   57.810423] logitech-hidpp-device 0003:046D:4013.0009: HID++ 2.0 device
> connected.
> [   60.146429] logitech-hidpp-device 0003:046D:4002.000A: HID++ 2.0 device
> connected.
>
>
> I am also getting this error
>
> kernel 4.19.5-1-default
> openSUSE Tumbleweed
"
1684123,2018-02-05 16:32:45 UTC,"> Something when wrong with nouveau globaly
"
1684123,2018-12-05 15:09:31 UTC,From my dmesg.
1684123,2018-02-05 15:41:42 UTC,"@Bruno, thanks for the comment. I will check it out. Bumblebee: you see, I'm fine with intel, I do not need extreme speeds and I have 16GB in RAM ...
nvidia - I could manage to install it either globally or in bumblebee but it blocks the brightness control when used permanently - very weird, so only bumblebee would go.
Something went wrong with setting nouveau globally and I have given up. Will retry. But it will not suit me if the brightness keys are blocked ...
And yes, my system is nearly the tomorrow's version. It is up-to date. At least the kernel is the one released few days ago ..."
1684123,2018-02-05 15:48:26 UTC,"(In reply to Alex from comment #13)

> @Bruno, thanks for the comment. I will check it out. Bumblebee: you see, I'm
> fine with intel, I do not need extreme speeds and I have 16GB in RAM ...
> nvidia - I could manage to install it either globally or in bumblebee but it
> blocks the brightness control when used permanently - very weird, so only
> bumblebee would go.
"
1684123,2017-03-27 20:42:44 UTC,"Created attachment 130492
dmesg output"
1684123,2017-04-07 13:37:01 UTC,"I have similar issue on dell precision 5520 with
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Has nvidia maxwell (NV117) and 4k touch screen"
1684123,2017-04-13 13:09:43 UTC,Same for: Intel i7-4710HQ + GM107M [GeForce GTX 850M]
1684123,2017-05-02 13:47:01 UTC,"Almost same for i7-6700, GM206 [GTX 950]
No touch screen, no hybrid graphics. Pure desktop. Intel 530 on chip but disabled in BIOS. Only one Asus Graphic Card.
Problem started on Kernel 4.10.x and is going on 4.11.0. Kernel 4.9.x is FAULT free. Different distributions Fedora 25, Gentoo.
------------------------------------"
1684123,2017-05-12 17:05:40 UTC,"@gene, Johnny B. Goode: From what I know, the “at” value matters, because they have meanings. Though from one generation to another this could be different values for the same register."
1684123,2017-07-27 19:57:27 UTC,Confirm. I get the same message with the same number (3e6684) using latest Debian testing with GeForce GTX 750 Ti:
1684123,2017-08-07 22:26:27 UTC,I have the same issue on system start. GTX1070. Ubuntu 16.04. default X.Org X Server driver
1684123,2017-07-27 19:34:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684123,2017-12-19 19:51:28 UTC,Looks like 22554 is no longer available on Maxwell. See where ltc reads it from for the new location. Needs to be split out of ramgk104 somehow.
1684123,2017-12-19 22:49:36 UTC,"(In reply to Ilia Mirkin from comment #6)

> Looks like 22554 is no longer available on Maxwell. See where ltc reads it
> from for the new location. Needs to be split out of ramgk104 somehow.
"
1684123,2018-01-16 04:28:24 UTC,"This also affects me.
Fresh install of Ubuntu Mate 16.04.3"
1684123,2018-01-28 21:34:05 UTC,"There is a new one now (10ac08, in addition to 022554):
```
[   10.667586] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
[   10.667788] nouveau 0000:01:00.0: NVIDIA GM107 (117310a2)
[   10.695951] nouveau 0000:01:00.0: bios: version 82.07.a9.00.0c
[   10.849391] nouveau 0000:01:00.0: fb: 4096 MiB GDDR5
[   10.849404] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ IBUS ]
[   10.851426] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
[   11.937159] nouveau 0000:01:00.0: DRM: VRAM: 4096 MiB
[   11.937160] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[   11.937163] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[   11.937164] nouveau 0000:01:00.0: DRM: DCB version 4.0
[   11.937165] nouveau 0000:01:00.0: DRM: DCB outp 01: 02811fa6 04420010
[   11.937167] nouveau 0000:01:00.0: DRM: DCB outp 02: 02011f62 04420010
[   11.937168] nouveau 0000:01:00.0: DRM: DCB outp 03: 08822fc6 04420010
[   11.937169] nouveau 0000:01:00.0: DRM: DCB outp 04: 08022f82 04420010
[   11.937170] nouveau 0000:01:00.0: DRM: DCB conn 01: 00010146
[   11.937171] nouveau 0000:01:00.0: DRM: DCB conn 02: 01000246
[   12.126552] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[   12.233419] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1"
1684123,2018-01-29 12:30:27 UTC,"(In reply to Bruno Pagani from comment #8)

>
> Should I open a new issue for this one?
"
1684123,2018-01-29 13:11:05 UTC,Done: https://bugs.freedesktop.org/show_bug.cgi?id=104835
1684123,2018-02-05 09:48:01 UTC,"Hi folks,
I have the very similar issue about drm, bus read FAULT, etc. However, my problem is more severe than just red lines in dmesg."
1684123,2018-02-05 15:13:08 UTC,@Alex You should not use Bumblebee with nouveau. Also your bug is similar to an old of mine: https://bugs.freedesktop.org/show_bug.cgi?id=98384. So part of your issue is that your system is likely not up-to-date.
1684123,2017-08-10 02:24:40 UTC,I've bisected the issue. It happens with this commit:
1684124,2017-05-24 10:53:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684124,2017-07-27 15:39:01 UTC,This is being worked https://patchwork.freedesktop.org/series/23107/
1684127,2017-04-19 21:10:56 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1684127,2017-04-20 08:47:08 UTC,"Hello sir.
Could you please tell me the reason of freezing my Ubuntu 16.04 LTS version.
I am having good hardware configration"
1684134,2017-04-19 15:20:00 UTC,Please take a look at Bug #515997.
1684134,2020-09-22 09:29:22 UTC,Closing because INVALID.
1684134,2017-04-19 14:47:00 UTC,"...some coincidence, just 1.5h apart..."
1684140,2019-09-19 14:58:53 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1684205,2017-06-15 21:36:25 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1684205,2017-05-15 05:49:35 UTC,This bug was fixed in the package gnome-shell - 3.24.2-0ubuntu3
1684205,2017-05-29 10:07:18 UTC,"Hello Jeremy, or anyone else affected,"
1684205,2017-05-29 14:18:16 UTC,"Hello Jeremy, or anyone else affected,"
1684205,2017-05-29 14:31:36 UTC,"Hello Jeremy, or anyone else affected,"
1684205,2017-05-31 13:28:17 UTC,"From Ubuntu (Unity) 16.04, 16.10 and 17.04, I enabled -proposed updated and installed gnome-shell. I logged out of Unity and logged into GNOME. I verified that the Lock button is present and works now. Ubuntu (Unity) uses LightDM and I did not switch to a different display manager."
1684205,2017-06-15 21:36:08 UTC,This bug was fixed in the package gnome-shell - 3.18.5-0ubuntu0.3
1684205,2017-06-15 21:37:01 UTC,This bug was fixed in the package gnome-shell - 3.20.4-0ubuntu3
1684205,2017-06-15 21:41:17 UTC,This bug was fixed in the package gnome-shell - 3.24.2-0ubuntu0.1
1684213,2017-05-26 10:52:15 UTC,Just a few updates which may be of use to anyone else having the same issues...
1684213,2017-04-21 19:16:05 UTC,Some additional notes after testing for a while...
1684213,2017-06-16 20:33:08 UTC,This one looks like the same bug: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1673344
1684213,2017-04-28 06:46:01 UTC,"Seth, you are right, I didn't check it careful enough."
1684213,2017-06-16 20:29:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684213,2017-04-27 15:17:57 UTC,"Zesty already has the latest 7260 firmware (revision 459231), and according to the attached CurrentDmesg.txt that's what being using:"
1684213,2017-04-20 12:10:15 UTC,"Dell xps 9333, same problem."
1684213,2017-04-26 18:27:48 UTC,Issue definitely persists on 4.11/upstream. I came across an interesting output in dmesg which may explain why bluetooth works while the WiFi doesn't:
1684213,2017-04-23 00:13:35 UTC,"It took less than 10 minutes of testing for the issue to come back up again under 4.11-rc7. Definitely NOT fixed upstream. I'll keep testing and see if I find any other unique behaviours/error messages. Thanks again, let me know if there's anything I can do!"
1684213,2017-04-20 15:42:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1684213,2017-04-19 16:01:03 UTC,This change was made by a bot.
1684213,2017-04-27 06:01:14 UTC,"There's a new 7260 firmware, can you try it?"
1684214,2017-06-28 01:33:51 UTC,"As Drew mentions, this may be difficult to implement well if auto_secrets is in play and, in fact, it was removed in r162 when auto_secrets was implemented!  Fixing the documentation seems like the most appropriate fix."
1684217,2017-08-03 20:00:43 UTC,"Ante, see https://bugs.launchpad.net/juju/+bug/1708492"
1684217,2017-09-12 21:25:36 UTC,With juju 2.2.3 https://bugs.launchpad.net/juju/+bug/1708492 was fixed (https://github.com/juju/juju/pull/7707).
1684217,2017-04-20 09:10:17 UTC,"Having compared diffs of the downloadable zip from the charm store and lp:charms/trusty/memcached, I can confirm that they are identical.  This probably means that lp:charms/memcached should be brought up to date to the trusy/memcached branch too."
1684217,2017-07-25 15:52:55 UTC,"I would assume juju 2.2 solves this by having private-address comming from default ("""") space."
1684217,2017-09-21 13:15:56 UTC,This feels like a gap in the network space support in the charms for this specific relation; triaging both bug tasks as 'Medium' and making note that using the default space binding support in 2.2.3 allows workaround of this missing feature.
1684219,2017-05-30 05:34:16 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/468990"
1684219,2017-04-20 13:30:55 UTC,It is working on networking_ovn (Master) with OpenStack (stable/ocata).
1684219,2017-10-25 00:14:38 UTC,"Change abandoned by Tony Breeds (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/468990
Reason: This branch (stable/newton) is at End Of Life"
1684220,2017-04-19 18:04:27 UTC,fixed with
1684223,2017-04-19 21:12:42 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1684223,2017-04-19 21:12:57 UTC,"Hello, I suggest trying"
1684227,2019-09-16 17:40:41 UTC,Migrated to https://github.com/widelands/widelands/issues/2074
1684228,2019-09-16 17:34:43 UTC,Migrated to https://github.com/widelands/widelands/issues/2075
1684228,2018-08-17 08:29:48 UTC,I think we have abandoned state-buttons and now favouring dropdown menus.
1684228,2018-08-17 07:46:29 UTC,"I'm against keyboard shortcuts to anything used rarely and also to anything that has a lasting effect. We need to be able to read a ship's mode later and to read it on its window, so we need a visual switch among modes. If only two modes exist, a checkbox would be enough. If more, another switch element would fit better."
1684228,2018-08-17 08:13:11 UTC,We have 3 modes proposed - maybe a button that changes state? Could also be a dropdown menu.
1684233,2017-04-24 21:51:29 UTC,"i suspect it was malicious, pretty sure it was my teacher in my IT program.
thank you for looking into it and getting back to me. i was having quite a
hard time removing the issue but as i need my system for school i wiped and
re installed losing my data in the process. is there any tips you might be
able to give me in securing my system a little better? currently i use
arpalert,arpwatch,chrootkit,and lynis. any pointers or help would be
greatly appreciated. again thank you for your time."
1684233,2017-04-24 21:52:45 UTC,"i also noticed it was extremely sloppy as well, it kind of made me laugh to
be honest"
1684233,2017-09-25 22:14:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684233,2017-04-19 21:39:23 UTC,"Hello, your logs indicate some problems. It sure looks like your /usr/sbin/adduser and /usr/sbin/addgroup programs have been modified and that appears to be preventing other programs from running correctly. Repairing this may be difficult depending upon when those programs were corrupted and what might have tried to use them in the meantime."
1684240,2018-05-08 13:26:14 UTC,"Hello everyone, I might have found some new clues about this problem (and a solution, for me at least ;)"
1684240,2018-02-11 17:10:37 UTC,This happen in Ubuntu 16.04 LTS.
1684240,2018-03-24 13:56:37 UTC,"I've found a more convenient workaround: the square does not appear at least on SDDM if the new session was started not from X but from a TTY.
The command I use in TTY is"
1684240,2020-10-13 13:39:09 UTC,Yes I had this issue described here https://askubuntu.com/questions/1256513/mouse-pointer-on-desktop-is-tailed-by-square-shaped-marks-in-20-04-lts
1684240,2018-05-09 15:05:06 UTC,"I began having this problem last fall after an update to Nvida from 378 to 384, IIRC.
A couple of weeks ago I installed Kubuntu 18.04 with the Nvidia 390 driver and did NOT have this problem.
I switched back to Neon for personal preference reasons.
A workaround that I've been using is to open a console on the login screen (which shows the mouse pointer defect) using Ctl+Alt+F2 and in that console enter:"
1684240,2018-02-11 16:09:25 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1684240,2018-05-09 13:56:41 UTC,"Hello Matthias,"
1684240,2018-02-10 02:32:59 UTC,"As mentioned in other comments here, one workaround is to restart sddm (or to log out and log back in again). Not very convenient."
1684240,2018-01-21 17:11:40 UTC,"I'm also having this big on following configuration:
KDE neon User Edition 5.11
Nvidia GT 540m Driver 384.111
happening in both Opengl 2.0 and 3.1 and single/dual display"
1684240,2018-02-03 20:21:42 UTC,Hello Andra.
1684240,2018-02-03 19:56:33 UTC,"Confirmed that this should solve the issue.
System settings -> Display and Monitor -> Compositor -> Rendering backend: set XRender instead of OpenGL."
1684240,2018-01-26 10:36:38 UTC,Kubuntu 16.04 LTS. Very annoying bug but logout(after boot) and in again works.
1684240,2018-01-22 13:15:13 UTC,"For people that do not need the external GPU, they could disable it and only use the integrated Intel driver, after fixing a bug that causes non-booting."
1684240,2018-01-22 06:34:35 UTC,Same even with the new nvidia drivers. Any solution near ?
1684240,2018-06-05 21:27:15 UTC,I will also confirm that I am using the most up to date version of the graphics drivers and that a logout will fix the issue. hopefully this is resolved in the upcoming update that i can not wait to try out. Keep up the good work. Just in case this is still being looked at by someone my hardware is as follows: Lenovo t530 with the Nvidia NVS 5400m graphics. Keep up the good work ladies and gents! I know that i greatly appreciate the hard work you all put in! It saves me from the disaster that is windows (in my opinion). :)
1684240,2018-01-19 15:09:09 UTC,I also have this on a fresh installation of Ubuntu 16.04 when using nvidia-384.
1684240,2018-02-05 20:53:49 UTC,"I experienced this bug on both my laptops (both with Nvidia 9xx series GPUs) with KDE Neon (developer stable), but not on my desktop PC. All are running the latest proprietary Nvidia 390 drivers."
1684240,2018-08-07 07:55:39 UTC,The bug still exists with latest nvidia drivers (!!!)
1684240,2018-08-29 19:22:48 UTC,"Okey guys i solved this i am on kubuntu i was having the exact same problem, now to the solution"
1684240,2018-08-11 23:54:00 UTC,"Have the same issue. My system:
Ubuntu 16.04.5, latest updates. Unity desktop.
Nvidia 384.130 driver.
DisplayLink 4.2, tried also with 4.1, the same issue."
1684240,2021-02-08 07:12:15 UTC,I have this problem in Ubuntu Focal 20.4 installed on an iMac 21.5' mid-2010 with a Radeon ATI card.
1684240,2020-07-17 13:36:50 UTC,"I have also found this in Ubuntu 20.04 ,Amd ryxen 1700x , nvidia 1070X 8GB system
its bit difficult when coding"
1684240,2020-07-01 10:14:02 UTC,"Hi I might have some updates. I have been reading all the comments but my issue was totally different. I use an Asus Tuf fx504 laptop and recently dual booted to Ubuntu 20.04. However I did not install the nvidia drivers yet. Not this issue of lagging box around cursor happened randomly one day. I then finally installed the nvidia drivers hoping it would help. I have tried logging in and out, reconfigured lightdm as some answers suggested but still the issue persists."
1684240,2019-06-03 06:28:17 UTC,I can confirm that this is happening only in combination with Display Link drivers.
1684240,2019-05-15 12:53:46 UTC,"Happens also to me:
Manjaro 18.0.4
KDE 5.15.4"
1684240,2019-05-04 03:00:56 UTC,"@jamie-2 the suggestion worked but of this way;
[Service]
# temporary safety check until all DMs are converted to correct
# display-manager.service symlink handling
ExecStartPre=/bin/sleep 10
ExecStartPre=/bin/sh -c '[ ""$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))"" = ""lightdm"" ]'
ExecStart=/usr/sbin/lightdm
Restart=always
BusName=org.freedesktop.DisplayManager"
1684240,2019-02-25 13:53:53 UTC,For me editing the display-manager.service made no difference.
1684240,2018-08-07 08:53:24 UTC,"Was fixed for me during the last updates on Lenovo W540 with Quadro K1100M.
I also updated to the latest displyLink drivers (4.2 08 Mar 2018).
NVIDIA driver version: 384.130"
1684240,2019-01-23 16:12:20 UTC,"Hi,"
1684240,2018-09-12 12:35:04 UTC,"Thank you, Witold Burkiewicz, it is really helpful workaround."
1684240,2018-08-29 21:04:19 UTC,"Crippling your system (switching to xrender and much slower nouveau driver) is not a solution.
What works for me flawlessly for more than a week on KDE Neon:
In file:
   /lib/systemd/system/sddm.service
Add:
   ExecStartPre=/bin/sleep 10
After [Service]
The problem apparently is that something SDDM needs is not initialized before is starts, so delaying SDDM by 10 sec is adequate workaround. Perhaps it could be less, but it doesn't bother me as long as I don't have to log out/log in manually."
1684240,2018-01-11 13:48:09 UTC,"Add Option ""DRI3"" ""1"" to XORG not run in KDE Plasma."
1684240,2018-08-18 23:12:00 UTC,"After several restarts the solution above sometimes didn't work, so I've modified it:
    exec sddm
    sleep 2
    killall sddm
    exec sddm
Possibly it will more persistent."
1684240,2018-08-18 22:42:52 UTC,"Hello,
this is really annoying problem and apparently nobody cares except for the people that experience it.
But I have found a better workaround that works at least for me:
In /etc/init/sddm.conf after line:
    exec sddm
add:
    killall sddm
    exec sddm"
1684240,2018-08-14 14:17:57 UTC,I have the same issue with KDE neon and Nvidia 396.51 on a Dell XPS 15 9570 (GTX 1050 Ti). Restarting sddm fixes the issue but is really annoying.
1684240,2018-08-11 23:55:29 UTC,"Update, logout and login again resolves the issue!!!"
1684240,2019-01-09 11:01:46 UTC,I used Witold Burkiewicz fix with GDM on Arch - i had to edit '/etc/systemd/system/display-manager.service'. Thank you all!
1684240,2018-01-10 09:10:16 UTC,"I had this problem with Cinnamon on ubuntu 17.04, and fixed it by adding:"
1684240,2017-11-21 12:02:39 UTC,i have this bug too can be fixed by (near fix):
1684240,2018-01-09 17:17:05 UTC,You can remove sddm and use lightdm instead  until this bug is not fixed
1684240,2017-06-08 04:07:22 UTC,A new development: today I installed Kubuntu 17.04 from scratch on a new laptop. The pointer behaves normally.
1684240,2017-05-29 20:03:40 UTC,I am affected by this bug as well.
1684240,2017-05-29 19:54:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684240,2017-05-18 16:34:15 UTC,"Like Loïc, I also use an external screen, with the laptop screen turned off, and I see this problem."
1684240,2017-05-18 15:00:09 UTC,"Ok, I'm using an external screen but laptop screen is off when screen is connected.
I removed all nvidia drivers and tools and thus switched to nouveau, the problem is gone."
1684240,2017-05-10 20:26:11 UTC,"I use dual screen quite often but not always. This behavior is the same for a single and a double screen. This is why I was reluctant to try nouveau, which used to have a lot of issues with that configuration. So far it works fine."
1684240,2017-05-10 14:06:18 UTC,"You're welcome Jacob :)
See also https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1677540 even if it seems less intrusive as what I'm experiencing."
1684240,2017-07-18 20:39:55 UTC,I'm also affected by this bug.
1684240,2017-05-05 18:25:30 UTC,"Merci beaucoup de votre soutien; comme vous pouvez le constater, je n'ai pas répondu à deuxième message, pour terminer cette discussion inutile."
1684240,2017-05-01 12:26:16 UTC,...and I should have guessed all that information from your six words post because...?
1684240,2017-04-30 22:14:04 UTC,"You should realize that this is not some sort of a help desk but a community where everyone is trying to help everyone by providing information about their issues. I ""own"" this bug because I reported it, but I am not a developer of the package involved."
1684240,2017-04-30 21:08:13 UTC,"Finally found the bug report of this problem. It affects me, exactly the same. I could provide more details BUT it doesn't seem to be relevant, doesn't it? I explain:"
1684240,2017-04-29 23:28:16 UTC,Changed to nouveau; the problem disappeared.
1684240,2017-04-24 12:51:27 UTC,"Some additionnal information: tried to change cursor theme from Brise to any other and problem is still there.
Also changing vsync tearing parameter (or any other in fact) in composer settings did not help either."
1684240,2017-04-24 12:46:45 UTC,"I can confirm this issue, I have the same problem since zesty update."
1684240,2017-04-24 12:36:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684240,2017-05-05 08:14:01 UTC,"Jacob message is pretty clear, I had no trouble understanding it, no need to write so many lines just for this, please get over it."
1684240,2018-01-09 18:46:28 UTC,"And, someone know when this bug will be fix? I have this bus from April 2017. Thanks!"
1684240,2017-07-18 20:56:19 UTC,I forgot to mention I'm also using double monitor (laptop + external screen with mini display port).
1684240,2017-08-09 19:11:09 UTC,I updated from Kubuntu 16.04 to 17.04 a few days ago to fix some other issues with frequent crashes and on Kubuntu 17.04 am now also affected by this bug.
1684240,2018-01-09 16:56:39 UTC,Hello.
1684240,2017-12-09 23:47:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684240,2017-11-23 16:08:24 UTC,"I have this problem only if there are two user accounts running, only on the second one and only after"
1684240,2017-11-02 00:38:35 UTC,I also am affected by this issue. I am running KDE Neon with the hwe kernel. My nvidia driver is 384.90.
1684240,2017-10-18 20:10:51 UTC,"I have this bug too.
Logout and then Login temporary solves the problem."
1684240,2017-10-18 15:55:16 UTC,I have this error also. Anyone can fix it? I can't install Nvidia Drivers Property of this. I have that use nouveau.
1684240,2017-07-26 19:13:45 UTC,"I have another big clue
This happened to me also, I'm on kubuntu 16.04.2 with nvidia drivers 384.47 and everything has been working fine while I was using xserver-xorg 1.18 (except for the know tearing).
So I updated to xserver-xorg-core-hwe 1.19.3 from the xenial proposed ppa and the cursor got corrupted.
So, it has to do with updating to xorg 1.19 and nvidia propietary driver
On the bright side, xorg 1.19 indeed fixes the screen tearing and vsync with the line ""options nvidia_384_drm modeset=1"" in /etc/modprobe.d/zz-nvidia-modeset.conf"
1684240,2017-10-07 01:22:22 UTC,"I can confirm this with
Nvidia Driver 375.66
Ubuntu 16.04 + Kubuntu Backports
KDE Plasma Version 5.8.7
Kde Frameworks Version 5.36.0
and sddm"
1684240,2017-10-14 09:16:19 UTC,I can now also confirm that this bug might be related to sddm.
1684240,2017-09-15 20:46:12 UTC,I can confirm that logging out and then logging in also resolves the issue for me.
1684240,2017-09-15 09:23:45 UTC,"PS1: That workaround works (for me) even when the rendering backend is OpenGL.
PS2: I'm also using multiple monitors."
1684240,2017-09-15 09:14:22 UTC,"This bug is driving me nuts, but thankfully a workaround (that has been working for me) is to log out of the initial KDE session and simply log back in."
1684240,2017-09-10 21:17:37 UTC,Oh it's back to being broken when playing factorio.
1684240,2017-09-10 20:57:26 UTC,I can confirm this with the nvidia drivers. It happens when using opengl (2.x and 3.x) compositing but not xrender compositing.
1684240,2017-08-11 23:08:02 UTC,"I am also experiencing the exact same issue on KDE Neon 5.10.4 and nvidia-384.59, and switching to Xrender also fixes it for me."
1684240,2017-08-11 13:45:26 UTC,"To me helped only unchecking the checkbox ""Enable compositor on startup""."
1684240,2017-09-23 16:39:25 UTC,"I have the same problem, when restarting the sddm, or after login and logout is resolved"
1684273,2017-04-22 06:50:52 UTC,"I agree that this is unexpected. It can be fixed by internally passing more data into the parser before generating the ""end"" parse event, i.e. by waiting for the tail text to end before yielding the element that owns it."
1684273,2017-04-19 19:43:11 UTC,"When used with the system python3-lxml package, rather than the version pip installed into a venv:"
1684280,2019-08-14 08:49:39 UTC,This is actually a bug in the mbrola package.
1684280,2017-04-22 22:56:36 UTC,"Same in Yakkety:
[00:54][nf@fox:~ ]$ apt-cache policy mbrola
mbrola:
  Installiert:           3.01h+1-3
  Installationskandidat: 3.01h+1-3
  Versionstabelle:
 *** 3.01h+1-3 500
        500 http://de.archive.ubuntu.com/ubuntu yakkety/multiverse amd64 Packages
        100 /var/lib/dpkg/status
[00:54][nf@fox:~ ]$ apt-cache policy espeak
espeak:
  Installiert:           1.48.04+dfsg-5
  Installationskandidat: 1.48.04+dfsg-5
  Versionstabelle:
 *** 1.48.04+dfsg-5 500
        500 http://de.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages
        100 /var/lib/dpkg/status
[00:54][nf@fox:~ ]$ lsb_release -rd
Description:    Ubuntu 16.10
Release:        16.10"
1684280,2019-08-14 08:53:52 UTC,When cloning mbrola source and building it with gcc the result works just fine.
1684280,2017-04-21 12:37:59 UTC,"For what it is worth it, I can't reproduce this in Debian Stretch,
neither with espeak, nor with espeak-ng."
1684280,2017-04-22 22:52:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684302,2017-04-20 06:30:23 UTC,"Since Gnocchi is not part of OpenStack anymore, the doc are not being built. But I imagine nothing on infra side deleted/redirected them."
1684304,2017-04-24 18:28:32 UTC,"Confirmed: Fixed in Zesty, still broken in Yakkety"
1684304,2017-04-24 18:34:18 UTC,New format is like this:
1684304,2017-04-24 18:37:34 UTC,"Thank you Mikkel for your report and your Help to make Ubuntu better.
Fortunately in this case newer Releases already hold a fixed version so we need to do nothing to on these and any future releases."
1684315,2017-04-19 23:13:02 UTC,"This would *also* allow us to use custom kernels for non-LTS cloud images that are produced, so that any users who install a non-LTS image, and then upgrade it to 18.04, will get the intended custom kernel for that environment."
1684315,2017-04-20 06:08:35 UTC,We should add these as transitionals on linux-meta to simplify maintenance. The version of the base kernel should exceed that in xenial.
1684315,2017-04-20 06:11:52 UTC,This should apply equally to any X only customkernel of this type.
1684327,2017-04-20 04:58:24 UTC,my-weather-indicator package is 0.8.1-0extras16.04.1
1684327,2017-04-20 22:52:14 UTC,one of the updates I installed today seems to have fixed the problem.
1684336,2017-04-21 06:50:41 UTC,I have the same problem. Here is a github bug report about it : https://github.com/JoseExposito/touchegg/issues/300
1684336,2017-08-26 15:59:45 UTC,"Guys, I recently updated my Ubuntu 16.04 (did not upgrade to 17.04), and I lost touchegg functionality. I looked around and found this:"
1684336,2017-06-12 09:34:46 UTC,"Same problem after apt update && apt upgrade. Ubuntu 16.04.2 Unity, synclient -V outputs 1.8.3.
Running touchegg in the foreground doesn't show any signs of life with any gesture."
1684336,2017-05-29 20:14:04 UTC,Same after upgrading to Ubuntu 17.04
1684336,2017-05-19 11:54:16 UTC,"Sane, xubunru 17.04"
1684336,2017-05-12 15:12:02 UTC,"Same thing here: Touchegg worked before, not anymore after upgrade to Kubuntu 17.04."
1684336,2017-04-23 21:28:47 UTC,"Max, excellent and thank you for cross-referencing with Jose Exposito."
1684336,2017-04-21 06:49:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684336,2017-04-20 08:52:22 UTC,apport information
1684336,2017-04-20 09:01:29 UTC,apport information
1684336,2017-04-20 09:01:27 UTC,apport information
1684336,2017-04-20 09:01:25 UTC,apport information
1684336,2017-04-20 08:52:25 UTC,apport information
1684336,2017-04-20 08:52:24 UTC,apport information
1684336,2017-04-20 08:52:23 UTC,apport information
1684336,2017-04-20 09:01:30 UTC,apport information
1684341,2017-06-06 23:00:00 UTC,"Hello Mathieu, or anyone else affected,"
1684341,2017-06-19 10:53:42 UTC,This bug was fixed in the package grub2 - 2.02~beta3-4ubuntu2.1
1684341,2017-06-16 17:14:40 UTC,Verification done for zesty:
1684341,2017-06-15 21:45:30 UTC,Verification done for yakkety:
1684341,2017-06-15 21:20:03 UTC,This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.11
1684341,2017-06-19 10:57:42 UTC,This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu11.3
1684341,2017-06-14 19:12:41 UTC,Verification done on xenial:
1684341,2017-06-06 23:25:32 UTC,"Hello Mathieu, or anyone else affected,"
1684341,2017-06-06 22:32:32 UTC,"Hello Mathieu, or anyone else affected,"
1684341,2017-05-20 00:41:17 UTC,"Hello Mathieu, or anyone else affected,"
1684341,2017-05-20 19:32:29 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of grub2 from xenial-proposed was performed and bug 1692181 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1692181 (not this bug). Thanks!"
1684341,2017-05-20 11:32:29 UTC,"looks like this change broke the installation process of grub-pc_2.02~beta2-36ubuntu3.10 for me (syntax-error in grub-pc.postinst). Please see bug #1692175, which is for grub-efi-amd64 2.02~beta2-36ubuntu3.10 but I believe the file might be the same anyway."
1684341,2017-05-20 00:50:23 UTC,"An upload of grub2 to yakkety-proposed has been rejected from the upload queue for the following reason: ""needs upgrade handling to remove /boot/efi/EFI/ubuntu/fbx64.efi""."
1684341,2017-05-20 00:48:49 UTC,"Hello Mathieu, or anyone else affected,"
1684341,2017-05-19 20:48:11 UTC,"An upload of grub2 to xenial-proposed has been rejected from the upload queue for the following reason: ""SRU should handle removal of /boot/efi/EFI/ubuntu/fb$arch.efi on disk""."
1684341,2017-05-11 19:51:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684341,2017-04-28 02:27:05 UTC,This bug was fixed in the package grub2 - 2.02~beta3-4ubuntu3
1684341,2017-06-06 22:17:58 UTC,"Hello Mathieu, or anyone else affected,"
1684343,2019-10-15 12:01:15 UTC,I'm re-assigning this to subiquity because it controls the display during that time.
1684347,2017-04-20 03:53:50 UTC,See upstream bug https://bugs.mysql.com/bug.php?id=85382
1684347,2017-04-20 03:58:39 UTC,"mysql  Ver 14.14 Distrib 5.7.17-13, for Linux (x86_64) using  6.0
Server version:		5.7.17-13-log Percona Server (GPL), Release 13, Revision fd33d43
CentOS release 6.8 (Final)"
1684347,2018-01-25 09:13:35 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1804
1684379,2017-08-22 18:40:31 UTC,Kevin/Ihar: please see comment #1 and if you have any thoughts as to what we should target/doc here. Thanks
1684379,2017-08-22 17:01:47 UTC,"IIUC, the documenting of running the API in wsgi env may require some work in order to collect the proper steps/docs/sample-configs, etc."
1684379,2017-10-09 20:54:09 UTC,"Based on discussion at the Denver PTG, this implementation isn't even done yet.
I'm moving this to wishlist as I think we need to bake the impl for awhile before addressing with in-depth docs."
1684413,2017-04-20 06:36:21 UTC,"It is also possible to 'juju resolved --no-retry' the unit until the original upgrade-charm hook has had a chance to run, but this would still be better resolved by 'juju upgrade-charm --force-units' doing what it is told and forcing an upgrade onto the units."
1684413,2017-04-26 00:50:42 UTC,"I do think we need to look at why the unit is currently failing, and the implications that might happen should we skip a number of other pending hook executions in order to force the charm update."
1684457,2018-06-27 02:27:11 UTC,"I have met the same problem, is there anyone know how to solve this? thx"
1684468,2017-10-26 20:12:13 UTC,Keystone package for reference: lp:~ubuntu-server-dev/ubuntu/+source/keystone
1684468,2017-10-26 20:11:00 UTC,"Hi Yuuki,"
1684468,2017-10-31 20:32:34 UTC,"Hi Yuuki,"
1684468,2021-01-08 15:38:02 UTC,I'm marking this wontfix for Ocata and Pike as those are end of life.
1684481,2017-04-20 16:12:49 UTC,apport information
1684481,2017-04-20 16:12:47 UTC,apport information
1684481,2017-04-20 16:12:44 UTC,apport information
1684481,2017-04-20 16:12:42 UTC,apport information
1684481,2017-04-20 16:12:41 UTC,apport information
1684481,2017-04-20 16:12:35 UTC,apport information
1684481,2017-04-20 16:12:38 UTC,apport information
1684481,2017-04-20 16:12:36 UTC,apport information
1684481,2017-04-20 16:12:32 UTC,apport information
1684481,2017-04-20 16:12:51 UTC,apport information
1684481,2017-04-20 16:12:33 UTC,apport information
1684481,2017-04-20 16:12:39 UTC,apport information
1684481,2017-04-20 16:12:53 UTC,apport information
1684481,2017-04-20 16:08:27 UTC,apport information
1684481,2017-04-20 16:13:47 UTC,"Since apport-collect detected this as apparmor for the report I was also forcing a ""linux"" apport collect via ""sudo apport-collect --package=linux 1684481"" on the host - since the guest is LXD the kernel there (if any) doesn't matter)."
1684481,2017-04-20 16:31:17 UTC,This change was made by a bot.
1684481,2017-04-20 22:36:23 UTC,"Ok, so that's an apparmor or apparmor profile problem."
1684481,2017-04-20 23:16:03 UTC,Its true there are a few issues with apparmor profiles being loaded as part of a stack when namespacing is involved. However this does not appear to be one of them.
1684481,2017-04-21 06:37:41 UTC,"Thanks Stephane for outlining the likely related timeline of changes.
Thanks John for picking that up, let me search the profiles for you."
1684481,2017-04-21 06:50:37 UTC,"Now the abstraction used in this case via:
#include <abstractions/libvirt-qemu>"
1684481,2017-04-21 08:26:50 UTC,"Hey Christian,"
1684481,2017-04-21 09:29:01 UTC,"Thank John,
as extra info on the ptmx pathing."
1684481,2017-04-21 16:55:38 UTC,"We're looking at changing lxc to show /dev/ptmx as a real file rather than symlink. This is however not particularly easy because:
 - It can't be a bind-mount from the host (or it will interact with the host's devpts)
 - It can't be a straight mknod (because that's not allowed in unprivileged containers)"
1684481,2017-04-21 20:26:53 UTC,"Thanks Stéphane,"
1684481,2017-04-21 22:17:37 UTC,"Hi John,
hi Christian,"
1684481,2017-04-24 05:40:40 UTC,Thanks Stephane and Christian!
1684481,2017-04-20 16:12:30 UTC,apport information
1684481,2017-04-20 16:12:56 UTC,apport information
1684481,2017-04-20 16:12:28 UTC,apport information
1684481,2017-04-20 16:08:17 UTC,apport information
1684481,2017-04-20 16:08:31 UTC,apport information
1684481,2017-04-20 08:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1684481,2017-04-20 15:54:17 UTC,apport information
1684481,2017-04-20 15:54:19 UTC,apport information
1684481,2017-04-20 15:54:20 UTC,apport information
1684481,2017-04-20 15:54:22 UTC,apport information
1684481,2017-04-20 15:54:24 UTC,apport information
1684481,2017-04-20 15:54:27 UTC,apport information
1684481,2017-04-20 15:54:28 UTC,apport information
1684481,2017-04-20 15:54:30 UTC,apport information
1684481,2017-04-20 15:54:31 UTC,apport information
1684481,2017-04-20 15:54:33 UTC,apport information
1684481,2017-04-20 15:54:26 UTC,apport information
1684481,2017-04-20 16:08:30 UTC,apport information
1684481,2017-04-20 16:08:19 UTC,apport information
1684481,2017-04-20 16:08:20 UTC,apport information
1684481,2017-04-20 16:08:22 UTC,apport information
1684481,2017-04-20 16:08:24 UTC,apport information
1684481,2017-04-20 16:08:25 UTC,apport information
1684481,2017-04-20 16:12:26 UTC,apport information
1684481,2017-04-20 16:08:29 UTC,apport information
1684481,2017-04-20 16:07:03 UTC,"Running apport-collect on Host (Xenial) and LXD Container (Xenial as well).
BTW I saw LXD is not in the report, it is at:
*** 2.12-0ubuntu3~ubuntu16.04.1~ppa1 500
    500 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu xenial/main ppc64el Packages
    100 /var/lib/dpkg/status"
1684486,2017-06-02 11:15:36 UTC,"Reviewed:  https://review.openstack.org/467496
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=3bba7ae8290cc08a15b5a6f14851d43cd4f57113
Submitter: Jenkins
Branch:    master"
1684486,2017-06-02 11:07:28 UTC,"Reviewed:  https://review.openstack.org/467495
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=d3e08b15fc3a698f4379085813c70ac862dc1afc
Submitter: Jenkins
Branch:    master"
1684486,2017-05-24 06:36:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467497"
1684486,2017-05-24 06:35:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467496"
1684486,2017-05-24 06:35:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467495"
1684486,2017-11-16 05:22:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/520295"
1684486,2017-12-29 00:52:03 UTC,"Reviewed:  https://review.openstack.org/520295
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=2372fbfe541ae37e8b151c7b502617e1db2370af
Submitter: Zuul
Branch:    master"
1684486,2019-12-04 08:58:24 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1684486,2019-12-04 08:58:32 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/467497
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1684486,2017-11-04 23:00:16 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/467497
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1684486,2017-04-20 08:27:17 UTC,https://review.openstack.org/#/c/458391/  project-config
1684488,2017-04-20 08:27:58 UTC,https://review.openstack.org/#/c/458392/ project-config
1684489,2017-04-20 08:12:26 UTC,"Launchpad added the xubuntu-meta package name to this bug, but I am not sure if that is correct, i.e. it might be that this is a general updating issue."
1684503,2017-06-28 01:16:20 UTC,Update Mojo's embedded copy of wait.py to version 2.5.1 or later.
1684507,2017-04-20 11:32:45 UTC,Attached is a patch that fixes the issue.
1684507,2017-05-09 14:44:47 UTC,"The bug fix is now in the repository (ocamlbricks).
Merci Stéphane,
Jean-Vincent"
1684523,2019-04-01 08:48:29 UTC,The template now says:
1684523,2020-03-23 02:48:54 UTC,"Hi,
I've confirmed once I change port with:"
1684529,2018-12-19 15:34:34 UTC,"Colin, suspect this might be impacted by the retry work that we're doing on LP?"
1684529,2017-04-28 15:25:26 UTC,"While snapcraft provides the --release flag as a convenience, in reality the process happens in distinct stages:"
1684529,2017-07-27 15:49:38 UTC,"> But note that if the store says the snap is NOT ready to publish (held for
> manual review, held behind another upload pending review or outright failed
> automated review) then snapcraft exits and doesn't have a chance to issue the
> publish request. Like you observed, an explicit snapcraft release is required
> in order to publish at this point.
"
1684529,2018-02-28 23:30:45 UTC,"I just want to add: not only is that single snap not released, but _every snap that is pushed after it_ loses the release intent as well. The store hiccuped on the first of like 10 snaps pushed from my CI today, showing a ""scan error."" Not only did that hold up the automated review of every following snap requiring manual intervention, but the release intent of every other snap pushed was lost. In many cases (since versions don't need to change) it's impossible to determine which release should go to which channel using only version and revision, requiring someone to take _further_ manual interaction to spin up new builds from CI, new uploads, and new releases."
1684529,2019-06-20 18:42:31 UTC,"There are one or two more bits to fix with how Launchpad presents the case where a pushed snap is held for manual review, but it's now passing release intents through to the store and the store is handling it from there."
1684529,2019-06-20 00:55:32 UTC,Fixed in stable r18988 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18988>.
1684588,2020-05-14 11:08:08 UTC,"ppc64el now finds qemu, but arm64 and s390x still does not."
1684600,2017-05-03 22:17:54 UTC,Code like
1684600,2017-05-03 22:10:54 UTC,Valid point. Repairing apport/packaging.py's get_os_version() is the way to go.
1684600,2017-05-03 20:17:12 UTC,Is there any reason not to fix this in apport/packaging.py's get_os_version() which is used to get DistroRelease?
1684600,2017-05-05 09:36:52 UTC,The updated patch is attached.
1684606,2018-11-26 16:45:27 UTC,"I'm now the new Debian Maintainer of it. And my sponsor uploaded today for me the new upstream version 1.5.3 to Debian unstable.
So now only someone from Ubuntu needs to pull it."
1684606,2019-10-27 10:39:15 UTC,"Looks like this was synced automatically, 1.5.3-1build1 is available in Ubuntu 19.04. (and 19.10 has an even newer version)"
1684652,2017-05-07 18:17:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684678,2017-05-11 07:30:59 UTC,"Since the release of NVIDIA 375.66, this issue is resolved for me. For reference, I have a GeForce 840M, in a Dell Latitude e7450 running Ubuntu 17.04."
1684678,2017-04-30 19:18:43 UTC,"This also affects me. I'm on a Latitude e7450, and tried exactly the steps described above, but no luck."
1684678,2018-03-07 20:34:46 UTC,"Same here in a Acer Aspire E5-771G with GeForce 820M.
The recent 4.4.0-112 has this issue yet, while 4.4.0-116 is not working for different reasons (perhaps has the same issue too, cannot know for it doesn't boot)."
1684678,2017-05-19 15:47:08 UTC,"@Andy, does NVIDIA 375.66 work for you?"
1684678,2017-06-10 12:36:48 UTC,I got the NVIDIA 375.66 update but still the problem persists..
1684678,2017-10-10 18:46:51 UTC,"I have a Dell Vostro 5470 with GeForce GT 740M and driver version 375.66. The bug is applied to me too, in the kernel versions 4.4.0-96-generic and 4.4.0-97-generic."
1684678,2017-04-22 16:32:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684678,2017-05-05 22:22:57 UTC,"Affects me too. This computer (an Asus VivoBook V551L) has worked successfully on about seven previous Ubuntu versions, but on upgrading to 17.04, it won't boot with exactly the error described above."
1684690,2017-05-03 20:29:03 UTC,I think we'd want to read the report's 'DistroRelease' field.
1684755,2017-11-25 11:29:39 UTC,"I was stung by this using the Mesa driver.
I concur that it should be a dependency of libgl1-mesa-dri instead of recommended, unless there is some downside to it that I can't see. I'm not a 3d drivers expert."
1684755,2017-07-02 06:10:07 UTC,I think this issue would be most easily solved by changing the package libtxc-dxtn-s2tc to be a required dependency for libgl1-mesa-dri rather than just a recommended package.
1684755,2017-07-02 06:03:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684755,2021-01-10 23:23:11 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1684772,2017-04-22 05:35:09 UTC,I've noticed that the desktop freezes when coming back from suspend and sometimes if you're switching from laptop display to a desktop display (via usb-c to HDMI). Gnome shell appears to crash or hang for minutes and requires a hard restart via power button.
1684772,2017-12-17 06:45:41 UTC,I can confirm this. It happens on my desktop PC and on my Lenovo Yoga 300. Maybe a switch to a higher gnome shell version would help?
1684776,2020-03-19 14:48:50 UTC,"As we're not testing ARM64 on Trusty ESM anymore, I will close this."
1684776,2018-09-13 09:23:31 UTC,This issue still exists
1684776,2017-04-21 17:24:04 UTC,"Hi,"
1684776,2017-09-14 06:43:15 UTC,Oh sorry missed this comment.
1684776,2018-01-18 04:46:40 UTC,Failed with Trusty kernel on Trusty too.
1684776,2018-02-07 07:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1684776,2018-09-12 18:21:13 UTC,"sam, any reason to keep this open?   i see random updates on it, yet have no looked at the issue in its entirety."
1684788,2020-07-24 21:36:05 UTC,Xenial 4.4.0-187.217
1684788,2018-09-12 18:19:29 UTC,"Sam, Joe,  is this still something to watch out for?    Considering we don't have logs from a year ago, just going to close if no action."
1684788,2017-09-18 09:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1684788,2018-09-13 08:13:30 UTC,"Hi Sean,"
1684789,2019-11-12 23:52:38 UTC,"I just tried this on an s390x box running Xenial. This is still an issue, but I don't think constrained to T-LTS like mentioned earlier."
1684789,2017-09-18 09:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1684789,2018-03-19 11:01:29 UTC,"The interesting thing is that this test passed on Trusty with 3.13 kernel, and Xenial with 4.4 kernel, just not 4.4 kernel on Trusty."
1684789,2018-09-12 18:23:33 UTC,"hi sam, joe, still an issue?  no updates in months."
1684789,2020-08-10 05:06:33 UTC,"Didn't see this on X-4.4 (passed with all arches) and T-4.4 (passed with all arches), closing this bug."
1684836,2018-01-09 18:20:10 UTC,modify the epiphany.desktop launcher (in /home/moncompte/.local/share/applications/) with scratch in order to obtain the following line:
1684836,2018-01-06 12:35:30 UTC,"Clicking a link in a pdf file or in a libreoffice document,  does also not open the related page in epiphany but only a new tab or window"
1684845,2017-05-05 12:36:20 UTC,The same occurs if I will make the pitch higher and higher in the Rubberband mode.
1684845,2017-05-05 12:33:11 UTC,"Debug [Controller]: ""__control: ""
Debug [Controller]: ""CMD PL-1 MIDI 1: outgoing: status 0xB0 (ch 1, opcode 0xB), ctrl 0x04, val 0x97""
Resampler::process: libsamplerate error: SRC ratio outside [1/256, 256] range.
terminate called after throwing an instance of 'RubberBand::Resampler::Exception'
Aborted"
1684845,2017-04-28 21:42:52 UTC,From the backtrace it looks like you are using SoundTouch. Does this also occur if you use Rubberband? You can switch between them in the Sound Hardware Preferences (that is admittedly a confusing place for that preference option).
1684845,2017-05-06 17:51:36 UTC,"I can confirm this, [Channel1],pitch = 30 works and [Channel1],pitch = 40 -> crash  (Soundtouch)
Rubberband crashes later, at least at 300.
I think a good band aid is to limit these values to a reasonable number."
1684845,2017-11-12 18:23:43 UTC,"Considering this only affects an edge case and has only been reported by one user, I am demoting it from Critical to High. If someone wants to step up to take care of this for 2.1, reassign it to that milestone."
1684845,2017-05-06 18:05:19 UTC,"@daschuer, yes."
1684845,2017-11-12 17:16:22 UTC,I am not able to make it.
1684845,2017-11-12 17:12:38 UTC,Hello Be. I am not going to make it.
1684845,2017-11-11 16:13:52 UTC,"Wihola IT, have you made any progress working on this bug or should someone else take it up for 2.1?"
1684845,2017-05-06 17:52:41 UTC,@Wihola IT: do you have fun to adopt this bug?
1684847,2017-04-25 08:05:13 UTC,Raised https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1686039 for the package update.
1684847,2017-04-25 06:19:18 UTC,Strange. I thought I'd set this to invalid. 2nd try..
1684847,2017-04-25 07:59:51 UTC,"This is indeed invalid from the software side, once there is a fix in the newer version, but it is not invalid if you look at it from the user's side which doesn't get the latest/fixed version from the distribution repos."
1684847,2017-05-22 14:07:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684847,2017-11-03 09:57:21 UTC,any updates?
1684847,2017-04-24 14:38:46 UTC,Updated packages fixing the problem can be downloaded from this PPA:
1684847,2017-04-20 19:57:45 UTC,Marking as Invalid/no-action
1684847,2017-04-24 19:58:22 UTC,I've had trouble installing the nightly. I get this error:
1684847,2017-04-20 18:34:14 UTC,I can reproduce with Ubuntu 17.04's package (1.90+bzr-1705-1) but not with current bzr (1.91+).
1684847,2017-04-20 19:57:18 UTC,"Yup, known and already fixed issue. Ubuntu 17.04 is packaging 1.90, and the fixes went in after that. It is a complex interaction of theme & gtk version and fixes to get the transparency to work which caused this."
1684850,2017-04-24 11:36:43 UTC,"Yep, thanks for the Report Mikko and your help to Make Ubuntu better!"
1684850,2017-04-24 15:28:19 UTC,"I'm okay with next auto-sync pulling the fix in. It's only the documentation problem and the short option ""-s"" works as described."
1684850,2019-07-02 16:15:42 UTC,Still broken
1684854,2017-04-24 07:16:29 UTC,Kubuntu 17.04: openvpn
1684854,2017-09-14 13:24:13 UTC,"> PS: short domains also don't work. Only FQDNs.
"
1684854,2017-09-14 11:11:51 UTC,"I added search domains in '/etc/resolvconf/resolv.conf.d/base'. Now, I have at least named access to servers outside of our internal network."
1684854,2017-08-08 21:00:46 UTC,I struggled with this long enough and took some notes about a workaround here: https://thealarmclocksixam.com/2017/08/08/dns-configuration-with-vpns-and-ubuntu-17-04-working-again/
1684854,2017-06-09 06:35:59 UTC,As a workaround you can do:
1684854,2017-04-26 07:47:22 UTC,This isssue is not relevant to VPN connections only but also for normal workin local network. systemd-resolve and systemd-resolved stub listener are behaving differently - the stub does not accept the domain/search domains sent by DHCP. THis is really weird. Isn't the issue in domain/search domains not properly put into a dynamic /etc/resolv.conf  ?
1684854,2017-04-26 07:05:04 UTC,Seems this lines of code are responsible:
1684854,2017-04-21 12:44:45 UTC,"I did some more tests. Using ""dns-search=my.domain"" and ""ignore-auto-dns=true"" actually works for wifi connections. For VPN (vpnc) is does not work."
1684854,2017-04-24 08:48:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684861,2017-08-12 00:37:49 UTC,"Reviewed:  https://review.openstack.org/463366
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7b29a5cf9e19ef5885759259aab439473d01a6b5
Submitter: Jenkins
Branch:    stable/newton"
1684861,2017-04-25 07:48:27 UTC,If you messed up the database during the upgrade from Kilo to Liberty following the workaround of bug 1511466 (comments #3 and #9) you can use this python script to fix your database:
1684861,2017-05-07 22:37:33 UTC,"Reviewed:  https://review.openstack.org/458564
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2cee5bb4d14a5ad6a037857bd3624833317cd931
Submitter: Jenkins
Branch:    master"
1684861,2017-05-08 16:25:36 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/463364"
1684861,2017-05-08 16:26:06 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/463366"
1684861,2017-06-12 16:19:41 UTC,"Reviewed:  https://review.openstack.org/463364
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=593e7081148b2b15f5923a8d7c609ae71dcbdbb6
Submitter: Jenkins
Branch:    stable/ocata"
1684861,2017-04-26 06:54:14 UTC,If you messed up the database during the upgrade from Kilo to Liberty following the workaround of bug 1511466 (comments #3 and #9) you can fix with this query:
1684861,2017-06-29 11:43:38 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1684861,2017-04-20 15:59:39 UTC,"Unfortunately, this bug seems to have been triggered by the ""workaround"" offered in bug 1511466, which disabled FK constraints and broke the model linkage between InstanceExtra and Instance. Doing so breaks a lot of code that assumes this linkage, and this bug is one manifestation of the problem."
1684861,2017-04-20 15:51:23 UTC,"This will probably happen to all those operators that in the upgrade Kilo to Liberty did follow this workaround here:
https://bugs.launchpad.net/nova/+bug/1511466"
1684861,2017-04-20 15:53:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/458564"
1684946,2018-03-03 08:21:11 UTC,I tested this with all 5 of the desktops I have.
1684946,2018-03-28 02:54:54 UTC,"Also, this is not only an issue for Kazam. OBS has the same problem when trying to record the entire screen."
1684967,2017-05-05 16:52:48 UTC,"Rohan, could you cherry-pick the commit (https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2a960d3936d78087d74ba556df8ac808639c96a0) mentioned in the https://bugzilla.gnome.org/show_bug.cgi?id=781580."
1684967,2017-05-05 16:46:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1684967,2017-05-02 07:02:34 UTC,"and this is supposed to be a solution for which problem? For disabled save button or for vpn passwords edit boxes shown empty disregarding if a show password checkbox is selected? What vpn connections have to do with the wireless security, huh?"
1684967,2017-05-02 06:34:26 UTC,"1.Go to ""connection information""
2.Left click the connections icon at the top right.
3.Choose edit connections and then choose edit on the connection you need and click the wireless security.
4.And click the 'show password'checkbox
5.Click on edit password
6.Change the password and save password"
1684967,2017-04-21 10:02:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1684967,2017-04-21 11:34:24 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=781580
1684986,2017-05-06 09:08:36 UTC,"(resubmitting against the right bug report, see 1684987)"
1684987,2017-05-04 11:35:17 UTC,"Hi,"
1684987,2017-05-06 02:48:50 UTC,I retested this with hplip-3.17.4.run but I am getting the same result. Here is the debug output of hp-levels:
1684987,2017-05-06 09:11:23 UTC,"Please ignore the previous message: I sent it against the wrong bug report, it concerns bug 1684986 instead."
1684989,2017-07-13 02:44:42 UTC,"Reviewed:  https://review.openstack.org/458626
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=1ae904a4912494b3d0ac87f22aaf958129744548
Submitter: Jenkins
Branch:    master"
1684989,2017-07-26 01:39:30 UTC,This issue was fixed in the openstack/python-openstackclient 3.12.0 release.
1684989,2017-04-20 19:20:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458626"
1684989,2017-04-20 18:16:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458608"
1684989,2017-04-20 18:57:40 UTC,"Reviewed:  https://review.openstack.org/458608
Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=a98d3ada2a4d51bd5fbd676fe3306871ad8228eb
Submitter: Jenkins
Branch:    master"
1685001,2017-04-20 23:13:49 UTC,What configuration involving quotes are you using?
1685001,2017-04-21 05:00:47 UTC,From ~/.config/variety/variety.conf:
1685004,2020-01-20 17:56:09 UTC,Also:
1685004,2020-04-07 15:21:16 UTC,"KiCad has migrated to Gitlab, this issue is available here: https://gitlab.com/kicad/code/kicad/-/issues/2061"
1685004,2019-11-12 16:21:37 UTC,I am creating a footprint which has to be compatible with a variety of similar parts (EC11 encoders).
1685004,2019-11-12 16:16:52 UTC,"The 3D viewer (ALT+3) ignores the ""Preview"" check box. Instead I see *all* 3D models overlaid.
----------------------------------------------------------------------------------------------
#Application: KiCad
Version: (5.1.4)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 32 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 7.3.0 with C++ ABI 1011"
1685004,2020-01-20 17:51:43 UTC,It works temporarily (i.e. whilst staying in PcbNew): Press 'E' (Edit) in PcbNew. Toggle visibility on one of several 3D models in a list. Return to PcbNew; 'Save' is now enabled (but does nothing useful).
1685018,2017-09-26 18:57:48 UTC,"There is no activity for fixing this bug for a while. I am going to remove assignee so that other contributors can take it, but please feel free to re-assign it to yourself if you want to continue to work on this bug."
1685019,2017-04-20 20:32:27 UTC,"For reference - same issue as bug 1672879
For agents, it can be argued that the controller agent stream should override model streams for API compatibility reasons. For image streams, that assertion doesn't hold true."
1685019,2017-06-01 03:48:29 UTC,"Ryan, we can prioritise this and other stakeholder issues based on how much they really hurt us."
1685019,2019-07-16 22:51:59 UTC,"Similar behavior has been observed with image-metadata-url as per bug # 1836814. Since both properties are in the same area, potentially these 2 bugs can be fixed at the same time."
1685025,2017-04-21 12:30:07 UTC,"confirmed on Windows 10, Inkscape 0.92+devel 15626"
1685025,2017-04-21 13:54:01 UTC,"Thanks for testing, Alvin!"
1685025,2017-05-01 15:25:49 UTC,"Also reproduced on Xubuntu 16.04, Inkscape 0.91 and lp:inkscape rev. 15657."
1685035,2018-07-25 01:50:29 UTC,Still happening for me as well...
1685035,2018-07-16 19:22:23 UTC,This bug is still happening on my 4K monitor with resolution 3840x2160 (16:9) and 200% scaling.
1685035,2017-11-05 23:15:03 UTC,"For me, the GDM screen is scaling the icons and text correctly."
1685035,2017-10-10 21:57:37 UTC,"I think this is still happening on 17.10 with 3.26.1-3ubuntu1.
I'm on a Lenovo Thinkpad T470p laptop with Intel video card."
1685035,2017-05-29 15:25:54 UTC,"The verification of the Stable Release Update for gnome-settings-daemon has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1685035,2017-05-16 15:13:51 UTC,"Hello jefferson, or anyone else affected,"
1685035,2017-05-22 09:40:46 UTC,"installed v3.24.2 in 17.04 proposed today and it works fine, Thank you :)"
1685035,2017-04-25 19:08:19 UTC,"Okay, before reverting out of curiousity I did try the recently updates packages and can confirm the issue is resolved, and everything seems stable, no regressions."
1685035,2017-04-25 12:02:56 UTC,"jefferson9, please don't install packages built for artful (Ubuntu 17.10) on your zesty (Ubuntu 17.04) install. Here's how I recommend getting back to the zesty packages. The gnome-settings-daemon-dev and gnome-settings-daemon-dbgsym packages are not in the default install and aren't needed by most people (but it's fine to keep them installed if you think you want them)."
1685035,2017-04-25 06:45:24 UTC,"OP here, I installed the 4 packages here: https://launchpad.net/ubuntu/+source/gnome-settings-daemon/3.24.1-0ubuntu2/+build/12460693 (change log has that patch)"
1685035,2017-04-22 15:01:52 UTC,This bug was fixed in the package gnome-settings-daemon - 3.24.1-0ubuntu2
1685035,2017-04-20 22:51:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1685035,2017-05-29 15:25:39 UTC,This bug was fixed in the package gnome-settings-daemon - 3.24.2-0ubuntu0.1
1685043,2017-04-20 23:40:54 UTC,Workaround for now is that I have to convert lxd:storage=0 to lxd:X where X is the machine number where storage/3 (zero'eth storage unit) resides.
1685043,2017-07-07 23:19:56 UTC,"It appears that defining ""services:"" as a top-level bundle definition name ends up overriding the juju model services when running through yaml definition validate tests.  It also changes yaml version parsing from V3 to V4 code."
1685046,2018-01-08 14:09:21 UTC,This is a nice idea and I would suggest to discuss it in the forum. We'll probably close it soon as we're trying to make use of the forum for discussions and keep launchpad for strict bugs.
1685057,2017-05-11 09:35:02 UTC,The problem is due to the same issue that caused https://bugs.launchpad.net/juniperopenstack/+bug/1680720 and https://bugs.launchpad.net/juniperopenstack/+bug/1681083.
1685077,2020-06-14 18:58:51 UTC,"I realize this is almost 3 years old, but I have had similar issues on Windows 10 and wanted to include a comment in case it helps anyone.  In my case, it was mounted Veracrypt drives causing win32diskimager to fail to start.  Unmount them, and it opens up immediately."
1685077,2017-08-08 22:20:35 UTC,"I root caused this to a race condition and have uploaded code to the git tree to work around it.  This may not be the final solution, but at least I can add this to my testing.  This will be fixed in the next release."
1685077,2017-04-22 06:32:13 UTC,"Ok I do indeed have a ramdrive running.  I have disable the drive and the software now comes up.  Thanks for the heads up.  I am using softperfect RAM disk the full purchased version.  I now at least can disable it when I want to use win32diskimager.  Let me know if you need me to test anything out happy to help but also understand this is your spare time thing so no pressure from me.  However thank you for your response, Big thank  you for your product, Cheers mate."
1685077,2017-04-21 17:08:14 UTC,"First, do you have any drive letters assigned to network shares , ramdisks, or using the ASSIGN to reassign a folder to a drive letter?  This appears to be a common issue that I am looking into.  If that is the case, I already have several bug reports both here and on Sourceforge."
1685108,2019-09-19 12:03:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1685109,2017-06-12 09:14:15 UTC,working on this
1685109,2019-10-28 18:02:07 UTC,"Is anyone working on this issue, is this still an issue in the latest build of manila"
1685112,2017-04-27 01:32:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685114,2019-09-17 09:55:20 UTC,Migrated to https://github.com/widelands/widelands/issues/2076
1685131,2017-04-21 11:12:56 UTC,I am using this backport and it's working:
1685131,2017-04-25 08:00:20 UTC,Hi Thomas thank you for your report and your help to make Ubuntu better.
1685131,2017-04-25 09:31:25 UTC,I've requested to add that commit to sssd-1-13 branch so that it'd be included in 1.13.5 which should be released sometime soonish
1685141,2018-05-12 08:44:30 UTC,"I also had this problem with AMD64 & Nvidia Geforce, but it doesn't actually freeze the system, you just can't get out of the screen lock.
I solved it by un-checking the option to show notifications on the lock screen - no problems since then."
1685141,2017-12-20 18:13:09 UTC,Also affected by this very annoying bug
1685141,2017-09-21 16:45:13 UTC,Also affects me. AMD GPU.
1685141,2017-05-27 11:55:47 UTC,"@stoutlaw You can disable it through the settings panel in the ""Notifications"" section."
1685141,2017-05-27 11:09:44 UTC,@jaes I'm not sure how you disabled notifications on the lock screen as I'm unable to find any settings along the lines of what you described on stock 17.04.
1685141,2017-05-10 13:10:45 UTC,"It seems, using the proprietary NVIDIA-driver works for me."
1685141,2017-04-23 15:37:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685141,2017-05-03 08:13:29 UTC,Same happened to me. For whatever reason both Intel Microcode and nvidia proprietary drivers were not used after upgrade from 16.10.
1685141,2017-04-28 17:14:43 UTC,I tried it with the Intel Graphics and it also happens.
1685141,2017-04-28 14:59:48 UTC,"Hi, I've been experiencing this bug too."
1685141,2017-04-28 07:45:39 UTC,"Well, ignore what I wrote above. The bug occured to me this morning."
1685141,2017-04-27 07:48:15 UTC,"Can wonfirm mwclark method. I installed the fitting driver through ""ubuntu-drivers autoinstall"" and for now it seems to have solved the problem."
1685141,2017-04-26 16:43:44 UTC,"I switched from the open source xserver-xorg-video-nouveau driver to nvidia-375 in the Additional Drivers tab of the Software & Updates application and was able to recover after locking my screen with Ctrl-Alt-L, which was locking up my mouse and keyboard before."
1685141,2017-05-03 08:37:44 UTC,I think I found a workaround. I noticed the traceback I saw in syslog happened a lot before I tried to log back in and I deduced it happened when notification were displayed on my locked screen.
1685145,2017-04-21 09:40:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458793"
1685147,2017-08-30 05:12:36 UTC,"Change abandoned by Madhuri Kumari (<email address hidden>) on branch: master
Review: https://review.openstack.org/458332
Reason: Abandoning this patch according to Akihiro's comments."
1685147,2017-04-21 12:56:28 UTC,"Reviewed:  https://review.openstack.org/457883
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=1a9768ac58a98964fb39a3ad5cb5b593f2a6e138
Submitter: Jenkins
Branch:    master"
1685147,2017-04-21 10:21:21 UTC,"For manila this issue is for the api-ref, not for the docs proper.  I adjusted the title of the bug accordingly but then saw that the bug is being used for zun to, so set it back."
1685147,2017-06-08 19:53:34 UTC,This issue was fixed in the openstack/manila 5.0.0.0b2 development milestone.
1685179,2020-03-18 05:22:31 UTC,"First, I think there is misunderstanding about the id `1`:
it's not autoincrementing id for the datasource, it's the org_id for the datasource, which is normally 1, but could be different."
1685182,2017-07-05 15:40:41 UTC,"Till, could you have a look to this one?"
1685182,2017-07-05 16:28:40 UTC,"This should be fixed upstream in cups-filters 1.14.1, which is already in artful-proposed (synced from Debian)."
1685185,2017-04-21 11:11:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458807"
1685185,2017-08-28 09:55:05 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1685185,2017-06-19 12:46:04 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1685185,2017-08-22 00:08:34 UTC,"Reviewed:  https://review.openstack.org/460482
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8fb411c9b2af9bb5fef3cc272517c54bab821cd4
Submitter: Jenkins
Branch:    stable/newton"
1685185,2017-06-06 22:13:05 UTC,"Reviewed:  https://review.openstack.org/460296
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fbcf8d673342570a1518dbf8d88f289c2c39cd30
Submitter: Jenkins
Branch:    stable/ocata"
1685185,2017-04-27 10:01:09 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/460482"
1685185,2017-04-26 20:26:08 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/460296"
1685185,2017-04-26 11:39:53 UTC,"Reviewed:  https://review.openstack.org/458807
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=809065485c19fd535db6740bb21b867c41c008fe
Submitter: Jenkins
Branch:    master"
1685185,2017-06-08 21:53:01 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1685189,2017-04-22 15:25:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685189,2017-04-21 11:34:40 UTC,"seems to be the same bug as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839870"
1685191,2018-04-24 00:23:17 UTC,Meet with the same issue in Queens dashboard.
1685193,2017-04-30 15:20:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685193,2017-05-05 17:54:55 UTC,"Yes, there are no permissions to write to /var/log, that is so far intentional."
1685193,2017-05-06 05:37:04 UTC,what are the intentions?
1685204,2017-04-24 09:13:35 UTC,This relates to the issue http://www.disobey.com/detergent/2002/extendingrss2/
1685212,2017-04-22 18:06:43 UTC,anyone can help me? please
1685212,2017-05-23 10:11:08 UTC,update on my lab:
1685212,2017-10-04 18:17:11 UTC,Was hoping there was a fix. I'm also having the same problem.
1685212,2018-01-22 18:14:05 UTC,Can confirm. I get the same issue.
1685216,2017-04-21 21:15:19 UTC,"Bug is fixed in Ubuntu 16.10.
Please backport http://archive.ubuntu.com/ubuntu/pool/universe/m/meld/meld_3.16.3-1_all.deb to Xenial."
1685223,2017-04-27 12:36:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/460528"
1685223,2017-05-31 23:52:20 UTC,"Reviewed:  https://review.openstack.org/460528
Committed: https://git.openstack.org/cgit/openstack/octavia/commit/?id=717bee352dc53c990e3dfbe2fa655a35afc617ef
Submitter: Jenkins
Branch:    master"
1685225,2017-04-21 15:52:52 UTC,"Yes, we intend to have a method to update the configurations inside the amphora.  We ran into a problem with flask/werkzeug failing when a new configuration was adopted.  We have replaced that code with gunicorn and this issue should now be resolved.  We just need to circle back and complete the code that allows configuration updates.  Thank you for opening the bug to track it."
1685226,2019-09-20 15:39:10 UTC,Looks like the patch from Sahid was abandoned because a unit test wasn't provided.
1685226,2017-11-21 12:55:59 UTC,"Interesting thanks for that - Can you share a bit more of information about the host CPU topology and configuration for Nova, example are you using the option CONF.vcpu_pin_set? is the host configured to use hyperthreading, what is the host NUMA topology and guest requested?"
1685226,2017-11-21 12:44:18 UTC,Seeing this repeatedly in logs:
1685226,2018-03-29 15:51:42 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.openstack.org/458848"
1685273,2017-04-21 17:00:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685273,2017-04-22 11:30:51 UTC,The ubuntu-themes source replaced light-themes after precise. The light-themes source only exists in precise.
1685273,2017-10-04 11:17:27 UTC,(cleaning up the tracking list; valid bug but not RC)
1685274,2020-04-27 04:17:36 UTC,[Expired for sosreport (Ubuntu) because there has been no activity for 60 days.]
1685274,2020-02-26 19:57:20 UTC,I don't see the value to keep this bug open.
1685274,2017-12-11 09:59:57 UTC,"Hi Christian,"
1685274,2017-12-08 12:11:54 UTC,"Hi,
your changes at https://github.com/sosreport/sos/pull/1030 seem to be lost - how did this went on?
Did you open another PR - is it accepted now?"
1685274,2017-06-06 13:41:30 UTC,"Cool, I've added a PR there https://github.com/sosreport/sos/pull/1030"
1685274,2017-06-06 14:41:57 UTC,I'm reworking that PR up here.
1685274,2017-04-24 15:06:46 UTC,After assessing the initial state I want to thank you Fabio for reporting this and your help to make Ubuntu better. Given its rather low priority chances are that for quite a while nobody takes care.
1685274,2017-04-24 15:02:40 UTC,"I can confirm the issue after testing, yet since the plugin is listed as ""requires root"" the severity of not working that well without root is rather low IMHO."
1685274,2017-06-05 18:37:54 UTC,Feel free to report it upstream https://github.com/sosreport/sos or make a pull request with your suggest changes.  Thanks!
1685274,2017-04-24 17:27:57 UTC,"Thanks Christian for the suggestion, I will try to do my best to attend the next server squashing day and help out on this (and maybe other) issues."
1685290,2017-05-10 07:18:17 UTC,1. PXC behavior is same as PS. Since PXC haven't changed anything in audit-log it is inheriting the same behavior as PS.
1685290,2018-01-25 09:26:41 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3688
1685291,2017-04-21 16:00:11 UTC,This change was made by a bot.
1685298,2017-04-22 09:56:44 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_09-51-00/results-index.html"
1685298,2017-04-22 09:38:06 UTC,"        tests ran:  38, failed: 4;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/rumford__4.10.0-20.22__2017-04-22_09-07-00/results-index.html"
1685298,2017-04-22 09:27:54 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_08-49-00/results-index.html"
1685298,2017-04-22 09:24:36 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/secchi__4.10.0-20.22__2017-04-22_08-36-00/results-index.html"
1685298,2017-04-22 08:42:10 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/rumford__4.10.0-20.22__2017-04-22_07-47-00/results-index.html"
1685298,2017-04-22 08:32:52 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/hainzel__4.10.0-20.22__2017-04-22_08-07-00/results-index.html"
1685298,2017-04-22 08:24:51 UTC,"        tests ran:  19, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_07-36-00/results-index.html"
1685298,2017-04-22 08:05:20 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/gonzo__4.10.0-20.22__2017-04-22_07-32-00/results-index.html"
1685298,2017-04-22 07:42:40 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/hainzel__4.10.0-20.22__2017-04-22_07-37-00/results-index.html"
1685298,2017-04-22 07:14:12 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/hainzel__4.10.0-20.22__2017-04-22_06-34-00/results-index.html"
1685298,2017-04-22 07:12:16 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_06-54-00/results-index.html"
1685298,2017-04-22 10:11:42 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onibi__4.10.0-20.22__2017-04-22_10-09-00/results-index.html"
1685298,2017-04-22 07:05:03 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/daedalus__4.10.0-20.22__2017-04-22_06-43-00/results-index.html"
1685298,2017-04-22 06:42:29 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/gonzo__4.10.0-20.22__2017-04-22_06-37-00/results-index.html"
1685298,2017-04-22 06:32:01 UTC,"        tests ran:   6, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_06-04-00/results-index.html"
1685298,2017-04-22 06:23:25 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/daedalus__4.10.0-20.22__2017-04-22_06-19-00/results-index.html"
1685298,2017-04-22 06:13:23 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/gonzo__4.10.0-20.22__2017-04-22_05-28-00/results-index.html"
1685298,2017-04-22 05:58:55 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/rumford__4.10.0-20.22__2017-04-22_05-56-00/results-index.html"
1685298,2017-04-22 05:39:19 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/hainzel__4.10.0-20.22__2017-04-22_05-19-00/results-index.html"
1685298,2017-04-22 07:21:21 UTC,"        tests ran:  21, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/rumford__4.10.0-20.22__2017-04-22_06-25-00/results-index.html"
1685298,2017-04-22 10:14:04 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/secchi__4.10.0-20.22__2017-04-22_09-44-00/results-index.html"
1685298,2017-04-22 11:20:49 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/secchi__4.10.0-20.22__2017-04-22_10-56-00/results-index.html"
1685298,2017-04-22 10:44:20 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onibi__4.10.0-20.22__2017-04-22_10-41-00/results-index.html"
1685298,2017-04-24 15:31:35 UTC,The package has been published and the bug is being set to Fix Released
1685298,2017-04-23 03:44:29 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onza__4.10.0-20.22__2017-04-23_03-04-00/results-index.html"
1685298,2017-04-23 02:13:05 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onza__4.10.0-20.22__2017-04-23_02-06-00/results-index.html"
1685298,2017-04-23 00:18:00 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onibi__4.10.0-20.22__2017-04-22_23-26-00/results-index.html"
1685298,2017-04-22 22:16:57 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onibi__4.10.0-20.22__2017-04-22_22-11-00/results-index.html"
1685298,2017-04-22 21:43:32 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onza__4.10.0-20.22__2017-04-22_21-26-00/results-index.html"
1685298,2017-04-22 21:01:36 UTC,"        tests ran:   5, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onza__4.10.0-20.22__2017-04-22_20-24-00/results-index.html"
1685298,2017-04-22 19:59:07 UTC,"        tests ran:  38, failed: 5;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onza__4.10.0-20.22__2017-04-22_19-23-00/results-index.html"
1685298,2017-04-22 18:27:16 UTC,"        tests ran:   8, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onza__4.10.0-20.22__2017-04-22_15-52-00/results-index.html"
1685298,2017-04-22 16:34:49 UTC,"        tests ran:  38, failed: 4;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onibi__4.10.0-20.22__2017-04-22_15-52-00/results-index.html"
1685298,2017-04-22 15:27:21 UTC,"        tests ran:   8, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onza__4.10.0-20.22__2017-04-22_14-17-00/results-index.html"
1685298,2017-04-22 14:01:19 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/rumford__4.10.0-20.22__2017-04-22_13-29-00/results-index.html"
1685298,2017-04-22 05:35:57 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_04-04-00/results-index.html"
1685298,2017-04-22 13:52:43 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onibi__4.10.0-20.22__2017-04-22_12-41-00/results-index.html"
1685298,2017-04-22 13:03:59 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/rumford__4.10.0-20.22__2017-04-22_12-58-00/results-index.html"
1685298,2017-04-22 12:32:53 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/rumford__4.10.0-20.22__2017-04-22_11-49-00/results-index.html"
1685298,2017-04-22 11:45:20 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/onza__4.10.0-20.22__2017-04-22_11-42-00/results-index.html"
1685298,2017-04-22 11:23:28 UTC,"        tests ran:  19, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/rumford__4.10.0-20.22__2017-04-22_10-32-00/results-index.html"
1685298,2017-04-22 10:49:50 UTC,"        tests ran:  64, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_10-21-00/results-index.html"
1685298,2017-04-22 10:37:08 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/secchi__4.10.0-20.22__2017-04-22_10-32-00/results-index.html"
1685298,2017-04-22 05:26:31 UTC,"        tests ran:   6, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/secchi__4.10.0-20.22__2017-04-22_04-48-00/results-index.html"
1685298,2017-04-21 21:35:08 UTC,"        tests ran:  10, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_21-03-00/results-index.html"
1685298,2017-04-22 04:55:56 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/daedalus__4.10.0-20.22__2017-04-22_04-26-00/results-index.html"
1685298,2017-04-21 23:08:39 UTC,"        tests ran:  14, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_22-41-00/results-index.html"
1685298,2017-04-21 22:59:12 UTC,"        tests ran:  19, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_22-42-00/results-index.html"
1685298,2017-04-21 22:54:14 UTC,"        tests ran:  38, failed: 4;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/pepe__4.10.0-20.22__2017-04-21_22-20-00/results-index.html"
1685298,2017-04-21 22:18:04 UTC,"        tests ran:  10, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_21-45-00/results-index.html"
1685298,2017-04-21 22:17:12 UTC,"        tests ran:  19, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_21-59-00/results-index.html"
1685298,2017-04-21 21:57:49 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/pepe__4.10.0-20.22__2017-04-21_21-15-00/results-index.html"
1685298,2017-04-21 21:21:02 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_20-15-00/results-index.html"
1685298,2017-04-21 20:52:40 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/pepe__4.10.0-20.22__2017-04-21_20-09-00/results-index.html"
1685298,2017-04-21 20:40:06 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_19-33-00/results-index.html"
1685298,2017-04-21 19:55:06 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/fozzie__4.10.0-20.22__2017-04-21_18-59-00/results-index.html"
1685298,2017-04-21 19:55:02 UTC,"        tests ran:  20, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_19-03-00/results-index.html"
1685298,2017-04-21 18:39:18 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_18-36-00/results-index.html"
1685298,2017-04-21 18:36:49 UTC,"        tests ran:  19, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/fozzie__4.10.0-20.22__2017-04-21_17-46-00/results-index.html"
1685298,2017-04-21 17:57:55 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_17-54-00/results-index.html"
1685298,2017-04-21 17:36:02 UTC,"        tests ran:  38, failed: 3;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/amaura__4.10.0-20.22__2017-04-21_17-11-00/results-index.html"
1685298,2017-04-21 17:26:52 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/fozzie__4.10.0-20.22__2017-04-21_17-22-00/results-index.html"
1685298,2017-04-21 16:59:27 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/fozzie__4.10.0-20.22__2017-04-21_16-56-00/results-index.html"
1685298,2017-04-21 16:56:53 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/amaura__4.10.0-20.22__2017-04-21_16-54-00/results-index.html"
1685298,2017-04-22 05:03:27 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/gonzo__4.10.0-20.22__2017-04-22_04-10-00/results-index.html"
1685298,2017-04-21 23:48:01 UTC,"        tests ran:   5, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/pepe__4.10.0-20.22__2017-04-21_23-17-00/results-index.html"
1685298,2017-04-21 23:51:02 UTC,"        tests ran:  14, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_23-24-00/results-index.html"
1685298,2017-04-21 19:09:34 UTC,"        tests ran:  20, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_18-22-00/results-index.html"
1685298,2017-04-22 00:08:39 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/hainzel__4.10.0-20.22__2017-04-22_00-06-00/results-index.html"
1685298,2017-04-21 23:58:58 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/daedalus__4.10.0-20.22__2017-04-21_23-56-00/results-index.html"
1685298,2017-04-22 04:54:13 UTC,"        tests ran:   6, failed: 1;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/hainzel__4.10.0-20.22__2017-04-22_04-04-00/results-index.html"
1685298,2017-04-22 04:27:19 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/secchi__4.10.0-20.22__2017-04-22_02-31-00/results-index.html"
1685298,2017-04-22 04:02:47 UTC,"        tests ran:   6, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/daedalus__4.10.0-20.22__2017-04-22_03-04-00/results-index.html"
1685298,2017-04-22 03:43:11 UTC,"        tests ran:   8, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/gonzo__4.10.0-20.22__2017-04-22_02-42-00/results-index.html"
1685298,2017-04-22 03:36:00 UTC,"        tests ran:  21, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_02-42-00/results-index.html"
1685298,2017-04-22 03:35:30 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/hainzel__4.10.0-20.22__2017-04-22_01-48-00/results-index.html"
1685298,2017-04-22 02:57:38 UTC,"        tests ran:  64, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-22_02-09-00/results-index.html"
1685298,2017-04-22 02:39:46 UTC,"        tests ran:  10, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/daedalus__4.10.0-20.22__2017-04-22_01-06-00/results-index.html"
1685298,2017-04-22 02:14:04 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/archytas__4.10.0-20.22__2017-04-22_02-11-00/results-index.html"
1685298,2017-04-22 02:14:30 UTC,"        tests ran:  21, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/gonzo__4.10.0-20.22__2017-04-22_01-12-00/results-index.html"
1685298,2017-04-22 02:08:28 UTC,"        tests ran:  64, failed: 2;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-22_01-24-00/results-index.html"
1685298,2017-04-22 01:42:38 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-22_01-36-00/results-index.html"
1685298,2017-04-22 01:22:01 UTC,"        tests ran:  21, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/hainzel__4.10.0-20.22__2017-04-22_00-33-00/results-index.html"
1685298,2017-04-22 01:09:18 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-34-mcdivittB0-kernel__4.10.0-20.22__2017-04-22_00-15-00/results-index.html"
1685298,2017-04-22 00:58:10 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/secchi__4.10.0-20.22__2017-04-22_00-55-00/results-index.html"
1685298,2017-04-22 00:57:41 UTC,"        tests ran:   2, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-22_00-52-00/results-index.html"
1685298,2017-04-22 00:46:39 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/gonzo__4.10.0-20.22__2017-04-22_00-44-00/results-index.html"
1685298,2017-04-22 00:26:23 UTC,"        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/ms10-35-mcdivittB0-kernel__4.10.0-20.22__2017-04-21_23-32-00/results-index.html"
1685298,2017-04-22 00:18:54 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/gonzo__4.10.0-20.22__2017-04-22_00-16-00/results-index.html"
1685298,2017-04-22 02:09:07 UTC,"        tests ran:  21, failed: 0;
  http://kernel.ubuntu.com/testing/4.10.0-20.22-generic/secchi__4.10.0-20.22__2017-04-22_01-19-00/results-index.html"
1685305,2019-03-18 10:43:33 UTC,AFAICS this is fixed in 2017.7.ubuntu1:
1685305,2019-07-07 13:45:51 UTC,"right, fixed in 2017.1, if anybody wants to do a SRU for trusty and xenial, they are welcome to."
1685332,2017-05-24 11:35:44 UTC,"> Having spoken to Christian...
"
1685332,2017-05-24 11:34:03 UTC,"Having spoken to Christian, marking this Triaged/Wishlist."
1685332,2017-04-23 13:26:36 UTC,"On 21 April 2017 at 22:47, Christian Franke <email address hidden> wrote:

> Add '-d nvme' directive to 'DEVICESCAN' line in /etc/smartd.conf. Note
> that this will exclude other devices unless e.g. '-d scsi -d ata -d sat'
> is added also.
>
> Background: The NVMe support in smartmontools is still EXPERIMENTAL. To
> avoid any serious problems after smartmontools package upgrade, I
> decided to exclude NVMe devices from default smartd DEVICESCAN (and
> 'smartctl --scan') result. This will be changed in some later release.
>
> Package maintainers could override this decision by using --with-nvme-
> devicescan configure option.
>
"
1685332,2017-04-25 15:58:06 UTC,"> ... any other help pointer (man page, comment in config, ...) that would help?
"
1685332,2017-04-25 07:31:00 UTC,"Thanks Christian to outline the backgrounds.
For now I'd agree that relying on an experimental feature as support would not be the preferred way.
It is great to have this bug also as a documentation for others wondering about the same."
1685332,2017-04-21 21:47:29 UTC,Add '-d nvme' directive to 'DEVICESCAN' line in /etc/smartd.conf. Note that this will exclude other devices unless e.g. '-d scsi -d ata -d sat' is added also.
1685332,2017-05-08 13:25:18 UTC,"I'm on 17.10
my mvne is THNSN5512GPUK NVMe TOSHIBA 512GB, FW:5KDA4101 on a DELL Precision 5510."
1685333,2017-10-13 13:21:01 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/511842"
1685333,2017-10-25 14:48:48 UTC,Based on logstash there was no new appearance of this problem since the related patch https://review.openstack.org/507239 was merged so I think the related patch actually fixed the problem. So this can be closed.
1685333,2017-10-13 00:50:05 UTC,"Reviewed:  https://review.openstack.org/507239
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0534872abb78738993a35d24a6640c82b711deee
Submitter: Jenkins
Branch:    master"
1685333,2017-12-13 04:31:14 UTC,"Reviewed:  https://review.openstack.org/511842
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d873550d3c357adb6f3544adbc43e8ab9b94cfbd
Submitter: Zuul
Branch:    stable/pike"
1685333,2017-08-02 14:19:11 UTC,The 'python3.5 -X faulthandler' could be a way to catch this but that also only supports dumping up to the last 100 stack frames.
1685333,2017-07-31 07:59:28 UTC,s/to to truncate/not to truncate/
1685333,2017-07-31 07:55:55 UTC,there was couple of new occurrences all in TestRPC. I still wasn't able to reproduce the problem locally. Can we somehow tell python to to truncate the stack trace in this case to see where the infinite recursion starts?
1685333,2017-07-27 11:04:33 UTC,"We have 7 occurrences so far with the stack overflow signature:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Fatal%20Python%20error%3A%20Cannot%20recover%20from%20stack%20overflow.%5C%22"
1685333,2017-09-25 19:00:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/507239"
1685333,2017-07-27 10:57:21 UTC,I saw a very similar failure https://bugs.launchpad.net/nova/+bug/1706563 but there a different test gets stuck:
1685340,2017-11-15 01:07:05 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1685340,2017-09-16 15:40:43 UTC,"Reviewed:  https://review.openstack.org/480744
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b296f1e2e6590262a6702fb49d175f761cb901e2
Submitter: Jenkins
Branch:    stable/ocata"
1685340,2017-07-05 21:27:53 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/480744"
1685340,2017-05-03 14:25:47 UTC,"Reviewed:  https://review.openstack.org/458958
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=746e48efa32fd599817197ffd7ad434a35f96165
Submitter: Jenkins
Branch:    master"
1685340,2017-06-08 21:52:50 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1685340,2017-04-21 20:00:37 UTC,The actual failure in this case happened on the source host:
1685340,2017-04-21 20:05:02 UTC,"(3:02:48 PM) kashyap: mriedem: It means (according to the QEMU commit that introduced it):
(3:03:12 PM) kashyap: Something tried to write to the image file on the source, _while_ it is being migrated"
1685340,2017-04-21 20:06:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/458958"
1685342,2017-04-26 13:15:02 UTC,"Hi Asquirrel,
i think I am running in to the same problem. Did you find any solution? I am running glance 13.0.0 and cinder 9.1.2 on Newton."
1685342,2017-08-10 17:59:03 UTC,Same happening in ubuntu/OCATA packages.
1685342,2017-05-03 16:44:38 UTC,"No joy, problem persists. That said, api=True is actually the default setting (and I had not set them either way) so...'it was already on'."
1685342,2017-05-03 16:00:08 UTC,"Hi, I got it to start a image. I had to enable v1 for glance again."
1685342,2017-08-11 16:37:25 UTC,"JFTR, found the final solution, and think is a configuration issue."
1685342,2017-04-27 13:01:59 UTC,cinder-api.log when pushing 'Launch Instance':
1685342,2017-04-27 12:28:00 UTC,"Hi, this is what I see in the cinder-api.logs:"
1685342,2017-04-27 01:07:28 UTC,Could you show your cinder-api's log? I guess there is something wrong during Cinder and Glance connection. Perhaps Cinder cant' get the image info from Glance.
1685342,2017-04-26 13:48:45 UTC,"No. I'd have to dig through the presumably python, modules which drive Cinder to find where this request is getting generated and I'm so bad at Python I would probably find it around the time Openstack Zebra came out."
1685342,2017-04-27 13:02:48 UTC,"Er, crap. I can't edit my previous comment. Controller = 192.168.3.70"
1685342,2017-08-10 18:26:15 UTC,"regarding comment #8 it's not absolutely right, it didn't worked in my case until i explicitly activated v1 on glance config"
1685348,2017-04-30 20:48:13 UTC,This bug was fixed in the package gnome-shell-extensions - 3.24.1-0ubuntu1
1685354,2017-04-21 21:16:34 UTC,"OP, can you confirm that pressing enter instead of focus out will save the name? Looks like a regression slipped in"
1685354,2017-04-21 22:36:42 UTC,"yes, pressing enter renames the file or folder, just focus out not, thanks a lot for the quick help, anyway thanks for your engagement with elementary os, great work!!"
1685354,2017-04-22 18:05:41 UTC,"This is due to an update to stop renaming ending when e.g. keyboard layout changes or the ""locate cursor by pressing Ctrl"" accessibility option is enabled.  Both of these cause a temporary focus out.  It may be possible to fix all issues by having a timout on the focus out and end renaming if it is not temporary."
1685356,2017-04-26 14:13:20 UTC,"Should a sticky value, applied at page load time, fire the on-change?"
1685356,2017-04-26 15:22:19 UTC,Noting some discussion on IRC today:
1685356,2017-04-26 15:59:33 UTC,And let's not forget the code from bug #1511742 which replaces the egOrgSelector uib-dropdown with a uib-typeahead text input.  Any chance that's the magic sauce this needs?
1685356,2017-04-26 16:22:26 UTC,"It may well help, as it looks like uib-typeahead is ngForm-aware."
1685362,2017-04-21 21:22:00 UTC,The full build log is available here: https://private-fileshare.canonical.com/~fginther/maas/lp-1685362/buildlog_ubuntu_xenial_amd64_cpc_BUILDING.txt.
1685371,2018-10-10 21:45:40 UTC,"FYI, I find that this change produces *most* of the expected behavior:
* https://github.com/Osndok/zim-desktop-wiki/commit/4f7233ace8666bd29c118289bd6c0c2258453339"
1685371,2017-05-31 12:42:52 UTC,Need to check with e.g. gedit what is expected behavior from other editors
1685376,2018-07-07 10:41:03 UTC,"There is an old work-around that still works (at least for me) : adding noautogroup after quiet splash in /etc/default/grub (GRUB_CMDLINE_LINUX_DEFAULT line).
Xubuntu 18.04 64 bits"
1685376,2018-04-02 14:12:25 UTC,Got the indexing (xapi-cache) working better  lp:#1760608
1685376,2018-03-10 13:33:20 UTC,"18.04 LTS with all updates, bug exists."
1685376,2018-02-13 12:57:21 UTC,And now in 16.04 and 17.10 it is slow.
1685376,2018-02-06 13:35:42 UTC,"What a pity. apt-xapian-index worked perfectly well in Trusty. It brought a very fast/easy way to dig dependencies, locked packages."
1685376,2018-01-06 17:37:06 UTC,It seems that bug 1612948 about axi-cache is related to this bug report. Please take care to it.
1685376,2018-01-06 16:30:02 UTC,"Hope to get the newer version for Bionic at least:
http://metadata.ftp-master.debian.org/changelogs/main/a/apt-xapian-index/apt-xapian-index_0.49_changelog"
1685376,2018-01-06 15:58:08 UTC,Just made clean installation of 16.04 LTS. Bug exists.
1685376,2018-02-06 13:32:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685376,2017-09-29 16:07:24 UTC,"Well the quick search never worked great, xapian was dropped from Ubuntu
image some time back  & synaptic itself is currently ill maintained. So
likely nothing will happen to change this."
1685376,2017-10-21 17:01:35 UTC,Bug exists in Ubuntu 17.10 final.
1685376,2017-04-21 22:06:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685376,2017-08-10 17:49:21 UTC,"I suspect that ""apt-daily-upgrade.service"" and ""apt-daily.service"" (both call /usr/lib/apt/apt.systemd.daily) cause Synaptic to rebuild apt-xapian-index. I disabled them with
sudo systemctl disable apt-daily.timer
sudo systemctl disable apt-daily-upgrade.timer"
1685376,2017-08-10 17:51:06 UTC,"I'm using SSD. May my mount options cause problems?
I have ""errors=remount-ro,discard,noatime,nodiratime"" for rootfs(""/"")."
1685376,2017-08-10 18:49:49 UTC,May bug 1612948 be related to this issue?
1685376,2018-01-06 16:16:27 UTC,Have the feeling that apt-xapian-index is the package to blame (instead of synaptic itself)
1685376,2017-08-26 11:07:28 UTC,"What is interesting - during reinstallation of apt-xapian-index 0.47 from xenial here is interesting message:
""The index /var/lib/apt-xapian-index/index is not CJK-compatible, rebuilding it"""
1685376,2017-08-26 15:52:12 UTC,"apt-xapian-index isn't default installed anymore, why do you have it?"
1685376,2017-09-29 13:08:11 UTC,Ubuntu 17.10 is affected too. Synaptic rebuilds its index very often.
1685376,2017-09-29 13:59:49 UTC,@mc3man
1685376,2017-08-25 06:14:39 UTC,I don't think stopping systemd timers helped at all. But did installing python2 version from debian strech help?
1685377,2017-04-24 08:51:20 UTC,"Yes, the version discovery had not been implemented in osc yet[1], but we start trying to support it[2], please add you advise in that patch, any feedback is valuable for us, thank you."
1685383,2017-04-27 15:53:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685383,2017-10-12 07:38:27 UTC,Happened again on this update Oct 12 2017 3:37 AM
1685383,2017-10-12 07:42:23 UTC,"Took a while before the status pop up changed, but has asked for a re-start to finish.   This apparently has not been fatal?"
1685383,2017-10-12 08:21:43 UTC,"re-start successful.
Scanned logs, saw no errors related to ""Kernel""
Other errors mostly to do with network identification, finding sockets and such which are out of my field of expertise."
1685383,2017-10-28 10:58:48 UTC,Apparently the 5.1 version of virtualbox was the problem and needed to be removed and replaced by 5.2.
1685383,2017-10-28 11:06:55 UTC,"Comment #9 supersedes comments #7 and #8 which should be ignored.
Replacing virtualbox 5.1 with 5.2 and removing the debian repository seem to have been effective at resolving the problem."
1685385,2020-02-14 09:48:33 UTC,Fixed on all still maintained branches.
1685385,2017-05-07 15:54:32 UTC,This bug was fixed in the package gcc-6 - 6.3.0-16ubuntu6
1685385,2017-04-27 15:50:08 UTC,This bug has been fixed on the GCC mainline at FSF.  It is PR 80533 on the FSF Bugzilla.
1685385,2017-04-26 19:07:20 UTC,"Created attachment 41274
Test case"
1685385,2017-04-27 07:55:09 UTC,Mine.
1685385,2017-04-27 12:35:16 UTC,"Author: rguenth
Date: Thu Apr 27 12:34:45 2017
New Revision: 247327"
1685385,2017-04-27 12:59:11 UTC,Fixed on trunk sofar.
1685393,2017-05-04 04:23:36 UTC,Fix committed today (05/03)
1685397,2019-08-31 13:26:32 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates.
1685397,2019-10-31 04:17:37 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1685399,2017-04-26 20:52:54 UTC,Why does MAAS needs to deal with this? What's your environment looking like?
1685399,2017-04-26 22:17:37 UTC,"I'm doing (2). The MAAS images contain cached apt lists from when the images were built in /var/cache/apt. If the mirror is behind, the apt-get update and/or upgrade will fail because the image expects newer apt lists/hashes than are present on the mirror, and doesn't overwrite the newer lists with the older lists."
1685399,2017-05-04 18:38:58 UTC,See attached screenshot when trying to commission a machine in MAAS using an out-of-date mirror.
1685399,2017-05-05 14:23:00 UTC,I discussed this with mvo; here's the debug output he requested from a run of 'apt-get update -o debug::acquire::http=true':
1685399,2017-05-05 15:07:42 UTC,"I've talked about this with Robie Basak before.
For cloud-images building, it seems like it makes sense to clear out apt cache for updates and security.  In the best case scenario, those files are up to date and apt wont re-download.  That lasts only until the next SRU or security update, so it is not a long term win."
1685399,2018-08-22 10:56:19 UTC,"Nothing to see here from the apt side, so I'm getting rid of the tasks."
1685436,2019-06-17 14:39:05 UTC,Proposed solution: https://zpl.io/aNDzMyD
1685439,2019-07-27 10:41:50 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu since that time.
1685439,2019-09-26 04:17:34 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1685439,2017-05-15 05:21:05 UTC,The issue is still present with firefox:amd64 53.0.2+build1-0ubuntu0.14.04.2
1685439,2017-05-12 10:36:08 UTC,Confirm: It affects Ubuntu 14.05 with GNOME..
1685439,2017-05-09 08:00:21 UTC,Also on Linux Mint 17.1 Rebecca - Cinnamon 2.4.8
1685439,2017-04-23 09:12:56 UTC,Also affects Ubuntu GNOME 14.04.5.
1685439,2017-04-23 09:11:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685439,2017-04-22 09:28:57 UTC,Attachment added
1685441,2017-04-24 15:58:58 UTC,Perhaps the most efficient way to fix the PyQt5 issue is to finish the port of OpenTeacher to Python 3.
1685441,2017-04-29 21:33:31 UTC,OT is now ported to Python 3. It **seems** like there are no major obstacles anymore to getting a working Windows build.
1685441,2017-06-26 17:16:04 UTC,Status update:
1685441,2017-06-26 19:58:09 UTC,Mostly works now.
1685442,2018-05-23 14:54:08 UTC,*** Bug 106422 has been marked as a duplicate of this bug. ***
1685442,2018-04-28 12:55:47 UTC,Just adding output from my machine:
1685442,2018-04-06 15:06:50 UTC,"The immediate bug is that the frame counter goes AWOL as soon as the TV encoder gets enabled on 965gm. It also has other issues such as the scanline counter speeding up during the the vertical blanking period and stopping entirely for the duration of the bottom border, which means the timestamp based frame counter emulation of gen2 wouldn't work reliably either."
1685442,2018-04-06 14:49:00 UTC,Same issue with GM965/GL960 on kernel 4.13.0-38:
1685442,2018-04-05 08:52:28 UTC,*** Bug 103812 has been marked as a duplicate of this bug. ***
1685442,2018-04-04 08:35:55 UTC,*** Bug 105878 has been marked as a duplicate of this bug. ***
1685442,2018-03-29 07:11:10 UTC,"First of all. Sorry about spam.
This is mass update for our bugs."
1685442,2018-02-12 05:58:38 UTC,"Please find the first -rc kernel between  v4.5-rc* and v4.8-rc* in [1], regression happens in one of the release."
1685442,2018-03-21 20:44:14 UTC,"Strange observation - to save my eyes from the strain of looking at the old laptop's screen, I hooked up a monitor over VGA - and the stalls stopped (on both the tested 16.04 and on 18.04!! The message is still there in dmesg, so this had the positive effect of cutting down the time to find ""first bad kernel"" drastically."
1685442,2018-03-21 12:43:15 UTC,"Tested yesterday's bionic daily server build, issue is still present on my FSC Esprimo Mobile U9200 (Intel GM965). Hopefully, I'll find time to track down which -rc release introduced the bug."
1685442,2018-06-03 07:13:35 UTC,For bug 106422 (marked as duplicate as this one) I provided the i915.vbt as requested. I hope doing a sudo cp to /tmp worked ok.
1685442,2018-02-09 13:41:13 UTC,Confirmed on Mackbook 2008 both the issue (flip_done error and very slow boot) and the work-around (video=SVIDEO-1:d)
1685442,2018-01-28 04:00:13 UTC,Thanks Remon! Got me up and running!
1685442,2018-01-07 15:46:54 UTC,I have the same problem on Ubuntu 16.04 in kernel 4.13.0-21.
1685442,2017-11-03 22:01:37 UTC,"Decreasing priority since there are workarounds, patches and is an old HW for this issue."
1685442,2018-03-22 09:27:15 UTC,Related: https://bugs.freedesktop.org/show_bug.cgi?id=93782
1685442,2018-06-04 14:25:53 UTC,"Dear all, as recommended by Ubuntu kernel team, after I posted automated apport messages here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774845, I tested:"
1685442,2019-05-31 17:53:44 UTC,*** Bug 100907 has been marked as a duplicate of this bug. ***
1685442,2018-09-20 17:34:54 UTC,Installed Linux Mint 19 32-bit xfce on HP 2710p.
1685442,2017-10-05 08:01:39 UTC,OS Fedora 26
1685442,2019-02-25 21:12:18 UTC,*** Bug 109776 has been marked as a duplicate of this bug. ***
1685442,2019-01-25 17:31:21 UTC,Fix merged.
1685442,2018-12-18 10:44:46 UTC,Affects also Lenovo Thinkpad R61 with Ubuntu 16.04.5 LTS.
1685442,2018-12-13 22:11:39 UTC,"Same bug with Linux Mint MATE, kernel 4.15.0-42, GPU Intel Mobile GM965/960, module i915.
Adding ""video=SVIDEO-1:d"" works."
1685442,2018-11-23 01:09:11 UTC,"(In reply to Ville Syrjala from comment #78)

> Fixes posted:
> https://patchwork.freedesktop.org/series/52378/
"
1685442,2018-11-22 12:59:02 UTC,*** Bug 108747 has been marked as a duplicate of this bug. ***
1685442,2018-11-20 07:00:43 UTC,"(In reply to Ville Syrjala from comment #78)

> Fixes posted:
> https://patchwork.freedesktop.org/series/52378/
"
1685442,2018-11-13 20:31:36 UTC,"(In reply to Ville Syrjala from comment #78)

> Fixes posted:
> https://patchwork.freedesktop.org/series/52378/
"
1685442,2018-11-13 14:33:25 UTC,"My vintage MacBook4,1 is obviously also affected by this:"
1685442,2018-11-13 14:30:16 UTC,"Fixes posted:
https://patchwork.freedesktop.org/series/52378/"
1685442,2018-10-28 18:00:57 UTC,"Thanks @Ryan for the post. I'm not sure in this case that a bisection would be the most effective cure. There must be many many legacy Dell and other machines that are affected but we never know because people give up on the install. I think the suggestion (see somewhere above) of defaulting to having the workaround ""Video=SVIDEO-1:d"" enabled by default would be much more useful. The probable minority of users who do need to use SVIDEO could be dealt with through release note information and pointed to a legacy driver."
1685442,2018-10-28 16:43:13 UTC,"This should be bisectable, but I don't think anyone has done it yet..."
1685442,2018-10-28 09:00:45 UTC,On Dell Inspiron 1525 auto upgraded from xubuntu 16.04 LTS 64bit to 18.04 LTS. This bug appeared.
1685442,2018-10-18 19:28:51 UTC,"Created attachment 142084
dmesg from old MacBook running lubuntu 18.04"
1685442,2018-08-16 07:10:20 UTC,"(In reply to Zakhar from comment #74)

> Dear all, as recommended by Ubuntu kernel team, after I posted automated
> apport messages here
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774845, I tested:
>
> - last ubuntu drm-tip (as of June 3rd):
> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
> - suggested patch on comment #12 on this thread (on 4.17 rc3+ kernel I
> already had the source)
>
> Both tests were unsuccessful to fix the bug (unlike the workaround that
> makes the time-out disappear).
"
1685442,2017-10-03 07:32:25 UTC,"Hi, unfortunately this problem is still present on current drm-tip (894ff8f6f64647989f77705813b6c69fdb2e21a5, 4.14.0-rc2+).
The video=SVIDEO-1:d workaround works, though.
I spare you the dmesg output, intel_tv_detect and intel_get_load_detect_pipe are still in the trace."
1685442,2018-11-13 14:29:38 UTC,*** Bug 108728 has been marked as a duplicate of this bug. ***
1685442,2017-09-12 15:21:04 UTC,"(In reply to Axel Kittenberger from comment #59)

>
> """"""""""""""""""""""""""""""""
> [   96.023467] fuse init (API version 7.26)
> [   98.449856] [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed:
> pipe A stuck
> [   98.504650] pipe A vblank wait timed out
> [   98.504692] ------------[ cut here ]------------
> [   98.504746] WARNING: CPU: 1 PID: 1522 at
> drivers/gpu/drm/i915/intel_display.c:12844
> intel_atomic_commit_tail+0xe46/0xe70 [i915]
> ...


Hello Axel, this seems to be a different problem that the one reported in this bug. Could you please file a new case for this problem, including HW and SW information, and dmesg log with debug parameter. Thank you."
1685442,2017-07-19 07:44:40 UTC,apport information
1685442,2017-07-19 07:44:38 UTC,apport information
1685442,2017-07-19 07:44:37 UTC,apport information
1685442,2017-07-19 07:44:36 UTC,apport information
1685442,2017-04-22 10:26:28 UTC,System info and dmesg text before error message:
1685442,2017-07-19 07:44:35 UTC,apport information
1685442,2017-07-19 07:44:33 UTC,apport information
1685442,2017-07-19 07:44:31 UTC,apport information
1685442,2017-07-19 07:44:30 UTC,apport information
1685442,2017-07-19 07:44:27 UTC,apport information
1685442,2017-07-19 01:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1685442,2017-07-06 13:36:12 UTC,"Maarten - were April updates related to this intended to fix this problem?Folks, do you still see the problem on your systems with the latest kernels (preferable from drm-tip)? If problem still persist please change the status as REOPENED, otherwise one can mark this as resolved."
1685442,2017-05-10 09:08:49 UTC,"Even if the device doesn't seem to have a physical S-VIDEO connector, it possibly can be made available by using a docking station. This is the case for the Dell D630."
1685442,2017-05-10 06:23:56 UTC,"(In reply to andram from comment #40)

> FWIW,  for me I can get around this problem by disabling the SVIDEO-1
> connector. The laptop in question does not even have a physical svideo
> connector, so no functionality is lost for me.
>
> I do this either by my patch above, or alternatively by adding
>
> video=SVIDEO-1:d
>
> to the kernel command line.
"
1685442,2017-05-09 17:39:59 UTC,"Adding tag into ""Whiteboard"" field - ReadyForDev
The bug still active
*Status is correct
*Platform is included
*Feature is included
*Priority and Severity correctly set
*Logs included"
1685442,2017-07-19 07:44:41 UTC,apport information
1685442,2017-07-19 07:44:42 UTC,apport information
1685442,2017-07-19 07:44:28 UTC,apport information
1685442,2017-07-19 07:45:29 UTC,apport information
1685442,2017-07-19 07:44:44 UTC,apport information
1685442,2017-08-24 13:37:31 UTC,"If below is the same error, then yes. I just tested with linux-4.13-rc6."
1685442,2017-08-01 04:56:03 UTC,"I still see the problem with 4.10, 4.11 and 4.12 and I also tried kernels from drm-tip. Can anyone else confirm?"
1685442,2017-07-30 23:28:49 UTC,"This bug affected me with Ubuntu 17.04 on a Dell D630 laptop as well. I applied the workaround that was suggested on the mentioned Arch forum thread (disabling S-video). Add ""video=SVIDEO-1:d"" to the kernel boot options in /etc/default/grub:"
1685442,2017-07-19 07:54:59 UTC,"I installed Ubuntu Mate 16.04.2 (with no updates) onto hard disk. After reboot, I could log in, but the computer hung.  Afte a second reboot, I logged in and the computer seemd to work okay.  I entered the command ""apport-collect 1685442"" as requested. Then I entered the command a second time, since I wasn't sure it worked (I had gotten warning messages).  Sorry if this made things comfusing."
1685442,2017-07-19 07:45:49 UTC,apport information
1685442,2017-07-19 07:45:47 UTC,apport information
1685442,2017-07-19 07:45:45 UTC,apport information
1685442,2017-09-15 10:52:03 UTC,"My problem seems to be fixed with 4.13.1 i just tried.
4.13.0-rc6 was the last I tried before still having had my issue.
Sorry for noise on this bug."
1685442,2017-07-19 07:45:42 UTC,apport information
1685442,2017-07-19 07:45:44 UTC,apport information
1685442,2017-07-19 07:45:41 UTC,apport information
1685442,2017-07-19 07:45:39 UTC,apport information
1685442,2017-07-19 07:45:37 UTC,apport information
1685442,2017-07-19 07:45:36 UTC,apport information
1685442,2017-07-19 07:45:35 UTC,apport information
1685442,2017-07-19 07:45:33 UTC,apport information
1685442,2017-07-19 07:45:32 UTC,apport information
1685445,2019-02-09 09:39:42 UTC,"It doesn't make sense to maintain a list of 'known but ignored devices',
those should just be added as known devices."
1685445,2019-02-05 15:53:24 UTC,At CPT Jan 2019 we discussed UI to:
1685445,2017-06-30 01:17:30 UTC,"I think a ""ping once per day, expire after one week"" approach sounds very reasonable. The required scope might be a little much for a bug fix, but we can take a look."
1685445,2019-03-06 10:52:22 UTC,I'm closing this bug as we added:
1685445,2017-04-23 08:56:43 UTC,"Ah, the observed address data as input to address allocation is cool."
1685445,2017-06-27 19:19:24 UTC,Initially we could keep these matters orthogonal.
1685445,2017-04-24 17:51:19 UTC,"Yes, and your comment about hard-probing reminds me of a subtle issue with aging things out: we don't do any hard-probing by default."
1685445,2017-04-22 18:54:21 UTC,"See also: bug #1680632, which is very similar."
1685457,2017-05-12 14:16:08 UTC,Related to an existing bug for improving the DHCP information presentation:
1685463,2017-08-16 19:31:20 UTC,"Hmm, I don't have this bug now, may be Fix Released by incremental updates?"
1685463,2017-08-16 19:32:34 UTC,Alternatively it might be because I have a faster laptop now (ThinkPad T430 instead of X201)
1685463,2017-08-17 14:24:04 UTC,I’m using the libreoffice 5.3.4.2 snap and I’m still seeing the issue as initially reported. That’s on a X230 running Artful.
1685484,2017-05-03 12:36:30 UTC,"I tried reproducing the issue, but without NM it worked.
Seems to be LP: #293139, but I dig further and test in a VM with NM."
1685484,2017-05-03 19:51:46 UTC,"Submitted patch in the bug for Debian, waiting for comments."
1685484,2017-05-04 10:08:11 UTC,"I think new NM dispatcher script for timesyncd should be executed not only on up/down actions, but on dhcp4/dhcp6 change to (and connectivity change to maybe - see https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/nm-dispatcher.h#n27). It should be possible to update NTP servers on each DHCP options change."
1685484,2017-07-27 15:57:11 UTC,"in Artful we are migrating away from ifupdown to netplan. Meaning we will not be using dhcp hooks by default, and only use networkd/network-manager. I believe networkd has native support to push NTP servers to timesyncd, and I think networkmanager should natively push ntp servers direct to timesync too - without using the dhcp hooks. Adding a task for networkmanager to check this."
1685490,2017-04-26 12:13:58 UTC,"Thanks Blake, that worked for the boot-server option but not for
sip-servers."
1685490,2017-04-25 14:09:44 UTC,ISC dhcpd does not come with those two options defined. This allows more flexibility as a user can call those options what every name they like. The option just needs to be defined with its RFC code and its parameters.
1685490,2017-04-23 13:35:38 UTC,"... and just to let you know, my phones don't work at home until this works, so Claire would really appreciate a fix :)"
1685503,2017-05-16 13:15:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685510,2017-04-22 14:25:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459059"
1685514,2017-04-28 21:41:24 UTC,This bug was fixed in the package gnome-documents - 3.24.1-0ubuntu1
1685515,2017-04-22 16:19:33 UTC,This bug was fixed in the package gnome-session - 3.24.1-0ubuntu2
1685516,2019-04-08 13:11:40 UTC,"Fixed in revision a1c162e59fa8f4c206bcaf22bece58404e0614db
https://git.launchpad.net/kicad/patch/?id=a1c162e59fa8f4c206bcaf22bece58404e0614db"
1685516,2019-01-08 18:30:17 UTC,I think this but is related to my wishlist for adding a check for pcb is up to date with schematic: https://bugs.launchpad.net/kicad/+bug/1809293
1685516,2018-01-24 19:06:09 UTC,See also https://bugs.launchpad.net/kicad/+bug/1522474 .
1685516,2018-01-23 14:30:59 UTC,"@Jeff, thanks for thinking long term.  If we are going to head down this
path, we really need to rethink the DRC design.  I have a few ideas
about this that I can share with you after the v5 stable release."
1685516,2018-01-23 11:41:13 UTC,"I might look into this for 6.0, but I'm lowering the priority for now as it doesn't look like something that would fit into 5.0."
1685516,2018-01-23 08:09:07 UTC,"I guess the hardest step here is getting a netlist before one starts board verification. It is easy if you had imported a netlist during the layout session, as it might be stashed somewhere, but otherwise you need to bother the user to give you one. The exception is when you run KiCad in the project mode, as then you can request it directly from eeschema."
1685516,2018-01-23 07:22:41 UTC,"There is already this option:
Netlist->Test Footprints"
1685516,2018-01-23 11:36:12 UTC,"Test Footprints looks for the netlist with the board name in the board's directory (ie: were it would be if you used a project), and if it doesn’t find it there simply reports an error.  Seems reasonable."
1685516,2018-01-23 00:08:22 UTC,"DRC is a bit of a hybrid.  The main function is to test if the board meets fabrication and electrical tolerances.  But it also has the List Unconnected feature, which wanders more into Netlist land."
1685516,2018-01-22 23:05:43 UTC,"I am not sure about the internals here, but there are two things in place here. The kicad_pcb file and the netlist file. I don't think the DRC currently reads the netlist, but I may be wrong here."
1685516,2018-01-22 22:30:38 UTC,"I think the “accidental” term in the bug report is a red herring.  Shouldn’t DRC report mismatches between the board and the netlist, no matter how they came about?"
1685516,2018-01-22 21:41:44 UTC,"This does not sound like a bug, but rather a wish to make the DRC able to check if the netlist and the board are not in sync."
1685516,2018-01-22 21:26:43 UTC,"Exactly how are we to determine if the footprint was intentionally
deleted or accidentally deleted?"
1685516,2018-01-22 21:04:53 UTC,Reproduces easily for me.
1685516,2017-05-01 20:16:28 UTC,Can you reproduce this issue in the nightlies?
1685516,2017-04-24 16:15:42 UTC,It also ignores duplicate and additional parts.
1685516,2018-01-23 00:28:22 UTC,"I've never used an EDA tool that does this but I haven't used them all.
I suppose we could be the first as long as I can disable it.  I would
reject any patch that didn't make this warning optional."
1685517,2017-04-29 07:53:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685520,2019-02-05 20:27:33 UTC,moved from https://bugs.launchpad.net/yade/+bug/1685520 to https://gitlab.com/yade-dev/trunk/issues/35
1685522,2019-09-08 21:27:27 UTC,Hey apw and adconrad -- a long time ago (2.5 years) we decided to keep WireGuard from migrating into Ubuntu. There's been tons of progress since then. It's now in the progress of migrating down into Debian testing and stable. I think it's time we let it migrate into Ubuntu too. Is there anything that needs to be done on your part of the build infra to unblock this?
1685522,2017-05-02 09:14:00 UTC,"The verification of the Stable Release Update for wireguard has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1685522,2017-05-02 09:13:57 UTC,This bug was fixed in the package wireguard - 0.0.20170214-1ubuntu0.17.04.1
1685522,2017-05-02 09:12:23 UTC,they are usually processed after 7-10 days from the verification-done tag.
1685522,2017-05-01 19:59:18 UTC,Any update on this SRU?
1685522,2017-04-25 12:23:51 UTC,I have performed testing with four separate VMs:
1685522,2017-04-25 05:18:01 UTC,"Using the .deb builds provided on https://launchpad.net/ubuntu/+source/wireguard/0.0.20170214-1ubuntu0.17.04.1/+build/12474101 , I can confirm that the packages work exactly as intended."
1685522,2017-04-25 04:58:41 UTC,"The uploaded package is wrong. This tarball contains actual minimal contents, as it should be."
1685522,2017-04-25 04:41:46 UTC,"Hello Jason, or anyone else affected,"
1685522,2017-04-25 04:16:32 UTC,"[Impact]
 * After discussion on IRC with the release team, it seems clear that this package should have stayed in Debian sid and not migrated into a stable release of Ubuntu. This sentiment is reflected in the original Debian bug report about such.
 * Thus, rather than keep a rolling package up to date in a stable distro, this update simply removes the package and informs users about the situation.
 * This was determined to be the right path forward in discussions with cjwatson and infinity."
1685522,2017-04-24 15:03:52 UTC,This appears to have been added to the queue and is now waiting for approval:
1685522,2017-04-23 23:01:56 UTC,"As discussed on IRC, the following empty package should be put into Zesty."
1685522,2017-04-23 21:38:09 UTC,"$ demote-to-proposed -m 'LP: #1685522' wireguard
Demoting packages to artful-proposed:
 wireguard 0.0.20170214-1 in artful
Comment: LP: #1685522
Demote [y|N]? y
Remove wireguard from release [y|N]? y
1 package successfully demoted."
1685522,2017-04-23 14:53:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685522,2017-04-25 05:12:19 UTC,"Hello Jason, or anyone else affected,"
1685526,2020-11-10 15:29:15 UTC,"Looking through old bug tickets ... When reporting issues, please provide proper information on the versions that you were using (QEMU, OVMF, ...) and complete information about which command line parameters you used to start QEMU."
1685526,2020-11-11 23:07:20 UTC,"Out of scope; please see my (independent, more recent) replies here:"
1685527,2017-04-26 17:23:41 UTC,"> Graphics: OpenGL: Version ""1.1.0""
"
1685527,2017-05-18 16:32:10 UTC,"Same problem reported for Windows Vista in https://bugs.launchpad.net/widelands/+bug/1691644, where the OpenGL version reported is ""(null)""."
1685527,2019-09-16 08:47:05 UTC,Migrated to https://github.com/widelands/widelands/issues/3196
1685548,2018-01-16 11:27:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685549,2017-09-30 01:21:16 UTC,This bug was fixed in the package python-launchpadlib - 1.10.5-1
1685551,2017-09-13 21:13:34 UTC,"It was like that on purpose, it was clearly a mistake."
1685554,2017-04-24 19:51:31 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1588129, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1685566,2017-04-23 00:35:51 UTC,"Oops, forgot system info:"
1685566,2017-04-30 00:38:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685566,2018-03-01 08:37:55 UTC,"We're in 2018, March, the first, and the problem still occurs."
1685569,2017-04-23 22:10:19 UTC,"Setting up makedev (2.3.1-93ubuntu2~ubuntu16.04.1) ...
/sbin/MAKEDEV: 215: /sbin/MAKEDEV: Cannot fork
/sbin/MAKEDEV: 220: /sbin/MAKEDEV: Cannot fork
/sbin/MAKEDEV: 626: /sbin/MAKEDEV: Cannot fork"
1685575,2017-04-23 02:23:33 UTC,PR: https://review.openstack.org/#/c/459087/
1685575,2019-09-11 11:55:09 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.opendev.org/459087"
1685590,2017-07-28 01:11:14 UTC,"Thanks for confirming this bug. Since I have not deep insight with nova, following statements may not accurate or true, but these is what I found and put here for reference."
1685591,2017-04-24 15:08:02 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1685591,2017-04-24 20:32:09 UTC,I reported this at https://bugzilla.gnome.org/show_bug.cgi?id=781637
1685591,2017-04-25 09:42:18 UTC,thanks
1685598,2019-07-14 00:59:11 UTC,This has been long since fixed.
1685598,2017-12-06 15:18:14 UTC,Accepted
1685598,2017-11-21 19:07:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685598,2017-11-22 03:51:36 UTC,You're right.
1685598,2017-12-06 01:09:31 UTC,Released as per the other bug.
1685598,2017-11-21 19:10:16 UTC,"I stated this issue before the release, and Simon promised to fix it as you can see here:"
1685606,2017-11-13 12:35:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1685608,2017-07-11 17:49:44 UTC,I'm having the same issue using Ubuntu 17.04.
1685608,2017-08-28 00:40:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685609,2017-06-26 03:18:29 UTC,adobe-flashplugin does not exist in Debian.
1685609,2017-06-26 12:05:44 UTC,"@Jeremy: That would be good for Debian users, but what's the point with providing both adobe-flashplugin and pepperflashplugin-nonfree in Ubuntu?"
1685610,2017-04-25 07:17:59 UTC,Thanks Azu for your report and your help to make Ubuntu better!
1685610,2017-04-25 07:19:43 UTC,"At least from the source containing the assert, this could go back to Trusty."
1685610,2017-04-25 07:20:46 UTC,"Added the matching bug tasks, but for now Incomplete until we know how to trigger/reproduce this."
1685615,2020-04-26 04:17:16 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1685615,2020-02-25 08:16:42 UTC,I believe that this has been fixed already. Can you please confirm whether this is still a problem in MAAS 2.7?
1685615,2020-04-27 06:57:23 UTC,"Yes, I can confirm this seems to have been fixed at some stage between 2.3 and 2.7."
1685615,2017-04-24 19:48:00 UTC,"I'm worried that this is related to bug #1685306, where a machine interface suddenly becomes unconfigured just as it is deployed. I'm going to dig into that one to see if I can find a connection."
1685615,2017-04-24 19:44:44 UTC,I've not been able to get this to happen in my MAAS test setups; MAAS is properly showing the controller's bond interface on its details page. (see attached screenshot)
1685615,2017-04-24 18:55:29 UTC,"I'm going to try to reproduce this issue, but if you get a chance, could you please attach the output of:"
1685615,2017-04-25 19:24:44 UTC,"Can you also test if this is HA related? That is, if you have multiple rack controllers, shut the secondary down and check if the issue still occurs on the controller that remains online."
1685619,2018-10-18 21:49:55 UTC,I fear your are completely correct.
1685619,2018-10-18 16:28:26 UTC,closed via
1685619,2017-04-26 06:49:41 UTC,"I think we're saying the same thing: the user starts typing, the
type-ahead prompt is smart (based on what MAAS knows of subnets). But
having a subnet AND an IP in the UX is pedantic and boring and ugly and
bad, so please take the guidance and show me you can run with it. The
subnet i implicit in the IP. Static addressing is focused on the IP."
1685619,2018-10-18 16:53:23 UTC,"@Martin,"
1685619,2017-04-25 06:54:04 UTC,"In the case of static addressing, I probably have an address in mind.
There is no way for MAAS to read my mind :)"
1685619,2017-04-23 20:26:27 UTC,"What if it automatically inputs the ""best"" recommended (least recently used/available) IP address when the subnet is selected? Then the user can change it if s/he desires, and would at most need to delete an octet or two to get the desired address, if customization is required."
1685619,2017-04-25 18:42:45 UTC,"I think maybe a hybrid approach would be good, so the user could either start typing and the subnet would change to the appropriate one (or warn that it isn't present on the VLAN), or choose a subnet and get a default address from MAAS."
1685619,2017-04-23 14:03:14 UTC,"Of course, for Auto address configuration, the subnet is essential."
1685628,2017-06-04 12:42:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685628,2017-06-04 12:46:40 UTC,"Yes, I have this problem in xubuntu 17.04."
1685630,2017-04-23 15:48:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/459115"
1685630,2017-04-25 22:58:26 UTC,"Reviewed:  https://review.openstack.org/459115
Committed: https://git.openstack.org/cgit/openstack/os-client-config/commit/?id=ff2c06c30538edb9cb47b83f0a194f7893a7f458
Submitter: Jenkins
Branch:    master"
1685639,2019-08-29 09:05:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685647,2017-12-21 01:03:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685647,2017-12-21 01:03:27 UTC,Duplicate of 1694454?
1685655,2019-11-06 23:53:13 UTC,"Reviewed:  https://review.opendev.org/692081
Committed: https://git.openstack.org/cgit/openstack/manila-ui/commit/?id=7d3eb82eb85b2cdd175b5091fe7b99f4547c6aae
Submitter: Zuul
Branch:    master"
1685655,2019-10-30 09:07:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/692081"
1685669,2017-05-06 23:05:14 UTC,"This bug happens, if screenreader is activated."
1685669,2017-05-06 23:07:01 UTC,"It happens more often, if screenreader was switched on and off multiple times."
1685672,2017-05-09 11:10:17 UTC,"For the record, this has also cause artful-proposed to artful migrations to go ""missing"" as britney's copy-then-delete has no way of knowing the copy failed, so it ends up just being a delete."
1685672,2017-06-05 09:19:53 UTC,"this probably happened also to frama-c 20161101+silicon+dfsg-5, disappearing from the artful archive
(copy-paste from -release log, from cjwatson)"
1685681,2017-04-24 09:48:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685696,2018-07-12 06:22:46 UTC,@Nobuto
1685696,2018-07-10 06:12:51 UTC,The commit 801c2e78294f7af0a058aca036b6d066e3f53a98 in percona-cluster charm has a fix for this issue as well because it restarts mysqld after bootstrapped.
1685696,2018-07-09 16:53:36 UTC,"Indeed, it's not reproducible with the current latest charm. rev no. 266 seems to bring the difference."
1685696,2018-07-09 11:42:42 UTC,I followed this reproducer but can't reproduce this. ( or need more condition? )
1685696,2017-12-07 07:25:24 UTC,Will this be fixed in next release of nrpe ie nrpe#42 ?
1685696,2017-09-21 14:32:55 UTC,Raised a task on the NRPE charm and marked the PXC task as won't fix; I don't think we can resolve this in the percona-cluster charm purely due to the way that pxc has to be bootstrapped.
1685696,2017-09-27 13:48:04 UTC,"For future travellers, the fix is likely line 23 of https://git.launchpad.net/nrpe-charm/tree/files/plugins/check_systemd.py and the tests after it (string will be ""active"" rather than ""running"" when we use the ActiveState).  This is worth testing on multiple installations with a hand-rolled copy to make sure it behaves as we expect in production."
1685696,2017-09-21 14:23:37 UTC,"The systemd mysql unit records - ""active (exited)"" rather than ""active (running)"" as the process is not tracked by systemd when the bootstrap path is followed."
1685696,2017-09-21 14:21:08 UTC,This happens because the lead unit does not get started using the normal start target provided by the init.d scripts (which are wrapped by systemd normally).
1685696,2017-06-26 12:25:37 UTC,Ran into the same issue.
1685696,2017-04-25 05:41:27 UTC,A simple workaround would be rebooting the leader unit after the cluster is up and running.
1685696,2017-04-24 05:10:01 UTC,https://bugs.launchpad.net/charm-percona-cluster/+bug/1664025
1685696,2017-09-21 14:30:15 UTC,"I'd really rather avoid having to restart percona-cluster just to get the monitoring right; maybe looking at the 'ActiveState' rather than the 'SubState' might make sense here - the unit is active, but is in 'exited' SubState, which is what is causing the problem with the nrpe check."
1685696,2017-04-24 05:07:22 UTC,I believe the background in Bug: #1664025 is related.
1685705,2017-08-18 09:34:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685714,2017-04-24 07:00:10 UTC,This change was made by a bot.
1685715,2018-05-08 18:06:17 UTC,This change was made by a bot.
1685715,2021-01-07 04:17:47 UTC,4.8 EOL
1685717,2018-05-08 18:06:31 UTC,This change was made by a bot.
1685717,2021-01-07 04:17:50 UTC,4.8 EOL
1685723,2018-04-03 02:16:49 UTC,move it into 18.10 as discussed
1685723,2018-03-19 18:36:31 UTC,This is a huge series that affects a lot of users out there as it changes lots of common MMC code. We should target 18.10 for that.
1685723,2018-10-02 16:14:57 UTC,"All of the requested commits should be present in the 4.18 kernel for Ubuntu Cosmic, please advise if anything additional is needed."
1685723,2018-05-01 05:36:20 UTC,the commit should be the same as 1645959.
1685723,2018-03-01 20:13:27 UTC,That is correct. This feature capability first introduced in Geminilake (GLK). Same code capability is used in Coffelake and Cannonlake SKUs.
1685723,2018-02-13 10:53:27 UTC,Commits for this feature. The commit list is same as LP#1645959
1685723,2018-02-23 23:19:11 UTC,The following landed in 4.16-rc1 and would need to be considered for backporting.  Adding a linux task for Bionic.
1685723,2018-03-01 19:57:37 UTC,"Following commits are not on 4.15 and were successfully cherry-picked. The changes are limited to mmc, but that impacts lots of hardware and platforms."
1685723,2017-07-12 18:00:25 UTC,"In review currently, plan for 4.13"
1685723,2017-07-11 21:25:26 UTC,Do we have a list of upstream kernel commits that we should confirm we are carrying in our Ubuntu kernel target for 17.10? Thanks.
1685723,2017-07-27 02:39:30 UTC,upstream moves it to 4.14. Therefore I change it to 18.04. I will provide commit id once Upstream finish it.
1685737,2017-04-24 08:19:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459189"
1685740,2017-05-06 08:19:33 UTC,"Confirmed on Windows XP (32-bit), lp:inkscape/0.92.x rev. 15420."
1685747,2017-10-13 10:58:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685747,2017-04-24 08:30:38 UTC,apport information
1685747,2017-11-10 15:06:51 UTC,"Note that xchat-gnome works on X session, and with XWayland when started with:"
1685747,2017-04-24 08:30:35 UTC,apport information
1685747,2017-04-24 08:30:34 UTC,apport information
1685747,2017-04-24 08:30:37 UTC,apport information
1685748,2017-05-29 01:14:07 UTC,Did I file this bug in the correct component/project?
1685754,2018-04-11 21:07:12 UTC,"Ray Strode, it sounds like a good news !"
1685754,2018-05-19 15:01:09 UTC,"In 16.04, I usually added `umask=0027` after `session optional pam_umask.so` in file `/etc/pam.d/common-session`. Not sure it was the appropriate place but worked for me."
1685754,2018-04-12 20:25:25 UTC,You can of course use pam_umask(8) on Ubuntu as well if you wish.
1685754,2018-07-01 20:39:07 UTC,"does not affect gedit instances which are launched via xterm or alt+F2, so I assume it's due to the systemd --user or the gnome-terminal user session."
1685754,2018-04-12 17:57:37 UTC,Ok... Thanks for explanation.
1685754,2018-04-12 10:38:45 UTC,"nope you got it backwards. pam_umask is the library that reads login.defs, login.defs isnt what sets pam_umask.  this has nothing to do with the gnome environment itself, but the system level services that start gnome (and those same system things start programs unrelated to gnome). see comment 31"
1685754,2018-04-11 22:09:34 UTC,You can of course use pam_umask(8) on Ubuntu as well if you wish.
1685754,2018-04-11 21:17:11 UTC,fwiw → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c44 → where security issue is also mentioned.
1685754,2018-07-01 20:36:34 UTC,"confirmed to affect user instance of gnome-terminal and nautilus.  xterm, su, and commands run by alt+F2 are all unaffected."
1685754,2017-11-11 01:50:58 UTC,"Hello,"
1685754,2018-04-11 20:13:51 UTC,"With systemd version 237-3ubuntu7 from Ubuntu 18.04 beta 2 (Bionic), the issue is still the same."
1685754,2018-04-11 20:09:53 UTC,"In Ubuntu 18.04 beta 2 (Bionic), the issue is the same."
1685754,2017-12-03 22:24:53 UTC,It's a real pain for managing machines with multi-users and shared folders.
1685754,2017-11-11 15:42:23 UTC,Files created with Gedit don't apply expected 002 umask.
1685754,2018-07-05 23:52:26 UTC,"This is a bug in every GNOME application that uses systemctl --user to start itself.  There is currently no sane fix because systemd is missing a feature of upstart, umask inheritance.  GNOME could abuse systemd's instantiated services feature to pass the umask through this but this would be far from ideal."
1685754,2017-11-11 01:42:51 UTC,"Hello,"
1685754,2017-08-06 22:08:26 UTC,"@Christian Perse, how can one set the default umask in Ubuntu Gnome 16.04+ or Debian Gnome 9?"
1685754,2017-06-30 07:07:17 UTC,"$ grep '^ *[^#].*pam_umask' /etc/pam.d/*
/etc/pam.d/common-session:session optional			pam_umask.so
/etc/pam.d/common-session-noninteractive:session optional			pam_umask.so"
1685754,2017-06-30 03:03:22 UTC,"Oh, one more possible confusion -- when a process's parent dies, it is reparented to pid 1. This guarantees that _some_ process will wait(2) on every dead child. So seeing 'ppid 1' in a process listing simply means the process's parent died before you looked for it."
1685754,2017-06-30 03:02:01 UTC,I believe even Gnome on 16.04 LTS is using the upstart user session rather than system user session. This could be part of why the Gnome bug discussion seemed to go around in circles.
1685754,2017-06-29 21:44:41 UTC,Now that the title of this issue is clearly focused on UMASK :
1685754,2018-04-11 20:20:27 UTC,"fwiw, in fedora we're going to start adding pam_umask to the default pam configuration so admins can edit /etc/login.defs"
1685754,2018-07-06 00:13:11 UTC,"Correction, I believe this is actually a bug in dbus.  gnome-terminal, and others are not setting <keep_umask> as it should, but as far as I know, dbus cannot support <keep_umask> in a systemd environment due to the limitations mentioned in #21."
1685754,2019-06-17 18:43:30 UTC,"Currently, the upstream issue has NOT been migrated to GNOME GitLab yet, but is still being tracked at https://bugzilla.gnome.org/show_bug.cgi?id=780622"
1685754,2018-08-07 22:20:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685754,2017-06-29 21:23:59 UTC,"Yes, I think that this issue comes from the 'gnome-session' issue described at https://bugzilla.gnome.org/show_bug.cgi?id=780622"
1685754,2021-02-24 21:22:51 UTC,"> REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy Gorilla), the issue had reappeared
"
1685754,2020-10-06 13:18:06 UTC,"REGRESSION:  With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy Gorilla), the issue had reappeared"
1685754,2020-09-09 18:09:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685754,2020-05-10 15:30:39 UTC,"This issue was fixed in systemd by https://github.com/systemd/systemd/pull/15318. Debian cherry-picked that change into 245.4-3, so Debian bullseye and buster-backports have the fix, as does Ubuntu 20.04 (focal)."
1685754,2020-04-15 10:39:02 UTC,@eurbah 245.4-4ubuntu1 fixed the issue in systemd.
1685754,2020-04-04 21:47:20 UTC,"With systemd version 245.2-1ubuntu2 from Ubuntu 20.04 Beta (Focal Fossa), the issue is still the same."
1685754,2020-02-10 16:10:24 UTC,"I think it's an systemd issue, which is already reported on GitHub but not fixed yet:"
1685754,2020-01-07 16:15:01 UTC,"Hello,"
1685754,2020-01-05 23:27:36 UTC,"Sven, here are the workaround steps (as root) :
1) Create the folder '/etc/systemd/user/gnome-terminal-server.service.d' (with usual mode 755).
2) In this newly created folder, create the 'umask.conf' file with following content :
   [Service]
   UMask=<umask value>"
1685754,2020-01-05 15:44:13 UTC,is there now a solution that works under Ubuntu 19.10?
1685754,2019-12-11 18:09:47 UTC,i have the same problem in Ubuntu 19.10 :-(
1685754,2019-11-23 18:58:09 UTC,"Is there any workaround for Nautilus?
I tried with /etc/systemd/user/nautilus.service.d/umask.conf and /etc/systemd/user/Nautilus.service.d/umask.conf but nothing seems to work.
Thanks in advance!"
1685754,2019-08-27 13:35:56 UTC,"Thanks for your answer and prompt support. I tried again and find my mistake, i am using models for test that are just a copy of file without changing models permissions, without models and just create empty document and directory IT WORK :-). I confirm that the workaround is effective on 18.04.3 LTS and 19.04. Thanks again"
1685754,2019-08-27 11:10:32 UTC,"In order that gnome-terminal starts with the correct umask :
Lot of thanks to Olivier JOLY for comment #27 :
His workaround is effective."
1685754,2019-08-25 08:03:31 UTC,"I move too Ubuntu 19.04 and we are still affected by this bug, into multi users professional environment we usually just use LTS, but try to solve this issue without success. ;-(
Try also without success :
===============
A workaround for those of us that need a solution now is to place"
1685754,2019-06-18 00:53:54 UTC,"Ah, OK, thanks. No news since 2018-08 then - I was hoping the GNOME GitLab would have something new :("
1685754,2019-06-17 15:04:56 UTC,"Does anyone know where this bug is being tracked upstream now? GNOME has migrated from Bugzilla to GitLab, and I haven't been able to find the GitLab version of the Bugzilla bug."
1685754,2018-08-28 15:08:08 UTC,"Ray, thanks for the suggestion. But the issue still remains: ""nautilus --gapplication-service"" is still running with umask=022 (stared by systemd --user) and creates directories with permission 755."
1685754,2018-08-28 13:45:05 UTC,try putting pam_umask in /etc/pam.d/systemd-user
1685754,2018-08-28 13:42:22 UTC,"Folks, sorry for the rant that will follow, but I am really astonished that this bug is now open for more than a year and that it seems to affect more or less every modern Linux distribution that uses Gnome."
1685754,2018-07-06 00:47:19 UTC,"I am fairly certain the bug is not (at least not completely) in any gnome project.  It appears to be in dbus.  In particular, dbus has two issues:"
1685754,2017-06-29 15:16:59 UTC,"@Christian Perse, do you know a workaround to get this working until this bug is fixed? What about Comment 39's ""UMask="" option. Is there a config file where this can be inputted to see if it has any effect?"
1685754,2017-03-28 14:16:21 UTC,"Christian, thanks for the clarification."
1685754,2017-06-29 15:09:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685754,2017-04-05 08:00:27 UTC,One extra piece of information: it seems that on my system gnome-terminal is indeed started by dbus:
1685754,2017-06-29 15:14:25 UTC,Isn't this a gnome-session bug?
1685754,2017-03-28 17:04:15 UTC,"You're reading this wrong, it's not the PID1 systemd, it's the user systemd. (Unless you're logging in to GNOME as root? That's completely unsupported.)"
1685754,2017-03-28 16:55:31 UTC,(I presume trying to attach gdb to PID 1 to find out the umask is not a good idea.)
1685754,2017-03-28 16:55:01 UTC,Confirmed with pstree --show-parents: it's PID 1.
1685754,2017-03-28 16:53:25 UTC,Thanks again.
1685754,2017-03-28 16:25:34 UTC,"Try using pstree to find which process is the parent of gnome-terminal-server, and then look what that one's umask is?"
1685754,2017-03-28 15:25:13 UTC,"I did some more investigation on how to set the umask for the user session in systemd, but I couldn't work out how to do it. I tried adding"
1685754,2017-03-28 14:37:08 UTC,"I can't find any mention of UMask in the systemd configuration. systemd.exec(5) says that the default value is 0022, so no explanation of how it's ending up as 0002 for me."
1685754,2017-03-28 14:20:08 UTC,I found this bug for dbus: https://bugs.freedesktop.org/show_bug.cgi?id=18446
1685754,2017-03-28 10:57:09 UTC,"(In reply to Reuben Thomas from comment #4)

> I am assuming therefore that my umask having been set, by my .profile, by
> /etc/gdm/Xsession, that the same process will (eventually) start
> gnome-terminal-server (via gnome-terminal), and that therefore the umask I
> set should be inherited (as occurs with xterm).
"
1685754,2017-03-28 10:21:17 UTC,"The answer is, the umask of that process is 0002. Thanks very much for digging out a way for me to get it."
1685754,2017-03-28 10:13:35 UTC,"Lack of the Umask line tells us nothing. Unfortunately it seems like a brand new feature, not yet available on your Ubuntu 16.04. (I'm on Ubuntu 16.10 and it's already there.) See e.g. http://unix.stackexchange.com/questions/258284/current-umask-of-a-process-with-pid for another possible method."
1685754,2017-03-28 09:24:22 UTC,"Thanks, Egmont. I'd already grepped through gnome-terminal, but I hadn't gone deeper (e.g. I didn't check glib for GApplication, though I read the docs and they don't mention changing the umask)."
1685754,2017-03-28 09:09:07 UTC,Just for the record: Could you please check the umask of your gnome-terminal-server process?
1685754,2017-03-28 09:01:19 UTC,Neither vte's nor gnome-terminal's code has any umask() calls.
1685754,2017-03-28 08:54:37 UTC,"Some additional information, for the sake of clarity: umask(2) says:"
1685754,2017-03-28 01:08:04 UTC,Just to confirm: /etc/gdm/Xsession on my Ubuntu system contains the lines:
1685754,2017-03-28 00:59:08 UTC,"Thanks for your reply. I am sorry, I tried very hard to be clear, but obviously failed."
1685754,2017-03-27 21:50:36 UTC,"(In reply to Reuben Thomas from comment #0)

> I set my umask in my .profile to 0027.


[...]

> Both are configured not to start a login shell.
"
1685754,2017-03-27 21:38:07 UTC,I set my umask in my .profile to 0027.
1685754,2017-04-05 08:33:08 UTC,"I cannot understand what is going wrong on my system: dbus's session.conf has the keep_umask option, so why when it starts gnome-terminal that does not preserve the umask I don't know."
1685754,2017-04-05 09:39:15 UTC,"So we've established (comment 9) that gnome-terminal-server's umask is set to the same value as the one as bash/etc inside gnome-terminal, so there's no bug in gnome-terminal here. How that umask comes to be set to the value it has is a problem elsewhere. Try your distribution's support forums or bug tracker."
1685754,2017-03-28 17:18:05 UTC,Sorry if I've misread something or done something wrong. Here's more detail:
1685754,2017-04-05 11:19:01 UTC,This really isn't the right place to discuss this.
1685754,2017-06-28 11:13:14 UTC,*** Bug 784113 has been marked as a duplicate of this bug. ***
1685754,2017-06-25 15:01:15 UTC,"In gnome 3.22, how do I set a default umask that gnome respects? So for example if I login to gnome thru GDM and then open gedit and create a document, the document has permissions 600 by default."
1685754,2017-06-25 13:53:28 UTC,Is this bug related to this: https://bugzilla.gnome.org/show_bug.cgi?id=784113
1685754,2017-05-01 15:57:52 UTC,"Environment variables
---------------------
For environment variables, it would be nice if GNOME considers 'systemd --user' as a login shell and runs it (with all its children) in the context of '.profile'."
1685754,2017-05-01 13:48:31 UTC,"(In reply to Christian Persch from comment #37)

> (In reply to Reuben Thomas from comment #36)
> > This is the bug that needs to be fixed: from a GNOME user's point of view,
> > systemd is an implementation detail, which has now (unfortunately) become
> > visible: a classic leaky abstraction.
> >
> > So GNOME needs to be fixed so that the entire user session is always run in
> > the scope of the user's .profile.
>
> That won't work, since the systemd --user instance will itself not see
> anything in .profile since it doesn't take its configuration from the
> environment, and thus still use its own default for umask, etc., when
> autostarting dbus services.
"
1685754,2017-05-01 13:00:38 UTC,"(In reply to Reuben Thomas from comment #36)

> This is the bug that needs to be fixed: from a GNOME user's point of view,
> systemd is an implementation detail, which has now (unfortunately) become
> visible: a classic leaky abstraction.
>
> So GNOME needs to be fixed so that the entire user session is always run in
> the scope of the user's .profile.
"
1685754,2017-05-01 11:47:48 UTC,"Christian, thanks for your excellent summary."
1685754,2017-04-05 09:53:00 UTC,I will do.
1685754,2017-04-30 21:02:23 UTC,Thanks to Seth Arnold for his advices to use the 'perf' or 'auditd' tools.
1685754,2017-04-30 20:56:47 UTC,Thanks to Seth Arnold for his advices to use the 'perf' or 'auditd' tools.
1685754,2017-05-01 08:37:26 UTC,"Again, gnome-terminal-server does *not* change your umask. In fact, it never calls umask(3p), as you can verify using 'git grep' on its source code."
1685754,2017-04-27 23:08:14 UTC,"Lot of thanks to Reuben Thomas for having discovered, reported and dug the issue."
1685754,2017-04-05 13:21:41 UTC,"I am running a default GNOME session from Ubuntu GNOME 16.04, which is indeed gnome-session started by gdm."
1685754,2017-04-27 23:39:39 UTC,"Etienne, the upstream bug comments suggest it may not be limited to just gnome-terminal. You may have success finding what component / process is performing the umask() calls via perf or auditd:"
1685754,2017-04-05 14:38:06 UTC,Thanks!
1685754,2017-04-06 15:04:44 UTC,~/.profile will not be sourced before gnome-terminal-server is started if it's started by dbus-daemon or systemd --user.  My guess is if you did
1685754,2017-04-05 14:34:41 UTC,"-> gnome-session for triage, although I'm not sure it's the right place either."
1685754,2017-04-07 15:38:38 UTC,"there's nothing gnome-session can do really. it's not involved at all.  gnome-terminal requests a service provided by gnome-terminal-server.  dbus either activated gnome-terminal-server or farms off the task of activating gnome-terminal-server to systemd.  The easy, maybe good enough, solution would be for you to tick the ""run a login shell"" preference in gnome-terminal or set umask in ~/.bashrc instead."
1685754,2017-04-07 17:59:45 UTC,"Thanks, Ray."
1685754,2017-04-27 15:11:00 UTC,"There is a discussion about a related problem in the upstream bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=780622
Since the problem space is known, I'm making the bug public and subscribing the desktop team for further assistance."
1685754,2017-04-27 22:39:49 UTC,Thanks to Emily Ratliff for https://bugzilla.gnome.org/show_bug.cgi?id=780622
1685754,2017-04-06 19:10:57 UTC,Thanks; I tried those two commands and both give an error:
1685761,2017-04-24 11:31:27 UTC,this problem is due to  horizon dir '/' do not hava enough space
1685761,2017-04-28 09:34:37 UTC,"this bug because horizon upload images /tmp/tmp* can't delete ,if you Continuous upload images may lead to  ir '/' do not hava enough space ."
1685761,2017-10-18 13:10:20 UTC,"If this is caused by the limited space in the directory, we just need to make sure the error message shown in horizon is appropriate."
1685761,2017-10-21 21:14:46 UTC,Maybe we should consider changing the default HORIZON_IMAGES_UPLOAD_MODE to 'direct' at some point?
1685769,2017-04-24 10:56:33 UTC,Original desktop background
1685769,2018-04-24 11:46:39 UTC,Fixed in Ubuntu MATE 18.04 via mate-screensaver 1.20.0-1.
1685769,2018-07-16 08:23:12 UTC,"apt policy mate-screensaver
mate-screensaver:
  Installed: 1.20.0-1
  Candidate: 1.20.0-1"
1685769,2018-07-16 16:48:48 UTC,Seems like a regression from this commit: https://github.com/mate-desktop/mate-screensaver/commit/c862d81db1e0ae1ce1f62a3aac1d915f5036c81c
1685769,2018-09-30 10:02:37 UTC,This is confirmed as regressing in Ubuntu MATE 18.04 but fixed in Ubuntu MATE 18.10 via mate-screensaver 1.20.2-1. I will SRU the fix to 18.04.
1685770,2017-10-16 13:54:27 UTC,"Wrong importance classification according to the triage of the 25-04-2017:
http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-04-25-16.04.log.html#l-18"
1685771,2017-04-24 12:45:11 UTC,"Need to backport properly the https://review.openstack.org/#/q/68318cf10bb7e9025fec06369a47ba54d741697a,n,z"
1685777,2017-04-24 11:49:08 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/459251"
1685777,2017-04-28 12:48:46 UTC,"Reviewed:  https://review.openstack.org/459251
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3890eb169aae42b20fbdde620e13970ccc105353
Submitter: Jenkins
Branch:    stable/newton"
1685777,2017-09-04 18:17:23 UTC,This issue was fixed in the openstack/tripleo-heat-templates 5.3.1 release.
1685778,2020-04-17 13:56:19 UTC,This bug was fixed in the package pdfchain - 1:0.4.4.2-2
1685778,2017-09-12 20:56:37 UTC,Is there something we can do on our devices to fix this until there is a general fix? Thanks!
1685778,2018-07-23 23:48:35 UTC,https://launchpad.net/~wdaniau/+archive/ubuntu/custom/+packages has a fixed package with the patch applied.
1685778,2017-09-06 16:06:17 UTC,"This is related to Debian Bug #725859, for which I have forwarded a patch. I have attached it here as well, in case you would like to release a fix before Debian does."
1685778,2017-06-22 14:26:26 UTC,Maybe it helps:
1685778,2017-05-23 17:02:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685778,2017-09-06 16:20:02 UTC,"The attachment ""fix_crash_on_startup.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1685794,2018-05-05 16:23:41 UTC,For me this problem appeared after I upgraded from 17.10 to 18.04 two of my machines. Both machines increased their boot times substantially (by around 30 seconds).
1685794,2018-05-07 19:46:10 UTC,"First of all, I do not use Ubuntu, I use Debian, but I thought it would be a nice input anyway, feel free to delete this if this don't help.
I had the same problem the first reboot I did after a system update to:"
1685794,2018-07-08 20:49:16 UTC,"In case it is helpful to anyone else, I found a resolution for my specific case. This askubuntu question helped: https://askubuntu.com/questions/1018907/ubuntu-installation-stuck-at-random-crng-init-done . In sum: sudo apt install rng-tools"
1685794,2018-07-24 08:43:14 UTC,Since the last kernel update it is fixed form me.
1685794,2018-08-10 00:32:36 UTC,"At boot, the kernel waits for mouse movements to initialize the random number generator.
Kernel messages on boot:
[code]
sudo dmesg | less
[/code]"
1685794,2018-08-13 19:28:24 UTC,haveged not solve for me.
1685794,2018-11-12 01:42:23 UTC,"Note that ""random: crng init done"" appearing very late is not a problem by itself. User-noticeable delays only arise if some components (like Bluetooth?) require the crng init to be completed in order for themselves to initialize. This indicates poor design in those components (they should never block indefinitely waiting for /dev/random) and is not a problem with the random number generator itself."
1685794,2018-11-12 01:43:09 UTC,... so using haveged is a workaround and not a fix.
1685794,2018-12-28 00:14:18 UTC,Neither rng-tools nor haveged solves this problem for me.
1685794,2018-12-30 05:35:32 UTC,"Ive had this problem numerous times, and my solution works in all situations."
1685794,2019-06-05 21:06:55 UTC,"To add to Andrew's solution, in my case, the UUID in /etc/initramfs-tools/config.d/resume was correct. But my swap was on an LVM partition."
1685794,2019-07-16 13:07:50 UTC,This debian bug
1685794,2019-07-16 20:25:11 UTC,Just to add more ubuntu/debian specific details because this includes a kernel config options that was changed from vanilla kernel and that not everyone may agree with and I had missed myself.
1685794,2018-04-29 18:05:54 UTC,"Cheered too soon: after a few reboots the problem is back.
:("
1685794,2018-10-20 15:03:49 UTC,Again Debian stretch with backports (kernel 4.18) on an Asus B53F with another wireless card and without that broadcom-sta-dkms package. Installing rng-tools solves the problem.
1685794,2018-04-29 15:35:04 UTC,"I had the same problem (or a problem like the one at hand).
In posts #12 through #15 the user commenting out a line in hist /etc/cryptsetup file resolved the problem.
As I did not have that file I installed the cryptsetup{,-bin} packages and rebooted: problem resolved!
:D"
1685794,2018-10-07 10:35:09 UTC,Debian stretch with backports (kernels 4.17 and 4.18) on a Dell Latitude E6420 with a Dell Wireless 1530 (Broadcom BCM43228) card.
1685794,2018-01-07 10:40:04 UTC,And here is a part of the gnome-system-log.
1685794,2018-01-07 10:50:20 UTC,My etc/fstab looks like this:
1685794,2017-04-24 13:04:20 UTC,Output of: sudo lspci -vnvn > lspci-vnvn.log
1685794,2017-04-24 13:30:12 UTC,This change was made by a bot.
1685794,2017-04-24 17:13:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1685794,2017-04-24 18:12:57 UTC,"It's a fresh 17.04 installation no upgrade involved. I will try the latest
upstream kernel and report back.
Thanks for the hint!"
1685794,2017-04-26 13:25:45 UTC,I just booted 4.11-rc8 as per your instructions and the issue is still present.
1685794,2017-05-08 11:00:23 UTC,"I've got a similar issue in that there's a pause of around 90 seconds during boot, though the messages either side of the pause are different. Thing is, there's no way of knowing whether the messages either side are even relevant - I can't believe that an almost identical length pause is not related to this issue though. I'm using 17.04 that was upgraded, though after the upgrade I also swapped the motherboard/processor to an Asus Prime X370-Pro and Ryzen 7 1700. I'm now using mainline kernel 4.11.0-041100-generic but the delay was also there with the stock 4.10."
1685794,2017-05-08 11:34:43 UTC,"Typical - been looking at this off and on for a week or so, but posting here got me looking again. Searched for ""linux 90 second boot delay"" and found a few people who'd found that the swap partition was incorrectly configured, causing a 90 second delay."
1685794,2017-05-08 12:57:31 UTC,I just checked my system and discovered configuration in my fstab and crypttab that pointed to a nonexisted file. I created a swapfile and corrected the configuration. Now my system boots in 13 seconds total! Thanks for the hint!
1685794,2018-08-29 06:42:44 UTC,Haveged and rng-tools5 or rng-tools didn't help me too.
1685794,2017-05-08 18:38:42 UTC,I'm having the same issue.  Running Ubuntu Gnome on a Macbook Pro.
1685794,2017-05-08 18:53:39 UTC,What does your /etc/crypttab look like?
1685794,2017-05-08 19:06:50 UTC,This is my cryptswap:
1685794,2017-05-08 19:15:02 UTC,crypttab*
1685794,2017-05-08 19:22:50 UTC,I commented that line out.  My boot is under 10 seconds now!  Thanks!
1685794,2017-05-08 19:33:50 UTC,You're welcome!
1685794,2018-01-07 10:39:18 UTC,Ubuntu 16.04.3 - 64bit - Gnome
1685794,2017-05-08 13:03:44 UTC,I completely disabled swap now and it's working flawlessly.
1685796,2019-01-22 07:17:11 UTC,"This bug is affecting me in 2019, it looks like it was fixed in 2016:"
1685796,2017-04-24 15:44:54 UTC,This bug is solved in Ubuntu 17.04 with systemd 232. Please solve it in Ubuntu 16.04 LTS.
1685796,2017-05-07 18:20:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685802,2017-04-24 17:46:45 UTC,"Setting smsd's effective group to 'smsd' (in /etc/default/smstools) seems to me the better option.  That way users can be given access to the smstools spool directories (by adding them to group 'smsd') without granting them access to the ""raw"" modems (which would happen if they were added to 'dialout')."
1685818,2017-05-24 08:48:18 UTC,"I reconfigured our production setup now: The parallel deletion of 100 volumes still triggers the above deadlock messages, but due to the concurrency introduced by the pymysql driver (in combination with  the reduction of the innodb_lock_wait_timeout to 1 second) the deletions went through w/o triggering client side timeouts. Seems to be OK now."
1685818,2017-07-26 18:34:17 UTC,"I'm seeing something very similar except on creates. Specifically I have a script that fires off 10 threads,  Each does a cinder create, gets the ID from the create call and then waits for the volume to become available. Normally all 10 call to 'create' return within the same second or 2. But every once and awhile there's a 50 second delay and I then also see the deadlock message in the API log, so it's not strictly related to a delete."
1685818,2017-05-23 11:55:45 UTC,"Thanks, Gerhard! This seems to work: with the connection string changed following your suggestion, I cannot reproduce the problem any more, it seems."
1685818,2019-08-28 16:27:14 UTC,Should we document a particular config setting to get around this?
1685818,2019-12-05 10:50:49 UTC,"The given solutions did NOT fix this bug for us.
pymysql+sql was already set and increasing the innodb_lock_wait_timeout did not help either."
1685818,2017-05-23 10:57:49 UTC,you should use  connection = mysql+pymysql://cinder:REDACTED@REDACTED/cinder
1685818,2017-07-27 06:48:40 UTC,"I've seen previous bug reports for this issue reporting problems on creations as well, yes. It's just that I never tried to reproduce this with creations."
1685818,2017-05-22 10:53:54 UTC,"Jay,"
1685818,2017-05-18 09:24:16 UTC,"I tried on my devstack environment with these steps below, but failed to reproduce the issue."
1685818,2017-05-18 09:59:34 UTC,"Would you mind retrying with ""cinder delete vol1 vol2 ... vol100""?
Because this is how I reproduce the issue."
1685818,2017-05-17 22:39:21 UTC,"Jay,"
1685818,2017-05-17 21:40:08 UTC,"I spent time trying to recreate this on our Ceph cluster this afternoon without any luck.  I was able to do a parallel delete of 100 volumes, multiple times, without any failures or DB deadlock messages."
1685818,2017-04-28 17:32:15 UTC, https://bugs.launchpad.net/cinder/+bug/1613947 seems to describe the same issue.
1685818,2017-04-27 08:32:52 UTC,"One mitigation is to reduce innodb_lock_wait_timeout (from default 50 secs to 1 sec in our case): the deadlock gets detected faster, retries are triggered and deletions finish quicker. The underlying problem is of course still there."
1685818,2017-04-26 13:58:45 UTC,I cannot reproduce this on devstack with LVM.
1685818,2017-04-25 11:37:35 UTC,"I've upgraded one of the Cinder instances to Otaca now, the issue persists (not excluded that this is due to my config, DB setup, or Ceph backend setup, of course)."
1685818,2017-05-19 18:52:44 UTC,"For comparison I tried doing this using one of my Lenovo backends and I was not able to recreate the problem with that driver either.  I was able to delete 100 volumes in parallel and though it took some time, it complete successfully."
1685822,2017-04-24 16:08:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459396"
1685822,2017-09-29 04:46:11 UTC,"I didn't get the AttributeError with horizon master branch. Instead, I got error message ""please fill out this field"" shown in a tooltip, but it should be shown below the field instead."
1685822,2017-10-17 16:35:22 UTC,"Hi Ying. Thanks for your comments.
When I upgraded the local environment, the problem didn't come back."
1685822,2018-09-06 08:09:33 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/459396
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1685824,2018-07-17 12:21:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685842,2017-04-24 16:31:47 UTC,Не знаю
1685844,2017-04-26 13:22:15 UTC,"Reviewed:  https://review.openstack.org/459757
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=0628e125eb3070afcbaf7a02ae5e2271676e984a
Submitter: Jenkins
Branch:    master"
1685844,2017-04-27 06:45:15 UTC,"I've submitted a patch to fix two NAt failure
https://review.openstack.org/#/c/460402/"
1685844,2017-04-28 13:14:12 UTC,"Reviewed:  https://review.openstack.org/460402
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=00bb39fb69cf9f1f6e8b487667e1163b0b74bb9e
Submitter: Jenkins
Branch:    master"
1685844,2017-04-25 10:25:05 UTC,I've proposed a patch to add a query to elastic recheck for this problem: https://review.openstack.org/#/c/459622/
1685864,2017-04-24 17:30:12 UTC,This change was made by a bot.
1685864,2017-04-24 17:36:46 UTC,"Might also be related to https://bugs.launchpad.net/ubuntu/zesty/+source/unity8-desktop-session/+bug/1632772 since removing unity8-desktop-session also allowed me to log in using gnome shell. However, I still think it shouldn't have caused a null pointer dereference."
1685864,2017-04-24 18:34:22 UTC,Are you able to login if you boot with the prior kernel version?
1685864,2017-04-24 19:38:43 UTC,"Yes, if I boot using the 4.8 kernel I am able to login."
1685864,2017-04-25 16:51:28 UTC,I'd like to perform a kernel bisect to figure out which commit caused this regression. We need to identify the earliest kernel that did not exhibit the bug and the first kernel that did exhibit the bug.
1685864,2017-04-26 16:18:48 UTC,"I couldn't boot into 4.10-rc1 (it got stuck at loading the initram), and the other two allowed me to login, however, there were errors printed:"
1685871,2017-08-15 08:49:46 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1685871,2017-06-28 16:50:03 UTC,Fix reviewed and merged here: https://review.openstack.org/460002.
1685871,2017-04-28 12:36:19 UTC,Thank you mark!  This is extremely logical to do.  I'm surprised we didn't already do it.  Thanks again!
1685875,2017-08-01 10:16:15 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1685875,2017-04-26 17:55:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/460244"
1685875,2017-08-01 09:54:26 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/460244
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1685876,2017-05-11 12:04:17 UTC,Fix merged here: https://review.openstack.org/#/c/460003/.
1685876,2017-08-15 08:49:47 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1685877,2017-06-28 16:48:54 UTC,Reviewed and merged here: https://review.openstack.org/#/c/460004/
1685877,2017-08-15 08:49:44 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1685878,2017-05-01 14:33:50 UTC,I have also found this issue in gnome-builder so I believe it to be a GTK+ issue.
1685878,2018-12-12 10:55:33 UTC,"Upstream issue now being tracked at
https://gitlab.gnome.org/GNOME/gtk/issues/809"
1685878,2018-12-12 10:55:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685879,2018-02-02 22:03:18 UTC,+2? :)
1685879,2018-05-03 18:47:52 UTC,Above patch now merged to master - will be released with rocky.
1685879,2018-08-10 21:39:50 UTC,This issue was fixed in the openstack/bifrost 5.1.0 release.
1685918,2020-06-24 11:25:27 UTC,Seems like fixed in Focal
1685918,2019-02-11 00:04:25 UTC,"It looks like this fix was dropped when going to cosmic, reopening."
1685918,2018-04-16 08:48:50 UTC,"Thanks Rolf and Simon. There are a few other packages with hard dependencies on fonts. When I come across those again, I will propose demoting those too."
1685918,2018-04-15 06:39:43 UTC,This bug was fixed in the package kodi - 2:17.6+dfsg1-1ubuntu1
1685918,2020-06-24 11:27:57 UTC,"Now other fonts have become a hard dependcy,"
1685918,2018-04-15 02:47:09 UTC,same change for xenial
1685918,2018-04-15 02:29:14 UTC,I agree that I cannot see a reason that a font should be a hard dependency
1685918,2017-05-03 11:16:36 UTC,"Kodi confirms that this is a dependency which is not required or added by them but added by the Debian packager. Hence, this is an action item for Ubuntu and Debian."
1685918,2017-05-01 08:29:33 UTC,See also bug report at Kodi https://trac.kodi.tv/ticket/17454
1685918,2017-04-24 20:27:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685918,2018-04-15 04:35:27 UTC,"I'm uploading to Bionic for the sake of getting this in the LTS release, but please forward it to Debian as well."
1685931,2017-04-24 21:27:30 UTC,apport information
1685931,2017-04-24 21:27:27 UTC,apport information
1685931,2017-04-24 21:27:23 UTC,apport information
1685931,2017-04-24 21:27:21 UTC,apport information
1685931,2017-04-24 21:27:19 UTC,apport information
1685931,2017-04-24 21:27:16 UTC,apport information
1685931,2017-04-24 21:27:18 UTC,apport information
1685931,2017-04-24 21:27:14 UTC,apport information
1685931,2017-04-24 21:27:12 UTC,apport information
1685931,2017-04-24 21:27:10 UTC,apport information
1685931,2017-04-24 21:27:08 UTC,apport information
1685931,2017-04-24 21:27:06 UTC,apport information
1685931,2017-04-24 21:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1685931,2017-04-24 21:27:15 UTC,apport information
1685931,2017-04-24 21:27:05 UTC,apport information
1685934,2017-04-25 09:43:50 UTC,"Thank you for your bug report, what desktop environment and desktop version do you use? Could you describe how to trigger that dialog? It looks like it's trying to use actions on notifications"
1685934,2017-04-25 11:15:43 UTC,"Ubuntu 17.04, it is triggered by calendar event notifications, propagated from Evolution."
1685934,2017-06-25 04:17:35 UTC,[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.]
1685934,2017-08-08 22:31:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1685935,2017-06-27 15:52:16 UTC,"The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1685935,2017-09-23 02:31:37 UTC,"This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New"
1685935,2017-06-27 15:54:45 UTC,This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-0ubuntu1~16.04.1
1685935,2017-06-27 15:54:02 UTC,This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-0ubuntu1~16.10.1
1685935,2017-06-13 21:57:28 UTC,No impact possible as Makefile doesn't exist in packaged deb
1685935,2017-06-13 19:07:16 UTC,"Hello Chad, or anyone else affected,"
1685935,2017-06-13 18:53:44 UTC,"Hello Chad, or anyone else affected,"
1685935,2017-06-13 18:05:21 UTC,"Hello Chad, or anyone else affected,"
1685935,2017-06-13 17:56:06 UTC,"Because I'm a nice guy I added a cloud-init Ubuntu task for this bug so it could be SRU'ed, I also manually verified that this particular fix exists in Artful by downloading the package and checking the Makefile."
1685935,2017-06-27 15:51:34 UTC,This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-0ubuntu1~17.04.1
1685937,2019-10-14 22:31:29 UTC,"Had the same issue with an Evoo 11.6"" tablet (Atom Cherry Trail, sold by Walmart) and fixed it by just removing the hid_multitouch kernel module...
Without it, the touch pad works fine for me with Lubuntu 19.04 (with a 5.0.0 kernel)..."
1685937,2019-07-12 17:02:36 UTC,"It looks like I am currently hit by the very same issue: bought a chinese tablet, its keyboard+touchpad is detected as 1018:1006 and the touchpad is not working (only sending garbage on 3-finger gestures)."
1685937,2019-02-25 13:21:26 UTC,I'll pick USB_VENDOR_ID_1018 as its vendor name.
1685937,2019-01-03 07:11:05 UTC,Sorry for the belated response.
1685937,2018-06-26 05:11:05 UTC,Workaround tested and still scroll/multitouch work. Maybe should be pushed to the upstream?
1685937,2019-02-23 08:02:12 UTC,"I'm sending the patch till the end of the weekend. Is it ok using ""USB_VENDOR_ID_RIPOFF"" on the upstream, as I can't really find any vendor?"
1685937,2017-12-20 09:56:39 UTC,"I recently bought the Voyo Vbook 3 (CherryTrail Edition) which employs the same touchpad.
I have emailed Voyo but didn't receive an answer yet. But judging from some screenshots I found the touchpad might very well be a Synaptics device."
1685937,2017-05-03 04:43:07 UTC,I can't find 1008:1016 in hid drivers - it's probably a rebranded touchpad from another vendor. You need to ask the laptop vendor to get this information.
1685937,2017-04-25 17:41:58 UTC,The bug exists since I installed Ubuntu on that laptop. It still exists in 4.11-rc8.
1685937,2017-04-25 16:15:59 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1685937,2017-04-24 21:30:14 UTC,This change was made by a bot.
1685937,2018-01-02 06:23:16 UTC,Then it behaves like a mouse - you lose features like scroll/multitouch.
1685962,2018-03-09 13:31:55 UTC,This bug was fixed in the package python-launchpadlib - 1.10.6-1
1685962,2018-01-04 20:27:05 UTC,"I asked upstream about this, as well: https://github.com/jaraco/keyrings.alt/issues/23, and they confirmed that set_password expects a unicode string, not a base64 encoded string."
1685962,2018-03-08 11:37:57 UTC,Fixed in launchpadlib 1.10.6.
1685970,2018-01-30 14:29:19 UTC,This problem affects 16.04.2 after installing geonode 2.8 rc11  from ppa:geonode/testing
1685971,2020-08-04 17:07:36 UTC,"Pinta recognizes files by file extension. Unsupported file format error is expected.
I am closing this bug down as invalid."
1685974,2017-04-25 14:11:39 UTC,"Adding a note that, until a more elegant solution is created, one option for an Evergreen site might be to ensure that each notification method is contained in a separate trigger and then use the opt-in settings to allow patrons to opt in or out of that notification method."
1685984,2017-12-26 22:21:31 UTC,"This bug also affects me, but apt segfaults sometimes:"
1685984,2018-01-02 21:29:28 UTC,Looking at the original reporter's Df.txt file we can see that /boot is not mounted. This would cause the failure and is not something we can really fix.
1685984,2018-05-02 13:37:33 UTC,Disabling sophos antivitus has fixed the problem for me. See original comment at https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1739991/comments/3
1685984,2019-12-31 10:37:52 UTC,"See this duplicate: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1855259/comments/11. This is likely a bug in fanotify or Sophos, not dpkg."
1685984,2020-01-16 17:27:43 UTC,"FYI, someone in a Sohos forum posted a workaround that can help relieve some of the pain with the issues caused by the product until it's more thoroughly diagnosed and addressed: adding pre & post rules to temporarily deactivate the AV on-access scanner while updates take place. Quoting from the forum post:"
1685984,2017-12-26 22:18:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686007,2017-04-25 06:24:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459522"
1686007,2019-10-28 18:04:47 UTC,"Ryan, are you still working on this issue?"
1686007,2017-04-25 06:03:05 UTC,"The root cause is that the required option `emc_nas_server_pool` is not configured.
Please refer to https://docs.openstack.org/newton/config-reference/shared-file-systems/drivers/emc-unity-driver.html, and add this option to manila.conf."
1686007,2017-04-25 06:13:51 UTC,The option `emc_nas_server_pool` is renamed to `unity_server_meta_pool` from Ocata.
1686007,2017-05-24 07:39:31 UTC,"Change abandoned by Ryan Liang (<email address hidden>) on branch: master
Review: https://review.openstack.org/459522
Reason: Not to fix. It will affect other UT cases."
1686010,2019-07-08 23:52:00 UTC,"Fixed in revision 3a8f32c38095ea4d980c545c9983ac1e4e32ac0b
https://git.launchpad.net/kicad/patch/?id=3a8f32c38095ea4d980c545c9983ac1e4e32ac0b"
1686013,2017-04-26 13:49:15 UTC,"I have found a neutron provisioning block bug, I will postpone solving this problem and see how neutron suggests solving that problem
https://bugs.launchpad.net/neutron/+bug/1686405"
1686023,2017-09-12 17:15:16 UTC,"Now DOWN to ACTIVE is supported.
The remaining issue is admin_state_up=DOWN case.
For now there isn't strong requirement to support admin_state_up except tesmpest testcase,
making this low priority."
1686023,2018-03-14 19:36:39 UTC,Is this fixed since https://review.openstack.org/#/c/465463/ is merged?
1686025,2017-04-25 07:02:31 UTC,... though it does seem to work in most cases.
1686027,2019-12-10 15:26:10 UTC,"Does not occur in production, but since we support it we should test it."
1686028,2019-12-09 09:54:52 UTC,This is fixed.
1686039,2018-06-13 08:53:26 UTC,When can we expect the next version to be released to teh official repository?  There are a number of significant bug fixes that need to be rolled out please
1686039,2017-04-26 13:26:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686043,2018-10-18 20:20:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1766945, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1686043,2018-10-18 20:26:26 UTC,this bug is in fact most likely not a duplicate of bug #1766945 based on the timing of when it was reported.  Un-duping.
1686048,2017-04-25 09:31:01 UTC,This change was made by a bot.
1686048,2019-02-28 13:47:47 UTC,sent
1686048,2019-02-28 07:16:54 UTC,Please send to <email address hidden> CC <email address hidden> and <email address hidden>
1686048,2019-02-25 19:54:10 UTC,Confirmed the patch works on the Lenovo s21e-20 laptop with 5.0.0-rc8 kernel. Surely could be backported to other releases.
1686048,2019-02-25 19:52:30 UTC,"Created attachment 281341
add the ELAN0601 ID"
1686048,2019-02-25 15:26:19 UTC,"ah, sorry. This looks like an i2c elan touchpad issue. My apologies.
[vbatts@dhcp6-118 ~]$ dmesg | grep -i elan
[    2.442191] i2c_hid i2c-ELAN0601:00: i2c-ELAN0601:00 supply vdd not found, using dummy regulator"
1686048,2019-02-25 14:50:08 UTC,"This is still not working on 4.16.3 and 4.20.8 on Fedora
reading on https://alpha-labs.net/2015/08/lenovo-s21e-linux-and-the-touchpad/
it looks like there had been a fix floated for the hid-rmi module."
1686048,2017-09-20 13:45:40 UTC,"NOTE : Currently on 4.9.48-1-MANJARO
output was too long so I pastebinned it"
1686048,2017-09-19 13:37:32 UTC,Can you attach the output of `udevadm info -e` run as root?
1686048,2017-05-05 09:11:22 UTC,"Thanks,"
1686048,2017-05-05 09:05:12 UTC,"Created attachment 256221
dmesg"
1686048,2017-05-05 09:04:20 UTC,"Created attachment 256219
lshw"
1686048,2017-05-05 05:10:46 UTC,You need to file an upstream report then. It's at https://bugzilla.kernel.org/
1686048,2017-05-04 16:53:36 UTC,"I tested with the parameters one by one but it made no difference.
Touchpad isn't detected"
1686048,2017-05-04 04:50:02 UTC,"Can you test these kernel parameter, one by one:
i8042.nomux=1
i8042.reset=1
i8042.noloop=1
i8042.kbdreset=1
i8042.nopnp=1"
1686048,2017-04-25 20:49:25 UTC,"Mainline kernel didn't fix it.
Tagged and confirmed as per instructions"
1686048,2017-04-25 17:00:27 UTC,"This is a brand new install.
I'll test the new kernel when I have time (in a few hours)"
1686048,2017-04-25 16:15:38 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1686048,2019-03-20 20:25:41 UTC,"my fix for this has been merged into master and all stable branches back to v4.4
This issue can be closed now."
1686048,2017-05-05 09:07:17 UTC,"Created attachment 256223
devices"
1686058,2017-04-25 10:03:27 UTC,"i literally installed the os and the package, threw this in /etc/network/interfaces :"
1686058,2017-04-26 14:32:22 UTC,Hi! Thanks for looking into this and determining what was going on.
1686060,2017-04-26 17:05:34 UTC,I'll give this a look when I have a minute.
1686060,2017-04-26 17:08:00 UTC,Yeah the host/port there are used by the worker model to send notifies. The nsd backend should be moved to use a pattern similar to BIND with it's rndc host/port.
1686077,2017-04-25 14:01:10 UTC,This bug was fixed in the package gnome-settings-daemon - 3.24.1-0ubuntu3
1686077,2017-05-16 15:14:08 UTC,"Hello Jeremy, or anyone else affected,"
1686077,2017-05-23 00:04:53 UTC,I installed gnome-settings-daemon 3.24.2-0ubuntu0.1 on Ubuntu GNOME 17.04 and successfully completed this test case with d-feet.
1686077,2017-05-29 15:25:39 UTC,This bug was fixed in the package gnome-settings-daemon - 3.24.2-0ubuntu0.1
1686077,2017-05-29 15:25:57 UTC,"The verification of the Stable Release Update for gnome-settings-daemon has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1686079,2020-11-26 12:40:36 UTC,"Fixed in 2.6.0
https://github.com/asdf-format/asdf/pull/743"
1686079,2017-04-25 12:20:30 UTC,Filed upstream bug report
1686081,2018-03-15 16:07:21 UTC,"Daniel, I built & installed mutter & gnome-control-center with your patches but I still don't see the Touchpad Settings in my Ubuntu (on Xorg) session after installing xserver-xorg-input-synaptics."
1686081,2018-03-16 01:32:56 UTC,"Jeremy,"
1686081,2018-03-16 07:46:04 UTC,"Upstream bug for GDK's touchpad detection:
https://gitlab.gnome.org/GNOME/gtk/issues/97"
1686081,2018-03-16 08:30:41 UTC,Fix (v2) for gnome-control-center.
1686081,2018-03-16 08:42:33 UTC,Fix (with the new bug ID) for mutter.
1686081,2018-03-19 12:54:18 UTC,This bug was fixed in the package mutter - 3.28.0-2
1686081,2018-03-19 15:37:51 UTC,This bug was fixed in the package gnome-control-center - 1:3.28.0-0ubuntu1
1686081,2018-03-21 09:37:50 UTC,"Daniel,"
1686081,2018-03-21 01:41:24 UTC,"Alex,"
1686081,2018-03-21 01:42:53 UTC,"Also make sure you have Settings > Mouse & Touchpad > Touchpad > Tap to Click = ON
:)"
1686081,2018-03-15 08:20:14 UTC,"The attachment ""mutter_3.28.0-1ubuntu1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1686081,2018-03-22 01:22:46 UTC,"Alex,"
1686081,2018-03-22 10:36:40 UTC,"Daniel,"
1686081,2018-03-23 01:17:57 UTC,"We're overloading this bug with tangential discussion. So if you have any ongoing issues, please open a new bug."
1686081,2018-03-28 03:33:32 UTC,I am unsubscribing ubuntu-sponsors now since the patches here for bionic for gnome-control-center and mutter have been uploaded.
1686081,2018-03-20 10:04:15 UTC,Hello!
1686081,2018-03-15 06:23:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686081,2018-01-30 22:10:10 UTC,Awesome. Welcome to GNOME proper!
1686081,2018-03-15 06:19:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686081,2017-04-26 08:04:10 UTC,the only one that needs -synaptics is unity
1686081,2017-04-29 12:09:54 UTC,When testing both Xubuntu 17.10 daily ISOs (20170428) I found that tap and double tap on the touchpad to not be working. Scrolling was fine.
1686081,2017-04-29 21:35:40 UTC,tap-to-click isn't enabled by default in -libinput
1686081,2017-05-03 09:11:34 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1686081,2017-06-06 16:26:35 UTC,Added to Trello: https://trello.com/c/9GI3EFh2/122-bug1686081-if--synaptics-is-installed-gnome-mouse--touchpad-settings-doesnt-work
1686081,2017-06-27 22:24:13 UTC,Here's a request asking for gnome-control-center to warn somehow when the Synaptics driver is in use:
1686081,2017-09-19 00:33:09 UTC,"Xfce still needs -synaptics, addressed with http://bazaar.launchpad.net/~xubuntu-dev/ubuntu-seeds/xubuntu.artful/revision/1015"
1686081,2018-03-15 06:20:43 UTC,I'm merging bug 1733032 (which contains fixes) into this one.
1686081,2017-09-19 02:49:38 UTC,This bug was fixed in the package xubuntu-meta - 2.216
1686081,2018-01-29 21:00:05 UTC,"Hi, I just upgraded from 17.04 to 17.10.
I m running my ubuntu in Xorg mode.
After the upgrade (Dell Laptop with an Alps touchpad) there are no touchpad settings available at all (see attached screenshot).
The touchpad would work though, but I could not disable it at all. Pressing the Function-key+F3 would show the on-screen symbol of the disabled touchpad, but it wouldn't disable the touchpad.
At the moment I am using a bash script that is utilizing ""xinput --disable $device"" to enable/disable the touchpad."
1686081,2018-01-29 21:32:15 UTC,"@k-one, do the following:"
1686081,2018-01-29 22:13:41 UTC,"Hi Chris,"
1686081,2018-01-29 22:27:26 UTC,Hrmmmm ... curious.
1686081,2018-01-30 21:29:20 UTC,"Hm, some things you should not do in the middle of the night. :-("
1686081,2018-01-30 22:11:32 UTC,@me ... remember to use the <code> tags !!
1686081,2018-02-13 00:28:21 UTC,I experienced this problem when doing a *clean installation* of Ubuntu GNOME 16.04.3.  I confirmed that the synaptics driver was in use.  apt-get update; apt-get upgrade did not resolve the problem.
1686081,2017-10-25 08:09:20 UTC,"After upgrading my laptop to 17.10 I had right click functionality on my touchpad. Then it was gone, some other people also reported this on askubuntu but I could not find a related bug. After finding this bug I installed xserver-xorg-input-synaptics and right click on my touchpad is back. So the disappearing right click functionality is a problem in libinput?"
1686083,2017-04-25 22:57:58 UTC,Thanks David!
1686083,2017-04-25 22:50:17 UTC,"It looks like the Vala bindings fixed this problem, though now I'm trying to work out how to get this to compile with both the old and new bindings..."
1686083,2017-04-25 22:56:44 UTC,From the Vala NEWS file:
1686084,2017-05-13 17:09:22 UTC,Same here - bug seems to affect only 0.9.13-2 but not 0.9.13-1.2 - but I had not the chance to test x11vnc v0.9.13-1.2 myself.
1686084,2020-03-23 13:25:48 UTC,"-noxrecord workaround works, also in 0.9.16 the problem seem fixed."
1686084,2020-02-28 16:13:57 UTC,according to https://github.com/LibVNC/x11vnc/issues/61  there is a workaround to use option -noxrecord
1686084,2019-08-24 15:46:24 UTC,"I'm seeing it consistently on 18.04.3 LTS. Fairly easy to reproduce by installing idle in the machine running x11vnc, starting idle and clicking in any of the menus. 9 out of 10 times it crashes x11vnc."
1686084,2019-08-23 11:26:12 UTC,0.9.13 crashes in Netbeans UI editor when [...] button in Properties pressed with a big chance.
1686084,2019-04-15 15:14:59 UTC,I confirm that  0.9.13-3 is affected. This seems to be the latest available version at Ubuntu 18.04.2 LTS.
1686084,2019-03-18 18:41:13 UTC,"I upgraded to Ubuntu-18.04.2 (up-to-date as of 2019/03/18) and keep stumbling on this crash.
It's a severe issues as x11vnc is almost unusable (crashes every few minutes)."
1686084,2018-12-05 22:37:55 UTC,Yes I can confirm - no more crashes
1686084,2018-11-30 15:12:17 UTC,"""How does one get the x11vnc-data and x11vnc.deb packages from Cosmic to install on the Bionic?"""
1686084,2018-11-29 19:55:39 UTC,How does one get the x11vnc-data and x11vnc.deb packages from Cosmic to install on the Bionic?
1686084,2018-07-23 12:08:32 UTC,I verified by installing x11vnc-data and x11vnc  .deb packages from Cosmic (over the already installed Bionic version) and there's no more crash.
1686084,2018-07-23 11:54:25 UTC,"I mean, 0.9.13-6 :)"
1686084,2018-07-23 11:53:46 UTC,"This is fixed in 0.19.13-6
The fix is in Cosmic, but this would need to be backported to Bionic"
1686084,2018-06-24 17:08:49 UTC,"What the hell, this bug is over a year old, there are patches for it, why isn't it fixed in bionic?"
1686084,2018-05-18 13:31:35 UTC,https://gist.github.com/mangoliou/407d6a39a60d128610c20c4143f39f0d workaround works on a fresh Ubuntu 18.04 install
1686084,2018-03-26 10:09:09 UTC,Also happening in 18.04 beta 1.
1686084,2018-01-30 17:02:12 UTC,This is happening on Artful Aardvark too.
1686084,2017-08-30 13:10:43 UTC,Hello!
1686084,2017-08-13 03:59:13 UTC,"Experienced a lot of the stack smashing errors  using qt-wine v1.3.3 over VNC connection from my Android, I compiled and installed 0.9.14.1-dev now and no errors. Thanks"
1686084,2017-07-19 04:34:12 UTC,"I've created x11vnc package adding the patches from https://github.com/LibVNC/x11vnc/pull/25 and works fine.
I'm attaching debdiff."
1686084,2017-05-13 17:42:55 UTC,I installed now 0.9.14.1-dev by use of the instructions outlined in the link below - that works (until now no crashes).
1686084,2017-05-13 17:12:07 UTC,Regaring 0.9.13-1.2 see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859213
1686084,2017-05-13 17:10:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686086,2019-10-16 16:12:15 UTC,TL;DR version:
1686086,2019-10-16 14:43:49 UTC,"An upload of simplestreams to xenial-proposed has been rejected from the upload queue for the following reason: ""See https://bugs.launchpad.net/charms/+source/glance-simplestreams-sync/+bug/1611987/comments/21""."
1686086,2019-09-20 09:50:26 UTC,"For Xenial SRU, please read summary at:"
1686086,2017-11-02 19:12:14 UTC,"I'm pretty sure this is fixed in commit
 3609b4f1129760ad6141de5f5bbc91424f3270ab
which is in
16.0.0.0b1"
1686086,2018-06-25 14:52:54 UTC,"This bug is believed to be fixed in simplestreams in version 0.1.0. If this is still a problem for you, please make a comment and set the state back to New"
1686086,2018-03-16 19:48:19 UTC,This bug was fixed in the package simplestreams - 0.1.0~bzr459-0ubuntu1
1686086,2018-10-16 15:03:54 UTC,"does anyone have a reproducer for this bug?, I've been having a hard time trying to come up with one on my own."
1686087,2017-04-27 16:34:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686087,2017-05-05 15:26:11 UTC,"I realize that ""rebuild"" isn't sufficient here. The thing I hear is that there was a mistaken assumption about VA size in Thunderbird and there were fixes in upstream firefox / js engine for it and this part was not rebuilt when Thunderbird was rebuilt for this release."
1686087,2017-05-05 15:29:22 UTC,"Regardless of whether the fix maybe a rebuild or not , the thunderbird package is completely borked on 17.04 on arm64."
1686087,2017-05-05 15:35:07 UTC,Ok on doing further research I'm reliably informed that this patch
1686087,2017-05-11 13:08:11 UTC,"We suspect this should be fixed in the upcoming releases of Thundrbird 52.x ... If you want a sneak peek, you can have a poke at https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages but I'd expect those packages (or newer) to hit the archive shortly."
1686089,2017-04-25 16:26:50 UTC,"The attachment ""k3b.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1686089,2017-05-10 06:26:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686099,2017-05-17 06:50:23 UTC,@Joseph Salisbury (jsalisbury)
1686099,2017-05-17 10:57:52 UTC,"@MichaelB, The commit is in Xenial master-next.  It has not been tagged for a specific version.  It looks like it will be in 4.4.0-80."
1686099,2017-05-17 14:19:29 UTC,I built a Yakkety test kernel with a cherry pick of commit 62a6cfddcc.  The test kernel can be downloaded from:
1686099,2017-06-14 09:11:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1686099,2017-05-22 09:08:11 UTC,@Joseph Salisbury (jsalisbury)
1686099,2017-05-22 12:36:44 UTC,"Hi,
I also ran the kernel for the past three days, and no
connection spam appeared."
1686099,2017-05-16 17:06:19 UTC,This has been fixed upstream by the following commit:
1686099,2017-06-28 16:34:43 UTC,This bug was fixed in the package linux - 4.8.0-58.63
1686099,2017-06-15 15:07:41 UTC,"Uhm, sorry too late in the evening...
What I wanted to say is: I tried the proposed kernel (4.8.0-55-generic #58~16.04.1-Ubuntu)
the whole day long, and NO connection spam appeared. This means the fix seems to work.
As I don't know how to set the tag, or have insufficient rights, please modify the tag
to verification-done-yakkety."
1686099,2017-06-15 15:10:45 UTC,"Is ok for me, 4.8.0-55-generic #58~16.04.1-Ubuntu SMP
No more flood with this kernel version."
1686099,2017-06-23 13:06:28 UTC,when the problem will be solved in a stable kernel ?
1686099,2017-06-28 11:07:24 UTC,"I also confirm that the issue is here with
4.8.0-56-generic #61~16.04.1-Ubuntu"
1686099,2017-06-28 17:23:35 UTC,"Hi, it may have been fixed in 16.10 yakkety 4.8.0-58.63, but 16.04.1 xenial (LTS) still has 4.8.0-56 as latest on one of my boxes, as woldemar and Andrij Abyzov report above."
1686099,2017-06-28 17:30:59 UTC,(A couple of other boxes with 16.04 (not 16.04.1) xenial have 4.4.0-81 as latest).
1686099,2017-09-01 10:13:39 UTC,"Hello, is it going to appear in 4.4? I'm getting tired of running 4.4.0-66 (jk works ok but still would prefer to update)."
1686099,2017-06-15 15:02:06 UTC,"Had 4.8.0-55-generic #58~16.04.1-Ubuntu the whole day, now connection spam appeared."
1686099,2017-05-16 11:57:09 UTC,4.8.0-52-generic #55~16.04.1-Ubuntu released today (2017-05-16) not ok - The bug is still here too! Please fix this quickly because my company network are overloaded because of this bug. Thanks!
1686099,2017-05-01 13:18:58 UTC,I failed to mention my kernel version: 4.4.0-75-generic #96-Ubuntu SMP
1686099,2017-05-04 13:03:08 UTC,Fix released in what version?
1686099,2017-04-25 14:06:14 UTC,The system is behind a firewall so I can't run apport-collect directly.  Is there a way to run it to a file and upload separately?
1686099,2017-04-25 14:07:43 UTC,"and the ""apport-bug linux"" attachment isn't sufficient?"
1686099,2017-04-25 16:14:38 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1686099,2017-04-25 17:54:05 UTC,Maybe.  This is a production system so I'll have to schedule something.
1686099,2017-04-30 12:35:33 UTC,"I've got the same flood here, on port 445, across my LAN. If I block that port, I get a flood instead via port 139."
1686099,2017-04-30 12:43:50 UTC,"The screenshot above is from traffic between the two RPis, which run Raspbian (RPi + Debian)."
1686099,2017-05-01 12:55:49 UTC,I've got the same problem from a number of Ubuntu 16.04 machines.  They're running on Hyper-V and so they've got the following installed as per Microsoft recommendations:
1686099,2017-05-01 13:13:24 UTC,"As a workaround, I've added a cron job that does a directory listing on the share every minute.  It has not stopped the flood but it seems to be allowing the cifs client to stay connected for a longer period of time (a major annoyance when the application relies on that share being available.)"
1686099,2017-05-01 13:41:18 UTC,"My workaround may have added some time, but eventually the share dismounted :("
1686099,2017-05-01 15:48:27 UTC,I did try to install the upstream kernel linux-image-4.11.0-041100rc8-generic_4.11.0-041100rc8.201704232131_amd64.deb and linux-headers-4.11.0-041100rc8-generic_4.11.0-041100rc8.201704232131_amd64.deb but unfortunately the system barely boots and the networking is messed up after the change.  I can't tell if the cifs problem is any better.
1686099,2017-05-01 16:45:10 UTC,"If you reboot (or unmount/remount) with the ""ls every minute"" cron job active, it should prevent the timeout on the share and not reach the keep-alive echo that starts the flood.  I think it is about the 15-minute mark (of inactivity) where the client starts the echo flood."
1686099,2017-05-01 19:12:57 UTC,I downgraded to linux-image-4.4.0-66-generic and no longer have the flooding issue.
1686099,2017-05-02 11:39:39 UTC,"I have 5 desktop on Ubuntu 16.04 with various official kernel 4.4, 4.8, 4.10. All this desktop are connected via CIFS to a Windows Server 2008 R2 for a simple shared folder."
1686099,2017-05-02 14:19:07 UTC,At https://bugzilla.kernel.org/show_bug.cgi?id=194531 Steve French writes:
1686099,2017-05-02 14:55:58 UTC,"At GitHub raspberrypi/linux, 6by9 writes: ""[The fix] was applied to the 4.4 tree 5 days ago, so should be in 4.4.64 and later. When Ubuntu bump the kernel in their repos is totally up to them."""
1686099,2017-04-25 14:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1686099,2017-05-11 10:43:55 UTC,"4.4.0-77-generic #98-Ubuntu, the bug is still here."
1686111,2018-01-17 16:52:48 UTC,"Indeed, it does not seems to work out of the box."
1686111,2018-03-09 15:27:01 UTC,"Putting the code to src/ folder looks a good practice, and it is sad that I can't use pbr for such project structure :-(."
1686111,2018-03-09 15:49:40 UTC,Steps to reproduce:
1686111,2018-07-23 22:17:29 UTC,"I have noticed this also.  If you run a 'pip install .' in the git checked out directory it doesn't work...but if you run 'python setup.py install' it does work.  It happens at. Low level as I put debug statements in setuptools, distribute, and pbr.  And dist itself finds no packages with 'has_pure_python'.  And indeed it finds no packages in general.  I'll perform more debugging. This is high on my list because I want the other machinery provided by pbr."
1686111,2018-07-25 20:15:31 UTC,Sorry for the terrible description above.  This is still a real problem.  But I found a way to still get the functionality of pbr to work while still using setuptools properly.
1686116,2017-07-06 16:19:39 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/481137"
1686116,2017-07-06 16:19:51 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/481138"
1686116,2017-07-06 16:20:04 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/481139"
1686116,2017-07-28 07:41:09 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1686116,2017-08-11 17:53:21 UTC,"Reviewed:  https://review.openstack.org/481135
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e1092323e216203b7a7004f787c4061f97fad355
Submitter: Jenkins
Branch:    stable/ocata"
1686116,2017-08-12 11:04:24 UTC,"Reviewed:  https://review.openstack.org/481137
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=34a0ade4cc15f0bb2303c461b99bd481ed907a0f
Submitter: Jenkins
Branch:    stable/ocata"
1686116,2017-08-11 23:24:16 UTC,"Reviewed:  https://review.openstack.org/481136
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=88927df9288b42b2f8f8f5b33f63b5a7530a863f
Submitter: Jenkins
Branch:    stable/ocata"
1686116,2017-08-12 11:06:17 UTC,"Reviewed:  https://review.openstack.org/481138
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=70ede864e74460d3cfde1c99c6a2879146b52dc4
Submitter: Jenkins
Branch:    stable/ocata"
1686116,2017-08-14 05:06:59 UTC,"Reviewed:  https://review.openstack.org/481139
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=be0f76ae6429e8d83fd99bd6c9365dfcd4702f42
Submitter: Jenkins
Branch:    stable/ocata"
1686116,2017-08-22 11:39:21 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1686116,2017-07-06 16:19:27 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/481136"
1686116,2017-07-06 16:19:13 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/481135"
1686116,2017-06-07 18:56:42 UTC,"Reviewed:  https://review.openstack.org/459737
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=724ca8227a23a918d1810f866af661ac2a0730a3
Submitter: Jenkins
Branch:    master"
1686116,2017-07-06 15:44:34 UTC,Would it be possible to backport the patch to newton?
1686116,2017-04-25 15:04:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459737"
1686116,2017-04-25 15:04:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459738"
1686116,2017-04-25 15:04:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459739"
1686116,2017-04-25 15:04:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459740"
1686116,2017-04-25 15:04:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459741"
1686116,2017-07-06 16:03:11 UTC,"I don't think it's something possible, i mean the release management does not allow to backport fix in 2 releases before or that should be related to the security."
1686116,2017-06-07 19:18:30 UTC,"Reviewed:  https://review.openstack.org/459739
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=215add554adb88d9ded4267f07968d8a7d166a45
Submitter: Jenkins
Branch:    master"
1686116,2017-07-03 18:46:12 UTC,"Reviewed:  https://review.openstack.org/459741
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c25629f85feb53b5be0347f68c43b3b55fb9f137
Submitter: Jenkins
Branch:    master"
1686116,2017-06-07 19:17:02 UTC,"Reviewed:  https://review.openstack.org/459738
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=74ece03d70fac926a5e25eb0663da098e44cbaa2
Submitter: Jenkins
Branch:    master"
1686116,2017-06-08 21:51:14 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1686116,2017-07-03 18:45:36 UTC,"Reviewed:  https://review.openstack.org/459740
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb343c402296c109af49bfca2f909680ca38a72b
Submitter: Jenkins
Branch:    master"
1686122,2017-04-25 15:11:28 UTC,"Submitted code review for this bug in here
https://review.openstack.org/#/c/459745/"
1686125,2017-06-29 09:00:39 UTC,"Please be more specific - what did you try, what did you expect, what happened? And where? Also, the packages website is in general not the place to install software from, it's about getting information about software.  Please use the software center for installing applications."
1686134,2017-04-25 18:04:31 UTC,"reproduced on Windows 10, Inkscape 0.92.1 r15371"
1686134,2017-04-25 20:10:55 UTC,"Thanks for testing, Alvin!"
1686170,2020-04-26 07:17:47 UTC,I had the same problem when I tried to run [boot.asm](https://github.com/yifengyou/The-design-and-implementation-of-a-64-bit-os/blob/master/code/c03/1/boot.asm).
1686170,2019-12-27 03:08:03 UTC,I had the same issue.  My workaround is to force the target description to be loaded from a local xml file where the architecture tag is i8086.  I took the one that was sent over the network from the server to the client and changed the architecture tag from i386 to i8086 and also the size of the i386_efer flags from 8 to 4.
1686170,2017-07-10 16:55:44 UTC,"Apparently none of the 32bit x86 modes are supported in 2.9 version of qemu-system-x86_64.  I realize the desire to simplify the code, and separate i386 from x86_64, but x86_64 really does need to support all the modes in which the processor can operate.  True that for major operating systems the processor is only briefly in any 32bit mode, but for boot ROM and boot loader work, and non-mainstream kernels we still very much need 32bit support *in* the x86_64 qemu."
1686170,2018-05-12 12:10:29 UTC,"Hi,
are there any updates on this issue?"
1686170,2017-04-26 15:24:14 UTC,"If it is decided to retain the change, please do consider adding a commandline option to enable debugging Real mode code after `set architecture i8086`, even if this requires the GDB workaround previously mentioned. Thanks in advance."
1686173,2020-10-14 18:11:39 UTC,This looks like the same issue - could you try installing the latest version of Mono from https://www.mono-project.com/download/stable/#download-lin?
1686173,2017-05-18 02:30:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686173,2017-08-05 20:08:50 UTC,"Interestingly, I can't get it to crash when I run `pinta` in a terminal. If I use the desktop launcher, however, it crashes if I try to do anything more than ""save as."""
1686173,2017-08-15 10:44:58 UTC,"For me the error starts when I press the OPEN FILE button (or inside the menu) on Pinta to open an image, it opens up and then the app crashes almost immediately. Instead, if I go direct to the image on directory and Right Click it selecting to open in Pinta, the app work as expected. Dragging the file inside the opened app will work as well."
1686173,2017-09-02 11:31:59 UTC,"Save fails for me, if start from the terminal I get"
1686173,2017-09-11 18:58:55 UTC,"When I open picture and try to select area, I'm getting the same error:"
1686173,2018-01-26 09:36:58 UTC,I had a related issue (https://bugs.launchpad.net/pinta/+bug/1720472) and updating \Mono to 5.4.1 using their PPA (http://www.mono-project.com/download/) resolved the issue.
1686173,2018-08-12 08:10:28 UTC,"Pinta 1.6 on Ubuntu 18.04.1
Pinta Crashed with *** Error in `/usr/bin/mono': free(): invalid pointer:
Followed #7 twdkeule and added Mono PPA, updated to
Mono JIT compiler version 5.14.0.177 (tarball Mon Aug  6 09:07:45 UTC 2018)
Issues resolved - Pinta stable."
1686173,2019-10-25 17:12:53 UTC,"The fix in the last version worked for me, using Debian 9.11 and Pinta 1.6. Can this then be closed and moved over to a Mono bug report? Or can it simply be closed, because the latest Mono version already fixes it?"
1686173,2020-10-13 08:36:54 UTC,I just got a SIGSEGV from using pinta 1.6-2 the first time.
1686185,2017-06-01 02:59:12 UTC,I'm curious if this still happens as the code should be using elements from the state pool.
1686186,2019-12-14 12:17:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686189,2020-01-03 19:13:12 UTC,Same fault by using VGA instead of DP.
1686189,2017-06-15 03:00:20 UTC,"Hi, please try Linux kernel version 4.4.71, 4.8, 4.9 at [1] so I can know the what exact patch series fixed the issue."
1686189,2017-06-21 10:24:07 UTC,"Thanks for the testing.
Can you also try 4.4.71, 4.8, 4.9 as #35 states?"
1686189,2017-06-14 15:24:15 UTC,@Kai-Heng
1686189,2017-06-27 05:20:14 UTC,"Moritz,"
1686189,2017-06-30 16:25:28 UTC,"Sorry for the delay, I tried:
linux-image-4.4.0-83-generic doesn't work
linux-image-4.8.0-040800-generic  doesn't work
linux-image-4.10.0-041000-generic works
linux-image-4.11.0-041100-generic works"
1686189,2017-06-30 19:50:38 UTC,"@Giacomo Orlandi, I experience what you describe since day one with Ubuntu 16.04 (DELL + USB DOCK). My work around is to disable the flickering screen and revert the settings."
1686189,2017-07-03 10:38:27 UTC,@Kai-Heng:
1686189,2017-07-03 21:58:04 UTC,"The drm nightly kernel works for me (4.12.0-994-lowlatency). However, I do not have WLAN."
1686189,2017-07-03 23:24:34 UTC,"I tried Ubuntu 17.04, still the same issue."
1686189,2017-09-20 07:19:36 UTC,"Same problem here, affects me on 4.4.0-93-generic. Dell E7450 with docking station and 2 monitors, used to work flawlessly on 14.04."
1686189,2017-10-19 09:47:33 UTC,It should be fixed in later 4.4 kernel [1]
1686189,2017-10-20 09:19:21 UTC,"@Kai-Heng: the problem is fixed here using your 4.4.0-99 version on my Dell Latitude E7470 with Skylake.
Well it's buggy like on 4.4.0-72, after loggin both screens go black, but I have my workaround works again. If I switch to text mode (Ctrl+Alt+F1) and back (Alt+F7) both screens work"
1686189,2017-10-20 09:49:13 UTC,Thanks for your testing.
1686189,2017-10-20 17:09:27 UTC,"@Kai-Heng thanks a lot, using the modesetting driver helped!
I just read that using the Intel driver is not recommended anymore on newer systems, I didn't know that."
1686189,2017-11-09 10:04:18 UTC,"@Kai-Heng I'm running that now it seems to be working well:
$ uname -a
Linux giacomo-awin-latitude 4.4.0-100-generic #123-Ubuntu SMP Thu Nov 2 10:16:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1686189,2017-11-10 03:21:01 UTC,"> On 9 Nov 2017, at 6:04 PM, Giacomo Orlandi <email address hidden> wrote:
>
> @Kai-Heng I'm running that now it seems to be working well:
> $ uname -a
> Linux giacomo-awin-latitude 4.4.0-100-generic #123-Ubuntu SMP Thu Nov 2 10:16:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>
>
> I see many changes in the changelog, what's the patch that fixed it?
"
1686189,2017-11-19 23:52:50 UTC,Are we going to see this released in xenial-main?
1686189,2018-03-07 15:47:19 UTC,"Hi there,"
1686189,2018-03-08 03:19:15 UTC,"Do you have package ""xserver-xorg-video-intel""?"
1686189,2018-03-08 14:52:04 UTC,"Yes, I do."
1686189,2018-03-08 15:00:02 UTC,THis is the result with
1686189,2018-03-09 03:09:53 UTC,Please see if this issue can be solved after remove xserver-xorg-video-intel.
1686189,2018-03-09 10:55:04 UTC,I tried to remove but if I do also this packeges will e removed
1686189,2018-03-13 03:37:26 UTC,You can also modify the xorg.conf to prioritize modesetting driver over intel.
1686189,2018-03-15 15:45:04 UTC,quick update.
1686189,2020-01-03 18:54:48 UTC,"I'm using a HP Pro X2 612 G1. It has VGA compatible controller: Intel Corporation Device 0a1e (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 221b. The external Monitor (connected to DisplayPort) is recognized, but it the grafics is distorted and flickering. There is no hardware issue, because the same configuration is working with windows 10."
1686189,2017-11-09 06:18:52 UTC,Linux kernel v4.4.0-100 in xenial-proposed contains the fix. Please give it a try.
1686189,2017-06-14 11:36:25 UTC,"E7470 on Dell dock 0PDXXF here as well. LCD(eDP-1)+DVI(DP-1-1)+VGA(DP-1-3).
Intel graphics only."
1686189,2017-06-26 15:56:47 UTC,Still the same issue:
1686189,2017-06-13 07:37:33 UTC,"Also, please try 4.8 and 4.9."
1686189,2017-06-13 08:56:14 UTC,"Last but not least, try latest 4.4 stable kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.71/"
1686189,2017-04-26 08:30:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686189,2017-04-26 08:32:59 UTC,"I have the same problem on 16.04.2 Xenial since upgrading the Kernel to 4.4.0-75 yesterday.
Booting the the older kernel version 4.4.0-72-generic seems to be a workaround."
1686189,2017-04-26 12:53:08 UTC,"Sorry for spamming everyone, as this started happening after a kernel upgrade is it a Kernel bug?"
1686189,2017-04-27 07:02:26 UTC,@naveenkumarmula do you mind trying to boot with the previous kernel version and see if that fixes it for you too? You should be able to choose the Kernel to start at boot.
1686189,2017-05-02 09:09:10 UTC,"I have this problem since linux-image-4.4.0-75
linux-image-4.4.0-77 is also affected.
linux-image-4.4.0-72 works"
1686189,2017-05-02 09:30:16 UTC,This change was made by a bot.
1686189,2017-05-08 12:14:58 UTC,"Confirming the same issue - 4.4.0-72 works on Dell E7470 with intel, 4.4.0-77 doesn't.
Seems like a kernel bug.
xrandr showing screens but displays fall into sleep whatever I try.
plymouth not affected, only X."
1686189,2017-05-08 19:30:06 UTC,Confirming the same issues - 4.4.0-77 bugs and wont display external screens on Dell E7250.  Can run with 4.4.0-72 kernel and everything is just fine.
1686189,2017-05-15 02:11:29 UTC,can confirm what others have reported above with 16.04
1686189,2017-05-17 00:35:05 UTC,Same problem here. Reverting to 4.4.0-72 fixed the issue.
1686189,2017-05-18 07:23:42 UTC,"Can confirm nvidia with and without intel profile get the same problem with 4.4.0-78-generic
same case was with 4.4.0-77-generic."
1686189,2017-05-24 01:54:50 UTC,"there was some improvement with 4.4.0-78 but still is ongoing - Ubuntu can't wake a suspended monitor, doesn't remember monitors positions"
1686189,2017-05-31 16:37:13 UTC,"For me, 4.4.0-78 actually made it worse on my Dell Latitude E7250 to the point where I had to downgrade to 4.4.0-72 in order to be able to use external monitors again."
1686189,2017-06-06 05:57:29 UTC,"Maybe graphics driver doesn't exist at all?
Can you attach output of `dpkg -l | grep linux-image`?"
1686189,2017-06-20 15:32:14 UTC,@Kai-Heng
1686189,2017-06-06 20:52:12 UTC,"@kaihengfeng this is my output of that command:
~ $ dpkg -l | grep linux-image
hi  linux-image-4.4.0-72-generic                  4.4.0-72.93                                          amd64        Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii  linux-image-4.4.0-78-generic                  4.4.0-78.99                                          amd64        Linux kernel image for version 4.4.0 on 64 bit x86 SMP
hi  linux-image-extra-4.4.0-72-generic            4.4.0-72.93                                          amd64        Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii  linux-image-extra-4.4.0-78-generic            4.4.0-78.99                                          amd64        Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii  linux-image-generic                           4.4.0.78.84                                          amd64        Generic Linux kernel image"
1686189,2017-06-13 02:27:49 UTC,"@Kai-Heng, if that can help this is my configuration below:
-Dell Latitude E7450 on a Dell docking station with two screens (1 VGA , the other
-Intel® Core™ i7-5600U CPU @ 2.60GHz × 4
-GeForce 840M/PCIe/SSE2"
1686189,2017-06-06 08:58:09 UTC,"Same thing here, 4.4.0-78 does not solve the problem at all, I barely can work, is there going to be any attempt to fix this soon?"
1686189,2017-06-12 18:32:17 UTC,@Kai-Heng I use a Dell E-Port Plus.
1686189,2017-06-09 15:23:31 UTC,"NVidia setup is also including a second intel card (for power saving mode), but yes I mainly try to use NVidia profile (kernel used to complain about the intel card just like it is in your case)."
1686189,2017-06-08 14:48:53 UTC,"Not sure if this is a coincidence or what, but I'm also using a Dell Docking Station / Port replicator."
1686189,2017-06-08 14:38:12 UTC,"Version 4.4.0-72-generic seems to be the last version that works for everyone here, on different systems. I renamed this bug to mention Intel, but Shay Perlstein above had the same problem on NVidia."
1686189,2017-06-09 06:36:19 UTC,"@Robert @Giacomo
Are Linux kernel 4.4.0-73 ~ 4.4.0-77 all failed to work?
Can you paste the output of `lsmod | grep i915` here?
Also, which docking station do you use? I have an USB type-C docking station (TB15) at my hand, but I am not sure if you use this one..."
1686189,2017-06-08 12:47:03 UTC,"I jumped to 4.10.1-041001-generic since I failed to go back to 4.4.0-72 which used to work, everything is working again as it should without any problem, I am now using the latest nvidia driver 381.22 (, also 378.13 worked perfectly fine).
The kernel version definitely makes a difference"
1686189,2017-06-08 04:36:18 UTC,"@Giacomo
On Xenial's linux 4.4, Skylake uses i915_bpo instead of i915.
Please file a separate bug for this."
1686189,2017-06-07 14:04:46 UTC,"I am having the same issues even with the newer Kernel, 4.4.0-79-generic."
1686189,2017-06-07 12:01:59 UTC,"The problem is only reproducible with some Kernel versions, how can it not be related to the Kernel?
I actually have a Sky Lake, not a Haswell like the reporter.
So maybe one of those commits for Baytrail caused a regression on other Intel Graphics processors?"
1686189,2017-06-07 02:45:41 UTC,"Most kernel drivers are in extra package, i.e. linux-image-extra-4.4.0-78-generic."
1686189,2017-06-08 13:58:52 UTC,"@Kai-Heng
4.4.0-72-generic"
1686189,2017-06-13 02:58:17 UTC,"Can you try if these kernel works?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/"
1686190,2017-07-01 06:34:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686190,2017-07-01 06:35:57 UTC,I have the same issue on Arch GNOME 3.24. I guess this may be a GNOME bug?
1686190,2017-10-20 18:11:03 UTC,"About the same happens on Ubuntu 17.10 wayland. After logging in account, I see Dropbox icon, but clicking on it has no effect at all until I double click it. Then undecorated white menu appears at current mouse pointer position and there is no way to close it apart from clicking some of the menu items. After that clicking Dropbox icon starts working and a decorated menu is displayed."
1686190,2018-05-19 21:16:30 UTC,This also happens on Ubuntu 18.04.
1686192,2017-04-26 16:10:12 UTC,Looks like they use a mailing list for bug reports:
1686192,2017-04-26 15:17:24 UTC,I am happy to report this bug upstream however I've been unable to find a bug tracker for DNSMASQ specifically.
1686192,2017-04-26 14:57:56 UTC,Hi! Thanks for reporting this and including your configuration file. Given you are seeing this across distros I think this warrants an upstream report. Would you be willing to file something upstream and provide a link back in this bug report? Thanks!
1686193,2017-04-25 22:17:50 UTC,"We'll need to be a bit careful about forum posts though I think. In contrast to a person's portfolio and files contained within it, forum posts are often part of a conversation and deleting them could destroy the conversation. I wonder, if that may need to be an option when  the user is deleted. If forum posts are to be deleted, then there should be a placeholder post saying that the post was deleted rather than making it vanish altogether (like we already do when an admin deletes a post that is not the last in a conversation)."
1686203,2021-01-09 22:42:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1273534, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1686204,2017-08-05 20:56:29 UTC,"Hi nondecidibile,"
1686206,2017-06-27 15:57:39 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1686239,2017-04-28 21:19:50 UTC,"We need a bit more information on this, it is likely caused by a) the cloud using Nova-network and not Neutron, and b) python-novaclient >= 8.0 is installed.  Can you confirm either or both of these?"
1686239,2017-04-28 23:35:46 UTC,"pip list | grep python-novaclient
python-novaclient (8.0.0)"
1686239,2017-05-04 20:55:46 UTC,"Confirmed fixed with python-openstackclient (3.11.0), please close at your leisure."
1686248,2019-09-19 12:03:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1686249,2017-04-29 06:39:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686252,2019-08-13 08:31:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686252,2019-08-13 08:31:04 UTC,I encounter the same problem with a 18.04.02 LTS version with a OpenVPN 2.4.4.
1686252,2017-05-24 22:55:34 UTC,"Network manager has the option to automatically connect a VPN while a wifi connection is active, it is expected for NM to maintain this auto-connection however it appears unable to do so.
Adding to that, the OpenVPN service has ping timers for restarting and terminating VPN connections, however these are not visible in kubuntu due to another bug;
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1693371"
1686252,2017-05-23 18:49:13 UTC,I'm not aware that NetworkManager currently does any kind of automatic reconnection in case of failure of a VPN. The only thing it could possibly do is bringing up a VPN automatically when some wifi network gets connected.
1686252,2017-04-26 01:07:36 UTC,"Possibly depends on;
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1686254"
1686252,2017-04-26 01:01:03 UTC,"Personal encrypted passwords for the certificates are in use, no manual authorisation required, NM is free to activate the OpenVPN connection whenever possible yet does not."
1686257,2017-05-16 23:06:12 UTC,"Johon, please open a new bug for your issue by running ""ubuntu-bug gdm3"" . Your issue is probably with the 3.24.1 upgrade (LP: #1685500) and not with this particular bugfix."
1686257,2017-05-16 22:12:32 UTC,"Works-for-me after dist-upgrade using Ubuntu Gnome 17.04 64-bit and Intel®
HD Graphics 520 (Skylake GT2)."
1686257,2017-05-16 15:37:57 UTC,The update to gdm3 - 3.24.1-0ubuntu0.1 is just crap.
1686257,2017-05-15 16:02:32 UTC,This bug was fixed in the package gdm3 - 3.18.3-0ubuntu2.1
1686257,2017-05-15 16:02:17 UTC,This bug was fixed in the package gdm3 - 3.20.1-1ubuntu2.1
1686257,2017-05-15 16:01:51 UTC,"The verification of the Stable Release Update for gdm3 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1686257,2017-05-15 16:01:42 UTC,This bug was fixed in the package gdm3 - 3.24.1-0ubuntu0.1
1686257,2017-05-10 02:46:37 UTC,"I tested this from both Unity and Ubuntu GNOME.
3.18.3-0ubuntu2.1 on Ubuntu 16.04 LTS
3.20.1-1ubuntu2.1 on Ubuntu 16.10
3.24.1-0ubuntu0.1 on Ubuntu 17.04
I verified that after rebooting into gdm, I could successfully log in to both Unity and GNOME Shell."
1686257,2017-05-11 17:55:39 UTC,@jbicha:  yeah ... I just tried to reproduce in a gnome-boxes clean install of ubuntu-16.04.2-x86_64 to no avail. gnome-session-wayland is _not_ required.
1686257,2017-04-26 20:38:49 UTC,This bug was fixed in the package gdm3 - 3.24.1-0ubuntu2
1686257,2017-05-04 18:06:24 UTC,"Hello Jeremy, or anyone else affected,"
1686257,2017-05-08 23:22:49 UTC,Need to have gdm3 depend on:
1686257,2017-05-04 18:10:43 UTC,"Hello Jeremy, or anyone else affected,"
1686257,2017-05-04 18:09:38 UTC,"Hello Jeremy, or anyone else affected,"
1686265,2017-04-26 05:07:10 UTC,"This error is caused by duplicate settings about ""enable_plugin watcher"" in both /devstack/local.conf and /opt/stack/watcher-dashboard/devstack/settings. One solution to this error can be: mv watcher-dashboard/devstack/settings watcher-dashboard/devstack/local_conf.example"
1686265,2017-07-27 13:33:54 UTC,This issue was fixed in the openstack/watcher-dashboard 1.3.0 release.
1686265,2017-08-11 01:09:23 UTC,This issue was fixed in the openstack/watcher-dashboard 1.4.0 release.
1686268,2017-05-19 05:09:18 UTC,"Seems like there are two possibility:
1. systemd-backlight didn't restore the value successfully.
2. It did, but something else changed the value."
1686268,2017-05-19 08:32:44 UTC,"Setting the multi-user.target causes a timeout error at boot, complaining that it cannot connet lumetad (?)."
1686268,2017-05-19 08:51:40 UTC,Just discovered that the value returned by grep . /var/lib/systemd/backlight/* is ALWAYS the value of cat /sys/class/backlight/intel_backlight/brightness BEFORE reboot.
1686268,2017-05-22 08:23:33 UTC,"> 1. the grep . /var/lib/systemd/backlight/* shows the value of the brightness that was right before the last reboot. That doesn't change real-time when I change the brightness with the slider. The value appear to get stored right before the reboot.
"
1686268,2017-05-23 03:35:15 UTC,"About the reading in #20, it was the situation at that given time, not after a reboot. Since the /sys/class/backlight/intel_backlight/brightness was not 1500 (full brightness after reboot) I obviously changed it."
1686268,2017-05-23 08:48:31 UTC,I now have Precision 5520 and I can reproduce the issue. I'll take a deeper look on this issue.
1686268,2017-05-25 07:03:29 UTC,"Also, try to upgrade to the latest BIOS, that may help:
$ sudo fwupdmgr refresh
$ sudo fwupdmgr update
$ sudo reboot"
1686268,2017-05-25 08:13:31 UTC,"Mario, can you take a look?"
1686268,2017-05-18 01:40:02 UTC,"$ cat /sys/class/backlight/intel_backlight/brightness
451"
1686268,2017-05-26 05:04:26 UTC,"That sounds a little crazy that it can't reproduce in my opinion. When it
""did"" reproduce was the brightness at one of the extremes? Eg full high on
shutdown or full low on shutdown?"
1686268,2017-05-26 05:14:11 UTC,Mine was about half in the battery slider and 0 in the AC slider.
1686268,2017-05-26 05:20:23 UTC,It can't be reproduced once you changed the brightness via slider in BIOS.
1686268,2017-05-26 11:49:12 UTC,"But so we're talking about the slider in the bios that adjusts keyboard
backlight right? That's not tied to display backlight."
1686268,2017-05-26 14:10:55 UTC,"On Fri, May 26, 2017 at 19:55 Mario Limonciello <email address hidden> wrote:"
1686268,2017-05-25 07:55:43 UTC,Changing the brightness in the BIOS video tab got rid of the problem! Great!!!
1686268,2017-05-10 05:51:57 UTC,"Hmm, I think I am still not pretty sure I fully understand the situation here."
1686268,2017-05-25 06:49:33 UTC,"The issue's gone after I changed brightness in BIOS video tab.
So I cannot dig this anymore =("
1686268,2017-05-06 09:59:54 UTC,"Ok, I think I should ask more explicitly:"
1686268,2017-05-06 10:39:18 UTC,"1. The real value of the current brightness (e.g. 75)
2. As I said: after the reboot that value is the same (e.g. 75)
3. As soon as I move the slicer in the Gnome Shell Panel, the new value gets saved into the file (e.g. 150)"
1686268,2017-04-26 06:38:21 UTC,apport information
1686268,2017-04-26 06:38:23 UTC,apport information
1686268,2017-04-26 06:38:26 UTC,apport information
1686268,2017-04-26 06:38:28 UTC,apport information
1686268,2017-04-26 06:38:30 UTC,apport information
1686268,2017-04-26 06:38:34 UTC,apport information
1686268,2017-04-26 06:38:35 UTC,apport information
1686268,2017-04-26 06:38:32 UTC,apport information
1686268,2017-04-26 16:39:11 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1686268,2017-04-27 11:33:33 UTC,"Apparently, it was working with 16.10 (4.8.0-46), although I had a different setup (GNOME desktop added on an official UBUNTU installation from DELL)."
1686268,2017-04-30 15:06:13 UTC,What's the output of `systemctl status systemd-backlight@intel_backlight.service`?
1686268,2017-05-01 03:02:41 UTC,The exact command you wrote:
1686268,2017-05-01 03:14:24 UTC,"I forgot to say that the above output comes after commenting out the @reboot cron entry workaround and restarting, so it is exactly what it does without any workaround."
1686268,2017-05-06 08:56:48 UTC,So is the value of '/sys/class/backlight/intel_backlight/brightness' the stored/restored value?
1686268,2017-05-06 09:41:38 UTC,"Yes, that value is saved as soon as I change the brightness. After reboot the brightness value is not restored (indeed the back-light is actually full brightness), although the value in that file is still the saved one."
1686268,2017-04-26 03:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1686278,2017-06-21 06:28:19 UTC,"this issue also affects XtremIO driver, it doesn't make sense to pass a None connector to the driver, it should first validate it."
1686278,2017-06-21 14:14:39 UTC,"Hi Shay,"
1686278,2017-04-26 19:59:55 UTC,The reason that the reference driver (LVM with tgtadm) didn't fail this test is because the terminate_connection implementation is a no-op. There's nothing for this driver to do:
1686278,2017-04-26 13:57:07 UTC,    Codes below is in cinder/api/contrib/admin_actions.py. That we can find that the connector can be set to None. Here I think /cinder/cinder/volume/drivers/dell_emc/vnx/driver.py should handle the scenario when connector is None.
1686278,2017-04-26 19:16:00 UTC,"""tempest.api.volume.admin.test_volumes_actions.VolumesActionsTest.test_force_detach_volume"" tempest test is failing for Kaminario CI for both FC and iSCSI Kaminario Cinder Drivers"
1686278,2017-04-26 14:01:27 UTC,"This isn't a bug in tempest, tempest is just exposing an issue in emc vnx cinder driver. (it's what tests are supposed to do)"
1686278,2017-04-26 19:34:21 UTC,"@Matthew Treinish,"
1686299,2017-04-26 07:00:14 UTC,This change was made by a bot.
1686299,2017-04-26 16:38:29 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1686299,2017-04-27 03:26:23 UTC,"Okay I was able to fix this.  I tried updating to nvidia-375 in case that was the issue, and during the install I noticed it was compiling something with clang instead of gcc.  After that I was getting the same behaviour from both 4.4.0-72 and 4.4.0-75."
1686299,2017-04-27 04:56:49 UTC,Sounds like maintainer scripts in Nvidia need some tweaks.
1686321,2017-04-26 11:28:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/460072"
1686321,2018-01-12 19:03:58 UTC,Unassigning due to no activity for > 6 months.
1686321,2018-02-12 15:33:16 UTC,Neither this patch nor the bug make the case that this is the right thing to do.
1686321,2018-02-12 15:42:50 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/460072"
1686324,2017-11-05 09:41:40 UTC,This bug was fixed in the package libvirt - 3.6.0-1ubuntu6
1686324,2017-10-24 17:08:55 UTC,SRU +1 for what is currently in the queue.
1686324,2017-11-01 00:27:49 UTC,This bug was fixed in the package libvirt - 3.6.0-1ubuntu6
1686324,2017-10-24 18:43:31 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1686324,2017-10-24 16:10:25 UTC,"Prepped the SRU Template for Artful as it is released now.
Also passed (the now fully running, due to the fixes) regression tests - so ready for SRU review."
1686324,2017-11-01 00:28:05 UTC,"The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1686324,2017-09-14 13:25:39 UTC,"That was a lot of text, the TL;DR is that I have a fix to upstream.
But I'll work on some other virt-aa-helper changes first to submit them together."
1686324,2017-10-24 10:55:41 UTC,"Related changes upstream now, will be picked no next merge.
Likely consider picking in advance as soon as BB opens up."
1686324,2017-05-18 05:22:14 UTC,Actually if possible this should become so good that we can drop the /dev/usb addition to apparmor that we have.
1686324,2017-06-13 13:55:21 UTC,"I don't seem to find time shortly, so I drop server-next tag.
But I ensured it is tracked to remind me and make me feel bad :-/"
1686324,2017-10-25 12:22:51 UTC,Use a guest XML that already combines the USB Hostdev in it.
1686324,2017-09-14 13:24:51 UTC,"Apparmor rule is:
  ""/dev/bus/usb/000/000"" rw,"
1686324,2017-09-11 06:05:41 UTC,"Documenting the workarounds we have until this is solved properly are as following:
- use virsh attach (hot-add) instead of adding it to the guest right away
- If you happen to use the same USB port every time the IDs won't change and you can check what was blocked in dmesg and add just that to the guests (or if you need for more guests libvirt-qemu profile) apparmor profile
- Open up USB more or less in general in libvirt-qemu profile (least recommended for security reasons)"
1686334,2017-04-26 07:54:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/459983"
1686334,2018-01-12 19:04:01 UTC,Unassigning due to no activity for > 6 months.
1686347,2017-06-03 15:10:23 UTC,"I meant, it is *OK to put into lib*, because of coinstallable of different go packages."
1686347,2019-03-22 20:14:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686347,2017-06-05 23:11:44 UTC,"Also, the MTA metaphor is a bit of a non-starter here, given that all MTAs in the archive conflict with each other.  They're not co-installable at all."
1686347,2017-06-05 16:37:31 UTC,Alternatives are not used for toolchain packages.  Toolchain defaults packages are used to define the *distro* default for a compiler for a release.  GCC works the same way.
1686347,2017-06-03 15:19:44 UTC,"Again, the philosophy of needing to install golang-go to get a go on $PATH is wrong."
1686347,2017-06-03 15:06:11 UTC,"@Michael, so how Ubuntu/Debian handle coinstallable different go packages?"
1686347,2017-04-26 11:49:40 UTC,Oh god damn web ui... :)
1686347,2017-04-28 18:17:18 UTC,With all due respect I have to object the resolution of invalid:
1686347,2017-04-26 21:18:36 UTC,You need to install golang-go to get a go on $PATH.
1686347,2017-04-26 11:36:44 UTC,"Ahem. Sorry flippant reply did not help. I was actually talking about this ticket. It is for *Terminator* which is written in Python and has nothing whatsoever to do with Go, so you probably won't find much help here. You should probably raise a new issue with the correct project/package."
1686347,2017-04-26 09:35:57 UTC,I am not sure what else i should have installed.
1686347,2017-04-26 09:16:40 UTC,Wrong package/project maybe?
1686347,2017-04-26 08:59:51 UTC,Ugh hit submit to soon:
1686347,2017-04-30 22:13:35 UTC,"The golang-1.8 package cannot install /usr/bin/go because it needs to be coinstallable with other golang-1.X packages. If you want to use a non default version of Go, you can put it's /usr/lib/go-1.X/bin directory on your $PATH."
1686350,2019-09-23 13:57:02 UTC,"The Skylake-Server cpu type was added for either QEMU 3.0 or 3.1, so this bug is fix-released."
1686353,2018-10-11 01:04:13 UTC,"Hi, I have environment with proxy and ""suffering"" from same problem."
1686353,2021-02-18 16:45:43 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1686353,2019-01-16 13:30:08 UTC,"I marked this as low even if it affects me personally as I do use a proxy locally. Still, this is low because I don't really see when the team will find time to address it."
1686353,2018-10-11 15:57:24 UTC,"@Yossi, go for it. Put up a patch and ping us in #tripleo
Thanks!"
1686353,2018-08-09 13:18:35 UTC,Please let me know if I am missing anything to reproduce the issue.
1686353,2018-08-08 16:11:37 UTC,Any chance using the option in L266 resolves the issue?
1686353,2017-04-27 18:53:29 UTC,"hello, thanks for trying out tripleo-quickstart."
1686353,2017-04-27 19:48:21 UTC,"Hi,"
1686353,2018-08-08 18:47:19 UTC,Looking at this... attempt to reproduce the issue with proxy and venv mix.
1686353,2018-08-08 16:04:18 UTC,"Ooof... apologies this bug got lost in shuffle.
Looking into this now."
1686353,2017-04-28 12:21:57 UTC,Attached my modified script.
1686368,2017-04-27 05:15:16 UTC,Steps to reproduce are fairly easy:
1686369,2018-01-03 11:29:41 UTC,"I can confirm this behaviour. If I do:
""""""
$ sudo snap install test-snapd-tools
$ sudo snap run --shell test-snapd-tools.echo
# less /proc/$$/smaps
/proc/17352/smaps: Permission denied
# exit
$ dmesg | tail -n
[ 8857.462687] audit: type=1400 audit(1514978876.528:426): apparmor=""DENIED"" operation=""ptrace"" profile=""snap.test-snapd-tools.echo"" pid=17410 comm=""less"" requested_mask=""trace"" denied_mask=""trace"" peer=""snap.test-snapd-tools.echo""
"""""""
1686374,2017-04-26 11:34:50 UTC,Doesn't happen in the latest Owncloud version.
1686387,2017-05-03 20:31:37 UTC,I don't think this would have any effect on the Error Tracker but that should be confirmed before using the new version of apport.
1686403,2017-08-29 14:13:05 UTC,"Reviewed:  https://review.openstack.org/498090
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=92fb7bb088f92033cb90f007726ddace4c5dd2d6
Submitter: Jenkins
Branch:    master"
1686403,2017-08-25 20:44:13 UTC,Partially addressed with https://review.openstack.org/498090
1686405,2017-04-26 15:15:28 UTC,Thanks for filing this bug. Would you please explain how the sequence of steps that you describe above reflect what may happen in a real deployment? Is this something that you have found or experienced in a real deployment?
1686405,2017-04-27 02:59:47 UTC,"The purpose of step 1 is to let ovs agent notify the neutron-server port down, unbounding port from ovs bridge is one of the approaches.
I just happen to find this issue when I was dealing with an provisioning block issue of networking-ovn[1], comparing the provisioning block behaviors between networking-ovn and neutron.
This issue does not seem to have a functional impact, but display status and real status are inconsistent.
[1] https://bugs.launchpad.net/networking-ovn/+bug/1686013"
1686412,2017-04-26 14:08:21 UTC," By default, it should always ignore a PXE request of a device. In fact, should we always ensure that we ignore all PXE request unless we add a DHCP snippet that would tell it to PXE?"
1686412,2019-09-19 12:03:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1686421,2017-08-23 16:08:19 UTC,This issue was fixed in the openstack/magnum 5.0.0 release.
1686421,2017-07-18 07:54:20 UTC,This issue was fixed in the openstack/magnum 3.3.0 release.
1686421,2017-05-30 17:36:56 UTC,"Reviewed:  https://review.openstack.org/468775
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=012696943a446b352ac1a5e4992034e75fb33ba0
Submitter: Jenkins
Branch:    stable/newton"
1686421,2017-05-29 06:09:40 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/468775"
1686421,2017-05-25 14:43:10 UTC,"Reviewed:  https://review.openstack.org/467901
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=dacadc2afd4b5675833987ca507ac16dae55996e
Submitter: Jenkins
Branch:    stable/ocata"
1686421,2017-06-08 11:31:16 UTC,This issue was fixed in the openstack/magnum 4.1.2 release.
1686421,2017-05-25 13:33:08 UTC,You need to resolve the conflicts.
1686421,2017-05-25 07:04:03 UTC,"@Spyros Trigazis
When i'm doing cherry-pick from master to newton , i'm getting merge conflict. Now what should i do for the newton release"
1686421,2017-05-25 06:13:50 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/467901"
1686421,2017-05-24 11:41:02 UTC,@M V P Nitesh
1686421,2017-05-10 10:41:06 UTC,"Reviewed:  https://review.openstack.org/463514
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=ad94578a2f5d3dd7fb6bad57cc7c741227ed5c30
Submitter: Jenkins
Branch:    master"
1686421,2017-05-25 13:38:37 UTC,Do the changes here: http://git.openstack.org/cgit/openstack/magnum/tree/magnum/drivers/swarm_fedora_atomic_v1/templates/fragments/volume-service.sh?h=stable/newton
1686424,2019-11-11 19:40:01 UTC,"This was actually merged a long time ago, just forgot to close the bug."
1686437,2019-01-14 11:39:31 UTC,"Also, it seems that the xenial-proposed (1.3) package has been deleted so we need to get the PPA version resubmitted as an sru and test that."
1686437,2019-01-14 11:50:18 UTC,The adjoining bug 1611987 to this one says there is a fix landed in Bionic but it is not clear from the changelog whether that actually fixes v3 support so im going to leave this targeted at X/B/C/D under the assumption that none is fixed yet.
1686437,2019-01-14 18:15:54 UTC,"For the keystone v3 fixes revno 454 is the minimum we need SRU'd back to xenial.
Bionic 0.1.0~bzr460-0ubuntu1 has these changes."
1686437,2019-01-15 14:08:31 UTC,"Version 0.1.0~bzr460-0ubuntu1 from bionic on fixes the problem, so I'm marking B/C/D as ""Fix Released""."
1686437,2019-10-16 14:43:50 UTC,"An upload of simplestreams to xenial-proposed has been rejected from the upload queue for the following reason: ""See https://bugs.launchpad.net/charms/+source/glance-simplestreams-sync/+bug/1611987/comments/21""."
1686437,2019-09-19 13:55:50 UTC,"Rafael's comment matches my memory, and also my comment in the merge proposal at https://code.launchpad.net/~smoser/ubuntu/+source/simplestreams/+git/simplestreams/+merge/341214"
1686437,2019-10-16 16:11:54 UTC,TL;DR version:
1686437,2019-01-14 11:33:53 UTC,I've tested this as well on xenial. This is what I tested:
1686437,2019-09-19 09:40:04 UTC,SUMMARY FOR SIMPLESTREAMS SRU TO XENIAL
1686437,2018-11-11 19:44:18 UTC,"I forgot to include my test cloud info:
Openstack Queens running on Xenial"
1686437,2019-09-20 09:55:09 UTC,"Thank you, Scott, for confirming my summary. I also got IRC confirmation from Billy and Ed."
1686437,2018-09-20 11:44:50 UTC,"Hi,
The current state of this bug:
a.) 0.1.0~bzr426-0ubuntu1.3 was uploaded. It contained a fix for
bug 1686437.  That change contained a regression (bug 1728982, bug 1719879),
so the bug was marked xenial-verification-failed."
1686437,2017-09-14 22:44:03 UTC,This bug was fixed in the package simplestreams - 0.1.0~bzr450-0ubuntu1
1686437,2017-09-20 16:09:34 UTC,"Scott, will 0.1.0~bzr450-0ubuntu1 be backported to xenial?"
1686437,2017-05-10 17:55:25 UTC,"i've linked a work-in-progress branch.
https://code.launchpad.net/~smoser/simplestreams/trunk.openstack-v3-auth
there i had keystone auth working."
1686437,2017-09-26 13:55:49 UTC,"Felipe,"
1686437,2018-04-09 23:09:33 UTC,Noting here the released version on xenial does not currently support Keystone v3 and blocks Bug #1611987.
1686437,2018-11-11 19:33:54 UTC,"Hi,"
1686437,2018-04-10 19:37:38 UTC,"Also, exercising the SRU ppa, I see xenial-pike fail similarly with ksv2:"
1686437,2018-04-23 15:07:21 UTC,"Hello Scott, or anyone else affected,"
1686437,2018-04-24 13:37:27 UTC,"Hi,
I've marked this verification-failed as we had found some issues and forgotten that there was an upload in the xenial queue."
1686437,2018-06-25 14:52:58 UTC,"This bug is believed to be fixed in simplestreams in version 0.1.0. If this is still a problem for you, please make a comment and set the state back to New"
1686437,2018-04-10 19:33:21 UTC,"I believe there is a ksv2 regression in the dev ppa of simplestreams, but I can also confirm that the ksv3 scenario is resolved with the dev ppa."
1686440,2017-04-26 15:35:34 UTC,Log of problem from apt:
1686441,2019-07-10 09:57:55 UTC,"Hi all,"
1686448,2018-03-26 18:06:55 UTC,"I remember I read that article two days after the notebook had arrived. Its Linux support was really poor, even with it having Satux Linux (a really bad distribution). It had much more problems which quickly were corrected, but this one is one of the most persistent issues (tied with the wireless problem we're nearly solving)."
1686448,2017-04-26 16:01:04 UTC,This change was made by a bot.
1686448,2017-04-26 16:08:14 UTC,"Here is the powertop output. Tuning additional options to ""Good"" from this point start to cause problems, as crackling sound and nonfunctional mouse."
1686448,2017-04-26 17:12:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1686448,2017-04-26 19:30:44 UTC,"With this notebook, I am using Xubuntu 16.04 since I bought it. Since the start battery lasted less time than on Windows 10, but I didn't know why this was happening. The kernel at December 2016 was way more problematic, but nearly all the problems were solved, but this one, which reduces battery time, is still present."
1686448,2018-03-25 02:21:37 UTC,"The behavior has greatly improved using the kernel 4.16.0-rc6, the package is reaching the state C8. It's still not C10, but it is pretty close."
1686448,2018-03-26 04:49:40 UTC,Try using r8168-dkms instead of r8169. Some platforms require features in r8168-dkms to hit deeper CPU package state.
1686448,2018-03-26 05:49:38 UTC,"r8168-dkms have not made it hit a higher package C state. On page 70 of the document I posted the link on comment 7, it shows the maximum package C state the Skylake U/Y would be able to reach, depending of screen resolution. As this notebook has a 1366x768 screen, I suppose that it would reach up to Package C8 without PSR (Panel Self-Refresh) disabled, but I have it enabled:"
1686448,2018-03-26 06:30:30 UTC,"This articles says that enabling SATA LPM [1] can reach deeper then C3. But since your laptop already reaches C8, I guess it won't help."
1686450,2020-10-05 15:45:59 UTC,Seems related to bug 489337
1686463,2020-09-22 18:09:14 UTC,"This has just come up again in our consortium, in regards to newly created items."
1686463,2018-08-25 17:02:53 UTC,Just a note that new item creation should ideally also cause relevant holds to be re-targeted.  This would be very helpful for cases in which catalogers add a new copy of an already popular item.  Requiring catalogers to manually retarget holds adds an extra step to the process.
1686463,2017-09-18 16:54:30 UTC,"Apparently so, based on the latest observation."
1686463,2017-06-07 18:35:42 UTC,"Another option which could work for existing, but not new, copies would be to record untargettable copies an a peer table to action.hold_copy_map.  Then we would have a definitive list of holds to retarget, and a potential short-circuit path for adding copies directly to the potentials list if it can be proven that they would now be targettable, all else being equal."
1686463,2017-09-18 15:27:09 UTC,Another situation that came up today was an item whose age hold protection expired while there were still a number of open holds for pickup at various libraries.
1686463,2017-06-23 21:00:14 UTC,"I can conceive of a checkin with hold capture expected happening quite soon after the update that makes the item holdable. There's also the frequent situation where a checkin IS the edit that puts the item into a holdable status. Ideally, the hold would just capture in that case."
1686463,2017-06-07 17:22:35 UTC,"How soon after a copy status, etc. update would we expect staff to check the item in for capture?"
1686463,2017-09-18 16:23:36 UTC,"So in addition to copies being put into a holdable state by staff action (copy edit, checkin, etc.) we are also talking about copies becoming holdable simply by the passage of time (copy age protection)."
1686464,2019-09-19 14:58:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1686484,2017-11-20 22:14:45 UTC,"But you seem to be getting those errors in the build step, not the stage step..."
1686518,2017-04-26 22:19:25 UTC,(Please consider trying to frame your bug reports in text form; video bugs take much longer for developers to process.)
1686518,2017-04-26 23:12:38 UTC,"Colin Watson:
 > I think we could be persuaded to move them up the page a bit so that
 > things flow in the right order.  Would that help?"
1686518,2017-04-26 23:27:25 UTC,"Colin Watson:

> Please consider trying to frame your bug reports in text form; video
> bugs take much longer for developers to process.
"
1686518,2017-04-27 00:25:41 UTC,"No, this can't depend on the text.  The UI here needs to be appropriate for all bug reporting contexts, not just for Ubuntu.  If it seems that in general the guidelines should be displayed before some form elements, then we can make that change in general, but it won't be an Ubuntu-specific change."
1686518,2017-04-27 04:27:11 UTC,"Colin Watson:

> The UI here needs to be appropriate
> for all bug reporting contexts, not just for Ubuntu.  If it seems that
> in general the guidelines should be displayed before some form elements
"
1686528,2017-04-27 00:15:34 UTC,"Many bitmaps in the file, plus masks and clips. I suggest tracing the bitmaps into vector objects."
1686532,2017-04-26 22:06:40 UTC,https://github.com/CanonicalLtd/landscape-client/pull/7
1686538,2017-05-03 12:34:53 UTC,"Hi,
Florian,
Thanks for filing the bug."
1686538,2017-05-03 15:25:05 UTC,"Hi Scott, thanks for getting back to me. I can no longer reproduce this (with 0.7.9-48-g1c795b9), which baffles me even more. The only change that I am aware of that was made in the OpenStack configuration was that dnsmasq_local_resolv was enabled in Neutron's dhcp_agent.ini, and that two upstream DNS servers were added to the dnsmasq_dns_servers list as well."
1686538,2017-05-04 02:10:40 UTC,"Florian,
Could you try switching it back, and then collecting /var/log/cloud-init.log ?  journalctl output would also be appreciated."
1686538,2017-10-04 22:39:10 UTC,"I am also experiencing this issue.  The problem is that it's not alway 100% reproducible.  I see it when deploying some instances and not on others.  I can shorten the datasources list to only include OpenStack which will ensure it always works, but I would rather that it only uses the detected datasources and errors out otherwise."
1686544,2017-05-07 05:58:15 UTC,sudoUser=%#gid is a known bug in sssd https://pagure.io/SSSD/sssd/issue/1678
1686544,2017-05-06 15:03:49 UTC,"In the link posted above, the OP solves the problem by adding objectClass: posixgroup to his groups.
In my case, they already are ""posix-ified""."
1686544,2017-05-04 20:57:38 UTC,reported here too : https://www.redhat.com/archives/freeipa-users/2017-May/msg00033.html
1686551,2017-07-28 17:35:57 UTC,"Committed to 0.92.x in
https://gitlab.com/inkscape/inkscape/commit/cd39fea30e30ac7af42b4c82a3892c76257168b3"
1686551,2017-07-27 20:42:01 UTC,Fixed in master in r.f5680325a3..cad1e0ce01
1686551,2017-07-26 22:13:53 UTC,This patch from Jacek Hyacinth Stypuła Fixes the problem in inkscape
1686551,2017-07-27 20:42:34 UTC,Git patch for 0.92.2
1686551,2017-06-12 14:10:35 UTC,"Hi: How can update jessyink with this workaround? I tried replacing the original jessyink.js with this version. After updating the jessyink, the SVG is slightly heavier, but it doesn't fix the bug in chromium."
1686551,2017-05-24 09:47:00 UTC,"This is caused by a new ""feature"" in Chrome, see https://www.chromestatus.com/feature/5736166087196672"
1686551,2017-05-05 21:54:13 UTC,Also not working well in Chromium 58 on Linux
1686551,2017-07-22 15:44:15 UTC,"I tested the original SVG file, adding the code Jacek Hyacinth Stypuła provided and seems to works. You can test and compare with the original file:"
1686579,2018-02-07 03:08:22 UTC,I don't have this bug but I think it is a feature and I want it.
1686579,2018-02-07 03:22:13 UTC,"AFAIK, the lower bound is machine-dependent. Same software, different hardware, different lower bound. Some machines can achieve full blackness already, and others can't. It's always been this way..."
1686579,2017-05-22 02:57:10 UTC,This doesn't occur in Unity - the lowest setting is dark but still visible.
1686579,2017-04-27 02:42:10 UTC,I can duplicate this bug with Intel graphics.
1686579,2017-05-18 21:03:47 UTC,"Robert, is this actually a gnome-settings-daemon bug (or even as https://bugzilla.gnome.org/782155 implies, a kernel bug)?"
1686579,2017-04-27 02:08:57 UTC,I don't know if this is a driver issue or GNOME shell should have a lower limit on brightness (e.g. 10%).
1686588,2017-04-27 06:48:54 UTC,"Hi,"
1686588,2017-04-27 09:00:55 UTC,"With v2 API, I only see (1) public images. Only images with the property is_public:True are listed, Project-owned and project-shared aren't visible in the drop-down list."
1686588,2017-04-27 23:53:02 UTC,"https://bugs.launchpad.net/horizon/+bug/1655259 looks similar but I think it is a different issue, though they may be related. In that case public and private images are listed and shared images are missing. In this issue both private and shared are missing."
1686595,2019-06-27 08:47:47 UTC,"Since this report was originally created, a lot of work has been done in the area including the ability to add several lxd 'clouds', lxd cluster, etc."
1686595,2019-08-27 04:17:21 UTC,[Expired for juju because there has been no activity for 60 days.]
1686597,2017-04-28 09:39:21 UTC,"Please show output of ""hiera repo_setup"" cmd on any controller.
It'd be good to get content of /etc/hiera dir as well."
1686597,2017-05-22 09:23:33 UTC,"Luca,
1. Could you please open a bug since you have more context/details.
2. All changes are in the changeLog."
1686597,2017-05-02 04:05:39 UTC,"root@node-111:~# hiera repo_setup
{""metadata""=>
  {""always_editable""=>true,
   ""group""=>""general"",
   ""label""=>""Repositories"",
   ""weight""=>50},
 ""pin_ceph""=>false,
 ""pin_haproxy""=>false,
 ""pin_rabbitmq""=>false,
 ""repo_type""=>""uca"",
 ""repos""=>
  [{""name""=>""ubuntu"",
    ""priority""=>nil,
    ""section""=>""main universe multiverse"",
    ""suite""=>""xenial"",
    ""type""=>""deb"",
    ""uri""=>""http://archive.ubuntu.com/ubuntu/""},
   {""name""=>""ubuntu-updates"",
    ""priority""=>nil,
    ""section""=>""main universe multiverse"",
    ""suite""=>""xenial-updates"",
    ""type""=>""deb"",
    ""uri""=>""http://archive.ubuntu.com/ubuntu/""},
   {""name""=>""ubuntu-security"",
    ""priority""=>nil,
    ""section""=>""main universe multiverse"",
    ""suite""=>""xenial-security"",
    ""type""=>""deb"",
    ""uri""=>""http://archive.ubuntu.com/ubuntu/""},
   {""name""=>""uca"",
    ""priority""=>1080,
    ""section""=>""main"",
    ""suite""=>""xenial-updates/ocata"",
    ""type""=>""deb"",
    ""uri""=>""http://ubuntu-cloud.archive.canonical.com/ubuntu""},
   {""name""=>""uca-proposed"",
    ""priority""=>1080,
    ""section""=>""main"",
    ""suite""=>""xenial-proposed/ocata"",
    ""type""=>""deb"",
    ""uri""=>""http://ubuntu-cloud.archive.canonical.com/ubuntu""},
   {""name""=>""mos"",
    ""priority""=>1050,
    ""section""=>""main restricted"",
    ""suite""=>""mos11.0"",
    ""type""=>""deb"",
    ""uri""=>""http://146.118.52.2:8080/ocata-11.0/ubuntu/x86_64""},
   {""name""=>""mos-updates"",
    ""priority""=>1050,
    ""section""=>""main restricted"",
    ""suite""=>""mos11.0-updates"",
    ""type""=>""deb"",
    ""uri""=>""http://mirror.fuel-infra.org/mos-repos/ubuntu/11.0/""},
   {""name""=>""mos-security"",
    ""priority""=>1050,
    ""section""=>""main restricted"",
    ""suite""=>""mos11.0-security"",
    ""type""=>""deb"",
    ""uri""=>""http://mirror.fuel-infra.org/mos-repos/ubuntu/11.0/""},
   {""name""=>""mos-holdback"",
    ""priority""=>1100,
    ""section""=>""main restricted"",
    ""suite""=>""mos11.0-holdback"",
    ""type""=>""deb"",
    ""uri""=>""http://mirror.fuel-infra.org/mos-repos/ubuntu/11.0/""},
   {""name""=>""Auxiliary"",
    ""priority""=>1150,
    ""section""=>""main restricted"",
    ""suite""=>""auxiliary"",
    ""type""=>""deb"",
    ""uri""=>""http://146.118.52.2:8080/ocata-11.0/ubuntu/auxiliary""}]}"
1686597,2017-05-02 04:07:13 UTC,let me know what files you need in /etc/hiera that I need to clean them up from private info
1686597,2017-05-03 11:36:54 UTC,"Please describe all the steps performed to get such apt policy output.
Since with latest iso with unpinned haproxy package we've got:
# apt-cache policy haproxy
haproxy:
  Installed: 1.6.3-1~u16.04+mos3
  Candidate: 1.6.3-1~u16.04+mos3
  Version table:
     1.6.3-1ubuntu0.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
     1.6.3-1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
 *** 1.6.3-1~u16.04+mos3 1050
       1050 http://10.20.0.2:8080/ocata-11.0/ubuntu/x86_64 mos11.0/main amd64 Packages
        100 /var/lib/dpkg/status"
1686597,2017-05-16 03:29:04 UTC,"Micheal,
If unpinned to mos repositories, why the package installed is from the mos repositories?
It should be the 1.6.3-1 from the UCA repos isn't it?"
1686597,2017-05-16 08:35:29 UTC,Because package candidate (latest by version) to install is from mos repo anyway.
1686597,2017-05-22 07:44:34 UTC,"Michael,"
1686597,2017-05-01 01:09:31 UTC,Here
1686604,2020-05-17 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1686604,2020-03-17 08:00:51 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1686610,2017-07-11 21:44:42 UTC,Do we have a list of commits or oprofile version number that we should confirm we are carrying in our Ubuntu 17.10 release? Thanks.
1686610,2019-10-23 05:39:57 UTC,1.3.0 in 19.10
1686610,2019-05-10 02:27:46 UTC,oprofile in 19.04 is 1.2.0.
1686610,2018-10-29 07:28:39 UTC,26715ca oprofile: Add support for Intel Goldmont Plus (Geminilake)
1686610,2018-08-09 01:11:30 UTC,"yes, please."
1686610,2019-05-06 06:47:14 UTC,any update from Canonical?
1686610,2018-07-05 01:53:24 UTC,26715ca oprofile: Add support for Intel Goldmont Plus (Geminilake)
1686610,2018-05-01 05:38:09 UTC,oprofile package upgrade. Currently there is no support in oprofile for GLK. upstream is working on that.
1686610,2018-02-23 23:26:10 UTC,Is there a list of commits we should confirm for 18.04?
1686610,2017-10-10 04:43:39 UTC,let's move it to 18.04 since no update from upstream.
1686610,2018-07-25 15:18:43 UTC,Can I move this bug to the linux package and mark it as public?
1686614,2017-04-27 09:48:34 UTC,"Just to mention an additional discrepancy:
According to https://lists.ubuntu.com/archives/ubuntu-announce/2017-March/000218.html the EOL date of precise is April 28, 2017, why does https://motd.ubuntu.com tell about April 25?"
1686614,2017-04-27 16:06:29 UTC,"I believe this is expected and by design, but I'll let Dustin comment."
1686614,2017-04-27 16:41:23 UTC,This fixes comment #1.
1686614,2017-04-28 10:19:15 UTC,I just did a new install of Ubuntu Server 17.04 and also received the MOTD.
1686623,2018-10-16 12:30:28 UTC,"I'm a user of the Paper Theme and can confirm that this is also happening! And yes, the bug disappear whenever I use default themes."
1686623,2017-12-08 21:17:38 UTC,"Using the default Nuxim or Adwaita GTK themes doesn't seem to produce this bug. I too am effective with this bug, but only when using 3rd party themes."
1686623,2017-11-09 17:03:22 UTC,"Same issue here, whether I'm on a phisical machine or a VM."
1686623,2017-11-09 17:04:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686623,2017-11-13 17:08:11 UTC,"This happend to me too.
I'm running Ubuntu Budgie 16.04 using the Elementary GTK theme.
Switching to a different theme seemed to stop this unwanted behavior, so in my case it must be a bug in the Elementary theme."
1686629,2017-05-09 21:47:39 UTC,any idea how to resolve that? thanks
1686629,2017-05-23 10:11:19 UTC,update on my lab:
1686632,2017-04-27 08:45:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686632,2017-04-27 08:47:31 UTC,"This does not affect other players such as Clementine.
Play/Pause control buttons also have no effect on playback.
Skip Next / Previous Buttons work however.
Reproduced on Ubuntu MATE 17.04"
1686632,2018-02-11 18:37:23 UTC,"I think this is not the correct bug title. In fact, There is no problem when you start a file from the vlc icon in the sound indicator. The problem is on the other way : the indicator sound is not able to know vlc status when a file is started from the file manager."
1686632,2018-02-11 18:38:19 UTC,reproduced on all ubuntu version (even ubuntu 18.04 with several mate version s)
1686638,2020-09-23 15:40:01 UTC,"Seeing this bug in current bionic/ussuri deployment, still actual:"
1686638,2020-09-23 15:39:37 UTC,"Can confirm, this is still actual:"
1686638,2020-04-22 08:35:37 UTC,"Hey, I wasn't able to reproduce the restart on update-status. I realize this is quite an old issue, but would you have any more details around this issue? Ideally a bundle and full logs, or maybe even an sosreport. Thanks!"
1686638,2017-09-27 05:00:20 UTC,"In addition, the telegraf charm logs considerable noise on every update-status hook run: https://pastebin.canonical.com/199361/"
1686638,2020-09-12 01:42:54 UTC,@peter-sabaini
1686639,2017-09-04 09:01:18 UTC,"This bug also exists in mate-screensaver[1], so I won't fix it unless the upstream submit a patch."
1686641,2017-09-11 17:39:53 UTC,We could add a validation check to secret delete to make sure that deleting a secret will not break a certificate container.  This is a wishlist item.
1686647,2017-07-02 22:18:22 UTC,This bug was fixed in the package ukui-screensaver - 1.0.2-0ubuntu1
1686653,2017-04-27 09:44:07 UTC,"Please review:
https://review.openstack.org/#/c/460471/"
1686653,2017-06-08 18:19:34 UTC,This issue was fixed in the openstack/freezer-web-ui 5.0.0.0b2 development milestone.
1686656,2017-07-06 09:28:32 UTC,"Reviewed:  https://review.openstack.org/480070
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=d0b32e8a737153da5f92848e2359a13e0e5f93e4
Submitter: Jenkins
Branch:    stable/ocata"
1686656,2017-04-27 09:42:20 UTC,"[root@controller openstack-dashboard]# pwd
/etc/openstack-dashboard
[root@controller openstack-dashboard]# ls
ceilometer_policy.json  glance_policy.json  keystone_policy.json  neutron_policy.json
cinder_policy.json      heat_policy.json    local_settings        nova_policy.json"
1686656,2017-05-02 03:30:18 UTC,"The local_settings.py file exists in ubuntu or obs.
The local_settings file exists in RDO."
1686687,2017-05-15 22:17:58 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1686687,2017-05-10 11:33:01 UTC,We did get around to do more testing and follow suggestions. The filesystem corruption could be reproduced. The run was done bypassing multipathing and using a single path directly.
1686687,2017-05-01 19:11:25 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1686687,2017-04-27 21:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1686687,2017-04-28 07:15:52 UTC,Marked as Confirmed in accordance with comment #3. Further detail might be provided on request.
1686687,2017-04-28 19:08:18 UTC,"Come to think of it, since you say it only seems to happen on a multipath SAN and not on a normal disk, it may be related to the order of requests being sent to the disk and XFS's use of io barriers to make sure that the unmap request for the old data does not hit the disk after the new filesystem metadata has been written.  IIRC, xfs has mount options to control the use of io barriers.  Do you have them enabled?"
1686687,2017-04-27 20:49:11 UTC,"Just reomve /etc/cron.weekly/fstrim as a workaround.  The underlying bug is not in fstrim, but in the kernel somewhere; probably the XFS filesystem driver and its interaction between preallocation and the FIBMAP ioctl."
1686687,2017-04-28 07:13:56 UTC,"For us, fstrim was the frontend to the bug and running it consistently damaged our filesystems. That is why util-linux was chosen as the affected package. Also removing the cron file will not be sufficient as any update to the package (using cron-apt) might re-install it. Maybe a conflicting change would be a better choice. Still seems to brittle in light of such severe consequences. Mitigated by not upgrading to 16.04 for now."
1686699,2017-04-27 12:19:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/460523"
1686699,2017-07-18 15:30:36 UTC,"Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: master
Review: https://review.openstack.org/460523
Reason: Unfortunately, I don't have time to figure out this. Anyone is free to take over."
1686710,2018-01-25 09:09:49 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2263
1686731,2017-05-03 18:06:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686738,2017-05-02 08:08:18 UTC,See also https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/7
1686759,2017-12-02 15:15:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686764,2017-09-28 21:49:42 UTC,"I think this can actually be closed. Since the config option enforces input now, and the only defined acceptable input are the two options that we know are good, it actually looks like this code isn't needed anymore and can just be removed."
1686764,2017-09-28 22:25:15 UTC,"@Sean: it's a bit more complicated than that.  As you point out, misconfiguration of the option is prevented by the 'choices' parameter when the option is defined, so we're OK there.  The test that was removed made sure that Glance handled a missing module gracefully (because it's possible for an operator to configure the option with the correct name, but not have the module present).  The easiest way to test that was to make up a module name that wouldn't be found, but that's blocked now by the change to oslo.config.  So I think we do need the code there (and we do know it did work before the change to oslo.config); it's just that we need to come up with some way to test it."
1686766,2018-01-29 18:23:28 UTC,"Having a ""snapcraft cleanbuild --profile <LXD profile>"" option would also make our use case tremendously easier (building a snap from a program with several private source git/bzr dependencies)."
1686781,2018-01-25 08:39:41 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3690
1686781,2017-07-03 20:57:22 UTC,"Setting this one to ""Confirmed"", but title should say something like ""Fully backport 5.7 fix into 5.6"""
1686781,2017-07-03 20:56:29 UTC,Version 5.7 supports gcc 4.4+: https://github.com/percona/percona-server/blob/5.7/cmake/os/SunOS.cmake
1686781,2017-05-02 07:07:36 UTC,"Yes, I've built it this way, but it's just a workaround. Treating gcc as unsupported compiler is strange."
1686781,2017-05-02 03:30:57 UTC,Is CMake option -DFORCE_UNSUPPORTED_COMPILER=ON a viable workaround?
1686781,2017-06-23 07:17:41 UTC,That is a pity: we use Openindiana Hipster at work just because of percona. We had problems with recent SuSE Linux systems and then went to Hipster because of the good integration...
1686781,2017-05-02 07:27:30 UTC,"OpenIndiana is an unsupported platform for us with either compiler. Please file a bug on bugs.mysql.com. For us, we can accept a PR that removes the fatal error property from ""Unsupported compiler!"" message added by the above commit in CMake."
1686788,2017-05-04 13:42:01 UTC,I have linux-image-extra-${ver}-generic for each normal Ubuntu linux-image-${ver}-generic package.
1686788,2017-04-27 17:30:10 UTC,This change was made by a bot.
1686788,2017-04-27 17:41:44 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1686788,2017-04-27 19:28:11 UTC,"I rebooted today and now none of my three monitors (DVI, VGA, Displayport) are not working with the docking station.  Network, Power, and USB functions still work."
1686788,2017-04-28 13:05:33 UTC,"Update, I am able to use the displayport and the hdmi interfaces on the back of my laptop.  Issue appears to be related to use of the docking station."
1686788,2017-05-02 15:01:58 UTC,"Tested with v4.4.65, the latest v4.4 stable kernel as of this writing. The problem happens with that as well."
1686788,2017-05-03 09:34:49 UTC,I have a Dell Latitude E7450 here and can confirm the problem. As soon as I try to activate both monitors over the docking station I end up in a kernel panic.  When I go back to to 4.4.0-72-generic all works as expected.
1686788,2017-05-03 09:36:41 UTC,My syslog with the relevant kernel panic.
1686788,2017-05-03 13:52:30 UTC,Can you ensure you have the linux-image AND linux-image-extra .deb packages installed?
1686788,2017-05-03 14:25:32 UTC,@jsailsbury: At least for my case the extra package is installed for all kernel versions.
1686796,2018-03-09 09:44:51 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1686796,2020-06-13 10:07:13 UTC,"This issue has sat incomplete for over two years now without any response to comment #12 or further reports of the problem so I closing this report as ""Invalid""."
1686796,2017-04-30 13:36:46 UTC,The report is here: https://bugs.launchpad.net/ubuntu-gnome/+bug/1687288
1686796,2017-04-27 17:30:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686796,2017-04-30 12:39:22 UTC,"As Epiphany uses the NPAPI plugin and the other browsers use chrome-gnome-shell, I will file another report for the other browsers."
1686796,2017-04-30 11:34:04 UTC,"The only real difference between the Firefox and Epiphany experience is that with Firefox I got no ""ERROR"" message on the site and the extensions did actually seemingly update properly, but it turned them all on and wouldn't allow me to disable them. It also messed the AO up and made the extensions not function properly."
1686796,2017-04-30 11:25:26 UTC,"I have now found the same issue with using Firefox, though I have not tried Chromium."
1686796,2017-04-30 13:36:32 UTC,I have filled another report as requested by upstream for chrome-gnome-shell where I experience very similar issues.
1686802,2017-04-27 21:37:27 UTC,This happens if I choose to use lightdm instead of gdm3.
1686802,2017-04-27 21:46:44 UTC,solved switching between login managers. Now the problem doesn't occurs neither with lightdm.
1686802,2017-04-28 08:49:39 UTC,"This morning, bug come back."
1686802,2017-11-11 05:19:09 UTC,Experiencing this on 17.10. It happens on every resume from suspend.
1686802,2017-11-11 05:19:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686804,2017-04-30 16:07:18 UTC,"Reproduced on Windows 7, lp:inkscape rev. 15653.
Not reproduced with 0.92.1."
1686804,2020-09-22 08:51:29 UTC,Closing because INVALID: Can't replicate.
1686807,2017-04-30 11:16:37 UTC,"""Phantom"" button is to create a gray scale copy of the measure for use as reference. I vote to mark this bug as invalid if no better explain of the bug. Im not english."
1686821,2020-07-20 20:19:36 UTC,working on this at https://github.com/gnome-terminator/terminator/issues/164
1686822,2017-04-27 20:25:02 UTC,"Platform info:
Linux  4.4.23-31.54.amzn1.x86_64 #1 SMP Tue Oct 18 22:02:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux"
1686822,2018-01-25 08:39:40 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3691
1686828,2017-04-27 20:30:17 UTC,This change was made by a bot.
1686828,2017-05-04 10:23:10 UTC,"Just to state that also affected me, seen many different bug reports (in different distros) and the general proposed solution is to upgrade BIOS."
1686828,2017-11-29 14:54:18 UTC,"Same here, latest BIOS updated, both kernal LTS and latest"
1686836,2020-01-14 14:49:06 UTC,I'm getting this bug on Ubuntu 19.10 Linux 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
1686848,2017-10-04 17:58:26 UTC,will be fixed in 4ppa53
1686855,2018-05-08 18:06:43 UTC,This change was made by a bot.
1686855,2021-01-07 04:17:58 UTC,4.8 EOL
1686867,2017-04-28 07:59:37 UTC,You don't mention which version of Terminator you are using. Terminator (1.90+) and Gnome-Terminal now  use the same version of the VTE terminal widget. With that version the behaviour should be identical.
1686869,2017-06-28 13:09:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1686872,2017-05-27 00:57:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686883,2017-05-08 06:24:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463252"
1686883,2017-11-04 23:07:48 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/463252
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1686887,2019-09-19 14:48:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1686887,2017-12-12 13:55:39 UTC,Still valid with 2.3.x of both Juju & MAAS.
1686887,2017-05-10 01:10:20 UTC,"Well, I'd say it is not strictly speaking 'must be used for neutron', rather 'may be used'. I may have x machines suitable for neutron but some of them may end up being used for something else."
1686887,2017-05-08 07:45:54 UTC,Juju itself does not determine what machines will use what tags or do any prioritization based on it. We simply hand the information off to MaaS to provide us with machines based on the constraints that a user passed in.
1686895,2020-11-17 09:08:01 UTC,Please use bug 1894596 instead.
1686895,2019-12-16 02:08:24 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1686895,2017-12-28 08:32:44 UTC,"For now, I use this workaround: Open Gnome ""Settings"", go to ""Devices"" -> ""Colour"" and toggle the colour management for the screen(s) off and on again."
1686895,2017-08-21 14:19:00 UTC,You're welcome.
1686895,2020-11-17 08:49:11 UTC,"Hi All,"
1686895,2017-08-21 14:13:00 UTC,"Reported upstream
https://bugzilla.gnome.org/show_bug.cgi?id=786569"
1686895,2017-08-21 09:45:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1686895,2017-08-21 08:59:38 UTC,Bug #1701772 seems to be a duplicate of this.
1686895,2017-08-21 08:49:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1686895,2017-08-21 08:49:26 UTC,"Hi I have the same bug.
Night Light stays orange after waking from sleep.
Turing it on or off etc. doesn't fix it."
1686895,2017-08-21 14:16:52 UTC,Thanks
1686905,2018-03-23 15:29:32 UTC,"Experiencing similar issues here.  ""touch"" works, a lot of other things (xtightvncserver, conky) don't.  Haven't tried some of my custom daemons yet."
1686920,2017-05-01 07:59:11 UTC,https://github.com/juju/juju/pull/7297
1686920,2017-05-08 02:30:16 UTC,Still being seen in CI: http://reports.vapour.ws/releases/5198/job/run-unit-tests-xenial-amd64/attempt/132#highlight
1686920,2017-05-08 07:33:17 UTC,"That particular test seems to be stuck in a TearDownTest. I wonder if there
was just a hang trying to cleanup:"
1686920,2019-07-07 22:32:06 UTC,"This is a very old report. It references code that is no longer there. In addition, we have not seen this failure for years."
1686925,2018-10-05 09:05:15 UTC,You can archive it with the new Clone LPE in devel
1686932,2017-04-30 09:29:54 UTC,"Thanks for taking the time to file a report!
Reproduced on Windows XP (32-bit), with lp:inkscape/0.92.x rev. 15419."
1686937,2018-10-13 23:19:38 UTC,"I fixed this by editing ~/.config/sakura/sakura.conf to change font size with ctrl-shift-minus and ctrl-shift-equals (plus) - at that point ctrl-minus results in the ctrl-underscore key, which is what I wanted:"
1686937,2017-10-02 22:27:06 UTC,"Something using gtk_accelerator_get_default_mod_mask seems right.
https://developer.gnome.org/gtk3/stable/checklist-modifiers.html"
1686937,2017-05-20 08:09:37 UTC,"actually, I'm not affected, I just proofread my sakura.conf with the
cheat sheet I posted in https://bugs.launchpad.net/sakura/+bug/689572
And every thing looks in order now."
1686937,2017-09-26 17:50:48 UTC,"I think this is caused by checking if the modifier key is pressed, instead of checking if *only* that modifier key is pressed."
1686937,2017-05-19 10:06:26 UTC,"I am affected, and think this is linked to https://bugs.launchpad.net/sakura/+bug/1673068"
1686937,2017-10-02 22:15:50 UTC,"Hmm, that doesn't work if e.g. Num Lock is pressed."
1686944,2017-08-30 20:48:12 UTC,"Reviewed: https://review.fuel-infra.org/36364
Submitter: Pkgs Jenkins <email address hidden>
Branch: mcp/1.0/mitaka"
1686944,2017-08-30 18:37:24 UTC,"Change abandoned by Vladyslav Drok <email address hidden> on branch: mcp/1.0/mitaka
Review: https://review.fuel-infra.org/36364"
1686944,2017-08-30 16:48:14 UTC,"Fix proposed to branch: mcp/1.0/mitaka
Change author: Chris Friesen <email address hidden>
Review: https://review.fuel-infra.org/36364"
1686944,2017-08-30 18:44:45 UTC,"Change restored by Vladyslav Drok <email address hidden> on branch: mcp/1.0/mitaka
Review: https://review.fuel-infra.org/36364"
1686944,2017-05-16 06:33:34 UTC,"Reviewed: https://review.fuel-infra.org/35173
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1686944,2017-05-04 10:40:45 UTC,The fix is already merged to 10.0: https://review.fuel-infra.org/#/c/30763/
1686944,2017-05-04 10:00:53 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Chris Friesen <email address hidden>
Review: https://review.fuel-infra.org/35173"
1686944,2017-04-28 09:18:41 UTC,sla1 for 9.0-updates
1686944,2017-05-17 10:55:18 UTC,Verified on 9.2 + mu2 updates.
1686980,2020-07-14 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1686980,2020-05-14 05:56:13 UTC,Is this faster nowadays if you use the new -blockdev parameter instead of -drive?
1686980,2017-04-28 10:30:21 UTC,The first place where it ages an insane amount of time is simply processing -drive options. The stack trace I see is this
1686980,2017-04-28 10:53:08 UTC,I instrumented drive_new to time how long 1000 creations took with current code:
1686980,2017-04-28 14:08:54 UTC,I added further instrumentation and got this profile of where the remaining time goes
1686982,2018-01-25 08:55:28 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1086
1686992,2017-04-28 11:00:12 UTC,This change was made by a bot.
1686992,2017-05-01 19:07:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1686992,2017-05-01 21:15:05 UTC,The issue started happening as soon as I started using the bluetooth dongle on this laptop some days ago.
1686992,2017-07-28 08:54:07 UTC,Please attach output of `hciconfig -a`.
1686992,2017-07-28 08:55:31 UTC,It probably needs something like commit 6cafcd959599d91d0fa4615feae7f1e7ab407c4b.
1687001,2017-04-28 11:53:28 UTC,"For the record the problem was that the IRC server password got lost somehow, and went I went to System Preferences -> Online Accounts and entered it again, Polari started working."
1687008,2017-06-11 14:11:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687009,2017-08-03 01:00:49 UTC,This issue was fixed in the openstack/heat 8.0.3 release.
1687009,2017-08-03 00:47:40 UTC,This issue was fixed in the openstack/heat 7.0.5 release.
1687009,2017-07-04 10:55:50 UTC,"Reviewed:  https://review.openstack.org/472524
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=f461a0b36215d5d830899c65ac4070a39d7c3b69
Submitter: Jenkins
Branch:    stable/newton"
1687009,2017-06-09 08:03:54 UTC,"Reviewed:  https://review.openstack.org/468010
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=437c5e7c4fe2f0fc3eaa034348384e7cd7cc81a6
Submitter: Jenkins
Branch:    stable/ocata"
1687009,2017-05-25 11:47:53 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/468010"
1687009,2017-05-25 07:43:16 UTC,"Reviewed:  https://review.openstack.org/462426
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=a8129573d221284a482e84e62a7e8b0732318bfe
Submitter: Jenkins
Branch:    master"
1687009,2017-06-09 05:07:12 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/472524"
1687009,2017-05-04 07:56:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462426"
1687009,2017-05-05 07:51:00 UTC,"That looks fantastic, thanks @rabi! Will this one be backported to Newton?"
1687009,2017-05-03 02:06:03 UTC,"I could reproduce this in my setup. So both snapshot and restore do not work for nested stacks( i'e OS::Nova::Server in a nested stack). We don't seem to do anything, in case of snapshot we set the status to SNAPSHOT_COMPLETE for the nested stack resource and ignore it completely for restore."
1687009,2017-05-03 02:06:39 UTC,The above comment applies to master too.
1687009,2017-06-07 15:45:21 UTC,This issue was fixed in the openstack/heat 9.0.0.0b2 development milestone.
1687009,2017-05-04 04:23:57 UTC,"> But I think what you're saying is that for nested stacks both snapshot and restore are broken, whereas for non-nested ones snapshot works but restore breaks. Did I understand that correctly?
"
1687009,2017-05-04 06:33:43 UTC,"It seems to be happening before calling defn.freeze(properties=props), when doing get_item to create props as we override defn properties and it doesn't resolve any intrinsic functions."
1687009,2017-05-03 06:57:40 UTC,"@rabi For the benefit of other subscribers following this, I'd like to emphasize that at least the restore problem is *not* limited to nested stacks."
1687013,2017-04-29 05:30:54 UTC,"use latest SikuliX version 1.1.1, which has xlrd bundled."
1687013,2017-04-29 06:43:08 UTC,"Thanks RaiMan for your reply . still i don't know how to setup with Jython 2.7 , Anyway I will google this, if problem still not solve hope you be here."
1687013,2017-07-05 10:27:37 UTC,"Hi RaiMan,"
1687013,2017-07-05 10:48:18 UTC,"book = xlrd.open_workbook('Excel.sikuli/myfile.xls')
worksheet = workbook.sheet_by_name('Sheet 1')"
1687015,2017-04-30 05:11:34 UTC,Which version of Ubuntu is this occurring on?
1687015,2017-05-02 14:52:08 UTC,"Xenial, sorry, ubuntu:x is lxd shortcut for xenial."
1687015,2017-05-02 14:54:35 UTC,"Installing systemd 229_4ubuntu17 also installs the same version of libsystemd0 and libpam-systemd, so possibly could be those packages, but as noted, an strace of 'apt install systemd' didn't indictate anything."
1687015,2017-05-02 14:56:33 UTC,"The source package: https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu17
and the diff: http://launchpadlibrarian.net/306522149/systemd_229-4ubuntu16_229-4ubuntu17.diff.gz"
1687015,2017-05-02 16:16:43 UTC,I'm an idiot. Of course strace doesn't trace forks by default.
1687015,2017-05-02 16:35:04 UTC,The explicit /bin/systemd-tmpfiles is invoked in the postinst script for systemd.
1687015,2018-02-08 10:16:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687018,2017-05-24 05:02:28 UTC,"If there are no objections, let's switch this to public and close the OSSA task."
1687018,2017-05-24 14:38:41 UTC,"Consensus already seems to have been reached that this is not a vulnerability, so I'm going to open it publicly as a hardening opportunity."
1687018,2017-05-02 09:42:46 UTC,"Yepp, it is not a big issue, just a kind of information leak. Maybe one tenant can try to DOS other tenant's VM via putting a volume next to it, and generate heavy IO."
1687018,2017-04-28 14:50:38 UTC,"If this risk relies strictly on guessing or finding a victim's instance UUID through other means, then it's a class C1 report per our taxonomy and can be triaged as a potential hardening opportunity instead. https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1687018,2017-04-28 14:46:52 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1687018,2017-04-28 15:05:22 UTC,"I don't think this is really a security concern. I don't see a possible data leak from one tenant to another. In fact, it's quite possible the chosen host could be running VMs for both the current tenant and the ""spoofed"" tenant."
1687024,2017-05-31 18:03:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687024,2020-07-03 04:25:36 UTC,"DistroRelease: SparkyLinux 4
libjpeg8:amd64 (8d1-2)"
1687025,2017-05-04 00:40:40 UTC,Confirming read-only access on disk with kernel versions 4.8.0-49 (linux-image-4.8.0-49-generic 4.8.0-49.52~16.04.1) and 4.8.0-51 (linux-image-4.8.0-51-generic 4.8.0-51.54~16.04.1). Downgrading kernel to 4.8.0-46 (linux-image-4.8.0-46-generic 4.8.0-46.49~16.04.1) does not show the issue.
1687025,2017-05-04 00:42:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687025,2017-05-04 09:26:15 UTC,Opened other bug report as I am not sure the issue here is identical. https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1688213
1687027,2019-02-23 03:52:52 UTC,"Reviewed:  https://review.openstack.org/638120
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8b255a648c381bfcff0623ba97880855c7fa21eb
Submitter: Zuul
Branch:    stable/pike"
1687027,2019-02-20 09:58:28 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/638121"
1687027,2019-02-20 09:57:59 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/638120"
1687027,2019-02-20 09:55:49 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/638117"
1687027,2019-02-20 09:55:34 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/638116"
1687027,2019-01-09 09:43:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/629420"
1687027,2019-02-14 10:14:01 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/629420
Reason: Let's try something different: https://review.openstack.org/636892"
1687027,2019-02-14 10:13:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/636892"
1687027,2019-02-23 03:53:03 UTC,"Reviewed:  https://review.openstack.org/638117
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8bf3a905e7d05715a913587a9077615a733e5ec1
Submitter: Zuul
Branch:    stable/queens"
1687027,2019-01-03 14:58:31 UTC,"Today I checked one failed test, from http://logs.openstack.org/30/626830/9/check/neutron-functional/e66470c/logs/dsvm-functional-logs/neutron.tests.functional.db.test_migrations.TestModelsMigrationsMysql.test_check_mysql_engine.txt.gz and compared it with same test which passed: http://logs.openstack.org/85/624685/2/check/neutron-functional/fede00f/logs/dsvm-functional-logs/neutron.tests.functional.db.test_migrations.TestModelsMigrationsMysql.test_check_mysql_engine.txt.gz"
1687027,2018-12-21 16:21:27 UTC,This issue was fixed in the openstack/neutron 14.0.0.0b1 development milestone.
1687027,2018-12-17 23:44:39 UTC,"Reviewed:  https://review.openstack.org/625556
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0a4d2ee87721da4472099c1043c0146a9e02ee6d
Submitter: Zuul
Branch:    master"
1687027,2019-02-20 05:59:55 UTC,"Reviewed:  https://review.openstack.org/636892
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c0fec676723649a0516cf3d4af0dccc0fe832095
Submitter: Zuul
Branch:    master"
1687027,2019-02-23 03:53:13 UTC,"Reviewed:  https://review.openstack.org/638116
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e6f22ce81c0a1130d45d290b185b736501e6dd1e
Submitter: Zuul
Branch:    stable/rocky"
1687027,2019-04-09 20:08:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/651371"
1687027,2019-04-01 15:11:57 UTC,With last patch https://review.openstack.org/636892 I think we mitigate this issue as much as we could and we can now mark it as fixed.
1687027,2019-04-09 19:43:09 UTC,"Even with added recently skip_if_timeout decorator those tests are failing from time to time and it looks that it may happen that different type of exception is raised in such case.
For example: http://logs.openstack.org/73/636473/25/check/neutron-functional-python27/0ef9362/testr_results.html.gz"
1687027,2019-04-11 04:16:07 UTC,"Reviewed:  https://review.openstack.org/651371
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b7458b615972dc6ff93a12abbd0a8f32e8da55eb
Submitter: Zuul
Branch:    master"
1687027,2019-04-11 07:21:54 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/651704"
1687027,2019-04-11 07:22:10 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/651705"
1687027,2019-04-11 07:22:25 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/651706"
1687027,2019-04-11 07:22:39 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/651707"
1687027,2019-04-11 19:21:46 UTC,"Reviewed:  https://review.openstack.org/651704
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=56974308424728637ab0303198036022c8568309
Submitter: Zuul
Branch:    stable/stein"
1687027,2019-04-12 05:08:48 UTC,"Reviewed:  https://review.openstack.org/651705
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=14ed5515b9a3fbc01d03270dfcc210586e781bc4
Submitter: Zuul
Branch:    stable/rocky"
1687027,2019-04-12 05:08:58 UTC,"Reviewed:  https://review.openstack.org/651706
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3d434814ef52a1393f8eb0f33672ae51188f7178
Submitter: Zuul
Branch:    stable/queens"
1687027,2019-04-15 16:38:18 UTC,"Reviewed:  https://review.openstack.org/651707
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d6189d3bc32a130b4941ff3e1333d42d4e7f1b13
Submitter: Zuul
Branch:    stable/pike"
1687027,2019-05-08 14:08:41 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657813"
1687027,2019-05-12 15:29:02 UTC,"Reviewed:  https://review.opendev.org/657813
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d83bb4f160ed7b85a6be8ae490dba1d9ec8c5561
Submitter: Zuul
Branch:    master"
1687027,2018-12-17 11:23:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625556"
1687027,2019-02-23 12:04:18 UTC,"Reviewed:  https://review.openstack.org/638121
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=55daaeca3e94aab0c27b82e59c79f182dd3ec1ea
Submitter: Zuul
Branch:    stable/ocata"
1687027,2018-12-14 12:28:43 UTC,"Reviewed:  https://review.openstack.org/624685
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b75cf8743cb4231c3a9bf9a34a58a083924ccf3b
Submitter: Zuul
Branch:    master"
1687027,2018-10-17 15:20:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/611357"
1687027,2018-11-06 06:13:26 UTC,This issue was fixed in the openstack/neutron 12.0.5 release.
1687027,2018-04-20 12:25:00 UTC,No hits in last 30 days for such error: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22IndexError%3A%20tuple%20index%20out%20of%20range%5C%22%20AND%20build_name%3Aneutron-functional
1687027,2018-04-26 19:18:59 UTC,Got a fresh hit at http://logs.openstack.org/59/563159/4/check/neutron-functional/1dd8b0d/logs/testr_results.html.gz
1687027,2018-06-26 10:59:46 UTC,"I think I just spotted similar issues at least twice:
http://logs.openstack.org/58/574058/10/check/neutron-functional/f38d685/logs/testr_results.html.gz
http://logs.openstack.org/61/567461/4/check/neutron-functional/81d69a4/logs/testr_results.html.gz"
1687027,2018-10-10 09:41:07 UTC,Another hit of this issue: http://logs.openstack.org/67/597567/21/check/neutron-functional/d28a948/logs/testr_results.html.gz
1687027,2018-10-12 10:50:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/610003"
1687027,2018-10-17 14:58:55 UTC,"Reviewed:  https://review.openstack.org/610003
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c2c37272bf788aac63399127cddd487dc0f15c38
Submitter: Zuul
Branch:    master"
1687027,2018-10-17 15:16:10 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611354"
1687027,2017-04-28 14:16:48 UTC,"In good runs, mysql flavours of the test work just fine, not taking much longer than postgresql."
1687027,2018-10-17 15:23:43 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/611358"
1687027,2018-10-17 15:24:20 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/611360"
1687027,2018-10-18 11:56:51 UTC,"Reviewed:  https://review.openstack.org/611354
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=026d911832256fa2f79ff808b99d578e43dd2c7f
Submitter: Zuul
Branch:    stable/rocky"
1687027,2018-10-18 11:57:01 UTC,"Reviewed:  https://review.openstack.org/611357
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=db07fe8698dc24b8a6b7f09a96492d1bb959cc74
Submitter: Zuul
Branch:    stable/queens"
1687027,2018-10-18 11:57:11 UTC,"Reviewed:  https://review.openstack.org/611360
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1cb8901b4213648a7fec1978e98905c6eac8bcd9
Submitter: Zuul
Branch:    stable/ocata"
1687027,2017-09-19 15:41:25 UTC,Can https://bugs.launchpad.net/neutron/+bug/1693950 be related?
1687027,2018-10-19 19:54:18 UTC,"Reviewed:  https://review.openstack.org/611358
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f26eed6677965de51fe8d88f9750c1b6a5becce5
Submitter: Zuul
Branch:    stable/pike"
1687027,2018-10-22 21:03:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612505"
1687027,2018-10-25 03:38:45 UTC,"Reviewed:  https://review.openstack.org/612505
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c39afbd5fcdfff2ad5e7f6963768da9f3d8027d2
Submitter: Zuul
Branch:    master"
1687027,2018-10-25 07:43:33 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/613230"
1687027,2018-10-25 07:43:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/613231"
1687027,2018-10-25 07:44:00 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/613232"
1687027,2018-10-25 07:44:13 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/613233"
1687027,2018-10-25 19:47:43 UTC,"Reviewed:  https://review.openstack.org/613232
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3eaaf0756cd1a422f03ebdfe2d8a55bb69e115e7
Submitter: Zuul
Branch:    stable/pike"
1687027,2018-10-26 12:45:20 UTC,"Reviewed:  https://review.openstack.org/613231
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6a9450b2036808748668a3439fdcebb77f071c5f
Submitter: Zuul
Branch:    stable/queens"
1687027,2018-10-27 11:47:22 UTC,"Reviewed:  https://review.openstack.org/613233
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1a3cc6e810e02a5b0aaa3bf948aebb1f29cf8f80
Submitter: Zuul
Branch:    stable/ocata"
1687027,2018-10-29 15:51:57 UTC,Still happening: http://logs.openstack.org/88/555088/29/check/neutron-functional/0b00b31/job-output.txt.gz#_2018-10-25_22_18_28_107639
1687027,2018-10-30 15:20:17 UTC,"Reviewed:  https://review.openstack.org/613230
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=63ebee37bbcf8b780210b7d923c5ce4f1591c345
Submitter: Zuul
Branch:    stable/rocky"
1687027,2018-11-06 06:08:06 UTC,This issue was fixed in the openstack/neutron 13.0.2 release.
1687027,2018-11-06 06:09:03 UTC,This issue was fixed in the openstack/neutron 11.0.6 release.
1687027,2018-10-22 20:56:41 UTC,It looks that in some cases such test can take longer than 300 seconds and there are still failures there. See: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22in%20test_walk_versions%5C%22%20AND%20filename%3A%5C%22job-output.txt%5C%22
1687027,2018-12-12 12:27:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624685"
1687034,2018-01-18 08:18:12 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1973
1687034,2017-05-01 01:49:34 UTC,This is due to involvement of the function that is local to the node.
1687035,2017-04-28 15:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1687039,2017-05-01 00:45:55 UTC,"Hey David, Thanks for the report."
1687039,2017-05-01 02:24:04 UTC,"I actually did something very similar to your version initially! In our case we're explicitly calling the __enter__ and __exit__ in the setUp and tearDown methods, not using a fixture, but the effect is similar. I had a pull request adding some tests which add mocks to the same mocker the way your example does, and a colleague objected to it in code review, b/c my equivalent of ""self.requests_mock.get('https://test.com/path', json={})"" isn't called inside a context manager."
1687039,2017-05-01 02:42:27 UTC,I should have also mentioned-- thanks for your work on this library! I really appreciate having it.
1687039,2017-05-01 08:01:29 UTC,"Thanks, it's always nice to here that people are using your stuff (even the problems)."
1687039,2017-08-28 11:29:10 UTC,"Hi. I'm a relatively new to requests_mock and also have an interest in this discussion.
First of all, thanks a bunch for providing this library and maintaining it. As David said, it is much appreciated."
1687039,2017-09-04 00:02:12 UTC,"So I'm still not entirely sure how to handle the nested mock situation, and I'm wary of changing behaviour that i've had people argue on both sides for."
1687048,2018-08-29 01:30:26 UTC,"Reviewed:  https://review.openstack.org/462905
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=7e5916ecdd89a0783ece2675704f701fbe845550
Submitter: Zuul
Branch:    master"
1687048,2018-01-12 19:04:06 UTC,Unassigning due to no activity for > 6 months.
1687048,2017-07-11 23:30:17 UTC,"Reviewed:  https://review.openstack.org/462902
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=c7fdc4d459a0bd09869bcc31f45499aa3274c760
Submitter: Jenkins
Branch:    master"
1687048,2017-06-29 09:31:48 UTC,"Reviewed:  https://review.openstack.org/461471
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=15eb00fc1e003868cd94dc9d83b155aaa5e34168
Submitter: Jenkins
Branch:    master"
1687048,2017-05-10 11:28:54 UTC,"Hmm, just took a quick look at the nfs driver. I think it has the same issue: it's resizing the base image instead of the latest qcow2 image (when having snapshots)."
1687048,2017-05-10 10:06:39 UTC,"@Silvan: thanks for sending this. It just needs a few small changes: checking the image format and resizing the latest image from the chain (as it is now, it's resizing the base image, corrupting the chain)."
1687048,2017-05-05 10:27:44 UTC,"@Lucian: Pls check https://review.openstack.org/#/c/462902/ , now a separate change for the SMBfs fix."
1687048,2017-05-05 10:26:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462905"
1687048,2017-05-05 10:21:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462902"
1687048,2017-05-04 11:07:27 UTC,"@Lucian:
Please check out the submitted change at https://review.openstack.org/#/c/461471/ and see how that needs to be adopted for the SMB driver. If you want to submit a different patch for the SMB driver just drop me a note and I'll remove the SMB related changes from the patch."
1687048,2017-05-04 10:22:24 UTC,This is a known limitation of the SMB driver as we're using differencing vhd/x images for snapshots.
1687048,2017-05-03 13:07:05 UTC,Regarding tempest status going invalid: No skipping of a test because some drivers fail on it.
1687048,2017-05-03 12:45:11 UTC,"Change abandoned by Silvan Kaiser (<email address hidden>) on branch: master
Review: https://review.openstack.org/461466
Reason: Not skipping a test because of some drivers having issues."
1687048,2017-05-01 18:13:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461471"
1687048,2017-05-01 17:53:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461466"
1687048,2017-05-01 17:18:34 UTC,Quite possible some of the drivers may hit #1687044 after this issue has been solved. This issue is an explicit check that intentionally fails on the given scenario.
1687048,2017-04-28 18:01:49 UTC,Maybe https://bugs.launchpad.net/cinder/+bug/1687044 is related.
1687057,2020-12-11 15:07:02 UTC,As I hit this with apache2 I tried to figure out a solution.
1687057,2020-06-29 13:03:02 UTC,"On Mon, Jun 29, 2020 at 12:37:33PM -0000, Paride Legovini wrote:

> The official git FAQ [1] suggest using an en .gitignore file as a
> placeholder for empty directories. This is also what git-svn does, see
> the --placeholder-filename option in git-svn(1).
"
1687057,2020-06-29 12:39:27 UTC,typo fix: an *empty* .gitignore file
1687057,2020-06-29 12:37:33 UTC,"The official git FAQ [1] suggest using an en .gitignore file as a placeholder for empty directories. This is also what git-svn does, see the --placeholder-filename option in git-svn(1)."
1687057,2020-06-26 19:24:46 UTC,"Christian's right that 99% of suggestions are to add a .gitkeep or similar, but found a couple other kludgy workaround ideas:"
1687057,2020-06-26 18:43:33 UTC,There may also be old branches affected as well
1687057,2017-05-02 13:45:23 UTC,"I haven't looked at the others yet, but for the exim4 case that is a dir called ""Local"".
BTW this easily finds offenders:
 $ find . -depth -empty"
1687057,2018-02-26 12:07:57 UTC,also affects apache2 (xenial at least)
1687057,2017-05-01 16:07:09 UTC,"Affects src:apparmor, src:gettext, src:ssl-cert, src:supermin,"
1687057,2017-05-02 13:23:48 UTC,Also affects src:exim4.
1687057,2019-07-11 19:28:50 UTC,Also affects samba ?
1687057,2018-02-20 15:13:09 UTC,also affects nmap
1687057,2017-05-02 13:49:44 UTC,"well the empty also spots empty files :-/, but one can add ""-type d"" to fix that."
1687063,2018-03-27 13:51:46 UTC,"It looks to me as if this is working as designed, please explain your use case in more detail if you think otherwise."
1687063,2018-03-27 14:14:57 UTC,"Hello j-harbott,"
1687063,2018-03-27 14:47:34 UTC,The reason for this seems that there is this guard against empty arguments here:
1687063,2018-03-27 14:48:54 UTC,Actually I think that we could place a check into localrc_set to generate a warning or maybe an error there.
1687063,2018-03-27 17:01:03 UTC,"Sounds good to me! But unless what we did was not valid (empty value for an option), I would like if there was a documented way of providing empty values for options."
1687064,2017-04-28 16:49:58 UTC,"We should not suppress them, they do have value. They are DEBUG logs and they are DEBUG information useful for finding race conditions. We specifically go to work to enable these logs--suppressing them would just be never setting them up in the first place with the vlog monkeypatching."
1687064,2018-04-18 21:29:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/562385"
1687065,2018-05-15 17:43:53 UTC,"Reviewed:  https://review.openstack.org/562385
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7326717d36d31e2cc383b535a4af06f0dae9e56d
Submitter: Zuul
Branch:    master"
1687065,2018-06-07 22:13:48 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b2 development milestone.
1687065,2018-04-18 21:01:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/562385"
1687065,2018-04-18 21:11:54 UTC,"I posted a patch to just disable the ovsdb debug logging by default. There is ovsdbapp.backend.ovs_idl.fixtures.OvsdbVlogFixture which could be used in functional test setup. It wouldn't kill the thread, but would un-patch the logging. ovsdbapp now allows one to shut down the connection to OVS when you are done with it, so it would also be possible to set up an OvsdbConnection fixture that stops at the end of the test as well."
1687069,2017-05-07 17:26:16 UTC,Just some further feedback on the random freezes. Since forcing uxa not a single system freeze.
1687070,2017-04-29 09:32:17 UTC,"Aparent the path to the socket is too long - I wasn't aware of a limit that would occur in practical circumstance, will need to find out what the restrictions are."
1687070,2017-04-29 13:16:35 UTC,"On 4/29/17 5:32 AM, Jaap Karssenberg wrote:

> print SERVER_ADDRESS % COUNTER
"
1687070,2017-04-30 06:52:24 UTC,"Thanks, looks indeed that the total path is too long."
1687070,2017-05-01 11:49:06 UTC,I've read that /var/folder is a temporary folder that survives reboot on MacOS.
1687070,2017-05-01 14:14:54 UTC,"Of course, but would like to confirm that reducing the path length indeed
fixes the issue."
1687070,2017-05-01 14:28:48 UTC,"On 5/1/17 10:14 AM, Jaap Karssenberg wrote:

> Of course, but would like to confirm that reducing the path length indeed
> fixes the issue.
"
1687070,2017-05-02 07:09:12 UTC,"Went with 8, but same idea :)"
1687070,2017-07-26 15:15:20 UTC,"I am suggesting to try ""Long Path Tool"" program."
1687085,2017-04-28 18:25:22 UTC,"Man, it's still going. This is crazy slow."
1687089,2017-09-22 04:44:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687095,2017-05-02 10:41:48 UTC,"There are multiple levels of ""not so easy"" here."
1687095,2017-05-02 10:42:40 UTC,Also added the FYI to the Debian bug that handled this issue.
1687095,2018-07-23 18:42:20 UTC,Is any fix to this available?
1687095,2018-07-23 18:52:49 UTC,"Ugh, this has been open for 14 months, so I guess not."
1687095,2018-07-24 14:10:45 UTC,"The change from pssh to parallax was done by upstream in Jan 2015:
* Fri Jan  9 2015 Kristoffer Grönlund <email address hidden> and many others
...
- high: crm_pssh: Switch to python-parallax over pssh (bnc#905116)"
1687095,2019-09-03 21:51:57 UTC,In Eoan:
1687095,2019-09-19 13:01:24 UTC,I'm dropping this from server-next because this fits the regular ubuntu-server queue purposes instead. Its importance is low in that queue (due to pcs being chosen as the platform to go when configuring crm and this crmsh sub command not being so commonly used).
1687101,2017-04-28 21:15:37 UTC,This bug was fixed in the package gnome-documents - 3.24.0-0ubuntu2
1687116,2018-01-22 20:49:24 UTC,Merge Proposal -> https://code.launchpad.net/~billy-olsen/nrpe-charm/+git/nrpe-charm/+merge/334727
1687116,2017-09-06 08:38:11 UTC,"@paulgear, I found why I couldn't find ""define service"" part on nrpe charm,"
1687116,2017-09-05 09:34:02 UTC,@xtrusia: Better to use the NRPE module in charmhelpers than implement it yourself: http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/charmsupport/nrpe.py
1687116,2017-09-19 16:51:23 UTC,In investigating this issue I've found that local monitors were not getting added in /etc/nagios/nrpe.d on each nrpe host.
1687116,2017-08-17 21:21:24 UTC,"Just to make a distinction since nrpe is a charm as well as a sub-system of Nagios: Customer is seeking custom nrpe ""checks"" as opposed to ""hooks"" which is a construct of the charm.  A check is called by the Nagios server.  Having the ability to have Juju manage customer-specific NRPE checks, will discourage the user from managing NRPE via both Juju and something else like Ansible."
1687116,2017-06-02 02:00:59 UTC,Next steps are to reproduce the symptoms.  Discussed with @billy-olsen and he's going to look for a test case or example deployment.
1687116,2017-09-05 08:28:24 UTC,I'm playing with this charm code
1687116,2017-08-15 20:10:37 UTC,"I was able to investigate and reproduce this issue. When configuring monitors=<monitor syntax> as well as setting export_nagios_definitions=True, I am expecting the nrpe charm to write out nagios definitions in /var/lib/nagios/export for those monitors. So far I am not seeing any of the nagios definitions written out to /var/lib/nagios/export for the monitors even if there is a relation with nagios and I see the monitors in the nagios dashboard."
1687116,2017-07-14 15:53:27 UTC,"I have been working with Billy on this request.  The thought is the following could be the YAML supplied in the ""monitors"", or similar new, config option:"
1687122,2017-04-28 22:32:58 UTC,This is a crash that recently started appearing in the Error Tracker the Traceback contains the following:
1687130,2019-10-27 04:17:35 UTC,[Expired for linux (Ubuntu Zesty) because there has been no activity for 60 days.]
1687130,2019-10-27 04:17:33 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1687130,2019-08-27 17:38:08 UTC,Thanks for reporting this bug and helping to make Ubuntu better.
1687130,2017-05-01 20:46:08 UTC,"Of the kernels in the mainline ppa i can at the moment confirm that none above v4.8.17 works (ie 4.8.17-040817-generic), and all of
- v4.9.24
- v4.9.25
- v4.10-rc1
- v4.10.8
- v4.10.12
- v4.10.13
have the bug present."
1687130,2017-05-03 21:42:05 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1687130,2017-04-29 07:46:09 UTC,apport information
1687130,2017-04-29 07:46:07 UTC,apport information
1687130,2017-04-29 07:46:06 UTC,apport information
1687130,2017-04-28 23:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1687130,2017-05-01 19:07:02 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1687130,2017-05-03 20:22:13 UTC,"Bug is still present in kernel 4.11.0-041100rc8-generic from ubuntu's mainline kernel ppa. Latest kernel that is unaffected are all kernels from the ubuntu 16.10 repos, and from the mainline kernel ppa 4.8.17-040817-generic ."
1687137,2017-05-21 15:36:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687175,2017-04-29 10:45:43 UTC,"It's a known issue in MSYS2 builds.
(The background is that we use a mingw-w64 based version of cmake that uses native Windows style paths but the version of bzr is cygwin based and therefore uses cygwin style paths - as bzr is stupid it chokes immediately when cmake invokes it with native Windows style paths)."
1687175,2019-05-26 12:58:24 UTC,Assuming fixed with migration to git and associated changes to inkscape-version.cmake: https://gitlab.com/inkscape/inkscape/commit/c7b8642bb62bbd4de6983c48e31e42c50a4e8001
1687178,2021-01-07 04:18:06 UTC,4.8 EOL
1687178,2017-05-05 13:11:58 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1687178,2018-05-08 18:06:59 UTC,This change was made by a bot.
1687180,2018-08-25 23:04:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687180,2017-04-29 12:28:05 UTC,"The attachment ""diff -U5 output of old and new version"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1687180,2018-03-25 23:03:09 UTC,"Just FYI, Fedora package has backported several patches to make it work with Wayland. Feel free to pull those patches into Debian/Ubuntu: https://src.fedoraproject.org/rpms/mypaint/tree/master"
1687187,2017-08-28 09:55:15 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1687187,2017-08-22 11:39:29 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1687187,2017-08-12 14:02:51 UTC,"Reviewed:  https://review.openstack.org/486272
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=16505d8e6e20159adc2bc6df81d2f415cffe83fe
Submitter: Jenkins
Branch:    stable/ocata"
1687187,2017-07-28 07:40:11 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1687187,2017-07-22 01:39:54 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/486273"
1687187,2017-08-11 20:12:45 UTC,"Reviewed:  https://review.openstack.org/486273
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3d889bbfcee42aec08ed746163157f13ed36955f
Submitter: Jenkins
Branch:    stable/newton"
1687187,2017-07-20 12:30:21 UTC,"Reviewed:  https://review.openstack.org/480765
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b7cb3b7523b70dd94135f07b6307fa48563119f8
Submitter: Jenkins
Branch:    master"
1687187,2017-07-05 22:57:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480765"
1687187,2017-07-05 22:18:03 UTC,"The problem here is that some parts of nova use the older style driver interface to configure networking (yet another pluggable python module thing), whereas most of nova uses the newer API interface. Antique remainders include the metadata server iptables thing, DHCP, and DNS."
1687187,2017-06-27 16:00:27 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1687187,2017-06-14 12:28:53 UTC,Should be fixed
1687187,2017-07-22 01:39:41 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/486272"
1687191,2017-06-14 05:48:31 UTC,"Hi, I got the exact same syslog message and also use a Lenovo ThinkPad X1 Carbon 5th Gen with Swedish keyboard. However, my trackpoint and mouse seem to work as expected. I.e., besides the syslog message. Two finger scrolling does as well. It also worked in 16.04, 16.10 and is currently working in 17.04 (upgraded two days ago). I have noticed the cursor skips in the text but have not excluded if it is the touchpad that is enabled while typing."
1687191,2017-04-29 13:09:28 UTC,apport information
1687191,2017-04-29 13:09:30 UTC,apport information
1687191,2017-04-29 14:01:35 UTC,`dmesg` log is filled with this:
1687191,2017-06-15 05:41:16 UTC,"FYI: while trying to get the ""disable keyboard while typing"" back online (is set to true in gconf and I'm testing  gnome now before 18.04) the touchpad got disabled for some reason. I only changed one setting in gconf which should not disable the touchpad on login. Had to reinstall xserver-xorg-input-synaptics and -libinput as well as running:"
1687191,2017-04-29 13:09:25 UTC,apport information
1687191,2017-06-15 21:51:19 UTC,"FYI: got a better experience in gnome when opening a terminal and running syndaemon -d in gnome. However, that seem to freeze the mouse slightly too long after I have stopped typing. The unity version works better (not sure what differs yet)."
1687191,2017-06-28 08:14:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687191,2017-06-28 11:33:32 UTC,"@Anders: No, my problem is different from yours: both trackpoint and touchpad is unusable. Some users claim this is fixed in psmouse Linux kernel module psmouse, from version 4.0.12-rc4. My only workaround is to use IMPS protocol, which works predictably (stable) with the drawback of all multiple touchpoints (two finger scroll, for instance) not being useable."
1687191,2017-06-30 10:24:04 UTC,"@Fredrik Ok, different problem then. I have tested some more now. It is still working good in most cases and it seems like disable while typing has improved as well (might be some update). However, I'm experiencing micro freezes/locks for the mouse (1-3 seconds) which is very annoying. I.e., everything is not perfect."
1687191,2017-06-15 06:23:22 UTC,"The ""disable keyboard while typing"" problem only affects Gnome (default) for some reason. In Unity (7) on Ubuntu 17.04 everything works perfectly."
1687191,2017-04-29 13:09:24 UTC,apport information
1687191,2017-04-29 13:09:09 UTC,apport information
1687191,2017-04-29 13:09:21 UTC,apport information
1687191,2017-04-29 13:09:20 UTC,apport information
1687191,2017-04-29 13:09:19 UTC,apport information
1687191,2017-04-29 13:09:18 UTC,apport information
1687191,2017-04-29 13:09:16 UTC,apport information
1687191,2017-04-29 13:09:15 UTC,apport information
1687191,2017-04-29 13:09:14 UTC,apport information
1687191,2017-04-29 13:09:13 UTC,apport information
1687191,2017-04-29 13:09:11 UTC,apport information
1687191,2017-04-29 13:09:07 UTC,apport information
1687191,2017-04-29 13:09:08 UTC,apport information
1687191,2017-04-29 13:09:22 UTC,apport information
1687194,2017-07-23 15:45:41 UTC,Confirmed on Ubuntu Gnome 17.04 along with workaround.
1687194,2017-05-25 06:17:43 UTC,"I also confirm that this bug exists. The workaround also worked, thanks."
1687194,2017-05-01 20:08:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687194,2017-05-23 11:50:55 UTC,I confirm the bug and the workaround on Gnome Ubuntu 17.04
1687195,2017-04-30 07:15:53 UTC,Arch Linux with KDE here. Same issue here.
1687195,2017-05-01 09:44:57 UTC,Patch in release_fixes 45ab3d8
1687195,2017-05-08 07:59:02 UTC,"Thanks Jaap, Zim works again."
1687207,2017-05-01 20:19:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687214,2020-11-09 12:29:22 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1687214,2021-01-09 04:17:39 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1687217,2017-12-20 15:18:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687217,2018-08-20 23:06:28 UTC,"More subtle, apparently a disconnect between the mysql timezone and the rest of the system timezone is created when using the above proposed solution.  ZoneMinder runs, and _most_ things work, but when reviewing event frames, they are stored under GMT timezone instead of the designated timezone, and then cannot be retrieved for playback with log messages like:"
1687219,2017-05-02 19:57:52 UTC,I may have encountered the same situation as you after the suspend. Font error can not see clearly. Hope this is fixed soon
1687220,2017-12-17 22:26:49 UTC,"Still happens in 17.10
The issue has been fixed,
http://banshee-media-player.2283330.n4.nabble.com/Media-import-crashes-Banshee-td4652627.html"
1687220,2018-05-24 05:58:47 UTC,"Still applies to 18.04, no fixes appear to have been released."
1687220,2017-08-24 16:21:35 UTC,"Same problem here.
This worked previously as I've currently got 51k+ songs in the library, but cannot add new media"
1687220,2017-05-31 12:38:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687220,2017-06-03 06:18:57 UTC,"Yes, that worked for me as well."
1687220,2017-05-31 12:49:06 UTC,"Not directly related to the bug, but as a workaround, I was able to ""import"" music by copying it into the location of the media library and re-analyse it."
1687220,2017-06-25 04:38:35 UTC,"I've been getting this crash as well (in 17.04). I don't know if it adds any useful information, but I've attached another log from: banshee --debug --show-import-media 2>&1 | tee /tmp/20172334-banshee.log"
1687236,2017-05-07 13:02:58 UTC,"This isn't due to libiconv, it's an incomplete implementation in lxml. See the difference between"
1687243,2017-09-11 08:25:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687245,2017-04-30 04:31:23 UTC,"Edit: I replicated this using a UHD monitor and two different computers driving my 4k monitor, same system specs."
1687245,2020-03-30 02:41:23 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1687246,2018-05-19 17:59:42 UTC,To get the same effect in Ubuntu 18.04 as 16.04 I used the tweak tool to set a text scaling of 1.3. Additionally I had to set a scaling in Firefox's about:config in the layout.css.devPixelsPerPx property to the same 1.3 value. It's annoying that this has been removed from the normal UI as the underlying feature is still there and works fine.
1687246,2018-07-30 04:47:50 UTC,I noticed that 18.04.1 has been released. Has there been any progress for providing fractional scaling (via the default GUI) like was offered in Ubuntu 16.04?
1687246,2018-09-10 01:49:52 UTC,Historically we use the tag 'hidpi' and not 'highdpi'. It doesn't hurt to have both but for searches you will find more under 'hidpi':
1687246,2018-09-10 06:30:07 UTC,"They had both been there from the start, but I typoed it into an ii when adding ""cosmic"" tag and so I restored the original"
1687246,2018-09-29 20:03:55 UTC,"What is left of this issue to be sorted, is there a way to track upstream progress on this ? From my testing many apps (non-gnome) get blurry when fractional scaling is enabled. So is that something those app developers will have to fix in their apps ?"
1687246,2018-09-29 21:09:14 UTC,"For my 15"" display with 3840*2160, without the workaround I get 100, 200 (too small), 300 (too large), and 400. Is it intentional that with the experimental workaround from the first comment enabled, I have 125, 150, 175 and 200% but nothing above it?
The maximum of 200% is too small and I use a 1.20 font scaling in Tweaks, so I'd be looking for an option to scale by 240%."
1687246,2018-10-01 04:12:22 UTC,"Mario: gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying. Please log a bug for it by running:"
1687246,2018-10-01 18:01:34 UTC,"Daniel, new gnome-control-center bug #1795483"
1687246,2018-11-28 14:04:46 UTC,"I'd like to air some disappointment. Whoever decided that we should be happy with 100,200,300% options is WRONG. We should have a field to enter 135 or 150 or 177, whichever works best for the screen size. I'm not able to use any latest Ubuntu releases on my laptop because of this decision. I'm currently forced to stay with Xubuntu that allows setting custom DPI."
1687246,2019-03-04 03:40:28 UTC,Is this really fixed in Ubuntu 18.04? I don't want to waste my time upgrading again unless fractional scaling truly supported.
1687246,2018-11-28 14:39:25 UTC,"I think 100,200 and 300% were the easiest to get done. The real issue is with fractional scaling, which KDE does better than others currently and then of course it depends how your GUI toolkit plays with fractional scaling."
1687246,2018-05-18 08:35:34 UTC,I am having this problem on ubuntu 18.04 on my dell precision m3800
1687246,2019-03-04 04:04:50 UTC,"I just install Ubuntu 18.04 in a virtual machine and updated it. I don't see a fix, I see the same disappointment:
https://i.imgur.com/tTanPlv.png"
1687246,2019-03-04 10:07:08 UTC,"No, it's not fixed in any Ubuntu version yet. The first part of the work just landed upstream and for wayland sessions only, that should be in the incoming Ubuntu Disco version first and unsure it's going to be something that is possible to SRU since it involves quite some refactoring."
1687246,2019-03-13 23:02:55 UTC,"I have this now on Disco in Wayland and with update to mutter 3.32 (incl. proposed, except gnome-settings-daemon at 3.31.91-1ubuntu1), but apparently I had to add scale-monitor-framebuffer to the gsettings key org.gnome.mutter.experimental-features (as mentioned by https://www.omgubuntu.co.uk/2019/03/best-gnome-3-32-features). Is this expected?"
1687246,2019-03-13 23:08:23 UTC,"(Note that adding scale-monitor-framebuffer to experimental mutter settings was already the workaround mentioned in Bug Description, so not new)"
1687246,2019-03-14 07:19:25 UTC,"Sorry for spamming, I should have clicked the source link on OMGUbuntu, experimental is apparently expected: https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/"
1687246,2019-04-21 10:41:04 UTC,So now we have another Ubuntu release: 19.04.
1687246,2020-07-25 14:23:14 UTC,Is this fixed now in Focal? I see fractional scaling in gnome-control-center.
1687246,2018-11-28 14:27:47 UTC,I agree with sergeiS 225%. Not 200%! Long live Ubuntu 16.04.5 and Unity 7!
1687246,2018-05-07 07:16:43 UTC,"No, the behaviour should be mostly identical between Wayland and Xorg sessions. You may notice some differences but if you do then that's probably a bug."
1687246,2018-09-29 20:06:02 UTC,"I may add that I believe we probably need more scaling steps than 125, 150, 175 and 200. On my Thinkpad X1C with 14"" display and 1080p resolutions 125% is still ""too small"" and 150% is too large."
1687246,2018-05-07 02:59:51 UTC,Note to all readers:
1687246,2018-05-07 06:42:58 UTC,"Doesn't that work-around only apply to Wayland, while the default GNOME3 desktop in Ubuntu 18.04 is Xorg?"
1687246,2017-04-30 18:57:27 UTC,Here's Reddit threads showing several dozen people complaining about this exact same thing:
1687246,2017-04-30 19:14:41 UTC,"Yes, the GNOME developers know about this issue. My understanding is that they intend to work on this for GNOME 3.26."
1687246,2017-06-24 19:57:41 UTC,Should this bug be marked duplicate of this? https://bugs.launchpad.net/ubuntu-gnome/+bug/1687245
1687246,2017-06-26 01:53:57 UTC,"No, I think bug 1687245 might be a slightly different issue. And even if it was the same issue as this one, this bug has more details so should remain the primary bug for fractional scaling. But again, it's possible the lock screen scaling is a different problem."
1687246,2017-06-26 20:09:44 UTC,One more potentially related bug just so it's on here: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1687253
1687246,2017-06-29 16:21:05 UTC,Work is ongoing on fractional scaling: http://blog.3v1n0.net/informatica/linux/gnome-fractional-and-multi-monitor-scaling-hackfest-the-report/
1687246,2017-11-29 01:47:03 UTC,Any news on this?
1687246,2017-11-29 03:30:43 UTC,It's working for me in Ubuntu 17.10 - gnome-settings lets me choose scaling between 100% and 200% in 25% increments for each monitor separately (and it defaults to 200% on my 4K screen with my 1920x1080 screen attached). You might have to change a setting for it to work - see http://www.omgubuntu.co.uk/2017/09/enable-fractional-scaling-gnome-linux.
1687246,2018-01-24 15:18:08 UTC,"Will the work being done here benefit GNOME installs in general (e.g., Gnome-shell without Ubuntu), or does it only apply to Ubuntu installs)?"
1687246,2017-04-30 07:19:22 UTC,"It would probably also be a good idea to noninteger values under 1 as well, because that would be important to making raspberry pi type stuff function correctly, and with the IoT boom that's probably going to be a thing. It'd also just be nice on netbook sized laptops."
1687246,2018-02-20 06:22:59 UTC,Is this going to come to 18.04? I used the beta and it's not there.
1687246,2018-03-16 15:54:55 UTC,"+1, using Ubuntu 18.04-beta here and it's not there."
1687246,2018-04-25 19:35:25 UTC,"This is my number one complaint for 18.04 and GNOME3. I'll be using 16.04.4 until 2021, or until it can compete with the perfection that is the Unity desktop (which supports fractal scaling)."
1687246,2018-04-25 19:50:49 UTC,I have updated the bug description with steps to enable the experimental feature. This feature is not fully complete in GNOME yet and will not be enabled by default or supported in Ubuntu 18.04 LTS. Apologies for the inconvenience.
1687246,2018-04-28 01:52:45 UTC,"I had it manually enabled in Gnome on 17.10 and just upgraded to 18.04. On Wayland, I'm noticing fractional scaling went from pretty good to broken; many fonts (even the datetime on the top of the screen) are now pixelated on 150% scaling."
1687246,2018-05-03 12:40:59 UTC,Lack of fractional scaling is a significant feature regression relative to 17.10 with Unity for those of us with hidpi displays. What can users do to show support for getting solved?
1687246,2018-05-03 13:35:49 UTC,"You should not only be able to have different fractal scaling for each monitor, but you should also be able to have fractal scaling for each separate window you launch."
1687246,2018-05-04 01:29:43 UTC,I also recall SGI workstations had some nice arbitrary scaling in the 1990's.
1687246,2018-05-04 12:54:44 UTC,Another consideration are users with Nvidia graphics.
1687246,2018-01-24 16:45:29 UTC,"It's done at gnome-shell / mutter level and worked upstream, so everyone using GNOME (w/ wayland) will get it."
1687253,2020-01-17 02:17:35 UTC,Is this problem still happening in current Ubuntu releases?
1687253,2020-03-17 04:17:25 UTC,[Expired for gnome-desktop (Ubuntu) because there has been no activity for 60 days.]
1687253,2020-03-17 04:17:27 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1687253,2020-03-17 04:17:29 UTC,[Expired for Ubuntu GNOME because there has been no activity for 60 days.]
1687255,2018-03-26 03:47:50 UTC,"I just tried with Ubuntu 18.04 daily builds and the bug is still present, could anybody care to comment if this bug is ever going to be fixed or not?"
1687255,2017-10-29 08:33:05 UTC,I just tried with Ubuntu 17.10 (mate edition) and the bug is still present...
1687256,2019-10-03 08:54:58 UTC,"I'm closing this with Won't fix.
If the issue still exist, please file a new bug.
Thanks"
1687256,2019-10-03 08:54:13 UTC,"4.8 has reached EOL.
Please give the supported version (19.04 Disco / 18.04.3 Bionic) a try."
1687256,2017-05-11 14:59:19 UTC,"Can you share your laptop's vendor name and product name?
The dmi string isn't really helpful."
1687256,2017-05-11 11:51:12 UTC,"Thanks for your patience, the touchpad is then recognised."
1687256,2017-05-11 09:30:32 UTC,type -> typo ...
1687256,2017-05-11 09:28:24 UTC,"Okay, it's a type in the commit log. Use this instead:
echo -n ""byd"" > /sys/bus/serio/devices/serio1/protocol"
1687256,2017-05-09 06:31:52 UTC,Maybe it's not exactly serio1? Maybe it's 0 or 2 or something.
1687256,2017-05-09 06:11:42 UTC,"I have tried this:   echo -n ""byd"" > /sys/bus/serio/devices/serio1/drvctl"
1687256,2017-05-03 21:40:09 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1687256,2017-05-06 19:32:33 UTC,"Thanks for the help and advice so far. Before making an upstream bug report I would like to be sure that is necessary, as I believe the problem relates to the patch referred to in bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424293.
What has actually happened is that my touchpad has reverted to the condition prior to BYD patch implementation described in this bug report."
1687256,2017-05-05 08:17:28 UTC,"Use ""sudo -s"" to get root permission first."
1687256,2017-05-04 20:26:22 UTC,"I have just tried that and get ""Permission denied"""
1687256,2017-05-04 06:47:57 UTC,"Did you try this command, as commit log suggested?
echo -n ""byd"" > /sys/bus/serio/devices/serio1/drvctl"
1687256,2017-05-01 19:56:45 UTC,kernel-bug-exists-upstream
1687256,2017-04-30 10:39:11 UTC,apport information
1687256,2017-04-30 11:00:12 UTC,This change was made by a bot.
1687256,2017-04-30 08:28:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1687256,2017-04-30 10:38:59 UTC,apport information
1687256,2017-04-30 10:39:01 UTC,apport information
1687256,2017-04-30 10:39:03 UTC,apport information
1687256,2017-04-30 10:39:05 UTC,apport information
1687256,2017-04-30 10:39:06 UTC,apport information
1687256,2017-05-01 18:56:24 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1687256,2017-04-30 10:39:09 UTC,apport information
1687256,2017-04-30 10:39:13 UTC,apport information
1687256,2017-04-30 10:39:14 UTC,apport information
1687256,2017-04-30 10:39:15 UTC,apport information
1687256,2017-04-30 10:39:20 UTC,apport information
1687256,2017-04-30 10:39:23 UTC,apport information
1687256,2017-04-30 10:39:08 UTC,apport information
1687257,2017-05-07 18:19:49 UTC,"Thank you, that works to install steam, though installing steam via the deb provided on steams website still doesn't work though and it's well documented:"
1687257,2017-05-06 05:52:58 UTC,AMDGPU pro does support 16.04 and it's still not an option for on it in 16.04.2 Gnome.
1687257,2017-05-06 06:45:49 UTC,"Justin, you should be able to run steam in Ubuntu 16.04 LTS."
1687257,2017-04-30 17:03:02 UTC,Is there any reason that 17.04 shouldn't be able to use a 16.04 driver and is this already being done on 16.04?
1687257,2017-04-30 08:44:23 UTC,AMDGPU Pro doesnt yet support 17.04 yet afaik.
1687257,2017-04-30 17:15:46 UTC,"Also, has the bug keeping people from running steam in 16.04 been resolved yet; I know its been reported? Thats why I switched to 17.04, and having to choose between a distribution version that supports steam and one that supports drivers for one of the most popular current video cards is a problem."
1687259,2017-04-30 08:32:51 UTC,"That is not an error message, its just the normal boot process. However it should be hidden by plymouth (which shows the Ubuntu GNOME logo spinner), which doesnt seem to be running on your machine."
1687259,2017-04-30 08:47:27 UTC,"Given that I'm running Ubuntu Gnome 17.04 without modificatoin doesn't that imply some sort of issue with the 17.04 release, especially since the gnome logo appears later? The logo also doesnt visuslly spin on either system I instslled 17.04 on, I dont know it that means sometginf is wrong or not."
1687259,2017-05-06 05:45:38 UTC,"Doesn't occur on Ubuntu 16.04.2, unique bug to 17.04."
1687259,2017-06-24 19:56:01 UTC,"Replicated by a bunch of other programmers intallting 16.04.2 on laptops in their office on their own, confirming"
1687259,2017-06-24 19:56:36 UTC,In my office on their own*
1687262,2017-09-08 22:00:05 UTC,Thank you for taking the time to file a bug report on this issue.
1687262,2017-09-12 20:15:16 UTC,Looks like duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547
1687262,2017-09-11 14:48:36 UTC,"Can you also test the 4.13 final kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13"
1687262,2017-09-08 21:42:51 UTC,Upgraded to artful beta - the issue persists.
1687262,2017-09-11 18:37:10 UTC,"@Joseph: no point, as indicated multiple times, network card works with current kernel 4.12.0-13, when configured in /etc/network/interfaces"
1687262,2017-07-02 04:17:43 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1687262,2017-07-02 04:17:42 UTC,[Expired for linux (Ubuntu Zesty) because there has been no activity for 60 days.]
1687262,2017-05-03 00:08:13 UTC,"Live Ubuntu 17.04 session is running OK (mentioned in original report) and it is using:
---------------------------------
$ apt-cache-policy linux-image-generic
linux-image-generic:
  Installed: 4.10.0.19.21
  Candidate: 4.10.0.19.21
  Version table:
 *** 4.10.0.19.21 500
        500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
        100 /var/lib/dpkg/status
$ uname -a
Linux ubuntu 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
---------------------------------"
1687262,2017-07-02 08:55:26 UTC,Bug is still relevant.
1687262,2017-05-01 18:57:27 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1687262,2017-04-30 08:00:16 UTC,This change was made by a bot.
1687266,2017-05-07 13:04:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687268,2017-05-01 17:02:34 UTC,Thank you for taking the time to file a bug report.
1687268,2017-05-01 16:47:01 UTC,From log:
1687270,2020-11-09 12:29:53 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1687270,2020-11-09 13:14:11 UTC,"Independent of the tracker transition, some feedback to your report: from what you described so far, the most common cause for the behaviour you described is a simple file permission issue on host side. Please check which user your qemu process is running with there, then ensure that the files you want to be able to access from guest by 9p has the appropriate file permissions for that user on host side."
1687270,2021-01-09 04:17:41 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1687273,2017-08-12 01:17:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687273,2017-07-27 19:53:33 UTC,"seems to be resolved, issue did not occured again"
1687273,2017-07-17 12:55:11 UTC,The patch posted in comment #19 was included in mainline as commit 62a6cfddcc0a5313e7da3e8311ba16226fe0ac10 and was cc'd to upstream stable.
1687273,2017-07-16 19:17:18 UTC,"any chance to get this resolved after no response at all, @Joseph Salisbury? i'm affected too"
1687273,2017-06-25 09:41:34 UTC,"still no update, any chance to get this fixed?"
1687273,2017-06-13 07:48:46 UTC,any update? what is necessary to include this patch?
1687273,2017-06-01 08:36:38 UTC,"The attachment ""fix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1687273,2017-06-01 08:19:02 UTC,This is some sort of race condition every 15 minutes causes a flood/ddos and will break the connection
1687273,2017-05-29 00:05:14 UTC,"Updating the kernel to the latest version did not fix the problem for me, unfortunately. This is still quite unacceptable, not being able to access essential files and folders!"
1687273,2017-05-26 21:47:56 UTC,"Hello,
i today i upgraded all my Systems and i was affected by this problem. Filesystem is a Windows Server 2016 Datacenter. All my Ubuntu releases have problems (16.04 LTS, 16.10 and 17.04)."
1687273,2017-05-26 19:10:19 UTC,This problem hit me on a xenial install with HWE and linux-generic-hwe-16.04 with generic kernels 4.8.0-52 and 4.8.0-53. Problem is alleviated by using the mainline kernel 4.12-rc2.
1687273,2017-05-19 16:55:36 UTC,I've had some luck adding this line to my crontab:
1687273,2017-05-19 05:11:16 UTC,"Please try latest mainline kernel, http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/"
1687273,2017-05-18 23:58:27 UTC,"I've mounted the following shared drive at around 8 am, it work fine then. This is now 10 am and the shared drive has started stall. The CIFS drive debug gave me the following messages:"
1687273,2017-05-18 23:55:45 UTC,"Another problem is that since the CIFS shared drive is mounted. It causes the Nautilus File Explorer to crash, this slows down all my processes on my computer, rendering my computer unable to work at all. It needs to be restarted about every 3 hours after that. Completely rendering us not being able to work efficiently. I have to spend precious work time copying over the files from my shared drive to my local computers, make sure that the files are copied correctly and connection did not died or failed. This is not practical."
1687273,2017-05-18 23:47:05 UTC,"This is a huge issue for me as I cannot access my shared drives from my Ubunut computer. If every computer updates have an issue like this, this will have big impact on peoples work. I think this is a critical issue that needs to be addressed asap."
1687273,2017-05-17 22:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1687273,2017-05-08 23:17:40 UTC,"Reverting to kernel (GNU/Linux 4.4.0-72-generic x86_64) undoes the damage this bug causes. My shares were disconnecting in about 5 minutes from mount. Quite annoying.
Confirmed 4.4.0-75 and 4.4.0-77 are both affected."
1687273,2017-05-06 07:13:24 UTC,"Upgrading to SMB version 3 seems to have fixed it, now running stable since 12 hours whereas the mount point went away after approx. 50 minutes with the old version.
Current mount options:
iocharset=utf8,rw,credentials=/path,uid=0,gid=0,file_mode=0660,dir_mode=0770,vers=3.0"
1687273,2017-05-05 18:04:42 UTC,"Not sure if this helps. This is what DebugData looks like after disconnecting.
% cat /proc/fs/cifs/DebugData
Display Internal CIFS Data Structures for Debugging
---------------------------------------------------
CIFS Version 2.08
Features: dfs fscache lanman posix spnego xattr acl
Active VFS Requests: 0
Servers:
Number of credits: 1
1) Name: <redacted>  Domain: WORKGROUP Uses: 1 OS: Windows 6.1
        NOS: Samba 4.3.13       Capability: 0x8080f3fc
        SMB session status: 1   TCP status: 4
        Local Users To Server: 1 SecMode: 0x7 Req On Wire: 1
        Shares:
        1) \\<redacted> Mounts: 1 Type: NTFS DevInfo: 0x20 Attributes: 0x1002f
        PathComponentMax: 255 Status: 1 type: DISK      DISCONNECTED"
1687273,2017-05-04 05:55:39 UTC,"Hello,
I only wanted to inform you, that the problem still exist in kernel 4.4.0-77."
1687273,2017-05-01 09:05:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687273,2017-05-19 17:07:22 UTC,"A better way is, at the moment, to put ""vers=3.0"" to the mount option, like Christian Drexler wrote. This helps."
1687273,2017-05-18 23:48:29 UTC,"Something serious like this should not technically appear on a Long Term Support Ubuntu version, and if it does, should be fixed in a very short time."
1687280,2017-09-27 18:57:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687288,2018-06-03 14:02:04 UTC,The upstream bug (along with most others) has been moved to their new bug reporting system here: https://gitlab.gnome.org/GNOME/chrome-gnome-shell/issues/1 And it is the first one to have been moved!
1687292,2017-05-01 14:06:17 UTC,"FWIW, the following can be used to check light type:
* position.w will be 0 for directional lights.
* spotCosCutoff will be -1 for non-spotlights.
* spotExponent will be 0 for non-spotlights."
1687292,2017-05-04 15:40:14 UTC,"In that case, both separate arrays and a dummy sampler would solve my problem. However, I need to run different fragment code depending on the light type - so if there are no separate arrays, a type member would still be useful to me (simply because checking for special magic values of spotCosCutoff seems a bit ugly to me). But separate arrays would be fine too."
1687298,2017-08-31 19:16:31 UTC,"Hi Tom,"
1687298,2017-09-01 16:21:22 UTC,This bug was fixed in the package congress - 6.0.0-0ubuntu1.1
1687302,2017-05-01 16:05:04 UTC,"Hello Andrey,"
1687302,2017-05-01 18:31:24 UTC,"Works like a charm, many thanks! (I've built it with Qt5, haven't tried Qt4)"
1687302,2017-05-01 18:43:58 UTC,"Hhhmmm, and now I have to decide whether to skip 0.4.17 since I will never get it out of the door anyway and continue with merging new functionality for what will hopefully become 0.4.18..."
1687302,2017-05-01 18:58:56 UTC,"Some time ago I've switched from kde to a simpler desktop, namely lumina (it uses Qt5). So, I now use qpdfview as my main viewer for pdf, djvu (and now ps.gz) instead of okular. Works nicely. If I could find some good viewer of dvi (xdvi is too awful), then I'd have no need in okular..."
1687306,2020-03-26 13:56:44 UTC,Hello!
1687306,2017-05-06 11:32:52 UTC,likely a duplicate of Bug #1685740
1687306,2017-05-02 17:20:27 UTC,"I am using Inkspace 0.92.1, Win 10  and J Tech plugin v1.7. I think Nico's examples represent my problem"
1687306,2017-05-02 16:38:56 UTC,"thank you for the files.
marking as confirmed based on the above attached files. (I am not sufficiently familiar with gcodetools to be able to reproduce the test output)"
1687306,2017-05-02 15:38:00 UTC,I did both V0.48.5 and V0.92.1 as examples
1687306,2017-05-02 10:51:52 UTC,"could you provide a sample svg file and a sample nc file, so that we can confirm the behavior?"
1687306,2017-05-02 20:47:42 UTC,"you could also try sending an email directly to the original developers:
http://www.cnc-club.ru/gcodetools"
1687306,2017-05-01 20:08:37 UTC,"since the output format has not been specified or indicated, I am going to assume that you are probably using dxf output."
1687306,2017-05-01 18:58:23 UTC,"My apology for too little info. Inkspace 0.92.1, Win 7, created rectangle
in inkspace, grbl Laserengraver. Just confirmed, J Tech Photonics Laser
Tool same problem.
On May 1, 2017 20:40, ""Alvin Penner"" <email address hidden> wrote:"
1687306,2017-05-01 18:31:11 UTC,"@lgi:
thank you for taking the time to submit a report! could you attach some additional info?
 - which OS?
 - which version of Inkscape (see the menu item Help->About)
 - which file format/extension are you using to produce the files for J Tech?
 - could you attach a sample svg file for testing purposes, as well as the file you sent to J Tech?"
1687306,2017-05-01 17:42:01 UTC,"I see same problem when using ""J tech Photonics Laser tool"" to generate Gcodes"
1687306,2017-05-01 08:32:56 UTC,If you are talking about dxf then this bug report might be relevant:  https://bugs.launchpad.net/inkscape/+bug/1643383
1687306,2017-04-30 18:52:26 UTC,"thank you for taking the time to submit a rteport! could you attach some additional info?
- which OS?
- which version of Inkscape (see the menu item Help->About)
- which file format are you using to produce the files for laserengrave?
- could you attach a sample svg file for testing purposes, as well as the file you sent to laserengrave?"
1687306,2017-05-02 07:01:04 UTC,"The output is in gcode nc files for grbl engraving
On May 1, 2017 22:15, ""Alvin Penner"" <email address hidden> wrote:"
1687309,2017-05-01 22:19:29 UTC,The attached ZIP file contains USB packet capture file made with Wireshark on host OS side during crash.
1687309,2020-11-09 12:30:39 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1687309,2021-01-09 04:17:40 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1687311,2017-04-30 19:21:46 UTC,Do you want pictures or something?
1687317,2017-05-01 18:25:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461476"
1687317,2017-05-16 22:41:54 UTC,"Reviewed:  https://review.openstack.org/461476
Committed: https://git.openstack.org/cgit/openstack/patrole/commit/?id=b18f98b28b9f6e70e603f12b71fac44f6b4ac280
Submitter: Jenkins
Branch:    master"
1687319,2017-05-24 20:13:13 UTC,"The ""Cancel"" link (which only displays if there is an error) also breaks when placing multiple holds at once from a list. Example URLs that are generated for the links."
1687319,2018-02-22 15:45:20 UTC,"Adding a note that Mary J. & I just saw this as well, both using ""continue"" and ""cancel""."
1687319,2019-01-21 18:38:18 UTC,I'm not seeing this on 3.2.1 -- can anybody confirm that it is still a problem in 3.2 or master?
1687319,2019-01-21 21:54:13 UTC,I'm still seeing this on the 3.2.2 community demo server.
1687321,2017-04-30 20:36:43 UTC,Continuing through with placing the metarecord hold gets even stranger.
1687322,2017-05-01 00:22:57 UTC,"The attachment ""patch-to-remove-the-at.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1687322,2017-12-02 10:11:58 UTC,"Hello,
Is there is something I need to do before my patch of May is applied?
Thank you."
1687332,2017-05-04 17:57:21 UTC,"I'm pretty sure that is simply not a supported use case for ubiquity, but I'll leave it to more active developers to decide if this should be a wontfix or just leave it as a new feature request."
1687332,2017-05-01 00:22:32 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We noticed that you were installing the LTS version of Ubuntu using an older version of the installation media.  The latest point release of 16.04 is 16.04.2. Please try installing from that version of the installation media and see if that resolves your issue. Thanks in advance!
1687332,2017-05-01 00:36:58 UTC,Tried using an updated LTS system.
1687333,2017-04-30 23:45:57 UTC,"Why would you ""have to upgrade to the development release"" after installing a daily Live CD? A daily Live CD is the development release of Ubuntu."
1687333,2017-05-01 00:40:45 UTC,@ Brian Murray
1687333,2017-05-01 04:28:29 UTC,It is straightforward to use zsync to keep the daily iso files up to date. There are links at http://iso.qa.ubuntu.com/
1687333,2017-05-01 05:25:54 UTC,I have for a while been dual booting a stable install alongside a development install even on external drives. This does not have the grub panicing if a drive is missing in bios mode with a missing drive and goes into recovery mode with even less options. Granted the choosing wrong partition can be a problem with catostrophic results. Although I am not sure this is good for others but I memorize which partition not to touch.
1687333,2017-05-01 22:02:42 UTC,Thanks for the info.
1687333,2017-05-04 21:25:24 UTC,How much should be the storage of the pen drive where we can install the ISO? Is it enough 4 GB?
1687333,2017-05-04 22:44:42 UTC,"@Filiberto,"
1687336,2017-05-01 08:27:36 UTC,Patch in release_fixes 7537a0a
1687341,2018-09-17 15:37:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687353,2017-05-03 06:11:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687353,2017-05-06 05:05:18 UTC,"The easiest way to reproduce it was in the game Starbound. Teleporting, quickly the computer would freeze. I could freeze the computer in seconds doing this."
1687353,2017-05-08 20:11:32 UTC,Hello
1687353,2017-05-08 20:20:35 UTC,I think this is the same bug I am having: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838
1687353,2018-03-25 17:07:36 UTC,This was corrected and is no longer happening to me.
1687354,2017-06-05 20:30:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687354,2017-05-01 05:12:49 UTC,https://launchpad.net/ubuntu/xenial/+source/python-crypto
1687367,2017-01-30 21:26:41 UTC,"I change the clock preferences to show in the form 13:00:00, and it looks just fine, but then as soon as I press the close button, it returns to a custom format that contains no text. If I then go to preferences again and enter in %T for the time and %c for the tooltip, it works, so I will use this as a workaround, but this is very buggy and it should work if I select something other than a custom format."
1687367,2017-05-05 08:03:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687367,2017-05-05 08:04:06 UTC,"As a workaround, xkill the settings dialog rather than closing it the normal way. Settings will be saved."
1687367,2018-08-13 18:43:59 UTC,Another relevant upstream report:
1687372,2017-05-05 13:11:22 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1687378,2017-05-01 10:39:19 UTC,"XPI files are typically effectively .zip files. Opening this type of file in scratch would give you little benefit. You might be better trying to open it in ""Archive Manager""."
1687378,2017-05-01 12:01:28 UTC,Hello David :)
1687382,2017-05-01 12:32:41 UTC,Happens also on Ubuntu Gnome 17.04 with Nautilus 3.20.
1687382,2017-05-02 08:08:24 UTC,See also https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/7
1687382,2017-05-04 06:53:27 UTC,I have tracked down the root cause to the statement gobject.threads_init() in zim/main/__init__.py. After removing that line I have seen no more segfaults on my linux system.
1687384,2017-09-14 12:13:28 UTC,"I just ran into this doing a dist upgrade from 14.04 to 16.04.3. Now, the initial do-release-upgrade failed mid way, because of something wrong with Postgres. (I can't remember the exact details now, but it started popping up a dialog about postgres, which had a 'close' button, but clicking close caused the dialog to pop up again. And eventually Unity died during the upgrade, forcing me to restart. Which had a number of follow on dpkg issues. (that's why we all want snaps, right?)"
1687384,2017-05-03 12:21:03 UTC,"My attempts to remove or re-install snapd failed so far. I lost patience and hacked snapd.prerm by making it exit 0 immediately. After that, the apt-get upgrade had no more issues changing that package. Snappy works now and can install and uninstall packages. I tested it with the ""hello-world"" package. Snappy had not worked before, so I guess that's a viable workaround?"
1687384,2017-05-31 17:17:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687384,2017-05-02 22:54:49 UTC,"Hi Jonny, that's really surprising. If you're not using snaps, I believe that the easiest way forward is to uninstall snapd:"
1687384,2017-05-02 01:56:16 UTC,"Hi Jonny, is this accurate?"
1687384,2017-05-02 06:12:46 UTC,"Hi Seth,"
1687384,2017-05-03 09:56:07 UTC,"It might be an awkward dependency between snapd and ubuntu-core-launcher
or snap-confine, I would suggest purging those then reinstalling snapd
which will bring in its dependencies cleanly."
1687390,2017-05-17 08:12:39 UTC,"By the way we have worked round this issue by:
1. converting a pools.yaml example to an ERB template
2. not including zone-manager and pool-manager in our site.pp
3. adding the code below to our site.pp."
1687397,2017-05-01 12:00:11 UTC,This change was made by a bot.
1687397,2017-05-01 18:54:15 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1687397,2017-05-03 16:08:05 UTC,"Thanks for the helpful link. I tested the kernel v4.11 and this fixes the issue. Now, the Display is also running at 60 Hz (not 30 as it was before).
There are still some minor errors in kernel.log when plugging In/Out but everything seems to work."
1687397,2018-03-08 22:33:38 UTC,"It seems this is the same bug for Dell XPS 15 as well. Not always, but sometimes this happens either using the DA200 adapter (Type-C usb) or direct HDMI. However, a related bug has been fixed (black screen)* so I will report back if this still happens on the Dell XPS 15."
1687397,2020-07-05 04:32:24 UTC,"My experience is on a dell precision which is pretty much the same as the XPS series.
Pulling the USB-C out quickly and re inserting can hang the computer.
Using 20.04."
1687399,2017-09-14 13:21:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687406,2017-05-03 13:27:43 UTC,You can backup the manifest file and then use a text editor to change the Manifest hash to the Calculated hash and retry again.  You'll probably need the --ignore-errors option.
1687406,2017-07-16 16:05:15 UTC,"Hello,"
1687413,2017-05-08 20:35:24 UTC,"@macat,"
1687413,2017-05-08 19:54:04 UTC,apport information
1687413,2017-05-08 19:58:03 UTC,"Mario, I tried the kernel you linked and experienced the same issue using it, so this has not been solved in that branch."
1687413,2017-05-08 19:54:13 UTC,apport information
1687413,2017-05-08 19:54:10 UTC,apport information
1687413,2017-05-08 19:54:09 UTC,apport information
1687413,2017-05-08 19:54:07 UTC,apport information
1687413,2017-05-08 19:54:06 UTC,apport information
1687413,2017-05-08 19:54:02 UTC,apport information
1687413,2017-05-08 19:31:27 UTC,"There has been a lot of work upstream in the graphics stack around MST, but not all of it has been merged yet.  Would you be able to test with drm-next to see if the problem is resolved there?
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/current/"
1687413,2017-05-08 19:53:59 UTC,apport information
1687413,2017-05-08 19:53:58 UTC,apport information
1687413,2017-05-08 19:53:56 UTC,apport information
1687413,2017-05-08 19:53:55 UTC,apport information
1687413,2017-05-08 19:53:53 UTC,apport information
1687413,2017-05-08 19:53:52 UTC,apport information
1687413,2017-05-08 19:53:50 UTC,apport information
1687413,2017-05-08 19:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1687413,2017-05-08 19:54:00 UTC,apport information
1687414,2017-05-07 19:12:25 UTC,commit 68466b625cf50cc148fdc98c66ac794e987ae10a
1687414,2017-05-08 06:23:43 UTC,make that fbdba42ebfff4e61a2891a898647a42f13c60586
1687414,2017-06-20 09:53:22 UTC,I'm using Zim 0.66 and I confirm this problem when click in the tray icon.
1687430,2017-05-02 05:25:16 UTC,In order to fix this bug existing kernel version should be updated.
1687431,2017-05-08 05:48:11 UTC,Apparently an invalid date was entered in the index table. Committed patch to prevent that.
1687445,2017-05-01 17:44:23 UTC,Fix is here: https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=6ca0dfd
1687448,2017-05-01 23:04:04 UTC,"And despite this note in the Constraints documentation ""To ignore any constraints which may have been previously set, you can assign a 'null' value."", this didn't actually ignore the previously set constraints."
1687448,2017-05-01 23:00:08 UTC,"That didn't work either, unfortunately. Trying a negative number doesn't work, and trying 0.00001 is automatically changed to 1. I don't see how to remove the mem constraint entirely, which I think would do the trick, if it's possible."
1687448,2017-05-01 21:01:41 UTC,"You might need to supply it in one argument
 --constraints ""mem=1 tags=xxx"""
1687461,2017-05-07 19:17:28 UTC,Commit: b8b7247b2cf4787f708a7145dd4513c9d98217e8
1687461,2017-05-08 06:23:23 UTC,Make that 022bfef5b6d55c84832d5f95d8e3e0b111f53864
1687461,2017-06-07 12:38:20 UTC,"hello,
same here on Windows 8.1 64bit.
Older Version 0.65 works."
1687461,2017-09-03 01:05:26 UTC,"Same on Arch Linux, zim 0.67-1. An attempt to attach a file leads to"
1687462,2017-05-17 09:52:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687466,2020-03-17 12:39:36 UTC,"Closing, 16.04 is way too old at this point."
1687466,2017-08-09 21:08:36 UTC,"@mitya57
On 16.04 LTS
indicator-bluetooth depends on unity-control-center, indicator-applet-complete depends on indicator-bluetooth and so on. So it is a kind of dependency problems. It seems that indicator-keyboard indirectly may depend on unity-control-center."
1687466,2017-07-25 07:37:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687466,2020-03-17 12:38:44 UTC,At least on Ubuntu 20.04 using GNOME Tweaks Alt+Shift as layout switching can be enabled under additional layout options.
1687466,2017-05-02 16:37:57 UTC,Hi Norbert!
1687466,2017-05-01 20:23:15 UTC,apport information
1687466,2017-05-02 17:52:25 UTC,"If you can, then please test with Ubuntu 17.04. There we switched back to GNOME settings daemon and also control center. Might be good to know it everything works there or not."
1687466,2017-05-01 20:23:13 UTC,apport information
1687466,2017-05-01 20:23:11 UTC,apport information
1687468,2017-05-07 18:22:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687470,2017-05-18 19:16:31 UTC,Fixed by: https://review.openstack.org/#/c/461660/
1687476,2019-07-07 12:57:05 UTC,"paste2.org is a CloudFlare site, so the functionality should be mothballed anyway."
1687477,2017-10-19 11:22:24 UTC,There is a file conflict between the two packages:
1687477,2017-10-19 11:24:28 UTC,Upstart install script needs to filter rbd-mirror files from ceph package:
1687477,2017-10-19 11:25:54 UTC,"Later ceph versions (>= yakkety) stopped shipping upstart configurations, so this only impacts on Xenial."
1687477,2017-05-05 13:11:07 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1687479,2017-05-24 21:16:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467774"
1687479,2017-07-11 16:18:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/482620"
1687479,2017-07-13 01:13:04 UTC,"Reviewed:  https://review.openstack.org/467774
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=42b1fa965028c12d6e78b70d2487d5dd49158176
Submitter: Jenkins
Branch:    master"
1687479,2017-07-17 17:29:45 UTC,"Reviewed:  https://review.openstack.org/482620
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2954f0dfc913c3ad6ffe8c5f1178c6711f64eb9d
Submitter: Jenkins
Branch:    stable/ocata"
1687479,2017-07-28 07:40:37 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1687479,2017-08-22 11:39:32 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1687480,2017-05-02 08:35:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687482,2017-05-03 03:19:42 UTC,Although it could still be a bug in ssh if ssh doesn't do ProxyCommand correctly.
1687482,2017-05-03 03:16:30 UTC,I've figured out that it is caused by this line in /etc/ssh/ssh_config
1687482,2017-05-03 10:14:04 UTC,"Thanks for investigating.  At minimum, I think sss_ssh_knownhostsproxy is going to need to provide a -4 flag for it to be possible to make that work correctly.  After that, it might be necessary to either mangle the configured ProxyCommand by hand or to somehow extend the ProxyCommand mechanism to support passing through information about the state of the -4 flag."
1687482,2017-05-02 15:04:51 UTC,"I'm running xenial.  After I saw your comment I tried it on zesty and have yet to run into this bug on zesty.  I haven't tried in the same environment yet though, I can try that later this week as well as get an apport-collect done."
1687482,2017-05-02 11:27:25 UTC,Without a sophisticated ipv6 setup I tried the most trivial.
1687482,2017-05-02 23:01:52 UTC,"I'd suggest using ""ssh -v"" rather than relying on the ""Last login:""
output.  For instance:"
1687483,2018-01-13 23:13:18 UTC,"Does this actually have much use?  A curved character with lots of segments ends up half-filled in anyway.  And if we move to actual fonts in the future, we won't have this option anyway."
1687483,2018-01-15 16:51:13 UTC,"It may not have a lot of use, but it is nice to have.
I least I sometimes like to work in outline mode."
1687483,2018-01-15 17:51:48 UTC,"On 1/15/2018 11:51 AM, Andrzej Wolski wrote:

> It may not have a lot of use, but it is nice to have.
> I least I sometimes like to work in outline mode.
>
> I don't see a reason why TrueType fonts cant be displayed in outline
> mode, they will look even better than stroke fonts.
"
1687483,2019-04-11 17:31:25 UTC,"This bug hasn't gotten any more love in 2 years, and the legacy canvas will be going away soon, so I'm going to remove the ""sketch text"" setting."
1687486,2017-08-28 13:41:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1687489,2018-02-06 12:33:14 UTC,"Change abandoned by Rob Cresswell (<email address hidden>) on branch: master
Review: https://review.openstack.org/461531
Reason: Repo retired"
1687489,2017-05-01 23:11:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461531"
1687489,2017-05-01 22:34:34 UTC,We need to remove following from overrides.py file
1687505,2018-06-01 13:22:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687514,2017-10-23 16:16:15 UTC,Possible duplicate: Bug #1726431
1687514,2017-05-06 08:02:03 UTC,"Confirmed on Windows XP (32-bit), lp:inkscape/0.92.x rev.15420.
Not reproduced with Inkscape 0.91."
1687514,2017-05-05 10:04:33 UTC,"Interesting note. The offset point 0 (in the defs) does not cause this problem, if you draw a regular path (no shape) and then apply powerstroke separately.  Somehow, it's only the powerstroke attached to triangle in/out, which causes this."
1687514,2017-05-04 10:51:13 UTC,Thanks TD  :-)
1687514,2017-05-04 10:50:06 UTC,"Oh, ok.  After some experimenting, I see what the offset point is/means.  So the user can do that from the canvas, unless they really want the end to be as flat as possible."
1687514,2017-05-04 03:24:52 UTC,It's in the def for the effect.
1687514,2017-05-03 13:46:24 UTC,"It seems the effect's point offset attribute being zero does not provide adequate direction for the stroke, interfering with the rendering of the canvas."
1687514,2017-05-02 04:55:57 UTC,"So far, I've found that I can avoid this problem (I mean drawing with Pen/Bezier with triangle in/out shape) by opening the Path Effects dialog, and changing the Interpolator Type from CubicBezierJohan to CubicBezierSmooth."
1687514,2017-05-02 04:48:47 UTC,"Hhm, I thought that the triangle in/out shapes (for Pen/Bezier tool) were automatically applying both pap and powerstroke.  But when I draw with that shape and open the Path Effects dialog, it's only showing the powerstroke."
1687514,2017-05-02 02:12:43 UTC,I don't need an ellipse to make this happen.  Screenshot with one object drawn in new blank file.  You can't see the mouse pointer.  But the Pen tool is still enabled when I made the image.
1687514,2017-05-04 03:11:18 UTC,"I can't find any attribute called ""point offset"".  The only thing I find in XML Editor referring to ""point"" or ""offset"" is in the style attribute, stroke-dashoffset:0.  But changing the value to 1 did not fix the problem."
1687517,2017-05-02 12:26:57 UTC,Could it be related to https://bugzilla.gnome.org/show_bug.cgi?id=772354 ?
1687517,2017-05-02 18:39:48 UTC,"It feels like the same sort of thing, yes."
1687520,2021-01-07 04:18:09 UTC,4.8 EOL
1687520,2017-05-30 23:10:17 UTC,"Update package appears to have stalled.
Initially orange installing progress bar showed install progress was progressing...
Then ""Install"" button returned to original appearence saying ""Install"" again...
Pressing button a second time resulted in ""Install"" button graying out....
Button then just stuck in this grayed out state."
1687520,2017-06-20 15:37:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687520,2017-05-18 15:08:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687524,2018-08-12 15:29:10 UTC,"Hmm, I've reproduced this bug."
1687524,2018-08-12 15:31:19 UTC,Possibly a bug in the uncommented_lines() function.
1687532,2019-07-07 22:34:47 UTC,"We can no longer see the details of of the failure since reports.vapour.ws has been decommissioned. In addition, we have not seen this failure recently, nor did we see the failure described in the related, linked bug."
1687533,2017-05-02 05:48:53 UTC,https://review.openstack.org/#/c/461625/
1687533,2017-06-21 14:17:47 UTC,"@Fei Long Weng: Any progress ? A solution would be to write a decorator for disabling tests for specific backend or if there is a decorator, re use it. This bug is resolved but we can have a new wishlist bug which makes us write a decorator for such purposes."
1687533,2017-06-29 09:22:34 UTC,force delete backup is backend specific feature and does not fall under Tempest scope. Test has been deleted from Tempest.
1687533,2020-04-02 12:31:00 UTC,The mentioned test has been deleted since 16.1.0 release.
1687545,2021-01-21 16:32:54 UTC,"And, since Jason beat me to it, I've signed off his branch:"
1687545,2021-01-21 16:24:53 UTC,"After just 3.5 short years, I offer a fix for this:"
1687545,2021-01-21 20:33:56 UTC,"Confirmed working on PINES production running 3.6.  Pushed to master, rel_3_6 and rel_3_5.  Thanks Dan, Jason, and Mike!"
1687545,2021-01-21 16:15:44 UTC,I have a branch here to address this: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1687545_chicago_handshake / working/user/jboyer/lp1687545_chicago_handshake but you have to supply your own Malört.
1687545,2017-05-02 06:09:13 UTC,"Per http://perldoc.perl.org/CGI.html, ""-newstyle_urls
Separate the name=value pairs in CGI parameter query strings with semicolons rather than ampersands. [...] Semicolon-delimited query strings are always accepted, and will be emitted by self_url() and query_string(). newstyle_urls became the default in version 2.64."""
1687545,2017-08-02 15:19:47 UTC,It looks like perhaps this impacts end users as shown by the following log entries?
1687545,2017-05-03 03:25:27 UTC,"The other piece of the puzzle to getting the TT2 mkurl() macro to generate links with & is to set the -oldstyle_urls flag in Template::Plugin::CGI. I thought we might have to fork that, but note that Template::Toolkit itself just celebrated its first release in three years on April 15, 2017: http://search.cpan.org/~abw/Template-Toolkit-2.27/ - so the timing might be right to press for at least an option to invoke -oldstyle_urls in the CGI plugin!"
1687545,2017-05-02 14:30:43 UTC,*grumble grumble grumble in the direction of the W3C*
1687545,2017-05-02 06:16:21 UTC,"Confirmed, adding the flag to OpenILS/WWW/EGCatLoader.pm does the trick for much of the TPAC:"
1687545,2021-01-21 15:13:59 UTC,http://irc.evergreen-ils.org/evergreen/2021-01-21#i_471358
1687549,2017-05-02 07:31:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687549,2018-02-02 15:06:22 UTC,Sadly Debian has orphaned it a while back; so no maintainer at time.
1687549,2020-01-08 15:36:18 UTC,"Even though it has been orphaned, when it is shipped with Ubuntu, I hope someone will do the updates for the Ubuntu repo."
1687551,2017-11-20 08:40:24 UTC,I have faced with the same problem. It's because python-jenkins uses GET request.
1687551,2018-05-15 14:11:44 UTC,"I have the same problem, I need to send POST request to jenkins with the data in its body. I ended up simply using the undocumented methods `jenkins_open` and `build_job_url` in the mean time:
from six.moves.urllib.request import Request"
1687551,2019-12-25 12:46:09 UTC,"I get the same problem.
The jenkinsapi package indeed overcomes this issue, however IMO is less robust and moving to it in my case raised some other bugs that needed to be handled."
1687554,2017-05-05 15:34:28 UTC,I think it is an issue with the default python version running on your local system when the virtualenvs for os-* are created. I fixed this by specifing a Python 2 virtualenv environment variable before calling disk-image-create like this:
1687554,2017-05-15 09:55:04 UTC,"Hi Jacob,"
1687563,2017-08-09 16:43:58 UTC,Aliases had been added to Interop-WG guideline.
1687569,2020-11-09 13:35:48 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1687569,2021-01-09 04:17:42 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1687570,2017-05-02 09:15:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461689"
1687570,2017-07-01 14:00:49 UTC,"Reviewed:  https://review.openstack.org/461689
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f842f11630a968fa67f531fb4f2e9b41d3be5f27
Submitter: Jenkins
Branch:    master"
1687570,2017-07-01 21:54:05 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/479522"
1687570,2017-07-28 07:41:16 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1687570,2017-08-12 08:14:44 UTC,"Reviewed:  https://review.openstack.org/479522
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=54284a4f0cb0e79cd5f1b53cfe4fc6210db7a0aa
Submitter: Jenkins
Branch:    stable/ocata"
1687570,2017-08-22 11:38:54 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1687578,2017-05-02 09:42:17 UTC,"Hi,
  What's the last thing the guest outputs before the hang?
  Does it get back to the bios or does it hang before that?
  Has the migration finished at that point or is it still going?"
1687578,2021-01-09 04:17:42 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1687581,2017-06-19 12:45:36 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1687581,2017-07-28 07:41:56 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1687581,2017-06-14 04:14:02 UTC,"Reviewed:  https://review.openstack.org/472687
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb4184f1e690901378a155573368a55ff9a8a779
Submitter: Jenkins
Branch:    stable/ocata"
1687581,2017-05-02 09:59:01 UTC,The following patch should fix this issue:
1687581,2017-06-09 13:48:29 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/472687"
1687581,2017-06-08 12:38:51 UTC,Likely caused by this change in Ocata: https://review.openstack.org/#/c/389399/
1687581,2017-06-12 21:46:43 UTC,"Reviewed:  https://review.openstack.org/472266
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2d27f6a8afb62815fb6a885bd4f8ae4ed287fd3
Submitter: Jenkins
Branch:    master"
1687581,2017-06-08 13:41:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472266"
1687585,2017-05-26 19:09:03 UTC,"Thanks for pasting the traceback, this looks like its a database type issue."
1687585,2019-03-01 17:29:56 UTC,"Change abandoned by Dirk Mueller (<email address hidden>) on branch: master
Review: https://review.openstack.org/467080
Reason: no time on this atm"
1687586,2017-05-04 21:10:29 UTC,Fixed in this commit...
1687591,2017-10-23 08:09:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687591,2017-10-23 08:15:53 UTC,The bug seems to effect all Ubuntu versions from Xenial to Artful. :(
1687593,2018-10-19 17:42:26 UTC,Ocata is moving/moved into extended maintenance. Going to mark the bug as generally wont fix as this is a very old bug. Modern keystones are not affected.
1687593,2017-07-13 22:15:41 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/483590"
1687593,2018-10-19 17:38:40 UTC,"Change abandoned by Morgan Fainberg (<email address hidden>) on branch: master
Review: https://review.openstack.org/463831
Reason: administratively abandoning this patch. It can be restored if someone is going to pick it up."
1687593,2017-07-14 19:45:47 UTC,"Reviewed:  https://review.openstack.org/483590
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8d3758fde99380d1258f72d489a22edacde331b7
Submitter: Jenkins
Branch:    stable/newton"
1687593,2017-07-14 19:45:37 UTC,"Reviewed:  https://review.openstack.org/483589
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=48a5336d3d4b54f954a0100ab864a5c3f6a71380
Submitter: Jenkins
Branch:    stable/newton"
1687593,2017-07-14 19:45:22 UTC,"Reviewed:  https://review.openstack.org/483586
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=215788d26db0649686ef9ba996a45f5d4c7c1f90
Submitter: Jenkins
Branch:    stable/ocata"
1687593,2017-07-14 19:44:29 UTC,"Reviewed:  https://review.openstack.org/483584
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=59e4b4923fb9d3d9a4cd9a3de4658abd91125fc0
Submitter: Jenkins
Branch:    stable/ocata"
1687593,2017-07-13 22:27:57 UTC,Marking the stable/ocata and stable/newton bugs as high since the tempest tests are currently breaking those gates.
1687593,2017-07-13 22:26:30 UTC,"The functional tests that we added to verify this fix are being run against the stable branches, causing them to break because neither stable/ocata or stable/newton have the fix posted here. This was found and reported in https://bugs.launchpad.net/keystone/+bug/1704148."
1687593,2017-07-13 22:15:28 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/483589"
1687593,2018-10-19 17:39:38 UTC,Newton is not maintained. Marked as wont fix.
1687593,2017-07-13 21:56:45 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/483584"
1687593,2017-05-02 10:36:37 UTC,This bug fix will affect Python keystoneclient as in the current version 'openstack request token create' always uses Public endpoint during OAUTH signature irrespective of --os-interface specified.
1687593,2017-05-02 11:15:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461736"
1687593,2017-05-08 03:40:13 UTC,"Reviewed:  https://review.openstack.org/461736
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=926685c5a4823d7e3ab3879bae1529052fff7d68
Submitter: Jenkins
Branch:    master"
1687593,2017-05-10 16:56:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463831"
1687593,2017-05-02 10:54:27 UTC,This bug is applicable for 2 API - OAUTH create request token and OAUTH create access token
1687593,2017-05-15 09:03:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/464577"
1687593,2017-05-31 21:18:39 UTC,"Reviewed:  https://review.openstack.org/464577
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b7aece57d2845fcfa45a84e6d21a6188ddd192cc
Submitter: Jenkins
Branch:    master"
1687593,2017-06-12 07:37:11 UTC,Functional test cases are ready for review here - https://review.openstack.org/#/c/473245/
1687593,2017-05-15 08:55:10 UTC, https://review.openstack.org/461736 does not cover the scenario where keystone endpoint is registered with HTTPS and HTTPS endpoint is terminated at HAProxy and keystone receives HTTP requests from HAProxy.
1687593,2017-07-13 22:10:42 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/483586"
1687599,2020-11-09 13:37:05 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1687599,2021-01-09 04:17:43 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1687601,2017-05-02 11:31:17 UTC,You appear to have panasoniclpd-init sysv initd script which is malformed and cannot be included as part of the system.
1687601,2017-05-02 11:31:50 UTC,"insserv: warning: script 'S80panasoniclpd-init' missing LSB tags and overrides
insserv: warning: script 'panasoniclpd-init' missing LSB tags and overrides
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!"
1687601,2017-06-07 04:48:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687604,2017-05-17 23:22:46 UTC,"@stub, before restarting an agent next time, can you please collect the output from the juju-goroutines function? It will help us determine what is stuck."
1687604,2017-05-16 07:54:07 UTC,"On 16 May 2017 at 06:03, Menno Finlay-Smits <email address hidden> wrote:

> A few questions:
>
> I can see the agent which failed to reconnect is running 2.1.1. Can you
> confirm the controller is running this too?
>
> How long is the controller typically unavailable when this happens?
>
> Can you give an idea of how many agents fail to reconnect? (e.g. approx
> X agents out of Y total)
"
1687604,2017-05-02 11:25:46 UTC,"In this log, the agent failed at 4:32 and was restarted at 11:14:"
1687604,2017-05-15 23:03:40 UTC,A few questions:
1687605,2017-05-04 12:08:36 UTC,"Please provide some more information, for example, what version of glance you are seeing this with, are you running in devstack, etc.  Thanks!"
1687605,2017-05-05 06:52:38 UTC,"Hi Brian rosmaita, below are the details.
glance client version is 2.6.0
glance version is 14.0.0
I am using packstack.
Thanks !!"
1687608,2017-05-02 13:17:04 UTC,"doing another test, i just noticed, hitting ctrl-c wildly eventually gets me the console back, so it seems to only randomly accept it ..."
1687608,2017-06-12 13:05:40 UTC,"I'm noticing that on some rare occasions, we see devices finish the core update and not hang until reboot, but I don't think anything intentional has been done to fix this yet, right?"
1687608,2018-05-03 07:57:46 UTC,A couple of recent comments about this as I've been discussing this behavior with customers.
1687610,2018-01-12 03:46:12 UTC,"Change abandoned by feng.shengqin (<email address hidden>) on branch: master
Review: https://review.openstack.org/461759"
1687610,2017-05-02 12:12:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/461759"
1687610,2017-05-03 05:23:12 UTC,"Hi Feng,"
1687623,2017-05-03 11:41:53 UTC,I just updated Ubuntu 16.04.2 kernel 4.4.0-75. New linux-image-4.4.0-77-generic was installed along with the corresponding linux-image-extra and linux-headers. After reboot both WiFi and ethernet work.
1687623,2017-05-03 13:00:28 UTC,"Sorry I didn't reply earlier - I'm in UK.
I've just now (1250 UTC on 3 May) used Software Updater from 4.4.0.75 and all is now OK.
Many thanks to all concerned."
1687623,2017-05-03 13:01:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687623,2017-05-03 21:05:47 UTC,"Everything seems to be fixed now!
Don't know if it is still relevant but when the ""broken"" update came out the system did not show up any warning on potential missing libs or that it was an incomplete update. Thank you!"
1687623,2017-05-03 15:54:00 UTC,Also encountered very similar problem.
1687623,2017-05-03 16:11:32 UTC,"What a pain!  I was affected by this issue and lost all network drivers, wifi and wired.  I had to use another computer with functional networking to reckon how to enable the grub boot menu; then boot to kernel v.75; then follow comment #12."
1687623,2017-05-03 19:16:45 UTC,"I think the issue regards Ubuntu 16.04.2 and its flavor Lubuntu, no idea about the others, I am on 64bit."
1687623,2017-05-03 22:52:37 UTC,"I have also experienced the same fault apparently with kernel linux-image-4.4.0-77.   The problems I noted was no wired network connection,  no sound and what appears to be a default low resolution video mode.  I was able to get the system to work normally by choosing an earlier kernel from grub menu."
1687623,2017-05-03 11:28:33 UTC,"The analysis in the bug below may be of interest when fixing this:
    https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1214482"
1687623,2017-05-04 00:29:56 UTC,"If I type ""dist-upgrade"" and press enter I get:
dist-upgrade: command not found."
1687623,2017-05-04 00:42:32 UTC,I did: sudo apt-get dist-upgrade and it fixed my issues.
1687623,2017-05-04 01:15:06 UTC,"I ran the command ""sudo apt-get dist-upgrade"" and it fixed my issues.  (I did not need to run dist-upgrade separately.)"
1687623,2017-05-04 09:56:37 UTC,"Update-manager is fixed now and as Andy wrote, a change in the process should prevent this from ever happening again. Unfortunately that does not help anybody who is already having the problem (at least not if that means no network connection). And without network it is hard to find any documents about this on the net."
1687623,2017-05-04 12:01:46 UTC,Thanks for the fix Stefan! If I wasn't on dual-boot it would have been a nightmare trying to fix it without internet.
1687623,2017-05-28 05:50:02 UTC,Posting because I ran into what I feel is the same problem between 4.8.0-52 and 4.8.0-53.
1687623,2017-05-28 09:51:20 UTC,I just ran Software Updater and after reboot I am now running kernel 4.8.0-53-generic without problems.
1687623,2017-05-03 23:39:49 UTC,"@Bryan Smith - dist-upgrade in Terminal should fix the problem, you will get the full kernel. I had this problem on Xubuntu 16.04 (and would have affected anyone on *buntu 16.04 updating through the Software Updater)."
1687623,2017-05-03 11:14:40 UTC,The linux-4.4.0-77.98 was released to -updates only.  It appears that this then lead to it being marked for phased updates.  The affected people appear to have phased linux-signed only and not linux and linux-meta.  This leads to linux-signed-image-4.4.0-77-generic (and its dependencies) to be installed only.  This essentially leaves the user with half a kernel with many drivers missing.  This leads to broken internet and the like.
1687623,2017-05-04 12:00:05 UTC,@Bryan Smith Sorry Bryan I should have been clearer. It is usual when updating/upgrading via the terminal to start with
1687623,2017-05-03 09:52:53 UTC,"Same issue here, no Wi-Fi or ethernet connection working.
No resolution problems, but when I restarted after the update I noticed the dimension of the Launcher icons was different than usual (it's usually set at 38, after the update it was switched to 48 or something like that).
Getting back to 4.4.0-75 from Grub makes everything go back to normal.
I'd like to help if possible, but I'm a REAL newbie on Ubuntu!"
1687623,2017-05-02 16:26:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1687623,2017-05-02 17:22:01 UTC,"We would like to collect some additional information about your system. From a terminal, please run the following:"
1687623,2017-05-02 17:41:13 UTC,"I tried that command but it asking me to authorize launchpad to access on my behalf, which does not seem to be a very safe thing to do. What info do you need?"
1687623,2017-05-02 18:09:41 UTC,Could you write the apport data to a file and attach it then?  It can be done with:
1687623,2017-05-02 18:10:13 UTC,At a minimum it would be good to have:
1687623,2017-05-02 18:22:26 UTC,"Also, I started a bisect between 4.4.0-75 and 4.4.0-77.  It would require testing about 5 test kernels, but will tell us the exact commit that introduced the regression."
1687623,2017-05-02 20:15:17 UTC,"lspci -vvvnn output:
The apport bug report was attached
---------------------
00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM Registers [8086:1904] (rev 08)
 Subsystem: Hewlett-Packard Company Skylake Host Bridge/DRAM Registers [103c:80a4]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>"
1687623,2017-05-03 00:00:36 UTC,"Wifi the same for me, also screen resolution set to 640 x 480 and no other choice, brightness setting not honoured."
1687623,2017-05-03 01:28:32 UTC,"I just upgraded to -77 and (on a 2009 Macbook pro 17"") the keyboard/mouse was unresponsive.
Reverting to -75 fixed this."
1687623,2017-05-03 10:37:10 UTC,"In general, it seems that for some reason there was a period of time (on a different box update-manager would offer me the complete set of packages) when for some unknown reason update-manager would offer only the minimal kernel and modules. This causes all sorts of HW related issues if the driver modules are either in the extra package or (like in the case of nvidia binary driver) are built on the system after updating the kernel (but that requires the headers)."
1687623,2017-05-03 02:38:30 UTC,"Also, Till and RobotOfBarr, can you post your hardware details?  See comments 4 and 5."
1687623,2017-05-03 07:42:45 UTC,"Additionally (due to personal experience) it might be worth checking whether linux-image-extra-4.4.0-77* got installed. Not sure how that could happen but it seems update-manager offered to install linux-image and linux-image-signed without any of the other packages which should be installed at the same time (I had no headers either which impacts anything dkms related).
This morning, from an older kernel boot, an ""sudo apt-get update; sudo apt-get dist-upgrade"" was installing the missing kernel packages."
1687623,2017-05-03 07:57:15 UTC,"I have similar issues with 4.4.0-77-generic, except that after the update no hardware is recognized at all. Ubuntu doesn't see my monitors, wired network card, etc. While booting with 4.4.0-75-generic has no such problems."
1687623,2017-05-03 07:57:43 UTC,"I have the same issue, no Ethernet, connection and low display resolution which I was unable to change (1024 × 768 I think). Rebooting on .75 kernel resolved the issues. Attached report as suggested in reply #4 (this is done after rebooting to the .75 kernel, if it makes a difference I can reboot to .77 and create a new report)."
1687623,2017-05-03 08:35:04 UTC,"@Thomas, Jacob,"
1687623,2017-05-03 08:48:36 UTC,"@Stefan thanks, that did indeed solve the problem for me. I thought I checked that it was installed before I reported the issue but I must've misread."
1687623,2017-05-03 09:31:11 UTC,"@Stefan, thank you. I can also confirm that linux-image-extra was not installed (I used Ubuntu Software Updater to do original upgrade) and running apt dist-upgrade solved the issue."
1687623,2017-05-03 09:47:19 UTC,I also have to revert to 4.4.0-75 from Grub since My resolution changed to 640x480 (I think) and I was stuck in a login loop
1687623,2017-05-03 02:27:29 UTC,I'd like to bisect this issue.  Can folks affected by this bug test the kernel posted in comment #6?  I'll then build then next test kernel based on testing results.
1687629,2017-05-02 14:35:34 UTC,"""perf/x86: Avoid exposing wrong/stale data in intel_pmu_lbr_read_32()"" required adapting the target file from arch/x86/kernel/cpu/perf_event_intel_lbr.c to arch/x86/events/intel/lbr.c due to ""perf/x86: Move perf_event_intel_lbr.c ........ => x86/events/intel/lbr.c"" being backported for bug #1559914."
1687629,2017-06-06 14:51:25 UTC,This bug was fixed in the package linux - 4.4.0-79.100
1687637,2019-04-09 01:51:17 UTC,This bug was fixed in the package ubiquity - 19.04.9
1687637,2019-04-08 00:08:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687637,2018-10-19 16:52:51 UTC,sadly it turns out im not allowed to have another OS since its a work pc so i found a way to get around it since ubuntu doesen't want to fix it
1687637,2018-10-19 16:16:12 UTC,"a year has past and STILL the bug persists, im glad i never actually got this crap installed on my pc, im going to find a distro that actually works and fixes bugs and doesen't just confirm they exist and ignore them!"
1687637,2018-09-16 13:12:40 UTC,I had an older 18.04 iso on my PC which I was using.  I'm going to try Kubuntu 18.04.1 to see if that works?
1687637,2018-09-16 12:34:56 UTC,I'm trying to install Kubuntu 18.04 on a Chromebook (that's been running Ubuntu) and this bug is still present.  When I go to click the format box the installer crashes.
1687637,2017-08-29 23:19:42 UTC,"This also effects i386 17.10 which failed during my testing
http://iso.qa.ubuntu.com/qatracker/milestones/381/builds/155535/testcases"
1687637,2017-08-29 23:18:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687637,2017-05-04 19:14:01 UTC,Hrm.. I am pretty sure I have seen a few bug reports like this now with 17.04 where it looks like partman is going off the rails:
1687637,2017-05-02 16:37:30 UTC,Here is the MD5 sum:  82e6833e66407e50d46d3c4b77212105  kubuntu-17.04-desktop-amd64.iso
1687637,2017-05-02 16:24:29 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1687637,2017-05-02 14:45:42 UTC,Attaching /var/log/syslog.
1687637,2017-08-30 00:11:12 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1687638,2017-05-02 15:38:48 UTC,The following patches were skipped because they were already applied:
1687638,2017-06-06 14:51:25 UTC,This bug was fixed in the package linux - 4.4.0-79.100
1687644,2017-05-18 14:48:19 UTC,Please make a merge proposal:
1687644,2017-05-18 19:26:58 UTC,https://code.launchpad.net/~ubuntubmw/intltool/fix-cache-race/+merge/324278
1687645,2017-05-02 20:31:30 UTC,Confirmed by at least one more user
1687653,2017-05-03 13:21:32 UTC,After further investigation on IRC the following points were raised:
1687653,2017-05-03 10:23:24 UTC,I'm unable to reproduce this issue.  The host stays responsive and the dd command completes in a reasonable amount of time.  QEMU does not exceed the 64-thread pool size.
1687653,2017-05-03 10:46:45 UTC,"Please be so kind and go for a 6G LVM-Vol and do ""dd if=/dev/zero of=/dev/sdb bs=3G count=2 oflag=direct"". Please keep an eye on your processor usage in comparison to the threads created. Its harder to knock-down an SSD-Backed system than one with spinners."
1687653,2017-05-02 21:18:00 UTC,Just to make this clear: This bug affects only LVM-backed storages. File-based-storage is not affected. LVM-Thin and also LVM-Thick.
1687653,2017-05-02 16:08:38 UTC,"Sorry ab out the visibility settings, this bugtracker drives me nuts."
1687653,2017-05-03 08:45:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687656,2017-05-02 16:08:41 UTC,"by the way, this bug is happened when I try to remove and reinstall the gnome-tweak-tool, but the system does not wants me to do so"
1687677,2017-05-04 06:51:09 UTC,See https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/7
1687677,2017-05-04 10:43:54 UTC,"Is there any way I can help? I'd like to keep 0.65 installed for daily work, but if it helps, I could run 0.66 directly from source. If I run it from the terminal I should get error messages. Would that help you?"
1687677,2017-05-11 15:24:59 UTC,"Hi Jaap,
pulled the latest master from your GitHub page. Ran zim directly from source with python 2.7.12 (as is standard in Ubuntu 16.04 repositories). Seems to run stable for me. Attachment browser works, links to attachments work. No dump."
1687705,2017-05-03 07:45:00 UTC,Which version of Fuel? Need more info about environment configuration.
1687705,2017-05-03 09:42:38 UTC,Fuel 9.0.
1687705,2017-05-04 11:21:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462502"
1687705,2017-10-11 14:38:48 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Michael Polenchuk <email address hidden>
Review: https://review.fuel-infra.org/36840"
1687705,2017-10-20 10:32:53 UTC,"Reviewed: https://review.fuel-infra.org/36840
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1687705,2017-10-27 11:12:55 UTC,Verified on 9.2+mu3
1687705,2019-12-18 17:19:17 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: master
Review: https://review.opendev.org/462502
Reason: This repo is retired now, no further work will get merged."
1687717,2017-05-05 13:10:52 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1687722,2017-07-12 00:37:02 UTC,"@robert-ancell Go on, give us a clue. Who _should_ we report this to? We've gotten so far as to figure out WHY volume mutes when the screen locks, which is frankly killer for any RT AV work, and now I'm lost in the maze of twisty microservices, all alike."
1687722,2017-05-04 03:09:36 UTC,This would need to be fixed in the appropriate greeter - LightDM does not write any files in /home/lightdm.
1687722,2017-06-16 14:53:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687724,2017-05-02 18:36:28 UTC,See also: https://bugs.launchpad.net/juju/+bug/1188126
1687724,2020-02-04 15:51:26 UTC,"There have been clouds where no network is seen by the user/juju, but is handled behind the scenes, thus juju will still bootstrap."
1687738,2017-05-02 20:30:39 UTC,This change was made by a bot.
1687738,2017-05-03 13:33:30 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1687738,2017-05-03 18:39:29 UTC,Tested on kernel v4.11 and bug still persists
1687738,2017-05-03 21:37:17 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1687742,2017-05-03 07:44:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687769,2017-05-02 22:06:30 UTC,Can you provide the full console log of the booting machine?
1687769,2017-05-03 19:53:01 UTC,"Hi Blake, unfortunately, the best I can do is a video of a direct attached monitor (check your email for a link).  The system has AMT, I can't get SOL to work, and Intel no longer provides the ips-schema files for setting things via wsmancli to enable/configure VNC.  And since this all happens at boot, there's no other way to do it."
1687769,2019-09-19 14:53:13 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1687791,2018-07-27 19:30:20 UTC,Adding initramfs-tools and nominating for bionic.
1687791,2018-07-01 00:26:41 UTC,Confirmed issue on Bionic. Also confirmed the suggested patch in 1661629 #3 fixed the install for me.
1687791,2018-06-06 17:29:37 UTC,Still an issue on Bionic
1687791,2017-06-21 12:02:05 UTC,The problem is this command in /etc/kernel/postinst.d/kdump-tools exiting with 1:
1687791,2017-06-21 12:04:09 UTC,May be related to https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1661629
1687791,2017-05-09 17:53:57 UTC,It looks like the failure is actually in /etc/kernel/postinst.d/kdump-tools.  Can you add a set -x there and try again?
1687791,2017-06-21 11:56:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1687791,2017-05-04 19:22:01 UTC,"Could you put a ""set -x"" at the start of the postinst file to see where it is failing?"
1687791,2017-05-05 13:16:38 UTC,"Hello,"
1687791,2017-05-05 14:58:27 UTC,"Seems, that this package gets included via preseed:"
1687791,2017-05-05 12:15:33 UTC,"~ #  sed -i.orig -e '/^set/ a\set -x' /target/var/lib/dpkg/info/kdump-tools.postinst
~ # tail -f /var/log/syslog
May  5 12:11:29 in-target:  linux-crashdump depends on kdump-tools; however:
May  5 12:11:29 in-target:   Package kdump-tools is not configured yet.
May  5 12:11:29 in-target:
May  5 12:11:29 in-target: dpkg: error processing package linux-crashdump (--configure):
May  5 12:11:29 in-target:  dependency problems - leaving unconfigured
May  5 12:11:29 in-target: Errors were encountered while processing:
May  5 12:11:29 in-target:  kdump-tools
May  5 12:11:29 in-target:  linux-crashdump
May  5 12:11:29 main-menu[422]: WARNING **: Configuring 'pkgsel' failed with error code 100
May  5 12:11:29 main-menu[422]: WARNING **: Menu item 'pkgsel' failed."
1687800,2017-05-04 17:03:03 UTC,Information regarding the bug:
1687812,2017-05-02 23:11:28 UTC,Qt-based testcase is attached.
1687813,2017-05-03 08:25:49 UTC,The problem remains in version 1.4:
1687813,2017-05-03 08:39:27 UTC,"I can see why this breaks; unfortunately, it will be hard to fix without removing other features.  (The \input{} hack is required for some of the more obscure things Rubber can do.)"
1687817,2017-05-03 11:13:19 UTC,"not reproduced on Windows 10, Inkscape 0.92.1 r15371"
1687817,2017-05-03 16:34:13 UTC,similar to Bug #1671059 ?
1687817,2018-05-16 02:10:11 UTC,"this is not the same as #1671691, as we're not importing legacy files"
1687817,2018-05-16 10:51:44 UTC,"could you attach the svg file you are using, for testing purposes?"
1687817,2018-07-31 06:12:43 UTC,"This is currently happening to me on Windows 10:  Inkscape 0.92.3 (2405546, 2018-03-11)  Didn't happen on 0.91"
1687817,2018-07-31 10:56:01 UTC,"appears to be a duplicate of
https://bugs.launchpad.net/inkscape/+bug/1671691"
1687818,2017-09-14 20:28:32 UTC,Still reproducible with the latest devstack. Here's my screen grab.
1687818,2017-09-14 20:29:01 UTC,"Seems like it's still using domain id ""default"" somewhere"
1687818,2017-05-10 03:24:53 UTC,"I try it again, but I don't meet any problem. Do you confuse ID and NAME? :)"
1687818,2017-06-09 07:30:25 UTC,"Sorry, I can't reproduce the bug too, my details in paste page[1]"
1687828,2017-05-03 23:37:50 UTC,"________________________________
From: <email address hidden> <email address hidden> on behalf of Daniel Schürmann <email address hidden>
Sent: Wednesday, May 3, 2017 5:00 PM
To: <email address hidden>
Subject: [Bug 1687828] Re: Playlist won't populate MIXXX after import"
1687828,2017-05-03 21:00:32 UTC,Please attach one of your playlist files.
1687828,2019-07-04 10:10:27 UTC,Has this already been fixed in 2.2.1?
1687828,2019-07-04 10:10:54 UTC,https://www.mixxx.org/forums/viewtopic.php?f=3&t=12824
1687828,2019-07-04 10:14:08 UTC,The linked file seems to be detected as a binary file and silently fails to open. These are at least two bugs.
1687828,2019-07-04 10:53:53 UTC,https://github.com/mixxxdj/mixxx/pull/2200
1687838,2017-05-08 07:37:59 UTC,"So it seems that this is pretty much just not supported by GCE at all. I
wonder if we could break down the 32k range into 100 element ranges (eg 320
100-port ranges, instead of 1 32k port range)."
1687838,2017-05-05 18:48:55 UTC,This is the error on the controller side :
1687863,2017-09-14 07:29:56 UTC,Still the case with zesty.
1687863,2017-09-19 16:19:07 UTC,"Somehow related:
When booting the system, if I do not log in immediately, I get a
""Failed to lookup credentials: Failed to get password from GOA: timeout"" message."
1687880,2018-01-12 19:04:09 UTC,Unassigning due to no activity for > 6 months.
1687880,2020-04-30 21:07:41 UTC,"Looks like this happens because the source volume is not the same size (larger) than the target. We're writing off the end of the device. In addition, that's related to cinder not being smart enough about managing the space loss due to encryption headers on encrypted volumes."
1687880,2020-07-30 04:35:14 UTC,This topic was discussed at Victoria PTG:
1687880,2020-07-30 05:12:59 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/743869"
1687880,2020-08-03 18:11:15 UTC,"Reviewed:  https://review.opendev.org/732988
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=662b8210aab8e08bdddbf30e2b21ae357f3be32e
Submitter: Zuul
Branch:    master"
1687880,2020-08-06 18:16:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/745199"
1687880,2020-08-07 06:27:17 UTC,"Reviewed:  https://review.opendev.org/745199
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=09ad89b7eecd6ea654a17690996c2ec4a63dd31e
Submitter: Zuul
Branch:    master"
1687881,2017-05-04 09:53:19 UTC,"I think we should add sudo authority when doing lvm snapshot, such as what cinder project do."
1687881,2017-09-26 06:36:27 UTC,"Change abandoned by Jiao Pengju (<email address hidden>) on branch: master
Review: https://review.openstack.org/462472"
1687902,2017-05-04 07:32:00 UTC,It's a feature request. It could be implemented not earlier than the Queens will be released
1687905,2017-09-21 14:35:41 UTC,"Wedged erlang processes are a nightmare for this - we actually had a script called the rabbit hammer that did what you describe above to resolve a wedged, clustered rmq deployment."
1687905,2017-09-21 14:36:27 UTC,"Not a charm specific issue, so raising a bug task for the RMQ packages - and marking the charm task as invalid."
1687905,2017-09-21 14:36:57 UTC,I've seen this behaviour to confirming the bug and triaging as 'Medium'
1687910,2019-08-21 18:20:01 UTC,Does this issue still happen?
1687910,2021-01-03 22:04:19 UTC,"One year later, bug still valid."
1687910,2019-11-22 21:05:35 UTC,"Yes, with several 4.x kernels and even with kernel 5.3"
1687910,2018-12-25 21:34:15 UTC,"Just ran into this issue on Ubuntu 18.10 on a Thinkpad T420. Adding ""nox2apic"" to the boot parameters fixed it for me."
1687910,2017-05-03 12:00:10 UTC,This change was made by a bot.
1687910,2017-10-11 12:00:05 UTC,exists in 4.12 and 4.13 in the 17.10 repositories.
1687910,2017-05-05 14:53:39 UTC,"Tested with mainline v4.11 kernel [0] and this bug exists in mainline kernel, too."
1687910,2017-05-03 16:11:59 UTC,I won't make it before Friday (2017-05-05).
1687910,2017-05-03 13:23:15 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1687910,2017-10-16 09:01:04 UTC,Exist on a ThinkPad T420s laptop with kernel 4.13.
1687911,2020-09-22 08:43:10 UTC,Closing because INVALID.
1687922,2017-05-03 14:22:20 UTC,"This is a side-effect of the comparatively little work that was put in livecd-rootfs to make this work. We should use the graphical splash from plymouth and make sure snapd happens earlier if possible, or handling plymouth stopping differently, and that will remove the cursor."
1687930,2017-05-23 18:51:54 UTC,The CVE is: https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-8779.html
1687937,2018-10-24 15:52:00 UTC,"It seems this is related to building with the 10.14 macOS SDK. We are using the 10.13 macOS SDK on the build server for 2.2, so we may not need to rush this for 2.2.
https://bugreports.qt.io/browse/QTBUG-71292"
1687937,2018-10-24 12:47:50 UTC,"We have reports that Mixxx 2.2 is entirely unusable with macOS with QGLWidget, therefore this is critical: https://mixxx.zulipchat.com/#narrow/stream/109122-general/subject/MacOS.20rendering.20issue.20(possibly.20hiDPI.20related)/near/136167907"
1687937,2018-10-24 06:14:41 UTC,"This bug dies not describe a critical issue.
The issue described here is the deprecated state. That is not critical."
1687937,2017-11-19 18:15:11 UTC,Perhaps related: Bug #1718066
1687937,2018-10-24 01:53:46 UTC,https://github.com/mixxxdj/mixxx/pull/1863
1687952,2017-05-03 13:00:59 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1687952,2017-05-03 13:21:36 UTC,I discovered that this might be related to the fact that my machine has no swap after the upgrade. I added swap again and will report back if the issue is resolved or now.
1687966,2017-05-03 13:22:07 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1687966,2017-05-03 13:30:11 UTC,This change was made by a bot.
1687988,2017-05-06 15:05:45 UTC,"Change abandoned by Amrith Kumar (<email address hidden>) on branch: master
Review: https://review.openstack.org/462165"
1687988,2017-09-26 18:51:26 UTC,"Change abandoned by Amrith Kumar (<email address hidden>) on branch: master
Review: https://review.openstack.org/462565"
1687988,2017-05-03 14:10:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462165"
1687988,2017-05-04 13:43:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462565"
1688013,2019-09-19 11:53:10 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1688014,2017-05-16 16:35:23 UTC,"We can indeed improve our documentation, or alternatively, make the code smarter."
1688018,2018-07-19 07:20:39 UTC,@egor-tensin you are awesome! I think there might be a few related problems (like https://github.com/systemd/systemd/issues/7182) but this seems to actually work. I actually saw this bug but didn't click that your fix would work until having wasted a huge amount of time.
1688018,2018-06-14 15:40:44 UTC,Thank you @egor-tensin! I've been struggling with this problem for years. This is the first work around that actually works! I added that line under the [ipv4] section of my VPN connection file and then restarted the network manager with:
1688018,2018-06-13 00:47:07 UTC,@egor-tensin Thanks. Your walk-around works.
1688018,2018-06-13 00:07:45 UTC,"> Comment here only if you think the duplicate status is wrong.
"
1688018,2018-06-13 00:06:51 UTC,I had a lot of trouble with NetworkManager+OpenVPN on Ubuntu and discovered a couple of workarounds.
1688018,2018-04-17 21:22:28 UTC,"Commenting out dnsmasq stopped working. What I have done recently:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
so my kernel is 4.13 and to my big surprise after connecting with OpenVPN I can resolve host names of my remote site (using host myhost.remote.domain.name), but I cannot ping to them (or krdc to them etc) host unknown and thats it. What is going on?"
1688018,2018-02-17 19:37:52 UTC,"By far, the easiest and most effective workaround I've found is commenting out ""dns=dnsmasq"" in ""/etc/NetworkManager/NetworkManager.conf"" as a few others have suggested above."
1688018,2018-04-03 18:59:29 UTC,"What happened to this bug? Is it still being addressed? I'm also experiencing the same problem and the solutions above don't work for me :(
----
Ubuntu 16.04.4 LTS
NetworkManager 1.2.6
dnsmasq 2.76"
1688018,2018-03-16 15:30:23 UTC,"Almost year old bug still there. This is core functionality of any OS (secure VPNs, DNS) which just does not work on Ubuntu. I don't know how about other distros but I doubt that Ubuntu can claim to be the desktop system with such a bug."
1688018,2018-02-25 22:27:21 UTC,"The script in #37 didn't work for me, as the interface name was ""tun0"". The following slightly modified script seems to work OK so far:"
1688018,2018-08-15 19:45:58 UTC,THank you Egor! that did the trick on Kubuntu 18.04. Now if I could only figure out why it disconnects from the VPN after .5-2 hours...
1688018,2018-02-17 17:00:09 UTC,Will the fix also ensure that the search domain of the VPN's DHCP server will be used?
1688018,2018-02-05 08:45:22 UTC,"I found another workaround, that works fine without changing package versions or DNS servers.
It is tested with the issues I had with openconnect for NM."
1688018,2018-04-17 17:05:12 UTC,This bug forced me to search for ubuntu alternatives. I'm looking currently at Manjaro.
1688018,2018-08-16 08:03:10 UTC,"@hckrmagoo I had this problem as well, try making NetworkManager run OpenVPN as root: https://askubuntu.com/a/906055/844205."
1688018,2018-12-11 23:06:07 UTC,"Sebastien, could you explain the 'status: Triaged → Won't Fix' meaning?"
1688018,2018-08-17 15:16:08 UTC,Thanks Egor! Connection stayed up all day!!
1688018,2020-10-25 09:28:23 UTC,"Ah, I forgot to mention I've found a somewhat working workaround. If you uncomment the line ""DNS"" in /etc/systemd/resolved.conf and put list of DNSes with first VPN's DNS then your normal DNS, then it will always try to go through the VPN's DNS first even if you're not trying to access a resource from the VPN. Be careful not to type any dangerous domain names when connected to the VPN though."
1688018,2020-10-25 08:54:37 UTC,I'm on Ubuntu 20.04 and I've tried every solution listed above and in the bug's duplicate and none of them worked... It's really disappointing that dns doesn't work with VPNs for over 4 years.
1688018,2020-03-15 05:34:08 UTC,"The silence regarding this problem is a bit disconcerting. After jumping through many hoops, I managed to resolve this with the help of this answer: https://forum.manjaro.org/t/weird-dns-issue-over-vpn/78092/11"
1688018,2019-12-19 14:27:50 UTC,"> I'm also effected by this bug on 18.04.3 (NetworkManager v1.10.14)
"
1688018,2019-12-19 11:00:15 UTC,Hi!
1688018,2019-09-01 17:37:39 UTC,On 19.04 I can see the following (correct) behavior.
1688018,2018-08-16 13:55:37 UTC,"Well, that was pretty straightforward! Thanks for pointing that one out, we'll know in a couple hours if it worked."
1688018,2019-08-21 08:04:52 UTC,This bug and the fact that there seems to be no care in fixing it made me leave the Ubuntu distro behind. Pathetic. I no longer care if you fix it or not.
1688018,2018-12-12 21:23:38 UTC,"Thanx Colin.
Anyway anyone knows why this bug is sooo hard to fix? It is old, and quite blocking someones workflow."
1688018,2018-12-12 19:23:31 UTC,"It has only been marked Won't Fix in Yakkety, because Yakkety is well past it's sell by date.  It is still open on Xenial."
1688018,2018-01-17 11:19:48 UTC,"This workaround is not bad indeed and saves me, too. But it has drawbacks that people need to know"
1688018,2018-11-26 11:57:45 UTC,I am running Ubuntu 16.04 with plasma. I was experiencing this issue and downgraded the network-manager package to 1.2.2-0ubuntu0.16.04.4. Since the downgrade I haven't had any trouble. Waiting for fix in the latest version :)
1688018,2018-11-26 01:11:27 UTC,This problem:
1688018,2018-09-08 10:37:51 UTC,"I'm experiencing this issue on Ubuntu 18.04.1. In case this helps anyone, I've been able to fix following https://wiki.archlinux.org/index.php/OpenVPN#Update_systemd-resolved_script. Only after that change the OpenVPN supplied DNS servers appear on `systemd-resolve --status`. In case that matters, I run `openvpn` from command line"
1688018,2019-02-13 15:32:16 UTC,"For those using OpenVPN, I discovered that there is a package named 'openvpn-systemd-resolvd' that finally resolved this issue for me.  Here's the synopsis for the package in the repo..."
1688018,2017-12-28 03:08:43 UTC,"As a workaround, I commented out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf.
Now network manager adds VPN DNS servers to /etc/resolv.conf and everything works as expected."
1688018,2019-11-11 09:27:38 UTC,"18.04.3 LTS !, still reproduced, which makes me sad."
1688018,2017-10-31 19:20:38 UTC,"... and my issue is now resolved in Ubuntu 17.10, at least on a fresh install. Not sure what changed, but no changes are necessary to /etc/nsswitch.conf in order to make resolving DNS work with internal domains while connect to openconnect VPN. Probably I should stick with LTS :-)"
1688018,2017-05-03 15:44:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688018,2017-05-11 16:34:36 UTC,"For weeks now my only workaround for this problem has been to run a terminal script to connect and disconnect the VPN every 20 minutes. This is very inconvenient and impractical for things which require uninterrupted network traffic, so I hope a permanent fix is released ASAP."
1688018,2017-05-12 09:59:55 UTC,"Seumas: since Canonical seem to be dragging their feet on this, you might as well downgrade to network-manager 1.2.2, which is a version that works."
1688018,2017-05-12 11:29:22 UTC,Seumas: It seems that Canonical simply don't care about VPN users. This is opened for more than two months and still not reasonable response :( ...
1688018,2017-05-23 18:25:27 UTC,"I don't know why bugs about ""DNS on VPN"" were being marked as duplicates of suspend/resume issues in dnsmasq. It's /related/, but definitely not the same thing at all. I can only apologize that this wasn't handled correctly, and try to fix things."
1688018,2017-05-23 18:28:00 UTC,"Has anyone tried to make their connections with an even newer version of Ubuntu and network-manager, such as on 17.04? That would be a very good test to do (in my experience, it works correctly)."
1688018,2017-05-23 19:17:02 UTC,"I'm running on Ubuntu GNOME 17.04 and I'm still affected by this issue. After connecting to VPN and running a DNS leak test, it still shows my DNS as my usual ISP."
1688018,2017-05-24 00:18:19 UTC,I experience the same issue on 16.04 but it ends up breaking DNS responses entirely because traffic is forced through the OpenVPN tunnel where the DNS resides and the local DNS is no longer accessible.
1688018,2017-05-31 17:11:24 UTC,I am glad to see that this bug is being worked on and is rightly labelled as being of high importance.
1688018,2017-06-14 00:58:29 UTC,"Might I ask when this rather severe bug is due to be fixed (in Xenial or rather, for me, in Mint)? Thank you."
1688018,2017-06-19 14:30:31 UTC,"On my Ubuntu 17.04 (also happened on 16.10, upgraded to 17.10 that same machine) the bug it's happening to me. My current workaround is to use an equivalent 'openconnect'."
1688018,2017-06-19 15:12:42 UTC,"Just expanding a little bit more my last comment, on Ubuntu 17.04, using the 'sudo openconnect xxx' command is adding to the file /run/resolvconf/resolv.conf file the DNS IP addresses as global ones. Just also added them on the 'icon' version and it fixed it too. In Ubuntu 17.04 it's using by default the systemd-resolved service (instead of the reported one dnsmasq)."
1688018,2017-06-19 23:32:19 UTC,"Cruz, thanks for this."
1688018,2017-07-09 10:00:05 UTC,Any updates? It would be nice to see full closure on this issue ASAP.
1688018,2017-07-13 00:45:32 UTC,1. It has been four months since this bug - it its original incarnation (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606) - was reported.
1688018,2017-05-23 23:52:07 UTC,"I don't know what your ""DNS leak test"" is, but we can't give much weight to that unless we also know a lot more about your config for the VPN and how the test is set up, what it looks for, etc."
1688018,2017-08-31 21:20:45 UTC,"Using a VPN I have at hand (I don't control the server part of it, though), I can confirm that with n-m 1.2.6 my local DNS (10.0.5.5) is injected after the vpn is established:
Aug 31 20:36:32 31-64 dnsmasq[1118]: setting upstream servers from DBus
Aug 31 20:36:32 31-64 dnsmasq[1118]: using nameserver 10.0.5.5#53(via ens3)
Aug 31 20:36:32 31-64 dnsmasq[1118]: using nameserver 10.172.64.1#53 for domain internal
..."
1688018,2017-07-13 00:48:45 UTC,Corrections to the above post.
1688018,2017-10-26 08:06:33 UTC,@jsseidel I believe starting from 16.10 ubuntu use systemd-resolved as dns. Your issues might come from that and it would explain why it's also present in Fedora 25
1688018,2017-10-25 16:45:45 UTC,"I don't know if my issue is related to this or the few others I've seen, so I pre-apologize if this should be moved elsewhere or even if it's not relevant in this context. I'm far from an expert in DNS . . ."
1688018,2017-10-20 07:45:22 UTC,I wonder how many people's DNS leaked over the year this bug hasn't been addressed. Oh well..it's just your users' security. Canonical is a joke. Please stop endangering your users with your incompetence.
1688018,2017-10-11 06:39:34 UTC,@cyphermox please comment on the status Mathieu.
1688018,2017-09-06 10:36:34 UTC,@joll-nicholas I just want to add my view of this situation to this bug report. :) It was more like message to all in this thread ... my apologize if it was not written properly (I am not native speaker)
1688018,2017-09-05 18:31:52 UTC,"On my Mint (18.2 and I think I did it on 18.3 too - both Cinnamon) the
network-manager downgrade sufficed; I did not need to adjust resolvconf.
However, I don't think I was using a 'PPTP tunnel'."
1688018,2017-09-05 17:55:50 UTC,"Just an FYI, I have to downgrade both network-manager=1.2.2-0ubuntu0.16.04.4 and resolvconf=1.78ubuntu2.  Doing one or the other would not fix the problem on my system (Linux Mint Mate 18.1)."
1688018,2017-11-09 19:02:57 UTC,I have exactly the same Problem like User Orange Shiang-Yuan Kao (orange-kao) wrote on 2017-03-22 in Comment #10 in duplicate Bug 1671606 since upgrading to
1688018,2017-09-05 17:00:43 UTC,Just downgrade network-manager to 1.2.2-0ubuntu0.16.04.4 until the issue is resolved. Pretty simple.
1688018,2017-09-05 16:38:38 UTC,"@lukas-d: I understand, but perhaps you are thinking that I work for Canonical or that I have the skill to contribute to the network-manager project. Neither of those things are true. I am a frustrated user (with fairly low programming ability)."
1688018,2017-09-05 08:23:10 UTC,"@joll-nicholas ... ""it is not guaranteed secure."" ... Explain this to employer. I am using VPN as it is requirement of my employer. They don't care if it work or not on Linux. M$ Windows client is working and that its. We are not in position to negotiate VPN solution especially if it is not guaranteed to be secure."
1688018,2017-09-03 15:25:09 UTC,"@terry69lawson and other frustrated users: perhaps you are in a position to try *WireGuard* as a replacement for OpenVPN (or for other methods of connecting to a VPN). Your VPN provider will need to have WireGuard servers for this to work. If your provider does have such servers, then you are in luck, for not only does Wireguard work with the latest (unfixed) Network Manager, it's also fast and easy. Still, it's also still in development and, though it has had some testing and had good reviews, it is not guaranteed secure."
1688018,2017-09-03 15:10:15 UTC,"Now NONE of my Ubuntu machines, on Xenial or Zesty, will use my VPN for even a brief time. I've tried several different versions of packages, but nothing. This is absolutely intolerable. Fix this soon Canonical or I will be forced to leave for a different Linux distro."
1688018,2017-09-02 10:09:50 UTC,I hope this bug will be fixed soon for 16.04
1688018,2017-08-31 21:21:14 UTC,"Oh, that box is on xenial, btw."
1688024,2017-05-03 20:51:13 UTC,probably requires a fix similar to https://review.openstack.org/#/c/451316/ that was made for cinder.
1688028,2017-05-16 12:18:34 UTC,"There is a successful and unsuccessful deploy in the log as we were trying to reproduce the issue, but it is sporadic."
1688028,2017-05-16 21:44:09 UTC,"I can see the unsuccessful deployment in the MAAS logs but not in the Juju logs. Tim's got a good idea of what the problem is (the retry limit in the provisioner), and I'll fix that, but it would be handy to see the Juju log for an unsuccessful deployment to confirm what we think is happening."
1688028,2017-05-16 22:25:35 UTC,PR to increase the retry limit: https://github.com/juju/juju/pull/7351
1688028,2017-05-16 05:48:23 UTC,Are you sure that the Juju log attached here is the right one?
1688028,2017-05-17 00:24:35 UTC,Bug to improve the provisioner retry logic: https://bugs.launchpad.net/juju/+bug/1691297
1688029,2017-05-05 13:09:58 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1688029,2018-01-03 06:45:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688033,2017-05-03 16:36:43 UTC,"Thanks for raising this bug and starting the discussion.
I will check and come back with my comments"
1688034,2017-05-03 19:03:55 UTC,Some additional info.
1688034,2017-05-03 20:33:07 UTC,Now trying with @debug instead of @info
1688034,2017-05-05 13:15:40 UTC,I found out how to enable debugging for sudoers:
1688034,2017-05-05 13:56:47 UTC,"I guess this also makes 1.8.16-0ubuntu1.3 a ""security"" update, since sudo+sssd now enforces policy which it should have done before, but didn't."
1688034,2018-03-10 05:41:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688051,2017-05-03 18:04:59 UTC,"Hello Arnaud,"
1688051,2017-05-03 19:48:18 UTC,"It works with
 0.4.16.99~2045~61~ubuntu16.04.1
Thanks!"
1688052,2018-01-17 14:02:22 UTC,"I am also affected by this, and I found the same issue with the Azure Ubuntu Server 16.04 image. This issue did not affect the Ubuntu Server 16.04 image in AWS."
1688052,2018-01-17 14:01:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688052,2017-05-05 18:36:43 UTC,"This is probably the same issue as Debian, which is this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807707"
1688061,2017-05-04 17:04:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688061,2020-01-06 15:15:38 UTC,"I have the same issue in Ubuntu 18.04.3.
The option ""freedesktop.org tray icon base on dbus"" mentioned by firfefoxfans no longer exists.
I found (searching for tray) DBus based new Freedesktop.org tray icon and disabled that."
1688061,2019-06-08 23:39:44 UTC,"I try again ,if have manual  select the skin,even return the origin defaul skin ,the menu can successfully pop up ,and the mate desktop don't freeze  again."
1688061,2019-06-08 23:34:07 UTC,"I have test on my local machine and two in virtualbox. install the change fcitx-ui-classic  package  and  change the skin to classic ,the problem will gone ."
1688061,2019-11-03 22:42:09 UTC,"I confirm it's the option ""freedesktop.org tray icon base on dbus"" in ""addon --->advanced"" that cause the problem .Please run fcitx-config-gtk3 to unchecked it ."
1688061,2019-04-18 14:51:41 UTC,"The issue still happens on Ubuntu MATE 19.04,
that uses fcitx 1:4.2.9.6-5,
which (debian changelog) says it was released on 30 Aug 2018."
1688061,2018-02-06 01:28:06 UTC,I fixed This specific issue with fcitx in fcitx upstream with https://github.com/fcitx/fcitx/commit/20cc3f1eda39cb577ae81791cfd96cc203da4538 .
1688061,2018-02-04 22:35:28 UTC,"Reproducible in bionic daily. It's actually worse now, input is blocked entirely and never restored."
1688061,2018-02-02 14:46:29 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1688061,2019-06-08 23:30:21 UTC,"I found the solution on 18.04 .It's something related with the ui skin。first use keyboard shortcut to active the input method to chinese (or other instead of the default english), click the menu ,select the skin from ubuntu-XXXX to classic or dark。"
1688062,2017-05-03 19:18:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1688062,2017-05-03 20:06:21 UTC,"Just installed 4.11rc8 and rebooted, the stack trace still appear after a few seconds."
1688062,2017-05-03 21:37:32 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1688074,2019-06-18 21:09:19 UTC,The original description of the situation isn't true anymore. Delete or Backspace do nothing while routing. But I miss possibility to delete the last segment or two. On the other hand deleting shouldn't be too greedy. Maybe deleting the last segment (attached to the mouse cursor while routing) with Backspace and warping the cursor back to the end of the previous segment would be good.
1688074,2019-07-04 07:35:29 UTC,"(Slightly different from the original bug listed in 2017, but falls under the same description)"
1688074,2018-12-10 15:04:42 UTC,Bumping the priority and setting to 6.0.
1688074,2018-04-25 22:08:54 UTC,Hmm... What was the expected behavior here?
1688074,2018-04-25 17:54:24 UTC,"@Seth, did by chance your commit d0ffff3b88 fix this bug or is this something different?"
1688074,2018-03-10 08:11:26 UTC,"Application: kicad
Version: 5.0.0-rc2-dev-unknown-30a78f0~62~ubuntu17.10.1, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 (+libidn2/2.0.2) librtmp/2.3
Platform: Linux 4.13.0-36-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    Curl: 7.55.1
    Compiler: GCC 7.2.0 with C++ ABI 1011"
1688074,2018-04-25 23:19:49 UTC,"I don't know that the expected behavior was ever defined only that it worked a certain way and now it acts a different way.  Maybe that is the fundamental problem here, we didn't define the behavior so everyone has their own expectations and we have no good response.  Before we make any more changes to the route, we should define this behavior first.  That's something to discuss during v6 development."
1688081,2017-05-03 20:52:34 UTC,apport information
1688081,2018-05-01 03:42:37 UTC,"I found some drivers here:
http://www.asix.com.tw/download.php?sub=driver"
1688081,2017-11-18 21:16:18 UTC,I can verify this bug.  4.10.0-38-generic didn't work but 4.10.0-28-lowlatency did.
1688081,2017-07-09 05:10:23 UTC,"Sorry for taking so long. I am now using kernel 4.10.0-26-lowlatency and the module works correctly, no problems at all. I think this issue can be closed."
1688081,2017-06-02 06:06:32 UTC,"Okay, let's do a bisection.
Please try Linux 4.9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/"
1688081,2017-05-04 08:55:26 UTC,"@kaihengfeng no, definitely not. As I said, I take the USB-ethernet dongle off and insert another, from another brand, and it works flawlessly. Besides, I have turned off networkmanager and noticed that even with ifupdown and/or manually raising the interface, it refuses to work. It seem that at the time of module loading, some firmware initialization or something like that is not happening. In the kernel version prior to 4.10 (4.8, 3.3 etc.), when the module was loaded, a light appeared on the dongle to show activity. Now it doesn't."
1688081,2017-05-04 06:23:06 UTC,Probably NetworkManager's problem? LP: #1676547
1688081,2017-05-03 23:00:20 UTC,"Ok. I installed kernel 4.11 from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8/"
1688081,2017-05-03 21:23:23 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1688081,2017-05-03 20:55:42 UTC,"Changed status to confirmed as per apport instructions. However, I had to use apport without the non-working adapter plugged in (another one in its place), so the hardware information would be wrong. For information, I plugged the working adapter (Realtek USB 10/100/1000 LAN) four times, and it worked these four times; the same goes for the non-working adapter (ASIX AX88x72A)"
1688081,2017-05-03 20:52:29 UTC,apport information
1688081,2017-05-03 20:52:10 UTC,apport information
1688081,2017-05-03 20:52:25 UTC,apport information
1688081,2017-05-03 20:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1688081,2017-05-03 20:52:01 UTC,apport information
1688081,2017-05-03 20:52:26 UTC,apport information
1688081,2017-05-03 20:52:07 UTC,apport information
1688081,2017-05-03 20:52:12 UTC,apport information
1688081,2017-05-03 20:52:04 UTC,apport information
1688081,2017-05-03 20:52:16 UTC,apport information
1688081,2017-05-03 20:52:18 UTC,apport information
1688081,2017-05-03 20:52:20 UTC,apport information
1688081,2017-05-03 20:52:23 UTC,apport information
1688081,2017-05-03 20:52:14 UTC,apport information
1688088,2017-05-03 20:27:54 UTC,"stack trace of the error messages:
2017-05-03 11:27:04.152 86004 WARNING magnum.common.keystone [req-c325779e-1f6d-4dce-adfa-ee3c3c9e8230 - - - - -] Auth plugin and its options for service user must be provided in [keystone_auth] section. Using values from [keystone_authtoken] section is deprecated.
2017-05-03 11:27:04.160 86004 ERROR magnum.conductor.handlers.common.cert_manager [req-c325779e-1f6d-4dce-adfa-ee3c3c9e8230 - - - - -] Failed to generate certificates for Cluster: 3bd279ad-a170-468c-ba4a-bd6366781f46
2017-05-03 11:27:04.160 86004 ERROR magnum.conductor.handlers.common.cert_manager Traceback (most recent call last):
2017-05-03 11:27:04.160 86004 ERROR magnum.conductor.handlers.common.cert_manager   File ""/usr/lib/python2.7/site-packages/magnum/conductor/handlers/common/cert_manager.py"", line 106, in generate_certificates_to_cluster
2017-05-03 11:27:04.160 86004 ERROR magnum.conductor.handlers.common.cert_manager     context=context)
2017-05-03 11:27:04.160 86004 ERROR magnum.conductor.handlers.common.cert_manager   File ""/usr/lib/python2.7/site-packages/magnum/conductor/handlers/common/cert_manager.py"", line 51, in _generate_ca_cert
2017-05-03 11:27:04.160 86004 ERROR magnum.conductor.handlers.common.cert_manager     context=context,
2017-05-03 11:27:04.160 86004 ERROR magnum.conductor.handlers.common.cert_manager   File ""/usr/lib/python2.7/site-packages/magnum/common/cert_manager/barbican_cert_manager.py"", line 91, in store_cert
2017-05-03 11:27:04.160 86004 ERROR magnum.conductor.handlers.common.cert_manager     connection = get_admin_clients().barbican()2017-05-03 11:27:04.167 86004 DEBUG oslo_messaging._drivers.amqpdriver [req-c325779e-1f6d-4dce-adfa-ee3c3c9e8230 - - - - -] CAST unique_id: 705940f2dd5c4a2e8a71a4355562b9f2 NOTIFY exchange 'magnum' topic 'notifications.error' _send /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py:426
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server [req-c325779e-1f6d-4dce-adfa-ee3c3c9e8230 - - - - -] Exception during message handling
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py"", line 155, in _process_incoming
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server     res = self.dispatcher.dispatch(message)
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py"", line 222, in dispatch
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server     return self._do_dispatch(endpoint, method, ctxt, args)
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py"", line 192, in _do_dispatch
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server     result = func(ctxt, **new_args)
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/osprofiler/profiler.py"", line 153, in wrapper
2017-05-03 11:27:04.170 86004 ERROR oslo_messaging.rpc.server     return f(*args, **kwargs..."
1688088,2017-05-03 20:34:03 UTC,"previous stack trace might have some line numbers off due to code added for debugging.
here is the original line numbers of the stack trace
http://paste.openstack.org/show/3z6pqcuUc0NGBbjoPhCJ/"
1688088,2017-05-22 14:25:25 UTC,Trying to reproduce
1688088,2017-08-16 07:38:33 UTC,Is there any recent progress? I have met same problem and executed on ocata version.
1688115,2017-05-03 21:26:55 UTC,"Oooh, I love that!"
1688115,2019-03-07 19:39:17 UTC,"If this does get implemented as a carousel, I'd recommend that we make it adhere to the WAI-ARIA Authoring Practices for carousels -- https://www.w3.org/TR/wai-aria-practices-1.1/#carousel -- for maximum accessibility and usability."
1688117,2017-06-20 13:34:29 UTC,Seems like we should try to sync but if not possible to ignore the error.
1688117,2019-09-19 11:59:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1688124,2017-05-04 18:05:42 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1688124,2017-05-06 18:31:33 UTC,"This usually happens because the ABI of python sip has changed, so veusz needs to be rebuilt."
1688124,2018-02-02 14:43:45 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1688149,2017-05-04 00:22:06 UTC,Al repetir la instalacion el error no se presenta. Puede entonces tratarse de un hecho aislado o un fallo en la secuencia de instalacion.
1688159,2017-05-04 07:21:23 UTC,"Hey Gabriel, thanks for reporting this issue, we'll investigate as soon as possible.
I moved the bug our bug tracker for the GUI on github, at https://github.com/juju/juju-gui/issues/2845"
1688159,2017-05-04 04:17:07 UTC,"Since bugs of juju-gui are being tracked on github, maybe you want to copy & paste it to here:"
1688160,2017-05-04 06:41:51 UTC,"If you just want to install the kernel, you can safely skip the linux-tools package. In case you do need it, please also add ""binary-perarch"" to the command:"
1688160,2017-05-04 08:37:20 UTC,Thanks you so much for answering. I will try this.
1688160,2017-07-16 13:34:30 UTC,"git clone -b joule https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial fails:
Cloning into 'xenial'...
fatal: Remote branch joule not found in upstream origin"
1688160,2017-07-25 02:17:55 UTC,"@fnoop, i think the new source is here https://code.launchpad.net/~canonical-kernel/ubuntu/+source/linux-joule/+git/linux-joule"
1688175,2017-05-10 01:54:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463638"
1688175,2017-05-24 05:54:10 UTC,"Reviewed:  https://review.openstack.org/463638
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=67eedb807290b6d7a3c6c2bb6e9296b5c16d3959
Submitter: Jenkins
Branch:    master"
1688175,2017-05-04 05:43:05 UTC,"@hongbin, I think the nova claim is try to consume from user quota and track quota usage. In zun, there is no quota control now. So the container consumed CPU will tracked by the dockerd, and zun compute node will get the real consumed CPU from dockerd periodically."
1688175,2017-05-05 02:03:45 UTC,"Sorry for not dig into the Nova claim before, I take back what i said, instance_claim do not have much relationship with the quota control."
1688178,2017-07-08 04:19:36 UTC,[Expired for Widelands Website because there has been no activity for 60 days.]
1688178,2017-05-08 09:08:23 UTC,Having a CAPTCHA is indeed important. I'll post here again if I run into a webclient that has both features.
1688178,2019-09-06 08:12:37 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/214
1688178,2017-05-06 19:15:11 UTC,"Finally found an IRC client that works (thanks, Hasi!), so this is low priority now."
1688178,2017-05-04 06:39:44 UTC,The Webchat interface used on widelands.org is the webinterface from freenode with some pre-settings shown in an iframe. You could try using that webinterface directly: http://webchat.freenode.net/
1688178,2017-05-07 09:32:09 UTC,"Using kiwiIRC (https://kiwiirc.com/) as our website widget, as you mentioned on irc, should be considered."
1688181,2017-05-10 12:19:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463734"
1688183,2019-02-27 16:19:53 UTC,This has become quite limiting for Kubernetes. Even in the AWS case it would be useful to have e.g.
1688184,2018-01-24 22:40:37 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1425
1688196,2017-09-21 14:47:14 UTC,I can see how that would be a problem; presumably some basic quoting in the configuration file is supported by oslo.config so we could just always do that.
1688202,2017-05-04 09:46:12 UTC," Just as a pointer for anyone looking into this, the existing DBUS interface can be used to find open copies of pcb and what file they have open."
1688207,2020-11-16 08:38:12 UTC,Zero crashes after 17.10 so consider it fixed.
1688208,2017-06-29 19:11:33 UTC,This bug was fixed in the package libgweather - 3.24.1-0ubuntu0.1
1688208,2017-06-29 19:11:38 UTC,"The verification of the Stable Release Update for libgweather has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1688208,2017-06-29 19:04:06 UTC,I also utilized a database query for the bucket associated with this crash to check the dependencies for the libgweather version of crashes reported in June of 2017.  This is the result:
1688208,2017-06-12 22:57:08 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1688208,2017-06-27 15:33:02 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1688208,2017-05-24 16:45:15 UTC,This bug was fixed in the package libgweather - 3.24.0-0ubuntu3
1688208,2017-06-28 01:20:43 UTC,This very common crash has not been reported to errors.ubuntu.com in several weeks on artful. I verified that I could not reproduce the crash at LP: #1695567 any more after updating libgweather to 3.24.1-0ubuntu0.1 on Ubuntu GNOME 17.04.
1688209,2017-05-18 03:55:01 UTC,Bump. Seems to be crashing the shell in zesty and artful fairly frequently.
1688209,2017-05-27 07:02:35 UTC,This looks like a duplicate of bug 1693964 based on the stacktrace
1688209,2017-05-29 02:27:53 UTC,"The stack trace does not match bug 1616651, and bug 1693964 is also unrelated."
1688209,2017-05-29 09:15:10 UTC,"1693964 was a cut and paste fail.
bug 1616651 was the correct one."
1688209,2017-05-29 09:23:08 UTC,"Have another look at bug 1616651. It does not mention ""gweather_location_unref""."
1688209,2017-05-29 09:26:21 UTC,However I know you are the original reporter so I won't stand in your way any more. Just suggest being cautious with marking duplicate bugs that have different stack traces. A common outcome from that is people continue to complain their problems actually aren't fixed even after you think you've released a fix. So you need to be very sure it's the same issue or else bugs linger open indefinitely.
1688209,2017-05-29 10:51:51 UTC,"right, I apparently mixed up invalid pointer: 0x00 bug at some point, and now my SRU is on the wrong bug! thanks for pointing it out. I'll sort it out"
1688209,2017-05-29 12:44:55 UTC,"Tim, you can ask in #ubuntu-release if you want an unapproved SRU rejected so you can upload a fixed version."
1688218,2017-05-04 10:24:40 UTC,"Fix proposed to branch: master
Change author: Roman Podoliaka <email address hidden>
Review: https://review.fuel-infra.org/35175"
1688218,2017-05-05 12:37:18 UTC,"Reviewed: https://review.fuel-infra.org/35175
Submitter: Pkgs Jenkins <email address hidden>
Branch: master"
1688228,2019-10-29 15:49:53 UTC,"This is true, and I left comments in the patch (it would still need work). It's also true of a *ton* of post-processing type code all over the compute manager where things in post ops could still fail on unnecessary stuff and result in errors even though the guest might be OK."
1688228,2017-08-03 08:46:16 UTC,"Change abandoned by Matthew Booth (<email address hidden>) on branch: master
Review: https://review.openstack.org/462499
Reason: This came loose from my series fixing this."
1688228,2019-04-08 20:28:04 UTC,Putting back to New to re-triage this.
1688228,2017-05-04 11:16:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462499"
1688252,2017-05-04 15:20:52 UTC,You have not an updated version of Xtracks or Ytracks. No OR problem here.
1688258,2017-05-04 14:53:33 UTC,"It should be    nModelVars because one can assign new values only to
independent parameters of the models.
But function  findVal  indeed scans     (nModelFunc+nModelVars) parameters"
1688262,2017-09-26 16:38:51 UTC,"Same issue, for torsocks as well. As a workaround I specify IP with 'HostName' in ~/.ssh/config."
1688262,2017-11-22 10:20:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688267,2017-05-05 06:54:54 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/462833"
1688267,2017-05-30 06:41:43 UTC,"Hello Michael, any update on this bug? Do you know when exactly can I expect a fix for this bug?"
1688267,2017-05-30 08:47:31 UTC,"Zoltan, please review the patch (https://review.openstack.org/462833).
This patch could be applied on fuel master (needed only manifests from deployment/ dir)."
1688267,2017-05-30 12:59:33 UTC,"Hello Michael,"
1688267,2019-12-18 16:47:51 UTC,"Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/462833
Reason: This repo is retired now, no further work will get merged."
1688312,2017-09-04 14:25:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688314,2018-11-05 15:53:22 UTC,"Hi, i'm attaching manpages which i've created from help information of each executable file. I think these are at least a good start and in most cases should be enough."
1688320,2017-07-19 23:25:10 UTC,"Reviewed:  https://review.openstack.org/485155
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-openstack_openrc/commit/?id=2d65f030663b7485640bc6a3611ce63626e9d3ee
Submitter: Jenkins
Branch:    master"
1688320,2017-05-18 15:16:52 UTC,"Reviewed:  https://review.openstack.org/462880
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=c0b5e8c90a159e9930651da9d217176080b5ff82
Submitter: Jenkins
Branch:    master"
1688320,2017-07-19 10:55:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/485155"
1688320,2017-05-05 09:19:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462880"
1688320,2017-05-15 15:18:24 UTC,"Reviewed:  https://review.openstack.org/462879
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-plugins/commit/?id=fa85b973130f3bc454c297759d0d28b1a55d7612
Submitter: Jenkins
Branch:    master"
1688320,2017-05-05 09:17:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462879"
1688329,2017-05-08 07:01:08 UTC,"I implemented VNCClient::serverCutText().
Should be available with Travis build 36 (2017-05-08)
Only tested with Mac-Mac"
1688335,2019-09-26 10:41:36 UTC,Hello!
1688335,2019-09-26 10:42:25 UTC,(please set this back to New when you respond...)
1688335,2019-11-26 04:17:27 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1688336,2018-03-20 17:04:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688336,2018-03-20 17:06:06 UTC,"I second this. All I wanted was to download bionic images, but uvtool surprisingly deleted my xenial image without my say-so:"
1688337,2017-06-20 22:22:31 UTC,See also: https://bugs.launchpad.net/juju/+bug/1690004
1688337,2017-06-20 23:30:49 UTC,"In general, the OpenStack provider checks the credentials at bootstrap, if they fail it says:
ERROR authentication failed."
1688337,2017-06-21 03:46:13 UTC,"AIUI this was a case of AddModel using different credentials which may have
then been revoked after. The original issue was the underlying workers kept
restarting without an indication of who or what was wrong."
1688337,2017-06-22 23:43:29 UTC,"I was able to reproduce by adding a second user to openstack, adding those credentials to juju for add-model and deploy a few charms.  You can then do a `openstack user set <username> --disable`"
1688340,2017-05-05 14:44:49 UTC,"confirmed on Windows 10, Inkscape 0.92.1 r15371
attached is the svg file I get after resizing the page."
1688342,2017-06-08 21:52:23 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1688342,2017-08-28 09:55:32 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1688342,2017-08-12 03:30:32 UTC,"Reviewed:  https://review.openstack.org/466481
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=10a62ec99e2839f0fb163d38f37fa09e9f7b6c1c
Submitter: Jenkins
Branch:    stable/newton"
1688342,2017-05-23 23:31:39 UTC,"Reviewed:  https://review.openstack.org/466480
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bc8d0723e6e43d9b95ff9a5c4cbf7b0bec503a2f
Submitter: Jenkins
Branch:    stable/ocata"
1688342,2017-05-20 10:48:16 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/466480"
1688342,2017-05-20 10:48:31 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/466481"
1688342,2017-05-19 15:49:40 UTC,"Reviewed:  https://review.openstack.org/462674
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=53a71c1241aac70018c16d174032427a172378ed
Submitter: Jenkins
Branch:    master"
1688342,2017-05-04 16:58:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462674"
1688342,2017-05-30 15:54:17 UTC,This issue was fixed in the openstack/nova 15.0.5 release.
1688345,2020-06-22 15:11:12 UTC,"11:41 <rafaeldtinoco> there was an old bug from cyphermox related to adding support for netplan into netcf:
11:41 <rafaeldtinoco> https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1688345
11:42 <rafaeldtinoco> I was wondering, should we keep it opened or just request netcf removal from the archive ?
11:42 <rafaeldtinoco> (it seems that netcf isn't much ""maintained"" lately, and our strategy is to support netplan with backends only, no ?)
11:42 — rafaeldtinoco waits feedback to continue or not with [RM] bug to AA"
1688353,2017-05-04 18:03:24 UTC,"Having strings that represent library policy statements bundled into a single resource file strikes me as something that would have been a reasonable design choice when TPAC was getting started, but the current approach is also a valid choice. Having the policy text split out keeps each part next to the context where the user is meant to read it, allowing for structural and design changes to be coordinated with changes to the text.  For example, a library might elect to link out to a policy rather than quote it."
1688353,2017-05-05 14:13:24 UTC,"The main benefit I see in favor of reducing the number of files is to decrease the likelihood that a new site might miss updating text that should be reviewed. It's obvious (hopefully) to a new site that they need update a logo and links. However, they may miss the smaller text informing users to log in with the last digits of a phone number or the  password message telling users what the format of their password should be (something that should be added to the existing docs)."
1688353,2018-06-11 20:00:10 UTC,"Note that bug #1732552 (pull request, but not yet committed) adds another of these little template files."
1688368,2017-05-04 22:07:20 UTC,"The reason we have it for machine is because we can guarantee a clean
removal (by destroying the instance). Applications that have units on
machines that are acting unruly will not clean themselves up, so are likely
to leave processes behind.
It would be possible to drop the objects without trying to clean things up,
if it was clear that it may leave things behind."
1688368,2019-05-07 10:04:55 UTC,"From Juju 2.6, 'remove-application', 'remove-unit', 'remove-relation' and 'destroy-model' have all gained a --force option."
1688374,2018-05-08 18:07:25 UTC,This change was made by a bot.
1688374,2021-01-07 04:18:16 UTC,4.8 EOL
1688391,2017-05-05 12:01:27 UTC,"> as if it was an URL, which it obviously isn't
"
1688391,2017-05-05 14:11:23 UTC,"This is not a matter of ""having to be heuristic"", this is plain wrong. Here you are matching something that can be easily ruled out by a non-heuristic rule without introducing any false negative, so it IS retarded."
1688397,2017-05-05 06:17:58 UTC,"During multinode devstack installation , first node is configured with controller as allinone ( controller + compute) with MULTI_HOST."
1688397,2017-06-14 21:07:07 UTC,"No reviews found in this bug, unassigning. Please add a comment with active reviews before assigning an individual, or tag the bug in the gerrit review, which will do that automatically"
1688397,2017-06-26 16:33:14 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'https://api.launchpad.net/1.0/devstack version: ...'"
1688397,2017-06-26 16:40:48 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'devstack version: ...'"
1688397,2017-06-28 12:55:08 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1688397,2017-07-25 20:20:48 UTC,"This likely won't be fixed in devstack since devstack doesn't control the subnode stacking in a multinode setup. In the upstream CI infra, the devstack-gate repo does that, and it runs the tools/discover_hosts.sh script in devstack from the control node once the subnode(s) are setup:"
1688397,2017-07-25 21:11:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/487217"
1688397,2017-07-25 21:17:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688397,2017-07-28 00:00:14 UTC,"Reviewed:  https://review.openstack.org/487217
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=c63ecadb08245eda3f4ef2327a2b9ca85cf4b4f9
Submitter: Jenkins
Branch:    master"
1688419,2018-01-24 22:25:22 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-730
1688419,2017-05-05 18:43:35 UTC,"Also, if autocommit = 0, CPU usage goes to 100%
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
28917 karl      20   0  104416  35116   9160 R 100,0  0,2   7:53.38 perl"
1688419,2017-05-05 22:10:32 UTC,"CPU spins up because when running pt-t-c on master, it continuously waits/contacts each slave looking for the checksums which never come because there was no commit. ouch!"
1688422,2017-05-05 12:53:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1688424,2017-05-05 03:24:09 UTC,"# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.2 LTS
Release:	16.04
Codename:	xenial"
1688424,2017-05-05 10:04:42 UTC,"Studied /etc/grub.d/10_linux a little bit deeper and found out, that the 'grub-mkrelpath /' is probably expected, but the way, how $rpool gets determined is buggy (and in this case it results into an empty string). Attaching a patch, which resolves the problem for me (just deduces it from whatever is mounted on / right now)."
1688424,2017-05-05 12:26:24 UTC,"The attachment ""grub-cfg.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1688447,2017-05-05 04:12:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688447,2017-05-05 04:24:51 UTC,See also https://github.com/andreafeccomandi/bibisco/issues/48
1688447,2017-05-05 23:55:03 UTC,*** This is an automated message ***
1688448,2019-06-25 02:46:13 UTC,I am pretty sure that veebers is not working on this bug.
1688454,2017-09-13 22:37:37 UTC,"Using a 128GB USB stick I bought and a 4GB iso - should be USB 3, but is writing at 22 - 40MB/s (speed seems to move up and down)"
1688458,2018-01-12 19:04:12 UTC,Unassigning due to no activity for > 6 months.
1688469,2018-01-14 14:03:41 UTC,"Hi,"
1688469,2018-01-14 14:47:14 UTC,Did you add it to 5.25? I translated another untranslated string.
1688469,2018-01-17 13:38:15 UTC,"Hi,"
1688469,2018-01-17 19:45:27 UTC,"Good, I made some more changes."
1688469,2019-12-29 08:24:38 UTC,Please update the translations again.
1688469,2019-12-30 08:49:15 UTC,"Jonatan,"
1688469,2020-01-16 19:42:46 UTC,They were updated again. Thanks Dave!
1688473,2017-05-05 08:50:00 UTC,"Hi,"
1688473,2017-05-05 09:12:55 UTC,"Dear sir:
Honestly speaking, this issue only happened on one PC used by my colleague.
On my computer, everything was fine. Therefore, I think it would be hard to reproduce the issue.
On his computer, we have tried to use the older versions (6.2 2016q4). The result remained.
However, we can use the Windows command line to successfully make the command of telnet localhost 4444 and connect to the OpenOCD. From my perspective, the setup of OpenOCD should have no problem."
1688483,2017-06-06 14:51:25 UTC,This bug was fixed in the package linux - 4.4.0-79.100
1688483,2017-05-05 07:55:45 UTC,The following patches were skipped because they were already applied:
1688489,2017-05-05 14:10:58 UTC,"I kind of feel like I would have to see a proof of concept of the implementation to wrap my head around this right now, at least right now without coffee on my brain.  I kind of think it would be viable, although I suspect we would need to pull a long deprecation period."
1688489,2017-08-11 10:58:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/492948"
1688489,2017-05-08 10:48:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/463303"
1688489,2017-08-07 18:00:37 UTC,On the meeting today we've decided this needs a spec.
1688491,2017-05-23 15:47:59 UTC,"found a work away:
run the game as root on a different X session (no compiz):
sudo startx /usr/games/etr -- :8"
1688491,2017-05-23 15:55:08 UTC,*work around
1688491,2017-05-23 16:10:43 UTC,"a better way - disable fullscreen mode:
create (or edit) the ""options.txt"" file in $HOME/.etr/ (where $HOME is your home folder)
with the following declarations:"
1688491,2019-04-05 10:31:03 UTC,Affects development version 19.04 (Disc Dingo) using Nvidia GTX750. Both versions 390 and 418 drivers have been tried and both fail.  The Nouveau driver works OK.
1688493,2018-01-20 07:43:34 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-950
1688494,2020-11-20 03:08:15 UTC,改善されました
1688502,2017-05-06 07:44:41 UTC,Thanks for taking the time to file a report!
1688505,2017-05-05 09:46:20 UTC,The following patches were skipped because they were already applied:
1688505,2017-06-06 14:51:25 UTC,This bug was fixed in the package linux - 4.4.0-79.100
1688509,2018-04-09 05:18:51 UTC,The 'cell_name' has been removed in the following patches.
1688509,2019-09-10 07:10:54 UTC,"This bug has been open as ""Incomplete"" status for about one and a half year without any activity.
I'm going to move it to ""Won't Fix"".
This bug can be reopened (set back to ""New"") if someone decides to work on this."
1688516,2017-06-27 21:37:59 UTC,"Ok, I've read that bug again and I think it's a drastic reduction in our testing commitment that needs more discussion; this proposal is for an uncontentious new feature."
1688516,2020-02-06 12:52:09 UTC,"We just deployed this; a new hint ""force-reset-test"" is now available"
1688516,2017-06-27 19:22:07 UTC,Cross-linking to bug #1700668; not marking either as a duplicate until we decide which approach we want to take.
1688516,2017-06-27 20:47:28 UTC,How do you think that the baseline reset should be effected?
1688523,2017-05-05 12:53:09 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1688529,2017-09-06 07:50:12 UTC,I get a similar error:
1688529,2017-09-12 09:09:27 UTC,I have somehow resolved my issue by adding a bunch of urls to our hellish proxy whitelist.
1688530,2017-05-05 12:36:35 UTC,Some extra information on what happens.
1688535,2018-03-09 09:29:40 UTC,Fix released (zero crash reports after 17.04)
1688545,2017-05-05 14:02:00 UTC,"This is related to the direction Variety is heading, please read here: http://peterlevi.com/variety/2017/03/changes/."
1688549,2017-05-05 13:39:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688558,2017-05-05 20:05:31 UTC,I think when an object gets re-uploaded it's possible the old expirer entry doesn't get reaped.
1688558,2017-05-17 17:52:38 UTC,I am very sorry for taking so long to respond. I will get the information you are asking for shortly.
1688558,2017-05-17 19:33:32 UTC,Ok when using swift-get-nodes it returns the urls to HEAD the individual nodes that should be storing the object.
1688558,2017-05-17 23:58:53 UTC,It could be left over entries from before the cut over to using sharded .expiring_object containers [1] - were you using swift before 2.1.0?
1688558,2018-01-17 05:31:27 UTC,"Reviewed:  https://review.openstack.org/496534
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=cf1a1e89bbca50e285e99d31209c6eac6c697083
Submitter: Zuul
Branch:    master"
1688558,2018-01-19 06:14:24 UTC,"Fix proposed to branch: feature/s3api
Review: https://review.openstack.org/535623"
1688558,2018-01-19 13:30:03 UTC,"Reviewed:  https://review.openstack.org/535623
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=271b80d0f51078719de35bf6f75b7e06ac3e5b91
Submitter: Zuul
Branch:    feature/s3api"
1688558,2018-01-19 23:04:36 UTC,"Fix proposed to branch: feature/deep
Review: https://review.openstack.org/535990"
1688558,2018-01-22 22:23:41 UTC,"Reviewed:  https://review.openstack.org/535990
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=3122895118111b2b11f5ef9d0b3410b337624b1b
Submitter: Zuul
Branch:    feature/deep"
1688569,2017-05-08 07:22:50 UTC,agreed it could be supported
1688569,2017-05-05 18:20:37 UTC,"""unknown placement directive"" seems from this part:
https://github.com/juju/juju/blob/master/provider/maas/environ.go#L589-L602"
1688573,2017-06-29 06:26:29 UTC,"Reviewed:  https://review.openstack.org/462953
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=69d39f79fdd83acaf2d7846b4ed0de73e551aaf4
Submitter: Jenkins
Branch:    master"
1688573,2017-05-05 14:04:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462953"
1688579,2017-05-26 02:56:09 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1688579,2017-05-30 13:42:01 UTC,Issue is now fixed:
1688579,2017-06-06 14:51:25 UTC,This bug was fixed in the package linux - 4.4.0-79.100
1688579,2017-06-06 15:02:55 UTC,This bug was fixed in the package linux-aws - 4.4.0-1018.27
1688579,2017-06-06 15:04:47 UTC,This bug was fixed in the package linux-gke - 4.4.0-1014.14
1688587,2017-05-06 00:35:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688587,2017-05-11 15:27:22 UTC,this seems very similar to #1689538.
1688587,2017-05-24 12:00:45 UTC,"@Corben check out #1674838 (#1689538 is marked a duplicate of #1674838). Per your syslog you're getting the swapops.h:129 error before the soft lockups, as I was."
1688587,2017-05-24 12:25:11 UTC,"Thanks for your answer @Adrian.
I went back to the linux-signed-image-generic-hwe-16.04 package, which has kernel 4.8.0.52.23 inside.
Haven't had any issues like this with that kernel since my bug-report here."
1688587,2019-09-26 13:27:47 UTC,"assuming this got fixed since then, reopen if not"
1688590,2017-05-05 15:39:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/462977"
1688590,2017-06-15 09:05:41 UTC,"Change abandoned by Rob Cresswell (<email address hidden>) on branch: master
Review: https://review.openstack.org/462977"
1688592,2018-03-18 11:41:42 UTC,There is a bounty for this issue at https://www.bountysource.com/issues/55506502-add-va-api-hardware-decoding-support-on-linux
1688592,2018-05-02 18:18:00 UTC,Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
1688592,2019-06-03 16:52:04 UTC,"The dependency of this bug could probably changed from ogl-linux-beta to bug 1491303, as webrender will replace all the old rendering architecture and is already enabled on linux + intel in nightly."
1688592,2019-09-24 14:02:17 UTC,@grmat libplacebo is a renderer not a hardware decoder and is unfit to be used in a browser. First thing we need dmabuf support so that we can import decoded frames without copying them back to the system RAM and then display it on the screen. If I understand it correctly this is the toughest part.
1688592,2019-07-01 13:31:49 UTC,"Although this bug is only about decoding support, I'd like to leave a note about the rendering: AFAIK rendering without any slow copies requires DMABUF support, so processes can share resources on the GPU.
For the Wayland backend this about to land, see bug 1552590, quote:"
1688592,2019-07-09 22:37:45 UTC,"I've recently spent some time testing the implementations in various browsers. Chromium implements VA-API but it's disabled in official builds and fragile, breaking regularly. Webkit uses gstreamer-vaapi and I've had quality issues with that using both Intel (wrong colours) and AMD (blur) hardware."
1688592,2019-08-12 20:11:18 UTC,"Also, please note that this would save the users a few GWh of electric energy and thus help protect the climate."
1688592,2019-09-24 14:36:12 UTC,That should be bug 1572697 for Wayland.
1688592,2020-06-17 19:43:23 UTC,"(In reply to eric.riese from comment #34)

>
> In my opinion the bounty was already earned when this issue was resolved but I don't know who gets to be the arbiter.
"
1688592,2020-03-03 07:16:39 UTC,"I'm glad to here that, but what about support for Firefox on X11? Is it given up?"
1688592,2020-03-03 07:31:46 UTC,"(In reply to lilydjwg from comment #30)

> I'm glad to here that, but what about support for Firefox on X11? Is it given up?
"
1688592,2020-03-03 09:01:00 UTC,"(In reply to lilydjwg from comment #30)

> I'm glad to here that, but what about support for Firefox on X11? Is it given up?
"
1688592,2017-09-19 01:04:23 UTC,"Personally, I do NOT care about accelerated layers for rendering frames. Who cares?
I just want to use ""accelerated video decoding via HW"" because solving the video codec exhaust many CPUs, not rendering frames after. Yes rendering via OGL will probably give much better results but who cares? We need accelerated youtube videos ASAP."
1688592,2020-06-17 19:17:54 UTC,Reminder that there is still a bounty for this issue at BountySource
1688592,2020-06-19 19:28:37 UTC,"(In reply to Robert Mader [:rmader] from comment #35)

> (In reply to eric.riese from comment #34)
> >
> > In my opinion the bounty was already earned when this issue was resolved but I don't know who gets to be the arbiter.
>
> That would certainly be Martin Stránský :)
> Martin, do you want to claim the bounty? If you don't care about it / don't need it yourself, you could donate it or so.
"
1688592,2020-06-19 19:37:46 UTC,This needs to be closed to claim the bounty at https://www.bountysource.com/issues/55506502-meta-add-va-api-hardware-decoding-support-on-linux so closing this one.
1688592,2020-06-21 07:55:41 UTC,This should depend on bug 1616185 and bug 1619523 so it's easier to find where the work happened.
1688592,2020-03-03 06:48:00 UTC,HW decoding support  has landed at Bug 1616185.
1688592,2017-08-16 02:02:42 UTC,"(In reply to Jean-Yves Avenard [:jya] from comment #15)

> Yes, we also need accelerated layers to be able to render the frames.
"
1688592,2020-03-04 00:01:25 UTC,re-opening as a meta bug for VA-API implementation (including X11)
1688592,2017-07-23 15:40:15 UTC,Just FYI: https://chromium-review.googlesource.com/c/532294 this will be [chrome-parity] soon
1688592,2015-10-02 10:33:11 UTC,"Hardware decoding on Intel Ironlake should be used only for 720p and lower.
Hardware 1080p decoding on Intel Ironlake is slower than software decoding on CPU: https://bugs.freedesktop.org/show_bug.cgi?id=47858"
1688592,2015-10-02 12:42:52 UTC,"(In reply to russianneuromancer from comment #1)

> Hardware decoding on Intel Ironlake should be used only for 720p and lower.
> Hardware 1080p decoding on Intel Ironlake is slower than software decoding
> on CPU: https://bugs.freedesktop.org/show_bug.cgi?id=47858
>
> GPU model from about:support
> Intel Open Source Technology Center -- Mesa DRI Intel(R) Ironlake Mobile
>
> I need to fill separate issue about VA-API on Ironlake or drop this info
> here is fine?
"
1688592,2016-07-06 04:29:09 UTC,Mass change P2 -> P3
1688592,2016-07-06 09:06:19 UTC,Is there a reason the priority would go from P2 to P3?
1688592,2016-07-11 06:18:47 UTC,See bug 1210726.
1688592,2016-08-11 18:00:44 UTC,"linux had have the firefox browser by default in all distros I think much users of firefox are from linux and the only thing we get from mozilla a long waiting for a feature that is very needed.. between google with chromium and the denied featured requests and firefox not to working on features for firefox, linux in browser category is very late and the battery for laptops is damaged with linux and video viewing with browsers, I feel really annoying"
1688592,2016-09-23 23:46:01 UTC,"I fully agree, video acceleration is a must have feature now a days. Please solve it! Don't force me to move to Chrome...."
1688592,2016-11-14 12:45:36 UTC,I still have hope too to see full VDPAU/VAAVI support in order to have hardware video acceleration.
1688592,2016-11-18 21:41:36 UTC,Gentle reminder:
1688592,2017-03-04 08:59:00 UTC,"Hi,"
1688592,2017-05-05 14:57:23 UTC,"(In reply to Laurent Bonnaud from comment #10)

> in firefox release/51 and beta/52 in about:support one can see ""Hardware
> H264 Decoding"" status.
>
> However in firefox aurora/53 and nigthly/54, this line is no longer visible.
>
> Was this done on purpose or is this an omission?
>
> BTW, how about adding a line about ""Hardware VP9 Decoding"" since recent
> Intel GPU do support hardware VP9 decoding?
"
1688592,2017-05-05 15:18:02 UTC,"@ehumphries, if I interpret the bug comments correctly, you flagged this report with *NEEDINFO*. Could you please tell us, what information is needed to get the feature implemented?"
1688592,2017-05-05 15:20:23 UTC,"""needinfo"" is intended to call the attention of a specific person to the bug - I need information from X, to answer question Y."
1688592,2017-06-22 07:22:11 UTC,"(In reply to Paul Menzel from comment #11)

> Laurent, if this is still reproducible – I only have 45.9.0 here –, could
> you please create a separate report for this issue? That’d be great.
"
1688592,2017-06-22 07:39:30 UTC,"Yes, we also need accelerated layers to be able to render the frames. And right now, this has taken a set back and the feature has been disabled for now."
1688592,2017-06-26 22:00:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688592,2017-07-13 21:08:27 UTC,"(In reply to Jean-Yves Avenard [:jya] from comment #15)

> Yes, we also need accelerated layers to be able to render the frames. And
> right now, this has taken a set back and the feature has been disabled for
> now.
"
1688592,2015-10-02 10:01:00 UTC,This would do decoding only ; not rendering (yet)
1688592,2017-08-16 01:04:33 UTC,"""The Quantum Flow (QF) initiative is a cross-component effort to improve user perceived responsiveness and performance.""
Could you please triage this if it would meet your demands for 57 or 58?"
1688599,2017-12-20 04:27:18 UTC,"After compute node is rebooted, failed to update numa usage:"
1688599,2017-05-05 16:33:14 UTC,"Even after updating _instance_in_resize_state() to account for rebuilds from vm_states.ERROR, I think there is a further race condition.  Down towards the end of _do_rebuild_instance() we call:"
1688604,2017-05-24 16:45:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688606,2017-05-22 15:47:15 UTC,This bug was fixed in the package cloud-initramfs-tools - 0.25ubuntu1.14.04.2
1688606,2017-05-22 15:47:02 UTC,This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.4
1688606,2017-05-22 15:46:47 UTC,This bug was fixed in the package cloud-initramfs-tools - 0.30ubuntu1.2
1688606,2017-05-12 17:47:07 UTC,"I've verified each of trusty,yakkety and xenial by modifying the user-data in the script and then running"
1688606,2017-05-22 15:46:52 UTC,"The verification of the Stable Release Update for cloud-initramfs-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1688606,2017-05-11 20:40:46 UTC,"Hello Scott, or anyone else affected,"
1688606,2017-05-11 20:39:42 UTC,"Hello Scott, or anyone else affected,"
1688606,2017-05-11 20:38:28 UTC,"Hello Scott, or anyone else affected,"
1688606,2017-05-11 17:30:01 UTC,"An upload of cloud-initramfs-tools to yakkety-proposed has been rejected from the upload queue for the following reason: ""Per uploader request.""."
1688606,2017-05-09 13:20:02 UTC,I've added a 'maas-images' task for this.  Under that task we will add the cloud-initramfs-rooturl package to the initramfs that are generated there.
1688606,2017-05-12 17:29:24 UTC,"I'm attaching version 2 of this script.
The changes from the first are from actually attempting the sru.
What I found was that
a.) trusty's initramfs built from linux-image-virtual cannot mount iso9660 or vfat filesystems.
   As a result I changed to using a command line parameter:
    ds=nocloud-net;seedfrom=http://../
   The url is the same as the file url and the user-data and meta-data just come from
   that location rather than the nocloud seed.img"
1688612,2019-09-19 19:23:57 UTC,"In doing research for one of my customer's who has run into this today, I discovered that this has actually impacted around 4 customers (3 BootStack, 1 UA) since this bug was originally filed in 2017."
1688612,2019-12-19 11:59:52 UTC,We discussed this bug at some length on the 18th of December.
1688612,2019-12-05 17:45:03 UTC,"So policy.d overrides as a feature has been added to these charms.  Now, we just need to work out what the overrides are and then this bug can be completed.  The feature is a bit ""course"" at the moment, in that the overrides have to be worked out manually, zipped into a ZIP file and attached to the charm.  Please see https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-policy-overrides.html for more information."
1688612,2019-10-01 19:39:50 UTC,"This is possibly a duplicate of https://bugs.launchpad.net/charm-keystone/+bug/1741723 which is about policy overrides using the policy.d directory for a service charm.  There is ongoing work (within the scope of the 19.10 charms delivery) to deliver this across a number of charms (including neutron-api, nova-cloud-controller and keystone)."
1688612,2019-10-01 19:29:32 UTC,the nova-compute charm doesn't have policies as its not an API charm; it just handles the instances on the host (hypervisor).  Adding nova-cloud-controller as that is the API charm that has policies.
1688612,2019-10-01 09:41:16 UTC,This bug is currently impacting 5 customers now (4 Bootstack and 1 UA)
1688612,2019-07-23 11:32:36 UTC,"There is another request from one of the customers to add a generic readonly role with relevant policies in keystone, neutron and nova. Is this going to be included in the upcoming releases?"
1688612,2017-05-05 17:08:50 UTC,"Creation of read-only roles requires modification of policy.json, which is currently not available via the charm."
1688612,2018-08-31 04:29:19 UTC,"Added Keystone charm, another similar requirement has been requested, for a role which allows a user to add Member role to a single project, but not other Admin-like activities."
1688612,2017-08-21 12:40:02 UTC,"Some clarification offered by the customer on what they are hoping to achieve (not sure this is the place for it, but thought if it was it would hurt not having it):
""We would like to have read only access group type account. When we assign any user to the group. The user permission right is read-only. e.g. The user account can't create, reboot instance. Of course the user also can't upload image or modify any network setting."""
1688612,2017-07-13 18:08:24 UTC,Currently we only render default policy.json files from https://github.com/openstack/keystone/blob/master/etc/policy.v3cloudsample.json and do not modify them in any way. The only diff in a template is handling of both v2 and v3.
1688612,2017-07-13 09:12:35 UTC,"Hi Jill, as previously mentioned policy.json management to allow arbitrary policies to be defined is not currently a supported feature in the charms. It is also not on the roadmap for this cycle so definitely won't be available in the upcoming 17.08 release. However, I do believe that this is something that is being considered for inclusion in a future release but the engineering team will need to comment on how this is going to fit in with their plans. To be clear though, even if this gets included for the next release it would not be available until 18.02 at the earliest."
1688612,2017-06-09 23:43:32 UTC,Will a change be merged into the compute charm to enable us to use this config?
1688612,2017-06-08 08:30:02 UTC,I tested it according to the following steps:
1688612,2018-08-31 07:32:43 UTC,"Also adding n-api charm, as we have a similar need -- configuring profiles for port binding (need admin_or_network_owner for port _create:binding:profile)"
1688613,2020-05-05 21:28:10 UTC,Cool bro.
1688613,2020-05-05 20:35:46 UTC,Trusty ended standard support April 2019
1688613,2018-01-07 13:50:32 UTC,Any update here? I am wondering whether we should recommend Ubuntu LTS to our clients if enterprise software stacks like Postgres on Pacemaker are severely broken for years without fixes.
1688613,2017-07-22 08:43:58 UTC,Any update here?
1688613,2017-06-23 13:00:53 UTC,"Sorry that you had to do work now, but I wrote in comment #4:"
1688613,2017-06-23 08:27:29 UTC,"Since you already worked out the patch (and thanks for the update BTW) the remaining task is packaging, building and testing - I call that less effort than usual and tag it bitesize for that.
In some sense this should make it even more likely to be picked up rather soon."
1688613,2017-06-23 08:25:18 UTC,"Clearly no one wants to dump work on you, so I checked the commits vs the git repo and the latest that got upstream is b7911abce27889becc8a4637e003bfcf5ef1b15e in 3.9.7"
1688613,2017-06-22 13:33:07 UTC,Any news on this? Should I be adding more information or can I help otherwise?
1688613,2017-05-30 06:24:08 UTC,Attached is an updated debdiff with dep3 header.
1688613,2017-05-24 10:48:36 UTC,"@nacc: Thanks for the comments, but I probably won't have time to work on the SRU template this week as I'm on vacation, or is there a point release deadline coming up?"
1688613,2017-05-23 21:49:43 UTC,@mbanck: thank you very much for your extensive analysis. Note that for SRU purposes we will eventually need to provide an SRU template in the Description per: https://wiki.ubuntu.com/StableReleaseUpdates. Would you be able to start doing that?
1688613,2017-05-05 17:33:01 UTC,Debdiff attached.
1688613,2017-06-23 08:19:08 UTC,"Hi Michael,
I have to excuse our team for not getting to your bug, there is no particular reason this was neglected other than being fully busy with even more pressing things.
OTOH we clearly want to encourage and support very responsive and active reporters.
Adding server-next tag which will give it a higher visibility."
1688620,2020-07-29 20:21:49 UTC,"Reviewed:  https://review.opendev.org/743718
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=1199489d998a729d7fcf7cf7f88ab34b6464d46b
Submitter: Zuul
Branch:    stable/stein"
1688620,2020-08-06 04:48:05 UTC,"Reviewed:  https://review.opendev.org/744724
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=826cbfa7cee207914a149c24a3a8755ca04583e5
Submitter: Zuul
Branch:    stable/queens"
1688620,2020-08-04 14:14:16 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/744724"
1688620,2020-07-29 23:55:41 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/743855"
1688620,2020-07-29 10:18:02 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/743718"
1688620,2020-07-30 23:51:57 UTC,"Reviewed:  https://review.opendev.org/743855
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=b8fc8feb070a61b957500a51a95af153da53a02c
Submitter: Zuul
Branch:    stable/rocky"
1688620,2020-07-28 15:18:59 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/743565"
1688620,2020-07-20 22:21:59 UTC,"Reviewed:  https://review.opendev.org/730383
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=71c3a08ead50e8aa68cef3a26c8f8485922895b6
Submitter: Zuul
Branch:    stable/ussuri"
1688620,2020-06-18 12:34:58 UTC,"Reviewed:  https://review.opendev.org/735384
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=a0dd86a98788f7e2d1ca55be26c2a3dea4e36f57
Submitter: Zuul
Branch:    master"
1688620,2020-04-07 21:38:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/718233"
1688620,2020-05-22 17:55:19 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/730383"
1688620,2020-05-22 17:52:16 UTC,"Reviewed:  https://review.opendev.org/718233
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=0ee414082318d22b3ed19acad6a479cb105c30e5
Submitter: Zuul
Branch:    master"
1688620,2020-07-29 05:08:48 UTC,"Reviewed:  https://review.opendev.org/743565
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=c915918f3c6ac608469263dd05e3f2b5eb61dc4e
Submitter: Zuul
Branch:    stable/train"
1688625,2017-08-29 16:41:14 UTC,"We assemble the pieces.
The touchpad manufacturer does not support Linux and refuses to give it."
1688625,2017-08-28 02:23:10 UTC,"On Sat, Aug 26, 2017 at 22:20 slimbook <email address hidden> wrote:"
1688625,2017-08-26 14:13:01 UTC,Hello @kaihengfeng
1688625,2017-08-18 04:30:44 UTC,"From the git log, I can see several commits are wrote by Elantech guy..."
1688625,2017-08-17 17:05:05 UTC,"Thanks @kaihengfeng
Neither Hantik nor Elan support Linux, we have already consulted with them.
We have the same computers with 2 different touchpad. We can assemble the orders with Cypress touchpad and Hantik touchpad (Synaptics does not manufacture in the correct size of these cases)"
1688625,2017-08-17 10:51:01 UTC,"Do, and the pointer is crazy.
:("
1688625,2017-08-17 10:26:27 UTC,"Try this:
$ sudo sh -c 'echo -n ""elantech"" > /sys/bus/serio/devices/serio2/protocol"
1688625,2017-08-16 13:28:39 UTC,"Sorry, attach now."
1688625,2017-08-17 15:40:24 UTC,"Well, then you probably need to ask Hantick or Elan for their support."
1688625,2017-06-27 05:30:40 UTC,"Otto,"
1688625,2017-06-26 13:53:40 UTC,I just tested with the latest 4.12rc7 kernel and it still detects the touchpad as a generic mouse:
1688625,2017-05-16 18:52:12 UTC,"Hello,
The problem continue."
1688625,2017-05-12 17:46:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1688625,2017-05-07 18:34:21 UTC,So perhaps it is possible to build a custom kernel for ubuntu with ELAN touchpad support enabled?
1688625,2017-05-07 14:10:20 UTC,"As I said at the beginning, the Miscrosoft Windows the Hantick touchpad is recognized as ELAN and works correctly.
Other linux users with other hardware recognized as ELAN, have more parameters available:"
1688625,2017-05-05 18:18:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688625,2017-05-05 18:17:38 UTC,"Details with ""libinput"""
1688625,2017-05-05 18:16:57 UTC,"Details with ""evdev"""
1688625,2017-08-16 13:28:20 UTC,"Hello @kaihengfeng,"
1688639,2017-07-26 05:31:04 UTC,Still not working copy/delete via ftp/ssh to a remote server.
1688639,2017-06-13 10:14:39 UTC,"not deleted, in various ways. I have Nautilus, with him no such problems."
1688639,2017-06-13 06:09:34 UTC,"In version 0.3.5, the files are copied, but now they can not depart from FTP."
1688639,2017-06-13 09:16:24 UTC,I also could not delete from a simple FTP server on my netwwork - but neither could FileZilla (permission denied).  I will have to set up another server with write permission to test this.  Make sure you have the necessary permissions on the server.
1688647,2017-05-05 20:30:02 UTC,"See also https://bugs.launchpad.net/hplip/+bug/1030639
I suspect this is the same bug."
1688651,2018-01-13 16:56:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688657,2017-05-05 21:37:45 UTC,Obviously backwards compatibility for a period will be crucial.
1688673,2020-07-13 15:21:49 UTC,"Reviewed:  https://review.opendev.org/461456
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9fc63c764429c10f9041e6b53659e0cbd595bf6b
Submitter: Zuul
Branch:    master"
1688673,2017-10-05 16:41:31 UTC,"Change abandoned by Chris Friesen (<email address hidden>) on branch: master
Review: https://review.openstack.org/461456
Reason: Abandoning this patch to instead add a new extra-spec/property along the lines of what Jay Pipes proposed."
1688673,2017-06-23 14:48:27 UTC,"There is an open review for this bug, don't know why the link wasn't added:"
1688673,2017-06-23 12:55:11 UTC,"There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments."
1688673,2017-06-27 19:29:01 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1688683,2018-09-24 13:57:54 UTC,"In case the code changes, the latest version of this patch can also be found there:
https://github.com/fgouget/hplip/commits/fixes"
1688685,2018-09-24 13:58:45 UTC,"More precisely it is on the fixes branch:
https://github.com/fgouget/hplip/commits/fixes"
1688686,2018-09-24 13:59:03 UTC,"More precisely it is on the fixes branch:
https://github.com/fgouget/hplip/commits/fixes"
1688689,2017-05-06 02:44:26 UTC,"Issue is also reproducible for files and folder within container, if container is btrfs subvolume instead of disk image."
1688689,2017-05-06 02:52:48 UTC,Example:
1688689,2017-05-20 07:52:14 UTC,https://github.com/systemd/systemd/issues/5900#issuecomment-300362005
1688697,2018-01-20 08:08:11 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1441
1688703,2017-05-06 10:44:30 UTC,"Yes, I think the guidance should be optimise by default. Developers can
override for their own debug builds, but what gets published in the
store should be aimed at general users and hence be both secure and fast."
1688709,2017-05-11 13:43:15 UTC,"On Wed, May 10, 2017 at 6:05 PM, Adrian Calvin <email address hidden>
wrote:"
1688709,2017-05-10 23:05:33 UTC,"Hi Edward,"
1688709,2017-05-07 15:27:08 UTC,"On Sun, May 7, 2017 at 6:51 AM, Adrian Calvin <email address hidden>
wrote:"
1688709,2017-05-07 11:51:46 UTC,OK thanks.
1688709,2017-05-07 09:28:45 UTC,"On Sat, May 6, 2017 at 3:25 AM, Adrian Calvin <email address hidden>
wrote:"
1688709,2017-05-06 20:12:11 UTC,Viewrendered plugin.
1688711,2017-05-31 12:48:50 UTC,Error in unsupported plugin - but will need to make dialog robust for such error
1688716,2017-09-02 15:52:19 UTC,apport information
1688716,2017-09-02 15:52:20 UTC,apport information
1688716,2017-09-02 15:52:21 UTC,apport information
1688716,2017-09-02 15:52:19 UTC,apport information
1688716,2017-09-02 15:52:24 UTC,apport information
1688716,2017-09-02 15:52:24 UTC,apport information
1688716,2017-09-02 15:52:26 UTC,apport information
1688716,2017-09-02 15:52:27 UTC,apport information
1688716,2019-05-16 11:06:12 UTC,"I am running Ubuntu MATE 19.04 on a Lenovo Thinkpad T470, without any dedicated graphics of any kind.  I have the same issue.  Upon closing the laptop, the screen turns off, but the machine is not suspended.  When I re-open the screen it is black, but still on.  Moving the mouse, using the keyboard doesn't do anything to fix the problem.  Changing the virtual terminal Ctrl + Alt + F1, then back again Ctrl + Alt + F7 starts the screen again, the lock screen is displayed."
1688716,2017-09-02 15:52:29 UTC,apport information
1688716,2017-09-02 15:52:30 UTC,apport information
1688716,2017-09-02 15:52:32 UTC,apport information
1688716,2017-09-02 15:52:33 UTC,apport information
1688716,2017-09-02 15:59:21 UTC,Issue updated. I'm not too sure what I did though.
1688716,2017-09-02 17:48:58 UTC,Maybe Launchpad is bugged? I don't see any attachment here...
1688716,2019-08-31 22:17:42 UTC,Have you tried touching it? I'm getting ready to try it on an amd/Radeon device. My first guess is there may be funny permissions in the x-org or hibernation files.
1688716,2017-09-02 15:52:28 UTC,apport information
1688716,2017-09-02 15:52:18 UTC,apport information
1688716,2017-09-02 15:52:22 UTC,apport information
1688716,2017-09-02 15:51:40 UTC,apport information
1688716,2017-08-27 19:51:38 UTC,What GPU/IGP and drivers are you using?
1688716,2017-08-27 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1688716,2017-08-28 11:22:09 UTC,"Hi,"
1688716,2017-08-29 05:18:08 UTC,Yes. Please run `apport-collect 1688716`.
1688716,2017-09-02 15:51:23 UTC,apport information
1688716,2017-09-02 15:51:24 UTC,apport information
1688716,2017-09-02 15:51:26 UTC,apport information
1688716,2017-09-02 15:51:27 UTC,apport information
1688716,2017-09-02 15:51:42 UTC,apport information
1688716,2017-09-02 15:51:29 UTC,apport information
1688716,2017-09-02 15:51:39 UTC,apport information
1688716,2017-09-02 15:51:38 UTC,apport information
1688716,2017-09-02 15:51:37 UTC,apport information
1688716,2017-09-02 15:51:28 UTC,apport information
1688716,2017-09-02 15:51:34 UTC,apport information
1688716,2017-09-02 15:51:31 UTC,apport information
1688716,2017-09-02 15:51:30 UTC,apport information
1688716,2017-09-02 15:51:35 UTC,apport information
1688717,2019-11-01 18:45:48 UTC,"Hi Wayne,
That’s OK as long as you’re keeping an eye open for this while you rework the file format.  I think changing the file format is a great time for this to be considered.
Some of the proposed implementation ideas to make sense: leave each schematic file as an item, and allow us to have multiple views within it.  I personally don’t care if we made use of a giant schematic canvas.  We have the commute and memory resources available. (The current file only allowed for a single title block IIRC.)  I want to be able to navigate and print that canvas as a bunch of A3 or B-size sheets.  I want to be able to navigate (warp) around that canvas as if flipping through pages.
BTW, did you intend to set a target release for this request?
I think this has been a significant limitation. I must admit I haven’t reassessed this request in light of bus harnesses being now available. One valid reaction I’ve heard from other designers is that the tool shouldn’t try to impose changes to the way we think about partitioning our designs.  The way we think may be wrong, but no better solution has emerged.
Berk"
1688717,2019-11-01 16:40:07 UTC,"If/when this does happen, it wont be until after the new schematic file format is implemented which is on the V6 road map.  I seriously doubt this feature request will happen in V6.  It's possible we could implement this in V7."
1688717,2019-10-31 02:17:33 UTC,A +1 for this. Any news on it?
1688717,2018-10-02 13:52:05 UTC,"@poeschlr said: ""Local labels apply to all pages on the same level. (Might be that they would need a new name in that case.)"""
1688717,2018-10-02 07:45:04 UTC,I fully agree with @berka on this one. There are workarounds available for some of the use-cases where having multiple pages of the same hierarchical sheet would be useful. (Especially for the ones regarding flat design.)
1688717,2018-08-11 08:43:05 UTC,Using global net names has been brought up before.  It doesn't work in the cases I'm talking about.  I'll pose the example again: 4 channels of DDR3 memory attached to a CPU: you can't use global net names in those blocks without shorting all 4 channels together.
1688717,2018-08-11 02:19:34 UTC,"Well, flat design with all global net name will work. Just use your first root page as a content summary of all the incoming schematic pages.... I see no issue at all! I think coding for the request require a lot of code hours with little gain here right?"
1688717,2018-07-23 12:39:43 UTC,I am hopeful.  Has this been fixed in 5.0.0?
1688717,2017-07-10 07:40:16 UTC,"@berka,"
1688717,2017-07-06 21:42:41 UTC,"@orsonmmz,
I don't follow how your workaround would apply.  That is the very problem I'm proposing be solved.  On a large design, the number of connections that would have to go on and off the root page are too large to manage on a reasonable sized sheet.  Also, global signals are not an option in  many large designs."
1688717,2017-05-16 06:59:24 UTC,"There is a much simpler workaround, though not so elegant. You can sacrifice the main schematic page to place subsheets there. In such case the hierarchy is root (the main page) with many leaves, effectively creating multiple sheets at the same level."
1688717,2019-11-04 12:46:00 UTC,"@Berk, it's much more involved than the file format changes.  There are some significant internal structural changes required to support this.  Otherwise, we could probably get it done during V6 development."
1688717,2017-05-15 12:12:06 UTC,"Please see the linked forum thread for history on this issue.  I am a 20-year user of various commercial schematic tools.  My first reaction was that I had to break old/bad habits, so I posed the question to the community.  I have not received a solution in the forum."
1688717,2017-05-13 13:05:26 UTC,"Ok, David's statement ""Forcing hierarchy and hierarchical pins and connections.."" is simply incorrect. So if you agree with that, you are not fully familiar with KiCad."
1688717,2017-05-13 01:16:56 UTC,"Hello Bob,"
1688717,2017-05-10 06:53:43 UTC,KiCad does not force the use of hierarchical pins for multi-sheet schematics.
1688717,2017-05-08 20:52:58 UTC,This is a significant limitation.
1688717,2017-07-10 07:42:53 UTC,"Have a look at 'flat_hierarchy' demo delivered with KiCad [1], it shows what I meant."
1688717,2017-05-15 12:20:14 UTC,"Another acceptable, and perhaps lighter-weight solution/workaround would be:
- Keep the eeschema single-sheet
- Allow adding more than one ""title block"" to the sheet.
  - this should probably be automated so that they can tile/snap reasonably.
- Have Print/Plot functions generate individual sheets for each title block."
1688719,2018-01-24 22:27:45 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-731
1688719,2017-05-09 13:29:25 UTC,"Hi,"
1688737,2017-05-06 16:15:05 UTC,has nothing to do with xorg
1688743,2017-05-13 18:52:18 UTC,Fixed by https://github.com/PintaProject/Pinta/pull/124
1688743,2017-05-12 22:46:49 UTC,Posted a pull request: https://github.com/PintaProject/Pinta/pull/124
1688743,2017-05-12 16:54:17 UTC,"It appears that there is already a ToolBarDropDownButton available in Pinta.Core/Classes/BaseTool, but its implementation isn't quite complete.
It only has two options -- Normal or Overwrite, which as I recall is all there is in Paint.net 3.x which Pinta is based on anyway."
1688743,2017-05-10 03:07:26 UTC,"Yeah, I guess the overwrite blend mode probably isn't too useful for layers, but I don't object to having it there if it makes the implementation simpler."
1688743,2017-05-09 16:53:39 UTC,"Also attached is a screenshot of the layer blend modes from 4.0.13.
It is worth noting that the 'Overwrite' option that is available in the pencil blend modes is not available in the layer blend modes."
1688743,2017-05-09 16:48:47 UTC,I'll see if I can find the time to look at this over the weekend.
1688743,2017-05-09 02:28:34 UTC,"Yeah, adding a new blend mode that maps to Operator.Source, and then adding a blend mode parameter to the tool, sounds like a good approach."
1688743,2017-05-06 20:02:36 UTC,"I've started to look at the source for this, and it appears that perhaps the bug is actually that the paint bucket tool is not honoring the blend settings under the hood."
1688743,2017-05-09 16:58:18 UTC,"One last note -- in paint.net 4.0.13 the full list of tools that include the 'Blending mode' drop down (I incorrectly referred to it as 'blend mode' in an earlier comment) are:
Paint Bucket, Paintbrush, Pencil, Gradient, Clone Stamp, Text, Line/Curve and Shapes
Probably any fix to the pencil tool should include a blending mode control that can be easily re-used in the other tools.
Also worth noting is that if you change the blending mode in one tool and then switch to another that honors it then the change you made is carried over to the new tool."
1688746,2017-05-06 15:03:26 UTC,"I attached a file with the same problem
Even trying to select the font displays a ""blank"" error message with an invisible text and invisible ok button"
1688746,2017-05-06 17:49:37 UTC,"Update:
The cause of the problem is the sample text, in my example file having no sample text doesn't cause a crash, but whenever I write 2 of the same characters next to eachother, it crashes"
1688746,2020-04-02 20:42:39 UTC,"So, I have an empty Sample Text box, but when I edit the kerning, it still crashes."
1688746,2020-04-02 20:43:22 UTC,"To specify, I was using the latest version."
1688749,2017-06-01 16:25:52 UTC,"As a workaround, if you use security with the tag parameter it does appear."
1688765,2019-05-14 19:33:11 UTC,"Bug report did not expire due to bug watch.
No problem here using Thunderbird 60.6.1 and Ubuntu 18.04.
Issues appear to have been fixed in bug 1687019."
1688765,2017-10-07 11:52:58 UTC,This problem still persists on Ubuntu 17.10 updated right now.
1688765,2017-08-25 21:12:33 UTC,"Finally found a workaround that works.
(credit goes to Salvador Pérez from https://addons.mozilla.org/de/thunderbird/addon/provider-for-google-calendar/reviews/?page=2)"
1688765,2019-02-09 14:26:11 UTC,Is this still an issue now that Thunderbird 60.4 is the currently supported version?
1688765,2017-05-10 09:09:42 UTC,"Also confirming behavior. Not 2FA enabled, but can't click on ""continue""."
1688765,2017-05-08 07:50:51 UTC,"I can confirm this behavior in Ubuntu 14.04 and thunderbird 45.8.0
In Windows 10 with thunderbird 52.0.1 this doesn't happen. I don't use 2 factor authentication."
1688765,2017-05-07 11:04:36 UTC,"Same problem here. Google pushed a new login screen for 2 factor authentication and some apps stopped working, like Epiphany, Gnome Online Accounts and Thunderbird."
1688765,2017-05-07 10:42:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688765,2017-08-20 12:23:00 UTC,Confirmed. This bug still exists in Ubuntu Artful (17.10) as of now.
1688890,2018-04-12 17:03:25 UTC,"@Richard, any followup on that testing?"
1688890,2018-04-16 19:36:24 UTC,"I haven't had a chance to write and test the zpool.cache copying. I keep meaning to get to it every day, but pushing it back for lack of time."
1688890,2017-06-26 12:21:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688890,2017-05-06 20:27:24 UTC,"The attachment ""honor misc /dev dirs"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1688890,2018-03-17 10:05:28 UTC,"I need to do some testing, but we might want to consider using the cache file. An approach (suggested to my by ryao, I think) was that we first import the root pool read-only, copy the cache file out of it, export the pool, and then import the pool read-write using the cache file."
1688911,2017-07-25 12:40:28 UTC,works on ubuntu-server but not on ubuntu-desktop
1688933,2017-11-16 16:23:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688933,2017-11-20 09:43:30 UTC,"Does anyone have an idea how to do a temp fix job on this? For us, this happens on an off the shelf gitlab AWS image (Ubuntu 16.04) Because the gitlab runners ssh into the gitlab server very many times, each one of those ssh logins needs to timeout on the login1 hand off and sometimes it crashes the build, so it's pretty serious for us. This is our log"
1688933,2018-05-24 10:33:51 UTC,"I just noticed that I have the same exact issue. I am running Ubuntu 16.04 Desktop, I enabled multiarch support and I am running 32 bit installation with 64 bit kernel."
1688963,2017-07-08 14:01:05 UTC,What version of Pinta are you using? On which operating system? How are you selecting the text tool (shortcut or mouse click?). More information is needed. I cannot reproduce on Windows 10 with Pinta 1.7 daily build
1688983,2017-05-07 00:31:39 UTC,"Please note that this report kinda contains multiple bugs.
Feel free to split it apart once the individual bugs are isolated"
1688988,2017-05-07 01:22:43 UTC,"I found a way to do that using Gnome Encfs Manager. Steps:
1. Using the Gnome Encfs Manager, unmount the Encfs volume
2. Using the Gnome Encfs Manager, select the appropriate volume. Click on ""Configure the selected stash"" button. It looks like a wrench.
4. Click on ""Advanced..."" button
5. Using ""encfs_config_file:"" field. Type in the absolute path to you new "".encfs6.xml"" file location. For example: ""/media/USERNAME/USB-KEY/EncFS/EncFS-Volume-1/.encfs6.xml"" without the quotes.
6. Using the Gnome Encfs Manager, mount the volume. Done :)"
1688988,2017-05-07 21:21:04 UTC,Suggested mockup with numbers 1 and 2
1688991,2017-05-17 16:13:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1688991,2017-05-17 16:13:48 UTC,Same warning for me on Kubuntu 16.04 with 4.10.0-20-generic.
1688997,2017-08-10 21:40:25 UTC,"I'm still getting this bug. I think it has to do with changing the default measurement in document properties. If 9 switch from mm to put, it gets all screwy."
1688997,2017-05-07 13:53:29 UTC,"Now I cannot reproduce, using CLI or GUI. I may have erroneously viewed the OP's results."
1688997,2017-05-07 03:08:07 UTC,As you can see the image has been shrunk from the original svg.
1688997,2017-05-07 11:21:17 UTC,Reproduced using GUI with Inkscape 0.92.1 r15371.
1688997,2017-05-07 11:39:22 UTC,"not reproduced using Windows 10, Inkscape 0.92.1 r15371, and the command:
inkscape --file=""exportBug.svg"" --export-pdf=""mycliexport.pdf"""
1689003,2017-05-12 11:49:57 UTC,"The attached simple program, compiled as a library, loaded by LD_PRELOAD before starting QEMU, avoids the problem by faking success of libusb_set_configuration(), as a workaround."
1689003,2020-11-09 17:03:34 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1689003,2021-01-09 04:17:45 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1689011,2018-09-06 07:50:44 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/529530
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1689011,2017-10-07 16:49:09 UTC,Clearing the assignee due to inactivity
1689011,2017-12-21 10:06:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529530"
1689035,2017-08-16 00:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1689048,2017-05-07 13:41:36 UTC,assign it to me
1689052,2017-05-07 13:45:01 UTC,Thanks @ian for confirming the bug.
1689052,2020-10-23 14:51:15 UTC,This is indeed a real issue. I have the same problem.
1689054,2020-10-23 14:52:55 UTC,Cruellers are the best.
1689054,2020-10-23 16:23:54 UTC,Someone else ate them.
1689059,2017-05-07 13:44:26 UTC,How to make us growing faster in the community
1689059,2017-05-07 15:45:37 UTC,Setting a proper variables and be cared of convention
1689064,2017-05-07 15:57:10 UTC,"Failing in binding the DPDK interface using dev-nic-bind script
Below is the error:"
1689065,2017-05-07 17:28:32 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/463152"
1689067,2017-05-07 13:45:39 UTC,Missing free stickers
1689081,2018-01-16 08:43:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689083,2017-12-25 11:11:24 UTC,What version of Ubuntu are you using?  What version of Firefox are you using?
1689088,2017-05-07 15:04:14 UTC,Current workaround:
1689088,2017-05-14 04:50:57 UTC,"Implemented in
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15690.1.4"
1689088,2017-11-08 17:23:07 UTC,"""Current workaround: One can use the shell to do the work by using ""inkview folder/*.svg"" (works on Windows, too)"""
1689088,2017-11-14 22:00:59 UTC,"The problem is your command line:
The first quoted argument to the START command is the ""title"" to use for the started command window, so in your case
- %inkview% will be interpreted as the title
- ""%CD%\MyFile.svg"" will be interpreted as the command to run
  (which obviously fails and which is the error you're seeing)"
1689090,2017-05-07 15:11:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463145"
1689090,2019-10-07 21:10:58 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.opendev.org/463145
Reason: Hi, I'm going to abandon this by doing an overall project cleanup. Please feel free to reopen this. Thanks."
1689096,2018-06-17 22:41:28 UTC,pypolicyd-spf is in maintenance only mode. Transferring to spf-engine for future consideration.
1689131,2017-08-04 07:05:26 UTC,Also causes inability to save service lists if media files (with wrong paths) are included.
1689131,2017-08-05 02:28:18 UTC,phill is busy with a change that will fix this bug.
1689138,2017-05-07 20:25:00 UTC,"The attachment ""gl.po.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1689138,2017-05-29 06:36:04 UTC,This bug was fixed in the package wicd - 1.7.4+tb2-4
1689171,2017-05-07 19:18:50 UTC,This has been addressed with patch https://review.openstack.org/#/c/463161/1
1689199,2018-01-18 08:18:04 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1975
1689199,2017-05-13 12:36:23 UTC,"Hello,
I didn't found the possibility to replicate the issue, but I found this in logs. It seems, that the crash is always preceeded by the killed thread and also that it's (at least during the last 10 days) connected with the same SQL command."
1689199,2017-05-13 12:38:47 UTC,"Is there any way so I can find out more? I was also able to capture the network traffic (captured ports 3306 and 4567). I can provide that also if you think it might help.
If there is some possibility to increase log level to help you sorting this issue out  or any other possibility to know more, just let me know."
1689199,2017-05-10 04:59:05 UTC,I couldn't reproduce the issue but it sounds like once u hit the DUPKEY issue all of following are repercussion from the said problem.
1689199,2017-05-08 13:42:09 UTC,"Hello,
I've turned on the wsrep_debug. Another crash of two nodes just happened, so I'm sending the logs since the last crash from all 3 servers.
The servers in my cluster (added names for clarity):
10.0.0.101 irbis
10.0.0.102 jaguar
10.0.0.103 puma"
1689199,2017-05-09 09:56:20 UTC,I couldn't trace the exact issue but I found that problem has to do with following
1689199,2017-05-08 13:43:38 UTC,"Also i'm using only the standard Percona mutli-master replication between the nodes, nothing else (like master-slave replica or so)."
1689199,2017-05-08 01:39:59 UTC,"Log suggest that some incompatible workload execution.
Do you have async master-slave replication link too."
1689199,2017-05-09 10:39:41 UTC,"Hello,
it's not only about dupe key (today morning crash):"
1689200,2017-06-10 03:00:13 UTC,this is an upstream bug in debian
1689234,2017-05-08 09:43:17 UTC,"This item is unclear. We need to figure out if the z specific requirement of >=512MB memory for a partition has impact on our host specific config option ""max_memory""."
1689234,2017-05-08 09:56:02 UTC,The >= m512 thing is handled in bug. https://bugs.launchpad.net/nova-dpm/+bug/1689267
1689234,2017-05-08 10:33:13 UTC,This bugs also tells that if value is less than 512 it should raise some exception in case there is some special parameter which rounds up to 512 needs to be verified under this bug
1689234,2017-06-21 08:41:11 UTC,"I found that the HMC rounds up values to certain boundaries. For example, specifying 2024 will be rounded up to 2048. I don't know whether that will happen with all input values. So if somebody is aware of a value that got rejected as invalid by the HMC, please post that to this defect."
1689234,2017-09-27 07:56:01 UTC,Devstack need certain memory for its cloud i.e max_memory which is monitored and viewed in the hypervisor list in dashboard. There is filter which checks this max_memory value allows the instances to be launched on cloud ...According to my understanding this max_memory is provided in local.conf used by devstack and HMC rounding has nothing to do with this as we allocate the memory details of the partition during its creation itself.
1689234,2017-09-27 08:00:45 UTC,So may be this value needs to be restricted to multiples of 512 so that max_memory parameter which restricts the maximum instances memory used efficiently
1689234,2017-10-11 09:35:11 UTC,"@andreas max_memory min value is 512 so may be we should change the summary and description to 512
https://github.com/openstack/nova-dpm/blob/9eceb535190b7bddedfce2bbff7bad69dec0416f/nova_dpm/conf/dpm.py#L34"
1689235,2017-05-19 16:02:55 UTC,This issue I had face twice.
1689235,2017-05-23 14:46:53 UTC,On which node(s) are you getting the error? Also please provide the Fuel snapshot so we can investigate the problem.
1689235,2017-05-25 13:13:35 UTC,"Hi Simon ,I get this error from node who enable SRIOV. I am sorry that env had be change, can not provide Fuel snapshot"
1689245,2021-01-09 04:17:46 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1689245,2017-05-08 10:33:18 UTC,"I try this steps and meet the similar issue:
1. Deploy a VM in ESXi from https://bintray.com/vmware/photon/download_file?file_path=photon-custom-hw10-1.0-62c543d.ova
2. Copy vmdk and flat.vmdk file
3. Convert from vmdk format to raw via qeum-img(qemu-img convert -f vmdk -O raw Photon.vmdk Photon.raw)
4. Launch the qcow2 image. The VM is started. And the splash screen is showed. But then there is no any output."
1689245,2020-11-09 17:05:04 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1689246,2017-05-08 08:29:54 UTC,savegame #2
1689246,2019-09-17 07:00:51 UTC,Migrated to https://github.com/widelands/widelands/issues/3199
1689253,2017-05-17 16:19:43 UTC,"I cannot reproduce the problem. I created the table, loaded 100K rows with random data including single quotes, double quotes, question marks, etc, but I am still not getting an error."
1689253,2017-05-17 19:23:53 UTC,i'll try to identify problematic dataset.
1689253,2017-05-17 15:49:34 UTC,"You may see here it falls here, it looks like where condition cause this issue:"
1689253,2017-05-17 15:32:20 UTC,I still cannot reproduce the problem.
1689253,2017-05-16 21:51:29 UTC,"Thanks a lot,"
1689253,2017-05-16 18:12:02 UTC,It looks like the problem might be the single quotes inside the subid field.
1689253,2017-05-16 07:55:09 UTC,"We'll need to reproduce this case, please share the following:
- mysql/mariadb version used on master and slave
- pt-table-checksum/pt-table-sync versions used
- table definition for vrtb.playerVastsStatsByDomain"
1689253,2017-05-12 17:49:27 UTC,"Is it possible to prioritize it? It is impacts us a lot, thank you in advance"
1689253,2017-05-08 09:11:46 UTC,Checksum table:
1689253,2017-05-08 09:11:22 UTC,Attached debug
1689253,2017-05-08 09:08:39 UTC,I see the root cause of the issue is:
1689253,2017-05-16 19:44:50 UTC,"Single quotes are not the problem.
I've tested using this:"
1689253,2018-01-24 22:27:49 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-732
1689253,2017-05-17 16:06:32 UTC,it looks like symbols ? cause to mess things ...
1689257,2018-02-20 06:25:15 UTC,Persists in current 18.04 release.
1689257,2018-03-22 11:46:37 UTC,"The ""compatibility"" .desktop files we add to some packages have multiple bugs. See LP: #1606901."
1689261,2017-05-08 11:02:04 UTC,"To make my workaround permanent, I tried adding the following lines to /etc/network/interfaces:"
1689261,2017-05-08 12:45:02 UTC,"Ok, I found a workaround here:
https://askubuntu.com/questions/865945/after-upgrade-to-16-10-ethernet-stopped-working"
1689264,2017-10-09 12:44:35 UTC,"Upstream bug fixed in 5.6.39, 5.7.21, 8.0.4"
1689264,2018-01-25 09:15:47 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1090
1689265,2017-10-09 13:56:06 UTC,"I'd vote for the second option, i.e, to live with this and print warning messages, as it is rounding off to the nearest multiple of 256, and according to me this is ok to live with."
1689265,2017-10-10 13:50:30 UTC,"we should not silently accept the rounding taking place.
My preferred way is to check for the actual memory consumption after the create partition has been triggered, and report this back to scheduler (i.e. update in nova database). However, I didn't check if this is possible from both current zhmcclient and nova(-spawn) implementations..."
1689265,2017-10-09 12:15:19 UTC,I think the solution is to deny instance creation if the flavor has a ram size that requires rounding (is not a multiple of 256) with an appropriate error message in the log. We should also add this piece of information to the docs.
1689265,2017-10-06 06:54:50 UTC,nice elaboration!
1689265,2017-10-06 06:32:58 UTC,"Yes I tried a scenario in which I gave the flavor as 1000MB ram with the ram_allocation_ratio as 1 and due to the HMC rounding property it rounded off this value to 1024MB and launched an instance...but the in the dashboard under the hypervisor stats it is showing as ram-used 1000MB and also ram_filter which is a scheduler filter com pares this condition
https://github.com/openstack/nova/blob/4f91ed3a547965ed96a22520edcfb783e7936e95/nova/scheduler/filters/ram_filter.py#L39
even this parameters like memory_mb are all taken from the flavor so...there are two problems in this"
1689265,2017-05-08 10:29:25 UTC,I think this is duplicate of https://bugs.launchpad.net/nova-dpm/+bug/1689234
1689265,2017-05-08 10:44:26 UTC,"no, this one is about the dpm partition memory properties, while the bug you are referring to is about the max_memory openstack dpm property"
1689265,2017-10-11 08:52:23 UTC,There are a copule of other bugs related to memory. I guess this is an area that needs some love
1689265,2017-10-11 08:04:29 UTC,This also solves this bug https://bugs.launchpad.net/nova-dpm/+bug/1691039
1689265,2017-10-11 07:55:41 UTC,"Yes as andreas told we are reporting the right value by [1] https://github.com/openstack/nova-dpm/blob/cb0074b90e432ffcb3c971576cfda65d84d855dc/nova_dpm/virt/dpm/host.py#L109,L115  but the hypervisor metrics are shown wrong as they are looking at the memory value consumed as  the flavor RAM value that is provided  ...I would like to attach the screenshot of the hypervisor stats tried for the above usecase"
1689265,2017-10-11 06:53:43 UTC,@Marco: But that doesn't solve the issue 2 issues sreeteja laid out.
1689284,2017-05-24 01:56:14 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/467441"
1689284,2017-05-09 18:45:06 UTC,"Oh I see, here:"
1689284,2017-05-19 03:05:29 UTC,"Reviewed:  https://review.openstack.org/464548
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=29c8ae3cd9653b310c3fac803e6295e5fa885d15
Submitter: Jenkins
Branch:    master"
1689284,2017-05-23 06:28:14 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/467028"
1689284,2017-08-28 09:54:55 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1689284,2017-08-21 19:07:21 UTC,"Reviewed:  https://review.openstack.org/467441
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5448a44c703c96d38ebfaf768214bf0600364c5b
Submitter: Jenkins
Branch:    stable/newton"
1689284,2017-06-08 21:52:18 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1689284,2017-05-30 15:54:20 UTC,This issue was fixed in the openstack/nova 15.0.5 release.
1689284,2017-05-09 18:40:51 UTC,"Kevin, can you please provide recreate steps or links to specific code?"
1689284,2017-05-23 23:59:52 UTC,"Reviewed:  https://review.openstack.org/467028
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b59d60f9520c7a1992a5753517e472f6dd8b85d
Submitter: Jenkins
Branch:    stable/ocata"
1689289,2020-03-18 08:04:51 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/463466
Reason: This is a pretty old patch in merge conflict. Feel free to restore it (or ask gibi on irc to restore it) if you still working on it."
1689289,2017-06-27 15:58:30 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1689289,2017-05-09 05:41:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463466"
1689294,2019-10-24 09:50:07 UTC,"> I am running out of intelligence on this issue now.
"
1689294,2019-10-24 11:10:59 UTC,"OK, the last two lines of previous comment are my fault - I fixed it."
1689294,2019-10-24 11:17:43 UTC,"try gcc options -save-temps -v, the former keeps all temp files, the later prints all tools componenents."
1689294,2019-10-24 12:45:14 UTC,"Nothing conclusive. The -v only display what GCC invokes, but verbosity is not passed down to ld and lto-wrapper."
1689294,2019-11-20 14:21:13 UTC,I managed to rebuild the toolchain in Windows Subsystem for Linux on Ubuntu 16.04.
1689294,2019-10-23 22:11:18 UTC,"> I am running out of intelligence on this issue now.
"
1689294,2019-10-23 16:04:22 UTC,89183 has been fixed in 8.3.1-2019q3. The attached case passed with that version.
1689294,2019-10-21 14:31:38 UTC,"So, with 8.3.1-2019q3 things are even worse, even adding the `bin` directory of the toolchain doesn't help gcc/ld in finding `lto-wrapper.exe` causing the error. The problem applies only to scenarios where linking gcc is invoked with `-flto=n` or `-fuse-linker-plugin. The inability to use the former strips us from even more aggressive optimisations."
1689294,2017-06-02 13:03:56 UTC,"Note that in order to recreate this issue, parallelised LTO should be employed using -flto=<n>"
1689294,2019-10-23 15:58:23 UTC,"Michal,"
1689294,2019-10-23 13:58:00 UTC,"Michal,"
1689294,2019-10-23 13:02:06 UTC,Ich bin bis 28.10. nicht im Haus und kann Ihre Nachricht daher leider nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
1689294,2019-10-23 12:45:44 UTC,"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89183
Is this bug fix included in 8.3.1-2019q3?"
1689294,2019-10-23 12:44:19 UTC,"Is it really ""Invalid"" as the error isn't informative regarding the problem? It's very hard to guess that's missing make problem (not an issue on Linux system, quite a trouble on Windows)."
1689294,2019-10-23 12:39:15 UTC,"My project with -fno-exceptions and -flto (so, not parallel & no plugin) still fails with the same error, however I can't make minimal example failing."
1689294,2019-10-23 15:37:14 UTC,"Yes, that's going to be hard. The problem exists on my proprietary project I cannot publish from obvious reasons. It's big, it's several libraries + main code, I can't figure out which library triggers lto-wrapper.exe at the final stage. A variant with exceptions works on one build server, but fails on another with the same error."
1689294,2019-10-22 17:08:44 UTC,"Further analysis suggests that missing make.exe in PATH is the root cause of the reported error message. As make.exe is not part of GCC, but is needed in -flto=n, user must make sure that make.exe be accessible in PATH."
1689294,2019-10-22 16:40:51 UTC,"At the same time please avoid -flto=n on Windows to workaround. -flto=n needs an installed make, which is easily to mess up on Windows."
1689294,2019-10-22 16:36:27 UTC,Reproduced with -flto=3. Looks like a LTO bug on windows
1689294,2019-10-22 15:33:18 UTC,"I can't find the rule where use of -fuse-linker-plugin causes the lto-wrapper.exe problem. Interestingly, I know build all with exceptions disabled..."
1689294,2019-10-21 14:57:07 UTC,"Michal,"
1689294,2019-10-22 13:30:13 UTC,"Thank for getting back to me @jinyun-ye, but your example it too simple."
1689294,2019-10-22 17:21:04 UTC,Ich bin bis 28.10. nicht im Haus und kann Ihre Nachricht daher leider nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
1689296,2017-05-08 13:05:32 UTC,The following patches were skipped because they were already applied:
1689296,2017-06-06 14:51:25 UTC,This bug was fixed in the package linux - 4.4.0-79.100
1689302,2019-10-15 12:49:50 UTC,"I just checked that program_usb_mode is indeed not surfaced through snappy configuration. Having said that, it feels like a weird configuration, especially since it is one-way-fuse that is being programmed."
1689302,2017-05-19 14:18:12 UTC,"Sergey asked whether this would require two gadget snaps: one for device that boot from usb, one from devices that work from sd."
1689302,2017-05-16 15:38:19 UTC,"What is the status of this bug? It was filed by a client project developer and I'd like to know if it is fixed, invalid, etc. Cheers."
1689302,2017-05-16 16:44:31 UTC,this should simply be set in their gadget snap in the original config.txt. the bootloader will apply it before the first boot (where potentially the config.txt gets re-written by the core config hook)
1689302,2017-05-17 04:53:47 UTC,"@Sergey, Kyle: Would Oliver's suggestion help to solve your issue?"
1689309,2018-04-17 08:01:04 UTC,"------- Comment From <email address hidden> 2018-04-17 03:57 EDT-------
Canonical, any update on this LP ?"
1689309,2020-04-23 19:55:57 UTC,"The new installer is now out, and supports configuring many networks at the same time."
1689309,2018-04-17 08:29:16 UTC,"d-i only supports configuring only one network connection. This is unlikely to change, even for the 20.04 timeframe. The workarounds are 1) getting install media exported on the same network as the network attached hard drives 2) configuring additional network interfaces by-hand using d-i interactive shell."
1689309,2017-05-11 11:49:59 UTC,"------- Comment From <email address hidden> 2017-05-11 07:46 EDT-------
(In reply to comment #10)

> And when I mean editing the /etc/network/interfaces, I mean
> /target/etc/network/interfaces at the end of the installation once netcfg
> purged and recreated it. Such that the installed system has correct
> interfaces.
>
> Looking at the interfaces from the logs, it only has one vlan defined. Thus
> ence530.209 is missing from /target/etc/network/interfaces which needs to be
> adjusted when installer offers to ""finish & reboot"", by going back to the
> main menu and dropping into the shell, editing that file, and updating
> initramfs in-target.
"
1689309,2019-06-03 16:46:04 UTC,Setting to 'In Progress' with the work on subiquity.
1689309,2017-05-11 10:34:37 UTC,"from the interactive shell of d-i, one should be able to do:"
1689309,2017-05-11 10:30:38 UTC,------- Comment (attachment only) From <email address hidden> 2017-05-11 06:19 EDT-------
1689309,2017-05-11 10:30:13 UTC,"------- Comment From <email address hidden> 2017-05-11 06:24 EDT-------
Sorry the file is larger than 10 MB and in case mirroring doesn't work, here's a link to the same file:
https://testcase.software.ibm.com/fromibm/linux/installer_logs_interfaces.tar"
1689309,2017-05-08 17:14:49 UTC,"When you brought up the networking manually, did you write out the updated /etc/network/interfaces and updated the target initramfs? By e.g. dropping back into shell at finish install step."
1689309,2017-05-11 10:19:21 UTC,"------- Comment From <email address hidden> 2017-05-11 06:18 EDT-------

> When you brought up the networking manually, did you write out the updated
> /etc/network/interfaces and updated the target initramfs? By e.g. dropping
> back into shell at finish install step.
"
1689309,2017-05-11 10:38:40 UTC,"And when I mean editing the /etc/network/interfaces, I mean /target/etc/network/interfaces at the end of the installation once netcfg purged and recreated it. Such that the installed system has correct interfaces."
1689341,2020-04-25 13:09:39 UTC,pydb isn't in focal anymore
1689344,2017-05-22 15:42:15 UTC,This bug was fixed in the package apport - 2.20.3-0ubuntu8.3
1689344,2017-05-22 15:31:50 UTC,"The verification of the Stable Release Update for apport has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1689344,2017-05-22 15:31:39 UTC,This bug was fixed in the package apport - 2.20.4-0ubuntu4.1
1689344,2017-05-15 22:09:18 UTC,Verification for yakkety:
1689344,2017-05-12 18:02:00 UTC,"Hello Brian, or anyone else affected,"
1689344,2017-05-09 21:05:23 UTC,"I tested the yakkety core file and binary with a xenial version of gdb and didn't still received the cannot access memory error, so I don't think its a gdb bug."
1689344,2017-05-08 22:00:48 UTC,This bug was fixed in the package apport - 2.20.4-0ubuntu6
1689344,2017-05-08 19:34:43 UTC,This was not failing in the autopkgtest for yakkety but does now in a chroot.
1689344,2017-05-08 17:50:17 UTC,It's also worth noting that running strings on the core file does reveal the contents of the assertion message.
1689344,2017-05-08 17:15:53 UTC,"There is another apport test, ""test_add_gdb_info_abort_libnih"", which was disabled for similar reasons - e.g. ""Cannot access memory""."
1689344,2017-05-12 17:49:07 UTC,"Hello Brian, or anyone else affected,"
1689355,2017-05-19 08:01:07 UTC,"The output for new added server resource (os::nova::Server) in ""Update Heat Stack preview"" should be identical to ""Heat Stack Create preview"". but that is not the case."
1689356,2018-03-18 11:50:56 UTC,"Confirmed on Ubuntu 16.04.4
Dmitry's fix seems to work, although (at least in my case) browsers (Chrome, Firefox) no longer seem to be be aware of HiDPI display and do not adjust scaling accordingly anymore."
1689356,2018-03-21 20:31:11 UTC,Same problem here in 16.04.4 after updating to unity 7.4.5.
1689356,2018-03-26 17:56:40 UTC,"With Ubuntu switching to GNOME, looks like Unity folks don't care about this anymore."
1689356,2018-03-29 00:32:05 UTC,Thank you Park very much for the patch! I am running Xenial (16.04) and installed the patch yesterday. Both fractional scaling issue and reset issue were fixed and the ubuntu has been running well since then.
1689356,2018-03-29 00:34:51 UTC,"By the way, I am using native ubuntu and a 4k monitor."
1689356,2018-05-14 15:06:19 UTC,"@arter97 yes, thank you for this fix, it works great for me too."
1689356,2018-04-08 22:20:55 UTC,"In my case, simply turning the monitor off and on would reset scaling to 1. Can confirm that Dmitri's fix works for me."
1689356,2018-08-28 07:26:20 UTC,"@arter97
can you post a link to the repo and or the two commits you mentioned? I don’t find my way to the source the package is build of. I assume it’s somewhere here on launchpad, but this thing is so confusing I never find anything."
1689356,2018-08-28 07:48:13 UTC,Neatly uploaded in my GitHub repository:
1689356,2018-03-18 08:58:16 UTC,"I have the same behavior on 16.04 after last kernel update, I am on 4.13.0-36-generic now and I was on 4.10.0-42-generic before that started happening."
1689356,2018-03-30 13:32:58 UTC,"Awesome, thanks for the confirmation :)"
1689356,2018-03-14 09:56:29 UTC,I have the same problem in 16.04. (It only started happening in 2 days ago.)
1689356,2018-03-14 10:01:05 UTC,Thank you fcole90 for the link.  :)
1689356,2017-05-08 21:15:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689356,2018-03-13 12:19:48 UTC,"Got the same problem on 16.04. It seems the issue was caused by Unity upgrade to 7.4.5.
I manually downgraded it to 7.4.0 and the issue was gone:"
1689356,2017-05-18 13:24:11 UTC,My desktop has integrated Intel gfx so the bug seems to be not related to gfx driver.
1689356,2017-09-17 15:01:15 UTC,To be able to use the UI of both Ubuntu and any applications you're using when running Ubuntu in a high resolution mode you have to use the UI scale settings. With the scale settings resetting every time the display sleeps a high resolution setting becomes practically useless.
1689356,2018-02-24 00:02:38 UTC,I just started seeing this behavior on 16.04.
1689356,2018-02-24 14:13:58 UTC,"Happening to me as well since few days. I tough it was a configuration issue, but probably this is a regression caused by some backport."
1689356,2017-11-06 06:36:24 UTC,"Also it is pretty annoying to restart all automatically started application (for example Slack, shutter and owncloud) that doesn't pickup the correct setting and the window layout is messed up."
1689356,2018-02-24 14:38:53 UTC,Reference on how to write/read these values: https://askubuntu.com/a/510476
1689356,2018-02-28 11:58:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689356,2018-02-28 21:21:34 UTC,"Started seeing this behaviour on 16.04 (fully updated), since 26-Feb."
1689356,2018-03-07 22:06:24 UTC,Just updated 16.04 and seeing this behavior.
1689356,2018-03-08 12:00:01 UTC,I have an the same problem. It is very unpleasant.
1689356,2018-02-24 14:37:59 UTC,Temporary workaround for me is to use
1689365,2017-06-05 15:49:31 UTC,"------- Comment From <email address hidden> 2017-06-05 11:48 EDT-------
So in terms of testing... I had someone in our internal IBMi OS team manually send abort operations so that it would trigger this bug. I wouldn't know how you would test it since the bug was found through them in the first place."
1689365,2017-08-30 20:39:53 UTC,"------- Comment From <email address hidden> 2017-08-30 16:30 EDT-------
I added the keyword: verification-done-zesty"
1689365,2017-08-28 10:14:27 UTC,This bug was fixed in the package linux - 4.10.0-33.37
1689365,2017-08-16 16:34:06 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1689365,2017-07-31 15:59:40 UTC,"------- Comment From <email address hidden> 2017-07-31 11:57 EDT-------
The reason target: Fix unknown fabric callback queue-full errors is required is because if ibmvscsi driver returns a non -EAGAIN or -ENOMEM error back to target-core then outgoing responses are leaked. This case is seen in ibmvscsis_write_pending, we added code to return 0 to address cases where if client failed or response queue is down to just return success to LIO, since they can't do anything about it. (This is part of ibmvscsis: Do not send aborted task response patch)  But for cases where we attempted to transfer the data and it failed and we return a -EIO, target core would leak. Thus we need the target-core fix to address the 2nd part of that issue."
1689365,2017-07-31 15:25:40 UTC,I got the following review comments for SRU from kernel team. IBM could you please comment?
1689365,2017-06-05 15:19:26 UTC,"------- Comment From <email address hidden> 2017-06-05 11:15 EDT-------
Works fine, thanks!"
1689365,2017-05-10 20:19:35 UTC,------- Comment on attachment From <email address hidden> 2017-05-10 16:17 EDT-------
1689365,2017-05-24 13:59:38 UTC,"------- Comment From <email address hidden> 2017-05-24 09:58 EDT-------
The patch are upstreamed now, since 4.12 rc1 window is now open."
1689365,2017-05-17 19:09:02 UTC,Will roll up a test kernel once these patches land upstream.
1689365,2017-05-15 14:09:52 UTC,"------- Comment From <email address hidden> 2017-05-15 10:02 EDT-------
ibmvscsis: Clear left-over abort_cmd pointers
ibmvscsis: Fix the incorrect req_lim_delta"
1689365,2017-05-12 20:16:25 UTC,I am a bit confused by the last couple of comments. The current test kernel has the following patches:
1689365,2017-05-10 18:59:20 UTC,------- Comment on attachment From <email address hidden> 2017-05-10 14:57 EDT-------
1689365,2017-05-10 18:59:18 UTC,"------- Comment From <email address hidden> 2017-05-10 14:58 EDT-------
Which has also been accepted by maintainer - https://www.spinics.net/lists/linux-scsi/msg108639.html"
1689365,2017-05-09 21:40:48 UTC,Can you please test the kernel in https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/test/ and report back here?
1689365,2017-06-02 22:17:29 UTC,I have submitted this patch series for SRU. Please test the kernel in https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1689365/ and report back here so that the Ubuntu kernel team has added confidence is picking up these patches. I boot tested the kernel on a Power8 and did not find any regressions. A functional test to make sure the patch fixes the issue is useful.
1689366,2017-05-09 07:49:00 UTC,Duplicate of https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/23
1689369,2017-05-10 10:49:32 UTC,"Yes, you nailed it, thanks :)"
1689369,2017-05-09 11:51:31 UTC,"We won't be killing the idea of a project default repository; it's a core part of Launchpad's git layout, and very useful in other contexts.  You've gone a few steps too far in your diagnosis as a result of being confused by the UI, I think."
1689369,2017-05-08 18:26:43 UTC,"Note that the ""owner default"" textbox has the label which says:"
1689378,2017-05-25 21:36:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689390,2017-05-10 22:47:16 UTC,"Your problem is that Nvidia experiences errors when building for this kernel. It needs a new patch, try contacting people here:"
1689390,2017-05-10 22:49:48 UTC,"Sorry, there actually is a new patch: https://pkgs.rpmfusion.org/cgit/nonfree/nvidia-340xx-kmod.git/plain/4.11_kernel.patch"
1689390,2017-05-13 17:37:19 UTC,"Distribution: Ubuntu 17.04
System architecture: amd64
Running kernel: 4.10.12-041012-generic
Kernel version: 4.10.12-041012-generic
Using cache directory: /home/aio/.cache/ukuu
Found installed: 4.6.7-040607.201608160432
Found installed: 4.9.0-040900.201612111631
Found installed: 4.8.17-040817.201701090438
Found installed: 1.0.amdgpu
Found installed: 4.10.6-041006.201703260832
Found installed: 4.8.7-040807.201611101131
Found installed: 4.7.3-040703.201609070334
Found installed: 4.2.8-040208.201512150620
Found installed: 4.10.0.21.23
Found installed: 4.10.0-20.22
Found installed: 4.10.12-041012.201704210512
Found installed: 4.10.0-21.23
Found installed: 4.7.2-040702.201608201334
Found installed: 4.10.8-041008.201703310531"
1689390,2017-05-13 17:40:03 UTC,"DKMS make.log for spl-0.6.5.9 for kernel 4.11.0-041100-generic (x86_64)
Sun 14 May 03:28:51 AEST 2017
make: *** No targets specified and no makefile found.  Stop."
1689390,2017-05-13 17:52:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689390,2017-05-13 21:55:57 UTC,"I've been about two days recovering my Ubuntu  in a try to update the nvidia driver...
I don't know if want to try to update the kernel now :-))"
1689398,2018-03-26 20:17:15 UTC,Assigning to the artwork lead for Lubuntu.
1689398,2018-03-26 17:41:46 UTC,beta 18.04 the same. White clock font on light panel
1689398,2017-11-18 22:49:58 UTC,I had the same problem when I installed Lubuntu Next 17.10.
1689398,2018-03-26 17:41:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689398,2017-05-09 22:24:03 UTC,"Appearance: theme-name --- > ""Lubuntu-dark-panel""
solved the issue."
1689408,2017-05-11 03:06:45 UTC,"Created attachment 131305
dmesg"
1689408,2018-08-31 23:09:19 UTC,"(In reply to Timothy Arceri from comment #8)

> Is this working for you now?
"
1689408,2018-08-31 06:35:41 UTC,Is this working for you now?
1689408,2017-05-11 04:53:58 UTC,"great, thanks"
1689408,2017-05-11 03:16:05 UTC,"(In reply to Michel Dänzer from comment #5)

> Is this a regression from an older version of Mesa? If so, can you bisect?
"
1689408,2017-05-11 03:11:49 UTC,"Created attachment 131306
post-hang xorg log, may not be relevant"
1689408,2017-05-11 03:09:17 UTC,"Is this a regression from an older version of Mesa? If so, can you bisect?"
1689408,2018-09-03 01:35:54 UTC,"Fix status is unknown and untested, it may not be fixed at all, I simply lack the hardware to actually test it."
1689408,2017-05-11 03:03:47 UTC,"Created attachment 131304
glxinfo, should contain all the hardware and package info needed"
1689408,2017-05-11 02:54:48 UTC,Please attach the output of glxinfo and dmesg and the Xorg log file.
1689408,2017-05-11 02:53:10 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=100995
1689408,2017-05-11 02:52:45 UTC,"This is easily reproducible via unigine's heaven benchmark, simply running it with normal tessellation settings results in the screen flashing black a few times and then an eventual system hang before anything even starts to render. A power cycle is the only way out."
1689408,2017-05-10 13:32:24 UTC,so file it upstream
1689408,2017-05-10 11:32:20 UTC,"The default is ignored however if the game requires tessellation or other 4+ features, which is pretty much every big game released in the past few years..."
1689408,2017-05-10 06:35:28 UTC,since the default is safe I'll lower the importance
1689408,2017-05-08 23:30:10 UTC,This change was made by a bot.
1689408,2017-05-11 03:01:24 UTC,"Created attachment 131303
errors that appear to be related to the hang"
1689413,2017-05-09 00:23:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1689413,2017-05-26 00:06:50 UTC,[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]
1689434,2017-05-09 03:01:36 UTC,Dropping severity to medium until such time as it is known to still occur in zesty (or yakkety).
1689446,2017-10-20 03:59:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689488,2017-09-06 14:49:55 UTC,"Hi,
I'm currently cleaning up dormant virtualization stack bugs.
Lets take the easy step first, Yakkety is EOL so this is Won't Fix."
1689488,2017-09-06 14:55:13 UTC,"Hi Gerd and Yang,
I happen to consider your change [1] as a fix for [2], but so far lack a
way to reproduce.
The bug as well as the upstream discussion I found around the actual patch
lack the detail to come up with a test for it."
1689488,2017-09-07 06:17:33 UTC,"Got feedback from Yang, trying that later today.
Quote of the reply mail:
""Hi Christian,
You could use novnc to send a bulk of text to the VM’s vnc console in one request.
https://github.com/novnc/noVNC"""
1689488,2017-09-07 14:58:15 UTC,"Well, to some extend today I accidentally found that the default sdl frontent might have this issue as well.
If you start qemu by cmdline and e.g. just give it an ISO.
You need to slow that X11 connection down e.g. by running this via X11 forwarding across an ocean.
So the handling gets sloggy, which is fine (distance is distance, latency is ok).
Now in the framebuffer console make it roll the full console which is as easy as typing commands until the console is completely full and then do
- CTRL+C (will go down one line causing a lot of transfer)
- Immediately roll 1-0 on your keyboard
=> Result is that quiote often (>50%) only chars 1-7 or 1-8 appear."
1689488,2017-09-07 21:10:03 UTC,"Hi Christian,"
1689488,2017-09-08 10:41:26 UTC,"Thanks for your feedback, so to confirm"
1689488,2019-05-24 15:01:55 UTC,novnc 1.1 is in disco and later at least.
1689488,2017-05-09 07:41:02 UTC,Thanks for reporting that issue and your help to make Ubuntu better.
1689488,2019-05-24 11:01:36 UTC,"Hi Christian,"
1689495,2017-06-12 10:47:09 UTC,"The first I knew of it was an apport/whoopsie GUI popup, which then sent me to this bug IIRC. I installed this machine fresh from an Artful daily. The only relevant change I think I made was to add an apt proxy in /etc/apt.conf.d/. I don't have any other information and didn't save my traceback, assuming it was the same as in this report. I haven't seen the issue since, though I don't know if that's due to whoopsie suppression."
1689495,2017-05-13 09:39:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689495,2017-05-17 18:58:57 UTC,"Still affects me on Artful with 0.93.1ubuntu4. uklas, why did you change this to Fix Released with no explanation?"
1689495,2017-06-09 19:30:15 UTC,Robie - Do you have any more information about how this crash occurs and its effects?
1689502,2017-05-09 08:30:15 UTC,This change was made by a bot.
1689510,2017-05-10 02:16:53 UTC,"Last time I tried using the neutron client, the server did not return the 'ha' and 'distributed' fields and the CLI did not list them. This may be a regression of the openstack CLI."
1689510,2017-05-10 08:06:48 UTC,"I guess it could be a regression, or a version incompatibility? These are the versions used when I encountered this behavior:"
1689510,2017-05-12 20:18:53 UTC,"I just tried this on master, 'openstack router show $router' for user and admin showed different results for distributed and ha fields."
1689510,2017-05-12 20:50:36 UTC,Thanks for confirming Brian.
1689510,2017-09-15 20:18:16 UTC,"So this is a bug in openstacksdk and/or python-openstackclient code, by default it is showing both ""distributed"" and ""ha"" values (with defaults to False), even if they are not in the JSON body returned from neutron-server.  I don't know of an easy way to fix that by specifying not to show it in that case."
1689510,2018-05-10 15:33:08 UTC,I agreed with Brian here and I removed neutron from affected projects for now. This should be fixed on openstacksdk and openstackclient
1689510,2018-05-10 15:34:14 UTC,"Oh, and I proposed patches to fix it:
https://review.openstack.org/567606/ and https://review.openstack.org/567620"
1689510,2018-05-25 14:08:12 UTC,"sdk and OSC are now using storyboard, you should create a story at http://storyboard.openstack.org/ instead."
1689510,2018-06-18 00:49:11 UTC,This issue was fixed in the openstack/openstacksdk 0.14.0 release.
1689510,2019-03-08 04:20:27 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1689510,2019-11-07 09:11:42 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.3 release.
1689517,2017-07-10 10:19:04 UTC,I've done a dist-upgrade to Ubuntu 17.04 with kernel 4.10.0-26-generic. This kernel doesn't contain the bug.
1689517,2017-06-23 12:47:49 UTC,"4.4.0-81 still contains this bug. Anything new, I should test?"
1689517,2017-05-17 14:51:56 UTC,"I'm sorry, 4.11.0-041100-generic doesn't show the bug. I performed a clean shutdown and reboot to revalidate it, and now 4.11.0-041100-generic works as well as 4.12-rc1."
1689517,2017-05-17 14:45:36 UTC,Kernel 4.11.0-041100-generic shows another issue: DP1-1 won't show any picture and simply enters standby mode.
1689517,2017-05-17 15:08:35 UTC,"I also want to note, that the initial resolution for DP1-1 (after startx, before i run my display script), is quite random. Most of the times it's 1920x1080, which is also the initial resolution for DP1-8. But sometimes it's a smaller (less pixels) resolution."
1689517,2017-05-17 12:57:44 UTC,Now tested 4.4.0-75-generic. The bug is also in this Version.
1689517,2017-05-16 16:50:55 UTC,Thanks for the update.  It's probably best for us to perform a bisect to identify the commit that introduced this.
1689517,2017-05-16 08:52:06 UTC,I've tested the latest upstream stable kernel. (4.4.68-040468-generic). The bug persists.
1689517,2017-05-15 18:17:11 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1689517,2017-05-09 10:00:14 UTC,This change was made by a bot.
1689517,2017-05-17 14:25:10 UTC,"Can you test the v4.11 final kernel?  If it has the bug, we can ""Reverse"" bisect between 4.11 and 4.12-rc1 to find the commit that fixes this."
1689524,2020-12-29 22:17:52 UTC,Try out our Flatpak package ;)
1689537,2017-05-09 11:50:35 UTC,apport information
1689537,2017-05-09 11:50:36 UTC,apport information
1689537,2017-05-09 11:50:38 UTC,apport information
1689537,2017-05-09 11:50:40 UTC,apport information
1689537,2017-05-09 11:50:41 UTC,apport information
1689537,2017-05-09 11:50:43 UTC,apport information
1689537,2017-05-09 11:50:52 UTC,apport information
1689537,2017-05-09 11:50:46 UTC,apport information
1689537,2017-05-09 11:50:48 UTC,apport information
1689537,2017-05-09 11:50:50 UTC,apport information
1689537,2017-05-09 11:50:33 UTC,apport information
1689537,2017-10-17 09:40:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689537,2017-05-09 11:50:44 UTC,apport information
1689537,2017-05-09 11:50:32 UTC,apport information
1689537,2017-05-09 11:50:47 UTC,apport information
1689537,2017-05-09 11:49:14 UTC,apport information
1689537,2017-05-09 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1689537,2017-05-09 11:48:57 UTC,apport information
1689537,2017-05-09 11:48:59 UTC,apport information
1689537,2017-05-09 11:49:01 UTC,apport information
1689537,2017-05-09 11:49:02 UTC,apport information
1689537,2017-05-09 11:49:03 UTC,apport information
1689537,2017-05-09 11:48:58 UTC,apport information
1689537,2017-05-09 11:49:06 UTC,apport information
1689537,2017-05-09 11:49:08 UTC,apport information
1689537,2017-05-09 11:49:10 UTC,apport information
1689537,2017-05-09 11:49:11 UTC,apport information
1689537,2017-05-09 11:49:12 UTC,apport information
1689537,2017-05-09 11:49:05 UTC,apport information
1689537,2017-05-09 11:49:16 UTC,apport information
1689539,2018-01-17 07:22:03 UTC,From reading the forum it looks like the problem is fixed now (by adding 'x11') ?
1689539,2018-01-17 10:00:40 UTC,It is true that the original issue I faced was when the app didn't include the 'x11' plug.
1689539,2019-05-05 08:44:47 UTC,"Hi, Tizonia is still experiencing AppArmor denials in Window Managers like Awesome WM and Cinnamon."
1689539,2019-05-07 01:25:57 UTC,"On Sun, May 05, 2019 at 08:44:47AM -0000, Juan A Rubio wrote:

> Hi, Tizonia is still experiencing AppArmor denials in Window Managers
> like Awesome WM and Cinnamon.
>
> See https://github.com/tizonia/tizonia-openmax-il/issues/588
>
> The Snap of Tizonia works perfectly fine in Gnome 3 or Unity.
"
1689539,2019-05-09 02:53:12 UTC,"Seth, thanks for your reply."
1689542,2017-11-04 05:15:22 UTC,"/usr/bin/su-to-root can be found in menu package, but gui-apt-key does not depend on it."
1689542,2017-11-04 05:18:21 UTC,The bug is still present in Ubuntu 17.10.
1689549,2017-05-10 06:13:15 UTC,https://review.openstack.org/#/c/463648/
1689565,2017-05-27 10:14:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689570,2017-05-09 14:40:48 UTC,There's a patch I submitted to the upstream bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862182#5
1689578,2017-05-09 15:45:52 UTC,Yes there is. http://chipaca.com/post/160369439977/in-snap-tab-completion
1689578,2017-05-09 15:46:51 UTC,Added a snapcraft bug task for the 'completer' support there.
1689578,2017-05-25 19:07:42 UTC,The review tools are updated for 'completer'.
1689578,2019-04-07 07:24:34 UTC,Isn't this feature already available now?
1689578,2019-04-17 18:22:16 UTC,yes https://bugs.launchpad.net/snapcraft/+bug/1751391
1689585,2018-05-29 07:30:18 UTC,"Nothing to do on NTP here, linked up the relayed Debian bug on openntpd - thanks Simon!"
1689585,2017-11-23 22:29:03 UTC,"Thanks for the patch Christian, I relayed it in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882556"
1689585,2017-11-15 11:28:34 UTC,"How about suggesting the following to openntpd in Debian then?
Simon would you be so kind and open a bug there if that would find a consensus?"
1689585,2017-05-15 14:16:57 UTC,"""Asking someone to know about that:"
1689585,2017-05-13 11:10:37 UTC,"> Sorry, I meant it's the service's job to properly/forcefully stop a
> daemon. I agree that killing processes in postrm is dangerous.
"
1689585,2017-05-12 19:59:00 UTC,"On 2017-05-12 03:34 PM, Seth Arnold wrote:

> On Fri, May 12, 2017 at 06:56:35PM -0000, Simon Déziel wrote:
>> If purging a package doesn't kill the running process, that's a
>> packaging bug, not something Apparmor should try to paper over, IMHO.
>
> Yikes, package pre/post inst/rm scripts already do way too many things.
> Deciding what processes to kill is way too much. No thanks. :)
"
1689585,2017-05-12 18:49:22 UTC,"Christian is right and this is precisely why dh_apparmor intentionally does not unload the profile. Marking the apparmor task as Won't Fix since this has been discussed several times in the past (if apparmor upstream wants to revisit, we can open the bug)."
1689585,2017-05-12 18:56:35 UTC,"On 2017-05-12 02:15 PM, Christian Boltz wrote:

> You are technically correct that the still-loaded profile doesn't
> match a clean uninstall. However, I have a different opinion on this
> and thing keeping the profile loaded is the better choice.
>
> Unloading a profile means removing the confinement from running
> processes. So if a process is still running and (Hi Murphy!) does
> something bad after being uninstalled and becoming unconfined, you
> are screwed up.
"
1689585,2017-05-12 18:15:28 UTC,"You are technically correct that the still-loaded profile doesn't match a clean uninstall. However, I have a different opinion on this and thing keeping the profile loaded is the better choice."
1689585,2017-05-12 13:13:05 UTC,"On 2017-05-12 01:48 AM, ChristianEhrhardt wrote:

> shouldn't dh_apparmor unload it just as it loads it?
"
1689585,2017-05-12 05:52:34 UTC,"From postinst of dh_apparmor:
        # Reload the profile, including any abstraction updates
        if aa_is_enabled; then
            apparmor_parser -r -T -W ""$APP_PROFILE"" || true
        fi"
1689585,2017-05-12 05:48:57 UTC,This is the section it created on postrm:
1689585,2017-05-12 05:45:13 UTC,"Hi Simon,
thank you for your report - it indeed should unload the profile."
1689585,2017-05-12 19:34:15 UTC,"On Fri, May 12, 2017 at 06:56:35PM -0000, Simon Déziel wrote:

> If purging a package doesn't kill the running process, that's a
> packaging bug, not something Apparmor should try to paper over, IMHO.
"
1689589,2021-01-13 20:12:10 UTC,works in 20.10
1689591,2017-08-10 15:49:50 UTC,"This is probably the same issue as https://bugs.launchpad.net/moonshot/+bug/1705714, which was fixed in moonshot-gss-eap-1.0.1"
1689591,2017-05-10 12:55:02 UTC,This might be related to https://bugs.launchpad.net/moonshot-tr/+bug/1648121
1689591,2017-05-11 13:48:57 UTC,Customer reports that TR 2.1.1 binaries still exhibit the same behaviour.
1689591,2017-06-16 15:05:28 UTC,More (probably relevant) info here: https://bugs.launchpad.net/moonshot-tr/+bug/1698394
1689592,2017-06-08 17:10:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689593,2017-09-22 08:36:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689598,2017-05-09 16:56:52 UTC,"I can connect to my router, but there is no internet"
1689598,2017-05-24 18:22:12 UTC,I reinstalled ubuntu 17.04 from my hardware supplier. Internet works when on battery but if I plug in the power it stops.
1689598,2017-05-31 06:45:45 UTC,Do you have something like TLP installed?
1689605,2017-05-10 16:54:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463829"
1689616,2017-12-04 16:48:27 UTC,Thanks Breno. I'll close out the LP bug.
1689616,2017-12-04 16:29:49 UTC,"------- Comment From <email address hidden> 2017-12-04 11:28 EDT-------
Since we are not seeing update on this bug, and neither I or Carol knows where this bug should go, I am rejecting/closing it."
1689616,2017-05-10 20:13:33 UTC,"ubuntu-docs is a package for the desktop documentation, and this issue is apparently not related to that. Which set of docs is it you would like to see updated?"
1689616,2017-09-20 19:45:56 UTC,"I don't find this request very clear.  Several questions:
 - What release are you seeking to have this release noted for?  tags suggest 17.04 or 17.10 or both, but neither of these are LTS releases, so I have to question whether the tags are correct.
 - Is the lack of persistent mac addresses a problem with the kernel driver?  With the underlying hardware?
 - In what environment should we expect to see this problem?  Is it POWER-specific?
 - The workaround suggested appears to be a one-off change, that would still not persist across reboots of the system (or perhaps the state persists within the VM, but would not persist across a cold boot).  Have I understood correctly?  If so, this does not seem like a complete workaround that warrants recommending to users in the release notes.
 - Why is this being suggested as a release notes change, instead of a request for a fix in the implementation?"
1689616,2017-05-09 18:20:26 UTC,"------- Comment From <email address hidden> 2017-05-09 14:14 EDT-------
Hello Canonical,"
1689616,2017-09-25 21:00:05 UTC,"Breno,"
1689625,2017-05-24 19:51:56 UTC,"Hi there,"
1689625,2019-10-04 00:54:08 UTC,This was fixed in realmd 0.16.3-2 which is available in Ubuntu 19.04 and newer.
1689627,2017-07-26 13:57:43 UTC,That is already covered by #1701744 for linux-azure.
1689627,2017-05-15 18:12:27 UTC,I built a Xenial test kernel with your patch  The test kernel can be downloaded from:
1689627,2017-05-09 19:04:00 UTC,"Patch request, marking confirmed. Microsoft will test the results."
1689627,2017-05-15 17:38:25 UTC,"I see this patch has not landed upstream yet.   Do you also want it in Yakkety, Zesty and Artful?"
1689627,2017-05-09 19:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1689633,2017-05-13 07:01:02 UTC,"Since release 3805 the manual
- does mention the control ""% external sound heard internally""
- has an updated image about sound options."
1689648,2017-05-09 20:33:54 UTC,"it generally seems to work for just about everything other than '['
# /bin/sh -c 'for i in ""$@""; do var=""${i}abc"";
    [ ""${var#$i}"" = ""$var"" ] && echo ""$i: broken"" || echo ""$i: ok""; done' \
    a b c '[' ']' d e f 1 2 3 '#' - _ = +
b: ok
c: ok
[: broken
]: ok
d: ok
e: ok
f: ok
1: ok
2: ok
3: ok
#: ok
-: ok
_: ok
=: ok
+: ok"
1689651,2017-05-09 21:00:13 UTC,This change was made by a bot.
1689651,2017-05-10 15:57:27 UTC,Here's a partial dmesg log from a locked screen to the hang with drm:debug=0xe.
1689651,2017-05-15 17:29:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1689651,2017-05-16 19:25:47 UTC,"This was actually on Elementary OS, but I've tried with a 4.2 kernel where the problem does not exist."
1689651,2017-05-16 19:40:45 UTC,Here's a link to my report of this to Freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=100992.
1689651,2017-05-09 20:54:26 UTC,Don't know if the stack trace was actually attached:
1689653,2019-12-08 00:17:19 UTC,"Thanks for your reply, closing now."
1689653,2019-12-07 23:39:14 UTC,I haven't seen this problem for quite a while. I guess it did get fixed by accident or by intention at some point.
1689653,2019-12-07 10:51:35 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1689653,2017-06-24 02:11:26 UTC,"It still happens occasionally. The menus are still there, but invisible. I wonder if it's a race condition involving loading of fonts."
1689653,2017-07-30 23:48:16 UTC,"I guess nobody else has this bug, oddly enough, and if it ever gets fixed, it will be by accident. Attached a screenshot."
1689653,2017-05-29 06:15:40 UTC,Now the problem has gone away. Or maybe it has become intermittent.
1689653,2017-05-09 21:33:49 UTC,"I tried starting it as firefox --safe-mode mode instead. The problem still exists, although it looks a little different, presumably because the Menu Bar isn't enabled. It starts up without any space between the title bar and the tabs. Right clicking above the tab gives the pop-up menu but with Menu Bar, Bookmarks Toolbar and Customize greyed out. Selecting Menu Bar produces some space where the Menu Bar would go, but no menu bar. The option in the right-click menu then has a tick beside it."
1689653,2018-02-03 07:33:04 UTC,Still occurring in latest Ubuntu. Using Xfce4 desktop with Xfwm4 window manager. Previous reference to fvwm may be bogus.
1689667,2017-05-19 19:23:37 UTC,Patch for the tools sent.
1689667,2017-05-19 20:54:59 UTC,Utils fixed in trunk r3659 and 2.11 branch r3658.
1689667,2018-07-25 20:58:13 UTC,(removing aa-tools tag because it's fixed in the tools since a year - a kernel and/or libapparmor fix is still welcome)
1689682,2017-05-11 10:53:01 UTC,https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/29
1689682,2017-05-18 10:16:11 UTC,"Same issue for me (Windows 7). Copy/Paste from Zim failed to any text editor.
Copy/Paste to Zim works."
1689682,2017-05-23 05:28:42 UTC,"This also affects the error window. I have a different ""Looks like you found a bug"" but am going to have trouble reporting it."
1689682,2017-07-25 09:06:38 UTC,"Zim 0.67 fixed this for me (Windows 7 x64), now I am able to copy from the Zim wiki."
1689682,2017-07-31 10:59:11 UTC,"v0.67 fixes this for me, too."
1689684,2018-05-08 18:07:48 UTC,This change was made by a bot.
1689684,2021-01-07 04:18:21 UTC,4.8 EOL
1689685,2018-12-02 18:00:56 UTC,Hi Yaju. Thanks for checking. We'll need to look into it again as I suspect that we still can't change the actual SAML library and need to find a different way of dealing with this issue.
1689685,2018-11-30 22:31:46 UTC,"Hi Kristina,"
1689685,2018-02-25 04:17:24 UTC,[Expired for Mahara because there has been no activity for 60 days.]
1689685,2017-12-27 02:12:37 UTC,"Hi Yaju,"
1689685,2017-12-18 01:18:15 UTC,"Hi Kristina,"
1689685,2017-10-17 22:50:32 UTC,"Hi Yaju,"
1689685,2017-12-17 04:17:44 UTC,[Expired for Mahara because there has been no activity for 60 days.]
1689685,2017-05-18 18:19:04 UTC,@Yaju It works!  Thanks again!
1689685,2017-05-17 16:41:02 UTC,"@Yaju Yeah, we're having a similar issue on 17.04.  Mahara sends the user to our idp to login, but then the idp can't send the user back to mahara because the assertion consumer service URL (simplesaml/module.php/saml/sp/saml2-acs.php/default-sp) is not registered in the metadata."
1689685,2017-05-17 05:15:32 UTC,Looking at the code I suspect its worked for some but not others is due to
1689685,2017-05-17 03:20:27 UTC,Tagged it to 17.10 so it stays on our radar to look at since we can't verify it immediately.
1689685,2017-05-17 02:06:41 UTC,"Hi Shane,"
1689685,2017-05-16 21:36:15 UTC,@Yaju Can you share what changes you made to get it working?
1689685,2017-05-10 02:19:55 UTC,"Hi Yaju,"
1689685,2017-08-30 07:56:14 UTC,@Yaju Thank you for the workaround. I hit the problem a couple of weeks ago and I wasn't sure where the problem was. Cheers.
1689692,2017-06-05 16:18:45 UTC,"Reviewed:  https://review.openstack.org/469206
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0316f63e56d2115f79880947cea828af29af37a6
Submitter: Jenkins
Branch:    stable/ocata"
1689692,2017-09-30 16:54:19 UTC,"Reviewed:  https://review.openstack.org/505661
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=affb25ecef86537bfaebc69eb0af3b84e9cad4de
Submitter: Zuul
Branch:    master"
1689692,2017-09-25 16:14:25 UTC,"Change abandoned by Dan Smith (<email address hidden>) on branch: master
Review: https://review.openstack.org/505661
Reason: This isn't really needed now that we sort by default in the instance_list routine"
1689692,2017-06-19 12:45:54 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1689692,2017-06-08 21:51:45 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1689692,2017-06-06 14:50:32 UTC,"Reviewed:  https://review.openstack.org/469207
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3696a895321f743a824d1b89feb51eccfd07a332
Submitter: Jenkins
Branch:    stable/ocata"
1689692,2017-05-30 20:39:14 UTC,"The compute API code is wrong in stable/newton, but we don't need to fix it there because we didn't actually populate cell0 in Newton. We started creating instances in cell0 in Ocata:"
1689692,2017-05-30 18:29:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469206"
1689692,2017-05-30 18:29:41 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469207"
1689692,2017-05-26 21:00:18 UTC,Here is the problem:
1689692,2017-05-30 17:29:05 UTC,"Reviewed:  https://review.openstack.org/468549
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fe0cf0fe047f9e8890170a90c48594d90e73bda5
Submitter: Jenkins
Branch:    master"
1689692,2017-05-26 21:49:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468559"
1689692,2017-05-26 21:25:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468549"
1689692,2017-05-26 21:20:24 UTC,This goes back to newton:
1689692,2017-05-30 20:04:55 UTC,"Reviewed:  https://review.openstack.org/468559
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dbaf80d2c94db074a6651c890d532a11baec8da0
Submitter: Jenkins
Branch:    master"
1689701,2017-05-10 19:45:04 UTC,This bug was fixed in the package python-pylxd - 2.2.3-0ubuntu2
1689710,2017-07-03 20:02:39 UTC,"possibly related?
https://bugs.launchpad.net/charms/+source/keystone/+bug/1698343"
1689710,2017-07-04 08:46:27 UTC,"@afreiberger As you've already determined, the keystone issue seems to be caused by the keystone-ldap charm which is a reactive charm.  aodh is ALSO a reactive charm.  This is also happening with designate, which is ALSO a reactive charm."
1689710,2017-07-05 02:59:42 UTC,Note that https://code.launchpad.net/~billy-olsen/charm-helpers/lp1698343/+merge/326495 includes a charmhelpers fix which maybe the solution to all this - but needs a fresh release of charmhelpers since it's not included in the current one on Pypi.  Current version is 0.16.0.
1689710,2017-07-05 08:31:58 UTC,Related bug in charms.openstack (the base of the OpenStack reactive charms): https://bugs.launchpad.net/charms.openstack/+bug/1702316
1689710,2017-08-25 15:12:02 UTC,This bug is now fixed in master:
1689710,2017-08-25 15:12:45 UTC,"Changing to incomplete and lowering the priority as I believe this is now resolved due to changes in charms.openstack around ordering of things, etc."
1689739,2017-05-10 12:02:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689747,2017-05-23 11:00:51 UTC,This bug was fixed in the package neutron-taas - 1.0.1~git20170522.e15cbf3-0ubuntu1
1689747,2017-08-31 19:09:58 UTC,Just a note that in 2.0.0 (final release for Pike) the console_script was removed upstream and the package was updated accordingly.
1689747,2021-01-08 15:36:15 UTC,"I'm marking this fix-released for the cloud archive. If this still affects you, please re-open this bug and provide more information about versions."
1689748,2017-05-12 02:55:43 UTC,"We'll need to be a little careful because of potential issues with series
that we don't know about yet. When ""artful"" is out, it can be available
from cloud-images before we internally recognize it as a series, and it
would be good to not have to get a new Juju version to support it. (In the
past we depended on distro-info, but people don't update that package
regularly on their controller machines.)"
1689753,2020-05-21 13:24:36 UTC,The RAM filter has been removed in recent versions of nova so there is nothing to resolve on master now and it's unlikely to be resolved for past releases. Closed as won't fix.
1689753,2017-06-27 15:58:33 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'"
1689753,2017-05-12 10:50:56 UTC,"Seems compute node just report instance used resources and reserved resources, hugepage does not belong to one of them，so ram_filter can not filter it out，even if you actually use the memory in other ways."
1689756,2017-05-14 09:25:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689767,2019-09-05 20:46:22 UTC,"This bug was fixed in later Plasma versions. Currently, In Kubuntu 19.04, the update process is a lot smoother and requires less clicks."
1689768,2017-05-11 17:48:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689777,2018-10-30 10:52:00 UTC,"You enabled rpc-statd on the server, right?"
1689777,2017-07-25 17:34:16 UTC,Came across this on Ubuntu 16.04 diskless client.  Fixed by enabling rpc-statd.service
1689777,2017-07-18 18:20:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689777,2017-05-12 09:28:46 UTC,Added APT history of updated packages
1689777,2017-05-11 21:23:01 UTC,Moved to nfs-kernel-server
1689777,2017-05-11 20:15:00 UTC,"Booting on old Kernel does not relove issue, not Kernel related so far."
1689777,2017-05-10 10:18:55 UTC,Attached log includes the existing problem at rotation time. Then a reboot was issued.
1689777,2017-05-10 10:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1689777,2017-05-11 21:24:48 UTC,"Following output in syslog, if rpc debug level is increased by
""echo ""65535"" > /proc/sys/sunrpc/nlm_debug"":"
1689780,2017-12-10 23:21:04 UTC,Can you check if you still have the semi-colon at the end of the line ?
1689785,2017-12-06 12:18:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689785,2017-12-06 12:18:24 UTC,"That would be a good feature to add, I'd like to see this support as well."
1689785,2017-12-07 10:03:07 UTC,The request has been made upstream on https://bugzilla.gnome.org/show_bug.cgi?id=747802 but there has be no activity there since it was reported
1689787,2017-05-15 17:28:01 UTC,Is this bug only happening with 4.8 based kernels?  Does the bug happen with Zesty?
1689787,2017-05-10 10:30:13 UTC,This change was made by a bot.
1689796,2017-05-10 13:20:09 UTC,It would be awesome if this could land in both 14.04 and 16.04
1689796,2017-06-01 08:11:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689807,2017-05-10 23:55:03 UTC,*** This is an automated message ***
1689808,2017-05-10 12:55:04 UTC,"Also we are getting another error, which is logged in the file
http://paste.openstack.org/show/609274/"
1689823,2017-08-02 19:04:43 UTC,"Dougal is there an example of the command which was run, in regards to the TripleO instance?"
1689825,2017-10-11 12:00:35 UTC,"Chrome/Chromium should probably not wait that long if keyring is not available. If it is not running, then it is not running, end of story. Chromium should just proceed launching instead of bothering user with behavior like this."
1689825,2017-08-24 03:43:59 UTC,"1. apt-get install dbus-user-session
2. reboot
3. confirm flatpak not installed:
emc@emc-office:~$ which flatpak"
1689825,2017-08-24 03:31:24 UTC,"Jeremy,"
1689825,2017-08-24 02:42:49 UTC,"$ apt rdepends dbus-user-session
dbus-user-session
Reverse Depends:
 |Suggests: dbus
  Depends: anbox-common
 |Suggests: dbus
 |Suggests: dbus"
1689825,2017-08-24 02:21:43 UTC,"Mike, what is the output of this command:"
1689825,2017-08-24 02:19:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689825,2017-08-24 01:45:06 UTC,This bug was not only related to Flatpak. I have never installed/used/heard of Flapak before I filed this bug. Maybe this bug should be filed against dbus-user-session.
1689825,2017-08-24 01:32:19 UTC,"Rocko, please file a different bug for that issue."
1689825,2017-10-18 18:10:23 UTC,After trying multiple options in this thread. I found that reinstalling the ca-certificates fixed this for me.
1689825,2017-08-24 01:12:55 UTC,"I also have this issue in Ubuntu 17.10 (running gdm/gnome-shell). Uninstalling dbus-user-session isn't really an option, because tons of apps depend on it."
1689825,2017-08-23 03:44:10 UTC,"Uninstalling polychromatic, razer-daemon, and then dbus-user-session resolved the chrome problem."
1689825,2017-08-23 02:39:37 UTC,"It turns out the workaround does resolve the long pause, but does not result in correct operation. Chrome has chrome sync not functioning, and gnome-encfs mounts fail unless manually mounted using gnome-encfs-manager"
1689825,2017-08-22 02:52:40 UTC,"I can replicate this problem on 16.04.3 after upgrade from 16.04.2. However, the package dragging in dbus-user-session are different in my case:"
1689825,2017-08-21 09:55:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689825,2017-08-14 15:15:50 UTC,"Since there are multiple packages that depend on dbus-user-session, there's really no need to mention a single package in the title."
1689825,2017-08-12 12:06:00 UTC,This is not fixed. What we have is a reliable workaround to a bug which apparently affects all Ubuntu 16.04 LTS users with the dbus-user-session package installed.
1689825,2017-08-24 01:34:32 UTC,"Eric, please contact the distributor/maintainer for razer-daemon and polychromatic since those packages are not provided by Ubuntu."
1689825,2017-10-25 02:36:55 UTC,Reinstalling the ca-certificates did not work for me.
1689825,2017-12-02 08:14:51 UTC,"Any update on this issue? I do not feel comfortable removing dbus-user-session as a workaround, and I have simply added --password-store=basic as an argument for Chromium/Chrome for now. However that is not completely suitable even though I only use Chromium/Chrome as a secondary browser, and I am wondering if this issue is still being looked into, and am inquiring for perhaps more details about it if anyone has any more details like if the maintainers/developers of dbus-user-session (whoever they may be?) are aware of this bug, etc.  I am using Ubuntu 16.04 and Xfce 4.12 and the latest google-chrome-stable, chromium-browser, dbus-user-session, etc. I see someone has stated back in August that using Ubuntu 17.10 with Gnome shell and gdm still produces this issue, I wonder if this is still the case or if this issue has been fixed by now at least on Ubuntu 17.10?"
1689825,2017-08-07 19:09:55 UTC,I can't believe all it took was to do:
1689825,2019-08-23 11:37:44 UTC,This also happens in disco dingo (19.04). Only solution is running `gnome-keyring-daemon` on a terminal.
1689825,2019-06-05 09:21:00 UTC,"As with comment #107, `sudo apt-get install --reinstall ca-certificates` was the only fix for me. Removing/re-installing/re-configuring dbus-user-session didn't help. This points to there being two issues. Neither issue is related to chrome."
1689825,2019-04-17 10:53:37 UTC,"Hi guys,
This bug is still present on latest versions (seahorse 3.30).
Why is assigned to chromium-browser package?"
1689825,2019-02-10 11:02:56 UTC,"Could this be an incompatibility between i386 and amd64 packages?  I have trouble adding my keys via ssh-add and after reading some comments here and elsewhere gave removing dbus-user-session a try.  My computer is amd64 with i386 foreign arch.  dbus-user-session was replaced with dbus-user-session:i386 and a few other :386 packages.  After the installation, the situation was much worse, with ssh-add completely hanging now."
1689825,2018-07-17 16:13:12 UTC,Ran into this after installing dbus-user-session in order to support systemd user services that raise notifiers via dbus.
1689825,2018-04-25 13:22:33 UTC,"Billy, please file a new bug for your issue with specific details about what you're experiencing."
1689825,2018-04-25 11:36:54 UTC,I still experience this bug in 18.04.
1689825,2017-10-25 02:39:33 UTC,"Also, openrazer & polychromatic no longer have the dependency on dbus-user-session. Thanks to the maintainers of these packages."
1689825,2018-03-14 15:30:02 UTC,"Every time I turn around, I have a no failure related to gnome-keyring.  After having Chromium running for a few minutes it hangs again for a minute or so with the same error message:"
1689825,2018-03-14 14:53:04 UTC,"Running ""chromium-browser --enable-logging=stderr"" results in:"
1689825,2018-03-12 17:39:23 UTC,"Thanks for the feedback Stephen. This thread has become very long and it's hard to extract the relevant information, so just to make sure that I fully understand the issue:"
1689825,2018-03-12 15:34:52 UTC," - I'm seeing slow downs.
 - I'm not using automatic login."
1689825,2018-03-12 15:05:40 UTC,"> This bug is not resolved. Seeing it under 16.04LTS without
> dbus-user-session or flatpak installed.
"
1689825,2018-03-12 14:59:38 UTC,"> I do not feel comfortable removing dbus-user-session as a workaround
"
1689825,2018-03-12 14:46:06 UTC,"> Also, on a side-note, does anyone know the exact details of what the
> password-store argument does? For example, if I turn password saving
> in Chromium off and don't use Google/Chrome sync, am I ""safe"" to log
> into websites without my passwords being stored in plain-text on my
> hard drive (even if temporary)?
"
1689825,2018-03-09 16:24:56 UTC,This bug is not resolved.  Seeing it under 16.04LTS without dbus-user-session or flatpak installed.
1689825,2018-03-14 15:25:47 UTC,"After killing and restarting the keyring which fixed Network Manager, then Chromium developed a slow start problem caused by gnome-keyring."
1689825,2017-08-04 11:23:24 UTC,I can confirm as well that removing dbus-user-session and reboot worked like a charm. Thx all.
1689825,2018-03-12 17:55:00 UTC,"Olivier:
1) Yes
2) Yes
3) Yes
4) I'll have to log out and/or reboot to get it back into that state.  Will post when I get a chance to do that."
1689825,2017-06-27 17:45:19 UTC,For reference... https://github.com/karma-runner/karma-chrome-launcher/issues/76
1689825,2017-05-27 09:17:03 UTC,Opera is also affected by this issue. Takes almost a minute to load whereas Firefox loads in under five seconds.
1689825,2017-05-26 21:47:58 UTC,I use KeePass 2 on Mono so I'm not too bothered by this. Wifi and NetworkManager still have problems though.
1689825,2017-05-26 10:10:36 UTC,I was wondering if there is anything I can to help regress the issue? Even if it is just trying to load various different older versions?
1689825,2017-05-26 00:48:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689825,2017-05-25 04:39:51 UTC,I've recently started getting this issue too. What is going on?? Ubuntu shouldn't be doing this on the LTS.
1689825,2017-05-22 15:23:05 UTC,"Well, I mean workaround by ""fix"" word. This workaround is the shortest, cleanest and working think I've seen about this bug."
1689825,2017-05-22 14:20:36 UTC,"That is not a fix. It is a workaround. On boot, my system has gnome-keyring-daemon running which needs to be killed and restarted without --login in order to function. This was working a couple weeks ago. There should be no ""fixes"" the user need to do to regain this functionality."
1689825,2017-05-22 14:10:29 UTC,This askUbuntu answer actually fixed the issue cleanly https://askubuntu.com/a/911755/61218. The solution is adding a startup item with this commandline
1689825,2017-05-22 12:17:03 UTC,"vinagre is also affected, running gnome-keyring-daemon restores the normal behavior."
1689825,2017-05-17 07:53:11 UTC,"This causes problems in other applications, too. I get constant requests from Evolution to enter my credentials (although they are stored in the keyring). The Nextcloud client asks for a(n actually stored) password as well."
1689825,2017-05-14 19:30:37 UTC,I'm also seeing slow response to taking a screenshot with shortcut keys.
1689825,2017-05-13 18:28:33 UTC,"I'm also seeing slow startup in chrome/chromium, and gnome-terminal using keyboard shortcut."
1689825,2017-05-11 14:27:23 UTC,"Here is another link with more users experiencing the same bug, while also noting that the CTRL-t shortcut to open terminal can take up to 2 minutes to start a new terminal session, which I am experiencing as well."
1689825,2017-05-10 15:31:26 UTC,I'm not positive when an update was pushed out that caused this - my machine gets updates automatically every night but I rarely reboot.  I rebooted yesterday and was immediately affected by it.
1689825,2017-05-10 15:30:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689825,2017-05-10 14:08:55 UTC,Links to other users with the same or similar issue within the past 2 days:
1689825,2017-08-03 14:53:46 UTC,"again, confirming: `sudo apt-get remove --purge dbus-user-session` and reboot resolved it for me on Ubuntu 16.04. No side-effects. On reboot, the Passwords>Login keyring was available, where before it wasn't."
1689825,2017-05-27 10:36:03 UTC,"I have this problem too. With mysql-workbench, connecting to remote servers from file manager and  other programs. The workaround from some upper posts restores functionality."
1689825,2017-05-28 11:15:30 UTC,"same for me here
by starting with the terminal"
1689825,2017-05-25 11:33:40 UTC,"Sorry, I should have been more constructive with my comment. The workaround in #10 seems to partially work. It doesn't allow the ""login"" password keychain to be unlocked on login, but it at least let you see the passwords in seahorse so that it can be unlocked manually - which in turn prevents applications from hanging."
1689825,2017-06-04 15:34:47 UTC,I am having this problem as well to the point that I can't use my desktop.  The only solution I have found is to install a different distro or version of Ubuntu other than 16.04.
1689825,2017-06-27 10:13:43 UTC,This is affecting basic NetworkManager use cases. It's impossible to connect to any password protected wifi. I'd bet this bug is the cause of many other requiring access to the keyring storage.
1689825,2017-06-26 19:51:19 UTC,"The following seems to have got me running normally again.  Working on the theory the keyring file was somehow corrupted, I deleted the keyring file...
rm ~/.local/share/keyrings/login.keyring
...and rebooted.  A new keyring file has been generated and everything looks good for now!"
1689825,2017-05-30 15:18:39 UTC,Same problem here:
1689825,2017-06-22 01:05:23 UTC,Maybe a clearer capture of something amiss... logging in and out and in repeatedly causes the keyring daemon process to be started again and again (as lightdm and as the user).  Please see attached.
1689825,2017-06-21 23:03:08 UTC,I uncovered another problematic side effect but I am unsure of the significance; perhaps this will trigger an idea for someone....
1689825,2017-06-21 20:29:50 UTC,"The only ""permanent"" (well, it still asks for the password once when opening google-chrome after login) workaround I found was creating a startup item as described here: https://askubuntu.com/a/911896."
1689825,2017-06-21 19:38:38 UTC,"I am experiencing the same issue on one of my two machines.  The 'Password and Keys' padlock icon next to 'Login' remains locked even with the correct password, and I'm unable to use Chrome, access e-mail etc..
I'm no expert but, in case it helps, these are two differences between the two machines I'm aware of...
- the machine with the problem has an encrypted installation and the other not. Otherwise both installations are similar (basic 16.04 and not much else)
- if I enter ""ps aux | grep keyring"" I get two 'gnome-keyring-daemon' processes listed on the problem machine (one for user 'lightdm' and one for myself), and only one on the machine without the problem (user is myself)
The machine with the problem is almost useless for the moment - would be great to get a solution."
1689825,2017-06-19 15:31:29 UTC,"Although chromium-browser is affected by the issue, it doesn't appear to be the cause of the issue itself (other apps like gnome-terminal appear to be similarly affected), so I'm marking this bug invalid for chromium-browser."
1689825,2017-06-18 22:16:22 UTC,"I've installed the flatpak (and added the PPA) quite recently, but uninstalling the package didn't solve the issue for me."
1689825,2017-06-23 20:42:34 UTC,"On my machine I'm unable to get any of the above workarounds to unlock the keyring.  Entering...
gnome-keyring-daemon --replace --foreground --components=secrets,ssh,pcks11
...ends in the terminal hanging at ""SSH_AUTH_SOCK=/run/user/1000/keyring/ssh""."
1689825,2017-06-18 11:11:35 UTC,"I also had the flatpak PPA, I removed it but the situation didn't improve, I also reinstalled the gnome-keyring package with no luck."
1689825,2017-06-17 22:26:11 UTC,"I agree with comments #25 and #26.  It's likely a red herring, but this issue arose for me right after I installed the flatpak PPA and a pile of mono/M$ stuff.  I still figure that those actions are orthogonal, but just in case everyone else recently installed similar stuff or a new PPA or..."
1689825,2017-06-17 09:08:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689825,2017-06-07 21:45:06 UTC,"Well, this bug also is affecting me, I used the workaround in #10 and it works, but I still need to put my password in order to unlock the ""Login"" Keyring (My system don't have autologin enabled btw), the weird thing is that this system is fresh installed (no more than a week) and It was working fine until today. Maybe there is some package that I installed yesterday that is affecting the system.
Google-chrome affected
Online accounts also is affected
I didn't test other apps, but as far I could check those apps were affected by this issue
Greetings"
1689825,2017-06-17 06:41:53 UTC,Hans' observation that this is not impacting all of his machines is consistent with my experience of this issue. I have three Ubuntu machines and this is only impacting one of them. It is driving me nuts because the machine that is impacted is my main laptop. My server and my test machine which would be less of an issue to me as they don't get booted so often are working fine. A classic example of Murphy's Law.
1689825,2017-06-17 00:07:27 UTC,What is odd is that it does not occur on all Ubuntu installations.  I have a 2nd Ubuntu machine that does not suffer from this issue.  What could possibly be different between a computer that exhibit this problem and another?  I do not recall having played with any configuration file that relates to this issue.
1689825,2017-06-16 22:23:44 UTC,This also affects chromium-browser installed from Ubuntu repository.
1689825,2017-06-18 13:39:07 UTC,This has manifested itself on a machine with a fresh install of 16.04.2 with nothing installed but google chrome. I have 2 other machines with this issue and neither have ever had the flatpak PPA enabled or anything installed from it.
1689826,2019-01-22 13:48:33 UTC,Is this still an issue?
1689826,2019-12-18 08:32:26 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1689829,2018-02-23 14:53:17 UTC,"Hi Dimitri,
hard to say, but this is taken into account :
https://github.com/open-power/petitboot/issues/15"
1689829,2017-05-12 12:25:45 UTC,"The attachment ""partman-auto-fix-baremetal-ppc64el.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1689829,2017-05-12 09:43:52 UTC,"Could you review this rollback patch ?
Thanks"
1689829,2018-02-23 14:24:10 UTC,I am sad =(
1689830,2017-07-28 09:10:43 UTC,@Kevin
1689830,2017-07-27 22:57:47 UTC,"@Denes,"
1689830,2017-07-25 21:32:09 UTC,"@Armando, they won't need to disable the current one because regular tenants already cannot set allowed address pairs on ports on shared networks."
1689830,2017-07-18 18:18:05 UTC,"If you are unable to use any type of routing capability (hardware or software) to provide internetworking between applications, then a shared medium sounds like it is your only option. I think your use case is clear now, thanks for providing these extra details."
1689830,2017-07-18 08:59:50 UTC,"An each application is deployed on a separate tenant. Each application has it's own tenant network (non-shared) for internal communication. The applications communicate with each other using ports on shared network, because in this case no router (internal/external) is required to be deployed between them. The router is not an option because it does not provide the required performance."
1689830,2017-07-17 20:56:06 UTC,"Now that we have the submitter's reply, let's mark this report triaged so that we can discuss it once more time during a future drivers meeting."
1689830,2017-07-17 20:59:53 UTC,"@Kevin: furthermore, the consumer of this new attribute need explicitly disable the 'untrusted' allowed address pair capability."
1689830,2017-07-17 20:51:38 UTC,"The use case here seems clear, allowing shared IPs within a tenant on provider networks."
1689830,2017-07-13 23:08:03 UTC,"We talked about this request during today's meeting, however it's not clear the exact use case. Could you walk us through the steps involved to set up this HA port pair? Is the tenant executing this steps a 'service' like a PaaS on top of OpenStack? Why wouldn't that own the network?"
1689830,2017-07-14 06:02:06 UTC,The use cases are the following:
1689830,2017-05-25 20:52:28 UTC,You mean you want to limit the user to be able to add IP/MAC pairs only if they match MAC/IPs assigned to existing neutron ports that he/she owns?
1689830,2017-05-25 20:57:49 UTC,"@Armax, yeah, I interpreted it the same way."
1689830,2017-05-25 20:58:34 UTC,"Basically you want to be able to run HA services on a provider network, is that right?"
1689830,2017-07-17 20:23:09 UTC,"The key element to the use case is that this happens on a shared network, but that needn't be. Why can't each vendor (tenant) have its own network?"
1689830,2017-05-26 08:25:48 UTC,"Sorry for the late response, but probably we are in different time zones."
1689830,2017-07-13 23:08:24 UTC,Marking incomplete until more details are provided.
1689830,2017-05-25 21:13:25 UTC,Moving to triaged because we have enough to discuss with it already while waiting for the response.
1689833,2019-09-19 15:13:39 UTC,Note: the if the solution needs an ifupdown hook like shown in comment #12 in >=Bionic I'd ask you to take a look for networkd-dispatch (the final solution for almost all of these bugs is that the upstream project starts to listen o netlink to pick up late ready IP addresses)
1689833,2019-03-18 11:03:29 UTC,Do you have a pointer to the upstream discussion?
1689833,2019-03-17 14:39:04 UTC,"Seems upstream kindly solved this bug, the solution is to:"
1689833,2019-03-17 14:00:56 UTC,"Also affected by this bug, fresh Ubuntu Ubuntu 16.04.6 LTS minimal server install + openvpn"
1689833,2018-10-09 09:04:07 UTC,It's the normal builtin NIC on a headless server. Tried with different hardware as well:
1689833,2018-10-08 15:08:05 UTC,"@jnx, the 192.168.11.254 address you are trying to bind to, is that the normal nic of that machine? Or something else, like a wifi interface, or something that would only come up after the user logs in, assuming this is a desktop?"
1689833,2017-11-20 20:34:34 UTC,https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ is a good read about this
1689833,2017-11-20 20:10:51 UTC,"In fact, our current openvpn package in bionic is using just these After and Wants values:
After=network-online.target
Wants=network-online.target"
1689833,2017-11-20 19:41:34 UTC,Found these other bugs which look related:
1689833,2017-11-20 19:35:29 UTC,"A possible workaround would be to add ""Restart=on-failure"" in the ""[Service]"" section of the systemd unit."
1689833,2017-11-20 19:19:30 UTC,"I finally got to confirm this. I had to install ntp to see the same problem in my vm. Before that, openvpn was always running after a reboot."
1689833,2017-05-23 22:39:44 UTC,"Thank you for reporting this bug. I will add it to the server team backlog, as it does appear to be a real issue."
1689833,2018-04-10 10:03:46 UTC,"I tried your suggested settings on fresh installs including all updates but this still regularly fails to bind the address. I have those servers running as virtual machines with Qemu/KVM.
If I do the same thing on bare metal, the binding will succeed in like 95% of boots."
1689833,2017-11-20 20:01:33 UTC,"> My guess is that systemd starts OpenVPN too early before the network is brought
> up sufficiently. Running 'sudo systemctl edit --full openvpn' and adding
> 'Wants=network-online.target' does not change that behaviour.
"
1689836,2018-01-12 19:04:16 UTC,Unassigning due to no activity for > 6 months.
1689842,2017-05-10 15:16:19 UTC,"To be slightly more specific, step by step:
- the launcher was named 'new launcher'
- I've search for 'new' in the top search field in menulibre
- launcher appeared on the list and I've selected it
- I clicked 'Delete' button
- launcher was still visible on the list, so I clicked 'Delete' button once again
- warning appeared that launcher cannot be deleted
- I closed menulibre window and relaunch it
- I searched for 'new', launcher did not appear on the list (it was deleted)
- I closed menulibre, seconds later the bug report window appeared"
1689842,2017-05-10 17:12:05 UTC,This bug has been reported on the Ubuntu Package testing tracker.
1689843,2017-05-10 15:34:53 UTC,"Thanks to this reply.
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1628053/comments/11"
1689855,2017-05-10 16:35:10 UTC,Initial upstream workaround submission: https://patchwork.kernel.org/patch/9601819/
1689869,2017-05-10 17:05:17 UTC,assigned to me
1689880,2017-05-16 07:51:53 UTC,"Hi Thiago,"
1689880,2017-05-18 07:31:47 UTC,I tested with the master using devstack and I couldn't reproduce the issue. I deleted the OVN NB db and restarted the neutron-server with sync mode set to repair. The OVN DB is recreated successfully.
1689880,2017-10-05 02:36:37 UTC,"I just ran into this issue on a brand new ocata deployment made from scratch, followed official documentation. It is a bare min deployment for proof of concept."
1689880,2017-10-06 05:29:12 UTC,Forgot to mention this was centos 7 dist
1689880,2019-01-10 04:58:36 UTC,I was recently encountering many errors while logging in to the gmail from my laptop. I was literally searching for the fix and then I got help from https://gmailtechnicalsupportnumbers.com/fix-gmail-error-codes-messages/ where it is clearly said about the fix.
1689880,2020-01-21 10:23:44 UTC,The OVN driver now lives in the neutron repository. Moving this bug to their tracker.
1689888,2017-05-14 19:56:14 UTC,"Hi Sam,"
1689888,2017-07-18 22:06:47 UTC,"I was able to recreate this locally, but I'm still tinkering with some caching settings so I can provide benchmarks with and without caching."
1689888,2017-07-19 14:30:07 UTC,"Ok - after doing some additional research I've confirmed the issue. I setup keystone locally and installed master (239bc3627cfb0546148e9d496f9e1536057052a7). I used a script to generate a bunch of data [0]. I ended up putting 10,000 project and 15,000 users in the system. Granted, I'm doing everything on my laptop (keystone + running with uwsgi, mysql, client, etc). My numbers won't be good representations of a real deployment, but I was able to notice a delta in the two APIs with respect to response time."
1689888,2018-03-16 18:54:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/553880"
1689888,2018-07-02 18:20:54 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.openstack.org/553880
Reason: Gonna split this up"
1689890,2017-05-17 20:44:07 UTC,"This is going to take some work.
The cloud-images built to run on IBM Bluemix are *very* odd.
To my understanding, they actually have data in /var/lib/cloud/nocloud and then sometimes also have a config drive attached.  I'm not sure if the config drive has a valid label or not (config-v2)."
1689890,2017-05-17 21:06:15 UTC,"I've just confirmed this, launched a vm in bluemix/softlayer and ssh'd in."
1689890,2017-05-17 21:10:11 UTC,"After seeing the warning, I did:
$ sudo umount /var/lib/cloud/seed/config_drive
$ sudo rm -Rf /var/lib/cloud/seed/config_drive/ /var/lib/cloud/{data,handlers,instance,instances,scripts,sem}"
1689890,2017-05-31 16:03:21 UTC,"Daniel grabbed some more info from a node that i had neglected.
not necessarily helpful, but
$ sudo sh -c 'cd /sys/hypervisor && grep -r . *'
compilation/compiled_by:mockbuild
compilation/compile_date:Mon Apr 24 15:29:46 UTC 2017
compilation/compiler:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
properties/pagesize:1000
properties/changeset:86f912c86501, pq 5f429748345d
properties/virtual_start:ffff800000000000
properties/features:000020f0
properties/capabilities:xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
type:xen
uuid:367fb048-191c-7ca9-1f86-79ee7f227a5e
version/extra:.1-1.3
version/major:4
version/minor:7"
1689890,2017-05-31 16:05:04 UTC,"And some more of my thoughts in
 https://bugs.launchpad.net/cloud-init/+bug/1673637/comments/4"
1689892,2018-12-03 13:31:30 UTC,Reported upstream as well on https://gitlab.gnome.org/GNOME/gnome-calendar/issues/298
1689899,2017-07-31 23:58:49 UTC,Might be related to bug #1658029.
1689901,2020-10-01 09:49:31 UTC,Thank you!!
1689901,2020-12-07 18:27:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1689934,2017-05-30 19:35:51 UTC,now better:
1689934,2017-05-10 21:20:00 UTC,the chronology of song.authors may be still a problem... or switch the json separator...
1689934,2017-05-11 20:08:31 UTC,a little bit better...
1689959,2017-08-17 16:56:18 UTC,This is similar to: https://bugs.launchpad.net/maas/+bug/1711411
1689959,2019-12-12 13:27:57 UTC,"This is the expected behavior, since the snap is now confined and thus independent from the host OS."
1689969,2017-05-11 02:16:11 UTC,"Hi @Yashaswini,
I downloaded the ISO image from http://people.canonical.com/~platform/snappy/tuchuck/desktop-final/tuchuck-xenial-desktop-iso-20170317-0.iso, and created a installation media. The boot process ran normally and did not show any error. Could you please provide your procedures used to create the disk, serial console log and screenshot? Then we can do further investigation."
1689969,2017-06-12 12:14:06 UTC,I bumped into the same issue this morning. i.e. when boot the Joule from bootable USB. It just get in to an infinite loop error message “error: no such device: /.disk/casper-uuid.”
1689978,2017-06-02 20:14:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690004,2017-11-03 04:02:11 UTC,"This happens in JAAS on 2.2.3, and is more than a usability/papercut issue due to the log volume: https://pastebin.canonical.com/202296/"
1690004,2017-06-15 05:53:22 UTC,"To add to this : as a Juju administrator/operator, it'd be great to have a command displaying some commonly occurring errors such as : bad cloud credentials (such as above), or, for example, the ""No default VPC for this user (VPCIdNotSpecified)"" error."
1690004,2017-06-15 06:18:09 UTC,"What do you mean by ""command displaying the errors""? As in a ""juju help
common-errors"" listing things you might expect? Or are you saying ""juju
whats-wrong"" that interprets the last errors and translates them? Or ""juju
bootstrap"" when it encounters a common error would give better indication
from it?"
1690004,2017-06-15 08:48:29 UTC,"Something like :
$ juju show-errors (<= name to be, huh, refined)
user1/creds1     bad credentials for cloud $cloud
user2/model2     no default VPC"
1690004,2017-06-20 22:23:06 UTC,"For the OpenStack piece, See also: https://bugs.launchpad.net/juju/+bug/1688337"
1690013,2017-10-27 03:27:16 UTC,See also bug 1727914
1690051,2018-11-15 01:43:48 UTC,Looks like the crash stopped happening in PulseAudio 12. Can you please try Ubuntu 18.10?
1690051,2018-11-15 02:22:04 UTC,"I was really hoping to keep this machine on LTS, is the fix not going to be backported?"
1690051,2018-11-15 02:35:07 UTC,There is no known fix to backport. I am just trying to confirm if it really has stopped happening in version 12.
1690051,2019-07-28 21:26:45 UTC,"I am still getting the crash, but the location of it has changed.  Now it dies at
    txt = avahi_string_list_add_pair(txt, ""device"", s->name);"
1690051,2019-07-29 01:40:30 UTC,"Owen, that sounds like bug 1679744."
1690051,2019-07-29 13:22:31 UTC,"so it is, thanks!  So I think we can say this original bug is obsolete / already fixed"
1690051,2018-11-15 01:08:46 UTC,"From my own debugging, the crash appears to be in this line:"
1690085,2020-06-01 19:55:08 UTC,I’ve tried that option of “Typical current idle” to no avail.
1690085,2020-06-01 18:59:44 UTC,"(In reply to Paul Menzel from comment #683)

> (In reply to Ashesh Ambasta from comment #680)
> > I've been facing the same issue since I've bought this machine and setting
> > my BIOS power settings to ""Typical current idle"" has only partially fixed
> > things (the system still crashes every 1-2 weeks during idle: I leave my
> > desk, screensaver fires up, then screens go to sleep, and by the time I get
> > back to my desk, the system no longer responds to any input and the only
> > option is a hard reset.).
> >
> > At the time of writing, I can't tell if the AGESA version has made it into
> > my motherboard: https://www.asrock.com/mb/AMD/X399M%20Taichi/index.asp#BIOS
>
> [I have an MSI board, but checked the firmware update files for you.]
>
> The description for version 3.60 includes:
>
> > Update AMD AGESA ThreadRipperPI-SP3r2 1.1.0.2
>
> Reading the ASRock forum thread *What happened to Fatality X399 Bios 1.60?*
> [1], it’s enough to run the firmware update file through a hexeditor. I
> searched for *GES* and was lucky for version 3.80.
>
>     $ hexdump -C X399MT3.80 | less
>     […]
>     00e34ce0  00 00 00 00 00 00 00 00  00 00 00 00 be 2c 63 17
> |.............,c.|
>     00e34cf0  80 6c b6 49 82 07 12 b5  3d 9b 25 70 41 47 45 53
> |.l.I....=.%pAGES|
>     00e34d00  41 21 56 39 00 54 68 72  65 61 64 52 69 70 70 65
> |A!V9.ThreadRippe|
>     00e34d10  72 50 49 2d 53 50 33 72  32 2d 31 2e 31 2e 30 2e
> |rPI-SP3r2-1.1.0.|
>     00e34d20  32 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> |2...............|
> […]
> ```
>
> So, it still has AGESA version 1.1.0.2.
>
> […]
>
>
> [1]:
> http://forum.asrock.com/forum_posts.asp?TID=6165&PN=4&title=what-happened-to-
> fatality-x399-bios-160
"
1690085,2020-06-01 18:51:06 UTC,"Several experiments with Ryzen 1700 and Gigabyte X370 Gaming K7 Board. Best choice was ""typical current idle"", but the latest Bios did'nt have that option. So I bought a R5 3600 put the latest BIOS at the board and all the problems gone away. Rock solid now. I think, that the first generation of Ryzen make some problems with Linux - mine was a RMA'ed because of the compiler error. See Comment 195.
Meanwhile gcc-9.3.0, Kernel-5.7.0, Bios F50a"
1690085,2020-06-01 16:15:40 UTC,"I see. But that is assuming that the 1.0.0.4 version “fixes” this issue. At this point it’s only a guess but it seems likely given the previous replies I’ve seen.
My god what a nightmare this has been. :-)"
1690085,2020-06-01 15:59:23 UTC,"(In reply to Ashesh Ambasta from comment #680)

> I've been facing the same issue since I've bought this machine and setting
> my BIOS power settings to ""Typical current idle"" has only partially fixed
> things (the system still crashes every 1-2 weeks during idle: I leave my
> desk, screensaver fires up, then screens go to sleep, and by the time I get
> back to my desk, the system no longer responds to any input and the only
> option is a hard reset.).
>
> At the time of writing, I can't tell if the AGESA version has made it into
> my motherboard: https://www.asrock.com/mb/AMD/X399M%20Taichi/index.asp#BIOS
"
1690085,2017-10-22 11:50:11 UTC,"I can confirm the issue with a week 33 Ryzen 1700 on Asus Prime B350 Plus.
I had segfaults with my previous 1700 (week 22 iirc). No more segfaults with the week 33 CPU but still random crashes on (long time) idle."
1690085,2020-06-01 10:46:10 UTC,"(In reply to Ashesh Ambasta from comment #680)

> I've been facing the same issue since I've bought this machine and setting
> my BIOS power settings to ""Typical current idle"" has only partially fixed
> things (the system still crashes every 1-2 weeks during idle: I leave my
> desk, screensaver fires up, then screens go to sleep, and by the time I get
> back to my desk, the system no longer responds to any input and the only
> option is a hard reset.).
>
> At the time of writing, I can't tell if the AGESA version has made it into
> my motherboard: https://www.asrock.com/mb/AMD/X399M%20Taichi/index.asp#BIOS
>
> But I'd be willing to give this a try. I also just yesterday requested an
> RMA from AMD though: I spoke to their support and they asked me to try
> setting the power settings in the BIOS settings. Once I reported back that
> the power settings only reduced the frequency of these crashes, their
> immediate response was to open an RMA request. It seemed like they were
> aware of the issue and they seemed quite confident that an RMA will fix this
> (I sure hope so since the RMA means at least 2 weeks of downtime for me).
"
1690085,2020-06-07 14:09:12 UTC,"I've also found https://www.reddit.com/r/Amd/comments/8yzvxz/ryzen_c6_state_sleep_power_supply_common_current/e33lc6s/ which seems to be promising. It is, however, appalling to see this kind of response from AMD and I'm quite sure this is my last AMD system."
1690085,2017-10-22 06:57:39 UTC,Ryzen CPUs manufactured before week 24 of this year were known to have issues (especially the segfault issue). It was officially fixed for all ryzen manufactured after week 30. All my ryzen are pre-24 CPUs and they all have this silent crash issue. Does it also happen with the post week 30 ryzen ? (@tgui what is yours ?)
1690085,2017-10-21 17:53:18 UTC,I too still have random computer shutdowns without logs. Uptime varies from a couple days to a week or so. It happens it seems after being relatively idle for a long period. I do have high memory usage because of the VMs I run.
1690085,2017-10-18 06:25:15 UTC,"Hi,
I'm getting the same issues on several identical builds, with an ASUS prime X370-PRO motherboard.
It's very hard to analyze since it happens randomly every other week, and it leaves no logs. It seems that the freeze happens at idle after very high memory load (observation after logging CPU and RAM loads).
Compiling the kernel as suggested in this thread didn't work (new freeze this morning)."
1690085,2017-10-06 08:14:06 UTC,"Stuart,"
1690085,2020-06-01 11:15:25 UTC,"Created attachment 289445
attachment-1715-0.html"
1690085,2020-06-11 16:03:14 UTC,"(In reply to raulvior.bcn from comment #653)

> (In reply to txrx from comment #651)
>
> Typical Current Idle might not be working. Read the sensor output. If
> voltage is not higher than without enabling it, try to increase the core
> voltage.
>
> My Ryzen 7 1800X seems to not produce hangs since I upgraded to 1003ABB with
> an ASUS Crosshair VI Hero and enabled Typical current idle.
>
>
> > I was able to update my BIOS to version 18, but my system still locks up.
> > I tried the following with the new BIOS:
> >  - use factory defaults
> >  - disable SMT
> >  - disable SMT with Typical Current Idle
> >  - all of the above with SVM disabled/enabled
> > Right now I set the power supply idle control to ""Low ..."" and will report
> > back.
> >
"
1690085,2020-06-28 05:23:16 UTC,"I’ll try that, but I doubt if at this stage it will have any effect."
1690085,2020-06-27 20:31:02 UTC,"Before you discard the CPU if your BIOS has PBO option turn it off, with latest BIOS on my B350 motherboard version 5406 PBO is on by default and apart from causing high temperature it would lead to this kind of crashes and reboots with my Ryzen7. Turning off PBO fixed it and now I am running a Ryzen9 with the same board and all works fine with PBO off."
1690085,2020-06-28 06:07:11 UTC,"Moreover, from a bit of reading I see that PBO is related to how fast the processor clock speeds are boosted. How is this related to crashes when idle?"
1690085,2020-07-12 14:08:16 UTC,"Created attachment 290243
attachment-20700-0.html"
1690085,2020-07-13 08:20:37 UTC,(In reply to Ashesh Ambasta from comment #699)
1690085,2020-07-24 02:17:28 UTC,"I'm also experiencing severe and constant crashes with a Ryzen 5 3600X. I also had problems with my Ryzen 7 1700 and I was confident that the problem was never going to have problems again with my Ryzen 5 3600X, but I was wrong."
1690085,2020-07-24 16:45:26 UTC,"Have you tried the suggested fixes in this thread? And what changed
between that reinstall and earlier?"
1690085,2020-08-01 11:15:33 UTC,"Even with screensavers enabled and displays never going to sleep; I just
experienced a crash on idle."
1690085,2020-09-17 05:25:09 UTC,Hello everyone.
1690085,2020-09-17 06:14:50 UTC,"I can confirm that in my case, all the suggested alternatives in this
thread didn't work (the ones that were applicable to my use-case anyway)."
1690085,2020-09-17 06:34:49 UTC,"(In reply to Ashesh Ambasta from comment #720)

> I can confirm that in my case, all the suggested alternatives in this
> thread didn't work (the ones that were applicable to my use-case anyway).
>
> In the end, I threw my hands up and did an RMA. And that was over a
> month ago. It seems to have solved the isssue. The processor I had
> previously and its replacement were different batches; the former being
> from 2019 and the latter from Feb. 2020. It seems to me that AMD ironed
> out some issues with processors and I got lucky with the replacement. Or
> it could just be some tiny variations in fabrication. I can never be sure.
>
> But my machine has been up since the RMA without any crashes.
"
1690085,2020-09-17 07:32:47 UTC,"my R5 3600 freezing was solved by RMA, running 3 weeks without problem"
1690085,2020-09-22 09:31:29 UTC,Another Ryzen 7 1800X user here with similar random crashes.
1690085,2017-10-05 16:08:33 UTC,"I finally managed to figure out how to compile a kernel with RCU_NOCB and disabled ASLR as Alex Jones mentioned, and it appears to have worked for me and another guy who helped me put the tutorial together:"
1690085,2020-06-27 11:42:11 UTC,"As a last resort, I've tried `idle=halt` on this machine. And yet my
system just crashed after 3 weeks of uptime."
1690085,2017-09-08 16:55:33 UTC,"Hi guys,"
1690085,2020-07-12 13:58:58 UTC,"Did you ask for an RMA? Did it work?
(In reply to Ashesh Ambasta from comment #692)

> As a last resort, I've tried `idle=halt` on this machine. And yet my
> system just crashed after 3 weeks of uptime.
>
> I'm done with AMD. I will RMA this processor to try things out, but
> overall, if that doesn't work, this thing is headed to the junkyard and
> I'm going to live with Intel.
>
> At least in the 13 or so odd Intel systems I've tried, I've not had
> exhasperating issues like these where the company is positively trying
> to ignore this ongoing issue.
>
> This is disgusting from AMD.
>
> On 6/11/20 6:03 PM, <email address hidden> wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=196683
> >
> > --- Comment #689 from <email address hidden> ---
> > (In reply to raulvior.bcn from comment #653)
> >> (In reply to txrx from comment #651)
> >>
> >> Typical Current Idle might not be working. Read the sensor output. If
> >> voltage is not higher than without enabling it, try to increase the core
> >> voltage.
> >>
> >> My Ryzen 7 1800X seems to not produce hangs since I upgraded to 1003ABB
> with
> >> an ASUS Crosshair VI Hero and enabled Typical current idle.
> >>
> >>
> >>> I was able to update my BIOS to version 18, but my system still locks up.
> >>> I tried the following with the new BIOS:
> >>>   - use factory defaults
> >>>   - disable SMT
> >>>   - disable SMT with Typical Current Idle
> >>>   - all of the above with SVM disabled/enabled
> >>> Right now I set the power supply idle control to ""Low ..."" and will
> report
> >>> back.
> >>>
> > The motherboard kept hanging. I had to remove the Vitals GNOME Extension.
> It
> > seems that polling voltage values hangs the motherboard... Still, there are
> > times that the computer does not come back from suspend. There's something
> > wrong with the BIOS/UEFI.
> >
"
1690085,2017-07-28 08:42:38 UTC,"Ok, this trick did not help and my PC did not make it through the night without freezing again."
1690085,2017-08-24 08:55:36 UTC,Just wanting to report that I am also experiencing this issue with a freshly installed Ubuntu Server 16.04.3 with 4.10 kernel on the 22nd August 2017. All the updates applied and running as a KVM host with hardware:
1690085,2017-05-11 08:42:45 UTC,apport information
1690085,2017-05-11 08:42:47 UTC,apport information
1690085,2017-05-15 10:22:13 UTC,"Hi Vicent,"
1690085,2017-05-15 12:25:15 UTC,"Hi Lipido,"
1690085,2017-05-15 15:27:56 UTC,"Ok, me too :-("
1690085,2017-05-15 15:40:19 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1690085,2017-05-15 15:59:49 UTC,"Hi Joseph,"
1690085,2017-05-15 16:45:55 UTC,Just go a kernel panic...
1690085,2017-05-15 22:00:02 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1690085,2017-05-17 15:38:46 UTC,"Hi,"
1690085,2017-05-18 14:22:47 UTC,"Hi,"
1690085,2017-05-22 09:39:34 UTC,"Hi Vincent,"
1690085,2017-05-24 07:55:15 UTC,"Hi,"
1690085,2017-05-29 08:44:27 UTC,"Hi Vincent,"
1690085,2017-05-11 08:30:17 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1690085,2017-06-09 01:07:18 UTC,This is a hardware bug in the CPU. This ticket should be closed as invalid.
1690085,2017-07-27 17:25:43 UTC,"I've ran into this problem several times. After disabling C-states in the motherboard, my system has been running stable for ~5 weeks uptime so far."
1690085,2017-07-26 16:15:38 UTC,I also experience this problem since I updated yesterday.
1690085,2017-07-26 03:50:39 UTC,This is beyond my expertise - let's see what upstream can do.
1690085,2017-07-26 02:20:06 UTC,"I've also determined that changing the CPU, memory, or SOC voltages or timings has little or no effect on either type of crash."
1690085,2017-07-26 02:15:06 UTC,"If the motherboard allows it, disabling the OpCache will completely prevent (or at least greatly reduce the probability of) the ASLR-related crash, even if ASLR is enabled in the kernel. As far as I'm aware it has no effect on the other type of crash."
1690085,2017-07-26 02:12:25 UTC,This is the DragonFlyBSD commit. https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/b48dd28447fc8ef62fbc963accd301557fd9ac20
1690085,2017-05-29 23:42:56 UTC,I'm seeing this crash even with the Nvidia official driver.
1690085,2017-07-23 19:49:50 UTC,"If any of your RAM timings are odd (eg. 17), setting them to the next even number (eg. 18) helps a lot. Recompiling the kernel with CONFIG_RCU_NOCB_CPU and CONFIG_RCU_NOCB_CPU_ALL, and disabling ASLR is still necessary though. It may also be a good idea to give the SOC slightly more voltage, but not more than 1.2 V."
1690085,2017-07-24 04:45:24 UTC,"Alex,"
1690085,2017-06-14 01:30:06 UTC,This change was made by a bot.
1690085,2017-06-14 01:27:12 UTC,Reopening because even though this is a known issue with the CPU we could still implement a workaround. One workaround is to disable address space layout randomization:
1690085,2017-07-21 22:45:00 UTC,"AMD has not publicly commented on this issue that I'm aware of. This issue has been seen on many different operating systems. DragonFlyBSD includes a workaround for this issue. The workaround on Linux is to compile the kernel with CONFIG_RCU_NOCB_CPU, CONFIG_RCU_NOCB_CPU_ALL, and disable ASLR using ""echo 0 >/proc/sys/kernel/randomize_va_space"". This can be put into rc.local. It's also possible to hardcode ASLR as disabled into the kernel, but this requires modifying the kernel source, not just the config file. There is a new AGESA update released about a week ago, 1.0.0.6a, although I have not tested whether the new AGESA alone (without any kernel changes) solves the issue."
1690085,2017-07-23 00:19:44 UTC,"I just tested 1.0.0.6a AGESA, and it does not solve this issue. In some cases just one program will crash, and in other cases the entire system will crash. I will test the workaround above later."
1690085,2017-07-06 22:02:42 UTC,"Was this issue officially confirmed to be a hardware bug in Ryzen processors by AMD?
If so, could you provide a link to the statement?"
1690100,2017-05-11 09:20:27 UTC,"   bzr branch lp:terminator
        cd terminator
        ./terminator"
1690100,2017-05-15 22:58:01 UTC,These plugins you are installing are external to the project?
1690100,2017-05-16 10:02:28 UTC,"Hello Stephen,"
1690100,2017-05-16 21:44:39 UTC,"Well from the debug it looks to me (from my quick scan) fairly obvious what is going on. get_text_range on 172 returns a single string/buffer. The writelines on 175 expects a list of strings, each one a line of text. Just changing writelines to write would probably fix this."
1690100,2017-05-16 11:02:54 UTC,"joost@cal-26:~$ terminator -d
ConfigBase::__init__: Borg::__init__: Preparing borg state for ConfigBase
noclass::get_config_dir: Found config dir: /home/joost/.config
ConfigBase::load: looking for config file: /home/joost/.config/terminator/config
ConfigBase::load: config validated successfully
ConfigBase::load: ConfigBase::load: Processing section: global_config
ConfigBase::load: ConfigBase::load: Processing section: keybindings
ConfigBase::load: ConfigBase::load: Processing section: profiles
ConfigBase::load: ConfigBase::load: Processing profile: default
ConfigBase::load: ConfigBase::load: Processing section: layouts
ConfigBase::load: ConfigBase::load: Processing layouts: default
ConfigBase::load: ConfigBase::load: Processing section: plugins
ConfigBase::load: ConfigBase::load: Processing plugins: TerminalExporter
Config::set_profile: Config::set_profile: Changing profile to default
Config::connect_gsetting_callbacks: GSetting connects for system changes
noclass::parse_options: OptionParse::parse_options: command line options: {'nodbus': None, 'classname': None, 'working_directory': None, 'select': None, 'fullscreen': None, 'layout': 'default', 'debug_classes': None, 'version': None, 'role': None, 'forcedicon': None, 'config': '/home/joost/.config/terminator/config', 'profile': None, 'debug_methods': None, 'maximise': None, 'debug': 1, 'borderless': None, 'new_tab': None, 'hidden': None, 'dummy': None, 'execute': None, 'geometry': None, 'command': None, 'forcedtitle': None}
ConfigBase::load: ConfigBase::load: config already loaded
Config::set_profile: Config::set_profile: Changing profile to default
Config::connect_gsetting_callbacks: GSetting connects for system changes
ConfigBase::get_item: ConfigBase::get_item: dbus found in globals: True
function::with_proxy: dbus client call: new_window_cmdline
function::with_proxy: dbus client call: new_tab_cmdline
function::with_proxy: dbus client call: new_window
function::with_proxy: dbus client call: new_tab
function::with_proxy: dbus client call: hsplit
function::with_proxy: dbus client call: vsplit
function::with_proxy: dbus client call: get_terminals
function::with_proxy: dbus client call: get_window
function::with_proxy: dbus client call: get_window_title
function::with_proxy: dbus client call: get_tab
function::with_proxy: dbus client call: get_tab_title
DBusService::__init__: Borg::__init__: Preparing borg state for DBusService
DBusService::prepare_attributes: Checking for bus name availability: net.tenshu.Terminator20x1a6021154d881c
Terminator::__init__: Borg::__init__: Preparing borg state for Terminator
ConfigBase::load: ConfigBase::load: config already loaded
Config::set_profile: Config::set_profile: Changing profile to default
Config::connect_gsetting_callbacks: GSetting connects for system changes
ConfigBase::get_item: ConfigBase::get_item: broadcast_default found in globals: group
noclass::get_pid_cwd: Using Linux get_pid_cwd
Terminator::attempt_gnome_client: GNOME session support not available
Factory::__init__: Borg::__init__: Preparing borg state for Factory
ConfigBase::get_item: ConfigBase::get_item: extra_styling found in globals: False
ConfigBase::get_item: ConfigBase::get_ite..."
1690104,2017-05-11 09:59:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/463960"
1690107,2017-05-11 10:00:12 UTC,This change was made by a bot.
1690107,2017-05-12 00:04:37 UTC,"Is this over vmconnect, RDP, or in an ssh session?"
1690107,2017-05-12 17:27:25 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].
1690110,2017-05-11 11:15:05 UTC,"I have fixed this problem which regrettably was operator error. Required a correctly-set up self-signed certificate which is now installed. citrus is working happily using php7 and mysqli.
Please cancel this bug report."
1690115,2017-12-15 10:42:04 UTC,"Reviewed:  https://review.openstack.org/524138
Committed: https://git.openstack.org/cgit/openstack/networking-generic-switch/commit/?id=d8d58a81565116a8fae796d55ab5ee6fe90d83c7
Submitter: Zuul
Branch:    master"
1690115,2017-11-30 11:07:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524138"
1690115,2017-11-30 10:50:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524135"
1690115,2017-12-14 15:57:49 UTC,"Reviewed:  https://review.openstack.org/524135
Committed: https://git.openstack.org/cgit/openstack/networking-generic-switch/commit/?id=16c50b691bbe67c267f0ebfde8a79a54f19ea0cd
Submitter: Zuul
Branch:    master"
1690118,2017-06-09 08:35:25 UTC,This bug was fixed in the package kernel-wedge - 2.96ubuntu2
1690131,2017-05-12 06:11:12 UTC,It looks like the logs you are posting are from a physical host running the modesetting driver on top of an intel kms driver. That's AFAIK not a VMware supported configuraion. Nevertheless you shouldn't see any rendering corruption caused by the VMware drivers in the guest.
1690131,2017-05-24 03:02:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690137,2017-05-15 04:30:47 UTC,"Does the following command in a terminal solve your issue? If not, can you please paste the full output here?"
1690139,2017-05-11 12:54:17 UTC,Attaching the snapcraft.yaml in case the git repo changes.
1690141,2019-08-14 04:17:15 UTC,[Expired for linux-hwe-edge (Ubuntu) because there has been no activity for 60 days.]
1690141,2019-06-14 09:30:03 UTC,"Hello,
do you still have this issue with the latest linux-hwe-edge kernel?
Thanks"
1690150,2017-05-11 13:43:19 UTC,"What happened to the DIT after ""addprinc steve"""
1690150,2017-05-11 13:46:36 UTC,What happened to the existing uid=john entry after addprinc -x
1690150,2017-05-11 16:40:58 UTC,"We don't necessarily have to show the output, much less the full diff. The
actual command output is the same in both cases. As you say, the full diff
might look too confusing, but I thought I would attach it to the bug since
I went through that exercise. At least I think it would help the writer in
explaining what are the differences between ""addprinc -x"" and just
""addprinc""."
1690150,2020-04-22 21:42:00 UTC,I fixed this in https://discourse.ubuntu.com/t/service-kerberos-with-openldap-backend/15356
1690150,2017-05-11 16:16:52 UTC,I'm not sure about showing a lot of command output. What will that look like?
1690153,2017-05-11 16:17:54 UTC,Agreed.
1690153,2020-04-22 21:40:34 UTC,I fixed this in the kerberos+openldap guide at https://discourse.ubuntu.com/t/service-kerberos-with-openldap-backend/15356
1690167,2017-05-12 03:56:50 UTC,"The support for Ubuntu 17.04 is not added in HPLIP 3.17.4. It will be added in the next release. You can manually add the printer using following link
https://wiki.archlinux.org/index.php/CUPS#Troubleshooting"
1690167,2017-05-12 12:48:15 UTC,Many thanks Kedar for the prompt response
1690167,2017-06-12 07:50:58 UTC, I to do the youyo talk talkingwith u
1690168,2017-05-11 17:08:07 UTC,Confirmed for regular files (folders of course react to a click by opening a new column).
1690174,2017-05-16 19:03:59 UTC,We need to backport the patch for the kernels with older versions of the driver. Can you please describe the steps to reproduce and test the issue?
1690174,2017-05-18 16:29:55 UTC,UDP packet loss with 8+ vCPUs can range as high as 80% when driven hard with multi-connection runs with iperf3 and ntttcp.
1690174,2017-07-25 19:44:19 UTC,In order to test and reproduce the problem the following iperf3 arguments can be used for the client side:
1690174,2017-07-26 13:49:25 UTC,Fix for linux-azure:
1690174,2017-07-26 13:50:16 UTC,"Fixes for xenial, zesty and artful:"
1690174,2017-08-10 05:56:17 UTC,This bug was fixed in the package linux - 4.11.0-13.19
1690174,2017-08-16 16:33:30 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1690174,2017-08-16 16:34:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1690174,2017-08-28 10:14:02 UTC,This bug was fixed in the package linux - 4.4.0-93.116
1690174,2017-08-28 10:14:27 UTC,This bug was fixed in the package linux - 4.10.0-33.37
1690174,2017-05-11 15:42:24 UTC,"This should apply to 4.4, 4.8, and 4.10 kernels. It's been accepted into linux-next."
1690177,2017-06-06 16:48:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1690177,2017-05-25 12:40:47 UTC,Second version of the pull request submitted:
1690177,2017-05-23 15:34:20 UTC,I removed these two commits and prepared a new kernel for testing:
1690177,2017-05-19 17:37:26 UTC,"First cut doesn't boot on local hyper-v still, but I'll try in Azure soon."
1690177,2017-05-18 23:07:32 UTC,I submitted the first version of the backport for review:
1690177,2017-05-11 15:54:41 UTC,"Since 4.10 did not apply cleanly to 4.4, I'm requesting these for 4.8, 4.10, and Azure kernel."
1690177,2017-05-11 15:54:13 UTC,"Some of these commits have already been applied, but are included for completeness."
1690177,2017-05-19 20:47:48 UTC,"I'm definitely seeing issues with PCI interrupts with PCI passthrough, probably related to"
1690183,2017-06-01 16:31:50 UTC,"Confirmed that linux-aws (4.4.0-1018.27) and linux-gke (4.4.0-1014.14), which are currently in -proposed, are not producing the linux-*-source packages anymore."
1690183,2017-06-06 15:02:55 UTC,This bug was fixed in the package linux-aws - 4.4.0-1018.27
1690183,2017-06-06 15:04:47 UTC,This bug was fixed in the package linux-gke - 4.4.0-1014.14
1690184,2017-12-03 19:34:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525000"
1690184,2017-12-03 19:37:19 UTC,"Hi all,"
1690186,2017-05-15 09:38:13 UTC,"apparently it's related to this tempest bug: https://bugs.launchpad.net/tempest/+bug/1556864.
Since sahara-tests uses tempest to initialize the http object. And the http object created doesn't handle proxying."
1690196,2017-06-06 16:48:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1690196,2017-05-25 13:30:43 UTC,A few comments and questions:
1690196,2017-05-29 12:54:40 UTC,Microsoft also requested the inclusion of these 2 patches related to hv_sock:
1690196,2017-05-11 19:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1690197,2017-07-20 17:06:40 UTC,"Yup; despite several patches [1][2][3] related to this general problem, we still haven't gotten it right. Part of the trouble is that we're trying to accommodate both protocol-aware terminators (which would add the Forward/X-Forwarded-Proto headers) as well as protocol-agnostic ones (which can't). And we *certainly* haven't been thinking about this problem from a bi-modal-access perspective."
1690197,2018-07-27 15:31:54 UTC,Maybe addressed by https://github.com/openstack/swift/commit/661838d and https://github.com/openstack/swift/commit/7b5c30d ?
1690197,2019-11-12 23:32:37 UTC,"So testing with haproxy configured like http://paste.openstack.org/show/786004/, I got http redirecting to http and https redirecting to https... I think that's probably the way to go? Not sure how best to handle it for other terminators like hitch or stunnel though..."
1690214,2017-08-01 15:07:25 UTC,Believe fixed - needs test
1690214,2017-09-20 16:27:36 UTC,"Change abandoned by Ian Wells (<email address hidden>) on branch: master
Review: https://review.openstack.org/463621"
1690215,2020-02-10 10:41:20 UTC,@garyrhook see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466330
1690225,2017-06-28 16:35:34 UTC,This bug was fixed in the package linux - 4.4.0-83.106
1690225,2017-07-10 14:47:48 UTC,I've tested this on ppc64el (Power8) Xenial. Everything worked as expected.
1690225,2017-05-12 12:05:22 UTC,Patch sent upstream at https://lists.ubuntu.com/archives/kernel-team/2017-May/084092.html
1690225,2017-06-14 09:09:32 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1690226,2017-05-13 16:44:10 UTC,Latest patch in https://review.openstack.org/#/c/459990/ seems to resolve the problem.
1690231,2017-05-19 14:56:16 UTC,Related? https://bugs.launchpad.net/maas/+bug/1546301
1690231,2017-05-16 00:27:05 UTC,"@paulgear, no, that type of change is out of scope and too risky to add to a maintenance release of MAAS. The change I proposed relies on the subnet's configured gateway IP to be correct."
1690231,2017-05-15 23:59:49 UTC,"@mpontillo, yep; so I guess the question is: does the ""simpler version of (2) which doesn't attempt to backport all the new smarts in MAAS 2.x"" include the smarts to use ping and/or ARP tables?"
1690231,2017-05-15 23:44:20 UTC,"@paulgear, MAAS uses the operational state of the network starting in version 2.1, but this bug was filed against MAAS 1.9."
1690231,2017-05-15 22:56:05 UTC,I'm proposing a simpler version of (2) which doesn't attempt to backport all the new smarts in MAAS 2.x.
1690231,2017-05-15 23:30:35 UTC,"@andresrl, to my knowledge this bug was created as a result of an outage on an unmanaged subnet, and there's nothing in the description which suggests it refers to managed subnets.  This leads me to the conclusion that it is the same problem as #1569683."
1690231,2017-05-15 20:50:59 UTC,"    MAAS did not start pre-reserving IP addresses until MAAS 2.0. MAAS 1.9
expects the static range to be under the complete control of MAAS."
1690231,2017-05-15 21:26:25 UTC,"For the record, support for exclusion of gateway IPs was added in revision 4657 for inclusion in MAAS 2.0, as part of IP range enablement work."
1690231,2017-05-11 21:14:30 UTC,"So, to be clear, MAAS allocated the IP of the default gateway of the rack controller.  You should not have to tell MAAS not to shoot itself in the face."
1690231,2017-05-11 21:10:21 UTC,Setting this back to invalid provided that it is possible to reserve IP's:
1690231,2017-05-11 22:08:21 UTC,"We having existing bugs open for the same, or similar - LP: #1569683 and #1600249."
1690231,2017-05-12 13:14:55 UTC,"@Haw,"
1690231,2017-05-11 21:22:59 UTC,"Wait, if this happened in MAAS 1.9, doesn't that mean that the static range on the cluster interface includes the gateway IP?"
1690233,2017-05-16 07:00:30 UTC,"I think a better solution would just be to download all available .po files. The problem is here, as outlined above, that Polish language for example is actually now below 40% because the JS .po files are not being pulled in at all, so the total % is falling."
1690233,2017-05-11 21:24:28 UTC,Example: Horizon has 4 po files per language - due to python and js files creating django and djangojs.po
1690233,2017-06-08 12:45:05 UTC,It would also fix the bug with some being forced lower because of low % JS translations
1690233,2017-06-08 12:44:33 UTC,"Did we get a resolution on this? I would really like to see us use all available translations. IMO, its more useful to see even 25% translated than zero. It seems like a waste of translator efforts if we don't include them."
1690233,2017-05-15 23:09:17 UTC,"It really makes sense when we consider po files from Horizon source codes: e.g., django.po and djangojs.po, but it is difficult to generalize to apply all po files including po files for Horizon release notes and documentation, and also in openstack-manuals different documents use different po files."
1690233,2017-05-21 19:30:39 UTC,"If you are talking about the translation check-site, the situation would be different. The site is to check translations, so the criteria of translation imports needs to be lower."
1690233,2017-05-21 19:29:22 UTC,"Per discussion in the i18n team, we list languages with 80~90% progress to horizon settings.LANGUAGES list."
1690233,2017-05-21 20:55:35 UTC,"So, that's my point really; I think Horizon should include *all* .po files regardless of %. Then let deployers manage what are shown. We can have 70% as our default languages, but we should still download all translations in the .po files."
1690249,2017-05-11 22:37:15 UTC,"Can't go so far..I'm a simple user. Thank you, it's up to you..in your hands..."
1690252,2017-06-07 14:09:03 UTC,"For now the ""workaround"" we found is to add a task to neutron/do_reconfigure.yml to make sure keepalived is kill properly before restarting the container."
1690252,2018-12-13 10:33:31 UTC,Should be fixed with: https://review.openstack.org/620238
1690252,2020-08-11 17:17:03 UTC,"Hi,"
1690252,2020-08-11 17:24:15 UTC,I'd like to add that Gaëtan Trellu's workaround is also working for me. When you manually kill all keepalived processes with SIGTERM then they are removing IP addresses before they quit.
1690253,2017-05-12 00:38:00 UTC,This bug was fixed in the package gnome-control-center - 1:3.24.2-0ubuntu1
1690254,2017-07-06 09:34:57 UTC,"That reminds me of a similar bug we had with the Ubuntu Touch webbrowser-app, where text selection on touch devices wasn't working for nytimes.com (bug #1573620). This was fixed by adding a specific (android-like) user-agent override for that site. I wouldn't be surprised if it was a similar issue where nytimes.com does funny things to disallow selection based on user-agent detection."
1690254,2017-06-23 15:13:58 UTC,"Moving this to the Chromium browser package. https://bugs.launchpad.net/ubuntu/+source/chromium/ is for the game package chromium-bsu, not the web browser (confusing, I know)."
1690254,2017-05-11 22:41:58 UTC,Done: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690254
1690254,2017-05-11 08:14:27 UTC,"Good idea. I've retested, results are as follows:"
1690254,2017-05-11 08:55:17 UTC,All the above Linux tests were on Ubuntu 17.04. Surprisingly:
1690254,2017-05-11 05:29:07 UTC,"Selection works fine for me, using FF53 on Linux64."
1690254,2017-05-11 13:49:19 UTC,Thanks for testing!
1690254,2017-05-11 01:11:50 UTC,"User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170418122848"
1690269,2017-05-25 02:50:04 UTC,"I just confirmed this bug comes from the upstream Ubuntu - exact same thing happens there. I am not sure which project do I chose from the list of ""Also affects project""."
1690287,2017-05-15 14:08:31 UTC,Thanks Luke for making us aware!
1690287,2017-05-15 14:10:10 UTC,"Older releases had that at least in a non version specific path, so with some hackery one could load it:"
1690287,2017-05-15 14:10:45 UTC,Luke you assigned the Ubuntu portion to yourself - will you be driving this on the Ubuntu side as well?
1690287,2017-05-16 03:30:09 UTC,"> Luke you assigned the Ubuntu portion to yourself - will you be driving this on the Ubuntu side as > well?
"
1690287,2017-05-16 04:00:51 UTC,Source package was different in 16.04
1690287,2017-05-16 04:05:46 UTC,"I think there was a *brief* period where this worked correctly in the archive, insofar as the version of ``libengine-pkcs11-openssl`` in Yakkety, built against xenial libssl1.0.0, would've used the right path."
1690287,2017-06-13 13:35:10 UTC,"I checked if I could help sponsoring that already - thanks Luke for all the work!
For engine-pkcs11 one has to realize that it was dropped in artful as it seems.
In that sense for he SRU ""it is released"" I'd think - at least when the other packages change are complete."
1690287,2017-12-11 15:38:36 UTC,Coming by checking bugs that were dormant an unexpected long time.
1690291,2019-11-22 02:05:33 UTC,"Reviewed:  https://reviews.mahara.org/10046
Committed: https://git.mahara.org/mahara/mahara/commit/08d5eeab1dd18afd04cb62a537e8f14c7a2d437c
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1690291,2019-05-27 23:20:02 UTC,After speaking with dev - Behat testing will be limited to partial functionality of the Web services.
1690301,2019-05-17 11:53:44 UTC,"Verified that fix for bug 1809249 applies to this bug as well.
So marking this bug as duplicate of 1809249."
1690303,2017-05-12 06:36:40 UTC,">The goods new is that Inkscape 0.92.1 on Windows displays the artwork correctly.
"
1690303,2017-05-12 07:38:45 UTC,"It depends on the perspective: For the average user's point of view one could say ""yes"", but from the computer scientist's point of view you can't decide until you know what the problem really was. So what was the problem?: Saving issue or loading issue?"
1690303,2017-05-12 14:25:56 UTC,"part of the problem is that the text in question is of type 'flowed text'. Not all browsers will support text of this type. I know that Firefox 43, and IE11, and IE8 with the Adobe plugin, will not display flowed text. You might wish to consider using normal text instead."
1690303,2020-03-25 08:51:13 UTC,Closing since it only affects very old Inkscape versions.
1690306,2017-05-12 06:41:22 UTC,"/usr/local/lib/python2.7/dist-packages/novaclient/client.py:268: UserWarning: The 'connection_pool' argument is deprecated in Ocata and its use may result in errors in future releases.
  warnings.warn(msg)
Traceback (most recent call last):
  File ""inspector.py"", line 95, in <module>
    inspector = DoctorInspectorSample()
  File ""inspector.py"", line 62, in __init__
    self.nova.servers.list(detailed=False)
  File ""/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py"", line 872, in list
    ""servers"")
  File ""/usr/local/lib/python2.7/dist-packages/novaclient/base.py"", line 254, in _list
    resp, body = self.api.client.get(url)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py"", line 223, in get
    return self.request(url, 'GET', **kwargs)
  File ""/usr/local/lib/python2.7/dist-packages/novaclient/client.py"", line 78, in request
    **kwargs)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py"", line 382, in request
    resp = super(LegacyJsonAdapter, self).request(*args, **kwargs)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py"", line 148, in request
    return self.session.request(url, method, **kwargs)
  File ""/usr/local/lib/python2.7/dist-packages/positional/__init__.py"", line 101, in inner
    return wrapped(*args, **kwargs)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py"", line 491, in request
    auth_headers = self.get_auth_headers(auth)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py"", line 818, in get_auth_headers
    return auth.get_headers(self, **kwargs)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/plugin.py"", line 90, in get_headers
    token = self.get_token(session)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/identity/base.py"", line 90, in get_token
    return self.get_access(session).auth_token
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/identity/base.py"", line 136, in get_access
    self.auth_ref = self.get_auth_ref(session)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/identity/v2.py"", line 65, in get_auth_ref
    authenticated=False, log=False)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py"", line 766, in post
    return self.request(url, 'POST', **kwargs)
  File ""/usr/local/lib/python2.7/dist-packages/positional/__init__.py"", line 101, in inner
    return wrapped(*args, **kwargs)
  File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py"", line 655, in request
    raise exceptions.from_response(resp, method, url)"
1690317,2018-05-25 10:47:49 UTC,"Sorry, That's not the solution.
Can't reproduce this error in devstack"
1690317,2018-05-25 10:45:58 UTC,"I think the problem is in request url:
GOT:      GET http://<ip>:8989/v2/executions/?fields=workflow_name,created_at
EXPECTED: GET http://<ip>:8989/v2/executions?fields=workflow_name,created_at
So last /  before ? is not needed"
1690318,2017-05-12 08:11:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/464144"
1690318,2018-12-29 13:37:54 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/464144
Reason: This patch has no activity for a while, per policy, we abandon it. Feel free to re-open if you think you're working on it."
1690320,2018-01-25 08:47:50 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3700
1690320,2017-05-12 12:23:26 UTC,"Further experimentation reveals that the (select ...) clause in the ORDER BY section causes the crash.  If the (select ... ) in the ORDER BY is replaced with a simple column reference, the query works."
1690322,2020-11-10 15:45:25 UTC,The memory region mapped by QEMU for -mem-path is configured such that changes are private to the QEMU process.
1690324,2020-09-22 08:26:04 UTC,Closing because INVALID: Can't replicate.
1690326,2017-05-12 18:53:46 UTC,The default values are already defined in the skin manifest. There would just need to be a way to restore all those defaults after loading the skin.
1690326,2017-05-13 14:12:28 UTC,"If this becomes a button in Preferences > Interface labeled ""Set skin defaults"" it would be a good opportunity to put a link to skin specific ReadMe files there, as well.
Skin names are short so selector drop down can be narrow, therefore ""Skin Defaults"" and ""ReadMe"" could be in the same row."
1690326,2017-05-13 15:55:34 UTC,"> skin specific ReadMe files
"
1690327,2019-09-19 08:21:13 UTC,"After booting (not always - some times), it is showing two indicator menu icons on the menu bar. They both are functional."
1690337,2017-05-18 01:30:07 UTC,This change was made by a bot.
1690341,2020-07-01 21:23:38 UTC,Thank you for your bug report. Is that still an issue in newer versions? If so could you report it upstream on https://gitlab.gnome.org/GNOME/evince/-/issues ?
1690341,2020-08-31 04:17:36 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1690345,2017-06-29 10:01:26 UTC,"Re ""juju add-relation ceilometer-agent nova-lxd"" - we don't have ceilometer metric collection support for LXD yet so that relation is superfluous at the moment."
1690345,2017-06-29 09:59:46 UTC,"lxdbr0 is not used by the nova-lxd driver (it wires things into Neutron, rather than into anything LXD itself controls) so I'd not expect that to fix anything."
1690345,2017-06-20 12:08:18 UTC,"James,"
1690345,2017-06-19 09:20:46 UTC,as it's not working i changed back to ZFS (and issued a reboot on the hypervisor)
1690345,2017-06-19 07:53:05 UTC,"Dear James,"
1690345,2017-06-16 09:24:22 UTC,"Dear James,"
1690345,2017-06-16 14:55:57 UTC,Patrizio
1690345,2017-06-16 14:50:40 UTC,"Thanks for that information; I actually need the version of the nova-compute-lxd package thats installed on the nova-compute-lxd units; 14.0.4 is the main nova version, not the driver version for LXD."
1690345,2017-06-16 09:12:18 UTC,Hi Patrizio
1690345,2017-05-28 14:21:28 UTC,"hi all, is anyone checking this issue?"
1690348,2017-05-13 00:20:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690348,2018-01-30 05:56:41 UTC,"I also observe this bug today, using:"
1690348,2018-06-21 00:36:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690348,2019-03-05 14:20:35 UTC,"I'm having the same issue with Firefox 65. Seems to be only happen on Facebook though.
When trying to reproduce with this comment field itself the bug doesn't happen."
1690350,2017-05-28 09:16:11 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1690351,2017-05-12 21:02:20 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1690351,2017-05-13 18:55:40 UTC,I've forwarded the issue (alongside a patch) to the Debian maintainer. See the attached bug watch for details.
1690351,2020-11-05 15:20:27 UTC,"Though the bug watch hasn't updated the status for some reason, the Debian bug has been fixed."
1690357,2017-05-12 12:08:30 UTC,apport information
1690357,2017-05-12 12:08:31 UTC,apport information
1690357,2017-05-12 12:08:32 UTC,apport information
1690357,2017-05-12 12:11:16 UTC,Please note that apport-collect was made with disabled faulty modules
1690357,2017-05-24 14:57:51 UTC,Probably still need to find the commit fixes the slowness.
1690357,2017-05-16 06:37:33 UTC,Verified with Linux E6400 4.12.0-041200rc1-generic #201705131731 SMP Sat May 13 21:32:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1690357,2017-05-16 07:24:18 UTC,So the issue didn't happen in 16.10 kernel (4.8)?
1690357,2017-05-24 14:08:57 UTC,Sorry for the delay.
1690357,2017-05-15 19:53:45 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1690357,2017-05-12 12:08:29 UTC,apport information
1690357,2017-05-12 12:08:28 UTC,apport information
1690357,2017-05-12 12:08:26 UTC,apport information
1690357,2017-05-12 12:08:25 UTC,apport information
1690357,2017-05-12 12:08:24 UTC,apport information
1690357,2017-05-12 12:08:23 UTC,apport information
1690357,2017-05-12 12:08:22 UTC,apport information
1690357,2017-05-12 12:08:21 UTC,apport information
1690357,2017-05-12 12:08:19 UTC,apport information
1690357,2017-05-12 12:08:18 UTC,apport information
1690357,2017-05-12 12:08:17 UTC,apport information
1690357,2017-05-12 12:08:16 UTC,apport information
1690357,2017-05-12 12:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1690357,2017-05-12 12:08:27 UTC,apport information
1690358,2017-11-03 16:43:06 UTC,Syncing task from Mir.
1690374,2018-10-10 09:37:22 UTC,Tested it with the above [nova] settings in cinder.conf and now the tempest test finishes successfully. So it seems to be a cinder configuration issue
1690374,2018-10-09 22:48:29 UTC,"Based on the previous comments, I don't think this is a nova bug, but rather a configuration issue. I think in order to use the assisted snapshots, you need to have configured the nova user in the cinder.conf, similar to how it's done in the legacy-tempest-dsvm-full-devstack-plugin-nfs job [1] (change this to match your environment):"
1690374,2018-09-10 23:25:14 UTC,"I guess the `some reason` the API is expected to called by only a service user on cider side. cinder supposed to decided about is the user allowed to do snapshot or not, than call nova `as admin` in case he is allowed."
1690374,2018-09-23 23:01:39 UTC,"Hmm, I'm pretty sure the NFS CI job is creating snapshots using this API, but the difference is probably that cinder is configured to call nova with a user that has the admin role. Is the VZ CI setup differently?"
1690374,2017-06-25 15:34:24 UTC,"Well, not. It's simply related. By default nova, for some reason, allows this actions only for admin user. Look here:"
1690374,2017-06-25 14:44:18 UTC,Looks like a duplicate of https://bugs.launchpad.net/cinder/+bug/1691362
1690374,2018-09-26 15:10:56 UTC,Running into the same issue when running tempest tests. This is with OSP12 (Pike)
1690385,2017-05-12 15:09:06 UTC,apport information
1690385,2017-05-20 18:43:23 UTC,Thank you very much.  I installed kernel v4.12-rc1 and the problem went away!  Thank you so much again~  I have added the tag.
1690385,2017-05-15 20:12:24 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1690385,2017-05-12 15:09:13 UTC,apport information
1690385,2017-05-12 15:09:10 UTC,apport information
1690385,2017-05-12 15:09:08 UTC,apport information
1690385,2017-05-12 15:09:07 UTC,apport information
1690385,2017-05-12 15:09:04 UTC,apport information
1690385,2017-05-12 15:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1690385,2017-05-12 15:08:59 UTC,apport information
1690385,2017-05-12 15:08:58 UTC,apport information
1690385,2017-05-12 15:08:57 UTC,apport information
1690385,2017-05-12 15:08:55 UTC,apport information
1690385,2017-05-12 15:08:54 UTC,apport information
1690385,2017-05-12 15:08:52 UTC,apport information
1690385,2017-05-12 15:08:51 UTC,apport information
1690385,2017-05-12 14:58:23 UTC,Refiled against the kernel as per https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions and advice from the forum link
1690385,2017-05-12 15:09:03 UTC,apport information
1690408,2017-12-11 17:39:44 UTC,I tried hplip-3.17.11.run in the meantime.
1690408,2017-12-11 17:50:23 UTC,I can confirm that everything works now. Setting the PATH variable to use system python version is also necessary when running hp-scan and the likes (otherwise you get an error):
1690408,2017-07-15 13:35:28 UTC,I have exactly the same errors with Mint-Sarah and hplip-3.17.6.run
1690409,2017-05-15 16:23:37 UTC,"Thanks for the bug report Paolo. Just note that for new features, we have moved the discussion to the forum instead. We are leaving the bug tracker only for actual defects in the current version."
1690409,2017-05-15 16:24:48 UTC,This is being discussed here: https://forum.snapcraft.io/t/snapcrafts-version-from-debian-changelog/633
1690410,2017-05-15 13:28:01 UTC,"Reviewed:  https://review.openstack.org/464228
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=dcaa7b11a86dd79eac5e88884bdb7a06a380468a
Submitter: Jenkins
Branch:    stable/mitaka"
1690410,2017-05-15 13:22:04 UTC,"Reviewed:  https://review.openstack.org/464600
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=9643b3035737a261ab74d8a193134096b2d91396
Submitter: Jenkins
Branch:    stable/newton"
1690410,2017-05-15 10:04:33 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/464600"
1690410,2017-05-15 10:03:34 UTC,Same issue with newton: http://logs.openstack.org/97/464597/1/check/gate-fuel-qa-pylint-ubuntu-trusty/de99ccc/console.html
1690410,2017-05-15 09:52:05 UTC,Fix: https://review.openstack.org/#/c/464228/
1690410,2017-05-15 10:11:48 UTC,https://review.openstack.org/#/q/topic:bug/1690410
1690414,2017-05-15 10:30:29 UTC,If a directory is empty (apart from .bzr) it should be repopulated.
1690414,2017-05-15 14:36:39 UTC,You can just bzr revert after doing an update or pull:
1690415,2017-05-14 03:28:28 UTC,"You can already replace the icons for all SmartEvidence matrices if you put the images into your local theme folder. However, that would affect all images."
1690418,2017-05-15 18:47:35 UTC,"Well, I guess if 680x larger is on the table, then maybe this is the proper level of precaution :)"
1690418,2017-05-15 18:36:03 UTC,Noting that I meant to say 'comparable update times' not 'delete' times a few comments up.
1690418,2017-05-15 14:21:11 UTC,"I gave this script a go on our production server, and it updated ~200,000 rows in under two seconds.  I know bigger installs will take more time, but even a factor of 10 or 20 feels within the range of a ""normal"" upgrade script."
1690418,2017-05-15 16:31:44 UTC,"Assuming comparable delete times, It'll be >20 minutes here (136M rows).  That may be an outlier (and I can always tweak the upgrade locally), but keeping the deletes out of the main upgrade transaction still seems like the better approach.  I think it can be in the same script, just at the end, post-transaction."
1690418,2017-05-12 17:50:48 UTC,Upgrade script pushed:
1690418,2017-05-15 16:33:14 UTC,"And thanks for testing that Dan, because I had not collected any data yet to justify the concern.  I'm trying a proper delete (w/ rollback) now on a test server to see what happens."
1690419,2017-05-12 17:33:41 UTC,"Might be duplicate with #1689378
BUG: unable to handle kernel NULL pointer dereference at 0000000000000022"
1690425,2017-11-30 21:19:06 UTC,"I had a conversation with Kris Lindgren of GoDaddy about this topic during the flight back from Sydney. The summary of it is that he would see a lot of benefit if we were able to improve the performance of the RPC bus by using message routing like suggested in comment #5.He also said, though, they would see a lot of benefit in moving to a configuration where cells would be reflected in Neutron for failure domain isolation purposes"
1690425,2020-06-02 19:57:44 UTC,"As was discussed on the PTG, we decided to close this RFE for now. Feel free to reopen it if there will be valid use case for that and if You will want to work on that. Then we can discuss it again in the drivers team meeting."
1690425,2020-03-19 15:22:13 UTC,"Is there still any interest in working on this? Anyone who wants to continue that?
Maybe it's not needed if we will move to ML2/OVN, where rabbitmq isn't used at all?"
1690425,2018-09-11 21:42:16 UTC,Rabbitmq vs Kafka: https://jack-vanlightly.com/blog/2017/12/4/rabbitmq-vs-kafka-part-1-messaging-topologies
1690425,2018-09-11 21:25:18 UTC,Presentation pointed to in note #5 is about Apache Qpid dispatch router. It's page is here: http://qpid.apache.org/components/dispatch-router/index.html
1690425,2017-12-21 22:36:13 UTC,It was agreed in the latest drivers meeting that the pertinent next step is to develop a prototype following the approach suggested in #5 above. The aim is to assess the feasibility of the approach and help uncover unforeseen problems
1690425,2017-10-30 15:49:11 UTC,"Members of the team will attend the ""Cells V2 update and direction"" forum session in Sydney: http://forumtopics.openstack.org/cfp/details/60. In that session we will also seek feedback from operators migrating to Cells V2 as to what bottlenecks they are finding in Neutron"
1690425,2018-09-11 21:40:39 UTC,Performance measurement of Qpid dispatch router and rabbitmq in the context of OpenStack: https://www.youtube.com/watch?v=xGTW3FvJYI4. This is the presentation: https://www.openstack.org/assets/presentation-media/Vancouver-summit-Openstack-internal-messaging-in-depth-evaluation2.pdf
1690425,2017-10-26 23:24:24 UTC,"As a reference, this is a high level description of cells V2: https://docs.openstack.org/nova/pike/user/cellsv2_layout.html"
1690425,2017-10-26 23:09:13 UTC,"The support of Cells V2 in Tricircle is experimental, according to this document: https://docs.openstack.org/tricircle/latest/install/installation-guide.html#work-with-nova-cell-v2-experiment"
1690425,2017-10-13 22:37:59 UTC,Update after meeting on 10/12/2017. Decided to take 3 actions:
1690425,2017-10-12 00:33:25 UTC,"For scaling reasons, approach as shown in [1] looks really cool."
1690425,2017-07-20 21:09:34 UTC,Let's agree on next steps here.
1690425,2017-07-12 00:52:22 UTC,"Neutron + Tricircle can work with cells v2 multi-cell to address the MQ/DB challenge: http://lists.openstack.org/pipermail/openstack-dev/2017-May/117599.html . No need to do 1:1 mapping, though it can do like this."
1690425,2017-05-16 19:23:54 UTC,"This specific proposal is not suggesting to introduce a first-class cell concept in Neutron, but rather make sure that Neutron be aware of the nova cells where the compute workload affected by networking events actually run. This has the benefit of spreading control messages over the DB/MQ clusters rather than overloading a single 'central' MQ/DB as it happens today. For this reason, I suspect that there is no need for a neutron cell abstraction per se (and thus no concern about mapping of scopes), at least in the first iteration of this effort, but I think we should be at least open to the idea in case we're missing other important use cases."
1690425,2017-05-13 18:19:02 UTC,Is it necessary that the nova cells and neutron cells are the same scope? I was wondering about an ML2 based neutron cell whereas nova cells tend to be grouped more on the hardware types (although not guaranteed)
1690425,2017-10-27 13:46:32 UTC,"Tricircle is not in production yet. OpenStack Cascading, its predecessor, is in production in 5 public clouds"
1690426,2017-05-12 18:12:06 UTC,"I also found this weird behavior: If I move a window towards plank, it looks like there's two planks, and one is hiding while the other keeps showing up. If I maximize the window, the other one hides too."
1690438,2019-12-04 08:34:45 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/488160
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1690438,2019-05-14 20:19:30 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.opendev.org/490228
Reason: This patch has been stale for awhile now. Moving it to abandoned to clean-up the queue. If this patch is still active, please push an update to it."
1690438,2018-08-31 07:43:35 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/527547
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1690438,2017-12-13 00:17:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/527547"
1690438,2017-08-02 21:58:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/490228"
1690438,2017-07-27 19:40:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/488160"
1690438,2017-07-20 21:10:29 UTC,"Looks like compare-and-swap approach is nearly done, and I already had a (racy) prototype that would implement this use case. Let's sync up on the latest state."
1690438,2017-05-25 21:52:14 UTC,This requires the compare-and-swap approach to be complete end-to-end before proceeding.
1690438,2017-05-12 18:57:46 UTC,One way to make this use-case possible is by doing the following:
1690438,2017-10-12 00:35:34 UTC,The spec is proposed and the code should be relatively contained. I need to refine the spec to incorporate feedback that Kevin gave me OTA but other than that this is a great starter RFE.
1690439,2018-06-29 20:03:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/579275"
1690439,2019-05-14 20:19:14 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.opendev.org/579275
Reason: This patch has been stale for awhile now. Moving it to abandoned to clean-up the queue. If this patch is still active, please push an update to it."
1690439,2018-10-23 18:05:31 UTC,"Change abandoned by Hongbin Lu (<email address hidden>) on branch: master
Review: https://review.openstack.org/520247
Reason: will restore it once i have a chance to work on it in the future"
1690439,2018-09-05 02:10:42 UTC,"Reviewed:  https://review.openstack.org/514110
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=7fa92e37b47641e26c071fb03d3d042e0e1bb0aa
Submitter: Zuul
Branch:    master"
1690439,2017-11-16 00:12:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520247"
1690439,2017-06-27 15:58:36 UTC,"Automatically discovered version pike in description. If this is incorrect, please update the description to include 'nova version: ...'"
1690439,2017-10-13 23:34:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511983"
1690439,2017-10-12 15:00:29 UTC,I am not sure this effort is high priority enough to deserve the attention of both teams. Work is relatively simple though.
1690439,2017-10-12 14:42:38 UTC,I have talked to Matt and will drive this effort on nova side. Will write a spec for this.
1690439,2017-10-12 13:47:30 UTC,"Nova's feature freeze will be on October 19th (in one week as of this writing). As a consequence, I don't think we are going to be able to get the Nova team to prioritize this effort during Queens. Probably the best approach is to start writing a spec on the Nova side, so we are ready the next time they unfreeze features. I will probe mriedeman to see if there is appetite for this on his side"
1690439,2017-07-20 21:13:45 UTC,"This needs a volunteer on both sides, neutron and nova. But doing the working in neutron alone is pointless if we don't have commitment on the nova side."
1690439,2017-10-23 03:01:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514110"
1690459,2017-05-13 00:25:21 UTC,"Is it really you want to mark is as a device? Because it can be PXE booted from MAAS and deployed. Seems like it would be better to keep it as a machine, but manually allow marking it as deployed and owned by a user."
1690459,2019-09-19 12:03:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1690460,2017-05-12 22:00:15 UTC,This change was made by a bot.
1690463,2017-06-20 14:01:44 UTC,"My guess: I have some backup scripts that run periodically (via crontab). (I wrote them because the version control plugin didn't work correctly, for me at least). Perhaps there's a locking problem if certain zim actions occur while a backup is running. Will try to gather evidence."
1690475,2017-10-14 07:55:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690475,2018-06-19 10:03:00 UTC,I get this bug on Ubuntu Mate 16.04 when another process is updating some packages.
1690475,2018-12-02 15:44:34 UTC,Installing update notifier fixed the problem for me in Ubuntu-MATE 18.04 LTS. Code: `$ sudo apt-get install update-notifier`
1690482,2017-05-13 00:49:04 UTC,"Stacktrace:
 #0  0xb7748a74 in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7
StacktraceSource: #0  0xb7748a74 in ?? ()
StacktraceTop: ?? ()"
1690484,2017-05-18 02:14:20 UTC,Hi Jeremy - Thanks for the bug report. We're aware of these CVEs and we're tracking them in the Ubuntu CVE Tracker:
1690485,2020-11-29 05:53:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690485,2019-06-10 15:44:23 UTC,Thank you for posting the additional information here. It sounds like this will help others affected.
1690485,2019-06-08 22:58:38 UTC,See also Ticket #1831765 and #1832110 regarding the path of the privilege separation directory (aka: /run/sshd).
1690485,2017-11-07 18:36:45 UTC,"Not trying to pester, but bumping this in case you didn't see that I posted the requested file."
1690485,2017-10-27 08:24:09 UTC,"Seth, this is not as helpful as you might think, because the socket call is being denied by seccomp so the relevant call never shows up in perf.  Feel free to try to construct a different perf call that takes account of that ..."
1690485,2017-10-29 21:59:10 UTC,"This looks very weird.  If it's calling EVP_Cipher, that should go through OpenSSL; it's conceivable that it might end up in libkeyutils via the Kerberos libraries, sure, but a simple cipher call should already have everything it needs; and libkeyutils doesn't use D-Bus."
1690485,2017-10-27 15:06:59 UTC,"I'm at a loss as to why Kerberos should affect this particular thing, at least when there's no actual Kerberos authentication involved.  Silly question, but you don't have a modified OpenSSL or anything related to it, do you, and what exact package version of libssl1.0.0 do you have installed?  Also, if you put --with-kerberos5=/usr back and remove --with-ssl-engine, does that also cure the crash?"
1690485,2017-10-27 14:13:55 UTC,"(And, for what it's worth, I don't, to the best of my knowledge, have anything
Kerberos-related set up. There is no /etc/krb5.conf file."
1690485,2017-10-27 13:58:52 UTC,I lied. I experimented with ./configure flags.
1690485,2017-10-27 13:46:18 UTC,"OK, I applied your patch, and was lucid enough to follow farther
into the maze with a few additional debug3's."
1690485,2017-10-27 08:35:33 UTC,"OK, so that puts it somewhere inside ssh_packet_send2_wrapped.  Can you revert my previous patch (patch -p1 -R <sshd-debug.patch, or use git if you're comfortable with it) and apply this one instead to narrow it down further?"
1690485,2017-10-27 01:29:24 UTC,Seth: Your requested output is perf-20171026.txt
1690485,2017-10-30 13:51:17 UTC,"Yeah, this is almost starting to look like malware trying to exfiltrate keys somehow! Unauthorized socket I/O being done by a library that doesn't match the symbol tables? (I'm glad I don't have any Kerberos keys to leak!)"
1690485,2017-10-26 22:44:40 UTC,"Hello Kevin, I don't want to step on Colin's toes here, but I couldn't sort out anything from the logs or files so far. I've had success before with perf to grab call graph information. The usual process is along the lines of:"
1690485,2017-10-27 01:12:06 UTC,The plot thickens.
1690485,2017-05-15 13:25:33 UTC,It seems surprising to me that the pre-authentication network listener would need to create new sockets.  I think the best thing to do here is going to be to rebuild sshd locally with SANDBOX_SECCOMP_FILTER_DEBUG defined (see the top of sandbox-seccomp-filter.c) to try to narrow this down.
1690485,2017-05-15 13:41:44 UTC,"Hi Kevin,
I quickly checked in the default config in zesty but ssh logins are working fine (pw logins is what I tested)."
1690485,2017-05-15 13:42:02 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1690485,2017-05-15 23:39:08 UTC,"I reset /etc/ssh/sshd_config to the attached version, and attempted"
1690485,2017-05-15 23:40:05 UTC,Here's /var/log/syslog from the ssh daemon restart through the authorization failure
1690485,2017-05-15 23:41:36 UTC,Here's the output of 'ssh -v localhost' when authorization is failing
1690485,2017-10-28 03:35:46 UTC,"Disable ssl-engine, re-enable kerberos5, it still crashes."
1690485,2017-10-25 04:56:26 UTC,"Upgraded to 17.10. Uninstalled and reinstalled openssh-client, openssh-server (including loading a fresh /usr/etc/ssh directory)."
1690485,2017-10-25 04:57:41 UTC,"Oh, another note: changing the UsePrivilegeSeparation setting no longer works. It reports that the setting is deprecated and ignores it. This leaves me without a workaround."
1690485,2017-10-25 16:00:00 UTC,"This issue was never previously closed, only marked Incomplete (which is an open state)."
1690485,2017-10-25 16:01:35 UTC,"And the exact change I want is to uncomment the ""#define SANDBOX_SECCOMP_FILTER_DEBUG 1"" line in sandbox-seccomp-filter.c; but please read the block comment above that line first."
1690485,2017-10-26 00:47:00 UTC,"OK, I think I've followed instructions here."
1690485,2017-05-15 23:42:39 UTC,And here's /etc/ssh/sshd_config on which authorization is failing.
1690485,2017-10-26 15:13:56 UTC,"Thanks.  The strace is indeed useful, although it doesn't get us all the way there.  This is very strange!  It appears that the network monitor is attempting to create a Unix socket in the middle of sending a USERAUTH_SUCCESS packet, which is peculiar to say the least."
1690500,2017-05-13 08:32:23 UTC,This bug was fixed in the package gnome-photos - 3.24.2-0ubuntu1
1690502,2017-02-28 17:53:07 UTC,"(In reply to Ivan Jurišić from comment #23)

>> ok, so if i understand it correctly, the error has always been there but is
>> now > being displayed with the 4.9 kernel?
>
> Yes, very annoying :-(
"
1690502,2017-03-28 02:17:38 UTC,When we will have the fix -- I am so tired about these messages.
1690502,2017-04-24 20:45:37 UTC,I'm using Xubuntu 17.04 with kernel 4.10.0 on ASUS GL552VW laptop and I have this from dmesg:
1690502,2017-05-15 20:09:24 UTC,"Commit 	3d4b7ae96d81dc8ed4ecd556118b632c2707ff08 was in mainline as of 4.7-rc1.  Does this bug occur with Yakkety, Zesty or Artful?"
1690502,2017-05-02 08:51:30 UTC,"ASUSTeK COMPUTER INC.
P8Z77-V LK with latest BIOS update (dated 2014 thought)"
1690502,2017-05-04 06:39:20 UTC,"Be patient.
ACPICA team now is actively working on this pull request:
https://github.com/acpica/acpica/pull/189/"
1690502,2017-02-28 07:54:23 UTC,"> ok, so if i understand it correctly, the error has always been there but is
> now > being displayed with the 4.9 kernel?
"
1690502,2017-05-17 19:11:58 UTC,It indeed happens with recent kernels; like 4.10 in Artful
1690502,2017-12-13 11:57:25 UTC,Same bug as: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407 opened one year earlier.
1690502,2017-06-04 12:09:02 UTC,Hello Mr. Zheng.
1690502,2017-07-04 01:14:32 UTC,Let me mark this as RESOLVED/MOVED.
1690502,2017-08-31 08:05:00 UTC,Artful 4.12 kernel still display these errors:
1690502,2017-10-16 08:00:45 UTC,"(In reply to Lv Zheng from comment #30)

> Let me mark this as RESOLVED/MOVED.
"
1690502,2017-12-24 07:20:57 UTC,"kail linux
#uname -a
Linux localhost 4.14.8 #4 SMP Sat Dec 23 14:33:47 CST 2017 x86_64 GNU/Linux
#dmesg | grep pcspkr
Error: Driver 'pcspkr' is already registered, aborting...
#dmesg | grep ACPI | grep -E 'Warning|Error'
[    0.036580] ACPI Error: [GPLD] Namespace lookup failure, AE_ALREADY_EXISTS (20170728/dswload-378)
[    0.037969] ACPI Error: 1 table load failures, 12 successful (20170728/tbxfload-246)
[    4.157907] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
[    4.157981] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20170728/psparse-550)
[    4.160396] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
[    4.160469] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20170728/psparse-550)
[   11.601550] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20170728/dsopcode-235)
[   11.601642] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.601718] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.601874] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20170728/dsopcode-235)
[   11.601954] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.602025] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.602173] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20170728/dsopcode-235)
[   11.602253] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.602324] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.602699] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20170728/dsopcode-235)
[   11.602783] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.602854] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.603001] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20170728/dsopcode-235)
[   11.603081] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[   11.603151] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20170728/psparse-550)"
1690502,2018-10-02 11:40:09 UTC,"On 15-dc0015np Omen device, this occurs if i use kernel 4.15 and above. But can't use kernels below, because they doesn't support many functions of my device.
Regards"
1690502,2018-11-10 00:15:17 UTC,"Hi,"
1690502,2019-11-17 15:52:56 UTC,Approaching the end of year 2019 and these bugs are still here. To make matters worse users with crashing systems unrelated to these bugs are falsely assuming they are the cause of the crash. When looking in journalctl boot startup these are the first errors you see in RED letters:
1690502,2017-05-30 17:10:43 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1690502,2017-02-28 07:49:46 UTC,"(In reply to Lv Zheng from comment #21)

> (In reply to Radek Podgorny from comment #5)
> > also, i forgot to mention i use this kernel cmdline:
> >
> > Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img
> > root=/dev/disk/by-label/PUPIK_ROOT rw ___acpi_osi=
>
> It looks your ssdt6 contains same information as dsdt.
>
>  193531\dsdt.dsl (18 hits)
>       Line 41101:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41133:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41165:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41197:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41229:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41261:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41293:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41325:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41357:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41389:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41421:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41453:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41485:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41517:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41549:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41581:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41613:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>       Line 41645:         Method (_UPC, 0, Serialized)  // _UPC: USB Port
> Capabilities
>   193531\ssdt6.dsl (20 hits)
>       Line 81:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 94:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 107:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 120:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 133:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 146:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 159:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 172:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 185:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 198:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 211:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 224:         Method (_UPC, 0, NotSerialized)  // _UPC: USB Port
> Capabilities
>       Line 237:         Method (_UPC, 0, NotSerialized)  // _...
"
1690502,2017-02-28 01:22:36 UTC,"(In reply to Radek Podgorny from comment #5)

> also, i forgot to mention i use this kernel cmdline:
>
> Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img
> root=/dev/disk/by-label/PUPIK_ROOT rw ___acpi_osi=
"
1690502,2017-02-23 14:54:58 UTC,"I can also report the bug, since I've updated to 4.9 debian 9."
1690502,2017-02-23 14:58:12 UTC,"Created attachment 254901
acpidump"
1690502,2017-01-31 05:22:59 UTC,"As for the technical details, these messages originates from the ACPI core. The _GPE._Lxx methods are level-triggered interrupts if I remember correctly and are triggered by the hardware (not Linux). Apparently this specific methods tries to evaluate some method or object at _TZ.THRM which failed because this ACPI scope does not exist.
-----------------------------------------------------------------------------
The possible fix right now is booting from whatever kernel 4.8.x or < 4.9.x. -- The kernel 4.9 includes something strange."
1690502,2017-02-01 14:07:00 UTC,"There are  people facing a similar issue on Fedora and Arch:
https://bugzilla.redhat.com/show_bug.cgi?id=1413342"
1690502,2017-02-03 02:38:30 UTC,"Hi,"
1690502,2017-02-03 10:17:35 UTC,"Created attachment 253911
acpidump.out"
1690502,2017-02-03 10:18:39 UTC,"also, i forgot to mention i use this kernel cmdline:"
1690502,2017-02-03 13:27:39 UTC,"Created attachment 253961
acpidump/out on fedora 25"
1690502,2017-02-03 15:16:07 UTC,"Created attachment 253971
""sudo acpidump > acpidump.out"" of a Dell Inspiron 7348"
1690502,2017-02-03 15:42:36 UTC,I just want to say it happens only on kernels 4.9.x on whatever distro.
1690502,2017-01-29 12:18:12 UTC,"Created attachment 253521
acpi info"
1690502,2017-02-05 10:42:13 UTC,I using motherboard:
1690502,2017-02-23 14:40:20 UTC,"Bump, I also have it since ~4.9 in fedora 25."
1690502,2017-02-19 18:10:14 UTC,"I see this in dmesg output on my Lenovo Yoga 2 11, BIOS 1.93 (latest) and N3520 processor:"
1690502,2017-02-15 22:33:29 UTC,"hmm, i can't really tell. i don't have the old kernels anymore..."
1690502,2017-02-15 22:30:59 UTC,"Addendum:
In my case the errors appear on my console as a result of the above isolated commit. However, they still, and always did, appear in the /var/log/kern.log file.
This may be slightly different than what others on this bug report are experiencing."
1690502,2017-02-03 17:25:24 UTC,"(In reply to Jose Luis Mantilla from comment #8)

> I just want to say it happens only on kernels 4.9.x on whatever distro.
"
1690502,2017-02-14 07:36:40 UTC,"My test computer is an Ubuntu server, on which this issue only occurs on resume from suspend. Normally this computer is not suspended, which is why I did not notice the issue until now. Kernel 4.8 is good, kernel 4.9-rc1 is bad. I've started a kernel bisection. It'll take a couple of days."
1690502,2017-02-10 18:01:15 UTC,I wonder what have happened about the issue -- I want to fix this error and the new updated kernel is equal.
1690502,2017-02-15 00:56:27 UTC,"Created attachment 254759
Kernel Bisection rsult and log"
1690502,2017-02-11 21:40:05 UTC,"Created attachment 254703
acpidump"
1690508,2017-05-13 08:32:28 UTC,This bug was fixed in the package gnome-documents - 3.24.2-0ubuntu1
1690511,2017-09-21 14:51:55 UTC,This would indicate that something went awry during the attachment process (hence the volume never goes to state attached/in-use).
1690512,2017-07-13 05:26:48 UTC,Please try the latest hwe stack by.  I'm using kabylake + the hwe stack without issue at the moment.
1690512,2017-05-15 00:47:42 UTC,"Hey Henrique, Thanks for your reply!"
1690512,2017-05-14 14:30:15 UTC,This change was made by a bot.
1690512,2017-05-14 17:02:01 UTC,"This is a Kabilake system, the intel-microcode does not support it as of 20161104 or 20170511 (upcoming release, to be uploaded in the next few days)."
1690515,2017-05-18 11:54:54 UTC,"Hi,"
1690516,2017-05-18 11:56:04 UTC,"Hi,"
1690516,2020-07-19 06:26:52 UTC,"Hi,"
1690516,2020-11-06 16:28:25 UTC,"Hi,
I Have the same on Arch with hplip 3.20.9. Has no attribute 'split'..."
1690524,2017-05-15 05:57:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/464540"
1690524,2017-05-15 07:38:34 UTC,"@Feng,"
1690524,2017-05-15 18:55:22 UTC,"I have the same question as Pradeep. In particular, Zun doesn't support port binding so I am not sure how ports could conflict between containers. Need further information for this bug."
1690524,2017-05-16 01:54:50 UTC,"Change abandoned by feng.shengqin (<email address hidden>) on branch: master
Review: https://review.openstack.org/464540"
1690528,2017-06-16 20:48:44 UTC,Haven't seen this since.
1690528,2017-05-14 08:11:14 UTC,"Today, screen corruption didn't happen. I did run an update after it happened yesterday."
1690533,2017-05-13 11:01:48 UTC,"its related to openssl 1.1.0 ( and above)
it should be ok if aviable with openssl 1.0.2k and so on"
1690533,2017-05-13 17:15:07 UTC,"Okay, I got it working by replacing
openssl with openssl-1.0 in CryptoManager.cpp and SSLSocket.cpp
and using
export CXXFLAGS=""$CXXFLASG -I/usr/include/openssl-1.0""
export LDFLAGS=""$LDFLAGS -L/usr/lib/openssl-1.0"""
1690543,2020-10-07 21:39:18 UTC,"Hi, Is this still an issue? Changing the status to incomplete."
1690543,2020-12-07 04:17:47 UTC,[Expired for pcsc-lite (Ubuntu) because there has been no activity for 60 days.]
1690546,2017-10-24 19:07:26 UTC,Happens with me also using 17.10.
1690550,2017-06-22 04:27:32 UTC,Can you please grab the logfiles from ~/.local/share/lyrice on the system so we can see what is happening here.
1690550,2017-06-27 16:54:52 UTC,"On Jun 21, 2017 9:35 PM, ""ChrisDebenham"" <email address hidden> wrote:"
1690550,2017-09-12 04:50:25 UTC,Does the timeline work when playing videos (ie not just backgrounds)?
1690550,2017-09-12 04:51:12 UTC,ignore that last update - was from different bug
1690550,2017-09-12 05:11:33 UTC,If you start the display portion of lyricue after starting the interface does it work?
1690550,2017-09-12 05:15:43 UTC,"Ahh - I found the problem.
I was clearing status updates for things from the last 120 seconds instead of ones older than that :P
Should be fixed in next release"
1690551,2017-06-22 04:27:56 UTC,Can you please grab the logfiles from ~/.local/share/lyrice on the system so we can see what is happening here.
1690551,2017-06-27 16:55:42 UTC,"On Jun 21, 2017 9:35 PM, ""ChrisDebenham"" <email address hidden> wrote:"
1690551,2017-09-12 04:50:42 UTC,Does the timeline work when playing videos (ie not just backgrounds)?
1690554,2017-09-12 04:48:13 UTC,"Is this for all looping videos?
By any chance could you try logging into a different desktop environment and see if it occurs there (just to rule out KDE)"
1690554,2017-07-05 21:40:52 UTC,Here's a quick view of what happens. Flash happens at about 4:20.
1690554,2017-06-27 16:56:29 UTC,"On Jun 21, 2017 9:35 PM, ""ChrisDebenham"" <email address hidden> wrote:"
1690554,2017-06-22 04:27:52 UTC,Can you please grab the logfiles from ~/.local/share/lyrice on the system so we can see what is happening here
1690570,2017-05-24 00:22:37 UTC,I'm seeing this message in 16.04.
1690570,2017-05-16 23:29:46 UTC,"ive tested some more with a loop mount
it seems some file managers have the bug others dont"
1690570,2017-05-15 18:55:24 UTC,"ps: forgot.. add user to samba before restarting server
  smbpasswd -a d1"
1690570,2017-05-15 18:51:22 UTC,@ChristianEhrhardt #1 - yea its me
1690570,2017-05-15 18:19:31 UTC,apport information
1690570,2017-05-15 18:19:29 UTC,apport information
1690570,2017-05-15 18:19:25 UTC,apport information
1690570,2017-05-15 18:19:27 UTC,apport information
1690570,2017-05-15 18:19:26 UTC,apport information
1690570,2017-05-15 18:19:23 UTC,apport information
1690570,2017-05-15 18:19:21 UTC,apport information
1690570,2017-05-15 18:19:22 UTC,apport information
1690570,2017-05-15 16:41:10 UTC,"Hi,
since the dates are so close - is that you asking as well?
=> https://askubuntu.com/questions/914152/dmesg-cifs-vfs-src-file-seems-to-be-from-a-different-filesystem-type"
1690570,2017-05-15 16:47:31 UTC,The only related change is the kernel patch you already found [1].
1690570,2017-05-15 16:47:39 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1690570,2017-05-15 18:19:17 UTC,apport information
1690570,2017-05-15 18:19:14 UTC,apport information
1690570,2017-05-15 18:19:15 UTC,apport information
1690570,2017-05-15 18:19:18 UTC,apport information
1690570,2017-05-15 17:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1690570,2017-05-15 18:19:19 UTC,apport information
1690573,2017-05-13 18:17:27 UTC,"Have to give it a juju enable-ha the -n3 flag, then down controller can be removed.
Doc is missing that bit."
1690573,2017-05-13 18:18:12 UTC,Could you paste output of juju show-controller and juju show-machines?
1690573,2017-05-13 18:19:27 UTC,"Also, try juju enable-ha -n 3  and then removing the down machine."
1690573,2017-05-14 03:11:20 UTC,"I walked him through that last night. This bug is essentially that the docs
don't guide you through that well."
1690573,2017-05-15 09:04:45 UTC,"Well, if enable-ha got the system into a situation where there were three active working HA machines in the cluster, then 'remove-machine 0' *should* just do the right thing."
1690577,2017-05-13 20:39:32 UTC,A work around is to install and use a virtual frame buffer. Instructions below with others who have the same requirement:
1690579,2017-05-28 17:10:05 UTC,"Sorry for this, but I'm abandoning now. Moving on to the (paying!) Readerware 3, that does the job :-(
If things change I'd be happy to know..."
1690582,2017-05-14 13:59:48 UTC,"Thought about this some more. Since we can't really change onboard-autostart.desktop, we would handle ""org.gnome.desktop.a11y.applications screen-keyboard-enabled"" in the shell extension."
1690582,2017-05-13 22:41:11 UTC,"Hmm, onboard ships an autostart file (like caribou) does except the Exec line is set to
Exec=onboard --not-show-in=GNOME,GNOME-Classic:GNOME --startup-delay=3.0"
1690582,2017-05-14 00:37:51 UTC,"I believe it is still needed. If you remove --not-show-in you'll get both keyboards showing at the same time. Out strategy so far was to disable Onboard in GNOME until it is explicitly requested. That request can come from installing and enabling gnome-shell-extension-onboard for example, which makes sure Onboard is launched.
There is an old bug report asking to resolve the clash between the two keyboards on Ubuntu. That behavior was one of the results."
1690583,2017-05-14 13:10:57 UTC,"I see, yes, it would pick a colored icon when the icon theme wasn't Ubuntu-mono-dark."
1690586,2017-05-13 21:30:11 UTC,This change was made by a bot.
1690586,2017-05-15 20:06:27 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1690586,2017-05-23 23:34:11 UTC,"So, the issue seems to be solved in v4.12 kernel. I have been running it for a week and the issue has not occurred."
1690586,2021-01-07 08:31:30 UTC,"4.8 EOL, please feel free to open a new bug is you're still seeing this issue."
1690588,2018-01-25 09:22:08 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3702
1690588,2018-06-15 07:19:16 UTC,Can you please specify the buffer pool size used?
1690601,2018-09-26 04:42:30 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/390
1690601,2018-09-19 12:02:36 UTC,"Hi, any progress on this bug?  I now have several folks hurt by this issue."
1690601,2018-07-27 20:32:05 UTC,"Here is the status of the bug, now on both retina Mac AND retina Windows computers:
(ONLY on computers with very high native resolution)"
1690601,2017-12-22 08:54:11 UTC,"I just pushed some changes to fix the distortion effect on retina display with OSX.
Hopefully it works better now."
1690601,2018-05-03 16:49:31 UTC,"@doctor-pat, did these recent changes help? Please test version 0.18 or current beta version."
1690601,2017-05-15 18:31:52 UTC,Thank you for this.
1690601,2017-07-30 02:01:52 UTC,mirror is bad in 0.15.2 and 0.16.  Ok in 0.15.1
1690601,2017-05-15 03:22:38 UTC,Please attach screenshot
1690601,2017-07-11 16:11:55 UTC,Please check Stellarium 0.90.0.9630
1690601,2017-05-15 12:43:35 UTC,"OK here is 0.15.1:
I open in fisheye, then choose mirror distortion.  I get this which is fine:"
1690601,2017-05-15 12:48:26 UTC,Here is a larger image of just the failed distortion (had to reduce size in previous report to stay under 10 MB limit).
1690609,2017-05-14 07:24:41 UTC,This bug was fixed in the package gnome-user-docs - 3.24.2-0ubuntu1
1690619,2017-07-01 13:01:10 UTC,"First let me point out I've been a user of me-tv for several years, not involved with the project."
1690619,2017-07-02 01:53:46 UTC,"With all due respect I think when you write ""me-tv isn't designed/intended to watch, record, rewind or pause LIVE tv."" you misunderstand the request and the use case somewhat and are misrepresenting simple design as well."
1690619,2018-01-27 07:34:04 UTC,"Hi Bernd, doesn't it minimise to the tray or something?  Agree, the obsolescence of TV was truly this project's demise."
1690619,2018-05-06 19:01:12 UTC,"I started a C++ rewrite with GTK+3 and GStreamer but it became a pain so I started a fresh with Rust, which has turned out quite nicely. Television viewing is fine,now to do the EPG. Tuning assumes dvbv5-scan is present."
1690619,2018-05-07 01:17:17 UTC,Good on you Russel!
1690619,2018-05-07 08:24:26 UTC,"@bwechner Thanks. There is no release of my Me TV v3 as yet, so you have to clone the GitHub repository and run ""cargo run"". Obviously this requires a Rust and Cargo installation as well as having dvbv5-scan, gtk+3 > 3.10 and gstreamer > 1.12 installed. Currently there are only two known users, both of whom are happy with this workflow. If there were more users, some of whom couldn't work with having Cargo and Rust installed, a way of having a continuous release executable file would be found."
1690626,2017-07-13 16:20:08 UTC,It might be necessary to update via the terminal after a clean install before the app store can correctly update programs and the OS.
1690635,2017-08-28 07:14:26 UTC,"this do reproduce on my env, and need deep investigation."
1690635,2018-02-16 13:51:18 UTC,I'm facing the same problem with plugin 5.11.0
1690650,2017-08-09 21:25:22 UTC,"I have same issue with linux-generic-hwe-16.04
Hardware        : Marvell Armada 375 (Device Tree)"
1690650,2017-08-09 21:25:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690650,2018-01-23 12:01:14 UTC,"I have uploaded a fixed version adding supporting rpi 2 1.2.
https://code.launchpad.net/~rbalint/+git/flash-kernel-merge/+ref/ubuntu/devel"
1690656,2017-05-14 17:32:51 UTC,Filed upstream: https://bugs.mysql.com/bug.php?id=86314
1690656,2018-01-25 09:06:24 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1094
1690666,2018-03-12 10:38:44 UTC,I can no longer reproduce this. It's all fine.
1690676,2017-05-23 09:11:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690676,2017-06-20 07:18:30 UTC,"After the last apt upgrade, the bug does not occur. gitg is not updated, probably something else changed."
1690676,2017-06-20 08:41:53 UTC,gitg works now for me as well. Bug fixed by apt-magic
1690677,2017-05-17 17:28:02 UTC,"You should attach your fstab files before and after. How else would this be fixed. And this is clearly upstream issue, launchpad is not really a good palce to report it. Report it to bugs.kde.org"
1690685,2020-07-31 14:11:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690685,2020-07-31 15:02:56 UTC,"Thanks for the info and workaround macg3, i had the same issue with .default being ignored over appletalk."
1690685,2017-05-14 23:57:11 UTC,It appears that there have been several unreleased commits to netatalk's 2.2 branch after the release of 2.2.5:
1690689,2017-06-30 13:38:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690693,2017-05-16 04:55:50 UTC,"Reviewed:  https://review.openstack.org/464292
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=afe207212dbbf9f1585cf362701ad6475f1c6d2c
Submitter: Jenkins
Branch:    master"
1690693,2017-06-09 15:29:34 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.
1690700,2017-05-18 11:53:17 UTC,"Hi,"
1690700,2017-05-20 00:56:47 UTC,I am a new user.  How do I get the logs you request?
1690706,2017-05-17 14:08:38 UTC,I would try making a temporary directory under $(CURDIR)/debian/ and export XDG_RUNTIME_DIR=that-directory. Make sure to remove it in clean too.
1690706,2017-05-17 17:28:03 UTC,"Iain, that didn't seem to help when I tried it."
1690706,2017-05-17 20:36:23 UTC,It does help. It changes the error message to:
1690706,2017-05-23 11:34:21 UTC,It occurs to me that you might be able to do something like
1690719,2017-08-14 16:21:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690719,2017-08-14 16:26:01 UTC,Upstream this issue: https://bugzilla.gnome.org/show_bug.cgi?id=745032
1690719,2018-03-29 06:12:25 UTC,"Subscribers: While this is the bug that started the investigation into gnome-shell smoothness, it's actually not the main issue."
1690719,2020-08-21 04:57:26 UTC,In progress upstream:
1690719,2020-10-09 03:22:57 UTC,Also in progress here:
1690719,2021-02-09 09:25:45 UTC,Marco says he is trying to get the above upstream fix into Ubuntu 21.04...
1690719,2021-02-09 09:26:41 UTC,I actually haven't had any trouble with this bug in a long time. So for me the only verification required would be to see the patch is present.
1690719,2021-02-09 16:19:24 UTC,"On Ubuntu 20.04.2 LTS problems are not happening, it seems."
1690729,2017-07-14 12:12:13 UTC,This bug was fixed in the package libvirt - 3.5.0-1ubuntu1
1690729,2017-05-15 06:20:34 UTC,"Also mod/long term this patch should become an upstream configure option.
That would:
1. allow to rely on it more
2. drop the delta patching the file
3. ease maintenance as we currently have to modify a lot of testcases (those would depend on the config then and change accordingly)"
1690740,2017-05-15 07:25:40 UTC,Changing the component for this bug.
1690740,2017-05-16 13:57:12 UTC,"Sorry, I am not quite sure what you are saying here."
1690759,2017-05-16 19:42:03 UTC,Adrian:
1690759,2017-05-31 02:43:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690771,2018-01-18 08:18:41 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1978
1690771,2017-05-31 06:32:48 UTC,The my.cnf file
1690771,2017-05-31 06:32:07 UTC,The output of show global variables ...
1690771,2017-05-31 06:34:05 UTC,I do not have a smaller data set which I was able to use for reproducing this bug ...
1690771,2017-05-31 04:32:43 UTC,Unfortunately I could not reproduce after loading the sql file and running the queries in your example. Can you share your my.cnf and output of 'show global variables' (please attach as text files for easier reading). Of course if you can provide a simpler reproducible case on smaller dataset that would be great as well.
1690771,2017-05-16 12:27:56 UTC,"And some more infos:
This seems to be related somehow to the numbers of entries ... see the following tries:"
1690771,2017-05-16 09:55:32 UTC,Got more info after finding a query which is syntactically right but triggers a ERROR 1032 (HY000) when executed.
1690771,2017-05-31 06:27:50 UTC,"Hello Jericho, thanks for your response.
Here is the my.cnf of the live system which crashes:"
1690791,2017-07-27 19:10:25 UTC,https://review.openstack.org/#/c/470440/
1690791,2017-07-27 19:29:34 UTC,"I think this mostly boils down to us continuing to make more and more conscious decisions about the difference in how we want to handle handoff partitions vs. mis-placed partitions.  A mis-placed partition (part moved from rebalance, non-primary & non-handoff) perhaps should not *immediately* move to handoff if a primary rejects it for e.g. concurrency... but the longer a part sits misplaced the more chance there is for reclaim age related dark data issues."
1690791,2017-09-10 23:28:25 UTC,"Change abandoned by Pavel Kvasnička (<email address hidden>) on branch: master
Review: https://review.openstack.org/470440
Reason: This issue should be solved by monitoring rsync log (something like I/O error on drive ...). When we focus on there errors then we don't need this patch."
1690808,2019-07-12 16:14:37 UTC,I have just pushed a fix for this in Debian unstable (gnome3-emblems 0.3.1-6).
1690812,2017-07-06 09:08:27 UTC,"Michael, Thanks for looking into this.
I submitted a tiny patch based on what you wrote in comment#4.
I'll test both this and the patch submitted against bug 1681623 and report my findings."
1690812,2018-07-04 10:53:53 UTC,"Change abandoned by Nir Magnezi (<email address hidden>) on branch: master
Review: https://review.openstack.org/480919"
1690812,2017-07-13 13:49:57 UTC,"@Michael, you were right.
apparently, my devstack used a cached amphora image without this fix.
As soon as I generated a new one, test_session_persistence worked with loadbalancer_topology = ACTIVE_STANDBY"
1690812,2017-07-12 14:07:35 UTC,Can you confirm you have a newly built image with the fix from: https://review.openstack.org/#/c/455569
1690812,2017-07-06 09:02:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/480919"
1690812,2017-07-11 12:06:57 UTC,Looks like the fix for bug 1681623 did not resolve this bug.
1690812,2017-07-05 23:02:29 UTC,The first issue I see is a python 3 bug:
1690812,2017-07-04 12:41:31 UTC,"Debugging shows that this is indeed an issue, probably in how Octavia configures HAProxy."
1690812,2017-05-15 12:58:53 UTC,More investigation logs
1690812,2017-05-15 12:58:23 UTC,Ubuntu amphora
1690812,2017-07-05 23:13:11 UTC,"Issue two, with the peers being incorrect.  I think you hit the bug reported here: https://launchpad.net/bugs/1681623"
1690817,2017-05-15 14:00:13 UTC,This change was made by a bot.
1690817,2017-06-06 16:21:03 UTC,"Can you interpret the comment: This change was made by a bot. I don't know what you mean. Does ""This change"" refer to the bug report or to something else? I suppose 'bot' refers to some automatic software program, but I don't know."
1690817,2017-07-01 22:14:30 UTC,"Not sure if using dkms, but if so may be related to bug 1515513"
1690832,2017-06-14 04:34:18 UTC,"You are right, I could reproduce it. Since Shutter is not maintained any more I would advise you to use the censor tool (directly above the pixelize tool)."
1690832,2017-06-07 23:33:53 UTC,Please note that using data-dependent operations in an attempt to obfuscate data is extremely dangerous:
1690832,2017-06-13 19:45:07 UTC,Unsubscribing ubuntu-security-sponsors since there is nothing here to sponsor.
1690832,2017-06-07 09:10:21 UTC,I tried to reproduce it but couldn't... Which version of imagemagick are you using?
1690832,2017-06-07 06:50:29 UTC,Nobody cares?
1690832,2017-06-07 10:14:24 UTC,All packages installed with 'magick' in it's packagename are version
1690836,2017-05-15 15:16:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690836,2017-05-17 21:54:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu
better. I appreciate the quality of this bug report and I'm sure it will be
helpful to others experiencing the same issue."
1690836,2017-05-17 21:56:42 UTC,"I believe this is the upstream project:
https://github.com/tgraf/libnl"
1690836,2017-05-18 06:39:45 UTC,"Joshua,"
1690836,2017-05-18 15:25:31 UTC,"@filofel, my bad yes you are right. This seems fixed in later versions and as such this requires an SRU."
1690836,2017-05-18 15:26:30 UTC,"We also need to confirm that this is fixed in Artful. Given it is fixed in Debian stable it probably is, but confirming that it is fixed in the latest development release will be required for the SRU."
1690836,2018-06-27 11:32:08 UTC,Artful
1690836,2018-06-27 11:34:29 UTC,Xenial seems affected
1690836,2018-06-27 11:44:39 UTC,"X: 3.2.27-1ubuntu0.16.04.1
A: 3.2.29-0ubuntu3"
1690836,2018-06-27 11:44:56 UTC,Needs debugging what the actual change is that could be considered for backporting.
1690845,2017-05-17 02:28:33 UTC,The patch already at https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/service-hyper-uuid-in-api
1690845,2017-05-17 12:28:26 UTC,"Alex, I don't actually see a patch up for this yet."
1690846,2017-05-15 16:28:41 UTC,This is affecting only xenial and yakkety
1690846,2017-05-18 21:31:17 UTC,"There is no information which meets the ""Test Case"" criteria of the Ubuntu SRU process. Given the large laundry list of changes, how do plan on testing that this works in Yakkety and Xenial and that there are no regressions?"
1690846,2017-05-22 14:47:59 UTC,"Borg has, broadly speaking, relatively few regressions. In the months since 1.0.9/10 I believe only one regression was reported (related to UNC paths on the not officially supported Cygwin platform, w/ workaround) and one or two minor bugs in some of the new functionality."
1690846,2017-05-31 06:51:00 UTC,"@Brian Murray, do you want me to check if the CVEs are fixed? Otherwise the testsuite creates directory files, backups them on various different filesystems, and recovers them after checking checksums of files and a lot of more stuff."
1690846,2017-06-13 19:25:15 UTC,"Do you think this qualifies as a ""New upstream microrelease"", https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases, if so then I'd expect the bug description to contain information about the upstream development process and how they test releases per the wiki page."
1690846,2017-07-06 14:58:37 UTC,(reuploaded the same file)
1690846,2017-09-01 14:34:36 UTC,"Hello, ping?"
1690846,2017-09-05 23:14:18 UTC,Could you respond to my previous comment?
1690846,2017-09-06 02:02:51 UTC,"It's good that this has a test-suite, and autopkgtests running it. Does it test the compatibility against archives created by previous versions?"
1690846,2017-05-15 16:25:47 UTC,Subscribing security team because of the CVEs
1690847,2018-11-27 01:10:47 UTC,"Change abandoned by Kaifeng Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/497156"
1690847,2017-08-24 09:02:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/497156"
1690847,2017-08-23 09:29:49 UTC,I have not had the time to begin this work as it needs a spec writing to cover the changes. So this is free for someone else to write the spec
1690847,2017-08-23 06:33:41 UTC,"Hi sam, are you working on this?
I prefer the first way, providing a new verb to move node from active to manageable.
it looks like a new 'unadopt failed' state is required to differentiate with 'error' if tearing down failed."
1690847,2017-05-16 17:30:15 UTC,"I'm quite in favour of this. But as it's an API and state machine addition, please write a spec for it."
1690847,2017-08-23 11:49:43 UTC,"thank you sam, i can work on this"
1690856,2017-05-18 09:10:07 UTC,"This is no longer present in the current dev version of Mnemosyne, and perhaps also in 2.4.1."
1690860,2018-08-18 12:45:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690860,2018-08-18 13:04:19 UTC,my syslog just says:
1690864,2017-05-24 18:23:55 UTC,"Ok, thanks dude!"
1690864,2017-07-28 08:36:37 UTC,I moved the project to Github. Please continue this discussion there: https://github.com/kgraefe/pidgin-hide-chat-on-join/issues/6
1690864,2017-05-22 09:36:00 UTC,Do not report it to EionRobb yet. I will have a deeper look first.
1690864,2017-05-20 20:17:51 UTC,"Hi dude...sorry for delay...I tried with IRC plugin on freenode and works great!...it seems the problem its on EionRobb's plugins like Hangouts, Discord, SkypeWeb...should I report it to him?"
1690864,2017-05-16 06:32:52 UTC,I had a quick test at seems to be working for me. Can you elaborate on your setup?
1690864,2017-05-17 19:14:19 UTC,I tried it on another Notebook (also with Windows 10 Pro x64 build 1703 and pidgin v2.12.0 ..but same results...maeby some depedency was losted/dropped over the time on newest version of pidgin?
1690864,2017-05-16 17:03:42 UTC,Forgot to say that I also cleaned all pidgin data from (Program Files\Pidign and %APPDATA%\.purple before reinstall it to do the test on fresh installation.
1690864,2017-05-16 16:51:07 UTC,"Yes of course...I'm using Windows 10 Pro x64 build 1703...Tested on a fresh pidgin pidgin-2.12.0-offline.exe installer with using only pidgin-hide-chat.dll (v1.0 downloaded from your page) and skypeweb plugin 1.4 (https://github.com/EionRobb/skype4pidgin/releases), you can also test with orthers protocols like Hangouts plugin or Discord...the results are the same."
1690864,2017-05-18 09:35:02 UTC,Can you check again with a protocol that is shipped with Pidgin? I used IRC for that (no registration needed).
1690882,2019-09-19 14:48:14 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1690883,2017-05-15 18:21:03 UTC,I thought that rack controllers can already post notifications to the region controllers ? This was the whole point of the notifications work...
1690883,2017-05-15 18:45:03 UTC,"The point was to allow the region to post messages. I do not believe a message can come directly from the rack controller. I message can be created by the region based on another action or observation by a rack controller, but I don't believe there is a direct RPC to create a notification."
1690883,2019-09-19 14:48:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1690884,2017-05-15 18:20:15 UTC,"It seems you are missing apparmor stuff in your host system to allow the usage, or you have upgraded your apparmor recently, or isc-dhcp on your host machine that could be the culprit."
1690884,2017-05-15 18:27:56 UTC,That message is always show the postinst script handles that failure correctly.
1690884,2017-05-15 18:29:01 UTC,"I have the `maas-dhcp` package installed on the host system, as required. That pulls in the `isc-dhcp-server` package, but it's not running on the host system. (only in the container via MAAS.)"
1690890,2017-06-13 17:32:53 UTC,"Reviewed:  https://review.openstack.org/465024
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2c5ee22610d13e00a1f1f54e8764009f4801c3f
Submitter: Jenkins
Branch:    stable/ocata"
1690890,2017-06-08 21:52:21 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1690890,2017-06-19 12:46:01 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1690890,2017-05-15 22:15:25 UTC,"Reviewed:  https://review.openstack.org/464726
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=902b7bf6f5425824a0661b8e4beac4a894749c03
Submitter: Jenkins
Branch:    master"
1690890,2017-05-15 18:55:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/464726"
1690890,2017-05-16 10:37:07 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/465024"
1690898,2017-05-15 16:34:33 UTC,Good evening.
1690898,2017-05-18 19:12:17 UTC,"Thanks, this was very informative."
1690898,2019-12-04 12:11:22 UTC,"This has to be fixed in Debian, and will likely require a wrapper of some kind."
1690903,2017-05-15 20:00:13 UTC,This change was made by a bot.
1690937,2020-06-02 19:57:12 UTC,"As was discussed on the PTG, we decided to close this RFE for now. Feel free to reopen it if there will be valid use case for that and if You will want to work on that. Then we can discuss it again in the drivers team meeting."
1690937,2020-06-02 15:04:09 UTC,"I may say this should make it 0.0.0.0/0 work for ml2 ovs driver:
https://review.opendev.org/#/c/712632/"
1690937,2017-07-18 13:47:47 UTC,"Ihar, we want spoofing protection without the IP and only the MAC address. So in the case of 0.0.0.0/0, all IPs are acceptable only if the MAC the IP is associated with is in the list of configured MAC addresses."
1690937,2017-07-13 23:05:26 UTC,"Sorry, this RFE got triaged too quickly, we need clarification on use case here."
1690937,2017-07-14 01:18:35 UTC,"0.0.0.0/0 works as far as I can tell for IP packets (though it doesn't allow non-IP packets, so there's that)."
1690939,2020-07-01 21:21:20 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1690947,2017-05-27 23:59:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690947,2017-06-25 03:13:47 UTC,"digikam was freezing on me, I had my db and collection on a share on the local machine.
So I am trying to put them in my local home folder.
Ubuntu 17.04 and digiKam 5.4
I uninstalled DigiKam and reinstalled
When I start digikam, the configure window comes up, I click ""add collection"" and it freezes.
Here is the terminal output.
rick@Dell-9010:~$ digikam
digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
   Type:                     ""QSQLITE""
   DB Core Name:             ""/home/rick/digiKamDB/digikam4.db""
   DB Thumbs Name:           ""/home/rick/digiKamDB/thumbnails-digikam.db""
   DB Face Name:             ""/home/rick/digiKamDB/recognition.db""
   Connect Options:          """"
   Host Name:                """"
   Host port:                -1
   Internal Server:          false
   Internal Server Path:     """"
   Internal Server Serv Cmd: """"
   Internal Server Init Cmd: """"
   Username:                 """"
   Password:                 """""
1690947,2017-07-09 15:26:47 UTC,Also reported upstream: https://bugs.kde.org/show_bug.cgi?id=378873
1690952,2017-05-15 23:39:20 UTC,"Another issue (maybe related, maybe not) is that Inkscape fails to render the marker (see attached screenshot)."
1690952,2017-05-16 00:46:39 UTC,"@Tavmjong: Subscribing you, as I'm not yet 100% sure I correctly understood the spec... maybe you could confirm if this is an issue or not?"
1690952,2017-05-16 13:34:29 UTC,The size of the rectangle is irrelevant. It does not establish a viewport size. The marker is being rendered by all browsers and Inkscape without scaling due to a view port. The inconsistency is that Inkscape is not properly clipping the marker. The browsers (Opera/Chrome/Firefox) clip the marker to a 3x3 square (or 300x300 square after the <svg> viewBox and 10px stroke width is accounted for). This can be seen by adding a stroke to the rectangle in the marker. All browsers and Inskcape give the same rendering when 'overflow' is set to 'visible' on the <marker> element.
1690959,2017-05-18 20:54:57 UTC,"Seems this is a cairo limitation. As PS/PDF do not render square linecaps on zero-length paths (as the direction would be undefined) cairo followed this behavior, see [1]."
1690959,2020-02-26 04:52:03 UTC,Closing as part of great bug migration
1690961,2019-05-25 04:39:57 UTC,This will be tackled when we look at https://wiki.mahara.org/wiki/Developer_Area/Specifications_in_Development/Page_layout_revision in phase 2 outsourcing the metadata to the modal.
1690964,2017-05-16 04:19:07 UTC,Whatever Gnome has done for years is not the point. I'm talking about a smooth transition and easy discoverability for current/former Unity7 users. But yeah discoverability is fine per the above methods.
1690964,2017-05-16 02:57:25 UTC,This is basically intentional for a couple reasons.
1690964,2017-05-16 03:16:48 UTC,"Thanks, but that does sound strange...
  Personal: 2 rows
  Hardware: 2 rows
  System: Limited to 1 row?"
1690964,2017-05-16 03:24:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1690964,2017-05-16 03:59:09 UTC,Personal is supposed to be just one row too but we need to fix bug 1631750 first and then drop language-selector-gnome from the default install.
1690964,2017-05-16 12:40:50 UTC,I feel it's more important that we integrate well in the new desktop than just copying something we did before. But I'll add the tag so that it shows up on the list of bugs we are tracking for 17.10 and so we can see what the rest of the Desktop Team wants to do.
1690967,2019-10-07 07:51:35 UTC,"FWIW, I ended up writing a wrapper for dput
https://github.com/mwhudson/dput-wrap that I still use daily. As the README
says, it might make sense to add this to dput-ng."
1690967,2019-10-04 19:34:59 UTC,"This would be a slick feature to add to dput itself, it already has a --lintian and --check-version, but those options don't look like they'd do this."
1690967,2017-08-28 11:44:56 UTC,"I wonder if we could have a ""git ubuntu dput [treeish]"" wrapper? It could lint, then build the source, then sign and upload. If the lint fails (even if just warnings), then it would fail by default and require a --force to succeed. Then the functionality in lint should be sufficient for this use case."
1690967,2017-08-28 11:26:37 UTC,After making a series of embarrassing mistakes trying to upload versions of docker for SRU I hacked this up: https://gist.github.com/mwhudson/616499edb1191bd99c987bbbd8781ce9
1690967,2017-08-02 16:42:35 UTC,4) Check branch name matches changelog target.
1690997,2017-06-04 23:45:45 UTC,Do you mean that fullstack test is not enough?
1690997,2017-06-01 06:32:53 UTC,I'm talking about scenario test.
1690997,2017-05-31 13:20:38 UTC,We already have some tests for security group[1]. Isn't it enough?
1691004,2017-05-31 13:50:12 UTC,Do you want scenario test? Fullstack test is enough?
1691018,2017-08-20 14:54:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691025,2020-06-14 13:05:23 UTC,"I couldn't install xpra because it depends on `xserver-xorg-core`. When trying to install that I saw it wants to remove lots of packages. Good thing I decide to do a little more research because if I went on with fingers crossed, I would probably have gotten myself into the same broken Linux situation. Please also think about the people who don't do some more research and break their system."
1691025,2019-04-06 15:19:37 UTC,xpra in 18.04 depends on xserver-xorg-video-dummy and xserver-xorg-input-void.
1691025,2017-05-23 19:08:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691025,2017-05-23 20:16:55 UTC,"I run Ubuntu 16.04 LTS on iMac. The problem appears when I try to install xpra from the official Ubuntu repo, the installer wants to delete my desktop environment which is MATE."
1691025,2017-08-01 10:42:07 UTC,You can work around this problem by running:
1691025,2017-10-31 18:43:11 UTC,This seems like a pretty easy change to depend on |'d xserver packages. Any idea if it actually works if so? If I build the package in a PPA will someone test it?
1691025,2017-10-31 18:49:00 UTC,For the sake of completeness this is what is removed:
1691025,2019-02-21 18:27:21 UTC,"I just ran into this with 18.04.2, which has HWE out of the box."
1691025,2019-02-25 23:11:05 UTC,FWIW the author of xpra recommends you use their repository instead of the Ubuntu repository. See
1691025,2019-03-12 15:03:39 UTC,A bit more discussion if you are using the xpra repo (and upgrading to hwe on bionic rather than a fresh install):
1691025,2020-04-15 11:10:00 UTC,Hi! Do you plan to release a fix for this for 18.04? It's already been fixed in xpra over a year ago.
1691030,2017-05-16 07:27:01 UTC,"In the latter screenshot, there is no headbar."
1691030,2017-05-22 14:38:10 UTC,"I can confirm this, I think it only happens for applications that are not using client side decorations like Gimp, Inkscape or Firefox."
1691030,2017-05-22 14:54:37 UTC,"Yes, that's right."
1691030,2017-05-22 15:08:35 UTC,"This issue was already posted:
https://github.com/elementary/screenshot-tool/issues/4"
1691039,2017-05-19 10:05:39 UTC,The question is: where does the 2.5 gig come from?
1691039,2017-05-19 10:19:29 UTC,"It is from local.conf
max_memory = 4000"
1691039,2017-10-11 08:24:00 UTC,Wasn't the issue here that there was this reserved_host_memory_mb variable set to some value?
1691039,2017-10-11 08:44:41 UTC,May be you are right at this time of bug the reserved_host_memory_mb parameter change that is been added to over conf file has not been taken...
1691051,2017-05-16 08:45:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691072,2017-05-16 10:35:11 UTC,"I've created this branch, removing the data_files that are placed in restricted places."
1691072,2017-05-16 10:35:20 UTC,https://code.launchpad.net/~joeborg/curtin/noroot
1691072,2017-05-16 14:11:21 UTC,Is this a python venv setup? How do I produce the error you're seeing ?
1691072,2017-05-16 14:24:43 UTC,"Hey Ryan,"
1691073,2018-01-20 08:08:09 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1443
1691073,2017-05-16 10:28:58 UTC,Can you please provide the command line you are using to take a backup and your my.cnf?
1691073,2017-05-16 10:30:03 UTC,"Crash in the bug you mentioned happens during prepare, yours seems to during the backup, so they are unlikely the same."
1691073,2017-05-17 02:21:52 UTC,"$ cat /etc/mysql/my.cnf
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - ""/etc/mysql/my.cnf"" to set global options,
# - ""~/.my.cnf"" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html"
1691073,2017-05-17 02:29:13 UTC,"> Can you please provide the command line you are using to take a backup
"
1691073,2017-05-17 08:58:37 UTC,"Sure, it makes sense to upgrade. I don't see anything unusual and the stack trace unfortunately doesn't give much information. Does xtrabackup crash like this all the time or just occasionally?"
1691075,2019-06-29 01:30:10 UTC,"Reviewed:  https://review.opendev.org/665494
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=ff4459ed6bcaa26bc4df9873577ccad9578a89fc
Submitter: Zuul
Branch:    master"
1691075,2019-02-04 17:48:01 UTC,"FWIW, the trouble is https://github.com/openstack/swift/blob/2.20.0/swift/obj/server.py#L1374-L1377 -- setting replication_concurrency = 0 in the [app:object-server] section of you object-server.conf should allow it to start... but we still need to figure out how to get that BoundedSemaphore to all the subprocesses that may be forked."
1691075,2019-07-11 23:20:08 UTC,"Reviewed:  https://review.opendev.org/668007
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=aca7474ca3c7bba54473fca35b6d88a3a1efdca4
Submitter: Zuul
Branch:    feature/losf"
1691075,2019-02-04 12:59:28 UTC,"I got similar issue with py3.7:
Feb 04 12:54:43 f29-dev-02 systemd[1]: Started Speedling sl-s-obj.service.
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]: Traceback (most recent call last):
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/usr/local/bin/swift-object-server"", line 7, in <module>
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     exec(compile(f.read(), __file__, 'exec'))
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/opt/stack/swift/bin/swift-object-server"", line 27, in <module>
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     **options))
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/opt/stack/swift/swift/common/wsgi.py"", line 1037, in run_wsgi
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     loadapp(conf_path, global_conf=global_conf)
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/opt/stack/swift/swift/common/wsgi.py"", line 402, in loadapp
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     ctx = loadcontext(loadwsgi.APP, conf_file, global_conf=global_conf)
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/opt/stack/swift/swift/common/wsgi.py"", line 386, in loadcontext
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     global_conf=global_conf)
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/usr/local/lib/python3.7/site-packages/paste/deploy/loadwsgi.py"", line 302, in loadcontext
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     global_conf=global_conf)
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/usr/local/lib/python3.7/site-packages/paste/deploy/loadwsgi.py"", line 326, in _loadconfig
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     return loader.get_context(object_type, name, global_conf)
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/opt/stack/swift/swift/common/wsgi.py"", line 68, in get_context
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     object_type, name=name, global_conf=global_conf)
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/usr/local/lib/python3.7/site-packages/paste/deploy/loadwsgi.py"", line 415, in get_context
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     defaults = self.parser.defaults()
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/usr/local/lib/python3.7/site-packages/paste/deploy/loadwsgi.py"", line 74, in defaults
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     defaults[key] = self.get('DEFAULT', key) or val
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/usr/lib64/python3.7/configparser.py"", line 799, in get
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     d)
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/usr/local/lib/python3.7/site-packages/paste/deploy/loadwsgi.py"", line 101, in before_get
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     value, defaults)
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:   File ""/usr/lib64/python3.7/configparser.py"", line 394, in before_get
Feb 04 12:54:44 f29-dev-02 swift-object-server[9565]:     self._interpolate_some(parser, option, L, value, section, defaults, 1)
Feb 0..."
1691075,2019-07-22 20:15:20 UTC,This issue was fixed in the openstack/swift 2.22.0 release.
1691084,2017-05-16 15:05:53 UTC,"may be you need to run, 'zun-db-manage upgrade'"
1691084,2017-05-28 00:01:05 UTC,"I am going to mark this bug as ""Imcompleted"". Will revisit the status after receiving response to @Pradeep's question."
1691105,2020-04-26 09:00:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691105,2020-04-26 09:23:54 UTC,"Yes, adding ""kio-extras"" to the ""depends"" list would solve those puzzling ""samba shares stopped working"" problems (and other weird ones) people are finding.
For example:
    - https://bugs.kde.org/show_bug.cgi?id=393983
    - https://bugs.kde.org/show_bug.cgi?id=379897
    - The description of this bug report."
1691107,2017-05-16 15:43:38 UTC,"It happened again, same situation. So it is reproducible."
1691108,2017-12-05 09:20:46 UTC,"Also faced with this issue on ""mount"" rules.
I noticed, that issue connected to variables that have slash (""/"" symbol). For example:"
1691108,2018-01-14 14:45:12 UTC,"I finally found the issue.
If I change the @{HOMEDIRS} and @{HOME} to
@{HOME}=@{HOMEDIRS}/@{USER}
@{HOMEDIRS}=/home"
1691109,2019-03-20 16:03:39 UTC,"I marked it as ""Incomplete"" since the bug reported is quite old and it's not clear what should be done at this point."
1691109,2017-10-23 14:20:33 UTC,@paelzer
1691109,2017-10-17 20:26:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691109,2017-07-10 17:49:31 UTC,"It appears that the recent qemu packages released for 16.04 set the machine type to ""pc-i440fx-zesty"" instead of ""pc-i440fx-xenial"".  If you override this and make it use ""pc-i440fx-xenial"" instances boot again."
1691109,2017-10-11 07:24:35 UTC,Thanks Thomas for redirecting this to us.
1691111,2017-09-26 08:57:33 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/507434"
1691111,2017-08-11 02:50:29 UTC,This issue was fixed in the openstack/keystone 12.0.0.0rc1 release candidate.
1691111,2017-08-01 22:32:00 UTC,"Reviewed:  https://review.openstack.org/465530
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=820d9d9a84f2a65677a2654b36a4677eaeba59fc
Submitter: Jenkins
Branch:    master"
1691111,2018-07-27 07:41:28 UTC,This issue was fixed in the openstack/keystone 11.0.4 release.
1691111,2017-05-17 12:03:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465530"
1691111,2017-09-27 18:20:20 UTC,"Reviewed:  https://review.openstack.org/507434
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=e1a94f39edb6cf777c71c7a511476b1e60436ab9
Submitter: Jenkins
Branch:    stable/ocata"
1691111,2017-06-09 16:50:17 UTC,"A bug was opened saying that the ec2 stuff in keystone is completely untested [0]. I'm pretty sure the ec2 stuff in contrib pre-dates my involvement on the project, but I'm pretty sure there was never testing for it."
1691112,2018-01-07 00:06:34 UTC,This is no longer an issue in 17.10 since Ubuntu Online Accounts has been replaced.  Can we close this bug?
1691112,2017-05-18 11:15:58 UTC,"Thanks Adam, that's more likely and e-d-s/u-o-a issue than gnome-calendar one but would be nice to see investigated since it's indeed quite a frustrating user experience"
1691115,2017-05-18 09:07:07 UTC,"> Do you mean this?
> alex@Lenovo $ export GTK_IM_MODULE=multipress libreoffice
Just this should already do:
GTK_IM_MODULE=multipress libreoffice
I then picked writer and the number pad would switch through multiple letters.
Configuration is in
/etc/gtk-3.0/im-multipress.conf
"
1691115,2017-05-18 10:58:28 UTC,I'll have a look at keysym_rule(s) and see if I can use them.
1691115,2017-05-18 10:49:39 UTC,multipress is installed:
1691115,2017-05-18 08:48:24 UTC,">>There not going to be removed, though.
s/There/They're/
>if this approach is deprecated, probably we'd better use the
>suggested, current approach. Which is what?
I had dynamic generation of labels in mind when I wrote that. That's what is already happening for most keycode keys across all of Onboard's layouts. Whenever the Xkb keymap changes, the labels change and that is what I think should happen for input methods too. I mentioned  getting them from libhangul before.
"
1691115,2017-05-18 05:37:27 UTC,@marmuta
1691115,2017-05-17 23:34:16 UTC,"> I was unable to use it with LibreOffice 5.x, instead.
Does it work with Onboard and multipress? It does here.
GTK_IM_MODULE=multipress libreoffice
then press any key on the number pad
"
1691115,2017-05-18 07:14:44 UTC,"Won symbol (""₩"") working (more or less...)"
1691115,2017-05-17 07:48:32 UTC,Complete Hangul layout
1691115,2017-05-16 16:37:14 UTC,Just to add the previous screenshot as an attachement...
1691115,2017-05-16 15:24:35 UTC,"Here a first (still incomplete) prototype, just to have something to play with and something to push on the discussion."
1691115,2017-05-16 15:05:32 UTC,"Looking forward to your layout, alexbottoni."
1691115,2017-05-17 23:27:34 UTC,"I had a quick look, will have more time on the weekend."
1691121,2017-08-31 14:20:38 UTC,"Campbell, what version of OpenStack do you use? We'd got a similar bug [1] in the past."
1691131,2017-05-20 10:03:03 UTC,"Change abandoned by Daniel Gonzalez Nothnagel (<email address hidden>) on branch: master
Review: https://review.openstack.org/465653
Reason: As discussed in the nova meeting, this is not the right fix for the problem.
Therefore I'm abandoning this patch."
1691131,2017-05-17 15:52:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465653"
1691131,2017-06-23 12:56:37 UTC,"There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments."
1691134,2017-06-11 03:46:22 UTC,"Hi, yes, the flow i was thinking about is as you described"
1691134,2017-07-01 01:02:29 UTC,"I am struggling to understand the need for this proxy, so I'm going to clarify a few things and some questions."
1691134,2017-06-06 08:50:39 UTC,"HI. Currently, the lb-mgmt-net use to server side to send rest request to amp agents, and also health check something. I just confuse the implementation details as you said."
1691141,2017-05-23 19:46:37 UTC,"Reviewed:  https://review.openstack.org/465105
Committed: https://git.openstack.org/cgit/openstack/glance_store/commit/?id=a8eec9f17c6bd7cf8d4dafea54f89d306d2cab63
Submitter: Jenkins
Branch:    stable/ocata"
1691141,2017-05-16 16:09:58 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/465105"
1691148,2018-01-02 16:49:35 UTC,We should make sure that snap/snapd detect and warn.
1691148,2017-05-16 15:46:58 UTC,Before we are on a LTS enablement kernel everything that uses snap execution environment will fail. This includes installing the core snap and running the configure hook.
1691151,2017-05-16 19:23:55 UTC,Identified that 3.19.0-80-generic works but 4.2.0-18-generic does not work.
1691152,2017-05-31 16:37:46 UTC,No SRU is going to be done for linux-azure this cycle.
1691158,2017-05-17 10:30:53 UTC,I should also mention that the symptom started recently. I am not sure exactly when but it did not occur before the last 3 or so kernel updates.
1691158,2017-05-16 16:12:47 UTC,root@riposo:~/works# fdisk /dev/sda
1691158,2017-05-16 16:21:07 UTC,As e.g. kernel upgrades fail I explicitely umount /dev/sda5 in rc.local
1691158,2017-05-16 16:27:47 UTC,*Correction*: As e.g. reboots after a kernel upgrade fail I explicitely umount /dev/sda5 in rc.local
1691158,2017-05-16 16:59:45 UTC,/boot != EFI partition. You should not be placing kernels in teh UEFI partition.
1691158,2017-05-17 10:04:36 UTC,"""/boot != EFI partition. You should not be placing kernels in teh UEFI partition.""
My root filesystem (sda10 in this case) contains the kernels, the sda5 EFI partition does not.
My sda10 partition does not contain a /boot/efi directory, so I created one and rebooted: sda5 is still mounted on /boot.
I then renamed that directory to /boot/EFI and rebooted: sda5 is still mounted on /boot."
1691158,2017-05-17 10:16:02 UTC,"Now imagine what happens when sda5 is mounted ""behind my back"" on /boot and a new kernel is installed by the Software Updater: the new kernel ends up on sda5 and the /vmlinuz and /initrd.img ""system"" symlinks point the new files.
On a reboot Grub does not mount sda5: the ""system"" symlinks point to non-existing files and Grub fails ..."
1691158,2017-05-17 12:25:03 UTC,A fuller sosreport would be helpful to see what is going on. ($ sudo sosreport)
1691158,2017-05-17 14:07:42 UTC,"It looks like /run/systemd/generator/-.mount is the culprit.
However, whatever I try issuing ""sudo systemctl mask -.mount"" fails with a ""systemctl: invalid option -- '.'"" error message."
1691165,2017-05-16 16:29:01 UTC,Just another quick note.  I had several items selected at the same time....approx 12.
1691165,2019-12-11 03:34:21 UTC,"Hhmmm....  Declining to migrate, and closing."
1691174,2017-05-16 17:48:31 UTC,apport information
1691174,2017-05-16 17:48:30 UTC,apport information
1691174,2017-05-16 17:48:32 UTC,apport information
1691174,2017-05-16 17:48:22 UTC,apport information
1691174,2017-05-17 16:16:50 UTC,"My system worked correctly with the mainline 4.4.68 kernel, so it appears to be fixed upstream."
1691174,2018-01-13 08:43:24 UTC,I have similar bug with 4.13.0-25-generic.
1691174,2017-05-16 17:48:28 UTC,apport information
1691174,2017-05-17 11:31:51 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1691174,2017-05-16 17:48:27 UTC,apport information
1691174,2017-05-16 17:48:17 UTC,apport information
1691174,2017-05-16 17:48:24 UTC,apport information
1691174,2017-05-16 17:48:23 UTC,apport information
1691174,2017-05-16 17:48:20 UTC,apport information
1691174,2017-05-16 17:48:19 UTC,apport information
1691174,2017-05-16 17:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1691174,2017-05-16 17:48:25 UTC,apport information
1691178,2019-04-18 11:48:25 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: master
Review: https://review.openstack.org/465160
Reason: im going to abandon this as it now work if you use a cpu_model that is supported by the mttcg backend which is enable by default on new enough qemu versions.
see
https://review.openstack.org/#/c/652197/
as an example of a ci job that uses that fact"
1691178,2017-05-16 18:35:53 UTC,addtional logs
1691178,2017-05-16 16:40:19 UTC,i will submit a partial fix for this shortly for the numa/hugepage case.
1691178,2017-10-13 00:37:25 UTC,Link to gerrit manually...
1691179,2018-08-12 15:20:04 UTC,"Hmm, motd is printing correctly here for me."
1691195,2017-11-01 00:20:10 UTC,This issue was fixed in the openstack/nova 14.0.9 release.
1691195,2017-10-19 06:24:46 UTC,"Reviewed:  https://review.openstack.org/471356
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8b9aa3e00101b1258f9b3dedca66aac81f655778
Submitter: Zuul
Branch:    stable/newton"
1691195,2017-06-19 12:45:42 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1691195,2017-06-10 17:44:54 UTC,"Reviewed:  https://review.openstack.org/471353
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ef853e038d9a3e9bfe02287c7c01c80b7a022ed6
Submitter: Jenkins
Branch:    stable/ocata"
1691195,2017-06-08 21:51:25 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1691195,2017-06-06 13:47:33 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/471356"
1691195,2017-06-06 13:44:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/471353"
1691195,2017-05-17 00:34:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465205"
1691195,2017-06-06 18:55:48 UTC,"Reviewed:  https://review.openstack.org/465205
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a8a4a8ea7b8e6c85273ddb02d34d6af1740b183f
Submitter: Jenkins
Branch:    master"
1691203,2019-09-19 12:03:53 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1691214,2017-05-17 20:10:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691214,2017-11-30 12:29:26 UTC,"Hi Jeremy,
the difference of this and the tools we already do so is a hard enable vs auto mode."
1691214,2018-02-18 07:10:58 UTC,Adding -colorauto patch to ip.  It allows the behavior requested.  Tested build and install on bionic.  Will in parallel work on sending the patch upstream.
1691214,2018-02-18 08:22:47 UTC,"The attachment ""iproute2_4.14.1-0ubuntu3.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1691214,2019-04-20 16:34:57 UTC,Bump; was this patch sent upstream? What is the status of it at the moment?
1691218,2017-05-18 16:22:41 UTC,"Same problem here, using pxelinux 6.03 as of 16.04."
1691239,2017-06-04 17:04:24 UTC,Haven't heard of any regressions associated to 2.0.7 and have myself been running it for over a week now.
1691239,2017-06-07 13:04:44 UTC,This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~16.04.1
1691239,2017-06-07 12:54:48 UTC,This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~17.04.1
1691239,2017-06-07 12:54:42 UTC,This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~16.10.1
1691239,2017-06-07 12:54:35 UTC,"The verification of the Stable Release Update for lxcfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1691239,2017-05-18 20:47:00 UTC,"Hello Stéphane, or anyone else affected,"
1691239,2017-05-18 20:45:34 UTC,"Hello Stéphane, or anyone else affected,"
1691239,2017-05-18 20:41:10 UTC,"Hello Stéphane, or anyone else affected,"
1691242,2017-05-17 12:50:18 UTC,"I believe that network-get should always return information for the cluster binding, even if not binding has been provided by the end-user of the charm.  Otherwise we're back to 'unit-get private-address' which is know to be non-deterministic."
1691242,2017-05-20 11:11:30 UTC,"Assuming this is about:
2017-05-16 19:01:30 INFO config-changed ERROR no network config found for binding ""cluster"""
1691242,2017-05-20 11:12:26 UTC,"I know Witold recently made some changes wrt this which also should make 'unit-get private-address' more stable (albeit in the presence of bindings).
We should see if his changes in 2.2 also stabilize and give a value for 'network-get' when there are no explicit bindings."
1691242,2018-03-13 20:10:01 UTC,I am seeing this too. Is anyone going to do anything about it ?
1691242,2018-03-13 20:10:24 UTC,Any workarounds ?
1691242,2018-03-14 11:38:58 UTC,Is this being seen after an upgrade (of either juju or of a charm)?
1691243,2017-05-17 16:21:36 UTC,"Thanks, Bill. It works on both the home and logout icons. But I still think it will be good have a link to open a new tab, e.g. on top of Change Operator."
1691243,2017-05-16 19:27:27 UTC,"I had the same concern too when I first started testing the web client, but I think this is actually a browser issue and not an Evergreen issue. I added a paragraph to the web client docs to talk about this a bit - http://docs.evergreen-ils.org/2.12/_tab_browser_based_tab_buttons_and_keyboard_shortcuts.html."
1691243,2017-05-16 21:49:27 UTC,Thanks Kathy for the link.
1691243,2017-05-16 22:00:29 UTC,"If you already have a client tab open, you can control-click (or middle mouse click) the home icon (top-left) to open the home page in a new tab.  You can do the same with other links in the browser client as well, e.g. you can control-click any of the entries in the main menu to open that entry in a new tab."
1691246,2017-05-16 19:28:18 UTC,"I think this should have a setting to control the granularity of the data stored, i.e. down to the day, the month, or just the year."
1691247,2017-05-18 21:41:40 UTC,The following packages ended up in the wrong component in the -proposed pocket:
1691247,2017-05-22 10:12:32 UTC,Regression tests completed.
1691271,2018-04-25 21:43:38 UTC,According to https://github.com/sileht/cotyledon/issues/11 this may be fixed?
1691274,2018-05-02 12:05:32 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1691274,2018-02-15 23:53:56 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1691274,2018-01-31 12:51:39 UTC,"Reviewed:  https://review.openstack.org/515421
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1d614443a7198642ef14467ab470ce1aa41f36b9
Submitter: Zuul
Branch:    stable/ocata"
1691274,2017-12-14 20:20:55 UTC,"Reviewed:  https://review.openstack.org/515418
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fe9192037c2db49393e2e5f4e1c088ad7c38215f
Submitter: Zuul
Branch:    stable/pike"
1691274,2017-10-26 14:13:51 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/515421"
1691274,2017-12-07 23:57:01 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1691274,2017-10-26 01:25:50 UTC,"Reviewed:  https://review.openstack.org/465173
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=083bc89f99e007c400b9f89c63ac0459da910df8
Submitter: Zuul
Branch:    master"
1691274,2017-06-23 14:21:26 UTC,Here you go: https://review.openstack.org/#/c/465173/
1691274,2017-06-23 12:58:14 UTC,"There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments."
1691274,2017-10-26 14:09:58 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515418"
1691279,2017-05-16 22:10:42 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1691283,2017-06-08 01:01:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/471976"
1691283,2017-07-27 14:54:34 UTC,This issue was fixed in the openstack/puppet-tripleo 7.2.0 release.
1691283,2017-05-16 22:16:58 UTC,"Almost forgot, panko::wsgi::apache also points to 8779 in stead of 8777"
1691283,2017-06-07 02:52:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/471551"
1691283,2017-06-08 21:29:52 UTC,"Reviewed:  https://review.openstack.org/471551
Committed: https://git.openstack.org/cgit/openstack/puppet-panko/commit/?id=b33c63233286c8bb4be73f8da9d7fc7ef944a4a9
Submitter: Jenkins
Branch:    master"
1691283,2017-06-16 12:05:32 UTC,"Reviewed:  https://review.openstack.org/471577
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=ead742e169d3ac5c5907ca1a526474bfa0dc1e06
Submitter: Jenkins
Branch:    master"
1691283,2017-06-19 18:29:53 UTC,"Reviewed:  https://review.openstack.org/471567
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=6b0084c85df7c94465e2d1e9cda42a52947feee4
Submitter: Jenkins
Branch:    master"
1691283,2017-06-20 03:01:13 UTC,"Change abandoned by zhongshengping (chdzsp@163.com) on branch: master
Review: https://review.openstack.org/471976"
1691283,2017-07-26 18:44:02 UTC,This issue was fixed in the openstack/puppet-panko 11.2.0 release.
1691283,2017-07-27 14:54:08 UTC,This issue was fixed in the openstack/instack-undercloud 7.2.0 release.
1691289,2017-05-16 22:32:30 UTC,Attached is an excerpt of my syslog which should contain the relevant period of time.
1691289,2017-05-16 22:37:02 UTC,unattended upgrades did an upgrade this morning:
1691297,2017-05-17 02:48:55 UTC,This will be the proper fix for https://bugs.launchpad.net/juju/+bug/1688028 (which was tactically fixed for release by just bumping up the retry limit).
1691299,2017-07-01 01:13:55 UTC,"This may have been fixed recently, we should attempt to reproduce."
1691314,2019-06-19 20:36:44 UTC,This was brought up previously on the bash mailing list in 2014:
1691314,2019-06-25 15:27:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691324,2017-05-31 20:27:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691331,2017-07-09 17:51:44 UTC,This was fixed in 3.2.1-11
1691331,2017-07-28 04:02:16 UTC,Any chance it cam be released for 16.04 via updates?
1691337,2017-05-17 18:07:20 UTC,Another user reports similar behavior here - https://bbs.archlinux.org/viewtopic.php?pid=1711778#p1711778
1691357,2017-09-20 22:20:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691357,2017-08-30 04:17:29 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1691357,2017-06-30 10:03:42 UTC,Any progress on that matter?
1691357,2017-05-21 17:59:36 UTC,"Hm, strange."
1691357,2017-05-21 16:28:29 UTC,"Hmm, I enabled auto login and restarted after applying this update and I still couldn't reproduce the issue. (I was able to log out and log back in and switch to a different user)."
1691357,2017-05-21 02:20:38 UTC,I am setting the importance to Critical since this is a regression introduced in a Ubuntu Stable Release Update according to #7 of https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
1691357,2017-05-21 02:24:04 UTC,"Johon, the system journal excerpt attached to this bug has this line:
Mai 17 08:27:51 username-201604 gdm-autologin][3152]: gkr-pam: no password is available for user"
1691357,2018-05-15 20:27:16 UTC,I see this same behaviour on 2 machines with 18.04 when I have no swap. With swap enable the problem goes away. Bug did not exist in 17.10 or I believe until quite late in the 18.04 development cycle.
1691357,2017-05-17 06:38:13 UTC,Also to add: It does not matter if the custom.conf file is standard or with the modification I made (which is not really a modification anyways).
1691357,2017-05-21 11:57:33 UTC,"Jeremy, thank you for looking into this regression."
1691409,2017-05-18 10:43:17 UTC,"Reviewed:  https://review.openstack.org/465780
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=5140b1f18e2448c4b6cf381b901b881e9f48c3aa
Submitter: Jenkins
Branch:    master"
1691409,2017-05-18 01:47:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465780"
1691409,2017-05-17 09:06:24 UTC,dragonflow/controller/*_app.py
1691409,2017-05-17 09:01:05 UTC,neutron-lib.constants.IP_VERSION_4 or IP_VERSION_6
1691418,2017-05-17 12:51:35 UTC,"The patch ""block: get rid of blk_integrity_revalidate()"" had to be adjusted due to having ""block: Use pointer to backing_dev_info from request_queue"" backported for bug #1659111 ""UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel 4.4.0-47-generic""."
1691418,2017-06-28 16:35:34 UTC,This bug was fixed in the package linux - 4.4.0-83.106
1691419,2017-05-18 20:19:04 UTC,"cleaned up and ported to latest version
https://code.launchpad.net/~ubuntubmw/bzr/reproducible-builds/+merge/324284"
1691420,2017-05-18 04:24:57 UTC,Looks like this could have been caused by installing KDE and then gnome
1691420,2017-06-10 00:38:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691430,2017-05-17 15:32:18 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/465637"
1691430,2017-05-18 09:20:27 UTC,"Reviewed:  https://review.openstack.org/465637
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=dd5525e3d344e7eeef54894933489d6cb69a0707
Submitter: Jenkins
Branch:    stable/mitaka"
1691451,2017-12-01 08:15:06 UTC,heat panel is split out to heat-dashboard. Retargeting to heat-dashboard.
1691454,2017-05-29 23:37:08 UTC,"Reviewed:  https://review.openstack.org/465204
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=bd5b1a72e0b9449b4f3d091cc8e9748e70dc093e
Submitter: Jenkins
Branch:    master"
1691457,2017-05-17 12:20:34 UTC,d-i info:
1691462,2020-06-11 13:10:05 UTC,Facing same issue after following above comments solution:
1691462,2019-01-16 07:51:23 UTC,This happened for me when I had https_proxy etc set with a https protocol (e.g. set to https://localhost:3128) instead of just http.
1691462,2018-06-09 03:18:53 UTC,What fixed it for me was explicitly setting git's http.proxyAuthMethod to basic: git config --global http.proxyAuthMethod basic
1691462,2018-01-07 09:00:04 UTC,is there any way to get this solved .. this is (as we sit on docker and build the images automatically a big bummer for us)
1691462,2018-01-06 09:59:27 UTC,we are affected as well.
1691462,2017-12-15 07:14:22 UTC,"Using git is already the newest version (1:2.7.4-0ubuntu1.3) on arm64, git worked on the 3rd attempt, with 1st and 2nd giving the 'push' error."
1691462,2017-12-15 07:13:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691471,2017-05-18 10:09:33 UTC,The stable version is 3.2 on Ubuntu 14.04.02.
1691471,2017-05-19 17:58:31 UTC,Did anyone face this issue. And how could you resolve it.
1691485,2017-06-30 07:03:55 UTC,Not sure what that was. I just hit re-try this morning and it passed now.
1691485,2017-06-29 17:58:52 UTC,There seems to be an autopkgtest regression: http://autopkgtest.ubuntu.com/packages/u/ubuntu-fan/yakkety/amd64
1691485,2017-06-13 09:30:17 UTC,Ran the dep8 tests which would fail for the LXD test if disable-fan without docker installed would produce an error message. Both tests passed.
1691485,2017-06-09 14:53:15 UTC,"Hello Stefan, or anyone else affected,"
1691485,2017-05-31 13:07:42 UTC,"The verification of the Stable Release Update for ubuntu-fan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1691485,2017-07-04 12:02:50 UTC,This bug was fixed in the package ubuntu-fan - 0.12.0.2
1691485,2017-05-24 10:19:56 UTC,"Verification on Zesty/17.04:
- with ubuntu-fan=0.12.2 and no docker installed: error message on disable-fan
- after updating to ubuntu-fan=0.12.2.1, disable-fan runs without errors."
1691485,2017-05-23 19:18:27 UTC,This bug was fixed in the package ubuntu-fan - 0.12.3
1691485,2017-05-23 07:53:52 UTC,"Hello Stefan, or anyone else affected,"
1691485,2017-05-23 07:25:39 UTC,SRU Justification:
1691485,2017-05-31 13:07:36 UTC,This bug was fixed in the package ubuntu-fan - 0.12.2.1
1691489,2017-09-23 02:32:44 UTC,"This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New"
1691489,2017-09-15 21:34:26 UTC,"As far as I can tell, I don't think we can ""delay"" the fsck service due to how the systemd-fstab-generator works on /etc/fstab entries"
1691489,2017-09-15 18:36:54 UTC,"Not sure what to do here.
We intend to fix the other bug (bug 1717477) by reverting this change.
Thus re-opening this bug."
1691489,2017-09-15 09:57:01 UTC,"This release broke a lot of my machines, generating ordering cycles on every machine."
1691489,2017-09-13 01:27:27 UTC,This bug was fixed in the package cloud-init - 0.7.9-233-ge586fe35-0ubuntu1~17.04.1
1691489,2017-09-13 01:26:37 UTC,"The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1691489,2017-09-13 01:26:05 UTC,This bug was fixed in the package cloud-init - 0.7.9-233-ge586fe35-0ubuntu1~16.04.1
1691489,2017-09-12 22:02:42 UTC,Validated across multiple (5) 'clean' reboots that Azure vms don't hit the race condition with mounts and don't result in cloud-init errors.
1691489,2017-09-12 22:20:55 UTC,"Zesty verification:
 # Saw initial failure before upgrade
ubuntu@zesty1:~$ dpkg-query --show cloud-init
cloud-init	0.7.9-153-g16a7302f-0ubuntu1~17.04.2
ubuntu@zesty1:~$ grep reformat /var/log/cloud-init.log
2017-09-12 22:08:16,313 - DataSourceAzure.py[DEBUG]: reformattable=True: partition 1 (/dev/sdb1) on device /dev/disk/cloud/azure_resource was ntfs formatted and had no important files. Safe for reformatting."
1691489,2017-08-23 12:27:59 UTC,"Hello Scott, or anyone else affected,"
1691489,2017-07-31 14:37:05 UTC,This bug was fixed in the package cloud-init - 0.7.9-231-g80bf98b9-0ubuntu1
1691489,2017-06-23 22:48:26 UTC,"I filed a merge request to limit the fsck delay to Azure, please take a look at it."
1691489,2017-06-21 18:22:59 UTC,"Balint,"
1691489,2017-06-19 16:32:28 UTC,"I tried finding other options, but to work around /etc/fstab containing potentially invalid swap partition the only options seems to be calling ""swapoff -a"" and then later ""swapon -a"" from cloud-init when it detects that a partition re-initialization needs to take place."
1691489,2017-05-19 18:38:11 UTC,"Dimitri,"
1691489,2017-05-19 18:36:23 UTC,"It seems that in addition to blocking fsck, we should also block swap usage.
The severity of this issue is somewhat limited as the scenario will only happen when
a.) there is a filesystem (or swap) on a disk
b.) there is a (likely stale) entry in /etc/fstab for that disk already"
1691489,2017-05-17 14:35:56 UTC,"These tarballs are collected with 'save-old-data' at
 https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin"
1691489,2017-08-23 12:31:23 UTC,"Hello Scott, or anyone else affected,"
1691505,2020-11-02 11:33:13 UTC,windows bootloader detection has improved in recent releases. thus I am expecting for this to be fixed in focal.
1691508,2017-09-04 12:18:27 UTC,"I have installed version 0.7.14 on that same server, and unfortunately, I've been experiencing the same buggy behaviour as before for several days. So I'm afraid the fix didn't solve my issue."
1691508,2017-09-04 13:51:36 UTC,"Do you have any error messages at all?  I fixed the one case I could find, but I guess I missed something."
1691508,2017-09-04 15:38:22 UTC,"Unfortunately, all I have is all I've provided so far: there's nothing new in terms of behaviour or output."
1691508,2017-08-31 13:06:27 UTC,Thanks for releasing the fix. I am going to test this and will report back.
1691508,2018-02-26 21:08:48 UTC,Makes perfect sense. Thanks for clearing it up!
1691508,2018-02-26 20:06:31 UTC,"It just means that I'm moving it.  I needed to get these changes out and
the release could not wait on the rest of the bugs."
1691508,2018-02-26 17:01:00 UTC,"Hi,"
1691508,2017-07-20 16:46:58 UTC,Thanks for that! I will confirm it is fixed once it is released.
1691508,2017-05-18 11:53:39 UTC,The command line is as follows:
1691508,2017-06-13 17:05:53 UTC,"Unfortunately, there is nothing relevant in my notice.log; all I've got is the error I've pasted in the original bug report."
1691508,2017-06-13 15:13:57 UTC,"No, not confirmed yet."
1691508,2017-06-13 14:53:54 UTC,Would you be able to tell me whether this issue has been confirmed? Thank you very much!
1691508,2017-05-18 14:07:39 UTC,"Oops, sorry about that, here's the full command:"
1691508,2017-05-18 13:04:17 UTC,What schema do you use?  You left out the source and target on the command line.
1691508,2017-05-17 20:55:34 UTC,What is the command line?
1691508,2017-07-20 15:25:45 UTC,I believe this is fixed in the trunk now.
1691518,2017-05-17 18:52:51 UTC,Now I get this:
1691521,2017-07-27 16:30:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691523,2017-05-17 19:39:17 UTC,"We could make the bulk delete middleware aware of the multipart-manifest=delete parameter, which would be propagated on delete requests. In conjunction with https://review.openstack.org/#/c/463849/, we could delete all objects with the same single request."
1691523,2017-05-18 04:03:46 UTC,Is this same for DLO upload also ?
1691523,2017-05-18 18:55:07 UTC,"DLO support in Swift does not have a mechanism to remove all of the segments as part of removing the manifest. Given the eventual consistency issues with LIST, I suspect it was never added as an option as there is no guarantee that all of the segments will be removed."
1691525,2017-05-17 18:19:30 UTC,we will need some kind of upgrade hook in the core snap for such removals of files that did not come from the removed package itself but were generated. i guess the same goes for /var/log/syslog which is an orphan file as well now.
1691529,2018-09-07 07:18:21 UTC,tracked on story board - https://storyboard.openstack.org/#!/story/1691529
1691533,2017-05-17 19:12:26 UTC,"StacktraceTop:
 HexEditorFrame::OnUpdateUI (this=0x164a3f0, event=...) at src/HexEditorFrame.cpp:847
 wxAppConsoleBase::CallEventHandler (this=0x15f1ee0, handler=0x164a3f0, functor=..., event=...) at ../src/common/appbase.cpp:623
 wxEvtHandler::ProcessEventIfMatchesId (entry=..., handler=<optimized out>, event=...) at ../src/common/event.cpp:1392
 wxEvtHandler::SearchDynamicEventTable (this=0x164a3f0, event=...) at ../src/common/event.cpp:1751
 wxEvtHandler::TryHereOnly (this=0x164a3f0, event=...) at ../src/common/event.cpp:1585"
1691545,2017-06-08 21:52:13 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1691545,2017-05-17 20:03:51 UTC,Patch is here: https://review.openstack.org/#/c/465042
1691545,2017-05-19 21:24:12 UTC,"Reviewed:  https://review.openstack.org/465042
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=47fa88d94754fcdad6bb132b45196b4d44c0f4cd
Submitter: Jenkins
Branch:    master"
1691545,2017-05-19 22:06:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/466420"
1691545,2017-05-19 22:28:15 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/466424"
1691545,2017-05-22 13:29:51 UTC,"Reviewed:  https://review.openstack.org/466420
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f4159d17552603b90912dba6fe5c604e8d0b8aa7
Submitter: Jenkins
Branch:    stable/ocata"
1691545,2017-05-22 14:56:35 UTC,"Reviewed:  https://review.openstack.org/466424
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6a628da62f810310ab1bdc2e04222d8010e7b62
Submitter: Jenkins
Branch:    stable/newton"
1691545,2017-05-30 15:54:30 UTC,This issue was fixed in the openstack/nova 15.0.5 release.
1691545,2017-05-30 16:05:15 UTC,This issue was fixed in the openstack/nova 14.0.7 release.
1691549,2017-05-17 20:33:40 UTC,"Here is PulseAudio output when game freezes:
I: [alsa-source-USB Audio] alsa-source.c: Decreasing wakeup watermark to 13,38 ms
I: [alsa-source-USB Audio] alsa-source.c: Decreasing wakeup watermark to 8,38 ms
I: [alsa-source-USB Audio] alsa-source.c: Decreasing wakeup watermark to 4,19 ms
I: [alsa-source-USB Audio] alsa-source.c: Decreasing wakeup watermark to 4,00 ms
D: [pulseaudio] module-suspend-on-idle.c: Source alsa_input.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X00000Q6-00.analog-stereo-input becomes idle, timeout in 5 seconds.
D: [alsa-source-USB Audio] alsa-source.c: hwbuf_unused=0
D: [alsa-source-USB Audio] alsa-source.c: setting avail_min=95809
D: [pulseaudio] module-suspend-on-idle.c: Source alsa_input.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X00000Q6-00.analog-stereo-input becomes idle, timeout in 5 seconds.
I: [pulseaudio] source-output.c: Freeing output 3 ""Record Stream""
I: [pulseaudio] client.c: Freed 12 ""FMOD Record Helper""
I: [pulseaudio] protocol-native.c: Connection died.
D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X00000Q6-00.analog-stereo-output becomes idle, timeout in 5 seconds.
D: [alsa-sink-USB Audio] alsa-sink.c: hwbuf_unused=0
D: [alsa-sink-USB Audio] alsa-sink.c: setting avail_min=95119
D: [alsa-sink-USB Audio] alsa-sink.c: Requested volume: front-left: 37985 /  58% / -14,21 dB,   front-right: 37985 /  58% / -14,21 dB
D: [alsa-sink-USB Audio] alsa-sink.c: Got hardware volume: front-left: 38295 /  58% / -14,00 dB,   front-right: 38295 /  58% / -14,00 dB
D: [alsa-sink-USB Audio] alsa-sink.c: Calculated software volume: front-left: 65005 /  99% / -0,21 dB,   front-right: 65005 /  99% / -0,21 dB (accurate-enough=yes)
D: [alsa-sink-USB Audio] sink.c: Volume not changing
D: [alsa-sink-USB Audio] alsa-sink.c: Requested to rewind 384000 bytes.
D: [alsa-sink-USB Audio] alsa-sink.c: Limited to 5888 bytes.
D: [alsa-sink-USB Audio] alsa-sink.c: before: 1472
D: [alsa-sink-USB Audio] alsa-sink.c: after: 1472
D: [alsa-sink-USB Audio] alsa-sink.c: Rewound 5888 bytes.
D: [alsa-sink-USB Audio] sink.c: Processing rewind...
D: [alsa-sink-USB Audio] sink.c: latency = 8085
D: [alsa-sink-USB Audio] source.c: Processing rewind...
D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.usb-Creative_Technology_Ltd_SB_Omni_Surround_5.1_X00000Q6-00.analog-stereo-output becomes idle, timeout in 5 seconds.
D: [pulseaudio] core.c: Hmm, no streams around, trying to vacuum.
I: [pulseaudio] sink-input.c: Freeing input 1 ""Mixer Stream""
I: [pulseaudio] protocol-native.c: Connection died.
D: [pulseaudio] ratelimit.c: 110 events suppressed
D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry)
D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry)
D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry)
D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry)
D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry)
D: [pulseaudio] flist.c: pulsecore/memblockq.c: list_items flist is full (don't worry)
D: [pulseaudio] flis..."
1691550,2017-06-20 21:10:31 UTC,Submitted https://review.openstack.org/#/c/465732/5 to fix this issue for VLAN overlay.
1691550,2017-06-21 21:16:43 UTC,"Reviewed:  https://review.openstack.org/465732
Committed: https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=0c66056dfbbfb4e1e309d9c791a149ebcd8d8fb3
Submitter: Jenkins
Branch:    master"
1691550,2017-07-11 18:06:03 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/482652"
1691550,2017-07-11 18:07:29 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/482653"
1691550,2017-07-18 23:39:23 UTC,"Reviewed:  https://review.openstack.org/482652
Committed: https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=34d295c9bf4200c2dc6077bb2990bb752d874e92
Submitter: Jenkins
Branch:    stable/ocata"
1691550,2017-07-18 23:48:12 UTC,"Reviewed:  https://review.openstack.org/482653
Committed: https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=160eae8c94859831895f7a69b92db9625b3b3ad9
Submitter: Jenkins
Branch:    stable/newton"
1691552,2017-05-17 20:30:08 UTC,This change was made by a bot.
1691556,2020-03-10 13:49:06 UTC,"I don't use Ubuntu currently, but I think this is a Linux issue anyway."
1691556,2019-07-02 22:27:02 UTC,After trying a random assortment of fixes to get my Amazon Echo Show to connect as a speaker using bluetooth to my Linux Mint 19.2 box I found the solution far too simple.  The magic reboot!  I rebooted the Echo and that must have cleared the bluetooth connections... ha
1691556,2019-01-18 10:03:26 UTC,"I had the same issue with Device or resource busy and the same problem when Alexa says that is connected to pc and no sound - but it's because your pc becomes bluetooth speaker for Echo, in that state pacmd list-cards shows:
...
a2dp_source: Przechwytywanie o wysokiej dokładności (źródło A2DP) (priority 20, available: yes)
a2dp_sink: Odtwarzanie o wysokiej dokładności (odpływ A2DP) (priority 40, available: no)
off: Wyłączone (priority 0, available: yes)
..."
1691556,2018-11-29 09:34:56 UTC,"my issue:
a2dp-source profile connect failed for XX:XX:XX:XX:XX: Device or resource busy"
1691556,2018-11-29 09:22:00 UTC,"I am using Ubuntu 18.04 and I have same issue. My echo was working fine from many days and suddenly I have this issue where when I goto bluetooth devices and right click on Echo and click on Audio Source, It says ""Now connected to Ubuntu"" but does not play sound."
1691556,2018-10-20 04:46:02 UTC,"On 18.04, I'm having this same issue. I can pair to an Echo, but cannot connect nor setup as an Audio Sink. I get errors like ""dbusfailederror input/output error"" in blueman."
1691556,2018-09-20 20:33:03 UTC,"I can confirm that pavucontrol shows moving sounds bars with an Output Device called ""Headphones (unplugged)"" and that the Configuration shows ""High Fidelity (A2DP Sink) Unplugged"" and ""High Fidelity Capture (A2DP Source)"". There is no sound however."
1691556,2018-02-08 21:02:06 UTC,"for what it's worth, pavucontrol shows that the Echo is playing music."
1691556,2017-06-18 00:55:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691556,2017-06-18 00:54:46 UTC,"I have the same problem. Dell XPS13 laptop Linux Mint 18. Finally managed to pair with Amazon Echo, but cannot get sound to it."
1691556,2017-05-18 01:54:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1582213, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1691556,2017-05-17 20:55:34 UTC,"Additionally, this issue also appeared along the line with Ubuntu+KDE and apparently was easily resolved, as described in ubuntuforums.org, [link](https://ubuntuforums.org/showthread.php?t=2318966).  Quoting another ubuntuforums.org post (also KDE), [link](https://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04), ""....So far, it seems that things only go wrong when I try to connect in A2DP mode. Until there is a real fix/workaround, I am going to try to remember to always switch to HSP/HSF mode before powering off or disconnecting the speaker."".  So, perhaps in the short-term for Ubuntu+Unity a similar workaround could be found, if this is indeed the correct diagnosis, and in the longer-term figure out why connecting in A2DP mode fails (for both KDE and Unity)."
1691556,2017-05-17 20:45:54 UTC,"I should also note that on the askubuntu.com site, I speculate that it may just be some permission issue deep down somewhere, and why."
1691556,2018-02-09 01:51:52 UTC,Can anyone with an Amazon Echo also try Ubuntu 18.04?
1691570,2018-01-02 23:29:29 UTC,james-page:
1691570,2020-07-22 21:59:44 UTC,"Reviewed:  https://review.opendev.org/700444
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=74daa465d626f04f30685f46025fbd6799be2657
Submitter: Zuul
Branch:    master"
1691570,2020-05-14 22:06:21 UTC,"Subscribing field-medium since we need the nrpe check urgently for a customer.
We have a merge proposal ready for it, we only need a review and a merge."
1691570,2020-04-15 16:25:58 UTC,"For the swift-storage charm, I've added in an nrpe monitor check that validates that the swift-object-replicator is actively logging into syslog.  The indication that this bug has been exhibited is that the logs from swift-object-replicator stop providing the ""replicated X of Y partitions (X%)"" messages every five minutes.  This monitor's alert will allow the cloud operators to identify and restart hung swift-object-replicator threads."
1691570,2018-11-27 19:57:25 UTC,For the charm at a minimum let's create a sanity check on the replication configuration.
1691570,2018-05-29 11:50:50 UTC,"Hi Drew, I don't see any patches pending for this bug so as it's been a few months I will mark this back to New. If you have a patch pending or landed for this LP please go ahead and paste a link. Thanks."
1691570,2017-10-05 18:55:39 UTC,1. https://etherpad.openstack.org/p/swift-replicator-handoff-only-workers
1691570,2017-06-16 19:13:17 UTC,"FYI, After updating the above server to swift 2.7.1, we are still seeing the exact same issues."
1691570,2017-10-04 23:23:02 UTC,It appears that this is an upstream swift issue.  I fear that the greenthreads coro reaping process being used in swift is failing to account for processes not dying due to being stuck in blocking i/o wait (D) state.
1691570,2017-09-29 11:07:35 UTC,(but the docs would indicate we're still pretty good on alignment)
1691570,2017-09-29 11:05:51 UTC,"I've marked this as  medium priority for the charm; however I'm not sure we're really to the bottom of the actual issue still - this might be a swift bug, rather than something the charm is doing with regards to configuration of swift."
1691570,2017-09-18 22:08:06 UTC,"I have a theory that perhaps the threading employed in swift-object-replicator may not be properly waiting for proper termination of the rsync processes if they are in the non-blocking i/o run state, as is often the case in the environment we are having issues with.  I believe it it due to many writes happening from other nodes via the inbound rsync connections are causing a denial of service to the outbound rsync traffic at the disk controller.  I think the ""killing coros"" section of code may need some improvement to ensure the rsyncs are culled before they return.  We are ending up with a lot of zombie rsync processes under the swift-object-replicator parent."
1691570,2017-09-07 20:29:32 UTC,"After updating to a version of the charm that includes the ability to tune the rsync timeout, we upped the timeout to >12 hours, and replication is able to complete on many hosts, but some rsync processes are hanging or timing out on the server side and causing swift-object-replicator hangups polling filehandles for the rsync pipes which interrupts the every 5 minute log-dump of current replication status.  This shows up after ""lockup detected, killing coros..."" shows up in the logs."
1691570,2017-08-07 20:12:36 UTC,I believe this issue was the result of hanging non-interruptable storage hardware errors.
1691570,2017-10-05 18:53:30 UTC,"yes!  that!  I think if the ""watcher"" was moved into a separate os thread it'd have a better chance of detecting the lockup.  But to do anything about it we'd need to be able to respawn a *process* - so the control needs to be moved *way* up.  The ""wrokers"" design [1] recently added to the reconstructor is ripe to be ported/extended/unified with the replicator and could help with this problem in two ways:"
1691574,2017-07-25 02:36:57 UTC,The same issue.
1691574,2017-07-25 05:59:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691577,2020-12-17 18:18:14 UTC,Does this issue still affect cups-pdf 3.0.1 packages?
1691581,2017-11-28 15:07:07 UTC,I can confirm that null sort keys prevent the item from being visible in shelf browse.
1691597,2017-05-17 23:44:45 UTC,Related logging messages:
1691597,2017-05-18 11:41:49 UTC,"So I have tried the package locally downloaded from the related loging messages provided by @cprov. That package reports the snap name for it is ""hello"" and not ""hello-robinhood2017"". Granted the error message should probably be more helpful but this is not really a malfunction of our checks."
1691597,2017-05-18 12:24:37 UTC,"Now that we know what the problem was, we could have spotted the mismatch just after pushing the file by checking that the snap-id in the upload-status URL (mVyGrEwiqSi5PugCwyH7WgpoQLemtTd6) is the ""hello"" snap, instead of ""JM8jBjdJsQWEEB4K7wfxKFfWamsFkvos"" (hello-robinhood2017)"
1691597,2017-09-18 06:19:24 UTC,"So snapcraft should check that the snap id and the snap name match, before trying to upload. I'm marking this as triaged."
1691597,2019-10-11 01:12:51 UTC,https://github.com/snapcore/snapcraft/pull/2749
1691600,2017-05-18 00:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1691600,2017-05-18 15:20:19 UTC,"It looks like this was ZFS related.  It sounds like there is no way to reproduce this bug, so it's probably best to keep a close eye on the instance."
1691602,2019-11-21 16:45:05 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/465792"
1691602,2019-11-21 16:44:58 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/687410"
1691602,2018-10-25 19:11:38 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/465792"
1691602,2018-07-08 02:05:34 UTC,"Reviewed:  https://review.openstack.org/578612
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8756d5a4a7c06d25705af6243ea8ce8fd148411
Submitter: Zuul
Branch:    stable/queens"
1691602,2018-06-28 00:16:44 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/578612"
1691602,2018-06-27 22:06:29 UTC,"Reviewed:  https://review.openstack.org/465787
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=537f480927293755bd6365068c1abd0c80951bad
Submitter: Zuul
Branch:    master"
1691602,2019-10-08 20:18:56 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/687410"
1691602,2017-07-28 20:21:46 UTC,This issue was fixed in the openstack/neutron 11.0.0.0b3 development milestone.
1691602,2017-06-27 16:00:45 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1691602,2017-06-15 17:22:46 UTC,"Reviewed:  https://review.openstack.org/465783
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bf8e6007cfa50d461790be325e9e97b8b396ae47
Submitter: Jenkins
Branch:    master"
1691602,2017-05-18 02:53:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465787"
1691602,2017-08-23 15:37:32 UTC,"Reviewed:  https://review.openstack.org/466449
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2f67b97577fa28f7e6ab23971e7d6f259889c992
Submitter: Jenkins
Branch:    master"
1691602,2017-05-18 02:21:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465783"
1691602,2017-05-18 01:08:45 UTC,"The messy thing with this is going to be the existing nw info cache refresh code in nova doesn't know how to handle a single port id, if it's given that it expects it's from attaching a port to an instance."
1691607,2017-09-29 10:54:46 UTC,"Moving bug to swift package, which provides the upstream and init scripts; that said they all call swift-init and it would appear that the process tracking under both upstart and systemd is foobar as neither init system is actually tracking the process ultimately run."
1691607,2017-07-28 22:14:48 UTC,This continues to be a recurrent problem.  Is there any additional information we can provide that would help?
1691608,2017-05-24 16:41:12 UTC,"I added the oem-audio-hda-daily-lts-xenial-dkms driver using Synapic and enabled it with the system settings.
That helped a little"
1691608,2017-05-31 14:22:13 UTC,"I got updates for the HDA driver, installed them but issue still there."
1691621,2019-03-22 15:47:31 UTC,Hey zhongjun the link does not work anymore could you send new logs if this is still occurring?
1691621,2019-10-28 18:07:36 UTC,closing this issue for now if you are still seeing this issue and are working on it please re-open
1691622,2017-05-18 12:42:47 UTC,"Actually, according to [1], the version introducing this error is sphinx 1.6.1"
1691622,2017-05-18 13:44:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/465978"
1691622,2017-05-18 14:02:16 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/465978"
1691622,2017-05-18 14:03:14 UTC,requirements/test-requirements.txt excludes sphinx 1.6.1 version.
1691622,2017-05-19 08:02:32 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/465978
Reason: Superseed by https://review.openstack.org/#/c/466133/"
1691622,2017-05-22 11:05:17 UTC,"Reviewed:  https://review.openstack.org/465436
Committed: https://git.openstack.org/cgit/openstack/manila-specs/commit/?id=d5dc5b51fa45f2a7ba947b844c769cf3a7e733ea
Submitter: Jenkins
Branch:    master"
1691622,2019-10-28 18:09:03 UTC,"zhongjun are you still seeing this issue, can we assist anyone helping you address this?"
1691625,2017-05-18 03:19:33 UTC,I am using Ubuntu 14 for the above.
1691625,2017-05-18 10:00:33 UTC,"confirmed on Windows 10, Inkscape 0.92.1 r15371 (32 bit)"
1691636,2017-08-30 19:53:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691646,2017-12-11 09:59:21 UTC,"In my environment of trove-dashboard with version master, I can get instances host info as below."
1691646,2018-01-08 05:59:44 UTC,"Not bug,modify the configuration file of trove."
1691646,2018-08-24 19:32:41 UTC,If it's not a bug then maybe this ticked should be closed?
1691648,2017-05-18 11:21:49 UTC,The idea of vacuuming has come up before. In the past we haven't bothered with vacuum because the normal life cycle of a Swift container in most clusters is heavy PUT focused and vacumming was an overhead that isn't worth it.
1691663,2017-05-18 08:30:39 UTC,I think it is a MAAS DNS issue.
1691673,2017-05-31 07:12:48 UTC,"Hi team,"
1691673,2017-05-31 09:05:45 UTC,Interesting...
1691673,2017-06-08 13:22:51 UTC,"Hi all,"
1691673,2017-08-11 04:48:59 UTC,"We can close this bug.
https://bugs.launchpad.net/zun/+bug/1703955
And it is resolved in  https://review.openstack.org/487381."
1691673,2017-08-11 07:57:56 UTC,thank you @eli qiao
1691678,2020-03-03 13:25:21 UTC,What's the current status of this bug? Where is the fix? One of my report is made duplicate to this bug but I think this is much older. I'm using 19.10
1691678,2020-03-03 13:57:01 UTC,It appears we would need a new upstream bug to track this because the old one didn't go anywhere. Please create one in:
1691678,2020-03-03 21:26:18 UTC,"> It appears we would need a new upstream bug to track this because the old one didn't go anywhere.
"
1691678,2020-03-04 17:48:04 UTC,"It's not an upstream bug. I checked several other distribution with different themes, none of them is affected. Only Ubuntu's gnome-terminal is affected."
1691678,2020-03-05 17:47:38 UTC,The issue is due to the patch scrollbar-background-theming.patch but dropping the change creates a regression on the Ubuntu session/theme which is what most users will see. It would be nice to see the problem resolved by removing the change is not the solution
1691678,2020-03-06 08:44:23 UTC,"> but dropping the change creates a regression on the Ubuntu session/theme
"
1691678,2020-03-06 15:55:45 UTC,I don't think that's necessary and probably not helpful. There are already multiple moving parts here so it would be easier to deal with if the theme was not changed simultaneously.
1691678,2020-03-06 14:43:06 UTC,"Hi Daniel,"
1691678,2020-05-25 02:12:44 UTC,I would like to continue working on this bug but it's just not a priority right now.
1691678,2020-03-12 09:26:22 UTC,"Possibly the pixels under the scrollbar are being painted as white before the scrollbar itself gets painted. So any transparency in the theme won't come out right, but is still technically transparent."
1691678,2020-03-19 06:33:05 UTC,"Actually the proper solution to comment #28 would be to change to overlay scrollbars, which is already covered by bug 1451924. It's still a different bug to this one, but if implemented it would close this bug nicely."
1691678,2020-05-23 17:53:37 UTC,What is the current status of this bug? Can we have any workaround for this bug?
1691678,2020-03-06 14:23:43 UTC,"I'm not familiar with gnome-terminal and not much with CSS, but I have decided to dig into this bug and see what's happening."
1691678,2019-10-29 08:37:35 UTC,Still a problem with upstream Adwaita so it would be nice to find a universal solution.
1691678,2020-03-04 17:50:30 UTC,"I support the idea in the last para. of @egmont-gmail. If a patch introduce a regression which is worse than the improvement made by the patch, the patch should be dropped. I'm getting tired of Ubuntu fixing something and breaking some other things."
1691678,2019-05-27 11:57:50 UTC,upstream bug report confirms that this is a bug in Ubuntu:
1691678,2019-09-09 07:25:55 UTC,"FYI, there's a workaround hacked into Yaru:"
1691678,2017-06-10 19:22:48 UTC,The package overlay-scrollbar hasn’t been used in GTK+ 3 applications for a long time
1691678,2017-06-12 03:21:19 UTC,Confirmed the same bug with Adwaita. In fact it's worse in Adwaita -- the overlay scrollbar can end up overrunning the right and bottom edges of the window after resizing finishes.
1691678,2018-09-10 07:56:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691678,2018-09-14 12:44:16 UTC,Is this an upstream issue (does Fedora show that behavior as well?) or the outcome of a Debian patch? There is at least one which is scrollbar related:
1691678,2018-09-14 12:49:37 UTC,https://4.bp.blogspot.com/-CKw5ikw4WNo/WWo7WrezseI/AAAAAAAAKC4/CPbs48OQj0A2hMNY5_Ivu6iTaRzClDYMQCLcBGAs/s1600/07%2BGNOME%2BTerminal.jpg
1691678,2018-09-10 07:57:15 UTC,Still a problem in Ubuntu 18.10 cosmic.
1691678,2018-09-15 18:34:06 UTC,"Nope. Not completely sure, sorry. I didn't compile GNOME apps before, so that would probably be a rather heavy task for me ;) I had a quick look at the 3.30.0 source but couldn't even find out which lines were changed by the Debian patch. Aren't the patches included within the source tar?"
1691678,2019-04-03 15:11:21 UTC,This issue is still there in in the current beta of Ubuntu 19.04 (Gnome 3.32 with Adwaita).
1691678,2019-04-03 16:15:42 UTC,Adwaita? What about Yaru?
1691678,2019-04-04 01:41:23 UTC,In 19.04 right now the bug appears with Adwaita but not with Yaru. That doesn't mean it's a theme bug though -- it might be a universal bug and something about the Yaru design is hiding it.
1691678,2019-05-27 11:40:07 UTC,I confirm the previous suspicion: This is _not_ an upstream bug. Upstream gnome-terminal draws the scrollbar perfectly.
1691678,2018-09-14 15:22:05 UTC,"Are you sure this is due to the above patch, can you try without it?"
1691688,2017-05-18 12:28:17 UTC,"AppCenter is using Stripe for payment, so I am afraid that paying with PayPal is not possible."
1691688,2017-05-19 21:30:44 UTC,Could this change in the future? Because this potentially is a significant loss in revenue.
1691688,2017-05-19 22:02:13 UTC,"Obviously, I can't speak for elementary OS, but I feel like this is an edge case."
1691693,2017-06-05 14:17:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691693,2017-06-15 16:21:42 UTC,This looks like a dpkg failure more than a libreoffice-common package issue.
1691693,2017-06-21 13:51:53 UTC,"Olivier, no, I'm having problems with the current kernel, can't connect to internet, but  I'm using a previous one. I thought I had resolved the problems, but did and update yesterday and they are back again."
1691693,2017-11-23 11:01:23 UTC,I'm having this problem with libreoffice-common 1:4.2.8-0ubuntu5.2 on one machine and perl-base 5.18.2-2ubuntu1.3 on another. Both 14.04.05 LTS.
1691693,2017-12-26 21:28:39 UTC,"Hey, I had this same problem and I was able to get around it by disabling sophos-av."
1691693,2019-09-24 19:27:08 UTC,"Hi Jeff, thanks that helped. Same problem was here."
1691694,2017-09-18 08:41:56 UTC,It's old code judging by `git blame` but:
1691694,2017-09-18 02:33:39 UTC,"After reading the source, it has become clear that this would probably work if we could avoid having to define the machine in the bundle."
1691694,2017-09-18 07:12:05 UTC,"Tim,"
1691694,2017-05-18 08:50:14 UTC,"The problem here is that the bundle deployment code splits an application deployment into ""juju add-machine"" and ""juju deploy application --to <machine> --storage foo"". Because MAAS storage is ""static"" (i.e. tied to the machine), this doesn't work."
1691694,2017-09-13 08:31:06 UTC,More info in a dup:
1691695,2017-05-27 11:34:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691707,2017-05-23 07:53:21 UTC,"With the Patch like the attached, the initscript is working as expected."
1691707,2017-05-23 08:28:29 UTC,"The attachment ""Amavisd-milter initscript Patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1691707,2017-06-12 09:08:53 UTC,"Hello? Is there anyone who wanna do something, or is amavisd-milter not maintained?"
1691707,2017-11-10 07:41:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691707,2017-11-10 07:49:37 UTC,There is a patch made for Debian package at:
1691707,2018-05-26 07:57:46 UTC,Any chances for backports?
1691707,2020-11-22 09:48:56 UTC,Waiting for new Debian release
1691707,2020-11-25 04:01:52 UTC,This bug was fixed in the package amavisd-milter - 1.7.1-2
1691712,2018-03-14 14:47:58 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1691729,2018-02-11 20:44:29 UTC,Same for me. Doesn't boot. Need to re-imaging.
1691729,2020-12-16 20:52:13 UTC,Getting this in 18.04.5
1691729,2019-10-15 19:43:11 UTC,"The current versions of linux-firmware-raspi2 for bionic and eoan (1.20190215-0ubuntu0.18.04.1 and 1.20190819-0ubuntu2 respectively) shouldn't conflict in this manner; neither include the -sdio.bin files, just the configuration text files and related .clm-blob files. Is anyone still seeing this issue with the latest versions?"
1691729,2018-01-12 20:48:16 UTC,"Jon,
    Does armbian-config work on ubuntu 16.04?    Does that command freeze all SW or allow you to specify?
THX"
1691729,2018-01-12 19:13:48 UTC,armbian-config -> System -> Freeze
1691729,2018-01-12 19:01:14 UTC,"I can confirm all of what Blake & Jim said, just tried it too. Raspberry Pi 3, Mainline Distro.   Pi did not come back from reboot.  Re-imaging now.  May ""freeze"" these packages as a work around and not attempt a dist-upgrade."
1691729,2018-01-12 18:46:04 UTC,"although the ""diversion"" workaround results in a nice-looking upgrade output.   The system fails to reboot for me as well."
1691729,2017-12-14 17:40:33 UTC,"The workaround (in Comment #4) is not working for me.  I'm running on a Raspberry Pi 3 Model B.  I've been working on this for several days and trying different variations in the order I do things (rebooting or not after upgrade, etc.), and eventually I always end up with a SD image that will not boot.  Which makes sense, I guess, since this involves a firmware image."
1691729,2017-12-08 06:26:48 UTC,This is still the case with linux-firmware 1.157.14.
1691729,2017-10-09 20:46:06 UTC,I had this very same issue when upgrading a Pi 2 image of Ubuntu Server 16.04.3 to Pi 3.  The directions are here:  https://wiki.ubuntu.com/ARM/RaspberryPi#line-105
1691729,2017-07-12 09:34:23 UTC,"I need a headless, minimal install of Ubuntu to run on a Raspberry Pi 3. I followed the instructions here:"
1691729,2017-07-06 14:56:21 UTC,The linux-firmware-raspi2 1.20161020-0ubuntu1~0.2~rpi3 is not the same linux-firmware-raspi2 that you find in the archive: it is actually a package from a PPA - you should contact the author and work out the problem with him.
1691729,2017-06-30 11:23:51 UTC,Thanks! The diversion worked for me as well.
1691729,2017-05-30 21:29:00 UTC,"Thank you for the workaround, that's very helpful :)"
1691729,2017-05-30 21:17:37 UTC,"For every-body who has this issue, the following command works around it until the package maintainers find a solution:"
1691729,2017-05-30 20:10:42 UTC,Any solution to this? - Experiencing the same problem:
1691729,2017-05-30 20:09:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691729,2017-05-18 11:43:58 UTC,Actually it wasn't stuck. It has now tried to install 1.157.10 and failed as well.
1691734,2017-05-28 13:56:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691735,2017-05-18 11:52:41 UTC,Version 0.158 in Artful.
1691735,2019-02-12 22:01:48 UTC,fixed in https://git.launchpad.net/~ddstreet/ubuntu-dev-tools/+git/ubuntu-dev-tools/commit/?id=abded7f62efe4479b4cfe7030e15a73e79745077
1691745,2017-05-18 12:30:07 UTC,"this is how the edit windows form a vpn connection named ""PureVPN"" looks like"
1691745,2017-05-18 12:34:38 UTC,kernel 4.11.1 is used from upstream packages supplied by official Ubuntu server:
1691756,2017-05-19 21:38:27 UTC,Tested on 2.12.1  & I'm not seeing the duplicate field addition in Reports.
1691756,2018-02-27 14:42:26 UTC," I am seeing what Jason reported.  It is easy to select fields for display and then, inadvertently, add them as filters as well.  I, too, like the ability to select multiple fields, but they should not stay selected after they are added either to the display or filter tabs."
1691756,2019-05-02 14:13:42 UTC,"For the record, the problem with the field transform mentioned in #2 has its own bug report: bug 1778521."
1691757,2017-05-19 13:15:43 UTC,"Makes sense to me, but I'm curious if you have a specific use case in mind?"
1691757,2017-05-22 12:29:56 UTC,"Mainly flexibility and consistency with egConfirmDialog which already allows this. It's slightly more hassle to translate but I'd rather that users be able to choose between 2 actions rather than having to click OK for choice 1 and cancel for choice 2, etc."
1691761,2017-05-18 15:50:16 UTC,Looks like /sys/kernel/security/apparmor/profiles has unexpected content.
1691761,2017-05-18 16:40:03 UTC,"I did
# cat /sys/kernel/security/apparmor/profiles > /tmp/aa_broken_profiles"
1691761,2017-05-18 20:45:33 UTC,"That already explains it - the regex doesn't match the ""(-)"", but the code expects that the regex always matches ;-)"
1691761,2017-05-18 21:41:51 UTC,"I did changes into aa-status (in line 148, as you mentioned above). This fixed the issue for me."
1691763,2017-08-17 23:11:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691763,2017-10-24 16:24:02 UTC,"I just encountered this myself. Was a bit bored, so did some testing."
1691769,2017-05-19 14:27:42 UTC,"Reviewed:  https://review.openstack.org/466097
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=994caa464efdbed3d684354d699cd79e41d7eb0f
Submitter: Jenkins
Branch:    master"
1691769,2017-05-18 20:23:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/466097"
1691769,2017-05-18 19:54:48 UTC,It might be possible to do something like this:
1691769,2017-05-18 19:47:45 UTC,Here is the state of our jobs that run live migration today:
1691782,2017-05-18 15:18:33 UTC,"One of these failure is definitely a kernel bug, see LP #1691752."
1691782,2017-05-18 15:24:50 UTC,Other amd64 failures.
1691782,2017-05-18 15:27:57 UTC,armhf - tests refuse to run due to being in a container.
1691782,2017-06-02 20:03:04 UTC,"The ""List prints core snap version"" test is still failing."
1691782,2017-06-13 14:33:44 UTC,"""List prints core snap version"" test still fails with 4.11.0-6.11 and snapd 2.26.4+17.10. I did some investigation running the tests locally. In the test environment 'snapd list' prints:"
1691784,2017-05-18 15:58:07 UTC,This sounds a lot like bug #849143.
1691784,2017-05-19 13:46:23 UTC,"Bill,"
1691784,2017-09-14 16:40:16 UTC,"""Evergreen should include a check for these and update them to the transfer destination record along with the ""delete the now empty bib"" step."""
1691786,2017-06-05 08:25:13 UTC,"Hi Kazunori,"
1691786,2017-06-09 08:25:41 UTC,"ok, will check that also."
1691786,2017-08-15 12:19:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/493852"
1691786,2017-06-05 03:48:12 UTC,"Looks nobody is working for this, I will propose the patch.  Thanks."
1691786,2017-05-19 05:05:59 UTC,Which heat version are you using btw?
1691786,2017-05-19 06:05:08 UTC,"Yeah, looks like it's broken. Feel free to propose a patch."
1691786,2017-05-19 05:37:45 UTC,I think it caused by the port which changes from None ==> <Port>
1691786,2017-05-19 07:58:54 UTC,There is a one more scenario where i saw this problem.
1691790,2017-05-20 14:18:26 UTC,You are using an old release (1.1). Please upgrade OpenRails to stable release 1.2 or to an actual experimental release and try again.
1691793,2017-05-19 10:38:34 UTC,"A related issue is that in the case of repeated pushes to a PRed branch, we'll request tests for each commit without removing the old ones."
1691793,2017-10-25 11:34:19 UTC,"I pushed a change which should help with this, but isn't a fundamental solution"
1691798,2017-05-20 15:08:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691804,2018-01-24 22:40:40 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1426
1691806,2017-05-18 18:31:46 UTC,Please file an issue on github:
1691806,2017-05-18 18:44:23 UTC,Github issue link
1691807,2017-06-12 03:38:16 UTC,A couple more thoughts on this.  There are still a couple cases where the decryption key is not verified (unless we persist something new for user-meta) even though the same object key is used for both body and headers at this point.
1691807,2017-06-11 20:05:38 UTC,"@Ruslan Hello.  I hope you don't mind, but I was thinking about this wishlist bug this weekend and have come up with some questions and a patch (#473149) to demonstrate what I was thinking.  But I see that you are the assignee on this bug.  It would be great to get your feedback on what I have proposed.  Have you started work on this issue?  If so, we can work together on the solution if you would like.  You can reach me in #openstack-swift as jrichli"
1691810,2017-05-21 03:25:25 UTC,same thing with linux mint 18 & not 17. so weird.
1691814,2017-06-29 06:26:39 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1061.69
1691814,2017-06-28 16:42:26 UTC,This bug was fixed in the package linux-gke - 4.4.0-1018.18
1691814,2017-06-28 16:42:04 UTC,This bug was fixed in the package linux-aws - 4.4.0-1022.31
1691814,2017-06-28 16:41:44 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1063.68
1691814,2017-06-28 16:35:34 UTC,This bug was fixed in the package linux - 4.4.0-83.106
1691814,2017-06-06 15:08:58 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-79.100~14.04.1
1691814,2017-06-06 15:02:55 UTC,This bug was fixed in the package linux-aws - 4.4.0-1018.27
1691814,2017-06-06 15:04:47 UTC,This bug was fixed in the package linux-gke - 4.4.0-1014.14
1691814,2017-06-06 14:54:04 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1059.63
1691814,2017-06-01 17:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1691814,2017-06-01 16:35:29 UTC,Confirmed that all derivatives from xenial kernel 4.4.0-79.100 were built successfully.
1691814,2017-06-06 15:06:27 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1057.64
1691825,2017-05-20 07:02:05 UTC,can you watch the progress after 'retry-provisioning' is issued?
1691825,2017-05-21 11:35:11 UTC,"dmitriis@maas-master:~/openstack-base$ openstack security group list -f value | wc -l
14"
1691831,2017-06-03 21:20:35 UTC,"Reviewed:  https://review.openstack.org/469013
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9d299ae50ea52c63811eba11ee974643c17079ad
Submitter: Jenkins
Branch:    stable/newton"
1691831,2017-08-28 09:55:31 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1691831,2017-06-08 21:52:12 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1691831,2017-05-30 15:45:39 UTC,"Reviewed:  https://review.openstack.org/469012
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=81838f1ae910383bf0992684e6b0ef30a6d943ba
Submitter: Jenkins
Branch:    stable/ocata"
1691831,2017-06-19 12:45:56 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1691831,2017-05-30 08:17:01 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469012"
1691831,2017-05-29 16:38:09 UTC,"Reviewed:  https://review.openstack.org/466088
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3072b0afbc157eef5e72f191525296cfa2b014cb
Submitter: Jenkins
Branch:    master"
1691831,2017-05-18 19:47:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466088"
1691831,2017-05-30 08:17:37 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/469013"
1691834,2017-05-19 09:42:40 UTC,"Hi Alan,
$ apt-get install golang-1.6-go golang-1.6-race-detector-runtime
works perfectly fine and /usr/lib/go-1.6/src is a symlink both packages own.
$ dpkg -S /usr/lib/go-1.6/src
golang-1.6-race-detector-runtime, golang-1.6-go: /usr/lib/go-1.6/src"
1691834,2017-06-14 07:22:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691835,2017-05-30 07:33:41 UTC,"This issue also affects Zesty kernel tests (4.10.0-22.24):
   ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/l/lttng-modules/20170529_124228_7417d@/log.gz"
1691847,2017-05-19 15:53:00 UTC,This looks like it may still be an issue in the pam from artful (1.1.8-3.2ubuntu3). Would you mind taking this to the upstream pam developers?
1691847,2017-05-18 20:23:48 UTC,"The attachment ""Add to parser system the fix"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1691847,2017-05-18 19:55:27 UTC,This is the patch that I came up with to fix pam_limits.c
1691856,2017-05-18 21:02:28 UTC,I just pushed the fix to master since it is a documentation change and Jason Boyer is not around right now to test it.
1691865,2017-05-20 13:07:01 UTC,"> That said, I think this bug is still valid - I don't believe that Deja-Dup
> is handling whatever gvfs returns properly, resulting in the blank screen.
"
1691865,2017-05-20 10:16:10 UTC,"Hi Nathanaël,"
1691865,2017-05-20 12:11:26 UTC,"For anyone coming across this same issue, the fix to get gvfs working was to add an entry ""client use spnego = no"" in the [global] section of the file /etc/samba/smb.conf. Without this line, gvfs can't authenticate properly on password-protected shares."
1691865,2017-05-19 05:55:53 UTC,"Hi Mike, thanks for your report."
1691865,2017-05-19 05:59:51 UTC,"PS: your Déjà-Dup configuration looks right, it's gvfs's SMB mounting that doesn't work, as far as I can tell."
1691867,2017-05-19 22:11:00 UTC,This bug was fixed in the package gnome-user-docs - 3.24.2-0ubuntu2
1691867,2017-05-20 15:32:51 UTC,This bug was fixed in the package gnome-getting-started-docs - 3.24.1-0ubuntu2
1691867,2017-06-10 16:45:08 UTC,This bug was fixed in the package gnome-panel - 1:3.24.1-1ubuntu2
1691867,2017-07-24 14:30:29 UTC,Spam reverted
1691867,2017-09-14 09:50:34 UTC,This bug was fixed in the package gnome-documents - 3.25.91-1
1691867,2017-09-19 17:45:04 UTC,This bug was fixed in the package meta-gnome3 - 1:3.22+5ubuntu1
1691867,2017-09-27 16:59:31 UTC,This bug was fixed in the package ubuntu-docs - 17.10.6
1691867,2017-10-11 15:29:52 UTC,This bug was fixed in the package gnome-session - 3.26.1-0ubuntu3
1691867,2018-01-03 00:30:15 UTC,This bug was fixed in the package gnome-commander - 1.4.8-1.1
1691867,2018-03-11 00:24:46 UTC,This bug was fixed in the package gnome-control-center - 1:3.27.92-1ubuntu1
1691867,2018-03-28 13:32:23 UTC,This bug was fixed in the package gnome-flashback - 3.28.0-1ubuntu1
1691885,2017-07-24 15:15:00 UTC,I don't believe this is implemented for baremetal back end. This is more of a spec to get that work in than a bug.
1691885,2017-06-01 06:53:40 UTC,"In my opinion, even if nova gets the error from neutron, nova doesn't output Error[1]. It's not neutron issue."
1691885,2017-05-23 08:46:40 UTC,"Looks to me like a neutron issue. neutron is looking for floatingips for the port/fixed_ip combination[1]. Not sure why? And probably floatingip extension is not available as this message suggests ""No controller found for: floatingips - returning response code 404"""
1691885,2017-05-23 00:21:03 UTC,"Here are the applicable log snippets, let me know if you want any more before/after:"
1691885,2017-05-19 04:31:15 UTC,I think the issue with with baremetal (ironic behind nova). Our implict port creation stuff in OS::Nova::Server is not working with baremetal.
1691885,2017-05-19 02:47:20 UTC,"What version of heat? And I can't reproduce this problem as following steps in master:
1. create a stack with the template:
  th_server:
    type: OS::Nova::Server
    properties:
      name: test_server
      flavor: {get_param: flavor}
      image: {get_param: image}
      networks:
        - network: {get_param: net}
          fixed_ip: 10.0.0.24
2. update the stack to change the fixed_ip to '10.0.0.25', stack update success and the server ip is changed to the new one."
1691885,2017-05-20 05:04:26 UTC,From the error it looks like it's failing with same vif attach/detach. Would you be able to share the heat engine nova logs?
1691892,2017-05-19 00:42:14 UTC,"Please, I need to know if this is a software problem or lack of memory problem."
1691892,2018-05-08 18:09:06 UTC,This change was made by a bot.
1691894,2017-05-30 22:04:52 UTC,Created pull request in https://review.openstack.org/#/c/468702/
1691894,2020-01-08 19:46:41 UTC,"Change abandoned by Clark Boylan (<email address hidden>) on branch: master
Review: https://review.opendev.org/468702
Reason: Fuel projects have been retired."
1691902,2017-05-19 02:57:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466160"
1691902,2017-11-09 02:30:43 UTC,"Change abandoned by Zhenyu Zheng (<email address hidden>) on branch: master
Review: https://review.openstack.org/466160"
1691907,2017-06-13 06:56:56 UTC,"Change abandoned by Tomasz Trębski (<email address hidden>) on branch: master
Review: https://review.openstack.org/466354
Reason: Handled in another change where need to look up for config file was removed."
1691908,2020-07-02 09:23:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu."
1691908,2020-10-07 23:12:48 UTC,This is occurring in Ubuntu 20.04. All my zfs mounts are appearing in my desktop file-manager. Screenshot attached. A total nuisance.
1691908,2020-10-08 10:18:26 UTC,"@Peter, please don't comment on a closed report but rather open a new one using ubuntu-bug and including current debug informations (in that case probably output of 'gio mount -li')"
1691908,2020-06-24 21:22:48 UTC,Could someone provide a testcase describing a situation that is buggy today and how to trigger it?
1691908,2020-10-08 22:22:58 UTC,"I have reported a new bug:
https://bugs.launchpad.net/bugs/1899089"
1691908,2020-10-09 08:04:28 UTC,"> `ubuntu-bug` requires a PID. '
"
1691908,2020-10-08 21:32:36 UTC,"@Sebastien,"
1691908,2019-04-17 11:30:25 UTC,This bug is still relevant for Bionic. Any info about possible backport?
1691908,2020-05-25 22:10:03 UTC,+1 to bionic backport please
1691908,2019-01-14 11:22:30 UTC,This bug is fixed upstream. Can we get backport to bionic?
1691908,2018-08-21 16:52:21 UTC,"The upstream bug report was migrated on May 19, 2017, to a new bug tracker."
1691908,2017-06-16 16:41:40 UTC,Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=782814
1691908,2017-06-16 16:41:07 UTC,Confirmed.
1691908,2017-06-16 16:40:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691908,2017-05-19 03:13:37 UTC,Cross posted to Gnome Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=782814
1691908,2017-05-19 02:46:50 UTC,"Sorry, by ""Nautilus"", I meant Deepin File Manager which is based on Nautilus."
1691911,2017-06-21 18:05:08 UTC,This bug was fixed in the package lxc - 2.0.8-0ubuntu1~16.10.2
1691911,2017-06-21 18:04:57 UTC,This bug was fixed in the package lxc - 2.0.8-0ubuntu1~16.04.2
1691911,2017-06-21 18:04:47 UTC,This has been in the development release and our PPA for a while now without any report of regressions. Releasing.
1691911,2017-05-29 09:53:44 UTC,"Hello Stéphane, or anyone else affected,"
1691911,2017-05-29 09:46:21 UTC,"Hello Stéphane, or anyone else affected,"
1691911,2017-05-29 09:55:53 UTC,"Hello Stéphane, or anyone else affected,"
1691921,2017-05-19 04:05:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691921,2018-07-27 06:34:47 UTC,"I have a theory we will occasionally hit this crash when the gnome-shell process leaks file descriptors. So it could easily be caused by a buggy extension, and may go away for some time and then return in a later release (as it did stop in 17.10 but now has returned in 18.10)."
1691924,2017-07-19 12:58:11 UTC,Huh? What's this about?
1691924,2018-03-01 22:08:01 UTC,"Marking as Invalid because the release is EOL is not correct. Marking as Incomplete. Also, 18.04 is (at the time of writing) still in development, and you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29"
1691924,2018-02-27 07:50:12 UTC,This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'
1691924,2017-05-19 16:15:11 UTC,"I did see that unhelpful generic boiler plate message every time I tried to run `sudo do-release-upgrade` yes. That doesn't exactly constitute a helpful error message. It's more like saying, ""There's a problem and what you tried to do failed"" which I already knew by the process not succeeding."
1691924,2017-05-19 15:41:42 UTC,Did you receive and error message like this?
1691924,2017-05-19 13:30:27 UTC,"Turned out that the culprit, despite a very long list of Broken packages in Apt.log, was this inconspicuous line in Main.log:"
1691924,2017-07-19 04:17:44 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1691943,2017-08-11 17:55:20 UTC,This is totally contained in the heat plugin.
1691946,2017-05-23 16:49:43 UTC,The actual error is:
1691964,2017-06-02 06:37:15 UTC,On correction:
1691964,2017-06-02 06:30:02 UTC,"Information about second point (f):
os-collect-config.service is defined to start in multi-user.target after cloud-final.service but
cloud-final.service is defined to start after multi-user.target (deadlock)
That's why the following works:"
1691969,2017-05-31 17:08:42 UTC,Can't we use the existing user that runs the test? It's guaranteed to be present.
1691971,2017-11-22 02:51:32 UTC,This issue was fixed in the openstack/puppet-tripleo 7.4.5 release.
1691971,2017-12-04 21:02:24 UTC,This issue was fixed in the openstack/puppet-tripleo 8.1.0 release.
1691971,2017-08-07 16:36:43 UTC,This is affecting me too.
1691971,2017-07-12 17:21:24 UTC,I'm seeing a similar traceback which may be related and provide more information:
1691971,2017-06-16 21:00:52 UTC,"Can we raise the priority of this bug? I don't see any patch in progress for the WSGI server, so it should probably be fixed in haproxy for the itme being? Thanks."
1691971,2017-10-12 13:13:25 UTC,I added the tripleo workaround in the meantime here: https://review.openstack.org/511462 feedback appreciated.
1691971,2017-06-02 13:44:47 UTC,"Hi, just saw the same myself.
I did some searching and this in particular might happen if the other end has already closed the (TCP) connection while inspector is still sending data. Maybe HAProxy's ""pings"" indeed."
1691971,2017-05-19 12:29:55 UTC,"I see that in tripleo undercloud /var/log/messages. ironic-inspect is behind haproxy, and haproxy has a periodic check request to see the service availability. You can see it in triple jobs log, eg http://logs.openstack.org/94/464094/3/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha-oooq/1c37a38/logs/undercloud/var/log/messages.txt.gz"
1691971,2017-05-19 12:09:01 UTC,"Hi Thomas,"
1691971,2017-06-02 15:04:29 UTC,"Done some more research on this issue.
The main reason is inspector runs the werkzeug.BaseWSGIServer which in turn uses socketserver.BaseServer that, upon connection error, prints(!!) the error and traceback in socketserver.BaseServer.handle_error."
1691979,2017-05-19 09:34:12 UTC,This appears to be fixed in 3.1.3 of etcd where they have fixed the sd_notify behaviour.
1691983,2017-05-19 09:50:19 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1679366, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1691983,2017-06-07 17:23:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1691998,2020-11-23 15:46:26 UTC,"After the talk with the Openstack team, we determined that due to the async nature and no guaranteed order of hooks execution after the `juju remove-unit` command is executed, there will have to be a new action implemented that prepares `nova-compute` unit for departure."
1691998,2019-09-18 06:57:32 UTC,"When removing a unit, case should be taken for aggregate de-registration and the neutron stuff that is related to the host instance."
1691998,2017-09-21 14:58:11 UTC,"I know this to be the case; its somewhat of a historic issue as very early juju versions never actually executed the stop hook, so no charm ever implemented them as they where useless with no way to test."
1691998,2017-05-19 19:10:07 UTC,i found that even neutron-openvswitch-agent is still registered
1691998,2017-05-20 05:37:22 UTC,I'm pretty sure this should be considered a bug in the charm itself.
1692021,2017-06-28 09:49:42 UTC,"Above issue is fixed and below is the commit id
https://github.com/Juniper/contrail-web-core/commit/abee7e3d15e60f8f0fcbb1f150a83974b3203b2d"
1692038,2017-06-24 18:40:17 UTC,"I run into the same issue on 17.04.  I have three monitors and the two secondary monitors become nonresponsive as well.  If I logout out, it fixes the issue.  My CPU and GPU below."
1692039,2017-05-19 14:52:34 UTC,There is a not-so-evident consequence of this bug.
1692042,2017-05-19 15:00:07 UTC,This change was made by a bot.
1692060,2017-05-19 16:39:26 UTC,Same with tor_vendor_name.
1692061,2017-05-23 10:11:14 UTC,update on my lab:
1692066,2017-10-28 00:16:17 UTC,"I suggest you file a Debian Request for Package (RFP) for network-manager-libreswan :
   https://wiki.debian.org/RFP"
1692066,2018-04-24 08:19:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692066,2017-08-27 21:33:26 UTC,"Hi Gustavo,"
1692066,2017-05-19 20:23:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1692066,2017-08-26 19:17:35 UTC,As suggested by user.
1692071,2018-08-23 21:28:50 UTC,Bug could be closed as fixed released or invalid since version is much higher : 4.4
1692096,2017-05-20 15:36:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692105,2017-05-24 14:05:28 UTC,Seems related to https://bugs.mysql.com/bug.php?id=78352
1692105,2017-09-22 21:07:22 UTC,This does not appear to be related to the aforementioned bug. relay_log_recovery is off in my scenario. I've set up a lab environment to create a reproduceable case for this. Please see below.
1692105,2018-01-25 09:22:05 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3704
1692108,2017-05-20 04:21:13 UTC,"Also, I had previously tried reducing the baud rate to the default 100,000, but there was no change.  After reading about this hardware bug from 4 years ago, https://github.com/raspberrypi/linux/issues/254, I lowered the baud rate to 50,000, and I am able to successfully access the device. I don't know where between 50KHz - 100KHz that it fails, but is there any update on this issue?  Also, of course, it might be something else with a similar symptom.  Thanks. -Tal"
1692108,2017-05-23 15:59:01 UTC,"Ugh.  On checking again at 400KHz after the successful testing at 50KHz, the issue is no longer reproducible.  I hate mysteries like this, and I would still appreciate any insights."
1692109,2017-05-19 20:43:12 UTC,"mount from util-linux 2.27.1 (libmount 2.27.0: selinux, assert, debug)
Description:	Ubuntu 16.04.2 LTS"
1692109,2017-05-20 01:48:43 UTC,AFAICS the problem is libmount/src/context_mount.c:exec_helper() which is uses operands in a wrong/not posixly incorrect way. See also http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
1692118,2019-04-11 16:07:30 UTC,Would it make sense to create a more generally useful logrotate subordinate charm?
1692118,2019-04-10 16:51:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651606"
1692118,2019-03-27 16:03:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648168"
1692118,2019-04-12 07:13:03 UTC,"> Would it make sense to create a more generally useful logrotate subordinate charm?
"
1692118,2019-03-26 17:43:03 UTC,I don't think any of the openstack charms provide log rotation config options so I'm going to add more charms to the affected projects.
1692118,2019-03-26 17:54:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692118,2021-01-29 18:10:57 UTC,This might already be superseded by https://jaas.ai/logrotated
1692118,2020-10-26 16:01:07 UTC,"Charmhelpers should support the logrotate change by writing a file on ""/etc/logrotate.d/<appname>"". One of the parameters of the helper function would be a list of log files to be tracked and rotated (so each charm will specify a different list)."
1692126,2017-05-25 20:53:11 UTC,This makes sense across all neutron resources.
1692126,2017-07-27 17:42:05 UTC,"Let's see if Kevin wants to expand the use case and have this be addressed as a ""standard attribute""."
1692126,2017-10-12 00:36:13 UTC,Also a potential starter RFE
1692126,2017-10-12 12:46:27 UTC,"i agree it makes sense to add the ""reason of status"" field to any resouces with ""status"".
otoh, i'm not sure if it belongs to standard attributes. after all, not all resources have ""status""."
1692126,2017-10-13 22:26:23 UTC,Update after meeting on 10/12/2017. The consensus of the drivers team is that this is a reasonable addition to VPN. We will let the VPN team whether they want to continue with this
1692147,2018-05-08 18:09:40 UTC,This change was made by a bot.
1692147,2021-01-07 04:15:31 UTC,4.8 EOL
1692150,2020-09-22 08:18:20 UTC,Closing because INVALID: Can't replicate.
1692150,2017-07-26 14:39:00 UTC,"Now is a external dependence. If not sure check if you have alowed trace bitmap, if not potrace is not instaled"
1692150,2017-05-21 12:02:01 UTC,"By the way, official PPA is currently with the broken version, see this bug:  https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1686345"
1692150,2017-05-20 11:51:54 UTC,This is with standard Ubuntu repository.  No other PPA's were added.
1692150,2017-05-20 11:31:02 UTC,"Is this with the package coming from the official Ubuntu archive, the inkscape PPA, or what?"
1692150,2017-07-26 14:22:45 UTC,Are you sure you have potrace instaled?
1692172,2017-05-20 05:43:16 UTC,Update:
1692185,2017-05-20 13:15:19 UTC,Copied the bug report to github: https://github.com/elementary/appcenter/issues/307
1692186,2017-05-20 13:12:30 UTC,Copied the bug report to github: https://github.com/elementary/appcenter/issues/306
1692188,2017-09-08 13:07:58 UTC,https://github.com/systemd/systemd/pull/6771
1692188,2017-09-08 15:39:05 UTC,Sweet! Thank you!
1692198,2018-01-02 14:17:31 UTC,status ok with granite 0.5 lib
1692199,2017-05-20 20:15:53 UTC,I can confirm this
1692206,2020-05-09 01:15:30 UTC,"No responds, I am closing it now."
1692206,2018-04-18 17:46:32 UTC,Please test the new version 2.1.0 that supports storing the BPM in file tags. Fractional digits for MP3 files should be preserved when re-importing tags.
1692206,2017-05-27 03:41:50 UTC,"I see. Sorry, but I didn't get where I can store the BPM. Separate tag? I saw some mp3 have custom fields, like ""encoder"". Integer means 103, not 103.5, right?"
1692206,2017-07-23 09:53:24 UTC,"Please refer to http://id3.org/id3v2.4.0-frames ""4.2.3 TBPM BPM (beats per minute)"". Integer = no fractional digits."
1692206,2017-07-23 14:47:10 UTC,"Integer for BPM, what a facepalm %)"
1692206,2017-05-25 17:06:49 UTC,"Yeah, string fields are sorted as strings; this is the normal way to sort strings that have numbers in them. If you want numeric sorting, use a numeric field. I think the solution to having software independent BPM data is for Mixxx to write the BPM to the files' tags, not to use the comments field for something it isn't meant for. Refer to https://github.com/mixxxdj/mixxx/pull/728"
1692206,2017-05-25 16:51:29 UTC,Comments are sorted lexicographically. Mixxx is not able to deduce the sort order from the contents of individual fields. In your case Mixxx would even need to know how to parse the number it should use for sorting from the remaining text.
1692206,2017-05-26 21:52:35 UTC,Writing BPM values into the corresponding tag works like a charm for various formats and is portable. Please note that BPM in ID3v2 tags (MP3) are rounded to integers according to the specification.
1692207,2017-06-03 14:24:33 UTC,"I created a new virtual machine, and installed an older Zim (version 0.60) in that and created a new notebook with 2 pages. One having no ""space"" character in its name, and other having ""space"" character(s). I then started the web-server, and opened it in my browser. All the pages were opening fine."
1692207,2017-05-31 13:21:30 UTC,"There is at least an bug hiding in the error reporting, but that is not the issue"
1692208,2017-05-20 11:19:45 UTC,"the 4.2.0 initrd's are pretty sparse, the recent ones seem to have a full set of modules and firmware (e.g. 18MB of drivers/net)"
1692208,2017-05-20 11:30:10 UTC,This change was made by a bot.
1692208,2020-01-09 06:53:09 UTC,"4.8 / 4.10 EOL,
please feel free to open a new bug if you're still encounter this issue with newer releases."
1692220,2017-07-30 16:39:56 UTC,"Hi Chad,"
1692220,2017-05-30 05:38:12 UTC,"Hi Chad,"
1692224,2017-06-16 14:00:41 UTC,Reattributing to the gtk+3.0 package...
1692242,2017-05-20 17:57:06 UTC,changelog for 6.0.4 http://www.syslinux.org/wiki/index.php?title=Syslinux_6_Changelog#Changes_in_6.04
1692242,2020-05-01 20:15:08 UTC,https://bugs.launchpad.net/ubuntu/+source/syslinux/3:6.04~git20190206.bf6db5b4+dfsg1-2
1692261,2017-05-26 14:48:06 UTC,"Most controllers have shift buttons and it's easy to map Shift+Play to Brake, Shift+Cue to SoftStart.
Even though I agree it would be cool to make those features accessible to mouse users, I don't feel they should be in effect units because they are basically transport controls.
On the other hand, in effect units one could adjust the parameters."
1692261,2017-05-26 15:06:06 UTC,"Long pressing the cue button already has its own behaviors with cue_default. IMO shift + cue is better used for jumping to the beginning of the track and stopping (start_stop Control), and this is how I've designed the CueButton in Components. But long pressing the play button is an option. This could be implemented in the Components PlayButton pretty easily."
1692261,2017-05-26 15:23:28 UTC,"On second thought, long pressing the play button would not work, because we cannot introduce a delay to determine whether to toggle the play Control or do the soft start/brake. With the play Control toggled immediately on press, soft start/braking would then be really awkward."
1692261,2017-05-27 23:57:15 UTC,"The right click play has different features across the skins.
I have never actually used it. So it is a good candidate for soft start and stop.
I would be relay happy to have this accessible from the skins."
1692261,2018-08-15 16:55:41 UTC,Why cant it be done like it is done in serato?
1692261,2018-08-15 20:09:24 UTC,"We can do it like this. It would be an improvement over the current state.
We just need a contributor, who had interests and time to implement it. A conditional soft start and brake however would be reasonable though."
1692261,2018-08-15 20:10:48 UTC,Can the user enable/disable it on the fly in serato?
1692261,2019-01-19 16:19:40 UTC,"Yes we could make this an effect, but I actually wouldn't sacrifice one or even two effect slots for this feature."
1692261,2019-01-19 20:25:47 UTC,"Yes, a hard coded engine solution sounds reasonable.
This is the inner play function:
CueControl::updateIndicatorsAndModifyPlay()
this is the speed function:
RateControl::calculateSpeed()"
1692263,2017-05-22 22:49:27 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1692292,2018-02-16 00:47:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692297,2017-05-22 20:12:31 UTC,"Witold,"
1692297,2017-05-21 20:34:07 UTC,"dmitriis@maas-master:~$ juju --version
2.2-beta4-xenial-amd64
dmitriis@maas-master:~$ juju add-model default
Uploading credential 'mightymaas/admin/joseph-mightymaas' to controller
Added 'default' model with credential 'joseph-mightymaas' for user 'admin'"
1692297,2017-05-21 19:11:07 UTC,There is a bug in ifupdown - '-i' argument is not being passed to ifquery. I'll work around that tomorrow.
1692297,2017-05-21 10:59:02 UTC,I can confirm that - I am facing the same issue with bonds on 2.2beta4 and I verified that 2.1.2 works properly.
1692297,2017-05-22 13:30:40 UTC,https://github.com/juju/juju/pull/7374
1692297,2017-05-21 14:31:37 UTC,Could you set log level to DEBUG and post the logs somewhere?
1692303,2019-03-26 05:47:38 UTC,Does this occur with the latest version of Inkscape?
1692303,2019-03-27 06:43:17 UTC,Thanks for letting us know the issue is resolved with the latest version.
1692303,2019-03-26 06:35:33 UTC,"Bug seems to be fixed with current version.
I startet Inkscape and tested some mouse overs on the right button bar. I could read all ""hints""."
1692305,2017-05-21 10:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1692305,2017-12-13 23:56:53 UTC,"I am seeing the same issue for
asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card
https://www.amazon.com/gp/product/B07532Y2LL/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1"
1692305,2017-07-11 14:46:05 UTC,"Can you also give the latest upstream 4.10 kernel a test?  It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/"
1692305,2017-06-27 22:49:57 UTC,"Hello,"
1692305,2017-05-30 16:59:24 UTC,"Could you also test the latest upstream stable 4.10 kernel? It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/"
1692305,2017-05-29 22:40:05 UTC,"Hi Joseph,"
1692305,2017-05-25 16:14:14 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1692305,2017-05-21 12:07:15 UTC,apport information
1692305,2017-05-21 12:07:08 UTC,apport information
1692305,2017-05-21 12:07:05 UTC,apport information
1692305,2017-05-21 12:07:06 UTC,apport information
1692305,2017-05-21 12:07:00 UTC,apport information
1692305,2017-05-21 12:06:57 UTC,apport information
1692305,2017-05-21 12:06:56 UTC,apport information
1692305,2017-05-21 12:06:54 UTC,apport information
1692305,2017-05-21 12:06:53 UTC,apport information
1692305,2017-05-21 12:06:51 UTC,apport information
1692305,2017-05-21 12:06:49 UTC,apport information
1692305,2017-05-21 12:06:47 UTC,apport information
1692305,2017-05-21 12:06:45 UTC,apport information
1692305,2017-05-21 12:06:44 UTC,apport information
1692305,2017-05-21 12:07:02 UTC,apport information
1692305,2017-05-21 12:07:03 UTC,apport information
1692319,2017-05-21 13:40:47 UTC,I did see a question on the main Chromium Discuss forum when I asked about this there:
1692319,2017-05-29 17:36:30 UTC,"I did find an link to the very-last version of GoogleChrome for 32bit Linux (one that Google didn't manage to obliterate from the internet) and the extension works there, although it whines and moans that it's an obsolete and unsupported version.  So I know it is not dependent on 64bit.   Would really prefer to use this under Chromium so I don't have to have the old GChrome build just to edit GoogleDocs offline."
1692319,2017-06-15 17:02:18 UTC,"For reference, here is the link to the chromium-discuss thread mentioned in comment #1: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-discuss/VoNNKLgmAzg."
1692319,2017-06-15 17:03:27 UTC,"And as I mentioned there, if the same extension works (although briefly) on a 64bits system with the same version of chromium, it's unlikely that the issue lies with the API keys, as they are exactly the same shared by all builds."
1692321,2017-06-30 10:02:24 UTC,Tried it with kernel 4.12-rc7 and iwlwifi-8000C-31.ucode. This combination seems to stop the problems.
1692321,2017-05-25 16:13:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1692326,2017-05-22 15:57:52 UTC,"This is broken *in the build produced in zesty*.  This is a bug specific to the version produced and packaged and delivered to ubuntu users by default as part of zesty 17.04, and this is not an invalid bug if a fix was made to it."
1692326,2017-05-23 04:46:02 UTC,"I'm not sure what the Ubuntu policy is with respect to upstream bugs, but can I humbly suggest looking at the latest Mnemosyne version first, and if the bug has been fixed there, open an Ubuntu bug to upgrade to the latest version? If it's a new bug, please open a report in the Mnemosyne tracker."
1692326,2017-05-22 06:40:08 UTC,This has been fixed in 2.4.1.
1692338,2017-12-28 02:03:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692343,2017-05-21 19:19:00 UTC,Not all browsers support all svg elements.
1692343,2017-05-22 07:41:39 UTC,The svg attachment.
1692343,2017-05-22 07:59:54 UTC,"I tried to save the svg as optimised svg but an error occurred dialog appears pointing error as
import scour in inkscape.scour.py.
I tried to install scour using pip3 install scour but the error remains.
I later tried previous extension which gives this error:-
File ""webslicer_export.py"", line 66
    except Exception, e:
                    ^
SyntaxError: invalid syntax"
1692343,2017-05-22 08:23:46 UTC,"Ok , I think the syntax error is due to python 3.5 incompatibility"
1692343,2017-05-22 11:21:11 UTC,"The fill of your clouds uses a meshgradient - those are not supported by browsers (yet).
Use a normal gradient or a solid fill."
1692345,2017-06-30 05:07:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692353,2020-07-28 01:41:46 UTC,Requesting patch to be included in bionic-updates as well. Current systemd-version = 237-3ubuntu10.41 (https://bugs.launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.41).
1692353,2020-07-14 17:33:50 UTC,This bug was fixed in the package systemd - 245.6-2ubuntu1
1692353,2019-03-20 12:54:07 UTC,This bug still exists in 19.04 Disco. Please fix it.
1692353,2018-07-25 06:09:17 UTC,"Interesting, I was sure we upstreamed completely systemd-fsckd. Anyway, +1 for me, let me assign to xnox who is doing most of systemd uploads nowdays so that he attaches it to next upload."
1692353,2017-12-12 12:07:32 UTC,Interesting.
1692353,2018-07-24 14:29:08 UTC,Thanks for submitting this patch and sorry for the time to review it!
1692353,2017-05-21 20:28:09 UTC,"The attachment ""patch_to_remove_useless_cr.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1692353,2018-07-24 15:25:05 UTC,"Hello,"
1692353,2017-12-01 15:44:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692353,2017-12-12 12:07:51 UTC,"Didrocks, would you be able to review this patch?"
1692363,2020-07-12 16:03:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692370,2017-05-22 23:00:54 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1692370,2018-08-10 03:27:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692373,2017-12-19 18:00:23 UTC,"Hello
I installed refind by naming it grubx64.efi.
Shimx64 launches it very well in NON SECURE mode.
But, if I change the bios to switch to SECURE mode, SHIMX64 does not succeed in launching it. Which is normal. but it does not launch MMX64.EFI that would allow me to define this ""grub"" as secure."
1692373,2017-05-24 00:56:29 UTC,"The sources are mostly same, so the problems are the same.
I submit this bug for debian as well."
1692373,2017-07-15 14:52:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692373,2017-05-23 01:08:03 UTC,"> > This is a low priority bug for ubuntu, cause it has grub2-signed
> > package. But in debian case it becomes problematic as debian has no
> > grub2-signed package.
>
> It doesn't have one *yet*. This is planned.
"
1692373,2017-05-22 22:49:24 UTC,"On Mon, May 22, 2017 at 10:08:21PM -0000, Mikhail Kshevetskiy wrote:

> This is a low priority bug for ubuntu, cause it has grub2-signed
> package. But in debian case it becomes problematic as debian has no
> grub2-signed package.
"
1692373,2017-05-22 22:08:21 UTC,"This is a low priority bug for ubuntu, cause it has grub2-signed package. But in debian case it becomes problematic as debian has no grub2-signed package. Thus users must use self-compiled monolith grub2 package. Evidently this package is not signed with Debian key, and hence it can't be loaded."
1692373,2017-05-23 19:12:41 UTC,"On Tue, May 23, 2017 at 01:08:03AM -0000, Mikhail Kshevetskiy wrote:

> > > This is a low priority bug for ubuntu, cause it has grub2-signed
> > > package. But in debian case it becomes problematic as debian has no
> > > grub2-signed package.
"
1692377,2017-12-06 20:27:44 UTC,"commited to master in 9cff10a53a3e0c404e5b5b7a56542360532b96c7
By the moment only remove the button show if sometime resurrect it in the future."
1692377,2017-12-06 18:40:17 UTC,https://gitlab.com/inkscape/inkscape/merge_requests/155
1692377,2017-05-22 20:48:26 UTC,I hope this weekend can do a fix for 0.93.
1692377,2017-12-06 15:06:08 UTC,"Hi Jabier - if it doesn't also reset any other parameters, then it's not really needed."
1692377,2017-12-05 21:22:23 UTC,"Hi Maren: Whats your opinion to drop the button. is not used in other toolbars and is a pecendence, not needed realy."
1692377,2017-12-06 18:29:32 UTC,"thanks, going to drop"
1692378,2017-05-22 00:52:57 UTC,I can confirm that this bug affects the latest version of Thunderbird (52.1.1) 64-bit.
1692378,2017-05-22 01:54:33 UTC,Seems fine using Xubuntu 17.10 so may be a problem with the theme rather than with Thunderbird.
1692378,2017-05-22 02:39:29 UTC,"Lubuntu 16.04.2 x64, Thunderbird 52.1.1 from Ubuntu repos."
1692378,2018-05-09 06:58:17 UTC,works fine in bionic
1692378,2018-05-09 06:58:33 UTC,still an issue?
1692378,2018-09-16 06:42:30 UTC,It's now an issue here with both Ubuntu 18.04 and Xubuntu 18.04 although different amount of text not visible. Thunderbird 52.9.1.
1692378,2020-02-08 13:43:30 UTC,Recent Thunderbird releases now display 'Preferences' in a main window tab which greatly increases the space available to display text boxes and buttons. Closing as fixed.
1692378,2017-05-22 00:49:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692384,2017-05-22 01:51:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466563"
1692384,2017-12-12 07:36:46 UTC,"Change abandoned by yuyafei (<email address hidden>) on branch: master
Review: https://review.openstack.org/466563"
1692394,2016-10-08 20:24:48 UTC,*** Bug 772625 has been marked as a duplicate of this bug. ***
1692394,2018-04-28 18:37:54 UTC,"I currently experience this issue on an up-to-date 18.04 install. I came across this bug while googling for ""gnome volume overlay wobble"". It also affects the other two overlays that I can use (screen brightness and keyboard backlight.) I was able to record in in 60fps so as to make it more evident. Just wanted to share my experience on the most updated as possible Ubuntu."
1692394,2018-05-09 05:16:47 UTC,Looks like a fix is coming: https://bugzilla.gnome.org/show_bug.cgi?id=782011
1692394,2018-05-09 08:15:12 UTC,"I think the bug you're referencing is about blurriness from y position calculation.
I believe the upstream bug about left/right jittering is https://bugzilla.gnome.org/show_bug.cgi?id=772287"
1692394,2018-05-09 08:23:48 UTC,There is a fix for the left/right jittering in https://bugzilla.gnome.org/show_bug.cgi?id=782011
1692394,2016-10-01 12:21:30 UTC,"Created attachment 336725
screencast"
1692394,2018-06-06 11:03:50 UTC,"Created attachment 372570
osdWindow: change the centering calculation"
1692394,2018-07-11 11:10:46 UTC,*** Bug 782011 has been marked as a duplicate of this bug. ***
1692394,2018-07-26 03:38:04 UTC,Downstream: https://launchpad.net/bugs/1692394
1692394,2018-07-26 09:56:42 UTC,"slatchurie, could you turn this into a merge request on gitlab?"
1692394,2018-08-23 19:24:56 UTC,"It's possible that the issue has been fixed in https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/2, as the level bar is (once again) a custom drawn actor instead of a fill-level actor inside a trough actor."
1692394,2018-08-23 21:05:30 UTC,"I can still reproduce on 3.28.3, I can't really tell what version that merge request ended up in."
1692394,2018-08-23 21:12:59 UTC,"Sorry I haven't been more clear. The merge request wasn't about this issue at all, but about implementing a feature - it just happened that the involved refactoring touched (and replaced) the code that was previously identified to cause the jiggling, which is why it's possible that the issue is fixed."
1692394,2020-07-03 02:08:40 UTC,I haven't seen this in a long time.
1692394,2018-04-13 14:48:13 UTC,*** Bug 778546 has been marked as a duplicate of this bug. ***
1692394,2018-04-12 02:06:35 UTC,I don't recall seeing this in a while.
1692394,2018-06-05 09:19:37 UTC,Please see attachment 352891 in bug 782011 for a potential fix.
1692394,2017-11-20 19:10:11 UTC,"I wrote a big post with my versions of gjs, libmozjs, etc. Then discarded it by accident. :|"
1692394,2017-12-29 09:55:41 UTC,*** Bug 792023 has been marked as a duplicate of this bug. ***
1692394,2016-10-11 00:03:20 UTC,"Created attachment 337381
osdWindow: always round-up sizes when updating allocation"
1692394,2016-10-11 00:14:18 UTC,Review of attachment 337381:
1692394,2016-10-11 00:25:33 UTC,Attachment 337381 pushed as f819654 - osdWindow: always round-up sizes when updating allocation
1692394,2016-11-08 16:32:00 UTC,*** Bug 774088 has been marked as a duplicate of this bug. ***
1692394,2017-10-04 06:05:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692394,2017-11-15 19:23:46 UTC,"Created attachment 363743
Screenshot of OSD"
1692394,2016-11-13 17:36:36 UTC,*** Bug 774369 has been marked as a duplicate of this bug. ***
1692394,2017-11-15 19:58:33 UTC,You should reopen this bug if you can still demonstrate the same problem. A video of your system would be good to confirm it's likely the exact same thing.
1692394,2017-11-15 20:09:12 UTC,"Created attachment 363759
volume overlay jittering"
1692394,2017-11-15 20:26:33 UTC,"(In reply to Daniel Boles from comment #9)

> For the other issue - which ideally would have a textual description too,
> but presumably is incorrect placement/clipping of the graphics? - you should
> open a new bug report.
"
1692394,2017-11-19 20:37:27 UTC,"(In reply to Kadir from comment #8)

> BTW, my shell version is:
>
> gnome-shell.x86_64   3.26.2-1.fc27
"
1692394,2017-11-19 20:40:18 UTC,I can still see this issue on 3.26.2.
1692394,2017-11-20 17:41:06 UTC,"Created attachment 364064
Jitter at 1920x1200"
1692394,2017-11-15 19:32:03 UTC,"BTW, my shell version is:"
1692397,2017-12-09 00:46:43 UTC,"Hello Zhenyu, or anyone else affected,"
1692397,2017-11-20 18:30:05 UTC,Thanks Edward. I've uploaded to xenial [1] and it is now awaiting review by the SRU team.
1692397,2017-11-15 13:44:41 UTC,SRUing to Xenial/Mitaka (see bug 1719770 for more info)
1692397,2017-08-28 09:55:23 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1692397,2017-08-21 18:49:20 UTC,"Reviewed:  https://review.openstack.org/468528
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6dc2a0ec1cfe70bbf0f50a36bca5d2794e34e1b1
Submitter: Jenkins
Branch:    stable/newton"
1692397,2017-05-26 19:59:08 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/468528"
1692397,2017-06-08 21:52:00 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1692397,2017-05-27 02:59:55 UTC,"Reviewed:  https://review.openstack.org/468526
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=74e2a400b2ea3b011f88a7dbd8bb0fa3547b3bfa
Submitter: Jenkins
Branch:    stable/ocata"
1692397,2017-05-26 19:48:05 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/468526"
1692397,2017-05-26 19:04:49 UTC,"Reviewed:  https://review.openstack.org/467220
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3d3e9cdd774efe96f468f2bcba6c09a40f5e71d3
Submitter: Jenkins
Branch:    master"
1692397,2017-05-25 02:01:31 UTC,"Looks like it doubled everything when you restarted the compute service, is it reporting 2 compute nodes records instead of one for that single service (or vice-versa)?"
1692397,2017-06-19 12:45:59 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1692397,2017-05-23 12:50:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467220"
1692397,2017-12-18 18:24:26 UTC,This bug was fixed in the package nova - 2:13.1.4-0ubuntu4.2
1692397,2017-12-12 11:21:21 UTC,Verified using testcase in description.
1692397,2018-01-10 19:59:39 UTC,"This bug was fixed in the package nova - 2:13.1.4-0ubuntu4.2~cloud0
---------------"
1692397,2018-01-10 19:59:37 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1692397,2018-01-10 19:55:16 UTC,This has also been regression tested successfully for trusty-mitaka-proposed and xenial-mitaka-proposed:
1692397,2018-01-04 11:49:22 UTC,Verified trusty-proposed/mitaka using test case in bug description.
1692397,2018-01-02 15:25:01 UTC,"Hello Zhenyu, or anyone else affected,"
1692397,2017-12-18 18:24:43 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1692410,2017-06-27 02:49:57 UTC,"This is a bug confirmed by developers, see
https://github.com/Motion-Project/motion/issues/389
for workaround and details."
1692410,2017-05-22 16:55:26 UTC,"No, it does. Was not reproducing it properly. Attaching a core dump along with the binary."
1692410,2017-05-22 16:04:47 UTC,A follow-up: motion 4.0.1+gitc50d4b5 doesn't crash. That's motion's @master as of now.
1692419,2017-05-31 14:33:57 UTC,It looks like networking-ovn side.
1692437,2018-01-31 05:49:46 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1692437,2017-06-03 23:15:18 UTC,Some more information:
1692437,2017-06-01 17:10:46 UTC,"I'm beginning to think this is a driver issue. I have a builtin ""Kaveri"" amd gpu, and pci Radeon HD 4850. I usually have the 4850 as my primary card/monitor setup. However, since upgrading to Ubuntu 17.04, once lightdm is started, only the monitor on the Kaveri works."
1692437,2017-05-22 17:10:13 UTC,"lspci and lshw show 2 GPUs. The builtin one, and the actual card, but xrandr only lists one provider."
1692437,2017-07-28 17:38:17 UTC,Is there anything I can do to move this along?
1692437,2019-02-01 21:08:15 UTC,I've come across this again after upgrading to 18.10
1692437,2019-02-01 21:56:38 UTC,"I filmed my computer boot up to better show what happens. The right monitor is on the integrated video card (the R7), and doesn't show anything initially. The center and left monitor turn on and mirror each other during boot, and show grub and most of the kernel and systemd messages, then at some point all output is sent to the right monitor. I believe the systemd log says something along the lines of ""detecting all video cards"" at that point."
1692437,2019-02-04 02:41:31 UTC,"After going on the #radeon channel on Freenode, we narrowed the problem down to the switcheroo-control package. We started by hand making an xorg.conf file and disabling gpu-manager, but still had issues. Looking at the dmesg log, we saw that the discrete gpu is enabled at first, then disabled sometime in the systemd start up. After trying to disable various things, including switcheroo, from the kernel parameters and having the problem still occur, we narrowed it down to being a service that was writing to `/sys/kernel/debug/vgaswitcheroo/switch`. I looked at my enabled services, and saw `switcheroo-control`, after disabling, everything started working again."
1692437,2019-02-03 21:34:24 UTC,Added gpu-manager log
1692441,2017-09-21 13:23:23 UTC,"TODO:
1. retry with the related Delta dropped, if it works good, if not we need to find the fix to reload the profile as suggested in the mail thead
2. once that is complete consider creating a separate issue for blkcommits/snapshots like
   virsh snapshot-create-as --domain xenial-testblockcommit snap1 --diskspec vdc,snapshot=external,file=/tmp/xenial-testblockcommit-testdevice-snap1.qcow --disk-only --atomic --no-metadata"
1692441,2017-09-21 12:51:58 UTC,"Some docs on the gereral use case:
- http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit
- http://wiki.libvirt.org/page/Live-merge-an-entire-disk-image-chain-including-current-active-disk"
1692448,2017-05-24 08:26:02 UTC,I finally tested:
1692450,2017-06-14 12:59:25 UTC,"------- Comment From <email address hidden> 2017-06-14 08:48 EDT-------
Hi Christian,"
1692450,2018-02-08 13:03:27 UTC,"This is targetted at 18.10 now, are there new package version requirements?"
1692450,2019-10-08 18:02:36 UTC,Thanks Michael. Closing out.
1692450,2019-10-08 16:29:32 UTC,"------- Comment From <email address hidden> 2019-10-08 12:24 EDT-------
Everything for this support did go upstream is already part of 19.10 so we can close."
1692450,2019-08-27 13:59:21 UTC,We are now past feature freeze for 19.10. Should this be re-targeted to 20.04?
1692450,2019-08-05 14:12:29 UTC,Note: Feature Freeze for 19.10 is 22nd August.
1692450,2019-03-13 20:39:28 UTC,"------- Comment From <email address hidden> 2019-03-13 16:28 EDT-------
This is still being discussed upstream."
1692450,2018-03-19 14:26:50 UTC,Since this is an 18.10 feature request marking priority a low for now.
1692450,2018-02-26 14:54:50 UTC,"From comment #7, waiting for ""XIVE in a guest"" support to land upstream."
1692450,2018-02-14 18:10:19 UTC,"------- Comment From <email address hidden> 2018-02-14 13:01 EDT-------
XIVE in a guest is not yet available upstream."
1692450,2017-05-22 08:50:21 UTC,"Hi,
thanks for starting the tracking of all related changes.
Is this in qemu 2.9, if not is it at least upstream and which are the related commits?"
1692450,2017-05-22 08:55:36 UTC,"Hi,
especially for new features I assume that you'll do the testing, but some sort of extra info on ..."
1692450,2017-06-14 09:36:00 UTC,Ping - Since 2.10 likely will be too late to make 17.10 polling for related commit ID's for p9 support
1692450,2017-06-14 09:36:43 UTC,"Also this might be 18.04 according to the tagging, but if known and ready please let me know."
1692450,2018-08-17 19:29:26 UTC,"------- Comment From <email address hidden> 2018-08-17 15:23 EDT-------
Feature still being worked upstream. Postponing to Ubuntu 19.04."
1692458,2019-07-01 14:29:53 UTC,"------- Comment From <email address hidden> 2019-07-01 10:27 EDT-------
Current progress: I chose to split the patch series into smaller chunks to make it easier to review and to be pushed. First part, 10 patches (out of 30) was sent to the Libvirt mailing list last Wednesday, June 26th [1]. It is still pending review. Before sending this first part I've sent a RFC to the mailing list reviving the discussion [2], and the community seems to approve it (or, at least, not rejecting it fiercely)."
1692458,2019-07-01 17:42:53 UTC,It's your targets/milestones - if 20.04 makes more sense for your upstreaming (and it seems it does) that seems fine for us.
1692458,2019-08-05 13:44:16 UTC,Moving to target 20.04.
1692458,2019-08-19 06:12:38 UTC,FYI: see [1] and related posts for further upstream activity.
1692458,2019-09-13 12:20:09 UTC,"------- Comment From <email address hidden> 2019-09-13 08:12 EDT-------
The first set of patches of the feature was pushed to Libvirt this last Monday, Sept 9th. The set contained enhancements/fixes in the test framework for the more sophisticated PCI multifunction tests that will come."
1692458,2020-01-13 13:50:10 UTC,"Hi,
I have not seen the final code in v6.0.0 of libvirt.
Was it renamed so I can't find it or didn't it make upstream yet?"
1692458,2020-01-13 16:37:58 UTC,Thx 'danielhb' for the feedback - changing ticket now to 20.10.
1692458,2020-01-30 17:03:41 UTC,"------- Comment From <email address hidden> 2020-01-30 11:52 EDT-------
Feature was submitted for approval as v2:"
1692458,2020-08-06 06:32:28 UTC,I can't find it in libvirt 6.6 even - unless there were massive renames this didn't land upstream yet. Please let us know if it already did or if there is anew schedule/plan to get it landed.
1692458,2020-08-17 16:20:35 UTC,"------- Comment From <email address hidden> 2020-08-17 12:17 EDT-------
According to development, patches are not ready for 20.10,  therefore moving target to 21.04."
1692458,2021-01-11 15:54:24 UTC,"Scanning the upstream libvirt git tree (https://libvirt.org/git/?p=libvirt.git) it looks like the patch set ""[PATCH v2 00/21] PCI Multifunction hotplug/hotunplug support"" is still not upstream accepted, i.e. not with libvirt 6.9 (which is the planned libvirt target release for hirsute/21.04).
Hence it's very unlikely that this can be picked up by and delivered with Ubuntu 21.04 (hirsute)."
1692458,2019-05-13 14:19:47 UTC,Updated title to reflect new 19.10 target.
1692458,2020-01-13 15:30:51 UTC,"------- Comment From <email address hidden> 2020-01-13 10:25 EDT-------
Hey,"
1692458,2019-03-26 14:33:48 UTC,Marking as incomplete while waiting for the patchsets to land upstream.
1692458,2017-09-14 14:59:31 UTC,"------- Comment From <email address hidden> 2017-09-14 10:55 EDT-------
Madhu,"
1692458,2018-12-06 07:19:30 UTC,"------- Comment From <email address hidden> 2018-12-06 02:13 EDT-------
The latest patch set is here:
https://www.redhat.com/archives/libvir-list/2018-March/author.html#00729"
1692458,2017-05-22 09:21:02 UTC,"Hi,
thanks for opening this bug to track that work.
I read this is known to be incomplete yet, please let us know when there is any code/release that be considered for inclusion."
1692458,2017-06-14 09:35:48 UTC,Ping - Polling for related commit ID's for p9 support
1692458,2019-03-26 14:33:17 UTC,"From looking at the maillist in comment #16, it would appear that this patchset is still in discussion."
1692458,2017-06-14 15:34:26 UTC,"Thanks to clarify - I expected just as much but wanted to be sure.
So we keep it open and incomplete for now and might punt it to 18.04 later on if it takes more time."
1692458,2017-07-20 09:09:27 UTC,"------- Comment From <email address hidden> 2017-07-20 05:08 EDT-------
*** Bug 156863 has been marked as a duplicate of this bug. ***"
1692458,2017-07-20 09:52:26 UTC,"The mentioned ""Bug 156863"" is obviously a bugzilla bug.
Is it also a duplicate of another bug in Launchpad?"
1692458,2017-08-07 19:29:41 UTC,"------- Comment From <email address hidden> 2017-08-07 15:22 EDT-------
(In reply to comment #22)

> The mentioned ""Bug 156863"" is obviously a bugzilla bug.
> Is it also a duplicate of another bug in Launchpad?
"
1692458,2017-06-14 14:19:47 UTC,"------- Comment From <email address hidden> 2017-06-14 10:16 EDT-------
Hi Christian,"
1692458,2018-02-12 05:30:07 UTC,"------- Comment From <email address hidden> 2018-02-12 00:27 EDT-------
@shiv will this be targeted for Ubuntu 18.04?"
1692458,2018-02-12 22:00:30 UTC,Looks like we are still waiting on the code to be upstreamed. Any updates on the upstream status ?
1692458,2018-02-14 18:50:01 UTC,"------- Comment From <email address hidden> 2018-02-14 13:40 EDT-------
This is not upstream yet. Shiva is working on it."
1692458,2018-08-20 13:45:45 UTC,"IBM, 18.10 feature freeze is on the 23rd of Aug, any news on the upstream status of this patch?"
1692458,2017-10-03 14:10:46 UTC,"------- Comment From <email address hidden> 2017-10-03 09:51 EDT-------
Hi Leonardo, This is not yet upstream, and will be too late for 17.10, so re-targeting to 18.04."
1692458,2018-11-19 14:44:05 UTC,Have the patches made its way upstream? if so could you please post those links here?
1692458,2018-08-21 17:49:26 UTC,"------- Comment From <email address hidden> 2018-08-21 01:20 EDT-------
Patches posted upstream and pending review."
1692471,2017-05-22 16:01:13 UTC,My suggestion doesn't work because grub-mkconfig is ran with dash and not bash.
1692471,2017-05-23 14:42:44 UTC,"The correct solution is to use the following:
GRUB_CMDLINE_LINUX_DEFAULT=""$GRUB_CMDLINE_LINUX_DEFAULT console=tty1 console=ttyS0"""
1692471,2020-11-13 01:48:44 UTC,"Just jumping in here to add that the provided suggestion by YKorman above, does not work."
1692473,2017-05-22 21:22:45 UTC,"Hi. 1) Please post your issue on the Github project page. The project has moved there, as the notice on the home page states. 2) Make sure you've tried the latest Nuget/Git version of the library. 3) Provide code or at least more detail on how to reproduce this."
1692475,2017-05-22 23:08:20 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1692481,2017-05-25 11:14:11 UTC,"Review in progress for https://review.opencontrail.org/32082
Submitter: Pavani (<email address hidden>)"
1692481,2017-05-24 11:29:08 UTC,"Review in progress for https://review.opencontrail.org/32082
Submitter: Pavani (<email address hidden>)"
1692481,2017-05-24 10:50:09 UTC,"Review in progress for https://review.opencontrail.org/32079
Submitter: Pavani (<email address hidden>)"
1692481,2017-05-25 09:42:46 UTC,"Review in progress for https://review.opencontrail.org/32145
Submitter: Pavani (<email address hidden>)"
1692484,2020-08-09 04:17:34 UTC,[Expired for tempest because there has been no activity for 60 days.]
1692484,2017-05-22 10:23:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466665"
1692484,2017-11-07 23:26:40 UTC,"Change abandoned by Andrea Frittoli (<email address hidden>) on branch: master
Review: https://review.openstack.org/466665
Reason: Already fixed elsewhere"
1692484,2017-05-22 11:32:09 UTC,"SSL settings are actually already passed, but http_timeout is not."
1692484,2017-05-23 01:13:18 UTC,"When you have finished updating the patch, I'd like to help test it locally."
1692484,2020-06-09 14:42:07 UTC,"Moving to Incomplete as there has been no activity for more than 2 years already  and due to tons of changes which have been merged since then. Can you still reproduce the issue on the current master branch? If so, feel free to reopen the issue with the current issue description. Thanks"
1692487,2017-05-22 23:12:55 UTC,"Hello,"
1692487,2017-05-22 23:12:14 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1692487,2017-05-22 23:24:00 UTC,Thank you for your reply and kind help.
1692492,2017-06-12 05:59:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692494,2017-05-22 12:30:22 UTC,"The attachment ""add-reboot-argument-support.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1692494,2017-05-25 08:32:22 UTC,Add a slightly modified version of the patch.
1692494,2017-05-31 06:39:21 UTC,Reported to debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863761
1692494,2018-07-16 06:58:28 UTC,The patch has been included in Debian klibc package 2.0.4-12:
1692494,2019-01-21 20:58:29 UTC,This bug was fixed in the package klibc - 2.0.5-2
1692494,2017-09-12 10:05:54 UTC,"It looks like both upstream and debian are not being responsive, looks like klibc has no maintainer in neither of those. Should we add this patch to the Ubuntu package?"
1692507,2017-07-24 10:01:13 UTC,Fixed with https://review.openstack.org/#/c/433480/
1692507,2017-11-25 00:33:38 UTC,I wiped /etc/ansible and re-installed kolla-ansible to fix this issue.
1692507,2017-07-24 10:02:08 UTC,"Change abandoned by Eduardo Gonzalez (<email address hidden>) on branch: master
Review: https://review.openstack.org/485217
Reason: Fixed with https://review.openstack.org/#/c/433480/"
1692507,2017-07-05 14:19:11 UTC,"mariadb optimize reconfiguration was not merged yet, so the issue is with the serial removal.
https://review.openstack.org/#/c/433480/"
1692507,2017-06-22 11:17:05 UTC,Enabling serial in mariadb fixes the issue. The problem is that restarting all mariadb containers at the same time loose cluster quorum.
1692507,2017-06-22 11:02:54 UTC,"Upgrade from newton to ocata worked.
Upgrade from ocata to pike(master) fail."
1692507,2017-05-25 11:28:01 UTC,Allinone upgrade worked.
1692507,2017-05-25 10:39:29 UTC,"Tried several times today with ansible2.3 and ansible2.1.0.
Cannot find the root cause of this issue"
1692507,2017-07-05 13:37:38 UTC,"Looking into mariadb role changes, seems that optimized reconfiguration breaks mariadb cluster lookup order while upgrading and do a restart of all mariadb containers at the same time causing cluster quorum issues."
1692511,2017-05-22 13:22:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/466729"
1692511,2017-07-09 03:33:42 UTC,"Change abandoned by Yuriy Zveryanskyy (<email address hidden>) on branch: master
Review: https://review.openstack.org/466729"
1692511,2018-03-16 20:46:59 UTC,"Reviewed:  https://review.openstack.org/466729
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=d81d2e7736cde319e5cb9ff8db334df1af264d84
Submitter: Zuul
Branch:    master"
1692521,2017-05-22 13:03:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466725"
1692521,2017-08-01 09:52:40 UTC,"Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/466725
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1692521,2017-08-01 10:15:22 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1692532,2017-05-22 13:59:20 UTC,Missing attachment.
1692535,2017-05-22 14:30:07 UTC,This change was made by a bot.
1692541,2018-04-11 15:02:27 UTC,"Yes, I can reproduce it in bionic too."
1692542,2017-05-23 16:46:06 UTC,"Reviewed:  https://review.openstack.org/466749
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=f83d6ffcfa5331e97d05536d6fa481efdf31ef1b
Submitter: Jenkins
Branch:    master"
1692543,2017-06-27 14:27:57 UTC,"This patch fixes the tests for me. Turns out that we can't simply skip writing to path_max as that seems to break the test case completely, so I changed it to print an XFAIL message and abort the test."
1692543,2017-06-22 20:22:10 UTC,"yes something like this should work. However 600 will not be the correct check, as in some cases the owner may differ, especially in the virtualized case because vfs doesn't let us virtualize the file's owner."
1692543,2017-05-22 20:55:38 UTC,"This is caused do a change made upstream in the 4.11 kernel, which forbids writing the buffer size parameter after boot. The change to boot time preallocated work buffers made this parameter useless, but 4.11 only partially merged that work, making writing the buffer size an attack vector on the kernel memory and with user namespaces enabled any user could exploit it. Hence a follow-on patch to make the buffer size read-only after boot."
1692543,2017-06-23 21:17:07 UTC,Something more like this then.
1692543,2017-06-22 19:31:21 UTC,"What if the test was changed to check writability of path_max? Just changing the the check for the sysfs path to -w won't work for root, but maybe something like this (perhaps there's a simpler way to do the check though):"
1692544,2017-06-10 23:57:42 UTC,"synaptic says xfce4-weather-plugin installed is version 0.8.6-1 and according to http://goodies.xfce.org/projects/panel-plugins/xfce4-weather-plugin version 0.8.9 is latest version; also worth mentioning version 0.8.8 notes mention: ""Use https://api.met.no, old site has been deprecated and will no longer work"""
1692545,2017-05-22 14:58:57 UTC,"I'd not ever expect these devices to have network data describing them - even in a KVM instance, they are in the domain of control of the user of the instance, not the operator of the cloud."
1692550,2018-05-23 03:48:37 UTC,"I was about to make this same request again, when I found I already had made it, haha!"
1692550,2019-12-09 07:56:52 UTC,Migrated to:  https://gitlab.com/inkscape/inbox/issues/1323
1692566,2017-08-03 06:56:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692582,2017-05-22 17:06:00 UTC,"If I'm reading the AppArmor user-space source code correctly, if backwards compatibility wasn't a concern then this could be achieved by adding an additional user-defined field to vec in dbus_rule::gen_policy_re(Profile&) and passing the new number of fields to add_rule_vec(), then adding that same field to the queries built by dbus-daemon in bus/apparmor.c build_message_query()."
1692582,2017-05-22 17:17:32 UTC,The message type certain could be added. However it is not the only way this separation can be achieved.
1692582,2017-05-22 17:42:10 UTC,"There are actually a couple of ways to add it, and still keep userspace compatibility. Kernel side we are actually often checking partial matches, and due is a permission but AA_CONTINUE to indicate that if permissions aren't satisfied to continue the match."
1692582,2017-05-22 17:52:49 UTC,"> 1. the label name on a service does not have to match its executable name so an executable could be labeled with a more generic profile
"
1692582,2017-05-22 17:59:57 UTC,"I think performance, and flexibility wise, the best solution would be to move mediation entirely to userspace."
1692582,2017-05-22 18:25:48 UTC,"@Simmon,"
1692582,2017-05-23 14:21:58 UTC,"> What time frame are you looking for to land fixes for this
"
1692607,2019-09-19 11:53:13 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1692650,2017-05-22 20:40:51 UTC,The size of the document is determined by libcdr [1].
1692650,2017-05-22 20:48:24 UTC,"fwiw, if you interpret the 1700.7874 as pt rather than px, then you get the right size.
i.e. perhaps Inkscape needs to do an internal conversion from pt to px similar to what is normally done for pdf files"
1692650,2017-05-22 20:29:48 UTC,"confirmed on Windows 10, Inkscape 0.92.1 r15371"
1692661,2017-05-22 23:39:23 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1692661,2017-05-22 18:34:06 UTC,"StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
 __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
 std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
 __cxxabiv1::__cxa_throw (obj=obj@entry=0x55e0d74b4ff0, tinfo=tinfo@entry=0x7fbfbd5a7c70 <typeinfo for google::protobuf::FatalException>, dest=dest@entry=0x7fbfbd20b990 <google::protobuf::FatalException::~FatalException()>) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:93
 google::protobuf::internal::LogMessage::Finish (this=0x7fff3d7b35e0) at google/protobuf/stubs/common.cc:259"
1692693,2017-05-22 19:54:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/466884"
1692693,2017-05-24 05:40:49 UTC,"Reviewed:  https://review.openstack.org/466884
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=007d4cbfdd4cfa3764b2b9789f129f2aae654a66
Submitter: Jenkins
Branch:    master"
1692693,2017-05-31 14:20:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469510"
1692693,2017-06-01 02:41:28 UTC,"Reviewed:  https://review.openstack.org/469510
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=45b9769212a7cdf61e44158395f3b97353feb7c0
Submitter: Jenkins
Branch:    stable/ocata"
1692693,2017-06-07 15:45:20 UTC,This issue was fixed in the openstack/heat 9.0.0.0b2 development milestone.
1692693,2017-06-12 13:25:43 UTC,This issue was fixed in the openstack/heat 8.0.2 release.
1692702,2018-09-14 09:58:05 UTC,"It has happened with 19. A long inactivity caused a screen lock, and it prompts a password for ""Live session user"". It doesn't work by simply typing enter."
1692702,2018-09-14 10:02:32 UTC,"..sorry, that was a wrong information. The user was actually using a Mint 12 when that happened. I will try to replicate it on 19 just to be sure."
1692712,2017-05-22 20:58:30 UTC,"I'm not sure what you mean. Currently language-selector-gnome does depend on aptdaemon, even if it soon may be changed due to bug #1673258."
1692712,2017-06-01 18:04:15 UTC,"On 2017-05-22 22:58, Gunnar Hjalmarsson wrote:

> Marking this as a duplicate of that other bug
"
1692755,2019-05-25 04:41:20 UTC,This has been fixed.
1692765,2017-05-23 08:37:35 UTC,"So this is when there's no output from any stages, right? How about making it green only if the following command has some output? And/ or alternating colors, say blue and green?"
1692771,2017-08-27 18:31:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692771,2021-01-07 04:15:25 UTC,4.8 EOL
1692778,2017-09-22 15:05:04 UTC,Should be fixed since 4ppa42.
1692778,2020-10-03 18:57:01 UTC,Still happens to me. Newly installed from ppa.
1692784,2018-10-10 03:39:05 UTC,"I'm experiencing the crashes since upgrade to 5.0.1-1.  Work around has been to wait for auto-save to run before clicking the confirmation message after the download completes.  If I do that, KMyMoney crashes when I click OK, but I can relaunch and my downloaded transactions are there."
1692784,2018-06-27 19:15:56 UTC,I am also experiencing crashes on import since upgrading to Ubuntu 18.04 / kmymoney 5.0.1-2. I haven't use gdb yet but I have gotten the following:
1692784,2018-06-27 19:10:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692784,2018-10-10 14:09:02 UTC,"Another work around is to download the transactions file to your hard drive, and then use the File->Import menu to import it, rather than having your web browser attempt to open the file with KMyMoney."
1692793,2020-04-29 05:34:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692815,2017-06-29 08:59:30 UTC,Can you please be more specific? I can't figure out from your mail what you mean. :)
1692817,2017-05-24 02:25:17 UTC,"Hi,
Thank you for report this issue i just noticed that the music service provider just changed the API again and makes it harder to get the audio url, i will try to fix it."
1692831,2017-06-01 00:05:29 UTC,Can you reproduce the issue?
1692844,2018-01-18 08:11:07 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1982
1692844,2017-05-25 09:47:24 UTC,"Thanks for the reply,there is 'innodb_data_home_dir=' in the /etc/my.cnf."
1692844,2017-05-23 22:02:23 UTC,Thank you for the report.
1692844,2017-05-24 09:35:11 UTC,Here is my whole log:
1692844,2017-05-24 00:26:04 UTC,"Hi, expert,there is my environment.
this is my configuration file:
[mysqld]
datadir=/var/lib/mysql
user=mysql
wsrep_provider=/usr/lib64/galera3/libgalera_smm.so
wsrep_cluster_name=pxc-cluster
wsrep_cluster_address=gcomm://98.0.15.31,98.0.15.32,98.0.15.33
innodb_buffer_pool_size=16M
innodb_data_home_dir=
innodb_data_file_path=/dev/raw/raw2:500Mnewraw
wsrep_node_name=pxc1
wsrep_node_address=98.0.15.31
wsrep_sst_method=xtrabackup-v2
wsrep_sst_auth=sstuser:123456
pxc_strict_mode=ENFORCING
binlog_format=ROW
default_storage_engine=InnoDB
innodb_autoinc_lock_mode=2"
1692844,2017-05-25 09:39:43 UTC,Thank you for the feedback.
1692844,2017-05-24 09:25:19 UTC,"Then ,I change a new way to create a raw device.I add a new disk to my virtual machine and reboot my vm.
Then I get a new clear disk: sdb.
I bind it to the raw device.
raw /dev/raw/raw1 /dev/sdb
chown mysql:mysql /dev/raw/raw1
chmod 660 /dev/raw/raw1"
1692860,2017-05-23 10:35:37 UTC,"Looks like the relevant code is here, where it has a 64 character limit:"
1692865,2018-10-24 18:47:59 UTC,"With i18n including the dependency, does Keystoneclient also need it explicitly?"
1692865,2018-01-24 13:07:46 UTC,"I checked the Ubuntu packages for python(3)-oslo.i18n back to Kilo and they all have python(3)-babel as a dependency, so marking as invalid for the Ubuntu packages."
1692865,2018-01-11 20:10:00 UTC,I've marked the corresponding upstream projects as affected by this bug in order to get their input.
1692865,2017-05-24 00:55:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692865,2018-01-22 16:34:34 UTC,The latest version of oslo.i18n does include babel in its requirements list.
1692869,2017-05-23 22:22:40 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1692869,2017-06-06 21:41:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692870,2017-05-23 12:28:55 UTC,"The attachment ""New version with patch included."" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1692870,2017-05-23 13:31:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692870,2017-06-17 12:45:35 UTC,"I tried to simulate the issue with Tomcat 7.0.77 (which is the version UniFi uses), but I was unable to simulate this on Ubuntu 17.04."
1692870,2017-06-21 20:40:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1692870,2017-08-17 15:22:04 UTC,Why does your debdiff drop the use-dso patch?  Can you confirm that *not* disabling the use-dso patch still lets this work for you?
1692870,2017-08-17 15:22:23 UTC,"Sorry, you already addressed this in comment #4."
1692870,2017-08-17 15:24:25 UTC,"For SRU, this is going to need a better test case."
1692870,2017-08-22 22:47:13 UTC,This bug was fixed in the package zlib - 1:1.2.11.dfsg-0ubuntu2
1692885,2017-07-02 22:18:15 UTC,This bug was fixed in the package ukui-control-center - 1.0.3-0ubuntu1
1692900,2017-06-28 16:35:34 UTC,This bug was fixed in the package linux - 4.4.0-83.106
1692905,2017-06-16 00:25:08 UTC,Ok thanks!
1692905,2017-05-23 15:42:52 UTC,It hasn't always been like this - this bug was introduced with https://github.com/juju/juju/pull/7324.
1692905,2017-05-23 15:09:43 UTC,"I believe if we get a hostname we explicitly try to resolve it, and if that
fails we omit it. This is because MAAS frequently return hostnames that
only MAAS can resolve and not everyone configures their laptops to point at
MAAS DNS."
1692905,2017-06-15 07:27:17 UTC,This was fixed by PR 7438.
1692905,2017-06-15 03:57:51 UTC,"If I try the repro steps ""juju list-models"" works for me. What's different?"
1692917,2017-05-23 14:57:47 UTC,"I previously made a GitHub issue out of this, but as it has been largely ignored it must be better to create a launchpad report instead."
1692920,2017-05-25 12:42:07 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-May/084390.html
1692920,2017-06-06 16:48:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1692956,2017-07-11 10:02:09 UTC,I think we have fixed this in https://review.openstack.org/#/c/467787/
1692956,2017-07-12 16:51:16 UTC,Thanks for checking ChangBo!  Looks good.
1692962,2017-05-23 15:48:27 UTC,Fixed in pike development under:
1692962,2017-05-24 16:45:16 UTC,This bug was fixed in the package nova-lxd - 16.0.0~b2~git20170524.5223204-0ubuntu1
1692962,2017-06-02 09:04:54 UTC,"Reviewed:  https://review.openstack.org/467292
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=6e57a5a2d25d8986ff85b25bc1ab991fc3411ed0
Submitter: Jenkins
Branch:    stable/ocata"
1692962,2017-06-16 10:22:55 UTC,"Hello James, or anyone else affected,"
1692962,2017-06-22 08:03:20 UTC,"Tested with version in zesty-proposed, worked for me!"
1692962,2017-07-05 01:22:31 UTC,This bug was fixed in the package nova-lxd - 15.0.2-0ubuntu1
1692962,2017-07-05 01:22:38 UTC,"The verification of the Stable Release Update for nova-lxd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1692971,2017-06-15 09:05:51 UTC,"Change abandoned by Thomas Morin (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/470430
Reason: mitaka is EOL since 2017-04-10"
1692971,2017-06-12 10:16:42 UTC,"Reviewed:  https://review.openstack.org/470428
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a08aa3bf2f567d4d0a5678d470cc3a3aec382d74
Submitter: Jenkins
Branch:    stable/ocata"
1692971,2017-06-08 10:24:38 UTC,"Change abandoned by Cristian Calin (<email address hidden>) on branch: master
Review: https://review.openstack.org/468421
Reason: Discussion is going nowhere based on feelings"
1692971,2017-06-06 23:27:46 UTC,"Reviewed:  https://review.openstack.org/470429
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e6c1d6dc0f80a27eba29009cf7a6bf7be3bb9c75
Submitter: Jenkins
Branch:    stable/newton"
1692971,2017-06-02 20:21:06 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/470429"
1692971,2017-06-02 20:20:53 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/470428"
1692971,2017-06-02 13:50:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/470295"
1692971,2017-05-26 08:17:31 UTC,Assigning to myself to push patch for review.
1692971,2017-06-03 02:25:25 UTC,"Reviewed:  https://review.openstack.org/470295
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a858ca7d8fdd625524859b723b9ce3fdb747b6b6
Submitter: Jenkins
Branch:    master"
1692971,2017-06-02 20:21:20 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/470430"
1692991,2017-06-19 20:16:58 UTC,"Technically, confirmed for openstack-manuals, but as http://lists.openstack.org/pipermail/openstack-dev/2017-June/118055.html is implemented, the origin of this content will change."
1693000,2017-05-23 18:50:12 UTC,AppCenter tracks its issues in GitHub. Please report your issue here: https://github.com/elementary/appcenter/issues
1693005,2017-10-16 12:30:15 UTC,"Related fix proposed to branch: feature/s3api
Review: https://review.openstack.org/512277"
1693005,2017-09-21 02:50:01 UTC,"Reviewed:  https://review.openstack.org/505844
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=67b3a747869ad1727d88cb77fa65858a3c98f8a5
Submitter: Jenkins
Branch:    feature/deep"
1693005,2017-09-20 22:57:27 UTC,"Related fix proposed to branch: feature/deep
Review: https://review.openstack.org/505844"
1693005,2017-09-15 06:51:43 UTC,"Reviewed:  https://review.openstack.org/458070
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=163fb4d52a85e0467c8c6b616e2cd9faa1faa41b
Submitter: Jenkins
Branch:    master"
1693005,2017-10-16 16:50:07 UTC,"Change abandoned by Alistair Coles (<email address hidden>) on branch: feature/s3api
Review: https://review.openstack.org/512283
Reason: I was just trying to get sensible topic"
1693005,2017-10-16 12:42:17 UTC,"Related fix proposed to branch: feature/s3api
Review: https://review.openstack.org/512283"
1693005,2017-10-18 18:55:09 UTC,"Reviewed:  https://review.openstack.org/512277
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=f94d6567a7e2e8b3ca1168b4a41c42c1ee371af5
Submitter: Zuul
Branch:    feature/s3api"
1693027,2017-05-23 21:48:21 UTC,"could you attach the svg file that is causing the problem, for testing purposes?"
1693027,2017-05-23 23:27:38 UTC,"This is a sample file reproducing the issue. I have copied the objects, which cause this problem. Small white objects on black background."
1693027,2017-05-24 02:12:38 UTC,"thanks for the file,
confirmed on Windows 10, Inkscape 0.92.1 r15371"
1693027,2017-05-24 07:55:54 UTC,"I guess this is a relevant piece of information: I have many such circles in my file. And these circles were originally generated in a separate python script. I generate repeating patterns in a script, because it is easier. Then I copied those shapes (all circles) into another inkscape SVG file. It might be that copying from plain SVG (generated by script) into inkscape SVG might be an issue, which then displayed itself during DXF export."
1693027,2017-05-24 12:45:12 UTC,"Thank you for the last comment. I could not figure out how you got the mm units into the specification of (for example)
r=""0.0015875002mm""
The Inkscape gui does not seem to support the use of such units when drawing a circle by hand, although it does interpret them if they are typed in manually using the XML editor. So this needs to be fixed in the dxf output."
1693027,2017-12-21 17:33:15 UTC,"Experincing problem with SVG To DXF convertion to UCCNC.
Attachment file in UCCNC.
ralphd3g"
1693027,2017-12-21 18:08:56 UTC,"Added Information
Generial:"
1693027,2017-12-21 19:24:35 UTC,@Ralph - could you attach the svg file that you are converting to dxf?
1693027,2017-05-24 13:15:34 UTC,separate report is Bug #1693200
1693030,2017-05-24 09:40:25 UTC,It is strange it is appearing as both a network mount and a local mount (different icons).  I have just tried setting up a nfs share mount (with default options) and I only get a network mount entry.
1693030,2017-05-24 14:49:34 UTC,"No, both entries point to the same location and show the same disk space data"
1693030,2017-05-24 18:18:42 UTC,"I have confirmed that it is the x-systemd.automount option that is causing this.  I note the duplicate sidebar entries also occur in (at least) PCManFM and Thunar but not Dolphin so it is not specifically a Pantheon Files bug.  I suspect it is a ""feature"" of systemd and gvfs so any filemanager using gvfs and GVolumeMonitor will experience this.  It may be possible to work around this by detecting entries in the Device list with the same path and only showing one."
1693040,2017-05-23 22:14:15 UTC,This signature is created in apport's report.py in the function crash_signature.  The doc strings includes the following:
1693040,2017-05-23 22:16:10 UTC,Some research should be done into the scope of the problem and how possible it is to clean up any incorrect duplication / consolidation.
1693043,2018-02-28 05:51:54 UTC,It's not specific to Ubuntu.
1693050,2020-03-25 20:50:52 UTC,"According to [1], this is still an issue today."
1693050,2020-03-26 18:54:26 UTC,"Odd, this should be fixed by commit 6ee021d41 and 36960b4d66..98f52cdbb5c."
1693050,2020-03-26 21:16:08 UTC,"According to Duncan, it’s not, and the paragraph from the original issue still applies."
1693063,2017-05-24 20:38:09 UTC,"It's the ""My portfolios"" block that is in question here."
1693064,2017-06-14 08:47:36 UTC,"Seems only DEBUG messages, no ERROR messages."
1693064,2017-11-09 06:44:07 UTC,"Since the change https://review.openstack.org/#/c/283695/, multi-attach for RBD had been disabled."
1693109,2018-09-09 13:40:52 UTC,Has this been addressed? I am trying to search for a word in Spanish in a huge document and I can put a diacritic so the search is broken for me. Searching for the letters before the diacritic is pointless since I am getting too much results.
1693110,2017-05-24 06:57:18 UTC,thanks for finding.
1693117,2017-05-26 00:53:35 UTC,"Yes, it is a documentation problem."
1693119,2017-05-26 19:44:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693122,2017-06-01 00:22:44 UTC,"I mean, it is a database service and 99% of the times can be, or it is used from the network.
In the mongodb configuration mongodb.conf:"
1693122,2017-06-01 00:54:36 UTC,"On 01.06.2017 [00:22:44 -0000], Luca Cervigni wrote:

> I mean, it is a database service and 99% of the times can be, or it is used from the network.
> In the mongodb configuration mongodb.conf:
>
> ...
> #Net
> net.bindIp:  127.0.0.1,10.4.78.23
> net.port: 27017
> ...
"
1693122,2017-06-01 01:43:39 UTC,"I thought this was the right place to fill the bug to have the source package fixed. Where should I report it to if not here?
Thanks"
1693122,2017-06-01 20:46:19 UTC,"Hi Luca,"
1693122,2017-05-24 08:40:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693122,2017-05-31 22:28:34 UTC,Hello and thank you for reporting this bug.
1693123,2018-01-28 19:28:26 UTC,@simon-m-m Any reason you are not using BumbleBee for managing Nvidia?
1693123,2019-04-23 12:52:08 UTC,As a workaround I did the following:
1693123,2019-01-29 01:54:20 UTC,I have a Dell Precision 16.04 upgraded to 18.04.1 LTS. HD Graphics is Coffeelake 3x8 GT2 and nvidia-graphics-drivers-390. I've had this problem for a year now and would like it to end. Moulick Aggarwal (byesahil) fix is for KDE I have Gnome is there a Fix?
1693123,2018-01-29 04:32:30 UTC,https://gist.github.com/whizzzkid/37c0d365f1c7aa555885d102ec61c048
1693123,2018-01-28 22:15:45 UTC,"Last time I tried it, it didn't work.
Also they dropped support for the nouveau driver because ""noveau will implement prime themself"". Noveau is no where near to supporting prime themself."
1693123,2018-01-28 19:13:55 UTC,I have no idea why this is being ignored. It isn't even a code bug. It is a simple misunderstanding/packaging error/wrong dependency.
1693123,2018-10-01 20:02:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693123,2017-12-21 00:32:15 UTC,"(To be clearer: the nvidia-persistenced _package_ was removed in artful, but nvidia-persistenced.service is still in the nvidia-384 package pointing to the wrong path for the nvidia-persistenced _binary_.)"
1693123,2017-12-21 00:29:57 UTC,Retitling to reflect the fact that nvidia-persistenced was removed in artful.  The /usr/bin/nvidia-persistenced path referred to by nvidia-persistenced.service doesn’t exist in any package now.
1693123,2017-11-13 10:35:51 UTC,"For some reason I cannot add nvidia-graphics-drivers-384, so I added Nvidia and another bug report (see duplicates)."
1693123,2017-05-24 22:31:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693123,2017-11-13 10:30:38 UTC,More to it: `/usr/bin/nvidia-persistenced` gets deleted by every `prime-select intel`. And I haven't found yet what exactly deletes it. Can anyone point it?
1693123,2017-08-02 12:11:15 UTC,Trying to workaround it with
1693123,2017-05-24 22:34:00 UTC,"I can confirm this bug. Interestingly nvidia-375 provides nvidia-persistenced.
Extracting the bin from nvidia-persistenced to /usr/bin/ fixes it as a workaround."
1693123,2017-06-07 19:23:08 UTC,[Related askubuntu question](https://askubuntu.com/questions/845113/how-to-get-nvidia-persistenced-daemon-to-work-properly).
1693123,2018-01-28 17:33:39 UTC,This bug is also present in Ubuntu 17.10 with Nvidia 390.12 drivers.
1693127,2018-05-23 02:33:07 UTC,"Change abandoned by Tuan Luong-Anh (<email address hidden>) on branch: master
Review: https://review.openstack.org/477437"
1693127,2017-05-30 12:10:02 UTC,This issue was fixed in the openstack/ironic-python-agent 2.1.0 release.
1693127,2017-05-24 14:28:18 UTC,"Reviewed:  https://review.openstack.org/467517
Committed: https://git.openstack.org/cgit/openstack/ironic-python-agent/commit/?id=35ea727e6a84706d7a2145c7c551b2479b717ed4
Submitter: Jenkins
Branch:    master"
1693127,2017-05-24 08:18:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467517"
1693127,2017-06-26 07:54:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477437"
1693135,2017-05-24 11:26:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693135,2017-05-24 11:28:09 UTC,"This package is not needed anymore, the functionality you are looking for is found in sugar-log-activity, which you already have installed. I have asked the Ubuntu Archive Administrators to remove this package from Ubuntu."
1693149,2017-05-24 09:33:14 UTC,both cases in that diff where it uses self.path that should just be builder_file or something reasonable - you get the idea.
1693152,2017-06-02 16:49:39 UTC,I can't see the overlaping in the screenshot.
1693152,2017-06-03 10:21:38 UTC,Look at the terminal icon in the top left corner. Just over the File menu. It seems that behind the terminal icon there's a circle. It is more clear if you zoom exactly a little over the terminal icon in the window decoration.
1693154,2017-09-14 17:32:10 UTC,"The verification of the Stable Release Update for freeipa has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1693154,2017-09-14 17:31:58 UTC,This bug was fixed in the package freeipa - 4.4.3-3ubuntu2.1
1693154,2017-05-24 10:05:03 UTC,"the client install creates /etc/krb5.conf with ""includedir /etc/krb5.conf.d/"""
1693154,2017-07-04 14:08:38 UTC,"Hello Martin, or anyone else affected,"
1693154,2017-06-14 11:01:47 UTC,fixed package uploaded to the queue
1693154,2017-05-24 15:48:22 UTC,"Splendid, thanks Timo!"
1693154,2017-09-14 10:24:22 UTC,"Using the reproduction steps in the description, I re-confirmed that with the current zesty version joining the domain fails because of that missing directory. After installing freeipa-{client,common} from -proposed, joining the domain now succeeds."
1693155,2017-07-04 02:24:45 UTC,This bug was fixed in the package ubuntu-themes - 16.10+17.10.20170703-0ubuntu1
1693155,2017-06-26 10:05:36 UTC,"OK, it turns out that just reverting to Adwaita's battery actually creates as many problems as it fixes (see unity7 and unity-greeter). So let's not do that."
1693155,2017-06-22 08:02:27 UTC,Although it appears tricky to just remove gnome-shell-related battery icon symlinks without causing the same changes to occur in Unity7 and unity-greeter. Needs more time and consideration than I have right now.
1693155,2017-06-22 04:02:32 UTC,and 3. Keep the SVGs as proper SVGs. Don't accidentally rasterize them like I did.
1693155,2017-06-22 06:12:02 UTC,"""New icons"" might not be strictly required."
1693155,2017-06-22 05:48:28 UTC,"Nope, comment #14 won't really work adequately either. As a proof of concept, here's something that demonstrates what the outcome would be:
   https://code.launchpad.net/~vanvugt/ubuntu-themes/fix-1693155/+merge/326127"
1693155,2017-06-22 03:48:49 UTC,"Actually, this might work (and I apologise to design for troubling them if it does):"
1693155,2017-06-22 07:42:26 UTC,"Design says:
""For now please revert to Gnome standard, we first want to get to a workable theme and once everything is converted to Gnome we can look at improving the icons (this might be an 18.04 timeframe)."""
1693155,2017-06-20 10:45:17 UTC,Ups... I didn't read your latest comment... So yeah. We agree :-D
1693155,2017-06-20 10:43:34 UTC,"Mh, i remember we had some kind of ""custom code"" in unity for this..."
1693155,2017-06-20 10:14:26 UTC,"And we could achieve the same ""fix"" as comment #8 by modifying gnome-shell itself to ensure non-square icons are padded into squares, and never stretched."
1693155,2017-06-20 10:11:52 UTC,And for future reference:
1693155,2017-06-20 10:05:04 UTC,"The good news: I have a proof of concept fix attached. Just made sure all the icons have invisible square borders, and all are 24x24."
1693155,2017-06-19 08:17:15 UTC,"Note this bug is most significant on low DPI machines. If you view it in high DPI then you can make out the shape of the battery better, but it's still not great."
1693155,2017-06-07 12:43:58 UTC,The ubuntu-mono source does not exist post-precise. It was replaced with the ubuntu-themes source.
1693155,2017-06-20 11:16:38 UTC,Deleted attachment from comment #8. I had unwittingly produced SVGs containing PNG (non-scalable) :)
1693155,2017-06-02 09:31:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693155,2017-05-24 10:53:54 UTC,"This happens when using ubuntu-mono-dark as icon them, I don't have any problem with other icon themes."
1693158,2017-05-24 09:45:05 UTC,"Look at the font and at the (x) in particular, are they grayed?"
1693158,2017-06-02 16:57:52 UTC,I'm using Ubuntu 17.04 with Gnome and I can't reproduce it. I see title and (x) fine and the bottom text grayed.
1693160,2017-05-26 01:42:08 UTC,"Hello Seth, I am afraid that technology is beyond my expertise.  I thank
you for your help but I am not knowledgeable at all to carry out your
instructions.  I will ask for help from the person where I purchased the
computer.  i phoned him today and he asked me to bring the computer in.  At
this time I believe it is the best alternative. Your effort to help me was
appreciated."
1693160,2017-05-25 17:01:32 UTC,"Thank you for your message I do not use ssh (I don't know what it is).
This is the message on my computer when I was notified that the updating
could not be completed ""THE PACKAGE SYSTEM IS BROKEN.  Check if you are
using third-party repositories (common source of problems)  Furthermore run
the following command on a terminal: sudo apt-get-install-f"".  I tried this
command and it did not help and I do not use third-party repositories.  I
will await your instructions.  It is comforting to receive this help from
you.  I do not know a technician and have been wondering where to take the
computer, if you can advise me how to fix the problem (with my limited
understanding of the computer mechanics) it would very appreciated.  Dorothy"
1693160,2017-05-25 05:56:52 UTC,"Hello Dorothy,"
1693160,2017-05-24 10:11:52 UTC,"I do not understand the technology and I find the instructions too
complicated for me.  I will take the computer to a technician."
1693160,2017-05-26 00:47:08 UTC,"Hello Dorothy,"
1693170,2017-05-25 08:25:54 UTC,https://kodi.tv/article/kodi-v173-minor-bug-fix-and-security-release
1693179,2017-05-24 11:42:43 UTC,test case for missing mask editing capabilities
1693181,2017-05-24 11:45:44 UTC,"When selecting the first object, the mask editing controls are scaled down and to the top left of where they should be."
1693188,2017-06-19 07:55:41 UTC,"Reviewed:  https://review.openstack.org/474529
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=245539ea9fa29e5c46e95947e77f64c62bb0daee
Submitter: Jenkins
Branch:    master"
1693188,2017-06-20 07:11:13 UTC,Affected only new deployment. In case of upgrade you can delete those parameters manually.
1693188,2017-06-19 07:51:54 UTC,"Reviewed:  https://review.openstack.org/474527
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=98154bff027073093b7142b22988cfc7d33cd05f
Submitter: Jenkins
Branch:    stable/newton"
1693188,2017-06-15 09:55:14 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/474527"
1693188,2017-06-15 09:56:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474529"
1693188,2017-06-15 09:56:04 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/474528"
1693188,2017-06-13 11:25:45 UTC,"Reviewed:  https://review.openstack.org/472738
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=f8cb7857342421232a97869a46e8a82f6055b0f1
Submitter: Jenkins
Branch:    stable/mitaka"
1693188,2017-05-24 13:37:16 UTC,sla2 for 9.0-updates
1693188,2017-06-19 07:50:57 UTC,"Reviewed:  https://review.openstack.org/474528
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=d076b4c6a5ab660caef43ecd7157348ead1956bb
Submitter: Jenkins
Branch:    stable/ocata"
1693188,2017-06-09 15:46:29 UTC,"Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/472738"
1693202,2019-07-21 12:02:36 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1693202,2019-09-20 04:17:55 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1693227,2017-05-24 22:38:24 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1693227,2017-05-24 22:39:11 UTC,"Hello Bruno, you can try to work around this error by running:"
1693235,2018-12-18 17:10:41 UTC,I am also having this issue:
1693235,2018-12-18 17:03:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693240,2018-05-17 13:43:31 UTC,"We have agreement from Nic vendors now to do this in kernel drivers via sysfs. In the nic driver, the trunk sysfs kobject supports two operations: add and rem. The add operator supports users to add one or more VLAN id into VF VLAN filtering. The rem operator supports removing VLAN ids from the VF VLAN filtering list."
1693240,2017-10-05 20:00:17 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/476547"
1693240,2017-06-09 17:46:34 UTC,"That would be my point about 'vlan filtering' - which I think is a lot closer to what we actually want to use.  VLAN aware VMs was intended to allow more network connections than you can reasonably have ports.  If you're doing NFV you're often looking at a limited trunk, which it *can* do but which it's not good at."
1693240,2017-06-22 15:05:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/476547"
1693240,2017-06-09 17:21:29 UTC,"by the way that comment is based on the orginal descripton no the update one that mentions subports but im not conviced subport are nessicarlly the best approch but
it the intent is just make vlan aware vms work with sriov i think that is also a good thing
though i i recall correctly trevor you request at the ptg went beyond that?"
1693240,2017-10-05 18:42:18 UTC,"I am still puzzled about the comments and the current description. My reading is the ask here is to support vlan_transparent API extension for SR-IOV ports, so that instances get all the incoming traffic when VIF is in promiscuous mode. Is it the case? If so, it seems like the description would need some love."
1693240,2017-06-09 07:54:44 UTC,"It's possible to the get the list of subports and the segmentation ID they are using querying the API, implementing this shouldn't be a problem"
1693240,2017-06-09 17:18:16 UTC,"this reads somewhat different then vlan aware vms though as this
is vlan trunking of user spcified vlans not trunking of
neutron networks using vlans as a segmentation type as supported by vlan aware vms."
1693240,2017-05-24 17:46:36 UTC,"(If it is proposing a new API, please provide more details about the expected user workflow)"
1693240,2017-05-24 20:51:08 UTC,"This sounds like it's the VLAN aware VM extension, extended to work with SRIOV (which isn't QinQ and isn't a new API either)."
1693240,2017-05-24 17:46:15 UTC,So is this proposing a new API or is this RFE just for the implementation of QinQ in the SR-IOV agent?
1693240,2017-05-25 21:58:49 UTC,"@Ian, that sounds right."
1693240,2017-05-25 23:44:06 UTC,"I recommend you read the VLAN aware VM spec very carefully - first it doesn't do qinq filtering if you'd like to do that, and second I'm not quite sure whether the VLANs are user-selected or not."
1693240,2017-05-24 20:52:54 UTC,"(Or you could do select VLANS from a flat network, conversely)"
1693240,2017-05-25 22:52:43 UTC,Ok. let's treat this as a regular bug since it's just parity with the existing stuff.
1693248,2018-07-13 04:26:08 UTC,https://review.openstack.org/#/c/574477/
1693248,2017-06-09 17:37:04 UTC,"@ian that may be possible depending on your choice of nic.
niantic an fortvile dont support this today if the forwarding mechanisum is l3 based
but it should be possible to use the flow director apis via the vfd to do mac based forwarding
to another host e.g. rewrited mac to remote back and tx to phyical networks assuming they are on the same l2 segment."
1693248,2017-06-09 18:33:15 UTC,"In this instance, SRIOV mirroring would want to spit the packets out of the net link in at least the worst case scenario - and this isn't a simple MAC rewrite, because you want the MAC in the information, it has to be an encap.  If that requires a duplication to a DPDK service that does the encap then that would meet the requirements, though the uncosted extra load on the host and the limited-capacity DMA interface would be a concern."
1693248,2017-05-24 17:45:20 UTC,"Since this is for tap-as-a-service which isn't under Neutron governance ATM you don't need drivers team approval for this one, just approval from TaaS folks."
1693248,2017-05-24 17:42:16 UTC,"Whoops, I didn't notice this is in the tap as a service context. This request makes sense."
1693248,2017-05-24 17:41:32 UTC,Can you please provide some more details about what mirroring ports means in this context?
1693248,2017-05-24 16:18:23 UTC,"if you have any idea how to implement it, can you share?"
1693248,2017-05-25 22:55:23 UTC,If you abide by the TaaS API they're not guaranteed to even be on the same host.
1693248,2017-05-25 22:30:29 UTC,"@YAMAMOTO, In the event there is a port that is from sr-iov, we will be calling VFd to setup mirroring. This probably only works if the source and destination are sr-iov ports, not sure about mixing them. VFd is apart of DPDK."
1693265,2017-05-24 18:01:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467699"
1693265,2017-07-20 17:42:46 UTC,"I changed the severity here because I don't think this is wishlist. Without a change, cloud-init has no option but to configure each interface with all the DNS servers. If you then take down an interface via which one of the per-net servers is reachable, you break resolution. Right now, multi-interface instances are being configured wrong, and thus that's a real issue."
1693265,2017-08-01 12:57:50 UTC,"Reviewed:  https://review.openstack.org/467699
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4b333b989dfc778a8b61db4a1b8552e988a10471
Submitter: Jenkins
Branch:    master"
1693265,2017-08-11 12:27:23 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1693281,2017-05-24 20:59:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467767"
1693281,2017-05-24 19:12:53 UTC,See https://github.com/openstack/kolla-kubernetes/pull/5
1693281,2017-05-24 20:53:59 UTC,Went thru the gerrit guide so redoing this bug and PR
1693281,2018-06-07 09:33:28 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/467767"
1693289,2017-05-25 15:12:58 UTC,"For a complete example, compile with clang >= 4.0:"
1693289,2017-06-11 03:23:34 UTC,"I would love to help get this fixed, but would appreciate any pointers in where to look. In principle the implementation should be reasonably straight forward, but I'm unfamiliar with the LD code-base..."
1693289,2017-06-12 08:27:29 UTC,"Hi Amit,"
1693309,2017-05-26 12:45:16 UTC,https://review.openstack.org/#/c/467357/
1693309,2017-08-15 08:49:43 UTC,This issue was fixed in the openstack/bifrost 4.0.0 release.
1693309,2018-02-09 03:02:56 UTC,This issue was fixed in the openstack/bifrost 3.1.1 release.
1693310,2017-06-12 11:02:27 UTC,https://github.com/jaap-karssenberg/zim-desktop-wiki/commit/45ab3d8fd52a36ec5baedcf966aaed46776199c2
1693315,2017-11-15 01:07:02 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1693315,2017-11-01 00:20:29 UTC,This issue was fixed in the openstack/nova 14.0.9 release.
1693315,2017-10-17 21:01:54 UTC,"Reviewed:  https://review.openstack.org/493206
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=89b6da0c2832e739e6e0d30a0e205165005dc41c
Submitter: Zuul
Branch:    stable/newton"
1693315,2017-08-11 12:27:28 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1693315,2017-08-11 19:27:55 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/493206"
1693315,2017-08-11 19:02:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/493141"
1693315,2017-07-28 20:43:59 UTC,"Reviewed:  https://review.openstack.org/467715
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=20c4715a49a44c642882618f102cd0fc9342978d
Submitter: Jenkins
Branch:    master"
1693315,2017-05-24 18:43:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467715"
1693315,2017-10-17 20:39:45 UTC,"Reviewed:  https://review.openstack.org/493141
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=50eb1c6df4ef067e2f3de1df4e89dfab5df66c47
Submitter: Zuul
Branch:    stable/ocata"
1693322,2020-11-15 20:30:44 UTC,Invalid since 17.04 is out of support.
1693322,2017-05-24 21:14:22 UTC,I think bug 1656071 was mostly about missing dependencies but that was fixed in 17.04 so I can't tell what is wrong here. I am not able to reproduce this bug with the information provided with a clean install of either Ubuntu or Ubuntu GNOME 17.04.
1693322,2017-05-24 21:43:01 UTC,Just wait around.
1693322,2017-10-19 16:47:58 UTC,Still the same bug in 17.10. Pretty weak.
1693322,2018-04-16 16:45:08 UTC,Still happens all day in 18.04.
1693326,2017-05-24 18:57:15 UTC,"Thanks for the feedback Thilo, I'll take a look into it. Best regards."
1693334,2017-05-24 23:22:45 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1693334,2017-05-24 23:23:11 UTC,This looks like the important part from the logs:
1693334,2017-09-18 14:20:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693335,2018-02-25 15:29:07 UTC,"Reviewed:  https://review.openstack.org/518997
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=09970fe366cf3200a53d93c41bc996a58a25a4af
Submitter: Zuul
Branch:    stable/ocata"
1693335,2018-02-15 23:53:58 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1693335,2018-02-02 06:40:42 UTC,"Reviewed:  https://review.openstack.org/518996
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=31b2f0a2a65b782be4d0a68b3b53604a076f4748
Submitter: Zuul
Branch:    stable/pike"
1693335,2018-05-02 12:05:39 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1693335,2017-11-10 23:43:23 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/518997"
1693335,2017-11-10 23:43:06 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/518996"
1693335,2017-11-10 08:27:04 UTC,"Reviewed:  https://review.openstack.org/467772
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ecfb65cee68e96cc99ceecddbf27c6d6f768358e
Submitter: Zuul
Branch:    master"
1693335,2017-05-24 21:09:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/467772"
1693335,2017-05-24 19:27:36 UTC,"I forgot to mention I'm seeing this on stable/mitaka, but looks like it could still be an issue on master."
1693335,2017-05-24 21:03:56 UTC,"The problem is the hide_server_addresses extension is looking for the instance in the request cache using the id passed in via the client, which is upper case, and the id key in the cache is from the db, which is lower-case, so it doesn't find the instance and blows up with a TypeError because it's not checking for None. This is something you'll hit with mysql which is case insensitive so it can find the instance but doesn't cache it using the same key."
1693335,2017-12-07 23:56:41 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1693342,2019-10-26 22:12:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693342,2020-04-15 22:23:09 UTC,"The highlight project is maintained on gitlab, not github."
1693345,2017-07-14 17:55:30 UTC,"I have this problem during booting Ubuntu 17.04/XUbuntu 16.04.2 with new dell 5580 Intel Kabylake + Nvidia 940MX, system never finish startup. Solution is here:
https://askubuntu.com/questions/875173/nmi-watchdog-bug-soft-lockup-cpu2-stuck-for-23s-plymouthd305
If system boot, it must set nouveau.modeset=0 ..., if boot with Nvidia proprietary, is it OK."
1693345,2017-05-26 13:39:30 UTC,One of these appear every time I resume from suspend.
1693345,2017-05-25 20:17:51 UTC,This is a fresh install of 17.04 from the ISO at https://www.ubuntu.com/download/desktop. I am testing v4.12-rc2.
1693345,2017-05-25 19:50:42 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1693345,2017-05-24 20:30:15 UTC,This change was made by a bot.
1693345,2017-05-26 03:57:48 UTC,"The upstream fixed this problem, but now I'm seeing another suspicious entry in the dmesg log:
[ 1923.628750] ------------[ cut here ]------------
[ 1923.628837] WARNING: CPU: 0 PID: 0 at /home/kernel/COD/linux/net/mac80211/rx.c:630 ieee80211_rx_napi+0x905/0xa20 [mac80211]
[ 1923.628842] Modules linked in: rtsx_usb_ms memstick rtsx_usb_sdmmc rtsx_usb ccm rfcomm bnep nls_iso8859_1 hid_rmi cmdlinepart rmi_core joydev intel_spi_platform intel_spi spi_nor intel_rapl mtd x86_pkg_temp_thermal intel_powerclamp kvm_intel dell_wmi sparse_keymap kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel arc4 pcbc dell_laptop dell_smbios ath9k dcdbas ath9k_common dell_smm_hwmon snd_hda_codec_hdmi snd_hda_codec_realtek aesni_intel snd_soc_rt5640 snd_hda_codec_generic aes_x86_64 snd_soc_rl6231 crypto_simd glue_helper ath9k_hw snd_hda_intel snd_soc_core uvcvideo snd_hda_codec cryptd ath snd_hda_core intel_cstate videobuf2_vmalloc snd_hwdep videobuf2_memops videobuf2_v4l2 snd_compress intel_rapl_perf ac97_bus snd_seq_midi mac80211 videobuf2_core snd_pcm_dmaengine snd_seq_midi_event
[ 1923.628944]  snd_rawmidi input_leds videodev ath3k hid_multitouch serio_raw cfg80211 btusb snd_pcm media snd_seq btrtl btbcm btintel snd_seq_device elan_i2c bluetooth snd_timer snd ecdh_generic soundcore mei_me shpchp lpc_ich mei snd_soc_sst_acpi i2c_designware_platform dw_dmac snd_soc_sst_match i2c_designware_core dw_dmac_core spi_pxa2xx_platform 8250_dw dell_rbtn mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp coretemp nf_conntrack parport_pc libcrc32c ppdev iptable_filter lp parport ip_tables x_tables autofs4
[ 1923.629067]  usbhid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 ahci drm libahci mii wmi video sdhci_acpi sdhci i2c_hid hid
[ 1923.629108] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.12.0-041200rc2-generic #201705212331
[ 1923.629113] Hardware name: Dell Inc. Inspiron 3542/0KHNVP, BIOS A03 05/27/2014
[ 1923.629119] task: ffffffff8c2104c0 task.stack: ffffffff8c200000
[ 1923.629179] RIP: 0010:ieee80211_rx_napi+0x905/0xa20 [mac80211]
[ 1923.629185] RSP: 0018:ffff97eddfa03d18 EFLAGS: 00010246
[ 1923.629196] RAX: 0000000000010000 RBX: ffff97edd4876a00 RCX: ffff97edd03fc1a8
[ 1923.629201] RDX: 0000000000000004 RSI: ffffffffc09c8000 RDI: ffff97edcfac0780
[ 1923.629206] RBP: ffff97eddfa03de8 R08: 0000000000000000 R09: ffff97eddfda5000
[ 1923.629211] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1923.629216] R13: 0000000000000000 R14: ffff97edd12cd9b8 R15: ffff97edcfac0780
[ 1923.629223] FS:  0000000000000000(0000) GS:ffff97eddfa00000(0000) knlGS:0000000000000000
[ 1923.629229] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1923.629234] CR2: 00007ff82a858000 CR3: 00000001b6a09000 CR4: 00000000001406f0
[ 1923.629240] Call Trace:
[ 1923.629246]  <IRQ>
[ 1923.629263]  ? map_single+0x32/0x80
[ 1923.629272]  ..."
1693361,2018-08-22 10:54:05 UTC,"Nothing actionable here for apt, so I'll close this. We should consider making frontend locking more flexible for scripts using apt, though, so scripts can hold the lock all the time and drive apt."
1693361,2017-09-23 02:33:29 UTC,"This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New"
1693361,2017-07-26 18:27:42 UTC,This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-0ubuntu1~17.04.2
1693361,2017-06-29 21:49:11 UTC,"The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1693361,2017-06-29 21:48:59 UTC,This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-0ubuntu1~16.04.2
1693361,2017-06-29 19:22:00 UTC,$ for rel in xenial yakkety zesty; do lxc-proposed-snapshot --proposed $rel proposed-$rel --publish || break; done
1693361,2017-06-27 21:56:55 UTC,This bug was fixed in the package cloud-init - 0.7.9-197-gebc9ecbc-0ubuntu1
1693361,2017-06-29 04:53:17 UTC,"Hello Jim, or anyone else affected,"
1693361,2017-06-29 04:45:32 UTC,"Hello Jim, or anyone else affected,"
1693361,2017-06-13 00:20:52 UTC,"We eventually want wait locking in apt, but I don't think it really solves all issues, especially in scripts with multiple apt invocations. Which is why apt-daily got an additional flock lock for the upcoming SRUs. (see artful)."
1693361,2017-06-01 22:17:19 UTC,Some research on this indicates:
1693361,2017-05-25 18:38:43 UTC,"I suspect that Steve's suggestion should fix this mostly for cloud-init.
Apt does of course have a general locking problem that really does need addressing."
1693361,2017-05-24 21:42:51 UTC,"My concern is another apt dependent task being added somewhere else in systemd that winds up triggering during boot.  IMO it's better to be generically defensive about the use of apt, but others certainly have more context and information than I do."
1693361,2017-05-24 21:30:51 UTC,"On Wed, May 24, 2017 at 09:10:37PM -0000, Jim Browne wrote:

> While it would be better to solve this in apt itself, I suggest that
> cloud-init be defensive when calling apt and implement some retry
> mechanism.
"
1693361,2017-06-29 04:55:56 UTC,"Hello Jim, or anyone else affected,"
1693379,2019-09-04 07:56:43 UTC,"we have that in 18.04, closing"
1693393,2017-06-22 09:18:12 UTC,"This commit is needed to fixed a issue introduced by 9d26d3a8f1b0 (""PCI: Put PCIe ports into D3 during suspend"")"
1693407,2017-06-06 11:31:38 UTC,"We could possibly arrange for the ""configure code"" page to let you select a repository from outside the project and move it within the project.  It would necessarily involve changing its URL (to e.g. lp:~myself/mystuff/+git/mystuff, which would then be aliased to lp:mystuff)."
1693409,2017-09-23 15:15:36 UTC,"Confirmed. Ospurge now discovers my resources, thanks!"
1693409,2017-09-04 08:16:59 UTC,"Hi, Mathias"
1693409,2017-09-14 10:41:04 UTC,I've just approved https://review.openstack.org/#/c/500468/ which should fix this. If anyone could confirm that would be great. Thanks :)
1693409,2017-08-16 13:55:35 UTC,"I had the same problem targeting Ice House, Juno, and Mitaka clouds when trying to utilize virtualenv."
1693409,2017-07-16 18:26:37 UTC,Same here.
1693409,2017-06-05 11:44:56 UTC,I am having the same problem on a Newton based cloud.
1693409,2017-09-01 06:43:05 UTC,"Andrew, which part exactly solves the issue? I was not able run ospurge a single time up to today :("
1693410,2019-07-19 22:29:03 UTC,https://askubuntu.com/a/1159551/368900
1693410,2019-07-19 22:39:58 UTC,"According to bug 1218510 comment #32,"
1693410,2019-07-19 22:44:54 UTC,Then in bug 1218510 comment #33
1693414,2017-06-06 18:59:58 UTC,"Error
All nodes are finished. Failed tasks: Task[node_reboot/11] Stopping the deployment process!"
1693414,2017-11-20 18:01:33 UTC,Please provide any meaningful logs from failing node.
1693423,2019-10-29 19:11:07 UTC,Based on the last comment I'm marking the bug as invalid (in the terms of support request) since it is not a problem that required any changes to snappy or ubuntu-core. Thank you and good luck :)
1693423,2017-06-09 14:32:15 UTC,"Thanks for your suggestion, Based on Hardware info Enabled Ethernet related Drivers now its working fine."
1693423,2017-06-09 06:42:25 UTC,"Dear Developers,
   Finally Customised Ubuntu core Image for x86 is booted on intel core i3 processor based Custom Board,but Right Now I am Facing Network Configuration Error.please find below attachment and suggest on it."
1693423,2017-06-02 07:08:58 UTC,"   Sorry for the Late Reply,
     Thanks for your quick reply,Actually we Builded Custom kernel snap with Kernel version 4.4 & gadget snap(pc-i386-gadget).Generated ubuntucore image with it."
1693423,2017-05-25 06:10:09 UTC,Please provide more information. What is likely going on is that the kernel doesn't have the module for your storage device and thus cannot continue the boot process. I saw something similar some time ago when I tried to boot of a PATA IDE device.
1693423,2017-06-09 08:19:48 UTC,seems you miss the driver/module for your network card in the kernel
1693427,2017-05-29 13:26:12 UTC,packstack bugs are reported here: https://bugs.launchpad.net/packstack
1693427,2017-05-29 14:42:19 UTC,"Could you confirm which versions of Packstack and the Puppet modules are you using? From the Packstack code reference you provide, it looks like stable/mitaka code: https://github.com/openstack/packstack/blob/stable/mitaka/packstack/puppet/templates/nova_sched.pp"
1693436,2017-06-17 14:42:16 UTC,"wifi fixed with driver below.
https://github.com/lwfinger/rtl8723bu"
1693436,2017-06-02 09:10:06 UTC,kernel-bug-exists-upstream
1693436,2017-05-29 13:18:45 UTC,"@jsalisbury Still not working with latest kernel. I intalled v4.12-rc3 kernel and wifi and trackpad is still down also has warning about i915.
SL:~$ modinfo rtl8xxxu
filename:       /lib/modules/4.12.0-041200rc3-generic/kernel/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.ko
firmware:       rtlwifi/rtl8723bu_bt.bin
firmware:       rtlwifi/rtl8723bu_nic.bin
firmware:       rtlwifi/rtl8192eu_nic.bin
firmware:       rtlwifi/rtl8192cufw_TMSC.bin
firmware:       rtlwifi/rtl8192cufw_B.bin
firmware:       rtlwifi/rtl8192cufw_A.bin
firmware:       rtlwifi/rtl8723aufw_B_NoBT.bin
firmware:       rtlwifi/rtl8723aufw_B.bin
firmware:       rtlwifi/rtl8723aufw_A.bin
license:        GPL
description:    RTL8XXXu USB mac80211 Wireless LAN Driver
author:         Jes Sorensen <email address hidden>
srcversion:     93A4EB53A9610C28FD9407E
alias:          usb:v0BDAp818Cd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2019pAB33d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2357p0107d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v7392p7822d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v4855p0091d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2357p0100d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v20F4p624Dd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2019pAB2Bd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2001p330Ad*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2001p3309d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2001p3307d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0E66p0020d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0E66p0019d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0BDAp2E2Ed*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0846pF001d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0846p9021d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v07B8p8178d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v07AAp0056d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0789p016Dd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0DF6p0070d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0DF6p0061d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0B05p17ABd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v06F8pE035d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0586p341Fd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v050Dp2103d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v050Dp2102d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v04BBp0950d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2019p1201d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v04F2pAFFCd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v04F2pAFFBd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v04F2pAFF8d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v04F2pAFFAd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v04F2pAFF9d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v04F2pAFF7d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:vCDABp8010d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v4856p0091d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v4855p0090d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2019pED17d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2019pAB2Ed*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v2019pAB2Ad*dc*dsc*dp*icFFiscFFipFFin*
alias:..."
1693436,2017-05-25 19:17:13 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1693436,2017-05-25 08:00:16 UTC,This change was made by a bot.
1693436,2017-05-29 13:25:31 UTC,warnings about i915 show below
1693440,2017-05-25 08:00:38 UTC,This change was made by a bot.
1693440,2017-05-25 19:16:49 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1693440,2017-05-29 13:27:47 UTC,Still not working with kernel v4.12-rc3.
1693440,2017-06-08 05:49:02 UTC,"Please try udev package here:
http://people.canonical.com/~khfeng/lp1693440/"
1693440,2017-06-08 22:06:11 UTC,@kaihengfeng Do youj mean I should install two packages you provided in the above link? B.t.w how to remove proto=imps option?
1693440,2017-06-08 22:10:37 UTC,@kaihengfeng I also have wifi connection issue which you can check out the WifiSyslog.txt. Failed to authenticate to any wireless network with rtl8xxxu driver module.
1693440,2017-06-23 13:41:01 UTC,"hgpk is not available, cypress and fsp option got no moving cursor, the rest works fine except for two-finger scrolling."
1693440,2017-06-09 07:05:36 UTC,Looks like I messed up something.
1693440,2017-06-17 14:38:02 UTC,"Any fix?
4.12.0-041200rc3-generic
psmouse serio2: cypress_ps2: Reconnect: Unable to initialize Cypress absolute mode"
1693440,2017-06-20 08:21:28 UTC,"Maybe it's not Cypress touchpad at all?
Let's try this:"
1693440,2017-06-23 13:39:23 UTC,"@kaihengfen
Tried them all, none of them works with two-finger scrolling. With fsp and cypress, I got no moving cursor, hgpk is not available, except for these, I got all work normal except for the two-finger scrolling function. Any fix?"
1693440,2017-06-24 07:02:04 UTC,"Can you add ""i2c-hid.dyndbg=+p"" to kernel parameter, and attach dmesg after boot?"
1693440,2017-06-08 22:45:56 UTC,"@kaihengfeng I installed the udev and libudev packages you provided but I got two errors during installation. After installing these two packages I rebooted, and the trackpad is still not working, I cannot make the trackpad work anymore, even with the two commands above that used to do the magic. Any rollback? If I marked these two packages as removal in synaptic I will remove a lot of packages linked to them, even some system packages."
1693440,2017-07-02 14:12:01 UTC,"It seems strange. I can scroll up or down with two fingers on my trackpad only when one finger stays still and the other finger move up or down. Any I need to run commands below to make this happen.
sudo modprobe -r psmouse
sudo modprobe psmouse proto=imps"
1693440,2017-07-02 13:46:04 UTC,"@kaihengfen
Here is the dmesg log after I added ""i2c-hid.dyndbg=+p"" to kernel parameter."
1693440,2017-07-15 11:46:49 UTC,"@kaihengfen
Sorry for the delay. The chip used is CY8CTMA140-LQI-1407. The PCB print 8442 TP RoHS."
1693440,2017-07-12 05:43:58 UTC,"Yoshiba,
Here's the request from the driver author:
""double the trackpad device is Cypress PS2 trackpad. Can check the label under the back of the trackpad."""
1693440,2017-07-08 15:42:58 UTC,"@kaihengfen
I also cannot wake my laptop now. Installed the 4.12.0-041200-generic kernel."
1693440,2017-07-07 06:08:06 UTC,I'll send a mail to ask linux-input and the driver author.
1693440,2017-07-06 08:06:46 UTC,"Yes, it works on Windows 8 and Windows 10. Any fix for it?"
1693440,2017-07-05 08:57:22 UTC,"Please try the new kernel. Keep parameter ""psmouse.dyndbg=+p""."
1693440,2017-07-06 00:13:04 UTC,"@kaihengfen
Still no luck."
1693440,2017-07-06 02:36:15 UTC,Does it work under Windows?
1693440,2017-07-03 08:27:38 UTC,Please try kernel in [1] and attach `dmesg` here.
1693440,2017-07-02 14:13:47 UTC,"B.t.w, sometimes it scrolls too fast with method above. Very strange workaround."
1693440,2017-07-04 05:36:25 UTC,Try kernel in [1]. It enables more debug message for cypress touchpad.
1693440,2017-07-05 04:58:39 UTC,"@kaihengfen
Tried kernel above still not working. Here is the dmesg log with kernel parameter."
1693440,2017-07-03 14:21:46 UTC,"@kaihengfen
Tried the kernel above, but still not working. Here is the dmesg log.
?field.comment=@kaihengfen
Tried the kernel above, but still not working. Here is the dmesg log."
1693449,2020-01-07 20:22:07 UTC,I wonder if anyone knows a workaround for this bug.
1693458,2017-05-25 10:15:52 UTC,apport information
1693458,2017-05-31 08:40:10 UTC,"#18 Joseph,
The bug appeared after a fresh install of 17.04. I was previously using 16.04 and hadn't experienced this bug (that I'm aware of)."
1693458,2017-05-25 19:15:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1693458,2017-05-25 10:16:07 UTC,apport information
1693458,2017-05-25 10:16:05 UTC,apport information
1693458,2017-05-25 10:16:04 UTC,apport information
1693458,2017-05-25 10:16:03 UTC,apport information
1693458,2017-05-25 10:16:02 UTC,apport information
1693458,2017-05-30 13:35:32 UTC,"I can confirm that I've experienced this bug as well on a brand new install of 17.04. Has happen twice when I leave the computer locked. When I try to resume, monitors don't come up and I can't SSH in as well."
1693458,2017-05-25 10:16:00 UTC,apport information
1693458,2017-05-25 10:16:01 UTC,apport information
1693458,2017-05-25 10:15:53 UTC,apport information
1693458,2017-05-25 10:15:54 UTC,apport information
1693458,2017-05-25 10:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1693458,2017-05-25 10:15:57 UTC,apport information
1693458,2017-05-25 10:15:58 UTC,apport information
1693458,2017-05-25 10:15:55 UTC,apport information
1693458,2017-05-25 10:15:59 UTC,apport information
1693470,2017-06-19 12:45:40 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1693470,2017-06-09 12:45:06 UTC,"Reviewed:  https://review.openstack.org/468838
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=93dc6f791bd6bd516cee5c8165e3e09ec8c158b9
Submitter: Jenkins
Branch:    stable/ocata"
1693470,2017-06-12 14:51:24 UTC,"Reviewed:  https://review.openstack.org/468647
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94a3ea56fad5e9890527ef6598bf3167f62bf6a6
Submitter: Jenkins
Branch:    stable/ocata"
1693470,2017-05-29 09:59:41 UTC,"Reviewed:  https://review.openstack.org/467370
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=387c53ccccd85a1ca43d9775ad12e4d98d86ebff
Submitter: Jenkins
Branch:    master"
1693470,2017-05-27 13:51:48 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/468647"
1693470,2017-05-26 19:08:28 UTC,"Reviewed:  https://review.openstack.org/467369
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f022d431e1f844a8faa7ab55597c83179c13022c
Submitter: Jenkins
Branch:    master"
1693470,2017-06-08 21:52:03 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1693470,2017-05-29 10:00:18 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/468838"
1693480,2017-08-20 18:02:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693487,2017-05-25 13:34:12 UTC,"could you attach the original svg file, for testing purposes?"
1693487,2017-05-27 09:10:09 UTC,Kind regards
1693487,2017-05-27 11:35:57 UTC,"thank you for the svg file. It appears that the unexpected behavior of the circumscribed circle is due to the fact that the drawn triangle does not consist of three straight lines, but instead contains a cubic Bezier curve in at least one segment. The control arms of the cubic Bezier curve are quite short, so you have to zoom in to see them. Attached is the raw data for the triangle, showing the Bezier contribution as well.
m 29.934188,162.83069 c 3.741772,1.06908 78.042702,28.33057 80.180852,28.33057 2.13816,0 16.03618,-28.33057 16.03618,-28.33057 z"
1693487,2017-05-27 11:54:32 UTC,"Thankyou for that explanation. I need to be more careful using the Bezuer
tool!"
1693488,2017-06-24 04:46:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693488,2017-06-24 04:48:28 UTC,same here on 16.04
1693494,2017-06-06 16:48:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1693494,2017-05-25 12:42:51 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-May/084393.html
1693495,2017-06-16 03:29:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474838"
1693495,2017-06-16 10:01:33 UTC,"in convergence, there is an other problem:
https://bugs.launchpad.net/heat/+bug/1698135"
1693495,2017-06-21 14:32:22 UTC,"There's no fully correct way to solve this class of bugs short of convergence phase 2 (i.e. getting the reality of the current networks from the Nova API, rather than trying to get them from the previous template). There are many, many steps to updating a Nova server resource, and we don't keep track of which ones have and have not been performed (arguably, we should use something like taskflow for this)."
1693495,2017-06-21 14:37:58 UTC,"Actually, it's surprising that the server isn't being replaced in the case where the update is being cancelled, since that should leave it in a FAILED state?"
1693495,2017-06-22 09:36:43 UTC,"There's no fully correct way to solve this class of bugs short of convergence phase 2
--- I hope the convergency phase 2 can solve the problem, but I meet some issue and can not test it deeper:
1. https://bugs.launchpad.net/heat/+bug/1696897  if we enable observe on update, the logic of getting reality networks and comparing with new network is not correct now
2. https://bugs.launchpad.net/heat/+bug/1698135  if enable convergence, the stack will hang in ROLLBACK_IN_PROGRESS after update cancelling"
1693495,2017-06-22 09:37:58 UTC,"In the legacy path, we are supposed to allow a grace period (configurable as `error_wait_time` in heat.conf, but 4 minutes by default) before we cancel a resource. So we should only hit this issue if it takes longer than that to update the server resource.
--- Yes, this works if resource.status is IN_PROGRESS. In this bug case, the server maybe FAILED when cancel message came? I am not sure of this."
1693495,2017-06-24 10:30:29 UTC,"@Zane,
I looked the code again, maybe there is bug in https://github.com/openstack/heat/blob/master/heat/engine/resource.py#L1140,
we introduced a mechanism to allow individual resources to control the cancellation grace period.
when we process new resource update, the runner key is new resource and the state is INIT_COMPLETE, so when we get the grace period we get None, so the task runner is closed immediately:
https://github.com/openstack/heat/blob/master/heat/engine/update.py#L229
https://github.com/openstack/heat/blob/master/heat/engine/scheduler.py#L401"
1693495,2017-06-24 10:56:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477087"
1693495,2017-07-04 06:36:43 UTC,"Reviewed:  https://review.openstack.org/477087
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=8c62e96947c70d577a9935a0c3a7b5a92efcbf5f
Submitter: Jenkins
Branch:    master"
1693495,2017-07-04 06:39:53 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/480034"
1693495,2017-07-08 07:44:42 UTC,"Reviewed:  https://review.openstack.org/480034
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=5034bc10afb736eedca0cb4e0503652711008e23
Submitter: Jenkins
Branch:    stable/ocata"
1693497,2020-08-05 11:35:21 UTC,"Open gnome-tweaks -> Keyboard & Mouse -> Set ""Middle Click Paste"" to OFF
It fixes the issue to me with terminator 1.91"
1693497,2018-10-17 09:47:25 UTC,"Workaround those who use 18.04 :
$ sudo add-apt-repository ppa:gnome-terminator/nightly-gtk3
$ sudo apt-get install terminator=1.91-0~1807~ubuntu18.04.1
$ sudo apt-mark hold terminator"
1693497,2018-06-13 08:46:49 UTC,"Confirmed on Ubuntu 18.04 using terminator 1.91-1 installed from default Ubuntu repository and up to date.
It has been a year since the fix was committed, when may we expect this fix to reach the official repo?"
1693497,2018-06-11 15:04:37 UTC,This is affecting me on ubuntu 18.04 as well. When will the fix end up in the official repo?
1693497,2017-05-26 01:37:07 UTC,Committed revision 1765.
1693497,2018-06-13 08:47:20 UTC,Is there a work-around to get this working again please?
1693498,2017-05-26 14:36:22 UTC,"The team had plans to deprecate the Credential and Policy APIs in the Pike release. Since that's the plan moving forward, I'm not sure it makes sense investing time into fixing the query parameter issues with those APIs."
1693498,2017-05-26 14:45:45 UTC,This work is documented in etherpads from the PTG [0].
1693498,2017-05-31 06:12:17 UTC,"Hi all,"
1693498,2017-06-09 17:32:13 UTC,If there are other APIs that are affected by this behavior then we should include them in this bug report and make it a bit more general. That will make it easier to ensure keystone handles this case consistently across all APIs and not just a couple.
1693498,2018-04-09 20:37:01 UTC,Automatically unassigning due to inactivity.
1693498,2020-07-23 17:34:53 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/742715"
1693498,2020-07-28 17:25:20 UTC,"This is valid but we can't fix it without breaking the API, see context here https://bugs.launchpad.net/keystone/+bug/1654084/comments/7"
1693498,2020-07-29 07:40:48 UTC,"Change abandoned by Vishakha Agarwal (<email address hidden>) on branch: master
Review: https://review.opendev.org/742715
Reason: It requires microversion inorder to chane the API."
1693504,2017-06-28 16:35:34 UTC,This bug was fixed in the package linux - 4.4.0-83.106
1693504,2017-06-29 07:17:58 UTC,This bug was fixed in the package linux - 4.10.0-26.30
1693504,2017-06-14 09:16:09 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1693504,2017-06-14 09:11:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1693504,2017-06-28 16:34:43 UTC,This bug was fixed in the package linux - 4.8.0-58.63
1693504,2017-06-14 09:09:46 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1693510,2017-07-26 04:46:19 UTC,This issue was fixed in the openstack/keystone 11.0.3 release.
1693510,2017-06-08 21:53:50 UTC,This issue was fixed in the openstack/keystone 12.0.0.0b2 development milestone.
1693510,2017-05-25 16:50:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468103"
1693510,2017-05-31 01:18:20 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469299"
1693510,2017-05-25 16:15:42 UTC,"I don't think include_names is needed to make this happen, if you have the fix for https://bugs.launchpad.net/keystone/+bug/1684820. But it still happens with effective even after that fix, so this is a new bug."
1693510,2017-05-31 21:28:03 UTC,"Reviewed:  https://review.openstack.org/469299
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=2fdf89554f75c46e20e4b0ec4c373037da2cfe53
Submitter: Jenkins
Branch:    stable/ocata"
1693510,2017-05-30 21:26:35 UTC,"Reviewed:  https://review.openstack.org/468103
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d09c337619fed8664272848abb3a1351dd5e4c85
Submitter: Jenkins
Branch:    master"
1693513,2017-05-25 14:34:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693513,2017-05-27 19:47:24 UTC,"No problem for the moment, the system works well."
1693513,2021-01-07 04:14:02 UTC,4.8 EOL
1693518,2017-05-31 15:20:18 UTC,Some additional clues:
1693518,2018-08-29 16:20:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693521,2018-12-17 13:43:45 UTC,"Thanks, I used same workaround on Debian for similar problem.
# cp /lib/firmware/brcmfmac43430-sdio.txt /lib/firmware/brcmfmac43455-sdio.txt"
1693521,2017-05-25 15:05:20 UTC,I installed bcmwl-kernel-source and can now connect to wifi networks. But the error persists:
1693521,2018-01-06 18:05:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693521,2018-02-20 04:28:27 UTC,"Not sure if it is a fix per se but it appears to just be looking for the presence of a .txt file by that name. I created brcmfmac43602-pcie.txt in the proper directory and just typed gibberish into it. I rebooted, re-ran 'dmesg | grep error', and found that the error is gone. Bluetooth seems to work just fine. Or at least my bluetooth mouse is connecting and working correctly."
1693522,2017-05-25 14:39:16 UTC,I've been using this profile https://github.com/simondeziel/aa-profiles/blob/master/16.04/usr.sbin.nginx for some time already which I think could be a good starting point.
1693523,2017-05-26 20:24:02 UTC,"Looks like the package was removed because it didn't support PHP7.0, see bug 1566572 for more details."
1693523,2018-03-23 08:25:25 UTC,PHP7 changes were backport to Ice 3.6
1693537,2017-07-18 17:12:49 UTC,- Mint 18.2 'Sonya' Cinnamon 64 bits
1693542,2018-01-25 09:22:04 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3706
1693544,2017-05-25 16:23:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1693544,2017-05-25 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1693544,2017-05-25 19:13:28 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1693544,2017-05-30 22:55:27 UTC,I have been running ~kernel-ppa/mainline/v4.12-rc2 for over 5 days now with neither screen blinking nor power loss.
1693551,2017-05-29 06:08:23 UTC,There should be already an alias for udisksctl in place but looks like we forgot to add it to the snap-declaration for udisks2.
1693562,2017-06-09 06:57:03 UTC,"Hi Adam:
    I try to reproduce the issue, like following, anything I miss? I use current master openstackclient with pip dev mode, so it's 3.11.1. More configuration is in paste page[1]."
1693564,2017-05-25 23:55:05 UTC,*** This is an automated message ***
1693564,2017-05-27 23:21:47 UTC,Here is some information about how this could be packaged: https://aur.archlinux.org/packages/ndpi-netfilter-dkms-git/
1693566,2017-05-25 17:49:38 UTC,Default Comment by Bridge
1693566,2017-05-25 17:49:36 UTC,Default Comment by Bridge
1693566,2017-10-10 19:15:30 UTC,I built a Zesty test kernel with a pick of commit 3d3efb68c19e539f.  The test kernel can be downloaded from:
1693566,2017-05-25 20:27:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1693566,2017-07-10 08:49:35 UTC,"------- Comment From <email address hidden> 2017-07-10 04:44 EDT-------
$ git log 3d3efb68c19e539f -1
commit 3d3efb68c19e539f0535c93a5258c1299270215f
Author: Paul Mackerras <email address hidden>
Date:   Tue Jun 6 14:35:30 2017 +1000"
1693566,2017-05-26 14:35:36 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1693566,2017-10-07 01:49:27 UTC,"------- Comment From <email address hidden> 2017-10-06 21:45 EDT-------
Hello Canonical,"
1693570,2017-06-01 23:51:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693573,2017-10-08 08:29:15 UTC,I suppose burg dosen't support ubuntu 17.04 cause in the reppository there are no folder for zesty
1693574,2017-06-02 14:58:19 UTC,Debdiff for Xenial
1693574,2017-06-02 14:58:50 UTC,Debdiff for Yakkety
1693574,2017-06-02 14:59:20 UTC,Debdiff for Zesty
1693574,2017-08-25 14:47:50 UTC,Debdiff for Artful (Devel release)
1693574,2017-11-23 14:19:14 UTC,The fix for this particular bug is now found in Debian and bionic-proposed (devel release) with version 3.5-1 (until the autopkgtest finishes)
1693574,2017-12-11 17:18:07 UTC,The bugfix for this particular bug will be included in the sosreport v3.5 backport effort in progress via :
1693574,2018-01-04 18:30:52 UTC,This bug is fixed with packages:
1693574,2018-01-15 22:02:12 UTC,"I tested the packages in trusty, xenial, zesty and artful. The Docker plugin runs well and gathers the expected information for Docker:"
1693576,2017-08-28 09:55:29 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1693576,2017-08-22 11:38:52 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1693576,2017-08-21 05:24:21 UTC,"Reviewed:  https://review.openstack.org/469672
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=76d59ebcb9ace58d9364877da25f1aa66fb759d8
Submitter: Jenkins
Branch:    stable/newton"
1693576,2017-05-31 22:16:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/469672"
1693576,2017-06-08 21:51:57 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1693576,2017-06-01 00:46:04 UTC,"Reviewed:  https://review.openstack.org/468136
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=452f21183f2f80cc5673ebd3fd3e5daf039caacc
Submitter: Jenkins
Branch:    master"
1693576,2017-05-31 22:10:55 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469671"
1693576,2017-08-15 03:58:48 UTC,"Reviewed:  https://review.openstack.org/469671
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=55684f6ac43ce2c55829337b7d24fe3059b866a8
Submitter: Jenkins
Branch:    stable/ocata"
1693576,2017-05-25 19:05:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468136"
1693578,2017-05-25 20:42:36 UTC,"confirmed on Windows 10, Inkscape 0.92.1 r15371, using the extension ""Arrange->Deep Ungroup""."
1693578,2017-05-25 22:13:32 UTC,"Thank you, Alvin!"
1693578,2017-05-26 15:25:31 UTC,Proposed patch to skip (valid) comments when iterating over children of etree elements.
1693578,2017-05-26 18:50:30 UTC,"Thank you, V, works! (corrected my forum post, too)"
1693578,2017-05-27 10:34:58 UTC,"The proposed patch from comment #3 does drop (i.e. not preserve) any XML comments within the ungrouped groups (inkscape does that too, when ungrouping ""manually""). I briefly investigated a different solution which preserves comments as such, but unfortunately, Inkscape (0.92.x) gets (temporarily) confused about the stack order when reloading a document returned from an extension where comments have been moved from inside a group to SVG Root (this can be reproduced independent of ungroup_deep.py). Reloading the file after saving though shows the expected result (and behavior)."
1693578,2017-07-08 12:34:46 UTC,Deleting the attached diffs - I am revoking my pending patches provided in this bug tracker for issues with python-based extensions distributed with Inkscape.
1693579,2017-07-16 21:51:30 UTC,"Same here. This is what htop shows after I lock and unlock the screen. When I scroll through other screensavers, each one of them takes one core to 100%."
1693579,2017-05-26 05:21:14 UTC,I'm also noticing this bug on 18.1 x64 Cinnamon.
1693580,2019-03-14 21:44:59 UTC,"I tracked the failure to report to the user back to bug #1808016.  However, the bug could also be avoided by checking permissions in advance, when the page first loads."
1693580,2018-11-30 16:38:19 UTC,Related: bug 1716765
1693580,2019-05-22 21:11:11 UTC,"Thanks, Dan.  Did a quick re-test and merged to 3.2 and above."
1693580,2019-05-22 19:03:41 UTC,Reinstating the signoff after retesting and proper inclusion of a second commit.
1693580,2019-05-22 18:58:11 UTC,Retracting the sign-off for further testing (I omitted testing one commit)
1693580,2019-05-22 21:12:36 UTC,"Setting 3.1 to WON'T FIX, since the patch does not cleanly back port to 3.1."
1693580,2019-04-05 15:15:55 UTC,I can verify that this had nothing to do with the undelete issue.
1693580,2019-04-02 13:05:39 UTC,"After applying this, attempting to undelete a title fails. I'm unsure if there's any relation, but wondered if anyone else could replicate the issue, before I started chasing red herrings."
1693580,2019-03-15 15:33:06 UTC,Fixes pushed:
1693580,2019-03-15 14:24:48 UTC,Marked bug #1716765 as a duplicate.
1693580,2019-03-15 14:10:55 UTC,"Additionally the MARC editor should probably use the 'open-ils.cat' API's since they have additional smarts baked in for handling TCN collisions, etc.  This would also resolve the silent-failure permission issue."
1693580,2019-05-22 18:32:41 UTC,"I have observed the error pop-up.  I disagree with the point about feature parity with XUL; by all rights, any attempt to edit the MARC should come up with the error. It does not serve the user to make edits, just to have to discard them.   Regardless, it does behave as intended, and I will sign off."
1693600,2017-07-19 15:48:49 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/485257"
1693600,2017-07-19 15:58:45 UTC,"Change abandoned by David Moreau Simard (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/485257
Reason: Correct, this doesn't seem required for newton."
1693600,2017-06-19 12:45:51 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1693600,2017-10-17 18:49:57 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/485257
Reason: It's unclear what is causing this in newton and tomorrow is newton-eol, so I'm going to abandon this. I asked for recreate steps a couple of months ago with no response."
1693600,2017-06-06 14:50:59 UTC,"Reviewed:  https://review.openstack.org/469548
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2868d52e42cccf539938afbb252650fb4ea4e3c5
Submitter: Jenkins
Branch:    stable/ocata"
1693600,2017-05-31 16:00:57 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469548"
1693600,2017-05-31 14:58:40 UTC,"Reviewed:  https://review.openstack.org/468147
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91bd79058abf79978335010a325952f17729d7a5
Submitter: Jenkins
Branch:    master"
1693600,2017-05-25 19:33:24 UTC,We stopped creating the instance in the API in Ocata so this has to go back to Ocata too.
1693600,2017-06-08 21:51:56 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1693600,2017-05-25 19:51:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468147"
1693609,2017-05-26 01:24:54 UTC,Agreed. You read my mind.
1693609,2017-08-21 06:51:13 UTC,It's not just about touchscreens. Even using a mouse it takes slightly longer to get the cursor exactly on the smaller icons.
1693609,2017-08-21 06:57:09 UTC,Actually we don't necessarily have to change the visual design at all. We could just add invisible padding around the circular graphics that makes their active area the same size as the bigger buttons.
1693609,2018-03-22 12:11:09 UTC,"The situation is even worse on my 13 inch laptop, with resolution 1920x1080. It seems that now gnome doesn't support fraction factor scale, so I didn't change anything except scaled font.Everthing looks fine except these three buttons, they look extremely small and hard to click."
1693609,2018-03-30 17:29:20 UTC,This bug was fixed in the package ubuntu-themes - 16.10+18.04.20180328-0ubuntu1
1693609,2018-03-31 13:42:17 UTC,"Hello, I updated my system but nothing happens, the window buttons are still very small as before, same with the click area. you can see from my screenshot."
1693609,2018-04-03 02:31:02 UTC,"The update that was released actually solved more subtle issues. It didn't solve this bug, as was mentioned in https://code.launchpad.net/~3v1n0/ubuntu-themes/windowbuttons-bg-and-padding/+merge/342171"
1693609,2018-04-08 23:33:09 UTC,"Please bare with me here, because this might not be the right way to do this, but changing the background-image size and the margin seems to look good here."
1693609,2018-04-09 01:47:57 UTC,"Thanks, but this bug is about making the buttons significantly bigger (more like Adwaita)."
1693609,2018-04-09 21:54:02 UTC,"MadsRH sent me the changes css, so that I could propose it as a usual MP"
1693615,2017-05-27 09:10:01 UTC,"I've reproduced it.  I haven't had a crash which produces the same error message, but I've achieved a fatal freeze."
1693615,2017-05-27 09:13:26 UTC,"Actually, using Task Manager, there is no jump in memory use when triggering this bug ;-)"
1693615,2017-05-27 12:08:34 UTC,"crash reproduced using Windows 10, Inkscape 0.92.1 r15371, and the drawing New document 1.2017_05_24_11_39_24.0.svg from the link in the original report"
1693622,2017-07-18 20:47:18 UTC,"Reviewed:  https://review.openstack.org/479167
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=94fdc38c867a9b5dd7cd28f77c64a6fa973336d9
Submitter: Jenkins
Branch:    master"
1693622,2017-10-03 00:25:21 UTC,APIs are in. CLI remain.
1693623,2017-10-03 00:22:56 UTC,API's are in.
1693624,2017-05-25 21:58:06 UTC,"Related
https://bugs.launchpad.net/mixxx/+bug/753301
https://bugs.launchpad.net/mixxx/+bug/888810"
1693634,2018-01-25 09:22:02 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3707
1693649,2017-05-26 04:40:41 UTC,"Further investigation shows that pause may be working, but very very slowly."
1693649,2020-05-22 05:19:19 UTC,Can you still reproduce this issue with the latest version of QEMU (currently 5.0)?
1693649,2020-05-22 12:51:32 UTC,Seems ok now.
1693649,2020-05-22 19:25:55 UTC,"Ok, thanks for checking again! So I'm closing this ticket now."
1693654,2017-06-19 12:45:58 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1693654,2017-06-08 21:51:42 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1693654,2017-05-26 01:36:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468232"
1693654,2017-05-27 13:40:29 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/468646"
1693654,2017-06-06 14:45:22 UTC,"Reviewed:  https://review.openstack.org/468646
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=893d11be86588c8da744f6bbdf24b184c2d78dc0
Submitter: Jenkins
Branch:    stable/ocata"
1693654,2017-05-27 13:16:59 UTC,"Reviewed:  https://review.openstack.org/468232
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=40cf447d28a5c9842f3546c4e7fe4efa682293cf
Submitter: Jenkins
Branch:    master"
1693657,2017-09-28 09:17:53 UTC,Something like this might work: https://pastebin.ubuntu.com/25632216/
1693665,2017-05-26 07:00:51 UTC,"Seems Jenkin job run Swift in py27, but install keystonemiddleware in py35."
1693665,2017-05-26 10:48:57 UTC,"devstack should install keystonemiddleware into python2.7 lib for swift (swift still run in py27) even if USE_PYTHON3=True, please see details in above comments, add devstack into affects project."
1693665,2018-03-19 19:40:16 UTC,"Gate setup has changed a lot in the meantime, please update with logs of current failures if the issue still exists."
1693665,2018-05-19 04:18:18 UTC,[Expired for devstack because there has been no activity for 60 days.]
1693667,2020-07-22 04:17:25 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1693667,2020-05-22 13:15:50 UTC,"This bug seems not to be a problem, and may reflect an issue with
NetBSD.  Even though the decode of the features1 register does not
include MONITOR/MWAIT, that capability is separately reported on a
separate line, further down (apologies in advance for any confusing
line-wrap):"
1693667,2020-05-22 05:17:24 UTC,"Can you still reproduce this issue with the latest version of QEMU? Looking at https://git.qemu.org/?p=qemu.git;a=commitdiff;h=0723cc8a5558c94388 for example, it might have been fixed since QEMU v4.2..."
1693670,2017-08-17 14:00:29 UTC,This issue was fixed in the openstack/zun 0.2.0 release.
1693670,2017-08-10 12:30:59 UTC,This issue was fixed in the openstack/monasca-transform 0.11.0 release.
1693670,2017-07-28 20:18:39 UTC,This issue was fixed in the openstack/networking-sfc 5.0.0.0b3 development milestone.
1693670,2017-07-28 18:54:28 UTC,This issue was fixed in the openstack/python-saharaclient 1.3.0 release.
1693670,2017-07-28 07:35:42 UTC,This issue was fixed in the openstack/zaqar 5.0.0.0b3 development milestone.
1693670,2017-07-26 18:41:41 UTC,This issue was fixed in the openstack/designate 5.0.0.0b3 development milestone.
1693670,2017-07-04 22:04:12 UTC,"Reviewed:  https://review.openstack.org/470674
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=7930f511f05d5842f59008cdc881f9b99b1adf20
Submitter: Jenkins
Branch:    master"
1693670,2017-07-19 18:11:00 UTC,This issue was fixed in the openstack/glance_store 0.21.0 release.
1693670,2017-07-17 12:04:46 UTC,This issue was fixed in the openstack/neutron-lib 1.8.0 release.
1693670,2017-07-11 13:45:20 UTC,This issue was fixed in the openstack/tempest 16.1.0 release.
1693670,2017-08-23 16:06:20 UTC,This issue was fixed in the openstack/tacker 0.8.0 release.
1693670,2017-06-23 07:19:01 UTC,"Reviewed:  https://review.openstack.org/470744
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=38498f40df885f57dea63970ab4354e85511a0c6
Submitter: Jenkins
Branch:    master"
1693670,2017-06-23 02:27:07 UTC,"Change abandoned by Van Hung Pham (<email address hidden>) on branch: master
Review: https://review.openstack.org/476321
Reason: Unnecessary patch"
1693670,2017-06-21 21:20:21 UTC,"Reviewed:  https://review.openstack.org/472581
Committed: https://git.openstack.org/cgit/openstack/glance_store/commit/?id=26241ee5d50a365afde7d576cd487577d5cdd385
Submitter: Jenkins
Branch:    master"
1693670,2017-07-26 13:30:21 UTC,This issue was fixed in the openstack/python-senlinclient 1.4.0 release.
1693670,2017-08-23 16:08:01 UTC,This issue was fixed in the openstack/magnum 5.0.0 release.
1693670,2018-02-13 10:01:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543877"
1693670,2018-01-31 19:46:47 UTC,This issue was fixed in the openstack/ldappool 2.2.0 release.
1693670,2019-03-05 14:34:30 UTC,"Change abandoned by Jens Harbott (frickler) (<email address hidden>) on branch: master
Review: https://review.openstack.org/472531"
1693670,2018-07-30 16:48:34 UTC,This issue was fixed in the openstack/aodh 7.0.0 release.
1693670,2018-07-30 15:21:11 UTC,This issue was fixed in the openstack/ec2-api 7.0.0 release.
1693670,2018-04-20 13:25:36 UTC,This issue was fixed in the openstack/monasca-ceilometer 1.8.0 release.
1693670,2018-03-19 19:54:14 UTC,Fixed in Glance by https://review.openstack.org/#/c/457235
1693670,2018-03-11 12:46:09 UTC,"Change abandoned by Min Pae (<email address hidden>) on branch: master
Review: https://review.openstack.org/472644
Reason: cue is being retired"
1693670,2017-11-06 19:12:23 UTC,"Change abandoned by Samuel Matzek (<email address hidden>) on branch: master
Review: https://review.openstack.org/472529
Reason: Abandoning due to the duplication and no updates from the author in about 5 months."
1693670,2017-06-19 19:00:50 UTC,This issue was fixed in the openstack/oslo.messaging 5.28.0 release.
1693670,2018-02-22 02:09:18 UTC,"Change abandoned by Nguyen Hung Phuong (<email address hidden>) on branch: master
Review: https://review.openstack.org/539806"
1693670,2018-02-15 00:00:14 UTC,"Change abandoned by Nguyen Hung Phuong (<email address hidden>) on branch: master
Review: https://review.openstack.org/539796"
1693670,2018-02-14 23:55:04 UTC,"Change abandoned by Nguyen Hung Phuong (<email address hidden>) on branch: master
Review: https://review.openstack.org/543873
Reason: Duplicate"
1693670,2018-02-14 06:46:55 UTC,"Change abandoned by Nguyen Hung Phuong (<email address hidden>) on branch: master
Review: https://review.openstack.org/543877
Reason: Duplicate"
1693670,2018-02-01 03:49:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539796"
1693670,2018-02-01 03:12:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539786"
1693670,2018-03-05 00:41:42 UTC,"Change abandoned by Zane Bitter (<email address hidden>) on branch: master
Review: https://review.openstack.org/472542
Reason: Irrelevant since we switched to openstackdocstheme."
1693670,2017-06-19 12:41:24 UTC,This issue was fixed in the openstack/karbor 0.3.0 release.
1693670,2017-06-08 12:32:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472238"
1693670,2017-06-14 08:09:07 UTC,"Change abandoned by Vu Cong Tuan (<email address hidden>) on branch: master
Review: https://review.openstack.org/470661"
1693670,2017-06-09 06:56:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472542"
1693670,2017-06-09 06:44:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472537"
1693670,2017-06-09 06:40:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472534"
1693670,2017-06-09 05:53:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472531"
1693670,2017-06-09 05:45:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472529"
1693670,2017-06-08 16:36:54 UTC,This issue was fixed in the openstack/keystoneauth 2.21.0 release.
1693670,2017-06-18 00:56:09 UTC,"Reviewed:  https://review.openstack.org/472593
Committed: https://git.openstack.org/cgit/openstack/meteos/commit/?id=64c3f88072288ebce86f42bef22ebc54c90421fd
Submitter: Jenkins
Branch:    master"
1693670,2017-06-08 15:27:38 UTC,"Reviewed:  https://review.openstack.org/472238
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=c6861fa915c35f0fe89fa34687861bcb92289e46
Submitter: Jenkins
Branch:    master"
1693670,2017-06-07 14:51:36 UTC,This issue was fixed in the openstack/murano-dashboard 4.0.0.0b2 development milestone.
1693670,2017-06-06 12:49:11 UTC,"Reviewed:  https://review.openstack.org/470666
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=fb262da62b33dc85b167f0ea0094bfe46f283962
Submitter: Jenkins
Branch:    master"
1693670,2017-06-06 09:03:33 UTC,"Reviewed:  https://review.openstack.org/470673
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=ef21b5798901243ec2eed4ba8af871029c33532d
Submitter: Jenkins
Branch:    master"
1693670,2017-06-05 03:58:37 UTC,"Hi Rajat Sharma,"
1693670,2017-05-28 16:25:43 UTC,"Reviewed:  https://review.openstack.org/457921
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=4eb91c8fd7ca9db3f615de4dc9cca8f6d472c43d
Submitter: Jenkins
Branch:    master"
1693670,2017-05-26 10:12:46 UTC,what is the error output like?
1693670,2017-06-08 06:58:59 UTC,"Reviewed:  https://review.openstack.org/470620
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=a0c2d904fd13aecef3674430164590c965378eb6
Submitter: Jenkins
Branch:    master"
1693670,2017-06-09 08:32:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472580"
1693670,2017-06-09 07:28:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472554"
1693670,2017-06-09 09:02:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472593"
1693670,2017-06-14 07:15:10 UTC,"Change abandoned by M V P Nitesh (<email address hidden>) on branch: master
Review: https://review.openstack.org/472537
Reason: Sorry this is duplicate of https://review.openstack.org/#/c/457235"
1693670,2017-06-12 13:21:11 UTC,This issue was fixed in the openstack/python-keystoneclient 3.11.0 release.
1693670,2017-06-12 04:53:17 UTC,"Reviewed:  https://review.openstack.org/472580
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=60dc7a3a94f28d257257f9d8cfbaa1f7732048b4
Submitter: Jenkins
Branch:    master"
1693670,2017-06-10 09:30:34 UTC,"Reviewed:  https://review.openstack.org/472600
Committed: https://git.openstack.org/cgit/openstack/python-senlinclient/commit/?id=2121b9e27c579d4ee5546202851e38d747bad151
Submitter: Jenkins
Branch:    master"
1693670,2017-06-09 21:32:25 UTC,This issue was fixed in the openstack/neutron-fwaas 11.0.0.0b2 development milestone.
1693670,2017-06-09 08:46:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472590"
1693670,2017-06-09 15:28:36 UTC,This issue was fixed in the openstack/barbican 5.0.0.0b2 development milestone.
1693670,2017-06-09 21:30:07 UTC,This issue was fixed in the openstack/networking-midonet 5.0.0.0b2 development milestone.
1693670,2017-06-09 11:39:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472648"
1693670,2017-06-09 11:22:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472644"
1693670,2017-06-09 11:12:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472639"
1693670,2017-06-09 09:45:38 UTC,"Reviewed:  https://review.openstack.org/472604
Committed: https://git.openstack.org/cgit/openstack/ldappool/commit/?id=68d46529c6b39292b10bf19108a0ca79fa2e79a7
Submitter: Jenkins
Branch:    master"
1693670,2017-06-09 09:36:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472604"
1693670,2017-06-09 09:21:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472600"
1693670,2017-06-09 09:18:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472599"
1693670,2017-06-09 12:16:23 UTC,"Reviewed:  https://review.openstack.org/470677
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=c7b3030d8980c5107a06f0c321c5856642ee8179
Submitter: Jenkins
Branch:    master"
1693675,2017-07-25 00:07:07 UTC,"@Paul Collins,"
1693675,2017-07-28 04:17:59 UTC,Juju 2.2.2 still behaves in the manner described.  This bug report is related to 1695098 only in that I encountered the difficulties described herein while trying to diagnose that other problem.
1693679,2017-08-28 09:55:06 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1693679,2017-08-12 13:08:09 UTC,"Reviewed:  https://review.openstack.org/474034
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ceb92524a9fac6e7cffcc05b1377e3cd99c1cb8
Submitter: Jenkins
Branch:    stable/newton"
1693679,2017-07-28 07:41:51 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1693679,2017-06-19 12:45:34 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1693679,2017-06-14 03:01:06 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/474034"
1693679,2017-06-14 02:37:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/474029"
1693679,2017-06-09 10:24:39 UTC,"Reviewed:  https://review.openstack.org/468269
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3342215034c7a7a938c497c39f6405763201a261
Submitter: Jenkins
Branch:    master"
1693679,2017-05-31 02:53:46 UTC,"I added ""When was this bug made?"" section to Bug Description."
1693679,2017-05-26 05:08:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468269"
1693679,2017-06-14 15:43:23 UTC,"Reviewed:  https://review.openstack.org/474029
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2a113159c00b51215f3506a9e9834fa7cc0d5ffb
Submitter: Jenkins
Branch:    stable/ocata"
1693684,2017-05-28 14:56:42 UTC,I think that getRow() is nothing changed.
1693684,2017-05-29 10:49:10 UTC,"ok, I will check."
1693687,2017-05-28 15:10:18 UTC,"I confirmed it works correctly.
Thank you RaiMan."
1693687,2017-05-28 16:47:47 UTC,"THANK YOUUUUU, for instantly testing ;-)"
1693687,2017-05-26 10:11:26 UTC,thanks for finding.
1693689,2019-12-04 08:57:11 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/500109
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1693689,2017-09-25 18:35:30 UTC,"Reviewed:  https://review.openstack.org/505805
Committed: https://git.openstack.org/cgit/openstack/group-based-policy/commit/?id=b7451022051bfc6fa2b6ecb9e52415b6217d0767
Submitter: Jenkins
Branch:    stable/ocata"
1693689,2017-09-20 21:38:59 UTC,"Reviewed:  https://review.openstack.org/505346
Committed: https://git.openstack.org/cgit/openstack/group-based-policy/commit/?id=555dc66610cde24110d708e7f4ac01e9405e37dd
Submitter: Jenkins
Branch:    master"
1693689,2017-09-20 20:50:03 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/505805"
1693689,2017-09-19 17:40:03 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/475294
Reason: Switching functional and fullstack tests to rootwrap is non-trivial job. I think we can live with spurious failures, especially now that Ocata transitioned to life support II cycle."
1693689,2019-12-04 08:56:59 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1693689,2017-09-01 15:26:54 UTC,"Aaarg, hitting the same issue I digged logs and devstack gate script shell, came to the conclusion that neutron fullstack jobs should have solved this issue (since n8g-bagpipe fullstack gate hook was stolen from neutron's), ran a git blame on neutron's gate_hook.sh and ended up here, and found a mention on n8g-bagpipe failure in the bug description."
1693689,2017-07-28 20:21:32 UTC,This issue was fixed in the openstack/neutron 11.0.0.0b3 development milestone.
1693689,2017-06-19 08:51:57 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/475294"
1693689,2017-06-09 01:40:35 UTC,"Reviewed:  https://review.openstack.org/469189
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=96a821c48b7de0017d00c43a3f9da91585873354
Submitter: Jenkins
Branch:    master"
1693689,2017-05-30 17:14:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469189"
1693689,2017-06-09 01:38:56 UTC,"Reviewed:  https://review.openstack.org/471097
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a99897ffb3e3a1247006b21103b54a71123a6b50
Submitter: Jenkins
Branch:    master"
1693689,2017-06-05 19:04:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/471097"
1693689,2017-09-09 22:21:29 UTC,"Reviewed:  https://review.openstack.org/502067
Committed: https://git.openstack.org/cgit/openstack/networking-bagpipe/commit/?id=8919a92225781588a2a8e795671cf8a0d9deb785
Submitter: Jenkins
Branch:    master"
1693691,2017-05-26 06:36:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468280"
1693691,2017-11-04 23:06:43 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/468280
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1693702,2020-03-20 19:59:21 UTC,Removing assignee due to a long inactivity and moving back to Confirmed as it seems the bug could be still valid and there is a potential fix as well.
1693702,2017-07-12 10:41:25 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1693702,2017-05-30 06:47:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469002"
1693702,2017-07-05 01:42:20 UTC,"Default policy for retype operation is admin_or_owner and Tempest tests use self.volumes_client which is owner of the volume hence should not be any issue.
We can see tests passing on gate-"
1693702,2017-05-26 07:17:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468285"
1693702,2017-07-05 02:19:20 UTC,"Has not run this case for quite some time. Will retry it later. BTW, previously, the policy has been confirmed to be correct."
1693703,2020-09-29 15:13:20 UTC,Closing because INVALID: Incomplete.
1693710,2017-10-03 09:29:32 UTC,"Reviewed: https://review.fuel-infra.org/35516
Submitter: Pkgs Jenkins <email address hidden>
Branch: 10.0/newton"
1693710,2017-07-19 07:28:38 UTC,Verified on Fuel 8.0 MU-5:
1693710,2017-09-14 08:36:26 UTC,"Verified on 9.0-2017-09-01 snapshot
Without proposed: error: argument --metadata: invalid str value: u'test=u\u0442\u0435\u0441\u0442'
With proposed: no errors
root@node-1:~# cinder create --metadata 'test'='тест' 1|grep metadata

|            metadata            | {u'test': u'\u0442\u0435\u0441\u0442'} |
"
1693710,2017-06-29 12:11:11 UTC,"Reviewed: https://review.fuel-infra.org/35511
Submitter: Pkgs Jenkins <email address hidden>
Branch: openstack-ci/fuel-8.0/liberty"
1693710,2017-06-01 17:35:26 UTC,"Fix proposed to branch: openstack-ci/fuel-8.0/liberty
Change author: Alexey Stupnikov <email address hidden>
Review: https://review.fuel-infra.org/35511"
1693710,2017-06-01 19:37:55 UTC,"Fix proposed to branch: 10.0/newton
Change author: Alexey Stupnikov <email address hidden>
Review: https://review.fuel-infra.org/35516"
1693710,2017-06-01 19:28:32 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Alexey Stupnikov <email address hidden>
Review: https://review.fuel-infra.org/35515"
1693710,2017-07-03 11:37:29 UTC,"Reviewed: https://review.fuel-infra.org/35515
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1693712,2017-05-26 08:05:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468307"
1693712,2017-07-27 07:58:54 UTC,"Change abandoned by shaofeng cheng (<email address hidden>) on branch: master
Review: https://review.openstack.org/468307"
1693720,2017-06-01 11:05:29 UTC,"confirmed on Windows 10, Inkscape 0.92+devel 15697, using the file demo_lite.svg"
1693720,2017-06-01 09:31:43 UTC,600 ppp export file
1693720,2017-06-01 09:30:07 UTC,150 ppp export file
1693720,2017-06-01 09:29:26 UTC,"My computer load it in 1 minute, I activate layers with texture only for export. And work only with one visible layer if needed. With 24Go of ram, I can work."
1693720,2017-05-29 13:03:40 UTC,"That file takes my computer several minutes to load (how do you work with that!?), although it doesn't really look that complex. Cleanup document also doesn't remove a lot."
1693720,2017-06-01 09:30:49 UTC,300 ppp export file
1693724,2017-06-02 17:02:58 UTC,Is this a feature request or a bug?
1693724,2017-06-06 02:20:15 UTC,Both. A regression in visual quality when compared to Unity7 is a bug. Even if it sounds like an enhancement :)
1693724,2017-07-11 06:57:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693724,2017-07-11 06:59:25 UTC,I come from elementary and it was the first thing i noticed. Right klick have no animation om manjaro linux (gnome shell 3.24) also
1693738,2017-05-26 17:20:12 UTC,"This is a consequence of ensuring we have a full listing, even if the cluster has been configured with a very small container_listing_limit. While two results seems fairly likely to be *all* of the results, the only way to be sure is to issue another listing starting from the end of the last one."
1693756,2018-02-05 09:31:07 UTC,fix release as LP: #1725190 does.
1693756,2017-10-20 09:45:54 UTC,"sounds good, if we just use latest modemmanager, it will be easier to apply further fix in the future."
1693756,2017-10-20 09:18:30 UTC,upgrade to 1.6.8 look good to me. AlexTu: can you also comment ?
1693756,2017-10-20 08:59:10 UTC,"After chatting with sil2100, he said that potentially we could backport artful 1.6.8 modemmanager to xenial, which would be great. I have created bug #1725190 to track that and start in a clean state from there."
1693756,2017-06-26 06:17:50 UTC,"this is the PPA that I used to test backported packages:
https://launchpad.net/~alextu/+archive/ubuntu/test"
1693756,2017-08-02 02:43:13 UTC,"@Sebastien
The final backported package in #17 has been landed to oem image. Do you have comment for also land it to Xenial?"
1693756,2017-07-04 08:05:21 UTC,"refer to versioning rule of libtool[1], there are some versioning changes added.
And this version is the candidate to be took into oem image.
The candidate binary packages could also be found in this ppa[1]"
1693756,2017-06-27 05:39:48 UTC,"followed #15, also sum things up here for expected package version change and share libs version change:"
1693756,2017-06-26 03:37:30 UTC,"Hi Sebastien,
Thanks for your review, there are some reasons to take the bumping version patch."
1693756,2017-10-06 07:02:04 UTC,version we release in oem project is: 1.4.12-1ubuntu1somerville1
1693756,2017-06-14 02:34:40 UTC,"just compared the source code of the package from maintainer's ppa[1] and the same version from Zesty, all source code are the same and just a bit change from control and rule files under debian folder."
1693756,2017-06-13 09:53:41 UTC,"The packages version of maintainer's ppa in #9 are:
libmbim	1.14.0-1+xenial
libqmi	1.18.0-1+xenial
modemmanager	1.6.4-1+xenial"
1693756,2017-06-13 02:35:14 UTC,"freedesktop upstream[1] rejected the backport operation and suggest user to add another maintainer's ppa instead:
https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-xenial"
1693756,2017-06-07 12:30:29 UTC,"The attachment ""libmbim_1.12.2-2ubuntu1.1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1693756,2017-06-07 08:47:23 UTC,debdiff of modemmanager for review
1693756,2017-06-07 08:46:49 UTC,debdiff of libqmi for review
1693756,2017-06-07 08:45:33 UTC,the debdiff of libmbim for review
1693756,2017-06-06 13:15:23 UTC,Added to Trello: https://trello.com/c/TzygcVy7/121-bug1693756-xenial-dw5816e-to-support-qmi-over-mbim-which-needed-for-fcc-authentication
1693756,2017-06-06 09:33:55 UTC,"#item fixed:
* backport needed patches to older version packages on Xenial."
1693756,2017-06-06 09:17:41 UTC,"item fixed:
* find out needed patches on newer version packages."
1693756,2017-06-20 10:26:27 UTC,Thank you for your work. I've sponsored libmbim.
1693756,2017-06-06 09:10:21 UTC,"item fixed:
 * let the newer version packages could also works well on Xenial."
1693757,2017-06-05 10:34:06 UTC,"I have the same behavior for package spl-dkms.
Please see attachment."
1693757,2017-06-30 15:00:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693773,2017-05-26 17:43:24 UTC,"Seems to do with how python-memcached [1] parses hosts. From digging in the code [2], I'd try a string like"
1693773,2017-06-16 03:25:29 UTC,I'd be curious to see if Tim's suggested work around in comment #1 works. That might give some relief until we determine how much we want to sanitize data before passing it to memcache. Or until we get a proper fix upstream.
1693774,2017-06-09 13:04:02 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1693777,2017-07-24 16:54:43 UTC,Yup; https://docs.openstack.org/swift/latest/deployment_guide.html only refers to replicas and doesn't mention EC at all.
1693778,2017-05-26 12:39:49 UTC,"The attachment ""Patch to fix privilege table structure warning"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1693780,2018-01-07 10:03:06 UTC,we should decide on backup-restore or restore-backup but not mix them.
1693780,2018-05-08 10:58:06 UTC,"I think it is sane to have us check that the target directory for the backup has at least as much free space as the size of the Mongo Database that we are backing up (ignoring the backups database itself).
We can allow passing a flag like ""--ignore-free-space"" to 'juju create-backup' in case we get that estimate wrong and the user needs to do it anyway. But by default, we can do some quick checks to make sure that we have a strong expectation of not filling our whole disk and breaking the backup in the first place."
1693786,2017-05-26 23:35:14 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1693819,2017-06-07 22:03:59 UTC,"PPA updated with the current patches.
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1693819"
1693819,2017-06-09 19:46:01 UTC,I should note:
1693819,2017-06-07 22:01:44 UTC,"Attached patches that rework the patch, instead of changing common/discover.c to strip the interface alias during name comparison, the new patch strips the interface alias in client/dhclient.c before copying the argv parameter, so dhclient does not use the alias at all.  I tested in t/x/y/z/a and dhclient still worked with normal (non-aliased) interface names, as well as working for dhcpv4 and dhcpv6 for aliased interface names, both requesting and releasing."
1693819,2017-05-26 14:43:01 UTC,"This problem is because isc-dhcp strips the interface alias when it enumerates the system interfaces, i.e. in common/discover.c function next_iface():"
1693819,2017-05-26 20:34:36 UTC,"The attachment ""lp1693819-trusty.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1693819,2017-05-26 17:18:43 UTC,This has been assigned upstream ISC bug: ISC-Bugs #45294
1693819,2017-05-26 17:03:12 UTC,"Test packages available in this PPA
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1693819"
1693819,2017-05-26 17:00:10 UTC,"This is specifically important for any configuration that wants to have both a IPv4 address and DHCPv6 IPv6 address on a single interface, and uses ifupdown for interface management, and wants independent control of the 4 and 6 address.  Meaning, to be able to add or remove an interface's IPv6 DHCPv6 address, while leaving the interface up and still configured with its IPv4 address.  The ifupdown program does not have any mechanism for controlling IPv4 and IPv6 addresses on a single interface separately, so interface aliases are the most convenient way to keep using ifupdown and be able to control the addresses separately.  An example ifupdown configuration might be:"
1693819,2017-06-07 12:00:41 UTC,"The attached debdiffs introduce a regression, please hold off applying until I can investigate and update the patches."
1693840,2017-05-31 20:09:20 UTC,Castellan does allow for passphrases to be stored.
1693845,2017-11-27 19:26:51 UTC,"Fix proposed to branch: openstack-ci/fuel-7.0/2015.1.0
Change author: Rakesh H S <email address hidden>
Review: https://review.fuel-infra.org/37305"
1693845,2017-12-12 14:24:41 UTC,"Reviewed: https://review.fuel-infra.org/37305
Submitter: Denis V. Meltsaykin <email address hidden>
Branch: openstack-ci/fuel-7.0/2015.1.0"
1693852,2017-05-26 17:45:36 UTC,"Hi, thank you for the code. We coordinate development and code review on GitHub. Please make fork mixxxdj/mixxx on GitHub and make a new pull request. Our Using Git wiki page has some more tips on getting set up: https://mixxx.org/wiki/doku.php/using_git"
1693852,2017-05-26 17:52:57 UTC,You will also need to modify build/depends.py and src/effects/native/nativebackend.cpp to include the new effect.
1693852,2017-05-27 21:33:25 UTC,"I had a short look into the code and it looks already cool, thank you."
1693852,2017-11-12 21:02:59 UTC,Does a Gater or Tremolo effect satisfy this? See https://bugs.launchpad.net/bugs/1299026
1693854,2018-05-08 18:09:53 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1693895,2017-06-21 11:40:27 UTC,With the latest kernel update Linux 4.10.0-24-generic the issue seems resolved.
1693895,2017-05-30 07:30:12 UTC,This change was made by a bot.
1693895,2017-05-28 10:09:59 UTC,Was a bit euphoric about the workaround.
1693895,2017-05-29 19:22:47 UTC,Uninstalled tlp -> Sleep works fine
1693895,2017-05-30 07:20:53 UTC,"It means there's a bug on kernel driver with runtime power management enable.
Runtime power management (RPM) is generally favorable because it can prolong your battery time."
1693895,2017-05-28 11:43:46 UTC,"This seems the normal case
---
May 28 12:37:49 mbpr15 systemd[1]: Started Suspend.
May 28 12:37:49 mbpr15 systemd[1]: sleep.target: Unit not needed anymore. Stoppi
ng.
May 28 12:37:49 mbpr15 systemd[1]: Stopped target Sleep.
May 28 12:37:49 mbpr15 systemd[1]: tlp-sleep.service: Unit not needed anymore. S
topping.
May 28 12:37:49 mbpr15 systemd[1]: Stopping TLP suspend/resume...
May 28 12:37:49 mbpr15 systemd[1]: Reached target Suspend.
May 28 12:37:49 mbpr15 systemd[1]: suspend.target: Unit is bound to inactive uni
t systemd-suspend.service. Stopping, too.
May 28 12:37:49 mbpr15 systemd[1]: Stopped target Suspend.
May 28 12:37:49 mbpr15 systemd[1]: Started Run anacron jobs at resume.
---"
1693895,2017-05-29 08:31:53 UTC,"Might be TLP related - to test, enable ubuntu budgie backports via budgie-welcome recommendations."
1693900,2017-05-30 14:35:03 UTC,"Hmmm, IMHO 'Err:' and 'W: Failed to fetch' indicate, that it was not able to update properly and thus the result of the operation is unreliable. So its like ""your connection is secured, but may be not"". I guess most people wouldn't do any financial transaction when reading this ... ;-)"
1693900,2017-05-30 23:12:51 UTC,"Well, it's more like ""this site is temporarily unavailable, please try again at a later time."""
1693900,2017-06-24 07:37:25 UTC,"Because of this bug ppa-purge misbehaves (Bug #1514839). Should one inspect the output of apt-get for '^Err:' (from standard output) or even '^W:' (from standard error) to determine, if it updated the repositories or not? Besides the output of `apt-get update` varies between versions in supported Ubuntu releases: In Ubuntu 14.04 it does not print ':' after 'Err', but ' ', instead."
1693900,2017-07-17 10:10:25 UTC,"You should probably use an API for that (like python-apt), rather than the command-line tools. We will have to rework error handling if we ever want to retry automatic updates on failures, but it's not entirely clear how this will happen yet."
1693900,2017-07-17 13:46:52 UTC,"The bug/subject here is, that apt-get doesn't return a proper exit code, not, what else one could use to workaround the bug."
1693900,2017-07-17 17:00:04 UTC,"Actually this is the problem: Users think, their system is up-to-date, but it is not for sure because a site failed to respond. Therefore only if _all_ sites answered the request properly, apt-get should return 0. If not, it should return a specified return code, which lets the callee know, that there was a problem [and imply, that a subsequent apt-get upgrade might bring the system to the latest supported state, or not]. If the exit code for such situations is documented properly, the tool can still decide, whether to run the upgrade or would be bredless art."
1693900,2017-07-17 17:27:08 UTC,"That's your opinion, and we already know it."
1693900,2017-07-17 19:29:18 UTC,"juliank, Do you mean ppa-purge should be translated to completely different programming language, and that I can not even rely on apt-get outputting something that matches '^Err[ :]' to stdout in such cases? Sounds difficult."
1693900,2017-07-17 20:03:57 UTC,"I can only tell you that either python or C++ should give you what you need at the moment. You could potentially just parse Err lines, but that's a bit hacky. As you mentioned, the output changed a bit."
1693900,2020-05-31 03:13:05 UTC,@Julian Andres Klode Is this something you'd be willing to reassess?  I saw your old message [1] on the Debian list that says:
1693900,2021-02-18 14:37:45 UTC,"For reference, ubuntu-devel post about '-o APT::Update::Error-Mode=any'
at https://lists.ubuntu.com/archives/ubuntu-devel/2021-February/041374.html"
1693900,2021-02-18 15:06:55 UTC,"Thanks Scott for digging out this bug again, I'll use it for SRUing."
1693900,2017-05-30 13:09:05 UTC,"Well, it did not fail, it re-used the existing information. Transient network errors do not cause the update to fail, because they are expected to be temporary. It's always been like this. I'm open to possibly changing this, but such a change could cause huge issues."
1693900,2017-07-17 14:39:00 UTC,"No, there are two different use cases here:"
1693901,2017-05-26 20:32:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693901,2017-05-30 17:21:07 UTC,Most everything OK !! just got bug report !!!
1693901,2021-01-07 04:13:43 UTC,4.8 EOL
1693903,2017-05-26 19:27:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468519"
1693903,2017-05-31 12:14:54 UTC,"Reviewed:  https://review.openstack.org/468519
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=590ecfb894a7da0c9a16ab9a60638963a10e48db
Submitter: Jenkins
Branch:    master"
1693903,2017-05-31 19:26:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469628"
1693903,2017-06-08 21:51:34 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1693903,2017-08-11 23:23:30 UTC,"Reviewed:  https://review.openstack.org/469628
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9f84d0d4358345c3fd29edb8da2a4d75803c11d6
Submitter: Jenkins
Branch:    stable/ocata"
1693903,2017-08-22 11:39:42 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1693912,2017-05-26 20:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1693914,2017-05-26 20:00:16 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1693918,2017-05-26 20:20:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/468534"
1693918,2017-07-06 03:34:27 UTC,"Reviewed:  https://review.openstack.org/468534
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=1f1d91b960ad8bc2b18e60ce1dd7ee0a16f46a3f
Submitter: Jenkins
Branch:    master"
1693918,2017-07-27 20:50:00 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.
1693920,2018-05-12 20:33:07 UTC,closing abandoned
1693920,2017-09-25 21:05:04 UTC,"Hi, installs here as well."
1693920,2018-04-04 21:49:50 UTC,"Hi, still installs still fine..."
1693920,2017-05-26 22:49:12 UTC,What is the problem in the installer? Does it show some screen or crashes with a Wine dialog?
1693920,2017-08-08 20:26:23 UTC,"Sorry, just saw the title ""Cumulus software not install in ubuntu-gnome"" - so it seems there is indeed an issue."
1693920,2017-08-08 20:16:34 UTC,Hi Cristian
1693920,2017-05-26 20:29:04 UTC,"Open bug in launchpad.net:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1693920"
1693924,2018-03-01 20:00:09 UTC,"I didn't get it! How to resolve the ""Active connection removed before it was initialized""?
The same bug heppens to me here and I can't find any other solution but restart the computer!"
1693924,2017-09-24 21:50:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693925,2020-04-15 11:02:21 UTC,Fixed by https://gitlab.com/inkscape/inkscape/-/merge_requests/1033
1693926,2017-06-02 14:44:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/470314"
1693926,2017-06-03 04:46:59 UTC,"Reviewed:  https://review.openstack.org/470314
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=91f20a6ef5240fcd16cb14fdd6b53913de1940c2
Submitter: Jenkins
Branch:    master"
1693926,2017-07-26 20:53:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/487584"
1693926,2017-07-31 15:02:02 UTC,"Reviewed:  https://review.openstack.org/487584
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=a27465512c74678c498680c844e7e9d091785ca0
Submitter: Jenkins
Branch:    master"
1693926,2017-06-02 11:45:50 UTC,"This seems to be related to https://review.openstack.org/#/c/453341/7/cinder/image/image_utils.py . This change is adding ""-f src_format"" to the qemu-img convert command-line, and that fails when the image type is ""ami"", because this is not a supported image type for qemu-img."
1693928,2018-09-28 16:07:54 UTC,"We should have done this via https://github.com/openstack/tripleo-specs/blob/master/specs/queens/tripleo-messaging.rst , yes?"
1693948,2017-10-17 20:10:57 UTC,The manual for journalctl for artful indicates that the default should be the full line.
1693948,2017-10-17 20:21:55 UTC,Looking at manpages for previous releases of Ubuntu they all contain the same information about --full for journalctl.  I did find lines being ellipsized in a DpkgTerminalLog.txt file. Is that what you were looking at? An example:
1693948,2017-10-17 20:25:08 UTC,Ah bug 1713435 looks like the situation you've reported. DpkgTerminalLog.txt contains the ellipsized lines but JournalErrors.txt does not.
1693948,2017-10-18 01:00:40 UTC,Thanks Brian; should we retarget this bug to dpkg to get it to show different output? or is it still apport that is collecting ellipsized logs?
1693948,2017-10-20 19:30:17 UTC,The file /var/log/dpkg.log contains the ellipsized lines so yeah I think dpkg is better place for this.
1693948,2018-10-12 10:42:40 UTC,Fixed in https://salsa.debian.org/debian/init-system-helpers/commit/5836b307724f8731b47d3d4d064ada1833182705 thus the package is fixed in version debian/1.49 and later.
1693964,2017-05-27 18:42:42 UTC,I am using Ubuntu. With lightdm
1693964,2017-05-27 17:37:00 UTC,"Are you using Ubuntu or Ubuntu GNOME?
gdm3 or lightdm?"
1693964,2017-05-27 07:02:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693966,2017-10-27 22:35:59 UTC,"The text should be: ""neutron server (neutron-server and neutron-*-plugin) This service runs on the controller node... """
1693966,2017-10-28 16:09:13 UTC,You can take the bug on if you like Miguel.
1693975,2020-07-01 21:25:11 UTC,"Sorry it took so long, but this should be addressed in the latest update (2020.0.0+really93u+20120801-7), binfmt-support is now a suggested dependency."
1693985,2017-06-02 01:58:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/470080"
1693985,2017-06-02 15:46:12 UTC,Was this in a legacy stack or convergence?
1693990,2018-01-24 22:40:39 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1427
1693992,2017-05-27 08:11:13 UTC,"#3  0x00007f66c8a93dfa in g_assertion_message_expr (domain=domain@entry=0x7f66c880cf52 ""AccountsService"", file=file@entry=0x7f66c880dc52 ""act-user-manager.c"", line=line@entry=2564, func=func@entry=0x7f66c8810438 <__func__.28806> ""load_users"", expr=expr@entry=0x7f66c880ee28 ""manager->priv->accounts_proxy != NULL"") at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gtestutils.c:2452
        s = 0x2557a30 ""assertion failed: (manager->priv->accounts_proxy != NULL)""
#4  0x00007f66c87f7b49 in load_users (manager=<optimized out>) at act-user-manager.c:2564
No locals."
1693992,2017-05-27 08:12:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1693992,2020-11-17 05:42:35 UTC,Zero crashes after 19.04 so consider it fixed.
1693993,2017-10-23 19:42:47 UTC,"Jira ticket:
https://jira.percona.com/browse/PT-211"
1693993,2018-01-24 22:40:48 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1428
1694002,2018-10-02 21:07:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694002,2017-10-21 17:09:13 UTC,Bug exists in Ubuntu 17.10 MATE final.
1694003,2021-01-07 04:03:00 UTC,4.8 EOL
1694003,2018-05-08 18:10:02 UTC,This change was made by a bot.
1694004,2017-10-11 08:50:20 UTC,Any news?
1694004,2017-11-09 14:08:04 UTC,Already fixed in Fedora and probably other distributions.
1694004,2017-11-21 14:54:37 UTC,"Here's an AppData (metainfo) file for pidgin-otr from Fedora, it should work in Ubuntu without any modifications."
1694004,2017-11-21 15:48:43 UTC,"AsciiWolf, Ubuntu's pidgin-otr is synced from Debian. Please report this issue there."
1694004,2017-11-21 22:26:27 UTC,Done.
1694004,2018-02-22 16:46:54 UTC,This will hopefully be fixed with the new pidgin-otr package release. But I think this probably won't happen before the Ubuntu 18.04 release. :-(
1694004,2018-03-31 05:08:00 UTC,Unsubscribing the Ubuntu Sponsors Team; there's nothing to sponsor.
1694004,2018-03-31 13:16:25 UTC,How this should be fixed in Ubuntu 18.04? SRU?
1694004,2019-07-09 22:34:41 UTC,Unfortunately still not fixed.
1694006,2017-05-27 11:14:39 UTC,Some more detail:
1694006,2017-05-27 12:04:06 UTC,"May 27 13:06:23 mbpr15 tracker-extract[11638]: Could not insert metadata for item ""file:///home/wolf/Documents/books/it-vertrage-kurz-und-praktisch.pdf"": 42.33: invalid UTF-8 character"
1694006,2018-11-15 22:55:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694010,2017-05-27 14:31:42 UTC,"I'm confused that this command is used to recover private directory(interactive mount), not to recover the encrypted directory(sudo mount -t ecryptfs secure raw). But it can be applied in the latter case."
1694010,2017-05-27 11:45:00 UTC,I'm going to assign this bug to me and fix this issue only by adding some if statement.
1694018,2017-06-01 17:04:28 UTC,Moved to: https://github.com/UbuntuOpenStore/openstore-meta/issues/110
1694021,2017-06-05 20:43:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694023,2017-06-13 07:40:41 UTC,Bug filed at https://bugzilla.kernel.org/show_bug.cgi?id=196051
1694023,2017-06-13 05:31:44 UTC,Please file an upstream bug at https://bugzilla.kernel.org.
1694023,2017-05-27 18:45:01 UTC,apport information
1694023,2017-05-30 16:01:59 UTC,I installed linux-image-4.12.0-041200rc3-generic_4.12.0-041200rc3.201705282131_amd64.deb but my system failed to boot so I can't test if the bug is fixed.
1694023,2017-05-30 15:14:07 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1694023,2017-05-27 18:55:41 UTC,I ran apport-collect 1694023 and changed status to 'Confirmed'.
1694023,2017-05-27 18:55:34 UTC,I ran apport-collect 1694023 and changed status to 'Confirmed'.
1694023,2017-05-27 18:45:08 UTC,apport information
1694023,2017-05-27 18:45:05 UTC,apport information
1694023,2017-05-27 18:44:59 UTC,apport information
1694023,2017-06-08 15:36:58 UTC,Bug is still there with 4.12-rc4.
1694023,2017-05-27 18:44:55 UTC,apport information
1694023,2017-05-27 18:44:56 UTC,apport information
1694023,2017-05-27 14:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1694023,2017-05-27 18:44:39 UTC,apport information
1694023,2017-05-27 18:44:40 UTC,apport information
1694023,2017-05-27 18:44:42 UTC,apport information
1694023,2017-05-31 06:34:35 UTC,Yea I think there are some issue in 4.12-rc3. Try 4.12-rc2 instead.
1694023,2017-05-27 18:44:48 UTC,apport information
1694023,2017-05-27 18:44:54 UTC,apport information
1694023,2017-05-27 18:44:52 UTC,apport information
1694023,2017-05-27 18:44:44 UTC,apport information
1694023,2017-05-27 18:44:51 UTC,apport information
1694023,2017-05-27 18:44:49 UTC,apport information
1694032,2017-08-12 17:06:58 UTC,"Sadly, all I can tell you is to go yet another level deeper and report the problem to the libxml2 project, which does the parsing here."
1694032,2017-08-12 17:18:11 UTC,"Hmm, I take that back. I couldn't reproduce this with plain libxml2 (i.e. their xmllint tool), so it must be something in lxml."
1694037,2020-11-27 21:01:14 UTC,"I also have this issue with:
MX Linux 19.3 (Debian based)
Plank Version 0.11.89"
1694037,2020-06-17 11:10:58 UTC,XFCE I meant!
1694037,2020-06-17 11:10:47 UTC,"Ubuntu 20.04 with XCFE installed, this is still very much a thing"
1694037,2020-04-24 14:47:04 UTC,Issue still apparent in Xubuntu 20.04 LTS
1694037,2021-02-02 07:29:02 UTC,"Got same issue:
Xubuntu 20.04.2 LTS
Plank 0.11.89"
1694037,2019-07-20 08:15:42 UTC,I have the same issue with Xubuntu. The only workaround seems to restart the panel with xfce4-panel -r
1694037,2020-04-06 19:33:26 UTC,"Can confirm this issue still exists in Xubuntu 20.04. Editing Panel preferences creates a Plank icon which will not close without the restart command in #7, even after prefs window closed, 'Keep in Dock' unchecked, and clicking Quit."
1694037,2018-02-20 12:54:54 UTC,"The same issue also occurs in MATE. If you right click the mate panel | properties, the mate panel icon appears in docky and stays there even after you close out of the panel properties. With MATE, clicking the icon doesn't affect the MATE panel though."
1694037,2018-06-19 10:15:06 UTC,I stumbled upon this bug today on xubuntu 18.04. Plank version: 0.11.4
1694037,2020-08-10 13:40:56 UTC,Same thing for me with Plank 0.11.89 and Xubuntu 20.04.01
1694037,2019-02-01 21:51:31 UTC,Same issue here.
1694037,2019-07-16 16:20:36 UTC,same issue with xfce4 and mate
1694037,2019-01-25 09:05:21 UTC,"I get the same issue - right click a panel > preferences, then after you close it, the icon remains in Plank. Clicking it toggles displaying the actual panel on/off. Clicking close does not remove it."
1694050,2017-05-30 18:07:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694050,2021-01-07 04:03:10 UTC,4.8 EOL
1694055,2017-12-18 21:12:36 UTC,"The tag upgrade-software-version was added first and then removed again. Could you explain why, please?"
1694055,2018-03-21 10:24:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694055,2018-03-21 13:22:51 UTC,"Hi,"
1694055,2018-03-25 10:28:44 UTC,"Hi Tronde, davfs2 1.5.4-2 package in ppa:baltix-members/ppa is 100% identical to official Ubuntu/Debian, because I simply copied sources from primary Ubuntu 17.10 archive to ppa:baltix-members/ppa 16.04 archive :)"
1694055,2020-06-27 06:10:11 UTC,"Due to the latest version is 1.5.6-0.1 on groovy and 1.5.5 on focal, I'd like to close this as Fix Release."
1694055,2020-06-28 11:25:16 UTC,">The tag upgrade-software-version was added first and then removed again. Could you explain why, please?
"
1694055,2018-03-21 10:26:58 UTC,"I've backported official davfs2 1.5.4-2 packages from Ubuntu 17.10 to 16.04 (Xenial), you can add official Ubuntu-derivative Baltix-Linux PPA - ppa:baltix-members/ppa and update, see https://launchpad.net/~baltix-members/+archive/"
1694067,2017-05-27 20:36:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1694084,2017-08-28 07:24:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694094,2017-10-12 21:23:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694094,2017-10-12 21:24:08 UTC,"I just noticed this in one of my projects.  This does seem to be a recent change.  I also have just upgraded to Artful.  The font displays correctly in Chromium, GNOME Fonts, etc.  Not quite sure what is going on."
1694095,2018-01-18 08:11:10 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1985
1694095,2017-05-29 02:30:41 UTC,Variable has global scope. Doc needs update.
1694095,2017-07-26 15:37:24 UTC,Will be tracked as part of https://jira.percona.com/browse/DOC-565
1694095,2017-05-28 23:36:38 UTC,"Also, https://www.percona.com/doc/percona-xtradb-cluster/5.7/wsrep-system-index.html#pxc_strict_mode :"
1694097,2017-05-28 05:34:03 UTC,"Hello, I think this is a problem with the Australian mirror that we are using (202.158.214.106) - I just ran into this and fixed it by using a VPN to the US."
1694097,2017-05-28 06:53:37 UTC,"On the Software and Updates panel I tried other option for Download From, but all give the same result."
1694097,2017-05-28 07:00:14 UTC,even Main Server fails
1694097,2017-08-30 22:15:54 UTC,"The issue seems to be your connection to your archive, but GNOME Software should show an appropriate error message."
1694097,2017-05-28 04:37:40 UTC,"For what it is worth, Ubuntu Software shows two available update which will not complete -- see attached screenshot"
1694097,2017-05-28 04:22:49 UTC,~$ sudo apt-get install openshot
1694100,2017-11-16 14:09:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694102,2017-05-30 19:34:46 UTC,"oooh, looks like it was a bug.   I guess this means I should try to give 1.1.2 a shot ;)"
1694114,2017-06-07 15:34:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694114,2021-01-07 04:03:15 UTC,4.8 EOL
1694121,2017-05-30 04:52:33 UTC,"It works for me, so no, it's not the same bug."
1694121,2017-05-30 16:25:17 UTC,"The linked bug report perfectly describes what I am seeing, but, if you want something more specific:"
1694121,2017-10-18 12:23:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694132,2017-06-15 06:45:06 UTC,"We just added something like this for ""reload-spaces"", we may need to consider something similar for refreshing storage information.
Most tags that we use are just passed through to maas (in the case of something like provisioning), which means Juju isn't keeping cached information that can get stale. Probably we are caching some of the storage information so we're failing to notice that things have been updated in MAAS."
1694132,2017-06-15 07:46:36 UTC,Something tells me that it may have to be even more generic.
1694149,2018-11-25 14:40:49 UTC,"Over a year later and no triage, no nothing."
1694149,2017-06-08 16:39:16 UTC,I wonder why this ticket has not even been triaged.
1694149,2017-06-18 13:12:38 UTC,Hrm.  What is the point of LTS even if bugs like this can go completely ignored?
1694153,2019-03-17 10:48:42 UTC,"This is would only be possible on certain OSes, as QScreen.model ,.make, etc is not implemented for all OSes"
1694156,2017-05-28 20:31:33 UTC,"Trying to understand why the dnsmasq is registered in /etc/resolv.conf at all, I find that it's listed in /etc/resolvconf/resolv.conf.d/tail.  So 192.168.122.1 being listed as a global DNS server is a result of local configuration, which means this problem is at least partly self-inflicted."
1694156,2017-05-29 12:15:57 UTC,"Hi Steve,
thanks for bringing that up and debugging that much already.
In regard to this issue you kind of continued in bug 1694161.
You outlined there that the reason this hit you more than others was that you added a /etc/resolvconf/resolv.conf.d/tail to make libvirts dns resolution known in the host.
I like the suggestion you made there as a proper solution via libvirt registering ""correctly"" into systemd resolvd."
1694159,2017-05-31 14:35:05 UTC,"Initial sniff tests were successful, now preparing various upgrade vectors to verify the result is the way we want it."
1694159,2017-05-31 18:39:55 UTC,"Final nail in the coffing from the second deb packager of kimchi/ginger on the mail thread [1].
(Replies might be stuck in moderation I guess, that is why I quote them)"
1694159,2017-05-31 18:47:56 UTC,"@~ubuntu-archive
per comments #8 #16 #25 and #29 I think we reached consensus and should remove the following packages from the archive in Artful:
- kimchi
- ginger"
1694159,2017-06-02 17:33:45 UTC,"It turns out mv_conffile + package rename doesn't work correctly.
It would not realize there was a changed conffile and drop the old content completely.
It would neither retain in moved file, nor in dpkg-bak which is the worst case."
1694159,2017-06-02 17:34:12 UTC,"PPA Fixes (https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2784/+packages):
FixX: is a build for Xenial to similulate an upgrade LTS->LTS with the fix.
FixA: is a fixed version for Artful to check full upgrade paths, as well as e.g. Zesty->Fix (not having old files)"
1694159,2017-06-02 17:52:12 UTC,Pushed the unreleased preliminary changes to [1].
1694159,2017-06-04 12:13:46 UTC,"Found a test issue in the TXUF cases which need to be re-ran, also we want to add cases with conflicting new content."
1694159,2017-06-05 13:10:26 UTC,"After some cleanups things make more sense now.
For >=Yakkety upgraders we really only want to clean up and not mess with their setup.
So the design slightly changed to do so as intended.
Otherwise we might ""bring back"" old changes breaking a working system.
Instead the remove + message will help to
a) clean up
b) remind the user if he wants to re-setup anything"
1694159,2017-06-05 20:34:16 UTC,"On the release notes for Artful we should add a about this along the usual Libvirt update info.
There is no release note wiki/template for Artful yet, so I added a tracker for that."
1694159,2017-06-06 15:00:04 UTC,This bug was fixed in the package libvirt - 2.5.0-3ubuntu8
1694159,2017-06-14 06:51:03 UTC,"$ remove-package -m 'Outdated, unmaintained; LP: #1694159' kimchi ginger
Removing packages from artful:
 kimchi 1.5.0-0ubuntu1 in artful
  kimchi 1.5.0-0ubuntu1 in artful amd64
  kimchi 1.5.0-0ubuntu1 in artful arm64
  kimchi 1.5.0-0ubuntu1 in artful armhf
  kimchi 1.5.0-0ubuntu1 in artful i386
  kimchi 1.5.0-0ubuntu1 in artful ppc64el
  kimchi 1.5.0-0ubuntu1 in artful s390x
 ginger 1.3.0.1-0ubuntu1 in artful
  ginger 1.3.0.1-0ubuntu1 in artful amd64
  ginger 1.3.0.1-0ubuntu1 in artful arm64
  ginger 1.3.0.1-0ubuntu1 in artful armhf
  ginger 1.3.0.1-0ubuntu1 in artful i386
  ginger 1.3.0.1-0ubuntu1 in artful ppc64el
  ginger 1.3.0.1-0ubuntu1 in artful s390x
Comment: Outdated, unmaintained; LP: #1694159
Remove [y|N]? y
2 packages successfully removed."
1694159,2017-07-06 13:20:05 UTC,Fixes needed in Debian went into 3.5.0-1 - so the merge will pick them up and the few remaining obsolete files will be correctly part of the pkg now.
1694159,2017-06-02 17:40:33 UTC,"From what I saw I think all planned use-cases and tests were correct now.
Attaching the logs."
1694159,2017-05-31 09:37:37 UTC,Interrupt on the kimchi Discussion from the Mail thread - quoting Frederic who uploaded what we have atm.
1694159,2017-05-28 20:08:52 UTC,"Note also that there is an ubuntu-virt-server package still in the archive which depends on libvirt-bin, despite being labelled transitional, and this is referenced by the virt-host task.  This all needs to be sorted before the libvirt-bin binary package could be dropped."
1694159,2017-05-31 08:53:14 UTC,"The generated line in /var/lib/dpkg/info/libvirt-daemon-system.postinst for the example of /etc/default/libvirt-bin is:
dpkg-maintscript-helper mv_conffile /etc/default/libvirt-bin /etc/default/libvirtd 1.3.3-2 libvirt-bin -- ""$@"""
1694159,2017-05-31 11:49:09 UTC,The rm_conffile was also working manually but not on the upgrade itself.
1694159,2017-05-31 08:44:15 UTC,"The list of dpkg -L libvirt-bin seems to be the ""more trustworthy"" one.
Here all of them categorized as later reference:"
1694159,2017-05-31 08:05:59 UTC,"Shortest test (WIP), it shows:
- Several dir deletes can't happen due to not-empty directories.
  Those are created later on by libvirt and the packages don't know them, those are all taken over so ""ok"".
    dpkg: warning: unable to delete old directory '/etc/libvirt/nwfilter': Directory not empty
    [...]
- Other dirs fail to delete due to stuff we forgot.
  We will handle those with rm_conffiles, but in all cases the new packages will extract things there so the dir won't (and shouldn't go away)
    dpkg: warning: unable to delete old directory '/etc/dnsmasq.d-available': Directory not empty
    [...]
- some valid handling of conffiles
  Installing new version of config file /etc/libvirt/libvirtd.conf ...
  [...]
- dpkg --status libvirt-bin listing way too much as obsolete.
  The status on libvirt-daemon-system lists them as well.
  dpkg -S Seems aware of that and lists libvirt-daemon-system is the sole owner
- some of the mv_conffiles in the package clearly did not work
  $ lxc exec ${REL}-test-virtdeps-X-to-UCA-O -- dpkg -S /etc/default/libvirt-bin /etc/default/libvirtd
    libvirt-bin: /etc/default/libvirt-bin
    libvirt-daemon-system: /etc/default/libvirtd
- dpkg -L more clearly pointing to those that are a problem"
1694159,2017-05-31 07:49:10 UTC,"Existing rules that seemed to not fully work in the past related to our reports:
  # on Steve and paelzers system
  mv_conffile /etc/default/libvirt-bin /etc/default/libvirtd 1.3.3-2 libvirt-bin
  mv_conffile /etc/init.d/libvirt-bin /etc/init.d/libvirtd 1.3.3-2 libvirt-bin
  # on Steves system
  rm_conffile /etc/apparmor.d/libvirt/TEMPLATE 1.3.3-2 libvirt-bin
  rm_conffile /etc/apparmor.d/libvirt/TEMPLATE 1.2.7-5~ libvirt-daemon-system
  rm_conffile /etc/apparmor.d/libvirtd/TEMPLATE 1.2.7-5~ libvirt-bin
  rm_conffile /etc/apparmor.d/libvirtd/TEMPLATE 1.2.7-5~ libvirt-daemon-system"
1694159,2017-05-31 07:43:55 UTC,"Both contributions to Debian seem to be accepted.
We for now can expect the following files to ""come back"":
- /etc/default/virtlockd
- /etc/libvirt/libvirt-admin.conf"
1694159,2017-05-31 07:34:53 UTC,Just to be sure I checked e.g. https://launchpadlibrarian.net/317266660/buildlog_ubuntu-artful-amd64.libvirt_2.5.0-3ubuntu7_BUILDING.txt.gz that package holds none of those conffiles - so all that is still listed on it is broken conffiles of some sort.
1694159,2017-05-30 14:32:15 UTC,Note: potentially similar issue in squid/squid3/squid transition https://git.launchpad.net/~racb/ubuntu/+source/squid3/commit/?id=bb2787bb2c0a0f3efa3d660299dd41d9e6716c57#
1694159,2017-05-30 14:27:27 UTC,I was summarizing the cases we have into three categories:
1694159,2017-05-30 14:12:52 UTC,"I got a reply on my mail which kind of echoes my sentiment for kimchi/ginger.
It referred to a similar ML post at [1].
+1 for removing them, but we have to give the owners a chance to comment."
1694159,2017-05-30 13:42:51 UTC,This bug was fixed in the package virt-manager - 1:1.3.2-3ubuntu5
1694159,2018-02-07 09:40:34 UTC,This bug was fixed in the package nova - 2:17.0.0~b3-0ubuntu3
1694159,2017-05-30 12:34:03 UTC,"Tested the virt-manager changes:
- Automated testing is only minimal but was working.
- Manual tests with the updated version worked as before
- only effect that surfaced from the change to me as a ""user"" was that libvirt-bin is now auto-removable (which is just right)
Note: I also updated the merge bug to make sure things are not lost on the merge."
1694159,2017-05-30 09:00:00 UTC,After a few checks and rewrites now there also is a merge proposal for uvtool [1]:
1694159,2017-05-30 08:49:02 UTC,This bug was fixed in the package ubuntu-virt - 1.5
1694159,2017-05-30 07:59:01 UTC,"For Nova I saw 2:16.0.0~b1-0ubuntu4 is already in artful-proposed;
git suggests that 2:16.0.0~b1-0ubuntu5 is still prepared (still at UNRELEASED). So I created a Merge Proposal for git://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/nova into ubuntu5."
1694159,2017-05-30 06:34:04 UTC,"There is no Launchpad user for Aline, so I assigned Frederic who did the initial uploads.
Yet given that Aline is listed in the recent .deb packages provided by the kimchi-project I assume she is responsible now."
1694159,2017-05-30 06:19:10 UTC,"Kimchi is currently a neglected package in the MOTU space.
The same applies to ""Ginger"".
It is severely outdated - the one in the archive is from June 2015 (Wily) and since then got no changes at all.
It had upstream a lot of changes/fixes - in general and for Ubuntu in particular."
1694159,2017-05-30 05:58:31 UTC,"There is also a Delta on virt-manager that needs to be changed.
And I realized that this could need a merge anyway - unfortunately I don't know if there just was no time yet or if there were reasons against it."
1694159,2017-05-29 18:28:44 UTC,"Can only track one as task above, other one is:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863649"
1694159,2017-05-29 18:27:51 UTC,"Bugs filed at Debian, linking up here"
1694159,2017-05-29 18:27:08 UTC,/etc/libvirt/libvirt.conf disappeared from the build log at the place /etc/libvirt/libvirt-admin.conf but is still delivered as part of libvirt-clients. So remove that from the list above that should be reported to Debian.
1694159,2017-05-29 14:01:15 UTC,"Most of this should have not existed or cleaned up long ago :-/.
But it wasn't, so we now have to decide how to distribute potential fallout the best way for end-users.
We need to ""protect"" the new files which already exist since yakkety, so we can't just move over the old ones.
There by since in most cases both (old&new) files exist, we can only rm_conffile the no more active ones to ensure users do not accidentially edit those without effect."
1694159,2017-05-29 12:26:53 UTC,"Thank you so much Steve for bringing that up, that is part of the ""inherited it that way and never needed to touch"" but it clearly should be cleaned up ""now"" as in ""artful"" to have a chance to clean it out post 18.04."
1694159,2017-05-30 11:25:55 UTC,"Brian is already working on the virt-manager merge, so no need to interrupt all the work he has done - see bug 1667114.
Which makes the virt-manager we consider here just the dependency change + a few related changes in help texts that Ubuntu adds."
1694159,2017-12-07 12:27:26 UTC,This bug was fixed in the package uvtool - 0~git136-0ubuntu1
1694159,2017-05-31 14:17:44 UTC,Moving those calls to the right package seems to be an easier fix than the referred hack in preint/postinst - I have a ppa building and testing.
1694161,2017-05-29 12:33:42 UTC,"Hi,
I only glimpsed over the implementation in NM so far. But as much as I saw there I can only agree.
Yet this clearly needs to be implemented and developed through upstream and backported/integrated from there - which will make it eventually more stable, but also slower to appear as fixed in Ubuntu."
1694165,2017-05-28 21:49:38 UTC,Here is the post on ML - https://<email address hidden>/msg106166.html
1694174,2017-10-16 16:47:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694175,2017-05-29 01:28:37 UTC,Ah unless the existing code is meaning the SAML auth at IdP end is good but fail to login into Mahara because we can't create new user so offers you to link to existing account if exists.
1694181,2017-05-30 01:26:11 UTC,Could you describe or list what scenarios are missing?  I want to add this the milestone for 0.3.0 when the scenarios are clear. It's better for this kind of bug reports to be actionable.
1694181,2017-05-30 02:20:05 UTC,I've added test scenarios. Please check if they are sufficient.
1694181,2017-09-01 08:12:38 UTC,All the scenarios are targeted to Queens release.
1694181,2017-11-27 03:32:35 UTC,"Reviewed:  https://review.openstack.org/482532
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=adeb401abcd967bd8a1d602c1b74067a15d9d901
Submitter: Zuul
Branch:    master"
1694181,2017-12-14 08:26:53 UTC,"Reviewed:  https://review.openstack.org/490351
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=5cd53f330879187fc43899db406bf30c65d95915
Submitter: Zuul
Branch:    master"
1694212,2017-06-02 19:22:45 UTC,"Reproduced again on swarm
9.2 MU-2 02/06/17 iso #06/02/17 11:58"
1694223,2017-05-29 10:42:56 UTC,"As you discovered, the default credentials are changed during installation per best practice."
1694223,2017-05-29 10:45:13 UTC,To get a cqlsh prompt on unit cassandra/0:
1694223,2017-05-29 13:06:47 UTC,"Thank you very much.
I used ""cqlsh"" instead of ""sudo -H cqlsh"" on the nodes."
1694237,2017-05-29 10:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1694237,2017-05-29 11:12:40 UTC,"Hi Brad-bot, the logs are attached since this related to autopkglogs and not a local bug report.
Setting back to New."
1694237,2017-05-29 11:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1694250,2017-05-29 11:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1694250,2017-05-29 14:30:48 UTC,Don't think this needs a log file. I have confirmed this on more than one computer so there shouldn't be any issues reproducing it from the instructions above.
1694250,2017-05-29 15:00:12 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1694252,2017-05-31 18:30:34 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1694252,2017-05-31 18:49:02 UTC,You're welcome!
1694252,2017-05-31 19:25:10 UTC,please send it upstream
1694259,2017-05-30 07:57:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694260,2017-06-23 07:33:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694269,2017-05-29 17:28:18 UTC,"Hi Fabricio,
I see you already tried several rounds of purging and reinstalling - thanks for that."
1694269,2017-05-29 17:29:21 UTC,"The TL;DR is that the server doesn't start after installation which lets the install/upgrade be considered failed. Yet since you purge and re-install it should work for you just as it does for me and others.
I hope the systemctl status output helps to get an initial lead where to look into."
1694269,2017-05-29 17:53:39 UTC,"$ systemctl status postgresql@9.3-main.service
Failed to issue method call: No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/systemd1/unit/postgresql_409_2e3_2dmain_2eservice"
1694269,2017-05-29 17:58:24 UTC,"2. ""apt-get upgrade -y --fix-missing"" is just your default upgrade"
1694270,2018-11-08 13:31:16 UTC,Patch merged to new rsyslog charm repo @ https://git.launchpad.net/rsyslog-charm/commit/?id=daebd4a6d700c518859f50caf8ff459b6af77837
1694272,2017-06-08 23:33:55 UTC,Fix committed to lp:ecryptfs as r892.
1694277,2017-10-24 11:22:08 UTC,"Seems like a reasonable change, would obviously need testing."
1694283,2019-05-27 10:09:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694284,2017-10-21 13:45:58 UTC,"Ubuntu 17.10 final with all updates - bug is not fixed.
Pressing <Alt+R> helps. What would be more user-friendly?"
1694294,2017-05-29 16:21:12 UTC,The same happens if I use the gnome-control-center
1694303,2017-09-06 12:08:29 UTC,I confirm that installing light-themes_16.10+17.10.20170817-0ubuntu1_all from Artful fixed the white-on-white issue (the monospace issue described also in #1700218 still remains).
1694303,2017-09-05 11:45:57 UTC,"I have the latest Zesty version, which is 16.10+17.04.20170406-0ubuntu1 at the moment."
1694303,2017-09-05 14:19:08 UTC,Confirmed on light-themes 16.10+17.04.20170406-0ubuntu1
1694303,2017-09-05 11:31:51 UTC,Actually I cannot reproduce this problem with
1694303,2017-09-04 14:35:25 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please report the information about the theme you are using? Also an image of the issue would be helpful. Thanks!
1694303,2017-09-05 10:56:31 UTC,"Hi. Since you're already monospace issue reported in #1700218, I will concentrate on the white commit description text."
1694306,2017-05-29 20:39:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1694323,2017-05-29 19:38:00 UTC,This was the arabic text used for testing:
1694323,2019-05-12 01:03:32 UTC,"Hi, could you provide an example of such an Arabic word? Also please provide information about your Inkscape version and operating system. Thank you!"
1694323,2019-09-19 12:11:28 UTC,"Closing as there has been no activity for 60 days. If you still have this problem, check the already reported issues at https://inkscape.org/report. Thank you!"
1694354,2017-06-05 08:16:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694354,2017-06-16 01:00:23 UTC,Upon reboot I am now unable to get-apt anything. update nada. I'm not positive this is the cause as I am new to Linux but it happened while installing this package among others. I know I am supposed to include log files but not sure which ones or where to find them.
1694358,2017-05-30 03:25:18 UTC,Attached debdiff containing the changelog and a updated debian/control file.
1694358,2017-06-10 02:55:55 UTC,"This currently doesn't make sense to SRU alone into trusty because openjdk-7 in trusty doesn't actually use it, so it can only be evaluated in context with a proposed update for openjdk-7 itself.  Have discussed this with Tiago offline, and am unsubscribing ubuntu-sponsors for now until this information is added."
1694367,2019-09-25 17:59:06 UTC,-- GitLab Migration Automatic Message --
1694367,2017-09-10 02:41:35 UTC,"(In reply to Justin Mitzel from comment #16)

> I also figured that posting here would be better than making a new bug report.
"
1694367,2017-09-09 23:11:16 UTC,"> https://vid.me/n0t1r
"
1694367,2017-09-09 16:07:56 UTC,(In reply to Michel Dänzer from comment #14)
1694367,2017-09-09 06:59:52 UTC,"(In reply to Paul from comment #0)

> Has affected mesa 12 and kernel 4.8 onwards.
"
1694367,2017-09-09 06:58:40 UTC,"(In reply to Justin Mitzel from comment #13)

> I've also had this problem,
"
1694367,2017-09-08 23:43:20 UTC,"I've also had this problem, I'm using the AMDGPU-experimental option that i've enabled in the kernels because I'm on a R9 390x. I'm in Mesa 17.1 on Kernel 4.12.11 in KDE Manjaro Linux. I am using a display port and this happens both at 144hz and 60hz. I've tried recording it using OBS, however, it did not show up in the video. I've also tried using compton and enabling full-screen reprints. Compton did not help at all, and enabling full-screen reprint v-sync helped a small amount but did not stop it from happening. Switching between Kwin and OpenGL 3.1 did not change anything."
1694367,2017-06-06 07:17:19 UTC,"(In reply to Paul from comment #11)

> Use the system and run OpenGL applications,
"
1694367,2020-03-19 21:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1694367,2017-05-30 06:31:18 UTC,"Created attachment 131571
glxinfo"
1694367,2017-06-06 01:06:57 UTC,"(In reply to Michel Dänzer from comment #8)

> To prevent tearing, you need to either choose OpenGL instead of XRender and
> an appropriate tearing prevention setting, or enable TearFree with
>
> xrandr --output eDP --set TearFree on
"
1694367,2017-06-01 03:13:38 UTC,"To prevent tearing, you need to either choose OpenGL instead of XRender and an appropriate tearing prevention setting, or enable TearFree with"
1694367,2017-05-31 22:16:36 UTC,"(In reply to Michel Dänzer from comment #6)

> Which rendering backend and tearing prevention method are selected in the
> kwin settings?
"
1694367,2017-05-31 03:30:20 UTC,Which rendering backend and tearing prevention method are selected in the kwin settings?
1694367,2017-05-30 22:41:49 UTC,"(In reply to Michel Dänzer from comment #1)

> Can you create a video demonstrating the problem when moving windows? If
> not, please describe which desktop environment / window manager /
> compositing manager you're using.
"
1694367,2017-05-30 22:28:47 UTC,"Created attachment 131585
dmesg | radeon"
1694367,2017-05-30 22:28:00 UTC,"Created attachment 131584
display modes"
1694367,2017-05-30 22:27:27 UTC,"Created attachment 131583
xorg"
1694367,2017-05-30 07:47:20 UTC,Please attach the Xorg log file and the output of xrandr and dmesg corresponding to the problem.
1694367,2017-06-06 01:19:30 UTC,"(In reply to Paul from comment #9)

> it's less obvious, but there still appears to be screen tearing
"
1694367,2017-06-06 03:51:57 UTC,"(In reply to Michel Dänzer from comment #10)

> (In reply to Paul from comment #9)
> > it's less obvious, but there still appears to be screen tearing
>
> How does that manifest, and when you do what?
"
1694370,2020-03-17 07:52:31 UTC,"Since 4.10 is not present in any Ubuntu version, I believe we can close this bug."
1694373,2018-11-01 19:21:24 UTC,*** Bug 783260 has been marked as a duplicate of this bug. ***
1694373,2018-11-01 19:21:24 UTC,*** This bug has been marked as a duplicate of bug 707973 ***
1694373,2018-11-02 01:11:59 UTC,Scrolling with a touchpad and mouse wheel are quite different things. The former is continuous and the latter discrete button events. But if bug 707973 improves the wheel case too then let's keep this as a duplicate.
1694373,2019-03-15 02:37:32 UTC,No longer tracking:
1694373,2019-10-07 15:42:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694373,2020-01-13 07:44:40 UTC,Reopened because resolving bug 707973 did not solve this one.
1694373,2020-01-13 07:08:46 UTC,"Hmm that upstream status is wrong, or linked to the wrong bug. It's definitely NOT fixed with the latest master code yet."
1694373,2017-11-01 09:48:29 UTC,Almost a duplicate of bug 707973. Possibly. Not quite.
1694373,2020-01-13 07:47:42 UTC,Moved to upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=783260
1694373,2020-01-13 07:53:16 UTC,The described issue is:
1694373,2020-01-13 07:57:08 UTC,"Yes, the page being ""stuck"" in the middle is more desirable. Because that way it's scrolling at the same pace as everything else in the world that responds to mouse wheels."
1694373,2020-01-13 07:58:18 UTC,"Then you're asking for a large-scale redesign. What about workspaces, which use exactly the same scrolling model and can't be made continuous?"
1694373,2019-10-21 17:11:22 UTC,I guess https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/605 fixes this
1694373,2017-10-14 21:54:04 UTC,*** Bug 788996 has been marked as a duplicate of this bug. ***
1694373,2017-05-30 11:28:45 UTC,"Personally, this is much worse with a touchpad than with a mouse."
1694373,2017-05-31 02:17:59 UTC,Gnome Shell app grid scrolls too quickly with mouse wheel.
1694373,2017-05-31 02:12:14 UTC,"Touchpad scrolling is covered by bug https://bugzilla.gnome.org/show_bug.cgi?id=707973
but I think that's not relevant to mouse wheels."
1694373,2016-12-22 10:19:46 UTC,I think about something that could work but should be implemented in libinput.
1694373,2016-12-19 17:38:19 UTC,*** Bug 775936 has been marked as a duplicate of this bug. ***
1694373,2016-09-26 23:26:20 UTC,"Hi all, if the previous proposed patch isn't suitable, here is what I've proposed in a duplicate reporting of this bug;"
1694373,2016-09-26 22:22:05 UTC,*** Bug 772017 has been marked as a duplicate of this bug. ***
1694373,2015-11-16 10:43:51 UTC,*** Bug 758142 has been marked as a duplicate of this bug. ***
1694373,2015-05-05 16:32:16 UTC,"How pagination works on MacOS with a trackpad, from: https://support.apple.com/en-gb/HT4721"
1694373,2015-04-15 20:04:47 UTC,*** Bug 747938 has been marked as a duplicate of this bug. ***
1694373,2015-03-19 10:21:52 UTC,Review of attachment 254782:
1694373,2015-03-19 02:05:09 UTC,*** Bug 727206 has been marked as a duplicate of this bug. ***
1694373,2015-03-19 02:04:59 UTC,*** Bug 731197 has been marked as a duplicate of this bug. ***
1694373,2013-09-12 13:25:55 UTC,"Currently scroll on touchpad devices are managed like pointer
devices scrolling. But since most touchpad devices are smooth
scroll capables, they trigger a lot of scroll-event for each
little change with the fingers.
Also, interpolated events cause that the view keeps scrolling
after the user raise his hand.
For a discrete elements inside a scrollView like the appPicker
it is annoying, since it changes pages for each little change.
Also, although we guess how to solve that; it still changes pages
after the user raise his hand."
1694373,2020-01-13 08:00:48 UTC,No need to focus on the solution right now. So long as the problem description is accurate then that's all I'm concerned about. That means keeping this bug open.
1694373,2017-05-31 02:20:01 UTC,Using: gnome-shell 3.24.2-0ubuntu4
1694373,2020-01-13 08:05:11 UTC,"Ok. Anyway, paginated scrolling cannot be 100% smooth with a mouse wheel, so I'm not positive it's possible to fix this other than tweaking the timeout without breaking the whole paginated model. Anyway, switching multiple pages per flick is impossible now, so :shrug:"
1694373,2013-09-12 13:25:58 UTC,"Created attachment 254782
appDisplay: Improve touchpad scroll on app picker"
1694375,2017-05-30 12:44:10 UTC,"@Alberto, yes."
1694375,2017-05-30 06:25:12 UTC,Log collected right after the system was installed.
1694375,2017-05-30 10:08:25 UTC,"This means that the problem is already in the archive, and installing the new driver is not the actual issue. Is this correct?"
1694375,2017-05-30 06:54:50 UTC,Log collected right after updating system again following the nvidia 375 installation.
1694375,2017-05-30 06:35:11 UTC,"Log collected right after installing nvidia 375, rebooting and getting the black screen."
1694376,2017-05-31 07:36:41 UTC,https://review.openstack.org/469000
1694384,2017-05-30 23:12:57 UTC,@Mark Sapiro
1694384,2017-05-30 16:55:54 UTC,Thanks for your report. I will fix the mailman-owner@VIRTUAL_DOMAIN issue. I will also address exposing the (mildly obfuscated) list owner addresses in the web page footer ( see the thread at <https://mail.python.org/pipermail/mailman-developers/2017-May/026047.html>).
1694385,2019-09-17 10:27:53 UTC,Migrated to https://github.com/widelands/widelands/issues/2078
1694387,2018-05-02 15:05:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694389,2017-08-28 01:15:03 UTC,This issue was fixed in the openstack/neutron 10.0.3 release.
1694389,2017-06-09 21:34:21 UTC,This issue was fixed in the openstack/neutron 11.0.0.0b2 development milestone.
1694391,2017-05-30 08:10:55 UTC,"To resolve the issue all I needed to do was:
$ sudo service postgresql start"
1694397,2017-06-24 13:53:41 UTC,Duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848799
1694400,2018-03-21 01:40:13 UTC,"I'll be glad to include a fix for this from someone who uses Windows, but as a non-Windows person, there's no way I can develop a solution."
1694404,2017-05-30 09:43:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694409,2017-05-30 13:51:14 UTC,"Thanks Daniel, could you maybe report the bug to Debian BTS since the changes should be done there as well"
1694409,2017-05-30 15:54:54 UTC,It's what the upstream project is called
1694409,2017-05-31 02:48:17 UTC,"Yes, the name libav was taken from the internals of ffmpeg's libav* libraries. If both libav and ffmpeg provide similar such libav* libraries then then project name ""gst-libav"" is not totally incorrect. Just the existence of a project that is called 'libav' which we actually no longer use is terribly confusing. I blame the people who forked libav from ffmpeg :)"
1694409,2017-08-30 06:19:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694409,2019-03-01 01:46:35 UTC,"If the package name still contains ""libav"" then this bug is not fixed."
1694409,2019-03-01 01:48:10 UTC,It appears the Debian bug was also closed prematurely. Just changing the description is less than half the fix required.
1694422,2017-07-19 04:26:51 UTC,"(I'm pretty sure we have other bugs for this, but we should also only expose an endpoint at a time, not everything in an application, but that also requires charm work because I don't think we track which ports are opened for what endpoint yet.)"
1694422,2020-09-23 16:59:46 UTC,All the required bits for supporting this feature have already landed on the develop branch. I have added a small writeup of how everything works together here: https://discourse.juju.is/t/granular-control-of-application-expose-parameters-in-the-upcoming-2-9-juju-release/3597.
1694422,2017-06-05 10:06:15 UTC,"Thanks for filing the bug Rick, it would certainly be a useful feature for apps where you want business wide access but possibly without users having to authenticate. Also keeps people who like to get pen tested happy because the ports aren't open to the general public."
1694422,2017-06-01 01:25:24 UTC,I think this should be solved by specifying a space for the application.
1694422,2017-05-30 12:26:48 UTC,"The internal provider firewaller APIs have already been refactored to supported opening ports for specific subnets, with ""open to the world"" being just a case of using CIDR 0.0.0.0/0. Yes, this was done for cross model relations."
1694422,2017-07-19 04:22:44 UTC,"We could use a space, but we would need to model ""spaces that you can't use for deploy"" first. At least from what I've seen, this has mostly been about exposing your services to other networks (eg, expose from AWS to my private cloud, without exposing to anyone else).
But you can't deploy ""on AWS"" to my private cloud."
1694427,2017-05-30 13:19:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694427,2017-07-09 17:48:22 UTC,This is now fixed in 3.2.1-16
1694428,2017-06-01 14:51:09 UTC,"Maybe we don't need an additional setting for this.
We could show the CCLI license only if a ""CCLI song number"" has been entered in the song editor."
1694430,2019-05-26 20:25:01 UTC,Fix committed
1694438,2017-05-30 13:33:34 UTC,This also affects PackageKit 1.0.1-2 in Debian Jessie.
1694451,2017-07-27 08:24:28 UTC,I have checked the branch so I can pick a new issue. Simple is better you're right. However I'll do this on Saturday.
1694451,2017-07-26 19:16:00 UTC,This is quite a large and complicated task for a first contribution. Please provide more details about your plans before you start implementing this. How do you intend to expose this in the GUI? We have a major redesign of the library GUI in progress ( https://github.com/mixxxdj/mixxx/pull/1117 ). It would probably be best to start working from that branch.
1694451,2018-09-20 18:06:20 UTC,"Due to lack of progress, marking Triaged and clearing assignee. Feel
free to revert if it is in fact still in progress :)."
1694451,2017-07-27 11:59:32 UTC,I'm afraid this is not a one day task. Could you make a mockup of how you intend to integrate this into the GUI?
1694451,2017-07-26 18:04:06 UTC,I'm using Qt Creator or Clion depending on purpose on Mac OS. For such case it would be affect to develop on Mac OS.
1694451,2017-07-27 13:46:02 UTC,I mean I can pick one easy bug for the first time. I should check all the easy-to-handle bugs firstly. I can only do this on Saturday.
1694451,2017-07-26 13:58:24 UTC,"Hi Daniel,"
1694451,2017-05-30 22:28:34 UTC,"Isn't this use case covered by crates and the crate filter ( https://github.com/mixxxdj/mixxx/pull/1263 )? Also, the library redesign branch ( https://github.com/mixxxdj/mixxx/pull/1117 ) adds a search filter for the library directory."
1694451,2017-07-26 17:25:25 UTC,"Cool. Thank you. Which IDE you will use on which Os?
This is a good start to read:
https://www.mixxx.org/wiki/doku.php/bugfix_workflow"
1694451,2017-05-30 18:30:57 UTC,This is already supported by the Mixxx command line.
1694451,2017-06-06 10:13:50 UTC,"What if implement some kind of profiles in options, like in games. That will implement the feature about ""rehearsal mode"", different libraries and other. Also you can take someone's computer, load your profile (with settings too, optional path to music) and go on DJing."
1694451,2017-07-04 19:05:20 UTC,"Hi Onur thank you for picking this up.
Do you need a helping hand?"
1694451,2017-06-01 20:52:54 UTC,"If a user wants for example two kind or star ratings, it is not covered.
https://bugs.launchpad.net/mixxx/+bug/1352126
https://bugs.launchpad.net/mixxx/+bug/973136
He may also want two kins of cues ..."
1694466,2017-05-30 15:32:04 UTC,"A small discussion about this can be found at https://github.com/painless-security/moonshot-portal/issues/775, where it was originally reported."
1694468,2017-08-08 14:31:05 UTC,"Similar issue here, probably linked to bug 1709316."
1694470,2017-05-30 16:00:11 UTC,If no LPE no problem.
1694470,2017-05-30 16:03:12 UTC,"Not related to clip is only LPE problem, with any LPE"
1694474,2017-06-19 14:08:03 UTC,This continues to happen in the same way as described above. This is a showstopper for CI jobs running in an automated way.
1694474,2017-06-20 17:36:05 UTC,Could you please do:
1694474,2017-06-21 12:57:31 UTC,"Hi Manoj,"
1694474,2017-08-04 18:04:31 UTC,This UCA issue has been documented here also:  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657440
1694474,2017-10-19 21:08:23 UTC,"Hello Rafael,"
1694474,2019-03-20 15:53:24 UTC,"I've marked the issue as ""Incomplete"" since we don""t have fresh news from reporter and based on comment #5 the issue should now be fixed."
1694474,2020-09-04 08:16:37 UTC,I believe that this has also been finally resolved with https://bugs.launchpad.net/cloud-archive/+bug/1772060
1694476,2017-06-11 13:19:50 UTC,Hi
1694476,2017-06-11 13:33:43 UTC,"About the UI problem, I do have some suggestions :"
1694476,2017-06-08 23:00:21 UTC,The minus (-) sign means NOT and keywords get a red background. I'm not sure which special character could be used for OR and which background color. As long as it is not misleading it's OK.
1694476,2017-06-08 22:52:50 UTC,"Not sure how the translation goes, but here is a screenshot about what I am talking about."
1694476,2017-06-08 21:18:46 UTC,"Am I correct that you are referring to the ""Tagged journal entries"" block?"
1694476,2017-06-11 05:54:07 UTC,"Yes, that is the ""Tagged journal entries"" block. I'll leave this open as wishlist item though right now I don't know how best to incorporate it with the current UI without it becoming confusing and too technical."
1694496,2017-05-30 17:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1694504,2017-06-01 04:39:14 UTC,Thanks for this Tyson.
1694513,2017-05-31 05:01:31 UTC,"Hey Steve,
Yes I was installing Nvidia proprietary driver for my 960MX in Xubuntu
using "" software and updates only"" GUI. Software and updates then
additional drivers then selecting the Nvidia driver and apply changes. It
keeps apply changing for hours on end.And doesn't get completed. I am new
to ubuntu and Xubuntu basically. I don't really know why is it not
installing the driver"
1694513,2017-05-31 16:26:24 UTC,"Thanks for the response.  I don't know why this has failed for you; we have seen problems with the debconf socket when using gnome-software, but this is the first report I've seen for this particular problem with software & updates.  It's possible that if you closed the window too soon, the install still running in the background was unable to contact the frontend."
1694513,2017-05-31 17:03:14 UTC,"The install went well after an sudo apt-get upgrade. I don't what was the
fault but there is another issue. As soon as I installed the propriety
Nvidia driver. After about 10 minutes , My system touched about 90 degree
Celsius. Showed on lm-sensors detection. Worried what was going on I
rebooted it and still the fan was blowing out heat and the gpu part of the
laptop became very hot. It could be well described like the GPU gets really
hot while playing a high FPS game on windows. So i shifted back to X.org's
driver now."
1694513,2017-07-25 19:09:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694513,2017-05-30 20:10:13 UTC,The error in your log is:
1694516,2017-05-30 19:09:08 UTC,Another regression of the infamous r15047 [1] which seems to have caused more issues than it solved?
1694516,2017-05-30 20:26:17 UTC,"- not reproduced on Windows 10, Inkscape 0.92.1 r15371, 32 bit build, using an embedded png file. Instead I get a status message at the bottom of the frame, saying ""No Objects to convert to path in the selection"""
1694524,2017-05-31 21:42:35 UTC,"Is this duplicate of bug 1694505 or followup work after https://review.openstack.org/#/q/Ic86b5eeae25a916c3c51f21e6820f5b0212dd5f8,n,z is merged?"
1694524,2017-06-01 04:26:46 UTC,"Alan, it's a separate bug. It's just that without bug 1694505 TripleO gate may have been unaffected."
1694540,2017-11-08 08:14:50 UTC,"I also had the same issue.
I use the following parameter and now i don't have any problems:"
1694547,2017-06-01 12:43:07 UTC,"after upgrading firmware, getting new set key failed errors and wifi not stable:
upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=195957"
1694547,2017-05-30 22:00:20 UTC,This change was made by a bot.
1694547,2017-05-31 08:05:45 UTC,Same with latest upstream kernel: 4.12.0-041200rc3-generic
1694547,2017-05-31 08:38:10 UTC,"Please download firmware in [1] and put it to ""/lib/firmware/""."
1694547,2017-05-31 09:34:14 UTC,I'm using rc-3
1694547,2017-05-31 09:44:38 UTC,It means it still successfully loads -27.ucode.
1694547,2017-05-31 12:02:49 UTC,"Bug reported here:
https://bugzilla.kernel.org/show_bug.cgi?id=195945"
1694554,2019-07-23 12:17:08 UTC,The relevant traceback:
1694557,2017-05-30 22:57:56 UTC,Update: I do see that it is possible for Airdc to show different 'update on' when i change folders so something make the 'Reload' not update the date if i choose a folder and do a 'Reload' on it.
1694559,2017-05-31 08:15:11 UTC,"We have precedence of not putting Ping RPC calls into the log even at DEBUG
level. It feels like tracking when logs get forwarded might be something
that would be useful to actually see, but I think it's reasonable for now
that we could suppress it by default."
1694560,2017-06-27 22:34:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694560,2017-06-02 20:41:11 UTC,Based on this comment: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1308714/comments/8 this seems related to #1308714.
1694561,2017-09-01 19:29:24 UTC,Can this be confirmed to be solved? I have a Lenovo Yoga 720 13'' and I am able to boot with 4.10.0-32-generic but not with 4.10.0-33 nor 4.12.9-041209 nor 4.12.10-041210 from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
1694561,2017-06-03 16:19:11 UTC,Same issue with Dell XPS 13 9343 and Intel Core i7-5500U CPU.
1694561,2017-06-02 20:02:22 UTC,@iLogin That does revert the troublesome commit and mainline at that commit boots for me.
1694561,2017-06-02 16:09:50 UTC,revert a broken PAT commit that broke a number of systems
1694561,2017-05-31 11:29:38 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1694561,2017-05-31 00:25:18 UTC,"I am unable to run apport-collect running 4.12-rc3, because I cannot actually boot my computer (an immediate kernel panic occurs, as evidenced by adding the output from earlyprintk=efi), so I'm marking this bug as confirmed. Please also see relevant discussion about this issue on the Linux Kernel mailing list: http://lkml.iu.edu/hypermail/linux/kernel/1705.3/04549.html"
1694561,2017-05-31 00:00:13 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1694561,2017-05-30 23:33:11 UTC,"It appears a kernel panic is happening immediately while attempting to boot 4.12-rc3, it doesn't happen on 4.12-rc2.
Adding earlyprintk=efi to the grub command line options, I get the following message (which explains why the bootloader stops at 'loading initial ramdisk...'):"
1694561,2017-06-03 16:28:22 UTC,Issue resolved with today's build http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-06-03/
1694568,2017-07-06 15:52:52 UTC,related bug - https://bugs.launchpad.net/evergreen/+bug/1677343
1694573,2017-05-31 23:11:47 UTC,"A number of problems in autopilot mode have allready been identified and corrected in version 3865. This should solve the problems with station stops.
This version also corrects a problem with AI trains not terminating at the end of their route."
1694573,2017-05-31 23:33:34 UTC,"Yes... thx! Platform stops fixed in 3866... just downloaded. Wipers still there, and yes, appearing with rain on, and still there in 3866. But that problem hadn't been in earlier builds, so I mistakenly associated it with this."
1694573,2017-06-01 01:12:42 UTC,"Correction. The wipers problem remains. Yes, associated with Rain/snow and autopilot. Problem disappears when either of those conditions not present. Oddly, hour time of game appears at left (beginning) of message string... so for example, ""00:01:30 Wipers on/off"" (on/off toggles continuously and appears to relate to speed of train)."
1694600,2017-08-04 10:47:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694605,2017-05-31 06:24:27 UTC,"it's a valid issue.
as far as i know no one is working actively on this."
1694606,2017-06-13 09:02:20 UTC,"Tried reproducing the bug. I used the ocata stable version on ubuntu 16.04 to verify the same.
I could see the subnet create command is returning the output first and then the delete output(cursor returning not any text) is displayed which I think is the correct order.
Please verify and let me know if I am missing anything."
1694606,2017-06-19 11:02:21 UTC,What is the expected behavior here? We can't really guarantee even without rabbitmq problems that one client will return before another one.
1694611,2017-11-17 16:54:27 UTC,Seen again here: http://logs.openstack.org/64/521064/3/check/heat-functional-convg-mysql-lbaasv2/f96c950/job-output.txt.gz
1694611,2018-02-20 22:04:37 UTC,A similar fix to bug 1732969 would probably do the trick.
1694616,2017-09-27 04:12:01 UTC,This issue was fixed in the openstack/zun by Rajat Sharma.
1694616,2017-08-18 08:01:50 UTC,This issue was fixed in the openstack/cloudkitty 6.0.0 release.
1694616,2017-08-10 12:30:39 UTC,This issue was fixed in the openstack/monasca-api 2.2.0 release.
1694616,2017-07-27 13:33:12 UTC,This issue was fixed in the openstack/watcher 1.3.0 release.
1694616,2017-06-12 13:22:44 UTC,This issue was fixed in the openstack/zaqar 5.0.0.0b2 development milestone.
1694616,2017-06-08 16:47:40 UTC,This issue was fixed in the openstack/senlin 4.0.0.0b2 development milestone.
1694616,2017-06-08 11:37:50 UTC,This issue was fixed in the openstack/watcher 1.2.0 release.
1694616,2017-06-07 04:25:23 UTC,"Reviewed:  https://review.openstack.org/469363
Committed: https://git.openstack.org/cgit/openstack/cloudkitty/commit/?id=34190c5794208c85fa89e3ac3de925d74ce75088
Submitter: Jenkins
Branch:    master"
1694616,2017-06-05 06:16:38 UTC,"Reviewed:  https://review.openstack.org/469717
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=f2f31c81d3235e850609d750921910848f505de8
Submitter: Jenkins
Branch:    master"
1694616,2017-06-14 06:50:17 UTC,"Change abandoned by Vu Cong Tuan (<email address hidden>) on branch: master
Review: https://review.openstack.org/470197"
1694616,2017-06-02 01:26:18 UTC,"Reviewed:  https://review.openstack.org/469720
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=f47fd9ac5ee89025cb368e47001816fdff357953
Submitter: Jenkins
Branch:    master"
1694616,2017-05-31 07:46:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469363"
1694616,2017-06-01 01:55:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469709"
1694616,2017-06-01 02:20:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469717"
1694616,2017-06-01 02:45:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469724"
1694616,2017-06-02 08:09:22 UTC,"Reviewed:  https://review.openstack.org/469405
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=ae24d85962f36e214b1e01585109ffc9dec6e669
Submitter: Jenkins
Branch:    master"
1694616,2017-06-01 03:50:29 UTC,"Change abandoned by miaohb (<email address hidden>) on branch: master
Review: https://review.openstack.org/469724"
1694616,2017-06-01 08:41:03 UTC,"Change abandoned by feng.shengqin (<email address hidden>) on branch: master
Review: https://review.openstack.org/469709"
1694616,2017-06-01 09:27:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469821"
1694616,2017-06-01 09:32:48 UTC,"Change abandoned by wanghao (<email address hidden>) on branch: master
Review: https://review.openstack.org/469821"
1694616,2017-06-01 03:02:59 UTC,"Change abandoned by feng.shengqin (<email address hidden>) on branch: master
Review: https://review.openstack.org/469717"
1694619,2020-12-26 04:17:21 UTC,[Expired for tempest because there has been no activity for 60 days.]
1694619,2020-10-26 10:48:06 UTC,"Due to the fact that this was created more than 3 years ago I'm gonna mark it as Incomplete. A lot of changes have been merged since than - the test got renamed at minimum - the following is showing no data:
http://status.openstack.org/openstack-health/#/test/tempest.api.compute.servers.test_device_tagging.DeviceTaggingTest.test_device_tagging?duration=P3M"
1694619,2020-10-26 10:43:27 UTC,removing the assignee due to a long inactivity
1694619,2017-07-11 10:43:23 UTC,"Hi! FYI: Just met this issue again (logs at http://78.46.57.153:8081/refs-changes-74-472674-21/console.log.out)
This is probably hard to reproduce as it happens not very often."
1694619,2017-06-23 14:09:07 UTC,The test passes on my setup. I would try to make the server build fail by hacking into the code and reproduce the error or if you can give some more inputs on how you got to this condition.
1694619,2017-06-22 11:40:41 UTC,A possible reason
1694621,2017-05-31 08:22:55 UTC,"The following patches were skipped because we already carry them for bug #1687512 ""Kernel panics on Xenial when using cgroups and strict CFS limits"":
- sched/fair: Do not announce throttled next buddy in dequeue_task_fair()
- sched/fair: Initialize throttle_count for new task-groups lazily"
1694621,2017-06-28 16:35:34 UTC,This bug was fixed in the package linux - 4.4.0-83.106
1694624,2017-06-01 19:22:42 UTC,"IMHO we should be sure that our new default skin ""fits all"". For the other skins we may consider to do a very optimized for any visual disablements in one case, or just optimized for high fashion.
We should be clear about which skin solves which requirements. So that we later are aware of that and not destroy these features by accident."
1694624,2017-06-02 03:01:21 UTC,"We should not ship skins that are impractical for color blind users. It is not okay to only have one acceptable skin for color blind users and multiple choices for others. Fortunately, I do not think very much needs to be changed in any skin. In LateNight, it is the same red color used throughout. In Deere, I think it is only the red knob notches and the red metaknob link inversion button that do not work well. In Tango, the problem is also the red used in the skin. If we can figure out a different color instead of red, I think it will be okay. I'll try different shades of orange."
1694624,2018-03-08 11:25:07 UTC,"I don't think that's too bad, you have the contrast difference already so even in monochrome you would be able to see in the indentations. I could suggest maying the brighter bit at the end of the line on the knobs just a little bit bigger or brighter in colour but that's about it...."
1694624,2020-07-05 11:49:22 UTC,"in https://github.com/mixxxdj/mixxx/pull/2913 all knobs are improved, finally."
1694628,2017-08-08 01:52:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694629,2017-10-09 08:08:04 UTC,"I think I might have some additional feedback.
The workstation is a 64bit and so it the os.
But I think that the video card has 32Bit HW. Once I reinstalled Ubuntu 32Bit, it is working again.
Hope this feedback helps a little."
1694642,2017-06-01 15:37:13 UTC,PR: https://github.com/snapcore/snapcraft/pull/1342
1694642,2018-02-25 00:01:07 UTC,"The PR Has been rejected in June. Are you still working on this? If you're not and being a high priority bug, perhaps we should assign to nobody and change status to Confirmed."
1694644,2017-06-01 08:23:47 UTC,"Hi Reetesh,"
1694644,2017-09-11 13:48:16 UTC,"Hi,"
1694644,2017-08-15 16:34:38 UTC,I have the same issue in my internal project.
1694644,2017-09-11 12:51:54 UTC,"Hi Tejas,"
1694644,2017-09-11 13:24:49 UTC,"Hi eDeviser,"
1694644,2017-05-31 12:59:10 UTC,"Hi Reetesh,"
1694644,2017-05-31 20:18:20 UTC,"Hi Tejas,"
1694670,2017-05-31 11:23:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694670,2017-05-31 16:30:31 UTC,"This crash has the same stack trace characteristics as bug #1693540. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package."
1694670,2021-01-07 04:03:20 UTC,4.8 EOL
1694697,2017-07-27 20:32:40 UTC,"Hello Julian, or anyone else affected,"
1694697,2017-07-27 20:37:21 UTC,"Hello Julian, or anyone else affected,"
1694697,2017-09-13 16:00:18 UTC,This bug was fixed in the package apt - 1.4.6~17.04.1
1694697,2017-07-31 16:25:52 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1694697,2017-07-31 16:25:38 UTC,This bug was fixed in the package apt - 1.2.24
1694697,2017-07-28 20:31:30 UTC,"Ah, i did not upgrade libapt-pkg5.0 as i wanted to leave some packages for the auto-upgrader test case."
1694697,2017-07-28 09:47:18 UTC,"Using:
ii  apt                                             1.4.6~17.04.1                amd64"
1694697,2017-05-31 22:01:17 UTC,"This affects all active releases AFAICT, so we should issue SRUs for these. It's questionable how to test the pre-1.1 release in trusty, though - they do not support build-dep from a file, so the test will be more complex - maybe it's not really worth it."
1694697,2017-07-28 09:35:14 UTC,"Using:
ii  apt                                             1.2.24                       amd64                        commandline package manager"
1694697,2017-05-31 21:38:45 UTC,This bug was fixed in the package apt - 1.4.5
1694697,2017-05-31 13:07:11 UTC,Fixed in upstream release 1.4.5. Now we only need to wait for it to sync :)
1694697,2017-05-31 12:27:26 UTC,"This also causes crashes in python-apt due to a off-by-one error in size checking there, see 1694702"
1694697,2017-07-28 10:03:51 UTC,"I'd say you forgot to upgrade libapt-pkg5.0 - the test is run in CI and autopkgtest too, so it's highly unlikely to not work."
1694699,2017-06-21 11:04:50 UTC,"Reviewed:  https://review.openstack.org/473711
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=004de67f83fcda84b78744c87221d4987972b405
Submitter: Jenkins
Branch:    master"
1694702,2017-05-31 12:27:17 UTC,"The underlying problem is caused by bug 1694697 actually, but this is still a bug on its own."
1694702,2019-05-28 11:48:16 UTC,"Can't reproduce the crash on xenial, though, so not entirely sure how to verify the bug yet."
1694702,2019-05-28 11:45:02 UTC,"This was fixed before 1.6, so only xenial and trusty affected at most."
1694713,2017-05-31 16:53:50 UTC,You still would need to support xml themes as well as we know not everyone updates as soon as a version comes out!
1694713,2017-05-31 16:44:53 UTC,We should probably only do this once 2.6 has been released.
1694716,2017-05-31 14:05:45 UTC,Stupid me.. Sorry.
1694716,2017-06-05 17:56:39 UTC,"Well.. don't ask me why or how, but all the computers were good to print the next day. No updates were made, nothing was changed anywhere..
The only thing different is that the printer was disconnected (not turned off) for 30 sec."
1694716,2017-05-31 14:00:15 UTC,I forgot to mention.
1694716,2017-12-15 11:04:32 UTC,"OK, I'm seeing this issue as well."
1694731,2017-06-14 15:51:26 UTC,All tasks have been completed and the bug is being set to Fix Released
1694734,2017-05-31 15:48:26 UTC,For completeness the controller version is 2.1.2 and the model version is 2.1.1.
1694734,2017-06-01 01:16:59 UTC,Possibly related to bug 1649637
1694734,2017-06-01 20:58:49 UTC,"Unsure if 1649637 has the same root cause, but I can still replicate it consistently on trusty instances: http://pastebin.ubuntu.com/24741077/"
1694734,2017-06-01 21:23:17 UTC,"It also seems that doing the reboot via `juju ssh` does not cause the failures, so the transaction cause seems reasonable."
1694734,2017-07-11 19:15:38 UTC,WORK AROUND
1694734,2018-02-26 12:08:43 UTC,https://github.com/juju/juju/pull/7552
1694736,2017-06-01 02:53:41 UTC,"These are only run when ssh validation is enabled, which was made the default in devstack last week:"
1694736,2017-06-02 13:18:12 UTC,"tempest.api.compute.servers.test_device_tagging is the only test that fails whith ssh validation enabled, the other tests works fine. We may need to find out what the guest is doing, it maybe could not start properly."
1694743,2017-05-31 17:13:11 UTC,"Hi charles,"
1694743,2017-05-31 17:01:14 UTC,recent versions of the charms should support the proxy settings on the model if they are declared and pass them to the snapd systemd environment.
1694743,2017-05-31 17:31:09 UTC,xref with  https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/270
1694743,2017-05-31 17:51:41 UTC,"Charles, for master charm we don't gave http_proxy variables, only for
workers"
1694743,2017-05-31 21:27:40 UTC,Try setting the snap_proxy configuration value on both the worker and the masters and this should unblock you.
1694743,2017-06-01 09:32:34 UTC,"Charles,"
1694743,2017-06-01 15:10:36 UTC,I'm glad this worked! I'm going to close this bug as incomplete as we have an open and running bug series for this issue over on the github repository. Should you encounter any further issues I encourage you to file/update the bugs there.
1694745,2017-05-31 19:05:51 UTC,"Just observed this with a juju2 environment on which agents were in a ""lost"" state."
1694758,2017-06-01 13:26:08 UTC,"(sorry, the indentation was lost in my example, but I think the point is clear)"
1694758,2017-06-07 15:59:43 UTC,"So, my proposal from comment #1 is probably not correct."
1694758,2017-06-01 13:23:50 UTC,"Regarding point 3 (attaching volume to the instance), the configuration passed from cinder connection only includes the options written in nfs_shares_config file. See"
1694760,2017-05-31 17:11:41 UTC,"Note: raising the cap ""solved"" the issue for me, but I think a corner-case bug is still there."
1694766,2017-05-31 17:30:09 UTC,This change was made by a bot.
1694766,2017-05-31 18:34:47 UTC,You may need to run the following from a terminal:
1694770,2017-09-11 15:03:43 UTC,edso:
1694770,2017-07-21 14:37:53 UTC,This bug is still present in Duplicity v0.7.13.1
1694770,2017-09-09 02:56:54 UTC,Bug is still present in Duplicity 0.7.14.
1694770,2017-09-09 21:39:24 UTC,The duplicity trunk 0.8 series does seem to work with the current version of azure-storage
1694770,2017-09-11 10:26:39 UTC,"David,"
1694770,2017-09-21 21:21:52 UTC,I've been testing with the latest public release of duplicity and it no longer works with 0.20.3 of Azure... getting the following:
1694770,2018-04-13 22:15:55 UTC,This will work with
1694770,2018-04-13 22:35:28 UTC,I like to add there is some time of solve on the version of 0.8.0 of duplicity
1694770,2017-07-21 14:36:04 UTC,There is no error as well when using old version of azure-storage 0.20.3 (coming into Azure SDK 1.0.3).
1694777,2017-05-31 17:55:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694779,2020-08-11 13:39:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694787,2017-08-03 08:18:58 UTC,The dmesg you attaches is not related to this issue.
1694787,2017-08-02 16:41:54 UTC,"Yes, it's the one that came with the laptop. I can't isolate the exact problem. It'll initially work  for a few minutes when I first plug it in, then it'll become completely unresponsive and I'll have to unplug it and use wireless. Then if I plug it in an hour later, it'll work fine for hours."
1694787,2017-08-02 07:25:02 UTC,Which dongle do you use? Is it a Dell one?
1694787,2017-08-02 04:17:37 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1694787,2017-06-02 12:10:28 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1694787,2017-05-31 19:00:19 UTC,This change was made by a bot.
1694787,2017-05-31 18:39:02 UTC,"The only suspicious entries in my /var/log/syslog from the time of the crash, are a few entries like:"
1694787,2017-08-02 04:33:03 UTC,"The default kernel in Ubuntu 16.04 is not stable on the Dell Precision 5520. I had to upgrade to 4.10.0-27 for this problem to go away. However, the ethernet dongle still does not work reliably."
1694799,2018-11-25 21:05:31 UTC,"Hi. I am so sorry, but it will not be fixed soon.
Best regards."
1694799,2017-05-31 21:37:56 UTC,Complicate implementation in the current code. I'll leave the bug as reminder. Thanks for the feedback.
1694799,2018-11-24 19:44:34 UTC,"Any status on this? It would be really useful to set intermediate point, basically to select alternative route."
1694800,2017-07-17 23:31:57 UTC,I have installed kernel 4.12.2 and have zero crashes in over 24 hours with several TB of network traffic through it. This is a first time in over a year. Seems stable but will let it burn in before calling it resolved by the kernel upgrade.
1694800,2017-07-17 03:11:25 UTC,You need to file an upstream bug or raise the issue to mailing list.
1694800,2017-07-16 20:07:09 UTC,I just noticed the recommended kernel of 4.12. I have installed the latest 4.12.2 and am currently testing
1694800,2017-05-31 19:30:14 UTC,This change was made by a bot.
1694800,2017-06-10 04:04:51 UTC,FYI I have since reinstalled with 17.04 and have the same crashes.
1694800,2017-06-10 03:58:57 UTC,I have had this issue since i first built this machine and installed 14.04 when 14.04 was current version. I can't remember what update this occurred after it was a long time ago. I thought this was a hardware issue originally. I am happy to try upstream kernel however i can't get ZFS to run and is required for my workflow. If someone can provide an upstream kernel with ZFS support I would be happy to install it and give it a try.
1694800,2017-06-02 12:09:57 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1694800,2017-07-16 09:38:30 UTC,I have removed zfs and migrated back to mdadm and was able to install an upstream kernel (4.10.17-041017-generic) and this issue persists.
1694800,2017-07-21 08:00:03 UTC,"I thought 4.12.2 fixed this issue but it just now crashed again.
I have replaced every single piece of hardware. CPU(fx and ryzen), mobo(asus and MSI), memory, hard drives(WD blue and re4 for boot disk, with red for storage array) , video card(nvidia and ATI).
The only commonality is Ubuntu with a large(7+TB) disk array on some kind a 64bit AMD CPU(i have not tried intel) with and without proprietary CPU code. I have used zfs and mdadm. I switched from samba to nfs for shares."
1694808,2017-06-01 08:43:00 UTC,"Have you tried whether it works with the latest upstream version of QEMU (currently version 2.9) - since you've marked this as upstream QEMU problem, too?"
1694808,2017-06-02 06:02:59 UTC,"Thanks Thomas, definitely worth to check.
@Colin - if you want a quick and easy short with qemu 2.8 you can try  [1]."
1694808,2017-06-11 13:28:29 UTC,"Same problem with qemu 2.8 from Ubuntu Cloud Archive.
Is that enough to consider the bug highly likely in latest upstream version too? I don't have a QEMU build system at hand right now.."
1694808,2017-06-13 09:21:36 UTC,"Doesn't happen when adding another UHCI controller and explicitly connecting the keyboard to it, like: -device vt82c686b-usb-uhci,id=myusb -device usb-host,bus=myusb.0,hostbus=3,hostaddr=2"
1694808,2020-11-08 01:08:34 UTC,"Hi,"
1694830,2017-05-31 21:54:20 UTC,+1
1694839,2018-01-10 19:11:33 UTC,This is still occurring in 1.4.3.
1694839,2019-11-18 14:13:54 UTC,"(let* ((t1 '(not (cons float t)))
       (t2 `(or (not (cons (eql 0)
                           (real -3.926510009989861d7 -3.926510009989861d7)))
                (not (cons t (eql 0))))))
  (subtypep t1 t2))"
1694839,2019-11-18 14:29:04 UTC,"That was from test SUBTYPEP.CONS.43 in ansi-test, which was added back in SBCL 0.9.6.57."
1694842,2018-01-10 21:44:26 UTC,"Changing ironic-inspector state to incomplete. The bug was for IPA, and fixed in ironic's devstack plugin. I'm unsure if any further action is required in ironic-inspector at this time."
1694842,2017-10-16 13:23:05 UTC,"Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: master
Review: https://review.openstack.org/469837
Reason: I think this is no longer needed"
1694842,2017-10-06 17:32:16 UTC,"Change abandoned by Ramamani Yeleswarapu (<email address hidden>) on branch: master
Review: https://review.openstack.org/489778
Reason: Testing complete."
1694842,2017-10-06 17:31:14 UTC,"Change abandoned by Ramamani Yeleswarapu (<email address hidden>) on branch: master
Review: https://review.openstack.org/499768
Reason: Testing complete. Patch merged."
1694842,2017-10-06 17:30:58 UTC,"Change abandoned by Ramamani Yeleswarapu (<email address hidden>) on branch: master
Review: https://review.openstack.org/492664
Reason: Testing complete. Patch merged."
1694842,2017-10-06 17:28:52 UTC,"Change abandoned by Ramamani Yeleswarapu (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/495432
Reason: Testing complete. Patch merged."
1694842,2017-10-06 17:28:26 UTC,"Change abandoned by Ramamani Yeleswarapu (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/495430
Reason: Testing complete. Patch merged."
1694842,2017-10-06 14:46:24 UTC,"Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/495428
Reason: Hi! As stable/newton goes EOL really soon, I have to abandon this change."
1694842,2017-08-18 21:03:10 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/495432"
1694842,2017-08-31 19:44:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/499768"
1694842,2017-08-18 20:53:32 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/495428"
1694842,2017-08-17 14:29:45 UTC,This issue was fixed in the openstack/ironic 9.0.0 release.
1694842,2017-08-10 19:44:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/492664"
1694842,2017-08-09 23:48:05 UTC,Posted a patch to project-config to enable tls for ironic gate jobs (except the grenade jobs):
1694842,2017-08-03 07:43:25 UTC,"Reviewed:  https://review.openstack.org/469836
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=f75ff901a9e9253e695900f5a821f39a1a5dfb67
Submitter: Jenkins
Branch:    master"
1694842,2017-08-01 23:29:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/489778"
1694842,2017-06-15 14:45:07 UTC,"Hi Dmitry, a fix is needed for ironic-inspector as well?"
1694842,2017-06-01 10:39:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/469837"
1694842,2017-06-01 10:39:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469836"
1694842,2017-06-01 10:32:57 UTC,"Moved to ironic, as I think it should be fixed in the devstack plugin."
1694842,2017-08-18 20:58:57 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/495430"
1694844,2019-11-01 13:05:09 UTC,"Reviewed:  https://review.opendev.org/469675
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=07a24dcef7ce6767b4b5bab0c8d3166cbe5b39c0
Submitter: Zuul
Branch:    master"
1694844,2019-09-23 21:49:33 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/684141"
1694844,2019-09-25 18:55:22 UTC,"Reviewed:  https://review.opendev.org/684141
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f212b855835d226189b202001bba97bb8c289179
Submitter: Zuul
Branch:    master"
1694844,2017-05-31 22:46:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/469675"
1694845,2017-05-31 22:51:31 UTC,I believe this issue duplicates this: https://groups.google.com/forum/#!topic/linux.debian.bugs.dist/g2S4E-QvmWA
1694845,2017-09-12 19:15:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694856,2017-06-05 13:02:35 UTC,That's probably the bug in kernel with amd gpu.
1694863,2020-12-10 03:08:23 UTC,"I no-longer have the system, or a system that can reproduce it, so I guess we'll just close this report..."
1694863,2020-12-04 03:39:10 UTC,"Thank you for the report, Paul."
1694863,2017-07-17 16:15:22 UTC,Thanks for the update; changing status.
1694863,2017-06-28 22:16:33 UTC,"Created attachment 106365
stacktrace of plasmashell"
1694863,2017-06-14 15:16:17 UTC,"If you can provide the information requested in comment #1, please add it."
1694863,2017-06-01 08:04:39 UTC,"If it is hanging, can you get us a backtrace of it blocking please."
1694863,2017-06-28 19:29:42 UTC,"To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment."
1694863,2017-06-01 00:42:51 UTC,"If pulseaudio becomes unresponsive or is in a bad state, plasmashell can hang, leaving the entire graphical system unresponsive unless you can kill and restart pulseaudio."
1694885,2017-06-01 03:24:30 UTC,"All this is in the ""checkbox"" testing app."
1694893,2017-06-05 20:09:51 UTC,"tl;dr: I think we should add a hard-switch script, that bypasses mojo any tests and juju-waits, and just does the minimum needed to switch services, and also make it obvious from juju status which service is currently active."
1694894,2017-06-01 04:28:09 UTC,I have observed this with 4.0.0.0-15 build
1694902,2017-06-27 03:33:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477733"
1694909,2017-06-02 00:40:13 UTC,I did a quick analysis.
1694909,2017-06-02 03:38:59 UTC,"Hi Ghada,"
1694912,2018-03-29 13:43:03 UTC,This issue is still present in latest nemo (3.6)?
1694913,2017-06-02 10:24:31 UTC,"Thanks, I found this in Newton, those above commits can solve my problem, and why we do not directly delete the instance files and path on destination host after revert a resize task?"
1694913,2017-06-01 13:16:43 UTC,On which release is this happening? I believe the console.log ownership issue has been fixed in newer releases.
1694913,2017-06-01 13:18:07 UTC,See https://review.openstack.org/#/c/392643/ and https://review.openstack.org/#/c/466088/ - do you have those fixes?
1694913,2017-06-05 09:17:00 UTC,"It is need to delete the instance files and path on destination host after revert a resize task, I try a live migration after revert a resize task when use rbd, and I see the error log like below"
1694913,2017-06-05 09:18:34 UTC,"I found this in Pike (devstack-master), and do live migration again will succeed"
1694913,2017-06-27 19:27:55 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1694913,2017-06-29 11:47:25 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1694913,2017-10-31 23:07:35 UTC,"Reading through the comments on this report, it sounds like there is no bug on the master branch and that this issue was noticed in the newton release, and thus we could close this bug and abandon the accompanying patch. Is that correct or have I misunderstood something?"
1694913,2019-09-27 08:46:43 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/469814
Reason: Bug sits in incomplete status since 2017-10-31. Bug reporter did not clarified the question. Bug reported against Newton that is EOL."
1694923,2017-06-07 18:58:49 UTC,I found another report about the same - which increases the severity in a sense of being an issue for more people.
1694923,2017-06-05 18:54:14 UTC,"I'll set it to confirmed, although I'm not sure what to do in general to cover your case and the potential others as well. Because if we consider this a default case that the default config should handle well, there could be way more."
1694923,2017-06-02 09:05:35 UTC,"> My unimportant opinion is - yes - it should find and try to compress all old files.
> Because there is no guarantee the job ran on the former days.
"
1694923,2017-06-02 07:42:44 UTC,"On the very interesting +0 vs -0 discussion I read the manpage that due to rounding +0 actually means yesterday. So while +/-0*24 is surely 0 we know that in the special case +0*24 is actually a day.
So -0 might just be a day in the other direction?"
1694923,2017-06-02 07:40:39 UTC,"Hi Thorsten,
while I'm not the logrotate expert I tried to read into your case trying to understand it.
I see your issue being many files (since they change names often) being found and tried to be compressed.
For you question in the last paragraph:
""So what is the intended behavior of the log rotating script? Should it find all modified files AT LEAST changed 24 hours ago, but arbitrary old? If so, shouldn't that script have an upper limit to make it more compatible with names like mine?"""
1694923,2017-06-02 07:45:06 UTC,"Setting incomplete since I'll wait on your feedback to my suggestions for now.
That should not stop others to chime in in case there are other ideas."
1694926,2019-11-29 12:59:34 UTC,"------- Comment From <email address hidden> 2019-11-29 07:58 EDT-------
Boost Context support has been implemented as part of the OpenMainframeProject:"
1694926,2020-04-24 08:11:58 UTC,"------- Comment From <email address hidden> 2020-04-24 04:00 EDT-------
IBM Bugzilla status-> closed, Fix Released by all requested distros"
1694926,2020-04-09 09:39:10 UTC,To late to enable this for focal - will do so in 'g'
1694926,2020-01-11 04:45:03 UTC,This bug was fixed in the package boost1.71 - 1.71.0-4
1694926,2019-12-10 13:11:18 UTC,"------- Comment From <email address hidden> 2019-12-10 07:54 EDT-------
Changed Target to Ubuntu 20.04. Please integrate"
1694926,2019-11-29 15:19:31 UTC,"------- Comment From <email address hidden> 2019-11-29 10:15 EDT-------
Re-opened also in Bugzilla"
1694926,2019-11-29 15:06:44 UTC,I can't remember if ceph has a vendored copy of boost or not. So reopening that task as well.
1694926,2018-10-02 13:18:09 UTC,Looking at https://www.boost.org/doc/libs/1_68_0/libs/context/doc/html/context/architectures.html I still do not see boost-context support for s390x.
1694926,2017-06-01 12:52:35 UTC,Working around this by disabling the beast frontend for rgw in ceph (inline with upstream ceph commits); however would be good to get these functional on s390x as well.
1694926,2017-06-20 13:59:47 UTC,"------- Comment From <email address hidden> 2017-06-20 09:49 EDT-------
(In reply to comment #4)

> The Boost packaging currently excludes s390x support for Boost.Context and
> Boost.Coroutine; These are required to support Ceph >= 12.0.3.
>
> Working around this by disabling the beast frontend for rgw in ceph (inline
> with upstream ceph commits); however would be good to get these functional
> on s390x as well.
>
> I do not believe these modules have been ported to s390x upstream.
>
> Boost Context need porting upstream:
> http://www.boost.org/doc/libs/1_64_0/libs/context/doc/html/context/
> architectures.html
>
> Coroutine depends on Context.
>
> This needs to be fixed upstream.
>
> Can you elaborate as to what ""beast frontend for rgw"" is?
>
> Emailed IBM contacts asking if anybody can look into porting Boost Context
> to s390x.
>
> The 'beast frontend' is a new HTTP frontend for the Rados Object Gateway
> base on async io, rather than the current default which is fastcgi.
>
> This is all quite new still, so its not the default.
>
> according to:
> https://github.com/ceph/ceph/blob/master/debian/rules#L25
> https://github.com/ceph/ceph/commit/25d794d98a68134f8097ed434909822ded0425df
> initial porting seems to be required
"
1694926,2017-06-20 07:29:27 UTC,"------- Comment From <email address hidden> 2017-06-20 03:25 EDT-------
The Boost packaging currently excludes s390x support for Boost.Context and Boost.Coroutine;
These are required to support Ceph >= 12.0.3."
1694926,2017-06-19 15:11:47 UTC,"according to:
https://github.com/ceph/ceph/blob/master/debian/rules#L25
https://github.com/ceph/ceph/commit/25d794d98a68134f8097ed434909822ded0425df
initial porting seems to be required"
1694926,2017-06-13 13:07:22 UTC,"The 'beast frontend' is a new HTTP frontend for the Rados Object Gateway base on async io, rather than the current default which is fastcgi."
1694926,2017-06-13 12:00:21 UTC,"Can you elaborate as to what ""beast frontend for rgw"" is?"
1694926,2017-06-13 11:28:14 UTC,"Boost Context need porting upstream:
http://www.boost.org/doc/libs/1_64_0/libs/context/doc/html/context/architectures.html"
1694926,2017-06-06 16:55:17 UTC,I do not believe these modules have been ported to s390x upstream.
1694926,2020-10-08 18:08:32 UTC,This bug was fixed in the package ceph - 15.2.5-0ubuntu1
1694926,2017-10-13 11:21:22 UTC,"Correct, this is not super-urgent. It is a nice to have. Current total list of packages that could use boost context / coroutine is rather small:"
1694928,2017-06-02 12:01:53 UTC,Can you post any errors you are seeing?  Maybe take a screenshot or digital picture?
1694928,2017-06-01 09:00:21 UTC,This change was made by a bot.
1694940,2017-06-01 11:24:07 UTC,"Hi Zoltan, this was an unintended and unfortunate consequence of a website change last week. I've started working on recovery."
1694940,2017-06-01 14:04:41 UTC,"Hello David, thank you very much."
1694940,2017-06-01 14:30:30 UTC,"Zoltan, I'm very aware of this and recovery is a priority."
1694940,2017-06-01 14:47:11 UTC,"David, thank you very much for your efforts!"
1694940,2017-06-02 13:11:01 UTC,Following up: I've received a db backup and I've been able to load it into a local old-devportal instance. Now working on locating which posts have not been replicated on Insights and what to prioritize.
1694940,2017-06-12 22:35:17 UTC,"Note that even the posts that have been replicated on Insights received updates (not only adding clarifications, but also adding whole sections for new features) contain valuable information that are not in the Insights posts (since the Insights posts were not updated)."
1694940,2017-06-12 22:37:13 UTC,It would be nice if I could fix the mistakes in my comment here too ;)
1694940,2017-06-13 16:57:08 UTC,"Hello David,"
1694960,2020-09-22 07:08:19 UTC,Closing because INVALID: Support request.
1694960,2017-06-02 09:51:32 UTC,"as far as I can tell, the file SAMPLE.svg was not created by Inkscape. It does not have a section called <sodipodi:namedview/> in it, which a typical Inkscape file would normally have. So you may need to investigate to see where the file came from, to find the source of the problem with the viewbox."
1694960,2017-06-02 03:31:46 UTC,"So it appears that Inkscape wrote wrong XML code?
Anyways, thanks for the help."
1694960,2017-06-01 11:21:36 UTC,"could you attach the svg file, for testing purposes?"
1694960,2017-06-01 11:54:04 UTC,"Oh, and another thing. Can I reply to this post using Evolution?"
1694960,2017-06-01 11:53:28 UTC,I'm sorry if the file don't show up a thumbnail and Inkscape can only see this file. I tried opening it on Chrome and it show nothing. I opened it with the image viewer on GNOME and the window glitches.
1694960,2017-06-01 15:32:38 UTC,"- confirmed on Windows 10, Inkscape 0.92.1 r15371"
1694962,2017-06-13 05:05:44 UTC,This is a part working patch I found lying around...
1694962,2017-06-12 09:46:11 UTC,"Do you have a branch with wip code somewhere Robert? I might try take a
look Into this later when work calms down a bit"
1694962,2017-06-08 04:50:41 UTC,We don't plan to do this for Ubuntu as we're using GDM [1]. Keeping open as it still would be desirable to do for those who do use LightDM and want to try GNOME.
1694962,2017-06-05 23:37:58 UTC,When I try to run GNOME Shell as a greeter the background doesn't render and the titlebar pixels start to bleed together. I get the same issue just running an X server on its own and running G-S in it.
1694962,2017-06-01 16:26:53 UTC,FYI: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1686393/comments/5
1694964,2019-07-11 16:37:51 UTC,"Fixed in revision 807b8d4cf13db5299c61c889210c57bd78398f9f
https://git.launchpad.net/kicad/patch/?id=807b8d4cf13db5299c61c889210c57bd78398f9f"
1694965,2017-06-19 11:00:44 UTC,I see a lot of DOWN ports in that output. All ports should be going to ACTIVE before you can expect them to work.
1694965,2017-06-19 12:05:59 UTC,"Hi Kevin,
just checked today the deployment and it works.
Might be some race condition, at the moment of opening this bug we had some other issues caused by different services, probably due this https://bugs.launchpad.net/neutron/+bug/1694420."
1694968,2017-06-06 15:21:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694980,2017-06-01 12:43:15 UTC,"I meant to say at the start of the description that the UI becomes unresponsive AFTER I move the cursor / read head around on the time line or move the clips on the time line, not just on loading the title."
1694985,2018-11-02 15:41:57 UTC,Version 1.3.4 from August 2018 https://leafletjs.com/2018/08/21/leaflet-1.3.4.html
1694985,2017-06-01 13:18:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1694988,2017-07-25 08:29:01 UTC,This has affected us deploying dualstack services so it would be good if it received more priority.
1694988,2017-07-26 03:42:44 UTC,"Enabling ipv6 on AWS is not in our immediate plans. if it is a blocker for people we can look to prioritize it but it  mean interrupting other work. It doesn't sound like a quick fix (knowing when the subnet has ipv6, setting start instance flags, and updating information to cloud init).
AIUI there is quite a bit of complexity from AWS side (something about doing a v4 DHCP first, then reading metadata, then triggering *another* dhcp6 request."
1694988,2019-11-22 08:26:13 UTC,"For this, we're working around it with the AWS CLI commands below:"
1694989,2017-06-03 06:46:21 UTC,"Ah, that makes sense. Downgrading importance then to match that this is actually working as dpkg intends it to work and us not refusing it is really just a usability issue."
1694989,2017-06-01 13:48:54 UTC,"Yup, something odd is going on there."
1694989,2017-06-02 21:02:26 UTC,Confirmed on artful with apt version 1.4.6.
1694989,2017-06-02 23:12:03 UTC,Is it really /any/ which I can't confirm at the moment as holding e.g. apt & dpkg works just fine…
1694989,2017-06-03 13:12:47 UTC,"Managed to get access, they weren't installed - once installed apt mark works as planned. Sorry for the wild goose chase, guys."
1694989,2017-06-03 11:37:46 UTC,"Just to confirm, both packages are installed on my system. (Can't be much more help as am a few thousand miles away from it until Tues.)"
1694995,2018-02-17 17:10:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695016,2017-06-02 06:23:49 UTC,"Thanks for the patch! We usually use an unified diff format, but don't worry, your file is perfectly usable, and it's great you took some time to investigate and find a fix!"
1695016,2017-06-05 07:04:36 UTC,"Fixed in the trunk rev. 15730.
Thanks for the patch, Mathieu!"
1695016,2017-06-05 07:05:39 UTC,And backported to the lp:inkscape/0.92.x rev. 15434.
1695016,2017-08-31 20:21:37 UTC,"Sorry, I did it wrong.
Testing with a bunch of svg I saw that Radial gradients often reference Linear Gradient Too.
So the best way I found is to simply remove the condition so it always work. Maybe people more aware than me could tell if there might be side effects."
1695019,2017-06-02 02:12:03 UTC,Assigning to gcc since it's just a compiler crash. Nothing obviously wrong with the nvidia driver.
1695019,2017-06-02 02:39:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695025,2018-01-18 08:11:11 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1986
1695036,2018-03-09 09:36:03 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1695036,2017-06-01 17:35:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1695036,2017-06-01 16:53:54 UTC,"Further to this, if the rectangles in the Display setup are set with the base of the right box 50% up the side of the left, the cursor will not move right of the lower 50% of the laptop screen or more left of the upper (non-overlapping) portion of the ASUS screen, however in the overlap area the mouse will still enter the receiving screen at the same proportional height as it was on the screen left, ie it is moving as if the screens were set horizontally aligned"
1695036,2017-06-01 21:30:38 UTC,Done: https://bugzilla.gnome.org/show_bug.cgi?id=783331
1695049,2017-06-16 13:53:07 UTC,"I'm leaving this bug for now. It's valid, but we have a trivial workaround for what we need (compare the hashes directly) and it looks like this doesn't affect today's upstream so it should get fixed in the Ubuntu development release in the end with no specific action."
1695049,2017-06-13 15:06:55 UTC,Also affects python3-pygit2 0.24.2-2build1 on Artful.
1695053,2017-06-06 11:52:44 UTC,OOPS-bb08a5d6e59825f47121f8269ce9c045
1695056,2017-06-08 14:18:45 UTC,https://www.redhat.com/archives/libvir-list/2017-March/msg01089.html
1695056,2017-06-08 21:00:39 UTC,"Very hard to make libvirt 3.2.1 work on ubuntu 16.04, existing latest package is 1.3.1.
Is it possible to expose hard_limit as a flavor key, or to disable /locked as an alternative flavor key? My understanding with hugepage, memory cannot be swapped, so no need for /locked."
1695056,2017-06-09 10:43:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472633"
1695056,2017-06-09 10:45:36 UTC,Wei Zhu can you try that patch [0]? Basically it's what libvirt is doing start to 3.1.0 [1]
1695056,2017-06-08 14:16:07 UTC,"Wei Zhu, can you try with a recent version libvirt (3.2.0 at least) it seems that now libvirt automatically set the limit to unlimited when using locked?"
1695056,2017-06-09 21:03:51 UTC,"With kernel 3.18 (since commit 3e32cb2e0a12b6915056ff04601cf1bb9b44f967) the
""unlimited"" value for cgroup memory limits has changed once again as its byte
value is now computed from a page counter.
The new ""unlimited"" value reported by the cgroup fs is therefore 2**51-1 pages
which is (VIR_DOMAIN_MEMORY_PARAM_UNLIMITED - 3072). This results e.g. in virsh
memtune displaying 9007199254740988 instead of unlimited for the limits."
1695056,2017-06-13 15:26:15 UTC,What exactly is the error ? can you share the traceback so at least I can explain the problem on the fix as a side note.
1695056,2017-06-13 15:41:52 UTC,"It's basically same mlock error as memtune option is not there, I think due to the value of sys.maxint >> 10 is too big. When I hardcoded smaller value or used ""sys.maxint >> 10 - 3"" then memtune option appeared."
1695056,2017-06-13 15:51:29 UTC,"Here with HARD_LIMIT_UNLIMITED = sys.maxint >> 10 <memtune> option is missed,"
1695056,2017-06-09 12:33:40 UTC,"Using newton, my fakelibvirt.py file content is a bit different, driver.py is fine,"
1695056,2017-06-13 14:06:51 UTC,"Sahid, Can we use ""HARD_LIMIT_UNLIMITED = (sys.maxint >> 10) - 3"" instead? I tested good."
1695056,2017-06-02 14:28:54 UTC,"It's a limitation of your host, when using hugepages the memory is locked, reserved, you can consider setting this limit in /etc/security/limits.conf"
1695056,2017-06-08 10:31:19 UTC,"Thanks Sahid, so the hard-limit is set to guest memory,
In my previous example, guest memory is 12288, I have two vfio host interfaces I read somewhere they need 1g memory each, so I had to make hard-limit 15000 even 14000 didnt work.
Can we expose hard-limit as a new flavor key?"
1695056,2017-06-08 08:51:42 UTC,https://paste.fedoraproject.org/paste/4EQYNVchSp-gvHKivpqp6l5M1UNdIGYhyRLivL9gydE=
1695056,2017-06-08 08:50:12 UTC,"Wei Zhu, can you test this and let me know the result?"
1695056,2017-06-08 07:28:40 UTC,"I don't think it something we want, even if you have disable KSM it's not a generality. For realtime we want reduce the latency not the memory consumption."
1695056,2017-06-07 14:20:04 UTC,"Hi Sahid,"
1695056,2017-06-07 13:30:54 UTC,"Default hard_limit is unlimited, but VM couldn't start as it needs real numbers, allocating 12G for guest with two vfio NIC, so had to set hard_limit to 15G to make it work,
Since I'm using HEAT to provision the VM, is there method to preset these values?"
1695056,2017-06-06 13:27:52 UTC,"Went over a bug in redhat with similar symptom, seems <memtune><hard_limit> needs to be exposed in order for <locked> to function well in this feature,"
1695056,2017-06-02 16:51:15 UTC,"My main intention for this feature is to secure emulator pin, not the locked memory but it cannot be disabled,"
1695056,2017-06-02 13:27:38 UTC,"root@TS01:~# libvirtd --version
libvirtd (libvirt) 1.3.1
root@TS01:~# kvm --version
QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.14), Copyright (c) 2003-2008 Fabrice Bellard"
1695056,2017-06-02 12:48:15 UTC,Which version of libvirt / qemu do you have installed?
1695056,2017-06-08 12:55:25 UTC,"I made the change per comment #9, VM couldn't start as hard_limit is not enough (comment #11)
  <currentMemory unit='KiB'>12582912</currentMemory>
  <memtune>
    <hard_limit unit='KiB'>12582912</hard_limit>
  </memtune>"
1695056,2017-06-13 15:55:36 UTC,"With HARD_LIMIT_UNLIMITED = (sys.maxint >> 10) -3 , it works with correct memtune and hard_limit"
1695056,2017-06-08 14:09:24 UTC,So nothing is really clear on how to configure this element. Someone says from #virt that we can set it to the host memory size but there is a security concern; QEMU might be compromised or have memory leak and so host itself could crash.
1695056,2017-06-16 08:41:40 UTC,Ok I think we should set it to -1 so libvirt will take care of using the unlimited value by reading the cgroup. I'm going to update the patch and make some tests. Can you do the same in your side ? to ensure that is well working?
1695056,2017-06-15 18:08:31 UTC,"Sahid, seems kmem max is 2**53 - 3 instead of 2**53 -1?"
1695056,2017-09-04 10:43:43 UTC,"Change abandoned by sahid (<email address hidden>) on branch: master
Review: https://review.openstack.org/472633
Reason: Blocked for no real reason"
1695056,2017-07-11 13:16:42 UTC,I don't know it seems to be blocked by a developer preference...
1695056,2017-07-11 12:38:26 UTC,can this be merged into ocata?
1695056,2017-06-27 16:05:16 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1695056,2017-06-27 14:07:45 UTC,"Works great, thank you!"
1695056,2017-06-27 07:08:31 UTC,"The current patch upstream [0] is proposing to hardcode a value which should be considered as unlimited for most of the cases, then libvirt in its version 3.1.0 is going to take care of that automatically."
1695056,2017-06-26 14:36:42 UTC,"HARD_LIMIT_UNLIMITED = -1  didn't work, just wondering any other value to use and get it worked around."
1695056,2017-06-15 20:47:39 UTC,sorry 2**53 - 4 instead.
1695056,2017-06-26 13:10:28 UTC,"Hi Sahid, just trying to follow up, much appreciated."
1695056,2017-06-19 16:12:33 UTC,"Sahid, is it possible to use system physical memory instead?"
1695056,2017-06-16 12:54:27 UTC,"This works good, using maximum system avaiable physical memory"
1695056,2017-06-16 12:08:04 UTC,"when using memtune hard-limit =-1, it removed the memtune portion, later VM crashed"
1695056,2017-06-16 11:48:22 UTC,HARD_LIMIT_UNLIMITED =  -1
1695056,2017-06-16 09:34:50 UTC,Oh actually virsh is taking care of that value when we pass -1 so it's not a bug of libvirt.
1695056,2017-06-16 09:27:58 UTC,Ok so that does not work with -1 which is strange since that is working with virsh.
1695056,2017-06-26 14:21:27 UTC,"Wei, can you elaborate little bit more why you would do that ? at the end it's going to be the same behavior or do I missed something."
1695065,2017-06-01 20:08:07 UTC,"Thank you for reporting this bug.  Your report shows that you had an unattended upgrade that ran and upgraded the version of the nvidia dkms module that you have installed; and that this triggered a request from shim to disable SecureBoot on your system, because dkms modules are incompatible with SecureBoot currently."
1695065,2017-06-02 16:09:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695065,2017-06-03 06:05:35 UTC,I understand this was an issue with how grub2 was booting unsigned kernels which has been resolved with grub2 2.02~beta3-4ubuntu4 in artful.
1695065,2017-06-03 06:17:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695080,2018-03-23 00:20:56 UTC,"The attachment ""glibc BZ#13862 backport to eglib-2.19-0ubuntu6.13"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1695085,2017-08-12 17:02:55 UTC,Could it be that your program is running out of memory due to some memory leak somewhere?
1695089,2017-06-02 00:45:28 UTC,"Well, since a bug has to be filed against a package... I'd guess ""systemd"" though I would say it's somehow related to systemd-network (which doesn't seem to have a package)"
1695089,2017-06-02 00:33:46 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1695089,2017-06-23 13:57:27 UTC,"To further troubleshoot this, it would be interesting to see the output of what udevadm thinks about these interfaces:"
1695089,2017-06-23 13:54:46 UTC,"systemd-networkd is not a separate binary package, and the networkd daemon and units are simply shipped by the systemd binary package."
1695098,2017-06-02 06:07:02 UTC,Seems it used to just check if a TCP connection succeeded but was changed in commit 37034d884bd7b7aca7f94bb5684ce813a51c3be1 to do more than that.
1695098,2017-06-02 07:35:11 UTC,"A simple TCP connect is not sufficient. In many of the places that interact
with Canonical and MAAS installs they actually have overlapping IP address
ranges. MAAS machines are configured with a ""private"" subnet that is
10.X... which is *not* routable from the driving machine, but the machine
is also attached to the Canonical VPN which *also* has a 10.X... subnet
that *is* routable from the driving machine. Imagine the topology:"
1695098,2017-06-02 11:37:59 UTC,"On Fri, Jun 02, 2017 at 07:35:11AM -0000, John A Meinel wrote:

> A simple TCP connect is not sufficient. In many of the places that interact
> with Canonical and MAAS installs they actually have overlapping IP address
> ranges. MAAS machines are configured with a ""private"" subnet that is
> 10.X... which is *not* routable from the driving machine, but the machine
> is also attached to the Canonical VPN which *also* has a 10.X... subnet
> that *is* routable from the driving machine. Imagine the topology:
"
1695098,2017-06-01 23:52:24 UTC,"Possible solutions could be to simplify the reachability check to succeed when an SSH banner is seen, or even to succeed merely if the TCP connection is successfully established."
1695100,2017-06-01 22:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1695102,2017-06-01 22:20:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/470040"
1695102,2018-04-11 06:02:55 UTC,"Reviewed:  https://review.openstack.org/466674
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=6f8e3548050b5126787a413c470ec980b2f4c211
Submitter: Zuul
Branch:    master"
1695102,2018-05-16 15:06:06 UTC,please backport it to queens
1695102,2018-05-16 16:00:09 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/568890"
1695102,2018-05-26 15:50:58 UTC,"Reviewed:  https://review.openstack.org/568890
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=cb30dc6e798d99b4f5c1dacf06ba4cbdb511f61d
Submitter: Zuul
Branch:    stable/queens"
1695102,2018-06-07 20:55:45 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b2 development milestone.
1695102,2018-07-24 03:00:38 UTC,This issue was fixed in the openstack/kolla-ansible 6.1.0 release.
1695102,2017-06-02 15:29:04 UTC,"Change abandoned by Michal Jastrzebski (inc0) (<email address hidden>) on branch: master
Review: https://review.openstack.org/470040"
1695112,2017-06-09 13:02:51 UTC,"Hi,"
1695112,2017-06-09 20:31:02 UTC,"Sure, I just did it myself."
1695112,2017-08-21 16:02:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1695115,2018-05-03 12:37:29 UTC,"Hi Ian,"
1695132,2017-06-02 17:54:41 UTC,"I/O errors are nearly always a failing drive (either HDD or USB stick), but theoretically it could also be that the USB is dropping out mid copy for some reason."
1695132,2017-06-03 00:28:09 UTC,"Thank you Mark. I will. Thanks again for all your hard work on Peppermint.
Kind regards,
Sara Ann"
1695141,2017-06-02 04:30:05 UTC,"% uname -a
Linux subdivisions 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1695141,2017-06-02 23:09:03 UTC,Confirmed that falling back to nvidia-graphics-drivers-375 375.39-0ubuntu5 fixes the problem.
1695141,2017-06-19 14:56:39 UTC,Has there been any updates to this in either the Zesty security channel or Artful?  It's a pretty serious regression.
1695144,2019-03-15 22:54:40 UTC,"Reviewed:  https://review.openstack.org/435667
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=97f2636dc72125897095e91b398da1cc20e9c39e
Submitter: Zuul
Branch:    master"
1695144,2017-11-20 05:58:42 UTC,"Change abandoned by Rabi Mishra (<email address hidden>) on branch: master
Review: https://review.openstack.org/435667
Reason: Now that we've split the plugin out, this has to be proposed to heat-tempest-plugin."
1695144,2017-06-02 05:17:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/470161"
1695144,2017-08-09 02:39:54 UTC,"Reviewed:  https://review.openstack.org/470161
Committed: https://git.openstack.org/cgit/openstack/python-heatclient/commit/?id=485a679f3e87d5e38a72c4da07f5fb3ecd6597c8
Submitter: Jenkins
Branch:    master"
1695152,2018-01-10 16:16:00 UTC,It is indeed unfortunate that the API requires you to know *both* the name and the UUID of the stack before you can fetch details about it directly.
1695152,2018-01-11 03:32:04 UTC,"I think , in the same environment, one direct request should be processed faster than that redirect.
I tests like that:"
1695152,2019-12-03 19:02:27 UTC,"Change abandoned by Zane Bitter (<email address hidden>) on branch: master
Review: https://review.opendev.org/527312"
1695156,2017-07-05 10:19:09 UTC,"For currently, you can try to validate it one by one, and yeah, will be greater if we can have nested check"
1695163,2017-06-02 05:34:33 UTC,"Stacktrace:
 #0  0x0804baa4 in main (argc=<optimized out>, argv=<optimized out>) at seahorse-daemon.c:321
         octx = 0x915c738
         error = 0x0
StacktraceTop: main (argc=<optimized out>, argv=<optimized out>) at seahorse-daemon.c:321"
1695169,2020-11-09 17:51:51 UTC,Patches should be sent to the qemu-devel mailing list for discussion and inclusion. Did you ever send your patch to the list?
1695169,2021-01-09 04:17:47 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1695170,2017-06-05 03:25:06 UTC,"yes, this is about a new job."
1695170,2017-06-04 19:01:05 UTC,"Can you elaborate a bit more the work needed?
Do we need to create the new job in openstack-infra project?"
1695172,2020-12-05 04:17:27 UTC,[Expired for tempest because there has been no activity for 60 days.]
1695172,2017-06-13 15:09:47 UTC,Glance v1 tests will stick around for a while more - see http://lists.openstack.org/pipermail/openstack-dev/2017-March/114141.html.
1695173,2017-07-30 21:39:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695173,2021-01-07 04:03:31 UTC,4.8 EOL
1695175,2017-06-02 17:30:08 UTC,kernel-fixed-upstream
1695175,2017-06-02 17:30:01 UTC,"@jsalisbury,"
1695175,2017-06-02 17:29:45 UTC,kernel-fixed-upstream
1695175,2017-06-02 16:45:43 UTC,"@brad-figg,"
1695175,2017-06-02 15:58:22 UTC,apport information
1695175,2017-06-02 15:57:23 UTC,apport information
1695175,2017-06-02 15:57:06 UTC,apport information
1695175,2017-06-02 15:56:57 UTC,apport information
1695175,2017-06-02 15:56:53 UTC,apport information
1695175,2017-06-02 15:56:48 UTC,apport information
1695175,2017-06-02 15:56:45 UTC,apport information
1695175,2017-06-02 15:56:42 UTC,apport information
1695175,2017-06-02 15:56:40 UTC,apport information
1695175,2017-06-02 15:56:37 UTC,apport information
1695175,2017-06-02 16:49:27 UTC,"@jsalisbury,"
1695175,2017-06-02 15:56:28 UTC,apport information
1695175,2017-06-02 06:33:16 UTC,"When putting the command
`sudo lspci -vnvn > lspci-vnvn.log`
It gives another error"
1695175,2017-06-02 12:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1695175,2017-06-02 12:00:08 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1695175,2017-06-02 15:55:53 UTC,apport information
1695175,2017-06-02 15:56:05 UTC,apport information
1695175,2017-06-02 15:55:57 UTC,apport information
1695175,2017-06-02 15:56:11 UTC,apport information
1695175,2017-06-02 15:56:15 UTC,apport information
1695175,2017-06-02 15:56:21 UTC,apport information
1695175,2017-06-02 15:56:26 UTC,apport information
1695175,2017-06-02 15:56:08 UTC,apport information
1695175,2017-06-02 15:56:33 UTC,apport information
1695187,2017-06-27 16:03:57 UTC,"Automatically discovered version kilo in description. If this is incorrect, please update the description to include 'nova version: ...'"
1695187,2019-10-07 10:20:02 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/470181
Reason: This has been in merge conflict for sometime so I'm going to abandon it to keep things clean. Please reopen if you think it's still valid :)"
1695187,2019-12-12 21:20:25 UTC,This is really old and needs to be re-triaged/re-reported if it's still a valid issue on master.
1695187,2017-06-02 07:40:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/470181"
1695216,2017-06-22 07:59:47 UTC,Accepted by upstream
1695216,2017-06-22 08:58:29 UTC,"Here is discussing thread
https://www.spinics.net/lists/linux-usb/msg157789.html"
1695216,2017-07-10 08:21:27 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1695216,2017-07-11 03:47:19 UTC,"I verified linux-image-4.4.0-85-generic #108 on Kona-SFF-DVT-C1 with BIOS 0.6.0.
The front USB is disabled when we disabled the front USB in BIOS settings."
1695216,2017-07-24 07:59:49 UTC,This bug was fixed in the package linux - 4.4.0-87.110
1695216,2017-06-02 08:46:51 UTC,"ASMedia provide a patch for this and has submitted to upstream.
Currently, no reply from the maintainer, but we need this fix as soon as possible, so we submit the SRU patch before this patch is accepted by upstream."
1695226,2019-01-19 11:55:06 UTC,it's the RAM and CPU of the VM .. I have this problem installing ceilometer and ironic on my VM ...
1695226,2017-06-07 12:29:23 UTC,can any one look into the bug ?
1695226,2017-08-28 12:50:57 UTC,"Sorry to take so long to get to this.  I looked through the logs you posted, and this doesn't seem to be a glance-specific problem.  It looks like the error is occurring during you packstack installation itself, not with specific components.  Could you provide more information about the particular problem you are seeing with glance?"
1695228,2017-06-08 07:41:56 UTC,"In case this is related, I use the following dual monitor setup:"
1695228,2017-06-08 09:07:51 UTC,"Well, after playing with hidpi setting, it appears that ALL bugs (empty menu, badly positionned tooltips) are only when windows scalling is set to 2!"
1695241,2017-11-20 20:46:53 UTC,I was able to duplicate this. I agree with the triaging given in the description.
1695241,2020-05-20 19:42:13 UTC,https://github.com/snapcore/snapcraft/pull/3134
1695244,2017-09-08 23:27:36 UTC,Looks like we need some logic to not print the _tabulated_channel_map_tree if the map is empty.
1695251,2017-06-02 14:00:36 UTC,"maybe won't fix, as it can be assembled easily enough with git describe --dirty --always"
1695253,2017-06-09 13:00:51 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1695258,2017-06-02 12:16:42 UTC,Attaching Heat templates being used during testing.
1695258,2017-06-02 12:17:38 UTC,Attaching another part of the heat template.
1695258,2017-06-09 11:59:26 UTC,"With the attach aodh_workaround.conf, this error is gone."
1695258,2020-09-18 13:48:55 UTC,I believe that is fixed upstream nowadays
1695262,2019-08-23 09:43:34 UTC,"@jani, were you able to resolve this issue?"
1695262,2017-06-02 17:12:55 UTC,"Recently, swift3 started requiring a more-recent version of swift to be installed[1]. This allows the project to move forward (eventually) on various bugs[2][3], primarily related to multipart upload support, as well as new features such as bucket versioning support. I'd recommend upgrading to a more-recent version of swift (a lot of great stuff has landed since 2.10.1!) or, if staying on the Newton release is a requirement, installing an older version of swift3. The last release (1.11) can run with swift as old as 2.1.0; the last commit off of master that supported your version of swift was fc66da8."
1695262,2017-06-03 07:27:45 UTC,Thanks so much for the update.
1695262,2017-06-05 05:13:00 UTC,We installed latest Oepnstack Ocata version and installed swift3 from master branch after which its working fine.
1695262,2017-06-05 05:50:23 UTC,Could you share your proxy server config (in particular pipeline and swift3/authtoken/keystoneauth sections)?
1695262,2017-06-05 06:08:49 UTC,"I have attached the available proxy config file, keystone and swift logs."
1695262,2017-09-27 20:47:55 UTC,"The pipeline in your proxy config is wrong, line 94 is like this:"
1695262,2017-09-27 20:48:47 UTC,"Also, it might be a good idea to join #openstack-swift on freenode to get some quick help, it might go faster then through the bug."
1695268,2017-06-03 13:44:43 UTC,Note:
1695268,2017-06-02 13:36:29 UTC,Log without any bibles in data folder
1695268,2017-06-03 22:22:48 UTC,The value comes from line 250 of the diff at https://code.launchpad.net/~phill-ridout/openlp/saved_bible_verses/+merge/324674
1695268,2017-06-02 13:29:18 UTC,Bibles data folder.
1695278,2017-09-05 04:33:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695279,2018-06-29 08:41:48 UTC,VPNaaS is intentionally not supported on any Xenial release within the OpenStack Charms.
1695279,2017-06-02 16:55:55 UTC,"If so, is there the possibility to run VPNaaS in Netwon/Xenial environments? Any workaround?"
1695279,2017-06-02 14:43:53 UTC,"So, VPNaaS is not supported in Xenial deployments?"
1695279,2017-06-02 14:27:50 UTC,VPNaaS was supported back on trusty deployments; it should not be enabled in Xenial deployments.
1695281,2018-03-15 18:53:19 UTC,"Thanks. This may be related to the OpenBLAS library, see for example upstream bug report https://savannah.gnu.org/bugs/?47400."
1695281,2018-03-15 17:26:07 UTC,"If you want to use Octave in terminal mode, you might consider using ""octave-cli"" instead of ""octave --no-gui"", they are slightly different. Does using octave-cli resolve this bug for you?"
1695281,2018-03-15 18:08:15 UTC,1. The bug still persists in octave 4.2.1 (started with --no-gui)
1695281,2018-04-28 09:10:16 UTC,"I'm sorry for the delay, I didn't notice your reply. Both recommended steps fix the bug."
1695281,2020-06-01 19:21:12 UTC,"As far as I can tell this bug has been resolved for the original reporter, no new activity has been made and this bug should have expired a couple years ago.  If this is still an issue feel free to reopen or report a new bug."
1695288,2017-06-30 09:15:57 UTC,"Hi Joffrey,"
1695288,2018-01-18 08:15:11 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1190
1695298,2017-06-04 22:22:44 UTC,"Hi, there is a change is the music service provider API and i cant get the music url anymore but some songs and artists are still working fine specially covers and free drm songs... i am still trying to get the music url for all songs."
1695315,2017-07-03 19:15:43 UTC,Hi. I don't see it in the Open Store. Has it a new name? I love your app. Thank you :)
1695315,2017-06-08 08:21:32 UTC,"Hi,"
1695397,2017-06-05 15:17:45 UTC,"There are 2 kernels in the grub: 4.4.0-78, and 3.13.0-86.  I have booted into both of these repeatedly.  The latter kernel works without any issues.  The former always has the issues as described above and in bug report # 1695400."
1695397,2017-06-02 18:30:14 UTC,This change was made by a bot.
1695397,2017-06-02 18:39:47 UTC,"Bug # 1695400 is on same computer (""Keyboard and mouse freeze up in Ubuntu 16.04 with 4.4.0-7 kernel"")."
1695397,2017-06-05 11:23:59 UTC,Can you boot back into the prior kernel and see if the bug goes away?
1695400,2017-06-02 19:35:31 UTC,apport information
1695400,2017-06-02 18:37:08 UTC,"Bug # 1695397 ""Cannot apt-get update by internet cable with Ubuntu 16.04 with 4.4.o-78 kernel"" is on same computer and has apport report"
1695400,2017-06-05 17:29:20 UTC,"Issues started after upgrading to 16.04.  The previous kernel that was in use was 3.13.0-86, which had no operating issues.
I have installed 4.12.0-0412004rc4-generic which is now in use.  I cannot access the internet with cable, but can with wireless.  The keyboard and mouse have not locked up as they did with 4.4.0-78, altho they do not operate smoothly.  In terminal (and wireless), sudo apt-get update yields ""Temporary failure resolving..."".  Pinging ubuntu.com and 8.8.8.8 results in ""unknown host"" and destination host unreachable"", respectively."
1695400,2017-06-05 11:23:17 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1695400,2017-06-02 18:30:32 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1695400,2017-06-02 19:35:34 UTC,apport information
1695400,2017-06-02 19:35:27 UTC,apport information
1695400,2017-06-02 19:35:25 UTC,apport information
1695400,2017-06-02 19:35:19 UTC,apport information
1695400,2017-06-02 19:35:22 UTC,apport information
1695400,2017-06-02 19:35:14 UTC,apport information
1695400,2017-06-02 19:35:12 UTC,apport information
1695400,2017-06-02 19:35:10 UTC,apport information
1695400,2017-06-02 19:35:08 UTC,apport information
1695400,2017-06-02 19:35:04 UTC,apport information
1695400,2017-06-02 19:35:02 UTC,apport information
1695400,2017-06-02 19:35:17 UTC,apport information
1695403,2017-06-21 13:52:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695466,2020-03-08 19:50:59 UTC,"Also, when I want to install moodle on Xubuntu 18.04 apt wants to install apache2 too, but I want to use nginx instead with moodle and not with apache."
1695526,2018-01-25 08:48:30 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3708
1695526,2017-06-06 01:57:17 UTC,"I think it is not honored for any blocking condition. See my comment with the test while trying to do load data infile from a broken fifo on this report, for example: https://bugs.mysql.com/bug.php?id=75161"
1695541,2017-09-18 18:37:02 UTC,A change to the user_data is only one of many reasons that a server resource may be replaced.
1695541,2017-09-01 15:52:03 UTC,"Adding `user_data_update_policy: IGNORE` to servers will avoid replacement, though it's not what people may generally want."
1695550,2017-06-02 22:28:37 UTC,"(octaviaclient) michjohn@devstackpy27:~/.../testclient/python-octaviaclient$ openstack loadbalancer pool set --session-persistence type=""SOURCE_IP"",cookie_name=""chocochip"" pool1"
1695564,2017-12-06 13:01:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695568,2017-06-03 02:39:21 UTC,This configuration issue is directly related to issue #18 in the atom github tracker:
1695583,2017-06-09 13:00:09 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1695583,2017-09-20 16:47:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695587,2017-06-03 16:20:35 UTC,"Well, there already are the two separated searches for ""Title"" and for ""Lyrics"". And as most titles should be included in the lyrics as well I don't see a valid point for ""Title or Lyrics"" to exist."
1695587,2017-06-03 17:16:29 UTC,"""Entire Song"" searches most attributes on the song, not just the title and the lyrics. I can't remember exactly which attributes, I'd have to go back and look at the code."
1695587,2017-06-04 14:10:58 UTC,"The actual code to search in ""Entire Song"" does only do a indirect database call over the plugin manager to search for a match in either of song.search_title, song.search_lyrics and song.comments. That's not searching in all possible attributes but only in three (admittedly the main ones)."
1695587,2017-06-03 13:27:20 UTC,"Not sure about this, but it's possible that ""entire song"" only
searches for titles and lyrics."
1695597,2017-07-22 12:44:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695597,2017-07-22 13:27:09 UTC,Ubuntu 16.04.2
1695601,2019-05-28 19:01:27 UTC,Thanks for keeping the bug updated
1695601,2017-06-04 12:56:00 UTC,"I just got confirmation from Beniamino Galvani that this is consistent with his change. Also, the patch is part of the  1.4 branch and should be in the next release: https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=nm-1-4"
1695601,2017-08-14 21:36:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695601,2019-05-28 10:00:58 UTC,"Newer versions of NetworkManager, after upgrading from 17.04, have been bundling the proper fix."
1695610,2017-10-27 07:33:37 UTC,"Thanks for the FYI Mark,
so this will be picke dup on the merge of 2.1.25 then."
1695611,2017-06-03 13:00:49 UTC,"The attached file is the key dump with gdb debug application.
The bug was fixed after rebuilding the libjson-c with source"
1695611,2019-08-08 11:08:25 UTC,I hope it is ok now
1695611,2019-08-08 11:08:33 UTC,Please reopen if you still have this issue!
1695625,2018-05-01 15:04:20 UTC,"bionic has no report, closing"
1695627,2018-05-01 15:03:56 UTC,"bionic has no reported of the issue, closing"
1695641,2017-06-03 16:40:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695649,2017-12-06 18:45:53 UTC,Commited in master in: 1c8ce1ee6081b4d2f5a111d4c960cedca77634dc
1695649,2017-12-05 21:35:35 UTC,merge request fot the bug: https://gitlab.com/inkscape/inkscape/merge_requests/153
1695651,2017-06-28 12:50:33 UTC,"Thanks, Sebastien Bacher. I found a similar thread from the upstream: https://bugzilla.gnome.org/show_bug.cgi?id=779897 (bug number 779897)"
1695651,2017-06-26 10:51:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1695651,2017-07-10 20:43:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695651,2017-08-19 08:40:02 UTC,"I have the same problem, but for me i think it is the locale with Swedish åäö characters that does not seem to work"
1695666,2017-06-07 18:08:25 UTC,"From the POV of ""u-r-u shouldn't be a dumping ground for quirking upgrade issues we can fix in packages"", shouldn't this check be in preinsts for the packages that twiddle /boot/efi, not in the upgrader?"
1695666,2018-01-26 23:27:57 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.6
1695666,2018-01-12 13:55:05 UTC,"Patch, needs review (especially of the new strings), and some testing - I only checked the function externally."
1695666,2018-01-13 01:52:56 UTC,For completeness we should also check that the filesystem mounted at /boot/efi is of type vfat.
1695666,2018-01-16 16:13:09 UTC,"Checking for vfat seems fragile. You could, like systemd does upstream, also mount it as an autofs with a short timeout."
1695666,2018-01-26 23:51:07 UTC,The changelog entry is the wrong one but it's fixed. String improvements are queued in bzr but some tests fail and need fixing :(
1695666,2017-06-07 18:41:53 UTC,"On Wed, Jun 07, 2017 at 06:08:25PM -0000, Adam Conrad wrote:

> >From the POV of ""u-r-u shouldn't be a dumping ground for quirking
> upgrade issues we can fix in packages"", shouldn't this check be in
> preinsts for the packages that twiddle /boot/efi, not in the upgrader?
"
1695675,2018-01-20 08:08:17 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1445
1695676,2017-06-05 12:20:05 UTC,"- confirmed on Windows 10, Inkscape 0.92+devel 15730
- also reproduced on Windows 10, Inkscape 0.92.1 r15371 using px as the document unit, file attached"
1695676,2017-06-05 12:50:04 UTC,curious side comment: on Inkscape 0.47pre1 the defect does not show up. Attached is a screenshot of the file polkadot_92.1_px.svg when viewed in Inkscape 0.47pre1. I see no evidence of a defect at the 100px boundary
1695676,2017-06-05 13:42:47 UTC,"it is possible that the problem is related to the switch from 90 to 96 dpi. When I view the file polkadot_92.1_px.svg in Inkscape 0.92.1 the size of the pattern is 100px as measured using the control points that are associated with the rectangle tool. When I view the same file in Inkscape 0.47pre1 the size of the pattern is 94 px, which is the same amount of change as the change from 90dpi to 96dpi."
1695679,2020-08-15 18:19:44 UTC,"Closing because issue is not reproducible (tested on 1.0 and 0.91.1 on Windows 10, master on Ubuntu 20.04)"
1695679,2017-06-05 12:01:31 UTC,"Replicated with Inkscape 0.92.1 r15371, Win 8.1/64  (""fatal exception"")."
1695686,2017-10-26 07:07:48 UTC,"Hi!
I too faced the same issue. I found that 'kvm-ipxe' is not available on Ubuntu16.04 (https://packages.ubuntu.com/xenial/). I then used 'ipxe-qemu' instead (https://packages.ubuntu.com/trusty/kvm-ipxe). With that, my setup progressed."
1695695,2017-06-09 07:20:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695698,2017-06-12 21:47:08 UTC,"Thanks for the feedback! :) Probably the system needs an icon in a specific resolution.
I'll take a look.
Best regards Robert and thanks!"
1695698,2017-06-13 04:52:07 UTC,You're welcome. :-)
1695698,2017-06-13 20:51:31 UTC,"Hi, I was looking into it and I didn't find a fix.
As ANoise hasn't window (it's only integrated in the sound menu) maybe I can't set an icon.
I asked in the mail list of the sound menu settings (message waiting moderation):
https://lists.freedesktop.org/archives/pulseaudio-bugs/2017-June/subject.html
Best regards."
1695698,2017-06-14 04:57:27 UTC,Thanks!
1695698,2018-07-30 14:30:47 UTC,Resolved this by adding:
1695698,2018-11-11 15:22:01 UTC,"Affects me too in GNOME 3.28.2-0ubuntu1, for Ubuntu 18.04.1 LTS. The sound indicator is different from the one shown on the website. Looks it was stuck stuck with Unity"
1695700,2018-05-02 14:52:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695704,2017-06-05 14:36:49 UTC,"I think I only have a single regiond server. How could it be 25%
connected in this case? There are 4 rack controllers in my MAAS, but
only one region-and-rack controller."
1695704,2017-06-05 15:01:22 UTC,Each regiond server runs 4 seperate regiond processes. Each rack controller connects to each process in the regiond server. Based on the degraded state your rackd is only connected to 1 or the 4 processes when it should be connected to all 4.
1695704,2017-06-05 13:45:22 UTC,"What that is actually say is that rackd itself is only 25% connected. All other services that the rackd manages is working fine, and rackd itself is working its just in a degraded state as its missing a couple of connections to the regiond. The rackd should automatically fix this issue and reconnect to the other regiond processes, and it should not cause any issues with operation."
1695704,2017-06-06 07:56:41 UTC,"Interesting. I believe the flag disappeared after a reboot, not sure
whether it was the region or the rack controller that rebooted."
1695706,2017-09-08 09:45:29 UTC,"Werd's versuchen, muss aber warten, bis das Problem wieder auftritt. Derzeit funktioniert es."
1695706,2017-09-04 22:00:29 UTC,"Kannst du bitte mal testen, ob das Problem mit der Version von  https://launchpad.net/~diesch/+archive/ubuntu/experimental noch auftritt? Danke :-)"
1695729,2017-06-05 15:28:53 UTC,"Confirmed. In fact any subsequent navigation in the new tab does not affect the breadcrumbs, so presumably a signal has not been connected."
1695729,2017-06-05 15:29:55 UTC,"As this does not seem to be a critical bug, fixing will be deferred until migration to GitHub."
1695731,2017-06-04 12:53:00 UTC,Also reported here - https://github.com/linuxmint/mintsources/issues/97 - not sure which is the right place.
1695736,2017-06-05 22:57:50 UTC,"Adam,"
1695736,2017-06-05 23:44:39 UTC,"- I tried rebooting and running cr_checkpoint again, and I got the same error."
1695736,2017-06-06 00:22:48 UTC,"Adam,"
1695736,2017-06-06 01:08:51 UTC,There is no such package in 17.04 (Zesty).  Apparently it last existed in 14.04 (Trusty):
1695736,2017-06-06 01:40:54 UTC,"Adam,"
1695736,2017-06-06 23:36:10 UTC,"Zesty has version 4.10.0 of the Linux kernel and yes, it appears that BLCR supports only up to 3.7.1, as mentioned at"
1695739,2017-06-04 20:06:26 UTC,"Hi Nithin,
Thanks for your feedback!
I'll take a look.
Note for me: I think I could add this parameter search for this:
&exclude_place_ids=15661882
Best regards!"
1695739,2017-06-04 13:59:45 UTC,After clicking on more results.
1695742,2017-06-09 13:45:09 UTC,"Update: the Unity session as well as the sessions from the packages ubuntu-mate-desktop and cinnamon-desktop correctly handle all Fn keys.
I'm stuck with Cinnamon for now."
1695744,2017-06-04 14:45:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/470754"
1695744,2020-03-18 08:58:21 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/470754
Reason: This is a pretty old patch with negative review. Feel free to restore it (or ask gibi on irc to restore it) if you still working on it."
1695745,2020-06-25 09:42:58 UTC,"Cada vez que se instala un nuevo programa o actualización, informa que la instalación (o desinstalación) no se completó.
Los programas se instalan y funcionan correctamente.
Con el único que hay problemas es con Spotify"
1695745,2018-02-20 08:34:06 UTC,.
1695745,2019-08-02 22:24:44 UTC,-
1695745,2019-08-21 09:09:05 UTC,.
1695745,2019-09-20 14:22:00 UTC,"No entiendo.
Siempre se produce el mismo error y nunca se soluciona?"
1695745,2020-06-25 09:44:03 UTC,"Cada vez que se instala un nuevo programa o actualización, informa que la instalación (o desinstalación) no se completó.
Los programas se instalan y funcionan correctamente.
Con el único que hay problemas es con Spotify"
1695745,2020-07-05 11:07:34 UTC,"Cada vez que se instala un nuevo programa o actualización, informa que la instalación (o desinstalación) no se completó.
Los programas se instalan y funcionan correctamente.
Con el único que hay problemas es con Spotify"
1695745,2020-08-06 10:37:08 UTC,"?
no entiendo pero el problema nunca se soluciona!!!"
1695745,2020-12-18 12:32:58 UTC,.
1695763,2017-06-04 18:21:27 UTC,"Naively installing the yakkety package does not work.
5.22.1-9 It would help if the perl depencency would just be a little lower.
And there is a problem with install-docs when trying that on xenial."
1695763,2017-06-04 18:41:08 UTC,"Alternatively, change the following code:"
1695767,2017-06-04 19:17:02 UTC,It has something to do with bug 878239.
1695767,2017-06-04 19:12:59 UTC,I'm assigning this to me...Any advice and comments are welcome!
1695767,2017-06-05 14:33:51 UTC,I'm done with that patch.
1695767,2017-06-08 00:23:26 UTC,Committed to lp:ecryptfs as r888. Thanks for the fix!
1695776,2018-11-14 07:21:14 UTC,Ubuntu 18.04 this bug is existing.
1695776,2020-08-12 20:00:02 UTC,This was already fixed in v1.7
1695776,2017-07-08 13:58:56 UTC,"Reproduced on Ubuntu 16.04 with Pinta 1.6. Does not reproduce with latest 1.7 daily build, so it can probably be marked as fixed"
1695784,2018-05-21 16:59:35 UTC,"Seems more like a bug in pycompile, as that is responsible to byte-compile the py files."
1695793,2020-04-28 23:01:26 UTC," I experience the same issue as OP on Ubuntu 18.04: WM_WINDOW_ROLE is respected, while WM_CLASS set via `--classname` is ignored."
1695793,2017-06-06 09:11:10 UTC,See https://developer.gnome.org/gtk3/stable/GtkWindow.html#gtk-window-set-wmclass
1695793,2017-06-06 09:35:05 UTC,"Hm, thats somewhat dumb. That destroys the use of the StartUpWmClass attribute in FreeDesktop files."
1695793,2020-01-18 19:24:48 UTC,"I ran into the same issue.  While not a fix, I found that if I can work around this with a symlink."
1695796,2017-06-08 04:43:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472060"
1695796,2017-06-08 09:13:29 UTC,"Change abandoned by lihaijing (<email address hidden>) on branch: master
Review: https://review.openstack.org/472060
Reason: duplicate https://review.openstack.org/#/c/471223/"
1695796,2018-01-12 19:04:36 UTC,Unassigning due to no activity for > 6 months.
1695802,2017-07-10 11:43:13 UTC,I think using http://sheep6:8000/admin/?start=2017-07-04&end=2017-07-05 is a valid use case.
1695802,2017-06-07 10:31:41 UTC,"I tried reproducing the same but I am getting pop-up warning as ""Error: Invalid date format: Using today as default."" when I try to feed invalid date through URL. But what I observe is today's date cannot be seen as said in the error message.
So either error message must be corrected or today's date should get loaded in the date field where invalid date is present. What do you think is the correct way to go about this."
1695802,2017-06-07 10:58:12 UTC,I think we should add a validation before the request sent. It means that we do not need to sent a request to the backend when an invalid date is inputed.
1695802,2017-06-26 08:48:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477453"
1695802,2017-07-10 11:36:29 UTC,"I am not sure what you mean by 'backend'.
horizon on a web server validates the request and shows the message in #1."
1695802,2017-07-10 11:44:18 UTC,I change the status back to In Progress as it can be improved a bit and a patch is proposed.
1695802,2018-05-02 12:39:42 UTC,"Change abandoned by Akihiro Motoki (<email address hidden>) on branch: master
Review: https://review.openstack.org/477453
Reason: Abandoned due to long inactivity. Feel free to restore it if you would like to continue the work."
1695807,2017-12-13 12:37:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695808,2017-06-08 16:18:43 UTC,"Note, I'm happy to update a fix for this for a (and a -proposed one
for xenial)."
1695808,2019-05-31 12:37:53 UTC,"This was fixed in upstream 2.3.2 which was fixed in cosmic. As of https://usn.ubuntu.com/4001-1/ pulling back 2.4.1, this is now fixed everywhere."
1695812,2017-06-05 14:52:02 UTC,Are you using the 32bit version of Peppermint 8 on a UEFI system ? .. UEFI is only supported in the 64bit version.
1695812,2017-06-05 15:19:55 UTC,"I'm trying to install 64 bit version of Peppermint 8, I have it installed on another laptop without any problems, but it's an older laptop with 32 bit.  Thanks for the reply.  Really loving Peppermint 8 on my other computer.."
1695812,2017-06-05 15:21:18 UTC,"I'm trying to install 64 bit version of Peppermint 8, I have it installed on another laptop without any problems, but it's an older laptop with 32 bit.  Thanks for the reply.  Really loving Peppermint 8 on my other computer.."
1695812,2017-06-05 15:49:16 UTC,"It would really help if you could raise this on the forum, so we can get the spec of the PC and things like the partitioning scheme."
1695821,2017-06-05 08:52:21 UTC,"This has been fixed by patch https://review.openstack.org/#/c/456800/ but the published docs do not appear to be using the latest source. My understanding is that the published docs are taken from a point soon after the Ocata release, and the publsihed docs are not updated until the next release (Pike)."
1695847,2017-06-05 08:21:06 UTC,(This was in Linux Mint 18.1).
1695861,2018-01-03 14:37:48 UTC,This issue was fixed in the openstack/nova 15.1.0 release.
1695861,2017-08-08 09:40:36 UTC,Sorry for messing up. I'm working here; https://review.openstack.org/#/c/490722/2
1695861,2017-11-15 01:10:41 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1695861,2017-10-24 15:31:30 UTC,"Reviewed:  https://review.openstack.org/509656
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a33634e5558b20e4bd496fe476f6ceb1a2ba79f6
Submitter: Zuul
Branch:    stable/pike"
1695861,2017-10-24 12:42:20 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1695861,2017-10-04 22:12:05 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/509659"
1695861,2017-10-04 22:07:17 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/509656"
1695861,2017-10-04 18:54:31 UTC,"Reviewed:  https://review.openstack.org/490722
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=38b25397e805dcf7a995666049713304fe4f1af1
Submitter: Jenkins
Branch:    master"
1695861,2017-08-28 13:54:51 UTC,"Change abandoned by Viktor Varga (<email address hidden>) on branch: master
Review: https://review.openstack.org/490776
Reason: There is already a fix in progress for this bug."
1695861,2017-12-13 19:28:14 UTC,"Reviewed:  https://review.openstack.org/509659
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c53df19bd4535c5a95cd1aa7e50f49e128f83b95
Submitter: Zuul
Branch:    stable/ocata"
1695861,2017-08-07 07:56:57 UTC,"Change abandoned by Tetsuro Nakamura (<email address hidden>) on branch: master
Review: https://review.openstack.org/491340
Reason: This bug should be fixed in the patch of Change-Id: I9b0d8e8d4b3ab2cb3d578c22fa259e0e7c0d325b"
1695861,2017-08-07 04:41:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491340"
1695861,2017-08-07 00:47:30 UTC,"Hi Viktor Varga,
No problem, thank you for telling me that I can reassign it again."
1695861,2017-08-07 00:43:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491282"
1695861,2017-08-04 07:46:08 UTC,"Sorry, Tetsuro Nakamura, I have not noticed you have already proposed a fix to this patch. Please reassign it to yourself."
1695861,2017-08-04 03:07:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490722"
1695861,2017-07-31 07:41:58 UTC,maybe A ? remove a functionaility looks bad than document the restriction
1695861,2017-06-07 08:12:42 UTC,"Which is better solution, option A or B?"
1695861,2017-06-06 08:27:35 UTC,I can reproduce it in nova master (commit 3ce0a050e1e611ad87336406c189522ee63ded30).
1695861,2017-08-07 07:58:01 UTC,"Change abandoned by Tetsuro Nakamura (<email address hidden>) on branch: master
Review: https://review.openstack.org/491282
Reason: This bug should be fixed in the patch of Change-Id: I9b0d8e8d4b3ab2cb3d578c22fa259e0e7c0d325b"
1695861,2017-08-04 07:31:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490776"
1695868,2017-06-05 11:54:45 UTC,"Hi Maria,"
1695868,2017-06-05 12:23:19 UTC,@Andres
1695868,2017-06-28 15:35:07 UTC,"I hit the same/a similar error - I tried to create a bond using an interface that already had a vlan device attached to it.  No error was shown in the UI, but there was an exception raised in regiond.log."
1695872,2017-06-06 03:56:54 UTC,"I receive the following warning:
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions."
1695872,2020-11-17 05:26:43 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life in April 2019."
1695872,2017-08-08 07:09:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695872,2017-06-06 03:27:35 UTC,"OK, could you please:"
1695872,2017-06-06 01:55:42 UTC,"That might be true, but NVIDIA isn't mentioned anywhere in this bug."
1695872,2017-06-05 12:53:23 UTC,I don't think the open source NVIDIA graphics drivers support GNOME on Wayland in Ubuntu 16.04 LTS.
1695872,2017-06-06 03:15:04 UTC,"I have an nvidia/intel hybrid GPU (GTX-850M), with nvidia proprietary drivers (nvidia-375) from the supported drivers PPA. The attempt failed when using the intel GPU, so the nvidia part is not involved. Using GDM I could load a fully functional Wayland session."
1695873,2017-06-06 18:04:38 UTC,"Translation updated in lp:inkscape rev. 15734.
Thanks!"
1695876,2017-08-30 13:02:58 UTC,Unsubscribing ~ubuntu-sponsors as there isn't an updated patch yet.
1695876,2017-07-10 16:47:15 UTC,# Sponsor review :
1695876,2017-07-10 16:43:47 UTC,# Sponsor review :
1695876,2017-07-10 16:21:36 UTC,"The attachment ""lp1695876_xenial.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1695876,2017-07-10 16:51:14 UTC,4) - Don't forget to file the SRU justification tmpl.
1695876,2017-06-07 12:47:05 UTC,Upstream commit url :
1695876,2017-06-07 12:29:27 UTC,"From previous experience in the same situation, *normally*, a typo like this are worth SRU'ing to stable release when it is bundled with other fixes (non-typo related)."
1695876,2017-06-06 13:59:30 UTC,* Upstream project :
1695876,2017-06-06 00:16:16 UTC,Reported upstream as
1695876,2017-06-14 14:35:50 UTC,Patch with the fix.
1695882,2017-07-10 15:30:04 UTC,This affects the MAAS snap as well since we transitioned to git and use the new version-script.
1695882,2017-07-13 11:41:14 UTC,"This is just the filename being different, the version inside the snap (once installed or pushed to the store) is correct."
1695882,2018-09-02 03:44:00 UTC,Seemingly relevant source: https://github.com/snapcore/snapcraft/blob/a0dac5a926fcbe534098b2d9926f97f34d648f77/snapcraft/internal/lxd/_containerbuild.py#L69
1695899,2017-07-26 01:05:45 UTC,leaving scrypt task open and assigning to James based on Tyler's feedback
1695899,2018-06-07 16:49:26 UTC,"James,"
1695899,2020-09-30 23:23:25 UTC,This bug was fixed in the package python-scrypt - 0.8.0-0.3ubuntu2
1695899,2017-07-26 01:05:13 UTC,"Override component to main
python-bcrypt 3.1.3-0ubuntu1 in artful amd64: universe/python/extra/100% -> main
python-bcrypt 3.1.3-0ubuntu1 in artful arm64: universe/python/extra/100% -> main
python-bcrypt 3.1.3-0ubuntu1 in artful armhf: universe/python/extra/100% -> main
python-bcrypt 3.1.3-0ubuntu1 in artful i386: universe/python/extra/100% -> main
python-bcrypt 3.1.3-0ubuntu1 in artful ppc64el: universe/python/extra/100% -> main
python-bcrypt 3.1.3-0ubuntu1 in artful s390x: universe/python/extra/100% -> main
python-scrypt 0.8.0-0ubuntu1 in artful amd64: universe/python/optional/100% -> main
python-scrypt 0.8.0-0ubuntu1 in artful arm64: universe/python/optional/100% -> main
python-scrypt 0.8.0-0ubuntu1 in artful armhf: universe/python/optional/100% -> main
python-scrypt 0.8.0-0ubuntu1 in artful i386: universe/python/optional/100% -> main
python-scrypt 0.8.0-0ubuntu1 in artful ppc64el: universe/python/optional/100% -> main
python-scrypt 0.8.0-0ubuntu1 in artful s390x: universe/python/optional/100% -> main
12 publications overridden."
1695899,2017-06-28 18:18:10 UTC,"I was hoping that I could quickly ack, from a security review standpoint, python-bcrypt since I already acked it in bug 1427861. However, the project has significantly changed since that review. The bcrypt backend has changed from Openwall's implementation to OpenBSD's implementation. Test vectors have also changed. I don't think this package will require a really close look but it is going to require a closer look than what I had anticipated."
1695899,2017-07-25 23:11:13 UTC,"Hello! This is a very accelerated security review of python-scrypt. I
didn't look at the scrypt implementation itself but did have a quick
look at a few important areas of the project."
1695899,2017-07-13 00:21:57 UTC,"Since Tyler mentioned it requires a review anyway, assigning to the Security Team."
1695899,2017-06-16 10:00:06 UTC,python-bcrypt has main history under MIR bug 1427861
1695899,2017-07-26 00:15:03 UTC,"Hello! This is a very accelerated security review of python-bcrypt. I
didn't look at the bcrypt implementation itself but did verify that the
test vectors used have overlap with Openwall's crypt_blowfish test
vectors:"
1695908,2017-06-10 13:14:06 UTC,"After several attempts to install Ubuntu from the same USB stick, I succeeded doing so:
- downloading kubuntu-16.04.2-desktop-amd64.iso and burning a DVD-RW
- keeping the DVD in the player
- Stopping Windows but with the choice ""Reboot"" and pressing the Shift key all along the closing process
- When a blue start screen ""Choose an option"" pops-up, choosing ""Open a peripherical device"" then choosing ""UEFI : DVD""
- installing Kubuntu with the standard process
- rebooting and discovering the GRUB menu with a choice between Ubuntu and Windows Boot Record"
1695908,2017-06-05 14:22:09 UTC,Install from an USB stick (32 Go) with a persistent live Ubuntu 16.04.2 LTS
1695911,2017-06-12 01:05:10 UTC,"This isn't the first time we've run into this sort of issue.  For another example, see: mfr.  We truncate there (transparently, through a view and query rewriting), FWIW."
1695911,2017-06-12 13:39:18 UTC,"> Truncation seems reasonable, and, IMO, favoring truncation of the value
> column is probably preferable up to some minimum length.  For instance,
> perhaps we truncate the sort_value column to no shorter than 2000, and
> give the balance of the ~2700 bytes to the value column.  That allows
> the non-filing part of the value column to continue acting as a tie
> breaker, which is how things work today.
"
1695911,2017-07-17 15:44:17 UTC,My first attempt to create a unique index over our data with truncated values was:
1695911,2018-09-13 15:27:38 UTC,"More testing, correction to my previous comment.  In practice, truncating  *_idx variant hasn't been necessary, only the *_key variant, which makes sense since the *_idx variant contains about half as much data. So more along the lines of:"
1695911,2018-09-13 17:54:14 UTC,"Bill, have you confirmed that the truncated index is still used without having to adjust the WHERE clause?  In the olden days, I believe that was not true (and part of the reason for the query rewriting stuff we do for mfr, IIRC)."
1695911,2018-09-13 18:42:02 UTC,"I may be oversimplifying the issue, but my understanding of the browse_entry_sort_value_value_key index is that it acts purely as a unique constraint.  The MD5 variant seems to handle that OK."
1695911,2018-09-14 16:19:06 UTC,"Sorry Bill, I was thinking that the unique index was doing double duty and providing a search function.  If not, then the MD5 way seems fine.  Do you see any reason not to do it like this:"
1695911,2018-09-14 18:05:18 UTC,"Yeah, I was thinking the same thing at first...  For _key, MD5(value || sort_value) makes sense.  Thanks for the suggestion.  I'll test that and push a branch in a bit."
1695911,2018-10-03 20:07:06 UTC,Expansion of the above proposals:
1695911,2018-09-13 14:20:07 UTC,"Stumbled on this while doing some local refactoring...  Dan, I think with the UNIQUE INDEX the table constraint is not necessary.  We have something like this locally:"
1695913,2017-06-11 06:49:41 UTC,"In fact digikam seems to freeze at *any* file dialog like ""Save As""..."
1695913,2017-08-14 15:55:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695914,2017-09-05 20:10:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695914,2017-09-05 20:10:03 UTC,I also have the problem with loosing the image editor menu bar when opening a second time. Problem is seen with 5.5. and appimage 5.6.
1695933,2017-06-07 14:23:42 UTC,"Change abandoned by Javier Peña (<email address hidden>) on branch: master
Review: https://review.openstack.org/471062
Reason: I'm abandoning the review on master and just keeping the one for stable/newton  [1]. Since we need to have a keystone v3 endpoint for the Nova Placement API to work, this doesn't make much sense on master. I'll check the options to remove keystone v2 support completely in Pike/Queens."
1695933,2017-06-19 22:59:07 UTC,"Reviewed:  https://review.openstack.org/471791
Committed: https://git.openstack.org/cgit/openstack/packstack/commit/?id=4a7f8d80beb6dbeb6c8bb1cc60143f613b5ac5cd
Submitter: Jenkins
Branch:    stable/newton"
1695933,2017-06-07 14:21:23 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/471791"
1695934,2017-06-05 16:54:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1695934,2017-06-06 07:35:43 UTC,How about a MOTD entry like this:
1695934,2018-01-31 14:15:52 UTC,"I think Mark the point is that it would be nice to have a full list of updates stored somewhere so that one can see exactly what happened to the snaps installed or previously installed over time, so if something goes wrong (but the bug isn't noticed for a while) then one can try and trace back to the exact revision combination of snap (+ content snap) + base snap that broke things."
1695934,2018-01-31 14:16:27 UTC,"Maybe this exists since this bug was filed, in which case, would be nice to have an explanation of where that information is! :)"
1695934,2018-04-21 06:11:51 UTC,Are the any news about the issue?
1695934,2018-08-03 13:48:58 UTC,"Today, snap updates (and any other changes under snapd's control) are visible in 'snap changes' for a few days."
1695935,2017-06-09 14:05:59 UTC,Any feedback on this? Is this totally useless?
1695935,2017-06-06 09:19:45 UTC,"Another, simpler, option would be to directly make the step used when using ctrl + shift + arrow key configurable, rather than the fixed value of 10 that is used now. This way there's no need to add four new operation and corresponding keyboard bindings. I'm fine with this solution as well (can produce a patch)."
1695935,2017-06-14 09:52:32 UTC,"Hi Walder. It's not at all useless, I just have a lot of other stuff going on."
1695935,2017-06-14 10:18:12 UTC,"> 1. Choice of 50px step. Will cause different behaviour for someone who switches to and from a HiDPI
> display - on HiDPI it will jump about half the lines of text. Even with single DPI the first press
> could step x lines of text, then the second press step x-1 lines depending on fontsize. I think a
> better approach would be to have a jump factor z, and multiply the font width/height by z.
"
1695935,2017-06-14 11:11:53 UTC,"1. I think you somewhat missed my point. :-) Yes it is configurable. But (taking me as an example) I take my HiDPI laptop on the train everyday, and have a LoDPI external monitor at home. As I switch between the two I don't want to have to change preference settings everytime to get predictable behaviour. To me predicatble is to jump X lines, not X pixels. You are mistaken about it only jumping ten. If the event widget is a terminal the line
  fontheight = widget.vte.get_char_height()
gets the height of a single char/cell/line in pixels, and resizes by that much. So on a HiDPI display where the font is 20px high, the jump is set to 20px. (Obviously width is as appropriate.)"
1695935,2017-06-14 11:40:29 UTC,"Addendum for 3. I'm trying to decide if there's a usecase for having different profiles have different step sizes, rather than a global setting. I'm also trying to figure out which section is the best place to add it the configurable option in the preferences pane (depends on Profile/Global). Let me mull that over before you go spending time editing the glade file."
1695935,2017-06-14 12:20:22 UTC,"1. I see now. For me when I wrote the patch the only thing that mattered was ""it just has to go fast"", but your concerns are valid."
1695935,2017-06-14 12:43:29 UTC,So your suggestion for 1) leads to code like the following:
1695935,2018-02-03 17:37:46 UTC,"For what it's worth, I've implemented the above set of changes (using separate keybindings for ""fast mode"" resize) at https://github.com/waldner/terminator, where I also plan to make some other slight modification to expose more data to plugins."
1695935,2018-02-03 19:00:45 UTC,"Sorry, I meant https://github.com/waldner/terminator/commit/ca41cb12b30c21b2bd6068eccee5cdccac1cd353."
1695935,2018-03-15 17:00:47 UTC,"I've just published the update version of core Terminator with support for the plugin_ng plugin architecture, along with a sample plugin to demonstrate what can be done with it. They are at https://github.com/waldner/terminator and https://github.com/waldner/terminator-runwith-plugin respectively."
1695935,2018-03-16 16:41:27 UTC,"Sorry, I'm not very familiar with LP.
I've now created a ""fast-resize"" branch and requested a merge directly on LP. https://code.launchpad.net/~waldner/terminator/fast-resize/+merge/341534."
1695935,2018-03-16 17:20:53 UTC,"Since the two patchsets are virtually non-overlapping, I've also created a merge request for the plugin-ng branch: https://code.launchpad.net/~waldner/terminator/plugin-ng/+merge/341537. Thanks."
1695935,2017-06-14 13:19:50 UTC,"It all boils down to whether you think user will be fine with a single operation that can be made slower or faster, or they'll want to maintain the original behavior and also have fast mode as an additional operation, so they can decide when to use which."
1695937,2019-09-19 14:48:20 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1695950,2017-06-20 21:30:00 UTC,"If you do steps 1-11 above, but don't turn left and just continue along the right edge of the world to the end, there is no crash. The crash only occurs if the end is reached while in the left half of the world."
1695950,2017-06-26 21:12:38 UTC,Now crashing at the end of other tracks. This seems to depend on the contents of the high score list. Crashes seem to occur when the high score list is full and being changed.
1695950,2017-06-29 20:35:17 UTC,Nothing to do with the track. It's a bug in the high score list update. Something is going wrong when a high score list has all 10 entries and a new one has to replace an old one.
1695968,2017-06-07 12:14:50 UTC,Issues with setup tools (closed in 1695969) and various python/system packages has been discovered.
1695968,2018-02-02 20:58:32 UTC,"I believe this has been corrected and that we have released the fix for this. We also have additional fixes to support newer versions of fedora, so we should be good here."
1695968,2018-02-08 13:21:15 UTC,This issue was fixed in the openstack/bifrost 5.0.0 release.
1695969,2017-06-06 11:30:11 UTC,"This is what occurs when env-setup.sh is not used to begin using the playbook.  tl;dr, we might want to stress that the latest pip should be installed, from pip, which will address setuptools as  well."
1695969,2017-06-07 12:09:01 UTC,This also affects fedora core 25 when running the test-bifrost.sh script.
1695969,2018-02-08 13:21:14 UTC,This issue was fixed in the openstack/bifrost 5.0.0 release.
1695969,2018-02-02 20:53:26 UTC,This was resolved by pach I31e2d3af04eb6fa74a03e7fa731f58dbb30bd3bc which landed in September.
1695988,2017-06-20 20:06:34 UTC,Glad to hear David!
1695988,2017-06-06 15:46:30 UTC,"Thanks for the patch Henrik, i'll release a new version with it asap."
1695992,2017-09-26 19:02:38 UTC,"There is no activity for fixing this bug for a while. I am going to remove assignee so that other contributors can take it, but please feel free to re-assign it to yourself if you want to continue to work on this bug."
1695992,2017-11-09 02:07:35 UTC,Fixed in patch:
1695992,2018-01-05 18:54:21 UTC,This issue was fixed in the openstack/python-zunclient 1.0.0 release.
1695994,2017-06-27 14:30:14 UTC,"Failed to import images from boot source http://images.maas.io/ephemeral-v3/daily/: HTTPConnectionPool(host='images.maas.io', port=80): Max retries exceeded with url: /ephemeral-v3/daily/streams/v1/index.sjson (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f09a41cbf28>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))"
1695994,2019-09-19 14:48:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1695998,2017-06-05 21:23:46 UTC,"Trying to correct line 22 of file ""classview.py"" with:"
1696001,2017-06-07 15:50:49 UTC,"Reviewed:  https://review.openstack.org/471487
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a33092fa9b0c65b37b9fdc860f5a571908d7a69
Submitter: Jenkins
Branch:    master"
1696001,2017-06-06 09:11:45 UTC,this is the commit that caused regression https://github.com/openstack/nova/commit/7a3362fd7b01152dcf1b62d0ce25663a3312aae8
1696001,2017-06-06 21:31:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/471487"
1696001,2017-06-07 14:19:53 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/471790"
1696001,2017-06-07 14:28:42 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/471796"
1696001,2017-06-08 21:51:10 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1696001,2017-06-19 12:45:48 UTC,This issue was fixed in the openstack/nova 15.0.6 release.
1696001,2017-06-09 13:04:41 UTC,"Reviewed:  https://review.openstack.org/471790
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6041572a4c95428f6b13a8d7569090b315a3abd1
Submitter: Jenkins
Branch:    stable/ocata"
1696001,2017-08-12 02:32:07 UTC,"Reviewed:  https://review.openstack.org/471796
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=041d58a980bd92efc26b20f062af423269b28429
Submitter: Jenkins
Branch:    stable/newton"
1696001,2017-08-28 09:55:27 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1696008,2017-06-05 23:07:35 UTC,"StacktraceTop:
 ?? ()
 closure_invoke_notifiers (notify_type=<optimized out>, closure=<optimized out>) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./gobject/gclosure.c:274
 g_closure_invalidate (closure=0x6e159b0) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./gobject/gclosure.c:583
 g_closure_unref (closure=0x6e159b0) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./gobject/gclosure.c:605
 g_source_destroy_internal (source=0x87b02f0, context=0x110a2b0, have_lock=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:1207"
1696008,2018-03-18 13:39:16 UTC,Gnome Shell crashed again this morning while doing software update with Webmin 1.880.
1696008,2018-04-02 20:52:52 UTC,Gnome Shell crashed again just now while updating
1696008,2020-11-16 08:36:29 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life on April, 2019"
1696009,2017-06-05 22:51:25 UTC,apport information
1696009,2017-06-05 22:51:29 UTC,apport information
1696009,2017-06-05 22:51:28 UTC,apport information
1696009,2017-06-05 22:51:27 UTC,apport information
1696009,2017-06-05 22:51:24 UTC,apport information
1696009,2017-06-05 22:51:35 UTC,apport information
1696009,2017-06-05 22:51:20 UTC,apport information
1696009,2017-06-05 22:51:17 UTC,apport information
1696009,2017-06-05 22:51:14 UTC,apport information
1696009,2017-06-05 22:51:31 UTC,apport information
1696009,2017-06-05 22:51:23 UTC,apport information
1696009,2017-06-05 22:51:12 UTC,apport information
1696009,2017-06-05 22:51:32 UTC,apport information
1696009,2017-06-05 22:51:38 UTC,apport information
1696009,2017-06-05 22:51:40 UTC,apport information
1696009,2017-06-05 23:00:10 UTC,This change was made by a bot.
1696009,2017-06-06 12:27:47 UTC,"Do you have a way to reproduce this bug, or was it a one time event?"
1696009,2017-06-05 22:51:34 UTC,apport information
1696021,2017-06-08 17:09:09 UTC,"Hmm, what's your proposed solution?  Can you propose a patch?"
1696021,2017-06-09 00:48:51 UTC,"Since the issue seems to be the same as it was for pysendy, where the version is being grabbed from __init__.py, you can either hardcode it in setup.py or add another version.py file that simply contains the version number and import that in both places. Unfortunately I have no idea how to submit a patch here..."
1696021,2018-05-11 19:20:13 UTC,"I've fixed this in setup.py now, somewhat hackily.
but basically we avoid importing ssh_import_id, but directly import version."
1696021,2020-02-11 17:05:54 UTC,This bug is fixed in the 5.8 release.
1696030,2017-10-23 08:18:54 UTC,One of the most important things we miss is the JS backtrace.
1696030,2017-10-23 08:21:12 UTC,"Related to this is also bug #1722886, as it's quite needed to include such informations we would collect in automatic reports."
1696030,2017-10-24 02:12:04 UTC,I'm not sure Gnome bug 789237 alone is sufficient here.
1696051,2019-06-06 21:59:45 UTC,I believe the overhauled bulk port code does include the binding information.
1696051,2017-09-29 08:43:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/508438"
1696051,2017-06-12 21:01:28 UTC,By visual inspection it seems valid. Still need to confirm with the API workflow. https://developer.openstack.org/api-guide/quick-start/api-quick-start.html
1696051,2017-06-19 10:51:18 UTC,What version?
1696051,2017-06-22 05:41:47 UTC,I tested this with master branch (of a couple of weeks ago) and ocata
1696054,2017-07-03 07:04:31 UTC,"You installed sicherboot, and did not create a /etc/kernel/cmdline with your kernel command line, hence it fails (in the first script). The second one it probably should not fail, but then, if you had created /etc/kernel/cmdline the first would not have failed either."
1696054,2017-07-04 09:59:41 UTC,Second part is fixed in https://github.com/julian-klode/sicherboot/commit/d520974305803d26de7b8a8b97eed1410635bfe8
1696054,2017-07-05 12:09:38 UTC,This bug was fixed in the package sicherboot - 0.1.3
1696054,2017-07-19 15:47:59 UTC,"This was actually happening for some other reasons, so the bug is actually of high priority, not low."
1696054,2017-07-19 15:48:38 UTC,"Ehm, medium, seeing as that is not really a core application."
1696071,2017-06-14 13:10:14 UTC,"There is no expectation in the charms at the moment that pool restrictions can be disabled, either for a specific relation or in general. We can discuss if that's a change we'd like to enable but the current expectation is that it is a one way change."
1696071,2017-06-14 13:26:35 UTC,"Right, and that makes sense. I've reported this one because we needed a way out of bug 1696073 and 'pending bug' with the same problem for radosgw."
1696072,2017-06-08 11:39:50 UTC,This issue was fixed in the openstack/neutron-lbaas-dashboard 3.0.0.0b2 development milestone.
1696076,2017-06-07 17:19:16 UTC,Tests are disabled because they ran on the older version of deployment. This bug says we need to make them work for v3 deployments and re-enable them. You can see which tests here: http://codesearch.openstack.org/?q=adopt%20to%20v3&i=nope&files=&repos=neutron
1696079,2017-08-22 14:23:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696079,2017-11-01 07:38:53 UTC,Have the same on 17.10 on 7700HQ with 1050 GTX
1696083,2017-06-27 07:47:49 UTC,Kolla is not affected by this issue by any of the packages. Marking as released
1696083,2017-06-27 07:45:31 UTC,"Change abandoned by Eduardo Gonzalez (<email address hidden>) on branch: master
Review: https://review.openstack.org/471285
Reason: yep, was fixed in ubuntu repositoriees"
1696083,2017-06-06 09:25:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/471285"
1696083,2017-06-12 10:15:23 UTC,Same issue found with ironic-inspector
1696083,2017-06-16 10:43:19 UTC,This bug was fixed in the package rally - 0.9.1-0ubuntu2
1696083,2017-06-12 08:07:27 UTC,"Hi James, how long use to take ubuntu packaging to be published into xenial-updates/pike repository?. Still seeing rally failing."
1696083,2017-06-12 08:32:59 UTC,Should be there today.
1696087,2018-09-26 17:47:08 UTC,mysql-utilities depends on python which in turn depends on python-minimal
1696087,2018-09-26 17:44:10 UTC,"Removing mysql-utilities (1.6.1-2) ...
/var/lib/dpkg/info/mysql-utilities.prerm: 6: /var/lib/dpkg/info/mysql-utilities.prerm: pyclean: not found
dpkg: error processing package mysql-utilities (--purge):
 subprocess installed pre-removal script returned error exit status 127"
1696092,2017-12-08 12:05:49 UTC,"Hi Roland,
Thank you for taking the time to report this bug and helping to make Ubuntu better.
But first of all I must beg your pardon as I don't see why no one came by here yet.
I currently clean up older bugs without actvitity."
1696099,2017-07-07 11:51:40 UTC,"I packaged:
- omniORB-4.2.2 - https://github.com/philippe-goetz/omniORB
- omniORBpy-4.2.2 including Python3 - https://github.com/philippe-goetz/omniORBpy
for debian stretch"
1696099,2019-10-27 10:01:51 UTC,Thanks for reporting.
1696101,2017-06-08 12:46:12 UTC,"Change abandoned by vinay kumar muddu (<email address hidden>) on branch: master
Review: https://review.openstack.org/471314
Reason: Creating new patch with more changes. Abandoning it."
1696105,2017-06-06 11:45:53 UTC,thanks for finding and the evaluation.
1696108,2019-09-19 14:48:25 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1696109,2017-06-06 12:46:09 UTC,I can't imagine how this is a client-side issue.
1696113,2017-06-20 09:46:06 UTC,"We also don't wait for Mongo to recover to a stable state, we should monitor how Mongo behaves and throttle connections until it's stable."
1696116,2018-06-20 11:20:24 UTC,I'm seeing this using a regular mouse with scroll wheel as well. The first click of the wheel after focusing qpdfview often scrolls in the wrong direction.
1696124,2017-06-06 14:13:34 UTC,"# This is the initial network config.
# It can be overwritten by cloud-init or console-conf.
network:
    version: 2
    ethernets:
        all-en:
            match:
                name: ""en*""
            dhcp4: true
        all-eth:
            match:
                name: ""eth*""
            dhcp4: true"
1696124,2017-06-12 21:19:21 UTC,@Paul
1696124,2017-06-06 13:27:16 UTC,Thanks for the report! What do you see in /etc/netplan/00-snapd-config.yaml ?
1696124,2017-06-15 19:10:53 UTC,"This actually is on a plano device (stlouis) where I'm hitting the problem, and it does have that in /etc/netplan/00-default-nm-renderer.yaml. It does not seem to depend on a lot of snaps being refreshed at once, as mentioned before, I can reproduce it with just 'sudo snap refresh network-manager --ignore-validation && sudo snap install <something>""  Anything can be used for the install snap, even hello. As a quick way of reproducing, something like this script should get you there (in this case, I'm flipping between edge and stable since there are different versions of nm in each - it ran about all the way through about twice for me before hitting the error):
#!/bin/bash
set -ex
while [ 1 ]; do
    sudo snap refresh --edge network-manager --ignore-validation && sudo snap install hello && sudo snap remove hello
    [ ""$?"" != ""0"" ] && break
    sleep 1"
1696125,2017-08-08 16:09:51 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/491844"
1696125,2017-06-13 19:36:24 UTC,This is the qemu guest log but there isn't much there:
1696125,2017-08-08 16:04:58 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/491843"
1696125,2017-06-27 16:04:15 UTC,"Automatically discovered version pike in description. If this is incorrect, please update the description to include 'nova version: ...'"
1696125,2017-06-19 10:47:40 UTC,It seems vif_type='tap' is just broken with libvirt so it's not safe to use. There isn't anything we can do on the Neutron side to fix this other than suggest plugins not use that vif_type until a fix is found in libvirt.
1696125,2017-06-13 23:06:45 UTC,"Reviewed:  https://review.openstack.org/472377
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a4e51d5c69b9dced99db0b0d78ef8b784cb50960
Submitter: Jenkins
Branch:    master"
1696125,2017-06-13 22:18:45 UTC,"I also wonder if we could be hitting some weird apparmor issues or something, see:"
1696125,2017-06-13 20:37:13 UTC,There is a weird 5 minute gap in the neutron L2 agent logs here:
1696125,2017-06-13 20:34:38 UTC,"Looking in the neutron L2 agent logs, I see the tap device is attached/added here:"
1696125,2017-06-13 20:16:57 UTC,"Looking at the libvirtd logs, I see the net1 device being added shortly before the detach:"
1696125,2017-06-13 19:30:26 UTC,Got a hit in the neutron debug patch:
1696125,2017-06-08 16:08:20 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/472309"
1696125,2017-06-08 21:51:13 UTC,This issue was fixed in the openstack/nova 16.0.0.0b2 development milestone.
1696125,2017-06-08 18:56:49 UTC,Running debug on the nova side using:
1696125,2017-06-08 18:54:30 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/472377"
1696125,2017-06-08 18:49:20 UTC,Neutron revert of the LB tap type change:
1696125,2017-06-08 18:31:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/472371"
1696125,2017-06-08 17:43:48 UTC,https://wiki.libvirt.org/page/VM_lifecycle#Transient_guest_domains_vs_Persistent_guest_domains
1696125,2017-06-08 17:43:16 UTC,Apparently this is still failing on master even though the fix was merged:
1696125,2017-06-08 17:01:08 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/472345"
1696125,2017-06-07 21:44:23 UTC,"Reviewed:  https://review.openstack.org/441204
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=563c0927d14d052e3f1fad80df95fe4a7c48d38b
Submitter: Jenkins
Branch:    master"
1696125,2017-06-06 16:59:17 UTC,Impacting CI runs so bumping to High severity.
1696125,2017-06-12 07:46:42 UTC,"Reviewed:  https://review.openstack.org/472371
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fabfb347f51afbe9064a6d0061404316786140cb
Submitter: Jenkins
Branch:    master"
1696125,2017-06-06 18:34:33 UTC,https://review.openstack.org/#/c/441204/ should address this.
1696125,2017-08-16 02:30:34 UTC,"Reviewed:  https://review.openstack.org/491843
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c04c5d57cc41deacec53e18abe3ba93a1d5b5ccf
Submitter: Jenkins
Branch:    stable/ocata"
1696125,2017-09-21 15:10:10 UTC,"It doesn't look like a timeout issue. When the test is going to fail, you see these messages in the logs:"
1696125,2019-08-02 12:23:36 UTC,"It is a great post. It's been such a wonderful experience while reading your blog. If facing any problem
 related to a Linux  please visit https://www.europewebsitedevelopment.com/ for any technical
support assistance"
1696125,2017-09-28 17:40:49 UTC,"Thanks for the comment. In this case, that shouldn't be the case as I don't think the volume was ever mounted by the instance's OS. From what I've seen cirros doesn't automount volumes that get attached. And if it's not mounted, I can't think of anything that the OS would do to prevent it from be detached. But I certainly could be missing something..."
1696125,2017-09-21 19:46:54 UTC,"Something to know about detaching from a guest transient domain is that it's an asynchronous request to the guest OS [1], which the guest OS can choose to ignore (e.g. if it has a file open or is otherwise busy)."
1696125,2017-09-21 12:46:07 UTC,Version of nova:
1696125,2017-09-21 12:45:32 UTC,"While debugging the LiveMigrationTest.test_iscsi_volume tempest test, I am seeing this in my local env as one of the causes of intermittent failures with this test. I can get this to fail maybe 2-3x a day. This is what I run to provoke it:"
1696125,2017-08-28 09:55:00 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1696125,2017-08-22 11:39:06 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1696125,2017-08-13 01:42:35 UTC,"Reviewed:  https://review.openstack.org/472309
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=55e2c851f15d68e7891f867cc5f32eece9a95034
Submitter: Jenkins
Branch:    stable/ocata"
1696125,2017-08-16 19:53:24 UTC,"Reviewed:  https://review.openstack.org/491844
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2cf2b7ea6441c2eb73574a6e35ef10ae07550c6b
Submitter: Jenkins
Branch:    stable/newton"
1696125,2017-08-16 08:48:48 UTC,"Reviewed:  https://review.openstack.org/472345
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b2bafd09c3cde8cfd782a69aa8aa5dd53809d5bc
Submitter: Jenkins
Branch:    stable/newton"
1696126,2017-06-06 13:42:35 UTC,I'm beeing asked to re-install apport 2.20.1-0ubuntu2. How do I do that?
1696127,2020-02-04 11:59:50 UTC,This was fixed many moons ago. Please re-open if you continue to see this.
1696139,2017-06-19 07:49:09 UTC,"Hello James, or anyone else affected,"
1696139,2017-07-17 14:43:28 UTC,This bug was fixed in the package cinder - 2:10.0.2-0ubuntu1
1696139,2017-06-29 21:33:36 UTC,xenial-ocata-proposed:
1696139,2017-06-29 16:05:48 UTC,Manually verified horizon as not covered by automated tests.
1696139,2017-06-16 09:45:44 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-29 16:03:51 UTC,zesty-proposed tempest smoke testing results
1696139,2017-06-27 15:31:31 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1696139,2017-06-19 07:50:36 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-19 07:50:13 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-19 07:50:02 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-19 07:49:51 UTC,"Hello James, or anyone else affected,"
1696139,2017-07-17 14:43:51 UTC,This bug was fixed in the package neutron - 2:10.0.2-0ubuntu1
1696139,2017-06-16 10:18:52 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-16 10:42:56 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-19 07:49:33 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-16 15:19:48 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-19 07:49:23 UTC,"Hello James, or anyone else affected,"
1696139,2017-06-16 10:47:07 UTC,"Hello James, or anyone else affected,"
1696139,2017-07-18 11:53:32 UTC,"This bug was fixed in the package swift - 2.13.1-0ubuntu0.17.04.1~cloud0
---------------"
1696139,2017-07-17 14:43:36 UTC,This bug was fixed in the package heat - 1:8.0.1-0ubuntu1
1696139,2017-07-18 11:53:31 UTC,The verification of the Stable Release Update for swift has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1696139,2017-07-18 11:53:20 UTC,"This bug was fixed in the package nova - 2:15.0.5-0ubuntu1~cloud0
---------------"
1696139,2017-07-18 11:53:20 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1696139,2017-07-18 11:53:06 UTC,"This bug was fixed in the package neutron - 2:10.0.2-0ubuntu1~cloud0
---------------"
1696139,2017-07-18 11:53:05 UTC,The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1696139,2017-07-18 11:52:54 UTC,"This bug was fixed in the package keystone - 2:11.0.2-0ubuntu1~cloud0
---------------"
1696139,2017-07-18 11:52:52 UTC,The verification of the Stable Release Update for keystone has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1696139,2017-07-18 11:52:34 UTC,"This bug was fixed in the package horizon - 3:11.0.2-0ubuntu1~cloud0
---------------"
1696139,2017-07-18 11:52:33 UTC,The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1696139,2017-07-18 11:52:22 UTC,"This bug was fixed in the package heat - 1:8.0.1-0ubuntu1~cloud0
---------------"
1696139,2017-07-18 11:52:21 UTC,The verification of the Stable Release Update for heat has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1696139,2017-07-18 11:52:09 UTC,"This bug was fixed in the package cinder - 2:10.0.2-0ubuntu1~cloud0
---------------"
1696139,2017-07-18 11:52:08 UTC,The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1696139,2017-07-17 14:53:48 UTC,This bug was fixed in the package keystone - 2:11.0.2-0ubuntu1
1696139,2017-07-17 14:44:02 UTC,This bug was fixed in the package swift - 2.13.1-0ubuntu0.17.04.1
1696139,2017-07-17 14:44:00 UTC,This bug was fixed in the package nova - 2:15.0.5-0ubuntu1
1696139,2017-07-17 14:43:55 UTC,This bug was fixed in the package horizon - 3:11.0.2-0ubuntu1
1696139,2017-06-16 09:29:55 UTC,"Hello James, or anyone else affected,"
1696139,2017-07-17 14:43:32 UTC,"The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1696139,2017-06-16 10:15:31 UTC,"Hello James, or anyone else affected,"
1696142,2017-06-26 09:40:57 UTC,"Currently set to Medium, since this is technically an optimisation issue."
1696146,2017-06-06 15:24:12 UTC,Xen support is 100% untested so I'm not surprised that this does not actually work.
1696146,2017-06-06 15:24:39 UTC,I'm going to propose that we take the Xen support out of the charm as its in such a bad way.
1696146,2021-01-08 11:22:15 UTC,https://review.opendev.org/c/openstack/charm-nova-compute/+/518439
1696153,2017-06-06 15:38:58 UTC,I believe putting 3.1.1 in xenial-backports would be also a solution
1696157,2018-02-16 18:07:49 UTC,This should also include the ability to display a copy bucket as a shared list
1696157,2018-08-03 22:21:09 UTC,+1 to allowing buckets with btype=staff_client to display in the OPAC!  Is this the line that prevents staff_client buckets from displaying in the OPAC? https://github.com/evergreen-library-system/Evergreen/blob/180e3329fcce010b58b9e9ca826f9c1757e091e3/Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader/Search.pm#L281
1696157,2019-03-08 20:59:33 UTC,"After poking at this a bit, it seems like I do not have enough understanding of the search code to accomplish this.  Changing the line I mentioned in line #2 allows the bucket's name and description to show up in the OPAC, but does not allow the records in that bucket to show up.  It seems like whoever tackles this would have to do some work on the container search filter here: https://github.com/evergreen-library-system/Evergreen/blob/6c0e0d5efaa90dd22468127d6e7d5bf87bdff6c1/Open-ILS/src/perlmods/lib/OpenILS/Application/Storage/Driver/Pg/QueryParser.pm#L725"
1696163,2017-06-07 12:25:51 UTC,How is that not a bug if the exported pdf is incorrect ? Is that a feature that grouped objects are exported with wrong colors ?
1696163,2017-06-10 13:03:03 UTC,"Here is a cleaned-up version of the original file, that exposes the same problem."
1696163,2017-06-10 12:40:21 UTC,"How the fact that the file was imported from a PDF changes that however inkscape displays a file, it should export it the same way ?"
1696163,2017-06-10 12:26:21 UTC,"If the file were a native Inkscape svg, I would consider this a likely bug."
1696163,2017-06-07 11:38:57 UTC,"I would suggest not a bug, but the svg is a likely imported from pdf or similar."
1696164,2017-08-21 20:58:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696165,2017-07-17 11:57:59 UTC,This bug was fixed in the package linux - 4.10.0-28.32
1696165,2017-06-06 16:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1696165,2017-06-13 21:44:56 UTC,"== Without the patch ==
ubuntu@ubuntu:~/testing/mce-test/cases/function/hwpoison$ sudo ./run_hugepage_overcommit.sh
[sudo] password for ubuntu:"
1696165,2017-06-14 19:33:42 UTC,"== With patch applied ==
ubuntu@ubuntu:~/testing/mce-test/cases/function/hwpoison$ uname -a
Linux ubuntu 4.10.0-22-generic #24~lp1696165+softlockup.1 SMP Wed Jun 14 19:05:07 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux"
1696165,2017-06-15 13:35:15 UTC,Test Kernel is available in PPA: https://launchpad.net/~centriq-team/+archive/ubuntu/lp1696165/
1696165,2017-07-10 08:23:23 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1696165,2017-07-14 13:49:40 UTC,== Testing kernel in -proposed ==
1696165,2017-07-14 14:18:39 UTC,== with hwpoison-inject module ==
1696168,2017-06-07 05:21:01 UTC,From DpkgTerminalLog.txt:
1696168,2017-07-04 13:49:34 UTC,I changed the wireshark group to a system group. No success. I will now delete it and retry.
1696168,2017-06-08 12:37:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696171,2017-06-06 16:57:16 UTC,"06/06 16:45:45 <Laney> bigon: is it intentional that libgeoclue-2-0 doesn't depend on geoclue-2.0?
06/06 16:46:00 <Laney> It's a generated wrapper around the DBus API, right?
06/06 16:50:24 <@bigon> mmh
06/06 16:50:57 <@bigon> not sure it's intentional
06/06 17:53:18 <Laney> bigon: ok, I'll file a bug"
1696171,2017-06-06 18:03:08 UTC,This bug was fixed in the package geoclue-2.0 - 2.4.5-1ubuntu1
1696173,2017-06-20 08:33:06 UTC,I think the easiest way to solve this to add --follow-symlinks to sed -i.
1696173,2018-01-18 08:11:12 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1987
1696175,2017-06-06 17:09:47 UTC,"On Tue, Jun 06, 2017 at 04:50:37PM -0000, Jeremy Bicha wrote:

> Public bug reported:
>
> Ubuntu 17.10 daily ISO with GNOME
>
> Of course, the current implementation isn't a true webapp but more of a
> bookmark but maybe there's some way we could get the blue dot.
>
> - Have a background service running? The problem is when should the service stop running?
"
1696179,2017-06-06 17:16:11 UTC,GNOME Tweak Tool does not respond well to changes in its fonts.
1696180,2017-06-06 17:08:56 UTC,I'm using Fedora 24 with version:
1696180,2017-06-06 17:32:33 UTC,"When reporting bugs to the QEMU project, please always try with the latest release first (distros are often not shipping the latest version). So can you please try with the latest release of QEMU (currently version 2.9.0)?"
1696180,2017-06-07 19:07:50 UTC,Just upgraded to 2.9.0 and actually I see a different issue:
1696184,2017-06-06 17:50:08 UTC,Please run the following commands and post the output:
1696184,2017-06-06 18:13:12 UTC,this is likely not your bug. apparently ubiquity does not install mdadm into target install dir at all.
1696184,2017-06-06 18:35:24 UTC,this is ubiquity not installing mdadm  onto target
1696184,2017-06-06 18:38:22 UTC,confirmed. a true dup of #880766 from 2011. Today is 2017 and installing ubuntu on software raid is still unsupported scenario. this is ubuntu...
1696184,2017-06-06 21:02:29 UTC,"Grub should not need mdadm for grub-probe to work.  Whenever I install on raid, I never have the boot loader fail to install; just have to remember to chroot in after and install mdadm before rebooting or the installed system won't boot past the initramfs."
1696184,2017-06-06 21:13:00 UTC,"It looks like it is finding the array, but doesn't find anything inside it.  What does blkid say is in /dev/md0?"
1696184,2017-06-06 21:41:23 UTC,"root@lelikusa:~# blkid /dev/md0
/dev/md0: UUID=""35233d76-cfd5-4608-a347-adc92b104f78"" TYPE=""ext2""
root@lelikusa:~# cat /proc/mounts | grep md0
/dev/md0 /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 0"
1696184,2017-06-08 13:09:26 UTC,"Oh, I missed it in the log the first time; grub-probe did detect ext2 on /dev/md0.  But that was on the installed system right?  Can you run it from the livecd?"
1696186,2017-06-15 10:48:20 UTC,"As far as I know, this is normal and expected behavior. Although perhaps not very helpful."
1696186,2017-06-15 11:07:21 UTC,"Thanks for looking at this. I realise it's not a bug but I think it is an
oversight and maybe fixing it could be considered a feature request?"
1696188,2019-03-12 05:50:21 UTC,Do you still have this issue with Inkscape 0.92.4? Can't reproduce with Inkscape 0.92.4 on Windows 10.
1696188,2019-06-10 07:58:28 UTC,"Closing as there has been no response for 60 days. If you still have a similar issue, please file a report on our new bug tracker: https://inkscape.org/report. Thank you!"
1696197,2017-12-28 19:30:10 UTC,"Apologies, I didn't get any notification of this and bug tracking has moved to https://bitbucket.org/jgoguen/calibre-kobo-driver/issues?status=new&status=open. I only used Launchpad because it let me set bugs private while books were uploaded but I have another solution and honestly I don't like Launchpad all that much."
1696197,2017-12-30 14:01:47 UTC,"Hi,"
1696197,2017-07-03 17:31:39 UTC,Bump
1696210,2017-06-06 18:56:11 UTC,"Also, python is installed, as is python3"
1696210,2017-09-11 12:02:49 UTC,"In Makefile I changed the 5th line from:
   py_compilefiles *.py
to
   pycompile *.py"
1696216,2021-01-07 04:03:34 UTC,4.8 EOL
1696216,2017-06-08 17:21:12 UTC,"Try
sudo apt-get autoremove
sudo apt-get update
sudo apt-get upgrade
reboot
This help me"
1696216,2017-06-06 20:05:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696216,2017-06-07 17:25:38 UTC,"I am new to the Linux environment and experienced this problem on my 1st install so I reinstalled the Ubuntu system figuring that I had done something wrong with the 1st Install.
After this 2nd install, I saw that there was a System Update listed and attempted to install this update and the update got about half way and froze.
Please help me.  I don't know what to do next."
1696221,2017-06-06 21:31:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/471486"
1696221,2017-07-01 02:52:24 UTC,"Reviewed:  https://review.openstack.org/471486
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c3d466dd4d9739844404fdd9c4170c4a8284a4aa
Submitter: Jenkins
Branch:    master"
1696221,2017-07-28 07:42:09 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1696221,2018-04-19 14:32:45 UTC,"Reviewed:  https://review.openstack.org/515581
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8c4db90d0398cefaac99fcef44a9e19d1bf40ad2
Submitter: Zuul
Branch:    stable/ocata"
1696221,2018-05-02 12:06:04 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1696221,2017-10-27 03:53:41 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/515581"
1696231,2017-06-06 19:55:28 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1543192, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1696231,2017-06-06 22:01:22 UTC,"The crash stacktrace might be the same as in the dup report, due to no screens found, but I think it is a separate bug: the dup bugreport has no indication of 2 graphics cards being used, and the need to blacklist one module."
1696231,2017-12-15 10:50:18 UTC,"how can I get radeon and amdgpu to play nice with each other ?
or better yet not use amdgpu and still be able to use opencl"
1696231,2018-05-15 10:06:21 UTC,"Firstly, AMD has released amdgpu-pro 18.10 (for rhel and supports Ubuntu 16.04.4):"
1696231,2018-05-15 10:07:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696236,2017-06-09 07:11:45 UTC,Agreed on the lack of documentation around this. I looked into the client functions a little bit tonight and came up with the following:
1696236,2017-06-10 01:52:15 UTC,"That looks like a good start, but it would mean handling reauth at the client level (ie, because Connection knows how to reauth with either a Session or a url/username/password, but can’t with just a token)"
1696236,2017-06-11 22:41:24 UTC,"Right. If Connection is given a storage URL and auth-token, it doesn't have the credentials to attempt to get a new token if the current one expires. I was trying to explore what can be done with the existing code."
1696238,2017-06-08 16:06:01 UTC,"I believe that replacing ng-if with ng-show will also correct any scope issues, as show doesn't create a new isolate scope. I ran into the ng-if issue myself last week."
1696240,2017-06-08 06:01:35 UTC,"Probably a good idea to use out-of-tree amdgpu.ko for now, until Artful release."
1696240,2017-06-07 12:49:27 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 stable kernel[0].
1696240,2017-06-07 20:04:38 UTC,"Ubuntu 4.10.0-22-generic: crash
mainline 4.10.17: crash
mainline 4.11.3: OK"
1696240,2017-06-06 20:30:16 UTC,This change was made by a bot.
1696247,2021-01-07 04:03:49 UTC,4.8 EOL
1696247,2018-05-08 18:10:25 UTC,This change was made by a bot.
1696252,2017-06-22 23:38:19 UTC,nagios3 is seeded in Ubuntu: http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.artful/view/head:/supported-misc-servers
1696252,2017-08-22 00:22:06 UTC,"We are in discussions to do this for 18.04 (with a transition to icinga2 everywhere). But it will need MIRs, etc."
1696252,2018-05-15 12:39:41 UTC,"By the way, monitoring-plugins is stuck in cosmic-proposed now because it drops the nagios-plugins* packages which nagios3 still depends on."
1696252,2018-08-23 20:01:15 UTC,"Removing packages from cosmic:
 nagios2mantis 3.1-1.1 in cosmic
  nagios2mantis 3.1-1.1 in cosmic amd64
  nagios2mantis 3.1-1.1 in cosmic arm64
  nagios2mantis 3.1-1.1 in cosmic armhf
  nagios2mantis 3.1-1.1 in cosmic i386
  nagios2mantis 3.1-1.1 in cosmic ppc64el
  nagios2mantis 3.1-1.1 in cosmic s390x
Comment: Depends on obsolete nagios3, removed from Debian testing; Debian bug #846854, LP: #1696252
1 package successfully removed."
1696252,2018-08-23 20:04:28 UTC,"Removing packages:
 nagios3 3.5.1.dfsg-2.1ubuntu8 in cosmic
  nagios3 3.5.1.dfsg-2.1ubuntu8 in cosmic amd64
  nagios3 3.5.1.dfsg-2.1ubuntu8 in cosmic arm64
  nagios3 3.5.1.dfsg-2.1ubuntu8 in cosmic armhf
  nagios3 3.5.1.dfsg-2.1ubuntu8 in cosmic i386
  nagios3 3.5.1.dfsg-2.1ubuntu8 in cosmic ppc64el
  nagios3 3.5.1.dfsg-2.1ubuntu8 in cosmic s390x
  nagios3-cgi 3.5.1.dfsg-2.1ubuntu8 in cosmic amd64
  nagios3-cgi 3.5.1.dfsg-2.1ubuntu8 in cosmic arm64
  nagios3-cgi 3.5.1.dfsg-2.1ubuntu8 in cosmic armhf
  nagios3-cgi 3.5.1.dfsg-2.1ubuntu8 in cosmic i386
  nagios3-cgi 3.5.1.dfsg-2.1ubuntu8 in cosmic ppc64el
  nagios3-cgi 3.5.1.dfsg-2.1ubuntu8 in cosmic s390x
  nagios3-common 3.5.1.dfsg-2.1ubuntu8 in cosmic amd64
  nagios3-common 3.5.1.dfsg-2.1ubuntu8 in cosmic arm64
  nagios3-common 3.5.1.dfsg-2.1ubuntu8 in cosmic armhf
  nagios3-common 3.5.1.dfsg-2.1ubuntu8 in cosmic i386
  nagios3-common 3.5.1.dfsg-2.1ubuntu8 in cosmic ppc64el
  nagios3-common 3.5.1.dfsg-2.1ubuntu8 in cosmic s390x
  nagios3-core 3.5.1.dfsg-2.1ubuntu8 in cosmic amd64
  nagios3-core 3.5.1.dfsg-2.1ubuntu8 in cosmic arm64
  nagios3-core 3.5.1.dfsg-2.1ubuntu8 in cosmic armhf
  nagios3-core 3.5.1.dfsg-2.1ubuntu8 in cosmic i386
  nagios3-core 3.5.1.dfsg-2.1ubuntu8 in cosmic ppc64el
  nagios3-core 3.5.1.dfsg-2.1ubuntu8 in cosmic s390x
  nagios3-dbg 3.5.1.dfsg-2.1ubuntu8 in cosmic amd64
  nagios3-dbg 3.5.1.dfsg-2.1ubuntu8 in cosmic arm64
  nagios3-dbg 3.5.1.dfsg-2.1ubuntu8 in cosmic armhf
  nagios3-dbg 3.5.1.dfsg-2.1ubuntu8 in cosmic i386
  nagios3-dbg 3.5.1.dfsg-2.1ubuntu8 in cosmic ppc64el
  nagios3-dbg 3.5.1.dfsg-2.1ubuntu8 in cosmic s390x
  nagios3-doc 3.5.1.dfsg-2.1ubuntu8 in cosmic amd64
  nagios3-doc 3.5.1.dfsg-2.1ubuntu8 in cosmic arm64
  nagios3-doc 3.5.1.dfsg-2.1ubuntu8 in cosmic armhf
  nagios3-doc 3.5.1.dfsg-2.1ubuntu8 in cosmic i386
  nagios3-doc 3.5.1.dfsg-2.1ubuntu8 in cosmic ppc64el
  nagios3-doc 3.5.1.dfsg-2.1ubuntu8 in cosmic s390x
Comment: (From Debian) ROM; unfixed security uploads, no maintainer upload since 2 years; Debian bug #845765
Remove [y|N]? y
Removing packages:
 nagios3 3.5.1.dfsg-2.1ubuntu9 in cosmic
Comment: (From Debian) ROM; unfixed security uploads, no maintainer upload since 2 years; Debian bug #845765
Remove [y|N]? y"
1696257,2019-03-21 02:59:21 UTC,"Can't reproduce this issue with Inkscape 0.92.4, using Breeze light on openSUSE TW 20190310."
1696257,2019-06-10 07:58:13 UTC,"Closing as there has been no response for 60 days. If you still have a similar issue, please file a report on our new bug tracker: https://inkscape.org/report. Thank you!"
1696261,2017-08-02 20:48:49 UTC,This is also the case on a clean Artful (17.10) install.
1696261,2017-06-06 22:12:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696272,2017-06-23 05:16:24 UTC,"Rich, was this done as part of accessibility? I've noticed that clicking on the label also toggles the option."
1696272,2019-09-19 14:48:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1696273,2017-06-20 22:56:08 UTC,"This will happen anytime we are sending data (not just for the keyring). Anytime the joiner is slow on starting to listen on the server socket, the donor will fail (because we only try it once)."
1696273,2017-06-21 02:32:01 UTC,Fix committed for the next release of PXC 5.6/5.7.  We now retry 30 times (with the default 1-second intervals).
1696273,2018-01-18 08:11:57 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-833
1696277,2019-07-17 14:47:40 UTC,"Maybe it's because of dpkg, apt, bad connection, unexpected interrupts, etc.  This error happens with any packages in the error messages but it's never by bugs from those packages."
1696285,2019-09-19 11:53:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1696285,2017-06-07 18:31:00 UTC,"Commissioning and testing are separate node states. They can be run independently and have different failure states. MAAS allows nodes to automatically transition from commissioning to testing as both states are often run sequentially. Once commissioning successfully finishes it does not need to be run again unless hardware has changed. So nodes which fail testing only need to be retested, not recommissioned."
1696289,2017-06-07 02:00:37 UTC,This change was made by a bot.
1696303,2017-06-07 06:41:41 UTC,Yeah that's because there is no way to pass the security group when creating the load balancer. This is a long standing bug in lbaas: https://bugs.launchpad.net/octavia/+bug/1295424.
1696308,2017-08-11 14:46:59 UTC,Bumping this from rc1 since the proposed solution contains an API change. We need to discuss approaches like this at the PTG (microversions).
1696308,2020-03-31 18:12:14 UTC,"This bug seems invalid due to [1], token revocation list is deprecated and only returns 410."
1696308,2018-04-09 20:36:38 UTC,Automatically unassigning due to inactivity.
1696308,2017-08-01 20:42:49 UTC,"Ah - good to know. In that case, we should take steps to clarify the documentation and comments."
1696308,2017-08-08 19:09:18 UTC,There is a patch up that addresses this - https://review.openstack.org/#/c/490685/
1696308,2017-07-25 17:27:09 UTC,"Another thing we can do now that PKI isn't in master, is make it so that API returns an empty list."
1696308,2017-06-09 19:58:35 UTC,"On second thought, if a deployment is not expecting to issue or use PKI tokens, a 500 seems like the right response. We take a similar stance when using Fernet tokens. If a key repository hasn't been setup to encrypt and decrypt tokens, keystone will 500 the authentication or validation request [0]."
1696308,2017-06-09 19:49:00 UTC,Setting this to high since it is backwards incompatible when keystone-manage pki_setup hasn't been run in the deployment.
1696308,2017-06-09 19:48:14 UTC,It looks like the issue is due to:
1696308,2017-08-01 18:20:10 UTC,"revoked tokens weren't specific to PKI (contrary to some documentation and code comments). They worked with UUID tokens as well as long as you setup the certificate signing (since the revocation list is signed... i.e., signing wasn't just for PKI). I suspect someone believed the incorrect docs/comments and removed more than they should have here..."
1696311,2017-06-09 16:45:16 UTC,Filed in GitHub (where layer-basic is maintained) in https://github.com/juju-solutions/layer-basic/issues/99
1696322,2017-06-07 08:29:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1696322,2020-06-05 15:23:20 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1696322,2020-08-05 04:17:36 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1696323,2017-06-07 08:49:13 UTC,"yeah, already have patch: https://review.openstack.org/471223"
1696323,2017-06-07 07:52:44 UTC,It seems a duplicate of this bug: https://bugs.launchpad.net/cinder/+bug/1566069.
1696323,2018-01-12 19:04:40 UTC,Unassigning due to no activity for > 6 months.
1696324,2017-10-03 18:27:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696325,2017-06-07 09:40:20 UTC,apport information
1696325,2017-06-07 07:39:50 UTC,"When connecting dock to laptop following lines appear to dmesg:
[  407.217872] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[  407.217885] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID)
[  407.217893] pcieport 0000:00:1c.4:   device [8086:a114] error status/mask=00000001/00002000
[  407.217899] pcieport 0000:00:1c.4:    [ 0] Receiver Error         (First)
[  407.750868] hp_wmi: Unknown event_id - 131073 - 0x1
[  407.863552] ACPI Error: [SPRT] Namespace lookup failure, AE_ALREADY_EXISTS (20160422/dswload2-330)
[  407.863564] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160422/psobject-227)
[  407.863569] ACPI Error: Method parse/execution failed [\_GPE._E4C] (Node ffff903add0f92f8), AE_ALREADY_EXISTS (20160422/psparse-542)
[  407.863581] ACPI Error: Method parse/execution failed [\_GPE._E4C] (Node ffff903add0f92f8), AE_ALREADY_EXISTS (20160422/psparse-542)
[  407.863594] ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_E4C] (20160422/evgpe-592)
[  408.175164] pci 0000:04:00.0: [8086:1578] type 01 class 0x060400
[  408.175332] pci 0000:04:00.0: supports D1 D2
[  408.175335] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[  408.175565] pci 0000:04:00.0: System wakeup disabled by ACPI
[  408.187146] pci 0000:05:00.0: [8086:1578] type 01 class 0x060400
[  408.187340] pci 0000:05:00.0: supports D1 D2
[  408.187343] pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[  408.187507] pci 0000:05:01.0: [8086:1578] type 01 class 0x060400
[  408.187679] pci 0000:05:01.0: supports D1 D2
[  408.187681] pci 0000:05:01.0: PME# supported from D0 D1 D2 D3hot D3cold
[  408.187825] pci 0000:05:02.0: [8086:1578] type 01 class 0x060400
[  408.187995] pci 0000:05:02.0: supports D1 D2
[  408.187997] pci 0000:05:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[  408.188152] pci 0000:05:04.0: [8086:1578] type 01 class 0x060400
[  408.188314] pci 0000:05:04.0: supports D1 D2
[  408.188317] pci 0000:05:04.0: PME# supported from D0 D1 D2 D3hot D3cold
[  408.188478] pci 0000:04:00.0: PCI bridge to [bus 05-6e]
[  408.188491] pci 0000:04:00.0:   bridge window [mem 0xb4000000-0xe20fffff]
[  408.188500] pci 0000:04:00.0:   bridge window [mem 0x50000000-0x99ffffff 64bit pref]
[  408.188619] pci 0000:06:00.0: [8086:1577] type 00 class 0x088000
[  408.188645] pci 0000:06:00.0: reg 0x10: [mem 0xe2000000-0xe203ffff]
[  408.188662] pci 0000:06:00.0: reg 0x14: [mem 0xe2040000-0xe2040fff]
[  408.188855] pci 0000:06:00.0: supports D1 D2
[  408.188857] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[  408.189037] pci 0000:05:00.0: PCI bridge to [bus 06]
[  408.189050] pci 0000:05:00.0:   bridge window [mem 0xe2000000-0xe20fffff]
[  408.189149] pci 0000:05:01.0: PCI bridge to [bus 07-39]
[  408.189161] pci 0000:05:01.0:   bridge window [mem 0xb4000000-0xcbefffff]
[  408.189170] pci 0000:05:01.0:   bridge window [mem 0x50000000-0x6fffffff 64bit pref]
[  408.189292] pci 0000:05:02.0: PCI bridge to [bus 3a]
[  408.189307] pci 0000:05:02.0:   bridge window [mem 0xcbf00000-0xcbffffff]
[  408.189436] pci 0000:05:04.0: PCI bridge to [bus 3b-6e]
[  408.189..."
1696325,2017-06-07 08:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
1696325,2017-06-07 09:40:18 UTC,apport information
1696325,2019-03-11 08:43:37 UTC,"On ""legacy enumeration"" systems, such as this one the BIOS SMI handler enumerates the PCI bridges before handing off to the OS. The bridges here are the TBT host router bridges so no need for any authorization."
1696325,2017-06-07 09:40:22 UTC,apport information
1696325,2017-06-07 09:40:23 UTC,apport information
1696325,2017-06-07 09:40:24 UTC,apport information
1696325,2017-06-07 09:40:25 UTC,apport information
1696325,2017-06-07 09:40:26 UTC,apport information
1696325,2017-06-07 09:40:27 UTC,apport information
1696325,2017-06-07 09:40:28 UTC,apport information
1696325,2017-06-07 09:40:30 UTC,apport information
1696325,2017-06-07 09:40:32 UTC,apport information
1696325,2017-06-07 09:40:33 UTC,apport information
1696325,2017-06-07 09:40:36 UTC,apport information
1696325,2017-06-07 12:47:59 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1696325,2017-06-08 05:50:59 UTC,I got my laptop and installed Ubuntu a month ago. This issue has been active from the beginning.
1696325,2017-08-18 19:27:41 UTC,Thunderbolt support for PCs is included in v4.13-rc1 and later kernels. Do you have a possibility to try the latest mainline kernel?
1696325,2017-08-18 20:02:16 UTC,"Unfortunately I don't have that laptop anymore. Currently I have Dell
Precision M5520 with Ubuntu 16.04 pre-installed and almost everything is
working excellently with its TB16 dock."
1696325,2018-03-11 13:44:35 UTC,"Hi guys, I have indirect comment, but related to thuderbold support. I have Dell xps 13 and by running on 4.12.12 kernel I get same messages on Dell DA200 UCB-C adapter (provides HDMI and Ethernet and VGA and USB). In didn't get it working yet, but just testing it with latest available kernel on Gentoo system =4.15.7 (release 1)."
1696325,2018-03-11 13:58:24 UTC,I confirm that after upgrade to latest 4.15.7 and few changes to kernel config my adapter DA200 works via USB-C as expected.
1696325,2019-03-07 08:11:05 UTC,I've got the same setup as the original report and the problem still exists on a fully upgrade BIOS and dock firmware (under certain circumstances).
1696325,2019-03-07 08:12:14 UTC,"Forgot to add, this is with Disco,"
1696325,2019-03-07 10:59:42 UTC,"Hi, the BIOS is expected to configure the PCI bridges leading to the TBT controller but it does not seem to do that:"
1696325,2019-03-11 07:36:10 UTC,"I'm not sure how the bridge initialization is supposed to work with TB3 security. But, I would guess that the dock needs to be authorized first before the PCIE bridges can be initialized."
1696325,2017-06-07 09:40:19 UTC,apport information
1696325,2017-06-07 09:40:34 UTC,apport information
1696345,2017-07-21 14:47:14 UTC,Noob question: has this fix been deployed for the general public? The bug still occurs for me on Elementary OS with Chromium and Vivaldi browsers.
1696345,2017-07-23 04:47:49 UTC,"This Problem did affect me at one and for me was linked to Dpkg Was Interrupted Error, Running sudo dpkg --configure -a fixed chrome crashing on open file chooser dialog for me, hopes this information is useful."
1696345,2017-06-07 16:44:09 UTC,Thanks for your report! We're investigating now :)
1696345,2018-03-14 17:17:01 UTC,Same problem in Elementary OS 0.3.2 Freya (64-bit)
1696377,2017-08-09 21:14:27 UTC,"Missed Pike release, untargetting"
1696377,2018-06-09 23:41:00 UTC,"Change abandoned by Tom Barron (<email address hidden>) on branch: master
Review: https://review.openstack.org/471627
Reason: No activity since June last year; feel free to restore, rebase, etc."
1696377,2019-08-08 14:47:36 UTC,closed due to inactivity please feel free to re-open if this is still an issue you are seeing
1696388,2017-06-07 10:33:31 UTC,"When I run xdg-open, here are the processes that get spawned:"
1696388,2017-06-07 10:44:54 UTC,"$ run-mailcap --action=view --debug linux-3.2.89.tar.xz
 - parsing parameter ""linux-3.2.89.tar.xz""
 - file ""linux-3.2.89.tar.xz"" has encoding ""xz""
 - Reading mime.types file ""/home/osomon/.mime.types""...
   could not read ""/home/osomon/.mime.types"" -- No such file or directory
 - Reading mime.types file ""/usr/local/etc/mime.types""...
   could not read ""/usr/local/etc/mime.types"" -- No such file or directory
 - Reading mime.types file ""/usr/share/etc/mime.types""...
   could not read ""/usr/share/etc/mime.types"" -- No such file or directory
 - Reading mime.types file ""/etc/mime.types""...
 - extension ""tar"" maps to mime-type ""application/x-tar""
 - Reading mailcap file ""/home/osomon/.mailcap""...
   could not read ""/home/osomon/.mailcap"" -- No such file or directory
 - Reading mailcap file ""/etc/mailcap""...
 - Reading mailcap file ""/usr/local/etc/mailcap""...
   could not read ""/usr/local/etc/mailcap"" -- No such file or directory
 - Reading mailcap file ""/usr/share/etc/mailcap""...
   could not read ""/usr/share/etc/mailcap"" -- No such file or directory
 - Reading mailcap file ""/usr/etc/mailcap""...
   could not read ""/usr/etc/mailcap"" -- No such file or directory
Processing file ""linux-3.2.89.tar.xz"" of type ""application/x-tar"" (encoding=xz)...
 - decoding ""linux-3.2.89.tar.xz"" as ""/tmp/fileIegizX.2.89.tar""
 - checking mailcap entry ""application/x-tar; /usr/lib/gvfs/gvfsd-archive file=%s; test=test -n ""$DISPLAY""""
 - program to execute: /usr/lib/gvfs/gvfsd-archive file=%s
 - running test: test -n ""$DISPLAY""  (result=0=true)
 - executing: /usr/lib/gvfs/gvfsd-archive file=/tmp/fileIegizX.2.89.tar"
1696388,2017-06-07 11:11:17 UTC,"In a zesty VM, xdg-open runs file-roller, whereas in artful it runs `run-mailcap --action=view`.
xdg-open itself hasn't changed recently though."
1696388,2017-06-07 11:17:12 UTC,"`xdg-mime query filetype linux-3.2.89.tar.xz` returns nothing on artful, whereas it returns ""application/x-xz-compressed-tar"" on zesty, which explains why xdg-open takes a different code path."
1696394,2017-06-07 12:17:49 UTC,"[root@cci06-rally01 database(openstack_admin_LinuxEng)]# rally --debug deployment check
2017-06-07 13:51:41.914 6587 RALLYDEBUG rally.api [-] INFO logs from urllib3 and requests module are hide.
2017-06-07 13:51:41.914 6587 RALLYDEBUG rally.api [-] urllib3 insecure warnings are hidden.
2017-06-07 13:51:41.914 6587 RALLYDEBUG rally.api [-] ERROR log from boto module is hide.
2017-06-07 13:51:41.915 6587 DEBUG oslo_db.api [-] Loading backend 'sqlalchemy' from 'rally.common.db.sqlalchemy.api' _load_backend /root/rally/rally-master/venv/cci06/lib/python3.5/site-packages/oslo_db/api.py:237
/root/rally/rally-master/venv/cci06/lib/python3.5/site-packages/requests/packages/urllib3/connection.py:344: SubjectAltNameWarning: Certificate for cci06-ostctrl-oc.cloud.internal has no `subjectAltName`, falling back to check for a `co)
  SubjectAltNameWarning
/root/rally/rally-master/venv/cci06/lib/python3.5/site-packages/requests/packages/urllib3/connection.py:344: SubjectAltNameWarning: Certificate for cci06-ostctrl-oc.cloud.internal has no `subjectAltName`, falling back to check for a `co)
  SubjectAltNameWarning
/root/rally/rally-master/venv/cci06/lib/python3.5/site-packages/requests/packages/urllib3/connection.py:344: SubjectAltNameWarning: Certificate for cci06-ostctrl-oc.cloud.internal has no `subjectAltName`, falling back to check for a `co)
  SubjectAltNameWarning
--------------------------------------------------------------------------------
Platform openstack:
--------------------------------------------------------------------------------"
1696395,2017-06-09 18:10:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696395,2017-06-07 11:04:48 UTC,"StacktraceTop:
 um_carousel_select_item (self=0x55c78de65520, item=0x0) at um-carousel.c:212
 reload_users (d=0x55c78d8fc440, selected_user=0x55c78dbfaec0) at um-user-panel.c:299
 g_closure_invoke (closure=0x55c78e06b900, return_value=return_value@entry=0x0, n_param_values=2, param_values=param_values@entry=0x7ffdbce75730, invocation_hint=invocation_hint@entry=0x7ffdbce756b0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55c78e0204e0, detail=detail@entry=0, instance=instance@entry=0x55c78dbfadb0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffdbce75730) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffdbce758f0) at ../../../../gobject/gsignal.c:3391"
1696399,2017-06-07 16:02:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696399,2021-01-07 04:03:54 UTC,4.8 EOL
1696405,2017-06-21 11:55:44 UTC,I can confirm this bug in Zim 0.66 running on Windows 10 Pro x64. Zim 0.67 has fixed this. Thanks!
1696406,2017-09-08 18:50:02 UTC,"Something like this also happen in .67, but it's more subtle: when I drop a filename onto a note, wherever in the note I drop it, the link gets added to the bottom of the note."
1696411,2017-08-13 11:55:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696415,2017-11-08 20:30:10 UTC,Upstream GNOME bug fixed.  I've applied the fix to Xenial's NM and tested.  SRU incoming.
1696415,2017-06-14 15:33:50 UTC,"By setting log_level to DEBUG, I could confirm from the logs that there is a miscommunication between dhclient and NetworkManager causing this issue."
1696415,2017-07-04 10:35:31 UTC,"I've closed down on the root cause being the /usr/lib/NetworkManager/nm-dhcp-helper tool. Occasionally, this binary runs, but fails to correctly send the update to NetworkManager. No errors occur when this happens; NetworkManager in debug mode just says ""accepted connection on private socket"" then ""closed connection on private socket"" without any updates happening."
1696415,2017-07-05 15:26:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1696415,2017-07-06 22:02:12 UTC,"Hi Sebastien, thanks for your comment!"
1696415,2017-10-16 21:35:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696415,2017-11-08 21:45:33 UTC,Correction/Addendum to the SRU justification above:
1696415,2017-11-08 21:08:50 UTC,[Impact]
1696415,2017-11-14 22:18:26 UTC,"Hi Ray/Julian,"
1696415,2017-11-14 22:44:10 UTC,Sjors:
1696415,2017-11-16 23:54:33 UTC,"Hello Sjors, or anyone else affected,"
1696415,2017-11-27 20:09:21 UTC,Sorry for the delay - I was away for a week.  I have deployed the packages from -proposed and will  confirm after keeping an eye on DHCP lease renewals for a while.
1696415,2017-11-29 18:22:20 UTC,Version 1.2.6-0ubuntu0.16.04.2 has been deployed here to several machines that were experiencing the bug multiple times per day.  All DHCP renewal requests since deployment have resulted in renewal notifications being successfully delivered to NetworkManager.
1696415,2017-11-30 18:06:53 UTC,There seems to be an autopkgtest failure on s390x which requires investigation.
1696415,2017-11-30 21:50:12 UTC,The autopkgtest failure on s390x is in a test that checks rfkill integration.  s390 kernels do not have CONFIG_RFKILL set.  Behavior change might have something to do with the recent change to s390x autopkgtest from LXC containers to VMs?
1696415,2017-12-06 19:21:16 UTC,Also note that the previous (current) version of network-manager (1.2.6-0ubuntu0.16.04.1) is also failing s390x autopkgtest.
1696415,2017-12-07 18:16:15 UTC,This bug was fixed in the package network-manager - 1.2.6-0ubuntu0.16.04.2
1696415,2017-12-07 18:16:22 UTC,"The verification of the Stable Release Update for network-manager has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1696415,2017-11-14 21:36:35 UTC,Fix uploaded.
1696417,2017-06-09 19:13:02 UTC,"There's a workaround for this,
Run these in this order"
1696417,2017-09-08 22:01:31 UTC,Pushed a patch for option #1 here
1696417,2017-09-06 23:21:27 UTC,But the fix is a bit complicated. I can think of a few option.
1696417,2017-09-06 23:12:40 UTC,"I also ran into this exact same issue. We have mysql as the backend. And the datetime type is not timezone aware. Neither ""--verbose"" and ""--debug"" are effective for the online_data_migrations command as they are not being taken into consideration. I ended up manually printing out the traceback by adding these two lines"
1696417,2017-06-07 16:49:31 UTC,Could you please provide more details about at least the stacktrace ?
1696417,2017-06-27 16:00:02 UTC,"Automatically discovered version mitaka in description. If this is incorrect, please update the description to include 'nova version: ...'"
1696417,2017-06-07 17:10:02 UTC,"There is no stacktrace to provide, the output of command is:"
1696417,2017-08-27 04:18:07 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1696429,2018-01-24 22:26:05 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1430
1696434,2017-06-27 15:24:58 UTC,As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.
1696434,2017-06-21 16:28:11 UTC,"On Wed, Jun 21, 2017 at 04:03:11PM -0000, Amartey Pearson wrote:

> Tested version 1.3.1-2ubuntu0.3 in 16.04.2 successfully.
"
1696434,2017-08-24 19:50:03 UTC,This bug was fixed in the package powerpc-utils - 1.3.2-1ubuntu2~17.04
1696434,2017-06-21 16:03:11 UTC,Tested version 1.3.1-2ubuntu0.3 in 16.04.2 successfully.
1696434,2017-07-04 12:12:25 UTC,"The verification of the Stable Release Update for powerpc-utils has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1696434,2017-07-04 12:12:17 UTC,This bug was fixed in the package powerpc-utils - 1.3.1-2ubuntu0.3
1696434,2017-07-26 14:54:52 UTC,Tested version 1.3.2-1ubuntu2 in 17.04 successfully.
1696434,2017-06-21 15:32:22 UTC,"Amartey, could you please test this package at -proposed archive? They are depending on it to release the package to the official archive."
1696434,2017-06-12 19:40:16 UTC,"------- Comment From <email address hidden> 2017-06-12 15:36 EDT-------
*** Bug 155320 has been marked as a duplicate of this bug. ***"
1696434,2017-06-20 00:14:23 UTC,"Hello bugproxy, or anyone else affected,"
1696434,2017-06-20 00:12:40 UTC,"Hello bugproxy, or anyone else affected,"
1696434,2017-06-19 22:16:53 UTC,This bug was fixed in the package powerpc-utils - 1.3.2-1ubuntu2
1696434,2017-06-19 19:59:40 UTC,You ask for fixing this in 17.04.  Does that mean this is not part of the 1.3.2 release?  We need this fixed in later series first before we can SRU it into 16.04.
1696434,2017-06-08 05:19:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696434,2017-06-08 15:10:55 UTC,"------- Comment From <email address hidden> 2017-06-08 11:05 EDT-------
Can we get the fix into both 16.04 (Xenial) and 17.04 (Zesty) please? Thanks."
1696434,2017-06-09 18:05:00 UTC,I created a new version for this fix. This is version 1.3.1-2ubuntu0.3 and you could see it on my PPA:
1696434,2017-06-12 16:26:33 UTC,"Looking at the diff, it appears you brought in:"
1696434,2017-06-20 00:18:51 UTC,"Hello bugproxy, or anyone else affected,"
1696436,2017-07-17 11:39:28 UTC,This bug was fixed in the package linux-raspi2 - 4.8.0-1043.47
1696440,2017-06-07 15:00:08 UTC,This change was made by a bot.
1696440,2017-06-14 22:14:25 UTC,Is there a fix or workaround for this bug? My update is still freezing.
1696448,2017-06-07 15:08:12 UTC,"Ubuntu's yacas package is currently synced from Debian, so I recommend filing a Debian bug to request this update."
1696448,2017-06-07 20:18:27 UTC,OK - I did that:
1696448,2017-06-07 20:39:58 UTC,Thanks Adam!
1696452,2017-06-07 15:41:48 UTC,"Hi Pavel. This looks like an issue inside the gtk libraries. The older gtk2 libraries could cause hangs and segfaults, but they are now also effectively unmaintained by anyone in the gnome/gtk community. As a non C dev, I don't have the skills to delve into that code base, even if the fixes could be passed back."
1696452,2017-07-20 12:16:49 UTC,"Okay, gtk3 version works ok. Tested it for 3 days and no hangs/crashes at all.
So for history: if you are using terminator from official ubuntu repo on ubuntu 16.04 and have similar problems, just upgrade to gtk3 version from terminator launchpad repo."
1696456,2019-08-22 22:13:32 UTC,"@~smiddy84 As you can see from my comment 2 years ago, this problem has already been solved in HDF View 3. Ubuntu / Debian just didn't update their package since then."
1696456,2019-08-22 10:27:21 UTC,I contacted the HDF Group today and asked for a fix. Perhaps you can do the same:
1696456,2020-05-02 03:43:58 UTC,Still the same issue in Ubuntu 20.04 :(
1696456,2017-06-23 01:52:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696456,2017-06-07 15:10:20 UTC,"With ubuntu shipping HDF libraries version 1.10, the only option is to bump hdfview to version 3 beta."
1696456,2018-04-13 17:50:40 UTC,"Severity of this bug should be raised accordingly, the package is completely useless and only confuses people."
1696471,2018-03-14 12:45:45 UTC,This bug was fixed in the package libvirt - 4.0.0-1ubuntu5
1696471,2018-03-08 16:37:19 UTC,"I pushed the commit upstream after some review, ready to be included in Bionic with the next upload."
1696471,2018-03-07 10:10:04 UTC,"Rule tested, not breaking things - fixing the deny as intended."
1696471,2018-03-07 09:53:34 UTC,"Rule we need is:
  /etc/gss/mech.d/ r,"
1696471,2018-03-07 08:59:21 UTC,"I have seen the same recently, but for without a clear repro I can't upstream.
Also we don't know the impact of that missing yet."
1696471,2018-03-07 10:20:09 UTC,Submitted as https://www.redhat.com/archives/libvir-list/2018-March/msg00328.html
1696471,2018-03-02 15:38:45 UTC,"Sorry for the delay, I finally found some time to get back to this. This is still reproducible on current Ubuntu 17.10:"
1696471,2017-11-06 07:25:10 UTC,"Yeah, thanks Martin, if that is the case I agree to this plan of action."
1696471,2017-11-06 07:08:46 UTC,"This still happens all the time, also in 17.10, reopening. I need to find some time to create a reproducer that doesn't involve the Cockpit tests."
1696471,2017-11-06 04:17:34 UTC,[Expired for libvirt (Ubuntu Xenial) because there has been no activity for 60 days.]
1696471,2017-11-06 04:17:33 UTC,[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]
1696471,2018-03-02 15:42:00 UTC,"Forgot to mention: I didn't change any libvirt config files, in particular not the ones you mentioned:"
1696471,2017-09-06 11:35:27 UTC,"Hi Martin,
I'm currently trying to clean up bugs that were missed or got no update.
First I have to beg your pardon for missing it in the first place."
1696476,2019-07-19 21:30:36 UTC,"Hi,  If you'd like to test something out, you can look at some of the other EC2 Look Alike classes, like AliYun."
1696476,2019-09-18 04:17:35 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1696476,2019-09-18 13:44:11 UTC,"@Marcin,
I've attached a branch, would you be able to test that?"
1696476,2019-09-19 14:28:55 UTC,"Wow, that's unexpected:-)
I'm out of office until wednesday, will test it when I get back."
1696476,2019-10-08 16:16:14 UTC,"@Marcin,
Are you able to check?
I'm pretty sure I've implemented the code correctly, but it would sure be nice if we had someone verify that before landing it."
1696476,2019-10-09 09:11:41 UTC,"Hi,
yes, from what I've tested, it detects Ec2 datasource correctly."
1696476,2019-10-11 14:54:52 UTC,"This bug is fixed with commit 7d5d34f3 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=7d5d34f3"
1696476,2019-12-19 23:00:00 UTC,"This bug is believed to be fixed in cloud-init in version 19.2-57. If this is still a problem for you, please make a comment and set the state back to New"
1696486,2017-06-07 16:52:03 UTC,This is possible if you use the website screenshot button (gnome-web-photo must be installed in order for it to work).
1696499,2018-01-25 09:15:22 UTC,"Hey,
Upgraded to Ubuntu 17.10 and had to do the workaround again for"
1696499,2017-06-08 09:31:50 UTC,"Current workaround:
Compile and build from here: http://www.linuxfromscratch.org/blfs/view/cvs/basicnet/dhcp.html"
1696499,2017-07-17 13:45:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696499,2017-07-21 07:25:50 UTC,"Workaround provided does not seem to work for me. It seems the dhclient binary only fails with Seg fault when it is at /sbin/dhclient, when it is moved to /usr/sbin/dhclient it works fine from command line. But this made nm-dhclient-helper to fail."
1696499,2017-07-21 09:47:15 UTC,Inspection of the core dump and some testing proves the Segmentation fault error is caused by denied permission to read /proc/self/cmdline. Moving the executable anywhere else the problem would simply disappear.
1696499,2017-07-21 09:51:08 UTC,"If you are using network-manager, remove the following modules from the enforcing mode should allow automatic DHCP from network-manager:"
1696499,2017-10-06 00:38:50 UTC,"The workaround was certainly helpful, but is there a more elegant solution? I had similar apparmor problem with cupsd (bug 1706052), which I worked around using the solution here, which eventually led to a fix via editing the cups apparmor profile."
1696499,2017-10-06 01:21:16 UTC,"Actually, I was able to connect with the exact same fix I used for the cups issue:"
1696499,2017-10-08 04:22:51 UTC,Works on aa-enforce.
1696501,2017-06-09 18:25:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472773"
1696501,2019-03-05 07:38:52 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/472773"
1696512,2019-01-11 13:51:36 UTC,"Whether it nukes data or not, MAAS is taking something down that it did not create as a side effect of another action. At the very least there should be a confirmation required from the user acknowledging that it's going to happen and/or a way to opt-out of the commissioning of existing VMs."
1696512,2017-10-30 20:05:34 UTC,"So, commissioning a box does nothing at all to the disk on the machine?  It does reboot the machine, which is far from ideal if you don't know that's going to happen."
1696512,2017-10-30 18:08:34 UTC,No data will be nuked. We do not auto deploy the machines! The machine will just be commissioned to gather the VM's information.
1696512,2017-10-30 17:11:46 UTC,"If that's by design, we should re-design it. It's poor UX. If you add a virsh POD that has existing KVMs it should error, not nuke data. At the very least there should be an exceptional confirmation where we warn them that there are existing KVMs and the data will be nuked."
1696512,2017-06-27 14:33:30 UTC,"Hi Peter,"
1696512,2019-12-18 14:51:35 UTC,Was this bug removed from development as the last update seems to imply?
1696523,2017-06-16 13:38:55 UTC,In which 'view' your drag&drog stops working?
1696523,2017-06-15 10:42:21 UTC,I'll mark as confirmed but unlikely to be addressed without further information.
1696523,2017-06-15 01:03:58 UTC,"Huh, I am also affected by this. Drag&Drop never actually worked for me, but now I've opened Files and it seems to be working. I'll keep an eye on it and report if have any idea on what causes this."
1696523,2017-06-09 10:05:42 UTC,Any information you can give as to the circumstances this occurs would help to confirm it.
1696545,2018-09-14 10:58:31 UTC,Full Python 3 support has now landed in trunk.
1696545,2019-11-14 08:55:33 UTC,"The soon EOL for Python2 would warrant a new bzr release with Python 3 support I think. While bzr itself clearly is in maintenance mode and there are not many new projects using it it is still out there, and it will be needed to access bzr repositories in the future."
1696545,2019-11-14 14:54:20 UTC,"There is a friendly fork of Bazaar called Breezy (https://Launchpad.net/brz), which supports Python 3 and can access bzr repositories."
1696545,2019-11-14 15:01:26 UTC,"Comment #1 refers to Breezy, not Bazaar. Bazaar doesn't have Python 3 support, not even unreleased."
1696546,2017-06-07 19:41:32 UTC,The file to source for zsh is .zshrc not .bashrc.
1696546,2018-08-12 15:11:19 UTC,Thanks!  Fix committed.
1696551,2017-07-01 11:53:34 UTC,I have similar problem with skypeforlinux profile I am developing.
1696551,2017-07-02 13:14:55 UTC,I solved my problem using:
1696552,2018-01-26 20:59:06 UTC,I found myself wanting to do this again and tried this:
1696557,2017-07-11 04:58:59 UTC,"This is a potential for fixing in the 2.2 series, but as it hasn't come up high enough to actually warrant direct investigation yet."
1696557,2018-03-22 06:13:59 UTC,We will not be fixing this in 2.2 as there are no further point releases planned in this series.
1696558,2017-06-09 17:12:24 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1696558,2017-06-12 19:41:13 UTC,"This bug is not to track a problem, it's to change a default kernel option to a more secure setting already in use by other distributions, such as upstream Debian."
1696558,2019-08-16 09:35:55 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-August/103163.html
1696558,2019-09-05 15:00:58 UTC,I don't think that we should make this change. I explained my reasoning in this email:
1696561,2017-06-10 13:09:41 UTC,"This is fixed in the source, just not released yet."
1696563,2017-06-13 05:15:58 UTC,"I have the feeling we are probably checking from the client what is available, but ultimately the download to the target machine is done from the target machine. Just because your laptop can see streams.canonical.com doesn't mean it is accessible out from the target machine."
1696563,2017-06-13 14:02:33 UTC,"There's actually a different failure mode if the target machine can't download from streams.c.c, I was going to open a second bug about that, though now I need to set something up to replicate it and capture output again."
1696567,2019-01-31 05:34:59 UTC,"@LaMont
Any chance you could bump those mirrors to 1 Mbps so I can propose this change?   Thanks!"
1696579,2019-04-16 21:30:13 UTC,I too would really like this
1696579,2019-04-16 21:34:29 UTC,This would also help the Ubuntu SRU team who has to frequently reject uploads where the uploader uploaded a package two times because they wanted to get in one more fix.
1696591,2018-01-23 18:47:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696594,2017-06-07 22:41:09 UTC,"StacktraceTop:
 gtk_header_bar_pack (bar=0x0, widget=0x5602138b8180, pack_type=GTK_PACK_END) at ././gtk/gtkheaderbar.c:1696
 font_view_application_do_open (self=0x5602136581a0, file=0x5602137cd300, face_index=0) at font-view.c:555
 query_info_ready_cb (object=0x5602137cd300, res=<optimized out>, user_data=0x5602136581a0) at font-view.c:746
 g_task_return_now (task=0x560213674ae0) at ../../../../gio/gtask.c:1145
 complete_in_idle_cb (task=0x560213674ae0) at ../../../../gio/gtask.c:1159"
1696594,2020-05-09 09:46:31 UTC,"I appreciate some considerable time has passed since this bug was reported.
Does it still occur with newer versions of the font viewer?
Was there (if you recall) a particular font file which triggered this?"
1696594,2020-05-12 02:50:32 UTC,"No, I don’t think this is still reproducible as it was. gnome-font-viewer is still rough around the edges, but not as egregiously as in 2017. Will close."
1696604,2017-08-29 09:15:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696608,2017-06-09 13:10:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696611,2018-05-08 18:10:38 UTC,This change was made by a bot.
1696611,2021-01-07 04:04:02 UTC,4.8 EOL
1696623,2017-07-18 20:51:10 UTC,"Still couldn't but I didn't forget, pretty busy and away on business travel lately"
1696623,2017-07-11 15:45:36 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1696623,2017-06-25 13:29:28 UTC,"Hi guys,"
1696623,2017-06-09 19:01:56 UTC,"Hi Joseph,"
1696623,2017-06-09 15:51:29 UTC,"I upgraded my Xenial test system to linux-virtual-hwe-16.04-edge and with that it is working fine.
So we have a good testcase (thanks Rolando) a crash dmesg on the issue and confirmed that it is solved in a newer kernel."
1696623,2017-06-09 15:45:13 UTC,"Hi,
thank you for your report - nicely written as well!"
1696623,2017-06-09 17:10:00 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1696625,2017-09-18 19:35:20 UTC,"I can reproduce this behaviour once the screensaver (or whatever it is that fades out the colour and then turns the screen black) kicks in. After unlocking the lockscreen nightlight is off but the switch is still turned to ""on"". The warmer colours are reset once the screensaver activates.
If I reset (reinitialize?) my Display-config by attaching an external Display I get back Night light.
I'm also running budgie linux
4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.04
DISTRIB_CODENAME=zesty
DISTRIB_DESCRIPTION=""Ubuntu 17.04"""
1696625,2018-02-08 13:06:03 UTC,known upstream issue - https://github.com/budgie-desktop/budgie-desktop/issues/1284
1696634,2017-06-08 05:40:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696634,2021-01-07 04:04:08 UTC,4.8 EOL
1696650,2017-06-09 13:02:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696655,2017-06-08 15:05:16 UTC,Does this bug go away if you boot back into the kernel prior to yesterday?
1696655,2017-06-08 15:15:34 UTC,This change was made by a bot.
1696665,2017-06-08 15:15:16 UTC,This change was made by a bot.
1696665,2017-06-08 15:36:15 UTC,"I tried the Ubuntu mainline builds. The bug happens on mainline 4.10.12 (and 13, and 15, and 17..), but not on 4.10.11. This tallies well with the Ubuntu versions, where 11 is before -22, and 12 is after."
1696665,2017-06-08 18:57:55 UTC,Bisecting. Trying a single boot only because it appears 100% reproducible. Famous last words.
1696665,2017-06-08 20:22:39 UTC,"It's somewhere in:
* e8f09b159634 - (refs/bisect/bad) drm/fb-helper: Allow var->x/yres(_virtual) < fb->width/height again (3 weeks ago) <Michel Dänzer>
* 62dd80f54582 - drm/etnaviv: fix missing unlock on error in etnaviv_gpu_submit() (3 weeks ago) <Wei Yongjun>
* 1611347ef50a - (HEAD) drm/nouveau: initial support (display-only) for GP107 (3 weeks ago) <Ben Skeggs>
* e0cc39c8a55c - (refs/bisect/good-e0cc39c8a55cd1cb51260678910d9bb1042cf5cd) drm/nouveau/kms/nv50: fix double dma_fence_put() when destroying plane state (3 weeks ago) <Ben Skeggs>"
1696672,2017-06-08 13:22:28 UTC,"You must at least attach logfile OpenrailsLog.txt here, else this is quite a mysterious bug report."
1696672,2017-06-09 13:34:09 UTC,"Sorry I had logging turned off.
Find log attached"
1696672,2017-06-12 07:41:09 UTC,There is a problem with one of the consist files of your AI train. Either it is missing or more probably it has an incorrect format.
1696701,2017-10-12 20:28:26 UTC,"Reviewed:  https://review.openstack.org/479844
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=0aefe6ab27a7a46220064b852108c67c823a9f0e
Submitter: Jenkins
Branch:    master"
1696701,2017-07-03 14:34:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/479844"
1696701,2017-06-30 15:20:35 UTC,"might have something to do with this
https://github.com/openstack/openstack-ansible-os_nova/blob/28face1a201946f9339387a3799b214a11f4c25e/vars/main.yml#L52-L62"
1696701,2017-06-30 11:09:41 UTC,"ok so i made some changes to these files. however i seem to be missing something for the following step wich throws the following error
TASK [os_nova : Create TEMP run dir
fatal: [aio1_nova_console_container-5f0e7062]: FAILED! => {
    ""failed"": true,
    ""msg"": ""The conditional check 'inventory_hostname in groups[item.value.group]' failed. The error was: error while evaluating conditional (inventory_hostname in groups[item.value.group]): 'item' is undefined\n\nThe error appears to have been in '/etc/ansible/roles/os_nova/tasks/nova_init_systemd.yml': line 16, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Create TEMP run dir\n  ^ here\n""
}"
1696701,2017-06-08 11:31:27 UTC,"As a simple test if the configuration you made is usable, you can use larsks's ""novaconsole"": https://github.com/larsks/novaconsole/"
1696701,2017-06-20 09:19:55 UTC,"FWIW, I think the code needs to go at: https://github.com/openstack/openstack-ansible-os_nova/blob/4d347885432f5c99b439157f71b2aba94b0ebfac/defaults/main.yml#L219-L237"
1696701,2017-06-22 08:45:08 UTC,"Markus you are right!
Next to that we need to create an entry in Service name-group mapping
https://github.com/openstack/openstack-ansible-os_nova/blob/4d347885432f5c99b439157f71b2aba94b0ebfac/defaults/main.yml#L428-L470 this creates the needed systemd file"
1696701,2017-06-08 11:29:15 UTC,"Two services need to be configured:
* nova-serialproxy  (on controller node)
* nova-compute      (on compute nodes)"
1696701,2017-06-13 16:17:21 UTC,"I've tagged this bug as low hanging fruit, as many implementation details are expressed here."
1696708,2017-06-09 12:11:33 UTC,"This only happened in the past with changed code, that is imported by a main script, if both are open in IDE."
1696709,2017-06-08 10:50:57 UTC,Oh!   This is my environment:
1696709,2018-08-06 13:02:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696715,2017-07-18 11:31:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484729"
1696733,2017-06-12 04:36:14 UTC,Could someone take a look at this bug? It happens again http://logs.openstack.org/16/462416/7/check/gate-os-brick-pep8-ubuntu-xenial/d692de6/console.html.gz
1696746,2020-11-16 18:05:28 UTC,"slirp (i.e. user networking) has been moved to a separate project... does this problem still persist with the latest version of QEMU? If so, could you please report it to the libslirp project instead:"
1696746,2021-01-16 04:17:49 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1696759,2017-06-09 15:20:29 UTC,Reassigning to the Neutron project as the notification is emitted by it.
1696759,2017-06-09 16:20:28 UTC,Can you test this on master?  I believe the message should now contain 'original_subnet' and 'subnet' fields.
1696759,2017-06-13 16:13:43 UTC,"Hi Brian.
A large part of the issue is that some messages are not posted at all (as described in issue text), some have event_type ""subnet.update.start"" and the rest have event_type ""subnet.update.end"". This is a larger problem than placement of fields inside the message.
Is this also fixed on master?
Thanks."
1696759,2017-06-19 10:38:14 UTC,Do you have something else taking notifications off of the queue?
1696760,2017-07-12 12:52:03 UTC,"Hello,"
1696760,2017-07-18 14:37:01 UTC,"Since the bug is not reproducible in 3.2.4.0, I think the bug can be closed.
In Contrail 3.2.3.0 version, route-targets were not exported and this is why ping was not working."
1696760,2017-07-11 08:37:10 UTC,What is the version of Contrail?
1696760,2017-07-12 14:34:10 UTC,"Hello again,"
1696765,2017-06-26 16:35:56 UTC,"On diff from bzr210 and bzr212, ""--bind"" uses ""="" when it should use "":"""
1696765,2017-06-26 16:54:21 UTC,"--bind actually uses =, the docs are wrong, see https://github.com/juju/docs/issues/1931"
1696766,2018-01-01 06:33:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696772,2017-06-08 15:02:12 UTC,Simply removing 'LOG.info('privsep daemon starting')' fixes the issue for me
1696772,2017-06-08 15:53:48 UTC,Seems that the bug is not present in the latest versions of the libraries
1696772,2017-08-22 15:19:08 UTC,Actually I'm still getting it on the freash install with oslo.privsep==0.22
1696773,2017-06-08 14:39:15 UTC,You will need to apply the patch from https://bugs.launchpad.net/qemu/+bug/1696353 to run this sample app on current master.
1696773,2018-09-05 18:24:27 UTC,This bug is mentioned in this account from Cloudflare of porting their software stack to arm64:
1696773,2019-07-23 12:07:27 UTC,The 'qemucrash' test case from this bug still crashes as of current head-of-git (4.1 rc1).
1696773,2019-07-25 13:23:04 UTC,"The 'qemucrash' test case problem seems to be because we were incorrectly implementing 'sigaltstack' as setting a process-wide signal stack. This is incorrect, as sigaltstack stacks are supposed to be per-thread, and the Go runtime relies on this. I've just sent a patch which seems to me to fix the qemucrash test case, at least:"
1696773,2019-07-29 09:26:32 UTC,"The sigaltstack fix is now in master (commit 5bfce0b74fbd5d530) and at least in my test environment this also fixes the ""can't build hello.go reliably"" example. So I'm marking this as 'fix committed'. If there are still problems with running Go binaries, these are likely to be independent bugs, so please open fresh LP issues for them."
1696773,2019-07-29 14:08:59 UTC,Note that this fix will be in the upcoming 4.1 release.
1696773,2019-07-23 08:48:39 UTC,Observed the same here... (details of the environment at the end of the post)
1696777,2017-06-08 14:47:32 UTC,Cleaned versions of the files that contained sensitive data have been uploaded.
1696780,2018-07-31 19:46:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587610"
1696780,2019-08-27 05:26:54 UTC,"Change abandoned by Rajat Dhasmana (<email address hidden>) on branch: master
Review: https://review.opendev.org/587610
Reason: New implementation
https://review.opendev.org/#/c/678523/"
1696780,2018-01-12 19:07:52 UTC,Unassigning due to no activity for > 6 months.
1696780,2017-06-09 00:51:26 UTC,"Hey, Eric, do we already have any command options that can accept multi values with the input of --key value1 --key value2?"
1696780,2017-06-09 10:32:31 UTC,"The argument parser we are using only restricts to 1 instance on positional arguments, and all optional arguments can be duplicated and the result will not be the expected one, but this is not limited to just this command but to *ALL* our commands."
1696780,2017-06-08 15:19:51 UTC,$ cinder --debug list --filters size=2 name=test1
1696789,2019-08-21 13:17:34 UTC,"The process for reformating OSDs has changed significantly in the charms since this bug was raised.  If the issue persists, please re-raise this bug.  Thank you."
1696790,2017-06-09 09:02:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696790,2018-08-11 16:26:55 UTC,Looks like you are not running as a superuser?
1696791,2017-09-27 20:04:53 UTC,patch to fix this: https://review.openstack.org/#/c/359061/
1696795,2017-06-14 07:18:41 UTC,"Hi all,"
1696800,2017-06-09 14:13:55 UTC,"Thanks Lienhart for the report, I must admit I don't know the backgrounds what might have happened here in regard to the packaging that was referred to in the discussions of the issue you linked."
1696800,2017-06-09 20:43:00 UTC,The failure appears to be due to the incomplete implementation of seek() -- missing the optional 'whence' argument -- in python-s3transfer's ReadFileChunk method.
1696800,2017-06-12 08:51:32 UTC,"Hello Kamal,"
1696800,2017-06-12 16:45:31 UTC,Proposed fix to upstream: https://github.com/boto/s3transfer/pull/88
1696800,2017-12-11 15:49:57 UTC,"This is still hanging on the GH review since ~a month.
@Kamal are you still driving this actively or just waiting on upstream in this case?"
1696800,2017-12-11 17:14:43 UTC,"@Christian, indeed I'm also just waiting on upstream.  I've just added another comment to the github PR to ping the maintainer, kyleknap."
1696800,2020-03-11 02:16:21 UTC,I think this open bug has the same root cause https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1711737
1696800,2017-06-09 18:12:05 UTC,This regression occurs in Xenial/Yakkety (1.11.13-1ubuntu1~16.*.0) and also in Zesty/Artful (1.11.44-1):
1696805,2017-06-08 22:42:05 UTC,"The same situation exists on a different computer- a 2009 Clevo MT570TU running Linux Mint 18.1. Gmail logon allows input of the username, but does not go to the password entry page/window."
1696805,2017-06-08 17:39:14 UTC,"Update:  I was able to log into a gmail account by creating a new account.  After logging out of the new account, I called up the gmail logon page, and this time the gmail account chooser came up, in which I was able to select the previous account.  Gmail then took me to the password field, where I was able to enter the password and logon to the account."
1696817,2017-06-13 05:35:44 UTC,"The problem probably stems from not letting you see other people's credentials, even though we let you use them for a given model. (eg, you're not allowed to see the credentials of the controller model, as you weren't the creator, but I think if you're superuser you should have access to those credentials, I think. Probably needs discussion)
I agree that you should certainly be able to get cloud/region information, etc."
1696825,2021-02-12 21:49:36 UTC,I have been looking at Overdrive issues and wished there was a command line tool to send API requests to Overdrive and view the response. Then I found this LP bug. I think it would be helpful to include this testing tool in the Evergreen support-scripts directory.
1696832,2017-06-09 00:35:19 UTC,What would this do? How would we translate a card's status to a bug status?
1696832,2017-06-23 13:42:36 UTC,This will allow teams to aggerate their launchpad bugs in trello.
1696832,2017-06-23 13:44:46 UTC,"As part of our team automation we are writting a bridge to ""trello-fy"" bugs and add them to our private boards. At the moment we are thinking to use commeents with full card url, and a tag with the card-id. However, it would be best if there were remote bug trackers available of type trello."
1696832,2017-06-23 13:52:33 UTC,The Kernel Team would be very interested in such capability.
1696832,2017-06-23 14:46:17 UTC,+1.  And in case it's of any help:  https://code.launchpad.net/~willcooke/+junk/trelloscripts
1696832,2017-08-23 04:17:48 UTC,[Expired for Launchpad itself because there has been no activity for 60 days.]
1696842,2017-06-08 19:44:23 UTC,"Forgot to mention, the nvidia blob(381) was installed from:
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa"
1696848,2017-12-18 09:24:09 UTC,"Reviewed:  https://review.openstack.org/519659
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a2653ac0d0ffd100ed6a26ed1901ad610c1b38bb
Submitter: Zuul
Branch:    stable/pike"
1696848,2017-06-10 13:27:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472933"
1696848,2017-11-14 11:58:40 UTC,"Reviewed:  https://review.openstack.org/472933
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c91ee68d493e8c813f4dcc4e46b1794a50f69f32
Submitter: Zuul
Branch:    master"
1696848,2017-11-14 14:56:32 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/519659"
1696854,2017-07-08 12:28:52 UTC,I agree and can confirm that this is how it works at the moment in Pinta 1.6 and latest 1.7 dev build
1696855,2017-06-12 22:08:23 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/473611"
1696855,2017-06-14 02:20:10 UTC,"Reviewed:  https://review.openstack.org/473611
Committed: https://git.openstack.org/cgit/openstack/oslo.log/commit/?id=527a76e4e33a980c925315dc7700afcb060c365c
Submitter: Jenkins
Branch:    master"
1696855,2018-01-22 14:49:08 UTC,Is this still a problem after the change in #2?
1696857,2018-05-23 06:13:11 UTC,Duplicate with https://bugs.launchpad.net/cinder/+bug/1754760
1696862,2017-09-19 10:14:59 UTC,"Change abandoned by Spyros Trigazis (strigazi) (<email address hidden>) on branch: master
Review: https://review.openstack.org/472701
Reason: Merged https://review.openstack.org/#/c/472721/"
1696862,2017-09-19 10:15:04 UTC,"Change abandoned by Spyros Trigazis (strigazi) (<email address hidden>) on branch: master
Review: https://review.openstack.org/472708
Reason: Merged https://review.openstack.org/#/c/472721/"
1696862,2017-06-16 13:05:26 UTC,"Reviewed:  https://review.openstack.org/472721
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=1e0785c32089229a65f0a3d469f899440d7af2a9
Submitter: Jenkins
Branch:    master"
1696862,2017-09-19 10:14:29 UTC,"Change abandoned by Spyros Trigazis (strigazi) (<email address hidden>) on branch: master
Review: https://review.openstack.org/472697
Reason: Merged https://review.openstack.org/#/c/472721/"
1696862,2017-06-09 15:03:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472721"
1696866,2019-10-04 08:52:04 UTC,This issue was fixed in the openstack/cinder 14.0.2 release.
1696866,2019-09-27 09:03:25 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1696866,2019-09-05 00:02:57 UTC,"Reviewed:  https://review.opendev.org/678601
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=88a87b2d4892fd8bdd3b80d1385775c5b044c368
Submitter: Zuul
Branch:    stable/stein"
1696866,2019-08-26 15:43:46 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/678601"
1696866,2019-08-23 20:27:12 UTC,"Reviewed:  https://review.opendev.org/677524
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=fddb9b7962ab2d4f3b6f57faef1c090b097b60c6
Submitter: Zuul
Branch:    master"
1696866,2017-06-23 20:46:07 UTC,Confirmed that this fixes the tripleo use case.
1696866,2017-06-23 20:42:46 UTC,"Change abandoned by Ben Nemec (<email address hidden>) on branch: master
Review: https://review.openstack.org/472455
Reason: Cinder changed the type of the opt back so this is no longer necessary."
1696866,2018-01-12 19:04:44 UTC,Unassigning due to no activity for > 6 months.
1696866,2017-06-23 16:18:49 UTC,"> I think the correct fix is for cinder to stop assuming the IP is ok to just concatenate with the port, example https://github.com/openstack/cinder/blob/a55a6b5c717c0802288ab802a8fbff287a4b6b66/cinder/volume/targets/scst.py#L233
"
1696866,2017-06-15 17:09:28 UTC,"I think the correct fix is for cinder to stop assuming the IP is ok to just concatenate with the port, example https://github.com/openstack/cinder/blob/a55a6b5c717c0802288ab802a8fbff287a4b6b66/cinder/volume/targets/scst.py#L233"
1696866,2017-06-15 15:16:32 UTC,Actually sounds like oslo.config needs to be updated to handle IPv6 addressing to me.
1696866,2017-06-15 15:04:19 UTC,"I did some more digging yesterday but concluded that this is beyond my ability to debug in a reasonable timeframe.  I no longer think os-brick is the problem though - it looks like the data passed in to os-brick is already bad, so I think it's something in Cinder or Nova that is not correctly handling the ipv6 iscsi address.  I'm going to add both projects to this bug and let them determine who needs to fix what."
1696866,2017-06-14 15:51:15 UTC,"Okay, if I un-bracket the IP then cinder-volume works, but the volume can't be attached to the nova instance.  I've attached the nova-compute log from the attempted boot."
1696866,2017-06-09 16:37:18 UTC,"Change abandoned by Ben Nemec (<email address hidden>) on branch: master
Review: https://review.openstack.org/472455
Reason: I don't think this actually works.  We need the brackets.  Will have to fix oslo/netaddr/socket to get this working."
1696866,2017-06-08 22:03:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/472455"
1696866,2017-06-23 16:40:38 UTC,"I'll doublecheck, but I believe that will fix the problem too.  It leaves us with the mismatch of having to put a bracketed URI in an option named _ip_address, but that's pretty far down my list of things to worry about. :-)"
1696866,2017-06-23 16:17:27 UTC,Was this fixed by this change?
1696875,2019-05-16 16:01:58 UTC,Fixed with change Ib1681fcab1e9428f4816d2a3a89b1aaea4366475
1696876,2017-06-08 23:47:43 UTC,"Is anywhere promised that there is a Linux driver/free software driver for this printer? If yes, where?"
1696876,2017-06-09 14:00:34 UTC,"@wgrant
I have a Epson Stylus photo 1390 printer and I installed CUPS and cups-driver-gutenprint, but no PPD driver is available for this printer.
The official Windows (x64 & X86) and Mac OS X driver is attached below.
http://www.epson.cn/resource/Download/Service/driver/Inkjet/SP1390/SP1390_x64_651CN_s.exe
http://www.epson.cn/resource/Download/Service/driver/Inkjet/SP1390/SP1390_W2K_651CN_s.exe
http://www.epson.cn/store/downloads/200987102327.dmg
Not sure how to extract the correct PPD file for this printer. Need help here."
1696876,2017-06-09 14:02:07 UTC,"Maybe we can extract the PPD driver from Mac OSX driver, but I don`t know how. Need some help here."
1696876,2017-06-09 14:35:30 UTC,"Extracting PPDs from Windows/Mac drivers does not work for non-PostScript printers, as the drivers also contain proprietary filters."
1696876,2017-06-09 14:36:26 UTC,We cannot fix anything here as the problem is simply a printer model without driver support under Linux.
1696885,2021-02-21 01:17:18 UTC,"GNOME now supports remote desktop sharing in Wayland, but it isn't enabled in Ubuntu. Apparently one of the prerequisites for being able to enable it in Ubuntu was recompiling mutter with support for it, and that has now been done in Hirsute. What else needs to be done in Hirsute to make this work?"
1696886,2017-07-25 22:16:34 UTC,This bug was fixed in the package openjdk-8 - 8u131-b11-2ubuntu1.17.04.2
1696886,2017-06-12 17:46:45 UTC,"I've uploaded this to artful, let's do an end to end test of the package hook and ensure everything appears in the Ubuntu Error Tracker before SRU'ing these changes."
1696886,2017-06-13 03:46:57 UTC,Verified to be working. The HotspotError is attached to the reports.
1696886,2017-06-13 16:38:18 UTC,It's not a big deal but I noticed the OOPSes contain the same tag multiple times:
1696886,2017-06-13 19:44:23 UTC,"The duplication was probably caused by myself while I was simultaneous running apport-cli, apport-noui and update-notifier-crash - for some reason my system does not set the systemd user graphical-session, so I ended running stuff manually and a duplication occurred somewhere along that."
1696886,2017-06-14 05:43:17 UTC,This bug was fixed in the package openjdk-8 - 8u131-b11-2ubuntu1
1696886,2017-06-21 17:12:36 UTC,Keep in mind when SRU'ing this we'll need to modify whoopsie to allow the large attachment.
1696886,2017-07-25 22:16:35 UTC,This bug was fixed in the package openjdk-8 - 8u131-b11-2ubuntu1.16.04.2
1696895,2018-02-07 08:32:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696903,2017-06-09 12:51:55 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1696905,2017-07-07 03:54:33 UTC,We suspect that the connection pool implementation within oslo_messaging library is not greenthread aware.
1696905,2017-06-16 12:43:52 UTC,It has been further identified that the oslo_messaging is stuck in wait_condition().
1696905,2017-10-10 18:02:50 UTC,Hi - sorry for the inexcusably late reply :(
1696905,2017-06-12 15:52:34 UTC,"Hi Sanchit,"
1696905,2017-10-09 10:18:03 UTC,We are facing the same issue. Swift-Proxy requests hung at ceilometer middleware.
1696905,2017-06-16 12:43:29 UTC,"Hi Ken,"
1696905,2017-10-11 11:04:55 UTC,"Hi Ken,"
1696911,2017-06-12 08:00:13 UTC,I've seen this again now:
1696913,2017-06-22 13:09:13 UTC,https://github.com/juju/juju/pull/7545
1696936,2017-06-09 08:31:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1696936,2019-03-01 14:38:16 UTC,I also experience this issue on 18.04.1
1696936,2019-03-01 16:24:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696936,2020-01-22 14:28:57 UTC,I also experience this issue on 19.10
1696942,2017-06-23 17:06:22 UTC,"Today 24.06.2017, we hit it again. MySQL crashed with the same bug:"
1696942,2018-01-25 08:48:24 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3709
1696945,2017-06-09 09:16:14 UTC,Although... if we fixed just this bug then it would have inconsistent padding compare to buttons on the right side.
1696951,2018-10-03 10:35:55 UTC,"This is less noisy than it was following https://code.launchpad.net/~cjwatson/launchpad-buildd/faster-cleanup/+merge/344938, but it's probably still possible to do better."
1696959,2017-06-09 12:51:00 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1696973,2017-06-10 11:14:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696978,2017-06-09 11:57:34 UTC,"When attaching gdb to the demo server, http://paste.ubuntu.com/24801119/ is the backtrace."
1696978,2017-06-12 03:38:04 UTC,"Sounds serious, till proven otherwise..."
1696978,2017-06-12 03:52:53 UTC,I can't reproduce the bug using either the latest release or building fresh from lp:mir.
1696978,2017-06-12 07:27:08 UTC,The essential step here is stopping lightdm. After which it seems Mir fails to restart compositing when the VT switches back. This scenario is low priority.
1696989,2017-06-09 15:34:50 UTC,"Hi,"
1696989,2018-12-10 04:30:38 UTC,"We never had any other report of this so it's not a generic issue in libpam-cgfs, this suggests a debconf issue, so closing the lxcfs task."
1696989,2017-06-09 19:20:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696989,2017-06-09 15:23:07 UTC,"Hi,"
1696992,2021-01-13 13:53:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696995,2020-07-06 16:07:52 UTC,"I think this needs to be scoped to a specific use case or use cases before it is actionable, so taking it out of the Triaged state."
1696995,2021-02-23 16:57:24 UTC,Setting it to triaged.  It's a wish-list item (new feature request) so does not need to sit at the 'new' state.
1696997,2017-06-09 14:12:47 UTC,You only allocated 4 gb of disk space and the minimum is 6 or 7 gb.  The installer should have stopped you and told you that and not let you proceed.
1696997,2018-06-20 15:42:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1696998,2017-06-12 06:40:59 UTC,"Hello Experts,"
1696998,2017-06-22 17:22:15 UTC,"Hello,"
1697001,2017-06-09 14:14:36 UTC,"The following patches were skipped as they already were applied:
* CVE-2017-9242
  - pv6: fix out of bound writes in __ip6_append_data()
* CVE-2017-9074
  - ipv6: Prevent overrun when parsing v6 header options
* CVE-2017-9075
  - sctp: do not inherit ipv6_{mc|ac|fl}_list from parent
* CVE-2017-9076 and CVE-2017-9077
  - ipv6/dccp: do not inherit ipv6_mc_list from parent
* CVE-2017-8890
  - dccp/tcp: do not inherit mc_list from parent"
1697001,2017-07-24 07:59:49 UTC,This bug was fixed in the package linux - 4.4.0-87.110
1697003,2018-12-06 23:20:17 UTC,"FWIW, there appear to be some buggy behavior when there are multiple uib-dropdown divs on the same page: https://github.com/angular-ui/bootstrap/issues/6335"
1697003,2020-02-06 16:31:04 UTC,"I tested out adding the keyboard nav to the menus on the record detail interface in the angularjs interface, and I can confirm the issue."
1697009,2017-10-26 07:36:21 UTC,"Actually this would be good for any part of ""git ubuntu submit"" to open up a ppa, push the package to build there and and make an auto-update to the MP linking to said ppa.
Doesn't have to be Bileto, but all-arch would be great."
1697009,2017-12-07 10:10:48 UTC,"Bileto is more and mor bit-rotting.
But opening up a ppa and pushing there would still be great."
1697021,2017-10-20 18:46:28 UTC,"still does this, same mouse different computer running artful/gnome/weyland/gdm3"
1697021,2017-10-23 02:14:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697021,2019-08-05 03:49:32 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1697032,2017-06-21 08:43:50 UTC,Is the VN configured as L3 only ? can you capture and upload the packet that is getting dropped. Please check the destination mac and IP on the packet and see which route entries get hit.
1697032,2017-07-10 07:23:40 UTC,"Hi all,"
1697032,2017-07-03 14:23:21 UTC,"Please upload the server capture as well. Also, the bridge table output from both compute nodes (output of ""rt --dump <vrf-id> --family bridge"")"
1697032,2017-06-27 13:13:21 UTC,"I see, thanks for info. I have done the capture on both tap interfaces associated to VMs.
We can see that in server.cap, DHCP Offer packet has destination mac address the same address as the source mac address from DHCP discover packet.
We can also see from client.cap that no DHCP Offer packet arrives on the client's interface."
1697032,2017-07-19 09:22:25 UTC,"Hi all,"
1697032,2017-06-22 13:57:31 UTC,"Hi all,"
1697032,2017-06-21 14:05:07 UTC,"Hi all,"
1697032,2017-07-19 08:52:37 UTC,"The bridge entry for 2:ca:92:10:1b:25 (which is the destination for the DHCP response) doesnt show the nexthop index above. Please check what value it has and using ""nh --get <nexthop-id>"" you can check if that points to the expected interface."
1697032,2017-06-26 14:56:24 UTC,Each VM interface has a corresponding tap interface on the compute node. You can do a tcpdump on this tap interface. The tap interface name is derived by from initial five bytes of VMI uuid (these are also the last five bytes of the interface mac address).
1697050,2017-06-10 08:54:55 UTC,"The script marionnet_from_scratch suppose the host GNU/Linux
distribution not minimalist, because it's very hard to know the precise
name of some basic package, like graphical (X) and GTK packages.
However, the error message is quite clear : you have to install the GTK
libraries. For instance, on Ubuntu 16.10 the names of related packages are :"
1697050,2017-06-13 07:43:28 UTC,"On 2017-06-10 at 08:54, Jean-Vincent Loddo wrote:"
1697051,2017-06-21 17:27:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697051,2017-06-22 05:43:52 UTC,"Today, it appears that the security protocol Munge fails to launch thus causing dependenciy problems for Slurm"
1697051,2017-06-13 04:51:49 UTC,This looks to be a consequnce of https://bugs.launchpad.net/ubuntu/+source/munge/+bug/1287624
1697051,2017-06-13 04:48:55 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1697053,2017-06-09 18:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1697053,2017-07-10 08:19:30 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1697053,2017-07-11 16:18:08 UTC,that indeed solved the problem.
1697053,2017-07-11 16:25:15 UTC,Sorry let me correct. I still need to validate with the -proposed kernel. The applied commit fix the issue though.
1697053,2017-07-13 22:04:18 UTC,proposed kernel tested by customer
1697053,2017-07-18 08:01:00 UTC,This bug was fixed in the package linux - 3.13.0-125.174
1697056,2018-01-24 11:34:34 UTC,"Double-sided printing is missing on this printer with a fresh Ubuntu 16.04 installation.
HPLIP seems to be version 3.16.3, so perhaps this was a bug that was fixed since that?"
1697056,2018-01-24 12:31:07 UTC,"Seems indeed to be a bug in 3.16.3. In https://bugs.launchpad.net/hplip/+bug/1482748, upgrade to 3.15 fixed the same issue for HP M277. Running the M477fdw with M277's driver makes double sided printing work."
1697056,2017-08-18 21:03:04 UTC,"Hello Shivani,"
1697056,2017-06-20 16:42:10 UTC,"Hello Jose,"
1697056,2017-06-09 18:38:25 UTC,"I am convinced these bugs are planted by the companies like HP, Canon, and
others that want a machine like your HP 477 fdw to remain propitiatory,
they do not want anyone to use free software to drive their devices.
I have decided to boycott their machines, it's the only tool we have to
fight back, and if I were you I would return that machine.  I had a
Canon multifunction machine that refused to work at all, I sent it back at
great expense to them.....Send it back !"
1697056,2017-08-18 14:01:28 UTC,"Hello Matthew,
     It looks like there was some problem during installation, we have verified that this printer supports duplex option with short edge and long edge.  Kindly uninstall hplip using hp-uninstall and then re-install using the steps mentioned in the website."
1697074,2017-06-09 19:36:06 UTC,"Server version: 5.7.18-15-log Percona Server (GPL), Release 15, Revision bff2cd9"
1697074,2017-06-09 19:38:29 UTC,I created upstream https://bugs.mysql.com/bug.php?id=86641
1697074,2018-01-25 09:38:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1099
1697095,2017-07-06 04:05:53 UTC,"The cloud as a whole is using the maas provider, I'm adding the s390x unit via add-machine since there's no s390x support in maas."
1697095,2017-07-07 02:37:23 UTC,"So you need to use the manual provider explicitly, you can't mix in any architecture that maas doesn't support with a maas provided environment?  That seems...kind of not great actually.  I've got this working but it's reliant on a relatively fragile set of circumstances for a correct deployment, i.e. the s390x node has to be the last thing to deploy and there must be no more deployable machines in maas, I was hoping to use architecture constraints to shore that piece of the deployment up.  Are there any other constraints I can apply in this situation?  I.e. is it possible to tag a machine added via add-machine perhaps?"
1697095,2017-07-04 01:39:50 UTC,Hmm...
1697095,2017-10-02 08:34:50 UTC,"Setting back to Triaged, as far as I can see this is still a valid bug."
1697095,2017-06-30 22:05:02 UTC,"$ juju deploy ./nova-compute nova-compute-s390x --constraints arch=s390x
Deploying charm ""local:xenial/nova-compute-136"".
ERROR cannot add application ""nova-compute-s390x"": invalid constraint value: arch=s390x
valid values are: [amd64 arm64 i386 ppc64el]"
1697095,2017-06-28 23:58:43 UTC,"Would it be possible to check that you can reproduce this without Mojo in the mix? I don't know that we have s390x machines to validate this locally, so we'll likely need to work with you directly if we want to make sure any patch that we do actually does work for you."
1697095,2017-07-11 08:40:46 UTC,"Well, excuse my ignorance, but how can we improve this situation to avoid such fragile workarounds like the one that Dave had to do?
Does this need to be addressed more towards Juju or MAAS?"
1697095,2017-06-30 22:05:18 UTC,"That's with juju 2.1, I haven't had a chance to try 2.2.1 as of yet."
1697095,2017-09-10 04:17:30 UTC,[Expired for juju because there has been no activity for 60 days.]
1697095,2017-07-06 05:31:07 UTC,"Ah... for MAAS, it does checks on the architecture of all the enlisted
machines to get a validation set. So if MAAS doesn't know it has any
s390x architecture, Juju won't let you specify it."
1697095,2019-05-23 02:09:46 UTC,I'm wondering what the status of this is. We're going to be adding s390x support to a cloud soon and would like to be able to specify architecture constraints like we do with arm64 and ppc64el.
1697095,2019-05-23 08:27:42 UTC,"There's been no further work on how arches are handled by the maas provider. Valid arches are restricted to the set of enlisted machines managed by maas. If a manual machine is added to the model, that machine's arch is not added to the allowed set. In general for maas provider, only machines managed by maas are available to be used with arch or tag constraints."
1697105,2018-03-03 17:34:54 UTC,"Also, this is the component transfer maxed out (how the pixellize filter should work instead of using fecolormatrix)."
1697105,2018-03-03 17:01:11 UTC,This is not perfect but better than previous mine.
1697105,2018-03-03 16:31:31 UTC,"I do a fix for image to allow X and Y to it, not sure is on 0.92.2 but in master yes"
1697105,2018-03-03 12:40:36 UTC,"Hi Jabiertxof, Thank's for taking a look!"
1697105,2018-03-03 17:29:50 UTC,"That filter also just forces the anti-aliasing for a steeper, more ""filled up"" edge.
If applied on a single object only, the aliased edge sticks out more."
1697105,2018-03-03 02:43:55 UTC,"Update:
submitted an issue at github's w3c project
titled >>new composite-mode for globalCompositeOperation<<"
1697105,2018-03-03 00:54:44 UTC,Just today we had a conversation at the #irc and maybe this description of the problem is not getting through?
1697105,2018-03-03 12:03:27 UTC,Hi Lazur.
1697112,2017-08-23 15:46:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697122,2020-09-14 05:27:53 UTC,Let's revert that in Bug 1660212.
1697122,2019-07-01 08:05:05 UTC,Note we already have bug 1312376 covering touchscreen support. This bug should be about touchpads.
1697122,2019-12-06 03:01:48 UTC,*** Bug 1597218 has been marked as a duplicate of this bug. ***
1697122,2020-04-18 12:25:23 UTC,"Still a problem on Ubuntu 20.04 beta, which prevent smooth scrolling in Firefox."
1697122,2020-07-27 19:42:15 UTC,"Is there any possibility of enabling this soon?  Out-of-the-box Firefox is unusable with touchscreens, and as touchscreens become more common (e.g. I just upgraded my laptop to one that has a touchscreen), having this enabled quickly becomes quite important for a large number of users.  Also, https://bugzilla.mozilla.org/show_bug.cgi?id=1182700 was just fixed in Kwin, and AFAIK that was the last blocker of this bug."
1697122,2020-10-27 19:48:47 UTC,Still not working in Ubuntu 20.10 with Firefox 82.
1697122,2020-09-15 06:18:35 UTC,This bug should probably be reopened since the change was completely reverted.
1697122,2020-08-18 15:40:58 UTC,https://hg.mozilla.org/mozilla-central/rev/6c7f2177e485
1697122,2020-07-30 00:40:43 UTC,"Martin, WDYT? Based on the above info, should we enable XInput 2 for KWin >= 5.19.3 (and >= 5.18.next)? How about other window managers?"
1697122,2020-08-13 13:04:14 UTC,"Created attachment 9169828
Bug 1207700 [Linux] Enable XInput2 on Gtk 3.24 and newer, r?botond"
1697122,2020-08-05 21:49:41 UTC,"(In reply to Martin Stránský [:stransky] from comment #19)

> Fedora has used XINPUT2 by default for five years and I don't have any reports so I guess it's okay to enable it for recent systems, at least for KDE/Gnome.
"
1697122,2020-08-03 12:31:09 UTC,"(In reply to Botond Ballo [:botond] from comment #18)

> Martin, WDYT? Based on the above info, should we enable XInput 2 for KWin >= 5.19.3 (and >= 5.18.next)? How about other window managers?
"
1697122,2020-07-27 19:46:31 UTC,"After some more thinking, it would probably make sense to enable it by default but disable it for KWin < 1.19.3, so those users don't get hit by the bug."
1697122,2020-07-27 20:21:18 UTC,"(In reply to QwertyChouskie from comment #13)

> Also, https://bugzilla.mozilla.org/show_bug.cgi?id=1182700 was just fixed in Kwin, and AFAIK that was the last blocker of this bug.
"
1697122,2018-01-22 14:07:52 UTC,"For Bug 1182700 looks like gnome folks gave up (https://bugzilla.gnome.org/show_bug.cgi?id=750994#c8) and recommend to use Wayland. I wonder how big complication is it and if benefits from enabled xinput2 outweigh it, especially when the focus bugs should be fixed on recent systems."
1697122,2020-07-27 21:11:51 UTC,"I am unable to reproduce using the steps in https://bugzilla.gnome.org/show_bug.cgi?id=750994#c0 with my laptop's touchpad, tested on Gnome Shell 3.36 (Ubuntu 20.04).  I tried the same steps with FF and also can not reproduce it there.  I suspect the bug was mitigated/had its impact lessened (perhaps unintentionally) in Gnome at some point, which then left the issue for KDE users (as per most of the comments in https://bugzilla.mozilla.org/show_bug.cgi?id=1182700)."
1697122,2019-06-02 22:53:00 UTC,"it's annoying for me too. The problem is that setting the envar just substitutes some problems with different ones:
- Without this envar set, there is no touchscreen scrolling, and touchpad scrolling goes three lines at a time rather than pixel-by-pixel
- With this envar set and a notification appears, touchpad scrolling is interrupted and mouse wheel scrolling stops working entirely until Firefox is de-focused and re-focused"
1697122,2020-08-18 07:23:20 UTC,"Pushed by <email address hidden>:
https://hg.mozilla.org/integration/autoland/rev/6c7f2177e485
[Linux] Enable XInput2 on Gtk 3.24 and newer, r=botond"
1697122,2019-06-02 21:58:51 UTC,"If this bug is not going to be fixed soon, I suggest Ubuntu should bundle another browser in the next release."
1697122,2018-01-19 13:26:19 UTC,"Before the switch we need to address Bug 1182700. Bug 1170342, Bug 1196777 should be fixed for reasonable recent systems."
1697122,2019-05-12 23:16:59 UTC,"BTW I've since changed my mind on this. Setting the proposed environment variable makes toupad scrolling mysteriously slow down after a notification arrives until you switch focus away from Firefox and back (See https://bugzilla.mozilla.org/show_bug.cgi?id=1182700). This problem is particularly severe for mouse scroll wheel users, where wheel scrolling breaks entirely until you switch away and back again."
1697122,2019-05-12 23:17:45 UTC,"So I recommend closing this bug, or else devoting some Canonical development resources to fixing the above-mentioned upstream bugs first."
1697122,2018-01-19 13:00:07 UTC,I think we can enable the XInput2 for recent Gtk+ versions (say Gtk+ >= 3.20) as the related Gtk+ focus bugs was fixed but for XInput2 only. Also Fedora enables XInput2 by default and we don't have any user complains.
1697122,2017-08-16 00:21:23 UTC,*** Bug 1390130 has been marked as a duplicate of this bug. ***
1697122,2017-08-11 03:23:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697122,2017-06-10 21:30:15 UTC,Upstream blockers: https://bugzilla.mozilla.org/showdependencytree.cgi?id=1207700&hide_resolved=1
1697122,2017-01-24 18:07:09 UTC,"Using ""MOZ_USE_XINPUT2=1"" &e10s worked for me (https://bugzilla.mozilla.org/show_bug.cgi?id=1268599#c10), but not very smooth (scrolling, afterwords opening the menu item, then trying to scroll results in an un-scrollable page). Fedora already compiles FF with ""MOZ_USE_XINPUT2=1"", which is very smooth on my tablet."
1697122,2015-12-22 23:46:58 UTC,*** Bug 1234005 has been marked as a duplicate of this bug. ***
1697122,2015-10-22 22:03:24 UTC,MOZ_USE_XINPUT2=1 is in Nightly (bug 1207973) but not yet in Aurora.
1697122,2015-10-14 10:30:26 UTC,"(In reply to Martin Stránský from comment #2)

> Just set MOZ_USE_XINPUT2=1 env variable which enables it in Firefox.
"
1697122,2020-07-28 18:03:35 UTC,"(Also FYI, the KWin fix was just backported to the 5.18 series, so it should be fixed in the next 5.18.x point release, meaning Ubuntu 20.04 and its derivatives should get this fix soon.)"
1697122,2015-10-14 10:00:07 UTC,Please add option to reenable via about:config or something - I'm really got used to it...
1697122,2019-05-08 16:41:59 UTC,"For completeness sake, here is the OpenSuse bug report talking about it:
https://bugzilla.opensuse.org/show_bug.cgi?id=1032003"
1697122,2019-05-08 16:40:27 UTC,"It is indeed a common complaint/request as evidenced by the people talking about it in various places (blogs, reddit, etc.):
https://www.rojtberg.net/1569/switching-back-from-chrome-to-firefox/
https://www.reddit.com/r/linux/comments/72mfv8/psa_for_firefox_users_set_moz_use_xinput21_to/
https://hackido.com/2019/02/01/2019-02-01-firefox-with-touch/"
1697122,2018-08-31 20:01:45 UTC,Counter-argument:  Try to zoom in on a PDF with this option on.  (It goes in increments of 10% *per pixel*.)
1697122,2019-05-08 22:11:03 UTC,"Quick workaround for those who want to enjoy the benefits right away:
echo ""MOZ_USE_XINPUT2=1"" | sudo tee /etc/environment.d/90firefox-xinput2.conf"
1697122,2018-05-10 03:59:02 UTC,"Gnome issue 750994 has been migrated to their Gitlab instance:
https://gitlab.gnome.org/GNOME/gtk/issues/558"
1697122,2015-09-23 17:37:55 UTC,We had to disable XI2/multidevice support in bug 1170342 due to focus and scrolling related issues. We should monitor these issues to see if it would be possible to re-enable XI2 in the future.
1697122,2015-10-14 10:09:09 UTC,"(In reply to Kuba Niewiarowski from comment #1)

> Please add option to reenable via about:config or something - I'm really got
> used to it...
"
1697123,2018-02-12 21:22:45 UTC,This issue was fixed in the openstack/requirements 1.2.0 release.
1697123,2017-07-27 13:23:41 UTC,note that pyasn1 0.3.1 is out
1697123,2017-08-01 20:24:37 UTC,"and the fix as been merged, marking as fixed in reqs"
1697123,2017-07-17 12:03:45 UTC,This issue was fixed in the openstack/requirements 1.1.0 release.
1697123,2017-07-13 04:49:24 UTC,Waiting for release:
1697123,2017-07-11 00:22:39 UTC,Just a quick note that this bug has been fixed in pyasn1 master (commit https://github.com/etingof/pyasn1/pull/42/commits/2e5bbe62012c593d606c71e02131c8b7d0eeb2dd) and will appear in the upcoming pyasn1 release (the one past 0.2.3).
1697123,2017-07-26 13:07:53 UTC,making a note for the reqs team to unblock pysnmp versions once the new pyasn1 is out.
1697137,2017-06-10 05:30:04 UTC,This change was made by a bot.
1697143,2017-06-10 12:49:50 UTC,One tricky part about the GNOME Shell design is that there isn't really room for another icon in the bottom row of the system status menu. See the attached screenshot.
1697143,2017-06-10 13:00:40 UTC,There would at least be room in the restart/shutdown/cancel dialog you get after choosing the rightmost icon from that menu.
1697143,2017-06-12 02:05:10 UTC,"Yes, I was thinking the same as comment #4."
1697143,2020-03-02 11:21:16 UTC,This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
1697143,2017-06-10 12:45:07 UTC,There are 2 or 3 ways to suspend your computer using GNOME:
1697149,2017-11-03 14:56:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697196,2017-06-13 04:46:48 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1697201,2018-02-10 17:39:35 UTC,As we already know from bug 1748624 - by default `snap find` shows only featured snaps.
1697201,2017-06-10 20:19:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697201,2018-02-10 11:15:40 UTC,Confirmed.
1697208,2018-08-05 15:36:04 UTC,Possibly related. On trying to install Karbon (Kubuntu 18.04.1) I get the following error
1697212,2017-06-16 21:54:57 UTC,that's a good question!
1697212,2018-04-20 15:00:26 UTC,The closest I could find to a documentation of InstallLocation is https://msdn.microsoft.com/en-us/library/windows/desktop/aa372105(v=vs.85).aspx
1697212,2017-06-15 09:49:50 UTC,"Hi Liviu, thanks for taking the time to raise the bug. Could you point me at where Microsoft say that InstallLocation is preferred please?"
1697214,2017-08-05 02:31:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697215,2020-02-26 12:01:53 UTC,"Hi Liviu,"
1697229,2018-01-08 11:25:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697229,2018-11-12 07:06:21 UTC,Started experiencing this bug after Ubuntu update 18.04->18.10.
1697229,2018-11-12 09:03:34 UTC,"I've experienced possibly this bug intermittently since moving to Manjaro Gnome with Gnome 3.30.2. In my case it's not all the extensions that are reset, but two that I've set different to default: Places status indicator and Topicons plus. Furthermore, rebooting usually puts it right; it's the locking and unlocking that deactivates those extensions on my system."
1697229,2019-12-28 07:32:40 UTC,"In Ubuntu 19.10 it still happens to me, after I logout and login again (I use Ubuntu Desktop not the Gnome desktop). Thanks for working on this."
1697229,2017-06-11 04:30:26 UTC,"After I created that ticket #1697229 I realized that this launchpad seems to be for Ubuntu. Since gnome-session is primarily maintain by bugs.debian.org it seems more appropriate to create this ticket with bugs.debian.org?
I created a ticket at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864592"
1697230,2017-06-11 01:00:12 UTC,This change was made by a bot.
1697230,2018-01-01 18:00:23 UTC,"I see this during bootup with a fresh install of artful on a HP Spectre x360 13-4104ng notebook. For me it's  setkeycodes e057 and code 0xd7, though."
1697230,2018-01-01 18:06:20 UTC,My problem seems to also be reported in bug #1535008 .
1697234,2017-06-11 02:17:57 UTC,"StacktraceTop:
 g_malloc (n_bytes=n_bytes@entry=6572719) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmem.c:99
 g_slice_alloc (mem_size=mem_size@entry=6572719) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gslice.c:1025
 _sysmem_new_block (flags=(unknown: 0), maxsize=6572575, align=31, offset=0, size=6572544) at gstallocator.c:414
 gst_buffer_new_allocate (allocator=0x0, size=6572544, params=params@entry=0x7f24804fa0d0) at gstbuffer.c:767
 video_buffer_pool_alloc (pool=0x7f24804fa1a0, buffer=0x7f2440027700, params=<optimized out>) at gstvideopool.c:247"
1697234,2018-01-02 09:57:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697234,2018-01-02 09:58:29 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/5756583e641495b2cfbe54170fbc865f2e7ff13f"
1697235,2017-07-13 18:00:00 UTC,"We need to drop the warning in this case.
on architectures without dmi information many of the datasources cannot be properly identified.
(the warning here is the same root issue as https://bugs.launchpad.net/cloud-init/+bug/1663315)"
1697244,2017-06-13 12:48:18 UTC,"Thx a lot for your answer.
The ppd file is not the problem, I can manage it, the real problem I want to remark is that hplip wasn't able to configure the wireless connection of the printer."
1697244,2017-06-12 14:01:37 UTC,"""... Failed to read /etc/cups/ppd/Deskjet_3520.ppd ..."""
1697245,2017-06-11 07:19:19 UTC,"Which guide is this referring to?
https://pypi.python.org/pypi/neutron-lbaas-dashboard
https://docs.openstack.org/developer/neutron-lbaas-dashboard/installation.html"
1697246,2017-08-22 08:19:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697255,2017-06-11 16:31:14 UTC,workaround: remove '*ABS*' section from applet.elf
1697255,2017-06-12 08:41:37 UTC,"Hi Necwerk,"
1697255,2017-06-12 14:15:40 UTC,How it can work in the second case?
1697255,2017-06-12 14:21:54 UTC,What second case do you mean?
1697255,2017-06-13 06:11:03 UTC,With my workaround
1697255,2018-11-08 00:47:02 UTC,"Bumping this thread.  Has any fix/patch been put in place for this issue.  I just got hit with the same issue on a Cortex-M4, linking with the latest GCC version (GNU Tools for Arm Embedded Processors 7-2018-q2-update) against an ARM Holdings generated elf file.  I am using -fpie which seems to cause this issue.  The symbols from the ARM elf file are:
00006d31     0 FUNC    GLOBAL DEFAULT  ABS memcpy   (using readelf)
00006d31 g     F *ABS*  00000000 memcpy             (using objdump)"
1697255,2017-06-13 16:50:31 UTC,before and after the strip command:
1697255,2017-06-14 16:17:28 UTC,"Hi,"
1697255,2017-06-15 14:16:02 UTC,Can I mark an address as function in symbol file?
1697255,2017-06-15 14:40:44 UTC,I don't think there is a syntax for that. Which is why I proposed declaring the prototype in the C file so an UNDEF function symbol will get generated in the hope that --just-symbols will just reuse that symbol and update its value.
1697255,2017-06-19 12:35:46 UTC,Can I mark an address as function in symbol file? Anyways it works well if I'm importing that symbol from symbol file...
1697255,2017-06-23 09:33:19 UTC,Where we could change the code to avoid the linker to switch arm mode if the target is cortex m4 that doesn't support the arm instruction set? elf32_arm_stub_a8_veneer_blx?
1697255,2017-06-11 15:32:13 UTC,as you can see test2_veneer compiled/linked as non-thumb code.
1697255,2017-06-13 09:50:18 UTC,I'm not sure. What's the output of arm-none-eabi-objdump -t applet.elf after the strip command?
1697255,2017-07-05 16:14:41 UTC,Cortex-M doesn't support ARM instructions so this is why I don't understand why the linker can switch to ARM mode from THUMB.
1697255,2018-11-08 14:55:01 UTC,"Hi John,"
1697255,2017-06-23 09:44:54 UTC,"The change would be in arm_type_of_stub to return a different type of stub. However I don't think this should be done, only an error should be reported if the target is ARM and the device is a Cortex-M. Otherwise you could by mistake link in an ARM function and you wouldn't get any error until you run it."
1697255,2018-11-20 20:11:08 UTC,"Hi, sorry for the delay.  I have attached a simple build.  I also noticed I
can create the same issue using addresses that are far, without PIE."
1697264,2017-06-12 08:16:40 UTC,"it is weird, because see my test bellow. It is working. Do you have enabled hugepages or anything specific?"
1697264,2017-06-12 12:10:07 UTC,"Hi,"
1697264,2017-06-11 10:58:58 UTC,Link to linux kernel crashdump https://drive.google.com/open?id=0Bw60UyguIymoWHVOSEtPUVFpODQ
1697265,2017-06-13 14:17:06 UTC,"<blockquote>no longer affects: 	ubuntu-mate</blockquote>
still not working, what can I do?"
1697265,2017-06-13 08:40:45 UTC,apport information
1697265,2017-06-13 08:40:41 UTC,apport information
1697265,2017-06-13 08:40:37 UTC,apport information
1697265,2017-06-13 08:40:35 UTC,apport information
1697265,2017-06-13 08:40:33 UTC,apport information
1697265,2017-06-13 08:40:31 UTC,apport information
1697265,2017-06-13 08:40:30 UTC,apport information
1697265,2017-06-13 08:40:28 UTC,apport information
1697265,2017-06-13 08:40:38 UTC,apport information
1697265,2017-06-13 08:40:23 UTC,apport information
1697265,2017-06-13 08:40:21 UTC,apport information
1697265,2017-06-13 08:40:18 UTC,apport information
1697265,2017-06-13 08:40:16 UTC,apport information
1697265,2017-06-13 08:40:13 UTC,apport information
1697265,2017-06-13 08:40:12 UTC,apport information
1697265,2017-06-12 23:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1697265,2017-06-13 08:40:26 UTC,apport information
1697268,2017-06-17 10:04:40 UTC,Is there any more information specifically that we should provide that would help to point out the root cause of this problem?
1697268,2017-06-15 09:31:32 UTC,I'm also using 16.04.2 (fully updated).
1697268,2017-06-14 15:35:17 UTC,Forgot to mention: This is on Ubuntu 16.04.2 with HWE-kernel (fully updated). Using Gnome Shell desktop.
1697268,2017-06-14 15:31:47 UTC,I can confirm this. Exactly the same behaviour and the same time frame.
1697268,2017-06-14 15:23:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697270,2017-06-14 22:16:36 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1697270,2018-05-08 18:10:54 UTC,This change was made by a bot.
1697270,2021-01-07 04:05:55 UTC,4.8 EOL
1697273,2018-04-13 06:43:24 UTC,Ctrl+R seems to work for me in bionic
1697277,2017-06-11 14:30:09 UTC,apport information
1697277,2017-06-11 14:30:12 UTC,apport information
1697277,2017-06-11 14:30:10 UTC,apport information
1697277,2017-06-11 14:30:14 UTC,apport information
1697277,2017-06-11 14:29:54 UTC,apport information
1697277,2017-06-11 14:30:18 UTC,apport information
1697277,2018-05-08 18:11:19 UTC,This change was made by a bot.
1697277,2017-06-11 14:30:07 UTC,apport information
1697277,2017-06-11 14:30:16 UTC,apport information
1697277,2017-06-11 14:30:05 UTC,apport information
1697277,2017-06-11 14:24:11 UTC,I have tried using 4.2.8 and 4.4.68 mainline kernels and the problem seems to exist in each.
1697277,2017-06-11 14:30:01 UTC,apport information
1697277,2017-06-11 14:30:00 UTC,apport information
1697277,2017-06-11 14:29:59 UTC,apport information
1697277,2017-06-11 14:29:58 UTC,apport information
1697277,2017-06-11 14:29:56 UTC,apport information
1697277,2017-06-11 14:29:52 UTC,apport information
1697277,2017-06-11 14:30:03 UTC,apport information
1697281,2019-12-06 03:33:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697283,2017-08-18 13:06:29 UTC,"Yes, you can."
1697283,2017-08-18 12:08:03 UTC,"Hi! Can I make this bug, including your test case public?"
1697283,2017-06-27 22:56:27 UTC,https://git.gnome.org/browse/librsvg/commit/?id=ecf9267a24b2c3c0cd211dbdfa9ef2232511972a
1697283,2017-06-11 15:22:58 UTC,The way to trigger this vulnerability is to use nautilus to open testcase.svg.
1697283,2017-06-15 18:02:30 UTC,"Thanks, I've filed https://bugzilla.gnome.org/show_bug.cgi?id=783835 for this."
1697287,2017-06-13 04:12:42 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1697287,2017-06-14 22:13:58 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1697296,2018-07-19 02:28:58 UTC,I think this is a reasonable feature request if it's presented as something you can explicitly do to 'smooth out' a parse tree rather than as something that's supposed to happen automatically.
1697296,2018-07-15 03:28:38 UTC,"Thanks for filing this issue. I don't know if I'm going to change this behavior, but I'll explain what you're seeing."
1697296,2018-07-15 16:28:08 UTC,"Thanks for the thoughtful response. I understand your concern about unintended consequences -- you're right, there could be some -- and in writing this response, I keep switching sides and convincing myself one way or the other."
1697296,2019-07-16 20:49:50 UTC,"Revision 509 implements a Tag.smooth() method which should have okay performance, given that it needs to operate recursively over the tree. I figure in most cases this isn't necessary (so I don't do any bookkeeping ahead of time), and even when it is necessary, relatively few strings in the document are affected."
1697297,2017-06-11 18:16:52 UTC,attachments
1697297,2018-09-29 22:57:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697297,2017-06-26 10:34:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1697312,2017-06-13 05:58:15 UTC,"Hi Victor, please try release x.3875."
1697312,2017-06-13 11:28:48 UTC,"Hi Carlo, thank you, there is no more crashes. Here is a new problem: AI train stops on waiting point, but ""WTP"" is not appearing in AI mode in Dispatcher Information and so waiting point never expires."
1697312,2017-06-17 15:09:17 UTC,"Are you using approach_control on the signal that remains at STOP?
If so, than the sequence is correct, as approach_control will not clear a signal until it is the first signal ahead of the train.
If you want to clear that last signal using approach_control if there are still other signals ahead of the train, try using approach_control_position_forced(distance) - this disregards other signals inbetween train and the actual signal."
1697312,2017-06-14 11:51:03 UTC,"Yes, I know that also this problem has been created with x.3863. X.3876 should have solved that. Pls. check. There could still be a timing problem (AI train slowed down more than usual at waiting points)."
1697312,2017-06-14 22:33:18 UTC,"I've checked X3876. Waiting points now operating properly. There is next problem in my activity. NORMAL signal before switch isn't cleared, until I dont occupy a block just in front of them. Here is some screenshots."
1697312,2017-06-15 21:43:08 UTC,"It looks to me that signal 5 is the signal protecting the section which is still occupied by train 1 - see image.
It could be that the changes cause a slight difference in timing such that train 1 is now in a slightly different position as it used to be.
It does not look like a signal error to me."
1697312,2017-06-15 21:57:03 UTC,"You're pointing to PLAYER service, but I have switched to Pzh1 service at this screenshot. The PLAYER is behind me, and after fifth signal there is nothing except switch"
1697312,2017-06-16 17:07:44 UTC,"You mention approach_control.
Do you use the approach control functions to switch between signal states other then STOP?
If so, that could explain what happens - if a signal uses an approach control function and the conditions are not met, the system will not clear any signals further on.
If that is what happens here, I would need to extend that logic by also testing the present state.
If that is indeed so, can you test it by removing the test for approach control?"
1697312,2017-06-16 17:37:32 UTC,"I'm using approach control to change STOP_AND_PROCEED to STOP, until next block will be cleared. Is it able to clear the fifth block behind the train using signal variables for example?"
1697312,2017-06-18 07:33:59 UTC,"I've removed the Approach_Control from these signals. Anyway, the fifth signal stays at STOP with only difference that signal clears after I passed first signal for me on that first screen."
1697312,2017-06-17 15:36:03 UTC,I'm using approach control to stop a train on STOP_AND_PROCEED. Not to clear.
1697314,2018-08-12 15:14:03 UTC,"On Mac, ""locale charmap"" seems to work."
1697314,2018-08-12 15:02:31 UTC,"Hmm, locale -m seems to list all available charmaps."
1697315,2017-10-06 16:28:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697319,2018-08-12 14:54:49 UTC,These tools must not exist in OpenBSD.
1697322,2017-06-12 16:09:56 UTC,"I SAID "" from download"" i.e. from the (see photo here of download pop-up
and the ""subscribe to newsletter"" THERE...)
​"
1697322,2017-06-12 11:32:31 UTC,"The newsletter subsription is working for me, I just added my email address, clicked the ""Subscribe"" button, I then received an email asking me to click a confirmation link, and then got a welcome email."
1697334,2017-06-14 07:56:51 UTC,"The end cmd PING is correct. But I think you didn't set the ip address in the vm to simulate the scenario of allowed-address-pair
I will show the details about that in devstack."
1697334,2017-06-13 18:12:26 UTC,Ok maybe it is correct. If that is not supposed to be true. I think I was just using the ping command incorrectly at the end there.
1697334,2017-06-13 16:13:07 UTC,"Did you notice how I couldn't ping from source IP 10.0.0.10 ? Can you update your bug to reflect that?
""All the Ping request packets which use 10.0.0.10 as Src ip from VM1 are accepted"" - This is not true."
1697334,2017-06-19 10:32:02 UTC,What is it that is broken? allowed_address_pairs is a flexible tool that allows you to duplicate addresses if that's what you want to do (you can even allow 0.0.0.0/0).
1697334,2017-06-12 16:19:41 UTC,Can you update your step by step instructions to have more detail? I can recreate the bug from the description but I'm not sure if it is the same approach as you. See my attempt below:
1697334,2017-06-13 07:04:08 UTC,Thanks for care about this.
1697339,2018-11-05 11:04:41 UTC,I'll take a look.
1697339,2019-04-26 18:03:04 UTC,And the var name is wrong AGAIN:
1697339,2019-04-26 18:00:56 UTC,"Oh, hm, I was mislead, this is using systemd already, it's just shipping the upstart files along for the ride."
1697339,2019-04-26 17:51:17 UTC,"How are you guys passing -D to rpc.gssd? I don't see any provision to do this via /etc/default/*, as the (on xenial) upstart job doesn't pass any command line parameters to rpc.gssd. It just calls:"
1697339,2019-03-21 18:46:47 UTC,Fixed from bionic onwards.
1697339,2018-11-02 18:02:28 UTC,There's a patch attached to the related Debian bug which works and is included in later packages.
1697339,2018-06-21 21:18:57 UTC,"Has there been any progress on getting this pushed to 16.04.4? If it's not going to be pushed to the public repos any time soon, is it available in a testing repo."
1697339,2018-01-15 02:41:41 UTC,I just lost a good chunk of my evening to this. I'm using native IPv6 from my upstream ISP and therefore do not have control of rDNS. I was expecting the documented behavior and didn't realize I'd hit a bug until on a lark I added the IP address of the NFS server to the client's /etc/hosts file.
1697339,2018-01-15 02:39:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697339,2017-06-12 04:29:01 UTC,"The attachment ""patch file of proposed fix (if necessary)"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1697339,2018-11-01 19:38:05 UTC,I'm running into the same exact issue. Is there a workaround for this? My CentOS7.4 machines don't have this problem and I use a standard NFS mount script (with FQDN to mount all the shared directories on our systems). This requires me to have one for Ubuntu machines and one for CentOS.
1697349,2017-12-01 08:07:54 UTC,heat panel is split out to heat-dashboard. Retargeting to heat-dashboard.
1697365,2017-06-13 05:11:21 UTC,"We've certainly talked about per-relation config in the past. This would be a very good fit for that. It also lets you do things like as the *operator* declare whether this application is creating its own database, or reusing an existing one."
1697371,2017-06-22 13:39:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/476521"
1697373,2017-06-12 09:33:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697373,2017-12-10 09:51:38 UTC,I confirm that also happens in firefox 57 on Ubuntu 17.10.
1697373,2017-06-12 09:25:33 UTC,"Sorry, that's the opposite of your problem :)"
1697373,2018-01-30 02:20:33 UTC,"From what I can tell, Xwayland is still missing DPMS support:
https://cgit.freedesktop.org/xorg/xserver/tree/hw/xwayland/"
1697373,2017-06-12 09:06:04 UTC,I am not sure it is a duplicate because I am using GDM
1697373,2017-12-09 02:07:18 UTC,Relevant Chromium bug is #783737: https://bugs.chromium.org/p/chromium/issues/detail?id=783737
1697373,2017-06-12 08:12:24 UTC,The behaviour is different in unity7 and gnome-shell. In unity7 screen blanking is disabled during video playback. Tested on the same machine with same settings.
1697373,2017-06-12 07:35:16 UTC,gnome-shell only knows that Chrome/Chromeium is running. It does not know what the browser is doing.
1697373,2017-08-10 09:43:31 UTC,chromium 61.0.3163.31 (from the beta channel) still affected.
1697373,2017-06-12 10:05:00 UTC,Assigned to xorg-server because the feature simply does not exist in Xorg/Xwayland 1.19.
1697373,2017-06-12 08:27:14 UTC,Oh... probably a duplicate of bug 1692762 :)
1697373,2017-06-12 09:55:04 UTC,It appears that Xwayland on artful has no DPMS support yet:
1697373,2019-12-30 19:22:10 UTC,"Yes, cannot watch video without display locking"
1697373,2019-11-15 15:57:52 UTC,yah it affects my new installation of ubuntu 18.04 lts
1697373,2020-03-06 12:33:57 UTC,Having this issue on Xubuntu 19.10
1697373,2021-01-09 13:20:34 UTC,Having this issue on Lubuntu 20.04.1 as well.
1697373,2019-09-30 09:00:44 UTC,its problem with vlc as well; I'm neither using wayland.
1697373,2018-01-30 07:42:23 UTC,As a workaround I found this GNOME extension:
1697373,2018-03-04 22:28:11 UTC,"Still happpening in Ubuntu 18.04. Maybe not that important now that wayland is not the de default session, but nonetheless worth of fixing I think"
1697373,2019-11-01 22:08:56 UTC,Still there with Ubuntu 19.10.
1697374,2017-06-12 08:00:04 UTC,This change was made by a bot.
1697374,2017-06-14 22:10:04 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1697376,2017-06-12 08:23:06 UTC,apport information
1697376,2017-06-12 08:23:22 UTC,apport information
1697376,2017-06-12 08:23:20 UTC,apport information
1697376,2017-06-12 08:23:18 UTC,apport information
1697376,2017-06-12 08:23:17 UTC,apport information
1697376,2017-06-12 08:23:14 UTC,apport information
1697376,2017-06-12 08:23:13 UTC,apport information
1697376,2017-06-12 08:23:11 UTC,apport information
1697376,2017-06-12 08:23:10 UTC,apport information
1697376,2017-06-12 08:23:02 UTC,apport information
1697376,2017-06-12 08:23:01 UTC,apport information
1697376,2017-06-12 08:22:59 UTC,apport information
1697376,2017-06-12 08:22:57 UTC,apport information
1697376,2017-06-12 08:22:55 UTC,apport information
1697376,2017-06-12 08:00:26 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1697376,2017-06-12 08:23:08 UTC,apport information
1697376,2017-06-12 08:23:05 UTC,apport information
1697377,2018-03-08 15:14:41 UTC,"Hi Reza, As I previously mentioned, this is not related to syslinux, I can try and help you find the source but the current classification is incorrect and thus nobody will handle it."
1697377,2018-04-08 21:12:35 UTC,"I Wrote about it in the past (...2011!).
http://shlomil.blogspot.co.il/2011/12/changing-text-direction-and-gnome.html
Nobody really cared back than.
So, as I wrote in the blog above, I think this issue can be solved as an input method plugin (or a patch to Gnome) which will let you control the invisible characters in the beginning of each paragraph using special hot keys. This is not too hard to do but I think that Gnome people do not acknowledge it as an issue that should be solved and will not accept a patch for it.
Want to solve it? This is what you should do:
1. Open a bug in GTK.
2. Convince them it should be fixed. (That's the hard part)
3. Propose a solution and/or patch."
1697377,2018-04-08 13:01:27 UTC,"Contacting Ubuntu in that case won't do any good, try and invite some more Persian and Arabic speaking members to this bug report and see how we can tackle this, it's far bigger that the scope you initially aimed to.
We might need to go to the source (gtk+ I guess) and try adding this feature."
1697377,2018-03-08 16:04:28 UTC,"Thank you @yaron, but i didn't know exactly what to do. As you can see, It's not only my problem. What i should do to Ubuntu add this feature?"
1697377,2018-03-08 14:58:53 UTC,:_|
1697377,2018-04-11 08:18:01 UTC,"Okay, Thank you for your response. I’ll submit the issue on that site. But i cant find any member with the name you mentioned."
1697377,2017-08-13 16:29:03 UTC,"I still don't understand, did you write something in your browser?"
1697377,2017-08-14 04:11:41 UTC,"Yes. In browser and any text-box(any text editor, user input etc). with this feature we can easily edit multi language texts with different direction."
1697377,2017-08-13 14:23:05 UTC,Any suggest?
1697377,2018-04-11 07:42:52 UTC,"Hi Reza,
Issues regarding GTK should be reported in the upstream issue tracker. Which seems to be:
https://gitlab.gnome.org/GNOME/gtk/issues
Maybe you should first have a chat with Behdad Esfahbod regarding this issue.
Good luck!"
1697377,2017-08-13 15:11:22 UTC,Can you please attach screenshots?
1697377,2017-08-13 16:14:01 UTC,Attaching a screenshot demonstrating the problem.
1697391,2017-06-12 10:54:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/473362"
1697391,2018-03-27 09:56:43 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.openstack.org/473362
Reason: This has been here for some time with no updates. Abandoning to clean up the review queue"
1697394,2017-06-12 09:31:29 UTC,The vertica that also has other type nodes shows the 'master' and 'member'. The other only have 'member'.
1697394,2017-06-12 10:14:26 UTC,"*******************************************************************
class MongoDbClusterView(ClusterView):"
1697394,2017-06-12 11:33:56 UTC,"yes,this is not a bug, is only for improvement experience.
Is there a way to call mgmt through troveclient? I see this patch out of stagnation[1]."
1697394,2017-12-27 06:23:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530177"
1697399,2018-12-23 00:18:41 UTC,"I'm having the same problem on Ubuntu 18.04. The fix suggested by the OP appears to work, and is implemented in this repo: https://github.com/Gekkio/gnome-session-xmonad."
1697399,2018-12-23 00:15:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697399,2018-12-23 00:24:32 UTC,"Mention that bug also affects 18.04, an LTS that will be supported for a long time."
1697403,2017-06-27 19:28:22 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1697403,2017-07-24 15:39:37 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1697403,2017-06-13 02:43:24 UTC,I can reproduce the bug at master (commit 3a5d592e607176f4159ff65b6df0e2b552156aaf).
1697407,2017-06-12 10:19:00 UTC,apport information
1697407,2017-06-12 10:30:08 UTC,This change was made by a bot.
1697407,2017-06-15 17:01:14 UTC,It might be worth trying to make the modules depend on each other.  So add something like this to the /etc/modprobe.d/modulename.conf file:
1697407,2017-06-12 10:19:04 UTC,apport information
1697407,2017-06-12 10:19:02 UTC,apport information
1697407,2017-06-12 10:18:58 UTC,apport information
1697407,2017-06-12 10:18:49 UTC,apport information
1697407,2017-06-12 10:18:55 UTC,apport information
1697407,2017-06-12 10:18:53 UTC,apport information
1697407,2017-06-12 10:18:51 UTC,apport information
1697407,2017-06-12 10:09:02 UTC,"The problem happens when XGene SlimPRO Mailbox (CONFIG_XGENE_SLIMPRO_MBOX) is loaded after XGene I2C SlimPRO (CONFIG_I2C_XGENE_SLIMPRO).
To fix this issue, please help change CONFIG_XGENE_SLIMPRO_MBOX to builtin, not module."
1697407,2017-06-12 10:18:56 UTC,apport information
1697417,2017-06-13 21:16:07 UTC,The export method modified with transparent background :
1697418,2018-04-14 13:04:14 UTC,"In Linux, it is possible to use the external tool xclip"
1697418,2018-04-14 16:42:40 UTC,Then execute the command with LibC package:
1697418,2018-04-19 15:40:07 UTC,"Should be
OSPlateform runCommand:"
1697422,2017-06-12 11:15:33 UTC,related bug:1696906
1697422,2020-06-17 17:16:57 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/736302"
1697422,2020-05-26 14:02:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/730830"
1697422,2020-06-17 16:26:16 UTC,"Reviewed:  https://review.opendev.org/730830
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=fc51678298a38dcd94bcfe92c590b38fdb7193e4
Submitter: Zuul
Branch:    master"
1697422,2020-06-29 14:16:15 UTC,"Reviewed:  https://review.opendev.org/736303
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=cfde6bd1c0129de86ce123c15742d948624b478f
Submitter: Zuul
Branch:    stable/train"
1697422,2020-06-17 17:17:16 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/736303"
1697422,2020-06-24 15:23:53 UTC,"Reviewed:  https://review.opendev.org/736302
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=408531cf2b0ae6bd5771046bd0f73cb795c7d9d4
Submitter: Zuul
Branch:    stable/ussuri"
1697422,2020-07-06 11:56:41 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/739468"
1697422,2020-07-14 10:08:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/740931"
1697422,2020-07-14 11:24:30 UTC,"Reviewed:  https://review.opendev.org/739468
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=ce9077467846fdb08d2de819ea6db7ef0fb99516
Submitter: Zuul
Branch:    stable/stein"
1697427,2017-06-12 11:54:31 UTC,The changes which I made in the answer file are :
1697427,2017-06-12 12:14:52 UTC,"What repo and what version of packstack are you using?, could you past somewhere the entire 172.16.93.197_controller.pp.log file?"
1697427,2017-06-13 04:46:32 UTC,Please check the attached log file.
1697427,2017-06-13 04:55:04 UTC,"I have used the repo ""centos-openstack-newton"" (centos-release-openstack-newton)."
1697429,2020-03-20 19:54:03 UTC,Due to a long inactivity I'm assigning this no one and putting back to Confirmed as it seems it could be still valid.
1697429,2020-11-18 10:24:46 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/763148"
1697429,2021-02-11 22:47:23 UTC,https://review.opendev.org/c/openstack/tempest/+/763148 got merged
1697438,2018-01-25 09:25:51 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3710
1697446,2017-06-12 12:51:40 UTC,"Review in progress for https://review.opencontrail.org/32760
Submitter: Hari Prasad Killi (<email address hidden>)"
1697446,2017-06-13 06:24:10 UTC,"Reviewed:  https://review.opencontrail.org/32760
Committed: http://github.com/Juniper/contrail-controller/commit/12f282c0f3b7389a7d12b8c359de8baca44d9a72
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1697448,2017-08-23 08:48:44 UTC,"In reply to my own question, I've found the following dirty hack:"
1697448,2017-06-12 12:58:46 UTC,"By the way, I don't know why, but now I have an additional line break after each printed entry. How can I remove that ?"
1697450,2018-01-02 07:06:07 UTC,"Ah, yes. Sorry but your bug 1726600 is a duplicate of bug 1505409. And I think this one is different to those two. It just means the wrong .crash file was sent..."
1697450,2018-01-03 13:33:11 UTC,"@Daniel I can't really follow those steps exactly, as the machine hangs as soon as either GDM or gnome-shell is started"
1697450,2018-01-04 01:37:54 UTC,"Yes, I am assuming ""hangs"" means that the user interface is hung, but not the internals of the system. So that's why the instructions in comment #15 require a second machine and for you to be logged in from that already before reproducing the graphical hang."
1697450,2018-01-05 08:30:23 UTC,"@Daniel no, the whole system freezes, even if I ssh before the UI starts (which requires exact timing), then the machine freezes."
1697450,2018-01-05 08:54:13 UTC,"OK, sounds very likely to be a kernel bug, triggered by GPU usage upon login."
1697450,2018-01-05 09:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1697450,2018-01-05 11:55:28 UTC,How can I collect logs?
1697450,2018-01-09 06:16:39 UTC,Can you switch to VT when this issue happens?
1697450,2018-01-11 04:51:21 UTC,"Zesty has this problem, right?"
1697450,2018-01-11 10:34:57 UTC,"yes, Zesty has the same issue, and apparently bionic too."
1697450,2018-01-13 10:28:21 UTC,"I tested the 4.9.0-040900-generic (4.9.0-040900.201612111631) kernel from the mainline PPA, same issue."
1697450,2018-01-26 08:45:38 UTC,Now please find the first v4.9-rc* that has this issue.
1697450,2018-01-26 11:55:32 UTC,"So, it seems that changing a bios setting for the (builtin) video card frequency to ""Auto"" fixed the issue. it was previously set to match the RAM freq (as the video memory is shared).
I can now run 4.13 fine.
Maybe something changed in the intel driver in 4.9 that makes it freeze when a fixed freq is set?"
1697450,2018-01-26 14:58:02 UTC,"> On 26 Jan 2018, at 7:55 PM, Alberto Donato <email address hidden> wrote:
>
> So, it seems that changing a bios setting for the (builtin) video card frequency to ""Auto"" fixed the issue. it was previously set to match the RAM freq (as the video memory is shared).
> I can now run 4.13 fine.
> Maybe something changed in the intel driver in 4.9 that makes it freeze when a fixed freq is set?
"
1697450,2018-01-10 23:36:11 UTC,"No, everything is frozen, if I ssh in the machine before starting the session, ssh is frozen too"
1697450,2017-12-22 16:46:17 UTC,"I'm still seeing a similar issue with daily images of Bionic.
At boot, the machine hangs at splash screen.
If I boot without ""splash quiet"", I can see the last message is about starting login session."
1697450,2017-10-23 03:39:21 UTC,"OK, we're going to need to analyse the hung gnome-shell process. Please try to do this:"
1697450,2017-10-23 21:25:09 UTC,"To test the issue, I booted in text mode (multi-user.target), logged in and then started gnome-shell."
1697450,2017-07-30 18:50:41 UTC,"I gave this another try with latest daily, with the same result."
1697450,2017-10-08 19:20:05 UTC,I can confirm this is a gnome-shell bug.
1697450,2017-10-24 04:51:09 UTC,"Great, thanks. Looks like a duplicate of bug 1505409."
1697450,2017-10-09 01:46:13 UTC,The version of GNOME in Ubuntu 17.10 is now quite different to when this bug was reported.
1697450,2017-10-09 01:47:39 UTC,"Also, comment #3 suggests this is a kernel bug so I'll add a kernel task."
1697450,2017-10-09 02:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1697450,2017-10-09 09:51:23 UTC,"If I run gnome-shell from the terminal with the latest (4.13.0-12.13) kernel, the system freezes."
1697450,2017-10-08 20:31:08 UTC,"As an additional info, running artful on the 4.8.0-59-generic kernel from yakkety seem to work fine."
1697450,2017-10-10 01:46:54 UTC,"It looks like that error is caused by sudo. Please just run:
  apport-collect 1697450"
1697450,2017-10-10 06:58:45 UTC,apport information
1697450,2017-10-09 16:30:40 UTC,Is there any way I could debug the issue with 4.13?
1697450,2017-10-10 06:58:46 UTC,apport information
1697450,2017-10-10 06:58:48 UTC,apport information
1697450,2017-10-10 06:58:49 UTC,apport information
1697450,2017-10-21 15:42:24 UTC,FTR this still happens with gnome-shell 3.26.1-0ubuntu4 and kernel 4.13.0-16-generic
1697457,2017-06-12 16:13:51 UTC,The whole plugins needs an update due to varnish v4:
1697464,2017-06-12 14:58:17 UTC,"I launch a live-usb 16.04 with select ""try without install"".
Only a ZIP file with password can't be open (fail error)."
1697468,2017-06-13 01:59:07 UTC,Hello Michael!
1697473,2017-11-20 20:06:18 UTC,"You're not setting the environment correctly for FLTK to find assets such as fonts. You can do this by hand, but I've had success using the desktop-gtk3 part to do it. Something like this:"
1697473,2017-11-24 03:00:01 UTC,I made the suggested changes and this is the error I am getting:
1697473,2018-01-23 04:17:32 UTC,[Expired for Snapcraft because there has been no activity for 60 days.]
1697473,2018-01-23 15:07:26 UTC,Adding $SNAP in front of the command path seems to have done the job:
1697488,2018-01-31 16:55:58 UTC,Same problem here. This bug have several years old.
1697488,2018-02-01 09:38:40 UTC,"Hello,"
1697490,2020-05-26 18:56:11 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/730936"
1697492,2017-06-14 16:54:11 UTC,one thing i suggested when discussing this on IRC with alfonso was to try to ship a modified /lib/systemd/system-sleep/wpasupplicant from the gadget snap (not sure if that works but would be worth a try) for systems where you pre-install the wpa-supplicant snap.
1697492,2017-06-14 15:47:38 UTC,This was tested with core rev. 1577.
1697492,2017-06-14 15:40:09 UTC,The wpa_cli suspend command triggers the following logic:
1697497,2017-06-13 13:02:57 UTC,"Reviewed:  https://review.openstack.org/473564
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d0d7fc3a19dba48fa988b995db620e0da066381a
Submitter: Jenkins
Branch:    master"
1697497,2017-06-12 18:30:04 UTC,"Yes, we need to use oslo_utils.strutils.bool_from_string() like the other APIs."
1697497,2017-06-13 13:24:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/473842"
1697497,2017-06-13 13:24:55 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/473843"
1697497,2017-07-28 07:41:49 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1697497,2017-08-12 09:56:48 UTC,"Reviewed:  https://review.openstack.org/473843
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9bc7db594ff8b15c3e6711f9a3430fbb43ea66e1
Submitter: Jenkins
Branch:    stable/newton"
1697497,2017-08-12 11:04:52 UTC,"Reviewed:  https://review.openstack.org/473842
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=586ed0ff1efc7a2b0fb36031f6cacef1e26faf05
Submitter: Jenkins
Branch:    stable/ocata"
1697497,2017-08-22 11:38:55 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1697497,2017-08-28 09:55:22 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1697497,2017-06-12 19:38:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/473564"
1697497,2017-06-12 16:25:25 UTC,We should probably be using oslo_utils.strutils.bool_from_string:
1697501,2017-07-07 12:40:13 UTC,"Bonjour,"
1697501,2017-07-07 13:05:39 UTC,Thanks Walter.
1697501,2017-07-14 13:27:29 UTC,"Bonjour,"
1697501,2017-07-14 13:54:41 UTC,# VERIFICATION TRUSTY #
1697501,2017-07-14 14:02:58 UTC,# VERIFICATION FOR XENIAL/YAKKETY/ZESTY #
1697501,2017-07-17 14:30:51 UTC,"I'll release the trusty part right now (since the target-of-interest for the issue is trusty). For the rest, as we discussed privately: please at least give a basic sanity-spin of the new ksh for each of the other stable series, at least to make sure those are not completely broken."
1697501,2017-07-18 15:54:50 UTC,"Hi Łukasz Zemczak (sil2100),"
1697501,2017-07-17 14:39:49 UTC,"The verification of the Stable Release Update for ksh has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1697501,2017-07-06 15:28:00 UTC,"Hello Eric, or anyone else affected,"
1697501,2017-07-19 09:44:12 UTC,@Eric
1697501,2017-07-19 13:20:00 UTC,"@Robie,"
1697501,2017-07-20 13:46:01 UTC,This bug was fixed in the package ksh - 93u+20120801-2ubuntu1
1697501,2017-07-20 13:46:15 UTC,This bug was fixed in the package ksh - 93u+20120801-2ubuntu0.16.10.1
1697501,2017-07-17 14:39:46 UTC,This bug was fixed in the package ksh - 93u+20120801-1ubuntu0.14.04.1
1697501,2017-07-06 15:10:00 UTC,"Hello Eric, or anyone else affected,"
1697501,2017-07-20 13:46:27 UTC,This bug was fixed in the package ksh - 93u+20120801-2ubuntu0.16.04.1
1697501,2017-07-06 14:57:44 UTC,"Hello Eric, or anyone else affected,"
1697501,2017-07-05 12:41:09 UTC,Patch uploaded for the following releases : T/X/Y/Z.
1697501,2017-07-04 19:59:14 UTC,This bug was fixed in the package ksh - 93u+20120801-3.1ubuntu1
1697501,2017-07-04 19:58:12 UTC,Trusty debdiff
1697501,2017-07-04 19:57:50 UTC,Xenial debdiff
1697501,2017-07-04 19:57:28 UTC,Yakkety debdiff
1697501,2017-07-04 19:57:02 UTC,Zesty debdiff
1697501,2017-07-04 17:21:07 UTC,"For ""Ubuntu Sponsors Team"","
1697501,2017-07-04 14:47:40 UTC,I have also reported a bug / submitted the patch to Debian upstream via :
1697501,2017-06-28 12:08:08 UTC,"I installed the test package this morning, and we will try to reproduce for the coming week."
1697501,2017-06-27 13:24:06 UTC,^^ should reveal version:  ksh - 93u+20120801-1+sf143225b2
1697501,2017-06-27 12:56:44 UTC,A test package is now available for testing (pre-sru) to determine if this fixes the problem in Ubuntu as well.
1697501,2017-06-23 20:51:47 UTC,Red hat fix :
1697501,2017-06-23 20:47:28 UTC,"I found a similar RH bugfix[1], not upstream[2]."
1697501,2017-07-06 15:05:49 UTC,"Hello Eric, or anyone else affected,"
1697501,2017-07-04 16:08:00 UTC,The suite of scripts that had the issue were run over 3000 times over the last week.
1697501,2017-07-04 17:09:01 UTC,Artful (Development Release) debdiff
1697507,2018-08-21 09:44:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697507,2018-08-21 10:02:56 UTC,"I can confirm this bug, using apache as a forward proxy too and getting 400 error. Manual patching this line eliminated the problem."
1697507,2021-01-10 03:46:51 UTC,This bug was fixed in the package corkscrew - 2.0-13
1697524,2017-06-13 05:01:21 UTC,"In 2.2 we include the name of the action that has been run (thanks to Eric,
I don't remember the bug # off hand). It may still be true that we don't
include the arguments passed, so I'd leave this bug open for the args being
included."
1697535,2018-06-12 02:15:03 UTC,This bug still exists in Ubuntu 18.04
1697535,2018-02-14 05:37:54 UTC,"You also said to ""change the bug status to Confirmed."" It is my impression that I'm not supposed to do that since I'm the original reporter."
1697535,2018-02-14 05:35:06 UTC,The bug still exists in Ubuntu 17.10.
1697535,2018-02-13 09:49:35 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1697535,2018-02-14 06:14:15 UTC,Thanks for the quick (and thoughtful) reply.
1697536,2018-12-09 07:25:03 UTC,"Same again with me. 16 character PSK, set by my company and is something I have no control over."
1697536,2020-10-31 07:03:41 UTC,"This problem still persist in my ubuntu 20.04 too
this is a great too but need to fix this one bug
thank you"
1697536,2020-09-16 07:12:17 UTC,This problem still persist in Ubuntu 20.04
1697536,2020-04-23 18:25:19 UTC,This problem still persist in Ubuntu 18.04
1697536,2019-11-08 13:25:04 UTC,"Hello,"
1697536,2018-11-22 23:33:50 UTC,"Same situation here. I totally agree with Agustin Rivero (agustin-midokura).
Please fix this limitation client-side!"
1697536,2017-06-14 07:47:33 UTC,"> Our Cisco Meraki appliance is expecting both a PSK to with the server, and a username and password for individual client auth.
"
1697536,2018-02-12 11:41:28 UTC,"Yeah, this seems to be pretty bad. I've been asked to connect to a corporate VPN using PSK that only has 7 characters and can't use Network Manager because this 20+ characters limit :(."
1697536,2018-02-09 10:35:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697536,2017-06-15 07:30:32 UTC,"> To clear this up, it'd be nice if the interface made it clear that the username field is unused
"
1697536,2017-06-14 17:47:33 UTC,"Ahhh yeah, our corporate PSK is only ~10 characters. so it sounds like there's no way to support this VPN with the strongswan plugin. that's unfortunate, since I have no way to change corporate IT infrastructure."
1697536,2017-06-13 18:19:18 UTC,"I have a username and password field, which should be separate from the PSK field, no? Our Cisco Meraki appliance is expecting both a PSK to with the server, and a username and password for individual client auth."
1697536,2017-06-13 08:44:43 UTC,You don't have a Password field?
1697536,2018-06-27 09:47:02 UTC,"Come on,
this a client configuration not a server configuration. In a server you could enforce the user not to use a insecure password. But is it insecure to configure the client wrongly? It's like not allowing a login prompt to enter a short password. Security must be implementing when setting the password in the server not when login in!!"
1697544,2017-06-12 21:00:14 UTC,This change was made by a bot.
1697544,2017-06-13 12:07:50 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1697544,2018-02-16 13:37:55 UTC,"Current kernel is 4.4.0-97-generic given we are blocked generating initramfs, upgrading kernels is interesting..."
1697556,2017-09-23 14:49:31 UTC,"@Hagen Kuehn
When I try to add nomodeset on the 4.10.0-35-generic kernel, my laptop freezes on the disk encryption screen. I tried it with a usb3 dock and hdmi monitor attached and without any peripherals."
1697556,2017-09-23 15:04:50 UTC,"With disk encryption enabled is more of an issue, because the Nvidia drivers need something on the encrypted partition and thus fails to boot."
1697556,2017-09-23 15:42:26 UTC,"@Hagen,"
1697556,2017-09-25 08:47:57 UTC,@Kai-Heng
1697556,2017-09-25 09:22:29 UTC,"There are two separate issues:
1. The original issue, freeze. Your test result:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
Can I say that -rc2 has freeze but -rc5 doesn't freeze?"
1697556,2017-09-25 11:47:04 UTC,@Kai-Heng
1697556,2017-09-26 07:41:56 UTC,Let's focus on the freeze (nouveau) first. We can solve the docking output (i915) later.
1697556,2017-09-26 12:52:13 UTC,@Kai-Heng
1697556,2017-09-27 07:54:44 UTC,"Sorry to ask again - so what's the result on v4.12-rc1, without ""nomodeset""?"
1697556,2017-09-27 09:08:52 UTC,"Your question:
""so what's the result on v4.12-rc1, without ""nomodeset""?"""
1697556,2017-10-04 14:56:12 UTC,"$ git bisect log
git bisect start 'drivers/gpu/drm/nouveau'
# old: [a351e9b9fc24e982ec2f0e76379a49826036da12] Linux 4.11
git bisect old a351e9b9fc24e982ec2f0e76379a49826036da12
# new: [2ea659a9ef488125eb46da6eb571de5eae5c43f6] Linux 4.12-rc1
git bisect new 2ea659a9ef488125eb46da6eb571de5eae5c43f6
# new: [6796b129b0e98162a84e0b6322ac28587556d427] Merge branch 'linux-4.12' of git://github.com/skeggsb/linux into drm-next
git bisect new 6796b129b0e98162a84e0b6322ac28587556d427"
1697556,2017-10-03 14:18:23 UTC,I have tested with kernel 4.11.0-rc1-lp1697556 with the default kernel with the same hardware setup as previously.
1697556,2017-09-22 19:12:08 UTC,@Kai-Heng Feng (kaihengfeng)
1697556,2017-10-04 16:31:42 UTC,I have tested with kernel 4.10.0-lp1697556 http://people.canonical.com/~khfeng/lp1697556/2/ with the default kernel parameters and with the same hardware setup as previously.
1697556,2017-10-04 18:21:41 UTC,"Again, try this:
http://people.canonical.com/~khfeng/lp1697556/3/"
1697556,2017-10-04 19:51:31 UTC,"I have tested with provided kernel at http://people.canonical.com/~khfeng/lp1697556/3/
The test setup was the same as previously."
1697556,2017-10-14 07:15:42 UTC,"Hagen,"
1697556,2017-10-14 13:47:18 UTC,"I agree with Kai-Heng. 17.04 is getting old and given all the good
work that went into the 17.10 release, I recommend you switch to it
Hagen."
1697556,2017-10-15 20:09:42 UTC,"Hi Anmar & Kai-Heng,"
1697556,2017-10-20 11:09:42 UTC,@Kai-Heng Feng and @Anmar Queja
1697556,2017-10-20 11:15:46 UTC,"This is a re-write of my previous response, as I should have reviewed it before submitting. I have simply been too excited! ;-)"
1697556,2017-10-20 14:21:45 UTC,"Hopefully future kernel releases don't need the nouveau.modeset=0
option. But until then, 17.10 is rock solid (been full time on it for
the past 3+ weeks) without issues. Kudos to the Ubuntu and Canonical
teams for doing such a great job."
1697556,2017-10-01 11:36:36 UTC,"To find the patch that fixes the issue, we need to bisect the kernel. Here's the first one:
http://people.canonical.com/~khfeng/lp1697556/1/"
1697556,2017-09-22 09:52:32 UTC,Correct me if I am wrong: 4.11 is bad but 4.12-rc5 works.
1697556,2017-08-31 09:29:57 UTC,"Well, I'm running 4.10.0-33-generic, and although sometimes I have to login twice, and it has frozen on a couple of occasions, it's pretty much okay. So I'm not sure what exactly is different about my combo than yours, except maybe the firmware version I'm running on the 9560."
1697556,2017-09-21 07:53:00 UTC,@dani_bs(sdaniele78)
1697556,2017-06-12 23:00:21 UTC,This change was made by a bot.
1697556,2017-06-13 12:05:46 UTC,Does this issue go away if you boot with the prior kernel version?
1697556,2017-06-13 12:06:49 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 stable kernel[0].
1697556,2017-06-16 20:35:14 UTC,In answer to your qeustion https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/3
1697556,2017-06-19 15:03:03 UTC,Can you also see if this bug happens with the latest mainline kernel?  It can be downloaded from:
1697556,2017-09-22 06:58:36 UTC,@Hagen Kuehn (hag-k)
1697556,2017-06-23 21:02:22 UTC,I'm confirming this issue on a DELL XPS 15 as well. It's still present with 4.10.0.24.
1697556,2017-07-03 13:49:32 UTC,Can confirm on Dell XPS 15 with 4.10.0-26. This is also the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696665 and another workaround is described here: https://rileymacdonald.ca/2017/06/26/ubuntu-broken-boot-on-dell-xps-15-after-kernel-update-upgrade/
1697556,2017-07-04 09:08:16 UTC,"Same here, with Dell XPS 15 (ngg9x) too"
1697556,2017-07-24 12:06:50 UTC,I have tested the suggested workarounds that were given with comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9 in conjunction with kernel 4.10.0-24. Those two workarounds basically suggest not to use the nouveau driver but instead the Nvidia drivers.
1697556,2017-07-24 12:22:31 UTC,"In line with comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/11, the workarounds suggested with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9  do not work with kernel 4.10.0-28 either. The computer freezes just before the login screen appears. Note, no key strokes are recognised and it's not possible to switch to another TTY (same as with originally reported problem)."
1697556,2017-07-29 20:49:37 UTC,"Well, I'm using 4.10.0.28 and nvidia-381 on my XPS 15 9560 and I'm able to login."
1697556,2017-06-19 19:44:35 UTC,In answer to your question https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/6
1697556,2017-08-31 09:08:33 UTC,"I have the same issue on my Dell XPS 9560. It has been running fine in ""intel"" graphics mode up until and including kernel 4.8. With 4.10 and 4.11 it either freezes pre-boot, before I even reach the FDE password prompt, or, if I uninstall the nvidia drivers, it freezes at some point after."
1697556,2017-08-31 09:31:14 UTC,"When you had the nvidia drivers installed, can you confirm how you installed them?"
1697556,2017-09-03 20:34:26 UTC,"Same issue here.
Dell XPS 15 9560, Ubuntu 16.04 (with the latest software updates), using Nouveau driver and the latest firmware available from Dell.
With kernel 4.10.0-33, the computer freezes after I enter the password of the login screen.
With kernel 4.8.0-58 the computer works well."
1697556,2017-09-04 12:40:23 UTC,"John: I tried 4.10.0-33-generic, I tried 32-generic, and several versions before. I'm running the latest firmware from Dell, 1.3.4 I believe, and had something older before that."
1697556,2017-09-04 12:44:23 UTC,"John: Sorry, I forgot to mention, I installed the drivers from the ""Additional Drivers"" menu (I run Gnome), and also from ""the"" PPA."
1697556,2017-09-05 12:20:59 UTC,"For reference; 4.13.0-041300-generic also BOOTS fine on my machine which fails with 4.9, 4.10 and 4.11."
1697556,2017-09-08 19:25:29 UTC,I have reviewed the kernel source code that was committed between the Ubuntu-4.10.0-21.23 and Ubuntu-4.10.0-22.24 and I believe commit b93843fcde501b92647777ac5dbe2c980eb0b479 introduced bug #1697556.
1697556,2017-09-18 19:02:52 UTC,"I just checked the the 17.10 live images on my XPS 15 (9560) and the kernel still doesn't boot without using ""nomodeset"" kernel boot arg."
1697556,2017-09-21 06:46:08 UTC,"I think is the same problem of kernel 4.10 described here:
- https://askubuntu.com/questions/941211/ubuntu-16-04-freezes-with-4-10-kernel-and-nouveau-driver
- https://askubuntu.com/questions/939417/ubuntu-16-04-freezes-with-4-10-kernel"
1697556,2017-09-21 06:48:06 UTC,"Sorry, I involuntarily changed the state to ""Fix Released"" :("
1697556,2017-09-21 07:40:26 UTC,Back to confirmed
1697556,2017-08-17 06:05:36 UTC,"Can confirm this issue on my Dell XPS 9560. I downloaded iso of ubuntu 16.04 made it bootable and i tried to boot into installation menu but i got stuck on loading screen, before it showed up error with noveau and cant create kernel channel, 22. Any fix please."
1697567,2020-07-21 17:04:20 UTC,How the fuck can this still be unfixed?
1697567,2020-04-28 08:34:55 UTC,"Same issue on my side with an Ubuntu 20.04 upgraded from 19.10 in the middle of march. At the beginning all was working fine.
Since yesterday I have exactly the same issue."
1697567,2017-06-13 13:47:20 UTC,I dubt this has anything to do with the kernel.
1697567,2017-08-13 04:17:33 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1697567,2017-06-13 12:04:59 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1697567,2017-06-13 00:30:09 UTC,This change was made by a bot.
1697567,2017-08-13 09:40:09 UTC,"The importance of this bug should obviously be critical, not medium.
It meets all the criteria, plus it may even cause hardware damage."
1697573,2017-06-13 02:12:51 UTC,Can you reproduce this on anything newer than Juno?  We no longer maintain it upstream.
1697573,2017-06-13 02:13:38 UTC,Should have mentioned - Newton or Ocata or master branch would be better as they are current.
1697578,2018-01-24 22:26:06 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1431
1697583,2018-11-17 11:08:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697583,2018-11-17 11:08:57 UTC,amule it'0s broken since 2 years ago.
1697595,2017-06-21 16:36:12 UTC,"Fix proposed to branch: openstack-ci/fuel-7.0/2015.1.0
Change author: Michael Still <email address hidden>
Review: https://review.fuel-infra.org/35726"
1697611,2017-06-21 21:23:22 UTC,That's expected since we patch and ship epiphany 3.18.
1697611,2017-06-22 00:30:49 UTC,"Of course, and epiphany-pantheon-bzr is versin 3.18. I have tried in the past to forward-port the patches to 3.22 with about the same amount of success, and having trouble with the same two patches. In April 2018 Ubuntu will ship 18.04 LTS, and I imagine elementary OS will import it as the base for a new release; the cause of these segfaults will have to be found and these patches updated by then. In the mean time, no rush, but if anyone would like to help me look it up so we can make a better release of epiphany-pantheon for other distros I'd much appreciate it."
1697611,2017-06-22 01:39:52 UTC,"I guess, for a start, can you provide a gdb backtrace for when the segfault occurs?"
1697611,2017-06-22 11:48:38 UTC,"Here's a backtrace for the bookmarks button, which causes epiphany to crash on start."
1697611,2017-06-22 11:58:52 UTC,"Here's a backtrace for dobule click on tab bar to make a new tab, which causes epiphany to crash when attempted."
1697625,2017-07-10 13:28:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697630,2020-02-04 18:59:05 UTC,"This was fixed in 0.6.4-1, published in disco."
1697631,2017-06-24 16:35:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697631,2018-04-18 12:35:38 UTC,"I believe this bug has been inherited from Debian, where it was fixed on Sep. 24th 2017 [1]. I don't know how the process of getting updated packages from Debian into Ubuntu, but to me it seems like an easy task for someone with the proper knowledge and permissions."
1697631,2019-12-22 13:34:55 UTC,The systemd opendkim service no longer reads /etc/default/opendkim. This has been the case since version 2.11.0~alpha-8 (Ubuntu 18.04).
1697635,2017-06-16 08:48:04 UTC,">For what its worth, this affects Ubuntu too.
 >I never understood why this change is needed.
 >Why is the platform so agressive on dropping network connections?
 >
"
1697635,2017-06-15 16:38:43 UTC,"For what its worth, this affects Ubuntu too.
I never understood why this change is needed.
Why is the platform so agressive on dropping network connections?"
1697637,2017-09-17 17:21:18 UTC,"There is a bug in the `linux-firmware-raspi2` package, which shares one file with `linux-firmware` (`/lib/firmware/brcm/brcmfmac43430-sdio.bin`)."
1697637,2017-09-17 20:17:28 UTC,"I've done a few tests, and the `linux-firmware`/`linux-firmware-raspi2` are a red herring - they're unrelated to the bug, as I can't boot even if I hold those packages."
1697637,2017-09-17 20:21:10 UTC,I've opened a separate bug (https://bugs.launchpad.net/ubuntu-pi-flavour-maker/+bug/1717809) for the apt problem mentioned.
1697637,2017-09-18 18:30:15 UTC,The bug is in the boot update (I guess initramfs/flash-kernel).
1697637,2017-06-14 18:24:24 UTC,Same problem here! After fresh install then update/upgrade+reboot
1697639,2017-06-23 13:52:02 UTC,I suppose this is with the custom chromium window with client-side decorations (and buttons on the right)?
1697639,2017-06-23 15:10:41 UTC,This is the default version.
1697640,2017-07-13 01:06:04 UTC,"Same issue experienced here, same workarounds, same solution (remove nvidia-304).  Running Elementary OS on an early 2009 MacBook Pro, dual graphics (NVIDIA GeForce 9600M GT, and NVIDIA GeForce 9400M)."
1697641,2018-06-04 10:38:38 UTC,"A long overdue update: accessibility seems to work again in chromium, it has to be force-enabled to actually function:"
1697641,2018-12-17 23:13:43 UTC,"Oliver, is it still works for you with current Chromium builds?"
1697641,2017-09-25 16:14:14 UTC,From http://www.chromium.org/developers/accessibility/linux-accessibility:
1697641,2017-07-26 16:06:40 UTC,Olivier - could you take a look at this one again when you're back from hols?
1697641,2017-06-23 16:38:16 UTC,It's both.
1697641,2017-10-10 08:43:55 UTC,Some data points:
1697641,2017-06-23 13:50:16 UTC,"Does that affect the omnibox (address bar), text fields in web content, or both?
I unfortunately don't have touch hardware to test that on."
1697646,2017-07-07 08:19:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697646,2017-07-29 13:32:35 UTC,This happens (or used to happen) also in 16.04.2 (current). I paste here a couple of evidences (17.04):
1697646,2017-09-12 09:23:13 UTC,Probably related: https://github.com/iputils/iputils/issues/85
1697655,2017-06-13 11:27:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/473789"
1697655,2017-07-05 11:49:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/480536"
1697655,2017-07-05 20:41:23 UTC,"Reviewed:  https://review.openstack.org/473789
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=2875c97bff9fe46a2f56f12adff28d7c3e0c2cec
Submitter: Jenkins
Branch:    master"
1697655,2017-07-14 17:40:10 UTC,"Reviewed:  https://review.openstack.org/480536
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=eba956061bcf595ed392bd0da26774677d6a5df0
Submitter: Jenkins
Branch:    master"
1697669,2017-06-22 21:47:45 UTC,"This is happening, at least with gmail, because the gmail server doesn't complete when given a large message with attachments to append to a folder. The call to `process-send-string' in `vm-imap-send-command' never returns. Even a LOGOUT command after it gets no response."
1697669,2018-03-03 12:49:31 UTC,"Also, the IMAP session buffer is getting ""lost"". It doesn't get garbage collected, and doesn't get attached in vm-imap-submit-bug-report."
1697669,2018-04-21 14:29:20 UTC,The hanging problem fixed in revision 1520 (recorded correctly in commit 1523). Session buffer problem still remains.
1697672,2017-07-13 15:42:57 UTC,Thanks for your report. I reproduced it on an up to date artful installation.
1697672,2017-08-28 13:23:24 UTC,Reported upstream on https://bugzilla.gnome.org/show_bug.cgi?id=786909
1697676,2017-07-03 08:11:54 UTC,"Reviewed:  https://review.openstack.org/473800
Committed: https://git.openstack.org/cgit/openstack/networking-generic-switch/commit/?id=3dbc82a98445905f88644ae335050d995745687a
Submitter: Jenkins
Branch:    master"
1697676,2017-12-05 07:33:45 UTC,"Report bug
https://bugs.launchpad.net/networking-generic-switch/+bug/1736341"
1697676,2017-06-13 11:43:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/473800"
1697677,2017-06-13 12:17:05 UTC,"Fix proposed to branch: 9.0/mitaka
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/35607"
1697677,2017-06-13 12:18:14 UTC,"Reviewed: https://review.fuel-infra.org/35607
Submitter: Ivan Udovichenko <email address hidden>
Branch: 9.0/mitaka"
1697677,2017-06-13 14:02:56 UTC,"Related fix proposed to branch: 9.0/mitaka
Change author: Ivan Udovichenko <email address hidden>
Review: https://review.fuel-infra.org/35610"
1697677,2017-06-13 14:03:38 UTC,"Reviewed: https://review.fuel-infra.org/35610
Submitter: Ivan Udovichenko <email address hidden>
Branch: 9.0/mitaka"
1697690,2017-06-20 13:02:04 UTC,"Reviewed:  https://review.openstack.org/474194
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=1acd2425e2eeb10c26bd655e192b7d11cd22b36f
Submitter: Jenkins
Branch:    stable/mitaka"
1697690,2017-06-14 13:07:25 UTC,"Related fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/474194"
1697690,2017-06-14 12:24:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474185"
1697690,2017-06-14 12:31:47 UTC,"Reviewed:  https://review.openstack.org/474182
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=d9facdcd975f6e2557a1bfaacdfff853c5d9e7e4
Submitter: Jenkins
Branch:    release/2.9"
1697690,2017-06-14 12:44:51 UTC,"Reviewed:  https://review.openstack.org/474185
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=3cb41214b566b116c4d33e906f3b3f25117a6a9b
Submitter: Jenkins
Branch:    master"
1697690,2017-06-14 12:14:31 UTC,"Fix proposed to branch: release/2.9
Review: https://review.openstack.org/474182"
1697692,2018-09-03 11:42:12 UTC,"I tried to install Qpdfview, but failed with the error message
W: Failed to fetch http://security.ubuntu.com/ubuntu/pool/universe/p/poppler/libpoppler-qt5-1_0.62.0-2ubuntu2.1_amd64.deb
  404  Not Found [IP: 91.189.88.149 80]"
1697712,2017-06-18 21:59:11 UTC,"NetCDF is not built with parallel support, because this breaks all reverse dependencies that require the serial behavior."
1697713,2017-06-14 02:25:25 UTC,This is not a openstack-manuals bug.
1697715,2017-06-13 15:06:30 UTC,I'm not sure it's RFE but put the tag.
1697715,2017-06-28 20:42:42 UTC,Regarding the 3 points in this RFE:
1697715,2017-07-20 21:07:41 UTC,this sounds like internal refactoring. We can drop the RFE
1697723,2018-06-04 14:45:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697723,2018-06-04 14:49:03 UTC,Affects me too
1697733,2017-06-14 18:35:39 UTC,"Reviewed:  https://review.openstack.org/473919
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=d095e97624467fb1e0fa38955b45960d3cbc5651
Submitter: Jenkins
Branch:    master"
1697733,2017-06-13 17:21:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/473919"
1697758,2017-06-13 20:16:50 UTC,This bug was fixed in the package gnome-calendar - 3.24.3-0ubuntu1
1697766,2017-07-09 18:31:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697770,2019-09-27 09:49:39 UTC,Currently there are no plans to support system configuration where various directories are symbolic links. Please consider mounting /var/lib/jenkins either directly or as a bind-mount from /srv/mnt/jenkins.
1697771,2018-03-31 17:20:33 UTC,Another bug related to unexpected display of 856 subfields: https://bugs.launchpad.net/evergreen/+bug/1350827
1697775,2017-06-14 13:46:46 UTC,"Actually, OS_VOLUME_API_VERSION=2"
1697775,2017-06-19 12:22:24 UTC,"Importantly, I did not mention that this is running with John Griffith's new cinder v3 api POC code- https://review.openstack.org/#/c/330285/"
1697775,2018-01-12 19:04:49 UTC,Unassigning due to no activity for > 6 months.
1697789,2019-01-17 05:02:07 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1697789,2017-08-08 09:52:54 UTC,"I'm seeing the same, also with kernel 4.12"
1697789,2017-06-14 13:58:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697789,2017-06-14 18:35:42 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=196075
1697799,2018-04-02 19:01:22 UTC,Not a blocker for 3.0
1697800,2018-07-27 22:09:55 UTC,"Nearly a year later, this is still an immediate problem. For people finding this bug via Google, the only fix I've found that cares about security is to use Debian GNU/Linux instead of Ubuntu and `apt install firefox-esr`. This works because the stable (Stretch) version of Debian uses Firefox-ESR 52.9.0 which was released last month (https://www.mozilla.org/en-US/firefox/52.9.0/releasenotes/)."
1697800,2017-06-17 05:14:11 UTC,"Seth writes, ""running a known-insecure webbrowser is probably a bad idea."""
1697800,2017-06-17 03:49:19 UTC,"By the way, since this problem is already causing Ubuntu LTS systems to break, it may make sense to implement a quick stopgap solution. One possibility is to change the version of Firefox in 16.04 to ""firefox-esr"" (Extended Support Release). While this release will only be supported by Mozilla until March 2018, which is not enough for LTS, it's available now and works."
1697800,2017-06-17 03:45:11 UTC,None of the upgrade tools are in a position to check architecture features before installing a package. There may not be a happy solution here.
1697800,2017-09-22 13:10:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697800,2017-06-16 07:04:11 UTC,"You can trigger a crash immediately on a machine without SSE2 by
running firefox 54 like so:"
1697800,2017-06-16 05:47:03 UTC,"Spoke too soon. Firefox does still die of SIGILL, it just doesn't die
immediately. It is still choking on an SSE2 instruction, though, so
this is the same bug."
1697800,2017-06-16 02:34:55 UTC,"I tried the version the version just released,
54.0+build3-0ubuntu0.16.04.1, and it appears Firefox is working again
on a machine without SSE2. Thank you!"
1697800,2017-06-14 13:27:58 UTC,Looks like it would be intentional according to https://www.mozilla.org/en-US/firefox/53.0/releasenotes/ :
1697800,2017-06-17 03:13:07 UTC,"It looks like this has been in the works for awhile and Mozilla had intended for Firefox to detect SSE2 support in the installer and in the automatic updates. Of course, Ubuntu is skipping both of those."
1697809,2017-06-14 01:27:23 UTC,"The previously attached logs are from after a reboot as I don't think I can run ubuntu-bug without internet access. I can do so if some steps are provided as this is easy to reproduce.
I'm also attaching a snippet (no-wifi) from dmesg after resuming from sleep that may help."
1697813,2017-06-16 02:34:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474829"
1697813,2017-06-16 03:13:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474835"
1697813,2017-06-19 09:06:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/475302"
1697813,2017-06-19 10:30:15 UTC,"Reviewed:  https://review.openstack.org/474498
Committed: https://git.openstack.org/cgit/openstack/mogan/commit/?id=19291b87f9af4b7fa876add464b90b67607b8fc6
Submitter: Jenkins
Branch:    master"
1697813,2017-06-19 10:30:22 UTC,"Reviewed:  https://review.openstack.org/474829
Committed: https://git.openstack.org/cgit/openstack/mogan/commit/?id=30767640c6847067a6f419271ac5209583a816f8
Submitter: Jenkins
Branch:    master"
1697813,2017-06-20 08:51:32 UTC,"Reviewed:  https://review.openstack.org/474835
Committed: https://git.openstack.org/cgit/openstack/mogan/commit/?id=e25a3deebafc98fa8e90d55136e417a3ace6ebf0
Submitter: Jenkins
Branch:    master"
1697813,2017-07-06 02:16:11 UTC,"Reviewed:  https://review.openstack.org/475302
Committed: https://git.openstack.org/cgit/openstack/mogan/commit/?id=393f8c5412e134f0f8589ef0911caab36422b809
Submitter: Jenkins
Branch:    master"
1697814,2017-06-14 02:10:30 UTC,"This was an answer to my original question from
actionparsnip (andrew-woodhead666) said 22 hours ago: 	#1"
1697814,2017-06-14 04:26:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1697817,2017-06-14 11:09:26 UTC,"List of protocols from the smb.conf(5) manpage. Looks like ""NT1"" is SMB1:"
1697817,2017-06-14 10:15:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697817,2017-06-14 11:14:45 UTC,This will require some discussion and thought about the implications. I created a trello card in the ubuntu server board trying to scope these out: https://trello.com/c/P73Okl8z
1697817,2017-06-19 14:00:34 UTC,"Am 19.06.2017 um 15:47 schrieb Andreas Hasenack:

> https://lists.ubuntu.com/archives/ubuntu-
> devel/2017-June/039820.html
"
1697817,2017-06-18 20:04:07 UTC,Just a side note folks but there's two SMBv1's involved here and both are mentioned in this bug report.
1697817,2017-06-19 13:47:09 UTC,RFC from ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2017-June/039820.html
1697817,2017-07-24 17:31:43 UTC,We are closely watching upstream as they move away from SMB1 by default.
1697817,2017-09-11 21:25:30 UTC,Hi!
1697817,2017-09-11 21:31:04 UTC,"Adding more info, next future SAMBA version 4.7 will increase the SMB ""client max protocol"" to SMB3_11 to be able to connect to servers with SMB1 disabled, ""client min protocol"" is still SMB1."
1697817,2019-01-04 06:41:32 UTC,"Hi,"
1697817,2020-01-01 22:57:42 UTC,Samba 4.11 (which looks like it will be in 20.04) now defaults the min protocol to SMB2_02 (https://www.samba.org/samba/history/samba-4.11.0.html )...
1697817,2020-04-13 13:25:28 UTC,"Correct, closing the bug."
1697817,2017-06-16 01:31:04 UTC,I think this is the option that you want to use to restrict the server to a minimum protocol version:
1697822,2017-06-14 20:53:43 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1697828,2018-01-12 19:04:53 UTC,Unassigning due to no activity for > 6 months.
1697835,2017-07-31 13:32:36 UTC,Same problem here
1697835,2017-11-15 16:39:57 UTC,Looks like mburling has also run into this issue: https://paste.ubuntu.com/25962951/
1697844,2017-06-14 05:10:36 UTC,performance issue
1697852,2021-01-07 04:05:59 UTC,4.8 EOL
1697852,2018-05-08 18:11:26 UTC,This change was made by a bot.
1697890,2017-06-16 01:30:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697890,2018-06-20 14:08:18 UTC,Hi there..i am new to ubuntu and am having trouble installing firefox updates
1697894,2017-06-14 09:00:10 UTC,This change was made by a bot.
1697894,2021-01-07 04:13:39 UTC,4.8 EOL
1697906,2018-01-12 19:04:57 UTC,Unassigning due to no activity for > 6 months.
1697912,2017-10-26 08:51:53 UTC,The link has changed to https://www.rdoproject.org/install/packstack/.
1697912,2017-10-25 17:56:57 UTC,This link doesn't exist anymore:  https://www.rdoproject.org/install/quickstart/
1697912,2017-06-22 11:41:06 UTC,"Thanks, adding a warning many a good idea."
1697912,2017-06-22 11:16:11 UTC,Note that extras repo is different that epel repo. Extras repo is part of core CentOS repos and is enabled by default. epel repos is not instaled by default in CentOS and it's not compatible with RDO. We may add a warning about this.
1697912,2017-06-22 10:37:34 UTC,"BTW, if this issue is related to package conflict with Extras repo, then it may be good to add it in the docs for packstack. For packstack, docs mention to use Extras repos:"
1697912,2017-06-16 06:51:57 UTC,I saw many entries like this in keystone logs:
1697912,2017-06-15 13:52:33 UTC,"We've seen you have epel repo installed before running packstack. That may have introduced conflicting packages with RDO, could you re-run packstack in a clean environment without installing any package from epel repo."
1697912,2017-06-15 11:42:28 UTC,"Please let me know if any more details would be helpful for investigating this problem, I can collect those before freshing the setup again.
Thanks for the help!"
1697912,2017-06-15 11:39:17 UTC,"Links to debug logs:
1. https://github.com/ashish-billore/packstack-ocata-error/blob/master/openstack-setup-fresh2.log.tgz
2. https://github.com/ashish-billore/packstack-ocata-error/blob/master/packstack-debug-fresh2.log.tgz"
1697912,2017-06-15 11:00:06 UTC,I managed to recreate the same error on fresh setup. Will provide the logs shortly.
1697912,2017-06-14 15:58:59 UTC,"Ok, I'll clean-up current setup and try again afresh."
1697912,2017-06-14 14:53:14 UTC,"I have tried to reproduce it locally, but didn't reach the error."
1697912,2017-06-14 14:38:58 UTC,"On a fresh setup, I got similar error and then I re-ran packstack on this same setup many times to get past the issue, so in this log some steps may seem to be skipped for this run."
1697912,2017-06-14 11:59:13 UTC,"I have had a look at the log file, and it looks like it is not the first Packstack execution in the system (there are many resources that do not get applied). Are you trying to reconfigure an existing Packstack deployment, or does it happen even on a clean install?"
1697912,2017-06-14 11:40:06 UTC,"Ok, so I managed to upload the full log here -->"
1697912,2017-06-14 11:31:05 UTC,"It is a 6+ MB file, finding problem pasting it here or uploading as attachment.
While I sort this out, are there any specific sections I can paste?"
1697912,2017-06-14 11:15:13 UTC,"That file should be located at /var/tmp/packstack/latest. In some cases, the authentication error may be caused by a previous problem, so it would be really helpful to troubleshoot the issue."
1697912,2017-06-15 11:11:58 UTC,This time the run traces are:
1697912,2017-06-14 10:55:27 UTC,Could you upload or paste somewhere the entire 128.0.0.50_controller.pp.log file?
1697914,2017-07-20 17:46:25 UTC,"For xenial, I tested d-i 20101020ubuntu451.12, which was built w/ netcfg 1.135ubuntu4.5, and the results look good there as well."
1697914,2017-07-26 20:47:22 UTC,This bug was fixed in the package netcfg - 1.135ubuntu4.5
1697914,2017-07-26 20:47:03 UTC,"The verification of the Stable Release Update for netcfg has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1697914,2017-07-20 17:45:44 UTC,"I rebuilt a zesty d-i against proposed & tested on a HiSilicon D05 board. The NICs were properly labelled ""Ethernet Onboard"". See attached screenshot."
1697914,2017-07-20 13:48:32 UTC,"Hello Dimitri, or anyone else affected,"
1697914,2017-07-19 22:28:01 UTC,This bug was fixed in the package netcfg - 1.142ubuntu3
1697914,2017-07-19 17:54:04 UTC,Here's a trivial patch that addresses the issue for me. It cleanly applies back to xenial (- the changelog of course).
1697914,2017-07-10 17:22:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697914,2017-07-20 13:50:40 UTC,"Hello Dimitri, or anyone else affected,"
1697915,2017-06-22 11:53:30 UTC,"Hello,"
1697915,2017-06-22 20:07:34 UTC,"Yes Miguel, unfortunately We lost users data and it was very strange for us because whenever something goes wrong, ""pt-online-schema-change"" goes roll back but this time it dropped current table and new table.
this is users  schema:
CREATE TABLE `users` (
 `id` int(10) UNSIGNED NOT NULL,
 `username` VARCHAR(255) NOT NULL,
 `full_name` VARCHAR(255) NOT NULL COLLATE 'utf8mb4_unicode_520_ci',
 `is_verified` TINYINT(1) NOT NULL DEFAULT '0',
 `is_private` TINYINT(1) NOT NULL DEFAULT '0',
 `profile_pic_url` VARCHAR(255) NULL DEFAULT NULL,
 `follower_count` INT(11) NOT NULL DEFAULT '0',
 `following_count` INT(11) NOT NULL DEFAULT '0',
 `media_count` INT(11) NOT NULL DEFAULT '0',
 `biography` VARCHAR(512) NULL DEFAULT NULL COLLATE 'utf8mb4_unicode_520_ci',
 `user_active` TINYINT(1) NOT NULL DEFAULT '1',
 PRIMARY KEY (`id`),
 INDEX `username` (`username`),
 INDEX `follower_count` (`follower_count`),
 INDEX `following_count` (`following_count`)
)
COLLATE='utf8_general_ci'
ENGINE=InnoDB;"
1697915,2017-06-23 11:20:38 UTC,"What's the struct of the table you wanted to alter?
Could you share, maybe not the real table, but at least the part having foreign keys pointing to the other table?
Could you please share the command line params you used?"
1697915,2017-06-23 12:11:01 UTC,"Hi Carlos,
Look at post number 0 and number 2.
I explained"
1697915,2017-06-26 15:23:36 UTC,"I've verified it fails but if you don't force set-vars=foreign_key_checks=0, all data is preserved."
1697915,2017-06-26 17:45:55 UTC,"To try to re-reproduce this error, I wrote this small Go program to load some sample data: https://gist.github.com/percona-csalguero/22457e02e46e10219ad0d8df892ce8e1"
1697915,2017-06-29 05:53:20 UTC,"Thank you for testing.
I think the document should be updated and warned to prevent this happen."
1697915,2018-01-24 22:27:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-735
1697923,2017-06-14 12:38:38 UTC,"Forgot to mention I'm running Ubuntu Xenial, so I'm using version 0.11.0+ds-1"
1697925,2020-03-12 10:00:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/712633"
1697925,2018-08-31 07:39:37 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/474552
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1697925,2020-04-06 11:57:07 UTC,"Reviewed:  https://review.opendev.org/709122
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=eb6104c0ac61216234ea958f2fd322e70b8e4bec
Submitter: Zuul
Branch:    master"
1697925,2018-08-31 07:39:28 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1697925,2017-06-14 12:30:38 UTC,This was tested with Ocata
1697925,2017-06-15 13:01:31 UTC,https://review.openstack.org/#/c/474552/
1697925,2017-06-14 12:37:58 UTC,"This is a valid use case and we supported this use case in the past.
I can reproduce this in Pike master."
1697925,2017-06-15 17:19:01 UTC,"The behavior reported in this bug in Ocata and master is the expected behavior. Please read the first paragraph of the ""Proposed Change"" in the spec for address scopes: https://specs.openstack.org/openstack/neutron-specs/specs/mitaka/address-scopes.html#proposed-change. This spec is correctly reflected in the original implementation of address scopes: https://review.openstack.org/#/c/197552/15/neutron/db/db_base_plugin_v2.py@707."
1697925,2017-06-15 12:41:16 UTC,"In my understanding, we cannot create subnet pools whose IP address range overlaps in a whole address scope, so we can allow non-admin project to create a subnet pool from a shared address scope. However, I believe we need to check more folks familiar with the L3 area on whether there is a reason we have the current behavior."
1697925,2017-06-14 12:38:28 UTC,"Got a chance to discuss this with Akihiro, basically the below is the usecase."
1697934,2017-06-14 13:19:46 UTC,"Although it actually builds on yakkety without modification, the package needs dependency modifications for xl2tpd and strongswan as indicated in the attached debdiff for yakkety"
1697934,2017-06-14 13:24:29 UTC,The package needs a number of compatibility fixes for xenial and like yakkety needs dependency modifications for xl2tpd and strongswan as indicated in the attached debdiff for xenial.
1697934,2017-07-23 10:08:25 UTC,yakkety is obsolete and will not accept new uploads
1697934,2017-07-23 10:14:16 UTC,Updated patch for network-manager-l2tp 1.2.8 on xenial
1697934,2018-05-03 23:39:53 UTC,Zesty is end of life
1697934,2019-11-05 21:41:33 UTC,"It is clear that the back-port of network-manager-l2tp 1.2.8-1 to xenial isn't going to happen, so status changed."
1697935,2020-05-18 17:47:45 UTC,https://review.opendev.org/#/c/662327/ took care of this.
1697935,2020-05-18 17:47:05 UTC,"Change abandoned by Eric Harney (<email address hidden>) on branch: master
Review: https://review.opendev.org/474205
Reason: Handled in
  https://review.opendev.org/#/c/662327/"
1697935,2017-06-14 13:47:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474205"
1697938,2017-06-14 14:00:37 UTC,PS: Here's the output of lspci -v showing that the nic is still there:
1697943,2017-06-14 14:57:04 UTC,"A few possibilities:
1) Catch the 'missing txn' error and handle it distinctly from other errors. Log it and just remove the TXN is an option, though it could lead to corruption that you could otherwise interpret from actions that you have been doing.
2) Special case Leases and Statuses which are where we get the most DB churn, and the most chance for missing TXNs. Both of those are cases where the 'current' value is the only one that is important, and the evolution over time isn't very interesting.
2a) do (1) on only leases/statuses
2b) on Jujud startup, purge all txns that are touching Leases and Statuses instead of trying to resume them. We'd want to do this at ~the time when we're doing Upgrade steps, before we allow anything to really be modifying the database."
1697943,2017-06-15 06:47:57 UTC,see also https://bugs.launchpad.net/juju-core/+bug/1697175
1697943,2017-07-07 12:24:51 UTC,"Also today on my 2.1.2 controller, there was a txn in state 2 to be applied on a non-existing document, and that led to huge txn-queues (with ~100k items). Is this is a good bug to track how Juju could work better around these ?"
1697943,2017-07-12 08:48:16 UTC,"This seems like an ok place where we want to track how we want to handle
invalid transactions."
1697943,2017-07-12 09:44:43 UTC,There were many surgeries done on the database since it got created.
1697949,2017-06-20 13:12:05 UTC,Confirmed. The volume group name doesn't seem to get saved to the database when editing it.
1697949,2017-06-14 15:45:20 UTC,"For the record, it's simple to circumvent this by updating the vgname in postgres:"
1697949,2019-09-19 11:53:18 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1697953,2017-06-27 08:31:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477821"
1697953,2019-06-26 21:48:21 UTC,The nova fix is being tested here: https://review.opendev.org/662327
1697953,2019-06-26 21:32:17 UTC,Looks like this is a duplicate of bug 1653953 which has a fix proposed here:
1697953,2018-07-27 08:30:59 UTC,"Change abandoned by Erno Kuvaja (<email address hidden>) on branch: master
Review: https://review.openstack.org/471352"
1697953,2017-10-23 11:45:33 UTC,"reproduced
        Body: None
    Response - Headers: {'status': '200', u'content-length': '1556', 'content-location': 'https://10.0.0.101:13774/v2.1/servers/cd83b1b9-6207-4c3a-892a-c8a060494060', u'x-compute-request-id': 'req-899731ef-29cc-41ac-876d-1bb436026850', u'vary': 'OpenStack-API-Version,X-OpenStack-Nova-API-Version,Accept-Encoding', u'server': 'Apache', u'openstack-api-version': 'compute 2.1', u'connection': 'close', u'x-openstack-nova-api-version': '2.1', u'date': 'Mon, 23 Oct 2017 11:42:20 GMT', u'content-type': 'application/json', u'x-openstack-request-id': 'req-899731ef-29cc-41ac-876d-1bb436026850'}
        Body: {""server"": {""OS-EXT-STS:task_state"": null, ""addresses"": {""tempest-ServerActionsTestJSON-1172139153-network"": [{""OS-EXT-IPS-MAC:mac_addr"": ""fa:16:3e:57:20:8e"", ""version"": 4, ""addr"": ""10.100.0.6"", ""OS-EXT-IPS:type"": ""fixed""}]}, ""links"": [{""href"": ""https://10.0.0.101:13774/v2.1/servers/cd83b1b9-6207-4c3a-892a-c8a060494060"", ""rel"": ""self""}, {""href"": ""https://10.0.0.101:13774/servers/cd83b1b9-6207-4c3a-892a-c8a060494060"", ""rel"": ""bookmark""}], ""image"": {""id"": ""8e57b8fa-871e-4299-a742-b6feedb5f016"", ""links"": [{""href"": ""https://10.0.0.101:13774/images/8e57b8fa-871e-4299-a742-b6feedb5f016"", ""rel"": ""bookmark""}]}, ""OS-EXT-STS:vm_state"": ""active"", ""OS-SRV-USG:launched_at"": ""2017-10-23T11:37:19.000000"", ""flavor"": {""id"": ""77b26b98-9182-4afc-8560-728bfd84e8ca"", ""links"": [{""href"": ""https://10.0.0.101:13774/flavors/77b26b98-9182-4afc-8560-728bfd84e8ca"", ""rel"": ""bookmark""}]}, ""id"": ""cd83b1b9-6207-4c3a-892a-c8a060494060"", ""security_groups"": [{""name"": ""default""}], ""user_id"": ""c3b9dd20a4eb4ee68b11dd5406722261"", ""OS-DCF:diskConfig"": ""MANUAL"", ""accessIPv4"": """", ""accessIPv6"": """", ""progress"": 0, ""OS-EXT-STS:power_state"": 1, ""OS-EXT-AZ:availability_zone"": ""nova"", ""config_drive"": """", ""status"": ""ACTIVE"", ""updated"": ""2017-10-23T11:37:19Z"", ""hostId"": ""c26060b2344c009f8c61122b329c9950178cc1c63a0bd1eaecf10f1c"", ""OS-SRV-USG:terminated_at"": null, ""key_name"": null, ""name"": ""tempest-ServerActionsTestJSON-server-1950192548"", ""created"": ""2017-10-23T11:36:25Z"", ""tenant_id"": ""25b0c5d99e784198ba5dbca95977d47f"", ""os-extended-volumes:volumes_attached"": [], ""metadata"": {}}}
}}}"
1697953,2019-02-18 09:44:43 UTC,"Marked invalid, no updates since last 6 months."
1697953,2017-07-13 07:57:18 UTC,Thanks Eric for information.
1697953,2017-07-11 15:52:43 UTC,See: http://logs.openstack.org/05/474205/3/check/gate-tempest-dsvm-full-devstack-plugin-ceph-ubuntu-xenial/69b8874/console.html
1697953,2017-07-11 15:52:06 UTC,This test still fails on Ceph RBD.
1697953,2017-07-11 13:45:11 UTC,This issue was fixed in the openstack/tempest 16.1.0 release.
1697953,2017-07-03 03:14:41 UTC,"Reviewed:  https://review.openstack.org/477821
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=43a40654f403237bc167d7b9d2edaf5a5188f147
Submitter: Jenkins
Branch:    master"
1697953,2017-07-26 16:42:16 UTC,See also:https://bugs.launchpad.net/nova/+bug/1653953
1697958,2018-01-28 16:49:53 UTC,Riparita per unplugging ĝin de la muro dum 10 sekundoj kaj konektante ĝin reen kaj ŝalti ĝin denove.
1697958,2021-02-23 20:48:49 UTC,Had the same issue on Ubuntu 18.04.5 LTS with hplip coming from Ubuntu repos.
1697958,2019-07-25 13:53:22 UTC,"Oh, and what exactly is a ""systemtray?"" All of a sudden, for the past year or so, the HP p1102w Pro has been eliciting an HPLIP error message saying that there is no ""systemtray"" and so it was stopping. I have no idea what a systemtray is. I obviously didn't lose a systemtray that was once there--all is like new in my old printer. Windows' driver makes no complaint about a systemtray but HPLIP in Linux is obsessed by it and the danger caused by it being missing. I don't want to be forced to go into Windows in order to print something. I have used Linux since 1997 and I don't want to have Linux suddenly fail to support my perfectly fine older HP printer that has been working fine under Linux for years."
1697958,2019-07-24 22:46:55 UTC,"For the first time in about 10 or 12 versions of Fedora, I cannot simply install my HP p1102w Laserjet Pro printer using HPLIP."
1697958,2018-01-28 14:54:14 UTC,"Mi uzas la presilon kutime per USB, sed hodiaŭ post presita horo antaŭe, ĝi subite ne presas ĉar ĝi diras min, ke ĝi haltis.
Se mi uzas hp-setup, la eraro aperas: error: No devices found on bus: usb
Sed lsusb diras: Bus 002 Device 009: ID 03f0:112a Hewlett-Packard"
1697958,2017-10-24 17:25:25 UTC,I've experienced this on Ubuntu 16.04.3 LTS and hplip 3.17.10. I tried the advanced and put in the printer's IP without success. localhost:631 does recognize the printer.
1697958,2017-11-04 19:20:26 UTC,"running hp-setup -g for debug mode shows the printer is recognized over the network but because its not found in the models.dat file the error showed is ""cant find printers on the network"""
1697958,2017-06-16 15:46:01 UTC,"A workaround seems to be to click the ""Show Advanced Options"" button in the Device Discovery window and change the Network Discovery Method to mDNS/Bonjour. It will successfully detect the printer with that method."
1697958,2017-06-16 16:27:01 UTC,"It seems that mDNS/Bonjour (aka DNS-SD) is more reliable than the method which HPLIP uses by default (SNMP? HP guys, am I correct?). DNS-SD is the more modern way to discover devices in the network and got standard for many device types, especially also printing. We have standardized driverless network printing concepts now (used by smartphones but currently also by desktops, including Ubuntu from 17.04 on) and they all use DNS-SD for printer discovery in networks. Also CUPS broadcasts shared printers via DNS-SD so that remote clients find them."
1697958,2017-12-10 09:28:51 UTC,I can confirm the behaviour as described by Dror Cohen - this is my result when adding a printer (the ENVY Photo 7100 series in that case) entering the IP address manuallly:
1697958,2017-08-18 14:09:24 UTC,"Hi Nick,
     Ubuntu 17.04 support is added in HPLIP 3.17.6. The packages which you are using 3.16.11 which doesn't support ubuntu 17.04.  Kindly install HPLIP 3.17.6 or the latest version and try."
1697958,2017-06-16 17:39:28 UTC,The current default discovery method is SLP.
1697958,2017-11-03 03:41:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697959,2017-06-15 07:54:31 UTC,"i'm not concerend about false positives arriving in the errors tracket, but it would be nice if they were marked as guessed version with like a question mark when there is UnreportableReason."
1697959,2018-05-29 23:34:54 UTC,Daniel van Vugt recently commented on a bug report about the errors bucket show a couple of crashes with the new package version and I'm concerned that those might actually be ones where the version collection was done after the package had been updated.
1697959,2019-04-05 17:09:03 UTC,When looking at bug 1822395 it occurred to me that this could also be an issue if an application were to crash during the release upgrade process and the data collection were done after the upgrade.
1697963,2017-09-04 13:53:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697969,2017-06-14 18:15:59 UTC,"protocol_id is expected to set by config/schema transformer, hence moved it to config.
/Prasad"
1697969,2017-06-14 18:24:16 UTC,Fixed with commit 5e415b8539206e7abdaee4e2acadc9747674aab3
1697980,2017-06-15 17:03:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1697983,2017-12-28 08:41:56 UTC,"I think I have taken up enough for myself for the 2.2 release with the effects system improvements. Does anyone else want to volunteer for this? Uwe? If not, let's remove it from the 2.2 milestone."
1697983,2017-06-14 20:17:08 UTC,"I think we should follow the Google syntax:
https://support.google.com/websearch/answer/2466433?hl=en
and use OR and AND"
1697983,2017-06-14 20:31:07 UTC,"Yeah, case sensitive ""OR"" would be easier to type while mixing."
1698001,2017-06-15 02:38:27 UTC,Changing the component for this bug.
1698001,2017-06-15 13:35:08 UTC,"@Erik: That is a weird log. It's putting the main storage as the first card, and the card as a second one. And of course, that won't work. Does it work OK without the SD card? Has it worked with the SD card in previous versions of calibre?"
1698001,2017-06-15 16:12:17 UTC,"Removing the SD did the trick, never happened before. I do not use it to save books so no problem. So is it a bug in Calibre or on my device?"
1698001,2017-06-15 04:24:19 UTC,"@davidfor: I have implemented a possible fix, see https://github.com/kovidgoyal/calibre/commit/f65e372828b42b60547569e8c56e12f3768aca7f"
1698002,2018-06-29 09:34:10 UTC,From https://bugs.launchpad.net/catfish-search/+bug/1698002
1698002,2019-07-22 20:04:49 UTC,Sean Davis referenced this bugreport in commit 01aa98ff32259ac45bd343d8ad55d21c79d5cea0
1698002,2019-07-22 20:05:15 UTC,Feature implemented in the above commit.
1698004,2018-06-29 09:35:48 UTC,From https://bugs.launchpad.net/catfish-search/+bug/1698004
1698004,2019-01-28 13:24:31 UTC,"Created attachment 8272
Fixes the fulltext search for non UTF-8 text files"
1698021,2017-06-27 10:54:24 UTC,"We could try to fix it by filtering out control chars as done here: https://stackoverflow.com/questions/8733233/filtering-out-certain-bytes-in-python
Note that there is a regex solution that is listed as the second answer that is much faster than the accepted answer..."
1698021,2017-10-28 10:09:25 UTC,"Finally worked out how to reproduce this. Create a string with '\x0b'
 (vertical tab) and then paste that in to the song edit window and save!"
1698023,2018-05-14 14:58:30 UTC,Is there a workaround for this issue?
1698023,2018-05-14 15:10:27 UTC,This is a workaround for the issue:
1698023,2018-05-14 16:07:15 UTC,Please don't do that.
1698023,2018-05-18 22:28:03 UTC,@cyphermox: Why should the user have to maintain nameservers in two separate places?  netplan should support this and I don't think it belongs in systemd.  Thanks for your help.
1698023,2018-09-03 18:59:30 UTC,"There seem to be a number of workarounds on the Web, and most of them revolve around modifying either the netplan config file or the systemd resolver config. None really worked for me -- usually, the resolver configuration did not survive a reboot."
1698023,2018-09-03 20:27:26 UTC,"Mark, this bug is solely about the lack of support for top-level declarations of DNS preferences in netplan.  At most, the consequence is that you must repeat yourself in the netplan config.  That's suboptimal and a bug we should fix, but I don't see any reason one should ever work around it by making resolve.conf immutable."
1698023,2018-09-04 15:26:12 UTC,"Steve: Maybe my comment does not really belong here, I agree. I admit that I have not fully investigated the problem -- the problem in my case being that a configuration with static IP does not appear to set the DNS correctly, either via netplan (and networkd) or via systemd's resolver. A web search for this problem reveals that I am not the only one."
1698023,2018-09-04 16:05:57 UTC,"On Tue, Sep 04, 2018 at 03:26:12PM -0000, Mark Rodgers wrote:

> Steve: Maybe my comment does not really belong here, I agree. I admit
> that I have not fully investigated the problem -- the problem in my case
> being that a configuration with static IP does not appear to set the DNS
> correctly, either via netplan (and networkd) or via systemd's resolver.
> A web search for this problem reveals that I am not the only one.
"
1698023,2018-03-04 08:09:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698036,2020-06-23 08:03:02 UTC,"I have retry it in libvirt 3.9.0, and it seems already fixed."
1698036,2017-06-29 18:53:42 UTC,closing. please retarget ceilometer if you think this isn't a libvirt fix.
1698036,2017-06-19 14:08:53 UTC,"considering you're using libvirt and not ceilometer in the description, i imagine this is solely a libvirt issue?"
1698037,2017-09-15 21:48:09 UTC,Bug still present in 55.0.2+build1-0ubuntu0.17.04.1
1698042,2017-06-15 04:42:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1698042,2017-06-16 02:52:22 UTC,"1. I assume the module nouveau is part of the kernel
2. I selected the kernel as close as possible to the current version; I don't know exactly which one it is since it doesn't boot.
3. Behavior described is what happens on 16.04.2 and 17.04"
1698050,2017-06-22 06:42:51 UTC,"Looking at xenial by comparison, it appears not that the disabled colour has changed, but that the disabled buttons are now placed on a lighter background."
1698051,2020-10-22 19:50:12 UTC,closing since the package is removed from Ubuntu
1698068,2020-08-27 17:40:51 UTC,"Core20 should limit the pull step to ""source"" pulling. There is no longer any plugin-specific pull steps."
1698068,2020-06-01 16:09:13 UTC,"Just a quick update on this one, the current support for overrides hasn't really helped all that much."
1698068,2017-09-05 21:08:36 UTC,A follow-up on this: we're planning on adding before/after scripts for each lifecycle step. This is something that would be best done in an `after-pull` script. As soon as that lands this will become less hacky.
1698068,2017-06-15 22:04:34 UTC,"As the upstream, it feels pretty weird to fork our own code just to include some cherry-picks that are already in our tree."
1698068,2017-06-15 23:45:25 UTC,"Ok, so I just changed our snap to use the prepare step and indeed, for Go it's not good enough, the patches are applied before ""go install"" but I'm guess snapcraft must copy the git tree to the gopath prior to that, so ""go install"" doesn't rebuild the modified code and we end up with an unpatched binary."
1698068,2017-06-15 22:30:58 UTC,"Another option (for some projects) might be to use the `prepare` script, something like so:"
1698068,2017-06-15 21:39:59 UTC,"I think this sort of falls under patching versus forking discussion, where we have historically leaned toward saying fork instead of patch. In this case, apply those commits to another branch and use that instead of lxd-2.14."
1698068,2017-06-16 00:01:23 UTC,"Just found a workaround for that, having ""prepare"" do ""cd ../src"" so that it updates the tree that's actually used by ""go install""."
1698068,2017-06-15 22:56:28 UTC,"Ah yeah, something like that would be fine.
It may still be fine for go. We don't introduce new dependencies in our cherry-picks, so having it run after ""go get"" but before ""go build"" should be fine."
1698077,2020-10-29 07:05:14 UTC,this seems to be fixed (although i cannot tell since when)
1698083,2018-05-04 01:31:32 UTC,"""Expired"" is a misnomer. It just moved to https://gitlab.gnome.org/GNOME/gtk/issues/539"
1698083,2017-07-17 03:29:34 UTC,"OK, so there are a few steps to fixing this bug:"
1698083,2017-07-17 03:30:17 UTC,It appears all middle-click titlebar actions don't work when in a Wayland session.
1698083,2017-10-13 08:03:58 UTC,"Actually this bug is only GTK apps on Wayland, so -> https://bugzilla.gnome.org/show_bug.cgi?id=746273"
1698083,2017-11-16 18:57:36 UTC,"This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'."
1698083,2018-02-20 15:24:23 UTC,"This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'."
1698083,2018-03-29 16:27:09 UTC,I'm using Ubuntu 17.10 and this bug is still present with Xorg AND Wayland.
1698083,2019-05-02 22:07:09 UTC,"This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'."
1698083,2018-04-03 02:40:08 UTC,Yes I can confirm that. But I think it should be discussed in a different bug report.
1698083,2020-04-28 09:20:49 UTC,This is one of the top most wayland itches as per https://hansdegoede.livejournal.com/21944.html where it points to few other bugtrackers:
1698083,2017-07-17 03:23:10 UTC,"Aha! It appears this feature only works in Xorg sessions (""Ubuntu"") and not in ""Ubuntu on Wayland"" sessions."
1698083,2018-04-20 03:17:11 UTC,"Sorry, I was wrong."
1698083,2018-04-25 08:31:33 UTC,"Observation on Ubuntu 18.04 :
- All work good on Xorg session
- Problem only affect Wayland session
- Classic windows with traditional decoration (chromium, pidgin, inkscape, ...) accept middle-click action
- GTK3 apps with Headerbar decoration who use CSD (Client Side Decoration) ignores middle-click
- Don't know why, but Evolution 3.28.1-2 ignores middle-click too (but have traditional decoration !)"
1698083,2018-04-26 01:36:44 UTC,"We know it's broken (and more so in Wayland sessions). For more up to date information, please see the upstream bug instead:"
1698083,2018-05-03 13:02:06 UTC,"Please change it to ""confirmed"". That's still a relevant issue."
1698083,2018-04-19 16:15:23 UTC,Why is this another bug?
1698083,2018-04-20 01:34:15 UTC,"Because middle click actions do work in Xorg sessions, and only fail in Wayland. If you find something is broken in a Xorg session then it is not this bug."
1698083,2017-07-17 03:20:39 UTC,"I take it back. It works randomly, sometimes."
1698083,2017-06-23 17:41:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698083,2016-06-23 02:28:42 UTC,"Description of problem:
I have focus-follows-mouse and no-raise-on-click. Under X, I can click on a title bar and the window raises. Under Wayland, this does not work for Gnome windows."
1698083,2016-06-23 07:17:39 UTC,"I wonder if this related to CSD, because with CSD mutter does not own the titlebar (it's all managed by the client) and under Wayland clients cannot manipulate the stack by themselves."
1698083,2016-06-23 07:24:01 UTC,"Humm, indeed, if you turn off ""raise-on-click"", the client cannot raise itself but that seems pretty much to be expected."
1698083,2016-06-23 08:07:28 UTC,Note the lengthy description of that option which make it very clear that this option should not be changed:
1698083,2016-06-23 12:17:53 UTC,Thanks for the investigation! I will follow the upstream bug.
1698083,2017-07-17 02:23:37 UTC,Seems to have started working in the past week or so. :)
1698083,2016-07-05 12:04:24 UTC,"(In reply to Adam Goode from comment #5)

> [...]
>
> Can extending the xdg-shell protocol to add raise/lower commands (and
> implementing in GDK) be considered a wayland-as-default blocker in Fedora?
> This is a regression though not in the default GNOME settings.
"
1698083,2016-07-04 15:50:44 UTC,Here is a summary of the upstream bug:
1698083,2016-11-28 20:18:57 UTC,"I can confirm that I can no longer lower windows after upgrading from Fedora 24 to Fedora 25. This is a serious problem for me, as I've been doing this in Linux for 22 1/2 years (since May 1994). My dconf-editor action-middle-click-titlebar setting is and continues to be 'lower'. I frankly don't care what mouse button or keystroke I need to use to lower windows, but this functionality has to be present for the desktop to be usable if you use auto raise. One of the reasons I deleted Windows entirely over two decades ago was that I despised click-to-focus."
1698083,2016-11-28 20:36:16 UTC,You should still be able to go back to X11 under Fedora 25. The solution is to implement the missing functionality in the wayland xdg-shell protocol.
1698083,2016-11-29 02:35:36 UTC,Switching back to X11 fixed the issue.
1698083,2016-11-29 02:37:42 UTC,5) The bottom area where you can set bandwidth constraints is missing with Wayland. This is critical in the office if you need to download a large torrent but you have a shared environment and you can't kill everybody else.
1698083,2016-11-29 03:32:05 UTC,"Yes, please file separate bugs for these Azureus issues."
1698083,2016-12-19 13:13:31 UTC,"(In reply to John Gotts from comment #11)

> Switching back to X11 fixed the issue.
"
1698083,2016-12-19 20:50:21 UTC,"You can follow along on the gnome bug:
https://bugzilla.gnome.org/show_bug.cgi?id=767967"
1698083,2016-11-25 04:51:22 UTC,"It's not just CSD.  Another problem resulting from Wayland not allowing clients to raise or lower themselves is that many desktop notification actions are now no-ops.  For example, clicking on Evolution's ""You have # new messages"" notification used to raise the message list window.  Gnome-terminal's command-completed notification used to raise the window that just finished.  Now both just dismiss the notification."
1698083,2016-07-05 15:41:08 UTC,This is an issue even when not using no click-to-raise. action-middle-click-titlebar is also broken.
1698084,2017-06-16 17:09:56 UTC,"Could be a loading problem.
The system loads tiles upto a certain distance from the train. If you run very fast you pass through the tiles so quick it may be the system just doesn't have enough time to load all data."
1698085,2017-06-15 07:28:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474468"
1698089,2017-08-22 13:47:33 UTC,Thanks Manas! Yours now.
1698089,2017-08-22 06:05:26 UTC,Any review comments on the bug??
1698089,2017-06-15 12:32:27 UTC,Hi Manas:
1698089,2017-06-16 05:06:27 UTC,"I have the code fixed already, once you accept the bug then I can raise code review for this fix."
1698089,2017-06-16 05:04:53 UTC,Input file:
1698089,2017-08-30 06:16:36 UTC,Raised the code review: https://review.openstack.org/#/c/499035/1
1698089,2017-06-16 05:04:10 UTC,The Key  value pair as in Interface for the VDU4 for the  VDU_ip: { get_input: VDU_IP } is not replaced by the input file.
1698089,2017-06-16 05:03:13 UTC,topology_template:
1698090,2020-11-22 16:03:52 UTC,"@Thanye, I've checked the stack trace above again, and then inspected the git history since 2.4.6 has been released in 2016, and only the following commits have touched the src/datasource/cmdline.c file:
- 4b4ab04 Sun Oct  4 2020 +0200  GH #157: Fix (potentially*) incorrect malloc size in cmdline
- ede16a4 Mon Nov 25 2019 +0000  correct pointer vs byte compare in cmdline.c
- e989f26 Thu Jul 27 2017 +0200  Make snoopy compile on 64-bit Arch Linux with GCC 7.1.1"
1698090,2020-11-22 05:57:16 UTC,"I can look at seeing if it can be reproduced with a newer version. 2.4.6 would be easier to test than 2.4.9, since it is in the apt repos for 18.04 and 20.04, but I might be able to compile 2.4.9 as well."
1698090,2017-06-19 08:22:26 UTC,We found the bug. The problem was the syslog-ng configuration file.
1698090,2018-03-06 04:44:04 UTC,"I'm not sure if this is the same issue. But while running BitBucket we got a segfault about once a day (and had to restart bitbucket), until we figured out it was coming from snoopy code and disabled snoopy on the host."
1698090,2018-03-06 04:39:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698090,2020-11-22 02:48:14 UTC,"@Thayne, can this one be reproduced with the latest Snoopy versions (2.4.9)? If so, can you provide either a patch that fixes it, or a method that I can use to reproduce the issue locally?"
1698091,2017-08-30 02:19:22 UTC,"Alternatively, shfmt recommends maintaining the same indentation level for each pattern as the opening ""case"" keyword. Yes, this is a somewhat subjective choice, but as there is now a semistandard tool for styling shell script code, we might as well follow it:"
1698091,2017-08-30 17:45:12 UTC,"shfmt is a new one, hadn't heard of it. I don't know how widespread their standard is."
1698094,2017-07-14 08:13:10 UTC,thanks for finding - fixed
1698099,2017-06-16 08:39:40 UTC,have you executed 'source ~/devstack/openrc'? It seems good in my environment.
1698099,2017-06-19 02:15:37 UTC,"Yes, I already 'source ~/devstack/openrc', and my environment is Ubuntu 16.04.2 LTS server version.  I found a possible error, it is I could not get 'RC_DIR' on line 21 in openrc when I source file."
1698099,2017-06-19 08:02:59 UTC,"Sorry, after my testing, I could get 'RC_DIR' value. The reason of $DEFAULT_IMAGE_NAME is empty, because local.conf set 'VIRT_DRIVER=ironic', the case VIRT_DRIVER didn't has option 'ironic' in  'devstack/stackrc', line 699."
1698114,2017-06-15 12:27:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1698114,2020-06-05 14:29:42 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1698114,2020-07-10 12:41:32 UTC,No response after approximately 35 days and as bug report contained no version/release information will now close.
1698130,2017-06-15 12:20:38 UTC,"From talking with mskalka it may just be that v6 is disabled on the host machines so we pick v6 when its available and then v4, but the host machines don't have v6 addresses."
1698132,2020-03-22 15:45:33 UTC,"What information is required for Status Incomplete?
This problem still persists in 18.04 Mate 1.20.1"
1698132,2018-08-12 17:20:28 UTC,"@Cristian (vmman)
It is called natural because if you push your finger on the mouse wheel UP, whats on the screen moves UP. Just like if you had a piece of paper on a table, if you pushed it UP, and it moved DOWN, that would be a very strange experience!"
1698132,2018-01-03 16:12:26 UTC,"I'm not sure what you mean by natural? But right now there's no option the roll 2-4 lines at the time when scrolling the scroll wheel in the web browser. Only option is to scroll a whole page at the time, which makes scrolling a news feed, i.e on facebook impossible."
1698140,2019-08-19 19:51:33 UTC,Workaround is to copy the template from /snap/mojo/current/usr/share/mojo/contrib/spec-template/ ? Or is there more to the new-spec command?
1698159,2019-04-25 10:50:00 UTC,This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.2
1698159,2019-04-09 17:10:09 UTC,"@jarnos(#20) The running kernel's related packages are protected by u-u. There are the packages protected by apt, which are also not offered for autoremoval, hence u-u would not remove them either.
When the kernel package for -39- is protected by apt in /etc/apt/apt.conf.d/01autoremove-kernels u-u does not remove it either."
1698159,2019-03-19 14:41:53 UTC,I have Unattended-Upgrade::Remove-Unused-Dependencies set to default value (false) and u-u 1.1ubuntu1.18.04.7~16.04.2 did not remove linux-hwe-cloud-tools-* package related to non-running protected kernel either.
1698159,2019-03-19 12:20:08 UTC,"@rbalint it says ""Keeping the following auto-removable package(s) because they include linux-cloud-tools-4.15.0-39-generic which package is related to the running kernel: linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39""."
1698159,2019-03-13 18:20:02 UTC,Tested with 1.1ubuntu1.18.04.7~16.04.2:
1698159,2019-02-28 12:58:45 UTC,"Hello Ian, or anyone else affected,"
1698159,2018-12-13 15:50:20 UTC,"Hello Ian, or anyone else affected,"
1698159,2018-12-03 19:17:03 UTC,"Hello Ian, or anyone else affected,"
1698159,2018-10-25 15:29:44 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1698159,2018-10-25 15:29:32 UTC,This bug was fixed in the package apt - 1.2.29
1698159,2019-03-28 10:33:38 UTC,Related bug report: Bug #1607845
1698159,2018-10-17 22:26:04 UTC,"Hello Ian, or anyone else affected,"
1698159,2018-10-02 08:15:22 UTC,"Hi,"
1698159,2018-10-01 18:35:05 UTC,"Hello Ian, or anyone else affected,"
1698159,2018-10-01 18:33:32 UTC,Thanks! Would it be maybe possible to actually check if the cloud-tools packages aren't auto-removed by unattended-upgrades as well besides just looking at the APT::NeverAutoRemove rules?
1698159,2018-10-01 18:09:18 UTC,"We would need some SRU information here. Since this is part of the xenial apt SRU, we'd need to have reliable testing steps for verification of the update. Thank you!"
1698159,2018-07-17 07:06:30 UTC,Cherry-picked the change into xenial's 1.2.y branch for the next SRU. Will do that in trusty too.
1698159,2018-03-06 09:46:20 UTC,This bug was fixed in the package apt - 1.6~beta1
1698159,2018-03-01 16:32:49 UTC,This bug was fixed in the package unattended-upgrades - 1.0ubuntu1
1698159,2018-02-23 15:20:21 UTC,apt fix committed: https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=923ba67464960940a19b24a341e896a9338161fb
1698159,2018-02-22 16:27:28 UTC,I'm testing the fix for u-u right now that will rely on apt's one. The u-u fix will land soon in the git repository.
1698159,2018-02-14 18:32:25 UTC,"Yes, indeed, the packages should be kept but 01autoremove-kernels is generated by /etc/kernel/postinst.d/apt-auto-removal which is shipped by apt.
Reassigning to apt."
1698159,2018-10-18 12:22:36 UTC,"Marking verification-done-xenial again, this got reset by 1.2.29."
1698161,2017-06-15 15:08:07 UTC,i can not instal the Ubuntu software updates
1698181,2017-06-15 19:29:44 UTC,"I just learned that this doesn't need changes in cloud-init, or shouldn't.  I was target this to ubuntu-meta for ifupdate to be removed from the seed in 17.10.  From that we should just switch to netplan like magic. ;)  I'll let the owners of the other affected packages close their own bits of this bug once they've evaluated the impact."
1698181,2017-06-15 18:20:05 UTC,Closing the LXD task but subscribing the ubuntu-lxc team.
1698181,2018-04-28 12:49:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698181,2017-10-31 19:28:19 UTC,"re: comment #14 (for future readers), please keep the discussion over on:"
1698181,2017-06-15 17:59:07 UTC,Marking lxd and maas as affected here as well to be aware of downstream effects.
1698181,2017-10-03 14:53:23 UTC,What is outstanding for MAAS?
1698181,2017-10-03 14:52:54 UTC,lxc templates got fixed to use netplan in artful.
1698181,2017-10-03 14:52:16 UTC,All cloud images do not have ifupdown installed and thus default to netplan.
1698181,2017-10-31 15:28:53 UTC,"For 17.10 forward, due to netplan being incomplete and lacking too many features, it is unsuitable for production use. What packages need to be added/removed to drop netplan and restore full network functionality as it existed in 16.04?"
1698181,2017-10-03 14:51:16 UTC,"resolvconf/resolved have updated integration which each other. Such that things work better, with default tipped to resolved. And for example removing resolvconf switches to using resolved."
1698181,2017-07-26 17:11:48 UTC,"On Wed, Jul 26, 2017 at 04:48:22PM -0000, Scott Moser wrote:

> I think that resolvconf should be listed here, as it Depends on ifupdown.
> also resolvconf is rdepend'd on by ubuntu-minimal, so I think that
> ubuntu-meta probably needs another bump.
"
1698181,2017-07-26 16:53:08 UTC,"apt-get upgraded lxc container just now, shows:"
1698181,2017-07-26 16:48:22 UTC,"I think that resolvconf should be listed here, as it Depends on ifupdown.
also resolvconf is rdepend'd on by ubuntu-minimal, so I think that ubuntu-meta probably needs another bump."
1698181,2017-07-26 16:44:13 UTC,marking cloud-init fix-released under bug 1705639.
1698181,2017-10-03 14:51:44 UTC,ifupdown/isc-dhcp is fixed to supplied dns servers to resolved instead of resolvconf
1698181,2017-06-20 14:18:42 UTC,This is now in place:
1698186,2017-06-27 14:56:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698186,2017-06-27 14:57:24 UTC,I don't know anything about the bug.  This report was automatically generated.
1698187,2019-05-08 04:50:25 UTC,"This seems like a case where destroy-machine --force gets you into trouble
because it doesn't wait for an ack from the machine agent before it starts
removing machine records. I would have thought we would still ensure that
machines instances are destroyed."
1698187,2019-05-07 04:53:22 UTC,Do you have a repro scenario? Could you easily test it on the latest Juju version?
1698187,2019-05-08 07:42:16 UTC,I see. I'll try to reproduce to confirm if it is still an issue... maybe get some metric of performance for benchmarking.
1698198,2017-06-15 19:30:39 UTC,"Results for additional infos
-----------------
echo ""lsb_release -rd"" > log.txt
lsb_release -rd >> log.txt 2>&1
echo ""apt-cache policy xserver-xorg-video-nouveau"" >> log.txt
apt-cache policy xserver-xorg-video-nouveau  >> log.txt 2>&1
echo ""dmesg"" >> log.txt
dmesg >> log.txt 2>&1
-----------------"
1698198,2017-06-15 19:38:25 UTC,"Bug appeared with new kernel release
ls -l /
lrwxrwxrwx   1 root root          30 juin   6 20:00 vmlinuz -> boot/vmlinuz-4.10.0-22-generic
lrwxrwxrwx   1 root root          30 mai   18 08:07 vmlinuz.old -> boot/vmlinuz-4.10.0-21-generic"
1698198,2017-09-16 01:52:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698202,2017-06-16 18:01:17 UTC,"Reviewed:  https://review.opencontrail.org/32897
Committed: http://github.com/Juniper/contrail-puppet/commit/dd30e9759af990d2be53a0994ef52bf8de63216b
Submitter: Zuul (<email address hidden>)
Branch:    R3.2.3.x"
1698202,2017-06-16 00:54:40 UTC,"Review in progress for https://review.opencontrail.org/32896
Submitter: Dheeraj Gautam (<email address hidden>)"
1698202,2017-06-16 17:58:06 UTC,This is broken in build 3 as build 2 provision went through without any issues.
1698202,2017-06-16 00:55:01 UTC,"Review in progress for https://review.opencontrail.org/32897
Submitter: Dheeraj Gautam (<email address hidden>)"
1698202,2017-06-16 18:01:09 UTC,"Reviewed:  https://review.opencontrail.org/32896
Committed: http://github.com/Juniper/contrail-puppet/commit/29868698cdf91b854c53a7273a5daaa55a957731
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1698208,2017-06-16 00:31:51 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1698208,2017-06-16 01:00:04 UTC,This change was made by a bot.
1698208,2017-06-16 00:31:35 UTC,"Hello havard, do you have a reason for isc-dhcp-server to be installed on this machine? It feels like a potential mistake."
1698222,2017-06-16 04:23:28 UTC,"The attachment ""1698222.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1698222,2017-06-16 14:38:48 UTC,"Thanks for working on this, there is a typo in the changelog entry of the word ""running"" that might be worth fixing."
1698222,2017-06-16 16:21:17 UTC,Brian -- thanks!  I'm getting a sponser on the git merge request I put in over here:
1698222,2017-06-16 16:59:57 UTC,"David fixed the typo before submitting the MP, and I've sponsored using the git tooling. Thanks!"
1698226,2018-01-12 19:05:00 UTC,Unassigning due to no activity for > 6 months.
1698241,2017-06-16 13:20:54 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1698241,2017-06-15 23:42:38 UTC,Cannot run apport-collect.
1698241,2017-06-15 23:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1698241,2017-06-19 20:45:06 UTC,This warning does not occur on the Ubuntu 4.8 kernel.
1698248,2017-06-16 04:41:02 UTC,https://github.com/lathiat/avahi/issues/41
1698248,2021-01-10 22:56:52 UTC,"On my network, tcpdump suggests this happened in response to the router sending an IPv6 router advertisement every few minutes, and was stopped after:"
1698248,2017-06-16 04:40:42 UTC,"This is known upstream but not yet solved, working on it I have a theory"
1698249,2017-06-16 03:17:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474837"
1698249,2017-06-16 03:21:36 UTC,"This pr is already merged in kolla-ansible.
related issue : https://bugs.launchpad.net/kolla-ansible/+bug/1693692"
1698249,2018-06-07 09:32:51 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/474837"
1698254,2017-06-19 20:11:30 UTC,"Do you have a link to the doc where this should be mentioned? Also, please mark as public, I don't think this needs to be marked private."
1698254,2017-06-27 17:43:02 UTC,in this doc https://docs.openstack.org/ocata/config-reference/compute/hypervisor-vmware.html#networking-with-vmware-vsphere
1698256,2017-06-23 01:42:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698256,2017-06-23 01:16:40 UTC,"I upgraded to the newly released Meson build 0.41.1 (from 0.40.1), and this isn't a problem anymore..."
1698256,2017-06-23 01:43:02 UTC,"I had the same issue. I'm assuming a regression in Meson, but I haven't checked."
1698261,2017-05-22 20:27:14 UTC,"Created attachment 58254
this is with ClientSdkFireWallHelper.exe renamed"
1698261,2017-05-24 21:13:38 UTC,"(In reply to Evren from comment #14)

> Here, https://us.battle.net/forums/en/starcraft/topic/20754425833 Blizzard
> dev suggests checking/allowing StarCraft.exe on the firewall using the
> following command. (ClientSdkFirewallHelper.exe should be within the same
> folder with StarCraft.exe)
>
> ""ClientSdkFirewallHelper.exe -allow [Path to starcraft.exe]""
"
1698261,2017-06-15 05:14:17 UTC,I tried a clean 16.04 Ubuntu install and this bug is gone. I did roughly the same steps as a clean 17.04 install which had this bug. This is regression in Ubuntu 17.04
1698261,2017-05-29 06:35:13 UTC,I installed a fresh Ubuntu 17.04 on a separate hard drive; installed 32 bit drivers and installed the game fresh. I'm still running into this issue.
1698261,2017-06-15 08:19:58 UTC,"(In reply to Igor Polyakov from comment #20)

> I tried a clean 16.04 Ubuntu install and this bug is gone. I did roughly the
> same steps as a clean 17.04 install which had this bug. This is regression
> in Ubuntu 17.04
"
1698261,2018-03-08 09:58:33 UTC,"(In reply to winetest from comment #25)

> Someone said bug 2467 is the same as this bug here.
"
1698261,2017-08-24 22:06:21 UTC,This bug also affects StarCraft Remastered v1.20.2.2660 using wine 1.15 (staging).
1698261,2017-08-25 07:51:00 UTC,"Yes, installing Ubuntu 16.04 instead of 17.04 resolved my issue."
1698261,2018-03-08 09:56:24 UTC,Someone said bug 2467 is the same as this bug here.
1698261,2018-10-28 19:26:23 UTC,"Looking at this and the upstream bugreport you didn't use the Ubuntu Wine packages, but wine-staging from upstream (since only the latter allows to even install StarCraft Brood War).  Therefore closing for ""Wine in Ubuntu""."
1698261,2017-05-22 20:14:37 UTC,"Created attachment 58253
Firewall calls"
1698261,2017-06-16 00:49:34 UTC,"(In reply to winetest from comment #21)

> (In reply to Igor Polyakov from comment #20)
> > I tried a clean 16.04 Ubuntu install and this bug is gone. I did roughly the
> > same steps as a clean 17.04 install which had this bug. This is regression
> > in Ubuntu 17.04
>
> Does your wine versions match also if you build from source do you have the
> same configuration at compile time?
"
1698261,2017-05-22 20:13:20 UTC,"I tried this, but renaming the file only gave me the prompt. The Battle.net menus are still slow. I reverted the change and ran it with WINEDEBUG set to +relay. I can't attach the whole file, since it's 400MB. I'll attach the relevant lines."
1698261,2017-08-28 21:06:54 UTC,I confirm the bug. In lubuntu 17.04 after installing starcraft as described in https://appdb.winehq.org/objectManager.php?sClass=version&iId=35639 i have experienced ~30 lag in every battlenet window.
1698261,2017-05-22 16:47:31 UTC,"I have the same issue - running Fedora 25, GNOME X11, on a Intel CPU with HD3000 integrated graphics."
1698261,2017-05-12 13:20:38 UTC,"Created attachment 58153
first file that gets loaded"
1698261,2017-05-12 13:21:54 UTC,"Created attachment 58154
second file that gets loaded"
1698261,2017-05-12 13:23:24 UTC,"Created attachment 58156
The logs starting from when you go to the battle.net menu up until it gets loaded"
1698261,2017-05-12 14:56:31 UTC,"(In reply to Igor Polyakov from comment #0)

> I built this version of Wine to run StarCraft 1.18:
> https://github.com/awesie/wine-starcraft
>
"
1698261,2017-05-12 15:23:19 UTC,"(In reply to Olivier F. R. Dierick from comment #4)

> This is a custom patched wine version.
> Please retest with plain wine or wine-staging (development version is
> currently 2.7).
"
1698261,2017-05-13 07:29:06 UTC,@Igor I still didn't experience this behaviour. Can I provide any information about my setup that might help find the cause?
1698261,2017-05-12 13:22:24 UTC,"Created attachment 58155
third file that gets loaded"
1698261,2017-05-13 10:02:25 UTC,"(In reply to Igor Polyakov from comment #7)

> (In reply to Tim from comment #6)
> > @Igor I still didn't experience this behaviour. Can I provide any
> > information about my setup that might help find the cause?
>
> Sure, I'd like to see who has this issue and who doesn't. I am on Ubuntu
> 17.04, I have an Intel i7-4770k processor and an AMD R9 290 graphics card.
"
1698261,2017-05-13 13:11:57 UTC,I built it with LXC like it says here https://wiki.winehq.org/Building_Biarch_Wine_On_Ubuntu
1698261,2017-05-14 16:05:56 UTC,"Hi Igor,
I created a custom installer for StarCraft 1.18.x on Ubuntu using the latest wine-staging source code. Andrew's build was based on 2.6, this uses 2.7 and you don't need to set XP mode for StarCraft.exe .It works with Global Settings (Windows 7) Actually, it crashes if you do otherwise :)"
1698261,2017-05-15 06:34:54 UTC,I just tried the script. It worked well to install the game and get to run. But it does not actually fix the issue.
1698261,2017-05-19 22:11:12 UTC,"I tried running this on 2.8 staging, I'm still getting this issue. I also switched to LXDE and that didn't affect it."
1698261,2017-05-13 08:10:24 UTC,"(In reply to Tim from comment #6)

> @Igor I still didn't experience this behaviour. Can I provide any
> information about my setup that might help find the cause?
"
1698261,2017-05-22 19:42:36 UTC,"(In reply to R Domingues from comment #13)

> I have the same issue - running Fedora 25, GNOME X11, on a Intel CPU with
> HD3000 integrated graphics.


Hi,"
1698264,2017-06-17 01:34:51 UTC,"Seth, I was able to try the Kernel provided by you (4.4.0-1019-aws) and it worked fine."
1698264,2017-07-17 11:57:59 UTC,This bug was fixed in the package linux - 4.10.0-28.32
1698264,2017-07-17 11:38:54 UTC,This bug was fixed in the package linux - 4.8.0-59.64
1698264,2017-07-14 09:03:59 UTC,"Given the nature of the issue, which is difficult to reproduce, and the fact that the fix is upstream, I'm changing the tags to verification-done-{yakkety,zesty} so we don't need to verify it on these two series."
1698264,2017-07-13 14:08:00 UTC,"Marked Xenial series as 'Fix Released' since the fix, commit b9a985db98961ae1ba0be169f19df1c567e4ffe0 upstream (pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes), has been included as part of update to 4.4.70 stable release (bug #1694621)."
1698264,2017-07-10 08:23:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1698264,2017-07-10 08:22:30 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed-yakkety'."
1698264,2017-06-19 12:26:01 UTC,"Yes, it should definitely be fixed before we release 16.04.3."
1698264,2017-06-16 16:08:29 UTC,I've tried reproducing this but haven't had luck. Something about my test environment must make it difficult to hit the issue.
1698264,2017-06-16 11:46:02 UTC,apport information
1698264,2017-06-16 11:46:04 UTC,apport information
1698264,2017-06-16 04:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1698264,2017-06-16 11:45:54 UTC,apport information
1698264,2017-06-16 11:45:55 UTC,apport information
1698264,2017-06-16 11:45:52 UTC,apport information
1698264,2017-06-16 11:45:57 UTC,apport information
1698264,2017-06-16 11:45:58 UTC,apport information
1698264,2017-06-16 11:46:00 UTC,apport information
1698264,2017-06-16 11:46:01 UTC,apport information
1698264,2017-06-16 11:45:56 UTC,apport information
1698267,2017-06-28 01:06:13 UTC,"We've been happily using include-file with multi-line files for years to configure e.g. haproxy, squid, ubuntu-mirror, .  Please supply a test case demonstrating the failure."
1698267,2020-12-23 04:17:19 UTC,[Expired for Mojo: Continuous Delivery for Juju because there has been no activity for 60 days.]
1698270,2017-10-31 12:39:09 UTC,"The attachment ""totem-pl-parser_3.26.0-1ubuntu2.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1698270,2017-12-05 13:13:04 UTC,This bug was fixed in the package totem-pl-parser - 3.26.0-1ubuntu2
1698270,2018-02-14 04:48:57 UTC,"I suspect there's another issue specific to Xorg that's causing stutter there, and not yet resolved. Although you won't see it till bug 1747744 is fixed :)"
1698270,2018-02-15 20:01:36 UTC,This bug was fixed in the package gtk+3.0 - 3.22.28-1ubuntu1
1698270,2017-10-31 09:31:38 UTC,A fix for bionic.
1698270,2018-08-21 20:04:07 UTC,"After gnome-twitch flatpak update (and some other ""core"" flatpak packages update) now I have same lags in gnome-twitch.
The bug comes from gnome. Just like most of bugs in Ubuntu and other distros."
1698270,2018-04-12 11:19:11 UTC,"Progress! I think...
https://bugzilla.gnome.org/show_bug.cgi?id=795195"
1698270,2018-04-17 09:54:01 UTC,"Maybe this is a better upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=795325"
1698270,2018-07-10 17:55:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698270,2019-03-04 02:10:58 UTC,I encounter probably the same bug in 18.04 and in 18.10.
1698270,2018-04-11 10:14:31 UTC,"I'm really not sure what changed to make 4K video so stuttery now in totem. The CPU is fairly low and goes through the roof only if I uninstall VAAPI. So VAAPI is working, and it works smoothly in mpv too."
1698270,2017-10-13 10:02:46 UTC,Here tis: https://bugzilla.gnome.org/show_bug.cgi?id=788926
1698270,2018-04-11 11:11:02 UTC,I am also having stutter videos in Totem in Bionic. I am using old hardware from 2011. I am ready to give more debugging info when needed.
1698270,2017-10-11 07:17:37 UTC,"The part relevant to clutter-gtk is now released with bug 1698282. Although that doesn't contribute much to the visible stuttering for me, it could in theory for some systems."
1698270,2017-10-13 09:46:56 UTC,"Some simple system monitoring:
  cat /proc/`pidof totem`/io
reveals totem's biggest skip coincides with a disk _write_ of some sort."
1698270,2017-06-16 04:08:17 UTC,The issue seems to persist regardless of which shell / desktop environment I use.
1698270,2017-06-16 04:16:06 UTC,Workaround: Use 'gst-play-1.0' instead of 'totem'. It avoids the rendering glitches and has much lower CPU usage.
1698270,2017-06-16 04:49:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698270,2017-06-16 04:59:57 UTC,This happens in full-screen mode for a window with client-side decorations using OpenGL. Another workaround is to use GNOME MPV without CSD or without OpenGL: https://bugzilla.gnome.org/show_bug.cgi?id=778766#c2
1698270,2017-06-26 12:15:23 UTC,I have this bug also in 3.18.1-1ubuntu4 in Xenial.
1698270,2017-08-18 10:26:46 UTC,First experimental fix: https://git.launchpad.net/~vanvugt/ubuntu/+source/totem/commit/?id=02076c41f892e214d946457f944c6da3011307f1
1698270,2018-03-08 09:39:16 UTC,This issue is still not fixed for Xorg. Not sure what package to target though...
1698270,2017-08-22 02:45:10 UTC,Does the fix apply in Xenial?
1698270,2017-08-22 03:00:42 UTC,I don't see why not. Let's just wait until upstream has accepted the fix and I'll be more confident about applying the same to xenial.
1698270,2017-09-06 09:21:28 UTC,"OK, I have now encountered a few reasons for totem stuttering..."
1698270,2017-09-13 09:44:04 UTC,Smoothness issue 4 above I have tracked down to this clutter-gtk code:
1698270,2017-09-13 09:45:11 UTC,"Sorry, in comment #12 I mean ""clutter"" (in its gdk subdir), not ""clutter-gtk""."
1698270,2017-10-10 10:01:02 UTC,Now looking into issue 3 from comment #11 again.
1698270,2017-08-21 23:43:41 UTC,This bug was fixed in the package totem - 3.25.90.1-0ubuntu2
1698277,2018-02-08 01:06:02 UTC,"Ivan submitted couple patches for UEFI 2.7, ex"
1698277,2018-04-19 05:47:17 UTC,prepare to add some tests for EFI_VARIABLE_AUTHENTICATION_3 in UEFI 2.7
1698282,2018-04-13 11:42:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698282,2018-04-13 06:31:55 UTC,"Upstream bug (possibly related) attached:
https://github.com/intel/intel-vaapi-driver/issues/379"
1698282,2017-10-11 09:54:20 UTC,It appears we've reached a milestone today: totem's CPU usage is no longer significantly higher than gst-play-1.0 --videosink=clutterautovideosink  (or glimagesink)
1698282,2017-10-11 07:33:56 UTC,"This gstreamer fix is also in Ubuntu, and is the intended replacement for my totem patch (no longer required):"
1698282,2017-10-10 17:23:45 UTC,This bug was fixed in the package clutter-gtk - 1.8.4-2
1698282,2017-10-10 13:48:19 UTC,I've uploaded the clutter-gtk fix to Debian and to Ubuntu's queue. I'm unsubscribing ubuntu-sponsors. Feel free to re-subscribe if you have something else that needs sponsoring.
1698282,2017-10-05 08:35:05 UTC,Debdiff for artful to fix the majority of the problem.
1698282,2017-08-24 05:15:51 UTC,Debug log requested by upstream: https://bugzilla.gnome.org/show_bug.cgi?id=786561
1698282,2017-09-06 07:00:19 UTC,"Another prototype fix done, this one more likely to be accepted upstream:
https://git.launchpad.net/~vanvugt/ubuntu/+source/clutter-gtk/commit/?id=eef8eb07e2516d08a984f8128a308943de0d0902"
1698282,2017-08-28 09:04:07 UTC,"Upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=786561 was initially, and still is, for totem too. The main totem patch is there."
1698282,2017-08-22 02:44:23 UTC,Does the fix apply in Xenial?
1698282,2017-08-21 23:43:41 UTC,This bug was fixed in the package totem - 3.25.90.1-0ubuntu2
1698282,2017-08-21 07:52:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698282,2017-08-10 08:07:42 UTC,"Actually about 25-30% of the problem is still totem-specific. The rest is common to other users of clutterautovideosink like:
  gst-play-1.0 --videosink=clutterautovideosink ..."
1698282,2017-07-05 01:59:00 UTC,Confirmed the problem is the gstreamer-clutter plugin (which only totem seems to use by default). You can see the same problem here:
1698282,2017-06-22 04:39:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698282,2017-09-06 08:08:49 UTC,Work in progress still... https://git.launchpad.net/~vanvugt/ubuntu/+source/clutter-gtk?h=fix-1698282
1698284,2017-07-28 20:18:33 UTC,This issue was fixed in the openstack/networking-odl 11.0.0.0b3 development milestone.
1698284,2017-06-22 04:44:26 UTC,"Change abandoned by Isaku Yamahata (<email address hidden>) on branch: master
Review: https://review.openstack.org/474855
Reason: https://review.openstack.org/#/c/476216/"
1698284,2017-06-16 05:38:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474854"
1698284,2017-06-18 18:13:39 UTC,"Change abandoned by Isaku Yamahata (<email address hidden>) on branch: master
Review: https://review.openstack.org/474854
Reason: https://review.openstack.org/#/c/448420/"
1698284,2017-06-16 05:39:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/474855"
1698284,2017-06-22 04:41:09 UTC,"Reviewed:  https://review.openstack.org/476216
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=9e208e90942f9553fde4d1f32b1aa462349dcbda
Submitter: Jenkins
Branch:    master"
1698287,2017-09-22 09:34:25 UTC,"What is the plan for this ""Forwarded: no"" patch in gst-plugins-bad?"
1698287,2017-09-25 20:51:29 UTC,It appears forwarding was blocked by uncertainty around comments made by the upstream reporter saying he would not accept it (although I'm not sure he himself is upstream):
1698287,2017-11-06 05:54:24 UTC,"Andrea,"
1698287,2017-11-06 06:35:50 UTC,"Generate video h264 file (however I get the same behavior for every file I tested).
$ ffmpeg -f lavfi -i color=white;fade=t=out:d=10 -t 10 -c:v libx264 test.mkv"
1698287,2017-08-21 21:51:23 UTC,"Please ignore above comment, my bad.
(- to save some time on fresh install of 17.10 I copied mpv.conf from 16.04
It has an autofit-larger option for the psuedo-gui that isn't compatible with wayland.
Sorry.."
1698287,2017-11-06 10:21:35 UTC,Thanks. I learned something new.
1698287,2017-11-06 10:26:08 UTC,"Andrea, it appears bug 1716800 already covers the problem to some extent. I suggest you subscribe there instead."
1698287,2018-03-01 14:38:06 UTC,"Daniel - with 1.13 -gl has moved from -bad to -base. I think that b769f022619db7b46851986494621492342eaafb is the same as your fix, so I have dropped your patch. Please let me know if that's wrong somehow."
1698287,2018-03-02 02:25:07 UTC,"Thanks Laney. It was in the back of my mind -- I knew upstream had done a fix identical to mine, but they just moved it. I had not stopped to go looking for it..."
1698287,2018-03-02 02:42:41 UTC,Oops. I wasn't testing the new packages yet. I guess we're waiting on:
1698287,2018-03-02 09:32:56 UTC,"On Fri, Mar 02, 2018 at 02:42:41AM -0000, Daniel van Vugt wrote:

> Oops. I wasn't testing the new packages yet. I guess we're waiting on:
>
> gst-plugins-base1.0 (1.13.1-1) experimental; urgency=medium
"
1698287,2018-03-02 09:44:02 UTC,"I might do that but:
 (a) We would have to exclude the old fix (upgrade plugins-bad) at the same time; and
 (b) It is almost EOW here. I can probably bet on everything just working by next week :)"
1698287,2018-03-04 18:02:01 UTC,"This seems fixed as of today's updates but does beg the question of how would most users even know to install the gstreamer1.0-vaapi package?
It doesn't show up here in ubuntu software no matter what I search.."
1698287,2018-03-06 02:02:44 UTC,"Doug,"
1698287,2018-03-06 03:48:41 UTC,"On 03/05/2018 09:02 PM, Daniel van Vugt wrote:

> Doug,
>
> Ideally it will be automatically installed, or at least gets installed
> with ubuntu-restricted-addons. See:
> https://wiki.ubuntu.com/IntelQuickSyncVideo
>


Good to know about the add-ons package, been quite awhile here that I've
used it. Generally on new install I'm just trying to play media &
looking to see if the gst-packagekit > ubuntu-software reacts properly,
ect. (- which it's doing a decent job atm, always some room for
improvement..
I'd think many users also follow that path, i.e add or access media then
follow the pop up if support isn't already available."
1698287,2017-12-11 23:28:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698287,2017-08-21 21:37:08 UTC,"In Regards to mpv:
While vaapi has now been enabled please note that in a 'wayland' session mpv will not work properly with vaapi from the nautilus context menu. Only audio will work, no video."
1698287,2017-08-09 00:52:26 UTC,"Regarding the mpv in artful:
You can currently get some vaapi support in wayland session, you'd need to use
hwdec=vaapi-copy
Not as effective as hwdec=vaapi but I don't think they'll be changing that (commit noted), in near future."
1698287,2017-08-09 09:28:24 UTC,Update:
1698287,2017-06-28 08:20:47 UTC,"A fix for mpv is pending upstream:
https://github.com/mpv-player/mpv/pull/4556"
1698287,2017-06-29 07:40:47 UTC,It seems we're loosely in a deadlock on this one...
1698287,2017-06-30 10:05:04 UTC,"Here's my first attempt at a fix for totem. Although fixing this bug in totem then triggers corruption (bug 1701463) as well as higher CPU, so still needs more verification to see if the higher CPU is just a side-effect of poor plugin choice or related to the corruption..."
1698287,2017-06-30 12:29:49 UTC,"The attachment ""fix-1698287-for-totem-via-gstreamer-vaapi.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1698287,2017-07-03 09:37:08 UTC,"Without sounding too defeated, I think it might be a good idea for us to not use the patch in comment #5 any time soon. The reason is that while the patch is correct, it triggers bigger issues in clutter-gst. And that starts to make me think I'm going too deep down this rabbit hole."
1698287,2017-07-03 10:00:34 UTC,"On second thoughts, if we keep this bug about decoding flaws, and deal with all the display flaws elsewhere then we might be able to close some tasks here..."
1698287,2017-07-06 09:14:34 UTC,More progress: gst-play-1.0 fails on Gnome Shell Wayland only (and not in Weston) because of a mutter problem (or arguably the gstreamer-vaapi plugin assuming that mutter should support it):
1698287,2017-08-09 11:12:20 UTC,This bug was fixed in the package mpv - 0.26.0-3ubuntu1
1698287,2017-07-16 12:03:22 UTC,"vaapi in mpv in a wayland session was broken due to this commit
https://github.com/mpv-player/mpv/commit/bba08e38ff9842c4edf9da6a1d54066a01acd982"
1698287,2017-08-08 10:26:12 UTC,"Here's the preferred clean fix. Doesn't build on my machine, but I suspect it will build in archive :S"
1698287,2017-08-08 23:07:19 UTC,"The simple version of the patch builds fine in a ppa, sponsoring that one"
1698287,2017-08-09 01:06:53 UTC,This bug was fixed in the package gst-plugins-bad1.0 - 1.12.2-1ubuntu2
1698287,2017-08-09 01:41:22 UTC,"Doug,"
1698287,2017-08-09 01:42:33 UTC,I am going to work on additional patches so that by the time 17.10 is released all you will need is:
1698287,2017-08-09 01:46:39 UTC,Actually comment #16 doesn't need a new bug. This bug will do fine for that. See comments #3 - #4.
1698287,2017-08-09 09:14:01 UTC,"Doug, and all:"
1698287,2017-08-08 10:25:35 UTC,"Here is the ""big"" patch I used in testing (includes makefile fix that I suspect archive doesn't need, but my machine does)."
1698287,2017-06-21 20:42:46 UTC,Bugs in gstreamer-vaapi and totem according to upstream.
1698291,2017-06-19 01:53:20 UTC,How clever does the fix need to be?
1698291,2017-06-20 03:12:50 UTC,"That's pretty much what we need to do. I'd need to dive into the code to make sure, but it shouldn't be much more complicated than that."
1698291,2017-06-20 05:33:16 UTC,In our xml-based importers we should make the parser try to recover from errors. This also goes for our song importers.
1698302,2017-06-16 08:07:06 UTC,"I agree on this, having an input file instead of several command parameters will help a lot on usability."
1698302,2017-06-16 09:10:23 UTC,Hi very good idea.
1698302,2017-06-16 09:29:08 UTC,"Note that at least for the environment files list, this is already how we work when deploying from the UI, and I believe shardy is working on making the CLI play more nicely with the list of environments as well (though I don't remember as part of which bug). Currently the CLI mangles all the environments into one big file."
1698304,2017-06-16 07:05:19 UTC,...probably applies to accounts too (as code looks similar)
1698304,2017-06-21 19:49:46 UTC,i can reproduce similarly on my development environment:
1698318,2017-06-28 08:50:50 UTC,This patch may fix it. https://review.openstack.org/#/c/476826/
1698318,2017-06-28 09:17:53 UTC,"@jiaopengju Thank you very much, I will try it."
1698318,2018-03-15 02:48:08 UTC,It work
1698319,2017-07-06 01:07:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698342,2018-03-25 15:09:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698351,2020-11-13 23:19:44 UTC,"Yep, this needs fixing. I upgraded from 16.04 to 20.04 LTS and while there have been some great improvements, what's changed in, and been removed from, Nautilus has been a huge disappointment. Search results are displayed in some crazed, random manner, and cannot be tailored, so when there are a lot of results, it's basically unusable. Because I use search so often, and in folders with lots of files, looks like I Have no choice but to use Nemo until this is resolved."
1698351,2019-12-09 16:43:13 UTC,fix is required
1698351,2019-02-08 21:41:17 UTC,I added an new issue on github https://gitlab.gnome.org/GNOME/nautilus/issues/888 but it seems that there is no intenstion so solve that behavior.
1698351,2019-02-08 20:18:03 UTC,Any update on that? This should not be a bug in LTS!
1698351,2018-06-24 08:51:46 UTC,"Is this getting fixed?
I just upgraded (or downgraded so it seems) to 18.04 from 16.04 and my most used feature is now not working.
Would nemo work better for this?
I specifically want to Sort Search Results in Nautilus.
Cheers."
1698351,2018-08-16 20:03:00 UTC,Example of search query that Nautilus refuses to sort.
1698351,2018-11-14 13:02:47 UTC,Is this going to be fixed in the near future or time to look for another file browser?
1698351,2017-06-22 12:13:44 UTC,After upgrading to nautilus 1:3.20.3-1ubuntu2~ubuntu16.04.1 with ppa:gnome3-team/gnome3-staging found that can't sort search results either in icon or list view.
1698351,2017-06-22 12:10:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698351,2017-08-28 13:15:17 UTC,"Indeed, that seems to be a known issue upstream
https://bugzilla.gnome.org/show_bug.cgi?id=778484"
1698351,2017-08-28 23:51:15 UTC,Thanks for the update. I've added my comments upstream as well.
1698358,2017-06-16 12:05:47 UTC,This came up after boot time. I realized that the root filesystem was mounted read only for some reason. After reboot with root filesystem in read-write mode I was lead here by clicking on the report problems button.
1698368,2017-08-21 09:50:23 UTC,"Thank for the answer,"
1698368,2017-12-08 20:27:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698368,2017-06-16 12:55:39 UTC,Text correction
1698368,2017-06-18 21:59:15 UTC,"NetCDF is no longer built with autotools, hence the static library is no longer built by default."
1698375,2019-06-10 00:12:38 UTC,Fixed in https://github.com/resurrecting-open-source-projects/scrot/commit/755f29de94c09721f953635151de6bd5fa53c06b
1698375,2019-07-12 00:33:36 UTC,This bug was fixed in the package scrot - 1.1-1
1698388,2020-09-15 16:16:51 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1698388,2020-09-10 17:06:39 UTC,I at least verified the update doesn't appear to cause any obvious regression:
1698388,2020-09-10 07:23:06 UTC,"I’m sorry, we stopped using systemd-journal-remote a few months after I opened this issue, I am no longer able to reproduce."
1698388,2020-09-15 16:16:33 UTC,This bug was fixed in the package systemd - 229-4ubuntu21.29
1698388,2020-09-04 21:09:40 UTC,"All autopkgtests for the newly accepted systemd (229-4ubuntu21.29) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:"
1698388,2020-09-04 08:31:51 UTC,"Hello Ruud, or anyone else affected,"
1698388,2017-06-16 14:13:47 UTC,"Upstream bug report, which indeed shows the same assertion failure, and which is fixed by the commit mentioned above: https://github.com/systemd/systemd/pull/3086."
1698388,2020-09-04 08:31:02 UTC,"It's a bit unfortunate that we don't have a test case for this assertion failure. That being said, the fix for it seems rather safe and sane. Still, I would like us to try and contact with the original reporter and ask him to test it, if possible."
1698388,2020-05-18 14:11:16 UTC,Fixed in Bionic and later.
1698388,2020-09-09 18:08:56 UTC,@ruuda-channable are you able to test this?
1698417,2017-07-01 22:15:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698424,2017-06-16 17:43:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/475043"
1698424,2017-07-06 16:34:47 UTC,"Reviewed:  https://review.openstack.org/475043
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=0f596ff20327451e414fb932be458e61d38bf43f
Submitter: Jenkins
Branch:    master"
1698430,2018-03-14 14:48:05 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1698437,2017-06-26 06:44:58 UTC,With current version of libgdata Google Contacts is unusable. See this bug: https://bugzilla.gnome.org/show_bug.cgi?id=780067
1698437,2017-06-30 04:33:54 UTC,This bug was fixed in the package libgdata - 0.17.8-0ubuntu1
1698438,2017-06-19 01:36:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698438,2017-06-19 19:42:20 UTC,"Yes, after last update Firefox to version 54.0."
1698438,2018-12-10 22:14:44 UTC,Still a problem in Firefox 63 with either:
1698438,2018-12-11 15:29:53 UTC,"Yes, still a problem in Firefox 63.0.3 with either :"
1698438,2018-12-11 15:40:23 UTC,but this site does not cause a problem.
1698438,2018-12-12 15:37:26 UTC,Possibly related: https://www.fxsitecompat.com/en-CA/docs/2016/flash-is-forced-windowless-mode-on-firefox-for-64-bit-windows-affecting-stage-3d/
1698438,2017-06-19 01:38:32 UTC,I can confirm this is happening after the latest Firefox update.
1698450,2017-07-22 23:36:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698454,2017-08-16 04:52:57 UTC,In light of my previous findings I did a dual boot install with 15.10 and 16.04.  I put both installs on 4.3.6 mainline kernel and found that 15 was fine and 16 was not.  I started looking at installed packages and tried to isolate some packages.  After uninstalling several and rebooting I found that my performance went back up to normal.  Long story short I found that uninstalling libnuma1 (which also uninstalls irqbalance) solved the problem after a reboot.  FYI simply killing the irqbalance task did not solve the problem.  I haven't taken time to troubleshoot further but it's something with numa/interrupt processing that is taking too long or something.  Reinstalling irqbalance/libnuma1 causes the problem again.  This is a single Xeon CPU on a dual CPU board.
1698454,2017-07-22 02:01:04 UTC,"Testing was with mainline builds in both cases, so it should rule out the kernel."
1698454,2017-07-22 01:57:51 UTC,My initial conclusion on something changing in the Kernel was incorrect.  I've since tested 17.04 all the way back to 4.2.8 and it still fails.  I've also tested 15.10 up to 4.3.6 and it works correctly.  So something in Ubuntu's implementation changed between 15.10 and 16.04 that is causing this bug.
1698454,2017-07-01 02:31:23 UTC,"Tested with mainline v4.12-rc7, bug still exists.  Added tag kernel-bug-exists-upstream and changed to Confirmed"
1698454,2017-06-20 15:28:41 UTC,"I will do that, won't be until end of next week though when I have access to it."
1698454,2017-07-11 15:03:41 UTC,Is this something I should try to report elsewhere as a kernel bug?  I haven't tried a dist other than Ubuntu yet.
1698454,2017-06-19 15:01:23 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1698454,2017-06-17 00:27:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1698454,2017-06-19 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1698457,2018-12-13 16:32:40 UTC,I just experienced this issue as well (in newest nightly). but for me it was simply a matter of setting the minimum width to something lower than 0.25mm. Some visualization of the joined soldermask in PCBNew and perhaps also the 3D viewer would be really handy as well. Should this be a seperate issue?
1698457,2018-12-14 08:30:43 UTC,Please add a test file such that it is easy to test.
1698457,2018-12-14 11:07:47 UTC,"Note that while it would be nice to fix the rounding error, the ""real"" fix to this would be DFM checks, which we're tracking here: https://bugs.launchpad.net/kicad/+bug/1783093."
1698457,2019-01-14 11:17:46 UTC,"@Jeff
I dont know if this should be a seperate bug, but could the minimum soldermask width be set to something lower by default? if a functioning board is made in V4 (which doesnt have the minimum width) and opened by V5 there will be 0.25mm minimum width which is not shown anywhere but the gerbers."
1698457,2019-01-14 14:20:25 UTC,@Frank-  We already changed that in v5.0.1
1698457,2019-01-17 01:55:23 UTC,@Seth the default solder mask min width being 0.25 when importing V4? This seems to still be an issue
1698457,2019-01-17 03:18:06 UTC,Only applies to new projects. We don't change people's existing board settings.
1698457,2019-01-23 00:12:03 UTC,"@Seth V4 projects doesn't have a solder mask min_width setting. So if we don't want to change peoples settings, we should set it to as close to zero as possible."
1698457,2019-01-23 00:49:31 UTC,Thanks Frank.  I see that now.  I'll check a fix later tonight.  That was an oversight in lp:1786765
1698457,2019-01-23 03:55:00 UTC,"Fixed in revision 6421b15b83be7fb086528666e33d3662acff1c93
https://git.launchpad.net/kicad/patch/?id=6421b15b83be7fb086528666e33d3662acff1c93"
1698457,2019-01-23 10:56:54 UTC,Thanks Seth
1698470,2017-10-30 19:26:53 UTC,This bug was fixed in the package linux - 4.10.0-38.42
1698470,2017-08-24 08:00:27 UTC,Ping
1698470,2017-10-18 08:59:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1698470,2017-06-19 20:20:12 UTC,Test okay on Zesty.
1698470,2017-06-19 20:37:17 UTC,4.8.0-56-generic tested okay
1698470,2017-07-26 15:50:24 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1698470,2017-06-19 19:23:24 UTC,I built Yakkety and Zesty test kernels with the four requested patches.  The test kernels can be downloaded from:
1698470,2017-06-16 22:30:15 UTC,This change was made by a bot.
1698478,2017-06-17 03:21:22 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1698478,2017-06-17 03:23:06 UTC,"Hi Troy, note the df output indicates a full /dev filesystem:"
1698478,2017-07-19 11:00:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698480,2017-07-31 23:05:52 UTC,Fixed in https://review.openstack.org/#/c/479092/ .
1698486,2017-10-05 10:10:23 UTC,"i  get this message anytime I try to install anything from the software manager, can anyone tell me how to fix this problem?"
1698499,2017-06-17 03:28:23 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1698499,2017-12-11 07:40:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698499,2017-06-17 03:29:35 UTC,"Hi Woodzy, note that android-androresolvd only makes sense in chroot-style environments -- you don't want it installed otherwise."
1698501,2017-06-17 06:03:41 UTC,"In Bug 1697800 Seth Arnold points out that the upgrade tools are not in a position to check architecture features before installation. While I don't know the best (least worst?) solution, here are some ideas."
1698501,2017-09-22 13:23:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698502,2017-06-17 04:05:53 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1698502,2017-06-18 20:09:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698502,2017-06-18 20:14:40 UTC,Thanks for reporting.
1698502,2019-10-22 16:48:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698520,2020-04-29 00:04:00 UTC,Closing this. ufraw has been removed from recent Ubuntu releases.
1698529,2017-07-26 23:09:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698531,2017-06-17 19:38:02 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1698536,2018-10-05 02:57:30 UTC,"David Timothy Strauss, (who seems to be a Breezy fan), thinks that sha512 should be used instead of sha256: https://medium.com/@davidtstrauss/stop-using-sha-256-6adbb55c608"
1698539,2018-10-02 13:23:27 UTC,Indeed Andreas. I've tested with the testcase provided in comment #4 (https://bugs.launchpad.net/gcc-arm-embedded/+bug/1698539/comments/4) and it works. It has been changed by revision 262437 on 5th of July. I'm marking the bug as Fix committed as a result (yes it will not be fixed in the next GNU Arm Embedded Toolchain release but the fix is committed and will be released as soon as we release a toolchain based of GCC 9).
1698539,2018-08-28 12:00:53 UTC,"upcoming gcc releases - I suspect gcc 9, will have that setting inverted and machine configs need to explicitly activate that behavior with SYSTEM_IMPLICIT_EXTERN_C."
1698539,2018-08-28 11:46:36 UTC,"I filed this issue also at the ubuntu package - which is probably better maintained:
https://bugs.launchpad.net/ubuntu/+source/gcc-arm-none-eabi/+bug/1789395"
1698539,2018-08-28 11:09:19 UTC,"I think ARM is just doing what every company is doing: react to the loudest complains first. Maybe we should ask other colleges, who are pestered by this bug to fill duplicates or to at least subscribe to this bug, to raise the ""bug heat"" :-)"
1698539,2018-08-28 10:49:38 UTC,"I think the best way to go forward is to just ignore arm and start our own ppa.
This is known for years and no reaction see: https://bugs.launchpad.net/gcc-arm-embedded/+bug/1585322"
1698539,2018-08-22 08:21:45 UTC,One possible solution that worked for me is to manually recompile the binaries from the sources with NO_IMPLICIT_EXTERN_C defined.
1698539,2018-08-02 12:29:44 UTC,@belagod-tejas: Any plans to change this behavior in the near future in the official binary packages?
1698539,2018-07-20 02:37:58 UTC,Any news on this... not sure how something like this could be open for a whole year and still not be fixed.
1698539,2018-08-06 06:32:01 UTC,This makes it difficult to use this toolchain in combination with Bazel. It's uses -isystem to pass include directories to the compiler and there seems no easy way to change this.
1698539,2018-05-03 17:54:38 UTC,"@torstenrobitzki I don't think that is a workaround we can use. We have code that extensively uses C++ headers, and we are using CMake plus the [Hunter package management system](https://github.com/ruslo/hunter) to manage our dependencies on external C++ packages such as Boost."
1698539,2018-05-03 07:33:50 UTC,"As a workaround, you can include a header and include the needed C++ headers from within an `extern ""C++""` block. For example:"
1698539,2018-05-03 00:28:29 UTC,I'm using the g++ 7.2 arm-none-eabi compiler shipped with the Xilinx SDK 2018.1 and am impacted by this issue.
1698539,2018-01-09 09:54:51 UTC,The reported behavior is still the same with 7-2017-q4-major. Are there any plans to build the binaries with NO_IMPLICIT_EXTERN_C ?
1698539,2017-12-12 15:07:30 UTC,This is a real pain since it makes impossible to include C++ library header files with -isystem. They must be included as standard includes (-I) which makes compilation very noisy.
1698539,2017-10-11 12:27:56 UTC,Have a file t.cpp:
1698539,2017-10-11 11:54:07 UTC,"Hi,"
1698539,2017-10-11 10:29:35 UTC,"One symptom for example is, that the compiler generates errors, when it hits a template declaration: ""error: template with C linkage"""
1698539,2017-06-20 08:41:14 UTC,"Hi Pedro,"
1698539,2018-07-13 14:14:59 UTC,And the problem still persists with 7.3.1
1698548,2017-06-19 14:27:23 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1698548,2017-07-04 03:45:26 UTC,Dupe of LP: #1693440?
1698548,2017-07-03 23:14:37 UTC,"kernel-bug-exists-upstream
Tried latest 4.12 kernel still not working."
1698548,2017-06-23 13:44:49 UTC,"@jsalisbury I did a fresh install of Lubuntu 17.04 and updated the kernel to 4.12.0-041200rc3-generic, none of the kernel worked. I will test the rc5 and rc6 kernel and report."
1698548,2017-06-18 07:51:38 UTC,apport information
1698548,2017-06-18 07:51:40 UTC,apport information
1698548,2017-06-18 07:50:38 UTC,apport information
1698548,2017-06-17 15:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1698548,2017-06-18 07:50:36 UTC,apport information
1698548,2017-06-18 07:50:34 UTC,apport information
1698548,2017-06-18 07:49:54 UTC,apport information
1698548,2017-06-18 07:49:52 UTC,apport information
1698548,2017-06-18 07:49:49 UTC,apport information
1698548,2017-06-18 07:51:36 UTC,apport information
1698549,2017-06-17 14:56:53 UTC,"StacktraceTop:
 ?? () from /tmp/apport_sandbox_hOkSjB/usr/lib/x86_64-linux-gnu/libcups.so.2
 renew_subscription (data=0x563f118c99f0, data@entry=<error reading variable: value has been optimized out>) at gsd-print-notifications-manager.c:1113
 g_timeout_dispatch (source=0x563f118e5280, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4715
 g_main_dispatch (context=0x563f11886a90) at ../../../../glib/gmain.c:3234
 g_main_context_dispatch (context=context@entry=0x563f11886a90) at ../../../../glib/gmain.c:3899"
1698551,2017-11-01 19:55:08 UTC,"Sorry, but IMHO also #1719102 is something completely different; I'd open a new bug."
1698551,2017-11-01 14:30:35 UTC,"Thanks for replying, Ian and Andreas."
1698551,2017-11-01 07:04:09 UTC,@Clenimar -- the real error will be well before this.  Please use --logfile (on master) or just redirect to a logfile and send us the full output
1698551,2017-10-31 03:33:06 UTC,"I could reproduce it in virtual machines running Ubuntu 16.04, Fedora 25 and Fedora 26. Any hint?"
1698551,2017-11-01 08:27:06 UTC,@Clenimar:
1698551,2017-07-11 14:48:17 UTC,"Apart from normally using centos7, the bug still applies to CentOS 6. In Sahara we still support CentOS 6 images with Hadoop stuff; if this is not addressed we should end up deprecating them, I guess (at least removing from the CI)."
1698551,2017-06-19 00:06:46 UTC,"And that worked, with the centos7 that is."
1698551,2017-06-18 23:27:37 UTC,"Oh, also, you probably want ""centos7"" ... i admit it's very confusing"
1698551,2017-06-18 23:26:52 UTC,"Actually this is a red herring, the problem is before this at"
1698551,2017-06-17 14:56:34 UTC,Thanks for the report.
1698551,2017-10-31 03:32:05 UTC,Just hit this when trying to build a fedora-atomic image.
1698567,2017-06-17 18:29:24 UTC,https://github.com/lxde/libfm/pull/30
1698571,2020-12-14 05:30:02 UTC,"I have an idea how to solve the problem simply and with much greater effect: allow users to use theys favorite EXTERNAL text editor to edit formula, i.e. parameter ""External math text editor path"" in settings needed. It it empty - LibreOffice Math runs, else the LibreOffice (or LibreOffice Math without GUI) run this actions:"
1698571,2020-12-14 14:14:59 UTC,"(In reply to Sergey from comment #13)

> I have an idea how to solve the problem simply and with much greater effect:
> allow users to use theys favorite EXTERNAL text editor to edit formula, i.e.
> parameter ""External math text editor path"" in settings needed. It it empty -
> LibreOffice Math runs, else the LibreOffice (or LibreOffice Math without
> GUI) run this actions:
>
> - create temp file XXXXX.eqn on trying to fornmula edit/create
> - run external text editor with this file as parameter
> - read file after editor closing and update formula object as it LibreOffice
> Math does
>
> It's AUTOMATICALY enables features on user side:
>
> - pair brackets highlighting
> - functions highlighting
> - more simple editing (change variable name with multicaret editing or vim
> commands, e.t.c.)
> - snippets (not only for math constructions, may be used to natural greek
> symbols writing - [a]+[Tab] -> α instead of %alpha - more simple reading)
> - macroses to text editing in some special cases
>
> It seems to be a great effect for easy implementation - don't you think so?
"
1698571,2020-12-15 16:24:38 UTC,"Thanks, V Stuart Foote!"
1698571,2021-01-29 17:47:41 UTC,"Created attachment 169284
Math Highlighting Comments"
1698571,2021-02-01 12:50:36 UTC,"Created attachment 169343
Highlighting Numeric Values"
1698571,2021-01-29 20:12:15 UTC,(In reply to Rafael Lima from comment #16)
1698571,2021-02-01 18:36:06 UTC,"(In reply to Rafael Lima from comment #19)

> Created attachment 169343 [details]
> Highlighting Numeric Values
"
1698571,2020-07-19 11:56:15 UTC,*** Bug 48671 has been marked as a duplicate of this bug. ***
1698571,2021-01-29 19:46:42 UTC,"Created attachment 169287
Math Highlighting Comments"
1698571,2019-11-29 13:28:33 UTC,Changing priority back to 'medium' since the number of duplicates is lower than 5
1698571,2013-11-07 10:38:00 UTC,"I'll start to work in this bug. Do you have some code pointers?
I was taking a look on EditEngine and EditView sources. I think we have to implement this on these classes, right?"
1698571,2018-01-02 21:56:42 UTC,On Ubuntu i
1698571,2018-07-13 19:36:01 UTC,Would be cool to have highlight of operands/functions in Formula editor
1698571,2012-04-14 13:00:05 UTC,Thank you. BTW; changed version.. and Status to NEW
1698571,2013-11-02 22:00:25 UTC,"I'm taking a look the bugs formula editor, to classify then and after try to solve them. I downloaded the file attachment and there are some germany comments on it. Is something relevant?"
1698571,2013-11-02 22:02:26 UTC,"(In reply to comment #3)

> I'm taking a look the bugs formula editor, to classify then and after try to
> solve them. I downloaded the file attachment and there are some germany
> comments on it. Is something relevant?
"
1698571,2012-04-14 12:51:14 UTC,"Complety right.
Even Gedit use sintax hilight."
1698571,2013-11-07 12:46:16 UTC,"No idea (regarding codepointer) Anyone?
Feel free to ask @ libreoffice-dev IRC channel @ freenode"
1698571,2017-06-17 19:05:17 UTC,Syntax highlighting and bracket matching will be very useful.
1698571,2017-06-23 12:04:47 UTC,"Removing the libreoffice source package task, as this is an upstream feature request, which when implemented will make its way to the ubuntu packages without any additional work needed on the packaging side."
1698571,2017-09-01 17:01:04 UTC,Bug exists in
1698571,2011-11-19 05:22:32 UTC,"Created attachment 53686
How syntax highlighting should work"
1698572,2021-02-01 18:36:06 UTC,"(In reply to Rafael Lima from comment #19)

> Created attachment 169343 [details]
> Highlighting Numeric Values
"
1698572,2021-02-01 12:50:36 UTC,"Created attachment 169343
Highlighting Numeric Values"
1698572,2021-01-29 20:12:15 UTC,(In reply to Rafael Lima from comment #16)
1698572,2021-01-29 19:46:42 UTC,"Created attachment 169287
Math Highlighting Comments"
1698572,2021-01-29 17:47:41 UTC,"Created attachment 169284
Math Highlighting Comments"
1698572,2020-12-15 16:24:38 UTC,"Thanks, V Stuart Foote!"
1698572,2020-12-14 14:14:59 UTC,"(In reply to Sergey from comment #13)

> I have an idea how to solve the problem simply and with much greater effect:
> allow users to use theys favorite EXTERNAL text editor to edit formula, i.e.
> parameter ""External math text editor path"" in settings needed. It it empty -
> LibreOffice Math runs, else the LibreOffice (or LibreOffice Math without
> GUI) run this actions:
>
> - create temp file XXXXX.eqn on trying to fornmula edit/create
> - run external text editor with this file as parameter
> - read file after editor closing and update formula object as it LibreOffice
> Math does
>
> It's AUTOMATICALY enables features on user side:
>
> - pair brackets highlighting
> - functions highlighting
> - more simple editing (change variable name with multicaret editing or vim
> commands, e.t.c.)
> - snippets (not only for math constructions, may be used to natural greek
> symbols writing - [a]+[Tab] -> α instead of %alpha - more simple reading)
> - macroses to text editing in some special cases
>
> It seems to be a great effect for easy implementation - don't you think so?
"
1698572,2020-12-14 05:30:02 UTC,"I have an idea how to solve the problem simply and with much greater effect: allow users to use theys favorite EXTERNAL text editor to edit formula, i.e. parameter ""External math text editor path"" in settings needed. It it empty - LibreOffice Math runs, else the LibreOffice (or LibreOffice Math without GUI) run this actions:"
1698572,2019-11-29 13:28:33 UTC,Changing priority back to 'medium' since the number of duplicates is lower than 5
1698572,2020-07-19 11:56:15 UTC,*** Bug 48671 has been marked as a duplicate of this bug. ***
1698572,2018-02-23 17:08:34 UTC,"Closing the bug against the source package, as it's not a packaging bug, but a missing feature upstream."
1698572,2018-01-02 21:56:42 UTC,On Ubuntu i
1698572,2017-09-01 17:01:04 UTC,Bug exists in
1698572,2017-06-17 19:05:17 UTC,Syntax highlighting and bracket matching will be very useful.
1698572,2013-11-07 12:46:16 UTC,"No idea (regarding codepointer) Anyone?
Feel free to ask @ libreoffice-dev IRC channel @ freenode"
1698572,2013-11-07 10:38:00 UTC,"I'll start to work in this bug. Do you have some code pointers?
I was taking a look on EditEngine and EditView sources. I think we have to implement this on these classes, right?"
1698572,2013-11-02 22:02:26 UTC,"(In reply to comment #3)

> I'm taking a look the bugs formula editor, to classify then and after try to
> solve them. I downloaded the file attachment and there are some germany
> comments on it. Is something relevant?
"
1698572,2013-11-02 22:00:25 UTC,"I'm taking a look the bugs formula editor, to classify then and after try to solve them. I downloaded the file attachment and there are some germany comments on it. Is something relevant?"
1698572,2012-04-14 13:00:05 UTC,Thank you. BTW; changed version.. and Status to NEW
1698572,2012-04-14 12:51:14 UTC,"Complety right.
Even Gedit use sintax hilight."
1698572,2011-11-19 05:22:32 UTC,"Created attachment 53686
How syntax highlighting should work"
1698572,2018-07-13 19:36:01 UTC,Would be cool to have highlight of operands/functions in Formula editor
1698574,2021-01-09 04:17:47 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1698574,2020-11-09 17:54:56 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1698580,2018-02-15 17:49:19 UTC,"Hi Daniel, thank you for taking time to report this and for providing a solution."
1698580,2017-06-17 21:02:24 UTC,I fixed it by:
1698603,2017-08-17 13:11:45 UTC,"Hi,"
1698604,2020-07-09 22:44:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698604,2020-07-09 22:46:01 UTC,Just had this when updating Ubuntu via the terminal - first three characters of sudo password displayed on terminal (where the green blob is on the photo).
1698616,2017-06-18 06:31:37 UTC,https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698508
1698616,2017-06-18 07:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1698616,2017-06-19 14:26:02 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1698616,2017-06-30 03:22:18 UTC,"~ > uname -a
Linux XPS 4.12.0-041200rc5-lowlatency #201706112031 SMP PREEMPT Mon Jun 12 00:38:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1698616,2017-07-15 21:23:52 UTC,Still present in -26
1698616,2017-07-17 07:27:15 UTC,I guess it's pretty similar to LP: #1697556. Try blacklisting nouveau.
1698616,2017-07-20 22:41:48 UTC,"> I guess it's pretty similar to LP: #1697556. Try blacklisting nouveau.
"
1698616,2017-07-21 04:30:26 UTC,Can you guys try what Joseph asked in comment #3?
1698617,2017-06-18 06:44:13 UTC,I think the best solution is to make loopingcall greenthread-agnostic. But this has to go through the oslo folk.
1698618,2017-08-15 05:54:49 UTC,Thank you for the response.
1698618,2017-06-18 07:30:04 UTC,This change was made by a bot.
1698618,2017-06-19 14:25:17 UTC,You may need to run the following from a terminal:
1698630,2017-06-28 21:35:24 UTC,"Yeahr, it should first only list the devices and then, the choosen one (or directly at the start the first one) should be scanned."
1698630,2017-06-23 12:57:15 UTC,"And this scanning happens again on every device, even if i modify only one partition on one device?"
1698630,2017-06-22 21:01:25 UTC,"@Phillip, scanning is performed to determine which devices are present, what partition tables these contain, what file systems are in the partitions, and other details such as volume labels, free space, UUID, etc."
1698630,2017-06-28 22:12:27 UTC,Scanning for all devices on startup is a design decision dating back to the initial development of GParted.
1698630,2017-06-20 15:28:17 UTC,You might create an icon on the desktop or in the menu system with the command line parameters that you desire to only access a USB drive when it is plugged in.
1698630,2017-06-22 18:39:30 UTC,"Hi Curtis... what exactly is it scanning for again, and why does it need to do that on any drive other than the one that is currently selected?"
1698630,2017-06-18 16:03:36 UTC,GParted already supports scanning only the devices you pass to it.  This is most easily done from a terminal window.
1698630,2017-06-28 20:22:32 UTC,Which devices are present should be as simple as looking what files are in /dev... reading the partition tables and identifying filesystems though... why does gparted care unless and until you have chosen to show that drive?
1698630,2017-06-19 15:05:12 UTC,"Good point about the lack of a ""--help"" argument from the command line."
1698630,2017-06-18 22:59:31 UTC,"Then it's sad, that there is no GUI-Option.
Or, when i start it from a terminal window, there is no --help argument, or no help screen, if i use an command which doesn't exist."
1698630,2017-06-19 21:04:53 UTC,"Is it possible to add a gui, which let me choose, which device i want to scan (maybe all), if there are more than one storages to the pc are attached, if i use no argument in the terminal?"
1698635,2017-06-18 12:32:32 UTC,"The attachment ""Fix error EAP-TLS: Cannot load PKCS11 key"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1698645,2017-10-06 16:09:25 UTC,"Thanks for reporting it. It's a very simple fix, if anybody has time to do it. The file to change is:"
1698655,2017-11-03 17:49:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698655,2018-09-17 17:05:48 UTC,"Dear Dan Smith,"
1698655,2020-08-12 05:56:33 UTC,"Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!"
1698656,2021-02-22 14:19:22 UTC,For me it worked to use the snap version.
1698656,2020-12-02 15:23:47 UTC,Still present in 20.10.
1698656,2018-07-17 11:59:53 UTC,Still present in 18.04.
1698656,2018-01-06 20:28:02 UTC,"As a workaround, what worked for me was:"
1698656,2017-11-10 17:01:53 UTC,Still present in 17.10.
1698656,2017-11-10 17:01:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698656,2018-02-19 09:50:39 UTC,The workaround works for me.
1698656,2018-02-18 14:05:55 UTC,"The steps described in #4 did not work for me. I managed to fix it by running qt5ct and selecting ""Oxygen"" as icon theme there.
Rem: I also have QT_QPA_PLATFORMTHEME=""qt5ct"" in my env."
1698665,2017-06-19 15:37:19 UTC,"The output from the command ""# pacmd list-sinks"" had  XGD-RUNTIME_DIR in the result, but that was because I made the command as superuser. If performed as regular user with sudo the result is as follws:"
1698665,2017-06-22 20:16:25 UTC,"I booted my computer with my USB flash memory with linuxmint-18.1-cinnamon-64bit.iso on it, so I ran a live USB session. I opened firefox and played a song on youtube. The sound worked perfectly! So I can rule out any hardware error."
1698665,2017-06-23 09:17:17 UTC,Sound is back!
1698666,2017-06-18 16:51:47 UTC,"duplicate of Bug 1691406?
https://bugs.launchpad.net/inkscape/+bug/1691406"
1698666,2020-03-25 08:44:07 UTC,Closing: Probably a duplicate.
1698671,2019-06-06 17:24:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that there was an error on your system when trying to update a package on your system due to a lack of free space on your system.  Please resolve this situation manually and try the update again.
1698673,2017-06-26 16:14:59 UTC,"Denis,  Could you give a rough translation of ""пакет абсолютно неработоспособен; перед настройкой его следует переустановить""?  Because I have no idea what it says there."
1698674,2018-02-10 16:17:23 UTC,"Pully request here
https://github.com/ricotz/plank/pull/4"
1698698,2020-09-22 07:06:33 UTC,Closing because INVALID: Support request.
1698698,2017-06-19 11:33:28 UTC,Here are the options and their respective tooltips displayed on hover:
1698700,2017-12-08 08:15:20 UTC,hi daniel
1698700,2017-12-15 07:55:36 UTC,"Hi Fred,"
1698700,2017-12-15 07:38:21 UTC,hi daniel:
1698700,2017-12-11 07:20:33 UTC,"Hi Fred,"
1698700,2017-12-11 07:00:28 UTC,"this  patch will solve commit #10 bug, please merge this patch."
1698700,2017-12-06 07:37:30 UTC,       Starting Hostname Service...
1698700,2017-12-15 05:36:35 UTC,There is another bug causing an artful regression - opening a new LP for that: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738334
1698700,2017-12-03 22:35:16 UTC,"The patch does seem to be in Artful, following up with the user."
1698700,2017-11-28 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1698700,2017-11-28 16:36:48 UTC,"Reopening for bionic/artful, as it is reported to have regressed post-zesty."
1698700,2017-07-17 11:57:59 UTC,This bug was fixed in the package linux - 4.10.0-28.32
1698700,2017-07-12 12:13:16 UTC,This bug was fixed in the package linux - 4.11.0-10.15
1698700,2017-07-05 01:33:41 UTC,Verified the proposed kernel on the D05.
1698700,2017-06-19 08:20:09 UTC,It looks like this will be rendered unnecessary by upcoming changes to the DRM core: http://www.spinics.net/lists/dri-devel/msg143831.html
1698700,2017-12-06 07:37:02 UTC,I use this following 17.10 ISO to test this xwindow for D05 board.
1698707,2017-09-13 22:59:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698717,2017-06-19 03:14:56 UTC,"One more thing,"
1698743,2019-04-18 23:25:13 UTC,"(In reply to Theo Linkspfeifer from comment #4)

> I think it makes sense to fall back to the directory which contains the
> currently active background image. Any reason why the user would change to a
> different directory, but not select a new image?
"
1698743,2019-04-18 20:58:42 UTC,"I think it makes sense to fall back to the directory which contains the currently active background image. Any reason why the user would change to a different directory, but not select a new image?"
1698743,2018-10-21 09:48:56 UTC,Added the upstream report.
1698743,2018-10-21 01:54:48 UTC,Still seeing this on Fedora with xfdesktop 4.12.4.
1698743,2017-02-03 19:59:59 UTC,Moving to Xfdesktop.
1698743,2016-06-14 03:45:56 UTC,"Hmmmm. After clicking on one of the picture from the directory, the path took and did not revert to the default."
1698743,2016-06-06 19:07:04 UTC,"$ rpm -qa xfce4\*
xfce4-datetime-plugin-0.6.2-6.el7.x86_64
xfce4-panel-4.12.0-4.el7.x86_64
xfce4-settings-4.12.0-7.el7.x86_64
xfce4-panel-devel-4.12.0-4.el7.x86_64
xfce4-terminal-0.6.3-4.el7.x86_64
xfce4-notifyd-0.2.4-8.el7.x86_64
xfce4-pulseaudio-plugin-0.2.4-4.el7.x86_64
xfce4-session-4.12.1-8.el7.x86_64
xfce4-about-4.12.1-3.el7.x86_64
xfce4-notes-plugin-1.8.1-2.el7.x86_64
xfce4-session-engines-4.12.1-8.el7.x86_64
xfce4-power-manager-1.6.0-2.el7.x86_64
xfce4-appfinder-4.12.0-4.el7.x86_64"
1698743,2018-08-20 14:16:10 UTC,"This was mentioned on the Xfce forums too, but no enhancement request was forwarded to the Xfce bug tracker."
1698758,2017-08-10 15:55:32 UTC,This bug was fixed in the package libapache2-mod-auth-pgsql - 2.0.3-6.1ubuntu0.17.04.1
1698758,2017-08-10 15:52:22 UTC,This bug was fixed in the package libapache2-mod-auth-pgsql - 2.0.3-6.1ubuntu0.16.04.1
1698758,2017-08-10 15:50:28 UTC,"The verification of the Stable Release Update for libapache2-mod-auth-pgsql has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1698758,2017-08-10 15:50:16 UTC,This bug was fixed in the package libapache2-mod-auth-pgsql - 2.0.3-6ubuntu0.1
1698758,2017-08-03 14:40:45 UTC,Trusty verification
1698758,2017-08-03 14:27:28 UTC,Xenial verification:
1698758,2017-08-02 11:55:10 UTC,"Hello John, or anyone else affected,"
1698758,2017-08-02 11:53:23 UTC,"Hello John, or anyone else affected,"
1698758,2017-08-03 14:21:41 UTC,Zesty verification
1698758,2017-07-19 19:07:40 UTC,test users
1698758,2017-06-20 18:44:50 UTC,Confirmed in my xenial testing:
1698758,2017-06-21 20:45:23 UTC,"It's segfaulting because of this odd usage of crypt(3):
                        sent_pw = (char *) crypt(sent_pw, real_pw);"
1698758,2017-06-22 14:16:00 UTC,"Ok, got a better hang of it. crypt(3) can indeed be used like that, but the code needs to check for it returning NULL in the case of errors:
diff --git a/mod_auth_pgsql.c b/mod_auth_pgsql.c
index 0a16e05..4f80917 100644
--- a/mod_auth_pgsql.c
+++ b/mod_auth_pgsql.c
@@ -868,6 +868,12 @@ static authn_status check_password(request_rec *r, const char *user,
                        break;
                case AUTH_PG_HASH_TYPE_CRYPT:
                        sent_pw = (char *) crypt(sent_pw, real_pw);
+                       if (!sent_pw) {
+                               apr_snprintf(pg_errstr, MAX_STRING_LEN,
+                                                ""PG user %s: password mismatch"", user);
+                               ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r, ""[mod_auth_pgsql.c] - ERROR - %s"", pg_errstr);
+                               return AUTH_DENIED;
+                       }
                        break;
                case AUTH_PG_HASH_TYPE_BASE64:
                        sent_pw = auth_pg_base64(sent_pw);"
1698758,2017-06-22 14:32:21 UTC,"One can use mkpasswd(1) from the ""whois"" package (!) to generate these hashes supported by crypt(3):
$ mkpasswd -5 secret
$1$0UiJQbpc$QoJQqJIT1DCHtQYGwJHZh0"
1698758,2017-08-02 11:51:55 UTC,"Hello John, or anyone else affected,"
1698758,2017-07-13 14:50:46 UTC,This bug was fixed in the package libapache2-mod-auth-pgsql - 2.0.3-6.1ubuntu1
1698758,2017-07-13 12:59:40 UTC,Here is a debdiff for artful
1698758,2017-07-18 21:15:21 UTC,"Sorry, I need to rework that debdiff to get the same patch that is already applied in the other ubuntu releases. I had updated the dep3 header."
1698758,2017-07-18 21:05:08 UTC,debdiff for trusty
1698761,2018-11-14 12:17:09 UTC,"Reviewed:  https://review.openstack.org/617369
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=cd95839e4ec752609d28733b06f768cb81a1b3aa
Submitter: Zuul
Branch:    master"
1698767,2017-08-10 07:37:08 UTC,"FWIW, even though I recognize all the reasons bug #1690466 was marked as won't fix and offer to use heuristics to get around that, perhaps we should mark this one as won't fix too?"
1698767,2019-09-19 14:48:30 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1698768,2017-06-19 09:23:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698773,2017-06-28 10:44:07 UTC,"Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'"
1698773,2017-06-28 10:45:20 UTC,"#needs-logs: nova-compute, nova-api"
1698773,2017-06-28 20:45:22 UTC,I'd also suggest providing `multipath -ll` output from the compute node after an attempted delete.
1698773,2017-07-03 13:58:06 UTC,instance uuid is 7023f1c1-a784-44a7-bddc-7e7821374577
1698773,2017-07-28 12:05:11 UTC,"Assuming this is an os-brick issue for now, @lyarwood, any update on this?"
1698780,2019-09-19 08:16:24 UTC,"It is not two installations. But after booting (not always - some times), it is showing two indicator menu icons on the menu bar. They both are functional."
1698784,2018-03-21 09:49:55 UTC,I tried to fix it where it crashes by this pull request at GitHub: https://github.com/jaap-karssenberg/zim-desktop-wiki/pull/394
1698784,2017-07-19 05:42:53 UTC,"Also, if the notebook name itself contains a non-ascii character, every page apart from root gives an Internal Server Error. In that case, however, the error message is different. Here log from trying to open page ""Page with only ascii characters in the name"" in notebook ""ääkköset web server"" using the embedded web server:"
1698784,2017-10-21 09:18:05 UTC,I see the same problem on Windows.
1698787,2017-06-19 15:46:38 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1698787,2018-03-12 02:13:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698794,2018-05-14 20:19:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698794,2018-09-08 23:59:52 UTC,"upgraded ubuntu to 18.04
```
ran.psg.com:/home/randy> uname -a
Linux ran.psg.com 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
```
/usr/bin/mail` no longer works.  this is becoming painful.
```
ran.psg.com:/home/randy> /usr/bin/mail -s foux randy < /dev/null
mail: mu_wordsplit failed: missing closing quote
mail: Unknown command: PѸÜU
mail: mu_wordsplit failed: missing closing quote
Segmentation fault (core dumped)
```
this is after an `apt install --reinstall mailutils mailutils-common`
```
ran.psg.com:/home/randy> /usr/bin/mail --version
mail (GNU Mailutils) 3.4
```"
1698795,2017-08-04 09:51:12 UTC,"We discussed it at GUADEC, the GNOME design is to use symbolic icons in the panel and our theme is missing ones to match our icons which creates the difference. But even if we fix the theme third party apps (and some of the default ones) are going to display a colored icon (e.g firefox) and it's going to be difficult to have visual conistency. One way would be to change the Ubuntu session to not display symbolic icons but always the normal one..."
1698795,2017-08-07 03:24:26 UTC,Is this humanity or just more missing icon symlinks (as usual) in ubuntu-themes?
1698795,2017-08-07 08:06:08 UTC,"Oh, sorry. This bug is about app icons. I was talking about indicators."
1698795,2017-08-07 12:15:25 UTC,"For now, let's use in the ubuntu session non symbolic icons:
- our theme doesn't support them and there are few changes we'll have app symbolic icons for our default applications in 17.10.
- for coherence reasons: most of branded apps outside of GNOME (firefox, chrome, thunderbird) don't have symbolic icons, and so, will appear colorized. Shipping two different experiences in the same session is weird. Let's ensure the ubuntu session don't use them by default thus."
1698795,2017-08-07 12:22:12 UTC,"Fedora includes a symbolic Firefox icon in their Firefox distro packaging:
http://pkgs.fedoraproject.org/rpms/firefox/blob/master/f/firefox-symbolic.svg"
1698795,2017-08-14 09:35:59 UTC,This bug was fixed in the package gnome-shell - 3.24.3-0ubuntu2
1698816,2017-07-12 09:02:23 UTC,"Any news on the incorportation of the upstream fix?
This is a blocker issue (application usage becomes so slow I had to switch to Thunderbird)."
1698818,2019-08-07 19:03:15 UTC,UI has been deprecated
1698818,2019-01-22 13:52:00 UTC,Is this still an issue?
1698818,2017-06-26 13:39:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477536"
1698818,2017-11-29 22:57:42 UTC,"Change abandoned by Ana Krivokapic (<email address hidden>) on branch: master
Review: https://review.openstack.org/477536"
1698831,2017-06-19 14:19:27 UTC,An initial workaround: https://review.openstack.org/475396
1698831,2017-06-23 19:17:15 UTC,"Reviewed:  https://review.openstack.org/475509
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_cinder/commit/?id=bdd22c7c2a08452ad82d37880cfeb83bf15b764f
Submitter: Jenkins
Branch:    stable/newton"
1698831,2017-06-19 19:35:41 UTC,"Reviewed:  https://review.openstack.org/475396
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_cinder/commit/?id=1bbe80e83dddbd14838f63c2c881627a74a3510b
Submitter: Jenkins
Branch:    master"
1698831,2017-06-19 19:49:40 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/475509"
1698831,2017-06-19 19:49:29 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/475508"
1698831,2017-06-23 18:33:01 UTC,"Reviewed:  https://review.openstack.org/475508
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_cinder/commit/?id=21f1cec004cff2a03705606cd58863b19c75630b
Submitter: Jenkins
Branch:    stable/ocata"
1698837,2018-03-08 11:57:18 UTC,Linked architecture page:
1698837,2020-02-21 08:34:38 UTC,Docs appear to be there for Train - and the architecture image shows up correctly.
1698838,2018-03-30 18:57:11 UTC,"We often use that drop-down, so we'd much prefer the drop-down-with-only-some-choices-enabled approach."
1698838,2018-08-31 15:26:39 UTC,"In this case, the only choice that would be enabled is the status that the item is in right now since it is already in the magical status. My preference is to see the entire selector disabled with the current status displayed."
1698847,2017-08-08 11:20:41 UTC,"So, with the latest (at the time of this comment) designate development charm, I can't reproduce this problem.  I've tried with and without designate-bind, scaling from 3 -> 2, 4 -> 3, etc.  The system always settles to idle and doesn't exhibit this problem."
1698847,2020-09-22 04:17:17 UTC,[Expired for OpenStack Designate Charm because there has been no activity for 60 days.]
1698867,2017-06-19 16:01:19 UTC,Update: Seems you can do this as a workaround.
1698888,2017-06-22 17:05:08 UTC,Thank you for this! Snapcraft should use a specific arch.
1698888,2018-07-17 14:50:27 UTC,This bug affects me as well. I was able to build a snap package with snapcraft for amd64 with the following hack:
1698889,2017-06-19 16:38:48 UTC,"FWIW, we are working on supporting newer Django versions, and as such, we are not concerned with the upgrade of it in the archives!"
1698889,2017-06-19 18:40:08 UTC,"This breaks my local maas install, since I'm running it on artful. After upgrade, I can't use the MaaS CLI:"
1698895,2017-06-19 16:49:48 UTC,See also bug #1636933
1698895,2019-09-19 14:48:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1698911,2017-08-09 10:22:54 UTC,"Hi, Please share more info /etc/magnum/magnum.conf . Also transport_url doesnot include port number as given in https://docs.openstack.org/project-install-guide/container-infrastructure-management/ocata/install-rdo.html"
1698911,2017-09-26 14:54:34 UTC,/etc/magnum/magnum.conf
1698919,2017-06-19 18:43:49 UTC,CVE-2017-1000364
1698919,2017-06-22 12:11:36 UTC,The fix for Xenial Xerus x86_64 (linux-image-4.4.0-81-generic) seems to break all versions of the Oracle Java plugin in all browsers while it works fine in Linux 4.11.6. See Bug #1699772 for details.
1698919,2017-06-22 21:04:58 UTC,This fix breaks Scilab 5.5.2 on Xenial - see bug 1699892 for details.
1698919,2017-06-22 22:40:38 UTC,"This fix causes problems with LPCxpresso (see https://community.nxp.com/thread/453939 ), RMongo (see https://stackoverflow.com/a/44699417 ), and may be others."
1698919,2017-06-22 22:47:50 UTC,It brokes UniFi Controller (see https://community.ubnt.com/t5/UniFi-Wireless/UniFi-Controller-failed-after-dist-upgrade/td-p/1967779 ).
1698919,2017-06-23 15:13:51 UTC,This fix breaks Scilab 5.5.0 on Trusty - see bug 1699892 for details. Kernel linux-image-3.13.0-121-generic is a problem.
1698919,2017-06-23 15:17:20 UTC,"as addition to my comment 7 - Trusty is affected too, see Raven's comment."
1698919,2017-07-26 15:23:34 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1698919,2018-07-24 09:30:46 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1698919,2017-06-23 15:15:32 UTC,New kernel in Xenial broke Eclipse (see https://askubuntu.com/questions/927746/eclipse-crashes-with-linux-kernel-4-4-0-81-generic ).
1698933,2017-06-20 21:42:33 UTC,"I did fine out that I could add the printer using one of the alternative options, but that failed in FAX sending."
1698962,2017-06-20 03:55:03 UTC,"This is completely harmless, KeyboardInterrupt is Python's way of signalling that the program was interrupted through the keyboard."
1698962,2020-05-21 12:58:53 UTC,works in focal
1698970,2017-06-21 03:59:54 UTC,PR against develop (2.3): https://github.com/juju/juju/pull/7527
1698977,2021-01-07 02:11:31 UTC,This bug was fixed in the package apt-btrfs-snapshot - 3.5.5
1698983,2017-06-20 10:26:49 UTC,"Without getting into design ideas, can you give me an idea of how you see this working? Would it be a phase to run a juju action? What would you do with the output?"
1698983,2017-06-20 21:03:21 UTC,The actions I presently want to invoke are
1698984,2017-06-20 01:38:13 UTC,I had to disable the Qt bindings and the docs as they don't build on Trusty. We could enable them if necessary with some patching (I doubt there is a need for either at the current time).
1698984,2017-06-20 03:33:46 UTC,The patch to make this work is in the glib-2-40 branch on GitHub (https://github.com/snapcore/snapd-glib/tree/glib-2-40).
1698984,2017-09-13 21:42:41 UTC,Currently stuck in NEW queue...
1698988,2017-06-26 18:32:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1698988,2021-01-07 04:11:19 UTC,4.8 EOL
1699051,2017-06-22 14:05:49 UTC,There was no precise release for 2017.06.07 cycle.
1699054,2019-12-02 10:11:50 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/696851"
1699058,2017-06-20 08:56:29 UTC,"Hi Tejas,"
1699058,2017-06-20 10:19:05 UTC,"Hi Tim,"
1699058,2017-06-20 10:42:29 UTC,"   ""Am I right in understanding from your description above that if you don't build the libs with -flto, gdb correctly shows the paths?"""
1699058,2017-06-20 08:40:34 UTC,"Hi Tim,"
1699059,2017-07-02 15:28:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699060,2018-10-24 18:59:06 UTC,"@Ben, this is nothing to do with oslo-policy. it has to do with the values passed to oslo-policy in the creds dict. If the creds dict does not have domain-id populated in it, you can't enforce on it."
1699060,2018-10-14 04:18:37 UTC,"This is actually due to oslo-context, which is what the services use to enforce policy."
1699060,2018-07-30 17:33:20 UTC,From this bug I'm not clear exactly what would be needed from oslo.policy for this.  I know we just merged https://github.com/openstack/oslo.policy/commit/775641a5fc549c20be37cf862deca394bf7f2d21 which allows policy to deal with context objects.  Would that be helpful here?
1699060,2018-01-18 15:54:24 UTC,"Agree with above. If we want this, this needs to be a general policy change across projects, and not something each project needs to address. This is a new feature request (probably for oslo.policy) and not a bug."
1699060,2018-01-30 12:12:45 UTC,I agree with Sean. It is worth tackled as a cross project topic.
1699060,2017-06-20 20:29:07 UTC,"Kirill,"
1699060,2017-06-20 12:44:23 UTC,"please don't create these openstack-wide bugs, it spams everyone. i've removed telemetry projects but feel free to apply patches to them (don't do it for ceilometer since it doesn't have an active api)."
1699060,2017-06-20 13:32:51 UTC,"Yeah, I don't think opening bugs against every project is the right way to go here. This really is a cross project thing that could use some discussion. Maybe start a mailing list thread?"
1699060,2017-06-23 16:57:32 UTC,"Items like this for Nova would definitely need a spec, it's not a bug"
1699060,2017-06-20 20:11:08 UTC,Mass opening bugs definitely not going to solve this. Also it's not quite clear from the bug or mail — what the projects should/shouldn't do. Is it really an issue with oslo.policy?
1699060,2017-06-20 13:42:11 UTC,Mail list thread is here: https://openstack.nimeyo.com/115438/openstack-dev-all-policy-rules-for-apis-based-on-domain_id
1699073,2017-06-20 09:26:48 UTC,I've edited the svg file to recover most of my data : the bug disappear when i get ride of the only hkern entry i've managed to add before having my initial work session crashing :
1699075,2017-06-21 01:15:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/475971"
1699075,2017-07-14 11:56:18 UTC,"Reviewed:  https://review.openstack.org/475971
Committed: https://git.openstack.org/cgit/openstack/mogan/commit/?id=ad83d1be16b896ae5399b52b9300c0c2f83ad1f4
Submitter: Jenkins
Branch:    master"
1699084,2017-06-20 09:58:24 UTC,Since -r 557 it is possible to workaround this with:
1699084,2017-06-20 10:44:21 UTC,"Fix committed into lp:miral at revision None, scheduled for release in miral, milestone Unknown"
1699084,2017-07-19 11:50:25 UTC,"OK, the reason for this is that MirAL is looking for cursor images of Mir's default 24x24 size and not finding any."
1699084,2017-07-20 09:23:47 UTC,"Fix committed into lp:miral at revision None, scheduled for release in miral, milestone Unknown"
1699084,2017-06-20 10:55:17 UTC,"Linked branch mitigates the impact, but doesn't fix the underlying problem"
1699103,2017-06-20 10:57:10 UTC,OS is Fedora 25 with last updates
1699110,2017-06-21 02:05:40 UTC,The important log file (DKMSBuildLog.txt) appears to be incomplete and isn't showing what went wrong (unless what went wrong was the whole system freezing).
1699110,2017-07-01 07:37:56 UTC,"I just logged into my system, the update-manager popped up and said there where a number of updates. When I told it to install them it went ahead, but in the middle of the update it reported that Ubuntu had experienced a problem (the update went on though) and when I reported it it offered me a largish number of issues that might be duplicates. I chose this one because it had the exact same subject line as the bug report generated for me."
1699110,2017-07-16 08:44:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699110,2017-08-29 06:35:19 UTC,Same here... i got the error after rebooting due to updates... As soon as desktio showed (after login screen) i got the message...
1699125,2017-06-21 01:46:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699126,2017-10-08 18:03:57 UTC,You just need to patch configure.ac with something like this:
1699126,2017-06-20 18:33:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699126,2017-06-20 20:24:50 UTC,Thanks for reporting.
1699132,2018-11-19 16:01:41 UTC,"Hi @gabor can you specifc which release of openstack you hit this issue with? I ask because I think there are two issues in the charm, first is the one you hit i.e. old records not removed but with Rocky these don't get updated at all since the charm is hardcoded to use python-designateclient which is deprecated and hardwired to use the deprecated v1 api. Solution is to switch to python-openstackclient (or just use the api direct) and also use designate-maname [1]. I'll raise a seperate bug for the second issue."
1699132,2018-11-20 14:18:27 UTC,"hello Ed, I'm running this on top of Ocata. I'll take a look at the openstackclient, thanks for the idea."
1699132,2018-12-12 11:07:47 UTC,This issue seems to be related to Designate bug [1]
1699132,2018-12-17 11:33:50 UTC,I believe this is invalid.
1699154,2017-06-20 19:39:06 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1699154,2017-06-21 11:45:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699154,2017-07-01 10:22:18 UTC,System on VMware Workstation 12 Player
1699154,2021-01-07 04:11:01 UTC,4.8 EOL
1699161,2017-10-30 11:58:39 UTC,debdiff for Xenial
1699161,2017-10-30 21:36:09 UTC,(re: comment #12)
1699161,2017-10-27 16:51:40 UTC,This bug was fixed in the package lshw - 02.18-0.1ubuntu4
1699161,2017-11-02 23:25:06 UTC,"Hello Christian, or anyone else affected,"
1699161,2017-11-09 17:44:21 UTC,This bug was fixed in the package lshw - 02.18-0.1ubuntu4
1699161,2017-11-03 13:00:54 UTC,### VERIFICATION XENIAL ####
1699161,2017-11-09 17:44:02 UTC,This bug was fixed in the package lshw - 02.18-0.1ubuntu3.1
1699161,2017-11-09 17:44:08 UTC,"The verification of the Stable Release Update for lshw has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1699161,2017-11-09 17:45:29 UTC,This bug was fixed in the package lshw - 02.17-1.1ubuntu3.4
1699161,2017-11-03 01:10:51 UTC,(As requested by bdmurray)
1699161,2017-10-26 21:13:12 UTC,### VERIFICATION ZESTY ###
1699161,2017-11-02 22:13:36 UTC,Could you confirm that lshw still works in unprivileged containers? After that's done I'd feel good about releasing this SRU.
1699161,2017-10-26 18:30:36 UTC,"Hello Christian, or anyone else affected,"
1699161,2017-10-26 21:09:39 UTC,### VERIFICATION ARTFUL ###
1699161,2017-06-20 17:25:14 UTC,According to this core:
1699161,2017-06-20 17:29:15 UTC,"In this container there is no /proc/bus/usb, and while /sys/kernel is present, I can't even list it:"
1699161,2017-06-26 06:35:52 UTC,"Unable to reproduce in a normal unprivileged container:
```
stgraber@castiana:~$ lxc launch ubuntu:16.04 unpriv
Creating unpriv
Starting unpriv
stgraber@castiana:~$ lxc exec unpriv bash
root@unpriv:~# ls -lh /sys/kernel/
total 0
drwxr-xr-x   2 nobody nogroup    0 Jun 26 06:32 boot_params
drwx------  38 nobody nogroup    0 Jun 24 14:56 debug
-r--r--r--   1 nobody nogroup 4.0K Jun 26 06:32 fscaps
drwxr-xr-x   2 nobody nogroup    0 Jun 26 06:32 iommu_groups
drwxr-xr-x  38 nobody nogroup    0 Jun 26 06:32 irq
-r--r--r--   1 nobody nogroup 4.0K Jun 26 06:32 kexec_crash_loaded
-rw-r--r--   1 nobody nogroup 4.0K Jun 26 06:32 kexec_crash_size
-r--r--r--   1 nobody nogroup 4.0K Jun 26 06:32 kexec_loaded
drwxr-xr-x   2 nobody nogroup    0 Jun 26 06:32 livepatch
drwxr-xr-x   6 nobody nogroup    0 Jun 26 06:32 mm
-r--r--r--   1 nobody nogroup  516 Jun 26 06:32 notes
-rw-r--r--   1 nobody nogroup 4.0K Jun 26 06:32 profiling
-rw-r--r--   1 nobody nogroup 4.0K Jun 26 06:32 rcu_expedited
-rw-r--r--   1 nobody nogroup 4.0K Jun 26 06:32 rcu_normal
drwxr-xr-x   4 nobody nogroup    0 Jun 24 14:55 security
drwxr-xr-x 140 nobody nogroup    0 Jun 26 06:32 slab
dr-xr-xr-x   2 nobody nogroup    0 Jun 26 06:33 tracing
-rw-r--r--   1 nobody nogroup 4.0K Jun 24 14:55 uevent_helper
-r--r--r--   1 nobody nogroup 4.0K Jun 26 06:32 uevent_seqnum
-r--r--r--   1 nobody nogroup 4.0K Jun 26 06:32 vmcoreinfo
root@unpriv:~# lshw >/dev/null
root@unpriv:~# echo $?
0
root@unpriv:~#
```"
1699161,2017-06-26 06:37:39 UTC,"Updated the description with more details, re-assigned to the lshw package."
1699161,2017-06-20 15:32:26 UTC,"However, lshw -disable USB does work fine."
1699161,2017-10-11 17:04:04 UTC,"I just sent a proposal patch to Lyonel Vincent, since I couldn't create a bug properly in their tracker."
1699161,2017-10-23 16:50:46 UTC,Debdiff for artful
1699161,2017-10-23 17:11:21 UTC,Debdiff for zesty
1699161,2017-10-23 17:13:28 UTC,"1) Sponsored for Artful (now consider stable)[1] and Zesty.
2) Xenial SRU will have to wait (LP: #1471983) is completed."
1699161,2017-10-26 18:29:04 UTC,"Hello Christian, or anyone else affected,"
1699161,2017-10-11 15:49:11 UTC,Update:
1699176,2017-06-20 15:07:12 UTC,After looking closer at the results of the tests one way to fix this would be to actually just change the test hash values to the new ones as these are the only changes that have appeared. They look like harmless as the output is identical to the previous ones.
1699176,2017-06-20 15:07:55 UTC,By 'the output is identical' I mean how the pdf generated out of the tex file.
1699176,2017-06-22 09:58:48 UTC,"For reference, logs to a failure against the new octave:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/m/matlab2tikz/20170612_093659_5f751@/log.gz"
1699176,2017-06-22 10:00:12 UTC,"Forwarded proposed hash change to upstream with the following PR:
https://github.com/matlab2tikz/matlab2tikz/pull/995"
1699229,2018-06-06 14:20:18 UTC,"FYI. I have done some work on this idea.  Enough to have it working for posix and WIN32.  I think I know to do this for RTEMS as well, and by extension vxworks.  Though I still don't have a firm timetable for doing this."
1699229,2017-06-20 21:16:42 UTC,"VxWorks doesn't have anything like a taskJoin() routine, so implementing this there would require pulling functionality from epicsThread::exitWait() and epicsThreadCallEntryPoint() down into the os/vxWorks/osdThread.c implementation."
1699229,2017-11-08 15:48:52 UTC,lp:1730982 is related.
1699248,2018-01-26 17:03:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538308"
1699248,2018-07-24 13:52:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585361"
1699250,2017-06-26 13:10:16 UTC,Please specify your Lifeograph and Gnome versions. It may be related to Wayland. Could you try it under X?
1699250,2020-03-15 09:10:29 UTC,Closing due to long time no feedback.
1699273,2017-06-22 09:27:45 UTC,Related bug in magnum: 1699735
1699274,2017-11-10 03:39:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699275,2017-09-08 02:17:14 UTC,I am having what I believe to be the same problem. Here is the log file:
1699275,2017-09-08 02:17:52 UTC,Oops - forgot to mention that I am running latest keryx 0.92.5
1699275,2017-06-23 18:34:13 UTC,"Weird. Even if you have no projects created, it should let you browse for
one. Can you check the logs folder and paste the contents of the log file
here?"
1699275,2017-06-23 17:35:18 UTC,https://launchpad.net/keryx/stable/0.92/+download/Keryx 0.92.5.zip
1699275,2017-06-29 15:51:33 UTC,"[17-06-29 16:41:41] INFO    wxWidgets interface loaded
[17-06-29 16:41:56] INFO    Shutting down"
1699275,2017-06-20 17:04:47 UTC,"Hey, Win! I notice from the log messages this is from a slightly old version of Keryx. Can you download 0.92.5 from here: https://launchpad.net/keryx/stable/0.92"
1699292,2019-06-27 08:50:47 UTC,I wonder if things have improved since this bug was reported?
1699292,2019-08-27 04:17:22 UTC,[Expired for juju because there has been no activity for 60 days.]
1699294,2017-10-13 15:26:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699295,2017-06-20 18:07:22 UTC,Linux mint 18.1
1699300,2017-06-26 16:51:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699300,2021-01-07 04:10:53 UTC,4.8 EOL
1699322,2018-06-05 14:13:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699324,2017-06-21 00:14:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/475961"
1699324,2017-12-13 20:42:58 UTC,I see the same issue. This is on x86 and ubuntu/centos.
1699324,2018-04-06 17:21:42 UTC,Waiting on fix to merge.
1699335,2017-07-27 20:49:56 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.
1699335,2017-06-21 11:11:41 UTC,"Yes, It can be backported in stable/ocata.
Thanks for filing the bug. would be good to track.
Need its association with fixing patch."
1699335,2017-06-22 14:46:52 UTC,"Reviewed:  https://review.openstack.org/475916
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=2e3b6639fe7dd4fd2fce48c950a18f4366364df8
Submitter: Jenkins
Branch:    master"
1699335,2017-06-22 17:42:00 UTC,"Change abandoned by Michal Jastrzebski (inc0) (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/476643"
1699337,2018-05-08 18:11:51 UTC,This change was made by a bot.
1699337,2021-01-07 04:10:49 UTC,4.8 EOL
1699351,2018-03-09 10:45:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699357,2017-06-20 23:49:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699359,2019-12-09 08:12:08 UTC,Migrated to:  https://gitlab.com/inkscape/inbox/issues/1324
1699360,2017-08-31 09:16:15 UTC,Unfortunately not.
1699360,2017-06-27 15:18:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699360,2017-08-30 22:26:02 UTC,Did the problem resolve after updating to zesty-proposed?
1699360,2017-06-27 09:51:38 UTC,The only thing that libpam-systemd postinst does is call
1699360,2017-06-23 05:40:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699360,2017-06-27 09:58:06 UTC,This is probably due to missing gnome-software update
1699360,2017-06-25 00:44:02 UTC,Picture included
1699374,2017-06-21 04:41:08 UTC,"Thank you, it's working on :667"
1699374,2017-06-21 05:01:32 UTC,Sorry about the documentation. I can't change what's in that magazine. :)
1699374,2017-06-21 05:50:44 UTC,"On Ubuntu 16.04.2, it starts from :666 as specified in /etc/darkstat/init.cfg after a reboot.  After this, changes to the config file port value seem to be observed following service darkstat restart.
A little confusing but solved, thanks."
1699374,2017-06-21 06:15:42 UTC,"Great, sounds like the distro part is working correctly! What's left to do in this bug?"
1699374,2017-06-21 07:21:11 UTC,"Not a bug as such as far is the software is concerned, but I wonder if confusion could be avoided if the port number value in the config file matched the actual default."
1699374,2017-06-21 10:26:13 UTC,"darkstat v2.x used 666
darkstat v3.x used 667"
1699374,2017-06-22 05:13:39 UTC,"Herewith the relevant part of comment #3, which has been hidden as I neglected to remove my email footer."
1699374,2017-06-21 03:19:30 UTC,Try: sudo darkstat -i eth0 --debug
1699374,2017-06-21 04:20:37 UTC,"The default webserver port should be 667. Try: ""netstat -lntp"" while darkstat is running."
1699376,2017-06-21 19:40:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699376,2017-06-21 19:40:39 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1699376,2021-01-07 04:10:44 UTC,4.8 EOL
1699381,2017-06-22 01:07:25 UTC,"Oh excellent!  I'm glad you came along to check into this, Eduard!"
1699381,2017-06-21 09:46:56 UTC,"thank you for taking the time to issue a report. I am not able to reproduce the problem using the extension Color->Replace Color on Windows 10, Inkscape 0.92.1 r15371. The relevant color data is stored in the preferences file in the variables:
     org.inkscape.color.replacecolor.from_color=""ff0000""
     org.inkscape.color.replacecolor.to_color=""00ff00"""
1699381,2017-06-21 12:42:24 UTC,"Thank you for taking the time to try to reproduce it!  I'm sorry, I seem to have wasted your time.  I'll try to come up with a better reproduction case."
1699381,2017-06-21 03:17:26 UTC,"Ah, never mind my ""spurious cast"" comment; I was misreading the member function ""string"" as a cast.  In any event, the code doesn't seem to work, and I don't see the color param show up in my preferences file at all."
1699381,2017-06-22 00:54:57 UTC,Issue confirmed with Inkscape 0.92.1 r15371 as well as current master.
1699390,2017-06-21 04:26:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/475995"
1699390,2017-11-05 11:15:03 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/475995
Reason: This review is > 3 months without comment and currently blocked by a core reviewer with a -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -1 on this review to ensure you address their concerns."
1699420,2017-06-21 05:51:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/476008"
1699427,2017-06-23 07:46:11 UTC,"Let me organize my thoughts. The purpose is that you want to use mysql in the mounted directory, right?
If so, please do this step by step.
1. Create two directories, say, <encrypted> and <decrypted>.
2. Execute ""sudo mount -t ecryptfs <encrypted> <decrypted>""
3. Then use basic file operations command and manipulate mysql in <decrypted> to see what will happen."
1699427,2017-06-23 06:13:46 UTC,I think the Pam issues relating to automount may be a red herring.
1699427,2017-06-23 05:15:53 UTC,Managed to get the following from our journal logs recorded just prior to the system crash.
1699427,2017-06-23 03:09:05 UTC,"No, unfortunately as stated before - no errors, no logs and no information whatsoever."
1699427,2017-06-23 00:46:29 UTC,Tried various mounting options as well as various mount points. I followed the steps for manual mounting but none of these actions appears to have any affect and the end result of a system crash without any error or warning is always and consistently the same.
1699427,2017-06-22 10:17:10 UTC,"Hello,"
1699427,2017-06-23 02:02:03 UTC,"I mean create two directories and do manual mount again.It seems that you've tried this method. Okay, that's really weird.Do you have some messages in the log (checking by ""dmesg"")?"
1699427,2017-06-22 00:15:28 UTC,If tried to set reboot on oops and kernel panic of three seconds but it does not appear to be hitting a kernel panic.
1699427,2017-06-21 23:50:41 UTC,"Hi Jason,"
1699427,2017-06-21 06:58:05 UTC,Does it work well when you create/remove some files in /var/lib/mysql? Can you see the contents of files in that directory when mounting/unmounting?
1699428,2017-07-09 06:09:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699428,2021-01-07 04:10:36 UTC,4.8 EOL
1699432,2017-07-05 05:23:04 UTC,"Looks like when the subnet is updated, logical_switch_port.dhcpv4_options is cleared. The expected behavior should have been to set logical_switch_port.dhcpv4_options = [e04f1a25-2134-49c6-b2db-6e688d8bcbb0]"
1699465,2017-09-27 05:58:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/507744"
1699465,2017-10-04 06:25:20 UTC,"Reviewed:  https://review.openstack.org/507744
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=c892077c75245cfc70e377a9d0a475867dd23b39
Submitter: Jenkins
Branch:    master"
1699465,2017-08-11 16:27:57 UTC,"Reviewed:  https://review.openstack.org/487660
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=87fb09f4edbccedb697b70eab2ed3b5aed7ccda9
Submitter: Jenkins
Branch:    stable/ocata"
1699465,2017-07-11 05:26:26 UTC,i added openstack version in the description
1699465,2017-06-22 02:32:35 UTC,"Reviewed:  https://review.openstack.org/467966
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=399cab82b8782c47d47384afa766175d7fab374a
Submitter: Jenkins
Branch:    master"
1699465,2017-07-27 02:00:29 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/487660"
1699465,2017-06-26 16:52:56 UTC,"No version was found in the description, which is required, marking as Incomplete. Please update the bug description to include 'devstack version: ... '."
1699472,2017-06-21 10:16:48 UTC,build arch:all on the fastest builder? (s390x)
1699487,2017-11-14 05:30:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699496,2017-06-22 20:42:28 UTC,"I thought the DB code took care of this?  At the end of _make_router_dict(), called from create_router():"
1699496,2017-06-23 06:51:01 UTC,That is for the response only though. Normally the router that enters the create_router function should already have all defaults applied as set in the attributes dict.
1699511,2018-05-08 18:12:15 UTC,This change was made by a bot.
1699511,2021-01-07 04:10:30 UTC,4.8 EOL
1699526,2017-07-18 10:28:26 UTC,It looks like install/remove hooks just landed a few days ago. I will see if they are actually present anywhere available to end-users yet.
1699526,2017-06-22 16:44:12 UTC,"No, good point -- converted this bug."
1699526,2017-07-18 07:49:12 UTC,bump ;)
1699526,2017-06-21 19:40:09 UTC,Fresh install of 16.04.2 desktop in a VM:
1699526,2017-06-21 17:43:53 UTC,"On 21.06.2017 [17:15:31 -0000], ChristianEhrhardt wrote:

> On Wed, Jun 21, 2017 at 6:42 PM, Nish Aravamudan <
> <email address hidden>> wrote:
>
> > 4) For your case, are you running from the git repository or the snap?
>
>
> Snap.
"
1699526,2017-06-21 17:15:31 UTC,"On Wed, Jun 21, 2017 at 6:42 PM, Nish Aravamudan <
<email address hidden>> wrote:"
1699526,2017-06-21 16:42:52 UTC,"1) The snap manpage already works, at least in my testing."
1699526,2017-06-22 05:48:45 UTC,"Do you have a bug to track to (one day) do this .rc setup once unblocked by the availability of uninstall hooks?
If not do you want to convert this bug into just such a bug?"
1699529,2019-04-01 06:47:48 UTC,"Hmm, I meant to attach apport-collect data just to have all in one place.
But it didn't add a lot :-)"
1699529,2019-04-01 08:33:41 UTC,"Note that the inital report was about flaky tests. This JVM crash causing failure is consistently happening at every test run, so technically that's a different problem, but it's probably okay to recycle this bug."
1699529,2019-04-01 08:31:06 UTC,Thanks for the detailed investigation Christian.
1699529,2019-04-01 07:38:36 UTC,MP up at https://code.launchpad.net/~paelzer/britney/hints-ubuntu-xenial-i386-libreoffice/+merge/365333
1699529,2019-04-01 07:34:46 UTC,"Oh it is rather trivial why the force-badtest no more works, there were uploads that got released but did not bump the test hinting - I'll provide an MP"
1699529,2019-04-01 07:25:53 UTC,"I knew all of this seemed somewhat known to me and look at that [1].
We merged such a change to ignore the error (I was about to ask about that) in the past.
It should actually already be an ignored error, but [2] currently complains."
1699529,2019-04-01 07:25:38 UTC,"BTW the dbg symbols have broken dependencies, I forked bug 1822538 for that.
Due to that debug symbols where a bit harder to install than usual."
1699529,2019-04-01 06:46:28 UTC,apport information
1699529,2019-04-01 06:45:04 UTC,"Here the core dump that the test generates.
Here [1] is a installed package list, but it is just Xenial as installed by the test as of today - nothing special and since the issue persists since almost two years I guess that isn't too important."
1699529,2019-04-01 06:46:26 UTC,apport information
1699529,2019-04-01 06:46:27 UTC,apport information
1699529,2017-06-21 14:54:12 UTC,"Olivier, would be good if you could look at this if you have some time ..."
1699529,2017-06-23 10:03:00 UTC,"For some of the failures (not all of them), the log ends with:"
1699529,2017-06-23 10:05:07 UTC,"Other runs complete but there are actual failures in junit-subsequentcheck, e.g.:"
1699529,2019-04-01 06:40:10 UTC,"This was reported for artful which is EOL nowadays.
But the very same RowSet error is still an issue and it seems that it blocks all i386-xenial tests since mid 2017 [1] - that is the last 41/41 tests.
I think we can agree that that seems pretty consistently broken for now."
1699529,2017-06-23 10:23:11 UTC,The complex.dbaccess.RowSet failure happens because the soffice executable crashed (exit code 139 == SIGSEGV). Indeed:
1699529,2019-04-01 06:41:14 UTC,Isolated run into C/Java stack trace
1699529,2019-04-01 06:46:25 UTC,"ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
DistroRelease: Ubuntu 16.04
Package: libreoffice
PackageArchitecture: i386
ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170
Tags:  xenial
Uname: Linux 4.4.0-143-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True"
1699529,2017-06-23 10:07:39 UTC,Other common failures:
1699530,2018-07-03 12:21:45 UTC,Please stop distributing gogglesmm 0.12.7 as this version is over 4 years old and plenty of newer versions have been released in the mean time.
1699530,2018-07-04 08:35:59 UTC,An updated version 1.2.0 is provided in my own PPA: https://launchpad.net/~s.jansen/+archive/ubuntu/gogglesmm
1699530,2019-03-06 02:49:01 UTC,"Seriously, I rather you just remove my software from this repo, than having a very old version being kept on distributed."
1699530,2019-04-17 19:06:22 UTC,"Removing packages from disco:
 gogglesmm 0.12.7-3build2 in disco
  gogglesmm 0.12.7-3build2 in disco amd64
  gogglesmm 0.12.7-3build2 in disco arm64
  gogglesmm 0.12.7-3build2 in disco armhf
  gogglesmm 0.12.7-3build2 in disco i386
  gogglesmm 0.12.7-3build2 in disco ppc64el
  gogglesmm 0.12.7-3build2 in disco s390x
Comment: Upstream requests not to release stale upstream version; LP: #1699530
1 package successfully removed."
1699530,2017-10-13 16:31:17 UTC,Thanks for reporting.
1699536,2017-06-21 22:34:06 UTC,"> sudo -E chroot /tmp/dib_build.98HoVIqX/mnt env
"
1699536,2017-06-24 10:25:32 UTC,"Ian, I instrumented diskimage_builder/lib/img-functions and dropped into a shell in the run_in_target() function."
1699540,2017-12-21 03:43:47 UTC,"manually edit /etc/locale.gen, un-comment"
1699551,2017-08-06 11:48:04 UTC,That error happened once and disappeared to never be shown again for now.
1699551,2017-08-06 10:49:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699551,2017-06-21 19:20:35 UTC,Same error here.
1699552,2017-10-10 14:55:14 UTC,This bug is also now blocking the nova-lxd gate
1699563,2017-06-21 21:20:53 UTC,This bug appears to be a duplicate of two different bugs. bug 1387803 covers the xul portion of this bug.
1699563,2017-06-21 21:22:58 UTC,"And...I just realized bug 1684202 is actually about Holdings View, so I'm removing the duplicate status."
1699567,2020-11-09 17:55:29 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1699567,2020-11-29 05:51:42 UTC,"I am currently running into this bug on QEMU emulator version 5.1.0.
movaps unaligned access works fine in qemu, when it should throw a GP. Likewise, the same code on physical hardware throws a GP."
1699567,2020-11-30 15:25:26 UTC,Yep.  Long-standing bug.
1699569,2017-06-22 02:31:30 UTC,This seems to be a recurrence of bug 1358966. That one was marked as Fix Released in vivid so I guess we should track the problem in a new bug now (this one).
1699569,2017-06-29 08:14:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699582,2017-06-21 23:56:49 UTC,https://review.openstack.org/#/c/476243/
1699592,2020-03-26 02:52:05 UTC,We don't use those template scripts anymore and foreign architecture was never really supported in the first place (and indeed inconsistently between templates).
1699592,2017-06-21 20:53:17 UTC,Whoops not quite addressing the issue
1699592,2017-06-21 20:30:22 UTC,It's under zesty
1699592,2017-06-21 20:35:02 UTC,"Looks related to bug 1671990 but it's marked as invalid. However, I'm not running lxc-create inside another container. It is under qemu-user-static though."
1699592,2017-06-21 20:29:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1699592,2017-06-21 20:51:42 UTC,https://wiki.debian.org/LXC#Debian_8_.22Jessie.22
1699593,2017-11-02 19:23:07 UTC,"it writes to the log at the configured log value.
Add a '-v' and you'll get something there.
its admittedly not a lot."
1699604,2017-06-22 19:42:26 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1699605,2019-10-02 06:17:25 UTC,"Hi G,
yes, I still see this issue on Disco with chromium and dark theme (this was a fresh install as well)."
1699605,2019-10-02 08:58:59 UTC,"Hi Olivier, I already did back when I noticed: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1824191"
1699605,2019-10-02 08:03:00 UTC,"Alberto, this issue was reported against firefox and thunderbird, not chromium.
The chromium issue is most likely a separate one, would you mind filing a separate bug for it at https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+filebug ?"
1699605,2018-07-22 19:27:24 UTC,"Thanks for the update, Wolf. I have checked with Alberto to see if he still has the issue.
Have a great day!
:)
G"
1699605,2018-04-05 08:55:26 UTC,Known issue upstream. It is a years old Firefox issue - workaround as described here:
1699605,2018-07-22 18:07:47 UTC,"Hi G,
this bug has been eliminated on my computer a long time ago (I did a fresh install for 18.04 as well)"
1699605,2018-07-20 17:05:44 UTC,"Hello Wolf,
Thank you for submitting this bug and reporting a problem with foreground and background colors in Thunderbird and Firefox. You made this bug report some time ago and Ubuntu, Firefox and Thunderbird has been updated since then."
1699605,2018-04-05 08:44:00 UTC,I have the same behavior in Bionic
1699605,2018-04-05 08:43:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699605,2018-07-22 19:24:41 UTC,"Hi Alberto,
I have subscribed you to this ticket so we can contact you regarding your report (comment #3 above)."
1699608,2017-06-21 21:49:07 UTC,"Apologies, I missed a couple of lines from my steps to reproduce when copy & pasting it over from my terminal history."
1699608,2017-06-21 22:07:56 UTC,*sigh* - even the second attempt I missed a zero in that sed command. I'll take myself to bed soon. It should have read:
1699617,2017-06-24 08:39:11 UTC,Thanks for reporting.
1699618,2017-06-26 23:06:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699621,2017-06-22 20:30:07 UTC,This change was made by a bot.
1699622,2017-06-21 23:24:15 UTC,Note that I reproduced this 3 times in a row.
1699622,2019-09-19 14:48:35 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1699625,2017-08-09 23:00:47 UTC,"I updated to the Remmina PPA latest version and it works better. But there are still strange cases where full-screen Remmina freezes my control over Ubuntu. I experience mouse control but no keyboard control. It seems like the 'grab keyboard' option gets stuck in some way. And I can't close or disable Remmina in such cases. Possibly only with RDP connections, I don't seem to see this bug with VNC connections."
1699625,2018-08-08 00:37:11 UTC,With Remmina 1.2.31.2 (from Remmina PPA) everything seems well behaved.
1699628,2020-04-30 13:33:07 UTC,"Fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=4ba664cb0aab"
1699631,2017-08-17 09:38:43 UTC,"Reviewed:  https://review.openstack.org/494391
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=2af0a09ef5645719efa16740b974be5260c44b38
Submitter: Jenkins
Branch:    release/2.9"
1699631,2017-08-17 06:24:25 UTC,"Fix proposed to branch: release/2.9
Review: https://review.openstack.org/494391"
1699631,2017-08-17 07:05:36 UTC,"Reviewed:  https://review.openstack.org/487674
Committed: https://git.openstack.org/cgit/openstack/fuel-devops/commit/?id=e67743b22c7da6cb27c264c9906c2904f9247d6c
Submitter: Jenkins
Branch:    master"
1699634,2017-06-22 01:33:48 UTC,"confirmed on Windows 10, Inkscape 0.92.1 r15371"
1699634,2017-06-22 01:48:55 UTC,duplicate of https://bugs.launchpad.net/inkscape/+bug/1691406 ?
1699634,2017-06-22 01:59:38 UTC,Look like maybe also a duplicate of or related to https://bugs.launchpad.net/lib2geom/+bug/1545489
1699637,2017-12-17 22:53:03 UTC,Can you attach /var/log/lightdm/lightdm.log - that might give a better idea where this is occurring.
1699637,2018-02-13 20:44:45 UTC,"I'm having the exact and/or similar problem, but I'm running on an Arch based distro. My Log is as follows:"
1699637,2018-02-13 20:45:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699637,2018-03-28 08:43:22 UTC,"Hi,
I've just upgraded my x86_64 laptop to Ubuntu 17.10, and I believe I'm hitting the same problem."
1699649,2018-05-08 18:12:31 UTC,This change was made by a bot.
1699649,2021-01-07 04:10:26 UTC,4.8 EOL
1699655,2017-06-22 21:51:29 UTC,I'm making this bug public as it looks to be the same crash as what's in bug #903959 which is already public.
1699655,2017-06-22 21:30:41 UTC,I believe that this crash is in libgps from gpsd.
1699655,2017-06-22 04:14:59 UTC,"StacktraceTop:
 gps_sock_read () from /tmp/apport_sandbox_Dwqnyn/usr/lib/x86_64-linux-gnu/libgps.so.22
 gps_read () from /tmp/apport_sandbox_Dwqnyn/usr/lib/x86_64-linux-gnu/libgps.so.22
 gpsmm::read() () from /tmp/apport_sandbox_Dwqnyn/usr/lib/x86_64-linux-gnu/libgps.so.22
 QGPSDDevice::onDataAvailable (this=0x56036adc5c60) at GPS/qgpsdevice.cpp:1006
 QGPSDDevice::run (this=0x56036adc5c60) at GPS/qgpsdevice.cpp:992"
1699660,2020-10-02 15:21:04 UTC,"Plain vanilla install of Kubuntu 20.04 and this still seems to be a problem.
Tried @peci1 solution, but didn't do anything. I still can't resolve names to IP-addresses."
1699660,2019-06-29 04:25:33 UTC,"Thanks Martin, your solution to disable systemd-resolve allowed me to finally resolve hosts on my local network again...  I was using a temporary workaround of replacing ""echo 'nameserver 192.168.1.1' > /etc/resolv.conf"", however that doesn't survive reboots."
1699660,2019-05-07 09:28:07 UTC,I successfully work around this issue by the steps described at https://askubuntu.com/a/907249/153828 :
1699660,2019-01-27 14:31:21 UTC,Try using this:
1699660,2018-12-25 01:02:57 UTC,"Hi,"
1699660,2018-06-02 01:10:35 UTC,"After testing further I get somewhat random results. Sometimes it fails and sometimes after running ""sudo service systemd-resolved restart"" I can resolve domains. Very weird."
1699660,2018-06-02 00:59:31 UTC,Just got bitten by this bug on 18.04 upgrade. This is the default config on LEDE/OpenWRT that gets broken by this upstream decision. Ubuntu should definitely ship a fix of some sort.
1699660,2018-05-10 09:18:46 UTC,"One more affected usecase - wired LAN connection is not working properly for VMWare Virtual Machine.
I use laptop with Win10 and run Ubuntu 18.04 as guest OS with VMWare.
Everything worked fine with Ubuntu 16 and 14, but with the current version the DNS resolution is now broken and I cannot run even ""sudo apt update"""
1699660,2018-12-25 01:20:54 UTC,IIRC what could be happening is that the additional timeout introduced by systemd-resolved first doing the newly implemented LLMNR lookup (which fails if not implemented by any device) causes some network tools to not even try doing a DNS lookup using the DHCP- or user-supplied DNS search domain suffixes.
1699660,2017-07-24 19:28:04 UTC,"There is a regression with dns handling between xenial and zesty. There are updates/improvements made in artful that will be published soon. It may not solve your issue, but maybe/hopefully it will improve things a lot."
1699660,2017-07-03 08:35:15 UTC,Same here. After upgrading somes pcs in my company from 16.04 to 17.10 : lots of local services are not working anymore.
1699660,2017-06-26 10:06:34 UTC,"Ok, i see what you mean now. I will test this locally to verify."
1699660,2017-06-22 10:04:25 UTC,you should be able to opt-into UseDomains by creating
1699660,2017-06-23 18:33:06 UTC,"No, that won't help either."
1699660,2017-06-23 12:02:03 UTC,"Sorry, typpo /etc/systemd/resolved.conf"
1699660,2017-06-23 12:01:35 UTC,You can adjust /etc/systemd/resolve.conf to add Domains= that you want to use for single domain resolution for non-DHCP specified DNS server.
1699660,2017-06-22 17:53:40 UTC,"According to the systemd documentation, UseDomains only affects systems that get their network setup from DHCP, which is not the case at my site.  Furthermore, it is documented as a way to add a DNS search domain, which would not help resolve hosts that have no domains."
1699660,2018-04-19 01:32:33 UTC,"This is still a problem in 18.04. Like the OP, I have localhosts on my LAN, but have no local domain configured. I had to disable systemd-resolved on each of my LXC containers. What's worse, resolvconf creates an empty /etc/resolv.conf file. So I had to create resolv.conf by hand and point to DNS. Again, on each of my containers."
1699670,2017-09-10 18:49:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699670,2017-09-10 18:50:57 UTC,"Same here: you have to remember which layout you were using before switching, and type your password in that layout… if that is possible."
1699670,2017-10-23 12:59:11 UTC,Gnome-screensaver shouldn't be running on GNOME Shell. It's 5 years old software and is needed only for old GNOME flashback (fallback) session.
1699670,2017-10-31 18:38:12 UTC,I hadn't mention that I've been using lightdm. After switching to GDM the issue was resolved.
1699670,2018-07-01 11:19:02 UTC,"Indeed, this issue only occurs to me when using lightdm. only then does gnome-screensaver kick in. otherwise, gdm3 handles both login and lock screen"
1699672,2017-11-29 16:38:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699672,2017-06-22 06:06:11 UTC,"And I have
systemd-logind[505]: Failed to abandon session scope: Connection timed out"
1699672,2017-06-22 05:54:46 UTC,"btw, solution mentioned here
https://github.com/systemd/systemd/issues/1961
to remove session dirs doesnt help"
1699673,2017-06-22 07:32:19 UTC,"you can use the vxlan to assign the cidr to physnet1
Do not have to change the code of daisycloud-core"
1699681,2017-06-22 06:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1699681,2017-06-23 19:18:46 UTC,"Looks like we need more fine grained version, but this works:"
1699681,2017-06-26 22:56:51 UTC,I've reassigned this bug to ejabberd since that package is what ships the profile in question:
1699684,2017-07-15 12:05:44 UTC,"If all instance are replaced, it would be cool to add a codecheck for it. Makes it easy to see the remaining cases while working on it, plus prevents new ones from being introduced in the future."
1699684,2019-09-16 17:58:20 UTC,Migrated to https://github.com/widelands/widelands/issues/1681
1699695,2017-10-18 09:00:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/512979"
1699699,2018-02-28 01:05:13 UTC,Ran into the same thing when an active-passive LB failed creation due to some issue with communication to the amphorae. I'm left with a LB that I apparently can't delete.
1699701,2017-06-22 08:44:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/476414"
1699706,2020-04-28 11:07:44 UTC,"Since I am not active anymore, I would like to remove myself from the assignee. Its open for anyone else to take up."
1699706,2020-06-16 19:52:39 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/488438
Reason: As we are going to deprecate master branch in this project this patch is not needed anymore."
1699706,2018-02-01 09:24:39 UTC,Could you please resolve the errors on patch and help in merging of code?
1699706,2018-02-01 04:52:08 UTC,"https://review.openstack.org/#/c/488438/
Is handling this issue."
1699706,2017-07-23 10:21:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/486377"
1699706,2018-02-01 04:17:49 UTC,"Reedip, are you still looking into issue?"
1699706,2017-08-17 03:08:39 UTC,"Change abandoned by Reedip (<email address hidden>) on branch: master
Review: https://review.openstack.org/486377"
1699706,2018-02-01 04:52:35 UTC,Fix proposed on https://review.openstack.org/#/c/488438
1699709,2020-10-22 19:50:31 UTC,closing since the package is removed from Ubuntu
1699726,2020-03-22 05:48:54 UTC,"Reviewed:  https://review.opendev.org/711789
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=601ced55757ee8081710ccb0553d8447263e7c7d
Submitter: Zuul
Branch:    master"
1699726,2020-04-03 20:18:52 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/717384"
1699726,2020-04-04 00:41:19 UTC,"Reviewed:  https://review.opendev.org/717384
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=3c0c0c536ccf043b90a70cdefa66b4275f39cab9
Submitter: Zuul
Branch:    feature/losf"
1699735,2018-08-24 19:47:08 UTC,If the fix is no longer needed shouldn't this ticket be closed?
1699735,2018-06-14 09:15:21 UTC,"Change abandoned by Bharat Kunwar (<email address hidden>) on branch: master
Review: https://review.openstack.org/558525
Reason: No longer needed"
1699735,2018-04-03 14:33:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558525"
1699739,2018-05-08 18:12:52 UTC,This change was made by a bot.
1699739,2019-10-03 10:38:05 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1699744,2017-06-22 10:05:34 UTC,"This isn't a bug in swift, sounds like it may be a bug/feature request for Horizon, if so please report for that project."
1699744,2017-06-23 10:34:49 UTC,"Which API or CLI command corresponds to this feature request?
I don't see ""swift list activated capabilities"" command.
Some more information might help someone who are interested in implementing this."
1699744,2017-06-26 13:29:51 UTC,Think command is `swift capabilities`. Seems a little bigger task but would love to work on this.
1699763,2020-01-29 10:21:26 UTC,"Using git-buildpackage, this bug can be worked around using the following flag:"
1699763,2018-08-04 14:44:15 UTC,Just ran into this myself. Bit of a pain if you want to test build & install in a ppa.
1699763,2019-10-19 18:46:12 UTC,"If you're using pbuilder then you can simply skip saving the .buildinfo with this command:
pdebuild -- --source-only-changes --debbuildopts --buildinfo-option=""-O"""
1699763,2018-06-02 02:05:28 UTC,Ok I worked around this by just removing the buildinfo from the file list in .changes/source.chanages.  Don't bother with any other trickery.
1699763,2018-03-25 10:10:35 UTC,"I am also running into this bug by building with --source-only-changes which is useful to locally build the binary to ensure it works, then upload a _source.changes, all in one command."
1699763,2018-06-02 01:31:36 UTC,Hit this as well. Preventing me from updating Antimicro for folks over at https://github.com/AntiMicro/antimicro/issues/192. Is there any workaround?
1699763,2018-07-09 20:40:04 UTC,"Yep, would be nice to fix this issue. Just ran into it."
1699767,2018-05-08 18:13:04 UTC,This change was made by a bot.
1699767,2021-01-07 04:10:24 UTC,4.8 EOL
1699768,2017-06-29 08:38:19 UTC,PR: https://github.com/snapcore/snapd/pull/3541
1699768,2017-08-18 08:17:01 UTC,I'm marking this as fix released since the PR linked above was merged and released as snapd 2.27.2 (or earlier).
1699768,2017-08-29 14:42:55 UTC,I have just tested on xenial and the fix never made it there:
1699768,2017-09-05 10:43:53 UTC,I run my tests again today (5th September 2017) and can confirm that everything works as expected on xenial now. Thank you!
1699768,2017-08-29 15:34:41 UTC,"please use ""snap version"" the version of the deb is meaningless and might not show what you are actually running (if the snapd inside the core snap is newer this one will be re-execed to)"
1699771,2017-06-22 13:19:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/476513"
1699771,2018-06-19 09:10:54 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/476513
Reason: This element doesn't seem to be used any more."
1699772,2018-01-12 12:50:13 UTC,*** Bug 114977 has been marked as a duplicate of this bug. ***
1699772,2018-01-10 10:15:56 UTC,*** Bug 114638 has been marked as a duplicate of this bug. ***
1699772,2018-01-10 10:13:13 UTC,*** Bug 114639 has been marked as a duplicate of this bug. ***
1699772,2017-10-29 20:19:49 UTC,*** Bug 113491 has been marked as a duplicate of this bug. ***
1699772,2018-01-07 20:13:46 UTC,*** Bug 114898 has been marked as a duplicate of this bug. ***
1699772,2017-12-25 16:52:05 UTC,*** Bug 114689 has been marked as a duplicate of this bug. ***
1699772,2017-11-17 18:55:53 UTC,*** Bug 113904 has been marked as a duplicate of this bug. ***
1699772,2017-07-05 21:35:37 UTC,"Libreoffice Base 5.1.6.2 is crashing on Ubuntu 16.04 LTS.
What I did:
0. Installed all updates, ""uname -a""
 Linux flash-1604 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:25 UTC 2017 i686 i686 i686 GNU/Linux
1. ""sudo apt-get install libreoffice-dbg ure-dbg uno-libs3-dbg libglib2.0-0-dbg""
3. run ""gdb --args /usr/lib/libreoffice/program/soffice.bin --base"", in Database Wizard selected 'Create a new database', 'Embedded database:' -> 'HSQLDB Embedded', click 'Next', click 'Finish', save database file in /tmp/db.odb.
   ""run""
   ""bt full""
    Got this backtrace: (see atachment)."
1699772,2017-09-23 16:23:01 UTC,The build time manifestation of this bug is a CppunitTest_dbaccess_hsqldb_test or CppunitTest_dbaccess_RowSetClones test failure. For details see:
1699772,2017-09-19 07:40:09 UTC,*** Bug 112479 has been marked as a duplicate of this bug. ***
1699772,2017-09-13 08:34:12 UTC,*** Bug 112357 has been marked as a duplicate of this bug. ***
1699772,2017-08-16 11:34:28 UTC,*** Bug 109014 has been marked as a duplicate of this bug. ***
1699772,2017-08-03 08:19:49 UTC,*** Bug 110748 has been marked as a duplicate of this bug. ***
1699772,2017-07-31 11:54:52 UTC,*** Bug 109101 has been marked as a duplicate of this bug. ***
1699772,2018-01-12 13:04:15 UTC,"Why then every other Java Programm not showing errors?
LibreOffice is the only one.
Thanks,"
1699772,2017-10-08 10:17:39 UTC,*** Bug 112930 has been marked as a duplicate of this bug. ***
1699772,2018-02-11 20:06:59 UTC,*** Bug 115631 has been marked as a duplicate of this bug. ***
1699772,2019-02-27 19:30:34 UTC,"(In reply to Dave Notman from comment #42)

> ""stack_guard_gap"" isn't a valid kernel parameter.
"
1699772,2018-07-18 21:39:21 UTC,*** Bug 118677 has been marked as a duplicate of this bug. ***
1699772,2020-02-06 13:08:20 UTC,openjdk 11 has since been backported to bionic.
1699772,2017-07-31 11:54:44 UTC,*** Bug 108854 has been marked as a duplicate of this bug. ***
1699772,2019-02-19 08:51:59 UTC,"Autopkgtests on cosmic started passing (as far as this bug is concerned − there were other unrelated failures) on 2018-10-10, when openjdk-lts was upgraded from 10.0.2+13-1ubuntu1 to 11~28-3ubuntu1."
1699772,2019-02-19 08:25:21 UTC,"As evidenced by http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/i386, the problem went away in cosmic at some point in November 2018."
1699772,2019-02-11 16:45:07 UTC,@ Seth Forshee (sforshee)
1699772,2018-12-15 19:17:57 UTC,xubuntu 18.04.1 32-bit (4.15.0-42-generic #45-Ubuntu)
1699772,2018-12-14 11:42:32 UTC,*** Bug 122062 has been marked as a duplicate of this bug. ***
1699772,2018-02-13 11:57:42 UTC,*** Bug 115222 has been marked as a duplicate of this bug. ***
1699772,2018-10-03 19:09:22 UTC,"I can reproduce using those steps, opened bug #1795956 from the crash report that was produced."
1699772,2018-09-28 19:03:59 UTC,"I've tried to reproduce the crash in a vm running up-to-date i386 cosmic, kernel version 4.18.0-7.8. I'm not seeing any crashes opening up the libreoffice apps. Can you give instructions on how to reproduce? Thanks."
1699772,2018-09-24 07:04:41 UTC,*** Bug 119614 has been marked as a duplicate of this bug. ***
1699772,2018-09-03 15:16:24 UTC,"Still crashing in cosmic on i386 with libreoffice 6.0.6 and kernel 4.17.0.9.12, and libreoffice 6.1.0 and kernel 4.18.0.7.8."
1699772,2018-08-27 08:17:52 UTC,*** Bug 119487 has been marked as a duplicate of this bug. ***
1699772,2018-08-27 08:16:57 UTC,*** Bug 119078 has been marked as a duplicate of this bug. ***
1699772,2018-08-23 18:22:38 UTC,"What's interesting, is that lowriter does not crash in 32-bit LinuxMint-Mate 19 (based on Ubuntu Bionic 18.04)
with either 4.15.0-20 initial kernel, or -33 updated from Bionic.
with 32-bit Lubuntu 18.04 it still crashes under -33 kernel, so the fix is clearly in some different place.
probably LinuxMint authors know some magic incantations"
1699772,2018-08-14 04:47:12 UTC,Is there any chance to have this fixed in Ubuntu 18.04 earlier than 20.04 is released ?
1699772,2018-09-28 20:32:03 UTC,"@Seth: I can reliably reproduce the crash in an up-to-date i386 cosmic VM. You need to install libreoffice-base (which is not installed by default, and pulls in all the java dependencies), then run it with ""libreoffice --base"", go through the initial wizard to create a new HSQLDB database, and that's when the crash happens."
1699772,2017-07-28 11:52:07 UTC,*** Bug 109327 has been marked as a duplicate of this bug. ***
1699772,2017-06-23 19:02:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699772,2017-07-24 02:49:50 UTC,There are 2 workarounds for this issue:
1699772,2017-06-24 16:27:10 UTC,Current state of the problem: Ubuntu kernel developers will prepare new patch in a few days (see https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2017-June/017507.html).
1699772,2017-06-24 09:43:08 UTC,"I confirm issue with full installation of Octave 3.8.1-1ubuntu1 on Trusty
(
dpkg -l | grep octave | grep ""^ii"" | awk '{print $2;}'
liboctave2:i386 octave octave-audio octave-benchmark octave-biosig octave-common octave-communications octave-communications-common octave-control octave-data-smoothing octave-dataframe
octave-doc octave-econometrics octave-epstk octave-financial octave-fpl octave-ga octave-gdf octave-general octave-geometry octave-gmt octave-gsl octave-htmldoc octave-image octave-info octave-io octave-lhapdf:i386 octave-linear-algebra octave-mapping octave-miscellaneous octave-missing-functions octave-mpi octave-nan octave-nlopt octave-nnet octave-nurbs octave-ocs octave-octcdf octave-octgpr octave-odepkg octave-openmpi-ext octave-optim octave-optiminterp octave-parallel octave-pfstools octave-plot octave-psychtoolbox-3 octave-quaternion octave-signal octave-sockets octave-specfun octave-splines octave-statistics octave-strings octave-struct octave-sundials octave-symbolic octave-tsa octave-vlfeat:i386 octave-vrml octave-zenity qtoctave
)
it crashes on 3.13.0-121-generic. strace says that segmentation fault is after loading openjdk and mmap something. Octave starts normally with 3.13.0-119-generic."
1699772,2017-06-23 23:29:13 UTC,"Applications that use jsvc can increase their thread stack space with -Xss1280k or larger (Red Hat, for example, suggested -Xss2m which is much larger)."
1699772,2017-06-23 23:20:48 UTC,"Interestingly, octave 4.2 comes up successfully under 4.40-81 under Ubuntu
16.04."
1699772,2017-06-23 22:31:56 UTC,Octave in Trusty is affected too (see bug 1699594).
1699772,2017-06-23 22:28:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699772,2017-06-23 19:05:46 UTC,"Also you can check comments on bug 1698919.
The (incomplete) list of affected applications include:
* LPCxpresso (see https://community.nxp.com/thread/453939 )
* RMongo (see https://stackoverflow.com/a/44699417 )
* Ubiquity UniFi (see
https://community.ubnt.com/t5/UniFi-Wireless/UniFi-Controller-failed-after-dist-upgrade/td-p/1967779
)"
1699772,2017-06-23 19:03:42 UTC,"Scilab is affected too. It uses openjdk-8.
See bug 1699892 for details.
Scilab is crashing with new kernel (linux-image-3.13.0-121-generic in Trusty / linux-image-4.4.0-81-generic in Xenial), but works with previous one (linux-image-3.13.0-119-generic in Trusty / linux-image-4.4.0-78-generic in Xenial)."
1699772,2017-06-23 12:29:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699772,2017-06-23 09:14:23 UTC,https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1700010
1699772,2017-07-25 14:52:56 UTC,pointers to the openjdk code / showing why only 32bit is affected
1699772,2017-06-23 06:53:32 UTC,"This is a ***MASSIVE REGRESSION*** affecting many or even all native applications that use the Java Invocation API, including at least Eclipse (crashes a few seconds after startup), and LibreOffice Base with any JDBC database connector (instant crash as soon as it tries to load the JVM)."
1699772,2017-06-22 12:48:18 UTC,This bug affects not only Oracle Java plugin but also those applications based on JNI Invocation API. Here is a very simple example to reproduce it.
1699772,2017-06-22 12:20:39 UTC,"The same bug appears on 17.04. 4.10.0-24-generic, which contains CVE-2017-1000364 fix, causes Oracle java plugin to crash. 4.10.0-22-generic, in exactly the same setup, works fine. The console error from Firefox (what most users will see) is"
1699772,2017-06-22 12:16:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699772,2017-06-24 16:44:41 UTC,Python-jpype is affected too - see https://stackoverflow.com/questions/44719488/segmentation-fault-when-starting-jvm-using-jpype .
1699772,2017-06-24 17:34:46 UTC,ImageJ is affected too (see http://forum.imagej.net/t/unable-to-start-imagej-on-ubuntu-16-04-2-fresh-install/5757/3 ).
1699772,2017-06-23 08:42:39 UTC,This should affect all embedded java uses which launch the JVM on the main thread (the regular java launcher does not do that) and is caused by the known buggy (http://www.openwall.com/lists/oss-security/2017/06/22/6) custom CVE-2017-1000364 fix. Testing the upstream patch on debian it seems to be fine (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865549).
1699772,2017-06-24 20:34:15 UTC,"Texas Instruments Code Composer Studio (http://www.ti.com/tool/ccstudio, Eclipse based) is affected too (see http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/604599/2226461#2226461 )."
1699772,2017-07-11 09:38:08 UTC,"Hi,
problem still present on linux-image-4.8.0-58-generic with these conditions:
    - while executing JVM launched from >>32-bit<< C (on 64-bit kernel)
    - defining ""higher"" JVM stack size (eg. -Xss2048k JVM argument)"
1699772,2017-07-10 12:25:49 UTC,"(In reply to Norbert X from comment #14)

> It seems that bug may be fixed soon in kernel (see
> https://lkml.org/lkml/2017/7/3/1008 ), not in LibreOffice.
> I'm sorry for the noise.
"
1699772,2017-07-07 20:27:01 UTC,"Libreoffice Base 5.3.1.2 is crashing on Ubuntu 17.04.
What I did:
0. Installed all updates, ""uname -a""
 Linux ubuntu-zesty 4.10.0-26-generic #30-Ubuntu SMP Tue Jun 27 09:29:33 UTC 2017 i686 i686 i686 GNU/Linux
1. ""apt-get install libreoffice-core-dbgsym libreoffice-writer-dbgsym ure-dbgsym uno-libs3-dbgsym libreoffice-gtk3-dbgsym libglib2.0-0-dbgsym""
3. run ""gdb --args /usr/lib/libreoffice/program/soffice.bin --base"", in Database Wizard selected 'Create a new database', 'Embedded database:' -> 'HSQLDB Embedded', click 'Next', click 'Finish', save database file in /tmp/db.odb.
   ""run""
   ""bt full""
    Got this backtrace: (see atachment)."
1699772,2017-07-05 20:09:57 UTC,"I can confirm that LibreOffice Base is crashing on Ubuntu 17.04 during database creation (launched Base, in 'Database Wizard' selected 'Create a new database', 'Embedded database:' -> 'HSQLDB Embedded', click 'Next', click 'Finish', save database file in /tmp/db.odb). After that Base is crashing silently.
I can't install libreoffice-dbg package on zesty (I reported bug 1702556 about it).
LibreOffice Writer does not crash in Zesty."
1699772,2017-07-04 21:42:24 UTC,Thanks!
1699772,2017-06-24 20:31:23 UTC,"Other Xenial kernels (linux-image-4.8.0-56-generic, linux-image-4.10.0-24-generic) are affected too."
1699772,2017-06-29 20:50:33 UTC,"Scilab and test C-Java program from bug 1700270 work normally with linux-image-4.4.0-83-generic, linux-image-4.8.0-58-generic, linux-image-4.10.0-26-generic.
Thank you!"
1699772,2017-06-29 14:17:06 UTC,"Upgrade to ""Linux ... 4.10.0-26-generic #30-Ubuntu SMP Tue Jun 27 09:30:12 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"" (Ubuntu 17.04 with XFCE under VMware WS Pro 12.5.7 build-5813279) fixed my problems with ""jsvc"" (starting ""tomcat"" 8.5.16) and kernel 4.10.0-24.28 ... catching ""signal 11"" immediately after start."
1699772,2017-06-29 21:04:03 UTC,"Thanks very much. I have installed it, and you're right."
1699772,2017-06-29 08:37:26 UTC,"4.4.0-83 fixes Eclipse, but LibreOffice Base still crashes with JDBC drivers."
1699772,2017-06-29 08:14:12 UTC,4.4.0-83.106 appears to be in the release repo's now and looks like it's fixed the issue for JSVC (commons-daemon (Ubuntu))
1699772,2017-06-29 00:19:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699772,2017-06-28 10:27:57 UTC,Rustc is affected too (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866185 ).
1699772,2017-06-27 21:16:28 UTC,With latest proposed kernel (4.4.0-83.106) Scilab does not crash.
1699772,2017-06-26 18:57:42 UTC,"Scilab is still crashing with kernel from xenial-proposed (4.4.0-82.105).
""JAVA_TOOL_OPTIONS=-Xss1280k scilab"" helps, but it is not a solution."
1699772,2017-06-24 20:58:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699772,2017-06-29 11:50:56 UTC,Kernel 4.10.0-26 (deb version 4.10.0-26.30) seems to have fixed crashes in Eclipse.
1699776,2019-09-15 15:52:17 UTC,Migrated to https://github.com/widelands/widelands/issues/1682
1699783,2019-02-08 12:41:12 UTC,"It prevents me from installing PHPMyAdmin, MySQL, and and MySQL Workbench on Kali-Linux...-_-'"
1699784,2020-07-04 11:39:56 UTC,Package: libpng12-0 1.2.50-2+deb8u3
1699794,2017-09-11 06:22:16 UTC,"On 11/09/17 07:13, Steve Langasek wrote:

> There doesn't appear to have been any progress on resolving this for
> close to three months.  I'm going to go ahead and remove the package
> from artful-proposed so that it's not showing up on proposed-migration
> as requiring action.  If a fix becomes available and the Kubuntu team
> wishes to reupload it, we can fast-track this through NEW again based on
> the past package history.
"
1699794,2017-06-24 21:09:35 UTC,Oooooh. Fails the same building against the old OpenCV. :/
1699794,2017-06-24 20:14:12 UTC,"On 24/06/17 20:23, Valorie Zimmerman wrote:

> Rik, I agree that seems the best idea. Perhaps ping the Simon devels and
> see if it can return soon, or will have to wait.
>
> There is active porting work going on, but I've not seen a mention of
> Simon.
"
1699794,2017-09-11 06:13:20 UTC,"There doesn't appear to have been any progress on resolving this for close to three months.  I'm going to go ahead and remove the package from artful-proposed so that it's not showing up on proposed-migration as requiring action.  If a fix becomes available and the Kubuntu team wishes to reupload it, we can fast-track this through NEW again based on the past package history."
1699794,2017-06-24 12:31:46 UTC,"Had a play with a few options, but still get a FTBFS."
1699794,2017-06-23 13:25:01 UTC,Log of the 0.4.90 beta failed build
1699794,2017-06-23 09:45:31 UTC,Failed builds of simon: https://launchpad.net/ubuntu/+source/simon/0.4.1-0ubuntu11
1699794,2017-06-24 19:23:52 UTC,"Rik, I agree that seems the best idea. Perhaps ping the Simon devels and see if it can return soon, or will have to wait."
1699800,2017-06-22 15:18:29 UTC,Confirmed on Ubuntu 16.10
1699800,2017-06-22 15:20:49 UTC,As workaround to take back control of banshee without reinstalling it
1699800,2017-06-22 15:21:32 UTC,"Basically, edit file"
1699800,2017-06-25 14:16:50 UTC,@Carlo L. Thanks for the workaround
1699824,2017-06-29 06:16:57 UTC,"Hi Michal,"
1699824,2020-11-09 17:59:27 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1699824,2020-11-10 14:30:08 UTC,"Still occurs with latest qemu built as of today.
 ✘  ~/qemu  qemu-system-sparc64 -cdrom ./tribblix-sparc-0m16.iso   -boot d -m 1024 -nographic -machine sun4v
qemu: fatal: Trap 0x0010 while trap level (6) >= MAXTL (6), Error state
pc: 0000000000000200  npc: 0000000000000204
%g0-3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
%g4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
%o0-3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
%o4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
%l0-3: 000000003ff00000 000001ff00000000 000001fff0080000 0000000000000000
%l4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
%i0-3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
%i4-7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
%f00:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
%f08:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
%f16:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
%f24:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
%f32:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
%f40:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
%f48:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
%f56:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
pstate: 00000014 ccr: 44 (icc: -Z-- xcc: -Z--) asi: 00 tl: 6 pil: 0 gl: 8
tbr: 0000000000000000 hpstate: 0000000000000004 htba: 0000000000000000
cansave: 6 canrestore: 0 otherwin: 0 wstate: 0 cleanwin: 6 cwp: 7
fsr: 0000000000000000 y: 0000000000000000 fprs: 0000000000000000"
1699833,2017-06-22 16:21:39 UTC,Sounds good to me
1699833,2019-09-19 12:03:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1699833,2019-09-20 12:16:44 UTC,MAAS 2.7 will have this both in the API and UI
1699833,2017-06-22 15:11:02 UTC,Since link_speed is not configurable by MAAS< this sounds like it could be a Interface Tag and not a property like MTU.
1699836,2020-05-05 07:02:26 UTC,"Reviewed:  https://review.opendev.org/724399
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=1f91b438d710547b9b8864c9d58695643f434c7e
Submitter: Zuul
Branch:    stable/queens"
1699836,2020-04-30 22:27:58 UTC,"Reviewed:  https://review.opendev.org/723658
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=f08c8be4370e3ec23edb5dd7b7a76325e94dc650
Submitter: Zuul
Branch:    stable/rocky"
1699836,2020-04-29 18:49:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/724399"
1699836,2020-04-27 19:05:46 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/723658"
1699836,2020-04-27 18:28:13 UTC,"Reviewed:  https://review.opendev.org/720206
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=30473c34810665dda1830d516951694ada09d198
Submitter: Zuul
Branch:    stable/stein"
1699836,2020-04-15 14:23:22 UTC,"Reviewed:  https://review.opendev.org/720091
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=18430ceafe2d5b46d496cf6ef33d5f1825cb82b8
Submitter: Zuul
Branch:    stable/train"
1699836,2020-04-14 22:20:41 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/720091"
1699836,2020-04-15 14:24:50 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/720206"
1699836,2020-04-06 02:04:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717646"
1699836,2020-04-05 23:33:39 UTC,"Change abandoned by Goutham Pacha Ravi (<email address hidden>) on branch: master
Review: https://review.opendev.org/717636
Reason: https://review.opendev.org/#/c/717516/"
1699836,2020-04-05 23:32:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717636"
1699836,2020-04-04 23:58:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717516"
1699836,2020-04-04 19:17:34 UTC,Re-opening this bug since I hit it through manila-ui.
1699836,2019-10-28 18:12:34 UTC,Yogesh I am going to close this if you are still seeing this issue can you let us know what version your testing and can you please add all relevant logs
1699836,2019-03-22 15:44:18 UTC,Hi Yogesh I was wondering if this is still occurring and second can you let me know what version of manila this is happening on?
1699836,2020-04-14 19:01:17 UTC,"Reviewed:  https://review.opendev.org/717516
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=470bab7c712b41fb22d2fd48ae6e43505525db31
Submitter: Zuul
Branch:    master"
1699841,2020-04-05 20:42:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717632"
1699842,2019-06-04 09:41:10 UTC,"It's not a full fix for this, but I proposed https://code.launchpad.net/~cjwatson/ols-jenkaas/log-approved-revision/+merge/368310 to at least log the approved revision, to make it slightly less utterly opaque what's going on."
1699842,2018-07-18 16:41:57 UTC,Set importance to high as when this happens code is dropped inadvertently.
1699844,2017-06-23 15:42:10 UTC,"I´ve tried in Ubuntu 12.04 and ubuntu 14.04.
The installation was made from the ppa."
1699844,2017-07-03 23:24:08 UTC,"Thank you, for testing."
1699844,2017-06-23 07:04:15 UTC,"Thanks for the bug report. I believe this issue has a fix in trunk, see
https://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2264
and
https://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2265"
1699844,2017-06-23 19:40:48 UTC,"You did probably install Onboard from our Stable PPA, which does not include the fix yet. Could you please try the Onboard version from our Snapshots PPA, which includes the fixes marmuta cited above?
https://launchpad.net/~onboard/+archive/ubuntu/snapshots"
1699844,2017-07-03 17:54:51 UTC,"Francesco is right, installing Onboard with the fix (and not from the stable PPA) works fine!"
1699845,2017-07-24 09:01:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699845,2017-07-27 16:19:13 UTC,Does the system boot if you select the prior kernel version from the GRUB menu?
1699845,2017-07-27 16:19:59 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 stable kernel[0].
1699845,2017-08-01 13:31:41 UTC,Hi Joseph
1699845,2017-08-12 14:01:05 UTC,I have just upgraded the system and installed kernel 4.10.17-041017-lowlatency.  I have just managed to boot with this new kernel.
1699845,2017-08-14 08:42:30 UTC,Update after only a day: again system not booting with new kernel 4.10.17-041017...  I'm back to booting with 4.10.0-21.
1699851,2019-10-27 10:20:01 UTC,"Sorry, *reporting :)"
1699851,2017-07-26 09:59:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699851,2019-10-27 10:16:08 UTC,Thanks for recording.
1699851,2017-07-26 09:59:33 UTC,+1
1699855,2019-09-19 12:03:57 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1699855,2019-09-20 12:19:38 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1699856,2020-05-16 02:00:18 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/728604"
1699856,2018-06-14 15:58:27 UTC,"The test passes with the generic driver only because the generic driver doesn't use security services. This is actually a design flaw in the generic driver, and thus a flaw in the design of the test."
1699856,2019-10-24 14:56:20 UTC,Any updates or milestones when this can be addressed?
1699856,2019-10-25 13:41:13 UTC,"Hi Jason, not yet. Will update it as soon as we have a milestone."
1699856,2020-07-13 20:17:39 UTC,"Reviewed:  https://review.opendev.org/728604
Committed: https://git.openstack.org/cgit/openstack/manila-tempest-plugin/commit/?id=1753a59b43448a77165103558d8d7a318b83f173
Submitter: Zuul
Branch:    master"
1699866,2017-07-07 19:49:02 UTC,Anything on this?
1699866,2019-03-28 10:36:22 UTC,Is it still a bug? If yes - please update.
1699866,2017-07-08 09:18:26 UTC,"Hi Ankit,"
1699866,2017-06-28 18:50:44 UTC,"Thanks Surya!
Appreciate your help in this regards."
1699866,2019-05-28 04:17:34 UTC,[Expired for kolla because there has been no activity for 60 days.]
1699866,2017-06-27 06:42:15 UTC,@Ankit Still looking into your 1st issue.
1699866,2017-06-26 21:24:43 UTC,"Hi There
I just did an upgrade on my linux on all the machines: controlnode, and two target nodes or compute nodes
and now I am not able to start the heka container.
the heka image exists and also was pulled by both the compute nodes(one of them is shown below)
The error is just"
1699866,2017-06-23 15:39:54 UTC,"thanks for your response Surya
Here are the details
docker version
Client:
 Version:      1.12.6
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   ac13b2b
 Built:        Wed Mar 22 02:52:47 2017
 OS/Arch:      linux/amd64"
1699866,2017-06-23 03:33:16 UTC,"@Ankit what version of docker and ansible using in current environment ?
At the first level I see two possibility one is whether ansible installed or not on controller node and second is version compatibility with docker."
1699866,2017-06-27 06:47:03 UTC,"but still It seems that there is some issue w.r.t Heka and upgrade, investigating the same."
1699867,2020-11-16 18:06:26 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1699867,2021-01-16 04:17:50 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1699868,2018-12-22 20:47:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699868,2019-10-12 17:22:07 UTC,The workaround:
1699871,2017-06-22 19:09:52 UTC,"Google Translate:
""Version 0.92.1, OS OS Windows 8, When I use the perspective, I'm hanging all the Inkscape"""
1699871,2017-06-23 12:59:17 UTC,"Hangs in Inkscape,but Inkscape doesn't use 100% CPU and uses the CPU stable."
1699874,2017-06-22 19:16:04 UTC,"In order to eliminate makedumpfile as the cause, I moved the makedumpfile binary out of the way so that kdump-tools would fallback to just copying all of /proc/vmcore. crash still reports an error, albeit a different one:"
1699874,2017-06-22 19:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1699878,2017-06-23 20:26:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699878,2017-06-28 03:47:08 UTC,"I know that there is another bug report on 4.4.0-81, and that there is a candidate kernel 4.4.0-83 that fixes other problems (octave and scilab not booting.) It would be prudent to see if nvidia-375 375.66-0ubuntu0.16.04.1 builds on the new candidate."
1699887,2017-08-07 18:34:56 UTC,Also seen with btrfs-progs:
1699887,2017-08-07 19:10:25 UTC,And util-linux:
1699887,2017-09-08 00:30:41 UTC,And perl:
1699888,2020-02-14 14:43:57 UTC,"Yeah, that would probably be helpful if you are relying on that to detect when the test fails. I actually thought it already did something like that, but maybe that's not in every condition. I'll take a look, thanks!"
1699888,2020-02-14 14:45:32 UTC,"Also, I'll try to remember to not respond to bugs that I think someone else wrote before drinking my coffee in the morning, so I don't talk to myself like a crazy person."
1699888,2021-01-11 14:38:08 UTC,This has been fixed in testflinger-agent to wait for the status before finishing up. I've also deployed it to all device agents we have deployed.
1699891,2017-06-23 05:25:19 UTC,"As per this link : https://github.com/openstack/python-novaclient/blob/9ca9ae6c1098e9c096aa7a400a8bfb153ef4d630/releasenotes/notes/pike-rm-deprecated-net-272aeb62b329a5bc.yaml
the novaclient.v2.security_group_rules has been deprecated and removed."
1699895,2017-06-23 19:43:04 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1699903,2017-06-22 22:44:47 UTC,"Hi Miroslav,"
1699903,2017-06-22 23:11:59 UTC,"Our actual templates are based on the lxc-sshd template example that comes with lxc-templates. There, basically all the lxc is is bind-mounts for necessary paths from the host, obviously read-only:"
1699903,2017-06-22 23:45:23 UTC,"On Thu, Jun 22, 2017 at 11:11:59PM -0000, Miroslav Los wrote:

> Our actual templates are based on the lxc-sshd template example that
> comes with lxc-templates. There, basically all the lxc is is bind-mounts
> for necessary paths from the host, obviously read-only:
"
1699904,2017-06-26 21:56:54 UTC,"Reviewed:  https://review.openstack.org/474599
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=158b91cf6b911e66b6de4c1e5de28ef22e802c30
Submitter: Jenkins
Branch:    master"
1699910,2019-05-25 04:45:38 UTC,This was fixed elsewhere.
1699913,2018-06-06 21:03:19 UTC,This bug was fixed in the package livecd-rootfs - 2.529
1699913,2018-06-06 18:39:16 UTC,"++ Absolutely agree that having ""apt-get install"" auto-update stale indexes would be ideal (or even a ""--update"" flag to install for combining them); looks like that discussion is over in bug 1709603. :)"
1699913,2018-06-06 18:23:45 UTC,"@Tianon,"
1699913,2018-06-05 13:07:34 UTC,"@mwhudson I'm concerned about https://bazaar.launchpad.net/~mwhudson/livecd-rootfs/lp-1699913/revision/1675 -- this leaves around the index files that aren't going to change, but I think this is going to cause subtle security issues for some users, isn't it?"
1699913,2018-04-19 11:33:24 UTC,Hi! It would be great if this change could be made for the Ubuntu 18.04 release.
1699913,2017-10-09 12:40:35 UTC,"in https://github.com/tianon/docker-brew-ubuntu-core/blob/8ff098f80b47a127e0ccfb8a1400bb40ab28e23a/update.sh#L90 there's a layer that removes /var/lib/apt/lists/* but having this on it's own layer is pointless because it will sill be in the previous layers, not only these files should not be in the tarball but also ""rm -rf /var/lib/apt/lists/*"" should be merged into the previous layer."
1699913,2017-07-25 17:13:00 UTC,Where do the build scripts for these images live? I can't seem to find the source.
1699919,2017-06-23 11:22:42 UTC,"On Fri, Jun 23, 2017 at 10:19:46AM -0000, PshemK wrote:

> The thing is - it didn't get remapped. Now I have two containers mapping
> to the same range, both live:
>
> pshemk@ii:~$ lxc list
> +---------+---------+---------------------+------+------------+-----------+
> |  NAME   |  STATE  |        IPV4         | IPV6 |    TYPE    | SNAPSHOTS |
> +---------+---------+---------------------+------+------------+-----------+
> | backend | RUNNING | 10.221.22.92 (eth0) |      | PERSISTENT | 0         |
> +---------+---------+---------------------+------+------------+-----------+
> | putils  | RUNNING | 10.221.22.91 (eth0) |      | PERSISTENT | 1         |
> +---------+---------+---------------------+------+------------+-----------+
>
> pshemk@ii:~$ lxc config show putils
> architecture: x86_64
> config:
>   volatile.base_image: 8fa08537ae51c880966626561987153e72d073cbe19dfe5abc062713d929254d
>   volatile.eth0.hwaddr: 00:16:3e:e3:20:21
>   volatile.idmap.base: ""0""
>   volatile.idmap.next: '[{""Isuid"":true,""Isgid"":false,""Hostid"":100000,""Nsid"":0,""Maprange"":65536},{""Isuid"":false,""Isgid"":true,""Hostid"":100000,""Nsid"":0,""Maprange"":65536}]'
>   volatile.last_state.idmap: '[{""Isuid"":true,""Isgid"":false,""Hostid"":100000,""Nsid"":0,""Maprange"":65536},{""Isuid"":false,""Isgid"":true,""Hostid"":100000,""Nsid"":0,""Maprange"":65536}]'
>   volatile.last_state.power: RUNNING
> devices:
>   root:
>     path: /
>     type: disk
> ephemeral: false
> profiles:
> - default
> stateful: false
> pshemk@ii:~$ lxc config show backend
> architecture: x86_64
> config:
>   volatile.base_image: 7a7ff654cbd8f5f09bec03aa19d8d7d92649127d18659036a963b1ea63f90d25
>   volatile.eth0.hwaddr: 00:16:3e:ec:03:84
>   volatile.idmap.base: ""0""
>   volatile.idmap.next: '[{""Isuid"":true,""Isgid"":false,""Hostid"":100000,""Nsid"":0,""Maprange"":65536},{""Isuid"":false,""Isgid"":true,""Hostid"":100000,""Nsid"":0,""Maprange"":65536}]'
>   volatile.last_state.idmap: '[{""Isuid"":true,""Isgid"":false,""Hostid"":100000,""Nsid"":0,""Maprange"":65536},{""Isuid"":false,""Isgid"":true,""Hostid"":100000,""Nsid"":0,""Maprange"":65536}]'
>   volatile.last_state.power: RUNNING
> devices:
>   root:
>     path: /
>     type: disk
> ephemeral: false
> profiles:
> - default
> stateful: false
>
> both have the same hostid, and get mapped to the same range.
>
> Should the files on the file system belong to the same uid:gid for 2
> different containers?
"
1699919,2017-06-23 10:19:46 UTC,"The thing is - it didn't get remapped. Now I have two containers mapping to the same range, both live:"
1699919,2017-06-23 08:54:50 UTC,"Hi, I'm not sure what the problem here is. LXD will copy the filesystem mapped and will remap on demand if there's another sub{g,u}id range allocated for LXD on the new host."
1699919,2017-06-23 18:19:05 UTC,See https://stgraber.org/2017/06/15/custom-user-mappings-in-lxd-containers/ for more details
1699925,2020-07-05 06:42:59 UTC,See PERL recommendations about deprecations: https://metacpan.org/pod/release/RJBS/perl-5.22.0/pod/perldelta.pod#A-literal-%22%7B%22-should-now-be-escaped-in-a-pattern
1699925,2020-07-05 05:06:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699927,2017-06-23 01:05:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/476736"
1699927,2017-08-22 11:39:01 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1699927,2017-08-12 06:17:30 UTC,"Reviewed:  https://review.openstack.org/477044
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2ea000061c571101ec604dd47425d7b32ee1e01b
Submitter: Jenkins
Branch:    stable/ocata"
1699927,2017-08-11 19:18:58 UTC,"Interesting. It seems we have some hacking rule against stuff like this, which seems to be ignored:"
1699927,2017-07-28 07:41:27 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1699927,2017-06-24 00:28:11 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/477044"
1699927,2017-06-23 19:44:11 UTC,"Reviewed:  https://review.openstack.org/476736
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a50d21662e121c50457f3154200845450e2af301
Submitter: Jenkins
Branch:    master"
1699933,2017-07-20 15:40:02 UTC,"FTR, Dann asked me about what I was looking for. I said I wanted testing of some representative sample of hardware in the wild. I'm open to suggestions on what that might mean, but I suggested testing against a couple of different manufacturers' BMCs, for example Dell and HP. Dann will ask the MAAS team if they can help with this."
1699933,2017-07-20 15:42:18 UTC,"> Dann
"
1699933,2017-07-20 16:23:36 UTC,"[ + Andres, for MAAS ]"
1699933,2017-07-20 17:17:59 UTC,With regards to comment #13 and testing that the update still works on non-arm64 systems - I don't see any indication of this testing happening for zesty.
1699933,2017-07-21 01:18:15 UTC,This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4~0.16.10
1699933,2017-06-28 03:35:14 UTC,http://lists.gnu.org/archive/html/freeipmi-devel/2017-06/msg00001.html
1699933,2017-07-20 06:15:48 UTC,"Same here. On x86 server, freeipmi-tools in -update and -proposed has the same output"
1699933,2017-07-21 09:09:22 UTC,On zesty ipmi-locate works well as expected. Actually in zesty and xenial are same source.
1699933,2017-07-27 20:28:58 UTC,This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4~0.16.04
1699933,2017-07-27 20:29:16 UTC,This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4~0.17.04
1699933,2017-07-21 01:18:21 UTC,"The verification of the Stable Release Update for freeipmi has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1699933,2017-07-19 16:44:42 UTC,"I verified this on an x86 server by testing that the output is the same before and after the update (see below). I also gave a heads-up to the MAAS team to consider adding this to their CI (see: https://bugs.launchpad.net/maas-images/+bug/1702976/comments/11), though I don't know if that occurred. @Andres: was your team able to run any tests with this?"
1699933,2017-07-11 03:09:21 UTC,"ubuntu@d05-4:~$ sudo ipmi-locate
[71285.659835] pgd = ffff801fbe0b3000
[71285.663245] [ffff93687c36] *pgd=0000001fd16f6003, *pud=0000001fbecab003, *pmd=0000001fbed7f003, *pte=0160000039860fc3
Bus error (core dumped)
ubuntu@d05-4:~$ dpkg --list | grep freeipmi-tools
ii  freeipmi-tools                      1.4.11-1.1ubuntu3                          arm64        GNU implementation of the IPMI protocol - tools
ubuntu@d05-4:~$"
1699933,2017-07-19 09:53:09 UTC,Thank you for your comprehensive verification report.
1699933,2017-06-29 09:32:00 UTC,This bug was fixed in the package freeipmi - 1.4.11-1.1ubuntu4
1699933,2017-07-11 03:03:23 UTC,"ubuntu@d05-4:~$ sudo ipmi-locate
[70950.778753] pgd = ffff8417cbcae000
[70950.782162] [ffff8b8f0c36] *pgd=00000417bf0e9003, *pud=00000417bf959003, *pmd=00000417bf5fa003, *pte=0160000039860fc3
Bus error (core dumped)
ubuntu@d05-4:~$ dpkg --list | grep freeipmi-tools
ii  freeipmi-tools                      1.4.11-1.1ubuntu3~0.16.10                  arm64        GNU implementation of the IPMI protocol - tools"
1699933,2017-07-11 02:26:01 UTC,"ubuntu@d05-4:~$ sudo ipmi-locate
[68526.721538] pgd = ffff801fcbfbb000
[68526.724948] [ffffa5ce0c36] *pgd=0000001fd272c003, *pud=0000001fc3da0003, *pmd=0000001fd2851003, *pte=0160000039860fc3
Bus error (core dumped)
ubuntu@d05-4:~$ dpkg --list | grep freeipmi-tools
ii  freeipmi-tools                      1.4.11-1.1ubuntu3~0.16.04                  arm64        GNU implementation of the IPMI protocol - tools"
1699933,2017-07-10 14:41:25 UTC,"Hello Ike, or anyone else affected,"
1699933,2017-07-10 14:38:56 UTC,"Hello Ike, or anyone else affected,"
1699933,2017-07-10 14:37:00 UTC,"Hello Ike, or anyone else affected,"
1699933,2017-07-19 09:54:35 UTC,And presumably this testing should take place on more than just arm64 as well?
1699933,2017-06-26 05:45:46 UTC,"Thanks Ike for the report, you also assigned yourself so I wanted to ask - are you going ahead and work on a fix that you'll report here?"
1699933,2017-06-26 08:37:28 UTC,"@paelzer,"
1699933,2017-06-27 14:39:52 UTC,http://lists.gnu.org/archive/html/freeipmi-devel/2017-06/msg00000.html
1699938,2017-06-23 02:51:50 UTC,"Is it possible for you to retry your testing on the master (Pike) branch?  It would be good to know if it was broken there, or if there is simply a backport to be made to stable/newton.  Thanks."
1699938,2017-06-23 07:51:40 UTC,"hi Brian Haley, thanks for your quikly respose, I checked the mysql logs,find the below error:"
1699938,2017-12-08 03:25:08 UTC,can you find the reason ?
1699945,2017-07-03 02:51:34 UTC,I have submitted the code to fix this bug.
1699945,2019-05-10 20:59:23 UTC,"Change abandoned by Adam Harwell (<email address hidden>) on branch: master
Review: https://review.opendev.org/476848
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1699950,2017-07-26 18:43:50 UTC,This issue was fixed in the openstack/puppet-openstacklib 11.2.0 release.
1699950,2017-06-23 15:09:54 UTC,https://review.openstack.org/#/c/476931/
1699956,2017-08-18 11:55:00 UTC,"Interesting, I will investigate making an Aline package for snapd available."
1699958,2017-10-12 17:00:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699959,2017-07-04 09:31:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699973,2017-06-23 16:47:19 UTC,Couple problems.
1699981,2017-06-23 16:54:35 UTC,"You're describing a client behavior -- the segments for a large object can be in any container within the same account; it's up to the client what naming conventions to use. That said, swiftclient is behaving as expected: whatever container you're uploading to (whether that's ""ContainerName"" or ""ContainerName_segments""), it will create the large object in <container> and default to putting the segments in <container>_segments (so, ""ContainerName_segments"" or ""ContainerName_segments_segments"", respectively). You can override this with the --segment-container option."
1699985,2017-06-23 07:13:58 UTC,Which version are you using?
1699985,2017-06-26 06:25:35 UTC,swift version is : python-swiftclient 3.3.0
1699986,2017-06-23 06:33:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1699987,2019-07-17 06:45:10 UTC,https://pastebin.ubuntu.com/p/Q64rNYbBGX/ Full result for the ARM64 test in this cycle.
1699987,2019-07-22 09:19:48 UTC,"Thanks for the fix Steve,
the ubuntu-qrt-apparmor is now marked as passed for Trusty ARM64."
1699987,2019-07-17 06:43:48 UTC,"Hi Steve,"
1699987,2019-07-19 19:16:40 UTC,"Ah, the old apparmor version tests were also missing the test fix for the getdents syscall not being supported on arm64, only getdents64. This has been fixed in https://git.launchpad.net/qa-regression-testing/commit/?id=8203725a3933bb3fa9f957a309b287d070bfbe9e ."
1699987,2019-05-21 05:34:03 UTC,"Hi Po-Hsu, I spent some time looking into this, and it looks like when the old apparmor tests got split out for trusty, one of the patches that needed to be applied to the regression test suite got dropped ('tests-convert_ptrace_getregset.patch'). I have committed a fix to qrt to re-apply this patch for the old apparmor source on trusty (it is already in the updated apparmor trusty source) in https://git.launchpad.net/qa-regression-testing/commit/?id=792e09115c319cf04839f0c4b2b7d43d018b5bcf ."
1699987,2017-06-27 04:11:22 UTC,"Hello,"
1699987,2018-09-12 18:24:29 UTC,"Sam, Tyler,  is this still something that needs to be chased down?"
1699987,2017-06-27 04:51:04 UTC,Thanks - It must be something specific to the arm64 environment that's a little off in regards to the header files that need to be included.
1699987,2018-09-13 05:11:41 UTC,"This issue is still valid.
http://10.246.72.4/test-results/3.13.0-158.208-generic/ms10-35-mcdivittB0-kernel__3.13.0-158.208__2018-08-28_04-11-00/ubuntu_qrt_apparmor/results/ubuntu_qrt_apparmor.test-apparmor.py/debug/ubuntu_qrt_apparmor.test-apparmor.py.DEBUG.html"
1699987,2017-06-26 22:24:50 UTC,The ptrace.c file contains both of these includes:
1699988,2017-06-23 07:14:55 UTC,Please give us more details about this bug - an example would be helpful to verify this.
1699988,2017-06-26 06:09:46 UTC,"Problem statement modified. It says that if we run ring-balance command and give input 0 for min_part_hour argument, It will run successfully. which is not a valid case."
1699990,2017-08-31 16:57:20 UTC,"    Please find below information about why some packages are not updated
after cluster update to 9.2MU ."
1699990,2017-10-25 06:33:43 UTC,Moving the bug to 9.2-Mu-4 since it's non trivial to solve.
1699999,2018-02-01 21:52:38 UTC,"When this happens, does the client retry that segment, or does it give up and fail the whole upload? If it's retrying, then I think there's nothing to be done here."
1700007,2017-06-23 07:25:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/476807"
1700007,2017-06-27 13:09:21 UTC,"Reviewed:  https://review.openstack.org/476807
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=acecdc2cf1506811f41c53860a3ff3c673370e9a
Submitter: Jenkins
Branch:    master"
1700007,2017-07-27 20:49:52 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.
1700011,2017-11-16 11:37:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700011,2017-11-16 11:55:37 UTC,It looks as though there is a failing attempt to upgrade some of the Mir libraries (probably Mir 0.24 to Mir 0.26) as IIRC the 16.04.2 shipped before that update in the archive.
1700021,2017-07-21 14:24:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700022,2017-09-16 23:23:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700022,2017-10-19 04:57:00 UTC,"Why would emcc from the current version of emscripten, 1.22.1-1build1, installed from the ubuntu synaptic package manager expect LLVM to be at 3.4 when the LLVM versions listed in synaptic are 3.7, 3.8, 3.9 & 4.0? I would presume that emcc would not give an error if I did things correctly. What is not right?"
1700034,2018-05-02 00:15:27 UTC,Horizon currently does not support multi-attach volume. It seems this is related to multi-attach volume.
1700034,2019-08-23 09:16:11 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678185"
1700034,2019-09-26 11:21:36 UTC,"Reviewed:  https://review.opendev.org/678185
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8051a2ca67edb4feda59103e38b1224ad4d959b2
Submitter: Zuul
Branch:    master"
1700034,2019-09-27 08:57:25 UTC,This issue was fixed in the openstack/horizon 16.0.0.0rc1 release candidate.
1700038,2017-11-21 19:32:58 UTC,Please provide more information.
1700048,2017-06-23 14:59:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/476937"
1700048,2018-02-18 23:43:25 UTC,"Change abandoned by Saad Zaher (<email address hidden>) on branch: master
Review: https://review.openstack.org/476937
Reason: Not valid anymore ..."
1700071,2017-07-31 17:56:14 UTC,"discussed and agreed to at Pike PTG, around L 54: https://etherpad.openstack.org/p/ironic-pike-ptg-ci-testing"
1700071,2017-07-31 17:56:44 UTC,"Discussed/mentioned at weekly ironic meeting on July 31, 2017. No one disagreed."
1700079,2017-06-26 14:47:57 UTC,Here's the info collected an machine that experienced the problem on June 23rd:
1700079,2017-06-26 14:17:08 UTC,We are having the accept same issue on several of our clients starting an 23th June at around 5 am and the numbers was ground till 6pm
1700079,2017-06-26 13:17:12 UTC,Reporter's dpkg.log:
1700079,2017-06-26 11:18:30 UTC,Could you please add /var/log/dpkg.log too? Thanks.
1700079,2017-06-26 05:51:45 UTC,"I'm not sure what upgrade log you are referrin to, this is the matching output from /var/log/apt/term.log:"
1700079,2017-06-24 14:32:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700079,2017-06-23 18:32:33 UTC,"Assigning to Marc initially; this doesn't look to me like a regression introduced in the SRU, but it will need investigation (and it would be nice to have it fixed)."
1700079,2017-06-25 20:48:28 UTC,Do you have an upgrade log from the same time period?
1700085,2018-10-18 23:37:58 UTC,"From what I see on Askubuntu may be related with
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1585332"
1700085,2018-10-03 09:22:43 UTC,"I encountered this issue in Ubuntu 18.10 beta, the cursor is very small in Snap apps."
1700085,2018-07-09 07:22:18 UTC,Also:
1700085,2018-07-09 07:07:11 UTC,"For people using Gnome Shell on Xorg, a possible fix just landed upstream:"
1700085,2018-06-07 16:38:16 UTC,Still an issue in 18.04
1700085,2017-10-04 12:24:27 UTC,"Here it stays tiny for a while after reboot/login, and eventually grows to a more normal size. I don't know what triggers the growth.
I have gnome-shell 3.26.0-0ubuntu2 on artful, same screen as Till's, and am using a 200% scale factor."
1700085,2017-08-14 02:17:44 UTC,I noticed in a Wayland session it's often only the X(Xwayland) apps that have the wrong cursor size. Sadly this includes the desktop area (nautilus-desktop is an X app).
1700085,2018-10-03 09:39:07 UTC,"zhiwei (chenzhiwei), same for me. The cursor is now as large as I set it by accessibility settings, but it is tiny in the snap version of LibreOffice."
1700085,2017-08-12 09:13:22 UTC,On Ubuntu 17.10 default (gnome) / nvidia 1050Ti - 384.59 / monitor 3840x2160:
1700085,2017-08-12 08:47:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700085,2017-06-28 01:31:46 UTC,"I found the opposite problem yesterday, which might be the same bug as this. When switching from a high scaling factor of 2 or 3 back to 1, the mouse cursor stayed big for longer than expected :)"
1700085,2017-06-27 16:53:51 UTC,The missing option to change the Cursor Size in gnome-control-center is LP: #841046
1700085,2017-06-27 16:51:17 UTC,"Unless you're in a hurry, I'd personally wait on backporting 3.26 changes to 17.10 ""Artful"" until we make the go/no-go decision on GNOME 3.26 in August."
1700085,2018-10-16 18:16:19 UTC,The cursor is tiny on my hidpi screen when using the snap version of inkscape. This is on Fedora 29/Wayland. It's the first snap I ever installed so i don't know whether it is reproducible with other snap apps.
1700085,2017-08-12 12:30:13 UTC,There is no way to adjust scaling in current Ubuntu Artful.
1700085,2017-06-27 16:49:20 UTC,#2: gnome-control-center master (future 3.26) has a Cursor Size setting in Settings>Universal Access so that issue is already fixed whenever we get the new version (probably at least in time for 18.04 LTS).
1700103,2017-11-02 22:04:11 UTC,"In addition, when editing a setting, the library list in the pop-up is also sorted incorrectly."
1700104,2018-12-12 10:45:11 UTC,Nice catch Martin!
1700104,2018-12-11 13:31:45 UTC,Reinstall doesn't help.
1700104,2018-12-11 12:25:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700104,2018-09-14 20:14:07 UTC,"According to https://serverfault.com/questions/715064/failed-to-issue-method-call-unit-failed-to-load-no-such-file-or-directory or https://bugzilla.redhat.com/show_bug.cgi?id=955379 the error message you have ""Failed to issue method call: No such file or directory"" comes from systemd."
1700104,2018-10-26 13:51:25 UTC,Ludovic:  I tried sudo apt install -- reinstall pcsd and got an internal error:  No file name for pcscd:amd64
1700104,2018-12-12 17:13:39 UTC,I have no problem with pcscd on Ubuntu 16.04 LTS:
1700104,2018-09-14 20:03:06 UTC,"Diego, Kurt, Do you also have the problem if you do:
sudo apt install --reinstall pcscd"
1700104,2018-09-14 14:54:05 UTC,I have this same problem as well - and have had this problem for a few months. Every time the update fails it takes me here.
1700104,2018-10-30 21:28:33 UTC,"The correct command should be:
sudo apt install --reinstall pcscd"
1700104,2020-10-07 21:25:29 UTC,Fixed in subsequent release. Closing.
1700120,2017-06-23 20:08:08 UTC,">> If it opens properly, it should import properly.
"
1700120,2017-06-23 19:48:04 UTC,"[What was the tool used to create this image ?] I'm not sure, it is a free CC0 license image downloaded from Pixabay.com."
1700120,2017-06-23 20:11:10 UTC,">> Is there a way to convert the file so it will import correctly?
"
1700120,2017-06-23 20:15:57 UTC,"alternatively, have you tried to copy and paste the entire image from one instance of Inkscape into another blank instance of Inkscape? I tried that and it appeared to work okay, apart from possible scaling changes."
1700120,2017-06-23 20:29:10 UTC,"> Given that these two operations were designed to operate quite differently, I doubt if it will be possible to fix this particular issue.
"
1700120,2017-06-23 19:25:22 UTC,What was the tool used to create this image ?
1700121,2017-06-26 16:37:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477605"
1700121,2017-07-07 03:11:20 UTC,"Reviewed:  https://review.openstack.org/477605
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=844ba6d4ba4f66629e621344d5b9d2fc03618bd7
Submitter: Jenkins
Branch:    master"
1700121,2017-07-27 20:49:53 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.
1700121,2019-04-08 09:52:11 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/481224
Reason: Very old"
1700121,2017-07-06 20:26:12 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/481224"
1700128,2017-06-26 01:47:12 UTC,Perhaps a duplicate of bug 1600205 ?
1700128,2017-11-03 16:43:10 UTC,Syncing task from Mir.
1700129,2017-06-23 17:07:20 UTC,"Review in progress for https://review.opencontrail.org/33132
Submitter: Hari Prasad Killi (<email address hidden>)"
1700129,2017-06-23 23:07:08 UTC,"Reviewed:  https://review.opencontrail.org/33132
Committed: http://github.com/Juniper/contrail-controller/commit/66803e43ca671293d21d36c4ff9472f1b284e9a2
Submitter: Zuul (<email address hidden>)
Branch:    R3.1"
1700135,2017-06-23 20:39:29 UTC,"Opera 12 is from the year 2011 and still has the old Presto eninge instead of Webkit inside. It's so old, _it might even be a security risk_... Since thenm there wer 33 major releases (number 13 was skipped, 14 was the first to use Webkit). After Webkit, Opera moved on to Blink (versiopn 15 and on)."
1700135,2017-07-01 06:44:11 UTC,Opera just released opera-stable_46.0.2597.32_amd64
1700135,2017-07-06 13:40:54 UTC,The opera package was deleted from the Ubuntu archive in 2008.
1700135,2017-07-06 19:59:45 UTC,"Obviously not. 12.16.1860-1linuxmint was what Synaptic offered to me, and I did not install any additional repository."
1700135,2017-07-06 20:07:20 UTC,"Hm, default package sources are:
deb http://packages.linuxmint.com rosa main upstream import"
1700135,2017-07-16 10:24:20 UTC,"Due to the version number, I would assume 12.16.1860-1linuxmint is packaged directly in Linux Mint. You can double-check this with `apt policy opera` which will list available versions and which repo they come from. I'm not familiar enough with Mint to know how to best contact package maintainers though :/"
1700138,2019-04-18 15:38:29 UTC,"According to gouthamr,"
1700138,2019-10-28 18:16:27 UTC,Lucio were you able to confirm the behavior and mark this Invalid?
1700138,2020-05-28 16:01:46 UTC,Additional comments  http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-05-28-15.00.log.html
1700138,2020-06-17 20:53:52 UTC,"Hi, I managed to reproduce the issue. I run the steps below:"
1700143,2020-04-14 15:17:23 UTC,@priteau has added some new instructions to an Etherpad which can serve as a useful guide until official docs are updated: https://etherpad.openstack.org/p/blazar-running-tempest
1700143,2017-07-27 14:44:26 UTC,I add the following to the tox.ini in my local environment (Tempest scenarios only):
1700151,2017-06-24 09:41:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700167,2019-01-09 17:33:26 UTC,This could be solved by https://bugs.launchpad.net/launchpad/+bug/1331914 I think?
1700167,2019-01-09 18:17:14 UTC,"They're related, but I'd rather consider that bug as a dependency of this one (that is, first add the capability, then later roll over everything still using 1024-bit keys in bulk)."
1700167,2019-08-23 03:37:22 UTC,Perhaps as an intermediate step deleting all PPAs for a user/team could be made to also delete their PPA key if it's shorter than what's currently being created for new PPAs?  Then at least a user/team could delete their PPA(s) and recreate them rather than having to create a new user or team to get a secure PPA key.
1700170,2017-07-20 19:15:45 UTC,"Verification-done for xenial, using shim-signed 1.32~16.04.1:"
1700170,2019-05-18 02:01:54 UTC,Package in yakkety-proposed removed from disk on 2018-01-23.
1700170,2017-08-28 15:29:46 UTC,This bug was fixed in the package shim-signed - 1.32~14.04.2
1700170,2017-07-28 00:47:07 UTC,This bug was fixed in the package shim-signed - 1.32~17.04.1
1700170,2017-07-28 00:46:48 UTC,"The verification of the Stable Release Update for shim-signed has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1700170,2017-07-28 00:46:31 UTC,This bug was fixed in the package shim-signed - 1.32~16.04.1
1700170,2017-07-24 17:01:35 UTC,"Verification-done for zesty, using shim-signed 1.32~17.04.1:"
1700170,2017-07-19 18:43:58 UTC,The verification for trusty was done against shim-signed 1.32~14.04.2.
1700170,2017-07-17 14:52:04 UTC,"Hello Mathieu, or anyone else affected,"
1700170,2017-07-18 04:56:24 UTC,"Hello Mathieu, or anyone else affected,"
1700170,2017-07-19 16:15:22 UTC,Trusty: verification-done
1700170,2017-07-13 21:14:19 UTC,"An upload of shim-signed to trusty-proposed has been rejected from the upload queue for the following reason: ""needs adjusted versioned dep on grub2-common; drop ref to LP: #1624096 from changelog""."
1700170,2017-07-13 21:03:19 UTC,"Hello Mathieu, or anyone else affected,"
1700170,2017-07-13 20:54:38 UTC,"Hello Mathieu, or anyone else affected,"
1700170,2017-06-23 19:41:06 UTC,Already fixed in Artful...
1700180,2019-09-19 14:53:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1700180,2020-01-24 09:13:45 UTC,"Just came across this issue when working with VMWare directly.
It was immediately pointed out that all dev/test activities are blocked due to the ssl error when connecting to the non-prod vsphere as most likely the ssl cert for that system is self-signed.
I suggest to introduce the option ""untrusted"" to the UI and the option to the API so that it's possible to connect to the untrusted endpoint and perform power operations."
1700180,2017-06-23 21:33:48 UTC,"Hi Dimitrii,"
1700190,2017-06-23 22:12:01 UTC,"To fix it, I used the following commands:"
1700190,2017-06-23 22:12:44 UTC,"sudo -H echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/splash
sudo update-initramfs -u"
1700203,2017-06-24 02:58:17 UTC,"Something funny is going on, your lsb-release package looks broken:"
1700203,2017-06-24 12:30:46 UTC,"I know!  I run an app that was made for python2 on a different distro. I
drag/drop the files on top of this distro that had python 3.  I have to
admit I'm just learning about the file system. The app seem to work 95%
with the old version py. But not with the py3."
1700205,2018-05-08 18:13:19 UTC,This change was made by a bot.
1700205,2021-01-07 04:10:18 UTC,4.8 EOL
1700206,2017-06-24 04:30:06 UTC,This change was made by a bot.
1700207,2017-06-24 04:30:32 UTC,This change was made by a bot.
1700208,2017-11-03 05:51:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700210,2018-05-08 18:13:33 UTC,This change was made by a bot.
1700210,2021-01-07 04:10:11 UTC,4.8 EOL
1700211,2017-06-27 18:45:53 UTC,E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.
1700211,2017-08-01 01:26:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700225,2017-07-15 14:55:41 UTC,"Yes, but it will take a few weeks since I am vacationing abroad. I'll try
it when I get back and let you know how it went."
1700225,2018-04-16 11:54:38 UTC,"Sorry this took so long, but I can confirm that the bug does not reproduce on kernel 4.10.17-041017-generic that you linked to, or on 4.13.0-37-generic from 17.10. Interestingly, kernel 4.10.17 is 3-4x slower at writing to the NVM device than 4.13.0-37, with the former I get 260-290 MB/s, with the latter I get about 1 GB/s."
1700225,2017-07-11 14:29:09 UTC,"Can you also give the latest upstream 4.10 kernel a test?  It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/"
1700225,2017-07-05 13:21:10 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1700225,2017-06-24 09:27:21 UTC,"Ran apport. Note that while during that apport run the kernel was marked as tainted because of the proprietary NVIDIA driver, the bug also replicates without that driver loaded in an untainted kernel. The dmesg logs I posted earlier are of that state."
1700225,2017-06-24 09:23:14 UTC,apport information
1700225,2017-06-24 09:23:12 UTC,apport information
1700225,2017-06-24 09:23:10 UTC,apport information
1700225,2017-06-24 09:23:08 UTC,apport information
1700225,2017-06-24 09:23:07 UTC,apport information
1700225,2017-06-24 09:23:05 UTC,apport information
1700225,2017-07-05 18:18:11 UTC,"The issue did not start happening after an update - I just got this NVM device, and kernel 4.10.0-24.28-generic was the latest one at the time."
1700225,2017-06-24 09:23:01 UTC,apport information
1700225,2017-06-24 09:23:00 UTC,apport information
1700225,2017-06-24 09:22:58 UTC,apport information
1700225,2017-06-24 09:22:57 UTC,apport information
1700225,2017-06-24 09:22:55 UTC,apport information
1700225,2017-06-24 09:22:54 UTC,apport information
1700225,2017-06-24 09:22:53 UTC,apport information
1700225,2017-06-24 09:23:04 UTC,apport information
1700225,2017-06-24 09:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1700225,2017-06-24 08:41:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1700226,2017-06-24 10:09:16 UTC,"Confirmed, with latest master"
1700226,2017-06-24 09:47:10 UTC,"Sorry, forgot to add these other problems I'm having."
1700226,2017-06-24 10:03:11 UTC,"Thanks for reporting the other issues too. In the future, please open a bug for each issue.
This makes it easier for contributor to fix specific bugs, as well as tracking the process."
1700252,2017-06-29 14:19:53 UTC,It looks like aptdaemon is incorrectly asking to install the same packages multiple times.
1700256,2017-06-26 20:25:22 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1700256,2018-02-27 01:47:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700272,2017-06-24 16:38:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1700272,2017-06-25 14:09:45 UTC,Confirmed also in Ubuntu 17.04 with libc-bin 2.24-9ubuntu2
1700272,2017-06-25 14:10:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700275,2017-07-03 19:34:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700283,2017-06-26 08:17:04 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1700283,2017-06-26 16:26:03 UTC,Done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866015
1700283,2018-05-25 18:24:33 UTC,"As indicated in the Debian bug, elinks is missing the server name indication (SNI) extension. A debian bug about that specifically is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797968."
1700283,2018-05-25 18:31:29 UTC,"#797968 is more specific, as this bug is about the lack of the SNI extension."
1700283,2018-05-25 19:34:21 UTC,"I have successfully cloned http://elinks.cz/elinks.git, built ELinks binary against OpenSSL and successfully opened https://metrocom-chat.ml with this binary. So I guess patch is applied or building against OpenSSL instead of GnuTLS did the trick."
1700283,2019-06-21 04:12:55 UTC,Any chances the fixed version will make it to Ubuntu 16.04?
1700286,2017-06-27 21:54:28 UTC,same here
1700290,2017-06-24 20:18:08 UTC,"StacktraceTop:
 pcap_next (p=0x0, h=h@entry=0xbf829198) at ./pcap.c:243
 next_packet (header=header@entry=0xbf829198) at 80211.c:42
 is_wps_locked () at 80211.c:190
 crack () at cracker.c:141
 main (argc=5, argv=0xbf829fe4) at wpscrack.c:103"
1700290,2017-06-26 22:34:24 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1700291,2017-06-24 23:30:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700292,2017-06-24 20:27:33 UTC,"I am sorry, there is a typo (a semicolon where should be none) in the for loop of the workaround. The correct command should be:"
1700297,2018-01-20 16:23:17 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1700306,2017-06-26 22:45:37 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1700306,2017-10-19 02:40:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700310,2019-01-30 19:12:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700311,2017-07-04 17:25:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700319,2017-06-25 04:37:15 UTC,"The attachment ""Patch from https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1700319,2017-06-25 06:55:51 UTC,Confirmed upstream and patch proposed
1700319,2017-10-03 01:54:14 UTC,"I installed this patch on 3.22.10, it did not solve the problem of no menu entries listed when menu headings chosen in virt-manager.  I also tried the latest upstream version, 3.22.21, which still has the same problem via x11 and no other time."
1700319,2017-10-30 04:12:49 UTC,fixed for Ubuntu 18.04 LTS with gtk+ 3.22.25. I'm proposing updating Ubuntu 17.10 to gtk+ 3.22.25 in LP: #1728421
1700319,2017-10-03 01:55:24 UTC,Just to be clear:  This is a regression.  It worked in 3.16.
1700327,2017-09-29 15:41:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700330,2017-11-10 00:32:56 UTC,"This is a false positive, in most of 0.3.5, virtio_blk & virtio_net are built into the kernel. In other kernels, they may be modular."
1700341,2017-07-01 16:09:05 UTC,Thanks for reporting.
1700351,2017-11-05 11:15:13 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/476511
Reason: This review is > 3 months without comment and currently blocked by a core reviewer with a -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -1 on this review to ensure you address their concerns."
1700351,2017-06-25 11:27:11 UTC,"I suspect this was added by patch https://review.openstack.org/#/c/475646 , which updates the port's revision number."
1700357,2017-06-26 18:33:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700357,2021-01-07 04:10:00 UTC,4.8 EOL
1700357,2017-06-25 19:41:28 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1700374,2017-06-25 16:54:38 UTC,"This problem affected both my desktop and laptop, both Mint 18 at the time.  All of the re-installs I did on desktop, my laptop still had the problem.  I just ran -"
1700374,2017-06-25 22:37:37 UTC,More detailed investigation -
1700382,2017-09-26 21:06:16 UTC,"Also, well network.target is pulled in by a lot of stuff, and ifup is just slow unless you specify allow-hotplug for your interfaces; unrelated to network-online.target or lxd."
1700382,2017-09-26 21:05:12 UTC,"What does a finished boot mean for you? It should indeed not affect time to login, but the boot time reported by systemd-analyze will always be longer even if network-online and lxd stuff is the only thing not started yet (as it considers the boot complete when all services are running)."
1700394,2017-06-26 21:05:39 UTC,"here is a fix i came up with
ever since i did these changes , the problems went away"
1700402,2017-06-27 11:30:15 UTC,this is an example
1700402,2018-05-01 04:29:26 UTC,It does not react to change in com.canonical.indicator.datetime.
1700402,2018-05-01 20:31:39 UTC,"I disabled ""show date"" and ""show day"" from settings, then in dconf-editor I set custom-time-format (under com.canonical.indicator.datetime) to '%a %d %B %H:%M' and time-format to 'custom'. Problem solved."
1700402,2018-05-01 04:27:18 UTC,"So do Italian dates, Ubuntu Unity 18.04."
1700402,2018-05-01 04:25:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700407,2017-06-29 11:36:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700413,2017-08-02 13:54:16 UTC,Could you check latest upstream version? [1]
1700416,2017-06-25 22:01:23 UTC,"For details, see /tmp/apparmor-bugreport-iwq9ml40.txt"
1700416,2017-06-27 20:59:58 UTC,Thanks for the bugreport!
1700418,2017-06-25 22:23:00 UTC,"It's very strange, but after manual installation of packages from Debian Wheezy
(
libavcodec53_0.8.20-0+deb7u1_amd64.deb
libavutil51_0.8.20-0+deb7u1_amd64.deb
libdirac-encoder0_1.0.2-6_amd64.deb
libopenjpeg2_1.3+dfsg-4.8_amd64.deb
libvpx1_1.1.0-1_amd64.deb
libx264-123_0.123.2189+git35cf912-1_amd64.deb
)
my RDP plugin is working."
1700418,2017-06-26 12:27:32 UTC,Here is ldd after installation of packages above
1700419,2017-11-28 12:01:27 UTC,Just to confirm (sorry that I didn't do this earlier): Caffeine 2.9.4 continues to work for me on my fully-updated Ubuntu GNOME 16.04 systems.
1700419,2017-11-28 04:17:21 UTC,[Expired for caffeine (Ubuntu) because there has been no activity for 60 days.]
1700419,2017-06-26 07:59:04 UTC,Thanks for investigating this.
1700419,2018-08-10 18:09:20 UTC,I'm getting the same protocol error on Debian
1700419,2020-08-31 16:08:27 UTC,Closing as out of date.
1700419,2020-09-12 21:57:18 UTC,"Reopening, as I have finally managed to reproduce this bug. It occurs for me when the title of a full screen window (the window for which Caffeine inhibits idleness) contains a non-ASCII character. This causes an error in the embedded Perl script in xdg-screensaver, in the subroutine screensaver_gnome_screensaver, where it tries to get the window name (the call to GetProperty). This in turn appears to be a bug in the Perl module X11::Protocol."
1700419,2020-09-12 21:59:45 UTC,Here is the upstream xdg-utils bug: https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/137
1700419,2020-09-12 22:05:40 UTC,"Unfortunately, the upstream bug I mentioned in #7 is for a related bug, not this one, and the patch for it has already been applied."
1700419,2020-09-12 22:10:36 UTC,"The patch for this bug: https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/98 does fix the problem, though I am not sure that the problem here is that the window has no title, rather that no title is reported by X11::Protocol. However, for our purposes that's good enough!"
1700419,2020-09-12 22:11:24 UTC,"Ah embarrassingly, I find that this xdg-utils bug was filed by me, and the patch was also provided by me!"
1700428,2020-04-02 01:40:46 UTC,"Reviewed:  https://review.opendev.org/716562
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a90654ae5a8f4cc8588f0f595af091f8cd986441
Submitter: Zuul
Branch:    master"
1700428,2020-04-01 16:30:06 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/716085
Reason: reverted in master"
1700428,2020-04-03 17:11:03 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717350"
1700428,2020-04-01 16:29:56 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/716070
Reason: reverted in master"
1700428,2020-04-01 16:29:31 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/716086
Reason: reverted in master"
1700428,2020-04-01 12:07:52 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/716562"
1700428,2020-03-30 21:34:44 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/716086"
1700428,2020-03-30 21:34:18 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/716085"
1700428,2020-03-30 20:04:18 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/716070"
1700428,2020-09-25 15:42:40 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1700428,2020-03-30 19:21:33 UTC,"Reviewed:  https://review.opendev.org/477286
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8ebc635a18fd23fd6595551a703961a4d4392948
Submitter: Zuul
Branch:    master"
1700428,2018-08-31 07:46:31 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/477286
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1700428,2020-04-01 16:30:15 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/train
Review: https://review.opendev.org/716061
Reason: reverted in master"
1700428,2018-08-31 07:46:21 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1700428,2017-06-28 05:38:41 UTC,"I think we may want to reconsider note [1], as setting the device ID should suffice to stop nova or neutron from 'stealing' the port if in use. That said, we need the compare and swap logic merged in tree to avoid introducing races while the device ID gets updated. This means that the precommit listener could be avoided."
1700428,2017-06-27 08:12:23 UTC,"Thanks for return. As the test env had been destroyed. I maybe miss some thing.
The repro steps are:
parent port case:
1. create 2 networks, named net1 and net2.Create subnet1 and subnet2.
2. create ""parent"" port from net1 and ""subport"" port from net2.
3. Then create trunk resource ""trunk"" with ""parent"" as parent port and ""subport"" as subport.
4. create a router Router. And set ""parent"" as subnet1 interface to Router.
5. can not remove ""parent"" port from Router, server raise the ""parent"" had been associated with a trunk ""trunk"".
6. can not delete ""trunk"", and no api to update the parent port."
1700428,2017-06-27 06:34:56 UTC,"Can you provide the steps to repro the issue you're facing? We left this area somewhat undefined for fear of limiting acceptable use cases, and/or potentially reducing throughput of port update operations."
1700428,2017-06-26 02:06:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477286"
1700428,2020-03-30 19:24:08 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/716061"
1700428,2020-09-25 15:43:15 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/717350
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1700444,2017-06-26 04:53:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477365"
1700462,2018-10-23 09:29:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700463,2017-06-26 19:42:05 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1700472,2017-12-07 13:24:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700473,2017-09-13 11:38:02 UTC,Needed for Kuryr use case
1700473,2017-09-13 13:37:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/503682"
1700473,2020-06-23 17:24:51 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/503682"
1700476,2017-11-03 16:37:00 UTC,Syncing task from Mir.
1700477,2017-07-02 15:31:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700480,2017-06-26 09:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1700480,2017-07-25 15:43:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1700480,2017-08-02 13:00:52 UTC,Snap build working as expected with the xenial kernel on -proposed.
1700480,2017-08-03 16:32:17 UTC,This bug was fixed in the package linux - 4.4.0-89.112
1700487,2017-07-26 05:15:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/487278"
1700487,2017-07-25 09:26:27 UTC,"Reviewed:  https://review.openstack.org/486778
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=b3913d9709dd4b824d7b4578f15f296f9e1968b8
Submitter: Jenkins
Branch:    master"
1700487,2017-07-28 20:17:26 UTC,This issue was fixed in the openstack/networking-midonet 5.0.0.0b3 development milestone.
1700487,2017-06-26 09:55:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/477473"
1700487,2017-07-31 09:12:56 UTC,"Reviewed:  https://review.openstack.org/487278
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=e8bf1152daf3d86d506995fb8360d27095fe9519
Submitter: Jenkins
Branch:    master"
1700498,2017-06-26 11:03:47 UTC,"Hi Stuart,"
1700499,2017-06-29 10:19:57 UTC,Thank you for the report.
1700499,2018-01-25 09:25:56 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3712
1700500,2018-03-04 19:14:05 UTC,"/etc/systemmd/resolved.conf
DNS=10.0.3.1
Domains=lxc"
1700500,2018-03-04 20:49:20 UTC,(Sorry if I misunderstand your answer)
1700501,2017-06-27 16:45:42 UTC,"In a private E-mail reply, Benjamin agreed with the suggestion to proceed with this report in public for now. As such, I'm triaging it as class B2 (""a vulnerability without a complete fix yet, security note for all versions, e.g., poor architecture / design""). The security note normally suggested by B2 is probably not warranted either given the existing treatment in the security guide, linked from the initial report."
1700501,2017-06-28 12:43:21 UTC,"Well, there is proposed code is up to start moving to privsep, but it's not
a priority right now..."
1700501,2017-06-27 13:48:13 UTC,"At a minimum, I think we can continue this in public because it's a known issue. The rootwrap base implementation was an okay idea in theory, but in practice many projects shipped terrible default configurations which bypassed any actual security afforded by the framework. As a result, rootwrap is itself on the path to deprecation with https://docs.openstack.org/developer/oslo.privsep/ as its eventual successor."
1700501,2020-05-06 15:53:50 UTC,"In Manila, we've discussed migrating off of rootwrap, to privsep - and are yet to find an owner to complete that work. We'll hopefully do that soon. However, I agree this bug is wide open. We'll use a different tracker to call out the tasks to deprecate the usage of rootwrap."
1700501,2017-06-28 10:33:04 UTC,"This is too vague to be actionable. There is one example, and it's not clear where in the system the concern is. And the kinds of changes to make this be as restricted as one would like really don't lead well to a bug, but would require a more systematic push to really embrace something like privsep."
1700501,2017-06-26 11:00:00 UTC,"Assuming this only affect localhost user and that rootwrap argument can not be set arbitrarily by remote user, I guess this is at best a class B2 or perhaps C1 according to VMT's taxonomy: https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1700501,2017-06-26 10:49:52 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1700507,2017-06-26 11:21:34 UTC,The account in question is a jabber account.
1700509,2017-06-27 11:47:40 UTC,"I have the same here, rollback to 5.6.35 resolves an issue."
1700509,2018-01-25 09:12:40 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1101
1700510,2017-09-04 10:27:15 UTC,Is Raspbian taking this seriously? It looks like some packets have not been compiled for the right platforms (not working on RPi1 by the looks). Is the RPi1 now considered unsupported?
1700510,2017-09-04 21:20:28 UTC,Reported to Raspberry pi at https://github.com/RPi-Distro/repo/issues/83
1700510,2017-07-14 08:17:59 UTC,I could trigger it with any plotting either in python or in octave
1700510,2017-07-12 09:48:36 UTC,That confirms my suspicion that the responsible package came from the raspberry pi foundation's repo.
1700510,2017-07-09 20:33:18 UTC,"Below is what I get. Am I correct to suspect something going on with processor versions? Will the RPi1 stop being supported soon? Or can I safely upgrade an RPi1 setup to stretch?
Best regards,
Max"
1700510,2017-07-09 10:05:53 UTC,I suspect that the raspberry pi foundation are responsible for this.
1700514,2017-06-26 15:35:35 UTC,It turned the camera was facing me. It was the front camera and i was thinking its the rear. Can we please have a a setting for which camera to use as default.
1700515,2017-08-01 04:46:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700516,2017-06-26 11:55:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/477502"
1700516,2017-08-10 09:03:25 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/492439"
1700516,2017-08-10 09:04:36 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/492440"
1700516,2017-08-10 09:04:55 UTC,"Change abandoned by James Page (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/492439"
1700516,2017-11-13 09:14:14 UTC,"Change abandoned by James Page (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/492440"
1700516,2019-08-09 15:25:37 UTC,"Change abandoned by Alex Kavanagh (tinwood) (<email address hidden>) on branch: master
Review: https://review.opendev.org/633270
Reason: The nova-lxd project is now archived."
1700516,2020-07-23 06:21:41 UTC,Project is no longer maintained.
1700516,2017-06-26 13:58:00 UTC,"Reviewed:  https://review.openstack.org/477502
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=f8daa3b38bb9953e216c8ddd4f9625d24bc7bf1e
Submitter: Jenkins
Branch:    master"
1700520,2017-06-26 13:32:09 UTC,Additional bug :
1700526,2017-06-29 19:39:00 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1700526,2017-06-26 19:40:48 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1700557,2017-06-26 14:18:39 UTC,diff between 20170620 (pass) and 20170620 (fail)
1700557,2017-06-27 07:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1700557,2017-06-26 15:09:20 UTC,Boot logs from a VM that hangs on boot.
1700557,2017-07-03 13:05:14 UTC,apport information
1700557,2017-07-03 13:05:19 UTC,apport information
1700557,2017-07-03 13:05:21 UTC,apport information
1700557,2017-07-03 13:05:23 UTC,apport information
1700557,2017-07-03 13:05:24 UTC,apport information
1700557,2017-07-03 13:05:26 UTC,apport information
1700557,2017-07-03 13:05:28 UTC,apport information
1700557,2017-07-03 13:05:30 UTC,apport information
1700557,2017-07-03 13:05:32 UTC,apport information
1700557,2017-07-03 13:05:34 UTC,apport information
1700557,2017-06-27 08:49:07 UTC,And the same happens in the lab. After installation the VM hangs until it receives an input event. Same gap in the logs
1700557,2017-07-03 13:05:17 UTC,apport information
1700559,2017-06-28 10:20:12 UTC,"Respin, no need to run certification-testing."
1700559,2017-06-28 12:46:48 UTC,"        tests ran:   1, failed: 0;
  http://kernel.ubuntu.com/testing/3.13.0-123.172~precise1-generic/fozzie__3.13.0-123.172~precise1__2017-06-28_12-44-00/results-index.html"
1700559,2017-06-28 19:31:09 UTC,The package has been published and the bug is being set to Fix Released
1700563,2017-06-28 21:01:43 UTC,The package has been published and the bug is being set to Fix Released
1700563,2017-06-28 10:19:58 UTC,"Respin, no need to run certification-testing."
1700569,2017-06-26 14:07:54 UTC,"Yeah that's expected. When you depend on something not created, we ignore the error (since recently), but we don't go up the dep chain. You need to add the dependency explicitly yourself."
1700569,2017-06-26 14:21:47 UTC,"hi Thomas, thanks again. We were indeed discussing with Steven on IRC if this is (or not) the intended behavior!"
1700569,2017-06-29 17:46:59 UTC,"This is really inconvenient for template authors though - I wonder if we should consider changing how conditionally defined resources work - what if we forced their type to OS::Heat::None when the condition is false, then the chain of dependencies and other weird corner cases related to skipping the node in the graph could be avoided?"
1700569,2017-06-29 20:02:38 UTC,"It would somewhat change the expected behaviour. We could change the pike behavior, as the condition parsing is template specific. We may need to check the impact, though."
1700579,2017-06-26 14:40:57 UTC,The reason this function does not work in the murano dashboard is because the dashboard is using legacy mode for yaql.  Legacy mode enables yaql 0.2 as well as yaql 1.0.  This range function was broken in yaql 0.2 and explains the behavior reported in this bug.
1700582,2017-06-28 09:40:45 UTC,good to hear. merged with trunk in rev:
1700582,2017-06-27 11:16:54 UTC,"attached is a modified version of the file dxf_input.py, which fixes the bug.
in order to apply this fix you will need to copy this file into the location Inkscape\share\extensions\. You may wish to make a backup copy of your current file first, just in case."
1700582,2017-06-27 12:53:03 UTC,Just tested and for me works. Thanks.
1700585,2017-06-26 15:08:41 UTC,This appears to only affect containers that have existed for some time. Recently created containers are not affected.
1700585,2017-06-27 15:52:38 UTC,"As of this morning, we have updated our Swift nodes from version 2.4.0 to 2.10.2 instead. We are unsure if this will help mitigate the issue, but we believe we ought to be on a version listed as ""stable"" on https://wiki.openstack.org/wiki/Swift/version_map which 2.4.0 is not."
1700585,2017-06-27 16:47:31 UTC,"Greg, based on your comment in #20, I realized that there is some confusion around ""stable"" releases and otherwise. I've updated the version map page to hopefully make it more clear."
1700585,2017-06-27 16:52:54 UTC,In response to comment #17:
1700585,2017-06-27 17:23:22 UTC,"John, we are using distro packages:"
1700585,2017-06-27 17:26:24 UTC,The previous comment was the distro for the proxy. These are for the three Swift nodes:
1700585,2017-06-27 15:35:40 UTC,"clayg, please look for a ghebda (Greg Hebda) on #openstack-swift if you can continue helping this investigation for us. Thanks."
1700585,2017-06-27 18:30:29 UTC,"You're talking about the base OS packages, but John meant Swift in comment #22. Only you know where you are obtaining it. AFAIK, CentOS itself does not publish Swift. Most of the time, it comes from RDO. But some people just run pip to get a stable branch (on top of CentOS, yes). In your original report you are aware that you run Swift 2.4.0, so you should also know where that comes from."
1700585,2017-06-27 20:44:23 UTC,Maybe we need recon-cron plumbing for part counting?
1700585,2017-06-27 22:04:48 UTC,Lots of discussion here today: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/%23openstack-swift.2017-06-27.log.html
1700585,2017-06-27 22:25:05 UTC,"Regarding comment #28, that is kind of what I was attempting to get at in comment #15 above. Some additional help from the system would be nice. It appears to me that the system can currently have ""the wheels almost coming off"", but nothing about swift-recon will indicate there is anything amiss. Unless there is another util that would catch this situation, I would think Swift ought to provide something above and beyond what is in Clay's script. I love that there is a script, but it feels like there reason it exists is because there is something lacking in Swift itself. IMHO, it is time to address that and entertain what Clay is suggesting in comment #28. Just my 2 cents."
1700585,2017-06-27 23:11:33 UTC,"yes, the recommended existing tooling for alerting about this specific problem (unavailability) is swift-dispersion-report:"
1700585,2017-06-28 16:34:52 UTC,clayg are we correct to assume that the output of
1700585,2017-06-28 16:43:35 UTC,"clayg, also, is it possible that the script"
1700585,2017-06-27 18:44:33 UTC,Appears to be from here (yum output):
1700585,2017-06-26 21:06:11 UTC,"These are definitely not ghost listings since we do (in some cases) have the original files in another file system (removable drives, etc) outside of Swift. In addition, these files in Swift should not have been deleted. So, I do not think bug #1619408 applies here."
1700585,2017-06-27 16:08:59 UTC,"I may be wrong in comment #18 if I misunderstand ghost listings. I am assuming them to be due to a delete operation. If they are instead due to a create operation that fails, then perhaps this is a dupe of that. I think we'd need more evidence to corroborate it first, though."
1700585,2017-06-26 17:19:40 UTC,Comment #9 above has the wrong curl cmd line for 2.1997 in that it does not cover 10.11.12.78 so here is the corrected one:
1700585,2017-06-26 15:09:35 UTC,The system has 3 nodes with 28 disks each. It has been running since Sept 2015.
1700585,2017-06-26 15:11:34 UTC,"The orphaned state affects only some of the files in a pseudo-folder. Our smallest container is ""1"" and a full audit of it shows:"
1700585,2017-06-26 15:13:12 UTC,Larger containers such as container 7 shows a similar pattern:
1700585,2017-06-26 19:42:46 UTC,Can you turn your proxies request_node_count [3] >= 84 (3 nodes * 28 devices) and check again for the 404'd objects.
1700585,2017-06-26 16:07:46 UTC,"Did you do any rebalance recently? Are all *.rings.gz identical on all nodes? Same for
swift_hash_path_prefix and swift_hash_path_suffix in /etc/swift.conf - this is unchanged and identical on all nodes?"
1700585,2017-06-26 16:42:37 UTC,We added 7 drives to each of the 3 nodes early last week.
1700585,2017-06-26 16:45:00 UTC,Here is the swift-get-nodes for both files in container 1.
1700585,2017-06-26 15:14:18 UTC,There appears to be no rhyme or reason as to the missing data. Our data is read-only once stored and we have eliminated local client applications from the root cause leaving only Swift.
1700585,2017-06-26 16:47:41 UTC,"Rather, the first curl is for the OK 200 file that is fine."
1700585,2017-06-26 16:48:30 UTC,Let me know if you need anything else.
1700585,2017-06-26 17:01:17 UTC,"[root@swift-r1z1n1 ~]# ll /srv/node/r1z1n1-d7/objects/506/490/7eb259c3a61b11add960a8470849b490
total 84
-rw------- 1 swift swift 81282 Dec  8  2016 1461540671.59374.data"
1700585,2017-06-26 17:02:39 UTC,"The one that is not there, isn't there, though:"
1700585,2017-06-26 17:08:37 UTC,"I think swift-recon covers this, but here is another look:"
1700585,2017-06-26 17:14:30 UTC,For the record:
1700585,2017-06-26 16:46:57 UTC,"Here is the curl output from those two. The first is there, so we only do the one. The last three curl cmd lines are all the places it ought to be, but is not:"
1700590,2017-06-28 14:08:31 UTC,Found relevant information in util-linux sources:
1700592,2019-09-19 12:04:00 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1700593,2017-10-24 10:33:16 UTC,1. Attached configuration has log-bin disabled. (default is off)
1700593,2017-11-14 19:43:36 UTC,Thanks for the fix y'all!
1700593,2017-10-26 08:06:01 UTC,Many thanks :)
1700593,2017-10-25 06:18:28 UTC,"commit 481c6e517ecba6acdfd2adc323921dc1434d2d74
Merge: 09dbf65 66b8ade
Author: Krunal Bauskar <email address hidden>
Date:   Wed Oct 25 11:37:20 2017 +0530"
1700593,2017-10-24 08:30:46 UTC,FYI it does seems to be enabled in our production cluster (log_bin = ON). I don't think we ever disabled it
1700593,2018-01-18 08:34:03 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-883
1700593,2017-10-20 20:11:13 UTC,"Our tests ran successfully with 5.6.28-25.14.1, but failed in the same way as the OP's did on 5.6.37-26.21.1 and 5.6.36-26"
1700593,2017-06-26 22:08:26 UTC,Thank you for the report.
1700593,2017-06-27 12:29:41 UTC,I've attached the configuration and logs.
1700593,2017-10-24 04:28:41 UTC,This error happens when log-bin=0
1700593,2017-06-27 12:38:47 UTC,"(woops, launchpad didn't show the last log I thought I forgot to paste it)"
1700593,2017-06-27 12:37:48 UTC,I've attached the configuration and logs
1700595,2017-06-28 11:15:52 UTC,"Hi Russ,"
1700595,2017-06-28 13:19:39 UTC,"You'll need to have a board supported by pyOCD connected. To show connected boards that pyOCD recognizes you can add the '-l' flag:
pyocd-gdbserver -l
0 => FRDM-K64F [k64f] boardId => 0240000033514e45001c500585d40025e981000097969900"
1700595,2017-07-01 16:16:18 UTC,"Issue raised by Tejas on the GDB bug tracker can be found here:
https://sourceware.org/bugzilla/show_bug.cgi?id=21698"
1700609,2017-06-26 17:12:43 UTC,"The hardware is a PIPo X9 Intel Baytrail device. My imediate problem is the GoodIDX touch screen is not usable.
[    5.734923] Goodix-TS: probe of i2c-GDIX1001:01 failed with error -22"
1700609,2018-01-19 22:04:08 UTC,"I can confirm this behaviour for a Chuwi H13 Tablet with Kubuntu (Ubuntu 17.10). There are a couple of reports in the Chuwi forum, concerning tablets recently delivered."
1700609,2018-03-23 21:40:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700609,2018-03-24 13:46:05 UTC,Same bug was fixed (only for Mageia) here https://bugs.mageia.org/show_bug.cgi?id=22703
1700609,2018-03-27 15:52:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1700624,2017-06-26 22:16:15 UTC,"I agree that it is inconsistent, though it happens that way because of what
is ""optional"" vs ""mandatory"". You have to specify a cloud to bootstrap
onto, from which we can come up with a default name. And for 'add-model' we
can default to the cloud that you bootstrapped onto, but we need the name
for the model."
1700624,2017-06-27 16:31:26 UTC,Totally fine with wishlist priority...
1700636,2017-09-29 05:07:20 UTC,"Even the lack of a ""File Save"" option in that menu is strange."
1700643,2017-06-26 21:02:08 UTC,"There are so many variables here that narrowing it down to a specific cause is probably not worth the effort. I imaging in trying to draw all the UI and icons on your display at a factor of 25x, your GPU ran out of memory or something."
1700645,2018-12-13 07:43:31 UTC,"'morning,
I'm also affected, I'm not sure since when as I only occasionally receive encrypted emails."
1700645,2017-12-21 18:56:49 UTC,"Hello Vej,"
1700645,2017-07-15 15:04:13 UTC,"Thanks for everything, Vej.
To answer your questions, /etc/X11/Xsession.d/90gpg-agent does exist on my system and use-agent is enabled in ~/.gnupg/gpg.conf."
1700645,2017-07-15 13:01:32 UTC,"Hello James,"
1700645,2017-07-03 19:30:00 UTC,"Hmm, no, my only output there is"
1700645,2017-07-09 20:13:55 UTC,"Hello James,"
1700645,2017-07-02 11:14:55 UTC,Hallo James.
1700645,2017-06-30 19:17:24 UTC,"||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
un  gpg            <none>       <none>       (no description available)
un  gpg-agent      <none>       <none>       (no description available)
un  gpgsm          <none>       <none>       (no description available)
ii  gpgv           2.1.15-1ubun amd64        GNU privacy guard - signature ver
un  gpgv1          <none>       <none>       (no description available)
un  gpgv2          <none>       <none>       (no description available)
"
1700645,2017-06-29 21:24:10 UTC,"Hello James,"
1700645,2017-07-10 21:08:40 UTC,"The backup completed successfully once I manually started gpg-agent. I'm not sure if this is meant to be triggered by deja-dup. If so it remains a bug, otherwise I can close it and launch the daemon manually at boot."
1700646,2017-07-01 16:02:04 UTC,"This may be related to how the linker retains debug information for functions that have been stripped via --gc-sections, but sets the address of those functions to 0. So gdb needs to ignore functions with address 0."
1700646,2017-07-01 16:12:23 UTC,"Yeah, that is a possibility, but the fact that the same elf file works with GDB 7.8 but not GDB 7.10 makes me think its a regression. Also, for further visibility there is also a ticket here to track this issue:
https://sourceware.org/bugzilla/show_bug.cgi?id=21695"
1700649,2018-05-29 14:50:41 UTC,usbfs: process <pid> (mtp.so) did not claim interface 0 before use
1700649,2018-05-29 14:40:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700652,2018-01-25 09:13:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1809
1700656,2017-06-26 22:07:36 UTC,"StacktraceTop:
 JS::Zone::isGCSweeping (this=<optimized out>) at ./gc/Zone.h:223
 js::gc::IsAboutToBeFinalized<js::gc::Cell> (thingp=thingp@entry=0x7fff75d57620) at /build/mozjs24-aUzIx7/mozjs24-24.2.0/js/src/gc/Marking.cpp:291
 js::gc::IsCellAboutToBeFinalized (thingp=thingp@entry=0x7fff75d57620) at /build/mozjs24-aUzIx7/mozjs24-24.2.0/js/src/gc/Marking.cpp:713
 IsAboutToBeFinalized (key=<optimized out>) at /build/mozjs24-aUzIx7/mozjs24-24.2.0/js/src/jsinfer.cpp:5515
 js::types::TypeSet::sweep (zone=0x32a3800, this=0x7ca9eb0) at /build/mozjs24-aUzIx7/mozjs24-24.2.0/js/src/jsinfer.cpp:6208"
1700656,2020-11-16 08:36:44 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life on April, 2019"
1700657,2017-09-11 14:37:47 UTC,How can I install the version on Ubuntu with this fix?
1700657,2017-09-10 01:20:38 UTC,Looks to me like the patch is in Ubuntu kernel.
1700657,2017-08-30 13:40:22 UTC,"The patch is accepted upstream, but has to be backported to Ubuntu kernels <= 4.13.
See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710392"
1700657,2017-08-30 13:07:39 UTC,Could we please get any report on the progress? Did someone respond?
1700657,2017-08-16 22:02:01 UTC,"The title of the email might be better to include the directory path to the file, and a brief description."
1700657,2017-08-16 21:59:53 UTC,"Please do use my email or name, etc."
1700657,2017-08-14 12:05:56 UTC,"I downloaded the kernel source (newest stable), added the line you mentioned and compiled it. It works for me."
1700657,2017-08-12 18:03:42 UTC,"Not at all, go ahead and add mine. Thanks!"
1700657,2017-08-12 16:04:28 UTC,"OK, I'm still fixing the patch ^^"
1700657,2017-08-10 02:55:09 UTC,"Actually I can't, I am not the maintainer for the subsystem."
1700657,2017-09-17 00:18:42 UTC,"Darn, fix is definitely not released yet. I bumped it. I don't have authority to bump it back however."
1700657,2017-08-09 20:50:02 UTC,@kaihengfeng
1700657,2017-08-03 19:42:46 UTC,"Never mind, I think I got it working:
https://lkml.org/lkml/2017/8/3/765"
1700657,2017-08-03 19:29:22 UTC,"Hi, I already created a pull request on Github.
@mykesx already noted, that I made a indentation error.
I updated the patch, see attachment."
1700657,2017-08-03 19:06:32 UTC,@mykesx I already set my drive's mode to AHCI and reinstalled Windows first thing :)
1700657,2017-08-03 18:36:52 UTC,"I must say the 720 is zippy to use.  It took me 36-38 minutes to do a complete kernel build.  apt-et update/upgrade takes just a few seconds.  At least with KDE (other desktops may vary), I was able to adjust the font sizes, and other window decorations and the like to make the environment look great (to me) in 4K resolution."
1700657,2017-08-03 18:32:45 UTC,@CoolStar nothing to do.
1700657,2017-08-03 18:30:55 UTC,"@CoolStar You have to change the bios to AHCI for the USB thumbdrive install image to boot.  At least for me.  I mean, we all have the same Yoga 720 15"" laptop, right?"
1700657,2017-08-03 17:44:11 UTC,"@mykesx I think that might be a problem with GRUB. I wasn't able to boot Ubuntu here at all (not even the installer) until I used another PC to install to a USB SSD, replaced GRUB with rEFInd, then plugged the USB SSD into the Yoga and booted up"
1700657,2017-08-10 09:25:15 UTC,"Yes, I'm currently not at home, so I'll have to wait until tomorrow to re-try."
1700657,2017-09-29 12:41:34 UTC,So will this be in the 17.10 release? The fix is in the Linux kernel since a month.
1700657,2017-10-11 04:22:55 UTC,"Sorry for the ignorance. Does ""fix committed"" mean it is ready to be
installed on my computer? If so, can you share a link for the correct
download?"
1700657,2017-10-12 14:14:49 UTC,"can someone please add a link to a instruction for someone who has never heard of ""compile your kernel with the patch"" that explains step by step the commands, they have to enter on the console please?"
1700657,2018-09-09 18:16:05 UTC,On 4.15.0-29-generic (Ubuntu 16.04) touchpad works for me except for mechanical left/right click (tapping the touchpad works though).
1700657,2018-01-14 12:50:47 UTC,I just tried the daily ISO of Bionic Beaver and there the touchpad doesn't work either (4.13.0-25-generic)
1700657,2017-11-04 17:35:20 UTC,Why didn't this land in mainline yet?
1700657,2017-10-30 19:26:53 UTC,This bug was fixed in the package linux - 4.10.0-38.42
1700657,2017-10-23 19:45:41 UTC,"I found out, that networking there is only broken due to a bug in the apparmor settings, you can fix this by"
1700657,2017-10-21 08:47:01 UTC,Everything works fine now with kernel 14.4.0-041400rc5 apart from DHCP. I still have to use manual IP4-settings to set my IP.
1700657,2017-10-20 18:31:16 UTC,@Aswin Gigi (aswingigi): I also had the problem that the boot freezes when I try to start with 14.4-rc5 and I solved it by disabling secureboot in bios.
1700657,2017-10-20 03:35:57 UTC,It's in zesty-proposed. You need to enable -proposed to test it.
1700657,2017-10-19 19:44:00 UTC,Built a new kernel from the Ubuntu git and applied the patch to intel-lpss-pci.c and the trackpad works fine again. I hope this gets into artful very soon.
1700657,2017-10-19 18:08:14 UTC,What's the current status on this? I updated to artful and expected this to be fixed but my touchpad no longer works (I'd build a patched 4.10 with the fix on zenial).
1700657,2017-10-18 23:59:43 UTC,"Sorry for the late reply but @io-mattia98, even hitting escape doesn't do anything for me when the system freezes."
1700657,2017-10-18 18:57:50 UTC,"I installed this kernel on my Ubuntu 17.10 Arful Awkward, but it does not seem to work since kernel 4.10 is too old for my Lenovo Yoga 720-15.
(Link: https://launchpad.net/ubuntu/zesty/amd64/linux-image-4.10.0-38-generic/4.10.0-38.42 )"
1700657,2017-10-18 08:58:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1700657,2017-10-15 03:37:54 UTC,I tried this instructions: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
1700657,2017-10-13 16:08:55 UTC,"Huh.. I've never had that problem.. What does it say when you press ESC at
the ""black screen""?"
1700657,2017-10-13 15:37:22 UTC,"Was trying to troubleshoot this after I got my 720 yesterday day and this thread was a godsend, I downloaded the latest stable kernel, applied the line patch and it worked perfectly. Thanks!! :D"
1700657,2017-10-12 16:40:05 UTC,"I just downloaded the source to the newest stable kernel from kernel.org, manually added the line that fixes this bug with a text editor and followed this guide to compile it: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild"
1700657,2017-10-12 14:44:38 UTC,I tried that like described here: https://askubuntu.com/a/963779/34298
1700657,2017-10-12 14:30:50 UTC,"The simplest way is to install the latest linux mainline kernel on Ubuntu:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Just download and ""dpkg -i"" the corresponding .deb packages."
1700657,2017-08-03 17:40:28 UTC,"Yes, this should be submitted upstream, although I don't know how to submit it myself. kaihengfeng, if you could submit it and just give me credit for the patch that would be great :)"
1700657,2017-08-02 19:21:10 UTC,"definitely.  If I sudo reboot, I get black screen and no boot.  If I power off the machine and boot, it works."
1700657,2017-07-21 14:24:18 UTC,"Sorry, forgot to mention the most important bit of information: that did not solve the problem.
Nor did adding ""acpi=biosirq"" or ""i8042.reset"" to the kernel line (solutions reported for other computers with similar problems)."
1700657,2017-08-02 18:43:48 UTC,"It seems that I have to power off the laptop and power it on to reboot, or I just get a black screen."
1700657,2017-07-30 15:54:41 UTC,"The previous entries in dmesg was with @coolstar's patch and with the patch to elan_i2c_core.c,
only applying @coolstar's patch for v4.13rc1 i see this in dmesg:"
1700657,2017-07-30 14:56:14 UTC,With @coolstar's patch the touchpad reported in dmesg:
1700657,2017-07-30 07:04:32 UTC,"I have managed to get my Yoga 720 15""'s touchpad working in Linux Mint (based on Ubuntu)"
1700657,2017-07-28 22:38:13 UTC,I also tried adding this line:
1700657,2017-07-28 22:05:50 UTC,"I compiled 4.13rc1 including the patch adding the ELAN0651 to the acpi device id array.
It did not help. I think the device is connected over USB:"
1700657,2017-07-28 02:41:11 UTC,"I just tried Kernel 4.13 RC2. Nothing changed.
I did not test your ""ELAN0651"" patch. Maybe both together could enable the touchpad..."
1700657,2017-07-27 16:11:07 UTC,"I just checked my dmesg:
If ACPI is the problem, shouldn't dmesg show some ""elan0651"" device (although it does not bind any driver to it)?"
1700657,2017-07-27 16:00:01 UTC,"There was a commit regarding the elan_i2c driver:
https://github.com/torvalds/linux/commit/a2eaf299d134cfe780c68c771f88d81516c1e70d"
1700657,2017-07-21 14:04:34 UTC,"This sounds like a problem with SecureBoot.
Did you disable UEFI SecureBoot?"
1700657,2017-07-21 13:47:52 UTC,I managed to boot the kernel I had compiled with the above patch (but not based on 4.12.1 but on 4.8.0). I needed to change to legacy boot mode in BIOS to get it to boot.
1700657,2017-07-17 03:51:51 UTC,"I am using Ubuntu 16.04.2, currently running the default 4.8.0-58-generic kernel (works fine except for the touchpad not being detected, had to switch sata mode from raid to ahci for it to detect the ssd though)."
1700657,2017-07-17 00:04:19 UTC,Which ubuntu distribution do you use?
1700657,2017-07-16 23:14:43 UTC,"I am affected by this bug as well (Lenovo Yoga 720-15IKB, touchpad not detected)."
1700657,2017-07-14 15:51:23 UTC,I attached parts of the requested dmesg to this comment.
1700657,2017-07-11 05:03:29 UTC,"Add ""i2c_hid.dyndbg=+p"" to the kernel parameter, reboot, then attach `dmesg` here, thanks."
1700657,2017-07-10 15:36:27 UTC,"I tried it with latest mainline kernel 4.12 on Ubuntu 17.10, but the touchpad is still not working"
1700657,2017-07-05 14:07:13 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1700657,2017-06-26 22:00:16 UTC,This change was made by a bot.
1700657,2017-08-02 19:08:59 UTC,"@mykesx, yes, it was my impression that ""changing"" a value in BIOS twice (to its original value was not an idempotent operation -- hence there are bugs in the BIOS). I can reproduce the black screen when rebooting, but it also happens for me on an unpatched kernel. I guess you should open a separate bug for that?"
1700657,2017-07-30 17:46:10 UTC,Wonder if there might be something with the kernel versions... can you try applying the intel-lpss-pci patch on top of an unpatched Ubuntu 4.10 kernel? I tested the patch with 4.10.0-28-generic here
1700657,2017-07-30 17:48:48 UTC,"Also, the BIOS version on my Yoga 720 15"" (where my patch is working) is 4MCN20WW (so we can try seeing if we can get reproducible results)."
1700657,2017-07-30 09:24:02 UTC,@CoolStar
1700657,2017-07-30 21:01:39 UTC,"I also compiled linux kernel 4.10.17 with your patch.
Using your patch causes crashing of the ""i2c_designware"" driver (see attachment).
I also tried the current Linux kernel commit (=> 4.13), with the same result."
1700657,2017-08-02 18:33:53 UTC,I got it working!
1700657,2017-08-02 16:22:22 UTC,I can send a patch to upstream. Let's wait for CoolStar's response.
1700657,2017-08-02 15:40:33 UTC,The patch isn't in the 4.13 master branch code.
1700657,2017-08-02 12:21:26 UTC,Thanks for the fix CoolStar! When will this patch integrated into the main Linux kernel?
1700657,2017-08-01 14:09:05 UTC,@bjorn exactly what I did.
1700657,2017-08-01 12:59:33 UTC,"@mykesx, I can relate, I'm in the same position (I set predefined charge level in windows for example, since yoga notebooks are not supported by tp_smapi). I've managed to keep the Windows install functioning (rebooted into safe mode when changing SATA mode from RAID to AHCI."
1700657,2017-07-30 19:44:26 UTC,"Thanks, I'm on the same BIOS version. Compiling for the 4.10.0-28 kernel did not help in my case:"
1700657,2017-08-01 07:07:58 UTC,"@mykesx I had the same problem, for some reason (I have no idea why) changing to legacy boot in BIOS helped. For 4.13rc I cloned: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/, applied the ubuntu specific patches, added the PCI id line and set do_zfs = false in debian.master/rules.d/amd64.mk (never figured out how to compile spl/zfs)."
1700657,2017-08-01 02:31:56 UTC,Thanks
1700657,2017-08-01 01:13:04 UTC,"@mykesx:
If you don't want to wait for a upstream fix I'd recommend you to simply compile your own kernel like described here:
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild"
1700657,2017-08-01 12:38:05 UTC,@bjorn I have come to the same conclusion.  THere's something about the kernel build process that yields a kernel that won't work due to some setting in the BIOS.  Yet kernels on the install media and from apt-get dist-upgrade do work fine.
1700657,2017-07-31 21:44:58 UTC,"Instructions in post #30 did not work for me.  In fact, my machine now won't boot."
1700657,2017-07-31 18:55:29 UTC,"I created a git repository with the patch:
https://github.com/Hoeze/linux/tree/zesty
The requested patch is attached to this comment."
1700657,2017-07-31 18:09:59 UTC,@CoolStar thanks! Applying the updated patch works for me (I applied it to v4.13rc1)
1700657,2017-07-31 17:27:09 UTC,@CoolStar
1700657,2017-07-31 17:07:57 UTC,aha I see the problem with the previous patch I posted here (copy error):
1700657,2017-07-31 16:57:45 UTC,Should see something like this in dmesg when the touchpad is working:
1700657,2017-07-31 16:55:47 UTC,Here's the kernel image + headers I'm using and the patched module I'm using:
1700657,2017-07-31 21:48:08 UTC,"^^^ Sorry, that was 17.04 (Kubuntu)"
1700657,2017-07-30 22:28:52 UTC,Looking closer at my dmesg that happens for me too (see attached file)
1700660,2017-06-26 22:02:36 UTC,There seem to be three solutions to this problem:
1700660,2019-03-22 15:28:54 UTC,Is anyone still working on this solution??
1700660,2020-06-25 15:40:34 UTC,"As temporary workaround, some driver's calls are receiving a dict with primitive types instead of DB objects[1]."
1700660,2020-06-25 16:54:48 UTC,"This bug was discussed during the upstream openstack-manila meeting on Thu 25th June 2020:
http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-06-25-15.01.log.html#l-74"
1700665,2017-06-27 17:02:53 UTC,"I just found ""gtcli new"" (or... ""gtgcli new""?) which makes gtg crash, but I think suits my purpose (except that I can't specify a title, but I'll either do that myself & submit a patch, or resubmit a more accurate bug report)."
1700665,2020-12-29 22:19:11 UTC,"Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1700668,2018-03-16 04:25:48 UTC,This is what I intend to use in Debian: https://github.com/Debian/britney2/commit/adbe6d5f67f63b88d9b19ad2c14359c0b3fd68af#diff-7fb9313c3c107442730b43189876c4ce
1700668,2018-05-03 08:13:10 UTC,"Debian is now (since yesterday) using my approach of baselining. I.e. Debian checks against a baseline that for PASS looks at all tests except one's own from unstable. A FAIL test triggered by ""migration-reference/0"" will reset the baseline for testing to FAIL."
1700668,2018-03-09 21:08:45 UTC,"As I am close to enabling autopkgtest results in Debian (albeit in a different form: not as gate, but as an age shifter) this is very relevant for me. In Debian it will happen way more than in Ubuntu that a regression moves into testing and remain there. Thus, for Debian I believe I'll have to be working along the reasoning of Steve."
1700668,2018-03-08 20:29:28 UTC,Bump; this is still often a pain to deal with as an uploader who does transitions (especially involving KDE packages with flaky autopkgtests (which is another issue)) but isn't a member of the Release Team.
1700668,2018-03-19 18:48:51 UTC,"The patch in my previous message is incomplete. I think it will work alright when a package migrates while having a regression, but the code is insufficient for regressions caused by dependencies migrating. I'll think about it."
1700668,2017-06-28 23:43:49 UTC,"We've discussed this further on IRC and I don't think we've converged on a consensus just yet, but I'll lay out my position here for the bug log:"
1700668,2017-06-27 16:39:21 UTC,Here's another example of a test that only passed once (well twice):
1700668,2017-06-27 14:39:57 UTC,I think this might be a dupe of bug #1688516 - please mark it if so.
1700668,2017-06-26 23:18:07 UTC,"As a concrete example of this, the latest perl upload triggered test failures on 34 reverse-dependencies, all of which were reproducible with the packages in the artful release pocket - at least on amd64, which was as much as I spent the time to analyze, and that alone took me upwards of an hour's investment."
1700668,2017-06-30 22:30:43 UTC,"On Wed, Jun 28, 2017 at 11:43:49PM -0000, Steve Langasek wrote:

> We've discussed this further on IRC and I don't think we've converged on
> a consensus just yet, but I'll lay out my position here for the bug log.
"
1700672,2017-09-11 13:10:28 UTC,"This is still valid, by the way."
1700672,2018-01-02 16:00:40 UTC,Still an issue with 384.90. In Xorg8.log I see
1700672,2018-08-30 16:34:52 UTC,Another issue as well in Ubuntu 18.04 and NVIDIA 390.00
1700684,2017-06-27 16:05:10 UTC,"Automatically discovered version newton in description. If this is incorrect, please update the description to include 'nova version: ...'"
1700684,2018-07-27 06:08:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586446"
1700684,2019-10-07 13:46:01 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/586446
Reason: This has been here in failing state for some time with no changes. I think it's safe to abandon now"
1700686,2017-06-27 07:50:41 UTC,"@Alfie and @Robert,"
1700686,2017-06-28 02:42:13 UTC,"Try the kernel mentioned in the comment #2 on the Ubuntu desktop, the HDMI audio works normally and there is no i915 or HDMI related warning message in dmesg"
1700688,2017-06-27 14:55:55 UTC,See the github pull request with some attempted improvement here: https://github.com/elementary/greeter/pull/50
1700688,2017-06-27 13:27:56 UTC,"Hi, this is a hi-dpi issue I guess already noted in this issue: https://github.com/elementary/greeter/issues/7"
1700691,2017-06-27 07:38:50 UTC,"Self-signed SSL certs are, generally speaking, a bad idea and they pose problems to operators.
The solution you propose does not solve the problem fully - you still have to ship certs around, the difference is that you use ""juju config"" to do that rather than ""juju scp"""
1700696,2017-06-27 04:38:50 UTC,Oh sigh debian has already been through this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846200
1700704,2017-06-27 06:30:07 UTC,This change was made by a bot.
1700711,2019-09-25 22:59:22 UTC,Where is the blank line? I don't quite understand what is empty here.
1700711,2019-09-25 23:19:00 UTC,The blank part was after the date..
1700711,2019-11-25 04:17:41 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1700720,2017-06-27 09:43:39 UTC,"Review in progress for https://review.opencontrail.org/33216
Submitter: Bruno Fernando (<email address hidden>)"
1700731,2017-07-25 05:17:17 UTC,"At this point we don't support having a subnet go away and come back with a different identifier. It would be possible to edit the database directly, and we have some plans around improving our space support (being able to add/remove/update existing definitions), but that work has not been started yet. It may be that we can get to some of this in a 2.3 time frame (in the next month or two)."
1700731,2017-06-29 11:04:17 UTC,"John,"
1700731,2017-06-27 10:30:39 UTC,I've uploaded machine-0 log here: https://private-fileshare.canonical.com/~sabaini/Lo4ahl2xohk3quoo/lp1700731/
1700731,2017-06-28 22:23:18 UTC,"I can see the folder holding the log file, but I'm unable to download the
log file itself."
1700744,2017-09-22 18:23:34 UTC,https://review.openstack.org/506743
1700746,2017-06-27 11:30:16 UTC,This change was made by a bot.
1700754,2017-06-29 06:58:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700754,2017-12-01 11:23:42 UTC,Specifically this bug:
1700759,2017-07-24 04:00:19 UTC,"just to add, i have ubuntu-sdk-team/ppa/ubuntu ppa installed for the sdk, maybe it conflicts with it?"
1700761,2017-08-24 14:39:58 UTC,Kolla still having this issue while building bifrost images.
1700761,2018-02-02 21:24:39 UTC,Just now noticing this since we typically interact through IRC. I'm afraid we are lacking context. Is this still occurring?
1700762,2018-01-18 08:21:15 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1991
1700762,2017-09-19 10:57:11 UTC,"This will be replaced with wsrep_debug in 5.7.19-29.22. Adding docs for it, tracked here: https://jira.percona.com/browse/DOC-539"
1700766,2017-07-24 08:40:19 UTC,"Jakub,"
1700766,2017-07-31 14:13:01 UTC,"Hello, sorry for late reply, I've been on vacation."
1700766,2017-07-31 19:53:26 UTC,I updated patch now it should work
1700766,2017-11-17 21:46:55 UTC,"- Rally works without admin, I am using it internally at my work"
1700766,2017-11-17 11:21:01 UTC,What's going on with this case?
1700766,2017-11-17 21:46:16 UTC,Can we have hangout call and try to debug this?
1700766,2017-07-03 09:44:04 UTC,"No problem, I'll wait."
1700766,2017-08-01 07:20:59 UTC,"Validation works, but it still complains about missing admin users, which I'm not able to provide:"
1700766,2017-07-03 09:09:23 UTC,"Jakub,"
1700766,2017-06-30 17:49:19 UTC,"Hi Jakub, I submitted my code yesterday to the git review.  I tried it with bunch of tasks and so far things work okay, but it definitely needs more effort on testing. I will work on it. And it will be great if you can help me with some testing stuffs!
https://review.openstack.org/#/c/479097/3"
1700766,2017-07-02 07:06:10 UTC,"I'm away from work machine now, it'll be done on Monday."
1700766,2017-07-02 04:29:39 UTC,"Jakub,"
1700766,2017-07-02 01:09:07 UTC,"Hello,"
1700766,2017-06-29 07:42:55 UTC,"> Yep Amy is working on it.
"
1700766,2017-06-28 20:07:42 UTC,"Yep Amy is working on it.
It would be nice if you could help her at least with testing that everything works."
1700766,2017-06-28 08:10:39 UTC,"> So that is possible to implement.
> Would you like to try?
"
1700766,2017-06-27 18:53:31 UTC,This looks more like a feature than bug.
1700766,2017-07-03 08:47:45 UTC,"Hello,"
1700770,2017-06-27 14:36:26 UTC,"Correct, packages may not depend on the -extra flavour of the kernel, as that does not at all make any guarantees that the running kernel as the necessory features."
1700775,2017-06-27 16:27:37 UTC,Added the screen about the issue
1700781,2018-01-25 20:26:18 UTC,Also marking this as high for cloud-archive even though it really isn't a cloud-archive issue. Appears to be an update-manager package issue.
1700781,2017-08-31 18:54:10 UTC,"Michael,"
1700781,2020-06-09 09:50:15 UTC,It looks like that has been fixed sometime in the last two and a half years as I cannot reproduce this error:
1700784,2017-06-27 18:00:42 UTC,"I am rather sure, that currently the VNC solution does not deal with the system type of the target system.
I have to check."
1700784,2017-06-27 18:54:31 UTC,"Thanks RaiMan, I will attempt a workaround in my test harness."
1700786,2017-06-27 23:40:15 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1700795,2017-06-27 17:08:42 UTC,YOu need to use the 'interface' endpoint with 'link-subnet': e.g.
1700795,2017-06-27 18:58:17 UTC,"Although I was using the wrong command, the bug remains valid: I cannot update, I need to destroy and create with 'unlink-subnet' and 'link-subnet'. This is inconsistent with the update capabilities of other commands."
1700795,2019-09-19 11:53:21 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1700810,2020-05-28 09:06:06 UTC,This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu14.3
1700810,2020-05-28 09:05:49 UTC,This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu19.3
1700810,2020-05-28 09:03:50 UTC,This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu28.2
1700810,2020-05-28 08:52:27 UTC,"The verification of the Stable Release Update for aptdaemon has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1700810,2020-05-28 08:52:23 UTC,This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu32.1
1700810,2020-05-21 01:45:57 UTC,Verified on Ubuntu 16.04 LTS
1700810,2020-05-21 01:34:03 UTC,Verified on Ubuntu 18.04 LTS
1700810,2020-05-20 23:46:56 UTC,Verified on Ubuntu 19.10
1700810,2020-05-20 23:35:05 UTC,Verified on Ubuntu 20.04 LTS
1700810,2020-05-28 08:51:57 UTC,"Ah, yes, didn't notice that the test case was invalidly stating `sudo python3 aptdaemon.crash` instead of `sudo python3 -m aptdaemon.crash`. Anyway, thanks for doing the right verification!"
1700810,2020-05-20 21:43:11 UTC,"All autopkgtests for the newly accepted aptdaemon (1.1.1+bzr982-0ubuntu14.3) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:"
1700810,2020-05-20 21:18:18 UTC,"All autopkgtests for the newly accepted aptdaemon (1.1.1+bzr982-0ubuntu32.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:"
1700810,2020-05-20 21:01:00 UTC,"All autopkgtests for the newly accepted aptdaemon (1.1.1+bzr982-0ubuntu19.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1700810,2020-05-20 19:05:32 UTC,"Hello Brian, or anyone else affected,"
1700810,2020-05-20 19:04:46 UTC,"Hello Brian, or anyone else affected,"
1700810,2020-05-20 19:04:10 UTC,"Hello Brian, or anyone else affected,"
1700810,2020-05-20 19:03:18 UTC,"Hello Brian, or anyone else affected,"
1700810,2020-05-12 19:54:55 UTC,This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu33
1700810,2020-05-11 21:27:01 UTC,"This is failing because apport's fileutils function ""make_report_path"" was renamed to ""make_report_file"" in September of 2015. So aptdaemon will need fixing in Ubuntu 16.04 LTS and later."
1700810,2020-05-20 22:47:09 UTC,"All autopkgtests for the newly accepted aptdaemon (1.1.1+bzr982-0ubuntu28.2) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1700811,2020-05-27 07:42:02 UTC,"BTW, the correct package for more recent releases is 'gnome-tweaks'."
1700811,2020-05-27 07:41:29 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1700811,2019-09-23 14:38:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700811,2017-09-02 21:03:46 UTC,"found this when searching for the same problem on arch-linux, i got it working again by launching tweak-tool and killing dependent python3 processes"
1700811,2017-06-27 19:15:11 UTC,"No, I started it several times and it always hanged."
1700811,2017-06-27 19:02:51 UTC,Did it work again the next time you tried to run Tweak Tool?
1700811,2017-06-27 18:04:01 UTC,After some minutes the process terminates and I get the message:
1700811,2017-09-07 20:06:34 UTC,"I can confirm, hitting this too."
1700812,2017-06-27 18:06:15 UTC,"Note, the actual manpage makes no mention of the package.  Which is
how it should be, as the manpage comes from upstream and not from
Ubuntu."
1700812,2017-06-27 21:11:45 UTC,"""So if this is a bug, it is a bug against manpages.ubuntu.com.""
Yes, I misspoke. To clarify I'm used to seeing the ""provided by"" link on manpages.ubuntu.com to link to the package I need to install to get the thing the man page references. That may just be a false association though."
1700812,2017-06-27 21:24:24 UTC,@mattofak - thanks for filing the bug.  I've linked it to the manpage project.  It'll get fixed.
1700814,2017-06-29 22:43:39 UTC,"Indeed it should be reasonable to do so.  Note that there are cases, including unprivileged containers, where file capabilities cannot be set, so the packaging would have to gracefully handle (i.e. ignore) that failure rather than fail the package install."
1700814,2018-02-26 16:12:51 UTC,"Even unprivileged containers are now usable in containers with the right kernel, so this would be a good thing to add to the packaging."
1700817,2017-07-12 18:14:53 UTC,"Don't worry about this now. It's so far off your radar and no one has even looked at it as far as I can tell, so I'm guessing that it'll never get fixed. I'll find something else."
1700818,2021-02-11 23:07:13 UTC,"Looks good to me! I filtered by Czech language to retrieve the titles, then did searching by some of their key words. My sign off is at:"
1700818,2017-11-08 19:10:49 UTC,Here's a conversion of the files from binary MARC to MARCXML.
1700818,2020-10-27 14:20:14 UTC,I'll make a branch to add this to the concerto data.
1700818,2020-10-27 15:41:50 UTC,user/dyrcona/lp1700818-add-czech-bibs https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dyrcona/lp1700818-add-czech-bibs
1700819,2017-06-27 19:11:00 UTC,Patch submitted to kernel-team mailing list:
1700819,2017-07-21 09:25:11 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1700819,2017-08-03 16:29:32 UTC,This bug was fixed in the package linux - 4.10.0-30.34
1700819,2017-08-10 05:56:17 UTC,This bug was fixed in the package linux - 4.11.0-13.19
1700825,2018-07-16 07:01:25 UTC,"Change abandoned by jichenjc (<email address hidden>) on branch: master
Review: https://review.openstack.org/489519"
1700825,2018-02-14 04:23:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544163"
1700825,2018-02-14 02:51:50 UTC,"oops incorrect input, still a valid bug"
1700825,2018-02-14 02:45:11 UTC,latest master fbdefacc1d7be98d9b34a2fb7f35aada33611604
1700825,2017-08-10 13:12:22 UTC,"Reviewed:  https://review.openstack.org/489525
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a36e7cda45f8b35f6d5325c3b9c77b80d7e1847
Submitter: Jenkins
Branch:    master"
1700825,2017-08-01 08:19:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/489525"
1700825,2018-07-16 07:01:39 UTC,"Change abandoned by jichenjc (<email address hidden>) on branch: master
Review: https://review.openstack.org/544163"
1700825,2017-08-01 07:17:45 UTC," 390 class InvalidName(Invalid):
 391     msg_fmt = _(""An invalid 'name' value was provided. ""
 392                 ""The name must be: %(reason)s"")
 393"
1700825,2017-08-01 06:46:24 UTC,"from compute/api.py, looks like key_name is None is valid..... we just set it to None"
1700825,2017-08-01 06:41:30 UTC,"sorry, a typo, null is not allowed"
1700825,2017-08-01 06:41:13 UTC,"key_name is defined
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/keypairs.py#L87"
1700825,2017-07-10 12:32:21 UTC,"Recently upgraded to Mitaka from Kilo and encountered this bug which broke a few of my apache-libcloud scripts. Ignoring the ""name/key_name"" naming issue, should key_name be allowed to be null to begin with?"
1700825,2017-06-28 10:26:36 UTC,This is going to take some unwinding of the schema validation code. The level of reuse there definitely doesn't make it clear how you'd specify which name in a big object is failing.
1700825,2017-08-01 07:54:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/489519"
1700827,2017-11-10 06:42:20 UTC,"> - Why is this set as a native package?
"
1700827,2017-11-11 11:40:41 UTC,"+1 on converting the package to a 3.0 quilt format, plus using debhelper 9 and fixing the plethora of lintian warnings."
1700827,2017-11-13 09:27:58 UTC,"| Using a proper 3.0 (quilt) package would make it easier to [...]
"
1700827,2017-11-13 14:07:55 UTC,"Hi Natha,"
1700827,2017-11-13 18:15:31 UTC,"Additionally,"
1700827,2017-11-13 21:10:31 UTC,Debian bugs related to my above comment ^
1700827,2017-11-15 15:23:37 UTC,I have reported another debian bug for pmatop (as discovered by Christian)
1700827,2017-11-21 15:26:14 UTC,"# Missing build dependency for Ubuntu :
https://bugs.launchpad.net/bugs/1733619 (related to debbug #881649)"
1700827,2017-11-24 07:20:34 UTC,"With the upstream changes mentioned above and a couple of tweaks (everything up to and including commit f09cac4), I've been able to complete a build, package, install and start PCP operation on all the machines in my PCP QA Farm."
1700827,2017-11-23 12:33:06 UTC,Nathan have committed upstream the two changes I have submitted :
1700827,2017-11-24 15:38:17 UTC,"Additionally, PCP upstream change the debhelper compatibility level (debian/compat) first introduced in commit : eb1ea37[1] from ""5"" to ""9""."
1700827,2017-11-24 21:02:28 UTC,About the pmatop segfault in 3.12.2
1700827,2017-11-27 06:00:38 UTC,Re systemd.
1700827,2017-11-27 17:21:57 UTC,3.12.2-1 from Debian got auto-synced in Ubuntu bionic
1700827,2017-11-28 05:01:40 UTC,things which should be addressed:
1700827,2018-03-13 23:30:36 UTC,"Hi Eric, all,"
1700827,2017-11-21 16:57:08 UTC,"# pcp - convert dpkg-source format to 3.0 (quilt)
https://bugs.launchpad.net/bugs/1733646"
1700827,2017-11-09 23:36:36 UTC,"> Why is this set as a native package? It's rather obviously not one, as it also ships and works on other distributions.
"
1700827,2017-11-10 21:24:42 UTC,"Eric,"
1700827,2017-11-09 14:26:39 UTC,"I believe it's really useful to also include papi [1] in main as it is a dependency of pcp and offers support for the performance counter hardware in many processor types providing a low-level source of metrics.
This ofc seems like an important feature in a performance monitoring suite."
1700827,2017-11-09 21:35:59 UTC,I'm doing this review (I'm not done though).
1700827,2017-06-27 19:45:44 UTC,"The following, must first be addressed before this package would be accepted into main :"
1700827,2017-06-27 20:00:57 UTC,Other discussions ....
1700827,2017-07-13 13:17:40 UTC,Reported main inclusion request for the dependency (papi): bug #1704130.
1700827,2017-08-04 13:22:48 UTC,"Dariusz has created some autopkgtest scripts doing invocation of some of the cli pcp tools, ..."
1700827,2017-08-07 10:22:29 UTC,I have reported a Debian bug with request to include the autopkgtests.
1700827,2017-08-17 07:15:01 UTC,"I reviewed pcp version 3.12.0build2 as checked into artful. This should
not be considered a full security audit but rather a quick gauge of
maintainability."
1700827,2017-08-17 14:26:05 UTC,"Hi, Seth -"
1700827,2017-08-18 21:34:51 UTC,"Apropos the CVE's all of these have been completely addressed in past PCP releases.
CVE-2012-5530 - fixed in PCP 3.6.10 (released 19 Nov 2012)
CVE-2012-3421, CVE-2012-3420, CVE-2012-3419 and CVE-2012-3418 - all fixed in PCP 3.6.5 (released 16 Aug 2012)
CVE-2001-0823 - fixed in PCP 2.2.1 (released 21 Jun 2001)"
1700827,2017-11-10 21:22:10 UTC,"Using compat 5 isn't wrong per se, but I did notice the need to modernize the packaging, and discussed this with Eric already. Using newer packaging makes it easier to maintain the package in the long run, as new developers may not know of or understand older tricks. A promise to keep improving the setup is enough for me. :)"
1700827,2017-08-28 16:39:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700827,2017-11-04 04:11:54 UTC,"Hello Frank, Ken, and Nathan,"
1700827,2017-09-28 01:10:41 UTC,Update #2.
1700827,2017-09-27 23:28:27 UTC,Update.
1700827,2017-08-23 02:04:05 UTC,"Hi Frank, Ken;"
1700827,2017-08-29 12:46:19 UTC,"Hi Ken/Frank,"
1700827,2017-08-29 01:15:59 UTC,"On 29/08/17 10:44, Eric Desrochers wrote:

> @Dariusz, Seth, Ken, Frank and anyone else involved in this discussion.
>
> What would you guys think if we schedule a hangout call between
> Canonical & PCP upstream folks to discuss about all this ?
"
1700827,2017-08-29 00:44:54 UTC,"@Dariusz, Seth, Ken, Frank and anyone else involved in this discussion."
1700827,2017-08-29 21:55:16 UTC,"Hi all,"
1700834,2017-06-27 20:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1700834,2017-07-05 21:16:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700834,2017-07-25 15:44:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1700834,2017-08-03 16:32:17 UTC,This bug was fixed in the package linux - 4.4.0-89.112
1700834,2017-08-25 17:16:48 UTC,"I'm running Xenial with kernel 4.4.0-92.115 on a Dell R330 with intel X710 NIC.
Under load it fails with message: ""TX driver issue detected, PF reset issued"" as original report says."
1700834,2017-08-26 13:30:57 UTC,"I forgot to mention in previous comment, that this happens within the hour (usually just a few minutes) of adding the server to production loads. I can provide more information and test patches if necessary."
1700834,2017-08-28 18:30:14 UTC,"> To me it looks like this issue isn't completely solved since I'm running a more
> recent kernel than the ""fix"" was commited to.
"
1700834,2017-08-29 07:09:48 UTC,">
> There is one additional upstream commit required to fully fix this,
> please see bug 1713553.
>
"
1700841,2017-06-27 23:44:38 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1700843,2017-08-08 13:43:29 UTC,Basing on the above explanation I believe it's more of a cosmetic issue so I'm setting the Medium importance.
1700843,2017-07-20 11:42:21 UTC,"Danil, could you please provide more data? Steps to reproduce, logs, anything? So for it doesn't look solvable."
1700843,2017-07-20 15:37:35 UTC,"Denis, sure."
1700845,2017-11-17 01:13:21 UTC,I have noticed this on 18.2 and Cinnamon 3.4.6
1700846,2019-08-06 06:00:43 UTC,This bug was fixed in the package ubuntu-dev-tools - 0.170
1700846,2017-06-27 21:54:22 UTC,"Robie, can you look at this and see if you can reproduce? I see it on my bastion and on my laptop with 17.10."
1700846,2017-06-28 08:45:54 UTC,Reproduced on 16.04.
1700846,2017-06-28 10:34:51 UTC,"""pull-debian-source -d texinfo 4.8.dfsg.1-4"" also fails with a similar error."
1700846,2017-06-28 11:54:02 UTC,"However ""pull-lp-source -d texinfo 4.8.dfsg.1-4"" succeeds."
1700846,2017-06-28 15:23:22 UTC,On 17.10:
1700846,2017-06-30 10:52:07 UTC,The cause is that the original uploaded dsc contains invalid UTF-8:
1700846,2017-06-30 11:12:36 UTC,Debian policy 3.8.1.0 first mandated UTF-8 in control files in March 2009. The dsc file in question is from November 2006. So it was valid by the policy that applied at the time. This suggests that we must be able to handle non-UTF-8 correctly for historical source packages.
1700846,2017-06-30 14:37:29 UTC,"Looks like pull-debian-source already opens as binary, but pull-debian-source is still Python 2 and in that case the autodetection appears to fail. Converting pull-debian-source to Python 3 with no other direct change fixes it."
1700846,2018-03-01 16:44:52 UTC,"This problem was not that the encoding was non-utf8, python-debian correctly detects that and uses chardet to autodetect the right encoding.  That 'decoding from utf-8 failed' message is harmless."
1700846,2019-02-12 22:05:32 UTC,fixed long ago in https://code.launchpad.net/~ddstreet/ubuntu-dev-tools/+git/ubuntu-dev-tools/+ref/master
1700848,2017-10-24 10:33:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700852,2017-06-28 22:49:30 UTC,Looks like the slow code here is strip_domain_roles:
1700852,2017-06-27 22:24:33 UTC,This seems like something we should be able to fix and backport to Ocata since it has an impact on performance.
1700852,2017-08-11 02:50:19 UTC,This issue was fixed in the openstack/keystone 12.0.0.0rc1 release candidate.
1700852,2017-08-10 21:01:28 UTC,"Reviewed:  https://review.openstack.org/487143
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=63124f703a81074793360c1b91711b6ee5a76196
Submitter: Jenkins
Branch:    master"
1700852,2017-08-08 20:57:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/491921"
1700852,2017-07-25 17:11:02 UTC,"Steve, I've proposed a patch that implements caching for the API in question [0]. Let me know if that helps in any way. It might end up being a work-around until we can get some patches proposed to speed up the assignment API."
1700852,2017-08-10 02:28:49 UTC,"Reviewed:  https://review.openstack.org/491921
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9fccd38d1b177664c64bbf987a8c31d06d7cfc60
Submitter: Jenkins
Branch:    master"
1700852,2017-07-25 17:08:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/487143"
1700858,2018-04-09 20:40:49 UTC,Automatically unassigning due to inactivity.
1700870,2017-06-28 08:25:13 UTC,"Bug report related to language support are better suited for bugzilla as we focus more on the platform support. I would suggest you ping the bugzilla ticket, perhaps people didn't notice it the first time."
1700871,2019-10-19 19:36:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/689638"
1700871,2019-11-12 11:39:33 UTC,This issue was fixed in the openstack/manila 7.4.0 release.
1700871,2019-11-12 11:32:45 UTC,This issue was fixed in the openstack/manila 8.1.0 release.
1700871,2019-11-12 11:23:56 UTC,This issue was fixed in the openstack/manila 9.1.0 release.
1700871,2019-10-25 12:53:30 UTC,This issue was fixed in the openstack/manila 6.3.2 release.
1700871,2019-10-21 16:32:00 UTC,"Reviewed:  https://review.opendev.org/689638
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=71cff225b079b8d7c8f9e5dfce18bfa8e179a75b
Submitter: Zuul
Branch:    stable/queens"
1700871,2019-10-19 19:22:08 UTC,"Reviewed:  https://review.opendev.org/689607
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=8ae267e4f144e88dda9b513f104b3244c544caea
Submitter: Zuul
Branch:    stable/rocky"
1700871,2019-10-18 23:38:31 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/689607"
1700871,2019-10-17 11:55:48 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/689137"
1700871,2019-10-16 15:25:04 UTC,"Reviewed:  https://review.opendev.org/688176
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=e38c8b508ff0cd1f5ea81a0f566fd83fb0b069ce
Submitter: Zuul
Branch:    stable/train"
1700871,2019-10-11 17:02:12 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/688176"
1700871,2019-10-09 12:50:24 UTC,"Reviewed:  https://review.opendev.org/686794
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=75f108b0aee630b54a44d0c27467a85fd8a6af3a
Submitter: Zuul
Branch:    master"
1700871,2019-10-04 17:54:48 UTC,"Hi,"
1700871,2019-10-04 17:47:53 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686794"
1700871,2019-09-25 21:37:33 UTC,"Hi,"
1700871,2019-10-19 00:49:58 UTC,"Reviewed:  https://review.opendev.org/689137
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=5255ca20fb2aff3b2548475d4b7914dc02eb8bbf
Submitter: Zuul
Branch:    stable/stein"
1700878,2017-07-03 20:25:06 UTC,This seems to be a bug for XFCE. I has happened on other versions. Could you try the fix proposed down below?
1700878,2017-07-03 21:45:42 UTC,Yea I fixed it using that link but they should repair it or add a little bit of script to repair that. It seems to be a very old problem from xfce.
1700880,2017-06-28 03:44:16 UTC,Seem like this bug was fixed with the bellow patchset: https://review.openstack.org/#/c/478299/
1700880,2017-06-28 03:52:54 UTC,"Yes, this has been fixed with that patch."
1700886,2018-03-22 05:59:13 UTC,Won't be fixed for 2.2 as there are not further releases in that series planned.
1700895,2017-08-17 11:44:13 UTC,"Hi,"
1700895,2017-08-18 05:09:28 UTC,"Manjaro 64-bit, with Gnome desktop environment."
1700895,2020-07-19 06:05:38 UTC,"I guess it's a duplicate of #1690516.
I have the same issue, so I wrote there about it."
1700898,2017-06-29 02:14:03 UTC,Maybe related to the crashes in bug 1700485??
1700898,2017-06-29 06:12:54 UTC,"Daniel van Vugt (vanvugt)
I don't think so because I can log-in w/o problem when using GDM, and don't have to reboot between logins. The problem is I can only use server mode in lightDM mode"
1700904,2017-06-28 07:04:57 UTC,Addendum: the kernel is of version 4.4.0-81.
1700905,2018-03-22 05:59:47 UTC,We will not address this in 2.2 as there are no further releases planned in this series.
1700908,2020-06-22 10:02:24 UTC,"Change abandoned by Riccardo Pittau (<email address hidden>) on branch: master
Review: https://review.opendev.org/478421
Reason: obsolete, please reopen if needed"
1700908,2017-06-28 07:56:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/478421"
1700914,2017-06-28 10:06:25 UTC,Fix committed in https://git.launchpad.net/~ltsp-upstream/ltsp/+git/ltsp-manager/commit/?id=52dbff554745439671ba3673ba3db556a9c81432.
1700914,2017-06-29 08:46:31 UTC,Moving LTSP Manager bugs to the appropriate (new) project.
1700917,2017-06-29 15:41:19 UTC,"Thanks for clarifying. I think ""request manual review"" would be the thing to do, and then having a reviewer process that as usual. I don't see that revision in the review queue, so looks to me like this would put it there for us to review."
1700917,2017-07-03 10:22:00 UTC,Hi Daniel. I am a reviewer. Why is the following (seemingly) not possible:
1700917,2017-07-03 10:58:55 UTC,"I've processed Peek through, but the problem still stands (as outlined in comment #4) for other snaps."
1700917,2019-10-22 20:30:35 UTC,"Likely fixed by recent updates to review queue (well, recent - in the past 2 years or so)"
1700917,2017-06-28 13:17:08 UTC,Hello!
1700917,2017-06-29 15:14:19 UTC,"Apologies Daniel, I should have provided more context."
1700921,2017-06-28 08:37:30 UTC,Note that this bug report was created on another desktop Ubuntu install. The block devices on this computer do not match the bug report.
1700921,2017-06-28 09:48:13 UTC,"Note: ""Installing mdadm package from Ubuntu 16.10 fixes the problem."" is probably incorrect. It seems that the above steps cause boot to fail even aftern installing mdadm version 3.4."
1700921,2017-06-28 09:55:28 UTC,Possible cause: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070#49
1700921,2017-06-28 10:10:46 UTC,See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781172#35
1700927,2018-01-12 19:07:11 UTC,Unassigning due to no activity for > 6 months.
1700927,2017-06-28 09:20:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/478447"
1700935,2017-06-28 14:51:43 UTC,"Thanks TylerDurden. When I looked at your screenshot, I recognized the following:"
1700935,2017-06-28 20:01:31 UTC,"Please note that the ""CMYK"" tab is just a sRGB approximation of the color, you have to use the ""CMS"" (color-managed system) to get ""real"" CMYK colors."
1700935,2020-09-21 11:04:21 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1700935,2017-06-28 12:34:18 UTC,"Duplicated with Win8.1-64, Inkscape 0.92.1 r15371."
1700937,2017-07-07 19:01:41 UTC,"@seth There's an error regarding the SQLite version number in the CVE text. It should read ""in SQLite before 3.17.0"" (and not 3.11.0)"
1700937,2017-07-14 19:23:59 UTC,"Even, we've triaged this as a 'low' priority for our team: https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-10989.html -- it might be a while before fixes are released."
1700937,2017-07-14 16:53:23 UTC,Will there be a security package with the patch ?
1700937,2017-07-07 20:17:53 UTC,"On Fri, Jul 07, 2017 at 07:01:41PM -0000, Even Rouault wrote:

> @seth There's an error regarding the SQLite version number in the CVE
> text. It should read ""in SQLite before 3.17.0"" (and not 3.11.0)
"
1700937,2017-07-07 18:25:59 UTC,Use CVE-2017-10989.
1700937,2017-07-01 15:46:12 UTC,"Update from our exchanges with Richard Hipp, SQLite3 developper"
1700937,2017-07-06 08:23:52 UTC,"The attachment ""Proposed patch to apply on top of sqlite 3.11.0"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1700937,2017-06-29 00:42:35 UTC,"Hello Even, thanks for this. There's a lot of complexity in that patch, and the commit message includes ""This is a work in progress"". I'm not sure we should just apply this patch ourselves without further interaction with SQLite3 developers."
1700937,2017-06-28 11:19:53 UTC,"I've run git bisect on the https://github.com/mackyle/sqlite mirror of sqlite3 source code repository and spotted that the following commit fixes the issue :
https://github.com/mackyle/sqlite/commit/ce015fb42bbb6cafdbfc9b028c2ec0626a8f3217"
1700937,2017-06-30 15:33:08 UTC,@seth-arnold Who does engage with SQLite3 developers: you/your team ?
1700937,2017-07-01 02:30:44 UTC,"Even, I just mailed some questions to http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users -- hopefully they'll have some advice."
1700937,2017-06-29 06:10:27 UTC,"I agree the patch is complex (I don't understand it, just blindly git bisected and applied it), the commit message doesn't specifically mention addressing database corruption (the fact it fixes the bug seems to be a side-effect) and should be vetted by SQLite3 developers. OSS-Fuzz has a 90 day deadline period (https://github.com/google/oss-fuzz/), starting yesterday."
1700940,2017-06-28 09:38:22 UTC,Attachment: After resizing the ruler.
1700947,2017-06-28 17:00:03 UTC,"Yup, known issue.  If the outline happens to touch all four edges, it can't figure out the shape.  Just remove the outline from the outline layer and it should work - the default outline is the ""whole board"" like you already have."
1700947,2017-07-30 16:14:52 UTC,"Hi Yu - Sian and DJ,"
1700949,2017-06-28 14:23:52 UTC,"Oddly enough, the official man page at http://ipset.netfilter.org/iptables.man.html is also lacking such information! :-("
1700949,2017-06-28 14:40:42 UTC,"The only mention is within the ""Packetfilter HOWTO"" at the chapter ""7.3 Filtering specification"".
See http://iptables.netfilter.org/documentation/HOWTO/packet-filtering-HOWTO-7.html"
1700949,2017-06-28 14:13:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1700950,2017-06-28 10:30:07 UTC,This change was made by a bot.
1700950,2017-07-06 00:09:26 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1700950,2017-07-06 11:38:59 UTC,"Confirmed, fixed upstream."
1700951,2017-06-28 11:09:50 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1700951,2017-06-28 12:29:12 UTC,I don't have this slide on in my latest merge but it was not taken in time I guess.
1700955,2017-06-28 21:53:54 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1700963,2018-09-21 14:48:31 UTC,Still exist in Ubuntu 18.04.
1700963,2020-04-23 21:44:32 UTC,Still broken in Ubuntu 19.10. But easy enough to install with: pip install ViTables
1700963,2017-06-28 13:55:57 UTC,Bug confirmed upstream. Also a patch is already available https://github.com/uvemas/ViTables/commit/a7dc69420ef48d7e20e3ee46d3d9b730785531c7
1700963,2017-10-27 13:41:04 UTC,I'm using Ubuntu 17.10 and this still seems to be an issue. vitables 2.1-1 included with Ubuntu 17.10 is incompatible with the pytables 3.3.0.
1700972,2017-09-01 08:27:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1700972,2018-01-09 19:07:33 UTC,This bug was fixed in the package linux-azure - 4.13.0-1005.7
1700972,2017-11-02 15:34:56 UTC,This bug was fixed in the package linux-aws - 4.4.0-1002.2
1700972,2017-09-18 14:05:46 UTC,This bug was fixed in the package linux-aws - 4.4.0-1035.44
1700972,2017-09-18 12:57:24 UTC,This bug was fixed in the package linux - 3.13.0-132.181
1700972,2017-09-18 10:13:40 UTC,This bug was fixed in the package linux-gke - 4.4.0-1031.31
1700972,2017-09-18 10:11:08 UTC,This bug was fixed in the package linux - 4.4.0-96.119
1700972,2017-09-18 09:21:44 UTC,This bug was fixed in the package linux - 4.10.0-35.39
1700972,2017-09-01 08:28:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1700972,2017-09-01 08:26:06 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1700972,2017-07-26 14:52:33 UTC,And linux-gke in particular is used *only* in images that boot without initrd.
1700972,2017-08-07 13:48:33 UTC,Patches for aws/gcp/gke/kvm/T/X/Z/A:
1700972,2017-07-26 21:35:36 UTC,"On Wed, Jul 26, 2017 at 09:15:33PM -0000, Marcelo Cerri wrote:

> Steve, any reason to also include ""linux""?
"
1700972,2017-07-26 21:15:33 UTC,"Steve, any reason to also include ""linux""?"
1700972,2017-07-26 21:14:03 UTC,"> That is incorrect.  We are in the process of building images for *all*
> cloud targets that boot without initrd.
"
1700972,2017-07-26 15:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1700972,2017-06-28 13:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1700972,2017-07-26 14:51:49 UTC,"> Currently linux-azure is the only kernel that actually has an use case
> that requires it to boot without an initrd.
"
1700972,2017-07-26 14:41:09 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-July/085941.html
1700972,2017-07-26 12:42:07 UTC,Currently linux-azure is the only kernel that actually has an use case that requires it to boot without an initrd.
1700972,2017-08-16 07:46:08 UTC,This bug was fixed in the package linux - 4.12.0-11.12
1700972,2017-06-28 14:16:45 UTC,I believe log files are not needed here.
1700983,2017-06-29 19:12:27 UTC,"As stupid as this may sound, I've found out the following:"
1700988,2017-06-28 14:26:07 UTC,"StacktraceTop:
 Digikam::BdEngineBackendPrivate::ErrorLocker::wait (this=this@entry=0x7f51a948e540) at ./core/libs/database/engine/dbenginebackend.cpp:566
 Digikam::BdEngineBackendPrivate::ErrorLocker::wait (this=this@entry=0x7f51a948e540) at ./core/libs/database/engine/dbenginebackend.cpp:566
 Digikam::BdEngineBackendPrivate::ErrorLocker::wait (this=this@entry=0x7f51a948e540) at ./core/libs/database/engine/dbenginebackend.cpp:566
 Digikam::BdEngineBackendPrivate::ErrorLocker::wait (this=this@entry=0x7f51a948e540) at ./core/libs/database/engine/dbenginebackend.cpp:566
 Digikam::BdEngineBackendPrivate::ErrorLocker::wait (this=this@entry=0x7f51a948e540) at ./core/libs/database/engine/dbenginebackend.cpp:566"
1700991,2017-09-28 10:57:50 UTC,How did you install imagej and the 3d viewer? The 3d viewer is an ImageJ plugin and is not part of the ImageJ package in Ubuntu.
1700992,2017-06-28 14:32:57 UTC,This looks like it'll be fixed with a sync from Debian; -2 has the fix.
1700992,2017-06-28 14:46:47 UTC,Confirmed by an upstream bug
1700999,2020-08-04 11:32:39 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/744681"
1700999,2020-08-07 04:10:22 UTC,"This is not an issue on the master branch, so marking it as Invalid for master."
1700999,2020-08-04 07:54:41 UTC,"Change abandoned by Harshavardhan Metla (<email address hidden>) on branch: master
Review: https://review.opendev.org/737215
Reason: since the change needs to be done on openstack-manuals and older verions"
1700999,2020-06-25 18:20:28 UTC,"Change abandoned by Harshavardhan Metla (<email address hidden>) on branch: master
Review: https://review.opendev.org/738081"
1700999,2020-06-25 18:19:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/738081"
1700999,2017-07-04 12:28:02 UTC,"The content in question is being moved to the nova repository, see https://review.openstack.org/#/c/477488/."
1700999,2020-06-22 05:56:57 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/737215"
1700999,2020-07-31 15:10:33 UTC,"This bug is from 2017 and affects only older releases: Rocky, Queens, Pike so I'm setting the importance to Low."
1701000,2018-01-16 15:54:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701011,2017-09-28 21:13:47 UTC,"Maybe I'm misunderstanding which API you are referring to, but isn't that available with this?"
1701018,2019-10-29 18:14:37 UTC,Two of the three pull requests referenced by the last comment are still open. One has been closed.
1701018,2017-12-08 16:04:31 UTC,"https://github.com/snapcore/pi2-gadget/pull/9
and
https://github.com/snapcore/pi3-gadget/pull/13"
1701018,2017-07-27 15:54:08 UTC,"yes, i'm working on a solution where the splash actually gets created during the gadget build and loaded into the initrd on boot via a uboot script snippet, then it will show on first boot too ... (this will still take some time though, but a proper solution is in the works (the above was just a proof of concept))"
1701018,2017-07-27 13:00:20 UTC,Hi. I tested this solution and it works great (not ideal as splash shows up after few seconds but that's details). But I ran into one big issue with this. When creating image with ubuntu-image and this snap built in on the first boot there is no splash screen. And that's when people would want to see it the most. I assume that's because splash screen snap is getting set up on the first boot as well. Any possible way to fix this?
1701018,2017-07-12 14:35:30 UTC,and this is my cmdline:
1701018,2017-07-13 09:40:32 UTC,"yes, i see exactly the same, but everything works just fine if i drop the dtb overlay from  config.txt ..."
1701018,2017-07-06 11:46:00 UTC,https://github.com/respeaker/openwrt/blob/master/target/linux/brcm2708/patches-4.4/0337-drm-vc4-Kick-out-the-simplefb-framebuffer-before-we-.patch might be of help with the dtoverlay bit
1701018,2017-07-03 14:01:33 UTC,above is an initrd.img with the psplash binary included. to test it you can just replace the exiting initrd.img on your SD (in /boot/uboot/<kernel_snap>/initrd.img)
1701018,2017-06-30 15:00:48 UTC,i think we are better off with completely quietening u-boot and kernel and shipping some very minimal splash inside the initrd (which the upcoming split-initrd model will allow easily by simply having the gadget ship a splash.img cpio archive)
1701018,2017-06-29 08:38:08 UTC,"Right, when enabling the framebuffer boot logo (CONFIG_LOGO), you hardcode a bitmap that will be showed up during every boot, and it'll be the same bitmap for everyone - i don't think there's a way to enable splash screen support and then make it generic enough so every can make customize / use it."
1701018,2017-06-28 17:15:29 UTC,"i subscribed paolo to this bug, perhaps he has any idea how to not hardcode a binary splash inside the kernel, but to my knowledge the only way to use an in-kernel splash is to build the bitmap you want to display directly into the kernel binary (essentially by enabling the penguin logo in the build config and replacing the bitmap for it)"
1701018,2017-06-28 17:09:39 UTC,traditionally ubuntu uses plymouth for splash screens and completely disables any kernel messages ...
1701018,2017-07-12 14:33:54 UTC,"The patch mentioned in #7 is already present in the kernel we ship, though i found something different (by testing this on ubuntu classic):"
1701022,2017-09-26 19:14:53 UTC,The problem appears to be a conflict between the dependency on devise-two-factor version 2.0.0 and the current version of devise-two-factor (3.0.0 on my system) It occurs when installing using sudo apt-get as well as synaptic and the software manager.
1701023,2018-05-10 21:00:34 UTC,I sent an email to ubuntu-server list requesting anyone with vlan ifupdwon config to give these -proposed pkgs a test.
1701023,2018-05-10 15:03:53 UTC,"Hello Sven, or anyone else affected,"
1701023,2018-05-10 14:22:41 UTC,"Hello Sven, or anyone else affected,"
1701023,2018-05-10 14:20:45 UTC,"Hello Sven, or anyone else affected,"
1701023,2018-05-10 14:18:27 UTC,"Hello Sven, or anyone else affected,"
1701023,2018-05-10 14:17:03 UTC,"Hello Sven, or anyone else affected,"
1701023,2018-05-07 13:19:03 UTC,@ddstreet - could we get the SRU template information included in this bug?
1701023,2018-05-07 21:15:50 UTC,">  I would feel better if a wider call-for-testing could be done on these packages
> in bionic-proposed
"
1701023,2018-05-07 16:14:30 UTC,"Seeing that the previous change caused regressions, I would feel better if a wider call-for-testing could be done on these packages in bionic-proposed, performing tests on various different configurations."
1701023,2018-05-07 16:13:30 UTC,"Hello Sven, or anyone else affected,"
1701023,2018-05-07 16:10:14 UTC,"Hello Sven, or anyone else affected,"
1701023,2018-05-07 15:44:25 UTC,"> could we get the SRU template information included in this bug?
"
1701023,2018-05-10 14:11:44 UTC,"Hello Sven, or anyone else affected,"
1701023,2018-05-15 18:16:20 UTC,This bug was fixed in the package vlan - 1.9-3.2ubuntu6
1701023,2018-05-24 07:44:00 UTC,This bug was fixed in the package vlan - 1.9-3.2ubuntu5.17.10.1
1701023,2018-05-17 20:53:45 UTC,tested on artful with:
1701023,2018-05-17 20:59:32 UTC,xenial:
1701023,2018-05-18 20:49:07 UTC,trusty:
1701023,2018-05-24 07:21:15 UTC,I think this aged long enough in -proposed - releasing.
1701023,2018-05-24 07:21:43 UTC,This bug was fixed in the package vlan - 1.9-3.2ubuntu6
1701023,2018-05-24 07:21:47 UTC,"The verification of the Stable Release Update for vlan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1701023,2018-05-24 07:21:50 UTC,This bug was fixed in the package ifupdown - 0.8.17ubuntu1.1
1701023,2018-05-24 07:44:07 UTC,This bug was fixed in the package ifupdown - 0.8.16ubuntu2.1
1701023,2018-05-24 07:46:33 UTC,This bug was fixed in the package vlan - 1.9-3.2ubuntu1.16.04.5
1701023,2018-05-24 07:46:37 UTC,This bug was fixed in the package ifupdown - 0.8.10ubuntu1.4
1701023,2018-05-24 07:47:27 UTC,This bug was fixed in the package vlan - 1.9-3ubuntu10.6
1701023,2018-05-24 07:47:31 UTC,This bug was fixed in the package ifupdown - 0.7.47.2ubuntu4.5
1701023,2020-07-14 15:39:21 UTC,"removing sts tag, as this is still marked new for vlan in debian; any vlan delta to debian should be handled elsewhere and is more than this bug's patches."
1701023,2018-05-17 20:46:57 UTC,tested bionic per comment 19 with:
1701023,2018-05-01 10:28:47 UTC,"> Neither issue is fixed by the downgrade
"
1701023,2018-04-25 12:50:39 UTC,"Debian's included a variation of my patch to ifupdown, so I'll update my ppa to use that patch instead and do some testing, then start sru'ing both ifupdown and vlan."
1701023,2018-04-30 12:14:45 UTC,"> We migrated from separate files in /etc/networking/interfaces.d to just declaring
> everything in the single /etc/networking/interfaces file. This overcomes a lot of
> issues with regards to bringing interfaces up in the proper order and ""ifup -a""
> now works perfectly again
"
1701023,2018-05-01 10:10:07 UTC,"Neither issue is fixed by the downgrade. As said, neither seems to have to do with vlan but with ifupdown."
1701023,2017-08-03 12:53:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701023,2017-09-04 03:12:50 UTC,"Note: This behavior is in direct violation of the Debian documentation: https://wiki.debian.org/NetworkConfiguration#Bringing_up_an_interface_without_an_IP_address
Specifies:
Note: If you create the VLAN interface only to put it into a bridge, there is no need to define the VLAN interface manually. Just configure the bridge, and the VLAN interface will be created automatically when creating the bridge (see below)."
1701023,2017-10-11 11:47:17 UTC,"Can we get someone to fix this policy violation, please?"
1701023,2018-01-20 03:01:54 UTC,This diff resulted in the boot breaking again: http://launchpadlibrarian.net/324174495/vlan_1.9-3ubuntu10.1_1.9-3ubuntu10.4.diff.gz - reverting the change fixed the issue.
1701023,2018-01-20 03:02:55 UTC,"Apologies, I had my versions screwed up. Disregard my previous comment."
1701023,2018-04-05 14:46:42 UTC,"The changelog since 10.1 mentions #1573272 three times, looks like that was a tough nut to crack. I'm subscribing ddstreet for consideration."
1701023,2018-04-06 12:39:27 UTC,"Well I can't say I'm too surprised that something broke, the ifupdown<->vlan<->udev love triangle of creating and configuring vlans, is a bit of a mess.  I'll take a look at this as soon as I have a chance."
1701023,2018-04-10 18:17:46 UTC,I reproduced this hang on trusty and I'm investigating.
1701023,2018-04-11 11:13:16 UTC,"@smu-u can you please test with the vlan pkg from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023"
1701023,2018-04-11 11:38:27 UTC,"It appears this ifupdown locking issue doesn't happen in Xenial, but I'll do more testing to confirm that."
1701023,2018-04-13 12:57:56 UTC,"marking this as affecting T/X/A/B, although I need to specifically check each."
1701023,2018-04-13 13:01:01 UTC,"from bug 1759573, looks like this does affect X as well as T."
1701023,2018-04-19 15:27:53 UTC,"This bug is caused in two different ways, both not directly from ifupdown or vlan, but instead because of 'helpful' actions in the ifenslave and bridge-utils if-pre-up scripts."
1701023,2018-04-19 15:51:46 UTC,"The reason the if-pre-up.d/vlan script was changed to call ifup for its raw-device, was for bug 1573272, where the problem was a race condition between the VLAN and its raw-device; if the VLAN interface was processed through if-pre-up.d/vlan before the raw-device was fully configured, then in some situations (such as if the raw-device is a bond device) the raw-device is brought down during its ifup processing (usually in order to set some device params that can't be set while the interface is up).  When the raw-device is taken down, the VLAN also goes down, and any routing or other associated configuration is lost, such as a default gateway.  When the raw-device comes back up, the VLAN comes up as well, but the (e.g.) default gateway is not restored, since the VLAN interface does not go through ifup again."
1701023,2018-04-19 19:49:14 UTC,The reason that udev calls /lib/udev/vlan-network-interface is because of hotplugging.
1701023,2018-04-20 13:16:20 UTC,There are 3 test cases here to verify this:
1701023,2018-04-19 22:30:44 UTC,"Anyone experiencing this bug, can you please test with the vlan package from this test ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023"
1701023,2018-04-30 10:10:44 UTC,"Hi @ddstreet. Completely understand your need to limit the scope of this bug. Just shared our findings, but feel free to ignore the stuff in #28 under item 2. We did a lot of extensive testing over the weekend with the latest version of your PPA package and here are our main findings:"
1701023,2018-04-26 16:13:00 UTC,"> Unfortunately it turns out this change does not fix the issue of interfaces not
> coming up correctly for a bond with a (static) network configuration
"
1701023,2018-04-26 14:35:06 UTC,We've been doing a lot more testing and debugging and I'd like to share our findings:
1701023,2018-04-23 21:29:04 UTC,"> @ddstreet tested with the latest version of ifupdown and vlan from your PPA with
> my 4 testscenario's and can confirm it works as expected. Interfaces come up
> correctly both when doing an ""ifup -a"" and during boot.
"
1701023,2018-04-21 10:53:21 UTC,"@ddstreet tested with the latest version of ifupdown and vlan from your PPA with my 4 testscenario's and can confirm it works as expected. Interfaces come up correctly both when doing an ""ifup -a"" and during boot."
1701023,2018-04-27 19:11:55 UTC,"I updated the ifupdown pkg builds in my test ppa using the upstream (debian) patch, which is a variation of my previous patch.  Anyone affected by this regression please test with the latest ifupdown and vlan pkgs from my ppa."
1701023,2018-04-20 19:07:51 UTC,"Also re: testcase 3, I could only reproduce it on reboot and ifup -a; it did not fail when i tried hotplugging the interface (modprobing its driver)."
1701023,2018-04-20 19:01:23 UTC,"@smu-u, please do let me know if you are seeing this issue in X/A/B. Otherwise, I'll assume you only see this issue in trusty, which matches what I found."
1701023,2018-04-20 19:00:06 UTC,"For testcase 3, from this bug, I'm able to reproduce it on trusty using vlan 1.9-3ubuntu10.5, and using the pkg from my ppa it is fixed."
1701023,2018-04-20 18:38:48 UTC,"For testcase 2, from bug 1759573, I can't reproduce the reported hang from that bug."
1701023,2018-04-20 17:41:05 UTC,"Test case #1 (bug 1573272), part (a) and (b) only:"
1701023,2018-04-20 13:18:29 UTC,"Also, for each of those test cases, this fix needs to be tested for:"
1701023,2018-04-20 20:43:12 UTC,"Test pkgs for both ifupdown and vlan available in this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023"
1701028,2017-07-01 16:13:40 UTC,Thanks for providing the additional information.
1701028,2017-06-29 17:53:43 UTC,The 14.04 version of jacksum is working without any issues.
1701028,2017-06-29 17:51:49 UTC,apport information
1701028,2017-06-29 16:59:41 UTC,apport information
1701028,2017-06-29 16:59:42 UTC,apport information
1701028,2017-06-29 16:59:40 UTC,apport information
1701028,2017-06-29 16:59:39 UTC,apport information
1701028,2017-06-28 19:28:38 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1701028,2017-06-29 17:51:48 UTC,apport information
1701032,2017-07-12 20:57:37 UTC,"This is not Rally problem, none code changes in Rally required."
1701032,2017-07-06 13:46:10 UTC,"Hi,"
1701032,2017-07-06 14:28:28 UTC,"Hi all,"
1701032,2017-06-29 14:06:03 UTC,"Hi,"
1701032,2017-06-29 13:34:17 UTC,"Hi,"
1701032,2017-06-29 13:04:17 UTC,"Hi Alfredo,"
1701032,2017-07-06 07:51:37 UTC,"hi, if your problem is resolved, can you run rally again? i want to confirm whether it is bug of rally."
1701032,2017-06-29 08:47:53 UTC,could you upload packstack answers file and following log files:
1701047,2019-05-17 09:56:00 UTC,"fonts-telu-extra is mentioned at https://bugs.debian.org/854163, but it does not seem to suffer from the same issue as the other ones. Dropping the fonts-telu-extra tasks."
1701047,2018-06-25 08:59:42 UTC,This bug was fixed in the package fonts-orya-extra - 2.0-5ubuntu0.1
1701047,2018-06-25 08:59:36 UTC,This bug was fixed in the package fonts-beng-extra - 1.0-6ubuntu0.1
1701047,2018-06-25 08:59:33 UTC,This bug was fixed in the package fonts-deva-extra - 3.0-4ubuntu0.1
1701047,2018-06-21 07:48:37 UTC,"The verification of the Stable Release Update for fonts-guru-extra has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1701047,2018-06-21 07:48:32 UTC,This bug was fixed in the package fonts-guru-extra - 2.0-4ubuntu0.1
1701047,2018-06-16 06:29:35 UTC,Verified the test case using these packages from bionic-proposed:
1701047,2018-06-16 04:42:19 UTC,"Hello Gunnar, or anyone else affected,"
1701047,2018-06-16 04:41:24 UTC,"Hello Gunnar, or anyone else affected,"
1701047,2018-06-16 04:40:33 UTC,"Hello Gunnar, or anyone else affected,"
1701047,2018-06-25 08:59:39 UTC,This bug was fixed in the package fonts-gujr-extra - 1.0-6ubuntu0.1
1701047,2018-06-16 04:35:59 UTC,"Hello Gunnar, or anyone else affected,"
1701047,2018-06-16 04:39:32 UTC,Fix confirmed with the bionic-proposed version of fonts-guru-extra.
1701047,2018-06-07 16:03:30 UTC,Fixed in 2.0-4ubuntu1 for cosmic.
1701047,2018-06-07 16:18:55 UTC,"Of these packages, fonts-guru-extra is the only one that in practice I see is affected by this bug on a continuously-upgraded system (16.04 -> 16.10 -> 17.04 -> 17.10 -> 18.04), so is the only package I am currently intending to SRU."
1701047,2018-06-07 17:55:45 UTC,"@Steve: fonts-guru-extra affects everyone, since fonts-guru is in desktop-common in Xenial, and thus is indeed the most important package to fix."
1701047,2018-06-07 19:05:58 UTC,"On Thu, Jun 07, 2018 at 05:55:45PM -0000, Gunnar Hjalmarsson wrote:"
1701047,2018-06-09 22:32:32 UTC,This bug was fixed in the package fonts-beng-extra - 1.0-6ubuntu1
1701047,2018-06-09 22:32:25 UTC,This bug was fixed in the package fonts-deva-extra - 3.0-4ubuntu1
1701047,2018-06-09 22:32:27 UTC,This bug was fixed in the package fonts-gujr-extra - 1.0-6ubuntu1
1701047,2018-06-09 22:32:35 UTC,This bug was fixed in the package fonts-orya-extra - 2.0-5ubuntu1
1701047,2018-06-07 19:50:51 UTC,"But when did you install the other packages? I suspect that you did so when upgrading to 17.10, where fonts-indic was added to ubuntu-desktop. In that case you never had the Xenial version of those packages which may explain why you didn't stumble upon the upgrade issue for those."
1701047,2018-06-14 09:28:18 UTC,"Hello Gunnar, or anyone else affected,"
1701049,2017-10-20 23:02:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701061,2019-01-07 11:13:50 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/482887
Reason: Marking this review as abandoned due to lack of activity in the past 6 months."
1701061,2017-07-12 11:32:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/#/c/482887/"
1701061,2017-07-11 13:47:08 UTC,"Right, we should definitely do something about the cluster name other than leaving it at the value set when the cluster was first created."
1701061,2017-07-04 13:08:44 UTC,"But still, I am not quite sure I see how not updating the RabbitMQ cluster_name relates to the changes made to fix bug 1691510."
1701061,2017-07-04 15:55:33 UTC,"On Tue, 04 Jul 2017 09:21:25 -0000
Frode Nordahl <email address hidden> wrote:"
1701061,2017-07-04 12:30:53 UTC,I think this test proves the contrary - http://pastebin.ubuntu.com/25017990/ i.e. that the amulet tests are not picking up the cluster_name.
1701061,2017-07-04 09:21:25 UTC,"DEBUG:runner:Cluster status of node 'rabbit@juju-4d268d-auto-osci-sv06-16' ...
DEBUG:runner:[{nodes,[{disc,['rabbit@juju-4d268d-auto-osci-sv06-15',
DEBUG:runner:                'rabbit@juju-4d268d-auto-osci-sv06-16']}]},
DEBUG:runner: {running_nodes,['rabbit@juju-4d268d-auto-osci-sv06-15',
DEBUG:runner:                 'rabbit@juju-4d268d-auto-osci-sv06-16']},
DEBUG:runner: {cluster_name,<<""rabbit@juju-4d268d-auto-osci-sv06-17"">>},
DEBUG:runner: {partitions,[]}]
DEBUG:runner:['Cluster registration check failed on rabbitmq-server/6: rabbit@juju-4d268d-auto-osci-sv06-17 should not be registered with RabbitMQ after unit removal.\n']
DEBUG:runner:Exit Code: 1"
1701061,2017-06-29 11:07:08 UTC,"Hi Frode, there are actually two issues at play here. The amulet error that you've pasted above is a result of a race condition whereby the removed unit reference has not yet been removed from rabbitmq cluster_status at the time amulet does the poll. It does however get removed eventually so its really just a timing thing. The second issue, which you allude to in your comments above is potentially more serious and is the fact that if we remove the unit that was set as the leader_node_hostname which is represented in ""cluster_name"", that name is never updated to be that of the new leader and that in turn likely messes with the code that you reference above which was added as a fix for bug 1691510."
1701061,2017-06-28 19:53:06 UTC,Note to self: Review in context with https://github.com/openstack/charm-rabbitmq-server/commit/6a66fd16124c60d056fc710c1f47df6855c8ba1e#diff-21870f9ed3cd89ae3ca8d1f237afc315R422
1701061,2017-06-28 19:26:04 UTC,"The root cause may be that the registration check and or regex is too wide and matches on the cluster_name row? That check should really just hit on nodes listed after ""nodes"". I'll dig into that too and see what shows up."
1701061,2017-07-04 13:01:09 UTC,"Right you are, now that is what you get for not quoting the whole context of the log output:
DEBUG:runner:2017-06-16 23:48:29,193 get_unit_hostnames DEBUG: Unit host names: {'rabbitmq-server/6': 'juju-4d268d-auto-osci-sv06-15', 'rabbitmq-server/7': 'juju-4d268d-auto-osci-sv06-16'}
DEBUG:runner:2017-06-16 23:48:34,445 run_cmd_unit DEBUG: rabbitmq-server/6 `rabbitmqctl cluster_status` command returned 0 (OK)
DEBUG:runner:2017-06-16 23:48:34,446 get_rmq_cluster_status DEBUG: rabbitmq-server/6 cluster_status:
DEBUG:runner:Cluster status of node 'rabbit@juju-4d268d-auto-osci-sv06-15' ...
DEBUG:runner:[{nodes,[{disc,['rabbit@juju-4d268d-auto-osci-sv06-15',
DEBUG:runner: 'rabbit@juju-4d268d-auto-osci-sv06-16',
DEBUG:runner: 'rabbit@juju-4d268d-auto-osci-sv06-17']}]},
DEBUG:runner: {running_nodes,['rabbit@juju-4d268d-auto-osci-sv06-16',
DEBUG:runner: 'rabbit@juju-4d268d-auto-osci-sv06-17',
DEBUG:runner: 'rabbit@juju-4d268d-auto-osci-sv06-15']},
DEBUG:runner: {cluster_name,<<""rabbit@juju-4d268d-auto-osci-sv06-17"">>},
DEBUG:runner: {partitions,[]}]
DEBUG:runner:2017-06-16 23:48:39,713 run_cmd_unit DEBUG: rabbitmq-server/7 `rabbitmqctl cluster_status` command returned 0 (OK)
DEBUG:runner:2017-06-16 23:48:39,713 get_rmq_cluster_status DEBUG: rabbitmq-server/7 cluster_status:
DEBUG:runner:Cluster status of node 'rabbit@juju-4d268d-auto-osci-sv06-16' ...
DEBUG:runner:[{nodes,[{disc,['rabbit@juju-4d268d-auto-osci-sv06-15',
DEBUG:runner: 'rabbit@juju-4d268d-auto-osci-sv06-16']}]},
DEBUG:runner: {running_nodes,['rabbit@juju-4d268d-auto-osci-sv06-15',
DEBUG:runner: 'rabbit@juju-4d268d-auto-osci-sv06-16']},
DEBUG:runner: {cluster_name,<<""rabbit@juju-4d268d-auto-osci-sv06-17"">>},
DEBUG:runner: {partitions,[]}]
DEBUG:runner:['Cluster registration check failed on rabbitmq-server/6: rabbit@juju-4d268d-auto-osci-sv06-17 should not be registered with RabbitMQ after unit removal.\n']
DEBUG:runner:Exit Code: 1"
1701061,2017-07-04 09:26:45 UTC,The code used in the test was stolen from get_rmq_cluster_running_nodes function in charm-helpers (charmhelpers/contrib/openstack/amulet/utils.py)
1701062,2017-07-26 17:05:06 UTC,"Paul Meyer gave example on how to launch and find ""latest"" image via the sku/urn [1]"
1701062,2017-10-11 18:12:40 UTC,"I'm annoyed by this again, trying to launch a ""latest ubuntu""."
1701062,2017-10-11 18:43:30 UTC,"On Wed, Oct 11, 2017 at 06:12:40PM -0000, Scott Moser wrote:

> I'm annoyed by this again, trying to launch a ""latest ubuntu"".
>
> The data that you can get from
>  $ az vm image list --all --publisher=Canonical | pastebinit
>  http://paste.ubuntu.com/25721526/
>
> Its basically unusable.
> In order to launch something by its sku, you have to:
>  a.) know if the release you're interested in is LTS (12.04.3-LTS versus 17.04)
>  b.) know the latest point version of that if it is an LTS.
>
> Can we please get stream data that gets us these 'urn' ?
"
1701065,2017-06-28 20:57:02 UTC,"Hi Jeremy,"
1701065,2017-06-28 22:06:41 UTC,"Axel, thank you for your comment."
1701079,2018-01-21 12:57:42 UTC,I was also hit an error with following command:
1701079,2018-02-08 02:17:16 UTC,Im hitting same problem:here is my ticket with more information: https://bugs.launchpad.net/python-openstackclient/+bug/1747721
1701081,2017-06-30 20:23:51 UTC,apport information
1701081,2017-06-30 20:23:42 UTC,apport information
1701081,2017-08-02 20:37:45 UTC,"I tested this for a while to be sure of the results. It appears that with the mainline kernel 4.13.0-041300rc1-generic resuming from hibernate works perfectly without the need to add the ""acpi_osi=Linux"" kernel boot parameter. It worked correctly and reliably 100% of the times I tried it (even repeatedly without a full shutdown)."
1701081,2017-07-05 23:24:44 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1701081,2017-06-30 20:24:10 UTC,apport information
1701081,2017-06-30 20:24:05 UTC,apport information
1701081,2017-06-30 20:23:59 UTC,apport information
1701081,2017-06-30 20:23:55 UTC,apport information
1701081,2017-06-30 20:23:54 UTC,apport information
1701081,2017-06-30 20:23:52 UTC,apport information
1701081,2017-06-30 20:23:50 UTC,apport information
1701081,2017-08-02 20:59:39 UTC,"Sorry, in my previous comment I meant 4.4.0-83 Ubuntu kernel."
1701081,2017-06-30 20:23:47 UTC,apport information
1701081,2017-06-30 20:23:46 UTC,apport information
1701081,2017-06-30 20:23:45 UTC,apport information
1701081,2017-06-30 20:23:43 UTC,apport information
1701081,2017-06-30 20:23:43 UTC,apport information
1701081,2017-06-30 20:23:41 UTC,apport information
1701081,2017-06-30 20:23:38 UTC,apport information
1701081,2017-06-28 20:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1701081,2017-06-30 20:23:49 UTC,apport information
1701082,2017-07-03 08:53:24 UTC,"Hi Simar,"
1701082,2017-07-05 20:11:03 UTC,"Hi Dharmendra,"
1701082,2017-07-05 22:02:02 UTC,this should be an environment since our CI is working.
1701082,2017-07-05 22:14:34 UTC,"Hi Yong,"
1701086,2019-08-02 04:17:26 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1701086,2017-07-03 19:34:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701086,2019-06-02 11:51:42 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1701102,2019-09-25 21:03:39 UTC,I have been attempting to preseed install 19.10 (eoan) and discovered that this fix has not yet made its way into Ubuntu yet. Does anyone have any idea when the fix is likely to make it in? Would be nice if it was available in LTS (18.04) as well.
1701102,2017-06-28 22:28:10 UTC,https://anonscm.debian.org/git/d-i/partman-auto-raid.git/commit/?id=d851cf0f7c5926b9ceb6208bf6464d85fbce9237
1701102,2017-06-28 22:26:16 UTC,"I knew that clone-and-hack I did in partman-auto-raid would come back to bite me eventually.  The partman-auto-lvm change was https://bugs.debian.org/610377, so I'll adopt that change here too."
1701105,2017-06-28 22:28:26 UTC,Assigned to nova also since the guides are going to move out of manuals and into the project repos.
1701139,2017-06-30 18:32:56 UTC,"Reviewed:  https://review.openstack.org/478341
Committed: https://git.openstack.org/cgit/openstack/omni/commit/?id=7823d3ddb479b7aa6855ceb20f9360765abbe677
Submitter: Jenkins
Branch:    master"
1701145,2017-06-29 02:09:45 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1701146,2017-06-29 03:09:02 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1701156,2017-07-20 08:34:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/485491"
1701156,2017-07-10 05:44:00 UTC,"Hi,"
1701164,2017-06-29 06:03:41 UTC,Can this be bound to the quantize button?
1701164,2017-06-29 19:29:11 UTC,It seems what is really being requested here is quantizing the deactivation of slip mode. Doing that correctly for rolling loops might be a little more complicated than in the general case of turning off slip mode.
1701164,2017-06-30 04:21:16 UTC,"related:
Enable quantization/synchronization of user actions to the beat
https://bugs.launchpad.net/mixxx/+bug/902239"
1701171,2017-06-29 06:00:06 UTC,This change was made by a bot.
1701171,2017-07-05 23:20:54 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1701171,2017-07-09 12:05:58 UTC,"I have tested it with the mainline kernel 4.12 (generic and low-latency). The bug is still there. I've notice that if I've unplugged the power adapter before trying to wake the laptop up the, sometimes it wakes up successfully, what never happens if the power adapter is pluggen in."
1701171,2017-07-09 12:11:19 UTC,"I've found an interesting post about similar problem with other Lenovo laptop, please take a look:"
1701171,2017-07-10 05:30:46 UTC,Kernel bisection [1] is a good start to find which version introduced this regression.
1701171,2017-06-29 16:37:49 UTC,Ubuntu 16.10 Mate 32-bit did not have the issue.
1701182,2017-06-29 07:00:03 UTC,This change was made by a bot.
1701182,2017-07-05 23:20:16 UTC,You may need to run the following from a terminal:
1701186,2017-06-29 07:16:59 UTC,Temporary bug fix provided in x.3884.
1701191,2017-06-29 07:43:39 UTC,"openstack version:kilo
powervc-drvier version:master"
1701196,2017-06-29 17:30:14 UTC,"Having compile issues here:
https://github.com/simonfuhrmann/mve/issues/359"
1701196,2017-06-29 19:27:11 UTC,"I just tried on mint 17.1, and once I installed libpng12-dev, libjpeg-dev and libqtopengl5-dev, it seems to have compiled ok. Compiling is about at the limit of my expertise, so I can't tell you any more than that."
1701198,2017-09-11 04:17:41 UTC,[Expired for apport (Ubuntu) because there has been no activity for 60 days.]
1701198,2017-07-12 16:48:07 UTC,"The UnreportableReason field does contain information about packages being out of date on your system. If I saw that message I'd update my system and try the operation again, so I think it is useful."
1701198,2017-07-12 17:29:36 UTC,"I've seen ""truncated"" report files being listed as `UnreportableReason`. In that case showing the reporting dialog doesn't make sense. I doubt that users who are not apport developers pay attention to that field without any further feedback/interaction from the apport dialog, but they should since if they're already willing to report bugs, they're most likely willing to update outdated packages."
1701199,2017-06-29 14:03:41 UTC,"In the future, please use 'ubuntu-bug package-name' to report Ubuntu bugs.
https://help.ubuntu.com/community/ReportingBugs"
1701199,2017-07-02 12:09:34 UTC,Please press Alt+F2 then type and run:
1701199,2017-08-21 15:19:24 UTC,apport information
1701199,2017-08-21 15:19:25 UTC,apport information
1701199,2017-08-21 15:19:26 UTC,apport information
1701199,2017-08-21 15:19:27 UTC,apport information
1701222,2017-09-06 20:27:03 UTC,"I built the next test kernel, up to the following commit:
2d796f537d26e54a7fdf87632f9b8ee811759bc9"
1701222,2017-09-13 16:03:46 UTC,"I have tested both kernels provided, and both exhibit the bug. In both cases the daemon does not stop after the integration services is being disabled."
1701222,2017-09-13 14:45:48 UTC,"Thanks for testing.  To confirm we provided the correct input to the bisect, can you test the following two kernels and confirm that they were good or bad:"
1701222,2017-09-13 10:23:54 UTC,"I have tested the above kernel. The daemon stops if the integration service is being disabled, but does not automatically start after the service is being enabled again (same behavior as 4.4.0-3)."
1701222,2017-09-12 19:35:11 UTC,Xenial commit 332e5643b07(Mainline commit b521549a09ddfac)  was reported as the first bad commit.  I built a Xenial test kernel with this commit reverted.  It can be downloaded from:
1701222,2017-09-11 15:54:58 UTC,I have tested the above kernel build. The issue still occurs.
1701222,2017-09-11 19:59:28 UTC,"I built the next test kernel, up to the following commit:
332e5643b07ad6f24fd86290b081fc43a2ece778"
1701222,2017-09-18 18:25:23 UTC,"Thanks for testing.  We told the bisect commit 74caead was good per comment #27, which led us down the wrong bisect path."
1701222,2017-09-11 14:27:31 UTC,"I built the next test kernel, up to the following commit:
0cff5d394aaba1d6c75fe0036981b7a93a1c4b36"
1701222,2017-09-07 12:25:37 UTC,Tested the above kernel build. The issue still occurs.
1701222,2017-09-12 06:03:33 UTC,I have tested the above kernel build. The issue still occurs.
1701222,2017-09-19 08:49:18 UTC,I have tested the kernel provided with commit ef754413085f5 and the bug persists. The daemons do not stop if the integration services are being disabled.
1701222,2017-09-21 23:27:37 UTC,I have tested 4.4.0-2.16 from here: https://launchpad.net/ubuntu/+source/linux/4.4.0-2.16/+build/8908724
1701222,2017-09-21 08:24:28 UTC,"I have tested the mainline kernel provided with the compiled daemons form linux-next. In this case, the daemons do stop when the integration service is being disabled, but do not automatically start after we re-enable the integration service. Manually starting the service works fine. So the mainline is still affected by the second issue."
1701222,2017-09-21 21:10:13 UTC,"Ok, I reread the bug description and more importantly, comment #15.  So it sounds like the first issue has been fixed in all kernels since kernel version 4.4.0-2, but that is when the second issue was introduced.  If that is the case, we should focus on the second issue, where the daemons do not automatically start after the integration service is disabled and then enabled again."
1701222,2017-08-10 16:48:21 UTC,Would it be possible to test some of the early 16.04 kernels to try and figure out a last good kernel and first bad kernel?
1701222,2018-07-24 09:31:15 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1701222,2017-11-09 17:17:26 UTC,"Since it requires control of the host, this cannot be done in Azure. Control of the host is rather restricted there."
1701222,2017-09-22 00:19:57 UTC,Thanks for the update.  So the mainline kernel still has the second issue and 4.4.0-2.16 also has the second issue.  Presumably all the kernel version in between these two also have the second issue.
1701222,2017-10-04 08:31:10 UTC,"The unit entered a failed state, and thus would not automatically started until failed state clears.
Why does bouncing of the services result in the daemon exiting with an error condition? Should that particular exit code result in a graceful shutdown of the service, such that the unit can be restarted again?
What userspace events should be causing the start of this unit? a udev event / udev rule? a .path unit monitoring sysfs or some such?"
1701222,2017-09-25 17:57:55 UTC,It is possible.  I've added a systemd bug task.
1701222,2017-09-25 17:30:39 UTC,"I have tested the proposed kernel, but with this version both bugs are showing up."
1701222,2017-09-25 15:30:07 UTC,"Can you test a 3.19 based kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13366909"
1701222,2017-09-25 10:46:58 UTC,I have tested Xenial back to 4.2.0-16 from here: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/8099555
1701222,2017-09-19 16:08:46 UTC,"Thanks for the clarification.  Since there are two issues, we should probably focus on one at a time.  The test kernel posted in comment #36 sounds like it fixes the first issue, so lets handle that one first."
1701222,2017-09-06 16:36:54 UTC,Tested the above kernel build. The issue still occurs.
1701222,2017-08-10 17:02:52 UTC,"For example, here is an early 4.4.0-40 kernel:"
1701222,2017-09-06 13:33:29 UTC,I have tested the kernel above. The daemon still remains running after the integration service is being disabled.
1701222,2017-07-21 17:19:13 UTC,"Do you know the specific kernel version when this bug started happening in 16.04?  If not, we may have to test a few to narrow it down.  All 16.04 kernels are available here:"
1701222,2017-07-21 11:41:02 UTC,"We verified anything between 14.04.0 and 15.10, the thing with those releases is that even if we disable the Data Exchange integration service, the KVP daemon remains running on the VM."
1701222,2017-07-06 17:40:18 UTC,"Do we know which kernel version caused the regression?  If so, I can review the commits or perform a bisect if needed."
1701222,2017-07-06 15:51:40 UTC,"This is a regression, we did lots of work a year ago to ensure the daemons handle bouncing integration services settings."
1701222,2017-07-06 08:46:06 UTC,I took the v4.12 kernel and compiled the LIS daemons from those sources as well.
1701222,2017-07-05 23:09:52 UTC,"Also, do you know if this is a regression?"
1701222,2017-07-05 23:07:12 UTC,"Hi Chris,"
1701222,2017-08-10 16:09:41 UTC,"From what I was just told, no, they don't know when this started happening."
1701222,2017-08-22 11:02:03 UTC,Can you see if the issue was happening back in 4.4.0-20:
1701222,2017-08-22 13:40:31 UTC,The same happens on 4.4.0-20 kernel.
1701222,2017-08-22 14:58:31 UTC,"Let's try further back, can you test 4.4.0-10:
https://launchpad.net/ubuntu/+source/linux/4.4.0-10.25/+build/9287900"
1701222,2017-08-22 09:00:31 UTC,"The same happens on 4.4.0-40 kernel, I think this goes with comment #6."
1701222,2017-08-23 18:31:27 UTC,I started a kernel bisect between Ubuntu 4.4.0-2 and Ubuntu 4.4.0-3. The kernel bisect will require testing of about 7-10 test kernels.
1701222,2017-09-05 21:01:33 UTC,"I built the next test kernel, up to the following commit:
74caeadc074b099b80abca86a19ab95003ca294e"
1701222,2017-09-03 21:27:01 UTC,I have tested the kernel above. The issue still occurs.
1701222,2017-08-23 09:53:29 UTC,"I have checked back to 4.2.0-16. It seems that 4.4.0-2 is the last kernel where the daemons remain running even if integration services are being disabled. Starting with 4.4.0-3 the daemons stop if the integration services are disabled, but do not automatically start if the integrations services are being enabled again."
1701222,2017-08-29 09:09:36 UTC,I have tested the kernel provided. The issue still occurs.
1701222,2017-08-28 21:04:16 UTC,"I built the next test kernel, up to the following commit:
501faf881377dc38998fe8603ee1767d61883cfb"
1701222,2017-09-01 14:15:34 UTC,"I built the next test kernel, up to the following commit:
49594cb78e0decefdd60bf462a25d7f50e8d5239"
1701222,2017-08-25 16:24:54 UTC,"I built the next test kernel, up to the following commit:
c0e46ba65adcd94a49c2d66bb600e66a56ace491"
1701222,2017-08-25 08:16:46 UTC,I have tested the kernel provided in the link above. The issue still occurs.
1701222,2017-08-24 16:18:35 UTC,"I built the next test kernel, up to the following commit:
c6f73b9f6bb9c8bf8e5beb31bbe4e18cb8c4b6d4"
1701222,2017-08-24 07:18:10 UTC,I have tested the kernel provided in the link above. The daemons do not stop when the integration services are disabled.
1701222,2017-08-28 08:09:17 UTC,I have tested the kernel provided. The issue still occurs.
1701222,2017-09-06 14:34:08 UTC,"I built the next test kernel, up to the following commit:
be636eeda2290c65f3283ee3bdc149a5d205a798"
1701232,2018-01-02 15:45:57 UTC,"Ideally the store would provide the required information. We get currently:
""""""
$ http --pretty=format --print b https://api.snapcraft.io/api/v1/snaps/details/robotfindskitten X-Ubuntu-Architecture:arm64 X-Ubuntu-Series:16 fields==anon_download_url,architecture,channel,download_sha3_384,summary,description,binary_filesize,download_url,icon_url,last_updated,license,package_name,prices,publisher,ratings_average,revision,screenshot_urls,snap_id,support_url,title,content,version,origin,developer_id,private,confinement channel==edge
{
    ""error_list"": [
        {
            ""code"": ""resource-not-found"",
            ""message"": ""Snap 'robotfindskitten' (CDwOz6O4zGyVXLcHbxWx9K7XTGmZCBye) has no published revisions in the given context.""
        }
    ],
    ""errors"": [
        ""Snap 'robotfindskitten' (CDwOz6O4zGyVXLcHbxWx9K7XTGmZCBye) has no published revisions in the given context.""
    ],
    ""result"": ""error""
}"
1701232,2018-01-02 15:58:13 UTC,"Omiting architecture makes it default to amd64 afaik; you'd need to know the list of architectures of the store you're querying, and loop"
1701232,2018-12-17 15:15:44 UTC,"$ uname -i
x86_64
ubuntu@bionic-snap:~$ snap install pi-kernel
error: snap ""pi-kernel"" is not available on this architecture (amd64) but exists on other
       architectures (arm64, armhf)."
1701232,2018-12-17 15:16:20 UTC,"I marked the store task as fix released, but I believe the snapd tasks can be marked as such as well."
1701237,2018-01-20 08:08:04 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1448
1701241,2017-08-17 11:46:07 UTC,"Hi,"
1701241,2017-06-30 17:14:09 UTC,Occurs during boot
1701249,2017-06-29 12:30:47 UTC,"(2 is ENOENT here, not actually the exit code of the process.)"
1701249,2017-07-04 05:30:44 UTC,"JUJU_VERSION was added to support Openstack workflows. AFAIK it isn't anything official, so there is no definition of 'proper formatting' except for what works for the Openstack Charmers (because they got here first)."
1701249,2018-03-02 09:12:48 UTC,"mojo should tell the operator that it tried to run juju-latest because of JUJU_VERSION, and should advise the operator to fix or unset this variable."
1701251,2017-06-29 14:51:33 UTC,"On Thu, Jun 29, 2017 at 12:24:13PM -0000, Dimitri John Ledkov wrote:

> s390x MAAS images are missing s390-tools
>
> ...
>
> e.g. like in the cloud images..... but it seems that those too lack
> s390-tools. Horum.
"
1701251,2020-10-09 21:51:55 UTC,Looking at some of the latest ephemeral-v2 and ephemeral-v3 image manifests this appears to be fixed:
1701256,2019-09-19 11:53:24 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1701273,2018-05-08 18:13:46 UTC,This change was made by a bot.
1701273,2021-01-07 04:09:45 UTC,4.8 EOL
1701282,2017-11-03 16:31:07 UTC,Syncing task from Mir.
1701289,2017-10-14 23:41:59 UTC,All good now!
1701289,2017-10-13 07:45:32 UTC,now ok. reboot at gnome
1701289,2017-10-13 06:45:33 UTC,In theory this should be fixed by https://bugzilla.gnome.org/show_bug.cgi?id=766233 but it seems to still happen.
1701289,2017-10-13 10:06:11 UTC,I think the upstream bug is this one: https://bugzilla.gnome.org/show_bug.cgi?id=788666
1701289,2017-10-11 08:51:59 UTC,This may have been fixed by mutter 3.26.1-2 (bug 1722510).  At least I can no longer reproduce it using the recipe in my duplicate bug 1722709.
1701289,2017-10-06 01:37:01 UTC,"Also tracking this crash in:
https://errors.ubuntu.com/problem/fb179bc620e408d216f4b8700f714e6ebb2ebf09"
1701289,2017-10-05 23:43:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701289,2017-06-29 14:58:13 UTC,"StacktraceTop:
 XIGetClientPointer (dpy=0x5609dc65fd40, win=win@entry=0, deviceid=deviceid@entry=0x7ffe47626ef4) at ../../src/XGetCPtr.c:59
 gdk_x11_display_get_default_seat (display=0x5609dc66d0a0) at ././gdk/x11/gdkdisplay-x11.c:2889
 get_pointer_position_gdk (mods=0x7ffe47626f64, y=0x7ffe47626f98, x=0x7ffe47626f94) at backends/meta-cursor-tracker.c:374
 meta_cursor_tracker_get_pointer (tracker=<optimized out>, x=x@entry=0x7ffe47626f94, y=y@entry=0x7ffe47626f98, mods=mods@entry=0x7ffe47626f64) at backends/meta-cursor-tracker.c:419
 shell_global_get_pointer (global=global@entry=0x5609dc5c24b0, x=x@entry=0x7ffe47626f94, y=y@entry=0x7ffe47626f98, mods=mods@entry=0x7ffe47626f9c) at shell-global.c:1430"
1701289,2017-10-11 21:26:14 UTC,It's okj after rebooting.
1701297,2017-07-06 15:06:31 UTC,"On 07/05/2017 08:14 PM, Daniel Axtens wrote:

> Hi Tyler,
>
> Do you know what the changes between the ga-16.04 and hwe-16.04 kernel
> are that make apparmor+overlayfs work?
"
1701297,2017-07-07 04:23:58 UTC,Tyler - thanks for that.
1701297,2017-07-07 07:07:17 UTC,"From an apparmor pov those 2 kernels are almost identical, with the 4.4 kernel picking up a couple of backport patches, that just do some simple remapping and should not affect behavior."
1701297,2017-07-07 16:52:36 UTC,"John is going to build a test kernel, based on the ga-16.04 kernel, with the binfmt_elf commit cherry-picked from the hwe-16.04. That will let someone from the MAAS team attempt to reproduce the issue with the test kernel and, if the deployment succeeds, it'll tell us that the binfmt_elf commit is causing the change in behavior."
1701297,2017-07-07 17:04:33 UTC,"@Andres One thing that I'm struggling with is why this bug hasn't been seen before. IIUC, it should be present in the very first ga-16.04 kernel that Ubuntu 16.04 LTS was released with (in addition to earlier kernels while Xenial was a development release). Has MAAS 2.1.x and ga-16.04 kernels just now been used together or could there be some other change (in the kernel, MAAS, or maybe even something else) since the time that Ubuntu 16.04 LTS was released that we're not considering?"
1701297,2017-07-07 17:13:40 UTC,"To elaborate a bit more, the apparmor and overlayfs incompatibility has been a known kernel issue from before 16.04's release and, at this time, isn't something that is likely to be fixed in 16.04. I'd like to better understand if something changed in userspace that started tickling the incompatibility issue. Did MAAS change how it was using AppArmor in the recent SRU that took it to version 2.1.5?"
1701297,2017-07-09 09:11:45 UTC,"I am also getting the same issue with ga kernel
Where we hav to set the hwe kernel?"
1701297,2017-07-08 05:13:17 UTC,Well that explains it. So we would have seen this issues from release except for the cloud-init bug.
1701297,2017-07-10 05:44:15 UTC,There is a xenial test kernel at
1701297,2017-07-11 19:29:47 UTC,"If you are affected by this bug, then you have the following options:
a.) upgrade to maas 2.2
 MAAS 2.2 sends 'apparmor=0' to the installation/commissionging kernel command
 line.  2.2 is in -proposed for 16.04, 16.10, 17.04 repositories and
 is already available in artful."
1701297,2017-07-06 13:58:21 UTC,"When using the following kernel (the default Xenial kernel, aka ga-16.04 in MAAS), we see this issue:"
1701297,2017-08-16 09:40:32 UTC,An addition to workaround b.) from #32.
1701297,2018-04-02 16:45:44 UTC,"Hi all, sorry to necro a thread, but I'm having this issue on MAAS 2.3.1. Is anyone able to provide some insight into this issue?"
1701297,2017-07-07 18:17:56 UTC,"@Tyler,"
1701297,2017-07-06 01:14:22 UTC,"Hi Tyler,"
1701297,2017-08-08 01:10:47 UTC,"Hi Marzog,"
1701297,2017-06-30 11:47:46 UTC,"@Tyler,"
1701297,2017-06-29 15:13:55 UTC,https://pastebin.canonical.com/192254/
1701297,2017-06-29 15:18:28 UTC,Seems this is related to:
1701297,2017-06-29 15:21:52 UTC,Please attach the journalctl -xe failure output
1701297,2017-06-29 15:41:11 UTC,https://pastebin.canonical.com/192261/
1701297,2017-06-29 16:07:50 UTC,"Note that this bug was reported by Ashley, you I filed it. That said, I've attempted to reproduce this with latest maas images containing cloud-init  0.7.9-153-g16a7302f-0ubuntu1~16.04.1 in MAAS 2.3 and have not come across such issue"
1701297,2017-06-29 16:48:45 UTC,"ubuntu@donphan:~$ sudo journalctl -u ntp --no-pager --since today
sudo: unable to resolve host donphan
-- Logs begin at Thu 2017-06-29 16:36:06 UTC, end at Thu 2017-06-29 16:44:47 UTC. --
Jun 29 16:36:36 donphan systemd[1]: Starting LSB: Start NTP daemon...
Jun 29 16:36:36 donphan ntp[2441]:  * Starting NTP server ntpd
Jun 29 16:36:36 donphan ntp[2441]:    ...done.
Jun 29 16:36:36 donphan systemd[1]: Started LSB: Start NTP daemon.
Jun 29 16:36:36 donphan ntpd[2453]: proto: precision = 0.057 usec (-24)
Jun 29 16:36:36 donphan ntpd[2453]: Listen and drop on 0 v6wildcard [::]:123
Jun 29 16:36:36 donphan ntpd[2453]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun 29 16:36:36 donphan ntpd[2453]: Listen normally on 2 lo 127.0.0.1:123
Jun 29 16:36:36 donphan ntpd[2453]: Listen normally on 3 eno1 10.245.208.209:123
Jun 29 16:36:36 donphan ntpd[2453]: Listen normally on 4 lo [::1]:123
Jun 29 16:36:36 donphan ntpd[2453]: Listen normally on 5 eno1 [fe80::eeb1:d7ff:fe73:1da4%2]:123
Jun 29 16:36:36 donphan ntpd[2453]: Listening on routing socket on fd #22 for interface updates
Jun 29 16:36:37 donphan systemd[1]: Stopping LSB: Start NTP daemon...
Jun 29 16:36:37 donphan ntp[2519]:  * Stopping NTP server ntpd
Jun 29 16:36:37 donphan ntpd[2453]: ntpd exiting on signal 15 (Terminated)
Jun 29 16:36:37 donphan ntp[2519]:    ...done.
Jun 29 16:36:37 donphan systemd[1]: Stopped LSB: Start NTP daemon.
Jun 29 16:36:37 donphan systemd[1]: Starting LSB: Start NTP daemon...
Jun 29 16:36:37 donphan ntp[2532]:  * Starting NTP server ntpd
Jun 29 16:36:37 donphan ntp[2532]: /usr/sbin/ntpd: error while loading shared libraries: libcap.so.2: cannot stat shared object: Permission denied
Jun 29 16:36:37 donphan ntp[2532]:    ...fail!
Jun 29 16:36:37 donphan systemd[1]: ntp.service: Control process exited, code=exited status=127
Jun 29 16:36:37 donphan systemd[1]: Failed to start LSB: Start NTP daemon.
Jun 29 16:36:37 donphan systemd[1]: ntp.service: Unit entered failed state.
Jun 29 16:36:37 donphan systemd[1]: ntp.service: Failed with result 'exit-code'.
ubuntu@donphan:~$"
1701297,2017-06-29 17:44:00 UTC,Hi Ashley --
1701297,2017-06-30 20:09:55 UTC,"Andres,"
1701297,2017-06-29 19:57:29 UTC,"Ok, so I have been able to consistently reproduce this issue:"
1701297,2017-06-29 20:07:54 UTC,"syslog http://paste.ubuntu.com/24983800/
dmesg http://paste.ubuntu.com/24983801/
journal http://pastebin.ubuntu.com/24983806/"
1701297,2017-06-29 20:24:58 UTC,"[   46.973551] audit: type=1400 audit(1498766510.281:15): apparmor=""STATUS""
operation=""profile_load"" profile=""unconfined"" name=""/usr/sbin/ntpd""
pid=2936 comm=""apparmor_parser""
[   48.051990] audit: type=1400 audit(1498766472.362:16): apparmor=""DENIED""
operation=""getattr"" info=""Failed name lookup - disconnected path"" error=-13
profile=""/usr/sbin/ntpd"" name=""overlay/etc/ld.so.cache"" pid=3019
comm=""ntpd"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0
[   48.052025] audit: type=1400 audit(1498766472.362:17): apparmor=""DENIED""
operation=""getattr"" info=""Failed name lookup - disconnected path"" error=-13
profile=""/usr/sbin/ntpd"" name=""lib/x86_64-linux-gnu/libcap.so.2.24""
pid=3019 comm=""ntpd"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0"
1701297,2017-06-29 20:25:21 UTC,that looks related to overlayfs use in ephemeral environment.
1701297,2017-06-29 23:22:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701297,2017-06-30 02:47:32 UTC,It seems that this only happens when using ga-16.04 and doesn't when using hwe-16.04
1701297,2017-06-30 03:40:13 UTC,AppArmor has difficulties mediating filesystem access when overlayfs is involved. That's a known issue but isn't one that is easily solved due to the internal design of overlayfs and its use of private vfsmounts. It also isn't something that we're planning to fix for the 17.10 cycle.
1701297,2017-06-29 18:08:43 UTC,"Ashley,
Can we get 'dmesg' output and syslog also?"
1701298,2017-07-01 19:25:39 UTC,"On Sat, Jul 01, 2017 at 01:27:13PM -0400, James Cloos wrote:

> CW> This is all very well and true, but it's not what this bug is about.
>
> My reading of this bug is that a patch to support .d/* is exactly what
> was requested.
"
1701298,2017-07-01 16:14:25 UTC,"On Fri, Jun 30, 2017 at 08:19:09PM -0400, James Cloos wrote:

> >>>>> ""CW"" == Colin Watson <email address hidden> writes:
>
> CW> Erich, could you give an example of the sort of changes you'd like to be
> CW> able to make in a .d directory?
>
> Colin,
>
> One good example is the port number(s).  Having to edit sshd_config
> every time the package changes the default contents is a pain.  And
> a non-default port number is very common.
"
1701298,2017-06-30 11:36:43 UTC,"There are already bugs about an Include directive in sshd, so please don't file more.  Also, it isn't really necessary to re-file this in Debian since I follow both trackers."
1701298,2017-06-30 07:36:01 UTC,"Hi Erich,
I agree that would be a nice change to have, but I got puzzled checking the details."
1701298,2017-06-30 12:44:54 UTC,"@cjwatson, I've been getting my work into the habit of deploying Debian packages for all organization-wide system configuration files.  So, when I noticed the other day that openssh-client 7.3p1+ now supports include directives I put together a new package that gives all of our internal users no-login access to the systems that they need for their work.  The exact "".d"" file I put together to do this is:
===
Match exec ""getent hosts %h | grep -qE '^10\.10\.10\.'""
        User root
        StrictHostKeyChecking no
        UserKnownHostsFile /dev/null
        IdentityFile /opt/insight/SLE-101_id_rsa
===
However, at the moment, for anyone to use this file I would need to modify /etc/ssh/ssh_config by adding ""Include /etc/ssh/ssh_config.d/*"".  While I can do that, I know that it's not generally recommended to have a package modify the config files of other packages.  So, ideally, the default ssh_config file would have an Include directive that allows me to simply place my "".d"" file in the appropriate "".d"" directory such that it automatically gets included whenever my custom package is installed."
1701299,2018-05-08 18:14:01 UTC,This change was made by a bot.
1701299,2021-01-07 04:09:18 UTC,4.8 EOL
1701307,2017-06-29 18:31:08 UTC,chmod a-x /etc/grub.d/30_uefi-firmware.  rm also works but changing the permissions is easier to reverse.
1701309,2020-07-03 05:03:39 UTC,DistroRelease: Kali 2017.1
1701310,2021-01-07 04:09:14 UTC,4.8 EOL
1701310,2017-06-29 19:39:48 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1701310,2017-06-29 17:50:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701318,2017-06-29 18:30:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701318,2021-01-07 04:09:02 UTC,4.8 EOL
1701318,2017-06-29 19:22:29 UTC,I agree this is the same as my bug-report #1701340 which you have correctly flagged as duplicate.
1701327,2017-07-05 10:31:36 UTC,"Hi Sridhar, Please find my analysis :"
1701327,2017-07-05 12:16:08 UTC,"Hi Anusha, thanks for looking into this problem."
1701327,2017-07-06 06:53:11 UTC,"Hi Sridhar, From the logs in the bug description, it is clear that l2population mechanism driver is invoked to notify agent on port update. So I thought l2population mechnanism driver is set in your setup, so that agent notification is invoked for each specified mechanism driver in ml2_conf.ini."
1701327,2017-07-06 14:02:56 UTC,"l2population mechanism driver is enabled in plugin.ini
mechanism_drivers = openvswitch,l2population,<other mechanism drivers>"
1701327,2017-07-07 05:51:14 UTC,Could you please enable l2_population = True in ml2_conf.ini as specified below and repeat the test steps. Because 'q-agent-notifier-l2population-update_fanout' queue is used by l2population mechanism driver to notify agent on port update and this queue is created if l2_population is set under agent section.
1701327,2017-07-07 13:06:08 UTC,"Anusha, I did not look into right file, l2_population is set to true in the environment:"
1701327,2017-07-10 20:06:11 UTC,"Anusha, are you able to make any progress?"
1701327,2017-07-11 05:18:25 UTC,"I am still debugging, for now I don't have any findings on these issue.
I have issued port-update continuously and didn't observe this error on ocata setup."
1701327,2017-07-11 12:17:20 UTC,"Anusha, this problem does not occur all the time, only one in few attempts. I will work to get you logs."
1701334,2017-07-07 18:38:19 UTC,"Still nothing, here's a copy of the output."
1701334,2017-07-06 13:37:18 UTC,You may need to run the following from a terminal:
1701334,2017-06-29 18:00:03 UTC,This change was made by a bot.
1701335,2019-11-27 12:27:10 UTC,https://salsa.debian.org/phpmyadmin-team/phpmyadmin/issues/31#note_119821
1701348,2017-06-30 00:28:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701348,2021-01-07 04:08:57 UTC,4.8 EOL
1701390,2018-01-25 09:25:48 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3714
1701392,2017-06-30 03:24:14 UTC,"I subscribed apport because it appears there's a python2 -> python3 regression in here too, see the HookError_ubuntu.txt file."
1701395,2017-06-30 13:58:03 UTC,referenced commit: https://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/revision/570.2.1
1701398,2018-03-22 06:23:58 UTC,Please see: https://git.opnfv.org/daisy/tree/docs/release/scenarios/os-nosdn-ovs_dpdk-noha/os-nosdn-ovs_dpdk-noha.rst and currently DPDK can be deployed only by Daisy4NFV automatic script.
1701400,2019-09-19 14:48:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1701410,2017-07-03 13:34:31 UTC,"I added following patch and tried to delete network resource.  As a result, I recorded trace for method calling.  Please refer attached file:"
1701412,2017-06-30 03:21:06 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1701412,2017-11-16 11:10:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701413,2017-06-30 05:30:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/479150"
1701413,2020-06-18 04:09:00 UTC,"Reviewed:  https://review.opendev.org/727073
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=e6bb1584d75cf5dd6aaff199f8c235e08fb6f1d9
Submitter: Zuul
Branch:    master"
1701413,2020-05-13 08:58:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/727667"
1701413,2020-05-12 07:19:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/727073"
1701413,2020-05-20 03:48:24 UTC,"Reviewed:  https://review.opendev.org/727667
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=89a2bd20013b47c1b65d47a46e032987d2409c9f
Submitter: Zuul
Branch:    master"
1701413,2019-12-04 08:33:26 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1701413,2018-01-19 14:12:31 UTC,This RFE is approved. The only caveat is that the ability to handle the new value should be discoverable as an API extension
1701413,2017-10-24 01:54:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/514497"
1701413,2017-07-27 17:59:54 UTC,"Strictly speaking this is an API change, and as such should be tracked by a versioned API definition in neutron-lib. Though neutron-vpnaas API is not in neutron-lib and neutron-vpnaas is not under neutron governance at the moment, there's no much the drivers team can provide oversight on. That said I reviewed change [1]."
1701413,2019-12-04 08:58:46 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/514497
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1701419,2017-08-30 18:49:42 UTC,Thanks for the report.  We agree this would be nice.
1701433,2017-08-14 16:13:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/493595"
1701433,2017-11-04 23:01:55 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/493595
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1701434,2017-07-13 01:01:44 UTC,"Was there any config provided when you did this? Seems like there are also all the service stop/start commands that should get attempted and fail (and these do throw exceptions). I don't think failing to unbind because of a missing file, for example, is critical enough to warrant to completing the apply, but failing to restart NM or systemd would definitely be."
1701434,2018-07-24 02:07:15 UTC,I'm marking this as confirmed as the behaviour has come up in LP: #1735318.
1701434,2018-07-24 03:46:49 UTC,It looks like at least some of this changed between Bionic and Cosmic - here with a netplan 0.39:
1701434,2019-07-05 19:49:14 UTC,I'm seeing the same thing in LP:1835275 except netplan doesn't output any errors.
1701434,2019-07-11 19:28:17 UTC,No; by now this is working exactly as expected; netplan should return 0 as long as there is no actual syntax error in the netplan config; for now everything else is left to the backends.
1701449,2018-10-01 19:44:37 UTC,"@Nick: if you can recreate the librbd memory growth, any chance you can help test a potential fix [1]?"
1701449,2018-10-01 19:23:32 UTC,Any reason we are keeping this bug and #1674481 separate? We are not sure?
1701449,2017-07-03 08:12:32 UTC,"We are seeing pretty much the same issue with even small (1G mem) virtual instances using 2-3GB of RSS after running I/O intensive applications. Live migrating the instance to another machine pushes the memory usage back, but it will grow back again once I/O is back."
1701449,2017-09-29 08:55:13 UTC,Linking back to bug 1674481 which I think is the same issue seen in Ubuntu
1701449,2017-09-29 10:18:51 UTC,Is there any progress on solving this or does anyone has an idea how to further debug this? I think we are kinda stuck in the ceph bug tracker issue as well [1].
1701449,2017-07-20 09:48:21 UTC,Any update on this?
1701451,2017-06-30 06:31:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/479170"
1701451,2018-03-29 03:12:29 UTC,"Reviewed:  https://review.openstack.org/543490
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb4b60a3af242892a4460a251ff067e00c47e43f
Submitter: Zuul
Branch:    stable/queens"
1701451,2018-02-09 15:56:05 UTC,"Reviewed:  https://review.openstack.org/540154
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7db20191206be454175e069cab08107a8c4fbe6f
Submitter: Zuul
Branch:    master"
1701451,2018-02-01 21:57:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/540154"
1701451,2017-08-28 09:55:17 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1701451,2017-08-22 11:38:57 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1701451,2017-08-12 13:08:56 UTC,"Reviewed:  https://review.openstack.org/479201
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f1cf54df9a80f87f4e4b497db587f24eea25523d
Submitter: Jenkins
Branch:    stable/newton"
1701451,2018-02-12 15:25:50 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/543490"
1701451,2017-07-28 07:41:17 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1701451,2017-07-03 01:12:47 UTC,"Change abandoned by Alex Xu (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/479201"
1701451,2017-07-03 01:12:31 UTC,"Change abandoned by Alex Xu (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/479197"
1701451,2017-06-30 14:41:48 UTC,"Reviewed:  https://review.openstack.org/479170
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aaeea4bf39377c4109f6b2857794ee0e7d51e786
Submitter: Jenkins
Branch:    master"
1701451,2017-06-30 07:43:38 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/479197"
1701451,2017-06-30 07:45:02 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/479201"
1701451,2017-08-12 11:05:19 UTC,"Reviewed:  https://review.openstack.org/479197
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=48fe8d17e38193c63b6aea98d73ce13a835cd0d0
Submitter: Jenkins
Branch:    stable/ocata"
1701453,2021-01-07 04:08:52 UTC,4.8 EOL
1701453,2017-06-30 19:41:42 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1701453,2017-07-11 16:23:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701465,2017-06-30 07:54:22 UTC,Fix committed in https://git.launchpad.net/ltsp-manager/commit/?id=43ecbc733682bec231e5f6320775926909181f16.
1701470,2017-06-30 09:02:52 UTC,Fix partially committed in https://git.launchpad.net/ltsp-manager/commit/?id=53a1be790093b11fd07cabd6b39e79de24db986e.
1701487,2018-02-08 10:26:28 UTC,"Reedip, Are you still looking into issue?"
1701487,2018-05-01 06:21:12 UTC,"I looked at the original problem and it doesn't reproduce any more. I think it was a driver issue, that was already fixed."
1701498,2017-10-10 20:32:38 UTC,Redelegation and impersonation are not designed to work together. Is the trust created with impersonation abilities?
1701498,2017-07-07 02:45:28 UTC,Maybe also set max_redelegation_count to a value larger than 0?
1701498,2017-07-07 03:47:57 UTC,"No that's the not issue, max_redelegation_count is by default 3. The issue is with keeping track of the delegation_count (which is decremented by 1 for every delegation) of the trust. That's alway initialized to 0 when the trust is fetched by the backend driver. Hence that check fails."
1701498,2017-07-06 11:15:47 UTC,"@Ethan,"
1701498,2017-06-30 11:14:04 UTC,"Ignore the comment above, I think it does not work. I'll have a look."
1701498,2017-07-03 08:33:36 UTC,"I think this is working as expected - keystone trusts by default don't allow a chain of delegation, to avoid unconstrained redelegation (such as the redelegation here between the parent stack and OS::Heat::Stack)."
1701498,2017-07-06 09:28:46 UTC,"Hi Steven,
  Thanks for sharing this, it's useful! I still have a question, if I set allow_redelegation = True in keystone.conf, do I need to do change in heat side?"
1701498,2017-06-30 11:06:08 UTC,"I've not tested it, but I would guess the domain information is not being passed correctly. We do a context.to_dict() and then context.from_dict() in the RemoteStack."
1701498,2017-07-03 07:02:46 UTC,"I think the issue is, when using reauth_auth_method=trusts, we reload the stack with the stored context (with trust_id) before creating the resources. Therefore, when making heap api call to create the remote stack, it would be using the trust scoped token, where again we try and create a trust for the remote stack (using that token) and it fails."
1701498,2017-07-03 01:24:11 UTC,Thanks Rabi.
1701499,2017-09-22 09:33:13 UTC,"Can you try v4.14-rc1?
There are some fixes about iommu, thunderbolt, ACPI, etc."
1701499,2017-09-25 08:31:12 UTC,"I was running v4.14-rc1 for the whole last week.
It is... different."
1701499,2017-09-25 08:43:06 UTC,"I also checked 4.13.3 a moment ago and when booting with the dock attached I got a freeze again soon after starting the desktop session. So the original bug I reported here was definitely not fixed in 4.13.3, nor by BIOS upgrade to 1.5.0. However, all network connections were active at the login screen."
1701499,2017-09-25 16:44:27 UTC,"Still using 4.13.3 today and I already had sudden ethernet connection dropout which couldn't be reestabliished from NetworkManager without replugging the dock. I conclude this problem must be related to kernel then, because as said earlier, on 4.14.rc1 I had no ethernet stability issues for the whole week (besides having to manually establish it after logging)."
1701499,2017-09-25 19:15:39 UTC,just FYI: 4.14.rc2 networking failure seems to be caused by dhcp client crash. Where to submit bug report for this?
1701499,2017-09-25 19:30:33 UTC,4.14.rc2 network problem fixed by running:
1701499,2017-09-26 06:47:50 UTC,That's probably some AppArmor regression introduced in v4.14-rc2.
1701499,2017-09-26 07:44:25 UTC,"No, after disabling apparmor for dhclient, I'm successfully running v4.14-rc2.
However, it looks like exactly the same problems exist with this kernel as with v4.14-rc2:"
1701499,2017-10-20 04:02:38 UTC,"Uh, I meant ""I cannot reproduce the issue""."
1701499,2017-10-20 04:44:41 UTC,"There was a problem I found a little while back with hooking up dock to
artful where gnome would crash. That was fixed recently, but I haven't seen
anything else either (both wd15 and tb16 with XPS 9350)"
1701499,2017-10-20 07:12:56 UTC,"Yea, I think it's related to gnome-shell."
1701499,2017-10-20 18:16:10 UTC,"Here's more detail, the gnome-shell fix came with this bug:
https://launchpad.net/bugs/1722811"
1701499,2018-09-17 19:57:12 UTC,Unfortunately I no longer have the WD15 dock. I switched to TB16 and it also has some hotplugging issue (there is a separate launchpad ticket reported by others).
1701499,2017-09-30 08:58:16 UTC,"After a week of testing v4.14-rc2, the conclusions remain the same:
- System doesn't freeze when booting up and logging in with the dock attached.
- Ethernet doesn't connect automatically on boot / after login, manual intervention required.
- System doesn't wake from suspend if the dock was disconnected during sleep.
- System does wake properly from suspend if the dock was connected during sleep or dock connection did not change at all.
- No sudden ethernet disconnects."
1701499,2017-10-19 10:15:45 UTC,I can reproduce the issue on latest Artful release. Although I use XPS 9360 instead of Precision 5520. The kernel is 4.13 based.
1701499,2017-09-16 12:00:35 UTC,"Also, what are these dots in syslog?"
1701499,2017-09-16 11:53:16 UTC,I upgraded to BIOS 1.5.0 yesterday and also upgraded the dock firmware yesterday as well again (using windows-10-on-the-go usb stick I created just for that purpose).
1701499,2017-06-30 09:24:06 UTC,apport information
1701499,2017-06-30 09:24:08 UTC,apport information
1701499,2017-06-30 09:24:09 UTC,apport information
1701499,2017-09-16 11:58:56 UTC,I can confirm 1.5.0:
1701499,2017-06-30 11:07:04 UTC,I did apport-collect immediately after filing the bug.
1701499,2017-07-06 13:33:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1701499,2017-06-30 09:30:21 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1701499,2017-07-31 08:25:35 UTC,"Unfortunately that turned out to be a fluke. I had two freezes on 4.11.12, and just a freeze a minute ago on fresh 4.13.rc3 installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/. No panics though."
1701499,2017-07-31 09:54:03 UTC,"Please file an upstream bug at [1], or escalate the issue to linux-usb mailing list [2]."
1701499,2017-09-15 17:25:16 UTC,Tried posting to linux-usb mailing list but I got no answer back. Any other ways to report this problem?
1701499,2017-09-15 17:27:50 UTC,"Also, I've read this on another USB ticket in bugzilla:
All USB bugs should be sent to the <email address hidden> mailing
list, and not entered into bugzilla.  Please bring this issue up there,
if it is still a problem in the latest kernel release."
1701499,2017-09-15 17:46:21 UTC,"Can you please check if you're on the latest firmware for the 5520? There
was a recent issue on many laptops that was leading to instability
specifically with USB. BIOS has been released for many of them already."
1701499,2017-09-15 22:46:35 UTC,From what I can tell you're on BIOS 1.3.3.  Please upgrade to 1.5.0.  It's available both for Ubuntu through fwupd (https://fwupd.org/lvfs/device/34578c72-11dc-4378-bc7f-b643866f598c) or can be updated from the F12 post menu by downloading from support.dell.com (https://www.dell.com/support/article/us/en/19/sln171755/updating-the-dell-bios-in-linux-and-ubuntu-environments?lang=en#updatebios2015)
1701499,2017-07-07 06:05:04 UTC,Yesterday I updated to 4.11.9 and so far everything is stable. I managed to reboot 6 times in a row with no issues. The kernel error is also gone from syslog.
1701500,2017-07-17 14:58:59 UTC,"Why the ""wishlist""?"
1701502,2020-11-17 05:27:02 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life in April 2019."
1701503,2018-05-08 18:14:15 UTC,This change was made by a bot.
1701503,2021-01-07 04:08:24 UTC,4.8 EOL
1701507,2017-07-08 05:06:45 UTC,"Reproduced with 3.0.3:
 pt-query-digest --create-review-table --review D=percona,t=review slow-log-lp1701507.txt"
1701507,2018-01-24 22:30:51 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-736
1701513,2018-08-07 10:49:44 UTC,"------- Comment From <email address hidden> 2018-08-07 06:45 EDT-------
(In reply to comment #7)

> This package / The package <xyz> is part of the universe section of the
> Ubuntu archive. Universe packages are maintained by the community, and the
> maintainers do not necessarily work for Canonical, therefore these packages
> are not always supported directly by Canonical.
"
1701513,2020-04-07 05:08:18 UTC,Thank you for taking the time to file a bug report.
1701513,2017-07-24 14:50:38 UTC,"This package / The package <xyz> is part of the universe section of the Ubuntu archive. Universe packages are maintained by the community, and the maintainers do not necessarily work for Canonical, therefore these packages are not always supported directly by Canonical.
The existing process to update packages in the Universe archive with patches, is as follows:
1. Upstream: Upstream your fix to the appropriate upstream project.
2. Debian: once your patch is ack’ed and accepted upstream, you need to request a merge of this patch to the package in Debian stable. https://www.debian.org/Bugs/Reporting use this link to report your issue and submit a fix.
3. Ubuntu: Once it is merged into Debian stable, request a merge of this package with Ubuntu. https://wiki.ubuntu.com/Debian/Bugs will provide you an overview on how to handle bugs that are reported to Debian and subsequently to Ubuntu.
- The merge request lands by default in Ubuntu's current development release (today ‘Artful’).
- If required an SRU may follow to get the changes into already released Ubuntu versions (like ‘Xenial’ or ‘Zesty’).
Work with the respective upstream maintainers (Debian and Ubuntu) is required during this process.  For critical issues we can advise you as you go through this process and help push the patches through by chasing the appropriate project contributors.
[To find out if a package is a universe package use: apt policy <package-name>.]"
1701513,2017-06-30 10:19:45 UTC,Default Comment by Bridge
1701513,2018-02-09 06:10:04 UTC,"------- Comment From <email address hidden> 2018-02-09 01:06 EDT-------
You need to ask Canonical about this issue having been fixed since this bug is already mirrored to Canonical."
1701529,2017-06-30 19:33:09 UTC,"Hello djcj,"
1701530,2017-07-06 09:10:18 UTC,https://review.openstack.org/#/c/472275/13/specs/pike/os-manuals-migration.rst
1701541,2020-03-03 10:45:56 UTC,Moving to Confirmed as tempest's client still expects 204 response code.
1701541,2018-11-28 15:30:39 UTC,"Change abandoned by afazekas (<email address hidden>) on branch: master
Review: https://review.openstack.org/479286
Reason: Looks like there is not much interest for this change."
1701541,2017-08-09 22:06:19 UTC,"As per lance, this is being marked as wont fix. we can re-visit when/if microversions or v4 is implemented."
1701541,2017-07-25 21:31:35 UTC,"According to the interoperability guide lines [0], we won't be able to fix this unless we implement v4 or microversions."
1701541,2019-07-13 21:13:04 UTC,Moving to New as the associated change has been abandoned.
1701541,2017-07-10 11:02:52 UTC,tempest change: https://review.openstack.org/#/c/479286/
1701541,2017-06-30 13:12:24 UTC,https://github.com/GrahamDumpleton/mod_wsgi/issues/2
1701541,2017-06-30 13:10:17 UTC,documented behavior
1701541,2017-06-30 12:37:11 UTC,"https://developer.openstack.org/api-ref/identity/v3/?expanded=confirm-role-inference-rule-detail,get-role-inference-rule-detail 204 unfortunately documented at the moment."
1701541,2017-07-12 10:41:06 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1701542,2017-06-30 20:02:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701542,2017-07-06 10:27:02 UTC,Same bug happened with mainline kernel (4.12.0-041200rc7-generic) and also with the regular trusty kernel (3.13.0-123-generic)
1701542,2017-07-06 11:17:59 UTC,"It sounds like this is not a regression and you tested the mainline kernel.  Version 4.12 final is now available.  For completeness, can you give that one a test:"
1701542,2017-07-06 13:25:49 UTC,"Unfortunately, we managed to free up some space on the disks, so it's going to be complicated to replicate for now."
1701556,2017-11-17 19:13:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701556,2017-11-17 21:28:16 UTC,I'm currently unable to compile the firefox package in Ubuntu 16.04 and 17.10 because the available versions of cargo and rustc are too old:
1701556,2017-12-26 14:31:47 UTC,"Indeed, it looks like the newer versions of these packages are missing from older Ubuntu releases, making it impossible to rebuild Firefox from scratch."
1701556,2017-12-29 09:50:43 UTC,"Since I can reproduce this with Docker image `ubuntu:bionic` I assume that 18.04 is affected as well. This might change since it's not released yet, but it's worth mentioning it."
1701556,2017-12-29 19:21:16 UTC,"Could you please post the complete error message for bionic? The cargo package version (https://launchpad.net/ubuntu/+source/cargo) should be sufficient there, but looks like there's a newer version of rustc which haven't migrated from the -proposed archive (https://launchpad.net/ubuntu/+source/rustc). Not sure why, but that might be the only problem for bionic. I believe packages are built with -proposed enabled, so I suppose that might be why it works."
1701562,2017-07-01 15:43:49 UTC,"The guide i was following was https://jujucharms.com/docs/stable/tut-lxd
The guide probably does not need updating​."
1701562,2017-07-01 10:53:33 UTC,"Precise is no longer a supported series as of a few months ago.
Can you link to the guide so that we can make sure to update it? Typically
you shouldn't need to specify a series, but if you do, then trusty/xenial
are likely to be better targets."
1701562,2017-07-12 23:21:22 UTC,I have added phpmyadmin project to this bug report.
1701563,2017-06-30 13:28:23 UTC,New behavior on Artful: calling mir_create_menu_window_spec() with parent == nullptr
1701563,2017-07-03 02:21:54 UTC,Probably the same as bug 1671047 (and others I can't find right now).
1701589,2017-06-30 15:22:51 UTC,"As I recall, tids and trust-router were packaged in the same binary
package.
So it's not really clear which you want to run, and they both require
configuration anyway."
1701589,2017-06-30 15:28:27 UTC,"Thanks. I think installing both services but not starting either would be fine, certainly for the immediate fix."
1701592,2017-06-30 14:44:32 UTC,I forgot to add that the patch is against the 2.0.2  version of lightdm-gtk-greeter
1701622,2017-07-05 09:45:27 UTC,Thank you very much for taking the time to file this issue. I have added a redirect on the developer website to fix this issue.
1701632,2017-06-30 15:27:26 UTC,Related: Bug #1370837
1701632,2017-07-01 09:11:30 UTC,"If implemented, paves way for lp:661917"
1701632,2017-07-02 19:24:01 UTC,"I started working on this and realized it would be pretty complicated to implement well. If the Echo effect does not output when the fader is up, there is a sudden jump when raising the fader to the top. I'm not sure how to work around that."
1701656,2017-06-30 16:10:40 UTC,Two further observations:
1701656,2017-07-02 07:02:02 UTC,Adding package name (metadata)
1701697,2017-07-14 15:48:35 UTC,"Added -proposed, did an upgrade and further dkms install and iscsitarget dkms was installed with success on all those kernels."
1701697,2017-07-17 09:14:11 UTC,As these must be released before the associated kernels these will be released today on an expedited schedule.  They will also necessarily be released to -security also.
1701697,2017-07-17 09:55:09 UTC,"The verification of the Stable Release Update for iscsitarget has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1701697,2017-07-17 09:55:11 UTC,This bug was fixed in the package iscsitarget - 1.4.20.3+svn502-2ubuntu4.3
1701697,2017-07-20 10:54:08 UTC,"So, this iscsitarget-dkms fails with other kernels, like linux-raspi2, linux-aws, etc."
1701697,2017-07-18 14:24:25 UTC,"Is this bug relevant for > xenial? I can't see an iscsitarget package in yakkety, zesty or artful."
1701697,2017-07-18 14:56:19 UTC,"No, not revelant for anything but 4.4 derived kernels, that is, Xenial, Xenial derivatives and lts-xenial on Trusty."
1701697,2017-07-20 13:25:39 UTC,Packages at https://launchpad.net/~kleber-souza/+archive/ubuntu/ppa/+packages with the changes suggested by apw.
1701697,2017-07-14 15:46:06 UTC,"iscsitarget, 1.4.20.3+svn499, 4.4.0-21-generic, x86_64: installed
iscsitarget, 1.4.20.3+svn499, 4.4.0-79-generic, x86_64: installed
iscsitarget, 1.4.20.3+svn499, 4.4.0-83-lowlatency, x86_64: installed
iscsitarget, 1.4.20.3+svn499, 4.4.0-86-generic, x86_64: installed"
1701697,2017-07-17 09:56:08 UTC,This bug was fixed in the package iscsitarget - 1.4.20.3+svn499-0ubuntu2.3
1701697,2017-07-13 18:07:33 UTC,"Hello Thadeu, or anyone else affected,"
1701697,2017-07-24 07:59:49 UTC,This bug was fixed in the package linux - 4.4.0-87.110
1701697,2017-07-13 02:54:24 UTC,"Tested the new packages on both xenial and trusty with different kernels, including 4.4.0-21, 4.4.0-83 and 4.4.0-85."
1701697,2017-07-12 18:59:19 UTC,"There is a small bug in the match for reverting the patch on older kernels. I tested it on 4.4.0-79 and it worked, but it doesn't work on 4.4.0-83."
1701697,2017-07-05 19:05:49 UTC,"Hello Thadeu, or anyone else affected,"
1701697,2017-07-04 20:21:17 UTC,"The attachment ""fixes failure to build with 4.4.0-84"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1701697,2017-07-04 19:29:37 UTC,Tested that iscsitarget builds on 4.4.0-79 and 4.4.0-84 after this patch.
1701697,2017-07-04 13:53:21 UTC,I am working on a fix for the iscsitarget package.
1701697,2017-07-04 13:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1701697,2017-06-30 18:34:19 UTC,apport information
1701697,2017-06-30 18:34:17 UTC,apport information
1701697,2017-06-30 18:34:16 UTC,apport information
1701697,2017-06-30 18:34:13 UTC,apport information
1701697,2017-06-30 18:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1701697,2017-06-30 17:49:12 UTC,https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/i/iscsitarget/20170630_143836_ce64a@/log.gz
1701697,2017-07-13 15:52:48 UTC,"Hello Thadeu, or anyone else affected,"
1701701,2019-09-19 14:48:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1701722,2017-07-01 19:30:55 UTC,"Yeah, the original report contains misleading information. The issue also exists in older versions."
1701722,2017-07-01 20:54:57 UTC,"Yes, that was unfortunately a mistake by me, but who is perfect?"
1701722,2017-07-01 18:47:02 UTC,In that case it has something to do with the file length too. This file i'm testing with have 104 chars. For me it happens everytime i do it.
1701722,2017-07-01 08:00:53 UTC,I created directories 12345 and 67890 with some files in them and everything is working just fine
1701726,2017-06-30 20:44:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701726,2017-07-03 11:47:51 UTC,"Not sure if this is relevant (I don't really understand what it is telling me):
unattended-upgrades.log :
    While building minimal partition: cache has not allowed changes"
1701729,2017-06-30 20:17:27 UTC,new design
1701729,2017-06-30 20:17:46 UTC,preferred old design
1701729,2019-07-31 15:20:25 UTC,"The wifi-connect snap has been deprecated, as such I'm updating the Status to WontFix."
1701730,2019-07-31 15:20:54 UTC,"The wifi-connect snap has been deprecated, as such I'm updating the Status to WontFix."
1701731,2017-09-19 14:26:47 UTC,This bug was fixed in the package phpldapadmin - 1.2.2-5.2ubuntu2.1
1701731,2017-09-14 14:31:01 UTC,"Thanks for providing the debdiff. This package has been built and is available in the security-proposed PPA for testing.
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa"
1701731,2017-07-08 02:05:14 UTC,"Very nice, thanks; I've asked what I think is upstream for feedback https://github.com/leenooks/phpLDAPadmin/issues/50"
1701731,2017-07-01 18:00:06 UTC,Here is a debdiff.
1701731,2017-07-07 02:24:10 UTC,"Hello Ismail, thanks for taking on this task."
1701731,2017-07-01 20:26:19 UTC,"The attachment ""phpldapadmin_1.2.2-5.2ubuntu2.1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1701731,2017-07-01 02:34:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1701731,2017-07-07 13:42:19 UTC,"Hello Seth, Thank you for replying."
1701742,2018-03-22 06:21:24 UTC,Currently we are short-handed on the GUi development. I suggest to use GUI only as an status kanban. and use scripts to do deployment in an devops way.
1701745,2017-07-01 00:27:56 UTC,"The attachment ""reset xsession to default if selected user is not found, for example the guest user"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1701745,2017-09-21 00:52:08 UTC,"Thanks for the patch! Applied at the below commit.
http://bazaar.launchpad.net/~lightdm-gtk-greeter-team/lightdm-gtk-greeter/trunk/revision/370"
1701745,2017-09-21 00:54:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701745,2019-10-26 13:52:04 UTC,"Fixed in 2.0.3, Bionic has 2.0.5-0ubuntu1"
1701745,2017-06-30 22:45:48 UTC,Probably the same as https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1667719
1701756,2019-04-09 16:18:06 UTC,"it would be nice if at least the problematic characters will see reporting.
other than that - where is the naming convention that this rule set arises from?"
1701756,2019-04-09 17:05:51 UTC,tracked it down to this lines in the file dpkg-1.18.4ubuntu1/lib/dpkg/parsehelp.c at the end of function parseversion() at line #186:
1701756,2019-04-09 16:16:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701757,2017-07-05 15:30:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1701757,2017-07-06 01:39:00 UTC,"Greg, Sebastien, does this look like a duplicate of bug 1685754? It's tough for me to tell. Of course ~/.profile is only used by some shells, nothing else, so this may not be a bug at all."
1701757,2017-07-06 16:32:21 UTC,"Ubuntu bug 1685754 seems specific to gnome-terminal. The bug I reported is for all gnome-session apps. Gnome-terminal can be made to work if a umask is added to .bashrc. This is not the case for other gnome apps like gedit. These bugs may be the same, but I don't know enough to be able to make that call."
1701757,2017-07-12 18:17:33 UTC,"Excuse me, but is it fair to rank this bug as ""Low"" importance? There appears to be no way to change the default umask on account of this bug. Umask setting carries privacy and security considerations depending on environment."
1701757,2017-11-11 01:38:10 UTC,"Hello,"
1701757,2017-11-11 15:41:57 UTC,Files created with Gedit don't apply expected 002 umask.
1701757,2018-04-11 21:15:07 UTC,fwiw → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c44 → where security issue is mentioned
1701767,2017-07-01 19:39:41 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1701769,2017-12-09 23:56:46 UTC,I am still having this error.
1701769,2018-07-09 20:32:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701769,2017-12-10 00:23:25 UTC,"Hi Kourosh,"
1701779,2019-10-15 01:31:22 UTC,What is the status on this? RHOSP is switching the OVS-Firewall instead of IPTables.
1701779,2019-12-15 04:17:32 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1701779,2019-10-15 09:01:25 UTC,There are some upgrade path exist on neutron doc side https://docs.openstack.org/neutron/latest/contributor/internals/openvswitch_firewall.html#upgrade-path-from-iptables-hybrid-driver
1701779,2019-10-15 08:15:06 UTC,https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutron.html
1701779,2019-10-15 08:14:01 UTC,"We considered switching to it recently, but decided to document how to switch instead. IIRC the OVS firewall requires a newer kernel, and would not work on CentOS 7."
1701779,2018-09-28 10:37:13 UTC,Any update at this bug? proposed change was abandoned
1701779,2017-12-18 02:46:45 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/479465"
1701779,2017-07-01 06:12:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/479465"
1701788,2019-05-21 22:43:28 UTC,"Encountered the same situation...getting a recurring crash in plasmashell under Kubuntu 19.04 (but only when I've left the computer unattended for hours; it's never occurred when I'm sitting at the terminal).  Crash handler told me which debug symbols I needed for a useful bug report, so I found the appropriate packages and installed all of them (including 'plasma-workspace-dbgsym' for '/usr/bin/plasmashell'), but the crash handler still claims I am missing debug symbols for '/usr/bin/plasmashell'."
1701788,2017-09-26 18:02:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701790,2017-08-08 17:31:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701798,2017-07-01 11:23:51 UTC,"I would guess that the problem comes from a missing (or an extra) BSWAP call in one of the files
  include/elf.h
  include/hw/elf_ops.h
  linux-user/elfload.c"
1701798,2019-02-18 20:09:11 UTC,Did we open a precise glibc upstream bug for this so I can go upvote it? :-)
1701798,2018-07-27 11:16:14 UTC,"I believe this same bug affects me on Linux Mint 18.3 Sylvia which is based on Ubuntu Xenial.
The suggestion from #12 helped me. Thank you @bruno-clisp!"
1701798,2017-12-15 15:24:46 UTC,"I still feel we shouldn't be working around guest code bugs in QEMU, so I'm not sure there's anything more for QEMU to do here. You should report the dynamic linker bug to glibc upstream."
1701798,2017-11-08 20:05:27 UTC,"> You can probably also work around this by creating an empty ld.so.cache in the QEMU_LD_PREFIX directory, though it's awkward if you wanted that to be the /usr/whatever directory.
"
1701798,2017-11-07 22:30:09 UTC,"> That patch would prevent us from picking up a legitimate ld.so.cache for the guest (in a chroot, for instance), so I don't think we should take it.
But in a chroot, QEMU_LD_PREFIX is most likely NOT set. So how about this pseudocode?
"
1701798,2017-11-07 21:45:14 UTC,"That patch would prevent us from picking up a legitimate ld.so.cache for the guest (in a chroot, for instance), so I don't think we should take it. (I'm also not a fan of trying to work around specific guest code issues: I'd much rather this was just fixed in ld.so where it ought to be, so I'd encourage you to report it to the glibc folks.)"
1701798,2017-12-15 16:26:05 UTC,My feeling is that glibc upstream will not want to care about cross qemu situations. I would prefer to report it to the Ubuntu cross-tools maintainers: The package libc6-<cpu>-cross contains the file /usr/<cpu>-linux-gnu/lib/libc.so.6; they could surely add the symlink for /usr/<cpu>-linux-gnu/etc/ld.so.cache as well.
1701798,2017-11-07 20:52:16 UTC,"> can you still reproduce any of the other problems with a new QEMU?
"
1701798,2017-08-16 20:28:22 UTC,I think I hit this problem trying to use qemu-s390x-static in the s390x/ubuntu:16.04 docker image. Running qemu-s390x-static 2.9.0 on binaries in that image (e.g. /bin/echo) results in a hang.
1701798,2017-11-07 21:22:33 UTC,"Re #4:

>  2) files like /etc/ld.so.cache (and other things the dynamic linker uses) are not in the -L directory but are in the host
>  3) the ld.so.cache format is not endian-agnostic
>  4) glibc's dynamic linker code does not ignore a wrong-endian ld.so.cache but crashes instead
"
1701798,2017-08-31 21:50:11 UTC,"Can you check whether these work if you copy the QEMU and the dynamically linked target binary into a chroot (which does not have the x86 host ld.so or /etc in it) instead of using QEMU_LD_PREFIX ? There is a problem I've seen before where:
 1) QEMU when run with QEMU_LD_PREFIX or -L works by ""first try in -L, then try in the host filesystem""
 2) files like /etc/ld.so.cache (and other things the dynamic linker uses) are not in the -L directory but are in the host
 3) the ld.so.cache format is not endian-agnostic
 4) glibc's dynamic linker code does not ignore a wrong-endian ld.so.cache but crashes instead"
1701798,2017-08-31 21:35:24 UTC,The behaviour in qemu-2.10 is nearly the same as in qemu-2.9. The only difference is a different kind of crash for m68k:
1701798,2017-11-07 11:27:08 UTC,I just tested with powerpc and current head-of-git QEMU and it works:
1701798,2017-11-07 15:42:37 UTC,"This patch fixes the s390 issue:
https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg01103.html"
1701798,2017-09-01 19:01:57 UTC,"For s390x, the hang definitely still occurs using a chroot with qemu-s390x-static copied in and no QEMU_LD_PREFIX. I'm not in a good position to test other big-endian architectures though."
1701814,2017-07-25 07:47:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701815,2017-07-01 13:55:46 UTC,why this happen ?
1701835,2019-04-24 05:28:25 UTC,Commit https://git.qemu.org/?p=qemu.git;a=commitdiff;h=29eb528078683 claims that this has been fixed. Is the problem still reproducible with QEMU 4.0?
1701835,2019-08-16 04:52:32 UTC,https://git.qemu.org/?p=qemu.git;a=commitdiff;h=21ba856499f9c0ccdc
1701835,2019-05-21 14:24:38 UTC,Patch now merged to master and will be in QEMU 4.1.
1701835,2019-05-19 13:31:27 UTC,"The patch mentioned in #15 fixes the issue:
- The test programs test-cbrt ... test-truncf1 now all succeed.
- The test program from comment #6, run with qemu-alpha, prints 680e800000000000, i.e. bit 59 is set."
1701835,2019-04-25 21:59:53 UTC,There seems to be more confusion of the sort. This fixes it for me:
1701835,2019-04-24 13:41:03 UTC,"The problem is still reproducible with QEMU 4.0.0:
- The test programs test-cbrt ... test-truncf1 crash or abort as described.
- The test program from comment #6, run with qemu-alpha, prints 600e800000000000, i.e. bit 59 is unset."
1701835,2019-01-06 22:20:33 UTC,"No, it is not fixed: even with this patch the program that fetches the fpcr still prints 600e800000000000, and the various program crashes still occur."
1701835,2019-04-27 01:04:17 UTC,"There is quite a bit missing for proper user-level emulation.
Please try"
1701835,2019-01-06 01:31:02 UTC,"The fpcr value seen in a process running in a VM comes from the Linux kernel, file linux/arch/alpha/kernel/process.c, function flush_thread():"
1701835,2019-01-05 20:19:18 UTC,https://download.majix.org/dec/alpha_arch_ref.pdf
1701835,2019-01-05 19:17:48 UTC,Under qemu-system-alpha I get 680e800000000000 as well.
1701835,2019-01-05 18:28:30 UTC,Run this:
1701835,2019-01-04 20:44:27 UTC,Most likely some bits are initialized differently in the FPCR.
1701835,2019-01-04 20:30:04 UTC,"> You should try building with -mieee.
"
1701835,2019-01-04 15:57:24 UTC,This is likely expected/correct behavior. You should try building with -mieee.
1701835,2017-12-15 06:14:12 UTC,The behaviour in qemu-2.11 is the same as in qemu-2.9.
1701835,2019-01-06 08:34:05 UTC,Should be fixed by:
1701842,2017-09-03 10:25:07 UTC,"In my case the same happens for timed events as well, not just all day events."
1701842,2017-09-03 16:15:10 UTC,This issue has been previously reported and has just been fixed in master [1].
1701873,2017-07-08 05:07:56 UTC,Thanks for the update. I read through the page you recommend. This seems risky to me. I have -extra package installed. I don't know what will happen to my system if I uninstall them. Installing a kernel manually is not in my comfort zone. I prefer to automatically boot on the old one that risk to crash my whole system.
1701873,2017-07-02 07:10:12 UTC,Adding another attachment.
1701873,2017-07-05 21:14:10 UTC,As a workaround - I read that Ubuntu 16.04 new installs now get linux kernel 4.8 but even a dist-upgrade of an exiting system leaves you with 16.04.2 still with the 4.4 kernel. I was able to upgrade to the 4.8.0-58-generic kernel which was able to boot successfully by using the command (while booted to the older 4.4.0-81 kernel)
1701873,2017-07-06 15:34:58 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1701873,2017-07-02 07:30:08 UTC,This change was made by a bot.
1701879,2017-07-03 05:31:21 UTC,Could you provide an example file? That would make it easier to debug...
1701879,2017-07-03 11:57:51 UTC,Just a short explanation to the XML files.
1701879,2017-07-04 23:52:43 UTC,"This is might be because of Window's ""fancy"" characters (quotes, dashes and the like) that tend to mess things up?"
1701879,2017-07-05 03:08:04 UTC,"Hi,"
1701883,2017-09-03 01:06:09 UTC,"Same on Arch Linux, zim 0.67-1. An attempt to attach a file leads to"
1701884,2017-07-06 01:28:39 UTC,This may be a duplicate of bug 1692981.
1701885,2017-07-02 10:49:48 UTC,"No problem opening file here  with Win 8.1-64, Inkscape 0.92.1 r15371."
1701885,2020-09-22 06:58:38 UTC,Closing because INVALID: Can't replicate.
1701887,2017-07-07 21:48:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701887,2021-01-07 04:08:21 UTC,4.8 EOL
1701887,2017-07-02 19:39:10 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1701891,2017-07-02 11:22:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/479606"
1701917,2017-07-09 12:59:05 UTC,Here's another test script attached; I used it with xscreensaver 5.36.
1701917,2017-07-09 07:53:54 UTC,...But I prefer to disable the setting and add a launcher for sh -c 'xflock4 && xfce4-session-logout -s'
1701917,2017-07-09 07:11:50 UTC,As for 5.36 the speed varies:
1701917,2017-07-08 22:17:39 UTC,Except that the attached script operates significantly faster by xscreensaver 5.36 than by xscreensaver 5.15.
1701917,2017-07-09 07:50:51 UTC,"./test-xscreensaver.sh && xfce4-session-logout -s
seems to wait fading to finish before suspending to RAM. If I cp ./test-xscreensaver.sh to /usr/local/bin/xflock4 and set ""Lock screen before sleep"" enabled in ""Session and Startup"" settings, it does not wait, which is bad."
1701917,2017-07-08 19:10:23 UTC,Same thing by xscreensaver 5.36-1-ppa3~trusty
1701918,2017-07-11 02:15:19 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1701922,2021-01-07 04:08:15 UTC,4.8 EOL
1701922,2018-05-08 18:14:26 UTC,This change was made by a bot.
1701937,2017-07-11 02:21:51 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1701940,2018-02-11 04:52:00 UTC,"Removing packages from bionic:
 indicator-keylock 3.1.0 in bionic
  indicator-keylock 3.1.0 in bionic amd64
  indicator-keylock 3.1.0 in bionic arm64
  indicator-keylock 3.1.0 in bionic armhf
  indicator-keylock 3.1.0 in bionic i386
  indicator-keylock 3.1.0 in bionic ppc64el
  indicator-keylock 3.1.0 in bionic s390x
Comment: Depends on obsolete and to-be-removed libunique3; LP: #1701940
1 package successfully removed."
1701940,2017-11-27 19:00:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701942,2017-07-28 21:07:19 UTC,2017-07-28: I am happy to see that the marking bug of LibreOfficeWriter has vanished today after the last system update which involved switching from Linux kernel 4.8.0-58-generic x86_64 to 4.10.0-28-generic x86_64 plus a bundle of other upgrades.
1701944,2017-07-02 19:14:17 UTC,"Two screenshots:
Left is from builder
Right is the result"
1701966,2018-01-23 08:42:26 UTC,"Hi Joseph,"
1701966,2018-02-12 20:01:02 UTC,[me]$ glxinfo -B -l
1701966,2018-02-12 20:04:19 UTC,I don't use any other OpenGl games that I know of.
1701966,2019-09-16 18:00:02 UTC,Migrated to https://github.com/widelands/widelands/issues/1056
1701966,2018-01-22 19:08:58 UTC,widelands version bzr8560[widelands](Release)
1701966,2017-07-02 21:34:23 UTC,"I know that this hardware has limited OpenGL 2 support, so I join the glxinfo result."
1701966,2017-07-03 07:56:14 UTC,Thanks for reporting.
1701966,2017-07-03 09:14:17 UTC,"I am running Mageia 6, for which I help packaging, I don't build it myself but I can. The important point is that this hardware is so limited that Mesa announces OpenGL 1.4 if I don't enable two options through driconf, as explained here :"
1701966,2017-07-04 08:37:17 UTC,There are no changes planned to the OpenGL code for Build20.
1701966,2018-01-22 19:12:11 UTC,(#5 continued)
1701972,2018-05-08 18:14:39 UTC,This change was made by a bot.
1701972,2021-01-07 04:06:04 UTC,4.8 EOL
1701981,2017-07-03 13:54:58 UTC,"> /var/lib/dpkg/info/python-cairo.prerm: 6: /var/lib/dpkg/info/python-cairo.prerm: pyclean: not found
> /var/lib/dpkg/info/python-cairo.postinst: 6: /var/lib/dpkg/info/python-cairo.postinst: pycompile: not found
> /var/lib/dpkg/info/python-gobject-2.prerm: 6: /var/lib/dpkg/info/python-gobject-2.prerm: pyclean: not found
> /var/lib/dpkg/info/python-sip-dev.prerm: 6: /var/lib/dpkg/info/python-sip-dev.prerm: pyclean: not found
"
1701989,2017-07-11 06:17:03 UTC,"IMO, the help message of CLI shouldn't be long.  It's also nice to point out the docs which describe how to use of the CLI."
1701990,2017-07-14 16:09:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1701991,2017-08-07 16:28:31 UTC,"The vif attach/detach API was designed to specifically not include the port/portgroup ID to allow network drivers the most freedom to operate and handle the mappings. For example there are scenarios where there won't be an ironic ports for a node until a vif is attached when supporting composable hardware where NICs are created on the fly. Now that doesn't mean we can't support more advanced mapping like what your asking for, and this is something we've planned to do for a while, it seems to me that a better/more generic solution would be to provide a means to specify attachment hints, similar to Ironic's existing root device hints, where you could specify information like ""speed>=10gE,mac-address==<mac address>"" or ""type==infiniband"""
1701991,2017-11-13 22:27:52 UTC,"I'd like to see a spec for this, that describes the flow of information (how the hints get into the system, where they are stored, what hints are supported, etc.)"
1702007,2017-07-06 01:32:41 UTC,This bug may be a duplicate of bug 1692981.
1702007,2017-07-06 02:00:04 UTC,This change was made by a bot.
1702010,2018-05-08 18:14:54 UTC,This change was made by a bot.
1702010,2021-01-07 04:06:10 UTC,4.8 EOL
1702013,2018-05-13 17:49:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702015,2019-11-14 05:02:22 UTC,This looks like some issue with the old deja-dup-backend-gvfs package. That’s no longer a separate package.
1702020,2017-07-03 09:47:51 UTC,"allowing snap packages to use system themes has been discussed at the snappy sprint in london last week, it is still a bit until this feature will be fully available ... until then you can use one of the snapcraft desktop parts in your snap to have at least some default themeing behaviour shipped with it. there are a few discussions about this on the forum at https://forum.snapcraft.io"
1702020,2017-07-04 09:44:14 UTC,"Thanks, I'll pass that on to the developer of Filebot"
1702020,2019-09-26 10:45:08 UTC,"Marking as invalid for snapd itself, as it's not a bug in snapd --- the snap needs to do a bit of work to pick up themes."
1702022,2017-07-03 09:45:26 UTC,A workaround you can use is to mount your disk under /media/$USER/ and use the removable-media interface to give your app access to this.
1702022,2019-09-26 10:55:42 UTC,I agree this would be nice.
1702022,2020-05-28 18:17:44 UTC,This limitation is the reason why I rarely use snaps. It make using a lot of programs way too cumbersome.
1702043,2017-07-03 09:26:15 UTC,"StacktraceTop:
 ?? ()
 XGetScreenSaver (dpy=0x55a6ecad4100, timeout=timeout@entry=0x7fff4a0062d8, interval=interval@entry=0x7fff4a0062dc, prefer_blanking=prefer_blanking@entry=0x7fff4a0062e0, allow_exp=allow_exp@entry=0x7fff4a0062e4) at ../../src/GetSSaver.c:44
 disable_builtin_screensaver (unblank_screen=0, watcher=<error reading variable: value has been optimized out>) at gs-watcher-x11.c:539
 watchdog_timer (watcher=<error reading variable: value has been optimized out>) at gs-watcher-x11.c:609
 g_timeout_dispatch (source=0x55a6ecc10bf0, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4629"
1702043,2017-10-26 11:29:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702043,2017-10-26 11:34:29 UTC,gnome-screensaver shouldn't be started under wayland sessions since it's not going to work there
1702043,2020-05-18 13:48:25 UTC,Old problem about Ubuntu 17.10. Changed status to invalid.
1702044,2017-07-05 06:43:45 UTC,"confirmed, however not yet reproducible when building from the preprocessed source. Not found in GCC 5 and GCC 7. Possible work arounds: Build the test with -O0, or -save-temps"
1702044,2017-07-03 09:20:46 UTC,(attached build log for persistence as well)
1702059,2017-09-20 15:53:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702059,2017-10-04 15:11:57 UTC,It is possible to override the --root option by creating an /etc/debmirror.conf file with the appropriate entry to override the default:
1702059,2017-10-04 15:26:24 UTC,It is possible to bypass the default root entry by creating /etc/debmirror.conf with the following entry:
1702059,2017-10-04 15:32:20 UTC,"Ah ok,
thanks for the input."
1702059,2019-11-29 13:37:18 UTC,"Hello,"
1702059,2019-11-29 13:45:58 UTC,"Sorry, little mistake in my previous comment,
it's not:
sed -i '/^$remoteroot =~.*/i $remoteroot =~ s|/?$|/| ;' /usr/bin/debmirror
But:
sed -i '/^$remoteroot =~.*/i $remoteroot =~ s|\/?$|\/| ;' /usr/bin/debmirror"
1702066,2017-07-07 12:40:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/481615"
1702071,2020-02-07 21:02:29 UTC,Still an issue on 19.10 and 20.04
1702071,2018-11-14 09:22:01 UTC,This is still a problem on Ubuntu 18.10:
1702071,2017-07-20 09:35:55 UTC,Laney says it's the same issue than https://bugzilla.gnome.org/show_bug.cgi?id=784251 which is fixed upstream now
1702071,2017-07-09 12:30:57 UTC,I am seeing this on a fresh install of Artful. In addition to the search running forever (or at least a long time) there are no apps to be seen in the various categories (just rectangles with ... inside) and the featured app and editor's picks just show dots.
1702071,2017-07-17 22:46:09 UTC,Colin - probably best to file a new bug and we can close as a duplicate if the same cause.
1702071,2017-07-17 22:45:28 UTC,Icon issue is bug 1704888
1702071,2017-07-04 03:25:17 UTC,"There's one thing I noticed in there, I think the pin-town icon is larger than the snap plugin can handle - can you confirm if this occurs after uninstalling pin-town? I don't think this is related but worth checking (and I'll fix that anyway)."
1702071,2017-07-18 08:18:30 UTC,Robert - yes I think you are right. In fact the issue went away after I rebooted (at least I think that was what did it). I need to re-install the OS and see if it happens again.
1702079,2017-07-04 08:03:45 UTC,"Yes, links to child pages should be updates as well, however the error probably happened before this was finished resulting in an ""in between"" state."
1702079,2017-07-04 12:58:27 UTC,"No need to do so on my account. With the way I'm working on this, a reason to methodically review each page is helpful, and I don't encounter the bug often enough to be a problem."
1702081,2020-07-01 21:19:02 UTC,"There has been no report since 18.10, closing"
1702104,2017-07-03 14:06:41 UTC,"The following 3 patches were skipped as they have already been applied when fixing up the kernel for CVE-2017-1000364:
 - mm: larger stack guard gap, between vmas
 - Allow stack to grow up to address space limit
 - mm: fix new crash in unmapped_area_topdown()"
1702104,2017-08-03 16:32:17 UTC,This bug was fixed in the package linux - 4.4.0-89.112
1702118,2017-08-03 16:32:17 UTC,This bug was fixed in the package linux - 4.4.0-89.112
1702118,2017-07-03 15:09:24 UTC,"Patch ""time: Fix clock->read(clock) race around clocksource changes"" applied but with fuzz 1."
1702118,2017-07-03 16:03:26 UTC,"Patch ""time: Fix clock->read(clock) race around clocksource changes"" had to be fixed up because we backported the following patches for bug #1519625 ""Always Running Timer (ART) to System Time translation"":
* time: Add timekeeping snapshot code capturing system time and counter
* time: Add history to cross timestamp interface supporting slower devices"
1702119,2017-07-06 07:33:31 UTC,Fixed in rev 1c815a028afc.
1702125,2018-10-04 15:28:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702130,2018-07-12 17:13:36 UTC,"Thanks Colin, this has been working great for me!
I can confirm that my previously failing builds with ant plugin are now working just fine, including opengrok snap."
1702130,2017-10-25 13:22:11 UTC,Also affecting jabref (https://build.snapcraft.io/user/JabRef/jabref/97443):
1702130,2017-10-25 13:25:35 UTC,"My previous comment may be a snapcraft bug. Adam fixed some issues with gradle and proxies in https://github.com/snapcore/snapcraft/pull/1490, but you can see http.proxyUser in these logs so there's evidently still something going on."
1702130,2017-10-11 12:55:22 UTC,"I tested again, and I actually pasted wrong build log, anyway here is correct one:
https://launchpadlibrarian.net/340422375/buildlog_snap_ubuntu_xenial_amd64_opengrok-snap_BUILDING.txt.gz
using snap craft.yaml
https://git.launchpad.net/~ondrak/ondras-snaps/+git/opengrok-snap/tree/snapcraft.yaml"
1702130,2018-06-10 13:54:36 UTC,"I've just merged https://code.launchpad.net/~cjwatson/launchpad-buildd/local-snap-proxy/+merge/322545.  In local testing, with launchpad-buildd running in a suitably-firewalled VM and a local deployment of snap-proxy, this fixes a number of problems in this area: for example, the cases reported in bug 1690834 and bug 1753340 now build cleanly, as does jabref.  In short, anything whose problem is just that it doesn't pass through proxy authentication details now works, which deals with quite a few disparate build systems."
1702130,2017-07-04 12:38:24 UTC,"Ah, I skimmed past local-snap-proxy on my first read. Any idea when that might land?"
1702130,2017-07-04 11:07:57 UTC,"Ah interesting. I'm using the ant plugin directly (cassandra, not snapcraft):
https://github.com/snapcrafters/cassandra/blob/master/snapcraft.yaml"
1702130,2017-07-03 23:57:27 UTC,"Actually, it looks like I filed https://github.com/snapcore/snapcraft/pull/1256 after those local attempts and got it landed, so it may well be that local-snap-proxy is all that this needs now.  I'll give it another try locally at some point and see what happens."
1702130,2017-07-03 23:45:00 UTC,"As I recall I got quite a way through debugging this and https://code.launchpad.net/~cjwatson/launchpad-buildd/local-snap-proxy/+merge/322545 was a big help, but the build logs in my local Launchpad instance suggest that that wasn't enough.  With local-snap-proxy applied, it looks like I ended up with this:"
1702130,2017-10-11 12:40:39 UTC,Ant and gradle fixes landed in https://github.com/snapcore/snapcraft/pull/1490 - still need to see if that fixes the issue
1702151,2019-10-02 19:45:12 UTC,"Ben, sorry I didn't notice your comment"
1702151,2019-05-20 19:35:24 UTC,I'm on 19.04 and I seem to be able to reproduce this at least once a day while I leave my screen locked overnight.
1702151,2019-03-27 16:40:08 UTC,Actually not... I misread the title.
1702151,2019-03-08 12:16:38 UTC,This is going to be fixed by https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/438
1702151,2018-10-04 20:01:13 UTC,"I agree, it's just quite hard to reproduce."
1702151,2019-05-03 22:31:44 UTC,"Similar issues in other distros:
 - https://bugzilla.redhat.com/show_bug.cgi?id=1494586
 - https://bugzilla.redhat.com/show_bug.cgi?id=1511704
 - https://bugs.centos.org/view.php?id=15970"
1702151,2018-08-01 21:48:38 UTC,Anyone affected here who can provide a full jouralctl log?
1702151,2018-03-27 08:19:44 UTC,"Tracking in:
https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d"
1702151,2017-10-19 16:55:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702151,2017-07-04 01:53:11 UTC,"Also similar to:
https://errors.ubuntu.com/problem/e9dbfbbbc04ccca9d8012dd11f60e810e033d7ac"
1702151,2017-07-04 01:52:10 UTC,"Sounds similar to bug 1702203, but a bit different."
1702151,2018-10-04 02:11:41 UTC,It would be better if this bug did not expire. It is confirmed by almost 3000 crash reports from 18.04/18.10 on errors.ubuntu.com.
1702151,2017-07-03 18:28:55 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x563538c8ee40, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x563538c8ee40) at ../../../../gobject/gobject.c:3180
 st_theme_get_custom_stylesheets (theme=0x56353d1bca80) at st/st-theme.c:311
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x56352dc4e538, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffe7a6c85e8, avalue=avalue@entry=0x7ffe7a6c84c0) at ../src/x86/ffi64.c:525"
1702161,2018-05-11 15:32:44 UTC,This change was made by a bot.
1702161,2021-01-07 04:08:11 UTC,4.8 EOL
1702164,2017-07-06 08:18:25 UTC,"sorry:
it's up since 2 days without crashes."
1702164,2017-07-07 19:51:41 UTC,"Sorry if this not the proper way to ask, but I think I may have the same problem (with a Clevo P150SM laptop), and asked for help on https://askubuntu.com/questions/933015/ubuntu-16-04-kernel-4-4-0-83-panic-fatal-exception-in-interrupt"
1702164,2017-07-07 20:30:46 UTC,"Joao, it's probably best to run ubuntu-bug linux to file a new report; that should automatically attach what it can from the logs. Your photo may be useful too. (I know it just reports a ""warning"" but that might be useful all the same.)"
1702164,2017-07-08 09:17:07 UTC,"Today, kernel 4.4.0-83 its booting fine (and it doesn't crash/hang on boot)."
1702164,2017-07-21 19:15:47 UTC,"We are experiencing these intermittent kernel panics running a very similar setup; using Apache Mesos and docker.  Due to security reasons, we are not able to run a previous version kernel due to the fixes included in 4.4.0-83 to address CVE-2017-1000364."
1702164,2017-07-20 15:10:19 UTC,"We are also seeing relatively frequent kernel panics using 4.4.0-83. We run an Apache Mesos cluster using the docker containerizer. The description of LP #1687512 appears to match quite nicely with our configuration (cgroups enabled with small allocations). That issue appears to have been addressed in 4.4.0-79, but perhaps this is related."
1702164,2017-07-24 19:48:50 UTC,"Below is a stack trace from kern.log for one of the hosts.  For security reasons, I have redacted the hostname from the output.  Stack traces for other machines also mention /build/linux-0uniEn/linux-4.4.0/net/ipv6/addrconf_core.c:160 in6_dev_finish_destroy. Hopefully, this may prove useful:"
1702164,2017-07-06 07:38:42 UTC,"Yes, I restored last kernel on another VM, and it worked fine
But panic just removed after kernel crashed, and server rebooted by itself 3 times.
it's up since 2 days with crash."
1702164,2017-07-08 09:42:39 UTC,Ooops! My first contact with ubuntu-bug was a bit messy. I seem to have reported #1703091
1702164,2017-07-05 18:39:08 UTC,Does the panic go away if you boot back into the prior kernel version?
1702164,2017-07-04 14:29:59 UTC,apport information
1702164,2017-07-04 14:30:05 UTC,apport information
1702164,2017-07-04 14:30:08 UTC,apport information
1702164,2017-07-04 14:29:54 UTC,apport information
1702164,2017-07-04 14:29:57 UTC,apport information
1702164,2017-07-04 14:29:58 UTC,apport information
1702164,2017-07-03 19:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1702164,2017-07-04 14:30:01 UTC,apport information
1702164,2017-07-04 14:30:02 UTC,apport information
1702164,2017-07-04 14:30:03 UTC,apport information
1702164,2017-07-04 14:30:00 UTC,apport information
1702172,2018-01-29 10:44:38 UTC,"On Sylvia, it is is not showing."
1702174,2017-07-04 07:14:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702186,2017-07-05 01:03:30 UTC,As far as I can tell this is pretty much how LXCs and workspaces are set up in Mojo.  The only difference from my local LXC-enabled projects is ROOTFS being a directory (on my machine it's a symlink back to /var/lib/lxc/mojo-foo.xenial/rootfs) but this may be something to do with how we create containers in CI and our desire to not store them in /var/lib/lxc.  I'm not seeing from this description where the second LXC image comes into the picture.
1702186,2017-07-05 02:25:31 UTC,"I found a mojo workspaces cleanup script deployed in the previous CI environment and it has recovered 150G (and counting) on the current environment.  I don't think there's a Mojo bug here, at least w/r/t containers."
1702186,2017-07-05 15:14:00 UTC,"That is good that there doesn't seem to be a bug regarding containers, I do think we should still consider this a bug for the Jenkins scripts. The need to manually run a special cleanup script is a bug in my opinion. The Jenkins scripts should include a workspace cleanup step whether that is cleanup done every run or only when workspace numbers exceed a threshold either way it should happen in normal running without manual SRE intervention."
1702187,2018-06-08 00:20:04 UTC,Still present in bionic.
1702187,2018-06-08 00:19:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702187,2017-09-22 20:23:37 UTC,unity-lens-files 7.1.0+17.10.20170605-0ubuntu1 also suffers from the same problem.
1702187,2017-09-22 20:28:23 UTC,The original report only emphasizes that the relevant file(s) should be shipped by language-pack-whatever instead.
1702187,2017-07-04 08:31:17 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1702187,2017-09-22 20:42:51 UTC,"On 2017-09-22 04:28 PM, Egmont Koblinger wrote:

> What I do care about, however, is that these misplaced files break my
> old habit of typing (and pressing the [TAB] key) ""cd
> /usr/lo[TAB]sh[TAB]"" to take me to ""/usr/local/share"". Autocompletion no
> longer completes to ""local/"" with the trailing slash since ""locale"" is
> another possibility.
"
1702191,2017-07-17 15:38:10 UTC,Really? No one uses 1280x800 with scaling? This is a major problem. I can't play OR multiplayer because the button is cut off.
1702204,2017-08-12 13:53:08 UTC,"FYI, I reported this bug upstream a few days after reporting it here, and it has been fixed, but not released yet. It will be released in an upcoming version of Subversion 1.9.x. It would be great if the fix could be backported to 16.04. The fix is in these two commits:"
1702204,2018-08-04 17:50:40 UTC,The fix for this bug was released upstream in Subversion 1.9.9. It would be great if the fix could be ported into 16.04 and 18.04.
1702206,2017-07-04 04:35:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1702215,2019-09-09 05:41:56 UTC,"I think this failure has been fixed by other work in the area since this
report was filed."
1702223,2017-07-24 17:45:41 UTC,Does not work
1702223,2017-07-04 07:51:12 UTC,"Put ""options snd-hda-intel model=mba42"" to the last line of /etc/modprobe.d/alsa-base.conf"
1702223,2017-07-05 11:12:57 UTC,"@Richard, does it work?"
1702223,2017-07-04 06:28:40 UTC,"It works for MacBook Pro.
It seems audio is erroneously processed as surround sound, the chip has a multiple of channel configurations"
1702223,2017-07-04 06:27:34 UTC,"One can also do Test Speakers in GNOME settings Sound, this also produces mono for headset but works for internal speakers"
1702223,2017-07-04 06:30:33 UTC,This change was made by a bot.
1702225,2017-07-06 02:33:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702225,2021-01-07 04:08:47 UTC,4.8 EOL
1702226,2017-07-04 15:34:23 UTC,"This is quite similar to https://github.com/mixxxdj/mixxx/pull/355
We probably just need to tweak the knob ranges and the effect name.
If that does not work, we may add or replace an EQ band from our graphic EQ."
1702253,2017-07-07 03:20:22 UTC,Huawei have fix this bug and provide patch to our team that will be merged in 4.12.
1702253,2017-07-05 09:43:03 UTC,We found same problem on Ubuntu17.04 the kernel version is linux-image-4.10.0-19-generic上. The apport report is in the attachment file.
1702253,2019-10-03 10:38:50 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1702253,2017-07-04 11:10:32 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1702253,2017-07-04 13:44:49 UTC,It is Ubuntu server without Desktop environment and I can't provide my launchpad access to customer too.
1702253,2017-07-04 11:08:14 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1702256,2017-07-05 14:35:08 UTC,Waiting on @redriver to get back.  Please re-open when ready.
1702256,2017-07-06 02:14:47 UTC,"I found the root cause: the script cloudinitlocal does not run because it has a circular dependence, which stifles the ""cloud-init init --local"". As a result, cloud-init fails for FreeBSD on Azure."
1702256,2017-07-04 09:57:41 UTC,This regression happens for cloudinit on FreeBSD.
1702256,2017-07-04 10:39:41 UTC,"It looks like ""cloud-init init --local"" does not work as expected. Let me check it further."
1702258,2020-03-30 02:41:02 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1702265,2018-10-21 16:47:19 UTC,apport information
1702265,2018-10-21 16:47:20 UTC,apport information
1702265,2018-10-21 16:47:21 UTC,apport information
1702265,2018-10-21 16:47:17 UTC,apport information
1702265,2018-10-21 16:47:22 UTC,apport information
1702265,2018-10-21 16:47:23 UTC,apport information
1702265,2018-10-21 16:47:25 UTC,apport information
1702265,2018-10-21 16:47:35 UTC,apport information
1702265,2018-10-21 16:47:27 UTC,apport information
1702265,2018-10-21 16:47:29 UTC,apport information
1702265,2018-10-21 16:47:32 UTC,apport information
1702265,2018-10-25 05:33:29 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0]."
1702265,2018-10-29 12:50:10 UTC,Same behaviour on kernel v4.19.
1702265,2019-03-05 11:34:41 UTC,"Possible to re-test v5.0? If it doesn't solve the issue, a kernel bisection is needed."
1702265,2018-10-21 16:47:16 UTC,apport information
1702265,2018-10-21 16:47:26 UTC,apport information
1702265,2018-10-21 16:47:13 UTC,apport information
1702265,2018-10-21 15:24:46 UTC,apport information
1702265,2018-10-21 15:24:57 UTC,apport information
1702265,2018-05-11 15:32:52 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1702265,2018-07-11 04:17:35 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1702265,2018-10-21 15:24:36 UTC,apport information
1702265,2018-10-21 15:24:38 UTC,apport information
1702265,2018-10-21 15:24:39 UTC,apport information
1702265,2018-10-21 15:24:41 UTC,apport information
1702265,2018-10-21 16:47:11 UTC,apport information
1702265,2018-10-21 15:24:42 UTC,apport information
1702265,2018-10-21 15:24:44 UTC,apport information
1702265,2018-10-21 15:24:47 UTC,apport information
1702265,2018-10-21 15:24:48 UTC,apport information
1702265,2018-10-21 15:24:49 UTC,apport information
1702265,2018-10-21 15:24:51 UTC,apport information
1702265,2018-10-21 15:24:52 UTC,apport information
1702265,2018-10-21 15:24:55 UTC,apport information
1702265,2018-10-21 15:24:43 UTC,apport information
1702270,2017-08-29 07:34:53 UTC,"For graceful shutdown user need to mention hook ( --hook-master-start ""unix_signal:15 gracefully_kill_them_all"") while starting the service."
1702278,2019-01-07 11:28:05 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/483323
Reason: Marking this review as abandoned due to lack of activity in the past 6 months."
1702278,2017-07-13 12:49:46 UTC,The issue I have with this is that Cisco ACI really should deduce which API version to use by other means.
1702278,2017-07-13 14:01:45 UTC,Have submitted a change for review.
1702278,2017-07-27 14:16:03 UTC,Marking Keystone task as invalid (its already passing the data - so any updates will be scoped to neutron-api).
1702290,2017-08-30 04:01:17 UTC,"Hello,"
1702290,2018-06-27 09:40:58 UTC,"This is essentially a config change breaking the service (re)start. and due to that upgrades.
While the init could be more resilient it is not really a bug but a misconfiguration as identified by Ryan already."
1702290,2018-06-27 09:41:06 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1702307,2017-11-26 17:51:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702309,2017-07-04 21:38:13 UTC,"Yes, we run the leadership workers for each state. I believe the leadership worker is only interested in docs for its own model."
1702309,2017-07-05 04:02:21 UTC,"So its possible that this is one for the 'default' model and one for the 'controller'. I'll need a bit more debugging.
However, I'm also seeing a lot more other churn that surprises me. It seems the restarts might now be out of sync after running the machines overnight.
However:"
1702309,2017-07-11 11:49:09 UTC,"It sounds like its by design (for now) that we run multiple leadership workers, and it shouldn't be bad as long as they are coordinating via the database, nobody should get a lease they shouldn't, and one of those workers just won't actually be managing anything. I'll note that we do still see things like:
machine-0: 15:42:24 DEBUG juju.worker.lease waking to check leases at 2017-07-11 11:43:24.55755107 +0000 UTC
machine-0: 15:42:24 DEBUG juju.worker.lease waking to check leases at 2017-07-11 11:43:24.561946773 +0000 UTC
machine-0: 15:42:24 DEBUG juju.worker.lease waking to check leases at 2017-07-11 11:43:24.778777446 +0000 UTC
machine-0: 15:42:24 DEBUG juju.worker.lease waking to check leases at 2017-07-11 11:43:24.799138555 +0000 UTC"
1702309,2018-03-22 06:00:47 UTC,We will not be fixing this in 2.2 as there are no further point releases planned in this series.
1702315,2017-07-04 14:32:09 UTC,"in 90 % aller Starts, also beim Hochfahren, muss ich die Stromzufuhr unterbrechen, neu einstecken und erst beim zweiten Versuch gelingt dann endlich der Start!!!"
1702319,2017-09-07 21:34:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702320,2017-07-04 21:15:03 UTC,"This is not a bug of cups-filters, but a bug in the set of UDEV rules which comes with Linux distributions. To support your USB->Serial adapter correctly the UDEV rule which you mention in the upstream bug report needs to be added. And as such adapters support not only printers cups-filters is the wrong place for adding this UDEV rule."
1702320,2017-07-21 19:22:14 UTC,"As reported in referenced bug, udev rule is a workaround. The real problem is TCSADRAIN that don't work correctly with usb to serial adapters. I don’t know if it's a bug related to kernel or to some others library."
1702323,2017-07-17 14:40:50 UTC,"A bit more information about my hardware setup.
This is a FUJITSU PRIMERGY RX2510 M22 x Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz (8 cores in each processor)
RAM 128GB
Swap 11GB"
1702323,2017-07-04 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1702323,2017-07-06 14:40:42 UTC,"Hi,
I'm in a loop. I try to run 'apport-collect 1702323' as instructed and I get a message saying I need to run 'apt-get install python-apport'.
I run 'apt-get install python-apport' and I get a message saying dpkg was interrupted run 'dpkg --configure -a'
I run 'dpkg --configure -a' and it hangs on 'update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic'
It will stay like this forever so I have to crash out of this and an unable to do any updates.
Any advice is gratefully welcomed.
Kind regards
Max"
1702324,2017-07-04 15:53:59 UTC,This bug came out of discussion in https://review.openstack.org/#/c/455174/56/mistralclient/api/httpclient.py . So there might be a need in this header.
1702324,2017-07-05 08:26:20 UTC,This is a duplicate for https://bugs.launchpad.net/mistral/+bug/1699248.
1702326,2017-07-04 15:29:34 UTC,"I might be re-using this bug for the matching changes in xenial and yakkety, unless these are subsets."
1702326,2017-07-04 15:43:12 UTC,Added link to the Debian stretch-pu bug.
1702326,2017-09-13 18:01:28 UTC,"Sorry for the status noise, I sometimes keep forgetting that statuses have a very different meaning for SRUs than for normal uploads."
1702326,2017-09-29 13:14:09 UTC,"Hello Julian, or anyone else affected,"
1702326,2017-09-29 13:17:33 UTC,"Hello Julian, or anyone else affected,"
1702326,2017-11-11 19:45:38 UTC,"I used 1.4.8 and 1.2.25 now for some time, and there seem to be no regressions. The autopkgtests for zesty fail in a flaky test case, I should eventually backport the disablement of that."
1702326,2018-02-14 01:05:15 UTC,This bug was fixed in the package apt - 1.2.25
1702326,2018-02-14 01:05:39 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1702328,2017-07-05 13:43:35 UTC,This issue was fixed in the openstack/openstackdocstheme 1.13.0 release.
1702328,2017-07-04 15:52:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480242"
1702328,2017-07-04 16:27:43 UTC,"Reviewed:  https://review.openstack.org/480242
Committed: https://git.openstack.org/cgit/openstack/openstackdocstheme/commit/?id=d727e522b910e29b245d394cb8199a67477dd157
Submitter: Jenkins
Branch:    master"
1702332,2017-07-05 19:12:58 UTC,"Ideally this should be handled directly by MaaS, or disable the unrelated services (such as snapd)."
1702332,2017-07-07 19:42:20 UTC,"The proxy is configured by cloud-init. I'd think that cloud-init would need to gain support for configuring the system proxy as well, and in MAAS, there should be an option that allows to select the user whether to enable this only for APT, or system wide."
1702332,2017-07-07 22:55:45 UTC,"Also, FWIW, since MAAS does only OS deployments (and not application deployments) MAAS only sets the APT proxy, as it is the only thing needed to deploy the machine."
1702332,2019-09-19 12:04:03 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1702335,2018-04-27 23:23:27 UTC,See also bug 1767522
1702335,2017-07-10 08:38:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702335,2017-07-26 05:39:07 UTC,whenever i installed something it work but gave me an error message about grub.Today i installed an app from software center and it crashed.
1702342,2017-07-05 10:34:47 UTC,"Which version of Brewtarget are you using?
Also which OS are you running it under?
Would it be possible to get a copy of your database to test with?"
1702342,2017-07-05 17:28:15 UTC,I am going to create a copy of this bug report at https://github.com/Brewtarget/brewtarget/issues .
1702342,2017-07-06 13:10:10 UTC,"On 05/07/2017 12:34, Daniel Pettersson wrote:

> Which version of Brewtarget are you using?
"
1702348,2017-07-23 07:10:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702351,2018-05-07 13:46:22 UTC,Hey.
1702351,2018-05-07 14:49:35 UTC,Hi!
1702351,2018-05-07 19:58:10 UTC,Hi Olivier!
1702351,2017-08-10 19:02:23 UTC,"So that looks like a more general problem, which potentially affects other snaps, not just libreoffice."
1702351,2018-05-07 20:36:19 UTC,"Olivier,"
1702351,2018-05-08 21:39:14 UTC,"Okay, so it looks like the traceback might have been a one-off."
1702351,2018-05-08 21:49:50 UTC,After rm...
1702351,2018-05-07 20:17:04 UTC,That looks correct.
1702351,2017-07-13 18:28:14 UTC,"Hi,"
1702351,2018-05-07 19:36:48 UTC,"Thanks for the feedback Marcelo.
The python traceback (""AttributeError: 'NoneType' object has no attribute 'group'"") is unexpected, may I ask you to share the output of the following command:"
1702351,2017-07-06 18:49:16 UTC,To make everything more complicated ...
1702351,2017-07-06 15:34:24 UTC,Libreoffice works very well from repositories!
1702351,2017-07-06 14:03:57 UTC,Thanks for the feedback Marcelo. Does libreoffice from the ubuntu repositories (not the snap package) work well in that setup?
1702351,2017-07-05 15:10:35 UTC,"Thank you for your bug report, you wrote ""This error occurs"" in the description but it looks like you didn't include the actual error?"
1702351,2017-07-06 13:52:22 UTC,Hi!
1702351,2017-07-06 04:59:01 UTC,"Interesting. Are you able to install and run other snaps in that setup, or do they all fail with the same error message?"
1702351,2017-07-05 18:51:55 UTC,I believe it is not possible to create local groups with words separated by spaces!
1702351,2017-07-05 18:29:31 UTC,"Thanks for the report modolo. May I ask how you create a group with a name that has whitespaces?
I tried `sudo addgroup --force-badname ""domain users""` but this bails out, refusing to create the group."
1702351,2017-07-05 16:11:34 UTC,Pardon!
1702351,2017-07-07 16:56:54 UTC,Hi!
1702360,2017-07-05 07:45:11 UTC,"> Should user-tmp have:
> owner /run/user/[0-9]/**
> ?
"
1702368,2017-07-04 22:50:28 UTC,apport information
1702368,2017-07-04 22:50:30 UTC,apport information
1702368,2017-07-06 07:21:58 UTC,I'm also hitting this with:
1702368,2020-08-26 11:42:48 UTC,This issue seems to have been fixed as of 5.8.3 kernel.
1702368,2017-09-01 06:18:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702368,2017-09-01 06:21:23 UTC,"I'm consistently seeing this on Zesty (linux-image-4.10.0-33-generic), the same fuse mount didn't prevent suspending before Ubuntu 17.04:"
1702368,2019-11-06 17:24:49 UTC,"If it's any bit of helpful information, I occasionally have this issue (on 18.04) and it is fixed by a proper shutdown and boot. It seems to happen for me when one of the servers that I sshfs to crashes/becomes unavailable (or something else server side) and the issue persists past the time in which the server is back and functional."
1702368,2017-07-04 22:50:25 UTC,apport information
1702368,2017-07-06 07:23:31 UTC,"A workaround for my gvim-based hang is to not have gvim open on the sshfs when I suspend. I don't have that option with gsd-housekeeping, so I basically have to unmount sshfs before suspend, which breaks everything else (eg. open bash prompts). Using ""sshfs -o reconnect"" works fine except for this."
1702368,2017-07-04 22:50:24 UTC,apport information
1702368,2017-07-04 22:50:27 UTC,apport information
1702368,2017-07-04 22:50:22 UTC,apport information
1702368,2017-07-04 22:50:21 UTC,apport information
1702368,2017-07-04 22:50:20 UTC,apport information
1702368,2017-07-04 22:50:18 UTC,apport information
1702368,2017-07-04 22:50:17 UTC,apport information
1702368,2017-07-04 22:50:15 UTC,apport information
1702368,2017-07-04 22:50:13 UTC,apport information
1702368,2017-07-04 22:50:12 UTC,apport information
1702368,2017-07-04 22:50:11 UTC,apport information
1702368,2017-07-04 22:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1702368,2017-07-04 22:50:24 UTC,apport information
1702369,2020-03-16 01:14:11 UTC,This seems to work for me.
1702369,2020-03-17 01:18:31 UTC,Fixed in rev 1833:
1702378,2017-08-17 07:03:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702381,2017-07-27 00:08:03 UTC,imposible instalar libc6-dev amd642.23-oubuntu9
1702382,2017-07-05 00:38:06 UTC,"The suggestion from comment is to revert the -x removal when upstream has merged, but who knows how long that can take to get into stable kernels."
1702382,2017-10-22 22:40:02 UTC,"Change abandoned by Jamie Lennox (<email address hidden>) on branch: master
Review: https://review.openstack.org/476732"
1702382,2019-01-25 18:21:25 UTC,"Hi, I have run into this bug year later, we have a ConcourseCI system that is supposed to use diskimage-builder to build images and this bug seems similar to our issue"
1702382,2019-01-25 18:26:33 UTC,Paste with the actual relevant lines
1702382,2019-06-26 16:02:43 UTC,"Hi, this bug is still present for disk-image-create version 2.24.0"
1702382,2019-06-26 17:35:15 UTC,"I should add that this was happening with a Debian 9.9 environment, kernel 4.9."
1702387,2017-07-05 02:00:03 UTC,This change was made by a bot.
1702408,2017-11-09 09:01:58 UTC,"3) How index descriptors are sorted during table creation?
Their initial order is the same as in the table definition,
see mysql_execute_command():"
1702408,2017-11-09 09:27:09 UTC,"I don't have any ideas how to fix it. If we does not have metadata, i.e. index names in correspondent order, then it looks like there is no way to map dictionary indexes on index root pages in innodb tablespace."
1702408,2017-11-09 09:14:24 UTC,https://bugs.mysql.com/bug.php?id=88418
1702408,2017-11-08 15:44:53 UTC,The detailed description is the following. How the initial data led to the indexes order issue see item 1 in https://percona.zendesk.com/attachments/token/EzERiNDmk8a1gJjtQMhPfA7Dv/?name=descr.txt.
1702408,2018-01-25 09:12:46 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1104
1702408,2017-07-19 11:05:29 UTC,"Not, because issue is repeatable only with sensitive data, attached to our ticket, so we do not have test case which can be shared with Oracle."
1702408,2017-07-18 03:48:34 UTC,Is there an upstream bug report?
1702408,2017-07-17 19:02:52 UTC,Bug is repeatable with upstream
1702408,2017-07-10 03:47:11 UTC,check i196447 for ibd and table structure file required for reproducing.
1702408,2017-11-07 14:57:52 UTC,"Briefly. When we create table it's dictionary contains the description of indexes in the certain order. In the case if we import tablespace for the table without cfg file(which contains metadata for indexes as well), there can be the case when the order of indexes in innodb dictionary (in .frm file as well) is not the same as the order of root pages for the indexes in tablespace file what cause the error during tablespace import or when the indexes are used."
1702421,2017-07-05 12:51:49 UTC,"After more thinking, it seems that in order to support the use case mentioned in the description (fetching all top level executions) we can just add the new parameter to /executions endpoint ""top_level=False|True""."
1702421,2017-08-02 18:46:00 UTC,This problem may be partially solved by new changes that Dougal M. will introduce.
1702421,2018-01-31 14:32:23 UTC,It's conceptually not an easy one. I think we need to recall it when we get to designing a new API.
1702421,2018-01-31 14:37:00 UTC,Waiting for new API version design is discussed at PTG.
1702421,2018-04-10 09:33:06 UTC,Removed assignee - please re-add yourself if you are actively working on this.
1702421,2019-11-19 09:12:54 UTC,"Reviewed:  https://review.opendev.org/684718
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=c49212e17168f5ebb0833d220bea1dddc5bc88a5
Submitter: Zuul
Branch:    master"
1702421,2019-12-13 17:31:13 UTC,This issue was fixed in the openstack/mistral 10.0.0.0b1 development milestone.
1702433,2018-05-10 12:34:08 UTC,"Change abandoned by Rico Lin (<email address hidden>) on branch: master
Review: https://review.openstack.org/490810
Reason: After discussion in previous PTG, we already provide other way to do this"
1702433,2018-02-09 02:44:25 UTC,"Agree, will target this in Rocky"
1702433,2018-02-08 16:18:31 UTC,"A partial fix was merged. I'm bumping this to Rocky, because it doesn't look like a total fix is feasible in the Queens timeframe."
1702433,2018-02-08 04:53:37 UTC,"@Rico, What's in-progress for this bug?"
1702433,2017-08-01 04:05:43 UTC,"Reviewed:  https://review.openstack.org/480450
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=601c5ba1e07c920bf382c1e0c10e9169b35c95b1
Submitter: Jenkins
Branch:    master"
1702433,2017-08-01 01:01:29 UTC,It can also exit early if it sees UPDATE_COMPLETE from a previous update. We need to check the timestamps as we do for nested stacks: http://git.openstack.org/cgit/openstack/heat/tree/heat/engine/resources/stack_resource.py?h=stable%2Focata#n384
1702433,2017-07-05 08:56:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480450"
1702436,2017-07-05 11:19:21 UTC,Thanks for reporting.
1702437,2019-02-06 18:44:19 UTC,Could not reproduce in python-ethtool_0.14-1 on debian/testing.  I suspect that this is fixed on Ubuntu Disco.
1702437,2020-02-15 04:17:26 UTC,[Expired for python-ethtool (Ubuntu) because there has been no activity for 60 days.]
1702445,2017-07-11 07:33:48 UTC,"Hi all,"
1702452,2017-07-07 09:21:58 UTC,"it's work after install package:
sudo pacman -Sy gstreamer
sudo pacman -Sy gst-plugins-ugly gst-plugins-base gst-plugins-good gst-plugins-bad
But I still have a bug:
(audio-recorder:10503): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
This happens when I turn on the tray icon via the slider in the settings. And I still do not know what package is needed to fix this."
1702452,2017-07-25 08:09:11 UTC,https://aur.archlinux.org/packages/audio-recorder/
1702452,2017-07-25 08:15:20 UTC,"it's work after install package:
sudo pacman -Sy gstreamer
sudo pacman -Sy gst-plugins-ugly gst-plugins-base gst-plugins-good gst-plugins-bad
But I still have a bug:
(audio-recorder:10503): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
This happens when I turn on the tray icon via the slider in the settings. And I still do not know what package is needed to fix this."
1702454,2017-10-29 17:41:56 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/516119"
1702454,2017-10-29 17:41:39 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/516118"
1702454,2017-10-29 16:26:32 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/516112"
1702454,2017-08-04 17:49:22 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/491001"
1702454,2017-10-29 16:26:15 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/516111"
1702454,2017-08-04 17:43:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/490997"
1702454,2017-08-01 13:55:22 UTC,"Why is this tagged as pike-rc-potential, it's a latent issue in stable branches, correct?"
1702454,2017-07-06 15:25:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/481116"
1702454,2017-11-01 18:39:41 UTC,"Reviewed:  https://review.openstack.org/490997
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6e332cb7f1f1b18d117685a0a0f5bb6a8e0c8e93
Submitter: Zuul
Branch:    master"
1702454,2017-08-04 17:49:09 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/491000"
1702454,2017-11-01 18:51:20 UTC,"Reviewed:  https://review.openstack.org/481116
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7317afd3201c4f9f21d3f37dab08423dae236b17
Submitter: Zuul
Branch:    master"
1702454,2017-11-07 00:14:53 UTC,"Reviewed:  https://review.openstack.org/491001
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fe8acf003e8e4d26f02ec38034c4715dfb9888ba
Submitter: Zuul
Branch:    stable/ocata"
1702454,2017-11-07 00:06:22 UTC,"Reviewed:  https://review.openstack.org/516111
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=de27ede60dd66f7c4b76fe39c63c0305424a7903
Submitter: Zuul
Branch:    stable/pike"
1702454,2017-11-07 00:06:11 UTC,"Reviewed:  https://review.openstack.org/491000
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b672420bceaf5a6e264a9362eeb6e29badd09d8
Submitter: Zuul
Branch:    stable/ocata"
1702454,2017-11-16 19:59:21 UTC,This issue was fixed in the openstack/nova 14.0.10 release.
1702454,2017-11-16 06:42:23 UTC,"Reviewed:  https://review.openstack.org/516119
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ce8bcab7cd73e27adfd26fceee7ec7c397bfa9b
Submitter: Zuul
Branch:    stable/newton"
1702454,2017-11-15 01:10:33 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1702454,2017-12-07 23:56:37 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1702454,2017-11-14 18:43:28 UTC,"Reviewed:  https://review.openstack.org/516118
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=32094105285daa7c420189f73025dd24437843bb
Submitter: Zuul
Branch:    stable/newton"
1702454,2017-11-07 00:14:40 UTC,"Reviewed:  https://review.openstack.org/516112
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0c0023d0759f54f5bd99d9ed29c2a2ccb3965cba
Submitter: Zuul
Branch:    stable/pike"
1702454,2017-11-15 01:06:47 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1702475,2017-07-05 12:22:40 UTC,Somewhat related to https://bugs.launchpad.net/nova/+bug/1679641 ( same theme )
1702475,2017-07-24 15:18:11 UTC,@jeroen - can you convert this into a Gerrit Review as you seem to have the code all here.
1702475,2017-07-24 21:04:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/486753"
1702475,2017-07-24 21:07:59 UTC,See https://review.openstack.org/486753
1702475,2019-03-09 20:42:40 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/486753"
1702482,2017-07-05 22:54:37 UTC,Fixed by https://github.com/linuxmint/Cinnamon/commit/9f3ee9b8856eba8accd76da98b65d8a139965563
1702483,2017-11-12 07:51:34 UTC,setuptools now has a release with this improvement
1702483,2017-11-15 08:30:34 UTC,"I have tried to estimate the improvement on CI devstack times with logstash, and came up with this nice graph, that show an approximate improvement of 3 minutes over 20~ for the legacy-tempest-dsvm-neutron-full job."
1702483,2017-10-16 19:33:51 UTC,"Sorry, this *will* *be* released in 36.6.1 ..."
1702483,2017-10-16 19:32:26 UTC,"Setuptools has merged a fix for this issue [1].
This is released as part of setuptools 36.6.1 [2]"
1702483,2017-10-16 20:20:44 UTC,"that's awesome to hear, thanks for sticking with this one thomas!"
1702483,2017-08-16 15:18:43 UTC,Thanks Dean.
1702483,2017-08-11 17:53:31 UTC,"Thanks for digging in to this, we know setuptools is a significant problem in startup times.  One thing that may be helpful (in case you are not aware of it) is the --timing option that reports the round trip times for API calls.  This would let you remove the servers from the total OSC run times and get rid of one variable."
1702483,2017-08-11 13:44:59 UTC,I've investigated deeper and perhaps found a place in setuptools that could lead to a significant improvement to iter_entry_point performance (the hotpoint to which the flamegraph above is pointing at).
1702483,2017-09-13 20:28:35 UTC,"Would there be some old time OpenStack guru having already had some interactions with setuptools folks and would may have a look, and possibly help push a pull request there ? [1]"
1702488,2017-07-05 14:17:07 UTC,"By the way, I mentioned that the File... menu isn't displayed.  That's true, but when I click where it should be, a pull-down menu does open.  But it opens on my second monitor, and is sized so that it runs down the entire height of the monitor - even though it only has 2 item.  I guess this could be a WINE bug - but again, it all worked fin on Mint 18.1."
1702488,2017-07-20 21:29:39 UTC,"Thinking that this might have had something to do with updating my 18.1 system to 18.2, I decided to try it on a fresh 18.2 system.  Booted from USB stick and tried to install wine.  Got the errors below.  Is it possible that 18.2 has an incompatible wine1.6 package - or is it just outlandish to try to install wine while running from the USB stick?"
1702488,2017-07-25 13:14:20 UTC,Turns out this can be fixed by deleting the .wine configuration directory and letting wine rebuild it.
1702489,2017-07-05 14:37:12 UTC,Branch here:
1702489,2017-09-22 15:34:43 UTC,"After deploying the change in the above branch in PINES production, I can confirm that it causes an error when activating purchase orders.  The problem reported here remains unsolved."
1702491,2017-07-05 14:47:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480630"
1702491,2017-08-07 12:14:58 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.openstack.org/480630
Reason: Per comments below, it would appear this is no longer necessary"
1702492,2017-11-15 14:28:05 UTC,"Additional notes:
I do NOT have an nvidia graphics card, just built-in graphics on haswell."
1702492,2017-11-15 13:58:50 UTC,Also affects me.
1702492,2018-02-08 13:07:30 UTC,think this is probably related or at least in the same area https://bugs.launchpad.net/ubuntubudgie/+bug/1696625
1702492,2018-03-10 09:42:16 UTC,Bug #1754827 raised for the issue I mentioned above.
1702492,2018-03-10 09:23:36 UTC,"How odd - when I go into Gnome settings > Color, there seems to be no way to simply add a profile from within the GUI, or to use anything other than the default profile. This seems inconsistent with the help page called ""How do I test if color management is working correctly?"", which I found via the ""Learn More"" hyperlink within Gnome Settings > Color. I'll raise a separate bug report for this."
1702492,2018-02-08 13:59:53 UTC,"yes, this sounds exactly like the process that resets the color management
as well."
1702493,2020-03-20 10:11:33 UTC,"in ubuntu19.10 I install wine5.0 the same error appear.
widon@widon-ubuntu:~$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  linux-headers-5.3.0-18 linux-headers-5.3.0-18-generic linux-image-5.3.0-18-generic linux-modules-5.3.0-18-generic linux-modules-extra-5.3.0-18-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libvdpau1
The following NEW packages will be installed:
  libvdpau1
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
84 not fully installed or removed.
Need to get 0 B/25.5 kB of archives.
After this operation, 109 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
 LANGUAGE = ""zh_CN:zh"",
 LC_ALL = (unset),
 LANG = ""en.US""
    are supported and installed on your system.
perl: warning: Falling back to the standard locale (""C"").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 222146 files and directories currently installed.)
Preparing to unpack .../libvdpau1_1.2-1ubuntu1_amd64.deb ...
Unpacking libvdpau1:amd64 (1.2-1ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/libvdpau1_1.2-1ubuntu1_amd64.deb (--unpack):
 trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64
Errors were encountered while processing:
 /var/cache/apt/archives/libvdpau1_1.2-1ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)"
1702493,2017-07-10 14:33:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702494,2017-09-04 21:59:05 UTC,v0.11 will check if there is a running instance by default
1702499,2017-07-05 14:55:29 UTC,Test file test.c added
1702499,2017-07-26 17:17:36 UTC,"Greetings,"
1702500,2017-07-05 15:14:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480640"
1702500,2019-11-20 04:17:41 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1702505,2017-07-29 04:01:32 UTC,"Reviewed:  https://review.openstack.org/480731
Committed: https://git.openstack.org/cgit/openstack/networking-vpp/commit/?id=24eeac8177a3b6eaf4d1b9f4f72c21b081f7f04a
Submitter: Jenkins
Branch:    master"
1702511,2017-07-11 23:13:06 UTC,"I checked with the original game and the Ares documentation (see the first blue box on the big diagram on the Prerequisites topic), and they both concur that this is the expected behavior. If you don't want to override the TechLevel but still make the TechnoType buildable when the player owns a certain building, wouldn't an alternative Prerequisite.List work there?"
1702539,2017-09-14 04:56:54 UTC,The reason for this what not what I expected...
1702539,2017-09-14 09:06:50 UTC,"Forum post asking to clarify what the newline characters are supposed to be:
https://forum.snapcraft.io/t/snap-metadata-newline-characters/"
1702539,2017-09-18 01:44:10 UTC,Bug 1717830 opened against the store.
1702539,2017-07-05 19:29:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702545,2017-07-08 05:26:29 UTC,https://github.com/linuxmint/nemo/commit/0eb939f29adbf6940b0f4402fa986c56253cbfef
1702553,2017-07-11 16:10:40 UTC,"An updated version of the role should have fixed this issue, could you confirm?"
1702553,2020-09-18 13:42:09 UTC,"V-38660 is not present in hardening anymore, marking as closed"
1702555,2017-07-05 21:55:23 UTC,"Hi this is the policy.json for heat.
Also after changing it I restarted the services with `systemctl restart devstack@*.service`"
1702555,2017-07-05 21:37:10 UTC,what does your heat policy file look like after changing?
1702555,2017-07-14 11:43:36 UTC,Is the tenant/project from which you are deploying VNFs have admin access ?
1702555,2017-07-14 20:15:41 UTC,"yes it does, I think the problems comes with the user ""tacker"" not having privileges."
1702555,2017-11-09 08:23:08 UTC,Is the issue is solved ?
1702574,2017-07-06 15:04:55 UTC,Try this https://github.com/zant95/elementary-dropbox
1702589,2017-07-11 06:22:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/482416"
1702589,2019-05-10 20:59:35 UTC,"Change abandoned by Adam Harwell (<email address hidden>) on branch: master
Review: https://review.opendev.org/482416
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1702589,2017-07-08 06:58:26 UTC,Forward the bug to octavia project (as neutron-lbaas is maintained by the octavia team).
1702589,2017-07-10 10:22:48 UTC,"The neutronclient are using a public library for LBaaS v2.
I suggest that the problem in neutron-lbaas modify more appropriate"
1702591,2020-04-26 03:08:56 UTC,This bug report can be closed.
1702591,2020-04-26 03:06:26 UTC,I believe this functionality is already implemented in the elementary language settings. It prompts the user to install missing language packages.
1702592,2017-07-06 02:29:19 UTC,I am really confused that why we need rebuild log_component line by line rather than directly publish original chunk as follows:
1702592,2017-07-06 02:31:02 UTC,"In addition, processing chunk data line by line, it doesn't work if the log is not text format like binlog."
1702592,2017-07-06 02:58:36 UTC,"some database has a binary log file? that's a new one ... it would be very hard to read, that's for sure."
1702592,2017-07-06 02:59:59 UTC,Was this 'bug' found in actual operation or is it a conjecture that this is a problem?
1702592,2017-07-06 04:48:56 UTC,This bug seems produce nearly 100% in our environment if the log is larger than chunk size.
1702595,2017-07-06 02:50:47 UTC,"apologies for the vile wrapping.  For those with access, https://pastebin.canonical.com/192695/ might be easier to read."
1702595,2017-09-02 14:10:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702595,2018-02-22 10:54:57 UTC,Hi @xavpaice are you to specify the package version you upgraded from/to?
1702601,2017-07-12 16:48:45 UTC,"Remember that if you update or reinstall this printer driver again in the future, it will undo this fix and you will have to apply it again."
1702601,2017-07-12 14:13:39 UTC,"Yes, it worked! Very much I thank you! The problem is removed."
1702601,2017-07-12 13:03:15 UTC,"Dear Andreas, I compared my file and the enclosed code. Difference only
in commented-out lines which I quote below. Or I was mistaken? These are
commented-out lines ""# comment"" or not? Unless they influence operation?"
1702601,2017-07-12 12:39:25 UTC,Try this one. Don't forget to chmod it to 0755 after it's in place.
1702601,2017-07-12 02:13:35 UTC,"Dear Andreas, I will be very grateful to you for the help! Help to
finish, please, correctly this problem. I worry to make something not so.
I attach these two problem files. Define that not so in them, correct.
The main thing that after adjustment the printer and the scanner as
worked for me earlier. Now they work perfectly. But because of them a
problem as you clarified. Correct, please."
1702601,2017-07-11 20:34:46 UTC,Can you edit that file like how it is suggested in the first answer here:
1702601,2017-07-12 13:23:55 UTC,"Correct, these lines do influence operation. These are the so called LSB headers and they influence service startup and shutdown ordering."
1702601,2017-07-11 14:57:06 UTC,"Drivers for the Panasonic MFP I set the latest from the website. And on
all signs updates won't be on this device any more. For this reason I
also ask how me to leave to workers the Panasonic MFP device and packets
of ""panasoniclpd"" and ""plymouth"" in Ubuntu? At the same time, how to
clean check APT, APT-GET, DKPG, etc.?
I don't need to update packets of ""panasoniclpd"" and ""plymouth"" more.
Where to disconnect it?"
1702601,2017-07-11 13:24:20 UTC,"Where did you get the panasoniclpd package from? A CD that came with the printer? Maybe there is an updated driver available in the panasonic website, have you tried that?"
1702601,2017-07-11 13:06:02 UTC,"Dear Andreas,
I know about a problem with ""panasoniclpd"" Actually there problem with
""plymouth"".
My Panasonic KX-MB2110 MFP. I can't and I don't want to delete it. How I
will print and scan?
It is possible to solve it on another. Perhaps, I suppose. It is correct
to clean from settings of repositories setup of updating/upgrading of
packets ""plymouth"" and ""panasoniclpd"" At the same time to leave them
operating, but without updating/upgrading in the future. It is possible?"
1702601,2017-07-11 12:24:29 UTC,"This is the error:
Setting up samba (2:4.3.11+dfsg-0ubuntu0.16.04.8) ...
insserv: warning: script 'S99panasoniclpd-init' missing LSB tags and overrides
insserv: warning: script 'panasoniclpd-init' missing LSB tags and overrides
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service panasoniclpd-init and plymouth if started
insserv:  loop involving service plymouth at depth 8
insserv:  loop involving service panasoniclpd-init at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package samba (--configure):
 subprocess installed post-installation script returned error exit status 1"
1702601,2017-07-11 20:29:02 UTC,Can you attach /etc/init.d/panasoniclpd-init please?
1702601,2017-07-11 02:45:52 UTC,I also subscribed apport because there are python2 -> python3 transition bugs in the HookError_ubuntu.txt file. Thanks.
1702601,2017-07-11 02:45:06 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1702621,2020-11-09 18:07:02 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1702621,2017-07-07 08:48:55 UTC,"I agree with David, you can try the RTL8139."
1702621,2021-01-09 04:17:48 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1702621,2017-07-06 07:50:02 UTC,"The qemu version is 2.9.0 release.
The 'irq_count' and 'irq_state' are sent by private vm, and loaded by secondary vm.  When they sent by private vm, they maybe not in a consistent state. So sometimes 'bus->irq_count[i]' becomes '-1' on secondary vm.
I deleted the assertions and then tested it several times, it worked well"
1702621,2017-07-06 11:07:11 UTC,"I haven't tried COLO for a while; I've got a note I hit a similar error in  the past -
I think I came to the conclusion it was the e1000 that was unhappy - probably sending an interrupt after it had stopped.
Try a different NIC.  I flipped to using a virtio-net at one point (but I think I had to disable vhost, there are some patches for this recently)."
1702634,2017-07-27 08:59:17 UTC,"Set to medium, since this is important, but not enough to do be rushed for Pike."
1702637,2017-07-10 01:04:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/481971"
1702637,2017-10-04 19:29:51 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.openstack.org/481971
Reason: This patch has been idle for some time and therefore I'm removing it from the queue for housecleaning purposes. If this is still a valid patch, please re-push an updated patch. Thanks."
1702645,2017-07-06 09:09:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480923"
1702645,2017-07-06 09:27:34 UTC,"So your keystone does not use ssl, but remote heat does or the certificates are different??"
1702645,2017-07-07 02:28:44 UTC,"Yes, I use internalURL in [clients_keystone] and set publicURL in [clients_heat], our internalURL is http, publicURL is https. This will cause error when I create a OS::Heat::Stack resource."
1702656,2017-07-26 16:56:25 UTC,"Yes, I certainly don't object to snapcraft's interface being improved (especially for the sake of cleanbuild et al), but we'll need to deal with it in launchpad-buildd as well at least for a while."
1702656,2017-07-25 13:07:09 UTC,"I had to revert this because it broke ""type: os"" and ""type: kernel"" builds.  Even with some Makefile changes from Oliver to run lb under sudo, the core snap build still failed because snapcraft was unable to stage the result:"
1702656,2017-07-25 22:56:52 UTC,We might be able to do 1 in snapcraft by re-exec-ing ourselves with sudo if we detect `os` or `kernel` as we will most likely follow the lead and move snapcraft to build as a regular user as well so it might be better to do the `root` required detection ourselves.
1702656,2017-07-26 09:29:34 UTC,"As I understand it, Launchpad won't be able to rely on a fix in snapcraft because snaps can be built with different suites so Xenial without -updates wouldn't have a new version. So I opened a forum topic to discuss improvements in snapcraft and not deter from the fix here:
https://forum.snapcraft.io/t/run-snapcraft-in-container-as-a-user/1438"
1702659,2017-07-06 10:13:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/480953"
1702660,2018-08-28 19:38:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702662,2017-08-05 21:18:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702664,2017-07-07 11:41:53 UTC,I don't understand your question 1)
1702664,2017-07-06 14:50:01 UTC,"My initial reaction is twofold:
1) Why not all *_these_nonmembers?
2) I don't think this will be of sufficient general interest to justify adding yet more configuration settings."
1702664,2017-07-07 11:44:13 UTC,"a now I see what you mean by 1).
Well the others would not hurt either. It's just that we only need discard_these_nonmembers"
1702664,2017-07-07 11:47:35 UTC,The problem with the report to be sent to the mailing list is that there is an admin link for this quarantine mailbox (and if the list is public) everyone would see this and might modify white/blacklist etc.
1702665,2017-07-11 14:44:44 UTC,"Can you also give the latest upstream 4.4 kernel a test?  It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.76/"
1702665,2017-07-11 16:48:17 UTC,"Sure. Upgraded one of an instance running 4.4.76-040476-generic, aside of existing 4.12 instance."
1702665,2017-07-11 16:48:51 UTC,"Clarify: Upgraded one of an instance running 4.4.0-83 to 4.4.76-040476-generic, *"
1702665,2017-07-11 21:17:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702665,2017-07-13 11:23:46 UTC,Not seeing crashes at 4.4.76-040476-generic for these few days.
1702665,2017-07-09 22:15:38 UTC,Additional logs from 4.4.0 machine by running `dmesg -w` until crash.
1702665,2017-07-10 01:46:29 UTC,"4.12 instance is still running without crash, survived this weekend."
1702665,2017-07-06 11:00:06 UTC,This change was made by a bot.
1702665,2017-07-06 15:22:51 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1702665,2017-07-06 16:05:06 UTC,Created new instance and bumped to the 4.12 latest.
1702665,2017-07-07 08:27:32 UTC,"We've switched most of instances in the cluster to c4.large instance type, but another panic occur. Panic happened at different trace, so this may not relate to the first GPF, but pasting log below for information."
1702665,2017-07-07 08:30:49 UTC,"Noticed that these log appears before panic occurs for both kind of panics (GPF and ""unable to handle kernel paging request"")."
1702671,2019-02-06 02:44:42 UTC,"MAAS version:
aloksingh@infr001:/var/log/maas$ dpkg -l | grep '^ii' | grep maas
ii  maas-cli                              2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          MAAS client and command-line interface
ii  maas-common                           2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          MAAS server common files
ii  maas-dhcp                             2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          MAAS DHCP server
ii  maas-dns                              2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          MAAS DNS server
ii  maas-proxy                            2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          MAAS Caching Proxy
ii  maas-rack-controller                  2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          Rack Controller for MAAS
ii  maas-region-api                       2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          Region controller API service for MAAS
ii  maas-region-controller                2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          Region Controller for MAAS
ii  python3-django-maas                   2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          MAAS server Django web framework (Python 3)
ii  python3-maas-client                   2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          MAAS python API client (Python 3)
ii  python3-maas-provisioningserver       2.3.5-6511-gf466fdb-0ubuntu1~16.04.1        all          MAAS server provisioning libraries (Python 3)"
1702671,2019-02-01 11:04:59 UTC,"The timestamp updates causes considerable CPU load. By watching top and pg_stat_activity, I was able to catch PID 51544 in the act. The actions of the PID are:"
1702671,2019-02-02 04:18:09 UTC,"Devs this was targeted to 2.3, please address it."
1702671,2019-02-05 03:42:21 UTC,"Subscribing field-medium as when this situation arises, it affects operations. For instance juju ssh will fail with errors of the form:"
1702671,2019-02-05 03:56:06 UTC,I’m setting this incomplete as there is not enough information to determine what the issue may be.
1702671,2019-02-05 04:01:30 UTC,"Also, logs provided in #1 seem to be updates from Maas due to being unable to make full connectivity between controllers. There is one log that stands out specifically and that is this:"
1702671,2019-02-06 02:50:18 UTC,"@Anders, the missing WAL segment error has been in the logs for some months before the problem manifested itself. The problem has also been seen in clouds where there are no missing WAL segments."
1702671,2019-09-20 10:16:32 UTC,We believe this bug is fixed in the up coming 2.6.1 release. We did a lot of performance analysis on database transactions to help reduce serialization issues and the number of retries.
1702677,2018-10-31 20:11:06 UTC,"We need that too ;)
That's really a valuable addition."
1702682,2020-02-26 11:57:26 UTC,"HI Liviu,"
1702682,2017-07-07 13:23:36 UTC,"> We shall leave 6_1-2017q1 as it is for now lest we break your scripts again and others' scripts elsewhere.
"
1702682,2017-07-07 13:00:30 UTC,"Hi Liviu,"
1702682,2017-07-07 08:02:39 UTC,"Hi Liviu,"
1702685,2017-07-07 06:33:31 UTC,"Pre-installed Dell Vostro 15-3568 with wifi component Atheros Communications - 168c:0036 could not reproduce this issue with kernel 4.4.0-85-generic, 4.4.0-84-generic and 4.4.0-82-generic"
1702685,2017-07-12 03:17:42 UTC,"[168c:0042] DW1810
[168c:0036] DW1707"
1702685,2017-07-07 06:56:42 UTC,The case of the comment 8[1] does not has ath9k-msi dkms installed.
1702685,2017-07-07 06:48:20 UTC,"checking the database, the platform was with pci id 168c:0042. but the one that the bug report and #8 use 168c:0036."
1702685,2017-07-12 06:42:52 UTC,Need to confirm the issue on correct platform before online update verify.
1702685,2017-07-07 04:32:43 UTC,"Based on advice by jeremy31 at Ubuntu Forums in https://ubuntuforums.org/showthread.php?t=2364875, I ran ""dkms status"" and got
09:38 AM ~ $ dkms status
ath9k-msi, 1.0, 4.4.0-81-generic, x86_64: installed
ath9k-msi, 1.0, 4.4.0-83-generic, x86_64: installed
intel-hid, 3.1, 4.4.0-81-generic, x86_64: installed
intel-hid, 3.1, 4.4.0-83-generic, x86_64: installed
oem-audio-hda-daily, 0.201612080732~ubuntu16.04.1, 4.4.0-81-generic, x86_64: installed
radeon-si, 1a, 4.4.0-38-generic, x86_64: built
radeon-si, 1a, 4.4.0-81-generic, x86_64: installed
radeon-si, 1a, 4.4.0-83-generic, x86_64: installed
09:41 AM ~ $"
1702685,2017-07-06 13:30:05 UTC,This change was made by a bot.
1702685,2017-07-06 16:03:11 UTC,Never mind. I read the wiki and understood it. I'll post back once I've done the test.
1702685,2017-07-06 15:48:37 UTC,I don't know if this helps but I also have Kubuntu 16.04.2 installed on the same machine with:
1702685,2017-07-06 15:21:10 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1702685,2017-07-06 17:23:49 UTC,I tried but failed to get the kernel going.
1702691,2017-08-23 18:39:14 UTC,"Oslo log makes it possible to control all oslo logging with one logger node. Therefore, we can create multiple logger nodes, they're all currently controlled by one configuration."
1702694,2018-01-20 07:38:40 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1451
1702694,2017-07-06 14:10:45 UTC,Introduced with bug#1135431 (commit 997554b300adaf87ac979ada30525cc516b1f750)
1702694,2017-07-08 06:40:42 UTC,PR: https://github.com/percona/percona-xtrabackup/pull/384
1702706,2017-07-10 16:44:49 UTC,"Thank you.
Yes, I think it is problem in Ubuntu Guide: https://docs.openstack.org/ocata/install-guide-ubuntu/keystone-openrc.html"
1702706,2017-07-10 09:17:39 UTC,As per documentation you need to register the endpoint using the CONTROLLER_IP or a dns name that the vms can find route to.
1702711,2017-07-07 04:38:08 UTC,"hmm, well I put this back in, but it seems like the bootloader is broken for wheezy"
1702721,2017-07-06 16:58:17 UTC,This issue can be observed when running under Ubuntu-Core (which has no dmidecode tool)
1702722,2017-07-23 14:11:39 UTC,This bug was fixed in the package gnome-settings-daemon - 3.24.3-0ubuntu2
1702723,2017-07-06 17:04:31 UTC,"Yep, running with LANG set to uk_UA.UTF-8 works fine -- only one warning still appears on stderr:"
1702726,2017-07-07 21:51:46 UTC,"Testing this, the results are not quite as clear-cut as the example. I
don't always see the same errors."
1702726,2017-07-07 06:51:26 UTC,"Hi Christopher,
thanks for the report and the nice steps to reproduce.
I can absolutely confirm your finding."
1702734,2017-07-06 18:23:43 UTC,"Any help appreciated. How do I upgrade from 16.04 to a 17.x, from a xterm command line. gnome-terminal and terminator will not start up on my box.  THANKS!"
1702750,2017-07-06 21:28:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/481288"
1702750,2018-07-13 00:09:51 UTC,"Change abandoned by James Slagle (<email address hidden>) on branch: master
Review: https://review.openstack.org/481288"
1702751,2020-04-26 04:17:18 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1702751,2020-02-25 08:23:33 UTC,"This bug was originally for MAAS 2.2 and a lot has changed since then. Have you seen this bug with 2.7 (or maybe 2.6)? If so, please attach the logs, so that we can take a closer look at what's going on."
1702751,2017-12-01 08:59:07 UTC,"Newell, I'm not sure.  I didn't get to look into the logs, I was watching
someone else type and couldn't access the system.  Once we found the
problem we just continued with other work."
1702751,2017-11-29 21:51:03 UTC,"I'm not quite sure we should fail adding a machine if we cannot power manage. That said, when this was first reported, Newell was unable to reproduce, so I wonder if this has anything to do with the rack not being fully connected or a similar case ?"
1702751,2017-11-29 22:56:29 UTC,"Jason,"
1702751,2017-07-06 20:38:18 UTC,"I am not able to reproduce this.  I was able to see the same error when trying to execute the same command as that supplied in the pastebin.  After that though, I don't see the error and things seems to be working correctly (when creating machines etc.)."
1702751,2017-07-06 20:16:32 UTC,"This is like bug 1600328, except I get a Nonce error."
1702751,2017-11-29 11:31:55 UTC,"We hit this onsite today.  It's fine that machine creation fails but the error message ""nonce already used"" is unacceptable.  It took us a while to figure out what was really happening.  We need an error like ""BMC can't be reached""."
1702752,2017-07-06 20:07:15 UTC,"BTW the bug happens only IF the eth0 is unplugged. When eth0 cable is plugged in, wlan0 stays connected."
1702754,2019-09-19 12:04:06 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1702754,2019-09-20 12:21:50 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1702755,2017-07-10 18:14:39 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1702767,2017-07-07 00:24:06 UTC,"The attachment ""Possible fix for pname completion (doesn't handle spaces in process name but I haven't seen spaces in yet in exes)"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1702773,2017-07-06 22:53:32 UTC,Can you reproduce with 0.92.1 ?
1702773,2017-07-07 02:51:21 UTC,"After installing 0.92.1 through snapd I can confirm this is not an issue in the latest version. In other words, everything works as expected in 0.92.1"
1702773,2020-08-19 12:04:27 UTC,"Confirmed still fixed in 1.0, but closing as fixed in 0.92.1. This is part of the bug migration effort to go through bugs in launchpad and manually migrate them over to GitLab (https://alpha.inkscape.org/bug-migration/)."
1702777,2017-07-07 08:05:14 UTC,"Marking this as a feature for now; we've used tcmalloc for a long time, and I'm not sure whether we can build the packages to support both versions."
1702777,2020-02-13 19:14:05 UTC,"The use of jemalloc is not possible with rocksdb [0], and has the option has been removed in luminous+, which use bluestore by default [1]."
1702785,2017-08-26 13:24:39 UTC,"I ran into this as well, with the same host's cron daemon reaching ~8GB RSS memory after a month."
1702785,2018-07-01 22:14:10 UTC,"Actually, an immediate fix for you guys may be to make sure that there is some *input_data. I have no clue what that means in terms of administrative setup, though. But maybe someone else can help in that area. The really bad statement looks like this:"
1702785,2017-07-06 23:26:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702785,2018-07-01 22:08:27 UTC,I found a bug in the code as described in this issue: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583
1702788,2017-07-07 16:40:46 UTC,"Cannot reproduce on win 8.1-64, Inkscape 0.92.1 r15371. Export is as expected, with pattern fill reproduced."
1702792,2017-07-07 00:24:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1702792,2017-07-28 13:28:16 UTC,"Hello Guilherme, could you please attach the installation logs? You can do it by exiting to shell, at d-i, and grabbing the logs at /var/log."
1702792,2017-07-28 21:42:08 UTC,"This is certainly a bug, but it is user error to configure an LVM volume as the prep partition; the prep partition must be a disk partition visible from firmware."
1702792,2017-07-29 01:12:07 UTC,"Yes, you're right. It works fine when using guided partitioning."
1702792,2017-08-19 19:50:37 UTC,"Steve Langasek said ""This is certainly a bug"". Why was the status changed to invalid?"
1702798,2020-11-09 18:07:32 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1702798,2021-01-09 04:17:49 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1702798,2017-07-07 02:00:34 UTC,"The qemu version is 2.9.0 release.
The secondary vm state make me confused. I tried to add vm_stop and vm_start in colo_process_incoming_thread function, but it crashed."
1702798,2017-07-10 07:29:44 UTC,"In qemu upstream COLO project can not fully running, you can test my internal branch.
https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10"
1702801,2019-04-30 02:46:04 UTC,This still occurs with with ubuntu 19.04.
1702807,2017-09-21 15:48:52 UTC,Marking hacluster task as Invalid as this is a landscape feature request.
1702807,2017-10-13 08:56:02 UTC,"Added Landscape server to this, as the current situation needs to be either resolved automatically or a suitable implementation method documented so we can prevent customers hitting this same problem again. I wonder if we had created different update schedules for different cluster nodes, if we'd have avoided the outage caused by updates in this case."
1702807,2018-10-12 04:44:49 UTC,"We are running upgrades manually from the NOC on specified nights but having to drag out and baby sit upgrades so we can avoid this issue. As we use Landscape to manage our cloud machines, it would be VERY helpful if it was cloud aware so we could leave it to do it's thing without handling the ""automatic"" upgrades manually."
1702811,2018-06-20 09:10:21 UTC,Any news? Already fixed?
1702811,2018-06-23 19:19:56 UTC,The dialog is now fixed in Caja 1.20 which is in Ubuntu 18.04 repos.
1702811,2017-07-19 11:19:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702811,2017-07-19 11:18:48 UTC,Known issue with the dialog: https://github.com/mate-desktop/caja/issues/506
1702811,2017-07-19 13:47:41 UTC,"Workaround by resizing the window works, thanks for that hint!
Hopefully it will be fixed soon anyway."
1702833,2017-07-07 09:17:37 UTC,Patch here: https://review.openstack.org/#/c/480886/
1702833,2018-09-06 08:10:46 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/480886
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1702836,2017-07-07 20:01:38 UTC,This may be a duplicate of bug 1692981.
1702842,2018-04-11 06:16:04 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: stable/ocata
Review: https://review.openstack.org/485003"
1702842,2017-12-15 09:04:59 UTC,This issue was fixed in the openstack/kolla 4.0.3 release.
1702842,2017-07-27 20:49:27 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.
1702842,2017-07-27 20:51:40 UTC,This issue was fixed in the openstack/kolla 5.0.0.0b3 development milestone.
1702842,2017-07-18 15:41:30 UTC,"Reviewed:  https://review.openstack.org/481517
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=a6831e945f8fe6bee2281ab18c1af3d57dff3167
Submitter: Jenkins
Branch:    master"
1702842,2017-07-16 17:14:21 UTC,"Reviewed:  https://review.openstack.org/482749
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=6ddb60e3e066b2a1a3f62071f6aa20b7989bdcc7
Submitter: Jenkins
Branch:    stable/ocata"
1702842,2017-07-12 00:22:09 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/482749"
1702842,2017-07-11 09:30:18 UTC,"Reviewed:  https://review.openstack.org/481493
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=d6b28258cca1b949ceba9224e85f17279ed21093
Submitter: Jenkins
Branch:    master"
1702842,2017-07-07 08:56:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/481517"
1702842,2017-07-19 01:32:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/485003"
1702844,2017-07-07 07:51:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/481483"
1702844,2017-10-23 15:34:04 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.openstack.org/481483
Reason: This hasn't been touched in a number of months. I'm abandoning to clean up my review queue"
1702848,2017-09-15 15:16:24 UTC,"the requested address: http://jenkins/me/api/json
triggers the following error when running Jenkins with anonymous user only:
rg.acegisecurity.AccessDeniedException: /me is not available when not logged in"
1702848,2017-10-24 17:42:19 UTC,"Jörn, as a user, how would you expect this to work when calling get_whoami() with an unauthenticated connection?"
1702860,2018-09-12 14:54:07 UTC,"Yes, I can reproduce it now. Wasn't able to do so, because I had some newer libraries installed via pip."
1702860,2017-07-26 07:35:56 UTC,"Hi Kanshi,"
1702860,2017-07-20 12:24:03 UTC,"I believe you should check the documentation for the openstack client first.
https://docs.openstack.org/python-openstackclient/latest/cli/man/openstack.html#manpage"
1702860,2017-07-19 11:05:51 UTC,"I forgot to notice, I downloaded it from official Debian repo:
https://packages.debian.org/stretch/python-openstackclient"
1702860,2017-07-27 08:50:55 UTC,"Hi all,"
1702863,2017-07-07 10:06:46 UTC,"The following patch was skipped because it was already applied for bug #1683976 ""Please backport fix to reference leak in cgroup blkio throttle"":
* block: fix module reference leak on put_disk() call for cgroups throttle"
1702863,2017-08-03 16:32:17 UTC,This bug was fixed in the package linux - 4.4.0-89.112
1702888,2021-01-28 12:59:39 UTC,I've just tried this and it seems to work fine. Can you confirm if this is still a problem?
1702888,2021-01-29 02:21:55 UTC,"Still fails here, I'm afraid:"
1702888,2021-02-02 09:15:39 UTC,This has landed in revno 577. Waiting for the snap to build and will confirm before closing out this bug.
1702888,2021-02-02 09:57:39 UTC,"Ok, this has now been released to the snap:"
1702893,2017-07-20 23:22:12 UTC,"I want to say we have fixed this in the past for some of the API references, by adding logic that put in a soft return at symbols such as underbar or period. Might work for this particular problem."
1702894,2017-07-07 14:30:04 UTC,"Didier uploaded a casper change to default to an xorg session which should workaround that bug for now, still ubiquity should work under wayland"
1702894,2017-10-06 13:54:04 UTC,This isn't going to happen for Ubuntu 17.10.
1702894,2017-08-25 11:32:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1702897,2017-07-26 23:42:45 UTC,"Reviewed:  https://review.openstack.org/481627
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e44ea07c4ddd4f493482fd6f4f02446a2718ed65
Submitter: Jenkins
Branch:    master"
1702897,2017-08-01 10:14:31 UTC,"There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments."
1702897,2017-07-24 14:46:15 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1702902,2017-07-07 13:53:16 UTC,"Bazaar-based MPs behave the same way.  At the moment the list of commits in question is presented as ""Unmerged revisions"" (bzr) or ""Unmerged commits"" (git).  While I can see the argument for freezing the list in the same way that we freeze the diff, we'd also have to think about how to present it post-merge to avoid confusion."
1702909,2017-07-07 20:11:00 UTC,"For a long time I would beeing able to import pdf text as curves in Inkscape, even when the fonts are not installed on my system."
1702909,2017-10-12 12:49:09 UTC,This seems to be related to (or maybe a duplicate of) bug #271614.
1702909,2019-12-17 07:34:49 UTC,Closing as part of the migration to GitLab http://alpha.inkscape.org/bug-migration/
1702910,2017-09-20 21:07:59 UTC,"Can folks affected by this bug test the kernel located at:
http://kernel.ubuntu.com/~jsalisbury/lp1702910/"
1702910,2017-09-19 15:46:31 UTC,There's a discussion here possibly about the same problem:
1702910,2017-09-15 21:05:19 UTC,I can confirm that this also happens with 4.4.0-87-generic.
1702910,2017-09-01 18:43:20 UTC,Can you also see if this bug happens with the latest upstream stable 4.4 kernel?  It is available from:
1702910,2017-08-02 09:41:09 UTC,We've successfully reproduced the error on a newly built instance.  We'll proceed to run the mainline kernel on the same instance.
1702910,2017-09-18 20:40:41 UTC,"Were you able to reproduce on a 4.12 kernel?  Maybe even a 4.14 kernel (even though it's just the first rc that's been cut, it is the next lts).  4.9 is another lts kernel series that could be tested."
1702910,2017-07-18 08:16:59 UTC,There is a similar stack trace on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702665.
1702910,2017-07-27 12:37:34 UTC,"I can confirm the bug:
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320092] ------------[ cut here ]------------
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320100] WARNING: CPU: 1 PID: 42381 at /build/linux-0uniEn/linux-4.4.0/net/ipv6/addrconf_core.c:159 in6_dev_finish_destroy+0x6b/0xc0()
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320102] Modules linked in: cmac arc4 md4 nls_utf8 cifs fscache xt_statistic sch_htb ebt_ip ebtable_filter xt_nat xt_recent ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_mark xt_comment veth ebtable_nat ebtables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc overlay i2c_piix4 8250_fintek input_leds joydev mac_hid serio_raw ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hv_netvsc hv_utils hid_hyperv hv_storvsc hid scsi_transport_fc hyperv_keyboard aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper hyperv_fb cryptd psmouse pata_acpi hv_vmbus floppy fjes
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320149] CPU: 1 PID: 42381 Comm: kworker/u128:3 Not tainted 4.4.0-83-generic #106-Ubuntu
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320151] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006  05/23/2012
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320155] Workqueue: netns cleanup_net
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320156]  0000000000000286 00000000174b4ae5 ffff880686863ba0 ffffffff813f9513
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320158]  0000000000000000 ffffffff81d75940 ffff880686863bd8 ffffffff81081322
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320160]  ffff88048ff82800 ffff88048ff80000 0000000000000006 ffff880686863ca8
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320162] Call Trace:
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320166]  [<ffffffff813f9513>] dump_stack+0x63/0x90
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320170]  [<ffffffff81081322>] warn_slowpath_common+0x82/0xc0
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320172]  [<ffffffff8108146a>] warn_slowpath_null+0x1a/0x20
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320173]  [<ffffffff8181ba0b>] in6_dev_finish_destroy+0x6b/0xc0
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320176]  [<ffffffff817f17e6>] ip6_route_dev_notify+0x116/0x130
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320178]  [<ffffffff810a1b1a>] notifier_call_chain+0x4a/0x70
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320180]  [<ffffffff810a1c96>] raw_notifier_call_chain+0x16/0x20
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320182]  [<ffffffff8172f655>] call_netdevice_notifiers_info+0x35/0x60
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320185]  [<fffff..."
1702910,2017-07-07 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1702910,2017-07-07 16:24:01 UTC,Logs are inline.  If anything else is needed I'll capture and attach.
1702910,2017-09-15 23:11:37 UTC,Here is additional debug information:
1702910,2017-07-10 17:47:38 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1702910,2017-07-12 13:22:17 UTC,"We're aiming to reproduce this issue on another instance, then will switch to the mainline kernel to gather the info you need."
1702910,2017-07-10 14:10:38 UTC,With the sysctl net.ipv6.conf.all.disable_ipv6=1 we have still seen another kernel error as follows:
1702922,2017-07-12 11:55:17 UTC,"Adding cinder, in the recent week(s) there were multiple issues with thin-lvm   reverts/new fixes , so the root cause of this issue is likely in cider."
1702922,2017-07-12 13:55:11 UTC,Appears to fail due to not being able to find the snapshot. Will have to investigate more.
1702922,2017-07-12 14:13:01 UTC,"The snapshot is bein created, because during the test, I can issue cinder list --all-tenant and I can see the snapshot there... But after a while, it disappears.."
1702922,2018-12-30 00:01:20 UTC,"This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced."
1702929,2018-05-29 16:00:23 UTC,The data storage for this bug is now covered by the code in bug #1750894.  This bug is now primarily focused on creating a grid option for storing values as org unit settings.  Something along the lines of...
1702929,2018-03-09 15:43:21 UTC,This bug may ultimately be absorbed by bug #1750894.
1702929,2017-08-03 16:28:02 UTC,Note this might be affected by the pending work to store workstation settings on the server.
1702929,2017-07-07 17:47:46 UTC,"I like it, Galen.  You had me at ""save to server"".  And +1 to org-scoped."
1702929,2017-07-07 16:24:23 UTC,"One advantage of doing it this way is that if the column configuration format were to change in an incompatible way, having them in the database would make them more accessible to an upgrade script."
1702929,2017-09-06 20:07:13 UTC,Just want to add another +1 to have these settings org-scoped.
1702929,2017-07-07 16:22:55 UTC,"While this approach would work, and I have no strong objection to it, I'd like to propose a variation that doesn't require that the EG admin mess around with files on the server: store them in the database as JSON blobs, possibly with an OU for scoping which ones to use, and either fetch the desired one when rendering a grid or fetching them en masse during app startup. To create or modify the templates, I further propose that a new column configuration action be added to specify saving the current config to the server."
1702957,2020-03-17 21:33:45 UTC,"The MP for this bug is currently blocked by bug 1822329, which has a few MPs not merged yet."
1702957,2020-03-23 20:30:15 UTC,"Asked Jeremy, the plan is to fix bugs first. The rewrite is in lower priority. So skip bug 1822329 for now.
This patch is ready for peer review."
1702965,2020-04-03 05:45:56 UTC,Closing as part of the manual migration of bugs to GitLab.
1702986,2017-07-07 19:25:58 UTC,In terms of installation - it doesn't install straight properly on any of the releases unless dpkg is also backported.
1702986,2017-07-10 08:40:53 UTC,Not sure - check with the Launchpad folks maybe?
1702986,2017-07-07 19:35:30 UTC,"@laney, not sure if you can comment more on the intention with that above^  Should that only be going on for artful?  Or will you intend to also generate dbgsym packages differently on xenial and yakkety and zesty?"
1703014,2017-07-07 20:41:59 UTC,"see here:
https://github.com/Bumblebee-Project/Bumblebee/issues/888#issuecomment-313630826"
1703051,2017-07-10 19:25:11 UTC,"Additionally, upgrading opendnssec from 1.4.9 in Xenial directly to 2.0.3 in Zesty is not supported by opendnssec. Migration to 2.0.x+ is only supported from 1.4.10+."
1703051,2019-11-28 14:34:58 UTC,"all these should be fixed in the latest package in eoan, or likely already in bionic"
1703066,2017-10-04 12:21:06 UTC,This issue was fixed in the openstack/horizon 11.0.4 release.
1703066,2017-08-25 10:04:18 UTC,"Change abandoned by Damon Li (<email address hidden>) on branch: master
Review: https://review.openstack.org/481443"
1703066,2017-07-27 20:57:54 UTC,This issue was fixed in the openstack/horizon 12.0.0.0b3 development milestone.
1703066,2017-07-24 14:48:01 UTC,"Found open reviews for this bug in gerrit, setting to In Progress."
1703066,2017-07-18 16:24:52 UTC,"Reviewed:  https://review.openstack.org/483531
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=9aa0915eb85c6b12676b789741a6964d43a60e28
Submitter: Jenkins
Branch:    stable/ocata"
1703066,2017-07-13 19:51:04 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/483531"
1703066,2017-07-13 18:28:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/483501"
1703066,2017-07-13 18:17:50 UTC,Horizon is hard-coded the old rule:
1703066,2017-07-13 18:15:50 UTC,There is no compute:get_all in horizon's default nova_policy.json either:
1703066,2017-07-13 18:13:48 UTC,compute:get_all doesn't exist in nova policy anymore:
1703066,2017-07-13 19:39:47 UTC,"Reviewed:  https://review.openstack.org/483501
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=69c81b16e07b67ba0a0bc8e1f55049e7987c5b8c
Submitter: Jenkins
Branch:    master"
1703066,2017-07-08 03:15:51 UTC,Please review: https://review.openstack.org/#/c/481443/
1703067,2017-07-08 17:46:33 UTC,"After further research, I found that running Thunar while Kazam was capturing a portion of the screen and if I moved the Thunar window into the area Kazam was capturing, after closing Kazam, Thunar would not allw me to change file names. After logging out and back in, Thunar let me rename files. I have reproduced this after the first time it happened. I am running Kazam installed from the main repositories and the Mint XFCE system is up to date as of the time tested."
1703070,2017-07-08 04:43:16 UTC,I hadn't realized that the package was incorrectly set on a previous setting.
1703074,2019-06-11 12:54:14 UTC,"Unable to reprodue this bug for master branch so marking it as invalid.
When i delete a resource like netwrok and subnet from the network topology panel,then it always shows a
sucess message after the resource deletion."
1703076,2017-07-11 19:31:44 UTC,"when I marked the dependent package for removal it was removable, I
reinstalled. Later, after disturbing fstab I re-entered as root, gave
myself write permission, controlled my errors and let DPKG fix broken or
missing packages.
My system runs fine now."
1703083,2019-08-29 15:24:21 UTC,Fixed by https://review.opendev.org/#/c/677507/ but I didn't format the commit message correctly...
1703083,2017-11-06 08:50:04 UTC,"The original link will be redirected to ""https://www.openssl.org/docs/manmaster/man1/ciphers.html"", seems it's from master branch not the latest release of OpenSSL."
1703088,2017-07-11 10:55:16 UTC,The -proposed package is from here LP: #1547647.
1703088,2017-07-08 09:04:57 UTC,"StacktraceTop:
 QtPrivate::RefCount::ref (this=0x4) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:54
 QV4::Heap::String::toQString (this=<optimized out>) at jsruntime/qv4string_p.h:84
 QV4::String::toQString (this=<optimized out>) at jsruntime/qv4string_p.h:145
 QV4::Heap::StringObject::StringObject (this=<optimized out>, engine=0xc88bb0, val=...) at jsruntime/qv4stringobject.cpp:91
 QV4::MemoryManager::alloc<QV4::StringObject, QV4::ExecutionEngine*, QV4::Value> (arg2=..., arg1=0xc88bb0, this=<optimized out>) at jsruntime/qv4mm_p.h:126"
1703089,2017-07-12 09:25:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/482867"
1703089,2018-04-03 19:12:04 UTC,"Reviewed:  https://review.openstack.org/482867
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=725873a7603946bd2bf3ba9476b947f6148fdf2f
Submitter: Zuul
Branch:    master"
1703091,2017-07-08 10:30:07 UTC,This change was made by a bot.
1703091,2017-07-24 19:29:43 UTC,"Replying to note 12, (I'm the guy with the Clevo P150SM)"
1703091,2017-07-24 18:31:07 UTC,"Revised report: 4.4.0-83-generic only affected one out of three Dell Precision M4600s. A quick look at their device compliment didn't reveal anything obvious. That is, the afflicted machine has the same network adapter as the other two, and the same camera device of one of the other two, and nothing unique on the USB bus."
1703091,2017-07-24 08:27:33 UTC,"Please try 4.4.0-87-generic from xenial-proposed, it has several fixes on nouveau."
1703091,2017-07-08 09:46:24 UTC,"Sorry for the wrong bug category, but it was my 1st contact with ""ubuntu-bug"" command line tool, and I did not know which category to choose."
1703091,2017-07-18 13:50:39 UTC,Confirm that same bug also affects Dell Precision T3600
1703091,2017-07-21 21:00:26 UTC,Confirm that same bug also affects Dell Precision M4600
1703091,2017-07-11 14:27:24 UTC,"Can you also give the latest upstream 4.4 kernel a test?  It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.76/"
1703091,2017-07-11 13:41:47 UTC,"Answering first to note 5, yes.
All the times that kernel 4.4.0-83 crashed, the problem goes away if I boot my previous kernel 4.4.0-81."
1703091,2017-07-10 17:45:50 UTC,"Also, does this bug go away if you boot the prior kernel version?"
1703091,2017-07-10 17:45:32 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1703091,2017-07-11 16:13:43 UTC,"Answering to note 7,"
1703091,2017-07-16 07:16:18 UTC,Confirm that same bug also affects Dell Latitude E5450
1703093,2017-07-08 09:53:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/481808"
1703093,2017-07-09 11:24:10 UTC,"Change abandoned by zhubingbing (zhu.bingbing@99cloud.net) on branch: master
Review: https://review.openstack.org/481808"
1703094,2017-07-08 10:10:42 UTC,"Perhaps important: I'm using RCS in emacs, so perhaps emacs (GNU Emacs 24.5.1) is acting weird and not RCS :). Anyway, RCS under emacs in Ubuntu 16.04 has a problem with editing log entries."
1703113,2017-09-12 16:52:00 UTC,"From overview, it looks like misconfiguration or something.
From the log, it's hard to tell.
Please provide more information."
1703116,2020-03-20 20:01:11 UTC,Not sure how I let this go for this long...
1703116,2017-07-21 10:34:37 UTC,This bug was fixed in the package ubuntu-mate-settings - 17.10.16
1703116,2017-08-30 01:29:22 UTC,This bug was fixed in the package xubuntu-default-settings - 17.10.0
1703116,2020-03-20 21:52:52 UTC,This bug was fixed in the package ubuntustudio-default-settings - 20.04.1
1703118,2017-07-12 14:31:05 UTC,Hello:
1703119,2019-07-28 00:17:36 UTC,Note: there's an interesting idea in the linked duplicate.
1703129,2017-07-11 19:06:27 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1703144,2017-07-11 19:57:19 UTC,"@Francesco, do we need the MimeType entries for anything? It seems quite useless for onboard-sessings.desktop, but is there a use case for onboard.desktop?
I believe opening *.onboard layout files would usually require extra work anyway to circumvent the single-instance checker. Clicking a layout file and switching Onboard to it at runtime isn't supported either."
1703144,2017-07-12 12:40:25 UTC,"I don't remember any special use of the MimeType in Onboard and considering that Onboard does not use any file associations, removing the MimeType from the desktop entries to silence the lintian warnings should not have any adverse side effect."
1703144,2017-07-22 07:01:24 UTC,"OK, they are gone, no more MimeType entries in trunk. Thanks for reporting, Jeremy."
1703147,2017-07-08 21:44:42 UTC,"On 8 July 2017 at 22:19, Duane Voth <email address hidden> wrote:

> Around line 1326 in gdbstub.c:
>
>             if (len > (MAX_PACKET_LENGTH - 5) / 2)
>                 len = (MAX_PACKET_LENGTH - 5) / 2;
>
> is truncating processor reg description xml files longer than 2045
> bytes.  Deleting these lines works for my immediate need, but they seem
> to be trying to fix some buffer overrun condition so I won't offer a
> patch until we understand their purpose.
"
1703150,2019-01-08 20:17:40 UTC,Confirming this for myself as it has just happened to me again with the same crashlog.
1703151,2017-07-18 06:26:39 UTC,"I have filed a bug report upstream, but am unable to add a tracker here - https://bugs.kde.org/show_bug.cgi?id=382450"
1703151,2017-07-27 16:37:46 UTC,Added the remote tracker.
1703162,2017-07-11 10:22:19 UTC,This issue has been ported over the current www.ubuntu.com project: https://github.com/canonical-websites/www.ubuntu.com/issues/2049.
1703165,2017-07-30 07:41:42 UTC,Did you use a turntable in your run?
1703165,2017-07-30 08:12:18 UTC,Yes. There's a turntables.dat in the OpenRails folder under this route. But I have set no paths go through the turntable during this run.
1703170,2020-04-11 01:26:47 UTC,This package is intended to provide a vanilla/upstream GNOME experience.
1703176,2017-07-09 08:48:32 UTC,"StacktraceTop:
 __assert_fail_base (fmt=0xf743009c ""%s%s%s:%u: %s%sAssertion `%s' failed.\n%n"", assertion=0xf6f38cd3 ""err >= 0"", file=0xf6f48d35 ""rawmidi.c"", line=268, function=0xf6f49588 <__PRETTY_FUNCTION__.9003> ""snd_rawmidi_open_conf"") at assert.c:92
 __GI___assert_fail (assertion=0xf6f38cd3 ""err >= 0"", file=0xf6f48d35 ""rawmidi.c"", line=268, function=0xf6f49588 <__PRETTY_FUNCTION__.9003> ""snd_rawmidi_open_conf"") at assert.c:101
 snd_rawmidi_open_conf (inputp=inputp@entry=0xf5f0081c, outputp=outputp@entry=0x0, name=name@entry=0xf5f007c8 ""hw:1,0,0"", rawmidi_root=0x980e5d8, rawmidi_conf=0xf5f01d58, mode=2) at rawmidi.c:274
 snd_rawmidi_open_noupdate (inputp=inputp@entry=0xf5f0081c, outputp=outputp@entry=0x0, root=0x980e5d8, name=0xf5f007c8 ""hw:1,0,0"", mode=2) at rawmidi.c:289
 snd_rawmidi_open (inputp=0xf5f0081c, outputp=0x0, name=0xf5f007c8 ""hw:1,0,0"", mode=2) at rawmidi.c:315"
1703176,2017-07-09 13:40:28 UTC,I think that the problem is likely in
1703184,2017-08-02 06:27:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703186,2017-09-21 09:39:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703186,2017-07-09 10:10:04 UTC,"StacktraceTop:
 request_find_from_trans_id (trans_id=23217, base=0x557bcd182560) at evdns.c:492
 reply_parse (base=0x557bcd182560, packet=0x557bcd183cc2 ""Z\261\201\200"", length=44, isudp=isudp@entry=0) at evdns.c:1148
 evdns_request_read_cb_tcp (bev=0x557bcd183950, ctx=0x557bcd1837f0) at evdns.c:906
 bufferevent_readcb (fd=10, event=<optimized out>, arg=0x557bcd183950) at bufferevent_sock.c:186
 event_process_active_single_queue (activeq=0x557bcd1622b0, base=0x557bcd182e60) at event.c:1368"
1703190,2017-07-23 23:59:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703190,2017-07-24 16:45:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu
better."
1703192,2017-07-10 10:41:10 UTC,This should be reported upstream.
1703194,2017-07-12 00:39:31 UTC,This may be a duplicate of https://bugs.launchpad.net/bugs/1673247
1703194,2017-07-12 00:40:34 UTC,I also added apport because this has some python 2 -> python 3 bugs in the hook errors.
1703194,2019-09-26 10:56:48 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1703195,2017-07-09 18:26:23 UTC,Thanks for reporting.
1703195,2017-07-11 07:02:17 UTC,"Thanks for that!
There were 2 problems...
One - My brain fade thanks - should have typed ubuntu-bug
Two - The location /usr/bin/VirtualBox worked (but without /usr/bin/ it failed)"
1703195,2017-07-12 16:41:14 UTC,The help for ubuntu-bug indicates that it can take the following arguments:
1703199,2018-01-15 19:22:10 UTC,Seems to be fixed in 17.10.
1703199,2018-01-15 13:53:45 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1703212,2019-07-17 13:20:43 UTC,"Can you reproduce this with a clean installation from stretch or buster? If not, please close this issue."
1703212,2019-09-16 04:17:34 UTC,[Expired for Raspbian because there has been no activity for 60 days.]
1703220,2017-12-19 06:50:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703226,2018-12-24 11:55:36 UTC,"Hello,
I also seem to encounter this bug, since the initial 18.04 release. Current system is:"
1703226,2018-03-31 18:18:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703226,2018-10-13 20:24:53 UTC,"Patrick, what did you find out? Other users have encountered this crash also, and it may be worth to investigate why it happens."
1703226,2017-07-09 17:24:56 UTC,"StacktraceTop:
 __GI___libc_free (mem=0xdbe258d4c544155) at malloc.c:2963
 g_free (mem=<optimized out>) at ../../../../glib/gmem.c:189
 g_error_free (error=0x55efe3884f80 <__libc_csu_init>) at ../../../../glib/gerror.c:491
 run (command=<optimized out>) at main.c:137
 main (argc=<optimized out>, argv=<optimized out>) at main.c:231"
1703226,2019-03-27 01:13:48 UTC,Noticed this bug in Ubuntu Studio 18.10 as well. After attempting to suspend session
1703226,2017-07-09 20:30:31 UTC,Cause of the system failed to hibernate has been traced to another issue and is no longer prevalent. Threfore this bug might be closed out.
1703226,2019-09-23 20:27:51 UTC,"This bug is still happening, and it's starting to get annoying."
1703227,2017-07-09 17:37:27 UTC,"Sorry, forgot to tell this error is booting from .Iso Live System."
1703229,2017-08-02 03:51:20 UTC,sadd
1703230,2017-07-09 19:36:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/481961"
1703231,2018-03-16 17:40:37 UTC,"Dear user,"
1703231,2018-04-24 18:23:27 UTC,This bug still exists in current MAAS stable release 2.3.2-6485-ge93e044.
1703231,2018-04-25 15:03:28 UTC,"Hi Vijay,"
1703231,2018-04-30 16:19:15 UTC,"Hi Andres,"
1703231,2018-08-07 15:23:06 UTC,"Possibly related, after concurrently updating multiple VMs I seem to end up with the below stack trace when I attempt additional updates to power parameters some of the time. It seems this magic to attempt to apply the update to multiple nodes may suffer a race condition."
1703231,2018-09-25 19:31:43 UTC,I think this issue may be the same issue as https://bugs.launchpad.net/maas/+bug/1793340
1703231,2019-09-19 14:48:44 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1703250,2019-09-24 11:43:00 UTC,Your fix from https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/trunk/revision/237 has a code size regression.
1703250,2019-08-30 16:46:45 UTC,I'm using avr-gcc 9.1 and worked around the issue with the -fgnu89-inline flag.  That way no code needs to be changed.
1703250,2019-07-21 02:35:28 UTC,Same with GCC 9.1. Replacing externing the inline fixes this for GCC 9.1 at least for the hello_world example.
1703250,2018-09-22 18:35:25 UTC,"Same with GCC 8
""extern inline"" hack solves the issue, Anduril had been successfully compiled on MacOs High Sierra with gcc and avr-gcc installed with Brew without specifying the versions etc (all default)"
1703250,2017-07-13 01:04:39 UTC,"I found a way to downgrade on arch, this is the most hassle free at the moment. The results are to no surprise the same for 5.3 on Arch and 5.4 on TW. For GCC 6.3 it was exactly the same as 7.1 but without failing:"
1703250,2017-07-13 14:59:06 UTC,I have looked up the changes that C99 brought to the inline keyword and changed the functions that threw an error to static inline and this results in no code size regression.
1703250,2017-07-11 23:17:47 UTC,"Interesting.  Thanks!  I don't have easy access to avr-gcc-7 yet, but this should be very helpful when that's more widely used.  I'll also have to do some testing to find the smallest compile options during the next updates."
1703250,2017-07-10 15:28:57 UTC,"Adding -std=gnu99 to the CFLAGS does nothing, while using extern inline to the functions, that are throwing the errors, works. -std=gnu89 works with just inline, but adds 4 byte. Sizes differ by a surprising amount, just in case you are interested:"
1703250,2017-07-09 21:25:23 UTC,"So, gcc 7.1 doesn't support the ""inline"" keyword by default?  What happens if you add -std=gnu99 to the compile options?"
1703250,2017-07-12 19:39:26 UTC,I was interested how everything behaves and got avr-gcc 5.4 to work on OpenSuse Tumbleweed (my main Distro) so here are tests with 5.4 and biscotti:
1703257,2017-07-09 22:28:57 UTC,There is an open issue for this at: https://github.com/linuxmint/Cinnamon/issues/5617
1703271,2017-07-31 08:52:34 UTC,"Although it's hard to tell if ""pulseaudio (1:10.0-2ubuntu1) artful"" fixed this because there are zero instances of this crash in artful. We won't really know until that version gets backported to zesty. And it's possibly still a bit too early for that."
1703271,2017-07-10 02:22:31 UTC,I expect this will be fixed by LP: #1690028 and LP: #1672171
1703271,2017-07-31 09:04:09 UTC,See also bug 1703272
1703272,2017-07-31 09:04:03 UTC,See also bug 1703271
1703272,2017-07-31 09:03:37 UTC,"Although it's hard to tell if ""pulseaudio (1:10.0-2ubuntu1) artful"" fixed this because there are zero instances of this crash in artful. We won't really know until the same fixes get backported to xenial. And it's possibly still a bit too early for that."
1703272,2017-07-10 02:22:27 UTC,I expect this will be fixed by LP: #1690028 and LP: #1672171
1703273,2017-07-10 03:07:34 UTC,Looks like this could be related to bug 1690028. That fix might improve things here.
1703280,2017-07-10 04:21:07 UTC,"The attachment ""Dmesg info of Guest OS"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1703280,2017-07-11 20:02:09 UTC,"Changing project to xen, as this is not related to qemu"
1703294,2017-07-10 06:25:05 UTC,This is not working with mainline kernel 4.12.0-041200-generic as well.
1703294,2018-03-26 11:15:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703302,2017-07-10 06:43:05 UTC,None
1703302,2017-07-19 15:47:31 UTC,You need to provide an /etc/kernel/cmdline file containing a kernel command line for dracut to work.
1703303,2017-07-18 06:39:48 UTC,"packstack versions:
openstack-packstack-10.0.1-1.el7ost.noarch
openstack-packstack-puppet-10.0.1-1.el7ost.noarch"
1703303,2017-07-13 02:17:32 UTC,"This isn't a nova bug, you'd have to find the proper bug tracker for packstack."
1703303,2017-07-17 07:56:31 UTC,"What version of packstack are you using?, this has been fixed in https://review.rdoproject.org/r/#/q/Ie7477ac07c61d0814598a95ea6289838ddea224c,n,z"
1703303,2017-09-29 12:21:55 UTC,any updates on this?
1703304,2017-07-27 20:58:02 UTC,This issue was fixed in the openstack/horizon 12.0.0.0b3 development milestone.
1703304,2017-07-15 19:07:10 UTC,Horizon patch here: https://review.openstack.org/#/c/482104
1703305,2017-07-10 14:33:12 UTC,"This isn't actually a bug in tempest, those are interfaces that will be removed in a future version. The neutron tempest plugin is using them which is causing the warning to be emitted. The issue is that the neutron plugin code needs to be updated"
1703315,2017-09-01 23:11:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703321,2017-07-11 06:25:07 UTC,"which XtraBackup version are you using?
please share the full backup command used and the full prepare command used.
please attach full backup log where backup completed OK."
1703321,2017-07-14 06:35:16 UTC,"backup log:
170708 04:03:11 innobackupex: Starting the backup operation"
1703321,2017-07-24 07:53:03 UTC,So could you please share the MySQL's my.cnf + exact backup and prepare commands?
1703321,2017-07-24 08:47:48 UTC,"the commands: innobackupex --apply-log --use-memory=20G  ${backup_file_dir} >${backup_file_dir}/apply.log 2>&1
innobackupex version 2.4.7 Linux (x86_64) (revision id: 05f1fcf)
 my.cnf :
[mysql]
port=*
prompt=\\u@\\d\\r:\\m:\\s>
no-auto-rehash"
1703321,2017-07-24 09:01:06 UTC,"Thanks,
So this is your prepare command:"
1703321,2017-07-24 09:19:22 UTC,"sudo ${innodbackup}  --defaults-file=${mycnf} --user=${user} --password=${password} \
       --slave-info --lock-wait-threshold=5 --lock-wait-query-type=all --lock-wait-timeout=60 \
       --stream=tar /*/tmp --no-timestamp  --socket=${socket} \
       | lz4 -B4 | pv -q -L${netlimit} | nc $localhost 9988"
1703321,2018-01-20 07:38:44 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1452
1703329,2018-03-30 08:46:09 UTC,I think there is a need for vnffg and vnffgd now.
1703333,2017-07-17 05:31:38 UTC,"Change abandoned by Imran Ansari (<email address hidden>) on branch: master
Review: https://review.openstack.org/482140
Reason: A similar patch by xing-yang is available at https://review.openstack.org/#/c/479517/"
1703333,2020-05-11 20:24:14 UTC,This has been implemented by https://review.opendev.org/#/c/479517/
1703333,2017-07-10 13:22:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/482140"
1703333,2017-07-10 13:22:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/482141"
1703333,2017-07-10 13:32:27 UTC,"Change abandoned by Imran Ansari (<email address hidden>) on branch: master
Review: https://review.openstack.org/482141
Reason: Not required as this has been taken care of in https://review.openstack.org/#/c/482140 as a patch"
1703339,2017-09-06 12:24:33 UTC,"Ah, yes I did forget to add the module to the installer udebs. I'll do that now."
1703339,2017-07-10 10:30:06 UTC,This change was made by a bot.
1703339,2017-08-16 07:46:08 UTC,This bug was fixed in the package linux - 4.12.0-11.12
1703339,2017-09-01 10:08:57 UTC,Has the change been applied to Ubuntu Server? It still doesn't seem to be working there.
1703339,2017-09-01 12:16:57 UTC,Are you testing artful? I just confirmed that vmd.ko is included in the main kernel package in artful.
1703339,2017-09-01 13:48:41 UTC,"Yes, I tested it today with artful."
1703339,2017-09-06 13:17:01 UTC,"A quick question about VMD, which will affect what installer package vmd.ko should go in. When I search about VMD everything I read is about disk devices, yet when I read the kernel changelog and Kconfig descriptions it sounds more like a generic PCI bridge. Is it possible that there would be non-disk devices under the VMD domain, e.g. NICs?"
1703339,2017-09-06 15:34:22 UTC,Thanks Keith. I've pushed a commit to artful 4.12 and 4.13 kernel trees to include this in the storage-core-modules udeb.
1703339,2017-09-21 00:28:06 UTC,This bug was fixed in the package linux - 4.13.0-11.12
1703339,2017-10-09 12:11:19 UTC,"The disks under VMD controller are visible in the installer, it is possible to install the system, however vmd.ko is not added to initrd so the system cannot boot."
1703339,2017-10-14 02:32:02 UTC,This bug was fixed in the package initramfs-tools - 0.125ubuntu12
1703339,2017-10-23 15:55:41 UTC,Added xenial nomination for initramfs-tools to add vmd.ko to initrd for 16.04.4.
1703339,2017-09-06 14:55:43 UTC,"The intended use for VMD is as a PCIe storage domain, so we expect only to see root ports, switches and NVMe SSDs in the VMD domain."
1703343,2019-07-03 10:46:01 UTC,"libwireshark8 being half-installed is rather strange. If the original reporter does not provide more details (such as further terminal output), I'd suggest to close this issue."
1703343,2017-07-11 19:31:08 UTC,This may be a duplicate of bug 1692981.
1703343,2019-09-02 04:17:21 UTC,[Expired for wireshark (Ubuntu) because there has been no activity for 60 days.]
1703343,2017-07-11 19:30:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1703343,2017-07-11 19:30:54 UTC,Please note you may have hardware issues on this machine. Install mcelog and check the resulting logfiles.
1703346,2017-10-25 11:49:15 UTC,Reported at https://bugs.mysql.com/bug.php?id=88223
1703346,2017-10-10 02:57:54 UTC,"Why 5.7 has been set to Invalid? https://bugs.mysql.com/bug.php?id=72457 says ""[8 May 20:13] Jay Edgar
I was able to reproduce this on both 5.6.35 and 5.7.18."""
1703346,2018-01-25 09:12:43 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1107
1703346,2017-10-25 10:57:49 UTC,Because I was not able to reproduce this bug with 5.7 back in time. But looks like it depends from internal_tmp_disk_storage_engine and default_tmp_storage_engine settings. If they set to MyISAM I either get:
1703346,2018-01-18 08:21:22 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1994
1703354,2017-07-10 12:01:43 UTC,Thanks for the report. I'll take a look. Can you attach the Phyml and the substitutions file (or the substitution you were trying to do) here so I can try and replicate this?
1703354,2017-07-10 12:22:20 UTC,"Thanks for the quick reply! Files are attached.
- Fabian"
1703354,2017-07-11 09:17:52 UTC,"Super. Thanks. I'll try and get this looked at this week.
J."
1703354,2017-07-12 06:54:40 UTC,Bug is caused by assuming tree names are in the form sourceName_n where n is an integer. This is a long-standing bug. Fix is to replace this code with more generic searches in _swap_tree_in_xml
1703354,2017-07-12 07:07:50 UTC,Fix committed in: https://github.com/supertree-toolkit/stk/tree/fix_lp1703354
1703354,2017-07-12 19:02:05 UTC,Thanks for the quick help John! The github link is not working (for me) though...
1703354,2017-07-13 04:18:37 UTC,Sorry - I merged it into master and deleted the branch: https://github.com/supertree-toolkit/stk
1703354,2017-07-15 13:24:17 UTC,Thank you very much :)
1703358,2017-07-10 12:14:12 UTC,This is the situation now:
1703358,2017-07-10 12:14:58 UTC,"Note that I did select gdm3 manually at the prompt, so that is correct now."
1703358,2017-07-10 13:04:18 UTC,Looking at your log i see:
1703358,2017-07-10 14:25:21 UTC,"According to my history.log, I upgraded from ubuntu-session 3.24.1-0ubuntu8 to 3.24.1-0ubuntu9 on 2017-07-03. Then from 3.24.1-0ubuntu9 to 3.24.1-0ubuntu11 on 2017-07-10 (today). I think you're looking at an older part of my log?"
1703364,2020-03-24 15:01:36 UTC,"I'd say this got fixed by https://review.opendev.org/#/c/527889/
If you disagree, feel, free to reopen the issue."
1703364,2017-07-13 06:03:56 UTC,https://review.openstack.org/#/c/481765/ and https://review.openstack.org/#/c/482218/3 reviews has some information related to cinder v2 API for tempest.
1703377,2020-08-12 08:44:03 UTC,This bug is still present on Ubuntu 20.04.
1703377,2018-03-03 17:28:45 UTC,This is reported as a bug in Gnome's bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=778662
1703377,2018-03-03 17:28:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703377,2017-07-10 14:16:33 UTC,Ubuntu GNOME 16.10 will reach End of Life next week which means there isn't really time for any bugfixes that are not already in progress or very critical.
1703377,2017-09-19 21:26:56 UTC,Same here.
1703377,2017-09-09 04:17:31 UTC,[Expired for gnome-online-accounts (Ubuntu) because there has been no activity for 60 days.]
1703377,2017-12-19 05:15:31 UTC,Same situation here but not specific to Ubuntu. Same situation on Debian Stretch with Gnome 3.22.2.
1703397,2017-07-20 07:03:47 UTC,There is no ADT testing running for ESM (as all is private PPAs).
1703397,2017-07-21 08:51:00 UTC,Skipping this time. The Trusty kernel of the same version is already in updates.
1703397,2017-07-21 11:32:48 UTC,The package has been published and the bug is being set to Fix Released
1703397,2017-07-20 14:10:27 UTC,"3.13.0-125.174~precise1 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1703401,2017-07-10 15:59:43 UTC,apport information
1703401,2017-07-10 15:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1703401,2017-07-10 15:59:40 UTC,apport information
1703401,2017-07-10 15:59:41 UTC,apport information
1703401,2017-07-10 15:59:42 UTC,apport information
1703401,2017-07-10 15:59:44 UTC,apport information
1703401,2017-07-10 15:59:46 UTC,apport information
1703401,2017-07-10 15:59:47 UTC,apport information
1703401,2017-07-10 15:59:49 UTC,apport information
1703401,2017-07-10 15:59:50 UTC,apport information
1703401,2017-07-10 15:59:51 UTC,apport information
1703401,2017-07-10 15:59:52 UTC,apport information
1703401,2017-07-10 15:59:54 UTC,apport information
1703401,2017-07-18 08:01:00 UTC,This bug was fixed in the package linux - 3.13.0-125.174
1703401,2017-07-10 15:59:45 UTC,apport information
1703405,2020-05-02 16:18:22 UTC,"Reviewed:  https://review.opendev.org/724690
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=68b381bf252939b48bbcc1e3e4c279ba7233d1d0
Submitter: Zuul
Branch:    stable/ussuri"
1703405,2020-04-30 15:12:06 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/724690"
1703405,2020-04-28 22:09:17 UTC,"Reviewed:  https://review.opendev.org/722353
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=406e0778ec0be8455091684667478d7a570ceaa0
Submitter: Zuul
Branch:    master"
1703405,2020-04-22 14:45:54 UTC,"Reviewed:  https://review.opendev.org/683103
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=06b9e3c498b833aa602cb10ca640979850af517a
Submitter: Zuul
Branch:    master"
1703405,2018-12-09 14:52:09 UTC,I agree with Jay. marking invalid for Tempest.
1703405,2018-12-06 14:55:21 UTC,There are a few features that fail tempest testing on various backends.  They blacklist those tests so that testing passes.  I don't know off the top of my head how many drivers don't implement this but I think that just disabling the test for drivers that don't is the best way to go rather than trying to add more config options.
1703405,2019-09-19 10:17:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/683103"
1703405,2018-10-11 13:45:31 UTC,"Hi Manik!
Yes, this issue is still current, i just manually verified to be sure.
Running current master branches with Devstack and using the Cinder Quobyte driver and the PosixBackupDriver to run the tempest test referenced above."
1703405,2018-10-11 12:04:24 UTC,We are running into a similar issue both in above tempest tests as well as when manually creating a backup of a volume with an attached snapshot. This is happening with OSP12 with a Isilon backed NFS cinder backend using the generic NFS driver (The error does not occur when using a NetApp backend with its native driver)
1703405,2018-10-11 06:34:34 UTC,"Hi Silvan,"
1703405,2017-09-14 12:23:21 UTC,"Change abandoned by Silvan Kaiser (<email address hidden>) on branch: master
Review: https://review.openstack.org/503686
Reason: This just overrides the default and does not fix #1703405"
1703405,2017-09-13 14:00:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503686"
1703405,2017-07-11 15:37:32 UTC,"The tempest test only checks for ""volume_feature_enabled.backup"", meaning it equates backup support with snapshot backup support.  This is not correct, not all Cinder drivers support snapshot backup."
1703405,2018-12-06 09:42:25 UTC,"yeah as per Eric, not all cinder driver support snapshot backup. is there any way to detect this via cinder API?"
1703411,2018-09-06 17:54:02 UTC,"I've got a typo there... Force-pushed a branch fixing that, but I'm going to push an update that attempts to shift completely to a subelement rather than duplicating attributes for backward compatibility with older clients.  That will cause a complete break in compatibility with older clients, but may well be necessary."
1703411,2018-08-29 12:53:39 UTC,Here's another set of logs from after Mike's branch is applied.
1703411,2018-08-28 19:18:46 UTC,"Well, that branch gets a little bit farther. When I run osrf_control -l --diagnostic after starting services, I get the folowing:"
1703411,2018-08-28 18:33:59 UTC,"If the comment in that link is correct, and enough, and we don't need to implement an entire extension, then I offer this WIP branch:"
1703411,2018-08-28 17:25:37 UTC,"So, my reading of the ejabberd bug is that we have to reimplement the OpenSRF message extensions for ejabberd 17+."
1703411,2018-08-28 16:24:03 UTC,I experimented with ejabberd and OpenSRF on Ubuntu 18.04 this morning. I could not get any better results than Chris Sharp reports in comment #3.
1703411,2018-08-28 16:50:15 UTC,I think this is the smoking gun (from router.log):
1703411,2018-08-10 11:40:00 UTC,"Well, actually, I spoke too soon.  ejabberd is still rejecting connections.  This time, the error message from OpenSRF is:"
1703411,2018-08-09 21:05:05 UTC,"I can confirm that uncommenting ""mod_legacy_auth: {}"" in /etc/ejabberd/ejabberd.yml allows OpenSRF to work, but the other problem here is that ejabberd is more strict about enforcing STARTTLS.  Setting ""loglevel"" to ""5"" (debug) allowed me to see this (after enabling legacy auth):"
1703411,2018-03-16 17:07:21 UTC,"Well, Ubuntu 18.04 is going to use a newer ejabberd that has the legacy auth disabled by default.  Adding the directive here does not get us all the way around the problem though.  There's a lot of areas in the design where the authentication just really does not like us using plain text.  Still testing with OpenSRF master and Ubuntu 18.04 at the moment and gathering information."
1703411,2018-08-28 17:02:02 UTC,Related to previous comment:  https://github.com/processone/ejabberd/issues/1692
1703411,2018-09-19 17:41:27 UTC,Opened a separate LP for addressing the XML attributes issue:  bug #1793356.
1703415,2020-12-17 01:49:02 UTC,Oops. It appears this was fixed in gdm3 in 2017. If you have any more problems then please open new bugs.
1703415,2017-07-25 13:06:39 UTC,I can confirm this one on (X)ubuntu 14.04.5 LTS with XFCE 4.10 desktop.
1703415,2020-12-16 15:07:20 UTC,"Hello,
I'm landing here after tracking a bug : I could not output sound to my SRS-XB22 bluetooth speaker.
I had in logs :
`src/service.c:btd_service_connect() a2dp-sink profile connect failed for F8:DF:15:7F:ED:AA: Protocol not available`"
1703415,2018-07-30 10:19:12 UTC,-- GitLab Migration Automatic Message --
1703415,2017-07-13 16:01:32 UTC,This bug was fixed in the package gdm3 - 3.24.2-1ubuntu9
1703415,2017-07-13 11:44:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703415,2017-07-13 04:10:05 UTC,"But see also:
https://bugs.freedesktop.org/show_bug.cgi?id=90490"
1703415,2017-07-12 09:55:15 UTC,The Arch wiki mentions this problem and only suggests disabling the gdm pulse instance :P
1703415,2017-07-12 09:30:38 UTC,I think you might have two different bugs...
1703415,2017-07-13 04:09:55 UTC,"A better upstream bug report for PulseAudio might be:
https://bugs.freedesktop.org/show_bug.cgi?id=98144"
1703415,2017-07-10 19:30:32 UTC,Ok. Also consider backporting this to 16.04 LTS and 17.04.
1703415,2017-07-10 19:17:41 UTC,@jbicha - Confirmed: same bug.  I have a branch with a workaround which I'll attach here shortly.
1703415,2017-07-10 19:11:51 UTC,"If this is accepted, we need to add a known issue to the release notes, and add a task for next cycle to follow up with the PulseAudio developers."
1703415,2017-07-10 18:25:06 UTC,"Will, could you check if this is a duplicate of LP: #1489651 ?"
1703415,2012-11-15 20:44:28 UTC,"(In reply to comment #0)

> The problem here is that
> there's no clean ""force unsuspend"" mechanism in pulseaudio.
> pa_sink_suspend(u->sink, FALSE, PA_SUSPEND_IDLE|PA_SUSPEND_USER) may not
> actually unsuspend the sink, because there are also other suspend reasons
> than just IDLE and USER. So, depending on the situation, the sink may or may
> not get unsuspended.
>
> module-bluetooth-device could list all possible reasons in the
> pa_sink_suspend() call, but that would be ugly. When adding new suspend
> reasons, it would be very easy to forget to update the pa_sink_suspend()
> call in module-bluetooth-device, and besides, if those suspend reasons are
> originally set by some other code, the original reasons to suspend don't
> really disappear when module-bluetooth-device unsuspends the sink, the old
> reasons are just overridden.
"
1703415,2012-11-15 19:31:15 UTC,In module-bluetooth-device.c in filter_cb() there's this piece of code:
1703415,2017-07-11 14:13:11 UTC,Added to Trello: https://trello.com/c/2ZNFGt8r/186-bug1703415-disable-bluetooth-sink-in-gdm-to-allow-a2dp-in-the-user-session
1703416,2017-07-14 04:07:49 UTC,Good Day Alvin
1703416,2017-07-14 10:59:33 UTC,For getting info about things that are not bugs:
1703416,2017-07-14 10:14:59 UTC,"I have never used these operations, so I can't comment on them. However, you may be able to get some help from the user mailing list:
http://inkscape.13.x6.nabble.com/Inkscape-User-f2857977.html"
1703416,2017-07-14 08:57:25 UTC,"Hi Alvin
Thanks for the feedback. I used Vacuum Defs in 0.48 on one of my images
that was 13MB and it decreased it to just over 1mb :-) . Is the a program
that can scan through all my images that I created with inkscape and do the
same job? Do I have to click on each image and run vacuum defs?
Remember that if and image is too big in 0.48, The app crashes when opening
the image.... or if Itry opening it with 0.92... it literally takes forever
to open."
1703416,2017-07-14 04:05:57 UTC,"Good Day
Where do I find the cleanup doc exe file and how do I run it?
Best Regards"
1703416,2017-07-14 08:17:27 UTC,I think that maren was referring to the menu item called 'File->Clean Up Document'
1703416,2017-07-13 09:43:31 UTC,"Hi,
    I was not able to open the image called Leeuw.png, I get a message saying it is not a valid bitmap file. However I was able to load the file ClintonLeeuw.svg. It took a while to load. When I click on the Select All menu item I get a lot of rectangles that look like your image in comment 1. When I interrogate these objects it appears that they are mostly either <flowroot> elements or <text> elements, except that the text in them consists of just a single blank space. I am attaching a typical flowroot element below.
    I guess the question is, where did they originate? Your initial comment seemed to say that this image was originally created in an earlier version of Inkscape. Could you attach that original image for comparison purposes?"
1703416,2017-07-13 06:52:34 UTC,Good Day
1703416,2017-07-11 04:50:27 UTC,"Good Day
Thanks for the reply.I checked the file size of a few .svg images I created
using inkscape 0.48 and some of them are between 16Mb - 20Mb. These images
are usually up to 5Mb max.
As mentioned, I import the image into 0.92.1 and it takes a very long time
to import the image (Clinton Leeuw.svg 29.5Mb) once it is open, I select
(just the image) of the two headstones and try to export it as a bitmap on
0.92.1, It then calculates the image to be 116044x61711 - 26.5Mb .... the
image selected should be no more than 2Mb max.
Best Regards"
1703416,2017-07-10 20:40:50 UTC,Those dots could also be selected objects. Could you rather provide the SVG file?
1703416,2017-07-13 16:59:29 UTC,"Also run 'clean up document' - you have > 134000 unused defs.
Here's the fixed file:
(removed flowed texts, cleaned up defs, resized objects, so they are in actual size, at least in relation to width, the proportions were already incorrect, centered contents on page, resized page to contents)"
1703417,2017-07-10 17:47:05 UTC,This is all!
1703419,2020-09-20 13:23:34 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1703419,2017-07-11 09:51:51 UTC,"yes, the terminology ""on Windows: (\share)\palettes directory in Inksape installation directory"" is a bit confusing in my opinion. It is not entirely clear from this that a user directory actually exists. It might be better to be a bit more explicit, as in:"
1703419,2017-07-10 20:38:11 UTC,"You're supposed to drop them into your user config directory, which is accessible to you without admin priviledges. It might be that you still need to create the palettes directory there.
(User config directory: Edit -> Preferences -> System: User config)"
1703419,2017-07-10 22:13:23 UTC,"In that case, the FAQ should be updated:"
1703424,2018-01-04 16:53:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703428,2017-07-12 19:17:15 UTC,It's the very first entry under the global (not profile) Preferences.
1703433,2017-07-10 20:42:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703434,2017-07-10 18:37:11 UTC,I'm assigning this to myself to prevent people submitting patches for this before Queens :-)
1703434,2017-07-10 18:40:34 UTC,Marking approved as there seems to be agreement from Today's IRC meeting that this should be the case.
1703440,2017-08-14 17:27:54 UTC,"Something else to bear in mind is that because you aren't using direct=1 (see http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-direct ) there's nothing (other than size) stopping your I/O being entirely cached in RAM thus creating unrealistically fast speeds. Worse still, there's a good chance that ZFS doesn't support O_DIRECT so you won't be able to use direct=1 even if you wanted to. To try and combat this you will have to write/read an area at least twice the size of your RAM (2 GBytes is likely too small). I know you get fast SSDs but doesn't 3GByte/s seem unusually high? :-) The usual telltale sign that your I/O is being cached in RAM is that the minimum latency is 0ms - if you ever see that you will know you're suffering/benefiting from OS caching."
1703440,2017-08-16 05:32:00 UTC,@fmyhr:
1703471,2017-08-18 13:32:02 UTC,Since the command-* wrappers are originating from snapcraft I'm moving the bug there. I'm also marking it as CONFIRMED since the wrappers don't have the desired PATH entry.
1703473,2017-07-24 08:16:07 UTC,A simple update to the latest version of Mnemosyne will fix this.
1703473,2018-01-18 12:53:09 UTC,Need both Debian & Ubuntu upgrades
1703473,2020-05-21 12:59:19 UTC,works in focal
1703475,2017-07-14 12:00:59 UTC,"Thank you very much for the picture.
I like to verify my magic formular using you vinyl player.
Could you record time code sound using your record player? Stating with normal speed, and then playing with minimum and maximum pitch, spin down and up cycle and finally a slow 0 to Max speed scratch."
1703475,2017-07-14 01:36:13 UTC,"Hmm, nevermind it seems the Z2 can't work that way unless you use another sound card. That's unusual."
1703475,2017-07-13 23:22:50 UTC,"By the way, Daniel, to be honest, I didn't notice that; but now I was paying attention to that, it's true that the wave dooesn't sound louder when scratching, like with real vinyl. I compared scratching the ""aaah"" sound between Traktor, Mixxx and real vinyl, and both software achieve it! It's nice!"
1703475,2017-07-13 23:28:50 UTC,"Ok, maybe that gain change it's too much in Mixxx... I'll tell you in the pull."
1703475,2017-07-15 00:11:51 UTC,Sure! Here you have it with the Traktor MKII...
1703475,2017-07-14 01:15:45 UTC,"I mean, why don't you use the unmixed Deck 1 & 2 outputs and use the Z2 for mixing instead of mapping the faders to Mixxx's software controls?"
1703475,2017-07-15 00:20:31 UTC,"...and here with the MixVibes (argh, dup MK2 comment!)"
1703475,2017-07-13 23:04:25 UTC,"Yes, it's workable for now, Ben, thanks. Besides, now I see it's more complicated than I expected to fix that (not just changing values)..."
1703475,2017-07-30 22:11:07 UTC,"Maybe Traktor uses such a curve because they want to avoid clipping at fast scratches?
From my test, when I have first worked on the vinyl gain PR, I notices less gain chaining in the fast regions but that happens by far later.
Your recording has an almost linear change up to 3 x speed.
You maximum speed is ~5x my curve will apply 5.5 dB in that case which should not clip with a reasonable gain leveling (headroom)."
1703475,2017-07-30 23:59:19 UTC,"> Did you use a phono preamp with a the Riaa curve applied?
My turntables are directly connected to my Traktor Z2 mixer (of course with the input line switch in phono mode). I have no idea about its internal preamps, but as I can read in the first post in the link above, it seems that the answer to this question is yes.
"
1703475,2017-07-31 06:15:41 UTC,"No, there is no need to do a recording with other gear. I believe the Z2 does the things just right."
1703475,2017-07-31 16:48:36 UTC,"Yes, I think that's a good shot, to limit it to 6 dB."
1703475,2017-12-28 10:12:59 UTC,This is a mandatory basic function.
1703475,2017-12-28 14:53:25 UTC,"I agree that this is a basic function, but I think it will require quite a bit of complicated refactoring and I'm not sure it should be rushed for 2.1. But discussing this any further may be premature without seeing the code."
1703475,2017-07-13 22:26:58 UTC,"> limiting the ramp time to 3 ms with the crossfader at maximum sharpness regardless of the configured buffer size?
"
1703475,2017-07-30 21:44:04 UTC,"Thank you for the very useful recordings.
Did you use a phono preamp with a the Riaa curve applied?
I am asking, because gain increases much more in the fast region before the needle starts loosing vinyl contact. The curve applied in Traktor does just the opposite, less gain changing in the fast region."
1703475,2017-07-13 21:59:14 UTC,"> Could anyone tell me why, please?
"
1703475,2017-07-11 12:04:33 UTC,"Thanks! Unfortunately, I can't run the installer even with the MSVC 2015 installed. I have a Spanish version, but I'll make an approximate translation of the message that appears just when I execute it: ""Can't open this installation pack. Please contact the application developer to verify that it's a good Windows Installer pack."""
1703475,2017-07-13 21:36:54 UTC,"This is with DVS. The wave is a human scream, so it's more irregular; anyway, the cuts are only when you see clearly the gaps (the end is not cut)"
1703475,2017-07-11 00:14:34 UTC,"Could you try installing this and setting the crossfader to the maximum sharpness in the preferences? Is it sharp enough for you?
https://ci.appveyor.com/api/buildjobs/fapudxr335hsgpc7/artifacts/mixxx-2.1.0-alpha-pre-master-PR1311-git6321-release-x64.msi"
1703475,2017-07-11 00:23:56 UTC,"The Kontrol Z2 is a USB class compliant sound card and HID controller and could be used that way on any OS Mixxx runs on. Unfortunately mapping HID controllers is currently quite a bit more complicated than mapping MIDI controllers. Recently work on improving the process of mapping HID controllers has been started, but it will probably be a while before it is ready. If you are curious, you can follow the discussion here:
https://github.com/mixxxdj/mixxx/pull/1308"
1703475,2017-07-11 12:26:40 UTC,Please report a new bug for that issue.
1703475,2017-07-11 12:49:42 UTC,"Ok, the last installer in bug #1663380 works fine for installation (but sblaisot is still working for a right unnstallation). I've tested by myself."
1703475,2017-07-12 17:00:06 UTC,"Ok, I finally could install that alpha you gave me. I set again the crossfader to the fastest cut and it sounds a little better, but I would need more. Could it be? The ideal is like a switch (on/off sound, with no curve). The only need to make a curve is for a technical thing: avoiding ""clicks"" (""ugly"" wave cuts done out of 0dB, specially dangerous when cutting bass, where it's more probable)."
1703475,2017-07-12 21:20:37 UTC,"Can you explain your use case?
Which audio buffer size do you use?"
1703475,2017-07-13 21:53:19 UTC,"> Do you mean limiting the ramp time to 3 ms with the crossfader at maximum sharpness regardless of the configured buffer size?
"
1703475,2017-07-12 22:29:52 UTC,"I'm not sure if I understood right the first question, so I'll answer it a little widely."
1703475,2017-07-13 06:32:12 UTC,"I the video in the initial post, do you use a time coded vinyl? I assume the buffer size is 21.3 ms I'm both cases?
I will analyze the recorded sound a and try to compare to compare the ramps. Maybe we can reduce the ramp internally for big buffers in the scratching case.t"
1703475,2017-07-13 08:23:26 UTC,"One unrelated question:
Did you notice a difference between vinyl scratching and time code scratching regarding gain by tempo changes? I have done a pull request that is trying to fix that:
https://github.com/mixxxdj/mixxx/pull/602
Does it has any value for you?"
1703475,2017-07-13 14:01:12 UTC,"> An other idea, could be a mapping issue.
Mixxx suffers the issue that the we engine is not synced with midi. So it might happen, that it receives a LSB midi message first. Which leads to a 42.6 ms fade.
"
1703475,2017-07-13 19:44:17 UTC,"I have measured the Video from the first post and I can clearly measure the 21.3 ms ramp up and down. While the first part only has ~3 ms.
The syncing is no issue, but it can be in theory.
So I think the best solution is to limit the ramp to 3 ms and remove all fading from the xfader curve at 1000 to avoid the theoretical midi race condition issue from above.
The 3 ms should be only applied for these hard -Inf t 0 transitions. Else a continuously fading is broken.
@Be: Do you have fun to adopt this, or should I take a look?"
1703475,2017-07-13 21:28:43 UTC,Do you mean limiting the ramp time to 3 ms with the crossfader at maximum sharpness regardless of the configured buffer size?
1703475,2017-07-13 21:31:42 UTC,"Be, it's true: I set the audio buffer to 5.3 ms and it improved a lot (now it's acceptable for me). I didn't expect this, because with Traktor, cuts always sound practically like the real crossfader, no matter what buffer audio size use. Could anyone tell me why, please? Audio buffer in Mixxx is for actual processing audio instead of for already processed audio?"
1703475,2017-07-12 22:52:55 UTC,"> I think this is not actually a movement distance problem in the crossfader, but in speed fading (cutting or ""switching on"") the sound by software when the crossfader sends the value for the change.
"
1703479,2018-07-08 10:53:34 UTC,"Sorry, I forgot this: Is there a boot option I can set to change this behavior? Either to use local-time in HW clock or simply prevent writing to HW clock in live mode?"
1703479,2018-07-08 10:52:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703479,2017-07-11 00:23:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1703479,2018-05-29 07:45:36 UTC,"On those live CDs there should be no NTP daemon running anyway.
And even if so we switched which defaults to non-utc for the following reason:
       rtconutc
           chronyd assumes by default that the RTC keeps local time (including any daylight saving changes). This is convenient on PCs running
           Linux which are dual-booted with Windows."
1703479,2018-07-08 10:51:47 UTC,This also happens with 18.04.
1703488,2017-07-21 15:55:50 UTC,We should have Moshe Levi (moshele in IRC) take a look at this.
1703488,2017-07-27 14:14:22 UTC,"This seems like a legit issue, should probably just scrub the node of all the pci data before new content is added."
1703488,2017-07-27 14:15:16 UTC,"By node, I mean that we seem to have this compute node scoped, so a node overwriting it's own entries (including delete) seems pretty safe"
1703493,2017-07-11 15:34:40 UTC,Please provide the actual input used to generate the above trace.
1703493,2017-07-12 00:45:58 UTC,"Hello, Eric, My input is as follows:
[root@ctrl173 ~(keystone_admin)]# cinder --debug create  1 --name 我的云盘
DEBUG:keystoneclient.session:REQ: curl -g -i -X GET http://192.168.100.176:5000/v2.0 -H ""Accept: application/json"" -H ""User-Agent: python-keystoneclient""
DEBUG:keystoneclient.session:RESP: [200] Vary: X-Auth-Token Content-Type: application/json Content-Length: 341 X-Openstack-Request-Id: req-07ff8e2a-a2c0-4277-af33-ee34d514b6d2 Date: Wed, 12 Jul 2017 00:34:01 GMT
RESP BODY: {""version"": {""status"": ""stable"", ""updated"": ""2014-04-17T00:00:00Z"", ""media-types"": [{""base"": ""application/json"", ""type"": ""application/vnd.openstack.identity-v2.0+json""}], ""id"": ""v2.0"", ""links"": [{""href"": ""http://192.168.100.176:5000/v2.0/"", ""rel"": ""self""}, {""href"": ""http://docs.openstack.org/"", ""type"": ""text/html"", ""rel"": ""describedby""}]}}"
1703493,2017-07-12 00:52:23 UTC,"I got it. This bug is triggered in debug mode. when you set debug = True in cinder.conf,
you will get it actually."
1703493,2018-01-19 10:35:34 UTC,It's a bug from oslo.log
1703493,2018-04-14 18:15:53 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/482389
Reason: No updates for a long time. Feel free to restore and update if you wish to continue with this."
1703493,2018-07-31 03:15:10 UTC,I ran into a very similar issue when debug was enabled. Tempest testing was running using unicode tests resulted in the following stacktrace - http://paste.openstack.org/show/726897
1703493,2018-07-31 03:40:30 UTC,"hi, Kevin,"
1703496,2018-01-20 07:38:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1453
1703501,2017-12-05 19:38:08 UTC,This issue was fixed in the openstack/freezer-web-ui 6.0.0.0b2 development milestone.
1703506,2017-07-18 13:43:38 UTC,"I can confirm this problem as it affects me, too on Ubuntu XENIAL, Kernel 4.10.0-26-generic"
1703506,2018-01-30 16:00:47 UTC,"Posted few patches to support this feature on AMD EPYC processors. Feel free to test and review.
1. Kernel kvm patch
   https://patchwork.kernel.org/patch/10190107/
2. qemu patches
   https://patchwork.kernel.org/project/qemu-devel/list/?submitter=178527
Thanks"
1703506,2020-11-16 18:08:34 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1703506,2017-07-25 18:38:53 UTC,The core topology info used by Linux (see linux/arch/x86/kernel/cpu/amd.c:amd_get_topology()) is actually at CPUID[0x8000001e].
1703506,2018-12-13 15:49:18 UTC,"I got it to work:
sudo nano /etc/modprobe.d/kvm.conf
add ""options kvm ignore_msrs=1"" (without quotes)
reboot"
1703506,2018-12-10 16:48:20 UTC,"QEMU 3.0 has limited TOPOEXT support.  You can try using `-cpu EPYC`, and the `threads` option is supposed to work."
1703506,2018-12-10 10:44:55 UTC,"Error I see in terminal:
AMD CPU doesn't support hyperthreading. Please configure -smp options properly."
1703506,2017-07-25 18:09:44 UTC,"I am looking at the diff between the host and guest CPUID, and we have a few candidates: CPUID[4] is all zeroes on the host, and the host has CPUID leaves up to 0x8000001f available, including CPUID[0x8000001d] (which contains cache topology information).  Probably we need to implement CPUID[0x8000001d], I will take a look at Linux code to find out if that's all we need."
1703506,2018-12-13 16:08:12 UTC,@ryzen27: do you have dmesg logs showing the MSRs being written by the guest? You may be hitting the bug described at https://bugzilla.redhat.com/show_bug.cgi?id=1592276
1703506,2017-07-20 02:48:30 UTC,"Attached Ubuntu 17.04 guest logs.
I wasn't able to run x86info as root. Only as regular user.
Error shown:
readEntry: Operation not permitted
error reading 1KB from 0x3fffc00"
1703506,2017-07-22 04:02:28 UTC,"I tried disabling the CmpLegacy bit directly on /target/i386/cpu.c deleting the If statement on ""case 0x80000001:"" or changing ""*ecx |= 1 << 1;"" to ""*ecx |= 0 << 1;""
But it didn't work, the VM still sees 8 physical cores.
I believe the HTT bit should be enabled by default
I tried changing it to ""*edx |= 1 << 28;"" in the If statement of ""case 1:"" just in case but it didn't matter.
Anything else that I could try to hard-code for testing?"
1703506,2017-07-18 18:52:30 UTC,"The warning doesn't make QEMU disable anything, it just warns the user that guests are likely to ignore the HT info on CPUID if CPU vendor is AMD."
1703506,2017-07-19 01:20:42 UTC,">Please confirm what's the QEMU command-line being used (especially the -smp and -cpu options), and check if the bug persists if using ""-cpu host"".
"
1703506,2018-01-30 16:19:39 UTC,just to be clear.. The kernel kvm patch is rebased on linux-next. If you are on older kernel then try this kernel patch. https://patchwork.kernel.org/patch/10031775/  plus qemu patch.
1703506,2017-07-19 10:32:00 UTC,"I can confirm the same behavior with a Ryzen 7 1700.
Host Arch Linux x64 Kernel 4.11.9, Guest Windows 10 Pro.
Running with -cpu host and -smp 8,sockets=1,cores=4,threads=2.
Attached the logs of the host and results of the output of msinfo32 and ""WMIC CPU Get NumberOfCores,NumberOfLogicalProcessors /Format:List"" in the guest.
Same results as scix, in my case 8 Core(s), 8 Logical Processors(s)."
1703506,2017-07-19 12:18:24 UTC,"Thank you for the info.  Having info on Linux guests' behavior would be nice to have, but it's possible to extract the raw CPUID data seen by the Windows guest using an equivalent Windows tool (suggestions of tools are welcome)."
1703506,2018-03-12 03:05:55 UTC,I tried the above patches on a TR 1900X and they do not help to enable SMT. I still receive the warning.
1703510,2018-03-31 01:10:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558016"
1703530,2018-04-24 16:39:59 UTC,I am also experiencing this issue.  I would class it as high priority.
1703530,2018-04-25 10:42:41 UTC,I can also confirm that this definitely seems to be an issue with 1.91-1 of terminator.
1703547,2017-07-11 23:52:18 UTC,"Hello agian,"
1703547,2017-08-04 11:19:01 UTC,"Case was reproduced, but the behaviour was different: neither master or backup wasn't restored, just one amphora with no role, which do nothing.
1) initial situation
mysql> select * from amphora;
+--------------------------------------+--------------------------------------+-----------+--------------------------------------+---------------+------------+------------+--------------------------------------+--------------------------------------+------------+---------------------+-----------+----------------+---------+---------------+

| id                                   | compute_id                           | status    | load_balancer_id                     | lb_network_ip | vrrp_ip    | ha_ip      | vrrp_port_id                         | ha_port_id                           | role       | cert_expiration     | cert_busy | vrrp_interface | vrrp_id | vrrp_priority |


+--------------------------------------+--------------------------------------+-----------+--------------------------------------+---------------+------------+------------+--------------------------------------+--------------------------------------+------------+---------------------+-----------+----------------+---------+---------------+

| 3af251d8-df87-4812-b907-fb69d2dae3db | 9a58b8df-a5de-49e9-aaad-e02d8ffb9648 | ALLOCATED | 2f88ac8e-ba2c-43ef-aa48-17fda3a200a9 | 192.168.0.4   | 10.20.0.12 | 10.20.0.13 | ddf9ab5c-66c0-4b28-bbaf-b27b47c94fba | c600c3c2-61f1-47e0-a1e7-da4296342990 | STANDALONE | 2019-08-04 10:57:43 |         0 | NULL           |       1 |          NULL |
| bc11b3f1-ee12-4cc2-9019-bd62dd15dd0a | b7b2be08-055f-4626-a257-5dd31b8d9030 | ALLOCATED | 2f88ac8e-ba2c-43ef-aa48-17fda3a200a9 | 192.168.0.10  | 10.20.0.22 | 10.20.0.13 | 8cfa09c3-0934-41ff-9ca0-2b9541cd8347 | c600c3c2-61f1-47e0-a1e7-da4296342990 | BACKUP     | 2019-08-04 10:54:32 |         0 | eth1           |       1 |            90 |


+--------------------------------------+--------------------------------------+-----------+--------------------------------------+---------------+------------+------------+--------------------------------------+--------------------------------------+------------+---------------------+-----------+----------------+---------+---------------+
2 rows in set (0.00 sec)"
1703547,2017-08-05 00:51:20 UTC,"The database information provided above is inconsistent.  The initial state output does not have a master amphora.  There should be one amphora with role ""MASTER"" and ""BACKUP""."
1703547,2017-08-05 01:13:51 UTC,"Ok, I can reproduce this."
1703547,2017-08-07 11:26:08 UTC,"Michael,"
1703547,2018-10-02 13:10:35 UTC,"Hello all,
What about this issue?, how can I fix this?, is there any workaround for this?
Thanks"
1703549,2018-03-14 14:48:12 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1703550,2018-03-14 14:48:18 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1703552,2018-01-02 17:50:29 UTC,This affects me exactly the same way as described by Thomas. This seems to match a problem in Debian Stretch that also leads to a timeout through the Xorg based session of xrdp....I mention this in case it helps to diagnose the issue. This is a fresh installation of Ubuntu 17.10.
1703560,2017-08-21 08:43:08 UTC,Patch containing functionality described in blueprint.
1703560,2017-08-28 15:03:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/498490"
1703560,2017-09-19 10:49:53 UTC,"For the record, the Windows SMB driver (which inherits the generic driver, adapted to work with Windows guests) already supports Active Directory integration."
1703560,2019-08-08 16:18:01 UTC,Jan my apologies for the lateness of the response we discussed this fix and want to ask if you still need this fix...also we want to invite you to the upstream weekly manila meeting  on IRC
1703560,2017-07-11 10:38:30 UTC,Added blueprint to this feature https://blueprints.launchpad.net/manila/+spec/active-directory-helper-for-generic-driver
1703570,2019-09-15 15:35:37 UTC,Migrated to https://github.com/widelands/widelands/issues/2079
1703581,2020-07-28 09:34:38 UTC,"Reviewed:  https://review.opendev.org/743028
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=48b2c835bba0346df6d06090a12d492196f9c19f
Submitter: Zuul
Branch:    stable/queens"
1703581,2020-07-25 11:10:48 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/743028"
1703581,2020-07-25 00:29:59 UTC,"Reviewed:  https://review.opendev.org/738890
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=a627a29e7225202475a8cdc927911b3cd80b487c
Submitter: Zuul
Branch:    stable/rocky"
1703581,2020-07-01 17:18:58 UTC,"Reviewed:  https://review.opendev.org/737324
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=a26b027b73669efb2a99530574051d284595b264
Submitter: Zuul
Branch:    stable/stein"
1703581,2020-07-01 16:45:16 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/738890"
1703581,2020-06-22 17:10:22 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/737324"
1703581,2020-06-08 23:43:00 UTC,"Reviewed:  https://review.opendev.org/732059
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=95d251e38b4b4526c862a428da93f568fe7a23ad
Submitter: Zuul
Branch:    stable/ussuri"
1703581,2020-06-08 23:43:15 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/734394"
1703581,2020-05-31 18:40:12 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/732059"
1703581,2020-05-28 23:29:00 UTC,"Reviewed:  https://review.opendev.org/498445
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=2c9fbc75059ac724cd845317473b7df4a8dcdc35
Submitter: Zuul
Branch:    master"
1703581,2019-10-28 18:25:36 UTC,Jan are you still working on this issue?
1703581,2017-09-21 15:17:11 UTC,"Well, the stacktrace is pretty useless, because it's wrapped into timeout exception:"
1703581,2017-09-20 10:37:51 UTC,Would it be possible to get a stacktrace of the error?
1703581,2017-08-28 12:24:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/498445"
1703581,2020-06-22 17:10:04 UTC,"Reviewed:  https://review.opendev.org/734394
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=b07c2484b6f0d5165d867651fbc123280e7b012d
Submitter: Zuul
Branch:    stable/train"
1703586,2017-07-11 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1703586,2017-07-11 12:26:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1703586,2017-07-11 16:46:18 UTC,"the linux-headers-4.9.36 package from //kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.36/ is broken, just see your own build log to confirm that."
1703594,2017-07-11 12:37:41 UTC,https://github.com/jameinel/juju/tree/2.2-presence-multi-1703594
1703594,2018-03-22 06:14:52 UTC,We will not be fixing this in 2.2 as there are no further point releases planned in this series.
1703611,2017-07-12 05:59:30 UTC,"@yatin (yatinkarel) I use magnum 2.5.1 but it is stable/ocata, so when i added name parameter, the cluster create command worked."
1703611,2017-07-11 14:16:41 UTC,"@ydemiral, your magnumclient version?
magnum --version"
1703615,2017-07-11 14:01:53 UTC,"Note also that ones the 'charm-revision-updater' gets this error, it fails the worker, which then bounces and restarts 1 second later, which fails in the same way."
1703629,2017-07-13 02:08:13 UTC,Which release is this tested against? Or is it master code (currently Pike)?
1703629,2017-07-17 13:54:56 UTC,"This is tested against Pike, but should be present in Newton and Ocata as well."
1703629,2017-07-17 13:56:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484381"
1703629,2018-01-26 00:44:35 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1703629,2018-08-08 23:18:15 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/590059"
1703629,2018-09-27 23:13:45 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/605881"
1703629,2018-10-01 21:59:29 UTC,"Reviewed:  https://review.openstack.org/590059
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9c1a58dd033fa8feeb1175956d57dc90aa55acd
Submitter: Zuul
Branch:    stable/pike"
1703629,2018-10-02 20:01:09 UTC,"Reviewed:  https://review.openstack.org/605881
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8b3b8e5657ffe0f12e1ccfbe6d978e62a2bfdc89
Submitter: Zuul
Branch:    stable/ocata"
1703629,2018-10-08 21:45:42 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1703629,2018-10-08 21:49:09 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1703629,2018-01-22 05:38:35 UTC,"Reviewed:  https://review.openstack.org/484381
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b930336854bffec1bb81b6d67079a4df59e0af19
Submitter: Zuul
Branch:    master"
1703637,2018-05-03 05:06:10 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.openstack.org/482621"
1703637,2017-07-11 16:22:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/482621"
1703638,2017-07-11 16:26:34 UTC,"$ snap info --verbose libreoffice core
name:      libreoffice
summary:   ""LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases""
publisher: canonical
contact:   http://www.libreoffice.org/get-help/community-support/
description: |
  LibreOffice is a powerful office suite – its clean interface and
  feature-rich tools help you unleash your creativity and enhance your
  productivity. LibreOffice includes several applications that make it the most
  powerful Free and Open Source office suite on the market: Writer (word
  processing), Calc (spreadsheets), Impress (presentations), Draw (vector
  graphics and flowcharts), Base (databases), and Math (formula editing).
commands:
  - libreoffice.base
  - libreoffice.calc
  - libreoffice.draw
  - libreoffice.impress
  - libreoffice
  - libreoffice.math
  - libreoffice.writer
notes:
  private:     false
  confinement: strict
  devmode:     false
  jailmode:    false
  trymode:     false
  enabled:     true
  broken:      false
tracking:      beta
installed:     5.3.4.2 (21) 368MB
refreshed:     2017-07-01 19:14:41 +0200 CEST
channels:
  stable:      5.3.4.2 (21) 368MB -
  candidate:   5.3.2.2 (19) 375MB -
  beta:        5.3.4.2 (21) 368MB -
  edge:        5.3.2.2 (19) 375MB -
---
name:      core
summary:   ""snapd runtime environment""
publisher: canonical
contact:   <email address hidden>
description: |
  The core runtime environment for snapd
type:          core
notes:
  private:     false
  confinement: strict
  devmode:     false
  jailmode:    false
  trymode:     false
  enabled:     true
  broken:      false
tracking:      candidate
installed:     16-2.26.8 (2329) 84MB
refreshed:     2017-07-05 14:46:19 +0200 CEST
channels:
  stable:      16-2      (2312) 83MB -
  candidate:   16-2.26.8 (2329) 84MB -
  beta:        16-2.26.8 (2329) 84MB -
  edge:        16-2.26.9 (2371) 84MB -"
1703638,2018-09-28 22:12:31 UTC,"The desktop interface includes <abstractions/fonts>, which allows reading /usr/share/fonts."
1703638,2018-09-26 12:02:47 UTC,"I think there’s a second issue: Now the LibreOffice snap does see the fonts installed in ~/.fonts, but it does not see system fonts installed in /usr/share/fonts (e.g., as a deb package). Should I open another bug for that issue?"
1703638,2017-10-25 23:22:02 UTC,Should be fixed in core 2.29 with the new desktop interface according to https://forum.snapcraft.io/t/desktop-allow-access-to-host-system-fonts/1796
1703638,2017-10-25 23:26:59 UTC,"Actually sorry that may have been a complete red herring, I'm talking about system fonts rather than fonts in ~/.fonts ..."
1703638,2017-10-25 23:25:38 UTC,"Tested 2.29~rc1 and `edge` (currently 2.28.5+git445.496e635 (3314)) and can't see the system fonts from LibreOffice, guessing the desktop interface needs to be connected? What command should I use to do that?"
1703638,2017-10-26 08:07:31 UTC,"I think ~/.fonts should also be exposed when using the new desktop interface. You will need a more recent libreoffice snap than the one currently in the candidate channel, as I recently added the desktop interface and didn't publish anything yet. I'm working on an update that I hope will go to the candidate channel later this week, so keep an eye out for it, and test again when the call for testing is out."
1703641,2017-07-11 20:13:47 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1703641,2017-07-27 13:55:51 UTC,I'm not entirely sure of the history here but it seems that openstacksdk may have replaced openstack-compute. The code for openstack-compute hasn't seen an update since 2011.
1703641,2017-07-27 13:57:30 UTC,"As a work-around, if you know you don't need python-openstack-compute, you can manually remove that package."
1703641,2020-03-27 10:53:28 UTC,python-openstack-compute has been removed from Ubuntu
1703643,2017-09-09 22:29:47 UTC,Mind verifying this is not a duplicate?
1703643,2017-09-15 03:37:43 UTC,"This is not a duplicate because the other one was released with 2.33, and this one still fails with 2.34."
1703643,2017-09-15 03:54:02 UTC,"Debugging on the container, there is not /root/build_heroku/parts/hello-node-snap/install/lib/node_modules/.staging/@heroku/, so chown /root/build_heroku/parts/hello-node-snap/install/lib/node_modules/.staging/@heroku/linewrap-6d8b1b65 of course fails."
1703649,2017-07-11 22:20:13 UTC,"This smells a lot like a systemdism. Wild guess time, is systemd-resolved in use on this system?"
1703649,2017-07-12 16:56:53 UTC,"Yes, systemd-resolved is running, and strace says that it does something when `traceroute -T google.com` is executed."
1703649,2017-07-12 17:23:04 UTC,Looks like culprit is libnss_resonve.so.
1703649,2017-07-12 17:27:22 UTC,"Added systemd because:
# apt-cache show libnss-resolve | fgrep Source
Source: systemd"
1703649,2017-08-09 13:23:08 UTC,How could I get comment from Systemd maintainers..?
1703652,2017-08-11 17:28:54 UTC,"This is not nearly enough information to debug.  --debug output would be helpful, as would comparing the output of 'openstack module list --all' between working and non-working installations."
1703652,2017-08-14 15:48:21 UTC,"Hi, here is the information you requested."
1703652,2017-07-12 08:29:00 UTC,Confirmed I see the same issue from Windows Desktop with same versions.
1703658,2021-02-25 15:13:17 UTC,At long last a branch appears from the mists: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1703658_gindexes / working/user/jboyer/lp1703658_gindexes
1703658,2021-02-25 15:14:12 UTC,I just started working on converting from GIST to GIN on a test database server.
1703661,2019-09-19 12:04:08 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1703661,2018-02-20 16:00:33 UTC,"For clarity, this would be good to have for both the web UI and the CLI"
1703661,2017-07-19 14:11:18 UTC,"Thank you, Andres.  I'll have to look into the API.  I had no idea it'd be possible from that direction.  Most excellent."
1703661,2017-07-11 18:42:41 UTC,"Hi Drew,"
1703670,2018-02-16 20:08:08 UTC,"Testing with the Ubuntu 4.13.0-32.35-generic 4.13.13 kernel on the 18.04 livecd, this doesn't seem to still be an issue."
1703673,2019-09-19 11:59:33 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1703673,2017-07-11 20:59:05 UTC,"also, the loading of items having thousands of course will take a long time. Maybe we shouldn't be showing the ""loading"" and the number of discoveries on page refresh."
1703673,2017-07-11 20:57:26 UTC,This seems like a UX bug really.
1703674,2018-02-16 20:05:34 UTC,"With 4.13.0-32.35-generic in 18.04 (via livecd), it seems that only this is needed:"
1703689,2017-07-11 21:58:19 UTC,"Hi Ben,"
1703689,2017-07-12 15:03:19 UTC,"Here you go, sure hope this helps.  Let me know what else I can do to help track this issue down.  If I do not use IPv6 there are no issues with the ifdown or deploying juju charms."
1703689,2017-07-17 16:50:22 UTC,"Hello,"
1703689,2017-07-17 19:51:20 UTC,"The interfaces do function correctly after manual intervention even with the errors but my problem, from what I understand about MAAS is the following"
1703689,2017-07-17 20:33:16 UTC,"On Mon, Jul 17, 2017 at 2:51 PM, Ben <email address hidden> wrote:"
1703689,2017-07-17 21:29:51 UTC,"ubuntu@server01:~$ sudo ifdown enp2s0f0.11; echo $?
Removed VLAN -:enp2s0f0.11:-
Cannot find device ""enp2s0f0.11""
0"
1703689,2017-09-16 04:17:40 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1703691,2017-07-11 23:11:55 UTC,"> 60000 I get 18 seconds and 10000 is 2 seconds.
"
1703691,2017-08-18 12:15:03 UTC,"What version of cryptsetup is this?
Also notice the official repository is on gitlab."
1703691,2017-08-18 12:23:47 UTC,"Obviously it is wrong repository, upstream is https://gitlab.com/cryptsetup/cryptsetup/ and mirror is https://github.com/mbroz/cryptsetup"
1703691,2017-08-18 12:27:14 UTC,"Whoops, sorry for pasting the wrong URL. As mentioned, the actual bug URL is here:"
1703691,2017-08-18 12:34:47 UTC,"Volume (master) key digest is there only to verify validity of the key.
The digest iteration count is not relevant for the security of LUKS in normal situation."
1703698,2017-08-07 02:07:28 UTC,"Hi Liping,"
1703698,2017-08-07 03:04:28 UTC,"Hi Hongbin,"
1703698,2017-08-06 10:54:40 UTC,"@hongbin,"
1703698,2017-08-07 17:49:58 UTC,"Thanks Liping,"
1703698,2017-07-16 01:36:48 UTC,"Hi Liping,"
1703698,2017-08-06 13:24:23 UTC,"@Hongbin,"
1703698,2017-07-15 02:30:50 UTC,"@hongbin,
BTW, same command can success when I run directly on host, it failed when I run in plugin container. Need to further debug."
1703698,2017-07-15 02:21:54 UTC,"@hongbin, I can reproduce this problem, I find the problem is when run ""iface.add_ip('fd34:d27c:33d3:0:f816:3eff:fe3f:8693', 64)"""
1703698,2017-07-13 14:13:52 UTC,"Hi Liping,"
1703698,2017-07-13 05:24:07 UTC,"@hongbin, I'm trying to re-produce this problem."
1703698,2017-07-15 07:07:04 UTC,"@hongbin,"
1703703,2017-08-28 09:57:33 UTC,This issue was fixed in the openstack/heat 7.0.6 release.
1703703,2017-08-17 08:44:35 UTC,"Reviewed:  https://review.openstack.org/483574
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=4e09419701090997c43fff847bd75b91b0c1ace9
Submitter: Jenkins
Branch:    stable/newton"
1703703,2017-08-03 01:00:44 UTC,This issue was fixed in the openstack/heat 8.0.3 release.
1703703,2017-07-28 18:57:13 UTC,This issue was fixed in the openstack/heat 9.0.0.0b3 development milestone.
1703703,2017-07-27 11:27:32 UTC,"Reviewed:  https://review.openstack.org/483571
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=3fb8722012a991855fc760ba450ed74acd8b43d2
Submitter: Jenkins
Branch:    stable/ocata"
1703703,2017-07-20 08:31:55 UTC,"Reviewed:  https://review.openstack.org/485364
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=65630d4e8bbff2f3ae5c659f8e9396ec7a6f6ae9
Submitter: Jenkins
Branch:    master"
1703703,2017-07-18 11:14:11 UTC,"Reviewed:  https://review.openstack.org/483512
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=5ce238fb17e38702ceef85a3706e9d2236c43e0e
Submitter: Jenkins
Branch:    master"
1703703,2017-07-13 21:44:58 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/483574"
1703703,2017-07-13 21:39:47 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/483571"
1703703,2017-07-13 19:09:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/483512"
1703703,2017-07-12 20:50:38 UTC,"It looks like the problem was introduced by https://review.openstack.org/#/c/278231/. We take the 'convergence' path in the case that the Resource object cannot be found in the Stack's dependency graph. The dependency graph is constructed from the Resource objects found in Stack.resources. However, the Resource objects we're listing are loaded from database objects independently of the Stack, and thus *never* appear in the dependencies."
1703703,2017-07-12 15:00:12 UTC,"Note that in theory we're not supposed to hit this path except in convergence, so although it would be simple to fix I'm not 100% sure that we'd be getting at the root cause."
1703703,2017-07-19 21:52:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/485364"
1703704,2017-09-21 01:50:34 UTC,"Patch Added here
https://review.openstack.org/#/c/505890/"
1703704,2017-11-08 12:06:13 UTC,"Updating status to ""Fix Committed"" as the patch referenced in comment #1 merged on master on Sept 27."
1703710,2018-10-26 03:51:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703711,2018-12-10 01:24:03 UTC,"^ I did find a ""dkms remove dahdi/2.10.2~dfsg-1ubuntu1"" to be necessary before building/installing. I think dkms thought it had already built the modules + didn't pick up my config changes."
1703711,2021-01-15 00:34:50 UTC,"The attachment ""dahdi.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1703711,2021-01-14 21:39:29 UTC,"BUILT_MODULE_NAME[32]=""wcte43x""
BUILT_MODULE_LOCATION[32]=""drivers/dahdi/""
DEST_MODULE_LOCATION[32]=""/kernel/drivers/telephony/dahdi""
are needed for wcte43x...
I have attached a patch with all the missing modules based on what dahdi builds by default (using its build_tools/dkms-helper generate_conf to get the missing ones)."
1703711,2018-08-18 02:31:50 UTC,@tufelkinder You need to add those lines in dkms.conf in /usr/src/dahdi-2.10.2~dfsg-1ubuntu2/dkms.conf and then rebuild using
1703711,2018-08-08 23:04:28 UTC,"Same problem with Digium TE121 cards which loaded the wcte12xp driver in the previous version, 1:2.10.2~dfsg-1ubuntu1 - reverted back to previous version until fix."
1703711,2017-08-05 15:40:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703711,2017-08-05 09:35:30 UTC,Same problem with Digium TE435 cards. I had to add build instructions for wcte43x and oct612x in dkms.conf to get it working.
1703711,2018-08-17 20:40:26 UTC,"""So Digium TE13x cards do not work unless the following lines are added to dkms.conf & drivers are rebuilt -"""
1703712,2019-09-19 14:48:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1703731,2017-07-12 04:00:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/482792"
1703731,2017-07-15 23:51:28 UTC,"Change abandoned by Amrith Kumar (<email address hidden>) on branch: master
Review: https://review.openstack.org/482792
Reason: in favor of https://review.openstack.org/#/c/444588/"
1703740,2017-08-08 21:39:11 UTC,"Anecdotally, seems to be correlated with gate infra load. It's been a lot worse recently as we close in on deadlines. I vaguely recall similar issues in past releases too."
1703740,2017-08-08 22:14:56 UTC,Also seems correlated with an increased incidence of other connectivity-related failures in tempest tests. E.g. Request to service '__engine' timed out
1703742,2017-07-12 14:54:07 UTC,Thank you for reporting this. I'm currently evaluating this with some benchmarking experiments and my current observation concurs with the observations.  I believe enabled=madvise is probably the best way forward but I still have several more test scenarios to complete to ensure we don't hit any unexpected performance regresions.
1703742,2018-03-19 18:13:53 UTC,I've been exercising the -proposed kernel all day on amd64 using stress-ng memory tests without any observed regressions.
1703742,2018-03-19 10:56:13 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1703742,2017-10-30 19:44:58 UTC,This bug was fixed in the package linux-gke - 4.4.0-1033.33
1703742,2017-08-10 05:56:17 UTC,This bug was fixed in the package linux - 4.11.0-13.19
1703742,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1703742,2017-07-13 14:00:09 UTC,Note: Current plan is to see how this works on Artful and SRU these once we are happy with the results in Artful.
1703742,2017-07-12 17:52:03 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-July/085565.html
1703742,2017-07-12 17:39:42 UTC,Data: http://kernel.ubuntu.com/~cking/transparent-huge-pages/transparent-huge-pages.ods
1703742,2017-07-12 05:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1703742,2017-07-26 15:57:54 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1703752,2017-07-12 18:18:00 UTC,"I will take a look if I can find the upstream fix for this -- I have done some cursory updating to the zabbix package for PHP7 compatibility, from upstream backports."
1703777,2020-10-22 17:48:40 UTC,two attempts to fix this in different ways:
1703777,2020-10-18 01:31:01 UTC,"https://github.com/mixxxdj/mixxx/pull/3184
(though not bound to 'fullscreen' yet)"
1703777,2017-07-12 10:59:03 UTC,"https://github.com/mixxxdj/mixxx/pull/927
Is the pending pull request, waiting to become ready. If you like help here, and appt this branch it would be great."
1703779,2019-01-07 11:13:49 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/482887
Reason: Marking this review as abandoned due to lack of activity in the past 6 months."
1703779,2017-07-12 11:32:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/#/c/482887/"
1703780,2017-07-14 06:13:40 UTC,"Above fix has still an issue with option bs=32M and still getting the error: ""dd: bs: illegal numeric value"""
1703780,2017-08-19 18:30:14 UTC,"The same issue is for Ubuntu, step 5, and it's not yet fixed neither for Mac OS nor for Ubuntu.
BTW, on Debian the ‘M’ should be uppercase."
1703780,2017-08-21 08:07:54 UTC,"Thanks for the update, there is indeed a discrepancy in unit parsing between Linux VS Mac, after some testing, this has been addressed in https://github.com/canonical-websites/developer.ubuntu.com/pull/311 and will be deployed later today"
1703780,2017-07-13 08:00:07 UTC,"Thank you for the report, the fix is tracked at https://github.com/canonical-websites/developer.ubuntu.com/pull/304"
1703786,2017-08-15 22:49:19 UTC,Tested in master web client and appears to be broken as indicated.  Marking issue confirmed.  Will need to test further to follow up on problem.
1703786,2018-11-26 20:27:40 UTC,Removing milestone due to lack of pull request.
1703789,2017-09-23 02:34:47 UTC,"This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New"
1703799,2019-10-15 20:43:39 UTC,"The firmware currently included in bionic-updates is from 2019-02-15 (primarily to support booting the CM3+), and in eoan is 2019-08-19; both of these support .dtbo files."
1703801,2017-07-13 08:06:17 UTC,"Yes, the Window geometry hints were turned on (it is the default) and, exactly as you write, turning off the option helped. Thanks."
1703801,2017-07-12 21:03:55 UTC,"Do you have geometry hints turned on? I can see this behaviour if I startup with hints on, and do the F11 shuffle. Curiously if I then resize the window to 80x24, and repeat the F11 shuffle, the problem goes away."
1703802,2019-03-26 18:50:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703802,2019-03-26 18:58:26 UTC,"I'm seeing this in bionic right now. I don't know how to add bionic to the tracker, though, even if xenial is fixed."
1703802,2017-08-03 16:33:25 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1067.75
1703807,2017-07-12 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1703819,2017-07-13 09:57:59 UTC,"Hi CTAC,
thanks for your report."
1703821,2020-02-17 08:19:15 UTC,"This is a post 2.13 fix upstream.
As mentioned by Christian it is in the backport branches, the respective merge for 2.13 is:
$ git tag --contains 28c4dcccc3a339dea8120eb59fea314bc0026b50
v2.13.3
Thereby this is fixed in E&F."
1703821,2020-02-16 13:54:05 UTC,"For the records: Upstream commit a57f01d86bdb01647966f3eeff7a1cc3fc6abd76 (from 2019-02-10) added rules to allow this (with an additional type=stream restriction, which matches the log mentioned in this bugreport), and was also backported to the maintenance branches."
1703821,2020-02-16 04:17:41 UTC,[Expired for apparmor (Ubuntu) because there has been no activity for 60 days.]
1703821,2020-02-16 04:17:39 UTC,[Expired for AppArmor because there has been no activity for 60 days.]
1703821,2019-12-17 19:32:24 UTC,"@Matyáš, this configuration seems like something you added:"
1703821,2017-07-12 19:55:11 UTC,"I applied the fix and it looks like it's all working now. I wan't aware of the anonymous sockets, so I was trying wrong things."
1703821,2017-07-12 19:17:10 UTC,"Oh, I always forget that unix has _anonymous_ sockets too. Silly complicated things. Thanks John."
1703821,2017-07-12 19:14:42 UTC,"This is caused by an anonymous socket communication channel between dovecot and anvil. If this problem is not happening in 16.04 (unless you are using the release kernel) then it will be because o a change to dovecot, newer versions of apparmor have been SRUed back to 16.04"
1703821,2017-07-12 18:51:37 UTC,"It is suprising for me too, as I don't know about this problem on 16.04 LTS and I could not reproduce it. It was probably introduced in 17.04 or around that."
1703821,2017-07-12 18:51:09 UTC,Its an anonymous socket. The best you can do is
1703821,2017-07-12 18:26:23 UTC,"I'm surprised about the ""addr=none peer_addr=none"" -- any idea what's going on here?"
1703821,2019-12-17 19:30:47 UTC,Marking the dovecot task as Invalid since it doesn't ship the profiles.
1703822,2017-07-13 09:54:30 UTC,"Hi CTAC,
this package is kind of deprecated and not changed at all since Xenial.
I have taken a task to check in detail if this package shall get some bigger attention or if we actually want to remove it (better than being out in a semi-broken way)."
1703827,2017-07-14 20:20:02 UTC,I wasn't able to recreate this issue e.g. the original code works fine for me.
1703827,2017-07-14 20:34:08 UTC,Well some of them in errors are due to bad translations.  From it.po:
1703827,2017-07-14 20:38:59 UTC,"gd.po:msgid ""You have %(num)s packages (%(percent).1f%%) supported until %(time)s""
gd.po-msgstr ""Tha agad % (num)s pacaidean (%(percent).1f%%) le taic gu %(time)s"""
1703827,2017-08-18 15:56:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703831,2019-05-01 06:55:11 UTC,"I had not been able to try for the few latest versions using Fedora 28-30 with this error:
$ openastro
Traceback (most recent call last):
  File ""/usr/bin/openastro"", line 37, in <module>
    from gi import require_version
ImportError: cannot import name require_version"
1703831,2017-12-25 11:02:36 UTC,"I sorry I didn't notice you are talking about the new release. I'm going to
test it and report later!"
1703831,2017-12-24 17:28:08 UTC,Are you still experiencing this problem?
1703831,2017-12-24 22:50:28 UTC,"Yes in Fedora 27 too.
North Nodes and some other special points are also missing in PNG export."
1703831,2017-12-25 07:52:26 UTC,What version of rsvg-convert do you have installled?
1703832,2017-07-13 16:11:37 UTC,"Hi all,"
1703832,2017-07-17 15:39:50 UTC,"Suppose that the network whose display name was changed was already part of at least one logical router. therefore, the network appears in ""Connected Networks"" list of at least one logical router."
1703838,2017-07-12 15:51:14 UTC,More system information:
1703838,2017-07-13 11:18:12 UTC,"I can induce a connection drop by changing the wireless channel on my router - this also produces a similar result (no auto reconnect) - it shows like it's trying for a minute or 2, and than shows the up/down arrows. Selecting the network manually connects immediately."
1703866,2017-07-12 19:09:06 UTC,I eventually succeeded to finish upgrading the system. The only thing I had to manually fix was to set TERM=xterm because the installer was not able to pop-up the purple selection screen with my self-compiled st terminal.
1703866,2017-07-12 19:41:26 UTC,"Damien, interesting; did st provide terminfo pieces to install too?"
1703866,2017-07-12 19:53:10 UTC,"Of course and I've installed them on my main machine but that was an upgrade over SSH and the term info were not on that remote host. All in all, I think it was more my fault than anything else..."
1703866,2017-07-22 00:38:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703895,2019-09-19 14:48:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1703898,2017-10-16 07:58:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1703908,2017-08-24 09:22:40 UTC,"I would like to add that the ""internally not connected"" pads should be able to be actually connected to anything in PCBNew."
1703908,2019-10-15 17:07:02 UTC,"Just as an example/typical application, see page 4 of"
1703940,2017-07-13 06:51:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/483221"
1703940,2017-07-13 08:35:36 UTC,"Change abandoned by wangzhh (<email address hidden>) on branch: master
Review: https://review.openstack.org/483221"
1703943,2017-07-12 17:46:55 UTC,"As a workaround, configure a wildcard constraint (`""*""`) if only one constraint is needed."
1703947,2017-07-26 09:16:27 UTC,"Well.. it's quite annoying. Any workaround, command line or file to edit?
Need some details?
Print as root is not a solution for us.
Thanks"
1703954,2018-02-10 05:47:05 UTC,This issue was fixed in the openstack/cinder 11.1.0 release.
1703954,2018-01-30 01:23:50 UTC,This issue was fixed in the openstack/cinder 12.0.0.0b3 development milestone.
1703954,2018-01-16 19:55:19 UTC,"Reviewed:  https://review.openstack.org/529045
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=cfe0cf93d7de384f81597214336c8d0d92dca233
Submitter: Zuul
Branch:    stable/pike"
1703954,2018-01-12 18:56:24 UTC,"Here is an empty, encrypted volume prior to attachment:"
1703954,2017-12-19 12:11:56 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/529045"
1703954,2017-12-19 01:08:17 UTC,"Reviewed:  https://review.openstack.org/528694
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=3b01eb78ce1c1ce388521f8122b3d6b8f2686fda
Submitter: Zuul
Branch:    master"
1703954,2018-01-12 18:52:58 UTC,I can 100% confirm this is still not working.  I am running fully patched CentOS 7.4 with all of the very latest available Pike RPMs from the CentOS Cloud Pike repos.  I can reproduce this again and again.
1703954,2017-09-26 19:09:09 UTC,"The code in os-brick has a workaround for the unexpected flow that Nova seems to have, so it will work, but the optimal solution would be to fix this flow in Nova."
1703954,2017-07-27 14:11:53 UTC,"The patch was recently merged, is this still an actionable Nova bug that is going to require a Nova patch?"
1703954,2017-07-13 21:20:57 UTC,"Reviewed:  https://review.openstack.org/483068
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=66520dcf6c1815f555eed4a241edf475d6ed0fee
Submitter: Jenkins
Branch:    master"
1703954,2017-07-13 16:00:12 UTC,"Reviewed:  https://review.openstack.org/483069
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=f341e9c3ed86d15b599c4547e783d1f9da011cdb
Submitter: Jenkins
Branch:    master"
1703954,2017-07-12 18:56:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/483069"
1703954,2017-07-12 18:56:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/483068"
1703954,2017-12-18 11:40:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528694"
1703978,2020-07-03 05:03:00 UTC,DistroRelease: Kali 2017.1
1703982,2019-06-15 20:29:40 UTC,"Fixed my issue by moving to a different printer/multifunction device. From now on I will not be able to make any test about this issue. Please consider closing the issue and simply marking the HP6950 as poorly supported by HPLIP, so that people shopping for printers that work well with ubuntu can make an informed choice."
1703982,2018-09-04 12:15:03 UTC,Also present in bionic.
1703982,2017-11-04 14:44:42 UTC,As expected the issue is also present in ubuntu artful.
1703982,2017-10-02 09:09:36 UTC,Looks like there is no activity from upstream. Please consider marking this all-in-one as only partially supported downstream since scanner does not work properly. There are a lot of HP printers that work fine and guiding the user to them seems proper.
1703982,2017-08-18 11:57:11 UTC,"Made a quick test, forcing the install of libsane-hpaio_3.17.7+repack0-3_amd64.deb from artful.  This makes the package manager complain a little about broken dependencies, but there does not seem to be any fundamental breakage as sane still works."
1703982,2017-07-17 06:28:47 UTC,@ Florio
1703982,2017-07-14 15:17:14 UTC,"Xsane doesn't seem to support Flatbed setting either, I'm thinking there is
a bug in it, and uninstalling and reinstalling it won't work either because
the bug is in the software at the source.
I think someone is hacking into the software, planting bugs so that Linux
won't work, we get disgusted and go back to Microsoft?
Not me, NEVER, Linux needs to fix it at their end, then put out a correct
disc, then tell us the corrected software is available, it's the only way,
so Linux software won't get infected again."
1703982,2017-07-12 21:13:20 UTC,"As a matter of fact, with hp-scan, the matter is worse:"
1703982,2017-07-12 21:00:55 UTC,"The same happens also with hp-scan, that says
""Read 1.0 MB from scanner.
error: Did not read enough data from scanner (I/O Error?)"""
1703982,2017-07-12 20:54:23 UTC,Activating the JPEG compression (which should not be available in lineart as it makes no sense for this mode) seems to relax the issue
1703982,2017-08-18 11:39:53 UTC,Can someone please indicate:
1703993,2017-07-13 21:41:20 UTC,"Reading the error carefully it looks like the problem is not classifier itself but one of it's dependencies, ""stemmer"" which seems to be provided by the package ruby-fast-stemmer."
1704002,2017-07-12 21:39:48 UTC,Added to Trello: https://trello.com/c/YZP4AmZj/194-bug1704002-missing-icon-for-mono-speakers
1704002,2017-07-13 14:50:45 UTC,This bug was fixed in the package gnome-control-center - 1:3.24.2-0ubuntu5
1704002,2017-07-13 15:06:38 UTC,Please report this to GNOME too.
1704002,2017-07-13 15:52:17 UTC,Done
1704011,2017-12-01 16:10:39 UTC,Just checking back in. I've been running a production cluster with this patch applied since I submitted this ticket without any issue.
1704011,2017-07-13 00:23:21 UTC,"The attachment ""Commit: cca1616b1a1aef9fe049e326a8936d006963b21b | Fix issue where 'alter ignore' isn't supported in MySQL anymore."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1704012,2017-07-12 23:56:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/483133"
1704012,2017-07-14 15:34:12 UTC,"Reviewed:  https://review.openstack.org/483133
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9eea8869eabf12d3e1a078bd48fa96f0badb1ed
Submitter: Jenkins
Branch:    master"
1704027,2017-08-08 14:38:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704044,2017-07-13 03:46:04 UTC,submit a patch for this issue: https://review.openstack.org/483165
1704052,2017-07-13 05:52:42 UTC,Here's a related crash file from my system.
1704052,2017-07-14 11:23:51 UTC,"I've found that even if I keep Tasque open and use the Workaround as mentioned to Toggle the window, Tasque seems to automatically crash just after midnight with what seems to be the same error."
1704074,2017-08-05 09:43:47 UTC,"Change abandoned by Debo Zhang (<email address hidden>) on branch: master
Review: https://review.openstack.org/483218"
1704074,2017-10-20 14:42:20 UTC,"I can reproduce this in the current horizon:
1. Start devstack with the swift options enabled, i.e. add this to your local.conf:
   enable_service s-proxy s-object s-container s-account
2. After devstack starts, login as the admin and navigate to Identity > Users
3. The user swiftusertest4, which is created by devstack, has a Domain Name of '-' in the user list table.
4. Click on the 'swiftusertest4' name to view its detail, which shows that its domain name is 'swift_test'"
1704083,2019-04-03 17:19:02 UTC,"Thanks for the update Sergey, I will test this soon."
1704083,2019-04-03 16:43:40 UTC,Still buggy with new algorithm in version 5.1.0-114-ge7900e9. Again any instance of same pin gets its own net name and only first net loaded from netlist.
1704083,2017-07-13 11:53:32 UTC,Hi Maciej.
1704083,2017-07-13 08:18:26 UTC,"Sorry, missed version info:"
1704083,2017-07-13 09:53:37 UTC,"Hi Sergey,"
1704088,2017-07-13 21:25:13 UTC,"Hello Steve,"
1704096,2019-06-03 16:09:54 UTC,This has been fixed for a while now.
1704103,2017-07-13 11:38:50 UTC,"We agreed that we would treat these parts as dependencies, just as new stage-packages don't mark the build dirty either and we would focus on `source-type: local` first."
1704106,2019-03-28 20:29:50 UTC,This is fixed in cinder 11.2.1 point release for pike so we might as well just pick this up in a new round of point releases. We'll do that via this bug: https://bugs.launchpad.net/cloud-archive/+bug/1822192
1704106,2019-04-01 16:45:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649106"
1704106,2019-03-28 20:31:31 UTC,This is currently not in the latest point release for ocata (10.0.8) so we'll have to cherry-pick it for now.
1704106,2019-03-28 20:57:20 UTC,New cinder package versions have been uploaded to ocata-staging and pike-staging.
1704106,2019-03-29 13:04:50 UTC,"Hello Arne, or anyone else affected,"
1704106,2019-03-29 13:31:12 UTC,This is also ready for testing in pike-proposed in the cinder 2:11.2.1-0ubuntu1~cloud0 package version.
1704106,2019-04-01 16:57:01 UTC,pike patch included in https://bugs.launchpad.net/bugs/1822192
1704106,2019-03-25 22:21:26 UTC,"Reviewed:  https://review.openstack.org/644232
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b1a0d62f357e431a6b74d38440a8392de972b824
Submitter: Zuul
Branch:    stable/ocata"
1704106,2019-04-08 13:36:47 UTC,The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1704106,2019-04-08 13:36:50 UTC,"This bug was fixed in the package cinder - 2:10.0.8-0ubuntu1~cloud1
---------------"
1704106,2019-05-13 16:05:18 UTC,"Reviewed:  https://review.opendev.org/649106
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=616ba364296687bfeb8d9bf35bb0e7628d573e5b
Submitter: Zuul
Branch:    master"
1704106,2019-06-04 09:25:48 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/662986"
1704106,2019-06-18 21:57:31 UTC,"Reviewed:  https://review.opendev.org/662986
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=2b7ffcaee81045af5893327f0cf2e603d8fd8f5f
Submitter: Zuul
Branch:    stable/19.04"
1704106,2020-11-04 15:00:23 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/761422"
1704106,2019-03-28 20:22:09 UTC,Switching to triaged/high for the Ubuntu cloud archive ocata and pike releases as this patch is not yet committed there.
1704106,2019-04-01 21:26:53 UTC,ocata-proposed tested and verified
1704106,2019-03-18 15:06:46 UTC,stable/ocata: https://review.openstack.org/#/c/644232/
1704106,2019-02-28 14:31:06 UTC,This issue was fixed in the openstack/cinder 11.2.0 release.
1704106,2018-10-17 05:45:50 UTC,"Reviewed:  https://review.openstack.org/607192
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=1dca272d8f47bc180cc481e6c6a835eda0bb06a8
Submitter: Zuul
Branch:    stable/pike"
1704106,2017-07-18 07:15:17 UTC,"As a simple mitigation, how about adding two config options to
- enable/disable provisioning stats gathering
- control the frequency of its periodic task ?"
1704106,2017-08-02 16:46:37 UTC,"This is probably happening to me as well. No matter how many osapi_volume_workers we have, the periodic tasks takes down cinder-volume service (it's running but not handling any RPC calls and shows as dead - XXX)."
1704106,2017-09-19 03:13:39 UTC,Refreshing this issue. It is still happening in latest stable/newton.
1704106,2017-10-17 14:04:01 UTC,"It happens with Ocata Cinder 10.0.6, too."
1704106,2018-02-06 14:25:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541285"
1704106,2018-03-11 23:03:31 UTC,"Reviewed:  https://review.openstack.org/541285
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=f33baccc3544cbda6cd5908328a56096046657ed
Submitter: Zuul
Branch:    master"
1704106,2018-03-23 13:28:59 UTC,"This is affecting an OpenStack Ansible Pike deployment, running 16.0.8"
1704106,2018-02-20 14:48:28 UTC,Running Ocata Cinder 10.0.6 too and having the same problem.
1704106,2018-04-02 13:48:15 UTC,"The biggest issue was when we were incorrectly doing calculations for the real used size instead of the provisioned size, but that was also fixed and backported to Pike: https://review.openstack.org/#/c/501316/"
1704106,2018-04-16 21:00:53 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561721"
1704106,2018-04-18 16:34:30 UTC,"Reviewed:  https://review.openstack.org/561721
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=21821c16580377c4e6443d0b440f41cb7de0ca8d
Submitter: Zuul
Branch:    stable/queens"
1704106,2018-04-19 14:00:08 UTC,This issue was fixed in the openstack/cinder 13.0.0.0b1 development milestone.
1704106,2018-06-04 12:31:00 UTC,This issue was fixed in the openstack/cinder 12.0.2 release.
1704106,2018-10-02 13:56:38 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/607192"
1704106,2018-03-27 08:33:01 UTC,This also affects the Pike version of Cinder
1704110,2019-05-22 10:31:18 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates.
1704110,2019-07-22 04:17:23 UTC,[Expired for totem (Ubuntu) because there has been no activity for 60 days.]
1704113,2017-07-13 11:50:12 UTC,"Hi,"
1704113,2017-07-13 16:10:06 UTC,"Change abandoned by Brad P. Crochet (<email address hidden>) on branch: master
Review: https://review.openstack.org/483320"
1704116,2017-07-14 01:24:44 UTC,I hearby affirm the OpenSRF/Evergreen Developer's Certificate of Origin v1.1 .
1704116,2017-07-31 14:42:00 UTC,"Pushed to master, rel_2_5, and rel_2_4. Thanks, Graham!"
1704116,2017-07-13 15:26:39 UTC,The patch in Git form (and tested by me) is available in the working/OpenSRF repository at the tip of the user/gmcharlt/lp1704116_parallel_build branch:
1704116,2017-07-13 15:05:11 UTC,"Thanks for this patch (and the others). We'll try them out, and I'm glad to see somebody working on expanding the list of supported platforms."
1704116,2017-07-13 15:16:15 UTC,"Pedant here: it's not ""accepting"" the DCO; it's ""affirming"" the DCO (stating that the contribution is your own work or that you have the right to submit the work)."
1704121,2017-08-31 19:13:30 UTC,"Today the VPNaaS API is marked as ""UNMAINTAINED"" [1].
That said this one seems like a wishlist item to me; something we can revisit."
1704128,2017-07-13 13:22:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/483388"
1704128,2018-06-06 18:33:20 UTC,"Change abandoned by Douglas Mendizábal (<email address hidden>) on branch: master
Review: https://review.openstack.org/483388
Reason: Abandoning patch due to lack of activity for months.  Feel free to re-submit if needed."
1704137,2021-01-18 10:56:48 UTC,Proposed fix https://review.opendev.org/c/openstack/neutron/+/770824
1704141,2018-06-06 18:33:34 UTC,"Change abandoned by Douglas Mendizábal (<email address hidden>) on branch: master
Review: https://review.openstack.org/483401
Reason: Abandoning patch due to lack of activity for months.  Feel free to re-submit if needed."
1704141,2017-07-21 13:02:16 UTC,See Patch: https://review.openstack.org/#/c/483400/
1704141,2018-06-06 18:33:29 UTC,"Change abandoned by Douglas Mendizábal (<email address hidden>) on branch: master
Review: https://review.openstack.org/483400
Reason: Abandoning patch due to lack of activity for months.  Feel free to re-submit if needed."
1704157,2017-11-20 18:12:36 UTC,Please provide diagnostic snapshot.
1704159,2018-03-06 13:00:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704159,2018-03-06 13:02:17 UTC,This bug caused me several hours of headscratching and work. :-(
1704159,2020-07-04 15:22:24 UTC,A fix has recently been committed upstream: https://salsa.debian.org/debian/ddclient/-/commit/82d99d1dfb0fb002a15e081fdc7ccf8f96215dc6
1704174,2017-07-13 20:24:20 UTC,"The attachment ""sbin.dhclient-wicd.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1704174,2017-09-16 20:23:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704176,2019-09-19 14:48:52 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1704178,2017-10-12 19:48:25 UTC,"I played around with the environment variable ""GTK_OVERLAY_SCROLLING=0"" which should disable automatically hiding scrollbars. Unfortunately it does not change the amount of scape allocated for the scrollbar, i.e. the size of the UI element does not change."
1704178,2017-07-13 16:41:50 UTC,"Have you seen the options for changing the size of the color fields?
Click on the tiny triangle at the left of the palette, then you will be able to set a height, and a width per color."
1704178,2017-10-12 19:40:20 UTC,This should be fixed for Inkscape 0.93 as it's a highly visible (and heavily used) part of the UI.
1704178,2017-07-13 16:42:05 UTC,at the right. Sorry!!!
1704178,2017-07-13 20:55:33 UTC,"Making the size of the color strip huge makes the color strip usable again.
Though you'll notice that the scrollbar of the color strip lies on top of the color strip."
1704178,2017-10-12 19:48:43 UTC,scape -> space
1704178,2017-07-13 19:54:38 UTC,Still seeing this on bzr rev 15740.
1704178,2017-07-17 01:35:54 UTC,I don't know what Fedora packagers decided for stable Inkscape 0.92.1. The screenshot attached in comment 1 however shows unstable trunk (Inkscape 0.92+devel) (e.g. the rotation widget at the far right end of the status bar belongs to a new feature that only exists in unstable trunk) - in contrast to the stable version mentioned by the reporter in the bug description.
1704178,2017-07-17 00:14:36 UTC,"If the Fedora build is problematic, maybe the flatpak version will be better?"
1704179,2017-07-13 18:53:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/483506"
1704179,2019-08-21 16:14:16 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/483506
Reason: This was fixed with https://review.opendev.org/#/c/520024/."
1704186,2020-10-07 18:54:53 UTC,"You can select the behavior of ^C when specifying ""-chardev stdio,signal=[on|off]"". See also https://www.qemu.org/docs/master/system/invocation.html#hxtool-6"
1704190,2017-11-15 21:26:15 UTC,The 'skip' feature is still there in 1.03-24. This is how you protect a shebang of a python script:
1704192,2017-10-16 12:30:10 UTC,"Related fix proposed to branch: feature/s3api
Review: https://review.openstack.org/512277"
1704192,2017-10-18 18:55:04 UTC,"Reviewed:  https://review.openstack.org/512277
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=f94d6567a7e2e8b3ca1168b4a41c42c1ee371af5
Submitter: Zuul
Branch:    feature/s3api"
1704192,2017-10-16 16:50:05 UTC,"Change abandoned by Alistair Coles (<email address hidden>) on branch: feature/s3api
Review: https://review.openstack.org/512283
Reason: I was just trying to get sensible topic"
1704192,2017-10-16 12:42:14 UTC,"Related fix proposed to branch: feature/s3api
Review: https://review.openstack.org/512283"
1704192,2017-09-30 16:12:41 UTC,"Related fix proposed to branch: feature/deep
Review: https://review.openstack.org/508700"
1704192,2017-09-27 03:54:39 UTC,"Reviewed:  https://review.openstack.org/506410
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=cc17c99e73e9ddb1768f2979074c3ec043e0a3b4
Submitter: Jenkins
Branch:    master"
1704192,2017-09-21 22:31:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/506410"
1704192,2017-09-30 19:16:44 UTC,"Reviewed:  https://review.openstack.org/508700
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=0c75ddf6fe5a4843fe60836b402f27cb1b83d8c5
Submitter: Zuul
Branch:    feature/deep"
1704193,2017-07-16 19:20:03 UTC,"This is totally weird: Finally I gave in and updated both, evince and mir. Turns out, neither show up as a result of ‘dpkg -l <pkg>’. What am I missing here?"
1704199,2017-12-06 08:24:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704199,2017-07-14 00:28:10 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1704200,2017-07-14 07:33:41 UTC,"Originally, the reason for this is that delete account was something only an reseller-admin would do and that end users cannot/should not do -- and the api docs were aimed at end users. However, given that a) we documented create (aka PUT) account and b) reseller-admins need an API reference, I think the original thinking is invalid, so delete account should be documented."
1704201,2018-05-22 19:43:43 UTC,At this point I would prefer we don't mess with the metadata method of setting mode any longer and instead move to using a field in the attachment-request.  The mode setting described here is less than ideal for a number of reasons.  Between the spec on the Nova side proposed by Matt and the WIP for the mode setting in Attach this should be resolved.
1704201,2018-05-15 16:42:22 UTC,"From an outside perspective (to cinder), it seems weird that this is stored as metadata on the volume, I'm not sure why this wouldn't just be an attribute directly on the volumes resource in the data model."
1704201,2018-05-15 16:41:19 UTC,"This appears to be the problem, if you're not an admin the value doesn't get set:"
1704201,2018-05-15 16:24:41 UTC,This would likely be resolved by this nova spec: https://review.openstack.org/#/c/552078/
1704201,2018-05-15 16:29:54 UTC,What version of cinder was this reported against?
1704201,2018-05-15 16:38:55 UTC,"> I also notice that the only time the read only tag is followed is when it is set in the cinder table: volume_admin_metadata. If it is set in the volume_metadata table it is ignored.
"
1704210,2017-07-14 16:11:58 UTC,"ubuntu@autopkgtest:/tmp/autopkgtest.BeZID5/build.9bb/real-tree$ sudo python3 tests/integration.py TestNetworkManager.test_eth_dhcp6_off
test_eth_dhcp6_off (__main__.TestNetworkManager) ... FAIL"
1704210,2017-07-14 16:12:11 UTC,"ubuntu@autopkgtest:~$ sysctl -a | grep veth | grep accept
sysctl: permission denied on key 'fs.protected_hardlinks'
sysctl: permission denied on key 'fs.protected_symlinks'
sysctl: permission denied on key 'kernel.cad_pid'
sysctl: permission denied on key 'kernel.unprivileged_userns_apparmor_policy'
sysctl: permission denied on key 'kernel.usermodehelper.bset'
sysctl: permission denied on key 'kernel.usermodehelper.inheritable'
sysctl: permission denied on key 'net.core.bpf_jit_harden'
sysctl: permission denied on key 'net.core.bpf_jit_kallsyms'
sysctl: permission denied on key 'net.ipv4.tcp_fastopen_key'
sysctl: permission denied on key 'net.ipv6.conf.all.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.default.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.ens3.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.eth42.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.eth43.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.hwsim0.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.lo.stable_secret'
net.ipv4.conf.veth42.accept_local = 0
net.ipv4.conf.veth42.accept_redirects = 1
net.ipv4.conf.veth42.accept_source_route = 1
net.ipv4.conf.veth42.arp_accept = 0
net.ipv4.conf.veth43.accept_local = 0
net.ipv4.conf.veth43.accept_redirects = 1
net.ipv4.conf.veth43.accept_source_route = 1
net.ipv4.conf.veth43.arp_accept = 0
net.ipv6.conf.veth42.accept_dad = 1
net.ipv6.conf.veth42.accept_ra = 1
net.ipv6.conf.veth42.accept_ra_defrtr = 1
net.ipv6.conf.veth42.accept_ra_from_local = 0
net.ipv6.conf.veth42.accept_ra_min_hop_limit = 1
net.ipv6.conf.veth42.accept_ra_mtu = 1
net.ipv6.conf.veth42.accept_ra_pinfo = 1
net.ipv6.conf.veth42.accept_ra_rt_info_max_plen = 0
sysctl: permission denied on key 'net.ipv6.conf.veth42.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.veth43.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.wlan0.stable_secret'
sysctl: permission denied on key 'net.ipv6.conf.wlan1.stable_secret'
net.ipv6.conf.veth42.accept_ra_rtr_pref = 1
net.ipv6.conf.veth42.accept_redirects = 1
net.ipv6.conf.veth42.accept_source_route = 0
net.ipv6.conf.veth43.accept_dad = 1
net.ipv6.conf.veth43.accept_ra = 1
net.ipv6.conf.veth43.accept_ra_defrtr = 1
net.ipv6.conf.veth43.accept_ra_from_local = 0
net.ipv6.conf.veth43.accept_ra_min_hop_limit = 1
net.ipv6.conf.veth43.accept_ra_mtu = 1
net.ipv6.conf.veth43.accept_ra_pinfo = 1
net.ipv6.conf.veth43.accept_ra_rt_info_max_plen = 0
net.ipv6.conf.veth43.accept_ra_rtr_pref = 1
net.ipv6.conf.veth43.accept_redirects = 1
net.ipv6.conf.veth43.accept_source_route = 0
sysctl: permission denied on key 'vm.mmap_rnd_bits'
sysctl: permission denied on key 'vm.mmap_rnd_compat_bits'
sysctl: permission denied on key 'vm.stat_refresh'"
1704210,2017-07-14 16:12:24 UTC,"ubuntu@autopkgtest:~$ sudo cat /run/NetworkManager/system-connections/netplan-eth42
[connection]
id=netplan-eth42
type=ethernet
interface-name=eth42"
1704210,2019-07-11 14:27:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704226,2019-02-11 12:01:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704226,2017-07-14 00:14:48 UTC,"Somewhat sheepishly, I have to admit that I didn't read the error message carefully at first. I think I see the issue now."
1704229,2017-10-08 09:33:37 UTC,The recommended approach is to create a virtualenv (virtualenv -p pypy my-virtualenv). This will have pip in it.
1704229,2017-07-17 13:40:39 UTC,May want to also package pypy-pip-whl as it is a dependency of python-pip.
1704233,2017-11-08 12:54:47 UTC,"Hi Guys,"
1704233,2017-08-04 08:39:59 UTC,"Point #1 is being addressed, and a newer CentOS version will include a newer cloud-init."
1704233,2017-09-07 14:23:14 UTC,#2: this is what happens on different hosts:
1704237,2017-07-14 13:58:44 UTC,I am running gnome 3.14.0 on CentOS Linux 7 (Core)
1704237,2017-07-14 07:04:55 UTC,what Linux with what windows manager?
1704237,2017-07-14 15:06:05 UTC,What about that?
1704237,2017-07-14 15:28:09 UTC,As requested:
1704237,2017-07-14 15:39:29 UTC,"I ran the older version 1.0.1 to use it for capturing, and it is also
now only capturing on screen 1.
I'm now suspecting a gnome / centos / hardware issue rather than a
sikuli issue."
1704237,2017-07-14 15:52:49 UTC,"Since I cannot test on Linux real machines and even not with more than one monitor, I wanted to be sure about the screen setup as Java sees it."
1704237,2017-07-14 16:06:05 UTC,That worked as it should:
1704237,2017-07-14 17:11:17 UTC,"ok, thanks for testing."
1704239,2017-07-14 03:05:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/483785"
1704239,2017-12-20 18:26:25 UTC,"Change abandoned by Akihiro Motoki (<email address hidden>) on branch: master
Review: https://review.openstack.org/483785
Reason: We have merged django-openstack-auth code into horizon. You need to re-propose it to the horizon repository to continue the work if needed. When re-proposing a patch to horizon, it would be nice if you include this review URL in the commit message so that reviewers can follow the discussion here. Thanks for the inconvenience and your patience."
1704242,2017-07-14 23:17:05 UTC,I updated Octave using the following commands:
1704252,2018-02-02 21:13:16 UTC,"I would love to implement such support, but I guess the trouble is having access to the hardware or (realistically) vm configuration that we could utilize to simulate. Any suggestions are greatly welcome!"
1704252,2018-06-22 00:59:09 UTC,"Julia,
  The OPNFV project has some arm64 servers available for adding arm64 support to bifrost.
  The servers are part of a Lab as a Service (LaaS) resource.  I can probably provide you access to a machine. I might be able to help you test, etc."
1704252,2018-07-03 17:02:29 UTC,"Julia, the Works on Arm project has hardware available for porting. Currently we support bare metal, and there are plans for vm configurations as well."
1704255,2017-07-20 20:28:47 UTC,I can confirm that this test works on master (commit 5eca374) and fails on plan (as of 2017-07-20; commit non meaningful because of frequent rebasing) using ABCL 1.3.2.
1704265,2017-07-14 18:35:19 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1704265,2017-07-14 18:35:47 UTC,This may be a duplicate of bug 1692981.
1704279,2017-07-25 07:45:38 UTC,Mr.Sean
1704279,2018-04-03 10:47:45 UTC,"Change abandoned by Tetsuro Nakamura (<email address hidden>) on branch: master
Review: https://review.openstack.org/483863"
1704279,2017-07-14 08:12:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/483863"
1704279,2017-07-23 04:16:27 UTC,virtio-net interfaces need to to handeled in a different way then standard network interafaces as of dpdk 2.X before they changed to the date based releases.
1704295,2017-07-14 06:34:56 UTC,Although closing the app and reopening it often skips the thin titlebars phase so it's not easy to reproduce on demand...
1704295,2017-07-17 02:09:58 UTC,Screenshot?
1704295,2017-07-17 02:27:21 UTC,Screenshot attached. You can see the titlebar is shrunken down to the size of the buttons.
1704295,2017-07-19 02:21:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704301,2017-08-03 11:02:47 UTC,Thank you for the report.
1704301,2018-01-25 08:36:34 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3721
1704301,2017-08-04 02:23:13 UTC,"Yes, I always crash mysqld with an empty table - no dml.  This happens after a short time running this in a loop:"
1704302,2017-07-14 07:00:07 UTC,"@Edmundo
Thanks for your efforts tracking down the problem."
1704302,2017-07-16 15:06:09 UTC,"To isolate a different version of Java I created a docker container with OpenJDK 7u131, it's working as expected so far."
1704302,2017-07-14 18:25:16 UTC,"I found other complaints about this problem, it seems to be a problem with Ubuntu 16.04 or systems based on it, and seems to happen in any window manager."
1704310,2019-05-06 08:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1704310,2019-07-30 01:02:45 UTC,00289cd87676 6de5d06e657a 700cd033a82d 87a30e1f05d7 8aac0e233891 b70d31d054ee ca6bf264f6d8
1704310,2018-07-25 16:06:27 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1704329,2019-12-11 09:11:54 UTC,"Change abandoned by Bharat Kunwar (<email address hidden>) on branch: master
Review: https://review.opendev.org/496702
Reason: The magnum team is cleaning the backlog of patches and stories. If you still face this issue and you want to work on it please reopen."
1704329,2017-08-23 13:03:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496702"
1704348,2017-07-14 09:08:42 UTC,Window manager used was Marco.
1704348,2017-07-14 09:47:25 UTC,Switching focus-mode to sloppy raise-on-click starts working.
1704349,2017-08-13 12:51:36 UTC,Founder of Elementary OS Daniel Foré confirmed that Elementary OS is very forward looking and thus will not support 32 bit builds anymore. Source: http://blog.elementary.io/post/145881464631/loki-beta#comment-2729205609
1704369,2017-08-17 07:32:24 UTC,No installation possible
1704369,2017-10-02 20:25:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704371,2017-07-14 10:29:48 UTC,"Please, type the command thay you was using to get this error.
It seems like an api error could you please share the freezer-api logs with debug mode enabled so we can understand what is the problem ?"
1704385,2017-12-05 21:59:21 UTC,Hi Stefan. The two parts of the the object has diferent transforms. Seems to me also happends in 0.48 whith the same file. Anyway Im not a python expert so remove my self asignation.
1704386,2017-09-28 18:10:12 UTC,"I experience the same issue, however, it's related to kernel 4.4.0.96."
1704388,2017-07-14 12:56:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704388,2018-05-02 22:35:21 UTC,"18.04 for ""Russian"" also has the bug"
1704388,2017-07-14 12:58:51 UTC,I just tested freshly downloaded Ubuntu Server 16.04.2 and 17.04 and both of them are affected by the bug.
1704388,2017-12-13 21:53:58 UTC,16.04.03 still has the bug
1704388,2018-04-30 11:31:05 UTC,18.04 also has the bug
1704391,2017-07-14 15:46:49 UTC,"Chris,"
1704402,2017-10-09 19:02:58 UTC,3 months and not a single response?
1704402,2017-08-20 23:29:42 UTC,Beuller?
1704402,2019-02-19 14:41:57 UTC,Dropping this from the cloud-init Ubuntu package so we're just tracking it in one place.
1704402,2017-11-01 21:17:15 UTC,"Hi David,This ticket is for the source-list, which is for dns resolver and the config is as follows.
  version: 1
  config:
  - type: physical
    name: eth0
  - type: nameserver
    address: ['xx.xx.xx.xx']    sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx'] I believe the only thing that is needed for cloud-init is to add the keyword ""sort-list"" to the case list, so that it is written to /etc/resolv.conf.
As for source-based routing, there is no config recognized by cloud-init.  It's just straight network statements, name, ip, netmask, etc.  The work is done by a shell script in the if-up.d directory as follows:
#!/bin/sh
set -e
if [ ""$METHOD"" = loopback ]; then
    exit 0
elif [ ""$METHOD"" = dhcp ]; then
    exit 0
elif [ ""$METHOD"" = static ]; then
    if [ ""$IF_GATEWAY"" ]; then
echo ""exiting...""
        exit 0
    fi
fi
IF_GATEWAY=""$(echo ""$IF_ADDRESS"" | cut -d. -f1-3).254""
ip route flush table ""$IFACE""
ip route add default via ""$IF_GATEWAY"" table ""$IFACE""
ip rule del lookup ""$IFACE"" || true
ip rule add from ""$IF_ADDRESS"" lookup ""$IFACE"""
1704402,2017-09-07 14:39:04 UTC,Is this site even monitored?
1704402,2017-10-27 19:00:06 UTC,"Hey Scott,
Been taking a deep dive into the netplan package, a la 17.10.  Less than 20 minutes review, and can already see 1/2 dozen things that aren't implemented and will completely break networking in just my environment.  Given its current state, I can't believe they even allowed it into 17.10 for testing.  It is woefully lacking so many functions it shouldn't have even been considered.  Hopefully, come 18.04, they'll drop the package and attempt it again later, say 19.04 or 19.10.  It's interesting in concept, but at this point, it's alpha code at best, and needs work to get to beta."
1704402,2017-10-18 18:46:42 UTC,"Damn, I just realized, netplan doesn't use ifup and ifdown now, does it?  That's going to completely break my source-based routing.  The important part is as follows:"
1704402,2017-10-18 18:30:55 UTC,"Hey Scott, was going back and forth a bit with Stephane.  Something goofy stil, as I was using ubuntu-daily:artful, which should have actually failed, cause daily doesn't have artful, but has 17.10, and images:, is the opposite.  so even though I specified ubuntu-daily, it seemed to still be using the artful from images despite my command.  I do have working instances of artful/17.10, whichever, lol, but cloud-enabled, yeah!!!  It thankfully renders my version1 systax to netplan, nice job, I was worried I was going to have to rewrite tons of network stuff.  Manually edit netplan to include sortlist, since cloud-init doesn't.  Restart, etc, netplan/systemd-resolve completely ignores it as I was expecting.  It does seem that netplan and systemd-resolve is going to defer to /etc/gai.conf which follows RFC 3484 as I mentioned previously.  But that's going to be a whole other issue, and frankly, until I'm stuck using 17.10 and later, I really don't want to brush up on yet another RFC.  I'm not that bored."
1704402,2017-10-18 18:08:42 UTC,"James, sorry, can you show what you were doing ?"
1704402,2017-11-01 20:42:36 UTC,Hi James -- do you have an example #cloud-config that you can attach that sets up source-based routing (please sanitize first if required)?
1704402,2017-10-18 17:25:08 UTC,"Appreciate that.  I always forget about daily.  So spun it up, and due to netplan, everything networking broke, as in network-config was ignored, and cloud-init couldn't use any of it.  I'm guessing that netplan is supported using Networking Config Version 2 — Cloud-Init 17.1 documentation?  I currently use Version 1.  FYI, sortlist under the old method, ie version 1, does no harm under netplan.  It in fact does the same as the rest of the network config, nothing, lol."
1704402,2017-10-18 14:45:52 UTC,'sortlist' is new to me.. I've just never ran into it before.
1704402,2017-10-18 17:54:49 UTC,"Well, build with the ubuntu-daily, and there weren't even any files at /var/lib/cloud.  I put up a post in lxc/lxd to inquire whether the image actually supports cloud-init under lxd with the new version.  network-config, user-data, vendor-data, etc were all missing and non-functioning under lxd.  Obviously more things have changed, as no adjustments were needed for 16.10 or 17.04.  Very sad. :("
1704402,2017-10-18 15:41:39 UTC,"Trying to do some testing real quick and research on systemd-resolve.    Unfortunately it doesn't seem there is a cloud-init enabled version of artful yet on ubuntu: to really test.  I have looked at what systemd-resolve is doing with it on 16.10 and earlier, and systemd-resolve seems to be oblivious to it, but then the system seems oblivious to systemd-resolve.  I think given that 16.04 LTS still has 3.5 years of support, it still has a long life, and that adding sortlist, which I think may just be a one line change(?) will add the functionality for those who want/need it, but come systemd-resolve coming in to effect, I will have to wait til cloud-init artful is available to test.  I will however continue to test against 17.10 as I'm able to get a cloud-init version functioning on lxd.  I can't imagine Stephane will be far off on that one.  He's usually pretty on the ball."
1704402,2017-10-18 15:45:24 UTC,"While I joked about it on github, it looks like sortlist from resolv may very well be superceded by RFC 3484 when falling under systemd-resolve."
1704402,2017-10-31 15:36:55 UTC,"Hi Scott,I know you're aware of and dealing with netplan issues, but not if you're directly involved with it.  But netplan has serious deficiencies and nowhere near as inclusive or as capable as the current system.  Functions such as source-based routing, open vswitch support, etc.  One release before an LTS seems far too late to introduce such a half-baked and untested package that is so central to network connectivity.  Please tell me their not seriously considering going forward with it for the next LTS.  If so, I may have to stay on 16.04 til 20.04 comes along, assuming they get it working by then.James"
1704402,2017-10-18 16:08:33 UTC,"Hi Scott,Not sure if launchpad sends you notice of updates or not.  Let me know if it does.  Was surprised that this message came from your actual address, so you sent, or that's just how launchpad works, but added some comments on the ticket for you to see.  I might be able to use packer to generate my own cloud-init version of artful til Stephane and the guys have a chance to add it to the ubuntu: image server.  If so, I'll test with a system running systemd-resolve, not just for sort list, but the networking functions in general.  My containers tend to be a little more complex than the average regarding network configs, ovs, multi-home, custom routing, vlans, etc.  Blame it on my 30 years of networking, lol.
James"
1704402,2017-10-18 17:03:42 UTC,"James,"
1704402,2017-10-18 17:04:14 UTC,"(I do get email on bug comments, but as you've seen sometimes I miss them)."
1704402,2017-10-18 15:59:24 UTC,"hmm...launchpad doesn't let me edit, so adding this from systemd-resolve docs:"
1704404,2017-07-17 08:52:45 UTC,"Przemek,"
1704404,2017-08-02 11:29:18 UTC,"Krunal,
I have very basic settings, this is from writer node and others have almost identical:"
1704404,2018-01-18 08:16:44 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-850
1704404,2017-11-01 12:37:10 UTC,"commit 28b60e8f723ab3d641cf7e14ea24ecad22f2bc9f
Author: Krunal Bauskar <email address hidden>
Date:   Fri Aug 11 08:59:51 2017 +0530"
1704416,2018-02-26 16:10:07 UTC,"Sorry - if this is still an issue, please reply here."
1704430,2017-07-14 19:17:50 UTC,apport information
1704430,2017-07-18 15:11:32 UTC,"kernel-fixed-upstream
4.13.0-041300rc1-generic"
1704430,2017-07-17 12:33:52 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].
1704430,2017-07-14 19:18:14 UTC,apport information
1704430,2017-07-14 19:18:08 UTC,apport information
1704430,2017-07-14 19:17:58 UTC,apport information
1704430,2017-07-14 19:17:54 UTC,apport information
1704430,2017-07-14 19:17:44 UTC,apport information
1704430,2017-07-14 19:17:40 UTC,apport information
1704430,2017-07-14 19:17:37 UTC,apport information
1704430,2017-07-14 19:17:26 UTC,apport information
1704430,2017-07-14 19:17:22 UTC,apport information
1704430,2017-07-14 19:17:13 UTC,apport information
1704430,2017-07-14 19:17:10 UTC,apport information
1704430,2017-07-14 16:57:07 UTC,"added xinput.log (getting info about mouse porperties) and system.log with some information
what Linux I'am running."
1704430,2017-07-14 16:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1704430,2017-07-14 19:17:47 UTC,apport information
1704433,2019-08-28 04:17:25 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1704433,2019-06-28 13:02:11 UTC,"Intel upstream think it is not must for OSV, so close it as invalid."
1704433,2018-02-24 00:01:18 UTC,"plan in 4.16, until now, no commit available."
1704433,2018-07-25 15:59:36 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1704433,2018-02-23 23:39:23 UTC,Is there a list of commits we should confirm for 18.04?
1704433,2019-05-06 09:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1704453,2019-09-18 10:44:22 UTC,"I have similar behavior: the automatic path creation to a file does not work correctly. There is an issue with too few ""..""
Example:
- I highlight some text in a page and want to link a file.
- In the ""Edit Link""-window, I open ""Browse"" and browse to the file.
- Choosing the file via the button ""Open"" brings me back to the ""Edit Link""-window.
- The automatically set path in ""Link to:"" is wrong if the link has to go up more than 1 hierarchy level: it places ONE AND ONLY ONE "".."" to navigate out of the current folder. However, more ""..""'s are necessary to navigate to the correct level."
1704464,2018-09-04 23:20:34 UTC,The current post-18.07 VPP master now has the APIs we require for this (https://gerrit.fd.io/r/#/c/14445/).
1704472,2019-06-14 03:55:28 UTC,This issue was fixed in the openstack/pbr 5.3.0 release.
1704472,2018-01-25 14:44:22 UTC,"The problem is, that when the file is open, no encoding is specified so it is dependent on current default console encoding what is definitely not deterministic."
1704472,2018-04-27 20:13:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564874"
1704472,2017-07-14 19:51:21 UTC,This is a serious issue because the chance of having Unicode characters inside description is huge if you append the automatically generated ChangeLog to it.
1704472,2019-06-10 22:55:43 UTC,"Reviewed:  https://review.opendev.org/564874
Committed: https://git.openstack.org/cgit/openstack/pbr/commit/?id=3b102a551bb2518682a0da4e6065feeb7f20807a
Submitter: Zuul
Branch:    master"
1704473,2017-07-14 19:58:58 UTC,Yakkety and xenial are the only affected. 3.5.3 has this fix in zesty and artful.
1704473,2018-02-28 06:30:14 UTC,"I just ran into this yesterday and was going to submit a bug report.  Given that this is a one-line fix, can we get this backported?  I'm happy to make the patch file."
1704484,2017-07-14 22:27:30 UTC,I think the Epoxy support should be enabled.
1704484,2017-07-14 22:32:15 UTC,This is also affecting others users of Mint: https://youtu.be/VsaFQdRfacQ
1704484,2017-09-02 11:00:59 UTC,"It's actually very easy to fix.
!!!
Apply commit ' compositor: Disable XPresent on error' (https://github.com/xfce-mirror/xfwm4/commit/7d9e6ceda2d02b4f1f00ce70e86333317c3369a1)!!!"
1704497,2017-07-14 21:59:46 UTC,I'm not sure helpful this is but I did a little testing with swift client cli
1704497,2017-07-31 14:09:21 UTC,"I haven't used RadosGW myself, we'll need someone with a working reproducer to take a look."
1704497,2017-08-01 13:55:02 UTC,"I have an environment that has the same issue, if you need someone to reproduce this so you can take a look around my environment is throw away. Let me know if you would like to schedule a meeting to troubleshoot."
1704497,2017-11-03 10:51:46 UTC,"I've run into this bug as well. As the comment of Alexander described, the swiftclient lib does know how to connect to radosgw, so the bug is in the Ironic part getting the tempurl. I spent some time searching and I came to the following dirty trick:"
1704497,2017-12-14 21:05:38 UTC,I am facing the similar error when I put /swift like
1704497,2018-01-11 02:52:54 UTC,"This is due to this patch https://review.openstack.org/#/c/367377/
Remove the check in python-swiftclient works for me(but not in an elegant way)."
1704512,2018-07-24 09:32:36 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1704512,2017-07-19 20:44:21 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1704512,2017-07-19 03:02:35 UTC,"I don't have relevant log files and can't currently replicate the issue since I'm on 4.11.10, so I will mark this as complete."
1704512,2017-07-17 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1704512,2017-07-17 19:35:44 UTC,Thanks for filing this bug in Ubuntu.
1704513,2017-12-07 12:16:35 UTC,see also:
1704513,2017-07-15 11:43:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704535,2017-07-15 08:30:04 UTC,This change was made by a bot.
1704540,2017-07-15 19:40:46 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1704545,2018-12-12 07:36:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704556,2020-04-17 16:10:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704556,2021-01-09 22:42:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1273534, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1704558,2017-12-11 06:08:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704558,2020-07-01 21:18:34 UTC,"Thank you for your bug report, it does sound like a local issue during the installation than a package bug though"
1704559,2017-07-27 16:31:57 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1704559,2017-07-15 16:15:58 UTC,"This may be a security problem, because also the currently running connection is also not shown/named. It looks like wifi is inactive, but the computer may be connected to an insecure, unencrypted or fishy network without user knowledge."
1704574,2017-07-18 16:27:40 UTC,"Reviewed:  https://review.openstack.org/484162
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=913149249cc00f50a6219d3ddc86f3600a610c00
Submitter: Jenkins
Branch:    master"
1704574,2017-07-19 16:06:31 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/485263"
1704574,2017-07-28 07:40:29 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1704574,2017-08-12 06:18:44 UTC,"Reviewed:  https://review.openstack.org/485263
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dc85c089702a9819fdab7c951d427de838a3dcc6
Submitter: Jenkins
Branch:    stable/ocata"
1704574,2017-08-22 11:39:31 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1704574,2017-07-15 17:54:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484162"
1704576,2017-07-16 10:45:53 UTC,"Hi, this activity was developed for MSTS and not for OR. The activity is too heavy for OR, you should try to modify the various options of OR to have a remote chance of playing it, otherwise you need to use MSTS for the first part. You also have the message that you miss many sounds
Regards,
Sergio."
1704579,2017-07-15 17:42:19 UTC,"Hmm, it's in a special section for Settings.  Which requires pressing Down then Right then Enter.  It should just be Enter, because it's the most relevant action."
1704579,2020-11-17 05:27:16 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life in April 2019."
1704583,2017-08-13 02:22:40 UTC,Anyone ?...
1704587,2019-03-08 02:26:49 UTC,Won't fix because affected branch no longer supported.
1704591,2017-07-16 06:39:23 UTC,"This feature is not complete, so this bug should be linked to Blueprint to implement Ejector"
1704597,2017-07-16 00:22:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1704599,2017-07-17 13:59:55 UTC,"I think I know what you mean, but just to express it in other words, the idea is that authority_control_fields.pl (or perhaps a separate batch job) would do something like this:"
1704599,2017-07-19 18:19:25 UTC,"That sounds like exactly what I would imagine.  Thanks, Galen!"
1704603,2017-07-17 16:03:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704614,2017-07-17 22:37:29 UTC,"I had this problem since I upgraded in 17.04, that is the main reason for me to make a fresh reinstall.
I don't remember however if I had this in 16.** series too."
1704614,2017-07-17 22:44:45 UTC,I don't find where to had the kernel-bug-exists-upstream tag...
1704614,2017-07-17 22:45:50 UTC,">I don't find where to had the kernel-bug-exists-upstream tag...
"
1704614,2017-07-19 13:22:16 UTC,My other PC on Fedora Linux hooked to the same KVM switch doesn't take this much to boot.
1704614,2017-07-20 05:28:05 UTC,"Fedora kernel you used is 4.11 ""Linux version 4.11.10-200.fc25.x86_64"""
1704614,2017-07-24 08:34:54 UTC,filled an upstream bug report
1704614,2017-07-24 06:42:11 UTC,"Ok, didn't notice it's two different machines - please file an upstream bug."
1704614,2017-07-27 13:04:18 UTC,"I followed the upstream bug report guidelines but I can't see my report being processed on the kernel ML, so I guess something made my report rejected..."
1704614,2017-10-23 10:14:45 UTC,"Today I upgraded my distro to 17.10, problem still remain."
1704614,2017-12-07 13:07:56 UTC,"new tests, maybe not USB related after all, look at #1736947"
1704614,2017-07-17 12:37:46 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1704614,2017-07-20 13:28:41 UTC,Did the test
1704614,2017-07-17 00:47:43 UTC,apport information
1704614,2017-07-17 00:47:27 UTC,apport information
1704614,2017-07-17 00:47:38 UTC,apport information
1704614,2017-07-17 00:47:36 UTC,apport information
1704614,2017-07-17 00:47:35 UTC,apport information
1704614,2017-07-17 00:47:33 UTC,apport information
1704614,2017-07-17 00:47:32 UTC,apport information
1704614,2017-07-17 00:47:30 UTC,apport information
1704614,2017-07-17 00:47:29 UTC,apport information
1704614,2017-07-16 05:09:22 UTC,I booted with 'debug' in linux line in grub and issued a 'journalctl -ab' command
1704614,2017-07-17 00:47:25 UTC,apport information
1704614,2017-07-17 00:47:23 UTC,apport information
1704614,2017-07-17 00:47:21 UTC,apport information
1704614,2017-07-17 00:47:20 UTC,apport information
1704614,2017-07-17 00:47:40 UTC,apport information
1704614,2017-07-16 08:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1704632,2017-10-22 08:12:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704652,2018-03-20 23:20:26 UTC,I have attempted to reproduce this locally and it seems to work just fine.
1704652,2018-03-21 09:03:09 UTC,"The scenario as I recall is this:
1. Set up a private index (e.g. with devpi)
2. Upload an older version of pbr to that index
3. Create a python package with pbr
4. Run pip install -e ./package -i <your index url>"
1704673,2017-07-16 19:39:57 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1704678,2017-07-20 18:59:28 UTC,"It might be that these entries are deliberately malformed, but seahorse also doesn't display them appropriately."
1704682,2017-07-16 23:12:03 UTC,I forgot to dump the routing table after the client went up:
1704682,2019-07-17 19:13:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704689,2017-07-17 02:01:26 UTC,"This may be a duplicate of lp:1433383.  Per the instructions there, I've collected /var/l*/{apt,dpkg,landscape}* before restarting the landscape client, and placed them in https://private-fileshare.canonical.com/~paulgear/lp1704689/"
1704689,2017-07-17 02:03:44 UTC,"Also, the system in question was recently upgraded from precise to trusty to xenial, if that makes any difference."
1704689,2017-07-18 11:08:09 UTC,"After restarting the landscape client, correct security updating has occurred.  I'm not sure if landscape or unattended-upgrades was responsible for this."
1704718,2017-07-17 06:25:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704718,2017-07-17 12:37:04 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1704718,2017-07-21 06:24:05 UTC,"I installed Kernel 4.13-rc1 on 3 workstations so far and tonight one of them froze once again, this time leaving the attached Kernel panics in the journal."
1704718,2017-07-21 07:04:32 UTC,You need to file an upstream bug to escalate this issue to AMD developers.
1704719,2017-07-17 06:31:18 UTC,my.cnf
1704719,2017-07-17 08:58:12 UTC,It is likely a VM related n/w issue if you don't see it with bare-metal (h/w) but only on VM.
1704719,2017-07-25 17:21:37 UTC,"We started to see such crashes on hardware setup as well, so I removed the VM from bug description."
1704719,2018-01-18 08:21:21 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1995
1704735,2019-08-03 12:21:09 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu since that time.
1704735,2019-10-03 04:17:19 UTC,[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]
1704735,2017-07-18 18:19:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704739,2017-07-17 07:50:26 UTC,syntax proposals (available as of 0.32.2):
1704740,2019-03-15 19:24:16 UTC,this issue is no longer reproducible with:
1704740,2019-04-29 08:49:16 UTC,Upstream fix is scheduled for 6.3.0 (Week 32)
1704740,2019-04-08 09:12:21 UTC,Setting to VERIFIED FIXED
1704740,2019-04-04 10:07:42 UTC,"You're right!!
This is fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=7fdc5df36f5b50e0629405a47ff3d5765fcfeb93"
1704740,2019-03-18 20:48:46 UTC,"(In reply to Xisco Faulí from comment #6)

> Still reproducible in
> Version: 6.3.0.0.alpha0+
> Build ID: a11a2d84b09f85d2020c47f3ce42cd9efbff818a
"
1704740,2019-03-18 19:47:19 UTC,Still reproducible in
1704740,2018-11-21 13:47:01 UTC,"Hi Eike, I've just found this issue as being the same root cause of bug 121568, I thought you might be interested in this issue as it's affecting formulas..."
1704740,2019-04-04 11:04:38 UTC,"No need a test for this, this is already covered by https://gerrit.libreoffice.org/plugins/gitiles/core/+/6280b5c1c62ad40b5b9780a93c7cbee9ca0260f8%5E%21"
1704740,2018-11-21 13:45:06 UTC,"Regression introduced by https://cgit.freedesktop.org/libreoffice/core/commit/?id=5ef856e975d7c0396984d588a43fd1a7c7085c55, which is the same as in bug 121043.
Closing as RESOLVED DUPLICATED"
1704740,2018-11-20 23:44:16 UTC,Thanks for looking at this. Filed upstream on Bugzilla: bug 121568
1704740,2018-11-20 23:42:51 UTC,"Created attachment 146856
""Before"" state of test case."
1704740,2018-11-20 23:41:03 UTC,"Description:
See attached test case. Sum two rows: A1 + B1 = C1; A2 + B2 = C2 where B1 is blank. Cut B2 and paste into B1. Result C2 is decremented correctly by old B2 value; but result C1 is NOT incremented by new B1 value. Formula of C1 remains correct =SUM($Sheet1.A1:B1) as is C2's formula but C1 result is wrong. Saving file, close and re-open does not fix incorrect C1 result. Undo undo to return to initial state results in C2 now having incorrect result. Bug occurs whether drag and drop or control-x/control-v used. This is a data integrity issue as the wrong answer is being displayed."
1704740,2018-10-29 19:35:31 UTC,"Created attachment 146149
Sample ODS"
1704740,2018-11-20 17:29:07 UTC,"I can reliably reproduce the issue with the test case attached, on Ubuntu 16.04 and 19.04 (libreoffice 6.1.3.2).
I can also reproduce the issue with the upstream build of libreoffice (6.1.3.2)."
1704740,2018-10-29 21:46:48 UTC,"Confirm with Version: 6.2.0.0.alpha1+
Build ID: a50f845957fff66ca7f459da4878be4597e0bae3
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: x11;"
1704740,2018-10-29 19:42:42 UTC,"There are a couple of other, already fixed bugs starting with the same commit, eg. bug 86615."
1704740,2018-11-21 13:45:06 UTC,*** Bug 121568 has been marked as a duplicate of this bug. ***
1704745,2017-08-29 16:08:10 UTC,"> Sorry, I don't understand why installing it from .deb should change the behavior
"
1704745,2017-08-29 15:46:27 UTC,"> The LibreOffice 5.4 in the daily build came with it. Unlike you, I didn't install it from deb.
"
1704745,2017-08-29 09:45:21 UTC,"It's Gnome Shell, with Activities, new Ubuntu Dock bar and everything."
1704745,2017-08-29 09:20:12 UTC,"Yes graphics driver could be a factor. Also your screenshot suggests maybe you're not using Gnome Shell, maybe Unity?..."
1704745,2017-08-29 09:08:04 UTC,That's weird. Do you think that the VM might affect this behavior? I just installed latest 17.10 build and Libreoffice 5.4 from debs in Virtualbox and the issue seems gone
1704745,2017-08-29 15:25:24 UTC,"The LibreOffice 5.4 in the daily build came with it. Unlike you, I didn't install it from deb."
1704745,2017-08-29 03:19:06 UTC,"By the way, in Ubuntu 17.10 daily build, and LibreOffice 5.0.4, the bug still exists. See attachement."
1704745,2017-08-29 02:06:40 UTC,"It's not a feature, it's a bug in some themes. If it was a feature, the ""white square"" would somehow appear in themes like Adwaita. But it doesn't. It would also appear in MacOS or Windows. It doesn't. Please, get real.  ;-)"
1704745,2017-08-29 01:48:53 UTC,"I do see the issue in 17.10 still. But to me it looks like a feature, if not a bug. The ""white square"" ties the close button to the document area. So it looks intentional and logical. Maybe it's not intentional, but either way not a big problem."
1704745,2017-08-28 17:46:17 UTC,I cannot reproduce the issue anymore with LibreOffice 5.4
1704745,2017-07-17 14:31:46 UTC,Confirmed on Ubuntu 17.04 using Libreoffice 1:5.3.1-0ubuntu2
1704745,2017-07-17 08:36:00 UTC,"By the way, I think that a mix of Pop!_OS GTK theme (from Adapta) and United-Gnome Ubuntu shell theme would do a great job. See attachements for an example. The United-Gnome GTK theme would be nice too."
1704745,2017-08-29 03:28:18 UTC,Yes confirmed the bug is still in 17.10.
1704750,2017-07-17 08:36:36 UTC,"Uploaded the photo elsewhere since it looks like it got dropped when submitting the bug:
 imgur.com  /a/GDHJI"
1704750,2017-07-18 11:56:12 UTC,"One important detail: I also had an AMD radeon video card plugged in but the display was connected to the integrated VGA port. After removing the radeon card, the artefacts went away."
1704753,2019-05-27 12:46:30 UTC,"Thank you for your bug report. What locale do you use? Where is the time format wrong, could you make a screenshot showing the issue?"
1704753,2019-07-27 04:17:29 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1704777,2019-12-11 04:04:26 UTC,migrated to:  https://gitlab.com/inkscape/inbox/issues/1355
1704777,2017-07-19 14:49:14 UTC,Thank you very much!
1704777,2017-07-19 12:33:50 UTC,"> Oh yes, I like that. Would it be hard to do?
"
1704777,2017-07-18 04:30:54 UTC," > This way one can have the convenience of tools remembering a style during one session, but they will revert to their default style the next time one uses Inkscape, reverting any ""strange"" styling that might have been set the last time Inkscape was used."
1704777,2017-07-17 14:05:50 UTC,"As a developer when I say ""by default"" I mean the state a new user without previous preferences will see, so we're talking about the same thing. As a developer I aim at setting those defaults to preferences that fit the largest possible group of users."
1704777,2017-07-17 16:54:14 UTC,One more comment.
1704777,2017-07-17 16:41:40 UTC," > You're right that changing the default would be easy, but I'm pretty sure if we change it to be ""own style"" we will get at least the same amount of forum posts complaining about the tools *not* saving their style and questions on how to adjust the default style, therefore I don't think this will solve the problem."
1704777,2017-07-17 14:16:32 UTC,"Maybe to clarify:
Setting those tools to ""own style"" would prevent newbies from doing errors, I agree with that.
However I'm pretty sure that ""own style"" is not the ideal setting for most users that spent some time with Inkscape."
1704777,2017-07-17 13:27:45 UTC," > On the other hand I also don't like the idea of having those tools use their ""own style"" by default: If I am working on an image and draw a rectangle it's likely that I want to draw some additional rectangles with the same style."
1704777,2017-07-17 12:33:27 UTC,"I certainly don't like the way it works now: How often have I opened Inkscape, drawn a rectangle and realized that it had opacity or fill transparency (sometimes both!) set from the last time I used the tool and had to click through the menus to reset those to sane defaults (i.e. opaque)."
1704777,2017-07-17 17:07:55 UTC,"> I didn't quite understand your suggestion about ""last used per session""
"
1704788,2017-08-22 11:39:17 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1704788,2017-08-12 11:05:47 UTC,"Reviewed:  https://review.openstack.org/490110
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3eefcce2553856a1635a62fecf73cd9a2d9097cb
Submitter: Jenkins
Branch:    stable/ocata"
1704788,2017-08-02 17:37:19 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/490110"
1704788,2017-08-11 12:27:10 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1704788,2017-07-18 14:39:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484828"
1704788,2017-07-18 14:02:03 UTC,"""because that would mean we would go against the consensus we had in Ocata."""
1704788,2017-07-18 10:03:10 UTC,"Agreed with Matt about a communication problem.
The Ocata consensus was about to say that we would stop using custom drivers also for scheduler, but still accepting custom filters (so people wanting to have a specific driver could just create a filter for the FilterScheduler that would be calling the 3rd-party driver)."
1704788,2017-08-02 16:58:01 UTC,"Reviewed:  https://review.openstack.org/484828
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1e5c7b52a403e708dba5a069dd86b628a4cb952c
Submitter: Jenkins
Branch:    master"
1704788,2017-07-17 21:23:03 UTC,This was introduced in this change in Ocata:
1704798,2017-10-25 19:22:39 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1704798,2017-10-24 12:42:34 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1704798,2017-09-20 08:54:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/505546"
1704798,2017-09-20 08:45:53 UTC,"Reviewed:  https://review.openstack.org/485121
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=905d31dd9715505599b0a2ad123eebef37f606f5
Submitter: Jenkins
Branch:    master"
1704798,2017-10-17 23:57:24 UTC,"Reviewed:  https://review.openstack.org/505546
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c0ff5b33ca42a417a5fa08e5133a27397af08c3d
Submitter: Zuul
Branch:    stable/pike"
1704798,2017-07-19 08:54:23 UTC,"ok, maybe need some testing, I remember we can't create https in devstack env, can we ? or could you please help to verify if this change could solve the problem you mentioned?"
1704798,2017-07-18 12:35:55 UTC,"it's not what that conf section is for, but yeah, I like that idea. We should avoid creating more conf options than we have to, and the cert needed for this verify_project_id would always match the one needed in that section, so creating a new conf option would just be duplicating things unnecessarily."
1704798,2017-07-18 07:10:10 UTC,"we rely on this for nova to communicate with keystone, and this bug also occurs when nova api talking to keystone, so the cred should be able to be reused?"
1704798,2017-07-17 16:48:24 UTC,"this presumably also impacts POST /flavors/{flavor_id}/action with addTenantAccess or removeTenantAccess actions, since they also call verify_project_id. E.g.: https://github.com/openstack/nova/blob/4d552d6bf61955fa121feedbb4469f4ed0b07cff/nova/api/openstack/compute/flavor_access.py#L99"
1704798,2017-07-17 15:16:31 UTC,The problem is that https://github.com/openstack/nova/blob/f6fbfc7ff07b790ef052a759552c69429b3d79c7/nova/api/openstack/identity.py#L32 simply relies on the default for the Session constructor's verify argument (True). We need to provide a configuration option to allow an operator to specify verify=False and verify=<path>.
1704798,2017-07-19 09:30:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/485121"
1704803,2017-08-30 11:06:25 UTC,Hello Paulo!
1704808,2017-07-18 13:48:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704808,2017-07-18 13:51:14 UTC,"this is a major Wayland problem. Also GIMP color picker does not work
https://bugzilla.gnome.org/show_bug.cgi?id=780375"
1704808,2017-08-21 12:37:57 UTC,Thanks for your report.
1704819,2017-07-25 18:31:16 UTC,Noting for reference the int() issue has come up before with credit card payments: bug #1282751.
1704819,2017-08-03 19:10:57 UTC,Branch with fix pushed:
1704819,2018-02-07 17:25:48 UTC,Re-marking as confirmed based on Jessica's comments.
1704819,2018-04-26 18:26:00 UTC,We are also now running this patch in production.
1704819,2019-05-23 15:29:21 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1 on the strength of this having been run in production for a couple years and per discussion at http://irc.evergreen-ils.org/evergreen/2019-05-23#i_407072. Thanks, Bill!"
1704819,2017-12-20 21:18:04 UTC,We observed this behavior in our 2.12 system as well. We're running your patch. Thanks!
1704820,2017-07-18 20:51:55 UTC,"Hi Melvin. Which blocks are your concerned about? If you allow comments on files and notes, you will be able to provide feedback on them. Or do you also want to comment on blocks with external content, plans and the resume?"
1704820,2017-07-19 12:05:59 UTC,"Hi,"
1704820,2017-07-19 20:24:40 UTC,"Thanks for the confirmation, Melvin."
1704820,2017-07-20 12:09:23 UTC,"Hi Kristina,"
1704833,2017-12-29 14:49:03 UTC,"I updated the bug status to ""In Progress"" and clear the assignee because it just fixes the bug partially. It is also because we need to investigate which actions should be added to close this bug. The analysis is required to close the bug."
1704833,2017-12-28 16:46:37 UTC,"Reviewed:  https://review.openstack.org/527147
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=7d7de3b37f85c2cdf064d5eaafc133abc76b21e3
Submitter: Zuul
Branch:    master"
1704833,2017-12-29 16:39:11 UTC,"> Please update the description of the bug or open an new bug after the analysis in order to submit a new fix.
"
1704833,2017-12-29 15:00:27 UTC,Please update the description of the bug or open an new bug after the analysis in order to submit a new fix.
1704833,2017-12-11 16:15:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527147"
1704833,2018-01-26 00:31:40 UTC,This issue was fixed in the openstack/horizon 13.0.0.0b3 development milestone.
1704833,2017-12-11 16:05:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527142"
1704833,2017-12-11 16:07:06 UTC,"Change abandoned by Ahmed Zaid (<email address hidden>) on branch: master
Review: https://review.openstack.org/527142"
1704833,2017-12-05 10:50:27 UTC,Fix proposed: https://review.openstack.org/#/c/519600/
1704833,2017-12-11 15:00:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527114"
1704833,2017-12-29 15:09:39 UTC,"The bug description is unclear on which actions should be added and which actions are specific to ""Project Dashboard"".
We first need to investigate which actions should be added to close the bug."
1704833,2017-12-11 15:02:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527116"
1704833,2017-12-11 15:00:34 UTC,"Change abandoned by Ahmed Zaid (<email address hidden>) on branch: master
Review: https://review.openstack.org/527114"
1704833,2017-12-11 15:31:41 UTC,"Change abandoned by Ahmed Zaid (<email address hidden>) on branch: master
Review: https://review.openstack.org/519600"
1704833,2017-12-11 15:02:26 UTC,"Change abandoned by Ahmed Zaid (<email address hidden>) on branch: master
Review: https://review.openstack.org/527116"
1704838,2019-04-05 11:17:06 UTC,Please see Bug #1819002 .
1704838,2019-04-05 11:09:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704855,2017-11-14 19:05:35 UTC,Fixed in 0.8.4
1704855,2017-07-18 21:15:11 UTC,Fix is on branch bug1704855
1704857,2017-07-24 07:59:49 UTC,This bug was fixed in the package linux - 4.4.0-87.110
1704857,2017-07-19 15:11:53 UTC,Package already tested by Thadeu Cascardo.
1704857,2017-07-19 15:08:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1704857,2017-07-17 19:17:57 UTC,As reported here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670508/comments/19
1704857,2017-07-17 20:46:59 UTC,"Hi Cascardo,"
1704857,2017-07-17 19:28:01 UTC,[Impact]
1704857,2017-07-17 19:26:09 UTC,"Hi, Pavel."
1704857,2017-07-17 19:19:38 UTC,"Per report, relevant commits:"
1704857,2017-07-18 11:54:22 UTC,[Test Case]
1704858,2017-07-18 03:28:20 UTC,"Reviewed:  https://review.openstack.org/484375
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=c2e59b9b8b43e5846c0fe20cfd7810bbc0291cad
Submitter: Jenkins
Branch:    master"
1704859,2017-07-18 03:40:16 UTC,"That is your own personal test. I like it. Beside menu separator is necessary for long nested menus found in apllication like Gimp, Inkscape etc."
1704859,2017-10-31 15:24:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1704870,2017-03-27 11:32:33 UTC,"(In reply to Pierre Ossman from comment #21)

> Nice to see this progressing. :)
>
> Just a quick note, override redirect is the old way of fullscreen on X11 and
> a lot of well behaved applications ask the window manager instead. So I
> guess Xwayland may need support for both extensions depending on how well
> behaved the application is?
"
1704870,2017-03-27 14:11:10 UTC,It sounded like one of your (two) grab extensions was specifically for O-R windows? Fullscreen via EWMH should be able to make do using the other proposed Wayland extension.
1704870,2017-03-28 07:10:35 UTC,"(In reply to Pierre Ossman from comment #23)

> It sounded like one of your (two) grab extensions was specifically for O-R
> windows?
"
1704870,2017-03-28 07:33:19 UTC,"And to clear up any misunderstanding, there is nothing neither in the protocol nor in the sample implementation I made which is specific for O-R windows in any way, it's just that the protocols is necessary for O-R window *because* they aren't focused by X11 window managers."
1704870,2017-04-27 20:29:36 UTC,"Adding myself to the CC list, and while here, I should add, the situation is worse still if another layer of indirection is involved. If I run virt-viewer or virt-manager as a remote X client under Xwayland, no keyboard events at all make it to the VM."
1704870,2017-05-16 05:13:20 UTC,I have issues only when using virt-viewer/virt-manager over ssh (from Fedora25). Simple workaround is to install virt-manager on your host and add the other Qemu/KVM servers as a new connection. Did the magic for me.
1704870,2017-10-10 14:35:29 UTC,"Fixed with native Wayland apps, x11 fix pending review/merge."
1704870,2017-11-09 15:58:29 UTC,"(In reply to Christophe Fergeau from comment #30)

> (In reply to Matěj Cepl from comment #29)
> > I wonder whether it is the same bug, but I don’t have ANY keys inside of the
> > VM machine when virt-manager runs under Xsession. Is it?
>
> Could it be https://bugzilla.redhat.com/show_bug.cgi?id=1479682 ?
"
1704870,2017-11-09 15:32:31 UTC,"I wonder whether it is the same bug, but I don’t have ANY keys inside of the VM machine when virt-manager runs under Xsession. Is it?"
1704870,2017-11-09 15:40:40 UTC,"(In reply to Matěj Cepl from comment #29)

> I wonder whether it is the same bug, but I don’t have ANY keys inside of the
> VM machine when virt-manager runs under Xsession. Is it?
"
1704870,2017-11-14 22:38:38 UTC,It works for me after upgrading to Fedora 27 (gnome-boxes)
1704870,2020-04-16 22:11:18 UTC,I can confirm that this bug is still present using gnome with ubuntu 18.04.lts
1704870,2017-03-27 10:38:18 UTC,Nice to see this progressing. :)
1704870,2020-05-01 15:25:57 UTC,"> Is it low importance for Ubuntu because we can go back to XOrg?
"
1704870,2017-10-13 08:19:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704870,2020-04-30 19:32:45 UTC,"It still happens with remmina on Ubuntu 20.04.
Is it low importance for Ubuntu because we can go back to XOrg? It also means it is a blocker for wayland."
1704870,2017-03-23 14:21:53 UTC,https://lists.freedesktop.org/archives/wayland-devel/2017-March/033526.html
1704870,2015-11-26 13:01:11 UTC,"In virt-manager, I can't send Win key to the client, it always triggers overview mode in the host. That's probably caused by the same issue."
1704870,2015-11-26 12:24:27 UTC,"Applications such as vncviewer[1] have the option of grabbing the keyboard in order to be able to send all keyboard input to a remote system, even if the window manager would like to reserve some things for itself. This is no longer possible when these applications are running under XWayland."
1704870,2017-01-09 15:03:30 UTC,"Ugh, thanks. Wrong tracker."
1704870,2015-11-27 12:47:50 UTC,VirtualBox also suffers from this issue; it makes using my Windows 98 VM really painful.
1704870,2015-12-16 13:51:15 UTC,"I think this is pretty much the desired behaviour, Wayland was designed with security in mind an no Wayland client can grab the keyboard exclusively."
1704870,2015-12-17 09:54:30 UTC,"OK, so IIUIC, this issue should be moved to Wayland, it's not XWayland specific. Thanks for info, Olivier. Is there some solution being worked on or proposed, or is there nothing like that planned?"
1704870,2016-07-05 17:29:06 UTC,Hello.
1704870,2016-07-19 07:15:03 UTC,"According to [1] this bug is being handled upstream at freedesktop.org by wayland devs. They are adding protocol extensions to wayland:
https://cgit.freedesktop.org/wayland/wayland-protocols/tree/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml
https://cgit.freedesktop.org/wayland/wayland-protocols/tree/unstable/relative-pointer/relative-pointer-unstable-v1.xml"
1704870,2016-07-19 07:31:41 UTC,"Those references only covers grabbing the pointer, not the keyboard."
1704870,2016-07-21 15:37:49 UTC,"(In reply to Sean Young from comment #2)

> VirtualBox also suffers from this issue; it makes using my Windows 98 VM
> really painful.
"
1704870,2017-03-03 12:27:50 UTC,The same problem when using Remmina and VMware-view Horizon.
1704870,2016-08-13 16:20:57 UTC,I've filed an upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=97333
1704870,2016-09-01 07:02:56 UTC,"(In reply to Kamil Páral from comment #4)

> OK, so IIUIC, this issue should be moved to Wayland, it's not XWayland
> specific. Thanks for info, Olivier. Is there some solution being worked on
> or proposed, or is there nothing like that planned?
"
1704870,2016-11-24 13:45:32 UTC,"This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'."
1704870,2016-12-11 16:19:52 UTC,Just letting you know that this is still valid bug.
1704870,2016-12-30 16:27:34 UTC,"Similar experience after upgrading from 24 -> 25, the Remmina clipboard sync no longer works. I expect this has something to to with Wayland and the isolation of the windows, but have not yet looked into that."
1704870,2017-01-08 22:08:23 UTC,"I confirm this bug using the freerdp client to connect to Windows remote desktop session. All Windows keyboard shortcuts (alt-tab, Windows-e, etc. are not sent to the remote desktop but to the local host instead."
1704870,2017-01-09 13:10:03 UTC,"Thanks, no more confirmations are needed. We know this is simply not implemented yet. If you need this, please use the X11 session until this is fixed."
1704870,2017-01-09 14:48:54 UTC,I don't think that was the right gnome bug number. :)
1704870,2016-07-21 21:17:31 UTC,*** Bug 1353422 has been marked as a duplicate of this bug. ***
1704874,2017-08-28 06:25:35 UTC,"This may be have something to do with data integrity during power loss, do you have disabled all caches coupled with non-volatile stores?"
1704875,2017-07-28 07:40:26 UTC,This issue was fixed in the openstack/nova 16.0.0.0b3 development milestone.
1704875,2017-07-27 21:03:06 UTC,This issue was fixed in the openstack/cinder 11.0.0.0b3 development milestone.
1704875,2017-07-24 21:22:50 UTC,"Reviewed:  https://review.openstack.org/485322
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=229e660e30d4efd2c47d29c2eccb0c2282a98b0e
Submitter: Jenkins
Branch:    master"
1704875,2017-07-19 18:45:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/485322"
1704875,2017-07-17 21:58:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484501"
1704875,2017-07-20 03:46:05 UTC,"Reviewed:  https://review.openstack.org/484501
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=47528cd5c264870c059dfe85bfeb22548d6cb618
Submitter: Jenkins
Branch:    master"
1704876,2017-07-17 21:29:47 UTC,"@Eric,"
1704876,2017-07-17 21:40:11 UTC,"Hi Anastasia,"
1704876,2017-07-17 22:16:40 UTC,"@Eric,
I do not think so :) AFAIK, it's on the list of things to do..."
1704876,2017-07-18 04:43:15 UTC,"Thank you.  I've confirmed that in my case, I am able to target specific
subnets.  Here are example commands:"
1704876,2017-07-25 03:40:58 UTC,Triaging as High as we really need to address spaces and subnets CLI.
1704876,2017-12-08 03:38:09 UTC,Any update on this? Should at least have a note in the documentation that this isn't working or not have it at all (https://jujucharms.com/docs/2.3/network-spaces).
1704881,2017-07-18 02:34:55 UTC,"These default subnetpools should be deleted at [1]:
https://github.com/openstack/neutron/blob/master/neutron/tests/tempest/api/base.py#L180-L186"
1704883,2017-08-28 09:58:29 UTC,This issue was fixed in the openstack/heat 8.0.4 release.
1704883,2017-08-17 15:50:28 UTC,"Reviewed:  https://review.openstack.org/485218
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=30c6e532b30566506c0a1b15edcb3acce304f7e3
Submitter: Jenkins
Branch:    stable/ocata"
1704883,2017-07-19 14:18:19 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/485218"
1704883,2017-07-17 22:27:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/484513"
1704883,2017-07-28 18:57:06 UTC,This issue was fixed in the openstack/heat 9.0.0.0b3 development milestone.
1704883,2017-07-19 03:57:06 UTC,"Reviewed:  https://review.openstack.org/484513
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=02176a581193b4ab60ad31e847ae3dd5f544c96a
Submitter: Jenkins
Branch:    master"
1704884,2017-07-18 01:08:38 UTC,"I think the library is free of both libevent2 and libsqlite3. The former it certainly should be, it's just a question of whether libevent2 crept outside of the trust router code where I intended to confine it."
1704884,2017-07-18 00:48:50 UTC,"I'd recommend balancing minimizing dependencies against complicating the
build system."
1704890,2018-01-15 13:03:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1704890,2018-01-15 13:04:57 UTC,"Now version 1.3 is out since 2017-10-27, is there any plan to release 1.2 or 1.3 in 17.04 ?"
1704890,2018-06-29 17:02:29 UTC,there is now version 1.4 available
1704890,2018-08-27 10:26:20 UTC,This needs to be done as a higher priority and the kea-admin package also needs serious attention.
1704890,2018-10-03 09:52:15 UTC,I would also appreciate if you included kea-admin in version 1.1 (ubuntu 18.04) and upgrade the entire package to a newer version.
1704890,2019-10-27 09:39:45 UTC,"Kea 1.4.0.P1-3build1 is available in Ubuntu 19.04, so the general upgrade part of this issue is resolved."
1704893,2020-03-24 13:45:56 UTC,"Reading back through this thread just now makes me realize that I may have conflated two different bugs. My initial report was that Writer alone was not working, now I can't get any part of LibreOffice working."
1704893,2020-03-24 13:28:15 UTC,I have the same results after upgrading via the libroffice ppa
1704893,2018-10-10 13:07:10 UTC,"@Sondra: can you please try the following? From a terminal, run `libreoffice --writer --backtrace`."
1704893,2020-03-23 22:00:49 UTC,"The attached file is the result of running this command:
$ rm -Rf ~/.config/libreoffice; libreoffice --calc --backtrace; rm -Rf ~/.config/libreoffice; libreoffice --help --backtrace"
1704893,2018-05-08 04:17:25 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1704893,2018-01-16 18:01:07 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1704893,2018-03-08 13:24:44 UTC,@Sondra: is this problem still happening? Or have you managed to get libreoffice writer to start?
1704893,2018-01-17 07:21:22 UTC,"The JournalErrors.txt above have lot of ""xfce4-notifyd[6564]: Theme parsing error: gtk-widgets.css"""
1704893,2018-01-16 23:18:20 UTC,"I can reproduce this bug on Ubuntu 16.04.3 LTS and libreoffice-writer 1:5.1.6~rc2-0ubuntu1~xenial2.
Ubuntu 16.04.3 doesn't reach end of life until April 2021
https://wiki.ubuntu.com/Releases
https://www.ubuntu.com/info/release-end-of-life"
1704893,2018-09-25 22:08:19 UTC,"@Olivier Tilloy: I continue to experience this problem on various systems. It's been a while since I tested with fresh installations, and I _was_ preserving various ~/.config files between those. I did not, however, preserve anything in ~/.config/libreoffice, and removing this directory has no effect."
1704917,2017-07-18 05:08:26 UTC,"Thanks Fabrice,"
1704928,2019-12-20 11:07:50 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/486561
Reason: I'm going to assume this is stalled and should be picked up at a later date"
1704928,2017-07-24 10:48:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/486561"
1704928,2017-07-24 07:38:26 UTC,Based on SQLAlchemy doc [1] onupdate is not expected to be called during INSERT so not having update_at set in the first instance.update seem OK.
1704928,2017-07-21 15:52:55 UTC,Is it possible there is something stubbing out some behavior in these tests that's making it behave this way?
1704928,2017-07-18 17:18:10 UTC,The updated_at field is defined in the TimestampMixin in oslo.db and says it should change the value on every ONUPDATE trigger:
1704928,2017-07-18 08:17:56 UTC,"During the Third instance update when the model_query with update runs in the  sqlalchemy api the updated_at field magically updated.
https://github.com/openstack/nova/blob/57473088857014d7f46c17ffb3a476e09e0db30f/nova/db/sqlalchemy/api.py#L2741"
1704928,2017-07-18 06:32:00 UTC,* First instance.update sent here https://github.com/openstack/nova/blob/57473088857014d7f46c17ffb3a476e09e0db30f/nova/conductor/manager.py#L976
1704928,2017-07-22 03:19:18 UTC,"I checked the versioned notification contents with nova that applied the 'updated_at' patch [1] in my testing environment.
(nova master: commit b529c32ca0923b6b180d252306f4c39033d2cd43 with [1])"
1704929,2019-07-29 04:17:21 UTC,[Expired for console-setup (Ubuntu) because there has been no activity for 60 days.]
1704929,2018-01-31 12:34:42 UTC,I just did a pure bionic LPAR install using exclusively the 'Operating System Messages' tasks at the HMC and interestingly I did not came across a single ttyX message there.
1704929,2020-02-27 07:11:38 UTC,"Since disco these messages are no longer visible.
Hence closing this ticket."
1704929,2017-09-27 16:31:14 UTC,"------- Comment From <email address hidden> 2017-09-27 12:20 EDT-------
Will be covered by original Launchpad bug"
1704929,2017-09-25 14:23:25 UTC,I'm seeing this installing 17.10 on s390x also.
1704929,2018-01-25 15:20:10 UTC,"------- Comment From <email address hidden> 2018-01-25 10:12 EDT-------
(In reply to comment #4)

> During the installation (z/VM guest and KVM virtual machine) of Ubuntu
> Server 16.04.1 (and 16.04.2) repeating messages of the form:
>
> ""
> Select and install software ... 10% can't open /dev/tty4: No such device or
> address
> can't open /dev/tty2: No such device or address
> can't open /dev/tty3: No such device or address
> can't open /dev/tty4: No such device or address
"
1704929,2019-05-29 07:27:31 UTC,"Since this only seems to happen with xenial, and not with any other Ubuntu release (Y to E) and since it only happens during install time, and even then only with using the console for the entire installation (and not using the 2nd stage via ssh), I closing this as Won't Fix."
1704929,2017-09-27 16:00:16 UTC,"/dev/tty1 file exists on s390x ubuntu, however, one cannot open that file doing that results in ENXIO."
1704929,2017-09-27 16:08:14 UTC,Reverse proxy initiated ...
1704946,2017-07-19 16:48:58 UTC,The actual error is:
1704961,2017-07-28 07:38:25 UTC,"4.10.0-29.33 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1704961,2017-08-03 08:27:59 UTC,Hardware Certification have begun testing this -proposed kernel.
1704961,2017-08-03 11:08:52 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/zesty/4.10.0-29.33/zesty-proposed-published.html"
1704961,2017-08-03 16:29:32 UTC,This bug was fixed in the package linux - 4.10.0-30.34
1704966,2017-08-03 08:27:08 UTC,Hardware Certification have begun testing this -proposed kernel.
1704966,2017-08-03 12:55:20 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.10.0-1012.15/raspi2-4.10-proposed-published.html"
1704966,2017-08-03 16:30:24 UTC,This bug was fixed in the package linux-raspi2 - 4.10.0-1013.16
1704984,2017-07-18 11:15:29 UTC,"Well, I guess this is bug.
User tries to send not allowed content, but message can't be generated... :-("
1704984,2017-07-18 11:20:03 UTC,"btw, if attached file with prohibited content is named in UTF-8 (let's say Тест.exe) , then  I hit this bug."
1704984,2017-07-18 13:20:55 UTC,As temporary workaround I changed
1704993,2019-09-19 14:48:54 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1704995,2017-08-07 07:00:47 UTC,The package has been published and the bug is being set to Fix Released
1704995,2017-08-01 06:37:52 UTC,Cert does not maintain precise anymore. Set cert-test as invalid.
1704995,2017-08-02 15:27:39 UTC,No ADT testing available for ESM PPAs.
1704996,2017-07-20 07:14:00 UTC,No ADT testing available for ESM PPAs.
1704996,2017-08-04 08:02:15 UTC,The package has been published and the bug is being set to Fix Released
1704996,2017-07-20 07:15:00 UTC,No bugs to be verified.
1704996,2017-07-26 11:23:55 UTC,Cert does not maintain precise anymore. Set cert-test as invalid.
1704996,2017-07-28 07:42:16 UTC,No image available for MaaS server.
1705003,2017-07-21 02:35:38 UTC,No bug was tagged with verification needed this time.
1705003,2017-07-21 09:33:55 UTC,"Image removed from MaaS, skipping this for the current cycle."
1705003,2017-07-26 11:23:02 UTC,Cert does not maintain vivid anymore. Set cert-test as invalid.
1705003,2017-08-10 21:00:35 UTC,This bug was fixed in the package linux - 3.19.0-91.99
1705003,2021-01-07 08:45:03 UTC,3.19 EOL
1705012,2019-12-04 08:53:43 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/577156
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1705012,2019-12-04 08:53:34 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1705012,2019-12-04 08:42:06 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/577153
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1705012,2019-12-04 08:41:55 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1705012,2019-11-22 15:23:48 UTC,"Hello All,"
1705012,2018-06-13 13:15:43 UTC,"Actually, for Pike, it will not be enough to revert https://review.openstack.org/#/c/441231/, we also need to revert https://review.openstack.org/#/c/441231, which is an update of the previous one."
1705012,2018-06-21 13:10:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/577153"
1705012,2018-06-21 13:19:12 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/577156"
1705012,2017-07-28 00:23:20 UTC,"@Sean,"
1705012,2017-07-28 09:56:14 UTC,I confirmed the symptom seen in bug 1700448 was fixed
1705012,2017-07-18 11:11:14 UTC,My initial investigation reveals that this started acting up in nova/stable/newton only after this following neutron patch was backported to neutron/stable/newton: https://review.openstack.org/#/c/470297/
1705012,2017-07-24 21:31:47 UTC,Something must be different about how the vmware driver is doing port binding. I need someone with VMware expertise to take a look at this.
1705012,2018-06-07 09:22:48 UTC,"This issue has been fixed in Newton, but it's still reproducible in Pike. The simplest solution would be to revert https://review.openstack.org/#/c/441231/ from Pike the same way that https://review.openstack.org/#/c/470297/ was reverted in Newton. Kevin, do you agree with my assessment ?"
1705012,2017-07-25 06:07:03 UTC,Please also see https://bugs.launchpad.net/networking-midonet/+bug/1700448
1705012,2017-07-27 18:26:44 UTC,Fixed in https://review.openstack.org/#/c/486867/
1705012,2017-07-25 05:06:06 UTC,"Hi,
Can you please let us know which neutron plugin you are using? If this is the ML2 plugin then which drivers?
Thanks
Gary"
1705012,2017-07-25 08:35:20 UTC,"My setup is using the ml2 plugin, with both vmware_dvs and openvswitch mechanism drivers enabled. This is the ml2 section of my ml2_conf.ini:"
1705013,2017-08-02 12:45:43 UTC,"Related bug, that has been fixed: https://bugs.launchpad.net/horizon/+bug/1675788"
1705015,2017-07-20 06:47:15 UTC,"The problem has been fixed. It is the conflict between TLP and bumblebee that causes the problem. Although I had included PCI ""01:00.00"" in tlp's pci blacklist, tlp still holds the control of nvidia graphic card's power management."
1705015,2018-02-08 23:00:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705016,2017-07-18 12:00:47 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 __GI_abort () at abort.c:89
 QMessageLogger::fatal(char const*, ...) const () from /tmp/apport_sandbox_6SPsCS/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QSGRenderLoop::handleContextCreationFailure (this=this@entry=0x55a701025fc0, window=0x55a701026040, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:264
 QSGThreadedRenderLoop::handleExposure (this=this@entry=0x55a701025fc0, window=window@entry=0x55a701026040) at scenegraph/qsgthreadedrenderloop.cpp:952"
1705016,2017-07-27 16:27:57 UTC,"I've subscribed Simon Quigley, Kubuntu member, in hopes that he can take a look at this crash and determine if it has a security relevance."
1705016,2017-07-28 18:50:21 UTC,This trace looks similar to the one in https://bugreports.qt.io/browse/QTBUG-48987
1705016,2017-07-28 19:04:52 UTC,Comment #2 I meant.
1705016,2017-10-05 21:02:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705016,2017-07-28 19:02:18 UTC,Maybe similar to the trace in attachment in comment #1 of? https://bugs.kde.org/show_bug.cgi?id=366156
1705032,2017-07-20 06:33:04 UTC,Some additional observations regarding this bug:
1705034,2017-07-18 14:45:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705043,2018-01-20 07:40:22 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-791
1705045,2019-03-27 13:13:24 UTC,Goutham has this been added to the upstream documentation? Thanks!
1705045,2020-08-06 20:51:09 UTC,"API reference was updated here: https://review.opendev.org/#/c/492817/ but still miss some details on access rules retrieve and list operations.
Developer guide was updated here: https://review.opendev.org/#/c/416870/
Admin guide was treated in a different LP: https://bugs.launchpad.net/manila/+bug/1707005 and proposed here: https://review.opendev.org/#/c/529904/"
1705045,2020-08-06 21:16:47 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/745232"
1705045,2020-09-10 17:44:43 UTC,"Reviewed:  https://review.opendev.org/745232
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=56a6b39aa045d15f96fbd3afc62ebc77e24b3740
Submitter: Zuul
Branch:    master"
1705058,2017-11-14 10:59:52 UTC,This can be fixed by removing ~/.treeline-1.4
1705064,2020-03-11 19:57:41 UTC,"Regardless, it'd be great for this to make it into the LTS release, but I don't know how to make that happen. It might also be too late, but I hope not."
1705064,2020-03-11 19:46:36 UTC,"nevermind my previous comment #9, wrong bug ..."
1705064,2020-03-09 10:32:32 UTC,"Don't know if someone should mark as fix committed in this case, seeing as there are fixes out there."
1705064,2020-03-09 10:31:59 UTC,"Also works for me. In my case, I ran the binary on Ubuntu 18.04 because that's what my real hardware is using."
1705064,2020-03-11 19:26:01 UTC,"Focal still has lshw 02.18.85-0.3ubuntu1, I don't see 02.18.85-0.3ubuntu2 in proposed,"
1705064,2020-03-07 13:41:37 UTC,per check fedora repo. I think the patch used in fedora should be the same as the one mentioned in #1. [1] vs [2]
1705064,2020-03-09 08:13:29 UTC,I upload 02.18.85-0.3ubuntu2~p1 (focal) to https://launchpad.net/~ycheng-twn/+archive/ubuntu/lshw and it works for me.
1705064,2019-10-27 13:56:01 UTC,"ppa for testing: https://launchpad.net/~ycheng-twn/+archive/ubuntu/lshw
TODO: change log need refine (might need to refine in patch file)"
1705064,2019-10-27 05:59:46 UTC,we need https://github.com/lyonel/lshw/pull/45
1705064,2020-03-05 16:30:51 UTC,Note that Fedora has patches in https://koji.fedoraproject.org/koji/buildinfo?buildID=1329140 that fix the NVME issue - maybe these could be used in the Ubuntu package builds too?
1705064,2020-03-05 16:28:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705066,2017-07-19 22:56:50 UTC,We ship a python-only version of rencode with Deluge so the rencode cython version must have an issue.
1705066,2017-07-20 03:33:53 UTC,"I have opened an issue, but given that upstream is already at 1.0.5 I do not hold my breath ..."
1705066,2019-06-28 16:28:04 UTC,It still fails using the most recent packages.
1705069,2017-07-26 13:30:11 UTC,This issue was fixed in the openstack/python-senlinclient 1.4.0 release.
1705095,2018-04-20 13:26:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705099,2017-07-18 21:53:21 UTC,"It works beautifully, I've updated the kernel.org bug."
1705099,2017-07-21 16:23:55 UTC,"Is CONFIG_ALLOW_DEV_COREDUMP = Y in this kernel ?
Trying to supply info to https://bugzilla.kernel.org/show_bug.cgi?id=196411 now.. :)"
1705099,2017-07-21 16:53:20 UTC,Yes tha value is set:
1705099,2017-07-21 19:03:45 UTC,Oh ok thanks.
1705099,2017-07-26 21:35:05 UTC,Any idea why I can't get a device coredump? (Discussion in https://bugzilla.kernel.org/show_bug.cgi?id=196411)
1705099,2017-07-31 06:22:09 UTC,"Thanks for the help, as for a third kernel bug being hunted down (https://bugzilla.kernel.org/show_bug.cgi?id=196415), would it be possible to get a 4.13-rc3 kernel with CONFIG_ACPI_DEBUG turned on?"
1705099,2017-08-10 15:23:07 UTC,"Sorry for the delay.  It might be best to open a new bug, that way they can be tracked separately."
1705099,2017-07-18 20:42:51 UTC,I built a 4.13-rc1 based test kernel with the patch. It can be downloaded from:
1705103,2017-11-26 12:09:51 UTC,"Hi,"
1705107,2017-07-20 12:45:30 UTC,Tags: kernel-fixed-upstream
1705107,2017-07-18 20:00:07 UTC,This change was made by a bot.
1705107,2017-07-19 20:35:10 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1705108,2017-07-18 20:54:57 UTC,"Well, I hoped you'd read the whole comment I posted and follow the link I provided."
1705108,2017-07-18 22:42:58 UTC,"The problem is that one often has to wait a long long time to be approved for the ~ubuntu-wiki-editors team (I had to wait), while the wiki page says ""a confirmation email will be sent in approximately 1-7 days"". Have a look now, 49 applicants pending going back many months, and the last one approved was about 8 days ago (admittedly, probably only 2 of the 4 applications since then should be approved, and both of those applications are only hours old)."
1705108,2017-07-19 03:39:29 UTC,"Thank you for taking the time to explain the process, that is helpful. The first 2 bugs just came across my email as closed / invalid without explanation."
1705109,2017-08-01 07:40:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705117,2017-07-19 00:22:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1705117,2017-07-19 10:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1705117,2017-07-19 14:57:57 UTC,"Can't write any logs, system freeze during the boot ..."
1705117,2017-07-20 13:54:10 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1705117,2017-07-20 16:39:12 UTC,"Thanks, the latest rc kernel is ok."
1705117,2017-07-21 18:08:33 UTC,"I'd like to perform a reverse bisect to figure out which commit upstream fixes this regression. It would be very helpful to know the last kernel that had this issue and the first kernel that did not.
Can you test the following kernels and report back? We are looking for the last kernel version that has the bug and the first that does not:"
1705117,2017-07-22 13:36:47 UTC,"I'll let you know as soon as I will perform tests, I can't do them in
the next days."
1705118,2017-12-15 06:33:22 UTC,"I confirm that in qemu-2.11, the ppc and s390x cases are fixed, however the sparc64 case is still failing:"
1705118,2017-12-15 15:08:16 UTC,"I don't suppose anybody's going to get round to implementing RT signals for SPARC any time soon, so let's retitle this bug to track the one remaining issue."
1705118,2017-11-06 17:53:12 UTC,"...and also
 * SPARC doesn't implement setup_rt_frame(), so it can't deliver RT signals at all.
That's a bigger missing feature than the rest."
1705118,2017-11-06 17:33:10 UTC,"This is an interesting collection of different bugs:
 * s390x is missing masking operations, as you describe
 * ppc is passing the PC of the offending insn, not the data address, into si_addr
 * sparc fails to record the address of a data fault and so passes 0 into si_addr
 * sparc also isn't implementing rt_sigaction correctly and so the calls in your test program fail EINVAL (your test program doesn't check the return value from sigaction, so it ploughs ahead and makes the faulting data access with the SIG_DFL behaviour for SEGV, hence the uncaught SEGV)."
1705118,2017-08-31 22:10:50 UTC,The behaviour in qemu-2.10 is the same as in qemu-2.9.
1705118,2017-11-06 19:01:43 UTC,"Patchset that fixes all the minor parts of this, leaving (probably) just sparc setup_rt_frame/rt_sigreturn:
https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg00833.html"
1705129,2017-07-25 02:09:40 UTC,"I think this bug is valid. But if in doubt, ask design."
1705138,2017-07-20 18:46:33 UTC,"Hi Simohe,"
1705138,2018-08-15 09:24:16 UTC,Normally the output is there after 0.2 seconds latest. This is fine of course.
1705142,2018-05-09 15:34:08 UTC,"According to logstash this is still happening, although not very often."
1705142,2017-07-19 00:32:28 UTC,I guess this is due to:
1705143,2017-07-18 23:55:04 UTC,*** This is an automated message ***
1705145,2017-07-27 16:22:27 UTC,Hello and thanks for the bug report. We've previously triaged this issue in the Ubuntu CVE Tracker:
1705146,2017-07-19 00:37:27 UTC,"StacktraceTop:
 __libc_message (do_abort=2, fmt=fmt@entry=0x7f7ca6ab3e98 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=0x7f7ca6ce7b20 <main_arena>, ptr=0x5405f00, str=0x7f7ca6ab0c35 ""corrupted size vs. prev_size"", action=3) at malloc.c:5006
 _int_free (av=0x7f7ca6ce7b20 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4014
 __GI___libc_free (mem=<optimized out>) at malloc.c:2968
 js::LifoAlloc::freeAll() () from /tmp/apport_sandbox_ejtQWW/usr/lib/x86_64-linux-gnu/libmozjs-24.so.0"
1705146,2017-07-19 02:25:12 UTC,"This looks similar to:
https://errors.ubuntu.com/problem/340939a3ba20443aa76b3360e7c0f1f70b6a5bff"
1705146,2017-07-19 02:38:58 UTC,"Thanks, however, I can't access the link you provided."
1705146,2017-07-19 02:53:17 UTC,I didn't even notice I'd put the release twice. Here's the gnome-shell info:
1705146,2017-07-19 03:36:36 UTC,The link in comment #6 requires you to login to view. However I don't know if access is restricted to less than those with Launchpad accounts.
1705146,2017-11-01 01:32:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705146,2017-11-01 01:55:12 UTC,I just got this same crash during a window switch (Activities Overview) in GNOME. The desktop completely freezes (input devices continue to work).
1705146,2017-11-01 01:59:06 UTC,And the gnome-shell info (which matches post #8)
1705146,2017-12-08 22:17:11 UTC,Happened just now as Firefox was being updated thru software updater.
1705146,2020-06-18 05:42:34 UTC,"Gnome Shell on 16.04 is not supported by Ubuntu. Please upgrade to 20.04, or at least 18.04 and continue to report any problems you find."
1705151,2018-01-25 09:12:35 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1109
1705151,2017-08-29 21:13:49 UTC,"Workaround from the upstream bug report: 'And if use `XA PREPARE` (not use `ONE PHASE`), replication error not occurs."""
1705151,2017-07-19 07:20:38 UTC,"Jaime, please use ""Target to Series"" and set individual statuses for series"
1705151,2017-10-02 12:40:10 UTC,Upstream bug fixed in 8.0.4 and 5.7.21
1705163,2017-08-07 08:26:52 UTC,Can not repro on master.
1705169,2017-08-16 16:33:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1705169,2017-08-16 16:35:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1705169,2017-08-28 10:14:02 UTC,This bug was fixed in the package linux - 4.4.0-93.116
1705169,2017-08-28 10:14:27 UTC,This bug was fixed in the package linux - 4.10.0-33.37
1705169,2017-07-19 05:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1705169,2017-07-26 15:57:57 UTC,"This bug was nominated against a series that is no longer supported, ie yakkety.  The bug task representing the yakkety nomination is being closed as Won't Fix."
1705179,2017-08-07 18:11:48 UTC,"Looks similar to bug 1700416, except that you see the crash at a different time. Nevertheless, the workaround from bug 1700416 should help here too."
1705179,2017-07-19 06:09:15 UTC,I had a similar error occur if I hit (inheret) for the last item as well.. so that's why this time I hit the F there to save them.
1705188,2017-07-19 08:10:31 UTC,Thanks for reporting!
1705188,2017-08-07 11:51:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705188,2017-08-07 11:54:10 UTC,The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=780375
1705188,2018-05-07 18:56:01 UTC,Still same problem with Gimp 2.10 in Ubuntu Cosmic 18.10
1705188,2018-10-05 15:10:09 UTC,The upstream bug was migrated to Gitlab. The link to the gitlab bug is https://gitlab.gnome.org/GNOME/gimp/issues/1074 now.
1705207,2017-07-25 07:52:26 UTC,"Review in progress for https://review.opencontrail.org/33981
Submitter: Vinay Vithal Mahuli (<email address hidden>)"
1705207,2017-07-26 14:57:25 UTC,"Reviewed:  https://review.opencontrail.org/33981
Committed: http://github.com/Juniper/contrail-packaging/commit/0595fae45c96795b4e303dd679e6fc1fad66f5d7
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1705211,2018-01-20 07:38:37 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1454
1705212,2019-09-19 11:53:28 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1705212,2018-09-10 20:16:54 UTC,**This is an automated message**
1705212,2017-07-19 11:58:42 UTC,"Hi There,"
1705212,2017-07-25 06:20:52 UTC,"OK more details:
 - My Deploy & Commission kernels are set to 16.04 (GA kernel) in settings
 - Releasing a machine deployed as xenial machine works
 - Releasing a machine deployed as trusty fails, trying to boot xenial but under the hwe-t directory"
1705212,2017-07-25 05:58:21 UTC,"I am hitting this issue on MAAS 2.2 only when ""disk erasing"".  It tries to boot from ubuntu/amd64/hwe-t/xenial/daily/boot-kernel."
1705212,2017-07-20 02:18:53 UTC,"Hi,"
1705212,2018-07-26 21:38:06 UTC,"Hello guys, I'm using MAAS version: 2.3.0 (6434-gd354690-0ubuntu1~16.04.1) and I'm facing the same problem here, I have to run this command to use the node ""cd /var/lib/maas/boot-resources/current/ubuntu/amd64/hwe-t ; ln -s trusty xenial"""
1705216,2017-12-19 23:13:57 UTC,"Running into this as well. Using yaql to get the length of a list and I get the same receiver for None error. What is interesting is when I instead used yaql to check if the data is a list, it returns true."
1705217,2017-07-19 13:25:48 UTC,"This should be safe to do as 2) by putting a commit on the orphan master branch, where you stay after the nofetch/nopush import."
1705217,2017-07-19 13:56:21 UTC,Thank you for the report!
1705217,2017-07-19 16:59:13 UTC,"On Wed, Jul 19, 2017 at 3:56 PM, Robie Basak <email address hidden> wrote:

> Thank you for the report!
>
> On Wed, Jul 19, 2017 at 08:57:12AM -0000, Konrad Zapałowicz wrote:
>> 1) for case mentioned above print short informational msg on the console
>> that would describe the current state and give insights on how to move
>> forward. kind-of a very quick start guide.
>
> I favour this option, as I'd prefer the result inside the git repository
> to be exactly the same between the push and no-push modes.
"
1705217,2017-07-19 17:12:34 UTC,"On Wed, Jul 19, 2017 at 04:59:13PM -0000, Nish Aravamudan wrote:

> I wonder if in the --no-push case, it would be sufficient to checkout
> a local branch to ubuntu/devel from namespace/importer/ubuntu/devel
> and leave the repo in that state.
"
1705217,2017-07-20 07:44:12 UTC,"@Robie, @Nish, I think it will be acceptable."
1705217,2017-07-20 08:36:02 UTC,There's a TAOUP principle that commands should be silently successful and only noisy on failure. Otherwise scripts become extremely noisy. And a familiar user loses the value of backscroll because it's too noisy too. So there's a balance that needs to be struck I think.
1705217,2017-07-20 08:36:22 UTC,"(also, being noisy hides errors)"
1705217,2017-07-21 07:13:22 UTC,Good point. However I have been thinking just about this part:
1705218,2017-10-25 06:24:50 UTC,But it works on ubuntu 16.04 by creating the service definition?
1705218,2017-10-24 14:18:57 UTC,The patch is not released for Ubuntu. Cause it still does not work in Ubuntu.
1705218,2017-08-15 15:51:24 UTC,"Adding Mhall in the loop as the package maintenar for this package is ""ubuntu-devel-discuss"" and being one of the owner of the list.
Please note - this is a security issue , but I did not find a way to raise flag for the same after filling the bug."
1705218,2017-07-19 09:08:17 UTC,Please assign this to branch Trusty (14.04)
1705218,2017-08-15 21:24:09 UTC,https://launchpad.net/ubuntu/+source/fwsnort/1.6.7-3
1705218,2017-08-15 15:13:57 UTC,"This bug affects another user as well hence changing the status to ""confirmed""."
1705222,2017-07-27 16:16:29 UTC,@Alberto I've subscribed you so that you can have a look. The amount of attachments to this bug (especially nvidia-bug-report.log.gz) makes me uneasy about making the bug public. I figure you're more familiar with these attachments and will either know if they're safe to make public or you'll be able to quickly triage this bug. Thanks!
1705222,2017-08-18 11:47:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1705222,2017-08-21 08:52:11 UTC,It looks like a distro upgrade issue. Nothing security related.
1705227,2017-08-17 14:56:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705229,2017-07-19 10:06:04 UTC,Tested on Percona server 5.6.36
1705229,2017-08-02 12:07:47 UTC,Thank you for the reasonable feature request.
1705229,2018-01-25 09:05:52 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1811
1705237,2017-07-20 08:51:38 UTC,"The fix in that new version is actually supposed to fix just one kind of such an issue.
    * Fix an upgrade error when JAVA_OPTS in /etc/default/tomcat8
      contains the '%' character (LP: #1666570)."
1705237,2020-07-17 05:59:44 UTC,"Tomcat 8.0 is no longer relevant, I'm closing this."
1705239,2017-07-19 11:33:36 UTC,"Probably related to this bug is that after mysql is restarted and you get error with table missing and actually try dropping table - mysql removes metadata (*.frm file) but leaves innodb (*.ibd) behind and from then on you cannot create table with missing table name anymore or do anything with it without risking mysql crash:
```
test> create table a(id varchar(1) character set utf8, primary key(id));
test> create table b(id varchar(1) character set utf8, b_id varchar(1) character set utf8, primary key(id), CONSTRAINT a_fkey FOREIGN KEY (b_id) REFERENCES a (id));
test> alter table a modify column id varchar(1) character set utf8mb4;
ERROR 1833 (HY000): Cannot change column 'id': used in a foreign key constraint 'a_fkey' of table 'test.b'
test> set foreign_key_checks=0;
test> alter table a modify column id varchar(1) character set utf8mb4;
service mysql restart
test> select * from b;
ERROR 1146 (42S02): Table 'test.b' doesn't exist
test> root@perconatraindb03-sjc1 test5> drop table b;
ERROR 1051 (42S02): Unknown table 'test.b'"
1705239,2017-08-01 09:32:45 UTC,"Verified as described with vanilla mysql 5.6 & 5.7, percona server 5.5, 5.6.,5.7
The issue is not reproduced with mysql 8.0.2."
1705239,2018-01-25 09:18:10 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1110
1705240,2020-07-04 15:32:49 UTC,Thanks for reporting.
1705240,2017-07-19 11:08:14 UTC,Using packaging here
1705240,2017-07-19 12:23:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705259,2017-07-19 17:14:53 UTC,For sensible please note we also deploy an I-tables firewall on the interface which connect to mgmt.
1705259,2017-08-05 00:44:46 UTC,A few comments:
1705259,2017-08-06 18:59:05 UTC,Is this a duplicate of: https://bugs.launchpad.net/octavia/+bug/1549297 ?
1705270,2017-07-28 07:24:32 UTC,Hardware Certification have begun testing this -proposed kernel.
1705270,2017-08-03 15:39:57 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-88.111/xenial-proposed-published.html"
1705270,2017-08-03 16:32:17 UTC,This bug was fixed in the package linux - 4.4.0-89.112
1705273,2017-08-03 08:27:20 UTC,Hardware Certification have begun testing this -proposed kernel.
1705273,2017-08-03 13:27:24 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1066.74/raspi2-4.4-proposed-published.html"
1705273,2017-08-03 16:33:25 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1067.75
1705274,2017-08-03 08:27:33 UTC,Hardware Certification have begun testing this -proposed kernel.
1705274,2017-08-03 16:33:36 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1069.74
1705275,2017-07-31 07:13:01 UTC,"Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1705275,2017-08-03 16:32:49 UTC,This bug was fixed in the package linux-aws - 4.4.0-1028.37
1705276,2017-07-31 08:39:08 UTC,"4.4.0-1023.23 - gke
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1705276,2017-08-03 16:32:56 UTC,This bug was fixed in the package linux-gke - 4.4.0-1024.24
1705286,2017-07-20 15:12:18 UTC,"Galen, I think either there's a bug in that grid or I am just not able to find where/how the provider.get() refresh code is getting called twice."
1705287,2017-07-19 15:29:48 UTC,"StacktraceTop:
 gd_tagged_entry_remove_tag (self=0x0, tag=0x0) at libgd/gd-tagged-entry.c:1084
 update_entry_tag (frame=0x58a8720) at gedit/gedit-view-frame.c:656
 update_entry_tag_idle_cb (frame=0x58a8720) at gedit/gedit-view-frame.c:686
 g_main_context_dispatch () from /tmp/apport_sandbox_s4igHq/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iterate.isra () from /tmp/apport_sandbox_s4igHq/lib/x86_64-linux-gnu/libglib-2.0.so.0"
1705287,2017-07-19 16:16:46 UTC,Eyeballed the attachments and cannot see anything sensitive in them.  Making this public instead of private.
1705293,2020-08-26 09:09:05 UTC,Fix commited upstream
1705302,2020-07-23 14:02:56 UTC,"Committed to master, rel_3_5, and rel_3_4. Thanks, Mike and Terran!"
1705302,2020-02-19 22:17:04 UTC,"I can confirm what Jessica reported. The branch in comment 2 fixed the format so it references the curly braces now, but the branch in comment 4 lost that fix and fixed the HTML/Macro part."
1705302,2020-02-19 21:58:39 UTC,It looks to me like the description is still referring to the way receipts used to work in XUL. I think it's meant to read this way (for example):
1705302,2020-02-21 15:39:44 UTC,"Thanks, Mike - looks good! My sign off at:"
1705302,2019-12-19 20:06:57 UTC,"I pushed a branch with the text adjustment.  I have not been able to visually confirm my changes are showing up.  I'm having difficulties figuring out where the text in question is in the UI.  I searched all through the Work station admin section and within ""Print Templates"" with no luck so far."
1705302,2019-12-19 22:36:49 UTC,Update:  Found out how where this text lives and was able to confirm the changes are there.  We're good to go!
1705302,2017-07-19 18:04:58 UTC,I changed the Importance from Wishlist to Low since presenting incorrect information is a bug that will need to be fixed. I think it should be changed beginning with 3.0.
1705302,2020-02-20 18:17:17 UTC,"Terran, I just did this.  Changes in branches 2 & 4 are both here now:"
1705302,2019-11-20 20:51:43 UTC,"The New Devs Working Group tested this patch and it does work well, except HTML and Macros no longer work in the web client, so it should just be read 'Text to be inserted into Print Templates in place of ...'"
1705302,2019-06-11 17:07:37 UTC,"I've pushed a branch here:
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mrisher/lp1705302-update-template-description"
1705310,2017-07-20 08:43:47 UTC,"Fix proposed to branch: stable/8.0
Review: https://review.openstack.org/485494"
1705310,2017-07-20 16:35:51 UTC,This issue was already solved for stable/mitaka branch. Closing as Invalid.
1705310,2017-08-03 08:27:53 UTC,"Reviewed:  https://review.openstack.org/485494
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=77bd52b07a918154b583420e459b86731df0a155
Submitter: Jenkins
Branch:    stable/8.0"
1705321,2017-07-20 05:33:56 UTC,https://review.openstack.org/#/c/485295/
1705321,2017-07-26 13:30:10 UTC,This issue was fixed in the openstack/python-senlinclient 1.4.0 release.
1705323,2017-07-19 21:51:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1705323,2017-07-20 17:16:27 UTC,"Upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=785180"
1705323,2017-07-20 17:37:53 UTC,Thanks
1705332,2019-08-06 20:50:06 UTC,Attempting to kick this along a bit further.
1705332,2017-08-01 15:53:46 UTC,"Just to contradict myself, I not opposed to adding a default of now in the database. I just think a null would be better for pre-existing ones, but if all of the upgraded ones have the same date, that would be a similar, though less obvious, clue."
1705332,2017-08-01 15:30:34 UTC,"For my last comment, I'm not defending the Alamo, just offering my preference.  It's a great feature either way.  Don't let me hold it up.  Big ++ to documenting example queries."
1705332,2017-07-28 17:48:08 UTC,"-1 for me, nestled under my coder's hat."
1705332,2017-07-28 15:55:56 UTC,+1 from me
1705332,2017-07-28 15:33:44 UTC,"That works for me, but go with the consensus if everyone else disagrees with me about guessing for defaults."
1705332,2017-07-27 14:47:02 UTC,"I'll second the concern about using auditor data as the default option, since it's not uncommon to purge data from auditor tables to keep the size in check.  Plus, if they're big enough, it can significantly slow down the upgrade.  Of the alternate options, I prefer a canned date (a la Bill O's deployment) to creating a partially accurate data set."
1705332,2017-07-27 15:31:21 UTC,I say let the field be null and don't set any dates. That way we're not lying at all.
1705332,2017-07-27 15:24:29 UTC,I did essentially leave the values NULL when we implemented the changes. The values were simply populated by the table definition:
1705332,2017-07-27 15:13:39 UTC,"ISTM that the main benefit of a preordained date is that it's a signal to staff that, for a given barcode, we don't know when it was created.  Since, in the ""all barcodes"" UI, staff will be looking at the set of barcodes for exactly one user, I think having the same date for all the barcodes conveys, in context, the same signal.  So, how about just using the create date for the user on all historical barcodes, and then we have, at least, accurate data on the first?  The benefit would be that reports could reliably use the card as a proxy for the user, where useful."
1705332,2017-07-27 13:59:58 UTC,"We didn't try to do anything special. For us, the epoch of all pre-existing cards became the time/date of implementing the feature (2010-12-16 22:10:04), and the ""creator"" was the actor.id 1.  We've just come to know that any card with this create_date was created prior to that time."
1705332,2017-07-19 19:31:35 UTC,"Here at GRPL, we've had a local customization for this for years. Here's a look at the commit against 2.10. I've also added changes to the Web client under 2.11, but I don't have those in a public repository yet."
1705332,2017-07-28 14:26:37 UTC,So how about for a plan:
1705332,2017-07-27 13:42:11 UTC,"Bill, thank you for sharing this.  How did you handle the initial switch over?  How did you fill in the values for barcodes already created when you enabled this feature?"
1705337,2017-07-24 08:06:55 UTC,"I've lowered the max number of retries in charmhelpers, so this should be much less of a problem now (once the next charm-helpers release is made)"
1705337,2017-07-19 23:19:34 UTC,"Speaking of invoked during update-status hooks, any chance the apt layer can be updated to do nothing on update-status?"
1705337,2017-07-20 05:32:13 UTC,Some of this behaviour comes from charmhelpers. I think sorting this properly involves pulling some or all of this code into the apt layer where we can control things better
1705337,2017-07-20 05:30:51 UTC,"@hloeung Certainly, but that would be a separate bug rather than derailing this one with unrelated discussion :)"
1705346,2017-07-19 21:57:29 UTC,Can you please collect the config drive that was used ?
1705346,2017-07-19 22:37:27 UTC,This is the config driver used on this tests.
1705346,2017-07-20 13:56:14 UTC,"Thiago, thanks for attaching the config drive."
1705346,2017-07-20 18:29:25 UTC,"Hmm... So, do you think that this is an OpenStack Nova bug instead?"
1705346,2018-09-13 19:41:00 UTC,I said 'clearly wrong' because the deivce is probably not called '/dev/sdb'.  I guess it might be but it could just as well be 'vdb'.
1705346,2019-06-19 19:51:33 UTC,"Hey Scott,"
1705346,2019-06-21 16:11:44 UTC,"Could you attach the output of
$ sudo blkid --cache=/dev/null
and also attach the output of running:
 $ cloud-init collect-logs"
1705357,2020-07-18 19:39:46 UTC,Can this be reproduced on newer Ubuntu versions? I'm suspecting this is similar to bug 1786822
1705357,2020-07-19 12:18:33 UTC,"Ubuntu 17.04 was end of support on January 13, 2018. Roland, can you reproduce a problem on supported Ubuntu. I suggest to test on LTS versions like Ubuntu 18.04 or Ubuntu 20.04. If not, then we should probably close this bug report down, because of unsupported operating system."
1705357,2020-07-20 00:39:35 UTC,I think this bug can probably be closed now. I'm on 20.04 now and I don't recall having this issue for a while now.
1705362,2017-07-21 05:11:26 UTC,"Line fader curve adjustment is not new - the mighty Vestax PMC 07 had it, and this feature can still be found on current models like the Pioneer Djm-S9 ."
1705362,2017-07-20 06:34:44 UTC,"Do we have a real user demand for it?
I have investigated this some time ago because the original fader curve was just bad. To solve this I have introduced the audio taper curve taken from high price audio taper pots. I came to the conclusion that there is no need for this feature if we do it just right.
And I do not know of any complains about the new curve since then."
1705362,2017-07-20 06:49:21 UTC,I don't think it makes much sense to have the crossfader curve adjustable but not the channel faders.
1705362,2017-07-20 11:05:39 UTC,Why do you think some users may find this usefull? Did you need this feature?
1705369,2018-04-13 16:57:08 UTC,"This also affected me on Bionic.  Note that I had the Nvidia native drivers working in 17.10, but the bug only affected me in Bionic.  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1763774"
1705369,2018-04-13 14:55:29 UTC,"i had the same problem in ubuntu 18.04 after upgrading to nvidia-drivers-390.48, than i could not login even using nouveau after removing all nvidia driver."
1705369,2018-04-07 21:59:50 UTC,Honestly I wouldn't concern yourself with it at this point. Ubuntu 18.04 is due out in just over two weeks.
1705369,2018-04-07 19:17:14 UTC,"I was reading everything and I want to make sure this is the same issue. When i install the nvidia driver everything runs, installs all good. when i reboot, under the login i dont have an option for ""ubuntu"" and ""ubuntu xorg"" im able to log in, theres screen tearing but ive managed to fix that. however, when i select the intel option under nvidia settings, i log out, then i get the choices. im able to log in under ""ubuntu"" however, when i try to log in under ""ubuntu xorg"" it crashes and i have to force it shut.... is this the same issue yall are having?"
1705369,2018-03-03 19:40:16 UTC,"hi, i have this problem too
im using sony vaio vpceg38fg with nvidia 410m
but the screen is not black, its just turned off.
i have tried nvidia binary driver 384.111, 304.137, 340.104 none of them worked bug-free
nouveau work but i cannot change the brightness of the screen."
1705369,2018-02-11 09:12:31 UTC,"And, I forgot to mention, I disabled Wayland in '/etc/gdm3/custom.conf' by uncommenting"
1705369,2018-02-11 09:06:23 UTC,"Hi there, I've made it work. I don't know if it matters but I am using nvidia-390.
So, first of all, we need to fix nvidia-persistenced."
1705369,2017-11-13 12:30:54 UTC,"There is a quite popular question on Askubuntu regarding this:
https://askubuntu.com/questions/966666/after-the-upgrade-to-17-10-i-only-get-a-black-screen-how-do-i-fix-this"
1705369,2017-12-30 12:20:51 UTC,"I'm also affected by this, running a laptop with intel i5-6300HQ, and GTX 950M. GDM3 won't work at all, but switching to lightDM and Xorg only seems to have solved it temporarily. I'm using nvidia-384 with a 4.13.10-* kernel."
1705369,2017-12-29 18:41:54 UTC,Ok found finally a work solution (I bet for most of you :))
1705369,2017-12-29 09:11:38 UTC,As it looks like there is no chance to make this work on 17.10 do you know if downgrading to 16.04 helps?
1705369,2017-11-28 16:50:48 UTC,#77 enabled me to use nvidia drivers
1705369,2017-11-20 23:09:27 UTC,"Is likley the same issue as this one:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1725169?comments=all"
1705369,2017-11-15 00:29:11 UTC,"Maybe there are separate issues. Booting to a black screen after update happened on three of my machines (2 nvidia, 1 AMD). On all of them it was enough to remove the binary drivers, reboot and reinstall them."
1705369,2018-04-14 17:01:30 UTC,In my issue the CPU is AMD ryzen.
1705369,2017-11-13 17:13:33 UTC,I actually don't think uninstalling nvidia & reinstalling is good enough. gdm3 has to be removed.
1705369,2017-12-30 14:13:35 UTC,"gdm3 and nvidia binary drivers don't work together yet. Maybe 18.04 although there's not much evidence that anyone who knows how to fix this problem is working on it.
This problem has emerged since the default Ubuntu session now uses gdm3 (as of 17.10) but standard gnome users on all recent distribution have the same problem."
1705369,2018-04-28 13:09:10 UTC,I am still affected by this bug after the 18.04 release.
1705369,2018-09-06 18:12:55 UTC,"I suffer from this issue with gtx770 nvidia card. Annoyingly, this freezes gdm3 so hard that I cannot even switch to a different tty.
The workaround above (in '/etc/gdm3/custom.conf' uncommenting #WaylandEnable=false) works for me."
1705369,2018-05-03 01:31:37 UTC,"Note that if the workarounds at the top of this bug don't work for you then you're subscribed to the wrong bug. In that case, please open a new one."
1705369,2019-07-02 16:02:13 UTC,This bug was fixed in the package gdm3 - 3.32.0-1ubuntu2
1705369,2019-06-24 06:18:59 UTC,"Upstream is against changing mutter for this, so ""Won't Fix"" to mutter. But the fix for gdm3 has landed and that's enough to resolve the bug."
1705369,2019-06-19 07:31:18 UTC,Oops. It appears upstream already fixed this bug. And we removed their fix in Ubuntu (revert_nvidia_wayland_blacklist.patch in gdm3). If you revert that revert then the bug is fixed.
1705369,2019-06-18 10:10:58 UTC,Fix proposed: https://gitlab.gnome.org/GNOME/mutter/merge_requests/625
1705369,2019-06-13 10:21:20 UTC,Two years later...
1705369,2019-06-13 10:13:48 UTC,"Comment #116 appears to be linking to the wrong bug. That link is for nvidia-drm.modeset=1 and this bug is specifically about when you don't have that set, like the default."
1705369,2019-06-13 10:09:14 UTC,"-black
+blank"
1705369,2018-05-02 14:13:37 UTC,I'm also affected by this bug on Ubuntu 18.04. This happens both with nvidia-driver-390 and nvidia-driver-396.
1705369,2019-04-28 09:36:55 UTC,I had same problem when disabled integrated card in bios. Found issue report in gdm3 https://gitlab.gnome.org/GNOME/gdm/issues/332. Issue description has link back to launchpad https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857.
1705369,2018-09-07 01:47:44 UTC,That sounds like a different bug. Do you have a separate bug report for that?
1705369,2018-07-31 01:40:33 UTC,"Eduardo, please log a separate bug for that."
1705369,2018-07-30 19:47:08 UTC,"I forgot to say I will try with nomodeset in my Grub config first. If that doesn't work, I will switch from GDM to LightDM."
1705369,2018-07-30 19:42:48 UTC,"Hi, this is the basic configuration of my desktop:
-Motherboard: ROG STRIX X370-F GAMING.
-CPU: Ryzen 7 1700.
-GPU: GTX 1050 2GB from MSI."
1705369,2018-07-02 01:59:03 UTC,"Note that if the workarounds at the top of this bug don't work for you then you're subscribed to the wrong bug. In that case, please open a new one."
1705369,2018-06-30 18:09:53 UTC,The last comment appliable to Laptop DNS H90MB with Intel GMA 3150
1705369,2018-06-29 20:33:41 UTC,"Laptop Samsung NC110-P03RU
Fix:
in '/etc/gdm3/custom.conf' uncommenting"
1705369,2018-11-06 04:41:24 UTC,"@amri,"
1705369,2017-11-13 12:28:44 UTC,The solution is actually easier than #60. You just need to remove and reinstall the nvidia drivers (or amd if you used those).
1705369,2019-07-01 07:20:45 UTC,Now in eoan proposed:
1705369,2017-09-25 20:54:17 UTC,"MicWit, please log a separate bug."
1705369,2017-07-21 04:34:02 UTC,Thanks again.
1705369,2017-07-21 04:06:57 UTC,@Daniel
1705369,2017-07-21 02:34:24 UTC,I'm a little confused because both the log files attached show 'nomodeset' is on the command line.
1705369,2017-07-21 02:27:29 UTC,Thanks.
1705369,2017-07-21 02:14:53 UTC,@Daniel
1705369,2017-07-21 01:39:46 UTC,"""The first try, grub had nomodeset in it, and the system was able to boot, the wayland session was filtered out."""
1705369,2017-07-20 15:06:43 UTC,"@Sebastien
I tried twice using Nvidia driver 375.66.
I also reset nvidia-drm.modeset to its default 0."
1705369,2017-07-20 07:21:18 UTC,"gdm should already fallback to an x11 greeter (with wayland user sessions filtered out from the login choices) on nvidia binary driver configs, could you enable debug in /etc/gdm3/custom.conf (uncomment the corresponding line), reboot and share the journal log?"
1705369,2017-07-20 06:00:17 UTC,"It sounds like what we actually want in future is to keep Wayland enabled by default and gdm3 to just detect the absence of KMS support, and in that case default to Xorg instead."
1705369,2017-07-20 05:55:52 UTC,I meant to say: edit /etc/gdm3/custom.conf and uncomment:
1705369,2017-07-20 05:54:59 UTC,Oh it's easy. Try this:
1705369,2017-07-20 05:48:18 UTC,"Sounds like #3 is the best option, assuming it's possible."
1705369,2017-07-20 05:30:49 UTC,@Daniel
1705369,2017-07-20 04:07:30 UTC,"Although given we have other reasons to prefer Xorg sessions, simply forcing GDM to use Xorg and not Wayland would also solve this."
1705369,2017-07-20 04:06:20 UTC,"I think the ideal solution is to modify gdm to detect if KMS support is missing and switch to X11 instead. It should also hide Wayland sessions when KMS support is missing, and it should hide X11 sessions when Nvidia KMS mode is enabled (bug 1697882)."
1705369,2017-07-20 03:48:44 UTC,For more information see related bug 1697882
1705369,2017-07-20 03:46:50 UTC,This is expected :(
1705369,2017-07-21 04:59:27 UTC,@Daniel
1705369,2017-07-21 06:32:49 UTC,Excellent.
1705369,2017-11-13 06:38:01 UTC,"It has been clear for a while now that Ubuntu actually has a 2-year release cycle.  I have used ubuntu since 8.10, always using the most recent release but since 10.04 I have considered that LTS stands for long term STABLE because of exactly this kind of problem with 17.10.  So I now consider the non-LTS releases to be a ""dev/tester"" release.  Ubuntu doesn't officially say that, but I notice that if you go to the download page, 16.04.3 is the first option available.  I think that Canonical should just be honest about it.  I would still use the  ""dev/test"" releases and they could take more risks.  When I recommend an ubuntu distro to a new user, I will usually recommend the LTS because I don't want them to have to mess around and be put off.  This is the reason why we still have bug #1 an issue for laptops and desktops"
1705369,2017-07-28 01:34:08 UTC,"Yes and no. I was going to look at this bug in detail soon, the first step of which would would also involve looking upstream."
1705369,2017-07-27 10:21:31 UTC,"For what it's worth, nvidia Optimus requires the integrated display to be modeset=1, this is what you mean by ""nomodeset would break laptops"", I assume. Should we be reporting this upstream?"
1705369,2017-09-25 03:19:52 UTC,"I have installed 17.10 in a virtual box (have an nvidia card in my pc, not sure what virtual box detects as, in a windows host), and been updating it daily to check out the 17.10 progression. It was fine for a few weeks, but then about a week ago I would install, and then boot - all good, and then I would do an apt update and upgrade. Once I reboot after an upgrade, I get a black login, then if I press enter, enter my password and press enter again, I get the brief screen with text (like when it worked) and then black again."
1705369,2017-09-12 08:32:54 UTC,"As of the latest updates to gdm3, I still can't boot with my laptop when it's in discrete mode (nvidia graphics only). Does not get to the greeter.
syslog is full of countless repetitions of ""Stopping NVIDIA persistence Daemon"".
CPU must be high because the fan comes on. I've reported this but it's going to be better if someone who knows what they are doing can reproduce it."
1705369,2017-08-29 08:08:39 UTC,"Yes, please log a different bug if you're using Intel graphics."
1705369,2017-08-29 07:58:51 UTC,"I have a similar problem with an intel graphic card
corrado@corrado-HP-aa-p5:~$ inxi -GxxIS
System:    Host: corrado-HP-aa-p5 Kernel: 4.12.0-11-generic x86_64
           bits: 64 gcc: 7.1.0
           Desktop: Gnome 3.24.3 (Gtk 3.22.19-0ubuntu1) dm: gdm3
           Distro: Ubuntu Artful Aardvark (development branch)
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           bus-ID: 00:02.0 chip-ID: 8086:0a16
           Display Server: x11 (X.Org 1.19.3 )
           drivers: fbdev (unloaded: modesetting,vesa)
           Resolution: 1366x768@76.00hz
           OpenGL: renderer: llvmpipe (LLVM 4.0, 256 bits)
           version: 3.3 Mesa 17.2.0-rc4 (compat-v: 3.0) Direct Render: Yes
Info:      Processes: 227 Uptime: 5 min Memory: 1133.9/3880.1MB
           Init: systemd v: 234 runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.121 running in gnome-terminal-) inxi: 2.3.34
corrado@corrado-HP-aa-p5:~$"
1705369,2017-08-28 16:09:39 UTC,Defaut seen ::
1705369,2017-08-28 10:54:10 UTC,"My pc .... ASUS GL753V  Core I7 7700  Video GeForce 1050  NVidia
Same p had artful 17.10 ubuntu before but dont work with X org video server but works with nvidia driver 375.82 ... Problem : all commands ok BUT noway to parameter gamma, contrast ... I used command xgamma - gamma 0.5 or another value but dont work. I put cairo desktop on  with ""luminosite"" command (I am french)... Dont work too. This way (xgamma, cairo lum.  seems not working on nvidia pilote driver but only on X org video serverdriver
The intel prime profile dont work too and crash pc... Hot temp on gpu and Fan hot works !
For info : goods work on 4.10.0.21 version and no generic upgrade possibility"
1705369,2017-08-15 16:31:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705369,2017-08-03 15:58:18 UTC,"I just installed daily iso and I cant login to Gnome at all, when I enter my password after initial reboot the desktop hard locks and I must turn off my laptop, I cant get into virtual consoles or anything. My graphics card is Nvidia, there is no integrated Intel graphics card, only dedicated Nvidia graphics card."
1705369,2017-08-04 01:43:37 UTC,"SB, please log a separate bug."
1705369,2017-07-31 13:58:43 UTC,"@vanvugt, the ""nomodeset"" is removed. After disabling the integrated graphics, I did not need it."
1705369,2017-07-31 11:28:32 UTC,"Daniel, does having switcheroo-control installed help? After reoboting, the computer should default to using the less powerful graphics card. GNOME Shell then provides a right-click option to run specific apps using the more powerful graphics card."
1705369,2017-07-31 08:30:47 UTC,"Tried again, this time remembering to tell my BIOS not to auto-disable the integrated graphics, so now I have both:"
1705369,2017-07-31 08:08:28 UTC,My first attempt at reproducing this bug has failed.
1705369,2017-07-28 03:57:26 UTC,"Yes this bug is only about desktops, where there is no monitor plugged into the Intel GPU."
1705369,2017-07-28 03:45:53 UTC,"OK, Alberto on the upstream bug says it is not the same as my bug, because
the upstream bug is for systems with only an nvidia card.
Mine is an Optimus bug. His point is, I think, that gdm chooses wayland
based on the modesetting value of the first card it sees, which in the case
of an Optimus laptop is the intel video, and the upstream bug is only for
situations where the first card is nvidia, which means it can't apply to
Optimus laptops. However, it seemed the same to me because Wayland and
nvidia modesetting don't seem to work in 17.04 or 17.10. If I can help at
all with testing please let me know."
1705369,2017-07-28 03:28:35 UTC,"No that matches your bug 1706474, both of which are actually the opposite to this one. So really bug 1706474 should not have been marked as a duplicate of this."
1705369,2017-07-28 03:17:01 UTC,Maybe https://bugzilla.gnome.org/show_bug.cgi?id=784470
1705369,2017-08-01 01:51:42 UTC,"Jeremy, I don't experience any bug myself. I'm just trying to find a way to reproduce this one."
1705378,2017-08-23 07:07:46 UTC,"Verified on xenial, this issue was fixed."
1705378,2017-08-28 10:14:27 UTC,This bug was fixed in the package linux - 4.10.0-33.37
1705378,2017-08-28 10:14:02 UTC,This bug was fixed in the package linux - 4.4.0-93.116
1705378,2017-08-16 16:34:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1705378,2017-08-23 06:34:23 UTC,"Verified on zesty, this issue was fixed.
$ uname -an
Linux u-Lenovo-V310-14ISK 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ rfkill list
0: ideapad_wlan: Wireless LAN
 Soft blocked: no
 Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
 Soft blocked: yes
 Hard blocked: yes
2: hci0: Bluetooth
 Soft blocked: yes
 Hard blocked: no
3: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no"
1705378,2017-08-10 05:56:17 UTC,This bug was fixed in the package linux - 4.11.0-13.19
1705378,2017-07-25 01:53:02 UTC,"[Impact]
wireless and bluetooth were blocked by ideapad_laptop module."
1705378,2017-07-25 01:52:23 UTC,From: Yang Jiaxun <email address hidden>
1705378,2017-07-20 04:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1705378,2017-08-16 16:33:28 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1705378,2017-07-20 04:20:43 UTC,"Here is the fix in upstream, we need to let them into xenial kernel, thanks!"
1705388,2017-07-20 12:29:08 UTC,"Indeed, it looks like ASDF will have to declare all its generic functions as ""dynamically modifiable"" to CLISP. And do so in a way backward compatible with older versions of CLISP that do not have the same declaration mechanism."
1705391,2017-07-20 06:25:14 UTC,"Sorry I want to add: it happens with any server, I have many of them to test."
1705391,2017-07-26 08:11:46 UTC,"Guys, seems I have found the conditions in which it happens. I have successfully managed to *not* make it happen."
1705395,2017-10-23 23:51:11 UTC,"@Christian, @Andreas, what do you think of my suggested changes? Given our new code, I think we would be able to use a temporary worktree (chdir'd to it after start) for doing the merge and finish would put you back where you started, at the update-maitainer commit (similar to what we do now, but everything is done in the worktree) and the worktree is pruned."
1705395,2017-10-27 11:45:27 UTC,"I like how rebase -i works. It's in the same directory of the repository, and the PS1 shell variable is updated accordingly via __git_ps1(). And I can simply abort and I will be back in my original state. The same happens with a merge that fails due to conflicts, my prompt always tells me in which state I am, even if I chdir out of the repository and later come back in."
1705402,2017-08-28 17:00:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705402,2017-07-20 08:08:42 UTC,Reported against libinput at the request (in person) of Will Cooke.
1705402,2017-08-31 10:04:16 UTC,I'm also seeing this issue with Wayland/GNOME on artful; any chance it might be addressed before artful releases?
1705402,2018-01-08 05:42:11 UTC,It appears the opposite is also true in some cases. See bug 1728778.
1705408,2017-10-19 18:49:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705409,2017-07-20 08:49:00 UTC,"Swift version: 2.9.0
Swift3 version: 1.11"
1705418,2019-09-19 11:53:31 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1705426,2017-10-18 03:23:55 UTC,"Please download the package or export ""COBBLER_LOADERS_SOURCE_ASIA"" from the url below:"
1705434,2017-07-20 09:57:55 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
 __GI_abort () at abort.c:89
 qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1682
 QMessageLogger::fatal (this=<optimized out>, msg=<optimized out>) at global/qlogging.cpp:793
 akInit(QString const&) ()"
1705434,2018-01-29 00:41:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705434,2018-01-29 03:11:26 UTC,"I get Akonadi crashing several times a day on a new laptop running Artful. My previous laptop, running Xenial, did not do this. I'm not sure that it's crashing with the same signal, as I don't know how to start Akonadi with this process being debugged. I tried attaching the debugger to the process, but the process simply exited without gdb being able to get a stack trace. The tail of strace looks as follows:"
1705434,2019-07-29 18:54:47 UTC,Upstream bug report:
1705442,2017-08-01 14:16:51 UTC,"The Lenovo Cinder driver fails the same way when @utils.synchronized() is replaced with @coordination.synchronized(), blocking https://review.openstack.org/#/c/479069/"
1705442,2017-07-28 15:28:47 UTC,"I agree with Eric, if this is a limitation in etcd3gw it needs to be fixed there or a workaround provided in TooZ, if none of those are possible we'll have to implement the workaround ourselves, but certainly rendering the lock useless by providing a unique ID is not the solution."
1705442,2017-07-31 03:05:33 UTC,"I agree with Eric. I was about to revert my patch with the actual code changes required.
Thanks for reverting."
1705442,2017-07-28 19:35:07 UTC,"Reviewed:  https://review.openstack.org/488158
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9b2a9407f7c1b4688b9f696ea94677516bca5eba
Submitter: Jenkins
Branch:    master"
1705442,2017-07-27 21:02:50 UTC,This issue was fixed in the openstack/cinder 11.0.0.0b3 development milestone.
1705442,2017-07-27 04:17:23 UTC,"Analysis :-
------------------------
1)Since we are using the same ‘image’ while creating all the volumes, cinder code uses same ‘image-id’ to create the lock_name, which in turn, used for creating the same key in etcd.
2)There is the limitation of ‘etcd3gw’ client (which communicates with etcd), that in one transaction, multiple request cannot modify the same key several times."
1705442,2017-07-27 19:40:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/488158"
1705442,2017-07-27 19:04:44 UTC,"Reviewed:  https://review.openstack.org/487694
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=35ae6fb90380a8e9db936827a4414cb249ef399b
Submitter: Jenkins
Branch:    master"
1705442,2017-07-27 05:07:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/487694"
1705442,2017-07-20 10:52:20 UTC,out of 10 volumes 6 were succesfull and 4 was in error state.
1705442,2017-07-27 20:15:29 UTC,This needs more investigation to determine whether there is a bug in tooz/etcd or what is going on here.
1705442,2017-07-20 10:36:06 UTC,"On further analysis, it fails to acquire the lock in decorator function coordination.synchronized(). This results in error ""ToozError: Not Found"""
1705470,2017-07-20 12:48:48 UTC,This is a replication v1 command that has only been help in the client for backwards compatibility support for older Cinder services. It should probably now be deprecated and removed.
1705470,2018-07-27 13:13:10 UTC,This issue was fixed in the openstack/python-cinderclient 4.0.0 release.
1705473,2017-08-25 17:38:50 UTC,"MAAS doesn't pass any network config to cloud-init, hence this should be limited only to curtin."
1705473,2019-09-19 12:04:13 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1705476,2020-12-03 12:59:47 UTC,"We don't use linuxcontainers.org as a source of the image nowadays. Moreover, neither of affected OS  or openstack versions are supported."
1705476,2017-07-20 13:08:05 UTC,when running ./scripts/run-playbooks.sh the failures appear to be realted to creating the containers such as:
1705476,2017-07-25 12:59:18 UTC,What happens if you run that lxc-create command manually on the system?  I can't think of anything specific to VirtualBox that would cause that part to fail.
1705476,2017-08-01 16:54:15 UTC,"I've seen this happen when the DNS resolution fails intermittently, which happens fairly often for linuxcontainers.org which some providers unfortunately. See if you can monitor DNS traffic in some way to validate whether that's the issue."
1705480,2017-07-28 14:04:39 UTC,This issue was fixed in the openstack/python-magnumclient 2.7.0 release.
1705483,2020-07-31 14:27:10 UTC,"This is still happening on xenial, although it seems to be happening on s390x now, so I decided to investigate why."
1705486,2017-12-08 16:08:08 UTC,"note that this is only true for the edge channel ... gadgets in stable, candidate and beta are still affected."
1705486,2017-12-08 15:11:43 UTC,"AIUI the gadget snap was updated for all pi2,pi3,cm3. So this should be fixed. Please reopen if I am mistaken."
1705486,2017-07-21 12:47:02 UTC,Awesome to hear :)
1705486,2017-07-21 12:13:47 UTC,It seems this makes it work. Thanks a lot for that!
1705486,2017-07-20 15:36:29 UTC,"the option to add to /boot/uboot/config.txt is ""dtparam=spi=on"", you can edit this file manually for the time being and install your snapped application in --devmode until snapd and the gadget bits are fixed (to unblock development etc) as a temporary workaround."
1705486,2017-08-03 10:33:28 UTC,a fix for the pi3 gadget just landed via https://github.com/snapcore/pi3-gadget/pull/12
1705486,2017-07-20 15:33:35 UTC,"while it is fairly easy to enable teh spidev overlay in /boot/uboot/config.txt (and we should be easily able to set this as default in the gadget snap), there is currently no interface in snapd that allows spidev access ... adding a snapd task here ..."
1705491,2017-07-20 14:07:31 UTC,What settings are you attempting to change?  How are you changing them?  Be specific please.
1705491,2017-07-20 16:17:13 UTC,The settings I mainly tried to change were the animations in cinnamon and the alt-tab switcher.
1705493,2017-07-20 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1705493,2017-07-20 14:57:03 UTC,I built a Xenial test kernel with commit b8c0d911ac528.  The test kernel can be downloaded from:
1705493,2017-07-24 09:18:36 UTC,"ubuntu@maas-xenial5:~$ uname -r
4.4.0-87-generic"
1705493,2017-08-14 12:47:24 UTC,SRU request thread:
1705494,2019-09-11 16:42:44 UTC,"I agree Andrea, I believe this is fixed in webby. I can run reports with birth dates before 1970 in webby. I am going to mark this one won't fix."
1705494,2019-03-05 20:56:15 UTC,"Looked at this in 3.2 and despite Reports being the ported interface I can in fact set pre-1970 dates on a date filter.  Tagging fixedinwebby, but not marking won't fix yet in case there's something I'm misunderstanding."
1705494,2017-07-20 17:47:57 UTC,Adding background info...
1705496,2020-06-23 09:38:14 UTC,"This would be also a fix for problems people often having with low quality wifi connections where local IP is acquired by DHCP and there are frequent disconnects which may change the local IP.
This call would be also useful to be fired when there are changes in the status of the bound network interface as when it goes down/up or when ""new internet connection"" detected by the OS."
1705497,2019-03-07 19:21:41 UTC,"Pushed to master and rel_3_2.  Thanks, Adam, Christine, Tiffany and others who commented on the thread!"
1705497,2019-03-07 17:23:44 UTC,"Great, thanks so much Christine! And thank you, Adam! This has been much anticipated. :)"
1705497,2019-03-07 17:14:06 UTC,"Tiffany,
I tested this on our 3.2.4 test system with production data. It worked beautifully. Testing from both the Item View or the List View, the correct line item was located every time."
1705497,2019-03-07 13:39:21 UTC,"With the updated code, this seems to be working for me! Very exciting."
1705497,2019-03-07 04:17:39 UTC,"Temporary breakdown in noticing IDs on my part. Try this one. I believe it works as expected, and I've added the functionality to the list, as well."
1705497,2019-03-06 16:22:07 UTC,Thanks!
1705497,2019-03-06 15:58:04 UTC,*locate?
1705497,2019-03-06 15:57:52 UTC,"Tiffany,"
1705497,2019-03-06 16:14:12 UTC,"Absolutely! I'll email you several of them, Adam."
1705497,2019-03-06 09:07:11 UTC,"Option added in ""Actions -> Find -> Originating Acquisition"" on /eg/staff/cat/item/x"
1705497,2019-03-06 08:51:43 UTC,https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=b464723d0e5c0750f8b75f8e7ae6ba3b169bad33
1705497,2018-03-23 18:38:56 UTC,I find it very useful in the XUL client and think it is important to include in the web client.
1705497,2018-10-23 18:53:42 UTC,"As a starting point for any developer who has time to implement this (not me!), here's what ""Find Originating Acquisition"" does in the XUL client:"
1705497,2018-10-23 18:28:53 UTC,"That's good news. I hope it's in place before we move to the web client, probably late next year."
1705497,2018-10-23 16:19:52 UTC,"Thanks Andrea! That's good to know, but I really, really hope it is resolved before then. It seems like a long time to wait for something that I'm guessing wouldn't take much time for a knowledgeable person to add."
1705497,2018-10-23 16:08:51 UTC,"Noting that this is on our list as something to pick up as part of Angular Acq, if it hasn't been addressed before then."
1705497,2018-10-22 23:16:53 UTC,Thanks for bumping this to high Kathy.  We're definitely missing this function and have also been unable to find a workaround for this in the web client (currently running 3.1.4).
1705497,2018-09-07 16:42:34 UTC,"I'm bumping the status of this bug up to high because this is a feature of the xul client that was frequently used and is no longer available to users. As far as I can tell, there is no workaround to get this information in the client."
1705497,2018-05-17 11:45:54 UTC,"I use this quite a bit, and definitely think it's important to have in the web client."
1705497,2019-03-06 14:38:27 UTC,"Adam,"
1705504,2017-08-03 14:28:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705511,2017-07-20 19:40:30 UTC,"DuplicateSignature:
 Unpacking kde-l10n-si (4:4.10.97-0ubuntu1) ...
 Unpacking kde-l10n-si (4:4.10.97-0ubuntu1) ...
 dpkg: error processing archive /var/cache/apt/archives/kde-l10n-si_4%3a4.10.97-0ubuntu1_all.deb (--unpack):
  trying to overwrite '/usr/share/locale/si/LC_MESSAGES/kcmkwm.mo', which is also in package kwin-data 4:5.5.5-0ubuntu1"
1705528,2017-07-24 13:47:06 UTC,"Hi all,"
1705530,2017-08-19 17:20:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705530,2018-01-31 14:13:34 UTC,See https://forum.snapcraft.io/t/use-the-system-gtk-theme/496 and https://forum.snapcraft.io/t/desktop-improvements-report-and-plans/3510 for progress on this
1705534,2018-01-17 11:48:16 UTC,"I'm sorry, but I still don't understand what you're saying or what you're doing."
1705534,2018-01-25 16:30:40 UTC,"In the absence of an explanation for why this bug should be closed when it is in fact still a bug in 17.10, I'm once again reopening it."
1705534,2018-01-17 07:33:47 UTC,"As you says, it's declared 'fixed' some releases ago (see Artful changelog); and zesty is now unsupported. So closing that report."
1705534,2017-07-20 17:07:05 UTC,Reported upstream as https://bugzilla.redhat.com/show_bug.cgi?id=1473392 .
1705534,2018-01-16 18:06:29 UTC,"I mean, did you even check if the bug still existed in 17.10 before marking it invalid?"
1705534,2018-01-16 18:06:05 UTC,"Bug still exists in 17.10, not clear to me why you marked it invalid."
1705534,2018-01-16 17:46:59 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1705534,2018-01-16 18:08:31 UTC,"Upgrading lvm2 in Ubuntu to the current upstream release will address this issue, according to a comment on the upstream bug I reported (link above)."
1705536,2019-03-20 21:50:39 UTC,"Change abandoned by David Shaughnessy (<email address hidden>) on branch: master
Review: https://review.openstack.org/528336"
1705536,2020-01-28 19:20:53 UTC,"Change abandoned by Xubo Zhang (<email address hidden>) on branch: master
Review: https://review.opendev.org/629761
Reason: the project is cancelled as we are moving to OVN, which also uses openflow to implement L3"
1705536,2020-01-28 18:13:35 UTC,"Change abandoned by Igor D.C. (<email address hidden>) on branch: master
Review: https://review.opendev.org/639605
Reason: Clean up."
1705536,2020-01-28 18:13:16 UTC,"Change abandoned by Igor D.C. (<email address hidden>) on branch: master
Review: https://review.opendev.org/642249
Reason: Clean up."
1705536,2019-03-10 03:28:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/642249"
1705536,2017-07-20 17:40:08 UTC,"Did you take a look at ODL, OVN, Dragonflow, and probably a bunch of other OVS based Neutron drivers I'm missing?"
1705536,2019-02-27 09:15:10 UTC,"Change abandoned by Igor D.C. (<email address hidden>) on branch: master
Review: https://review.openstack.org/639603
Reason: commit mistake"
1705536,2019-02-27 09:17:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/639605"
1705536,2017-10-19 13:59:35 UTC,i'm not sure why the operator needs yet another option while there are already plenty of options as pointed out.
1705536,2017-07-20 20:50:58 UTC,"The use of namespaces limits the adoption of things like DPDK, but there are other solutions out there that do not have that limitation, as Assaf pointed out. Enabling the L3 agent DVR mode to be purely Openflow based (as this RFE seems to imply) now that major strides have been made into OVS is something in the minds of many. Not sure if I would consider it yet another agent_mode, but rather just an internal re-architecture. With that though there's the pain of migration and we all know how tricky these are."
1705536,2017-11-03 16:19:10 UTC,"This RFE was discussed on Nov 2 in the drivers meeting. The consensus was that we will not be able to accept this work in the near future (Quuens cycle) due to the continued instability of the DVR - HA gate jobs.Until we can get those jobs stable and voting, it is not advisable to add more moving parts to them."
1705536,2019-02-27 09:12:51 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/639603"
1705536,2017-11-02 22:27:17 UTC,POC code is here: https://review.openstack.org/#/c/472289/
1705543,2017-07-20 17:44:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/485755"
1705543,2017-09-13 16:18:02 UTC,I'm here at the PTG - perhaps we could discuss this?
1705543,2017-09-14 23:20:47 UTC,Thoughts from Ken: http://lists.openstack.org/pipermail/openstack-dev/2017-August/120478.html
1705543,2017-09-20 14:51:40 UTC,And further replies in September: http://lists.openstack.org/pipermail/openstack-dev/2017-September/122243.html
1705543,2018-06-06 18:39:09 UTC,"Change abandoned by Douglas Mendizábal (<email address hidden>) on branch: master
Review: https://review.openstack.org/485755
Reason: Abandoning patch due to lack of activity for months.  Feel free to re-submit if needed."
1705543,2018-02-27 11:44:55 UTC,We're here at the Dublin PTG and hoping to discuss this shortly.
1705570,2017-07-20 20:47:59 UTC,"StacktraceTop:
 Streaming::StreamProcessor::packetsStopped() () from /tmp/apport_sandbox_uhD_iu/usr/lib/libffado.so.2
 IsoHandlerManager::IsoHandler::disable() () from /tmp/apport_sandbox_uhD_iu/usr/lib/libffado.so.2
 IsoHandlerManager::IsoHandler::~IsoHandler() () from /tmp/apport_sandbox_uhD_iu/usr/lib/libffado.so.2
 IsoHandlerManager::pruneHandlers() () from /tmp/apport_sandbox_uhD_iu/usr/lib/libffado.so.2
 IsoHandlerManager::unregisterStream(Streaming::StreamProcessor*) () from /tmp/apport_sandbox_uhD_iu/usr/lib/libffado.so.2"
1705570,2017-08-24 15:39:51 UTC,"Only a single device connected, the connection might have been unreliable while I plugged a headphone.  dmesg says:"
1705574,2017-07-20 20:56:45 UTC,"StacktraceTop:
 QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /tmp/apport_sandbox_QDIgjg/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /tmp/apport_sandbox_QDIgjg/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QDBusConnectionPrivate::registerObject(QDBusConnectionPrivate::ObjectTreeNode const*) () from /tmp/apport_sandbox_QDIgjg/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
 QDBusConnection::registerObject(QString const&, QString const&, QObject*, QFlags<QDBusConnection::RegisterOption>) () from /tmp/apport_sandbox_QDIgjg/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
 QDBusConnection::registerObject(QString const&, QObject*, QFlags<QDBusConnection::RegisterOption>) () from /tmp/apport_sandbox_QDIgjg/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5"
1705574,2017-08-03 13:35:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705574,2017-08-17 09:02:42 UTC,"Hi,"
1705593,2018-01-31 12:48:00 UTC,"This issue is still present on 18.04, but it proved to be Wayland specific. The gnome-language-selector UI works as expected if I log in to Ubuntu with Xorg. The fact that Xorg will be default in 18.04 reduces the urgency of this bug."
1705593,2020-08-21 13:40:24 UTC,Tried this with Ubuntu on Wayland on 20.04. The issue seems to be gone. Closing.
1705596,2019-04-25 15:11:27 UTC,"Hi, apologies for the very long lack of response. Is this still an issue with the latest Fedora and Inkscape versions?"
1705596,2019-06-30 00:48:50 UTC,"Closing as there has been no response for over 60 days. If you still have a similar problem with the latest version of Inkscape, please report it on our new bug tracker: https://inkscape.org/report. Thank you!"
1705605,2018-08-15 22:24:29 UTC,No longer affects me.
1705609,2017-07-21 02:48:15 UTC,"This bug was submitted with the nvidia-384 drivers from the driver-updates PPA installed, but the same behaviour is apparent with nvidia-375 from the Artful repositories."
1705609,2017-08-16 10:27:33 UTC,"Hi Chris, can you reproduce the problem and attach your /var/log/gpu-manager.log, please?"
1705609,2017-08-17 02:07:33 UTC,Hah!
1705626,2017-08-30 21:51:22 UTC,Closing as this bug report doesn't seem to describe what the issue is. You can do a single click upgrade with update-manager.
1705626,2017-08-31 12:40:32 UTC,"This bug it is valid, we can upgrade Ubuntu with update-manager but we can not upgrade with gnome-software like fedora does https://fedoraproject.org/wiki/File:Upgradef24f25-gs.png"
1705626,2017-08-31 12:49:02 UTC,"that's not a bug, Ubuntu just uses a different tool for system upgrades"
1705626,2021-02-24 20:09:25 UTC,"[Important]
This must be able to perform as two separate tasks (not together); UI enhancement in update section may help to address that and  classic terminal ways, software updater should remain as it"
1705636,2017-08-23 07:43:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705647,2017-07-21 07:48:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705647,2017-07-21 07:48:58 UTC,"IMHO, the window isn't its own X window, and global size = size of the main gedit window + transparent borders."
1705650,2018-02-27 06:31:34 UTC,"Duplicate of Bug : #1691283
Fix merged at https://review.openstack.org/#/c/471551/"
1705661,2018-04-09 13:32:51 UTC,I ran a simple script to detect how much cruft (classes with no references in Dr. Geo 17-07a) is left into the image. (see script attached)
1705661,2018-04-09 20:42:43 UTC,"It will be great! Removing packages is tedious and an helper application will be very useful for Dr. Geo and very likely to other applications.
By the way, Dr. Geo is now developed against Pharo7, although still alpha."
1705661,2018-04-13 11:25:01 UTC,Just started investigating and thinking about what is needed to do an image stripper.
1705663,2019-10-07 13:52:02 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/486850"
1705663,2017-07-27 08:18:52 UTC,looks like this is a older issue as I am using a Newton environ to test
1705663,2017-07-27 08:18:31 UTC,"[root@OSPRUI ~] #         curl -g -i --cacert ""/data/PKIcerts/certs/cacert.pem"" -X GET https://9.60.29.98:8774/compute/v2.0 -H ""OpenStack-API-Version: compute 2.37"" -H ""User-Agent: python-novaclient"" -H ""Accept: application/json"" -H ""X-OpenStack-Nova-API-Version: 2.37"" -H ""X-Auth-Token: 28cf476873b14b6088e9c575e9be3afe""
HTTP/1.1 300 Multiple Choices
Content-Length: 465
Content-Type: application/json
Date: Thu, 27 Jul 2017 08:17:30 GMT"
1705663,2017-07-25 13:46:29 UTC,Is this latent or a regression in Pike?
1705663,2017-07-25 03:58:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/486850"
1705666,2017-07-26 09:24:23 UTC,This issue is also reproducible with Zesty ADT tests with linux 4.10.0-29.33
1705683,2017-07-24 13:54:31 UTC,Just setting the same assignee for all components.
1705683,2017-10-24 12:43:29 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1705683,2017-09-25 14:28:05 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1705683,2017-09-15 22:14:38 UTC,"Reviewed:  https://review.openstack.org/501254
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd82d551a95b2fb7ae69c8234a4f9a250e015ac7
Submitter: Jenkins
Branch:    stable/pike"
1705683,2017-09-06 13:15:45 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/501254"
1705683,2017-08-04 14:02:27 UTC,"Reviewed:  https://review.openstack.org/486113
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=2eabb86120237192aa4f7581fee3799a96f7d27e
Submitter: Jenkins
Branch:    master"
1705683,2017-08-31 10:59:25 UTC,"Reviewed:  https://review.openstack.org/499551
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=6887bbf70b134461011157b996a2014ff39923b5
Submitter: Jenkins
Branch:    stable/pike"
1705683,2017-08-31 10:46:44 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/499551"
1705683,2017-08-31 08:21:24 UTC,"Reviewed:  https://review.openstack.org/499127
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=fedb492a1466ab0fdb9a055b4399f1876e19f291
Submitter: Jenkins
Branch:    master"
1705683,2017-09-06 12:39:54 UTC,"Reviewed:  https://review.openstack.org/486955
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=20196b74dea4a1af4ea643a45fdb96b03f8ea96d
Submitter: Jenkins
Branch:    master"
1705683,2017-08-30 12:11:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499127"
1705684,2019-10-11 01:12:24 UTC,https://github.com/snapcore/snapcraft/pull/2749
1705684,2017-09-09 22:27:38 UTC,Did the API change
1705684,2017-09-09 22:28:09 UTC,"Said differently, where is this documented?"
1705687,2017-07-23 10:55:26 UTC,"I've had the same issue, but I think it fixed itself after booting for the first time, installing all the updates in Ubuntu Software, and then rebooting."
1705693,2017-07-21 12:12:42 UTC,Confirming that check number is not a column picker option in Bill History in either the xul or web client.
1705693,2020-12-08 21:05:24 UTC,Here's a branch for testing: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbriem/lp_1705693_check_number_bill_history
1705693,2021-02-08 23:01:20 UTC,It looks like the code was changed for both Payments and Transaction Details
1705693,2021-02-08 23:08:59 UTC,"Ah, not Bills > History > Transactions, though."
1705693,2021-02-09 16:19:44 UTC,"Upon considering this further, I'm not sure that it really makes sense to have check number in the transaction history tab -- a transaction can have multiple payments, in which case there can be multiple check numbers."
1705693,2021-02-08 20:05:09 UTC,Feedback Fest 2/8/2021 comment:
1705694,2017-07-25 06:28:59 UTC,"Reviewed:  https://review.openstack.org/484307
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=a7ab475cd0917ffdeb1dd5ffa5a8a9a38f907b78
Submitter: Jenkins
Branch:    master"
1705694,2017-07-25 08:46:22 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/486949"
1705694,2017-07-25 18:23:39 UTC,"Reviewed:  https://review.openstack.org/486949
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=34f3011913a4480d935fa7d8755ef1947ad5010c
Submitter: Jenkins
Branch:    stable/ocata"
1705695,2017-07-27 13:08:09 UTC,"Fix committed into lp:miral at revision 568, scheduled for release in miral, milestone Unknown"
1705707,2017-09-11 16:23:17 UTC,"Hi @justinkl,"
1705707,2017-07-21 13:54:42 UTC,"""net_sched: fix error recovery at qdisc creation"" applied with fuzz2 in net/sched/sch_mqprio.c hunk#2."
1705707,2017-09-06 22:37:43 UTC,"Hi all,"
1705707,2017-08-28 10:14:02 UTC,This bug was fixed in the package linux - 4.4.0-93.116
1705707,2017-09-07 13:14:18 UTC,I created another bug to track the Address Sanitizer issue: LP #1715636.
1705719,2017-12-14 22:54:01 UTC,"This RFE has been postponed for lack of implementation resources. If someone is interested in pursuing it, it can be re-considered in the future"
1705719,2017-11-27 14:36:16 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/483020"
1705719,2017-11-27 14:36:11 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/482307"
1705719,2017-11-27 14:36:06 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/458531"
1705719,2017-11-27 14:36:00 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/446047
Reason: just going to abandon in case anyone else wants to work on it, go ahead."
1705719,2017-11-21 14:43:41 UTC,I'm not really sure what to say at this point.
1705719,2017-11-16 22:31:41 UTC,"Trevor,"
1705719,2017-11-16 09:30:41 UTC,"Trevor,"
1705719,2017-11-02 20:13:50 UTC,"Yamamoto,"
1705719,2017-11-02 14:06:57 UTC,"Trevor,"
1705719,2017-10-27 05:14:01 UTC,"Trevor,"
1705719,2017-10-26 14:03:37 UTC,"@YAMAMOTO, yes.
what's ""provider:s_tag:c_tag""?
 - This is a way to identify a specific QinQ network
""provider:s_tag:c_tag_min:c_tag_max"" is configured like phynset1:1:1:1000. Both c_tags and s_tags are statically configured. Upon allocation of segmentation_id 1 on physnet1 c_tags 1-1000 will be allocated with the above example."
1705719,2017-10-26 11:53:54 UTC,"Trevor,"
1705719,2017-10-25 18:41:09 UTC,"@YAMAMOTO, yes. provider:segmentation_id would be a provider:s_tag:c_tag. s_tag comes from the segmentation_id. When configured for c_tags, the range of c_tags is allocated upon creation of a network with a configured s_tag matching the specified segmentation_id. Perhaps my blog on this would help explain it a bit, https://trevormccasland.wordpress.com/2017/07/21/neutron-qinq-network-type-driver-wip/"
1705719,2017-10-19 14:07:18 UTC,"is this about introducing a new network_type for provider network extension?
provider:segmentation_id would be a s_tag:c_tag pair?  or, does s_tag come from somewhere else?"
1705719,2017-08-04 19:45:01 UTC,I would move it back to Triaged if I had permissions..
1705719,2017-07-26 22:41:07 UTC,Moved to Triaged state so we can discuss in drivers meeting tomorrow.
1705719,2017-11-03 18:11:28 UTC,"Trevor,"
1705719,2017-10-31 20:42:49 UTC,"Yamamoto,"
1705720,2019-05-08 02:20:27 UTC,Looks like this was misfiled against logcheck rather than logwatch
1705720,2017-07-24 17:05:28 UTC,"Looks fixed in Artful and Zesty, needs fix in Xenial."
1705720,2018-01-19 22:01:23 UTC,This issue has popped up on a server just upgraded from 14.04LTS to 16.04.3LTS.
1705728,2017-07-21 15:56:46 UTC,http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1705728-fine-gen-cache-parallel
1705728,2017-07-24 15:46:40 UTC,"Removing pullrequest for now.  After running the patch for several days on a large data set, the storage drones, which are not recycling as quickly now, are slowly consuming enough memory to have a noticeable impact on the system."
1705728,2017-07-24 16:24:32 UTC,"Bill, I think perhaps a smaller overall change would be:
 * Continue to use MultiSession
 * Generate a session token in the client script, perhaps based on it's pid, and send that along with each circ id
 * Have the storage backend use that session token as a prefix to a memcache key for grabbing circ lib org settings out of the cache
 * If not there, grab them from the db and populate the memcache slot for other backends."
1705728,2017-07-24 18:12:51 UTC,"I'm going to put something together that looks like what I describe, and we can choose which way to go after looking at both.  I think it'll be pretty quick to put together."
1705728,2017-07-24 18:59:26 UTC,"Bill, here's a version of what I was thinking.  Thoughts on that?"
1705728,2017-07-24 19:53:35 UTC,My last comment lead me to open bug #1706147 which would solve the memory issue.
1705728,2019-04-30 14:26:14 UTC,I am looking at options to improve our fine generator performance. It presently runs for 45 minutes every hour.  We run it every hour because we have hourly fines and staff like to be able to tell patrons how much they owe in fines without having to check things in or do any math in their heads.
1705737,2017-09-01 17:13:25 UTC,"Replace all ocurrences in a text editor of ""e218"" by """" and it show.
Anyway is a malformed path maybe a bug on 0.48."
1705737,2017-09-01 17:06:31 UTC,¿Can you try to remove all wrong elements to see if the file is full draw correctly or missing some parts?
1705737,2017-09-01 12:58:25 UTC,"Hi Javier,"
1705737,2017-08-28 16:48:31 UTC,Inside Inkscape
1705737,2017-09-01 17:14:31 UTC,Not sure if auto remove it from Inkscape 0.93 is a good idea.
1705737,2017-08-28 16:47:50 UTC,"To test the wrong path open a new file, add a line and substitute the d=""...."" with ""m 562.10383,1.9527134e218 v 0"" by this way you have a less sice scope to work. The first thing I try is remove ""e228"" text and see if is the desirable result, or maybe need to be 0, or one or a totaly loosed value...."
1705737,2017-08-28 16:45:08 UTC,"Hi the problem is the lines with id=""what id I say"" and something more has a d=""with wrong data not a path"""
1705737,2017-08-28 16:07:36 UTC,"Hi Jabiertxof,"
1705737,2017-08-28 14:39:55 UTC,Hi.
1705737,2017-08-28 14:02:00 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1705737,2017-08-28 13:31:58 UTC,"Good Morning,
I reported this bug about a month ago. What is the status of this request please?"
1705737,2017-08-28 16:48:18 UTC,You can do this things with the XML inspector
1705748,2018-02-24 11:48:17 UTC,"Sorry for being so slow, and not sure I have run the correct tests:"
1705748,2018-02-13 05:55:22 UTC,Please try [1].
1705748,2018-02-10 06:52:49 UTC,"Can you manually install libssl1.1? Or skip installing header files, if you don't use any DKMS."
1705748,2018-02-09 23:13:52 UTC,"Unable to install the file:
linux-headers-4.13.0-34-generic_4.13.0-34.37~lp1746340_amd64.deb"
1705748,2018-02-09 18:45:26 UTC,"Build a new one, based on artful,"
1705748,2018-02-09 10:42:53 UTC,"Yes, but I am bit confused by that other thread, can you direct me to the download of the specific kernel you want me to try."
1705748,2018-02-09 06:58:32 UTC,"Steve,"
1705748,2017-11-12 16:15:24 UTC,"Sorry for slow response.
Yes all seems to be fine, I have had 9 days of uptime with numerous suspend and resumes without issue."
1705748,2018-01-09 04:29:38 UTC,"> On 5 Jan 2018, at 7:28 PM, Steve Roberts <email address hidden> wrote:
>
> Will this make it into the mainstream kernel updates or how do I track when it is ?
> I just installed 4.13.0-19 and the issue is still there.
"
1705748,2018-01-05 11:28:40 UTC,"Will this make it into the mainstream kernel updates or how do I track when it is ?
I just installed 4.13.0-19 and the issue is still there."
1705748,2017-11-09 06:12:42 UTC,https://lkml.org/lkml/2017/11/9/34
1705748,2017-11-09 03:28:42 UTC,"Steve, I'll send the patch if you have no concern."
1705748,2017-11-02 15:27:17 UTC,"Yes. Use ""nvme_core.force_apst=1"""
1705748,2017-11-02 11:10:58 UTC,"Installed that latest version, can confirm that apst is disabled without the max_latency setting kernel parameter ...."
1705748,2018-02-24 12:11:50 UTC,"Hmm, I'll build a new one based on Bionic's kernel."
1705748,2018-01-09 06:50:26 UTC,SRU: https://lists.ubuntu.com/archives/kernel-team/2018-January/089222.html
1705748,2018-02-25 16:05:57 UTC,http://people.canonical.com/~khfeng/lp1705748-pcireset/
1705748,2018-06-14 10:39:30 UTC,"Hi Steve,"
1705748,2018-02-25 17:06:05 UTC,"The code is ""Fix Committed"" in the Arftul kernel tree, but it's not yet ""Fix Released"" as a binary package. So 4.13.0-34 package doesn't contain the fix yet."
1705748,2018-08-24 16:54:16 UTC,Apparently yes. File attached.
1705748,2018-08-23 09:22:15 UTC,"Steve,"
1705748,2018-08-09 12:15:36 UTC,"$ cat /proc/cmdline
BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-3-generic root=UUID=0885f579-b2ff-4c94-964c-d65c30bb7761 ro rootflags=subvol=@ nvme_core.force_apst=1"
1705748,2018-08-08 16:52:32 UTC,"Ok, testing now... will report back..."
1705748,2018-08-01 05:44:25 UTC,"Steve,"
1705748,2018-06-25 21:32:23 UTC,Hmmm.... so if I understand PCIe ASPM would be set in the BIOS. I updated the BIOS to a later version (3803) since the original issue (soon after the last testing at end of Feb). So I guess it may be that it has been disabled in the bios ?
1705748,2018-06-21 09:04:42 UTC,"There is another user faces the same issue. The PCIe ASPM is enabled for SM/PM/EVO 961, and disabling ASPM solves the issue for the user."
1705748,2018-02-25 16:47:10 UTC,"In case it helps, further test with 4.13.0-34"
1705748,2017-10-31 08:51:34 UTC,"My apology, I typed wrong PCIID for the Samsung device."
1705748,2018-06-14 09:17:14 UTC,"Hi Kai-Heng, Guessing that request is directed at me, so here it is:"
1705748,2018-06-14 05:26:09 UTC,"Robert,"
1705748,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1705748,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1705748,2018-03-23 11:01:49 UTC,"I am not sure if I have done the correct thing, but following the instructions above I have managed to install xenial-proposed kernel 4.13.0-38 on my Mint 18.2 XFCE system:"
1705748,2018-03-19 10:58:32 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1705748,2018-03-19 10:56:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1705748,2018-06-14 09:24:39 UTC,"Realise I probably should have run as sudo, so sudo version attached"
1705748,2017-10-30 12:02:03 UTC,Output from get-feature:
1705748,2018-06-14 14:00:42 UTC,"I have deleted/removed many of the older testing kernel, but I think this one does not have the fix, based on post #97"
1705748,2017-10-26 21:12:25 UTC,Oct 26 17:23:41 phs08 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro
1705748,2017-07-24 09:06:06 UTC,"Please remove ""nvme_core.default_ps_max_latency_us=0"" then try this linux kernel:
http://people.canonical.com/~khfeng/lp1705748/"
1705748,2017-07-22 00:58:52 UTC,"Confirm that removing:
nvme_core.default_ps_max_latency_us=0
from boot params results in reproducible problem on resume from suspend."
1705748,2017-07-21 18:23:28 UTC,apport information
1705748,2017-07-21 18:23:26 UTC,apport information
1705748,2017-07-21 18:23:25 UTC,apport information
1705748,2017-07-21 18:23:24 UTC,apport information
1705748,2017-07-21 18:23:22 UTC,apport information
1705748,2017-07-21 17:49:27 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1705748,2017-07-21 18:23:21 UTC,apport information
1705748,2017-07-21 18:23:20 UTC,apport information
1705748,2017-07-21 18:23:19 UTC,apport information
1705748,2017-07-21 18:23:18 UTC,apport information
1705748,2017-07-21 18:23:17 UTC,apport information
1705748,2017-07-21 18:23:15 UTC,apport information
1705748,2017-07-21 18:23:14 UTC,apport information
1705748,2017-07-21 18:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1705748,2017-10-27 06:02:56 UTC,Can you attach the output of `nvme get-feature -f 0x0c -H /dev/nvme0`?
1705748,2017-07-25 00:51:17 UTC,"Many thanks, suggested kernel now under test..."
1705748,2017-07-25 08:51:47 UTC,"Unfortunately the problem is still there with this 4.11 kernel...
After initial install of the kernel and a suspend/resume it all seemed ok, but then after leaving suspended overnight, the disk goes missing again, see extracts below."
1705748,2017-07-21 18:28:27 UTC,"This is a brand new build, with Mint 18.2 installed intitally with kernel 4.8.53, but upgraded straight away to latest kernel due to using Ryzen cpu."
1705748,2017-07-25 16:53:07 UTC,"Try the kernel here, it adds a delay before controller reset."
1705748,2017-08-18 09:56:44 UTC,I guess NVMe probably needs a to sleep exlat time (6000 here) to let it transit back to power state 0.
1705748,2017-08-15 13:50:55 UTC,Sorry for slow feedback....
1705748,2017-08-09 15:55:52 UTC,"Here you go:
http://people.canonical.com/~khfeng/lp1705748-8-9/"
1705748,2017-08-09 08:34:46 UTC,"Yea, I think it's normal, because the kernel version is the same. The old one with the same version will be removed before installing the new one."
1705748,2017-08-08 16:16:19 UTC,"Unfortunately there seems another issue with this kernel:
The screen/video is blank on resume, I think this is the offending part:"
1705748,2017-07-25 08:58:30 UTC,"One curious thing I note, probably irrelevant, is that after resume, there is lots of stuff recorded in the logs that seem to be about suspending...... e.g. Freezing remaing tasks after the computer has resumed..."
1705748,2017-08-07 05:44:28 UTC,"Please try this one:
http://people.canonical.com/~khfeng/lp1705748-3/"
1705748,2017-08-03 14:48:20 UTC,I don't have a dmesg log file (due to systemd ?) but I attach syslog from start of boot with the kernel to when the reset button pressed...
1705748,2017-08-03 13:26:39 UTC,Can you attach the full dmesg? I'd like to check some additional information.
1705748,2017-08-08 10:10:07 UTC,"Ok, will test and report and back"
1705748,2017-08-02 17:09:46 UTC,"Sorry, I have downloaded but haven't got to testing it yet.... have had to prioritise the day job... will aim to try this evening and report back tomorrow..."
1705748,2017-08-02 16:23:33 UTC,"Roberts, does the new kernel I built still have the issue?"
1705748,2017-07-31 09:56:53 UTC,"Please try this one:
http://people.canonical.com/~khfeng/lp1705748-disable-apst/"
1705748,2017-07-31 03:39:32 UTC,"Probably need to change the device to full functional state before S3, like how basic power management works."
1705748,2017-07-29 10:03:53 UTC,"I have also just noticed that the nvme drive seems to disappear 2 or 3 minutes after the system has re-awakened, so whilst it consistently seems to happen *after* resume from S3, it is not *on* resume."
1705748,2017-07-28 13:15:18 UTC,"Unfortunately there seems no improvement, system boots fine, and operates fine, but nvme disappears again after suspend. However I didn't see any spontaneous disappearance of device (so could be some progress ? but will need to test for longer to be certain)"
1705748,2017-07-25 22:25:42 UTC,"Ok, thanks, will try and report back..."
1705748,2017-08-03 09:32:26 UTC,So last night I installed the kernel and it seems the issue persists:
1705755,2017-11-16 16:48:56 UTC,Sorry for a long post.
1705755,2017-11-17 14:36:07 UTC,Akihiro thanks for the insight.
1705755,2017-11-21 20:27:10 UTC,The discussion in the drivers meeting http://eavesdrop.openstack.org/meetings/neutron_drivers/2017/neutron_drivers.2017-11-16-22.00.log.html#l-86
1705755,2017-12-07 23:57:57 UTC,On November 30th we decided to continue support of neutron python client so we can support API resource attribute extension
1705755,2017-11-30 13:28:17 UTC,(Although I could not join the drivers meeting Nov 16) I see several points:
1705755,2017-12-24 12:06:43 UTC,The meeting log is http://eavesdrop.openstack.org/meetings/neutron_drivers/2017/neutron_drivers.2017-11-30-22.00.log.html#l-18
1705755,2017-11-16 09:38:24 UTC,"Boden,"
1705755,2017-11-21 20:56:19 UTC,RE comment #16 and the neutron drivers meeting.
1705755,2017-11-03 13:06:03 UTC,"Not sure I understand comment #11.
Based on what I see referenced there, the neutron client is being used; not OSC.
The support for ""extra args"" in the neutron client is one of the features that allows the extensions to work with neutron client, but not OSC (OSC doesn't support extra args as far as I know)."
1705755,2017-10-04 15:37:29 UTC,"We are 100% not adding extensions to openstacksdk. If a service offers some API and it wants to be exposed via openstacksdk, add it to openstacksdk. The end."
1705755,2017-10-05 19:25:09 UTC,Let's brainstorm a little on this one during one of the drivers meetings.
1705755,2017-07-21 18:21:48 UTC,"I plan to let this age a little here, and then I'll try to get a slot on the OSC meeting to discuss; say in about 2 weeks time."
1705755,2017-08-07 19:33:05 UTC,Nova does not support stevedore loading of API extensions anymore:
1705755,2017-08-09 15:24:21 UTC,"Matt: thanks for the info on nova's approach to API extensions. Admittedly I'm out of sync with nova, but it's good to understand how other projects are approaching to the topic."
1705755,2017-08-09 15:31:08 UTC,"In regards to the ""gap"" herein specifically with neutron support in OSC; resource attribute extensions today have the following problems:
- They must redefine the entry points they want to override. For example [1][2]. While this works sometimes, there's no guarantees as to which entry point will be loaded first/last.
- They must duplicate the ""base action"" code since there's no way to extend them in base OSC. For example [3]. Ideally extensions can reuse OSCs functionality only providing the difference they need. Without such constructs the code in the client extension can get out of sync with the base OSC (since it duplicates code).
- There's still no way to add attributes to collect/display in the SDK resource. Thus even if the above things are done, the attribute(s) are not collected/shown in the OSC CLI output."
1705755,2017-11-02 23:10:51 UTC,just a data point:
1705755,2017-08-10 18:10:00 UTC,"I don't really get what you're asking here with regards to SDK. If you want to add things to SDK, just add them. Turning it into a mess of feature plugins would go the opposite direction of one of the reasons the project exists in the first place."
1705755,2017-10-04 15:23:28 UTC,"Brian: please see #b under the problem description in the defect text.
Non-stadium projects are not supposed to be adding ""custom"" logic to OSC/SDK/etc. so therein lies one gap."
1705755,2017-10-04 18:37:08 UTC,I think what @boden tries to get is affirmation that gaps between neutronclient and OSC can be solved by adding implementation for missing Neutron APIs (including those that add new attributes to existing resources like port or network) to OSC itself.
1705755,2017-08-09 21:06:44 UTC,Related ML discussions:
1705761,2018-03-02 15:04:52 UTC,Huge page support was added in vrouter from R4.1 to do away with the contiguous memory requirement.
1705761,2018-03-02 15:05:25 UTC,https://bugs.launchpad.net/juniperopenstack/+bug/1728925 was the bug in which the change was committed.
1705762,2018-03-13 03:13:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/552256"
1705762,2018-03-13 12:13:25 UTC,"True Jeremy, iirc  the problem with that solution is that we would need to pass on into the cluster the swift credentials which is not the safest thing to do. But, once we clear that we have SSL/TLS communication between Sahara and cluster we can certainly review this and make the change."
1705762,2017-07-21 19:53:37 UTC,Another possible solution is moving job binary retrieving to be inside the cluster itself instead of inside Sahara.
1705766,2017-07-21 19:42:39 UTC,"When 16.04 LTS was released, PowerDNS had not yet reached a full 4.0.0 release; a pre-release version was included into xenial with the understanding that at some point an update would be made to a point release. I filed bug 1652392 to suggest that this should happen but of course have not found time myself to prepare packages for testing."
1705766,2017-07-22 10:12:05 UTC,"Upstream says this bug was fixed in 4.0.4. Zesty is on 4.0.3-1, so this bug presumably also affects Zesty (17.04)?"
1705766,2017-07-22 10:18:49 UTC,"> So I suggest rather than backporting this specific fix we should instead focus on updating 16.04 LTS to include an actual released version of PowerDNS.
"
1705766,2017-08-13 18:30:54 UTC,"PDNS 4.0.0-alpha2 in Xenial is horribly broken(*) so IMO it seems a bit of a waste of effort backporting this specific fix, without also backporting the critical fixes from 4.0.0 alpha 3 and later, which in turn would be best done by going straight to 4.0.0 release (or 4.0.4+)"
1705766,2017-08-13 18:32:23 UTC,"P.S. Changelogs for 4.0.0 alpha3, beta1, rc2 and release are here:
https://doc.powerdns.com/authoritative/changelog/4.0.html#powerdns-authoritative-server-4-0-0"
1705766,2017-08-13 19:02:08 UTC,"> ...IMO it seems a bit of a waste of effort backporting this specific fix, without also backporting the critical fixes from 4.0.0 alpha 3 and later, which in turn would be best done by going straight to 4.0.0 release (or 4.0.4+)
"
1705767,2019-01-29 20:57:40 UTC,Taking the milestone off as to not set unrealistic expectations.
1705767,2017-12-05 20:31:12 UTC,Tagging canonical-bootstack as we run into this when troubleshooting a deployment and not wanting to destroy the live-working model for a single space addition or rename for one or two charms.
1705790,2017-09-11 19:29:17 UTC,Confirmed in 3.0 beta.  My preference here would be to couple this with a previous/next mechanism while in Detail View as described in bug 1609950.
1705799,2017-08-14 01:31:46 UTC,Is there any progress?
1705799,2017-07-27 01:37:52 UTC,"Oh, unfortunately, I cat't test v4.13 now. Becase the cpu I use is Amlogic S905x(ARMv8), and its USB host is not working in mainline, so I can't move the window via a USB mouse."
1705799,2017-07-26 17:46:08 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1705799,2017-07-22 11:11:22 UTC,apport information
1705799,2017-07-22 11:11:20 UTC,apport information
1705799,2017-07-22 11:22:26 UTC,You can refer to https://youtu.be/TTgallD_Fxo for the video.
1705799,2017-07-22 04:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1705799,2017-07-22 11:11:17 UTC,apport information
1705807,2017-07-22 06:11:52 UTC,Adding lsusb output for the device.
1705808,2017-08-31 06:24:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705813,2017-07-22 09:22:51 UTC,I even can't reboot the system:
1705813,2017-08-02 20:08:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705813,2017-08-02 20:10:15 UTC,"root@Ubuntu-1604-xenial-64-minimal ~ # apt update && apt upgrade
Hit:1 http://mirror.hetzner.de/ubuntu/packages xenial InRelease
Hit:2 http://mirror.hetzner.de/ubuntu/packages xenial-backports InRelease
Hit:3 http://mirror.hetzner.de/ubuntu/packages xenial-updates InRelease
Hit:4 http://mirror.hetzner.de/ubuntu/security xenial-security InRelease
Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:6 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Hit:7 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:8 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
Ign:9 http://download.webmin.com/download/repository sarge InRelease
Hit:10 http://download.webmin.com/download/repository sarge Release
Hit:11 http://dl.ubnt.com/unifi/debian testing InRelease
Hit:13 https://deb.nodesource.com/node_7.x xenial InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
34 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 libpam-systemd : Depends: systemd (= 229-4ubuntu19)
 systemd : Depends: libsystemd0 (= 229-4ubuntu17) but 229-4ubuntu19 is installed
E: Unmet dependencies. Try using -f.
root@Ubuntu-1604-xenial-64-minimal ~ # apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic linux-image-4.4.0-78-generic
  linux-image-extra-4.4.0-78-generic
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  systemd
Suggested packages:
  systemd-ui systemd-container
The following packages will be upgraded:
  systemd
1 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
3 not fully installed or removed.
Need to get 0 B/3,811 kB of archives.
After this operation, 12.3 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 157791 files and directories currently installed.)
Preparing to unpack .../systemd_229-4ubuntu19_amd64.deb ...
Unpacking systemd (229-4ubuntu19) over (229-4ubuntu17) ...
Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up systemd (229-4ubuntu19) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Failed to try-restart sys..."
1705813,2018-01-03 16:57:19 UTC,"There seem to be a few other issues going on, from CurrentDmesg.txt:"
1705820,2020-09-14 00:04:38 UTC,Does this package have an owner?  This really needs to be fixed since it blocks every new user of Ubuntu with this network hardware who has automatic upgrades enabled.
1705820,2019-07-07 09:25:35 UTC,Can anyone explain how I can apply this patch easily? It is kind of annoying I have to reinstall every time. Of course I understand that the developers are busy and maybe this issue is not on top of their list. So if anyone can help me how to sort this out myself...
1705820,2019-04-26 13:41:27 UTC,"Running :
Ubuntu 19.04
kernel 5.0.0-14-generic"
1705820,2019-07-27 13:33:20 UTC,"Ernst, you can apply Mabins patch with these commands:"
1705820,2018-11-04 14:50:40 UTC,"Btw. this appears to be a common type of issue with DKMS; eg. bug 1687492 appears to be the same issue in another dkms source package, and the fix was kinda similar."
1705820,2018-11-04 14:49:11 UTC,"Mabin, thanks a lot for your patch, it appears to have fixed this problem for me (with Ubuntu 16.04.5 x86_64 and rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu2)!"
1705820,2018-11-04 14:24:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705820,2017-09-04 22:59:00 UTC,"Mabin, I agree with your solution, see https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1613837/comments/3"
1705820,2017-07-22 16:21:25 UTC,"The attachment ""rtl8812au-4.3.8.12175.20140902+dfsg.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1705820,2019-02-05 07:23:32 UTC,This bug is till today not fixed in Ubuntu 18.04
1705821,2018-09-26 14:46:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705859,2017-07-28 16:53:27 UTC,apport information
1705859,2017-08-05 23:04:04 UTC,Bug persists after upgrade to 4.10.0-30.
1705859,2017-07-28 16:53:37 UTC,apport information
1705859,2017-07-28 16:53:34 UTC,apport information
1705859,2017-07-28 16:53:31 UTC,apport information
1705859,2017-07-28 16:53:30 UTC,apport information
1705859,2017-07-28 16:53:29 UTC,apport information
1705859,2017-07-28 16:53:28 UTC,apport information
1705859,2017-07-28 16:53:25 UTC,apport information
1705859,2017-07-28 16:43:54 UTC,"We are not able to test the upstream kernel at this time. The consensus is that the risk, however unlikely, of extended downtime is too great at this point in our development cycle. It must wait for a break in the action, my apologies."
1705859,2017-07-28 16:53:22 UTC,apport information
1705859,2017-07-28 16:53:21 UTC,apport information
1705859,2017-07-28 16:53:19 UTC,apport information
1705859,2017-07-28 16:53:18 UTC,apport information
1705859,2017-07-28 16:53:16 UTC,apport information
1705859,2017-07-26 17:45:43 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1705859,2017-07-26 17:45:22 UTC,Does this issue go away if you boot back into the prior kernel?
1705859,2017-07-22 23:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1705859,2017-07-28 16:53:24 UTC,apport information
1705859,2017-07-26 18:41:47 UTC,"> Does this issue go away if you boot back into the prior kernel?
  Yes
"
1705861,2017-07-22 23:41:30 UTC,"This bug report seems to be related:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1556156"
1705861,2017-07-23 11:08:52 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1705861,2017-07-23 20:21:59 UTC,Thank you for the detailed explanation. I helped to make sense of all this.
1705861,2017-07-23 22:54:33 UTC,*it helped..
1705863,2020-09-19 15:43:01 UTC,Closing because INVALID: Incomplete.
1705869,2019-07-01 08:01:37 UTC,Thanks for the pointer. I think we should group this with bug 1312376.
1705870,2017-07-23 01:09:37 UTC,"StacktraceSource:
 #0  0x00007fbf77691753 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   [Error: syscall-template.S was not found in source tree]
 #1  0x0000558cc4bfee6d in sd_event_wait ()
 #2  0x0000558cc4bff7f6 in sd_event_loop ()
 #3  0x0000558cc4bc5484 in main ()
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 sd_event_wait ()
 sd_event_loop ()
 main ()"
1705870,2017-07-31 22:54:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705870,2017-10-27 04:27:37 UTC,Not virtual. Occurs a few minutes after boot.
1705870,2017-07-31 23:00:31 UTC,"I've experienced this bug, also in a virtual machine (though with VMware rather than QEMU). See bug 1707792 for details."
1705882,2017-07-24 01:43:27 UTC,"I was experiencing similar problems, sometimes, until recently. The problem went away for me more recently in 17.10. Can you please try live booting:
   http://cdimage.ubuntu.com/daily-live/current/
and see if the problem is fixed there in 17.10?"
1705884,2017-07-24 09:41:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705884,2017-09-09 21:18:52 UTC,"I have this problem with Nvidia GeForce 1080 Ti. Driver version 381.22. Ubuntu 16.04, kernel version 4.10.0-33-generic."
1705884,2017-12-27 20:48:02 UTC,"Had the same symptoms with the latest 4.10.0 kernel. It seems to have gone away in 4.13
sudo apt-get install linux-image-4.13.0-21"
1705885,2018-04-19 11:12:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705906,2017-07-23 13:30:03 UTC,This change was made by a bot.
1705908,2017-07-24 01:40:51 UTC,"No, lags with GUI doesn't happen in Deck 1/2. Everything is fine. I don't know how to try with preview deck and keyboard though."
1705908,2017-07-23 21:21:29 UTC,"I think your code is missing the release part. ""fwd"" has to go back to 0 to stop it."
1705908,2017-07-24 06:39:32 UTC,"Interesting. You can do this with preview deck by starting Mixxx with
Mixxx --developer
Than you can go to the developer menue find the fwd co from the preview deck and set it to 1."
1705913,2020-05-19 16:19:33 UTC,https://github.com/mixxxdj/mixxx/pull/2612
1705913,2020-05-19 19:18:11 UTC,"The title request is indeed fixed, but there's also the very interesting part ""Often times I think of notes I would like to add to a track when it is playing"", thus lp:1879553"
1705913,2017-07-23 21:07:01 UTC,"This request is similar to:
https://bugs.launchpad.net/mixxx/+bug/1277689"
1705915,2017-07-24 09:31:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1705921,2017-08-02 08:43:03 UTC,"I still get only the silly Audio Port error. Is there a way I can tell
dmesg to ignore it?"
1705921,2017-07-26 12:12:48 UTC,"Hmm, can you find the relevant part?
The message ""Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port"" flooded over the dmesg, so we don't know what really happened on ath9k."
1705921,2017-07-26 12:59:40 UTC,Removed the alsa problem.
1705921,2017-07-27 05:44:16 UTC,"There are too much messages are being snipped.
Please provide dmesg from beginning at boot: `journalctl -b -k`.
Also, please provide both message from the kernel I built and from mainline 4.12."
1705921,2017-07-27 11:31:33 UTC,My mainline is 4.10. Is it o.k?
1705921,2017-07-27 11:42:55 UTC,KHF
1705921,2017-07-28 07:12:59 UTC,This is super weird - no ath9k messages in both dmesg.
1705921,2017-07-28 08:09:21 UTC,"Yes. I think ath9k relates to an external wireless card I plugged to upload
these logs. What about brcmfmac? It does appear and allegedly it has to
correspond to the Ampak ap6212 (e.g.
http://linux-sunxi.org/Wifi#Ampak_Devices)."
1705921,2017-07-28 08:38:48 UTC,"Hmm, so I was debugging the ath9k issue all the time."
1705921,2017-07-28 11:24:26 UTC,Sorry for that. Do you have any idea about the brcmfmac?
1705921,2017-07-31 10:42:46 UTC,"Use 4.13-rc2 and boot with kernel parameter ""brcmfmac.debug=1FFFFE"". Attach the dmesg afterwards."
1705921,2017-07-31 13:43:42 UTC,I didn't put the parameter in brackets. Hope it's fine.
1705921,2017-07-31 14:22:09 UTC,Tons of unrelated messages...
1705921,2017-07-26 11:29:01 UTC,Attached.
1705921,2017-08-02 04:31:27 UTC,Checked it once again. The moment I add this parameter to the kernel it gives only the audio message. When I boot I get `1FFFFE is invalid for parameter debug`. Maybe it's related?
1705921,2017-08-02 07:22:19 UTC,"Oops, it should be ""0x1FFFFE"" instead. Sorry."
1705921,2017-08-03 07:31:49 UTC,You can blacklist your audio kernel module.
1705921,2017-07-26 10:29:05 UTC,Please attach output of dmesg.
1705921,2017-07-23 19:22:51 UTC,apport information
1705921,2017-07-26 09:02:38 UTC,i386 variant: http://people.canonical.com/~khfeng/lp1705921/i386/
1705921,2017-07-23 16:19:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1705921,2017-07-26 09:49:50 UTC,Still no connection.
1705921,2017-07-23 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1705921,2017-07-23 19:22:47 UTC,apport information
1705921,2017-07-23 19:22:49 UTC,apport information
1705921,2017-07-23 19:22:52 UTC,apport information
1705921,2017-07-23 19:22:53 UTC,apport information
1705921,2017-07-23 19:22:54 UTC,apport information
1705921,2017-07-23 19:22:56 UTC,apport information
1705921,2017-07-23 19:22:48 UTC,apport information
1705921,2017-07-23 19:22:58 UTC,apport information
1705921,2017-07-26 07:28:40 UTC,Please try linux kernel here: http://people.canonical.com/~khfeng/lp1705921/
1705921,2017-07-24 15:37:59 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1705921,2017-07-23 19:23:17 UTC,apport information
1705921,2017-07-23 19:22:57 UTC,apport information
1705921,2017-07-23 19:23:03 UTC,apport information
1705921,2017-07-23 19:22:59 UTC,apport information
1705921,2017-07-26 07:49:47 UTC,My architecture is i386 and not amd64. Do you have the kernel for my architecture?
1705921,2017-07-23 19:23:00 UTC,apport information
1705924,2017-07-25 09:46:48 UTC,Thanks Anastasia. How about:
1705924,2017-07-26 00:28:24 UTC,"The quick answer is that ""allocating"" is the initial agent status when the unit is created."
1705924,2017-07-26 07:10:46 UTC,"OK, so we could use the message to provide more insight, and a shorter
word than 'allocating' in the table. How about 'pending'? It's common to
machine agent, because I think it's the same thing in both cases right?"
1705924,2017-07-26 08:19:19 UTC,"If memory serves, we used to use ""pending"" for both machine and unit agents. However, several people did a review of things and the advice was that for units, ""allocating"" was better, as in the machine on which the unit is to be run is being allocated by the cloud. But if length is an issue, then I guess we can change it back to ""pending""."
1705924,2017-07-26 12:02:26 UTC,"How about 'holding'? I think there's some benefit to a unique word
because then things like IRC and bug reports don't need a second round
of questions for disambiguation."
1705924,2017-07-26 12:56:31 UTC,"Yeah, the disambiguation aspect also come into the decision to rename the ""pending"" unit status, now that you mention it."
1705924,2017-07-26 13:30:20 UTC,"Booting would be better for the machine agent :) It's a good word but I
think it will confuse people. What's really happening is waiting-for-boot :)"
1705924,2017-07-26 20:20:18 UTC,"""queued"" sounds great to me"
1705924,2017-07-28 00:32:00 UTC,"Mark,"
1705924,2017-07-28 07:47:54 UTC,"On 28/07/17 01:32, Anastasia wrote:

> We can, however, display the values that you are suggesting in tabular
> format only.
"
1705924,2017-07-25 04:00:08 UTC,This is the list of all agents' status values.
1705938,2019-11-05 04:17:47 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1705938,2017-07-24 20:28:08 UTC,Thank you Brian for your help.
1705938,2017-07-24 20:15:23 UTC,"This isn't a bug with ubuntu-release-upgrader which performs the release upgrade, rather with the system after upgrading. Subsequently, I'm removing the package assignment. You'll want to report the bug about the desktop environment, gnome or unity, that you are using."
1705938,2019-09-05 17:22:38 UTC,"Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1705947,2017-07-28 10:56:15 UTC,"Actually, it appears this issue is caused by a bug in libgnutls:"
1705951,2018-02-15 18:16:19 UTC,"After a number of updates I've retried a couple scenarios:
1) noveau driver and wayland : froze ~30 seconds after login (I clicked on terminal from the dock)
2) noveau driver and xorg : freezes from time to time.  System preferences never opens and sometimes freezes the entire system"
1705951,2017-12-20 12:09:55 UTC,"Same here! If I remove the drive everything works, but I need it to work with TensorFlow"
1705951,2017-10-30 20:19:49 UTC,"I have an NVIDIA GeForce GTX 960M with Intel HD Graphics 530. Now I am able to login the xorg session with discrete gpu. The freeze happens when I try to login with intel and xorg. I've tried intel and wayland session but the fan goes full trottle, with acpi_osi= boot parameter the fan acts normal but i have wayland and gnome-shell processes duplicated one owned by user and one by gdm."
1705951,2017-11-15 02:40:24 UTC,"Old NVIDIA G73 (GeForce 7600 GS) here.  Fresh install.
Freezes with Wayland and xorg using the nouveau driver, also seeing various flashing and other issues when using the recommended nvidia driver (+ freezes)."
1705951,2017-07-31 18:31:18 UTC,"Updates continued and the picture changed. Now I can not get in any way. Start with cd-live and everything works fine. Start the installation and everything happens normally. Restart the PC and the login screen appears. I enter the password, press enter and ... freeze! Nothing else is possible."
1705951,2017-07-31 10:02:54 UTC,"don't install the nvidia driver then, if the stock nouveau driver works?"
1705951,2017-07-27 19:47:32 UTC,"I start with cd-live and everything works perfectly. I install the system and the process runs normally. I reboot, log in and ... freezes. What did the installer do wrong?"
1705951,2017-10-20 23:30:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705951,2017-07-25 18:16:16 UTC,"Since I posted this report, some updates were made available, but the situation got worse. Soon after the log, the screen turns black with no action alternatives. In the ""GNOME Classic"" mode that was previously able to access the system, it is now freezing too. :("
1705960,2017-07-24 14:03:30 UTC,"My experience with this driver or any broadcom wl or wl/bt card is that it is too much trouble to deal with. I pulled both of them I had and replaced them with Intel cards which have great support and 'just work'. Amazon or newegg or wherever has great intel cards that work for about $25.00.  It is not too much trouble to rip the broadcom card out. Broadcom does not appear to support Linux WL driver development for whatever reason. I get that you are usually stuck with whatever is in the laptop you buy. That is a sticking point but if you want to timker, great. If you want to use the laptop for work, get a different card. I've worked with broadcom cards for about 5 years (since ubuntu 10.04) and am just done. I had a 5ghz card which would only work at 2.5 and then only sporadically. Disconnects no reconnect, type in correct password and no connect, suspend and no reconnect on resume, etc. I'm unsubscribing from bug and done with BC WL cards."
1705960,2020-08-20 15:22:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1705960,2020-08-20 15:23:38 UTC,This seems to be an issue still in 20.04.1
1705967,2017-08-06 14:03:50 UTC,"Hi Hyunsun Moon,"
1705967,2017-08-07 09:03:18 UTC,"Hi Hyunsun Moon,"
1705969,2017-08-02 09:41:48 UTC,I am also having frequent Cinnamon crashes with latest Mint 18.2 on a more powerful laptop.
1705969,2017-09-08 20:43:05 UTC,"Try removing the legacy Intel graphics driver ""xserver-xorg-video-intel"" and see if that fixes it:
sudo apt remove xserver-xorg-video-intel"
1705969,2017-09-10 23:19:14 UTC,"I am getting a cinnamon crash about once per day. It started also when I updated from 18.1 to 18.2. I updated without reinstalling. There is another bug report about this cinnamon crashing where some have upgraded with new install, so updating may not be the cause. In that other bug report it was recommended to upgrade from libcjs0f (3.4.3+sonya) to 3.4.4+sonya. I did that and still get crashes. I was supposed to be fixed in libcjs0f 3.4.4"
1705970,2017-07-29 07:27:44 UTC,"Amendment 1:
The login screen of LightDM shows a background image with only a rough rendering of the grey phases. It seems that LightDM uses something like a ""provisional"" graphics device."
1705973,2017-07-28 13:51:48 UTC,"Fix committed into lp:miral at revision 570, scheduled for release in miral, milestone Unknown"
1705985,2017-07-24 10:07:55 UTC,probably a duplicate of bug 1628289 ... does installing snapfuse fix it ?
1705985,2017-07-24 23:23:00 UTC,"I assume you mean squashfuse instead of snapfuse, and it is already installed in the container, so that's not it.  Are there any other dependencies that it could be missing?"
1705985,2019-10-15 12:38:26 UTC,I'm marking this as incomplete. If there was absence of the snap/squash-fuse package it is now automatically bundled by snapd. If there was something else (this is unclear from the information provided thus far) please try to clarify.
1705985,2019-12-15 04:17:39 UTC,[Expired for snapd because there has been no activity for 60 days.]
1705988,2019-11-26 04:17:33 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1705988,2019-11-26 04:17:31 UTC,[Expired for snapd because there has been no activity for 60 days.]
1705988,2019-09-20 08:06:37 UTC,"I'm switching this bug to incomplete because the last update was over two years ago. Dear reporter, can you please look at assessing this issue again? Is it still a problem?"
1705988,2017-07-26 07:13:44 UTC,"AIUI there a a few AppArmor patches that have not yet landed upstream,
for confinement. For the rest, vanilla latest upstream should work, most
of the things snapd requires have landed."
1705988,2019-11-26 04:17:29 UTC,[Expired for juju because there has been no activity for 60 days.]
1705988,2017-07-26 04:12:46 UTC,"root@peleg:~# snap version
snap    2.26.9
snapd   2.26.9
series  16
ubuntu  17.04
kernel  4.12.0-041200-generic
root@peleg:~# snap list
Name  Version    Rev   Developer  Notes
core  16-2.26.9  2381  canonical  -
root@peleg:~# snap refresh
All snaps up to date."
1705988,2017-07-25 18:45:11 UTC,"If you are installing snaps in an LXD container, you also need to make sure
you have squashfuse installed (and possibly also 'fuse' as there may be a
problem with the dependencies).
They were looking to add those into the default images (since snapd is also
there), but its possible your image is older than that."
1705988,2017-07-25 13:41:38 UTC,I think this is related to the lxd container. Can you tell me if it has apparmor stacking enabled or runs unconfined? The error message (cannot change profile for the next exec call: No such file or director) seems to say that snap-confine cannot change the apparmor profile for during the exec call. This implies writing to /proc/$PID/attr/exec so maybe the container limits (in whatever way) access to procfs?
1705988,2017-07-25 12:54:23 UTC,"What is the output of: ""snap version"" on the system where this fails? Fwiw, it works fine on my 2.26.14 based machine. So any hint on what I can do to reproduce is appreciated."
1705988,2017-07-26 04:13:27 UTC,Maybe this is related to the fact that I'm running a generic kernel?  (The zesty kernels are unstable on my machine.)
1705988,2017-07-25 04:34:51 UTC,I created a fresh zesty lxd container (installed squashfuse to let snap work in a container) and tried to install juju as per commented in the bug and it installs fine for me.
1705992,2017-08-11 13:21:21 UTC,"Reviewed:  https://review.openstack.org/486522
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=dc2daad2fc4ac6b3d5b7d0f6fdbedfcd9159ff83
Submitter: Jenkins
Branch:    master"
1705992,2020-02-17 14:49:32 UTC,"The cluster driver is now properly cleaning up resources after failovers if the source host is still available, especially since distributed locking was introduced by I3dbdcf208bb7a96bd516b41e4725a5fcb37280d6."
1705994,2019-02-26 13:49:50 UTC,Is this still needed?
1705994,2019-02-27 07:52:59 UTC,"Hey,
No, I think this is not needed anymore,
It looks like there is no real business value in this scenario
You can close it.
Thanks
Raviv"
1705997,2017-12-05 05:57:27 UTC,"Noticed this bug in 0.66 as well, on Win7, and it persists into 0.67 (also Win7).  Poked around in a file where I'd linked a few images and think I've figured out what's off.  (Fortunately for me I link few enough images that for the time being I'm willing to fix this manually on a per-case basis.)"
1705998,2017-08-07 16:05:08 UTC,"Hi,"
1705998,2017-08-05 18:59:14 UTC,"Carlos, I don't want to nit pick, but the changelog is wrong -
The *only* reason pt-online-schema-change failed the ALTER, and did not end up with silent data corruption is that the column *happen* to not have a default value. If the column had default value, the tool would have ran and swap the tables, leading to data loss."
1705998,2018-01-24 22:27:43 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-737
1705998,2017-08-04 16:11:20 UTC,"Thanks, Carlos.
I am still not sure the severity is accurate.
This bug could easily lead to silent data loss, while using perfectly legal
column names - this classifies as very high severity in my opinion."
1705998,2017-08-07 16:21:30 UTC,"And the mixed case is perfectly legal and valid. So a perfectly legal and
valid usage can lead to silent data loss. This ranks as a severe bug in my
book."
1705998,2017-08-03 14:03:57 UTC,"pt-online-schema change is already using lowercase.
You need to specify the column name in lowercase."
1705998,2017-08-04 22:30:32 UTC,Fix committed: https://github.com/percona/percona-toolkit/pull/252
1705998,2017-08-03 07:06:31 UTC,"I think this is high priority, because this can lead to silent data corruption if the column has a default value."
1705998,2017-08-03 07:07:39 UTC,The fix is also very trivial (lower case both sides when comparing).
1705998,2017-08-02 05:50:26 UTC,"Please provide a test case that we can reproduce, like a simple table and the full pt-osc command you used to alter this table. We will also need the exact pt-osc version used and errors encountered when the tool was executed."
1705998,2017-08-02 11:28:22 UTC,"I will, but it seems like *any* alter which involves uppercase column names in renaming columns ALTER will trigger it."
1705998,2017-08-03 15:19:04 UTC,"Carlos, I beg to differ. Using the column name in upper case is valid, as
column names are case insensitive, and pt-online-schema-change should
adhere to this rule.
One could easily copy and paste from SHOW CREATE TABLE, which retains the
case, and suffer from silent data loss. Saying that column names should be
specified in lower case is both against mysql's syntax rules, and also not
documented in pt-online-schema-change documentation."
1705998,2017-08-03 06:23:19 UTC,I can't seem to repeat it with latest pt-osc 3.0
1705998,2017-08-03 06:33:11 UTC,"The problem is not that the column is not created, but that it is not detected as *common* column, and therefore not included in the chunk copy SELECT.
Run with PTDEBUG=1 and look for the common columns line."
1705998,2017-08-03 06:59:43 UTC,"I got it now, and I can confirm the bug. If column is all lowercase the alter will not fail."
1705998,2017-08-02 12:11:51 UTC,Test schema:
1705999,2017-07-24 12:26:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1706041,2017-07-24 11:17:58 UTC,"Jeremy, could you have a look? those report started with your update it seems"
1706041,2019-11-27 20:27:33 UTC,The issue looks like https://bugzilla.gnome.org/show_bug.cgi?id=782738 which was fixed with the next version
1706045,2020-01-14 22:22:54 UTC,"This bug has been fixed in the major maintenance performed on the wordpress charm, now known as cs:wordpress-0."
1706046,2017-07-25 08:39:57 UTC,"Fix proposed to branch: stable-mu/8.0
Review: https://review.openstack.org/486944"
1706046,2018-02-27 14:36:41 UTC,"Change abandoned by Alexey Stepanov (<email address hidden>) on branch: stable-mu/8.0
Review: https://review.openstack.org/486944
Reason: mu8 is not supported anymore"
1706052,2017-08-15 08:25:55 UTC,apport information
1706052,2017-08-15 08:26:40 UTC,"Ok, so if I pick in the ""Text"" dialog ""yes"", it sends a report, and it also gives the following error inside ""lpstat: Bad file descriptor"". Indeed, if I run /usr/bin/lpstat I get the error:
lpstat: Bad file descriptor"
1706052,2017-10-02 00:28:19 UTC,From /var/crash
1706052,2017-10-02 00:34:55 UTC,Ubuntu 17.04 4.10.0-35-generic amd64 (upgraded from Wiley->Xenial->Zesty)
1706052,2017-10-04 19:42:04 UTC,Workaround:
1706052,2017-10-04 20:01:35 UTC,"HuaiDan (dhutchison69), if this works for you, please post all the CUPS-related ""audit"" lines from your /var/log/syslog file."
1706052,2017-10-05 03:20:57 UTC,Here's something else you may want to look at: The apparmor profile on my machine for cups.
1706052,2017-10-04 21:37:56 UTC,"Here's one set:
[  189.457095] audit: type=1400 audit(1507146357.726:48): apparmor=""STATUS"" operation=""profile_replace"" profile=""unconfined"" name=""/usr/sbin/cups-browsed"" pid=2784 comm=""apparmor_parser""
[  216.802135] audit: type=1400 audit(1507146385.075:49): apparmor=""ALLOWED"" operation=""open"" profile=""/usr/sbin/cups-browsed"" name=""/proc/2864/cmdline"" pid=2864 comm=""cups-browsed"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0
[  217.974857] audit: type=1400 audit(1507146386.247:50): apparmor=""ALLOWED"" operation=""open"" profile=""/usr/sbin/cupsd"" name=""/proc/2871/cmdline"" pid=2871 comm=""cups-exec"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0
[  217.978903] audit: type=1400 audit(1507146386.251:51): apparmor=""ALLOWED"" operation=""open"" profile=""/usr/sbin/cupsd"" name=""/proc/2871/cmdline"" pid=2871 comm=""dbus"" requested_mask=""r"" denied_mask=""r"" fsuid=7 ouid=7
[  358.429024] audit: type=1400 audit(1507146526.583:52): apparmor=""ALLOWED"" operation=""open"" profile=""/usr/sbin/cupsd"" name=""/proc/3294/cmdline"" pid=3294 comm=""cups-exec"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0
[  358.429102] audit: type=1400 audit(1507146526.583:53): apparmor=""ALLOWED"" operation=""open"" profile=""/usr/sbin/cupsd"" name=""/proc/3295/cmdline"" pid=3295 comm=""cups-exec"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0
[  358.429204] audit: type=1400 audit(1507146526.583:54): apparmor=""ALLOWED"" operation=""open"" profile=""/usr/sbin/cupsd"" name=""/proc/3296/cmdline"" pid=3296 comm=""cups-exec"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0
[  358.429339] audit: type=1400 audit(1507146526.583:55): apparmor=""ALLOWED"" operation=""open"" profile=""/usr/sbin/cupsd"" name=""/proc/3297/cmdline"" pid=3297 comm=""cups-exec"" requested_mask=""r"" denied_mask=""r"" fsuid=0 ouid=0"
1706052,2017-10-04 21:42:21 UTC,"I also did
aa-complain /usr/sbin/cups-browsed"
1706052,2017-08-15 08:25:51 UTC,apport information
1706052,2017-10-05 19:14:07 UTC,"Everyone with this problem, can you please add a line"
1706052,2017-10-05 23:32:21 UTC,"Here's what we've got so far:
Cups is back online and working in enforce mode. No errors are thrown, no crash reports.
HPLIP toolbox shows the printer and the right information.
I am able to print."
1706052,2017-10-05 23:33:07 UTC,"Thanks BTW, good work."
1706052,2017-10-06 13:20:54 UTC,"Thanks, so the adding of said line to usr.sbin.cupsd helps?"
1706052,2017-10-06 16:04:06 UTC,"Yes,
@{PROC}/*/cmdline r,
and resetting to enforce fixed the printing problem. For the record, the same solution also worked for a problem I was having with the dhclient apparmor profile that was stopping NetworkManager from connecting."
1706052,2017-10-04 20:18:55 UTC,"Ok really strange, after running once with aa-complain, it seems to solve the problem."
1706052,2017-08-15 08:25:50 UTC,apport information
1706052,2017-10-01 22:13:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706052,2017-08-15 08:25:48 UTC,apport information
1706052,2017-08-15 08:25:49 UTC,apport information
1706052,2017-07-24 15:29:25 UTC,"If you start cupsd from the command line and it reproducably crashes (or it at least crashes often enough so that you can easily get it to crash), please do the following:"
1706052,2017-07-27 22:37:20 UTC,"Attaching, the output from gdb is:"
1706052,2017-07-28 18:29:17 UTC,"Thanks for the reply, but if you run the gdb command from comment #2, it does not exit, but it stays running with its own command prompt."
1706052,2017-07-28 22:51:49 UTC,"Sorry, missed that last part.
Here is the full output:"
1706052,2017-08-14 08:26:48 UTC,"Hey, I updated the bug report, can you please update it and change it from incomplete?"
1706052,2017-08-14 22:31:24 UTC,"Unfortunately, your gdb backtrace is touching nowhere the code of CUPS, probably due to being a sub thread which was created somewhere in the libraries."
1706052,2017-08-14 22:38:35 UTC,Another posibility is to check whether there is already a crash report file. You can attach it to this bug report.
1706052,2017-08-15 08:24:29 UTC,"Well the good news there is a /var/crash/_usr_sbin_cupsd.1000.crash file.
The bad (not so bad) news is, well this is what apport-collect 1706052 outputs this amazing question dialog (what do I pick?)."
1706052,2017-08-15 08:25:54 UTC,apport information
1706052,2017-08-15 08:25:35 UTC,apport information
1706052,2017-08-15 08:25:37 UTC,apport information
1706052,2017-08-15 08:25:41 UTC,apport information
1706052,2017-08-15 08:25:42 UTC,apport information
1706052,2017-08-15 08:25:43 UTC,apport information
1706052,2017-08-15 08:25:44 UTC,apport information
1706052,2017-08-15 08:25:45 UTC,apport information
1706052,2017-08-15 08:25:46 UTC,apport information
1706052,2017-08-15 08:25:47 UTC,apport information
1706052,2017-08-15 08:25:34 UTC,apport information
1706058,2017-09-06 14:34:12 UTC,"Hi Victor,
I'm currently updating bugs on our virt-stack that are open but seem dormant."
1706058,2017-09-06 15:06:30 UTC,"Hi Christian,"
1706058,2017-07-26 10:49:48 UTC,"To confirm the issue described in the original fix, I traced the virtio balloon subsystem (using QEMU simpletracing) while the VM:"
1706058,2017-07-24 14:09:10 UTC,Thanks Thomas!
1706058,2017-08-07 12:40:22 UTC,Thanks Victor for bringing this up and working on it!
1706058,2017-07-24 13:46:57 UTC,Please make sure to use the right target for downstream bugs ==> Re-assigned this to qemu-ubuntu
1706083,2017-07-24 15:30:56 UTC,Here's the change to fix this issue:
1706083,2017-07-28 16:15:16 UTC,"Reviewed:  https://review.openstack.org/485752
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=14c38ac0f253036da79f9d07aedf7dfd5778fde8
Submitter: Jenkins
Branch:    master"
1706083,2017-07-29 15:18:31 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/488959"
1706083,2017-07-31 12:18:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/489198"
1706083,2017-08-11 12:27:19 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1706083,2017-08-15 16:04:34 UTC,"Reviewed:  https://review.openstack.org/489198
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=306b3f1aac4fc30ee14a7f5f66474d68860768fa
Submitter: Jenkins
Branch:    stable/ocata"
1706083,2017-08-21 13:54:23 UTC,"Reviewed:  https://review.openstack.org/488959
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1797d73efc0601a0a664d32a127669e93bce3d45
Submitter: Jenkins
Branch:    stable/newton"
1706083,2017-08-22 11:38:50 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1706083,2017-08-28 09:55:12 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1706085,2017-07-25 17:46:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706092,2017-07-24 14:56:35 UTC,"[root@chadcloud1 network-scripts(keystone_admin)]# manila list
+--------------------------------------+------+------+-------------+----------+-----------+-----------------+-------------------------------------------+-------------------+

| ID                                   | Name | Size | Share Proto | Status   | Is Public | Share Type Name | Host                                      | Availability Zone |


+--------------------------------------+------+------+-------------+----------+-----------+-----------------+-------------------------------------------+-------------------+

| f10b9908-d662-4454-9d65-a0fb0c2b6bac | None | 1    | NFS         | creating | False     | multi           | chadcloud1@cdot_multi#openstack1_sas_aggr | nova              |


+--------------------------------------+------+------+-------------+----------+-----------+-----------------+-------------------------------------------+-------------------+"
1706092,2019-10-28 18:33:28 UTC,Do we have any updates on this issue?
1706109,2018-02-16 21:43:47 UTC,Handle authentication issues when a service provider's keystone is down.
1706109,2018-06-08 21:07:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/573832"
1706111,2017-07-24 16:12:46 UTC,This seems to be related to: https://bugzilla.redhat.com/show_bug.cgi?id=1456134
1706111,2017-07-24 16:13:50 UTC,"Note that I still see this even when the terminal comes up fast:
Jul 24 11:12:48 iolanthe org.gnome.SettingsDaemon.MediaKeys.desktop[6820]: Warning: DESKTOP_STARTUP_ID not set and no fallback available."
1706112,2019-02-26 18:44:12 UTC,Yea I don't think we ever fixed this
1706112,2019-02-26 13:50:06 UTC,Is this still an issue?
1706114,2017-07-24 16:23:48 UTC,Added the bug into GNOME's  Bugzilla.
1706114,2017-07-24 16:31:15 UTC,"Added Linux Mint and Debian projects to the report as well, as both use the same (or similar) vino and vino-server packages."
1706114,2018-02-18 11:57:14 UTC,"Adding official RDP support should also, I hope, get Microsoft and Amazon's attention to begin using RDP as r default way to remote into virtual machines hosted in their cloud services."
1706114,2018-02-18 11:57:41 UTC,*their default
1706118,2017-09-27 16:35:25 UTC,"Reviewed:  https://review.openstack.org/501746
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b55ca354463a387d79e265701dd78cf3a51e457f
Submitter: Jenkins
Branch:    stable/ocata"
1706118,2017-09-15 22:19:47 UTC,"Reviewed:  https://review.openstack.org/501745
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=423c7bbdb99e14fd49681dd58edd348060f25005
Submitter: Jenkins
Branch:    stable/pike"
1706118,2017-09-07 13:49:55 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/501746"
1706118,2017-09-07 13:49:41 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/501745"
1706118,2017-09-07 02:23:55 UTC,"Reviewed:  https://review.openstack.org/486660
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=05f3d9d39b7b95fac343ba431855482a5d96584a
Submitter: Jenkins
Branch:    master"
1706118,2017-07-24 18:02:49 UTC,The workaround for now is specify the --database_connection option with the 'nova-manage cell_v2 map_cell0' command to avoid the command messing up the URL stored for the cell0 mapping in the nova_api.cell_mappings table.
1706118,2017-07-24 18:01:19 UTC,"As noted in IRC, it sounds like another variant of bug 1673613 which was fixed in Ocata 15.0.5:"
1706137,2020-05-08 22:58:41 UTC,"Reviewed:  https://review.opendev.org/725109
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=66117610f92fe3e7632980ccef007ced7f952385
Submitter: Zuul
Branch:    stable/queens"
1706137,2020-05-03 14:32:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/725109"
1706137,2020-05-03 02:39:24 UTC,"Reviewed:  https://review.opendev.org/723621
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=6e52af90f828c6fc34cad4bd788e9264c321bac0
Submitter: Zuul
Branch:    stable/rocky"
1706137,2020-04-27 17:10:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/723621"
1706137,2020-03-30 18:51:03 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/716044"
1706137,2020-04-25 13:28:30 UTC,"Reviewed:  https://review.opendev.org/716044
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=1fddc0794f89dc9fb8381e622855d76839136c5d
Submitter: Zuul
Branch:    stable/train"
1706137,2020-04-11 02:23:56 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/719132"
1706137,2020-03-13 22:14:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/713073"
1706137,2017-08-09 21:16:17 UTC,"Missed pike, untargetting"
1706137,2020-04-27 15:43:38 UTC,"Reviewed:  https://review.opendev.org/719132
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=15dc973b17cb0557f192a97d1efcb8ce235c54e1
Submitter: Zuul
Branch:    stable/stein"
1706137,2020-03-30 18:38:46 UTC,"Reviewed:  https://review.opendev.org/713073
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=14b75b1fdd753c6d90c301cd4576706024a9356f
Submitter: Zuul
Branch:    master"
1706138,2020-06-10 04:55:28 UTC,"So, it's not a bug, it simply that it's not supported.
What kind of message did you have."
1706165,2017-07-26 13:48:02 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-July/085896.html
1706168,2021-02-19 23:04:57 UTC,This bug was fixed in the package update-notifier - 3.192.40
1706170,2017-07-25 08:12:50 UTC,"Hi, this bug was fixes in master with this commit https://github.com/openstack/kolla-ansible/commit/fdc75cdd8c686d55ad2fcc5b86287a82b853cc78 ."
1706170,2017-07-25 09:44:22 UTC,Thanks a lot.
1706170,2017-12-15 09:11:18 UTC,This issue was fixed in the openstack/kolla-ansible 4.0.3 release.
1706186,2017-07-26 05:09:53 UTC,"Reviewed:  https://review.openstack.org/487260
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=edf75cf9f2a75d795f5882d285b67c24283d7f65
Submitter: Jenkins
Branch:    master"
1706186,2017-07-26 02:52:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/487260"
1706188,2020-02-01 04:17:29 UTC,[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]
1706188,2019-12-02 16:07:19 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1706191,2017-10-05 19:51:55 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/444516"
1706199,2017-07-24 21:09:17 UTC,"Apparently only two people in the FreeDesktop upstream have any interest in this driver. Anyway, here’s a link to the same bug I reported there https://bugs.freedesktop.org/show_bug.cgi?id=101908"
1706199,2018-09-05 09:25:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706199,2020-03-26 16:45:21 UTC,Totally agree. Tapping the touchpad should continue to work normally even after switching the mouse to the left-handed mode.
1706199,2020-11-23 03:08:42 UTC,"Agreed, very unfriendly and existing since 2017. I can confirm it is still present in Ubuntu 20.04.
Does anyone know what this is set to ""Won't Fix""?"
1706200,2017-07-24 21:50:11 UTC,http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2720&p=18146#p18146
1706212,2017-12-27 15:39:20 UTC,The digikam photo management app complains about the standard version of opencv being too old on xenial.
1706217,2017-10-26 13:28:01 UTC,"There's git-format-patch and git-send-email. I think it makes sense for 'git ubuntu' to do things the git way, which would involve sending them like this. git's emailed patches are nice in that the recipient can programatically accept these patches with less metadata loss, and those maintainers not using git wouldn't have a problem accepting git-emailed patches either, as they are straightforward patches."
1706217,2017-10-26 03:42:37 UTC,"I don't think that this necessarily should be a 'git ubuntu' subcommand vs. part of the existing 'submittodebian' command, but I think this is a critically important part of the merge workflow that needs to be supported."
1706219,2018-09-24 23:54:22 UTC,A possible workaround is something along the lines of:
1706219,2018-09-25 00:06:58 UTC,This is somewhat (extremely!) hairy but seems to work:
1706223,2018-07-15 15:24:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706223,2018-02-05 13:37:36 UTC,"Debian maintainer is now Thomas Lange; Seems Christos is now away from that project.
https://salsa.debian.org/debian/tcsh"
1706223,2018-02-03 18:08:04 UTC,Thanks dino99!
1706223,2018-02-03 14:27:07 UTC,Request for archive upgrade:
1706223,2018-01-16 13:03:30 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1706223,2017-09-09 21:31:18 UTC,"The issue has been fixed in https://github.com/MidnightCommander/mc/commit/0fec3ef449de6f22281161ba7af8f5dbb948292d , and is to appear in the next mc release (4.20)."
1706223,2017-09-05 20:20:56 UTC,"The attachment ""mc.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1706223,2017-07-25 00:15:06 UTC,"I'm sorry, actually the Christos have naswered my email, but it got into the spam folder. Let's see if we can get an upstream solution."
1706223,2017-07-25 00:09:41 UTC,"I'm also trying to contact the upstream commit author Christos Zoulas, but he seems to be busy."
1706223,2018-02-01 18:53:35 UTC,"dino99, why should this bug be marked as Invalid? The newer releases (Artful and Beaver-dev) are still (as of today) have the older version (3:4.8.19-1) of Midnight Commander without the patch (upstream release 4.8.20 of 25.11.2017). The newer releases just weren't released in July 2017."
1706223,2017-09-05 19:51:13 UTC,"Christos explained that tcsh escaping is tricky, buggy, and ""fixing"" it in a proper way can break legacy scripts."
1706234,2017-08-22 12:20:07 UTC,"Hello, Linda Yu!
I found several solutions to solve your problem:"
1706234,2017-09-08 06:40:46 UTC,Hi Linda could you please certify what Pavlukhin suggest suit for your cases or not?:)
1706237,2017-08-01 17:19:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706240,2017-07-25 04:07:14 UTC,Is this related to bug #1498142?
1706240,2017-07-30 16:32:16 UTC,"Yes, this is caused by tolua++ only supporting Lua 5.1. However, this should still be provided for Fedora 23: https://www.rpmfind.net/linux/RPM/fedora/26/x86_64/c/compat-lua-devel-5.1.5-7.fc26.x86_64.html"
1706240,2017-07-30 18:00:41 UTC,"Yes. From the link I provided it seems like a ""compat-lua-devel-5.1.5"" package should be available for Fedora."
1706240,2017-07-30 21:32:32 UTC,"I deleted the entire directory structure and started from scratch. The build still fails, but now it reads..."
1706240,2017-07-30 21:34:22 UTC,"FWIW, Fedora 26 requires a ""dnf install compat-lua-devel"" to install Lua 5.1."
1706240,2017-09-02 15:48:51 UTC,With Fedora 26 tolua++ is made to use Lua 5.3.
1706240,2017-07-30 17:44:43 UTC,"OK, but just to make sure I understand correctly. You want me to..."
1706256,2017-07-25 07:11:47 UTC,"Yes, a lovely one. Thanks for sharing. ;)"
1706256,2017-07-26 07:41:50 UTC,Hm I would suggest to document it and leave it be.
1706265,2020-03-05 00:52:51 UTC,"I realized the approach in the PR above will break the existing escaping workarounds used in all such  add_check calls, so I've closed the PR while I try to think of a better idea."
1706265,2020-03-04 01:10:31 UTC,"PR won't work as-is, since shlex.quote is very new."
1706265,2020-03-04 00:45:17 UTC,https://github.com/juju/charm-helpers/pull/438
1706265,2020-03-04 02:10:33 UTC,Updated PR with adapted copy of shlex.quote etc. from Python 3.8 to use as a fallback.
1706265,2020-03-04 00:37:48 UTC,I think it's because Check.__init__ does this:
1706274,2017-09-14 16:37:14 UTC,"I'm not 100% sure, since this module is a parser and not a serializer, but it appears HTML::HTML5::Parser is just building a DOM, and the serialization is then done by XML::LibXML. Therefore, it seems likely the bug is indeed in HTML::HTML5::Parser."
1706274,2017-09-14 16:45:16 UTC,"I was able to reproduce the bug, and I have committed the example as test data to my own fork of the module: https://github.com/kjetilk/p5-html-html5-parser/commit/c4be3e6ee63d0850079c115ef4274e4c2c3befa9
I'm not a maintainer, so it doesn't bring us much closer to a solution though. Just did it since I have a fork :-)"
1706285,2017-07-26 16:05:35 UTC,The iptables defer_apply() code is a little better in that it catches the exception in defer_apply_off() and raises a consistent value.
1706290,2017-07-25 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1706290,2017-07-25 09:44:14 UTC,we can not use the command apport-collect 1706290 .
1706290,2017-07-27 16:30:32 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1706290,2017-07-28 01:21:13 UTC,kernel-bug-exists-upstream
1706296,2017-08-18 12:20:10 UTC,"On Fri, Aug 18, 2017 at 10:23:25AM -0000, Alex Bennée wrote:

> That said from John's update it sounds very much like a symptom of not
> emulating the right processor type rather than behaviour we are
> incorrectly modelling.
"
1706296,2020-11-09 21:18:56 UTC,"With the original repro command line, the guest now crashes ""cleanly"", ie without triggering a QEMU assert. If you give the guest a CPU type it recognizes, eg '-cpu pentium' (as noted in comment 7) then it boots OK, at least to the point of user control in the installer. So I think this is fixed."
1706296,2020-11-09 20:03:13 UTC,"commit 8b81253332b5a3f claims in its subject line that it ""fixes #1706296"", and it implements Paolo's option (2) from comment #4. So I'd go with ""already fixed"". The bug has a simple reproducer in the report though, so it's also easy to test..."
1706296,2020-11-09 18:27:38 UTC,"Was this ever fixed in QEMU, or can the issue still be reproduced in the latest version?"
1706296,2017-08-18 13:32:18 UTC,Actually Windows NT 4.0 requires a 486 or higher. https://en.wikipedia.org/wiki/Windows_NT
1706296,2017-08-18 12:51:30 UTC,"On 18 August 2017 at 11:23, Alex Bennée <email address hidden> wrote:

> If we invert the lock before writing the stack
> page is it just going to crash in a more esoteric way?
"
1706296,2017-08-18 10:33:27 UTC,"On 18 August 2017 at 11:23, Alex Bennée <email address hidden> wrote:

> Peter Maydell <email address hidden> writes:
>> On 18 August 2017 at 09:40, Alex Bennée <email address hidden> wrote:
>>> It might be related. The assertion error is caused by the fact an
>>> exception has occurred and processor is trying to dump a stack frame that
>>> overlaps from RAM into device memory. As the IRQ/exception handling is
>>> already under the BQL (as it changes machine state) we get the assertion
>>> when it tries to take the BQL a second time when accessing device
>>> memory.
>>
>> This sounds worrying -- lots and lots of target backend code
>> does writes to memory. Is it all going to cause assertions if
>> it happens to be pointing at a device?
>
> Currently yes.
>
> That said from John's update it sounds very much like a symptom of not
> emulating the right processor type rather than behaviour we are
> incorrectly modelling. If we invert the lock before writing the stack
> page is it just going to crash in a more esoteric way?
>
> I'm not sure how you correctly emulate writing random stack pages to a
> random device. Unless there is some sort of weird [un]documented behaviour
> we should be doing?
"
1706296,2017-08-18 10:23:25 UTC,Peter Maydell <email address hidden> writes:
1706296,2017-08-18 08:59:41 UTC,"On 18 August 2017 at 09:40, Alex Bennée <email address hidden> wrote:

>
> John Arbuckle <email address hidden> writes:
>
>> Using '-cpu 486' gets past the assertion error. I guess Windows NT 4.0
>> is not compatible with newer Intel processors.
>
> It might be related. The assertion error is caused by the fact an
> exception has occurred and processor is trying to dump a stack frame that
> overlaps from RAM into device memory. As the IRQ/exception handling is
> already under the BQL (as it changes machine state) we get the assertion
> when it tries to take the BQL a second time when accessing device
> memory.
"
1706296,2017-07-25 15:12:56 UTC,"On 25 July 2017 at 15:54, Alex Bennée <email address hidden> wrote:

>
> Thomas Huth <email address hidden> writes:
>
>> On 25.07.2017 11:30, Richard Jones wrote:
>>> ERROR:/home/rjones/d/qemu/cpus.c:1580:qemu_mutex_lock_iothread: assertion failed: (!qemu_mutex_iothread_locked())
>>> Aborted (core dumped)
>>>
>>> The stack trace in the failing thread is:
>>>
>>> Thread 4 (Thread 0x7fffb0418700 (LWP 21979)):
>>> #0  0x00007fffdd89b64b in raise () at /lib64/libc.so.6
>>> #1  0x00007fffdd89d450 in abort () at /lib64/libc.so.6
>>> #2  0x00007fffdff8c75d in g_assertion_message () at /lib64/libglib-2.0.so.0
>>> #3  0x00007fffdff8c7ea in g_assertion_message_expr ()
>>>     at /lib64/libglib-2.0.so.0
>>> #4  0x00005555557a7d00 in qemu_mutex_lock_iothread ()
>>>     at /home/rjones/d/qemu/cpus.c:1580
>>> #5  0x00005555557cb429 in io_writex (env=env@entry=0x555556751400, iotlbentry=0x55555675b678,
>>>     iotlbentry@entry=0x5aaaaae40c918, val=val@entry=8, addr=addr@entry=2148532220, retaddr=0, retaddr@entry=93825011136120, size=size@entry=4)
>>>     at /home/rjones/d/qemu/accel/tcg/cputlb.c:795
>>> #6  0x00005555557ce0f7 in io_writel (retaddr=93825011136120, addr=2148532220, val=8, index=255, mmu_idx=21845, env=0x555556751400)
>>>     at /home/rjones/d/qemu/softmmu_template.h:265
>>> #7  0x00005555557ce0f7 in helper_le_stl_mmu (env=env@entry=0x555556751400, addr=addr@entry=2148532220, val=val@entry=8, oi=<optimized out>, retaddr=93825011136120, retaddr@entry=0) at /home/rjones/d/qemu/softmmu_template.h:300
>>> #8  0x000055555587c0a4 in cpu_stl_kernel_ra (env=0x555556751400, ptr=2148532220, v=8, retaddr=0) at /home/rjones/d/qemu/include/exec/cpu_ldst_template.h:182
>>> #9  0x0000555555882610 in do_interrupt_protected (is_hw=<optimized
>>> out>, next_eip=<optimized out>, error_code=2, is_int=<optimized out>,
>>> intno=<optimized out>, env=0x555556751400) at
>>> /home/rjones/d/qemu/target/i386/seg_helper.c:758
>
> Erm, what is happening here? I think the seg_helper is writing a stack
> frame but for some reason to io memory, triggering the BQL. This just
> seems weird.
"
1706296,2017-07-25 17:54:40 UTC,"* Alex Bennée (<email address hidden>) wrote:

>
> Thomas Huth <email address hidden> writes:
>
> > On 25.07.2017 11:30, Richard Jones wrote:
> >> ERROR:/home/rjones/d/qemu/cpus.c:1580:qemu_mutex_lock_iothread: assertion failed: (!qemu_mutex_iothread_locked())
> >> Aborted (core dumped)
> >>
> >> The stack trace in the failing thread is:
> >>
> >> Thread 4 (Thread 0x7fffb0418700 (LWP 21979)):
> >> #0  0x00007fffdd89b64b in raise () at /lib64/libc.so.6
> >> #1  0x00007fffdd89d450 in abort () at /lib64/libc.so.6
> >> #2  0x00007fffdff8c75d in g_assertion_message () at /lib64/libglib-2.0.so.0
> >> #3  0x00007fffdff8c7ea in g_assertion_message_expr ()
> >>     at /lib64/libglib-2.0.so.0
> >> #4  0x00005555557a7d00 in qemu_mutex_lock_iothread ()
> >>     at /home/rjones/d/qemu/cpus.c:1580
> >> #5  0x00005555557cb429 in io_writex (env=env@entry=0x555556751400, iotlbentry=0x55555675b678,
> >>     iotlbentry@entry=0x5aaaaae40c918, val=val@entry=8, addr=addr@entry=2148532220, retaddr=0, retaddr@entry=93825011136120, size=size@entry=4)
> >>     at /home/rjones/d/qemu/accel/tcg/cputlb.c:795
> >> #6  0x00005555557ce0f7 in io_writel (retaddr=93825011136120, addr=2148532220, val=8, index=255, mmu_idx=21845, env=0x555556751400)
> >>     at /home/rjones/d/qemu/softmmu_template.h:265
> >> #7  0x00005555557ce0f7 in helper_le_stl_mmu (env=env@entry=0x555556751400, addr=addr@entry=2148532220, val=val@entry=8, oi=<optimized out>, retaddr=93825011136120, retaddr@entry=0) at /home/rjones/d/qemu/softmmu_template.h:300
> >> #8  0x000055555587c0a4 in cpu_stl_kernel_ra (env=0x555556751400, ptr=2148532220, v=8, retaddr=0) at /home/rjones/d/qemu/include/exec/cpu_ldst_template.h:182
> >> #9  0x0000555555882610 in do_interrupt_protected (is_hw=<optimized
> >> out>, next_eip=<optimized out>, error_code=2, is_int=<optimized out>,
> >> intno=<optimized out>, env=0x555556751400) at
> >> /home/rjones/d/qemu/target/i386/seg_helper.c:758
>
> Erm, what is happening here? I think the seg_helper is writing a stack
> frame but for some reason to io memory, triggering the BQL. This just
> seems weird.
"
1706296,2017-07-31 20:34:57 UTC,There are three possibilities:
1706296,2017-07-25 14:54:19 UTC,Thomas Huth <email address hidden> writes:
1706296,2017-08-17 18:53:07 UTC,If you forget to add -cpu 486 or -cpu pentium your disk image will be corrupted and the display will display random characters.
1706296,2017-08-18 08:40:31 UTC,John Arbuckle <email address hidden> writes:
1706296,2017-08-10 23:42:55 UTC,Using '-cpu 486' gets past the assertion error. I guess Windows NT 4.0 is not compatible with newer Intel processors.
1706296,2017-08-17 19:20:03 UTC,This workaround should help you avoid problems with Windows NT 4.0.
1706301,2017-07-25 13:44:45 UTC,"On Oocata, I think it might be related to my deployment because at some point we switch form spice to novnc."
1706301,2018-05-30 10:49:54 UTC,"We currently don't do any clean-up when switching console types. I'm of the opinion that we should just change it to deploy all console types, but set one as a primary. That way switching will be supported, and the option of using more than one console type is available. I'll see if I can find some time to put a patch together to make that happen."
1706301,2017-07-25 12:44:06 UTC,"Which branch/tag did you deploy? I just checked the master, ocata, and newton branches, but I see the ExecReload line in all of those branches."
1706313,2017-07-25 11:18:43 UTC,Description of problem:
1706313,2017-07-25 11:18:57 UTC,Forwarded to https://bugzilla.redhat.com/show_bug.cgi?id=1474766
1706313,2017-08-03 16:42:09 UTC,"Thanks for the report, fixed upstream now:"
1706313,2017-09-04 06:12:36 UTC,"Fixed in:
commit c4826444e98428d7770c9933428e7b7b0911bbdb (HEAD -> master, origin/master, origin/HEAD)
Author: Cole Robinson <email address hidden>
Date:   Thu Aug 3 12:38:37 2017 -0400"
1706313,2017-09-04 12:19:50 UTC,"Hi Marius,
I checked to confirm the actual bug and while it exists and I thank you for your report, its severity is rather low."
1706313,2017-09-04 15:25:50 UTC,I agree completely.
1706318,2017-10-05 17:47:37 UTC,"This bug was fixed in the package magnum - 4.1.3-0ubuntu0.17.04.1~cloud0
---------------"
1706318,2017-10-05 17:47:35 UTC,The verification of the Stable Release Update for magnum has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1706318,2017-09-04 14:37:27 UTC,"Hello sean, or anyone else affected,"
1706318,2017-08-17 22:13:45 UTC,"Hello sean, or anyone else affected,"
1706318,2017-08-08 08:55:03 UTC,"I've uploaded magnum 4.1.3 to the zesty queue for SRU team review; once accepted into zesty, this version will auto-backport to the Ocata UCA as well."
1706318,2017-08-07 11:42:29 UTC,Did you have chance to upload a new point release of Magnum for testing?
1706318,2017-07-25 12:41:51 UTC,Sure I can set aside some time to test this.
1706318,2017-07-25 12:08:28 UTC,Hi Sean
1706318,2017-08-10 17:50:29 UTC,"The test case section of the bug report indicates that magnum is not covered by Openstack CI at this point in time, however the Stable Release Update policy for microreleases, https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases,  indicates that automated testing shall exist. Is there any automated testing of magnum itself?"
1706318,2017-08-15 11:57:32 UTC,There are a number of gate tests that are running as apart of the magnum project code reviews:
1706325,2017-07-26 06:25:13 UTC,"Tried the same thing, using a 31GB virtualbox HDD, with 64bit Ubuntu Budgie, version 20170725.1"
1706325,2017-07-26 08:52:38 UTC,"tried also 64bit latest alpha 2 image.  40GB virtualbox HDD - again
the same issue occurred.  Odd that it doesnt occur with a 31GB HDD but
does with 40GB."
1706325,2017-08-31 18:48:08 UTC,The installer should have prompted you to file a bug report and automatically attach /var/log/syslog.  We need the logs to diagnose the problem.
1706325,2017-10-18 18:48:38 UTC,syslog attached.
1706330,2017-11-21 17:14:34 UTC,I have the same problem.
1706331,2017-07-25 12:48:13 UTC,"I have provided an example for Networks, but this is a general issue affecting all Objects."
1706331,2017-08-02 15:17:25 UTC,Any update on this issue?
1706331,2018-01-25 07:59:59 UTC,fetching virtual-networks from Api Server by using parent_id filter doesn't list shared virtual-networks
1706331,2018-01-29 09:11:13 UTC,"Maybe something related, if user without access to Contrail GUI or API would like to share networks/fip pools via neutron api: https://bugs.launchpad.net/opencontrail/+bug/1712501"
1706331,2018-03-20 00:46:48 UTC,"You need to request network list without any parent id. If you filter by parent id, it will only return networks with that project as parent."
1706336,2017-08-03 08:31:01 UTC,good catch. I hope this bug will be fixed soon. Thanks for opening the bug
1706338,2017-07-25 13:33:30 UTC,"FWIW miral::ActiveOutputsMonitor already provides the necessary notifications, so this is just legacy code we ought to get rid of."
1706338,2017-11-03 16:37:05 UTC,Syncing task from Mir.
1706342,2018-01-20 07:38:38 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1457
1706342,2017-08-19 14:26:14 UTC,"yes, nothing changes"
1706342,2017-07-25 17:41:38 UTC,"Are you running DDL run during backup? If yes then please see also this reports:
https://bugs.launchpad.net/percona-xtrabackup/+bug/1555626
https://bugs.launchpad.net/percona-xtrabackup/+bug/1532878"
1706342,2017-08-18 10:28:20 UTC,"I have noticed that even if the ""log scanned"" log entry stops often for several seconds the backup runs fine since we have set old_alter_table=ON"
1706342,2017-07-25 20:49:50 UTC,"It doesn’t seem to be related with any DDL. Most of the time I get the other error.
Question, should the “log scanned up to … (LSN)” appear once every second (by default)?
It seems to get “stuck"" in our tests quite often, like in:"
1706342,2017-08-19 08:55:10 UTC,Have you try to tune log copying thread with --log-copy-interval?
1706358,2017-07-25 14:16:20 UTC,"Further, when selecting interfaces, add logic to determine if the interface selected already has lifs assigned, if it does continue on looking for a port to use until one without a lif is found"
1706358,2017-08-09 21:16:33 UTC,"Missed pike, untargetting"
1706358,2019-10-28 18:36:29 UTC,DO we have any update on this bug?
1706361,2017-07-25 17:09:45 UTC,in fact with latest version 1.1.1 it acts like Region.click() (clicks on last match or center).
1706361,2017-07-26 08:07:20 UTC,check nightly build 1.1.2 in a few hours
1706371,2017-09-09 22:25:09 UTC,"This is because classic is just hard, you would need to compile your interpreter for this to work transparently. I am guessing this is because bin/heroku has a wrong shebang."
1706375,2017-07-25 18:04:01 UTC,"I think it might have been this one:
https://bugzilla.gnome.org/show_bug.cgi?id=766834
In any case, I remember that there were problems with XML-Schema in the latest version. This and iterparse() are entirely different parts of the API, so preferring one over the other means preferring some users and their use cases over others. Your ticket shows where that leads."
1706375,2017-07-25 15:38:45 UTC,"Both 2.9.4 and 2.9.3 have bugs. There's a regression in 2.9.4, I don't recall which one right now, but I found it annoying enough to drop back to the previous version for the binary builds."
1706375,2017-07-25 17:05:54 UTC,"The mentioned bug in 2.9.3 causes random failures when doing `etree.iterparse` on xml files with non-ascii characters. Since we need to parse big xml files with non-ascii character, we did not manage to find a way to avoid that bug without using libxml2 2.9.4."
1706377,2017-07-25 15:47:58 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Live%20Migration%20failure%3A%20Unable%20to%20read%20from%20monitor%3A%20Connection%20reset%20by%20peer%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d
1706377,2017-08-03 14:55:52 UTC,Similar issue here:
1706377,2017-08-03 15:20:59 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22post_live_migration_at_destination%5C%22%20AND%20message%3A%5C%22InstanceNotFound%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d
1706377,2019-06-25 23:44:39 UTC,"Hey all.
Just started up a big live-migration project in our pike based cluster.  Testing showed that migrations were working well.  However after a batch of about 200 instances 3 have now lost customer data.  This manifests as a migration going into error state as described in this bug again.  Then we re-try the migration to the same destination and it completes.  Customer then reports that all of their data has been wiped back to the base image they first deployed months ago on the affected instances.  My guess is the local disk image isn't fully copied over before it's deleted at the source so nova just boots from the base image."
1706377,2019-06-26 14:10:44 UTC,"@Adam, I'm not aware of any nova changes since pike that have resolved this issue, but I can say anecdotally that I don't think we're seeing this in the upstream CI system anymore once we started using newer versions of libvirt/qemu in our CI jobs (I'd have to probably dig into the details of when this was reported and what libvirt/qemu versions were used versus when we stopped since this as a result of using a newer ubuntu cloud archive release or using ubuntu bionic nodes)."
1706377,2019-06-26 15:18:04 UTC,"Thanks for the update Matt.
I figured it was some bad match between those packages and nova.
We run the same version of libvirt/qemu in our Queens cluster that hasn't seen this problem that happens in the pike cluster."
1706377,2019-06-26 15:25:40 UTC,"Correction..
pike cluster with the issue quemu versions are 1:2.10+dfsg-0ubuntu3.8~cloud1
queens cluster without the issue quemu versions are  1:2.11+dfsg-1ubuntu7.13~cloud0"
1706393,2017-07-25 16:22:03 UTC,thanks for the info! Will fix soon and inform you once it is done
1706393,2017-07-25 16:33:55 UTC,fixed!
1706393,2018-01-20 07:38:35 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1458
1706397,2017-07-25 16:17:10 UTC,Or maybe we should dump the guest console when this fails to see if we're trying to mount the config drive too early?
1706397,2017-07-25 16:24:21 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22DeviceTaggingTestV2_42%3Atest_device_tagging%5C%22%20AND%20message%3A%5C%22mount%3A%20mounting%20%2Fdev%2Fsr0%20on%20%2Fmnt%20failed%3A%20Device%20or%20resource%20busy%5C%22%20AND%20tags%3A%5C%22tempest.txt%5C%22&from=7d
1706401,2017-08-09 15:14:39 UTC,Happened again with 35ffa9f6826f20797e3354caee03384f01e2b573
1706401,2017-10-09 13:18:02 UTC,This happened again when using the snap on a different machine:
1706401,2020-01-09 14:31:17 UTC,"Now that we have implemented the systemd watchdog, I think it's OK to downgrade this to Low, as it no longer impacting widespread availability."
1706409,2017-10-06 12:17:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706409,2019-03-15 15:23:17 UTC,"On Fri, Mar 15, 2019 at 02:41:22PM -0000, Jonathan Kamens wrote:

> >You should be able to remove or edit /etc/cron.d/certbot, and by policy
> packaging is required to respect your change. Does this not work?
>
> Yes, this appears to work (at least, after removing the file, `apt-get
> install --reinstall python3-certbot` on disco doesn't recreate it), but
> as I understand it, this is a non-standard mechanism for disabling a
> cron job. In the past the standard mechanism has been to include a
> variable in /etc/default/[whatever] to indicate whether the cron job
> should run.
"
1706409,2019-03-15 14:41:22 UTC,">You should be able to remove or edit /etc/cron.d/certbot, and by policy packaging is required to respect your change. Does this not work?
"
1706409,2019-05-15 04:17:38 UTC,[Expired for python-certbot (Ubuntu) because there has been no activity for 60 days.]
1706409,2019-03-07 13:45:16 UTC,"You should be able to remove or edit /etc/cron.d/certbot, and by policy packaging is required to respect your change. Does this not work?"
1706409,2017-10-06 13:13:08 UTC,(Sorry can't edit my comment - the output of renew that I pasted doesn't match the cli.ini contents because I ran them at different times and forgot I'd changed it from one to the other!)
1706409,2017-10-06 13:07:38 UTC,I think I've found a solution (for my issue at least):
1706409,2017-10-06 12:31:57 UTC,"I have the same problem - I'm trying to make sure Apache and MySQL are reloaded after the renewal happens so they pick up the new SSL certificate. (I don't know if that's handled by this package already, but I haven't seen anything to indicate it is - there's no post-renew hook in the cron job.)"
1706409,2019-03-07 13:46:36 UTC,"(and similarly you should be able to disable the systemd certbot.timer using systemd's usual mechanisms, and this change should also be preserved by packaging)"
1706413,2017-07-25 17:57:46 UTC,"I think that if we treat each checking function as returning a sequence of booleans, telling us whether each check was successful or not, then yielding works. You can interpret the results of any check function using all(), any() or examining the individual booleans. A check function can use ""yield from"" to incorporate other check functions, and each check function can adjust its control flow according to previous checks (for example if a check isn't possible because a previous check failed)."
1706413,2017-07-25 18:14:43 UTC,"Thanks for this suggestion, I'd not seen that pattern before, and I like
the idea of two internal objects with truthiness and print-ability."
1706415,2017-09-27 00:56:03 UTC,Just adding a note that we're seeing this problem on the patron edit screen if there are survey questions with drop downs as well.
1706415,2020-01-31 21:48:00 UTC,It doesn't look like anyone has touched this in a year. This problem came up on a survey we did about moving entirely to the web client. I'd like to revive this and see if anything can be done about the dynamic menus.
1706415,2018-03-19 19:23:39 UTC,"I took another look at this code to see if we might want to consider the dropup menus as a temporary measure while we work on getting the dynamic menus in. However, upon testing, I noticed the dropup menus for patron stat cats made no sense for sites that use surveys, since the surveys display below stat cats. IOW, menus that drop up or down dynamically depending on where they land on the page really does seem to be the way to go. I'm going to create a new bug for the additional padding so that we can get the padding in sooner rather than later."
1706415,2017-09-27 14:32:16 UTC,"Re: my scroll bar comment, it's not actually permanent.  It's there because the patron summary extends almost to the bottom of the page and the padding pushes it barely past the end of the page.  If I change the padding to 45px or hide the side bar or change the browser dimensions or add a visible blocking penalty, I can make it appear and disappear.  So, really, it's doing what you'd expect given the content in the page."
1706415,2017-09-26 19:25:11 UTC,"The pop-up menus work for me.  There is one issue with the body padding, though.  It creates a permanent scroll bar in the patron interfaces (checkout, items out, etc.), likely because of the fixed-height stuff we added to implement the fixed tabs in the patron UIs."
1706415,2017-08-09 20:27:42 UTC,"There's also the answer here https://stackoverflow.com/questions/41446122/make-dropdown-menu-go-upwards-if-it-is-at-the-bottom-of-the-browser-window-auto that may be useful, especially on grid-generated dropdowns and context menus."
1706415,2017-08-09 20:47:11 UTC,"Oh, yes! I would definitely prefer to go in the direction of something that handles this issue dynamically."
1706415,2017-08-09 20:20:46 UTC,"I was looking around and it seems someone has managed to find a good solution for this.
 Coming from https://github.com/angular-ui/bootstrap/issues/1317 there's a plunker at http://plnkr.co/edit/wzrfiP0vsvgkg3McUvh0?p=preview that seems to do what we want dynamically.  Should we consider going this way?"
1706415,2017-07-25 21:45:22 UTC,"I don't know if my approach is 'correct', but it seems to work. I have a working branch at"
1706415,2017-07-25 19:16:52 UTC,"Jason Boyer said he had added 2 inches of padding in base.tt2. This much space at the bottom has been sufficient in my test cases to display the entire menu, but my test stat cat menus are fairly small. Also, 2 inches looks like a lot of space in interfaces where it really isn't needed."
1706415,2017-07-25 18:07:47 UTC,See also related bug 1669120
1706415,2017-08-24 17:39:33 UTC,"Adding a note that regardless of what we do with the dropdown menus, I still would like to add the additional padding at the bottom of the page to give us some breathing room. Maybe I'll pull that commit out from the rest of the branch and submit it in a separate LP bug."
1706423,2017-07-26 13:33:55 UTC,"How is it going to start commissioning? Or would the machines go into ""New"" state?"
1706423,2019-09-19 11:53:34 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1706430,2017-08-17 01:03:37 UTC,This bug was fixed in the package ndiswrapper - 1.60-4ubuntu1
1706430,2017-10-18 09:38:52 UTC,We should SRU that to xenial as 1.60-4ubuntu1~16.04.1 for the HWE kernels.
1706430,2017-10-18 09:42:10 UTC,"(If we upload like that with -v1.60-3), we also get bug 1691838 in the changes file, which is quite nice I think. It also matches the existing practice - since the package is basically dead, I just change the version number like that and upload it instead of doing more work :D"
1706430,2017-07-25 19:56:36 UTC,"ACK, gotta replace __GFP_REPEAT with ___GFP_RETRY_MAYFAIL"
1706444,2017-07-26 05:35:09 UTC,A simple solution would be an adjustable tanh clipper. We may consider to add other curves as well.
1706445,2017-07-25 21:10:08 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1706445,2017-07-27 20:53:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706445,2017-07-27 20:53:47 UTC,I can reproduce this on my laptop.
1706447,2017-07-26 20:02:16 UTC,"Player locomotive file NSE455.eng is not present in folder G:\Program Files (x86)\Microsoft Games\Train Simulator\trains\trainset\NSE455, so game can't start."
1706452,2017-11-09 20:25:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706452,2017-11-09 20:26:40 UTC,"jbales@bales:~/myfonts$ sudo gnome-font-viewer Snell-Roundhand-Script.ttf
[sudo] password for jbales:
No protocol specified
Unable to init server: Could not connect: Connection refused"
1706460,2017-09-18 11:46:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706460,2017-09-18 11:46:43 UTC,"the documentation being outdated is a known issue upstream
https://bugzilla.gnome.org/show_bug.cgi?id=729766"
1706460,2018-05-07 07:09:16 UTC,"the problem still remains
corrado@corrado-p9-cc-0506:~$ apt policy totem
totem:
  Installed: 3.26.0-0ubuntu6
  Candidate: 3.26.0-0ubuntu6
  Version table:
 *** 3.26.0-0ubuntu6 500
        500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status
corrado@corrado-p9-cc-0506:~$"
1706460,2018-05-25 03:50:30 UTC,"Problem is still present in Ubuntu 18.04 , totem 3.26.0"
1706460,2018-05-26 03:43:23 UTC,"Now tracking in:
https://gitlab.gnome.org/GNOME/totem/issues/108"
1706460,2019-10-11 13:23:31 UTC,"Upstream report closed 20190131 as user docs updated in version 3.32
I can't check with totem 3.32 in Ubuntu 19.04 but...
Online help and man page both updated in Ubuntu 19.10 with totem 3.34.1"
1706460,2017-09-18 02:23:03 UTC,See also bug 1717658
1706462,2017-11-19 13:25:10 UTC,"If you're seeing panics in the firewaller, you should be able to increase
the debug level to TRACE and be able to see the traceback for the panic,
which would help us determine where the nil reference lies."
1706462,2017-11-16 19:16:31 UTC,"@jamesbeedy, there's a tiny change that went in after beta3, in edge now, that might resolve the problem you're seeing in the pastebin.  What you're seeing is mostly due to the recent provisioner changes."
1706462,2017-11-15 16:49:49 UTC,@ecjones @wallyworld feel liek I'm hitting something similar on aws too http://paste.ubuntu.com/25968550/
1706462,2017-08-15 02:18:39 UTC,"I agree with John's summary. Due to the significant change in behaviour, this should be a 2.3 change, not 2.2."
1706462,2017-08-09 05:41:00 UTC,"This happens because Juju has a default policy of spreading instances across Availability Zones because that's what the ""Availability"" portion is supposed to mean."
1706462,2017-11-16 18:16:16 UTC,@jameinel might you have 2 cents to give here?
1706471,2017-07-29 01:32:22 UTC,Thank you!
1706471,2017-11-03 15:46:25 UTC,"Unsubscribing ~ubuntu-archive, this is up to the desktop team to choose to remove from their seeds and, if they do, our magic reports will tell us to demote, we don't need a bug for that."
1706471,2017-07-29 01:03:35 UTC,"Good idea Jeremy; https://bugzilla.gnome.org/show_bug.cgi?id=785547 (heh, launchpad called it 'exiv2' when I linked them together. Oh well.)"
1706471,2017-07-28 21:30:19 UTC,shotwell depends on libgexiv2-2 which depends on libexiv2-14
1706471,2017-07-28 23:43:46 UTC,"Yes, but could you file a bug or whatever upstream?"
1706471,2017-07-28 23:23:02 UTC,"I'm not saying it's not useful. The point is that the library that we're
using for Exif metadata is unsuited for use on a modern desktop operating
system or server connected to the Internet."
1706471,2017-07-28 22:47:14 UTC,shotwell doesn't build without libgexiv2-dev.
1706471,2017-07-28 23:44:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1706471,2017-07-28 22:03:45 UTC,I certainly hope that shotwell's dependency can be disabled at build time.
1706476,2018-01-13 20:02:47 UTC,ok. this is good in a way because at least someone else besides me has seen this issue. thank you daniel for the response.
1706476,2018-01-08 02:23:58 UTC,"Yes I saw this bug with Firefox in 18.04 yesterday, so it's still an open problem."
1706476,2018-01-07 17:20:46 UTC,"Daniel, I know it's been some time since we've commented on this and I just wanted to come back and comment again about the status of all of this. This graphical issue is still occurring and like you, it happens when I resize the window with the cursor (click/hold/drag to desired size)."
1706476,2017-09-29 15:48:52 UTC,Thunderbird is also exhibiting the problem for me. The shadow around child windows like composition/preferences flickers especially when the window is resized.
1706476,2017-09-27 00:56:31 UTC,i'm still having this issue.
1706476,2017-09-16 20:24:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706476,2017-09-16 20:24:02 UTC,I believe I have seen this issue with Firefox also. I assumed it was because Firefox uses XWayland.
1706476,2017-09-16 15:07:18 UTC,This issue has occurred again. I think it might've been the result of the last few updates from the software updater. Perhaps a regression? This time I noticed it when I opened the download window from within Firefox to view the status of a download and this odd box/shadow happened.
1706476,2017-08-23 02:12:54 UTC,Incomplete then. If the problem doesn't reoccur and nobody adds further comments then the bug will eventually close itself.
1706476,2017-08-22 22:03:18 UTC,"Fortunately, one of the recent updates has seemingly fixed this issue. I've tried several things like downloading some files and repeating the above processes and that weird box hasn't happened yet so looks like it's been triaged pretty well."
1706476,2017-07-28 14:21:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1706476,2017-07-27 19:03:53 UTC,And you're welcome!
1706476,2017-07-27 19:03:30 UTC,I opened all of the apps in settings and those are fine. No glitches at all. The soft shadows those windows have around them are normal and don't look like black boxes surrounding the windows that I showed you and they're always there.
1706476,2017-07-27 03:49:36 UTC,Thanks. It looks like the glitch might actually be triggered by self-resizing windows. Does it also happen in Settings? (Try clicking on the different icons in system settings which resizes the window too)
1706476,2017-07-27 01:52:20 UTC,If it's very brief then best to just take a video with a phone or camera.
1706476,2017-07-26 22:40:01 UTC,what's a good/recommend screen/desktop recorder to record what I do to replicate that effect?
1706476,2017-07-26 20:14:41 UTC,"i'm not using any themes downloaded by me. i'm using the dash to dock and wifi refresh extensions if that helps, too."
1706476,2017-07-26 20:12:07 UTC,"yeah, it looks like that but it's brief. it doesn't stay like that all the time. just momentarily upon clicking the box to check/uncheck. i'm still working on a video of it (screen capture/desktop recording)."
1706476,2017-07-26 02:59:43 UTC,Thanks. It sounds like we should look at how gnome-shell performs when using radeon graphics.
1706476,2017-07-26 02:44:22 UTC,"oh, i should mention that i did install the open-source driver for the wifi/ethernet controller and the AMD firmware update for AMD CPUs in additional drivers, too."
1706476,2017-07-26 02:40:48 UTC,hey daniel! here's the output for lspci per your request:
1706476,2017-07-26 02:16:30 UTC,"Charlie,"
1706476,2017-07-28 16:05:34 UTC,You're welcome! I'm very proud to be helping now. I'll go through that link and see what I can do to get the bug over to the developers for them to look at it. And I'll come back with the number and get it into bugwatch.
1706516,2019-11-27 17:20:15 UTC,Find patch attached to read string as ucs-2 on sb-unicode builds
1706516,2019-11-27 17:54:48 UTC,Thanks.
1706516,2019-11-27 16:58:39 UTC,"The attached patch works, but is incorrectly interpreting the data as CHAR rather than WCHAR and not producing the right string"
1706516,2019-11-27 16:27:43 UTC,Also observed in Qtools: https://github.com/Shinmera/qtools/issues/20
1706516,2019-11-27 17:12:38 UTC,Let the people who care about that part submit a new patch.
1706516,2019-11-27 16:48:41 UTC,0942dab06fc0379fb51f9b29a02acbab0a5ffe39
1706523,2018-05-11 15:33:07 UTC,This change was made by a bot.
1706523,2021-01-07 04:07:53 UTC,4.8 EOL
1706524,2017-08-17 13:09:01 UTC,This bug was fixed in the package gnome-settings-daemon - 3.24.3-0ubuntu3
1706524,2017-08-16 21:16:14 UTC,This bug was fixed in the package gnome-shell - 3.24.3-0ubuntu3
1706524,2017-08-16 07:46:08 UTC,This bug was fixed in the package gnome-control-center - 1:3.24.3-0ubuntu3
1706524,2017-07-26 08:24:35 UTC,"That was already the case and still will be, hence the switch and the default key being off in gnome-control-center."
1706524,2017-07-26 08:14:54 UTC,Yeah it's a good option to have. I'm just suggesting it should not be possible to accidentally push volume over 100% by pressing the volume keys. You should have to enable the option explicitly and it should not be on by default. Because distortion and clipping may (will?) occur.
1706524,2017-07-26 08:04:19 UTC,"This isn't a good answer for people working with laptops, where this issue occurs the most. I don't want have speakers with me everwhere I'm travelling :p"
1706524,2017-07-26 07:13:28 UTC,I'm not sure what >100% means but if it means there might be distortion or clipping then those would be reasons to not allow >100% by default.
1706524,2017-07-26 14:36:46 UTC,Hi!
1706532,2017-07-28 02:20:57 UTC,"When execute cluster-node-add,you must perform the node's current state detection.　The node status of database records is not updated every moment．"
1706539,2017-08-31 11:17:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499560"
1706539,2019-10-28 18:38:45 UTC,Hey Goutham Pacha Ravi ... how is this going?
1706541,2017-07-26 08:13:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706568,2017-08-11 15:04:26 UTC,"It's been set to low, as it's only an install issue and doesn't stop the charm progressing to an installed/running state."
1706571,2018-07-04 17:27:28 UTC,Same lag confirmed on Mint 19 Cinnamon 64 bit.
1706580,2017-08-30 09:48:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706587,2018-01-20 07:40:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-793
1706592,2017-07-28 14:16:22 UTC,Any updates on this defect?
1706592,2017-08-15 14:16:22 UTC,"looks like that was a neutronclient bug fixed by https://github.com/openstack/python-neutronclient/commit/a905f755b995f358116a11f77de71893b0601937, but ocata is capped at an older version of neutronclient than was fixed. Do we need to backport the fix in neutronclient, then?"
1706592,2017-08-15 14:04:40 UTC,Why is the request GET /v2.0/agents.json.json and not GET /v2.0/agents.json ?
1706592,2017-08-01 17:47:10 UTC,Any updates?
1706592,2017-07-26 15:40:58 UTC,Correction to previous comment.. it is 6.1.0.
1706592,2019-07-03 12:42:57 UTC,"Marking as fixed, Ocata has been maintenance-only for some time now (and Pike too) and newer releases are not affected"
1706592,2017-07-26 15:20:23 UTC,"dump of request :
GET /v2.0/agents.json.json HTTP/1.0
Accept: application/json
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Type: text/plain
Host: 127.0.0.1:9696
User-Agent: python-neutronclient
X-Auth-Token: gAAAAABZeHalBtTzcEv94enqwcUcD-jAmBfU_A8rBr3STNUdDYqJ6t3CX-vIBHWWFhiBx4z8elau_9ZKTXeUBC3GxTNUFRMump0AaM_D-1i33jpK0EqaFb3lM0MVlwFS-6usbg7nNhmvfw3rT7Xs0awUDihdKf5k0r7M0OHVmqCxNMQ5DMLcDiba6hEDOSExLLGydX8iOw0qxnpLOOCDQZhw1EbdmWPwJ_ONFql-dqhMufuLpLTNtaM
X-Domain-Id: None
X-Domain-Name: None
X-Identity-Status: Confirmed
X-Is-Admin-Project: False
X-Project-Domain-Id: 03bd7eef7bd943c29a273b82d7ef12c4
X-Project-Domain-Name: Service
X-Project-Id: 5f0805bffd4349c4a53a81a5516c5631
X-Project-Name: service
X-Role: admin
X-Roles: admin
X-Service-Catalog: <removed>
X-Tenant: service
X-Tenant-Id: 5f0805bffd4349c4a53a81a5516c5631
X-Tenant-Name: service
X-User: neutron
X-User-Domain-Id: 03bd7eef7bd943c29a273b82d7ef12c4
X-User-Domain-Name: Service
X-User-Id: 09190e437c2fd33046047c5458396ba91f2468cc22a1c33bbc12a0148d0885e4
X-User-Name: neutron
(<routes.util.URLGenerator object at 0x100437447d0>, {'action': u'index', 'controller': <wsgify at 1100652491600 wrapping <function resource at 0x10043ffb668>>, 'format': u'json.json'})
{}
json.json
{'json': 'application/json'}

> /usr/lib/python2.7/site-packages/neutron/api/v2/resource.py(96)resource()


-> args['id'] = '.'.join([args['id'], fmt])"
1706592,2017-07-26 14:26:21 UTC,Can you give us full info about the request in question? I wonder how you get json.json in wsgi context dictionary.
1706592,2017-07-26 14:16:38 UTC,Just adding links to the original bug and upstream review:
1706592,2017-07-26 12:59:54 UTC,"In failing case: variable route_args : (<routes.util.URLGenerator object at 0x10034269a50>, {'action': u'index', 'controller': <wsgify at 1100392530832 wrapping <function resource at 0x100347fe668>>, 'format': u'json.json'})"
1706592,2017-07-26 12:53:17 UTC,"Above comment is from ocata environment. In Pike :

> /usr/lib/python2.7/site-packages/neutron/api/v2/resource.py(93)resource()


-> if fmt is not None and fmt not in format_types:
(Pdb) l
 88  	            # to tackle it without breaking API backwards compatibility.
 89  	            import pdb; pdb.set_trace()
 90  	            print args
 91  	            print fmt
 92  	            print format_types
 93  ->	            if fmt is not None and fmt not in format_types:
 94  	                args['id'] = '.'.join([args['id'], fmt])
 95
 96  	            method = getattr(controller, action)
 97  	            result = method(request=request, **args)
 98  	        except Exception as e:
(Pdb) n

> /usr/lib/python2.7/site-packages/neutron/api/v2/resource.py(96)resource()


-> method = getattr(controller, action)
(Pdb) p fmt
u'json'
(Pdb) p format_types
{'json': 'application/json'}"
1706592,2017-07-26 15:39:03 UTC,"neutron client used is :
/usr/lib/python2.7/site-packages/python_neutronclient-6.3.0-py2.7.egg-info"
1706592,2017-07-26 12:52:15 UTC,"Did more analysis using pdb. In failing environment seeing this :

> /usr/lib/python2.7/site-packages/neutron/api/v2/resource.py(93)resource()


-> if fmt is not None and fmt not in format_types:
(Pdb) l
 88  	            # to tackle it without breaking API backwards compatibility.
 89  	            import pdb; pdb.set_trace()
 90  	            print args
 91  	            print fmt
 92  	            print format_types
 93  ->	            if fmt is not None and fmt not in format_types:
 94  	                args['id'] = '.'.join([args['id'], fmt])
 95
 96  	            method = getattr(controller, action)
 97  	            result = method(request=request, **args)
 98  	        except Exception as e:
(Pdb) n

> /usr/lib/python2.7/site-packages/neutron/api/v2/resource.py(94)resource()


-> args['id'] = '.'.join([args['id'], fmt])
(Pdb) p fmt
u'json.json'
(Pdb) p format_types
{'json': 'application/json'}"
1706596,2017-07-26 14:33:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706596,2017-07-26 17:16:05 UTC,This has been reported to Debian as a feature request a while ago. Please refer to https://bugs.debian.org/741097 for the original bug report and discussion.
1706596,2017-07-27 12:18:55 UTC,These are very good points. Practically this would mean the following variables should be set during configuration:
1706597,2018-01-15 16:58:40 UTC,This issue was fixed in the openstack/python-novaclient 10.0.0 release.
1706597,2017-09-27 16:40:09 UTC,"Reviewed:  https://review.openstack.org/495901
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=a1c00740c5b709a7d2bc4289fa6e28eac7909b8f
Submitter: Jenkins
Branch:    stable/pike"
1706597,2017-10-04 12:20:00 UTC,This issue was fixed in the openstack/python-novaclient 9.1.1 release.
1706597,2017-08-21 10:16:31 UTC,"Reviewed:  https://review.openstack.org/492003
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=0a3cf89c67a3fb78876137506fe57e645f4fabe4
Submitter: Jenkins
Branch:    master"
1706597,2017-08-21 08:51:11 UTC,It was broken by this patch https://review.openstack.org/#/c/429512/13/novaclient/v2/shell.py
1706597,2017-08-09 06:48:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492003"
1706597,2017-08-21 15:14:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/495901"
1706613,2017-07-29 16:04:14 UTC,Thought I already responded to this. But anyway...
1706613,2017-08-06 18:29:38 UTC,"Sorry for the late response, I wasn't able to use the said computer for a few days."
1706613,2017-08-06 18:31:35 UTC,Forgot to add my PS1...
1706630,2017-12-14 19:37:39 UTC,Is this reproducible w/ the hwe kernel?
1706630,2019-06-11 19:27:49 UTC,Fully functional aarch64 (arm64) kvm xml definition example:
1706630,2019-06-11 19:02:40 UTC,"> The most common related mistake is the lac of <gic version='3'/>
"
1706630,2019-06-11 08:52:42 UTC,"@RussianNeuromancer for aarch64 you need to tweak quite some things to work.
Openstack does so by default, but I doubt that virt-manager comes up with a great default config.
The most common related mistake is the lac of
  <gic version='3'/>"
1706630,2019-06-09 21:14:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706630,2019-06-09 21:14:06 UTC,"Getting same issue with both of libvirt 4.0.0/qemu 2.11 (18.04.2) and libvirt 5.0.0/qemu 3.1 (19.04) on attempt to run AArch64 guest on AArch64 host. Virtual machine setting is default generated by virt-manager wizard, so there is no big changes to default devices, I just filled iso, hdd and network bridge."
1706630,2017-12-14 22:35:17 UTC,"No - with the hwe-kernel (4.10.0-42-generic from 4.10.0-42.46~16.04.1), this doesn't happen."
1706630,2017-12-14 18:22:01 UTC,I'm running qemu-system-arm 2.10+dfsg-0ubuntu3.1~cloud0 and still seeing this issue.
1706630,2019-06-12 05:07:25 UTC,"Rafael, I posted results of testing aarch64 xml example in bug 1832394."
1706630,2017-08-29 08:23:39 UTC,"From the log:
<type arch='aarch64' machine='virt-2.8'>hvm</type>"
1706630,2017-09-26 11:17:31 UTC,@admcleod : Any updates on Pike testing with qemu2.10 mentioned in comm #9 ?
1706630,2017-07-26 14:45:37 UTC,https://bugzilla.redhat.com/show_bug.cgi?id=1414081
1706630,2017-07-26 14:50:29 UTC,The attached xml is that returned from libvirt - the nova generated xml does not include a gic version:
1706630,2017-08-02 07:52:14 UTC,"I meet the same problem in AArch64, with latest Nova and qemu 2.8.1, libvirt 3.0.0"
1706630,2017-07-26 13:43:36 UTC,Attaching XML generated by OpenStack for the failed instance launch.
1706630,2017-08-28 13:46:04 UTC,"Can confirm this bug exists as of today, with xenial-pike/proposed"
1706630,2017-08-28 14:14:00 UTC,"Well the status of today should have qemu 2.10-rc3 right?
Is that in xenial-pike/proposed already?"
1706630,2017-08-28 15:26:53 UTC,"Re the state of qemu ver, I've asked someone else to comment on that. XML from before was:"
1706630,2017-08-08 05:45:29 UTC,"This does not match James finding of missing the gic version in the generated XML.
Also the error is to not start the guest at all.
Yet still on the changed MSI interrupt behaviour the following change might be related:"
1706649,2018-03-09 20:04:36 UTC,This is a bug vienna will need fixed.
1706649,2018-05-18 17:19:48 UTC,@koza: what's the latest status on fixing this bug?
1706659,2017-07-26 14:57:34 UTC,What exactly do you want to see?
1706664,2017-07-31 15:35:54 UTC,"Michele,"
1706680,2018-07-19 09:58:58 UTC,Hi!
1706686,2017-07-28 12:57:48 UTC,"Hello Andy, or anyone else affected,"
1706686,2017-10-27 19:29:25 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for xenial for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1706686,2017-07-26 14:52:05 UTC,Probably caused by 96a8fae0fe09 (ARM: convert to generated system call tables).
1706686,2017-07-28 09:24:43 UTC,Looks likely as the compat change in zesty was excluding a few syscalls based on #ifdefs.
1706694,2017-07-26 19:29:39 UTC,"Carlos, an easy fix, any chance you can do this before the weekend deployment?"
1706694,2017-07-26 19:57:32 UTC,"Fixed. Would you believe the typo has been around for at least 8 years? We can only look as far as the date of the svn repository restructure, so maybe more."
1706694,2017-07-26 20:18:48 UTC,"Wow, 8 years!"
1706694,2017-07-26 21:56:18 UTC,Deployed to staging.
1706699,2017-08-10 12:02:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492491"
1706699,2017-08-10 15:36:24 UTC,"Fix proposed fix puts a 'band-aid' on the bug in that it is recovered from on the next 'update-status' hook.  As the bug only seems to present itself during Amulet tests during deployment, and only ever during deployment, this is now a low priority bug."
1706699,2017-08-10 20:42:08 UTC,"Reviewed:  https://review.openstack.org/492491
Committed: https://git.openstack.org/cgit/openstack/charm-manila/commit/?id=df96346eb9ce729a58a57a96f756551c398068e0
Submitter: Jenkins
Branch:    master"
1706700,2019-09-19 14:48:57 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1706701,2018-03-12 07:25:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706701,2018-03-12 07:27:29 UTC,I can confirm this bug in Lubuntu Bionic installed from the daily iso file 'bionic-desktop-amd64.iso'.
1706701,2018-03-12 08:06:08 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1706705,2017-09-21 15:55:50 UTC,"Inspection of previous configuration values should be possible so that automatic removal of devices from bridges could occur when configuration changes; its made slight tricky that in order to restore the previous state, we also need to understand whether an ifdown/ifup cycle needs to be performed on the nic."
1706705,2018-02-08 10:26:42 UTC,"This bug also affects a change on ""os-data-network"", which will reconfigure new tunnels on br-tun, but not delete the ones from the old ""os-data-network""."
1706705,2019-10-11 09:20:34 UTC,For future travelers: the recreation of the ovs db as a workaround for this bug did not work properly for me. After the restart of the services I was left with only br-int and had to re-add br-data manually and stop/start instances to get tap ports back and return to a healthy state.
1706706,2017-07-26 16:09:08 UTC,This OpenStack environment is running Mitaka.
1706708,2017-11-21 03:13:41 UTC,Added share groups and share group snapshots quotas doc in https://review.openstack.org/#/c/514080/
1706708,2017-11-21 03:10:11 UTC,Added share groups and share group snapshots quotas api in https://review.openstack.org/#/c/491700/
1706708,2020-04-30 17:37:05 UTC,"These fixes were released in Queens: https://review.opendev.org/#/c/514080/5/doc/source/admin/shared-file-systems-quotas.rst
https://docs.openstack.org/manila/queens/admin/shared-file-systems-quotas.html"
1706713,2017-07-26 20:23:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706713,2017-07-31 20:18:58 UTC,Recent apt update/apt upgrade fixed the problem.
1706713,2017-08-02 18:30:46 UTC,"Yeah, it doesn't seem to be happening for me either anymore."
1706713,2018-03-31 15:23:34 UTC,This is affecting me on an Ubuntu 16.04 fresh install. Uname -a gives:
1706713,2018-04-06 13:27:11 UTC,Confirm this on Xubuntu 17.10
1706728,2017-07-26 20:30:52 UTC,"I think this might be ""by design"". The English strings read:
- ""Regular polygon (with one handle) instead of a star""
- ""Star instead of a regular polygon (with one handle)"""
1706728,2017-07-26 17:59:48 UTC,"I tried the the new version 0.92.2 pre0(973e216, 2017-07-25) and the mistake is the same."
1706728,2017-07-27 06:50:27 UTC,"I complety agree with your explanations.
Thanks.
Regards."
1706729,2017-10-13 07:07:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511737"
1706729,2017-10-20 20:28:55 UTC,"Reviewed:  https://review.openstack.org/511737
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=a638f483fb41df4f4acc0b0f42d289ba711333e5
Submitter: Zuul
Branch:    master"
1706730,2017-07-26 19:09:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1706738,2017-07-29 04:44:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706740,2017-07-28 12:15:43 UTC,Issue popped up again this night on unattended-upgrade of apache packages affected by USN-3370 (https://usn.ubuntu.com/usn/usn-3370-1/).
1706745,2017-07-26 19:25:52 UTC,"StacktraceTop:
 XSync (dpy=0x55893da04100, discard=discard@entry=0) at ../../src/Sync.c:42
 RGFlushInterface () at rgutils.cc:68
 RGMainWindow::buildInterface (this=this@entry=0x55893dd493d0) at rgmainwindow.cc:973
 RGMainWindow::RGMainWindow (this=0x55893dd493d0, packLister=0x55893dd42da0, name=...) at rgmainwindow.cc:815
 main (argc=<optimized out>, argv=<optimized out>) at gsynaptic.cc:462"
1706745,2017-09-19 09:58:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706761,2017-07-26 20:10:42 UTC,"StacktraceTop:
 empty () from /tmp/apport_sandbox_O4lP_7/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 brisk_menu_window_filter_apps ()
 gtk_list_box_apply_filter () from /tmp/apport_sandbox_O4lP_7/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_list_box_insert () from /tmp/apport_sandbox_O4lP_7/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_cclosure_marshal_VOID__OBJECTv () from /tmp/apport_sandbox_O4lP_7/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1706761,2017-08-09 16:45:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706761,2017-10-21 18:45:50 UTC,Yeah the same thing happened to me while installing new software from boutique!
1706761,2019-02-23 07:40:21 UTC,High Priority pls...
1706770,2020-05-09 19:12:04 UTC,Dammit! I cant believe this level of lack of security could happen in this project. WHAT A SHAME!
1706770,2020-06-16 14:37:11 UTC,"#6 Chris quote:
4. Go to ""System"" -> ""Administration"" -> ""Users and Groups"".
5. Change password from ""Asked on logon"" to ""Not asked on logon"".
6. Lock your machine.
7. Press ""Switch User"".
8. Observe no password is required to unlock as the current user."
1706770,2017-10-18 16:49:51 UTC,"After a bit more investigation, being in the `nopasswdlogin` group is what causes the switch-user screen to not ask for a password."
1706770,2017-08-18 11:28:41 UTC,"Hi! Can I make this bug public so more developers can see it?
Thanks!"
1706770,2017-10-11 06:52:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706770,2017-09-02 19:46:44 UTC,Unable to reproduce this in Ubuntu MATE 17.04. I use full-disk encryption too and enabled auto-login as well.
1706770,2017-08-18 11:38:14 UTC,That's fine with me.
1706770,2017-10-18 16:31:40 UTC,"If it helps, I've reproduced this in a fresh Ubuntu Mate virtual machine."
1706772,2017-08-22 11:39:10 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1706772,2017-08-12 06:18:22 UTC,"Reviewed:  https://review.openstack.org/491835
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c46f037a0f57710553b5ff8f02bc08ebedf3c5fb
Submitter: Jenkins
Branch:    stable/ocata"
1706772,2017-08-08 17:47:51 UTC,"Reviewed:  https://review.openstack.org/487925
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c2d33c3271370358d48553233b41bf9119d834fb
Submitter: Jenkins
Branch:    master"
1706772,2017-08-08 15:16:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/491835"
1706772,2017-08-11 12:26:55 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1706772,2017-07-27 16:01:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/487925"
1706772,2017-07-27 17:21:37 UTC,Note that this fix only smooths the behavior in the ironic driver so that it doesn't crash when this happens.
1706772,2017-07-26 22:00:46 UTC,"Actually this wasn't caused by the migrate instance flavors change mentioned above, it was happening before that as well:"
1706772,2017-08-10 15:24:27 UTC,"We're also hitting this issue on our grenade job on ocata http://logs.openstack.org/04/480904/10/check/gate-grenade-dsvm-ironic-ubuntu-xenial/a13a964/logs/new/screen-n-cpu.txt.gz. In this case, placement start causes apache restart, and compute is started at the same time. Will propose a patch to grenade and see if it'll break anything."
1706772,2017-07-26 22:40:31 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22DiscoveryFailure%3A%20Could%20not%20determine%20a%20suitable%20URL%20for%20the%20plugin%5C%22%20AND%20tags%3A%5C%22screen-ir-api.txt%5C%22&from=7d
1706772,2017-07-26 22:03:22 UTC,Looks like the failure is in ironic-api on startup:
1706772,2017-07-27 12:51:03 UTC,The reason is someone restarting apache at that moment -- http://logs.openstack.org/49/484949/14/check/gate-tempest-dsvm-ironic-ipa-wholedisk-bios-agent_ipmitool-tinyipa-ubuntu-xenial-nv/69b18d7/logs/apache/error.txt.gz. We need to come up with an idea how to work around this (again)
1706773,2017-08-12 15:59:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706779,2017-07-26 21:23:25 UTC,Inkscape version Inkscape 0.92.1 r15371
1706779,2017-07-26 22:18:05 UTC,I assume you're facing two different issues here:
1706779,2017-07-27 09:03:57 UTC,The subscript issue: the box didn't turn red and I tried resizing it.
1706779,2017-07-27 09:34:11 UTC,"> The subscript issue:
"
1706780,2017-07-26 21:30:22 UTC,Attaching test program to demonstrate the problem. Compile with
1706780,2018-09-12 21:26:05 UTC,"I'm using robust mutexes in a similar way, and I've found that if I use PTHREAD_PRIO_INHERIT attribute on my mutexes, I can no longer reproduce this bug."
1706788,2017-07-27 00:02:33 UTC,Looks like it has something to do with this file: /usr/lib/python2.7/dist-packages/ryu/services/protocols/bgp/speaker.py
1706795,2017-07-28 15:38:34 UTC,"Traceback (most recent call last):
  File ""/usr/lib/python3/dist-packages/menulibre/MenulibreApplication.py"", line 1688, in on_delete_cb
    delete_func()
  File ""/usr/lib/python3/dist-packages/menulibre/MenulibreApplication.py"", line 1611, in delete_launcher
    self.treeview.remove_selected()
  File ""/usr/lib/python3/dist-packages/menulibre/MenulibreTreeview.py"", line 197, in remove_selected
    model.remove(treeiter)
AttributeError: 'TreeModelFilter' object has no attribute 'remove'"
1706803,2017-08-15 23:12:33 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x5651821cb21c ""Indicator-Applet-Complete"", file=file@entry=0x5651821cb622 ""applet-main.c"", line=line@entry=173, func=func@entry=0x5651821cbaf0 <__func__.53871> ""place_in_menu"", message=message@entry=0x565182bc3dd0 ""assertion failed: (io != NULL)"") at ../../../../glib/gtestutils.c:2433
 g_assertion_message_expr (domain=0x5651821cb21c ""Indicator-Applet-Complete"", file=0x5651821cb622 ""applet-main.c"", line=173, func=0x5651821cbaf0 <__func__.53871> ""place_in_menu"", expr=<optimized out>) at ../../../../glib/gtestutils.c:2456
 place_in_menu (widget=0x565182d69730, user_data=0x7ffe8a2360c0) at applet-main.c:173
 entry_added (io=0x565182a9f600, entry=0x565182da23b0, menubar=0x565182d56830) at applet-main.c:355
 g_closure_invoke (closure=0x565182c88db0, return_value=return_value@entry=0x0, n_param_values=2, param_values=param_values@entry=0x7ffe8a2362d0, invocation_hint=invocation_hint@entry=0x7ffe8a236250) at ../../../../gobject/gclosure.c:804"
1706803,2017-10-17 15:10:20 UTC,"Had problem that battery icon disappears while clicking right on it to add remaining battery time.
After a while the icon returns with this crash message.
For now, it is working ok."
1706803,2018-01-30 12:56:21 UTC,This problem persists in 18.04 daily
1706803,2018-03-18 02:52:12 UTC,this is happening in 18.04 daily for me too
1706803,2018-06-04 04:17:29 UTC,"My indicator applet vanished and couldn't be reloaded, which disabled sound completely. I use my laptop to perform a college radio show, and this made it impossible today. Fortunately, the station has a computer, so I used YouTube to play the Kinks live."
1706803,2017-10-19 17:17:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706816,2020-01-28 13:41:09 UTC,note to anyone stumbling upon this: designate::keystone::authtoken needs to be defined before designate::api
1706825,2020-11-09 18:28:35 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1706825,2021-01-09 04:17:50 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1706837,2017-07-28 18:24:09 UTC,"StacktraceTop:
 epoll_wait () at ../sysdeps/unix/syscall-template.S:84
 sd_event_wait (e=e@entry=0x558b5eefa230, timeout=timeout@entry=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2525
 sd_event_run (e=0x558b5eefa230, timeout=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2683
 main (argc=<optimized out>, argv=<optimized out>) at ../src/journal/journald.c:107"
1706837,2017-07-27 03:09:37 UTC,"Stacktrace:
 #0  0x00007fe7053b3773 in ?? ()
 No symbol table info available.
 #1  0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0  0x00007fe7053b3773 in ?? ()
 #1  0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()"
1706837,2018-03-17 10:58:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706859,2017-10-18 19:56:18 UTC,When installing Ubuntu 17.10 http://cdimage.ubuntu.com/daily-live/20171018/artful-desktop-amd64.iso in Italian it proposed for English keyboard instead of Italian.
1706859,2019-11-10 07:26:04 UTC,This error still occurring on 20.04 Focal daily build 20191109.
1706859,2019-05-09 07:28:49 UTC,"This regression still happens on 19.04 (and 18.04 LTS). I selected Finnish as the language, but it still offered English keyboard by default on the following page, which is unfortunate."
1706859,2018-10-28 08:58:48 UTC,This seems to be a duplicate of bug 521025.
1706859,2017-12-18 08:00:08 UTC,"1. I installed 17.10 server today
2. I use English for language
3. and Swedish as the keyboard (select it with F3 before start the installation)
4. installation goes OK but it doesn't let me select the keyboard when installing, it seems to use the locale - which in this case will be US for the keyboard.
5. I tried to go back in the installation to select another keyboard but it will not allow me
6. After reboot I can't enter the encryption key since it has characters that doesn't exist in the US keyboard"
1706859,2017-10-19 07:20:27 UTC,The behaviour is also different if you start ubiquity from the live session or directly from 'Install Ubuntu'
1706859,2017-10-16 22:26:00 UTC,The same on Kubuntu when I tested earlier with latest isos
1706859,2020-02-05 07:34:33 UTC,"Tested Lubuntu 18.04.4 and this bug occuring on Dell Inspiron laptop 3521 and also tested
in a VirtualBox on another machine."
1706859,2017-10-16 21:53:28 UTC,I certainly can't reproduce this anymore. I've updated console-setup a few weeks ago to fix a clear issue in the config script that would affect this as well.
1706859,2017-10-16 22:04:44 UTC,Mathieu - still occurs in todays release candidate for Ubuntu Budgie.
1706859,2017-07-27 06:56:17 UTC,"This only seems to happen when you launch ubuiqity in a live session. Starting the installation from the ""try or install screen"" instead seems to correctly set the matching keyboard layout by default."
1706859,2017-07-27 07:09:29 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1706859,2017-07-27 07:33:29 UTC,Also same behaviour in Ubuntu Mate
1706859,2017-10-18 20:53:17 UTC,Ok; there's different behavior depending on whether someone picks language at the splash screen or at the welcome screen in the installer.
1706859,2017-07-27 08:30:22 UTC,I meant daily iso for Ubuntu
1706859,2017-08-20 07:33:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706859,2017-09-27 14:49:10 UTC,unlike #1 - on Ubuntu Budgie we see this issue occurring from the Try/Install screen as well EXCEPT (oddly) if encrypting/lvm the drive when the UK keyboard is then automatically chosen.
1706859,2017-07-27 08:26:53 UTC,Also same for main ubuntu Alpha2 gnome iso
1706859,2017-09-28 08:33:05 UTC,"Doing iso testing this morning, I indeed see this on the Try/install screen as well."
1706863,2017-07-27 06:40:53 UTC,"StacktraceTop:
 LLVMCreateTargetMachine () from /tmp/apport_sandbox_xFYyaa/usr/lib/x86_64-linux-gnu/libLLVM-4.0.so.1
 si_create_llvm_target_machine () from /tmp/apport_sandbox_xFYyaa/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 radeonsi_screen_create () from /tmp/apport_sandbox_xFYyaa/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 amdgpu_winsys_create () from /tmp/apport_sandbox_xFYyaa/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 pipe_radeonsi_create_screen () from /tmp/apport_sandbox_xFYyaa/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so"
1706871,2017-07-27 14:37:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/487874"
1706873,2017-07-27 07:52:58 UTC,"We are, of course, using Percona Server (5.7.18)"
1706873,2017-07-27 09:34:56 UTC,"Hi Rick,
Could not reproduce with following steps:
Run this on master:"
1706873,2017-07-27 10:02:23 UTC,"Yes, we use multi-source replication with two different masters.
Perhaps this bug only bites when multi-source replication is in use.
I will run some more tests in the next days."
1706873,2017-07-27 10:17:34 UTC,"I have tested also with multi-master setup.
3 master - 1 slave.
I used node1(master) to run DMLs and node4(slave) to run xtrabackup. But no success to reproduce issue."
1706873,2018-01-20 08:02:32 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1460
1706879,2017-09-19 09:45:53 UTC,I only just noticed you've posted your settings file and your settings are correct. Ignore my previous comment.
1706879,2017-09-17 07:33:05 UTC,"Hi,"
1706879,2017-07-27 09:10:54 UTC,Attaching my local_settings.py
1706879,2017-08-24 04:40:40 UTC,The domains panel is not showing probably because of the absence of the domain_token. https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/identity/domains/panel.py#L37 It can be that the user doesn't have the right permission or something to do with the keystone policy.
1706880,2017-07-28 22:26:18 UTC,"ContrailDpdkCoremask: ""0x3f"" works"
1706880,2018-09-19 16:33:55 UTC,"Reviewed:  https://review.opencontrail.org/46305
Committed: http://github.com/Juniper/contrail-tripleo-heat-templates/commit/d70817c7a0f61ba1083b752c1340741600cbd659
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    stable/newton"
1706880,2018-09-19 16:33:52 UTC,"Reviewed:  https://review.opencontrail.org/46304
Committed: http://github.com/Juniper/contrail-tripleo-heat-templates/commit/460e1e488c6e7dfb4ab72f754f8f89afedba704f
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    stable/newton"
1706880,2017-07-31 07:56:23 UTC,"Release-Notes:
==============
While deploying a DPDK compute on a RHOSP10 cluster, value for ContrailDpdkCoremask variable need to be mentioned as string (within quotes)."
1706880,2018-09-19 10:06:56 UTC,"Review in progress for https://review.opencontrail.org/46305
Submitter: alexey-mr (<email address hidden>)"
1706880,2018-09-19 09:56:52 UTC,"Review in progress for https://review.opencontrail.org/46304
Submitter: alexey-mr (<email address hidden>)"
1706880,2018-09-19 09:55:13 UTC,"Review in progress for https://review.opencontrail.org/46305
Submitter: alexey-mr (<email address hidden>)"
1706880,2018-09-19 12:03:51 UTC,"There is nothing to change in the code, just fixed an example."
1706896,2017-07-27 10:09:13 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1706899,2017-07-27 10:09:12 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1706942,2017-07-27 10:54:49 UTC,re-uploaded images
1706942,2017-07-27 21:43:23 UTC,"OK, never mind."
1706946,2017-08-09 18:22:41 UTC,"$ syncpackage -b 1706946 -s rbalint -f crash
syncpackage: Source crash -> artful/Proposed: current version 7.1.8-1ubuntu2, new version 7.1.9-1
syncpackage: New changes:
crash (7.1.9-1) unstable; urgency=medium"
1706955,2017-07-27 13:02:07 UTC,"IMO, it is an issue in cinder, not nova.
But the version information of the following openstack components should be added in this report."
1706955,2017-07-28 05:31:48 UTC,Please find the version details below
1706955,2017-08-01 06:05:21 UTC,Can you please provide any kind of update ?Is this any kind of bug or misconfiguration issue
1706956,2017-08-04 15:16:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706957,2017-07-27 13:54:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706957,2017-08-21 12:39:02 UTC,Thanks for your report.
1706960,2017-07-27 12:23:49 UTC,I think this bug is related: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/1468742 but was said to be fixed.
1706960,2017-07-27 12:33:49 UTC,Verisign changed the output and broke the client. Wait for the next release.
1706966,2017-12-28 17:34:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706967,2017-07-27 13:55:18 UTC,On it.
1706968,2017-07-27 16:02:42 UTC,What about just doing these as git aliases? I'm hesitant to add a ton of subcommands.
1706968,2017-07-29 09:17:52 UTC,What would the command I'd be typing look like then?
1706968,2017-07-31 17:07:27 UTC,"[alias]
    ubuntu-changelog = ""!f() { git show $1:debian/changelog; }; f""
[alias]
    ubuntu-version = ""!f() { git ubuntu-changelog $1 | dpkg-parsechangelog -SVersion; }; f"""
1706969,2017-12-04 11:41:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706969,2017-12-26 15:04:35 UTC,After some more testing that seems to be an upstream openjdk issue as reported in https://bugs.openjdk.java.net/browse/JDK-8185424 [1].
1706971,2017-07-27 20:53:39 UTC,"Sure, but in that case the panel preferences UI should block the user from reducing size further. I've checked and it does that in Xenial. The hard limit to panel width seems to be 17px."
1706971,2017-07-27 20:36:40 UTC,What is the use case for scaling below 24px? The menu has to render in a readable way.
1706973,2017-07-31 16:46:35 UTC,"In particular, this tests covers setting different MTUs for interfaces which may have IPV6 configurations which need an IPV6_MTU setting; while IPV6_MTU is supported, if the IPV6_MTU value is higher than the device MTU, the IPV6_MTU setting won't be value (the device will break up the v6 packets at the lower MTU).  In Ubuntu, there's some additional logic added to raise the underlying device MTU to match the IPV6_MTU.  This logic is not present in sysconfig scripts at this time."
1706978,2017-10-30 08:03:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1706978,2020-11-17 05:41:39 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life in April 2019."
1706988,2017-07-27 16:00:05 UTC,This change was made by a bot.
1706991,2017-07-27 14:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1706991,2017-07-27 16:18:14 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1706991,2017-07-31 13:54:58 UTC,"Patches has been posted to ubuntu mailing list to address this issue.
Link: https://lists.ubuntu.com/archives/kernel-team/2017-July/086027.html
      https://lists.ubuntu.com/archives/kernel-team/2017-July/086028.html"
1706991,2017-08-16 16:33:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1706991,2017-08-28 10:14:02 UTC,This bug was fixed in the package linux - 4.4.0-93.116
1706991,2018-05-21 11:48:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1706991,2019-02-14 16:55:07 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1706992,2017-12-26 07:43:27 UTC,I got this error too unexpectedly!
1706992,2018-01-18 08:21:17 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1997
1706992,2017-12-26 07:45:35 UTC,"mysql -V
mysql  Ver 14.14 Distrib 5.7.19-17, for debian-linux-gnu (x86_64) using  6.3"
1706992,2017-08-01 20:04:36 UTC,"Can almost confirm that was the issue. After removing the generated column expression and using triggers on the table to keep the column updated as the work around, we have had 0 crashes."
1706992,2017-08-02 04:15:51 UTC,"Brian,"
1706992,2017-07-27 15:04:29 UTC,"The Percona package was installed from the source, package percona-xtradb-cluster-57, version 5.7.18-29.20-1.xenial"
1706992,2017-07-27 15:06:28 UTC,"# dpkg -l | grep percona
ii  percona-release                   0.1-4.xenial                               all          Package to install Percona gpg key and APT repo
ii  percona-xtrabackup-24             2.4.8-1.xenial                             amd64        Open source backup tool for InnoDB and XtraDB
ii  percona-xtradb-cluster-57         5.7.18-29.20-1.xenial                      amd64        Percona XtraDB Cluster with Galera
ii  percona-xtradb-cluster-client-5.7 5.7.18-29.20-1.xenial                      amd64        Percona XtraDB Cluster database client binaries
ii  percona-xtradb-cluster-common-5.7 5.7.18-29.20-1.xenial                      amd64        Percona XtraDB Cluster database common files (e.g. /etc/mysql/my.cnf)
ii  percona-xtradb-cluster-server-5.7 5.7.18-29.20-1.xenial                      amd64        Percona XtraDB Cluster database server binaries"
1706992,2017-07-27 16:33:15 UTC,That bin log shows the last query that was run as (not sure if this is the problem query)
1706992,2017-07-31 22:34:59 UTC,"Actually I think I found the bug possibly. I followed the stack trace for every one of the crashes (was almost up to 10 times a day, today included so far) and I noticed that nullif was being called followed by three ""trim""s, and I had a generated column on my users table with that exact same function order."
1706992,2017-07-31 13:06:42 UTC,"Yes, I listed those in the initial post as the settings that I added. I have the settings that I've added added to my.cnf listed above, would those settings cause possible crashing? I migrated some rough data from a very old system, and strict mode was causing all sorts of issues, so I added that line manually as a work around."
1706992,2017-07-31 08:05:35 UTC,There are couple of things to consider here:
1706995,2017-07-31 08:12:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489125"
1707001,2017-07-27 15:17:38 UTC,"We should fix this in pike, ocata and newton:"
1707001,2017-07-31 14:04:46 UTC,"Reviewed:  https://review.openstack.org/487179
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bc4f842caccec7641da910bb615cc64cff80d861
Submitter: Jenkins
Branch:    master"
1707001,2017-08-11 12:27:17 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1707001,2017-08-22 11:39:16 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1707001,2017-08-12 06:17:59 UTC,"Reviewed:  https://review.openstack.org/490234
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b0cdac7e3cfa604badf03a9d2239536e47439e34
Submitter: Jenkins
Branch:    stable/ocata"
1707004,2017-07-27 15:53:57 UTC,additional operations posted on pastebin here:
1707004,2017-07-28 08:59:54 UTC,"[root@localhost ~]# lvs
  WARNING: Device for PV mFRxBp-h855-e9nF-gfSs-MVrm-03d1-CGb8ky not found or rejected by a filter.
  LV                                          VG             Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  volume-4ddc80d5-c3ed-4770-a7c6-3c8356674d79 cinder-volumes -wi-------  10.00g
  volume-6ca23cd3-879d-4f22-ac13-95888198cdad cinder-volumes -wi-------   6.00g
  volume-b7fe5630-62cd-4a4b-a0b6-ce3dcc563bdd cinder-volumes -wi-----p-  10.00g
  volume-ec9fd81d-0490-46f4-9d68-d039c002afc5 cinder-volumes -wi-----p-  10.00g
  home                                        cl             -wi-ao---- 100.00g
  root                                        cl             -wi-ao---- 291.76g
  swap                                        cl             -wi-ao----  16.00g
[root@localhost ~]# vgs
  WARNING: Device for PV mFRxBp-h855-e9nF-gfSs-MVrm-03d1-CGb8ky not found or rejected by a filter.
  VG             #PV #LV #SN Attr   VSize   VFree
  cinder-volumes   2   4   0 wz-pn-  60.59g  24.59g
  cl               2   3   0 wz--n- 612.38g 204.62g
[root@localhost ~]# lvremove volume-4ddc80d5-c3ed-4770-a7c6-3c8356674d79 cinder-volumes
  Volume group ""volume-4ddc80d5-c3ed-4770-a7c6-3c8356674d79"" not found
  Cannot process volume group volume-4ddc80d5-c3ed-4770-a7c6-3c8356674d79
  WARNING: Device for PV mFRxBp-h855-e9nF-gfSs-MVrm-03d1-CGb8ky not found or rejected by a filter.
  Logical volume ""volume-4ddc80d5-c3ed-4770-a7c6-3c8356674d79"" successfully removed
  Logical volume ""volume-6ca23cd3-879d-4f22-ac13-95888198cdad"" successfully removed
  Logical volume ""volume-ec9fd81d-0490-46f4-9d68-d039c002afc5"" successfully removed
  Logical volume ""volume-b7fe5630-62cd-4a4b-a0b6-ce3dcc563bdd"" successfully removed"
1707015,2017-08-07 15:02:44 UTC,The patch at https://github.com/ImageMagick/ImageMagick/issues/640 does not fix the issue.
1707015,2017-08-02 17:15:49 UTC,Could you try patch at  https://github.com/ImageMagick/ImageMagick/issues/640
1707015,2017-08-01 11:07:23 UTC,Removing the patch was just a temporary fix until a proper solution is found. Re-opening bug.
1707015,2017-07-31 16:49:01 UTC,This bug was fixed in the package imagemagick - 8:6.8.9.9-7ubuntu5.9
1707015,2017-07-31 16:49:00 UTC,This bug was fixed in the package imagemagick - 8:6.7.7.10-6ubuntu3.9
1707015,2017-07-29 17:39:34 UTC,It's caused by 0224-Ensure-token-does-not-overflow.patch. I'm not sure why yet.
1707015,2017-07-29 15:07:38 UTC,Reporter could you try to bisect ?
1707015,2017-07-28 11:32:15 UTC,"Thanks for reporting this issue, I can reproduce it on Ubuntu 14.04 LTS and Ubuntu 16.04."
1707015,2017-07-30 11:40:13 UTC,"I attempted to downgrade by downloading the 6.7.7.10-6ubuntu3_amd64.deb package, but after removing the 6.7.7.10-6ubuntu3.8 version and installing the regressed version, the defect still seems to be present.  I can wait for the patch to be available, but if someone can offer me some guidance for downgrading to bypass the issue for now, I'd appreciate it."
1707015,2017-07-30 14:47:19 UTC,"Never mind...I believe I figured out my issue.  I had to uninstall the libmagickcore5 and libmagickwand5 packages (along with ImageMagick), download the ""ubuntu3"" .DEB files for those 2 packages as well, and after installing those with the downgraded ImageMagick package, the issue with Variety is now being successfully bypassed."
1707016,2017-07-27 17:23:23 UTC,Syslog from the system
1707016,2017-07-27 21:09:40 UTC,Another bit from Butch:
1707016,2017-07-27 21:47:23 UTC,@Butch
1707016,2017-08-02 11:21:15 UTC,"Hi @Butch,"
1707018,2017-07-27 16:59:06 UTC,"pt-table-checksum --no-check-binlog-format --function murmur_hash -h monty --recursion-method hosts --ignore-tables mysql.gtid_executed,mysql.engine_cost,mysql.server_cost --tables foo.bar"
1707018,2018-01-24 22:26:09 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1435
1707019,2017-07-27 17:38:37 UTC,I added this line to setup.cfg for now:
1707023,2017-09-18 15:33:02 UTC,"Additional:  it seems the trick to making it appear in the dropdown is to switch the connection ""ON"" first."
1707023,2017-09-18 15:29:01 UTC,Would be nice to upstream to https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-control-center by somebody having the issue
1707023,2017-08-12 14:10:24 UTC,"lsusb:
Bus 002 Device 002: ID 12d1:15bb Huawei Technologies Co., Ltd."
1707023,2017-09-09 14:02:59 UTC,"tried it again with daily image from today (9.Sept) still the same, followed the dialog selected My Country and my Network-Provider finished the dialog, no new connection, ""Logs"" shows:
""Failed to add new connection: (7) gsm.username: property is empty""."
1707023,2017-07-27 20:22:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1707023,2017-09-18 15:24:45 UTC,I just tried that here with a ZTE MF112 3G modem.
1707023,2017-08-13 14:53:52 UTC,"workaround:
[Alt] + [F2]
nm-connection-editor
[Enter]"
1707024,2017-07-27 17:22:47 UTC,"It is missing:
https://hub.docker.com/r/coredns/coredns/tags/"
1707026,2017-07-27 20:22:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1707026,2017-07-28 13:19:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1707026,2017-07-28 13:19:50 UTC,"That's a known issue and a design decision from upstream, see e.g https://unix.stackexchange.com/questions/242129/gnome-3-how-to-set-power-button-to-shutdown-instead-of-suspend"
1707026,2017-07-28 13:23:26 UTC,In fact it's already reported upstream as https://bugzilla.gnome.org/show_bug.cgi?id=781108
1707032,2017-07-27 20:11:00 UTC,Apparently this error manifested after today's libinput update. I can confirm it.
1707032,2017-07-28 12:51:16 UTC,After a little more research is appears is has adjusted the mouse/touchpad threshold and acceleration settings. The base speed is too slow and the acceleration too high with a very high threshhold. This leads to a very inconsistent mouse feel.
1707040,2017-07-27 18:48:37 UTC,The version of openstack which devstack is using is pike
1707040,2017-07-31 10:25:22 UTC,Hello
1707040,2017-07-31 23:03:31 UTC,"Hi,christophe.sauthier:
Yes, I can confirm that this bug still exits. Is there anything I should provide with?"
1707040,2017-08-14 07:35:33 UTC,Hello
1707047,2019-11-26 04:17:35 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1707047,2019-09-26 10:59:34 UTC,"Do you still have this problem, and if so, could you share the snap (or how to build it)? This way we might be able to reproduce the issue."
1707047,2017-07-31 06:31:57 UTC,"Ogra, can you reproduce that or is it just a problem of mine?"
1707047,2017-07-31 06:27:09 UTC,Here you are
1707047,2017-07-28 11:15:05 UTC,you syslog might be helpful too (to see possible apparmor denials)
1707047,2017-07-31 06:30:16 UTC,"grep ""audit:"" /var/log/syslog"
1707056,2017-08-21 10:36:42 UTC,"I think it's probably once for downloading and once for installation, slightly annoying I agree."
1707056,2018-03-10 23:27:17 UTC,"The same thing happened to me today, using yesterday's daily build of Ubuntu Budgie 18.04 (32bit) with all updates applied, using Gnome Software v3.27.92."
1707056,2018-03-15 10:12:10 UTC,The upstream bug is now at https://gitlab.gnome.org/GNOME/gnome-software/issues/216
1707064,2017-08-05 09:00:23 UTC,"In my situation, it failed during the install of nvidia driver (381.22)."
1707070,2018-03-12 04:14:48 UTC,"Looks like this is an upstream bug report:
https://github.com/ansible/ansible/issues/31691"
1707070,2019-05-27 20:36:20 UTC,This original code fails:
1707071,2017-10-12 23:43:11 UTC,"Reviewed:  https://review.openstack.org/496847
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e3b7f43e3ae9689967d2ecd1cd7974d829c78c85
Submitter: Jenkins
Branch:    master"
1707071,2017-08-23 18:52:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/496847"
1707071,2017-08-11 02:29:57 UTC,"Reviewed:  https://review.openstack.org/488510
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5390210a4fa46e2af6b6aec9b41c03147b52760c
Submitter: Jenkins
Branch:    master"
1707071,2017-08-10 16:23:50 UTC,"Reviewed:  https://review.openstack.org/491850
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=09e169bd7a74deaf52d9d6d38ff37799cab24157
Submitter: Jenkins
Branch:    master"
1707071,2017-08-08 16:21:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491850"
1707071,2017-08-02 07:04:50 UTC,"Reviewed:  https://review.openstack.org/489714
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dea7a19c361be8180c35ed09ce12434de0e9fc87
Submitter: Jenkins
Branch:    master"
1707071,2017-07-27 22:31:12 UTC,I pushed up a sanity check patch:
1707071,2017-07-27 22:33:56 UTC,From the three points:
1707071,2017-08-03 14:48:46 UTC,"Change abandoned by Jay Pipes (<email address hidden>) on branch: master
Review: https://review.openstack.org/488595
Reason: I'll come back to this later..."
1707071,2017-07-28 20:05:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/488595"
1707071,2017-08-01 19:02:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/489714"
1707071,2017-07-28 16:10:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/488510"
1707080,2017-07-31 11:31:42 UTC,"I can confirm the issue in trunk.
It seems to be an issue with the underlying XML-import library we use (lxml). My guess is that a bug was introduced in the newer version we bundle in 2.4.x. More testing is needed..."
1707080,2017-08-01 19:05:09 UTC,"I've now tested on a system with a newer lxml version (on ArchLinux), and the issue seems to be fixed now. The imported lyrics (first verse) now looks like this:"
1707080,2017-08-03 10:18:21 UTC,"that is very good
I hope I could download this update and try it to make shore that it is ok"
1707080,2017-10-04 07:31:08 UTC,"Not technically a bug with OpenLP, so I've set it to low."
1707080,2017-10-04 07:30:21 UTC,"Unfortunately we're not producing test builds at the moment, however, that is something that Thomas is working on. I will try to remember to inform you as soon as we start releasing test builds."
1707083,2017-07-27 23:47:21 UTC,"StacktraceTop:
 __bswap_32 (__bsx=<error reading variable: Cannot access memory at address 0xc374a91c>) at /usr/include/i386-linux-gnu/bits/byteswap.h:47
 get_leaf_size (buffer=0xc374a91c) at rom1394_internal.c:321
 rom1394_get_size (buffer=0xbff4d0fc) at rom1394_main.c:207
 main (argc=1, argv=0xbff4d5c4) at mkrfc2734.c:59"
1707084,2020-04-29 15:12:15 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/724346"
1707084,2020-05-12 01:16:14 UTC,"Reviewed:  https://review.opendev.org/725110
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=c4f952f5a9996a9ddb3daf50529d1a8142c9a23a
Submitter: Zuul
Branch:    stable/queens"
1707084,2020-05-03 14:32:40 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/725110"
1707084,2020-05-02 16:09:17 UTC,"Reviewed:  https://review.opendev.org/724346
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=fa0b0ec94e319caebe96c4595c60d2c0b803b950
Submitter: Zuul
Branch:    stable/rocky"
1707084,2020-04-11 02:22:10 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/719131"
1707084,2020-04-08 00:22:36 UTC,"Reviewed:  https://review.opendev.org/718053
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=678ea79f85e53ec21a0fb74758875b3a7ebe1aa7
Submitter: Zuul
Branch:    stable/train"
1707084,2020-04-07 10:54:29 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/718053"
1707084,2020-04-07 06:10:28 UTC,"Reviewed:  https://review.opendev.org/712512
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=9250e02b56fa4a0d93fe4c32cdfac4eceab8d095
Submitter: Zuul
Branch:    master"
1707084,2020-03-11 17:20:47 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/712512"
1707084,2017-08-09 21:17:14 UTC,"Missed pike, untargeting"
1707084,2020-04-27 19:22:28 UTC,"Reviewed:  https://review.opendev.org/719131
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=644e2cfc564208bd5b9b3e1201f8f9718ca65823
Submitter: Zuul
Branch:    stable/stein"
1707100,2018-09-19 11:03:15 UTC,"Hello
I'm using lubuntu 18.04 and the problem described above is still  present."
1707105,2017-07-28 14:10:31 UTC,Someone before you complained that staying with the cursor is the wrong way and demanded snapping to the clearance area...
1707105,2017-07-28 22:14:06 UTC,"Cool. Though I'd expect snapping to the valid clearance distance rather
than snapping to a invalid  configuration is what that type of user would
want."
1707107,2018-05-11 16:33:05 UTC,apport information
1707107,2018-05-11 16:32:57 UTC,apport information
1707107,2018-05-11 16:33:01 UTC,apport information
1707107,2018-05-11 16:33:00 UTC,apport information
1707107,2018-05-11 16:32:59 UTC,apport information
1707107,2018-05-11 16:32:57 UTC,apport information
1707107,2018-05-11 16:33:04 UTC,apport information
1707107,2018-05-11 16:32:54 UTC,apport information
1707107,2018-05-11 16:32:55 UTC,apport information
1707107,2018-05-11 15:33:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1707107,2018-05-11 16:32:48 UTC,apport information
1707107,2018-05-11 16:33:02 UTC,apport information
1707107,2018-05-11 16:32:51 UTC,apport information
1707107,2018-05-11 16:32:49 UTC,apport information
1707107,2018-05-11 16:32:53 UTC,apport information
1707107,2018-05-11 16:32:52 UTC,apport information
1707117,2017-07-28 16:57:48 UTC,"Thx, I think it is a kernel bug. So I have assigned now linux-meta-hwe (Ubuntu)"
1707117,2017-07-28 08:23:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1707121,2018-10-01 01:41:59 UTC,"Change abandoned by Kuo-tung Kao (<email address hidden>) on branch: master
Review: https://review.openstack.org/488300
Reason: there is not such option for cinder client"
1707121,2017-07-28 06:03:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/488300"
1707121,2018-09-28 10:43:02 UTC,"To summarize the issue, other clients allow to set internalURL for api communication, cinder not."
1707125,2017-07-28 06:28:20 UTC,complete Fab logs @
1707125,2017-07-28 22:19:42 UTC,"@jebap, we know what went wrong and now setup_all is going through…but not yet identified why it went wrong in the first place"
1707125,2017-08-11 23:02:10 UTC,Fix committed into R3.2 through https://review.opencontrail.org/#/c/34172/.
1707125,2017-08-11 23:03:20 UTC,Issue is already fixed in mainline through #1689640.
1707126,2017-07-28 17:18:22 UTC,"Inkscape sets up shortcuts in GDKs ""group 0"" keyboard layout (so if you switch between different keyboard layouts on the same PC shortcuts stay constant)."
1707126,2017-07-30 05:53:42 UTC,"Thanks for your explanation. The workaround you propose would only work when I'm in colemak, but I regularly use Qwerty too. Why is Inkscape not doing the same as Gimp?"
1707126,2017-07-30 11:53:43 UTC,"Because people were complaining abut shortcuts being dependent on keyboard layout... Inkscape fixed this using custom logic, GIMP uses GTK+ native shortcut handling (with all its advantages and disadvantages)."
1707131,2020-01-22 11:56:11 UTC,"Change abandoned by Eyal (<email address hidden>) on branch: master
Review: https://review.opendev.org/703290"
1707131,2020-01-22 17:21:45 UTC,"Reviewed:  https://review.opendev.org/703290
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=947a986a72a1f2ccf139fd42a33897f8746f89ae
Submitter: Zuul
Branch:    master"
1707131,2020-03-02 14:51:41 UTC,This issue was fixed in the openstack/mistral 10.0.0.0b2 development milestone.
1707136,2017-07-28 07:16:20 UTC,"This should be fixed as of Zesty based on the changelog in the Debian bug report, but remains an issue on Xenial."
1707136,2018-04-04 09:44:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707136,2018-06-20 14:12:07 UTC,"Per former comments marking as fixed and adding Xenial task.
It is still an issue in Xenial, but since no one here was participating I wonder about the severity."
1707140,2017-07-31 13:30:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707151,2017-08-23 16:07:45 UTC,This issue was fixed in the openstack/magnum 5.0.0 release.
1707151,2018-05-09 15:48:14 UTC,This was wrapped up in https://github.com/openstack/oslo.middleware/commit/2b8db6d3989cfc478f575f661cab404163fb15e2
1707151,2018-02-05 22:44:27 UTC,This issue was fixed in the openstack/zun 1.0.0 release.
1707151,2017-08-21 06:27:22 UTC,There is only one place to use set_latent
1707151,2017-08-18 03:25:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/494778"
1707151,2017-08-18 06:57:55 UTC,"Reviewed:  https://review.openstack.org/494780
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=1c265af18209dfc773674abe21b0996f78245f27
Submitter: Jenkins
Branch:    master"
1707151,2017-08-18 03:33:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/494780"
1707151,2017-08-05 00:34:27 UTC,Octavia proposed patch here: https://review.openstack.org/#/c/489169
1707151,2017-07-28 09:21:59 UTC,There are two kinds of usage for set_latent
1707151,2017-08-21 04:16:40 UTC,"Reviewed:  https://review.openstack.org/494778
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=f46cb1fc3d8cfd85e74833380052aacfc716d3a4
Submitter: Jenkins
Branch:    master"
1707159,2017-07-28 12:36:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/488400"
1707160,2017-08-02 18:54:53 UTC,"I marked the bug as fixed for neutron; if you still experience problems with Neutron though, feel free to reopen (a ping in IRC would also help to get my attention)."
1707160,2017-09-06 08:27:39 UTC,This issue was fixed in the openstack/oslo.messaging 5.31.0 release.
1707160,2017-08-22 16:44:38 UTC,"Reviewed:  https://review.openstack.org/486706
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=f059bba6ae9642675bc1c9004a4a4adc5d1b19a6
Submitter: Jenkins
Branch:    master"
1707160,2017-08-07 16:07:17 UTC,Adding oslo to the list of affected projects. The fix is here: https://review.openstack.org/#/c/486706/
1707160,2017-08-07 16:04:10 UTC,"For Neutron, a workaround was committed as: https://review.openstack.org/#/c/490305/"
1707160,2017-08-03 14:32:09 UTC,"It is not clear this is really a Nova bug, putting into incomplete. It's definitely not critical in Nova unless it's confirmed that it's something we need to handle."
1707160,2017-08-03 09:20:56 UTC,Looks like the bug is not related to Nova but rather oslo.messaging to me when looking at the logs and the above discussion.
1707160,2017-08-02 21:02:05 UTC,The issue is extensively being discussed in #openstack-oslo; logs: http://eavesdrop.openstack.org/irclogs/%23openstack-oslo/%23openstack-oslo.2017-08-02.log.html#t2017-08-02T19:18:05
1707160,2017-08-02 19:17:23 UTC,"OK, I still see this failing on a neutron api request here: http://logs.openstack.org/01/489701/1/check/gate-grenade-dsvm-ironic-ubuntu-xenial/50785e5/logs/testr_results.html.gz"
1707160,2017-08-02 18:49:44 UTC,"In the last failure, it's not neutron API but nova API that times out:"
1707160,2017-07-28 10:42:03 UTC,"That's a pretty precise troubleshooting,"
1707160,2017-08-02 18:27:43 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: master
Review: https://review.openstack.org/489697"
1707160,2017-08-02 18:31:05 UTC,The latest recheck on the revert patch suggests that it doesn't help either.
1707160,2017-07-28 10:09:15 UTC,I see http://logs.openstack.org/58/487458/6/check/gate-grenade-dsvm-ironic-ubuntu-xenial/d8f187e/logs/new/screen-q-svc.txt.gz#_2017-07-28_09_15_51_588 happening before the DELETE subnet API request.
1707160,2017-08-01 16:52:16 UTC,We landed a fix for https://bugs.launchpad.net/neutron/+bug/1705351 and think it's related and should help here. Could you please check if you still have the problem?
1707160,2017-08-01 17:09:28 UTC,"Hi Ihar, do you mean the ignoring exception patch? If so, it does help in not raising exception further up, but here we just see some super-slowness from neutron or rabbit, which might be related. This log is what we see after that fix merged. Sometimes we see this not found exception for subnet, sometimes for router, sometimes for router interface, on random api tests as it seems to me."
1707160,2017-08-01 17:10:18 UTC,FYI the neutron fix in question that should have fixed this was: https://review.openstack.org/#/c/485365/
1707160,2017-07-28 10:20:57 UTC,I also see that after reconnection deletion seems to pass:
1707160,2017-08-01 18:13:18 UTC,I think the security groups NotFound error is the result of https://review.openstack.org/#/c/410422/ landed. A possible fix is: https://review.openstack.org/486687
1707160,2017-08-01 18:17:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489697"
1707160,2017-08-01 18:21:42 UTC,Testing two options: revert for security group push notifications patch; and a patch to catch all NotFound for all RPC endpoints; using those two Depends-On patches for ironic:
1707160,2017-08-02 15:58:29 UTC,FYI: Even though https://review.openstack.org/#/c/486687/ (Catch exceptions for all rpc casts) merged it has not resolved the Ironic gate errors we are seeing.
1707160,2017-08-01 17:33:50 UTC,And now I also see this stuff on grenade -- http://logs.openstack.org/42/358142/35/check/gate-grenade-dsvm-ironic-ubuntu-xenial/2e6b101/logs/new/screen-q-svc.txt.gz#_2017-08-01_17_07_08_874
1707162,2017-08-03 18:23:25 UTC,"A lot of users at Veritas have tried the same and its failing for them with a couple of different errors(Please note that for some Users it succeeded at first, but failed later). From what we figured we are only observing issues with “hyperscale-controller” charm (cs:~vtas-hyperscale-ci/hyperscale-controller). It seems that issue is occurring only for charm which has “terms” defined in metadata."
1707166,2017-09-14 10:42:38 UTC,Yeah... A patch should be not so difficult to write. I am not working actively on openstack anymore unfortunately.
1707167,2017-05-19 12:26:23 UTC,The cifs kernel module currently is currently disregarding the nt_status USER_SESSION_DELETED packets sent to it from remote SMB2+ peers and is subsequently holding onto clearly dead SMB2+ sessions as a result.
1707167,2019-02-07 04:25:43 UTC,"This was fixed in :
commit d81243c697ffc71f983736e7da2db31a8be0001f
Author: Mark Syms <email address hidden>
Date:   Thu May 24 09:47:31 2018 +0100"
1707185,2017-10-02 21:52:08 UTC,"Dave, Lwfinger is Larry Finger, the maintainer of the rtl8821ae driver already in Ubuntu 16.04.  When you used his GitHub driver, you had undone a change by Realtek, and that's why it worked.  The Realtek change was 40b368af4b75 (""rtlwifi: Fix alignment issues"") and caused the connection loss."
1707187,2017-09-21 01:01:56 UTC,Can you convert this to a merge proposal?
1707187,2017-09-21 01:55:50 UTC,I committed this with the associated changes to liblightdm and tests.
1707187,2017-09-21 02:36:21 UTC,This has exposed a bug in LightDM - if the greeter does an automatic login without a session set it should use autologin-session (bug 1718565). This may actually solve your original issue.
1707187,2017-09-21 09:07:20 UTC,"Hallo Robert, thanks for merging the fix. Regarding your question in #4 I think the complementary patch in the greeter is still required, since at least the GTK greeter actually *does* select a session on autologin - the default session or the one that has been selected on the last login."
1707195,2017-07-28 12:54:29 UTC,github.com/snapcore/snapd/vendor/gopkg.in/tylerb/graceful.v1 github.com/snapcore/snapd/vendor/gopkg.in/yaml.v2 github.com/snapcore/snapd/wrappers github.com/snapcore/snapd/x11 returned exit code 2
1707200,2017-08-01 10:19:55 UTC,Happy birthday terminator! Thank you for the years we had together and for the years we will have together. Terminator is and will be the one and only for me.
1707200,2017-07-31 14:09:35 UTC,:)
1707208,2017-07-28 13:49:46 UTC,The logs from a bzip2 tar archive of the /var/lib/tomcat8/logs directory contents after the tomcat8 and MetaboAnalyst installation to run as tomcat8. The logs show the messages logged from tomcat8 when the failed connection attempt at the URL...
1707211,2017-07-28 15:28:02 UTC,Thanks!
1707211,2018-09-25 09:24:40 UTC,"@jaya, we can help. You can start."
1707211,2018-08-18 18:43:23 UTC,"are anyone working on this? if not, could i try working on this? i will need mentor/someone to ask though :)"
1707212,2020-02-03 06:21:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707212,2017-08-17 13:51:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707212,2018-05-12 02:42:25 UTC,"Improved workaround so that it's compatible with the alternatives configured by the older lua packages, like lua5.2:"
1707212,2018-05-12 01:42:09 UTC,This is still an issue on 18.04 Bionic.
1707212,2019-12-13 07:52:03 UTC,"I just acme by by accident, but wanted to update that this is fixed in 5.3.3-1 which means >=Bionic"
1707214,2017-10-19 10:13:29 UTC,I was pleased to see that there was a new trusty-updates package for curl that fixes a number of out-of-bounds reads!
1707220,2017-08-01 15:31:11 UTC,"Updates submitted in RDO repos: https://review.rdoproject.org/r/#/c/8045/
Please pay attention as upstream developper told us to be careful with this update, report any issue you'll find asap."
1707220,2017-08-01 12:40:57 UTC,Just cross referencing the Bugzilla on our end: https://bugzilla.redhat.com/show_bug.cgi?id=1468002
1707220,2017-08-01 08:48:22 UTC,"Sweet! Thanks Tim, that should be enough to get a version bump inside of RDO - @dmsimard thoughts? :)"
1707220,2017-08-28 16:53:25 UTC,We'll be able to update eclib to 1.5.0 in RDO once upstream has bumped upper-constraints to 1.5.0 for Ocata. Tim proposed the bump here: https://review.openstack.org/#/c/498521/
1707220,2017-07-29 15:38:53 UTC,"Thanks for the response Tim - I know its not technically a ""libec"" or swift issue as such, but would be cool to debug it further (I'm pretty sure we ran into a similar situation last cycle)"
1707220,2017-07-28 23:16:06 UTC,"It sounds like the proxy worker died trying to service the request, and each time the parent daemon spawned a new one... all the ""Removing dead child <pid>"" messages like http://logs.openstack.org/25/485225/5/check/gate-openstack-ansible-os_swift-ansible-func-centos-7/8ad31e6/logs/openstack/swift-proxy/swift/proxy-error.log.txt.gz#_Jul_24_19_20_58 seem to confirm that."
1707220,2017-07-28 23:14:00 UTC,"Sorry, I thought this was filed as a libec bug - I don't think I have anything helpful to contribute here - sorry."
1707220,2017-07-28 15:08:18 UTC,"Readable stack traces: http://paste.openstack.org/raw/616874/
Full task output: http://logs.openstack.org/25/485225/5/check/gate-openstack-ansible-os_swift-ansible-func-centos-7/8ad31e6/logs/ara/result/28186869-2e52-467a-bbc0-03b39091963e/"
1707220,2017-07-28 23:12:18 UTC,The information needed to debug this is in the proxy log lines.
1707220,2017-07-31 16:47:40 UTC,"Perfect, that's *exactly* what I needed!"
1707223,2017-07-31 15:27:08 UTC,Please check the attached Alarms.PNG which shows that 'Filter' and 'Acknowledge' buttons are missing.
1707229,2017-08-08 08:13:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707238,2017-08-07 21:47:43 UTC,"Reviewed:  https://review.openstack.org/488545
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d39934ad6afb7e2729bb45235f363ada86012d15
Submitter: Jenkins
Branch:    master"
1707238,2017-07-28 17:26:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/488545"
1707238,2017-08-07 23:29:27 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/491630"
1707238,2017-08-11 12:27:08 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1707238,2017-08-16 02:30:55 UTC,"Reviewed:  https://review.openstack.org/491625
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=539d3bbb8aced7703914bb7ef0b72ac3a471c54e
Submitter: Jenkins
Branch:    stable/ocata"
1707238,2017-08-17 03:18:09 UTC,"Reviewed:  https://review.openstack.org/491630
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dd925025543bfd1c826db728caf9832f44c1bacd
Submitter: Jenkins
Branch:    stable/newton"
1707238,2017-08-22 11:39:03 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1707238,2017-08-28 09:54:57 UTC,This issue was fixed in the openstack/nova 14.0.8 release.
1707238,2017-07-28 20:53:28 UTC,Here are the steps to reproduce the bug:
1707238,2017-08-07 23:11:07 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/491625"
1707243,2017-09-05 16:09:50 UTC,This issue was fixed in the openstack/puppet-tripleo 6.5.1 release.
1707243,2017-09-04 18:16:29 UTC,This issue was fixed in the openstack/puppet-tripleo 5.6.2 release.
1707243,2017-08-14 17:34:17 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/493619"
1707243,2017-07-31 16:45:24 UTC,"Reviewed:  https://review.openstack.org/488514
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=f175a6e2820b0f05eca15f882b3b271b99790774
Submitter: Jenkins
Branch:    stable/ocata"
1707243,2017-07-28 16:18:02 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/488514"
1707243,2017-08-17 07:36:48 UTC,"Reviewed:  https://review.openstack.org/493619
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=8a154df52af7ba21e468806618e88316c0bc90d7
Submitter: Jenkins
Branch:    stable/newton"
1707247,2017-10-08 18:21:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707249,2018-05-08 07:26:49 UTC,I can confirm the bug in Xubuntu 18.04 (64 bits).
1707250,2017-07-28 16:42:48 UTC,"The attached file inkscape_selection_tool_control_points_fix_proposal.webm
shows my proposal to fix the issues from above."
1707250,2017-07-28 17:28:32 UTC,"> The doubt I still have is about the _grip control point,
> should it be always displayed or could it be removed completely?
"
1707250,2017-07-28 17:30:59 UTC,"P.S. I don't think the _grip control point is necessary (I never missed it ;-) ), but if we already have code for it I guess it also does not hurt to fix it and show it. After all it's an indicator for the user which point is actually being dragged."
1707250,2017-07-28 17:54:25 UTC,">> The doubt I still have is about the _grip control point, should it be
>> always displayed or could it be removed completely?
"
1707250,2017-07-31 09:00:40 UTC,MR sent: https://gitlab.com/inkscape/inkscape/merge_requests/55
1707250,2018-10-30 08:39:04 UTC,"A fix was committed in master, see the merge request page for info."
1707256,2018-01-05 15:17:12 UTC,I *think* this has now been addressed in Queens.  Marking Incomplete pending confirmation from Jay/Matt/Chris.
1707256,2017-10-03 21:56:39 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/491098"
1707256,2017-10-27 04:11:18 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/490733"
1707256,2017-08-07 19:47:54 UTC,We're just going to document this as a limitation for Pike in the release notes (it's really an incomplete feature) and work on it in Queens.
1707256,2017-08-07 19:26:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/491582"
1707256,2017-08-04 21:17:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491098"
1707256,2017-08-10 00:48:11 UTC,"Reviewed:  https://review.openstack.org/491582
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0d31698d9e97e98f599f6b7ee0f1533677deee97
Submitter: Jenkins
Branch:    master"
1707256,2017-08-04 03:29:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/490733"
1707267,2017-07-28 18:28:10 UTC,"autopkgtest [11:09:53]: test boot-smoke: [-----------------------
...
checking that there are no running jobs
running jobs after remaining timeout -1:
 61 apt-daily-upgrade.timer            start waiting
209 systemd-hostnamed.service          start running
 64 NetworkManager-wait-online.service start running
 59 timers.target                      start waiting
 63 network-online.target              start waiting
 62 apt-daily.timer                    start waiting
autopkgtest [11:10:53]: test boot-smoke: -----------------------]
autopkgtest [11:10:53]: test boot-smoke:  - - - - - - - - - - results - - - - - - - - - -
boot-smoke           FAIL non-zero exit status 1"
1707267,2017-07-28 18:50:59 UTC,This has been noted. Also we have similar reports that ubuntu starts degraded in containers by default on all arches in artful at the moment.
1707268,2017-09-04 09:12:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707268,2017-09-04 10:51:13 UTC,I can confirm this bug.
1707268,2017-10-02 00:27:07 UTC,"I tried this in an Artful LXD container, the attached log might be relevant."
1707272,2017-07-28 19:09:24 UTC,Marking it as medium since workaround available
1707272,2017-07-28 19:13:48 UTC,[root@overcloud-novacompute-0 heat-admin]# ldconfig
1707272,2017-08-18 18:14:49 UTC,"one of my customer also ran into this.
He was running Contrail 3.2.4.4"
1707276,2017-07-28 19:25:38 UTC,"edit: sorry I meant ""snap to upper HALF of screen"" not ""upper left corner""."
1707276,2017-07-28 20:29:07 UTC,"edit: actually, snapping to upper left corner breaks it too."
1707278,2020-07-13 03:15:12 UTC,"Thanks @Andersoyvind, It's working."
1707278,2019-01-17 10:43:14 UTC,"Also experiencing this, version 1.91."
1707278,2017-10-06 09:30:20 UTC,I don't know why.. It seems like shortcut for 'hide_window' Shift+Ctrl+Alt+a is fired when I press Ctrl-Alt-a
1707278,2018-08-28 16:19:02 UTC,"This bug still exists. It collides with Ctrl+Alt+a as a shortcut to git ""Add file"" in Jetbrains IDEA.
Disabling Ctrl+Alt+A in terminator preferences did not help.
I had to additionally disable Shift+Ctrl+Alt+A . Otherwise shortcut was ""stolen"" by terminator - even though there was no focus on terminator window !
This might be related to the fact that IIRC letter ""a"" in terminator config file was in fact a capital ""A"" which may have been resolved as : Ctrl+Alt+A=Ctrl+Alt+(Shift+a)
...if you know what I mean..."
1707278,2017-07-31 17:26:12 UTC,"Thank you. That was embarrassing.
But still I cant see any shortcuts in Keybindings which correspond to C-M-A so not sure how to overrride that."
1707278,2017-07-31 17:45:53 UTC,Ctrl-***Meta***-A? Or Ctrl-***Alt***-A?
1707278,2017-07-29 15:52:15 UTC,Why edit the config file? There's a perfectly good preferences tab for configuring keyboard shortcuts (Keybindings).
1707278,2017-08-01 16:47:47 UTC,Ctrl-***Alt***-A
1707278,2017-07-30 01:23:47 UTC,"Apologize for not mentioning info
$ terminator -v
terminator 1.90"
1707278,2017-07-30 16:58:35 UTC,O_o
1707278,2017-07-29 15:54:05 UTC,Reassigning these keys is working for me. So I can't decide if this is Invalid (a support request) or Incomplete (not enough info to understand your issue). I'll err on the side of caution.
1707285,2017-07-31 14:13:28 UTC,Reworked pull request:
1707285,2017-08-01 18:29:31 UTC,"Please merge the pull request too:
https://github.com/dcui/linux/compare/350771e4b20a888e9d5d857f46497ae08e8cf8bb...dcui:decui/upstream-ubuntu-marcelo/lp1707285-update-linux-azure
(only 2 patches)"
1707285,2017-08-07 13:41:30 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086122.html
1707285,2017-08-16 01:39:51 UTC,"I created a new pull request against the master-next branch (709d133bc3132eac96e455b9c94b8c5b78479393, Ubuntu-azure-4.11.0-1006.6) of https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/log/?h=master-next:"
1707288,2020-07-27 15:50:51 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/488849"
1707288,2019-02-06 22:46:35 UTC,https://review.openstack.org/#/c/488849/
1707291,2017-07-31 01:31:31 UTC,"I just learned about a discussion on the Ubuntu Mate forum regarding ""Developing a Window Buttons Applet for Mate."" See https://ubuntu-mate.community/t/developing-a-window-buttons-applet-for-mate/8637"
1707291,2017-08-15 12:58:20 UTC,"This is on the roadmap, no ETA yet."
1707291,2017-11-01 12:02:12 UTC,there is an applet for mate panel for this https://github.com/IKRadulov/mate-window-applets
1707291,2018-03-11 08:23:12 UTC,"It would be great if maximized window control buttons moved to the panel and also window title disappear, like in Unity and MacOS. It is a total waste of space."
1707291,2018-06-10 09:34:04 UTC,"I consider this issue to be a kind of serious
- you maximize a window and find after the maximization the control buttons of maximized window in the global menu bar. It is even worse: the control buttons are multiplied when the are in the wrong location (global menu). For your reference, please see screenshot attached"
1707291,2017-07-28 20:35:31 UTC,"I'll just add that, as an alternative to displaying the window control buttons (close, min, and unmax buttons) within the Global Menu itself, displaying them within a separate panel applet (which could be independently positioned on the panel) would also be great."
1707294,2017-07-28 20:28:58 UTC,virtual memory exhausted: Cannot allocate memory
1707294,2017-08-03 13:22:19 UTC,"This happened again on retry, so re-opening bug."
1707295,2018-05-11 03:58:33 UTC,To do this you'd have to provide AppStream data with that package.
1707297,2017-07-31 12:39:13 UTC,"On 07/31/2017 03:34 AM, Markus Armbruster wrote:

> John Florian <email address hidden> writes:
>
>> Public bug reported:
>>
>> With qemu-kvm-2.9.0-3.fc26.x86_64 I am no longer to specify the memory
>> size using something like ""-m 1.00000GiB"" but with qemu-
>> kvm-2.7.1-7.fc25.x86_64 I could without any problem.  I now get an error
>> message like:
>>
>> qemu-system-x86_64: -m 1.00000GiB: Parameter 'size' expects a non-negative number below 2^64
>> Optional suffix k, M, G, T, P or E means kilo-, mega-, giga-, tera-, peta-
>> and exabytes, respectively.
>>
>>
>> Is this expected or a regression?
>
> We recognize suffix ""G"".  Before commit 75cdcd1 (v2.9.0), trailing
> garbage after a recognized suffix was silently ignored.  ""1.0G"",
> ""1.0GiB"", ""1.0Garbage-trucks-of-RAM"" were all the same to QEMU.  No
> more.
>
> All clear?
"
1707297,2017-07-31 13:09:20 UTC,Not sure why I can only see Markus' comment here as part of Eric's but anyway... the behavior change *is* expected.
1707297,2020-09-26 17:04:44 UTC,Looks like nobody cared to implement this within 3 years ... and IMHO it's maybe even better to not overload the CLI syntax too much ... so I'm closing this ticket now.
1707306,2017-07-28 21:36:35 UTC,This affects flashrom 0.9.9~rc1+r1942-1 on Ubuntu 16.04
1707306,2019-01-30 08:39:05 UTC,can you confirm bionic is not affected anymore?
1707306,2019-02-08 08:24:41 UTC,"On 2019-01-30 09:39, Lenin wrote:

> can you confirm bionic is not affected anymore?
>
"
1707307,2017-08-25 17:37:41 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/498000"
1707307,2017-08-25 17:37:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/498001"
1707307,2017-08-25 17:38:05 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/498002"
1707307,2017-08-29 02:13:37 UTC,"Reviewed:  https://review.openstack.org/496927
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=de712bf467888b05de14bcbe6e65cc1765692c62
Submitter: Jenkins
Branch:    stable/pike"
1707307,2017-08-29 04:07:53 UTC,"Reviewed:  https://review.openstack.org/498002
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=406472f3ea5aebbb6d02763cf21da4488095daed
Submitter: Jenkins
Branch:    stable/newton"
1707307,2017-08-29 04:16:05 UTC,"Reviewed:  https://review.openstack.org/498000
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=38a98fcfed5c40bf031fe1cc96359a819dc4953c
Submitter: Jenkins
Branch:    stable/pike"
1707307,2017-08-31 16:03:50 UTC,"Reviewed:  https://review.openstack.org/499533
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=22a63315d85db05eaa67f3599caa82c5966b880c
Submitter: Jenkins
Branch:    stable/pike"
1707307,2017-08-31 09:23:55 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/499533"
1707307,2017-09-19 19:21:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505384"
1707307,2017-09-23 00:39:45 UTC,"Reviewed:  https://review.openstack.org/505384
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f8fb73aa30f075712b5ca18c78b88d6ae9e60566
Submitter: Jenkins
Branch:    master"
1707307,2017-09-23 20:15:05 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/506892"
1707307,2017-10-14 00:43:36 UTC,"Reviewed:  https://review.openstack.org/506892
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4cbf3153e840315daae698037ec9c6a785d4e5d8
Submitter: Jenkins
Branch:    stable/pike"
1707307,2017-08-25 02:58:33 UTC,"Reviewed:  https://review.openstack.org/492421
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=03898582c81547f048fd9c1d51527c7f6c44f6ba
Submitter: Jenkins
Branch:    master"
1707307,2017-08-29 17:13:43 UTC,"Reviewed:  https://review.openstack.org/498001
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1c6d8b255baea287489db8a36c339798ddc1b44f
Submitter: Jenkins
Branch:    stable/ocata"
1707307,2017-08-23 21:23:12 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/496927"
1707307,2017-08-10 07:52:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492420"
1707307,2017-08-15 15:18:07 UTC,"Reviewed:  https://review.openstack.org/492420
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2d8ffe2a08120f835c875060a197b4db2ec8c735
Submitter: Jenkins
Branch:    master"
1707307,2017-07-31 18:47:30 UTC,"From the file you linked, two-thirds of the lines are from ovsdbapp:"
1707307,2017-08-23 11:09:41 UTC,"Reviewed:  https://review.openstack.org/492418
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=62c1a4b6873d0b2382349ece65545bf28c9c87ca
Submitter: Jenkins
Branch:    master"
1707307,2017-07-31 23:00:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489429"
1707307,2017-07-31 23:00:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489430"
1707307,2017-08-02 00:57:23 UTC,"Reviewed:  https://review.openstack.org/489430
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d92dc1244ed8277bf0c204448b49a425b40f55b1
Submitter: Jenkins
Branch:    master"
1707307,2017-07-31 22:59:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489428"
1707307,2017-08-02 21:27:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490212"
1707307,2017-08-02 17:42:54 UTC,"Reviewed:  https://review.openstack.org/489428
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ce8dbcff838a6e89cba87882d84365db590508b8
Submitter: Jenkins
Branch:    master"
1707307,2017-08-02 21:36:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490213"
1707307,2017-08-10 07:51:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492418"
1707307,2017-08-10 07:51:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492419"
1707307,2017-08-12 06:04:10 UTC,"Reviewed:  https://review.openstack.org/489429
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=72f7f1eaa8a4b9b2c792d4466506b8164020d922
Submitter: Jenkins
Branch:    master"
1707307,2017-08-14 01:44:34 UTC,"Reviewed:  https://review.openstack.org/490213
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1865f27a8b98f322caaad46cbb145c0972753d84
Submitter: Jenkins
Branch:    master"
1707307,2017-08-14 12:38:53 UTC,"Reviewed:  https://review.openstack.org/492419
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c36676877eccca983aba1bf64a953bc65bf78c36
Submitter: Jenkins
Branch:    master"
1707307,2017-08-02 21:32:15 UTC,"Change abandoned by Miguel Lavalle (<email address hidden>) on branch: master
Review: https://review.openstack.org/490212"
1707312,2017-10-05 21:22:00 UTC,"The moment we have a reload action in systemd (via ExecReload), then ""service lighttpd reload"" will call that instead of the misnamed and broken one from the sysv script. We are changing behavior of the reload action, but I think we have to: we are changing it from a broken restart to an actually working reload. That should be acceptable for an SRU as it gets us into a better situation I think."
1707312,2017-10-05 21:34:14 UTC,"Nice! ""KillMode=mixed"" is important here, though."
1707312,2017-10-05 21:49:47 UTC,"Yeah, CanReload will only be true if the service has a ExecReload config. I was toying with this for a bit:
[Service]
...
ExecReload=/bin/kill -HUP $MAINPID"
1707312,2017-10-06 14:51:28 UTC,"Can you comment on why KillMode needs to be set to ""mixed""? The default is control-group. The sysv script also only seems to kill the main process (which could be a bug, granted). Is it because of CGI scripts?"
1707312,2017-10-06 15:14:32 UTC,From systemd documentation:
1707312,2017-10-06 19:07:35 UTC,Filed https://redmine.lighttpd.net/issues/2825 upstream
1707312,2020-09-23 22:06:25 UTC,"Well, the issue is still not resolved in Ubuntu 16.04 and probably 18.04 as well. And 16.04 is still supported. Let's wait until 16.04 support ends and close this instead of fixing or backporting new version."
1707312,2017-11-18 02:20:35 UTC,"So, what is going on with this bug? Do more people need to test the package before it goes into repository?"
1707312,2017-12-06 18:24:01 UTC,"I would like the opinion of more people, yes. I fear we are changing the behavior of the restart action. Before it would be immediate (tearing down live connections), whereas with the fix it is transformed into a graceful-restart. Normally services have these two options separate so that the admin can choose. That was the case with the sysv script. But now with the systemd service file that choice is no longer available."
1707312,2017-12-06 23:24:33 UTC,"Actually this wasn't the case with sysv script. If you remember, sysv script was the first thing I attached patch for, because it was obviously bugged: both --signal and change --retry options given, so a signal given with --signal was simply ignored. If you check sysv script in Debian, at least in wheezy, you will find it wasn't using --retry at all, so only --signal INT was used, which is exactly as we are trying to achieve now. There was never supposed to be an ungraceful restart option. It appeared only because someone made a mistake when modified sysv script."
1707312,2017-12-06 23:30:46 UTC,"Hmm, I was wrong. Actually, sysv script in Debian Wheezy was using TERM for stop (and thus for restart as well), and INT for reload and force-reload. So yes, you were right, there was a way to kill it ungracefully. But documentation never suggested anything but force-reload to apply new settings, which is supposed to be graceful but is broken currently."
1707312,2020-09-23 21:53:59 UTC,"lighttpd 1.4.46 was released in Oct 2017, almost 3 years ago.
Is there any reason this is still open?"
1707312,2020-09-23 23:35:22 UTC,"See Bug #1721635
https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/1721635"
1707312,2017-10-05 21:15:27 UTC,"Haha, I had almost the same thing :)"
1707312,2017-10-06 21:04:12 UTC,"Test packages are building here for xenial, zesty and artful: https://launchpad.net/~ahasenack/+archive/ubuntu/lighttpd-reload-1707312-1721635"
1707312,2017-10-05 20:47:40 UTC,"Ok, I'm really sorry for spamming, but here's a proper fix for systemd's lighttpd.service. After these changes command `systemctl force-reload lighttpd.service` does a proper graceful reastart. It will also kill all children after 60 seconds in case something goes wrong (for example, if lighttpd fails to kill spawned fcgi processes). This patch should make everyone happy. :)"
1707312,2017-10-04 22:27:11 UTC,"Ah, nice. So ""force-reload"" is the right name, but for some reason ""reload"" is aliased to it."
1707312,2017-10-05 20:15:32 UTC,https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/1721635
1707312,2017-10-05 20:31:20 UTC,I see. Can you just fix systemctl's force-reload action to send SIGINT instead of SIGTERM? I am not familiar with systemd and couldn't find where it's defined.
1707312,2017-07-28 23:29:33 UTC,After reading man start-stop-daemon I found the problem.
1707312,2017-07-29 00:21:52 UTC,"The attachment ""lighttpd.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1707312,2017-08-17 08:29:55 UTC,Can someone please review and accept patch? This is pretty-much critical issue for those using lighttpd as a primary web server.
1707312,2017-09-22 09:29:37 UTC,"Hello? Anyone here? If this package is not supported, please remove it from repository then."
1707312,2017-09-22 09:35:26 UTC,"Since Ubuntu Review Team is ignoring this ticket, I subscribed Robie Basak and Artur Rona. Hope you guys can help."
1707312,2017-09-25 13:34:00 UTC,"Andreas, could you validate this and convert it into a suitable form for upload, please?"
1707312,2017-10-04 22:02:12 UTC,"The only way to reload configuration is actually through a graceful restart, so that's why they called it ""force-reload"", I guess. I don't know when ""force-reload"" and ""reload"" became aliases, though. Renaming might be a good idea, but then /usr/sbin/lighty-{enable,disable}-mod scripts should be updated as well. And probably some docs too."
1707312,2017-10-04 20:16:22 UTC,"xenial is a confusing case, at least it was to me. The package has both a sysv initscript and a systemd service file."
1707312,2017-10-05 19:55:17 UTC,"Ok, sorry for spamming on this bug, but I'm not happy with that reload action, fixed or not. Everything breaks after it's issued, it's not just status: stop, start and restart also don't work anymore. I'm having a hard time overlooking that. I'll file a separate bug."
1707312,2017-10-05 19:31:20 UTC,"Yes, if all is done via systemd, then status after reload works. But that change is too much for an SRU I think."
1707312,2017-10-05 15:27:21 UTC,I believe it should all be done via systemd instead. Less work in the future when sysv will be deprecated. But as a quick solution an obvious bug should be fixed right now.
1707312,2017-09-25 21:21:52 UTC,"The analysis is correct and easy to reproduce. Just keep a connection open to the server and issue the reload. Without the fix, the connection is terminated immediately. With the fix, the timeouts are respected, and if the connection is closed before the timeout is reached, the reload action continues."
1707312,2017-10-04 22:14:35 UTC,"""reload"" and ""force-reload"" are defined in
https://www.debian.org/doc/debian-policy/#writing-the-scripts"
1707312,2017-10-04 20:18:04 UTC,"""reload"" the way it is implemented should be called something else: ""graceful-restart"" probably, because that's what it is (even in the source code)."
1707312,2017-10-05 15:00:08 UTC,"Ok, so I just need to sort out the fact that ""status"" doesn't work after that ""reload"" (because there is a new process, and the reload was done via the sysv script while the status is done via systemd). One could argue this is a different bug, though."
1707313,2017-07-31 12:18:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707313,2018-01-27 18:42:34 UTC,"Yes, it happens in 'dropbox' on 16.04 LTS, Gnome Flashback."
1707313,2018-04-06 18:50:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707324,2017-10-06 10:54:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707324,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1707325,2017-07-29 09:12:04 UTC,Could we also perhaps have an option to specify that the name being given is in the binary namespace? So:
1707327,2017-08-02 16:37:20 UTC,Also see bug 1595744
1707330,2017-07-29 14:33:01 UTC,"I suspect the game Ace Penguin freecell from having this bug, because it happened when I played with it."
1707330,2017-08-07 02:45:22 UTC,"Ace Penguin is not the culprit, it happens more times with other programs."
1707341,2020-05-25 02:41:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707341,2020-06-03 20:46:07 UTC,"thank you for your bug report, if the kernel crash it's a bug there, it should be robust to anything userpace is doing, reassigning"
1707354,2017-07-29 07:10:28 UTC,Similiar to this bug https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1573762 but I am using Intel® HD Graphics 520 (Skylake GT2)
1707354,2017-08-26 08:58:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707360,2017-07-30 09:24:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707365,2017-07-30 14:00:33 UTC,"AFAICT, the defs are all in use in the file icons.svg."
1707365,2020-01-11 06:39:15 UTC,Closing as it is resolved by TylerDurden's post.
1707366,2017-10-20 00:32:02 UTC,I'd like a policy decision (or perhaps a ubuntu-devel ML post) to decide this.
1707367,2017-10-20 00:32:38 UTC,I'd like a policy decision (or perhaps a ubuntu-devel ML post) to decide this.
1707367,2017-10-24 00:02:52 UTC,"And I think that with the quiltify/changelogify changes landed, that it's less controversial to use patches-applied by default."
1707367,2017-07-29 16:04:27 UTC,"I think this goes back to the idea that submit and/or lint would be able to
determine if upstream changes have been made, transform ""new"" git commits
(commits relative to nearest pkg/ branch) into quilt patches (which might
fall if dpkg-source --commit fails) and provide (always) a
patches-unapplied version of any change(s) or emit a warning otherwise. A
nice sanity check is that in all cases where the above works, we should be
able to derive an original and new treeish of the upstream source and they
should match."
1707367,2017-07-29 16:53:21 UTC,"I'm not keen on automatic folding into quilt patches. What we want are any changes correctly squashed into the correct quilt patches. If a drive-by contributor isn't operating quilt directly, it seems unlikely that the squashing would get done first. I'm concerned that if we encourage use of automatic tooling that will be wrong, people will treat that as a shortcut to checking that it is done properly."
1707370,2017-07-31 12:58:36 UTC,"@lah7's working on that.
See here for more info:
https://ubuntu-mate.community/t/sneak-peek-new-software-boutique-17-10/13891"
1707371,2017-07-29 12:48:23 UTC,- confirmed using Inkscape 0.92.1 r15371 and the file example.svg from comment 2.
1707371,2019-05-17 09:02:53 UTC,"Hi there, this bug has been migrated to our new GitLab bug tracker. Please follow there for all future updates. Thank you!"
1707371,2017-07-29 11:58:25 UTC,Here you are:
1707371,2017-07-29 11:23:46 UTC,thank you for taking the time to issue a report.
1707373,2017-07-29 11:31:48 UTC,thank you for taking the time to issue a report.
1707373,2017-07-29 11:37:18 UTC,"- problem not reproduced using Inkscape 0.92.2pre0 (973e216, 2017-07-25)
- in this case I get no output and no error message"
1707373,2020-10-20 03:57:01 UTC,"Replicated in Inkscape 0.92.5 (2060ec1f9f, 2020-04-08)"
1707378,2019-05-13 15:32:15 UTC,Was this defect discussed at the PTG in Denver?
1707378,2020-04-23 04:17:18 UTC,[Expired for Manila because there has been no activity for 60 days.]
1707378,2019-04-29 14:55:27 UTC,Hi Zhongjun is there any progress with this are you still seeing an issue?
1707378,2017-08-10 14:55:48 UTC,"We have two or more ways to fix this bug,
1. We could combine the quota record in db if these quota's user_id, project_id and share_type_id etc at the same when we create a share.
2. The quota reserve and commit model has many problems [1]. We could just remove the quota model in the code."
1707378,2019-04-30 01:20:07 UTC,"sorry, it isn't any progress with this."
1707382,2017-08-09 07:16:29 UTC,any updates on this?
1707393,2017-07-29 19:37:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707393,2017-08-18 16:15:30 UTC,Reporter of #1710503 uses mesa-vdpau-driver. Re-assigning accordingly.
1707393,2017-09-03 12:08:17 UTC,"As a workaround switching the ""Output"" parameter from ""Automatic"" to ""X11 video output (XCB)"" restores video."
1707393,2017-09-03 12:17:01 UTC,About the packages that were upgraded. This bug appeared a few days before it was reported here on 2017-07-29. I can remember I tried to investigate for a few days before finding and confirming this bug report.
1707393,2017-10-22 22:17:04 UTC,"Hi, I also have the same pb."
1707393,2017-12-09 00:19:57 UTC,This bug also appears on a fresh install of Kubuntu 16.04 which was then immideately upgraded to Kubuntu 18.04 Ubuntu Bionic Beaver (development branch).
1707393,2017-08-11 21:48:25 UTC,So this sound like a driver bug then. What VDPAU driver do you use and which packages were upgraded?
1707395,2017-08-21 06:44:43 UTC,"Ok, the difference on i2c-designware between 4.10 and 4.13 are quite huge, it's not a good idea to backport those commits back to 4.10, it's quite likely to cause regression."
1707395,2017-08-19 08:24:10 UTC,"Ok, so it's the i2c support from i2c-designware:"
1707395,2017-08-18 21:32:52 UTC,Output of the udevadm when booted 4.12
1707395,2017-08-18 21:32:11 UTC,Output of the udevadm when booted 4.13-rc1
1707395,2017-08-17 07:21:44 UTC,Can you attach `udevadm info -e` under 4.12 and 4.13-rc1? Or do you know which driver does the touchpad use?
1707395,2017-08-16 12:04:38 UTC,Since release 4.13-rc1 the touchpad starts to work
1707395,2017-08-15 00:56:41 UTC,I tried both of them. The problem persists and touchpad is not detected.
1707395,2017-08-15 02:07:45 UTC,"OK, so the commit(s) that enables the touchpad is in 4.13-rc1 to 4.13-rc4."
1707395,2017-07-29 14:00:05 UTC,This change was made by a bot.
1707395,2017-08-10 17:08:08 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1707395,2017-08-12 16:48:20 UTC,That package does not appear as available to me. Perhaps it is because I already update to 17.04?
1707395,2017-08-12 06:45:27 UTC,"Try use ""linux-generic-hwe-16.04-edge""."
1707395,2017-08-11 03:57:48 UTC,Hello.
1707395,2017-08-14 07:10:16 UTC,"Can you try mainline kernel 4.11, 4.12?"
1707403,2018-01-24 22:26:07 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1436
1707409,2017-07-29 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1707409,2018-06-27 09:16:48 UTC,Setting qemu task to invalid per Colins explanation that the LP case doesn't use it.
1707409,2017-09-06 09:55:01 UTC,"Interesting, so somewhat the system is triggering an illegal arm64 instruction? Can be that gdb needs somebody telling it to use armhf platform?"
1707409,2017-09-06 09:28:47 UTC,qemu isn't involved.  We intentionally run armhf builds on an arm64 kernel (with an appropriate personality set) because this allows us to make denser use of our build resources; I don't expect this to change.
1707409,2017-08-10 13:20:16 UTC,"Well, LP builders have qemu 2.5, so this might be true for the syscall."
1707409,2017-08-10 06:20:06 UTC,There is two issues being mixed up here
1707409,2017-08-09 14:19:31 UTC,">I agree on 384 being getrandom and there are other cases like [1].
"
1707409,2017-07-29 15:38:34 UTC,"I'm assigning launchpad, maybe somebody can try notmuch/armhf with an updated qemu or a downgraded kernel :)"
1707409,2017-08-08 10:36:01 UTC,"well, some tests are failing just because of 384 non implemented on artful
T150-tagging: Testing ""notmuch tag""
 FAIL   Xapian exception: read only files
 --- T150-tagging.24.expected	2017-08-08 10:28:25.000000000 +0000
 +++ T150-tagging.24.output	2017-08-08 10:28:25.000000000 +0000
 @@ -1 +1 @@
 -A Xapian exception occurred opening database
 +"
1707409,2017-07-29 19:20:33 UTC,"Yes, the nature of the bug makes impossible to do as requested by the bot…"
1707409,2017-07-31 08:43:24 UTC,"I think it's very unlikely indeed that this is a Launchpad bug, and we're not here to go on fishing expeditions for you testing random things.  qemu/kernel developers are generally better placed to be able to bisect this sort of thing.  Of course you can reopen this if there turns out to be some evidence that this is in fact a Launchpad bug."
1707409,2017-08-09 09:04:46 UTC,"I agree on 384 being getrandom and there are other cases like [1].
I don't know details but would consider the pure lack of the system call support a feature request to upstream qemu.
We could add a qemu upstream task here for that FR - in the worst case we are told why we are wrong - opinions?"
1707409,2017-08-08 09:52:43 UTC,">And with that finally I found:
>override_dh_auto_test:
>ifeq ($(DEB_HOST_ARCH),armhf)
>        TERM=vt100 dh_auto_test || true
>Which means it is not meant/expected to work properly on archhf.
"
1707409,2017-08-08 10:29:30 UTC," +qemu: Unsupported syscall: 384
 +qemu: Unsupported syscall: 26
 +exit status: 255"
1707409,2017-08-08 09:27:50 UTC,"TL;DR:
- you can use the pbuilder + static qemu setup to debug
- qemu/libvirt throw no error
- the tests do not ""consider"" the unsupported syscall
- I found to get just the same issues on Artful but with more context indicating that missing syscall
- You can use the setup described above (or sbuild) to debug further as there are 1-2 issues which seem to have other reasons e.g. ""Xapian exception: read only files""
- the testcases might need several fixes, but one of them is surely to test not only if gdb is installed, but if it is working."
1707420,2017-08-19 13:54:09 UTC,Everything seems to be fine after running the following command:
1707421,2020-09-09 08:37:31 UTC,"Closing given native macOS Inkscape 1.0 makes this report obsolete. If there are issue with the native release, please check here to see if it has been reported: https://inkscape.org/inbox. Thank you!"
1707429,2017-08-31 23:24:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707454,2017-07-29 22:55:06 UTC,http://bazaar.launchpad.net/~online-accounts/account-plugins/trunk/view/head:/data/providers/facebook.provider.in.in#L8
1707455,2017-07-29 23:12:19 UTC,apport information
1707455,2017-07-29 23:12:20 UTC,apport information
1707455,2017-07-29 23:12:22 UTC,apport information
1707456,2017-11-14 14:05:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707456,2018-06-16 17:31:51 UTC,"I have seen this issue for monitors of mismatched resolutions. What resolutions do you have? Also, are the position of the monitors ""snapped"" on the xrandr tool?"
1707459,2017-07-31 11:47:40 UTC,This is not a bug in my opinion.
1707459,2017-09-02 08:05:17 UTC,For Percona Server it makes sense to support clause CHANGE MASTER ... KEEP RELAY LOGS; to keep them no matter if RELAY_LOG_FILE/POS specified or not
1707459,2018-01-25 09:39:07 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2506
1707461,2019-02-15 01:34:11 UTC,similar problem under ubuntu 18.04 with all updates:
1707461,2017-08-01 14:35:17 UTC,"I am not exactly sure how you created the dir in the first place, but the error is coming from the system itself, not duplicity.  What is the filesystem encoding?  Is it the same system the file was created on?"
1707461,2018-02-21 15:45:25 UTC,"I am having the same issue, running on Ubuntu 16.10."
1707461,2018-02-21 15:50:54 UTC,"The file had a wrong encoding itself (not only in the backup). This means, that it included non-utf-8 characters and nautilus also mentioned that the encoding is invalid. Anyways it is not satisfying that the restoring stops and fails because of this. A little better but still not good were, if the file could be skipped."
1707481,2017-07-30 08:50:37 UTC,Update:
1707487,2017-07-31 09:20:12 UTC,"Now the Ubuntu updater is doing a ""partial upgrade"". I hope I don't break anything?!!"
1707487,2017-10-02 04:17:24 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1707487,2017-08-02 08:12:37 UTC,Thank you for replying.
1707487,2017-08-02 02:12:53 UTC,"David, we have done a lot of work improving Bluetooth audio support recently. But most of the work only exists in Ubuntu 17.10 right now. Please also try booting up a live image of 17.10 (no need to install it) and see if that solves your problem:
  http://cdimage.ubuntu.com/daily-live/current/"
1707487,2017-08-01 17:48:22 UTC,"I have already tried that. When I go into the sound GUI options (by clicking on the speaker icon in the top-right, then ""Sound Settings...""), the option for ""Hi fidelity"" is there, but often times it does not let me choose it. Sometimes it will let me choose it then instantly jump back to ""mono""."
1707487,2017-08-01 01:49:53 UTC,"David, have you tried setting the speaker mode to A2DP in sound settings? If it defaulted to headset mode then it might indeed be in low quality mono mode. Make sure the correct mode is set in your sound settings."
1707487,2017-07-31 09:45:42 UTC,"I need to report a SIMILAR bug, which affects the same GUI for the audio. Bear with me."
1707487,2017-07-31 09:17:20 UTC,apport information
1707487,2017-07-31 09:54:32 UTC,I have reported a similar bug that affects the same audio GUI: bug number 1707611
1707487,2017-07-31 09:17:18 UTC,apport information
1707487,2017-07-31 01:34:39 UTC,"Also, please run this to give us more information automatically:
   apport-collect 1707487"
1707487,2017-07-31 08:54:55 UTC,Open a terminal window (Ctrl+Alt+T) and then run:
1707487,2017-07-31 09:11:03 UTC,"Thanks. I tried it, got this:"
1707487,2017-07-31 09:17:14 UTC,apport information
1707487,2017-07-31 08:39:09 UTC,"Who do I run ""apport-collect 1707487""?"
1707487,2017-07-31 01:33:07 UTC,Bluetooth profile selection and generally all bluetooth audio issues are actually the domain of PulseAudio. Which is surprising at first...
1707487,2017-07-31 09:17:15 UTC,apport information
1707487,2017-07-31 09:17:17 UTC,apport information
1707487,2017-07-31 09:17:14 UTC,apport information
1707487,2017-07-31 09:17:19 UTC,apport information
1707491,2017-07-30 10:58:02 UTC,"StacktraceTop:
 QQmlPropertyCache::resolve (this=this@entry=0x555f6dbf2f50, data=data@entry=0x555f6dbf5580) at qml/qqmlpropertycache.cpp:741
 ensureResolved (p=0x555f6dbf5580, this=0x555f6dbf2f50) at qml/qqmlpropertycache_p.h:505
 QQmlPropertyCache::findProperty (this=0x555f6dbf2f50, it=..., vmemo=<optimized out>, context=<optimized out>) at qml/qqmlpropertycache.cpp:920
 property<QV4::String*> (context=0x555f6dc495e0, object=0x7fa2d42f0fa0 <Units::instance()::units>, key=<synthetic pointer>, this=<optimized out>) at ../../include/QtQml/5.7.1/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:288
 QV4::QObjectWrapper::findProperty (this=this@entry=0x7fa2ccda23e0, engine=engine@entry=0x555f6db34230, qmlContext=qmlContext@entry=0x555f6dc495e0, name=name@entry=0x7fa2ccda23d8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::IgnoreRevision, local=local@entry=0x7ffc03f8c430) at jsruntime/qv4qobjectwrapper.cpp:257"
1707493,2017-07-31 12:48:08 UTC,"Hello
Can you please raise this issue upstream @ https://github.com/robint99/mate-dock-applet/issues and link to your upstream report here?
Also, given the number of memory-related errors you have in your Journal, I'm curious about how much RAM your machine has."
1707493,2017-07-31 15:05:22 UTC,"Etienne,"
1707493,2017-10-25 10:22:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707499,2017-07-30 15:14:18 UTC,Using 'localhost' rather than '127.0.0.1' seems to fix this.
1707502,2017-10-16 21:47:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707504,2018-09-11 22:58:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707509,2017-12-02 11:38:14 UTC,"-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
"
1707509,2017-08-30 07:01:27 UTC,"Is this fixed in r931? I experienced this before on debian sid, but it seems solved on lp:virtualbrick."
1707510,2020-07-03 13:35:23 UTC,Closing as part of bug migration to GitLab
1707510,2017-07-30 15:23:44 UTC,"MSYS2 builds of current trunk - Inkscape 0.92+devel (353fc816d9, 2017-07-29) - with old versions of cairo seem to support the previous observations:
- cairo 1.14.4 behaves like devlibs (no clipping at all)
- cairo 1.15.2 crashes"
1707523,2019-07-03 21:31:12 UTC,"Hello,"
1707542,2018-03-22 07:34:08 UTC,"Hi Sridhar,"
1707548,2017-08-03 18:00:11 UTC,here is what menulibre shows
1707548,2017-08-03 18:08:39 UTC,I took some more pictures if it helps
1707586,2017-08-08 08:35:54 UTC,It seems to be caused by the overlapping with nova datasource.
1707586,2017-08-08 11:32:10 UTC,"The following change solved a similar problem a few months ago:
https://github.com/openstack/vitrage/commit/761e712dd85172e672e1861e2379caeb094263f3"
1707587,2021-01-09 04:17:50 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1707587,2020-11-09 18:29:09 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1707588,2017-08-04 05:25:41 UTC,"Thanks for submitting this. I don't know if this will fit with the project, but I've marked it as Wishlist for now. Will update this if/when it is discussed."
1707611,2019-10-25 16:58:11 UTC,"I tried it on the live session USB 3.0, Ubuntu 19.10 (I checked the disk for defects: no errors found). I still had to manually enable the sound over HDMI for the TV."
1707611,2019-10-22 08:19:23 UTC,I think this is fixed in recent releases. Please confirm or just let the bug expire...
1707611,2019-06-05 19:50:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707611,2017-10-02 04:17:26 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1707611,2017-08-02 12:24:50 UTC,"I used a ""live"" version of 17.10"
1707611,2017-08-02 08:16:37 UTC,"I tried the image of 17.10 (checked its sha256sum after download, it matched) and tested the 17.10 live USB using ""test disc for defects"" and no errors found."
1707611,2017-08-02 08:28:03 UTC,"The output is selected on ""connection"". So maybe try not plugging in HDMI until after you have logged in."
1707611,2017-08-02 02:17:10 UTC,"The fix only exists in Ubuntu 17.10 right now. Since it's a ""feature"" more than a bugfix (according to PulseAudio developers) it might not get backported to 16.04 at all."
1707611,2017-08-01 17:43:41 UTC,"I have all the updates installed, but still the same problem. Is the fix downloaded separately?"
1707611,2017-08-01 01:45:14 UTC,Oh I forgot; according to bug 1707487 you are using Ubuntu 16.04. So you are missing the fix for bug 1702794. And this becomes a duplicate of bug 1702794.
1707611,2017-08-01 01:41:40 UTC,Please run:
1707611,2017-08-02 12:00:49 UTC,"I am now also reminded of this ""feature"", which was a patch in 16.04 and seems to be an upstreamed feature in 17.10:"
1707611,2017-08-01 17:45:19 UTC,"Tried running apport-collect 1707611, then got this message:"
1707620,2017-08-15 06:58:38 UTC,We are busy looking into the issue.
1707620,2017-08-21 12:32:02 UTC,"ns-agilio-vrouter does not support QOS,"
1707623,2017-07-31 11:18:58 UTC,Should we enable it by default?
1707623,2017-08-01 23:18:06 UTC,We disable DNS in the amphora by design.  Having DNS enabled increases the time required to boot the amphora as well as other operations of the load balancer.
1707623,2017-08-01 23:19:22 UTC,Can you check if that line is in your no-resolvconf element?
1707623,2017-08-02 04:01:31 UTC,"Newton dose not have that line to disable dns in nsswitch.conf
hosts:          files"
1707623,2017-08-04 06:44:41 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/490758"
1707623,2017-10-09 15:07:29 UTC,"Change abandoned by Michael Johnson (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/490758
Reason: Abandoning.  Newton is going EOL."
1707623,2017-07-31 11:15:10 UTC,I found this configuration will disable dhcp to get dns nameservers.
1707626,2017-09-06 23:29:44 UTC,Reports have been moved. New link is http://ci.jujucharms.com/job/github-check-merge-juju/1868/artifact/artifacts/xenial.log
1707626,2017-09-07 02:53:25 UTC,it would appear that there is something wrong with starting the apiserver
1707626,2019-07-09 01:36:20 UTC,"This failure has been fixed.
I have run both
github.com/juju/juju/worker/introspection/introspectionSuite.TestPrometheusMetrics and
github.com/juju/juju/featuretests/introspectionSuite.TestPrometheusMetrics
locally under stress and neither have failed."
1707638,2017-07-31 18:57:31 UTC,"thanks, crash confirmed on Windows 10, Inkscape 0.92.2pre0 (973e216, 2017-07-25)"
1707638,2017-07-31 15:00:27 UTC,could you attach the svg file that caused the original crash?
1707638,2017-07-31 13:55:43 UTC,YW!
1707638,2017-07-31 12:51:14 UTC,Thanks for the report!
1707638,2017-07-31 17:47:39 UTC,Attached the subject file. As I saved over it again it is not in the similar condition when it crashed.
1707641,2017-07-31 13:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1707641,2017-07-31 13:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1707641,2017-07-31 15:11:48 UTC,Do you mean there's no such issue on 4.10? There's no change on sm750fb between 4.10 and 4.11 though...
1707641,2017-07-31 17:54:58 UTC,"Yes, exactly. There is no issue with Kernel 4.10 (16.04 HWE or 17.04). Current 17.10 Kernel does not boot properly. Unfortunately there are no logs, even on persistent journald. The OS freezes after switching from initramfs to real rootfs."
1707641,2017-08-01 03:01:53 UTC,"Maybe some config changed when v4.10 -> v4.11?
Can you provide the kernel config from the fedora server with linux 4.11?"
1707641,2017-08-01 05:31:04 UTC,I have attached the dmesg log from the booted Fedora and the Kernel config as requested:
1707641,2017-08-01 05:57:49 UTC,"Fedora does not have module sm750fb:
# CONFIG_FB_SM750 is not set"
1707641,2017-08-01 06:55:42 UTC,I have sent a message to the mailing list.
1707641,2017-08-01 07:28:12 UTC,Just attach the http link should be sufficient.
1707641,2017-08-01 07:44:20 UTC,http://marc.info/?l=linux-fbdev&m=150157026614752&w=2
1707642,2018-03-12 23:32:35 UTC,So scratch my earlier workaround or patching. After reading what /etc/init/gnocchi-api.conf is doing around lines 31 to 36 I found I can modify startup behavior by creating `/etc/defaults/gnocchi-api` and adding the following contents
1707642,2018-03-12 14:41:15 UTC,My team has a suspicion adding uwsgi package is causing a problem with openstack-dashboard. I am looking to patch the init script that calls the original gnocchi-api to call the correct arguments this week and will post it here.
1707642,2018-03-28 13:56:34 UTC,It seems that the latest version (4.2.0) does not have the gnocchi-api service unit installed.
1707642,2018-03-06 22:34:32 UTC,To add a little more of the back story:
1707642,2017-09-05 04:01:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707642,2018-03-06 23:13:23 UTC,as a work-around I did the following:
1707642,2017-09-04 05:42:05 UTC,I am having the same problem:
1707645,2018-10-26 10:10:22 UTC,"Someone needs to take on all the affected systems, PAM, users etc to find a fix."
1707645,2017-09-21 19:42:49 UTC,I don't see what we can be expected to do with this bug report.  This is the defined file format for /var/log/lastlog.
1707645,2018-10-26 10:05:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707645,2017-07-31 15:48:26 UTC,"FYI, people using rsync for backups might be interested in the --sparse (-S) option."
1707655,2017-12-08 14:44:07 UTC,I pined the #docs-team on irc about this.
1707656,2019-08-21 09:18:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707656,2019-08-21 09:52:28 UTC,"17.04 reached end of life about a year ago, and 18.04 certainly works fine, so closing this bug."
1707667,2018-05-17 05:56:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707667,2018-06-04 19:13:38 UTC,Please provide a backtrace of the segmentation fault. See https://wiki.ubuntu.com/Backtrace and https://wiki.ubuntu.com/DebuggingGNOME - thanks!
1707668,2017-07-31 16:04:14 UTC,Here it is: http://git.evergreen-ils.org/?p=working/NCIPServer.git;a=shortlog;h=refs/heads/user/jboyer/lp1707668_renewitem
1707668,2017-11-15 15:39:27 UTC,"Pushed to master. Thanks, Jason!"
1707669,2017-07-31 16:32:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489273"
1707669,2017-08-02 17:35:03 UTC,"Reviewed:  https://review.openstack.org/489273
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=afab0ca0c8f4c68b8d6d8646f408e9522596870e
Submitter: Jenkins
Branch:    master"
1707669,2017-08-02 22:11:44 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/490231"
1707669,2017-08-11 23:23:47 UTC,"Reviewed:  https://review.openstack.org/490231
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9f4db205bbbb215e77741df22979a20d62d80ae8
Submitter: Jenkins
Branch:    stable/ocata"
1707676,2017-08-08 08:52:39 UTC,"Looks like a Windows bug, so please ignore."
1707676,2017-08-02 17:22:24 UTC,"To add to my own bug report, the issue might be only indirectly related to Zim."
1707685,2017-08-01 11:40:26 UTC,"Reviewed:  https://review.openstack.org/489565
Committed: https://git.openstack.org/cgit/openstack/charms.openstack/commit/?id=698337c5eed531d942dc75791248ad8e2ca6bf45
Submitter: Jenkins
Branch:    master"
1707685,2017-08-02 17:46:03 UTC,"The fix committed in charms.openstack means that no changes are required to any of the charms to use the changed defaults.  Therefore, closing all of the bugs as invalid as when they are rebuilt for the next release they will pick up the new versions."
1707685,2017-08-01 11:11:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489565"
1707695,2018-11-14 09:56:16 UTC,"From https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707695 , what would be an workaround until this bug is fixed for Ubuntu 18.10 / kernel 4.18.0-10-generic ?"
1707695,2021-02-12 14:47:35 UTC,Recently I'm also experiencing this on:
1707695,2020-12-13 07:59:52 UTC,No need to throw away those cards.  They are serviceable.
1707695,2020-06-28 21:29:03 UTC,I have the same effects as the description with the following graphics card:
1707695,2020-02-27 23:45:10 UTC,One does not simply close a bug report about a Radeon driver because Christopher went out and got an Nvidia card.
1707695,2019-01-16 08:51:15 UTC,"Resolving per comment 4, thanks for the report and follow-ups."
1707695,2019-01-15 21:38:12 UTC,"(In reply to Pander from comment #3)

> Christopher, are you still experiencing this bug?
"
1707695,2018-11-14 09:47:30 UTC,"I see a lot different workarounds, but all for older versions of Ubuntu. What would be the best workaround for 18.10?"
1707695,2019-01-15 09:25:56 UTC,"Christopher, are you still experiencing this bug?"
1707695,2018-11-14 09:42:46 UTC,"In Ubuntu (Lubuntu) cosmic 18.10 with Linux 4.18.0-10-generic, this bug is worse than before. How can one disable the features causing this? I prefer to have a stable screen without accelleration for now that a machine with GPU problems and multiple freezes per day."
1707695,2018-11-14 09:44:53 UTC,"$  lspci -k | grep -EA2 'VGA|3D'
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hemlock [Radeon HD 5970]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Hemlock [Radeon HD 5970]
        Kernel driver in use: radeon"
1707695,2017-09-19 17:41:00 UTC,The problem reoccurred while running what was the most recent mainline kernel when I downloaded it (v4.13/	2017-09-03 22:30).  The log file is attached.
1707695,2017-09-19 22:14:48 UTC,Please file a bug report at https://bugs.freedesktop.org/
1707695,2017-09-20 20:06:42 UTC,"My system intermittently locks up every few days. It does not seem to correspond to a particular program or action. When that happens, the screen goes to black, then returns after a few seconds. At that point, the time on the clock is static and indicates that the screen is frozen, but audio continues to play for 30 seconds to a minute. The keyboard and mouse do not affect what's being displayed, but I can Alt - SysRq - REISUB to restart."
1707695,2017-08-11 20:55:36 UTC,"Hello there!
I experienced absolutely the same with an older Sapphire Radeon HD5450.
The system is a freshly installed Xubuntu 16.04.3 LTS.
I just installed the xserver-xorg-video-ati-lts-xenial package but this didn't resolv the problem.
Currently the AMD64 4.10.0-30-generic is installed on an older Asus 775 motherboard.
Do we have any other ideas?
I don't think the mainline kernel can solve anything, seems like 4.4 and 4.10 is involved in this case. I think it's more likely a DRM/Mesa/Xorg related bug.
I we can't figure out anything I will jump to the 17.04 version, however I'd like to stay in the LTS version
Thank you"
1707695,2017-12-27 13:18:57 UTC,Happens to me too intermittently Dell PC's with pre-installed Ubuntu 16.04 (I have 6 of them and it will occasionally happen on any of them). I've attached the syslog for one occurence.
1707695,2017-07-31 18:30:07 UTC,This change was made by a bot.
1707695,2018-02-03 20:55:25 UTC,Hello guys!
1707695,2017-09-20 20:09:29 UTC,"kaihengfeng, I posted at fredesktop.org as you suggested.  Thanks!"
1707695,2017-08-10 17:44:40 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1707717,2017-07-31 20:35:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707717,2018-06-07 17:48:00 UTC,"assigning to desktop team, if it's wanted in main."
1707743,2017-07-31 21:21:01 UTC,"@Seth, the first test cases use 'aa-exec -p test' and therefore didn't need anything else. I omitted the binary attachment profile since it simply changes this:"
1707743,2017-07-31 21:36:03 UTC,"AppArmor has a small deduplication LRU cache in its capability audit logging. Its pretty basic just using a profile capability pair, which will prevent further logging of capability requests for the profile capability pair in question while the entry remains in the cache."
1707743,2017-08-01 15:55:06 UTC,"Thanks John, that sounds wonderful."
1707743,2017-07-31 20:49:40 UTC,The profile given here doesn't have an attachment specification:
1707783,2019-02-19 13:43:09 UTC,Is this still an issue?
1707783,2019-12-18 08:33:05 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1707785,2019-03-28 10:37:05 UTC,"Dan, is this still a bug? If yes - please update."
1707786,2017-07-31 22:25:41 UTC,"StacktraceTop:
 ?? ()
 brisk_menu_window_filter_apps ()
 gtk_list_box_apply_filter () from /tmp/apport_sandbox_bKEEsR/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_list_box_insert () from /tmp/apport_sandbox_bKEEsR/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_cclosure_marshal_VOID__OBJECTv () from /tmp/apport_sandbox_bKEEsR/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"
1707786,2017-10-19 12:32:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707788,2017-07-31 23:54:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/489434"
1707788,2017-07-31 22:22:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/489423"
1707788,2017-10-27 16:05:05 UTC,This issue was fixed in the openstack/python-tripleoclient 8.0.0 release.
1707788,2017-09-10 14:51:25 UTC,This issue was fixed in the openstack/python-tripleoclient 7.3.0 release.
1707788,2017-09-04 18:16:36 UTC,This issue was fixed in the openstack/python-tripleoclient 5.4.3 release.
1707788,2017-08-04 01:58:41 UTC,"Reviewed:  https://review.openstack.org/490646
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=ac73d7efda693c1ee1afa6c050d221fecec77af5
Submitter: Jenkins
Branch:    stable/newton"
1707788,2017-08-03 23:43:02 UTC,"Reviewed:  https://review.openstack.org/490645
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=8dbebd4e79c04878abf432d90285d3ba1fcc44e6
Submitter: Jenkins
Branch:    stable/ocata"
1707788,2017-09-05 16:10:03 UTC,This issue was fixed in the openstack/python-tripleoclient 6.2.1 release.
1707788,2017-08-03 20:47:32 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/490646"
1707788,2017-08-03 20:47:14 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/490645"
1707788,2017-08-03 14:53:24 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/490504"
1707788,2017-08-03 14:21:02 UTC,"Reviewed:  https://review.openstack.org/490265
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=1b6585494f925ac64aba14ea362f1d58673ae291
Submitter: Jenkins
Branch:    master"
1707788,2017-08-03 01:14:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490265"
1707788,2017-08-01 21:03:00 UTC,"Reviewed:  https://review.openstack.org/489434
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=818b75af41b99b7573d3d9da132c7b866a2ac2a1
Submitter: Jenkins
Branch:    master"
1707788,2017-08-01 01:38:25 UTC,"Change abandoned by Steve Baker (<email address hidden>) on branch: master
Review: https://review.openstack.org/489423
Reason: Idd4ae71ee6deee84604823b6b5dc4a845f316e01 looks like a better fix"
1707788,2017-08-03 21:52:22 UTC,"Reviewed:  https://review.openstack.org/490504
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=70103905c43f9dfa3e56c21311423ff6ee69e861
Submitter: Jenkins
Branch:    stable/pike"
1707793,2017-08-01 00:11:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489436"
1707793,2017-08-01 06:59:53 UTC,"Change abandoned by Martin Lopes (<email address hidden>) on branch: master
Review: https://review.openstack.org/489436
Reason: Reviewing options for now."
1707795,2017-11-23 10:10:14 UTC,"Hi @feng-shengqin,"
1707795,2017-11-24 12:03:56 UTC,Already CLI options are there in ZUN/OSC cli.
1707808,2017-08-01 00:19:24 UTC,"As a workaround the (workaround button?) ""?"" can be clicked to unset the line-height attribute of the children again."
1707808,2017-08-01 00:33:06 UTC,Likely related: bug #1677490
1707808,2017-09-30 23:58:13 UTC,Likely related: bug #1718617
1707810,2017-08-02 03:25:14 UTC,The post mentioned it was fixed here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751271
1707810,2017-09-21 09:53:40 UTC,"I've backported usb-modeswitch 2.4 and usb-modeswich-data 2017-01 from Ubuntu 17.04 (Zesty) to 16.04 LTS (Xenial), you can update packages from ppa:baltix-members , see
https://launchpad.net/~baltix-members/+archive"
1707810,2017-08-01 02:45:05 UTC,"$ dpkg -S /lib/udev/rules.d/40-usb_modeswitch.rules
usb-modeswitch-data: /lib/udev/rules.d/40-usb_modeswitch.rules"
1707810,2017-08-01 01:15:18 UTC,"Just to be clear, I commented the ""catch all"" line:"
1707810,2017-08-01 17:46:32 UTC,Strange as this sounds I went to try the solution above on a different computer with the same Ubuntu version (16.04) and didn't work - device appeared as mass storage. The line that worked was this one:
1707810,2017-08-01 01:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1707811,2018-01-20 08:02:34 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1462
1707811,2018-06-12 11:30:02 UTC,"Hi, Is there any update on this issue?"
1707811,2017-08-02 08:45:40 UTC,"I did not understand your point about master/slave switch.
This time I took backup with 2.3.9 on PS 5.6 master server with --history option:"
1707811,2017-08-02 06:51:10 UTC,"can you test  when master/slave Switching occurs，and i found when SELECT @@global.gtid_executed; have not only one record like ：
SELECT @@global.gtid_executed;
+---------------------------------------------------------------------------------------------------+

| @@global.gtid_executed                                                                            |


+---------------------------------------------------------------------------------------------------+

| 12361081-90f4-11e6-8413-0050569293fc:1-286495163,


59eaee0c-9289-11e5-8911-005056923a57:1-40235250 |
+---------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)"
1707811,2017-08-02 15:01:55 UTC,"thank you for support me. I means is if ""SELECT @@global.gtid_executed;"" have not only one values,it like this have the other server_uuid after switch,it can not insert the records with --history
SELECT @@global.gtid_executed;
+---------------------------------------------------------------------------------------------------+

| @@global.gtid_executed |


+---------------------------------------------------------------------------------------------------+

| 12361081-90f4-11e6-8413-0050569293fc:1-286495163,


59eaee0c-9289-11e5-8911-005056923a57:1-40235250 |
+---------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)"
1707811,2017-08-01 07:51:45 UTC,"Hi,
What is your xtrabackup version?"
1707817,2017-08-01 02:23:02 UTC,Switching this bug to public since it doesn't describe a security vulnerability.
1707817,2017-08-16 02:26:13 UTC,"https://github.com/openstack/trove/commit/3f93ff110bec754e5a3d955fef2daaed3510aaf4#diff-bc988b82060c9f1fbc749f542592ae2aL332
The patch removed the quota_notification_interval default, it seems that this will not be have error meesage"
1707823,2020-09-20 12:12:20 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1707830,2017-08-01 06:05:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489484"
1707830,2017-08-01 09:43:45 UTC,"Please don't change the bug status to Fix Committed, it will automatically be changed to that once the change lands in Gerrit."
1707830,2018-12-17 08:42:39 UTC,"It's also related bug 1808728.
https://bugs.launchpad.net/nova/+bug/1808728"
1707830,2019-05-30 14:52:51 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/489484
Reason: I'm going to abandon this since it's so old and I'm not getting replies to my questions. I don't think the complaints about xen or ironic drivers are likely valid (you can't migrate / resize baremetal instances anyway), but no one is following up on that assertion. We could discover the virt driver capability using traits if we want to be careful, but that requires some more thought and is a bigger change."
1707832,2018-09-18 17:53:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707832,2017-08-03 23:48:42 UTC,"> The computer still boots successfully!
"
1707832,2017-08-03 20:09:59 UTC,"Hi Steve,"
1707832,2017-08-02 22:41:27 UTC,"Thanks, the trace shows:"
1707832,2017-08-03 19:48:09 UTC,"Hi Steve,"
1707832,2017-08-01 22:17:09 UTC,When I try those commands I get error messages (see below).
1707832,2017-08-02 22:06:57 UTC,"Hi Steve,"
1707832,2017-08-01 05:27:26 UTC,The error in your log shows:
1707832,2017-08-02 20:56:56 UTC,"On Tue, Aug 01, 2017 at 10:17:09PM -0000, cristina wrote:

> When I try those commands I get error messages (see below).
"
1707832,2017-08-01 17:06:16 UTC,"Hi Steve,"
1707832,2017-08-01 19:42:30 UTC,"Ok, there's nothing obviously wrong in that output.  Can you please try the following commands:"
1707832,2017-08-01 17:05:12 UTC,"Hi Steve,"
1707834,2017-08-09 13:18:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707835,2017-08-24 14:44:43 UTC,"Great idea!
I vote for that!!"
1707835,2017-09-03 15:01:10 UTC,AFAIU already tracked in earlier bug #789804.
1707835,2018-05-27 11:32:40 UTC,It would be really great if Inkscape came with a few different options of built in icon sets e.g these simple monotone icons https://logosbynick.com/new-icons-for-inkscape/
1707835,2020-09-14 10:26:21 UTC,Closing because INVALID: Fix released (>=1.0).
1707851,2017-08-01 11:09:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1707856,2017-08-04 07:55:08 UTC,"I tried to append ""master_host: YOUR_HOSTNAME"" into /etc/kolla/globals.yml to workaround this problem.
But I 'm not quite sure whether it's the right solution or not."
1707856,2017-09-18 14:00:07 UTC,Also seeing this. The problem is that master_host is set dynamically in bootstrap.yml but this is not executed during genconfig.
1707856,2017-10-11 13:03:41 UTC,Fix release https://review.openstack.org/#/c/506843/
1707856,2017-12-07 14:50:58 UTC,This issue was fixed in the openstack/kolla-ansible 6.0.0.0b2 development milestone.
1707856,2017-12-21 20:56:00 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.1 release.
1707864,2017-08-01 18:14:55 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1707865,2017-08-01 09:43:18 UTC,"I suppose this not really a mesa bug as it occurs with many packages which I try to install,
so I'm changing it to dpkg, since that seems to be where symlinks are checked for size"
1707880,2017-08-03 15:28:50 UTC,"Or as per adam. If the deb-systemd-invoke tracks magic state at install time, and knows which units are brand new, it should do start on those, and retry-start on the known updated units."
1707880,2017-11-29 10:08:30 UTC,This bug was fixed in the package debhelper - 10.10.9ubuntu1
1707884,2017-08-02 08:59:40 UTC,apport information
1707884,2019-09-18 19:24:04 UTC,-- GitLab Migration Automatic Message --
1707884,2018-11-28 21:08:38 UTC,"no reply, closing"
1707884,2018-10-04 08:59:59 UTC,is this still an issue with 18.04 or newer?
1707884,2017-08-30 15:01:39 UTC,"(In reply to Ilia Mirkin from comment #20)

> does EXA support DRI3?
"
1707884,2017-08-30 14:55:07 UTC,"One quick drive-by observation... does EXA support DRI3? If not, does disabling DRI3 with glamor ""fix"" things?"
1707884,2017-08-30 14:33:47 UTC,"Created attachment 133881
Xorg log after Option ""AccelMethod"" ""glamor"""
1707884,2017-08-30 13:47:04 UTC,Did you test 7.7.0 with
1707884,2017-08-30 12:43:21 UTC,"OK, I have made a mistake and tested some combinations."
1707884,2017-08-30 01:54:37 UTC,"Does the bug summary change mean you've confirmed that the problem doesn't happen with an older version of Mesa? If so, which version?"
1707884,2017-08-07 17:50:38 UTC,Thanks Michel. Should I open a new bug about the window resizing issue?
1707884,2017-08-07 07:34:44 UTC,"Given that there haven't seemed to be any similar reports with GCN hardware, I suspect the tooltip issue is a Mesa r600 driver bug. E.g."
1707884,2017-08-03 09:43:02 UTC,"OK, the driver modesetting brings back the two problems."
1707884,2017-08-02 07:01:27 UTC,install xdiagnose and run 'apport-collect 1707884'
1707884,2017-08-03 09:24:31 UTC,"Ah, you also need to comment out Option ""AccelMethod"" for testing the modesetting driver."
1707884,2017-08-03 09:41:55 UTC,"Created attachment 133225
Xorg log after Driver ""modesetting"" and without Option ""AccelMethod"""
1707884,2017-08-03 08:28:44 UTC,"Created attachment 133224
Xorg log after Driver ""modesetting"""
1707884,2017-08-02 08:59:41 UTC,apport information
1707884,2017-08-02 08:59:43 UTC,apport information
1707884,2017-08-02 08:59:43 UTC,apport information
1707884,2017-08-02 09:09:57 UTC,"oh right, apport doesn't know of the hwe packages.. so just attach /var/log/Xorg.0.log"
1707884,2017-08-02 09:36:10 UTC,"ok, please file this upstream at http://bugs.freedesktop.org xorg;Driver/Radeon"
1707884,2017-08-03 08:42:28 UTC,"The whole desktop is much slower after Driver ""modesetting"". Playing small videos in Totem is slow. Playing big videos crashes the session and brings me back to the login screen. Compiz and Totem together use 100% CPU for switching, moving windows and playing videos."
1707884,2017-08-02 10:14:58 UTC,"Created attachment 133193
Xorg log"
1707884,2017-08-02 10:08:47 UTC,"Created attachment 133192
GTK3 tooltips are corrupted"
1707884,2017-08-02 15:26:42 UTC,I don't have this file /etc/X11/xorg.conf.
1707884,2017-08-02 22:13:50 UTC,"Michel, yes, adding that option fixes the tooltips problem."
1707884,2017-08-02 22:16:44 UTC,"Created attachment 133215
Xorg log after Option ""AccelMethod"" ""EXA"""
1707884,2017-08-02 22:27:49 UTC,"Created attachment 133217
Resizing windows artefacts before Option ""AccelMethod"" ""EXA"""
1707884,2017-08-03 01:07:03 UTC,Please try
1707884,2017-08-03 08:27:25 UTC,"Adding Driver ""modesetting"" made the two problems disappear by making compiz (unity7) go into low graphics mode. Effects and animations are gone. Compiz was using 50% CPU."
1707884,2017-08-02 14:09:14 UTC,Does
1707888,2017-08-01 22:02:47 UTC,"Makes sense I think, although, what is blocking on systemd-networkd-wait-online? I think it's behaviour of waiting on all interfaces is pretty unhelpful, but even given that, an Ubuntu core system shouldn't block for 2 minutes on boot if it is not connected to the internet..."
1707888,2017-08-02 10:04:10 UTC,seems that systemd 229 had a bunch of such issues that were fixed in a later version (bug 1673092 is an example ...) seems some of the network bits got some overhaul in 232.
1707888,2017-10-11 10:46:26 UTC,"@steve ... i'm not sure this is actually a duplicate, if i did never touch the eth0 interface and only configured wlan0 on a device that has two such cards, subiquity will still put a default config in place for the untouched device ..."
1707893,2017-08-02 10:08:47 UTC,"Created attachment 133192
GTK3 tooltips are corrupted"
1707893,2019-09-18 19:24:04 UTC,-- GitLab Migration Automatic Message --
1707893,2017-08-30 15:01:39 UTC,"(In reply to Ilia Mirkin from comment #20)

> does EXA support DRI3?
"
1707893,2017-08-30 14:55:07 UTC,"One quick drive-by observation... does EXA support DRI3? If not, does disabling DRI3 with glamor ""fix"" things?"
1707893,2017-08-30 14:33:47 UTC,"Created attachment 133881
Xorg log after Option ""AccelMethod"" ""glamor"""
1707893,2017-08-30 13:47:04 UTC,Did you test 7.7.0 with
1707893,2017-08-30 12:43:21 UTC,"OK, I have made a mistake and tested some combinations."
1707893,2017-08-30 01:54:37 UTC,"Does the bug summary change mean you've confirmed that the problem doesn't happen with an older version of Mesa? If so, which version?"
1707893,2017-08-07 07:34:44 UTC,"Given that there haven't seemed to be any similar reports with GCN hardware, I suspect the tooltip issue is a Mesa r600 driver bug. E.g."
1707893,2017-08-03 09:43:02 UTC,"OK, the driver modesetting brings back the two problems."
1707893,2017-08-07 17:50:38 UTC,Thanks Michel. Should I open a new bug about the window resizing issue?
1707893,2017-08-03 09:24:31 UTC,"Ah, you also need to comment out Option ""AccelMethod"" for testing the modesetting driver."
1707893,2017-08-02 10:14:58 UTC,"Created attachment 133193
Xorg log"
1707893,2017-08-03 09:41:55 UTC,"Created attachment 133225
Xorg log after Driver ""modesetting"" and without Option ""AccelMethod"""
1707893,2017-08-02 15:26:42 UTC,I don't have this file /etc/X11/xorg.conf.
1707893,2017-08-02 22:13:50 UTC,"Michel, yes, adding that option fixes the tooltips problem."
1707893,2017-08-02 22:16:44 UTC,"Created attachment 133215
Xorg log after Option ""AccelMethod"" ""EXA"""
1707893,2017-08-02 14:09:14 UTC,Does
1707893,2017-08-03 01:07:03 UTC,Please try
1707893,2017-08-03 08:27:25 UTC,"Adding Driver ""modesetting"" made the two problems disappear by making compiz (unity7) go into low graphics mode. Effects and animations are gone. Compiz was using 50% CPU."
1707893,2017-08-03 08:28:44 UTC,"Created attachment 133224
Xorg log after Driver ""modesetting"""
1707893,2017-08-03 08:42:28 UTC,"The whole desktop is much slower after Driver ""modesetting"". Playing small videos in Totem is slow. Playing big videos crashes the session and brings me back to the login screen. Compiz and Totem together use 100% CPU for switching, moving windows and playing videos."
1707893,2017-08-02 22:27:49 UTC,"Created attachment 133217
Resizing windows artefacts before Option ""AccelMethod"" ""EXA"""
1707895,2018-03-12 00:36:42 UTC,"If they wait for another month, they can skip right to 18.04."
1707895,2018-05-31 19:36:03 UTC,I updated title to not specify version and instead just say updated versions.  I think that should be appropriate.
1707899,2017-09-16 21:33:05 UTC,Please consider backport 0.92.3. Commit to master on d0930c9b
1707899,2017-08-14 09:08:04 UTC,"You are welcome Glenn. I hope Brynn can help us. And maybe can be on 0.92.3.
Cheers, Jabier"
1707899,2017-08-13 19:18:20 UTC,"Not sure if the last email was directed to me or if I was simply CC'd on it... In any event I am an infrequent user of Inkscape and only use the stable versions rather than the in-progress builds. Hopefully Brynn can help you out. Thanks for looking into it, anyway.
Regards,
 Glenn Slingsby
Website/Blog
Instagram
 CustomMade"
1707899,2017-08-13 15:19:11 UTC,"Hi, could we try lastest branch to know if fixed?
I also add to retain last width stroke used."
1707899,2017-08-10 09:19:20 UTC,"Hi!
On Thu, 2017-08-10 at 02:48 +0000, Brynn wrote:"
1707899,2017-08-08 20:48:43 UTC,"Hi Bryn, finaly I find the problem by myself but lately Im too bussy to
reply."
1707899,2017-08-06 05:36:55 UTC,"Hi Jabier,
Pen tool with shapes maybe is stroke and no fill technically.  But the style indicator (bottom-left corner of window) shows it has fill and no stroke."
1707899,2017-08-01 23:04:06 UTC,"I can reproduce this on Windows 7 Pro, 64-bit, Inkscape 0.92.1, 64-bit, exe installer."
1707899,2017-08-02 00:23:03 UTC,"Ok, I get a different behavior with 0.92.2pre0.  But I'm not sure if I would call it fixed.  I'm not really sure how it's supposed to behave."
1707899,2017-08-10 02:48:53 UTC,Thanks Jabier.
1707899,2017-08-05 14:26:51 UTC,Hi Brynn!
1707899,2017-08-05 14:33:10 UTC,Hi Brynn.
1707906,2017-08-16 23:40:19 UTC,"Since there is not much activity regarding this bug, it could easily be solved by simply replacing this package by the one distributed on launchpad (https://launchpad.net/~ok2cqr/+archive/ubuntu/ppa/+sourcepub/8146390/+listing-archive-extra)
:-)
Thanks again,"
1707906,2017-08-16 23:51:09 UTC,"Package Info from launchpad:
 Package: cqrlog
 Version: 2.1.0-1~xenial
 Architecture: amd64
 Maintainer: Debian Hamradio Maintainers <email address hidden>
 Installed-Size: 28418
 Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.2.5), libcairo2 (>= 1.2.4), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.12.0), libgtk2.0-0 (>= 2.24.0), libpango-1.0-0 (>= 1.14.0), libx11-6, libssl-dev, mariadb-server | mysql-server, mariadb-client | mysql-client, libhamlib2 (>= 1.2.10), libhamlib-utils (>= 1.2.10)
 Section: hamradio
 Priority: extra
 Homepage: http://www.cqrlog.com
 Description: Advanced logging program for hamradio operators
  CQRLOG is an advanced ham radio logger based on MySQL embedded database.
  Provides radio control based on hamlib libraries (currently support of 140+
  radio types and models), DX cluster connection, HamQTH/QRZ callbook
  (XML access), a grayliner, internal QSL manager database support and a most
  accurate country resolution algorithm based on country tables developed by
  OK1RR. CQRLOG is intended for daily general logging of HF, CW & SSB contacts
  and strongly focused on easy operation and maintenance."
1707906,2017-08-16 23:55:04 UTC,*** This is an automated message ***
1707906,2017-08-17 18:50:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707906,2017-08-17 18:50:51 UTC,"I can confirm this. Get the same error. After start of cqrlog there is a messagebox:
""Error during connection to database: TMySQL56Connection can not work with the installed MySQL client version: Expected (5.6), got (5.7.19)."""
1707908,2017-08-10 10:16:01 UTC,See also bug 1707890 (LP bug that contributed to the strange behaviour)
1707908,2018-01-02 15:09:08 UTC,I filed a bug upstream about this: https://savannah.gnu.org/bugs/index.php?52788
1707910,2017-08-04 06:19:44 UTC,"Agreed, this was an oversight."
1707917,2017-10-07 22:02:47 UTC,"Thanks to Johannes Benoit, here is the patch file to fix the bug."
1707919,2020-04-11 15:43:56 UTC,"Hi - thanks for reporting this bug, I've manually migrated it (including your patch) to Inkscape's new bug tracker on GitLab, and closed it here."
1707919,2017-08-01 20:48:54 UTC,"Hi Antonio
On Tue, 2017-08-01 at 14:07 +0000, Antonio Ospite wrote:

> Public bug reported:
>
> Hi,
>
> the newly added center control points of shapes currently have a
> fixed
> stroke color of 0x010000000, the main problem with this is that the
> control points become invisible on black backgrounds.
>
> The fill and stroke colors for shape control points are hardcoded in
> SPKnot::SPKnot(), and for the other control points the default values
> work fine, for the NORMAL status they are:
>
>   fill_color   = 0xffffff00
>   stroke_color = 0x01000000
>
> That is white fill with a basically black stroke.
>
> AFAICS when the alpha channel is 0 Inkscape does not apply the XOR
> operator but uses the color as is  (see
> src/display/sodipodi-ctrl.cpp::sp_ctrl_render()) however the
> combination
> from above still works fine on every background even without the XOR
> compositing because of the heavy contrast between the stroke and the
> fill color.
>
> The problem with the center control points is that they are only
> drawn
> with the stroke color, so XOR blending is actually needed for them.
>
> An hackish solution would be to call SPKnot::setStroke() for any
> entity_center->knot objects, like in the attached patch.
>
> However this is not very elegant IMHO.
>
> A better alternative would be to be able to pass a _set_ of colors
> for
> the different states to KnotHolderEntity::create() which currently
> only
> accepts a fill_color, but that would need some refactoring and I'd
> like
> advice from developers more familiar with the Inkscape codebase than
> I am.
>
> Inkscape has different ways of specifying the control points color
> depending on the state (normal, mouseover, dragging, selected).
>
> guint32 arrays in src/seltrans-handles:
>
>   guint32 const DEF_COLOR[] = { 0xff, 0xff6600, 0xff6600, 0xff, 0xff,
> 0xff };
>   guint32 const CEN_COLOR[] = { 0x0, 0x0, 0x0, 0xff, 0xff0000b0,
> 0xff0000b0 };
>
"
1707919,2017-08-01 14:13:52 UTC,"Updated the attachment, the old one contained an unrelated change."
1707919,2017-08-02 15:11:09 UTC,">> Ideally I would like to be able to pass a ColorSet to
>> KnotHolderEntity::create(), and possibly even to SPKnot::setFill()
>> SPKnot::setStoke().
>>
>> Any advice about what the best place to move the ColorSet definition
>> would be?
>>
>  to me is better create a similar structure than color set in
>  knot.cpp/h because ControlPoint is a particular type of knot focus on
>  node editing. As far I undertand dev on control/selected points need
>  different aproach than other knot staff, so feel free to create
>  a structure on knot.cpp/h to pass to create and change the create
>  fill by a setFill, setStroke from the new create argument/s
"
1707922,2017-08-01 14:18:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707925,2018-05-11 15:33:23 UTC,This change was made by a bot.
1707925,2021-01-07 04:07:48 UTC,4.8 EOL
1707936,2017-08-01 14:57:29 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/489630"
1707936,2017-08-01 15:09:40 UTC,rbd.Image().diff_iterate() will take a look of all objects of all volumes on all Ceph OSDs.
1707936,2017-08-01 15:17:56 UTC,Also the experience to debug the issue is terrible. Nothing appears in logs during the volume_stats update.
1707936,2017-08-01 20:37:02 UTC,v.diff_iterate without fast-diff and object-map feature is really slow because it have to dig into all rados objects to get the information.
1707936,2017-08-04 08:25:06 UTC,"After looking into the matter of the stats I've realized that the RBD stats are wrong, and we shouldn't be returning physical used space in the first place as I explain in the improve provisioning spec [1]."
1707936,2017-09-05 19:41:01 UTC,"Change abandoned by Mehdi Abaakouk (sileht) (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/489630
Reason: better solution: https://review.openstack.org/#/c/486734/"
1707936,2017-09-05 19:41:06 UTC,"Change abandoned by Mehdi Abaakouk (sileht) (<email address hidden>) on branch: master
Review: https://review.openstack.org/489718
Reason: better solution: https://review.openstack.org/#/c/486734/"
1707936,2017-12-31 18:04:10 UTC,"I'd like to follow up on this issue, with the new changes, it gets better, but it is still problematic."
1707936,2018-04-02 09:16:00 UTC,"with this patch, this issue should be fixed. https://review.openstack.org/#/q/I78e552998e822fff37fb2c7cf890ebab65d9291f"
1707936,2017-08-01 14:57:12 UTC,The rbd pool have only ~ 200 volumes.
1707936,2017-08-01 19:25:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489718"
1707945,2017-08-01 15:46:03 UTC,The undocumented location is implemented in the file pkcs11/gkm/gkm-util.c
1707960,2018-07-26 08:57:43 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.0 release.
1707960,2018-04-02 22:19:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558315"
1707961,2017-11-18 17:18:09 UTC,"Yes, it should be fairly easy to implement at this point. Implementing it for the whole EffectRack wouldn't be very useful though. I imagine making a new QComboBox subclass like WEffectSelector that would be at the top of each EffectUnit in the skins to select among saved chains. This would make it easy to quickly recall saved setups during a set."
1707961,2017-11-18 17:41:57 UTC,"I think it's useful for the rack, as well.
Just had someone screwing up my FX settings, wished I could have just reloaded th whole rack to reset to my defaults.
And if it's really that simple as it looks, this feature could make it into 2.1 beta, couldn't it?"
1707961,2017-11-18 17:50:17 UTC,"While this feature would be relatively easy, I'm sure there will be quite a bit of work to refine the UI & UX and carefully think through the technical details. AFAIK no one has started it yet. I don't want to rush it for 2.1."
1707961,2017-11-21 14:02:25 UTC,"Yes, restoring a previously saved FX setup would be sufficient.
How can we implement this? Wouldn't it require UX changes anyway? Like a button in skin menu or in Effect Preferences?"
1707961,2017-12-16 21:17:43 UTC,"In implementing post fader effects, I realized this actually won't be very easy to implement because there are major architectural issues with the main thread side of the effects system that should be taken care of before implementing this. Here is a brief outline of my thoughts at the moment. I'm only putting these here so I don't forget them. I will not discuss these until after 2.1 beta is released:"
1707961,2017-12-16 21:31:56 UTC,"Here my comments, original from https://github.com/mixxxdj/mixxx/pull/1254#issuecomment-352209090"
1707961,2017-12-28 23:28:02 UTC,it will also be nice to have a section on forums to allow users to share custom effect chains.
1707961,2017-12-30 01:09:15 UTC,"My end goal is to be able to have intuitive control of complex effect chain setups like depicted in this video:
https://www.youtube.com/watch?v=m0_Ku9PChlw
but without coupling the effect chains to the controller mapping like Traktor requires. This will let all users benefit from chains shared on the forums, not just users with a particular controller."
1707961,2017-12-30 01:12:22 UTC,"In the future, when we have controller mapping preferences (Bug #1470278), we may consider implementing an API that lets controller mappings load a particular effect chain preset and let the user select which of their chain presets the controller will load in the mapping preferences."
1707961,2018-02-16 05:28:17 UTC,"I may get started on the preliminary refactoring for 2.2, but I don't think I'll have enough time to complete this for 2.2."
1707961,2018-03-08 23:29:30 UTC,I'm unassigning myself from this in case a GSOC student wants to make it their project this year.
1707961,2017-11-18 16:52:26 UTC,"At least implementing this for the whole EffectRack should be easy now that effects are stored in an xml?
Save/Load mechanism of samplers could be re-used, no?"
1707964,2017-11-09 16:13:05 UTC,"I can confirm this, and it even wouldn't let me save once I had selected blanket order so it went a step further. But I'm not sure why we would want this to happen? Blanket orders should originate on POs since we want them to encumber a set amount of funds to be invoiced later, potentially over multiple invoices. So a blanket order shouldn't originate on an invoice at all, I would think."
1707970,2018-04-05 14:24:28 UTC,This is fixed in artful and bionic.
1707970,2020-04-22 19:02:56 UTC,"Xenial is still in LTS maintenance support until 2021, however given that the fix has not been isolated to a patch and that the importance of the bug is Low, I don't think a SRU to Xenial is justified at this point."
1707977,2017-08-01 18:02:10 UTC,"Oh joy, a bug in the work-around (and no way to edit the post).
Please add ""-a"" to the egrep command line to avoid a warning due to the nul terminator in cmdline."
1707977,2017-08-01 17:53:05 UTC,"I hope this bug will be fixed before the next release.  But meanwhile, here is a nasty workaround which can be used in bash startup scripts:"
1707977,2018-10-04 13:38:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1707982,2017-08-01 18:40:46 UTC,"Hari, Please see my email about this. This was an issue that came up during windows port."
1707991,2018-09-20 18:08:16 UTC,"Due to lack of progress, marking Triaged and clearing assignee. Feel
free to revert if it is in fact still in progress :)."
1707991,2017-12-21 03:28:09 UTC,Lazy loading singletons: https://github.com/mixxxdj/mixxx/pull/1426
1707991,2017-12-18 16:46:30 UTC,I think we need a conditional widgets. That are only instance instead of a connected co has a certain value.
1707991,2017-12-18 07:29:25 UTC,It might be a good idea to restrict the number of samplers in the engine in PlayerManager::addSampler to respect the preference option. That would limit RAM wasted by unused samplers.
1707991,2017-12-18 07:27:45 UTC,Adding a combobox to the preferences would be easy. But how would skins make use of it to load a different template depending on the preference?
1707991,2017-12-18 07:07:16 UTC,I am pro a persistent preferences option in the view menu. This is are just a view lines and can be done before beta. Defaulting to 8 sounds reasonable. What do you think?
1707991,2017-12-18 02:01:58 UTC,"It's working fine.
Though, this is only a workaround, no matter if it's an option in preferences or a duplicate skin, so I won't assign this bug to me."
1707991,2017-12-18 01:21:01 UTC,"> Hmm, that gives me an idea. We could make a new preference option to select the number of samplers and have the skin load a different template depending on the preference option.
"
1707991,2017-12-18 01:16:22 UTC,"> My concern with duplicating skins is that every little change would have to be made to both copies of the skin, which would be a big hassle.
"
1707991,2017-12-18 00:58:30 UTC,"This issue is annoying, but IMO it is not such a big deal that it needs to be rushed for the beta release. We can take care of it during the beta period."
1707991,2017-12-18 00:26:00 UTC,"Cool, feels like we have a compromise!"
1707991,2017-12-15 21:45:12 UTC,"I have thought about the duplicate skins solution. It is ugly, but it may be the best option for now..."
1707991,2017-12-18 00:57:48 UTC,"My concern with duplicating skins is that every little change would have to be made to both copies of the skin, which would be a big hassle."
1707991,2017-12-14 17:44:08 UTC,"For now I vote for limiting the number of samplers.
On my machine (quadcore @1.8GHz) it now takes around 30 seconds to shutdown when I enable all 64 samplers in Tango..."
1707991,2017-12-14 20:06:22 UTC,"Duplicating the skins will work for me. We but we should only duplicate the a single skin file.
Thinking about it, redirecting to a different skin folder is probably the same work than a preferences option  .... what do you think."
1707991,2017-08-02 11:43:25 UTC,"Aren't collapsed regions parsed anyway?
I am afraid we can only slice this by introducing a michanism that allows to skip skin regions by a preferences option or something. An other idea is to allow to duplicate an ready initialised widget in memory. Mmm .. all a lot of work."
1707991,2017-08-03 00:58:41 UTC,"> Aren't collapsed regions parsed anyway?
"
1707991,2017-08-03 17:54:35 UTC,What do you mean by *much faster*?
1707991,2017-08-03 18:39:52 UTC,"> What do you mean by *much faster*?
"
1707991,2017-08-03 18:41:00 UTC,"We have a scaling issue with just 8 samplers, so I don't think reducing the number of samplers is a good solution."
1707991,2017-08-06 17:54:22 UTC,"You're right, shutting down & reloading a skin is much faster."
1707991,2017-12-15 21:52:54 UTC,From my perspective I can't imagine using more than 16 samplers and I definitely use the volume knob. Reducing the memory footprint is surely a good thing so duplicating skins might be fine :-)
1707991,2017-11-07 09:03:35 UTC,"A global approach could be to set the number of samplers in the Preferences window (8 being the default?) while skins could define the maximum. Controller mappings could overwrite this value if a controller is built to support more samplers.
I guess this would accelerate loading on slower machines (8 vs. 64 samplers in Tango and Deere)"
1707991,2017-11-07 08:56:49 UTC,"I don't really see which Widgets could be removed from Tango samplers without cutting expected features.
The only element I'm not sure about are the hotcue buttons, though I doubt that significantly improves loading time (didn't find a good way to accurately measure the loading time):
As a workaround for long tracks with where the samplers cue point should be altered in samplers, those tracks could be loaded into decks first, be prepared and the dragged to any sampler deck."
1707991,2017-11-23 18:02:46 UTC,"I did some further testing to determine the scaling issues with the skin widgets versus instantiating so many samplers in the engine. I commented out the setting of [Master],num_samplers in Deere's skin manifest and the sample_decks.xml template, plus deleted my samplers.xml file in my configuration folder. With this setup, Mixxx took about 325 MB resident memory and deleting the skin on shutdown took about 3 seconds. Uncommenting the sample_decks.xml template from the skin kept memory usage the same but increased shutdown time by a whole second. Uncommenting the setting of [Master],num_samplers to 64 in the skin manifest brought memory usage up to 575 MB and shutdown time was the same."
1707991,2017-12-02 23:02:18 UTC,"Hi, in mixxx-2.1.0-alpha-pre-master-git6402-release-x64.exe Deere skin, volume and hotcue buttons are lost."
1707991,2017-11-14 16:41:25 UTC,test was done with Tango btw
1707991,2017-11-14 16:54:13 UTC,"My first thought was the saving the loaded samples to the samplers.xml file could be slowing it down, but I think that would happen even if the sampler skin widgets weren't loaded. Have you tested commenting out the whole sampler section of the skin?"
1707991,2017-11-14 16:38:42 UTC,"I wanted to check if a sampler rework is really worth the effort, so I tested this with my stopwatch.
Via commandline I started just 'mixxx' with all 64 samplers loaded, all have cover art available."
1707992,2017-10-22 15:52:59 UTC,Probably the same issue as https://bugs.launchpad.net/gpxviewer/+bug/1271593 .
1707995,2018-06-25 12:29:31 UTC,Anyone who wants to work on this -- take a look at https://bugs.launchpad.net/python-glanceclient/+bug/1748009 first.  I suspect that that's the place to make the fix.
1707995,2018-06-25 12:26:22 UTC,"Importance ""Low"" because it's only happening when you use the --os-image-url option; workaround is to not use that option."
1708011,2018-01-31 12:01:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708018,2017-08-01 20:55:28 UTC,# yum upgrade percona-toolkit
1708018,2017-08-01 20:58:23 UTC,CentOS release 6.7 (Final)
1708018,2017-08-01 21:07:10 UTC,Install a version of percona-toolkit earlier than 2.2.20
1708018,2018-01-24 22:26:07 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1437
1708046,2017-11-21 16:09:42 UTC,"Jelmer, you reported duplicate bugs:
* Bug #1714718 reported by Jelmer Vernooij on 2017-09-02
* Bug #1708046 reported by Jelmer Vernooij on 2017-08-01"
1708046,2017-11-21 19:51:26 UTC,"Ah, thanks for pointing that out. Clearly I have a bad memory :)"
1708047,2017-08-01 23:27:00 UTC,"StacktraceTop:
 mate_panel_applet_can_freely_move (applet=0x0) at applet.c:1440
 mate_panel_applet_frame_sync_menu_state (frame=0x55e2b474a250) at panel-applet-frame.c:511
 _mate_panel_applet_frame_activated (frame=0x55e2b474a250, frame_act=0x55e2b4449300, error=<optimized out>) at panel-applet-frame.c:619
 mate_panel_applet_frame_dbus_activated (container=<optimized out>, res=<optimized out>, frame=0x55e2b474a250) at panel-applet-frame-dbus.c:410
 g_simple_async_result_complete (simple=0x55e2b448ddf0) at ../../../../gio/gsimpleasyncresult.c:801"
1708047,2017-08-07 07:43:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708049,2020-07-22 10:28:31 UTC,Did the suggestion in comment #2 help?
1708049,2018-07-17 11:35:13 UTC,Can you try:
1708065,2020-05-04 06:05:43 UTC,"Hi, this issue has been reported to Gitlab: https://gitlab.com/inkscape/inbox/-/issues/2626
Closed by: https://gitlab.com/jhofinger"
1708065,2018-08-10 16:39:15 UTC,"Same limit in next version. I use Slackware and install `inkscape-0.92.3-x86_64-1ponce.txz` but then it says `Inkscape 0.92.2 2405546, 2018-03-11` so not really sure which exactly version it is.
BTW, here [1] talks about larger zooms requires double precision. True or not, but 256x (25600%) is far not enough for me. Please fix.
Thanks.
[1] http://inkscape.13.x6.nabble.com/patch-Allow-inkscape-to-zoom-a-wider-range-td2852669.html"
1708069,2017-08-02 03:27:03 UTC,"StacktraceTop:
 XFlush (dpy=dpy@entry=0x557fb5d46400) at ../../src/Flush.c:39
 draw_background (fade=fade@entry=0x557fb60c7b90) at mate-bg-crossfade.c:444
 on_finished (fade=0x557fb60c7b90) at mate-bg-crossfade.c:535
 g_source_callback_unref (cb_data=0x557fb5d9ef40) at ../../../../glib/gmain.c:1566
 g_source_destroy_internal (source=0x557fb5d9fa10, context=0x557fb5d21510, have_lock=1) at ../../../../glib/gmain.c:1255"
1708069,2017-10-05 08:34:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708075,2018-05-20 14:02:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708084,2017-08-02 12:36:35 UTC,I have a also uploaded the api.log file
1708084,2017-08-02 07:45:51 UTC,"Description
   ===========
 I was installing ONAP and attached is the YAML and ENV file for the same, where I got this error."
1708084,2017-08-02 09:54:34 UTC,Could you please paste the nova-api logs showing the full stacktrace ?
1708084,2017-08-02 12:35:15 UTC,"2017-08-01 15:51:06.038 32732 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.
2017-08-01 15:51:06.722 32732 WARNING oslo_config.cfg [-] Option ""use_neutron"" from group ""DEFAULT"" is deprecated for removal.  Its value may be silently ignored in the future.
2017-08-01 15:51:07.338 32732 INFO nova.api.openstack [req-28b8ac08-342a-434c-b747-fb029f00c3b0 - - - - -] Loaded extensions: ['extensions', 'flavors', 'image-metadata', 'image-size', 'images', 'ips', 'limits', 'os-admin-actions', 'os-admin-password', 'os-agents', 'os-aggregates', 'os-assisted-volume-snapshots', 'os-attach-interfaces', 'os-availability-zone', 'os-baremetal-nodes', 'os-block-device-mapping', 'os-cells', 'os-certificates', 'os-cloudpipe', 'os-config-drive', 'os-console-auth-tokens', 'os-console-output', 'os-consoles', 'os-create-backup', 'os-deferred-delete', 'os-evacuate', 'os-extended-availability-zone', 'os-extended-server-attributes', 'os-extended-status', 'os-extended-volumes', 'os-fixed-ips', 'os-flavor-access', 'os-flavor-extra-specs', 'os-flavor-manage', 'os-flavor-rxtx', 'os-floating-ip-dns', 'os-floating-ip-pools', 'os-floating-ips', 'os-floating-ips-bulk', 'os-fping', 'os-hide-server-addresses', 'os-hosts', 'os-hypervisors', 'os-instance-actions', 'os-instance-usage-audit-log', 'os-keypairs', 'os-lock-server', 'os-migrate-server', 'os-migrations', 'os-multinic', 'os-multiple-create', 'os-networks', 'os-networks-associate', 'os-pause-server', 'os-quota-class-sets', 'os-quota-sets', 'os-remote-consoles', 'os-rescue', 'os-scheduler-hints', 'os-security-group-default-rules', 'os-security-groups', 'os-server-diagnostics', 'os-server-external-events', 'os-server-groups', 'os-server-password', 'os-server-tags', 'os-server-usage', 'os-services', 'os-shelve', 'os-simple-tenant-usage', 'os-suspend-server', 'os-tenant-networks', 'os-used-limits', 'os-user-data', 'os-virtual-interfaces', 'os-volumes', 'server-metadata', 'server-migrations', 'servers', 'versions']
2017-08-01 15:51:07.343 32732 WARNING keystonemiddleware.auth_token [req-28b8ac08-342a-434c-b747-fb029f00c3b0 - - - - -] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
2017-08-01 15:51:07.774 32732 INFO nova.api.openstack [req-28b8ac08-342a-434c-b747-fb029f00c3b0 - - - - -] Loaded extensions: ['extensions', 'flavors', 'image-metadata', 'image-size', 'images', 'ips', 'limits', 'os-admin-actions', 'os-admin-password', 'os-agents', 'os-aggregates', 'os-assisted-volume-snapshots', 'os-attach-interfaces', 'os-availability-zone', 'os-baremetal-nodes', 'os-block-device-mapping', 'os-cells', 'os-certificates', 'os-cloudpipe', 'os-config-drive', 'os-console-auth-tokens', 'os-console-output', 'os-consoles', 'os-create-backup', 'os-deferred-delete', 'os-evacuate', 'os-extended-availability-zone', 'os-extended-server-attributes', 'os-extended-status', 'os-extended-volumes', 'os-fixed-ips', 'os-flavor-access', 'os-flavor..."
1708088,2017-11-18 14:55:53 UTC,"Iš aprašyto visai neaišku, kur čia galėtų būti ispell-lt kaltė ar problema. Tuo beprasmiškiau dabar spėlioti apie kokius naujumus eina kalba, jei jau jie patys nesiteikia to paaiškinti.
Kol kas matau situaciją taip: iOS veikiausiai naudoja kažkokį propietary spellcheck'erio formatą, tad native žodynus/kalbas autodetect'as ir atpažįsta, o išorinių (hunspell/myspell) — ne. Gali pabandyti įsidiegti kitų kalbų žodynus ir pabandyti; veikiausiai įsitikinsi, kad ispell-lt čia niekuo dėtas, tad derintis prie neaiškių obuolio naujumų/reikalavimų — ne šio projekto tikslas. Nebent patvirtintum, kad problema būtent su ispell-lt žodynais, o kitų kalbų myspell žodynai veikia."
1708096,2017-11-06 15:23:33 UTC,"As this is an issue with the upstream kernel, we need assistance from upstream to address this issue. Marking as ""incomplete""."
1708096,2017-09-29 03:03:14 UTC,Just to be clear: The above tests were done using ppc64el user-space emulation on x86_64.
1708096,2017-09-29 02:24:50 UTC,I'm able to reproduce the OOPS by booting a Xenial VM with root on JFS:
1708096,2017-09-29 02:04:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708096,2017-08-16 13:20:04 UTC,"Turns out this looks to be the same issue, due to filesystem corruption the disk is unavailable in that Linux image that runs petitboot; so it can't be scanned to find something to boot."
1708096,2017-08-15 21:58:32 UTC,"Testing the same scenarios (X-on-multipath and just-X) where X is ext4 works correctly in all cases. This really looks to be specific to the JFS support somewhere. I'm not sure it's a kernel issue, but it looks like it might be."
1708096,2017-09-29 02:44:29 UTC,Same issue with upstream 4.14.0-rc2:
1708096,2017-08-03 19:19:35 UTC,"------- Comment From <email address hidden> 2017-08-03 15:10 EDT-------
Tried with latest net-boot."
1708096,2017-08-04 00:04:40 UTC,"> The installation completes with no error, but after installation completes
> and reboots there is no disk listed in Petitboot menu.
"
1708096,2017-08-02 07:19:24 UTC,Default Comment by Bridge
1708096,2017-08-02 10:02:04 UTC,Is this a regression from 16.04.2?
1708096,2017-08-15 20:04:41 UTC,"Grub supports JFS to some degree; systems boot on JFS over multipath with relative ease (see below). Using JFS without multipath, it seems to fairly reliably fail to complete the install (so of course you wouldn't manage to boot). In this case it looks as though detection of jfs fails in grub-install."
1708096,2017-08-02 14:34:57 UTC,"On Wed, Aug 02, 2017 at 11:28:42AM -0000, Adam Conrad wrote:

> Also, my attempts to reproduce this with the current (20170801) 16.04.3
> release candidate haven't panned out.  I can install to JFS root just
> fine on ppc64el.
"
1708096,2017-08-02 11:28:42 UTC,"Also, my attempts to reproduce this with the current (20170801) 16.04.3 release candidate haven't panned out.  I can install to JFS root just fine on ppc64el."
1708096,2017-08-03 16:29:46 UTC,"------- Comment From <email address hidden> 2017-08-03 12:23 EDT-------
I tried installing ubuntu 16.04 from below link, and see the same issue."
1708100,2017-08-05 11:52:29 UTC,"confirmed on Windows 10, Inkscape 0.92.1 r15371, using the code:"
1708104,2017-09-25 10:00:29 UTC,Getting this rather regularly by now.
1708111,2017-08-02 08:53:25 UTC,"Is this showing availability zone of nova, neutron, etc one time?
It is difficult to understand."
1708134,2019-09-06 02:35:39 UTC,"See' similar erros (on rocky)
was this solved ?"
1708137,2017-08-07 08:56:44 UTC,Thanks.
1708137,2017-08-07 08:38:23 UTC,apport information
1708137,2017-08-07 08:38:22 UTC,apport information
1708137,2017-08-07 08:38:20 UTC,apport information
1708137,2017-08-07 08:38:19 UTC,apport information
1708137,2017-08-07 08:38:18 UTC,apport information
1708137,2017-08-07 08:38:17 UTC,apport information
1708137,2017-08-07 08:38:16 UTC,apport information
1708137,2017-08-07 08:38:14 UTC,apport information
1708137,2017-08-07 08:38:13 UTC,apport information
1708137,2017-08-07 08:38:09 UTC,apport information
1708137,2017-08-07 08:38:08 UTC,apport information
1708137,2017-08-07 08:38:07 UTC,apport information
1708137,2017-08-07 08:38:05 UTC,apport information
1708137,2017-08-07 08:38:03 UTC,apport information
1708137,2017-08-07 08:38:02 UTC,apport information
1708137,2017-08-07 08:38:00 UTC,apport information
1708137,2017-08-07 03:13:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1708137"
1708137,2017-08-02 10:30:24 UTC,thats the error msg i get when i start my application
1708137,2017-08-07 08:38:11 UTC,apport information
1708137,2017-08-07 08:38:12 UTC,apport information
1708138,2017-08-02 11:06:26 UTC,"Interesting. According to https://en.wikipedia.org/wiki/Processing_Instruction
""""""
An SGML processing instruction is enclosed within <? and >."
1708138,2017-08-02 11:42:36 UTC,The link in the Wikipedia article (http://www.is-thought.co.uk/book/sgml-8.htm#PI) is a 404. But https://www.w3.org/TR/NOTE-sgml-xml seems to indicate that the PI terminators in XML and SGML are indeed different. However this would mean that the _ProcessingInstruction object might have to remember whether it is an XML or an SGML PI?
1708138,2017-08-02 13:02:02 UTC,"> this would mean that the _ProcessingInstruction object might have to remember whether it is an XML or an SGML PI?
"
1708142,2018-06-19 17:44:35 UTC,I observed the same behavior in a new Ubuntu-Server 18.04 install.
1708142,2018-06-19 17:41:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708153,2017-08-02 12:14:42 UTC,"I guess the bug also affects zesty as it's the same tbb version, but not arftul"
1708153,2017-08-02 12:11:02 UTC,it seems to be fixed at least in latest tbb stable of june 2017
1708157,2017-08-02 11:53:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/489994"
1708157,2017-08-14 10:56:55 UTC,"Reviewed:  https://review.openstack.org/489994
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=6a7085fe642d512045777690b35c91cffffbe596
Submitter: Jenkins
Branch:    master"
1708161,2018-04-18 05:15:03 UTC,"I am trying to reproduce this issue but not able to confirm the actual behavior
I have tried using subprocess, please find attached screenshot."
1708165,2017-08-28 12:00:44 UTC,We clarified in the internal Meeting on 2017-09-28 that this is not a use case. Now it's possible to discuss a solution...
1708172,2017-08-02 13:51:44 UTC,"Possibly related old bug, but with a bigger scope maybe: https://bugs.launchpad.net/launchpad/+bug/507319"
1708178,2018-05-29 18:59:56 UTC,"Reviewed:  https://review.openstack.org/480196
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=ba93ad9a2e421ae16ebbb2b7cf895008e9cfeafd
Submitter: Zuul
Branch:    master"
1708178,2017-12-25 17:28:37 UTC,"Reviewed:  https://review.openstack.org/494557
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=395eeabf241bc200fbc91757a412900de650b4d0
Submitter: Zuul
Branch:    master"
1708178,2017-08-23 07:51:16 UTC,"Selective-Proactive is disabled and handled in bug #1712266. Bumped down to medium, but kept so we can verify integration with l3 agent and l3 advanced services work as expected."
1708178,2017-08-03 08:26:08 UTC,"<irenab> oanson, hi
<oanson> irenab, hi
<irenab> oanson, tired of PTO?
<oanson> I can do both. Cooperative threading! :)
<irenab> oanson, once you have few mins, would like to chat about integration with 3rd party LBaaS providers
<irenab> seems to be broken/not supported now when L3agent is disabled
<oanson> Sure. We can do that now
<irenab> dimak, do you have few mins ^^
<irenab> https://bugs.launchpad.net/dragonflow/+bug/1708178
<openstack> Launchpad bug 1708178 in DragonFlow ""LBaaSv2 with 3rd party provider does not work if L3agent is disabled"" [Undecided,New]
<dimak> irenab, yes
<oanson> Yes
<irenab> first, please set the priority for this bug
<dimak> I think we'll need to come up with an lb app that forwards packets bound to VIP port into the relevant compute/namespace
<oanson> The truth is I didn't know we support this feature :)
<oanson> irenab, what priority would you like? High?
<irenab> oanson, it worked before (with l3), this is how kuryr implements k8s services
<irenab> oanson, for kuryr integration its critical
<oanson> l3 agent is still supported. So that can be a workaround until this bug is fixed
<oanson> It can also be gated in the Kuryr-Dragonflow integration gate (which we can add to Dragonflow gate), so it will even be gated
<dimak> dnat acts funny with l3
<irenab> I think now with l3 agent we have some conflicts with DNAT, dimak has much more details
<dimak> because both will plug into br-ex and answer arps
<oanson> I'm not sure I want to say we don't support l3 agent.
<oanson> Is there a way we can get to play nice?
<oanson> Unless we do better on all fronts. Then we can do away with it completely.
<oanson> (And then we might do well to remove it from our code base)
<irenab> oanson, I agree with your approach
<oanson> Do we know if we are feature-compatible?
<irenab> lets keep L3agent enabled deployment possible, since it seems to be enabler for 3rd party services integ for now
<irenab> oanson, if DF supports all l3 extensions, I beleive the answer is yes
<dimak> I'll see if l3+ no dnat app works finne
<dimak> fine*
<irenab> is it possible to disable DNAT on l3agent?
<oanson> Is it possible to support l3 extensions in general, or do we have to support one by one? e.g. a single l3 extensions app, or do we need an app for lbaas, and one for e.g. vpn, etc?
<oanson> (I don't remember the API. Someone will have to look it up if we don't know)
<irenab> lbaas, vpnaas, fwaas are not l3 extensiosn
<irenab> each service is a separate extension set, and may have even separate api server (lbaas) is now octavia and not neutron
<oanson> Then l3 extensions is not enough.
<irenab> but they have proper integration into neutron by creating nets, ports, ets
<irenab> etc
<oanson> Sounds like we need to keep l3 agent support, since new extensions may be written to first support it, and if Dragonflow supports it we get it for free
<irenab> oanson, I will try to summarize
<irenab> 1. Keep L3agent support in DF (+fixing the issues to make it work again)
<irenab> 2. Advanced net services, lbaas (and maybe vpn) made working in l3agent enabled deployment
<irenab> 3. Provide DF native advanced services support
<irenab> correct?
<oanson> This is a t..."
1708178,2017-08-17 06:36:01 UTC,"After some investigation -
It's looks that  the lport of the logical-router is created before it's logical-switch created.
And for that we have no connectivity between the PODs and the service.."
1708178,2017-08-03 08:26:30 UTC,"Set to critical, since it breaks Kuryr integration. See IRC log above for plan."
1708186,2017-08-02 15:12:09 UTC,"StacktraceSource:
 #0  0x00007ff892566428 in ?? ()
 #1  0x00007ff89256802a in ?? ()
 #2  0x0000000000000020 in ?? ()
 #3  0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()"
1708186,2017-08-02 15:12:13 UTC,Thank you for your report!
1708186,2017-08-02 15:18:20 UTC,The related Xorg crash LP: #1708185.
1708191,2018-05-11 15:33:32 UTC,This change was made by a bot.
1708191,2017-08-03 06:18:55 UTC,see bug 1680904
1708191,2017-08-03 02:34:15 UTC,From the associated forum post (https://ubuntuforums.org/showthread.php?t=2367549) the following is claimed as dmesg output:
1708191,2017-08-02 15:43:09 UTC,apport information
1708191,2017-08-02 15:43:06 UTC,apport information
1708191,2017-08-02 15:43:01 UTC,apport information
1708191,2017-08-02 15:43:00 UTC,apport information
1708191,2017-08-02 15:42:58 UTC,apport information
1708191,2017-08-02 15:42:57 UTC,apport information
1708191,2017-08-02 15:42:54 UTC,apport information
1708191,2017-08-02 15:42:56 UTC,apport information
1708191,2017-08-02 15:42:46 UTC,apport information
1708191,2017-08-02 15:42:47 UTC,apport information
1708191,2017-08-02 15:42:55 UTC,apport information
1708191,2017-08-02 15:42:50 UTC,apport information
1708191,2017-08-02 15:42:49 UTC,apport information
1708191,2017-08-02 15:42:52 UTC,apport information
1708191,2017-08-02 15:42:51 UTC,apport information
1708193,2017-08-02 15:47:13 UTC,"Reported upstream with a screenshot, https://bug785741.bugzilla-attachments.gnome.org/attachment.cgi?id=356791"
1708197,2017-10-10 13:27:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708197,2018-06-09 22:29:33 UTC,Confirming this bug also affects users of Ubuntu 16.04.4 LTS - which has the same version of fail2ban (0.9.3-1).
1708201,2020-10-16 10:19:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708207,2020-09-24 13:12:53 UTC,"This got implemented as notes in the end, so that the import tags can be hash stable. The main commit that added this support is b94455f."
1708207,2017-08-09 16:27:22 UTC,"I think we should do this before re-importing the world and declaring hash stability, so I think it'd be useful to tag it as if it affects hash stability, so we don't forget about the necessary ordering here."
1708207,2017-10-26 22:27:47 UTC,"Would you like this to be in the tag message? Is the ""who"" a git identity?"
1708207,2017-08-09 16:27:51 UTC,"(and effectively we'd be rewriting tags, which breaks user expectations wrt. repo stability)"
1708212,2017-08-02 21:26:41 UTC,"The charm reports the number of OSDs as the number of running OSD processes, so from this perspective the charm is reporting the correct value since it appears that the process is running. To better determine where the issue might lie, is the storage truly removed, or is the disk actually still attached to the running instance?"
1708212,2017-08-03 06:05:52 UTC,"Billy, I can reproduce this with the following (on AWS):
 - juju deploy -n 3 ceph-mon
 - juju deploy -n 3 ceph-osd --storage osd-devices=ebs,32G,2 --storage osd-journals=ebs,8G,1
 - juju add-relation ceph-mon ceph-osd"
1708212,2017-09-04 15:32:05 UTC,"I'm marking this as 'Low' as the typical deployment use case for Ceph is not clouds, where block device detachment is something that can actually happen; most Ceph deployments are hardware bases where the block devices attached don't change via software operations."
1708214,2017-08-07 18:18:16 UTC,"To be clear, this won't really help the importer. We don't use pristine-tar directly (and in fact, you can't in the most general case), but have to use gbp to extract orig tarballs, because of component tarballs. So, really, it would be most useful to have this flag to gbp as well, which probably relies on pristine-tar having this :)"
1708215,2017-08-02 17:19:43 UTC,"UPDATE:
Restarting ""SPICE VDAagent"" within the VM allows me to paste again from host to VM, however as soon as I use copy within the VM, it stops working again."
1708215,2020-09-26 17:08:27 UTC,"This sounds like a bug in Spice, and not like a bug in QEMU. If you still face this problem, please report it to the spice project instead (see https://www.spice-space.org/support.html)."
1708221,2017-08-02 17:26:12 UTC,"I suggest using https://github.com/freeekanayaka/charm-test as the basis, and extending it as needed"
1708222,2017-08-02 17:58:53 UTC,apport information
1708222,2017-08-02 17:58:56 UTC,apport information
1708222,2017-08-10 17:57:23 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1708222,2017-08-04 22:09:50 UTC,It had just exploded in Phoronix! See
1708222,2017-08-02 17:58:52 UTC,apport information
1708222,2017-08-11 12:11:43 UTC,It seems to be confirmed as a hardware problem. See:
1708222,2017-08-02 17:58:59 UTC,apport information
1708222,2017-08-02 17:58:51 UTC,apport information
1708222,2017-08-02 17:58:47 UTC,apport information
1708222,2017-08-02 17:58:48 UTC,apport information
1708222,2017-08-02 17:58:46 UTC,apport information
1708222,2017-08-02 17:58:43 UTC,apport information
1708222,2017-08-02 17:58:41 UTC,apport information
1708222,2017-08-02 17:58:40 UTC,apport information
1708222,2017-08-02 17:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1708222,2017-08-02 17:26:41 UTC,The other log file.
1708222,2017-08-02 17:58:50 UTC,apport information
1708222,2017-08-02 17:58:44 UTC,apport information
1708225,2017-08-04 17:17:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490992"
1708225,2017-08-04 22:25:16 UTC,"Change abandoned by Gerald McBrearty (<email address hidden>) on branch: master
Review: https://review.openstack.org/490992
Reason: Missed the blueprint https://review.openstack.org/#/c/483790
Abandoning"
1708234,2020-02-11 07:44:29 UTC,"Francesco & John,"
1708234,2020-02-11 10:50:00 UTC,"Hi Gael,
afaik this bug was solved with a validation [1], and it's also backported in the old releases [2][3][4][5], so I think we're good here."
1708235,2017-11-24 01:52:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708241,2017-09-12 16:30:58 UTC,"This may caused by l3 plugin bug. so possibly l3 flavor may solve this.
So for now this is low priority and assigned to me."
1708241,2017-11-04 23:01:09 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/331382
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1708255,2021-01-26 06:51:56 UTC,"bridges:
  br-lan:
    dhcp4: false
    addresses:
      - 10.0.0.1/24
      - fd00::1/60
    interfaces: []
    parameters:
      stp: false"
1708255,2021-01-26 14:40:10 UTC,"Hey DanyChen, thanks for using cloud-init, and for taking the time to comment.  I've just quickly tested that network configuration locally, and it doesn't seem to cause an error for me.  Would you be able to open up a new bug with further details?  (If it turns out to be the same as this one, we can always mark it as duplicate. :)"
1708255,2021-01-26 14:48:33 UTC,I've just tested the two configs given as examples here; the invalid config produces this traceback in the logs:
1708255,2019-02-22 10:54:07 UTC,"I've confirmed locally that this is still an issue, but it's not clear to me how many places might provide empty/broken configuration, so I'm not sure what the priority should be."
1708259,2018-08-05 10:53:31 UTC,"pywin32 had no wheels available until very recently (Jan 2018), so the package had to be installed manually through their exe installer, now it can be finally pip installed."
1708259,2018-08-07 13:41:49 UTC,"So should the status be changed to ""Fixed Released""?"
1708260,2017-08-02 20:21:44 UTC,"My feeling is this should be a 400 returned to the user, because this is probably not what they intended (maybe they typoed an assignment on their side)"
1708260,2017-08-02 20:25:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490195"
1708260,2017-08-03 15:57:38 UTC,This is a latent issue so I'm going to remove the pike-rc-potential tag.
1708260,2017-08-04 09:18:34 UTC,"Reviewed:  https://review.openstack.org/490195
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9155da345e5d6d1aee293bc66f746da52bca4c79
Submitter: Jenkins
Branch:    master"
1708260,2017-08-07 13:23:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/491487"
1708260,2017-08-07 23:37:44 UTC,"Reviewed:  https://review.openstack.org/491487
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c95cd011d01f7e5cbd10346223be995f6507f9e7
Submitter: Jenkins
Branch:    stable/ocata"
1708260,2017-08-11 12:27:05 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1708260,2017-08-22 11:39:12 UTC,This issue was fixed in the openstack/nova 15.0.7 release.
1708289,2019-09-19 14:49:01 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1708293,2017-08-16 17:40:39 UTC,"I've tested this kernel and observed no regressions. Updated firmware has not been released to expose these IDs, so I can't directly test this. However, it turns out that there is a typo in the ACPI IDs that has since been fixed upstream, meaning the proposed patches are insufficient to solve the issue. One more patch is needed, and I've filed LP: #1711182 to track that."
1708293,2017-08-28 10:14:27 UTC,This bug was fixed in the package linux - 4.10.0-33.37
1708293,2017-08-16 16:34:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1708293,2017-08-02 21:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1708302,2020-12-08 15:00:56 UTC,"The puppet change [1] to address this bug has merged.
When the THT chagne [2] lands the bug can be closed."
1708302,2021-01-28 10:57:32 UTC,This issue was fixed in the openstack/puppet-tripleo 14.0.0 release.
1708308,2017-08-02 23:04:02 UTC,"Output from test program with boost 1.58 and boost 1.59
 Compiled against boost 1_58
 a = 00000000-0000-0000-0000-000000000100
 b = 00000000-0000-0000-0000-000000000131
 a !< b
 a !> b
 a != b
 mappa[""00000000-0000-0000-0000-000000000100""] = Riga a
 Mappa contains 1 elements
 Mappa[""00000000-0000-0000-0000-000000000100""] = Riga a
 Mappa[""00000000-0000-0000-0000-000000000131""] = Riga a (Should raise an exception because we never
 assigned it)"
1708313,2017-08-03 00:20:20 UTC,Ditto systemd-localed.service
1708316,2019-10-03 17:14:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686444"
1708316,2019-10-03 16:59:31 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/625371
Reason: Yup, this needs a spec. Note that there was some pre-existing work here too https://review.opendev.org/#/c/490332/"
1708316,2019-10-03 16:59:12 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/490332"
1708316,2018-12-14 22:53:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625371"
1708316,2018-11-18 20:30:18 UTC,"Change abandoned by Maciej Kucia (<email address hidden>) on branch: master
Review: https://review.openstack.org/575998"
1708316,2018-07-09 13:14:33 UTC,"Reviewed:  https://review.openstack.org/558125
Committed: https://git.openstack.org/cgit/openstack/nova-specs/commit/?id=75099b24d24e2212486ccdd427a98a007aea74e7
Submitter: Zuul
Branch:    master"
1708316,2018-06-17 21:00:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575998"
1708316,2017-11-19 22:48:34 UTC,"Posted spec for API change in Nova. Feedback is appreciated
https://review.openstack.org/#/c/521392"
1708316,2018-04-01 21:29:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558125"
1708316,2017-08-03 00:58:41 UTC,"From the debug messages, below part are releated to this problem."
1708316,2017-08-03 01:26:14 UTC,This is the JSON data when VM has two ports for connecting different networks :
1708316,2018-03-27 19:34:02 UTC,"Reviewed:  https://review.openstack.org/521392
Committed: https://git.openstack.org/cgit/openstack/nova-specs/commit/?id=253e0acafe7024e1869745b98e270f30cbc32d48
Submitter: Zuul
Branch:    master"
1708316,2017-08-09 10:39:30 UTC,"API spec is wrong. For example:
https://developer.openstack.org/api-ref/compute/#servers-ips-servers-ips
Addresses field is a dict not a list. Therefore it is not expected that network name is non-unique."
1708316,2017-08-09 10:47:41 UTC,"This is going to need to come in as a spec, as it would be an API change. I'd also want the Neutron folks involved in this to figure out if this is their desired state."
1708316,2017-08-03 02:08:31 UTC,Found same bug in Mitaka.
1708316,2017-08-09 22:52:45 UTC,"network names are definitely not unique in neutron and I don't think it would be tenable to make them that way. Ignoring the backward-compatibility, it would make the acceptable name field values for a given tenant completely unpredictable because they can't see all of the names that are in use."
1708343,2018-02-26 20:01:26 UTC,I have the exactly same problem anyone could help us with this please?
1708360,2017-08-08 02:24:33 UTC,"Update to my earlier report, after performing a clean install it looks like Linux Bridge is still installed by ""/etc/ansible/roles/openstack_hosts"" during the initial run for use by lxcbr0, on a clean install the workaround failed from what I presume is do to the order of operations of the original workaround.  By switching the check to look for OVS first it allowed the containers to be wired and the initial ""openstack-ansible setup-hosts.yml"" as well as subsequent installation playbooks required to run the full install without failing."
1708360,2017-08-08 16:20:39 UTC,"I am sorry we don't have enough resources to triage this bug at the moment.
Please see our bug triage conversation."
1708360,2017-11-07 05:50:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518230"
1708360,2020-12-03 13:06:12 UTC,"we nowadays do not run neutron agents inside lxc, and run ovs in CI so I think the issue should have been resolved now."
1708367,2017-08-03 23:55:03 UTC,*** This is an automated message ***
1708372,2017-08-03 07:15:10 UTC,"commit 504c932c7c47a6b4c572302a13873f7d83af1ff3
Author: Masaki Ota <email address hidden>
Date:   Fri Jun 16 09:29:39 2017 +0900"
1708372,2017-08-16 16:33:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1708372,2017-08-28 10:14:02 UTC,This bug was fixed in the package linux - 4.4.0-93.116
1708375,2018-10-10 01:31:29 UTC,"Please add DEP-3 headers here, and preferably reattach as a debdiff with a changelog entry."
1708375,2018-10-01 15:27:16 UTC,I have updated the patch with required changes. Thanks.
1708375,2018-10-01 15:04:41 UTC,I recommend changing these to be:
1708375,2018-10-01 14:31:12 UTC,Updated the patch as quilt patch
1708375,2017-08-08 12:26:28 UTC,"The attachment ""telepathy-purple.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1708375,2018-03-23 14:34:19 UTC,I have updated the patch. Is there anything else needed for this?
1708375,2018-07-03 08:14:23 UTC,Subscribing the security team to get their input since that changes the apparmor profile
1708375,2017-08-03 11:10:35 UTC,"> - I don't understand the line `/usr/lib/purple-2*/`.
"
1708375,2017-08-03 10:01:10 UTC,I did some work on telegram-purple.
1708375,2017-08-07 19:57:13 UTC,Updated
1708375,2017-09-23 18:22:22 UTC,Patch updated
1708378,2017-09-15 07:52:53 UTC,Having a similar issue in a kolla pike ubuntu/binary deployment:
1708378,2017-10-27 07:31:31 UTC,This issue was fixed in the openstack/heat 10.0.0.0b1 development milestone.
1708378,2017-10-23 06:04:55 UTC,"Reviewed:  https://review.openstack.org/512907
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=95ed444fbbc83e26d99ff2fcdfed874a3710cdc7
Submitter: Zuul
Branch:    stable/pike"
1708378,2017-10-18 01:23:59 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/512907"
1708378,2017-10-30 11:58:19 UTC,This issue was fixed in the openstack/heat 9.0.1 release.
1708378,2017-10-13 08:20:53 UTC,I changed this bug to incomplete from magnum.
1708378,2017-10-13 08:20:23 UTC,"This run is from yesterday and it shows just a timeout, nothing broken. On openstack-infra extremely frequently is related to powerless resources (i.e. a m1.large vm running all openstack services plus a magnum cluster)."
1708378,2017-10-13 08:16:08 UTC,How is this confirmed in magnum? We don't see any problem's with magnum pike and our CI passes without any problems
1708378,2017-10-13 07:55:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511752"
1708378,2017-10-13 06:01:20 UTC,"Not sure if they are the same, attaching my log here."
1708378,2017-10-17 21:21:33 UTC,"Reviewed:  https://review.openstack.org/511752
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=a532535b613777b144b2e159e349783d2a21fd1e
Submitter: Zuul
Branch:    master"
1708384,2017-08-28 02:24:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/498289"
1708417,2017-08-22 11:19:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1708417,2017-08-28 10:36:00 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1071.79
1708433,2017-08-04 10:23:38 UTC,"this was done on a fortvile (intel XL710)
this should be a supported nic."
1708433,2017-08-03 14:27:17 UTC,is there a specific requirement on the kind of hardware used?
1708433,2019-11-21 12:04:10 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/695408"
1708433,2019-03-24 23:04:48 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1708433,2019-03-22 03:48:26 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1708433,2018-10-08 20:53:33 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1708433,2018-10-03 22:06:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/607729"
1708433,2018-10-03 17:03:37 UTC,"Reviewed:  https://review.openstack.org/605118
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e1d55af4089fe6b76680285e36069ab0f57404ab
Submitter: Zuul
Branch:    stable/rocky"
1708433,2018-09-25 16:22:35 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605118"
1708433,2018-09-18 20:14:20 UTC,"Reviewed:  https://review.openstack.org/591898
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=68011c40ae2ab0900674408a88f62a60a802fef7
Submitter: Zuul
Branch:    master"
1708433,2019-12-17 20:21:46 UTC,"Reviewed:  https://review.opendev.org/695408
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=af5df70f617b03f86cd3dc898c889a1825630c9e
Submitter: Zuul
Branch:    stable/pike"
1708433,2018-08-15 05:40:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/591898"
1708433,2018-08-15 05:38:42 UTC,I'll post a patch to make this a fast failure in the API when trying to attach sriov ports to existing instances. Support for this in the API would require a microversion to indicate when nova actually supports it (if we ever support it) and it would require RPC API version checks on the nova-compute service (and some compute drivers might not support it at all).
1708433,2018-08-15 03:38:18 UTC,Setting to Triaged to acknowledge we could use a bug fix here to fail fast in the API since attaching SRIOV NIC to existing instances is not currently supported.
1708433,2018-08-15 03:36:05 UTC,"Nova doesn't support hot-plugging SR-IOV ports to existing instances, see the spec:"
1708433,2018-07-27 03:22:39 UTC,Someone in the nova channel just reported this same bug running queens version 17.0.4:
1708433,2018-04-05 17:48:30 UTC,"Just posting a ""me too"" ;-)"
1708433,2017-10-04 04:17:26 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1708433,2017-08-04 10:49:48 UTC,Is this related to https://blueprints.launchpad.net/nova/+spec/sriov-interface-attach-detach maybe?
1708433,2017-08-04 11:49:07 UTC,yes it is... i taught that was fixed litrally years ago.
1708433,2018-08-15 14:53:12 UTC,"I would like to develop this feature, How can I start?"
1708442,2020-11-05 04:17:23 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1708442,2017-08-15 11:00:20 UTC,ping
1708442,2020-09-05 12:21:54 UTC,Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays?
1708442,2017-08-03 14:46:39 UTC,"I've build qemu-nbd-bug.go into binary qemu-nbd-bug (go build qemu-nbd-bug.go), so to reproduce bug anyone may try:
0) ensure image.img exists in current folder. image.img may be copied from ""Qemu-nbd core dump and script to reproduce "" attachment.
1) sudo ./qemu-nbd-bug
2) wait while binary aborting(panicking)
3) check dmesg for error like ""blk_update_request: I/O error, dev nbd0, sector 42117""
4) check qemu-nbd core dump (since it's aborting due to assert in aio_co_enter(), util/async.c:468)."
1708442,2017-08-03 14:30:06 UTC,"03.08.2017, 17:01, ""Eric Blake"" <email address hidden>:

> On 08/03/2017 07:12 AM, Andrey Smetanin wrote:
>>  Public bug reported:
>>
>>  Description:
>>  During reading image from nbd device mounted by qemu-nbd server with url backend I/O error happens
>>  ""blk_update_request: I/O error, dev nbd0, sector 42117"" dmesg. After some investigation I found that qemu-nbd server aborts in aio_co_enter() assert in util/async.c:468.
>
> Based on the backtrace, this looks to be a bug in the block/curl.c
> driver, rather than the nbd/ or block/nbd.c code. If I'm right, it
> should be possible to reproduce the crash using qemu-io directly on the
> curl path, rather than adding the extra layer of an nbd client reading
> through qemu-nbd (then again, having the qemu-nbd layer may be what is
> allowing multiple parallel requests to hit the curl driver at once,
> while qemu-io is not quite as easy to provoke into performing
> complicated access patterns).
>
>>  Steps to reproduce:
>>
>>  1) sudo go run qemu-nbd-bug-report/qemu-nbd-bug.go (see qemu-nbd-bug-
>>  report.tar.gz)
>>
>>  or try directly
>>
>>  1) qemu-nbd -c /dev/nbd0 -r -v --aio=native -f qcow2 json:{""file.driver"":""http"",""file.url"":""http://localhost:9666/image"",""file.readahead"":3276800
>
> Presumably, you've got something serving the file at port 9666?


Yes, you are right. I'm using qemu-nbd-bug.go(see qemu-nbd-bug-report.tar.gz) script which does it.

>
>>  2) try read whole nbd device while error in dmesg appears x
>>
>>  Versions:
>>
>>  1) qemu built from sources(/configure --target-list=x86_64-softmmu --disable-user --enable-curl --enable-linux-aio --enable-virtfs --enable-debug --disable-pie
>>  , top commit 5619c179057e24195ff19c8fe6d6a6cbcb16ed28):
>>
>>  qemu-nbd -v
>>  qemu-nbd 2.9.90 (v2.10.0-rc0-67-g5619c17)
>>
>>  2) libcurl(built from sources, top commit
>>  1767adf4399bb3be29121435e1bb1cc2bc05f7bf):
>>
>>  curl -V
>>  curl 7.55.0-DEV (Linux) libcurl/7.55.0-DEV OpenSSL/1.0.2g zlib/1.2.8
>>
>>  Backtrace:
>>  (gdb) bt
>>  #0 0x00007f7131426428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
>>  #1 0x00007f713142802a in __GI_abort () at abort.c:89
>>  #2 0x00007f713141ebd7 in __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x54c924 ""self != co"",
>>      file=file@entry=0x54c871 ""util/async.c"", line=line@entry=468,
>>      function=function@entry=0x54c980 <__PRETTY_FUNCTION__.24766> ""aio_co_enter"") at assert.c:92
>>  #3 0x00007f713141ec82 in __GI___assert_fail (assertion=0x54c924 ""self != co"", file=0x54c871 ""util/async.c"", line=468,
>>      function=0x54c980 <__PRETTY_FUNCTION__.24766> ""aio_co_enter"") at assert.c:101
>>  #4 0x00000000004fe6a2 in aio_co_enter (ctx=0xf0ddb0, co=0xf14650) at util/async.c:468
>>  #5 0x00000000004fe637 in aio_co_wake (co=0xf14650) at util/async.c:456
>>  #6 0x0000000000495c8a in curl_read_cb (ptr=0xf566d9, size=1, nmemb=16135, opaque=0xf1cb90) at block/curl.c:275
>>  #7 0x00007f713242ac24 in Curl_client_chop_write () from /usr/lib/x86_64-linux-gnu/libcurl.so
>>  #8 0x00007f713242ae03 in Curl_client_write () from /usr/lib/x86_64-linux-gnu/libcurl.so
>>  #9 0x00007f713244e1cf in readwrite_data () from /usr/lib/x8...
"
1708442,2017-08-03 13:51:44 UTC,"On 08/03/2017 07:12 AM, Andrey Smetanin wrote:

> Public bug reported:
>
> Description:
> During reading image from nbd device mounted by qemu-nbd server with url backend I/O error happens
> ""blk_update_request: I/O error, dev nbd0, sector 42117"" dmesg. After some investigation I found that qemu-nbd server aborts in aio_co_enter() assert in util/async.c:468.
>
"
1708442,2017-08-03 14:51:02 UTC,"I've attached patch which resolves bug, but actually it's just workaround and may be not unsafe, because it's just ignore assert."
1708443,2017-08-04 00:00:50 UTC,"The attached patch fixes the build.
Please find build log here:
https://launchpad.net/~rbalint/+archive/ubuntu/libevent-2.1/+build/13193953"
1708443,2017-08-04 13:05:00 UTC,"The...ubuntu1 upload did not apply the full patch, this new patch adds the missing ocamlbuild build-dep."
1708445,2017-08-04 10:25:39 UTC,Step-by-step on how to replicate:
1708445,2017-08-04 10:28:01 UTC,"Please ignore these two lines, just running ""docker run"" is required:"
1708445,2017-08-04 11:02:55 UTC,A workaround may be used to temporarily fix the problem (following on from the replication instructions above):
1708445,2017-08-04 15:43:03 UTC,Additional note:
1708460,2019-11-14 10:14:51 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/534213
Reason: According to what we agreed during Shanghai PTG, I abandon this patch for now due to no activity. If You would be interested in continue work on this, feel free to restore the patch."
1708460,2018-02-01 22:56:12 UTC,"Fouad,"
1708460,2018-02-06 00:03:08 UTC,"Miguel,
As I explained above, our contribution does not depend on #445762. We would like to add new QoS rule that dynamically reacts to congestion sources if they exceed their limits. In this process, we used ECN marking as a mechanism to detect the congestion in the network. As you know ECN is an end-to-end process where the sender, receiver, and the middle device must be ECN enabled. For the #445762 proposal, the sender and receiver (mostly VMs) must by their selfs activate ECN (it could be by an administrator) which is not all the time possible especially for Cloud provider. In our contribution we avoid OS dependency and we ensure that ECN is activated in VMs tap interfaces using OVS table rules.
In addition to the activation, we calculate the congested packets related to VMs or tenants and react to the congestion case using bandwidth limitation rule. By doing that, we keep the bandwidth consumption at its normal rate and avoid the congestion in the network which could impact performance-sensitive applications.
Read more details in our Spec #534213."
1708460,2018-01-25 21:50:53 UTC,"Similar RFE, https://bugs.launchpad.net/neutron/+bug/1505627, was tentatively approved on 2017-05-25, contingent on submission of a spec (https://review.openstack.org/#/c/445762). Since this RFE (spec https://review.openstack.org/#/c/534213) seems to be a superset of the former one, will bring it to the attention of the drivers team, with the hope of unifying the efforts. We have scarce resources, let's not spread ourselves thin duplicating effort"
1708460,2017-08-04 08:44:46 UTC,"Yes, that's a good idea, we could combine both enhancements to integrate ECN in neutron qos."
1708460,2018-01-19 08:40:34 UTC,"There is also another RFE for similar feature: https://bugs.launchpad.net/neutron/+bug/1505627
Maybe I'm wrong but for me it looks like we can do one of them (don't know which) but not both. Can You talk about it and maybe continue work only on one of them.
Specs proposed for these feature are: https://review.openstack.org/#/c/534213 and https://review.openstack.org/#/c/445762"
1708460,2017-08-24 06:18:45 UTC,"Marking this as invalid, to allow tracking the bug from 1505627"
1708460,2017-08-04 08:38:32 UTC,"Hello Reedip, yes the two enhancements are related, it's a good idea to work on both in order to make a coherent addition to QoS."
1708460,2017-08-04 03:05:04 UTC,Lets work together on this with [1].
1708460,2018-01-24 15:56:14 UTC,"The scope of #445762 is to activate ECN marking in routers and networks which are places among others in the architecture where ecn could be enabled. Besides the ECN enablement which we do on OpenvSwitch in case the VMs do not activate it, we compute the congestion and react to it which is not #445762 objectif."
1708471,2017-10-17 23:33:14 UTC,I could replicate this as well.
1708480,2017-08-20 05:30:26 UTC,apport information
1708480,2017-08-20 05:30:28 UTC,apport information
1708480,2017-08-20 05:30:31 UTC,apport information
1708480,2017-10-07 16:48:28 UTC,"There have been no updates to this bug report, but I wanted to post that the latest daily 17.10 image (installed today, 10.07.2017) still has this screen tearing problem.  Worse, on a Yoga 910, it adds a problem that the screen starts rotated 90 clockwise and can't be fixed."
1708480,2017-09-01 20:25:43 UTC,I experience this as well on fully up to date XPS 13 (9560) on 17.10
1708480,2017-09-03 15:25:29 UTC,"In attempting to find a Debian-based build that does not have this issue, I ran across Debian 9 - Stretch. It is running the 4.9.0-3-amd64 kernel.  There is NO SCREEN TEARING with that kernel (though it does start the screen rotated 90 degrees)."
1708480,2017-08-20 05:30:25 UTC,apport information
1708480,2017-12-18 11:40:29 UTC,"I also feel the tearing problem on my MSI GP62 notebook running Ubuntu 17.10. The tearing sometime occurs when login, when many process has been run, and at this time when I write this comment, the tearing is also revealed."
1708480,2017-08-20 05:30:33 UTC,apport information
1708480,2017-08-20 05:30:24 UTC,apport information
1708480,2017-08-20 05:30:18 UTC,apport information
1708480,2017-08-20 05:30:21 UTC,apport information
1708480,2017-08-20 05:30:19 UTC,apport information
1708480,2017-08-20 05:30:16 UTC,apport information
1708480,2017-08-20 05:30:15 UTC,apport information
1708480,2017-08-20 05:30:13 UTC,apport information
1708480,2017-08-20 05:30:12 UTC,apport information
1708480,2017-08-15 02:52:06 UTC,Apologies!  I got my numbers crossed.  The bug is NOT fixed in the mainline kernel!  I had loaded a prior kernel from 16.04 (v.4.4).  That was what I reported on.  Kernel v4.13.0-041300rc4-(4.13.0-041300rc4.201708062231) still has screen tearing.  I will remove the tag and replace it with 'kernel-bug-exists-upstream'.
1708480,2017-08-15 02:28:33 UTC,The bug does seem to be fixed in the mainline kernel v4.13.0-041300rc4-(4.13.0-041300rc4.201708062231).  I will add the tag.  Thank you.
1708480,2017-08-14 19:06:42 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1708480,2017-08-14 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1708480,2017-08-03 16:22:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1708480,2017-08-20 05:30:22 UTC,apport information
1708491,2019-10-28 18:43:45 UTC,closing fix-release based on https://review.opendev.org/#/c/541478/
1708491,2018-01-05 11:50:01 UTC,"As we discussed in a weekly meeting, one possible reason for the tests to take too long is because the waiters on both tempest side and manila server side are too long."
1708491,2018-02-06 22:23:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541478"
1708491,2017-08-03 17:14:25 UTC,"Even with the lvm driver instead of generic these tests take significant time.  From the same review as above, see http://logs.openstack.org/39/489639/7/check/gate-manila-tempest-minimal-dsvm-lvm-centos-7/62f0c3f/console.html"
1708491,2018-02-07 16:22:48 UTC,"Reviewed:  https://review.openstack.org/541478
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=53ec28a1caa2555917974c8e0eb0efffdf58dfdb
Submitter: Zuul
Branch:    master"
1708509,2017-11-08 12:30:41 UTC,In my particular case the issue was misconfiguration of nodepool. I was missing the 'formats' configuration element causing nodepool to provide an incomplete command to diskimage-builder:
1708509,2017-11-07 18:48:23 UTC,"I'm seeing the same thing with the checkout at bc6c928bb960729e8df60562adafe2d50a1f55ec (today's HEAD) on ubuntu-xenial when using a cloud instance. Given that in the above-mentioned abandoned review there is confirmation that others have seen it too, I'm marking this confirmed."
1708509,2017-11-07 18:55:40 UTC,"Interestingly, I'm seeing that the image failed to convert in the log which may be a vector here:"
1708509,2017-08-22 18:19:41 UTC,"Here is the complete log.
http://paste.openstack.org/show/619079/"
1708509,2017-08-03 18:45:34 UTC,Here is the identified fix for this issue.
1708509,2017-09-13 20:18:16 UTC,"Change abandoned by Swaminathan Vasudevan (<email address hidden>) on branch: master
Review: https://review.openstack.org/490637
Reason: Abandon this patch because the issue is with the 'kpartx' in the distro."
1708509,2017-08-03 19:20:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490637"
1708511,2017-08-03 23:21:26 UTC,This may be a duplicate of bug 1692981. Thanks.
1708513,2017-08-03 19:25:39 UTC,Screenshot of workarounds windows
1708516,2017-08-03 19:34:58 UTC,upload the error1 file
1708516,2017-08-24 16:33:10 UTC,"This is likely due to Docker for Mac's transparent use of QEMU user mode emulation via binfmt-misc.  I don't think I've ever seen OpenJDK work successfully under QEMU's user mode emulation, but I seem to recall the last time I went looking for an issue about it I wasn't very successful."
1708516,2017-08-29 22:22:18 UTC,"We meet the same issue. We use Docker and qemu-user-static to build our project (CRIU) in travis-ci. We used ppc64le/ubuntu:trusty and it worked fine, but it was broken about a month ago (#1710399). I tried to use ppc64le/ubuntu:xenial and meed this issue."
1708522,2017-10-15 23:55:56 UTC,"Hi David,"
1708522,2017-10-17 21:22:23 UTC,"Robert, this is already a feature proposal on the spreadsheet when we discussed the functionality at the beginning. We didn't implement it in the initial development work though to keep the effort manageable. So I'll keep this wishlist item here."
1708526,2017-10-03 07:16:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708527,2017-12-08 14:10:32 UTC,https://github.com/snapcore/snapd/pull/4381
1708527,2019-10-29 18:18:16 UTC,The referenced pull request was merged in 2017 and has been released for a long time. I'm marking this bug as fix released.
1708528,2017-08-04 01:55:03 UTC,"The desktop icons actually aren't part of gnome-shell. It's nautilus-desktop, which may also go away in future releases (!) It's also an X11-only app so depends on Xwayland (!)"
1708528,2017-08-28 13:17:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1708528,2017-08-28 13:18:09 UTC,"indeed, it doesn't seem due to the .desktop files since copying one from /usr/share/applications has the same issue"
1708529,2019-11-21 14:23:44 UTC,This is the expected behaviour. The commissioning Ubuntu release must be imported for that architecture for the image to be allowed. This is because MAAS uses that Ubuntu to deploy that custom image.
1708529,2019-11-21 07:55:01 UTC,Still failed becuase no Ubuntu images were imported on 2.4.2 version. :(
1708529,2019-09-19 14:49:03 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1708539,2017-08-03 21:24:32 UTC,"For an example of how this could work, see what happens when, on a clean install, you try to do a backup with the Backups program."
1708550,2018-07-06 08:27:53 UTC,"I disagree here, the idea of running tempest with pre-provisioned credential is also to use pre-defined networks only, in order to be able to restrict the effect of running these tests in a production environment. See also the description of this config option:"
1708550,2018-12-13 11:25:37 UTC,I am re-analysing this bug from what I said during office hour[1]
1708550,2017-08-18 07:21:08 UTC,"Thanks for reporting this.
It's no harm for neutron testcases to create networks,
and we'd better do so to get a clean test environment."
1708550,2018-06-14 10:28:44 UTC,"I agree that creating network ""per test class"" shouldn't be any problem in Neutron tests so IMHO this is not an issue at all (at least from neutron perspective)."
1708551,2017-08-22 11:16:11 UTC,xhci doesn't work with macos because macos has a white list of supported xhci controllers and ignores the xhci adapters emulated by qemu.
1708551,2017-08-08 05:15:32 UTC,"In doing so, the device is now unseen by the system."
1708551,2017-08-04 15:29:23 UTC,"Then simply omit the ""bus=usb-bus.0"" here - the devices then should be put onto the XHCI bus automatically."
1708551,2017-08-04 16:18:57 UTC,"Removing the `bus=usb-bus.0` param from everything, [as shown here](https://pastebin.com/x0Cp70XD), boots fine; but completely breaks mouse functionality. To mitigate, i tried passing through a Logitech mousepad I own--in similar fashion to the iPhone; but Host complained about permissions & `libusb` requiring ""write access to USB device nodes""."
1708551,2017-08-07 16:34:57 UTC,"Ok, could you maybe try something like this instead:"
1708551,2017-08-04 06:31:29 UTC,"Could you please try to run QEMU without the ""-usb"" option here? ""-usb"" automatically creates an EHCI and UHCI controller on the q35 machine, so that might be the reason that your USB devices get connected as USB 2.0 instead."
1708551,2017-08-04 13:19:12 UTC,"Doing so returns:
`qemu-system-x86_64: -device usb-tablet,bus=usb-bus.0: Bus 'usb-bus.0' not found`"
1708563,2017-08-04 15:22:53 UTC,"Crash reports from apport are only sent to Launchpad, where you would have a browser window opened to add more details, if you are running the development release of Ubuntu (currently Artful Aardvark).  Otherwise, crash reports are silently sent to errors.ubuntu.com.  If I recall correctly, the design decision was to make apport as unintrusive as possible hence there is not a second dialog displayed saying ""Yes, it was sent"".  That being said perhaps the dialog about sending the crash could be modified to notify you that no further action is required."
1708563,2017-08-09 22:58:44 UTC,"That would be great. For years now I have been assuming it was broken, since there is no acknowledgement of any form. Consequently I have been pressing 'cancel' instead of submitting the report. Why not wait until the report has been sent before closing the dialog, for example, and giving an error if it isn't sent?"
1708565,2017-08-04 12:33:02 UTC,"Hello,"
1708570,2017-08-04 02:52:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490718"
1708572,2019-05-15 14:33:47 UTC,"This bug was fixed in the package nova - 2:13.1.4-0ubuntu4.4~cloud0
---------------"
1708572,2019-05-15 14:33:45 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1708572,2019-05-15 11:52:34 UTC,This bug was fixed in the package nova - 2:13.1.4-0ubuntu4.4
1708572,2019-05-15 11:42:30 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1708572,2019-05-13 19:26:49 UTC,Tagged xenial and mitaka as verified in line with https://bugs.launchpad.net/nova/+bug/1744079.
1708572,2019-05-02 17:30:48 UTC,"Hello lanrui280, or anyone else affected,"
1708572,2019-04-30 20:28:16 UTC,"Hello lanrui280, or anyone else affected,"
1708572,2019-04-15 14:33:25 UTC,"Reviewed:  https://review.openstack.org/530744
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e2d2c3e8b14a5461c95014be3accb1e40f3d1a0b
Submitter: Zuul
Branch:    stable/ocata"
1708572,2019-03-26 04:18:20 UTC,"Reviewed:  https://review.openstack.org/530743
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1a4debb3dd2726299bbee0c07b7fc052ac72555b
Submitter: Zuul
Branch:    stable/pike"
1708572,2019-01-24 07:12:45 UTC,"Change abandoned by Zhang Hua (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/631372"
1708572,2017-10-17 13:31:51 UTC,Are you using OpenStackClient for calling the live-migration action ? Which exact CLI call do you do ?
1708572,2019-01-17 02:22:58 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/631372"
1708572,2019-01-17 02:29:44 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/631376"
1708572,2017-12-01 17:04:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524681"
1708572,2017-12-14 17:17:31 UTC,"Reviewed:  https://review.openstack.org/524681
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e097c001c8e11110efe8879da57264fcb7bdfdf2
Submitter: Zuul
Branch:    master"
1708572,2018-01-02 13:53:29 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/530743"
1708572,2017-10-26 06:43:06 UTC,I just used 'live migration' button of dashboard with 'disk over commit' and 'block migration' options.@Sylvain Bauza (sylvain-bauza)
1708572,2018-01-11 12:11:45 UTC,How to get this patch in Newton?
1708572,2018-03-18 10:28:37 UTC,"When I launched an instance using a volume stored on IP-SAN, 'Disk of instance is too large' exception was raised, and the amount of disk space available was also a negative number. It seems that all allocated IP-SAN volumes used to create instances are taken into account when computing the free space on the target host."
1708572,2018-09-28 16:15:34 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/530743
Reason: I'm just going to abandon. If anyone cares, restore and sort this out."
1708572,2018-09-28 16:15:40 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/530744
Reason: I'm just going to abandon. If anyone cares, restore and sort this out."
1708572,2018-01-02 13:53:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/530744"
1708576,2017-08-04 07:37:30 UTC,"In pike, the error raised:
rces.my_router-interface: Router interface for subnet 035c288e-e1ff-4b43-ac14-b8977a53b2bc on router 21893d1a-9018-48f9-a924-95b6211fd4df cannot be deleted, as it is required by one or more floating IPs."
1708576,2017-08-04 04:04:29 UTC,The version is mitaka
1708578,2017-08-04 04:06:33 UTC,This issue combined with lp#1703499 makes VMWare only able to display 800x600 by default since there is no obvious way to launch Ubuntu using Xorg and the Wayland patch still hasn't been applied for open-vm-tools.
1708580,2017-11-02 08:16:51 UTC,I suggest closing the OSSA task because of class D ( https://security.openstack.org/vmt-process.html#incident-report-taxonomy )
1708580,2021-02-17 20:01:05 UTC,"Fixes merged so long ago that no vulnerable branches are still supported, so I've marked our security advisory task Won't Fix indicating publication of any advisory at this point is highly unlikely."
1708580,2017-11-15 08:28:11 UTC,"Hi Tristan,"
1708580,2017-11-06 04:41:05 UTC,"IWAMOTO, I guess you could use this definition: https://cve.mitre.org/about/terminology.html#vulnerability"
1708580,2017-11-06 04:10:15 UTC,"Is there a definition of a vulnerability?
There have been a couple of security groups OSSAs. To me, it is not clear what amounts to a OSSA or note."
1708580,2017-10-25 22:48:03 UTC,This issue was fixed in the openstack/neutron 12.0.0.0b1 development milestone.
1708580,2017-09-09 08:04:39 UTC,"Reviewed:  https://review.openstack.org/501948
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6d43f2b1ad0f15992364cda3a0c691de5768dfd2
Submitter: Jenkins
Branch:    stable/pike"
1708580,2017-09-08 05:26:32 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/501948"
1708580,2017-09-08 01:17:57 UTC,"Reviewed:  https://review.openstack.org/490753
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=effa12889ba3393ec22d9a44e21cf00768643730
Submitter: Jenkins
Branch:    master"
1708580,2017-08-23 01:47:44 UTC,"Not sure if this is a security advisory item.
If it is, bug/1708358 needs to be handled so, too."
1708580,2017-08-23 01:08:31 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1708580,2017-09-25 14:33:07 UTC,This issue was fixed in the openstack/neutron 11.0.1 release.
1708580,2017-08-04 06:27:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490753"
1708592,2017-10-31 08:47:05 UTC,"Change abandoned by jiamin (<email address hidden>) on branch: master
Review: https://review.openstack.org/490762
Reason: Peng has created a patch to replace this one, https://review.openstack.org/#/c/516221/"
1708592,2017-08-04 06:55:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490762"
1708604,2017-09-08 07:55:32 UTC,Please backport these tcp_bbr patches to ubuntu-zesty 4.10 kernel. These patches have already landed in linux-stable kernels in 4.9.42 and 4.12.6.
1708604,2017-10-18 08:59:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1708604,2017-10-27 14:14:06 UTC,"I'm setting the Xenial task to invalid, since these patches are only for 4.10. Xenial/hwe kernel will get these patches automatically."
1708604,2017-10-27 14:15:14 UTC,"Hi @savetherbtz,"
1708604,2017-10-28 20:59:14 UTC,"Sadly, we've already workedaround that problem with a custom-built module. Let me see if my colleagues can test the kernel."
1708604,2017-10-30 19:26:53 UTC,This bug was fixed in the package linux - 4.10.0-38.42
1708604,2017-08-04 07:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1708607,2017-08-04 20:24:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708610,2018-02-09 03:50:25 UTC,"who can you start you mariadb service ,i have a issue:  sudo: unable to change to sudoers gid: Operation not permitted. when delopy in openshift."
1708610,2017-09-29 13:40:50 UTC,"I have the same issue:
170929  8:30:13 [Note] /usr/sbin/mysqld (mysqld 10.0.29-MariaDB-wsrep) starting as process 335 ...
170929  8:30:13 [Note] WSREP: wsrep_load(): Galera 25.3.19(r3667) by Codership Oy <email address hidden> loaded successfully.
170929  8:30:13 [Note] WSREP: CRC-32C: using hardware acceleration.
170929  8:30:13 [ERROR] WSREP: Bad value for 'node_address': '0.0.0.0': 22 (Invalid argument)
  at galera/src/replicator_smm_params.cpp:InitConfig():85
170929  8:30:13 [ERROR] WSREP: wsrep::init() failed: 7, must shutdown
170929  8:30:13 [ERROR] Aborting"
1708610,2017-10-16 12:57:48 UTC,"It works run the following command:
$ sed -i 's/wsrep_node_address = 0.0.0.0:4567/#wsrep_node_address = 0.0.0.0:4567/' /etc/kolla/mariadb/galera.cnf"
1708610,2017-08-16 12:54:24 UTC,"Hi,
After commenting-out/removing wsrep_node_address everything work's fine."
1708610,2017-12-05 05:49:18 UTC,could not reproduce with Debian source 5.0.1
1708613,2017-08-04 08:21:21 UTC,"One possible reason is there are multiple neutron-zvmagent run on the zVM, the guest is revoked by one of the agent, but this revoke operation didn't update switch tale ( switch table is deleted when the whole guest is destroyed), so there is a time gap between the revoke and the guest deploy. During this time, it is possible that another neutron_zvm_agent start and check the vswitch table, to regrant the guest. It will cause the guest is deleted but the still existed in the vswitch's authorized list."
1708617,2020-09-05 12:20:52 UTC,"ooking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays? And what is a ""question ping between 2 vm error"" ?"
1708617,2020-11-05 04:17:22 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1708636,2020-04-04 01:42:43 UTC,Do a fresh install of Classic Ubuntu and test on Debian. Are you experiencing the same issue?
1708636,2020-04-13 16:23:16 UTC,Do I still experience the bug I hit 4 years ago? I honestly can't remember which computer it was.
1708641,2018-02-16 09:31:50 UTC,"All hotkeys can be redefined by users (unless bug).
You can easily redefine them yourself according to you specific keyboard."
1708641,2019-06-21 10:05:06 UTC,Now that the new hotkey architecture is in (with importing of sparse files) I'll reopen this in case anyone wants to develop a specific hotkeys file for laptops.
1708641,2019-07-08 23:48:40 UTC,"It occurs to me that it's not just laptop vs. desktop but also regional variations.  Given that, this is probably something better addressed on the forum than in the bug database."
1708644,2020-09-19 10:45:31 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1708649,2017-08-04 12:10:48 UTC,Related:
1708665,2017-09-20 19:27:57 UTC,Very much related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858461
1708665,2017-12-15 20:26:17 UTC,This affects xenial and higher.
1708665,2018-01-05 17:21:15 UTC,There won't be time to SRU this for zesty before its EOL.
1708665,2018-01-11 07:15:39 UTC,This bug was fixed in the package awstats - 7.6+dfsg-1ubuntu2
1708665,2018-01-11 21:07:31 UTC,"Hello Carl, or anyone else affected,"
1708665,2018-01-11 21:08:18 UTC,"Hello Carl, or anyone else affected,"
1708665,2018-01-12 11:43:36 UTC,Verification for xenial:
1708665,2018-01-12 11:47:23 UTC,Verification for artful:
1708665,2018-01-12 14:42:54 UTC,Thanks much for the fix and the verification!
1708665,2018-01-22 09:43:52 UTC,This bug was fixed in the package awstats - 7.6+dfsg-1ubuntu0.17.10.2
1708665,2018-01-22 09:43:55 UTC,"The verification of the Stable Release Update for awstats has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1708665,2018-01-22 09:44:06 UTC,This bug was fixed in the package awstats - 7.4+dfsg-1ubuntu0.3
1708665,2017-09-18 12:10:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708665,2017-09-20 19:05:56 UTC,"I'd suggest /bin/sh, as that is the shell in the shebang line of the script."
1708668,2017-08-04 14:15:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/490885"
1708672,2018-05-11 15:33:35 UTC,This change was made by a bot.
1708674,2018-12-13 20:53:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708674,2018-12-14 19:32:42 UTC,"Correction:
1) futzing with /lib/systemd/system/haveged.service doesn't help
2) strace -f shows that haveged is indeed failing because it can't write to /var/run
3) adding the line suggested in the original post to /etc/apparmor.d/usr.sbin.haveged works"
1708674,2018-12-13 20:52:45 UTC,I verified that my 16.04 system has upstart-sysv installed and that /var/log/syslog contains
1708676,2017-08-04 17:29:39 UTC,"I have been bit by this on Xenial as well. However, it works on bare metal (Zesty). It could have something to do with the cloud images."
1708676,2017-08-07 15:17:48 UTC,This started working again for me today (on Xenial).
1708676,2017-08-14 17:33:09 UTC,"Thanks to Ian, who clued me into the issue. Juju isn't bubbling up underlying cloud-init issues. In this specific case, apt was locking up trying to install (no network connectivity). For those who may encounter this before this is surfaced into juju, ssh into the machine manually and look at the cloud-init logs."
1708676,2017-08-15 15:05:04 UTC,"I discovered that manually launching a container and ssh'ing into it using lxd I have network connectivity. For juju launched containers however, I do not. In addition, cloud-init shouldn't hang forever when attempting to install apt packages and apt fails (apt in this case doesn't seem to timeout)."
1708677,2017-08-04 15:10:08 UTC,"StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
 __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
 std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
 __cxxabiv1::__cxa_pure_virtual () at ../../../../src/libstdc++-v3/libsupc++/pure.cc:50
 usbguard::IPCServerPrivate::handleListDevices (this=0x55bcf1cba880, request=..., response=...) at src/Library/IPCServerPrivate.cpp:712"
1708677,2017-08-04 15:15:21 UTC,I just love ubuntu have always just windows
1708679,2017-08-04 15:39:36 UTC,"boot-resources read shows what's currently imported, but does not show what's in progress nor what's queued for download:"
1708679,2017-08-04 15:43:45 UTC,"If you use ""boot-resource read"" on each boot-resource you will get the information you are looking for. Queued images also show up in the list."
1708679,2017-08-04 15:51:46 UTC,This is a valid bug that needs addressing because:
1708679,2017-08-04 15:55:14 UTC,boot-resources read does list items that are both complete and incomplete:
1708679,2017-08-04 16:03:18 UTC,"@Andres,"
1708679,2019-09-19 11:53:36 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1708679,2019-09-25 08:04:27 UTC,"I can confirm that this is an issue, I'v also run into it from time to time. We might want to look into having code that detects that an image sync is stuck."
1708686,2018-11-29 14:19:27 UTC,"We are currently using local mirrors in most places which accelerates and lower the chance of getting an error but even these do fail from time to time, causing lots of build failures."
1708686,2018-11-29 14:20:15 UTC,Correction: https://review.openstack.org/#/c/620630/
1708692,2017-08-04 17:20:02 UTC,"The issue is quite clear. The VID and PID of the BT has to be added upstream.
Next week I will build a test module."
1708692,2017-08-04 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1708692,2017-08-08 11:09:02 UTC,"T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=03 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=13d3 ProdID=3494 Rev= 2.00
S: Manufacturer=Realtek
S: Product=Bluetooth Radio
S: SerialNumber=00e04c000001
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms"
1708692,2017-08-08 10:51:43 UTC,File transfers is a different issue. You can search or ask at AskUbuntu.
1708692,2017-08-07 18:40:38 UTC,"Installation went just fine....
After reboot I could connect my phone to the notebook.
But I can NOT transfer files between the two...don't know if this is related to the driver."
1708692,2017-08-08 11:15:16 UTC,"Hi Dmitry,"
1708692,2017-08-05 13:47:06 UTC,@Kai-Heng This is not a perfect way of testing for a regular user. The 4.13 kernel may break something like proprietary video drivers.
1708692,2017-08-05 13:31:57 UTC,"@Pilot6
Sure. I'll do it."
1708692,2017-08-05 11:28:04 UTC,"@Kai-Heng I am at a vacation and have a limited internet access. I
think it makes sense to make a test module fot Oliver to test and then
send a patch upstream if it works."
1708692,2017-08-05 11:02:03 UTC,apport-collect probably won't provide anymore information here.
1708692,2017-08-04 22:33:57 UTC,I did as requested (apport-collect)...needed to tweak python a bit before I got it running. Anyways...it launched the launchepad...I granted token...but I could not see if it actually worked (how is it indicated that the apport-collect made it...??) Thanks again!!
1708692,2017-08-07 13:54:53 UTC,So I built a test module. Install it by running:
1708699,2017-08-07 13:42:28 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086207.html
1708704,2018-09-18 18:29:27 UTC,"The issue with CentOS in case of mirror usage, it does not retries if it just have one mirror configured.
WORKAROUND: multiple mirror alias"
1708729,2017-08-04 19:35:02 UTC,"Ankit, please add platform info, OS and provisioning system used"
1708729,2017-08-04 19:46:59 UTC,"Review in progress for https://review.opencontrail.org/34317
Submitter: Ankit Chadha (<email address hidden>)"
1708729,2017-08-10 16:50:37 UTC,"Reviewed:  https://review.opencontrail.org/34317
Committed: http://github.com/Juniper/contrail-controller/commit/9c157cc893f1ed3f43a733386d484c849036772b
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1708735,2018-08-01 00:21:42 UTC,The failing tests:
1708740,2017-08-04 20:44:09 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1708740,2017-08-04 20:46:11 UTC,Mounting volumes while ignoring /etc/fstab is a security-related problem.
1708766,2017-08-04 23:32:21 UTC,Reported upstream @ https://github.com/mate-desktop/marco/issues/340
1708766,2017-08-04 23:19:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708766,2020-02-19 10:55:52 UTC,I can no longer reproduce this using MATE Desktop 1.24 (Marco 1.24.0) on Ubuntu MATE 20.04 daily.
1708768,2017-08-16 14:05:32 UTC,(I'm the author of the barbican charms)
1708768,2017-08-15 19:55:36 UTC,Confirming that currently encrypted volumes are not supported by the cinder or barbican charms. Barbican is required but the Barbican charm currently doesn't support integrating with cinder.
1708772,2017-08-20 13:31:59 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1708777,2017-09-08 14:40:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708777,2021-01-10 18:30:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1273027, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1708779,2019-07-17 13:28:08 UTC,Can you reproduce this with final release of buster?
1708779,2019-09-16 04:17:35 UTC,[Expired for Raspbian because there has been no activity for 60 days.]
1708785,2017-08-16 10:17:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708804,2018-02-11 03:07:13 UTC,This bug still remains in 17.10.
1708804,2018-08-18 20:38:29 UTC,"I can confirm that this happens with indicator-sound and notify-osd (or xfce4-notifyd), but not with xfce4-pulseaudio-plugin which does not send a notification when using its menu slider."
1708804,2019-02-05 01:15:41 UTC,That's not the case with me. In Xubuntu 18.04 the notification appears over PulseAudio Plugin as well.
1708805,2017-08-05 08:40:03 UTC,18.2 before the normal display
1708805,2017-08-05 08:37:29 UTC,"I am completely re-installed in the virtual machine system and numix, or the same"
1708811,2017-08-09 20:46:10 UTC,What release of Ubuntu did you test this on?
1708811,2017-08-09 21:00:46 UTC,Exactly what the title says: Ubuntu mainline 16.04.3
1708811,2017-08-09 21:24:04 UTC,Also the same drive works fine with a fat32 or ext4 filesystem.
1708811,2017-08-05 12:26:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1708822,2017-08-05 11:34:37 UTC,thank you
1708860,2020-12-29 22:19:50 UTC,"Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1708870,2019-01-08 21:07:14 UTC,"Good!  I had to subscribe to the bug to get apport-collect to work but obviously after doing so (and answering Yes to ""... really .. proceed?"" then ""Send report"") it did what it said."
1708870,2019-01-08 20:46:39 UTC,apport information
1708870,2019-01-08 20:46:36 UTC,apport information
1708870,2019-01-08 20:46:34 UTC,apport information
1708870,2019-01-08 20:46:33 UTC,apport information
1708870,2019-01-08 20:46:32 UTC,apport information
1708870,2019-01-08 20:46:30 UTC,apport information
1708870,2019-01-08 20:46:29 UTC,apport information
1708870,2019-01-08 20:46:27 UTC,apport information
1708870,2019-01-08 20:46:25 UTC,apport information
1708870,2019-01-08 20:46:23 UTC,apport information
1708870,2019-01-08 20:46:22 UTC,"AlsaDevices:
 total 0
 crw-rw----+ 1 root audio 116,  1 Jan  8 13:21 seq
 crw-rw----+ 1 root audio 116, 33 Jan  8 13:21 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=80757df8-19e5-4abd-9cec-f7106619f2b8
InstallationDate: Installed on 2019-01-08 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS ""Xenial Xerus"" - Release amd64 (20170801)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Supermicro Super Server
Package: linux (not installed)
PciMultimedia:"
1708870,2019-01-08 20:39:34 UTC,"I logged in using the elinks browser (since the system has no GUI), allowed the application to have access via my account and nothing apparent happened.  I did change the status to confirmed as requested above.  If I need to do something after allowing the application to have access then please provide the steps i need to take, thanks."
1708870,2019-01-08 20:35:15 UTC,I am also needing the updated driver for a firewall appliance.
1708870,2017-08-05 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1708870,2019-01-08 20:46:28 UTC,apport information
1708874,2017-11-14 12:22:39 UTC,"I have similar issue on Ubuntu 17.10(Ubuntu on Xorg), 4.10.0-37-generic running on:"
1708874,2018-09-15 14:13:10 UTC,the same thing happens with me.... wired mouse works in and but touchpad is incompatible i am on lenovo ideapad 330
1708874,2017-12-20 13:12:49 UTC,"I have a similar problem in Lenovo Ideapad 320 80YF0005BR. The touchpad doesn't hold left click to select text and right click isn't working either, but the pointer moves normally.
I'm using Ubuntu 16.04.2 LTS (MATE) Linux 4.4.0-59 i686 X.Org 1.18.4."
1708874,2017-10-31 11:40:54 UTC,"I think what is not problem of synaptic package, because evdev driver is using."
1708874,2017-12-22 11:59:38 UTC,I've fixed the issue installing the newest stable Kernel 4.14.8.
1708874,2017-10-13 01:19:28 UTC,/proc/bus/input/devices entry:
1708874,2017-10-13 01:14:39 UTC,"Similar issue on Ideapad 320 80YH, mine is working, but with strange behavior: the right click is triggering the left click function, and sometimes both clicks (left and right)."
1708874,2017-10-02 05:18:28 UTC,I also faced the same issue. Unable to use the touchpad (Lenovo Ideapad 320).
1708874,2017-08-19 13:00:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708874,2017-10-26 12:44:52 UTC,"I have the same, identical bug with the IdeaPad 320-15ABR (same of Ben i think, according with him hardware specs).
Ubuntu 17.10 and Linux 4.13.0-16-generic"
1708874,2017-08-05 20:25:21 UTC,I uploaded a video to YouTube showing what happens:
1708875,2017-08-16 09:45:24 UTC,Open /lib/udev/hwdb.d/60-keyboard.hwdb
1708875,2017-08-16 11:32:52 UTC,I deleted those two occurrences but it's not working.
1708875,2017-08-16 14:52:57 UTC,"It's typo.
Just find ""KEYBOARD_KEY_1a"" underneath ""evdev:name:ThinkPad Extra Buttons:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*"" and let it ""=mute""."
1708875,2017-08-16 16:53:54 UTC,Still not working after those edits. Did I do something wrong?
1708875,2017-08-17 05:49:19 UTC,Find the Lenovo section:
1708875,2017-08-17 07:43:34 UTC,"I am pretty sure I didn't do any mistake but the key is still not working. I will also attach an animation to show how volume mute produces a notification, and volume down/up as well. Just the mic doesn't trigger a notification, nor does it actually mute the mic (checked in the sound preferences)."
1708875,2017-08-17 08:14:38 UTC,Looks like MATE's mate-settings-daemon doesn't do anything to the hotkey [1].
1708875,2017-08-17 08:09:10 UTC,"I am sorry, I was totally wrong, I thought it's ""mute"" button instead of ""mic mute""."
1708875,2017-08-16 08:21:30 UTC,"Thanks, Kai-Heng!"
1708875,2017-08-17 08:51:02 UTC,"Thanks for your help on this, Kai!"
1708875,2017-08-17 09:11:05 UTC,Please forget my previous comment. Found the solution to restoring the file:
1708875,2017-08-17 09:16:28 UTC,"This should do:
$ sudo apt --reinstall install udev"
1708875,2020-10-10 11:21:03 UTC,Support for mic mute key was implemented in MATE 1.22
1708875,2017-08-17 07:44:45 UTC,Here is the animation. In the last seconds I am pressing the mic mute button but nothing happens.
1708875,2017-08-16 08:07:47 UTC,"Looks like it can mute:
P: /devices/platform/thinkpad_acpi/input/input9/event7
N: input/event7
S: input/by-path/platform-thinkpad_acpi-event
E: BACKSPACE=guess
E: DEVLINKS=/dev/input/by-path/platform-thinkpad_acpi-event
E: DEVNAME=/dev/input/event7
E: DEVPATH=/devices/platform/thinkpad_acpi/input/input9/event7
..
E: KEYBOARD_KEY_16=mute"
1708875,2017-08-16 07:34:21 UTC,apport information
1708875,2017-08-16 07:34:34 UTC,apport information
1708875,2017-08-15 23:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1708875,2017-08-16 07:34:18 UTC,apport information
1708875,2017-08-16 07:34:19 UTC,apport information
1708875,2017-08-16 07:34:22 UTC,apport information
1708875,2017-08-16 07:34:23 UTC,apport information
1708875,2017-08-16 07:34:24 UTC,apport information
1708875,2017-08-15 22:53:45 UTC,I can't reproduce this on my hardware. I believe Thinkpad require some tuning.
1708875,2017-08-16 07:34:24 UTC,apport information
1708875,2017-08-16 07:34:26 UTC,apport information
1708875,2017-08-16 07:34:27 UTC,apport information
1708875,2017-08-16 07:34:29 UTC,apport information
1708875,2017-08-16 07:34:30 UTC,apport information
1708875,2017-08-16 07:34:31 UTC,apport information
1708875,2017-08-16 07:34:33 UTC,apport information
1708875,2017-08-16 07:34:25 UTC,apport information
1708875,2017-08-16 07:35:12 UTC,"Hey Martin, I hope this helps. If anything else, please let me know!"
1708905,2017-08-06 08:20:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1708905,2017-08-06 16:30:43 UTC,I forgot to mention that my /etc/resolv.conf uses OpenDNS IP addresses for DNS lookups.  I don't think the DNS settings actually matter though due to the strange behavior caused by wildcard DNS.
1708912,2017-10-04 10:38:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708919,2020-12-15 09:17:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708922,2018-05-27 17:24:54 UTC,"Ok, I will do that."
1708922,2018-04-12 21:29:38 UTC,"If you can, please file a separate bug for uvcvideo with a stacktrace. Then
please link those bugs"
1708922,2018-04-12 13:52:53 UTC,"Looking at the stacktrace, this is coming from /usr/bin/cheese. Even with bad input from the driver (which seems like a valid issue to investigate and improve) - an error message is preferable to a SIGFPE as seen in the initial report."
1708922,2018-04-12 06:20:16 UTC,"Unfortunately I don't have the machine, so this requires the bug reporters to find out."
1708922,2018-04-11 08:00:58 UTC,No idea. Maybe vlc has some hacks to workaround buggy drivers?
1708922,2018-04-11 05:27:50 UTC,"I am not familiar in this area, but why does VLC work but not other Apps?"
1708922,2018-04-10 20:27:35 UTC,"I don't see how this is a bug in ffmpeg. The feature request linked in this bug report is asking for a workaround for a buggy kernel driver which will not fix the underlying issue, and isn't going to fix any other programs using the webcam anyway."
1708922,2017-11-06 21:48:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708922,2018-04-12 21:12:06 UTC,"Original reporter here. I am willing to assist wherever I can, but I
reported chiefly because I cannot debug or investigate of my own."
1708922,2017-08-14 15:24:39 UTC,"Here is my output from ffmpeg -f alsa -i default -f v4l2 -s 640x480 -i
/dev/video0 -acodec flac -vcodec libx264 output.mkv
ffmpeg version 3.3.3-1ubuntu1 Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 6.4.0 (Ubuntu 6.4.0-2ubuntu1) 20170724
  configuration: --prefix=/usr --extra-version=1ubuntu1
--toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu
--incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping
--enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa
--enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca
--enable-libcdio --enable-libflite --enable-libfontconfig
--enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm
--enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt
--enable-libopus --enable-libpulse --enable-librubberband --enable-libshine
--enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh
--enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx
--enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid
--enable-libzmq --enable-libzvbi --enable-omx --enable-openal
--enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libiec61883
--enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264
--enable-shared
  libavutil      55. 58.100 / 55. 58.100
  libavcodec     57. 89.100 / 57. 89.100
  libavformat    57. 71.100 / 57. 71.100
  libavdevice    57.  6.100 / 57.  6.100
  libavfilter     6. 82.100 /  6. 82.100
  libavresample   3.  5.  0 /  3.  5.  0
  libswscale      4.  6.100 /  4.  6.100
  libswresample   2.  7.100 /  2.  7.100
  libpostproc    54.  5.100 / 54.  5.100
Guessed Channel Layout for Input Stream #0.0 : stereo
Input #0, alsa, from 'default':
  Duration: N/A, start: 1502723857.171781, bitrate: 1536 kb/s
    Stream #0:0: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
[video4linux2,v4l2 @ 0x3ddca87320] Dequeued v4l2 buffer contains 32756
bytes, but 614400 were expected. Flags: 0x00012001.
Input #1, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, bitrate: 147456 kb/s
    Stream #1:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480,
147456 kb/s, 30 fps, 30 tbr, 1000k tbn, 1000k tbc
Stream mapping:
  Stream #1:0 -> #0:0 (rawvideo (native) -> h264 (libx264))
  Stream #0:0 -> #0:1 (pcm_s16le (native) -> flac (native))
Press [q] to stop, [?] for help
[video4linux2,v4l2 @ 0x3ddca87320] Dequeued v4l2 buffer contains 32534
bytes, but 614400 were expected. Flags: 0x00012001.
/dev/video0: Invalid data found when processing input
[alsa @ 0x3ddca6a520] Thread message queue blocking; consider raising the
thread_queue_size option (current value: 8)
frame=    0 fps=0.0 q=0.0 size=       0kB time=-577014:32:22.77 bitrate=
-0.0kbframe=    0 fps=0.0 q=0.0 size=       0kB time=-577014:32:22.77
bitrate=  -0.0kbframe=    0 fps=0.0 q=0.0 size=       0kB
time=-577014:32:22.77 bitrate=  -0.0kbframe=    0 fps=0.0 q=0.0 size=
 0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=    0 fps=0.0 q=0.0 size=
     0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=    0 fps=0.0 q=0.0
size=       0kB time=-577014:32:22.77 bitrate=  -0.0kbframe=    0 fps=0.0
q=0.0 size=       0kB time=-577014:32:22.77 b..."
1708922,2017-08-14 16:56:41 UTC,"Further information: ffmpeg stops after it detects broken frames, with
error messages like here:
https://superuser.com/questions/1048637/ffmpeg-video-recording-freezes-after-invalid-data-found-when-processing-input"
1708922,2017-08-06 10:42:36 UTC,"StacktraceTop:
 cheese_camera_set_new_caps (camera=0x561943bee460) at libcheese/cheese-camera.c:772
 cheese_camera_play (camera=0x561943bee460) at libcheese/cheese-camera.c:789
 cheese_camera_switch_camera_device (camera=<optimized out>) at libcheese/cheese-camera.c:714
 cheese_preferences_dialog_on_source_change (combo=0x561944509330, self=0x561944588320) at src/cheese-preferences.c:601
 _cheese_preferences_dialog_on_source_change_gtk_combo_box_changed (_sender=0x561944509330, self=0x561944588320) at src/cheese-preferences.c:613"
1708922,2017-08-11 06:19:14 UTC,Can you attach dmesg?
1708922,2017-08-11 06:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1708922,2017-08-13 15:25:47 UTC,"Okay, the error happens in avcodec_send_packet() or avcodec_receive_frame().
Needs to find out what ffmpeg did here..."
1708922,2017-08-12 13:31:02 UTC,Nothing suspicious. Why do you think it's a kernel bug?
1708922,2017-08-13 05:34:52 UTC,"I researched the issue some time ago. My webcam and several others like HP
are affected by a faulty driver for this webcam, which should be the kernel
uvcvideo module. This is the reason why it happens in several progs, like
guvcview and cheese."
1708922,2017-08-12 11:24:44 UTC,Here it is:
1708922,2017-08-13 15:17:09 UTC,So which kernel module does VLC use?
1708929,2020-08-11 07:18:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708933,2017-09-18 09:01:24 UTC,"I'm seeing the same bug, same gnome-online-accounts version but on 17.04. First time running Online Accounts I was presented with a Microsoft option. I signed in (and I also have a non-standard Live account meaning it's not outlook.com or hotmail.com), seemed successful, I turned off e-mail but left documents on. The account seemed to add but I couldn't find the documents anywhere. Now when I go back into Online Accounts I'm only given three options for accounts to add: Facebook, Flickr, and Google. The Microsoft account doesn't appear. I tried to uninstall completely and install (just the gnome-online-accounts applet) and it still shows the same. Is there a way to remove the configuration and start completely over? I can't even seem to get to that point."
1708933,2017-08-07 16:27:35 UTC,"I cannot reproduce this bug with gnome-online-accounts 3.24.1-0ubuntu1 on artful, which is the same version that you are running."
1708933,2017-08-07 20:58:04 UTC,"Right, good suggestion.  That reveals the error:"
1708935,2017-08-06 14:36:00 UTC,The folders are created so they can be previewed in the download subfolders in the destination panel. They are deleted at program exit if not downloaded to.
1708935,2017-08-07 06:07:21 UTC,"I have just double checked, is not the case. Attached you can find some screenshots to illustrate the problem, I downloaded only one picture with date 06/08/2017 (DD/MM/YYYY) but since on the SD card there are some pictures from the 02/08/2017 the folder 02_Test is created, with inside an empty folder called RAW."
1708935,2017-08-12 03:09:26 UTC,"Hi Fioravanti,"
1708938,2017-08-06 15:58:05 UTC,Here's a trivial patch that makes sure the macro is called unconditionally.
1708938,2017-08-06 16:21:29 UTC,"The attachment ""0001-configure-Fix-HAVE_VALGRIND-not-being-defined-when-t.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1708947,2017-08-14 13:40:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708947,2017-10-03 15:06:34 UTC,From what I can tell DLFCN has been dropped from Python 3.6.
1708955,2017-08-08 12:36:18 UTC,"Dell have uploaded the BIOS update now, please close."
1708969,2017-08-07 19:53:59 UTC,"It seems that LastSearchFiletype type=""string"">0</LastSearchFiletype won't be saved and it will be stuck on the last file type you have used before this issue was introduced. It seems to work in 3.31."
1708971,2018-02-23 14:07:52 UTC,I can confirm the bug. I'm not able to install ceres via packages.
1708971,2017-08-16 16:55:03 UTC,"SRU:
[Impact]"
1708971,2018-02-23 14:09:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708972,2017-08-07 00:20:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1708974,2017-08-11 07:13:52 UTC,Same for me. Good wish
1708974,2017-08-08 15:01:06 UTC,"Yes, I'd like this feature too."
1708974,2020-10-24 15:22:55 UTC,"Is it possible to make that delay configurable ?
Got a transfer that took 4 days to display in my other account.
Maybe just a ""config file"" parmeter, if you think that this is a too specific need."
1708974,2019-05-31 20:58:21 UTC,let's go for 2 then
1708974,2019-05-15 03:49:08 UTC,"Hmm, I'm not sure... some transfers have just a 1 day gap."
1708974,2019-03-28 22:50:57 UTC,"working on this.
Question: does a fixed day gap of 2 (or more but max=5) would suit ?"
1708974,2019-01-02 18:00:30 UTC,"Hello Maxime, I have the same situation when the tranfers occur between accounts of mine held at different banks, so there is always one or two days of delay unfortunately.."
1708974,2017-08-08 23:39:03 UTC,Same for me. This and automatic assignment of transfers are my most wanted features and currently are dealbreakers for me to use just homebank.
1708974,2017-11-04 14:21:51 UTC,"Maxime, I treat any transfer from any of my accounts at the several banks that I use in the same way, they are just a *transfer*. But as has been said before there seems to be a delay in processing credit card transactions by one or two days. I also have a two day delay with an account from which I draw an income so regardless of the intended use of ""Internal transfer"" I think your users have two needs:"
1708974,2017-08-11 19:30:58 UTC,"Agreed, I found this wish while checking if it was already mentioned before making it myself."
1708974,2017-10-21 09:28:40 UTC,"Hey guys,"
1708974,2017-12-16 09:40:50 UTC,"OK, I still need to think a good way of doing this, as to find potential linked txn homabnk uses guess what: same date and amount in its criteria, so maybe a solution would be to introduce a decay for date.
At last as the usage can be within different institution, as the account are supposed to be of the same owner, I should disable and empty the payee filed for that."
1708974,2017-11-03 18:24:54 UTC,"Maybe what is the need here is to do something similar but for normal transfer (and keet internal the way it is, or maybe merge this).
I think about enable to have a linked txn, and when you edit the SRC txn you are prompted what to sync to DST one.
What do you think ?"
1708974,2017-10-21 09:54:57 UTC,"Maxime, you're right I didn't read the docs!"
1708980,2019-07-19 04:14:11 UTC,The link is working now: https://forge.puppet.com/openstack/nova/dependencies
1708988,2017-08-09 06:23:10 UTC,we should fix the error in horizon.
1708988,2017-08-09 06:22:33 UTC,"It is not this way. the call stack trace is showing very clear.
the ns_db.get_ns is working well."
1708988,2017-08-07 13:28:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491490"
1708988,2018-03-17 02:47:43 UTC,"Does this still exist on queens? Or, can we move it to rocky?"
1708988,2017-08-10 00:56:14 UTC,"But in ns_db.get_ns, self._get_resource call the nfvo_db._get_resource, the nfvo_db._get_resource doesn't process the issubclass(model, NS), it just raise."
1708995,2017-08-07 13:38:32 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086246.html
1709019,2017-10-27 15:01:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709021,2018-03-05 08:24:17 UTC,you mean that it's status should not change to 'error' in that case ?
1709023,2017-08-22 13:03:24 UTC,All patches are merged.
1709023,2017-08-16 11:55:47 UTC,"Thank you, Vladyslav."
1709023,2017-08-16 09:11:54 UTC,"Hey Alexander, sorry for the delay. Yes, we have discussed this, the patches are +2'd."
1709023,2017-09-06 18:07:08 UTC,Verified on 9.0-2017-09-01 snapshot
1709023,2017-08-07 09:55:16 UTC,"Yes, I think so. I'll propose these downstream and see what other folks from nova team think about these."
1709023,2017-08-07 09:41:16 UTC,"As far as I understand, these patches will never be merged in upstream due to Mitaka lifecycle phase. Can we take them directly to downstream?"
1709023,2017-08-07 09:23:37 UTC,"Yes, that should fix the problem, there are abandoned patches on review, namely https://review.openstack.org/329421, https://review.openstack.org/329425 and https://review.openstack.org/329422"
1709023,2017-08-07 09:09:02 UTC,"Upstream LP bug that is probably related:
https://bugs.launchpad.net/nova/+bug/1405533"
1709023,2017-08-16 06:35:01 UTC,"Vladyslav,"
1709023,2017-08-07 07:57:56 UTC,sla2 for 9.0-updates
1709026,2018-08-22 13:42:39 UTC,This issue was fixed in the openstack/heat-agents 1.7.0 release.
1709026,2018-03-26 18:50:28 UTC,"As far as I can tell it's not any non-ASCII character, it's any sequence of bytes that are not valid UTF-8. That's the only way I've been able to reproduce the UnicodeDecodeError reported in the commit message of the patch (https://review.openstack.org/491395)."
1709032,2017-08-22 14:22:15 UTC,"Hi @libosvar,"
1709032,2017-08-17 15:30:32 UTC,"Xenial kernel 4.4.0-92.115 had a quick fix for the issue, which was to revert the patch that introduced the regression (""netfilter: synproxy: fix conntrackd interaction""). The kernel build that's in -proposed (currently 4.4.0-93.116) reapplies this patch and applies on top the proper fix found upstream (""netfilter: nf_ct_ext: fix possible panic after nf_ct_extend_unregister"")."
1709032,2017-08-15 09:00:32 UTC,This bug was fixed in the package linux - 4.4.0-92.115
1709032,2017-08-11 09:30:31 UTC,"I cherry-picked 9c3f3794 to Ubuntu-4.4.0-89.112 tag and built the kernel and I'm able to create a conntrack entry without any issues or traces, so it *does* fix the issue. I assume what I had is the same as what Joseph provided :) Thanks for helping us out guys!"
1709032,2017-08-10 16:12:39 UTC,I built a xenial test kernel with a pick of commit 9c3f379492 and WITHOUT commit 2ad4caea651 reverted.
1709032,2017-08-10 15:33:02 UTC,I'll build a Xenial test kernel with the commit Jay mentioned in comment #16 and post it shortly.
1709032,2017-08-10 15:24:19 UTC,"Just to confirm, the revert did fix the bug as posted in comment #15?"
1709032,2017-08-10 09:51:04 UTC,"Are you sure 9c3f3794 fixes it? I'm not a kernel expert but since the backtrace differs and, according to the commit message, I'd say it's a different issue.
We could try backporting it manually and check but maybe reverting 2ad4caea651 suffices until
ubuntu guys fix the bug in a future tag?"
1709032,2017-08-10 09:43:15 UTC,Is it possible to backport the patch to 4.4.0 kernel in Xenial LTS version?
1709032,2017-08-09 21:34:08 UTC,The panic appears to be fixed upstream via:
1709032,2017-08-29 08:51:07 UTC,We enabled back our failing CI tests after switching to kernel 4.4.0-92.115 and everything went back to normal. Current 4.4.0-93.116 works just fine too. Thanks a lot for a quick help! I think you can close this bug as resolved :)
1709032,2017-08-16 16:33:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1709032,2017-08-09 19:14:39 UTC,"Thanks Joseph, I tested both, creating a conntrack entry using conntrack CLI and running the Neutron functional tests, both are fine with the revert."
1709032,2017-08-09 14:21:05 UTC,"New kernel Ubuntu-4.4.0-89.112HEADUbuntu-4.4.0-89.112master was
tagged 9 days ago (07/31/2017) [0]."
1709032,2017-08-09 16:21:14 UTC,Re-confirmed - I see the same regression in behaviour between -81 -> -89 using the test case in #11.
1709032,2017-08-07 09:02:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/491403"
1709032,2017-08-07 09:04:49 UTC,Maybe it's a problem with ovsdb again: http://logs.openstack.org/14/488914/8/check/gate-neutron-dsvm-functional-ubuntu-xenial/75d7482/logs/openvswitch/ovsdb-server.txt.gz
1709032,2017-08-07 09:08:27 UTC,"Change abandoned by Jakub Libosvar (<email address hidden>) on branch: master
Review: https://review.openstack.org/491403
Reason: It's communication with ovsdb getting stuck"
1709032,2017-08-07 10:00:10 UTC,"On mobile at the moment so I can't easily find it, but there was a recent change to that kernel detection for the ovs compile from source script. I would confirm that didn't mess up what got compiled."
1709032,2017-08-07 11:55:41 UTC,We don't use that in functional tests. We compile kernel module only for fullstack.
1709032,2017-08-09 18:11:17 UTC,I built a test kernel with a revert of commit	2ad4caea651.  The test kernel can be downloaded from:
1709032,2017-08-07 13:30:16 UTC,"Change abandoned by Jakub Libosvar (<email address hidden>) on branch: master
Review: https://review.openstack.org/491403"
1709032,2017-08-09 09:21:45 UTC,"With enormous help of Daniel Alvarez, we were able to root cause analyse this issue. We merged functional tests using conntrack [1] and then later Ubuntu kernel at the gate was bumped from 4.4.0-87.110 to 4.4.0-89.112. The newer kernel contains a bug in conntrack and all conntrack calls get stuck, the process can't be even killed by sending a SIGKILL signal."
1709032,2017-08-09 09:31:39 UTC,[1] https://review.openstack.org/#/c/470911/
1709032,2017-08-09 09:36:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/492068"
1709032,2017-08-07 11:56:22 UTC,Also worth to note that this issue is not reproducible on Ocata branch.
1709032,2017-08-09 12:45:22 UTC,The reproducer is following:
1709040,2017-09-25 11:30:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/507064"
1709040,2017-09-26 10:12:20 UTC,"Reviewed:  https://review.openstack.org/507064
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=596f73814a0ac174f81292625f96e1b200df3294
Submitter: Jenkins
Branch:    master"
1709040,2017-08-16 15:46:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/494247"
1709040,2017-08-29 08:08:46 UTC,"Reviewed:  https://review.openstack.org/494247
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=eea8229c9c3bb567201a81230af569b7f5ac8838
Submitter: Jenkins
Branch:    master"
1709040,2017-08-16 10:43:36 UTC,Adding requirement to this bug: A fullstack test that verifies the DB API of the chosen implementation.
1709053,2017-08-16 23:49:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709053,2020-08-17 18:34:43 UTC,Fixed via mate-notifications-daemon 1.24.1-0ubuntu1 in Ubuntu Groovy.
1709055,2017-08-08 07:00:41 UTC,"Ok, fair enough, let's handle the trust store case in another round later"
1709055,2017-08-07 11:09:25 UTC,"Thanks for working on that. Before I look more at it/sponsor, is there any reason you didn't drop the trust store support? Some of the changes are required by the snappy patch but that doesn't require the module so we could at least remove the corresponding deb from debian/control right?"
1709055,2017-08-07 10:09:51 UTC,Here's the patch
1709055,2017-08-08 01:51:44 UTC,"I don't know anything about the details. I just kept what appeared to be required by snappy support (wouldn't build without it). Also, this patch is what I have been testing for the past week, so if there's more that can be removed I suggest we do that separately. To change the patch now would impact its theoretical maturity and set us back a week."
1709060,2019-10-08 13:12:47 UTC,"snapcraft version - 3.8
core18
python3"
1709060,2019-10-08 18:27:08 UTC,"I've created a minimal example to reproduce the bug:
https://github.com/randomchars42/snap_python_tkinter_skeleton"
1709067,2017-08-07 12:05:48 UTC,This happens very rarely but i have to change directory and it gets sorted out.
1709073,2017-08-07 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1709073,2017-08-07 13:13:04 UTC,"apport-collect does not work after triggering the issue, and I have included the relevant kernel traces anyway. => confirmed"
1709073,2017-09-01 08:25:52 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1709073,2017-09-01 09:02:06 UTC,"no longer have the test hardware to verify the kernel in -proposed, but I did verify that the commit in question fixes the problem (hence my report ;))."
1709073,2017-09-18 09:21:44 UTC,This bug was fixed in the package linux - 4.10.0-35.39
1709101,2017-08-07 14:55:52 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086267.html
1709104,2017-08-07 16:24:41 UTC,"I'm not sure this is a neutron issue then.  Without an IPv4 address you won't be able to communicate with the metadata IP, barring some translation or other mechanism."
1709104,2017-08-07 16:16:22 UTC,In this case we are using config-drive as the 169.254.169.254 address can not be reached.
1709104,2017-08-07 15:59:24 UTC,"There is no metadata support over IPv6, so I wouldn't expect this to work, you should be using config drive in this scenario."
1709104,2017-08-08 14:04:00 UTC,"Would it be worth considering when deploying an IPv6 only network that an IPv4 link local configuration is also enabled (as though deploying a dual stack network), simply to allow communication with the metadata service to record the encrypted Windows password without forcing users to create a dual stack network themselves?"
1709104,2017-08-11 21:05:55 UTC,"I'm confused by the last comment.  If there's only an IPv6 subnet configured Neutron can't force an IPv4 subnet also be configured, or do it behind the tenant's back, some could feel that's a security issue as they didn't explicitly configure it."
1709118,2017-09-21 18:03:25 UTC,It's possible https://review.openstack.org/#/c/500956/ will help with this.
1709118,2019-06-11 21:21:40 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/664703"
1709118,2019-06-11 21:22:37 UTC,"If https://review.opendev.org/664703 works, we can close this bug."
1709118,2019-06-12 18:46:26 UTC,"Change abandoned by Eric Fried (<email address hidden>) on branch: master
Review: https://review.opendev.org/664703
Reason: Okay, we're not ready for this."
1709118,2019-10-07 16:22:57 UTC,"> It's possible https://review.openstack.org/#/c/500956/ will help with this.
"
1709118,2019-10-07 16:24:21 UTC,"BTW, https://review.opendev.org/#/c/524316/ took advantage of the ksa fix and removed the workaround for this bug."
1709118,2019-10-08 04:57:38 UTC,"Reviewed:  https://review.opendev.org/524316
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5601c82915a2d745ee600a4ca4c0e7215206dbb6
Submitter: Zuul
Branch:    master"
1709122,2017-08-12 20:20:20 UTC,https://git.launchpad.net/ltsp-manager/commit/?id=5adebdc72590efc75ed46df6c376ceac65486bbd
1709124,2017-08-09 18:04:36 UTC,please forward the issue upstream!
1709124,2017-08-07 16:43:04 UTC,"StacktraceTop:
 MediumLock::Unlock (this=this@entry=0x700071) at /build/virtualbox-2umW4l/virtualbox-5.1.26-dfsg/src/VBox/Main/src-server/MediumLock.cpp:143
 MediumLockList::Unlock (this=this@entry=0x7faedc0008c0) at /build/virtualbox-2umW4l/virtualbox-5.1.26-dfsg/src/VBox/Main/src-server/MediumLock.cpp:261
 MediumLockList::Unlock (this=0x7faedc0008c0, this@entry=0x0) at /build/virtualbox-2umW4l/virtualbox-5.1.26-dfsg/src/VBox/Main/src-server/MediumLock.cpp:254
 MediumLockList::Clear (this=this@entry=0x7faedc0008c0) at /build/virtualbox-2umW4l/virtualbox-5.1.26-dfsg/src/VBox/Main/src-server/MediumLock.cpp:210
 MediumLockList::~MediumLockList (this=0x7faedc0008c0, __in_chrg=<optimized out>) at /build/virtualbox-2umW4l/virtualbox-5.1.26-dfsg/src/VBox/Main/src-server/MediumLock.cpp:164"
1709126,2017-08-07 17:15:40 UTC,"Mainline commit 892d1fa ""tty: Destroy ldisc instance on hangup"" (circa v4.6) appears to fix this issue, per positive test feedback in LP: #1707089.  Additional prerequisite patches are required:"
1709126,2017-08-16 16:33:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1709126,2017-08-18 20:11:39 UTC,"Waiving the verification-needed-xenial, since this was originally reported against linux-lts-xenial (no known xenial test installation exists).  Will ask the original reporter to re-verify the fix in linux-lts-xenial."
1709126,2017-08-28 10:14:02 UTC,This bug was fixed in the package linux - 4.4.0-93.116
1709126,2017-08-28 10:18:07 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-93.116~14.04.1
1709126,2018-01-10 04:16:22 UTC,"I just upgraded to kernel 4.4 108, and got a similar kernel panic. Is there a regression to this fix?"
1709145,2019-08-04 08:03:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709149,2017-11-16 00:13:46 UTC,SetSelected() is not sufficient. It looks like we'll need to expose some of the GAL selection APIs to Python.
1709149,2019-06-04 02:24:36 UTC,FWIW this still doesn't appear to work on KiCAD 5 stable
1709149,2019-06-05 13:13:29 UTC,The 5 branch is no longer supported.  Please upgrade to 5.1.2 which is the latest stable release.  I suspect that this may have already been fixed.
1709149,2019-06-08 18:32:08 UTC,"OK, got all my versions straight again (ubuntu distro update disabled PPAs...) and this is still an issue."
1709149,2017-08-07 22:51:01 UTC,"Hi Greg,"
1709149,2017-08-08 00:00:53 UTC,"Tom, OpenGL does seem to recognize. When I switch to default view, then back to OpenGL, the selected items display as selected (brighter than non selected items)."
1709155,2018-08-04 14:09:10 UTC,"Got the same bug on Linux 4.18rc6, which is obviously not an outdated kernel."
1709155,2018-08-04 15:12:17 UTC,In my opinion the title of the bug is misleading.
1709155,2018-08-05 14:50:07 UTC,"the title is perfectly fine, this bug is about printing a proper error instead of a cryptic readlinkat() message when there is a kernel in use that lacks the necessary features (which a proper ubuntu kernel provides) for snapd to operate correctly. in case there will be 4.18 ubuntu supported kernels (i.e. in 18.10) they will work and not print this error. it is not depending on a version (you'D likely also see it if you'd build 4.2 mainline with upstreams defconfig or some such)."
1709155,2018-08-06 06:43:03 UTC,Hmm... I see.
1709155,2018-08-11 05:32:26 UTC,"I have the same problem. I would use canonical livepatch, but I get this error also."
1709155,2018-08-06 08:12:57 UTC,"It's always bee the case that a properly configured kernel is needed for snapd to work. There even have been features added, and bugs fixed, in the kernel as a direct result of needing features working for snapd (and in those cases the Ubuntu kernel has often shipped the patches before they were upstream, and in fact there might be still patches that need upstreaming; for example I'm not sure if the fix for https://bugzilla.kernel.org/show_bug.cgi?id=195453 has been picked up or not)."
1709155,2018-08-11 06:37:15 UTC,Found this thread about Apparmor confioguration changes to support kernel 4.18. Give it a try: https://forum.snapcraft.io/t/custom-kernel-error-on-readlinkat-in-mount-namespace/6097/18
1709155,2018-08-18 02:39:51 UTC,Now you can just `sudo snap refresh core --beta` for the 4.18 problem (tested on 4.18.2 aarch64 from the mainline ppa).
1709155,2018-08-18 18:42:34 UTC,Thanks. 'sudo snap refresh core --beta' worked. Kernel 4.18.3 64bit
1709155,2018-08-03 08:15:35 UTC,Am I the only one really affected by this bug?
1709155,2018-07-30 11:28:20 UTC,Is there any idea or plan when this will be resolved?
1709155,2018-07-17 13:09:39 UTC,I see the same log when trying to start KeePassXC: cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied.
1709155,2018-07-25 12:08:58 UTC,Do you mean something like this?
1709155,2018-07-25 11:18:50 UTC,"For people seeing the ""cannot perform readlinkat() on the mount namespace file descriptor of the init process"", are there any security denials in journald at the time of the error?"
1709155,2018-07-25 08:24:31 UTC,Effecting 4.18.0-041800rc6-generic
1709155,2018-07-18 09:09:49 UTC,"So it's not because the kernel is too old, but because it is too new :-\."
1709155,2018-07-18 09:07:26 UTC,Same with nextcloud-client.
1709155,2018-07-16 20:27:56 UTC,"Same problem:
4.18.0-041800rc1-generic"
1709155,2018-07-15 06:48:07 UTC,I can confirm this is affecting mainline 4.18.0-rc4.
1709155,2018-07-10 16:55:09 UTC,"I'm also encountering
cannot perform readlinkat() on the mount namespace file descriptor of the init process"
1709155,2018-06-24 21:01:07 UTC,Having this problem on 4.18.0-041800rc1-generic
1709155,2018-02-22 19:43:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709155,2018-02-11 23:47:18 UTC,"It was the same error with kernel 3.13.0-95-generic.  Once I updated to 4.4.0-112-generic, the snap works."
1709155,2018-07-25 18:05:45 UTC,"Yes, that's exactly it."
1709159,2020-05-11 06:31:52 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1709159,2017-08-15 01:40:20 UTC,I just changed my video card to a Radeon RX 560 using the open source driver and the same problem exists.
1709159,2017-12-23 15:10:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709160,2017-08-07 19:15:52 UTC,"This is split off from bug 1693851. While I've set this one's importance to wishlist, I think it could also be considered an outright bug."
1709162,2018-01-20 08:02:27 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1465
1709166,2017-09-29 14:37:36 UTC,This bug was fixed in the package ubiquity - 17.10.8
1709166,2017-09-08 19:56:38 UTC,"Thanks Jeremy - proposed to remove Flash wording from Ubiquity.  ubiquity-slideshow-ubuntu just shows AFAICT that Adobe Flash is ""supported software"" so that can stay."
1709166,2017-09-07 02:46:59 UTC,"I did the install today and got both vaapi, fluendo mp3, and -ugly - maybe you got Flash installed and got the old restricted one?"
1709166,2017-08-18 15:13:03 UTC,Will update the description to reflect this modified patch. I believe it's ready now.
1709166,2017-09-07 02:32:00 UTC,"Released, but not working!?"
1709166,2017-08-30 20:29:03 UTC,"Indeed, I've been advised to leave Fluendo on.  Thanks!"
1709166,2017-08-30 10:18:33 UTC,"Hey Bryan! The debdiff looks good. But as per Sebastien's post on the mailing thread, could you maybe take a closer look into why we actually pulled in gstreamer1.0-fluendo-mp3 in the first place (when it got added)? I'd also like to be extra sure we're not breaking any workflow by accident."
1709166,2017-08-18 15:02:47 UTC,"Agreed with the fluendo plugin, just removed it from my machine and mp3 plays fine.  Will redo the debediff with that and the Lubuntu changes"
1709166,2017-09-07 02:41:23 UTC,My concern is now logged as bug 1715527
1709166,2017-08-18 14:38:46 UTC,"I would say to also drop gstreamer1.0-fluendo-mp3.
MP3 decoding is done by the mpg123 plug-in in gstreamer1.0-plugins-ugly, which depends on libmpg123-0.
https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-ugly-plugins/html/gst-plugins-ugly-plugins-plugin-mpg123.html
I don't know whether Fluendo (the company) still maintains gstreamer1.0-fluendo-mp3 or not. On the other hand, I can see that mpg123 is actively maintained."
1709166,2017-08-07 20:13:20 UTC,Dropped the MSFT fonts as I noted the warning about consulting a lawyer before adding items to addons.
1709166,2017-08-18 14:38:59 UTC,"The dependency chain for pulling in video acceleration drivers is:
gstreamer1.0-vaapi depends on libva1
libva1 recommends va-driver-all
va-driver-all depends on i965-va-driver mesa-va-drivers vdpau-va-driver"
1709166,2017-08-07 20:20:37 UTC,Got poked that I should offer making similar changes for the Kubuntu/Lubuntu-restricted-addons packages at the same time.  Happy to add other changes to the debdiff if requested too.  Thanks!  (Remove your team and accept my apologies if this wasn't the right way to approach this)
1709166,2017-08-08 12:26:50 UTC,"The attachment ""ubuntu-restricted-addons_25.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1709166,2017-08-09 09:42:26 UTC,"Bryan,"
1709166,2017-09-06 02:23:33 UTC,Thank you for helping to make Ubuntu better. I have uploaded this to Ubuntu now. I apologize for the delay.
1709166,2017-08-10 02:04:13 UTC,"Thanks, that's probably fine then."
1709166,2017-08-09 13:33:41 UTC,"@daniel
gstreamer1.0-libav or gstreamer1.0-vaapi will bring it in (via recommends).  I just did the current restricted-addons during the install and it brings it in (both va-driver-all and vdpau-driver-all actually)."
1709166,2017-08-10 02:23:13 UTC,"Yup, fresh install w/ restricted done yesterday does include i965-va-driver.  Can't test actual acceleration though as I'm doing this in a VM."
1709166,2017-08-15 21:14:40 UTC,Lubuntu devs (tsimonq2 and wxl) +1ed removing Flash.
1709185,2017-08-08 00:44:06 UTC,at somepoint it might be worth it to produce a minimally viable test case against eventlet.wsgi.server and send it upstream to see what temoto thinks
1709194,2019-04-04 14:11:16 UTC,The issue should be fixed in Disco now
1709194,2019-01-31 10:04:12 UTC,Upstream commited a fix for that now
1709194,2017-08-09 14:01:14 UTC,Discussed it a bit with upstream and reported on https://bugzilla.gnome.org/show_bug.cgi?id=786052
1709194,2018-11-08 15:00:10 UTC,"Upstream is working on fixing that issue now, discussions on https://gitlab.gnome.org/GNOME/gnome-shell/issues/726"
1709194,2017-08-09 13:11:25 UTC,"If I leave it alone when the notification appears, it does indeed suspend successfully. That's not my concern in this bug. I'm more looking at the notification with no idea what it actually means. The fact I had to run some dbus monitor utility to find that out says it's not a very good notification :)"
1709194,2017-08-09 12:49:16 UTC,So your computer does not automatically suspend when locked?
1709194,2017-08-09 12:01:07 UTC,Go it
1709194,2017-08-09 11:15:41 UTC,"Thank you for your bug report, could you run that on a command line
$ dbus-monitor interface='org.freedesktop.Notifications' > gsdpower.log"
1709194,2017-08-09 13:55:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1709194,2017-08-09 13:54:52 UTC,"""Computer will suspend very soon because of inactivity."" comes from gnome-settings-daemon so reassigning."
1709202,2018-09-09 06:49:24 UTC,This has been tackled and fixed in the release for 18.04 in https://git.launchpad.net/~ltsp-manager/ltsp-manager/commit/?id=db275f94b7919b30cda38e5550e8053a8ecdbb89
1709227,2017-08-08 02:55:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491653"
1709228,2017-08-08 04:29:58 UTC,TEST
1709228,2018-05-11 15:33:41 UTC,This change was made by a bot.
1709228,2021-01-07 04:05:15 UTC,4.10 EOL
1709236,2017-08-09 06:56:29 UTC,"Hi, Sylvain,
The whole log for nova is in the attachment.
We checked the Nova API versions, 2.33 works well, 2.34 failed. So it should be related to the modification you mentioned.
Thank you very much."
1709236,2017-08-10 14:16:19 UTC,Putting back the new state since we now have the logs and that issue could be sensitive.
1709236,2017-08-08 14:11:57 UTC,"Looks like the compute service provides the exception, but you only give us the conductor one. Could you please provide the nova-compute.log that returns this exception so we can verify which decorated RPC method returns this ?"
1709236,2017-08-08 04:53:50 UTC,"stack@DevStackOSDomU:~$ nova instance-action-list 04f7d20b-7c47-4c81-b7bc-e601f6db1870
+----------------+------------------------------------------+---------+----------------------------+

| Action         | Request_ID                               | Message | Start_Time                 |


+----------------+------------------------------------------+---------+----------------------------+

| create         | req-31b8da65-2e44-4475-a4b0-bb3655b0305a | -       | 2017-07-27T02:10:21.000000 |
| live-migration | req-54635c3c-dc43-4244-a0d6-c1da0d68c19c | -       | 2017-07-27T02:13:22.000000 |


+----------------+------------------------------------------+---------+----------------------------+"
1709236,2017-08-08 06:17:44 UTC,"According to Jianghua's testing, the live migration would be failed in current CI test. The default nova API version is 2.1. The reason is same with the logs in the description.
He also tested other nova APIs. version 2.1 and 2.27 failed while version 2.0 and version 2.53 work well."
1709236,2017-08-08 05:28:23 UTC,"I did a test with V2.27 and the latest version V2.53.
The live-migration works well with V2.27 but failed with V2.53 with the same error reported by Naichuan:"
1709236,2017-08-08 04:54:24 UTC,"Seems this issue doesn't exist with nova API2.0.
So a workaround to verify other change is to force it to use API2.0: export OS_COMPUTE_API_VERSION=2.0"
1709236,2017-08-08 06:20:35 UTC,"Sorry, the nova API version 2.0 and 2.27 work well, 2.1 and 2.53 would fail."
1709238,2017-08-09 10:04:07 UTC,"Hi hongbin,"
1709238,2017-08-21 11:36:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/495825"
1709239,2017-08-15 22:39:26 UTC,"Have to test this behavior.  According to miker in IRC, this is ""normal"" cause the page will try to find the specific cs-cz and not finding that, drop down to cs and find that."
1709239,2017-08-16 15:03:28 UTC,"Well, specifically, the nls files are showing the normal Dojo behavior.  Dojo will look for cs-cz, and if it gets a 404, it will look for just cs.  It causes log noise, but it's working as designed (for better or worse)."
1709239,2017-08-27 13:25:58 UTC,"Thank you, Ben and Mike, for taking a look at this!"
1709256,2018-03-11 10:47:50 UTC,Isn't this related to Wayland security feature?
1709256,2018-03-11 08:39:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709256,2017-08-12 09:10:04 UTC,"Will do some more testing and if necessary, report it to GIMP."
1709256,2017-08-09 04:27:58 UTC,Where should I address this best in an attempt to restore it?
1709256,2017-08-08 20:51:30 UTC,"IINM, GNOME2 did offered ""Clipboard management"" via ""gnome-settings-daemon"" package. I believe GNOME2 to MATE transition somehow lost this default behavior."
1709256,2017-08-08 14:42:51 UTC,Thanks for testing and reproducing!
1709256,2017-08-09 11:43:49 UTC,"Indeed, MATE does have msd-clipboard-manager as a plugin of mate-settings-daemon. And looking at dconf editor, org.mate.SettingsDaemon.plugins.clipboard is active by default."
1709256,2017-08-08 13:45:00 UTC,"With this steps I could reproduce on Ubuntu MATE 16.04. So, I could imagine that this issue might be considered a security feature."
1709260,2018-09-25 23:09:55 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605261"
1709260,2018-09-25 23:21:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/605267"
1709260,2018-09-25 23:25:33 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/605269"
1709260,2018-09-28 05:26:54 UTC,"Reviewed:  https://review.openstack.org/604906
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8e2de668434861b87495e0a0f715b2f90d8ec05
Submitter: Zuul
Branch:    master"
1709260,2018-09-29 02:13:46 UTC,"Reviewed:  https://review.openstack.org/605261
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c72bb2c747016b22e71109b9750d5899b776e67a
Submitter: Zuul
Branch:    stable/rocky"
1709260,2018-10-08 21:50:42 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1709260,2018-10-08 20:53:29 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1709260,2018-09-24 20:49:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604906"
1709260,2018-10-24 22:35:52 UTC,"Reviewed:  https://review.openstack.org/605269
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0bd38dbadcaeef59213e5471018649f7a9d2d9bf
Submitter: Zuul
Branch:    stable/pike"
1709260,2018-12-19 10:04:50 UTC,This issue was fixed in the openstack/nova 16.1.7 release.
1709260,2019-03-22 03:47:20 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1709260,2018-10-01 21:44:28 UTC,"Reviewed:  https://review.openstack.org/605267
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=22197f3d0156b9fb87a132e77ab44dbdd63bc826
Submitter: Zuul
Branch:    stable/queens"
1709260,2018-09-24 20:36:33 UTC,"Note the change is being reverted https://review.openstack.org/#/c/604898/ due to it causing a regression, see bug 1793747."
1709260,2017-08-08 10:58:08 UTC,"Hi Sylvain,"
1709260,2018-09-24 14:46:45 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1709260,2017-08-08 09:08:57 UTC,"For clarity on the bug report, could you please provide the nova-sceduler log that shows the filter missing that host because the name is different ?"
1709260,2017-08-08 11:34:52 UTC,I think it is the problem of inconsistent behavior between mysql DB and the in-memory cache in the nova scheduler.
1709260,2017-08-08 12:09:33 UTC,Please find the attached n-sch logs for more information.
1709260,2018-09-24 14:47:11 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1709260,2017-08-28 07:04:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/498334"
1709260,2018-07-09 12:58:27 UTC,"For the record, MySQL *does* support case-sensitive matching. It's just not the default."
1709260,2017-08-10 09:25:52 UTC,related bug https://bugs.launchpad.net/nova/+bug/1538011
1709260,2018-07-24 12:19:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/585334"
1709260,2018-07-24 12:19:21 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/585335"
1709260,2018-07-24 12:24:13 UTC,"Reviewed:  https://review.openstack.org/498334
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0dc0db932e3ad5ad911f2072015cb9854f6e4e23
Submitter: Zuul
Branch:    master"
1709260,2018-07-28 15:18:46 UTC,"Reviewed:  https://review.openstack.org/585334
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2caf8f65e414732fb1ef1ac32a5884a48af6655d
Submitter: Zuul
Branch:    stable/queens"
1709260,2018-07-30 16:08:17 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1709260,2018-07-30 17:55:06 UTC,"Reviewed:  https://review.openstack.org/585335
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8f5fbd83de3759407b8f928159067211af156d60
Submitter: Zuul
Branch:    stable/pike"
1709260,2018-07-09 13:03:01 UTC,"According to https://github.com/openstack/nova/blob/c0350da4a1607d7aa113caceaefb5d29303c7eed/nova/db/sqlalchemy/api_models.py#L53, there is no character set specified for the aggregate_hosts.host field (and there is no default in the oslo_db.sqlalchemy.models.ModelBase class) so the default character set will be latin1_swedish_ci."
1709261,2017-08-11 04:12:23 UTC,"Hrm, in my GNOME shell, it says ""Backups is ready"" to let you know that deja-dup has requested attention, but isn't stealing it.  We actively try to avoid the bug you're describing, actually."
1709261,2017-08-11 12:45:22 UTC,"I don't think so, the only extensions enabled are Gpaste and Openweather"
1709261,2020-08-24 22:31:22 UTC,"Yup, can confirm this does not happen on X, but does happen on wayland."
1709261,2020-08-26 00:48:25 UTC,"Landed a fix that stops showing the hidden windows (and thus stealing focus) and instead shows a notification. Besides not working on Wayland today, the old way of showing a window without stealing focus won't work on Gtk4 at all."
1709269,2017-08-10 00:06:05 UTC,Why this happen to me?? Please help
1709273,2019-04-13 08:25:09 UTC,"I saw this one was still open. The statuses available however do not include anything like solved, not change necessary. Maybe one of the developers can change the status (I may not see all the statuses possible)."
1709273,2017-08-08 09:50:23 UTC,Attaching config file.
1709273,2017-08-08 17:02:31 UTC,Try disabling (comment out) 37-39 and see if you get your powerline. Pretty sure that vte.sh is overriding your sourced powerline.
1709273,2017-08-08 20:48:44 UTC,You are completely right. Thank you for the advice. Problem solved (I will leave closing the issue to you). Thanks.
1709279,2017-08-08 11:35:05 UTC,The issue here is attachments for 'server_volume' change after 'server_volume_attachment' resource is created.
1709279,2017-08-08 16:23:05 UTC,"I tried the following:
- change the 'bootstrap' resource definition (see below) and recreate a stack.
---
  bootstrap:
    type: OS::Heat::SoftwareDeployment
    depends_on: server_volume_attachment
    properties:
      name: 01_bootstrap
      config:
        get_resource: bootstrap_script
---"
1709279,2017-08-09 04:22:43 UTC,Looks like the issue exists in master too. Will have a look.
1709279,2017-08-10 03:17:08 UTC,"It seems we keep the referenced attributes of a resource in node_data/stack_defn immediately after the resource is created/updated. Hence any changes to it afterwards is not accounted for when the resource with the referenced attribute is created/updated . I suggested the user an workaround for this, by splitting the template into two."
1709283,2017-08-08 17:49:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491871"
1709293,2017-08-18 11:29:59 UTC,"3.13.0-129.178~precise1 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1709293,2017-08-29 10:31:28 UTC,The package has been published and the bug is being set to Fix Released
1709308,2017-09-05 07:43:25 UTC,This bug has been addressed in https://review.openstack.org/#/c/491780/. We can set the status to fix committed.
1709312,2017-08-28 23:50:47 UTC,Juju does not support IPv6 yet.
1709312,2019-10-01 06:46:38 UTC,"Still biting us. Would be nice to at least just add a secgroup to allow connections from '::/0', so Ipv6Ranges and CidrIpv6 in addition to IpRanges and CidrIp."
1709312,2019-11-22 08:17:51 UTC,"At the moment, we're using the AWS CLI to work around this. The commands are:"
1709312,2020-03-17 08:38:56 UTC,"Ran into this issue again today when adding some additional apache units into aws, this would be a nice feature to have."
1709319,2017-11-15 01:07:03 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1709319,2017-08-24 06:33:54 UTC,"Reviewed:  https://review.openstack.org/495814
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bcf110fe7ca2d989a956303313f413614e7a6548
Submitter: Jenkins
Branch:    stable/ocata"
1709319,2017-08-11 12:26:52 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc1 release candidate.
1709319,2017-08-10 18:25:39 UTC,"Reviewed:  https://review.openstack.org/491822
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=376a902cabd548f1bcc7f7f7f8f98bd2dfa87c89
Submitter: Jenkins
Branch:    master"
1709319,2017-08-08 14:21:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491822"
1709319,2017-08-21 10:34:54 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/495814"
1709323,2017-08-08 17:07:12 UTC,idempotent_id will stay the same for a test method but not for a test case which is defined using a fully qualified test name.
1709326,2018-05-11 15:33:48 UTC,This change was made by a bot.
1709331,2020-10-23 13:56:05 UTC,"Marking as invalid for juju-deployer, as we'd use native juju bundles for this now"
1709331,2017-08-16 18:10:05 UTC,"As discussed over irc, I believe this bug https://bugs.launchpad.net/juju/+bug/1642868 is related to this situation, the sequence of events (as I interpret them from the logs)"
1709331,2017-08-16 18:02:38 UTC,"See also, related:  https://bugs.launchpad.net/juju/+bug/1642868"
1709331,2017-08-16 18:00:27 UTC,A bit prettier output from comment #3 is here:
1709331,2017-08-16 17:07:19 UTC,"Unfortunately, 600s is also not enough time, which leads me to believe there may be a Juju core bug in terimate-application when a unit is in error state, or a bug in bundletester's reset/terminate implementation."
1709331,2017-08-16 16:52:33 UTC,FYI There is a batch of changes which is already underway to raise the ceiling on the bundletester default timeout (180s) to 600s.
1709331,2017-08-16 17:46:58 UTC,"It turns out Bundletester reset: True is a requirement, because the previous deployment will not be torn down if it is False.  If we set it True, then after trusty-icehouse, the trusty-liberty run will go on top of an existing trusty-icehouse model, and we can't have that.  So, I set reset: True back on that WIP patchset."
1709331,2017-08-16 15:51:59 UTC,This timeout threshold has been raised and landed in keystone master as of https://review.openstack.org/#/c/492265/.
1709337,2017-08-10 15:04:22 UTC,This bug was introduced in rev 344d7f981a4d7d1ef7d8f8d7645aa9c1d153b6cf of www.project-moonshot.org:/srv/git/mech_eap.git (aka moonshot/moonshot). I've reproduced it on Centos7 and Debian. The common factor is that it happens when we fall back to using the .gss-eap-id file for identities.
1709337,2017-08-09 07:37:34 UTC,Yes.
1709337,2017-08-09 12:20:04 UTC,"No, scratch that: I may have received the same ""unknown CA"" message in
the freeradius logs, but that was apparently for an auth request that
succeeded anyway. (In which case, ""unknown CA"" may have been more of a
warning than an error -- at least in my case.)  I'll look into it more
when I get into the office."
1709337,2017-08-09 11:54:35 UTC,"Thanks, Stefan. Unfortunately, I'm not able to get the VM to boot up.
I'm running VB 5.1.22. I've found that snapshots can be problematic even
between VB point releases. Would it be a problem for you to delete the
snapshot, and then export the VM as an appliance?"
1709337,2017-08-08 22:17:06 UTC,Is this the same image that you just emailed me a link to on another thread?
1709337,2017-08-08 21:03:31 UTC,"Correction to above: I meant to write that older versions of Freeradius don't play nicely with TLSv1.2. I'm not sure whether it works with TLSv1.1. But in any case, the newer mech_eap library insists on using TLSv1.2."
1709337,2017-08-08 21:33:28 UTC,"The system in question (a test system for our macOS team) uses FR 3.0.15. Default setup with only our required changes at this point. It was set up from the CentOS 6.9 LiveDVD, updated to the latest of *everything*. I will post a link to the image (privately) if that's helpful."
1709337,2017-08-08 20:21:30 UTC,"> When used with the newest moonshot-ui package (see Bug 1709316) in a mode that uses .gss_eap_id, RADIUS reports a TLS failure:
"
1709337,2017-08-08 20:40:49 UTC,"Hi, Stefan,"
1709337,2017-08-08 15:58:19 UTC,"Stefan, thanks for the bug report.  I'll get Dan to look at this after he finishes with But 1709316."
1709342,2020-09-19 09:57:12 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1709342,2018-06-03 14:05:26 UTC,"phiscribe, where would you have looked to find this info about the units.xml file?"
1709342,2018-06-02 01:09:51 UTC,"Happy feet, then :) (but we really need to document this, Eduard is right)"
1709342,2018-06-02 00:44:17 UTC,"Hachmann, I missed this till just today. I will do that."
1709342,2018-04-03 16:22:34 UTC,(capitalization may be different)
1709342,2018-04-03 16:22:11 UTC,@phiscribe You can put it in yourself :)
1709342,2017-08-08 17:19:12 UTC,"Hi Bruce,"
1709342,2017-08-09 17:55:34 UTC,I agree with Mc.
1709342,2017-08-08 18:06:47 UTC,found the file at /usr/share/inkscape/ui/units.xml
1709342,2017-08-08 18:09:55 UTC,AWESOME!
1709342,2017-08-08 18:16:02 UTC,the normal way is to choose the item called Invalid underneath the Status column
1709342,2018-04-03 15:31:51 UTC,I can live with inches.  It's easy to do 12xnumberxin.  I just am a hard core keep metric out of my head USA type.  Put ft back in.  I can not be reasoned with.
1709342,2017-08-09 11:36:06 UTC,"Despite this being marked invalid, I see merit in restoring m and ft to the GUI in release versions. Inkscape is being widely used beyond the scope of SVG as a web format, as the OP demonstrates."
1709342,2017-08-08 18:59:33 UTC,thanks for the information.  Another bug gone!
1709342,2017-08-09 17:45:18 UTC,"What may be done is better document the process of how to add/modify units, but I don't think it would be good to restore non-svg units to a release version"
1709344,2019-08-09 03:44:18 UTC,"This was handled in:
https://review.opendev.org/#/c/580535/"
1709346,2017-08-28 01:08:48 UTC,This issue was fixed in the openstack/openstack-ansible 14.2.8 release.
1709346,2017-08-28 00:58:23 UTC,This issue was fixed in the openstack/openstack-ansible 15.1.8 release.
1709346,2017-08-25 19:21:16 UTC,Also confirmed on my cinder-backup host. Sent a SIGHUP and did not observe any unusual CPU impact.
1709346,2017-08-25 19:10:31 UTC,Curious too on the above as I have a running setup where I sent SIGHUP to the cinder-scheduler service and I was not able to reproduce this behavior.
1709346,2017-08-18 07:57:14 UTC,This issue was fixed in the openstack/openstack-ansible 16.0.0.0rc1 release candidate.
1709346,2017-08-25 19:09:11 UTC,"Would it be possible to add a sleep to the ansible script before sending the SIGHUP. Investigating now, but a good suspicion raised was that it may be sending the signal before all the services are fully up and ready for it."
1709346,2017-08-15 00:48:41 UTC,"Reviewed:  https://review.openstack.org/491550
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=7b39cbaa4f1f3254b7969ad9e8c8cb1ec506301a
Submitter: Jenkins
Branch:    master"
1709346,2017-08-14 18:30:27 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/493639"
1709346,2017-08-14 18:30:15 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/493638"
1709346,2017-08-14 15:52:31 UTC,workaround proposed and being tested - https://review.openstack.org/#/c/491550/
1709346,2017-08-14 13:22:00 UTC,"Not that this will be super helpful, but strace on the 100% cinder-sched process shows this just reoccurring constantly:"
1709346,2017-08-09 20:31:20 UTC,Triggered at the point where SIGHUP is called.
1709346,2017-08-15 09:35:52 UTC,"Reviewed:  https://review.openstack.org/493638
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=045c4c5601a7f1d2e63303c7420e9fd518704c4b
Submitter: Jenkins
Branch:    stable/ocata"
1709346,2017-08-15 09:35:45 UTC,"Reviewed:  https://review.openstack.org/493639
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=191155546c655131222bf1ac7c0101b7eae5d840
Submitter: Jenkins
Branch:    stable/newton"
1709360,2017-08-08 15:56:43 UTC,"eller% strace ../apparmor_parser --debug --base /tmp/aa-caching-_5sxbkdo --skip-kernel-load -M ./features_files/features.all --cache-loc /tmp/aa-caching-_5sxbkdo/aa-alt-cache8eia9fdh --write-cache -r /tmp/aa-caching-_5sxbkdo/sbin.pingy
execve(""../apparmor_parser"", [""../apparmor_parser"", ""--debug"", ""--base"", ""/tmp/aa-caching-_5sxbkdo"", ""--skip-kernel-load"", ""-M"", ""./features_files/features.all"", ""--cache-loc"", ""/tmp/aa-caching-_5sxbkdo/aa-alt-""..., ""--write-cache"", ""-r"", ""/tmp/aa-caching-_5sxbkdo/sbin.pi""...], [/* 18 vars */]) = 0
brk(NULL)                               = 0xaab9436000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffebe05000
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
access(""/etc/ld.so.preload"", R_OK)      = -1 ENOENT (No such file or directory)
open(""/etc/ld.so.cache"", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=15753, ...}) = 0
mmap(NULL, 15753, PROT_READ, MAP_PRIVATE, 3, 0) = 0xffebe01000
close(3)                                = 0
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
open(""/lib/mips64el-linux-gnuabi64/libpthread.so.0"", O_RDONLY|O_CLOEXEC) = 3
read(3, ""\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\10\0\1\0\0\0\360\204\0\0\0\0\0\0""..., 832) = 832
lseek(3, 8944, SEEK_SET)                = 8944
read(3, ""\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\257\374\36\345\304\3317$\252{-7u(9\330""..., 36) = 36
lseek(3, 9608, SEEK_SET)                = 9608
read(3, ""\4\0\0\0\20\0\0\0\1\0\0\0GNU\0\0\0\0\0\3\0\0\0\2\0\0\0\0\0\0\0"", 32) = 32
fstat(3, {st_mode=S_IFREG|0755, st_size=169816, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffebdff000
mmap(NULL, 206600, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xffebda1000
mprotect(0xffebdbf000, 61440, PROT_NONE) = 0
mmap(0xffebdce000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1d000) = 0xffebdce000
mmap(0xffebdd0000, 14088, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xffebdd0000
close(3)                                = 0
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
open(""/lib/mips64el-linux-gnuabi64/libm.so.6"", O_RDONLY|O_CLOEXEC) = 3
read(3, ""\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\10\0\1\0\0\0\200\262\0\0\0\0\0\0""..., 832) = 832
lseek(3, 19016, SEEK_SET)               = 19016
read(3, ""\4\0\0\0\24\0\0\0\3\0\0\0GNU\0-0\327W\10\270`\223m\214\204\374!\237W\236""..., 36) = 36
lseek(3, 19648, SEEK_SET)               = 19648
read(3, ""\4\0\0\0\20\0\0\0\1\0\0\0GNU\0\0\0\0\0\3\0\0\0\2\0\0\0\0\0\0\0"", 32) = 32
fstat(3, {st_mode=S_IFREG|0644, st_size=849872, ...}) = 0
mmap(NULL, 895920, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xffebcc6000
mprotect(0xffebd90000, 61440, PROT_NONE) = 0
mmap(0xffebd9f000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc9000) = 0xffebd9f000
close(3)                                = 0
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
open(""/lib/mips64el-linux-gnuabi64/libc.so.6"", O_RDONLY|O_CLOEXEC) = 3
read(3, ""\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\10\0\1\0\0\0\230\310\3\..."
1709360,2017-08-08 16:17:41 UTC,A quick observation is that the strace output doesn't show any syscalls failing with -EOPNOTSUPP.
1709360,2017-08-08 16:48:41 UTC,Built the library with --enable-debug-output and set LIBAPPARMOR_DEBUG=1:
1709360,2017-08-08 17:08:16 UTC,Thanks for rebuilding with debug output! Could you apply this patch and then rebuild once again with debug output? Then run the command by hand and include the output? Thank you!
1709360,2017-11-01 22:11:29 UTC,This turned out to be a miscompilation bug in the mips64el toolchain and not a bug in AppArmor.
1709364,2018-01-24 22:26:09 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1438
1709370,2017-08-15 10:21:08 UTC,newton only fix so removing pike milestone
1709370,2017-08-14 03:39:52 UTC,"Reviewed:  https://review.openstack.org/491847
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3f1a33666a9a5a960c79cd3142dc77c73cd7e506
Submitter: Jenkins
Branch:    stable/newton"
1709370,2017-09-04 18:17:02 UTC,This issue was fixed in the openstack/tripleo-heat-templates 5.3.1 release.
1709370,2017-08-08 16:16:26 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/491847"
1709384,2018-03-22 19:48:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709384,2018-03-22 22:07:27 UTC,• disable pam_systemd in the pam session config
1709384,2018-03-22 22:12:30 UTC,"an NFS filesystem which is in use, should not cause failure to shutdown, this part of the bug report is valid."
1709384,2017-08-30 04:09:51 UTC,i've figured out at least part of this issue.
1709399,2017-08-09 13:37:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709399,2018-07-07 14:08:51 UTC,"Current llvm-toolchain-* packages do have versioned symbols (since 3.8.1-22 / 3.9.1-8 / 4.0-5: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849098), but this 3.8 has not been backported."
1709399,2018-07-07 19:18:35 UTC,"It seems that this could have been backported by now, the ticket has been open for (almost) a year now ..."
1709407,2020-07-10 07:45:58 UTC,https://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-6706.html
1709416,2018-07-11 12:01:27 UTC,Isn't this ~solved by bug #1754405?
1709416,2017-08-09 17:04:40 UTC,"> arbitrary PRs shouldn't produce snaps that are trusted by snapd the same as official builds.
"
1709416,2017-08-09 01:21:55 UTC,"This isn't quite as simple as letting LP build arbitrary code to arbitrary branches. We need to consider how the store should handle the uploads in terms of assertions etc., as arbitrary PRs shouldn't produce snaps that are trusted by snapd the same as official builds."
1709416,2017-08-09 17:12:53 UTC,I guess what I'm saying is: we already have risk levels and branches to convey how much something should be trusted. Why invent something new? Developers can utilize those mechanisms how they see fit.
1709441,2017-08-08 18:28:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491881"
1709441,2018-02-02 14:24:26 UTC,"Change abandoned by James Slagle (<email address hidden>) on branch: master
Review: https://review.openstack.org/491881"
1709441,2019-02-19 13:43:23 UTC,Is this still an issue?
1709442,2019-11-23 16:54:38 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1709442,2020-01-23 04:19:21 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1709461,2017-08-08 18:55:36 UTC,"StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x7f5fe688a1b7 ""m_handle == NULL"", file=file@entry=0x7f5fe6889058 ""src/libieee1394/IsoHandlerManager.cpp"", line=line@entry=1795, function=function@entry=0x7f5fe688ada0 ""bool IsoHandlerManager::IsoHandler::enable(int)"") at assert.c:92
 __GI___assert_fail (assertion=0x7f5fe688a1b7 ""m_handle == NULL"", file=0x7f5fe6889058 ""src/libieee1394/IsoHandlerManager.cpp"", line=1795, function=0x7f5fe688ada0 ""bool IsoHandlerManager::IsoHandler::enable(int)"") at assert.c:101
 IsoHandlerManager::IsoHandler::enable(int) () from /tmp/apport_sandbox_3_Bb6j/usr/lib/libffado.so.2
 IsoHandlerManager::IsoHandler::updateState() () from /tmp/apport_sandbox_3_Bb6j/usr/lib/libffado.so.2
 IsoHandlerManager::IsoTask::updateShadowMapHelper() () from /tmp/apport_sandbox_3_Bb6j/usr/lib/libffado.so.2"
1709470,2017-08-09 07:40:25 UTC,"You must insert the time with a colon separator, e.g. 7:25, and not with a period separator, e.g. 7.25."
1709473,2018-05-19 01:21:11 UTC,"I forgot to mention, the issue I'm referring to is on enfuse"
1709473,2018-04-12 08:47:29 UTC,"Carl,"
1709473,2018-05-19 01:19:09 UTC,"I'm also affected by this issue.
If I can help by providing some data just let me know.
In my case, the colored dots show up on very bright areas of the sky."
1709473,2018-04-04 19:10:40 UTC,I think I'm also affected by this bug:
1709474,2019-05-13 16:55:20 UTC,Goutham was this talked about as a wish list item in PTG Denver 2019?
1709474,2019-05-13 21:41:30 UTC,"Hi Jason,"
1709487,2017-11-14 19:06:03 UTC,Fixed in 0.8.4
1709493,2017-08-08 23:26:43 UTC,"Indeed, clearer error message would be helpful here."
1709496,2017-08-09 13:44:14 UTC,"- thank you for taking the time to issue a report.
- could you indicate, specifically, which extension you are using?
- also, the current version of Inkscape is 0.92.2, so there may have been some menu changes since your version, see:
https://inkscape.org/en/release/0.92.2/"
1709501,2020-04-13 11:17:33 UTC,Had this bug when playing around changing colours and desktop layouts on a fresh install daily image 2020-04-13 which should have this fix but I experienced the bug.
1709501,2017-08-09 00:11:45 UTC,"StacktraceTop:
 g_type_check_instance_cast (type_instance=type_instance@entry=0x55a1bd13ea60, iface_type=94153151557488) at ../../../../gobject/gtype.c:4057
 brisk_apps_backend_reload (self=0x55a1bd13ea60, self@entry=<error reading variable: value has been optimized out>) at src/backend/apps/apps-backend.c:245
 g_timeout_dispatch (source=0x55a1bd4c1f00, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4629
 g_main_dispatch (context=0x55a1bceedf20) at ../../../../glib/gmain.c:3148
 g_main_context_dispatch (context=context@entry=0x55a1bceedf20) at ../../../../glib/gmain.c:3813"
1709501,2020-04-09 23:49:00 UTC,This was fixed via brisk-menu 0.5.0-1 in Bionic.
1709501,2017-10-14 20:26:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709536,2017-09-07 20:34:21 UTC,"Thanks for uploading the fix for this bug report to -proposed.  However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process.  You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential.  Thanks in advance!"
1709536,2017-09-15 04:55:53 UTC,Artful was fixed in systemd 234-2ubuntu2 - Ignore failures to set Nice priority on services in containers.
1709536,2017-08-31 16:25:15 UTC,"All charms using snaps are currently failing, so I'm looking forward to a snapd release with the commented out Nice. The alternative is adding the systemd override workaround to the snap layer and making everyone rebuild and republish their charms."
1709536,2017-10-23 12:13:02 UTC,This bug was fixed in the package systemd - 229-4ubuntu20
1709536,2017-09-19 16:13:41 UTC,I've confirmed that snapd with Nice=-5 will start with the updated systemd.
1709536,2017-10-23 12:13:30 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1709536,2017-09-19 15:24:01 UTC,"Hello Stéphane, or anyone else affected,"
1709536,2017-08-31 15:46:36 UTC,"As a workaround, you can override the snapd systemd unit with:"
1709536,2017-08-18 09:45:26 UTC,this is in snapd since may https://github.com/snapcore/snapd/pull/3270 why did this break all of a sudden ?
1709536,2017-08-31 08:49:08 UTC,Is there any workaround available other than switching to privileged containers?
1709536,2017-08-31 14:47:06 UTC,@xnox
1709536,2017-08-09 06:01:24 UTC,Added an Ubuntu systemd task.
1709536,2017-08-09 06:01:54 UTC,This bug affects anyone currently running ubuntu-core inside a LXD container as the current stable core snap is affected by this problem.
1709536,2017-08-14 10:25:01 UTC,"commit 5b8e457f8d883fc6f55d33d46b3474926a495d29
Author: Dimitri John Ledkov <email address hidden>
Date:   Tue Aug 1 18:51:20 2017 +0100"
1709536,2017-08-14 10:25:59 UTC,Is SRU of this fix to e.g. xenial's systemd desired?
1709536,2017-08-18 10:53:06 UTC,We can disable it for now: https://github.com/snapcore/snapd/pull/3763
1709536,2017-08-21 12:37:51 UTC,"That was not useful at all @ogra @mvo
As on the 18th systemd migrated that can set Nice in artful.... yet you disabled it on the 18th."
1709536,2017-08-30 20:09:40 UTC,"So I'm confused, wasn't the SRU supposed to have been fixed for this?"
1709536,2017-08-14 15:39:13 UTC,"Yeah, xenial is where most of the snapd users are for us, so that'd certainly be desired.
We wouldn't need trusty though as snapd doesn't work inside trusty containers."
1709537,2017-08-09 06:09:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/491995"
1709537,2017-10-31 08:45:14 UTC,"Change abandoned by jiamin (<email address hidden>) on branch: master
Review: https://review.openstack.org/491995
Reason: Peng have created another patch, https://review.openstack.org/#/c/516551/"
1709549,2017-08-10 07:15:42 UTC,cannot quite understand.
1709549,2017-08-10 10:40:30 UTC,"Sorry, I will try to be more precise."
1709549,2017-11-12 10:03:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519069"
1709550,2017-08-10 02:12:11 UTC,"This is a bug in the nova-lxd driver code, which manages bugs through some other launchpad project."
1709550,2017-09-05 08:27:37 UTC,Tricky one this as the main nova driver has no knowledge of the nova-lxd driver (and as a result can interrogate the LXD daemon to figure things out).
1709550,2017-09-05 08:28:45 UTC,"I'm marking this as Triaged and Low; I'm not sure how much we can realistically do being and out-of-tree driver, but this at least leaves a bug trail for anyone else tripping over this problem."
1709562,2017-10-06 12:52:06 UTC,"Another way to do this:
1. Install GNOME Tweaks (gnome-tweak-tool)
2. Open the Tweaks app
3. Switch to the Keyboard & Mouse panel
4. Click Additional Layout Options
5. Use the ""Switching to another layout"" section"
1709562,2018-12-12 15:39:09 UTC,"Thank you for your bug report, that has been resquested upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/290"
1709562,2017-10-06 11:54:45 UTC,Found a workaround for this bug:
1709577,2017-08-09 10:12:29 UTC,"Add patch link:
    https://review.openstack.org/#/c/492080/"
1709577,2017-08-31 08:32:21 UTC,Patch https://review.openstack.org/#/c/492080/ had been merged into master.
1709577,2017-09-06 08:29:05 UTC,This issue was fixed in the openstack-infra/shade 1.23.0 release.
1709577,2018-01-16 14:52:53 UTC,This issue was fixed in the openstack/python-openstacksdk 0.10.0 release.
1709593,2017-08-10 09:27:29 UTC,"After some tests and a look at the code, it is actually"
1709594,2017-08-11 16:00:25 UTC,Was there a reason that we needed this change?
1709594,2017-08-11 15:49:40 UTC,"Reviewed:  https://review.openstack.org/493006
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=904c4a1d9ac25119bb3100a349e19fef8d318527
Submitter: Jenkins
Branch:    master"
1709594,2018-03-20 06:17:32 UTC,"This bug is expected to be resolved after we complete this BP:
https://blueprints.launchpad.net/nova/+spec/live-migration-in-xapi-pool"
1709594,2017-08-11 18:37:43 UTC,"Matt,
 Understood. It works well after switching to singleconductor mode.
 R.g.t. I85047d44e388c89938f80ad8be1724bd11ed0225
 Live migration without block migration requires the source and destination hosts are on the same shared storage. For xenapi driver, the implement in the above commit is to check the shared storage basing on aggregate.
 See the spec: https://specs.openstack.org/openstack/nova-specs/specs/mitaka/implemented/making_live_migration_api_friendly.html#the-detection-of-block-migration"
1709594,2017-08-11 13:47:22 UTC,"> Matt thanks for your analysis and suggestions. It works well if we put the api_database in /etc/nova/nova_cell1.conf to allow local conductor accessing API database.
"
1709594,2017-08-10 05:25:58 UTC,"Matt, thanks for the comments."
1709594,2017-08-11 11:44:02 UTC,Matt thanks for your analysis and suggestions. It works well if we put the api_database in /etc/nova/nova_cell1.conf to allow local conductor accessing API database.
1709594,2017-08-11 13:25:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/493006"
1709594,2017-08-09 10:52:55 UTC,"I have no idea why the connection is None when trying to query AggregateList:
  rpc.server aggregate_list = objects.AggregateList.get_by_host(context, CONF.host)"
1709594,2017-08-10 02:09:31 UTC,Is this a devstack configuration? I'm assuming running in superconductor mode (the default)? That is set on the CELLSV2_SETUP variable in stackrc.
1709594,2017-08-10 05:36:06 UTC,"I tried to print the stack in enginefacade.py.
Checking source code:
  https://github.com/openstack/oslo.db/blob/master/oslo_db/sqlalchemy/enginefacade.py#L471
  conf.register_opts(options.database_opts, 'database')"
1709594,2017-08-10 15:26:45 UTC,"That's your nova.conf, but what about the nova-cpu.conf? That's not going to have the [api_database]/connection set, and that's probably your issue. The AggregateList.get_by_host code is looking up aggregates in the API database, and there is no connection set in the context for that, it's an up-call from the compute service, which is running isolated in the cell, to the API DB, and that's blocked in super-conductor mode."
1709594,2017-08-09 11:00:02 UTC,"At line:https://github.com/openstack/oslo.db/blob/master/oslo_db/sqlalchemy/enginefacade.py#L471
it will load the database section. The connection option loaded is None for the above test. But the configuration in the nova*.conf seems correct. And other attempts connecting database, it can get the correct connection also."
1709603,2017-08-09 11:46:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709603,2017-08-09 12:47:46 UTC,Some IRC discussion on this: https://irclogs.ubuntu.com/2017/08/09/%23ubuntu-devel.html#t11:32
1709603,2018-04-06 09:07:51 UTC,Alternate:
1709603,2018-06-06 18:56:58 UTC,"Just a comment...
'apt' indicates that its cli is unstable and should not be relied upon by scripts.
So fixing this general problem in 'apt' (and not apt-get) means you fix it possibly for humans who are typing things, but all non-human package installations needlessly have to 'apt-get update'. :-("
1709603,2019-08-27 15:44:47 UTC,"Ideally, `apt-get` could behave like a `dnf`, updating caches on `update` after some expiration period."
1709603,2019-08-27 15:54:20 UTC,"Huge anti-feature of dnf IMO, always totally confusing me when I'm on an RPM system."
1709605,2018-09-04 09:05:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709607,2017-08-09 12:04:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492112"
1709607,2017-08-11 09:09:47 UTC,Here is a stack trace:
1709607,2017-08-11 09:14:14 UTC,"The version of mongodb I'm using is Percona MongoDB 3.0.10-1.5. The extra ""-"" breaks the parsing."
1709614,2017-08-09 18:49:19 UTC,Waiting to see if issue is due to controller & analyticsdb being on same node
1709614,2017-08-09 19:01:56 UTC,keystone endpoints were not configured correctly due a ceilometer issue. issue has been fixed by https://review.opencontrail.org/34360 check-in and is available in build #17 (change #51).
1709616,2017-10-24 15:36:47 UTC,The commits were merged to the upstream stable 4.13 kernel - see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/log/?h=v4.13&ofs=2100
1709616,2017-08-22 08:37:56 UTC,@jsalisbury Where can I see that the two commits were cc'd to upstream stable? How soon can we expect to see these commits in a normal zesty update (educated guess)?
1709616,2017-08-11 17:04:04 UTC,It looks like both the commits mentioned were cc'd to upstream stable.  They should make their way into Ubuntu through the normal stable update process.
1709616,2017-08-15 20:11:53 UTC,Two things:
1709616,2017-08-09 12:30:07 UTC,This change was made by a bot.
1709616,2017-08-20 20:24:04 UTC,see also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711951
1709621,2017-08-09 22:07:35 UTC,This bug was fixed in the package gnome-online-accounts - 3.25.90-0ubuntu1
1709643,2017-08-14 15:17:57 UTC,Hi JC.
1709643,2017-08-14 16:01:41 UTC,"I did more playing since reporting this, and discovered that, as @Phill finds, setting it to very large values does work. It's tricky: in traditional typography typefaces and their leading are described like ""30/36pt"", but modern apps such as Word would regard this as font size ""30pt"" and line spacing ""1.2"" or ""6pt"" after paragraph.  So, perhaps it's more of a comment on the need for the documentation to reflect this, and the default settings when making a new Theme are more sensible. Currently they are ""Size 40pt"" and ""Line Spacing 0pt""."
1709655,2017-10-20 14:35:22 UTC,"Hi.  Could you indicate whether it was migrate or resize that caused the error, and if any other commands worked.  It looks like pylxd is failing to get a client connection to lxd as part of the error (about half way up), and so it's not clear if it's the migration or resize that's failing or something a bit more fundamental."
1709660,2018-08-10 02:57:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709668,2017-11-13 22:20:24 UTC,I am also having the same issue with Ubuntu 17.10. Any solution?
1709668,2017-11-13 14:43:10 UTC,Same here Ubuntu Server 17.10. Solution?
1709668,2017-10-01 00:11:54 UTC,Oh I should have added this system giving me this error is running the 17.10 beta and is up to date.
1709668,2017-10-04 16:20:48 UTC,Please delete my comment #3. I re-read David' post.
1709668,2017-10-04 16:18:17 UTC,I ran into this. Although the netplan ifupdown-migrate doesn't like 'static' we can config a static interface as so:
1709668,2017-10-01 00:09:29 UTC,I've also run into this error.  My network config attaches my physical nic to br0 and assigns a static ip address to the bridge.
1709668,2017-10-26 18:56:07 UTC,This still happens in 17.10 release...any update or plans to fix this?
1709675,2017-08-17 09:28:18 UTC,"Hi Gauthier,"
1709675,2017-08-17 14:06:23 UTC,"Hi Olivier,"
1709681,2017-08-11 22:33:16 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086402.html
1709698,2019-06-03 13:22:56 UTC,"I fixed the milestone and status for this bug, which was released in 3.3.0.  Thanks to Michele Morgan for the clue (via her comment on bug 1780639)."
1709698,2019-03-08 19:04:52 UTC,"Committed to master.  Thanks, Rogan and Jessica!"
1709698,2018-11-30 19:37:29 UTC,New patch.
1709698,2018-12-14 14:15:13 UTC,"I have tested this code and consent to signing off with my name, Jessica Woolford, and email address, <email address hidden>."
1709698,2018-11-07 15:35:17 UTC,http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=cf982a7931c52f4502d281af1f602fa60a1dd8eb
1709698,2018-11-06 21:02:50 UTC,HEAD:user/rogan/lp1709698_template_description_should_be_nullable
1709698,2017-08-28 18:22:12 UTC,"In the xul client, we are able to save a template without adding a description. Is this because the xul client was defaulting to an empty string in that field?"
1709698,2017-08-09 20:38:10 UTC,"The description field on reporter.template has actually always been marked NOT NULL.  IIRC, the intention was to strongly encourage staff to enter a meaningful description of the report, and (also IIRC) the decision on that didn't come from the developers."
1709698,2018-11-07 18:54:16 UTC,Removing pullrequest. Some issues were found that need to be addressed in how the information ends up passing to the report interface.
1709699,2018-12-07 06:04:42 UTC,"Me too, but on Kde system"
1709699,2020-04-26 16:31:15 UTC,"The attachment ""patch removing pk_backend_get_distro_upgrades and disabling the feature"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1709699,2020-04-26 13:06:14 UTC,I think this is really a bug in packagekit. On 18.04 I can also trigger this by just running pkcon get-distro-upgrades in a terminal:
1709699,2019-02-25 06:17:48 UTC,Experiencing same in 18.10
1709699,2018-12-27 17:26:38 UTC,Same problem still in gnome-packagekit 3.30.0-1for Ubuntu 19.04.
1709699,2018-12-27 17:23:07 UTC,"After 18.04 - 18.10 update same;
sudo nano /etc/update-manager/release-upgrades"
1709699,2018-12-27 13:32:05 UTC,"Go into terminal
Change Prompt=lts to normal
Save [CTRL]+O and exit. [CTRL]+X"
1709699,2018-10-18 21:05:19 UTC,"Me too, same problem with Ubuntu 18.04.1"
1709699,2020-04-26 18:42:53 UTC,"Marking this as fix released in PackageKit then, seeing that we ship 1.1.13."
1709699,2018-09-19 09:10:05 UTC,"Yes, fresh install 18.04, same prob."
1709699,2018-09-05 18:32:34 UTC,Can confirm on my fresh bionic installation (with pk-update-icon)
1709699,2018-07-11 02:01:32 UTC,I also have the problem which  presents on installing pk-update-icon
1709699,2018-07-04 07:29:37 UTC,"Adding ""bionic"" tag based on above comment and duplicate."
1709699,2018-06-23 09:33:05 UTC,still happens in 18.04
1709699,2018-05-04 07:33:28 UTC,"Lo mismo/The same
Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed: failed to spawn /usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Falló al ejecutar el proceso hijo «/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py» (No existe el archivo o el directorio)"
1709699,2018-04-28 10:31:15 UTC,same here. Ubuntu 17.10. Intel i5 2500k. gnome-shell version 3.26.2
1709699,2018-04-28 03:43:26 UTC,"I have the same problem-- is there a solution?
Lubuntu 17.10 on a Yoga 2 Pro."
1709699,2017-09-13 18:20:49 UTC,This is the error.
1709699,2018-09-27 14:13:27 UTC,I have the same problem with 18.04
1709699,2017-08-10 07:35:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709705,2017-08-10 14:39:58 UTC,Here you go:
1709705,2017-08-10 13:08:02 UTC,"To help with prioritizing this, I don't know that this actually breaks anything in OpenStack."
1709705,2017-08-10 13:33:29 UTC,"I am not sure if anything breaks either, but I'd like to validate it."
1709705,2017-08-09 20:05:59 UTC,I will need to investigate any side effects with renaming the original volume which is attached/in-use
1709706,2019-02-26 13:51:13 UTC,Is this still an issue?
1709706,2019-02-28 14:07:18 UTC,"Same question and if yes, that be possible to have little more information please? Know more about improvement."
1709706,2019-02-28 14:23:18 UTC,"I'm not aware of any work having been done on this, but it's possible someone did it without attaching it to this bug."
1709708,2017-11-06 01:47:37 UTC,"> On 4 Nov 2017, at 7:29 PM, Rael Gugelmin Cunha <email address hidden> wrote:
>
> I'm using the X-Swat PPA
> (https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates) with mesa
> 17.2.3-0ubuntu0~16.04.0. Should I purge it in order to receive the fix?
"
1709708,2017-11-04 11:29:01 UTC,I'm using the X-Swat PPA (https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates) with mesa 17.2.3-0ubuntu0~16.04.0. Should I purge it in order to receive the fix?
1709708,2017-10-31 20:35:56 UTC,It is v4.14-rc4 which produced sound without playing with pulseaudio or restarting display.
1709708,2017-10-31 07:06:10 UTC,Can you try which is the first version of v4.14-rc* that fixes the issue?
1709708,2017-10-28 10:20:54 UTC,"Well, to be honest, it was your tip about the dpms that I followed! Thanks!"
1709708,2017-10-28 10:06:34 UTC,@Rael That is odd. My TV and cable are way too old to be 2.0 (circa 2008-2009 I believe) and yet the firmware went through and the version number changed. Then again the 2.0 update doesn’t fix anything for this issue. I am also using the 1 second workaround for now!
1709708,2017-10-27 19:29:46 UTC,"@Olivier, I installed a Win10 yesterday with no activation key, and ran the upgrader tool in a old HDMI TV, and the upgrader said it cannot upgrade (according the PDF is because my TV is not HDMI 2)."
1709708,2017-10-27 18:02:14 UTC,"@Rael: I thought so too, but it upgraded just fine on a <2.0 HDMI cable and TV! (afaik)"
1709708,2017-10-27 12:48:53 UTC,"The Intel firmware upgrade is intended only for HDMI 2.0 displays. And, interestingly, you can install it only if NUC is attached to a HDMI 2.0 device."
1709708,2017-10-20 04:37:55 UTC,"The firmware updates have no effect on this issue, Daniel! (It would've been nice though...)"
1709708,2017-10-20 02:46:04 UTC,... but I mostly still expect this is a Linux kernel bug that applies to all manufacturers.
1709708,2017-11-02 09:09:03 UTC,This commit fixes the issue:
1709708,2017-10-19 19:23:43 UTC,"Hi,"
1709708,2017-10-20 02:45:21 UTC,Interesting to see Intel released a firmware update specifically for HDMI on the NUC. If you can boot Windows to install it then it might be worth trying for NUC owners like Neilen...
1709708,2017-08-17 10:13:41 UTC,"I was slightly surprised to see the word ""Broxton"" since Intel canceled that product line before it was ever released. However that just seems to be an incorrect label arising from multiple Intel product lines sharing chipsets... The system is really a J3455 (Apollo Lake) and shares some silicon with the Broxton line."
1709708,2017-08-26 19:46:55 UTC,I have the same exact issue!
1709708,2017-08-17 09:34:31 UTC,Also see askubuntu question: https://askubuntu.com/questions/944735/silent-hdmi-sound-with-nuc6cayh-16-04?noredirect=1#comment1505598_944735
1709708,2017-08-26 20:00:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709708,2017-08-26 19:52:13 UTC,"It also happens in Zesty and Artful, by the way."
1709708,2017-10-10 08:30:14 UTC,"Ironically, the first information we would ask for is for someone to test 17.10:"
1709708,2017-10-11 09:38:43 UTC,"Hi All,"
1709708,2017-10-12 01:55:56 UTC,Thanks.
1709708,2017-10-12 02:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1709708,2017-10-13 18:01:13 UTC,"I was close to submit missing log file.
The command returned that I am not the owner of this bug (translated from Polish :)"
1709708,2017-10-10 08:05:38 UTC,"Dear Community,"
1709725,2020-05-27 15:11:11 UTC,"This bug has been true for me for more than 1 year, and my workaround is to type:
sudo aptitude
(password)
U                                                  (to get ready to update)
g                                                  (to show what it’s going to update)
g                                                  (again to actually DO the update of the files.)"
1709725,2020-05-27 13:12:04 UTC,"I reported bug 1879543 on 2020-0519 and just remembered to check email. On 2020-0520, I got referred to this bug 1709725. The bug is still present on my system running Ubuntu 18.04LTS as of this morning 2020-0527, confirmed by using aptitude. Thanks."
1709725,2018-04-23 08:43:28 UTC,"Actually the Updates tab works, showing firmware(fwupd) and flatpak updates. I think better solution is bug 1733245"
1709725,2018-03-22 09:17:58 UTC,Can the Updates tab be removed if it does nothing.
1709725,2017-08-31 10:51:53 UTC,"Well that's a shame, as now it is more confusing. IF a user happens to go to the section and clicks on refresh but the app comes back and states that the system is up to date. Yet the update manager has a slew of updates waiting, it is a bit misleading. Honestly, I think we should just use Gnome/Ubuntu Software to update our system, and the Update Manager should be retired or only used in case of dist-upgrade."
1709725,2017-08-31 12:38:36 UTC,"The current wording/UI is a bit confusing as it is now I think, some ideas of potential tweaks we could do"
1709725,2017-08-31 08:11:44 UTC,That is turned off deliberately in Artful.
1709725,2017-08-31 07:16:09 UTC,"I can confirm that on artful, the ""updates"" tab states that the system is uptodate when update-manager has a stack of upgrades available"
1709725,2017-08-31 00:27:49 UTC,"Launch Ubuntu Software click on Updates then click on Refresh on top left. This used to work and populate packages that needed to be updated. Not any more, just shows message that ""Software up to date"" yet Update Manager has updates pending."
1709725,2018-01-18 08:01:25 UTC,Added to Trello: https://trello.com/c/vNPbGaYl/172-bug1709725-the-updates-tab-states-that-the-system-is-uptodate-when-its-not
1709725,2017-08-30 22:27:26 UTC,What steps are you using to do the updates?
1709727,2017-10-04 17:11:48 UTC,"The verification of the Stable Release Update for gcc-5 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1709727,2017-10-04 17:11:20 UTC,This bug was fixed in the package gcc-5 - 5.4.0-6ubuntu1~16.04.5
1709727,2017-08-21 07:39:08 UTC,This bug was fixed in the package gcc-6 - 6.4.0-4ubuntu1
1709727,2017-09-13 20:13:52 UTC,"Hello dann, or anyone else affected,"
1709727,2017-08-21 11:36:08 UTC,This bug was fixed in the package gcc-5 - 5.4.1-12ubuntu2
1709727,2017-08-10 13:51:20 UTC,The same fix works for gcc-5/xenial.
1709727,2017-09-14 22:25:51 UTC,xenial/gcc-5 verification:
1709729,2017-08-10 23:23:27 UTC,"Dear Eduard.  Regarding yours of Thu, 10 Aug 2017 23:13:10 -0000:"
1709729,2017-08-10 23:21:29 UTC,"Dear Eduard.  Regarding yours of Thu, 10 Aug 2017 20:05:09 -0000:"
1709729,2017-08-10 23:13:10 UTC,Please re-read comment #12
1709729,2017-08-10 22:57:21 UTC,"Dear Eduard.  Regarding yours of Thu, 10 Aug 2017 20:05:09 -0000:
This doesn't explain why when I set the path to just the c:\windows\system32;c:\windows Inkscape still fails.
Also, I just tried renaming all the other fonts.conf files to fonts1.conf (none of these belong to Demeter, BTW), and it
still fails."
1709729,2017-08-10 20:05:09 UTC,"I also think we found the culprit:
The PATH variable you posted erlier referenced ""DemeterPerl""; the same program was also installed in the system of the reporter of the linked bug."
1709729,2017-08-10 20:03:22 UTC,"I *finally* found the issue I had in mind all along (damn you Launchpad search!):
I'd bet you're facing the same issue we already had in bug #1697681!"
1709729,2017-08-10 19:20:46 UTC,Why don't you try to rename them first...
1709729,2017-08-10 17:51:20 UTC,The last time an invalid fonts.conf caused the issue (unless I dreamt that up).
1709729,2017-08-10 17:50:46 UTC,Seems to be the same issue reported as bug #1662293 (no solution so far).
1709729,2017-08-10 17:22:12 UTC,"Dear Eduard.  Regarding yours of Thu, 10 Aug 2017 17:03:35 -0000:"
1709729,2017-08-10 17:03:35 UTC,"The issue with fonts with special characters in family name was fixed in Inkscape 0.92.2 (see bug #1508928), so this should not be an issue anymore."
1709729,2017-08-10 16:35:44 UTC,"Dear Eduard.  Regarding yours of Thu, 10 Aug 2017 16:01:37 -0000:"
1709729,2017-08-10 16:01:37 UTC,"> I also tried just typing 'inkscape' at the command line (in the directory)
> and it spat out a whole lot of Gtk-WARNINGs about missing actions and
> died with internal error.
"
1709729,2017-08-10 15:34:06 UTC,"Dear Eduard.  Regarding yours of Wed, 09 Aug 2017 23:16:32 -0000:"
1709729,2017-08-09 23:16:32 UTC,JFTR: I guess we're talking about 0.92.2?
1709729,2017-08-10 19:09:48 UTC,"Dear Eduard.  Regarding yours of Thu, 10 Aug 2017 17:50:46 -0000:"
1709729,2017-08-10 16:01:38 UTC,"Dear Eduard.  Regarding yours of Wed, 09 Aug 2017 23:16:32 -0000:"
1709741,2017-08-10 04:09:44 UTC,"I figure out the problem and solved, was in ""/usr/lib/libpoppler.so""."
1709765,2017-08-10 09:25:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492445"
1709765,2018-09-06 07:46:51 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/492445
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1709765,2020-01-10 15:04:25 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.opendev.org/663603"
1709765,2020-01-10 15:03:10 UTC,Fixed with https://review.opendev.org/#/c/677580/3
1709781,2019-08-31 09:22:59 UTC,Thanks for your reply Oliver.
1709781,2019-08-29 14:21:37 UTC,"hi paul, fixed for me!"
1709781,2019-08-22 11:07:14 UTC,"Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1709781,2018-04-04 19:25:57 UTC,Is there any update on this issue?  I posted a thread on /r/gnome and didn't really get any good feedback (https://www.reddit.com/r/gnome/comments/86dcnh/gnomescreenshot_copy_to_clipboard_fails_on_medium/)
1709781,2017-08-29 09:20:11 UTC,"Thank you for your bug report, it works fine here under wayland, could you reply to some questions
- Do you use the interface or keybindings to the take the screenshots?
- Do you have any error in your system logs or if you start gnome-screenshot from a command line?
- What version of the package do you use?"
1709781,2017-11-27 19:05:24 UTC,No screenshots go to my clipboard either. Saving to files is just fine
1709781,2017-11-15 15:26:47 UTC,"Sorry for wrong posting. I'm new in gnome! ""Shift + printscreen"" saves a file in Pictures (doesn't put in the clipboard). So my testing should be updated with that (the shortcuts are working fine on my machine!!!)"
1709781,2017-11-08 15:00:30 UTC,@seb128 I've made several tests here:
1709781,2017-09-18 09:31:35 UTC,"With some recent update to 17.10, this issue seems to be fixed, at least on my machine. Creating Screenshots with gnome-screenshot works as expected"
1709781,2017-09-01 04:03:12 UTC,"- It doesn't matter if i use the Keyboard Binding, or call ""gnome-screenshot"" by hand - the result is the same.
- No, no errors in the log or console window
- Version is: 3.25.0-0ubuntu1 on Ubuntu 17.10 daily build"
1709781,2018-01-15 13:06:47 UTC,"I got the same issue like reported by @cruz-fernandez - small screenshost may work, larger ones will just display the top part, and most of the times there is nothing to paste...saving always works."
1709782,2017-08-28 13:42:44 UTC,"Greetings! It appears that the credential reset is not a manual cleaning step, that it is automatic and is looking into the driver_info field to determine behavior when executed."
1709782,2017-08-29 12:33:46 UTC,"Thanks Julia.
yes reset_ilo_credentail turns out to be automated cleaning only. Is there any change of enhancement that it can be taken up as manual_cleaning?"
1709782,2017-11-21 17:25:50 UTC,"Greetings,"
1709783,2017-08-10 06:14:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492384"
1709783,2017-11-06 15:25:36 UTC,"Change abandoned by Samuel Matzek (<email address hidden>) on branch: master
Review: https://review.openstack.org/492384
Reason: Abandoning per owner's agreement."
1709785,2017-08-29 22:46:46 UTC,"So you mean these are in the commit messages, but you don't want to incorporate them? I'm not a fan of adding too many heuristics (although Signed-off-by- is well-established, perhaps). In general, we have the --CL-- mechanism for this?"
1709788,2017-12-18 12:51:45 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1709788,2017-12-11 17:43:30 UTC,"Reviewed:  https://review.openstack.org/508885
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8f765408ffcccd8802b4ffb33806e7db15a1029f
Submitter: Zuul
Branch:    stable/pike"
1709788,2017-10-02 14:00:59 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/508885"
1709788,2017-08-15 21:11:53 UTC,"Reviewed:  https://review.openstack.org/492395
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2e5f293f13e8f38e8cb6b4b58bd69d04eb808b9e
Submitter: Jenkins
Branch:    master"
1709788,2017-10-24 12:44:08 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1709788,2017-08-10 06:43:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492395"
1709793,2017-08-10 11:55:31 UTC,"This is by design.  Otherwise, the size of the step file would be massive on complex boards.  I suppose we could generate the top and bottom layer copper as an option.  I will tag this as wishlist.  Finding a developer who has time to implement this may be a long shot."
1709799,2019-09-06 20:42:45 UTC,Fixed in ubuntu-mate-settings 19.10.1
1709801,2017-08-10 08:38:23 UTC,"Looks like such backport are unable to include in upstream, so if someone have same issue, here are solution:"
1709801,2017-08-10 13:14:19 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/492527"
1709801,2017-08-10 15:20:47 UTC,The EndpointFilter catalog was removed in Pike [0] and the issue isn't reproducible in stable/ocata.
1709801,2017-10-24 23:01:05 UTC,"Change abandoned by Tony Breeds (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/492527
Reason: This branch (stable/newton) is at End Of Life"
1709808,2017-08-10 07:58:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492422"
1709808,2017-12-01 08:16:00 UTC,heat panel is split out to heat-dashboard. Retargeting to heat-dashboard.
1709808,2020-09-02 13:29:02 UTC,Any progress?
1709826,2021-02-18 16:45:46 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1709837,2018-07-19 22:55:11 UTC,"I can duplicate this, but not reliably, so I think the problem isn't an infinite recursion, just a very large recursion. Making a deepcopy of an Element that's connected to a Beautiful Soup tree will make a deepcopy of every single element in the tree. I had assumed deepcopy memoized elements and reused the memos, but I don't think that's the case -- I would have to implement __deepcopy__ and take care of the memoization myself."
1709837,2020-09-22 17:29:21 UTC,Any updates on this? Is there a way to mitigate the issue at least?
1709837,2020-09-26 15:38:36 UTC,"No, I haven't found a way around this short of implementing my own version of __deepcopy__. Mitigating the problem depends on your situation, but two solutions I can think of are to extract() the item you're about to copy (so that copying it doesn't copy the entire tree), or convert it to a string with decode() _instead_ of copying it."
1709837,2020-09-26 16:24:41 UTC,"That's the thing, I need to copy the entire document, and decode sometimes raises the exception as well."
1709837,2020-09-26 17:23:24 UTC,Does sys.setrecursionlimit help at all?
1709838,2017-08-18 04:51:25 UTC,"What's the value?
logger should log related value for debug."
1709838,2017-09-12 16:13:59 UTC,"Neutron LBaaS api also return json value to user.
How does the logic do? Why does it have same issue. we can follow how they do."
1709838,2018-02-26 12:18:33 UTC,Please provide the command that was used
1709855,2018-01-23 08:18:32 UTC,"I have faced the same issue with this new ""Inkscape 0.92.2""
Many of my files (about 4000) have created by ""Inkscape 0.91 r13725"" using some Persian fonts and it a very serious challenge for me to fix this issue or back to my old friend Inkscape 0.91.
Any help please."
1709856,2017-08-10 11:42:27 UTC,s/user.conf/user.rules/g
1709856,2018-12-14 15:43:58 UTC,"In thinking about this, ufw manages user*rules and it hex_encodes/decodes the comment string. If someone comes in and changes this, ufw *should* error, which you agree with. However, displaying that string to the user in a meaningful way is difficult. Returning '<Bad string>' is definitely prettier, but the question then is 'what string?' and trying to display the bad string is probably a bad idea. We could instead do something like: 'Malformed encoded comment for rule: ...' though."
1709859,2017-08-15 14:30:31 UTC,Can someone validate this bug please.
1709866,2017-08-10 13:57:46 UTC,After i restarted the computer and those two broken files was removed i did a new 'Recheck integrity' i can now see the bundle in Queued (1) and status Rechecking and when it was finished no files was downloaded (so it won't download missing files?).
1709890,2019-12-06 07:02:47 UTC,"Now I see the root cause of problem:
https://www.fujitsu.com/pl/products/computing/peripheral/scanners/scansnap/ix500/"
1709890,2019-12-05 23:20:57 UTC,Please reopen this bug report if it is not working for you.
1709890,2019-12-05 23:20:11 UTC,"The Front, Back and Duplex are working only in ADF mode."
1709896,2017-08-10 15:02:07 UTC,"StacktraceTop:
 send_delete_event (data=0x1c3a3f0) at /build/gtk+3.0-2Ut_nl/gtk+3.0-3.18.9/./gtk/gtkwindow.c:1285
 gdk_threads_dispatch (data=0x3bbcc80) at /build/gtk+3.0-2Ut_nl/gtk+3.0-3.18.9/./gdk/gdk.c:719
 g_main_dispatch (context=0x1a7dc00) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3154
 g_main_context_dispatch (context=context@entry=0x1a7dc00) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3769
 g_main_context_iterate (context=context@entry=0x1a7dc00, block=block@entry=0, dispatch=dispatch@entry=1, self=<optimized out>) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3840"
1709899,2017-09-01 20:45:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709899,2017-09-04 21:54:45 UTC,"Not sure how much help it will be, but I keep getting redirected to this bug as already having been reported and each time I've been quietly minding my own business doing something completely unrelated to the dock - this time reading a web page in Firefox. I presume it is doing something in the background to trigger the problem."
1709899,2017-09-10 11:16:29 UTC,"I'm getting this several times a day now, so if there is an update I should notice quite quickly whether it has had an impact. In case there is a common link I also have other bugs against the mate-dock-applet:"
1709899,2017-09-30 17:25:09 UTC,"Just clicked on 'Network Servers' on the desktop (put there by Mate Tweak), ended up here"
1709913,2017-08-17 21:51:33 UTC,"works for me.
I changed quota for floatingip and created floating ip, then quota show.
The logic that caused the stack trace is in neutron common code.
I suspect config issue."
1709913,2017-09-22 17:09:03 UTC,Isaku I can still see this test failing with:
1709964,2017-08-11 20:56:47 UTC,I built a 17.04(Zesty) test kernel with a pick of commit 8c218578fcbbbdb104. This kernel can be downloaded from:
1709964,2017-08-17 19:29:26 UTC,"------- Comment From <email address hidden> 2017-08-17 15:11 EDT-------
I believe Puvi verified the PMC5 issue is fixed with this build, although it hit a stability issue which is being addressed in bug 157728 (Canonical Launchpad bug 1711104 )."
1709964,2017-08-24 16:39:25 UTC,"------- Comment From <email address hidden> 2017-08-24 12:31 EDT-------
(In reply to comment #18)

> I built a 17.04(Zesty) test kernel with a pick of commit 8c218578fcbbbdb104.
> This kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1709964
>
> Can you test this kernel and see if it resolves this bug?
"
1709964,2017-09-01 08:26:19 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1709964,2017-09-06 19:59:24 UTC,"------- Comment From <email address hidden> 2017-09-06 15:53 EDT-------
Thanks, this problem is now resolved with the -proposed kernel."
1709964,2017-09-18 09:21:44 UTC,This bug was fixed in the package linux - 4.10.0-35.39
1709965,2017-08-13 04:35:02 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1709965,2017-08-13 04:46:47 UTC,Thank you for your report!
1709965,2017-08-13 04:46:41 UTC,"StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()"
1709978,2017-08-27 23:55:19 UTC,Do you have any example images that reproduce this issue?
1709978,2017-08-28 01:37:52 UTC,"Oh...my fault!
I didn't explain properly. Sorry|!! :-("
1709983,2017-08-10 22:10:36 UTC,Gerrit review: https://review.openstack.org/492702
1709989,2017-12-14 09:20:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1709989,2017-12-14 09:20:56 UTC,The same for Thinkpad t470
1709995,2017-11-01 22:31:45 UTC,https://github.com/juju/juju/pull/8010
1710008,2019-05-25 10:26:08 UTC,"This was a good report, but it is not a bug as such. Closing."
1710008,2017-09-11 10:11:00 UTC,I opened bug 1710125 to track efforts to prevent this problem from reoccurring.
1710008,2017-08-11 12:48:51 UTC,"All configuration files are in labs/osbash/config. The configuration file named ""openstack"" contains a variable ""OPENSTACK_RELEASE"" which configures which basedisk is used (or which OpenStack release is downloaded and installed if the basedisk does not exist)."
1710008,2017-08-11 12:23:31 UTC,"Thanks for the response. Yes, it looks like it is trying with 9.2.0 - not sure which configuration file is being used? Am not able to find it.Trying to find that out. Appreciate any help on this."
1710008,2017-08-11 09:50:41 UTC,I just remembered where I have seen this error before.
1710008,2017-08-11 08:02:21 UTC,I assume you downloaded the software from https://docs.openstack.org/training_labs/. Which version did you download?
1710019,2017-11-14 15:27:06 UTC,Uploaded qemu_2.8+dfsg-3ubuntu2.8 to unapproved.
1710019,2017-11-16 20:57:50 UTC,"Hello dann, or anyone else affected,"
1710019,2017-11-17 15:45:59 UTC,"I've verified this for zesty, using my patched zesty kernel. Demonstration of that follows. However, the kernel patches have not yet been approved for zesty, and may never be. I'll hold-off on updating the tags here until a) we have a final answer on the kernel patches or b) we decide there is value in updating QEMU w/o the kernel side."
1710019,2017-11-22 14:19:31 UTC,"Hello dann, or anyone else affected,"
1710019,2017-11-24 11:51:36 UTC,"Hi Dann,
maybe it was good to hold off on this.
It seems it causes a regression on arm, see bug 1734326.
Also by holding for an arbitrary amount of time it might block the SRU queue for something else."
1710019,2017-11-29 15:16:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1710019,2017-11-29 16:54:32 UTC,"On Fri, Nov 24, 2017 at 4:51 AM, ChristianEhrhardt
<email address hidden> wrote:

> Hi Dann,
> maybe it was good to hold off on this.
> It seems it causes a regression on arm, see bug 1734326.
> Also by holding for an arbitrary amount of time it might block the SRU queue for something else.
"
1710019,2017-11-30 09:32:06 UTC,Removed qemu from zesty-proposed based on this discussion.
1710019,2017-11-30 09:38:08 UTC,"Thanks Andy,
I pushed a revert to qemu's packaging git to ensure there is no accidential upload of the same content on the next zesty SRU."
1710019,2017-12-12 12:45:22 UTC,This fix has been reverted in qemu 1:2.8+dfsg-3ubuntu2.9~cloud1 to align with Zesty. qemu 1:2.8+dfsg-3ubuntu2.9~cloud1 has now been released to ocata-updates.
1710019,2017-12-06 13:00:37 UTC,"@Kleber - that would mean we also want to ping Po-Hsu for a bug 1734326 retest?
He would need a ppa for that - @Dannf do you still have that in a ppa for him to test against the kernel in proposed?"
1710019,2017-12-06 16:48:29 UTC,"artful verification:
ubuntu@seyfert:~/vm-save-restore$ ./test.sh
+ i=0
+ [ -f /var/log/libvirt/qemu/4172-0.log ]
+ name=4172-0
+ ./randmac.py
+ mac=00:16:3e:7b:3b:f1
+ uuidgen
+ uuid=33815e19-0f44-4e6f-8209-ada375484ba3
+ mktemp
+ xml=/tmp/tmp.Mc2sJDaknd
+ cp template.xml /tmp/tmp.Mc2sJDaknd
+ trap cleanup EXIT
+ mkdir -p vms
+ dd if=/dev/zero of=./vms/4172-0_CODE.fd bs=1M count=64
64+0 records in
64+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 0.173587 s, 387 MB/s
+ dd if=/usr/share/qemu-efi/QEMU_EFI.fd of=./vms/4172-0_CODE.fd conv=notrunc
4096+0 records in
4096+0 records out
2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.0523696 s, 40.0 MB/s
+ dd if=/dev/zero of=./vms/4172-0_VARS.fd bs=1M count=64
64+0 records in
64+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 0.173042 s, 388 MB/s
+ cat
+ cloud-localds vms/4172-0_seed.img vms/4172-0_user-data
+ pwd
+ qemu-img create -f qcow2 -o backing_file=/home/ubuntu/vm-save-restore/zesty-server-cloudimg-arm64.img ./vms/4172-0.img
Formatting './vms/4172-0.img', fmt=qcow2 size=2361393152 backing_file=/home/ubuntu/vm-save-restore/zesty-server-cloudimg-arm64.img cluster_size=65536 lazy_refcounts=off refcount_bits=16
+ sed -i s/\#VM\#/4172-0/ /tmp/tmp.Mc2sJDaknd
+ pwd
+ sed -i s,\#DIR\#,/home/ubuntu/vm-save-restore, /tmp/tmp.Mc2sJDaknd
+ sed -i s/\#UUID\#/33815e19-0f44-4e6f-8209-ada375484ba3/ /tmp/tmp.Mc2sJDaknd
+ sed -i s/\#MAC\#/00:16:3e:7b:3b:f1/ /tmp/tmp.Mc2sJDaknd
+ sudo virsh define /tmp/tmp.Mc2sJDaknd
Domain 4172-0 defined from /tmp/tmp.Mc2sJDaknd"
1710019,2017-12-06 18:16:54 UTC,@Christian: I don't know that we need Po-Hsu to retest bug 1734326 - the accepted fix as for the artful kernel - there's no artful QEMU counterpart needed.
1710019,2017-12-07 07:26:41 UTC,"Oh I see that was artful, thanks dannf for clarifiaction.
So no reasons to move on bug 1734326 unless you come back having it analyzed then."
1710019,2017-12-07 17:42:36 UTC,This bug was fixed in the package linux - 4.13.0-19.22
1710019,2017-12-11 15:35:07 UTC,The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1710019,2017-12-11 15:35:12 UTC,"This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.8~cloud0
---------------"
1710019,2017-11-14 07:10:34 UTC,Note: tested version was 1:2.8+dfsg-3ubuntu2.7+lp1710019.1
1710019,2017-12-12 12:46:26 UTC,qemu (1:2.8+dfsg-3ubuntu2.9~cloud1) xenial-ocata; urgency=medium
1710019,2018-01-10 01:35:55 UTC,This bug was fixed in the package linux - 4.13.0-25.29
1710019,2017-12-06 11:47:48 UTC,"Hi @dannf,"
1710019,2017-11-14 07:09:55 UTC,"I have kicked off a verification run on the ppa to check the qemu in there.
I passed all stages just fine, which means you are likely fine to go when you have the kernel ready.
Thanks for also clarifying if we need to BP the #1731051 fix in relation to this change."
1710019,2017-11-09 02:21:46 UTC,@Christian: The blocking issue was with the kernel. It has now been fixed upstream and I've begun submitting SRU patches for the kernel. +1 from me on proceeding with the QEMU portion.
1710019,2017-11-10 06:45:16 UTC,"Ok, Dann - thanks for the clarification.
So per the SRU rules to not regress on updates that would then be Zesty, Artful, Bionic.
With Qemu being ok since Artful and Kernel needing your backports in Zesty 4.10 and Artful 4.13 then."
1710019,2017-08-11 06:21:32 UTC,"Hi Dann,
you aready added half a SRU template - so are you knowing/working on a fix already?"
1710019,2017-08-11 17:05:01 UTC,"Indeed! I've updated the bug status to reflect that. Currently I do have a backport to 2.8 that seems to be working as well as latest upstream. That is, I can save and restore a UEFI guest, prior to starting Linux. I'm working on diagnosing an issue where a guest that has been saved after Linux has booted fails to restore with:"
1710019,2017-08-11 21:35:45 UTC,"Here's the test tool I'm using to verify this. It spins up a zesty guest and gives it time to get past the bootloader and into Linux, then tries to save and restore it."
1710019,2017-08-14 08:24:20 UTC,"Ok, thanks for calrification good to know this is in your hands."
1710019,2017-08-15 02:35:11 UTC,"On Mon, Aug 14, 2017 at 2:24 AM, ChristianEhrhardt
<email address hidden> wrote:

> Ok, thanks for calrification good to know this is in your hands.
>
> About:
> [*] Note: you currently need to boot the Ubuntu kernel w/ apparmor=0 to work with latest upstream QEMU
>
> I haven't seen anything like that when testing 2.10-rc1/rc2 - is that arm specific (apparmor usually prefers to fail everywhere the same way)?
> Maybe it depends on the host kernel as most of my tests use Xenial-Kernel + LXD<newrelease>.
> Since soon there will be a 2.10 based upload to artful please let me know if there is a bug or details about this somewhere else.
"
1710019,2017-08-15 15:18:27 UTC,"Hi Dan was already on that error:
""2017-08-14T23:43:10.255936Z qemu-system-aarch64: -drive
file=/home/ubuntu/vm-start-stop/vms/7936-0_CODE.fd,if=pflash,format=raw,unit=0,readonly=on:
Failed to lock byte 100"""
1710019,2017-08-15 19:53:10 UTC,(AppArmor/pflash issue has been forked off in to LP: #1710960)
1710019,2017-08-24 15:51:20 UTC,"Was able to reproduce the issue with 4.13 + latest qemu with the scripts provided.
Issue seems to be with restoring of ITS table is failing. Investigating further."
1710019,2017-11-10 17:21:09 UTC,"I have a staging PPA that I'm using for testing at ppa:dannf/lp1710019. The QEMU there is the attached debdiff (trivially) forward-ported to the latest qemu in updates, and the kernel has the patches I plan to submit to the kernel team. I've verified that this all works together on a zesty system."
1710019,2017-08-25 17:20:31 UTC,"With the below patch, The issue seems resolved. Please check and let me know."
1710019,2017-08-28 05:45:26 UTC,"That is a kernel patch.
@Vijaya/Dannf - should we add a kernel task for them to be aware of?"
1710019,2017-08-24 15:52:06 UTC,4.13-rc6
1710019,2017-08-28 21:49:47 UTC,"Here's a backport for zesty's QEMU, tested with the 4.13.0-7.8 kernel from ppa:canonical-kernel-team/unstable w/ the patch from Comment #10 applied."
1710019,2017-11-10 01:02:28 UTC,"libvirt's apparmor policy doesn't allow for restoring instances from /tmp, so I've updated my reproducer tool:
  https://code.launchpad.net/~dannf/+git/vm-save-restore"
1710019,2017-08-28 21:34:30 UTC,"@Vijaya: Yes, that patch does resolve the issue for me, thanks! Do you plan to submit this upstream?"
1710019,2017-11-09 08:48:02 UTC,"I assume this is:
commit b92382620e33c9f1bcbcd7c169262b9bf0525871
    KVM: arm/arm64: vgic-its: Fix return value for device table restore
And some more patches around it."
1710019,2017-09-07 05:47:38 UTC,"On Wed, Sep 6, 2017 at 7:20 PM, dann frazier <email address hidden>
wrote:"
1710019,2017-11-09 16:26:23 UTC,"I plan to submit my backport to zesty's (4.10) kernel - I haven't yet investigated the feasibility of backporting this feature to xenial's virt stack. With respect to QEMU, at this time I'm only requesting that the backport for zesty be considered."
1710019,2017-09-06 08:50:48 UTC,"Dann, I don't want to miss the activity here - so the next step you are expecting is me to evaluate the diff in detal and prep a qemu SRU?
Along that you will do regression tests on arm and I could do x86/ppc/s390x?"
1710019,2017-08-30 17:35:57 UTC,"On Wed, Aug 30, 2017 at 12:35 AM, ChristianEhrhardt
<email address hidden> wrote:

> Hi Dann,
> Sorry to ask, really I'm not neglecting all the work you do here.
> But it is a huge set of changes (17 files changed, 929 insertions(+), 46 deletions(-), and not all arm only) and I wonder as Zesty will never have the 4.13 kernel (as HWE is for LTS only).
"
1710019,2017-08-30 06:35:56 UTC,"Hi Dann,
Sorry to ask, really I'm not neglecting all the work you do here.
But it is a huge set of changes (17 files changed, 929 insertions(+), 46 deletions(-), and not all arm only) and I wonder as Zesty will never have the 4.13 kernel (as HWE is for LTS only)."
1710019,2017-08-29 16:27:58 UTC,"Hi Dann,"
1710019,2017-09-06 17:20:16 UTC,"On Wed, Sep 6, 2017 at 2:50 AM, ChristianEhrhardt
<email address hidden> wrote:

> Dann, I don't want to miss the activity here - so the next step you are expecting is me to evaluate the diff in detal and prep a qemu SRU?
> Along that you will do regression tests on arm and I could do x86/ppc/s390x?
>
> Is that correct then I'd create a ppa for both of us to do the checks or
> is something missing that I should wait on?
"
1710022,2021-01-20 08:51:25 UTC,"Hello,"
1710022,2020-12-29 09:18:41 UTC,@Daniel Manrique (roadmr) wrote:
1710022,2020-06-03 15:36:20 UTC,Just had #1878679 marked as duplicate of this.
1710022,2020-12-29 09:08:26 UTC,"I ran across this trying to set up an IPv6 machine, and found that api.snapcraft.io does not support IPv6."
1710022,2020-11-22 17:49:47 UTC,Add me as impacted
1710022,2020-05-19 14:03:02 UTC,I'm also suffering from api.snapcraft.io only being reachable via legacy IP.
1710022,2017-08-14 21:51:37 UTC,"I can do NAT64 in the meantime, but obviously not a long-term solution."
1710022,2020-01-29 13:13:32 UTC,"Is there any information on when this will be put on the roadmap? Currently we are using a workaround using hardcoded nat64 endpoints to a tcp proxy It's 2020 now and native ipv6 support should be a no-brainer, especially for products targeted at IOT. I understand that until recently kubernetes could only drop ipv6 (by default), but the end customer should not be the victim of that poor architecture. There are other ways like putting a CDN in front."
1710022,2020-02-23 19:34:00 UTC,"@Daniel
How is it more difficult than just assigning an IPv6 to the webserver? I don't need to know what you're doing internally. If IPv6 isn't a priority there, it's none of my concern. Also, it should be quite high on the priority list now, as IPv6-only machines are becoming more and more common and IPv4 addresses are getting more and more expensive. Right now, not offering IPv6 is starting to disable people in doing ""stuff"", contrary to enabling people what was once the benefit of using snap."
1710022,2017-08-11 00:25:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1710022,2017-08-11 22:07:21 UTC,"This makes me think we should be looking up 'assertions.snapcraft.io'
rather than 'assertions.ubuntu.com'"
1710022,2017-08-14 20:11:44 UTC,"How do you access IPv4-only resources from that system? Do you have some sort of gateway you could use to talk to the IPv4-only snap store services? I would suggest that as a workaround, since the work needed to make the snap store IPv6-ready will take some time, due to the fact there are many components in the stack and we need careful coordination of changes in all the pieces for enabling IPv6 support."
1710022,2019-08-15 16:35:26 UTC,Agree with t-jeske above. Enabling IPv6 on a web server is not a rocket science really. This bug has been open for 2 years now.
1710022,2019-03-28 19:14:50 UTC,"It's 2019 now and snapcraft is still not reachable via IPv6. I also have some IPv6-only machines (or some, where IPv6 is preferred as it doesn't count towards the traffic quota). I think it is about time this gets sorted. There is really not much to consider when turning on IPv6 on a webserver."
1710022,2019-08-15 16:59:47 UTC,You make it sound like it's just a matter of assigning an IPv6 address to a host and tweaking a couple of Apache configs. It is not. The stack is more complex than that and changes are needed in other parts as well. We have this in our radar and will complete it as soon as feasible given other Snap Store priorities.
1710023,2017-08-10 22:11:22 UTC,lshal.txt was empty
1710023,2017-08-10 22:09:43 UTC,devices.txt added
1710023,2021-01-09 18:22:31 UTC,That's one way to end an issue.  Yes the issue still exsits.  It has birthdays.  I never saw that someone asked for verification 60 days ago.
1710023,2021-01-09 04:17:23 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1710023,2020-11-09 08:32:12 UTC,"Hello,
As kernel 4.10 is no longer supported, can you give the latest supported kernel a try to see if this issue still exist?
Thanks!"
1710023,2019-03-04 23:17:15 UTC,microSD workshop for me only with Linuxmint mate 17.# either live or installed with 4.4 kernrl. Instead mint mate 18.# or 19.# doesn't work.
1710023,2018-03-16 15:11:19 UTC,Do I need to do any more in the reporting?
1710023,2018-03-16 03:44:57 UTC,Also: I have kernel 4.13.0-37-generic.
1710023,2018-03-16 03:42:16 UTC,I (believe that I) am having the same issue (on the same computer) running a fresh install of 17.10. The returns I receive from the commands listed in the Bug Description are substantively identical.
1710023,2019-04-29 04:30:11 UTC,"FYI: I tried using my SD card again after a fresh install of Ubuntu 19.04 (kernel 5.0.0-13-generic) and my SD card (SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)) now works properly. I have a ThinkPad E580."
1710023,2018-01-13 01:58:45 UTC,"Am I correct in finding the proper mailing list (haven't sent mail yet)?
I send a plain text email to here containing the data required in the link?  Grr - I don't have or need email setup on this computer."
1710023,2017-08-10 22:12:03 UTC,udev.log was empty
1710023,2018-02-09 04:26:58 UTC,"I can confirm this. Numerous attempts of different versions 16.04 and up, no read write or detection of sd card."
1710023,2017-08-12 04:22:44 UTC,"Reverting kernel to 4.8.17-040817-generic fixes the problem.  sdhci-pci module flags bus master, fast devsel, latency 0, IRQ 18 set and works."
1710023,2018-01-10 20:59:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710023,2017-08-10 22:10:15 UTC,dmesg.txt added
1710023,2018-01-12 02:05:36 UTC,Tested 4.15-rc7 and no difference - card is still not recognized.
1710023,2018-01-12 02:10:30 UTC,kernel-bug-exists-upstream tag added
1710023,2018-01-12 15:24:36 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1710023,2018-01-11 01:51:06 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1710028,2017-08-10 22:57:00 UTC,quiero que me ayuden a solucionar este error
1710037,2017-08-12 23:42:27 UTC,I fixed it by changing the mirror from the out-of-the-box default to Waterloo Canada in repositories.
1710040,2018-02-21 23:26:37 UTC,"Hrm.. I wonder if the existing ""Create New Crate"" dialogue could be re-jigged for this?"
1710040,2018-01-08 01:22:42 UTC,"FWIW, I still think a free-tagging style text-based crate assignment and creation dialogue with autocomplete would be useful, but that could be accessed via the context menu."
1710040,2017-12-28 15:21:05 UTC,I think it may be better to implement this in the deck section of the skins. Or maybe both.
1710040,2017-08-16 05:22:58 UTC,"Also, this would be *great* if it had crate auto-completion, a-la question tagging on stackexchange sites."
1710040,2018-01-03 04:27:44 UTC,"I think if https://bugs.launchpad.net/mixxx/+bug/1271812 was implemented, right-click on the artist/track title in the deck would solve that problem. I don't think this is big enough to warrant an extra button in each deck."
1710049,2017-10-24 03:18:59 UTC,This issue was fixed in the openstack/cinder 12.0.0.0b1 development milestone.
1710049,2017-12-05 19:38:07 UTC,This issue was fixed in the openstack/freezer-web-ui 6.0.0.0b2 development milestone.
1710051,2017-11-04 18:05:00 UTC,"For the help of other users, I just want to mention that in Ubuntu 17.04, I ended up switching back to stable xorg and *removing* xserver-xorg-video-intel, as suggested in some online documentation, in order to force the modesetting driver to run. I'd see modesetting and glamoregl modules loading in the Xorg.0.log file."
1710051,2018-07-23 17:03:46 UTC,I have been seeing this similar issue for some time but hadn't gotten to looking into it. My system was also running with the subject driver:
1710051,2017-09-01 16:51:38 UTC,@chipaca Thanks for the suggestion. Interesting. I see a reddit thread about this here:
1710051,2017-09-01 15:10:54 UTC,"The package description of xserver-xorg-video-intel says,"
1710051,2017-08-12 17:09:54 UTC,"Also, a couple of days later, I experienced another full system hang. I was using GPU-accelerated Chrome at the time, but it was when a new page was loading. So, the newer PPA may not have totally corrected this issue, perhaps it just moved it around somehow."
1710051,2017-10-15 07:01:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710058,2017-09-20 09:50:57 UTC,"Reviewed:  https://review.openstack.org/492796
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=2b01b054443097ba344fa00d1055dbce22e6b8ea
Submitter: Jenkins
Branch:    master"
1710058,2017-12-07 14:48:59 UTC,This issue was fixed in the openstack/kolla 6.0.0.0b2 development milestone.
1710058,2018-05-08 05:59:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/566785"
1710058,2018-05-22 12:16:42 UTC,"Reviewed:  https://review.openstack.org/566785
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=2191d62144a35818b4f62840c89dac09a820d87c
Submitter: Zuul
Branch:    stable/pike"
1710058,2018-07-24 12:24:19 UTC,This issue was fixed in the openstack/kolla 5.0.3 release.
1710059,2018-10-04 14:55:49 UTC,Upgraded to Ubuntu 18.04 - still the same issue...
1710059,2018-04-18 03:17:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710059,2017-08-15 22:43:36 UTC,What theme is that?
1710059,2017-08-30 13:04:30 UTC,"I can't use GTK inspector with Thunderbird. No idea what selectors it is using, but they are clearly not the correct."
1710059,2017-08-16 07:43:16 UTC,"Hey Martin,"
1710059,2018-03-05 17:54:23 UTC,This bug happens also with the default Ambiance theme on Ubuntu 17.10. See attached screenshot.
1710060,2020-02-17 15:51:45 UTC,This is also an issue with Kubuntu 19.10 eoan 5.3.0-40-generic and pulseaudio 13.0
1710060,2019-06-10 12:24:59 UTC,"Sorry, -r is the correct option, of course. If the problematic rate works with the direct ALSA interface, you may try to simulate stream parameters (buffers) like PA uses and use '-b -p -P' arguments for speaker-test to force them. The actual streaming parameters are in /proc/asound/card#/pcm0p/sub0 directory."
1710060,2019-06-10 12:18:49 UTC,"Do you mean -r or -f ?  I hear ""pink noise"" with all selected frequencies with either -r or -f."
1710060,2019-06-10 11:40:11 UTC,The device reports those supported sample rates:
1710060,2019-06-10 11:14:11 UTC,"pulseaudio-12.2-3.fc30.x86_64
alsa-lib-1.1.9-1.fc30.x86_64
$ uname -r
5.1.6-300.fc30.x86_64"
1710060,2019-06-10 11:13:24 UTC,I see this with the Jabra Evolve 65 headset as well in Fedora 30.
1710060,2018-07-31 01:42:20 UTC,"Sam,"
1710060,2018-09-11 09:49:41 UTC,"Faced the same issue with following device and OS.
Jabra 65
Linux waimw030207 4.4.0-133-generic #159-Ubuntu SMP Fri Aug 10 07:31:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1710060,2017-08-11 04:47:25 UTC,"""Chipmunks"" sound implies that the audio is being played back at a higher sample rate than it was recorded at. Obviously this should not happen if all layers are aware of the recording sample rate and adjust playback accordingly. So you would need to find out what part of the system is using (or guessing) the wrong sample rate."
1710060,2018-04-25 10:59:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710060,2015-11-16 02:50:21 UTC,"Description of problem:
When playing audio through the Jabra Evolve 65 UC headset using either the USB cable or the Jabra Link 360 USB dongle, sound is played back too fast, with a 'chipmunk' effect.  I don't know if the recording side is affected or not, but people have not commented on it if it is."
1710060,2016-01-26 20:16:12 UTC,"This bug has been open now for 2 months with zero movement.  Is there anything I can do to help out here?  I'm willing to troubleshoot, I just have no idea what to do next."
1710060,2016-01-29 18:50:29 UTC,I'm pretty sure that this is an alsa problem. The driver probably configures the wrong samplerate or maybe it needs a tweak for this particular hardware.
1710060,2018-07-31 00:22:36 UTC,"For what its worth, I had this issue on Ubuntu 18.04 - but also on Antergos 18.7."
1710060,2016-02-15 19:13:10 UTC,"(In reply to Wim Taymans from comment #2)

> I'm pretty sure that this is an alsa problem. The driver probably configures
> the wrong samplerate or maybe it needs a tweak for this particular hardware.
"
1710060,2016-03-05 22:15:20 UTC,"Hi. I've had the same problem.
Here is workaround that helped me:"
1710060,2016-03-08 03:56:03 UTC,"Just tried this, and it appears to work here as well."
1710060,2016-02-15 17:11:38 UTC,"Exactly the same here.
Trying with newest version of Debian 8 and SuSE 42.1."
1710060,2016-07-19 20:15:30 UTC,"Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1710085,2017-11-03 18:17:20 UTC,"exact amount, or with a x% tolerance ?"
1710085,2017-12-29 16:54:32 UTC,"Exact amount is a good idea.
With a x% tolerance : Why not but optional"
1710096,2019-09-19 12:04:15 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1710102,2017-08-11 08:33:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/492876"
1710102,2018-12-14 06:04:26 UTC,"Change abandoned by Kaifeng Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/492876"
1710104,2017-08-13 09:38:11 UTC,Looks like the issue is caused by the use of underscores in the links. Filed a github ticket for further tracking here: https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/183
1710105,2017-08-11 14:14:16 UTC,"I will try to identify the root cause instead of playing with fire, but thanks anyway."
1710105,2017-08-11 08:46:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710105,2017-08-11 09:28:57 UTC,Most likely kernel issue. Downgrade to 4.2 and see if that helps.
1710109,2017-09-26 10:55:48 UTC,Thanks for your patch. This was committed to trunk in revision 2768.
1710128,2017-09-18 14:26:17 UTC,"I have re-tested this on version 3.2.5 and the bug is still reproducible.
Is this a known limitation of contrail?"
1710134,2018-05-11 15:33:59 UTC,This change was made by a bot.
1710138,2019-09-16 14:29:49 UTC,Migrated to https://github.com/widelands/widelands/issues/1686
1710141,2018-04-20 06:20:03 UTC,"Though the log already disappeared, probably, the remaining issue was fixed with this report[1]."
1710141,2018-01-31 13:50:08 UTC,"In fact, this issue is still present: http://logs.openstack.org/86/537386/5/check/ironic-a-dsvm-ipa-partition-uefi-pxe_ipmitool-tinyipa/fded21b/logs/screen-n-cpu.txt.gz?level=WARNING"
1710141,2017-08-16 23:44:24 UTC,"Reviewed:  https://review.openstack.org/494216
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c92337bdf80fea4c0a8ebb433bacec4cc07f7a94
Submitter: Jenkins
Branch:    stable/pike"
1710141,2018-01-24 15:08:47 UTC,"I think we're seeing a similar issue to this on Pike with this fix applied. We have resource providers for active ironic nodes that have no inventory in placement. When the resource tracker tries to update the RP allocations, we get a conflict because there is no inventory to allocate from for the RP:"
1710141,2017-08-16 13:57:42 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/494216"
1710141,2017-08-11 15:31:39 UTC,Patch is at https://review.openstack.org/492964
1710141,2017-08-11 12:45:07 UTC,"If we're just fixing the warnings, then this isn't pike-rc-potential for rc2, we could just fix the warnings issue and backport to stable/pike and stable/ocata since it's not a regression in pike."
1710141,2017-08-11 12:11:17 UTC,"One question is, why don't we report inventory for an ACTIVE node? If the inventory is 1 but an instance is also allocating that 1 of whatever resource class, then isn't that sufficient? In other words, if an instance is consuming all of the node inventory, that should take the node out of scheduling decisions for building new instances, which is also how things work for regular compute nodes for building VMs."
1710141,2017-08-16 15:23:06 UTC,"Reviewed:  https://review.openstack.org/492964
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9ed692bf8c84e0a702536101cd6cb084d33e1c26
Submitter: Jenkins
Branch:    master"
1710146,2019-05-18 15:20:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710155,2017-10-12 22:10:13 UTC,"Thanks for the report, Rob."
1710208,2019-12-18 18:56:58 UTC,"Reviewed:  https://review.opendev.org/697708
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=8b6d16698aa96133edf0f2ec84f5e12474bcd46f
Submitter: Zuul
Branch:    master"
1710208,2018-03-13 23:13:32 UTC,"There's an old commit at https://github.com/CanonicalBootStack/charm-openstack-dashboard/pull/1/commits/94d1e086d694d14541c543ca194ad191d81f0c3e which addresses this, but we will need to work on that change in order to make it merge cleanly against master before we can submit that upstream."
1710231,2017-08-17 08:19:26 UTC,"Hi all,"
1710239,2018-04-17 04:00:54 UTC,I had a look into this and can't see it in the charm itself:
1710239,2018-04-17 14:12:36 UTC,This is a custom config that we set on disk_root.
1710239,2018-04-25 07:49:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710243,2017-08-15 07:32:21 UTC,"Hi Alexey,"
1710243,2017-08-15 15:06:29 UTC,"Hi Nickolay,"
1710243,2018-01-25 09:34:25 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3730
1710245,2018-01-08 08:52:43 UTC,See also bug 1741715.
1710245,2017-08-17 02:44:55 UTC,This issue is being tracked in:
1710245,2017-12-28 04:17:31 UTC,[Expired for gnome-sushi (Ubuntu) because there has been no activity for 60 days.]
1710245,2017-08-17 02:43:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710247,2017-08-21 23:14:12 UTC,I found that the charm upgrade would complete (and other hooks that call the status check) after creating a symlink /<email address hidden> to <email address hidden> files on all rabbit units.  Obviously not a scalable solution.
1710253,2017-10-20 00:33:25 UTC,"I started some of this refactoring in one of my branches, but it can be continued from there to incorporate this request."
1710253,2017-09-01 23:11:53 UTC,"Yeah, I think it makes sense for run() to take *different* parameters than subprocess, based upon what we actually need. In this case, we need quiet==True, so that run() doesn't output, but only because we want it to go to the console instead. So there should be a parameter like ouput_to_console=True/False, rather than having the caller know about that implementation detail."
1710254,2017-11-14 00:25:47 UTC,Ouch. Yeah we need to look at the path that being resolved and ensure it's actually in the snap.
1710261,2017-08-21 20:04:29 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086378.html
1710261,2017-08-31 20:39:53 UTC,v2: https://lists.ubuntu.com/archives/kernel-team/2017-August/086770.html
1710262,2017-08-11 17:52:42 UTC,I have no experiences with this.
1710262,2017-08-18 11:25:52 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1710263,2017-10-06 22:33:56 UTC,dmsg output:
1710263,2017-10-06 22:35:57 UTC,Forgot to say: using ubuntu 17.04. This is the uname output: 4.10.0-36-generic #40-Ubuntu SMP Tue Sep 19 12:15:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1710263,2017-10-06 22:37:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710263,2017-10-06 22:38:52 UTC,dmsg output:
1710263,2017-12-12 21:58:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710263,2018-01-25 19:51:57 UTC,Looks like it works with  4.15.0-rc8 kernel (you'll probably need to modprobe snd_hda_intel
1710267,2017-08-12 14:19:46 UTC,Not sure what you mean by low resolution.
1710267,2017-08-12 12:20:55 UTC,From what i see it's that you have a low rezolution monitor?
1710277,2019-10-27 08:59:51 UTC,8.6.9 is in Ubuntu 19.04 and later (https://bugs.launchpad.net/ubuntu/+source/tcltk-defaults/8.6.9+1)
1710278,2019-08-05 13:32:23 UTC,Please wait before testing my ppa [ppa:slashd/lp1710278]
1710278,2019-08-02 07:30:19 UTC,In Reply to Seth's suggestion:
1710278,2019-08-01 20:38:26 UTC,"As mentioned in previous comment, I had to turn off pkcsk11"
1710278,2019-08-01 20:31:50 UTC,I have inverted the output accidentally by mistake:
1710278,2019-08-01 20:23:59 UTC,"# Quick note before one want to test this package:
* This is a test package for others to test, ONLY made to determine that it works as expected and fixes the current situation (pre-sru).
* This is NOT a long term nor final solution yet, please wait until the package is found in the official Ubuntu archive before considering this official (Post-SRU)
* DO NOT test on production area.
* This package is subject to change as we progress."
1710278,2019-08-01 01:52:32 UTC,"Am I reading this bug correctly, that MAAS currently asks BIND to reload its entire configure file on every machine provision and removal?"
1710278,2019-08-05 13:41:02 UTC,I have double-check in the buildlog and everything seems to indicate that multi-treading is turned off:
1710278,2019-07-31 17:12:06 UTC,I think an external provider can be mentioned via '-E engine-name' (see: NAMED(8))
1710278,2019-07-31 14:04:36 UTC,For now I have to use the following to make the build works in
1710278,2019-07-31 14:03:12 UTC,"I started to look for the singlethread new binary approach. So far it seems like bind9 won't be able to use pkcs11 library provider, thus I'm afraid there will be no DNSSEC capabilities in the singlethread binary package as it seems to require pthreads."
1710278,2019-07-30 20:04:02 UTC,Last resolution update:
1710278,2019-08-01 19:40:54 UTC,Ok I have something ready and installable to do further testing now.
1710278,2019-08-05 15:52:04 UTC,"The build works as expected, I think ""dh_install"" is where the named binary got overwritten because ""-pPACKAGE"" is not mentioned."
1710278,2019-08-05 17:37:16 UTC,Which explain why multi thread binary pkg and single thread binary package have the same named binary.
1710278,2019-07-24 09:36:19 UTC,"> Looks like that was the last one for this particular bug.
"
1710278,2019-08-06 02:59:17 UTC,Ok I made some progress
1710278,2019-08-06 05:01:07 UTC,** important note ***
1710278,2019-08-06 05:05:38 UTC,I just confirmed the above ^ :
1710278,2019-08-06 13:12:34 UTC,"ok next challenge, named single-thread coredump as following:"
1710278,2019-08-06 13:23:00 UTC,"$ ldd /usr/sbin/named | grep -i thread
 libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6495778000)"
1710278,2019-08-06 14:39:11 UTC,"Due to the complexity of the work and various challenges I'm facing (fix one problem, find another one, fix it, find another one, and so on) during the process of having a single thread package of bind9. Not counting the complexity to maintain both multi-thread/single-thread package types until the deadlocks situation upstream is fixed, plus version 9.14 not offering single-thread (possibly landing in next release 19.10, and/or 20.04 (which will also be LTS))"
1710278,2019-09-12 14:11:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710278,2019-09-24 13:21:55 UTC,"Hi, I see that the backport fix is released and/or committed to MAAS 2.2, 2.6 and 2.7. Can we get it backported to 2.4 as well? It is currently affecting a customer in production. Thank you!"
1710278,2019-09-24 14:02:37 UTC,We are current working on getting this backported to 2.4.
1710278,2019-09-24 14:31:24 UTC,"Additionally, any idea as of when proposed 2.6.1 (including the dns reload fix) will become available in MAAS/stable ?"
1710278,2019-11-01 17:05:05 UTC,Release 2.4.3 debdiff.
1710278,2020-08-18 16:57:29 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1710278,2019-08-05 17:35:42 UTC,"In the multiple binary package case, the files are instead installed into debian/tmp/, and should be moved from there to the appropriate package build directory using dh_install(1)."
1710278,2019-07-23 12:09:20 UTC,Looks like that was the last one for this particular bug.
1710278,2019-07-31 20:08:02 UTC,"After reading more, I think what is most important for DNSSEC is --with-openssl.
I don't quite get the goal of PKCS11 but it doesn't seem as important as I would first think, if I read this correctly."
1710278,2019-07-19 18:13:51 UTC,first deadlock from comment 27 fixed/workedaround.
1710278,2017-08-11 21:05:18 UTC,"Assuming the debug symbols I grabbed[1] for my install of bind9 on Xenial match yours (I have bind9 version 1:9.10.3.dfsg.P4-8ubuntu1.7 installed per ""apt-cache policy bind9""), I did the following to grab a traceback:"
1710278,2017-08-11 21:09:23 UTC,"This is technically Invalid for MAAS unless there is something unsupported about how we're using BIND, but I'm marking it Triaged for now so we don't lose visibility (in case a fix in MAAS itself turns out to be required)."
1710278,2017-08-11 21:44:37 UTC,"named is being asked to reload its zones quite frequently, sometimes within the same second:
Aug 11 16:31:08 maas named[3174]: received control channel command 'reload'
Aug 11 16:31:17 maas named[3174]: received control channel command 'reload'
Aug 11 16:31:18 maas named[3174]: received control channel command 'reload'
Aug 11 16:31:22 maas named[3174]: received control channel command 'reload'
Aug 11 16:31:26 maas named[3174]: received control channel command 'reload'
Aug 11 16:31:29 maas named[3174]: received control channel command 'reload'
Aug 11 16:31:30 maas named[3174]: received control channel command 'reload'
(...)
Aug 11 17:07:35 maas named[3174]: received control channel command 'reload'
Aug 11 17:07:35 maas named[3174]: received control channel command 'reload'"
1710278,2017-08-11 21:49:28 UTC,"Right; to attempt to reproduce the issue, I would aggressively reload (changing the zone files each time) while at the same time sending a large amount of queries to the server (for records in locally authoritative zones?)."
1710278,2017-08-11 22:13:50 UTC,"In MAAS, we should:"
1710278,2017-08-12 00:11:07 UTC,I'm +1 on throttling reloads; I think that is the most obvious and critical work item for the MAAS team to address. I have filed that as bug #1710308.
1710278,2017-08-12 01:12:31 UTC,I attempted to reproduce the bind9 issue by doing the following (in two separate sessions):
1710278,2017-08-12 09:12:22 UTC,"On 12/08/17 01:11, Mike Pontillo wrote:

> Finally, I think your last bullet requires more discussion before we can
> work on it. MAAS currently uses sudoers rules specific to the init
> system to start and stop services like bind9; we do not currently have
> permission to 'kill -9' arbitrary processes. I'm concerned that if we go
> down that road, we would open up the possibility that MAAS could
> erroneously (or due to a malicious attack) believe that bind9 isn't
> working and repeatedly kill it without good cause, or be convinced to
> 'kill -9' an incorrect process.
"
1710278,2019-07-19 19:41:10 UTC,"Another test build ready.
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1710278"
1710278,2017-08-12 12:54:55 UTC,"Maybe dns dynamic updates could be used instead of zone reloads if just a
few IPs were added or removed."
1710278,2017-08-14 22:53:02 UTC,"Mark, if you observe the deadlock again, can you run ""systemctl stop bind9"", wait a few minutes (at least 2, but maybe up to 5), and then check if bind9 successfully stops? It looks like systemd will (by default) resort to more aggressive methods to kill a service if it doesn't stop after ~90 seconds."
1710278,2017-08-15 14:48:27 UTC,"OK, will do, thanks :)"
1710278,2017-08-18 15:17:21 UTC,"OK, restarting via 'sudo service bind9 restart' does work in the end, it just takes a long time. The downside is that MAAS is not going to have an effective DNS for a few minutes, which is unacceptable."
1710278,2017-08-18 20:58:43 UTC,Thanks. I wonder if we shouldn't fix this in Ubuntu by tweaking the systemd control files so that the timeout values are more acceptable for production use.
1710278,2019-02-20 15:03:27 UTC,"Hold on, I think this bug is still problematic for MAAS and Ubuntu."
1710278,2017-08-12 09:14:58 UTC,"To avoid reloads in parallel, I think we should:"
1710278,2019-06-26 15:12:09 UTC,"Mark,"
1710278,2019-02-20 15:13:54 UTC,"Hey Mark, was cleaning up bug tags; still consider this an issue."
1710278,2019-07-17 21:33:57 UTC,Test build in ppa:
1710278,2019-07-17 19:46:10 UTC,https://gitlab.isc.org/isc-projects/bind9/issues/1148
1710278,2019-07-17 18:29:35 UTC,This deadlock doesn't appear to be fixed in the latest upstream
1710278,2019-07-18 15:27:41 UTC,"Ok, updated the test build in ppa with locking for view->attributes as well, should fix this particular bind9 deadlock."
1710278,2019-07-17 21:40:30 UTC,"> Test build in ppa:
"
1710278,2019-07-17 18:24:21 UTC,"This is a deadlock in bind9 code; thread A runs ns_client_endrequest->dns_view_detach->view_flushanddetach, which includes:"
1710278,2019-07-10 16:05:05 UTC,repro.py attempts to trigger DNS queries during DNS Reloads.
1710278,2019-07-10 15:53:02 UTC,repro.py attached
1710278,2019-07-10 15:52:21 UTC,"OK - I was able to repro again, and this time with MAAS 2.6."
1710278,2019-07-10 08:57:32 UTC,"OK, interesting. I really don't like the reloading strategy but am not
sure that BIND gives us many better options. Let us know what you find."
1710278,2019-07-09 16:44:26 UTC,"Hi Mark,"
1710278,2019-06-27 08:01:01 UTC,"On 6/26/19 5:12 PM, Sam Lee wrote:

> When I compare our v2.5.3 install from our v2.4.2 install, the amount of
> rndc reloads is vastly more on v2.5.3.
"
1710278,2019-07-10 16:15:23 UTC,"I'm not sure why a ""broken"" Upstream DNS helps repro this bug, but I was not able to repro when the Upstream DNS was working."
1710283,2018-05-11 15:34:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1710283,2018-05-12 01:15:27 UTC,"There are many logs attached like the syslog, so you should have any information."
1710291,2018-02-13 09:39:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710293,2017-08-11 19:57:46 UTC,"Note: This is unrelated to, but precipitated from initial investigation into, bug 1709710."
1710293,2018-06-05 02:54:08 UTC,Here's a branch to implement these changes:
1710293,2018-06-05 16:45:18 UTC,Per Mike's recommendation I made some further removals of now-redundant code.  Pushed to same branch.
1710293,2020-10-15 19:01:29 UTC,Just squashed/rebased the branch and lightly tested.  Same location:
1710294,2019-07-14 02:33:35 UTC,Resolved since Cosmic.
1710296,2017-08-14 20:01:47 UTC,"Thanks for reporting this issue, what does /etc/update-manager/release-upgrades contain?"
1710296,2017-08-15 15:14:13 UTC,Yes i can connect to the changelog server.
1710296,2017-08-23 15:38:40 UTC,"Hello, the ticket is still marked as incomplete, what additional information do you need from me."
1710296,2017-08-30 15:55:11 UTC,"user@somenode:~$ ps -ef | grep check-new
root       5102      1  0 Jul30 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root       9228      1  0 Jul16 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      16718      1  0 Jul02 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      18286      1  0 Aug20 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      40711      1  0 Jun25 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      42309      1  0 Jul23 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      44891      1  0 Jun18 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      49048      1  0 Jun11 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      56328      1  0 Aug27 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      67336      1  0 Aug06 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root      89995      1  0 Jul09 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
root     130476      1  0 Aug13 ?        00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
user@somenode:~$ lsb_release -d
Description:    Ubuntu 16.04.2 LTS"
1710296,2018-01-02 16:33:26 UTC,"This is becoming a persistent problem on numerous servers that I monitoring/maintain.
I am seriously considering disabling this cron.
Is there anyway I could get some traction on this issue?"
1710296,2018-03-19 12:15:15 UTC,this issue persist
1710296,2017-08-14 20:13:37 UTC,"user@mm02archive:~# cat /etc/update-manager/release-upgrades
# Default behavior for the release upgrader."
1710296,2017-08-15 15:05:09 UTC,Can you connect to the changelog server?
1710299,2019-08-19 19:46:40 UTC,"Hi Bill,"
1710299,2019-08-19 20:44:20 UTC,"Hi Terran, just to clarify, this bug was opened before the Angular migration project started.  (Hence the ""Angular"" in the bug description -- I'll update that)."
1710299,2019-08-20 12:52:26 UTC,+1
1710302,2017-08-14 10:00:44 UTC,Something similar to https://bugs.launchpad.net/python-saharaclient/+bug/1560557 ?
1710302,2017-08-14 13:40:15 UTC,"Yes, same bug."
1710304,2017-08-14 14:59:38 UTC,"Redirecting sahara to openstack dataprocessing is a too much for a branch which is almost at its end of life.
While fixing the UI is possible, I advise to use the new CLI also in Newton."
1710304,2017-08-14 14:35:32 UTC,So was the idea to cause the sahara command to call the unified client in newton?
1710304,2017-08-14 13:53:36 UTC,I don't think we quite have the cause of the UI issue pinned down.
1710307,2017-08-12 00:19:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1710307,2017-08-12 00:28:00 UTC,"I'd love to know which package this is; it's part of the boot process, but (to my knowledge) there aren't any packages associated with the boot process."
1710310,2019-09-19 14:49:05 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1710313,2017-10-23 13:05:56 UTC,Looks like somehow 'python-configparser' is no longer installed on your desktop; try resolving using:
1710313,2017-10-23 13:06:28 UTC,Re-assigning to python-defaults (which provides python-minimal).
1710319,2020-07-01 21:18:07 UTC,"Thank you for your bug report, it does sound like a local issue during the installation than a package bug though"
1710321,2019-07-17 12:55:21 UTC,"Sounds more like a user question than a bug. If it is still an issue in stretch or buster, please report again with more details."
1710326,2017-08-21 08:43:35 UTC,Now Device Manger will display !   I made no further changes to cause this.
1710326,2017-08-12 05:27:19 UTC,I can print to paper.
1710326,2017-08-21 20:56:14 UTC,I get error - hpfax crashed with FileNotFounndError in _main_:[Errno2] No such file or directory:'/home/roger/.hplip/hp_fax-pipe-171'
1710331,2017-09-11 21:39:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710332,2017-08-12 06:50:33 UTC,"The inkscape.desktop.template file is used by po/CMakeLists.txt	but I
haven't found a	user of	inkscape.desktop.in, but I'm not sure if it is
safe to	delete.	 Also, it looks	to me like po/CMakeLists.txt could be
made to	load the file from packaging/ instead of the root dir, but I'm
not certain.  This would be worth further investigation."
1710332,2017-08-12 07:04:20 UTC,"not safe to delete one (depends on 'supported' gettext), but safe to move to another dir with the correct fixes to po/CMakeLists.txt and CMakeScripts/inkscape-desktop.cmake."
1710332,2017-08-12 07:31:25 UTC,"Thanks for the quick response, Mc!"
1710332,2017-08-12 08:32:26 UTC,"yeah but ""template"" is processes by gettext and "".in"" is processed by cmake."
1710341,2018-06-06 05:33:06 UTC,"I identified that most likely there was minimal security impact, however I reported the issue upstream via the security contact anyway.  They generally agreed exploit-ability didn't seem likely and so have simply applied a patch to stop using the bad RNG."
1710341,2017-08-12 08:56:06 UTC,Seems that viruuid.c:virUUIDGenerate tries to use virUUIDGenerateRandomBytes from /dev/urandom in preference to virUUIDGeneratePseudoRandomBytes which uses virRandomBits().
1710341,2017-08-18 11:24:56 UTC,"Hi Trent,"
1710341,2017-09-28 15:45:28 UTC,"Hi Trent,"
1710353,2017-09-29 21:57:49 UTC,"See this bug for Firefox. In a future release, Firefox will move its window control buttons to the same bar as the tabs which will save vertical space."
1710353,2018-01-25 07:12:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710354,2017-08-12 10:55:30 UTC,"StacktraceTop:
 OsAbort () at ../../../../os/utils.c:1355
 AbortServer () at ../../../../os/log.c:877
 FatalError (f=f@entry=0x999bd27f40 ""EnterVT failed for gpu screen %d\n"") at ../../../../os/log.c:1015
 xf86VTLeave () at ../../../../../../hw/xfree86/common/xf86Events.c:482
 WakeupHandler (result=result@entry=-1) at ../../../../dix/dixutils.c:427"
1710354,2018-02-26 18:42:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710362,2017-08-28 07:51:05 UTC,"Hello again,"
1710366,2017-08-12 16:20:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1710368,2017-08-12 13:30:04 UTC,This change was made by a bot.
1710370,2019-07-03 00:38:36 UTC,"Artful is EOL, and I just deleted the above mentioned PPA."
1710370,2018-03-14 17:28:52 UTC,I was able to reproduce this issue on the latest Fedora Rawhide under Wayland so this is an upstream issue.
1710370,2017-12-16 00:24:35 UTC,"This may be a long shot, but I encountered another problem on 17.10 with cheese: It starts with the message ""There was an error playing video from the webcam""."
1710370,2017-11-13 12:56:44 UTC,Done.
1710370,2017-11-25 14:42:28 UTC,Still happening on the latest Bionic build.
1710370,2017-12-09 17:52:08 UTC,I have just tested this on Fedora 27 under Wayland and Cheese works correctly when no camera is connected. So I am not sure if this is really an upstream issue.
1710370,2017-10-04 18:14:49 UTC,Still the same issue.
1710370,2017-11-13 10:28:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1710373,2017-09-15 17:33:02 UTC,This is an upstream issue: Vino VNC server does not support Wayland yet.
1710373,2017-11-09 16:28:42 UTC,I think this is at least in part a duplicate of bug 1730612.
1710373,2018-04-11 12:42:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710377,2017-10-15 15:15:58 UTC,That “Additional Drivers” has its own .desktop file at all is the result of two ancient accidents.
1710377,2017-10-17 14:42:17 UTC,"it's minor and we are not changing that for artful at this point, updating the tag according"
1710377,2019-05-11 15:30:49 UTC,Any news?
1710377,2019-05-29 06:07:41 UTC,This bug was fixed in the package software-properties - 0.98.3
1710377,2017-10-14 19:49:49 UTC,"Yes, software-properties-drivers.desktop has NotShowIn=GNOME;KDE;"
1710378,2017-08-12 14:25:03 UTC,Bug got also reported to Debian as
1710378,2017-08-13 16:47:45 UTC,It is fixed now. Thanks to OdyX from Debian for the quick fix.
1710378,2017-08-13 16:48:36 UTC,To the HPLIP developers at HP. Please apply the fix also upstream. Thanks in advance.
1710378,2017-08-13 16:54:32 UTC,To the HPLIP developers at HP:
1710379,2017-08-12 14:40:35 UTC,"StacktraceTop:
 init_jack () at /build/jack-keyboard-5Kr1NP/jack-keyboard-2.7.1/src/jack-keyboard.c:790
 main (argc=0, argv=0x7ffc3c6bf0f0) at /build/jack-keyboard-5Kr1NP/jack-keyboard-2.7.1/src/jack-keyboard.c:1858"
1710382,2018-01-23 18:22:08 UTC,I am also having the same problem w/ 17.10.
1710382,2017-12-06 09:35:19 UTC,Can you check bug 1736690 to see if it's the same bug as this?
1710382,2017-12-06 09:29:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710385,2017-08-12 16:20:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1710390,2019-01-11 19:08:37 UTC,"This is actually about two bugs in one and related to bug 1804841
Lets disambiguate them."
1710390,2018-09-11 11:08:52 UTC,Hardware is:
1710390,2018-09-11 11:06:20 UTC,I still have this:
1710390,2017-12-03 13:29:56 UTC,I have this bug. Can someone pls explain to me how to implement this workaround in more details?
1710390,2017-08-12 17:33:27 UTC,apport information
1710390,2017-08-12 17:33:25 UTC,apport information
1710390,2017-08-12 17:33:24 UTC,apport information
1710390,2017-08-12 17:33:23 UTC,apport information
1710390,2017-08-12 17:33:22 UTC,apport information
1710390,2017-08-12 21:49:04 UTC,"Ok, seems that there is a workaround for this problem.  Updating /etc/NetworkManager/NetworkManager.conf and adding this to the file did solve the problem."
1710390,2017-08-12 17:33:19 UTC,apport information
1710390,2017-08-12 17:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1710390,2017-08-12 17:33:21 UTC,apport information
1710390,2017-08-12 17:01:01 UTC,Driver is Intel Corporation Centrino Advanced-N 6230
1710390,2017-08-12 17:33:09 UTC,apport information
1710390,2017-08-12 17:33:10 UTC,apport information
1710390,2017-08-12 17:33:12 UTC,apport information
1710390,2017-08-12 17:33:29 UTC,apport information
1710390,2017-08-12 17:33:18 UTC,apport information
1710390,2017-08-12 17:33:14 UTC,apport information
1710390,2017-08-12 17:33:15 UTC,apport information
1710390,2017-08-12 17:33:17 UTC,apport information
1710390,2017-08-12 17:33:13 UTC,apport information
1710392,2017-09-10 01:21:25 UTC,http://kernel.ubuntu.com/git/kernel-ppa/mirror/linux.git/tree/drivers/mfd/intel-lpss-pci.c
1710392,2017-08-14 19:32:18 UTC,"I changed it to confirmed, although I am the reporter."
1710392,2017-08-14 19:30:15 UTC,The bug exists upstream in 4.13-rc4
1710392,2017-08-14 19:21:43 UTC,No.
1710392,2017-08-14 19:09:15 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1710392,2017-08-12 17:01:50 UTC,"I searched the WWW for any kind of solution to the trackpad not being recognized.  There are several months of similar questions, but no resolution.  Until this patch was made public/known."
1710392,2017-08-12 17:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1710392,2017-08-14 19:23:29 UTC,"Sorry, to answer the first question, the latest kernels do boot on the machine, the trackpad isn't recognized and doesn't respond to anything at all."
1710399,2017-08-17 18:01:46 UTC,"More specifically, the release file says:"
1710399,2017-08-17 18:02:52 UTC,"Same for all other releases, not just trusty."
1710399,2017-08-18 13:14:18 UTC,"Here: https://github.com/xemul/criu/issues/376 we were told that
""ppc64el is a ports architecture, and therefore the security pocket is hosts on ports.ubuntu.com/ubuntu-ports not on security.ubuntu.com domain."""
1710399,2017-08-17 17:59:18 UTC,"The files went away from the mirror, but are listed as available. Reassigning to launchpad."
1710409,2017-08-12 20:12:12 UTC,"Phew, can't say if this test is portable. It's pretty low-level, and the failure you see is not actually testing any functionality yet, just preparing stuff."
1710409,2017-08-13 20:32:33 UTC,Thanks for looking at this.
1710412,2017-08-13 07:58:00 UTC,I found a workaround: I copy and paste an old rectangle (from an old file). Than I change the filename (and directory) in the inbuilt XML Editor.
1710415,2017-12-24 13:25:15 UTC,"I have exactly the same issue on Linux Mint 18.3 Cinnamon, Inkscape 0.92.2"
1710416,2017-08-26 13:48:49 UTC,"Worked around in https://git.launchpad.net/ltsp-manager/commit/?id=f1089eebbc0c3225688b286c4d721d4d9fe77a0c, will properly fix it later on."
1710418,2017-08-12 21:14:31 UTC,I received the following email from Dropbox about this.
1710418,2017-09-20 16:25:50 UTC,Just wanted to mention that this is going to be broken in about a week.
1710418,2017-09-20 17:16:20 UTC,"Thanks for the information, unfortunately, there seems to be no devs to take care of it..."
1710418,2017-09-20 17:28:43 UTC,Too bad as I use this quite often.. :(
1710418,2017-09-23 16:10:14 UTC,"I had a look on what has to be done. It looks like Dropbox's API v1 has both OAuth1 and OAuth2 support. Shutter was using OAuth1 (importing the Perl module http://search.cpan.org/~kgrennan/Net-OAuth/ which also only supports OAuth1). The new Dropbox API v2 only supports OAuth2. This means, it is not just a matter of changing some API related paths, but changing from OAuth1 to OAuth2 and therefore switching to a different Perl library."
1710418,2017-10-02 09:17:43 UTC,"Dead now and not working:
http://pix.toile-libre.org/upload/original/1506935257.jpg"
1710418,2017-10-02 10:11:48 UTC,Until it starts working I just save the image to my dropbox folder and fetch a dropbox link in Nautilus. But I hope it will get fixed eventually!
1710418,2018-04-17 17:53:41 UTC,"After seeing http://shutter-project.org/2017/09/after-a-long-time-a-new-bug-fix-release-0-94/, I thought this might be fixed. But alas, it isn't. It is the lone reason I stopped using this amazing piece of software."
1710419,2017-09-23 20:43:07 UTC,A diff with the fix is attached.
1710419,2017-09-24 00:33:04 UTC,"The attachment ""diff.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1710419,2017-09-23 11:03:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710419,2017-09-23 11:20:26 UTC,I have this problem too. For me it appeared between 4.4.0-87-generic and 4.4.0-89-generic on 16.04 LTS. I have confirmed it by rebooting multiple times with both kernels.
1710419,2017-09-23 12:06:55 UTC,"Some more information:
- Attaching full dmesg of working and non-working boot. Also .ko from working and non-working kernel (although I doubt there is any debug info in there)
- I am using different hardware than the original poster, WinTV HVR-1900 Model 73219 LF, rev D2F5, but the same driver
- There is also someone else affected by the bug here: https://askubuntu.com/questions/945568/no-dev-mount-for-usb-device
- The newest kernel available for me on 16.04 LTS is also affected, 4.4.0-96-generic."
1710421,2017-08-13 21:21:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710421,2017-08-13 20:46:53 UTC,"Not only is this functionality useful, it is part of many people's workflows, and is expected at this point."
1710421,2017-08-13 21:21:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1710421,2018-10-19 11:24:49 UTC,"If @nrbrtx had offered any good advice at all, it's that someone else on the same page said that Super+H can perform the minimize (hide) action that I sought. I'll try this. It doesn't resolve the menu bug but it'll get me my missing keyboard functionality."
1710421,2018-10-19 10:25:51 UTC,"Thanks @nrbrtx for the link. Unfortunately, I use"
1710421,2018-10-19 09:43:50 UTC,@Ritesh see the full list of alternatives in this AskUbuntu Q&A - https://askubuntu.com/a/1073932/66509 .
1710421,2020-08-11 18:22:02 UTC,"On Tue, 11 Aug 2020, 11:51 Daniel van Vugt, <email address hidden>
wrote:"
1710421,2018-09-16 02:42:43 UTC,"Not sure if this is the same bug, but recently I've lost the ability to use the Enter key on the window menu. Alt+Space works, the Up/Down arrows work on the menu, but pressing Enter does nothing. Are these things related somehow?"
1710421,2018-05-07 04:07:55 UTC,"Also worth noting: Keyboard navigation of the window menu is still possible, just slower:"
1710421,2018-05-07 02:54:46 UTC,Ubuntu did not design or write the relevant code here. It's not our choice. Just that nobody in the world has implemented it yet.
1710421,2018-05-06 16:24:32 UTC,"It is unbelievable, Ubuntu 18.04 LTS is released with this bug.
I can't understand for whom you are designing you smart new glossy desktop."
1710421,2018-10-19 08:41:27 UTC,"I am facing the same issue. Unable to use enter key to select any menu option. Moreover, enter does not work on top right menu which manages wifi, sound level, screen brightness etc. Seems like these issues are related."
1710424,2017-08-13 06:37:46 UTC,"Debian maintainer here, thanks for providing patches for wx3.x compatibility! I'll apply those patches to the codeblocks package in my next upload."
1710424,2017-08-13 09:05:49 UTC,"@Vincent:
Yes, we have see rev 11006 in trunk and rev 11145 in the release branch."
1710424,2017-09-22 12:36:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710437,2017-08-15 06:25:19 UTC,"In charm-helpers, fetch/ubuntu/import_key does not handle comments and insists there is nothing before or after the PGP key block. Which is a rather fragile way of handling the recommended case, and punting everything else off to the known insecure keyserver retrieval."
1710437,2017-08-15 08:08:20 UTC,Worked around in the PostgreSQL charm by making the embedded key match current charm-helpers constraints
1710443,2017-08-26 17:49:50 UTC,Namaste tanmoy.
1710443,2017-08-26 15:14:51 UTC,Mathematically boundaries are correct in the boundary.dat file. But The mathematical division does not fit with the division made with main star or Yogtara. So boundary implementation create more confusion for general users. More than 40% of Constellations or Nakshatra lies outside its mathematical boundaries. I think boundary implementation by default is not a good idea.
1710443,2017-08-23 18:37:20 UTC,"Thanks, alexander - an update to the guide is indeed useful.
I have opened https://bugs.launchpad.net/stellarium/+bug/1712641 , but in the meanwhile we can stick with constellations to represent both raashi-s and nakShatra-s."
1710443,2017-08-26 18:11:23 UTC,"Considering the above, I now wonder if we should take the following approach instead to clearly *see* the division of the ecliptic based on raashi-s and nakshatra-s :"
1710443,2017-08-23 15:54:13 UTC,I think I should update subsection 9.8 in the Stellarium User Guide.
1710443,2017-08-24 21:41:28 UTC,It delights me that so far shrI tanmoy's boundaries help me so that - I can for the first time **see** that the moon is in hasta - http://imgur.com/a/AJXF5 compared with http://www.prokerala.com/astrology/nakshatra-finder/?date=2017-08-25&time=03%3A06&loc=1277333&p=1 !
1710443,2017-08-26 18:50:30 UTC,"> In the future, if and when stellarium supports specification of longitudes by skycultures (as originally requested in this thread), we may elide this roundabout ""boundary"" technique.
"
1710443,2017-08-27 01:27:32 UTC,Ah - all is well; it was a false alarm. Comment #31 holds.
1710443,2017-08-26 20:44:44 UTC,"I catch the drift from both @alexwolf and tanmoy's comments that you feel that the desired partition boundaries should not be implemented as nakShatra boundaries (based on conceptual ugliness in the force-fit, rather than any user inconvenience). This is reasonable. Perhaps we can use separate imaginary nakShatra-s as a stop-gap solution, as proposed."
1710443,2017-08-26 22:38:54 UTC,"namaste tanmoy, I finished writing code to produce the nakShatra-strip-boundaries - https://github.com/sanskrit-coders/jyotisha/blob/master/jyotisha/zodiac.py ."
1710443,2017-08-27 01:13:32 UTC,Please ignore the last comment above - There's possible bug https://github.com/sanskrit-coders/jyotisha/commit/86c13cb0e3cf51bb9eb6a4726a047f0afdec97fc##commitcomment-23899164 .
1710443,2017-12-18 02:37:05 UTC,I await a response for #30 . Mainly:
1710443,2018-09-26 06:15:14 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/437
1710443,2017-08-23 15:52:03 UTC,"> 2 CON1 CON2 legacy data. They indicated “border between 2 constellations, CON1, CON1” but are now only required to keep the format.
"
1710443,2017-08-26 19:38:19 UTC,Hi @alexwolf -
1710443,2017-08-23 15:47:32 UTC,"Yes, it's correct. We use separate file for asterisms now."
1710443,2017-08-13 07:30:47 UTC,"No dashed line, but boundaries of the constellations is possible - see data/constelaltions_boundaries.dat file for details. Similar file should be created for Indian skyculture (he should be put with other files of skyculture)."
1710443,2017-08-23 12:46:08 UTC,"I used stellarium to get those coordinates.
Just use:   bzr branch lp:~t4saha/stellarium-skycultures/indianV2boundary in terminal then change accordingly and commit and push the update."
1710443,2017-08-13 05:17:59 UTC,You can update the Indian vedic skyculture and propose patch for us.
1710443,2017-08-13 05:44:30 UTC,"@alexwolf, gladly - but I need to know the following:"
1710443,2017-08-13 19:08:46 UTC,"Thanks for the idea. How do I understand what each line means? For example, what is each field in this line:"
1710443,2017-08-14 11:12:26 UTC,This line need read as: 3 couples of coordinates (with sequence of RA & Dec for each point) for border between 2 constellations - AQL and AQR.
1710443,2017-08-16 23:44:43 UTC,"hi @alexwolf :  I want to draw a line between the ecliptic poles via http://simbad.u-strasbg.fr/simbad/sim-id?Ident=Beta+Arietis , but:"
1710443,2017-08-17 03:25:03 UTC,"RA is given in decimal hours, not degrees."
1710443,2017-08-17 04:15:25 UTC,"Thanks- Just to double check, would 1 hour 54 minutes be 1+54/60 (and not 1.54)? Also do you know of any website which would, given a star, provide the decimal hour for a given star (like http://simbad.u-strasbg.fr/simbad/sim-id?Ident=Beta+Arietis )?"
1710443,2017-08-17 04:32:07 UTC,"I've deduced the answer to my first question by experimenting - and things look good so far - http://imgur.com/a/NITiZ . Once I get an answer for the second question, I should be able to rapidly add the other 26+ boundaries."
1710443,2017-08-17 06:25:01 UTC,wolframalpha maybe useful tool here
1710443,2017-08-17 16:48:07 UTC,"shrI tanmoy in https://bugs.launchpad.net/stellarium/+bug/1710444/comments/15 and https://bugs.launchpad.net/stellarium/+bug/1711229 claims: ""There is no mention of specific boundary co-ordinates of constellations in any authentic Vedic scripts or any papers, except that the ecliptic is divided into 27 equal parts of 13deg20"". As such boundary or gridline implementation may not be correct."""
1710443,2017-08-17 21:06:04 UTC,"A bit of clarification regarding [1] above. yoga-tAra-s are supposedly the most prominent stars *within* a naxatra-division, and do not by themselves specify the start of the respective divisions. Rather, sUrya-siddhAnta and vedAnga-jyotiSha specify start coordinates for the 13deg20 divisions using other stars (Please see penultimate paragraph in the next page: https://archive.org/stream/HistoryOfCalendarPanchangaCommittee/History-of-Calendar-Panchanga-Committee#page/n42/mode/1up )."
1710443,2017-08-23 05:24:42 UTC,"@alex, I think you missed my question in https://bugs.launchpad.net/stellarium/+bug/1710444/comments/16 : ""are the last 2 fields in `3 18 66.82 1.9 20.80803147 6 -66.82 2 N27 N01` of any significance at all? Can they correspond to asterisms?"""
1710443,2017-08-23 05:33:11 UTC,"shrI tanmoy in https://bugs.launchpad.net/stellarium/+bug/1710444/comments/19 onwards says: ""Yes and that will create more confusion for most of the general users. That's why I think boundary implementation should be avoided but transliteration is very good idea. Pro user can implement this for their own use. We may provide a link in description to download the boundary.dat file but in default package it should not be included. ... I also created the boundary in first time but when I show some of my friends who uses stellarium regularly basis their opinion was it was confusing. ... "" and attaches https://launchpadlibrarian.net/333918325/im2.png to illustrate the source of the confusion."
1710443,2017-08-23 05:42:12 UTC,"shrI tanmoy in says: ""Found my old boundary.dat file and attached to the branch.
https://code.launchpad.net/~t4saha/stellarium-skycultures/indianV2boundary "" This seems to solve the nakShatra-boundary problem. @tanmoy can you tell me how exactly you deduced these coordinates? Did you use a script? If everything looks good, we can just use that file to take care of this bug."
1710443,2017-08-23 07:13:26 UTC,"> ""are the last 2 fields in `3 18 66.82 1.9 20.80803147 6 -66.82 2 N27 N01` of any significance at all? Can they correspond to asterisms?""
"
1710443,2017-08-23 15:17:13 UTC,"@alexwolf, the user guide states:
```
N RA_1 DE_1 RA_2 DE_2 ... RA_N DE_N 2 CON1 CON2
  where
  N number of corners
  RA_n, DE_n right ascension and declination (degrees) of the corners in J2000 coordinates.
  2 CON1 CON2 legacy data. They indicated “border between 2 constellations, CON1, CON1” but
  are now only required to keep the format.
```"
1710443,2017-08-13 05:55:46 UTC,"First question remains, but regarding the second question above a modification: I now realize that http://bazaar.launchpad.net/~stellarium/stellarium/trunk/view/head:/skycultures/indian/constellationship.fab lists the stars. But, how to show a boundary - ie surround these stars (82396 82545 82545 82729 82729 84143 84143 86228 86228 87073 87073 86670 86670 85927 85927 85696) with a dashed line?"
1710444,2017-08-18 11:35:32 UTC,"I know these boundary co-ordinates. But problem is that in this system some major stars or Yogtara and parts of nakshatra will lie outside their boundaries. To solve this if we unevenly distribute the boundary range (not 13 deg 20"") then calculated data will not match with the observed data."
1710444,2017-08-13 05:23:02 UTC,Please update the Indian vedic skyculture and propose patch for us.
1710444,2017-08-13 18:23:20 UTC,"Alas, stellarium does not support accented roman characters (part of UTF8) used with IAST (http://i.imgur.com/RLEwheO.png from the 3rd and 4th commits in https://github.com/sanskrit-coders/stellarium/tree/patch-1/skycultures/indian ). Given this, switching over to a faithful phonetic rendering (with the intuitive OPTITRANS schema - https://sites.google.com/site/sanskritcode/optitrans#TOC-History ) seems the way to go. Do you agree, @alexwolf?"
1710444,2017-08-13 19:48:23 UTC,(PS: I'm not sure why git is not showing the file contents in utf-8 encoding. My local files look like - https://pastebin.com/h6JfRi7W )
1710444,2017-08-14 11:01:54 UTC,"Stellarium is support UTF8 encoding for .fab files - could you check encoding of file and show a name of text editor, what you are using?"
1710444,2017-08-14 17:36:05 UTC,"Thanks! I've fixed the file encoding problem (was using Intellij). Everything looks good, except for śrāvaṇa - http://imgur.com/a/QPeWB - I don't know where the text with ? is coming from. I've sent https://github.com/Stellarium/stellarium/pull/3 ."
1710444,2017-08-15 08:14:15 UTC,Please read the Chapter 9 of Stellarium User Guide.
1710444,2017-08-15 14:50:20 UTC,"namaste alex, http://www.stellarium.org/wiki/index.php/Creating_a_Script_for_Stellarium was what I got. But I did not understand why you pointed to it - is the pull request all right?"
1710444,2017-08-15 15:25:58 UTC,"I'm sorry, but you read outdated version of User Guide (see right top corner: Information is actual for version 0.13.1)"
1710444,2017-08-16 05:16:40 UTC,Ah - got it! Fixed the files to conform and it makes much more sense - http://imgur.com/a/V0VWr . Please take another look.
1710444,2017-08-16 09:41:51 UTC,"OK, it looks good for me now"
1710444,2017-08-16 09:45:05 UTC,I have a question for star_names.fab data - is it really correct transliteration? Could you add a comments for translators?
1710444,2017-08-16 14:52:03 UTC,"I checked the transliteration again, and it looked fine except for a couple of missing accents (they can be checked at http://www.sanskrit-lexicon.uni-koeln.de/scans/awork/apidev/sample/list-0.2.html by setting input to IAST). Added comments for translators."
1710444,2017-08-17 16:30:33 UTC,namaste tanmoy -
1710444,2017-08-16 19:19:12 UTC,https://code.launchpad.net/~t4saha/stellarium-skycultures/indianV2
1710444,2017-08-16 19:48:09 UTC,"namaste tanmoy! Thanks for the pointer, and for your pioneering work 🙏. I am far more comfortable with github than on launchpad, but I found my way to changes in http://bazaar.launchpad.net/~t4saha/stellarium-skycultures/indianV2/revision/95#indian/star_names.fab . There are several conflicts between those files and https://github.com/Stellarium/stellarium/pull/3/files . It would be good to resolve them and proceed further, so that duplicated effort can be avoided and the skyculture grows richer faster.  I think we can do more together (I invited participation in this thread as well - https://groups.google.com/forum/#!topic/sanskrit-programmers/btt7Cz1BM2U ). If you're comfortable with github, (once we discuss and agree on the way forward) would you care to join my repository and do the merge?  I am currently focusing on adding grid lines along the yogatArA-s."
1710444,2017-08-20 10:43:08 UTC,https://code.launchpad.net/~t4saha/stellarium-skycultures/indianV2
1710444,2017-08-20 06:13:21 UTC,Yes and that will create more confusion for most of the general users. That's why I think boundary implementation should be avoided but transliteration is very good idea. Pro user can implement this for their own use. We may provide a link in description to download the boundary.dat file but in default package it should not be included.
1710444,2017-08-26 17:53:51 UTC,"I received the following notification:
""
** Branch linked: lp:~t4saha/stellarium-skycultures/indianV2"
1710444,2017-08-24 21:32:58 UTC,"Thanks for clarifying, @tanmoy. @alexwolf, I think we have agreement here. This particular thread can be closed by accepting https://github.com/Stellarium/stellarium/pull/3/files . It should also take care of https://bugs.launchpad.net/stellarium/+bug/1710443 (I've for now copied tanmoy's boundaries - cross-checking will take more time)."
1710444,2017-08-23 05:23:19 UTC,"namaste tanmoy, thanks for the comments - I will address them in https://bugs.launchpad.net/stellarium/+bug/1710443 . We should broadly stick to the subject of this thread here. Back to that topic: Can we solve the inconsistency between your branch and my pull request? We could use the following principles:
* Use standard Sanskrit words (with perfectly the right syllables)
* Use IAST for devanAgarI transliteration.
* Use the most direct English translation, following the standard entries in the vAchaspatyam and kalpadruma sanskrit-to-sanskrit dictionaries which provide native etymology."
1710444,2017-08-17 10:15:56 UTC,"1.There is no mention of specific boundary co-ordinates of constellations in any authentic Vedic scripts or any papers, except that the ecliptic is divided into 27 equal parts of 13deg20"". As such boundary or gridline implementation may not be correct.
2.nakshatra's are more like asterisms. Changing them into that category we can separately view them from Constellations (rashi) with different colors or the other way.
3. We can not expect to use this ancient data to observe modern things and modifying to match current observations or astrological things makes it non-vedic and may end up with a alternative Indian sky culture."
1710444,2017-08-18 17:04:56 UTC,"namaste tanmoy, Indeed it is true that a few of the yogatArA-s (going by their mainstream identification) will lie outside their boundaries - in which case, any resultant problem (with regards to ritual timing or astrology) should be solved by other means (some people propose alternate identifications for such yogatArA-s). But in most of the cases, no such problem arises. In either case, careful practitioners of the tradition do not give up on current observations."
1710444,2017-08-23 13:10:01 UTC,"Yes names are used accordingly IAST.
I am not very use to with Sanskrit.
I get help from one of my school old teacher and friends for right syllables and meanings. I don't know which dictionary they used.
You may Update if there is any irregularity with syllables and meanings."
1710444,2017-08-20 06:33:57 UTC,I also created the boundary in first time but when I show some of my friends who uses stellarium regularly basis their opinion was it was confusing.
1710447,2018-05-11 15:34:18 UTC,This change was made by a bot.
1710447,2017-08-18 11:20:15 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1710453,2017-08-14 20:26:53 UTC,fixed in v4.13-rc4 mainline build
1710453,2017-08-14 19:08:53 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1710453,2017-08-13 12:30:07 UTC,This change was made by a bot.
1710453,2017-08-13 11:54:47 UTC,apport information
1710453,2017-08-13 11:54:45 UTC,apport information
1710453,2017-08-13 11:54:42 UTC,apport information
1710453,2017-08-13 11:54:39 UTC,apport information
1710453,2017-08-13 11:54:41 UTC,apport information
1710453,2017-08-13 11:54:37 UTC,apport information
1710453,2017-08-13 11:54:36 UTC,apport information
1710453,2017-08-13 11:54:34 UTC,apport information
1710453,2017-08-13 11:54:32 UTC,apport information
1710453,2017-08-13 11:54:31 UTC,apport information
1710453,2017-08-13 11:54:29 UTC,apport information
1710453,2017-08-13 11:54:28 UTC,apport information
1710453,2017-08-13 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1710453,2017-08-13 11:54:38 UTC,apport information
1710453,2017-08-13 11:54:40 UTC,apport information
1710474,2017-09-04 14:13:16 UTC,"Marking as a feature bug; we have basic bluestore support in for the next release, these further improve the support to allow broader configuration of WAL and DB devices for bluestore configurations."
1710474,2017-09-04 14:36:21 UTC,I have reviews here which I tested with config options and juju storage on MAAS. I submitted them on the Pike charms freeze day so they did not make it there.
1710474,2018-01-05 16:13:20 UTC,"Reviewed:  https://review.openstack.org/497691
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=189e7620c07d81c5fdaa2c680c51ffd2d29f168b
Submitter: Zuul
Branch:    master"
1710474,2019-05-30 12:03:00 UTC,Marking the charm-ceph task wontfix as the ceph charm has been removed from support for a while now
1710477,2017-09-06 11:36:23 UTC,"1) ok that's a great release note and addition to the ceph-mon/ceph-osd docs
2) that can happen next development cycle (not for 17.08)"
1710477,2017-09-04 16:09:34 UTC,I think there are a few potential bugs here; specifically please can we break out
1710477,2017-08-14 07:37:46 UTC,The converged architecture issue shouldn't be too problematic as the Ubuntu packages for Ceph intentionally do *not* restart running ceph* services on upgrade specifically to assist with not taking down the world.
1710477,2017-09-06 11:16:35 UTC,1. Agreed. A change of a storage backend does not affect what gets transferred over the wire so this can be an action-based feature.
1710477,2017-08-14 07:11:41 UTC,"For a converged architecture where nova-compute resides on the same host as ceph-osd there is another potential problem: if nova-compute is upgraded before ceph-osd, ceph packages will get upgraded as well due to `apt upgrade` before ceph-mons are upgraded on other units (although an osd process might still be running with an old version unless explicitly restarted)."
1710478,2017-12-14 13:11:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710478,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1710489,2017-09-13 17:19:00 UTC,Bug still:
1710489,2018-02-02 16:52:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710494,2019-08-08 14:44:30 UTC,Debian and Ubuntu are now in sync (Eoan) with audacity upstream on Version 2.3.2.
1710515,2017-08-16 20:38:05 UTC,"Thanks a lot Vej !
You are right, but i'm a bit unconfortable with this solution which i'm not at all familiar with and which will probably take time and nerves ;-)
Well, if nothing else works, i'll try the ""duplicity"" thing."
1710515,2017-08-21 20:39:13 UTC,"Ok, After the ""restore one file only"" method, everything restored in Thunderbird from second back up !!!"
1710515,2017-08-14 22:04:51 UTC,"Ok, now i've tried the ""restore-missing-file"" method at the lowest level of directory (/q21d1m3p.erijou/Mail/Local Folders/Inbox for example)."
1710515,2017-08-14 20:08:18 UTC,"there are some information in this directory that are private and/or ""confidential"" professionally speaking (i don't work in the military or in the nuclear industry ;-) )
So it would bother me to send it to someone, but depending on where you are, i can come and give you access to the back up, as long as i can see what is done with it.
I work in Paris France, are you in the US or UK ? (seeing you answering at times that are 3am for me makes me think it's the first option...)"
1710515,2017-08-14 16:37:34 UTC,"Oh for sure, someone (thunderbird, duplicity, deja-dup) is screwing up. With the limited information I have so far, I'm going to guess duplicity (deja-dup doesn't deal too directly with issues of file permissions, but maybe we are trying to be too clever for our own good in some way or maybe we should have reported some error back when the original backup was being made that we didn't )."
1710515,2017-08-14 16:20:49 UTC,"Ok, thanks again, i'll try it as soon as i can.
But it is very strange that i found other examples on the web in which directories involved are always different but ALWAYS include vital thunderbird files.
It's also strange that among maybe 15000 + directories, it's only 25 of them that have the problem and among those 25, 17 are about Thunderbird..."
1710515,2017-08-14 14:22:07 UTC,"Ugh. I'm so sorry this is happening to you. For whatever reason, deja-dup isn't working. I think your best bet is digging into it manually with duplicity or, if even that still has the problem, manually unpacking the tarballs. Instructions on that are here:"
1710515,2017-08-14 01:28:41 UTC,"ok, i'll do that, and i'll also give you all the info you want WHEN the problem is solved ;-)
For the moment, i let my copy by itself and i'm going to get some rest, i really need that..."
1710515,2017-08-14 12:11:17 UTC,"I wrote ""retired"" i meant ""restored"".
Well, restoring all on a new place is in progress, don't have much hope in it: i already checked the .thunderbird dir size and it's the same as before..."
1710515,2017-08-14 01:46:33 UTC,"If it may help, list of the files that were not retired after "" deja-dup --restore ~/.thunderbird "":"
1710515,2017-08-14 01:16:27 UTC,"Hmm, I'm sorry you're still having the problem.  :(  When this is done and you have your files, I'd be interested in digging into what's causing that."
1710515,2017-08-14 00:46:43 UTC,"OK so you could use duplicity directly. But first, let's try using deja dup again. Deja dup doesn't have a mode that lets you restore just some files to a new location. But it does have a mode that lets you restore just some files to the original location."
1710515,2017-08-14 00:33:49 UTC,"Dear Michael,"
1710515,2017-08-13 23:55:03 UTC,"The message might be because you chose ""restore files to original locations"" and for some reason the file permissions on your thunderbird folders are problematic?"
1710515,2017-08-14 12:36:09 UTC,"Ok, restore to a different location ended up the same.
Unrestored directories list:"
1710515,2017-08-14 00:58:26 UTC,Thank you again for your help Michael.
1710515,2017-08-16 07:28:38 UTC,Hello Leroy!
1710517,2017-08-16 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1710517,2018-04-10 19:07:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1710517,2017-08-17 09:35:07 UTC,->Confirmed.  The title says it all really.  I'm on xenial at the moment.
1710517,2017-08-19 07:03:00 UTC,The raspi 64 bit kernels in zesty also don't have EFI stub enabled.
1710517,2017-11-03 19:54:38 UTC,Raspbian (http://archive.raspbian.org/raspbian/pool/main/l/linux-4.9/ ) have EFI stub enabled on their kernels.
1710534,2019-03-20 01:21:21 UTC,Can reproduce with Inkscape 0.92.4. This seems inconsistent with other input fields so I guess it's more of a bug than a feature request?
1710534,2019-03-20 01:44:39 UTC,"Still the same with Inkscape master, too."
1710534,2020-09-21 18:57:52 UTC,Closing because INVALID.
1710535,2018-03-01 10:22:14 UTC,"Watcher team have discussed it and we have found the following solution:
1. Advice to use auto-trigger option for consolidation strategy.
2. As of starting Action Plan we check for new instances.
3. Watcher consume notifications from Nova during Action Plan execution.
4. If second and third steps are true, Watcher send a notification about changing of cluster state."
1710548,2017-08-14 06:00:06 UTC,This change was made by a bot.
1710548,2017-08-14 19:07:11 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1710548,2017-08-16 00:59:36 UTC,"Thank you, Joseph!"
1710548,2017-08-16 01:04:27 UTC,Placeholder for attachment
1710548,2017-08-16 01:14:32 UTC,"Post script: these warnings do not crash or otherwise interfere with system operation.  ZoneMinder, in particular, `seems to function just fine."
1710548,2017-08-16 01:34:14 UTC,"Will sit, and think, and talk to you soon."
1710548,2017-08-17 23:30:11 UTC,Placeholder for DMESG attachment after the fix incorporated by  Kai-Heng Feng in
1710548,2017-08-17 09:59:04 UTC,Here you go:
1710548,2017-08-17 23:38:43 UTC,"Placeholder for DMESG attachment after the fix, sorry: file extension collision."
1710548,2017-08-18 04:23:31 UTC,You can check the patch here: https://lkml.org/lkml/2017/8/18/4
1710548,2017-08-20 01:05:04 UTC,Title and post edited to reflect actual chipset name Renesas / NEC - µPD720202 not 27xxx2 as initially and mistakenly reported.
1710548,2017-10-23 22:46:29 UTC,"Curious as to when this fix will propagate into mainline. Haven't looked into it very deeply, but it seems that kernel/""ubuntu base"" updates trounce the fix."
1710548,2018-03-25 21:55:23 UTC,Bug still exists in 4.15 kernel/Bionc Beaver
1710548,2018-03-26 04:26:47 UTC,"This was my attempt to send a quirk patch:
https://lkml.org/lkml/2017/9/6/516"
1710548,2018-04-27 07:44:48 UTC,"Hmm, having resigned to building my own kernels for the foreseeable future, I DL'd the source tree for bionic and took a peek at xhci-pci.c It looks like someone has tried to incorporate the patch of interest. I find:"
1710548,2018-05-08 05:42:35 UTC,Yeah it's a typo.
1710548,2018-05-08 05:51:12 UTC," Hi,
It looks like someone attempted a fix, but it was beset by a typo. I fixed the typo and compiled the kernel and the issue was resolved. I detailed the typo in the original thread. Can you run this up the flagpole for me? I don't know how to get in touch with the devs.
Thank you,
-Jeff
    On Sunday, March 25, 2018, 9:36:06 PM PDT, Kai-Heng Feng <email address hidden> wrote:"
1710548,2018-10-01 02:14:35 UTC,This may be related.
1710548,2017-08-17 22:56:53 UTC,"Dear Kai-Heng Feng,"
1710561,2017-12-28 11:05:56 UTC,Bug confirmed still present in Version: 2017-12-27 revision fab6fc69e (Win64 nightly under Win7)
1710573,2018-05-11 15:34:23 UTC,This change was made by a bot.
1710575,2017-08-14 09:01:05 UTC,There are many others USB Wi-Fi sticks that have the same chipset and the same bug : https://doc.ubuntu-fr.org/wifi_liste_carte
1710579,2017-08-15 22:36:19 UTC,"The postinst script has guards against adding the user if it exists already:
    if [ ! `getent passwd snmp >/dev/null` ]; then"
1710579,2017-08-15 22:42:21 UTC,They probably meant for the check to be:
1710579,2017-08-16 20:48:37 UTC,"Ok, got it. To reproduce the problem, before installing the snmpd package you need to have an snmp user with an uid that does not belong in the system user range. Something with an uid higher than 999."
1710579,2017-08-16 20:53:16 UTC,@~its-ashish can you please confirm that your existing snmp user (and group) have a high uid? Please show:
1710584,2018-05-17 12:00:24 UTC,доброго времени  госпо
1710584,2018-05-17 12:03:51 UTC,почему вы на меня так ополчились я только хотел вернуть свои право админа  у себя в ноутбуке
1710585,2017-10-27 10:44:25 UTC,Can you suppress your wsrep_sync_wait setting and re-try.
1710585,2018-01-18 08:20:56 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1999
1710585,2017-10-09 06:11:56 UTC,pt-pmp output of other node when issue happened
1710585,2017-10-09 06:14:12 UTC,"We again had DDL statment hang in ""checking permission"" state"
1710585,2017-10-09 06:11:22 UTC,We faced this problem again. Attaching pt-pmp trace from node with hang DDL command
1710585,2017-08-14 10:03:19 UTC,Can you help us with some reproducible use-case.
1710585,2017-08-14 10:20:36 UTC,The bug seems not to be easy reproducible
1710585,2017-08-15 11:18:15 UTC,When it stuck next time can you send us pt-pmp output. It will try to get a stack trace of what threads are stuck at. Any other way of generating stack trace is good enough.
1710585,2017-10-09 06:12:17 UTC,pt-pmp output of other node
1710587,2017-08-14 12:10:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/493523"
1710589,2017-09-05 06:34:02 UTC,"Reviewed:  https://review.openstack.org/492374
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=0eba6c8bb436970307651f5b19358cd9e0627cbd
Submitter: Jenkins
Branch:    master"
1710589,2017-08-15 16:41:49 UTC,Can we get a logstash link produced for that? It may help to understand how often it affects midonet. We don't see any major failure spikes in neutron gate for rally.
1710589,2017-08-14 22:11:59 UTC,Added neutron as it doesn't seem networking-midonet specific
1710589,2017-10-27 06:21:59 UTC,"In my environment,
The neutron-server log also prints the following error message.
""UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched.""
[Logs]
4124:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api [req-3a38738f-efbf-45b0-ae65-3af84f6aae2c - - - - -] DB exceeded retry limit.: StaleDataError: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched.
4125:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api Traceback (most recent call last):
4126:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/oslo_db/api.py"", line 138, in wrapper
4127:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api return f(*args, **kwargs)
4128:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/neutron/db/api.py"", line 128, in wrapped
4129:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api LOG.debug(""Retry wrapper got retriable exception: %s"", e)
4130:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/oslo_utils/excutils.py"", line 220, in _exit_
4131:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api self.force_reraise()
4132:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/oslo_utils/excutils.py"", line 196, in force_reraise
4133:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api six.reraise(self.type_, self.value, self.tb)
4134:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/neutron/db/api.py"", line 124, in wrapped
4135:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api return f(*dup_args, **dup_kwargs)
4136:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/neutron/plugins/ml2/plugin.py"", line 1702, in update_port_statuses
4137:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api context, port_dbs_by_id[port_id], status, host)
4138:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/neutron/plugins/ml2/plugin.py"", line 1714, in _safe_update_individual_port_db_status
4139:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api ectx.reraise = bool(db.get_port(context, port_id))
4140:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/oslo_utils/excutils.py"", line 220, in _exit_
4141:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api self.force_reraise()
4142:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/oslo_utils/excutils.py"", line 196, in force_reraise
4143:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api six.reraise(self.type_, self.value, self.tb)
4144:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/neutron/plugins/ml2/plugin.py"", line 1710, in _safe_update_individual_port_db_status
4145:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api context, port, status, host)
4146:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api File ""/usr/lib/python2.7/site-packages/neutron/plugins/ml2/plugin.py"", line 1769, in _update_individual_port_db_status
4147:2017-09-19 17:10:15.211 10600 ERROR oslo_db.api levels = db.get_binding_levels(context, port_id, host)
4148:2017-09-19 17:10:15.211 ..."
1710595,2017-09-25 10:29:35 UTC,This problem was not seen in recent days. Marking it as incomplete for now
1710601,2017-08-15 02:35:49 UTC,Please check to see if the bluetoothd process has gone away (crashed?) after the problem occurs. You might also want to look in /var/crash/
1710601,2017-08-15 11:37:03 UTC,This is not a crash. Nothing crashes. It just disconnects immediately after connect and bluetoothctl is frozen without sudo.
1710601,2017-08-15 11:16:21 UTC,apport information
1710601,2017-08-15 11:16:20 UTC,apport information
1710601,2017-08-15 11:16:19 UTC,apport information
1710601,2017-08-15 11:16:18 UTC,apport information
1710601,2017-08-15 11:16:17 UTC,apport information
1710601,2017-08-15 11:16:16 UTC,apport information
1710601,2017-08-15 11:16:13 UTC,apport information
1710601,2017-08-15 11:16:12 UTC,apport information
1710601,2017-08-15 11:16:11 UTC,apport information
1710601,2017-08-15 11:16:10 UTC,apport information
1710601,2017-08-15 11:16:09 UTC,apport information
1710601,2017-08-15 11:16:08 UTC,apport information
1710601,2017-08-15 10:59:49 UTC,"bluetoothd is still running after the problem occurs.
there is a /var/crash/_usr_lib_blueman_blueman-rfcomm-watcher.0.crash which in my opinion refers to an unrelated incident involving blueman. if you want I can upload the file."
1710601,2017-08-15 11:16:14 UTC,apport information
1710601,2017-08-15 11:16:15 UTC,apport information
1710622,2018-06-23 21:19:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710626,2017-08-14 13:41:18 UTC,The above was on Ubuntu 16.04 with 3.4.10-4ubuntu1.3
1710632,2017-08-14 14:59:52 UTC,Pending moderator approval but a suggestion is sent to https://www.redhat.com/archives/virt-tools-list/2017-August/thread.html
1710632,2017-08-14 14:09:16 UTC,This clearly is only wishlist
1710641,2018-03-02 13:46:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1710655,2018-02-20 15:22:47 UTC,"This bug continues on.  Currently running Mint 18.3, Mintstick v1.3.5"
1710671,2017-08-17 20:10:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710674,2017-08-15 18:48:30 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1710674,2017-08-14 18:04:19 UTC,"In one of the crashes, I saw:"
1710674,2017-08-31 18:00:03 UTC,I managed to apply -XX:+UseMembar to the JVM created by unit test.
1710674,2017-08-31 15:10:11 UTC,I tried the following passing the flag to JNI_CreateJavaVM() call:
1710674,2017-08-31 14:42:42 UTC,"I took a look at the core file and the stacktraces, but so far I couldn't pinpoint what might be causing that, much less reproduce it."
1710674,2017-09-06 22:33:34 UTC,Gentle ping.
1710674,2017-08-18 17:52:06 UTC,Is there any more information I should provide ?
1710674,2017-08-17 04:55:17 UTC,I haven't found reproducible steps for segfault.
1710674,2017-08-17 04:29:14 UTC,Thanks for the information!
1710674,2017-08-17 00:31:22 UTC,Any more information that I should provide ?
1710674,2017-08-29 02:50:04 UTC,Gentle ping.
1710674,2017-08-15 19:13:29 UTC,"# apt-cache policy openjdk-8-jre
openjdk-8-jre:
  Installed: 8u131-b11-2ubuntu1.16.04.3
  Candidate: 8u131-b11-2ubuntu1.16.04.3
  Version table:
 *** 8u131-b11-2ubuntu1.16.04.3 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
        100 /var/lib/dpkg/status
     8u77-b03-3ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages"
1710676,2017-08-17 14:33:59 UTC,"More information:
printing the webpage to PDF and then print the PDF works. But it takes a considerable time. The PDF is 3 pages long. The first page takes around 30 seconds until printing starts. After that, another 10 seconds pause and the remaining two pages are printed."
1710676,2017-08-17 13:56:43 UTC,I saved the webpage I used for testing and attached it here.
1710676,2017-08-17 13:55:26 UTC,"Affected HPLIP versions:
3.16.3 (available from package repositories)
3.17.7 (downloaded from hplipopensource.com)"
1710676,2017-08-17 13:58:28 UTC,"There seems to be a problem with the printer driver on the Linux side. Compared to the Windows driver, it appears it create way too large print data that fills up the printers internal memory."
1710682,2019-02-19 13:44:58 UTC,Is this still an issue?
1710687,2017-08-14 18:07:54 UTC,"An strace of GIMP, grepping the output for ""gvfs"" prints the following lines:"
1710687,2017-08-14 22:47:20 UTC,"All right. It actually works with gvfs-backends package installed, but it refuses to download images using HTTPS. I have to use plain HTTP to download the image."
1710693,2017-08-14 18:58:58 UTC,From the ADT history it looks to me like this failure is related to the switch of binuitls to 2.29.
1710698,2017-08-15 13:48:58 UTC,"This is not a bug, but wrong settings in your configuration."
1710698,2017-08-20 19:50:35 UTC,"yes, i have remove that non release PPA using"
1710704,2017-10-18 06:38:24 UTC,Looks like this has been fixed in 22d06152d0fabc7fe50bb6829f00b2bac4ed1796
1710705,2017-08-15 06:15:55 UTC,ok
1710705,2017-08-15 06:17:38 UTC,reinstal program or route\
1710705,2017-08-14 20:29:29 UTC,"You get many errors of type
Warning: Expected end of file in D:\Program Files (x86)\OR\MSTS\ROUTES\E30-Podkarpacie\WORLD\w-005296+014896.w:line 648
I suspect that your installation of the route E30-Podkarpacie is corrupt. I'd suggest to reinstall it and try again."
1710705,2017-08-15 08:12:15 UTC,Didn't help
1710709,2017-08-14 22:29:48 UTC,"Jason, just a quick question to be sure you're no longer using the snap package:
What does it say when you enter 'which inkscape' in the command line?"
1710709,2017-08-15 16:21:54 UTC,"Btw. I can install and use it with Inkscape.
I believe this is https://bugs.launchpad.net/inkscape/+bug/1655609"
1710713,2017-08-15 22:42:03 UTC,"I'm using version is 3.1.0 from Pike, I believe generic groups were introduced in Newton though.
To get the option you need to run ""export OS_VOLUME_API_VERSION=3.10"" or --os-volume-api-version=3.10."
1710713,2017-08-16 15:02:07 UTC,"Thanks Cripps. Didn't know the default devstack API version was so old, I assumed it would be a recent one. I will look into updating this."
1710713,2017-08-16 18:17:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/494286"
1710713,2018-05-11 16:11:24 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/494286
Reason: No update for some time. Feel free to restore and address comments if you wish to pursue this."
1710713,2018-07-24 10:45:38 UTC,"Is anyone working on this,
I would like to take this issue. Thanks"
1710713,2018-07-24 14:32:13 UTC,"Hey Rajat,"
1710713,2017-08-15 21:35:32 UTC,"Which version of Openstack was this seen in? I have just checked the latest Pike devstack, and at least with my configuration the group-id is not an argument for create or list. If it was pike, then I may need a different configuration."
1710722,2017-08-14 21:57:46 UTC,"Corrections: My apologies, I was too hasty with the KDE testing. The problem also occurs in Linux Mint 18.2 KDE, however the workaround fails and the following command is not helpful:"
1710728,2018-02-06 13:17:53 UTC,I agree that clarification here helps to get the package installed from its sources.
1710728,2018-04-07 17:14:58 UTC,"I just upgraded from 17.10 to bionic beta and had this problem. python3-gi was installed already for me, but installing the other package did fix it. But note it's gir... not girl...!"
1710728,2018-04-08 14:38:50 UTC,"... And just fixed in version 3.0.0-1, released in Bionic."
1710746,2017-08-15 01:06:37 UTC,"As long as you don't touch the settings in the ""Titlebar Buttons"" section, it shouldn't override your custom button-layout."
1710746,2017-08-15 01:44:43 UTC,"logically that's what I figured, but it seems even looking at the page that setting is located causes an overwrite. Occasionally just touching tweak causes it. I wouldn't complain, it's obviously a design choice. But using dconf is just horrible now, and its really hard to find all the settings that tweak does help with."
1710746,2017-08-15 02:27:14 UTC,"It is difficult to provide a nice easy UI but support lots of options for the window buttons. As an example, before GNOME 3.25/3.26, the GNOME Tweaks app did not support window buttons on the left at all!"
1710746,2017-08-15 22:16:16 UTC,"I understand I'm not programmer, but I seem to recall an earlier version on tweak showing just a blank box for that setting when I set a custom value. Now it still shows left or right. So it seems it used to have a way to handle custom keys."
1710746,2017-09-02 15:11:17 UTC,"I've had a thought on this. Budgie is now doing the same thing even more aggressively than tweak.
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1714692"
1710750,2018-06-27 16:09:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710750,2018-06-27 16:13:39 UTC,"With only one user, if I logout, X hangs -- can't even get a console with ctrl-alt-f3."
1710750,2018-06-27 16:15:51 UTC,"Forgot to mention that I am running Ubuntu 18.04 using the Gnome X session, but I also tested the Ubuntu X session and Ubuntu Wayland sessions."
1710752,2018-03-17 03:38:29 UTC,I just installed the 18.04 daily and formatted a fresh partition (no prior home directory or any existing data used) and this is still an issue in 4.15.0-12-generic.
1710754,2017-10-28 15:39:04 UTC,"This was fixed for a while by an update that came in, but now this problem has come back."
1710754,2018-03-17 20:49:19 UTC,Also note that this problem also affects Bionic 18.04 users with 4.15.0-12-generic
1710765,2017-08-16 14:18:24 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1710765,2017-08-16 18:19:35 UTC,Thanks for the response and sorry for the limited details.
1710765,2017-08-16 20:10:30 UTC,The builtin module in http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-vivid/linux-headers-3.19.8-031908-generic_3.19.8-031908.201505110938_amd64.deb is also broken.
1710765,2017-08-15 03:00:07 UTC,This change was made by a bot.
1710784,2017-11-26 09:59:38 UTC,"Reviewed:  https://review.openstack.org/477463
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=f567a5cb26d62f24f58fe9e125c3fceab09784d4
Submitter: Zuul
Branch:    master"
1710795,2017-08-15 19:37:08 UTC,"DuplicateSignature:
 Processing triggers for man-db (2.7.5-1) ...
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package python3-problem-report (--configure):
  package python3-problem-report is not ready for configuration"
1710808,2017-08-16 15:17:47 UTC,"Given zesty and newer has 2.2.27, marking invalid for development release, adding target for Xenial."
1710808,2017-08-16 15:28:45 UTC,Thanks for filing the bug and providing a link to a couple of patches.
1710808,2017-08-17 10:53:08 UTC,"I'm still weighing my options and may go with the PPA dovecot. I'm not able to evaluate the regression potential for the fix. For reference, here are my findings:"
1710808,2017-11-18 20:55:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710824,2017-08-28 08:50:06 UTC,Trunk should now display result count and occurence page number as a separate column in the extend search results view.
1710831,2017-11-16 12:51:30 UTC,I think that ceilometer's event_definitions.yaml could be extended to consume those events.
1710831,2017-10-05 15:45:12 UTC,I see the same:
1710831,2018-02-12 14:02:54 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: stable/17.11
Review: https://review.openstack.org/534506
Reason: Old code."
1710831,2018-02-12 14:02:30 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: stable/17.11
Review: https://review.openstack.org/534504"
1710831,2018-02-12 14:02:09 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: stable/17.11
Review: https://review.openstack.org/534505"
1710831,2018-02-09 11:51:39 UTC,"Reviewed:  https://review.openstack.org/540837
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=ff2547c6d552e85890c86d0677126ca1c09a9a04
Submitter: Zuul
Branch:    master"
1710831,2018-02-09 11:49:09 UTC,"Reviewed:  https://review.openstack.org/540834
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=6b9b02c11201d1afd960af0196eff56c6f81ffef
Submitter: Zuul
Branch:    master"
1710831,2018-02-09 11:47:54 UTC,"Reviewed:  https://review.openstack.org/540833
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=269ba2bb1d48ea515b315a9a7226dc010784ccaa
Submitter: Zuul
Branch:    master"
1710831,2018-02-05 12:01:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/540837"
1710831,2018-02-05 11:35:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/540833"
1710831,2018-01-17 00:29:06 UTC,"Fix proposed to branch: stable/17.11
Review: https://review.openstack.org/534506"
1710831,2018-01-17 00:24:51 UTC,"Fix proposed to branch: stable/17.11
Review: https://review.openstack.org/534505"
1710831,2018-01-17 00:23:23 UTC,"Fix proposed to branch: stable/17.11
Review: https://review.openstack.org/534504"
1710831,2018-02-05 11:40:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/540834"
1710831,2018-01-10 15:39:02 UTC,I think charm-based customization of event_definitions.yaml is needed after all although ceilometer needs to ship a more up-to-date list of events.
1710831,2017-11-16 18:45:47 UTC,"So, to break the comms down, designate components do both sending and receiving via AMQP."
1710831,2018-01-16 08:38:36 UTC,"Reviewed:  https://review.openstack.org/531334
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=4adfc46f842e1aec20e739a7b6d94ab14e7f4cfe
Submitter: Zuul
Branch:    stable/17.11"
1710831,2017-11-17 10:11:57 UTC,@dmitriis
1710831,2017-11-17 10:41:09 UTC,@james-page I do agree about upstream ceilometer defaults. I think the new object CRUD events were just not added there.
1710831,2017-11-17 12:36:30 UTC,the topic side of this:
1710831,2017-12-04 09:59:34 UTC,"Reviewed:  https://review.openstack.org/521073
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=45792d3c865149f2c94cef42b19c1385d7f7b0ee
Submitter: Zuul
Branch:    master"
1710831,2017-11-17 07:56:53 UTC,It's questionable which traits to add to event_definitions.yaml by default on the ceilometer side.
1710831,2017-12-15 15:09:26 UTC,"Fix proposed to branch: stable/17.11
Review: https://review.openstack.org/528304"
1710831,2018-01-05 08:32:47 UTC,"Fix proposed to branch: stable/17.11
Review: https://review.openstack.org/531334"
1710831,2018-01-05 08:32:55 UTC,"Change abandoned by James Page (<email address hidden>) on branch: stable/17.11
Review: https://review.openstack.org/528304"
1710831,2018-01-05 11:27:55 UTC,"Reviewed:  https://review.openstack.org/521075
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=1879b16ea543b076c9555fdc0258355d39af9ad0
Submitter: Zuul
Branch:    master"
1710831,2017-12-15 14:54:05 UTC,"Reviewed:  https://review.openstack.org/521072
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=b89de21d47dc9114d20456452cd867041bcd83c5
Submitter: Zuul
Branch:    master"
1710844,2017-08-15 09:42:51 UTC,"StacktraceTop:
 OpalPluginControl::Call(void*, unsigned int*, void*) const () from /tmp/apport_sandbox_9iWB7M/usr/lib/libopal.so.3.10.10
 OpalPluginVideoTranscoder::EncodeFrames(RTP_DataFrame const&, PList<RTP_DataFrame>&) () from /tmp/apport_sandbox_9iWB7M/usr/lib/libopal.so.3.10.10
 OpalPluginVideoTranscoder::ConvertFrames(RTP_DataFrame const&, PList<RTP_DataFrame>&) () from /tmp/apport_sandbox_9iWB7M/usr/lib/libopal.so.3.10.10
 OpalMediaPatch::Sink::WriteFrame(RTP_DataFrame&) () from /tmp/apport_sandbox_9iWB7M/usr/lib/libopal.so.3.10.10
 OpalMediaPatch::DispatchFrame(RTP_DataFrame&) () from /tmp/apport_sandbox_9iWB7M/usr/lib/libopal.so.3.10.10"
1710845,2017-08-18 07:51:48 UTC,"3 patches have been trying to solve the similar problem, maybe we need more discussion.
And would you please read the following patchhes to see if any other opinion
https://review.openstack.org/#/c/477445
https://review.openstack.org/#/c/383049
https://review.openstack.org/#/c/367113"
1710845,2018-06-14 10:32:02 UTC,Do You have link to logs of such failed test? I would like to take a look why port was DOWN all time.
1710845,2018-10-11 06:57:28 UTC,"I think, merging of https://review.openstack.org/#/c/383049 will solve the purpose of this issue."
1710845,2018-10-11 09:01:03 UTC,"The port implicitly created with the machine should not be down state after the machine become active, the interfaces added later may require time for being wired."
1710845,2018-11-29 06:43:19 UTC,@Sofiia Andriichenko: Are you still working on this issue or should we move it to un-assigned category so that someone can assign it and fix it?
1710845,2018-12-20 05:46:50 UTC,One more issue of similar type on which work is still in progress: https://bugs.launchpad.net/tempest/+bug/1728600
1710845,2020-02-18 09:22:58 UTC,Long inactivity.
1710850,2018-02-26 11:40:24 UTC,https://review.openstack.org/547999
1710850,2018-02-26 11:40:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547999"
1710850,2017-11-20 18:12:26 UTC,"This was discussed in the ironic meeting [1] and Dmitry, Julia are good with approving this without a spec, although the issues discussed in the meeting need to be mentioned here. I suggest updating the description to include the answers to the questions we asked, then ping us to approve this RFE. Thanks!"
1710850,2017-11-14 15:05:19 UTC,I'd be fine if we implement this feature without a dedicated spec.
1710850,2017-11-22 20:23:26 UTC,Approving this. Thanks!
1710850,2017-11-13 23:22:11 UTC,Do we need a spec for this? I'd be fine if the additional config parameters were described here and they aren't controversial :)
1710862,2018-01-09 08:32:46 UTC,Are you sure you have xserver-xorg-input-synaptics installed? Ubuntu 17.10 doesn't ship with it any more.
1710862,2018-01-09 08:33:41 UTC,"Ah, yes. Seems to be there:
[     6.062] (II) LoadModule: ""synaptics""
[     6.063] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so"
1710862,2018-04-07 18:20:44 UTC,Same issue on 18.04 (beta)
1710873,2017-08-18 10:04:58 UTC,"Hi Dove,"
1710873,2017-08-17 10:28:43 UTC,"Hello,"
1710873,2017-08-17 23:08:09 UTC,"Hi Yannick, let me first congratulate you on a fantastic piece of software.
Keep it up!
I am strongly urging my state fencing body to start utilising it."
1710874,2020-05-27 07:51:34 UTC,This bug is marked incomplete for tripleo. Please remove the milestone to stop the spam with each RC :)
1710874,2017-09-05 13:45:39 UTC,This issue was fixed in the openstack/kolla 5.0.0.0rc1 release candidate.
1710874,2017-08-22 07:57:01 UTC,"Reviewed:  https://review.openstack.org/477517
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ecc022177c7569b4c2066d64a93d47d72bfa7bdf
Submitter: Jenkins
Branch:    master"
1710874,2017-08-22 03:56:26 UTC,"Reviewed:  https://review.openstack.org/477494
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=7b2dea5506375cb868d6acb6a99b0aca916fad6c
Submitter: Jenkins
Branch:    master"
1710874,2017-09-05 13:10:37 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0rc1 release candidate.
1710884,2017-08-15 16:38:10 UTC,"Looking at the output of the command for that job, I think the culprit is the characters in this section of the output:"
1710884,2017-08-15 16:40:34 UTC,Summary changed I can reproduce this on amd64 as well:
1710889,2017-08-15 14:35:20 UTC,"Yes, I am not sure if it's worth doing this as the command needs to go fast."
1710897,2017-08-15 14:44:08 UTC,"StacktraceTop:
 raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=40) at ./debian/build-src/src/emacs.c:381
 emacs_abort () at ./debian/build-src/src/sysdep.c:2255
 x_connection_closed (dpy=dpy@entry=0xcf3000, error_message=<optimized out>, error_message@entry=0x7fff041466b0 ""Connection lost to X server ':0'"", ioerror=ioerror@entry=true) at ./debian/build-src/src/xterm.c:9468
 x_io_error_quitter (display=0xcf3000) at ./debian/build-src/src/xterm.c:9574"
1710897,2017-08-27 17:23:46 UTC,"""Connection lost to X server"", so this sounds like the following entry from Emacs's etc/PROBLEMS:"
1710897,2017-10-17 09:14:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710901,2017-08-15 14:50:37 UTC,"Thanks in advance for your help because I am a French beginner on Linux-Ubuntu.
Nevertheless, I want to increase my experience and agree to help you as much as possible.
Regards.
AL"
1710901,2018-05-11 15:34:34 UTC,This change was made by a bot.
1710910,2017-08-28 19:26:58 UTC,"(In reply to Caolán McNamara from comment #9)

> The ""original"" dialog wasn't resizeable, it was resizeable for a while after
> conversion to .ui and then back to resizeable again.
>
> Its trivial to make it nominally resizeable, just remove the resizeable
> property of False line in sc/uiconfig/scale/ui/standardfilterdialog.ui but
> the dialog doesn't play particularly well when resized, so I'm going to
> personally leave this alone as I don't see it as a regression from the
> original state and I've no enthusiasm to be on the hook to work through
> making it play perfectly when resized.
"
1710910,2017-08-28 19:32:34 UTC,"So developer said that it's intentional because ""dialog doesn't play particularly well when resized"".
For those who want to make it re-sizable again:
sudoedit /usr/lib/libreoffice/share/config/soffice.cfg/modules/scalc/ui/standardfilterdialog.ui
<property name=""resizable"">False</property>
<property name=""resizable"">True</property>"
1710910,2017-08-28 14:05:35 UTC,"The ""original"" dialog wasn't resizeable, it was resizeable for a while after conversion to .ui and then back to resizeable again."
1710910,2020-03-09 16:21:30 UTC,"still similar in Version: 7.0.0.0.alpha0+
Build ID: 4c009d523f1017def872f0c69caafd7d1826c263
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: gtk3;
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-03-06_13:17:52
Locale: nl-NL (en_US.UTF-8); UI-Language: en-US
Calc: threaded"
1710910,2018-08-29 02:41:51 UTC,** Please read this message in its entirety before responding **
1710910,2017-08-21 05:29:28 UTC,"author	Caolán McNamara <email address hidden>	2016-07-13 19:09:41 (GMT)
committer	Caolán McNamara <email address hidden>	2016-07-13 19:10:46 (GMT)
commit	595c049afe0aff08ec350100bda5a2528f660a8e (patch)
tree	f698068192502689920b29a0174f5aebeb845f6c
parent	87c7d2902f419041b76bb7b5af8e38d5acbac733 (diff)
Resolves: tdf#98240 limit width of widgets of standard filter
and make the dialog non-resizeable because the ancient
core impl can only have 4 rows visible at a time"
1710910,2017-08-20 18:06:33 UTC,"Created attachment 135673
Screenshot of a regression"
1710910,2017-08-20 18:07:44 UTC,"It's not a duplicate of bug 49813, it's a different bug. I reported about unrealizable narrow Dialog window of Standard filter, not Autofilter pop-up window.
Added screenshot"
1710910,2017-08-13 22:25:01 UTC,"Description:
Some dialog windows (like Standard filter) have fixed size so searched results won't fit. Prior to version 5.3 standard filter results were long enough to read them without horizontal scrolling because dialog window size adapted to the longest cell content. Now I have to either use older version or use special rules of window manager (KWin) to enlarge those dialogs.
Similar thing with search results, initially that dialog window is too small to see fully long line but at least it's re-sizable."
1710910,2017-08-14 08:37:27 UTC,Moving it back to UNCONFIRMED until someone else confirms it.
1710910,2017-08-21 05:02:35 UTC,Confirm the regression.
1710910,2017-08-15 06:40:36 UTC,"Yes, I tried 'fresh' / 5.4.0.3 version from Ubuntu's ppa. This issue is easily reproducible under most Desktop envirornments (I tried XFCE, MATE, KDE) with gtk2, gtk3 and kde VCL UI."
1710910,2017-08-20 06:43:24 UTC,"Hello,"
1710910,2017-08-15 00:13:04 UTC,"Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version."
1710911,2017-08-15 16:48:40 UTC,"juliank: From what I can see, cache files generated by apt-ftparchive do not contain versioned entries.  They can also be located anywhere on a machine's filesystem, depending on how the sysadmin chose to apply the utility; there isn't one canonical file that can be automatically refreshed on package upgrade."
1710911,2017-08-16 12:49:33 UTC,"I believe this issue also affects apt-ftparchive in Debian, so have raised a bug there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872334"
1710911,2017-08-17 14:13:10 UTC,"Removed the patch tag here and there, as the patch is incomplete."
1710911,2017-08-15 16:10:24 UTC,"Just increment the cache version, thus forcing a regeneration. It's needed anyway so you don't destroy stuff on downgrades."
1710911,2017-08-15 16:19:34 UTC,"The attachment ""Fix truncation of 64-bit file-sizes caused by htonl()"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1710913,2017-08-28 07:54:13 UTC,"Hello Vicenç,"
1710913,2017-08-28 16:28:17 UTC,"Hello Adam,
just to be sure I have tested it in qpdfview 0.4.16 and 0.4.17beta1, together with poppler-qt5 0.57.0.
In all cases the issue is present.
In the attachments there is an screenshot without the trim option set (to show the full contents of page 3) and another one with (to show the contents of page 3 are cropped).
Also, I am building qpdfview from https://aur.archlinux.org/packages/qpdfview"
1710913,2017-08-28 18:36:42 UTC,"Hello again,"
1710913,2017-08-28 23:36:51 UTC,"Hi Adam,"
1710921,2021-01-30 10:10:33 UTC,"Casey, I've just tried this and was able to successfully destroy a project without having lxc-ls installed, so I'm not sure if something's changed since you experienced this issue. Could you check again and confirm the version of mojo you're using, the type of project you're destroying, and the output of `mojo project-list`?"
1710923,2017-08-20 15:11:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710929,2017-08-15 19:17:34 UTC,Please do separate bug reports for separate feature requests
1710929,2017-08-15 20:15:53 UTC,"1/ Flames are iterated function system class of fractals.
Apophysis is based on this algorithm http://flam3.com/flame.pdf (https://en.wikipedia.org/wiki/Fractal_flame) but Apophysis has more wider variety of classes.
It has graphical widget UI based on trangles whihc you can rotate and translate to control the variables and parameters. These has their own classes.
https://upload.wikimedia.org/wikipedia/commons/0/0a/Apophysis.png"
1710929,2017-08-15 21:43:01 UTC,"Also, I would like to draw attention of this procedural generation of 3D curl noise and if some framework could be done in Inkscape to make such 2D curl noise vectors. Not just the noise but also other classes of procedural 2D generation."
1710931,2019-10-22 20:21:36 UTC,"Status is ""expired"", but this is still here in late 2019 on Ubuntu 18.04.3 LTS. A behavioral work-around for me is to use Super+# to open the (pinned) Nautilus from the dock ... then use Ctrl+l to get to wherever I *really* want to go."
1710931,2020-05-11 10:51:17 UTC,"Nautilus stopped handling the Desktop in newer series, marking as wontfix. It doesn't seem important enough to get prioritized for a Bionic stable update either at this point"
1710931,2018-12-28 15:27:02 UTC,Invoking nautilus with ctrl-n from the desktop is not a synonym for having files on the desktop. What sense does it make to bring that up here?
1710931,2018-01-28 21:41:01 UTC,"NB: this will never be fixed, as gnome doesn't think users should have files on the desktop. Witness the sort desktop icons bugs filed in 2003 which sat unresolved for 15 years before being quietly expired upstream."
1710931,2018-12-29 23:03:04 UTC,"One correction from the previous posting: it is not gnome but ""nautilus-desktop"" which handles the keyboard shortcut for ctrl-n. If nautilus-desktop is not running, then the shortcut will not have any effect."
1710931,2017-11-09 14:49:20 UTC,"Affects me, thanks for upstreaming it."
1710931,2017-08-28 13:17:29 UTC,"Thank you for your bug rpeort, I reported the issue upstream on https://bugzilla.gnome.org/show_bug.cgi?id=786908"
1710941,2017-08-16 02:12:37 UTC,"You can try previous kernel versions your system had prior to the problem, using this technique:
  https://wiki.ubuntu.com/RecoveryMode"
1710941,2017-08-16 04:18:30 UTC,"Thanks Daniel.  Rolling back to kernel 4.4.0-87-generic #110-Ubuntu SMP seemed to fix the problem.  Upgrading to 4.4.0-91 also seemed to cause other problems: My system started overheating, eventually slowed to a crawl (i.e., over a matter of minutes after each reboot slowed to the point of being unresponsive), and I saw 4 instances (one for each core, I presume) of kidle_interrupt, which I had never seen before."
1710941,2017-08-16 05:00:06 UTC,This change was made by a bot.
1710941,2019-03-03 01:56:35 UTC,"I may be running into the same issue as reported here.  Has any progress been made, or any workaround been found?"
1710941,2017-08-16 02:04:19 UTC,If you're using 16.04 then there have been no high-level bluetooth-related updates at all recently:
1710943,2017-08-15 19:20:09 UTC,Agreed that it would be useful.
1710943,2017-08-16 15:18:39 UTC,"Just as a potential implementation note, it's possible to use a CTE for the main search and then select from the CTE twice, once to get the ""window"" of results based on limit/offset, and a second time to get the count.  I used this technique in the ""eliminate staged search"" branch, and it works well.  It's not free, but cost effective because non-recursive CTEs are only executed once in a query plan."
1710945,2017-08-16 10:38:39 UTC,Proposed spec: https://review.openstack.org/494157
1710945,2017-08-17 13:07:18 UTC,The spec has moved to https://review.openstack.org/494534
1710947,2017-08-15 19:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1710947,2017-08-15 19:23:11 UTC,"Logs not relevant, but I have confirmed that suspend works with a mainline kernel build that includes the new patch"
1710947,2017-08-16 14:47:24 UTC,I've dropped the patch in artful. Thanks!
1710965,2018-09-05 02:53:23 UTC,tracked on story board - https://storyboard.openstack.org/#!/story/2003660
1710965,2018-10-23 16:59:05 UTC,"It's fixed in the https://review.openstack.org/#/c/601680/ patch, can be closed"
1710971,2017-08-16 00:20:59 UTC,"The attachment ""Patch according to the recommendation within the bug report."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1710971,2017-08-18 07:52:36 UTC,"Hi Christian,
while I agree with the patterns and the counters this should be suggested upstream first.
Once integrated there the next merge will pick it up automatically.
And having it there ensures that SRU backports and what comes due to upgrades will not diverge."
1710971,2019-05-10 22:12:20 UTC,"Thanks for forwarding your change upstream, it looks like they've incorporated the systemd-logind log handling, via commits dcb79597 and 44d6719b (the latter including mention of your patch), which are now included in the 7.5.0 release.  So, I think we can close this bug as fixed in eoan.  14.04.6 support ended last month, so this isn't a candidate for backporting to that release, but if you need it in bionic or xenial, feel free to reopen."
1710973,2017-08-15 21:26:03 UTC,The runcon call in this script is done to ensure we can set the selinux context in the chroot regardless of the host policy. Can you provide more information about whether or not selinux was enabled on your build host and distro and version of distro you are using? Guessing that on certain platforms the required context to update selinux contexts has changed in policy somewhere.
1710973,2017-08-16 04:56:59 UTC,The build host is Centos7 and selinux is set to 'Enforcing' according to 'getenforce'.
1710973,2017-08-16 13:34:51 UTC,"I was able to make it work with enforcing, but adding this custom module:"
1710973,2017-08-18 06:18:18 UTC,"I experiemented with this today, and I could see this with selinux and enforcing, but only if I did *not* run the ""sudo semanage permissive -a setfiles_mac_t"" before it"
1710973,2017-08-18 06:45:37 UTC,"Hi Ian,"
1710973,2018-12-12 10:53:52 UTC,"Hi,"
1710979,2018-05-17 09:51:34 UTC,fix is still missing in bzr repo
1710979,2017-12-19 18:27:20 UTC,"Sure, I updated the tracker. Not sure why it listed 3.0.0."
1710979,2017-12-19 18:06:51 UTC,+ubuntu-security
1710979,2017-12-09 03:25:28 UTC,"https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-14176.html claims that ""release 3.0.0"" of bzr fixes this issue, but there is no such release."
1710979,2017-12-09 03:16:17 UTC,"This isn't actually fixed in bzr upstream, just in breezy and in the ubuntu package."
1710979,2017-09-07 17:15:36 UTC,CVE-2017-14176 has been assigned for this vulnerability.
1710979,2017-09-06 05:32:05 UTC,"Hi Marc, any news on the CVE?"
1710979,2017-09-05 23:57:43 UTC,This bug was fixed in the package bzr - 2.7.0-2ubuntu3.1
1710979,2017-09-05 23:57:42 UTC,This bug was fixed in the package bzr - 2.6.0+bzr6593-1ubuntu1.6
1710979,2017-09-05 23:57:41 UTC,This bug was fixed in the package bzr - 2.7.0+bzr6619-7ubuntu0.1
1710979,2017-08-26 22:45:34 UTC,I've just done so.
1710979,2017-08-20 17:40:08 UTC,Can I make this bug public?
1710979,2017-08-20 02:09:28 UTC,Thanks. We can cherry-pick the patch from Breezy for Bazaar.
1710979,2017-08-16 12:16:30 UTC,"Thanks, I've requested a CVE for Bazaar."
1710979,2017-08-16 12:16:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1710979,2017-08-15 21:49:14 UTC,"Bazaar distinguishes between the different implementations, so I've opted for adding -- for openssh and print an error for all the other ones (including plink - putty's implementation)."
1710979,2017-08-15 21:38:26 UTC,I've posted an initial fix for Breezy in https://code.launchpad.net/~jelmer/brz/fix-ssh-sec
1710979,2017-08-15 21:17:31 UTC,"Subversion explored poking a -- on the ssh command string to be safe, but discovered that putty's implementation doesn't understand -- so it would have broken Windows users."
1710981,2017-08-15 21:29:09 UTC,"The bug leads to ugly output on the console if the data contains such characters.
See the 3rd song in the following play queue listing:"
1710983,2017-08-15 21:41:48 UTC,"Edit:  That definition is in toolchain/c-toolchain.lisp, not in grovel.lisp."
1710995,2017-09-19 21:33:04 UTC,"I've reinstalled network-manager and commented out all lines associated to eth0 in /etc/network/interfaces. Now whoopsie is able to see if the system is connected to the inter net again. perhaps one ""quick"" solution could be making the package network-manager a hard dependency for whoopsie package."
1710995,2017-08-18 14:54:25 UTC,I've confirmed this with my mythbuntu 16.04 install with whoopsie 0.2.52.5 from xenial-updates.  It might be interesting to try and bring down the network interface and then bring it back on line and see if whoopsie then comes on-line.
1710995,2017-08-16 22:31:02 UTC,"Yes, mythbuntu."
1710995,2017-08-18 18:14:04 UTC,Restarting networking does not bring whoopsie online.
1710995,2017-08-16 18:52:15 UTC,"Sure, let me know if you need more information."
1710995,2017-08-16 21:55:44 UTC,"It looks like you are using XFCE and mythtv, is this a mythubuntu install of 16.04?"
1710995,2017-08-15 23:32:13 UTC,Can you connect to https://daisy.ubuntu.com?
1710995,2017-08-15 23:08:13 UTC,"sjuk@obelix:/var/crash$ sudo systemctl status whoopsie
● whoopsie.service - crash report submission daemon
   Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled)
   Active: active (running) since Di 2017-08-15 23:58:15 CEST; 1h 9min ago
 Main PID: 1327 (whoopsie)
   CGroup: /system.slice/whoopsie.service
           └─1327 /usr/bin/whoopsie -f"
1710995,2017-08-16 09:17:58 UTC,I think so. Curl gets the following answer.
1710995,2017-08-16 16:53:56 UTC,"Could you also add the output of ""journalctl -u whoopsie""? Thanks again!"
1710998,2017-09-01 22:02:28 UTC,This issue is reproducible by following the steps
1710998,2017-09-13 20:44:01 UTC,This can sometimes occur when previous ceph cluster data is left behind in /var/lib/openstack-helm from previous instantiations of ceph. The authentication details from the prior the ceph installs can hang around preventing the osd from registering with the monitors.
1710998,2017-10-16 16:07:13 UTC,"Looks like it works after deleting /var/lib/openstack-helm. But user will always face the problem  when the node goes up/down or when  the pod restarts. Every time we have to delete the folder and it's not a good idea. Is it possible to integrate the solution before starting the container (i.e., in scripts)?"
1710998,2018-10-04 13:37:10 UTC,I do see the same issue
1711004,2020-03-03 10:55:51 UTC,"Marking invalid, this was resolved by a MAAS update at some point."
1711009,2018-07-24 09:31:19 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1711009,2017-08-17 13:21:08 UTC,"I can't run apport-collect in that environment, but this is trivial to reproduce in any ppc64el qemu VM. Just use JFS as the filesystem for the root partition."
1711009,2017-08-16 13:08:41 UTC,"Can't run apport-collect; looks like there's nothing to save the apport data in this kind of case, so I can't transmit it anywhere. I'll see if I can reproduce this on amd64, should make it easier."
1711009,2017-08-16 02:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1711009,2017-08-17 13:13:48 UTC,"Note too that we now have a 4.12 kernel in artful-release, so you might give that a spin."
1711009,2017-08-16 14:10:07 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1711011,2017-08-16 02:00:37 UTC,"I'm unsure if this is a bug in jfsutils (which maybe should ship its own logic like btrfs does), or in initramfs-tools where its testing fails for jfs, hence the multiple tasks."
1711011,2017-08-16 13:01:03 UTC,"Nope, this is in fact /dev/mapper/mpatha-part2 that is missing when fsck runs. fsck.jfs is present on at least some initrd after installing."
1711011,2017-08-16 13:04:38 UTC,"Nope, that's wrong. fsck.jfs is there in xenial, but apparently not there in artful. This needs further investigation."
1711012,2019-10-21 17:42:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711020,2017-08-18 11:19:35 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1711020,2017-08-29 18:32:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711024,2020-09-19 08:59:47 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1711024,2017-08-16 21:52:52 UTC,"running Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06) (32 bit .exe)"
1711024,2017-08-16 21:36:09 UTC,Where did you get that file from?
1711024,2017-08-16 21:57:45 UTC,The file was from Wikimedia Commons: https://commons.wikimedia.org/wiki/File:Simple_Globe.svg
1711027,2017-09-07 04:23:10 UTC,"Fix committed via
https://github.com/Juniper/contrail-ansible-internal/commit/76ef9dc8a77f3c2e7a6824175e6cd88cee73b775
as part of fix for bug 1712231."
1711033,2017-08-18 11:19:27 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1711052,2018-03-08 20:50:48 UTC,Have you tested this with go 1.10 out of curiosity? I doubt it's been fixed but who knows... In any case I'm about to request the removal of 1.8 from the archive.
1711056,2017-09-18 10:11:08 UTC,This bug was fixed in the package linux - 4.4.0-96.119
1711056,2017-08-16 07:30:14 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1711056,2017-09-01 08:27:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1711056,2017-08-17 13:43:28 UTC,Test packages: http://people.canonical.com/~juergh/review/lp1711056/
1711056,2017-09-06 13:47:28 UTC,"This is looking great so far.  Instance booted nicely, no signs of a
kernel panic.  The driver was happily picked up in the initramfs.  I'm
going to run it through some stress-ng tests to make sure everything is
fine but we're off to a good start."
1711057,2017-08-16 13:10:34 UTC,"State of the new attach interface is LINK_DOWN. And can not tcpdump any packets from the new attach interface.
compute-h06-1:~# ovs-ofctl show br-int
 21(vhu4e163396-06): addr:00:00:00:00:00:00
     config:     0
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max"
1711057,2018-01-09 09:14:52 UTC,"Unfortunatelly, I was not able to reproduce behavior described in your bug-description.
Can you please provide step-by-step installation instructions to get
identical environment you have.
Also please provide any custom settings you have.
I set status of this bug to 'Incomplete', but please be free to reopen this bug after providing all
necessary information."
1711068,2017-09-12 15:59:36 UTC,LBaaS is no longer part of neutron.  LBaaS bugs should be submitted to the Octavia project on Storyboard.
1711070,2017-08-16 10:00:48 UTC,"You need this patch:
https://github.com/evgeni/bley/commit/fe64c8890d09ccee126680cda7f1b8d1d2369764"
1711070,2017-08-16 13:54:06 UTC,Could anyone add this patch to the package to have something that works?
1711078,2017-10-20 14:27:35 UTC,"I'm not sure I understand the bug report.  Assuming that the last 'stable/newton' in the description above was on the same line as the 'enable_plugin' (i.e. it's a formatting error in launchpad description), then this will pull the the 'stable/newton' branch from the git repo for nova-lxd, which is what you want."
1711079,2017-08-16 12:25:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1711079,2017-08-18 07:55:01 UTC,mobile-broadband-provider-info 20140317-1
1711079,2019-10-09 08:07:23 UTC,"This is unlikely to be a bug in mobile-broadband-provider-info.
Similar to LP: #1826461 , it is probably a bug in the kernel."
1711079,2019-12-09 04:17:16 UTC,[Expired for mobile-broadband-provider-info (Ubuntu) because there has been no activity for 60 days.]
1711095,2018-09-28 11:02:48 UTC,Any update on this bug?
1711100,2017-08-16 21:33:24 UTC,"I'm sure there exists functionality like the one you're looking for in Inkscape (it may be convoluted to get there, but it will be possible), but I'm not sure what exactly this is about.
Can you make a video or screenshot that explains it a bit better than just words?"
1711101,2016-05-25 12:56:26 UTC,What's the PulseAudio version?
1711101,2016-05-25 13:23:03 UTC,"(In reply to Tanu Kaskinen from comment #1)

> What's the PulseAudio version?
"
1711101,2016-05-25 13:24:12 UTC,"Created attachment 124084
with tv/hdmi disconnected but sound has not been redirected to local speakers"
1711101,2016-05-25 14:00:52 UTC,"(In reply to Tanu Kaskinen from comment #5)

> You also had some issue with remembering routing choices. Is it so that if
> you route to HDMI and reboot, audio isn't routed to HDMI any more, even if
> the HDMI cable stays plugged in all the time?
"
1711101,2016-05-28 01:22:02 UTC,"(In reply to Tanu Kaskinen from comment #5)

> Ok, so HDMI is on a different alsa card than analog output. That explains
> why unplugging HDMI doesn't result in moving audio to the analog output. We
> don't currently automatically reroute from one card to another on an unplug
> event. This should be fixed, but I can't give any timeline.
"
1711101,2016-05-28 11:07:05 UTC,"(In reply to Raymond from comment #7)

> but there is no available HDMI ports available anymore , this mean that the
> only available port is the internal speaker as headphone is not plugged
"
1711101,2017-08-17 02:18:25 UTC,"We now have autoswitching on connect in 17.10, but not on disconnect :)"
1711101,2018-07-06 02:04:58 UTC,See also bug 1777367
1711101,2018-07-30 10:03:13 UTC,-- GitLab Migration Automatic Message --
1711101,2018-10-16 08:55:18 UTC,"Upstream bug links:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/185
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/259"
1711101,2019-04-11 10:31:18 UTC,"Facing the same issue with 18.04.2 LTS
Had the same issue with previous versions as well
Will there be a fix anytime soon?
Thank you."
1711101,2019-10-09 17:32:58 UTC,"In my case with Ubuntu 18.04.2, In order to reestablish the sound after have removed the HDMI cable I need: to reattach the HDMI cable and turn the TV on. Only then I can change the selected sound board to Built-in Audio again and only after that I can detach the HDMI cable."
1711101,2019-10-10 01:48:42 UTC,"The upstream bug suggests this was fixed in PulseAudio 12.99.1, so should be fixed in Ubuntu 19.10 now. Can anyone test that?"
1711101,2016-05-25 12:47:51 UTC,Setup:
1711101,2016-05-25 13:23:35 UTC,"Created attachment 124083
with audio directed to TV via HDMI"
1711101,2016-05-25 13:42:08 UTC,"Ok, so HDMI is on a different alsa card than analog output. That explains why unplugging HDMI doesn't result in moving audio to the analog output. We don't currently automatically reroute from one card to another on an unplug event. This should be fixed, but I can't give any timeline."
1711112,2017-08-18 11:03:46 UTC,A video that I sent to Roland tech support to show that there may be a bug in their drivers
1711112,2017-08-18 12:41:38 UTC,Tested with my other printer on Windows 10 x64 version 1703 (Build 15063.540). Same problem.
1711112,2017-12-31 11:28:17 UTC,"Using other laptop, still settings do not save, I use Roland Stika SV-15."
1711112,2017-12-31 11:31:09 UTC,"This is a really important bug for me, I cannot print some stuff without changing preferences."
1711112,2018-10-25 19:44:51 UTC,Related MR: https://gitlab.com/inkscape/inkscape/merge_requests/386
1711112,2018-10-27 05:18:53 UTC,Fixed here: https://gitlab.com/inkscape/inkscape/merge_requests/391 (note the fine print: there's also a GTK bug involved)
1711114,2017-08-16 11:30:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/494174"
1711114,2017-08-16 18:10:03 UTC,"The bug fix would be a backport candidate for Pike.
So this is marked as critical."
1711114,2017-08-17 18:12:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/494663"
1711114,2017-08-22 08:39:26 UTC,"Change abandoned by rajiv (<email address hidden>) on branch: master
Review: https://review.openstack.org/494174"
1711118,2017-08-16 15:32:03 UTC,Thanks for the report.  This fix is already committed and will be in the next release.
1711119,2017-08-19 11:26:18 UTC,"Thank you for nice idea, Martin!
I reported bug to the upstream - https://github.com/mate-desktop/mate-system-monitor/issues/97 ."
1711119,2017-08-16 13:05:05 UTC,Can you raise this upstream as well please: https://github.com/mate-desktop/mate-system-monitor
1711124,2017-08-16 13:00:06 UTC,This change was made by a bot.
1711124,2017-08-16 14:25:26 UTC,I have reproduced the scenario also with bridges and vlan veths.
1711126,2020-07-15 14:03:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711128,2017-08-16 13:38:15 UTC,"Checked number of available_copies. If greater than 9000 display ""Always available""
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/spaterno/LP1711128_overdrive_always_available"
1711128,2017-08-16 17:09:40 UTC,"Thanks, Suzanne!"
1711128,2017-08-17 00:01:52 UTC,"If it's too much of a momentum killer, we can open a separate bug for this, but we'll want to I18N'ize those strings sooner or later."
1711128,2017-08-17 13:48:28 UTC,"NOBLE doesn't have any Cost Per Circ items yet, so we don't have the details on exactly how they work. But I would think from the patron's perspective they would also be always available, unless there's a configuration that restricts the number of times they can be checked out that way."
1711128,2017-08-29 22:14:24 UTC,The patch just committed for bug 1710512 has a model for how the I18N can be handled.
1711128,2020-02-21 21:50:33 UTC,"This branch adds internationalization to the ""Always available"" label"
1711129,2017-09-06 13:31:42 UTC,"Change abandoned by Fellype Cavalcante (<email address hidden>) on branch: master
Review: https://review.openstack.org/493983"
1711129,2017-10-18 18:22:21 UTC,I changed the status to 'Triaged' since there doesn't seem to be any patch to address it. Although is this still an issue?
1711129,2018-02-19 13:07:16 UTC,Is it still needed now that we moved away from oneviewclient?
1711132,2017-08-16 13:54:49 UTC,"StacktraceTop:
 variable_hash_1 (keyv=0x6989d943f0) at ../../variable.c:140
 hash_find_slot (ht=ht@entry=0x7ffe467c60d0, key=key@entry=0x6989d943f0) at ../../hash.c:89
 target_environment (file=<optimized out>) at ../../variable.c:1037
 start_job_command (child=child@entry=0x6989fccaa0) at ../../job.c:1443
 start_job_command (child=child@entry=0x6989fccaa0) at ../../job.c:1313"
1711132,2017-08-18 11:18:37 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1711136,2017-08-17 13:28:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711145,2018-11-05 16:15:25 UTC,"Tested pushed to master and (sans websocketd patch) rel_3_0 and rel_2_5. Thanks, Bill!"
1711145,2018-11-05 15:51:43 UTC,Changing to a public security bug after discussion with Bill.
1711145,2018-09-13 17:09:54 UTC,Rebased working branch to master and pushed another commit with commented-out websocketd configs.
1711145,2017-08-16 14:56:23 UTC,"Right, here's what we're currently using on Ubuntu 16.04 - a combination of what SSLabs suggested and Mozilla's config generator suggested. The comments might be useful for, for example, generating the dhparams (useful for external docs as well as inside our example config file):"
1711145,2018-07-11 16:40:51 UTC,Branch pushed to user/berick/lp1711145-nginx-config-updates @ security.
1711148,2017-08-16 15:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1711148,2017-08-16 15:14:59 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1711148,2017-08-31 10:41:43 UTC,Why should this have changed. This anoying bug is existing since 15.10 and even if there are several tickets nobody funkin cares!
1711148,2019-06-25 16:11:58 UTC,Nothing you say in your rant rules out an upstream bug.  But maybe you are not so interested in getting this analysed and fixed?
1711165,2017-08-16 18:19:12 UTC,"can you add more details when do you exactly see the error ? is it when you enable qos with networking-odl,"
1711165,2017-08-16 18:08:20 UTC,This is a candidate for backport to Pike. So this is marked as critical.
1711165,2017-08-16 18:30:18 UTC,"Please also add details, which mechanism_driver are you using opendaylight_v2 or v1 ?"
1711165,2017-08-16 21:58:27 UTC,This is with V2 driver. Attached neutron server log with error.
1711165,2017-08-17 19:40:17 UTC,Tim can you try https://review.openstack.org/#/c/494663/ and confirm if it is still an issue ?
1711165,2017-08-22 22:01:41 UTC,"Change abandoned by Isaku Yamahata (<email address hidden>) on branch: master
Review: https://review.openstack.org/494663
Reason: Now neutron patches were merged to master and stable/pike."
1711165,2017-08-23 00:03:23 UTC,"Reviewed:  https://review.openstack.org/495904
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=13ab6e350cc011e40b79b1e0f680bbabc4af3fe1
Submitter: Jenkins
Branch:    stable/pike"
1711171,2017-08-16 16:31:54 UTC,I noticed neutron-vpnaas does not provide the policy.json.... so the priority might be lower.
1711178,2017-09-08 13:22:14 UTC,"I've hit this a few times and was never ever to find anything useful.  However, this time I think I know what triggered the load.  I manually installed d-feet with apt, and within a couple minutes removed it with apt.  My laptop load spiked and stayed that way until I killed the process over 2 hours later.  While debugging it, the only thing that stood out was this log message:"
1711178,2017-08-18 12:22:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711178,2017-10-19 21:19:23 UTC,Could be the same as bug #1716579 which has details/backtraces of snapd-glib code
1711178,2017-09-06 07:09:55 UTC,Same experience than Olivier on resume from suspend. gnome-software was using 200% CPU.
1711178,2017-08-18 12:22:04 UTC,"Seen that this morning on a fully updated artful. Shortly after boot, a gnome-software process started consuming 100% CPU and continued doing so for a few hours, after which I killed it.
I had not opened the gnome-software GUI, only applied a few updates manually with apt:"
1711178,2017-08-19 08:45:59 UTC,It's done it again this morning. See attached screenshot.
1711181,2017-08-16 20:56:40 UTC,"I'm not too familiar with the OPAC or its modperl back-end to much, but should there be some server-side code that also checks for the proper inputs, once posted to the server?"
1711181,2017-09-13 15:58:25 UTC,3.0 beta OPAC
1711188,2017-08-17 09:15:01 UTC,After disabling '[] Use LibreOffice dialogs' I can reproduce this as well.
1711188,2017-08-17 09:15:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711188,2017-08-17 13:06:55 UTC,"I have icons now that I installed `sudo apt install ubuntu-dekstop*` (I was on ubuntu-gnome-desktop), that brought in a bunch of icons not on ubuntu-gnome."
1711195,2017-10-13 16:08:19 UTC,"Dmitrii,"
1711195,2019-11-29 15:04:17 UTC,"It's down to undecided, and likely will be made invalid as there's been no activity for 2 years."
1711197,2017-08-16 22:13:55 UTC,"FWIW, while this change may things nicer moving forward, this makes it very difficult to maintain code that needs to work on both, Xenial and Artful+. Having the old API still available would allow applications to continue to rely on the module without having to do any hackery, specially, since the module doesn't seem to expose any versioning information."
1711197,2021-01-31 00:24:54 UTC,Closing as those _ attributes were private APIs.
1711197,2017-08-16 18:40:56 UTC,"Benjamin, we see that you made this API change as part of addressing bug #1253208.  Do you see a fundamental reason not to continue supporting the old API?"
1711197,2017-08-16 18:44:02 UTC,Other areas this doesn't work anymore:
1711197,2018-02-04 19:47:04 UTC,_date and _rows were never part of the API since these properties are private.
1711202,2017-08-18 11:17:52 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1711203,2017-08-16 20:49:23 UTC,Can we please get some clarity on what curtin needs to do?  We've had two bugs in this area:
1711203,2017-08-16 20:43:38 UTC,"Note that these logs reflect installation with Secure Boot OFF, at least part of the time. If you need a log of a FAILED deployment with Secure Boot on, please tell me."
1711203,2017-08-17 21:06:39 UTC,"I don't think this requires gsbx64.efi at all, it looks to me like a different issue; but one that we'd likely hit in the future anyway when enforcing signatures on kernels."
1711203,2017-08-16 19:50:13 UTC,"Setting to confirmed... this has also been reported by a customer in the field (OEM Partner) and I was investigating it for them, Rod now has also experienced this."
1711203,2017-08-17 14:47:29 UTC,"Rod,"
1711203,2017-08-16 20:25:10 UTC,Please attach the curtin configuration and the installation log.:
1711203,2017-08-17 19:22:15 UTC,"> Curtin/MAAS will install the linux-image-generic kernel for the specific
> release unless otherwise specified by MAAS in their kernel config mapping.
"
1711203,2017-08-17 14:19:13 UTC,"Ryan, neither of the bugs you reference is a duplicate of this one. This bug is new. Both the nodes I've tested have been successfully deployed with Secure Boot active in the past. In fact, brennan had been successfully deployed with Secure Boot but then failed to boot from that very deployment some days or weeks later (I'm not sure how long it had been since I last booted it), which suggests to me that the Shim/GRUB provided by the MAAS server when PXE-booting had changed in that period."
1711203,2018-02-22 20:45:17 UTC,Can we please verify that with one of the original failing systems (Cisco UCS C-240 M4) as well?
1711203,2018-02-15 15:25:17 UTC,"Hi Matthieu,"
1711203,2018-02-15 20:40:04 UTC,"Just as an update, this is still an issue with Grub in Bionic..."
1711203,2018-02-15 20:52:53 UTC,and Xenial
1711203,2018-02-21 14:31:55 UTC,"I have provided a workaround in comment #36, has this not been applied? Landing a fix for this is going to take time, as it depends on a full roundtrip of getting shim prepared, tested, and signed by Microsoft."
1711203,2018-02-21 15:09:46 UTC,"Mathieu, the workaround of chainloading GRUB rather than shim that you suggested in comment #36 does not work; see my comment #39."
1711203,2018-02-21 18:08:36 UTC,I'm at a loss to explain that. This works quite well in my netboot testing when I remove MAAS from the equation. You *are* meant to be able to chainload grub from another grub; and the reason why grub can't chainload shim is that you then get the wrong set of shim protocols to properly validate the next binary. This will need more testing; I will need to know what hardware this is and what exactly is the content of the grub configs.
1711203,2018-02-22 17:11:53 UTC,"So I've enabled secure boot on my Intel NUC's and have *not* used to workaround in #36, and the machines deployed just fine (that is, they pxe boot off MAAS and they are told to load the shim). The same scenario is when using workaround in #36."
1711203,2018-02-22 18:54:47 UTC,"Now, at this point, I'm stuck unbooted on the initial post-deployment reboot.  So I reset the node by hand (poked the reset button) and disabled SecureBoot in the config and rebooted it again."
1711203,2018-02-22 20:32:05 UTC,"Ok, so I've tested the workaround in a supermicro system provided by the cert team, and this is my evaluation:"
1711203,2017-08-17 20:11:27 UTC,"I agree with Steve that installing linux-signed-image-generic as a default is best at the moment. Such kernels should boot whether or not Secure Boot is enabled, and AFAIK they'll even boot on BIOS-based computers (but I've not checked that, and there may be dependency issues on such systems). There is the caveat that this will increase the space used in /boot, which could cause out-of-space errors if /boot is a separate partition that's too small (see bug #1465050). I recommend 500 MB as a MINIMUM size for /boot these days."
1711203,2018-02-22 21:04:47 UTC,"The workaround in #36 is now working for me on my home network, too. Perhaps when I tested it in December (comment #39) I had different software versions; or maybe I didn't correctly reproduce the changes in comment #36."
1711203,2018-01-25 18:35:34 UTC,I also face this issue with nodes running on Hyper-V 2016 and enabled Secure Boot (Microsoft UEFI cert.).
1711203,2018-02-22 21:22:44 UTC,"On Thu, Feb 22, 2018 at 08:45:17PM -0000, Jeff Lane wrote:

> Can we please verify that with one of the original failing systems
> (Cisco UCS C-240 M4) as well?
"
1711203,2018-02-22 23:28:26 UTC,"On Thu, Feb 22, 2018 at 11:06:51PM -0000, Jeff Lane wrote:

> > Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the
> > Canonical-signed image from grub-efi-amd64-signed?
"
1711203,2018-02-23 00:50:47 UTC,"This brings a good point. What I didn’t test, which will do tomorrow, is
what happens if I kill Maas and let the same system boot from disk. I
wonder if it will boot."
1711203,2018-02-23 00:55:47 UTC,"On Thu, Feb 22, 2018 at 6:28 PM, Steve Langasek
<email address hidden> wrote:

> On Thu, Feb 22, 2018 at 11:06:51PM -0000, Jeff Lane wrote:
>> > Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the
>> > Canonical-signed image from grub-efi-amd64-signed?
>
>> I presume so? dpkg says it is:They look the same to me:
>
>> ubuntu@xwing:/boot/efi/EFI/ubuntu$ dpkg -S grubx64.efi
>> grub-efi-amd64-signed: /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed
>
> That doesn't establish that /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed
> and /boot/efi/EFI/ubuntu/grubx64.efi match.  Can you please verify that they
> do?
"
1711203,2018-02-23 01:13:42 UTC,"On Thu, Feb 22, 2018 at 7:55 PM, Jeff Lane <email address hidden>
wrote:"
1711203,2018-02-23 01:18:00 UTC,"FWIW, I did a bit of extra testing. I killed maas' rackd (which provides PXE). Rebooted the machine and I saw:"
1711203,2018-02-23 01:41:43 UTC,"On Fri, Feb 23, 2018 at 01:13:42AM -0000, Andres Rodriguez wrote:

> > bladernr@critical-maas:/var/lib/maas/boot-resources/
> > current/bootloader/uefi/amd64$
> > ll
> > total 2328
> > drwxr-xr-x 2 maas maas    4096 Feb 22 17:34 ./
> > drwxr-xr-x 4 maas maas    4096 Feb 22 17:34 ../
> > -rw-r--r-- 2 maas maas 1196736 Feb  5 07:29 bootx64.efi
> > -rw-r--r-- 2 maas maas 1173368 Feb  5 07:29 grubx64.efi
"
1711203,2018-02-23 15:40:44 UTC,"Jeff,"
1711203,2018-09-14 19:45:38 UTC,The SRU of shim 15+ has been rolled back from bionic-updates while we investigate this issue.
1711203,2018-09-14 19:46:08 UTC,"Sorry, commenting on the wrong bug - this bug is obviously older than the most recent SRU-induced problem."
1711203,2018-09-14 21:12:23 UTC,Shim 15+ includes the fix for this chainloading trick; you should now be able to chainload from:
1711203,2019-12-04 09:02:03 UTC,"Hi,"
1711203,2018-02-22 23:06:51 UTC,"> Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the
> Canonical-signed image from grub-efi-amd64-signed?
"
1711203,2017-12-14 13:40:52 UTC,"Andres,"
1711203,2018-02-22 18:51:16 UTC,"MAAS version: 2.3.0 (6434-gd354690-0ubuntu1~16.04.1)
This is my observation on a Lenovo RS140 with workaround enabled from comment #36:
Also, to be sure it's not something we've injected, I am using the default curtin_userdata, NOT our customized cert one."
1711203,2017-12-08 13:36:24 UTC,"Lee, I tried http://162.213.35.187/proposed/streams/v1/index.json earlier, in response to Andres' suggestion, and that stream did not help. (See comments #24 and #25.) If you think that stream has changed since I did my testing on November 27, I'm happy to try again; but if not, it doesn't help."
1711203,2017-08-17 21:29:06 UTC,To get this in the bug report: Replacing /var/lib/maas/boot-resources/current/bootloader/uefi/amd64/grubx64.efi with the grubnetx64.efi.signed file specified by Mathieu results in a successful boot. My understanding is that this is NOT good news. :(
1711203,2017-08-18 02:04:38 UTC,Since 2.02-beta2-36ubuntu3.11 works but .12 (which is the latest in Xenial updates doesn't) this seems to confirm the regression in grub. marking invalid for NAAS and curtin!
1711203,2017-12-13 17:47:34 UTC,"@Rod,"
1711203,2017-09-11 16:22:26 UTC,"Set the Grub2 task to High to grab attention (and because it's at least a High, if not Critical, bug).  My gut says this should be critical as it's blocking the deployment of systems from multiple vendors in multiple datacenter and lab environments anytime SecureBoot is enabled."
1711203,2017-11-16 20:23:24 UTC,any updates on this issue?
1711203,2017-11-16 21:25:36 UTC,"If maas+curtin are not installing the signed variant of the linux-image package on UEFI systems, this is not invalid for maas+curtin - when we rev the grub secureboot policy (ETA January), these systems will be unbootable BY DESIGN.  Regardless of whether this configuration has tickled a regression in grub, this MUST be fixed."
1711203,2017-11-16 21:53:18 UTC,"No one in this thread has answered how MAAS or curtin
knows that it should install the -signed version of linux-image."
1711203,2017-11-16 22:02:43 UTC,"On Thu, Nov 16, 2017 at 09:53:18PM -0000, Ryan Harper wrote:

> No one in this thread has answered how MAAS or curtin
> knows that it should install the -signed version of linux-image.
"
1711203,2017-11-16 23:03:45 UTC,"To be clear, although installing the signed kernel package is necessary, a failure to do this is NOT the source of this bug, which seems to relate to how Shim and/or GRUB handle the MAAS boot path, which involves Shim and GRUB being PXE-booted and then chainloaded to (Shim and?) GRUB on the hard disk. I am available for testing of proposed fixes; I have one system with Secure Boot available on my home network and sporadic access to others in 1SS (from OIL; we can transfer them over to the certification network from time to time)."
1711203,2017-11-22 17:50:31 UTC,We have a test streams that uses the signed linux kernel instead of the non-signed for x86. Can you please test it from this stream:
1711203,2017-11-22 18:48:11 UTC,"Andres, I've downloaded that file, but I have no idea where to put it. I can't find a file called index.json on my MAAS server."
1711203,2017-11-27 17:27:20 UTC,"@Rod,"
1711203,2017-09-11 16:10:05 UTC,I am facing similar issue at Dell site and all Dell servers are exhibiting this behavior when secure boot is enabled.
1711203,2017-11-27 19:09:08 UTC,"Here's the install log, cut-and-pasted from the MAAS web UI, for the latest installation. Note that after the node shut down, I restarted it and disabled Secure Boot to get it to complete."
1711203,2017-11-27 19:12:26 UTC,"So to clarify, MAAS pxe config searches & chainloads /efi/ubuntu/shimx64.efi. It seems here the issue is with the shim. As per Rod's comments:"
1711203,2017-11-27 19:27:47 UTC,Should we re-open the grub2 task then? or add a shim task?
1711203,2017-11-27 18:32:24 UTC,"I've tried this and the problem persists. Note that MAAS *IS* installing the signed kernel, which is necessary but insufficient for a fix; the problem seems to be that Shim/GRUB is becoming confused by the handoff from the PXE-boot version of GRUB to the GRUB stored on the hard disk. If my analysis is correct, this will require either:"
1711203,2017-12-01 21:57:25 UTC,I've updated lp:maas-images to produce new images using the linux-signed kernel on AMD64. New images are produced when http://cloud-images.ubuntu.com/daily/ adds new images so it may take a few days for signed kernels to appear in the stream. Unsupported releases are no longer updated so we'll have to manually regenerate them if we want signed kernels.
1711203,2017-12-05 13:58:05 UTC,"I'd just like to emphasize that, although a change to always install the linux-signed kernel on AMD64 systems is necessary to fix this bug, it's not sufficient to fix the bug. As noted in my comment #25 (and elsewhere), another change is also required -- either a change to Shim or GRUB (I don't know which) or a change to how MAAS handles the boot process (to have the PXE-booted GRUB read the configuration file from the hard disk rather than chainload to GRUB on the hard disk; or perhaps a change to the way the handoff is done, if some tweak could bypass the bug)."
1711203,2017-12-05 15:15:57 UTC,Reviewing @slangasek's notes
1711203,2017-12-05 15:45:47 UTC,"As per Rod's comments, I'm re-opening the grub task."
1711203,2017-12-06 23:41:43 UTC,"From Andres, the grub.cfg used for chainloading to local disk is:"
1711203,2017-12-07 01:52:35 UTC,"Yes, it's absolutely possible to recreate the environment for testing this without MAAS -- there's nothing all that special to it, chainloading *any* image should work and maintain a Secure Boot-verified chain provided all the links in the chain validate images."
1711203,2017-12-07 09:32:03 UTC,While reading through #1730493 and #1437024 I noticed both had various UEFI bootloader issues fixed by switching to the Artful version of grub and the shim. I've updated http://162.213.35.187/proposed/streams/v1/index.json to use boot loaders from Artful in case anyone wants to test.
1711203,2017-12-07 22:39:42 UTC,"That's not going to change anything -- grub is doing exactly what it should: ask shim to validate the image it tries to chainload; and the image *does* validate successfully. The chain of trust is technically preserved, but shim doesn't manage to make sense of things, and refuses to continue loading."
1711218,2017-08-29 09:04:00 UTC,"Hi Lucas,"
1711239,2017-08-28 23:57:51 UTC,It sounds to me that we need clearer names for these commands to make easy distinction and to allow for intuitive flow of control.
1711239,2017-08-17 02:15:42 UTC,"Just a note here: ""juju offers"" is a command to be used by model admins to see information about the offers they have made."
1711243,2017-08-21 19:56:00 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086540.html
1711257,2017-08-17 01:27:04 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fa2158d9f68 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7fa2158da098 ""double free or corruption (!prev)"", action=3) at malloc.c:5049
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:3905
 __GI___libc_free (mem=<optimized out>) at malloc.c:2985
 g_free (mem=<optimized out>) at ../../../../glib/gmem.c:189"
1711258,2017-08-17 01:23:50 UTC,Inkscape runs on Windows XP Tablet Edition
1711258,2017-08-18 00:46:29 UTC,I made some experiments.
1711258,2017-08-18 00:59:13 UTC,"Ah, I just copied the fragment of my comments from GIMP bug report %) - of course there are no ""dotted circle"" and brushes in Inkscape, only line appears in the wrong position."
1711281,2017-08-18 11:17:41 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1711306,2017-08-17 08:27:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/494433"
1711306,2018-09-28 11:03:40 UTC,Any update on this bug?
1711306,2019-09-19 16:46:29 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.opendev.org/494433
Reason: Very old"
1711306,2021-01-16 04:17:47 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1711308,2017-08-17 08:52:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/494446"
1711308,2017-08-23 20:20:19 UTC,"Reviewed:  https://review.openstack.org/494446
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=048400bd4bbbf3bdf80f8b391712c5bc1e9dde79
Submitter: Jenkins
Branch:    master"
1711308,2017-08-24 08:59:41 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/497153"
1711308,2017-08-24 12:44:32 UTC,"Reviewed:  https://review.openstack.org/497153
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=44d21724a9da1d63e4bd26daf04ba7ab88200690
Submitter: Jenkins
Branch:    stable/pike"
1711324,2017-08-17 10:38:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/494473"
1711324,2017-08-24 08:56:45 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/497148"
1711324,2017-08-24 09:52:58 UTC,"Reviewed:  https://review.openstack.org/494473
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=c22f9cd882cd899b0e25796c40da67960d7a038d
Submitter: Jenkins
Branch:    master"
1711324,2017-08-24 12:58:10 UTC,"Reviewed:  https://review.openstack.org/497148
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=a8fe48685d7775e9dc439de08c1431ccdbacf8a9
Submitter: Jenkins
Branch:    stable/pike"
1711333,2018-08-14 23:34:50 UTC,">well, the snapcraft.yaml is the *exact* build reciepe
"
1711333,2017-09-09 22:10:37 UTC,"We are working on recording all assets of a snap, including additional assets brought in like plugins. We can certainly work on some tooling to read this recording and generate a snapshot of assets."
1711333,2017-08-18 15:00:21 UTC,"""Saying ""we're pretty sure the source is over there somewhere"" does not
satisfy our responsibility when distributing GPL binaries."""
1711333,2017-08-17 14:24:45 UTC,"Yes, this is an agreed goal, together with things like debug artifacts
(symbols). It is also important so that we can automate the process of
notifying publishers about security issues in dependency libraries that
would warrant a rebuild."
1711333,2017-08-18 09:58:25 UTC,"snaps nowadays ship /snap/<snap name>/current/snap/snapcraft.yaml which should have most/all build information in it already ... (upstream source, binaries that are used from the archive, patches (or at least a source to the build system used to build it to look up patches))"
1711333,2017-08-18 14:18:33 UTC,"On Fri, Aug 18, 2017 at 09:58:25AM -0000, Oliver Grawert wrote:

> snaps nowadays ship /snap/<snap name>/current/snap/snapcraft.yaml which
> should have most/all build information in it already ... (upstream
> source, binaries that are used from the archive, patches (or at least a
> source to the build system used to build it to look up patches))
"
1711337,2017-09-19 09:34:00 UTC,Today I build firefox 56.0 beta 12 which segfaults as well (on gentoo-armv7a-unknown-hardfp)
1711337,2017-09-04 23:14:13 UTC,"Same problem on ASUS Chromebook C201 running Xenial under Crouton (armhf).
firefox 55.0.1 and 55.0.2 (both published 8/17) crash immediately at launch."
1711337,2017-09-18 06:02:52 UTC,"On a rpi2 I tested Arch Linux recently, and their firefox-55.0.2 binary does work like a charm. Which makes me wonder if this is a bug somewhere in the toolchain (they use bleeding edge very latest gcc/glibc/etc.), or if the culprit could be found with the configure options."
1711337,2017-09-05 22:12:45 UTC,Not in Ubuntu.  The link above is from March.
1711337,2017-09-05 18:15:30 UTC,"No, people go back to 52 because it is working and it is under active developement, hence gets sec. updates. firefox 53 and 54 branches are stalled, they are very likely vulnerable."
1711337,2017-09-05 18:01:04 UTC,"On the Mozilla bug people are saying they had 54 working, but there was no 53 or 54 on armhf in Ubuntu?  That is why people are rolling back to 52 isn't it?"
1711337,2017-09-04 19:30:09 UTC,"Same problem, Ubuntu MATE 16.04 on ASUS Chromebook Flip (C100P)"
1711337,2017-10-20 12:47:10 UTC,"Please, fix it on Ubuntu 16.04 (latest Release and latest Beta are KO) !"
1711337,2017-09-02 12:47:02 UTC,"I also got the same problem on Raspberry Pi3 with Ubuntu Mate 16.04 as soon as I did the first update.
https://ubuntu-mate.community/t/firefox-55-0-2-doesnt-start-crashes-on-ubuntu-mate-raspberrypi-3/14637 has some workarounds, if anybody thinks to look there."
1711337,2017-09-01 19:28:15 UTC,"I run into this on 14.04 with armhf / arm device, it is an old ac100 netbook. Is there any kind of upstream bug at mozillas bugtracker?"
1711337,2017-08-29 20:13:37 UTC,I got the same problem on Raspberry Pi3 with Ubuntu Mate.
1711337,2017-08-27 18:17:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711337,2017-08-17 19:05:38 UTC,I have both an Odroid XU4 and crouton xenial  (running on Asus C100) which are arm based and Firefox also does as described - Intel based machines that I have do not exhibit this issue
1711337,2017-09-23 05:55:45 UTC,This bug was fixed in the package firefox - 55.0.2+build1-0ubuntu4
1711337,2017-09-04 12:22:50 UTC,"This is probably an unhelpful post, but ff 55 works on arm64.  So if you have a pi 3 and are desperate for the latest ff then *ubuntu arm64 is a possibility.  Same machine crashes with lubuntu 16.04 armhf."
1711337,2017-09-28 20:54:03 UTC,Firefox (55.0.2+build1-0ubuntu0.16.04.1) still crashing / unable to open on my Asus Chromebook running crouton target lxde
1711337,2017-09-29 06:54:38 UTC,"That is because, as far as I understand it, this bug hasn't been resolved for any ubuntu version lower than artful (17.10), for reasons unexplained. It might be related to the release of 56.0 a day ago, so it is best to wait a few days and hopefully the fix will be backported to esr branches."
1711337,2018-03-25 22:59:07 UTC,"I thought it might be useful for you folks who have compiling experience to compare the compiler switches used in the Trusty build for 57.04 with those from Arch 59.0 (from post #90), so I've listed them in columns (attached), after I attempted to pull the switches out of @herrtmison's screenshot (might be a few errors from that though)."
1711337,2017-10-11 13:38:18 UTC,Any idea when the bug will be fixed in 56?
1711337,2018-03-26 12:09:23 UTC,@jdonald: how can I direct the output of 'layout asm' from gdb into a textfile?
1711337,2018-03-27 03:37:10 UTC,Thanks @Chris!
1711337,2018-03-31 23:33:56 UTC,"@levente (and maybe @herrtimson),"
1711337,2018-04-01 22:22:14 UTC,"The fix from 59.0.1 to 59.0.2 is literally two lines, it shouldn't be a problem."
1711337,2018-04-06 01:30:41 UTC,Here is a working Firefox 59 deb package cross-compiled for 18.04 armhf: https://www.dropbox.com/s/17ypog6btdq4wj7/firefox_59.0.1%2Bbuild1-0ubuntu1_armhf.deb?dl=0
1711337,2018-04-06 02:01:28 UTC,"Great , thank you ! I have a special build of skia dir I will try this into your build and see if it will work with skia asm anabled . Thanks again for hard work !"
1711337,2018-04-06 08:33:18 UTC,"This patch should make it work! I was more lucky than anything else, because there is a compile error with firefox-60.0 betas on armhf which made me find https://bugzilla.mozilla.org/show_bug.cgi?id=1434526"
1711337,2018-04-06 08:51:08 UTC,toolchain used is:
1711337,2018-04-07 03:50:51 UTC,"@herrtimson are you expecting revert-128661.patch to fix the strd r2, r3, [r1] startup segfault on xenial/trusty, the Skia assembly illegal instruction, or both?"
1711337,2018-04-07 08:16:46 UTC,"The patch unbreaks the compile of firefox-60 betas on armhf, but at the same time it fixes the startup segfault which I had with the toolchain pasted in #120 with stable firefox."
1711337,2018-04-09 23:14:01 UTC,"@herrtimson from my tests that patch does not resolve the strd r2, r3, [r1] crash on Xenial. However, I do believe it's entirely possible that it indirectly fixed the issue with your gcc-7 toolchain. I'm starting to wonder if this crash does not have a single cause but rather is a codepath that Firefox goes down if there is one of many possible failures in startup."
1711337,2018-04-10 03:57:16 UTC,"@jdonald Wow (& sound a hats being taken off).
That really moves the boat forward - well done!
I did wonder what it was that allowed arch to work, and had a hunch that it would be hiding in plain sight in their PKGBUILD file, if only I could understand it.
Thank you for all that work - & your upstream fix intentions!"
1711337,2018-03-25 04:09:56 UTC,"@herrtimson we already confirmed that the gcc-7 / Bionic build crashes on the exact same misaligned instruction in Skia. See responses #48 and #50 for how I tested this, the point being that waiting for Bionic alone won't fix this."
1711337,2018-05-04 17:36:05 UTC,@herrtimson
1711337,2018-05-04 17:57:23 UTC,"With debian file I mean the xz file which has all the patches, build scripts and so on, it should be called firefox_59.0.2+build1-0ubuntu0.14.04.4.debian.tar.xz"
1711337,2018-05-04 19:22:30 UTC,"Fine!!!!!!
I installed this to my new tinkerboard ubuntu 16.04, Armbian kernel 4.4.120.
Seems to work fine."
1711337,2018-05-05 00:13:46 UTC,@herrtimson I looked in the tarball and don't even see mention of my use of clang in mozconfig.
1711337,2018-05-05 05:52:29 UTC,"Hi Donald,
I am writing this e-mail using your new
firefox_59.0.2+build1-0ubuntu0.14.04.4_armhf.deb version on a
TinkerOS, Debian GNU/Linux 9.4 (stretch) , kernel 4.4.71+
I started firefox in Downloads folder from terminal and got the following lines:
linaro@tinkerboard:~/Downloads$ firefox
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so
[fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so"
1711337,2018-05-05 13:20:40 UTC,"Well, for me it doesn't really work. Downloaded this deb file from the github repo: firefox_59.0.2.build1-0ubuntu0.14.04.4_armhf.deb , installed it with dpkg -i , and got the error of 'ungültiger maschienenbefehl', which I am not sure what it does mean at all. Could be illegal assembler instruction."
1711337,2018-05-06 01:55:11 UTC,"Lars, I went to sites like Gmail or Youtube that I thought had a chance of using optional NaCl, but I haven't been able to reproduce those error messages. I don't think Firefox supports NaCl, even with a plugin. Is it possible you imported browser settings from Chromium and it happened to include their NaCl extension? You could rule this out by moving or deleting ~/.mozilla/firefox then trying again."
1711337,2018-05-06 10:28:19 UTC,"James,
Sorry, I had to report that the bug appeared only when starting
Firefox the first time since then everything is ok."
1711337,2018-05-10 16:45:21 UTC,"Hi James, I have tested your
firefox_59.0.2+build1-0ubuntu0.14.04.4_armhf.deb on a
Debian GNU/Linux 9.4 (stretch) and Rockmyy's
Linux tinkerboard 4.17.0-rc3-RockMyy-Seventeen"
1711337,2018-05-11 13:21:02 UTC,"Hi everybody, Mozilla developer here, I've come across this after we noticed the crash spike on our servers. The relevant bug is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1452128"
1711337,2018-05-17 11:31:45 UTC,firefox 60.0+build2-0ubuntu1 is launching for me without crashing (on ubuntu-mate 18.04 on rasberrypi 2B). I have not made any other changes.
1711337,2018-05-30 14:24:34 UTC,Firefox working too on armhf xubuntu 18.04! (Pi 3B)
1711337,2018-07-17 03:16:58 UTC,"Thanks Mathias and Donald (comments 39 & 40)
after update to v61, Firefox crashes when lunched
Now, It works for me after installing v 57.0.4
Thanks a lot again for your help"
1711337,2018-07-21 20:28:18 UTC,still fails over and over again with 14.04 and 16.04!
1711337,2018-05-04 17:55:45 UTC,"Ah, cool thing! Could you please post a split patch against the debian file, so that I can see what you have changed exactly and how?"
1711337,2018-09-19 07:48:42 UTC,so the next update for thunderbird will carry this error?
1711337,2018-03-24 11:08:34 UTC,"If I use gcc-6.4.0 to compile with -g I get the same corrupt stack error as @levente before. Currently thinking about upgrading to gcc-7, as a last ressort, or waiting for bionic release in roughly a month or so."
1711337,2018-03-22 23:26:25 UTC,"@Chituc,"
1711337,2017-10-28 09:37:20 UTC,"I just tested, bug is not fixed in 16.04 and not in 14.04."
1711337,2017-11-07 16:31:25 UTC,"This is not fixed in 17.04 either.  Tried 55 which supposedly has the fix above, and 56."
1711337,2017-11-07 16:33:34 UTC,Sorry that should of been 17.10 (artful ardvark)!
1711337,2017-11-10 21:42:38 UTC,Tagged also affected releases based on comment #20 and comment #22.
1711337,2017-11-20 05:34:11 UTC,57 on 17.10 does not work either.
1711337,2017-12-08 18:43:35 UTC,"Please change status back to ""confirmed"". The released fix did not work, as evidenced by the ongoing duplicate bug reports."
1711337,2017-12-11 03:28:13 UTC,"The latest package installs on 16.04.3 does not work either.
I only could get it working by installing the ""firefox_57.0.1+build2-0ubuntu0.16.04.1_armhf.deb"" package.
Anyone has got if there is any latest fixed version?"
1711337,2017-12-11 07:03:26 UTC,"So ""firefox_57.0.1+build2-0ubuntu0.16.04.1_armhf.deb"" is working ?"
1711337,2017-12-11 10:35:58 UTC,Confirmed as still broken on Raspberry Pi3
1711337,2017-12-11 10:40:17 UTC,The fix was never ported into v56 or newer
1711337,2017-12-30 08:55:28 UTC,"That fix was:

>   * Hopefully fix LP: #1711337 by building the armhf build with
>     -fno-schedule-insns to work around a compiler bug


?"
1711337,2017-12-31 05:40:12 UTC,firefox 57.0.3+build1-0ubuntu0.17.10.1 still fails.
1711337,2018-03-23 19:13:42 UTC,"Ubuntu builds firefox for trusty with g++-4.9 , I checked this on amd64 some time ago and the build logs tell me that the armhf toolchain is as well g++-4.9"
1711337,2017-12-31 09:48:17 UTC,"Not fixed for trusty, it still fails with the same error over and over again."
1711337,2018-01-07 20:30:50 UTC,Maybe someone could ping the team in the irc?
1711337,2018-01-08 23:26:07 UTC,firefox-57.0.4 still fails
1711337,2018-01-09 10:59:46 UTC,This bug is not fixed properly
1711337,2018-01-10 04:07:31 UTC,"Thanks for providing the stack trace, Lars."
1711337,2018-01-10 21:41:22 UTC,"I have the same issue, however, I don't have the same stack trace."
1711337,2018-01-11 07:08:50 UTC,"levente,"
1711337,2018-01-11 10:11:29 UTC,This works with Ubuntu Mate 17.10 (armhf) on a Raspberry Pi 3
1711337,2018-03-19 14:10:49 UTC,"there is one bug at mozilla about clang and arm, but it is more about android, I guess. Still: https://bug635044.bugzilla.mozilla.org/show_bug.cgi?id=1163171"
1711337,2018-03-19 14:42:45 UTC,"This is the freebsd patch from their bug report. It was generated against their ports tree, I edited it so that it can be applied against the firefox source tree instead. This is not an official patch, and it fixes freebsd only, but still it might be helpfull to see what they changed. It is confirmed to build at their ends with clang for armv6 + armv7"
1711337,2018-03-19 16:23:24 UTC,"The attachment ""firefox-esr-arm-clang-FREEBSD.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1711337,2018-03-19 17:23:14 UTC,"> [herrtimson] I wrote an email to Chris Coulson, asking for some assistance with the cflags. Hopefully he'll read it.
"
1711337,2018-03-20 02:48:59 UTC,"CFLAGS=""-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16"" is the default for armhf.  In fact, it's what *defines* armhf as armhf.  Unless something is explicitly setting those things differently, they don't need to be on the commandline at all."
1711337,2018-03-20 15:19:19 UTC,"Ugh, yeah doing some simple helloworld tests confirms these are armhf gcc *defaults*."
1711337,2018-01-07 14:23:48 UTC,"I think this bug can be fixed, but the first step is getting someone with the required permissions to acknowledge that it exists, and change the status back to confirmed. With its current status, it probably isn't showing up on the radar of any Ubuntu developers."
1711337,2018-11-12 08:11:31 UTC,"From what I can tell the maintainers have no intention of spending time supporting Ubuntu 16.04 or older. Even when Xenial was the current LTS they weren't responding here, and now that 18.04 has been out for 5 month there's even less motivation to handle older distros."
1711344,2017-09-19 15:47:19 UTC,"Please provide more details - situation, actual returned state etc."
1711344,2017-10-02 20:16:10 UTC,Function block_state() doesn't return a value block_jn_obstructed when next junction is switched on ex. ahead once we stand on the sidetrack. It makes junction ripped.
1711344,2017-10-16 16:14:19 UTC,"If the switch ahead is set against the train and it is 'locked' by another train (path for other train is cleared over the switch or the train is occupying this switch), the state BLOCK_JN_OBSTRUCTED is returned as it should.
Are you changine the setting of the switch manually?
In what mode are you running (explorer, activity, timetable?)"
1711344,2017-10-24 12:59:13 UTC,"I play in the explorer mode, but in MSTS this also worked."
1711346,2018-11-08 00:47:20 UTC,I can confirm this bug still exists on Ubuntu 18.04 as of today.
1711346,2018-07-05 11:22:33 UTC,"thanks - I can confirm gprolog 1.4.4 compiles from source ok on Ubuntu 18.04, and runs without this bug.  I wasn't expecting the 1.4.5 bugfix to appear here but thought it would make sense to package 1.4.4 rather than 1.4.5"
1711346,2018-07-04 08:23:52 UTC,"Here's the simplest failing test example I could come up with, which is close to 'hello world' for prolog :"
1711346,2018-07-04 16:02:43 UTC,"Hello,"
1711346,2018-07-04 16:33:48 UTC,"The attachment ""Patch against previous version of gprolog (latest stable)."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1711346,2018-02-25 16:56:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711346,2018-07-03 17:59:36 UTC,"Just to emphasize, this bug means that the Prolog programming language is realistically unavailable in all Ubuntu versions since 16.04.  The 1.4.5-4.1 build of gprolog has this fundamental crippling bug as reported by the OP - even the most basic Prolog programs will not run - and unfortunately the 1.4.4 make from source also throws up a number of compile errors so it is a specialist job to get that code installed."
1711348,2017-09-05 19:45:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711355,2017-08-18 02:48:18 UTC,"There is a way to set this for a single agent as of 2.2.0, but requires editing the agent.conf file for any agent, and setting the LOGGING_OVERRIDE key in the values map, and restarting the agent."
1711355,2017-08-18 13:28:56 UTC,"On Fri, Aug 18, 2017 at 02:48:18AM -0000, Tim Penhey wrote:

> There is a way to set this for a single agent as of 2.2.0, but requires
> editing the agent.conf file for any agent, and setting the
> LOGGING_OVERRIDE key in the values map, and restarting the agent.
"
1711355,2017-08-22 02:31:08 UTC,Ah... yes that does look right.
1711355,2017-08-22 15:15:23 UTC,"On Tue, Aug 22, 2017 at 02:31:08AM -0000, Tim Penhey wrote:

> Ah... yes that does look right.
>
> Which agent.conf did you change, and what version of juju are you
> running?
"
1711357,2018-12-03 02:39:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711358,2017-10-14 08:56:21 UTC,This bug was fixed in the package linux - 4.13.0-16.19
1711358,2017-10-11 17:44:31 UTC,"I found that a fix for this was comitted upstream quite recently, cherry picked this to artful and it resolves the issue in my testing. Now applied to artful/master-next."
1711358,2017-10-09 15:24:13 UTC,I ran a bisect which identifies this as the first commit with this bug:
1711358,2017-09-29 18:53:13 UTC,"So I think I can now at least explain the weirdness. Booting from the ISO as well as the first boot in OEM mode seem to be in a way where grub does not use graphics mode and hands that off to a vt. In that case, when the kernels starts there will be no VESA framebuffer which later gets switched over to qxl framebuffer."
1711358,2017-09-28 14:20:34 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1711358,2017-09-28 12:49:41 UTC,Just as an update as I do not know how much gets accomplished here this week. The info from the crash indicates that some swap linked list which is supposed to be empty seems to have some elements on it. There is no obvious change related to that in 4.14~rc1 (which is the upstream version the tested kernel is based on). So we need to figure out what would be the change which we need. Some reference counting feels like maybe could be related but hard to say and we might need to bisect to find it.
1711358,2017-09-26 20:11:04 UTC,"4.14.0-0.1
from https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+sourcepub/8271798/+listing-archive-extra"
1711358,2017-09-25 21:47:27 UTC,This bug is also reproducible with the end user stage of an OEM installation which runs ubiquity-dm like a boot from an ISO.
1711358,2017-09-22 08:42:24 UTC,"Unfortunately I don't seem to have access to the latest images and this happening only when booting the ISO makes it hard(er) to grab data. I did finally succeed by using ""virsh dump --memory-only <domain> <file>"" and then ""sudo strings <file>|less"". And it looks like the qxl drm driver is crashing. I put the data here for reference but if you could do the same with an iso containing the 4.13 kernel, that would be great."
1711358,2017-09-26 19:33:07 UTC,"Hm, would be good if you noted down more exactly which version/ppa. I assume it is the mainline builds and likely 4.14~rc2."
1711358,2017-09-15 07:06:31 UTC,It happens even if you start a VM directly with qemu from the command line with the qxl driver (option -vga qxl) independently of virt-manager.
1711358,2017-09-18 10:02:42 UTC,"@bdmurray, I'd like you to reconsider the notfixing tag, it's a real issue for QA because qxl is the only driver that works with wayland. The system falls back to X with the standard vga driver and does not boot after installation with cirrus."
1711358,2017-08-17 12:38:29 UTC,manifest of the last known good image
1711358,2017-08-17 12:38:49 UTC,Manifest of the first broken image
1711358,2017-08-17 12:39:29 UTC,diff between the manifests
1711358,2017-09-04 10:10:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711358,2017-09-22 09:08:22 UTC,"Trace with 4.13
kernel BUG at /build/linux-jlxc7t/linux-4.13.0/drivers/gpu/drm/ttm/ttm_bo_util.c:589!
invalid opcode: 0000 [#1] SMP
Modules linked in: overlay nls_utf8 isofs dm_mirror dm_region_hash dm_log qxl ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse pata_acpi e1000 floppy
CPU: 0 PID: 210 Comm: plymouthd Not tainted 4.13.0-11-generic #12-UbuntuJ
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014
task: ffff9b5639bb9600 task.stack: ffffbac6806ac000
RIP: 0010:ttm_bo_kmap+0x1b5/0x260 [ttm]
RSP: 0018:ffffbac6806afb80 EFLAGS: 00010202
RAX: ffff9b5639831f90 RBX: ffff9b5639b18000 RCX: ffff9b5639b18290
RDX: 0000000000000300 RSI: 0000000000000000 RDI: ffff9b5639b18058
RBP: ffffbac6806afbc0 R08: ffff9b5639b18128 R09: 0000000000000400
R10: 0000000000000008 R11: 0000000000001559 R12: ffff9b5639e206a8
R13: 0000000000000000 R14: ffff9b563ab52b40 R15: 0000000000000000
FS:  00007f203aef2b80(0000) GS:ffff9b563dc00000(0000) knlGS:0000000000000000^
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f245a8d3f20 CR3: 000000007a0a7000 CR4: 00000000000006f0
Call Trace:
 ? qxl_bo_kunmap_atomic_page+0x85/0x90 [qxl]-c
 qxl_bo_kmap+0x42/0x70 [qxl]ut
 qxl_draw_dirty_fb+0x1f5/0x420 [qxl]
 qxl_framebuffer_surface_dirty+0xa0/0xf0 [qxl]
 ? __kmalloc+0x1c5/0x200o
 drm_mode_dirtyfb_ioctl+0x17e/0x1c0 [drm]
 ? drm_mode_getfb+0x110/0x110 [drm]
 drm_ioctl_kernel+0x5d/0xb0 [drm]
 drm_ioctl+0x31b/0x3d0 [drm].
 ? drm_mode_getfb+0x110/0x110 [drm]
 ? ep_poll+0xa7/0x3b0
 do_vfs_ioctl+0xa5/0x610H
 ? wake_up_q+0x80/0x80
 SyS_ioctl+0x79/0x90
 entry_SYSCALL_64_fastpath+0x1e/0xa9.
RIP: 0033:0x7f203a5cedd7
RSP: 002b:00007ffdbe6da488 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000564f2479f3a0 RCX: 00007f203a5cedd7
RDX: 00007ffdbe6da4c0 RSI: 00000000c01864b1 RDI: 0000000000000009
RBP: 0000000000000002 R08: ffffffffffffff80 R09: 00007ffdbe6da460
R10: 000000000000000a R11: 0000000000000246 R12: 00007ffdbe6da760
R13: 00000000ffffffff R14: 0000000000000000 R15: 00007f203acd32d0
Code: d0 49 8b be 80 00 00 00 48 c1 e6 0c 41 f6 46 62 04 74 4a 49 03 7e 70 4c 01 e7 e8 97 33 b3 ca 48 89 03 44 8b 45 d0 e9 18 ff ff ff <0f> 0b 4b 8d 7c 2c 58 44 89 45 c4 e8 0b b0 3c cb 44 8b 45 c4 e9
&RIP: ttm_bo_kmap+0x1b5/0x260 [ttm] RSP: ffffbac6806afb80"
1711358,2017-09-04 12:10:35 UTC,Whatever it is causing the issue - it's not specific to Ubuntu as Xubuntu affected as well.
1711358,2017-09-07 15:28:34 UTC,Realized a plymouth task would be right when I checked for the bug number to pass it along.
1711358,2017-09-12 18:55:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711358,2017-09-14 22:21:27 UTC,A comment in a duplicate bug of this states the following:
1711358,2017-09-04 10:11:34 UTC,"I can confirm the issue and dup'ed bug 1714638 onto this where people assumed first it would be an error in the virst stack.
From there TL;DR:
- works with cirrus/vga, but not qxl
- works if nosplash is set
- works on Xenial but not on Artful"
1711359,2019-11-01 21:09:04 UTC,"pkg does seem to be an odd choice of name, but by now it's pretty well established.  And on the plus side it's short."
1711377,2017-08-17 14:22:04 UTC,Added to Trello: https://trello.com/c/OZL9UVED/245-bug1711377-nautilus-desktop-mode-should-relearn-handline-a-dock-nicely
1711377,2017-08-17 22:06:08 UTC,The first issue is bug #1705285 / https://bugzilla.gnome.org/show_bug.cgi?id=760651 right?
1711377,2017-08-18 16:10:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711377,2017-09-20 07:13:48 UTC,I am unduplicating that one as it was for intellihide as well. Keeping the intellihide part here.
1711377,2017-09-27 21:01:28 UTC,"Valid bug, but there are more important bugs to fix before release."
1711377,2018-03-06 08:45:23 UTC,This will require significant work and won't get done this cycle.
1711377,2019-05-22 21:57:44 UTC,"An alternative (preferable IMO, and probably simpler) is to make the dock configurable to always hide."
1711388,2017-08-17 19:03:42 UTC,Added gdm log
1711388,2017-08-21 22:47:04 UTC,"I found the issue. It was mainly me, but i think something is still missing.
As I was updating from early ubuntu GNOME, the ubuntu-desktop metapackage wasn't installed, causing the ubuntu session to silently fail.
I think that ubuntu-session should depend on ubuntu-desktop."
1711395,2019-09-19 12:04:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1711395,2018-08-26 19:54:05 UTC,"There should be a way to add both allow-transfer and allow-query in the global options block, as well as per-domain.  (Data center my have customers that are providing off-site secondary DNS, and need to be able to get the zone.)"
1711395,2017-11-10 00:35:35 UTC,It would be great if implemented with 'allow-query' option with being able to define ACLs as well.
1711407,2020-02-24 05:23:18 UTC,"4.15.0-54-generic is bug free
5.3.0-28-generic has the bug"
1711407,2018-04-30 12:18:41 UTC,"Hi Dan,"
1711407,2018-04-30 11:52:50 UTC,"Hi @gservat,"
1711407,2018-04-29 23:54:14 UTC,"Hi Dan,"
1711407,2018-04-23 21:43:08 UTC,"> the CPU usage is zero, there is nothing popping up. The tasks causing the high load
> value are in D state
"
1711407,2018-04-18 08:17:59 UTC,"Hi Dan,"
1711407,2018-04-16 17:57:01 UTC,"> The machine continue to run and the docker is still able to create new instances,
> i.e. there is no complete lock out.
"
1711407,2018-04-30 14:14:08 UTC,"> The symptoms seen are a number of docker commands that just hang indefinitely (e.g.
> docker ps, spinning up new containers). Occasionally, after a long time, we have
> seen it come back and continue working OK (like whatever was holding the lock
> released it finally), but most of the time it hangs indefinitely
"
1711407,2018-04-14 20:16:00 UTC,"Hi Dan,"
1711407,2018-04-13 17:15:35 UTC,"Hi there, great to hear the progress!"
1711407,2018-04-13 14:23:58 UTC,"Jiri,"
1711407,2018-04-13 12:39:32 UTC,Just to re-summarize this:
1711407,2018-04-12 21:43:33 UTC,"Hi Jiri,"
1711407,2018-04-12 19:55:05 UTC,"Hi Dan,"
1711407,2018-04-02 12:53:16 UTC,"Jiri,"
1711407,2018-04-01 14:01:27 UTC,"Hi Dan,"
1711407,2018-04-13 17:43:45 UTC,"> I have just reproduced it using the previous #43+hf1711407v20180412b2"" kernel:
"
1711407,2020-08-21 17:50:48 UTC,Bug also happens on 5.4.0-42-generic.
1711407,2018-05-07 02:14:14 UTC,"Hi Dan,"
1711407,2018-03-22 17:24:18 UTC,"> Hi, might be useful to find root-cause
"
1711407,2020-02-24 05:21:05 UTC,"4.15.0-54-generic did work great in the past
we moved to 5.3.0-28-generic and this bug is notable..."
1711407,2020-02-23 16:47:53 UTC,"hey guys, we create our namespace using ip netns add.
Each nameSpace has it's ipv6 and ipv4.
We notice that the ipv6 ping continues to report, but the namespace at /run/netns does not exist anymore."
1711407,2020-02-23 05:59:06 UTC,"Hi! I'm on Debian and I'm getting this issue with the following kernel:
4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26)"
1711407,2019-04-04 12:23:00 UTC,"unfortunately I've moved away from kernel work, for now at least, and no longer have time to continue this bug; if anyone else would like to pick up the work, I'm happy to answer questions."
1711407,2018-08-08 21:45:29 UTC,Using:
1711407,2018-08-08 21:44:20 UTC,"Dan,"
1711407,2018-08-05 07:40:06 UTC,Also seeing it on Ubuntu 18.04 on AWS:
1711407,2018-05-18 21:19:50 UTC,"> Would you be able to build a test kernel against this version?
"
1711407,2018-08-01 12:07:25 UTC,I'm hitting this bug frequently on AWS with Ubuntu 16.04.5 LTS:
1711407,2018-06-04 16:21:17 UTC,"> So they should not be operating on the same sock concurrently.
"
1711407,2018-06-04 16:19:30 UTC,"> is it possibility that sk->sk_dst_cache is overwritten?
"
1711407,2018-05-30 07:41:27 UTC,"is it possibility that sk->sk_dst_cache is overwritten? like in __sk_dst_check,
when tcp timer tries to resend a packet, at the same time, tcp_close is called, and a reset packet will send, and ip_queue_xmit will be called concurrent；"
1711407,2018-05-30 03:26:03 UTC,"I have the same issue, and I dump the vmcore, and find dst cache, hope it has some help.
this leaked dst is in dst_busy_list, except dst_busy_list, nowhere I can find it in
==============================
First case:"
1711407,2018-05-28 04:55:13 UTC,"Many thanks, Dan! Going to roll it out to a few test boxes and try it out over the next few days. Will report back as soon as I have some feedback."
1711407,2018-05-25 12:00:13 UTC,"> We're using a newer kernel:
> 4.4.0-109-generic
"
1711407,2018-05-19 11:02:08 UTC,"Thanks for the ping, Dan. No worries. Looking forward to it as this issue
seems to be biting us more frequently nowadays so really interested to see
if this kernel helps."
1711407,2018-07-24 09:32:47 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1711407,2018-03-22 14:21:05 UTC,"Hi, might be useful to find root-cause: we kept running into this Kernel bug triggered by docker somehow until deactivating IPv6. I have not seen it since then.
Regards, Hamza"
1711407,2017-11-02 12:15:15 UTC,According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
1711407,2017-12-20 18:54:20 UTC,"$ sudo add-apt-repository ppa:ddstreet/lp1711407
Cannot add PPA: 'ppa:~ddstreet/ubuntu/lp1711407'.
ERROR: '~ddstreet' user or team does not exist."
1711407,2017-08-31 16:31:36 UTC,With https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with:
1711407,2017-08-17 22:58:48 UTC,apport information
1711407,2017-08-17 22:58:46 UTC,apport information
1711407,2017-08-17 22:58:45 UTC,apport information
1711407,2017-08-17 22:58:44 UTC,apport information
1711407,2018-03-10 08:02:26 UTC,"Hi Dan, thanks for commenting. I started to lose hope already ;) Looking forward for next kernel, will test it right away."
1711407,2017-08-17 22:58:42 UTC,apport information
1711407,2017-08-31 17:55:10 UTC,Attached are the logs for an Oops on Ubuntu 14.04 on kernel linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
1711407,2017-08-17 22:58:40 UTC,apport information
1711407,2017-08-17 22:58:38 UTC,apport information
1711407,2017-08-17 22:58:37 UTC,apport information
1711407,2017-08-17 22:58:35 UTC,apport information
1711407,2017-08-17 22:58:35 UTC,"AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116,  1 Aug 17 17:27 seq
 crw-rw---- 1 root audio 116, 33 Aug 17 17:27 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=7356cc51-3c3e-4d0d-bb9c-9d8daf436e5c
InstallationDate: Installed on 2016-09-20 (331 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS ""Xenial Xerus"" - Release amd64 (20160719)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Dell Inc. PowerEdge R710
Package: linux (not installed)
PciMultimedia:"
1711407,2017-08-17 22:55:33 UTC,"Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial"
1711407,2017-08-17 16:34:07 UTC,Can anyone experiencing this issue please provide details such as:
1711407,2017-08-17 16:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1711407,2017-08-17 22:58:39 UTC,apport information
1711407,2017-09-07 15:33:10 UTC,bug 1715660 seems related
1711407,2017-08-17 22:58:43 UTC,apport information
1711407,2017-09-29 15:36:22 UTC,"We're seeing this on our build servers. These are VMWare virtual machines which run docker containers in privileged mode. Inside the containers are Jenkins agents and a build environment. Part of the build process uses unshare to create these namespaces: ipc uts mount pid net. If you have any questions about this arrangement, I can try to provide more detail and maybe example code."
1711407,2017-09-12 12:50:44 UTC,"Thank you for the reproducer, I have been able to reproduce this using docker-samba-loop scripts.  This should help me to dig into the kernel to see where the dst leak is coming from."
1711407,2017-12-20 16:11:24 UTC,"> the test kernel you were using had this one [1] included? It's upstream commit f186ce61bb82
"
1711407,2017-12-20 15:50:43 UTC,"Hi Dan,"
1711407,2017-12-13 17:46:41 UTC,"> So if there is something to test or debug, I would be happy to help fixing this issue.
"
1711407,2017-12-13 09:15:40 UTC,"Hi,"
1711407,2017-12-07 19:53:06 UTC,simpler reproducer for this using LXD instead of Docker:
1711407,2017-12-07 18:44:37 UTC,"> In both of our reproducers, we added ""ip route flush table all;
"
1711407,2017-11-27 08:36:37 UTC,his information might be relevant.
1711407,2017-12-20 17:13:10 UTC,"Ok, waiting for the build to finish and then will test&report ASAP."
1711407,2017-11-02 14:59:53 UTC,"Ok, seems that I'm than in the wrong ticket with my issues. :-)
Should separate Ubuntu bug reports be created (if they don't exist already) regarding the kernel
crashes?"
1711407,2017-11-02 15:16:56 UTC,"> Should separate Ubuntu bug reports be created (if they don't exist already) regarding
> the kernel crashes
"
1711407,2017-10-02 15:27:41 UTC,"Since xenial we have this very annoying behavior (unregister_netdevice: waiting for lo to become free. Usage count = 1) as well, which in turn makes a container reboot taking several minutes instead of seconds e.g. on vivid (lxc-ls -f also hangs for that time). E.g.:"
1711407,2017-10-11 21:04:58 UTC,"Hi everyone,"
1711407,2017-10-24 19:29:07 UTC,Is there any way for a non-kernel-dev type to see exactly which resource unregister_netdevice is waiting for? (Or does it only keep track of usage count?)
1711407,2017-09-07 16:13:09 UTC,I could not reproduce the bug with the described method with kernel 4.4.0-81-generic and neither with 4.13.0-041300rc7-generic. 4.4.0-81 logged a hung tasks but does not Oops.
1711407,2017-11-02 13:35:35 UTC,My analysis so far of the problem:
1711407,2017-11-02 13:39:43 UTC,"> Is there any way for a non-kernel-dev type to see exactly which resource
> unregister_netdevice is waiting for? (Or does it only keep track of usage count?)
"
1711407,2017-11-02 13:40:57 UTC,"> That the startup of containers is delayed is annoying.
> The much bigger issue is that it can reproducible cause a kernel Oops and
> crash a whole machine.
"
1711407,2017-10-25 10:23:36 UTC,"Hello Dan,"
1711408,2017-08-17 16:42:28 UTC,"This module is needed for HPC on IB/RDMA in Azure, so we'd like to avoid installing extras."
1711408,2017-08-21 19:44:37 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086539.html
1711411,2019-11-25 10:47:24 UTC,It's expected that the OS would show as Ubuntu Core.
1711413,2018-01-08 09:04:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711428,2017-10-17 04:17:41 UTC,[Expired for apt (Ubuntu) because there has been no activity for 60 days.]
1711428,2017-08-17 20:16:19 UTC,"On Thu, Aug 17, 2017 at 07:59:00PM -0000, Jim Browne wrote:

> However, is juliank's note about the implementation of After= a concern
> w.r.t. how LP#1693361 was resovled?
"
1711428,2017-08-17 19:49:13 UTC,"On Thu, Aug 17, 2017 at 07:20:20PM -0000, Jim Browne wrote:

> Hmmm.  I confirm what you see.
"
1711428,2017-08-17 19:33:05 UTC,"Not that if B has After=A does not imply that the two don't run at the same time. If B is already running, A will be started as well. That's the reason why we added a lock file in apt:"
1711428,2017-08-17 19:20:20 UTC,Hmmm.  I confirm what you see.
1711428,2017-08-17 19:59:00 UTC,"> So I think this is something that you will want to fix in your image
> mastering scripts.
"
1711428,2017-08-17 18:46:50 UTC,"The apt-daily-upgrade service already declares itself to be 'After=apt-daily.service'.  So there should be strict sequencing here of cloud-final.service -> apt-daily.service -> apt-daily-upgrade.service.  If that's not happening, this warrants analysis to understand why so that it can be fixed in the apt package directly rather than adding more relationships to the cloud-init unit."
1711429,2018-11-19 15:56:22 UTC,"I believe this is a duplicate of bug #1578662, which has a patch (I've been using https://launchpadlibrarian.net/279275413/debmirror.deb.patch)."
1711429,2020-05-19 11:42:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711457,2017-08-17 20:55:37 UTC,"I tried downloading Mono from their website (5.2.0.215) instead of the 3.12.1 offered on your website, and that didn't work either."
1711457,2017-09-11 03:07:59 UTC,Hello? :(
1711457,2020-07-18 21:04:17 UTC,Can this be reproduced with the latest Mono installer? https://www.mono-project.com/download/stable/
1711457,2019-06-04 22:16:02 UTC,Version 1.6 still has this problem on MacOS Mojave 10.14.5.
1711460,2017-08-18 20:42:14 UTC,"I believe so.
If my understanding on how tools that relay on libpcap works (arp-scan, netdiscover, ...) this could be a feature request for them.
For example, netdiscover beside active mode (that arp-scan also use) it have an additional passive mode, where it does not send ARP requests just listen for other's and it also omits local IP/MAC from report."
1711460,2017-08-18 00:03:33 UTC,"AFAIK, As arp-scan will show data for packets that went trough the interface, you won't see ARP request/reply to itself (as those will not ""reach the wire""). Hence, the ""missing"" local IP/MAC pair.
IINM, You can observe same behavior on any other linux system and with other tools (netdiscover, tcpdump).
(I agree that this behavior does make additional cognitive load - It will easily show duplicate IP address for other hosts but for your own host you have to keep in mind that your IP/MAC is missing from the report)"
1711460,2017-08-18 06:11:52 UTC,"So, if I understand correctly, this an issue with the arp-scan package?"
1711469,2018-11-08 10:12:38 UTC,I'm hitting this in RDO when building packages with python 3.6.
1711469,2019-09-19 17:27:11 UTC,"Reviewed:  https://review.opendev.org/587628
Committed: https://git.openstack.org/cgit/x/python-glareclient/commit/?id=b1364646f78cf9e24ca9f74a7af093d240c094c0
Submitter: Zuul
Branch:    master"
1711469,2017-08-23 15:44:21 UTC,This test also fails if the list order is different than expected:
1711474,2017-08-17 23:14:49 UTC,"Forgot to wrte that I do
# mount -o remount,rw /
# systemctl restart sddm systemd-resolved NetworkManager"
1711474,2017-08-17 23:16:01 UTC,"Upgraded to artful proposed, now NetworkManager does start, but the system still does not boot without
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=""rw"""
1711487,2017-08-28 15:49:01 UTC,did you run gnocchi-upgrade?
1711487,2017-08-29 04:03:50 UTC,"@gordon chung (chungg)
Yes, many times:)"
1711487,2017-08-29 12:59:25 UTC,can you create a new instance and see what error you see in collector and gnocchi-api logs? the errors you have in descriptions are errors post-creation so i'm not sure if the actual creation worked.
1711487,2017-10-03 18:24:38 UTC,closing since no feedback. please reopen if still an issue.
1711487,2018-03-26 02:54:29 UTC,I have got the same problem.
1711487,2018-03-26 02:55:18 UTC,ceilometer  -> gnocchi-api，/v1/resource/instance/xxx 404 error .
1711487,2018-03-26 03:00:42 UTC,"I have got the same problem.the following is the error log(gnocchi-api):
 [26/Mar/2018:10:55:58 +0800] ""PATCH /v1/resource/instance/13f27322-618f-45d3-b567-c7de223d0cc8 HTTP/1.1"" 404 114 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:02 +0800] ""POST /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1"" 400 580 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:03 +0800] ""POST /v1/resource/instance HTTP/1.1"" 400 117 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:04 +0800] ""POST /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1"" 202 4 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:04 +0800] ""PATCH /v1/resource/instance/13f27322-618f-45d3-b567-c7de223d0cc8 HTTP/1.1"" 404 114 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:06 +0800] ""POST /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1"" 400 580 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:07 +0800] ""POST /v1/resource/instance HTTP/1.1"" 400 117 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:08 +0800] ""POST /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1"" 202 4 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
[26/Mar/2018:10:56:08 +0800] ""PATCH /v1/resource/instance/13f27322-618f-45d3-b567-c7de223d0cc8 HTTP/1.1"" 404 114 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:15 +0800] ""POST /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1"" 202 4 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5""
 [26/Mar/2018:10:56:16 +0800] ""POST /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1"" 202 4 ""-"" ""ceilometer-collector keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.5"""
1711500,2017-08-18 11:17:28 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1711538,2017-10-23 12:08:48 UTC,Having it on by default was rejected in https://bugzilla.gnome.org/show_bug.cgi?id=694304
1711538,2020-04-26 11:42:09 UTC,"On a fresh Ubuntu 20.04 install I ran into this same issue. Tap to click works fine on the desktop, but it does not work on the login screen. The inconsistent behaviour can be very confusing."
1711538,2018-12-17 18:34:15 UTC,"Upstream bug-watch(Launchpad does not track GitLab, so here it is):"
1711538,2018-03-02 20:56:27 UTC,"Is this the same problem I'm currently experiencing on 18.04? Started to wonder if it froze as tap to click didn't work. The default setting in Ubuntu seems to be tap-to-click enabled, so it should probably work by default on the login screen too, for the sake of consistency."
1711538,2017-10-31 21:12:38 UTC,:/
1711538,2017-10-23 12:08:01 UTC,There is an upstream bug about that on https://bugzilla.gnome.org/show_bug.cgi?id=785855
1711538,2017-10-23 12:28:25 UTC,"Yeah, with an absolutely stupid comment. Anyway, there should be a way to enable it for login screen otherwise this commend is totally invalid and bug should be reopened."
1711538,2017-10-20 03:24:26 UTC,"  * What model laptop are you using?
Acer V3-771G / Acer V5-171G"
1711538,2013-05-24 04:17:58 UTC,"I have in mind that this idea was discussed along with other bug 651134 , however, not clear to me its not included as default feature."
1711538,2015-04-10 15:51:03 UTC,"http://wayland.freedesktop.org/libinput/doc/latest/tapping.html says:
""
Tapping is disabled by default, see this commit because:
- if you don't know that tapping is a thing (or enabled by default), you get spurious button events that make the desktop feel buggy.
- if you do know what tapping is and you want it, you usually know where to enable it, or at least you can search for it.
"""
1711538,2017-08-18 08:33:07 UTC,"Two questions:
  * What model laptop are you using?
  * Does tap-to-click start working after login?"
1711538,2017-10-23 09:37:38 UTC,Same issue on Lenovo Flex 14 laptop and 17.10.
1711538,2017-10-20 02:09:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711538,2013-02-20 20:14:53 UTC,"I introduced this bug in fedora, (https://bugzilla.redhat.com/show_bug.cgi?id=912886) and I've seen other distros that use GNOME with this capability enabled by default, but suggested I leave the bug in GNOME Bugzilla."
1711538,2017-08-18 09:17:23 UTC,"* What model laptop are you using?
- Lenovo Thinkpad X240"
1711541,2017-08-24 07:58:46 UTC,"This patch add check or uncheck pad length in die when tuning length single or diff track in PNS-router.
Autor Roman Bashkov."
1711541,2017-08-28 18:28:34 UTC,This patch seems reasonable to me except for a few coding policy violation.  Would our resident tuned length router expert care to weigh in on this?
1711541,2019-08-14 15:28:15 UTC,"Hi,"
1711541,2019-10-31 23:01:24 UTC,"Fixed in revision 4178cf7f3670df1b91953d0012de2c32e084144d
https://git.launchpad.net/kicad/patch/?id=4178cf7f3670df1b91953d0012de2c32e084144d"
1711541,2019-10-31 23:05:01 UTC,"If this shakes out in 6.0 with no issues, we'll consider moving it to 5.1.6 as well."
1711541,2019-11-04 17:16:19 UTC,"If cherry-picked, bring lp:1851251 with as well."
1711541,2017-11-16 00:24:39 UTC,"Hi Andrey,"
1711544,2017-08-19 05:41:27 UTC,For me it started to happen after Unity:Unity7 session was renamed To Unity:Unity7:Ubuntu. So many services which checks with XDG_DESKTOP are failing. And unnecessary services are starting.
1711566,2018-09-19 14:30:35 UTC,This is fixed in kio-extras 18.12.0 (which will be released in approximately 3 months). See the upstream bug report: https://bugs.kde.org/show_bug.cgi?id=375176
1711566,2018-05-05 17:50:27 UTC,+1
1711566,2017-10-13 00:59:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711566,2017-10-13 00:57:48 UTC,KDE bugs: https://bugs.kde.org/show_bug.cgi?id=375176
1711566,2017-11-25 02:42:29 UTC,+1
1711568,2017-10-10 14:54:23 UTC,"I have been running tempest against a new devstack and live migration seems fine. If this is still happening, can you re-open the bug. Thanks!"
1711568,2019-03-08 07:29:11 UTC,"Hello Chris,"
1711568,2019-03-24 23:47:08 UTC,I sent a mail about this issue to openstack-discuss mailing list.
1711571,2017-09-01 14:01:31 UTC,The package has been published and the bug is being set to Fix Released
1711571,2018-07-24 09:32:51 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1711571,2021-01-07 08:49:21 UTC,4.12 EOL
1711573,2017-09-27 04:22:50 UTC,This issue was fixed in the openstack/oslo.middleware 3.23.3 release.
1711573,2017-10-05 17:48:34 UTC,The verification of the Stable Release Update for python-oslo.middleware has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1711573,2017-09-27 04:22:24 UTC,This issue was fixed in the openstack/oslo.middleware 3.30.1 release.
1711573,2017-10-25 18:30:31 UTC,Regression testing was successful for xenial-ocata-proposed and zesty-proposed:
1711573,2017-10-25 18:13:14 UTC,The verification of the Stable Release Update for python-oslo.middleware has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1711573,2017-10-25 18:13:17 UTC,"This bug was fixed in the package python-oslo.middleware - 3.30.0-0ubuntu1.1~cloud0
---------------"
1711573,2017-10-24 16:08:10 UTC,OpenStack tempest regression tests have passed successfully against pike-proposed.
1711573,2017-09-26 15:28:37 UTC,"Hello Adam, or anyone else affected,"
1711573,2017-10-05 17:48:36 UTC,"This bug was fixed in the package python-oslo.middleware - 3.23.1-0ubuntu1.1~cloud0
---------------"
1711573,2017-09-26 04:07:10 UTC,This bug was fixed in the package python-oslo.middleware - 3.30.0-0ubuntu1.1
1711573,2017-08-21 15:15:56 UTC,"Reviewed:  https://review.openstack.org/495172
Committed: https://git.openstack.org/cgit/openstack/oslo.middleware/commit/?id=480d60ac856937e1a48c1ed6df3b7d2e59a974dc
Submitter: Jenkins
Branch:    master"
1711573,2017-09-26 14:27:12 UTC,"Hello Adam, or anyone else affected,"
1711573,2017-08-31 06:35:59 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/499470"
1711573,2017-08-31 06:41:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/499471"
1711573,2017-08-31 17:38:03 UTC,"Reviewed:  https://review.openstack.org/499470
Committed: https://git.openstack.org/cgit/openstack/oslo.middleware/commit/?id=d9ad4bae1e0d6c43a009d393ac94f7ff50116171
Submitter: Jenkins
Branch:    stable/pike"
1711573,2017-09-27 21:17:10 UTC,"Hello Adam, or anyone else affected,"
1711573,2017-09-06 08:27:47 UTC,This issue was fixed in the openstack/oslo.middleware 3.31.0 release.
1711573,2017-09-22 13:59:05 UTC,I've updloaded new versions of the package to artful (pike) and zesty (ocata).
1711573,2017-08-31 20:17:38 UTC,"Reviewed:  https://review.openstack.org/499471
Committed: https://git.openstack.org/cgit/openstack/oslo.middleware/commit/?id=74208402c6cadc0fb46379e2f7122eade7998883
Submitter: Jenkins
Branch:    stable/ocata"
1711573,2017-09-22 13:06:27 UTC,Ubuntu SRU details:
1711595,2017-08-18 12:24:43 UTC,"Hi Mounika,"
1711595,2017-08-21 07:15:07 UTC,"Hello Sharat,"
1711603,2017-08-18 15:15:11 UTC,does the apparmor being checked?
1711603,2017-08-18 17:30:31 UTC,"apparmor is enabled on all nodes.
Should I disable apparmor on all systems?"
1711603,2017-08-18 18:32:02 UTC,You can try to disable it. Do the compute node able to mount ceph storage?
1711603,2017-08-21 12:06:24 UTC,Disabling apparmor on all nodes doesn't helped.
1711603,2017-08-21 12:15:03 UTC,"Also, I am unable to mount ceph storage on compute."
1711603,2017-08-21 12:16:14 UTC,"root@vm0:~# sudo mount -t ceph 192.168.0.1:6789:/ /mnt/
mount error 110 = Connection timed out"
1711603,2017-08-22 01:51:48 UTC,"Does the ceph server 192.168.0.1 is listening on 6789? On the 192.168.0.1, check listening port, 'netstat -nutlp | grep 6789'."
1711633,2017-08-18 14:03:51 UTC,needed params:
1711638,2018-12-18 15:14:15 UTC,This is still an issue with Queens.
1711657,2017-08-18 14:44:20 UTC,"Adding gnome-settings-daemon as well for the OSD part, if communication needed."
1711687,2018-10-07 08:58:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711707,2017-09-18 19:11:31 UTC,"When we were working on requirements for moving course reserves to Evergreen, we also created requirements for the ability to store and revert copy parameters (circ modifier in addition to copy location). The requirements may be helpful for this bug - http://masslnc.org/node/3181#Feature:_The_ability_to_create_temporary_copy_parameters_and_to_restore_permanent_parameters"
1711710,2017-08-18 15:42:53 UTC,"Just to note, even when fixed, ironic+neutron+contrail will still have a problem of PXE->iPXE chainloading not working, but at least pure iPXE starts to work."
1711710,2017-08-22 06:18:20 UTC,the patch proposed here
1711710,2020-06-24 09:28:49 UTC,"Change abandoned by Riccardo Pittau (<email address hidden>) on branch: master
Review: https://review.opendev.org/493527
Reason: obsolete"
1711712,2017-08-18 18:24:24 UTC,"I see it fine, both in F&S and in the XML dialog (.92.1)"
1711716,2017-11-12 10:13:55 UTC,"Change abandoned by Eyal (<email address hidden>) on branch: master
Review: https://review.openstack.org/495411"
1711719,2017-08-18 19:27:20 UTC,You are missing some track sections in your tsection.dat. Probably you don't have the Xtracks or Ytracks version needed for this route.
1711734,2018-01-25 09:34:24 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3733
1711737,2020-03-11 02:18:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711741,2017-08-18 19:16:22 UTC,The upstream fix is available here:
1711747,2017-08-22 02:20:59 UTC,To be honest I don't think it is just openstack that has this implicit constraint.
1711747,2019-05-23 01:59:56 UTC,I ran into this as well when trying to add units to a model to test mixed CPU architectures.
1711750,2017-10-10 09:55:26 UTC,@Christopher Barrington-Leigh: Did the next backup finish without failure?
1711750,2017-09-24 21:26:58 UTC,This has just occurred to me on Ubuntu 17.04. My laptop was not put to sleep/closed during the backup. The backup was to an SSH site. I've been doing that for years and never received this error (to my knowledge).
1711753,2017-10-04 20:58:28 UTC,Upstream bug report: https://github.com/micheleg/dash-to-dock/issues/173
1711753,2017-08-19 05:36:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711753,2017-08-29 05:59:19 UTC,This is an extra-good idea given it would allow us to disable nautilus-desktop and thus avoid bug 1696621.
1711753,2017-08-19 06:44:02 UTC,"For some people like me who want their desktop to be clean, I prefer the trash bin to be on the Dock. This also has the advantage of easy access to the trash bin without going to the desktop."
1711755,2018-09-14 16:27:58 UTC,"Hello,"
1711761,2020-09-21 03:03:25 UTC,Thank you for reporting this bug to Ubuntu.
1711761,2020-11-20 04:19:25 UTC,[Expired for lxpanel (Ubuntu) because there has been no activity for 60 days.]
1711764,2017-08-19 03:08:16 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06) (32 bit exe build)"
1711764,2017-08-19 12:31:39 UTC,"it is interesting to note that this crash does not occur in the current 0.92.x branch, compiled using cmake. this is
Inkscape 0.92.2 (unknown), compiled Aug 7, 2017
the dll is libglib-2.0-0.dll version 2.28.8.0"
1711764,2017-08-19 20:18:14 UTC,"Duplicated crash on Win 8.1 64-bit, Inkscape 0.92.2 (5c3e80d, 2017-08-06)."
1711764,2018-01-20 16:53:55 UTC,This crash happens only on windows it seems!
1711764,2018-01-20 17:23:19 UTC,crash seems to depend on the version of glib
1711764,2020-09-09 08:25:03 UTC,"This seems to be a glib problem. As the included glib has been updated, this should no longer be an issue."
1711769,2017-08-19 00:55:02 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fecb74e4f68 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7fecb74e1b18 ""free(): invalid pointer"", action=3) at malloc.c:5049
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:3905
 __GI___libc_free (mem=<optimized out>) at malloc.c:2985
 CRYPTO_free (str=0x8e2d49adb0) at mem.c:442"
1711769,2017-09-01 20:37:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711775,2017-08-24 11:15:11 UTC,"Hi Henry,
here from your logs:"
1711775,2017-08-31 13:40:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711778,2017-10-07 10:59:58 UTC,Two options here - make official Firefox ESR package (see bug 1676164) or convert xul-ext-ubufox to WebExtension.
1711788,2017-09-05 06:44:46 UTC,I have been doing a lot of branch line working with single loco single cab GP American type loco.
1711788,2017-08-22 20:17:33 UTC,"The reference is where the train driver is. Even with a flipped loco, if the train driver is in the cab which is in front of the train, the gradient shows the correct indication, so there is no problem in my opinion."
1711800,2017-08-19 07:50:19 UTC,This is probably the same as Debian bug 864829¹. No solution found yet.
1711800,2017-08-19 07:55:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711800,2017-08-19 23:44:19 UTC,"In a common installation with ""sudo apt-get install espeakup"", it gives error and does not conclude.
The error does not occur when the kernel module ""espeakup_soft"" was previously loaded before installation: ""sudo modprobe speakup_soft && sudo apt-get install espeakup""."
1711801,2017-08-19 08:45:53 UTC,"Le 19/08/2017 à 10:20, Amr Ibrahim a écrit :

> apport-collect 1711801
"
1711801,2017-08-19 08:18:38 UTC,Thanks for filing a bug to help improve Ubuntu.
1711801,2017-08-19 08:20:34 UTC,Please type this in Alt+F2:
1711801,2017-08-19 08:35:59 UTC,"Le 19/08/2017 à 10:18, Amr Ibrahim a écrit :

> Thanks for filing a bug to help improve Ubuntu.
>
> In the future, please use 'ubuntu-bug package-name' to report Ubuntu bugs.
> https://help.ubuntu.com/community/ReportingBugs
>
> ** Package changed: plank (Ubuntu) => gnome-software (Ubuntu)
>
"
1711801,2017-08-19 08:45:34 UTC,apport information
1711801,2017-08-19 08:45:35 UTC,apport information
1711801,2017-08-19 08:45:37 UTC,apport information
1711801,2017-08-20 17:44:57 UTC,"OK, the bug is targeting gimp now."
1711801,2017-08-21 00:20:53 UTC,"The top one is the new GIMP snap, and the bottom one is the traditional GIMP .deb. The snap metadata is not translated yet, see [1] for some ideas on improving this. I'll assign this bug back to GNOME Software as that is the package that can try and reduce this confusion."
1711801,2017-08-21 00:23:40 UTC,"Forum post about GIMP snap:
https://forum.snapcraft.io/t/call-for-testing-gimp/"
1711801,2017-08-21 17:53:21 UTC,apport information
1711801,2017-08-21 17:53:22 UTC,apport information
1711801,2017-08-21 17:53:23 UTC,apport information
1711801,2017-08-21 17:53:25 UTC,apport information
1711801,2017-08-21 17:56:59 UTC,Apport done.
1711801,2017-08-20 17:45:39 UTC,"Again, please type this in Alt+F2:"
1711805,2019-02-07 14:36:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711809,2017-09-27 16:53:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711818,2018-04-26 16:14:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711820,2020-12-29 22:20:03 UTC,"Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1711826,2018-05-11 15:34:45 UTC,This change was made by a bot.
1711827,2019-12-02 21:12:01 UTC,"This is not a Scapy issue but an issue with your Python environment
(Probably was. This bug is years old)"
1711834,2017-08-19 14:13:20 UTC,You can see the transparent corner with GIMP.
1711836,2017-08-19 14:25:07 UTC,"StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
 __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
 std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
 __cxxabiv1::__cxa_throw (obj=obj@entry=0x931dd044c0, tinfo=0x931c312d50 <typeinfo for std::runtime_error>, dest=0x7f0bdecfc5b0 <std::runtime_error::~runtime_error()>) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:93
 repowerd::DBusConnectionHandle::request_name (this=this@entry=0x931dcfbb18, name=<optimized out>, name@entry=0x931c0f8c5d ""com.canonical.Unity.Screen"") at ./src/adapters/dbus_connection_handle.cpp:88"
1711838,2017-08-19 15:00:12 UTC,"StacktraceTop:
 WebCore::GLContextGLX::~GLContextGLX (this=0x7f57e82c3000, __in_chrg=<optimized out>) at ./Source/WebCore/platform/graphics/glx/GLContextGLX.cpp:286
 WebCore::GLContextGLX::~GLContextGLX (this=0x7f57e82c3000, __in_chrg=<optimized out>) at ./Source/WebCore/platform/graphics/glx/GLContextGLX.cpp:294
 std::default_delete<WebCore::GLContext>::operator() (this=<optimized out>, __ptr=<optimized out>) at /usr/include/c++/7/bits/unique_ptr.h:78
 std::unique_ptr<WebCore::GLContext, std::default_delete<WebCore::GLContext> >::reset (__p=<optimized out>, this=0x7f57e8609fb8) at /usr/include/c++/7/bits/unique_ptr.h:376
 std::unique_ptr<WebCore::GLContext, std::default_delete<WebCore::GLContext> >::operator=(decltype(nullptr)) (this=0x7f57e8609fb8) at /usr/include/c++/7/bits/unique_ptr.h:312"
1711838,2017-08-19 18:41:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711838,2017-08-30 21:04:45 UTC,"Can't help you more, because I DO NOT KNOW ""HOW""! You must understand that i am JUST A COMMON USER, who tries hardly. Thank you for your patience & assistance."
1711841,2018-12-19 15:55:04 UTC,The UI got refreshed and the issue seems to not be there anymore in the current version
1711841,2017-09-20 09:11:28 UTC,"Thanks, confirmed and sent upstream to https://bugzilla.gnome.org/show_bug.cgi?id=787933"
1711848,2019-11-15 05:37:47 UTC,"Closing because no longer replicated on master build or 1.0alpha0 appimage release (there is possibly some leakage, but its in the couple MB range, sometimes not growing at all)."
1711849,2017-08-19 19:48:51 UTC,Doesn't reproduce anymore - Just now it seems to have stopped happening. Maybe a recent update?
1711849,2017-09-02 08:46:01 UTC,"The problem seems to be connecting my Asus ux560u laptop (Ubuntu 17.04) to my Edimax EW-7438RPn router. The signal strength seems ok, and this issue happens only with my Edimax EW-7438RPn router."
1711849,2017-09-02 08:47:14 UTC,Additional info provided in comment #2
1711849,2020-06-05 15:26:27 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1711849,2020-08-05 04:17:37 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1711851,2017-09-27 00:17:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711854,2019-05-17 15:03:03 UTC,Is still wrong in the 1.6 and dev 1.7 releases from the official site. It seems it is a problem with the pinta.mo file in the locale/es/LC_MESSAGES folder. Generate a new one (with PoEdit or any online tool) from .po file in source should solve the problem. Maybe include a new generated pinta.mo file in the next release?
1711855,2019-12-26 19:15:12 UTC,Is there a PPA anywhere that contains a usable wine-stable?  Six months since the last post here and no progress seems to have been made...
1711855,2019-05-07 13:02:02 UTC,"Bug #1576326 (Xdg .desktop, .directory and mimetype files missing) seems to be a duplicate of this bug"
1711855,2017-09-01 16:01:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711855,2017-08-19 18:49:13 UTC,"When I was looking around some Wine repositories on another computer, I noticed that the Zorin OS guys have a Testing PPA for Wine builds with wine-stable 2.0.2 and the missing .desktop files included in the package (thereby fixing this usability bug). You can find the PPA here: https://launchpad.net/~zorinos/+archive/ubuntu/wine-testing"
1711855,2018-04-15 17:56:55 UTC,"[Speaking as Debian co-maintainer, Ubuntu is of course absolutely free to change the packages as they see fit.]"
1711858,2017-08-19 19:32:17 UTC,apport information
1711858,2017-08-19 19:32:18 UTC,apport information
1711858,2017-08-19 19:32:19 UTC,apport information
1711867,2018-09-30 12:23:11 UTC,I am currently running the 2.1.5-pre (build 2.1 r6771)
1711867,2020-05-29 21:40:41 UTC,Does it still happen with Mixxx 2.2.x?
1711867,2018-09-30 03:10:56 UTC,"Thanks for the update Ron, that doesn't sound good. Are you using the 2.1.4 release version or are you still building from master (2.3 pre-alpha)?"
1711867,2017-08-24 17:55:42 UTC,"Workaround is changing the folders (I added a few songs) so Mixxx 'accepts' them again.
But the Mixxx library is weird. Sometimes moving files works great and Mixxx updates the path, sometimes the old ones are marked as missing and new library entries are created and sometimes it breaks the whole Mixxx library system ^^"
1711867,2017-09-28 17:50:39 UTC,"Ok, continued using Mixxx:
I added a lot of files. New files are accepted correctly but often old files are then marked as missing - still remaining usable."
1711867,2018-09-21 14:00:59 UTC,"Since the report got updated just now, I wanted to inform you, that my library contains 444 tracks marked as missing as of today. Nearly all of them (didn't check all though) are actually available on the disk and I'm able to play them with mixxx.
Performing a library rescan increased the amount of missing tracks to 758."
1711886,2017-08-25 03:58:40 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1711886,2017-12-31 13:29:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711890,2017-08-20 07:22:52 UTC,Please let the machine run for 3-4 minutes in Live Mode. It would boot.
1711890,2017-08-20 07:28:27 UTC,Please take a look at this video helping to boot BackSlash Linux in Virtual Machine
1711890,2017-10-10 05:47:37 UTC,FIX:
1711891,2017-08-20 16:58:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/495569"
1711891,2018-11-09 09:57:27 UTC,The proposed fix errors with:
1711895,2018-01-24 22:26:17 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1441
1711895,2017-08-24 16:14:36 UTC,Could you run the program using PTDEBUG=1 pt-index-usage ... and paste the output please?
1711895,2017-08-26 05:54:46 UTC,"Hi,"
1711895,2017-08-22 14:44:40 UTC,"According to the error I see, the problem is there are references to a non-existing table in the slow.log file and pt-index-usage is failing in this situation. Could you confirm that's the issue?"
1711895,2017-08-23 09:03:00 UTC,You are right.
1711908,2018-05-11 15:34:53 UTC,This change was made by a bot.
1711916,2017-08-20 14:12:04 UTC,"StacktraceTop:
 wxWindow::DoClientToScreen (this=0x20aa719350, x=0x7ffcc0da674c, y=0x7ffcc0da6750) at ../src/gtk/window.cpp:3114
 wxWindow::DoClientToScreen (this=0x20aa719350, x=0x7ffcc0da674c, y=0x7ffcc0da6750) at ../src/gtk/window.cpp:3124
 wxWindow::DoClientToScreen (this=0x20aa719350, x=0x7ffcc0da674c, y=0x7ffcc0da6750) at ../src/gtk/window.cpp:3124
 wxWindow::DoClientToScreen (this=0x20aa719350, x=0x7ffcc0da674c, y=0x7ffcc0da6750) at ../src/gtk/window.cpp:3124
 wxWindow::DoClientToScreen (this=0x20aa719350, x=0x7ffcc0da674c, y=0x7ffcc0da6750) at ../src/gtk/window.cpp:3124"
1711916,2018-03-07 19:58:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711916,2018-10-04 19:37:29 UTC,Still crashes in 18.04/18.10.
1711916,2018-10-12 07:20:07 UTC,Still crashes with Ubuntu 18.10 beta (12 oct 2018) // amule 1:2.3.2-3build1
1711933,2017-10-14 21:47:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711939,2018-09-14 16:29:37 UTC,"I've upgraded the nvidia-340 driver to version 340.107, and the problem persists."
1711939,2017-10-19 15:08:51 UTC,Any ideas?
1711940,2017-08-20 20:11:07 UTC,"Sorry, but we don't use launchpad for project management anymore."
1711947,2019-12-19 11:29:17 UTC,Closing as part of bug migration (duplicated in https://gitlab.com/inkscape/inkscape/issues/380)
1711948,2017-11-03 19:56:52 UTC,"Sorry, not understanding your ""fix"" here. I tried the change you note, and restarted x11vnc (server) ... it's still not listening on the defined ports."
1711948,2017-11-03 17:52:54 UTC,UPDATE: I resolved my console only issue by changing /etc/X11/Xwrapper.config from default
1711948,2017-11-03 16:43:36 UTC,"disabled vino and installed x11vnc on artful, and can only login using macos screen sharing app when i already have a xorg session active. if i logout on the console, then can't start a remote session. pwd is set and systemd service is running..."
1711948,2017-10-27 17:26:35 UTC,"It seems that Wayland is not supported by x11vnc（ which user libvncserver）
because Wayland doesn't have a screen capture api for x11vnc to use？"
1711948,2017-12-21 23:09:40 UTC,"I was able to start up x11vnc by disabling Wayland in the /etc/gdm3/custom.conf file and rebooting as per this post: https://askubuntu.com/questions/981313/x11vnc-on-ubuntu-17-10-not-running-on-startup. I'm not sure what I lose by changing the DM, but for now it seems to be OK."
1711948,2017-10-26 08:51:14 UTC,I have the same problem:
1711948,2017-10-24 21:21:13 UTC,"What fixed the issue for me was reverting to ""Ubuntu on Xorg""."
1711948,2017-10-22 17:52:36 UTC,"Arrgh ... OK, was having issues getting the new desktop working. Uninstalled / reinstalled the display manager, moving it from lightdm to gdm3 (the default, right?) => now VNC is broken on the second machine as well ... :-(."
1711948,2017-09-03 07:19:13 UTC,x11vnc not working under  17.10 artful
1711948,2017-10-25 00:14:43 UTC,"Hmmm ... you mean you logged in with that Window Manager? I can't even connect to the machine any more - and checking it locally, the same issue here ... it's not even listening on the port any more."
1711948,2017-10-22 15:46:18 UTC,"Hi,"
1711948,2017-09-26 20:17:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711954,2018-09-14 16:30:53 UTC,"This can be closed, as the current HWE kernel is version 4.15.
Operating temperature is back to normal but disk I/O performance is awful on laptops."
1711957,2017-08-20 21:40:09 UTC,"StacktraceTop:
 g_vfs_monitor_emit_event (monitor=monitor@entry=0x0, event_type=event_type@entry=G_FILE_MONITOR_EVENT_ATTRIBUTE_CHANGED, file_path=0xe135f33a40 ""1e8717540d9b2fcd0db5283d5994b457"", other_file_path=other_file_path@entry=0x0) at gvfsmonitor.c:357
 reload_recent_items (backend=<optimized out>) at gvfsbackendrecent.c:566
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=0x7ffc10a761b0) at ../src/x86/ffi64.c:525
 g_value_set_enum (value=<optimized out>, v_enum=<optimized out>) at ../../../../gobject/genums.c:710"
1711957,2017-10-11 09:31:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1711969,2019-08-21 03:29:48 UTC,I think i also see this when attempting to delete a container using chrome.
1711969,2017-08-21 04:34:12 UTC,Seems Safari also fails.
1712001,2017-08-21 06:43:27 UTC,Please check the checksums of Downloaded ISO file. The checksums are as follows:
1712001,2017-08-21 13:54:53 UTC,"I used these commands (screenshot of CMD) to verify checksums of beta file,
I downloaded that file from sourceforge."
1712001,2017-08-21 14:35:44 UTC,Check if it boots on real hardware
1712008,2017-08-23 16:19:02 UTC,"Reviewed:  https://review.openstack.org/496725
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c12446ecabd5987f0a3a9184691a1e42352e3070
Submitter: Jenkins
Branch:    stable/pike"
1712008,2017-08-23 17:42:31 UTC,"Reviewed:  https://review.openstack.org/496727
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7f282839911222223652245b2dd12ca26d42a9d3
Submitter: Jenkins
Branch:    stable/pike"
1712008,2017-08-23 18:06:20 UTC,"Reviewed:  https://review.openstack.org/496729
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b37411c1e3d167156b6e54f837fc291c9e61eeef
Submitter: Jenkins
Branch:    stable/pike"
1712008,2017-08-25 03:51:02 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc2 release candidate.
1712008,2017-09-06 23:59:11 UTC,"Reviewed:  https://review.openstack.org/501314
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=02a82c41f90a64f261d81cdc0bc57471d15a7c8e
Submitter: Jenkins
Branch:    master"
1712008,2017-09-06 21:56:00 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/501477"
1712008,2017-10-24 12:43:51 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712008,2017-09-15 22:21:56 UTC,"Reviewed:  https://review.openstack.org/501477
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7d220b3dd7f9a52773604eab8160503b05f586b3
Submitter: Jenkins
Branch:    stable/pike"
1712008,2017-09-06 15:30:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/501314"
1712008,2017-08-23 15:19:37 UTC,"Reviewed:  https://review.openstack.org/496419
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8fc789deb7c774bcc5b5128d638c6c7e30bf0a54
Submitter: Jenkins
Branch:    master"
1712008,2017-08-23 14:30:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/496729"
1712008,2017-08-23 14:29:48 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/496727"
1712008,2017-08-23 14:29:22 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/496725"
1712008,2017-08-22 20:58:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496419"
1712008,2017-08-22 14:13:09 UTC,"Reviewed:  https://review.openstack.org/495170
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=52d732d6bdb78ca5c940112e8dff6eef7f6828e8
Submitter: Jenkins
Branch:    master"
1712008,2017-08-21 22:39:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496031"
1712008,2017-08-21 19:33:17 UTC,"Semi-related but another problem here is when forcing a host during live migration, we don't check that the source and destination hosts are within the same cell if you're running a multi-cell deployment with cells v2."
1712008,2017-08-21 19:13:30 UTC,"After discussing this with Dan Smith a bit in IRC, solution #2 in comment 1 isn't great either since it would mean duplicating more of the allocation logic in multiple places, which is something we're already having to deal with between the compute service and the scheduler service right now, so we really want the scheduler to be responsible for this, so we should do something where conductor calls select_destinations with a target host and just make it do the claim, and I guess run the filters?"
1712008,2017-08-21 19:07:31 UTC,The problem is here:
1712008,2017-08-23 14:57:55 UTC,"Reviewed:  https://review.openstack.org/496031
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5d3a11b9c9a6a5aecd46ad7ecc635215184d930e
Submitter: Jenkins
Branch:    master"
1712021,2017-08-28 03:01:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712027,2021-01-09 04:17:51 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1712027,2017-08-24 10:08:39 UTC,"If the alg is GCRY_CIPHER_AES256 and length of data to be encrypted is multiple of 16 (16/32/48...),the length of encryted data is equal to the raw data. There is no padding and the bug is triggerd."
1712027,2020-11-09 18:29:51 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1712028,2020-11-09 08:50:54 UTC,"Hello,
do you still seeing this issue with the latest kernel?
Thanks."
1712028,2021-01-09 04:17:34 UTC,[Expired for linux-hwe-edge (Ubuntu) because there has been no activity for 60 days.]
1712032,2018-03-15 15:40:29 UTC,"Reviewed:  https://review.openstack.org/496481
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=aef133ab893baa6ce68bce8a5cfe3e3898d2826e
Submitter: Zuul
Branch:    master"
1712032,2018-04-18 10:59:55 UTC,"Reviewed:  https://review.openstack.org/528609
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=c7e938cd57ac53ba2aa578c76e1f5d67c071a9b4
Submitter: Zuul
Branch:    master"
1712032,2018-05-30 04:47:41 UTC,"Reviewed:  https://review.openstack.org/512579
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=254d37033172fb06672fc5743d8b05150208ffb7
Submitter: Zuul
Branch:    master"
1712032,2018-03-20 17:51:03 UTC,"Reviewed:  https://review.openstack.org/554406
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=93fd4b1fb4f7c58d20faae206af213e7bb31c671
Submitter: Zuul
Branch:    master"
1712032,2018-03-20 03:02:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554406"
1712032,2017-12-18 03:20:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528609"
1712032,2017-09-27 08:51:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507793"
1712032,2017-10-16 07:54:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/512200"
1712032,2017-10-13 05:45:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511714"
1712032,2017-10-12 07:18:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511402"
1712032,2017-10-11 07:26:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511162"
1712032,2017-08-23 05:11:10 UTC,Proposed spec: https://review.openstack.org/#/c/496481/
1712032,2017-10-17 10:44:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/512579"
1712042,2017-09-22 16:16:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712042,2017-09-22 16:45:05 UTC,"If we enable bottom left hot corner to open ""Show Applications"", then it would be nice if ""Show Applications"" icon remains in the left bottom corner when we set ""Screen position"" to bottom in Settings window.
Currently ""Show Applications"" icons moves to right bottom instead of left bottom corner, but in all popular Desktop environments (KDE, LXDE, Windows, MacOS X, etc) Applications (Start menu) button is in the left bottom corner.
Original Dash to Dock extension has a setting to move the Show Applications icon to the top of the dock, maybe it would be wise to implement this setting in gnome-shell-extension-ubuntu-dock?
See LP bug #1713621 for this feature request."
1712045,2017-10-24 12:43:52 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712045,2017-10-24 11:48:54 UTC,"Reviewed:  https://review.openstack.org/509924
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9ee18e90cca226b5bf90b3b26fbc8e17228f55c
Submitter: Zuul
Branch:    stable/pike"
1712045,2017-10-05 22:22:18 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/509924"
1712045,2017-09-25 15:06:25 UTC,"Reviewed:  https://review.openstack.org/496202
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=633ebd1e9b057f0614961d79391987b51bb5d5a0
Submitter: Jenkins
Branch:    master"
1712045,2017-08-25 03:51:04 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc2 release candidate.
1712045,2017-08-23 18:06:03 UTC,"Reviewed:  https://review.openstack.org/496728
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d041569ad540e9eb57eeaf5b20df4c8bde8b189f
Submitter: Jenkins
Branch:    stable/pike"
1712045,2017-08-23 16:19:29 UTC,"Reviewed:  https://review.openstack.org/496726
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2f967b403ab1225c5ccb39bb52977748ebbd32d
Submitter: Jenkins
Branch:    stable/pike"
1712045,2017-08-23 14:29:34 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/496726"
1712045,2017-08-23 14:30:03 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/496728"
1712045,2017-08-22 14:15:09 UTC,"Reviewed:  https://review.openstack.org/495811
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1ce7a136b362fbfb2d3d231ba8e1cd77081139ce
Submitter: Jenkins
Branch:    master"
1712045,2017-08-22 11:01:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/496202"
1712045,2017-08-21 22:50:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496032"
1712045,2017-08-21 20:31:58 UTC,"To be clear, the bug here is that the allocations are not cleaned up from the source node once the migration is complete."
1712045,2017-08-21 19:56:15 UTC,Looks similar to what was needed for removing the allocations for an instance on the source node in an evacuate operation:
1712045,2017-08-21 10:29:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/495811"
1712045,2017-08-23 15:06:08 UTC,"Reviewed:  https://review.openstack.org/496032
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=72728ed01fe5d568855ad92596740a2da81169c4
Submitter: Jenkins
Branch:    master"
1712057,2017-09-06 09:12:13 UTC,"deploy VM pass through disk/ram/core filters, the limits will be saved in the cache. Since then, deploy VM not through  filters, the limits value in the cache will be used. At this point, the host of aggregate set allocation ratios will not change limits. Only once again through filters to deploy VM, the aggregate's allocation ratios take effect.
I think all versions have this problem."
1712057,2017-08-31 14:04:42 UTC,So the issue is that allocation ratios are changed after things a deployed? What version of the system and openstack?
1712057,2017-08-21 15:56:33 UTC,"Is the RamFilter enabled? If not, that's why the ram_allocation_ratio isn't in the limits passed from the scheduler to the compute. The RamFilter was recently removed from the list of default enable filters:"
1712057,2017-08-22 02:09:11 UTC,"Sorry， I didn't describe it very clearly. For example:
1) Set ram_allocation_ratio=2.0 and create vm_1 pass through all filters. if the host1 is selected, then it's host_state.limits['memory_mb'] = host_state.total_usable_ram_mb * ram_allocation_ratio.
2) Add host1 to aggregate of ag_1 and set ag_1 metadata ""ram_allocation_ratio=2.5"". Then create vm_2 to the host1 not pass through all filters,the memory limits still 2.0*host_state.total_usable_ram_mb, it should be 2.5*host_state.total_usable_ram_mb. when I restart scheduler service, the limits will become None."
1712059,2019-07-18 19:12:41 UTC,Is this a purposeful design principle or a real bug? Its not been looked at in 2 years.
1712059,2019-07-18 19:34:59 UTC,Yeah could be nice to have this implemented.
1712060,2017-08-21 12:03:04 UTC,This problem occurs on ALL versions of Ubuntu 16.04.x
1712068,2017-08-22 14:33:30 UTC,"The command is available in version 3.11.0, not sure when it was introduced. Since your distro doesn't have a new enough version, you may need to install it via pip."
1712069,2018-02-08 18:03:10 UTC,We don't support submodules in most of the rest of the tools for OpenStack so I'm not all that interested in adding support to reno unless someone else wants to write it.
1712069,2018-03-14 14:48:26 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1712071,2018-01-23 08:17:54 UTC,"During ""juju upgrade-juju"" with 100s of machines, that presents a
particularly large memory footprint. They don't even have to be all that
slow, just lots of concurrent requests.
(we should at least only be streaming binaries for machine agents, because
once they copy the binary locally, then the unit agents should just use the
one they find there.)"
1712071,2018-01-23 07:59:41 UTC,When the agent binaries are requested they are read in full into a byte slice and then streamed over HTTP to clients.
1712071,2017-08-21 17:45:44 UTC,"Heap profile doesn't seem to cover all of the memory that I see in Resident memory but doing:
$ for i in `seq 2 5`; do go tool pprof -base heap-0001.pprof -top jujud heap-000$i.pprof >tmp; head -n 10 tmp; done
65564.57kB of 58896.72kB total (  100%)
Dropped 1667 nodes (cum <= 294.48kB)
Showing top 80 nodes out of 156 (cum >= 512.04kB)
      flat  flat%   sum%        cum   cum%
33915.52kB 57.58% 57.58% 33915.52kB 57.58%  github.com/gorilla/websocket.newConn
 8446.65kB 14.34% 71.93%  8446.65kB 14.34%  crypto/tls.(*block).reserve
 4097.62kB  6.96% 78.88%  4097.62kB  6.96%  runtime.malg
 1559.76kB  2.65% 81.53%  2071.79kB  3.52%  github.com/juju/juju/apiserver.(*apiRoot).FindMethod.func1
 1539.94kB  2.61% 84.15%  1539.94kB  2.61%  reflect.unsafe_NewArray
 1536.67kB  2.61% 86.76%  1536.67kB  2.61%  gopkg.in/mgo.v2/bson.(*decoder).readStr
151.11MB of 157.10MB total (96.19%)
Dropped 1739 nodes (cum <= 0.79MB)
Showing top 80 nodes out of 144 (cum >= 25.80MB)
      flat  flat%   sum%        cum   cum%
   80.14MB 51.01% 51.01%    80.14MB 51.01%  github.com/gorilla/websocket.newConn
   18.56MB 11.81% 62.82%    18.56MB 11.81%  crypto/tls.(*block).reserve
    8.50MB  5.41% 68.24%     8.50MB  5.41%  runtime.malg
       6MB  3.82% 72.06%        6MB  3.82%  reflect.mapassign
       4MB  2.55% 74.60%        4MB  2.55%  gopkg.in/mgo.v2/bson.(*decoder).readStr
    3.09MB  1.97% 76.57%    18.11MB 11.52%  gopkg.in/mgo%2ev2.(*mongoSocket).readLoop
258.73MB of 276.24MB total (93.66%)
Dropped 1792 nodes (cum <= 1.38MB)
Showing top 80 nodes out of 120 (cum >= 64.60MB)
      flat  flat%   sum%        cum   cum%
  123.42MB 44.68% 44.68%   123.42MB 44.68%  github.com/gorilla/websocket.newConn
   36.01MB 13.04% 57.71%    36.01MB 13.04%  reflect.mapassign
   20.11MB  7.28% 64.99%    20.11MB  7.28%  crypto/tls.(*block).reserve
   11.50MB  4.16% 69.16%    11.50MB  4.16%  runtime.malg
   10.40MB  3.76% 72.92%    25.96MB  9.40%  gopkg.in/mgo%2ev2.(*mongoSocket).readLoop
    8.50MB  3.08% 76.00%     8.50MB  3.08%  gopkg.in/mgo.v2/bson.(*decoder).readStr
338.51MB of 364.73MB total (92.81%)
Dropped 1824 nodes (cum <= 1.82MB)
Showing top 80 nodes out of 129 (cum >= 4.50MB)
      flat  flat%   sum%        cum   cum%
  160.78MB 44.08% 44.08%   160.78MB 44.08%  github.com/gorilla/websocket.newConn
   39.52MB 10.83% 54.92%    39.52MB 10.83%  reflect.mapassign
   38.98MB 10.69% 65.61%    38.98MB 10.69%  crypto/tls.(*block).reserve
   15.01MB  4.11% 69.72%    15.01MB  4.11%  runtime.malg
   12.50MB  3.43% 73.15%    12.50MB  3.43%  gopkg.in/mgo.v2/bson.(*decoder).readStr
   10.58MB  2.90% 76.05%    10.58MB  2.90%  reflect.unsafe_NewArray"
1712071,2017-08-21 14:24:18 UTC,"I noted that there were several agents in a failed state (presumably because of the oom kill of the original jujud process), so I went through and restarted all agents with:
for i in `seq 0 14`; do juju ssh $i 'for agent in $(cd /var/lib/juju/agents; ls -d *); do echo jujud-$agent; sudo service jujud-$agent restart; done'; time sleep 10; done"
1712071,2017-08-21 14:17:19 UTC,"While adding another 450 units, I do see memory consumption going up significantly (from something like 2GB up to 5.3GB, adding a bunch more units saw memory going up to 5.6GB, and the system again becoming unresponsive.)
Mongo memory consumption stayed around 1.2GB."
1712071,2017-08-21 13:30:21 UTC,"The traceback lists 49010 goroutines active, and has a goroutine counter of ~1,057,000 goroutines."
1712071,2017-08-21 13:13:41 UTC,"(for example, it may be that something hung, preventing us from saving say data to Mongo, but we continued to read and buffer Log messages until we ran out of memory.)"
1712072,2018-03-15 12:57:32 UTC,Also seen on Bionic (gedit 3.28)
1712072,2020-03-09 20:47:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712076,2018-07-20 20:36:32 UTC,This issue was fixed in the openstack/tosca-parser 1.1.0 release.
1712076,2018-06-14 10:23:26 UTC,"Hi Bob,"
1712076,2018-06-04 13:28:20 UTC,Thanks - that would be great.
1712076,2018-06-04 12:20:01 UTC,"Also in the properties of a policy, the get_input is not resolved as it is in the node_templates. I haven't saw anything related to it in the list of bug (I don't know if I missed it somewhere?) should I report a new bug related to this?"
1712076,2018-06-04 11:16:36 UTC,Greg - I have one more patch that I want to land this week and then I'll look at a release.
1712076,2018-06-04 08:47:42 UTC,"Thanks for the changes, and the commit! Do you know when will be the next time that the TOSCA Parser will be updated in the pip repository?"
1712076,2018-06-01 13:56:54 UTC,"Thanks, because I didn't understand why that happened, when I only edited some comments!"
1712076,2018-06-01 09:28:25 UTC,"Okay I've added some comments and amended the commit, should I push it then?"
1712076,2018-06-01 10:35:10 UTC,"Okay, after I amended the commit I did a git review with the Closes-Bug line added. This created a new patch, what should be done now to merge it to the master?"
1712076,2018-05-31 14:54:25 UTC,You can checkout the patch (git fetch https://git.openstack.org/openstack/tosca-parser refs/changes/97/498797/11 && git checkout FETCH_HEAD) and update the commit message with the Closes-Bug: tag as requested by Sahdev.  You can add a Co-Authored-By: with your information so you get credit for assisting with the change.
1712076,2018-05-31 12:18:17 UTC,"Hi,"
1712076,2018-05-31 12:07:35 UTC,The patchset was reviewed and the originator has not responded to the comments.
1712076,2018-05-31 08:13:28 UTC,can we please review this bug and merge it
1712076,2017-08-29 12:58:47 UTC,"raised the code review. https://review.openstack.org/#/c/498797/
Please add the reviewers."
1712076,2017-08-22 13:46:40 UTC,Thanks Manas! Yours now.
1712076,2018-06-01 13:14:55 UTC,"Thanks Gregoire.  The builds failed due to a regression in the tests
that was introduced recently.  I'll add the fix for the regression to
that patchset and see if it builds successfully.  Once the builds pass
we can go ahead and merge it."
1712076,2017-08-22 13:26:22 UTC,Please assign to me I can submit the code fix.
1712088,2017-08-21 14:23:53 UTC,"Forgot to mention, I am on Ubuntu 17.04"
1712089,2017-10-24 13:23:12 UTC,"sudo gedit fstab
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused"
1712089,2017-10-24 13:51:47 UTC,"Re comment #21, according to https://bugzilla.redhat.com/show_bug.cgi?id=1274451"
1712089,2017-10-25 15:54:15 UTC,"ah, the xhost command still works, even though on wayland; I didn't expect that.
executing the below xhost on the command line worked, so I assume the creation of the xhost.desktop file (described below) will indeed do the trick.
thanks!"
1712089,2017-10-26 08:47:11 UTC,"> ah, the xhost command still works, even though on wayland; I didn't expect that.
"
1712089,2017-10-27 22:59:35 UTC,A Complaint: The work-arounds given here no longer function after the recent updates. WTF! How about fixing this requirements-related bug so I can partition my new drive? Barring that give me an Ubuntu-supported path back to 17.04 that doesn't involve my losing all my data.
1712089,2018-01-23 04:46:45 UTC,"@PeterPall, why did you make bug #1551951 a duplicate of this bug? See comments 7 & 8 in bug #1551951 for explanation of why I separated all the Synaptic bugs from this bug in the first place."
1712089,2017-11-14 12:40:24 UTC,Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
1712089,2017-12-30 21:28:42 UTC,answer #2 worked for me. could start synaptic again on Ubuntu 17.10
1712089,2018-02-20 13:00:50 UTC,"""Wayland"" doesn't appear to care how many bugs they have created with their philosophical decision to not allow actions like ""sudo synaptic"" starting a graphical application from the command line.  Is there any rationale??"
1712089,2018-08-05 09:17:29 UTC,"I have a variation of this:   pardon any imprecision here I am NOT an expert sysadmin,  I am a mid-stage learning Linux enthusiast."
1712089,2017-10-23 00:05:21 UTC,Thanks a lot! I've got a script that I run on each login to fix that.
1712089,2017-10-27 23:40:30 UTC,"It's a bug in the individual packages, not Wayland."
1712089,2017-10-22 23:53:10 UTC,"According to https://bugzilla.redhat.com/show_bug.cgi?id=1274451 there are no plans for Wayland to support running graphical applications as root so that bug has been closed as WONTFIX. The correct fix is for Synaptic, and other graphical apps needing root, to be rewritten to run the GUI as a normal user and to use ""polkit"" for the parts where they need root access."
1712089,2018-01-03 02:25:42 UTC,Answer #2 works but needs to be used prior to any attempt to use gui for gedit.
1712089,2017-10-06 10:34:02 UTC,Affects Bleachbit too. Ubuntu 11.10 vanilla gnome-session.
1712089,2017-08-21 14:40:37 UTC,Workaround typed into a terminal:   xhost +si:localuser:root
1712089,2017-08-21 14:50:35 UTC,Thanks for your report.
1712089,2017-08-22 11:34:42 UTC,Annoying -- the developers over at Fedora seem to suggest that there is an unwillingness to provide support for any GUI that runs as root. Surely a problem for many admin tools like this?
1712089,2017-08-22 11:55:29 UTC,"Discussed on Debian mailing list:
https://<email address hidden>/msg1541135.html"
1712089,2017-08-22 12:06:43 UTC,@John
1712089,2017-08-26 21:52:00 UTC,"cat <<EOF | sudo tee /etc/xdg/autostart/xhost.desktop
[Desktop Entry]
Name=xhost
Comment=Fix graphical root applications
Exec=""xhost +si:localuser:root""
Terminal=false
Type=Application
EOF"
1712089,2017-08-27 10:40:21 UTC,Just installed Artful x86 on USB-flash.
1712089,2017-10-07 11:08:00 UTC,"Got this warning message on ""dpkg-reconfigure keyboard-configuration"":"
1712089,2017-08-30 09:47:44 UTC,"In artful the problem seems no more be limited to wayland, but to extend to all kinds of gnome session."
1712089,2017-09-01 14:28:03 UTC,"@PeterPall (peterpall)
The full list of pkexec'ed applications is located in bug 1713313. It is long."
1712089,2017-09-16 01:57:39 UTC,Debian report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872553
1712089,2017-09-29 11:56:53 UTC,"Ubuntu 17.10 with all updates, bug is not fixed. Still can't use Synaptic on Wayland."
1712089,2017-10-06 07:07:27 UTC,"Ubuntu 17.10 beta installed on 6.10.2017:
Still the same problem, not only with synaptic but also octave wouldn't work properly, gave similar error."
1712089,2017-10-06 10:16:19 UTC,"@matej
please describe when and why GNU Octave needs root access.
You can post answer here, or mark bug 1713313 as affecting Octave package (use ""Also affects distribution/package"" link) with corresponding comment."
1712089,2017-08-27 13:27:25 UTC,Just installed Artful x86 on USB-flash.
1712091,2017-10-16 04:34:10 UTC,Need to understand why provider network configuration is used here. Contrail is currently supporting this only for SRIOV and has to change to make it neutron compatible.
1712096,2019-09-19 11:53:39 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1712105,2017-09-16 20:23:05 UTC,"What Marcello wants (and I also see it would be nice) is clicking on the map and getting not only long/lat but also the correct timezone. This would require a polygon lookup (inside/outside testing) with a set of timezone-describing polygons, which we however do not have. (And they are frequently changing!)"
1712105,2017-08-24 09:36:52 UTC,Please write detailed description or explanation what exactly you want to see or where is the problem.
1712105,2018-09-26 06:06:59 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/433
1712105,2017-08-23 06:05:31 UTC,Selecting a stored location will set correct time zone. Clicking on the map enables only local mean time. Setting time zone in addition should not be too difficult.
1712105,2017-08-21 15:58:57 UTC,0.11? But version 0.11 is doesn't know about time zones. 0.90.0.9767 changed time zones when location are changes.
1712105,2017-08-24 09:17:26 UTC,"Thank you for the answer.
It's too long to explain why I got into thinking that a version that is not the 0.90 was automatically adapting the time zone to the chosen location. I was mistaken."
1712105,2017-08-21 19:46:13 UTC,Sorry about that. The version that I know such feature is working is 0.16.0 (the latest one on http://www.stellarium.org/)
1712114,2017-08-21 19:53:28 UTC,"- could you attach the 0.91 file you are importing, for testing purposes?
- sounds a bit similar to https://bugs.launchpad.net/inkscape/+bug/1671059"
1712114,2017-08-21 20:28:15 UTC,sure. see attached.
1712114,2017-08-21 23:17:39 UTC,"thanks for the file.
I believe this is a duplicate of Bug 1671059
The problem is caused by the fact that the old document has no viewbox.
see https://bugs.launchpad.net/inkscape/+bug/1671059/comments/6
and https://bugs.launchpad.net/inkscape/+bug/1671059/comments/8"
1712122,2017-08-22 03:19:39 UTC,It gets worse. The terminals may open when you're pressing nothing: bug 1707828 :)
1712122,2018-08-08 07:45:47 UTC,This sounds like something Andrea is working on already...
1712122,2019-03-08 10:05:33 UTC,This has already been fixed upstream.
1712122,2019-03-11 01:46:57 UTC,Yeah I thought so. Can you point to where?
1712122,2020-03-19 10:18:02 UTC,Fix Released some time ago I assume.
1712179,2017-08-21 22:39:20 UTC,"Andreas, can you document your conclusion from IRC in the bug when unassigning yourself?"
1712179,2017-08-22 12:35:25 UTC,"Definitely, sorry I missed it."
1712181,2018-08-12 22:41:40 UTC,"Manually removed
sudo apt-get remove libobs0"
1712181,2017-11-23 21:38:57 UTC,"I have that exact issue on my Laptop, Ubuntu Unity 17.04 Kernel: 4.14.0-041400-generic
Please let me know if you need more information from my side."
1712181,2017-08-22 17:57:25 UTC,"I'm having this same exact issue on my end. Ubuntu Gnome 17.04, AMD Ryzen 5. Let me know if you need more information from my side."
1712181,2017-08-22 17:57:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712200,2017-10-21 13:11:27 UTC,apport information
1712200,2017-10-21 13:11:28 UTC,apport information
1712200,2017-10-21 13:11:29 UTC,apport information
1712200,2017-10-21 13:11:30 UTC,apport information
1712200,2018-01-03 11:06:20 UTC,"Is the bug fixed? Luckly it isn't reproduced anymore on my machine (Ubuntu 17.10, Firefox 57.0.3)."
1712200,2017-10-21 13:11:32 UTC,apport information
1712200,2017-10-21 13:11:34 UTC,apport information
1712200,2017-10-21 13:11:25 UTC,apport information
1712200,2018-06-11 20:33:00 UTC,The bug happens again on Ubuntu 18.04
1712200,2017-10-21 13:11:31 UTC,apport information
1712200,2017-10-21 13:11:24 UTC,apport information
1712200,2017-10-21 13:11:18 UTC,apport information
1712200,2017-10-21 13:11:21 UTC,apport information
1712200,2017-10-21 13:11:20 UTC,apport information
1712200,2017-10-21 13:11:16 UTC,apport information
1712200,2017-10-21 13:11:15 UTC,apport information
1712200,2017-10-21 13:11:14 UTC,"AddonCompatCheckDisabled: False
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  artful64   1468 F.... pulseaudio
BuildID: 20171003222101
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.10 ""Artful Aardvark"" - Release amd64 (20171018)
IpRoute:
 default via 192.168.3.1 dev wlp2s0 proto static metric 600
 169.254.0.0/16 dev wlp2s0 scope link metric 1000
 192.168.3.0/24 dev wlp2s0 proto kernel scope link src 192.168.3.15 metric 600
Locales: extensions.sqlite corrupt or missing
Package: firefox 56.0+build6-0ubuntu1
PackageArchitecture: amd64
PrefSources: prefs.js
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
RunningIncompatibleAddons: False
Tags:  wayland-session artful
Themes: extensions.sqlite corrupt or missing
Uname: Linux 4.13.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC."
1712200,2017-10-21 13:02:55 UTC,I have just made a clean installation of Ubuntu.
1712200,2017-10-17 16:47:07 UTC,"No, we definitely don't want to set ui.key.menuAccessKeyFocuses to false since that's how you get the full traditional File/Edit/View/etc. menu."
1712200,2017-10-06 21:59:42 UTC,The bug still exists after upgrade of Firefox to version 56.0.
1712200,2017-09-29 11:27:17 UTC,Same with Firefox 55.0.2.
1712200,2017-09-29 10:36:50 UTC,"Got this bug with Firefox 50.1.0 on Ubuntu Artful x86 with ""ubuntu on wayland"" session."
1712200,2017-09-26 08:24:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712200,2017-10-21 13:11:22 UTC,apport information
1712211,2017-08-21 22:58:52 UTC,"Oh, I spoke too soon: the old rpi1 firmware gives the correct mac address but seems to break when trying to setup a PAN/NAP connection. It just hangs and doesn't give any hints in terms of logs. The new firmware goes through the NAP setup but breaks because the MAC address is invalid."
1712211,2017-08-22 18:53:08 UTC,I've submitted this issue to raspberrypi/firmware as well:
1712211,2017-08-23 18:12:06 UTC,Per the github issue there's a work around with an updated btuart script. It would be good to get that packaged in raspbian.
1712211,2017-08-30 21:54:30 UTC,Looks like this was fixed in pi-bluetooth 0.1.6. Thanks!
1712212,2017-08-21 22:07:50 UTC,Full listing of apt-get install logs:
1712212,2018-01-18 08:29:09 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2000
1712218,2017-08-23 03:53:02 UTC,I guess it works on Zesty?
1712218,2017-08-22 20:25:44 UTC,"@kaihengfeng, which kernel would that be? In grub I only see (taken from  ""dpkg --list | grep linux-image | grep ii""):
  - linux-image-4.12.0-11-generic
  - linux-image-4.13.0-041300rc6-generic"
1712218,2017-08-22 03:32:11 UTC,Does it work on Zesty kernel? You can still pick old kernel in GRUB menu.
1712218,2017-08-22 00:32:32 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1712218,2017-08-22 02:21:10 UTC,I installed the requested kernel[0] and the issue still remains[1]. Tagging as requested.
1712218,2017-08-22 00:00:07 UTC,This change was made by a bot.
1712220,2017-08-22 02:20:29 UTC,I installed the requested kernel[0] and the issue still renames. Tagging as requested.
1712220,2017-09-01 18:32:06 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1712220,2017-08-22 00:00:15 UTC,This change was made by a bot.
1712220,2017-08-22 00:32:55 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1712223,2017-08-22 00:16:53 UTC,additional information about when one doesn't hold the package back (note the error from VMWare Workstation 12.5).
1712223,2017-08-23 07:57:51 UTC,Thanks for your report.
1712223,2017-08-23 17:38:11 UTC,I can confirm that using X11 as you suggested instead of Wayland is a viable workaround and that both multi-monitor support and resolution re-scaling work when moving VMWare Workstation around.
1712223,2017-08-23 17:59:04 UTC,Thank you for confirming it is an issue specific to wayland. I'm retargeting the bug report.
1712228,2017-08-28 13:05:12 UTC,"Greetings, I suspect this is a wishlist item, although it sounds like the hardware you are using is somehow defaulting to the second com port being for serial console access, where as most devices tend to use the first serial port. Is this something that was configured in the hardware? Is it a hardware default?"
1712228,2017-09-20 06:14:33 UTC,"Hi Julia, the second com port support SOL and can work with shellinabox, but the first com doesn't work with shellinabox. so I think it is better to modify the user operating system configration during deploying."
1712228,2017-09-20 06:49:39 UTC,"If you are using local boot, I am afraid the only way is modifying user image.
If you are using netboot, I have an impression there is an unfinished spec to support adding command line to node, kernel params can be passed to instance image, but I can't remember the link."
1712228,2017-09-20 07:38:30 UTC,"Hi KaiFeng, you are right. What you said spec maybe is this: https://bugs.launchpad.net/ironic/+bug/1526766.  In fact，it is better to insert the parameter into user instance no matter local boot or netboot. But as a temporary solution，I will modify the user image. I am not sure this spec will be finished soon."
1712230,2017-09-05 04:07:28 UTC,"Just for tracking the info and discussion on https://review.openstack.org/#/c/491663/:-
I too checked, the issue is only with --tls-disabled.
With tls-disabled --apiserver-host argument need to be passed, me neither know about auto discover, attaching kubectl log for dashboard with apiserver-host and without apiserver-host:-"
1712230,2019-08-25 20:06:51 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.opendev.org/494770
Reason: https://docs.openstack.org/doc-contrib-guide/writing-style/code-conventions.html"
1712231,2018-03-10 18:40:01 UTC,Won't fix on R5.0 (mainline) due to micro-services architecture.
1712231,2017-10-30 01:33:59 UTC,"Reviewed:  https://review.opencontrail.org/36967
Committed: http://github.com/Juniper/contrail-ansible-internal/commit/ee3558bbd8eef265a6a6732c6392f1a5dbfb93fd
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1712231,2017-10-30 01:33:51 UTC,"Reviewed:  https://review.opencontrail.org/36966
Committed: http://github.com/Juniper/contrail-packages/commit/766e611fbe8b27bd7aadf41b2d5c7772c1fb5088
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1712231,2017-10-30 01:33:19 UTC,"Reviewed:  https://review.opencontrail.org/36965
Committed: http://github.com/Juniper/contrail-ansible/commit/4c3e263435b663edfcb805554786702346335788
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1712231,2017-10-29 14:17:35 UTC,"Review in progress for https://review.opencontrail.org/36967
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1712231,2017-09-12 19:01:51 UTC,"Reviewed:  https://review.opencontrail.org/35497
Committed: http://github.com/Juniper/contrail-ansible/commit/09b4701e5c7224773cc8f4bf5fce1c4eda111d84
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1712231,2017-09-12 00:51:05 UTC,"Review in progress for https://review.opencontrail.org/35497
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1712231,2017-08-23 21:54:23 UTC,"Review in progress for https://review.opencontrail.org/34856
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1712231,2017-10-29 14:17:00 UTC,"Review in progress for https://review.opencontrail.org/36966
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1712231,2017-08-24 16:38:13 UTC,"Reviewed:  https://review.opencontrail.org/34856
Committed: http://github.com/Juniper/contrail-packages/commit/f63ceddea11df550a9b32d035d00a71c1eb0c22b
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1712231,2017-08-24 13:45:56 UTC,"Reviewed:  https://review.opencontrail.org/34857
Committed: http://github.com/Juniper/contrail-ansible-internal/commit/76ef9dc8a77f3c2e7a6824175e6cd88cee73b775
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1712231,2017-08-23 22:00:07 UTC,"Review in progress for https://review.opencontrail.org/34857
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1712240,2017-08-24 12:37:45 UTC,Thank you for the report.
1712240,2017-08-26 06:10:54 UTC,This is the same bug (with repro steps):
1712240,2017-08-28 04:04:21 UTC,"Hi Sveta Smirnova (svetasmirnova),"
1712240,2017-08-30 03:23:56 UTC,"Hi Kenn Takara (kenn-takara),"
1712240,2017-09-28 15:01:24 UTC,I have exactly the same problem.
1712240,2018-01-25 09:34:20 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3734
1712243,2017-08-22 23:55:55 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1712243,2017-08-23 00:00:08 UTC,This change was made by a bot.
1712253,2019-01-23 23:33:07 UTC,This still occurs with glibc 2.27-3ubuntu1 from Ubuntu 18.04.1 LTS x64.
1712255,2017-08-24 03:35:48 UTC,"In rally, method enforce_type only exists in release notes, so it is not a bug in rally:
doc/release_notes/archive/v0.2.0.rst
149 * #1517839: Make CONF.set_override with parameter enforce_type=True by default"
1712255,2017-08-25 14:15:49 UTC,@maxinjian: thanks for checking
1712255,2017-08-30 13:15:17 UTC,The networking-dpm fix has merged: https://review.openstack.org/#/c/497104/
1712255,2017-09-08 08:21:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501989"
1712255,2017-09-08 08:27:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501990"
1712255,2017-09-15 01:04:38 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/501990"
1712255,2018-05-09 16:05:09 UTC,It looks like the only remaining reference to this is in poppy: https://review.openstack.org/#/c/501989
1712269,2017-08-29 00:19:35 UTC,Coresponding juju-gui issue filed - https://github.com/juju/juju-gui/issues/3175
1712269,2017-08-29 06:05:04 UTC,"Actually, the issue linked above was closed as team will address it as part of https://github.com/juju/juju-gui/issues/3067"
1712269,2017-08-29 07:07:48 UTC,"This seems to be more of a bug in the GUI, if it needs changes to juju itself, we can reopen this."
1712280,2017-08-22 09:52:43 UTC,I reproduced this like:
1712280,2018-01-25 22:43:05 UTC,"Reviewed:  https://review.openstack.org/523137
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=6a27419521bae9cf6b0ca033d04ef268abebe1bd
Submitter: Zuul
Branch:    stable/pike"
1712280,2017-12-11 21:48:50 UTC,This issue was fixed in the openstack/heat 9.0.2 release.
1712280,2017-12-07 14:38:04 UTC,This issue was fixed in the openstack/heat 10.0.0.0b2 development milestone.
1712280,2017-11-27 14:44:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/523137"
1712280,2017-11-23 13:47:39 UTC,"Reviewed:  https://review.openstack.org/507249
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=af0feeb18a4f5fb2c20fffb6d85617d1775e5844
Submitter: Zuul
Branch:    master"
1712280,2017-11-01 12:35:31 UTC,"Reviewed:  https://review.openstack.org/515454
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=31175a5641035abeec58c3f135ad09d3f231ac41
Submitter: Zuul
Branch:    stable/pike"
1712280,2018-01-26 15:36:38 UTC,I think this can be closed in TripleO now that all of the patches are in Heat?
1712280,2017-10-26 14:49:03 UTC,"Reviewed:  https://review.openstack.org/506678
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=4f4932c7900ae0e88e9a44f06b952c882474729e
Submitter: Zuul
Branch:    master"
1712280,2017-09-27 09:28:13 UTC,"Change abandoned by Steven Hardy (<email address hidden>) on branch: master
Review: https://review.openstack.org/496196
Reason: https://review.openstack.org/#/c/506678/ is the preferred alternative"
1712280,2017-09-25 19:41:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507249"
1712280,2017-09-22 14:46:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506678"
1712280,2017-08-22 10:37:14 UTC,I pushed a WIP patch to heat showing how we might do (2)
1712280,2017-08-22 10:35:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496196"
1712280,2017-08-22 10:12:57 UTC,My vote goes for the #1
1712280,2017-10-26 15:50:18 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515454"
1712280,2017-08-22 09:57:10 UTC,"My previous comment was truncated, I think we probably need two changes:"
1712282,2017-08-22 07:58:32 UTC,"we notice that ""openstack image show"" also failed, maybe from same reason."
1712283,2017-10-21 04:47:56 UTC,livecd-rootfs fixed in version 2.468:
1712283,2017-10-21 04:51:10 UTC,network-manager is also fixed:
1712283,2017-10-21 05:00:21 UTC,netcfg is also fixed.
1712283,2017-10-21 08:06:28 UTC,@vorlon
1712283,2017-10-21 08:32:34 UTC,Were you not using resolvconf on this system prior to upgrade?  NetworkManager should only have managed /etc/resolv.conf contents if it did not detect that another system was managing it (resolvconf or resolved).
1712283,2017-10-22 14:45:23 UTC,@vorlon
1712283,2017-10-21 20:51:39 UTC,"On Sat, Oct 21, 2017 at 08:54:03AM -0000, diabloneo wrote:

> No, I wasn't using resolvconf.
"
1712283,2017-10-21 21:28:37 UTC,"On 21 October 2017 at 21:51, Steve Langasek
<email address hidden> wrote:

> On Sat, Oct 21, 2017 at 08:54:03AM -0000, diabloneo wrote:
>> No, I wasn't using resolvconf.
>
> Ok, is there any particular reason for that?  The resolvconf package is part
> of ubuntu-minimal in Ubuntu 17.04.  Removal of ubuntu-minimal leaves you
> with an unsupported configuration.
"
1712283,2017-10-22 20:54:23 UTC,@diabloneo
1712283,2017-10-22 20:55:06 UTC,"Actually, since you have already used the method from comment #6 to point /etc/resolv.conf directly at resolved instead of at resolvconf, this is also fine."
1712283,2017-10-23 03:11:27 UTC,"@vorlon thank you for your well explaination. My system was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10, I'm not sure  how it became that in 17.04."
1712283,2017-10-21 08:54:03 UTC,"No, I wasn't using resolvconf."
1712283,2017-10-21 04:39:31 UTC,"So how was /etc/resolv.conf configured before you removed it?  To my understanding, there should be no problems after upgrade from any of the default configurations in 17.04."
1712283,2017-09-27 15:43:10 UTC,@prefec2 that sounds like a different bug. This one is not intermittent.  If the workaround in comment #6 does not fix it for you then I suggest filing a new bug.
1712283,2017-09-27 15:24:56 UTC,"I have the same issue. A couple of month ago we had a similar issue, which could be fixed by ""downgrading"" the resolver setup for systemd. However, the issue returned a couple of days ago.
In general networking works after start up, but stops after a random time period. When I ""turn off"" the connection and then turn it on again, it works again for some time before it breaks down again."
1712283,2017-10-21 03:05:55 UTC,"I just upgraded from 17.04 to release version of 17.10, then I encounter this problem, too. comment #6's method fixed this issue for me."
1712283,2017-08-22 09:33:54 UTC,Confirmed with Ubuntu same build number.
1712283,2017-08-22 09:43:10 UTC,manifests diff between 20 and 21. resolvconf is gone from 20170821.
1712283,2017-08-22 14:46:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712283,2017-08-23 09:07:27 UTC,I can confirm that for me removing /etc/resolv.conf and replacing it with a link to stub-resolv.conf using
1712283,2017-08-25 02:54:19 UTC,This bug was fixed in the package systemd - 234-2ubuntu9
1712283,2017-08-29 20:16:17 UTC,"Started working for me about yesterday, but then dropped again.
I use .domain vpn and no .domain get resolved by the system.
It was ok about a week ago, then not working, working for a day, then again - none."
1712283,2017-08-28 16:55:43 UTC,"On Mon, Aug 28, 2017 at 01:47:23AM -0000, Jarod wrote:

> update to systemd (234-2ubuntu9) doesn't help, after reboot I still need
> manually add nameserver to /etc/resolve.conf
"
1712283,2017-08-29 05:45:14 UTC,"jarod@ubuntu-pc:~$ ll /etc/resolv.conf
-rw-r--r-- 1 root root 78 Aug 28 09:38 /etc/resolv.conf"
1712283,2017-08-29 20:13:28 UTC,"● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2017-08-29 22:12:30 CEST; 36s ago
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
  Process: 3497 ExecStartPre=/bin/sh -c [ ! -s /etc/resolv.conf ] && ln -snf ../run/systemd/resolve/stub-resolv.conf (code=exited, status=1/FAILURE)
 Main PID: 3498 (systemd-resolve)
   Status: ""Processing requests...""
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-resolved.service
           └─3498 /lib/systemd/systemd-resolved"
1712283,2017-09-25 08:08:16 UTC,"Today, I also ran into this issue. Wifi was working and I could successfully ping Google's DNS 8.8.8.8."
1712283,2017-08-28 01:47:23 UTC,"update to systemd (234-2ubuntu9) doesn't help, after reboot I still need manually add nameserver to /etc/resolve.conf"
1712283,2017-09-25 08:10:20 UTC,"Forgot to mention, I have a fresh install from the daily artful image on 21st of September 2017."
1712285,2017-09-26 05:04:52 UTC,Fixed in subsequent builds.
1712288,2017-08-22 23:44:13 UTC,"Hi,"
1712288,2017-08-22 21:16:28 UTC,"Hi Mikhail, I like it."
1712297,2017-08-29 00:23:37 UTC,"I agree, we should at least log the failure message as received from the cloud provider."
1712297,2017-08-22 12:25:10 UTC,This is juju 2.2.2 by the way.
1712301,2017-12-03 17:12:18 UTC,Fix landed here: https://code.launchpad.net/~kissiel/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/333607
1712301,2019-04-25 08:56:13 UTC,# reopen this issue based on https://docs.google.com/document/d/1Cj-HMAnY-W1uwoYIgTW36aFz3fIbQzVzjKpLktIt9Is/edit#heading=h.4lu4w12akx1h
1712301,2019-04-25 09:08:41 UTC,"Discussion on irc, the effective operations that checkbox should carry out are:"
1712301,2019-04-25 08:55:25 UTC,"The fix was only fixed dual graphic auto switch, OEM projects need a suspend_30_cycles_with_reboots/logs for dual graphic like"
1712308,2017-08-22 10:31:09 UTC,"StacktraceTop:
 stpcpy () at /usr/include/x86_64-linux-gnu/bits/string3.h:117
 sd_device_new_from_subsystem_sysname (ret=ret@entry=0xb26a042e78, subsystem=<optimized out>, subsystem@entry=0x7ffd0ea40060 ""pci"", sysname=0x7ffd0ea40064 ""0000:00:1c.5"") at ../src/libsystemd/sd-device/sd-device.c:319
 sd_device_new_from_device_id (ret=0xb26a042e78, id=<optimized out>) at ../src/libsystemd/sd-device/sd-device.c:675
 udev_device_new_from_device_id (udev=<optimized out>, id=0xb26a03274f ""+pci:0000:00:1c.5"") at ../src/libudev/libudev-device.c:328
 dev_kmsg_record (l=<optimized out>, p=<optimized out>, s=0x7ffd0ea43b20) at ../src/journal/journald-kmsg.c:229"
1712312,2017-12-08 15:18:35 UTC,The shadow package needs to grow support for extrausers group handling.
1712316,2017-08-22 11:10:21 UTC,"StacktraceTop:
 v8::base::NoBarrier_Load (ptr=0x2dd30e4fb5e8) at ../deps/v8/src/base/atomicops_internals_x86_gcc.h:236
 v8::internal::HeapObject::map_word (this=0x2dd30e4fb5e9) at ../deps/v8/src/objects-inl.h:1445
 v8::internal::HeapObject::map (this=0x2dd30e4fb5e9) at ../deps/v8/src/objects-inl.h:1402
 v8::internal::Object::IsOddball (this=<optimized out>) at ../deps/v8/src/objects-inl.h:836
 v8::internal::Object::IsUndefined (this=<optimized out>) at ../deps/v8/src/objects-inl.h:1077"
1712338,2017-08-29 00:25:20 UTC,"At the same time as addressing this bug, we should also ensure that we log clearly any secgroup manipulation failures as per bug # 1712297."
1712340,2017-11-27 13:16:00 UTC,Duplicate of bug #170356.
1712340,2017-11-27 13:22:44 UTC,"Correction: Inkscape actually *should* support the shape rendering option, see
https://bugs.launchpad.net/inkscape/+bug/170356/comments/21
and the relevant commit
https://gitlab.com/inkscape/inkscape/commit/32ef25632164e5af8766a5364400b579edde4ebf"
1712345,2017-08-22 14:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1712345,2017-09-01 08:26:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1712345,2017-09-01 08:27:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1712345,2017-09-01 08:28:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1712345,2017-09-11 15:21:59 UTC,This bug was fixed in the package linux - 4.12.0-13.14
1712345,2017-09-18 09:21:44 UTC,This bug was fixed in the package linux - 4.10.0-35.39
1712345,2017-09-18 10:11:08 UTC,This bug was fixed in the package linux - 4.4.0-96.119
1712345,2017-09-18 12:57:24 UTC,This bug was fixed in the package linux - 3.13.0-132.181
1712345,2017-10-17 14:53:08 UTC,"This bug was nominated against a series that is no longer supported, ie vivid.  The bug task representing the vivid nomination is being closed as Won't Fix."
1712351,2019-06-09 13:24:10 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape/issues/300
1712352,2019-01-24 20:12:09 UTC,"Reopening.  after: doesnt address this adequately.  I had two potential uses in mind just now, the first of which IS answered by after: and that's the case of test teardown where you might do something like this:"
1712352,2018-09-21 07:02:59 UTC,Use after: instead of depends:
1712352,2017-09-11 19:44:18 UTC,"That's a nice/interesting idea and could open a lot of possibilities like only grabbing logs if a job fails, or perhaps something like this:"
1712352,2017-09-11 19:05:39 UTC,Current approach to define that kind of relationship is:
1712358,2017-09-05 14:03:44 UTC,"Hello,
Rewriting the aforementioned part of swiftclient into
        #scheme = urlparse(url).scheme
        #netloc = urlparse(url).netloc
        #url = scheme + '://' + netloc + '/info'
        parts = url.split(""/"")
        parts[-1] = ""info""
        url = ""/"".join(parts)
and it works like a charm now."
1712358,2017-09-05 15:17:08 UTC,"Change abandoned by Daniel Čech (<email address hidden>) on branch: master
Review: https://review.openstack.org/500875
Reason: wrong update"
1712358,2020-04-25 02:07:24 UTC,"Reviewed:  https://review.opendev.org/722395
Committed: https://git.openstack.org/cgit/openstack/python-swiftclient/commit/?id=947c09f30c6b603e3f4da060bc913407b158a0ca
Submitter: Zuul
Branch:    master"
1712358,2020-04-29 08:13:34 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/724247"
1712358,2020-04-29 19:08:16 UTC,"Reviewed:  https://review.opendev.org/724247
Committed: https://git.openstack.org/cgit/openstack/python-swiftclient/commit/?id=e1c05cffbe980807f170731028ca1a007fcc6f10
Submitter: Zuul
Branch:    stable/ussuri"
1712358,2020-11-05 09:27:59 UTC,Will this ever be included in an actual ussuri release? I can see it is included in 3.10.x but those are victoria packages..
1712358,2020-11-06 20:33:51 UTC,This will be fixed this in Ubuntu via https://bugs.launchpad.net/bugs/1902944.
1712363,2018-06-05 15:16:27 UTC,"No users have been asking for this, probably applies to all output record types."
1712366,2017-08-22 14:52:41 UTC,extra non-findings:
1712366,2017-08-23 19:17:04 UTC,"Since I reported this, the Ubuntu Appindicators extension has turned up. If I enable that, and not TopIcons Plus, and log in using the Ubuntu desktop session rather than the Gnome one, the QT tray icons now show up. This appears to apply both in Xorg and Wayland. This is clearly The Future, given the planned demise of the legacy system tray, so I'm OK for this bug to be closed."
1712381,2019-03-05 18:34:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641103"
1712381,2017-12-01 11:39:34 UTC,This also impacts the end_lease event if the user has been disabled or deleted in the meantime.
1712381,2017-08-22 15:50:45 UTC,"This is because Blazar tries to use the trust created for the user, which is not valid anymore. Blazar should allow admins to bypass trusts and perform the operations with their own context."
1712381,2017-08-22 20:49:16 UTC,"It seems to bother a former user's coworkers within a project most of all, who would ordinarily be able to delete the lease."
1712384,2017-08-22 16:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1712384,2017-08-22 16:15:42 UTC,"I'm sorry, the 'apport-collect 1712384' command does not work."
1712384,2017-09-05 11:56:39 UTC,"Installing the mainline kernel 4.13rc6 intermediately solved the problem until the recent Ubuntu update from approximately 4.9.2017. This also upgraded the 4.10 kernel, which introduced the issue again. Even though the running kernel is 4.13rc6."
1712384,2018-01-17 04:36:18 UTC,I'm seeing a similar error on my Dell XPS 15 9550 with Geforce GTX 960M. I've installed nvidia-384 (384.111-0ubuntu0.17.10.1) from the propietary repository. It happens after suspending too!
1712384,2018-01-17 04:37:02 UTC,"Forgot to add, my Ubuntu installation is 17.10 version."
1712395,2017-08-30 02:16:27 UTC,"As a workaround, the ""stank"" program can quickly identify shell script files, which can be piped to xargs bashate in order to lint just the shell scripts."
1712395,2017-08-30 17:46:43 UTC,"I don't know why you'd need a separate (non builtin, go) package. `file` does this just fine:"
1712396,2017-08-31 05:37:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499459"
1712396,2018-10-01 13:17:58 UTC,"Change abandoned by Ken Giusti (<email address hidden>) on branch: master
Review: https://review.openstack.org/499459
Reason: Option removed via:"
1712406,2017-08-23 13:23:01 UTC,"Traceback (most recent call last):
  File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 434, in errback
    self._startRunCallbacks(fail)
  File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 501, in _startRunCallbacks
    self._runCallbacks()
  File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 588, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 1184, in gotResult
    _inlineCallbacks(r, g, deferred)
--- <exception caught here> ---
  File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 1126, in _inlineCallbacks
    result = result.throwExceptionIntoGenerator(g)
  File ""/usr/lib/python3/dist-packages/twisted/python/failure.py"", line 389, in throwExceptionIntoGenerator
    return g.throw(self.type, self.value, self.tb)
  File ""/usr/lib/python3/dist-packages/provisioningserver/drivers/pod/virsh.py"", line 906, in compose
    created_machine = yield deferToThread(conn.create_domain, request)
  File ""/usr/lib/python3/dist-packages/twisted/python/threadpool.py"", line 246, in inContext
    result = inContext.theWork()
  File ""/usr/lib/python3/dist-packages/twisted/python/threadpool.py"", line 262, in <lambda>
    inContext.theWork = lambda: context.call(ctx, func, *args, **kw)
  File ""/usr/lib/python3/dist-packages/twisted/python/context.py"", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File ""/usr/lib/python3/dist-packages/twisted/python/context.py"", line 81, in callWithContext
    return func(*args,**kw)
  File ""/usr/lib/python3/dist-packages/provisioningserver/utils/twisted.py"", line 232, in wrapper
    result = func(*args, **kwargs)
  File ""/usr/lib/python3/dist-packages/provisioningserver/drivers/pod/virsh.py"", line 750, in create_domain
    self.attach_interface(request.hostname, best_network)
  File ""/usr/lib/python3/dist-packages/provisioningserver/drivers/pod/virsh.py"", line 638, in attach_interface
    '--model', 'virtio', '--config'])
  File ""/usr/lib/python3/dist-packages/provisioningserver/drivers/pod/virsh.py"", line 242, in run
    cmd = ' '.join(args)
builtins.TypeError: sequence item 3: expected str instance, NoneType found"
1712406,2019-09-19 14:49:07 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1712406,2017-09-27 12:36:09 UTC,"Hi Ante,"
1712406,2017-09-27 09:44:17 UTC,"@MAAS you might reconsider and invalidate this bug, since it was a configuration error. However, a cleaner error/feedback to the user would be helpful."
1712406,2017-08-22 18:53:04 UTC,"Hi Jeff,"
1712406,2017-08-24 13:55:08 UTC,"Hi Jeff,"
1712406,2017-08-23 13:12:25 UTC,"libvirt-bin was installed as part of the hand installation by selecting ""Virtualization Host"" as part of the package selection."
1712406,2017-08-24 14:54:01 UTC,"Right, we can confirm that with networking in place it all works fine."
1712411,2017-09-06 01:06:54 UTC,"Reviewed:  https://review.openstack.org/498861
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94b904abbad1c9655b6dec1a2e58d73bc913ed47
Submitter: Jenkins
Branch:    master"
1712411,2017-09-05 16:03:43 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/500908"
1712411,2017-09-15 22:14:57 UTC,"Reviewed:  https://review.openstack.org/500907
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fd59e9adc62bec4502e764ff380a318d27a58b57
Submitter: Jenkins
Branch:    stable/pike"
1712411,2017-09-05 16:03:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/500907"
1712411,2017-09-25 14:28:08 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1712411,2017-10-24 12:43:27 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712411,2017-09-15 22:19:20 UTC,"Reviewed:  https://review.openstack.org/500908
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a1462d2608bd0c3ee9cd8686b145bb1d84ffab3b
Submitter: Jenkins
Branch:    stable/pike"
1712411,2017-08-29 18:48:47 UTC,Bug 1713796 is reported for some things missing in unshelve instance scenarios.
1712411,2017-09-04 17:19:15 UTC,"Reviewed:  https://review.openstack.org/498627
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b05655ef8b62bcb21345e778baeed3114c11571
Submitter: Jenkins
Branch:    master"
1712411,2017-08-29 17:02:06 UTC,"Following up on some earlier comments, this is already handled for cold migration / resize via this change: https://review.openstack.org/#/c/497606/"
1712411,2017-08-29 16:31:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/498861"
1712411,2017-08-29 00:09:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/498627"
1712411,2017-08-28 15:05:14 UTC,"After discussing this bug in the nova-scheduler meeting today, we agreed to just fix the problem in the conductor live migration task at the point of failure, rather than work on some periodic cleanup task."
1712411,2017-08-24 06:16:19 UTC,"@Matt, yea, I filed a bug for that https://bugs.launchpad.net/nova/+bug/1712718"
1712411,2017-08-24 03:27:27 UTC,"Another semi-related bug Alex Xu pointed out, is that we don't cleanup allocations for the current host when doing a reschedule. The scheduler will claim allocations against the next host, but won't remove them for the current host."
1712411,2017-08-22 19:44:22 UTC,"Semi-related, but probably a separate bug, is that there is the ability to cancel an in-progress live migration and that also does not remove the allocation on the destination node for the instance."
1712411,2017-08-29 17:32:22 UTC,"Looks like evacuate has some gaps still though, which should go into a new bug:"
1712415,2017-12-08 15:27:02 UTC,This issue was fixed in the openstack/keystone 13.0.0.0b2 development milestone.
1712415,2018-07-27 07:54:10 UTC,This issue was fixed in the openstack/keystone 12.0.1 release.
1712415,2017-10-31 21:20:37 UTC,"Reviewed:  https://review.openstack.org/514885
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d07677aba54362a4a3aa2d165b155105ffe30d73
Submitter: Zuul
Branch:    stable/pike"
1712415,2017-10-24 23:23:06 UTC,"Reviewed:  https://review.openstack.org/511822
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f776fc18383fcfdc97932eaaab261a0b85e0ef68
Submitter: Zuul
Branch:    master"
1712415,2017-10-13 12:29:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511822"
1712415,2017-08-23 13:36:21 UTC,"I'd like to recreate this locally, but it certainly sounds like something keystone can check for gracefully."
1712415,2017-10-25 02:06:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/514885"
1712421,2017-08-22 21:42:26 UTC,"As an example of the use-case described, see e.g. https://github.com/WebDrake/unity-system-compositor/pull/1/commits/83f95752717168d49c4b8d1d67ec7d111fb1c50a."
1712421,2017-08-23 09:39:53 UTC,"CommandLineOption and the other ""glue"" classes were designed with the idea that they'd be passed to MirRunner::run_with() and exist for the lifetime of the server."
1712421,2017-08-23 14:43:18 UTC,Good point re the `usc::Blacklist` class. I do however have other use cases involving multiple different command-line options which all need to be handled before the real init callback can run (this will be useful in separating out the different components of the `SystemCompositor` init callback and the custom command line options it needs).
1712427,2017-08-22 21:32:36 UTC,apport information
1712427,2017-08-22 21:32:34 UTC,apport information
1712427,2017-08-22 21:32:35 UTC,apport information
1712427,2017-08-22 21:32:37 UTC,apport information
1712427,2017-08-22 21:32:33 UTC,apport information
1712427,2017-08-25 14:37:48 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1712427,2017-08-27 10:38:38 UTC,"I have had this problem since a long time.
With kernel 4.13 it seems to be fixed."
1712427,2017-08-31 00:00:22 UTC,"Unfortunately I have to revise what I said. The bug does still exists in 4.13.
There is however the difference that with the 4.10 kernel it always exists, whereas in 4.13 it sometimes happens and sometimes correctly switches to analog audio. I haven't found yet any pattern when it happens."
1712427,2017-08-22 21:32:38 UTC,apport information
1712427,2017-08-22 21:32:32 UTC,apport information
1712427,2017-08-22 21:32:23 UTC,apport information
1712427,2017-08-22 21:32:30 UTC,apport information
1712427,2017-08-22 21:32:29 UTC,apport information
1712427,2017-08-22 21:32:28 UTC,apport information
1712427,2017-08-22 21:32:27 UTC,apport information
1712427,2017-08-22 21:32:25 UTC,apport information
1712427,2017-08-22 21:32:24 UTC,apport information
1712427,2017-08-22 21:32:22 UTC,apport information
1712427,2017-08-22 21:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1712427,2017-08-22 21:32:31 UTC,apport information
1712430,2017-12-12 20:15:44 UTC,"Reviewed:  https://review.opencontrail.org/38251
Committed: http://github.com/Juniper/contrail-packaging/commit/4c45280aad9f245d0ce02cc7ffe5e2f606a885dd
Submitter: Zuul (<email address hidden>)
Branch:    R3.2.3.x"
1712430,2018-01-16 21:40:57 UTC,"Review in progress for https://review.opencontrail.org/38946
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1712430,2017-12-11 18:39:19 UTC,"Review in progress for https://review.opencontrail.org/38251
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1712430,2018-01-18 18:18:51 UTC,"Reviewed:  https://review.opencontrail.org/38946
Committed: http://github.com/Juniper/contrail-packaging/commit/fa18174c47419eaa86e9b576dc35da3e500aa2e8
Submitter: Zuul (<email address hidden>)
Branch:    R3.1"
1712430,2017-08-31 04:57:30 UTC,"Reviewed:  https://review.opencontrail.org/34891
Committed: http://github.com/Juniper/contrail-packaging/commit/e5ec890a7dd989c990fe2b4032300797ed347758
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1712430,2017-08-24 22:51:36 UTC,"Review in progress for https://review.opencontrail.org/34891
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1712430,2017-09-26 22:17:59 UTC,Workaround for LAB:
1712431,2017-08-22 21:40:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712433,2017-08-22 21:51:56 UTC,The word 'strogly' should be 'strongly'
1712433,2017-08-23 16:08:49 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1712433,2017-10-09 16:48:20 UTC,Pull request created upstream - https://github.com/karelzak/util-linux/pull/519
1712433,2017-10-10 11:43:32 UTC,Upstream pull request has been merged and will be available in next release
1712433,2020-09-19 13:29:42 UTC,Looks like the upstream fix was included in the newer version of mount which is available in Ubuntu 18.04. The typo is now gone from http://manpages.ubuntu.com/manpages/bionic/en/man8/mount.8.html
1712440,2018-04-07 00:24:34 UTC,"Affects me, too, on OpenStack Pike & cloud-init 17.2-35-gf576b2a2-0ubuntu1~16.04.2."
1712440,2019-07-19 21:26:51 UTC,"Hi,"
1712440,2019-08-28 01:07:53 UTC,"Hello.  Yes I can confirm that, when this was written, the nameservers on lo would not be present in /etc/resolv.conf."
1712440,2019-08-28 18:47:44 UTC,Is this still reproducible on current Ubuntu cloud-images?  I can't reproduce this behavior you're describing.
1712440,2019-10-28 04:17:22 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1712441,2017-09-05 16:32:35 UTC,"There seems to be other problems when building with new binutils, thus waiting for the next version in Debian seems to be wise."
1712441,2017-11-03 17:01:27 UTC,I just uploaded
1712442,2020-05-03 17:29:25 UTC,"Same here on a brand new xubuntu 20.04.
I like the way text is condensed and the lines are sitting tight but missing underscores are a deal breaker."
1712442,2019-11-11 22:54:06 UTC,This is still a problem.
1712442,2019-11-11 23:23:52 UTC,"Oh, ya forgot to mention all the DejaVu Sans Mono fonts also don't display the underbar in Geany."
1712442,2020-05-03 17:27:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712451,2017-08-23 01:57:33 UTC,"Hi Qianyu, could you clarify what does ""network"" mean here? In allowed address pair there is only IP and MAC, so I think you mean subnet? If you mean subnet, then I think this is not a problem, because OVN/Neutron is L2 based. There is no requirement that a lport has to use IP from any specific subnet."
1712455,2017-08-23 02:06:09 UTC,"Hello Stéphane, or anyone else affected,"
1712455,2017-08-25 23:18:25 UTC,I've confirmed that the updated package does cause stale images to get updated (those that were marked as cached=true prior to the upgrade) and I've confirmed that LXD now updates images again as it used to.
1712455,2017-08-30 16:46:16 UTC,This bug was fixed in the package lxd - 2.0.10-0ubuntu1~16.04.2
1712455,2017-08-30 16:46:30 UTC,"The verification of the Stable Release Update for lxd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1712458,2017-08-23 06:36:33 UTC,You know liberty had been EOL for long time. I don't think we would maintain it.
1712460,2017-10-24 12:43:49 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712460,2017-09-25 14:28:25 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1712460,2017-09-20 01:12:50 UTC,"Reviewed:  https://review.openstack.org/498478
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5fa3f2ce5c7745c592bfefbd591f31db83a85175
Submitter: Jenkins
Branch:    stable/ocata"
1712460,2017-09-15 18:05:40 UTC,"Reviewed:  https://review.openstack.org/498477
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=98f0d8162167d1ff6e680adbc622ff7dbadc5a9a
Submitter: Jenkins
Branch:    stable/pike"
1712460,2017-08-28 19:18:02 UTC,"Reviewed:  https://review.openstack.org/496515
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ac4705516ada36794c7cc6626875c74c4ef8e547
Submitter: Jenkins
Branch:    master"
1712460,2017-08-28 14:22:23 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/498477"
1712460,2017-11-15 01:07:00 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1712460,2017-08-23 06:50:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496515"
1712460,2017-08-23 03:43:23 UTC,get_domain() calls conn.lookupByName() in nova/virt/libvirt/driver.py
1712460,2017-08-28 14:22:56 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/498478"
1712460,2017-08-23 08:40:37 UTC,I can reproduce the bug with nova(master) with virt_type = qemu.
1712463,2018-01-05 20:23:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531493"
1712463,2018-01-15 16:33:44 UTC,This issue was fixed in the openstack/oslo.concurrency 3.25.0 release.
1712463,2017-08-30 18:15:52 UTC,To be more specific about the preceding comment:
1712463,2017-08-30 17:01:16 UTC,Taskflow problem:
1712463,2018-01-11 22:45:34 UTC,The Glance part of this bug is addressed by https://review.openstack.org/531498
1712463,2017-08-29 21:25:35 UTC,This definitely looks like a bug in the prlimit stuff to me. The assumption that sys.executable is always going to something that can run the prlimit module definitely isn't always the case. Besides the uwsgi case (which admittedly does some weird things) there is also the case where sys.executable is None.
1712463,2017-08-30 16:53:33 UTC,It looks like there are two different bugs here:
1712463,2017-08-29 16:23:11 UTC,Had to put a waitall() on the greenpool when the task was being spawned.  That gave me some useful logs and I can watch the task going to failure.  Not sure yet exactly why without the waitall() the tasks are just sitting there.
1712463,2018-01-11 00:08:57 UTC,"Reviewed:  https://review.openstack.org/531493
Committed: https://git.openstack.org/cgit/openstack/oslo.concurrency/commit/?id=55e06261aa86c87c7c059fbddc97cdbaae06e8dd
Submitter: Zuul
Branch:    master"
1712463,2017-08-29 20:57:36 UTC,We're using oslo_concurrency.processutils to call qemu-img ; want to use the process limits facility that gives us because of a security issue (bug #1449062).
1712478,2017-10-24 09:22:13 UTC,2.5.3 looks to contain some fixes for rstp; we will be updating to this version soon in Ubuntu 16.04.
1712478,2017-10-24 09:27:04 UTC,I've uploaded 2.5.4 to:
1712478,2017-10-24 09:28:34 UTC,Marking 'Incomplete' for now - please test the proposed package updates and set back to 'New' with some feedback once tested.
1712480,2018-09-18 09:22:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/603340"
1712480,2019-03-22 03:48:32 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1712480,2018-09-24 14:46:46 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1712480,2018-09-24 14:46:45 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1712480,2018-09-20 15:40:21 UTC,"Reviewed:  https://review.openstack.org/603340
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=787120498813c9928cb40ce4ad27f73d506e3721
Submitter: Zuul
Branch:    stable/queens"
1712480,2018-09-17 14:02:46 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/603140"
1712480,2018-09-17 18:28:06 UTC,"Reviewed:  https://review.openstack.org/603140
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6c291830232cf0b628bf55dd2ae3f0966327645b
Submitter: Zuul
Branch:    stable/rocky"
1712480,2018-08-30 15:03:25 UTC,"Reviewed:  https://review.openstack.org/546920
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=018522f4d0566bf9f22fe0264eaedffa12f245e9
Submitter: Zuul
Branch:    master"
1712480,2018-02-22 08:37:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546920"
1712480,2017-08-23 10:04:41 UTC,"Hi,"
1712484,2017-09-18 03:53:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712487,2017-08-23 12:56:17 UTC,This sounds very strange and I doubt it's caused by Inkscape itself.
1712487,2019-06-21 12:53:49 UTC,"Closing as there has been no response for over 60 days. If you still have a similar issue with the latest Inkscape version, please file a report on our new bug tracker: https://inkscape.org/report. Thank you!"
1712501,2018-01-29 09:16:12 UTC,Any updates? Thanks.
1712501,2018-03-20 00:45:05 UTC,neutron rbac extension is not supported
1712501,2018-03-20 08:46:48 UTC,"Neutron rbac is not an api extension, but working policy framework. Lack of neutron rbac support in OpenContrail is causing a not fully multi-tenant experience with OpenStack and OpenContrail as there's no possibility to grant access to resources for specific projects."
1712507,2017-10-16 10:45:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/512258"
1712507,2017-09-12 12:13:33 UTC,"This is cool, it will also reduce usage of `curl` in many heat-templates and provide native support for tempurl"
1712508,2017-08-23 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1712508,2019-12-07 20:04:12 UTC,"I confirm this bug is present on Ubuntu 18.04, my hardware is an Intel HD Graphics 5500."
1712508,2018-08-16 09:52:54 UTC,"The bugs prevails in kubuntu 18.04, unfortunately."
1712508,2018-04-13 09:05:52 UTC,"Christian,"
1712508,2017-11-12 13:38:34 UTC,"Christian,"
1712508,2017-11-07 17:47:14 UTC,Great! Thanks a bunch!
1712508,2017-11-07 16:55:50 UTC,"@udippel @kaihengfeng Sorry for the late get back, for some reason I didn't get notified there were answers."
1712508,2017-11-02 07:20:23 UTC,Please try kernel in http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/
1712508,2017-11-01 16:25:41 UTC,"Christian, the problem is that 17.10 does not use the mainline kernel. I bet that the mainline kernel doesn't work. Still, I can't tag it, and with *buntu's distro kernel, you can't neither.
Could you follow #4 using the most recent mainline kernel as described in that link in order to tag this bug appropriately?"
1712508,2017-11-12 13:21:42 UTC,@udippel What project do I need to file the bug into? Their site is confusing me.
1712508,2017-08-30 04:25:00 UTC,"The ""experts"" (i915 maintainers in this case) only pay attention to bugs that exist in latest mainline kernel..."
1712508,2017-08-29 16:21:07 UTC,"#6:
It says different over there. Nevermind. I don't want to break my system, since I need it."
1712508,2017-08-29 04:25:58 UTC,You don't need to touch those DKMS to install mainline kernel.
1712508,2017-08-28 18:13:06 UTC,"at #4: I'd love to, but need to get rid of all kernel modules (hopefully without breaking the system).
The link isn't specific on how to do that. Here I have"
1712508,2017-08-25 14:39:11 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1712508,2017-08-24 08:08:02 UTC,"For comparison, here is the dmesg of a functional machine, same type, lenovo T410s, same software, same BIOS; but with deactivated NVIDIA graphics (type 2924)"
1712508,2017-08-23 20:57:26 UTC,"Sorry, but I run into another bug:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439784"
1712508,2017-11-01 15:17:56 UTC,"I'm suffering from the same problem. I'm also the author of the referenced question on askubuntu, https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04 which I update periodically when I've tried new things."
1712520,2020-03-18 01:04:22 UTC,I am getting this message very very frequently.
1712520,2019-07-02 18:17:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712522,2019-03-26 12:45:42 UTC,This bug is dependent on https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1702777
1712523,2018-12-04 09:00:48 UTC,"That's a known issue with architectures living on different servers. Please use apt directly as suggested by the page, it might take a while to adjust the code for that."
1712531,2017-08-23 10:38:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496608"
1712531,2018-09-28 11:10:02 UTC,"Hi, i cannot reproduce the issue? Could you try to see if still present? Maybe was fixed on other patch no attached to this bug id"
1712531,2018-10-09 08:17:44 UTC,"Hi Eduardo Gonzalez,"
1712532,2017-10-19 08:43:04 UTC,Could be this the same of bug #1712866
1712532,2017-10-20 21:34:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712543,2017-08-29 00:31:02 UTC,"In the long run, we probably should support doing this in 1 step."
1712543,2017-08-29 00:33:27 UTC,"@Roger Peppe,"
1712543,2017-08-30 10:35:20 UTC,"I think we just need to update the documentation. SCP doesn't really
support this.
https://www.balabit.com/documents/scb-latest-guides/en/scb-guide-admin/html/chapter-scp-agent-forwarding.html"
1712543,2017-08-30 11:19:02 UTC,"Yeah you're right. I didn't realise that normal scp didn't support this.
The error message is really terrible for it - I wonder what the
underlying issue actually is."
1712543,2017-08-30 12:12:19 UTC,"The doc I linked seems to say that scp forcibly disables Agent forwarding,
and then it ends up trying to use something like host auth (instead of user
auth) between the remote machines."
1712543,2017-08-30 12:40:13 UTC,"I don't really understand the exact relevance of that linked doc.
Are you saying that wendigo.canonical.com uses agent forwarding,
or that any scp between two remote endpoints will use agent
forwarding or... ?"
1712543,2017-09-07 09:02:35 UTC,"It sounds like the first machine you need to connect to would want to directly connect to the second machine. But you wouldn't have your local credentials on the remote machine, which is where you usually forward your agent connection (so you can:
 $ ssh machine-1
 $$ ssh machine-2
) uses your agent from your desktop tunneled over ssh to machine-1 so you don't have to have your credentials there."
1712573,2018-02-28 09:45:52 UTC,Is this still relevant? Looks like the test failures have stopped now:
1712580,2017-09-20 19:35:49 UTC,= Testing AMD64 =
1712580,2017-09-20 18:36:39 UTC,= Testing ppc64el =
1712580,2017-09-20 17:13:37 UTC,= Testing =
1712580,2017-08-23 13:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1712580,2017-08-25 01:23:24 UTC,"Jeff,"
1712580,2017-09-20 17:11:37 UTC,From WuFan:
1712581,2017-08-23 14:06:31 UTC,"On Wed, Aug 23, 2017 at 01:29:21PM -0000, Jean-Baptiste Lallement wrote:

> Public bug reported:
>
> artful desktop 20170823
>
> When the user clicks on the oem-config-prepare-icon on the desktop, it
> cannot be executed directly and there is a dialog saying that the
> application is not trusted (cf screenshot - in french)
"
1712581,2017-09-07 19:32:31 UTC,This bug was fixed in the package ubiquity - 17.10.7
1712586,2017-12-25 12:11:52 UTC,Blocked by bug 1737981 ( https://bugs.launchpad.net/dragonflow/+bug/1737981 ).
1712586,2020-06-23 17:22:07 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/496837"
1712587,2017-11-07 02:02:49 UTC,Got the same problem here with ubuntu 16 and firefox 56. Instant crash
1712587,2018-06-27 13:24:48 UTC, Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.
1712587,2019-01-16 10:18:06 UTC,"Bug did not close due bug watch
Upstream report has since been closed ""RESOLVED WORKSFORME""
No reply from reporter so closing"
1712589,2020-07-09 13:33:56 UTC,"I tried Andrea's reproducer on Focal and couldn't get apache2 to crash. It's tempting to set it Fix Released, but we didn't really identify where the problem is, so Incomplete will be."
1712589,2020-01-10 17:35:40 UTC,"No new info at the moment, bug still in our queue."
1712589,2018-06-27 10:04:04 UTC,More detailed backtrace:
1712589,2019-01-09 14:05:10 UTC,"Still happens on xenial, and disco as well, where we have:
apache2: 2.4.34-1ubuntu2
libapache2-mod-wsgi-py3: 4.5.17-1build2"
1712589,2019-07-10 14:35:44 UTC,Still happening on xenial:
1712589,2018-06-27 10:03:47 UTC,"Add
        WSGIDaemonProcess example.com processes=2 threads=15 display-name=%{GROUP}
        WSGIProcessGroup example.com"
1712593,2017-09-12 09:58:13 UTC,"I can confirm this change of behaviour, and it points to the KDE menue rather than wakeonlan.
Since I wrote 'wakeonlan' and the MAC-address into file, saved it under /usr/local/bin, the machine starts perfectly okay.
Therefore, it really looks like an inconsistency of KDE, and its behaviour of accepting parameters following a command."
1712602,2019-09-19 11:53:41 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1712607,2018-03-02 13:48:59 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1712612,2017-08-28 15:37:12 UTC,"Live example from the python-ironicclient CLI docs:
https://docs.openstack.org/python-ironicclient/latest/cli/osc/v1/index.html#baremetal-volume-connector-create"
1712615,2017-09-13 16:10:44 UTC,"3.0 beta, confirmed.  There was one instance where a page refresh changed the Folders dropdown display a bit -- it appeared to have both up/down arrows, and didn't dropdown but only showed a single line at a time.   Another refresh returned it to normal, and I wasn't able to get that to happen again so it must have been a reload error or something."
1712626,2017-08-25 17:33:13 UTC,"I will look into testing it on our nova host.
I tested it on a vm just to ensure it booted ok- no issues.  I will try it on the nova host as soon as i can and see if i am able to launch a virtual instance."
1712626,2017-08-25 14:46:16 UTC,Can you test the kernel posted in comment #7 of bug 1709784 ?
1712626,2017-08-24 18:00:05 UTC,Also see Bug 1709784  -- seems to be the same issue.
1712626,2017-08-28 19:34:18 UTC,I noticed that the repo now has kernel 4.4.0-93 available- i tried that but it did not work either - it also seemed to set SMT to 8 which caused me a few problems until i realized what it did.
1712626,2017-08-23 21:41:09 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1712626,2017-08-24 12:33:57 UTC,not able to run apport-collect
1712626,2017-08-23 20:20:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1712626,2017-08-25 18:21:53 UTC,"Added kernel 4.4.0-94-117 to the nova node
I am now able to create VMs on it."
1712626,2017-08-23 21:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1712630,2017-08-23 17:52:41 UTC,"ML v2.1.3 btw, sorry"
1712630,2017-08-24 23:37:13 UTC,"Looks like it's appeared after a reboot. Odd that it doesn't happen immediately, however, given other actions propagate to the menu seemingly live."
1712633,2017-10-15 16:09:03 UTC,I switch it to public as a private bugreport has been ignored for two months.
1712633,2017-10-21 15:30:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712633,2018-06-13 13:59:46 UTC,It is still there: blueman-applet crashed with AttributeError in _on_transfer_started(): 'NoneType' object has no attribute transfers.
1712635,2017-08-28 21:55:14 UTC,"The link on secondary ID is broken, too."
1712635,2017-09-13 18:46:27 UTC,Confirmed this in a very specific case on 3.0 beta
1712635,2017-10-03 21:42:27 UTC,"This is actually worse in 3.0.0 - now, I'm not even seeing an alert message if there is another patron with the same ID. (I was seeing the alert message in 2.12.4, but clicking on the link wouldn't pull up anything.)"
1712635,2017-10-09 16:15:22 UTC,"Tested on a fresh 3.0.0 server - I'm getting the alert message, but if I try to either right or left click on it, it disappears and doesn't go anywhere."
1712635,2017-10-13 20:16:28 UTC,Tested on demo.evergreencatalog.com (3.0.0)
1712635,2018-05-29 16:11:51 UTC,Still wonky in 3.1
1712635,2020-12-18 15:51:47 UTC,I'm no longer seeing this problem in 3.6.1 so marking it Won't Fix
1712639,2017-08-23 18:57:46 UTC,The nfs-server.service unit declares a dependency on the local fs being mounted before it starts:
1712639,2017-10-24 04:17:21 UTC,[Expired for nfs-utils (Ubuntu) because there has been no activity for 60 days.]
1712639,2017-08-24 05:05:32 UTC,Hi Steve
1712639,2017-10-24 06:00:36 UTC,The problem still exists.
1712644,2018-06-08 20:57:13 UTC,The ability to do this is actually useful for testing.
1712644,2019-08-06 17:11:43 UTC,"The branch has been rebased to latest master, and changes have been made to ensure the page is watching changes to the date input even when the input is seen as identical to what it was previously."
1712644,2019-08-06 15:13:25 UTC,"*Doh* Spoke too soon, I wasn't using the ""Until logout"" option. Investigating a fix..."
1712644,2019-08-06 15:09:03 UTC,"Thanks Galen,"
1712644,2019-08-06 00:30:20 UTC,"Upon testing, this needs a little more bullet-proofing:"
1712644,2019-06-19 15:12:02 UTC,"On further testing without the additional checks in egDatePicker, it seems to be working just fine only using getTime(). I've squashed both Katlyn's and I's on my collab branch, as all changes to the ui.js have been reverted by my commit."
1712644,2019-06-18 14:49:50 UTC,"We ran into an edge case where if you manually input a previous month or year without the additional checks, it would still allow you to submit. I originally assumed getTime would have done the trick as well, and I'm still not 100% sure why it didn't"
1712644,2019-06-18 14:28:01 UTC,"Thanks, All.  Regarding the implementation, I'm curious about the added year/month/date checks.  Is the getTime() check not sufficient?"
1712644,2019-12-27 21:03:26 UTC,"Pushed to master, rel_3_4, and rel_3_3. Thanks, Katlyn, Kyle, and Terran!"
1712644,2019-05-24 17:41:55 UTC,I was unable to test this fix on the bugsquash server.
1712644,2019-05-24 17:44:20 UTC,"Sorry, last comment was posted to the wrong bug."
1712644,2018-11-26 20:52:54 UTC,Removing milestones for lack of pull request.
1712644,2018-11-26 21:36:27 UTC,"I've resolved this issue with the following branch:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/klbeck/lp1712644-check-out-due-date"
1712644,2019-11-20 20:25:19 UTC,Tested and signed off with the New Devs Working Group. Sign off branch is here:
1712644,2018-12-13 20:30:41 UTC,Tested on 3.2.1 and it works well for us!
1712644,2018-11-27 23:08:48 UTC,"I've fixed a minor thinko and amended my previous commit with a fix.
Now, when the date picker is open, past dates cannot be selected. When a past date is manually typed into the due date input box, the checkout input is disabled and an error will appear below the date-picker."
1712644,2019-01-03 14:07:46 UTC,"Removing signoff because it causes an ""input out of range"" error on the patron registration / edit screen. (It doesn't stop it from saving on that screen, but shows an error.)"
1712644,2019-05-22 17:03:55 UTC,"The branch had the right general idea, but some things needed to be moved around a bit. I've made some changes and also added a year check to the outOfRange check(previously there was only a month and a day) and pushed up a branch here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/khuckins/lp1712644-check-out-due-date"
1712647,2018-01-20 07:46:29 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-509
1712649,2017-08-24 11:52:11 UTC,"While versions 5.5 and 5.6 do not support XA RECOVER statement they still commit only if XA COMMIT written as xa commit X'6774726964',X'627175616C',1234; So I marked these versions ""Confirmed"" too."
1712649,2018-01-25 09:05:46 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1818
1712649,2017-08-23 18:57:39 UTC,patch is against PS 5.7
1712649,2017-08-24 11:45:54 UTC,Thank you for the report.
1712654,2017-08-23 19:25:29 UTC,It's possible this is similar to https://review.openstack.org/#/c/463563/
1712654,2017-08-25 15:48:10 UTC,Can you make sure that you did not install the _1480_project_loadbalancersv2_panel.py enable script into openstack_dashboard/local/enabled directory?
1712654,2017-08-25 17:57:07 UTC,"Thanks Michael, I think you're correct for the install time issue. This PR https://review.openstack.org/#/c/495122/ fixes the problem I was hitting while running unit tests. I posted https://review.openstack.org/#/c/498003/1 for this as well, however I've not tested it and the prior review fixed my issue, but figured I'd post the code since I had it locally."
1712654,2017-08-29 20:25:54 UTC,"According to Michael's comment, _1480_project_loadbalancerv2_panel (i.e., Django version) looks **unmaintained**.
Is this bug 'Won't Fix'?"
1712654,2017-10-27 19:23:53 UTC,This issue was fixed in the openstack/neutron-lbaas-dashboard 4.0.0.0b1 development milestone.
1712654,2017-08-25 12:55:49 UTC,I'm also hitting this when deployed with 12.0.0.0rc2 of horizon and 3.0.0.0b1 of neutron-lbaas-dashboard for pike. I'll test with rc1 of n-l-d shortly but I assume the results will be the same.
1712655,2017-08-23 19:16:19 UTC,I checked and this is also an issue in artful.
1712655,2020-03-30 18:41:12 UTC,does work on later releases
1712656,2017-09-11 15:03:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712659,2017-09-08 21:00:04 UTC,Allow me to clarify my comment (thank you Friday brain):
1712659,2021-02-11 23:27:02 UTC,See current work to angularize the interface at: https://bugs.launchpad.net/evergreen/+bug/1846552
1712659,2017-09-08 18:43:57 UTC,"Ok, after further testing and poking around the code and database..."
1712659,2017-09-06 20:35:17 UTC,"Actually, it looks to me like the ""Apply Changes"" button has sort of double function:
  1. updating view to the currently selected Org Unit's list of copy locations
  2. ""saving"" any changes to the ordering of the copy locations."
1712659,2017-09-06 18:57:19 UTC,"I agree the ""Apply Changes"" button's function is ambiguous here. It is not 100% clear at first whether it's supposed to ""apply changes"" to a change in the selected Org Unit or the change(s) in the ordering of the Copy Locations."
1712659,2017-09-08 20:55:30 UTC,"So I'm confirming this, but also removing the webstaffclient tag since this exact behavior is also present in XUL & this is a ported interface."
1712665,2017-09-06 15:21:08 UTC,Really would like to use this updated package!
1712665,2017-09-06 16:29:02 UTC,Ubuntu 16.04 with the 4.10 HWE kernel needs an updated ifupdown2 and iproute2 packages for VRF support. Please consider updating this package
1712665,2017-09-19 18:34:32 UTC,If you'd like to download the latest ifupdown2 on your ubuntu box you can use this .deb:
1712680,2018-04-13 14:34:08 UTC,"Cloud-init fixed this in the commit 5f550420d2.
  https://git.launchpad.net/cloud-init/commit/?id=5f550420d2"
1712680,2018-03-13 14:46:41 UTC,Addendum to comment #8
1712680,2018-03-13 14:11:11 UTC,"If you're plagued by this bug, there are at least 2 workarounds and one
long term solution.  'A' and probably the easiest and most effective
workaround."
1712680,2018-02-22 22:33:12 UTC,"This bug is believed to be fixed in cloud-init in 18.1. If this is still a problem for you, please make a comment and set the state back to New"
1712680,2018-01-17 12:00:16 UTC,@Lee
1712680,2017-12-15 19:14:16 UTC,I'd like to add that we are seeing the same behavior as of Centos 7.4 and cloud-init 0.7.9-9.el7.centos.2.x86_64 in centos/os and 0.7.9-9.el7.centos.1.x86_64 in centos/updates.
1712680,2018-04-04 10:25:18 UTC,"Can someone please reference the _EXACT_ resolution w.r.t. ""cloud-images"" that has been released? (reference to git commit?)"
1712680,2017-12-12 20:54:14 UTC,"Networking is intended to only be rendered once per instance.
This re-rendering happens in MAAS because MAAS is a network datasource, and
network information is provided to cloud-init via system config (in
/etc/cloud/cloud.cfg.d by curtin)."
1712680,2017-12-07 02:32:34 UTC,@raharper I think the issue is MAAS is always sending the config. On Ubuntu its only applied on first boot while on CentOS its applied on every boot. I've confirmed /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg is being written. I think the bug is in cloud-init and out of MAAS control.
1712680,2017-10-05 13:11:30 UTC,I have the same problem - cloud-init is rewriting /etc/sysconfig/network thus undoing my change of default route.
1712680,2017-09-26 15:29:24 UTC,Quick note.  This case originally arose from a customer case who has agreed to close the ticket out as he believes he has a good way to proceed with this
1712680,2017-08-24 18:51:20 UTC,I think that we need the in-image curtin hooks for centos to write out a cloud-init network config disable if maas isn't sending network config to the image;  this is what curtin does for ubuntu.
1712680,2017-08-23 20:46:07 UTC,"Adding MAAS for tracking, as this was seen via maas testing affecting production environments."
1712680,2017-12-12 22:31:48 UTC,"Cloud-init certainly knows that MAAS is the datasource without networking;  During a curtin deploy, MAAS either dpkg-reconfigures cloud-init, or provides a cloud-config that writes out a config with MAAS URL defined (or one is provided on the kernel command line)."
1712684,2017-08-25 03:51:00 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc2 release candidate.
1712684,2017-08-24 16:11:03 UTC,"Reviewed:  https://review.openstack.org/496997
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b2f3c7bb25667527e7e1d2afd84d5d5533e7751
Submitter: Jenkins
Branch:    stable/pike"
1712684,2017-10-24 12:43:46 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712684,2017-08-24 03:25:44 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/496997"
1712684,2017-08-23 21:43:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496942"
1712684,2017-08-24 03:29:56 UTC,"Reviewed:  https://review.openstack.org/496942
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6de0e57c21472b99cbe71ec62b3967ef7282dec
Submitter: Jenkins
Branch:    master"
1712689,2017-08-23 21:28:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/496930"
1712689,2017-08-24 13:05:46 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/497237"
1712689,2017-08-24 14:26:49 UTC,"Reviewed:  https://review.openstack.org/496930
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e208cbb1f122b948af91a8d11c0f45dcec5bbc76
Submitter: Jenkins
Branch:    master"
1712689,2017-08-24 17:46:42 UTC,"Reviewed:  https://review.openstack.org/497237
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=df6ea0412f462815cf57560e96f33f4e2ff9d072
Submitter: Jenkins
Branch:    stable/pike"
1712689,2017-08-25 03:50:59 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc2 release candidate.
1712689,2017-10-24 12:43:47 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712692,2018-04-08 13:17:48 UTC,"Same here.
It looks like when it sees the current directory as ""selected object"", it treats 1 level above it as ""working directory""."
1712692,2018-04-08 13:18:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712692,2018-04-08 13:32:03 UTC,"It appeared that this bug was actually invalid. It is the %f parameter that is submitted for the directory selection and %d gives, as expected, the parent directory of selection. So check what you actually want to achieve with passing the parameters to the custom action."
1712695,2019-09-19 14:53:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1712695,2017-12-07 02:34:56 UTC,Adding juju to verify if they are looking at /etc/network/interfaces.
1712695,2017-12-07 19:27:05 UTC,"well, specifically, when reading an eni, one needs to account for:"
1712695,2018-01-31 08:21:49 UTC,"I believe there were issues with interfaces.d and Juju 2.1. I think in either 2.2 or 2.3 we switched to parsing both /e/n/i and all included files. We still only render a single /e/n/i that no longer has the include directive, but we've read the contents of the included locations."
1712695,2017-08-23 22:15:08 UTC,They cannot just parse /etc/network/interfaces;  curtin has always written out an eni that includes a source /etc/network/interfaces.d/*.cfg (meaning juju has a bug if they don't read all eni configs).
1712718,2017-08-24 21:30:45 UTC,"Reviewed:  https://review.openstack.org/496995
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c19ebcbd58bc673e336bc5fa3b815c7b0a20d628
Submitter: Jenkins
Branch:    master"
1712718,2017-08-24 23:45:09 UTC,"Reviewed:  https://review.openstack.org/497542
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=27fa0f03d266975e37dda6f4ccae1a58f7d5a029
Submitter: Jenkins
Branch:    stable/pike"
1712718,2017-08-25 03:50:57 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc2 release candidate.
1712718,2017-10-24 12:43:44 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712718,2017-08-24 04:03:07 UTC,There ia functional test for this bug https://review.openstack.org/#/c/496995/
1712718,2017-08-24 18:26:09 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/497542"
1712731,2017-08-27 17:20:39 UTC,See eg https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25234#8
1712735,2017-08-25 08:54:30 UTC,"Fail is from ./open-vm-tools-desktop.prerm
+ ./open-vm-tools-desktop.prerm remove
+ pkill -USR1 -f (vmtoolsd.*vmusr|vmware-user)
+ true
+ [ -d /run/systemd/system ]
+ deb-systemd-invoke stop run-vmblock\x2dfuse.mount
+ [ -d /run/systemd/system ]
+ [ remove = remove ]
+ deb-systemd-invoke stop run-vmblockx2dfuse.mount
Failed to stop run-vmblockx2dfuse.mount: Unit run-vmblockx2dfuse.mount not loaded."
1712748,2017-12-06 02:27:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712748,2018-05-10 13:06:07 UTC,I think this bug could be related to Debian bug #875651 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875651
1712748,2019-04-17 17:38:37 UTC,"I'm installing glusterfs-server on some new hardware.  If I ssh to the new host, sudo -i, then apt-get install glsuterfs-server, it fails with the timeout, and pstree shows that the process is hung up in systemd-ask-tty, but nothing ever appears on the terminal."
1712748,2019-05-27 18:55:34 UTC,Joi Owen (jlellis)
1712748,2019-06-10 20:37:40 UTC,This bug was fixed in the package glusterfs - 3.13.2-1ubuntu1
1712752,2017-08-24 07:55:41 UTC,"No idea if this is relevant, but the issue occured while using the attached font."
1712757,2017-08-24 19:11:42 UTC,"So my best guess... is that deja-dup-monitor is being run (it starts 120s after login) while an upgrade is happening, before the gschemas are re-compiled but after the binaries are installed."
1712757,2017-08-28 09:04:58 UTC,"There is no real solution to those cases and as you said it shouldn't be an issue for most users, probably not worth coming up with an hackish workaround (and the issue is not specific to deja-dup). One other case of such reports is also an outdated schemas in /usr/local or such taking over the package version"
1712757,2017-08-28 09:15:01 UTC,There is currently a segfault in the glib-compile-schemas code in artful (bug #1711545) which can explain outdated schemas registers
1712765,2017-08-24 09:00:07 UTC,This change was made by a bot.
1712765,2017-08-25 14:49:00 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1712765,2017-09-24 19:22:06 UTC,I reproduces the issue with the current mainline kernel 4.14.0-041400rc1-generic.
1712765,2017-09-25 05:34:59 UTC,"Try these kernel parameters, and see which works:
reboot=b
reboot=t
reboot=k
reboot=a
reboot=e
reboot=force"
1712765,2017-09-25 21:07:09 UTC,Thanks for your suggestions. I tried them all for 4.10.0-35-generic and 4.14.0-rc2 without any change to the issues. I noticed that the shutdown (until the power LED turns off) is very quick (1 to 2 seconds). The delay between shutdown and the unwanted reboot is about 3 seconds.
1712765,2017-09-26 03:32:05 UTC,Does the BIOS have anything related to autoboot? e.g. Wake of Lan. Try to disable them in the BIOS may help.
1712765,2017-11-06 20:15:09 UTC,the bios shows the following:
1712765,2017-11-07 03:02:15 UTC,"> On 7 Nov 2017, at 4:15 AM, Felix <email address hidden> wrote:
>
> the bios shows the following:
>
> graphic mode: [switchable]
> quiet boot: [enabled]
> network boot: [disabled]
> f12 boot: [enabled]
> d2d recovery: [disabled]
> wake on lan:[disabled]
> sata mode: [ahci mode]
>
> i dont have the skills to evaluate these settings, please advice whether
> it makes sense to chance any of them.
"
1712779,2017-08-24 10:58:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/497197"
1712782,2018-01-25 09:34:21 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3735
1712782,2017-08-24 14:30:27 UTC,"Queries missing are all of the same format, very simple primary key single row updates
e.g.
UPDATE tevoc SET `ev_oc_id` = '60750331',`ev_mkt_id` = '9675871',...... WHERE ev_oc_id = '60750331'"
1712782,2017-08-24 13:02:24 UTC,"SET GLOBAL log_output='TABLE';
SET GLOBAL slow_query_log=0;
SET GLOBAL general_log=0;
TRUNCATE TABLE mysql.slow_log;
TRUNCATE TABLE mysql.general_log;
SET GLOBAL long_query_time=0;
SET GLOBAL log_slow_rate_type = 'query';
SET GLOBAL slow_query_log=1;
SET GLOBAL general_log=1;
SET GLOBAL log_slow_admin_statements = 1;
SELECT SLEEP(120);
SET GLOBAL slow_query_log=0;
SET GLOBAL general_log=0;"
1712782,2017-08-24 12:33:45 UTC,Thank you for the report.
1712782,2017-08-24 10:25:23 UTC,"mysql> show variables like 'min%';
+------------------------+-------+

| Variable_name          | Value |


+------------------------+-------+

| min_examined_row_limit | 0     |


+------------------------+-------+"
1712782,2017-08-24 10:02:46 UTC,"mysql> SELECT VERSION();
+-----------------+

| VERSION()       |


+-----------------+

| 5.6.32-78.0-log |


+-----------------+
1 row in set (0.00 sec)"
1712782,2017-08-24 10:24:36 UTC,Current settings
1712789,2017-08-28 17:13:54 UTC,"As index in wordlist is the result of the match, resorting after creating the model element is not an option. Hence the wordlist has to have correct shape beforehand."
1712801,2019-12-12 21:16:20 UTC,The fix for this https://review.opendev.org/495756 was abandoned so while I've confirmed the bug since the reporter pushed a fix for it I'm not sure anyone cares about fixing it anymore.
1712801,2017-08-24 14:56:15 UTC,This was opened in response to this patch for the fix:
1712801,2017-08-24 14:55:07 UTC,I think it's upsream master
1712801,2017-08-24 14:46:21 UTC,Which release of Nova are you using?
1712801,2019-10-07 14:19:10 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/495756"
1712802,2017-08-24 12:00:03 UTC,This change was made by a bot.
1712802,2017-08-25 14:49:23 UTC,You may need to run the following from a terminal:
1712802,2017-08-26 08:44:51 UTC,"Hello Joseph,"
1712802,2017-08-27 14:40:30 UTC,"Further information after applying the suggested changes:
After inserting ""sudo apt-get install -f"" an error message was returned as: /var/cache/apt/archives/linux-image-3.19.0-84-generic_3.19.0-84.92 i386.deb
I then applied the second command of: ""sudo apt-get clean"". No error message.
I then entered ""sudo apt-get update"" to be met with a further group of error messages: Failed to fetch http://archive.canonical.com/ubuntu/distro/vivid/partner/binary-i386/Packages  404 Not Found {IP:91.189.91.15 80}
E: Some index files failed to download. They have been ignored, or old ones used instead."
1712802,2021-01-07 08:44:04 UTC,"3.19 EOL, please feel free to open a new bug is you're still seeing this issue."
1712808,2019-03-27 20:19:18 UTC,"Hmm, cgroup:rw has absolutely nothing to do with this.
LXD uses a cgroup namespace by default which completely ignores that particular setting."
1712808,2020-12-11 19:06:25 UTC,"For reference, the PR that Zygmunt had which was planned to fix this was https://github.com/snapcore/snapd/pull/8219, but there were issues with that approach. We need to pick it up again and rework to get an approach which matches the comments from Jamie there."
1712808,2020-03-22 01:53:19 UTC,"At the last engineering sprint, Zygmunt on the snapd team indicate that this was or would soon be sorted out in snapd."
1712808,2019-03-27 23:00:41 UTC,"Yeah, unprivileged LXC is likely to work pretty differently in the way it handles both cgroups and apparmor namespacing both of which are very relevant when you want to run snaps."
1712808,2019-03-27 22:48:29 UTC,"I was not doing this in lxd, but in an unprivileged lxc (not sure if it changes the things) that I've in my qnap nas, but without it I wasn't able to use snap at all."
1712808,2018-12-20 22:55:50 UTC,Actually to get this working I only needed to use this:
1712808,2018-01-08 14:05:27 UTC,I'm not quite sure what's the difference between the regular and privileged (or more privileged) containers but last time we looked at similar issues we came to the conclusion that any container in which apparmor is not stacked but instead directly shared with the host is unsupportable for us. I'm not sure if this is the same problem again. I didn't try to reproduce it yet.
1712808,2018-10-25 14:36:53 UTC,"I just hit this in a 16.04 container, but for reasons I don't understand installing the core snap first worked around the problem:"
1712808,2018-10-16 08:19:38 UTC,This will come up again and more frequently now that the LXD package upgrade will do the deb->snap transition even when running in a container itself.
1712808,2018-04-01 04:17:27 UTC,[Expired for snapd because there has been no activity for 60 days.]
1712808,2018-01-30 11:14:11 UTC,"I filed this bug because it seems ugly, but it does at least work with our current hacks, so closing this as Won't Fix would be better than changing something in a way that makes our hacks not work. :-)  If you feel you need to close it then go ahead."
1712808,2018-01-30 10:11:01 UTC,I'm wondering what we can do about it.
1712808,2018-01-08 14:32:47 UTC,"The ""even more privileged"" workarounds have been working in launchpad-buildd for a while now.  We can't use unprivileged containers for various reasons, for example because one of the categories of builds that needs to install snaps sometimes is live filesystem builds, and those do various things like mknod that'll never work in unprivileged containers."
1712808,2017-08-25 00:21:29 UTC,"On IRC, Stéphane suggested making the container ""even more privileged"" as a cleaner workaround, by adding the following to raw.lxc:"
1712808,2018-10-25 16:09:00 UTC,"Yeah, we've seen that re-running the command usually gets you past the error, so in your case, just running the ""snap install go --classic"" would likely have been enough."
1712814,2017-08-24 12:54:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/497235"
1712814,2017-09-28 23:54:19 UTC,"Reviewed:  https://review.openstack.org/497235
Committed: https://git.openstack.org/cgit/openstack/group-based-policy-ui/commit/?id=cf76c87cc7c0f090ec4ec4a55ac7c9b05804d902
Submitter: Zuul
Branch:    master"
1712817,2018-04-13 16:37:00 UTC,"Robie Basak:

> Based on https://irclogs.ubuntu.com/2018/04/13/%23ubuntu-
> devel.html#t11:56, this sounds valid for either init-system-helpers or
> debhelper.
>
> 13:47 <xnox> rbasak, the description sounds valid. i believe i have hit
> something similar before, thus yeah a fix to debhelper for this class of
> issues would be most welcomed.
>
> 13:47 <rbasak> xnox: thanks. debhelper, or invoke-rc.d?
>
> 13:48 <xnox> rbasak, my understanding was that maintainer scripts that
> are generated, do attempt to check if a thing was ""enabled and active""
> before the upgrade; and post upgrade. But maybe they only do so for
> systemd native units, and not for init.d->systemd units.
>
>
> ** Also affects: debhelper (Ubuntu)
>    Importance: Undecided
>        Status: New
>
"
1712817,2018-04-13 11:59:24 UTC,"On second thought, perhaps invoke-rc.d should treat a systemd disabled service the same way as one done through the policy-rc.d mechanism. Whichever way, the correct behaviour should be decided package-wide by the invoke-rc.d wrapper, so I'm reassigning to init-system-helpers."
1712817,2018-04-13 11:55:12 UTC,Thank you for reporting back.
1712817,2017-08-30 08:38:57 UTC,"Ok, so it looks like the following policy-rc.d will do the job for that particular case:"
1712817,2018-04-13 12:50:18 UTC,"Based on https://irclogs.ubuntu.com/2018/04/13/%23ubuntu-devel.html#t11:56, this sounds valid for either init-system-helpers or debhelper."
1712817,2017-08-25 17:30:12 UTC,systemctl:
1712817,2017-08-25 13:51:21 UTC,"Instead of adding “|| true”, it may have the possibility to check if the service is active and running?"
1712817,2017-08-25 13:50:24 UTC,"Yes, we provide an Ubuntu GNU/Linux derivatives for french national education, the software is installed and the admin can activate/desactivate it as wanted."
1712817,2017-08-25 12:57:51 UTC,Do you still have your terminal log from before the bits you showed in the bug report?
1712817,2017-08-25 13:29:10 UTC,"Ah, it's really disabled via systemd. Do you have any particular reason to have it installed but not running? The debian and ubuntu way is that if you don't want it running, you shouldn't install it."
1712817,2017-08-25 13:19:40 UTC,In fact the problem is that freeradius is stoped and disabled:
1712817,2017-08-25 18:21:51 UTC,"As a workaround, you can create a /usr/sbin/policy-rc.d file with these contents:"
1712818,2020-11-05 04:17:21 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1712818,2018-08-09 07:45:42 UTC,"It seems that the following commit for libvirt fixed the problem.
https://github.com/libvirt/libvirt/blob/960326237764f8970250a3608e7b2b880e030715/src/qemu/qemu_migration.c"
1712818,2020-09-05 12:19:29 UTC,Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays?
1712818,2017-08-25 03:24:10 UTC,"hi,eblake,the problem still exists on qemu 2.10_rc4,although the possibility is less than before."
1712818,2017-08-25 01:25:52 UTC,"Thank you,I will try it."
1712818,2017-08-24 16:48:53 UTC,"On 08/24/2017 07:59 AM, meeho yuen wrote:

> Public bug reported:
>
> The vm guest runs a iotest program, and i migrate it with virsh --copy-
> storage-all,then the qemu process on the source host happens to crash
> with the following message:
>
> kvm: block/io.c:1543: bdrv_co_pwritev: Assertion `!(bs->open_flags & 0x0800)' failed.
> 2017-08-24 11:43:45.919+0000: shutting down, reason=crashed
"
1712818,2017-12-28 21:50:33 UTC,I see the same thing:
1712835,2019-08-22 23:26:29 UTC,This issue was fixed in the openstack/python-cinderclient 4.3.0 release.
1712835,2019-03-22 13:38:22 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/645577"
1712835,2019-05-16 06:20:42 UTC,This issue was fixed in the openstack/python-cinderclient 4.2.0 release.
1712835,2019-03-26 15:17:57 UTC,"Change abandoned by Brian Rosmaita (<email address hidden>) on branch: stable/stein
Review: https://review.openstack.org/645573
Reason: Consensus on the dependency review is that it shouldn't be backported to Stein.  That makes this patch unnecessary."
1712835,2019-03-26 14:51:14 UTC,"Reviewed:  https://review.openstack.org/645582
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=47ef57982420e66a32e1860900802e28d5951959
Submitter: Zuul
Branch:    stable/stein"
1712835,2019-03-26 14:42:49 UTC,"Reviewed:  https://review.openstack.org/645577
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=5a884fb68f8610b379ce5b6c7a857b3f78201359
Submitter: Zuul
Branch:    stable/stein"
1712835,2019-03-22 13:39:56 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/645582"
1712835,2019-03-22 13:34:30 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/645573"
1712835,2018-10-15 15:05:40 UTC,Functionality appears to have been removed in https://review.openstack.org/#/c/63147/ .
1712835,2019-02-21 22:17:57 UTC,"Reviewed:  https://review.openstack.org/638179
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=7ee806f218cb22972a60d4e38ba1a4078e383f60
Submitter: Zuul
Branch:    master"
1712835,2019-02-26 20:09:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639424"
1712835,2018-10-15 14:57:51 UTC,Same issue still appears in 4.1.0.
1712835,2018-10-15 15:35:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/610619"
1712835,2017-08-24 13:50:39 UTC,See comments here:  https://git.openstack.org/cgit/openstack/python-cinderclient/tree/cinderclient/base.py?h=3.1.0#n251
1712835,2018-12-19 17:39:24 UTC,"Reviewed:  https://review.openstack.org/610619
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=7319a40767641aa83d75cc99a807fd231f52f1ac
Submitter: Zuul
Branch:    master"
1712835,2019-01-08 21:16:20 UTC,"Reviewed:  https://review.openstack.org/612529
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=e40166740ea78d4a1eb2a7040afe3a502374af51
Submitter: Zuul
Branch:    master"
1712835,2019-02-20 15:18:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638179"
1712835,2018-10-15 15:48:15 UTC,"At a quick scan, manilaclient seems to need the same fix: it has a ""_write_to_completion_cache"" method that isn't called anywhere."
1712841,2017-08-25 01:24:01 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1712843,2018-05-07 16:44:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712843,2017-09-10 23:55:09 UTC,*** This is an automated message ***
1712843,2017-09-10 10:11:54 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1712844,2017-09-06 22:29:08 UTC,"Release 17.04 (Zesty Zapus) 64-bit
Kernel Linux 4.10.0-34-generic x86_64
MATE 1.18.0"
1712844,2017-09-10 04:50:18 UTC,Additional info:
1712844,2018-01-14 04:28:27 UTC,"Ubuntu 16.04 64bit server edition, with xfce desktop"
1712844,2018-01-14 02:26:15 UTC,@<email address hidden>
1712850,2017-10-24 12:43:43 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712850,2017-08-25 03:50:55 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc2 release candidate.
1712850,2017-08-25 02:58:17 UTC,"Reviewed:  https://review.openstack.org/497606
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1dafea91bf6070c414c54ec0c26ebb4b6cb096c0
Submitter: Jenkins
Branch:    stable/pike"
1712850,2017-08-25 00:27:48 UTC,"Reviewed:  https://review.openstack.org/497592
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b53133ba50457f1a4983434800ebef710da67999
Submitter: Jenkins
Branch:    master"
1712850,2017-08-24 21:31:23 UTC,"Reviewed:  https://review.openstack.org/497541
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=78850296a54ff2e1ec298c013fa91fc6eace962b
Submitter: Jenkins
Branch:    master"
1712850,2017-08-24 23:45:29 UTC,"Reviewed:  https://review.openstack.org/497605
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ec8b92eceb7ecdce78037c2959cc106fd1e8f1f5
Submitter: Jenkins
Branch:    stable/pike"
1712850,2017-08-24 19:35:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/497592"
1712850,2017-08-24 18:23:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/497541"
1712850,2017-08-24 20:35:37 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/497606"
1712850,2017-08-24 20:35:17 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/497605"
1712852,2017-08-28 16:00:35 UTC,"I'm guessing we report whatever the most ""public"" address appears to be at
the time we list the machine addresses. I would guess the cloud gave us the
private address before it had allocated a public one.
The problem with never giving private addresses is that some clouds the
""public"" address is still one of the 10. addresses. (private deploys often
have an local LAN address but still RFC 1918)"
1712854,2018-08-21 14:51:28 UTC,I tested this on a test server with production data and can confirm Jason Boyer's observation where the same item can show up multiple times on the holds shelf due to previously cancelled holds.
1712854,2018-08-22 13:44:12 UTC,"I think I know where that's coming from.  I'll look at that ASAP, it should be a simple bug fix.  FWIW, I'm not in favor of that holding up merge. :)"
1712854,2018-08-29 18:28:02 UTC,"You didn't follow it, Mike, because it didn't go anywhere.  I was only thinking about the server-stored data (and people running master).  I now understand the need to change the persist key."
1712854,2018-08-28 14:22:14 UTC,"Or just leave the persist keys alone so no new settings are required?  (May want to delete existing values in this case).  Otherwise, we'll have to delete the abandoned WS setting types while adding new ones."
1712854,2018-08-28 14:34:54 UTC,"I'm fine with leaving the persist keys alone.  I mainly didn't want things to break with existing values, and it wasn't clear how we'd delete those on the browser side, but just once, without adding even more cruft like a ""I did the delete"" setting or cookie or something."
1712854,2018-08-28 14:53:28 UTC,"I know what you mean..  I guess a DB upgrade to delete existing workstation setting values would work, but since server-stored settings are new in 3.2, only those bravely testing master will have any values to clear.  Maybe just a comment in the release notes?"
1712854,2018-08-28 15:23:41 UTC,"Regarding the canceled holds, am I correct that we only want to see canceled holds if there is no succeeding hold (defined by having a later capture date) on the copy?"
1712854,2018-08-28 16:28:55 UTC,I've updated the branch with three commits:
1712854,2018-08-29 17:54:56 UTC,"I'm taking another look at this branch now, but I didn't see any changes made regarding eg.grid.circ.wide_holds.shelf. Do we have a consensus on this?"
1712854,2018-08-29 18:08:30 UTC,"Kathy, that's correct, I intentionally did not address that."
1712854,2018-08-24 19:57:38 UTC,Adding a note that eg.grid.circ.wide_holds.shelf and eg.grid.cat.catalog.wide_holds should be added to config.workstation_setting_type
1712854,2018-08-29 21:30:16 UTC,I forgot to mention that the three fixes Mike noted in comment #40 appear to work as expected.
1712854,2018-08-29 21:29:17 UTC,"I have a new branch available at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/kmlussier/lp-1712854-hold_ui_speed_improvements that resolves a conflict in hatch.js, rebases the code against master, and adds the new persist settings to server storage."
1712854,2018-08-17 13:26:45 UTC,"We've been testing this in IN briefly and have come across a fun thing, at least for the holds shelf. The API call used currently to show the holds shelf calls open-ils.circ.captured_holds.id_list.on_shelf.retrieve.authoritative.atomic which uses the alhr source, while the new code's call to open-ils.circ.hold.wide_hash.stream doesn't perform the same tricks to only look at the latest hold for each copy. So when you pull up the holds shelf and there's a popular item on it you can end up with situations like bug 1787590; which probably should have been put here as a comment but we had both forgotten that this branch was installed when that request came in. Anyway, you can see from that screenshot that the same copy is listed twice in the Canceled holds at the top, in addition to the active hold that it is currently on the shelf for (though the active hold is off the screen)."
1712854,2018-08-30 20:30:23 UTC,"Kathy, that looks like a thinko on my part.  Testing a fix now..."
1712854,2018-08-30 20:40:10 UTC,I've updated the branch with a commit to address that issue.
1712854,2018-08-30 20:40:35 UTC,"""That issue"" being the clear list not including shelf-expired holds."
1712854,2018-08-30 20:51:26 UTC,"I've also added a requested default sort order to each UI: shelf expire time for the shelf interface, and request time for the record holds interface."
1712854,2018-08-30 20:52:13 UTC,"Kathy, I was not working against your branch.  If you want me to pick those commits to a copy of yours, I can, or you can grab them.  Either works for me."
1712854,2018-08-31 13:15:47 UTC,I can work off your branch. It's not a problem. I'll take a look at this later this morning.
1712854,2018-09-04 17:01:49 UTC,"I have signed resolved the hatch.js conflict, signed off on Mike's commits, and picked my previous commit that adds the persist settings to server storage. This last commit will need a signoff before it can be merged."
1712854,2018-09-04 18:08:10 UTC,Thanks everyone!  Did some more basic tests and confirmed the new workstation setting types are accepting values.  Merged to master.
1712854,2018-10-04 17:09:00 UTC,Is this a fix that can be included in a 3.1 point release or do the changes prevent it from being backported?
1712854,2018-10-17 17:39:53 UTC,"This fix needs to be included in a 3.1 point release, and I understand that it should backport cleanly, so I have targeted it at 3.1.7. Since it is already marked as Fix Released for the 3.2 series I am not sure whether this bug will show up when the 3.1 RM looks for fixes to include."
1712854,2019-01-14 16:42:12 UTC,"Noting that when this is backported to 3.1.x, the fixes for bug 1792621 and bug 1792429 should be backported as well."
1712854,2018-08-29 19:13:31 UTC,"OK, thanks for the clarification! I can add the sql bits that move eg.grid.circ.wide_holds.shelf and eg.grid.cat.catalog.wide_holds to config.workstation_setting_type and removes the old persist keys."
1712854,2018-08-07 19:03:42 UTC,"Hi Bill,"
1712854,2018-08-06 22:02:52 UTC,"Agreed those are nice to have, but they come at a cost.  We have a chance to improve initial page load time and we're choosing not to, to speed up sorting and printing."
1712854,2018-08-07 01:05:52 UTC,"Bill,"
1712854,2017-09-15 18:21:05 UTC,"Holds appear to sort by hold ID, highest to lowest (or reverse chronological order by request date)."
1712854,2017-11-01 16:39:20 UTC,"There was actually no sorting at all on that record holds grid, IIRC the data just comes back in the order that it was retrieved from the database."
1712854,2017-11-27 22:02:17 UTC,"Thanks Cesar! I tested this today and discovered a problem that may also be an issue with the other grids using clientsort. The sorting works as expected on a small set of data, but once the dataset is large enough to require paging, it looks like we are only sorting one page at a time."
1712854,2017-11-28 21:57:58 UTC,"Kathy,"
1712854,2017-11-29 19:33:23 UTC,Thank you for the further explanation Mike! That's good to know.
1712854,2017-11-29 20:05:02 UTC,"We should be able to, but the risk is slowness for large hold lists. It's worth a try, though, I think."
1712854,2017-12-01 16:51:20 UTC,"Adding a note that sorting in Browse Holds Shelf works the same way. I also checked negative balance users (another grid touched by this branch), but was unable to determine if it experienced the same issue due to bug 1735791."
1712854,2017-12-04 16:43:49 UTC,"I've pushed a branch that causes the Hold Shelf and Record > View Holds UIs to load all hold data up front.  It works fine with my small dataset, of course, but will need testing in large environments to confirm that it's usable."
1712854,2017-12-12 21:36:59 UTC,"I've been looking at this on a test VM and would like to get some of our people to look at it on a system with production data. In the meantime, however, I noticed a couple of issues."
1712854,2017-12-19 22:55:08 UTC,Kathy here's a branch that addresses the issues above:
1712854,2018-01-05 18:52:38 UTC,"We put this on our test server that has a copy of production data and it took a full five minutes to load a branch that had a large hold shelf - not sure how many items was on the shelf, but more then 1200. When I tried to get farther, it got confused and started redownloading the whole list again."
1712854,2018-01-08 19:55:47 UTC,"Hi Terran, thanks for testing this!
Are holds shelves with 1000+ holds a common occurrence?
I was under the impression those were the exception/outliers."
1712854,2018-01-08 20:13:34 UTC,"That was at one of our larger branches, but they're not the only one, and we expect to add additional large locations in the future."
1712854,2018-01-11 15:35:18 UTC,"Adding a note that I saw similar issues with performance. I've been adding 178 holds to a record in the Concerto dataset for this testing. When I first tested the code back in December, it took about 20 seconds to load the holds on this record. When I tested with the new branch this morning, it took more than 40 seconds to load. Our top bestsellers are likely to have hundreds of holds on them, so the 178 holds on one title seems like a reasonable threshold to test."
1712854,2018-01-24 16:32:30 UTC,"I've rebased the latest branch for the fixes relating to this LP here:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/cesardv/collab_lp1712854_clientsort_hold_grids_rebased"
1712854,2018-02-07 17:07:12 UTC,"I just wanted to add a note that I don't support merging this branch at this time. Although we want to see sorting in these interfaces, the slow retrieval speeds would be problematic for our staff. I would prefer to pursue an alternate method that would allow sorting with faster page loading times."
1712854,2018-02-07 17:28:28 UTC,I agree with Kathy on on not merging this branch.
1712854,2018-02-16 12:57:50 UTC,Sorting of columns in View Record Holds is critical for PaILS.
1712854,2018-02-26 21:23:53 UTC,"Scott,
Is it critical enough that libraries would be willing to wait this long for the interface to load so that they could have sorting? https://drive.google.com/file/d/1JArB98mpMfWlUYOrzNIY-bSvflCOUiBi/view"
1712854,2018-02-27 14:56:11 UTC,I agree that we do not want to implement anything that increases response time or wait time to load the screen.
1712854,2018-07-11 15:48:26 UTC,"Using Missouri Evergreen web client 3.0.9 - Yes, we must be able to sort these lists, especially the Hold Shelf. Waiting for long loading is not a good option. I'm glad you are already working on this issue."
1712854,2018-07-13 15:28:17 UTC,MassLNC has contracted with Equinox to address the speed issues with holds shelf & record view holds sorting.  Specs here: https://yeti.esilibrary.com/dev/public/techspecs/hold_list_speed.pdf
1712854,2018-08-01 17:08:21 UTC,"Hi all, please find a branch addressing the above at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1712854-hold_ui_speed_improvements"
1712854,2018-08-02 19:31:06 UTC,"Mike, API looks very useful.  I'm curious about the decision to pre-load all of the holds and use client sort, instead of using the shiny new server-side paging and sorting in these UI's, though. Is the assumption that staff will invariably do a lot of sorting and/or page through every hold on these UI's, making the initial extra data load worth it?"
1712854,2018-08-02 20:37:08 UTC,"Thanks, Bill.  There are a few reasons, some of them subjective, but one is behavioral."
1712854,2018-08-07 18:38:09 UTC,"Thanks, Mike.  Unfortuantely, I don't have anything newer than 2.12 on a production-sized database.  I thought about back-porting, but it would mean backporting/reindexing metabib display fields as well, so I can't offer any data at the moment.  (Soon, though, soon)."
1712854,2018-01-11 15:47:12 UTC,"Kathy,"
1712854,2018-01-11 16:42:24 UTC,"Details, details! ;)"
1712855,2017-08-24 15:31:38 UTC,Fix is here: https://review.openstack.org/#/c/497460/
1712855,2017-08-24 15:36:22 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/497461"
1712855,2017-08-24 20:44:24 UTC,"Reviewed:  https://review.openstack.org/497460
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=64cb56c81a7309a667eea2ce85147e62d02cac91
Submitter: Jenkins
Branch:    master"
1712855,2017-08-24 23:44:49 UTC,"Reviewed:  https://review.openstack.org/497461
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=96dcbdcbae0fa68076dea0b83c2baa17ae685b8b
Submitter: Jenkins
Branch:    stable/pike"
1712855,2017-08-25 03:50:58 UTC,This issue was fixed in the openstack/nova 16.0.0.0rc2 release candidate.
1712855,2017-10-24 12:43:45 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1712860,2017-08-30 16:44:06 UTC,"Reviewed:  https://review.openstack.org/499081
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=92e451c1af3a9590d8a701901f8adb58f5bb9341
Submitter: Jenkins
Branch:    master"
1712860,2017-09-07 21:07:01 UTC,"Reviewed:  https://review.openstack.org/501442
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=72f8b11e338e5cc2b2e0f81aece550d6969a1a03
Submitter: Jenkins
Branch:    master"
1712860,2017-09-06 21:03:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501442"
1712860,2017-09-05 14:15:51 UTC,"Reviewed:  https://review.openstack.org/500557
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=b57ef5643270da57b3c485106065fcdaa7b417bd
Submitter: Jenkins
Branch:    stable/pike"
1712860,2017-09-04 14:02:24 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/500557"
1712860,2017-08-30 00:06:12 UTC,"Reviewed:  https://review.openstack.org/497971
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=cb793d013610e6905f58c823e68580714991e2df
Submitter: Jenkins
Branch:    master"
1712860,2017-08-30 08:47:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499081"
1712860,2017-08-25 16:19:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/497971"
1712861,2019-10-22 17:45:05 UTC,Tested this and found an error that Bill corrected.  I added that correction in the top commit of my signoff branch:
1712861,2019-07-17 15:39:38 UTC,I have pushed a follow-up branch:
1712861,2019-11-20 20:06:05 UTC,Blake attempted to put this on a master sandbox and got a perl compilation error.
1712861,2019-07-03 20:05:23 UTC,"Thanks, Kyle.  +1 to wide_holds migration.  Did some testing and code review and have a few comments."
1712861,2019-11-25 17:50:14 UTC,"Oops, somehow managed to only copy the branch name and not the full URL: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1717366-patron-summary-autocollapse-rebase"
1712861,2019-07-10 17:23:43 UTC,"Okay, one last squash and now it should be ready. No changes to the API were needed(I was hesitant to modify the API for this as it's so context-specific), but instead making sure not to overwrite order_by, and ensuring its rules matched the rules set in the holds.retrieve API seems to have done the trick."
1712861,2019-11-25 17:49:48 UTC,"Thanks everyone! This branch should get that Perl compiling correctly, an additional syntax correction needed to be made: user/khuckins/lp1712861-notices-column-picker-patron-holds-perl-corrections"
1712861,2019-07-10 16:32:19 UTC,"I've made some changes and squashed them into a single commit(and a second for release notes) - Jumped the gun on the pullrequest above, as the sorting issues still persist, however there are some changes to the wide_holds that are included in the latest version of this code - it will now support multiple conditional restrictions(previously it only supported 'not')."
1712861,2017-09-14 14:02:35 UTC,Confirmed 3.0 beta
1712861,2020-04-21 16:08:19 UTC,"I have just tested this, as well, and was about to add my sign off into the mix."
1712861,2019-07-02 20:05:50 UTC,"I added the pullrequest prematurely previously, re-adding it now after a bit more thought has been put into the code changes."
1712861,2019-06-12 15:44:52 UTC,"I've pushed a branch here, migrating the Patron Holds UI over to the wide_holds API introduced in bug 1712854, allowing us access to the notice count and last notify time columns: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1712861-notices-column-picker-patron-holds"
1712861,2018-08-24 20:44:37 UTC,"It also adds it to record holds. The code doesn't touch patron holds, so we still have a need to add those columns in that interface."
1712861,2018-08-24 14:15:56 UTC,"Adding a note that the code in bug 1712854 adds the notice count and the last notify time columns in the holds shelf interface. I haven't tested a notification to see if they actually work, but they are there."
1712861,2018-04-13 19:41:49 UTC,Tested 3.0.6
1712861,2019-12-03 21:54:36 UTC,"And wrong link too, oops:"
1712861,2019-07-03 22:19:20 UTC,"Thanks for the feedback Bill! I've pushed a small commit that honors the display_count - the best way to do this here seemed to be on the JS side of things, making use of the existing limit parameter. 'display_age' looks like it'll want to be done on the API side of things, but I have an idea on a slight expansion of the restrictions parameter. There's handling for {not: blah}, handling for {greaterThan/lessThan} may be useful in this and other cases as well, so unless there's objection there, that's where I'm thinking of starting."
1712861,2020-02-20 18:12:42 UTC,"I have tested this code and consent to signing off on it with my name, rfrasur, and my email address, <email address hidden>."
1712864,2018-01-18 08:29:12 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2003
1712867,2017-09-20 00:26:27 UTC,This bug was fixed in the package linux-azure - 4.11.0-1011.11
1712867,2017-09-16 00:25:30 UTC,This bug was fixed in the package crash - 7.1.4-1ubuntu4.2
1712867,2017-09-16 00:25:24 UTC,"The verification of the Stable Release Update for kexec-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1712867,2017-09-16 00:25:18 UTC,This bug was fixed in the package kexec-tools - 1:2.0.10-1ubuntu2.4
1712867,2017-09-15 23:59:24 UTC,I have verified kexec-tools and crash with the 4.4 kernel in a ppc64el machine and both packages are working as expected.
1712867,2017-09-15 17:09:37 UTC,"Additionally took the new crash version and installed it on s390x. I can still load dumps produced before and also dumps done after updating crash (just in case crash is in any way used to produce the dumps, which I do not think is true)."
1712867,2017-09-15 16:47:07 UTC,I also verified that the current version fails to load the kdump kernel with linux-azure (4.11.0-1009.9) and that the version in -proposed fixes the problem. The version in -proposed also works as expected with the 4.4 xenial kernel running in azure and in kvm.
1712867,2017-09-15 16:23:51 UTC,Verified on Azure with 4.11 kernel that the current version (updates) fails to load the kdump kernel and the new one from proposed succeeds to load.
1712867,2017-09-15 16:01:22 UTC,"Hello Joshua, or anyone else affected,"
1712867,2017-09-15 15:51:56 UTC,Verified that kexec-tools 1:2.0.10-1ubuntu2.4 on s390x still works (with 4.4 kernel).
1712867,2017-09-08 19:00:17 UTC,I was able to properly dump a vmcore with the following steps:
1712867,2017-09-13 13:31:43 UTC,We are testing and will report soon.
1712867,2017-09-09 01:44:26 UTC,The following packages/versions are available in the PPA https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/azure/ for testing:
1712867,2017-09-09 01:15:30 UTC,I was able to make the xenial version of crash to work with both the linux-generic and linux-azure kernels applying the following upstream changes:
1712867,2017-09-08 20:07:06 UTC,Looks good! Glad we're making progress.
1712867,2017-09-08 19:53:22 UTC,linux-azure kernel patch: https://lists.ubuntu.com/archives/kernel-team/2017-September/086944.html
1712867,2017-09-05 20:02:57 UTC,Any news? Anything I should help test?
1712867,2017-09-01 13:53:04 UTC,Porting the artful kexec-tools from artful to xenial fixes the kcore parse failure and doesn't cause any regressions when used with the regular xenial kernel.
1712867,2017-09-14 22:28:11 UTC,"Hello Joshua, or anyone else affected,"
1712872,2019-06-03 22:39:10 UTC,"There is no longer a Creator filter in the serials interface, or at least I couldn't find it?"
1712882,2017-11-07 17:48:45 UTC,the patch is much better then the thing in the OP here....
1712882,2017-11-07 17:46:34 UTC,alredy done that. Even proposed a patch.... But they take for ever....
1712882,2017-11-07 13:30:03 UTC,the request should be send to upstream on the freedesktop bug tracker
1712900,2018-11-13 14:32:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712900,2019-09-25 12:50:26 UTC,https://salsa.debian.org/phpmyadmin-team/phpmyadmin/issues/24
1712900,2019-11-10 16:09:16 UTC,https://tracker.debian.org/news/1078745/accepted-phpmyadmin-4491dfsg1-2-source-into-unstable/
1712902,2017-08-24 19:51:06 UTC,https://github.com/phuang/ibus/pull/12
1712902,2017-10-21 13:43:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712914,2017-08-24 22:12:42 UTC,Why are you running gpk-update-icon?
1712914,2017-08-25 06:52:40 UTC,Uh... aren't we suppossed to test these programs?
1712914,2017-08-25 10:48:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1712914,2017-08-25 16:33:58 UTC,It's not trying to call another program. Ubuntu has a tool that tries to suggest tools when you type a non-existent command from the command line.
1712914,2017-08-26 13:31:33 UTC,e-mailed  author
1712915,2017-08-30 13:58:28 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-August/086749.html
1712915,2017-08-29 15:54:50 UTC,Option #2 makes the most sense.
1712915,2017-09-12 19:27:27 UTC,This bug was fixed in the package linux-azure - 4.11.0-1009.9
1712915,2017-08-25 20:06:39 UTC,"Josh,"
1712916,2018-09-19 14:02:58 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/371
1712917,2019-09-19 11:53:44 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1712918,2020-10-07 15:19:01 UTC,MP with fix: https://code.launchpad.net/~alfonsosanchezbeato/snappy-hwe-snaps/+git/network-manager/+merge/391889
1712918,2020-10-09 10:28:58 UTC,Bug fixed in the network-manager 20/beta channel:
1712918,2020-12-09 11:50:01 UTC,Fix backported to 10/stable (version 1.10.6-9) and latest/stable (version 1.2.2-28)
1712938,2019-10-22 03:50:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712938,2019-10-22 03:52:22 UTC,Sorry to drag up a very old bug like this - but this still seems to be an issue in new ubuntu/debian based distributions. I ran into this issue when using llvm-strip and it doesn't preserve .ARM.attributes - I have written a patch against llvm-strip that's being discussed here: https://reviews.llvm.org/D69188
1712970,2017-09-19 15:56:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712979,2017-09-04 17:47:47 UTC,"I think this issue was that we missed the gstreamer1.0-packagekit in the base install. I'm fixing that, then let's see."
1712979,2017-09-16 17:28:08 UTC,"Still having the problem. see screenshot.
corrado@corrado-HP-p3-aa:~$ uname -a
Linux corrado-HP-p3-aa 4.12.0-13-generic #14-Ubuntu SMP Sat Sep 2 15:52:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
corrado@corrado-HP-p3-aa:~$"
1712979,2017-09-04 19:06:06 UTC,This bug was fixed in the package ubuntu-meta - 1.399
1712979,2017-09-04 17:48:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712979,2017-08-30 22:14:43 UTC,"That bug seems old & ignored.
What works here is to install gstreamer1.0-packagekit, then -"
1712979,2017-09-23 10:09:02 UTC,I filed a new bug #1719077.
1712979,2017-08-30 07:22:41 UTC,"Thank you for your bug report, indeed I can confirm that, the issue is in gnome-software, command line line which has the same issue
$ gstreamer-codec-install ""gstreamer|1.0|rhythmbox|Apple Lossless Audio (ALAC) encoder|encoder-audio/x-alac"""
1712979,2017-08-25 15:01:08 UTC,"""find software"" does nothing."
1712979,2017-08-25 13:20:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1712979,2017-08-30 08:09:39 UTC,it seems to work for mp3 so it's not all codecs missing
1712993,2017-08-25 15:09:14 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1712993,2017-08-25 15:09:58 UTC,Thanks for taking your time to report this issue and make Ubuntu better.
1712993,2017-08-29 11:27:38 UTC,"This is a Debian patch for the issue:
https://anonscm.debian.org/cgit/collab-maint/zabbix.git/diff/?id=ea3c3ea"
1712997,2017-12-26 18:30:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713016,2017-08-29 05:20:39 UTC,"First, try the latest mainline kernel [1] to see if the fix is already in upstream kernel."
1713016,2017-08-29 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1713017,2021-01-12 12:46:28 UTC,"As far as I can see, it is still disabled by default [in kernel bluez](https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/configure.ac#n243) nor [in launchpad](https://git.launchpad.net/bluez/tree/configure.ac#n239), neither do I find in being enabled explicitely in a package (but could not so easily find the package code online)."
1713017,2021-01-10 14:02:36 UTC,"@henning that sounds great! In which version did you see this? I expect the build would also need the libasound2-dev dependency, which should be in the control file."
1713017,2021-01-08 00:44:10 UTC,"as far as I can see in the bluez package source, the midi option is enabled now, so it *could* be closed..."
1713017,2020-02-11 23:41:27 UTC,"I have that problem on an Ubuntu 19.10 box. I tried to connect an ESP32 using BLE to act as a MIDI device. The device is detected and can be paired, but no MIDI device is created. It would be good to have this enabled."
1713017,2019-06-03 14:04:21 UTC,"The option is off by default in the upstream build see
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/README#n252"
1713017,2017-08-28 01:54:21 UTC,"Very interesting suggestion. Yes I think we should do this. Since it's a feature rather than a bug though, we would either need to request an exception to get it into 17.10, or wait till 18.04."
1713017,2019-02-15 05:55:36 UTC,"Any chance this could be added? I know the last message is from 2017, but there commercial products such as the Yamaha MD-BT01 Bluetooth Wireless MIDI Adaptor that rely on this being enabled."
1713017,2017-08-28 23:32:35 UTC,"For those seeking a workaround, see instructions here: https://gist.github.com/wvengen/7ebd29da38c08540832fb228c4628171#bluez-546"
1713017,2017-08-28 09:42:52 UTC,"Thanks, I agree that 18.04 would be good."
1713017,2019-06-02 12:47:49 UTC,I tried the latest version (5.50) from
1713021,2017-12-18 13:21:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713021,2017-12-18 13:22:07 UTC,Btw it's even worse with time - if you run your computer for 2-3 days those action start taking not 100ms but 1500-3000ms
1713021,2017-12-19 02:46:46 UTC,In theory that should never happen... If a machine is no longer able to provide adequate performance then the animation should be 0-1 frames long instead. But thanks -- that's an interesting observation that probably also needs fixing. Probably with a separate bug.
1713021,2017-08-28 01:58:08 UTC,"Yes, it had the same problem when I was testing the 3.25 PPA. And I can see the issue is still in upstream git:
  https://git.gnome.org/browse/gnome-shell/tree/js/ui/windowManager.js#n1191"
1713021,2017-08-25 10:01:09 UTC,gnome-shell's minimize/unminimize animations do nothing for almost the first 100ms or so. They look slow because the easeInExpo curve does nothing for most of the first half of the animation time:
1713021,2017-08-25 10:11:51 UTC,"This appears to be non-trivial to fix though, because changing to eastOut* curves reveals another bug: The animations overshoot their destination position and then suddenly snap back."
1713021,2017-08-26 15:59:59 UTC,Have you checked whether this issue is still present with GNOME Shell 3.25.91?
1713024,2017-09-22 14:54:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506682"
1713024,2019-10-28 19:01:02 UTC,"Tom this was not rebased or abandoned, what do we normal do in this  case where the code was +2 but needs a workflow label...https://review.opendev.org/#/c/506682/"
1713024,2019-10-28 20:41:18 UTC,"Jason - I'm unassigning this one since it's not being worked on actively.  Also tagged it for the generic driver.  It will be in the queue of genuine issues for that driver, with some good work towards a fix but (see toabctl's remarks) perhaps some more to be done."
1713029,2018-05-14 12:34:22 UTC,apport information
1713029,2018-05-14 12:34:20 UTC,apport information
1713029,2018-05-14 12:34:20 UTC,apport information
1713029,2018-05-14 12:34:18 UTC,apport information
1713029,2018-05-14 12:34:17 UTC,apport information
1713029,2018-05-14 12:34:16 UTC,apport information
1713029,2018-05-14 12:34:11 UTC,apport information
1713029,2018-05-14 12:34:09 UTC,apport information
1713029,2018-05-11 15:35:01 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1713029,2017-09-25 09:06:59 UTC,"I've used script
#!/bin/bash"
1713029,2018-05-14 12:34:23 UTC,apport information
1713029,2018-05-14 12:34:14 UTC,apport information
1713029,2018-05-14 12:34:15 UTC,apport information
1713029,2018-05-14 12:34:12 UTC,apport information
1713029,2018-05-14 12:34:13 UTC,apport information
1713032,2017-10-20 14:02:07 UTC,Note that the original bug report was on an older ceph version (rc)
1713032,2017-10-20 14:02:20 UTC,no - its on a newer ceph version - retrying.
1713032,2019-11-26 15:00:32 UTC,"------- Comment From <email address hidden> 2019-11-26 09:51 EDT-------
IBM bugzilla status -> Closed, will not be fixed by Canonical. Further processing will be tracked via different LP document in LP....."
1713032,2019-11-26 14:38:24 UTC,"The s390x support got fixed upstream and in Focal/Ussuri
and a backport for nautilus is upstream available, too.
There is currently an SRU in progress to get the backport into nautilus/Eoan.
A separate LP bug was opened for the work on nautilus, see LP 1851290.
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1851290"
1713032,2019-09-20 09:20:39 UTC,"I got an update that work is in progress.
Latest status can be seen here: https://github.com/ceph/ceph/pull/30079"
1713032,2019-06-03 14:40:38 UTC,Waiting for an update from IBM - setting to Incomplete for now.
1713032,2019-01-24 20:40:03 UTC,------- Comment on attachment From <email address hidden> 2019-01-24 15:35 EDT-------
1713032,2019-01-24 20:20:01 UTC,------- Comment on attachment From <email address hidden> 2019-01-24 15:18 EDT-------
1713032,2019-01-22 14:39:17 UTC,If you add the debug symbols repo as follows here:
1713032,2019-01-21 12:08:16 UTC,"Just noticed that all the packages here: https://launchpad.net/ubuntu/+source/ceph/13.2.0-0ubuntu1
don't have the suffix, hence one pick all needed ones from there.
But downloading and installing them manually is cumbersome and probably not the recommended way ..."
1713032,2019-01-21 11:50:57 UTC,"We got asked about the package with the debug symbol for ceph-mon - ceph-mon-dbgsym.
Since I couldn't find the packages with the debug symbols in the 'normal' UCA:
deb http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/rocky main
and since there doesn't seem to be a ddeb version of the UCA
I tried downloading the ceph-mon-dbgsym package manually from here:
https://launchpad.net/ubuntu/cosmic/+package/ceph-mon-dbgsym
But when I try to install I get:
sudo apt install ./ceph-mon-dbgsym_13.2.1+dfsg1-0ubuntu2.18.10.1_s390x.ddeb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'ceph-mon-dbgsym' instead of './ceph-mon-dbgsym_13.2.1+dfsg1-0ubuntu2.18.10.1_s390x.ddeb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:"
1713032,2019-01-10 13:30:23 UTC,"------- Comment From <email address hidden> 2019-01-10 08:20 EDT-------
I investigated the encode() / decode() of the magic number bit more:"
1713032,2019-01-09 16:30:31 UTC,"------- Comment From <email address hidden> 2019-01-09 11:25 EDT-------
From the stack backtrace ..."
1713032,2018-08-31 15:27:19 UTC,"this same problem is still present in rocky, using ceph mimic"
1713032,2017-10-20 14:01:45 UTC,Better:
1713032,2017-11-29 06:25:49 UTC,"This is not a regression. Furthermore the following link let's assume that s390x is not yet upstream supported (as well as ppc64el ?!):
https://download.ceph.com/debian-luminous/dists/xenial/
Would be good to see parity between all architectures."
1713032,2017-11-27 15:40:30 UTC,"------- Comment From <email address hidden> 2017-11-27 10:33 EDT-------
Does this problem exit on previous levels, and its a regression problem due to package upgrade, or is this a new used case...?"
1713032,2017-11-27 15:03:22 UTC,re-attaching log from bug description for external visibility
1713032,2017-10-20 16:43:38 UTC,"requested to reverse proxy this ticket, because it looks like an s390x code issue"
1713032,2017-10-20 14:51:09 UTC,To reproduce on an Ubuntu install on s390x:
1713032,2017-10-20 13:56:33 UTC,(trying again with more storage this time)
1713032,2017-10-20 13:38:28 UTC,I got a failed bootstrap with a quick test - journalctl -xe -u ceph-mon revealed:
1713032,2017-09-12 14:57:44 UTC,"This was using the openstack-on-lxd and instructions, but was not using zfs backend - it is using directory backend."
1713032,2017-09-12 14:43:34 UTC,"Can you please add the deploy/config info, such as bundle and juju status?  Is this openstack-on-lxd, or multi-lpar?"
1713032,2017-08-29 13:07:20 UTC,Just talked with Andrew and this is not a BlueStore issue.
1713032,2017-08-28 19:14:06 UTC,This may be specific to use with Ceph BlueStore.
1713032,2017-10-20 14:44:27 UTC,Confirmed on artful and xenial/pike; attached backtrace is from an artful install.
1713032,2018-03-13 15:01:17 UTC,"------- Comment From <email address hidden> 2018-03-13 10:54 EDT-------
My team don't have experience on this. I recall some folks in Germany has file system type of skills before, asking broader team might help."
1713034,2018-09-08 01:37:56 UTC,"Mh, I see them https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745"
1713034,2020-08-11 09:31:10 UTC,Looks like most of the crashes stopped happening in previous series. And the most recent one stopped happening after 3.36.0. So probably fixed?
1713034,2018-04-24 21:42:24 UTC,"Anyone getting this bug could please attach the report from
  jouralctl /usr/bin/gnome-shell"
1713034,2017-08-28 02:07:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713034,2018-03-19 01:44:51 UTC,"Tracking in:
https://errors.ubuntu.com/problem/3554ed6882d41ea6b6fe921fbc9450c857b89eaa
https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745"
1713034,2018-08-06 07:15:00 UTC,"Fix Released, apparently. Zero reports of this crash after 17.10."
1713048,2017-08-29 00:41:31 UTC,"It sounds like one of the area that may benefit from re-try logic.
However, if re-tries failed, we'd still have no public key for Identity Server and machine agent will need to be re-started..."
1713052,2017-12-05 09:16:16 UTC,"This error can be solved by adding padding-right: unset in the following file
https://docs.openstack.org/oslo.policy/latest/_static/css/bootstrap.min.css"
1713052,2017-12-05 13:48:34 UTC,"Does that completely remove the padding from the right side of all code elements? Are there any situations where we want to keep that padding? Maybe in cases where we just have a bit of code inlined in a sentence, for example? Is there some way to more specifically identify code elements in the auto-generated documentation where the layout problem exists?"
1713054,2018-05-09 16:25:36 UTC,"The problem appears to only be on the API doc pages.  The main page for oslo.policy links correctly, but the API ones don't.  The same problem exists in other projects as well, so I'm going to add openstackdocstheme to this bug since it doesn't appear to be a misconfiguration in oslo.policy itself."
1713054,2018-06-20 05:58:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576737"
1713054,2018-06-21 12:03:25 UTC,"Reviewed:  https://review.openstack.org/576737
Committed: https://git.openstack.org/cgit/openstack/openstackdocstheme/commit/?id=ae474238263524f4d970ad78faf47885defb421b
Submitter: Zuul
Branch:    master"
1713054,2018-07-25 21:39:49 UTC,This issue was fixed in the openstack/openstackdocstheme 1.21.1 release.
1713060,2020-08-21 22:58:52 UTC,"Reviewed:  https://review.opendev.org/747481
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=dd770bd2063a734441390a60b8f14ece82dda2b1
Submitter: Zuul
Branch:    master"
1713060,2017-10-26 15:40:34 UTC,Modifying network-related configuration options after manila has already created some shares using those options is not supported. Manila treats some configuration options are immutable (which is probably a bad design) and the simplest way to fix the problem is to better document which options can't be changed without causing breakage. This looks like one of those cases.
1713060,2019-10-28 19:13:04 UTC,"Has anyone taken a look at updating the docs, or looked into making the code changes to make these kinds of changed immutable and not in a config file but the DB."
1713060,2020-08-21 21:30:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/747481"
1713062,2017-10-26 15:27:42 UTC,See related nodes from Cinder PTG:
1713062,2017-10-26 15:28:02 UTC,Example of how Nova is doing it:
1713062,2017-10-26 15:28:50 UTC,"Relevant link:
https://docs.openstack.org/oslo.config/latest/reference/sphinxext.html"
1713063,2017-10-21 14:32:31 UTC,I made above changes because I notice that activities in ubuntu-gnome related ppas may not affecting directly this issue.
1713074,2017-08-25 19:25:00 UTC,Potentially a toolchain problem.
1713077,2019-06-11 03:28:49 UTC,Closing as duplicate of bug 1482823.
1713078,2017-08-25 14:42:57 UTC,"I've tested this on 3 different machines running Artful, patched up to 8am EDT on 25 August 2017. As long as I'm not running Wayland and running X, works fine."
1713078,2017-10-26 04:29:48 UTC,"Kris,"
1713078,2020-05-08 02:36:21 UTC,Cubic Experimental works in Wayland.
1713078,2020-05-31 20:14:30 UTC,Bug fixed in release version 2020.06-23.
1713085,2017-08-25 19:00:06 UTC,"The trouble with that is that users might not have write access to the main extensions directory; I certainly don't without becoming a super-user, and the whole point of a system with a package manager is that it manages all that stuff for me. If I mess with the files, and then my system tries to upgrade me to the newest Ubuntu with Inkscape 0.92, I then have a conflict I have to resolve. The whole point of having a user extensions directory is so you can install extensions without having to mess with the main installation, and extensions can be installed per-user. AIUI, this is a fairly standard model for extendable software like Inkscape."
1713085,2017-08-25 17:11:03 UTC,"Best practice here may be to suggest that user-installed extensions (if having the same name as those bundled) should be installed in the main extensions directory itself, rather than in ~/.config/inkscape/extensions/"
1713086,2017-10-22 14:43:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713089,2017-08-25 19:52:32 UTC,Compile-tested on 16.04 LTS's gcc; not tested and not even compile-tested on gcc 7.
1713090,2017-08-28 11:32:13 UTC,I'm concern if there is need change list-volume to list-volumes.
1713090,2017-08-28 12:14:51 UTC,but the metavar of [<False|True>] shouldn't be really removed.
1713094,2017-08-25 16:40:17 UTC,"I wonder about the wishlist classification. The impact if the missing dns_v4_first is imho quite severe, as lots of juju charms like to do 'apt-get update' during hook runs. With a malfunctioning maas-proxy this will hang juju units. Similarly, eg. security updates could fail to roll out."
1713094,2017-09-21 09:34:05 UTC,"IMHO a failing maas-proxy qualifies as a bug, not a feature request. But thanks for the pointer to the workaround and squid bug."
1713094,2017-09-20 15:33:57 UTC,Wishlist are feature request. These end up in the roadmap for discussion in order to get prioritized.
1713094,2017-11-27 20:30:59 UTC,It indeed seems to take some time to fail:
1713094,2017-12-20 14:44:46 UTC,"So based on the last two comments, it seems that this is an issue with squid itself, rather than MAAS."
1713094,2017-11-22 15:26:28 UTC,"Could you check how long it takes to wget/curl each of the ipv6 ips? If you don't have ipv6 configured, it usually fails immediately."
1713094,2019-04-24 13:33:19 UTC,"I'm switching this back as fix released, because this was fixed as per the milestone on 2.4.  This is a new feature, and new features are never usually backported to far advanced point releases, specially when these involve database changes such as this one."
1713094,2018-02-28 00:47:20 UTC,"Ok, so y default we will send the option as 'on' for ipv4, otherwise, users will have to disable such option to set it 'off'."
1713094,2017-12-26 11:21:54 UTC,Not sure about the implications of making ipv4 default - might just create the same effect for ppl running ipv6?
1713094,2019-03-06 17:18:41 UTC,We would need this for Maas 2.3.5 as distributed by xenial too please.
1713095,2017-10-24 12:43:39 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1713095,2017-09-25 14:27:54 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1713095,2017-08-25 16:03:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/497966"
1713095,2017-09-08 15:00:26 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/502082"
1713095,2017-09-04 17:18:44 UTC,"Reviewed:  https://review.openstack.org/497966
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=361287debf7c2cd5751517cedda8c960c5b5eb66
Submitter: Jenkins
Branch:    master"
1713095,2017-09-15 22:20:57 UTC,"Reviewed:  https://review.openstack.org/502082
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e53115da7fc10381c6f9cedcd909461e3c13c4ea
Submitter: Jenkins
Branch:    stable/pike"
1713098,2018-03-21 17:11:30 UTC,"Using this patch:
diff --git a/test/gvfs-test b/test/gvfs-test
index 4537d8a5..c82e13a8 100755
--- a/test/gvfs-test
+++ b/test/gvfs-test
@@ -278,7 +278,7 @@ class GvfsTestCase(unittest.TestCase):"
1713098,2018-03-19 20:49:29 UTC,"Unfortunately the timeout bump didn't fix the problem:
======================================================================
FAIL: test_anonymous_api_user (__main__.Ftp)
ftp:// anonymous (API with user)
----------------------------------------------------------------------
Traceback (most recent call last):
  File ""/home/gvfs-testbed-script"", line 676, in test_anonymous_api_user
    self.unmount_api(gfile)
  File ""/home/gvfs-testbed-script"", line 287, in unmount_api
    self.assertNotEqual(self.cb_result, None, 'operation timed out')
AssertionError: None == None : operation timed out"
1713098,2018-03-19 17:45:31 UTC,"I included that patch in 1.36.0-1ubuntu1 just uploaded, but I forgot to close this bug with that upload, sorry."
1713098,2018-03-19 20:50:11 UTC,"We need a way to reproduce this locally, so that we can get a shell and investigate what is going on. So far I tried locally with amd64 and i386 vms, and the tests always pass. I guess I really need a ppc64el one."
1713098,2018-03-16 20:54:10 UTC,"I don't know if the timeout is borderline short, but the unmount definitely failed. Logs further down (sorry, these logs are interleaved and have no timestamp) show that unmount failed because the filesystem was busy:
ftp: Queued new job 0x1002d932210 (GVfsJobCloseRead)
ftp: <- 0 --  226 Transfer Complete.
ftp: send_reply(0x1002d932210), failed=0 ()
ftp: backend_dbus_handler org.gtk.vfs.Mount:Unmount (pid=7819)
ftp: g_vfs_job_unmount_new request: 0x789a5002adf0
ftp: Queued new job 0x1002d93f740 (GVfsJobUnmount)
ftp: send_reply(0x1002d93f740), failed=1 (File system is busy)
ftp: send_reply(0x1002d93f740), failed=1 (File system is busy)"
1713098,2018-03-16 20:35:16 UTC,"Oh, look at that unmount_api() docstring:"
1713098,2018-03-16 20:33:49 UTC,"This is the first test that fails:
======================================================================
FAIL: test_anonymous_api_user (__main__.Ftp)
ftp:// anonymous (API with user)
----------------------------------------------------------------------
Traceback (most recent call last):
  File ""/home/gvfs-testbed-script"", line 676, in test_anonymous_api_user
    self.unmount_api(gfile)
  File ""/home/gvfs-testbed-script"", line 287, in unmount_api
    self.assertNotEqual(self.cb_result, None, 'operation timed out')
AssertionError: None == None : operation timed out"
1713098,2017-09-06 12:32:56 UTC,"The errors read like networking or concurrency breaking it.
I agree to have the bug to debug and improve the case."
1713098,2017-09-06 12:30:30 UTC,s390x and arm skip the test so all green there isn't worth anything.
1713098,2018-03-19 15:32:10 UTC,"After increasing the timeout, I ran the tests 5 times each on i386 and amd64."
1713110,2017-08-25 16:54:37 UTC,This error report is generated immediately upon startup of Zim
1713115,2018-01-22 02:48:02 UTC,Now it's up to 1.39.
1713118,2019-09-19 12:04:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1713118,2019-09-20 12:24:00 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1713120,2020-06-29 15:34:21 UTC,In progresss branch here:  https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/rogan/lp1713120_delete_acn_presufs
1713127,2017-08-31 08:28:50 UTC,Added elastic-recheck query here: https://review.openstack.org/499516
1713127,2017-08-31 08:30:38 UTC,"This is the full query to match clustercheck failures + fence-agents-all issue:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22Failed%20to%20call%20refresh%3A%20%2Fusr%2Fbin%2Fclustercheck%5C%22%20and%20message%3A%20%5C%22Error%3A%20Execution%20of%20'%2Fusr%2Fbin%2Fyum%20-d%200%20-e%200%20-y%20install%20fence-agents-all'%20returned%201%3A%20Error%20downloading%20packages%5C%22"
1713127,2017-08-30 05:24:14 UTC,Meh I think we lost the CIB collection capability in the CI when we moved to oooq? :/
1713127,2017-08-30 06:05:09 UTC,So the issue seems that the stonith-enabled=false is never set and so pacemaker does not start the db and hence clustercheck fails.
1713127,2017-08-30 06:13:03 UTC,"Oh I see the problem:
Aug 25 15:44:33 localhost os-collect-config: ""Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install fence-agents-all' returned 1: Error downloading packages:"",
Aug 25 15:44:33 localhost os-collect-config: ""Error: /Stage[main]/Pacemaker::Install/Package[fence-agents-all]/ensure: change from purged to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install fence-agents-all' returned 1: Error downloading packages:"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Service/Service[pcsd]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Corosync/User[hacluster]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Corosync/Exec[reauthenticate-across-all-nodes]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Corosync/Exec[auth-successful-across-all-nodes]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Corosync/File[etc-pacemaker]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Corosync/File[etc-pacemaker-authkey]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Corosync/Exec[Create Cluster tripleo_cluster]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Corosync/Exec[Start Cluster tripleo_cluster]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Service/Service[corosync]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Service/Service[pacemaker]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Corosync/Exec[wait-for-settle]: Dependency Package[fence-agents-all] has failures: true"",
Aug 25 15:44:33 localhost os-collect-config: ""Notice: /Stage[main]/Pacemaker::Stonith/Pacemaker::Property[Disable STONITH]/Pcmk_property[property--stonith-enabled]: Dependency Package[fence-agents-all] has failures: true"","
1713127,2017-08-28 08:55:36 UTC,"there are multiple hits reported (14 for multiple tripleo CI gates), this should be a high bug to get fixed in the pike scope"
1713136,2019-09-16 22:13:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713137,2017-08-26 06:45:22 UTC,"Reviewed:  https://review.openstack.org/383516
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=ebc1c1bc8047a3fad3f9195807b62c7d38f5768a
Submitter: Jenkins
Branch:    master"
1713137,2017-10-27 16:04:01 UTC,This issue was fixed in the openstack/os-net-config 8.0.0 release.
1713138,2017-08-25 20:16:19 UTC,http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1713138-edireader-vendcodes
1713138,2017-10-23 16:22:01 UTC,We've been running this in production for a while.  Adding pullrequest.
1713138,2020-02-12 17:41:58 UTC,"We've been running this in production for awhile, so adding my signoff."
1713138,2020-10-15 19:04:18 UTC,"Pushed to master.  Thanks, Bill and Tiffany!"
1713139,2017-08-25 19:42:04 UTC,"StacktraceTop:
 ?? ()
 g_object_new_with_custom_constructor (n_params=1, params=0x7ffd407670c0, class=0x71e28277a0) at ../../../../gobject/gobject.c:1699
 g_object_new_internal (class=class@entry=0x71e28277a0, params=params@entry=0x7ffd407670c0, n_params=n_params@entry=1) at ../../../../gobject/gobject.c:1779
 g_object_new_valist (object_type=489133717856, first_property_name=first_property_name@entry=0x7f7de4536f86 ""id"", var_args=var_args@entry=0x7ffd40767210) at ../../../../gobject/gobject.c:2104
 g_object_new (object_type=<optimized out>, first_property_name=first_property_name@entry=0x7f7de4536f86 ""id"") at ../../../../gobject/gobject.c:1624"
1713147,2017-09-02 16:47:35 UTC,Did you try to upload it?
1713147,2017-09-02 13:19:33 UTC,"I dropped shipping cacerts and used this (ie, removed files/usr/... and added 'build-packages'):
parts:
  content:
    plugin: dump
    source: files
  minecraft:
    plugin: nil
    build-packages:
    - ca-certificates
    - ca-certificates-java
    stage-packages:
    - openjdk-8-jre-headless"
1713147,2017-08-30 13:25:25 UTC,"""(Is there any reason to prefer the stage-packages version?)"" - not that I know of-- my snapcraft.yaml predates the jdk part I think."
1713147,2017-08-30 10:13:16 UTC,snapcraft needs to install packages that it requires but aren't in a standard build chroot; we can't install things like Java on the buildds for this sort of scenario.
1713147,2017-08-29 13:55:32 UTC,"Not sure about the intersection with snapcraft on the buildd, but it seems like making sure ca-certificates-java is on the host where snapcraft is being run, that should address the issue."
1713147,2017-08-29 13:53:24 UTC,"What is happening is that usr/lib/jvm/java-8-openjdk-amd64/jre/lib/security/cacerts points to a file (/etc/ssl/certs/java/cacerts) that is only generated as part of the ca-certificates-java postinst deb, and that file can't be gernerated without running the postinst from the ca-certificates deb. Snapcraft doesn't run the postinst, so that file isn't created. If the files already exist, they are used, but with 'snapcraft cleanbuild' they do not exist because the lxc container doesn't have those packages installed."
1713147,2017-08-28 05:49:03 UTC,I think it is NOT snapcraft...
1713147,2017-08-30 08:25:45 UTC,+1 :: https://bugs.launchpad.net/snapcraft/+bug/1713147/comments/3
1713147,2017-08-30 07:23:50 UTC,"  minecraft:
    plugin: nil
    stage-packages:
    - openjdk-8-jre-headless
    - ca-certificates
    - ca-certificates-java
    stage:
    - -usr/lib/jvm/java-8-openjdk-amd64/jre/lib/security/cacerts"
1713156,2017-08-25 21:41:13 UTC,"StacktraceTop:
 eina_log_print (domain=55, level=level@entry=EINA_LOG_LEVEL_DBG, file=file@entry=0xd6d45e377c ""win.c"", fnc=fnc@entry=0xd6d45e3f50 <__FUNCTION__.30958> ""_tabs_focus"", line=line@entry=2388, fmt=fmt@entry=0xd6d45e3af8 ""tc:%p tc->is_focused:%d from_parent:%d"") at lib/eina/eina_log.c:2035
 _tabs_focus (tc=0xd6d62a3d10, relative=0xd6d612d790) at win.c:2387
 _solo_focus (tc=0xd6d612d790, relative=0xd6d5ee8850) at win.c:385
 _win_focus (tc=0xd6d5ee8850, relative=0xd6d62a3d10) at win.c:858
 _solo_focus (tc=0xd6d612d790, relative=0xd6d5ee8850) at win.c:385"
1713156,2018-03-18 22:51:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713162,2017-08-31 14:06:17 UTC,Kernel panics in guests are unlikely to be Nova bugs. This is probably an underlying kvm / libvirt issue.
1713162,2017-09-27 19:55:04 UTC,Another hit in gate: http://logs.openstack.org/55/506355/3/gate/gate-tempest-dsvm-py35-ubuntu-xenial/279313c/logs/testr_results.html.gz
1713162,2019-10-23 16:29:49 UTC,Another hit in gate for an entirely unrelated devstack commit.
1713162,2019-10-23 16:40:39 UTC,"I found this after a random google. It's pretty ancient but I don't know if it's applicable.
https://bugzilla.redhat.com/show_bug.cgi?id=1175502"
1713163,2020-03-23 19:11:04 UTC,Marking as Fixed Committed as https://review.opendev.org/702808 got merged.
1713163,2020-02-28 08:01:43 UTC,"Reviewed:  https://review.opendev.org/702808
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=faa163442beca2844183f25443e3168a87dbeaa8
Submitter: Zuul
Branch:    master"
1713163,2017-08-28 06:18:52 UTC,"accordingly to avoid description, looks like this is a tempest issue?"
1713163,2018-03-27 19:22:29 UTC,"As far as I understand, this test shouldn't even exist in scope of tempest, because you can't guarantee that backend will be slow to process the request. This kind of interaction would be better served by a test with better execution flow control. I am not sure if glance have those, but in neutron realm it would be a functional test with backend persistence artificially slowed down."
1713163,2018-03-27 19:23:01 UTC,Added glance to the list of affected projects because I believe they will need to port the tempest test to somewhere else.
1713163,2018-03-27 19:23:15 UTC,The failure happened lately here: http://logs.openstack.org/45/556545/1/check/legacy-tempest-dsvm-neutron-src/7b9f588/logs/testr_results.html.gz
1713163,2018-04-02 10:47:01 UTC,"Marking as invalid for Glance.   The problem is occurring in a Compute API (nova) test.  I think your analysis is correct, that this is a timing problem and that this may be too fine-grained a test; the test should use a different success criteria."
1713163,2020-01-16 07:40:42 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/702808"
1713163,2020-06-22 08:46:08 UTC,Fix Released as the change is part of tempest 24 tag already.
1713163,2020-01-21 17:08:45 UTC,"Yeah, Tempest should not assert on timing operation or at least should not assume the operartion timing as test critria."
1713164,2020-02-18 21:18:27 UTC,This bug overlaps heavily with https://bugs.launchpad.net/evergreen/+bug/1821950.  Because of this I plan to mark this bug as a duplicate of 1821950 and put my work on a branch based off of the work on 1821950.  I hope it have it completed very soon.  My apologies for not communicating this sooner.
1713164,2020-02-18 20:29:18 UTC,"I can confirm that the ""missing call number"" warning appears under the call number box if no call number is pulled in from the bib record.
I can confirm that the ""save & exit"" button is grayed out if no call number is added."
1713164,2018-03-02 19:38:29 UTC,"Confirmed, 3.0.3"
1713164,2017-09-14 13:53:38 UTC,"Confirmed, 3.0 beta"
1713164,2017-09-13 20:47:15 UTC,"Adding a note that this only happens if adding a volume to a record that is not pulling in call number information from the bib record. In cases where the call number is automatically generated, when we clear the call number, we get a nice, visible alert telling us a call number is required."
1713164,2020-01-16 21:47:52 UTC,I pushed a branch with a fix. Now when you add a new copy the editor highlights that it's missing a call number and won't let you save til you add one.
1713174,2017-08-28 01:20:36 UTC,I've uninstalled 16.04 because I've realized that LTS is just a silly sticker meaning nothing practical: people from IRC (#kde) couldn't provide any help because they're basically don't use such an old Plasma desktop which is shipped with 16.04 - it is about two years old.
1713175,2017-09-28 20:05:16 UTC,My intention was to attempt to recover a filesystem. It just happened to be the wrong block device on which there was a functioning LUKS partition.
1713175,2017-08-26 21:54:10 UTC,"Ah, well, the whole thing is more of a stupid lesson learned."
1713175,2017-09-28 13:10:18 UTC,"I have to disagree; the only tool that uses the backup superblock is e2fsck, and if you accidentally run wipefs on the volume, you should be able to recover it with e2fsck."
1713175,2017-08-26 20:31:32 UTC,"You are correct, not running atleast wipefs before using luksFormat on the block device was a mistake on my part, but I barely remember making it. I half expected fsck to come up with some errors, so I let it make changes. It is not a volume that is always connected at startup, hence the manual check. It was just the wrong block device. An isLuks check would have returned yes and prevented fsck from running. Maybe libblkid could detect luks partitions?"
1713175,2017-08-26 15:18:07 UTC,"One day cryptsetup will link to liblkid, adding two ""use friendly"" things in luksFormat
- warn if it detects something on disk before destroying it
- run wipefs to really destroy all the magic strings there (as Teo suggested)"
1713175,2017-08-26 14:42:45 UTC,"Note: I think this should be a low-priority/wishlist/feature request.  But I can't edit the importance.    It is a valid feature request though, so I plan to treat it at that priority."
1713175,2017-08-26 21:23:39 UTC,FYI libblkid/blkid detects LUKS for years already.
1713175,2017-08-26 14:40:05 UTC,"So what happened is the following.   There was a previous ext4 file system on the disk.  You ran ""cryptsetup luksFormat /dev/sda1"" which wiped out the primary superblock."
1713189,2017-08-29 19:59:10 UTC,has nothing to do with xorg?
1713190,2017-12-18 20:39:15 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.openstack.org/498141
Reason: Feel free to restore this patch if it is need. Abandoning per our policy https://docs.openstack.org/puppet-openstack-guide/latest/contributor/reviews.html#abandonment"
1713201,2019-05-07 20:33:47 UTC,Is there any fix for this?
1713209,2018-02-14 17:21:17 UTC,@Fredrik: is this still an issue with the released 17.10 ? Or in the upcoming 18.04 ?
1713209,2018-02-15 10:15:53 UTC,"No at least not in 18.04, 17.10 i wouldn't know, but I had the same problem in the beginning of 18.04 but it seams to have resolved it self :D"
1713219,2020-05-28 10:46:26 UTC,I'm not going to add a second independent reader to apt just so that apt-mark runs a bit faster.
1713219,2020-05-28 10:45:15 UTC,The problem is that the code that reads the state reads it into the depcache.
1713219,2020-05-15 20:14:11 UTC,"Well, I think it is not a problem, if we do not need depcache here :)"
1713219,2017-09-09 20:07:08 UTC,"Two problems: (1) depcache opening is slow (2) we don't really need the depcache here. Anyway, triaged, but low importance."
1713219,2017-08-26 12:33:14 UTC,"It first builds or opens the cache, then the depcache, which reads extended_states. Just reading extended_states may be inaccurate."
1713219,2017-08-26 12:15:44 UTC,"Do you say information about automatically installed packages can not be read from /var/lib/apt/extended_states (or whatever file set in configuration variable Dir::State::extended_states)? If I install something by apt, I see modification time of /var/lib/apt/extended_states about 1 sec later than /var/log/apt/term.log"
1713219,2017-08-26 10:21:55 UTC,"Everything in apt uses the cache and that has to be generated. Plus the depcache, I guess."
1713221,2017-09-24 14:38:53 UTC,Swedish also missing
1713221,2017-09-24 14:39:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713221,2017-09-24 14:40:07 UTC,is running Artful just like OP
1713224,2018-08-18 18:04:39 UTC,I do not see that notification in Xubuntu 18.04.
1713224,2018-08-18 18:07:27 UTC,"Also, please forward any potential patch to the Xfce bug tracker. Thanks."
1713224,2018-11-09 04:17:30 UTC,[Expired for xfce4-power-manager (Ubuntu) because there has been no activity for 60 days.]
1713224,2018-11-15 12:53:25 UTC,https://bugzilla.xfce.org/show_bug.cgi?id=12317#c4
1713226,2017-10-02 20:28:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713226,2017-08-30 15:48:51 UTC,"Here are the files of the networkmanager systemd-networkd conflict (I already removed ifupdown, the problem is the same, so we say for sure networkmanager or systemd-networkd causes the problem)"
1713226,2017-08-30 15:57:01 UTC,The example 2 in my first posting is not an bug since the package contains /lib/systemd/network/80-container-host0.network. As I wrote this only affects systemd-nspawn containers
1713226,2017-08-29 22:10:19 UTC,@msaxl
1713226,2017-08-29 11:58:25 UTC,"this was a upgrade so the ifupdown problem should not happen with clean installs.
How is the migration planned?"
1713226,2017-08-29 12:36:17 UTC,"Steve,"
1713226,2017-08-29 22:10:48 UTC,"also, we got new network-manager in artful which may have regressed."
1713226,2017-08-29 11:13:28 UTC,Is this on upgrades to artful? or clean-install / clean-bring up of artful?
1713227,2018-10-06 04:29:32 UTC,"It sucks that I can't create a workflow where I have everything the way I want it
for fast working, but the thing is Inkscape has a saver for it, but it just does
not save it. I could use floaters, but it looks so unprofessional to use a bulky
window in different positions. I want to at least have the freedom of making a
custom default workspace for speed like a save workspace setting in Blender and
Krita, and a theme maker would also be pretty cool :)."
1713227,2018-09-17 07:12:33 UTC,"I just found a workaround for my problem. If I use floating windows instead of dockable windows, Inkscape after restart remembers the position of windows on my second screen. I can live with that..."
1713227,2019-12-11 04:22:58 UTC,Migrated to:  https://gitlab.com/inkscape/inbox/issues/1356
1713227,2018-08-26 18:33:47 UTC,Same problem on Arch Linux. Every time I open document I need to expand xml editor by x/y-axis because it always collapsed to unusable small dialog. Usually I keep opened only xml editor and all dialogs I open in right dock.
1713227,2018-03-05 18:26:52 UTC,(I am pressing F12 for hide and unhide dialogs)
1713227,2018-03-05 18:23:59 UTC,"I have the same problem in kubuntu and ubuntu 17.04.
Inkscape version:0.92.2 (5c3e80d, 2017-08-06)
here a sample:
https://youtu.be/OC5w3zRard4"
1713227,2018-09-17 06:41:09 UTC,"I can report the same problem on windows 10. I'm using two screens and it is really convenient, that I can dock dialogs on the second window and use the primary window for drawing, but as reported, I need to arrange dialogs every time when I open Inkscape... hopefully this can be solved by smart Inkscape developers soon :)"
1713233,2017-09-14 09:26:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713238,2020-01-16 20:46:37 UTC,Yes I'm positive: gufw works here on my Wayland session.
1713238,2019-07-20 18:34:24 UTC,"Running Ubuntu 19.04
After noticed GSConnect stopped working, I've tried launch GUFW to disable fw,
but even after request password, didn't show any screen for GUFW.
From terminal, it gives segmentation fault.
After trying this answer from AskUbuntu, it came back to work."
1713238,2019-12-01 12:25:08 UTC,"It seems to be working now on 19.10, indeed."
1713238,2020-01-16 13:12:52 UTC,"Great! Can someone else confirm this and close this ticket as ""Fix Released""?"
1713238,2019-06-19 09:52:18 UTC,Is this still an issue on latest Ubuntu?
1713238,2020-01-16 18:04:53 UTC,"Although gufw works in Ubuntu 19.10 by default, I'm not sure that 19.10 uses wayland like (I've read) 20.04 will. Those who confirm this works, really need to make sure you're logged in using Wayland and not X."
1713238,2020-01-19 09:55:42 UTC,"Hi, Franck could you send me the content of this file? Thanks."
1713238,2020-01-23 18:13:20 UTC,"Uhm, @Frank This should not work with Wayland :O
Are working other programs as gparted or synaptic?
Thanks in advance!
--
Costales."
1713238,2020-01-21 20:13:21 UTC,"Hi,"
1713238,2020-01-22 19:34:10 UTC,cat: /bin/gufw: No such file or directory
1713238,2020-01-22 20:09:26 UTC,"Yes, that was my previous comment:"
1713238,2020-02-03 18:58:21 UTC,I'm having the same issue on Ubuntu 18.04.
1713238,2020-05-27 17:21:20 UTC,"Hi,
Could you try this package from focal?
http://mirrors.kernel.org/ubuntu/pool/universe/g/gui-ufw/gufw_20.04.1-1_all.deb
It should works fine in other versions.
Thanks.
--
Costales."
1713238,2020-09-12 07:05:26 UTC,Deprecated release
1713238,2019-02-12 16:45:37 UTC,Wayland is planned to be default Ubuntu Desktop session from 20.04 LTS. This should be fixed quickly.
1713238,2020-01-21 19:59:54 UTC,Sure. Here it is (from /usr/bin although):
1713238,2018-03-17 06:59:17 UTC,The problem is that wayland as a security measure *either* gives you access to the display server *or* to root => the interactive part of gufw needs to be running with the user account and the small portions root privilleges are needed for need to be run by policykit. Which is a good idea - but which synaptic and gufw currently fail to do.
1713238,2020-01-22 19:49:02 UTC,"Hi,
My fault, please, this path:
cat /usr/bin/gufw*
Thanks"
1713238,2018-02-09 13:02:38 UTC,"Yep, but it still should be fixed so users could switch to Wayland without having any issues in the future."
1713238,2018-02-09 14:08:39 UTC,@asciiwolf: I wish this interface allowed me to upvote posts like yours.
1713238,2017-08-26 14:01:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713238,2017-08-26 15:04:41 UTC,"If I remember correctly, this app used to have proper PolicyKit implementation but it was replaced by pkexec. GNOME Shell does not currently support pkexec."
1713238,2017-08-26 15:13:35 UTC,It works just fine with GNOME SHELL.
1713238,2017-08-26 15:18:06 UTC,It works just fine with GNOME SHELL.
1713238,2017-08-26 15:19:57 UTC,#append#
1713238,2017-08-26 15:28:10 UTC,"Hi, is this a wayland issue then? Is it working gparted? Thanks in advance.
Best regards."
1713238,2017-08-26 16:02:39 UTC,Yes. Wayland issue. gparted works fine in gnome-shell. Calls policykit for authentication .. etc..
1713238,2017-08-26 17:11:29 UTC,"I didn't like politykit in the past, so so so complicate to debug. I
migrated Gufw looking into the Gparted code."
1713238,2019-11-30 21:36:18 UTC,"Hmm, do you have the same issue on latest Ubuntu 19.10?"
1713238,2017-08-27 10:46:44 UTC,"Yes, gparted does not work with the default Ubuntu 17.10 session since Ubuntu is now using GNOME on Wayland."
1713238,2017-08-27 09:52:13 UTC,"It is important to have this working by release day for 17.10 We will be testing wayland hard during 18.04 cycle and we need a graphical firewall. It makes it hard to recruit new testers when synaptic,gufw and gparted are not working nativley in wayland when thy should be."
1713238,2018-01-25 21:28:39 UTC,The same problem here.
1713238,2018-01-06 16:12:43 UTC,"I am glad they  marked it up critical, especially in light of Specter/Meltdown exloitables. Not sure if gufw would do any good anyways , but at least it is one layer of security."
1713238,2018-01-06 02:06:18 UTC,Still not fixed.
1713238,2018-01-28 00:31:28 UTC,Since xorg is now the new default the wayland/gnome devs can take a breather. So can the rest of us.
1713238,2017-09-30 19:19:31 UTC,For you information - here is a list of all affected pkexec'ed applications - see bug 1713313 .
1713238,2017-08-27 11:18:41 UTC,"@costales,"
1713238,2017-09-30 19:20:59 UTC,And also we have a list of gksu/gksudo applications here - see bug 1713311 .
1713238,2017-08-27 11:01:50 UTC,Thanks!
1713239,2018-09-20 08:57:05 UTC,PR against 2.3: https://github.com/juju/juju/pull/9235
1713239,2018-09-12 13:29:51 UTC,"I've added the Juju project to this bug because in order to support requesting for a partition (via tag, and similarly to how we do it for block devices), Juju would need to be changed to correctly interpret this request."
1713239,2018-09-11 15:09:15 UTC,"No it will not fallback to searching for a partition, when a block device cannot be found to match that tag, but a partition does exist. That would create undetermined behavior to the charm and the deployer of the charm."
1713239,2018-09-13 13:39:37 UTC,This pull request for gomaasapi adds the support for handling partitions in the allocation constraint map response.
1713239,2018-09-10 20:18:33 UTC,Working on this now and some things have to be changed with how the constraints will work with a partition.
1713239,2018-08-07 14:55:07 UTC,re #2:
1713239,2018-08-07 14:11:07 UTC,"Blake came out with a good solution, where MAAS would add pseudo/inherited tag based on whether it is a partition or a block device. So all of this would work:"
1713239,2018-09-11 08:04:20 UTC,It seems reasonable that there should be a separate tag in the query.
1713239,2018-08-07 14:04:09 UTC,"Hi Dmitrii,"
1713241,2017-08-26 16:58:31 UTC,I already got Wifi drivers installed.
1713241,2017-08-26 15:57:34 UTC,"There is no module loaded for your wifi, what have you done to try to fix this?"
1713242,2021-01-10 22:11:08 UTC,Ubuntu 14.04 is past end of life.
1713242,2021-01-26 10:55:08 UTC,"Oh, but user is not guided to use debian for bug reporting beforehand, but to use launchpad.net:"
1713242,2020-04-12 10:50:08 UTC,An example of an application in which this is annoying is linux-purge (https://launchpad.net/linux-purge)
1713242,2021-01-26 11:54:26 UTC,Could you be more specific about where to discuss this in Debian?
1713266,2017-08-30 18:06:06 UTC,Reproducible on artful.
1713274,2017-08-29 20:34:05 UTC,"Triage notes: I don't know if there are implications when installing the ""menu"" package in a desktop system nowadays. I also don't know why the provided su-to-zenmap.sh was dropped, since it says it was based on debian's su-to-root to begin with."
1713276,2017-10-04 14:18:31 UTC,"The file you linked to does not contain any license information, without that we cannot incorporate it into Ubuntu. In searching I can't find specific information about which firmware version has the fix, but even the RPi-Distro github trees do not seem to have been updated. So I haven't been able to find an updated version of the firmware that we will be able to distribute."
1713276,2018-02-07 13:17:03 UTC,New firmware https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=203508
1713276,2018-02-09 13:45:00 UTC,"Sorry, same problem as before. There's still no license information, and without that we cannot know if we are allowed to redistribute the firmware."
1713276,2018-10-23 12:13:28 UTC,I guess this is fixed in 18.10 due to new firmware files.
1713279,2020-12-21 07:29:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713290,2018-05-08 18:10:19 UTC,Workaround: Reinstall without any wireless USB keyboard connected.
1713290,2018-05-08 18:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1713290,2018-05-08 18:51:17 UTC,"not possible to run apport-collect, already reinstalled."
1713310,2020-08-16 14:25:34 UTC,"NOT FIXED (should be labeled invalid, at least that's how I mark migrations per https://alpha.inkscape.org/bug-migration/)."
1713310,2017-08-27 11:55:01 UTC,"running Windows XP, and Inkscape 0.92.x branch, compiled Aug 7, I get the backtrace:"
1713310,2017-08-27 11:34:17 UTC,"- confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)
- no error messages are generated in DOS"
1713310,2020-08-16 13:23:11 UTC,Closing as fixed in 1.0. Thanks for reporting!
1713311,2017-08-27 13:12:21 UTC,Wayland does not support root applications by design.
1713311,2018-09-06 23:12:26 UTC,su-to-root apparently still works (for those who know about its existence)
1713311,2018-09-06 23:10:01 UTC,setting to critical for gadmin-proftpd as it renders the package useless in bionic.
1713311,2018-06-02 04:18:47 UTC,@kravemir It does not have to be a long running process. Just give it a short timeout like 10s. D-Bus/systemd will take care of starting new daemons when new requests come in.
1713311,2018-06-01 21:31:44 UTC,"In unreleased version, HW access will be performed via D-Bus daemon. No need to run ddccontrol/gddccontrol with root privileges. See https://github.com/ddccontrol/ddccontrol/blob/master/CHANGELOG.md"
1713311,2018-03-23 13:41:52 UTC,"I have just uploaded Bleachbit 2.0-2 to the Debian archive, switching from su-to-root to policykit. This will fix the issue."
1713311,2017-12-31 18:04:04 UTC,This bug was fixed in the package hannah-foo2zjs - 1:3
1713311,2017-12-03 11:44:06 UTC,"I have just installed i7z and i7z-gui packages on Ubuntu 16.04.3 LTS. i7z_GUI requires root privileges, so it seems to be affected by this bug on newer Ubuntu."
1713311,2017-12-01 19:07:29 UTC,"pkexec does not work under wayland either, so that change does not fix the issue."
1713311,2017-11-16 15:30:59 UTC,"I can't comment whether it's really fixed, though, if it's not, well, I'm sorry and please reopen."
1713311,2017-11-16 15:29:48 UTC,It does in an earlier entry that was skipped in the fake changes somehow:
1713311,2017-11-16 14:36:41 UTC,WTF Launchpad?  That changelog does not say it fixes this bug.
1713311,2017-11-03 00:50:55 UTC,This bug was fixed in the package gsmartcontrol - 1.1.1-1
1713311,2017-10-21 14:10:25 UTC,At least `zenmap` and `wifi-radar` do not run on default fresh clean installation of Ubuntu 17.10.
1713311,2017-09-29 14:28:32 UTC,@Norbert
1713311,2017-08-27 20:10:46 UTC,We are currently in the process of removing dependency on gksu from Ubuntu MATE. caja-gksu is not longer seeded in Ubuntu MATE and will soon be removed from the Debian and Ubuntu archives. caja-admin will be replacing caja-gksu.
1713311,2017-08-27 13:31:58 UTC,"And what should users do if Wayland may become new GNOME standard?
Is it possible to replace su-to-root with pkexec?
20 applications are affected. They are popular. On Wayland they are useless. Great to hear."
1713311,2017-08-27 13:38:22 UTC,@Norbert
1713311,2017-08-27 13:52:41 UTC,"Generally speaking, all (Wayland-capable) apps that currently run their UI as root need to be restructured to use PolicyKit for the privileged operations, and have the UI run as a normal user."
1713311,2017-08-27 13:53:19 UTC,@dino99 packagekit has nothing to do with this. pk means policykit in this context.
1713311,2017-08-27 14:05:48 UTC,@Julian
1713311,2017-09-29 11:37:46 UTC,"Ubuntu 17.10 with all updates, bug is not fixed."
1713311,2017-08-27 15:47:20 UTC,"@dino99
Thanks! So I dig deeper."
1713311,2017-08-27 16:00:18 UTC,"Grepping rdepends of gksu for gksu gives `caja-gksu`, `ltsp-live`, `gddccontrol`."
1713311,2017-08-27 16:04:00 UTC,+ `spacefm-gtk3` to c10
1713311,2017-08-27 16:49:01 UTC,"BleachBit 1.17 (beta) switched from su-to-root (from the menu package) to pkexec, and I hope to soon release it as BleachBit 2.0 (final). This may resolve this issue too."
1713311,2017-08-27 17:25:03 UTC,Here is my simple script for grepping su-to-root|gksu|pkexec inside application.desktop files in packages.
1713311,2017-08-27 19:05:45 UTC,Is caja-extensions listed here because of caja-gksu?
1713311,2017-08-27 19:34:33 UTC,+c15
1713311,2017-08-27 15:54:57 UTC,"Grepping rdepends of gksu for su-to-root gives `guymager`, `hannah-foo2zjs`, `zenmap`"
1713311,2017-08-27 19:19:34 UTC,"@Martin Wimpress (flexiondotorg)
yes, because of caja-gksu. It does not work under Wayland."
1713313,2017-08-27 11:49:17 UTC,"This a well known wayland limitation.
The workaround (till the pkexec -> policykit transition is made) is to use xhost script.
Gparted already has an opened bug: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1652282
and policykit has to be used, but is not directly concerned as a bug."
1713313,2017-08-27 13:34:24 UTC,"@dino99
for me it seems that this"
1713313,2017-08-27 20:23:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713313,2017-08-27 16:20:25 UTC,"What is interesting `gnome-system-log` depends on `policykit-1`, it has `gnome-system-log-pkexec`, but it works without xhost command!"
1713313,2017-12-08 15:33:31 UTC,Please could both of you take a deep breath and stop the personal attacks and aggressive language?
1713313,2017-12-08 18:28:31 UTC,"Speaking as a member of the Ubuntu Community Council, I'm going to have to ask that we dial down the tone here. As you know, the Code of Conduct (https://www.ubuntu.com/about/about-ubuntu/conduct) means that we should act with respect and consideration, act collaboratively and work towards consensus and clarity. That's sadly not what I'm seeing in this discussion and we need to put an end to it."
1713313,2017-12-08 18:38:16 UTC,"I did not start the personal attacks, I did not reply until you all allowed
his comment to stand for a full 24 hours, and I already apologized for my
posts. However, I will not allow psusi to bully me on launchpad either. If
he posts personal attacks here I will defend myself."
1713313,2017-12-08 18:49:01 UTC,"Frankly, his first post is not only wrong regarding wayland, but it is also
a clear violation of the Ubuntu code of conduct."
1713313,2017-12-08 19:16:10 UTC,"Again: let's keep any further discussion about people directed towards <email address hidden> and let's keep the bug report for talking about the actual software. In other words, no more comments about the CoC violations in this bug report. Let's get back to talking about the software."
1713313,2017-12-08 20:34:50 UTC,I'm wontfixing the gdm3 component. See LP: #1652282
1713313,2017-12-09 01:51:53 UTC,"Folks, let's all calm down a bit and try to cooperate..."
1713313,2017-08-27 17:26:29 UTC,For those who interested I post my simple script for grepping su-to-root|gksu|pkexec inside application.desktop files in packages here - https://bugs.launchpad.net/ubuntu/+source/gadmin-samba/+bug/1713311/comments/13 .
1713313,2017-12-11 18:50:28 UTC,"On 12/7/2017 8:15 PM, bodhi.zazen wrote:

> Wayland , upstream, does not and will not support running graphical
> applications, as root, from the terminal using sudo , period, end of story.
> There are other mechanisms to grant graphical applications root access, but
> again the application itself is not going to run as root.
"
1713313,2017-12-11 21:53:01 UTC,"We need to talk about software here, not personal issues. You both are going to stop attacking each other, defending yourself against each other, and talk about software. If you cannot talk about the software without getting these other issues intermingled here, do not comment at all."
1713313,2017-12-13 04:36:20 UTC,Phillip:
1713313,2018-01-09 17:39:13 UTC,"Problem with `nemo` ""Open as Root"" is confirmed on 18.04."
1713313,2018-01-09 17:41:41 UTC,synaptic confirmed on 18.04.
1713313,2018-08-05 16:16:07 UTC,Gui no longer run su
1713313,2018-08-06 16:57:08 UTC,This isn't a bug but a major feature of wayland: If you have root rights you no more get access to the graphical user interface which makes it harder for a gui application to spy on another application's keyboard input. The backdraw of this is that every application that needs root rights for its work has to be re-written to have 2 parts:
1713313,2018-08-09 12:18:33 UTC,"Are there any plans to move forward and try to coordinate applications rewrite/adaptation ?
I'm not in love with wayland, but isolating graphical applications for each other seems a legitimate concern (see https://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolation.html for example)."
1713313,2018-08-09 13:10:46 UTC,"> Now that Ubuntu has given up on Wayland by default
"
1713313,2018-08-09 14:05:38 UTC,"Franck, I liked your post, because I think you addressed a serious issue. As Joanna R. (Invisible Things Lab) pointed out repeatedly, X is not secure by design."
1713313,2018-08-09 15:48:21 UTC,At scanmem/GameConqueror we handle this like GParted. Setting this to invalid as no other security model fits our need. Btw.: OpenSUSE Leap 15 managed to provide Wayland with proper pkexec permissions so that GameConqueror runs unchanged on Wayland.
1713313,2018-08-10 12:14:48 UTC,"@aquina I was just pointing ufw vs firewalld as it is the app (gufw) that drove me here. I also wanted to point out that by adopting Gnome / Systemd / Wayland / ... Ubuntu is now dependant and has to keep up with the new upstream, that tends to be RedHat / Fedora."
1713313,2018-08-15 14:55:23 UTC,"On 8/6/2018 12:57 PM, PeterPall wrote:

> This isn't a bug but a major feature of wayland: If you have root rights
> you no more get access to the graphical user interface which makes it
> harder for a gui application to spy on another application's keyboard
> input. The backdraw of this is that every application that needs root
> rights for its work has to be re-written to have 2 parts:
"
1713313,2018-08-15 15:46:02 UTC,Phillip: I don't know why they even allow you to speak on this thread. Please stop spreading misinformation .
1713313,2018-08-20 15:21:04 UTC,"On 8/15/2018 11:46 AM, bodhi.zazen wrote:

> Phillip: I don't know why they even allow you to speak on this thread.
> Please stop spreading misinformation .
"
1713313,2018-08-20 15:40:28 UTC,"Phillip and bodhi, I know this is something we have discussed before, but I'm going to say it again and hopefully for the last time: please keep your comments civil. You can disagree with each other all you want, but do it respectfully, please. If you see yourself using the word ""you"" (or if it's implied) in a comment, that's a sign you're probably doing something wrong."
1713313,2018-09-10 05:09:15 UTC,"@Walter Lapchynski (wxl) please have the technical board review the bullshit Phillip Susi (psusi) posts here and then ask him to stop. Until then, leave me alone and do not include me in your moderation."
1713313,2018-09-10 17:05:37 UTC,"bodhi, having the Technical Board review Phillip's posts might be completely reasonable so as to finally end this conversation once and for all. That has no bearing on the moderation, though."
1713313,2019-05-01 09:26:07 UTC,"Hi,"
1713313,2019-05-01 18:48:51 UTC,costales writes:
1713313,2017-08-27 14:57:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713313,2017-12-08 15:19:48 UTC,Because lanuchpad clips comments I am re-posting so it does not so easily get lost
1713313,2017-12-08 15:13:43 UTC,"First, let me say, I apologize for the tone of my last post."
1713313,2017-08-27 20:16:37 UTC,Gdebi is affected too. Unable to install package with it:
1713313,2017-12-06 14:11:21 UTC,"Excuse my language Bodhi, but bull shit.  You actually can run wayland apps as root just fine.  It is only X11 apps running under wayland that no longer run as root, and the reason is simply that gdm3 fails to configure Xwayland with a proper Xauthority policy, the way its man page says it should.  It isn't doing what its documentation says it should, so it's a bug."
1713313,2017-12-08 01:15:28 UTC,"Obviously Phillip you are shooting off your foul mouth without knowing a
dammed thing you are talking about. It is obvious from your comments you
know nothing about wayland or wayland security and that you are just
spewing shit on the bug report."
1713313,2017-08-27 21:48:19 UTC,Many other packages are affected via /usr/share/polkit-1/actions/*.policy files with these xml-rules:
1713313,2017-08-27 21:59:25 UTC,"And finally with `apt-file search pkexec | grep ""pkexec$""`"
1713313,2017-08-27 22:21:27 UTC,"Here is my simple script for grepping ""<allow_any>auth_admin</allow_any>
      <allow_inactive>auth_admin</allow_inactive>
      <allow_active>auth_admin</allow_active>
    <annotate key=""org.freedesktop.policykit.exec.allow_gui"">true</annotate>"" inside /usr/share/polkit-1/actions/*.policy files in packages."
1713313,2017-09-04 14:11:56 UTC,"I don't get where is the problem, wayland or all the applications using policykit?"
1713313,2017-09-04 14:32:30 UTC,@LOB
1713313,2017-09-04 15:23:28 UTC,the question is more tricky
1713313,2017-09-04 20:44:25 UTC,"Greetings,
two of my projects are on the list(SiriKali and zuluCrypt) and latest versions of these projects are not affected by the problem."
1713313,2017-09-05 05:54:54 UTC,The Python/GTK3 GUI GameConqueror uses libscanmem for memory scanning with /proc/$pid/mem or ptrace(). Root privileges are required because of the Yama security module and its ptrace_scope set to 1.
1713313,2017-09-29 12:03:54 UTC,"Looks like all the required work will wait for 18.04, both Debian & Ubuntu have not started working around the pkexec problem not working with wayland."
1713313,2017-09-29 12:30:55 UTC,"@dino99
I understand that we talk about security here."
1713313,2017-09-29 14:26:58 UTC,@Norbert
1713313,2017-09-30 18:25:27 UTC,Budgie welcome in its current form will never be run on a Wayland session. Marked as invalid
1713313,2017-09-30 18:35:38 UTC,"Gufw is really affected.
See below:"
1713313,2017-09-29 11:35:20 UTC,"Ubuntu 17.10 with all updates, Synaptic still does not start from Wayland."
1713313,2017-09-30 19:18:07 UTC,"@Jeremy Bicha (jbicha)
As you may know I created script for automation - see my comment #20 https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1713313/comments/20 ). And I collected all found problems here."
1713313,2017-09-30 19:34:34 UTC,It doesn't make sense to run cinnamon inside GNOME on Wayland.
1713313,2017-09-30 19:35:59 UTC,"@Jeremy Bicha (jbicha)
FYI on other similar bug report dino99 was pleasant about one big bug report (see his comment - https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1713311/comments/4 ). So we can choose this bug-report style here too."
1713313,2017-09-30 19:36:30 UTC,This appears to be a false positive.
1713313,2017-10-12 13:21:54 UTC,The wayland package just needs to change its absurd default security policy back to the one that X has used.
1713313,2017-11-23 18:38:11 UTC,Y PPA Manager seems to be affected because of 'auth_admin' in /usr/share/polkit-1/actions/org.freedesktop.pkexec.y-ppa-manager.policy .
1713313,2017-10-17 02:43:23 UTC,"Source: zulucrypt
Source-Version: 5.2.0-2"
1713313,2017-10-19 13:10:10 UTC,Raised https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1724748 which I think is actually a dup of this existing bug.  Here's what I'm seeing:
1713313,2017-10-19 13:37:51 UTC,Please do not use sudo to run gedit. Just use admin:/// URIs.
1713313,2017-10-19 15:46:34 UTC,"Right, it's just an example.  Replace with `sudo virt-manager` equally."
1713313,2017-10-21 13:56:43 UTC,At least `gparted` and `synaptic` do not run on default fresh clean installation of Ubuntu 17.10.
1713313,2017-10-21 16:25:48 UTC,"On Sat, 21 Oct 2017, Norbert wrote:

> At least `gparted` and `synaptic` do not run on default fresh clean
> installation of Ubuntu 17.10.


And as standard software installer does not:
a) pass on querries from the package install (so that jackd can be
properly installed for example)
b) does not alert the user that a package they are installing has to
remove another package the user still needs. This can leave the user with
a crippled system."
1713313,2017-10-22 17:31:16 UTC,"Just a heads up, you do understand that this is a feature , not a bug ?"
1713313,2017-09-30 18:50:58 UTC,"Norbert, yes but the package name was wrong. There already is LP: #1713238"
1713313,2017-11-07 16:14:51 UTC,https://bugs.launchpad.net/ubuntu/+source/sirikali/+bug/1713313/comments/24
1713317,2017-08-27 12:04:07 UTC,This affects both the installed documentation and the online documentation:
1713331,2017-10-01 16:40:03 UTC,"Still not possible to update the language. I've got a part in French and a part in English (not very clean)!!
as of today october the 1st 2017 after update and upgrade"
1713331,2017-08-28 21:34:14 UTC,"Same issue w/ another laptop more recent (2016) and more powerful i5-6200,
RAM = 4 Go.
And also 64 bits EFI instead of 32 bits MBR."
1713331,2017-09-26 08:01:16 UTC,No change as of today
1713339,2017-08-27 16:21:00 UTC,"The attachment ""a few ported patches"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1713348,2017-09-01 04:17:38 UTC,"> If you have a kernel image package say linux-image-4.9.0-test,
> you may have have a header package linux-headers-4.9.0
> (without the '-test' part) or some other similarly named package, right?
"
1713348,2017-09-02 14:55:25 UTC,"> It should not error exit now
"
1713348,2017-09-02 04:53:41 UTC,"It should not error exit now, but I suppose it will not purge 4.9.0-test, if you do not choose to purge 4.9.0-test-test. Is that a problem? If it is, the current logic of removing unneeded dependencies can not be applied."
1713348,2017-09-01 23:45:39 UTC,"Works well. Thanks.
I did (on test clone VM):
0.) Remove gawk package, so only mawk is still there.
1.) Don't select anything. Observe it clean up a previous partially uninstalled kernel.
2.) Don't select anything again. It exited with an error, I guess because nothing was selected.
3.) Remove a lowlatency kernel, but keep the same one generic.
4.) Remove another Ubuntu kernel."
1713348,2017-09-01 20:30:44 UTC,"I try to protect e.g. reserve depending header packages from being purged and it works fine with usual kernel; if I want to keep linux-headers-4.4.0-92-generic, I should keep linux-headers-4.4.0-92 even if I am going to purge linux-headers-4.4.0-92-lowlatency (i.e. respective header package with different flavor).  Maybe I can not rely on package naming generally; I hope there is some naming convention I can rely on. Anyway, I pushed some changes that aim to make the script work better with your development kernels and also work better with mawk as awk alternative, and display checklist better in debug mode."
1713348,2017-09-01 14:44:23 UTC,"Could you attach output of
dpkg-query -W -f='${Status} ${Package} ${Depends}\n' linux-headers-'*'"
1713348,2017-09-01 03:36:32 UTC,"If you have a kernel image package say linux-image-4.9.0-test, you may have have a header package linux-headers-4.9.0 (without the '-test' part) or some other similarly named package, right?"
1713348,2017-08-29 21:52:35 UTC,Now most kernels are not listed at all.
1713348,2017-08-30 15:13:15 UTC,"I installed the problem kernels on my master VM, and then re-cloned my test VMs.
I get the same issue, which eliminates anything to do with them having been deleted and re-installed, because they have never been previously installed on the VM."
1713348,2017-08-29 23:53:21 UTC,"For comment #9 above: It turns out that the kernels are there in the menu list, if one scrolls down. It is just, for whatever reason, the menu now only shows 4 kernels at a time."
1713348,2017-08-30 22:52:21 UTC,"The following additional testes were done:
1.) checkout my old kernel 4.9 branch and compile, using the same kernel configuration file from back then. It seems to want to delete that kernel also. (4.9.0-test)
2.) Observing that all the kernels it seems to want to delete have names with 4.N.0-string and all the others have names with 4.N.0-string-string, then re-compile kernel 4.9 again but call it -test-test (4.9.0-test-test). Not only did the script not want to purge that kernel without me asking for it, it also no longer wanted to purge 4.9.0-test."
1713348,2017-08-29 19:34:34 UTC,Please pull the latest from git and run the command with new --debug option and attach the generated file.
1713348,2017-08-28 14:32:24 UTC,"I manually un-installed kernel 4.13.0-rc2-doug2 and then re-installed it. No problem.
I used the rm-kernels-server script (from askubuntu.com) to un-install 4.13.0-rc2-doug2 and then re-installed it. No Problem."
1713348,2017-08-27 21:24:59 UTC,The only thing I can think of that might be different with those 4 kernels is that I might have purged them before and subsequently re-installed them. I'll do some tests based on this idea.
1713348,2017-08-27 19:17:03 UTC,"> BTW I wonder why the lines in your screenshot are drawn as letters.
> It does not happen in my system, and locale is reset by 'export LC_ALL=C' in the script.
"
1713348,2017-08-27 17:46:15 UTC,Notice that I did not ask it to delete 4 of the 5 kernels it seems to want to purge.
1713348,2017-08-27 18:53:00 UTC,"Could you attach the output of command
dpkg-query -W -f='${db:Status-Abbrev} ${Package}\n' linux-'*'
in the system you ran the simulation in."
1713361,2017-08-27 20:19:00 UTC,Thanks for reporting.
1713374,2017-08-27 23:20:15 UTC,"I actually had Ubuntu with unity, but that had a bug that opened photo search, and nobody could solve it, as I was the only one, as it appears."
1713379,2017-09-13 10:31:34 UTC,One More Reference. https://github.com/mirkosertic/FXDesktopSearch
1713381,2017-08-28 04:11:04 UTC,Two things; firstly F25 build seems to have a machine-id
1713381,2017-08-29 06:32:28 UTC,"Urgh, so looking at [1] and local testing -- I guess this fails on install time too, but dnf doesn't return an error code then.  It's only on the cleanup path, when we're just uninstalling the one kernel, that it fails and then breaks the build"
1713381,2017-08-30 06:33:03 UTC,"Ok, so I've determined a few things"
1713405,2017-08-31 11:30:04 UTC,"Hi,
I tried using pdb step by step debugging but
didn't got any result
here is my sikuli code"
1713419,2017-08-28 07:52:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713420,2018-01-29 21:07:41 UTC,"closing, as i assume nothing was done on neutron end. if there is, this is a trivial addition to event_definitions"
1713420,2017-08-29 07:47:43 UTC,"@jdanjou / @chungg , thanks for the help!"
1713420,2017-08-28 15:46:07 UTC,"if you need it, feel free to add it :)"
1713420,2017-08-29 01:37:45 UTC,"That's great! But I currently only know how to modify event_defintion.yaml file. I believe that on the neutron side, we also have to add something, yet I know almost nothing about code in neutron. Should I work on neutron side myself, or should I ask people in neutron to help us? (Maybe by add 'Also affects project' tag?)"
1713420,2017-08-29 07:35:21 UTC,I've added Neutron. Feel free to request help there!
1713439,2017-08-28 19:57:13 UTC,"Confirmed on Inkscape 0.92.2, LM 18.3"
1713439,2017-10-05 17:37:23 UTC,...just another illustration how this (buggy or inconsistent) behaviour is confusing users...
1713443,2017-10-09 11:50:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510542"
1713443,2020-11-06 14:56:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/761754"
1713450,2017-08-28 11:38:21 UTC,"- reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06) using the internal import option
- also reproduced on Inkscape 0.47pre1"
1713450,2020-09-12 20:22:43 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1713451,2017-08-30 22:15:56 UTC,Above testbed is in the bug state now.
1713451,2017-08-30 23:29:24 UTC,"Review in progress for https://review.opencontrail.org/35116
Submitter: amudha ramachandran (<email address hidden>)"
1713451,2017-08-31 05:44:47 UTC,"Reviewed:  https://review.opencontrail.org/35116
Committed: http://github.com/Juniper/contrail-provisioning/commit/3364f50b8d5b1bbe98f4d1d31f3d2bb66d67407c
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1713452,2017-10-14 21:39:46 UTC,fixed in 4ppa57
1713457,2017-11-13 13:26:10 UTC,OK I can confirm that uninstalling resolvconf is fixing that behavior here
1713457,2017-11-13 12:08:39 UTC,"Hi,"
1713457,2017-11-13 12:08:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713457,2017-11-13 13:07:41 UTC,@andersk Is resolvconf installed on your machine?
1713457,2017-11-13 16:27:43 UTC,Is this reported upstream?
1713457,2017-12-05 01:04:24 UTC,So this has occurred again:
1713457,2018-01-16 11:53:27 UTC,"Please, is there there any known work around?"
1713457,2018-01-16 14:45:47 UTC,"Try removing the resolvconf package. It is only one mechanism of managing /etc/resolv.conf, and it seems to conflict with the (new) systemd-resolved daemon."
1713457,2018-01-17 18:33:07 UTC,Thanks. That works.
1713457,2017-11-13 19:03:41 UTC,I cannot reproduce this on debian.
1713475,2017-10-05 04:30:18 UTC,"There is a deadlock even during --initialize-insecure:
docker run --cap-add sys_ptrace --rm  -it -e MYSQL_ALLOW_EMPTY_PASSWORD=1 --name lp1713475 mysql:5.7 --log-isam=myisam.log --myisam_use_mmap=1"
1713475,2018-01-25 09:18:13 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1113
1713479,2017-08-29 05:44:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713484,2017-08-31 20:21:55 UTC,"As an additional point of information, when dashboard packages (ie. openstack-dashboard, neutron-lbaas-dashboard, designate-dashboard, etc) are installed they install panel config to /usr/share/openstack-dashboard/openstack_dashboard/enabled."
1713484,2017-09-02 06:57:48 UTC,"In my opinion, we never be able to guess what users would like to hide in an opinionated way. So hiding part would be an arbitrary config option something like:"
1713487,2017-11-14 21:36:17 UTC,"Reviewed:  https://review.openstack.org/518532
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=77cbc291fb689ce01e88963ce8e34e4df3dfe2bf
Submitter: Zuul
Branch:    stable/pike"
1713487,2017-11-14 21:30:34 UTC,"Reviewed:  https://review.openstack.org/515998
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=803a953031036279ad8bac6cd65f580c25a63482
Submitter: Zuul
Branch:    stable/pike"
1713487,2017-11-02 20:42:35 UTC,"Reviewed:  https://review.openstack.org/514355
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=5df60d55a33a08a2e892ac6df84681e68a323adc
Submitter: Zuul
Branch:    master"
1713487,2017-11-08 13:52:22 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/518532"
1713487,2017-10-27 22:00:14 UTC,"Reviewed:  https://review.openstack.org/514354
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=beeaf24dc8342c70c19baa72f8881e663ddd1973
Submitter: Zuul
Branch:    master"
1713487,2017-10-19 07:52:18 UTC,"While indeed alerting, there isn't enough information in the logs to identify exactly what caused the bug (current suspicion is some problem in the dependency calculations, but without more info it's hard to know for sure)."
1713487,2017-10-23 15:21:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514355"
1713487,2017-10-23 15:21:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/514354"
1713487,2017-10-28 08:04:12 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/515998"
1713490,2018-02-08 14:36:24 UTC,This bug was fixed in the package ipxe - 1.0.0+git-20180124.fbe8c52d-0ubuntu2
1713490,2019-01-08 09:40:29 UTC,We just upgraded an OpenStack compute from 16.04.4 to 16.04.5 and live migration is broken for VMs running on a 16.04.4 host to a 16.04.5 host.
1713490,2019-01-08 13:38:37 UTC,"I subscribed James and Corey as this might be special to Ubuntu Cloud Archive.
Maybe an upgrade path that we have missed?"
1713490,2019-01-08 13:57:48 UTC,@Christian E.
1713490,2019-01-08 14:08:40 UTC,And this is the virsh dump: http://paste.openstack.org/show/740502/
1713490,2019-01-08 16:29:10 UTC,@paelzer
1713490,2019-01-09 06:25:51 UTC,"As discussed on IRC this would most likely be a Cloud Archive only patch on top.
Therefore we don't even need a new qemu bug for it, we can add a task here."
1713490,2019-01-09 06:30:15 UTC,"For the actual change, you'd want to do this:
in qemu's debian/contol.in there are a bunch of Recommends and Depends like this:
  ipxe-qemu (>= 1.0.0+git-20131111.c3d1e78-1~)
change all those in UCA to
  ipxe-qemu (>= 1.0.0+git-20180124.fbe8c52d-0ubuntu2.1~)"
1713490,2021-02-20 06:09:06 UTC,"Hello, thank you very much for working on this and reverting to an older ipxe package does solve the issue.  but I am curious why qemu needs to compare it with local romfile? why cannot rom be synced from source vm?"
1713490,2021-02-22 07:42:41 UTC,"@Norman - Not a bad idea. The content is synced from the source already, just the size allocation is what can mismatch - it happens so early that it is local. It was suggested like 3 times (I'm sure you could find them on the ML-archive somewhere) or so to transfer the source-size as part of the initial migration meta-data (that would then need a new arg to qemu to specify the size, so it would be qemu arg + libvirt migration data + libvirt rendering that arg accordingly + capability checks for the same). But so far no one ever (neither upstream nor any distro) found the time to implement this feature."
1713490,2018-02-08 13:15:36 UTC,qemu 2.11 is in proposed
1713490,2019-01-08 16:11:31 UTC,"Your guest already is pc-i440fx-bionic (because that is what the cloud archive is based on).
That means that qemu expects it to already run with the newer ipxe."
1713490,2018-01-30 10:06:06 UTC,"I can't file a MIR for the new src:ipxe-qemu-256k-compat we need for this bug 1713490.
Only after new queue I can open up requests.
We discussed that via mail and the TL;DR is: src:ipxe-qemu-256k-compat is the same as src:ipxe (xenial) and has the same timeline of support and therefore should fall under the same ack IMHO."
1713490,2018-02-08 14:36:05 UTC,This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu1
1713490,2018-01-25 07:42:55 UTC,"actually ipxe will get the new sizes and a bump, so yes there is also a fix in src:ipxe so setting back to triaged on that package bug task."
1713490,2017-08-28 13:15:34 UTC,"qemu-ipxe:
Z: 1.0.0+git-20150424.a25a16d-1ubuntu2
A: 1.0.0+git-20161027.b991c67-1ubuntu1"
1713490,2017-08-28 13:53:17 UTC,"The dev is as expected the virtio network card
    <interface type='network'>
      <mac address='52:54:00:cc:a3:b7'/>
      <source network='default'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>"
1713490,2017-08-28 14:09:30 UTC,"It is ""just"" the size that breaks it, as soon as I append a bunch of zero's to the source of the migration it will allocate 0x8000 as well and work  to migrate then.
 $ truncate --size=272384 /usr/lib/ipxe/qemu/efi-virtio.rom"
1713490,2017-08-28 15:02:52 UTC,"As a follow on for ipxe we certainly want to implement a size check post build to catch changes out of a power-of-two bucket in advance next time.
Might even be worth to discuss on ipxe upstream."
1713490,2018-01-29 12:31:42 UTC,Bonus: since the ipxe roms are reused arm64 and ppc64le are also affected and need the compat code in qemu to map to the compat rom files.
1713490,2017-08-29 11:02:58 UTC,"All base roms grow ~4-5k, the EFI addon grew 20-24k.
I discussed the ""might need to go backward plan"" (at least for now), and there are examples of this like:
https://lists.ubuntu.com/archives/artful-changes/2017-August/007901.html
https://lists.ubuntu.com/archives/artful-changes/2017-July/005052.html
https://lists.ubuntu.com/archives/artful-changes/2017-May/001471.html
https://lists.ubuntu.com/archives/artful-changes/2017-May/001728.html"
1713490,2017-08-29 10:21:18 UTC,"I'm currently working on various options from turning back the time via an AA or some magic (unlikely :-) ), or patching back to the old version (plus a few fixes that are needed for FTBFS) but also trying to shrink size on the new versions if that is reasonable."
1713490,2017-08-29 14:52:46 UTC,The test builds in [1] soon abandoned) are good now.
1713490,2017-08-29 14:55:54 UTC,"No changes to Qemu planned to auto-fixup the migration, that is too complex to try so late in the cycle. Also due to Ubuntu Cloud Archive(s) not having ipxe in it we would have to add there as well or otherwise qemu 2.10 wouldn't be 2.10.
On LTS releases it might be better to push ipxe changes that break the migratability as all migrations have to go ""though"" LTS (like updates), so we can fix up there if we get that in qemu."
1713490,2017-08-29 15:14:08 UTC,Related MP up in https://code.launchpad.net/~paelzer/ubuntu/+source/ipxe/+git/ipxe/+merge/329820
1713490,2017-08-30 11:04:55 UTC,This bug was fixed in the package ipxe - 1.0.0+git-20161027.b991c67+really20150424.a25a16d-1ubuntu1
1713490,2017-11-09 13:52:25 UTC,"Reported it to Debian to agree on a solution which they can use in >=Buster and we in >=Bionic.
=> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881263"
1713490,2018-01-24 14:40:41 UTC,"change will need a new src package for the compat roms, so ipxe is not affected (but the compat is).
Qemu will carry the machine type dependent link changes matching the compat package."
1713490,2017-08-29 12:09:23 UTC,"To quote something comparable, best old example to match the current case seems to be the following:
https://lists.ubuntu.com/archives/xenial-changes/2015-November/000988.html"
1713491,2017-12-05 23:18:25 UTC,MR to this bug: https://gitlab.com/inkscape/inkscape/merge_requests/154
1713491,2017-12-05 23:18:54 UTC,Thanks Alvin for fill the bug!
1713491,2017-12-06 18:43:38 UTC,Merged on: da4e818f765c88916763e17d2180f9df22bf5038
1713491,2017-12-06 18:46:36 UTC,Merged on master
1713493,2020-09-21 18:45:22 UTC,Closing because INVALID: Works as described in https://bugs.launchpad.net/inkscape/+bug/1713493/comments/1 throughout Inkscape.
1713493,2017-08-28 18:46:01 UTC,"you can already enter formulas ""1+1/6"" in most of the dialogs"
1713493,2017-08-30 14:12:08 UTC,"MC Thanks,  Can someone check if this is also applicable to Live Path Effects, I am still investigating but it seems some input fields for these seemingly round off to 2 d.p, not 3 or 4 as I was expecting."
1713501,2017-08-29 07:34:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713504,2017-08-28 15:04:24 UTC,This has been fixed in the development version.
1713508,2017-11-21 14:15:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713513,2017-08-31 12:21:20 UTC,"I've also had the same problem. I tested it with a few extensions and the error happened with all of them, so it seems to be an issue with the start of a gnome session. It happens mostly with guest sessions, but I've also seen it happen in normal sessions occasionally."
1713513,2017-09-04 14:40:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713519,2017-11-21 17:43:50 UTC,https://review.openstack.org/#/c/516144 has been approved to land in ironic-ui which adds this feature.
1713519,2018-02-05 23:47:26 UTC,This issue was fixed in the openstack/ironic-ui 3.1.0 release.
1713533,2017-08-29 22:23:00 UTC,Neal Gompa pointed us to the Fedora font licenses documentation: https://fedoraproject.org/wiki/Licensing:Main#Font_Licenses
1713533,2017-08-29 19:14:20 UTC,"Unfortunately I can't check all the licenses right now, but I'm sure that almost all of these fonts can be freely distributed (with the exception of some script typefaces)."
1713533,2017-08-29 20:11:51 UTC,I've added the licenses for all the fonts in the document
1713533,2017-08-28 18:56:38 UTC,Thank you for your suggestions.
1713533,2017-08-29 14:42:20 UTC,"Interesting innitiative. However, I see that it doesn't cover one very important aspect at all: licenses. The license needs to allow inclusion in the distribution and be compatible with the other licenses that we ship."
1713533,2017-08-28 17:32:33 UTC,"Great initiative! Two comments: please change the sharing settings to allow comments by anyone with the link, and include image samples of the fonts in the tables, for convenience."
1713535,2017-08-28 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1713535,2017-08-29 21:18:11 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1713535,2017-08-29 15:36:07 UTC,apport information
1713535,2017-08-29 15:36:06 UTC,apport information
1713535,2017-08-29 15:36:05 UTC,apport information
1713535,2017-08-29 15:36:04 UTC,apport information
1713535,2017-08-29 15:36:03 UTC,apport information
1713535,2017-08-29 15:36:02 UTC,apport information
1713535,2017-08-30 12:58:46 UTC,I've just installed v4.13-rc7 and no more luck .
1713535,2017-08-29 15:36:00 UTC,apport information
1713535,2017-08-29 15:35:57 UTC,apport information
1713535,2017-08-29 15:35:56 UTC,apport information
1713535,2017-08-29 15:35:55 UTC,apport information
1713535,2017-08-29 15:35:53 UTC,apport information
1713535,2017-08-29 15:35:51 UTC,apport information
1713535,2017-08-29 15:36:00 UTC,apport information
1713535,2017-08-29 15:35:50 UTC,apport information
1713537,2017-10-06 10:46:05 UTC,This bug was fixed in the package curtin - 0.1.0~bzr532-0ubuntu1
1713537,2017-09-06 18:31:21 UTC,The previous fix was not sufficient for raid over iscsi and I missed running that test case.
1713537,2017-12-15 22:12:57 UTC,"This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New"
1713537,2017-08-29 02:13:40 UTC,"Due to some change in behavior of iscsi, we now trip up over not disconnecting the targets after unmounting them from the target.  The disconnect code is call with the target dir path (Which isn't valid any more due to being unmounted).  We should definitely umount the targets first (to flush data on the device) but then call disconnect with a path of / to use the config on the ephemeral host (which was copied into the target anyhow)."
1713537,2017-08-29 02:41:13 UTC,"Well bummer, pre-artful, it doesn't find the session data.
Let's try logging out before umounting (which still syncs devices)."
1713537,2017-08-28 19:54:12 UTC,"When I first saw this, I assumed that it was a result of ifupdown being
dropped from the image (bug 1698181).  However, it seems (as of the
20170826 cloud image) that that has not yet happened."
1713539,2017-09-05 06:06:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/500680"
1713539,2017-10-09 19:27:14 UTC,https://review.openstack.org/510637 and https://review.openstack.org/510638 to switch the scenario upgrade jobs to non-voting
1713539,2018-07-03 14:30:25 UTC,"Can this be closed out?  Looks like the patch is ready to be abandoned, and other work by myself and bodango has been going on in this area."
1713539,2018-07-31 17:25:36 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.openstack.org/500680
Reason: Abandoning this patch per the TripleO Patch Abandonment guidelines (https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html). If you wish to have this restored and cannot do so yourself, please reach out via #tripleo on freenode or the OpenStack Dev mailing list."
1713539,2019-08-02 15:05:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/674327"
1713539,2019-08-06 15:18:42 UTC,"Reviewed:  https://review.opendev.org/674327
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=a6b920419caaec25cb7cf71c7b00636ddea82938
Submitter: Zuul
Branch:    master"
1713539,2019-09-18 19:27:49 UTC,This issue was fixed in the openstack/python-tripleoclient 12.2.0 release.
1713548,2017-09-29 12:02:04 UTC,"New indicator-keyboard 0.0.0+17.10.20170906-0ubuntu1 fixed this bug, but created new bug 1720344."
1713548,2017-08-28 18:26:50 UTC,"Oh, it tries to open unity-control-center. :( Dmitry, can you fix that? I guess that is also problem in 17.04..."
1713548,2017-09-08 16:00:25 UTC,Bug is not fixed.
1713548,2017-09-14 09:04:39 UTC,This bug was fixed in the package indicator-keyboard - 0.0.0+17.10.20170906-0ubuntu1
1713552,2017-08-28 18:47:24 UTC,Can you try with 0.92.2 ?
1713572,2017-08-28 20:30:05 UTC,This change was made by a bot.
1713577,2018-05-11 15:35:09 UTC,This change was made by a bot.
1713577,2020-01-09 07:43:02 UTC,"4.10 EOL,
please feel free to open a new bug if you're still encounter this issue with newer releases."
1713578,2017-08-29 06:42:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713578,2017-08-29 11:24:41 UTC,"At the moment the following is done:
- on debootstrap resolved symlink is configured
- on upgrades resolvconf is preserved, and resolved is integrated to feed data into resolvconf
- if upgraded resolvconf is removed, the postrm in artful configured symlink to point at resolved
- static file is preserved i believe (need to check)
- if /etc/resolv.conf is a static file configured by network-manager, resolved may take over it (since network-manager has resolved integration), but currently doesn't."
1713580,2017-08-30 07:49:01 UTC,Here is the upstream bug report:
1713584,2017-08-28 22:40:35 UTC,"StacktraceTop:
 g_cancellable_cancel (cancellable=0x7ffc4d58679f) at ../../../../gio/gcancellable.c:485
 model_free_row_data (button=button@entry=0x7fc4fc00c2c0, iter=iter@entry=0x7ffc4d5867c0) at ././gtk/gtkfilechooserbutton.c:1698
 model_update_current_folder (file=0x8eb3ab48e0, button=0x7fc4fc00c2c0) at ././gtk/gtkfilechooserbutton.c:2070
 update_combo_box (button=button@entry=0x7fc4fc00c2c0) at ././gtk/gtkfilechooserbutton.c:2435
 gtk_file_chooser_button_select_file (chooser=0x7fc4fc00c2c0, file=0x8eb3ab48e0, error=<optimized out>) at ././gtk/gtkfilechooserbutton.c:591"
1713595,2017-11-26 16:05:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713601,2017-08-29 21:09:19 UTC,"Do you have the steam tray icon enabled?  Does this happen if you disable it?  (Meaning, only a steam window is open, but no tray icon)"
1713601,2017-08-29 21:12:47 UTC,Just a quick search yielded this:
1713601,2017-10-19 21:48:47 UTC,I was just about to link to that myself.
1713605,2017-12-28 13:46:05 UTC,"Without us doubling up all the relevant testcases for Kubuntu not sure what we can do about this, other than commenting in the current testcases."
1713607,2017-09-01 08:57:51 UTC,found the answer https://lists.ubuntu.com/archives/ubuntu-desktop/2017-July/005054.html
1713610,2017-10-27 20:29:58 UTC,If I remember correctly we wanted to keep the reference in admin interface to alert mahara admin that they need to talk to sysadmin about why the file has gone away - as this could happen when dataroot is on a different server/partition and it's going away was a mistake/temporary.
1713610,2017-11-09 09:16:27 UTC,"Should we remove the link then and leave the entry and / or add a column ""Deleted"" so entries can be sorted?"
1713615,2017-09-02 06:52:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713615,2017-09-14 15:48:01 UTC,"This is a bug in Debian too, I think it should be fixed there"
1713615,2017-09-14 16:50:42 UTC,The last working version was this:
1713615,2017-09-15 05:15:57 UTC,It worked fine for me on a different internet connection.
1713615,2017-09-28 15:18:01 UTC,I hit this bug today under Ubuntu MATE 17.10 x64.
1713615,2017-09-30 07:55:52 UTC,"Hello Dan,"
1713615,2017-10-20 21:42:19 UTC,"package from debian repo 3.6_all works fine, but this, 3.6ubuntu2, is crap and it is not working."
1713615,2017-11-13 19:12:31 UTC,Issue still exists. Tried also with 3.6ubuntu2
1713615,2018-05-07 09:00:51 UTC,Can anybody please report the bug in Debian?
1713615,2018-04-02 18:58:32 UTC,Still broken on up-to-date (2nd of April 2018) 18.04 installation:
1713615,2019-04-28 06:56:27 UTC,I tried:
1713615,2019-04-28 11:04:20 UTC,"The space is not the problem, as downloading another file from the same project, but in a different directory, 'cabextract', also fails intermittently:"
1713615,2019-04-28 11:33:17 UTC,Building the source package with only the following change works for me:
1713615,2019-04-29 07:21:19 UTC,"> -URLROOT = http://downloads.sourceforge.net/corefonts/
> +URLROOT = https://github.com/pushcx/corefonts/raw/master/
"
1713615,2019-04-29 08:40:39 UTC,Fetching from github was significantly faster than fetching from sourceforge (when it worked) for me in South Africa.  I contacted Peter (pushcx on github) and he set up his mirror four years ago in order to work around a different sourceforge issue [1] and does not intend to remove it.
1713615,2019-04-29 09:00:36 UTC,Downloading from github.com redirects to raw.githubusercontent.com (github.map.fastly.net).  So it appears to be using Fastly's CDN which has POPs all over the world.
1713615,2019-04-29 19:00:17 UTC,This bug was fixed in the package msttcorefonts - 3.7ubuntu5
1713615,2019-04-29 19:03:00 UTC,"The problem here seems to be that the files are already downloaded, and when asking sourceforge to continue the download, it does the redirect rather than responding with a 416 error with the appropriate content-range as it should."
1713615,2019-04-29 21:02:22 UTC,This bug was fixed in the package update-notifier - 3.192.20
1713615,2019-05-13 11:19:46 UTC,Still happening on Ubuntu 18.04.2 with all the latest updates.
1713615,2019-05-16 10:13:26 UTC,affects me here also.
1713615,2019-05-28 11:14:54 UTC,"Still happening on 19.10 (updated from 18.10, which had previously been updated from 18.04)"
1713615,2019-06-06 13:50:57 UTC,"I confirm I also see it in Ubuntu 18.10 and 19.04, upgraded from 18.04 (I was not seeing it in 18.04). A recurring bug, as I was also getting it in older versions of Ubuntu (in 16.04 if I remember well)."
1713615,2019-07-29 07:07:10 UTC,"I can confirm that this is a very old bug. There seems to be a fix by using the original package from Debian. It would be nice if this would be fixed in Ubuntu, too."
1713615,2019-08-15 06:48:18 UTC,Still happening in 18.04.03. Installing http://ftp.de.debian.org/debian/pool/contrib/m/msttcorefonts/ttf-mscorefonts-installer_3.7_all.deb solved the problem for now for me.
1713615,2019-10-27 15:12:31 UTC,"This seems to be a recurrent and intermittend problem. I have just run into it again, installing Ubuntu 18.04 LTS Server. One one box, no problem, on the other fail.
In some attempts it fails at the beginning, in others after download of a few fonts. And the most
annoying thing is, that the package is recorded as installed, even when the installation fails, so you have to do multiple apt purge... apt install..."
1713615,2019-11-13 12:19:50 UTC,"> 19.10 network install
"
1713615,2019-11-24 18:37:15 UTC,"I can confirm this is also impacting the 19.10 normal desktop installation, when you do a sudo apt-get install ubuntu-restricted-extras after a clean install."
1713615,2019-12-04 08:56:53 UTC,"I am on 18.04, tried"
1713615,2019-12-05 18:15:30 UTC,"I was affected by this bug while installing ubuntu-restricted-extras on a fresh installation of 18.04.3. Purging and reinstalling several times seems to have worked, and the package is installed. Maybe use a better mirroring service for this package?"
1713615,2020-01-04 10:30:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713615,2020-01-11 08:15:43 UTC,"Affects me too. Debian workaround works, it is shame what problem exists in Ubuntu..."
1713615,2020-02-24 16:21:16 UTC,"Debian package downloads the font files with wget, using a lot of parameters and several possible URLs, so it eventually succeeds.
Ubuntu package uses update-notifier, which in turn uses apt-helper ( thanks the sources in Python language ), which uses I don't know what...
I found a method leading to a successful installation of Ubuntu package. The clue consists in :
1. pre-loading the font files with wget,
2. create a small database file for debconf, telling that the EULA MS licence has been accepted and that the font files are stored in a certain directory,
3. installing the ttf-mscorefonts-installer package after setting two debconf variables."
1713615,2020-02-24 16:27:14 UTC,"This is the continuation of my previous comment, containing the HOWTO.
In a fresh dedicated directory containing the two scripts, type :
./recup_files
sudo ./mstt_inst"
1713615,2020-04-14 17:25:28 UTC,"Seeing this on 20.04 daily, three purge + reinstall required before successful installation."
1713615,2019-04-27 20:57:11 UTC,"FWIW, this is likely a regional thing, as it depends on which mirrors sourceforge gives you and them being broken."
1713615,2019-04-27 20:54:14 UTC,"In APT, redirection from https to http is not supported for security reasons. Debian does not use APT's functionality for downloading in this package, but another thing that does follow such redirects, and hence does not fail."
1713615,2018-05-04 17:54:38 UTC,"I just tried it again and after several attempts, it eventually worked. I think the issue is with mirrors at SourceForge and it is an intermittent problem."
1713615,2019-04-27 15:26:32 UTC,If you do it multiple times you will end up on a mirror after a while that does not do the redirection to http..
1713615,2019-04-27 15:31:07 UTC,"I tried it multiple times, it didn't work, although it failed on different files. Debian package succeeded from the first attempt."
1713615,2018-05-07 19:54:05 UTC,I've just tried again now after upgrading to 18.04 and the problem still occurs.
1713615,2018-05-04 17:50:58 UTC,"I'm seeing this issue on the latest up-to-date Ubuntu 18.04 as of May 4th, 2018:"
1713615,2018-07-14 16:34:44 UTC,"Copying comment from LP: #1767748, which is a work-around for this bug. Copying from since this is the main bug, and the other is a duplicate of this bug."
1713615,2018-09-02 04:17:40 UTC,To consolidate the workaround to this ticket:
1713615,2018-09-12 15:17:12 UTC,Not easy to do if an upgrade fails with 1341 packages left to update! Can't this just be fixed?!
1713615,2018-10-20 12:21:02 UTC,Happens when upgrading from Kubuntu 18.04 to 18.10.
1713615,2018-11-02 09:32:00 UTC,"I started experiencing this bug when I upgraded 16.04 LTS to 18.04 LTS a few days ago, following a month or so of nagging by the software updater."
1713615,2018-11-09 02:01:30 UTC,#17 works on clean install of 18.10.
1713615,2018-11-09 02:09:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713615,2018-11-12 10:17:21 UTC,"#17 works. In order to keep the package manager from updating the package to the broken version it helps to run ""sudo apt-mark hold ttf-mscorefonts-installer"" after."
1713615,2019-03-03 23:32:10 UTC,Just upgraded from 16.04 to 18.04 a few days ago.
1713615,2019-03-07 14:05:10 UTC,Ubuntu 18.10 ... this is just ridiculous.
1713615,2018-10-26 07:55:54 UTC,This bug is still present. Just upgraded from 18.04 to 18.10. Fixed by the proposed solution above.
1713615,2019-03-07 15:35:22 UTC,"I think it would help of somebody created an SRU, https://wiki.ubuntu.com/StableReleaseUpdates"
1713615,2019-04-13 13:34:05 UTC,"Purged and installed the debian version ""ttf-mscorefonts-installer_3.6_all.deb"". All fonts downloaded and installed correctly."
1713615,2019-04-14 09:57:00 UTC,"Upgraded to disco, purged and installed:"
1713615,2019-04-20 06:31:43 UTC,"Upgraded to disco, purged and installed:"
1713615,2019-04-22 02:56:50 UTC,Confirmed that it affects disco (5 attempts at apt install --reinstall failed)
1713615,2018-03-06 11:44:38 UTC,Seems to work on 18.04 for the past couple of days.
1713615,2019-04-22 18:57:38 UTC,Workaround does not work in my case (upgrade from 18.10 to 19.04:): sudo apt purge ttf-mscorefonts-installer && sudo apt install --reinstall ttf-mscorefonts-installer
1713615,2019-04-23 06:39:36 UTC,"Confirmed that it affects Ubuntu Cosmic -> Disco upgrade. Still failing, just as #33."
1713615,2019-04-24 12:41:19 UTC,It's still happening in April 2019.
1713615,2019-04-24 19:31:04 UTC,"Clean install of Ubuntu 19.04:
`sudo apt install ttf-mscorefonts-installer` results in redirection bug above.
Only solution that works for me was installing the Debian package from #6."
1713615,2019-04-26 14:04:48 UTC,A quick re-test in Ubuntu 19.04:
1713615,2019-04-27 15:03:54 UTC,This workaround:
1713615,2019-03-07 14:39:57 UTC,"Please do not forget that this bug is present at least since 15.10 while we are going to see 19.04 released next month. Hey you, Ubuntu devs, can I buy a beer someone for copying the original Debian version over finally? If one of you do it once, thousands of users will not have to on every update."
1713621,2017-11-09 02:27:20 UTC,I vote for this feature too
1713621,2017-10-23 14:20:51 UTC,"You can move the Show Applications icon to the top/left by setting show-apps-at-top=true, as described here: https://askubuntu.com/a/966777/589052"
1713621,2017-10-22 14:44:39 UTC,"Thanks Daniel, nice to see some common sense to be used here."
1713621,2017-09-05 17:27:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713621,2017-09-22 16:29:59 UTC,"Original Dash to Dock extension has a setting to move the Show Applications icon to the top of the dock, please implement this setting in gnome-shell-extension-ubuntu-dock.
Ability to move the Show Applications icon to the top of the dock is especially important if we set ""Screen position"" to bottom in Settings window because now Applications icons moves to right bottom instead of left bottom corner, like in other popular Desktop environments (KDE, LXDE, Windows, MacOS X, etc)"
1713621,2017-09-20 07:16:19 UTC,"We discussed it at GUADEC and the application button doesn't do the same than the BFB. In addition, the proximity with Activities will be puzzling to the users and deviates from GNOME Shell upstream Dash experience. Setting as invalid."
1713621,2017-10-10 01:44:09 UTC,Reopened because a third person has requested this today.
1713626,2017-08-29 07:09:30 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1713634,2017-08-29 07:30:06 UTC,This change was made by a bot.
1713635,2017-08-29 07:09:29 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1713635,2017-08-31 08:56:38 UTC,一些小城市数据不全，没有进行异常处理，导致数据库写入失败。
1713650,2020-11-15 19:29:02 UTC,"Gnome now differs from every single other window manager. I understand that alt+drag interferes with some former mac users' workflows, but really, we've been here for 20 years and they just arrived... why should we change our workflows to suit theirs?"
1713650,2017-09-15 07:15:05 UTC,Workaround:
1713650,2020-11-16 02:09:41 UTC,We've now been using Super+drag for a few years in Ubuntu so I think people are getting used to it.
1713650,2017-09-04 12:35:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713650,2017-09-01 06:21:40 UTC,Didier pointed out that GNOME uses super instead of alt for that (which creates less conflicts in softwares)
1713650,2017-09-05 02:03:30 UTC,I'm not sure I agree with Gnome's decision to change to Super+drag. It's been Alt+drag in Ubuntu for so long that I wonder what was conflicting with that?
1713650,2017-08-29 08:04:20 UTC,"I wonder if this is relevant:
https://bugzilla.gnome.org/show_bug.cgi?id=772908"
1713663,2017-08-29 13:30:26 UTC,One question is: can we enable that option even when there is HAProxy in front?
1713663,2017-08-29 13:57:16 UTC,See my comment https://bugs.launchpad.net/oslo.middleware/+bug/1590635. Let's wait a bit to see the outcome there.
1713663,2020-02-05 17:40:57 UTC,"We are still encountering this same issue with designate when paging over the public ssl endpoint. The link being sent back in the 'links' json var is coming back as 'http'(non-ssl) when it should be 'https'(ssl) over the public endpoint.  This is due to it being behind a loadbalancer that is hitting the backend over http.  Haproxy is configured to set the ""X-Forwarded-Proto: https"" header.  Designate should be seeing this and setting the link reference to utilize https."
1713663,2020-02-05 19:14:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/706090"
1713663,2020-03-30 16:01:40 UTC,"Reviewed:  https://review.opendev.org/706090
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_designate/commit/?id=7cdb8ea27c017fd056edfea056114b5329f8248a
Submitter: Zuul
Branch:    master"
1713666,2018-03-19 21:12:05 UTC,Please try again with 3.3.0
1713666,2017-08-31 10:55:02 UTC,"I also noticed that your Ubuntu is out of date. I currently test with 16.04, you run 14.04."
1713666,2017-08-30 12:21:03 UTC,"here is the screenshot - worked in older versions til versionn 3.xx
here you also can see the screen (graphical) problem
Am 30.08.2017 12:07, schrieb bdaum:

> cannot reproduce this under ubuntu. Can you send a screenshot?
>
> ** Changed in: zora
>         Status: New => Incomplete
>
"
1713666,2017-08-30 10:07:23 UTC,cannot reproduce this under ubuntu. Can you send a screenshot?
1713666,2017-08-31 10:45:40 UTC,Works fine under Ubundu KDE and Suse Gnome. Maybe a Ubuntu Gnome issue.
1713667,2017-08-30 08:09:18 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1713669,2017-08-30 10:10:18 UTC,"What do you mean with ""text annotation""? A text note? Works for me. Can you attach a crash report (log file)?"
1713669,2017-08-30 12:30:47 UTC,the new feature: Textnotizen als Alternative zu Sprachnotizen
1713669,2018-03-19 21:10:23 UTC,Please try again with 3.3.0
1713670,2017-09-13 08:56:33 UTC,It would be useful to have a mongo dump if there is a repro of that. A mongo dump would give us complete controller-side state including logs.
1713670,2017-08-30 02:24:51 UTC,"It would really help to get the unit logs for that unit (if they exist), and the machine logs for the machine that the unit was on (18/lxd/0 ? )."
1713670,2017-09-04 08:09:00 UTC,"The machine was eventually destroyed as it was preventing deploying other charms.
I'm sorry we can't provide you with more information to understand what was happening. Our wild guess is that the image needed by the unit was removed and the unit was stuck trying to download it.
A part what caused this specific issue, it would be very useful to have a way to force removing a unit independently by the state of the unit itself, so that a customer deployment don't get stuck by something unexpected."
1713671,2017-08-29 10:55:20 UTC,Reassigning to readline:
1713672,2017-09-21 16:11:45 UTC,Issue persists (on cmu-21b__21b_unicode_-linux-x86):
1713672,2017-09-21 20:38:12 UTC,"Maybe on some platforms, including cmucl, launch-program should ensure the pathname is absolute, at least if a relative directory is specified? I hope that doesn't mean we have to reimplement PATH processing, though."
1713672,2017-09-22 11:58:17 UTC,"Well, I'm not sure if this should fix only cmucl or all implementations; either way, there's the output of a couple of runs of a different script:"
1713672,2017-09-22 16:24:30 UTC,"Unlike unix-namestring's, native-namestring's are not guaranteed to use / as separator. The separator might even vary with the host on a given implementation."
1713674,2017-08-29 16:09:41 UTC,"This is already in our stable-2.0 branch, so both LXC 2.1 and LXC 2.0.9 will have it."
1713677,2017-08-29 09:15:26 UTC,w3hat do i do now?
1713683,2017-08-30 10:19:50 UTC,cannot reproduce unter Ubuntu. Please add the crash report (log file)
1713683,2018-03-19 21:10:49 UTC,Please try again with 3.3.0
1713687,2020-08-30 09:09:00 UTC,"python-pip (18.1-1) experimental; urgency=medium
...
* Only default to --user when --target/--prefix not set
     (Closes: #830892, #895232, #876145)"
1713687,2020-01-27 08:27:43 UTC,And this is because: https://sources.debian.org/patches/python-pip/18.1-5/set_user_default.patch/
1713687,2020-01-27 08:25:45 UTC,"I can confirm, for example in Mint 19.3:
Collecting pysimplegui
  Downloading https://files.pythonhosted.org/packages/fd/2e/684784669c904431190964e210fbeb4920b5137afb4731ff924de93cef9e/PySimpleGUI-4.15.2-py3-none-any.whl (291kB)
Installing collected packages: pysimplegui
Exception:
Traceback (most recent call last):
  File ""/usr/lib/python3/dist-packages/pip/basecommand.py"", line 215, in main
    status = self.run(options, args)
  File ""/usr/lib/python3/dist-packages/pip/commands/install.py"", line 360, in run
    prefix=options.prefix_path,
  File ""/usr/lib/python3/dist-packages/pip/req/req_set.py"", line 784, in install
    **kwargs
  File ""/usr/lib/python3/dist-packages/pip/req/req_install.py"", line 851, in install
    self.move_wheel_files(self.source_dir, root=root, prefix=prefix)
  File ""/usr/lib/python3/dist-packages/pip/req/req_install.py"", line 1064, in move_wheel_files
    isolated=self.isolated,
  File ""/usr/lib/python3/dist-packages/pip/wheel.py"", line 247, in move_wheel_files
    prefix=prefix,
  File ""/usr/lib/python3/dist-packages/pip/locations.py"", line 153, in distutils_scheme
    i.finalize_options()
  File ""/usr/lib/python3.6/distutils/command/install.py"", line 274, in finalize_options
    raise DistutilsOptionError(""can't combine user with prefix, ""
distutils.errors.DistutilsOptionError: can't combine user with prefix, exec_prefix/home, or install_(plat)base"
1713687,2018-01-31 06:53:30 UTC,It is still actual for Ubuntu 17.10
1713687,2018-06-15 07:41:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713687,2018-01-16 13:33:20 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1713687,2018-06-15 07:42:12 UTC,Still current for 18.04
1713690,2018-10-15 11:05:13 UTC,This bug was fixed in the package git - 1:2.19.1-1ubuntu1
1713690,2020-08-05 22:07:19 UTC,Adding to my post above:
1713690,2020-08-05 22:04:40 UTC,"Same problem on WSL 1, Ubuntu 20.04."
1713690,2020-04-29 13:33:08 UTC,I'm having the same problem on Ubuntu 18.04 on Windows 10 WSL. Upgrading to 20.04 remains the same.
1713690,2018-10-12 14:38:43 UTC,"On Fri, Oct 12, 2018 at 07:18:51AM -0000, Georgi Georgiev wrote:

> Any reason why the executable bit of diff-highlight is stripped?
>
> If I run `sudo make -B -C /usr/share/doc/git/contrib/diff-highlight
> diff-highlight` the generated file is executable, but the one shipped
> with the package is not.
"
1713690,2020-11-08 16:40:38 UTC,Same error:
1713690,2018-10-12 00:23:58 UTC,This bug was fixed in the package git - 1:2.17.1-1ubuntu0.3
1713690,2018-10-12 07:18:51 UTC,Any reason why the executable bit of diff-highlight is stripped?
1713690,2017-08-29 10:20:44 UTC,"(Filing this in Ubuntu even though it's being tracked in Debian, because I think this will be a papercut for a number of users if it ends up in artful.)"
1713690,2017-08-29 10:41:35 UTC,https://github.com/git/git/commit/0c977dbc8180892af42d7ab9235fd3e51d6c4078 introduced the need to run the diff-highlight Makefile to build diff-highlight.
1713690,2018-05-12 14:42:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713690,2018-09-20 10:15:22 UTC,"Hello Dan, or anyone else affected,"
1713690,2018-10-11 01:40:56 UTC,"Hi, I can confirm that the version in bionic-proposed (1:2.17.1-1ubuntu0.2) adds back the /usr/share/doc/git/contrib/diff-highlight/diff-highlight to the git package."
1713691,2017-08-29 10:30:06 UTC,This change was made by a bot.
1713696,2017-08-29 11:39:18 UTC,Thanks for your report.
1713696,2017-08-29 12:09:32 UTC,"Ah, sure, I installed Budgie 17.10 Beta1 on a real machine, option: erase whole disk."
1713696,2017-08-29 12:39:29 UTC,Thanks. Same result in a VM.
1713696,2017-09-26 09:20:21 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1713697,2018-10-16 10:34:01 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/500366
Reason: Cleaning up changes that seem to be abandoned or are older than two months. If you think this was an error and the change is still relevant, please be free to restore it. Sorry for any inconvenience that I might have caused by this."
1713697,2018-10-16 10:32:51 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/527654
Reason: Cleaning up changes that seem to be abandoned or are older than two months. If you think this was an error and the change is still relevant, please be free to restore it. Sorry for any inconvenience that I might have caused by this."
1713697,2018-10-16 10:32:42 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/527676
Reason: Cleaning up changes that seem to be abandoned or are older than two months. If you think this was an error and the change is still relevant, please be free to restore it. Sorry for any inconvenience that I might have caused by this."
1713697,2018-10-16 10:31:48 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/527624
Reason: Cleaning up changes that seem to be abandoned or are older than two months. If you think this was an error and the change is still relevant, please be free to restore it. Sorry for any inconvenience that I might have caused by this."
1713697,2018-04-30 07:46:14 UTC,"Reviewed:  https://review.openstack.org/527391
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=6e9cb606ec837ec5e380703c895132d7f7df6591
Submitter: Zuul
Branch:    master"
1713697,2018-01-26 10:53:25 UTC,"Reviewed:  https://review.openstack.org/523043
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=64f0692d680b15530c8c1dc9f6366a49aec57d0d
Submitter: Zuul
Branch:    master"
1713697,2018-01-25 11:05:29 UTC,"Reviewed:  https://review.openstack.org/533157
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=1196e9de2823d7041abb322019044821e37c72bd
Submitter: Zuul
Branch:    master"
1713697,2018-01-17 20:07:05 UTC,"Reviewed:  https://review.openstack.org/521815
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=24675835eef2f8aae4dde9d37fb772706c1892fa
Submitter: Zuul
Branch:    master"
1713697,2018-01-12 11:08:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533157"
1713697,2017-12-13 11:49:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527676"
1713697,2017-12-13 10:00:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527654"
1713697,2017-12-12 12:42:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527391"
1713697,2017-11-07 20:55:29 UTC,"Reviewed:  https://review.openstack.org/514404
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=ab4c69a47228315448a1ccbd21829b4029b74bb7
Submitter: Zuul
Branch:    stable/pike"
1713697,2017-10-23 17:47:47 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/514404"
1713697,2017-10-23 16:31:57 UTC,"Reviewed:  https://review.openstack.org/513158
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=7366ac0455a335e8f56a8467515bca33f3d29e28
Submitter: Zuul
Branch:    master"
1713697,2017-09-03 13:49:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/500366"
1713697,2017-12-13 08:05:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527624"
1713720,2017-08-29 13:00:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713720,2017-08-29 13:00:45 UTC,This affects both Ubuntu Budgie and Ubuntu MATE.
1713720,2019-10-01 20:39:39 UTC,This bug was fixed in the package ubiquity-slideshow-ubuntu - 149
1713725,2017-08-31 13:45:33 UTC,"Reviewed:  https://review.openstack.org/498799
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=c24afe6d6839786a7624c28fb3c180716d1b2cb1
Submitter: Jenkins
Branch:    master"
1713725,2017-09-05 13:10:21 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.0.0rc1 release candidate.
1713725,2017-09-09 08:15:19 UTC,"i have submitted a revert for this as the patch is broken in two ways.
first this patch moved the gatering of facts before we install the requirment for the setup module to work on the remote host and second ansible_play_batch is undefiend."
1713726,2017-09-06 17:01:39 UTC,"Yeah, we need to get another fix in for that. We released LXC 2.1 yesterday which contains that fix, but are waiting for a freeze exception."
1713726,2017-08-29 13:28:17 UTC,Has the `/etc/init/` directory and associated files been removed from artful I remember @xnox removing old init scripts.
1713726,2017-08-29 16:03:03 UTC,"Yeah, that's getting fixed upstream, it's part of the chaos caused by removing a bunch of upstart jobs that weren't hurting anyone..."
1713726,2017-09-06 13:55:08 UTC,"With the latest upload tests still fail, but it seems to get slightly farther. Is this a different issue?"
1713727,2017-08-30 18:23:26 UTC,FAIL: intl/tst-gettext
1713732,2017-10-13 06:31:21 UTC,"@Syed Armani,@Linda Wang; I fix this issue,just like  https://review.openstack.org/498828, add the section
[oslo_middleware]
enable_proxy_headers_parsing = True in cinder.conf."
1713732,2017-08-29 14:11:45 UTC,"When I run tempest, 2 tests failed in https supported deployment:"
1713732,2017-08-30 12:33:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499129"
1713732,2017-08-30 15:33:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499196"
1713732,2017-09-04 18:14:28 UTC,"Reviewed:  https://review.openstack.org/499129
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=6bb387ec141ca758929387afcc31dc846e9ac54c
Submitter: Jenkins
Branch:    master"
1713732,2017-09-05 14:34:58 UTC,"Change abandoned by Jens Harbott (frickler) (<email address hidden>) on branch: master
Review: https://review.openstack.org/499196
Reason: I'm not sure anymore that this is what is really needed."
1713732,2017-09-05 14:41:54 UTC,"@Linda: If you want to continue with this issue, please provide further information about your setup that allows to reproduce it. With https://review.openstack.org/498828 applied, there are no more tempest failures in devstack for me."
1713732,2017-10-10 05:50:29 UTC,@lindamy Were you able to resolve this issue? I am facing this problem as well.
1713732,2017-10-11 03:51:56 UTC,"@Syed Armani  Not yet, the issue is still there for me."
1713734,2017-08-29 14:00:12 UTC,"After some further investigation, this behavior occurs when adding a space to the end of a non-empty line as well. Tabs do not seem to produce this behavior. If a space or newline is added before some visible character on the line, the character is inserted properly and no freeze occurs."
1713734,2017-08-31 12:37:03 UTC,I solved this problem by upgrading libpcre3 to the latest version. It was being held back previously.
1713735,2017-08-29 15:39:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/498845"
1713735,2017-08-29 15:42:42 UTC,"Aug 28 10:22:51.522922 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs [None req-3022f65f-b7e0-43b1-8258-e41f75a9f106 tempest-VolumesSnapshotTestJSON-799368090 None] Call to Nova to create snapshot failed: BadRequest: No volume Block Device Mapping with id a10bd120-9b88-4710-bf6e-f1d34de87da2. (HTTP 400) (Request-ID: req-14d58a0b-bc8c-4521-908e-84cfadd7033a)
Aug 28 10:22:51.523057 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs Traceback (most recent call last):
Aug 28 10:22:51.523171 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs   File ""/opt/stack/new/cinder/cinder/volume/drivers/remotefs.py"", line 1459, in _create_snapshot_online
Aug 28 10:22:51.523282 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs     connection_info)
Aug 28 10:22:51.523407 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs   File ""/opt/stack/new/cinder/cinder/compute/nova.py"", line 225, in create_volume_snapshot
Aug 28 10:22:51.523516 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs     create_info=create_info)
Aug 28 10:22:51.523623 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs   File ""/usr/local/lib/python2.7/dist-packages/novaclient/v2/assisted_volume_snapshots.py"", line 43, in create
Aug 28 10:22:51.523728 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs     return self._create('/os-assisted-volume-snapshots', body, 'snapshot')
Aug 28 10:22:51.523831 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs   File ""/usr/local/lib/python2.7/dist-packages/novaclient/base.py"", line 361, in _create
Aug 28 10:22:51.523949 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs     resp, body = self.api.client.post(url, body=body)
Aug 28 10:22:51.524098 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs   File ""/usr/local/lib/python2.7/dist-packages/keystoneauth1/adapter.py"", line 294, in post
Aug 28 10:22:51.524215 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs     return self.request(url, 'POST', **kwargs)
Aug 28 10:22:51.524320 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs   File ""/usr/local/lib/python2.7/dist-packages/novaclient/client.py"", line 83, in request
Aug 28 10:22:51.524424 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs     raise exceptions.from_response(resp, body, url, method)
Aug 28 10:22:51.524542 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs BadRequest: No volume Block Device Mapping with id a10bd120-9b88-4710-bf6e-f1d34de87da2. (HTTP 400) (Request-ID: req-14d58a0b-bc8c-4521-908e-84cfadd7033a)
Aug 28 10:22:51.524648 ubuntu-xenial-rax-ord-10656600 cinder-volume[2128]: ERROR cinder.volume.drivers.remotefs"
1713735,2017-08-29 22:51:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/498979"
1713735,2017-08-30 05:15:59 UTC,"Reviewed:  https://review.openstack.org/498845
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=074614f07751f3a10e630fc7344a0794516bb32b
Submitter: Jenkins
Branch:    master"
1713735,2017-09-01 18:30:48 UTC,"Reviewed:  https://review.openstack.org/498979
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b514f93c404b3054d0caff94f37d87cd49d9071b
Submitter: Jenkins
Branch:    stable/pike"
1713735,2017-09-25 14:28:22 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1713735,2017-10-24 12:43:34 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1713736,2019-12-01 20:00:10 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1713736,2020-01-31 04:17:28 UTC,[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]
1713738,2018-05-11 15:35:17 UTC,This change was made by a bot.
1713739,2019-09-25 08:46:33 UTC,This was fixed as part of the fix for bug 1707252
1713739,2017-08-29 16:39:27 UTC,"I uploaded the patch, which extends the server moving testcase class with custom resources (WIP actually, but good enough for reproduction now):
https://review.openstack.org/497399"
1713739,2017-08-29 14:52:59 UTC,Lajos has a regression test for it as well and he will push that up soon.
1713739,2017-08-29 16:40:24 UTC,"Yeah, and the test  actually which shows the trouble:
nova.tests.functional.test_servers.ServerMovingTestsWithCustomResources.test_resize_confirm_same_host"
1713746,2018-03-22 22:27:52 UTC,"Can confirm the bug in Stretch. glxgears reports 45fps because it is using llvmpipe instead of VC4.
When enabling the GL driver via raspi-config, raspi-config should remove/disable /usr/share/X11/xorg.xonf.d/99-fbturbo.conf (e.g. rename it to disable it), but it does not, which results in Xorg not using the GL driver. A manual workaround is renaming this file manually (don't forget to rename it back when disabling the GL driver or you'll get no video!).
So this is IMO at least a bug in raspi-config.
Why jessie gives 180fps in glxgears even when using llvmpipe, I have no idea. llvmpipe is software rendered, it's not VC4 which is hardware rendered."
1713746,2018-03-22 23:10:58 UTC,I opened an issue at https://github.com/RPi-Distro/raspi-config/issues/78
1713747,2017-11-21 21:18:41 UTC,Verification-done for xenial with klibc 2.0.4-8ubuntu1.16.04.4:
1713747,2017-11-22 15:16:18 UTC,This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu1.1
1713747,2017-11-21 23:47:49 UTC,Verification done for isc-dhcp 4.3.5-3ubuntu1.1 as well:
1713747,2017-11-21 22:25:22 UTC,This bug was fixed in the package klibc - 2.0.4-8ubuntu4.1
1713747,2017-11-21 22:24:49 UTC,"The verification of the Stable Release Update for klibc has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1713747,2017-11-21 22:24:46 UTC,This bug was fixed in the package klibc - 2.0.4-8ubuntu1.16.04.4
1713747,2017-11-21 15:18:09 UTC,"Verification-done for zesty, with klibc-utils 2.0.4-8ubuntu4.1:"
1713747,2017-10-04 21:38:48 UTC,"Hello Mathieu, or anyone else affected,"
1713747,2017-11-14 19:48:17 UTC,"Hello Mathieu, or anyone else affected,"
1713747,2017-11-14 19:40:37 UTC,"Hello Mathieu, or anyone else affected,"
1713747,2017-11-10 17:00:53 UTC,This bug was fixed in the package klibc - 2.0.4-9ubuntu2
1713747,2017-10-05 14:29:08 UTC,"Turns out this is something directly in klibc in the case of xenial: since xenial is not yet using isc-dhcp for IPv4 DHCP, since that was deemed too intrusive a change for xenial."
1713747,2017-10-04 21:39:07 UTC,"Please add SRU information to the bug:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template"
1713747,2017-09-19 21:06:49 UTC,This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu2
1713747,2017-11-14 19:50:53 UTC,"I accepted the packages as is. Was worried a bit as the patch is not handling the case of dev->dnsdomainname being NULL when being passed to write_option() (causing a SEGFAULT), but as per discussion with Matt - since upstream doesn't do a check for it != NULL it might mean such a case is not really a possible edge case."
1713749,2018-01-16 13:31:52 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1713749,2018-04-07 18:38:12 UTC,"I am testing ubuntu studio 18.04 beta final and it affects openshot 2.4.1 and flowblade 1.16
<b>Flowblade<b>
<pre>
(flowblade:3098): Gtk-<font color=""#DED82C""><b>WARNING</b></font> **: <font color=""#0039AA"">23:58:21.334</font>: Theme parsing error: gtk.css:597:14: not a number"
1713757,2017-08-29 16:06:10 UTC,"""Raspbian Stretch the library is called ""libbrcmGLESv2.so"" and not ""libGLESv2.so"" as in Jessie."""
1713757,2017-08-30 03:58:36 UTC,"""By chance I decided to run sudo rpi-update this morning: I had updated the OS, so maybe I should update the firmware too. The missing libraries are now back in /opt/vc/lib. They have last modified dates of 22:49 on August 23rd. picam is now working again."""
1713757,2018-03-22 22:19:13 UTC,"I think rpi-update is unsupported for a while now, the normal procedure for updating is via apt-get upgrade/dist-upgrade. Upgrading to newer release versions can be done via editing sources.list and files in sources.list.d."
1713769,2018-01-18 08:29:13 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2004
1713769,2017-09-07 10:28:17 UTC,It is possible that this only happens if ntp jumps the clock forward by a significant amount (several minutes perhaps) whilst mysqld is running.
1713773,2017-08-29 17:00:04 UTC,This change was made by a bot.
1713775,2017-08-30 16:51:29 UTC,Suspend/resume with no obviously open mic handle still reproed this issue a few hours later.  May not be related to suspend/resume with open mic handle as previously stated.
1713775,2020-11-19 06:49:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713782,2017-12-04 11:03:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713783,2017-10-24 12:42:40 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1713783,2017-11-09 13:42:54 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/518733"
1713783,2017-09-25 14:27:43 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1713783,2018-02-22 20:47:52 UTC,"Reviewed:  https://review.openstack.org/498482
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f1215e07a5185a8590104235fcbde4b5a23c3545
Submitter: Zuul
Branch:    master"
1713783,2018-04-16 20:00:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/561707"
1713783,2018-04-17 16:17:09 UTC,"Reviewed:  https://review.openstack.org/505160
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=590fd6d2f8497af83307025c8cb796fb433ae80b
Submitter: Zuul
Branch:    stable/ocata"
1713783,2018-04-20 05:56:02 UTC,"Reviewed:  https://review.openstack.org/518733
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=604954a70a5dbf6a1bf79d8b67e8d92c2bf46386
Submitter: Zuul
Branch:    stable/ocata"
1713783,2018-05-02 12:00:53 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1713783,2019-04-03 10:15:25 UTC,"Verified:
Instance is set to error status after a new evacuation. Instance is not deleted."
1713783,2018-11-30 16:13:54 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/621203"
1713783,2018-12-07 06:39:40 UTC,"Reviewed:  https://review.openstack.org/621203
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c5cd6c8e50201dfaa192cdfbbc64d714eeadcd95
Submitter: Zuul
Branch:    stable/pike"
1713783,2019-01-16 13:47:13 UTC,"Change abandoned by Oleksiy Molchanov <email address hidden> on branch: 9.0/mitaka
Review: https://review.fuel-infra.org/40162"
1713783,2019-01-21 11:44:00 UTC,"Fix proposed to branch: mcp/1.0/mitaka
Change author: Előd Illés <email address hidden>
Review: https://review.fuel-infra.org/40217"
1713783,2019-02-15 11:21:06 UTC,"Reviewed: https://review.fuel-infra.org/40217
Submitter: Pkgs Jenkins <email address hidden>
Branch: mcp/1.0/mitaka"
1713783,2019-03-25 22:22:56 UTC,"Reviewed: https://review.fuel-infra.org/40164
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1713783,2017-09-20 14:55:28 UTC,"Reviewed:  https://review.openstack.org/500144
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aec81e7d98c1ca082abd157dab5cc83b5bedfd89
Submitter: Jenkins
Branch:    master"
1713783,2018-10-25 19:46:10 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/561707"
1713783,2017-09-19 16:03:17 UTC,"Reviewed:  https://review.openstack.org/504979
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a3f286f43d866cd343d26d9bafadecab1c225e4b
Submitter: Jenkins
Branch:    stable/pike"
1713783,2017-08-31 12:44:09 UTC,"I'm also not sure why the _destroy_evacuated_instances method in the ComputeManager is including 'accepted' migrations, since that is set in the API when the migration record is created and doesn't mean the migration is done."
1713783,2017-09-19 02:58:54 UTC,"Reviewed:  https://review.openstack.org/504943
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e87d9f51abea0b1c97628ef02435157da4b334ec
Submitter: Jenkins
Branch:    stable/pike"
1713783,2017-09-19 10:40:23 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/505160"
1713783,2017-08-31 10:24:47 UTC,A regression test was pushed for this bug https://review.openstack.org/#/c/498482/. (It seems that the automatic linking doesn't work in later patch sets)
1713783,2017-08-31 12:33:40 UTC,"https://review.openstack.org/#/c/491808/ could be a related recent regression, but I'm not sure yet."
1713783,2017-08-31 13:09:37 UTC,"It looks like the _destroy_evacuated_instances method in the compute manager has always filtered migrations on the 'accepted' status since originally this code was just meant to cleanup local resources once an evacuation from the source host has started, which is fine. The problem is with removing the source node allocations if the evacuation failed, but if it failed in the conductor, we can fix that here:"
1713783,2017-08-31 13:10:31 UTC,We should backport this as it actually leads to deleting things in the source node...
1713783,2017-08-31 13:14:05 UTC,"I've marked this as a potential security issue. If conductor fails to find a host for the evacuation, the migration record status is left in 'accepted' state and the compute service on the source node, if brought back up, will delete the guest from the source node because of this method pulling in 'accepted' state migration records:"
1713783,2017-08-31 13:15:48 UTC,"We could maybe argue that if the source node is down, the guest is already down, but it's at least not deleted."
1713783,2017-08-31 13:17:46 UTC,I'm really not clear why this is a security issue.
1713783,2017-08-31 12:33:14 UTC,"Somewhere in the evacuate cleanup flow on the source host once it comes back up, we should be comparing local instances and their instance.host to the current host and if they are the same, we shouldn't consider them evacuated. I don't see that happening anywhere though."
1713783,2017-08-31 18:31:48 UTC,OK after talking with a few people we can mark this as public again.
1713783,2017-08-31 19:04:14 UTC,"Agreeing with Tristan et al, and adding the ""security"" bug tag to indicate it's a hardening opportunity (C1)."
1713783,2017-09-01 13:47:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/500057"
1713783,2017-09-01 16:45:09 UTC,"Reviewed:  https://review.openstack.org/500057
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5687c170ea003aafa2720fb00af9d84836bb41df
Submitter: Jenkins
Branch:    master"
1713783,2017-09-01 17:58:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/500144"
1713783,2017-09-18 13:37:45 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/504943"
1713783,2017-09-18 14:50:56 UTC,"Reviewed:  https://review.openstack.org/499237
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a8ebf5f1aac080854704e27146e8c98b053c6224
Submitter: Jenkins
Branch:    master"
1713783,2017-09-19 00:14:18 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/504979"
1713783,2017-08-31 14:51:23 UTC,"I tend to agree with Sean, admin action based security issue are usually classed as type C1 (Not a vulnerability, just a bug with (some) security implications) according to VMT's taxonomy."
1713786,2017-09-12 21:03:12 UTC,"Reviewed:  https://review.openstack.org/499399
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d564266a019cb009ece1a63e5d544698f2bf74d1
Submitter: Jenkins
Branch:    master"
1713786,2017-09-12 21:03:51 UTC,"Reviewed:  https://review.openstack.org/499874
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ed80ddcdd3f9e40f0ada581ac7bd524ec48135b
Submitter: Jenkins
Branch:    master"
1713786,2017-09-12 21:05:10 UTC,"Reviewed:  https://review.openstack.org/499877
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=30946f9a5eeea839631cdb1dba9c26d45f7a8d00
Submitter: Jenkins
Branch:    master"
1713786,2017-09-12 21:05:44 UTC,"Reviewed:  https://review.openstack.org/499878
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5bc137f7ebc266f8a73d6febc7c10d8d648924e0
Submitter: Jenkins
Branch:    master"
1713786,2017-09-15 18:03:07 UTC,"Reviewed:  https://review.openstack.org/503159
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5ee7f9d5c8bd53394ef73a52171b4ded451be45e
Submitter: Jenkins
Branch:    stable/pike"
1713786,2017-09-15 18:30:44 UTC,"Reviewed:  https://review.openstack.org/503163
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=61ad70565e4d241f0a3f01d999e3aaf7a2eef3a3
Submitter: Jenkins
Branch:    stable/pike"
1713786,2017-09-15 18:04:13 UTC,"Reviewed:  https://review.openstack.org/503161
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=21150948246d52060a38e93f98982c2e5c9b347d
Submitter: Jenkins
Branch:    stable/pike"
1713786,2017-09-15 18:30:22 UTC,"Reviewed:  https://review.openstack.org/503162
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d0375c2f9e5cc4dac7f8805382c09dbe6224dcd9
Submitter: Jenkins
Branch:    stable/pike"
1713786,2017-09-15 19:49:07 UTC,"Reviewed:  https://review.openstack.org/503165
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=21d7f8b11f217b7e5ece6868a06df70a7a065b6b
Submitter: Jenkins
Branch:    stable/pike"
1713786,2017-09-25 14:27:57 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1713786,2017-10-24 12:42:47 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1713786,2017-09-12 20:00:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/503165"
1713786,2017-09-15 18:03:52 UTC,"Reviewed:  https://review.openstack.org/503160
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b5ea0d1231009ba1f4a9ba87ecfc05e489c4017f
Submitter: Jenkins
Branch:    stable/pike"
1713786,2017-09-12 20:00:28 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/503163"
1713786,2017-09-07 19:06:46 UTC,"Reviewed:  https://review.openstack.org/499718
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=34f8a351502418d30f137ad49e948802d6b2ab3c
Submitter: Jenkins
Branch:    master"
1713786,2017-09-12 20:00:03 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/503161"
1713786,2017-08-30 13:13:05 UTC,Is there a difference between providing setting the force flag in the API request? I guess in case of force=False the scheduler is involved somehow.
1713786,2017-09-12 20:00:16 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/503162"
1713786,2017-08-31 00:45:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499399"
1713786,2017-08-31 15:26:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/499678"
1713786,2017-08-31 16:47:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/499718"
1713786,2017-09-01 00:33:12 UTC,Actually #2 might be OK if the move claim fails because of how ResourceTracker.drop_move_claim works. We should have a functional test to verify this though.
1713786,2017-08-30 14:41:58 UTC,"Correct, it's like with the live migration API and it's force option:"
1713786,2017-09-01 03:02:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/499877"
1713786,2017-09-01 03:21:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499878"
1713786,2017-09-05 23:52:00 UTC,"Reviewed:  https://review.openstack.org/499678
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f34b487db4864787ad92f5a7d6568f31812f1ddb
Submitter: Jenkins
Branch:    master"
1713786,2017-09-12 19:59:35 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/503159"
1713786,2017-09-12 19:59:47 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/503160"
1713786,2017-09-01 02:49:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/499874"
1713788,2019-09-19 14:49:10 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1713796,2017-09-21 23:15:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/506414"
1713796,2017-09-22 02:27:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506458"
1713796,2017-09-25 16:15:40 UTC,"Reviewed:  https://review.openstack.org/506414
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=56232e5de9cd2b74a2879e2e9c09099c0de2609e
Submitter: Jenkins
Branch:    master"
1713796,2017-09-25 16:31:11 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/507196"
1713796,2017-09-25 16:31:29 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/507197"
1713796,2017-10-25 19:22:31 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1713796,2017-10-24 12:42:24 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1713796,2017-10-05 04:08:56 UTC,"Reviewed:  https://review.openstack.org/507197
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a2e0bfdea8b36755e01e210f11f206f436e8d8ec
Submitter: Jenkins
Branch:    stable/pike"
1713796,2017-09-25 16:38:10 UTC,"Reviewed:  https://review.openstack.org/506458
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f18202185d05e3f7e89fca6bbc17daf3c5dc4b98
Submitter: Jenkins
Branch:    master"
1713796,2017-10-05 03:16:12 UTC,"Reviewed:  https://review.openstack.org/507196
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=819aea74f3952ff39580396cf0dbfe98e2ee259d
Submitter: Jenkins
Branch:    stable/pike"
1713803,2018-02-16 16:53:41 UTC,"Ubuntu has long carried a patch which ""Eliminate all references to /etc/resolvconf/run."" However, freedombox-setup contains the following code in a preseed file."
1713803,2018-02-16 18:17:42 UTC,ndisc6 appears to Recommends: resolvconf (in rdnssd); will drop to a Suggests. The code in the merge hook for resolvconf already checks whether resolvconf is present before making use of it.
1713803,2018-02-16 18:26:58 UTC,"It looks like open-iscsi makes use of resolvconf in debian/net-interface-handler, but does check for its presence before doing so. That said, there is not additional integration with anything to set nameservers/search domains, so open-iscsi will need further investigation to see if all is well with it when resolvconf is not present and the iSCSI server is configured with an FQDN rather than a straight IP address."
1713803,2018-02-16 18:38:58 UTC,vpnc and vpnc-scripts check for existance of /sbin/resolvconf and only Suggests: resolvconf. DNS integration by modifying /etc/resolv.conf (and thus the systemd symlink) should work appropriately and let systemd-resolved know about the new nameservers.
1713803,2018-02-16 19:24:32 UTC,"dnsmasq Suggests: resolvconf only, and checks before using it. None of the steps involved would break with resolvconf not being present, integration just happens via /etc/resolv.conf normally."
1713803,2018-02-16 20:06:25 UTC,This bug was fixed in the package ndisc6 - 1.0.3-3ubuntu1
1713803,2018-02-17 00:11:12 UTC,"Marking open-iscsi high, because passing the configured network interface from initramfs to root system needs to be done cleanly in the non-resolvconf world (though this is likely going to be handled via netplan rather than directly to resolved)."
1713803,2018-03-26 20:15:28 UTC,"I had a quick look at unbound, it seems quite difficult. People who install unbound probably want it so they can have DNSSEC supported in their local resolver which we can't really do by integrating with resolved. OTOH, if installing unbound replaces (in some sense) resolved and everything else integrates with resolved, that has problems too."
1713803,2018-03-26 21:07:16 UTC,"dhcpcd5 is redundant as a DHCP implementation in Ubuntu; but it does ""integrate"" with resolvconf by way of its own shipped dhcpcd-hooks/20-resolv.conf. It does check before calling 'resolvconf -a' and 'resolvconf -d' to add/remove its own interface file; and uses this hook file in order to integrate nicely with VPN clients and/or local nameservers."
1713803,2018-03-26 21:15:14 UTC,"postfix takes a copy of resolv.conf for its own use, in its own queue directory. This is already well integrated by way of either resolvconf triggering the copy on changes (using update-libc.d) or by if-up / if-down. This will need work to ""improve"" the integration story; however postfix should still work well in its current state with systemd given that the effective nameserver should remain just the local systemd-resolved."
1713803,2018-03-26 23:12:04 UTC,Looks like the current behavior should be sufficient for postfix to integrate as well as it did with resolvconf: marking this Invalid.
1713803,2018-04-09 19:41:23 UTC,"squid3: same story as sendmail, uses update-libc.d to get notified of nameserver changes."
1713803,2018-04-09 19:54:19 UTC,unbound attempts to add itself as a local resolver (pointing to 127.0.0.1). I think this will require specific integration work so that unbound can properly update/ tell systemd-networkd that it wants to be able to serve as a resolver.
1713803,2018-05-12 03:53:42 UTC,This bug was fixed in the package initramfs-tools - 0.130ubuntu6
1713803,2018-06-19 15:54:04 UTC,How will the initramfs-tools change be validated? What test case will be run to make sure it's working as intended?
1713803,2018-02-10 00:00:36 UTC,"On Fri, Feb 09, 2018 at 10:29:57PM -0000, Brian Murray wrote:

> pump also suggests resolvconf but the pump binary is modified to have a
> --no-resolvconf switch so this seems easy to workaround. It's worth
> noting that the resolvconf support is a separate patch in debian/patches
> so would be easy to drop.
"
1713803,2018-02-09 23:52:52 UTC,pppconfig seems to fall in the same category as dnssec-trigger and dnscrypt-proxy.
1713803,2018-04-09 18:42:09 UTC,"sendmail only uses an update-libc.d script to reload the daemon on changes to resolv.conf, which should be sufficient for DNS resolution to remain working as it did with resolvconf; seeing as the nameserver will generally not change from 127.0.0.53"
1713803,2018-02-09 22:29:57 UTC,pump also suggests resolvconf but the pump binary is modified to have a --no-resolvconf switch so this seems easy to workaround. It's worth noting that the resolvconf support is a separate patch in debian/patches so would be easy to drop.
1713803,2018-02-09 23:36:39 UTC,Integrating openvpn with resolvconf requires the user to take manual action and modify their openvpn .conf file to call /etc/openvpn/update-resolv-conf. That being said it'd be good to help users who rely on this and are upgrading.
1713803,2017-08-29 19:35:29 UTC,"I've added open-iscsi and cloud-initramfs-tools and initramfs-tools as also affects.
These packages are affected by the generic problem where 'configure_networking' from initramfs-tools is executed in the initramfs ('ip=dhcp' for example) and then the link is left up. In those cases we need to apply the /etc/resolv.conf changes from the initramfs to the ""real root"".  I described how this *did* work for the open-iscsi package in the past, but there was no centralized handling of it (although there should have been)."
1713803,2017-08-30 02:24:31 UTC,At https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1713537/comments/1 I described how open-iscsi (iscsi root) works with resolvconf in xenial -> zesty.  We will need a solution for that path as well as 'root=squashfs:http://...../squashfs' that MAAS now uses.
1713803,2017-08-31 20:23:57 UTC,I filed bug 1714308 to cover dns functionality in the initramfs.
1713803,2017-09-20 01:03:27 UTC,avahi's hook is for purposes of disabling .local resolution in the event that a .local domain becomes available as a DNS search domain.  This is the unresolved integration/design issue LP: #327362.
1713803,2017-09-20 01:05:28 UTC,"android-androresolvd: ""This only makes sense to install on a Debian chroot running on Android."""
1713803,2017-09-20 03:41:18 UTC,bind9 integrates with resolvconf to register itself as a DNS server.  It is reasonable to expect something similar for integration with resolved.
1713803,2017-09-20 04:51:36 UTC,"isc-dhcp-client only suggests resolvconf, it does not interface with it."
1713803,2017-09-20 04:21:10 UTC,"dibbler-client doesn't interface with resolvconf, it only recommends it.  This does not warrant carrying an Ubuntu delta."
1713803,2017-10-03 14:56:09 UTC,isc-dhcp now integrates with resolved.
1713803,2017-10-03 15:07:07 UTC,i see no direct calls to resolvconf or hooks installed by cloud-init. Marking incomplete.
1713803,2018-02-06 23:52:26 UTC,fetchmail suggests resolvconf and does not actually utilize it.
1713803,2018-02-07 00:27:02 UTC,fetchmail integrates with resolvconf via /etc/resolvconf/update-libc.d/fetchmail; I think this warrants another look.
1713803,2018-02-07 17:35:35 UTC,"I've looked more closely at fetchmail and while the resolvconf integration isn't critical to it working it does improve fetchmail, so I'm reopening the bug task althought it is a minor issue."
1713803,2018-02-07 23:39:53 UTC,dnscrypt-proxy is another package which suggests resolvconf and one where the integration is not critical. It also seems like a minor issue.
1713803,2018-02-09 19:51:30 UTC,dnssec-trigger actually has and has had a Breaks with resolvconf so that task seems unnecessary.
1713803,2017-09-20 04:52:49 UTC,netscript-2.4 is an alternate network manager package which would make its own technology selections independent of Ubuntu defaults and systemd.
1713807,2018-07-18 11:50:41 UTC,"Reviewed:  https://review.openstack.org/583496
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-radosgw/commit/?id=a2a3250afb29c67924526bd9e1286014557b3027
Submitter: Zuul
Branch:    master"
1713807,2018-07-18 11:46:43 UTC,"Reviewed:  https://review.openstack.org/583494
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=eb5f3ba080d6f1d7c6992e9d0ad6d948c0163ce9
Submitter: Zuul
Branch:    master"
1713807,2018-07-18 12:21:19 UTC,"Reviewed:  https://review.openstack.org/583498
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=58ed31327b63dcde2daa5e1cea3e73d15871b362
Submitter: Zuul
Branch:    master"
1713807,2018-09-19 08:18:09 UTC,"Reviewed:  https://review.openstack.org/583499
Committed: https://git.openstack.org/cgit/openstack/charm-lxd/commit/?id=4d7b3e924008af878b0c369c1bd3e92238d51a93
Submitter: Zuul
Branch:    master"
1713807,2018-07-18 12:59:30 UTC,"Reviewed:  https://review.openstack.org/583497
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=cef0c23583a5ad6c7faa2883486e1fc2f561c618
Submitter: Zuul
Branch:    master"
1713807,2018-07-18 16:21:49 UTC,"Reviewed:  https://review.openstack.org/583501
Committed: https://git.openstack.org/cgit/openstack/charm-odl-controller/commit/?id=18326375bd6de02fd44bdceab3dcb8a3de2d035a
Submitter: Zuul
Branch:    master"
1713807,2018-07-18 10:49:20 UTC,"Reviewed:  https://review.openstack.org/583492
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=fed72d6f2efbbbfaa5af701d4c1cca9e9b10efa5
Submitter: Zuul
Branch:    master"
1713807,2018-07-18 12:56:13 UTC,"Reviewed:  https://review.openstack.org/583500
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=4e7dfc3714e06ab81dfe5bc26625a5cc1be7cda2
Submitter: Zuul
Branch:    master"
1713807,2018-07-18 10:47:09 UTC,"Reviewed:  https://review.openstack.org/583495
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=6847ff93733f3238eeb67c2a098e5f803ff7ca5b
Submitter: Zuul
Branch:    master"
1713807,2017-10-13 15:04:20 UTC,"And, we will need to make sure the specs and bundles in lp:~ost-maintainers/openstack-mojo-specs/mojo-openstack-specs have this relation removed."
1713807,2018-07-17 15:01:30 UTC,"Reviewed:  https://review.openstack.org/499823
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=584a8414fe07a77ba93276e2c569045f8356001e
Submitter: Zuul
Branch:    master"
1713807,2017-10-13 15:17:28 UTC,"Re-triaged the test projects as high, because they will break once the nova-compute charm change lands, which is likely very soon."
1713807,2017-10-13 15:03:41 UTC,We will also need to make a sweep of all lp:openstack-charm-testing bundles to make sure these are removed:
1713807,2017-10-13 15:02:42 UTC,We will need to make a sweep of amulet tests to ensure the following (and similar expressions of the same) are no longer declared:
1713807,2017-10-04 13:59:48 UTC,"For info purposes, nova-conductor was introduced in grizzly: https://blog.russellbryant.net/2013/02/19/deployment-considerations-for-nova-conductor-service-in-openstack-grizzly/ - thus it is present in icehouse/kilo which is still in support."
1713807,2017-08-31 21:56:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499823"
1713807,2017-08-31 21:10:26 UTC,In a functional trusty-icehouse deployment with the relation in place nova-compute does NOT connect to nova.
1713807,2018-07-18 10:33:07 UTC,"Reviewed:  https://review.openstack.org/583493
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer-agent/commit/?id=ddc41e7e4b2256905df53774344c4336965a4285
Submitter: Zuul
Branch:    master"
1713815,2017-09-05 13:41:25 UTC,"What's the best way to proceed forward on this?  Should I report it somewhere else, or should it be assigned to somebody else?"
1713815,2017-08-30 10:15:44 UTC,"I can reproduce this both in a lxd container and in an instance on GCE,
so I don't think this is Docker-image-specific."
1713816,2017-08-29 20:36:08 UTC,"In case it's relevant, I recently ran into an issue that I resolved by reinstalling pantheon."
1713825,2020-09-26 17:11:23 UTC,Does this issue still persist with the latest version of QEMU/libvirt/qxl-drivers ?
1713825,2017-09-27 18:35:34 UTC,I reproduce it on 2.10.0
1713825,2017-09-28 17:46:45 UTC,"Hi Maciej,
  Can you clarify:
     a) What version of the qxl drivers you have installed in windows
     b) Does it crash immediately or only when you do something specific?
     c) Can you give the qemu command line and/or libvirt xml
     d) What resolution have you got the guest set at?
     e) What version are your spice-server libraries at?"
1713825,2017-09-30 18:16:56 UTC,Sorry - email with reply got misdirected in inbox:
1713825,2017-11-14 13:41:49 UTC,"Doesn't reproduce.  It's a newer driver though (10.0.0.18000).
Does updating the driver help?"
1713825,2017-11-14 20:45:07 UTC,It helps but I'm quite sure that lower level security systems (guest) should never be able to crash higher level security systems (hypervisor).
1713825,2017-11-15 07:43:27 UTC,"Guest triggerable assert() isn't exactly nice indeed.
But it's not a show stopper.
It doesn't allow exploiting the host, the guest can only DoS itself.
And you must be priviledged in the guest to do so."
1713825,2020-11-26 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1713834,2017-12-08 19:17:10 UTC,this seems similar to bug #1725834
1713857,2017-11-29 00:58:11 UTC,"Reviewed:  https://review.openstack.org/498983
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5b008c6540f948d28dc50a0ef84095ebd96d198d
Submitter: Zuul
Branch:    master"
1713857,2017-11-29 15:35:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/523910"
1713857,2017-11-29 15:35:47 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/523911"
1713857,2017-12-07 23:55:51 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1713857,2018-01-13 00:54:32 UTC,"Reviewed:  https://review.openstack.org/523910
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3dbcf9d5be0f631f4d963117a242006df3649b8d
Submitter: Zuul
Branch:    stable/pike"
1713857,2018-01-13 00:55:33 UTC,"Reviewed:  https://review.openstack.org/523911
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aa0e4ebd2c02c042bbe2c0d58e690e3e43b04a17
Submitter: Zuul
Branch:    stable/ocata"
1713857,2018-02-15 23:53:54 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1713857,2018-05-02 12:05:20 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1713857,2017-08-29 23:00:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/498983"
1713871,2018-09-13 20:46:27 UTC,"This is a horrible workaround, please don't use it."
1713871,2018-08-07 21:50:44 UTC,"Is there a workaround for this? I seem to be unable to get mojo working on bionic, getting this same error."
1713871,2017-10-18 17:35:50 UTC,bundletester pinned websocket-client to <=0.40.0 https://github.com/juju-solutions/bundletester/commit/78b7b5b2707d1f6eaa507b38b33a1eccf715c3d9
1713871,2017-09-19 13:19:44 UTC,"Tagged python-jujuclient, as it appears to be incompatible with the latest websocket_client."
1713871,2017-08-30 13:33:07 UTC,"FYI, this dependency issue is coming from jujuclient:"
1713889,2018-08-28 03:39:34 UTC,sae problem as with #1789317
1713889,2018-09-05 08:24:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713889,2018-09-05 08:24:50 UTC,still happens on 18.04
1713898,2018-05-31 12:47:49 UTC,It does appear as an option in the removable media settings panel in Fedora 28 though.
1713898,2020-04-13 16:16:17 UTC,"Until and including 0.9.19, RPD was the default on Linux Mint 19.3 for camera SD card but the upgrade to .20 and now .22, it is not and it is not possible to change the default of LM to change applications."
1713898,2020-04-13 17:36:17 UTC,"Julian please ask in the Mint Forums why it might be, and report back. Tell them the relevant line in the .desktop file is:"
1713900,2017-08-30 04:29:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499020"
1713900,2017-09-20 20:54:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505811"
1713900,2017-10-07 12:48:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510290"
1713900,2017-10-07 12:59:59 UTC,"Change abandoned by Rico Lin (<email address hidden>) on branch: master
Review: https://review.openstack.org/510290"
1713900,2018-02-08 18:37:00 UTC,"Reviewed:  https://review.openstack.org/505811
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=09d74ffa3cb55e62318e0cd9eac10a9cb0c1a70a
Submitter: Zuul
Branch:    master"
1713900,2018-02-09 17:02:54 UTC,We merged a possible improvement in Queens. Whether to go all the way and alter the dependency graph is something there isn't consensus on. Moving this bug to Rocky.
1713916,2017-08-30 07:08:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499050"
1713918,2017-09-07 22:17:22 UTC,This issue was fixed in the openstack/python-mistralclient 3.1.3 release.
1713918,2018-01-30 21:51:15 UTC,This issue was fixed in the openstack/python-mistralclient 3.2.0 release.
1713931,2017-08-30 07:32:36 UTC,"Using current artful, g-s 3.25.91 and snapd-glib 1.18, looking for ""vlc"" or ""gimp"" in the gnome-shell overview returns a ""no result"", after deleting the snapd plugin and restarting g-s it lists them fine"
1713931,2017-08-30 07:39:00 UTC,"it doesn't seem to block all queries but the ones which should return a deb and a snap, if you look for something which isn't snapped (e.g ""pidgin"") that gets listed"
1713931,2017-08-30 07:39:56 UTC,"the description is a bit misleading, it returns results but only for things which don't have a snap available (e.g ""pidgin""), those which have a deb and a snap don't get listed"
1713931,2017-08-31 01:50:20 UTC,"What seems to be occurring here:
1. GNOME Shell sends the search term to GNOME Software.
2. GNOME Software does a search for this by passing the search term to each plugin.
3. Both the appstream and the snap plugin return results.
4. The IDs are sent back to the Shell.
5. The shell asks for additional metadata on these IDs.
6. For some reason, we don't get data for the snaps, but we do for the appstream IDs.
7. Only some of the metadata is returned to the Shell.
8. The Shell ignores all the results because not all the metadata is there"
1713931,2017-08-31 01:53:45 UTC,This is occurring because a bug in GNOME Software is causing GetResultMetas() to not return metadata for the snap results. This is causing the Shell to ignore all results. It probably should just use the results it can get.
1713931,2017-10-20 11:51:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713931,2018-02-10 20:58:06 UTC,"Not sure if I am experiencing exactly the same bug, but it sounds like it."
1713931,2018-02-10 21:00:11 UTC,"➜  ~ gnome-software --version
gnome-software 3.26.1
➜  ~ gnome-shell --version
GNOME Shell 3.26.2"
1713936,2017-08-30 07:54:41 UTC,"StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 __strdup (s=0x401ecc <error: Cannot access memory at address 0x401ecc>) at strdup.c:41
 decompose_rpath (sps=sps@entry=0x5611855d74a0, rpath=<optimized out>, l=l@entry=0x5611855d7188, what=what@entry=0x5611853cfc02 ""RPATH"") at dl-load.c:585
 _dl_init_paths (llp=0x0) at dl-load.c:762
 dl_main (phdr=<optimized out>, phnum=9, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:1248"
1713936,2017-09-11 17:03:43 UTC,It crashed again after login.
1713936,2017-09-21 08:22:44 UTC,This crash is always accompanied with another crash bug #1715211.
1713937,2018-01-25 09:00:46 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1820
1713937,2017-08-30 13:27:13 UTC,"For the record, we discussed how to reproduce this on chat."
1713937,2017-08-30 13:04:36 UTC,"Jaime,"
1713937,2017-08-30 08:04:16 UTC,"Affects Percona Server 5.6, 5.7 and upstream"
1713941,2020-07-23 09:09:56 UTC,Installed All Basic Controller Services on a Single Machine then tried to install Mistral.
1713945,2017-08-30 08:48:59 UTC,Note: before I compiled the same program for MySQL. I used package libmysqlclient-dev. In this case the function is available in this library.
1713945,2017-09-04 21:42:18 UTC,"Frankly I don't have a clue about this, i'm not even sure whether it is a bug or a user error."
1713945,2017-09-05 15:13:05 UTC,"I suspect this is due to some distinction between libmysqlclient18, libmysqlclient20, and MariaDB's ""drop-in"" replacement of libmysqlclient18 (which in Debian we call libmariadbclient18 to disambiguate)."
1713946,2020-09-14 10:10:26 UTC,Closing because INVALID: Fix released (>=1.0).
1713946,2018-02-26 00:50:51 UTC,"(Xfce, btw.)"
1713946,2018-02-26 00:50:14 UTC,"That should have been Linux Mint, of course."
1713946,2018-02-24 10:48:13 UTC,"Fedora 26(x64), Inkscape 0.92.2, Ukrainian locale. Defect is still
reproducible by initial scenario."
1713946,2018-02-23 12:42:25 UTC,"While waiting on the above, I 'downgraded' Inkscape using the PPA you provided, and oddly end up with Inkscape reporting the same version of ""Inkscape 0.92.2 (unknown"". But it did change, as the document properties window is now what I would call a normal properties window, appropriately sized and looking like I would expect it to. This window is not resizable, but I do not need to. I just wanted to note this as the ability to resize was in my initial query."
1713946,2018-02-23 12:27:28 UTC,"Ahh, I see. The version I have is: 0.92.2+68~ubuntu17.10.1
This version is of a higher version than the one offered at the PPA you provided: 0.92.2-15598+69~ubuntu18.04.1. Is there an alternative way to do this? Maybe I should remove the other PPA, or? I would prefer not to force and lock a version as it seems that usually creates issues."
1713946,2018-02-26 00:49:16 UTC,"So, this is how it looks on Linux Min 18.3, on a 1280x1024 screen, first with the dialog as small as possible:"
1713946,2018-02-23 12:02:36 UTC,"Hi Brian, you'd need to use the PPA at [1] to get the latest build from the 0.92.x branch (i.e. future 0.92.3). The PPA you linked has the latest stable released version (0.92.2)."
1713946,2018-02-23 12:23:29 UTC,Thank you for that information. I have added that PPA and ran update. There was no newer version of Inkscape offered to me.
1713946,2017-10-17 20:44:44 UTC,"I have since upgraded to Ubuntu 17.10, the issue is unchanged. The problem is I cannot save anything with no access to the OK button or what ever label it has."
1713946,2018-01-03 20:24:58 UTC,Duplicate? https://bugs.launchpad.net/inkscape/+bug/1720899
1713946,2018-01-03 20:26:20 UTC,"Could this be fixed here:
https://bugs.launchpad.net/inkscape/+bug/1510831 ?"
1713946,2018-02-24 11:07:20 UTC,"If it helps, I an running Ubuntu MATE 17.10, 64 bit, English UK and US both installed and used."
1713946,2018-02-23 07:22:07 UTC,"I experience the same issue, but my version is not updated. Could you direct me to the PPA to obtain the version to try this on? I am currently on Inkscape 0.92.2 (5c3e80d, 2017-08-06)."
1713946,2018-02-23 07:34:07 UTC,"The PPA was not here in my Ubuntu, so I added it back in. I did the update to version Inkscape 0.92.2 (unknown), from the PPA https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable."
1713946,2018-02-02 17:22:10 UTC,"Partial fixes already landed in master and 0.92.x branches, see previously linked bug #1510831. If you can test those changes and give feedback on any potentially remaining issues in the linked bug this would be very helpful!"
1713948,2017-08-31 07:26:37 UTC,"now I make some investigation for the reason of that behavior
I noticed,that this always happens with very long Folder Names.
conclusion:
The minimum Window with depends on the lenth of the folder (directory) name, caja always shows the ful Folder Name at the ""Orte (places) panel, if you open the folder, caja adjusts the window with that it can show the complete folder name, ad afterwards it is not possible to reduce the window-with."
1713954,2017-09-13 19:52:08 UTC,Please provide the following:
1713954,2017-09-14 16:24:28 UTC,"Ok I've had a look at the swift-proxy charm code to refresh my memory on how this is currently working and can confirm that replicas config is only used by the charm when the builders are first created so modifying this config option post-deployment will not have any effect. This is in fact the intended behaviour i.e. we just didn't add support for this to be changed. I assume that right now, users of this charm are manually updating the builders and re-spinning and syncing the rings manually. As previously mentioned this is not advisable since it will eventually conflict with the charms handling ring maintenance the next time it tries to update the rings in any way. So in my view the way forward is to extend what we have to be able to support updating this setting post-deployment while ensuring that we are able to do this without putting the cluster at-risk. I can see how this might seem suitable as a charm action but since the code that currently handles rings and builders is not controlled by actions (it actually pre-dates actions) and relies on charm config that actions can't set, it probably going to make most sense to extend the existing hook code. I intend to work on a patch to do this and document how it should be done so will post back once i have something."
1713957,2017-11-13 10:50:48 UTC,"Change abandoned by Ciara Stacke (<email address hidden>) on branch: master
Review: https://review.openstack.org/499104
Reason: There are issues with Unisphere that are unfortunately taking some time to rectify - abandoning this patch for the time being until they can be resolved"
1713960,2017-09-02 02:50:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/500241"
1713960,2018-04-11 02:57:13 UTC,"Change abandoned by Kaifeng Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/500241
Reason: This is not the right approach, will figure out a way in the future, just no time for this time."
1713969,2017-08-30 10:23:28 UTC,Happy to aid investigation if not too technical :-)
1713969,2017-08-30 10:38:32 UTC,Crash log attached
1713969,2017-08-30 14:54:35 UTC,To be clear: the crash occurs when trying to change font type and is repeatable.
1713969,2020-07-18 19:38:06 UTC,Can this be reproduced on more recent OS versions? You could also try installing a newer Mono version as described in bug 1786822
1713972,2017-09-01 08:04:57 UTC,Controller get crashes due to this issue
1713976,2019-05-13 04:17:26 UTC,[Expired for Mahara because there has been no activity for 60 days.]
1713976,2017-12-14 02:08:01 UTC,I'm running 7.1 and page edit works for me. Is there a particular part confirmed not to work?
1713976,2017-10-17 23:04:25 UTC,"Hi Kwong,"
1713976,2018-10-28 02:03:14 UTC,Please also mention which version of Mahara you are using.
1713984,2017-08-31 06:48:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713984,2017-08-31 06:56:52 UTC,I am affected by this on Ubuntu MATE 17.10.
1713984,2017-09-06 16:10:12 UTC,"I'm not certain this is related but I did not experience the delay when using lightdm, but do when using gdm3."
1713984,2017-09-07 12:22:46 UTC,"Sony VAIO VPCEB1M1E
Ubuntu 17.10
systemd 234-2ubuntu6 -> boot time: 47 sec
systemd 234-2ubuntu9 -> boot time: 72 sec"
1713984,2017-09-16 07:45:27 UTC,Wild guess: this might be because you have only one network interface that is set to use DHCP but the DHCP server is set not to return any routers. See https://github.com/systemd/systemd/issues/3752 for this type of scenario.
1713991,2017-08-30 12:14:04 UTC,Additional info re bug.
1713991,2017-08-31 12:26:53 UTC,Apport log
1713991,2017-11-23 13:18:05 UTC,"This ""bug"" appears to be the result of an APT RAT. Signature provided by Sguil. Anubis RAT. See attached."
1713991,2017-11-23 13:18:25 UTC,Second attachment
1713991,2017-11-23 13:18:46 UTC,Third attachment
1713991,2017-11-27 18:29:28 UTC,"Hi,"
1713997,2017-12-03 17:21:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713999,2018-03-08 04:09:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1713999,2017-08-30 12:38:39 UTC,Note: this problem occurs on every boot up.
1713999,2017-08-31 01:04:44 UTC,Note: this problem also happens with a Fedora 26 live CD.
1714001,2017-09-12 10:26:42 UTC,still ftbfs on arm64
1714011,2020-06-09 09:32:41 UTC,"Apologies - seems like I had missed the suggestion of ""Cleanup old kolla-toolbox images and containers from Openstack hosts."""
1714011,2020-06-25 08:23:24 UTC,"I'm afraid we can't really bump the ansible version in the Stein kolla-toolbox image. If that works for you, I would suggest using the train image (if it works, although mixing versions is not really supported), or building your own image locally with an ansible version bump."
1714011,2020-06-09 08:37:40 UTC,Hi All
1714011,2019-09-03 12:25:05 UTC,"As stated by Joseph M, and confirmed in IRC by andrein, this issue appears to have been fixed on master by updating packages in kolla-toolbox, commit https://opendev.org/openstack/kolla/commit/e3108d93c69dbad0c575da719f842d36c195a673. It's not clear exactly which part of that change fixed the issue."
1714011,2019-09-03 12:23:57 UTC,I can also confirm that kolla_toolbox from master fixes the issue.
1714011,2019-08-28 00:44:05 UTC,"Confirmed what Florian found, it seems to be an Ansible version issue. It may have been related to Ansible migrating from shade to openstacksdk around that time. Luckily for us this was accidentally resolved via the following commit:"
1714011,2019-07-01 08:24:35 UTC,"Scott, do you have a fix for this?"
1714011,2019-06-07 20:34:59 UTC,This exact issue appeared for me today using ubuntu source stein with kolla from git master. Running deploy with multi domain support enabled causes magnum to fail trying to create magnum_trustee_domain_admin.
1714011,2020-06-25 05:54:05 UTC,Ok I'm back on this issue - it turns out using the kolla-toolbox from `master` is not a good idea if you are on the stein release. This is because the kolla-toolbox in master no longer uses custom ansible modules for creating keystone users.
1714011,2019-02-12 09:55:51 UTC,"Hello,"
1714011,2019-02-12 09:58:29 UTC,Can someone please verify it?
1714011,2017-08-31 10:07:17 UTC,"Hi, could you share logs in -vvv verbose mode to see what output and what parameters are provided.
Looks like a bug in os_user module or python-shade not being idempotent with user/domain already existing."
1714011,2017-09-01 08:34:18 UTC,"That was exactly the problem, funny thing is that when You delete the user and let Ansible create it, reconfigure will fail in the next step (adding an Admin role for the created user).
So either both os_user and os_user_roles modules are both not idempotent or , more likely, there is something wrong with shade!
I've done some testing with my little ansible code, and it looks like both modules have problems when listing users in domain magnum. Running the same thing using API calls or CLI - works like a charm"
1714011,2017-09-01 08:36:06 UTC,Added verbose logs from 2 reconfigure runs ( 1 when user exists and 1 when it does not ).
1714011,2018-09-28 11:12:06 UTC,"Hi,any update on this issue?"
1714011,2018-11-19 15:42:19 UTC,"I am also suffering this issue. Queens. I notice it's marked as incomplete and more info needed.
Is there anything I can add / any info required ? My issue is identical to the original bug reporter. Kolla deployment with domain specific drivers, one domain with LDAP. We cannot now redeploy because of this error. We have to disable magnum which is currently preventing our deploying Kolla OpenStack in production as we need container services."
1714011,2018-06-24 22:45:23 UTC,"This parameter in keystone.conf is enabled：
```
[identity]
domain_specific_drivers_enabled = True
```
**Appearance:**
1> openstack user list only users in the default domain will
be displayed, not all doamin users."
1714011,2018-12-11 06:45:42 UTC,"I had a similar problem, using openstack-ansible for Rocky.
Ansible already has a bug report for this: https://github.com/ansible/ansible/issues/42901"
1714012,2017-09-21 10:33:10 UTC,"Reviewed:  https://review.openstack.org/500819
Committed: https://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin/commit/?id=e4c646942957595a7ff12dff273582cf0b77f542
Submitter: Jenkins
Branch:    master"
1714012,2017-09-26 09:41:43 UTC,"Reviewed:  https://review.openstack.org/501361
Committed: https://git.openstack.org/cgit/openstack/collectd-ceilometer-plugin/commit/?id=f6fd19b620c3ae0d252fa99c1b3f063ff6851164
Submitter: Jenkins
Branch:    master"
1714014,2019-12-18 08:42:49 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1714014,2019-02-19 13:47:41 UTC,Is this still an issue?
1714014,2018-11-13 14:27:40 UTC,"I am all for improving reliability of CI jobs to make the more resilient to networking glitches, still we need to answer few questions before making a change to defaults:"
1714014,2020-01-29 09:53:09 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.opendev.org/617663"
1714014,2018-11-13 14:16:42 UTC,A patch to increase the ssh timeout is ready to review:
1714014,2018-11-13 14:10:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617663"
1714014,2017-08-30 13:57:18 UTC,"As this is intermittent, Importance is not 'critical' - however as this jams the production chain when it does occur, setting to 'high'."
1714014,2018-11-13 14:18:12 UTC,The version of ansible is already update. The current of ansible is 2.5.7 in the project.
1714017,2018-01-26 21:10:33 UTC,"Reviewed:  https://review.openstack.org/514761
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=9a5252ae6ed3f49ec8bd59032c9374b3cb77f78e
Submitter: Zuul
Branch:    master"
1714017,2017-10-26 01:05:22 UTC,"Reviewed:  https://review.openstack.org/514738
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3fc85389e5e500e25cebf4d89094e7d06bf63605
Submitter: Zuul
Branch:    master"
1714017,2017-10-26 01:05:00 UTC,"Reviewed:  https://review.openstack.org/514723
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=59bd2f6adc1777c7c8d7a2f442be965fecb573a0
Submitter: Zuul
Branch:    master"
1714017,2017-10-25 13:13:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515054"
1714017,2017-10-25 13:13:15 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515053"
1714017,2017-10-24 16:52:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514761"
1714017,2017-10-24 16:39:27 UTC,I've got changes up for two pages: config-drive and user-data
1714017,2017-10-24 15:55:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514723"
1714017,2017-10-03 14:25:06 UTC,I don't see any nova proposed changes for this and I'd like to see this fixed sooner than later so we can backport to stable/pike. Is someone working on this?
1714017,2017-10-03 10:07:48 UTC,Marking the python-novaclient component as invalid as these docs belong in the nova tree alone
1714017,2017-09-26 07:48:20 UTC,"Set the status ""In Progress"" because this report has an assignee."
1714017,2017-09-08 06:33:40 UTC,"Not sure why heat was listed here, so mark it as an opinion for now. We surely welcome any improvement with document, but it's not a bug IMO."
1714017,2018-01-30 22:30:33 UTC,This issue was fixed in the openstack/heat 10.0.0.0b3 development milestone.
1714017,2017-08-30 14:10:40 UTC,The Link to the Lost Article Screenshot
1714017,2017-10-24 16:21:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514738"
1714017,2017-09-01 07:09:04 UTC,It seems that documentation is being rewritten now. This changes will affect the structure of the OpenStack documentation.
1714017,2018-02-01 17:30:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540048"
1714017,2018-02-02 04:43:48 UTC,"Reviewed:  https://review.openstack.org/540048
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4ed5e81ee0a7df28547d87e28f2eabe395d4737d
Submitter: Zuul
Branch:    master"
1714017,2018-02-02 19:18:40 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/540495"
1714017,2018-02-05 16:08:15 UTC,"Reviewed:  https://review.openstack.org/540495
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2d49eb8e4f5aaff88ee7288d4fadd07c0e2e499d
Submitter: Zuul
Branch:    stable/pike"
1714017,2018-02-05 19:18:35 UTC,"Reviewed:  https://review.openstack.org/515053
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2c77e4f7c48e8d3984400169bfb1b60ee7004032
Submitter: Zuul
Branch:    stable/pike"
1714017,2018-10-23 15:28:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612730"
1714017,2018-12-18 16:05:35 UTC,"Reviewed:  https://review.openstack.org/612730
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9de70aed23a28dca90dd3e860a5951d4e1a79e44
Submitter: Zuul
Branch:    master"
1714018,2017-08-30 17:22:54 UTC,this is a bug which actually crashes the right part(where push notification is shown). Had to restart mate to fix it. Fellow linux mint 18.2 mate user (I use it by the way) can also feel the freeze/bug by following the link https://bose.ga/rn/notify.html  but yes beware of the freeze that follows
1714018,2017-08-30 15:09:51 UTC,"Just want to make sure wheter the basic notification works properly or not. open terminal and type or copy paste this command without quotes ""notify-send  test message"". If things works out ok I will then provide you an javascript code basically  doing the same thing/mechanism."
1714018,2017-08-30 17:31:06 UTC,this bug affects opera web browser only. Source code to try javascript based push notification can be found here https://github.com/siddht4/push_notification/blob/master/index.html .You can also alternatively try it in opera web browser following this link https://siddht4.github.io/push_notification/    or the one mentioned earlier i.e https://bose.ga/rn/notify.html
1714022,2017-09-12 09:10:17 UTC,"Quoting from AWS documentation:
http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html#RequestWithSTS"
1714022,2017-09-12 08:49:34 UTC,We have found that there is a third environment variable needed for us in order to authenticate with AWS which is a session token.
1714022,2017-09-22 11:35:24 UTC,"I understand the need for temporary credentials but, in my view, having short-lived credentials for a Juju controller might not make a lot of sense in terms of continuous status polling."
1714022,2017-09-11 13:58:04 UTC,The error message says:
1714024,2017-08-30 17:52:26 UTC,"I might also mention that if brave isn't working right in strict mode, please file bugs with the 'snapd-interface' tag or open a forum topic here: https://forum.snapcraft.io/c/snapd and click 'New Topic' in the upper right."
1714024,2017-08-30 17:22:38 UTC,"classic is a feature the snap developer has to set at snap creation time (and means all snap security will be dropped), the brave snap is (luckily) not classic but seems to use strict confinement proper, so you can not ""just refresh to classic"" here ..."
1714030,2017-12-07 13:24:04 UTC,"There is little information here to work with, best I can tell is that some post-installation script returned an error. I can't tell which one, but chances are that the problem is with the package that provided the script and not actually with linux-firmware."
1714030,2017-12-06 16:17:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714032,2017-09-11 11:28:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714037,2019-12-11 04:32:08 UTC,"Hhmm, no other comments.  I think I won't migrate this, and see if it gets reported independantly later."
1714043,2019-09-06 08:14:54 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/271
1714045,2017-08-30 16:40:29 UTC,"Further info: Debian Stretch seems to create the symlink. /etc/alternatives/my.cnf is another symlink, which points to /etc/alternatives/my.cnf."
1714045,2017-08-30 17:29:19 UTC,"Sorry, whatever went wrong there.
/etc/alternatives/my.cnf is a symlink that points to /etc/mysql/mariadb.cnf. The latter works in the config."
1714068,2017-11-20 16:12:50 UTC,This issue was fixed in the openstack/neutron 11.0.2 release.
1714068,2017-10-25 22:47:27 UTC,This issue was fixed in the openstack/neutron 12.0.0.0b1 development milestone.
1714068,2017-09-23 19:29:31 UTC,"Reviewed:  https://review.openstack.org/504515
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=42f90203dde38830882518709e471f105451ff3a
Submitter: Jenkins
Branch:    stable/pike"
1714068,2017-09-19 16:28:14 UTC,"Don't know why the Closes-bug in the commit message didn't trigger an update here, but this merged to master:"
1714068,2017-09-15 20:44:54 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/504515"
1714068,2017-09-15 02:04:12 UTC,"Reviewed:  https://review.openstack.org/501852
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4833852abb864230daecf97bc672ad9a4a9c4267
Submitter: Jenkins
Branch:    master"
1714068,2017-09-07 19:47:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501852"
1714068,2017-09-02 09:29:20 UTC,I think in this case just check to see if the segment is None and treat it as an unbound port like if binding_levels was empty.
1714068,2017-08-30 18:22:33 UTC,A pointer to the review - https://review.openstack.org/#/c/410385/
1714072,2017-08-31 14:23:08 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/499615"
1714072,2017-09-25 14:28:18 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1714072,2017-09-15 18:05:14 UTC,"Reviewed:  https://review.openstack.org/499616
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2b82aa3a9978ecb31632fae6b400d7fe9137c01b
Submitter: Jenkins
Branch:    stable/pike"
1714072,2017-08-31 14:23:23 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/499616"
1714072,2017-10-24 12:43:26 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1714072,2017-08-31 07:00:57 UTC,"Reviewed:  https://review.openstack.org/499270
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=10f8a9aa127cfaecab368e26c3b896e203e301bc
Submitter: Jenkins
Branch:    master"
1714072,2017-09-15 18:04:52 UTC,"Reviewed:  https://review.openstack.org/499615
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=334905a753c660c5f02ec6c03c427ebbbaf4b89a
Submitter: Jenkins
Branch:    stable/pike"
1714072,2017-08-30 19:34:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499270"
1714072,2017-08-30 19:34:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/499269"
1714072,2017-08-30 18:57:42 UTC,I think 400. Since we said you have to provide at least one resource provider:
1714072,2017-08-30 18:54:42 UTC,what should the outcome be here:
1714072,2017-08-31 06:01:50 UTC,"Reviewed:  https://review.openstack.org/499269
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad2d3fc0f806f46382fa3c0a95c2a5d003d40736
Submitter: Jenkins
Branch:    master"
1714074,2020-08-31 18:18:51 UTC,"Same here. Same version of aegisub. But Mint Mate 20. Kernel: 5.4.0-42-generic
I load any .mp4 file to add subtitles. I play the video file. While the video itself plays with correct speed the sound track plays much faster. 3 times as fast? Because the sound track finishes while the video track is around 1/3 of the complete video file."
1714074,2020-10-18 17:57:07 UTC,"I had this issue as well, and this was the setting I changed to fix it:"
1714076,2018-03-09 15:24:51 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1714078,2017-08-30 19:55:50 UTC,I would like it if the delete process checked to see if it was in transit and then removed it from transit as part of the deletion process.
1714078,2017-12-14 19:03:56 UTC,"I would agree with Terran that the deletion of an in transit item should cancel the transit. The In transit status can be delete restricted, but if a user has permission, they can proceed with the deletion. Presumably they have a good reason for deleting the In transit item and shouldn't need to jump through hoops to cancel the transit and then proceed with the deletion."
1714078,2020-09-03 15:58:19 UTC,Was this resolved by bug 1735566 ?
1714081,2017-11-10 10:45:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714082,2019-07-07 22:56:57 UTC,"Reviewed:  https://reviews.mahara.org/10037
Committed: https://git.mahara.org/mahara/mahara/commit/52ce6a21021dafc0a815621e7cbb2bbb81ef22a5
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1714082,2019-06-26 22:34:29 UTC,Title: 2 Error messages when trying to use accented letter in email address on registration page
1714082,2019-07-07 22:49:19 UTC,Still working as expected ✔
1714082,2019-06-25 01:35:44 UTC,Bug Fixed
1714082,2019-07-02 18:33:17 UTC,BUG - 2 Error messages when trying to use accented letter in email address on registration page
1714082,2019-05-29 22:15:32 UTC,"Scenario: Log in as Site admin -> browse to Add user page -> Try creating users with the following emails and verify the Error message displayed
1) Log in as Site admin
2) Browse to Admin menu > Users > Add user
3) Try creating users with the following emails and verify the Error message displayed = ""This email address has already been registered here.""
   a) <email address hidden> = error expected = ""This email address has already been registered here."" ✔
   b) <email address hidden> = error expected = ""This email address has already been registered here."" ✔
   c) <email address hidden> = error expected = ""This email address has already been registered here."" ✔
   d) userā@example.com = error expected = ""Invalid email address"" ✔
   e) <email address hidden> = error expected = ""This email address has already been registered here."" ✔"
1714082,2019-05-22 23:29:07 UTC,"Commit hash: a14b6396b94b750b2c0194ccec4d271c604e75f7
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw"
1714082,2019-05-22 00:58:11 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10037"
1714082,2019-05-31 03:07:06 UTC,This is still an issue
1714085,2017-11-29 18:40:24 UTC,"Nicolas, I was not able to reproduce this. Can you try to reproduce this and share full diagnostic snapshot."
1714086,2018-03-21 10:40:17 UTC,"I cannot reproduce this with the current client version. Please show the output of ""openstack --version"" and ""openstack --debug --insecure catalog show object-store""."
1714089,2017-08-30 20:55:02 UTC,"StacktraceTop:
 Streaming::StreamProcessor::packetsStopped() () from /tmp/apport_sandbox_4O6Pex/usr/lib/libffado.so.2
 IsoHandlerManager::IsoHandler::disable() () from /tmp/apport_sandbox_4O6Pex/usr/lib/libffado.so.2
 IsoHandlerManager::IsoHandler::~IsoHandler() () from /tmp/apport_sandbox_4O6Pex/usr/lib/libffado.so.2
 IsoHandlerManager::pruneHandlers() () from /tmp/apport_sandbox_4O6Pex/usr/lib/libffado.so.2
 IsoHandlerManager::unregisterStream(Streaming::StreamProcessor*) () from /tmp/apport_sandbox_4O6Pex/usr/lib/libffado.so.2"
1714090,2018-12-12 00:51:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714090,2017-09-29 15:40:23 UTC,"Philip, after installation, MAAS configures nodes to PXE-boot, but the GRUB delivered chainloads a locally-installed GRUB on the hard disk. The PXE-boot part is a requirement of the MAAS environment. (If systems booted straight from the hard disk, the MAAS server could not re-deploy them.) Re-thinking the design so that only one GRUB is loaded (via PXE) might help with this problem, but would render the design fragile to the case when the MAAS server becomes unavailable."
1714090,2017-09-28 16:36:42 UTC,"If you are PXE booting, then why do you have grub-efi installed?  If you aren't using it, remove it."
1714090,2017-08-31 21:56:37 UTC,"In principle, we have all the necessary information to:"
1714090,2017-08-31 23:06:57 UTC,"Steve, there have been two problems that are feeding into this bug report, both on MAAS installations to EFI-based nodes, which must normally PXE-boot so that the MAAS server can maintain control of its nodes:"
1714090,2017-08-31 19:12:17 UTC,Comment I made on https://bugs.launchpad.net/maas/+bug/1642298. Was requested to direct it here.
1714090,2017-08-30 20:54:07 UTC,So the concern we are primarily interested on is the upgrade scenario.
1714090,2017-08-31 19:30:33 UTC,I'm copying my comment #49 from bug #1642298 here....
1714092,2018-01-04 09:36:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714092,2018-01-04 09:37:08 UTC,I confirm that this bug is also affecting me on Ubuntu 17.10 - x86_64
1714092,2018-02-26 23:57:52 UTC,Workaround: change line 50 of /usr/share/qreator/qreator/qrcodes/QRCodeLocationGtk.py from
1714092,2019-06-10 22:04:11 UTC,This bug also occurs on Ubuntu 18.04 and is worked around by the change described in Comment #4
1714094,2017-08-31 02:31:55 UTC,Upstream bug # ?
1714094,2017-08-31 09:33:22 UTC,CSV file is too large for attachment. Download it from https://drive.google.com/open?id=0B67lYkmv0ZcsU2R5eVJ5OGZ1eG8
1714094,2017-08-31 09:52:37 UTC,Using VARCHAR column instead of TEXT changes nothing.
1714094,2018-01-25 09:00:47 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1821
1714103,2017-08-30 22:11:22 UTC,Log copied to /auto/cs-shared/bugs/1714103
1714103,2017-08-30 22:32:56 UTC,we address this issue in 4.1.
1714103,2017-10-10 05:06:07 UTC,we are not seeing the issue in the 4.1 latest release. so moving to fix committed state.
1714106,2019-09-19 12:04:25 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1714112,2018-07-24 09:32:59 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1714112,2018-02-27 20:10:26 UTC,My problem above might be slightly different. Have found reference to something similar here - https://www.spinics.net/lists/linux-edac/msg08263.html. I'm not sure....
1714112,2018-02-27 19:58:22 UTC,I think I have same problem on my Intel(R) Xeon(R) CPU E3-1226 v3 on kernel 4.13.0-36-lowlatency:
1714112,2018-02-05 13:50:52 UTC,"A fix for HWE kernels would be most welcome. While some of our systems (for example Ivy Bridge-based) work fine, the newer ones (Broadwell) fail with:
MC0: Giving out device to module sb_edac.c controller Broadwell SrcID#0_Ha#0: DEV 0000:ff:12.0 (INTERRUPT)
EDAC sbridge: Some needed devices are missing
EDAC MC: Removed device 0 for sb_edac.c Broadwell SrcID#0_Ha#0: DEV 0000:ff:12.0
EDAC sbridge: Couldn't find mci handler
EDAC sbridge: Failed to register device with error -19."
1714112,2018-01-17 15:09:42 UTC,I am seeing this problem still occuring in kernel 4.13.0-26-generic:
1714112,2017-12-21 07:31:26 UTC,I am seeing this re-appearing in kernel 4.13.0-21-generic:
1714112,2017-11-27 20:09:51 UTC,The artful 4.13 kernel needs this upstream 4.13.14 patch.
1714112,2017-09-22 22:51:38 UTC,This bug has reappeared in 4.13.0-11.
1714112,2017-09-11 15:21:59 UTC,This bug was fixed in the package linux - 4.12.0-13.14
1714112,2017-09-01 15:06:00 UTC,"Funny, the Kconfig help text says it should be enabled. They need to make up their minds :-P"
1714112,2017-08-30 23:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1714112,2017-10-24 04:16:42 UTC,I'm also seeing this under kernel version 4.13.0-16-generic on artful (17.10).
1714113,2018-06-01 18:08:14 UTC,"Looking through the code, elasticsearch-charm sets port 9300 open for it's cluster peers until the cluster is established, then re-closes port 9300.  Since graylog expects to be relatively a ""peer"" with elasticsearch, this current methodology would not work well without logic change."
1714113,2018-06-01 18:24:28 UTC,"@freiberger for better experience, give this a try https://jujucharms.com/u/omnivector/elasticsearch/"
1714126,2020-05-20 08:21:20 UTC,Raising this issue to field-medium since we have a work-around with proposed PR in place.
1714126,2020-05-19 11:34:12 UTC,This PR: https://code.launchpad.net/~aym-frikha/charm-elasticsearch/+git/elasticsearch-charm/+ref/master
1714126,2017-08-31 21:22:45 UTC,@ivoks great catch
1714126,2017-08-31 13:10:38 UTC,"See the error - ""No up-and-running site-local (private) addresses found, got [name:lo (lo), name:eth0 (eth0), name:lxdbr0 (lxdbr0)]"". It indicates that the IP, whatever AWS (or anyone else) calls it, is a public IP. 172.100.50.142 is a public IP (belong to Time Warner Cable)."
1714126,2017-08-31 08:07:17 UTC,Charm is missing space functionality. Currently it uses hardcoded definition for interface. It listens only on private IPs. IPs you are using are global (public IPs) and therefore elasticsearch refuses to start.
1714126,2017-08-31 09:57:49 UTC,"Hmmm.... I'm just deploying to aws, it has a priavte ip other then the public you see in juju status."
1714126,2020-05-22 05:59:34 UTC,"The limitation of https://code.launchpad.net/~aym-frikha/charm-elasticsearch/+git/elasticsearch-charm/+ref/master is that it restricts the unit to listen on only the private address, which isn't ideal.  I did look to try to add network space support but the charm is written with Ansible and   the template context is supplied by charmhelpers.contrib.templating.contexts.juju_state_to_yaml, and that doesn't have network_get_primary_address(binding).  We could open a fresh bug against charmhelpers if that's what we want - or just open it up to 0.0.0.0, which is covered in https://code.launchpad.net/~xavpaice/charm-elasticsearch/+git/charm-elasticsearch/+merge/384414"
1714126,2017-08-31 10:17:59 UTC,"@ivoks in my case the failing unit only has a private ip, it is deployed to a NAT space that doesn't get a public, only a private."
1714132,2020-06-24 12:40:43 UTC,This has been fixed now with the switch to python3 and updated packages
1714137,2017-09-01 00:13:02 UTC,"mysql  Ver 14.14 Distrib 5.7.18-15, for Linux (x86_64) using  6.0"
1714137,2018-01-25 09:34:18 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3737
1714137,2017-08-31 02:58:22 UTC,Upstream https://bugs.mysql.com/bug.php?id=72131
1714160,2017-08-31 05:31:11 UTC,https://review.openstack.org/#/c/499115/
1714165,2017-10-10 08:10:29 UTC,Please provide a diagnostic snapshot.
1714169,2017-09-01 19:36:26 UTC,"I believe debian-installer has resolvconf integration which used to fake this for us, and this must be extended to fake things for resolved too."
1714178,2019-09-23 13:45:00 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1022.24
1714178,2017-08-31 07:31:46 UTC,apport information
1714178,2017-12-06 12:56:50 UTC,I would contact the authors of the commits.
1714178,2017-12-07 09:34:53 UTC,"refer to this patch:
https://patchwork.freedesktop.org/patch/124918/"
1714178,2017-12-07 09:36:39 UTC,"verified kernel 4.15-rc2 with this patch, 3 X 4K works well.
https://patchwork.kernel.org/patch/10097883/"
1714178,2017-12-08 03:35:01 UTC,"my patch is not acceptable,
Refer to the last comment from Ville Syrjälä
 ""
 Even if this would be correct (which it's not for most platforms at
 least, not quite sure about the very latest hardware), anyone doing
 this should at least do a cursory check of the relevant math in the
 driver to make seure we don't end up with integer overflows.
 """
1714178,2017-12-13 23:33:54 UTC,"I'm not sure if this is the right place to report it, but:
I have a similar problem, I've tried to apply all the patches mentioned here - for i915 driver in the kernel, for modesetting driver in xorg-server and updated mesa to 17.3.0 which is supposed to be updated, but I'm still seeing some sort of corruption - without the patches, the screens would remain black, but with the patches I see something like this - https://bugs.freedesktop.org/attachment.cgi?id=135329"
1714178,2017-12-14 09:41:59 UTC,"Created attachment 136168
dmesg -w with drm.debug=0x5e before patch"
1714178,2017-12-14 09:45:07 UTC,"Created attachment 136169
dmesg -w with drm.debug=0x5e of only applied the change in comment 6"
1714178,2017-12-14 09:48:04 UTC,"Created attachment 136170
dmesg -w with drm.debug=0x5e after my patch in comment 10"
1714178,2017-12-15 08:10:24 UTC,"Created attachment 136189
dmesg -w with drm.debug=0xe of wayland in artful after patch"
1714178,2018-06-05 11:19:18 UTC,I am working on the this feature request.
1714178,2018-06-08 16:19:30 UTC,Here is the first version of the patchset: https://cgit.freedesktop.org/~mperes/xserver/log/?h=3x4k
1714178,2018-09-06 02:17:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714178,2018-09-06 02:18:38 UTC,*** Bug 107840 has been marked as a duplicate of this bug. ***
1714178,2018-09-11 20:32:45 UTC,"This just changed for me... but the hardware may matter, as I'm on Hades Canyon, using the amd gpu, not HD graphics.
A few days ago I updated to the then-latest 4.19-rc2
(and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting
exactly what I did).
Using plain old X (no desktop) on my Hades Canyon, I now see a 16384 x 16384 limit:
$ xrandr
Screen 0: minimum 320 x 200, current 11520 x 2160, maximum 16384 x 16384
Three screens horizontally work.
https://<email address hidden>/msg24954.html looks related."
1714178,2018-09-11 21:17:56 UTC,"I should have mentioned, my Hades has 32GB of RAM.
With 8GB or less of RAM, the problem might persist (if I understand the mailing list posts)."
1714178,2018-09-24 15:23:01 UTC,"I posted a patch series for -modesetting that fixes this issue, and also adds TearFree support: https://gitlab.freedesktop.org/xorg/xserver/merge_requests/24"
1714178,2018-09-27 06:26:22 UTC,This bug was fixed in the package mesa - 18.2.1-1ubuntu1
1714178,2019-08-06 08:40:07 UTC,this will be fixed in the kernel
1714178,2019-06-04 11:29:39 UTC,"The kernel part will be fixed in 5.3, and will be backported to linux-oem-osp1 later"
1714178,2019-05-24 07:02:12 UTC,Thankyou (my bug report a duplicate of this one).
1714178,2019-05-21 05:20:13 UTC,"yeah, thanks! :)"
1714178,2019-05-21 02:54:58 UTC,Update: The patches have been merged to drm-tip: https://cgit.freedesktop.org/drm-tip/commit/?id=1a74fc0b3f49a0603f230b6f087da33bda3d7c66.
1714178,2019-05-20 15:23:23 UTC,Thanks Ville making this!
1714178,2017-12-06 10:17:35 UTC,"Created attachment 135996
extend max buffer size for test."
1714178,2019-05-20 15:13:53 UTC,Took a while but we got there in the end.
1714178,2019-04-04 02:32:55 UTC,"If I understand it correctly, to completely resolve this issue, we will need mesa + xserver + kernel fix, but currently only mesa fix is in place, right?"
1714178,2019-03-19 06:49:42 UTC,This bug is filed to monitor the progress on getting this patchset upstream:
1714178,2019-02-01 05:25:35 UTC,This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1
1714178,2018-12-17 07:46:30 UTC,update on upstream status:
1714178,2018-12-17 07:42:31 UTC,18.2.x backport from cosmic is in bionic-proposed
1714178,2018-12-13 18:10:39 UTC,-- GitLab Migration Automatic Message --
1714178,2019-09-02 13:02:10 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1020.22
1714178,2017-11-20 11:56:36 UTC,I don't know why the 8192 limit never has been raised. Maybe the hardware never adopted for higher resolutions. Anyway:
1714178,2019-04-04 04:53:17 UTC,"more or less, though AIUI the xserver changes aren't necessary if the kernel support is there"
1714178,2017-09-01 09:10:10 UTC,"Created attachment 133921
kern.log"
1714178,2017-09-01 09:11:58 UTC,"Created attachment 133922
Xorg.0.log"
1714178,2017-08-31 07:31:50 UTC,apport information
1714178,2017-08-31 07:32:00 UTC,apport information
1714178,2017-08-31 07:32:01 UTC,apport information
1714178,2017-08-31 07:32:05 UTC,apport information
1714178,2017-08-31 07:32:07 UTC,apport information
1714178,2017-08-31 07:32:09 UTC,apport information
1714178,2017-08-31 07:32:10 UTC,apport information
1714178,2017-08-31 07:32:12 UTC,apport information
1714178,2017-08-31 07:32:13 UTC,apport information
1714178,2017-08-31 07:32:15 UTC,apport information
1714178,2017-08-31 07:32:17 UTC,apport information
1714178,2017-08-31 07:32:18 UTC,apport information
1714178,2017-08-31 07:32:20 UTC,apport information
1714178,2017-08-31 07:32:22 UTC,apport information
1714178,2017-08-31 07:32:04 UTC,apport information
1714178,2017-08-31 07:32:24 UTC,apport information
1714178,2017-09-01 09:08:30 UTC,"Created attachment 133920
Xorg.0.log"
1714178,2017-09-01 08:31:04 UTC,"Created attachment 133919
lsb_release"
1714178,2017-09-01 08:28:55 UTC,"Filed one freedesktop bug for this issue.
https://bugs.freedesktop.org/show_bug.cgi?id=102508"
1714178,2017-09-01 08:25:10 UTC,"Created attachment 133918
Xorg.0.log"
1714178,2017-09-01 08:24:54 UTC,"Created attachment 133917
kern.log (drm.debug=0xe)"
1714178,2017-09-01 08:23:28 UTC,"Created attachment 133916
Screenshot"
1714178,2017-08-31 10:06:18 UTC,"After applying the following patch, there is no pop-up window (#24).
But, all three screens turn into black screens after I click ""apply"" button."
1714178,2017-08-31 07:31:49 UTC,apport information
1714178,2017-08-31 07:46:44 UTC,now install xserver-xorg-hwe-16.04 and attach Xorg.0.log
1714178,2017-08-31 07:32:36 UTC,apport information
1714178,2017-08-31 07:32:28 UTC,apport information
1714178,2017-08-31 07:32:35 UTC,apport information
1714178,2017-08-31 07:32:33 UTC,apport information
1714178,2017-08-31 07:32:32 UTC,apport information
1714178,2017-08-31 08:40:12 UTC,"forget about #25, as you pointed out the bug is in hw/xfree86/drivers/modesetting/drmmode_display.c:"
1714200,2017-09-01 09:58:50 UTC,"Thanks so much Eduard! I think the bug you identified (#1441998) is the problem but unfortunately didn't help me resolve the issue. However, I have reverted to version 0.48 of Inkscape and this does appear to be working so that is what I'll use for now."
1714200,2017-08-31 14:52:22 UTC,Could you please give more details (ideally precise steps on how to reproduce this issue?).
1714200,2017-08-31 17:41:52 UTC,"> OK, thanks for clarification, just wanted to make sure the ""does not
> work at all"" part in 0.92.2 was due to a typo...
"
1714200,2017-08-31 17:35:06 UTC,"OK, thanks for clarification, just wanted to make sure the ""does not work at all"" part in 0.92.2 was due to a typo..."
1714200,2017-08-31 16:15:38 UTC,Thanks for the quick replies Eduard and apologies I
1714200,2017-08-31 17:39:28 UTC,"Related (with details on the text-related issues): bug #1441998
There's also some workarounds presented there as well as the likely source (fontconfig), i.e. might need to be reported upstream."
1714200,2017-08-31 15:02:31 UTC,P.S. While testing I noticed we do in fact have some kind of regression since Inkscape should warn when encountering an invalid command line option. Command line output seems partially broken in 0.92.2 for which I filed bug #1714278.
1714202,2019-03-19 13:23:36 UTC,Is this still an issue?
1714202,2018-12-05 19:20:21 UTC,For the url in the top comment openstack infra does proxy cache centos buildlogs. https://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/templates/mirror.vhost.erb#n172
1714202,2018-12-05 19:12:02 UTC,http://logs.openstack.org/66/594566/8/check/tripleo-ci-centos-7-standalone/dd8b0d8/logs/delorean_logs/9e/86/9e8612fe401331a324fb491dd9a6b4c6740aaa02_dev/rpmbuild.log.txt.gz seems to be an example of this failing against a local repomd.xml file:
1714202,2018-11-29 16:02:19 UTC,This happens again and the failure is not identified by elastic-recheck which means that the original fix was not complete.
1714202,2018-01-04 21:39:33 UTC,"This should be resolved, buildlogs.centos.org is now accessed via caching proxy in openstack-infra."
1714202,2018-11-29 16:05:15 UTC,LogStash query: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ERROR%3Adlrn%3AReceived%20exception%20Error%20in%20build_rpm_wrapper%5C%22%20%20%20AND%20tags%3A%5C%22console%5C%22
1714211,2017-08-31 09:58:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714211,2017-08-31 13:59:42 UTC,"Hello, sure thing."
1714211,2017-10-23 11:23:29 UTC,I tested the panel configuration in Xubuntu and found an option to assign the panel to a fixed screen (like 0/1/2). If the screen is not connected the panel is hidden. Is it posible to make this feature configurable?
1714211,2017-08-31 10:34:53 UTC,Please offer us more like what version of mate interfere and what Ubuntu Mate version
1714214,2019-02-26 13:54:32 UTC,This still seems to be an issue.
1714235,2019-11-10 21:28:02 UTC,The one open issue might be this TODO:
1714235,2019-11-10 21:23:11 UTC,"I'm just going to invalidate this since if you're using microversion < 2.34 you'll get a 400 because of the UnableToMigrateToSelf error from conductor and if you're using >= 2.34 you'll get a 202 response but the operation will fail and a fault will be recorded, there would just be more work to do, e.g. swapping allocations, calling the scheduler, reverting the allocation swap, etc. As long as the instance isn't put into ERROR state though we're probably OK."
1714235,2018-08-03 16:35:33 UTC,The live migration task in conductor will check that the specified host != the instance.host:
1714235,2018-02-12 07:41:13 UTC,https://review.openstack.org/#/c/542689/
1714235,2019-11-10 21:21:41 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/542689
Reason: This is in merge conflict and doesn't seem all that worthwhile anymore since eventually the live migration will fail even if running the conductor task asynchronously."
1714235,2017-08-31 19:17:25 UTC,"The REST API handler code checks this, I just missed that since I was expecting to find it in the nova.compute.api.API.evacuate method:"
1714235,2017-08-31 13:06:10 UTC,The same issue exists for the live migration API if you specify a host and it's the same as instance.host.
1714235,2017-08-31 12:55:14 UTC,Note that the failure mode is different based on if the force flag is True or not.
1714235,2017-08-31 12:23:25 UTC,I've marked this as low severity since it's been a latent bug for a long time and is really just a safeguard against someone shouldn't actually do unless they screwed up.
1714235,2017-08-31 20:01:39 UTC,The evacuate issue was fixed with change Ic468cd57688b370a18cacfc6e0844a8201eb9ab3 but it's still a problem for os-migrateLive.
1714237,2017-11-15 01:10:39 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1714237,2017-10-24 12:50:02 UTC,"Reviewed:  https://review.openstack.org/509926
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=76a3465271bdf48ebf579df77bb93739f39745c0
Submitter: Zuul
Branch:    stable/pike"
1714237,2017-10-24 12:42:13 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1714237,2017-10-24 11:49:03 UTC,"Reviewed:  https://review.openstack.org/509925
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=56914621952811edddf882dc64a167cc6924142b
Submitter: Zuul
Branch:    stable/pike"
1714237,2017-10-06 14:30:35 UTC,"Reviewed:  https://review.openstack.org/507687
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f90c61cd88edce74e3dbfd069beb2c33793d3371
Submitter: Jenkins
Branch:    master"
1714237,2017-10-04 13:30:53 UTC,This is the fix: https://review.openstack.org/#/c/507687/
1714237,2017-10-05 22:22:30 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/509925"
1714237,2017-09-26 08:41:04 UTC,"Reviewed:  https://review.openstack.org/499583
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=143fe79c9e4daf9ab0b10402caea444080d3bf1f
Submitter: Jenkins
Branch:    master"
1714237,2017-09-06 04:24:02 UTC,"Yes I meant this operation:
https://developer.openstack.org/api-ref/compute/#delete-abort-migration"
1714237,2017-09-05 19:18:20 UTC,"By ""delete"" I assume you mean the REST API delete action, which is really canceling an in-progress live migration which should stop things on the destination node."
1714237,2017-08-31 12:42:39 UTC,"Functional test for reproduction (the good assertions commented out, and replaced with the currently working ones):
https://review.openstack.org/499583"
1714237,2017-10-05 22:22:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/509926"
1714237,2017-08-31 12:41:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/499583"
1714244,2019-10-17 08:10:02 UTC,"Is there a separate bug somewhere about actually implementing custom policies? Since 19.10 switched Chromium to Snap this means that not having those is an actual regression compared to 18.10 or 19.04, so I'd say this warrants a slightly higher priority now."
1714244,2017-11-08 15:16:17 UTC,"Given that the denials are harmless and that getting rid of them would require a patch that wouldn't enable sysadmins to actually implement custom policies, I'll lower the importance of that bug."
1714244,2020-11-06 06:00:25 UTC,"@Olivier Ah, sorry, thank you for explaining this. This isn't what I want to do, I was just trying to strip back to the basics of what https://www.chromium.org/administrators/linux-quick-start said to do and demonstrate that it wasn't working."
1714244,2020-11-05 11:20:01 UTC,"""HomepageLocation"" has a bit of a misleading name. It defines only the page that is opened when clicking the homepage toolbar button, which isn't a thing anymore."
1714244,2020-11-05 07:40:55 UTC,"@Olivier Thank you for working on this, but chromium policies do not appear to be working for me."
1714244,2020-11-03 10:48:20 UTC,@Jon: are your policies in /etc/chromium-browser/policies ? Is there a symlink in that directory?
1714244,2020-11-02 21:12:16 UTC,Running Chromium Version 86.0.4240.111 (Official Build) snap (64-bit) on Ubuntu 20.04 and I'm not seeing my policies enforced inside Chromium.
1714244,2020-08-31 20:31:30 UTC,"@Ian, I meant that a snapped application, run as the current user, won't be able to write to its $SNAP_DATA. I just verified that with:"
1714244,2020-08-31 17:45:54 UTC,"@osomon,"
1714244,2020-08-26 13:23:21 UTC,Note to self for testing purposes: https://www.chromium.org/administrators/linux-quick-start
1714244,2020-09-28 14:34:50 UTC,Now really fixed with https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=6f2b87da50bce971f4baadae348331e1bd024cb8.
1714244,2020-08-25 16:13:05 UTC,"The following two commits are an attempt at fixing this:
  https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=bfe4c3bf4e082ca6329040db23bdee858bd204d2
  https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=6c9bd6a725fc7b7d560cc20ac9cee1c7cf84cadf"
1714244,2020-08-26 13:02:33 UTC,"$SNAP_DATA/policies is not writable by the snap, so the import of existing policies won't work.
This would have to be implemented in the transitional deb package's postinst script."
1714244,2019-10-23 10:46:55 UTC,"@Joachim: there's no separate bug for this yet, but you're right that this needs attention. Would you mind filing one to track this separately? If you can attach examples of custom policies that would be great, too."
1714244,2020-03-13 14:12:17 UTC,A separate bug was filed: bug #1866732.
1714244,2020-05-26 15:07:00 UTC,is there any particular reason to not simply adjust the patch to point to $SNAP_DATA/etc/chromium-browser/policies ? after all this is where system-wide configs should go ...
1714244,2017-11-08 15:15:10 UTC,The code in chromium that determines where to look for policies is there: https://cs.chromium.org/chromium/src/chrome/common/chrome_paths.cc?l=482.
1714244,2020-06-11 15:27:14 UTC,"And for migration purposes, ideally the existing policies in /etc/chromium-browser/policies would be copied over to $SNAP_DATA/."
1714244,2020-08-06 20:59:02 UTC,Is there any update or workaround on this issue? This is going to be a problem to everyone in enterprise environments.
1714244,2020-06-11 15:25:57 UTC,"You're right Oliver, the patch should be adjusted to look for policies in $SNAP_DATA."
1714245,2017-09-10 22:38:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714245,2017-10-01 19:26:05 UTC,I added a gnome-shell task since this string comes from gnome-shell.
1714245,2017-10-04 06:47:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714246,2017-09-01 10:36:56 UTC,"I completely agree on the shortcomings.
Let's hope that the Autotools framework is easy to understand and modify..."
1714247,2017-10-12 02:52:43 UTC,"Thanks for the response. I have stopped and started the nova-compute service. The re-starting of nova-compute service is shown in the log (I am not sure why the stopping of nova-compute service is not shown; probably I should use ""raw"")."
1714247,2017-10-13 06:35:33 UTC,"Lucian, thanks. I can reproduce the issue now."
1714247,2017-10-12 09:45:29 UTC,I've added a cmd log that describes and helps recreating the issue. I tried to keep it as simple as possible.
1714247,2017-10-12 04:05:03 UTC,Attach a script log as a file so that the log won't get truncated.
1714247,2017-10-11 09:21:16 UTC,This happens when cleaning up instances that were deleted while the nova-compute service was down. I've checked your paste and I think that the missing step is exactly that: stopping the nova-compute service before deleting the instance and turning it back on afterwards.
1714247,2017-08-31 20:53:28 UTC,Isn't this fixed by https://review.openstack.org/#/c/486955/ so it's a duplicate of bug 1705683?
1714247,2017-09-01 16:13:37 UTC,"The network info fetched here [1] will be empty as it relies on the info cache [2], which won't contain vif details for deleted instances, as far as I can see."
1714247,2017-09-01 15:05:31 UTC,"Can you be more specific where we're not passing through network info or terminating block device connections? Because looking at the periodic task code when it shuts down an instance to delete it locally, we call here:"
1714247,2017-09-01 06:49:45 UTC,"Indeed, I was talking about the compute manager periodic task, sorry for being vague. Updating the description."
1714247,2017-08-31 20:54:03 UTC,"Well, maybe this is something else. Can you be more specific? Are you talking about a periodic task in the compute manager?"
1714247,2017-10-11 08:06:36 UTC,Tested in the latest master branch using devstack:
1714248,2017-12-11 12:13:01 UTC,"This started breaking ironic multinode CI, see investigation in https://bugs.launchpad.net/ironic/+bug/1737395"
1714248,2017-12-12 15:11:27 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/527423"
1714248,2017-12-12 15:12:26 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/517925
Reason: This is using the wrong change ID. I've re-proposed the cherry pick here:"
1714248,2017-12-13 13:41:19 UTC,"Reviewed:  https://review.openstack.org/508555
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e3c5e22d1fde7ca916a8cc364f335fba8a3a798f
Submitter: Zuul
Branch:    master"
1714248,2018-01-26 00:44:07 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1714248,2018-10-03 16:11:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/607626"
1714248,2018-04-02 13:19:10 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1714248,2018-10-03 16:22:37 UTC,"Change abandoned by Jay Pipes (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/607626
Reason: Need to start over with -x"
1714248,2018-10-04 21:32:56 UTC,"Reviewed:  https://review.openstack.org/607626
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=028f03c8c3d3dac4de50aa8658c474395a683d61
Submitter: Zuul
Branch:    stable/ocata"
1714248,2018-10-08 21:48:56 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1714248,2017-11-06 11:31:03 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/517925"
1714248,2018-03-30 17:46:51 UTC,"Reviewed:  https://review.openstack.org/527423
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e95277fa3eba86a7290212313da4dc3c81c286f3
Submitter: Zuul
Branch:    stable/pike"
1714248,2017-09-29 16:14:38 UTC,"Change abandoned by John Garbutt (<email address hidden>) on branch: master
Review: https://review.openstack.org/508508"
1714248,2017-09-28 17:32:17 UTC,"Oh, I think I understand: at the moment, this code is out of the control of ironic itself; it's all handled by the resource tracker."
1714248,2017-09-29 14:00:20 UTC,"Better idea: after rebalance, we must create compute nodes, lets check other compute nodes don't already exist, and either create or re-purpose depending on what happens."
1714248,2017-09-29 13:48:18 UTC,"... another possible fix is to change the ComputeNode.uuid to match the ironic_node.uuid, but we hit the same race above on the first restart after we make this change, as we delete all the auto-generated ComputeNode.uuids and update them to ironic_node.uuids. Although at least we only hit the nasty re-calculate race once... Yuck again."
1714248,2017-09-29 13:17:33 UTC,So idea for brute force fix...
1714248,2017-09-29 13:02:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/508508"
1714248,2017-09-29 12:43:58 UTC,"Oh wait, its totally the compute node uuid. RP uuid=computeNode and name=ironic node uuid"
1714248,2017-09-29 12:27:04 UTC,"The ironic driver just passes the node uuids up to Nova:
https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L718"
1714248,2017-09-29 16:10:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/508555"
1714248,2017-09-28 16:21:31 UTC,"Pursuant to comment #3, why doesn't the new compute host react to the 409 by deleting the old RP?"
1714248,2017-09-13 13:20:16 UTC,"Actually, looking at the ironic logs, the node was being provisioned at the time of the abort and the conductor had locked the node as it was handling the IPA callback."
1714248,2017-09-13 11:34:54 UTC,"Staring at the nova code a little longer, I think I've pieced together what happened."
1714248,2017-09-13 11:05:59 UTC,"I believe I am also seeing this issue. First, a little about the environment."
1714248,2017-09-01 15:52:06 UTC,"This isn't the first time we've seen something like this. I wonder if we should think about what the impact would be if we removed the uniq requirement on the name field of a resource provider. It seems like it will inevitably cause problems as people/services start doing things with placement that span arbitrary boundaries (like time in this case) that matter to the client side, but are meaningless to placement."
1714250,2017-08-31 13:40:01 UTC,"StacktraceTop:
 __GI___libc_free (mem=0x401) at malloc.c:2966
 ?? ()
 __libc_start_main (main=0xf6ba13cd97, argc=1, argv=0x7ffc0fddf5f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc0fddf5e8) at ../csu/libc-start.c:291
 ?? ()"
1714252,2017-09-01 10:40:59 UTC,My goal with the 'preprocess-to-enable' test in alloc.F90 was to have a self-contained file that could be shipped around without turning it into a new library. Note that it has no other dependencies.
1714252,2017-09-01 10:43:48 UTC,"In Siesta we are currently using the convention (for new features) to have preprocessor names of the form SIESTA__XXXXX.
Nick suggested it to avoid possible clashes when a cascade of programs and libraries is compiled. I guess that you have this under control."
1714252,2017-08-31 14:15:50 UTC,A few words to clarify the proposed refactoring.
1714264,2017-08-31 14:18:04 UTC,Please see attached file/patch implementing the suggested fix
1714264,2017-08-31 16:19:09 UTC,"The attachment ""Patch implementing fix"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1714264,2019-04-05 21:20:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714264,2019-04-07 05:23:08 UTC,I can confirm this to be true in the 3.40-3 version which specifically had a change from Debian:
1714264,2020-06-03 11:24:33 UTC,I can't change mtpaint %U to mtpaint %f
1714265,2017-09-01 10:35:18 UTC,"OK.
Do you have a favorite way to invoke the pre-processor? There seems to be quite a lot
of variability in their behavior (cpp (several variants) vs. built-in preprocessor in gfortran, for example). Nick has had a hell of a time with this."
1714265,2017-09-01 10:53:42 UTC,"Yes, the preprocessing variants may be very different from different compiler suites and/or distributions. Generic cpp behaves very different from gcc-cpp, let alone ifort pre-processor."
1714265,2017-09-04 10:22:14 UTC,"My philosophy is to use the "".F90"" extension only and add the following at the beginning of every single Fortran file:"
1714265,2017-09-04 10:57:54 UTC,"I generally have no decide to force something, I am just happy for the current capitalization currently, because it is easy to see whether it makes use of pre-processor statements."
1714265,2017-09-04 12:25:28 UTC,"Your comments are actually of great importance. My priority is that you developers feel at ease with the proposed changes and that they fit as well as possible with the way you like to work. Technology is (or should be) there to help us do our work, not to tell us how to do it."
1714265,2017-09-04 12:39:36 UTC,Ok. Thanks.
1714266,2018-02-15 09:17:20 UTC,"Perfect, I will commence the transition!"
1714266,2018-02-15 10:38:29 UTC,Thanks for your valuable comments Jose!
1714266,2018-02-15 10:18:32 UTC,"I agree with changing to free format, if that helps in any way."
1714266,2018-02-15 09:04:57 UTC,"I agree with upgrading the source code to free-form.
No other development is ongoing now, just the auto-toolization by Yann."
1714266,2018-02-14 22:22:42 UTC,"P.S.: Once you are satisfied with the new build system, we'll be able to talk about wether you want systematic preprocessing or not."
1714266,2018-02-14 22:20:37 UTC,"Re-reading my comments now, I realize that I mixed-up different concepts."
1714266,2017-09-01 11:00:54 UTC,"A comment to the f77 performance issue. This is also something I have never experienced. If one ""mixes"" (as is done throughout siesta and libgridxc) intents with f77 one can get the correct aliasing. And if a simple conversion between format is done, no difference will be experienced (unless f77 weirdness stuff are around the code)."
1714266,2017-09-01 10:32:28 UTC,"These are just comments and questions to try to frame and improve my understanding of the issue.
I broadly agree with you on the need to update the code."
1714267,2017-10-06 22:16:22 UTC,"Hello Scott, or anyone else affected,"
1714267,2017-10-20 18:55:34 UTC,Verification-done on xenial with nplan 0.29~16.04.1:
1714268,2017-08-31 14:29:07 UTC,I'm on Ubuntu 16.04.
1714268,2018-03-07 15:33:25 UTC,There appears to be 4 strings in package descriptions containing a 0 instead of a capital o:
1714268,2018-03-08 11:19:20 UTC,I sent the correction.
1714268,2019-04-01 17:25:06 UTC,Fix not yet released needs-ddtp-pot-update
1714268,2019-12-31 00:02:31 UTC,Fixed since bionic.
1714272,2020-03-31 11:58:26 UTC,"Change abandoned by Spyros Trigazis (<email address hidden>) on branch: master
Review: https://review.opendev.org/489676
Reason: The magnum team is cleaning up the backlog of changes older than 30 days. Feel to restore your patch."
1714272,2018-02-02 18:25:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540475"
1714272,2018-04-25 08:35:23 UTC,"Change abandoned by Michal Nasiadka (<email address hidden>) on branch: master
Review: https://review.openstack.org/540475"
1714272,2018-02-02 17:50:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540465"
1714272,2018-02-02 18:19:02 UTC,"Change abandoned by Michal Nasiadka (<email address hidden>) on branch: master
Review: https://review.openstack.org/540465
Reason: error"
1714277,2018-03-19 18:28:47 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/523976
Reason: Abandoning my patches with no activity for eight weeks - https://etherpad.openstack.org/p/qa-queens-retrospective"
1714277,2021-01-08 16:11:59 UTC,"Based on comment #17, the plan was to push patches addressing this issue in identity tests - the patches have been merged for 2 years.
Based on the merged patches and no activity since then I'm assuming this is done. If that's not the case, feel free to reopen it by providing more current info."
1714277,2019-04-11 08:02:52 UTC,"Reviewed:  https://review.openstack.org/628211
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=7ea7e0a14e6bfdb01972c3cddc26326b12486214
Submitter: Zuul
Branch:    master"
1714277,2019-03-17 21:49:11 UTC,"Reviewed:  https://review.openstack.org/628284
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=bd89841dc6106cd30789edd9879cd35011349481
Submitter: Zuul
Branch:    master"
1714277,2019-03-06 04:26:08 UTC,"Reviewed:  https://review.openstack.org/525244
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=8d94885df02ea0a4826a1f271f011dfefd2c2ca9
Submitter: Zuul
Branch:    master"
1714277,2019-01-22 22:29:59 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/524746"
1714277,2019-01-03 16:18:24 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/524655"
1714277,2018-07-20 06:51:05 UTC,"Reviewed:  https://review.openstack.org/531450
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=87a71821f25c87bb40b7cad6a68b81b7cfd5432e
Submitter: Zuul
Branch:    master"
1714277,2018-07-17 07:13:31 UTC,Thanks for bug report. I am partially agree here.
1714277,2018-07-11 21:39:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/581891"
1714277,2018-07-10 08:53:25 UTC,"Reviewed:  https://review.openstack.org/521981
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=285b3f887ec4cbe5b4f6afe236c390b59f175c89
Submitter: Zuul
Branch:    master"
1714277,2018-03-19 18:28:29 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/524655"
1714277,2020-10-26 09:27:18 UTC,"What is the status here? Is it still in progress? I see that a few patches got merged, can this be considered done?"
1714277,2018-03-19 18:28:06 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/531450"
1714277,2018-03-19 18:26:53 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/521981
Reason: Abandoning my patches with no activity for eight weeks - https://etherpad.openstack.org/p/qa-queens-retrospective"
1714277,2018-01-05 17:46:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531450"
1714277,2017-12-04 16:02:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525244"
1714277,2017-11-29 19:50:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523976"
1714277,2017-11-21 19:03:26 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/499756
Reason: Breaking this up into changes at a per test basis. If the first one goes well I propose more, see for test_tokens test https://review.openstack.org/#/c/521981/"
1714277,2017-11-21 19:01:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521981"
1714277,2017-11-21 18:12:41 UTC,admin tests are not a concern for interoperability based on feedback I got from ML.
1714277,2017-11-10 16:02:28 UTC,Can we discuss this bug in the comments here?
1714277,2017-08-31 18:50:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/499756"
1714277,2018-03-19 18:28:12 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/525244"
1714277,2017-08-31 15:52:00 UTC,Re identity v2 testing: i found using the rest_client results in a 404 too.. http://paste.openstack.org/show/620100/
1714286,2017-11-12 21:04:47 UTC,"Maybe a workaround, using dconf-editor, browse to /org/gnome/shell/extensions/dash-to-dock"
1714286,2017-11-09 07:24:37 UTC,"I think we discussed multiple times (french forum, other bug reports here) that this isn't suitable for a default and why (case with one window differentiating action with multiple windows…)."
1714286,2017-11-08 18:17:41 UTC,"Minimize on click was introduced in Unity Tweak Tool and many users liked it, personally I see no point in classic dock that does not have that functionality, clicking constantly on minimize button requires more mouse work and effort and if I dont use minimize button, but instead use the overview, why bother with a classic dock in the first place? I believe introducing the option for minimize on click in Dock settings would make many users happy."
1714286,2017-09-04 05:43:44 UTC,"Thanks for filing that bug as we discussed on the french forum. I would really go for solution #1 as we were discussing about. Setting it as low as I'm unsure we'll have time to tackle it this cycle, still subscribing to it :)"
1714286,2017-09-04 12:55:58 UTC,I'd prefer :
1714286,2017-09-01 04:42:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714286,2017-11-07 23:25:35 UTC,See https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1723835
1714292,2017-08-31 15:55:28 UTC,"StacktraceTop:
 ?? ()
 DeviceManager::busresetHandler(Ieee1394Service&) () from /tmp/apport_sandbox_RvkoWL/usr/lib/libffado.so.2
 Util::MemberFunctor1<DeviceManager*, void (DeviceManager::*)(Ieee1394Service&), Ieee1394Service&>::operator()() () from /tmp/apport_sandbox_RvkoWL/usr/lib/libffado.so.2
 Ieee1394Service::resetHandler(unsigned int) () from /tmp/apport_sandbox_RvkoWL/usr/lib/libffado.so.2
 Ieee1394Service::resetHandlerLowLevel(raw1394_handle*, unsigned int) () from /tmp/apport_sandbox_RvkoWL/usr/lib/libffado.so.2"
1714302,2019-07-22 21:39:54 UTC,"Hi,"
1714302,2019-11-20 12:37:26 UTC,"The output of ""xrandr -q"" command with the monitor connected:"
1714302,2019-11-20 12:35:38 UTC,"The output of ""xrandr -q"" command with the projector connected:"
1714302,2019-11-20 12:33:32 UTC,I can confirm that the workaround from comment 2 still works. I was hit by this bug recently when attempting to mirror my laptop screen and a projector at work (NEC P502HL-2: https://www.necdisplay.com/p/np-p502hl-2). Both support 1920x1080 resolution but refresh rates differ very slightly and as XFCE tries to find an exact refresh rate match it sets lower 1680x1050 resolution. Unfortunately the projector was really unhappy about this and started to flicker like mad:(. So I had to use the screens in a side by side configuration without mirroring (this made the presentation a bit less comfortable for me:).
1714302,2019-07-23 06:52:40 UTC,"I see. From technical point of view it makes sense, but for a user difference is not important. BTW there is no clone function in XFCE. I suggest to change mirror button behaving:
1) create option (advanced settings) whether to prefer match for refresh rate or for highest resolution
2) based on 1):
- if set to prefer refresh rate, use current approach
- if set to prefer resolution, find matching resolutions and prefer highest refresh rate on each display"
1714302,2019-11-20 13:14:07 UTC,I forgot to mention that I have the current XFCE 4.12.3 from Debian Stretch. I may be able to test this with XFCE 4.12.5 in Debian Buster when I migrate to a new stable (hopefully in a month:). Although I am not sure it will be all that different - maybe in due time Debian backports will offer XFCE 4.14 and I will be able to finally enjoy a new XFCE:). But still XFCE 4.12 is good enough for now since the stability and configurability with readable XML files are the main reasons I use XFCE in the first place on all computers I maintain.
1714302,2019-07-22 23:27:27 UTC,"There is a difference between display ""cloning"" and ""mirror"" mode."
1714302,2019-07-18 01:26:31 UTC,"I'm seeing this problem, past the middle of year 2019!"
1714302,2016-04-22 14:44:57 UTC,"I'm afraid the problem is deeper, see below."
1714302,2018-03-10 14:22:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714302,2016-04-23 18:49:33 UTC,"(In reply to j.novak from comment #5)

> Created attachment 6656 [details]
> Patch for display setting dialog
>
> The patch make mirror function working when xfce_randr_clonable_mode
> function do not allow it.
> New xfce_randr_mirrorable_mode function calls old xfce_randr_clonable_mode.
> When it do not allow cloning, xfce_randr_mirrorable_mode checks whether
> there are one or more common resolutions (same dimensions) on attached
> displays. If it finds it, select the biggest one.
>
> Note: xfce_randr_mirrorable_mode works for two displays only.
"
1714302,2016-04-22 20:24:02 UTC,"Created attachment 6656
Patch for display setting dialog"
1714302,2016-04-22 13:18:21 UTC,"I think bug 11107 is somehow related to this issue that causes the mirror option to be greyed out. If you read through the comments in that bug report, xfsettingsd is not re-activating the display when it is turned on again. When the display dialog is shown, it does not know about the attached and/or reactivated monitor, thus it does not enable the mirror option. Interestingly, it does know that a second display is attached as it presents the options to extend or make the external monitor primary. Searching the code, it appears that the check for the clone option occurs in the xfce_randr_clonable_mode function (http://git.xfce.org/xfce/xfce4-settings/tree/dialogs/display-settings/xfce-randr.c line #651).The check for extended occurs in http://git.xfce.org/xfce/xfce4-settings/tree/dialogs/display-settings/main.c (line 2947)."
1714302,2016-04-20 09:46:39 UTC,"Hello,"
1714302,2015-11-06 20:21:29 UTC,"Just upgraded to 4.12, and I'm hitting this bug as well.  Any chance of a work around or fix in the near future (this bug has been open for nearly 8 months)?"
1714302,2015-03-16 18:00:37 UTC,"Created attachment 6088
Mirror Displays bug"
1714302,2019-01-20 19:00:09 UTC,We've made a large number of improvements in this area recently. Can you please test with the current development release or git master?
1714303,2017-09-05 08:38:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714307,2017-11-07 16:57:24 UTC,"I agree we shouldn't fail if it's not installed, but we will have to try calling it to see what projects have been created, and then just move on if not available."
1714308,2017-09-19 23:11:52 UTC,This bug was fixed in the package initramfs-tools - 0.125ubuntu11
1714323,2017-09-01 00:20:20 UTC,Workaround:
1714323,2017-09-02 05:17:49 UTC,"Review in progress for https://review.opencontrail.org/35216
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1714323,2017-09-08 16:41:23 UTC,"Reviewed:  https://review.opencontrail.org/35216
Committed: http://github.com/Juniper/contrail-packaging/commit/42cb32903d43a3ac5502aac3b491b02984f40a34
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1714323,2017-12-11 18:38:02 UTC,"Review in progress for https://review.opencontrail.org/38250
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1714323,2017-12-12 20:15:53 UTC,"Reviewed:  https://review.opencontrail.org/38250
Committed: http://github.com/Juniper/contrail-packaging/commit/536fc34659b3e33eec8748e18fa1c8d690baf63a
Submitter: Zuul (<email address hidden>)
Branch:    R3.2.3.x"
1714323,2018-01-16 20:00:36 UTC,"Review in progress for https://review.opencontrail.org/38942
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1714323,2018-01-18 18:18:31 UTC,"Reviewed:  https://review.opencontrail.org/38942
Committed: http://github.com/Juniper/contrail-packaging/commit/37769e348c84595af48ffd8451b5904dc3628b5f
Submitter: Zuul (<email address hidden>)
Branch:    R3.1"
1714328,2018-01-16 22:33:02 UTC,"Review in progress for https://review.opencontrail.org/38947
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1714328,2017-12-13 15:54:18 UTC,"Reviewed:  https://review.opencontrail.org/38277
Committed: http://github.com/Juniper/contrail-packaging/commit/3e8c91f22436adb8fb8f485d855e6188e979c53f
Submitter: Zuul (<email address hidden>)
Branch:    R3.2.3.x"
1714328,2018-01-18 18:19:04 UTC,"Reviewed:  https://review.opencontrail.org/38947
Committed: http://github.com/Juniper/contrail-packaging/commit/af6243eed6393be51d3d907ce8a531ab0bed68a4
Submitter: Zuul (<email address hidden>)
Branch:    R3.1"
1714328,2017-09-05 13:59:02 UTC,"Reviewed:  https://review.opencontrail.org/35172
Committed: http://github.com/Juniper/contrail-packaging/commit/57ce5d15e1cc0000d6c24f85dacda85f4de8133b
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1714328,2017-09-01 00:15:08 UTC,"Review in progress for https://review.opencontrail.org/35172
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1714328,2017-12-12 20:16:07 UTC,"Review in progress for https://review.opencontrail.org/38277
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1714331,2017-10-23 21:02:24 UTC,"> Should this be opened as a bug on the `ovmf` Ubuntu package (xenial/zesty/artful)? I'm very familiar with the Ubuntu version policies.
"
1714331,2017-10-23 18:57:48 UTC,See also LP#1725560.
1714331,2017-09-07 12:38:18 UTC,Building the OVMF from the `edk2` current master (89796c69d9) fixes both (non/vfio) issues.
1714331,2017-09-07 11:42:55 UTC,"I was using a version of OVMF from about a year ago which works fine with QEMU 2.8 and 2.9 but doesn't work with 2.10.  I just updated to the latest OVMF from master and everything's working now with QEMU 2.10 and WIndows 10 64 bit, so the old OVMF was the issue."
1714331,2017-09-07 09:37:45 UTC,"I'm using the Ubuntu artful version (0~20161202.7bbe0b3e-1), so I'll need to build a recent OVMF package to verify the solution."
1714331,2017-09-06 14:34:30 UTC,"On Tue, Sep 05, 2017 at 06:42:06PM -0000, Chris Unsworth wrote:

> I think my issue looks like the same.  Sometimes I just get spinning
> dots, and sometimes there is the message about doing an automatic repair
> below the spinning dots before it stops and uses 100% cpu.  I just did a
> git bisect:
"
1714331,2017-09-07 09:23:39 UTC,"Hi Stefan,"
1714331,2017-09-05 10:31:49 UTC,"OK, I'll do that. It will take me a bit of time - I'll timeframe a week."
1714331,2017-09-05 10:14:16 UTC,"Mary: If you have time to run a git bisect that would be very helpful, thanks!"
1714331,2017-09-03 18:49:45 UTC,I am also unable to boot Windows 10 64 bit since updating to 2.10.0.  I was previously using 2.8.0 which worked perfectly.  Windows gets stuck at the big Windows logo with the spinning dots underneath and QEMU uses 100% CPU of 1 core.  I am using kernel 4.11.9 and the following command line:
1714331,2017-09-01 11:26:11 UTC,"> Please try: -machine pc-q35-2.9,accel=kvm,mem-merge=off
"
1714331,2017-09-01 11:03:25 UTC,"Please try: -machine pc-q35-2.9,accel=kvm,mem-merge=off"
1714331,2017-09-05 18:42:06 UTC,"I think my issue looks like the same.  Sometimes I just get spinning dots, and sometimes there is the message about doing an automatic repair below the spinning dots before it stops and uses 100% cpu.  I just did a git bisect:"
1714356,2019-12-11 09:21:27 UTC,"Change abandoned by Bharat Kunwar (<email address hidden>) on branch: master
Review: https://review.opendev.org/499842
Reason: The magnum team is cleaning the backlog of patches and stories. If you still face this issue and you want to work on it please reopen."
1714365,2020-05-24 07:30:20 UTC,Fixed by https://gitlab.com/inkscape/inkscape/-/merge_requests/1673 (fix was cherry-picked to 69d5fb4e2949d9a20ba10ca6503c60636b10b2e0 and is in 1.0)
1714365,2017-09-03 13:10:58 UTC,AFAICT duplicate of bug #1411718.
1714365,2017-09-01 13:44:33 UTC,"Duplicated using CLI on Win 8.1 64bit, Inkscape 0.92.2 (5c3e80d, 2017-08-06)."
1714365,2017-08-31 21:49:51 UTC,"Inkscape 0.92.2 5c3e80d, 2017-08-06
OSX"
1714366,2018-11-27 18:46:07 UTC,"Hello, just to let you know. I can repro this problem on a raspberry3b+ (raspberian with realtime kernel) with serato 2b discs and traktor audio 6 on Mixx2.1.6. I would like to use visual marks on the disc, rather than waveforms on the monitor.
Other than that - really great software!!! :)"
1714366,2017-09-29 22:15:27 UTC,"I was thinking in opening a new bug because this indeed, but I wasn't sure because I think it's related with this."
1714366,2017-09-29 17:46:08 UTC,"Yes, that sounds like a bug, it is worth to change. Isn't this a separate issue?
If yes, please copy you drscribtion to a new bug.
I hope, I will find time to look into it."
1714366,2017-09-29 14:37:22 UTC,"""mind ""and ""don't/doesn't mind"" must be interchanged in #6, sorry."
1714366,2018-09-21 23:54:16 UTC,"Tested xwax under Ubuntu 18.04 and a MixVibes U-MIX44, just in case that this problem comes from there. It seems that it doesn't: xwax makes corrections automatically. In the same cases that Mixxx lose the last position in fast backspins, xwax reports ""Seek to new position Xs."" (X = time value) I understand that Mixxx doesn't do that, so maybe there the problem is."
1714366,2017-09-23 13:48:54 UTC,I finally got the Serato CV02!
1714366,2017-09-01 20:11:21 UTC,"I've just ordered a Serato Control Vinyl (CV02, the recommended one by Xwax). So I guess that in two weeks more or less (maybe ""more more than less"") I'll be able to test it with it as well."
1714366,2017-08-31 22:10:29 UTC,Can anyone confirm this with other types of control vinyl?
1714366,2017-08-31 21:52:36 UTC,"I attach this as well, just in case that there's something different (but I guess not)"
1714366,2017-09-29 14:25:05 UTC,"Ok, I change my mind about the needle drop relevance."
1714387,2019-09-25 04:17:22 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1714387,2019-07-26 09:59:05 UTC,"Rafael,"
1714387,2017-09-01 12:34:49 UTC,"It seems that problem is caused by LEGACY addons.
I Refreshed my Firefox and installed my addons back to it."
1714387,2017-09-01 12:37:50 UTC,See https://support.mozilla.org/en-US/kb/firefox-add-technology-modernizing
1714387,2017-09-01 12:13:29 UTC,It seems that I have the same bug. If I start `firefox` from terminal I get only two lines of text:
1714387,2017-09-01 12:15:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714387,2017-09-01 12:14:05 UTC,My version is 55.0.2+build1-0ubuntu0.16.04.1.
1714396,2017-09-14 17:07:28 UTC,anyone can help to verify this bugs?
1714405,2019-03-27 12:38:12 UTC,https://bugs.launchpad.net/juju/+bug/1613839 is the bug recently addressing an issue with a float. Given that was in bundle code I'm not sure what overlap with the actions it would be here. This also seems more around the idea of upgrading a charm and changing the type of a property in an action file. Juju isn't liking the change to the type?
1714405,2019-03-26 14:37:14 UTC,"I've just tried to implement this option as 'string' and convert it to 'float' later on, but now I got the following error when running the action:"
1714405,2019-03-27 05:02:31 UTC,"https://bugs.launchpad.net/juju/+bug/1613838 is a bug about multi architecture builds for Juju, I'm guessing it is adifferent bug that you are referencing."
1714405,2019-03-26 14:21:48 UTC,"This is related to https://bugs.launchpad.net/juju/+bug/1613838, for which a fix was released in juju 2.5.2"
1714405,2017-09-06 12:26:27 UTC,"YAML tries to interpret things that aren't in quotes as numbers and then
falls back to strings. Also, your shell would be trying to interpret """" on
the command-line. I think the syntax would be"
1714405,2017-09-15 03:12:17 UTC,"Yes, I am pretty sure ""float"" in config.yaml works fine - we have a unit test exercising this."
1714405,2019-03-26 13:52:58 UTC,I've just faced that when trying to implement an action with a param of the 'float' type. When trying to upgrade the charm the following error message is displayed:
1714405,2017-09-01 03:36:25 UTC,"It appears ""number"" is the proper type for a floating point value.  My use of type: float in config.yaml worked in juju 1.25.6.  Perhaps the types changed between versions.  Will use ""number"" for this solution, but more useful expounding upon available types in the upgrade-charm check would be helpful."
1714413,2017-10-12 08:59:02 UTC,related patch - https://review.openstack.org/#/c/499885/3
1714413,2018-09-07 07:17:04 UTC,tracked on story board - https://storyboard.openstack.org/#!/story/1714413
1714414,2017-09-01 13:50:35 UTC,we will fix it 4.1
1714416,2017-09-01 15:58:49 UTC,I generally agree that this is bad behavior and it would be nice if 406 were the response.
1714416,2017-09-04 16:51:46 UTC,Further discussion was here:
1714416,2017-09-06 13:54:24 UTC,"Glance is behaving within acceptable parameters of RFC 7231 (""HTTP/1.1 Semantics and Content"") on this [0]."
1714416,2017-10-03 21:18:52 UTC,Keystone will require some sort of versioning change in order to fix this (e.g. microverions).
1714433,2017-09-03 21:00:44 UTC,"While these error log messages clearly indicate that something went wrong, they don't point to what may have caused the issue. Some additional debugging is going to be required to figure out what went wrong. It may be merely a timeout, or it may be that something failed (and is being seen on the controller as a timeout)."
1714433,2017-09-01 07:57:02 UTC,"I log in the instance,there is also a error in the log:
2017-09-01 02:00:18.175 935 DEBUG trove.guestagent.datastore.experimental.mongodb.service [-] Disconnecting from MongoDB. __exit__ /usr/local/lib/python2.7/dist-packages/trove/guestagent/datastore/experimental/mongodb/service.py:823
2017-09-01 02:00:18.176 935 ERROR trove.guestagent.datastore.service [-] Timeout while waiting for database status to change.Expected state running, current state is shutdown
2017-09-01 02:00:18.177 935 INFO trove.guestagent.datastore.service [-] Service status did not change to running within the given timeout: 180s
2017-09-01 02:00:18.177 935 DEBUG trove.guestagent.datastore.service [-] Attempting to cleanup stalled services. _wait_for_database_service_status /usr/local/lib/python2.7/dist-packages/trove/guestagent/datastore/service.py:343
2017-09-01 02:00:18.178 935 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): ps xaco pid,cmd | awk '/mongo(d|db|s)/ {print $1}' execute /usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:344
2017-09-01 02:00:18.244 935 DEBUG oslo_concurrency.processutils [-] CMD ""ps xaco pid,cmd | awk '/mongo(d|db|s)/ {print $1}'"" returned: 0 in 0.066s execute /usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:374
2017-09-01 02:00:18.246 935 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): sudo kill  execute /usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:344
2017-09-01 02:00:18.274 935 DEBUG oslo_concurrency.processutils [-] CMD ""sudo kill "" returned: 1 in 0.028s execute /usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:374
2017-09-01 02:00:18.275 935 DEBUG oslo_concurrency.processutils [-] u'sudo kill ' failed. Not Retrying. execute /usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:422
2017-09-01 02:00:18.276 935 DEBUG trove.guestagent.datastore.service [-] Cleanup failed. _wait_for_database_service_status /usr/local/lib/python2.7/dist-packages/trove/guestagent/datastore/service.py:347
2017-09-01 02:00:18.276 935 ERROR trove.guestagent.datastore.service Traceback (most recent call last):
2017-09-01 02:00:18.276 935 ERROR trove.guestagent.datastore.service   File ""/usr/local/lib/python2.7/dist-packages/trove/guestagent/datastore/service.py"", line 345, in _wait_for_database_service_status
2017-09-01 02:00:18.276 935 ERROR trove.guestagent.datastore.service     self.cleanup_stalled_db_services()
2017-09-01 02:00:18.276 935 ERROR trove.guestagent.datastore.service   File ""/usr/local/lib/python2.7/dist-packages/trove/guestagent/datastore/experimental/mongodb/service.py"", line 462, in cleanup_stalled_db_services
2017-09-01 02:00:18.276 935 ERROR trove.guestagent.datastore.service     utils.execute_with_timeout(system.MONGODB_KILL % pid, shell=True)
2017-09-01 02:00:18.276 935 ERROR trove.guestagent.datastore.service   File ""/usr/local/lib/python2.7/dist-packages/trove/common/utils.py"", line 239, in execute_with_timeout
2017-09-01 02:00:18.276 935 ERROR trove.guestagent.datastore.service     return execute(*args, **kwargs)
2017-09-01 02:00:18.276 935 ERROR trove.guestagent.datastore.service   File ""/usr..."
1714433,2017-09-04 02:05:25 UTC,"When I modify the time for the timeout, the instance is in a build state for a long time and then it become error, the log shows that
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api [-] Error calling get_filesystem_stats
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api Traceback (most recent call last):
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api   File ""/usr/lib/python2.7/site-packages/trove/guestagent/api.py"", line 63, in _call
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api     result = cctxt.call(self.context, method_name, **kwargs)
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py"", line 157, in call
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api     retry=self.retry)
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api   File ""/usr/lib/python2.7/site-packages/oslo_messaging/transport.py"", line 90, in _send
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api     timeout=timeout, retry=retry)
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 470, in send
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api     retry=retry)
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 459, in _send
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api     result = self._waiter.wait(msg_id, timeout)
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 342, in wait
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api     message = self.waiters.get(msg_id, timeout=timeout)
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 244, in get
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api     'to message ID %s' % msg_id)
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api MessagingTimeout: Timed out waiting for a reply to message ID d25c3687071d40fba5b40f5d3308b3ed
2017-09-01 09:32:59.562 2135 ERROR trove.guestagent.api
2017-09-01 09:32:59.563 2135 ERROR trove.instance.models [-] An error occurred communicating with the guest: Timed out waiting for a reply to message ID d25c3687071d40fba5b40f5d3308b3ed."
1714433,2017-09-04 02:23:23 UTC,"I see, the Correct error log is that:
2017-09-01 21:08:37.376 21576 ERROR oslo.service.loopingcall [-] Fixed interval looping call 'trove.common.utils.poll_and_check' failed
2017-09-01 21:08:37.376 21576 ERROR oslo.service.loopingcall Traceback (most recent call last):
2017-09-01 21:08:37.376 21576 ERROR oslo.service.loopingcall   File ""/usr/lib/python2.7/site-packages/oslo_service/loopingcall.py"", line 136, in _run_loop
2017-09-01 21:08:37.376 21576 ERROR oslo.service.loopingcall     result = func(*self.args, **self.kw)
2017-09-01 21:08:37.376 21576 ERROR oslo.service.loopingcall   File ""/usr/lib/python2.7/site-packages/trove/common/utils.py"", line 200, in poll_and_check
2017-09-01 21:08:37.376 21576 ERROR oslo.service.loopingcall     raise exception.PollTimeOut
2017-09-01 21:08:37.376 21576 ERROR oslo.service.loopingcall PollTimeOut: Polling request timed out.
2017-09-01 21:08:37.376 21576 ERROR oslo.service.loopingcall
2017-09-01 21:08:37.377 21576 ERROR trove.taskmanager.models [-] Failed to create instance ebc5502a-e2cc-43e5-af44-f8196ea49aea. Timeout waiting for instance to become active. No usage create-event was sent.
2017-09-01 21:08:37.404 21576 ERROR trove.taskmanager.models [-] Service status: ERROR
Service error description: guestagent error"
1714434,2019-12-04 08:58:48 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1714434,2018-08-22 07:03:54 UTC,"Actually,I find the same problem today.
[openstack version:kilo]
Totally I created one vpn-service and build 2 site-to-site ipsec-site-connection which stay active.
Then I deleted these 2 site-connections that may lead to pluto-process-deleting but the result is that nothing exists under dir /var/lib/neutron/ipsec but ""ps -ef|grep pluto"" indicates that there are still 4 entries of single-side pluto.
I am not sure if this is a bug or a not-impact detailed issue."
1714434,2019-12-04 08:58:57 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/499929
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1714434,2017-09-04 01:45:50 UTC,"Hi,"
1714434,2017-09-01 09:29:59 UTC,Which device driver are you using to test?
1714434,2017-09-04 05:53:17 UTC,"The neutron version we use is stable newton ,the vpnaas version is stable newton. The IPSec driver I use is libreswan.
VPN configuration file： etc/neutron/vpn_agent.ini
[vpnagent]
vpn_device_driver=neutron_vpnaas.services.vpn.device_drivers.libreswan_ipsec.LibreSwanDriver"
1714446,2017-09-01 23:04:57 UTC,"Unfortunately there are implications to enabling https support on cdimages.ubuntu.com.  Many people use zsync and the use of https would stop that from working, plus the site is owned and operated by Canonical, so it is really up to them if they want to do it or not."
1714446,2017-09-01 22:45:25 UTC,Ultimately the solution is to support https on cdimage.ubuntu.com.
1714446,2017-09-01 21:05:25 UTC,"The same CSS and profile links are embedded in the ""home page"" and other pages as well, however these don't get a degraded security warning."
1714446,2017-09-01 22:26:21 UTC,I have temporarily removed the <form> elements and replaced them with linked buttons and it seems to resolve the issue.
1714447,2017-09-01 17:17:25 UTC,Might be tricky to fix.
1714455,2017-09-01 16:59:56 UTC,"The YAJL JSON parser library that we use for channel filters and new link types currently only supports strict JSON. The 3.16 DB file parser (implemented in Lex & Yacc) actually converts relaxed JSON into strict JSON for YAJL to parse, and IIRC this means that when setting a new link type at run-time you also have to use strict JSON syntax."
1714455,2020-05-19 16:17:33 UTC,The changes to YAJL for this are complete and just need to be pulled into Base.
1714455,2020-08-09 05:47:49 UTC,PR for my json5 branch on GitHub at https://github.com/epics-base/epics-base/pull/86
1714473,2017-09-03 07:09:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/500348"
1714473,2018-04-14 17:32:37 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/500348
Reason: No updates for a very long time. Feel free to restore and update if you wish to continue working on this."
1714482,2017-09-03 21:53:18 UTC,I think that this is related to bug # 1616295 -  we do not read what the file actually say and get the stream from products file not the one that contains images metadata themselves.
1714482,2017-09-15 03:40:55 UTC,"@James Page, @Ryan Beisner (1chb1n),"
1714495,2018-07-13 16:43:37 UTC,Marked 'confirmed' just to triage it.  I'm open to patches or advice on how to handle this.  You've done a good job in the bug description of triaging.
1714495,2019-05-31 09:05:28 UTC,I know this is nearly a year old but there is clearly no way to make netctl work nicely due to the nature of it and systemd.
1714507,2020-09-19 08:21:52 UTC,Closing because INVALID: Incomplete.
1714513,2017-09-04 21:57:11 UTC,Thanks for reporting this bug. Could you please try if the version from https://launchpad.net/~diesch/+archive/ubuntu/experimental works for you? Thanks :-)
1714514,2017-09-01 15:41:59 UTC,This bug was fixed in the package frama-c - 20170501+phosphorus+dfsg-1ubuntu1
1714514,2017-09-01 13:59:40 UTC,"frama-c package, compiles jemalloc with '-C' in CPPFLAGS and thus ftbfs.
Will try to fix frama-c to not use '-C' when compiling jemalloc sub-component.
'-C' is not default CPPFLAG for jemalloc."
1714514,2017-09-01 14:19:10 UTC,"This sort of seems like a classic case of ""don't do that, then""?"
1714517,2018-09-30 12:41:04 UTC,I can reproduce this on cosmic and bionic.
1714518,2018-06-14 09:20:25 UTC,"Hi Daniel, Carlo and everyone!"
1714518,2018-02-15 20:01:36 UTC,This bug was fixed in the package gtk+3.0 - 3.22.28-1ubuntu1
1714518,2018-02-16 09:55:34 UTC,"Ok,"
1714518,2018-02-15 14:42:04 UTC,Still affecting Thunderbird in 14.04LTS.
1714518,2018-02-16 14:20:39 UTC,"Jon, the changelog message said that this bug was fixed in bionic (which is Ubuntu 18.04 Alpha). The bug is not fixed in Ubuntu 14.04 LTS ""Trusty"" yet."
1714518,2018-02-16 15:00:54 UTC,"Thank you to all for your work, from another ""simple user"" really looking
into this fix update :)"
1714518,2018-02-18 15:41:29 UTC,"+1, Thanks for the clarification Jeremy!"
1714518,2018-03-09 21:28:42 UTC,¿Is there a way to resolve this problem in Ubuntu 16.04.4 LTS? Path is not available for this version.
1714518,2018-03-23 07:01:47 UTC,"I am hoping for a patch too...I have in my company users with Xubutu 16.04 and Xubuntu 14.04.
This could seem to be a minor bug, but for users who have their pc in a networks it is very annoying."
1714518,2018-06-14 17:46:00 UTC,Hi Colin
1714518,2018-08-29 12:40:34 UTC,I'm using Debian Stretch. Is it possible to fix this problem using this patch for Ubuntu?
1714518,2018-06-15 20:33:36 UTC,"Hi Jon, Vikrant"
1714518,2018-06-18 06:46:00 UTC,"Thanks Daniel, I will take another look when I'm back in the office with
the network."
1714518,2018-06-18 09:32:04 UTC,"Hi Jon,"
1714518,2018-06-18 11:01:27 UTC,"Ah, ok, that explains why it didn't work.. 😁"
1714518,2018-06-18 11:29:42 UTC,"Canonical doesn't bother fixing anything. They are too busy breaking new
stuff. They expect __you__ to fix it for them."
1714518,2018-08-17 04:25:26 UTC,Artful is EOL.
1714518,2018-12-21 15:30:04 UTC,"Bug fixes are normally uploaded to the development release so that users will get the fix when updating to the next release. As in this case, the bug also exists in the still supported stable releases (Xenial and Trusty), it is necessary to follow the Stable Release Update (SRU) process in order to fix the problem in those releases."
1714518,2018-12-21 15:37:13 UTC,"@adaucyjr: It looks like the same bug has been reported in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899147"
1714518,2018-02-15 13:23:33 UTC,"Colin, yes please. If you want to fix this issue in Ubuntu 16.04 LTS, you also need to fix it in Ubuntu 17.10. (That's because we don't want to introduce avoidable regressions when people upgrade.)"
1714518,2018-06-15 20:14:21 UTC,"Hi,
I am on Ubuntu 16.04, added the ppa, installed the patch and rebooted.  I tried a file in an ssh mounted folder with Geany with the right click Open-as, but it didn't work.  Even when manually trying to open the file from the ssh mount didn't work.
Not sure if the patch made any difference for me."
1714518,2018-02-15 12:57:16 UTC,"Thanks a bunch, Jeremy. Should I provide a backport to the patch for 16.04 ?"
1714518,2018-06-15 08:20:29 UTC,Hi Colin
1714518,2018-02-05 17:27:05 UTC,"Never mind, found it:  https://bugs.launchpad.net/launchpad/+bug/1747469"
1714518,2017-09-01 14:12:37 UTC,"Here's the patch.
It's also been provided upstream at https://bugzilla.gnome.org/show_bug.cgi?id=787128"
1714518,2017-09-04 10:20:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714518,2017-09-07 08:52:43 UTC,Here is a debdiff with that patch integrated. I hope it'll help.
1714518,2017-09-07 10:34:54 UTC,Why do you think showing network shares is supposed to be the default in GTK+ 3?
1714518,2017-09-07 11:59:53 UTC,"Hi,"
1714518,2017-09-07 13:04:17 UTC,"I would also add that even though asking for GTK3 applications like Chromium, Firefox, Thunderbird to call gtk_file_chooser_set_local_only(FALSE) seems like an easy fix, it is not:"
1714518,2017-09-07 15:14:05 UTC,"Hello,"
1714518,2017-10-31 21:02:37 UTC,"Some Ubuntu users are newbies, they do not know about GVFS, FUSE and so on, so they can't suppose to use /media folder for network filesystems."
1714518,2017-10-31 21:14:35 UTC,What is interesting gnome-mplayer shows my SMB/CIFS share.
1714518,2018-02-15 12:16:59 UTC,Thanks @jbicha --- you are moving mountains in Ubuntu theses past few months!
1714518,2017-09-01 16:20:55 UTC,"The attachment ""gtk_3_fix_fuse_mounts.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1714518,2017-10-31 21:21:16 UTC,Gedit and Evince show my SMB/CIFS share. So some applications have problems in their GtkFileChooser dialog code.
1714518,2017-10-31 21:45:05 UTC,For meld see bug 1335457.
1714518,2017-11-03 16:00:38 UTC,"Hi,
Yeah. That bug hits a lot of applications because GTK+3 does things differently than GTK+2 in this regard, which is why I submitted the bugreport (and a patch) to GTK+3 instead of all these applications."
1714518,2017-12-13 15:52:39 UTC,Requesting a sponsor to upload the fix's backport :)
1714518,2018-01-23 09:48:28 UTC,When will this fix be available in an updated version of the 16.04.3 LTS libgtk-3 package ?
1714518,2018-01-23 13:06:21 UTC,"Hi Richard,
Well, somebody from the Ubuntu Sponsors Team would need to notice that patch I've prepared and care enough to handle it..."
1714518,2018-01-26 15:40:36 UTC,In case any Ubuntu/GNOME Dev's are confused about the urgency of this and they don't work in a LAN/WAN-based environment:
1714518,2018-01-26 22:35:48 UTC,"GNOME devs accepted my patch upstream. I made a debdiff to fix the Ubuntu package .Now we're just waiting for an Ubuntu dev with some motivation to fix this.
Chris is right. This regression *in an LTS release even!* and the time it takes to fix it is awfully long."
1714518,2018-01-27 00:09:22 UTC,@colin-colino Awesome!  Thanks for your work on this.
1714518,2017-10-31 21:16:49 UTC,And baobab shows my SMB/CIFS share.
1714518,2018-02-05 16:52:47 UTC,"OK .... so I'm _really_ glad to see the work on this bug progressing and, as such, I've been attempting to ""add myself"" to this bug's ""affected user"" list. However, I have _not_ been able to do so for the past 2-weeks with the error message:  ""timeout, please try again later"". Does anybody know how to create a bug-report for Launchpad, itself?"
1714526,2017-09-05 14:15:14 UTC,"I'm not sure what the best resolution is. The issue is that someone upgraded to a 'manually build' binary/local jujud. When doing so, that would only upload the version on your machine (thus amd64 only). And there are no binaries matching for arm64. Hence the recommendation to not use '--upload-tools' style workflow."
1714526,2017-09-05 20:01:39 UTC,"I discussed this further with Nick Skaggs and dug through the command histories a little more, the upgrade was performed without --upload-tools so if a binary was uploaded, juju did it on its own.  The environment was bootstrapped without --upload-tools and shows that the original binaries came from streams.  It does appear that the upgraded binaries were uploaded, but that decision appears to have happened inside the juju client for reasons now lost to the mists of time.  I would venture to guess that there's another bug similar to https://bugs.launchpad.net/juju/+bug/1696563 lurking in the client code somewhere."
1714526,2017-09-06 20:58:56 UTC,"I've verified that this is not a recurrence of 1696563, both the client machines and controller can access streams.c.c via http and https both, so this is another failure mode."
1714533,2017-09-01 17:01:21 UTC,"Hi David,"
1714533,2017-09-01 20:39:33 UTC,"I've no idea frankly, it certainly still exists in the architecture dropdown of the MaaS UI. We're importing all arm64 images.  Which logs would you like?"
1714533,2017-10-05 13:11:03 UTC,"David,"
1714533,2017-10-05 13:49:11 UTC,"The nodes I have deployed are set up as arm64/xgene-uboot with no minimum kernel defined, they're booted with the ga-16.04 kernel, nothing special."
1714533,2017-10-05 13:50:21 UTC,"I'm honestly surprised they haven't been certified, I thought the Moonshots were a partnership project with HP, they certainly have documentation for Ubuntu on their website..."
1714533,2019-09-19 12:04:28 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1714542,2017-10-10 04:57:06 UTC,"@azzar1, installing the packages from your ppa results in an immediate crash of the session on attempting to login for me.  nothing showing up in /var/crash"
1714542,2017-10-10 05:18:02 UTC,"That's weird. Please revert the PPA using ppa-purge. I need to understand
why nothing shows up in /var/crash."
1714542,2017-10-10 05:58:18 UTC,@thejoe
1714542,2017-10-10 02:00:21 UTC,My apologies for not being able to communicate earlier since I was out of town. I am back now can install via the ppA if you will. Thanks
1714542,2017-10-11 14:04:58 UTC,This bug was fixed in the package gnome-shell - 3.26.1-0ubuntu2
1714542,2017-10-13 05:43:20 UTC,"So for the people that were affected by this crash before and willing to help, can you please install this ppa https://launchpad.net/~azzar1/+archive/ubuntu/gnome-shell-check-nan-2 and wait for the crash to happen and then send me the crash file in /var/crash? There was a problem with apport until few days ago, that's why crash file were not being collected."
1714542,2017-10-10 06:12:22 UTC,"Quite the same crash exposing ""_cogl_onscreen_free: assertion 'onscreen->winsys == ((void *)0)' failed""
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717928"
1714542,2017-10-09 13:07:30 UTC,@thejoe (or others interested to help)
1714542,2017-10-09 08:10:57 UTC,"Hi, my fix is just a workaround. To properly fix the bug we need your help.
I'll pass you a PPA with a customized version of gnome shell that should
give us more insights on what's really going on."
1714542,2017-10-09 11:45:44 UTC,For the moment we can distro patch my workaround to avoid crashing. I'm already working to understand the true problem and propose the proper fix. For the moment it's better to avoid the crash.
1714542,2017-10-09 12:26:44 UTC,"The attachment ""ubuntu_avoid_crash_if_nan.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1714542,2017-10-04 22:05:39 UTC,I'm happy to help.  I've applied the patch from the gnome bug to a local package build.  Haven't seen the crash since but only been a day or so (was crashing on the order of once a week prior)
1714542,2017-10-04 19:07:54 UTC,We need someone that can easily reproduce it to help us debugging the issue. If anyone is willing to help please write me here or on freenode or by email. Thanks.
1714542,2017-09-14 16:00:31 UTC,"This appears to happen much more with the experimental mutter fractional scaling support turned on and scaling set to 150% (and font scaling set to 100%), but also happens without that enabled.  Without it enabled, I have scaling set to 100%, but font scaling set to 150%."
1714542,2017-09-03 06:38:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714542,2017-09-01 15:27:57 UTC,"StacktraceTop:
 st_theme_node_reduce_border_radius (node=node@entry=0x0, width=width@entry=210, height=height@entry=nan(0x400000), corners=corners@entry=0x7ffd3815cae0) at ../src/st/st-theme-node-drawing.c:280
 st_theme_node_paint_borders (state=state@entry=0x8857b0cd28, framebuffer=framebuffer@entry=0x885513cac0, box=box@entry=0x7ffd3815cda0, paint_opacity=paint_opacity@entry=31 '\037') at ../src/st/st-theme-node-drawing.c:1663
 st_theme_node_paint (node=node@entry=0x885612c780, state=0x8857b0cd28, framebuffer=0x885513cac0, box=box@entry=0x7ffd3815cda0, paint_opacity=paint_opacity@entry=31 '\037') at ../src/st/st-theme-node-drawing.c:2598
 st_widget_paint_background (widget=<optimized out>) at ../src/st/st-widget.c:459
 st_label_paint (actor=0x8857b0d0a0) at ../src/st/st-label.c:195"
1714544,2019-02-26 13:55:31 UTC,Is this still an issue?
1714546,2017-09-05 08:52:26 UTC,"Recommended fix would be to not use the @hook('install') decorator, and instead use normal states."
1714546,2017-09-05 10:07:39 UTC,Yeah that works too. It's much more involved because it means rewriting reactive logic in quite a few places but we should benefit in the long term.
1714546,2017-09-05 08:31:56 UTC,Storage hooks run before install so we will always hit this when using juju storage.
1714553,2018-05-06 19:30:35 UTC,Can you still reproduce this with version 5.0.2? I can't.
1714556,2017-09-01 17:42:52 UTC,"During the time that Cinder Volume was down, was the host where Cinder volume service was running able to access the Ceph cluster from the command line?"
1714556,2017-09-05 09:13:21 UTC,"Gorka, I meet this same issue these days. The Ceph correlated volume service is down, but the Ceph cluster could be accessed using command lines and Ceph backend works well."
1714560,2017-10-20 00:34:07 UTC,"This is now possible, so we can make this work, I think."
1714560,2017-10-27 01:10:08 UTC,"Given that we, for now, are not going to allow building dirty trees, this is not as important of a problem to solve. It can be, in general, if we decide it should be, by using a temporary directory with a temporary worktree in a subdirectory, and extract the pristine-tar tarballs to the temporary directory, then copy them to the parent directory."
1714560,2017-10-27 01:11:03 UTC,"@Robie, I'm assigning to you, for now, because it's a matter of questioning what the various methods in build.py should do when in a given repository state."
1714565,2017-09-04 09:10:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714573,2020-09-20 12:01:17 UTC,Closing because INVALID.
1714580,2019-09-19 11:53:47 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1714583,2017-09-01 20:00:07 UTC,This change was made by a bot.
1714583,2018-07-24 09:35:09 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1714597,2019-02-13 21:23:53 UTC,This should be resolved in Stien and is covered with the following review https://review.openstack.org/#/c/636192/
1714597,2019-02-13 21:23:50 UTC,This is addressed by https://review.openstack.org/#/c/636192/ and the whole process is being overhauled in the Stein release. Marking as fixed
1714597,2017-10-10 16:50:19 UTC,This *might* be a related fix here: https://review.openstack.org/#/q/I63817bb3c58a2c44d3e948bdb81005dc2e734c21
1714597,2017-09-14 19:48:24 UTC,"Sorry -- I have been unable to reproduce this error. With the help given from odyssey4me and cloudnull I was able to move past the problem. Now, with how far I've come in my installation procedure, I have not seen this again and am unable to go backwards."
1714597,2017-09-05 16:07:20 UTC,Waiting for confirmation from manual triaging/other bug reporter.
1714597,2017-09-04 12:49:22 UTC,"I have seen multiple reports of there being issues, but inspecting the way it all works right now I don't understand why it's happening. As it stands right now each wheel/venv build process is completely independent per-distro per-arch. This means that if a new arch/distro is added, the requirements and other files checked when doing a build to determine if something has changed should pick up the change (as there are no previous files). I'll have to make some time to build a multi-distro environment to see the problem first-hand."
1714597,2017-10-03 16:57:36 UTC,"We'll leave the bug open, as currently no one has been able to reproduce it."
1714602,2017-09-15 04:18:18 UTC,Is there anything I can do to help get this fixed in xenial?
1714602,2017-09-18 09:40:04 UTC,"Thank you for volunteering! Please see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. If you need any help, please ask in #ubuntu-devel on IRC (Freenode) if you are able."
1714607,2017-09-01 22:49:52 UTC,Preventing users from using insecure/compromised passwords is covered by bug 1714606.
1714617,2020-04-04 14:21:00 UTC,"Hi, using 1.1-dev (6b4d57f, 2020-04-01), I have no problems adding chamfers to a path generated by ""Fill between many"", see attached file. Since Fillet/Chamfer was added only after 0.92.4, I'll close this bug. If you have further issues, please open at Gitlab."
1714624,2017-09-02 10:58:32 UTC,Any way to mark this as a bug in Artful daily builds?
1714625,2017-09-02 05:42:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/500251"
1714625,2017-09-04 02:11:21 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/500251"
1714625,2017-09-08 09:50:30 UTC,"https://review.openstack.org/#/c/453723/ have been fixing this.
So close this bug."
1714630,2017-12-14 04:23:42 UTC,"related issue:
https://bugs.launchpad.net/percona-toolkit/+bug/1738128"
1714630,2018-01-09 17:38:39 UTC,Was this fixed in the related issue?
1714630,2018-01-24 22:26:16 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1442
1714636,2017-09-02 07:00:26 UTC,Screenshot of the error shown by the application
1714645,2019-12-07 12:15:35 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1714645,2020-02-06 04:17:35 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1714646,2018-01-12 22:27:19 UTC,"Thanks for the quick response and kudos on the new UI/UX.
Icons sizes seem to be in the right size.
Feel free to close this issue."
1714646,2018-01-12 19:15:49 UTC,"Go ahead and try out the development version:
https://sourceforge.net/p/inkscape/mailman/message/36176150/
Use the ones with 'master' in the name."
1714646,2018-11-14 07:43:54 UTC,"I have the same issue on 4k retina display on iMac running in Ubuntu with Inkscape 0.92.3
The problem is just with some of the icons of the Inkscape interface. such at the toggle visible layer and lock/unlock layer buttons. Also buttons for specific context in top toolbar."
1714646,2018-01-12 13:52:42 UTC,Temporary work-around:
1714646,2018-01-12 14:25:13 UTC,"As a workaround I downgraded to 0.91, I was hoping you guys would solve it for the next release...
If you need me to test this in order to know that this will solve the problem I don't mind."
1714648,2017-09-02 08:52:10 UTC,"If I try to launch the program through Activities menu, this time toolbox.py crashes (see screenshot)."
1714659,2018-05-26 15:56:50 UTC,"Same issue with HPLIP 3.18.5 on 18.04 LTS, only show on startup. But when I open printer (HP Laserjet p1006), it can print normally."
1714659,2020-02-11 19:48:05 UTC,Same problem on Ubuntu 18.04 - thankfully edelans posted a fix in #19 for removing the message!
1714659,2019-10-30 09:26:39 UTC,"Ubuntu 19.10, Gnome-Session, same problem."
1714659,2019-04-23 01:53:41 UTC,"Ubuntu 18.04.2 fresh install on System 76 Laptop
Downloaded the latest Version of HPLIP 3.19.3
from https://developers.hp.com/hp-linux-imaging-and-printing/gethplip"
1714659,2019-01-09 00:37:32 UTC,"In the above post, I was in error about hplip causing the high CPU usage. I have changed my Desktop management from Gnome to Unity. The hp systray icon is back on the panel. I apologize for the CPU usage mistake."
1714659,2019-01-08 20:49:54 UTC,"I think that is error is now causing very high CPU usage. Typically my CPU load averages are under 1. They usually range like thus: .5 to .8 for all time frames (1 min, 5 min, 15 min). Currently my avgs. are 3.00 to 4.00. These high loads started after HPLIP's ""No systray"" on daily power up."
1714659,2018-10-08 20:40:09 UTC,"I have the very same error, on 18.04.1 and HPLIP-3.18.6"
1714659,2018-07-14 21:04:18 UTC,"I have the very same error, on 18.04 and HPLIP-3.17.10.
Is there any workaround within /etc/xdg/autostart/hplip-systray.desktop to turn this off? - instead of removing the file. completely."
1714659,2018-06-19 20:40:55 UTC,I had this error on every boot on a fresh and up to date ubuntu 18.04 Bionic Beaver after installing the latest drivers for my HP printer.
1714659,2018-06-18 14:52:33 UTC,"same issue Ubuntu 18.04 hplip-3.18.6 at evey boot i get this error when i log in to my account.
Woulud be nice to have this solved."
1714659,2018-05-28 15:09:03 UTC,I try this method from 'Edson Jose dos Santos' from this link.
1714659,2018-05-21 11:57:36 UTC,"Same issue with HPLIP 3.18.4 on 18.04 LTS fresh install. No system tray detected unable to start, but I can print with no problems but no access to scanner functions or faxing."
1714659,2018-03-03 00:07:43 UTC,"I also have this problem.
Every time at startup the ""No system tray detected"" erro message shows up.
I use Ubuntu 17.10 and HPLIP 3.17.11 (last version at the time of writing)."
1714659,2018-05-07 19:35:48 UTC,"Same issue here with official 18.04 LTS release.  I have installed HPLIP 3.18.4,  but I get the error message, No System Tray Detected on this system: Unable to start, exiting.  What's worse is that the HP Officejet printer will not print anything.  It just keeps sending all print jobs to ""pause""."
1714659,2018-05-07 00:05:29 UTC,"Same issue in Ubuntu 18.04 LTS, HPLIP 3.18.4.
Every time at startup a popup error display the message ""No system tray detected"".
Please solve the problem.
Thanks."
1714659,2018-05-05 12:51:15 UTC,"Just purchased and installed an HP printer with software from HP web page, device. I have this same bug.  Ubuntu 18.04, HPLIP 3.18.4, device manager 15.0 (Qt4)"
1714659,2018-04-04 06:05:14 UTC,"Same Issue, and I just run an update, I still get
No system tray detected on this system.
Unable to start, exiting.
on Startup"
1714659,2018-03-27 18:30:33 UTC,Experiencing the same problem with bionic.  Reproducible.
1714659,2018-01-28 16:51:01 UTC,"I also have this bug with HPLIP 3.17.11 on Ubuntu 18.04 - I know this is an alpha, but just to inform."
1714659,2017-12-04 18:45:42 UTC,"To the HPLIP developers at HP: Can you provide a patch which we can apply to the HPLIP 3.17.7 which comes with Ubuntu 17.10, especially if you have fixed this already in a later version (like 3.17.11)? Thanks."
1714659,2017-12-04 18:20:12 UTC,Sorry but this bug was not fully fixed back in September. It's still affecting me in December.
1714659,2017-11-22 17:46:19 UTC,"Ubuntu 17.10 with all updates, however, this problem persists for me.  I would not describe it as ""fixed""."
1714659,2017-09-29 11:58:28 UTC,Ubuntu 17.10 with all updates. Bug is fixed.
1714659,2017-09-02 11:15:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714659,2018-05-09 16:53:23 UTC,"Just purchased and installed an HP printer with software from HP web page, device. I have this same bug. Ubuntu 18.04, HPLIP 3.18.4, device manager 15.0 (Qt4)
tanks"
1714662,2017-09-03 13:20:41 UTC,I found out about the SIGN_PASSPHRASE environment variable.
1714662,2017-09-03 13:41:15 UTC,"""It asks about the passphrase for the signing key, but does not using it!"""
1714662,2017-09-03 07:56:29 UTC,"The second example works. But if I try with passphrase protected GnuPG key for encryption and key for signing with empty passphrase, it still asks about the empty password:"
1714662,2017-09-02 20:06:16 UTC,Just a couple of workarounds:
1714662,2017-09-02 19:29:24 UTC,"Never mind, need more coffee!  Forgot --encrypt-sign-key was combined option."
1714662,2017-09-02 11:40:36 UTC,"Are you sure this is the way you intended?  You are asking duplicity to use a passphrase to encrypt the data, then asking it to sign the data with a key.  I think you want to just use --encrypt-key by itself."
1714665,2017-09-02 20:57:19 UTC,"I think, as a minimum change, a changed tooltip would already be helpful. Separating this snapping from snapping to intersections would be more useful, but take up more space."
1714667,2018-03-31 07:53:47 UTC,"Unicode Old Hungarian part:
https://unicode.org/charts/PDF/U10C80.pdf"
1714667,2018-03-22 10:51:12 UTC,Please don’t add redundant tasks to the ticket.
1714667,2018-03-22 04:58:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714667,2018-03-11 11:18:24 UTC,"Sorry, I unassignee, because I work on a huge project. Here nobody help me."
1714667,2018-02-27 19:10:23 UTC,"This patch mutch more readable, thanks to Tisza András (his name written by Hungarian name order rule)
This file developed for Ubuntu Regular font, Old Hungarian letters."
1714667,2018-02-15 16:01:29 UTC,"Patches removed permanently, because those are under improvement of quality."
1714667,2018-02-15 15:58:36 UTC,"Patches removed permanently, because those are under quality improvement."
1714667,2018-02-13 18:38:55 UTC,"@Ivanka Majic
Have you send me any critics, suggestions about patches?
Or could you invite somebody, who should help me?"
1714667,2018-02-08 14:44:49 UTC,Here is the Regular version final.
1714667,2018-01-25 13:30:38 UTC,Owner this file is The Unicode organisation.
1714667,2018-01-25 13:27:25 UTC,"This patch have several rendering problems (Missing extrema) Please, talk to me about mistakes, how to can I resolve them! If it has problem with copyright or licence, write to me, please!"
1714667,2017-11-18 20:17:25 UTC,"I am working on the patches regular and its subversions (bold,italic,bold-italic)"
1714667,2017-09-24 10:29:43 UTC,"I need Old Hungarian font,too"
1714667,2017-09-24 10:28:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714667,2017-09-02 16:20:50 UTC,"The attachment ""Old hungarian letters are useable"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1714669,2017-09-17 05:29:19 UTC,Thank you. We will fix it in the next stable release
1714680,2019-09-16 19:09:06 UTC,Migrated to https://github.com/widelands/widelands/issues/3209
1714684,2017-09-02 17:25:09 UTC,"have added archive with
- output of dmesg
- output of pt-summary
- output of pt-mysql-summary
- full copy of /var/log/messages (or syslog)
- full copy of /etc/my.cnf and any other cnf file that might be included
- full copy of error logs
- full copy of /var/lib/mysql/innobackup.*.log
- output of  rpm -qa |egrep -i ""mysql|percona|maria""   (or dpkg -l |egrep -i ""mysql|percona|maria"" |grep ""ii"")"
1714684,2017-09-05 03:14:03 UTC,"- From the log and output it suggest that SST is still active.
- Did you run out of disk space on JOINER ?"
1714684,2018-01-18 08:29:14 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2005
1714689,2020-06-09 04:17:24 UTC,[Expired for darktable (Ubuntu) because there has been no activity for 60 days.]
1714700,2017-09-04 02:34:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714700,2017-09-02 18:49:25 UTC,here's a screen grab from the video i took this morning.
1714705,2019-04-07 09:48:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714712,2017-09-03 02:48:18 UTC,"I see the same missing icon in 17.04 as well. It's ""AC adapter"" in en-us."
1714712,2017-09-03 13:42:11 UTC,"I just tried an up-to-date Artful live session, and it is missing the icon as well."
1714712,2017-10-08 11:22:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714712,2019-09-26 09:53:04 UTC,Fixed via ubuntu-mate-artwork 19.10.8
1714723,2017-09-02 23:22:41 UTC,"Correcting my error: I revisited the CLI terminal. For lsb_release, it says that no LSB modules are available."
1714723,2017-09-04 09:58:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714723,2017-09-04 10:02:17 UTC,"I can confirm that this parameter seems to be ignored.
I've recently witnessed this on 17.10, and have previously seen this happening on Xenial and Zesty.
Steps to reproduce are easy:"
1714727,2019-06-30 19:24:52 UTC,"(I'm not a developer, just a user commenting here) Gnome 3 is not the only desktop environment, some still support the old and reliable status icons, instead of trying to reinvent it over and over.."
1714727,2019-07-23 20:43:40 UTC,"It still works in X with an extension, but not in Wayland. However, this software seems to be deprecated since quite some time…"
1714727,2019-09-25 13:33:39 UTC,"Frank, what extension would that be? cheers."
1714739,2017-09-10 18:08:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714746,2018-01-25 09:34:16 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3738
1714749,2017-09-06 13:11:04 UTC,known issue with modesetting ddx
1714754,2017-09-03 08:56:59 UTC,"just reproduced same issue in Ubuntu 16.04, so looks like it's not bug of Ubuntu Mate"
1714760,2018-01-15 21:20:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714760,2018-01-15 21:56:47 UTC,"After stumbling upon the same issue, I realized that this is not a bug, but intended behavior."
1714764,2017-09-30 02:00:54 UTC,I think it is an essential part of the Ubuntu Desktop that there be an audio cue when the login screen is ready for the benefit of users who are blind.
1714785,2018-01-29 16:59:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714791,2017-09-06 12:18:39 UTC,"--all means all machines not all units. And there is no hook context for a
machine."
1714791,2017-09-06 12:33:54 UTC,Makes sense.
1714804,2018-02-28 16:52:25 UTC,"@Jacopo (rad750): If it affects you, please just click on the link at the top, and do not add comments to that effect as it only serves to spam everyone subscribed to the ticket without adding any progression to the issue.  Thanks."
1714804,2018-02-28 18:33:08 UTC,"@Colan Schwartz (colan) and everyone who was annoyed: I am really sorry for that, it is the first time I comment on a bug report. I found the ""affects me too"" link only after posting the comment."
1714804,2018-04-15 10:52:32 UTC,same here. it stucked on my system and the animation is rolling back and moving slowly on ubuntu 18.04 beta 2.
1714804,2018-05-06 14:50:06 UTC,Same problem here.
1714804,2018-06-27 07:30:29 UTC,You can reset the width using
1714804,2020-03-11 18:56:40 UTC,"While I suggest you to use syspeek (as it causes the shell not to use as much CPU as indicator-multiload), this is now fixed by version 32-1"
1714804,2018-06-27 15:39:36 UTC,"For cross-referencing purposes, the Ask Ubuntu thread is https://askubuntu.com/questions/968641/how-does-one-get-system-load-indicator-or-something-similar-working-in-17-10."
1714804,2018-08-19 19:36:46 UTC,"I can confirm that Martin Vysny's solution/workaround works in Ubuntu 18.04.1LTS.
(this was not the case in Ubuntu Alpha when I reported this bug)"
1714804,2018-09-04 18:54:46 UTC,"Well, please see i just fixed the official gnome shell extension for the indicator-multiload. Source:"
1714804,2018-02-28 14:43:48 UTC,Also affects me.
1714804,2018-06-27 07:42:46 UTC,Workaround is simply to use the gnome-shell-extension-system-monitor instead - it's essentially the indicator-multiload but better integrated with gnome-shell. To install it:
1714804,2017-11-22 21:28:00 UTC,I's also affect me and it's very annoying since I use this indicator all the day along.
1714804,2017-11-03 15:40:30 UTC,"Because that application was written for the platform that Ubuntu is now using (Gnome), and the other one wasn't."
1714804,2017-11-05 17:33:48 UTC,"""It doesn't make sense to spend time porting non-native applications when native applications already exist that can do the job."""
1714804,2017-11-21 08:38:48 UTC,Ubuntu has used Gnome by default for every version since 2004. This bug has nothing to do with “non-native applications”.
1714804,2017-11-02 17:20:56 UTC,Also it is odd to say something is unnecessary because another application has a similar function in a similar way. Why should the developers behind Cerin (gnome-shell-system-monitor) get preference on a platform above the developers behind Michael Hofmann's Indicator-Multiload (aka System Load Indicator)?
1714804,2017-11-02 17:12:13 UTC,I was under the impression that things offered via the Software Center are officially supported (by the Community and some by Canoncial) and scanned for vulnerabilities and compatibility. It's very uncomfortable to be enabling and disabling operating system extensions through a website. It appears as if indicator-multiload is safer to use and would be nice if it were fixed.
1714804,2017-10-31 14:52:55 UTC,"Couldn't get it enabled via apt, but flipping the switch on the extension page (https://extensions.gnome.org/extension/120/system-monitor/) worked."
1714804,2017-10-22 01:39:20 UTC,"Thanks, I wasn't aware of the GNOME Shell System Monitor, and I agree it largely obviates the need for indicator-multiload on GNOME."
1714804,2017-10-20 09:40:12 UTC,We still have Ubuntu Flavours that are non-gnome-shell based and use indicators.
1714804,2017-10-20 06:36:55 UTC,"GNOME Shell already has a nice system monitor (https://extensions.gnome.org/extension/120/system-monitor/), so I'm not sure it is worth the hassle to fix the indicator."
1714804,2017-10-19 23:25:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714804,2017-09-03 17:31:53 UTC,Please see the screenshot to show the settings are exactly the same for 16.04.3LTS and 17.10Daily.
1714804,2017-09-03 17:25:24 UTC,Please see the screenshot for the difference between 16.04.3LTS and 17.10 Alpha
1714805,2017-09-07 15:06:46 UTC,The *exact* architecture should be described as 'aarch64'. It is about a Pinebook: https://www.pine64.org/?page_id=3707
1714817,2017-09-30 17:39:57 UTC,Nice find.
1714823,2020-05-30 12:24:45 UTC,"it would be usefull also to be able to merge duplicates tracks entries into the library. For instance after renaming a track, there is two entries I would like to merge in order to not loose the metadatas on the first entry."
1714832,2017-09-03 22:30:12 UTC,This change was made by a bot.
1714842,2017-09-04 03:04:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/500425"
1714842,2017-09-11 06:28:26 UTC,"Change abandoned by sunguangning (<email address hidden>) on branch: master
Review: https://review.openstack.org/500425"
1714842,2017-09-11 06:42:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502397"
1714842,2017-10-24 20:36:42 UTC,This issue was fixed in the openstack/oslo.db 4.29.0 release.
1714846,2019-08-02 14:36:14 UTC,this is a very old issue. i'm sure it isn't the same as the current breakage.
1714857,2017-09-04 16:10:03 UTC,"I think this is because the --templates option is missing the path to match the -e options, try this:"
1714857,2019-02-26 13:55:09 UTC,No information was given for a long time after Steven's suggestion.
1714857,2019-12-18 08:34:14 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1714858,2018-08-16 20:52:17 UTC,"Marking as fixed, but please change the state back if there is something more to this."
1714858,2018-10-18 19:27:22 UTC,"Was this issue only in Rocky/Queens, or does it exist in the other stable branches?  It looks like the authorize code changed between Pike -> Queens."
1714858,2018-09-20 22:10:25 UTC,"Reviewed:  https://review.openstack.org/593675
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=76d3c644f3f5866a5c07f80b66132d81b8b57e78
Submitter: Zuul
Branch:    stable/queens"
1714858,2021-02-17 20:02:58 UTC,"Since the fixes for this merged long enough ago, there are no longer any stable branches under support which were vulnerable to it. As such, I'm setting our security advisory task to Won't Fix."
1714858,2018-08-04 23:25:09 UTC,"TommyLike, the merged patch was marked as a partial fix for this. Were there more cases identified that we still need to fix, or should that have been Closes-bug instead?"
1714858,2018-08-20 15:46:34 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/593675"
1714858,2018-03-15 03:51:15 UTC,"After investigation in cinder, found one API that would have a potential security issue: reset volume's status, this is the process to reproduce."
1714858,2018-03-02 13:27:28 UTC,"I see you've switched this from Public to Public Security bug type indicating you believe it describes a vulnerability. Unfortunately, the security implications of this report are unclear (at least to me). Can someone elaborate on the associated risks and a possible exploit scenario or two? Having a more thorough list of which ""some other APIs"" are guessed to be similarly wrong would also be appreciated."
1714858,2018-03-23 16:29:07 UTC,"Reviewed:  https://review.openstack.org/548650
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=7391070474269dc247fc1d1f43520087a6a10267
Submitter: Zuul
Branch:    master"
1714858,2018-03-07 17:35:12 UTC,This needs more investigation on the exact impact.
1714858,2018-03-07 01:51:08 UTC,"@Eric Harney, @Jeremy Stanely, I think this bug not belongs to a Public Security or even Security/Critial bug as non-administrator still can not query the resource which doesn't in his tenant."
1714859,2017-09-04 03:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1714859,2017-09-04 04:40:15 UTC,While attempting to reproduce:
1714859,2017-09-05 16:03:04 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1714859,2017-09-11 03:36:26 UTC,I hadn't used sshfs on Power machines before so there isn't a prior good version.
1714859,2017-09-11 06:44:25 UTC,fyi - did more testing - seems to not to affect x86_64 - detailed test should appear in https://lists.ozlabs.org/pipermail/linuxppc-dev soon.
1714859,2018-07-24 09:33:02 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1714870,2017-09-04 05:42:56 UTC,"Sorry few misspelling
I must run command sudo dpkg --configure -a"
1714880,2018-04-16 13:13:19 UTC,I am still experiencing this issue with the latest Fedora Atomic (Fedora-Atomic-27-20180326.1.x86_64.qcow2 as of this writing) on Queens.  Do I need to build my own atomic image with disk image-builder for this to work?
1714880,2018-02-12 10:24:50 UTC,"Hi, Spyros, how we fix this in magnum ourselves?"
1714880,2017-10-23 12:51:56 UTC,https://github.com/projectatomic/atomic-system-containers/issues/133
1714880,2018-02-19 11:48:39 UTC,In any case you need the fixed images with 1.7.7 or higher to have the proper mounts and permissions.
1714880,2017-10-22 17:50:49 UTC,"We can try to pass this parameter to the apiserver --cert-dir
when tls-disbled."
1714880,2017-10-23 11:23:26 UTC,"It doesn't work, we need to have a writable directory for the kubernetes-apiserver system container OR create certs for the apiserver. I'll open an issue in atomic-system-containers"
1714880,2017-09-14 11:33:35 UTC,If we mount /var/run/kubernetes does it work? I mean if it can write in /var/run/kubernetes
1714880,2018-02-19 11:48:01 UTC,In the v1.7.7 container images the problem is fixed (in pike). I'm not sure how useful is a non tls cluster though. With RBAC enabled it can not work. AFAIK there is no option for RBAC enabled clusters to work without tls. If there is a requirement to have non-tls cluster we can do  the following separation.
1714880,2017-09-15 11:57:00 UTC,"Haven't tried this, will try and update."
1714890,2017-09-04 08:20:46 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1714894,2017-09-04 08:50:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/500482"
1714894,2017-09-22 06:40:59 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/500482"
1714899,2017-09-04 08:57:18 UTC,"Docker fails to create service instance sometimes for the error log above from /var/log/kuryr/kuryr.log.
Restring Docker resolves the problem."
1714902,2017-09-04 09:02:23 UTC,"Looks to me as if nl_phrase_search is a bit on the quadratic side, and we may need to tune it."
1714914,2017-09-08 11:53:56 UTC,Thanks Nobuto. This sounds like a reasonable feature and an action sounds like a good way to solve this.
1714916,2017-09-28 20:49:41 UTC,Marking this bug as confirmed because I just ran into it in the context of helping a user with no namespace set.
1714919,2017-09-05 17:29:38 UTC,Hello and thanks for the bug report!
1714919,2017-09-05 18:59:23 UTC,"Thanks for the response Tyler. Just to clarify, I don't necessarily think ecryptfs is the reason for hibernation crashing as I don't always get this error (its somewhat random since I havn't figured out how to reproduce it yet)."
1714920,2017-09-04 16:03:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714926,2017-09-05 16:09:13 UTC,Thank you for your bug report.
1714926,2018-08-02 00:39:59 UTC,We're trying to consolidate horizon and other services into a separate model and we need cross model relations to work.
1714930,2018-05-11 15:35:32 UTC,This change was made by a bot.
1714936,2017-09-04 12:23:01 UTC,"Trying to purge gnome-shell-extension-taskbar from synaptic:
- the removal start as expected, but freeze before ending: no more mouse, keyboard, full freeze
- the next boot is unable to load gnome-shell: heavy hdd scanning job
- switching to F2 console: first reinstall the package to overwrite the removal failure, then purge it.
- next reboot load gnome-shell as expected."
1714938,2017-09-08 12:15:16 UTC,"Thank you, I will take into account the suggestion and work on the subject.
Happy day and happy weekend"
1714941,2017-09-04 12:21:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714941,2021-02-18 19:20:28 UTC,Dear reporter.
1714941,2021-02-22 13:53:51 UTC,"AFAIU this bug is already fixed. Snapd adds x-gdu.hide to mount options for snaps, and they are no longer visible in gnome disks utility."
1714948,2017-09-04 12:51:49 UTC,http://logs.openstack.org/20/499820/1/check/gate-tempest-dsvm-networking-ovn-neutron-api-ovs-release-nv/ad597c9/console.html
1714958,2019-02-15 22:21:47 UTC,It is happening on 64-bit too with 1.7.6-0ubuntu4.
1714958,2017-11-09 08:04:07 UTC,Im having this exact problem on the Ubuntu 16.10 Server PowerPC installation image.
1714958,2017-11-11 05:48:21 UTC,Seems that the package does not like being installed in a 32-bit userland on a 64-bit system.  Started the powerpc-64 installer and it was not a problem.
1714959,2017-09-12 21:10:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714961,2017-10-19 21:27:16 UTC,"As far as I read the source code, the is_public flag gets set to true if no projects are added - as long as the change is done in Horizon."
1714961,2020-06-17 11:55:07 UTC,"Observation with cli command, when all projects are removed via Horizon GUI - in a bug senerio. Cli command of Flavor list don't show the flavor, Even flavor show command fail for that flavor."
1714977,2018-04-12 19:59:00 UTC,This issue was fixed in the openstack/python-openstackclient 3.8.2 release.
1714977,2017-09-05 13:08:58 UTC,https://review.openstack.org/#/c/466507/ looks promising as a backport that may help to resolve the issue.
1714977,2017-09-06 09:53:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/501191"
1714977,2017-09-06 18:06:18 UTC,"Reviewed:  https://review.openstack.org/501191
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=5eb85674668e46fd657f150c77239b6a980eb2f5
Submitter: Jenkins
Branch:    stable/ocata"
1714977,2017-09-07 07:14:15 UTC,"Closing as I think this was a stable/ocata issue only (I can't set ""Target to series"")."
1714982,2019-09-11 22:36:11 UTC,This seems to have been fixed at some point; there are no ‘for each…in’ loops in the current version.
1714987,2019-07-25 10:02:49 UTC,@Nobuto Murata The current description in '_create_backup.html' looks good to me. So mark it as invalid.
1714989,2017-11-21 16:08:40 UTC,"GadLinux, not so hard now... We've added tools in gnome-shell to show this in the journal."
1714989,2017-11-22 12:04:42 UTC,"Hi Marco,"
1714989,2017-10-23 20:16:36 UTC,"Mattéo, what are the steps to reproduce your crash?"
1714989,2017-11-27 00:30:08 UTC,"@marco, should an extension be able to crash a gnome-shell session?"
1714989,2017-11-18 09:34:47 UTC,"Hi,"
1714989,2017-11-24 02:16:39 UTC,"Well, you won't be able to catch it immediately."
1714989,2017-11-17 21:40:04 UTC,Thanks for all these reports...
1714989,2017-10-29 13:40:19 UTC,I've not had one of these crashes since removing Global App Menu. Anyone else got it installed?
1714989,2017-11-09 08:41:24 UTC,I have (what looks like) the same issue with another extension (specifically this commit: https://github.com/projecthamster/hamster-shell-extension/tree/07cea1824291cb818befd5fb473a065abe334bde).
1714989,2017-10-30 16:08:58 UTC,"thanks for the valgrind log, that indeed has error but seems to be missing the gnome-shell and libmozjs debug symbols"
1714989,2017-10-30 05:14:15 UTC,I also experience this crash. I don't have global app menu installed but for me the crash occurs when the following line of code is being executed in the Freon shell extension: https://github.com/UshakovVasilii/gnome-shell-extension-freon/blob/f9756b2430b3766c3d21d71e9928963032617bf7/freon%40UshakovVasilii_Github.yahoo.com/extension.js#L360
1714989,2017-11-27 19:50:58 UTC,"André, this is something we discussed a bit upstream (see comments starting from https://bugzilla.gnome.org/show_bug.cgi?id=788931#c61)."
1714989,2017-10-23 20:53:48 UTC,Thank you Marco for having forwarded the bug to the right developers.
1714989,2017-10-23 20:51:22 UTC,"Looking through the journalctl, I saw Global App Menu and also Pixel Saver were having problems. Hopefully these issues can be fixed. Though it seems we shouldn't hold out hope for GAM as the author discontinued it: http://www.omgubuntu.co.uk/2017/09/gnome-global-menu-extension-discontinued"
1714989,2017-11-09 08:42:39 UTC,"By the way, comment #48 is on Ubuntu Artful, latest packages at the time of writing, with Gnome Shell 3.26.1-0ubuntu4."
1714989,2017-11-28 01:46:11 UTC,Adding gjs here as it's the one that should avoid such hard crashes.
1714989,2017-12-12 17:33:10 UTC,"Marco, thanks for the context and the steps you and the team are taking to resolve this issue more broadly. Linking js and C is bound to have these problems."
1714989,2017-12-05 04:50:05 UTC,new gjs available: http://ftp.gnome.org/pub/GNOME/sources/gjs/1.51/gjs-1.51.2.news
1714989,2017-12-05 05:38:27 UTC,"2017-12-04 23:50 GMT-05:00 dino99 <email address hidden>:

> new gjs available:
> http://ftp.gnome.org/pub/GNOME/sources/gjs/1.51/gjs-1.51.2.news
"
1714989,2017-12-05 11:09:54 UTC,"Thank you, would be great to have this backported into 17.10 as this is causing me occasional login issues with the set of extensions I have installed."
1714989,2017-12-08 11:47:12 UTC,"I'm running gnome-shell on upgraded Ubuntu 17.10 with X server, not Wayland, due to other compatibility issues.
In my case if I lock the desktop but the gnome-shell is restarted because of segfault it kills the lock screen and leaves the desktop completely open with the user logged in."
1714989,2018-01-15 07:33:07 UTC,"It appears the fix for this bug is scheduled for release in gnome-shell, specifically 3.26.3:"
1714989,2018-03-04 13:03:49 UTC,This bug was fixed in the package gnome-shell - 3.27.91-0ubuntu1
1714989,2018-03-29 02:09:03 UTC,It's still happening in 3.28.0: bug 1759621
1714989,2018-04-16 02:43:06 UTC,"Closing this bug, but it continues in bug 1759621."
1714989,2018-06-26 01:46:47 UTC,OK then. Forget bug 1759621. Let's continue using this one.
1714989,2018-06-28 19:37:21 UTC,"Hello Paul, or anyone else affected,"
1714989,2018-07-09 09:25:06 UTC,Using 3.28.2-0ubuntu0.18.04.1 there are no visible issues and the error report page has no entry for this version
1714989,2018-07-09 16:36:33 UTC,The patch got accepted upstream for gnome-shell 3.30. And hopefully for some 3.28.3 version.
1714989,2018-07-09 23:20:25 UTC,This bug was fixed in the package gnome-shell - 3.28.2-0ubuntu0.18.04.1
1714989,2018-07-09 23:20:44 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1714989,2017-12-05 02:55:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714989,2017-10-23 20:15:13 UTC,"Mh, that's again caused by another extension (gnomeGlobalAppMenu), but I'm not sure if the bug is the same, as I don't see any text reference there."
1714989,2017-10-31 22:29:47 UTC,The JS stack trace from comment 45 is:
1714989,2017-10-23 12:06:19 UTC,"To get that content easily, just attach here the output of:"
1714989,2017-09-04 16:19:37 UTC,"StacktraceTop:
 g_type_check_instance_cast (type_instance=0xcc06b6cda0, iface_type=876225709408) at ../../../../gobject/gtype.c:4058
 st_label_set_text (label=0xcc06696e10, text=0xcc061762b0 ""Nightly Web Browser"") at ../src/st/st-label.c:331
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0xcc05332598, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffcbc1c0608, avalue=avalue@entry=0x7ffcbc1c0500) at ../src/x86/ffi64.c:525
 gjs_invoke_c_function (context=context@entry=0xcc03821400, function=function@entry=0xcc05332580, obj=..., obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at gi/function.cpp:1037"
1714989,2017-09-06 13:27:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1714989,2017-10-04 06:58:42 UTC,This also happens quite frequently on Artful.
1714989,2017-10-14 00:15:02 UTC,It's quite hard to debug this without a javascript dump...
1714989,2017-10-15 10:07:18 UTC,@Marco:
1714989,2017-10-16 08:31:59 UTC,Hmm...
1714989,2017-10-16 23:48:18 UTC,"Juerg, I forgot to mention. Check your journal (journalctl -e /usr/bin/gnome-shell) the output for the ""call gjs_dumpstack()"" will be there (not in gdb)."
1714989,2017-10-16 23:48:58 UTC,"Paul, sorry it was"
1714989,2017-10-17 11:56:57 UTC,I kind of suspected that it was dash-to-panel. But a misbehaving extension shouldn't bring gnome-shell down.
1714989,2017-10-18 22:15:35 UTC,"Been experiencing this issue as well, and like Juerg said, I also have dash-to-panel running."
1714989,2017-10-19 07:37:49 UTC,I also have dash-to-pannel running.
1714989,2017-10-19 08:55:36 UTC,"The dash to panel extension is not present on my system (Ubuntu GNOME), so the bug is surely not specific to that, as seen in the linked GNOME Bugzilla report."
1714989,2017-10-20 05:05:29 UTC,"Indeed these bugs might be triggered by one extension, more than vanilla experience, but they still underline issues in the code, so it's still a bug we've to fix."
1714989,2017-10-20 05:26:20 UTC,"Juerg, also, if you have a core file handy (or a full /var/crash/ *.crash file), that would be helpful."
1714989,2017-10-20 21:19:37 UTC,I use dash to dock rather than dash-to-panel but am now running the command and will try and get an output for you.
1714989,2017-10-20 20:36:40 UTC,"So this is mostly triggered by extensions (and considering how things are done, we can't prevent them).
Or some wrong JS code which we didn't identified yet."
1714989,2017-10-21 09:16:29 UTC,I attempted to run
1714989,2017-10-23 11:57:48 UTC,"Paul, you uploaded the journalctl itself :)"
1714989,2017-10-23 11:57:14 UTC,"Mateo, that issues is triggered by"
1714989,2017-10-23 10:34:44 UTC,I worked with Marco on Friday and he submitted a PR for dash-to-panel which fixes my crashes. See https://github.com/jderose9/dash-to-panel/issues/261.
1714989,2017-10-23 04:48:09 UTC,"Sure, it probably can't hurt."
1714989,2017-10-23 04:24:06 UTC,Sorry for the inconvenience. I’m new to reporting bugs on Launchpad. Should I post my logs over on the other bug?
1714989,2017-10-23 12:43:16 UTC,Hopefully this is what you was looking for.
1714989,2017-10-21 08:20:03 UTC,I use dash to panel.
1714989,2017-10-23 03:42:20 UTC,"Mattéo, that is bug 1723705. Not this one."
1714989,2017-10-22 13:56:35 UTC,"I’m encountering a similar crash, this time in ""g_type_check_instance_is_fundamentally_a"", and not ""g_type_check_instance_cast"". Attached are the gdb.txt and journalctl.txt files generated following the procedure given above."
1714989,2017-10-22 09:49:37 UTC,And here's my journalctl
1714989,2017-10-22 09:45:17 UTC,Here's the gdb.txt
1714989,2017-10-21 23:43:10 UTC,Using pgrep here is actually safer:
1714989,2017-10-21 20:22:38 UTC,"Ok, actually that's not needed..."
1714989,2017-10-21 20:02:31 UTC,"Paul, you need to do that from another system via SSH or from tty3 (or any free one), although you still might not be able to go back to the tty when frozen...
So having another system around (using byobu too) would help."
1714989,2017-10-22 13:56:56 UTC,(Here is the journalctl.txt file.)
1715004,2017-09-04 21:06:05 UTC,"I'm not sure how that syslog is different from a successful connection? It
looks like it did connect, although possibly it dropped again straight away?"
1715009,2017-11-21 14:40:08 UTC,"I'm curious in general why power adds the config drive as a cdrom.
In other arch it is added as virtio (or whatever other block device might be)."
1715010,2017-09-14 16:59:35 UTC,"The verification of the Stable Release Update for cryptsetup has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1715010,2017-09-14 16:59:30 UTC,This bug was fixed in the package cryptsetup - 2:1.6.6-5ubuntu2.1
1715010,2017-09-06 20:46:33 UTC,"Hi, I installed the proposed cryptsetup and ran the common criteria testcases for cryptsetup, that before had failed. My environment includes the fips-supported kernel and modules. With the new cryptsetup, all the common criteria cryptsetup testcases passed."
1715010,2017-09-06 10:06:44 UTC,"Hello Marcelo, or anyone else affected,"
1715010,2017-09-06 10:06:30 UTC,We'll have to wait with releasing the xenial change until the artful's 2:1.7.3-4ubuntu1 version migrates to the release pocket.
1715013,2017-09-11 11:16:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715013,2017-10-31 12:37:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1715023,2017-09-04 21:18:50 UTC,Stripping whitepsace in front of the EOF on line 9 makes the error go away.
1715027,2018-05-11 15:35:42 UTC,This change was made by a bot.
1715027,2017-09-04 23:35:52 UTC,"Comments #3 - #17 are from the same laptop with 16.04.0 LTS, fully updated.  The wifi light has the correct functionality with this installation."
1715027,2017-09-04 23:33:42 UTC,apport information
1715027,2017-09-04 23:33:40 UTC,apport information
1715027,2017-09-04 23:33:36 UTC,apport information
1715027,2017-09-04 23:33:34 UTC,apport information
1715027,2017-09-04 23:33:33 UTC,apport information
1715027,2017-09-04 23:33:32 UTC,apport information
1715027,2017-09-04 23:33:37 UTC,apport information
1715027,2017-09-04 23:33:29 UTC,apport information
1715027,2017-09-04 23:33:28 UTC,apport information
1715027,2017-09-04 23:33:27 UTC,apport information
1715027,2017-09-04 23:33:26 UTC,apport information
1715027,2017-09-04 23:33:30 UTC,apport information
1715027,2017-09-04 23:33:24 UTC,apport information
1715027,2017-09-04 23:33:23 UTC,apport information
1715027,2017-09-04 23:33:20 UTC,apport information
1715027,2017-09-04 23:33:19 UTC,apport information
1715034,2017-09-18 19:23:43 UTC,"Just to add some further information: I have found that if I install without ticking the ""Encrypt Home Folder"" checkbox, and I then encrypt the home folder post installation (using sudo ecryptfs-migrate-home -u user), then start-up and shutdown operations are normal (quite fast)."
1715034,2017-10-25 07:43:46 UTC,"I have performed two installs of Kubuntu 17.10 (final) on two separate computers (one laptop, one desktop) with the home folder encryption option, and both have worked fine. Both startup and shutdown are fast, as expected."
1715034,2017-09-18 12:17:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715048,2018-09-20 12:07:24 UTC,I have that same problem in my high resolution Dell (but not in my high resolution Mac).
1715048,2018-09-20 12:38:49 UTC,"@doctor-pat, did you try version 0.18.2 on both systems? Or which versions? Guillaume apparently fixed a lot of those problems for Macs over the last year, but Mac and Windows behave very differently. In addition, screen settings like magnification factors may interfere. Only a developer with HiDPI device can go deeply enough into matters to fix that."
1715048,2018-09-26 04:12:11 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/386
1715062,2017-09-06 15:32:42 UTC,From log:
1715062,2017-09-06 15:33:12 UTC,Thank you for taking the time to file a bug report.
1715062,2017-09-07 06:24:41 UTC,"yeah, you are correct i upgraded from python 2 to 3"
1715062,2017-09-22 09:50:25 UTC,I'm afraid we don't support running with /usr/bin/python pointing to Python 3.  For Python 3 you should use /usr/bin/python3.
1715062,2017-09-27 19:15:05 UTC,This bug was fixed in the package python-defaults - 2.7.14-2ubuntu1
1715062,2017-11-24 00:51:02 UTC,"Hello Success, or anyone else affected,"
1715062,2017-11-24 07:40:47 UTC,"the xenial uploads work as expected, and are using python2 as the shebang"
1715062,2017-11-27 16:40:56 UTC,"Hello Success, or anyone else affected,"
1715062,2017-11-28 08:22:35 UTC,"the zesty upload works as expected, and is using python2 as the shebang"
1715062,2018-02-20 09:10:27 UTC,This bug was fixed in the package python-defaults - 2.7.12-1~16.04
1715062,2018-02-20 09:10:32 UTC,"The verification of the Stable Release Update for python-defaults has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1715080,2018-10-25 14:42:34 UTC,"global-requirements isn't synced to all projects anymore, see http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html"
1715080,2018-10-24 17:38:44 UTC,"This is just something to do, update global-requirments and it is populated down. Updating global-requirements for a past release is hard to do, it is suggested that you simply propose the changes and it will be synchronized to keystone once it is approved."
1715080,2017-10-03 21:00:39 UTC,"I don't think global requirements is the problem here. It would appear that this is also an issue in master. Since pyldap is an optional dependency that is managed in setup.cfg, we'll need to bump it there [0]. Then we can discuss the process for backporting this to stable/pike with the stable maintenance team."
1715080,2017-10-03 21:01:48 UTC,Marking this as Low since the workaround is to upgrade pyldap manually.
1715083,2017-10-09 07:41:09 UTC,"Reviewed:  https://review.openstack.org/502957
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=d14d9202e3a0d7ce4547d69a6857c8b9f1874a65
Submitter: Jenkins
Branch:    master"
1715083,2018-01-10 22:06:18 UTC,Why was https://review.openstack.org/#/c/514761/ only a partial fix? What is there left to do?
1715083,2018-05-09 07:18:22 UTC,"So, I rechecked this issue and it seems it has been solved in queens, but it's still happening in pike and ocata's jobs:"
1715087,2018-04-10 06:20:39 UTC,"Reviewed:  https://review.openstack.org/536859
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=e2722c8493e72febc91b784f8c58cde47555e940
Submitter: Zuul
Branch:    stable/pike"
1715087,2018-04-23 19:02:05 UTC,This issue was fixed in the openstack/tripleo-heat-templates 7.0.12 release.
1715087,2018-01-23 15:24:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/536859"
1715087,2017-11-09 22:37:37 UTC,"Reviewed:  https://review.openstack.org/502542
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=fe8551a056a769d3a0a9c39546f9f14d142bf57f
Submitter: Zuul
Branch:    master"
1715087,2017-09-11 19:45:19 UTC,Proposed fix https://review.openstack.org/#/c/502542/
1715087,2017-12-04 21:04:37 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0b2 development milestone.
1715091,2017-09-05 11:51:35 UTC,"Hi! We'd better ask Renat, but as far as I understand, we should not use native keystone authentication module in mistral client[1]. It's outdated and doesn't support many keystone features."
1715091,2017-09-06 07:52:51 UTC,"@Mike, I'm not completely sure how this could be achieved in mistralclient/auth/keystone.py. Mistral is running in stand alone mode and we are using the target* parameters to direct the workflow executions to arbitrary clouds."
1715095,2019-02-22 11:02:36 UTC,"Hi Marc,"
1715095,2020-12-09 04:17:26 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1715096,2019-12-18 11:13:33 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/500737
Reason: Yup, this is incorrect and needs more work. I'll abandon this since that work will be done elsewhere"
1715096,2017-09-05 08:59:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/500737"
1715097,2019-09-28 08:45:10 UTC,"this issue seems to be fixed in 18.04, i didn't have to install mysql-server to install postfixadmin, just having mariadb-server installed was enough to satisfy apt"
1715097,2017-09-06 10:28:41 UTC,"AFAIK this is fixed in the upstream debian/control (at least on github, didn't check the release tarball), so syncing with that might be a better option."
1715097,2017-09-05 12:25:58 UTC,"The attachment ""MariaDB Patch for postfixadmin DEBIAN/control"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1715102,2017-09-08 12:20:19 UTC,Thanks Nobuto.
1715102,2017-09-08 12:23:13 UTC,I'm marking this as a bug vs wishlist since the (upstream) default changed on a release boundary there's no way to enable this functionality via the charm.
1715102,2017-09-08 12:50:02 UTC,"@Corey,"
1715102,2017-09-08 15:40:55 UTC,Thanks for the info Nobuto. Let's mark this as wishlist then.
1715112,2020-11-25 15:05:14 UTC,Drivers requests are upstream bugs and as such should be redirected to the official wiki
1715112,2017-12-19 13:05:23 UTC,"I have same problem on my Dell XPS 15 9560 (2017 model), if you need any help like testing, providing debug data and so on, I'm open for such activities."
1715112,2018-06-27 08:31:08 UTC,See also this reverse engineering project: https://github.com/hmaarrfk/Validity91
1715112,2017-09-05 10:00:37 UTC,sudo lsusb -s 001:003 -v
1715112,2017-10-16 12:24:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715113,2017-09-05 10:30:07 UTC,This change was made by a bot.
1715113,2017-09-05 15:52:05 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1715113,2017-09-06 10:00:49 UTC,Works with upstream kernel:
1715113,2021-01-06 04:36:23 UTC,"I am closing this bug as Artful has already reach its End-Of-Life,
please feel free to file a new bug with the latest Ubuntu.
Thanks"
1715125,2017-10-04 07:21:26 UTC,I've noticed this on Ubuntu too!
1715125,2017-10-04 07:21:51 UTC,But it doesn't affect windows as it automatically adds the extension.
1715130,2018-05-14 11:03:08 UTC,This change was made by a bot.
1715130,2021-01-07 04:07:44 UTC,4.8 EOL
1715133,2018-10-17 08:56:31 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/545660
Reason: Michel Peterson, done"
1715133,2018-10-16 10:34:21 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/501308
Reason: Cleaning up changes that seem to be abandoned or are older than two months. If you think this was an error and the change is still relevant, please be free to restore it. Sorry for any inconvenience that I might have caused by this."
1715133,2018-02-18 07:16:34 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/545660"
1715133,2017-09-06 15:16:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501308"
1715133,2017-09-06 04:07:28 UTC,"Full sync for other resources which have their own v2 drivers may have the similar issue.
sfc, qos, bgpvpn ..."
1715138,2017-09-05 12:13:49 UTC,According to su_v on #inkscape-devel:
1715138,2017-09-05 13:15:21 UTC,/me contd on #inkscape-devel:
1715138,2017-09-05 13:36:22 UTC,Interesting... it works in a not too old version of master. Something else must have changed since the hackfest.
1715140,2019-06-10 17:00:16 UTC,"I cannot reproduce it any more, possibly it has been a bug in some perl lib which has been fixed by now. If anybody else can still reproduce it, please comment!"
1715140,2019-06-19 14:46:15 UTC,"Hello @Photon.
The last part(https://bugs.launchpad.net/shutter/+bug/1556021/comments/16) I told you is not fixed yet."
1715140,2019-06-21 04:02:22 UTC,"Weird, it works for me, see attached screenshot."
1715140,2019-06-21 05:05:57 UTC,"Hi Photon.
My version of Shutter is 0.94.2-0build3~ubuntu18.04 on KDE Neon."
1715140,2019-06-29 07:19:01 UTC,"Sorry, missed your comment. Yep, I can also reproduce this."
1715141,2020-03-03 14:16:30 UTC,This issue was fixed in the openstack/oslo.messaging 12.0.0 release.
1715141,2020-02-18 23:28:41 UTC,"Reviewed:  https://review.opendev.org/703106
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=fed48aea44d2d7683516cf0e9f427cd1113c2694
Submitter: Zuul
Branch:    master"
1715141,2020-01-17 15:31:18 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/703106"
1715141,2020-01-17 15:09:21 UTC,Do we have more visibility about this topic?
1715141,2018-03-12 16:13:17 UTC,Mistral has requested an extension in order to address
1715141,2018-10-19 18:04:09 UTC,Let's push the removal off to the T release.   No point in breaking things if we can avoid it.  Besides there are still a few other users of blocking out there who will also be affected.
1715141,2018-10-18 05:02:45 UTC,"Dear Oslo Team, https://bugs.launchpad.net/mistral/+bug/1696469 has been closed but it has unexpected consequences that make it necessary to keep using the blocking executor. Namely, under high parallelism, the connections to RMQ becomes unstable to the point when it starts missing heartbeats and finally causing the whole service to fail unrecoverably. We are working on fixing this issue."
1715141,2018-10-19 18:10:56 UTC,Adding a requirement:
1715148,2018-04-08 05:43:44 UTC,"Change abandoned by Chenghui Yu (<email address hidden>) on branch: master
Review: https://review.openstack.org/501099"
1715148,2017-09-06 03:32:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501099"
1715150,2020-07-19 12:04:06 UTC,"I tested steps from post #1 using Pinta-daily on Ubuntu 18.04. It looks like if Pinta does not have access to some directory it just crashes with ""Permission denied"" exception."
1715150,2021-01-01 20:10:24 UTC,"I did tests on Pinta 1.8-development on Ubuntu 20.04:
https://github.com/PintaProject/Pinta/actions/runs/455360743"
1715150,2018-07-18 07:14:32 UTC,"I can confirm this happens (in my case for png files - type of file should not matter though)
Steps to reproduce:
1. Open pinta as a regular user
2. Save the image to /usr/share/alsa/test.png
3. Unhandled exception is triggered:"
1715160,2018-07-08 15:29:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715162,2020-11-05 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1715162,2020-09-05 12:17:39 UTC,Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays?
1715166,2017-09-06 11:55:30 UTC,"@Lius,"
1715166,2017-09-06 15:23:09 UTC,"I'm testing this with Kuryr and containers, but it should be the same behavior for VMs. To reproduce my devstack setup, you need to do:"
1715166,2017-09-06 15:38:38 UTC,Can you confirm that the member has a route to the VIP network and there are no security group uses?
1715166,2017-09-06 15:54:48 UTC,"I can confirm that the curl request arrives all the way inside the amphora-haproxy namespace of the amphora VM, so it is not a security group issue."
1715166,2017-09-06 18:08:09 UTC,If you disable strict reverse path forwarding inside the amphora-haproxy namespace do you still notice the issue?
1715166,2017-09-07 00:19:50 UTC,"Note, we are tracking this here now after the storyboard migration: https://storyboard.openstack.org/#!/story/1715166"
1715173,2018-10-08 08:39:22 UTC,I think this bug is related to bug #1767765 (Clicking on fcitx applet hangs Ubuntu MATE)
1715173,2020-04-12 21:31:21 UTC,"I am using Debian 10:
Linux Vostro430a 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux
with mate desktop manger:
version: 1.20.4"
1715173,2018-10-08 17:46:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715173,2018-04-07 16:49:44 UTC,18.04 beta I meant
1715173,2018-04-07 16:18:16 UTC,damn just seen the bug filed against 17.10... hadn't seen it in this version (there are other bugs with the applets tho) but have hit it instantly as soon as I booted in the 18.10 beta live
1715173,2018-04-07 16:14:25 UTC,"Can confirm this. The problem runs deeper, there are two indicators from separate applets - one configured to show a flag for the current layout the other is a 2 letter code. The latter is one that keeps popping up *when you click on the desktop*. i.e. it seems that caja (it still manages the desktop right?) behaves differently from just about every other app..."
1715173,2018-04-27 20:09:01 UTC,"This problem is a bit more critical than first meets the eye. The two letter US code shows up when in a text input context of some sort, and disappears when such input doesn't make sense. This leads to an unfortunate case where attempting to click on the menu item when the code is visible, switches to a context where it disappears, and the entire desktop becomes unresponsive to mouse and keyboard input."
1715173,2017-09-18 14:16:47 UTC,"So the issue also happens in the Contemporary, Cuptertino, Mutiny, and Pantheon layouts."
1715173,2017-09-18 13:37:10 UTC,@nadrimajstor: I only had 1 keyboard layout listed in the Input Method Configuration and the Keyboard Preferences dialogs
1715173,2017-09-07 22:12:51 UTC,"OK, I can confirm this issue except in my case the text is the whole applet so switching to redmond means there's nothing left."
1715173,2017-09-05 18:54:22 UTC,"@Etienne You need to have, at least, two keyboard layouts for Layouts Indicator to appear."
1715173,2017-09-05 15:28:06 UTC,How do you get this indicator to appear? I can't find it in the list of panel applets.
1715173,2017-10-15 06:10:01 UTC,"Hi all,
I also have this issue. Keyboard language indicator is lost after reboot or if I change panel layout. It is same for me on two installations, one i virtual box and another is clean install on hdd."
1715182,2017-10-24 12:42:11 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1715182,2017-10-23 07:37:26 UTC,"Reviewed:  https://review.openstack.org/509923
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=81c4c17f2a0b9cd3a4d27c0b06092ef456c8979f
Submitter: Zuul
Branch:    stable/pike"
1715182,2017-10-06 14:30:29 UTC,"Reviewed:  https://review.openstack.org/507687
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f90c61cd88edce74e3dbfd069beb2c33793d3371
Submitter: Jenkins
Branch:    master"
1715182,2017-10-05 22:22:45 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/509926"
1715182,2017-09-26 21:07:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/507677"
1715182,2017-09-30 17:56:47 UTC,"Reviewed:  https://review.openstack.org/507677
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6c3a58ce8001c588fe225d60ec198c7141d74700
Submitter: Zuul
Branch:    master"
1715182,2017-09-26 21:39:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507687"
1715182,2017-10-24 12:49:58 UTC,"Reviewed:  https://review.openstack.org/509926
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=76a3465271bdf48ebf579df77bb93739f39745c0
Submitter: Zuul
Branch:    stable/pike"
1715182,2017-10-05 22:22:05 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/509923"
1715182,2017-11-15 01:10:37 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1715185,2019-10-04 14:49:57 UTC,"Yes, you are right - removing the local .desktop file ""activated the
global"" .desktop file, which made it visible in the menu."
1715185,2019-10-04 13:57:25 UTC,"Hi @mapreri,
I know about the stable distributions, but I was just wondering why this stable version ended up here, really old and without the install hooks.
Sorry about the PPA, must have been tired - wanted to put it in here: https://launchpad.net/~atareao/+archive/ubuntu/telegram
Regarding the icon problem, I just spun off a couple of clean installs, and from what I can tell, both work just fine with a clean install.
The original problem I've had is that there was an existing ./.local/share/applications/telegramdesktop.desktop, pointing to ""Exec=/opt/telegram/telegram -- %u"" (probably from the binary version, or from the abovementioned ppa, which is just a wrapper for the binaries), and it wasn't removed or overwritten by the telegram-desktop app upon install.
Apparently, they can also co-exist at the same time, but whichever one was installed and launched first, stays in the menu. I'll check with the maintainer of the PPA if I can submit a pull request for the dependencies and cleanup."
1715185,2019-10-03 07:38:51 UTC,"it's not that the version in ubuntu 18.04, that's just how stable distribution works: once a package version is there, it won't be touched (barred some exceptions)."
1715185,2019-10-04 14:17:26 UTC,"anything regarding /opt/ definitely comes from unofficial packages.  Also, just installing packages must not touch anything in a user's home."
1715185,2019-10-02 19:41:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715185,2017-09-05 17:50:43 UTC,On further investigation it would appear the fix is to rename the .desktop file from:
1715185,2017-09-05 17:19:05 UTC,"A bit more info following investigation. When using MenuLibre to investigate the menu applications Telegram is listed. It is also listed when using the MATE Menu Editor (mozo). It doesn't, however show in the menus - Brisk Menu, Main Menu (The Main MATE Menu) or MATE Menu (Advanced MATE Menu)."
1715185,2019-10-02 20:29:04 UTC,"Hi all,"
1715188,2017-10-19 15:07:38 UTC,Any ideas?
1715188,2018-09-14 16:31:51 UTC,*bump*
1715188,2020-05-15 16:30:54 UTC,"Well, this project seems to be dead."
1715188,2020-05-18 07:12:19 UTC,"Thank you for your bug report. Indeed rhythmbox is on low maintainance nowadays, you would still have a better chance by sending the issue upstream to the people writing the software
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues"
1715192,2017-11-14 17:12:37 UTC,nrpe-external-master relation was added to the charm but it did not work for me on trusty
1715200,2017-09-05 18:10:43 UTC,"Specifically, we need something akin to the resource-tags model config but for IAM roles."
1715200,2017-09-05 18:15:49 UTC,"OTOH, there was discussion in Warsaw about properly modeling native integration in Juju by providing a way that a charm could request a short-term token to perform cloud operations directly rather than depending on something external, such as conjure-up, to do those operations.  That would make this moot and enable us to move the cloud-specific behavior into something like an AWS ELB proxy charm."
1715203,2020-11-17 18:33:13 UTC,"https://git.qemu.org/?p=qemu.git;a=commitdiff;h=9fc33bf4e1d694225
... the test suite is still failing, but at least we can compile test Haiku now. Thanks!"
1715203,2020-09-06 14:45:24 UTC,A patch for this work has been posted to the qemu-dev ML.
1715203,2020-09-05 14:48:12 UTC,"$ ./haiku.x86_64 --verbose --image /tmp/haiku.img uname
Haiku"
1715203,2020-09-05 14:46:53 UTC,ok..  a Haiku vm for QEMU is WIP here:
1715203,2020-09-05 12:03:12 UTC,Hi!
1715203,2020-09-05 15:19:57 UTC,and away we go..
1715203,2017-09-08 01:09:58 UTC,"We're purchasing some new hardware, once we get it set up we'll setup a x86_64 Haiku machine to build qemu."
1715203,2017-09-05 19:00:35 UTC,Contacting our board of directors to see if I can get a VM deployed at Vultr. I'll keep this ticket updated.
1715203,2017-09-05 18:25:08 UTC,"On 5 September 2017 at 19:14, kallisti5 <email address hidden> wrote:

> Haiku recently got a virtio driver, so running a Haiku system in cloud
> infrastructure seems possible now. (I've personally run it on vultr.com)
> Does QEMU have some infrastructure available so we can stand up a x86_64
> system?
"
1715203,2017-09-05 18:14:07 UTC,"Haiku recently got a virtio driver, so running a Haiku system in cloud infrastructure seems possible now. (I've personally run it on vultr.com) Does QEMU have some infrastructure available so we can stand up a x86_64 system?"
1715203,2017-09-05 18:08:44 UTC,"On 5 September 2017 at 18:55, kallisti5 <email address hidden> wrote:

> It was pointed out that the 2.10 release notes are pushing to drop Haiku
> support.  The qemu port is currently working as-is under Haiku.
>
> Was there a reason this was recommended? Is there anything Haiku can do
> to keep it from being dropped?
"
1715203,2020-09-05 09:43:17 UTC,"Is there any update on this? Could you provide a machine with ssh login to the QEMU project where QEMU could be built and tested on Haiku? Or can Haiku be installed automatically without graphical UI interactions? In that case, would it be feasible that you provide a VM setup for our tests/vm/ files in QEMU?"
1715212,2020-04-09 23:41:20 UTC,Can you confirm if this is still an issue in Ubuntu MATE 20.04 daily?
1715212,2020-06-09 04:17:30 UTC,[Expired for brisk-menu (Ubuntu) because there has been no activity for 60 days.]
1715222,2017-09-05 19:44:33 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x7f7fa93b86cd ""gstaudiodecoder.c"", line=line@entry=1505, func=func@entry=0x7f7fa93ba6b0 <__func__.21887> ""gst_audio_decoder_push_buffers"", message=message@entry=0x7f7f3c007270 ""assertion failed: (offset + len <= av)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x7f7fa93b86cd ""gstaudiodecoder.c"", line=line@entry=1505, func=func@entry=0x7f7fa93ba6b0 <__func__.21887> ""gst_audio_decoder_push_buffers"", expr=expr@entry=0x7f7fa93b8a17 ""offset + len <= av"") at ../../../../glib/gtestutils.c:2459
 gst_audio_decoder_push_buffers (dec=dec@entry=0x7f7f3c0175d0, force=force@entry=0) at gstaudiodecoder.c:1505
 gst_audio_decoder_chain_forward (dec=dec@entry=0x7f7f3c0175d0, buffer=0x0, buffer@entry=0x7f7f484ac990) at gstaudiodecoder.c:1652
 gst_audio_decoder_chain (pad=<optimized out>, parent=0x7f7f3c0175d0, buffer=0x7f7f484ac990) at gstaudiodecoder.c:1912"
1715222,2017-09-27 16:57:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715222,2021-02-25 09:36:20 UTC,No crashes after 19.10.
1715237,2017-12-08 14:39:23 UTC,"Amr, would you like to try preparing this SRU instead of waiting for someone else to get around to it?"
1715237,2017-12-08 13:35:37 UTC,Ping!
1715240,2017-09-05 21:08:15 UTC,"to clarify - Network autodetection fails because i dont use a DHCP-Server.
so the installer lets me choose to set a manual ip. but the network configuration step does not show.
to make it easier to understand please check out the picture attached. please excuse that they are from a german installation run."
1715240,2017-09-05 21:09:09 UTC,next image - cant put all in one comment - sry.
1715240,2017-09-05 21:09:47 UTC,"this is what correctly shows up @16.04.1
thank you in advance for your time..."
1715240,2017-09-05 21:15:59 UTC,i did not have the time to test it on physical hardware...
1715240,2017-09-06 00:21:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1715240,2017-09-06 12:29:16 UTC,"Thank you for pointing that out @Bot. This is my first bug report. I added the ""debian-installer"" as the affected package."
1715240,2017-09-20 10:18:07 UTC,Sorry for the delay in responding to you.
1715240,2017-09-23 11:10:39 UTC,"Hello there, I just stumbled on this bug while installing a vm on Proxmox VE 5."
1715240,2017-09-30 03:36:57 UTC,"Thank you @ xnox & bitwolf for your comments and suggestions.
I just tried an english installation run and the manual network configuration showed up!"
1715245,2017-11-14 06:33:49 UTC,With nvidia-384 it works.
1715249,2019-12-11 04:35:27 UTC,Appears to be fixed in 1.0beta2.  Will not migrate.  Closing.
1715259,2020-10-02 17:24:27 UTC,"It's the nature of a binary distribution like Debian and Ubuntu that dynamically linked things pull in dependencies to provide those dynamic libraries even if you don't want them yourself. Removing the dependency would require a rebuild from source or a patch to the code that pulls it in to use dlopen(3) or similar instead. However that's not within the normal design scope of anything in our ecosystem, so I don't think it's realistic to expect that."
1715259,2018-10-09 08:37:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715259,2020-10-02 17:28:58 UTC,"> the mailutils can use MySQL, PostgreSQL and ODBC as SQL interface. But package (library) pulls only MySQL client. It's strange, why mailutils does depend only on MySQL client? Why is such discrimination?
"
1715259,2018-01-25 13:05:25 UTC,"May be you don't need whole mailutils, but only a mailx client? Use other alternatives: bsd-mailx (minimalistic), s-nail (feature rich) or what your else prefer."
1715259,2018-01-25 13:01:54 UTC,"Yep, according to the mailutils documentation,"
1715259,2017-09-08 16:01:04 UTC,"Thank you, I see that now, and why does libmailutils5 need an libmysqlclient20?
I would request that if it does not really has a dependency then remove it from the dependency list.
Maybe this should be moved to the libmailutils5 package team?"
1715259,2017-09-07 18:29:15 UTC,">Also the documentation show that the packages are not part of the dependency list:
"
1715259,2017-09-05 23:15:02 UTC,"Also the documentation show that the packages are not part of the dependency list:
https://packages.ubuntu.com/search?keywords=mailutils&searchon=names&suite=zesty&section=all"
1715262,2017-09-06 00:58:54 UTC,This is nothing to do with vcenter.
1715262,2017-09-06 19:05:05 UTC,"As re-image only target-nodes and re-provisioning from SM handled hostname correctly,
need to figure out where this hostname change happened."
1715279,2017-09-06 02:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1715279,2017-09-07 18:49:10 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1715279,2017-09-08 07:20:35 UTC,"Thanks for your reply! Joseph. I have fixed this bug in 2.6.32, with the help of this git commit (e53376be) of the kernel. So in the 4.13, it is not a problem."
1715280,2017-09-07 12:05:32 UTC,"Try this without --asynchronous-upload.  If that does not work, I'll need
the -v9 logging done.  Thanks!"
1715280,2017-09-11 02:02:48 UTC,"Hi,
  I have taken out the --asynchronous-upload from the backups.  Will let you know how it goes."
1715280,2017-09-06 02:43:01 UTC,Let me know what else I can provide.  I am going to be increasing duplicity verbosity to info level and might get the occasion to increase to debug as well.
1715280,2017-09-07 01:59:32 UTC,"I can provide the following information today...  coredump, some basic gdb output, the duplicity logfile at info verbosity and the crash dump."
1715295,2018-02-06 12:32:19 UTC,This addresses part of the issue (adding new services to existing deployments) https://review.openstack.org/#/c/541225/
1715295,2018-02-09 01:52:50 UTC,"Reviewed:  https://review.openstack.org/541225
Committed: https://git.openstack.org/cgit/openstack/novajoin/commit/?id=e2a15af973935a2be650b5fab28d12cb26f32e12
Submitter: Zuul
Branch:    master"
1715310,2017-09-06 14:29:06 UTC,"If you're using sources for the puppet module, it was updated yesterday to swap out puppet/staging for puppet/archive.  https://github.com/voxpupuli/puppet-rabbitmq/commit/f223f66894e5e948bcd2cf05d7beaa911605b3ff  This shouldn't affect package based installations because we're using a version of 5.6.0 i believe https://github.com/redhat-openstack/rdoinfo/blob/master/rdo.yml#L746"
1715310,2017-09-19 14:44:51 UTC,"This seems to be still an issue running when puppetlabs_rabbitmq =source, fails with same error."
1715310,2017-09-19 15:32:37 UTC,"Want to add this to my above comment.
This bug affects all repo, not just consistent."
1715310,2018-02-25 16:34:34 UTC,I get this with RHOSP 12 / RHOSP 13.
1715314,2018-01-04 07:26:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715314,2018-01-25 14:18:22 UTC,Fixed in bionic
1715317,2018-12-05 16:27:12 UTC,"Reviewed:  https://review.openstack.org/505731
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=4d108c1c8f4ea9c147c4cac59fe9ecebf73e3bd7
Submitter: Zuul
Branch:    stable/pike"
1715317,2018-12-10 04:49:18 UTC,This issue was fixed in the openstack/os-vif 1.7.1 release.
1715317,2018-01-11 21:37:42 UTC,This issue was fixed in the openstack/os-vif 1.8.0 release.
1715317,2017-09-20 16:55:58 UTC,"Reviewed:  https://review.openstack.org/501132
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=fa4ff64b86e6e1b6399f7250eadbee9775c22d32
Submitter: Jenkins
Branch:    master"
1715317,2017-09-13 06:13:17 UTC,https://review.openstack.org/#/c/501132/
1715317,2017-09-12 22:53:11 UTC,"Sahid, could you please clarify what steps you have in mind to fix the problem ? When you say ""the linux bridge should learn the MAC addresses"", you mean the Neutron L2 agent running on the compute nodes, right?"
1715317,2017-09-20 16:59:43 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/505731"
1715325,2018-01-31 10:51:20 UTC,"Reviewed:  https://review.openstack.org/501527
Committed: https://git.openstack.org/cgit/openstack/cloudkitty/commit/?id=07ba0dc64474dd66b87bbd3649fe6d3026cfaf80
Submitter: Zuul
Branch:    master"
1715325,2017-09-06 09:20:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501178"
1715325,2017-09-06 10:25:42 UTC,https://review.openstack.org/#/c/501178/
1715325,2017-09-07 01:50:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501527"
1715325,2017-09-07 03:48:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501556"
1715325,2017-09-07 10:49:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501673"
1715325,2017-09-07 15:34:35 UTC,"Reviewed:  https://review.openstack.org/501178
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=2058b54b72a0c0ea25552afbc6e7f250f259876f
Submitter: Jenkins
Branch:    master"
1715325,2017-09-14 07:28:34 UTC,"Reviewed:  https://review.openstack.org/501556
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=3a7fc7a8e502f9ac0db28aefcd1e9f2742a15e44
Submitter: Jenkins
Branch:    master"
1715330,2017-09-12 09:48:34 UTC,"Created attachment 359592
[PATCH v2] wayland: Keep the inhibit shortcut dialog"
1715330,2017-09-12 13:04:27 UTC,Review of attachment 359592:
1715330,2017-09-14 07:36:51 UTC,"Comment on attachment 359586
[PATCH] wayland: do not leak shortcut inhibit data"
1715330,2017-09-14 07:37:35 UTC,"Comment on attachment 359592
[PATCH v2] wayland: Keep the inhibit shortcut dialog"
1715330,2017-09-12 08:50:15 UTC,Review of attachment 359586:
1715330,2017-10-11 14:01:25 UTC,I verified in artful with the latest mutter and cannot reproduce this defect. I'm marking it as fix released.
1715330,2017-10-20 08:25:47 UTC,Not fixed?... It's still happening with the latest gnome-shell/mutter -> bug 1725162
1715330,2017-11-03 01:59:18 UTC,"This crash continues to reoccur. See the duplicates and also:
https://errors.ubuntu.com/problem/923e1f8ff89aa3ff451c6aec260ec590152cf01a"
1715330,2017-11-03 02:48:28 UTC,"Those commit NNNN links aren't working. Can someone assign this bug to ""mutter"" to fix that?"
1715330,2017-10-04 14:26:18 UTC,*** Bug 768959 has been marked as a duplicate of this bug. ***
1715330,2017-09-12 08:49:34 UTC,Review of attachment 359585:
1715330,2017-09-12 04:13:13 UTC,"The bug is in gnome-shell, so moving there."
1715330,2017-09-12 08:33:34 UTC,"Created attachment 359585
[PATCH] wayland: Keep the inhibit shortcut dialog"
1715330,2017-09-12 07:04:47 UTC,"The issue is that virt-manager issues a grab() when it gains keyboard focus, and an ungrab() when it loses the keyboard focus."
1715330,2017-09-12 04:28:08 UTC,"Uh, must have slipped. Reopening."
1715330,2017-09-12 04:27:26 UTC,"To actually reproduce this reliably, the patch from bug 787570 is needed. On my set up, this exposes a gtk+/virt-manager bug resulting in the inhibit request being created and destroyed repeatedly."
1715330,2017-09-12 04:25:03 UTC,"Created attachment 359569
inhibitShortcuts: Don't destroy actor when hiding"
1715330,2017-09-12 01:18:45 UTC,Filed https://bugzilla.gnome.org/show_bug.cgi?id=787568 .
1715330,2017-09-12 01:16:46 UTC,"There's some discussion of this in https://bugzilla.gnome.org/show_bug.cgi?id=787240 , but that's really about another crash, so I figure this deserves its own report."
1715330,2017-09-12 00:12:57 UTC,"There's some discussion upstream too at https://bugzilla.gnome.org/show_bug.cgi?id=787240 - but note that it's a confused bug report that starts out being about a different bug, which is reported in Launchpad as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714330 . I will file a new upstream bug for the _console_boxed_value_set_x crash."
1715330,2017-09-12 00:04:03 UTC,"We're seeing what's probably the same crash in Fedora 27, though my reproducer is to start a VM in virt-manager:"
1715330,2017-09-06 08:42:48 UTC,"StacktraceTop:
 _cogl_boxed_value_set_x (bv=0x0, size=1, count=1, type=type@entry=COGL_BOXED_FLOAT, value_size=4, value=0x10080d8e800, transpose=0) at cogl-boxed-value.c:141
 _cogl_boxed_value_set_float (bv=<optimized out>, n_components=<optimized out>, count=<optimized out>, value=<optimized out>) at cogl-boxed-value.c:212
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x1007f034eb8, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffed1542b68, avalue=avalue@entry=0x7ffed1542a20) at ../src/x86/ffi64.c:525
 gjs_invoke_c_function (context=context@entry=0x1007d9a7000, function=function@entry=0x1007f034ea0, obj=..., obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at gi/function.cpp:1037"
1715330,2017-09-12 08:34:14 UTC,"Created attachment 359586
[PATCH] wayland: do not leak shortcut inhibit data"
1715338,2017-09-06 14:27:51 UTC,"This occurs after MAAS deploys a node for Juju.  The ""data"" field for the row contains base64-encoded gzip data which contains:
#cloud-config
apt_mirror: """"
output:
  all: '| tee -a /var/log/cloud-init-output.log'
package_update: true
package_upgrade: true
packages:
- bridge-utils
- curl
- cpu-checker
.
.
."
1715338,2017-11-22 19:20:42 UTC,"Can I ask what you are using this command for? This is a Django command that just happens to exist because we didn't take steps to block its usage. It is neither tested or supported in the context of MAAS, to my knowledge."
1715338,2017-11-23 08:14:26 UTC,We were thinking about using these below commands for collecting MAAS data from customers for support purposes in case of any need:
1715338,2018-02-23 15:57:03 UTC,"I recently ran into the same exact issue with MAAS + dumpdata, and determined that it was Juju (2.3.2 and 2.3.3) that triggeredg dumpdata to fail, while a ""normal"" machine deployment did not. This doesn't mean Juju is necessarily at fault, it just triggers this behavior."
1715340,2017-09-11 01:37:37 UTC,"@Swaminathan, I see the intial setup for dvr, I am confused about the FIP implementation, the FIP exists both on the source host and destination host, for the incoming FIP traffic from internet in dvr mode, how to know which fg port is the right nexthop, because both fg port proxy the port arp."
1715340,2017-09-07 22:20:24 UTC,"In the case of DVR we handle it in the pre-live migration. If the VM port is migrating, we do the intial setup in the host for the fipnamespace and as soon as the VM lands in the new host, we configure the rules for the fip."
1715340,2017-09-06 19:04:45 UTC,"I did some digging about this. It turns out that for the DVR case, L3 networking wiring is carried out during the pre_live_migration stage since the Mitaka release. These are the patchsets that implemented this:"
1715350,2017-09-06 10:23:11 UTC,"Ok, this looks really strange:"
1715350,2017-09-06 10:25:37 UTC,So I _purged_ the already removed libxvmc1:i386 (no idea how it actually got installed though) and then libxvmc1 (:amd64) updated/installed fine.  Very peculiar.
1715351,2017-09-06 10:17:02 UTC,Known issue: https://bugs.debian.org/873008 - will be fixed in Debian.
1715356,2017-09-09 06:18:23 UTC,"Clearly there isn't consensus on what it correct. The Fedora Virtualization Maintainers decided 0666, the Debian maintainers decided 0660. I think the respective mailing lists and/or bug trackers is a more appropriate place to discuss it."
1715356,2017-09-08 10:39:56 UTC,"Reviewed:  https://review.openstack.org/501909
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=b0e26030583f881934a42e6c5f121736f9f5341e
Submitter: Jenkins
Branch:    stable/pike"
1715356,2017-09-08 15:20:36 UTC,This needs to be mode 666 - there is a udev rule that does this:
1715356,2017-09-08 15:49:10 UTC,For reference this is the correct behaviour on Fedora/CentOS/RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=497341
1715356,2017-09-09 01:39:44 UTC,"Disagree on 666.  Just because udev does it, doesn't mean it is correct.  E.G. dd if=/dev/zero of=/dev/kvm will blow up the system.  kvm should only be accessible by the qemu group.  It is possible to properly set permissions for qemu:"
1715356,2017-10-31 04:48:39 UTC,"Reviewed:  https://review.openstack.org/501653
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=f1b98a4925826333cf22dafe15ef755066c51d48
Submitter: Zuul
Branch:    master"
1715356,2017-12-06 06:23:14 UTC,"The root cause for this issue is that qemu not run with nova user on debian.
If we set qemu running with nova user with this patch: https://review.openstack.org/#/c/525891/
Then we need to revert commit f1b98a4925826333cf22dafe15ef755066c51d48."
1715356,2017-12-06 06:35:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525900"
1715356,2017-12-07 14:48:40 UTC,This issue was fixed in the openstack/kolla 6.0.0.0b2 development milestone.
1715356,2017-12-13 13:10:59 UTC,"Reviewed:  https://review.openstack.org/525900
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=14cda91c4ef7020ac43f430869798387de15dae4
Submitter: Zuul
Branch:    master"
1715356,2018-01-30 00:17:44 UTC,This issue was fixed in the openstack/kolla 6.0.0.0b3 development milestone.
1715368,2017-09-27 05:59:27 UTC,"Hi Joseph,
Did we zero down on the kernel that we see this issue with.
Can we pull in the latest bnxt driver for 16.04.03 updates ?"
1715368,2017-09-27 16:20:09 UTC,We don't generally pull in a new version of a driver to fix a bug.  There is a document that describes the SRU process[0].
1715368,2017-09-21 11:19:54 UTC,"Hi Joseph,"
1715368,2017-10-02 19:22:18 UTC,Can you run: 'lspci -vvvnn' on a kernel that is working properly and attach the output?  That will give us the exact pci id's that need to be added.
1715368,2017-10-02 12:34:04 UTC,"You don't need to test multiple kernels or perform a bisect.  You know the latest kernel has the IDs, so just run a git blame on that module and see what commit added those new IDs to the list."
1715368,2017-09-20 19:24:20 UTC,"The purpose of going through a ""Reverse"" bisect is to identify the commit that fixes this bug and adds the proper CuW B1 device IDs.  To do that, we would want to figure out the last kernel that did not have the ids and the first kernel that did."
1715368,2017-10-12 11:12:29 UTC,"Hi Joseph,"
1715368,2017-09-13 15:14:31 UTC,Can you also test the follow kernels:
1715368,2017-09-12 08:50:00 UTC,"Hi Joseph,"
1715368,2017-09-11 14:46:06 UTC,I'd like to perform a reverse bisect to figure out which commit upstream fixes this regression.  We need to figure out  the last kernel that had this issue and the first kernel that did not.
1715368,2017-09-11 04:06:36 UTC,"We installed the latest upstream kernel and we do see the Broadcom devices listed.
Below is the mail I have copied from the Engineer who verified this."
1715368,2017-09-07 18:48:40 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1715368,2017-09-06 15:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1715368,2017-09-14 06:39:15 UTC,"Joseph,
Murali has tried with 4.4 kernel as well and even that kernel has Cu device
ID's. Can we not just pull in the latest kernel patch which is 4.13."
1715371,2017-09-07 11:46:19 UTC,"[cbrown2@flash neutron]$ grep -ir ""_ensure_vr_id_and_network"" *
neutron/tests/unit/db/test_l3_hamode_db.py:            net = self.plugin._ensure_vr_id_and_network(
neutron/tests/unit/db/test_l3_hamode_db.py:    def test_ensure_vr_id_and_network_net_exists(self):
neutron/tests/unit/db/test_l3_hamode_db.py:            self.plugin._ensure_vr_id_and_network(
neutron/tests/unit/db/test_l3_hamode_db.py:    def test_ensure_vr_id_and_network_concurrent_create(self):
neutron/tests/unit/db/test_l3_hamode_db.py:            net = self.plugin._ensure_vr_id_and_network(
neutron/tests/unit/db/test_l3_hamode_db.py:            self.plugin._ensure_vr_id_and_network(
neutron/tests/unit/db/test_l3_hamode_db.py:    def test_ensure_vr_id_and_network_interface_failure(self):
neutron/tests/unit/db/test_l3_hamode_db.py:    def test_ensure_vr_id_and_network_concurrent_delete(self):
neutron/tests/unit/db/test_l3_hamode_db.py:    def test_ensure_vr_id_and_network_concurrent_swap(self):
neutron/db/l3_hamode_db.py:    def _ensure_vr_id_and_network(self, context, router_db):"
1715371,2019-06-15 13:25:44 UTC,"Hi all,
Is this bug still valid? If yes then I would like to work on this.
Shall I remove _ensure_vr_id_and_network from the code?"
1715372,2017-09-06 11:23:52 UTC,Please assign to me for the code fix.
1715373,2017-09-06 17:47:49 UTC,Thank you!
1715373,2017-09-06 12:34:17 UTC,"Would it be possible to attach an SVG file that demonstrates the issue, Patryk? You don't need to include the whole drawing, only the part that is important for the report."
1715373,2017-09-06 14:00:22 UTC,"Yes, sure"
1715374,2019-03-12 19:00:53 UTC,"Change abandoned by Guilherme  Steinmuller Pimentel (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/642846"
1715374,2019-01-28 07:51:10 UTC,"Change abandoned by Ralf Haferkamp (<email address hidden>) on branch: master
Review: https://review.openstack.org/633220"
1715374,2019-03-07 20:32:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641793"
1715374,2019-03-08 03:15:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641907"
1715374,2019-03-08 03:28:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641911"
1715374,2019-03-08 16:20:53 UTC,"Change abandoned by Dan Smith (<email address hidden>) on branch: master
Review: https://review.openstack.org/641793
Reason: I still think the is-daemon check (and original justification) is wrong, but it's not the acute problem right now so I don't care enough to push on this."
1715374,2019-03-08 23:05:04 UTC,"Reviewed:  https://review.openstack.org/641911
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=817c95fdac916f9b736308cc18f884ba61f502fa
Submitter: Zuul
Branch:    master"
1715374,2019-03-12 18:17:20 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/642846"
1715374,2019-03-20 08:03:11 UTC,"Reviewed:  https://review.openstack.org/642842
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=02ca9bc374423567e695a075bbfbecef506c86cd
Submitter: Zuul
Branch:    stable/rocky"
1715374,2019-09-04 11:50:50 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/679974"
1715374,2019-04-03 17:14:19 UTC,"stack@train:~$ grep privsep /etc/nova/rootwrap.d/compute.filters
# os_brick.privileged.default oslo.privsep context
privsep-rootwrap-os_brick: RegExpFilter, privsep-helper, root, privsep-helper, --config-file, /etc/(?!\.\.).*, --privsep_context, os_brick.privileged.default, --privsep_sock_path, /tmp/.*
privsep-rootwrap-sys_admin: RegExpFilter, privsep-helper, root, privsep-helper, --config-file, /etc/(?!\.\.).*, --privsep_context, nova.privsep.sys_admin_pctxt, --privsep_sock_path, /tmp/.*
stack@train:~$
stack@train:~$ sudo systemctl status <email address hidden>
● <email address hidden> - Devstack <email address hidden>
   Loaded: loaded (/<email address hidden>; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-04-03 17:05:17 UTC; 8min ago
 Main PID: 19990 (nova-compute)
    Tasks: 29 (limit: 4915)
   CGroup: /<email address hidden>
           ├─19990 /usr/bin/python /usr/local/bin/nova-compute --config-file /etc/nova/nova-cpu.conf
           ├─20063 /usr/bin/python /usr/local/bin/privsep-helper --config-file /etc/nova/nova-cpu.conf --privsep_context vif_plug_ovs.privsep.vif_plug --privsep_sock_path /t
           └─20123 /usr/bin/python /usr/local/bin/privsep-helper --config-file /etc/nova/nova-cpu.conf --privsep_context nova.privsep.sys_admin_pctxt --privsep_sock_path /tm"
1715374,2019-04-03 17:23:25 UTC,This is the <email address hidden> status after a full restart and after just a HUP:
1715374,2019-04-03 17:24:32 UTC,There isn't much interesting in the unit file either:
1715374,2019-04-04 14:43:42 UTC,"FWIW the privsep SIGHUP issue with nova-compute isn't a regression in Stein, I was able to reproduce the issue with a stable/rocky devstack environment."
1715374,2019-09-03 19:10:02 UTC,This issue was fixed in the openstack/oslo.privsep 1.33.2 release.
1715374,2019-01-25 14:58:27 UTC,I've just resubmitted the old patch (with smaller changes to address the feedback) as this but can cause serious issue for upgrades  when following the official documentation.
1715374,2019-09-06 19:34:22 UTC,"Reviewed:  https://review.opendev.org/679974
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=73f1fda7e93325d3ca2b2c62afb17fe011d650f3
Submitter: Zuul
Branch:    master"
1715374,2019-10-01 18:29:09 UTC,"as of https://github.com/openstack/nova/commit/73f1fda7e93325d3ca2b2c62afb17fe011d650f3
this is now fix in nova 20.0.0.0rc1"
1715374,2020-01-09 18:50:31 UTC,This issue was fixed in the openstack/oslo.privsep 1.32.2 release.
1715374,2019-04-03 17:12:09 UTC,I created a train devstack today:
1715374,2019-01-25 14:53:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633220"
1715374,2019-03-12 18:06:54 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/642842"
1715374,2018-10-31 11:13:11 UTC,"We can't fix that for tripleo as it requires nova fixes for SIGHUP processing, so marked it invalid (for tripleo). Logrotate configs had been switched from sending SIGHUP to using copytruncate, so tripleo is not affected with this anymore."
1715374,2017-09-13 12:40:10 UTC,https://review.openstack.org/#/c/420026/
1715374,2018-09-11 10:44:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/601544"
1715374,2018-09-11 12:08:16 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/601558"
1715374,2018-09-18 15:30:24 UTC,"Reviewed:  https://review.openstack.org/596277
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=305445bac6ccf2cb491f451412035f08aa2928ba
Submitter: Zuul
Branch:    master"
1715374,2018-09-20 07:47:49 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604006"
1715374,2018-09-23 21:51:11 UTC,"Reviewed:  https://review.openstack.org/604006
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=fc31a1c649cca06d0340a15a55339757ff002775
Submitter: Zuul
Branch:    stable/rocky"
1715374,2018-09-24 09:26:59 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/604708"
1715374,2018-09-24 09:40:05 UTC,Remaining patches to close this bug:
1715374,2018-09-29 01:18:00 UTC,(and the backports)
1715374,2018-09-29 01:17:52 UTC,remaining patch : https://review.openstack.org/#/c/596275/
1715374,2018-09-30 19:30:58 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/606864"
1715374,2018-10-01 09:03:35 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/606908"
1715374,2018-11-08 09:30:57 UTC,"Change abandoned by sahid (<email address hidden>) on branch: master
Review: https://review.openstack.org/420026"
1715374,2018-10-03 09:45:59 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/604708
Reason: not needed any more as we fallback to copytruncate"
1715374,2018-10-03 09:46:31 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/601558
Reason: not needed any more as we fallback to copytruncate"
1715374,2018-10-03 11:48:42 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/601544
Reason: implementation falls back to copytruncate making this not needed any more"
1715374,2018-10-03 11:48:51 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/606908
Reason: implementation falls back to copytruncate making this not needed any more"
1715374,2018-10-03 11:48:59 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/606864
Reason: implementation falls back to copytruncate making this not needed any more"
1715374,2018-10-08 18:14:03 UTC,This issue was fixed in the openstack/puppet-tripleo 10.0.0 release.
1715374,2018-09-30 08:18:50 UTC,"Reviewed:  https://review.openstack.org/596275
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=d37c74d6382690a05ba3ca10edd7f2acb0fbbb2e
Submitter: Zuul
Branch:    master"
1715375,2017-10-05 13:39:51 UTC,I have a similar problem on Ubuntu 17.10: cheese takes about 15 seconds to start using an UVC camera (046d:0990) on USB3 but start immediately using an old Philips 740 webcam.
1715375,2017-09-06 11:38:48 UTC,Running Ubuntu Mate 17.10 Mate 1.18.0
1715375,2017-10-05 13:21:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715375,2017-10-09 19:00:49 UTC,"ott 09 20:54:58 corrado-beta-4ott cheese[4667]: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version
ott 09 20:55:12 corrado-beta-4ott cheese[4667]: Device '/dev/video0' cannot capture in the specified format: gstv4l2object.c(3640): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
... and a black screen with a message: There was an error playing video from the webcam"
1715381,2019-11-11 19:16:27 UTC,This has been fixed here:
1715386,2017-10-05 19:47:42 UTC,Whenever I see the word policy I fear that the topic can be turned into a huge discussion and we could easily go and attempt to boil the ocean.
1715386,2017-10-11 02:03:16 UTC,"Thanks for concern, Armando. I will show the answer the questions as below."
1715386,2017-10-12 00:18:23 UTC,Thanks for providing further details. There's still more to understand to better scope the problem. For instance:
1715386,2017-10-16 06:03:25 UTC,"Thanks for quick return. :)
As your suggestion&quesions, I answer them below.
* What kinds of rules can the user specify (e.g. source routing, type of traffic)?
For this point now, we are very interested on source based routing, such as subnet CIDR or specific IP address. Of course we could implement this feature for add other criteria either, such as ip address range, type of traffic, etc."
1715386,2017-11-06 11:37:49 UTC,"This most likely needs to be elaborated in the form of spec, but let see if amongst the drivers team, there's any comment on the direction of this proposal."
1715386,2017-11-09 03:43:20 UTC,"@Armando,
Thanks for return. I will search the proposal in the driver meeting and post the spec."
1715386,2017-11-16 11:06:35 UTC,i'm not sure if i understand the use case.  does it really require source routing?  isn't having multiple routers enough?
1715386,2017-11-29 02:21:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523658"
1715386,2017-12-15 03:32:01 UTC,"Oh, I'm sorry for refresh the status, I will move back."
1715386,2017-12-22 14:39:01 UTC,Spec is here: https://review.openstack.org/#/c/523658
1715386,2019-11-14 10:15:04 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/523658
Reason: According to what we agreed during Shanghai PTG, I abandon this patch for now due to no activity. If You would be interested in continue work on this, feel free to restore the patch."
1715393,2020-12-22 19:23:20 UTC,Weekly mode added in v2.0.0.
1715396,2019-02-09 01:34:36 UTC,"Well, this branch should preserve the current default behavior while giving the option to skip an authenticator when no context org is supplied:"
1715396,2019-02-08 21:07:39 UTC,I'm marking this bug as High priority since it can break login globally.
1715396,2017-12-09 17:58:32 UTC,"That's fine, we'll just carry around a local patch to invert the behavior."
1715396,2017-12-08 16:06:20 UTC,Confirmed in Evergreen 2.12.8
1715396,2017-12-08 18:18:08 UTC,Hi Dan.
1715396,2017-12-08 17:12:39 UTC,"John, thank you for digging into this.  I have a few questions:"
1715396,2017-12-09 15:05:53 UTC,"John, thank you for providing the requested details.  I will make every effort to push on this and see what I can make of it."
1715398,2017-09-06 14:17:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501276"
1715398,2017-09-08 09:16:38 UTC,The problem in our deployment was in cinder. Even without heat we could make cinder fail by deleting 10 volumes at once. We have cinder since a while and the db connection wasn't configured to use pymyql which is the recommended one since a while.
1715398,2018-02-08 16:27:32 UTC,"The proposed patch requires a resource schema change and we are past feature-freeze, so bumping this to Rocky."
1715406,2017-09-06 15:59:24 UTC,"> Can you call the python that is in $SNAPCRAFT_PART_INSTALL/bin/python instead of calling python from the host?
"
1715406,2017-09-06 16:00:10 UTC,"In case it wasn't clear: ""and this is where we started"" is what the tensorflow team came up with and ""for reference"" is the final version I wrote."
1715406,2017-09-06 15:38:58 UTC,"Regardless, I'll look into this this week."
1715406,2017-09-06 15:38:39 UTC,Can you call the python that is in $SNAPCRAFT_PART_INSTALL/bin/python instead of calling python from the host?
1715406,2017-09-06 14:32:58 UTC,And this is where we started: https://github.com/av8ramit/tensorflow/blob/d5cd86db4f53b486b97adb80b2a887d7ec93d5a0/tensorflow/tools/ci_build/snap/snapcraft.yaml
1715406,2017-09-06 14:24:18 UTC,For reference: https://github.com/evandandrea/tensorflow-snap/blob/86d3eb919522aeed188861b5e93e38a105b0b5c9/snapcraft.yaml
1715408,2017-09-09 16:31:22 UTC,More sample files. The zip file contains both .svg and the converted .pdf files.
1715408,2017-10-16 19:38:28 UTC,"Confirmed in Inkscape 0.92.1 and 0.92.2 as well as current master (dd69413884, 2017-10-15) on Windows 10 x64."
1715415,2017-09-10 14:30:26 UTC,Why is this an issue? DC++ only indexes each TTH once which makes is easy to just go through the files and get the size of unique files. AirDC++ needs to index all instances of the same file due to support for partial filelist refresh (which is missing from DC++) so it's not as simple (or fast) to figure out the unique files from it.
1715415,2017-09-12 23:06:33 UTC,It would make it possible to increase the share by adding the same files over and over again. That shouldn't be possible to do.
1715419,2017-09-07 01:32:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501511"
1715420,2017-09-06 15:47:11 UTC,Ah this is a good idea!
1715424,2019-02-03 13:19:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715429,2017-09-07 11:16:46 UTC,"Reviewed:  https://review.openstack.org/501423
Committed: https://git.openstack.org/cgit/openstack/charm-designate-bind/commit/?id=1b1fc3ea1d78ebf6a7591aa22ade47da90e0274b
Submitter: Jenkins
Branch:    master"
1715429,2017-09-07 03:04:32 UTC,"Reviewed:  https://review.openstack.org/501418
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=e3be7c0e8924c1c84f0c76d3d08d8059b891048c
Submitter: Jenkins
Branch:    master"
1715429,2017-09-07 03:53:29 UTC,"Reviewed:  https://review.openstack.org/501401
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=a6239d88777436afd1a34d7e8ad285d51add72bb
Submitter: Jenkins
Branch:    master"
1715429,2017-09-06 19:58:58 UTC,"Reviewed:  https://review.openstack.org/501396
Committed: https://git.openstack.org/cgit/openstack/charms.openstack/commit/?id=62f0b4769b72b6acd93184a0cadad5e7ea3126a8
Submitter: Jenkins
Branch:    master"
1715429,2017-09-06 19:56:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501401"
1715429,2017-09-06 20:43:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501423"
1715435,2018-10-23 14:05:35 UTC,"Yes, I mean set it to false. I have made an upgrade from 16.04. Maybe the key wasn't on its default value before the upgrade. But on ubuntu 16.04 I didn't have this problem."
1715435,2020-04-14 04:14:20 UTC,"Rocko, that is probably bug 1851992 and not this one. This one is about lightdm."
1715435,2020-04-13 12:08:08 UTC,My Ubuntu 20.04 installation just did this - something changed the org.gnome.desktop.lockdown disable-lock-screen to true and also the blank screen to never (did an update do this?).
1715435,2020-03-26 21:06:33 UTC,"The fix provided by chris-18 worked for me, same issue."
1715435,2019-11-30 20:36:42 UTC,Just ran into this issue on a fresh install of 19.10 with all updates installed as of 2019/11/30. The lock icon in the menu is missing and the keyboard shortcut is non-functional. The Screen Lock dialog in settings is greyed out entirely.
1715435,2019-05-18 20:24:31 UTC,Any news here? :(
1715435,2018-12-12 10:01:47 UTC,"> Disabling the key ""/org/gnome/desktop/lockdown/disable-lock-screen"" in dconf-editor solved the problem.
"
1715435,2018-10-17 23:25:25 UTC,"> Disabling the key ""/org/gnome/desktop/lockdown/disable-lock-screen"" in dconf-editor solved the problem.
"
1715435,2019-12-05 10:07:21 UTC,Bug 1851992 has been opened about the disable-lock-screen option too. But it's private for now.
1715435,2018-05-21 12:42:58 UTC,"Sorry, small adjustment. I use wayland as default since 17.10 with gdm (works well in general for me):"
1715435,2018-10-17 07:18:06 UTC,"I had the same problem on ubuntu 18.04. Disabling the key ""/org/gnome/desktop/lockdown/disable-lock-screen"" in dconf-editor solved the problem."
1715435,2017-10-20 21:59:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715435,2017-11-12 11:20:40 UTC,"I am using gdm3 (AFAIK) and super-L also stopped working just now when I did ""apt dist-upgrade"". So in my case it does not seem to depend on lightdm vs gdm3."
1715435,2017-09-06 16:23:32 UTC,Using the lock icon in the upper right corner did work though.
1715435,2017-12-13 14:09:03 UTC,Same issue after an upgrade from 17.04
1715435,2018-05-14 19:32:25 UTC,Ubuntu 18 is still with the same bug
1715435,2018-05-21 12:38:18 UTC,"Confirm (Super - L) not working on Ubuntu 18.04, switching keyboard language does not work either most of the time (Super + Space). Those I use the most. Extremely annoying after some time, especially when using dual screens (since the Gnome top bar is only on one monitor which is even more annoying: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1682542)."
1715435,2017-11-12 11:29:58 UTC,"In my case I was able to workaround this issue by changing the lock shortcut from super-L to ctrl-alt-L. All shortcuts using super are broken. My ""window action key"" in gnome-tweaks is ""super"". So it appears that it is impossible to use the window action key for shortcuts any more after some very recent updata."
1715438,2017-09-06 16:30:03 UTC,This change was made by a bot.
1715438,2017-09-06 16:35:10 UTC,"It's a pity that everything is in English, being French I do not understand your answers for solutions. What can I do ?"
1715442,2017-09-20 08:45:55 UTC,Backported to 0.92.x.
1715442,2017-09-07 14:13:27 UTC,"Based on tests with archived trunk builds and the three test files (Text_1.svg, 1715442-Text_2.svg, 1715442_Simplified.svg), inkscape hanging on load"
1715442,2017-09-07 21:08:50 UTC,"Hachmann wrote:

> Does this also fix the bugs you linked in the description, su_v?
"
1715442,2017-09-07 19:08:41 UTC,"Fix confirmed with Inkscape 0.92+devel (bfc701393, 2017-09-07) on Windows 10 - all three test files open ok."
1715442,2017-09-07 16:11:17 UTC,This turns out to be a bug under very special conditons:
1715442,2017-09-07 15:53:05 UTC,"Thank you for all that testing work, su_v and Tav!"
1715442,2017-09-07 13:28:21 UTC,"Tavmjong Bah wrote:

> A very simple test file. (...)
"
1715442,2017-09-07 20:16:54 UTC,"Does this also fix the bugs you linked in the description, su_v?"
1715442,2017-09-06 18:46:36 UTC,"su_v wrote:

> Further detail: flowing text into such a path fails in 0.92.2 (works
> in 0.91). (...) the flowed text is entirely truncated (not visible).
"
1715442,2017-09-06 18:39:05 UTC,"Further detail: flowing text into such a path fails in 0.92.2 (works in 0.91). Please test with the attached ""unflowed"" version in 0.92.2 (select all, Text > Flow into frame): the flowed text is entirely truncated (not visible)."
1715442,2017-09-06 18:27:20 UTC,Reduced test case (created with 0.91 r13725) attached.
1715442,2017-09-06 17:59:24 UTC,"That could explain it, V, yes. But I don't remember it, it's only that I had made a note in my workshop notes libreoffice file."
1715442,2017-09-06 17:38:47 UTC,"Hachmann wrote:

> because in Version 0.91, normal non-flowed text would just 'vanish'.
"
1715442,2017-09-06 16:54:43 UTC,"(Additional info: I just found that I had labelled the document as 'somehow broken', because in Version 0.91, normal non-flowed text would just 'vanish'. So perhaps not a real issue."
1715442,2017-09-07 11:57:50 UTC,A very simple test file.
1715462,2017-10-24 12:42:58 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1715462,2017-09-25 14:28:00 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1715462,2017-09-08 21:29:04 UTC,"Reviewed:  https://review.openstack.org/501821
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a98a52d85eb2c695568ac01d5ae7baf1bc20d9e3
Submitter: Jenkins
Branch:    stable/pike"
1715462,2017-09-06 20:12:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501408"
1715462,2017-09-07 17:07:20 UTC,"Reviewed:  https://review.openstack.org/501408
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bf0f5d475458a67a12000ff49a8c5285c3ac9e45
Submitter: Jenkins
Branch:    master"
1715462,2017-09-06 19:49:42 UTC,"Just to update, this only affects Pike and newer due to the fact that the codebase for quota recheck not being present before.  I'll be publishing a fix shortly (unit tests okay, testing functional locally before pushing up)."
1715462,2017-09-07 17:36:08 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/501821"
1715463,2017-12-01 09:00:40 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/524531"
1715463,2017-12-18 12:51:31 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1715463,2017-12-11 09:20:21 UTC,"Reviewed:  https://review.openstack.org/524531
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2d79baf6a3ce4529ba61a5efded7f043d89825a2
Submitter: Zuul
Branch:    stable/pike"
1715463,2017-10-24 12:42:49 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1715463,2017-09-06 19:14:41 UTC,"What sequence of events got you here? Is this changing the deployment type post upgrade as well? It would be good to fully qualify what failed here, and why we didn't catch it, and if we need to put something into nova-manage to help."
1715463,2017-09-06 20:31:05 UTC,"If you look at the code in the patch, or rather the code before the patch, it tries to update one service-binary 'osapi_compute'. If it doesn't find it, it tries to insert a *different* service-binary 'nova-osapi_compute'."
1715463,2017-09-06 20:18:21 UTC,"We're running nova-os-compute-api (nova/api/openstack/compute/wsgi.py), nova-metadata-api (nova/api/metadata/wsgi.py) and nova-placement-api (nova/api/openstack/placement/wsgi.py) under uwsgi. Each in separate containers, under venvs."
1715463,2017-09-06 19:23:24 UTC,Patch in progress - https://review.openstack.org/#/c/501359/
1715463,2017-10-18 10:55:47 UTC,"Reviewed:  https://review.openstack.org/501359
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b4a021e4224981e83dca67e7519458f9939f3cd
Submitter: Zuul
Branch:    master"
1715465,2017-09-14 20:23:28 UTC,The role assignment for the heat_domain_admin was incorrectly scoped for v3 deployments; raising a fix now.
1715465,2017-09-20 12:45:16 UTC,"Fix proposed to branch: stable/17.08
Review: https://review.openstack.org/505614"
1715465,2017-09-20 12:17:05 UTC,"Reviewed:  https://review.openstack.org/504219
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=501e3415b346322769947ddfb5665e56490b3e3f
Submitter: Jenkins
Branch:    master"
1715465,2017-09-14 21:30:09 UTC,I can confirm the patch posted by James fixes the problem here is the result after the fixes.
1715465,2017-09-21 08:46:33 UTC,"Reviewed:  https://review.openstack.org/505614
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=f30723b839fb91f0f50873b16cc724c02845e324
Submitter: Jenkins
Branch:    stable/17.08"
1715465,2017-09-14 16:24:51 UTC,"This is for OPNFV E release which is based on Ocata and current charms integrated in this is 17.08 bundle file is as follows.
http://paste.ubuntu.com/25532647/"
1715465,2017-09-14 20:31:35 UTC,https://review.openstack.org/504219
1715465,2017-09-08 06:35:04 UTC,"I test this on my lab, heat_template_version: 2016-04-08, not 2017-02-24.
But the issue don't be reproduced.
can you show your heat.conf"
1715465,2017-09-08 05:20:44 UTC,yes thats part of post deployment step we execute and I can confirm that was executed as we have CI in OPNFV community and we are able to reproduce there also.
1715465,2017-09-07 17:19:11 UTC,"Out of curiosity, did you execute the heat action below before trying to use Heat?"
1715465,2017-09-07 17:02:44 UTC,"I tested this on our lab and was able to reproduce the issue, just as narinder reported above."
1715465,2017-09-06 19:13:43 UTC,"cat joid_config/admin-openrc
export OS_AUTH_URL=http://192.0.5.229:5000/v3
export OS_USER_DOMAIN_NAME=admin_domain
export OS_PROJECT_DOMAIN_NAME=admin_domain
export OS_USERNAME=admin
export OS_TENANT_NAME=admin
export OS_PROJECT_NAME=admin
export OS_PASSWORD=openstack
export OS_IDENTITY_API_VERSION=3
export OS_REGION_NAME=RegionOne"
1715465,2017-09-06 18:39:09 UTC,"heat log sho the below error.
2017-09-06 10:56:49.663 27620 WARNING oslo_config.cfg [-] Option ""rabbit_password"" from group ""oslo_messaging_rabbit"" is deprecated for removal.  Its value may be silently ignored in the future.
2017-09-06 17:01:16.177 27616 WARNING oslo_config.cfg [req-d4e1387c-9a1a-4957-9e19-cc66fe5fa44c - admin - - -] Option ""auth_plugin"" from group ""trustee"" is deprecated. Use option ""auth_type"" from group ""trustee"".
2017-09-06 17:01:16.925 27616 ERROR heat.engine.clients.keystoneclient [req-d4e1387c-9a1a-4957-9e19-cc66fe5fa44c - admin - - -] Domain admin client authentication failed
2017-09-06 17:01:17.673 27617 ERROR heat.engine.clients.keystoneclient [req-d4e1387c-9a1a-4957-9e19-cc66fe5fa44c - admin - - -] Domain admin client authentication failed
2017-09-06 17:01:19.341 27619 ERROR heat.engine.clients.keystoneclient [req-d4e1387c-9a1a-4957-9e19-cc66fe5fa44c - admin - - -] Domain admin client authentication failed
2017-09-06 17:03:21.484 27620 WARNING oslo_config.cfg [req-729f984d-ac3b-4cba-b679-22fa46711ece - admin - - -] Option ""auth_plugin"" from group ""trustee"" is deprecated. Use option ""auth_type"" from group ""trustee"".
2017-09-06 17:03:22.165 27620 ERROR heat.engine.clients.keystoneclient [req-729f984d-ac3b-4cba-b679-22fa46711ece - admin - - -] Domain admin client authentication failed
2017-09-06 17:03:22.892 27618 ERROR heat.engine.clients.keystoneclient [req-729f984d-ac3b-4cba-b679-22fa46711ece - admin - - -] Domain admin client authentication failed
2017-09-06 17:03:24.497 27618 ERROR heat.engine.clients.keystoneclient [req-729f984d-ac3b-4cba-b679-22fa46711ece - admin - - -] Domain admin client authentication failed
2017-09-06 18:32:27.573 27617 WARNING oslo_config.cfg [req-3b132976-9f5a-4e68-8719-9d1597be163e - admin - - -] Option ""auth_plugin"" from group ""trustee"" is deprecated. Use option ""auth_type"" from group ""trustee"".
2017-09-06 18:32:28.194 27617 ERROR heat.engine.clients.keystoneclient [req-3b132976-9f5a-4e68-8719-9d1597be163e - admin - - -] Domain admin client authentication failed
2017-09-06 18:32:28.948 27620 ERROR heat.engine.clients.keystoneclient [req-3b132976-9f5a-4e68-8719-9d1597be163e - admin - - -] Domain admin client authentication failed
2017-09-06 18:32:30.553 27620 ERROR heat.engine.clients.keystoneclient [req-3b132976-9f5a-4e68-8719-9d1597be163e - admin - - -] Domain admin client authentication failed
2017-09-06 18:35:58.046 27616 ERROR heat.engine.clients.keystoneclient [req-2ccc34cd-821a-47cd-be03-4350c1f880f6 - admin - - -] Domain admin client authentication failed
2017-09-06 18:35:58.759 27617 ERROR heat.engine.clients.keystoneclient [req-2ccc34cd-821a-47cd-be03-4350c1f880f6 - admin - - -] Domain admin client authentication failed
2017-09-06 18:36:00.306 27617 ERROR heat.engine.clients.keystoneclient [req-2ccc34cd-821a-47cd-be03-4350c1f880f6 - admin - - -] Domain admin client authentication failed"
1715465,2017-09-08 06:49:00 UTC,here is my heat.conf
1715467,2017-09-06 19:58:49 UTC,Most important question: Which version of Inkscape?
1715467,2017-09-06 20:12:49 UTC,"Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1715467,2017-09-06 20:34:07 UTC,I can confirm that the PDF import dialog is opened in a strange position.
1715467,2017-09-07 11:06:56 UTC,"The behavior I experienced was immediately after a first-time-ever install of Inkscape on the computer. So if any usability problems are related to settings, it indicates that better default settings are in order, or else a re-thinking of what those settings are."
1715480,2017-09-08 10:40:40 UTC,"Okay, then: yes :)
Thank you!"
1715480,2017-09-08 10:11:11 UTC,"> I don't know what a paint server is, (...)
"
1715480,2017-09-08 10:00:48 UTC,"Thank you for the corrections, su_v. I've updated the description."
1715480,2017-09-08 07:21:21 UTC,"> Filters, patterns or opacity (...)
"
1715483,2017-09-08 06:17:55 UTC,"Related comment by developer who implemented initial version of the Glyphs dialog:
https://bugs.launchpad.net/inkscape/+bug/343186/comments/14"
1715483,2017-09-08 10:03:24 UTC,"Those plans were good :) Thank you, V, for digging around a bit in the fixed bugs!"
1715483,2019-08-07 01:43:47 UTC,Transferred to: https://gitlab.com/inkscape/inbox/issues/744
1715486,2017-09-11 07:44:25 UTC,"Reviewed:  https://review.openstack.org/501472
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=2f9ca1b4defb68a394f874b02b205b6ec27b9179
Submitter: Jenkins
Branch:    master"
1715486,2017-09-13 13:21:27 UTC,"Reviewed:  https://review.openstack.org/501518
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=887fa746aec17e673e418d96f2e8476194c38de5
Submitter: Jenkins
Branch:    master"
1715486,2017-09-15 06:47:12 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502029"
1715486,2017-09-22 06:42:55 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502027"
1715486,2017-09-27 17:01:11 UTC,fixed in https://review.openstack.org/#/c/498275/
1715486,2017-09-29 04:46:51 UTC,"Reviewed:  https://review.openstack.org/501515
Committed: https://git.openstack.org/cgit/openstack/masakari/commit/?id=d9c87bba0adc3f27b90d8309381c3f1445ba7bf1
Submitter: Zuul
Branch:    master"
1715486,2017-10-16 01:05:30 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502023"
1715486,2017-10-24 03:18:00 UTC,This issue was fixed in the openstack/cinder 12.0.0.0b1 development milestone.
1715486,2018-02-08 17:36:24 UTC,This issue was fixed in the openstack/magnum 6.0.0 release.
1715486,2017-11-07 00:32:40 UTC,This issue was fixed in the openstack/manila 6.0.0.0b1 development milestone.
1715486,2017-11-15 14:55:55 UTC,This issue was fixed in the openstack/ironic 9.2.0 release.
1715486,2017-12-07 14:31:32 UTC,This issue was fixed in the openstack/senlin 5.0.0.0b2 development milestone.
1715486,2018-01-18 19:02:30 UTC,glance: http://logs.openstack.org/73/535173/3/check/cross-glance-py35/9b06b73/testr_results.html.gz
1715486,2018-01-18 19:52:44 UTC,"This new Glance failure looks to be a little different. Instead of changing the location, it looks like they have now changed the default format for zulu to UTC."
1715486,2018-01-18 20:41:37 UTC,Opened https://bugs.launchpad.net/glance/+bug/1744160 to track this new failure.
1715486,2018-01-26 00:20:33 UTC,This issue was fixed in the openstack/senlin 5.0.0.0b3 development milestone.
1715486,2017-09-09 15:43:31 UTC,"Reviewed:  https://review.openstack.org/501516
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=1ae1a61a34179ca6d028d43498351214db9ef60a
Submitter: Jenkins
Branch:    master"
1715486,2017-10-25 20:45:30 UTC,This issue was fixed in the openstack/watcher 1.5.0 release.
1715486,2017-09-08 10:29:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502029"
1715486,2017-10-12 08:07:42 UTC,"Reviewed:  https://review.openstack.org/502028
Committed: https://git.openstack.org/cgit/openstack/iotronic/commit/?id=7cf5f4de23c4ecf7945e8cdb4d082d1da277b924
Submitter: Jenkins
Branch:    master"
1715486,2017-09-08 10:15:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502027"
1715486,2017-09-06 21:12:44 UTC,Looks like there are several projects that will need to update for this change:
1715486,2017-09-06 21:28:21 UTC,There was another bug 1715486 for this which fixed it in nova already:
1715486,2017-09-06 21:46:55 UTC,oslo.versionedobjects already in the works with https://bugs.launchpad.net/nova/+bug/1713354
1715486,2017-09-06 21:49:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501472"
1715486,2017-09-06 21:52:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501474"
1715486,2017-09-06 21:57:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501479"
1715486,2017-09-06 21:59:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501480"
1715486,2017-09-07 01:37:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501515"
1715486,2017-09-06 21:55:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501476"
1715486,2017-09-07 01:42:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501518"
1715486,2017-09-07 01:39:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501516"
1715486,2017-09-08 09:01:03 UTC,"For reference, the patch [1] that caused this issue was introduced in 0.1.12."
1715486,2017-09-07 17:47:42 UTC,"Reviewed:  https://review.openstack.org/501476
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=c8b8fe86fc8640386fc59e3f42f9995e8507ab45
Submitter: Jenkins
Branch:    master"
1715486,2017-09-07 09:45:19 UTC,"Reviewed:  https://review.openstack.org/501479
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=640217d22ebfc07fbab84ef7b8c3c974fbc75a8a
Submitter: Jenkins
Branch:    master"
1715486,2017-09-08 10:06:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502023"
1715486,2017-09-07 03:02:29 UTC,"Reviewed:  https://review.openstack.org/501474
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=a63d4bafdbadf3308ee368c85e693184efc592b4
Submitter: Jenkins
Branch:    master"
1715486,2017-09-07 03:16:22 UTC,"Reviewed:  https://review.openstack.org/501480
Committed: https://git.openstack.org/cgit/openstack/mogan/commit/?id=07caad2946177c0aee972f6b535fe08d44d4d5c0
Submitter: Jenkins
Branch:    master"
1715486,2017-09-08 10:19:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502028"
1715488,2017-09-07 21:30:04 UTC,This change was made by a bot.
1715489,2017-09-07 19:08:37 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-September/086902.html
1715489,2017-09-12 19:27:27 UTC,This bug was fixed in the package linux-azure - 4.11.0-1009.9
1715490,2017-09-21 19:37:35 UTC,"From what I can tell this only happens when I have the video configured for VGA, with QXL I am able to enter the passphrase at with pretty plymouth."
1715490,2020-10-22 19:00:09 UTC,"closing, it hasn't get any activity in years"
1715490,2018-06-18 17:13:40 UTC,Perhaps we should just close this. What do you think?
1715490,2017-10-04 23:27:34 UTC,"I don't know if it is related but I've also noticed that I cannot use the command ""videoinfo"" in a grub console if I have the virtual machine setup to use the VGA driver but I can if I use the QXL driver."
1715490,2017-09-21 21:31:02 UTC,"I can also enter my passphrase when using the Cirrus driver, but then something else with the boot hangs."
1715490,2017-09-21 14:48:57 UTC,"I think this is likely VM setup: I have installed a new system with the 20170919 image (a Thinkpad T450p), and the plymouth screen responds correctly. I will try to reproduce this in a VM here."
1715490,2017-09-06 23:59:19 UTC,This also happened to me after install Ubuntu 16.04.3 so perhaps it something with my virtual machine setup.
1715490,2017-09-06 21:10:08 UTC,This is what I'm referring to as plymouth text which does accept my passphrase.
1715490,2017-09-06 21:09:23 UTC,"This what I see when I return to tty7, yes ubuntu was my passphrase."
1715490,2017-09-06 21:08:34 UTC,This is the screen that does not accept my input.
1715490,2017-09-21 14:49:18 UTC,What VM configuration were you using?
1715492,2020-03-02 07:05:52 UTC,Closing as part of the bug migration (http://alpha.inkscape.org/bug-migration/). The issue has been manually migrated to GitLab (see https://gitlab.com/inkscape/inbox/issues/1942)
1715493,2017-10-24 12:42:59 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1715493,2017-09-25 14:28:02 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1715493,2017-09-08 21:28:21 UTC,"Reviewed:  https://review.openstack.org/501820
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2ad865fb36fd92cf6d950fe05cd3d3eaa3488ed5
Submitter: Jenkins
Branch:    stable/pike"
1715493,2017-09-08 00:49:01 UTC,"Reviewed:  https://review.openstack.org/501819
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=72e50bedd65787ebbfddf41759babebcb281e7fb
Submitter: Jenkins
Branch:    stable/pike"
1715493,2017-09-08 00:46:14 UTC,"Reviewed:  https://review.openstack.org/501818
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a791df1ecf5a60cd4e7bfedd0df8aae294d2df1
Submitter: Jenkins
Branch:    stable/pike"
1715493,2017-09-07 17:35:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/501820"
1715493,2017-09-07 17:35:31 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/501819"
1715493,2017-09-07 17:35:15 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/501818"
1715493,2017-09-07 17:05:07 UTC,"Reviewed:  https://review.openstack.org/501514
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bcd1f1d8c833c4c12399ba84934a9a72a2bde122
Submitter: Jenkins
Branch:    master"
1715493,2017-09-07 17:04:22 UTC,"Reviewed:  https://review.openstack.org/501513
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=53c2a979e25c6b017f2e8c7b8c357f275bb13a7a
Submitter: Jenkins
Branch:    master"
1715493,2017-09-07 01:36:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/501514"
1715493,2017-09-07 01:36:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/501513"
1715493,2017-09-06 21:21:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501452"
1715493,2017-09-07 17:06:14 UTC,"Reviewed:  https://review.openstack.org/501452
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e801775959a8ae0f9c09767021a40b6a746d1928
Submitter: Jenkins
Branch:    master"
1715501,2017-09-06 23:15:32 UTC,"Michael,"
1715501,2017-09-07 01:11:26 UTC,/var/log/maas/*.log
1715501,2017-09-07 01:15:40 UTC,Below is the error message.
1715501,2019-09-19 12:04:31 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1715526,2017-09-08 08:30:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501994"
1715527,2017-09-07 02:47:01 UTC,"I did the install today and got both vaapi, fluendo mp3, and -ugly - maybe you got Flash installed and got the old restricted one?"
1715527,2017-09-07 03:19:30 UTC,"OK, it's just because I don't allow machines to connect to the internet during install."
1715527,2018-03-02 05:06:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715529,2017-09-26 13:47:59 UTC,"I don't think this requires a spec, and it seems strait forward enough. Partially in nova, which as I understand it has an open blueprint for, but supporting this internally would be cleaner.  I'm for approving this RFE, although Hironori indicated that he would post proof of concept code soon."
1715529,2017-11-13 22:14:12 UTC,"I agree, I don't think it requires a spec. Am approving it. Thanks Hironori!"
1715529,2017-11-13 22:21:10 UTC,"I think we kind of set ourselves up for this with the original bfv effort, so I'm +2 approval without spec, given we made the data storage such to support new things."
1715529,2018-01-25 01:00:31 UTC,Hironori submitted this patch: https://review.openstack.org/#/c/532442/
1715529,2018-01-26 00:27:57 UTC,This issue was fixed in the openstack/python-ironicclient 2.2.0 release.
1715533,2017-10-25 19:22:29 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1715533,2017-10-24 12:42:15 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1715533,2017-10-17 20:09:10 UTC,"Reviewed:  https://review.openstack.org/507557
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e0ed9d8532873bbfff9648fd020c4e6e8e15ba7
Submitter: Zuul
Branch:    stable/newton"
1715533,2017-10-04 23:51:19 UTC,"Reviewed:  https://review.openstack.org/507556
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f5e8060441f74b9add0f683558e2f4648ef54efd
Submitter: Jenkins
Branch:    stable/ocata"
1715533,2017-09-28 07:44:49 UTC,"Reviewed:  https://review.openstack.org/507552
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c3f3f62b090f6b2e4b69db09e16cac0fe6c843c9
Submitter: Jenkins
Branch:    stable/pike"
1715533,2017-09-26 14:17:39 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/507552"
1715533,2017-09-26 14:20:18 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/507557"
1715533,2017-09-26 14:19:30 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/507556"
1715533,2017-11-01 00:20:24 UTC,This issue was fixed in the openstack/nova 14.0.9 release.
1715533,2017-09-09 12:05:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502236"
1715533,2017-09-07 05:45:42 UTC,Set the status 'In-Progess' because this bug report has assignee.
1715533,2017-09-27 22:59:12 UTC,"Reviewed:  https://review.openstack.org/502236
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=87a53cc45283a81386ee8f870a25a315b8527749
Submitter: Jenkins
Branch:    master"
1715533,2017-11-15 01:06:55 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1715537,2020-03-26 02:57:26 UTC,"Error was visible in the log, address/port already in use."
1715541,2017-09-21 15:41:55 UTC,can't reproduce. my output is http://paste.openstack.org/show/621638/
1715541,2017-09-21 15:45:17 UTC,the fields indeed missing in the next link
1715541,2017-09-21 16:30:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506280"
1715541,2017-09-29 00:33:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/508368"
1715541,2017-10-10 23:28:07 UTC,"Reviewed:  https://review.openstack.org/505837
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=f8a42d366c0d20918fee579406feffe83c1f7b9a
Submitter: Jenkins
Branch:    master"
1715545,2018-02-15 23:54:02 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1715545,2018-02-05 14:22:48 UTC,"Reviewed:  https://review.openstack.org/515410
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad6208c19c2011718db68d1d3ec0ea7d582b320b
Submitter: Zuul
Branch:    stable/pike"
1715545,2017-10-26 13:35:37 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515410"
1715545,2017-09-19 13:23:35 UTC,"Reviewed:  https://review.openstack.org/502017
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2fce8a1396816a3917606b8d736f3d5b57ae7f56
Submitter: Jenkins
Branch:    master"
1715545,2017-09-08 09:35:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502017"
1715545,2017-10-24 12:42:35 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1715552,2018-02-28 07:03:59 UTC,"Yes +1 on patrick, qorks for me, thanks."
1715552,2017-10-25 20:31:36 UTC,Upgrading to vmware workstation 14 is inconvenient because:
1715552,2017-10-26 13:04:34 UTC,Oscar: I only have player 14. But maybe you can test this:
1715552,2017-10-26 23:53:32 UTC,I confirm that the recipe listed by Patrick (thanks!) works.
1715552,2017-11-03 05:21:30 UTC,+1 on Patrick's fix.  Thanks for the update.
1715552,2018-02-28 12:43:03 UTC,"the only thing needed for the bug referenced here, is the line (already commented on the Patrick's fix):"
1715552,2018-09-05 04:25:18 UTC,Really the update is very usefull...Awsome!
1715552,2018-05-16 01:15:54 UTC,"A small correction to the step 2 above:
In the example, after you do the 'git clone ...' command, you have to change directory to the git repo dir (e.g. 'cd vmware-host-modules') before issuing the 'git checkout workstation-x.y.z'. Else, you'd get a git error like this: 'fatal: not a git repository ...', which, while harmless, it might confuse you. Sorry for the lapse."
1715552,2018-05-22 22:17:13 UTC,"Thank you iLugo, your workaround instructions work for me with 18.04 and VMPlayer 12.5.9"
1715552,2018-07-09 16:20:57 UTC,"@Michael Harmon, you are very welcome.
I can confirm that my above procedure also works for Workstation Pro 14.1.2."
1715552,2018-08-21 18:58:42 UTC,It works with VMware 14.
1715552,2017-10-25 19:55:34 UTC,with vmware-player 14.0.0 it works for me
1715552,2018-09-12 08:28:50 UTC,"Many thanks, iLugo!
I followed your instructions from 2018-07-09 and wmplayer 12.5.9 worked at once! I run ubuntu 18.04."
1715552,2018-05-16 01:02:49 UTC,"To successfully install VMware Workstation 12.5.9 (and probably 14.x also) in Ubuntu 18.04, follow this procedure:
1. Do the normal installation of VMWare Workstation. Do not run vmware yet. It will fail anyway.
2. Do a git clone (or download as zip package) of the vmware-host-modules project hosted in https://github.com/mkubecek/vmware-host-modules. Make sure to read the README to understand what branch you need to checkout. Detailed instructions for doing this is in the INSTALL document. For example: If you are installing Workstation 12.5.9, then you'd do:
   git clone https://github.com/mkubecek/vmware-host-modules.git
   git checkout workstation-12.5.9
(This project is recommended by: https://wiki.archlinux.org/index.php/VMware#Kernel_modules).
3. cd to the git repo dir (vmware-host-modules) and follow the instructions in the INSTALL document of the project to ""Build and install modules - DIRECTLY"", i.e., the section ""2a."" as of this writing. This is important, as it will ensure that your modules are build specifically for your CURRENT kernel. Follow all the steps carefully. You are NOT done yet. If you run vmware at this point, you will get the error that this bug mentions. Next step, you'll fix it.
4. Enter the following sequence of commands in the console:"
1715552,2017-10-25 13:56:27 UTC,"Patrick: are you sure you fixed the bug described on this report? The commit you mention is for fixing a problem with memory handling, which is a different issue altogether. This bug is about VMware WS 12.5.7 failing to start on Ubuntu 17.10. AFAIK WS 14 starts fine on 17.10."
1715552,2017-10-11 01:49:26 UTC,"After testing further, I actually see the same thing with VMWare Player 14.0.0:"
1715552,2017-10-23 19:27:03 UTC,Confirmed on Ubuntu 17.10
1715552,2017-10-22 15:23:09 UTC,"This occurs also with Kubuntu 17.10 RTM and VMware Workstation Pro 12.5.7-5813279.
I remember that on 17.04 it didn't occur.
I used to install the same version of VMWare Workstation in Kubuntu 17.04, running inside a virtual machine (just for testing purposes)."
1715552,2017-10-11 21:47:29 UTC,I am stuck on 12.5.7 for the time being so if anyone gets past the:
1715552,2019-04-10 22:15:35 UTC,Running Ubuntu 18.04.1 LTS with Workstation 12.5.9 installed. Encountered the dreaded error:
1715552,2017-10-10 18:11:50 UTC,"At the time VMWare Player 14 was unavailable for Linux at least. For the record, I just tested VMWare Player 14.0.0 for Linux on Ubuntu 17.10 and it launches fine for me now. Can anybody else confirm?"
1715552,2017-10-10 10:48:21 UTC,VMWare currently ships version 14 of its software. They probably have no interest to fix this issue.
1715552,2017-09-20 10:03:32 UTC,Is there a known way to work around the problem? Maybe something like downgrading libbsd0?
1715552,2017-09-12 07:49:32 UTC,@Joseph Salisbury re: #3
1715552,2017-09-10 16:59:10 UTC,"$ ldd libbsd.so.0
 linux-vdso.so.1 =>  (0x00007ffcdafe6000)
 librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fda779ee000)
 libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fda7760e000)
 libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fda773ef000)
 /lib64/ld-linux-x86-64.so.2 (0x00007fda77e0b000)"
1715552,2017-09-10 15:24:17 UTC,same error here
1715552,2017-09-08 17:39:29 UTC,I agree with Seth:
1715552,2017-09-08 12:18:08 UTC,vmware-modconfig is segfaulting.
1715552,2017-09-07 18:47:47 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1715552,2017-09-07 06:00:07 UTC,This change was made by a bot.
1715552,2017-10-25 11:43:11 UTC,I´ve found a workaround on superuser.com (https://superuser.com/questions/1261885/vmware-workstation-14-not-enough-physical-memory-available-to-start-this-vm-w)
1715552,2020-02-13 07:16:11 UTC,"I don't have anything useful to contribute to this bug, but I still wanted to thank iLugo for comment #26
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/comments/26"
1715552,2017-10-10 19:29:39 UTC,I installed VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle
1715569,2018-05-02 12:02:37 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1715569,2018-02-27 16:27:07 UTC,"Reviewed:  https://review.openstack.org/541904
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6b753f0b5ea734432d2f45fb11884ea1b110ed77
Submitter: Zuul
Branch:    stable/ocata"
1715569,2018-02-15 23:53:16 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1715569,2018-02-08 18:16:46 UTC,"Reviewed:  https://review.openstack.org/541642
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d91e881890933363550ffb9e114c6df4c32a4090
Submitter: Zuul
Branch:    stable/pike"
1715569,2018-02-07 09:56:31 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/541642"
1715569,2018-01-26 00:43:52 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1715569,2017-12-15 02:33:19 UTC,"Reviewed:  https://review.openstack.org/518022
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b196857f04e41dde294eaacc2c1a991807ecc829
Submitter: Zuul
Branch:    master"
1715569,2017-11-21 22:02:11 UTC,Thanks Mike for providing detail of the change in the XML after the update function.
1715569,2017-11-07 15:19:13 UTC,Writing out the xml before and after the update the update function changes the address.
1715569,2017-11-07 15:14:29 UTC,I had attributed the change to RHEL 7 derived distros moving from libvirt 2.x to 3.x.  My problems coincided with the upgrade from CentOS 7.3 to 7.4. This may not be the case as the original report was with Ubuntu 16.04.
1715569,2017-11-07 14:35:52 UTC,"Doing some investigation into this bug, I've found that the code that creates the XML snippet for disk devices hasn't changed in 2+ years."
1715569,2017-11-06 16:14:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518022"
1715569,2017-10-05 23:24:10 UTC,I am also having this problem with ocata
1715569,2017-09-07 07:33:39 UTC,This is the corresponding libvirt configuration file of the vm.
1715569,2017-12-01 14:29:17 UTC,"Good sleuthing, Melanie, I concur with your conclusion."
1715570,2019-11-15 07:19:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/694462"
1715570,2019-11-15 07:19:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/694463"
1715570,2018-08-31 14:32:25 UTC,Something like this:
1715570,2018-10-23 08:15:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612626"
1715570,2018-08-31 14:05:37 UTC,"See related bug 1469179 which was fixed in Rocky. As of Rocky, we don't schedule based on DISK_GB or report DISK_GB usage for volume-backed servers, so we likely shouldn't report local_gb usage in the simple tenant usage API anymore either."
1715570,2017-09-08 01:11:19 UTC,Set the status 'In-progress' because this report has an assignee.
1715570,2018-08-31 14:28:41 UTC,"One issue with fixing this in the simple tenant usage API is we pull potentially a lot of instances out of the database and it would be inefficient to call nova.compute.utils.is_volume_backed on each one. We could stash an is_bfv flag in the instance_system_metadata table but that's also not very efficient, and not something we join on today in that API (since joining on that table is also inefficient)."
1715570,2017-09-12 13:12:39 UTC,"Hi all,"
1715573,2017-09-13 07:49:50 UTC,This is maybe a duplicate of https://bugs.launchpad.net/qemu/+bug/1714331 ... could you please try a newer version of the OVMF firmware (if you're using it)?
1715573,2017-10-16 20:37:48 UTC,It works with a newer OVMF version!
1715577,2020-06-29 04:17:37 UTC,[Expired for linux-aws (Ubuntu) because there has been no activity for 60 days.]
1715577,2018-01-09 15:31:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715577,2019-03-25 11:17:02 UTC,"switched for tests to generic kernel (currently without other problems), but hope it will be fixed soon for aws kernel"
1715577,2020-04-30 02:00:23 UTC,"Hello Piotr and anyone else who is affected by this bug,"
1715586,2018-07-16 21:33:19 UTC,"Note that a security update overrode the version in -proposed, so this never got in -updates. Is it still needed?"
1715586,2017-10-12 06:57:55 UTC,"with AOC monitor, it issued an unexpected acpi event after external monitor be disabled, that caused mode switching."
1715586,2017-09-20 03:55:29 UTC,"Tested the package and found issue still can be reproduced,
""Internal Only"" mode is missing in the switch mode cycle."
1715586,2017-09-14 20:14:24 UTC,"Is this fixed in the development release of Ubuntu, Artful Aardvark?"
1715586,2017-09-15 05:03:28 UTC,"Yes, they're upstream since xserver 1.19.1, we have 1.19.3"
1715586,2017-09-07 12:23:22 UTC,"The attachment ""lp1715586.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1715586,2017-09-15 14:15:53 UTC,"Hello Kai-Heng, or anyone else affected,"
1715602,2019-05-03 15:04:49 UTC,"@Yuan, indeed those would be nicer. You marked it as an oem issue but are you using normal ubiquity in your process? Usually oem machines come pre-installed with the oem-setup mode no?"
1715602,2019-05-06 02:33:00 UTC,"@Sebastien, we use ubunquity with plugins for oem image."
1715602,2019-06-01 03:28:19 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1715602,2018-05-22 06:12:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715602,2018-05-15 07:49:43 UTC,Also affected bionic
1715602,2018-05-22 06:10:34 UTC,"On bug LP: #771719: it's said ""Pressing the power button should not start the shutdown sequence once the installer has started writing files to the disk."""
1715609,2017-10-16 02:19:50 UTC,Seeing this in
1715609,2017-12-11 05:16:22 UTC,"I'm still seeing this in the latest 4.10, 4.11, 4.13 and 4.15 (from mainline)."
1715609,2017-12-11 20:35:34 UTC,"Hi Eric,"
1715609,2017-12-11 20:37:35 UTC,I requested feedback from upstream regarding this bug.  I will update the bug as soon as there is anything new.
1715609,2017-12-11 21:26:22 UTC,Comment #20 is the message sent upstream.
1715609,2017-12-13 17:37:13 UTC,"Just a note that I'm seeing far less skb_warn_bad_offload warnings in Xenial with the last 3 or 4 official 4.10 kernels (4.10.0-42, 4.10.0-40, 4.10.0-38, etc). Sometimes I don't see any warnings for a week or so, sometimes a few pop out. So it looks much better now, I'm just not sure it is fixed completely."
1715609,2017-12-12 14:10:11 UTC,"From: Willem de Bruijn <email address hidden>
Date: Mon, 11 Dec 2017 16:56:56 -0500"
1715609,2018-01-04 09:16:10 UTC,I can confirm the bug is still present in 4.10.0-42. I can experience it with LinPhone working on a VLAN defined on an igb managed card.
1715609,2018-04-06 10:22:33 UTC,"Hi,"
1715609,2018-07-27 07:04:25 UTC,Same output on 4.10.0-42：
1715609,2017-10-14 21:44:54 UTC,This bug also affects the low-latency kernel Linux iglulik 4.10.0-37-lowlatency #41-Ubuntu SMP PREEMPT Fri Oct 6 21:30:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and you can make that four people that are affected.
1715609,2017-12-11 21:28:51 UTC,"From: Joseph Salisbury <email address hidden>
Date: Mon, 11 Dec 2017 15:35:34 -0500"
1715609,2017-09-25 18:01:53 UTC,Can you also give the mainline kernel a test?  A link to it is posted in comment #13.
1715609,2018-04-06 16:25:56 UTC,I built a test kernel with commit b2504a5dbef3305ef41988ad270b0e8ec289331c reverted.
1715609,2017-09-20 16:09:37 UTC,"It might also be good to test the latest mainline kernel.  This will tell us if this commit needs to be reverted, or if there are other commits in mainline that might be needed in combination with b2504a5dbef."
1715609,2017-09-25 17:37:05 UTC,Booted the test kernel and so far no more warnings
1715609,2017-09-07 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1715609,2017-09-07 13:02:46 UTC,"I don't have apport installed on my servers and was hoping the linked bug (1705447) is providing enough context. If not, please let me know and I'll try to provide what I can."
1715609,2017-09-07 21:02:22 UTC,I built a test kernel with the commit to fix bug 1705447 reverted.  The reverted commit is:
1715609,2017-09-08 09:44:21 UTC,"Joseph, thanks for your help! Will need a bit of time to set up a testing environment for this."
1715609,2017-09-11 06:13:12 UTC,"I'm also experiencing this issue with 4.4.0-93-generic in combination with docker,kvm and bonding on host. Not sure if docker or kvm is causing the warnings."
1715609,2017-12-12 20:34:29 UTC,"Can those affected by this bug give the following kernel a try:
http://kernel.ubuntu.com/~jsalisbury/lp1715609/"
1715609,2017-09-14 15:25:05 UTC,Can confirm the same issue with the 4.4.0-93-generic with LXC container running OpenVPN client.
1715609,2017-09-16 17:53:56 UTC,Can you also build an update for the 4.4.0-93 kernel ?
1715609,2017-09-16 17:26:20 UTC,"Joseph, I've been running your test kernel since yesterday. Looking good, no skb_warn_bad_offload warnings so far. With the original kernel I was getting hundreds of these warnings every day."
1715609,2017-09-20 14:19:07 UTC,"@jo Vanvoorden,"
1715609,2017-09-14 16:52:32 UTC,Can those affected by this bug test the kernel posted in comment #3?
1715609,2017-09-12 13:26:40 UTC,"Can confirm the same issue with ""4.10.0-33-generic #37~16.04.1-Ubuntu"". I also have LXD containers, strongswan ipsec VPN server running on that host. Also, there are 6 e1000e/igb network cards installed and being used, if that matters."
1715609,2017-09-15 09:03:41 UTC,"Also reproduced on:
Linux node-dock-b 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Running docker in bridge configuration"
1715624,2017-09-08 02:27:24 UTC,"Reviewed:  https://review.openstack.org/501841
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer-agent/commit/?id=2c4766575866057eb191f2fe8e79e6005312c844
Submitter: Jenkins
Branch:    master"
1715624,2017-09-07 22:49:30 UTC,"Reviewed:  https://review.openstack.org/501882
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=0524e9e4002f666350f932ffc6d744c1131c576a
Submitter: Jenkins
Branch:    master"
1715624,2017-09-07 21:47:37 UTC,"Reviewed:  https://review.openstack.org/501813
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=0161dde79660a248742e41e67f92ed13af561dd7
Submitter: Jenkins
Branch:    master"
1715624,2017-09-07 21:45:47 UTC,"Reviewed:  https://review.openstack.org/501790
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=7fb7ff9063e5b7487694902cf68e078c3780ebcf
Submitter: Jenkins
Branch:    master"
1715624,2017-09-07 21:37:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501882"
1715624,2017-09-07 22:49:10 UTC,"Reviewed:  https://review.openstack.org/501881
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=624c77ca594bf38437e9d8700e10db8f8e53ab4b
Submitter: Jenkins
Branch:    master"
1715624,2017-09-07 19:07:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501841"
1715624,2017-09-07 21:37:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501881"
1715624,2017-09-07 12:37:43 UTC,"another option would be to update all charms to call os_release(... , reset_cache=True) after they upgrade."
1715624,2017-09-07 18:18:02 UTC,"Reviewed:  https://review.openstack.org/501785
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=f778d87ca870ce31840d2c067d5f720af99bda32
Submitter: Jenkins
Branch:    master"
1715624,2017-09-07 21:46:43 UTC,"Reviewed:  https://review.openstack.org/501712
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=fa7655baeb9dc2c0ccdd3ca4d8d1c7575eec7675
Submitter: Jenkins
Branch:    master"
1715624,2017-09-07 18:19:00 UTC,"Reviewed:  https://review.openstack.org/501801
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=efda3b9ddfcb8a249ae30cd4516feac19c5f40c9
Submitter: Jenkins
Branch:    master"
1715624,2017-09-07 18:18:38 UTC,"Reviewed:  https://review.openstack.org/501788
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=7f38a8b648d16148d106e7cb9c3ed9f0ca9bc7fa
Submitter: Jenkins
Branch:    master"
1715630,2017-09-07 12:51:50 UTC,"2017-09-02 12:51:02 INFO juju-log cluster:2: Starting apache
2017-09-02 12:51:02 INFO cluster-relation-changed Site archive_ubuntu_com already enabled
2017-09-02 12:51:02 INFO cluster-relation-changed active
2017-09-02 12:51:02 INFO juju-log cluster:2: Cleaning metadata directory
2017-09-02 12:51:02 INFO juju-log cluster:2: Removing tree /srv/ubuntu-repository-cache/apache/data/ubuntu_2017-09-02_12:49:01_u0
2017-09-02 12:51:03 INFO cluster-relation-changed Traceback (most recent call last):
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/var/lib/juju/agents/unit-ubuntu-repository-cache-0/charm/hooks/cluster-relation-changed"", line 245, in <module>
2017-09-02 12:51:03 INFO cluster-relation-changed     HOOKS.execute(sys.argv)
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/var/lib/juju/agents/unit-ubuntu-repository-cache-0/charm/lib/charmhelpers/core/hookenv.py"", line 715, in execute
2017-09-02 12:51:03 INFO cluster-relation-changed     self._hooks[hook_name]()
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/var/lib/juju/agents/unit-ubuntu-repository-cache-0/charm/hooks/cluster-relation-changed"", line 186, in cluster_relation_changed
2017-09-02 12:51:03 INFO cluster-relation-changed     mirror.peer_update_metadata()
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/var/lib/juju/agents/unit-ubuntu-repository-cache-0/charm/lib/ubuntu_repository_cache/mirror.py"", line 301, in peer_update_metadata
2017-09-02 12:51:03 INFO cluster-relation-changed     _leader_update_metadata()
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/var/lib/juju/agents/unit-ubuntu-repository-cache-0/charm/lib/ubuntu_repository_cache/mirror.py"", line 181, in _leader_update_metadata
2017-09-02 12:51:03 INFO cluster-relation-changed     metadata_sync.clean_metadata_dir(apache_root, LOG)
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/var/lib/juju/agents/unit-ubuntu-repository-cache-0/charm/lib/ubuntu_repository_cache/metadata_sync.py"", line 362, in clean_metadata_dir
2017-09-02 12:51:03 INFO cluster-relation-changed     shutil.rmtree(entry)
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/usr/lib/python3.5/shutil.py"", line 474, in rmtree
2017-09-02 12:51:03 INFO cluster-relation-changed     _rmtree_safe_fd(fd, path, onerror)
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/usr/lib/python3.5/shutil.py"", line 416, in _rmtree_safe_fd
2017-09-02 12:51:03 INFO cluster-relation-changed     onerror(os.rmdir, fullname, sys.exc_info())
2017-09-02 12:51:03 INFO cluster-relation-changed   File ""/usr/lib/python3.5/shutil.py"", line 414, in _rmtree_safe_fd
2017-09-02 12:51:03 INFO cluster-relation-changed     os.rmdir(name, dir_fd=topfd)
2017-09-02 12:51:03 INFO cluster-relation-changed OSError: [Errno 39] Directory not empty: 'dists'
2017-09-02 12:51:03 ERROR juju.worker.uniter.operation runhook.go:107 hook ""cluster-relation-changed"" failed: exit status 1"
1715636,2017-09-07 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1715636,2017-09-07 13:56:44 UTC,"Setting bug status to ""Confirmed"", I do not have a way to reproduce the issue. Relying on the statement from the reporter."
1715636,2017-09-11 16:21:11 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1715636,2017-09-18 10:11:08 UTC,This bug was fixed in the package linux - 4.4.0-96.119
1715640,2018-09-25 12:20:16 UTC,"This seems to be an issue with ""build"" versions of the packages, potentially only older ones ...  The issue is not with the packages website but the extraction of the changelogs, because I can see in http://changelogs.ubuntu.com/changelogs/pool/universe/c/clearsilver/ that there are build versions in there, but not the one for trusty, which is interesting. Potentially this is a trusty only issue.  Would have to dig around/ask someone from the corresponding teams to investigate where something might have went wrong here."
1715660,2017-09-07 14:40:18 UTC,"The """"unregister_netdevice: waiting for lo to become free"" logs are also present in the Openstack CI in many kolla jobs, although these jobs don't have the kernel ""task ... blocked for more than 120 seconds"" message. Kolla may be hitting a different issue, or the same issue but the deadlock resolving before the 120s limit."
1715660,2017-09-07 14:56:15 UTC,"Possibly related:
* https://github.com/moby/moby/issues/5618
* bug 1711407
* https://<email address hidden>/msg179703.html"
1715660,2017-09-14 19:06:50 UTC,"Since we are using vxlan a lot, and in particular with multiple fdb entries for 00:00:00:00:00:00, it seems that this would be a possible cause:"
1715660,2017-09-14 19:45:24 UTC,It's been merged to v4.13 upstream kernel - https://github.com/torvalds/linux/commit/35cf2845563c1aaa01d27bd34d64795c4ae72700#diff-4f541554c5f8f378effc907c8f0c9115 and is not in current 4.4.0 Ubuntu Xenial.
1715660,2017-09-15 17:14:09 UTC,This is the tooling I was mentioning earlier today:
1715660,2017-09-20 11:12:45 UTC,I found out the patch I posted is probably not relevant as the dst_cache is not in current Ubuntu 4.4.0 kernel.
1715663,2018-06-07 07:54:52 UTC,I have tried to reproduce using master(Rocky):
1715663,2018-06-11 11:25:34 UTC,It seems tempest run is already stdout the error when there is Bad entry. Please find below the output from console. Please advice suitable action for this issue?
1715663,2017-10-12 09:30:17 UTC,"As from my last comment, we can see that i already logs the information about misconfiguration of the plugin. So i think it does not appears to be a bug and but marking it as wishlist if someone wants to add the stdout for the same."
1715663,2017-09-13 14:13:20 UTC,"If tempest plugin entrypoint is not properly defined, on doing tempest list-plugins will give you error. For example I have changed something in zaqar tempest plugin entrypoint. Here is the things you can get:
[centos@zaqar-devstack zaqar]$ vim zaqar.egg-info/entry_points.txt
[centos@zaqar-devstack zaqar]$ tempest list-plugins
/usr/lib/python2.7/site-packages/eventlet/convenience.py:6: DeprecationWarning: EVENTLET_NO_GREENDNS is noop, dnspython is bundled and DNS resolution is always green
  from eventlet.green import socket
/opt/stack/cinder/cinder/tests/tempest/plugin.py:19: ImportWarning: Not importing directory '/opt/stack/cinder/cinder/tests/tempest/config': missing __init__.py
  from cinder.tests.tempest import config as project_config
Could not load 'zaqar_tests': No module named tempest_plugin.plugin
No module named tempest_plugin.plugin
[centos@zaqar-devstack zaqar]$
I hope it will solve your problem."
1715663,2017-09-07 15:16:45 UTC,"I've tried it with last tagged version 17.0.0 and I didn't check logs, but my bugreport is about cli behaviour. If entrypoint is invalid, user see nothing, application is just terminates."
1715663,2017-09-07 15:07:45 UTC,We should be logging this already: https://github.com/openstack/tempest/blob/master/tempest/test_discover/plugins.py#L190 did you check the log file?
1715663,2017-10-12 09:30:03 UTC,I would not say this is a bug either. I think it would be fine to add a stdout output as well for this case.
1715665,2020-09-20 09:55:01 UTC,Closing because INVALID: Can't replicate.
1715665,2019-03-11 03:04:28 UTC,"Can reproduce crash but not X freezing with the attached file. Inkscape 0.92.4, openSUSE TW 20190301. I'll attach a backtrace when I get the time."
1715668,2018-02-26 06:44:22 UTC,This looks more like bootstrap failing to provision the machine is destroying the known controllers.yaml file. I'm wondering if they're doing something funny with JUJU_HOME/JUJU_DATA ?
1715668,2017-09-07 20:59:44 UTC,It seems that bootstrap needs a sanity check against the controller name already existing.
1715668,2017-10-23 20:06:37 UTC,Issuing a bootstrap command against an existing controller results in juju producing an error stating that the controller already exists. I cannot reproduce the issue. I've tried the issue with both maas and LXD providers.
1715677,2017-09-08 12:28:26 UTC,Getting the same error on mint 18.1 since about a week or so.
1715677,2018-01-22 13:50:52 UTC,Try
1715677,2017-10-31 08:55:50 UTC,"@Diego that worked, thanks!"
1715677,2017-10-30 22:57:14 UTC,@VirtualThai: Try to extend the startup timeout in preferences!
1715677,2017-10-30 22:55:18 UTC,@Lolwhites: Did you try to crop the image with the Crop Tool??
1715677,2017-10-30 22:36:23 UTC,I tried Diego's workaround but it places the image in the top left hand corner and leaves white space along the bottom and right edges. No amount of playing with the seeetings will make it fill the screen like before. This worked fine in 17.04 but not 17.10.
1715677,2017-09-22 12:15:03 UTC,"Hi guys!
Live Earth does not work after application re-install...
Live Website need to be re-activated to work... each time system boots up!!!
WHY Live Earth give this problem? It was so lovely!!!!
Please solve this!!!!"
1715677,2017-09-19 18:49:09 UTC,@ Diego
1715677,2017-09-15 16:25:48 UTC,"Same ""strange"" connetion error here...
Live Website with 1600.jpg picture works fine in my Elementary OS!
Thanks!"
1715677,2017-09-14 21:14:48 UTC,"site also quit working for me recently, same connection error, no real reason, must be server side"
1715677,2017-09-14 21:14:22 UTC,thanks for the link! i had figured out the site but couldnt find a link for just the image itself!!!
1715677,2017-09-10 00:42:27 UTC,Update:
1715677,2017-09-20 14:34:32 UTC,I came here looking for help but instead I became a helper. I'm glad that it worked for @akbagchi and for @Mauro Inglese.
1715677,2017-09-20 06:37:27 UTC,@ Diego   Thank you very much for your suggestion to make the Wallch working from a different way than it is prescribed inside the apps.
1715686,2017-09-09 07:48:44 UTC,"So, in order for me to work, i needed to add lvm2 on the dracut image, using dracut-regenerate element:
http://git.openstack.org/cgit/openstack/diskimage-builder/tree/diskimage_builder/elements/dracut-regenerate"
1715686,2017-09-09 10:27:36 UTC,It looks that there are a couple of issues here:
1715686,2017-09-11 12:33:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502454"
1715686,2017-09-12 09:31:08 UTC,"Reviewed:  https://review.openstack.org/502452
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=b84997036da20c45318fae65309468e55f619eab
Submitter: Jenkins
Branch:    master"
1715686,2017-09-13 06:26:38 UTC,Adding a comment is a first small step here - hopefully now at least some users are able to build an image with LVM.
1715686,2017-09-15 13:52:39 UTC,"Reviewed:  https://review.openstack.org/502454
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=da5c926fe92170446f4f0033f6494fbe2871ec82
Submitter: Jenkins
Branch:    master"
1715686,2017-09-16 15:08:20 UTC,"I filed a patch for Debian / Ubuntu which addresses the last section in my latest comment:
https://review.openstack.org/#/c/504588/"
1715692,2017-09-07 16:36:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501803"
1715692,2018-10-25 02:57:11 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/501803"
1715708,2017-09-15 05:39:49 UTC,"I've been deploying xenial on vsphere all this week and last week without issue, so I don't think that's all there is to it. Can you please try again with develop? I landed some significant changes today that affect VM creation."
1715708,2017-11-13 10:11:23 UTC,I can confirm that this has been fixed in the edge channel (2.3-beta4+develop-e488d78 (2878))
1715708,2017-11-13 11:01:27 UTC,"Thanks, Merlijn!"
1715711,2018-05-14 11:03:24 UTC,This change was made by a bot.
1715715,2017-12-03 21:24:14 UTC,I've just tested MacOS 9.2.1 as part of my QEMU pre-release testing and it works fine for me with latest QEMU git and the following command line:
1715715,2017-12-03 23:37:10 UTC,I just tried the latest git and it actually boots fine with your command... so I guess whatever issue I was having (the null dereference in the timer code I pasted above) must have been fixed... however I've noticed another issue with a different command that causes the bootup to hang:
1715715,2020-09-05 09:47:56 UTC,Looking through old bug tickets ... can you still reproduce the segfault with the latest version of QEMU?
1715715,2020-11-05 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1715740,2017-09-07 20:41:37 UTC,"StacktraceTop:
 totem_object_play (totem=totem@entry=0xb9c8124190) at ../src/totem-object.c:1478
 totem_object_set_mrl_and_play (subtitle=<optimized out>, mrl=0xb9c8f82ea0 ""trash:///The%20Boss%20Baby%20(2017)%20%5BYTS.AG%5D/The.Boss.Baby.2017.720p.BluRay.x264-%5BYTS.AG%5D.mp4"", totem=0xb9c8124190) at ../src/totem-object.c:1517
 playlist_changed_cb (playlist=<optimized out>, totem=0xb9c8124190) at ../src/totem-object.c:2976
 g_closure_invoke (closure=0xb9c8da0230, return_value=0x0, n_param_values=1, param_values=0x7ffe691f0c50, invocation_hint=0x7ffe691f0bd0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0xb9c891cc20, detail=detail@entry=0, instance=instance@entry=0xb9c89392d0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffe691f0c50) at ../../../../gobject/gsignal.c:3635"
1715744,2017-09-08 03:40:26 UTC,"Superficially the initial key parts must be shared and not result in duplicate stat entries (with differing values), right? Since SHOW INDEX must return the index name, the same shared row should be returned several times?"
1715744,2017-09-12 23:02:32 UTC,"Yes, this is correct. For f1 part of key(f2, f1), key(f3, f1) cardinality is same."
1715744,2018-01-25 09:00:49 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1822
1715749,2018-02-24 23:16:35 UTC,"I'm currently working without an external display and without a docking station/port replicator, and the screen just went black for a couple of seconds. The system had been running for 1–2 hours at the time."
1715749,2018-02-25 22:17:37 UTC,"Michael von Glasow, if you disable the laptop turning the screen off or dimming after inactivity via the GUI, does this still happen?"
1715749,2018-02-25 22:36:08 UTC,"I just set the screen timeout to Never; dimming was already disabled. I did this only for the AC profile, not the battery profile, as I’m on AC power most of the time. I’ll report back if the screen goes black again (or if it doesn’t happen for a while)."
1715749,2018-02-25 23:42:38 UTC,"And the screen just went black again. I haven’t rebooted since I changed the settings; I will report if I still experience issues after a reboot, just to be sure."
1715749,2018-04-18 10:19:13 UTC,18.04 LTS is just around the corner and I will be upgrading soon. Is there any more information you’d like me to gather while still on 16.04? Please let me know; otherwise I will post any news on how this behavior also affects 18.04 once I’ve upgraded and used it for a while.
1715749,2018-04-18 14:40:03 UTC,"After today’s updates, I am seeing another strange issue: whenever all displays go out due to inactivity and I touch the keyboard or mouse again, the internal display starts to flicker. It looks as if the entire image is shifted by some 25% of its width to one side, then to the other (with the part that would be outside the display area wrapping around to the other end of the display). It flickers back and forth between the two offsets somewhere near the refresh rate. So far I’ve always been able to recover by pressing Ctrl+Alt+F1 to go to a tty, then Ctrl+Alt+F7 to return to the MATE desktop. Not sure if it’s related."
1715749,2018-04-18 14:40:45 UTC,"Forgot to add, the laptop’s currently docked with an external display on DisplayPort."
1715749,2018-04-18 21:05:19 UTC,"Michael von Glasow, to clarify, what update are you referring to? Package(s) update (which specifically) or updating the OS to 18.04?"
1715749,2018-04-18 22:26:09 UTC,"I am referring to package updates, still on 16.04, whatever was made available on the repos in the last ~24 hours before comment #33. (Is there an install log which will tell me what was updated when?)"
1715749,2018-04-30 12:43:07 UTC,"I noticed another issue recently: when the device displays woke up after a period of inactivity, the picture of the external (!) display was stretched vertically by a factor of 2, with the bottom half missing. I took a screenshot, but that looked OK and didn’t reflect what I actually saw."
1715749,2018-08-25 19:03:18 UTC,"And the issue described in comment#37 is also back. This time, however, after doing Ctrl+Alt+F1, everything was black (except for the cursor blinking on the internal display), and I was unable to switch back to the GUI with Ctrl+Alt+F7; I ended up having to cold boot the system using the power button."
1715749,2018-02-13 17:29:14 UTC,"Re 1: the issue started to happen after I moved the hard disk to the 840 G1 (from a 6930p), which was around August/September. Updates usually get installed within a day (unless I have only limited Internet access, which was not the case when I switched laptops), thus the system should have been fairly up-to-date at the time."
1715749,2018-11-18 21:47:50 UTC,"For the issue in #37, I was able to restore the external display by undocking and re-docking the laptop."
1715749,2019-09-12 10:59:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715749,2019-09-12 11:04:09 UTC,"I have exactly the same problem described in the title since 2018-11-27, when I bought this laptop."
1715749,2019-10-17 09:19:11 UTC,I have exactly the same problem too with the same computer. I also have ubuntu on a dual boot with Windows.
1715749,2019-11-17 13:20:45 UTC,"Black internal screen on my G1 820 too. May be its a problem with function ""lower screen intensity when inactive"" (energy), i have disabled it now."
1715749,2019-11-17 15:17:22 UTC,@Maik Schulze did that change anything? are you still getting the error?
1715749,2019-11-17 15:20:31 UTC,"Just had a look at my own settings: I have ""Dim display when idle"" unchecked in the AC power tab, checked in the Battery tab. I am still getting a dark screen every now and then, even though I mostly work on AC power."
1715749,2020-03-24 07:06:09 UTC,I'm having the same issue on Mint 19.3.
1715749,2018-05-09 16:36:19 UTC,I upgraded to 18.04 last week. So far none of the screen issues (black screen or image corruption) has reappeared; I will post an update if anything comes up.
1715749,2018-02-13 01:41:17 UTC,Michael von Glasow:
1715749,2018-07-23 21:28:06 UTC,"The black screen issue reappeared on 18.04 sometime last week, after two completely trouble-free months, and it is quite frequent again. I haven’t done and in-depth diagnosis or troubleshooting so far. The flicker issue hasn’t appeared since I upgraded."
1715749,2018-02-12 21:32:11 UTC,"Update done. I’ll keep an eye on this and report back if I encounter the issue again (or do not encounter it for a longer time—being a sporadic bug, it’s difficult to tell if it’s gone away for good)."
1715749,2018-02-09 22:49:58 UTC,"Michael von Glasow, thank you for reporting this and helping make Ubuntu better."
1715749,2018-02-10 16:25:37 UTC,apport information
1715749,2018-02-10 16:25:41 UTC,apport information
1715749,2018-02-10 16:25:43 UTC,apport information
1715749,2018-02-10 16:25:45 UTC,apport information
1715749,2018-02-10 16:25:46 UTC,apport information
1715749,2018-02-10 16:25:47 UTC,apport information
1715749,2018-02-10 16:25:49 UTC,apport information
1715749,2018-02-10 16:25:50 UTC,apport information
1715749,2017-09-10 14:56:55 UTC,"Update on behavior: the last few times the internal display went black, I did not touch the keyboard and mouse at all, and the display came back after a few seconds. (Tested with the laptop in the port replicator and an external display connected via the DP port.)"
1715749,2018-02-13 00:35:59 UTC,"Well, that didn’t take long: screen just went black again for somewhere around a second. Let me know if you need further input from me."
1715749,2018-02-10 16:25:51 UTC,apport information
1715749,2018-02-10 16:25:53 UTC,apport information
1715749,2018-02-10 16:25:54 UTC,apport information
1715749,2018-02-10 16:25:55 UTC,apport information
1715749,2018-02-10 16:25:56 UTC,apport information
1715749,2018-02-10 16:25:58 UTC,apport information
1715749,2018-02-10 16:25:59 UTC,apport information
1715749,2018-02-10 16:26:00 UTC,apport information
1715749,2018-02-10 16:26:01 UTC,apport information
1715749,2018-02-10 16:26:03 UTC,apport information
1715749,2018-02-11 04:44:25 UTC,"Michael von Glasow, could you please update your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the results?"
1715749,2018-02-10 16:25:52 UTC,apport information
1715755,2017-09-15 21:45:59 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-September/087074.html
1715755,2017-09-20 00:26:27 UTC,This bug was fixed in the package linux-azure - 4.11.0-1011.11
1715755,2017-09-09 21:28:29 UTC,The revert alone doesn't solve the problem. We will run new tests enabling CONFIG_ND_BLK and CONFIG_ACPI_NFIT.
1715755,2017-09-15 21:39:28 UTC,"The revert is not necessary anymore since the issue was fixed upstream by the commit id fd96b8da68d3 (""ext4: fix fault handling when mounted with -o dax,ro"")."
1715758,2017-09-07 23:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1715758,2017-09-08 00:07:41 UTC,"This is a feature request, thus doesn't require logs"
1715758,2017-09-21 16:17:10 UTC,"We have BFQ configured as a module, so you should be able to load it and use it already. We could consider making it built-in though."
1715758,2018-07-24 09:35:12 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1715764,2020-07-27 15:39:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715771,2019-08-05 03:49:56 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1715774,2017-09-08 02:06:41 UTC,"I think, this is a duplicate of #1711874. Let's shift the discussion to the other report."
1715774,2017-09-08 17:20:27 UTC,"Looks like it is not a duplicate in the end, sorry for the confusion!"
1715785,2019-10-02 16:53:36 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/501928"
1715785,2017-09-08 02:52:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501928"
1715785,2017-09-08 02:53:36 UTC,"https://review.openstack.org/#/c/501928/ Proposing something like this, will this help?"
1715801,2018-01-24 22:26:15 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1443
1715807,2017-09-09 17:15:20 UTC,"Something to keep in mind is that there are two types of images that Word recognizes: ""Shapes"" and ""InlineShapes""
I have written a macro (below) to do this, but it would be much more convenient to add the option under ""DOCX output"" in Caliber."
1715807,2019-04-18 05:15:24 UTC,"calibre generally tries to preserve the formatting of input documents as
much as possible. The imaging models of EPUB and DOCX are very different
so a one-to-one conversion is not always possible. That said if you
provide some example documents, I can take a look at improving the
translation heuristics for image sizes."
1715807,2019-06-18 04:17:17 UTC,[Expired for calibre because there has been no activity for 60 days.]
1715811,2019-08-05 03:50:14 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1715811,2017-09-18 12:29:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1715811,2018-01-19 23:04:35 UTC,I had the same issue on a Dell XPS 13 with Intel HD Graphics 4000 after upgrading from 16.04 to 17.10.
1715811,2017-11-14 09:08:14 UTC,I ran into this upgrading from 17.04 to 17.10 on an X1 Carbon 3rd Gen (Intel HD Graphics 5500). Inspired by reading Mentis's comment. This fixed it for me:
1715811,2017-09-18 12:32:41 UTC,"Also having an ""Unrecoverable failure in required component org.gnome.Shell.desktop"" in the same log."
1715811,2017-09-18 12:31:55 UTC,I cannot log to ubuntu wayland session on 17.10. Xorg works fine. The logs show the same error messages with org.gnome.ScreenSaver. I don't know if it is related. I am still researching the cause.
1715811,2017-09-10 06:50:06 UTC,Was able to make GDM to work by reinstalling all installed packages using this guide: https://ubuntuforums.org/showthread.php?t=1407060
1715811,2018-02-18 23:14:45 UTC,same error for me while using a X1 lenovo - Intel® HD Graphics 520 (Skylake GT2)
1715811,2017-09-08 19:32:06 UTC,I see this error in syslog:
1715811,2017-09-08 19:25:59 UTC,Thank you for your help Daniel
1715811,2017-09-08 19:42:42 UTC,Another repeated error I spotted in syslog:
1715811,2017-09-08 07:47:26 UTC,Just trying to figure out what the problem is. It may not be GDM at all.
1715811,2017-09-08 07:33:43 UTC,"Sure.
How about syslog? Will it help?
 $ lspci -k
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07)
 Subsystem: Dell Skylake Host Bridge/DRAM Registers
 Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
 Subsystem: Dell HD Graphics 530
 Kernel driver in use: i915
 Kernel modules: i915
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 07)
 Subsystem: Dell Skylake Processor Thermal Subsystem
 Kernel driver in use: proc_thermal
 Kernel modules: processor_thermal_device
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
 Subsystem: Dell Sunrise Point-H USB 3.0 xHCI Controller
 Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
 Subsystem: Dell Sunrise Point-H Thermal subsystem
 Kernel driver in use: intel_pch_thermal
 Kernel modules: intel_pch_thermal
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
 Subsystem: Dell Sunrise Point-H CSME HECI
 Kernel driver in use: mei_me
 Kernel modules: mei_me
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 31)
 Subsystem: Dell SATA Controller [RAID mode]
 Kernel driver in use: ahci
 Kernel modules: ahci
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2 (rev f1)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
 Subsystem: Dell Sunrise Point-H LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
 Subsystem: Dell Sunrise Point-H PMC
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
 Subsystem: Dell Sunrise Point-H HD Audio
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
 Subsystem: Dell Sunrise Point-H SMBus
 Kernel modules: i2c_i801
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
 Subsystem: Dell Ethernet Connection (2) I219-LM
 Kernel driver in use: e1000e
 Kernel modules: e1000e
01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
 Subsystem: Intel Corporation Wireless 8260
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
 Subsystem: Dell RTS525A PCI Express Card Reader
 Kernel driver in use: rtsx_pci
 Kernel modules: rtsx_pci"
1715811,2017-09-08 07:25:43 UTC,"In that case maybe there is no ""crash"", but some other problem."
1715811,2017-09-08 07:06:05 UTC,No crash files there. Any other log I can provide?
1715811,2017-09-08 06:48:50 UTC,Do you have any .crash files in /var/crash/ ?
1715815,2017-09-08 06:59:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/501977"
1715815,2018-10-25 02:57:18 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/501977"
1715852,2017-10-28 04:33:37 UTC,This bug was fixed in the package pdf-presenter-console - 4.0.8-2
1715852,2017-10-28 04:35:25 UTC,"Generally, packages are only updated in stable Ubuntu releases to fix high-priority bugs. Read this page for more information about how updates work."
1715854,2017-09-19 13:49:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1715858,2017-09-08 17:47:23 UTC,">>>> Haven't seen this before, not sure it can be reproduced also, hence filing a low priority bug for tracking.
"
1715858,2017-09-29 18:01:20 UTC,Can you please replicate the problem and provide access to setup?
1715866,2017-10-12 15:13:19 UTC,"not sure where to add the tag ""kernel-fixed-upstream"" as with kernel 4.13.x
this issue disappeared. Only bluetooth module (also come within Ralink
RT3290 module) doesn't work and needs custom compile/installation to be
found and activated by the system."
1715866,2017-10-12 15:09:42 UTC,kernel-fixed-upstream
1715866,2017-09-08 18:03:39 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1715866,2017-09-08 13:49:15 UTC,apport information
1715866,2021-02-01 08:10:36 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018."
1715866,2017-09-08 13:49:03 UTC,apport information
1715866,2017-09-08 13:48:59 UTC,apport information
1715866,2017-09-08 13:48:57 UTC,apport information
1715866,2017-09-08 13:48:55 UTC,apport information
1715866,2017-09-08 13:48:53 UTC,apport information
1715866,2017-09-08 13:48:43 UTC,apport information
1715866,2017-09-08 13:48:50 UTC,apport information
1715866,2017-09-08 13:48:48 UTC,apport information
1715866,2017-09-08 13:48:47 UTC,apport information
1715866,2017-09-08 13:48:45 UTC,apport information
1715866,2017-09-08 13:48:42 UTC,apport information
1715866,2017-09-08 13:48:38 UTC,apport information
1715866,2017-09-08 13:48:37 UTC,apport information
1715866,2017-09-08 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1715866,2017-09-08 13:48:51 UTC,apport information
1715876,2019-09-19 12:04:34 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1715883,2017-09-08 13:53:05 UTC,"Nautilus migrated to gitlab.gnome.org.
The patch for this bug is at https://gitlab.gnome.org/GNOME/nautilus/merge_requests/2"
1715883,2017-09-08 13:54:09 UTC,Thunar suffers from the same bug.
1715883,2018-07-20 16:21:24 UTC,"Hello Colin,
Thank you for submitting this bug and reporting a problem with drag and drop from network shares IN Ubuntu. You made this bug report some time ago and Ubuntu has been updated since then."
1715893,2017-09-27 14:14:07 UTC,What is the value of vendordata_dynamic_connect_timeout in nova.conf?
1715893,2017-09-27 19:26:06 UTC,"Hello Rob,"
1715915,2018-02-22 04:57:13 UTC,"Reviewed:  https://review.openstack.org/465636
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=52965d8974ca62bfaa4201d3057a0b5742e5c818
Submitter: Zuul
Branch:    master"
1715915,2018-02-20 11:02:34 UTC,"Reviewed:  https://review.openstack.org/545950
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9eeda1db928bab477cd7fb8435fa217ad1e49d1c
Submitter: Zuul
Branch:    master"
1715915,2018-02-20 11:01:53 UTC,"Reviewed:  https://review.openstack.org/545949
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=3b13d77a263d787fce7d6e627ceda9e38fde2236
Submitter: Zuul
Branch:    master"
1715915,2018-02-19 18:27:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545949"
1715915,2018-01-04 15:48:06 UTC,"Goutham,"
1715915,2018-02-19 18:27:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/545950"
1715924,2019-03-05 14:56:45 UTC,"I suspect the reported problem is not linked to the number of file descriptor available to the DB, nor to the configured LimitNOFILE for pacemaker."
1715924,2019-03-05 15:00:53 UTC,Setting as incomplete due to both inactivity and the need for more info. Please update if you think this is relevant still.
1715931,2020-03-24 15:06:20 UTC,Closed via https://launchpad.net/ubuntu/+source/exiv2/0.27.2-8ubuntu2
1715931,2020-02-07 07:51:54 UTC,I got tricked because the very same patch was applied on the function 10 lines above...
1715931,2020-02-07 07:51:22 UTC,reuploaded thanks Rico!
1715931,2020-02-05 08:48:04 UTC,Note that 0.27.2-8ubutnu1 dropped the previously applied patch for CVE-2019-17402 which is still required!
1715931,2020-01-28 09:02:17 UTC,exiv2 (0.27.2-7) just landed in debian unstable
1715931,2019-12-22 19:04:58 UTC,"it doesn't look like it's going to be actioned at all,"
1715931,2019-12-21 23:03:43 UTC,Is this going to be actioned for 20.04?
1715931,2018-09-11 22:49:32 UTC,Thanks Jeremy. It's a bit challenging for anyone doing photography work with recent hardware. Key apps like darktable and digicam rely on this library and ubuntu/debian are way behind. Last year's fedora had 0.26.
1715931,2018-09-11 21:26:31 UTC,This is actually blocked because 0.26 has *new* security issues.
1715931,2018-08-22 13:09:57 UTC,"The update is still in Debian/experimental and require a transition
https://release.debian.org/transitions/html/auto-exiv2.html
Unsure if it's worth trying to do in Ubuntu before Debian though"
1715931,2018-08-10 07:41:58 UTC,Exiv2 0.25 as used by ubuntu 18.04 and the upcoming 18.10 is really obsolete and this brings all kinds of annoying problems with darktable - inability to recognize lenses and so on.
1715931,2018-03-24 21:30:52 UTC,"At this point, this would require a Feature Freeze Exception to be considered for Ubuntu 18.04 LTS."
1715931,2018-02-16 21:55:24 UTC,Seems not
1715931,2018-01-21 02:50:38 UTC,"Bump, was anything done with this?"
1715931,2018-09-11 21:30:11 UTC,Several of those issues are fixed at https://github.com/Exiv2/exiv2 but it's going to be a bit of work to handle all of that in Debian or Ubuntu.
1715995,2017-12-01 04:34:13 UTC,"Reviewed:  https://review.openstack.org/509438
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ece825bd2b8695f8581c2da9f51795fb0dbf4da5
Submitter: Zuul
Branch:    stable/pike"
1715995,2017-12-18 12:51:42 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1715995,2017-10-24 12:42:56 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1715995,2017-09-13 17:54:57 UTC,"Reviewed:  https://review.openstack.org/502112
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a9f11002cc1b668b612a4ac7ce3d9662efbd2fd5
Submitter: Jenkins
Branch:    master"
1715995,2017-09-08 16:11:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502112"
1715995,2017-10-04 13:25:11 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/509438"
1716007,2017-09-09 00:59:29 UTC,"After the bug fix https://bugs.launchpad.net/juniperopenstack/+bug/1699097, rules have to be configured against singular object type for individual object CRUD operations, and plural object if multiget is involved."
1716007,2017-09-09 01:01:39 UTC,"Hi Bogdan Ratiu,"
1716007,2017-09-11 19:09:37 UTC,"Hi Suresh,"
1716008,2019-02-19 13:49:17 UTC,should we keep this open?
1716008,2019-02-19 22:20:46 UTC,"It was originally opened to be a target for elastic-recheck. I'm not sure if the query still exists or even works if it does, so it can probably be closed unless someone else is interested in the e-r query."
1716013,2017-09-28 15:24:50 UTC,Can I make this bug public?
1716013,2017-10-20 13:00:34 UTC,I didn't make it private intentionally. The software seems to make it private by default when Security is checked. I see no reason why this shouldn't be public.
1716013,2017-10-23 21:07:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1716019,2017-10-20 15:19:39 UTC,Reproduce the bug:
1716020,2017-09-09 07:26:14 UTC,Fixed in revision #189
1716020,2017-09-21 19:21:41 UTC,"Thank you for your marvelous project !
Quarte is one of my most used application.
best regards,
Eton"
1716026,2017-09-08 17:55:52 UTC,"StacktraceTop:
 g_path_is_absolute (file_name=file_name@entry=0x4 <error: Cannot access memory at address 0x4>) at ../../../../glib/gfileutils.c:2119
 canonicalize_filename (filename=filename@entry=0x4 <error: Cannot access memory at address 0x4>) at ../../../../gio/glocalfile.c:209
 _g_local_file_new (filename=0x4 <error: Cannot access memory at address 0x4>) at ../../../../gio/glocalfile.c:307
 gtk_file_chooser_set_current_folder (chooser=0xcdc00cabf0, filename=filename@entry=0x4 <error: Cannot access memory at address 0x4>) at ././gtk/gtkfilechooser.c:908
 handle_open (object=<optimized out>, invocation=0x7f64e80119c0, arg_handle=<optimized out>, arg_app_id=<optimized out>, arg_parent_window=<optimized out>, arg_title=<optimized out>, arg_options=0x7f64e8019190) at src/filechooser.c:458"
1716026,2017-09-09 16:33:00 UTC,https://github.com/flatpak/xdg-desktop-portal-gtk/issues/93
1716029,2017-09-27 09:19:18 UTC,The effect of this is minimal and its intended use is to by-pass BZ k-points where there are no propagating states. I.e. so long as the edge of the sampled BZ has no weights the results are correct.
1716033,2017-09-15 20:39:43 UTC,Validated.
1716033,2017-09-11 13:14:26 UTC,"Jeff,"
1716033,2017-09-08 19:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1716034,2017-09-10 20:58:01 UTC,This also affected my machines. Thanks to the forum reference I was able to piece together this:
1716034,2017-09-10 21:02:04 UTC,Looking at the changelog I see that the new conf.d file is a debian addition. The relevant changelog says:
1716034,2017-09-11 09:45:58 UTC,Is that any better with the fix in bug 1690992? That sounds very much like a duplicate?
1716034,2017-09-11 09:47:15 UTC,"I'm sorry, I mean bug 1676547."
1716034,2017-09-11 13:11:18 UTC,Chatting with Martin it seems that an upload to xenial-updates has broken the logic since the test in network-manager's postinst script is now out out date.
1716034,2017-09-11 14:05:14 UTC,"FTR, I don't want to blame the NetworkManager 1.2.6 SRU to xenial - that new upstream version now evades the version test in the postinst, but of course it's still that version test which is at fault. I don't see how we can use a simple version test to determine the situation that we want (one-time test after upgrading from 16.04 LTS), I suppose it needs to move to ""$2 is not empty"" plus creating a migration stamp file somewhere."
1716041,2017-09-10 02:41:23 UTC,"I'm pretty sure --replay overrides --lines. 'lines' says to go back N and
start replaying, --replay says to start from the beginning and display
everything."
1716041,2017-09-18 17:48:19 UTC,"> juju debug-log --no-tail --lines=1
"
1716043,2017-09-14 19:34:15 UTC,"Related patch for OpenstackSDK: https://review.openstack.org/#/c/504111/
Related patch for Shade: https://review.openstack.org/#/c/504155/"
1716043,2017-09-25 16:36:51 UTC,Abandoned patch for neutron neutronclient https://review.openstack.org/#/c/449209/
1716043,2017-10-26 13:12:21 UTC,Related patch for Openstack Client: https://review.openstack.org/#/c/515401/
1716043,2018-10-19 13:14:54 UTC,This patch hasn't been merged in the OpenStack Client yet.
1716049,2017-09-08 21:08:30 UTC,"Odd.  At least in 16.04, package pam-krb5-migrate no longer exists, according to apt-cache search.
But I'll gladly specify it!"
1716049,2017-09-08 20:19:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1716050,2019-09-22 02:47:43 UTC,"My OSA deployment has a proper DNS working but, I can't see a way to tweak /etc/openstack_deploy/* files to set the FQDN (osa-1.cloud.mydomain.com) for all ""openstack endpoint""s."
1716050,2018-12-06 14:11:24 UTC,My current workaround : put the external FQDN in /etc/hosts pointing to the internal IP where haproxy should bind.
1716050,2019-09-22 02:44:21 UTC,I'm a bit surprised that this isn't an option!
1716056,2017-11-07 19:35:29 UTC,Issue was resolved in latest Dropbox version 38.4.27.
1716056,2018-10-13 10:22:05 UTC,"I still have this problem after upgrading to ubuntu 18.04, dropbox 59.4.3"
1716056,2018-11-05 23:12:03 UTC,How can you say that it was resolved? I still have this bug.
1716056,2019-04-11 08:53:31 UTC,This bug was fixed in the package gnome-shell-extension-appindicator - 28-1
1716057,2017-11-26 20:34:34 UTC,"On a Intel Sandy Bridge System, I had a bug causing freezes after removing HDMI, solved by removing this package.
On a Intel Ivy Bridge System, I had a bug causing the progress bar to show up, every 5 minutes on video play (without user input, touchpad off, no mouse, no keyboard input), solved by removing this package.
On a Intel Kaby Lake System, I didn't noticed bugs, but to hell with this package."
1716057,2017-12-01 00:03:58 UTC,The package should be xserver-xorg-video-intel-hwe-16.04 for HWE kernels anyway
1716063,2017-09-08 22:55:29 UTC,"xml network file has domain name set, and so does the generated dnsmasq config."
1716063,2017-09-11 06:29:26 UTC,"Hi Xnox,
so since you said the generated dnsmasq config has the domain name set.
Can we reproduce this without libvirt using a manual config of dnsmasq to start ruling out components?"
1716063,2017-09-11 09:41:57 UTC,"I set up three Artful VMs:
1. one with a dnsmasq in it.
2. the other one to correctly remote request from it
2. the other one to correctly remote request from it (but via dhcpcd instead of isc-dhcp)
3. Added an extra separate virtual network without dhcp from the host where all those guests can reach each other"
1716064,2019-12-02 14:49:01 UTC,"I don't understand why this abandoned project still is listed in software managers!
I'm on Linux Mint 19 Tara 64-bit and all the edit and file menu's are greyed out.
Help page is missing and http://www.lottanzb.org/ is down."
1716071,2018-04-13 10:59:15 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/507688
Reason: Current versions works well without this change."
1716079,2019-10-29 13:52:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716079,2017-09-09 02:41:02 UTC,This also might be of interest:
1716079,2017-09-09 02:17:58 UTC,"These files are then present:
test case/
test case/debootstrap
test case/debootstrap/debootstrap.log
test case/var
test case/var/lib
test case/var/lib/apt
test case/var/lib/apt/lists
test case/var/lib/apt/lists/partial
test case/var/lib/apt/lists/debootstrap.invalid_dists_artful_InRelease
test case/var/cache
test case/var/cache/apt
test case/var/cache/apt/archives
test case/var/cache/apt/archives/partial"
1716079,2017-09-09 02:17:22 UTC,"sudo debootstrap --arch amd64 artful ""test case"""
1716079,2017-09-09 02:16:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716079,2017-09-09 02:38:36 UTC,"This also affects cdebootstrap, I tried this with directory ""Test 1"" and I set it to use my local archive mirror at 8080:"
1716101,2017-09-09 08:58:30 UTC,"Summary before reboot to installed OS:
- Multiple input settings are confusing.
- Settings in one, are not reflected in all.
- Settings for layout during installation are applied, but not reflected.
- Settings for layout in system tray settings are applied, but not reflected.
- Settings for layout in Hardware settings are not applied, and not reflected."
1716101,2017-09-09 08:45:49 UTC,"The assistive technologies icon also doubled. not sure if that's related, but it happened after installation."
1716101,2017-09-09 08:46:51 UTC,But before reboot to the new installation*
1716101,2017-09-09 08:52:23 UTC,"also found that setting the input in the system tray setting is not reflected in the one from hardwaresettings, but still takes affect.
and setting the keyboard layout in the one from hardwaresettings is not reflected in the one from systemtray, and does not take affect either."
1716101,2017-09-09 08:54:38 UTC,"and heres the screenshot from setting set in hardwaresettings, when not taking affect.
(system tray is set to dvorak, hardaware is set to querty)."
1716101,2020-05-22 04:17:36 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1716109,2017-09-22 06:40:18 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502282"
1716109,2017-09-22 06:41:27 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502283"
1716109,2017-09-22 06:40:03 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502254"
1716109,2017-09-26 18:20:39 UTC,"Since the new method was added in Python 3.1 and Swift only supports Python 2.7, marking invalid."
1716109,2017-10-16 01:04:32 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502240"
1716109,2017-09-22 06:42:10 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502286"
1716109,2017-09-22 06:39:47 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502253"
1716109,2017-09-10 02:00:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502286"
1716109,2017-09-22 06:31:26 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/502243"
1716109,2017-09-10 01:52:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502283"
1716109,2017-09-10 01:46:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502282"
1716109,2017-09-09 15:37:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502254"
1716109,2017-09-09 14:16:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502243"
1716109,2017-09-09 13:34:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502240"
1716111,2017-09-29 11:26:18 UTC,"Feature request, triaging as wishlist."
1716114,2017-09-21 18:01:14 UTC,"Change abandoned by Sashi Dahal (<email address hidden>) on branch: master
Review: https://review.openstack.org/506322
Reason: wrong bug fix.. will resubmit"
1716114,2018-03-15 14:42:53 UTC,This doesn't explain what the issue is.
1716114,2017-09-21 17:44:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506322"
1716119,2017-09-09 12:01:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502235"
1716119,2017-09-12 17:30:59 UTC,"Reviewed:  https://review.openstack.org/502235
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=eafed0be45214852cfa04140b101f617dce59bf3
Submitter: Jenkins
Branch:    master"
1716120,2019-08-10 20:33:00 UTC,Still doesn't work on package 5.8.0
1716120,2018-02-14 20:20:08 UTC,"Steps to reproduce:
1. Install Muon on Ubuntu Zesty, Artful or Bionic.
2. Enable columns ""Installed Size"", ""Installed Version"", ""Available Version"" by right click
3. Click on any column of ""Installed Size"", ""Installed Version"", ""Available Version"" to sort by it."
1716120,2018-04-06 21:30:54 UTC,Bug exists in bionic beta2.
1716120,2018-06-19 09:15:12 UTC,"Git commit c3fe8f7ceb66d33aa24999df5ab0572d10044700 by Carlo Vanini.
Committed on 19/06/2018 at 09:12.
Pushed by vanini into branch 'master'."
1716120,2019-04-01 17:29:54 UTC,Still unable to sort on 19.04 beta.
1716120,2019-08-10 20:32:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716120,2020-09-25 20:58:55 UTC,"Fixed in upstream git, waiting on new release or someone to add the patch to ubuntu"
1716126,2017-09-09 13:48:30 UTC,Screenshot of error-message.
1716132,2020-11-09 18:32:10 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Thank you and sorry for the inconvenience."
1716132,2021-01-09 04:17:52 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1716139,2017-09-12 00:02:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716139,2017-12-02 16:10:52 UTC,This was fixed in Firefox 57 but reintroduced in 57.0.1
1716139,2018-09-12 09:42:13 UTC,Please consider removing unnecessary OS information form Chromium.
1716139,2019-02-20 18:37:18 UTC,"Also, the chromium snap UA has extra info identifying it as a snap:
""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/72.0.3626.96 Chrome/72.0.3626.96 Safari/537.36"""
1716141,2017-10-20 12:15:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716141,2017-10-20 12:15:57 UTC,I have the same issue after upgrading to 17.10
1716141,2017-10-20 12:40:41 UTC,I fixed it in my case by reinstalling pulseaudio and pulseaudio-module-bluetooth and restarting pulseaudio
1716146,2020-08-04 17:16:24 UTC,Looks like a duplicate of bug 1679570.
1716172,2018-09-21 14:44:15 UTC,"Created attachment 7992
Proposed fix"
1716172,2018-08-21 06:52:38 UTC,Still have this problem on Arch GNU/Linux:
1716172,2017-12-03 18:34:29 UTC,I guess my bug https://bugzilla.xfce.org/show_bug.cgi?id=12463 is related to this one.
1716172,2017-10-27 18:40:19 UTC,Similar problem here with XFCE on Gentoo Linux:
1716172,2017-09-16 19:25:22 UTC,What info is needed?
1716172,2017-09-15 13:05:53 UTC,I'm seeing this with:
1716172,2017-09-15 12:37:27 UTC,"After comparing both bugs, I think think one more accurately matches the issue"
1716172,2017-09-13 00:48:26 UTC,"Also, I think this is a related or duplicate bug in the xfce bug tracker:  https://bugzilla.xfce.org/show_bug.cgi?id=10459"
1716172,2017-09-13 00:27:56 UTC,"It seems the mirror displays issue is tracked in a separate ticket upstream and launchpad is discouraging adding a second external link, so it's probably best that I just make that a separte issue here and then link."
1716172,2016-05-18 19:27:50 UTC,"[Please somebody set this bug's status to something other than ""needinfo"".. It is not the reporter's turn.. It needs attention from somebody else that reporters.]"
1716172,2016-05-18 17:00:02 UTC,"Hi! This bug (re)appeared in my freshest Xubuntu! Just upgraded to xenial.
I have ""xfce4-settings  4.12.0-2ubuntu1  amd64"" (if it matters)."
1716172,2015-12-01 15:00:43 UTC,"CONFIRMED.  This happens to me on Archlinux using Intel HD 6000 GPU, with dual monitors, one above another."
1716172,2015-02-16 23:53:15 UTC,"Added the PPA, updated and upgraded XFCE."
1716172,2015-02-04 02:01:23 UTC,You can get the latest git snapshot (4.11.3 + fixes) here:
1716172,2015-02-01 01:58:18 UTC,Is there a PPA for Ubuntu that I can get that version from (the latest in the normal repos is 4.11.2)
1716172,2015-01-31 12:37:01 UTC,Can you please test this again with xfce4-settings 4.11.3?
1716172,2013-11-02 13:13:22 UTC,"Given an nVidia card driving 2 displays (one laptop display, one LCD on DVI), configured for dual display (over and under), the settings are correctly enacted when XFCE first starts from boot, but thereafter, if I suspend the computer and restart, the settings are reset to one monitor (external display)."
1716184,2017-10-24 01:20:51 UTC,"I got the bios upgraded, but the problem has not gone away.
I hope someone would look into this problem.  The machine is usable, but I cannot
access any display output except default, as described in the the original bug
report.  I can demonstrate that the hardware is correctly working by changing the
bios setting to boot using the hdmi display, but then the laptop screen does not
work and xrandr does not find it."
1716184,2018-01-23 02:13:11 UTC,This problem has been RESOLVED.
1716189,2017-09-18 12:06:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1716189,2017-09-19 00:49:36 UTC,"On 2017-09-18 08:06 AM, Sebastien Bacher wrote:

> ...
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
> tell us the number of the upstream bug (or the link), so we can add a
> bugwatch that will inform us about its status. Thanks in advance.
>

https://bugzilla.gnome.org/show_bug.cgi?id=787868"
1716189,2017-09-19 11:41:35 UTC,thanks
1716190,2017-11-27 18:18:11 UTC,"gpg changed the output format later on to remove ""Key fingerprint=""."
1716190,2017-11-27 18:16:58 UTC,"Notably, the word fingerprint does not appear anywhere in the output, so if you search for literally that, then that's your problem."
1716190,2017-11-27 18:20:48 UTC,"Or maybe we did, but I'm not sure where."
1716190,2017-11-27 18:15:20 UTC,Works for me:
1716190,2017-11-27 17:58:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716190,2017-11-27 18:15:48 UTC,Does it output anything to your terminal?
1716197,2017-09-11 15:20:23 UTC,The transform is applied to accommodate the scale of 1uu/mm. The transform would not be applied if the scale were set to 3.77953/uu (=96dpi). (See bug https://bugs.launchpad.net/inkscape/+bug/1670913)
1716197,2017-09-12 07:19:51 UTC,"Yes, I've made the suggestion to the user to try a diffrent gcode tool, because that behavior seems odd to me as well."
1716197,2017-09-12 13:43:19 UTC,"The user would likely benefit from setting the default.svg document properties such that display units = mm and scale = 3.77953. For new documents, this should prevent the transform attribute from occurring (which seems to be a source of confusion and could possibly interfere with the user's particular CAM application)."
1716205,2020-08-10 10:38:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716205,2020-08-10 11:20:29 UTC,"This is a bit late, but can you please provide some additional info:"
1716205,2020-10-10 04:17:17 UTC,[Expired for ibus (Ubuntu) because there has been no activity for 60 days.]
1716208,2017-09-28 11:32:54 UTC,"The crash seems random when opening the overview mode in Gnome shell. The entire desktop crashes and the user is logged out from session.
Uninstalling Epiphany browser for now as a workaround seems to make crash go away."
1716208,2017-09-10 09:06:25 UTC,"StacktraceTop:
 wl_list_insert_list (list=0xcb25de8388, other=0xcb25de8378) at ../src/wayland-util.c:89
 wl_priv_signal_emit (signal=signal@entry=0xcb25de8378, data=data@entry=0xcb25de8310) at ../src/wayland-server.c:1955
 wl_display_destroy (display=0xcb25de8310) at ../src/wayland-server.c:1077
 WebCore::PlatformDisplayWayland::~PlatformDisplayWayland (this=0x7f94528f31f8, __in_chrg=<optimized out>) at ./Source/WebCore/platform/graphics/wayland/PlatformDisplayWayland.cpp:71
 WebCore::PlatformDisplayWayland::~PlatformDisplayWayland (this=0x7f94528f31f8, __in_chrg=<optimized out>) at ./Source/WebCore/platform/graphics/wayland/PlatformDisplayWayland.cpp:72"
1716208,2017-09-12 00:04:33 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1716208,2017-09-20 08:25:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716212,2017-09-15 23:57:28 UTC,"A hell! It's the ""bin"" folder!
I just verified it by putting Inkscape into a bin folder on my system and - it crashes when selecting the node tool."
1716212,2017-09-16 06:47:48 UTC," >  libraries often check if they're run from a folder called ""bin""."
1716212,2017-09-15 22:47:38 UTC,"It's puzzling that a fresh install of 64-bit Inkscape 92.2 appears to use (e.g.) libgtk-win32-2.0-0.dll, whereas the instructions for compiling 64-bit Inkscape on Windows via MSYS2 produces an install directory that appears to be using libgtk-3-0.dll. I don't see how I could actually accurately recreate the 64-bit release version via those instructions."
1716212,2017-09-16 13:18:05 UTC,"Some more details:
The bug is in glib (specifically the function g_win32_get_package_installation_directory_of_module) which is supposed to make relocations work but actually seems to break them in this case by returning the parent directory of whatever /bin directory it can find in the path as the alleged installation directory of the module."
1716212,2017-09-15 10:31:47 UTC,"Gave it a go. After much work, all I ended up with was an inkscape.exe that dies at early startup in one of the many DLLs. Discouraging."
1716212,2017-09-18 17:05:35 UTC,"Well, let's see what upstream decides, first (they seem to slowly acknowledge the problem)."
1716212,2020-08-15 18:27:16 UTC,Closing for 2 reasons:
1716212,2020-08-20 07:27:15 UTC,u just lost 46 points jonathan 🤣🤣🤣
1716212,2017-09-18 02:17:18 UTC,My obviously biased desire would be that no one else in the great wide world ever waste as much time on this wildly unexpected behavior as we have :-). Possible actions that come to mind:
1716212,2017-09-14 09:06:32 UTC,"> I naively thought that 64-bit Inkscape would
> be compiled with a different memory model.
"
1716212,2017-09-15 23:50:40 UTC,"After cloning the GitLab repository using
  git clone https://gitlab.com/inkscape/inkscape.git master
you've checked out the master branch by default (what will eventually become Inkscape 0.93) which uses GTK+3 as you noticed."
1716212,2017-09-11 09:42:47 UTC,"It's not overly surprising all builds behave similarly:
They're all built identically (with MSYS2) since Inkscape 0.92.2."
1716212,2017-09-11 06:53:20 UTC,"To my surprise, 32-bit Inkscape produces the same crash (as does ""Inkscape Portable"")."
1716212,2017-09-11 06:35:15 UTC,"Found another 64-bit Windows 7 machine to run 64-bit Inkscape on. Works fine there, of course. By stripping stuff, was able to make the DLL loads look as close as possible. MSVCR90 was pulled in by the HUION tablet driver (which of course should cause no problem, but...). Uninstalled tablet. Turned off Windows Tablet Components. Turned off ""use pressure sensitive tablet"" in Inkscape. In the end there are about three differences between the DLL profile of the machine that works and the one that doesn't."
1716212,2017-09-14 06:30:12 UTC,I naively thought that 64-bit Inkscape would be compiled with a different memory model.
1716212,2017-09-10 23:33:06 UTC,"Removed bluetooth hook DLL, no change in behavior. Usually I use windbg to watch the DLLs load and get a second opinion on crashes, but if I can't figure out why it's failing to operate on inkscape.exe, I'll give ntldd a try."
1716212,2017-09-10 22:55:00 UTC,"Yes, uninstalling that bluetooth driver that is so rudely injecting itself into every process is worth a try at this point. I was putting it off because I have a jillion windows open, but will bite the bullet now."
1716212,2017-09-10 22:37:16 UTC,Find above the output of set and listdlls from a 32-bit Windows 7 Enterprise (Modern IE Virtual Box image) where Inkscape is running flawless.
1716212,2017-09-10 20:16:38 UTC,"- I confirmed that %APPDATA\Roaming\inkscape was removed after I did a full uninstall
- Each Inkscape install required creating a new directory, which was removed upon uninstall
- I have no virus scanners installed
- I only installed MinGW to get the gdb trace, so the problem appeared before that
- executing with a reduced PATH produced same behavior, no output in the console window
- not sure why I can't run windbg on inkscape.exe; presumably unrelated issue or misunderstanding on my part"
1716212,2017-09-10 18:44:40 UTC,To be honest this issue leaves me a bit puzzled: simply selecting the node tool should obviously not crash Inkscape...
1716212,2017-09-10 18:11:56 UTC,"Thank you much(!) for trying to repro, which helped me stop focusing on things like the png file and using a gradient mesh. Actually, F2 simply crashes on any file, including empty file. Did I really never use node tool after upgrading to 0.92.2? Not sure, could be losing my mind at this point."
1716212,2017-09-10 13:58:49 UTC,"With ""Node edit tool"" you meant ""Edit path by nodes (F2)""?"
1716219,2017-09-10 11:21:54 UTC,My initial triage:
1716219,2018-11-26 12:57:05 UTC,Any news on this? It's been almost 1.5 years since reporting...
1716227,2019-05-28 04:17:36 UTC,[Expired for kolla because there has been no activity for 60 days.]
1716227,2019-03-28 10:37:37 UTC,Is this still a bug? If yes - please update.
1716227,2017-09-10 14:39:17 UTC,"After adding and chown/chmodding /etc/ceph/ceph.client.admin.keyring, I can successfully connect to ceph (ceph -s) as the cinder user. Restarting the container at that point still doesn't fix the problem with cinder-volume failing to connect."
1716227,2017-09-10 14:12:55 UTC,"Does ceph require ceph.client.admin.keyring? This is a kolla defect if so, since that file is not populated in the container."
1716227,2017-09-10 14:01:17 UTC,-rwx------   1 cinder cinder   64 Sep 10 08:24 /etc/ceph/ceph.client.cinder.keyring
1716227,2017-09-10 13:59:26 UTC,That fails: Error connecting to cluster: ObjectNotFound
1716227,2017-09-10 13:49:34 UTC,"Can you please try out if you are able to run the ceph commands from cinder
volume"
1716229,2017-09-10 13:49:44 UTC,"As a consequence of this issue, if you are on a 64 bit system and you need to use legacy gtk2 applications, you get lots of warnings and a bad integration of the application with your system look and feel."
1716232,2017-09-20 12:09:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716232,2017-09-21 22:00:07 UTC,"I guess this bug is about making the option available from the GUI. In any case, for people that want to try it, you can set it by running:"
1716232,2017-11-12 20:49:03 UTC,"Coming from https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730199 I've recently noticed there is one wheelmouse action available on artful dock by default : on the « applications » icon, it allows you to change workspace, which is very convenient ( no more need for the ugly activities button )"
1716232,2019-04-23 12:25:23 UTC,"Thanks François, this command did enable the feature for me:"
1716235,2017-12-12 15:39:01 UTC,"> I mean if switching between passthrough and plain Aux is a use case?
"
1716235,2017-12-12 12:13:51 UTC,"I mean if switching between passthrough and plain Aux is a use case?
.. or will the user use Aux only though decks in this case an never as plain aux."
1716235,2017-12-12 11:14:34 UTC,"I didn't do this during live gigs, but in sessions with friends we sometimes try to blend in snippets from news shows and other stuff we don't have available in the library (""Dude, I have this BANGER track on my phone, let me drop that!!"""
1716235,2017-12-12 06:55:00 UTC,"Yes, that would be an option."
1716235,2017-12-12 00:41:56 UTC,"The longer I think about this, shouldn't all controls in the Aux section be blocked? FX assign  buttons, orientation, even Gain?"
1716235,2017-12-10 23:28:36 UTC,"Yes, the Conexant soundcard supports 48kHz, too. My mistake..
API is alsa. Buffer underflow happens no matter which latency I set."
1716235,2017-12-10 23:22:50 UTC,"I imagine that the L-M-R bus in the Aux unit would be ignored as soon as Aux is assigned to a deck (i.e. greyed out with a proper tooltip), and only the decks crossfader orientation is used (exposed in skin or not) as one would expect when playing a regular track. You're right, anything else would be confusing. If a user routes Aux to two or more decks he would be aware off that.
I think that can be a nice toy, for example one could use different effects/filters on the same source: Aux copy1 is just the bass, Aux copy2 is the isolated voice with a reverb."
1716235,2017-12-10 19:20:07 UTC,"What is you Mixxx sample rate and API?
Normally all soundcards support 48000 Hz. So you have to pick 48000 Hz in Mixxx."
1716235,2017-09-10 22:41:27 UTC,"I think Daniel was alluding the possibility of routing the auxiliary input to an effect rack with an EQ effect loaded in it. That could work, but IMO it is an ugly hack, not really a solution. I think ronso0 is asking for a way to set any deck to any configured sound card input."
1716235,2017-12-10 18:35:21 UTC,"The buffer underflow happens for Aux as well.
But only when I set Terminal Mix 2/4 as output device (48000Hz only) and internal Conexant CX20590 (44100Hz) as input device. When I configure them the other way around (Terminal as input, Conexant as output), there's no underflow."
1716235,2017-12-05 16:52:25 UTC,Do you have no buffer underflow reports if you use Aux instead of talkover? This seems to be a separate issue.
1716235,2017-12-05 15:20:49 UTC,"Okay, I wasn't aware that we can assign one vinyl control signal to multiple decks.
That solves the bug for my use case."
1716235,2017-12-04 23:11:36 UTC,"We can do this already.
You can assign one input, from your mobile device to all decks vinyl control.
Now you can decide via the pass-through switch, through which deck this should play.
Does this solve the bug for you?"
1716235,2017-09-10 20:02:29 UTC,"I route the line-in of my Reloop Terminal Mix 2/4 as Vinyl Control passthrough to a deck, mostly deck 1. I don't use control vinyl to play mixxx tracks."
1716235,2017-09-10 18:25:14 UTC,"Do you use vinyl control and Aux?
What is the reason to not use an effect rack for Aux and the Aux x-Fader orientation?"
1716235,2017-09-10 15:26:53 UTC,Related: Bug #1407222
1716235,2017-12-10 19:10:02 UTC,"From the UI aspect that could makes sense. But the L/M/R bus is still active than. That can be confusing.
Will Aux than be passed directly for instance to the L Bus AND to the decks?
Or should we force the routing button to ""Ch1"" in this case?"
1716249,2017-09-13 10:45:48 UTC,"I agree with Daniel that hiding headphone controls is not a good solution.
A first-time user who has not yet set up the output devices properly may be irritated/disappointed by this basic feature missing. This might also happen if devices get messed up/removed between mixxx shutdown/restart."
1716249,2017-09-12 21:01:32 UTC,This is a question of consistency.
1716249,2017-09-12 19:32:45 UTC,I disagree. I find that dialog annoying. I think it would be better to hide parts of the GUI that are not functional with the user's configuration.
1716249,2017-09-12 19:16:50 UTC,Good idea.
1716249,2017-09-12 18:51:08 UTC,What about adding a hint like the one that pops up when trying to enable 'passthrough' although there's no vinyl/line input set up?
1716249,2017-09-10 22:47:02 UTC,I am not aware of any DJ mixers that have an auxiliary input which can be sent to headphones but not the main output. That would just be another normal deck input. The Preview deck is a convenience feature for some users who prefer to use it with internal mixing. It is not at all necessary and the use case is already supported by previewing decks normally (personally I never use it). IMO the only problem here is that the GUI for the Preview Deck is shown when the user's hardware configuration does not support it without any explanation of why the feature doesn't work.
1716249,2017-09-10 23:19:42 UTC,Daniel: Thanks for the suggestion. You've been more than kind in indulging my questions.  I don't want to waste any more of your time with this. I was just curious and I didn't understand the intended functionality of the Preview Deck. I understand now that the Preview Deck is intended for those without an external mixer. You can close this issue.
1716249,2017-09-10 20:49:44 UTC,I am not sure what you are requesting. Which version of Mixxx you are using? Which external Mixer are you using?
1716249,2017-09-10 18:36:14 UTC,"Be: Thanks for your clarification. Perhaps, the Preview Deck could have a HEADPHONE Toggle, like the Sampler Decks. If the Preview Deck is only ever intended to be sent to headphones, I understand and this bug can be closed as intentional / won't fix. I suppose the fact that headphone output CANT be sent to an external mixer, without an additional soundcard output, would be out-of-scope for this bug report. If I'm dreaming of out-of-scope features, though, it would be neat if Mixxx could BUS / MUX multiple outputs to any single channel."
1716249,2017-09-10 17:09:38 UTC,"The Preview Deck is only sent to the Headphones output, so it cannot be used with an external mixer unless your sound card and mixer both have a spare stereo pair of channels, in which case it would probably make more sense to send another regular deck instead. I think the issue here is that the UI has no indication that the preview deck is not functional when there is no Headphones output configured. Mixxx could either hide all Preview Deck widgets from the GUI or pop up a dialog explaining that the feature only works with the Headphones output configured when the preview button is pressed in the library. I think it would be better to hide the features."
1716249,2017-09-10 23:29:23 UTC,"I have changed the bug title to reflect the issue better. It is indeed a user experience issue, but it is a minor one."
1716250,2017-09-12 06:22:35 UTC,"Locale affects also Google maps. see attached screenshot: same map on left with US locale, on right with Italia"
1716250,2017-09-19 07:31:37 UTC,This bug was fixed in the package mesa - 17.2.1-0ubuntu1
1716250,2017-09-12 13:27:57 UTC,waiting for 17.2.1
1716250,2017-09-11 18:33:16 UTC,"Hello,"
1716250,2017-09-11 12:01:45 UTC,"Thank you for your bug report, what packages did you upgrade to get the issue?"
1716250,2017-09-11 13:53:11 UTC,Similar problem with cheese: see attachment.
1716250,2017-09-11 13:34:46 UTC,That seems similar to https://bugzilla.gnome.org/show_bug.cgi?id=787328 upstream
1716250,2017-09-11 13:20:21 UTC,I don't know what package upgrade caused the problem because I just run apt update+upgrade and the upgrade changed a lot of packages. If needed I may attach \var\log\apt ... please let me know if You need it.
1716250,2017-09-11 14:09:57 UTC,"After reading notes in https://bugzilla.gnome.org/show_bug.cgi?id=787328 I changed my 'locale' from Italia to United States and the problem disappeared, so I can confirm this bug is the same.
Thanks."
1716266,2019-12-11 20:07:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716278,2017-09-10 20:26:58 UTC,"StacktraceTop:
 XForceScreenSaver (dpy=0x9a7e52c900, mode=mode@entry=0) at ../../src/FSSaver.c:53
 XResetScreenSaver (dpy=<optimized out>) at ../../src/FSSaver.c:42
 gs_monitor_simulate_user_activity (monitor=0x9a7e584340) at gs-monitor.c:195
 listener_simulate_user_activity_cb (listener=<optimized out>, monitor=0x9a7e584340) at gs-monitor.c:287
 g_closure_invoke (closure=0x9a7e5b4210, return_value=0x0, n_param_values=1, param_values=0x7fff374682c0, invocation_hint=0x7fff37468240) at ../../../../gobject/gclosure.c:804"
1716278,2017-10-06 18:55:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716278,2017-10-23 12:53:40 UTC,Gnome-screensaver shouldn't be running on GNOME Shell. It's 5 years old software and is needed only for old GNOME flashback (fallback) session.
1716278,2017-10-23 20:02:59 UTC,"This is a system that's gone through upgrades from at least xenial through artful. I never manually enabled it, but it could have been included in an older session along the way and carried forward if nothing stopped it."
1716283,2018-03-06 20:51:03 UTC,"Hmm, I can no longer reproduce this... closing"
1716295,2018-01-31 08:40:49 UTC,I have the same issue!!
1716295,2019-01-15 16:30:36 UTC,I have this issue as well.
1716295,2019-01-15 16:31:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716298,2018-05-14 11:03:41 UTC,This change was made by a bot.
1716301,2017-11-03 17:20:45 UTC,"$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.14.0-041400rc7-generic root=UUID=7c46b69f-ad98-4f49-93ac-2e5a68fbd6dc ro quiet splash usbcore.autosuspend=-1 vt.handoff=7"
1716301,2017-11-03 04:34:49 UTC,"Try if kernel parameter ""usbcore.autosuspend=-1"" helps."
1716301,2017-11-02 16:50:23 UTC,Luckily I could convince the owner of the system that testing this kernel wouldn't do any harm.
1716301,2017-11-02 09:14:22 UTC,Yea I can see same error.
1716301,2017-11-01 15:47:00 UTC,Attached dmesg output from a USB 3.0 system with kernel 4.4.0.
1716301,2017-10-14 12:48:26 UTC,"BTW, is mt7601u also a GSM modem?"
1716301,2017-10-29 16:09:12 UTC,Tried kernel 4.13.10 to no avail. Seems my adapter is slightly different. It does not show up as disk. Instead it is recognized as WLAN device immediately. Error msg is also different. Pls see attached file dmesg_kernel_4.13.10 and let me know if you need more information or want my to test further.
1716301,2017-10-27 17:06:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716301,2017-10-16 01:57:54 UTC,A log:mt7601-1.pcapng caputured by Wireshark on Windows.
1716301,2017-10-14 14:43:27 UTC,"I am not sure if mt7601u is GMS modem or not, however, I guess Yes, because it's the only device related to wireless on my computer"
1716301,2017-10-31 08:04:48 UTC,Both of you plugged mt7601u into EHCI (USB 2.0) port.
1716301,2017-11-06 09:28:12 UTC,"Forgot to ask an important question, did the device work on on earlier Ubuntu Release, e.g. Precise & Trusty?"
1716301,2019-04-18 12:26:57 UTC,"The attachment ""patch for the driver"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1716301,2017-11-07 03:34:08 UTC,"Please try kernel here, I added some quirks for the device,
http://people.canonical.com/~khfeng/lp1716301-corequirks/"
1716301,2017-11-08 06:11:35 UTC,Thanks for all your efforts.
1716301,2017-11-08 07:44:02 UTC,So it didn't work.
1716301,2017-12-10 17:08:04 UTC,Unfortunately the workaround from the previous post did not work for me. Do still get the same error.
1716301,2017-12-20 14:16:57 UTC,"The Windows driver that's on an adapter's embedded virtual CD contains FW_7662.bin (79216 bytes). I tried replacing the /lib/firmware/mt7601u.bin with that firmware. Driver loads the firmware onto the device:
mt7601u 1-3:1.0: Firmware Version: 0.0.00 Build: 1 Build time: 201411280941____"
1716301,2018-01-17 02:31:40 UTC,"In ubuntu 14.04,kernel 4.4.0-109-generic also has this issue，I tried https://github.com/kuba-moo/mt7601u/issues/64 but is not work.lsusb show Bus 003 Device 005: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter,which model is TP-link w725n （Free drive）.I have tried many ways but still can't resolve it,however it works fine in Virtual box win7 system."
1716301,2018-10-29 23:13:36 UTC,"The solution described here worked for me in Ubuntu 16.04 and 18.04:
https://github.com/kuba-moo/mt7601u/issues/64#issuecomment-352250127"
1716301,2019-04-18 08:36:22 UTC,"Hello folks,"
1716301,2019-04-18 09:27:45 UTC,Please upstream the patch first so we can backport it.
1716301,2020-01-23 23:37:00 UTC,"Seems the fix was not accepted/applied. Just tried latest 18.04, 19.04 and finally 19.10 with kernel 5.3.0-26-generic #28-Ubuntu"
1716301,2020-07-02 03:46:53 UTC,"Tested and now my MT7601U USB Dongle (Ralink Technology, Corp. MT7601U Wireless Adapter) is working in Ubuntu 20.04 :)
https://askubuntu.com/questions/1205254/ralink-tech-mt7601u-wireless-adapter-on-xubuntu"
1716301,2017-10-14 12:47:48 UTC,You can use usbmon and Wireshark.
1716301,2017-11-06 19:02:24 UTC,Bought the device some days ago. Had no chance to test earlier Ubuntu releases.
1716301,2017-10-14 11:34:28 UTC,"Sorry the late.
Test Result on the new kernel:
same vendor request failed -110"
1716301,2017-12-26 16:15:15 UTC,"Retried with recent instructions from mrgromov in post https://github.com/kuba-moo/mt7601u/issues/64 and got it to work.
Would it be possible to create a fix or is this particular device buggy?"
1716301,2017-10-06 09:24:01 UTC,"Okay, I think it'll be better to debug yourself, it's hard to debug without physical hardware access."
1716301,2017-09-11 03:00:39 UTC,This change was made by a bot.
1716301,2017-09-11 14:13:46 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1716301,2017-09-11 22:35:14 UTC,I bought this adapter just few days ago and did not have a system upgrade in recently week.
1716301,2017-09-20 10:50:07 UTC,Does 148f:7601 only appear after the disk gets ejected?
1716301,2017-09-22 07:48:31 UTC,"Yes, it's first mounted as a readonly USB disk, including driver files for Windows.
and lsusb shows:
Bus 003 Device 002: ID 148f:2878 Ralink Technology, Corp."
1716301,2017-09-25 07:41:33 UTC,"Ok, after some digging, the kernel mode modeswitch was deprecated long time along."
1716301,2017-09-25 07:43:32 UTC,Add the following to /lib/udev/rules.d/40-usb_modeswitch.rules:
1716301,2017-09-25 16:09:11 UTC,"@Kai-Heng Feng,
I guess adding that line in the /lib/udev/rules.d/40-usb_modeswitch.rules is
to automatically switch the adpater to wireless card mode, however, after added that line,
and tried restart service udev (sudo service udev restart), the adpater is still first mounted
as usb storage disk (yes, lsusb only show 148f:2878, I must click an icon on the Launch Bar to eject the disk, and lsusb changed to 148f:7601."
1716301,2017-09-26 04:00:45 UTC,"Okay, you also need to add more data to /usr/share/usb_modeswitch/configPack.tar.gz."
1716301,2017-09-26 06:09:32 UTC,"This time, the adapter is first recognized as 148f:7601.
and the dmesg output is some different."
1716301,2017-09-26 07:01:38 UTC,Now please go back to comment #3 to test kernel itself (again).
1716301,2017-09-26 08:29:25 UTC,"I tried kernel 4.13. however, no much diff with kernel 4.4.0-91.
I must mention that in both kernel, no ALAWAYS the adapter is automatically recoginized as 148f:7601, sometimes, it still mounted as 148f:2878, sometimes, it's 7601. ( I found the pattern is: unplug the adapter, wait a relative long time, e.g: 1 or 2 minutes, plug the adapter, then it's 7601. if immediately plug in the adapter, say just wait 10 seconds, mostly, it's mounted as usb stroage disk and will not change to 7601)."
1716301,2017-09-26 09:07:29 UTC,"I just fell a little strange that is , why some info log in mt7801u is not printed,
e.g: in 09-26.2.txt, no any log about mt7601u. however, in mt7801u code, it printed those info...."
1716301,2017-10-10 10:52:24 UTC,"The device probably requires a delay between modeswitch, it's pure guesswork though. Please try kernel here:
http://people.canonical.com/~khfeng/lp1716301-delay-quirk/"
1716301,2017-09-27 12:34:39 UTC,"What do you mean ""Artful live image"" ?
do you mean boot computer with the latest release ISO ?
Ubuntu 17.04 ISO on the page: https://www.ubuntu.com/download/desktop"
1716301,2017-10-06 09:22:41 UTC,"forget to mention test result:
same vendor request failed with -110 event long timeout"
1716301,2017-10-06 08:51:06 UTC,"I tried the timeout value: 10000
Please see the attached: 4.14-long-timeout.txt
Thanks"
1716301,2017-10-06 06:36:50 UTC,"Can you try values even larger? e.g. 3000, 10000."
1716301,2017-10-06 03:27:44 UTC,You can use modprobe conf to do that:
1716301,2017-10-05 23:53:46 UTC,"Hi, I am not sure where to add this timeout ?
in the /etc/sysctl.conf, or in the /boot/grub/grub.cfg
Thanks!"
1716301,2017-10-06 06:16:42 UTC,"Test result on kernel 4.14
1. same vendor request failed with -110
2. I notice that the Wire network(yes, Wire network) is also not work on 4.14. on kernel 4.4.0-91 (the kernel my mostly used), it's work"
1716301,2017-09-27 07:48:54 UTC,Weird. Can you try Artful live image?
1716301,2017-10-02 16:27:10 UTC,"I tried on kernel 4.13. that's,"
1716301,2017-10-02 07:10:44 UTC,"Can you add ""mt7601u.dyndbg=+p"" to your kernel parameter and attach dmesg here? Thanks."
1716301,2017-09-28 13:49:57 UTC,"I tried the Artful image.
on the Artful image, it doesn't need to change any settings, the adapter is automatically recognized as 148f:7601, however, the same vendor request -110 error in the dmesg log."
1716301,2017-09-28 07:37:05 UTC,http://cdimages.ubuntu.com/daily-live/current/
1716301,2017-10-03 07:11:16 UTC,Please use the kernel here: http://people.canonical.com/~khfeng/lp1716301/
1716304,2017-09-11 17:04:51 UTC,apport information
1716304,2017-09-11 17:35:41 UTC,"I used this command in a terminal as directed:
apport-collect 1716304
and now the post seems to be corrupted."
1716304,2017-09-11 17:05:08 UTC,apport information
1716304,2017-09-11 17:05:04 UTC,apport information
1716304,2017-09-11 17:04:58 UTC,apport information
1716304,2017-09-11 17:04:57 UTC,apport information
1716304,2017-09-11 17:04:50 UTC,apport information
1716304,2017-09-11 17:04:53 UTC,apport information
1716304,2017-09-11 17:04:45 UTC,apport information
1716304,2017-09-11 17:04:43 UTC,apport information
1716304,2017-09-11 17:04:39 UTC,apport information
1716304,2017-09-11 17:04:38 UTC,apport information
1716304,2017-09-11 14:14:22 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1716304,2017-09-11 03:30:20 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1716304,2017-09-11 17:04:47 UTC,apport information
1716322,2017-09-11 06:10:02 UTC,"This might be related to the setting ""org.gnome.desktop.interface scaling-factor"", because if I manually set it to zero (gsettings set org.gnome.desktop.interface scaling-factor 0), g-c-c now can change the display resolution."
1716322,2017-09-11 11:57:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1716322,2017-10-20 15:10:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716322,2019-06-08 02:47:24 UTC,"Same for me: I can use xrandr manually in an Xorg session, but not in the Wayland sesson."
1716326,2017-09-12 02:19:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502875"
1716329,2018-07-10 07:02:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/581223"
1716329,2018-07-24 10:14:59 UTC,"Reviewed:  https://review.openstack.org/528615
Committed: https://git.openstack.org/cgit/openstack/proliantutils/commit/?id=8bda34245178f3db40651d94c7c1e95b8ddddf51
Submitter: Zuul
Branch:    master"
1716329,2018-07-10 07:09:35 UTC,"Change abandoned by paresh sao (<email address hidden>) on branch: master
Review: https://review.openstack.org/581223
Reason: same topic"
1716329,2017-09-26 13:40:37 UTC,"Greetings,"
1716329,2018-03-23 07:12:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555664"
1716332,2017-09-11 07:43:08 UTC,"Btw: HP Thunderbolt Dock 65W variant works like a charm, without his problem.
USB devices (e.g. USB Keyboard) works, e.g. for boot selection, before booting the linux kernel."
1716332,2017-09-11 08:00:09 UTC,This change was made by a bot.
1716332,2017-09-11 14:14:45 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1716332,2017-09-11 14:26:29 UTC,"I bought the docking station some days ago and tested with kernels 4.10, 4.12 and 4.13 - all with the same result. For using the ubuntu-bug command, i switched back to 4.10. So, there's no (known) working kernel."
1716332,2017-09-20 11:04:20 UTC,Probably a good idea to ask thunderbolt maintainer about this issue...
1716332,2017-10-20 06:31:39 UTC,"Patch accepted, should be in the next kernel release."
1716342,2018-08-30 08:28:17 UTC,"Verified on Stable/Rocky.
No server crash observed, even in multiple iteration."
1716342,2018-08-30 08:50:03 UTC,Branch stable/Rocky
1716342,2018-07-11 04:45:33 UTC,@dharmendra
1716342,2018-07-10 02:39:05 UTC,"I tried to reproduce on master(rocky) with small number of VNFs(i.e. 20), but could not be able to reproduce it. I will try to verify it with same number of VNFs(i.e. 100) on master again."
1716344,2018-02-23 19:26:04 UTC,"Disregard #18. It is not really correlated with this bug. (this bug is about session parameters, my bug is about auth parameters)
https://bugs.launchpad.net/nova/+bug/1751349"
1716344,2018-02-23 06:18:53 UTC,"I am also seeing nova-api attempting to use the keystone public endpoint when /v2.1/os-quota-sets is called on my Pike deployment. This is not valid in my environment; the API must use the internal endpoint to reach keystone. When the public endpoint is used, the connection sits in SYN_SENT state in netstat until it times out after a minute or two."
1716344,2018-01-02 22:36:23 UTC,"For the record, this bug *does* break things (quotas) if the admin/internal networks can't access the public network (complete isolation).
Christoph Fiehe's solution works in that scenario too. Thank you for that snippet!"
1716344,2017-12-18 12:51:27 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1716344,2017-12-07 23:55:45 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1716344,2017-12-05 06:32:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/525475"
1716344,2017-12-05 02:53:15 UTC,"Reviewed:  https://review.openstack.org/513243
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1606467b29969eb45efbb56c1b148a4a6f53c5cf
Submitter: Zuul
Branch:    master"
1716344,2017-10-19 03:34:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/513243"
1716344,2017-10-17 14:25:14 UTC,"Looks like the APIs will still function, but you get a stacktrace:"
1716344,2017-12-11 21:25:07 UTC,"Reviewed:  https://review.openstack.org/525475
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=02af3d5901968927222c153cd768295f6b113fb0
Submitter: Zuul
Branch:    stable/pike"
1716344,2017-10-17 14:19:57 UTC,"To clarify, are you unable to update quota and flavor access? Or are you just seeing errors in the logs now but the APIs still work?"
1716344,2017-10-17 14:17:23 UTC,This is the similar change we made for nova making requests to placement:
1716344,2017-10-17 14:16:23 UTC,https://review.openstack.org/#/c/435010/6/nova/identity.py@34
1716344,2017-10-17 14:11:08 UTC,"The original description of this bug says it makes instance create fail, which would be incorrect. As stated, keystone is only used for project_id verification when updating quota or changing flavor access. There was a conscious decision to hard-code the public endpoint as the interface when this change was made, but we changed that hard-coding for nova talking to the placement endpoint so I don't see why we wouldn't also allow different endpoints for talking to keystone. And actually, the KSA adapter stuff that Eric Fried is working on in Queens all defaults to using the internal interface I think."
1716344,2017-10-17 13:45:40 UTC,"@jichenjc, I think the bug you mention *could* solve the certificate verification failure, but doesn't address the fact that we only get the endpoint URL from the service catalog by looking up the public one, even for internal communications."
1716344,2017-09-26 01:46:17 UTC,is this duplicate to  https://bugs.launchpad.net/nova/+bug/1704798 ?
1716344,2017-09-13 10:18:01 UTC,"With an additional dependency to ""keystoneclient"", we are able to get ride of the problem. This requires a small code modification of the class ""nova/api/openstack/identity.py"":"
1716344,2017-09-13 08:21:30 UTC,"It took some time to narrow down the problem. The issue was introduced with the Pike release, where project id verification for flavor access and quota modification got added."
1716344,2017-10-17 14:22:36 UTC,What actual API calls are returning 400s? Because VM Create shouldn't be touching this.
1716347,2017-09-12 15:37:20 UTC,"> However, this stackoverflow post (https://stackoverflow.com/questions/8487986/file-macro-shows-full-path) claims that it just gives the same result as __FILE__.
"
1716347,2017-09-12 10:51:54 UTC,"Gcc has a __BASE_FILE__ macro for this: https://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html.
However, this stackoverflow post (https://stackoverflow.com/questions/8487986/file-macro-shows-full-path) claims that it just gives the same result as __FILE__."
1716347,2017-09-11 10:00:00 UTC,"Hi Franz,"
1716352,2018-01-04 06:55:06 UTC,I am also facing the same issue. I could see heat is not updating the updates given in tacker. Please let me know the fix.
1716355,2017-10-11 13:11:54 UTC,"Is fixed, the next kolla tag 5.0.1 will carry the fix, in using stable/pike branch rather than git tag, the fix is already there."
1716357,2017-10-14 00:41:02 UTC,I ended up doing the extra work myself.
1716357,2017-10-14 00:40:56 UTC,"Hello Esko, or anyone else affected,"
1716357,2017-10-14 00:41:45 UTC,"Hello Esko, or anyone else affected,"
1716357,2017-10-05 19:29:10 UTC,"it's fixed in artful, it might affect zesty but I don't think it's important enough to be fixed in a non LTS which is about to become the non current one"
1716357,2017-11-02 15:56:04 UTC,This bug was fixed in the package evince - 3.18.2-1ubuntu4.2
1716357,2017-11-02 15:56:15 UTC,"The verification of the Stable Release Update for evince has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1716357,2017-11-02 15:56:55 UTC,This bug was fixed in the package evince - 3.24.0-0ubuntu1.2
1716357,2017-10-06 05:38:26 UTC,unassigning myself so others are free to take on and do the extra work requested
1716357,2017-10-30 15:32:25 UTC,"Tested version 3.18.2-1ubuntu4.2 (packages evince_3.18.2-1ubuntu4.2_amd64.deb, evince-common_3.18.2-1ubuntu4.2_all.deb, libevdocument3-4_3.18.2-1ubuntu4.2_amd64.deb and libevview3-3_3.18.2-1ubuntu4.2_amd64.deb) on xenial."
1716357,2017-10-06 05:37:15 UTC,"Well, feel free to work on a zesty update, I just don't intend to spend effort on a non LTS-version which is going to be the non current one before the SRU is in updates"
1716357,2017-09-29 19:22:41 UTC,I've uploaded a SRU bugfix for xenial
1716357,2017-10-05 19:50:58 UTC,Xenial to Zesty is still a supported upgrade path though.
1716357,2017-10-05 19:11:15 UTC,"Yes, zesty is affected. artful is not affected, as upstream did not apply the fix for CVE-2017-1000083 to trunk, due to the introduction of using libarchive by default. trusty is also not affected, as the mime types configure processing is handled differently there."
1716357,2017-10-04 21:35:21 UTC,Does this also affect Artful? Looks like Zesty is also affected.
1716357,2017-09-26 18:30:42 UTC,Please observe that this bug causes all lines in /etc/mailcap after the broken line to be skipped. Therefore it also prevents other mime type files from being opened by the intended application.
1716357,2017-09-26 16:09:07 UTC,"That's a regression from CVE-2017-1000083.patch, upstream fixed it with
https://git.gnome.org/browse/evince/commit/?h=gnome-3-20&id=ef6c1d98"
1716357,2017-09-11 16:28:25 UTC,"The attachment ""A patch for configure.ac that fixes this issue."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1716357,2017-09-11 09:38:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716357,2017-10-05 19:55:58 UTC,"Additionally, if it is a regression due to an update in zesty it certainly should be fixed there."
1716367,2017-10-01 06:29:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716373,2017-09-20 16:45:18 UTC,Thanks for reporting.
1716376,2017-09-12 09:00:32 UTC,Fixed in revision 1267.
1716389,2017-09-26 07:49:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716391,2019-03-06 14:07:51 UTC,I plan to pick up where kamil left off in train.
1716391,2019-03-05 13:11:41 UTC,Anybody planning to work on this?
1716391,2018-07-09 12:49:44 UTC,Related bug https://bugs.launchpad.net/heat/+bug/1635409
1716391,2018-07-09 12:48:49 UTC,Related (from UX view) https://bugs.launchpad.net/tripleo/+bug/1775346
1716395,2020-09-21 13:08:54 UTC,Closing because INVALID.
1716406,2017-09-11 16:41:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716409,2018-05-19 23:59:27 UTC,"Strange, installing Flatpaks seems to work fine in 0.11.3-3 now (with gnome-software 3.28.1-0ubuntu4.18.04.1 (the new version is a patch for snaps from bionic-proposed, nothing to do with Flatpak I don't think)). Glad that an Ubuntu dev is on it with keeping Flatpak up to date! :D"
1716409,2018-05-03 09:16:45 UTC,"@Ads20000, Yup I'm preparing an SRU for the next microrelease, you can track in bug 1767215. I am able to use flatpakref's with 0.11.3-3, if you are still having an issue please report upstream :-) (I have also seen issues discussed as different browsers acting differently, or the browser associating mime types itself - causing issues, wonder if that is the case here)."
1716409,2018-05-03 09:01:14 UTC,"I'm using 0.11.3-3 from the repositories, does 0.11.6 need to be SRU'd? Since this is a new upstream microrelease that should be acceptable, if someone wants to follow the process for making that happen: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure"
1716409,2018-05-02 23:37:35 UTC,"@Ad20000, Are you using flatpak version 0.11.4 or 0.11.5 from the PPA ? There was a regression which I found and reported here https://github.com/flatpak/flatpak/issues/1632 where flatpakref's could crash gnome-software. It has since been fixed and released in 0.11.6."
1716409,2018-05-02 09:19:32 UTC,"This bug seems to have been re-introduced in Ubuntu 18.04 (GNOME Software 3.28.1-0ubuntu4), should I file a new bug or re-open this one?"
1716409,2018-04-02 19:30:12 UTC,"Ok, I'll give you medium. Enjoy!"
1716409,2018-04-02 18:32:29 UTC,"For those wondering: I should've realized this much earlier, the importance being 'Low' is not some sort of anti-Flatpak conspiracy, it's because the bug satisfies the criteria for Low importance as per: https://wiki.ubuntu.com/Bugs/Importance"
1716409,2018-03-15 14:29:06 UTC,"@jbicha, sure reported an issue here to track the potential cache upgrade issue with 3.28 https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756098"
1716409,2018-03-15 13:58:42 UTC,"On Ubuntu 18.04 daily with flatpak 0.11.3, gnome-software-plugin-flatpak 3.28.0 I have not been able to reproduce this issue. I did have a separate issue, which looks like a bug in cleanups between versions of gnome-software as removing all apps, remotes and caches resolved the issue - I have reported this upstream https://gitlab.gnome.org/GNOME/gnome-software/issues/328."
1716409,2018-03-15 14:11:57 UTC,Could you split the cache upgrade issue into a separate Launchpad bug?
1716409,2018-01-31 12:42:49 UTC,I had the same error. So I installed gnome-software-plugin-flatpak and flatpak :
1716409,2017-09-11 15:31:01 UTC,I did 'sudo killall gnome-software'
1716409,2017-09-11 15:17:46 UTC,Screenshots showing me trying to install the pithos flatpak.
1716409,2017-09-11 15:16:20 UTC,"Did you restart GNOME Software after installing the plugin? And with that I mean kill it completely, even its background process."
1716409,2017-09-11 15:15:45 UTC,"I killed gnome-software and tried again, got the same experience Martin did."
1716409,2017-09-11 15:02:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716409,2017-09-11 15:01:51 UTC,I installed `gnome-software-plugin-flatpak`.
1716409,2017-09-11 14:58:33 UTC,You're right that I didn't have that plugin package installed. I installed it and double clicking the package still presents the same error. Apologies I omitted the screenshot in my initial report.
1716409,2017-09-11 14:39:11 UTC,"The GNOME Software Flatpak plugin is not installed by default.
Does installing the `gnome-software-plugin-flatpak` package fix this for you?"
1716409,2018-02-28 18:22:08 UTC,Is this still an issue on Ubuntu 18.04 with gnome-software-plugin-flatpak installed?
1716411,2017-12-11 15:59:10 UTC,This issue was fixed in the openstack/openstack-ansible-os_nova 17.0.0.0b2 development milestone.
1716411,2017-10-27 12:01:38 UTC,"Reviewed:  https://review.openstack.org/512044
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=b21acaf0c89379e020be8dc30d87d397889e16f7
Submitter: Zuul
Branch:    master"
1716411,2017-09-11 14:21:14 UTC,The full error from nova-compute:
1716411,2017-09-19 16:02:36 UTC,Fixed upstream by https://review.openstack.org/#/c/502487/
1716411,2017-10-03 16:50:48 UTC,See also: https://bugs.launchpad.net/openstack-ansible/+bug/1720535
1716418,2017-09-11 15:56:50 UTC,Probably related to: https://bugs.launchpad.net/tempest/+bug/1715859
1716418,2017-09-11 21:58:02 UTC,"Yea, a new release of os-testr was recently released which seems to be causing a few issues as now os-testr is using stestr (https://github.com/mtreinish/stestr) under the covers."
1716418,2017-10-26 09:36:45 UTC,"You should try this again with the latest stestr version, there were a couple of bugs in stestr that got fixed in the most recent 1.1.0 release: https://github.com/mtreinish/stestr/releases/tag/1.1.0 including the issues with the filter arguments."
1716418,2017-10-26 09:39:27 UTC,If you're still facing issues with any of the filter arguments please file an stestr bug so we can work on a fix.
1716424,2017-10-26 15:24:36 UTC,This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.14
1716424,2017-10-26 15:24:51 UTC,This bug was fixed in the package grub2-signed - 1.66.14
1716424,2017-09-25 19:34:02 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of grub2 from xenial-proposed was performed and bug 1719271 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1719271 (not this bug). Thanks!"
1716424,2017-09-26 19:34:40 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of grub2-signed from xenial-proposed was performed and bug 1719622 was found.  Please investigate that bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1719622 (not this bug). Thanks!"
1716424,2017-09-11 16:04:53 UTC,"Hello Mathieu, or anyone else affected,"
1716424,2017-09-11 16:02:28 UTC,"Hello Mathieu, or anyone else affected,"
1716424,2017-09-11 15:58:15 UTC,Can you expand on the test case to explain how to configure such a pmem-enabled system?
1716434,2019-03-27 13:51:09 UTC,"Doing some more testing on the desktop system, this now gets weird and weirder. My desktop is also effected by this, just not when running glxgears, I bought a bluetooth dongle to have the circle animation.
gnome-shell cpu usage:
Threaded swap wait enabled - Desktop:
glxgears - normal, no cpu spikes
g-c-c bluetooth animation - 85% cpu
dragging windows - 85%cpu"
1716434,2019-03-27 13:25:19 UTC,"As a PRIME (NVIDIA+Intel) user, I would be happy to help you test but I don't know how to trace the events."
1716434,2019-03-27 12:02:00 UTC,A quicker fix for people might just be to use:
1716434,2019-03-27 09:47:41 UTC,"Yes, it sounds like a good theory that COGL_FRAME_EVENT_SYNC/COGL_FRAME_EVENT_COMPLETE are missing/invalid in hybrid/PRIME setups. Someone should test that. Maybe me when I get time :)"
1716434,2019-03-27 09:37:19 UTC,"Leo, I can confirm that setting __GL_MaxFramesAllowed=1 also mitigates gnome-shell freezes in startup animations. The icon zoom animation would sometimes freeze for some seconds when starting an application from the dash. Just as additional info."
1716434,2019-03-27 01:32:37 UTC,Although not entirely the same.
1716434,2019-03-27 01:22:15 UTC,"The fix in comment 81 sounds the same as what this does:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/281"
1716434,2019-03-26 21:13:58 UTC,"Interesting, so GNOME is also affected by this glXSwapBuffers misimplementation?
Furthermore, setting this environment variable also fixes some big freezes that I had with GNOME Shell (or Mutter ?) 3.32."
1716434,2018-10-26 03:38:36 UTC,"Maik,"
1716434,2019-03-27 13:58:55 UTC,"@Maik I think you should also try with or without PRIME Synchronisation, just in case."
1716434,2019-02-28 21:20:50 UTC,"Ok, nvidia driver 418.43, gnome-shell 3.31.91 + mutter 3.31.91 freshly built without any additional patches.
Running only glxgears in a small window, not anything else open, not touching anything, gnome-shell cpu usage spikes to 85%."
1716434,2019-02-01 01:58:32 UTC,"And remember, this bug is about high CPU only. Other issues should not be discussed here."
1716434,2018-12-04 11:46:44 UTC,Correction: Please DON'T note if the bug affects Xorg or Wayland sessions.
1716434,2018-12-04 10:22:04 UTC,"For those of you who still find reverting commit 383ba566bd7c2a76d0856015a66e47caedef06b6 helps to reduce CPU, can you please note the Nvidia driver version you are using? I've tested some theories today and retested drivers 340 and 390 but can't find any problem. Or at least can't find any problem that's unique to Nvidia."
1716434,2018-11-27 04:03:20 UTC,Just a reminder to all:
1716434,2018-10-26 08:29:43 UTC,"PS:
Daniel, in general I completely agree with you, curently mutter uses too many glFinish and glxWaitVideoSync which are both blocking. The prop. driver to my knowledge needs exactly one glFinish per frame for proper operation so my idea was about using that as efficiently as possible.
A web-search trying to re-find the mentioned article brought up that many gl devs were hitting the same behaviour of the prop. driver and used the same solution I was thinking of.
I didn't look into why mutter uses glxWaitVideoSync so often to wait a little here, wait a little there."
1716434,2018-10-26 07:59:21 UTC,"Thank you, Daniel. This specific info destroys my idea:

> Moving GL commands into a new thread is non-trivial (you need to manually set
> up the context so that the commands will work)
"
1716434,2019-03-26 10:17:37 UTC,"https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-KDE-High-CPU-Fix
gnome-shell-3.32.0+mutter-3.32.0
Setting __GL_MaxFramesAllowed=1 returns cpu usage to normal when running glxgears or opening the bluetooth pane. Mystery solved?"
1716434,2019-02-28 21:23:55 UTC,Even just the small circle animation in the g-c-c bluetooth pane puts gnome-shell to constant 85% cpu usage.
1716434,2019-03-27 14:03:31 UTC,"With glxgears, I get spikes up to 3% without moving the mouse and 4% while moving the mouse. This is a massive improvement (mr281 + mr363). My desktop feels very fast!"
1716434,2019-03-27 14:16:21 UTC,"PRIME Sync on/off changes:
__GL_MaxFramesAllowed=1 unset:
g-c-c bluetooth animation - 85% -> 30%
dragging windows - 85% -> 40%"
1716434,2019-06-07 19:48:24 UTC,Closed via https://gitlab.gnome.org/GNOME/mutter/merge_requests/363
1716434,2019-06-03 17:23:17 UTC,"Tested mutter 3.32.2 +MR281+520+576(-1Hunk)+602 on the single gpu system, runs fine. No noticeable issues until now. Due to the removal of threaded wait moving windows is also back to normal/expected cpu usage now."
1716434,2019-05-31 15:33:54 UTC,"I now tested on my Optimus system using PRIME sync with __GL_MaxFramesAllowed unset using mutter/gnome-shell-3.33.2+MR602.
The good news is, while previously MR363 had no effect on CPU usage while constantly rendering on this system, MR602 now fixes it. CPU usage on bluetooth-pane circle is ~12%.
The bad news, unrelated to this bug is that without setting __GL_MaxFramesAllowed=1 on PRIME sync, mutter is stuttering and intermittently freezing. Let alone still being laggy with or without that setting."
1716434,2019-05-31 11:12:29 UTC,"Nevermind, didn't get that MR602 includes MR363."
1716434,2019-05-31 11:04:48 UTC,"Thanks again, Daniel.
Unfortunately, I'm unable to apply MR602, tried mutter 3.32.2+MR363, mutter 3.33.2+(rebased)MR363 and mutter-HEAD+(rebased)MR363
Any prerequisite I'm missing?"
1716434,2019-05-31 08:33:45 UTC,"And an extra, final nail in the coffin for this bug:"
1716434,2019-04-12 03:17:14 UTC,My mistake. If you ever do experience the problem fixed by:
1716434,2019-04-04 01:29:51 UTC,Maybe I need to provide a backport for older mutter releases?
1716434,2019-04-04 01:28:39 UTC,"Thanks, that is very encouraging because mr216 would explain the root cause here, and why the bug randomly affects some Nvidia systems sometimes and not others."
1716434,2019-04-03 10:21:15 UTC,"Daniel, re-reading your comment, I think I might have misunderstood you. So I now restested the following setup:
Single GPU, mutter-3.32+mr216 only (mr363+mr281 left out)
I can confirm that this setup also fixes this specific bug ( High cpu while constant rendering) but only this. (mr363 also fixes high cpu on mouse movement.)"
1716434,2019-04-03 09:27:26 UTC,"Of course, this is now mutter-3.32.0+mr216+mr363+mr281."
1716434,2019-04-03 09:20:20 UTC,"Just to put it straight:
- mr363 fixes this bug on single GPU systems
- mr363 does not have any effect on hybrid GPU systems using PRIME sync
- __GL_MaxFramesAllowed=1 is a workaround on PRIME systems currently."
1716434,2019-04-03 08:45:08 UTC,Random thought: This might be the real root cause:
1716434,2019-03-28 01:46:02 UTC,"I almost forgot, dragging windows is extra expensive with the Nvidia driver:"
1716434,2019-03-28 01:41:29 UTC,"Maik,"
1716434,2019-03-27 20:51:31 UTC,"On the desktop system with single nvidia gpu, I can only second Hussam: it's a blast when using mutter-3.32 plus both patches. Snappy, fast, great user experience.
Great work Daniel, thank you.
In the prime sync case, mutter obviously somehow derails taking different code paths."
1716434,2019-03-27 15:02:15 UTC,"Now applied mr363+mr281, results are mixed:
Desktop:
g-c-c bluetooth animation - 85% -> 9% Good!
dragging windows - 85% -> 75% slightly better"
1716434,2019-03-27 14:00:39 UTC,"With mr363 and mr281 (minus the first commit of 281), moving the mouse spikes the CPU up to 3% and then settles down. dragging windows around spikes CPU usage up to 10% but then immediately goes back to 0% once the dragging stops."
1716434,2018-10-25 10:08:19 UTC,"(In reply to Daniel van Vugt from comment #62)

> This bug should not be about general Nvidia performance when the original
> reporter was citing a specific commit.
>
> I am analysing the performance of Nvidia right now, and certainly it is not
> good. But if we're no longer talking about commit
> 383ba566bd7c2a76d0856015a66e47caedef06b6 then this bug should probably be
> closed and replaced with new more current bug reports.
"
1716434,2017-05-18 16:24:19 UTC,"Hi, I'm a Manjaro user. I was redirected to here from Manjaro Forum and I think I have the issue explained here, and if it's true, I have something to add."
1716434,2018-04-16 03:19:25 UTC,See also bug 1764137.
1716434,2018-08-15 04:53:13 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1716434,2017-05-12 12:55:30 UTC,"The nvidia changelog says:
""Disabled OpenGL threaded optimizations by default, initially enabled in 378.09, due to various reports of instability.""
Could this be related?"
1716434,2017-05-12 12:26:57 UTC,"(In reply to Peet from comment #10)

> I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and
> latest mutter release the high cpu usage is finally gone. Also the
> animations are back to normal as in having very smooth animations and window
> movements, whatever. I am not sure if it's the NVIDIA release or mutter
> which has included a fix but I would assume that NVIDIA has somehow fixed
> the locking issue.
"
1716434,2017-05-12 01:44:53 UTC,I use the nvidia-340.102 legacy drivers which is up-to-date.
1716434,2017-05-12 01:17:09 UTC,"(In reply to Frank from comment #11)

> (In reply to Peet from comment #10)
> > I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and
> > latest mutter release the high cpu usage is finally gone. Also the
> > animations are back to normal as in having very smooth animations and window
> > movements, whatever. I am not sure if it's the NVIDIA release or mutter
> > which has included a fix but I would assume that NVIDIA has somehow fixed
> > the locking issue.
>
> The update to mutter-3.24.2 (ArchLinux) has not resolved the issue for me.
"
1716434,2017-05-12 00:05:39 UTC,"(In reply to Peet from comment #10)

> I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and
> latest mutter release the high cpu usage is finally gone. Also the
> animations are back to normal as in having very smooth animations and window
> movements, whatever. I am not sure if it's the NVIDIA release or mutter
> which has included a fix but I would assume that NVIDIA has somehow fixed
> the locking issue.
"
1716434,2017-05-11 23:01:04 UTC,"I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and latest mutter release the high cpu usage is finally gone. Also the animations are back to normal as in having very smooth animations and window movements, whatever. I am not sure if it's the NVIDIA release or mutter which has included a fix but I would assume that NVIDIA has somehow fixed the locking issue."
1716434,2017-05-07 10:00:50 UTC,"Same for me, this is a really annoying issue."
1716434,2017-05-03 02:06:35 UTC,"(In reply to Frank from comment #7)

> I've been experiencing sluggish animations in gnome-shell after updating to
> v3.24.1 on ArchLinux on my laptop with dedicated Nvidia GPU (NVS 5100M); no
> integrated GPU is present.
>
> The previous Gnome version did not show this behaviour.
>
> I reverted the commit:
> https://git.gnome.org/browse/mutter/
> commit?id=383ba566bd7c2a76d0856015a66e47caedef06b6
> as mentioned by somebody on the Arch Forums and this fixed the issue for me.
"
1716434,2017-05-03 01:51:44 UTC,I've been experiencing sluggish animations in gnome-shell after updating to v3.24.1 on ArchLinux on my laptop with dedicated Nvidia GPU (NVS 5100M); no integrated GPU is present.
1716434,2017-04-29 18:44:20 UTC,I am seriously wondering why no devs have noticed this yet. This bug seems to affect literally everyone who uses an NVIDIA gpu.
1716434,2017-04-28 17:39:11 UTC,"(In reply to Maxim from comment #4)

> I make a screenshot of cpu usage before and after  applying
> Call-coglxlibrenderersetthreadedswapwaitenabled.patch
> http://storage4.static.itmages.ru/i/17/0411/h_1491948046_9928347_1598f98b62.
> png
>
>
> I also noticed that this patch have improved responsiveness when moving
> windows. But now, the animations of the Gnome Shell to lag even more. Now
> without the load on the CPU, the decrease in FPS became visible. This is all
> tested on a proprietary Nvidia + 650GTX.
"
1716434,2017-04-27 22:18:42 UTC,"I make a screenshot of cpu usage before and after  applying
Call-coglxlibrenderersetthreadedswapwaitenabled.patch
http://storage4.static.itmages.ru/i/17/0411/h_1491948046_9928347_1598f98b62.png"
1716434,2017-04-27 18:44:19 UTC,I have also encountered this issue on the Nvidia proprietary driver. Reverting the patch fixes the problem.
1716434,2017-04-27 18:36:03 UTC,"I can also confirm this issue, gnome-shell hits around 80% CPU usage on one core when running glxgears, It also causes stuttering in all games I have tried as well. Reverting the patch mentioned by Hussam brings the CPU usage back down to normal levels."
1716434,2017-04-27 13:46:22 UTC,I forgot to mention that I had asked a nvidia developer about this and he said it was due to the overhead of many xlib calls.
1716434,2017-04-27 13:41:23 UTC,"As per bug 779039#c14, this checkin https://git.gnome.org/browse/mutter/commit/?id=383ba566bd7c2a76d0856015a66e47caedef06b6 makes gnome-shell use ~80% cpu of one core out of 4 (I am running a skylake corei5) constantly when running something like glxgears."
1716434,2017-05-12 16:25:39 UTC,This is was my recent upgrade:
1716434,2017-05-12 16:31:07 UTC,Not resolved for me too.
1716434,2017-05-12 12:58:30 UTC,"(In reply to alecdc272 from comment #14)

> (In reply to Peet from comment #10)
> > I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and
> > latest mutter release the high cpu usage is finally gone. Also the
> > animations are back to normal as in having very smooth animations and window
> > movements, whatever. I am not sure if it's the NVIDIA release or mutter
> > which has included a fix but I would assume that NVIDIA has somehow fixed
> > the locking issue.
>
> The Mutter 3.24.2 and Nvidia 381.22 updates have not fixed the issue for me
"
1716434,2017-06-08 00:27:26 UTC,"Well, yeah, my next GPU is definitely not going to be an NVIDIA card (GTX 1060 6GB). The linux drivers are buggy as hell. But yeah, you can't really compare the performance to Intel HD Graphics or the recent AMD gpus, so I guess I am stuck here."
1716434,2017-11-06 01:56:06 UTC,"Alexandre,"
1716434,2017-11-03 18:27:54 UTC,This one makes my brand new ThinkPad P51 ridiculously slow. Just sayin' :)
1716434,2017-09-11 18:28:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716434,2017-07-30 21:33:55 UTC,"So, nobody in the GNOME community is able to do something for a such obvious performance issue?"
1716434,2017-07-20 03:54:51 UTC,"Confirmed here too on two different computers with Gnome 3.24.3 on Fedora 26/Linux 4.11 + NVIDIA 381.22 (GTX 560 and GTX 760), i also tried with NVIDIA 375.66 in the same computers and see the same lag after updated to Gnome 3.24."
1716434,2017-05-12 16:36:04 UTC,"I am not sure if this can make a difference but, @Léo could you try using nvidia-dkms instead of the nvidia package?"
1716434,2017-06-07 21:04:27 UTC,"(In reply to Peet from comment #30)

> @Hussam Al-Tayeb Did you get any response from NVIDIA?
"
1716434,2017-05-28 06:59:41 UTC,"Unless anyone has an objection, I am going to email NVIDIA with a link to this bug report (as there is obviously a bug in the driver causing this)."
1716434,2017-06-07 20:53:01 UTC,@Hussam Al-Tayeb Did you get any response from NVIDIA?
1716434,2017-05-19 19:17:29 UTC,"Well, I think I'm following now the correct bug: https://bugzilla.gnome.org/show_bug.cgi?id=781799"
1716434,2017-05-19 11:38:11 UTC,"(In reply to Eduardo Medina from comment #23)

> It seems the problem is systemd-coredump, it appears with a high CPU usage
> more or less in the same times than GNOME Shell crashed.
"
1716434,2017-05-19 11:08:14 UTC,"I see, I'm collecting all data I can to fill another bug."
1716434,2017-05-19 10:40:22 UTC,That's definitively a different issue. This bug is about high CPU usage cause by mutter/gnome-shell on Nvidia GPUs.
1716434,2017-05-19 10:34:19 UTC,"Created attachment 352150
CPU log from Eduardo Medina's old Toshiba laptop"
1716434,2017-05-18 17:54:25 UTC,"(In reply to Eduardo Medina from comment #20)

> Well, the problem I have is sometimes the environment crashes randomly. It
> recovers perfect after crashing, but when the bug occurs is very annoying.
>
> I couldn't catch any log or message to know what is the exact error, the
> only thing I have clear is the bug runs always when I have an amount of
> windows spreaded through some virtual desktops.
>
> Yes, the bug occurs on Mesa too if it's the same problem I'm responding.
"
1716434,2017-05-18 16:37:36 UTC,"I forgot to say that Wayland looks much more stable than Xorg, but the bug happens on both servers."
1716434,2017-05-27 14:16:17 UTC,Maybe a9f139cab66b532e83fca31d35f01b1b5650ca24 to 383ba566bd7c2a76d0856015a66e47caedef06b6 can be reverted? They are supposed to help in NVIDIA's situation but ended up causing more issues. And it was verified that reverting helps.
1716449,2020-09-14 10:02:10 UTC,Closing because INVALID: Can't replicate.
1716459,2018-09-19 16:27:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716460,2017-09-13 02:30:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716464,2018-03-16 18:37:57 UTC,"Worth a try - however, with the upgrade I got rid of the keystone database which had to be recreated from scratch. One of the items in the old database has been that I had doublettes of endpoints in it from previous upgrades. Might be that the cleanup of the databases contributed to the issue resolution too ...."
1716464,2018-03-16 16:44:47 UTC,"Dr. Hardewig,"
1716464,2019-10-28 19:22:12 UTC,Closing this issues Dr. Hardewig I am going to close this please feel free to re-open
1716464,2018-03-16 16:02:03 UTC,Updated to Openstack Queens
1716464,2018-03-16 19:12:58 UTC,"> however, with the upgrade I got rid of the keystone database which had to be recreated from scratch. One of the items in the old database has been that I had doublettes of endpoints in it from previous upgrades. Might be that the cleanup of the databases contributed to the issue resolution too
"
1716464,2018-01-04 08:38:35 UTC,"I double checked this issue from current Queen and last Pike, and I couldn't reproduce the error on my envrionment."
1716464,2017-10-19 15:04:54 UTC,Here we are:
1716464,2017-10-19 13:51:05 UTC,"I just tried this on a recent DevStack build and I couldn't reproduce the error. If you can get the error again, could you try running the command with --debug to see some more detail? Thanks!"
1716464,2018-01-04 21:24:42 UTC,I just updated to the most recent 1.17.1 Version of manila client - its directly for the ubuntu repository and - sorry to say - the error still persist
1716479,2021-02-13 00:17:20 UTC,I tested a little more after reading Beth's note.
1716479,2021-02-12 22:06:51 UTC,"Tested during Feedback Fest using terran-testbox.gapines.org
Authority Linker is now working as expected."
1716479,2021-02-12 22:10:00 UTC,I tested on Terran's https://terran-testbox.gapines.org/ server for both Z39.50 Edit then Import view and the Merge marc editor
1716479,2019-08-29 01:23:34 UTC,This is still happening in master as of today.  Note that it also affects the merge interface in record buckets:
1716479,2017-12-05 14:57:55 UTC,Note: this bug also affects Webby.
1716479,2019-09-11 19:16:49 UTC,Confirmed this behavior still exists in the 3.2.8 web client.
1716484,2017-09-11 20:18:03 UTC,I'm afraid I can't reproduce this issue (neither on Windows 7 nor on Windows 10).
1716484,2017-09-11 20:19:48 UTC,"To get an idea what might be going wrong one could set a new custom shortcut pressing ""Ctrl + D"" and see if the shortcut is properly set up (i.e. if Inkscape actually uses that combo)."
1716488,2017-09-11 20:41:04 UTC,This is intentional to provide hierarchical information.  We could try to do that in other ways...
1716488,2017-09-11 20:54:55 UTC,Hmmmm...I think I may have an old mock-up lying around with suggested improvements. I'll see if I can dig it up and post it.
1716488,2017-09-16 19:59:15 UTC,"The problem with using this approach for hierarchical information is that it looks like libraries with short names are subsidiaries of libraries with long names.  In the attached screenshot, for example, it really looks like Scio is a subsidiary of Albany."
1716488,2017-09-27 14:01:49 UTC,Here is the mockup we created a while ago to improve alignment and display of Holdings View.  I'm not sure how doable it is.
1716488,2019-03-07 18:48:50 UTC,"For anybody that takes this on, I wanted to pass along the WAI-ARIA authoring practices for Treegrids, which seem like a good way to measure the usability and accessibility of any hierarchical Holdings View design."
1716488,2020-01-31 22:14:14 UTC,Another bug that makes moving entirely to the web client problematic so trying to revive it since nothing has happened in two years.
1716488,2020-01-31 23:10:48 UTC,I think this is tackled in the new Angular Holdings View (https://bugs.launchpad.net/evergreen/+bug/1821382).
1716507,2018-01-25 09:38:47 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3740
1716508,2017-10-19 21:09:36 UTC,the issue is in the limba code
1716508,2018-03-06 19:45:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716508,2017-09-11 22:13:55 UTC,"StacktraceTop:
 g_main_loop_is_running (loop=0x1) at ../../../../glib/gmain.c:4130
 li_manager_bus_vanished (connection=<optimized out>, name=<optimized out>, mgr=<optimized out>) at ./src/li-manager.c:153
 do_call (client=client@entry=0x7f374444b400, call_type=call_type@entry=CALL_TYPE_NAME_VANISHED) at ../../../../gio/gdbusnamewatching.c:219
 call_vanished_handler (client=client@entry=0x7f374444b400, ignore_cancelled=0) at ../../../../gio/gdbusnamewatching.c:245
 call_vanished_handler (ignore_cancelled=0, client=0x7f374444b400) at ../../../../gio/gdbusnamewatching.c:243"
1716510,2017-09-12 17:54:05 UTC,Possibly a duplicate of:
1716510,2017-09-12 18:51:29 UTC,Ok. It looks like EDK was added to my distro and using it fixed it - https://packages.gentoo.org/packages/sys-firmware/edk2-ovmf (at least W16 - I'll try W10 tonight).
1716510,2020-10-07 18:50:52 UTC,"Since this seems to be fixed when using EDK, I'm marking this ticket as Fix Released"
1716512,2017-10-27 13:26:22 UTC,I came across this while researching a different issue.  I'm not sure why additional information has not been requested here.  And I'm not really a bug manager either.
1716512,2017-11-08 18:52:39 UTC,Hi Brynn.
1716539,2017-10-04 01:59:23 UTC,"Some initial work has landed, but I'd say it's incomplete:
1) does not create database, users, grant privileges; and possibly
2) only creates a single data source in the main org"
1716549,2019-08-28 21:44:28 UTC,Basically this is a problem with systemd-logind that effects any process that wants to run past what should be a SIGHUP.
1716549,2018-08-13 03:32:42 UTC,"Just tested this again, and it's still happening as of 5.125-0ubuntu1 in Ubuntu 18.04.1. Here are the steps I used just now to reproduce:"
1716549,2018-08-12 14:47:10 UTC,"Hmm, this is high priority bug, but unfortunately I'm unable to reproduce it..."
1716549,2018-07-19 19:02:20 UTC,"does this manifest by when you connect to a ssh server with byobu running (and has existing tabs and stuff) , it seems to randomly just 'reset' and you lose all your open tabs and scrollback? This has been happening to me for several major versions and is currently happening in the latest version in ubuntu artful and it makes it pretty much impossible to rely on byobu"
1716550,2017-10-07 00:41:48 UTC,"This was basically bug 1190879.  Individual archive/suite pairs that were last published before that fix landed will vary depending on the exact way the upload happened, but everything after that should consistently have the stronger hashes.  Unfortunately with the current architecture republishing all old PPAs would be extremely expensive - it would be much worse than https://www.chiark.greenend.org.uk/~cjwatson/blog/re-signing-ppas.html, which was just about re-signing Release files."
1716550,2017-10-07 00:43:26 UTC,"(I've triaged this as Low not because I don't think strong hashes are important - I do - but because it only affects suites last published over four years ago, and because the cleanup work for those would be very arduous and difficult to prioritise over other things.)"
1716567,2019-06-13 03:01:25 UTC,"Since the structure of snap based checkbox has changed, suggest closing this bug as most generic jobs have been moved to checkbox/checkbox18 and are automatically included alongside project providers."
1716567,2019-06-13 06:49:34 UTC,"I agree, thanks Kristin"
1716570,2019-12-11 01:55:59 UTC,"Aah, I finally learned the trick to making it work."
1716570,2019-03-28 06:32:29 UTC,"In versions before 0.92, there was no option to set the line spacing.  (Try using version 0.91, if you're curious.)  The line spacing was automatically set, I assume relative to the font size, although I don't really know how it was accomplished."
1716570,2019-03-26 05:50:09 UTC,"Hi, line spacing should be set as a multiplier of the font size by default. Is this not the case, or is there a problem with the way this is one?"
1716579,2018-01-26 11:35:26 UTC,"This happend to me _three_ times in the last week, gnome-software runs amok and takes up 16GB ram + 16GB Swap and managed to write a 13.7GB-14.3GB syslog. Couldn't view the syslogs, but there is a comment in another bug-thread on the same issue with info from syslog: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/comments/12"
1716579,2017-12-18 10:45:02 UTC,SSD Kingston V300 60Gb. Dell Optiplex 755
1716579,2017-09-19 09:45:51 UTC,"It happened again just now. From the trace it looks like it was when I searched for ""gedit"" in the overview - which has a snap result AFAIK."
1716579,2017-12-18 10:38:47 UTC,https://www.facebook.com/groups/GNU.Linux.deb.ua/permalink/1213411782124847/
1716579,2017-09-13 10:13:26 UTC,Is there any possibility that the snapd socket closed? I have found a bug in snapd-glib where it continuously reads the socket when it closes.
1716579,2017-09-12 09:40:32 UTC,"It's not really useful assigning the bug to Robert without knowing what went wrong, because there's no information to go on for fixing it."
1716579,2017-09-12 06:02:03 UTC,Confirmed by several users.
1716579,2017-09-17 06:23:47 UTC,Not only CPU. It (very) quickly skyrocket RAM memmory usage until system completely slow down and eventually running out of RAM.
1716585,2017-09-12 06:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1716585,2017-09-12 19:23:46 UTC,You may need to run the following from a terminal:
1716585,2017-09-12 21:02:55 UTC,I tried to run the comands but unsuccessfully.
1716605,2018-06-07 09:33:08 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/502960"
1716605,2017-11-30 07:21:48 UTC,My guess is that the patch has not caught the attention of relevant persons yet.
1716605,2017-11-29 20:51:39 UTC,Any particular reason the patch for this didn't get merged yet?
1716605,2017-09-12 11:30:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/502960"
1716607,2019-05-17 09:12:56 UTC,Fixed here: https://gitlab.com/inkscape/inkscape/commit/0f11301d961d0ccfea3c09b14cad2d354c0c39ab
1716635,2017-09-15 02:54:00 UTC,"Stefan:
Certification and regression test results should be valid with the previously
uploaded kernels. We will sync results from current to new tracking bugs."
1716635,2017-09-17 04:10:05 UTC,cert does not support precise 3.13
1716635,2017-09-18 10:58:27 UTC,The package has been published and the bug is being set to Fix Released
1716639,2020-05-27 03:21:22 UTC,"I see this on Ubuntu 18.04 as well, but I have a gnome-based gui that works.  Here's my log snippet:"
1716639,2018-07-05 22:19:02 UTC,"Same here. Ubuntu 18.04 on Dell E7440.
I was forced to switch to switch to lightdm, because gdm3 simply won't start."
1716639,2017-11-28 07:29:24 UTC,Same issue on Ubuntu 17.10 on a Lenovo B50 10.
1716639,2017-10-25 21:28:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716639,2017-09-12 09:54:16 UTC,Using gdm instead of lightdm produces a similar issue.
1716639,2017-10-25 21:34:38 UTC,I see the same issue on Ubuntu 17.10 on a Dell XPS 9530.
1716640,2017-09-13 04:37:32 UTC,Fixed in revision 1269.
1716641,2019-09-26 11:02:00 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1716641,2019-09-28 06:14:31 UTC,"You guessed right, I could resolve it. Anyway, thanks for your help."
1716644,2017-09-16 09:07:08 UTC,precise is not supported by cert EOL.
1716644,2017-09-18 06:59:42 UTC,"3.2.0-131.177 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1716644,2017-09-18 10:32:42 UTC,The package has been published and the bug is being set to Fix Released
1716651,2017-11-24 15:03:04 UTC,"By default I think it makes sense to have cirros have a well known user-name and password.
I'm not opposed to the suggestion of having it generate a random one or disable password auth entirely."
1716651,2017-11-24 15:17:29 UTC,"Note that 'a' is probably possible right now via 'sed' editing of /etc/shadow.
Just adding an 'x' to the password field (2nd field) would do it, or deleting that field entirely or making it a '*'.  Anything not a valid 'crypt()' is going to result in no long."
1716651,2017-11-24 08:56:05 UTC,Having a fixed username/password combination in cirros is a feature that is used in various automated testing setups. Having a random password would make this much more complicated.
1716655,2017-09-12 14:49:41 UTC,"Hi,"
1716673,2017-11-13 04:17:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1716673,2017-09-12 13:30:10 UTC,This change was made by a bot.
1716673,2017-09-12 19:22:09 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1716673,2017-09-13 06:45:56 UTC,The bug is not fixed there.
1716673,2017-11-13 21:35:53 UTC,"Sorry but there still is no driver for the PCIe Facetime camera, neither within the kernel or as a loadable module."
1716673,2017-11-13 22:00:06 UTC,This change was made by a bot.
1716675,2017-09-12 13:23:19 UTC,my graphics card is a gtx 1060 6gbs btw
1716681,2017-09-29 07:56:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716681,2018-05-31 06:33:38 UTC,It's also affected on Queens version
1716688,2018-04-11 01:13:18 UTC,"I get this error as well. Nothing in particular seems to trigger it - my Gnome session just crashes. Sometimes while I'm working, sometimes while I've stepped away from my laptop."
1716688,2017-09-17 16:00:40 UTC,Unfortunately I can't.
1716688,2018-05-13 22:07:20 UTC,same for me on bionic
1716688,2017-10-19 19:43:41 UTC,I got this error by doing nothing in particular. I was just checking Facebook on Google Chrome when the error message popped up. Sadly I had just made a fresh install of Ubuntu 17.10 and then installed a lot of metapackages which I need to work.
1716688,2017-09-12 14:41:20 UTC,"StacktraceTop:
 JSAutoCompartment::JSAutoCompartment (this=0x7fc1d57f94b0, cx=0x556e1130a550, target=0x0) at ./js/src/jsapi.cpp:719
 gjs_callback_closure (cif=<optimized out>, result=0x7fc1d57f9910, args=0x7fc1d57f9770, data=0x556e11ceb180) at gi/function.cpp:211
 ffi_closure_unix64_inner (closure=0x7fc214000410, rvalue=0x7fc1d57f9910, reg_args=0x7fc1d57f9860, argp=0x7fc1d57f9930 ""\020\071+\334\301\177"") at ../src/x86/ffi64.c:670
 ffi_closure_unix64 () at ../src/x86/unix64.S:229
 g_task_return_now (task=0x7fc1dc2b3910) at ../../../../gio/gtask.c:1145"
1716688,2017-09-22 06:48:39 UTC,I did switch from gnome into unity and it reproduced.
1716688,2017-09-12 18:56:19 UTC,Thanks for your report. Can you provide steps to reproduce this issue?
1716688,2017-09-22 07:03:53 UTC,Do you have a script or a set of commands that you're running in gjs and would trigger this bug?
1716690,2017-12-26 22:05:31 UTC,I am also having this problem... thanks for the ARandR tip. Anything one have anything more permanent?
1716690,2017-12-28 19:45:19 UTC,"SOLVED: @Manu I did find the problem.
Somehow, and I'm not sure which process triggered this but in my /home/'your username'/.config/autostart folder there was an arandr?.desktop file.  (not sure the exact filename but delete or stow away in trash anything with arandr"
1716690,2018-03-24 00:07:18 UTC,"Ran in the same problem:
- bad file is named 'cinnamon-settings-daemon-xrandr.desktop', deleting this solved the issue.
- System is Linux Mint 18.3 Cinnamon 64-bit
- Graphics Intel Sky Lake integrated with two monitors"
1716690,2018-03-28 18:58:11 UTC,"Thank you Jesse!!
I had the same problem after a freeze, deleted the file and all good to go now. Thanks again!!
(Now if someone could just fix the random 18.3 Cinnamon random freezes....!!!!!!!!!)"
1716690,2018-07-12 19:30:18 UTC,"I found that enabling ""Cinnamon Settings Daemon - xrandr"" in ""Startup Application"" Fixes this BUG."
1716690,2019-02-20 08:17:20 UTC,"As Charles said re-enabling ""Cinnamon Settings Daemon - xrandr"" in ""Startup Application"" is fixing this bug."
1716690,2020-11-27 08:04:46 UTC,"Thank both Jesse and Charles, for their suggestion.
Both procedure are fixing this bug."
1716691,2017-09-12 16:12:20 UTC,There seems to a problem if a folder is clicked on while the information overlay (at bottom right) is still working (spinner active); this click seems to be ignored/lost. The folder only opens in another column  if you click when the overlay has finished working.
1716706,2019-01-04 18:06:15 UTC,I think https://blueprints.launchpad.net/nova/+spec/count-quota-usage-from-placement will also inadvertently resolve this bug.
1716706,2017-12-05 09:27:44 UTC,"Reviewed:  https://review.openstack.org/515631
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f49ec409fd8fe2dc38d2978255c68850c427f94a
Submitter: Zuul
Branch:    master"
1716706,2018-08-02 17:59:32 UTC,"This bug came up again on an internal bug at my organization, so I took another look at this again."
1716706,2017-12-11 21:24:45 UTC,"Reviewed:  https://review.openstack.org/525511
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=43dbbf8d877124145b277129cbb8a12a7a0e7a0d
Submitter: Zuul
Branch:    stable/pike"
1716706,2017-10-24 17:57:57 UTC,"@Zhenyu Zheng I am wondering if you are still working on a fix for this one? If not it might be good to drop the ""Assigned to"" bit. Many thanks."
1716706,2017-12-05 09:28:51 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/525511"
1716706,2017-09-13 18:28:09 UTC,"This is a script that can be used to recreate this. Pass in the number of instances you want, I used 30 and had one instance go over the quota limit and fail the recheck in conductor."
1716706,2017-09-12 16:08:19 UTC,"We should be able to easily count build_requests in the API DB and include those in the count for instances, but the API also checks cores/ram when counting instances and we don't have that information in the build_request (well, we do, but it's in the serialized build_requests.instance field, which can't be queried via SQL)."
1716706,2017-09-13 19:07:56 UTC,Bug 1717000 is the issue putting the instance into ERROR state mentioned in comment #4.
1716706,2017-09-12 16:22:52 UTC,melwitt made a good point that we'd still have to deal with avoiding a duplicate count of build_requests and instances regardless of the call from the API or conductor:
1716706,2017-09-12 16:20:07 UTC,"The other thing we have to handle here is if we count build_requests, we have to avoid double counting where the build_request and instance exist at the same time, which we know is the case when we recheck quota in conductor (after the instances are created in the cells but before the build requests are deleted). So only the API service can count build_requests *and* instances in cells, but conductor can only count instances in cells."
1716708,2017-09-13 07:31:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1716708,2017-09-13 07:33:18 UTC,Seems like it has been reported upstream on https://bugzilla.gnome.org/show_bug.cgi?id=771918
1716708,2018-12-12 15:42:41 UTC,see also https://bugzilla.gnome.org/show_bug.cgi?id=744079
1716709,2017-09-12 18:46:59 UTC,Installing the HWE kernel onto the neutron-gateway and nova-compute fixes the issue.
1716709,2017-09-14 14:37:39 UTC,I think this is where we are:
1716709,2019-03-20 15:58:01 UTC,I haven't had time to check if this is still an issue. If someone else is hit by it please update the bug with additional info.
1716709,2019-05-20 04:17:25 UTC,[Expired for Ubuntu Cloud Archive because there has been no activity for 60 days.]
1716711,2017-09-12 17:56:59 UTC,This can sometimes occur when previous ceph cluster data is left behind in /var/lib/openstack-helm from previous instantiations of ceph.  The authentication details from the prior the ceph installs can hang around preventing the osd from registering with the monitors.
1716712,2017-10-05 17:00:59 UTC,perhaps this is related to not openstack-doc-tools but openstackdocstheme.
1716712,2017-09-12 18:52:04 UTC,"This is a problem with the presentation of the horizon documentation on the docs site, rather than a problem with the horizon documentation.  Assigning to openstack-doc-tools"
1716721,2017-09-13 05:25:37 UTC,"I think heat is sending 'gateway_ip': None in the request, but neutron is ignoring it."
1716721,2017-09-23 18:22:14 UTC,"This is caused by a neutron subnetpool and gateway implementation.
The easiest way to reproduce is: ""neutron -v subnet-create --no-gateway --use-default-subnetpool net3"" or use compatible osc command."
1716721,2017-09-23 18:22:56 UTC,Marking this as High because the behavior is different from CIDR and subnetpool and this is confusing.
1716721,2017-11-04 22:09:32 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1716721,2017-11-04 22:09:46 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/507350
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1716721,2019-07-04 08:42:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669107"
1716721,2019-12-04 08:49:09 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1716721,2019-12-04 08:49:19 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/669107
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1716724,2017-09-12 19:35:35 UTC,"Further investigation shows it's a byte-order-mark ("""" in ANSII)"
1716724,2020-09-12 20:47:51 UTC,Closing because INVALID.
1716724,2017-09-12 19:42:22 UTC,"P.S. I'm not sure if a BOM is allowed (or reasonable) in attribute values, but at the very least Inbkscape could stop rewriting it."
1716724,2017-09-12 19:30:01 UTC,"It almost had me fooled but it seems to be a Photoshop issue after all:
While the attribute begin="""" looks empty there is already some kind of special character in the original file!"
1716724,2017-09-12 18:16:51 UTC,"As per https://www.w3.org/TR/SVG/implnote.html#ErrorProcessing , ""The document shall be rendered up to, but not including, the first element which has an error. """
1716724,2017-09-12 18:41:37 UTC,"Yes, before seeing the comments I have just seen that removing that <?xpacket?> part corrects the issue, I will check if it's Photoshop who is putting this or Inkscape..."
1716724,2017-09-12 17:57:21 UTC,"I spoke to soon:
It's actually sufficient to remove the (illegal?) UTF-8 character in the ""begin"" attribute of that ""xpacket""."
1716724,2017-09-12 17:53:04 UTC,"Well, the attached file is invalid (and doesn't render in Firefox either)."
1716724,2017-09-12 18:59:54 UTC,"Ok, so what happens is that Photoshop adds the `xpacket` tags, but when Inkscape saves it, it's modified and Inkscape adds the invalid character."
1716732,2017-09-15 04:15:47 UTC,"I agree...
Although I had several bootstraps taking very long (20+ mins) because of my poor connection. I think if there was a timeout, it would have surprised me :) I mean I wanted to bootstrap no matter how long it took."
1716732,2017-09-17 05:48:16 UTC,"Even in the case of 20min you'd probably like some sort of indication that
things are working. If it is uploading (juju agent) we should be giving
progress around that."
1716735,2017-09-12 21:26:48 UTC,"Note that if newer HWE kernels are in use, this workaround is not required as the tunables for Jewel are supported from 4.5 onwards - so this only impacts the release 4.4 kernels."
1716735,2017-11-08 05:53:03 UTC,I didn't realize this bug was open and raised bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728739 against the Ubuntu kernel and have submitted a backport https://lists.ubuntu.com/archives/kernel-team/2017-November/087984.html.
1716747,2017-10-25 10:42:48 UTC,Thanks so much for working on this. I am unable to install 17.10 as a result of this bug.
1716747,2017-10-25 15:50:43 UTC,"@Albert and Jay, are you still seeing this bug with the latest release of Artful?"
1716747,2017-10-26 07:56:34 UTC,"Hello,
I think I have this bug (see syslog extract) with a lenovo t470, ubuntu 17.10, kernel 4.13.4 and 4.13.9
With 17.04 Gnome +  kernel 4.13.4, I've never encountered these crash during three weeks. And since having upgraded to 17.10, two crashs in two days.
It seems to occurs when the screen is locked (maybe during sleep). When I'm away from keyboard. But not systematically. No usb peripherals are connected.
regards."
1716747,2017-10-26 16:58:34 UTC,"Joe,"
1716747,2017-10-26 19:29:31 UTC,I am still seeing this issues with 4.13.0-16. Ultimately this problem (at least in my case) seems to be a PCI express power management issue (see https://www.spinics.net/lists/linux-pci/msg64778.html).
1716747,2018-03-05 08:54:51 UTC,"@Jay, did it not exist in 4.13-0.35-generic?  This bug kind of fell of the radar for a while, but it would be good to know when it came back.  We can then bisect down the commit."
1716747,2017-10-29 22:08:01 UTC,It seems that the PCI Express card was the culprit. When I removed my PCI Express USB 3.0 card everything worked fine.
1716747,2018-03-02 20:16:18 UTC,"Joe,"
1716747,2018-07-24 09:33:06 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1716747,2017-10-23 21:01:24 UTC,"Hello Joseph, I have the same error with my Ubuntu 17.10. Syslog are full of error messages. It's almost impossible to work."
1716747,2017-10-29 18:58:57 UTC,Experiencing the same problem
1716747,2017-10-05 04:05:59 UTC,"Albert,"
1716747,2018-03-05 09:32:19 UTC,"Joe,"
1716747,2017-09-24 02:16:18 UTC,"Just a comment that I have observed this bug as well, on an X220 T.  The test kernel from comment #11 also appears to resolve the problem (so far).  I do not have any external USB controllers attached, though, so I'm not sure what the failure path was."
1716747,2017-09-12 19:00:12 UTC,This change was made by a bot.
1716747,2017-09-25 07:40:42 UTC,that's strange - could you please post the output of lspci -vt
1716747,2017-09-12 19:20:56 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1716747,2017-09-12 23:45:47 UTC,The bug is still present in the latest mainline kernel (v4.13.1).
1716747,2017-09-13 15:27:26 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the last kernel that did not exhibit the bug and the first kernel that did exhibit the bug.
1716747,2017-09-13 15:22:04 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1716747,2017-09-13 20:12:17 UTC,I have added a bug report to https://bugs.freedesktop.org/show_bug.cgi?id=102711
1716747,2017-09-18 23:16:45 UTC,Can you test the following kernel and see if it resolves this bug:
1716747,2017-09-19 04:38:35 UTC,Thank you for providing the test kernel. I am afraid this does not resolve the issue.
1716747,2017-09-21 21:13:36 UTC,I built a second test kernel.  This one with commit 8466489ef5ba48272ba4fa4ea9f8f403306de4c7 reverted.
1716747,2017-09-22 03:11:09 UTC,Thank you - now everything works perfectly well :)
1716747,2017-09-13 17:22:05 UTC,Done - the last working kernel version is 4.12.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12.7/
1716749,2017-11-01 16:35:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716749,2018-06-17 02:50:51 UTC,"Well, it's 06-16-2018 and we're up to Xubuntu 18.04 and this problem has not been addressed."
1716755,2018-06-19 06:19:51 UTC,I cannot reappear this bug:
1716759,2020-05-22 04:17:35 UTC,[Expired for caja (Ubuntu) because there has been no activity for 60 days.]
1716759,2020-05-22 04:17:35 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1716759,2017-09-13 11:53:40 UTC,"I can confirm this, and I've reproduced in Xenial."
1716759,2018-01-07 09:48:50 UTC,Also affects 17.10 final release.
1716760,2018-01-30 14:29:29 UTC,"Change abandoned by Hunt Xu (<email address hidden>) on branch: master
Review: https://review.openstack.org/539115"
1716766,2017-09-13 19:27:47 UTC,"Hi Drew, it should be possible to modify partition power with the charms today. There are some conditions that need to be met in order for it to work though. To help me figure out what's going on can you please provide the following:"
1716766,2017-09-14 16:23:29 UTC,"Ok I've had a look at the swift-proxy charm code to refresh my memory on how this is currently working and can confirm that partition power is only used by the charm the builders are first created so modifying this config option post-deployment will not have any effect. This is in fact the intended behaviour i.e. we just didn't add support for this to be changed. I assume that right now, users of this charm are manually updated the builders and re-spinning and syncing the rings manually. As previously mentioned this is not advisable since it will eventually conflict with the charms handling ring maintenance the next time it tries to update the rings in any way. So in my view the way forward is to extend what we have to be able to support updating this setting post-deployment while ensuring that we are able to do this without putting the cluster at-risk. I can see how this might seem suitable as a charm action but since the code that currently handles rings and builders is not controlled by actions (it actually pre-dates actions) and relies on charm config that actions can't set, it probably going to make most sense to extend the existing hook code. I intend to work on a patch to do this and document how it should be done so will post back once i have something."
1716770,2020-06-29 15:40:34 UTC,"@fossfreedom now that the ubuntu-budgie packageset has been created and you're on the uploaders team, can you check if any of your personal packageset packages are missing from the ubuntu-budgie packageset? And also, I assume we can remove the personal packageset, once ubuntu-budgie has all the proper packages included? Unless your personal pkgset includes non-budgie-related packages, of course."
1716770,2017-09-15 01:11:14 UTC,"> If you feel it makes more sense to name it ubuntu-budgie, I'm fine with that too.
"
1716770,2017-09-15 08:33:07 UTC,"I think in general we'd like this to be available to others as well. He applied for PPU rights for the following packages, but we anticipate more people applying for the same PPU rights in the future."
1716770,2017-09-17 15:38:21 UTC,"I think I was on vacation during the meeting where this was discussed. Is there any reason this can't be an automatically generated packageset based on the seeds, like the other flavours? If there are exceptional packages that aren't appropriate for a Budgie packageset but are appropriate and approved for fossfreedom, then we could manage just those ones as PPU."
1716770,2017-09-19 05:52:22 UTC,"On Sun, Sep 17, 2017 at 03:38:21PM -0000, Robie Basak wrote:

> I think I was on vacation during the meeting where this was discussed.
> Is there any reason this can't be an automatically generated packageset
> based on the seeds, like the other flavours? If there are exceptional
> packages that aren't appropriate for a Budgie packageset but are
> appropriate and approved for fossfreedom, then we could manage just
> those ones as PPU.
"
1716770,2017-10-24 10:55:00 UTC,"This is taking too long, fossfreedom got his application approved long ago and still didn't see his upload rights granted. I agree that we should consider creating a seed-based packageset for budgie developers but seeing that this requires some additional preparations (and that his original application was for the PPU rights, not budgie-seed ones) I would like to request that the TB creates this personal-fossfreedom packageset for now. As this is a fact - we granted fossfreedom the upload rights to the selected packages and this is irrelevant to what is the 'better solution'."
1716770,2017-10-24 19:29:53 UTC,"Thanks, with this clarification from the DMB I'm happy to go ahead with creating a PPU ACL here."
1716770,2017-10-24 20:48:45 UTC,fossfreedom clearly applied for upload rights to the Ubuntu Budgie packageset in November 2016. See
1716770,2017-10-27 14:43:55 UTC,"Hi,"
1716770,2020-07-27 15:59:05 UTC,"closing this bug as it appears everything is taken care of, @fossfreedom if there is anything else please send a new request to the dmb."
1716773,2017-09-26 14:09:50 UTC,kind of thought on this yesterday... i dont know wif 'apply_networking' actually makes sense in the network stage. kind of just to think on that.
1716773,2017-09-25 21:57:32 UTC,"An explanation of what happened here:
 a.) in local mode we did 'instancify()' which (through _reflect_cur_instance)  did a '_write_to_cache'. At this poing .network_config had never been called, so the DataSourceAzure did not have the ._network_config property set and thus not stored.
 b.) main called init.apply_network_config().  This ends up calling 'network_config' on the datasource, which sets the ._network_config.
 c.) stages exits because 'if mode == sources.DSMODE_LOCAL'"
1716774,2017-09-13 00:28:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1716780,2017-09-12 22:33:01 UTC,Are you sure you looked in the correct spot (see attachment)?
1716780,2017-09-13 01:04:10 UTC,"Also it might be docked, possibly minimized."
1716784,2017-09-12 22:29:41 UTC,From our irc discussion:
1716784,2017-10-22 04:03:09 UTC,"I'm still getting this.  I tried updating the NUC firmware where this repeats, no joy."
1716784,2017-10-22 04:32:01 UTC,I found out a trick:
1716784,2019-09-19 11:53:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1716789,2019-09-12 09:37:35 UTC,This issue was fixed in the openstack/python-openstackclient 4.0.0 release.
1716789,2017-09-14 09:43:38 UTC,"Are you using curl/shade/OSC/neutron client?
Some example would be great :)"
1716789,2017-11-10 15:08:31 UTC,"German - this looks like it's intended behavior, the help message in the openstack client actually says the default is TCP:"
1716789,2017-11-10 15:09:03 UTC,The change BTW was https://review.openstack.org/#/c/307908
1716789,2017-12-07 02:01:35 UTC,https://review.openstack.org/#/c/518954/ is the fix for this German it's just stuck in limbo.
1716789,2018-03-19 09:29:45 UTC,The issue is actually that currently it is not possible to specify 'Any' (or None) as protocol by omitting the --protocol argument (since it defaults to tcp).
1716789,2019-06-27 20:03:52 UTC,"https://review.opendev.org/#/c/518954/ has merged, changing the default back to protocol 'any'."
1716792,2018-07-27 07:54:13 UTC,This issue was fixed in the openstack/keystone 12.0.1 release.
1716792,2017-10-12 01:31:42 UTC,"Reviewed:  https://review.openstack.org/504084
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5c9ccced69a6dbf46ab4b8c8e805789b0a4c47af
Submitter: Jenkins
Branch:    stable/pike"
1716792,2017-09-14 15:38:19 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/504084"
1716792,2017-09-14 16:07:44 UTC,"This issue came up after we moved the install guides from openstack-manuals into keystone itself. Sphinx has an issue with building the navigation links when multiple pages try to reference the same one document, and the chain doesn't properly render. openstack-manuals used a custom script to fix this and we have a fix for this already on master."
1716794,2017-09-15 20:23:42 UTC,A workaround is creating an image manually[1] with the following setup before shutting down the instance.
1716794,2017-09-26 13:35:51 UTC,Discussion from the ironic boot from volume meeting last week indicated that mjturek would work on a dib element to help automate this for users.
1716794,2017-10-18 18:29:56 UTC,"No patch has been submitted for this yet, so changing status to 'Triaged'."
1716794,2017-12-11 14:31:00 UTC,"Hey Ruby,"
1716794,2018-06-15 07:38:46 UTC,"Reviewed:  https://review.openstack.org/511494
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=91e3b72a23a4bde3c811cedf2224f682aa4d99b7
Submitter: Zuul
Branch:    master"
1716813,2020-09-14 07:33:38 UTC,The problem seems to be fixed in 20.10. Not sure exactly when it got fixed.
1716813,2017-09-13 02:46:32 UTC,"I wouldn't have the tech know-how to explore if it's a 'dock/shell bug', I do see 2 things
1. happens with gnome-shell's default dock also (gnome-session
2. See this line which doesn't occur without vaapi
totem[2604]: Native Windows taller than 65535 pixels are not supported"
1716813,2018-04-08 07:43:06 UTC,"It does this with GNOME Web too, it seems (even still in Ubuntu 18.04)."
1716813,2017-09-13 02:09:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716813,2017-09-13 02:12:16 UTC,"Confirmed, but I wonder if this is a dock/shell bug. If that OpenGL window is actually the video sub-surface then the shell or dock should ideally recognise it's a child and not list it as an application window."
1716817,2018-01-25 09:38:46 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3741
1716819,2017-09-13 04:49:23 UTC,apport information
1716819,2017-09-13 14:21:31 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].
1716819,2017-10-27 09:26:19 UTC,"On 4.13.1-041301-generic, the problem persists."
1716819,2017-10-27 09:28:21 UTC,And it persists on Ubuntu 17.10.
1716819,2017-10-31 04:21:21 UTC,Try linux kernel 4.14-rc7.
1716819,2017-10-31 05:53:50 UTC,Just tried kernel 4.1.4-rc7. The issue persists.
1716819,2017-10-31 08:47:00 UTC,"So under v4.14-rc6, it can successfully suspend once, right?"
1716819,2017-10-31 11:09:53 UTC,Seems like it does (with 4.14-rc7).
1716819,2017-10-31 11:14:14 UTC,"It's actually a bit strange. If I unlock and try to suspend again, it does suspend."
1716819,2017-11-03 06:22:59 UTC,I guess you use lid to suspend the machine?
1716819,2018-01-03 04:17:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1716819,2018-01-03 09:00:07 UTC,This change was made by a bot.
1716819,2017-10-31 05:54:25 UTC,"Sorry, meant 4.14-rc7."
1716819,2017-09-13 04:49:21 UTC,apport information
1716819,2017-09-13 04:49:15 UTC,apport information
1716819,2017-09-13 04:49:16 UTC,apport information
1716819,2017-09-13 04:49:13 UTC,apport information
1716819,2017-09-13 04:49:11 UTC,apport information
1716819,2017-09-13 04:49:10 UTC,apport information
1716819,2017-09-13 04:49:08 UTC,apport information
1716819,2017-09-13 04:49:07 UTC,apport information
1716819,2017-09-13 04:49:06 UTC,apport information
1716819,2017-09-13 04:49:05 UTC,apport information
1716819,2017-09-13 04:49:03 UTC,apport information
1716819,2017-09-13 04:49:00 UTC,apport information
1716819,2017-09-13 04:48:59 UTC,apport information
1716819,2017-09-13 04:48:57 UTC,apport information
1716819,2017-09-13 04:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1716819,2017-09-13 04:49:19 UTC,apport information
1716822,2019-06-10 07:54:53 UTC,"Closing as there has been no response for 60 days. If you still have a similar issue, please file a report on our new bug tracker: https://inkscape.org/report. Thank you!"
1716822,2018-07-18 17:47:56 UTC,"Same issue for me ...
Need to restart ."
1716822,2019-03-11 02:58:55 UTC,Can't reproduce this issue with Inkscape 0.92.4 on openSUSE TW 20190301. Are you still seeing this issue with the latest Inkscape version?
1716828,2018-10-08 22:28:34 UTC,fails in --unpack
1716828,2018-10-08 22:29:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716830,2018-04-30 04:51:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716831,2017-10-30 13:47:39 UTC,what is the content of fireewall_update.yaml?
1716832,2017-09-13 08:29:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1716834,2018-08-11 16:52:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/591161"
1716834,2018-08-21 13:18:14 UTC,"Reviewed:  https://review.openstack.org/593629
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=364b8155000be4a5d00e5fd483185908d1090f8f
Submitter: Zuul
Branch:    stable/rocky"
1716834,2018-09-06 08:07:57 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/503539
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1716834,2018-08-20 14:24:11 UTC,"Reviewed:  https://review.openstack.org/591161
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=9fbdc81038d13864c9280102c6a357e29f259ac5
Submitter: Zuul
Branch:    master"
1716834,2018-08-20 14:05:36 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/593629"
1716834,2018-08-20 14:03:15 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/593629"
1716834,2018-08-11 16:48:10 UTC,"After merging https://review.openstack.org/543231, bug 1786628 happens."
1716834,2018-02-04 14:58:35 UTC,@Marek Lyčka: are you still working on this bug ?
1716834,2018-06-26 10:53:47 UTC,"Reviewed:  https://review.openstack.org/575073
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=1ca8555011ad345e6343eded2fcca4516aa70944
Submitter: Zuul
Branch:    master"
1716834,2018-06-13 10:40:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/575073"
1716834,2018-06-13 10:23:45 UTC,"Reviewed:  https://review.openstack.org/543231
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=e5dae9b35349c53fa6184e415e254094893cab1f
Submitter: Zuul
Branch:    master"
1716834,2018-02-11 14:55:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543231"
1716834,2017-09-13 06:32:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503539"
1716834,2018-07-26 21:20:27 UTC,This issue was fixed in the openstack/horizon 14.0.0.0b3 development milestone.
1716845,2017-09-13 13:28:57 UTC,Can you explain a bit more? Why would the image of the server be deleted?
1716845,2017-09-14 01:55:15 UTC,"For step 2 we create the snapshot for the stack, create images for the two servers ('external_ser' and 'th_server'), when we delete the stack, the snapshot image of 'th_server' be deleted as expected,see the code:
https://github.com/openstack/heat/blob/master/heat/engine/stack.py#L1926-L1940"
1716845,2017-09-14 05:57:06 UTC,"IMO we should not even snapshot an external resource when doing a stack snapshot, as it's not managed by heat."
1716845,2017-09-14 06:32:17 UTC,"@Rabi Mishra,
In fact this bug is not related with the 'external' resource, just my template with it. If you remove a normal server resource, the bug is still happen. Of course, I think you mentioned another bug: don't snapshot an external resource when doing a stack :)"
1716845,2017-09-14 06:39:40 UTC,I register a bug https://bugs.launchpad.net/heat/+bug/1717178
1716845,2017-09-14 07:24:45 UTC,I have modified the bug description to use the normal resources.
1716845,2017-09-18 07:09:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/504862"
1716846,2017-09-13 07:47:47 UTC,One method would be rendering the defined repositories under sources.list.d and trusted.gpg.d respectively and render those again whenever the config optionsa are changed.
1716846,2017-09-13 11:54:59 UTC,This likely requires pulling in the code from charm-helpers that handles this.
1716846,2017-09-13 11:55:53 UTC,"(or adding the necessary to charm-helpers, which is trickier than doing it in the apt layer)"
1716851,2017-10-02 14:25:20 UTC,"I just find that (looks same issue but with pyqt4):
https://stackoverflow.com/questions/28318309/embedding-pyqtgraph-into-tab-widget-pyqt"
1716852,2017-09-13 07:43:33 UTC,Dcraw in system is 9.21.
1716852,2017-09-19 14:45:02 UTC,I'm not able to reproduce this bug.
1716852,2017-10-02 08:11:42 UTC,"Hi,"
1716852,2017-10-04 22:10:46 UTC,Fixed in revision #1283.
1716857,2019-06-21 03:02:42 UTC,"just one last thing, possibly you are not aware that 19.04 Ubuntu wayland
sessions have exactly the same problem: no external monitors. While this
bug refers to Xorg, the problem is not limited to Xorg. At least on my
Optimus laptop. And when I use its multiplexor to go into pure Nvidia mode,
no monitors work, not even the laptop panel."
1716857,2019-06-21 02:35:40 UTC,"Actually, maybe those other DMs don't run as root. My memory is failing. So again maybe we do want a similar workaround in gdm3. But that doesn't seem to be the root cause of the bug."
1716857,2019-06-21 02:31:34 UTC,"> If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)
"
1716857,2019-06-21 02:15:19 UTC,"I think his point was to isolate the problem as being gdm3's wayland code.
If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)"
1716857,2019-06-21 01:44:01 UTC,"Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind of pointless. It's pointless because the most common reason for using nvidia-drm.modeset=1 is to get Wayland support. I know there are other reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in PRIME setups. But mostly if people use modeset=1 it is to get Wayland support."
1716857,2019-06-20 23:35:52 UTC,"What we know about this bug is that gdm3, nvidia and modeset=1 is broken under configurations which are not broken when sddm and lightdm are used."
1716857,2019-06-21 03:18:31 UTC,"In isolation I don't think it's correct to say that Wayland sessions have ""no external monitors"". Wayland sessions do work with external monitors on the Nvidia driver if you have nvidia-drm.modeset=1. I've confirmed this on a desktop at least."
1716857,2019-06-13 09:28:30 UTC,Not yet. I am just untangling more Nvidia bugs today.
1716857,2019-06-14 02:30:47 UTC,Nvidia 430.26 behaves a bit differently. It just fails to start as non-root and gives reasons:
1716857,2019-06-13 13:44:42 UTC,"User generix reports that when gdm3 is compiled without wayland support, this bug is not seen."
1716857,2019-06-13 13:43:34 UTC,I posted here:
1716857,2019-06-20 23:36:51 UTC,"""gdm3 compile without wayland"", I meant"
1716857,2019-06-24 04:43:54 UTC,"Being duped here with a more specific bug, i.e
19.10
optimus hardware
No login to ubuntu session possible with gdm, lightdm is ok"
1716857,2020-05-03 13:15:12 UTC,"Hi, thanks to everyone, especially Daniel for unpacking this issue."
1716857,2019-09-28 00:44:41 UTC,"And PS: workaround continues to be: use lightdm, a five minute fix at worst."
1716857,2019-10-05 16:27:22 UTC,Jeremy Soller's fix to edit Xwrapper seems to be good.
1716857,2019-11-03 05:16:40 UTC,"I just installed popOS 19.10 an an Optimus laptop, nvidia option. Out of the box you get gdm3 and tear-free prime-sync; it uses Jeremy Soller's solution (root rights granted in Xwrapper)"
1716857,2020-02-22 20:35:26 UTC,I confirm Xwrapper root rights worked for me too.
1716857,2020-02-27 21:10:44 UTC,"This bug persists in 20.04 daily.
The one-line Pop!OS solution (https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26) works, just logout and login."
1716857,2020-03-02 16:15:23 UTC,I think forcing all users (even on systems that don't use the NVIDIA driver) to run X with root privileges would be a little heavy-handed.
1716857,2020-03-02 16:32:59 UTC,"Is it a kernel, systemd or Nvidia issue to get the right device nodes exposed here?"
1716857,2020-03-05 09:02:13 UTC,"@Alberto, couldn't prime-select do this when going into hybrid or Optimus mode? Only users with nvidia hybrid graphics would go down this logic path, and they are only ones who need the fix (but only if they are using gdm3, sddm and lightdm continue to be unaffected by this)"
1716857,2020-04-07 10:48:13 UTC,"I've added systemd to the bug because that seems to be involved in device permissions, as well as proving useful in the above comments."
1716857,2020-05-03 13:40:23 UTC,"Apologies, continuing the comment above (mistakenly posted when adding the log attachment). Let me retry."
1716857,2020-05-03 13:41:59 UTC,Here's the script I run to workaround the intital failure of gnome to use the external display after unlocking or resuming from DPMS suspend/off.
1716857,2020-05-03 14:23:00 UTC,"Another correction. For the one workaround, switching to discrete graphics in the BIOS only seemed to get past the initial gnome login. But resuming from DPMS off/suspend, the same error loop happens even when hybrid graphics is disabled in the BIOS."
1716857,2019-06-13 09:27:28 UTC,I will post your findings to the nvidia developers forum.
1716857,2019-09-28 00:37:49 UTC,19.10 beta and nvidia drivers 430 and 435 have the same problem. I have made the bug title correctly specific.
1716857,2019-06-13 09:22:05 UTC,"Hi Daniel, thanks for not forgetting about this, unlike everyone else :)
Have you communicated this observation to Nvidia at all?"
1716857,2020-07-14 07:30:01 UTC,Test on Intel Tiger Lake platform with nvidia dGPU (N17S-G5 PCI\VEN_10DE&DEV_1C94).
1716857,2019-06-13 09:16:27 UTC,"For a full list of reasons to not use nvidia-drm.modeset=1 right now, please see:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset"
1716857,2017-12-13 03:26:29 UTC,Celebratory fireworks from me.
1716857,2017-12-13 06:45:14 UTC,"Tim, are you really saying just that one-line change fixed it?..."
1716857,2017-12-13 06:50:21 UTC,Actually the offending line is directly from Debian: http://http.debian.net/debian/pool/main/g/gdm3/gdm3_3.26.2.1-2.debian.tar.xz
1716857,2017-12-13 07:10:54 UTC,"Let me clarify: the problem exists in Fedora too. Until a few hours ago, I
had never got prime sync and gdm3 working in any distribution.
This one line fix works, believe it or not. It's really a half a line fix.
I have only tried it in ubuntu 17.10 so far. Fedora is not a focus for me,
and I have other problems with nvidia binary support on Fedora 27. The
learning curve for Fedora is steep for me so I am not motivated to
investigate it."
1716857,2017-12-17 00:12:25 UTC,"Daniel, yes that one line fixes the bug. It's not a proper fix but a work-around for GDM3."
1716857,2017-12-17 00:45:48 UTC,"However with this change I'm seeing very long pauses on restart/shutdown, i haven't found any iclue why in the logs."
1716857,2017-12-29 22:43:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716857,2018-04-20 01:46:01 UTC,"Same on Thinkpad P51 (Nvidia Quadro M2200), Ubuntu 18.04, Nvidia 390"
1716857,2018-04-20 02:48:40 UTC,I re-confirm this. Stock 18.04 has no graphics in pure nvidia mode (on a Thinkpad W520 in discrete graphics).
1716857,2018-09-14 08:28:52 UTC,"The current 18.10 nvidia packages have this problem too. That is, out of the box, the nvidia driver defaults to KMS now (first time on any distro) but the nvidia driver does not detect external screens. Probably should be a new bug I guess."
1716857,2018-12-18 03:04:20 UTC,18.10 Lightdm works but GDM works only with the mentioned hack/workaround (but with slowdowns):
1716857,2019-01-03 13:56:25 UTC,"sddm works too: I just put kde plasma on my ThinkPad P50 with ubuntu 18.10, it works well."
1716857,2019-01-16 23:20:01 UTC,"Same issue in here on Ubuntu 18.04.1 LTS. I have a Dell G3 3579 with Nvidia Geforce 1050TI. I've tried to use a Samsung SmartTV as a secondary display connected to HDMI port but Gnome settings only shows laptop display. I've tested drivers 390, 396, 410, and 415 without success. This issue doesn't occurs using lightdm instead of gdm3.
I think developers have to solve this issue that has been reporting since 2017-09-13 and people who wants do use a external HDMI TV/Monitor to play games, like me, will face this issue."
1716857,2019-02-14 08:34:33 UTC,"Running Ubuntu 18.10 here. Wanted to do a presentation with my Notebook, but it failed me cause of this bug.
I can confirm that it works ""Out of the box"" with lightdm and that it also works with gdm3 if you modify /lib/systemd/system/gdm3.service, changing the ""ExecStartPre"" line to the above mentioned: ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config"
1716857,2019-02-20 21:35:51 UTC,Yes but this workaround is going to create others issue for suspend and resume.
1716857,2019-02-20 22:24:48 UTC,"There are two workarounds mentioned: swap to lightdm and manipulate gdm3
start. I think you refer to the gdm3 startup changes when you say it causes
problems with suspend/resume (which I didn't try).
The other workaround is changing display manager to lightdm (or sddm, the
KDE display manager).
swapping to lightdm has not caused any suspend/resume problems for me on
the two Optimus laptops I used,  so I think the lightdm workaround is ok.
It was the default display manager of ubuntu for a long time and is still
the default for xubuntu."
1716857,2019-02-20 22:36:04 UTC,Yes I was talking about the gdm3 workaround
1716857,2019-02-21 01:41:37 UTC,The problem with the lightdm workaround is that many had this cursor issue:
1716857,2019-02-21 03:12:50 UTC,"Personally, I have not encountered that when using ubuntu or fedora and
simply swapping gdm3 for lightdm but it's good that the other bug report
has a fix. It looks like a hidpi bug; none of my monitors are hidpi."
1716857,2019-03-21 10:21:36 UTC,"I confirm the bug exists and workarounds work, both with lightdm and ExecStartPre line. Also, adding xinit to ExecStartPre messes up suspend functionality. That is a pity..."
1716857,2019-03-21 10:22:49 UTC,Forgot to add: Ubuntu 18.04.2
1716857,2019-03-25 07:00:08 UTC,"After adding the line ""/usr/bin/xinit"" to gdm3.service I get this in every boot:"
1716857,2019-04-21 23:21:12 UTC,"Still present in 19.04, although as a workaround, the nvidia drivers have reverted to installing without modeset=1, so external monitors work, and Optimus users get dreadful tearing on their laptop's internal screen."
1716857,2019-04-22 22:23:12 UTC,I'm on Ubuntu 19.04 as well and having issues with this.
1716857,2019-05-15 17:40:31 UTC,"The solution to this is to run X11 as root, so it can use VGA arbiter and detect displays on both the NVIDIA and modesetting drivers."
1716857,2019-05-15 21:29:32 UTC,This works. Thanks. What does gdm3 do that requires this?
1716857,2019-06-13 09:11:29 UTC,"In a more pure development environment, I can confirm this bug without needing hybrid GPUs, or gdm3."
1716857,2017-12-13 02:51:51 UTC,"ubuntu user Hon Weng Chong has emailed me as he continues to investigate the problem.
He believes he has proof that it is is GDM configuration issue and has provided the following fix"
1716857,2019-06-13 09:21:12 UTC,"Also, it sounds like the root cause here is the same as bug 1769857."
1716871,2017-09-24 13:42:04 UTC,I tested in our production environment and it works fine. I'll try a comple more times in devstack and see how it goes.
1716877,2017-09-15 19:39:31 UTC,Were you installing from the latest point release of 16.04?
1716877,2017-10-06 10:49:19 UTC,I've verified this on current ubuntu-16.04.3-server-amd64.iso (SHA1=f3532991e031cae75bcf5e695afb844dd278fff9)
1716877,2017-12-06 04:17:20 UTC,[Expired for debian-installer (Ubuntu) because there has been no activity for 60 days.]
1716878,2018-07-26 02:58:56 UTC,"Change abandoned by fupingxie (<email address hidden>) on branch: master
Review: https://review.openstack.org/546877"
1716878,2018-02-22 06:25:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546877"
1716878,2017-12-07 16:14:03 UTC,"Adding a node here for other people looking, this bug is for the case when:"
1716878,2018-02-22 07:10:10 UTC,"Change abandoned by fupingxie (<email address hidden>) on branch: master
Review: https://review.openstack.org/511422"
1716878,2017-10-12 14:00:55 UTC,I'm a bit lost here only one conductor should manage node at a time unless `hash_distribution_replicas` is set to non default value which is experimental.
1716878,2017-10-12 08:33:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511422"
1716878,2017-10-13 06:54:34 UTC,"@Vasyl, here is my config:
[DEFAULT]
auth_strategy = keystone
enabled_drivers = pxe_ipmitool
my_ip = 10.127.2.41
transport_url = rabbit://openstack:Abc12345@10.127.2.146
enabled_network_interfaces = neutron
default_network_interface = neutron
debug = True
use_stderr = False
hash_distribution_replicas = 3
[agent]
deploy_logs_local_path = /var/log/ironic/deploy
deploy_logs_collect = always
[amt]
[api]
port = 6386
api_workers = 5
enable_ssl_api = True
[audit]
[cimc]
[cisco_ucs]
[conductor]
api_url = https://10.0.202.41:6386
automated_clean = False
[console]
[cors]
[cors.subdomain]
[database]
connection=mysql+pymysql://ironic:Abc12345@10.127.2.146/ironic?charset=utf8
[deploy]
default_boot_option = local
[dhcp]
[disk_partitioner]
[disk_utils]
[drac]
[glance]
auth_url = https://10.127.2.146:35357
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = glance
password = glance
glance_host = $my_ip
glance_cafile=/etc/ironic/ssl/ca.crt
glance_protocol=https
glance_api_insecure=False
[iboot]
[ilo]
[inspector]
enabled = false
auth_url = https://10.127.2.146:35357
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = ironic_inspector
password = 123456
[ipmi]
[irmc]
[ironic_lib]
[iscsi]
[keystone]
[keystone_authtoken]
auth_url = https://10.127.2.146:35357
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = ironic
password = Abc12345
cafile=/etc/ironic/ssl/ca.crt
[matchmaker_redis]
[metrics]
[metrics_statsd]
[neutron]
auth_url = https://10.127.2.146:5000
cafile = /etc/ironic/ssl/ca.crt
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = neutron
password = neutron
provisioning_network_uuid =  8d5a74b3-3c43-46a2-a7de-0d5eb3d152c3
cleaning_network_uuid =  8d5a74b3-3c43-46a2-a7de-0d5eb3d152c3
[oneview]
[oslo_concurrency]
[oslo_messaging_amqp]
[oslo_messaging_notifications]
[oslo_messaging_rabbit]
amqp_durable_queues = True
[oslo_messaging_zmq]
[oslo_policy]
[pxe]
tftp_server = 10.0.202.41
images_path = /opt/imagecache/images
instance_master_path = /opt/imagecache/master_images
image_cache_size = 500
image_cache_ttl = 10080
pxe_append_params = nofb nomodeset vga=normal ipa-debug=1 ipa-insecure=1 coreos.autologin console=tty0 console=ttyS0,115200n8
[seamicro]
[service_catalog]
auth_url = http://10.127.2.146:35357
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = ironic
password = Abc12345
[snmp]
[ssh]
[ssl]
cert_file = /etc/ironic/ssl/server.crt
key_file = /etc/ironic/ssl/server.key
[swift]
[virtualbox]
You have new mail in /var/spool/mail/root"
1716879,2017-09-20 16:32:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505710"
1716879,2017-10-24 14:17:25 UTC,I uploaded two screen shots. The one with-patch.png is after the proposed patch is applied and the other (latest-master.png) is when using the latest master.
1716879,2017-11-08 15:08:24 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/505710
Reason: This patch doesn't fix issue in a right way. I'll post more details in launchpad"
1716879,2017-11-08 15:11:07 UTC,"The issue is how MS browsers render fonts inside SVG. We use fontwaesome package for icons on network graph panel. Because different icons have a different width, we can't create a generic solution for it w/o vertical alignment support from browsers."
1716884,2017-09-13 09:52:45 UTC,"Looks like the issue starts when connect a USB wifi dongle (based on ath9k_htc).
After a fresh NetworkManager restart, journalctl shows that USB device is enumerated periodically, and for some reasons, failed to be configured correctly."
1716887,2017-09-15 04:39:40 UTC,"I believe this stems from a time before Azure Resource Manager update which allowed more flexible setting of IP ranges. I don't think there is any specific reason why we couldn't allow users to specify an existing subnet range anymore, just historical baggage and not having the time to come back and clean this one up."
1716887,2017-11-07 03:45:50 UTC,Space and subnet work across providers is on the roadmap for 18.04
1716887,2020-10-09 18:47:02 UTC,"Azure provider now supports spaces. So you can use a space constraint to provision instances to specific subnets. It's also now possible to provision a machine with multiple NIC, depending on how the constraint is specified (see juju spaces doc)."
1716890,2018-09-13 11:11:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/602296"
1716890,2017-09-21 06:50:15 UTC,I also observed it
1716894,2019-09-19 11:59:36 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1716895,2017-11-05 10:53:47 UTC,"In some other soft they colorize the background color of the drop target, which is conveniently obvious.I´d prefer it over a tiny mouse pointer."
1716895,2018-01-31 13:10:02 UTC,"As a first step we could extend the tooltips of artist & title items like this. Currently they have the 'dropTracksHere' string attached, so something like the following would make sense:
""You can drag title/artist to other decks, samplers, as well as drop it into playlists and crates"""
1716898,2017-09-13 11:46:31 UTC,This problem was apparently caused by the combination of running Ubuntu in Virtualbox and trying to apply GUI settings (either through Tweak Tool or the System Settings > Appearance panel) with a dual screen setup. After closing my laptop screen this started working.
1716903,2017-09-20 15:04:00 UTC,"Reviewed:  https://review.openstack.org/503601
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=062f5b2e876a09119e43c1905f91610cd4e5d015
Submitter: Jenkins
Branch:    master"
1716903,2017-09-20 17:19:04 UTC,"Reviewed:  https://review.openstack.org/505285
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a9f9e70dd08295618731445f38af2031adc859f1
Submitter: Jenkins
Branch:    stable/pike"
1716903,2017-09-19 14:12:01 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/505285"
1716903,2017-10-24 12:42:41 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1716903,2017-09-25 14:27:41 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1716903,2017-09-15 18:27:34 UTC,The reason the live migration CI job didn't catch this is that it doesn't test microversion >= 2.34 which changes to use the live_migrate_instance method. If the microversion < 2.34 it uses the migrate_server method which has the @targets_cell decorator.
1716903,2017-09-14 09:32:25 UTC,Is your super conductor nova.conf configured to hit the [api_database]?
1716903,2017-09-14 07:31:33 UTC,Sorry for the lack of information I given.
1716903,2017-09-13 19:05:17 UTC,Is your super conductor nova.conf configured to hit the [api_database]?
1716903,2017-09-13 19:04:47 UTC,"This needs more details. When we lookup the instance in the API we target the context to the cell that the instance is in, and then that context is used when the API calls conductor so we should be fine, plus we have live migration CI tests which are not failing, so this seems invalid."
1716903,2017-09-13 15:17:20 UTC,https://review.openstack.org/#/c/503601
1716903,2017-09-15 01:51:15 UTC,"BTW, Without the @targets_cell decorator:
1. (before casting)API context.db_connection in api is **cell1** db connection.
I print api context before casting:
context.db_connection._root._root_factory.__dict__ ==>'connection': u'mysql+pymysql://root:1@127.0.0.1/nova_cell1"
1716904,2017-09-14 09:34:13 UTC,"Did another round of testing:
(sha256sum verified)"
1716904,2017-09-14 11:27:16 UTC,"Sorry about that, it seems stable in both the 14/09/2017 and the beta1. (iso was written poorly to usb)"
1716909,2019-09-25 09:54:05 UTC,"Active/active is supported via coordination since rocky, more flexible config available in stein."
1716909,2018-09-28 11:13:19 UTC,"Hi, any update on this bug?"
1716909,2019-04-08 09:50:56 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/510566
Reason: Very old"
1716909,2019-06-19 02:23:49 UTC,"https://review.opendev.org/#/c/608511/
Active/active is now supported.
active/passive should be using pacemaker."
1716921,2017-09-14 13:11:57 UTC,This bug was fixed in the package gnome-shell - 3.25.91-0ubuntu5
1716924,2018-04-06 13:54:35 UTC,"I have pushed cxlflash 5.0.2669-0ubuntu1~test1 to the earlier PPA for a test-build. The rename of libcflsh to libcxlflash is acceptable, so I did that in the version I prepared, although I preferred the former as usually it's good if the library binary package name corresponds to an soname. Of course in this case we have bundled many libraries into one binary package so the binary name doesn't matter so much."
1716924,2018-04-05 15:31:45 UTC,"------- Comment From <email address hidden> 2018-04-05 11:26 EDT-------
I published a new release which removed the debian files, and has a couple of minor fixes."
1716924,2018-04-04 19:44:29 UTC,"On Wed, Apr 04, 2018 at 06:44:24PM -0000, Breno Leitão wrote:

> I was able to talk to Mike and he is OK with most of the changes, we
> just need two minor fixes, if possible:
"
1716924,2018-03-28 14:53:47 UTC,"Locally I only tested source-package builds and those worked fine. But as seen in the test-package PPA the package seems to build fine on bionic:
https://launchpad.net/~sil2100/+archive/ubuntu/cxlflash/+build/14497603"
1716924,2018-03-30 15:20:43 UTC,"------- Comment From <email address hidden> 2018-03-30 11:14 EDT-------
https://github.com/open-power/capiflash/releases
5.0.2663"
1716924,2018-03-29 22:00:23 UTC,"------- Comment From <email address hidden> 2018-03-29 17:56 EDT-------
I pushed the 5.0.2663 level to github with the libcxlflash chgs. Pls review for 18.04 inclusion. thx."
1716924,2018-03-28 22:10:26 UTC,"------- Comment From <email address hidden> 2018-03-28 18:08 EDT-------
5.0.* is the latest dev, and it needs to be in 18.04. That update comes when I push these packaging changes, very soon.
I have the new packaging working, and it built in my PPA."
1716924,2018-04-06 16:01:34 UTC,"------- Comment From <email address hidden> 2018-04-06 11:54 EDT-------
you are correct, cxl_flash_vm does not belong. I removed the file, pushed that commit to github, and re-released 5.0.2669."
1716924,2018-04-04 18:44:24 UTC,"I was able to talk to Mike and he is OK with most of the changes, we just need two minor fixes, if possible:"
1716924,2018-04-10 06:54:38 UTC,"It has been validly pointed out to me by a fellow archive-admin that the current cxlflash sources seem to ship a non-free license in src/build/install/resources/license/ of the tarball contents. This can cause some legal confusion, as the sources are apparently Apache 2.0."
1716924,2018-05-14 17:15:12 UTC,"changed title to 18.10, according to targetmilestone change after comment #39"
1716924,2018-04-11 08:23:26 UTC,"This might be problematic in that case. The license that the user is asked to accept when running one of the cxlflash scripts seems to be written in a way that makes the resulting binaries no longer Apache 2.0 licensed. I am not a licensing expert, but when users need to accept a license that seems to prohibit the user of using the 'Program' with any other hardware, as well as seemingly limit the ability to redistribute or modify (and others), the resulting software doesn't seem to be free software anymore. For us to consider the package and its binaries being Apache 2.0 would mean the binaries being licensed in the same (or compatible) way. I might be reading this wrong, but the shipped license files do not seem to address the 'hardware usage' but the ""Program"" usage - which I guess in this case would mean the binaries that are present in cxlflash. Although I might be misunderstanding something."
1716924,2018-04-11 19:30:52 UTC,"------- Comment From <email address hidden> 2018-04-11 15:28 EDT-------
We agree that multiverse works."
1716924,2018-04-11 20:10:47 UTC,"For either universe or multiverse, we need a clear debian/copyright that explains what the user's rights are on the software.  Currently the packaging declares an Apache license, but it's not clear that these are the rights that the user has on this software; the EULA imposes other conditions and asserts that they are binding by simply downloading or installing the package.  So what are the effective license terms of this software?"
1716924,2018-04-11 20:18:32 UTC,"Also, in the course of digging deeper into the EULA handling (in the hopes of finding a path by which this could still be accepted into universe), I noticed that the maintainer scripts for this package (postinst) use 'mv' to stow the libraries into a directory outside of the linker path until the license is accepted.  This isn't an acceptable technical mechanism from the point of view of distribution integration.  Preferred technical mechanism would be either:"
1716924,2018-04-11 22:40:38 UTC,"------- Comment From <email address hidden> 2018-04-11 18:30 EDT-------
-Replacing the current EULA handling with a EULA prompt before install sounds great.
-The thought of a developer removing a EULA prompt from a package sounds very strange."
1716924,2018-07-02 13:50:38 UTC,Marking as incomplete until the EULA handling is resolved.
1716924,2018-07-31 17:01:05 UTC,"Hi,"
1716924,2019-02-21 00:29:48 UTC,"------- Comment From <email address hidden> 2019-02-20 19:22 EDT-------
I will close this bug - the utility won't be needed now.  If it's needed in the future we'll still need to address the IBM EULA issue."
1716924,2019-02-21 06:53:19 UTC,Thanks Michael. I'll close this bug out. Please reopen if it's required in the future.
1716924,2018-04-10 16:10:46 UTC,"------- Comment From <email address hidden> 2018-04-10 12:06 EDT-------
The license agreement is used when a customer has purchased and installed our adapter card, to detail a liability and support agreement with IBM. The customer runs a configuration script after installing our adapter card, and the script has a ""click to accept"" agreement based upon the license text.
The source code itself is bound by the apache 2.0 license."
1716924,2018-03-27 22:50:20 UTC,"------- Comment From <email address hidden> 2018-03-27 18:41 EDT-------
I couldn't get the 18.04 debuild to run, it doesn't do the compile:

> fakeroot debian/rules build


dh build --with=systemd

> echo $?


0"
1716924,2017-09-21 14:19:00 UTC,"@Steve: There is an updated version (4.3.2560-1) on mentors if you would like to continue the review. I can take a look, too, if needed."
1716924,2018-03-26 16:39:29 UTC,"One question regarding the packaging itself - the description of the cxlflash package mentions cxlflashimage. I saw this package in one of the cxlflash versions in some PPA, but the main upstream tarball's debian/control does not define that binary package. Should it exist? What should be its contents?"
1716924,2018-03-27 15:30:39 UTC,"------- Comment From <email address hidden> 2018-03-27 11:22 EDT-------
The cxlflash-test and cxlflashimage packages contain binary files which are not open-source, and therefore won't be included in a linux distro."
1716924,2017-09-14 07:34:46 UTC,"Other bugs impacting the cxlflash driver have been handled by the kernel team, e.g. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702521 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605405."
1716924,2017-09-14 20:14:37 UTC,I have commented on the packaging at <https://mentors.debian.net/package/cxlflash>.  Some changes are needed before this package should be included in Ubuntu.
1716924,2017-09-14 20:43:38 UTC,"On Thu, Sep 14, 2017 at 10:14 PM, Steve Langasek
<email address hidden> wrote:

> I have commented on the packaging at
> <https://mentors.debian.net/package/cxlflash>.  Some changes are needed
> before this package should be included in Ubuntu.


...

>   RFS 870909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870909
>   package on mentors: https://mentors.debian.net/package/cxlflash
"
1716924,2017-09-14 23:55:08 UTC,*** This is an automated message ***
1716924,2017-09-18 19:29:24 UTC,"------- Comment From <email address hidden> 2017-09-18 15:22 EDT-------
Hi,"
1716924,2017-11-20 14:53:50 UTC,Updating title based on change in target release milestone.
1716924,2018-02-14 19:19:57 UTC,"------- Comment From <email address hidden> 2018-02-14 14:18 EDT-------
*** Bug 143338 has been marked as a duplicate of this bug. ***"
1716924,2018-03-07 15:40:12 UTC,"------- Comment From <email address hidden> 2018-03-07 10:30 EDT-------
I can't tell what the next step is here. What is still needed/outstanding. This is a request for 18.04 only at this point, not 17.10. Please update."
1716924,2017-09-13 18:51:08 UTC,This is a bug that should be assigned to the foundation team.
1716924,2018-03-20 18:10:21 UTC,"------- Comment From <email address hidden> 2018-03-20 14:04 EDT-------
The consumers of the shared libraries are those who purchase a compatible IBM Adapter card on an IBM POWER system."
1716924,2018-03-20 19:30:41 UTC,"My question is more about if those libraries will be linked by external programs in external Debian packages, or are only used by the binaries included in the cxlflash package. Will other packages depend/build-depend on the cxlflash package for those libraries?"
1716924,2018-03-20 20:20:12 UTC,"------- Comment From <email address hidden> 2018-03-20 16:15 EDT-------
I think you are talking about managing the library version dependencies with the library package version. Yes, external developers may use dynamic linking to our shared libraries and create their own packages. Those developers may set their package dependency to our package version."
1716924,2018-03-23 18:28:32 UTC,"In that case I am splitting out all the shared libraries into one libcflsh0 (and it's libcflsh-dev counterpart) package to make sure we have an easy way to handle ABI breakages and transitions. Normally we'd split out each library into its own package but after inspecting the source I saw that all of the generated libraries are handled by a single SOVER, so during an ABI break it would just bump the soname for all libraries anyway. After some additional minor cleanup and sanity testing I would expect it to be good to go for review."
1716924,2018-03-23 19:10:14 UTC,"------- Comment From <email address hidden> 2018-03-23 15:07 EDT-------
Since we have current customers with dependencies upon our existing package name and version, we do not like that solution."
1716924,2018-03-23 19:34:09 UTC,"> Since we have current customers with dependencies upon
> our existing package name and version, we do not like that
> solution.
"
1716924,2018-03-26 11:45:03 UTC,"It's as commented by Steve. The libcflsh0 library binary package will be automatically pulled in as a dependency of cfxflash, ensuring that people upgrading from previous PPA-based versions get the same set of runtime dependencies. The source headers have been moved to libcflsh-dev though, so for development purposes the development package should be used."
1716924,2018-03-26 15:30:22 UTC,"------- Comment From <email address hidden> 2018-03-26 11:24 EDT-------
We appreciate the effort, but changing the package names wont work for us. It would require existing customers to make changes for dependencies based on the new package names."
1716924,2018-03-26 16:35:14 UTC,"Could you explain how it will not work for you? I suspect customers are depending on the cxlflash binary package name to get the required tools and libraries, correct? If that's the case, everything should work as with the new package naming layout installing cxlflash will also automatically install libcflsh0, pulling in all the shared libraries as previously. So generally any users and their applications depending on the .so files should not see any difference, without requiring any manual intervention."
1716924,2018-03-20 17:30:12 UTC,"Hey! I am looking at the package that has been once previously submitted to Debian mentors. It looks ok, but I was wondering about the libraries that cxlflash is shipping - there seems to be a symbols file for all those that are bundled in this one binary package. Are those meant for external consumption? Usually for libraries that are to be used by external packages/applications we tend to have separate binary packages for each lib. Who would be/are the consumers of the cxlflash-shipped libraries?"
1716932,2017-09-15 04:43:05 UTC,"To get *you* connected back to the controlller, you should be able to look at ~/.local/share/juju/controllers.yaml which lists what IP address it thought the Controller was at, and you should be able to update that."
1716932,2017-09-15 05:42:58 UTC,"I believe the problem is more nefarious than that. IIANM, the issue is that the cloud definition inside the controller refers to the old IP address (it's stored in the cloud endpoint). We need a way of updating the cloud definition inside the controller."
1716932,2017-09-17 05:50:24 UTC,"Why would the controller IP be stored as information about the cloud? I
could see us storing the Host machine address so we can contact the correct
LXD agent, but likely that is just the .1 address and is unlikely to have
actually changed."
1716932,2017-09-18 03:04:13 UTC,":8443 is the LXD port. Juju is not connecting to the controller, it's connecting to LXD. The LXD host address is stored in the cloud endpoint."
1716933,2020-06-23 17:25:02 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/507034"
1716933,2018-01-22 16:20:23 UTC,"Reviewed:  https://review.openstack.org/534777
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=e27525801f2a51bc77e095693678c097b1525a87
Submitter: Zuul
Branch:    master"
1716933,2018-01-08 08:36:43 UTC,"Reduced in priority. Workaround: Use etcd with etcd pub/sub, or redis with redis pubsub."
1716933,2018-01-17 14:53:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/534777"
1716940,2017-09-13 15:09:54 UTC,"StacktraceTop:
 g_wakeup_new () at ../../../../glib/gwakeup.c:161
 g_main_context_new () at ../../../../glib/gmain.c:658
 initable_init (initable=0x5633ea0afc20, cancellable=0x0, error=0x0) at ../../../../gio/gdbusproxy.c:1938
 g_initable_new_valist (object_type=<optimized out>, first_property_name=0x7fb566249a08 ""g-flags"", var_args=0x7ffe67588850, cancellable=0x0, error=0x0) at ../../../../gio/ginitable.c:248
 g_initable_new (object_type=<optimized out>, cancellable=cancellable@entry=0x0, error=error@entry=0x0, first_property_name=first_property_name@entry=0x7fb566249a08 ""g-flags"") at ../../../../gio/ginitable.c:162"
1716940,2018-03-27 03:02:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716940,2019-04-30 15:48:51 UTC,"Is that still an issue in newer Ubuntu series?
The problem here is 'Creating pipes for GWakeup' which is sign that something on the system is leaking fds, gvfs is just hitting an error due to the lack of resources on the system so it's not really a gvfs bug (unless it's the one having the leak, but that's not likely)"
1716940,2019-05-04 11:16:00 UTC,"It is an issue for me on 18.04.2, see my recent duplicate reports."
1716940,2019-08-06 20:13:45 UTC,Upstream is here:
1716944,2017-09-13 15:56:53 UTC,I believe the behavior was chosen for backward compatibility with common idioms that were merging pathnames with system-source-directory or such.
1716944,2017-09-13 19:23:58 UTC,"I think the behavior was reasonable when we didn't have the ""slashy"" systems, but now that we do, it seems reasonable that a user would want to reference the source directory of a slashy system, instead of the parent directory where the slashy system *definition* is located together with the parent system *definition*."
1716949,2017-09-13 15:49:30 UTC,"UPDATE: I've partially solved the issue using the following command,"
1716951,2018-04-24 09:26:42 UTC,"To be more precise, at least occurring in Lubuntu."
1716951,2018-04-24 09:10:59 UTC,Same problem here for keepass2 2.36+dfsg-1 on up-to-date Ubuntu 17.10. Note that Windows key was used in combination with an arrow key to reposition the window at half width on one side of the screen. That is how to reproduce this.
1716951,2018-04-24 09:11:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716957,2020-01-01 04:17:54 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1716957,2019-11-01 14:49:26 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1716957,2017-09-18 08:24:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716963,2017-09-13 16:11:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503729"
1716963,2018-08-31 07:43:51 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1716963,2018-08-31 07:44:01 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/503729
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1716964,2017-10-05 16:57:54 UTC,This bug was fixed in the package vlan - 1.9-3.2ubuntu2.17.04.3
1716964,2017-10-05 16:25:41 UTC,This bug was fixed in the package vlan - 1.9-3.2ubuntu1.16.04.4
1716964,2017-10-05 16:25:21 UTC,"The verification of the Stable Release Update for vlan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1716964,2017-10-05 16:25:13 UTC,This bug was fixed in the package vlan - 1.9-3ubuntu10.5
1716964,2017-09-21 20:48:40 UTC,zesty:
1716964,2017-09-21 20:46:43 UTC,xenial:
1716964,2017-09-21 20:44:17 UTC,trusty:
1716964,2017-09-21 18:28:10 UTC,"Hello Juan, or anyone else affected,"
1716964,2017-09-21 18:27:13 UTC,"Hello Juan, or anyone else affected,"
1716964,2017-09-21 18:22:50 UTC,"Hello Juan, or anyone else affected,"
1716964,2017-09-21 06:22:33 UTC,"BTW it has to do with vlan (example [1][2] - just not dependent as it has use cases without vlan, never the less this shouldn't be the place where it should have been implemented in the first place. But for now this is bugfixing and not a rewrite of hwo things should be."
1716964,2017-09-20 18:58:29 UTC,This bug was fixed in the package vlan - 1.9-3.2ubuntu5
1716964,2017-09-20 16:20:37 UTC,"The attachment ""lp1716964-artful.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1716964,2017-09-20 15:09:56 UTC,After IRC discussion the answer to the non ifupdown world is that this should never have been in vlan and the fix is more to be correct on the SRU path than on the future - thanks for explaining ddstreet.
1716964,2017-09-20 14:59:42 UTC,"@paelzer re: ifupdown, the vlan package is only used by ifupdown.  How other nw management allows changing an interface's rp_filter is up to that tool, e.g. netplan or networkd, and this particular bug does apply (they may do it wrong also, but it has nothing to do with the vlan package)."
1716964,2017-09-20 14:51:56 UTC,"Sponsored the Artful upload [1], please as mentioned look into the post ifupdown world case and consider fixing vlan for that as well."
1716964,2017-09-20 14:49:57 UTC,"Well it needs ifupdown for it to work (with and without your fix).
For the fix at hand it is that is ok - no need to block this or the SRUs on that.
But add it to the steps to reproduce."
1716964,2017-09-20 14:39:59 UTC,test ppa: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1716964
1716964,2017-09-20 13:23:28 UTC,"As the comment says in the vlan if-up script, this setting has nothing to do with vlans and really should go into ifupdown itself; it makes no sense for the setting to only work if the 'vlan' package is installed (and it will work for vlan and non-vlan interfaces as long as 'vlan' is installed)."
1716964,2017-09-15 07:45:34 UTC,"@Dan - IIRC you look currently for work that is sponsored for your uploader application. This looks like a great case and more than that you did the last 6 uploads to this package so you likely have some sort of test environment already.
Would you mind picking that up?"
1716964,2017-09-15 07:41:55 UTC,"Related doc ont he parameter:
https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt"
1716964,2017-09-14 12:00:33 UTC,The following modification on /etc/network/if-up.d/ip makes it work.
1716968,2017-09-13 16:36:35 UTC,When passing a signed message in as a UTF-8 string (decoded from bytes):
1716968,2017-09-13 16:36:10 UTC,When passing a signed message in as bytes to the function in Python 3:
1716973,2017-09-29 13:14:18 UTC,"Hello Julian, or anyone else affected,"
1716973,2017-09-29 13:17:40 UTC,"Hello Julian, or anyone else affected,"
1716973,2017-11-11 19:26:38 UTC,xenial verified:
1716973,2017-11-11 19:32:46 UTC,Verified on zesty:
1716973,2018-02-14 01:05:15 UTC,This bug was fixed in the package apt - 1.2.25
1716973,2018-02-14 01:05:42 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1716976,2017-09-25 23:14:08 UTC,"Sorry, sorry, it does still happen."
1716976,2019-03-05 15:20:31 UTC,"I'm currently on 18.10 and this bug seems to have been fixed. Abam, the bug you point to does not currently happen on my system, so maybe both have been fixed in 18.10."
1716976,2019-03-05 12:22:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716976,2017-10-26 21:43:56 UTC,This is still happening with 17.10 final. I have been digging a bit and found something that makes me think that this is a caching / IPv6 issue. Attached is the screenshot of a Wireshark capture of the DNS packets on all interfaces on the affected machine (the IP address of the machine is 192.168.0.154).
1716976,2017-09-25 23:11:08 UTC,"It looks like this has been fixed, it is not occurring anymore."
1716976,2019-03-05 12:25:35 UTC,I have a the same kind of errors. DNS resolution sometimes fails due to cache issues.
1716976,2017-09-21 20:13:47 UTC,Output of systemd-resolve --status when the problem does not occur
1716976,2017-09-21 20:13:21 UTC,Output of systemd-resolve --status when the problem occurs
1716976,2017-09-19 13:04:10 UTC,"The caches should be flushed each time machine changes networking =/ does your system e.g. bounce between ""public dns wifi network"" and a ""internal dns ethernet network""?"
1716976,2017-09-13 17:14:43 UTC,"Maybe interesting: systemd-resolve --status eth2 always reports the correct, internal DNS server, even though names are incorrectly resolved to their public IPs (I tried resolving with both dig and systemd-resolve)."
1716976,2017-09-21 20:18:34 UTC,"I attached the output of systemd-resolve --status in both cases. There is no difference. In both cases it says the DNS server is 192.168.0.2 (our local resolver), although it seems it is using another, external DNS server after a while."
1716986,2017-09-14 12:59:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1716986,2017-12-15 07:29:54 UTC,"@sebastien,"
1716986,2017-12-15 17:22:12 UTC,"@ventrical, it's:
/usr/share/unity-greeter/unknown_badge.png"
1716993,2017-09-14 07:27:10 UTC,I assume you're talking about the website? I've forwarded this to our webmaster.
1716993,2017-10-30 10:43:50 UTC,"I assume this is solved now? If not, please let us know."
1716993,2017-10-30 12:34:40 UTC,"Hello,"
1717000,2017-10-24 12:42:45 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1717000,2017-09-19 18:53:54 UTC,"Reviewed:  https://review.openstack.org/504178
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9cddde1f9775847d4b6671595dfc5c4b1bc8e718
Submitter: Jenkins
Branch:    stable/pike"
1717000,2017-09-25 14:27:52 UTC,This issue was fixed in the openstack/nova 16.0.1 release.
1717000,2017-09-14 19:28:59 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/504178"
1717000,2017-09-13 21:42:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503839"
1717000,2017-09-15 01:50:38 UTC,"Reviewed:  https://review.openstack.org/503839
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7e02f02d1501925ddeb15266c05d4d95f852e21a
Submitter: Jenkins
Branch:    master"
1717005,2017-09-13 19:40:47 UTC,"Problem was a ""failed to upload"", because I uploaded an ubuntu1 package soon after the sync, but the bug here is that being the person who have force-syncd it, I would have expected to be emailed, not the maintainer that just uploaded it in Debian"
1717021,2017-09-13 20:23:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503802"
1717046,2018-03-15 17:59:06 UTC,"I don't recollect the failure lately, and logstash query is empty:"
1717046,2017-11-04 22:41:29 UTC,"Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/503854
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1717046,2017-11-04 22:41:16 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1717046,2017-09-19 15:33:39 UTC,"Gate failure is fixed, removed the gate-failure tag, and lowered the importance to Medium."
1717046,2017-09-15 19:26:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/504498"
1717046,2017-09-13 22:29:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503854"
1717046,2017-09-18 04:36:50 UTC,"Reviewed:  https://review.openstack.org/504498
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c56a8c1b7ef554ea93a2def2c1ffab3e82f1592e
Submitter: Jenkins
Branch:    master"
1717061,2017-09-20 09:36:43 UTC,"Fix committed into lp:miral at revision 580, scheduled for release in miral, milestone Unknown"
1717069,2020-10-15 08:47:03 UTC,"Confirmed with Casey this is no longer needed, as bundles are used for this."
1717069,2018-03-26 05:41:42 UTC,"Looks like it's happening in juju-deployer, adding it to this bug."
1717069,2018-04-04 06:12:11 UTC,"This is due to juju-deployer expecting user/password to be provided in accounts.yaml.
It should also be able to handle credentials.yaml."
1717089,2018-02-02 14:22:28 UTC,I've hit this and I'm wondering if there's a workaround for this? The PPA of charm is deprecated and it's snap only from this point and I'm looking for some path forward.
1717089,2018-03-26 06:37:58 UTC,"I could reproduce a similar issue (though not exactly the same error message):
ubuntu@epic-bear:~/spec$ mojo run
2018-03-26 06:29:57 [INFO] Using pre-existing container class lxd
/usr/lib/python2.7/dist-packages/pylxd/model.py:116: UserWarning: Attempted to set unknown attribute ""description"" on instance of ""Container""
  key, self.__class__.__name__
2018-03-26 06:29:58 [INFO] Rsyncing /home/ubuntu/spec to /home/ubuntu/.local/share/mojo/lp1717089/xenial/lp1717089/spec
2018-03-26 06:29:58 [INFO] Retrieve the spec's manifest
2018-03-26 06:29:58 [INFO] Building resource tree
2018-03-26 06:29:59 [INFO] Downloading cs:ubuntu-12 from charm store to ubuntu
2018-03-26 06:29:59 [INFO] Downloading cs:nrpe-49 from charm store to nrpe
2018-03-26 06:29:59 [ERROR] Error calling external process
Traceback (most recent call last):
  File ""/usr/lib/python2.7/dist-packages/mojo/cli.py"", line 628, in run_with_args
    args.func(args)
  File ""/usr/lib/python2.7/dist-packages/mojo/utils.py"", line 305, in wrapped
    return method(*args, **kwargs)
  File ""/usr/lib/python2.7/dist-packages/mojo/cli.py"", line 346, in run_from_manifest
    manifest.run(project, workspace, args.stage)
  File ""/usr/lib/python2.7/dist-packages/mojo/manifest.py"", line 100, in run
    auto_repo=auto_repo)
  File ""/usr/lib/python2.7/dist-packages/mojo/phase.py"", line 255, in run
    collect_success = collect_config.build()
  File ""/usr/lib/python2.7/dist-packages/codetree/config.py"", line 271, in build
    results.append(f.result())
  File ""/usr/lib/python2.7/dist-packages/concurrent/futures/_base.py"", line 405, in result
    return self.__get_result()
  File ""/usr/lib/python2.7/dist-packages/concurrent/futures/thread.py"", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File ""/usr/lib/python2.7/dist-packages/codetree/config.py"", line 115, in run_with_dependency
    return self.run()
  File ""/usr/lib/python2.7/dist-packages/codetree/config.py"", line 83, in run
    result = self.source.get(self.location, self.source_options)
  File ""/usr/lib/python2.7/dist-packages/codetree/handlers/charm.py"", line 85, in get
    if downloader.get(dest):
  File ""/usr/lib/python2.7/dist-packages/codetree/handlers/charm.py"", line 193, in get
    subprocess.check_output(cmd, stderr=subprocess.STDOUT, universal_newlines=True)
  File ""/usr/lib/python2.7/subprocess.py"", line 574, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
CalledProcessError: Command '('charm', 'pull', '--channel', 'stable', u'cs:nrpe-49', 'nrpe')' returned non-zero exit status 1
ubuntu@epic-bear:~/spec$"
1717089,2017-09-15 13:45:33 UTC,This is related to the latest charm tools snap. I'm also seeing the same when trying to build charms:
1717090,2017-12-19 20:47:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717090,2017-12-19 21:08:06 UTC,"This goes back to at least 2014.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772571"
1717113,2017-10-08 22:59:50 UTC,thunderbird builds on armhf now. s390x is the only release architecture where it doesn't build.
1717113,2018-07-15 18:05:45 UTC,"Hello Balint,
Thank you for submitting this bug and reporting a problem with building Thunderbird.  You made this bug report some time ago and there have been several versions of Ubuntu and Thunderbird since then."
1717113,2018-09-14 04:18:25 UTC,[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.]
1717113,2021-01-07 10:47:55 UTC,"This was fixed a while ago.
Note that no real testing is done on s390x as it's not a supported desktop platform, but at least the package builds there."
1717127,2020-10-13 04:17:18 UTC,[Expired for llvm-toolchain-5.0 (Ubuntu) because there has been no activity for 60 days.]
1717127,2017-09-19 14:36:21 UTC,"Hello, you should report this bug in Debian, since this package is maintained there with no Ubuntu specific changes.
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=openmprtl"
1717129,2017-10-02 04:14:59 UTC,"Hola, puedes ejecutar en una terminal OpenShot
Como el ejemplo de abajo
↓↓↓↓"
1717129,2017-10-02 05:04:23 UTC,"------------------------- ERROR 1 ------------------------------
Failed to import 'from openshot import main'
Error Message: cannot import name main
----------------------------------------------------------------
--------------------------------
   OpenShot (version 1.4.3)
--------------------------------
Adding files to the watch queue:
/home/lisette/-v
Another instance of this program is already running
lisette@PC:~$"
1717129,2017-10-02 05:05:41 UTC,"yo no soy muy experimentada en computación, disculpa..."
1717129,2017-10-15 03:11:17 UTC,Puedes publicar todo lo que te salga en la terminal hasta que cierre openshot?
1717141,2017-09-14 02:20:12 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1717143,2017-09-18 21:17:12 UTC,Closer inspection suggests that the glusterfs-common package in 16.04 doesn't have this problem...
1717147,2017-09-14 03:33:49 UTC,"Please also create a red hat bugzilla for this, and I will make sure it gets pulled in when a fix is accepted here."
1717147,2017-09-14 18:51:45 UTC,"Because $JOB has a RH support agreement, I created a support ticket (01932169).  Do you also want a public bugzilla entry created?  (Would require digging up my old RH Bugzilla creds...)"
1717147,2017-09-15 04:36:04 UTC,"This is a replicate of upstream bug
https://bugs.launchpad.net/cloud-init/+bug/1717147"
1717147,2017-09-15 14:01:51 UTC,Thanks for the good bug and root cause diagnosis.
1717147,2017-09-18 04:02:05 UTC,"Looks like a fix has been committed upstream, as noted in Launchpad at https://bugs.launchpad.net/cloud-init/+bug/1717147"
1717147,2017-09-23 02:36:02 UTC,"This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New"
1717147,2018-06-19 18:03:08 UTC,The rebase is being tracked via Bug 1525267.
1717149,2017-09-14 03:18:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503911"
1717149,2017-09-18 13:41:41 UTC,"Reviewed:  https://review.openstack.org/503911
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=fb39de18e41a5e50f7f840336429109e847c816d
Submitter: Jenkins
Branch:    master"
1717149,2017-09-20 17:49:52 UTC,This broke the unit tests of the sahara dashboard. Compare:
1717149,2017-09-21 12:51:16 UTC,This breaks sahara-dashboard gate and is reverted in https://review.openstack.org/506108
1717149,2017-10-27 00:37:30 UTC,This issue was fixed in the openstack/horizon 13.0.0.0b1 development milestone.
1717155,2019-05-10 15:53:06 UTC,-- GitLab Migration Automatic Message --
1717155,2017-09-14 03:48:37 UTC,Xwayland refresh rate reported by 'xrandr' is incorrect:
1717162,2017-09-14 17:07:27 UTC,"That is annoying.  If it were an ftp location, you could specify ""anonymous"" as the user, but smb doesn't allow for that.  I've filed a bug with gvfs upstream to ask for that feature."
1717175,2017-09-14 06:15:59 UTC,"A possibility might be to add a Region.getLastScore(), which would be available independently from the existence of a match object."
1717177,2017-09-14 06:36:18 UTC,no more comment
1717178,2017-09-14 14:47:22 UTC,"Hum, that's arguable. What's the problem with doing the snapshot?"
1717178,2017-09-18 05:00:49 UTC,"No problem, but not sure why would we do that? Should we also restore from the snapshot of an external resources? IMO, 'external' resource is not managed by heat and we don't do any manipulation of that resource in the backend service."
1717191,2018-05-14 11:03:47 UTC,This change was made by a bot.
1717194,2020-03-31 20:44:18 UTC,Confirmed this is still an issue in 3.5beta
1717194,2019-09-16 06:25:07 UTC,The bug is still valid for 3.3.2.
1717194,2018-05-23 20:11:50 UTC,Still exist in EG 3.1.1
1717194,2019-03-06 16:39:25 UTC,"The multiple sending of patron registration form values after clicking ""Back"" button is still possible (tested in the bug squashing week sandbox)"
1717195,2017-09-14 07:49:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/503989"
1717195,2020-06-25 20:18:04 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/503989
Reason: Project is going to be abandoned"
1717198,2017-10-06 15:16:08 UTC,@seb128
1717198,2017-09-14 08:34:03 UTC,"The attachment ""72_use_smaller_volume_step.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1717198,2017-09-20 08:27:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1717198,2017-09-20 10:56:45 UTC,@seb128
1717198,2017-10-06 13:51:28 UTC,where did they do recommend downstream patch?
1717218,2018-05-16 11:08:15 UTC,"I am having this same problem. I am a newbie to Linux and to computing, as a whole. Please refer to the most ""beginner-friendly"" fix/guide to this issue."
1717218,2018-02-15 22:07:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717235,2017-09-15 01:00:08 UTC,This change was made by a bot.
1717245,2017-09-25 23:45:13 UTC,"stack@linux-controller:/opt/stack/devstack> neutron port-show a416d128-ed71-493d-b6c6-b5ec1f991e71
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
+-----------------------+--------------------------------------------------------------------------------------+

| Field                 | Value                                                                                |


+-----------------------+--------------------------------------------------------------------------------------+

| admin_state_up        | True                                                                                 |
| allowed_address_pairs |                                                                                      |
| binding:host_id       | linux-controller                                                                     |
| binding:profile       | {}                                                                                   |
| binding:vif_details   | {""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}            |
| binding:vif_type      | ovs                                                                                  |
| binding:vnic_type     | normal                                                                               |
| created_at            | 2017-09-25T23:31:21Z                                                                 |
| description           |                                                                                      |
| device_id             | 7939dcb2-dacb-4901-ae58-c192c75826df                                                 |
| device_owner          | network:router_gateway                                                               |
| extra_dhcp_opts       |                                                                                      |
| fixed_ips             | {""subnet_id"": ""372dea1c-0270-42c1-b1c4-71739b4434a5"", ""ip_address"": ""192.168.60.18""} |
| id                    | a416d128-ed71-493d-b6c6-b5ec1f991e71                                                 |
| mac_address           | fa:16:3e:a6:90:4e                                                                    |
| name                  |                                                                                      |
| network_id            | 8d78fded-aa91-4b46-92fe-64173f8947fe                                                 |
| port_security_enabled | False                                                                                |
| project_id            |                                                                                      |
| revision_number       | 6                                                                                    |
| security_groups       |                                                                                      |
| status                | ACTIVE                                                                               |
| tags                  |                                                                                      |
| tenant_id             |                                                  ...
"
1717245,2017-09-26 03:11:37 UTC,It seems the tenant_id is intentionally not set here. [1]
1717246,2017-10-06 22:55:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717246,2018-02-03 17:11:01 UTC,"C61 [GeForce 7025 / nForce 630a] ""Proprietary, tested"" driver allows hardware acceleration in Chrome browser"
1717248,2017-09-14 13:38:46 UTC,5.43-2+rpi1 is a raspberry pi package. I just spoke to them now and they have released a fixed version 5.43-2+rpt1+deb9u1
1717266,2020-11-19 20:43:37 UTC,"As there was no activity in that RFE for more than 6 months already, I'm closing it for now. Feel free to reopen it if You will have time and need to work on it."
1717266,2020-04-27 15:23:02 UTC,"Hi, @slaweq, if I have time, I can look at this at Victoria"
1717266,2020-03-24 21:18:05 UTC,"Is there still any interest in implementation of vpnaas support for DVR routers in Neutron? If so, we can discuss that in drivers team but I would like first to know that there is someone interested in working on implementation of it in next cycle."
1717266,2017-12-12 04:26:33 UTC,Could you please check this one [1] if it is the same with your case?
1717266,2018-03-15 01:18:19 UTC,"As commented above """
1717266,2018-03-14 22:47:05 UTC,Got the same error when trying to use vpn-agent on pike installed with openstack-ansible 16.0.8 with dvr routers:
1717266,2018-03-19 03:21:45 UTC,"Thanks, Cao. I think DVR/VPN need to support this. As DVR had support dvr_no_external now, it can support centrilized case. I think we could support it. I will mark this as wishlist."
1717266,2021-01-19 04:17:51 UTC,[Expired for neutron because there has been no activity for 60 days.]
1717269,2019-09-19 14:49:13 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1717269,2017-09-14 17:26:53 UTC,"Excellent, thanks Graham."
1717269,2017-09-14 15:51:16 UTC,Thanks for taking the trouble to flag these; I've created separate issues for each on the MAAS docs GH repo.
1717275,2019-06-25 08:27:06 UTC,This has already been solved in latest wifi-ap snap.
1717277,2017-09-14 15:21:03 UTC,"StacktraceTop:
 g_type_check_instance_cast (type_instance=type_instance@entry=0x555ef9cedaf0, iface_type=93866403363680) at ../../../../gobject/gtype.c:4057
 goa_object_peek_account (object=0x555ef9cedaf0) at goa-generated.c:24246
 on_notification_closed (button=button@entry=0x0, self=0x555ef91887a0, self@entry=<error reading variable: value has been optimized out>) at cc-online-accounts-panel.c:911
 on_remove_account_timeout (user_data=<error reading variable: value has been optimized out>) at cc-online-accounts-panel.c:937
 g_timeout_dispatch (source=source@entry=0x555ef9b67000, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4633"
1717277,2017-10-19 14:04:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717285,2018-11-25 20:47:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717287,2017-09-14 21:17:57 UTC,The fix is a proper api_url regex:
1717287,2017-09-20 08:11:56 UTC,Could this fix be backported to current releases too?
1717290,2018-09-10 20:51:29 UTC,There was discussion at the Stein PTG about this approach: support in client vs support in API. Pierre will prepare a client-side patch and we will continue the discussion on Gerrit.
1717290,2019-05-14 14:25:53 UTC,support in client vs support in API
1717299,2018-11-06 18:36:24 UTC,branch here: user/rogan/lp1717299
1717299,2018-11-06 17:41:48 UTC,This behavior is different in the web client than it was in XUL.  Now the template will save but with the invalid circ modifier.
1717300,2018-06-01 06:02:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717302,2018-10-31 10:52:11 UTC,Is this still happening? I can't find it with query like: http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_status%3A%5C%22FAILURE%5C%22%20AND%20build_name%3A%5C%22neutron-tempest-dvr-ha-multinode-full%5C%22%20AND%20message%3A%5C%22in%20_test_east_west%5C%22
1717302,2018-11-15 09:20:59 UTC,"I was using wrong query, good one: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22marked%20as%20unstable%20because%20of%20bug%201717302%5C%22 shows a lot of such issues still"
1717302,2018-11-16 16:29:39 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/618557"
1717302,2018-11-16 21:27:02 UTC,"I don't think this issue is related to keepalived as keepalived is not used in scenario where those tests are failing.
I deployed similar env as in dvr-multinode scenario job used in gate and I run those tests.
It's very often that one of FIPs configured during test is not pinging. What I found there is that there is no routing to such FIP configured in fip-xxx namespace on host where it should be. Even after restart L3 agent it's not there so I think it's something wrong on server's side instead of some race on L3 agent.
Also when I detached and attached broken FIP to instance again, I saw in L3 agent's logs something like:"
1717302,2018-11-16 21:28:21 UTC,"The same issue is visible also in gate's logs, see: http://logs.openstack.org/57/618557/1/check/neutron-tempest-plugin-dvr-multinode-scenario/ce48f7d/controller/logs/screen-q-l3.txt.gz?level=ERROR"
1717302,2018-11-19 13:34:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/618750"
1717302,2018-11-27 17:56:56 UTC,"Reviewed:  https://review.openstack.org/618750
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7d0e1ccd34a473c511c9c2357421825539965e41
Submitter: Zuul
Branch:    master"
1717302,2018-12-03 12:37:04 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/618557
Reason: It's not completely fixed yet for sure :("
1717302,2018-11-29 08:32:23 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/620804"
1717302,2018-11-29 08:32:49 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/620805"
1717302,2018-11-30 03:26:45 UTC,"Reviewed:  https://review.openstack.org/620804
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=968dba2aaa8c89a57e0fd3f78a2e174bca1a9aa3
Submitter: Zuul
Branch:    stable/queens"
1717302,2018-11-30 03:42:07 UTC,"Reviewed:  https://review.openstack.org/620803
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=115a9f55583b1b762954b046947394b5a3032d52
Submitter: Zuul
Branch:    stable/rocky"
1717302,2018-10-23 13:06:31 UTC,What about this bug? Is it safe to ignore floating IP tests results because of this bug? Shouldn't we skip these tests only in the configuration type we know this problem can happen?
1717302,2018-12-03 18:36:39 UTC,"Reviewed:  https://review.openstack.org/620805
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6e3102b095413f05488868f7b0d3327bc70a5554
Submitter: Zuul
Branch:    stable/pike"
1717302,2018-11-29 08:31:57 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620803"
1717302,2018-09-20 07:04:01 UTC,"Hi Gökhan,"
1717302,2018-09-20 07:29:50 UTC,"Hi Slawek,
thanks for your explanation. You are right. Problem is only with this specific keepalived version, but unfortunately this is stable version on ubuntu xenial. I will share my findings to https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1789045"
1717302,2018-09-19 21:02:11 UTC,I will bring this up in the next Le sub-team meeting
1717302,2018-09-20 06:44:18 UTC,"I think, ı find the problem.  keepalived 1:1.2.24-1ubuntu0.16.04.1 is broken. if you downgrade it, it will work properly. I run sudo apt-get install  --allow-downgrades keepalived=1:1.2.19-1 and it is worked. we need to check  neutron side for keepalived 1:1.2.24-1ubuntu0.16.04.1"
1717302,2017-09-14 21:10:51 UTC,http://logs.openstack.org/30/503530/6/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/ba5131c/logs/subnode-2/screen-q-l3.txt.gz?level=DEBUG#_Sep_14_18_31_35_136440
1717302,2017-09-14 21:54:17 UTC,Sep 13 07:16:43.404250 ubuntu-xenial-2-node-rax-dfw-10909819-895688 neutron-keepalived-state-change[5461]: ERROR neutron.agent.linux.ip_lib [-] Failed sending gratuitous ARP to 172.24.5.3 on qg-bf79c157-e2 in namespace qrouter-796b8715-ca01-43ad-bc08-f81a0b4db8cc: Exit code: 2; Stdin: ; Stdout: ; Stderr: bind: Cannot assign requested address
1717302,2017-09-20 18:51:10 UTC,"@anil-venkata can you comment on this bug.
I am trying to understand this scenario test case.
We are basically using two node setup, with one DVR node and the other DVR_SNAT node.
With DVR, ha should not be enabled, since we only have one node.
If it can be enabled, then how are we testing the master/slave snat_namespace here."
1717302,2017-10-12 15:08:24 UTC,"I think I have a patch for this bug, maybe I didn't tag it correctly with the BZ #."
1717302,2017-10-12 15:11:01 UTC,"https://bugs.launchpad.net/neutron/+bug/1696893 is the bug I've been tracking the arping fix under, mostly just a cosmetic error since it's asynchronous."
1717302,2017-10-12 15:21:22 UTC,"Even with the above patches (bad arping arguments, arping error), we still have a failure:"
1717302,2017-11-30 04:26:48 UTC,I was able to reproduce this issue locally.
1717302,2017-09-14 17:28:09 UTC,http://logs.openstack.org/43/500143/5/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/0a58fce/logs/subnode-2/screen-q-l3.txt.gz?level=DEBUG#_Sep_13_07_16_43_022775.
1717302,2017-12-01 00:30:11 UTC,The 'odd' behavior here is
1717302,2017-12-07 14:52:56 UTC,"I am running out of ideas on this bug.
Can anyone else take a look at it."
1717302,2018-08-10 07:14:19 UTC,"I think this is the root cause:
https://bugs.centos.org/view.php?id=11238
It's a kernel bug."
1717302,2018-09-09 22:16:37 UTC,"Reviewed:  https://review.openstack.org/600197
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dbd6dbb5e19a269c17601a4038eae8eb050d182c
Submitter: Zuul
Branch:    stable/pike"
1717302,2018-09-15 11:35:23 UTC,http://logstash.openstack.org/#/dashboard/file/logstash.json?query=build_status:%5C%22FAILURE%5C%22%20AND%20build_name:%5C%22neutron-tempest-dvr-ha-multinode-full%5C%22%20AND%20message:%5C%22FloatingIpSameNetwork%5C%22&from=7d
1717302,2018-09-19 21:01:32 UTC,"Note that in related bug https://bugs.launchpad.net/neutron/+bug/1793118, the submitter reports that:"
1717302,2017-11-30 04:52:48 UTC,"Also on the 'Node1', floatingIP is configured but the DNAT rule is missing in the router namespace."
1717321,2018-02-11 05:31:06 UTC,"Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/513974"
1717321,2017-10-31 04:43:21 UTC,"Reviewed:  https://review.openstack.org/513973
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=bb64d2bd4309b1e538f88725b29dde659d3ecd2b
Submitter: Zuul
Branch:    stable/pike"
1717321,2017-10-22 04:50:56 UTC,"Reviewed:  https://review.openstack.org/507189
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=81a28142a065e07f16756b1bc4cfb68a98e0a2e9
Submitter: Zuul
Branch:    master"
1717321,2017-10-22 03:06:02 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/513974"
1717321,2017-10-22 03:01:44 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/513973"
1717321,2017-09-25 16:17:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507189"
1717321,2017-09-19 16:57:44 UTC,"OK, current plan, ssl settings can be done in another bug or something"
1717321,2017-09-19 16:44:14 UTC,"see also our bug triage conversation about the impact and the decision on how to fix it.
We need someone with cycles to fix it."
1717321,2017-09-14 17:52:19 UTC,"oh ya, generate your own dhparam..."
1717321,2017-09-19 17:44:12 UTC,"dns setup isn't needed, so the last stanza (resovler) is not needed."
1717337,2018-02-14 10:52:54 UTC,"Note that for queens, mongodb is not required and that's implemented in the current next charms."
1717337,2018-04-26 13:13:20 UTC,"So, for 18.02 charms and Pike+ this is now usable without mongodb."
1717341,2017-09-14 20:35:14 UTC,"Hi Yuri,"
1717342,2018-09-06 07:47:46 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/511472
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1717342,2019-05-22 10:04:48 UTC,"Change abandoned by Deividas Pranevicius (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/660250
Reason: Moved to master."
1717342,2017-10-12 12:57:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511472"
1717342,2019-05-22 06:16:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660567"
1717342,2017-09-17 19:27:09 UTC,"We have local patch for showing quotas when creating volumes, however nothing for Admin panel as we don't use it at all. Bellow screenshots, feel free to let me know if there is an interest in putting this upstream"
1717342,2017-09-25 10:19:14 UTC,"Horizon doesn't use RFEs, and we don't have the development scope right now to pick up general feature requests. If you have some time / resources to work on this feature, please propose a blueprint using the template here: https://blueprints.launchpad.net/horizon/+spec/template"
1717342,2017-09-17 19:26:53 UTC,"We have local patch for showing quotas when creating volumes, however nothing for Admin panel as we don't use it at all. Bellow screenshots, feel free to let me know if there is an interest in putting this upstream"
1717346,2017-09-15 01:03:19 UTC,Are you sure you're using gnome-screensaver and not e.g. lightdm's locker?
1717347,2017-09-14 20:00:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/504187"
1717347,2018-10-16 10:34:26 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/504187
Reason: Cleaning up changes that seem to be abandoned or are older than two months. If you think this was an error and the change is still relevant, please be free to restore it. Sorry for any inconvenience that I might have caused by this."
1717348,2019-09-19 12:04:36 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1717349,2017-09-15 13:06:11 UTC,This will be fixed in our major release at the end of this year which will be based on gcc 7.
1717352,2017-09-14 20:43:30 UTC,Fixed by installing:
1717352,2019-05-09 22:48:33 UTC,"> Fixed by installing:
"
1717352,2019-05-10 00:27:19 UTC,"Is this behavior reproducible on 18.04? If it is, can you please explain what you did to make that ""Install Language"" show up."
1717352,2019-07-09 04:17:28 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1717356,2018-03-07 05:49:08 UTC,Bump.
1717356,2017-09-15 13:12:09 UTC,Tests are here: https://github.com/latchset/jwcrypto/pull/66/commits/b2b66b53bc0df72eb761959fe39700451803d8ab
1717356,2017-09-14 20:43:53 UTC,"17.04 and 17.10 are not affected since they publish the fixed version 0.3.2. 16.04 appears to be affected, but the code is significantly different. I've requested info from the source project owner to test my proposed patch for 16.04."
1717360,2017-10-17 21:19:58 UTC,"Hello Brian, or anyone else affected,"
1717360,2017-10-17 21:24:29 UTC,"Hello Brian, or anyone else affected,"
1717360,2017-10-30 21:20:59 UTC,The 17.04.8 autopkgtest did pass.
1717360,2017-10-30 21:21:33 UTC,The 16.04.10 autopkgtest passed too.
1717360,2017-10-31 17:06:22 UTC,This bug was fixed in the package update-manager - 1:17.04.8
1717360,2017-10-31 17:06:36 UTC,"The verification of the Stable Release Update for update-manager has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1717360,2017-10-31 17:06:48 UTC,This bug was fixed in the package update-manager - 1:16.04.10
1717363,2017-12-17 15:37:50 UTC,"#3 has some funny side-effects: Many people dismantle military buildings far away from borders and thus have no military presence there. What if there is a farm on top of the port space, would it burn down?"
1717363,2019-09-15 16:55:57 UTC,Migrated to https://github.com/widelands/widelands/issues/541
1717363,2017-09-21 10:06:48 UTC,"Would #7 make the port under construction indestructible only while the wares are being unloaded or until the building process is completed?
If the latter, I´d prefer #7; otherwise #3."
1717363,2017-09-18 13:49:22 UTC,"I like #7 - that seems very simple and does not change the rules of Widelands at all. It is still possible to conquer a portspace and burn down the port, but that is just as expensive as keeping the port."
1717363,2017-09-18 12:24:49 UTC,All those solutions seem workable.
1717363,2017-09-18 08:58:56 UTC,Or have the sip unload all its wares anyway?
1717363,2017-09-22 08:47:31 UTC,until the building process is completed makes most sense and is probably easiest to implement IMHO.
1717363,2017-09-15 22:05:36 UTC,"From my side, the land currently not in range of any military building (headquarters is also a military building here) is not ""real conquered land"". It is rather ""temporarily conquered"" and you can pick it.
This is my point of view.
With this, empty land, ""conquered"" by previous port building, can be captured by anyone. Really anyone. Also this can help with solving some issues if we will go to ""military expeditions"" (conquering port & building one)."
1717363,2017-09-15 16:05:08 UTC,If feasible it would be enough to switch the order of building a port. Currently we have:
1717363,2017-09-15 10:13:20 UTC,"I would make a special code for expeditions that reverts the terrain to unclaimed if the ship is not fully unloaded, or if the port is not completed within a limited time."
1717363,2017-09-15 10:13:13 UTC,"A suggestion for a possible solution: If there is no portconstructionsite on a port space and no player (except possibly the one who wants to found a colony there) has military influence over the port space, then it should be possible for an expedition ship to found a colony on this port space, conquering the other player´s unguarded land to do so.
That way, a port space would only be blocked if a player is actively constructing a port there or he has an occupied military building nearby that makes it impossible for another player to conquer the entire land required by the constructionsite.
This would fix both the rush-to-block-port-spots-problem (which I consider not a bug but an unfair strategy) and the issue that the same player can´t build a port there later (which is most certainly a bug)."
1717363,2017-09-15 09:08:18 UTC,"From what I got from WorldSavior’s answer, even he wasn’t able to build a port there after he destroyed the construction site. (https://wl.widelands.org/forum/post/21343/ last line) So there’s definitely something wrong."
1717363,2017-09-15 07:44:42 UTC,"> it's clearly a bug, and must be fixed.
"
1717363,2017-09-18 08:57:43 UTC,How about we disable the option to destroy the construction site for expedition ports?
1717365,2017-11-15 01:06:58 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1717365,2017-10-25 19:22:35 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1717365,2017-10-24 12:42:32 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1717365,2017-10-17 20:39:35 UTC,"Reviewed:  https://review.openstack.org/506320
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b2577207203167d7b8610531bedf0f480a9b7865
Submitter: Zuul
Branch:    stable/ocata"
1717365,2017-10-17 20:39:26 UTC,"Reviewed:  https://review.openstack.org/506319
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c393e490751416f408432ec20e2b1afc1af88af0
Submitter: Zuul
Branch:    stable/pike"
1717365,2017-10-17 20:33:08 UTC,"Reviewed:  https://review.openstack.org/506323
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2d76ed6e8a98f995e3693450cc788e70080691d5
Submitter: Zuul
Branch:    stable/newton"
1717365,2017-11-01 00:20:26 UTC,This issue was fixed in the openstack/nova 14.0.9 release.
1717365,2017-09-21 17:38:10 UTC,Changing the severity to high since this breaks live migration.
1717365,2017-09-21 17:38:04 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/506320"
1717365,2017-09-21 17:34:00 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/506319"
1717365,2017-09-21 17:26:54 UTC,"Reviewed:  https://review.openstack.org/504260
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8ac7be36bedaf0dd3467efc5b5bffdb365b8231b
Submitter: Jenkins
Branch:    master"
1717365,2017-09-14 22:08:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/504260"
1717365,2017-09-21 17:49:51 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/506323"
1717366,2020-08-18 19:07:11 UTC,"It appears to be working for me, but only with Hatch installed on my local machine"
1717366,2020-08-18 18:17:21 UTC,"In my testing, this change appears to do the opposite of what was intended. The first time I load a patron with this setting enabled, the summary bar is collapsed and then it stays open when I switch between the patron tabs."
1717366,2019-11-25 18:26:06 UTC,"Oops, pasted the branch name when I meant to paste the url: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1717366-patron-summary-autocollapse-rebase"
1717366,2019-11-18 19:30:58 UTC,Please rebase against current master. Thanks!
1717366,2019-11-25 17:32:59 UTC,"As Katlyn's not working on Evergreen anymore, I performed the rebase: user/khuckins/lp1717366-patron-summary-autocollapse-rebase"
1717366,2018-11-27 23:07:31 UTC,The previous link is incorrect. The branch can be found here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/klbeck/lp1717366-patron-summary-toggle
1717366,2018-11-27 21:43:07 UTC,"I've abstracted out the functionality in toggle_expand_summary() into a controller function. This is called when the summary expand button is pressed as well when there is a change in the ""toggle off patron summary"" library setting."
1717366,2017-09-15 15:14:16 UTC,"Confirmed the org unit setting ""circ.auto_hide_patron_summary"" is not referenced in the web client."
1717366,2019-01-15 17:27:09 UTC,"Thanks, Katlyn."
1717382,2017-09-19 03:26:23 UTC,"This is documented upstream as fixed in glibc 2.26, which is the version we will ship in artful; therefore marking as resolved for the devel series."
1717382,2018-05-29 16:24:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717382,2020-05-04 18:57:37 UTC,"This is fixed in newer releases of Ubuntu, including 2 LTSes that have been released since this bug was filed.  We have not found capacity to land this in Ubuntu 16.04 in 2.5 years; I'm therefore marking this wontfix which is more realistic.  Users will get improved performance by upgrading to Ubuntu 18.04 or Ubuntu 20.04."
1717398,2017-09-15 12:32:06 UTC,"The attachment ""patch.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1717398,2017-09-15 07:58:31 UTC,"# Bazaar merge directive format 2 (Bazaar 0.90)
# revision_id: <email address hidden>
# target_branch: http://bazaar.launchpad.net/~unity-settings-daemon-\
#   team/unity-settings-daemon/trunk/
# testament_sha1: 98208daf40f4bae50249e1b14e227521f9cad7b8
# timestamp: 2017-09-15 19:57:38 +1200
# base_revision_id: <email address hidden>
#
# Begin patch
=== modified file 'debian/source_unity-settings-daemon.py'
--- debian/source_unity-settings-daemon.py	2013-12-04 23:55:26 +0000
+++ debian/source_unity-settings-daemon.py	2017-09-15 07:54:46 +0000
@@ -3,7 +3,7 @@"
1717398,2017-09-15 07:59:56 UTC,Patch added above to fix the typo
1717398,2017-09-15 08:36:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717398,2017-10-06 07:27:53 UTC,"Thanks for the fix, there is an upload in the queue but the fix can land once this one is cleared"
1717413,2017-09-15 14:30:15 UTC,"I'd suggest raising SnapcraftEnvironmentError(""The directory idontexist doesn't contain a file meta/snap.yaml. If you meant to build a snap in the given folder, cd into the folder instead and re-run Snapcraft."""
1717414,2020-09-13 20:14:43 UTC,Seems to work fine now. Thank you!!
1717414,2020-09-05 09:49:19 UTC,There have been quite a bunch of improvements in the keysyms handling during the past years ... can you still reproduce your issue with the latest version of QEMU?
1717414,2020-09-15 10:24:53 UTC,Thanks for testing! So I'm closing the ticket now.
1717433,2017-09-15 06:11:22 UTC,Seems to be a recurring problem:
1717436,2017-11-26 04:33:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717436,2020-07-23 15:32:26 UTC,looks like you tweaked /usr/bin/python symlink point to python3
1717446,2017-10-23 05:35:57 UTC,"OK, let's use bug 1725708 for the wrongly placed bubble menu."
1717446,2017-10-23 05:23:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717446,2017-10-23 05:34:18 UTC,Whether or not this bug triggers an accidental minimize seems to depend on the style of the headerbar.
1717453,2019-04-24 07:24:49 UTC,Downstream bug: https://bugs.launchpad.net/bugs/1717453
1717453,2020-03-02 13:10:19 UTC,Sadly this still doesn't work in 3.35.91-1ubuntu2
1717453,2020-03-02 11:21:16 UTC,This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
1717453,2019-12-04 01:54:56 UTC,"I haven't verified it myself yet, but it looks like this has been fixed upstream in gnome-shell 3.36 (!486)."
1717453,2019-06-17 08:31:28 UTC,Fix in progress: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/486
1717453,2019-06-17 08:31:04 UTC,In progress: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/486
1717453,2018-08-18 09:29:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717453,2016-05-03 21:05:14 UTC,Hi! I'm willing to work on a fix for this and came up with two ideas:
1717453,2017-04-27 19:02:24 UTC,*** Bug 781858 has been marked as a duplicate of this bug. ***
1717453,2016-07-22 14:12:20 UTC,"Hm ... what is the long goal for GNOME Shell themes btw? Because right now it isn't possible to set a font from Gtk themes, but from Shell themes. And I think most people want to have the same font for Gtk and the Shell, so I would say it might be a good idea to ignore the font-family option in Shell themes completely and simplify the GNOME Tweak font settings to"
1717453,2016-07-22 04:14:31 UTC,"For simplicity sake (and not adding another option), i'd initally choose #1, however i think #2 is the way it should be done."
1717453,2013-08-20 10:44:42 UTC,*** Bug 706016 has been marked as a duplicate of this bug. ***
1717453,2012-11-13 23:53:58 UTC,"That's chosen by font-config. I'm not sure how easy it is to hook up to the desktop-font GSetting, considering it has abilities like size and weight: things we typically want to control from the theme ourselves."
1717453,2012-11-13 22:29:13 UTC,"Currently, the default font-face for the shell theme is set in the CSS for the theme with the current rule:"
1717453,2017-09-15 07:36:49 UTC,See also bug 1717456
1717453,2013-08-20 10:45:05 UTC,*** Bug 706251 has been marked as a duplicate of this bug. ***
1717458,2020-08-25 02:31:55 UTC,"Fix released, at some point before focal..."
1717458,2018-08-16 07:16:22 UTC,Confirmed again in 18.10.
1717459,2017-12-10 10:46:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717459,2017-11-09 12:01:58 UTC,Possibly duplicate of bug 1487679 .
1717461,2017-09-15 08:12:03 UTC,"Do not ask me why, but putting a ""preemptive"" import subprocess into Sikuli.py (which in turn is run as strtup of a scriptrun) fixed the issue."
1717461,2020-02-13 21:00:31 UTC,"Hello, RaiMan!
Could you elaborate on this. I am currently using Sikuli version 2.0.0 and the same thing happens to me. As I understood I should just add ""import subprocess"" to the Sikuli.py? But this didn't do anything."
1717466,2017-09-15 12:33:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1717466,2017-09-15 14:29:30 UTC,"I'm guessing you are using the gnome desktop environment, if not please change the assigned package for this bug."
1717466,2017-11-07 17:28:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717466,2020-05-30 06:54:13 UTC,"I am facing the same problem in Ubuntu 20.04 LTS ( 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) , Gnome-control-center 3.36.2 ."
1717476,2017-09-15 20:51:12 UTC,"Hi Sven,"
1717476,2017-09-18 08:21:45 UTC,"Hi Seth,"
1717476,2017-09-22 08:23:13 UTC,"JFYI, I opened an issue with ISC, they are currently triaging the report."
1717476,2017-09-28 15:42:13 UTC,Can I make this bug public?
1717476,2017-11-30 09:58:31 UTC,I pinged the ISC twice because they did not react in two months. They did reply once and asked to keep this need-to-know until they decided if it is a security issue or not. Apparently that takes a long while... I pinged them again to speed up the process.
1717476,2018-01-12 09:46:32 UTC,"Still no reply from the ISC, and I pinged them like 10 times now. I don't mind if you mark this public."
1717476,2018-01-15 18:51:45 UTC,"Hi Sven - I just became aware of this because of your tweet. We (ISC) investigated this back in September and determined it was not present in ISC's distribution. Further, we felt it was not a significant security issue in any case. I haven't found any issue in our bug database with your name as reporter, however, so if you can tell me the bugID, I will make sure it is updated and closed. I sincerely apologize if we dropped the ball on updating you.  If you would like to message me privately, I would also like to know what alias or ID you pinged so many times, because I suspect that ended up in a spam filter somewhere - at least I can't find it in our issue tracker. Thank you."
1717476,2018-01-16 08:38:57 UTC,"Hi Vicky,"
1717481,2017-09-15 12:32:59 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1717481,2017-10-21 19:29:41 UTC,may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1716250
1717484,2018-01-11 19:08:22 UTC,Is the application not launching in MenuLibre or GNOME? Do they launch successfully from the terminal?
1717485,2019-04-09 10:59:46 UTC,Note that only an admin can make and image public already - this is part of the default glance policy:
1717485,2019-04-09 11:01:18 UTC,There is a good question in the linked ask.openstack.org question:
1717485,2019-04-09 12:30:06 UTC,Concerning the ask.openstack.org question:
1717485,2019-04-09 12:32:09 UTC,I didn't realise there were publicize_image and communitize_image policies. Maybe the publicize_image policy is enough for the original requestor?
1717485,2019-04-09 12:46:43 UTC,@miguel.meneses
1717485,2019-06-09 04:17:24 UTC,[Expired for OpenStack glance charm because there has been no activity for 60 days.]
1717485,2019-04-05 18:17:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650408"
1717486,2020-11-14 04:17:16 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1717486,2020-09-14 07:30:41 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1717486,2020-09-14 07:30:15 UTC,"Diogo, that sounds like a different bug. Please open a new bug."
1717486,2020-04-26 21:50:16 UTC,"In my system, disabling IMWheel (https://wiki.archlinux.org/index.php/IMWheel) solves the problem."
1717486,2020-04-25 22:12:38 UTC,"The issue seems to be even worse in Ubuntu 20.04 LTS. A two-finger horizontal scroll on the dock will make the system (almost) irresponsive: no response to keyboard,  only the mouse cursor moves, but clicking anywhere has no effect. Icons on the dock do not disappear anymore, though. I have to close the laptop lid to force suspend so I can control the system again."
1717486,2018-10-11 01:50:13 UTC,"I can confirm this bug, and the workaround with gsettings works. I encountered this same bug on two different machines on 18.04, both updated multiple times daily, one with a Logitech mouse + unifying receiver and the other with a standard Apple wired mighty mouse, on both Wayland and Xorg.
I think this bug is quite universal, the Logitech mouse machine uses Xorg daily with an HD 5570 and the mighty mouse machine uses Wayland daily with a GTX 760 (nouveau)."
1717486,2018-03-09 12:40:33 UTC,"Replying to seb128:
Current Dash to Dock from extensions.gnome.org installed on the same system does not suffer from the same issue."
1717486,2018-03-09 11:24:30 UTC,I have established a workaround which involves no session locking
1717486,2018-03-09 11:00:36 UTC,Confirming with my Bluetooth MS mouse.
1717486,2017-12-11 16:14:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717486,2017-09-17 11:18:04 UTC,Figured out how to reproduce this:
1717486,2017-11-16 15:34:29 UTC,is that still an issue?
1717486,2017-11-17 10:02:49 UTC,"Yes it is.
I found some more evidence to this:"
1717486,2017-12-11 16:17:21 UTC,Could somebody with a device doing horizontal scrolling test in an upstream GNOME session if dash-to-dock has the same issue?
1717486,2017-11-17 11:47:37 UTC,"Yes, I can confirm that scrolling right triggers the same effect.
Curious."
1717486,2017-11-17 14:27:36 UTC,"right, I think the ""crash"" is just a wording issue from the user trying to describe the problem"
1717486,2017-11-17 10:40:29 UTC,the issue seems similar to bug #1727363
1717490,2017-11-30 09:57:22 UTC,Any update on this?
1717490,2017-12-01 01:17:17 UTC,"Thanks for subscribing us Sven, this bug was invisible until then."
1717490,2017-12-01 01:23:40 UTC,"BTW, is there a reason to keep this bug private? It doesn't directly allow privilege escalation, it feels like the privacy is unneeded here."
1717490,2017-12-01 09:07:52 UTC,"That is up to you, I just felt to rather be cautious just in case this has side effects I am not aware of. :)"
1717490,2017-12-02 11:07:09 UTC,I suppose most of the time authentication childs actually exit? There's a lot of indirection in the source because it's a child that communicates with the greeter through another daemon. But AFAICS it expects PAM to free() the strings:
1717499,2017-09-15 12:00:54 UTC,"StacktraceTop:
 gs_app_kv_printf (str=str@entry=0x7fd0cca81d20, key=key@entry=0x560552b3858f ""kudo-percentage"", fmt=fmt@entry=0x560552b3b4b1 ""%u"") at ../lib/gs-app.c:215
 gs_app_to_string_append (app=app@entry=0x7fd0d4085850, str=str@entry=0x7fd0cca81d20) at ../lib/gs-app.c:422
 gs_app_to_string (app=0x7fd0d4085850) at ../lib/gs-app.c:368
 gs_details_page_app_refine_cb (source=<optimized out>, res=0x5605560babb0, user_data=<optimized out>) at ../src/gs-details-page.c:1514
 g_task_return_now (task=0x5605560babb0) at ../../../../gio/gtask.c:1145"
1717511,2019-09-19 11:53:53 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1717515,2017-09-19 05:02:21 UTC,"Removing packages from artful-proposed:
 dipy 0.12.0-1build1 in artful
  python-dipy 0.12.0-1build1 in artful amd64
  python-dipy 0.12.0-1build1 in artful arm64
  python-dipy 0.12.0-1build1 in artful armhf
  python-dipy 0.12.0-1build1 in artful i386
  python-dipy 0.12.0-1build1 in artful ppc64el
  python-dipy 0.12.0-1build1 in artful s390x
  python-dipy-doc 0.12.0-1build1 in artful amd64
  python-dipy-doc 0.12.0-1build1 in artful arm64
  python-dipy-doc 0.12.0-1build1 in artful armhf
  python-dipy-doc 0.12.0-1build1 in artful i386
  python-dipy-doc 0.12.0-1build1 in artful ppc64el
  python-dipy-doc 0.12.0-1build1 in artful s390x
  python-dipy-lib 0.12.0-1build1 in artful amd64
  python-dipy-lib 0.12.0-1build1 in artful arm64
  python-dipy-lib 0.12.0-1build1 in artful ppc64el
  python-dipy-lib 0.12.0-1build1 in artful s390x
Comment: FTBFS, removed from Debian testing; Debian bug #851048
1 package successfully removed."
1717515,2017-09-19 04:55:31 UTC,"nipype already has a pre-existing build failure unrelated to FPE; removing instead.
Removing packages from artful-proposed:
 nipype 0.12.1+git4-gbc3a0b5-1 in artful
  python-nipype 0.12.1+git4-gbc3a0b5-1 in artful amd64
  python-nipype 0.12.1+git4-gbc3a0b5-1 in artful arm64
  python-nipype 0.12.1+git4-gbc3a0b5-1 in artful armhf
  python-nipype 0.12.1+git4-gbc3a0b5-1 in artful i386
  python-nipype 0.12.1+git4-gbc3a0b5-1 in artful ppc64el
  python-nipype 0.12.1+git4-gbc3a0b5-1 in artful s390x
  python-nipype-doc 0.12.1+git4-gbc3a0b5-1 in artful amd64
  python-nipype-doc 0.12.1+git4-gbc3a0b5-1 in artful arm64
  python-nipype-doc 0.12.1+git4-gbc3a0b5-1 in artful armhf
  python-nipype-doc 0.12.1+git4-gbc3a0b5-1 in artful i386
  python-nipype-doc 0.12.1+git4-gbc3a0b5-1 in artful ppc64el
  python-nipype-doc 0.12.1+git4-gbc3a0b5-1 in artful s390x
Comment: FTBFS, removed from Debian testing; Debian bug #848777
1 package successfully removed."
1717515,2017-09-19 05:01:28 UTC,"Removing packages from artful-proposed:
 nipy 0.4.1-1build1 in artful
  python-nipy-lib 0.4.1-1build1 in artful armhf
  python-nipy-lib-dbg 0.4.1-1build1 in artful armhf
Comment: FTBFS, removed from Debian testing; Debian bug #868916
1 package successfully removed."
1717517,2017-09-17 12:09:09 UTC,apport information
1717517,2017-09-17 12:09:08 UTC,apport information
1717517,2017-09-17 12:09:06 UTC,apport information
1717517,2017-09-17 12:09:05 UTC,apport information
1717517,2017-09-17 12:09:03 UTC,apport information
1717517,2017-09-17 12:09:01 UTC,apport information
1717517,2017-09-17 12:09:00 UTC,apport information
1717517,2017-09-17 12:08:00 UTC,apport information
1717517,2017-09-17 12:07:57 UTC,apport information
1717517,2017-09-17 12:07:55 UTC,apport information
1717517,2017-09-17 12:07:53 UTC,apport information
1717517,2017-09-17 12:07:52 UTC,apport information
1717517,2017-09-16 01:44:22 UTC,"Hello Lewis, could you please run apport-collect 1717517 ? That should gather some log files and attach them to this bug for inspection."
1717517,2017-09-17 12:07:58 UTC,apport information
1717517,2017-09-17 12:07:51 UTC,apport information
1717522,2021-02-17 13:50:25 UTC,this has been fixed in g and later.
1717522,2021-02-17 13:51:42 UTC,"> this has been fixed in g and later.
"
1717523,2017-09-18 16:41:34 UTC,"I have also tried installing nemo / Files under 17.10b using Preferred Applications to set Files as the default File Manager but only Caja gets opened when you click Home on the desktop or Home under Places, just as happens with Thunar."
1717523,2017-09-18 17:14:47 UTC,"If I right click on a directory under caja, the top five options in the context menu are:"
1717523,2017-09-18 18:10:45 UTC,"It seems I was right in thinking it is caja that handles the desktop icons for MATE although I'm not sure about the 'Places' links etc yet. Maybe that is something that would need to change in MATE menu, the advanced menu etc?"
1717523,2020-05-22 04:17:22 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1717526,2017-09-15 14:51:50 UTC,"Thanks, Dan.  Here's a branch that signs off on your commit and adds another with inline documentation and a minor optimization."
1717528,2017-09-15 14:13:35 UTC,"This is the case under UM 17.10b x64. I should add that video thumbnails for local files work fine and that I'm mainly concerned with h264 MP4 and mkv files, but I'd hope all popular formats could be previewed over a network."
1717528,2017-09-15 18:13:56 UTC,Have you enable Thumbnails for remote drives?
1717528,2017-09-15 18:51:55 UTC,Hi Wimpy
1717528,2018-10-20 16:43:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717528,2018-10-20 16:57:40 UTC,"Similar behaviour in 18.04 ubuntu-mate
Thumbnails for video files and those of ooo-thumbnailer do not show up in sftp or smb shares
mounted via the caja menu option sftp://<email address hidden>/xxxx smb://<email address hidden>/xxxx
In cifs shares instead mounted via autofs preview works as it should
/mnt/xxxxxx -fstype=cifs,vers=3.0,rw,credentials=/home/xxxxx/.cifspwd,nodfs,iocharset=utf8,uid=1000,gid=1000,file_mode=0700,dir_mode=0700 ://169.254.43.186/xxxxx"
1717539,2019-03-07 17:16:05 UTC,"I've confirmed this, but it appears to be intended behavior that would require a css change.  The style.css file works to hide the table header when the window width is below 600 pixels.  This appears to apply to all table headers, so is linked to Bug#1717553 in that respect.  I'd be willing to crack at it, but I'm not sure what end result is the most desirable."
1717539,2019-03-07 18:11:15 UTC,"What about leaving the existing header behavior as-is, but then adding another 'check all' option that only appears when the window width is below 600 pixels?"
1717540,2017-11-22 07:16:31 UTC,"Hi,"
1717542,2017-11-03 09:50:42 UTC,Here are more details from the auditing scan.
1717542,2017-09-20 18:03:05 UTC,Let's not mark importance until its confirmed please :)
1717542,2017-09-20 20:43:55 UTC,"If you believe you have encounter a security issue, please mark it as such and don't mark as public."
1717544,2017-09-15 17:31:40 UTC,I wonder if upstream would accept the patches for Python 3 support.
1717547,2017-09-29 14:48:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/508533"
1717547,2018-10-30 20:52:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/614351"
1717547,2018-11-06 15:09:47 UTC,"Change abandoned by Jay Pipes (<email address hidden>) on branch: master
Review: https://review.openstack.org/614351"
1717547,2018-11-06 21:24:13 UTC,"Reviewed:  https://review.openstack.org/614351
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5c21a00e89539bbb271ccfa05e4a2ba1cddae58e
Submitter: Zuul
Branch:    master"
1717547,2019-03-22 03:46:17 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1717547,2019-04-04 16:25:32 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650064"
1717547,2019-04-04 16:25:47 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/650065"
1717547,2019-04-06 09:55:35 UTC,"Reviewed:  https://review.openstack.org/650064
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=07ccc82af048494cb7d4c4b0cc191cc30544a270
Submitter: Zuul
Branch:    stable/rocky"
1717547,2019-04-08 02:49:21 UTC,"Reviewed:  https://review.openstack.org/650065
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f1554d1b527bbf09229273508ce1fb234caf6a66
Submitter: Zuul
Branch:    stable/queens"
1717547,2019-04-23 15:17:45 UTC,"Note that we don't want to backport this any further without some other fixes related to a regression it caused, see bug 1803717."
1717547,2019-05-13 14:58:14 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/508533
Reason: bug: #1717547 has been fixed with an alternative patch https://review.opendev.org/#/c/614351/ in the meantime"
1717547,2019-06-18 03:41:31 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1717547,2019-07-10 21:40:15 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1717553,2019-03-07 17:22:33 UTC,Copying my comment with minor change from: https://bugs.launchpad.net/evergreen/+bug/1717539
1717560,2017-10-05 19:27:17 UTC,The proposal sounds problematic in that a subnet with no default route may lead a VM with a single interface to lack a default gateway :(
1717560,2018-02-02 17:19:46 UTC,Discussed briefly during today's drivers meeting. Reclassifying as a normal bug so a fix can be submitted for it
1717560,2018-01-25 12:28:35 UTC,i guess it's nice to have a tempest scenario for this to ensure the consistent behavior among implementations.
1717560,2018-01-19 15:07:21 UTC,"@Miguel: yes, I'd agree.
@Armanda: did your mulling over bring over something ?"
1717560,2018-01-19 14:28:58 UTC,"@Thomas,"
1717560,2018-01-12 02:38:07 UTC,"@Thomas, thanks for following up on it. Let me mull over this a bit, I wonder if there's something else we don't recall/misusing, but the initial result is certainly promising!!"
1717560,2018-01-11 10:35:25 UTC,"@armando: I've done a bit of testing, and while I could successfully change the routers options via DHCP, I could not have it omitted by using an empty value."
1717560,2018-01-08 16:56:39 UTC,@Thomas: happy new year! Glad I was able to give you a homework ;)
1717560,2017-09-27 21:04:37 UTC,see also bug 1718954
1717560,2018-01-05 21:01:37 UTC,"Just adding a comment since there is one other issue here - since neutron port security is adding anti-spoofing rules, there is still a need for some kind of configuration on the instance, since trying to use the IP of one interface on another would lead to packets being dropped on egress.  This can be worked-around with routing rules and sysctl settings, but is more likely to happen in this situation."
1717560,2018-01-05 14:42:00 UTC,"@Thomas,"
1717560,2017-12-22 14:57:22 UTC,"@Thomas,"
1717560,2017-12-22 02:08:40 UTC,Thomas: ping?
1717560,2018-01-08 09:36:31 UTC,"(Sorry for the delayed answer, I took some time off for the end and beginning of year.)"
1717560,2017-11-16 17:52:40 UTC,"Problem is that the default route is advertised even though you set ""Disable gateway""."
1717560,2017-12-15 03:38:07 UTC,"We revived the discussion about this request during today's drivers meeting. That prompted me to look into this more closely. I must admit I have not tried this myself yet in practice, but I wonder if the dhcp extra option on ports can come to the rescue here [1,2,3]. If I understand this correctly, it should be possible to clear the dhcp-option = option:router on a given port and that should allow dnsmasq to stop advertising the default route. Should that not work, my point being that we can address your use case without coming up with a new API but leverage the existing bits we have. Have you by any chance looking into that already?"
1717560,2017-10-05 19:32:38 UTC,"I mean, there's steps one can take to address this issue, and I am not sure that an API to alter the behavior of the DHCP service is the right approach."
1717560,2017-10-06 09:47:00 UTC,"Armando,"
1717560,2017-10-10 08:52:51 UTC,"I do not understand how your new option would behave different than setting ""gateway=None"" on your subnet. You can still attach a router to the subnet and use host-routes via that router if you do so. This sequence of commands seems to do just the right thing it seems:"
1717560,2017-10-12 00:43:14 UTC,@Thomas: I may have articulated my point very poorly. My bad.
1717560,2017-10-05 19:31:54 UTC,"How does this work in 'real life'? At first I feel like we have to complicate our lives too much, though I appreciate the source of contention that may arise when a host connects to multiple networks."
1717560,2017-10-12 11:58:14 UTC,"Hello,"
1717560,2017-10-12 12:37:49 UTC,"> default route is advertised even though you set ""Disable gateway"". Check following network_data.json >  http://paste.ubuntu.com/25725747/
"
1717560,2017-10-12 15:54:30 UTC,Thomas: +1
1717560,2017-10-13 07:33:33 UTC,"Ok, Lukas we're in line."
1717560,2017-10-26 13:17:49 UTC,i skimmed all comments but failed to understand what's wrong with j-harbott's example.
1717560,2017-10-12 09:19:55 UTC,"Ah yes, ok, my ""custom teaks via cloud-init that fix routing"" was too elliptic."
1717563,2017-09-19 16:04:29 UTC,I haven't been able to reproduce this in master as of today. A couple things that might help narrow it down would be:
1717563,2017-09-21 13:32:25 UTC,"FWIW, our production server is also on EG 2.12.4 and OpenSRF 2.5.0 and we are not seeing problems with PO JEDI action triggers, or action triggers in general."
1717563,2019-03-04 21:00:49 UTC,Marking incomplete as more info is needed to determine if this is a local issue or not
1717573,2017-09-18 04:45:41 UTC,The bug appears to be in snapd which is returning this error.
1717573,2017-09-18 04:48:35 UTC,From store/store.go in the snapd repository:
1717573,2017-09-18 04:57:00 UTC,"Testing shows +&><() seem to work fine, but =|!{}[]^""~*?:\/ do not."
1717573,2017-09-18 05:00:37 UTC,"I opened a forum topic to discuss with the snapd authors:
https://forum.snapcraft.io/t/special-characters-cause-searches-to-fail/2158"
1717573,2017-11-21 22:54:28 UTC,Still happening in Bionic.
1717573,2018-01-02 09:47:17 UTC,"It seems what you need is the right error kind to distinguish this error, this is done in: https://github.com/snapcore/snapd/pull/4428 now"
1717581,2017-09-19 17:09:03 UTC,"Bisected to f1dd2cd13c4b ""mm, memory_hotplug: do not associate hotadded memory to zones until online."" Reported upstream."
1717581,2017-09-15 19:06:22 UTC,"memory-hotplug kselftest is failing. A bug in the test means it wasn't actually doing anything before, so possibly this doesn't represent an actual regression vs. previous artful kernels. However the test does pass in xenial so it warrants investigation."
1717581,2017-09-15 23:36:52 UTC,Reproduced in a VM.
1717590,2017-10-03 10:40:24 UTC,"So to read through this, if a hook is never exited, then definitely it would cause starvation because only 1 hook is allowed to run. If a hook was run, exited, and then something caused it to run again, I would expect that would still provide opportunity for a different application on the same machine/container to get a chance to acquire the hook lock and run."
1717590,2017-09-26 14:00:25 UTC,"Reviewed:  https://review.openstack.org/507187
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=fb95b22add55e0254523c9a6a6f84c832931c20c
Submitter: Jenkins
Branch:    master"
1717590,2017-09-26 14:17:52 UTC,"Fix proposed to branch: stable/17.08
Review: https://review.openstack.org/507553"
1717590,2017-09-27 19:40:56 UTC,we had a run last night using the cs:~openstack-charmers-next/percona-cluster charm that actually completed deployment before timing out; hacluster-pxc units were all up about 45 minutes after deploy where they wouldn't all come up after 3 hours before.  the mysql unit log looks much quieter too.
1717590,2017-09-28 07:41:58 UTC,"Reviewed:  https://review.openstack.org/507553
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=c8e8adc1e69fcabeebb0901175e52d8bd1c68d42
Submitter: Jenkins
Branch:    stable/17.08"
1717590,2017-09-29 11:32:03 UTC,Landed into 17.08 stable - marking fix released and closing out hacluster bug task.
1717590,2017-10-26 15:58:17 UTC,"We're still running into this.  These logs show the hacluster unti waiting 5 minutes to acquire the machine lock, while the mysql unit acquires and releases it about 32 times during the same time period.  It doesn't seem like the lock has any queuing properties."
1717590,2017-09-19 18:39:48 UTC,"Apologies, I could have made it more clear which charm code I was referring to:  The unit which has no agent is the hacluster charm, and since that charm has no agent up, that charm code is not in effect."
1717590,2017-10-30 20:28:07 UTC,"Yes, this is the case. The lock is taken for any particular hook execution. The lock is machine wide, and impacts all agents on that machine."
1717590,2017-10-30 20:55:48 UTC,"There is one thing juju could do, and that is to add a sleep for half a second once the hook execution lock is released. This would allow other units on the machine to acquire the lock and progress, but I'm not sure this would result in a faster final deployment."
1717590,2017-10-30 21:25:15 UTC,"+1 I was thinking the same thing.  I think it would result in faster
deployments - I think the busy units are running hooks that end up saying
""we can't do anything because we're not clustered"" and will be able to
progress past that faster if the unit responsible for clustering gets to
run its hooks faster."
1717590,2017-11-02 10:27:28 UTC,"keystone lacks the 'if vip and not clustered, defer' optimisation at the moment which would help this; however it won't avoid the work having to be done at some point in time so I don't think it will impact hugely on overall deployment performance."
1717590,2017-11-08 10:50:22 UTC,https://github.com/juju/mutex/pull/4 will make the hook execution lock fair. Once that lands I'll update Juju to get this into 2.3.
1717590,2017-11-09 02:12:17 UTC,"juju/mutex changes have landed, https://github.com/juju/juju/pull/8039 updates Juju to bring it in for 2.3-beta3."
1717590,2017-11-10 03:05:19 UTC,"Unfortunately the fix had to be backed out just before the beta3 release process started, due to a bug in the new code. It'll be in rc1 instead."
1717590,2017-10-26 16:05:38 UTC,"Here's another example from the same deployment.  The keystone unit on this machine has been hogging the machine-lock for over an hour, preventing subordinates like hacluster-keystone (which needs to finish setup before keystone can really do anything) from getting the lock.  You can see the subordinates on this machine have all been waiting over an hour for the lock"
1717590,2017-09-19 17:59:48 UTC,"#16
@1chb1n"
1717590,2017-09-19 16:49:37 UTC,"Ok Dmitrii, that makes sense.  I think what you're saying is telegraf is only talking to mysql to get information from it to report on, not to use it as a database, so only the telegrafs running on the same containers as mysql need to join the relation with mysql."
1717590,2017-09-19 17:42:24 UTC,"Can someone from the juju team confirm my theory that the mysqld unit servicing hooks constantly can block the hacluster-pxc unit on the same machine from progressing past ""agent initializing""? I haven't found any clear documentation on this."
1717590,2017-09-19 15:46:31 UTC,"Per the attached logs, one of the hacluster-pxc appears to not have gotten a juju agent:"
1717590,2017-09-19 15:49:05 UTC,"This appears to be a system resource/sizing issue, and/or a tooling issue."
1717590,2017-09-19 16:00:14 UTC,"No, sorry, that's exactly the problem.  Its agent doesn't get initialized until I disable the mysqld unit on that machine."
1717590,2017-09-19 16:03:00 UTC,"Once mysqld is disabled on the machine, the hacluster-pxc unit gets a chance to start doing stuff, and moves past ""agent initializing"" to get setup."
1717590,2017-09-19 16:07:22 UTC,The mysql/* units are all in active/ready state.
1717590,2017-09-19 16:09:25 UTC,fyi everybody on telegraf:
1717590,2017-09-19 16:13:54 UTC,"I'm not convinced it's not a charm issue.  If mysql is being clustered using hacluster, should it not wait to join relations with other applications until its hacluster is done being setup?"
1717590,2017-09-18 19:52:13 UTC,"Liam,"
1717590,2017-09-19 16:41:46 UTC,"I'm not sure what context this is in, but I see the same services causing the mysql unit to be doing stuff over and over and over, blocking hacluster-pxc from getting a chance to do anything:"
1717590,2017-09-19 16:15:29 UTC,"Dmitrii, sorry, I don't fully get your comment. Is there some action to be taken based on that information?"
1717590,2017-09-19 17:12:17 UTC,"The mysql charm code is very much a factor in that situation, in that it's servicing a bunch of hooks, hundreds of times for the same services, preventing the hacluster-pxc agent from getting a chance to initialize itself.  I do think bug 1718247 would address that situation."
1717590,2017-09-19 17:10:06 UTC,"Ryan, thanks for the responses."
1717590,2017-09-19 17:59:13 UTC,"Jason,"
1717590,2017-09-18 09:03:29 UTC,"Hi Jason.
    To narrow down the issue would it be possible to test without telegraf ? Looking at the mysql hook executions from your pastebin I see ~60 telegraf units with relation to mysql ( http://paste.ubuntu.com/25563847/ )"
1717590,2017-09-19 16:50:50 UTC,Hi @jason-hobbs - I think there are 3 things happening here.
1717590,2017-09-19 16:44:43 UTC,"Jason, I suspect that having a non-container-scoped relation will generate a lot of unnecessary traffic."
1717599,2020-09-14 07:34:41 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1717599,2017-11-18 04:17:20 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1717599,2017-09-18 06:20:01 UTC,apport information
1717599,2017-09-18 06:41:28 UTC,The kernel I have is http://kernel.ubuntu.com/git/ubuntu/ubuntu-artful.git/tag/?h=Ubuntu-4.13.0-10.11 built by hand with
1717599,2017-09-18 06:19:56 UTC,apport information
1717599,2017-09-18 02:16:30 UTC,"Oh, I see from the video thanks. Half Life 2 is likely using GLX."
1717599,2017-09-18 02:10:07 UTC,How an app goes full screen could affect the result. And there are traditionally a couple of ways apps can go full screen if they are using X11.
1717599,2017-09-18 06:20:00 UTC,apport information
1717599,2017-09-18 06:19:58 UTC,apport information
1717605,2017-09-15 21:30:16 UTC,Attached the screenshot of phatch by try to open drop down menu of watermark images.
1717605,2017-09-26 10:53:32 UTC,Here is the Error Log:
1717608,2017-09-20 20:41:08 UTC,"See resolution here:
https://github.com/sddm/sddm/issues/892#issuecomment-330970061"
1717608,2017-09-21 14:04:19 UTC,"After updating one of these packages I don't have this problem anymore. Unfortunately, I cannot pinpoint the exact package that fixed it."
1717608,2017-09-20 20:42:14 UTC,Also note that this bug affects the lock screen.
1717608,2017-09-16 22:24:20 UTC,Correct.
1717608,2017-09-16 21:42:52 UTC,The letters on the visual keyboard are invisible too.
1717608,2017-09-16 20:24:50 UTC,"Interesting though, if you click the place with the mouse, where the ""show password"" eye icon should be, the password text is visible (or the grey ""Password"" is shown). But if you click it again, the text disappears."
1717608,2017-09-16 20:09:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717608,2017-09-17 14:15:26 UTC,"I'm afraid, the problem can be in some related QT or KDE library: I've tried to downgrade sddm and sddm-theme-breeze to the versions from zesty (0.13.0-1ubuntu5 and 4:5.9.4-0ubuntu1 correspondently), but the problem is still there."
1717628,2019-12-24 15:58:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717628,2021-01-09 22:43:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1273534, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1717635,2017-10-19 21:03:29 UTC,Thank you for your bug report. Do you get the issue every time? Is that specific to chrome or does it do it with other debs as well?
1717635,2017-10-26 04:31:23 UTC,@seb128 Happened almost every time. Also observed with other debs such as https://atom.io/download/deb
1717635,2017-12-26 04:17:16 UTC,[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.]
1717646,2018-06-09 08:50:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717646,2018-12-06 03:56:23 UTC,This bug was fixed in the package previsat - 3.5.1.7+dfsg1-3
1717649,2017-09-18 19:16:34 UTC,"Hi,"
1717652,2017-09-20 17:08:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717653,2017-09-16 10:17:04 UTC,Was this already an issue in 0.92.1 or is it a regression?
1717653,2017-09-16 10:19:38 UTC,"On second thought the commits are probably unrelated, but figuring out if this is a regression (and a regression window) will be helpful either way"
1717653,2017-09-19 19:14:01 UTC,Inkscape 0.91r13725 shows the same behavior (Ubuntu 16.04.03)
1717653,2017-09-20 19:48:56 UTC,"The issue doesn't reproduce on Windows Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1717654,2017-09-17 10:00:40 UTC,"DistroRelease: Ubuntu 16.04
Package: snapd 2.27.6~14.04
...
UpgradeStatus: Upgraded to xenial on 2017-09-09 (6 days ago)"
1717654,2019-04-08 02:41:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717667,2017-09-19 10:13:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717667,2017-09-19 10:56:17 UTC,Looks like https://github.com/hughsie/fwupd/commit/0dec274e56c23c4afdda75bb42d5b6c9928cb1b6
1717667,2017-11-06 17:43:48 UTC,"@bigon had confirmed that 1.0.0 did fix it, which is now in master.  According to github #259 the patch linked in comment #7 on top of 0.9.x didn't fix it however, so it could have been a combination of other items in master that had actually fixed the issue."
1717667,2017-09-16 10:55:36 UTC,"StacktraceTop:
 FU_IS_DEVICE (ptr=0x55e63330a790) at ../src/fu-device.h:31
 fu_plugin_device_add (plugin=0x55e6332e2280, device=0x55e63330a790) at ../src/fu-plugin.c:317
 fu_plugin_device_add_delay_cb (user_data=0x55e633313260, user_data@entry=<error reading variable: value has been optimized out>) at ../src/fu-plugin.c:374
 g_timeout_dispatch (source=source@entry=0x55e633313290, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4633
 g_main_dispatch (context=0x55e6332a98a0) at ../../../../glib/gmain.c:3148"
1717672,2017-09-18 16:45:33 UTC,"As is the case for https://bugs.launchpad.net/ubuntu-mate/+bug/1717528 , my Caja's Edit -> Preferences -> 'Preview' tab -> 'Show Thumbnails' is set to 'Always' and 'Only for files smaller than' is set to 4GB."
1717672,2018-03-04 15:11:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717672,2018-06-18 15:17:27 UTC,"I have this problem too in Ubuntu Mate 18.04. I tried it with a persistent USB installed genuine Ubuntu 18.04 (64bit) and that too shows this problem. On 16.04 LTS the problem does not occur.
Indeed it is just the DCIM/Camera folder that has the problem.
Cheers,
Peter"
1717678,2018-01-23 16:49:04 UTC,apport information
1717678,2018-01-23 16:49:03 UTC,apport information
1717678,2018-01-23 16:49:07 UTC,apport information
1717678,2018-01-23 10:56:03 UTC,Same with Symbol font from  https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf :
1717678,2018-01-23 10:54:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717678,2018-01-23 16:49:02 UTC,"ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: MATE
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2014-02-07 (1445 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS ""Precise Pangolin"" - Release amd64 (20140204)
Package: gnome-font-viewer 3.16.2-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Tags:  xenial
Uname: Linux 4.4.0-104-generic x86_64
UpgradeStatus: Upgraded to xenial on 2017-04-15 (282 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video wireshark
_MarkForUpload: True"
1717678,2018-01-23 16:49:06 UTC,apport information
1717701,2017-09-17 09:25:21 UTC,Please give the URL of the published page that you consider is wrong.
1717701,2017-09-17 09:35:27 UTC,I added the link. Kindly check
1717701,2018-02-14 07:54:16 UTC,"@mish24 When I read the link, gedit is one of GUI editors in Linux environment and other editors such as Atom and vim are also mentioned. Just changing from less into gedit would not guarantee consistency I think. Moreover, less is basic command in Linux/Mac environment (without installation) whereas gedit requires GUI environment."
1717701,2019-05-16 16:03:35 UTC,"You don't need an editor, you just need to see the content. less is perfect for this - we expect a command line elsewhere."
1717708,2017-11-17 19:11:43 UTC,"Sigh, in bullet (1) of comment #10, I obviously didn't mean to link this same LP entry. Instead I meant <https://bugzilla.tianocore.org/show_bug.cgi?id=785>. Sorry."
1717708,2020-08-12 11:54:07 UTC,No need to keep this open any longer (no activity for 19 months). Please follow the links captured above to the past discussions. There's nothing new to add wrt. the situation.
1717708,2019-01-11 08:27:54 UTC,"I encountered same problem. No video output when I start win10 with kvm enabled on arm64 host.
Is there any update?"
1717708,2018-04-14 17:33:17 UTC,Has anyone been able to find a workaround to run this with KVM from an ARM64 host? What exactly is the problem with Qemu/KVM/Aarch64 that stops KVM from working - and are any efforts being made to get around it?
1717708,2018-01-08 01:23:38 UTC,"@Andrew can you upload these three drivers somewhere for the lazy people?
thanks.."
1717708,2017-11-20 23:11:44 UTC,"@Laszlo, I got the binaries from someone else, but they from a parallel build system... nothing particularly special: some preprocessor rules to build against the newer WDK, and also it was just those three drivers (netkvm, vioinput, viostor). I imagine you can get the same result by tweaking the VS-based build (sln/vcxproj files), but haven't tried. Sorry that's not terribly helpful."
1717708,2017-11-20 16:01:05 UTC,"@Andrew: are you implying that you successfully rebuilt the virtio guest drivers for ARM64 Windows? If that's the case, could you please share specifics about the build setup? I'm not the one working on the virtio GPU driver for Windows, but I assume your aarch64 build steps would apply to that driver similarly. Thank you."
1717708,2017-11-18 05:21:08 UTC,"I just noticed this bug via qemu-devel. For the record, recent QEMU (2.11-rc1 and later) can run recent arm64 Windows images using -M virt and the virtio storage/input/networking drivers in the guest. I was using older UEFI build that still includes the VGA framebuffer support. (I only just learned via this bug that it had been removed, but as PeterM pointed out this isn't the right place to discuss it.)"
1717708,2017-11-17 19:06:45 UTC,(1) See also <https://bugs.launchpad.net/qemu/+bug/1717708>.
1717708,2017-11-14 14:40:17 UTC,"I know it won't work in KVM. I'm arguing that something not working in KVM is not grounds for removal from the UEFI image, since qemu != KVM."
1717708,2017-11-14 13:43:47 UTC,"Plain linear framebuffer won't work with KVM, unfortunately. The best fix is for Windows to support virtio-gpu, then it will work in KVM as well as pure emulation."
1717708,2017-11-14 13:35:41 UTC,virtio-gpu-pci will not work for booting Windows.
1717708,2017-09-18 12:49:41 UTC,"The virtio-gpu is not Linux specific. If windows could include the device driver, it can be used on windows as well like other virtio devices on windows x86."
1717708,2017-09-18 04:30:41 UTC,"thanks Peter..
Shannon,
using your launch arguments seems to go as you write..
nice progress.."
1717708,2017-09-17 14:10:22 UTC,"""D:\Program Files\qemu\qemu-system-aarch64.exe"" -device virtio-scsi-pci,id=scsi -drive if=none,id=cd,file=\path\to\iso -device scsi-cd,drive=cd,bootindex=0 -m 2048 -cpu cortex-a57 -smp 4 -machine virt -device virtio-gpu-pci -bios ""QEMU_EFI .fd"" -device usb-ehci -device usb-kbd -device usb-mouse -usb"
1717708,2017-09-17 11:00:08 UTC,"It's expected behaviour that you don't have any video output, because by default the ""virt"" board has no graphics device. Most people use a serial console here. It should also be possible to set it up with a virtio gpu graphics device, but I don't know whether Windows supports that."
1717708,2017-09-16 18:23:15 UTC,"I meant: ""says guest has not initialized the display"".."
1717708,2017-11-14 14:58:18 UTC,"If you want to argue for things being in UEFI images, you're in the wrong place, because this is the QEMU bug tracker, not a UEFI one..."
1717713,2020-07-26 13:48:25 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1717713,2020-09-25 04:17:20 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1717733,2018-02-11 18:42:05 UTC,It looks this bug disappear now. I will proceed to close this bug if there is no further reports.
1717733,2017-09-27 07:51:22 UTC,"@kien, my devstack crashed and i am trying to make up again. i ll share the information once it got up."
1717733,2017-09-29 09:22:12 UTC,"@kien, kindly check the following things in your environment:"
1717733,2017-09-21 07:29:59 UTC,cooldharma06: Thanks for your feedback. I will try it in another testing environment to make sure.
1717733,2017-09-21 06:39:25 UTC,"i think recheck is needed for this bug, because in my environment its working fine."
1717733,2017-09-23 11:24:31 UTC,"cooldharma06: I have re-checked, the same bug still happens. In my setup, /etc/neutron/dhcp_agent.ini: dnsmasq_local_resolv = True and even set dnsmasq_dns_servers = 8.8.8.8, 8.8.4.4, nothing change."
1717735,2017-09-17 00:50:03 UTC,Sorry for the typo in the title.
1717735,2017-09-17 04:33:24 UTC,An additional note.
1717735,2017-09-17 22:55:45 UTC,Thanks bob...
1717735,2018-04-06 09:46:22 UTC,What is the problem with using KIPRJMOD (not KISYSPROJ)?
1717735,2018-10-31 13:02:11 UTC,This kinda-sorta works now in master (pre-5.1) - you can add the (non-project) .pretty FP/3D libraries to the 3D search paths in the Configure Paths dialog. For example:
1717735,2018-10-31 13:14:57 UTC,"Also, the 3D cache can be upset by this. Imagine both mylib.pretty and otherlib.pretty have a file called ""part.step"". Searching ""./part.step"" in both libs will always return the first one to be cached."
1717735,2019-08-16 08:28:22 UTC,It tried to make KISYS3DMOD a relative path and that doesn't work. Is there a reason for this?
1717735,2019-08-16 08:48:15 UTC,Did you do as in #4?
1717735,2019-08-16 09:59:58 UTC,Yes. KISYS3DMOD = ${KIPRJMOD}/k_kicad_libs/models.3d does not work
1717735,2019-08-16 13:13:55 UTC,I filed a seperate Bug because I think this is more a general issue than of the footprints itself
1717743,2017-09-29 03:42:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717746,2017-09-17 06:02:31 UTC,Also changed ex-orange line between panes to red.
1717746,2018-08-12 14:43:28 UTC,Good find.  This functionality was broken.  I'm deprecating the interactive mode of this command.  Thanks!
1717746,2020-04-06 02:45:15 UTC,Thank you very much Dustin!
1717752,2017-10-20 11:00:47 UTC,"But what I describe above is not enough. Because netaddr module use index files, generated from oui.txt and iab.txt"
1717752,2017-10-23 13:54:20 UTC,You might like to forward this bug to Debian and/or the python-netaddr [0] project itself.
1717770,2017-09-17 12:02:33 UTC,This appears to be fixed in the latest version on master.
1717778,2017-11-07 16:46:50 UTC,"Hello,
Do you dual boot with windows? I have encountered this issue before and it was solved by switching on bluetooth in windows and then booting into mint. Maybe mint has trouble switching devices on which are disabled by windows..."
1717783,2017-11-16 08:24:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717783,2017-11-16 08:37:38 UTC,"This seems related to #1723422 for me. Fixing that issue on my system, this problem disappeared."
1717783,2017-11-18 16:07:13 UTC,"I have the same bug in Ubuntu 16.04 for a few days now. Might be related to the last update of ubuntu-desktop, but I can't figure out how to downgrade to the previous version. I'm not sure if #1723422 also applies to 16.04, as I don't have the package ubuntu-themes installed."
1717783,2017-09-17 14:55:34 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 __GI_abort () at abort.c:89
 __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x7f80195f38a8 ""!xcb_xlib_too_much_data_requested"", file=file@entry=0x7f80195f34cb ""../../src/xcb_io.c"", line=line@entry=732, function=function@entry=0x7f80195f38d0 <__PRETTY_FUNCTION__.14493> ""_XRead"") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f80195f38a8 ""!xcb_xlib_too_much_data_requested"", file=file@entry=0x7f80195f34cb ""../../src/xcb_io.c"", line=line@entry=732, function=function@entry=0x7f80195f38d0 <__PRETTY_FUNCTION__.14493> ""_XRead"") at assert.c:101
 _XRead (dpy=0x556e9be16480, data=data@entry=0x7f7fec378ba0 ""\370\006"", size=size@entry=176) at ../../src/xcb_io.c:731"
1717786,2017-09-20 07:42:34 UTC,"The syntax should be neutron.pool.v6.name. But it is just a minor.
This bug happens because V6 stills False and Pool is empty. I have raised an issue in moby/moby, wait for Moby developers confirmation:"
1717792,2020-08-24 21:39:11 UTC,"I doubt Deja Dup has done anything special to fix this since it was reported, but gvfs might have gotten some fixes. Does this work any better these days, if you are still using Deja Dup?"
1717792,2020-10-24 04:17:30 UTC,[Expired for Déjà Dup because there has been no activity for 60 days.]
1717792,2017-10-29 16:06:45 UTC,"Well, no, not fixes :/"
1717792,2017-09-17 22:40:09 UTC,I am having trouble reproducing this.
1717792,2017-09-18 17:56:56 UTC,Is the network smb server up and available when you get these messages?
1717792,2017-09-18 17:55:53 UTC,And similar to old bug 1351025.
1717792,2017-09-18 17:52:57 UTC,This does sound similar/related to bug 1715582 though.
1717792,2017-10-16 08:15:38 UTC,I updated to 36.2 and this seems fixed now
1717793,2018-12-11 19:10:06 UTC,Confirmed Evergreen version 3.2.1
1717797,2017-09-17 19:01:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1717804,2018-04-10 07:35:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717807,2019-04-24 18:52:42 UTC,Bug still present in Ubuntu 18.04. Bug logged at Remmina for top bar connection list and were directed here. When too many connections is added the list goes over the screen and no scroll bar aprears.
1717807,2018-03-11 20:47:05 UTC,"I also experience this problem. In the ownCloud menu, lower items, e.g. the activity monitor or the close app button, are inaccesible. See attached screenshot."
1717807,2018-03-08 23:18:57 UTC,We also experience this in our application.
1717807,2018-06-19 11:47:19 UTC,"I also experienced this bug with a different clipboard history indicator. Also, these kind of applications (those that keep a history of clipboard contents for easy retrieval) are relatively common, so I disagree with the ""low"" priority categorization of this bug, which literally makes any indicator that is higher than your given screen height useless. As the sole purpose of this plugin is to display and allow interaction with indicators, such an issue seems fairly important. :-)"
1717807,2017-09-22 13:09:48 UTC,"settings to low, having that long menus is not the most common case"
1717807,2017-09-22 12:54:07 UTC,See also https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/69
1717807,2017-09-18 16:51:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717807,2017-12-12 08:01:42 UTC,"I have the same problem with remmina and long menu whit many items.
this way the applet become useless for me: I cannot open the sub-menu to start the connection because there is non place to shift the menu down and let the sub-menu to open."
1717808,2017-09-17 20:26:34 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fd565b24906 ""*** %s ***: %s terminated\n"") at ../sysdeps/posix/libc_fatal.c:181
 __GI___fortify_fail_abort (need_backtrace=need_backtrace@entry=false, msg=msg@entry=0x7fd565b248ee ""stack smashing detected"") at fortify_fail.c:33
 __stack_chk_fail () at stack_chk_fail.c:29
 UFRaw::Lensfun::Interpolate (this=this@entry=0x559a42189260) at ufraw_lensfun.cc:765
 UFRaw::LensModel::Event (this=0x559a41eed410, type=<optimized out>) at ufraw_lensfun.cc:155"
1717810,2017-10-30 12:15:14 UTC,Moved here:
1717810,2017-11-03 10:57:32 UTC,"Should already have been fixed in the latest version here: https://github.com/mnemosyne-proj/mnemosyne , as I cannot reproduce it."
1717814,2017-09-17 21:18:09 UTC,Downloaded and installed OLDER NVIDIA Driver Version #22.21.13.8541 from NVIDIA dated 08/21/2017 also is compatible and WHQL certified and OR works perfectly UNWINDOWED again!!!!
1717814,2017-09-19 01:23:44 UTC,"Well, that having been said, today I downloaded a new file of a route from Train-Sim.com - can99v301.zip and can99v302.zip - the latest iteration of the *   CN Blackfoot Subdivision    *
*     Route for Microsoft Train Simulator /Open Rails    *."
1717814,2017-09-24 18:43:22 UTC,"1.) By reverting to an OLDER NVIDIA driver (August 2017) the spanning/windowed issue has been avoided.
2.) The issue with the file of a route from Train-Sim.com - can99v301.zip and can99v302.zip - the latest iteration of the * CN Blackfoot Subdivision *
 * Route for Microsoft Train Simulator /Open Rails *.
Has apparently also been resolved by applying the ""FIX"" found in the TS Forum - using the original route (can99) TERRTEX folder instead of the newer one."
1717821,2017-09-26 08:11:33 UTC,"Thanks,   It is now good."
1717821,2017-09-24 13:50:16 UTC,"Hello
So I use it. it  is good  but it was necessarry for me to do this thing"
1717821,2017-09-24 02:34:26 UTC,Fixed in 4ppa47.
1717821,2017-09-24 17:30:26 UTC,thx Bougron for the feedback.
1717821,2017-09-20 08:53:56 UTC,"Hello.
To days, on the french   https://forum.ubuntu-fr.org/viewtopic.php?pid=21797923#p21797923 forum i saw"
1717821,2017-09-19 16:15:54 UTC,"Hello
If only one disk
     Windows has a FAT32 partition
     Some applications of the free world format this partition by forgetting that windows is inside.
     I think one day windows will do the housework when one will need room because it installs full of new languages in this structure.
     A constructor (HP) was able to block this partition in writing for ubuntu. FSCK launched by boot-repair could do nothing. The solution was to back up the windows directory, remove and recreate the partition and to put the windows software back before repairing with boot-repair.
    I chose to install refind in another partition."
1717821,2017-09-19 16:13:56 UTC,"Hello
When there is only  one disk
   i prefer another partition because
     Some constructor (HP) look this partition  and even an fsck can't repar this, Is was absololuty necessary to do this thing manually   (see some french discussion)
     Some tools,  forget that the ESP partition can contains files for windows and format this partition if bad paraameters are used
     Pearheaps, one day, microsoft will destroys also this partition
When there are two devices, some users install ubuntu on the second device.
    actually, if the first"
1717821,2017-09-17 23:19:51 UTC,"To be sure I understand,
- if Windows and Ubuntu are on the same disk, and there are 2 ESPs on this disk, you suggest that Boot-Repair installs GRUB EFI files in the ESP that does not contain Windows EFI file, correct ?
- if the Windows ESP is not on the same disk as the Ubuntu ESP, what do you suggest ?"
1717821,2017-09-23 09:50:13 UTC,"Hello
Don't forget,   on external disk, it is also necessary to write /EFI/ubuntu/grubx64.efi on /EFI/boot/bootx64.efi  ( https://doc.ubuntu-fr.org/tutoriel/installation_sur_disque_usb#specificites_support_usb_efi )"
1717825,2017-09-17 23:58:22 UTC,I have updated the patches to do this in the wip/rancell/snap-auth-3-20-rebase git branch.
1717826,2017-09-18 07:43:17 UTC,"supplement high-availability.rst about cinder
for cinder-volume is making progress in Active/Active HA mode by distributed lock mechanism."
1717826,2017-09-18 08:34:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/504880"
1717826,2018-09-28 11:14:15 UTC,"Hi, any update on the proposed change?"
1717826,2019-11-20 04:17:38 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1717831,2021-02-25 07:06:20 UTC,Review: https://review.opendev.org/c/openstack/charm-hacluster/+/766222
1717831,2019-01-07 11:36:42 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/500655
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.
Feel free to restore it again if you want to pick up and continue the work."
1717831,2019-09-19 13:31:11 UTC,The set of actions should also include the ability to clear failed actions (crm_resource -P).
1717837,2017-09-18 04:14:33 UTC,Fixed in newton with backport https://review.openstack.org/#/c/504378/
1717837,2017-09-21 15:25:10 UTC,"Reviewed:  https://review.openstack.org/504378
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=3b32b44d87dc387a475ce09b569c7dcb5ebae869
Submitter: Jenkins
Branch:    stable/newton"
1717845,2017-09-27 17:28:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717856,2017-09-18 07:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1717856,2018-02-06 09:38:36 UTC,"Tested with one of the laptop in the cert lab. (201307-13930)
This issue can be reproduced with 3.2.0-131 but not with 3.2.0-133 in the proposed pocket."
1717856,2018-09-12 18:30:24 UTC,"Hi Sam, still an issue?"
1717856,2018-09-13 10:48:22 UTC,This issue can be reproduced on that specific system here.
1717856,2019-11-12 23:39:00 UTC,ESM for Precise ended in April 2019.
1717859,2017-09-24 07:56:01 UTC,What is the state of such handbrakes at game start?
1717859,2017-09-24 07:59:27 UTC,"In other words, what does the .eng file say about the starting state of such handbrakes?"
1717859,2017-09-24 09:30:51 UTC,"These are cars in sidings, so handbrakes are on."
1717859,2017-09-24 09:32:31 UTC,"Its the wagon handbrakes that are not reset with <shift> :
How ever <shift> ? does reset them."
1717865,2020-09-14 07:34:37 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1717865,2017-09-18 08:03:35 UTC,apport information
1717865,2017-09-18 08:03:32 UTC,apport information
1717865,2017-09-18 08:03:31 UTC,apport information
1717865,2017-09-18 08:03:29 UTC,apport information
1717871,2017-10-09 07:28:28 UTC,Here's the state transition diagram of Nova: https://docs.openstack.org/nova/latest/reference/vm-states.html
1717877,2017-09-18 19:37:30 UTC,">I am interested in looking into fixing this issue myself, but I would need a bit of tutoring (to help locate where the relevant pieces of code sit in the repo).
"
1717878,2017-09-18 09:40:09 UTC,"StacktraceTop:
 get_fallback_session_name (self=self@entry=0x55c1e2529580) at gdm-session.c:593
 get_default_session_name (self=0x55c1e2529580) at gdm-session.c:619
 get_session_name (self=self@entry=0x55c1e2529580) at gdm-session.c:2426
 get_session_filename (self=self@entry=0x55c1e2529580) at gdm-session.c:2999
 gdm_session_is_wayland_session (self=self@entry=0x55c1e2529580) at gdm-session.c:3014"
1717878,2017-09-18 09:48:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717878,2017-09-18 09:49:01 UTC,"I think this looks like the same as:
https://errors.ubuntu.com/problem/b8e7721d0034b2c4a5ddafcac2e1cc55703f9dbd"
1717878,2019-10-07 03:14:39 UTC,See also bug 1846895
1717878,2019-10-07 03:20:40 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/55afdb022e0f09e32692656f5ec80985acf385cc"
1717895,2018-03-28 23:22:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717895,2020-07-29 14:42:20 UTC,"Hi Jeroen,
I was looking at jq and if we could/shoudl support it more deeply.
As part of that I was checking open bug and found this one.
Probably not important for anyone else in the community since then nothing happened :-/"
1717916,2017-09-19 06:21:37 UTC,@Matt thanks for looking on this.
1717916,2017-09-18 19:45:24 UTC,"tempest.scenario.test_server_multinode.TestServerMultinode.test_schedule_to_all_nodes has existed in Tempest for almost 2 years now, why is this just a recent issue? Or was the test always blacklisted before this for Ironic CI jobs and is just now being investigated?"
1717916,2017-09-18 19:41:17 UTC,"The problem in this utility code is we don't know if there is 1 or more nodes on the host...and we don't want to look that up every time, but maybe that could be optimized to only check if force_hosts is specified and force_nodes isn't."
1717916,2017-09-18 19:37:19 UTC,"To be clear, the issue here is that force_hosts is set but force_nodes is not, correct? So what you want is for the reschedule to try other nodes on the forced host. The linked code is not accounting for the 1:M relationship between host:node for Ironic."
1717916,2017-09-18 12:17:11 UTC,related nova patch:  https://review.openstack.org/#/c/499545/
1717918,2019-04-29 09:37:08 UTC,When I run Tempest test I met the same problem when I set reauthentication_auth_method = trusts.
1717918,2017-10-10 20:54:53 UTC,This might be something we can improve in the keystone documentation. It appears keystone has some limitations on what you can do with impersonation and redelegation [0].
1717918,2017-09-20 03:03:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/505476"
1717918,2017-09-19 16:32:14 UTC,No it would not work as by default we use the access plugin[1] with the token_info we get from the auth middleware.
1717918,2017-09-19 16:02:14 UTC,"Rabi, thanks for your comment.
From the link you pasted[1], The re-authentication happened in keystone that looks like working for all kinds keystone session(not only trusts auth plugin but also [2]). If that we could leave reauthentication_auth_method = """"(re-authentication will still work). Please correct me if anything wrong."
1717918,2017-09-19 12:59:19 UTC,"Yeah, that's in heat (we use trusts auth plugin with keystone session which would request for another token if the token expires(401][1]. But if sahara uses heat provided trust token to again request for a token, then it would fail."
1717918,2017-09-28 09:39:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/508099"
1717918,2017-09-19 08:33:31 UTC,"> We also need to modify heat to create trust. Add allow_redelegation=True parameter
"
1717918,2017-09-19 08:22:24 UTC,"When reauthentication_auth_method = trusts, heat uses trust token to build sahara client. However, sahara uses heat`s trust token to build nova session client without auth_ref."
1717918,2017-09-19 07:48:18 UTC,"When reauthentication_auth_method = trusts, heat uses trust token to build sahara client. However, sahara uses heat`s trust token to build nova session client without auth_ref."
1717918,2017-09-19 05:13:15 UTC,"Hi Rabi, I have retried it on my env (pike RDO) and it can be reproduced 100%."
1717918,2017-09-18 12:51:16 UTC,Is it the last sahara master? Is it pike? What is the content of sahara.conf? Can you please share some details from your deployment?
1717918,2017-09-19 02:35:51 UTC,"AFAICT, from heat point of view it should work from newton onwards after https://github.com/openstack/heat/commit/cd125f328e3e4e9f517278b04347515eba380d5a#diff-661fd41a079826552bb7477bd817ea8f landed."
1717918,2017-09-18 14:52:39 UTC,"Luigi, this problem affects us from mitaka to stable/pike at least. I don't have master branch to test it right now.
This env is latest RDO deployed by packstack. and the sahara.conf is the default value without any change."
1717918,2017-09-19 12:33:44 UTC,"Hi Rabi, AFAIK reauthentication_auth_method =trusts was introduced in[1] to defeat token expiry by reauthentication. So if set reauthentication_auth_method = """", the long-running stack creation will be failed by token expiry? Could you help explain it?"
1717920,2017-09-26 16:33:50 UTC,This bug was fixed in the package linux - 4.13.0-12.13
1717921,2017-10-19 22:15:35 UTC,"It's getting hard to get tests pass because of this one. I know subprocess uses nonblocking IO to get stdout/stderr, I suspect our issues can be traced to that somehow."
1717921,2017-10-19 22:14:35 UTC,"And another, different PR, different test:"
1717921,2017-10-19 22:12:34 UTC,"I'm seeing this all over the place, in different tests, and unrelated PRs. Here's a full one:"
1717923,2017-09-18 23:38:48 UTC,"Nicolás, this is the first bug reported for this issue in Launchpad that I am aware of so there's no need to mark this as a duplicate."
1717923,2020-06-05 04:54:56 UTC,This looks like an issue that was fixed in 20.04 this year. Can anyone confirm if it still happens on a fully updated 20.04 system?
1717923,2019-07-10 01:48:49 UTC,Bug kept open based on Stewart's comment #10.
1717923,2019-07-09 13:39:13 UTC,"I am seeing an issue with mutter-2 in Ubuntu 18.04, a fresh installation on Virtualbox 6.08.  The host machine is a Mac Pro on macOS 10.14.5 Mojave."
1717923,2018-08-15 04:02:55 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1717923,2017-10-06 20:11:29 UTC,So the commit https://github.com/GNOME/mutter/commit/43eeb009ce78588db9fba48574f377629d5de1aa avoids invalid configurations to be migrated. As for the crash nor me or Jonas can reproduce it.
1717923,2017-09-18 17:09:55 UTC,"Thank you Jeremy! That did the trick! It seems it is that same bug.
Should I mark this bug report as duplicated of some other?"
1717923,2017-08-23 12:13:57 UTC,"(In reply to Jonas Ådahl from comment #2)

> Could you provide a backtrace? I can't reproduce any crash when using your
> monitors.xml, I only see the ""not adjecent"" error, then everything works
> anyway.
"
1717923,2017-09-18 15:21:49 UTC,"Just to be clear: the previous is an old (from last wednesday) crash that happened when trying to enter the wayland session. In that time, after I logged on xorg, a crash report appeared.
Since then, in all my last tries, wayland session login failed silently, without a crash report."
1717923,2017-09-18 15:19:48 UTC,This is on real hardware. I am using an hybrid Intel Ironlake Mobile / AMD Redwood notebook. It should boot using the Intel GPU.
1717923,2017-09-18 14:48:36 UTC,"Thank you for your bug report, is that on real hardware or in a vm? What videocard/driver do you use? Do you get any report in /var/crash?"
1717923,2017-08-29 13:02:45 UTC,"(In reply to Jeremy Bicha from comment #3)

> (In reply to Jonas Ådahl from comment #2)
> > Could you provide a backtrace? I can't reproduce any crash when using your
> > monitors.xml, I only see the ""not adjecent"" error, then everything works
> > anyway.
>
> Could you show me how to do that? Ubuntu's apport did not automatically
> catch a backtrace for gnome-shell/mutter.
"
1717923,2017-08-23 01:21:33 UTC,"Created attachment 358188
monitors.xml"
1717923,2017-08-23 02:26:06 UTC,"Could you provide a backtrace? I can't reproduce any crash when using your monitors.xml, I only see the ""not adjecent"" error, then everything works anyway."
1717923,2017-08-23 01:26:30 UTC,"I believe I had copied my ~/.config/monitors.xml from one or two previous computers. Currently, I don't use any external monitors with my laptop."
1717923,2017-09-18 16:22:23 UTC,Please try moving your ~/.config/monitors.xml file somewhere else. This sounds like https://bugzilla.gnome.org/786660
1717926,2018-06-07 17:52:49 UTC,"assigning to desktop team, if it's wanted in main."
1717926,2018-08-10 17:29:59 UTC,"This is a reasonable request, ack from the desktop team."
1717926,2018-09-13 13:17:24 UTC," - tests are run during the build
 - packaging looks good
 - missing symbols file
 - in any case, this library processes user input, should
   get a course security review."
1717926,2018-11-13 04:17:30 UTC,[Expired for libzmf (Ubuntu) because there has been no activity for 60 days.]
1717930,2018-11-13 04:17:31 UTC,[Expired for libstaroffice (Ubuntu) because there has been no activity for 60 days.]
1717930,2018-09-13 16:01:26 UTC,"Yes, we had the discussion but it wasn't resolved. There is a difference in opinion among Ubuntu Developers on whether it should be required. I'm ok with this specific question being forwarded to the Tech Board."
1717930,2018-09-13 15:19:36 UTC,"it is recommended in the things to check for, when a package goes to main.  We had this discussion before.  This is especially important for packages where the upstream isn't that pedantic with symbols changes."
1717930,2018-09-13 12:53:52 UTC,"- the package doesn't have a test suite.  Is there any test that can either be
  run as a simple test, either during the build or the autopkg test?
- The build log is non verbose, not showing compiler options.  This is now at
  least recommended by the Debian policy. Please could you add that?
  Or run the tests that are included in the package?"
1717930,2018-09-13 13:16:08 UTC,forgot:
1717930,2018-08-10 17:42:02 UTC,"This is a reasonable request, ack from the desktop team."
1717930,2018-06-07 17:53:49 UTC,"assigning to desktop team, if it's wanted in main."
1717930,2018-09-13 14:05:51 UTC,There isn't consensus in Ubuntu or written policy that symbols files are required for C++ libraries in main.
1717943,2017-10-17 23:59:04 UTC,"Reviewed:  https://review.openstack.org/509441
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1d2cfc4f5689fa1d88fb9aa13be14a6b7cc17a89
Submitter: Zuul
Branch:    stable/newton"
1717943,2017-11-15 01:10:43 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1717943,2017-11-15 01:06:52 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1717943,2017-11-01 00:20:19 UTC,This issue was fixed in the openstack/nova 14.0.9 release.
1717943,2017-10-24 12:42:36 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1717943,2017-10-24 11:47:14 UTC,"Reviewed:  https://review.openstack.org/509439
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1a1b65fac9ed429516338bc468144bf742c94824
Submitter: Zuul
Branch:    stable/pike"
1717943,2017-10-23 07:37:04 UTC,"Reviewed:  https://review.openstack.org/509440
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c88f3f75d827610be925f68b076253dba76cfcc
Submitter: Zuul
Branch:    stable/ocata"
1717943,2017-10-04 13:26:29 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/509441"
1717943,2017-09-18 19:33:26 UTC,Since gerrit is currently down I've attached a patch.
1717943,2017-10-04 13:25:44 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/509439"
1717943,2017-09-21 13:34:05 UTC,"Reviewed:  https://review.openstack.org/504978
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=963bf956ce93ba02bf9f38f979fe914d090b76d4
Submitter: Jenkins
Branch:    master"
1717943,2017-09-19 00:11:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/504978"
1717943,2017-09-18 19:33:06 UTC,Another warning is emitted if the following is missing from the [DEFAULT] section of nova.conf.
1717943,2017-09-18 19:31:54 UTC,"To recreate, configure nova.conf to set:"
1717943,2017-09-18 19:26:53 UTC,This goes back to https://github.com/openstack/nova/commit/590d40c in mitaka.
1717943,2017-09-18 19:09:44 UTC,"I'm not sure what ""whitelisted"" means here - does that mean it should simply be listed here?"
1717943,2017-10-04 13:26:14 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/509440"
1717944,2017-10-12 07:30:37 UTC,"In Ubuntu MATE 17.10 onwards all layouts, other than Traditional, use Indicators. Consequently the fcitx applet menu looks correct when Indicators are available but doesn't use QPA style hints when it falls back to the old style tray applet mode."
1717944,2017-09-23 01:33:06 UTC,"Hello
Can you reproduce after install & update?"
1717944,2017-10-12 07:26:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717951,2017-10-06 13:44:41 UTC,"amano, please file a separate bug for the cups issue."
1717951,2019-03-15 16:40:49 UTC,"As Sebastien Bacher pointed out, ImageMagick can be removed for good now as CUPS does no longer depend on it in Disco."
1717951,2019-03-11 18:43:13 UTC,Filed https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1819503
1717951,2019-03-10 17:09:49 UTC,"amano, please open a new bug for new issues instead of commenting on old closed bugs."
1717951,2019-03-10 14:33:40 UTC,Hmm. I upgraded to Disco today and the icon is back. Is that expected?
1717951,2018-09-07 15:29:04 UTC,"Martin, please open a new bug with specific details."
1717951,2018-04-05 10:27:47 UTC,"while I agree with removing, imagemagick is used for printint and in several graphics applications, I would propose to get rid of a particular file from the imagemagick package: /usr/lib/mime/packages/imagemagick-6.q16"
1717951,2017-10-06 07:27:58 UTC,"While the visual side of this bug is fixed now (the ugly wizard-icon is gone from the launcher), the usability side is still alive:"
1717951,2017-10-04 02:00:59 UTC,"Here's a patch for ubuntu-settings to hide the Display app from the Ubuntu and Ubuntu on Xorg desktops. This is similar to what Ubuntu Budgie, Ubuntu MATE and Ubuntu GNOME already do."
1717951,2017-10-04 11:09:10 UTC,"On Wed, Oct 04, 2017 at 02:00:59AM -0000, Jeremy Bicha wrote:

> Here's a patch for ubuntu-settings to hide the Display app from the
> Ubuntu and Ubuntu on Xorg desktops. This is similar to what Ubuntu
> Budgie, Ubuntu MATE and Ubuntu GNOME already do.
"
1717951,2017-09-18 21:49:25 UTC,Not a problem from a docs POV.
1717951,2017-09-20 06:15:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717951,2017-09-21 05:59:09 UTC,To add to the things mentioned above:
1717951,2017-10-05 13:03:32 UTC,This bug was fixed in the package ubuntu-settings - 17.10.17
1717951,2017-09-18 19:54:01 UTC,"The tools doesn't fit well in a modern desktop and can confuse user, sounds like a good idea to not list it by default"
1717951,2017-10-04 05:22:34 UTC,"Will that work for the gnome session (and gnome-on-xorg-session). Since imagemagick isn't “gnomey“ at all, it should be hidden there as well..."
1717951,2017-09-21 06:03:02 UTC,s/possibly/possibility
1717954,2017-09-18 16:18:16 UTC,Possibly same issue as in https://answers.launchpad.net/ubuntu/+source/apt/+question/284708
1717961,2017-09-18 17:38:11 UTC,Opened this in storyboard which I believe is the right place for issues for shade? https://storyboard.openstack.org/#!/story/2001203
1717977,2017-09-18 18:25:23 UTC,These lines from the DpkgTerminalLog are the important ones here:
1717978,2017-09-18 18:01:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1717983,2019-05-09 23:14:22 UTC,"ubuntu-meta retains a dependency on isc-dhcp-client for use in initramfs (via initramfs-tools integration), and application which will not be replaced by networkd for the foreseeable future."
1717983,2018-05-22 03:59:48 UTC,"Per /usr/share/sendmail/dynamic, /etc/dhcp3/dhclient-exit-hooks.d/sendmail is considered deprecated in favor of /etc/network/if-{up,post-down}.d/sendmail.  Therefore for sendmail's purposes, this is a duplicate of LP: #1718227."
1717983,2018-05-21 23:45:47 UTC,python3-maas-provisioningserver calls dhclient directly in order to do network discovery.  This does not need replaced with networkd integration.
1717983,2018-05-21 23:22:14 UTC,"""high"" for ddclient wrt the importance of the hook to the operation of the package."
1717983,2018-05-21 23:20:58 UTC,ddclient wants to send updated IP address information to the dyndns server when a new IP address is received from DHCP.
1717983,2018-05-21 23:17:43 UTC,"controlaula does not exist in Ubuntu beyond artful.  So invalid for bionic, and wontfix for artful."
1717983,2017-10-05 18:15:00 UTC,This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu3
1717983,2019-05-09 23:15:36 UTC,"Based on https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1717983/comments/9, marking this done for cloud-init."
1717983,2017-09-19 20:22:13 UTC,I opened bug 1718227.  for packages that ship if-up.d or if-down.d scripts.
1717983,2017-10-02 11:45:22 UTC,I believe all of the cloud-init is covered by https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1718029 and addressed by https://code.launchpad.net/~xnox/cloud-init/+git/cloud-init/+merge/331642
1717983,2017-09-19 04:04:20 UTC,Packages which depend on isc-dhcp-client do so because they invoke the dhcp client directly for their own purposes.  This will not change; systemd-networkd does not expose a dhcp client for direct use by other callers.
1717983,2017-09-19 04:15:07 UTC,madwimax is a network driver package (not a network manager) that invokes dhclient directly on events.  That looks like something that should be integrated with systemd-networkd somehow.
1717983,2017-09-19 04:38:42 UTC,avahi-autoipd's dhclient hook exists for stopping and restarting the avahi-autoipd daemon while other dhclient hooks are running.  I don't know why exactly it does this but I don't think there's going to be a relevant equivalent in systemd-networkd.
1717983,2018-05-22 00:23:54 UTC,"samba-common's dhclient hook needs porting.  Setting to 'medium' as this only affects dhcp-provided netbios nameservers and netbios scope, which are relatively uncommon options."
1717983,2017-09-19 04:42:12 UTC,"resolvconf is being dropped at the same time as ifupdown/isc-dhcp-client; there is no need to integrate it with systemd-networkd.
openresolv is an alternative implementation of resolvconf which has never been used in Ubuntu."
1717983,2017-09-19 13:09:24 UTC,"""I don't know.... I don't think.."" doesnt really seem like valid justification for marking Invalid on avahi.  I went looking a bit further.  I'm not exactly sure why it ties into dhcp hooks, but it also ties into ifupdown hooks."
1717983,2017-09-19 18:18:48 UTC,"On Tue, Sep 19, 2017 at 01:09:24PM -0000, Scott Moser wrote:

> ""I don't know.... I don't think.."" doesnt really seem like valid
> justification for marking Invalid on avahi.  I went looking a bit
> further.  I'm not exactly sure why it ties into dhcp hooks, but it also
> ties into ifupdown hooks.
"
1717986,2017-09-22 15:33:29 UTC,"I cannot reproduce the issue.
This is my .cnf file :
[client]
user=ptcheck
password=password
#ssl-cert=/tmp/12345/certs/client-cert.pem
#ssl-key=/tmp/12345/certs/client-key.pem
#ssl-ca=/tmp/12345/certs/ca.pem"
1717986,2017-10-04 17:54:08 UTC,I modified 'pt-table-checksum' and added a line similar to the following to hard code my SSL settings:
1717986,2018-01-07 20:46:50 UTC,"I've spent ages debugging this. I'm not really any further forward for a solution, but what I have found is that it appears to be a bug somewhere between the Perl DBD::mysql driver (which pt-table-checksum uses) and Mysql/Mariadb."
1717986,2018-01-07 21:19:38 UTC,"I don't know whether this is actually a bug with DBD::mysql, but I've opened a bug report there anyway: https://rt.cpan.org/Public/Bug/Display.html?id=124031"
1717986,2018-01-24 22:26:14 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1444
1717996,2020-07-31 18:47:51 UTC,"Pushed to master, rel_3_5, and rel_3_4 along with a little nudge to realign the tag layout. Thanks Tiffany and Jane!"
1717996,2019-10-26 04:18:04 UTC,"Works well for me, Tiffany.  Sign off branch here: user/sandbergja/lp1717996_bucketsvisiblelabel_signoff"
1717996,2019-10-21 19:09:43 UTC,Thanks Jane! New branch for further review: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=c2b1263b5119191df49fb6d6e5eb8a88bd5b4079
1717996,2019-08-19 16:53:35 UTC,"This looks good -- thanks, Tiffany and Dan."
1717996,2019-05-24 17:16:35 UTC,Works as intended.
1717996,2019-03-07 01:50:13 UTC,+1 for Shareable
1717996,2019-01-18 16:27:47 UTC,+1 for Shareable
1717996,2018-09-14 17:44:44 UTC,"Just agreeing that this should be changed to Shareable (with or without the word staff.)  Publicly visible implies that this turns the bucket into a bookbag, which would be cool, but isn't what happens here.  The priority is low because it doesn't affect functionality, but unclear wording like this requires repeated clarification."
1717996,2017-09-26 12:35:11 UTC,"I noticed that patron buckets say 'staff sharable.' This is better than publicly visible. I still prefer ""Shared"", but if we keep it as staff sharable, we should probably spell it as shareable. http://grammarist.com/spelling/sharable-shareable/"
1717996,2019-03-08 14:28:46 UTC,Patch for review here:
1717996,2017-09-26 16:16:41 UTC,"FWIW, the ""pub"" bool column on record and copy buckets allows them to be used in searches, as well as to be shared between staff.  Perhaps ""Shareable"" without ""Staff"" is best?  I'm OK with ""Shared"" if that's the consensus, but that suggests that they are directly accessible through some list interface, which isn't true today except by the owner."
1717997,2017-09-18 19:13:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1718009,2017-09-19 00:02:03 UTC,"Do we care that the api.snapcraft.io URLs redirect to a combination of public.apps.ubuntu.com and an Internap CDN URL, or is this purely about upload paths that are hardcoded in clients?"
1718009,2018-12-19 16:42:12 UTC,Getting https://api.snapcraft.io/api/v1/snaps/download/YbGa9O3dAXl88YLI6Y1bGG74pwBxZyKg_9.snap takes me to the following (redirections):
1718009,2018-12-21 05:17:05 UTC,api.snapcraft.io and Fastly are only used for downloads. Uploads still use upload.apps.ubuntu.com.
1718017,2017-09-18 19:42:25 UTC,Added LTrace Log
1718017,2017-09-18 19:50:10 UTC,Added Valgrind Log
1718017,2017-09-18 19:56:57 UTC,"StacktraceTop:
 match (eptr=0x561bf5b59940 ""\377\376;"", ecode=<optimized out>, mstart=0x561bf5b59940 ""\377\376;"", offset_top=2, md=0x7ffd373ad5c0, eptrb=0x0, rdepth=<optimized out>) at pcre_exec.c:5534
 match (eptr=<optimized out>, ecode=0x561bf5aa9e40 ""\203"", mstart=0x561bf5b59940 ""\377\376;"", offset_top=2, md=0x7ffd373ad5c0, eptrb=0x0, rdepth=<optimized out>) at pcre_exec.c:1080
 pcre_exec (argument_re=0x561bf5aa9e00, extra_data=<optimized out>, subject=<optimized out>, length=3, start_offset=0, options=8192, offsets=0x561bf5997b80, offsetcount=9) at pcre_exec.c:6936
 g_match_info_next (match_info=match_info@entry=0x561bf5cfea90, error=error@entry=0x7ffd373ad7e8) at ../../../../glib/gregex.c:734
 g_regex_match_full (regex=regex@entry=0x561bf5b54eb0, string=string@entry=0x561bf5b59940 ""\377\376;"", string_len=string_len@entry=3, start_position=start_position@entry=0, match_options=<optimized out>, match_info=match_info@entry=0x7ffd373ad7f0, error=0x7ffd373ad7e8) at ../../../../glib/gregex.c:1803"
1718018,2017-09-18 19:57:14 UTC,"Hi Rena.
You can hide Individual LPE in the eye icon in the LPE list. Is the most convenient way to do."
1718018,2017-09-18 20:03:31 UTC,"Sorry I missundertand. To make it we need a extensive list of suitable LPE, his parameters, and the desirable value with less CPU to be simplified, If not a complete and big list is better not complicate the UI with a limited scope feature that can cause errors to the user if not remember this setting is applyed."
1718018,2017-09-19 03:20:05 UTC,"The behaviour would have to be part of each effect's code, but the general idea is to have a global scale factor. Eg if set to 10%, the Stitch Sub-Paths effect would render 10% as many paths as the Number of Paths parameter says (only for display)."
1718018,2017-09-19 07:39:11 UTC,Yes all need to be in LPE code but drop some questions:
1718028,2017-10-04 10:05:22 UTC,"I'm pretty sure we do the right thing around normal ""juju
destroy-controller"", but probably ""juju kill-controller"" running from the
client isn't tracking VPC correctly. Certainly need some testing on regions
with multiple VPCs, and ensuring we don't kill the wrong machines, etc."
1718030,2017-09-19 20:27:49 UTC,libhybris (0.1.0+git20151016+6d424c9-0ubuntu26) artful; urgency=medium
1718030,2017-09-18 20:07:50 UTC,"Simon, you appear to still be committing changes upstream in <https://github.com/libhybris/libhybris>.  Do you care about this being fixed in Ubuntu 17.10?"
1718031,2017-09-19 08:55:43 UTC,Fixed in revision 191
1718040,2018-10-01 20:03:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718040,2020-04-12 14:46:30 UTC,Fixed via brisk-menu (0.6.0-1ubuntu1)
1718041,2017-09-19 02:59:03 UTC,"Given model config is set via a very different mechanism and usually had
very different meaning, I'm curious what you're looking for."
1718047,2017-09-22 21:35:09 UTC,"Right before requesting my LUKS password, while booting without splash and with $vt.handoff=7, I see these errors:"
1718047,2017-09-18 22:33:56 UTC,apport information
1718047,2017-09-22 04:42:03 UTC,The problem is unchanged in 4.4.0-96.
1718047,2017-09-18 22:34:05 UTC,apport information
1718047,2017-09-18 22:34:03 UTC,apport information
1718047,2017-09-18 22:34:00 UTC,apport information
1718047,2017-09-18 22:33:59 UTC,apport information
1718047,2017-09-18 22:33:57 UTC,apport information
1718047,2017-09-18 22:33:54 UTC,apport information
1718047,2017-09-18 22:30:01 UTC,"Alright, booting in recovery mode, and then ""continuing with regular boot"", leads to a freeze with a blank grey background.  (Disc activity continues for a long time.)  So, I am reporting against the kernel."
1718047,2017-09-18 22:33:49 UTC,apport information
1718047,2017-09-18 22:33:47 UTC,apport information
1718047,2017-09-18 22:33:46 UTC,apport information
1718047,2017-09-18 22:33:42 UTC,apport information
1718047,2017-09-18 22:33:41 UTC,apport information
1718047,2017-09-18 22:33:39 UTC,apport information
1718047,2017-09-18 22:33:37 UTC,apport information
1718047,2017-09-18 22:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1718047,2017-09-18 21:42:08 UTC,"apport <this_bug#> refuses to collect any more information, and I don't know what package/project to report this against.  Suggest what I might add and I'll be happy to do it."
1718047,2017-09-18 22:33:52 UTC,apport information
1718051,2020-05-28 05:20:16 UTC,I'm going to mark this bug as Invalid - I think there is just a missing relation in the bundle between a cinder-ceph application and nova-compute which is why the libvirt secrets are missing.
1718051,2020-05-28 07:40:50 UTC,"Reviewed:  https://review.opendev.org/731437
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=f200d8dff52367e15595e72f952ac53ba7713819
Submitter: Zuul
Branch:    master"
1718051,2020-05-28 05:59:51 UTC,As I added field-high removing - this is a UX improvement only now IMHO
1718051,2020-05-28 05:49:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/731437"
1718051,2020-05-28 05:17:15 UTC,Two block devices presented inside instance (1G size)
1718051,2020-05-28 05:18:37 UTC,OSC commands to setup two different volume types and create volumes - normal 'server add volume' used to attach to the instance.
1718051,2017-09-19 22:19:20 UTC,"Hi Drew, it is already possible to relate multiple storage backends to a single cinder-volume instance e.g. if i deploy a cinder principle and relate it to two cinder-ceph subordinates e.g. cinder-ceph-ssd and cinder-ceph-sata, I will end up with two pools called cinder-ceph-ssd and cinder-ceph-sata respectively and I am then able to to create two new storage types via the cinder api that then allow me two create volumes within one of those pools. Now, the part that is missing here is the ability for the ceph* charms to configure multiple pools on different types of storage BUT there's nothing stopping you from either doing that after the pools have been created by the charms OR creating the pools prior to deploying the charms and then deploying (if the pools already exist the charms will carry on regardless i.e. the create should silently fail and carry on)."
1718051,2020-03-04 03:25:39 UTC,"When multiple backends are in place and cinder is related to multiple cinder-ceph subordinates, there is an issue with the ceph-auth and  it requires to manually replace the user's definition in cinder.conf."
1718051,2020-03-06 22:52:37 UTC,"I dug a bit deeper and the root cause is clear.
Yes, it is possible to do all this, however it is impossible to attach the volumes from ""another"" backend to the instances.
The reason is that on the compute side only one libvirt secret is created:
root@ashg3ackvm05:~# virsh secret-list
 UUID                                  Usage
--------------------------------------------------------------------------------
 514c9fca-8cbe-11e2-9c52-3bc8c7819472  ceph client.nova-compute secret
 8078c8c3-61a0-48bb-a252-f069b7ac7c04  ceph client.cinder-ceph secret"
1718051,2020-05-28 05:16:16 UTC,Tested OK - see attach libvirt xml with RBD's attached from two different pools using different UUID's for secrets.
1718051,2020-05-28 04:55:15 UTC,OK so I'm stumbling at the first hurdle here - reproduction of the issue.
1718051,2020-04-03 13:49:29 UTC,tl;dr this should work we should fix this under a field-high
1718067,2020-04-19 15:21:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718087,2020-05-18 18:34:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718098,2017-09-19 09:27:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505133"
1718098,2019-05-07 07:59:18 UTC,"Change abandoned by Luka Peschke (<email address hidden>) on branch: master
Review: https://review.opendev.org/505133"
1718100,2020-05-19 17:39:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718119,2017-09-19 08:36:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718125,2018-02-12 13:49:51 UTC,This issue was fixed in the openstack/glance 15.0.1 release.
1718125,2017-11-01 23:58:20 UTC,"Reviewed:  https://review.openstack.org/515104
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bdd0b13633571ed0a72f32d3730c1f45b771acf7
Submitter: Zuul
Branch:    stable/pike"
1718125,2017-10-25 15:10:10 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515104"
1718125,2017-10-24 13:06:12 UTC,This issue was fixed in the openstack/glance 16.0.0.0b1 development milestone.
1718125,2017-10-10 16:43:49 UTC,"Reviewed:  https://review.openstack.org/505172
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=47f43070e002663b73408256dea852ee5578b502
Submitter: Jenkins
Branch:    master"
1718125,2017-09-28 19:37:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/508279"
1718125,2017-09-20 17:19:15 UTC,"Reviewed:  https://review.openstack.org/505123
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=2f8edeedc88491214d2502c5b1d17a155f452a47
Submitter: Jenkins
Branch:    master"
1718125,2017-09-19 11:14:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505172"
1718125,2017-09-19 09:03:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505123"
1718125,2017-09-29 16:08:27 UTC,"Reviewed:  https://review.openstack.org/508279
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=06af2eb5abe0332f7035a7d7c2fbfd19fbc4dae7
Submitter: Zuul
Branch:    stable/pike"
1718128,2020-02-06 21:41:12 UTC,"@ Andy,"
1718129,2018-09-19 12:55:29 UTC,"Hello,
On Fedora this bug has occured too. It is caused by use of python3 where Exception class error message can not be accesed by indexing. The patch i'm attaching fixes it."
1718129,2018-09-19 16:19:32 UTC,"The attachment ""Use msg variable instead of [0] to acces error message"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1718135,2019-02-06 20:11:38 UTC,Upstream report https://gitlab.gnome.org/GNOME/nautilus/issues/124
1718135,2019-11-05 14:03:08 UTC,I have experienced this bug in a clean 18.04.3 install.
1718135,2019-02-06 20:10:25 UTC,Error report https://errors.ubuntu.com/problem/68df9602b1c148589a9c540e5e143ac70ebadb63
1718135,2020-08-05 09:39:44 UTC,it's fixed in upstream git now
1718135,2018-10-12 13:42:33 UTC,Could you give specific steps you use to trigger the bug?
1718135,2018-10-12 11:29:19 UTC,Still issue in Ubuntu 18.10.
1718135,2017-10-17 20:11:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718135,2018-10-13 06:33:54 UTC,"I not sure what exactly crashed it, I just got similar crash on Ubuntu 18.10, that all I know."
1718135,2017-09-19 08:56:55 UTC,"StacktraceTop:
 nautilus_progress_manager_has_viewers (self=0x0) at ../src/nautilus-progress-info-manager.c:239
 on_progress_info_finished (self=0x5573e4f3ab70, info=0x5573e766ede0) at ../src/nautilus-toolbar.c:508
 g_closure_invoke (closure=0x5573e7700750, return_value=0x0, n_param_values=1, param_values=0x7ffc1cbcd410, invocation_hint=0x7ffc1cbcd390) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x5573e7c2f390, detail=detail@entry=0, instance=instance@entry=0x5573e766ede0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc1cbcd410) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x5573e766ede0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffc1cbcd5d0) at ../../../../gobject/gsignal.c:3391"
1718138,2019-12-25 04:17:29 UTC,[Expired for kolla because there has been no activity for 60 days.]
1718138,2019-10-25 17:06:39 UTC,"Update: In my case the issues were caused by using a xenial builder machine, which came with an older kernel, for which the linuxheaders package couldn't be found anymore.
I have started to build with a bionic machine and the installation ends without issues."
1718138,2019-10-24 22:08:59 UTC,"Correction: ""uname -r"""
1718138,2019-10-24 20:22:27 UTC,"Yes, ""uname -a"" is still present in rocky, stein and master:"
1718138,2017-09-19 15:59:37 UTC,"Marked as incomplete as bug seems to not be in kolla side, will expire in 60 days. Please, re-open the bug if still facing the same issue, also provide more information."
1718138,2018-11-20 08:22:57 UTC,"Typically, docker build get current kernel info. If want to build image on other kernel, I think should create ARG kernel_version to user can set manually. Example:"
1718138,2017-09-20 01:14:54 UTC,"@Eduardo,"
1718138,2017-09-19 15:58:12 UTC,"Could you please try again, probably the error was in during a repo update when the updaterepoxml id changed."
1718138,2019-03-28 10:38:13 UTC,Is this still a bug? If yes - please update.
1718158,2017-10-16 14:15:44 UTC,"For Xubuntu (20171016) I continue to see what is shown in screen shot. For Ubuntu, same date, I also see ""Categories"" but not ""Recent Releases"" so I will continue to report the bug against the relevant ISOs."
1718158,2017-09-20 04:46:09 UTC,My guess is the live session doesn't have any appdata to show apps.
1718158,2017-09-26 20:23:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718161,2017-09-28 09:22:19 UTC,"3.13.0-133.182~precise1 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1718161,2017-10-10 15:36:39 UTC,The package has been published and the bug is being set to Fix Released
1718174,2017-09-19 10:33:13 UTC,"Review in progress for https://review.opencontrail.org/35725
Submitter: Vedamurthy Joshi (<email address hidden>)"
1718174,2017-09-21 03:53:07 UTC,"Reviewed:  https://review.opencontrail.org/35725
Committed: http://github.com/Juniper/contrail-test-ci/commit/58f0253e7e6c663f486a72fcbbb5e1d7328b4f3d
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1718176,2019-06-09 13:24:17 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape/issues/300
1718176,2017-09-19 22:06:34 UTC,Even Windows 7 has confusing and erratic handling of moving new windows into the background when the GUI thinks they would obstruct your work (and it's not just me — it's a fundamental problem with Windows as a graphical interface).
1718176,2018-02-03 00:16:44 UTC,"Repeat occurrence on a different computer in Windows 10 1709 64-bit, 64-bit Inkscape."
1718176,2017-09-19 21:06:40 UTC,"I realised that this is what you were trying to do, but in reality it's not what happens. On the third attempt (while trying to track an unrelated bug) it worked, while on the previous attempt I clearly saw the windows display in the wrong order. On the first attempt I was completely oblivious to the first window for ages."
1718176,2017-09-19 19:47:43 UTC,I just confirmed on my system that the uninstaller window is positioned *in front* of the installer window by default (as is the intended and designed behavior).
1718176,2017-09-19 10:46:06 UTC,"I used PowerShell to delete all the files from the program directory while the installer was running (all except the locked uninstall log), and that knocked sense into it and got it to complete."
1718176,2017-09-19 21:42:30 UTC,"I'm on Windows 10 myself and it plays nice, so maybe I taught my OS better manners than you did ;-)"
1718188,2017-09-19 16:17:53 UTC,Please also check our bug triage conversation of today for the context.
1718191,2018-08-06 09:14:21 UTC,"Change abandoned by Dougal Matthews (<email address hidden>) on branch: master
Review: https://review.openstack.org/505206
Reason: Abandoning this patch per the Mistral Patch Abandonment guidelines
(https://specs.openstack.org/openstack/mistral-specs/specs/policy/patch-abandonment.html).
If you wish to have this restored and cannot do so yourself, please reach
out via #openstack-mistral on freenode or the OpenStack Dev mailing list."
1718192,2017-09-19 21:55:56 UTC,Seems like Glibmm updated to C++ 14 now...
1718192,2017-09-19 22:52:52 UTC,"Thank you very much!
Worked perfectly!"
1718197,2017-10-03 15:35:39 UTC,"We are also seeing Ansible fail tasks with ""UNREACHABLE"" errors which should not be happening:"
1718197,2017-10-03 17:41:54 UTC,"Disregard comment #1, let's track privilege escalation timeouts and unreachable hosts separately."
1718197,2017-10-03 17:44:56 UTC,https://bugs.launchpad.net/openstack-gate/+bug/1721093 for unreachable tasks
1718202,2018-02-18 16:54:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718204,2017-09-19 18:36:37 UTC,"Ahhhh, ok.  Now it's starting to make sense :) I was reading the bugs and MRs in the wrong order."
1718206,2017-09-19 14:48:16 UTC,Please submit this to <email address hidden>. Please also mention how you've tested it.
1718206,2017-10-07 10:43:30 UTC,"This patch is incomplete and not cover all possible variants (CPU with or without float point unit).
Here is better my version. https://pastebin.com/z4AcpbDu"
1718206,2017-10-08 18:00:06 UTC,"Hi jdobry,"
1718208,2017-10-05 14:05:59 UTC,"Need to track this; the shims will eventually go away, probably should target this to a release."
1718208,2017-09-19 15:50:48 UTC,"The lack of backwards compatible shims / references was an oversight which has been corrected in the latest beta release, so the ""won't build"" should no longer be true.  However, those shims / imports are deprecated so moving off of them would be best."
1718210,2017-09-19 19:01:17 UTC,"> For now we tell our users to stop using the AppStore version
> but that's not a good long term solution.
"
1718212,2017-09-19 21:52:39 UTC,What version of nova are you running? https://review.openstack.org/#/c/126237/ was proposed over 2 years ago and bug 1240200 was opened in 2013. So I would not consider this an extreme priority given how latent it is.
1718212,2017-09-29 06:57:42 UTC,"I should also add - instead of launching 1000 instances, they could create 1000 volumes, and assume they are 500GB each, run a dd command in them and do the same thing."
1718212,2017-09-29 06:48:35 UTC,"Hi,"
1718212,2017-09-27 12:17:22 UTC,"Unfortunately there is no easy way to calculate the ""reserved"" disk space, i.e. the non-OpenStack usage. In the VMware case this is not a static value, especially if you are using a shared datastore for both OpenStack and non-OpenStack workloads."
1718212,2017-09-19 18:33:15 UTC,"In https://review.openstack.org/#/c/441543/ a new virt driver method, get_inventory(), was added that ought to be able to help this problem once implemented in the vmwareapi virt driver. This will allow the disk, memory, etc to express a ""real"" ""total"" and a ""reserved"" value which represents any resources that are consumed by anything that nova does not track (e.g. pre-existing vms)."
1718212,2017-09-20 18:43:44 UTC,Rado is looking into this
1718212,2017-09-19 22:08:30 UTC,Thank you for responding.
1718212,2017-09-21 13:42:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506175"
1718214,2018-08-06 09:14:09 UTC,"Change abandoned by Dougal Matthews (<email address hidden>) on branch: master
Review: https://review.openstack.org/505287
Reason: Abandoning this patch per the Mistral Patch Abandonment guidelines
(https://specs.openstack.org/openstack/mistral-specs/specs/policy/patch-abandonment.html).
If you wish to have this restored and cannot do so yourself, please reach
out via #openstack-mistral on freenode or the OpenStack Dev mailing list."
1718224,2017-09-19 16:50:23 UTC,"Hi because Gtkmm problem compiling couldent try with last master here but with r. ""a113f4663e, 2017-09-05"" in debian this not happends."
1718224,2017-09-19 20:06:49 UTC,"Hi! I see the bug, is in the original path not on extra path. I go to fix it."
1718224,2017-09-19 20:21:57 UTC,Fixed in trunk in r.d86ea8daa7. Thanks for fill the report!
1718224,2017-09-19 20:42:27 UTC,"Wow, that was fast! Thank you, Jabier! (what is the 'power of triangle in'?)"
1718224,2017-09-19 20:50:35 UTC,"You are welcome. Is the median of all powerstoke knots, in triangle in the half I supose"
1718227,2018-04-16 11:16:15 UTC,Lets break this into use cases in Bionic:
1718227,2018-04-16 11:17:46 UTC,"Nice summary, but wrong bug - sorry for the noise here :-/"
1718227,2018-04-18 12:09:44 UTC,Tested on chrony which has a NetworkManager dispatch script that also works as a hook for networkd-dispatcher.
1718227,2018-04-19 11:56:23 UTC,Fix for chrony (following networkd-dispatcher change in bug 1765152) uploaded to bionic-unapproved as 3.2-4ubuntu4
1718227,2018-04-20 01:40:45 UTC,This bug was fixed in the package chrony - 3.2-4ubuntu4
1718227,2018-05-23 00:25:53 UTC,"controlaula was not shipped in 18.04.  Invalid for trunk, wontfix for artful and earlier."
1718227,2018-12-03 11:37:31 UTC,"Done in Chrony and setting to Won't Fix (to manage expectations) for NTP as it is universe only and if people care they can drop in networkd-dispatcher files to get it working (open for community contribution, but main will rely on chrony)."
1718227,2018-05-30 00:05:24 UTC,"even if not the default ntp implementation, I think this is still a valid bug task and should be tracked as such."
1718227,2018-11-15 16:29:05 UTC,This bug was fixed in the package openssh - 1:7.9p1-1
1718227,2018-04-04 14:40:36 UTC,"I heard people talk about it, but realized the tracker is missing a Task for openvswitch:
/etc/network/if-post-down.d/openvswitch
/etc/network/if-pre-up.d/openvswitch"
1718227,2019-12-11 15:12:14 UTC,An example of dns update after putting:
1718227,2019-12-11 17:33:02 UTC,For openvpn + systemd-resolve:
1718227,2019-12-11 17:43:21 UTC,"On 2019-12-11 12:33 p.m., Rafael David Tinoco wrote:

> For openvpn + systemd-resolve:
>
> With ""up / down"" openvpn config file commands you can wrap ""systemd-
> resolve --set-dns=XXX"" and update the given DNS servers.
"
1718227,2019-12-12 23:36:35 UTC,"> For openvpn + systemd-resolve:
>
> With ""up / down"" openvpn config file commands you can wrap ""systemd-
> resolve --set-dns=XXX"" and update the given DNS servers.
"
1718227,2018-05-29 07:22:47 UTC,"We handled chrony and ntp was demoted, so set ntp to Won't Fix in regard to this bug."
1718227,2018-04-02 19:02:24 UTC,"On Thu, Mar 29, 2018 at 06:27:18PM -0000, Alkis Georgopoulos wrote:"
1718227,2018-03-29 03:35:03 UTC,"vzctl is a set of tools for OpenVZ, a very early container technology which I think it's fair to say is obsoleted by lxd.  For anyone running openvz, it would still matter to have vzctl integration with networkd, but I think this would be a low priority to fix."
1718227,2018-03-29 12:19:44 UTC,"clamav explicitly mentions ifupdown in a debconf question regarding how the user would like freshclam (updating the virus signatures db) to work. One of the options is a ifupdown hook attached to what the user calls ""the internet interface"". That option should be removed, or better yet, migrated to a systemd ""something"" attached to that specific interface."
1718227,2017-09-19 15:32:45 UTC,aiccu package should be taken out of distribution due to closing of sixxs.net - there is no running tunnel broker any more.
1718227,2018-01-31 18:27:35 UTC,$ apt show plan netplan | grep -A 3 Description
1718227,2018-01-31 19:55:05 UTC,"On Wed, Jan 31, 2018 at 06:27:35PM -0000, Vagrant Cascadian wrote:

> This doesn't sound like the sort of thing to replace ifupdown...  some
> more information about what this actually refers to would be helpful.
"
1718227,2018-02-08 07:15:53 UTC,"FYI: The discussion in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889010 nicely outlined that we rely on those hooks in chrony.
That makes having them working critical for 18.04 to have it working correctly for late or changing network topology."
1718227,2018-02-15 00:06:04 UTC,I have a problem with tinc and netplan.
1718227,2018-02-15 07:25:18 UTC,"On Thu, Feb 15, 2018 at 12:06:04AM -0000, Crashbit wrote:

> I have a problem with tinc and netplan.
"
1718227,2018-03-29 18:27:18 UTC,"For the maintainers of the affected packages to be able to help in this issue,
addressing the main question already stated above would be most helpful:"
1718227,2018-03-22 14:09:16 UTC,Any update on the integration of networkd-dispatcher or a similar technology to allow the dependent packages to use that?
1718227,2018-03-28 14:05:23 UTC,bind9 in bionic at least detects nic changes and does not need to be reloaded.
1718227,2018-03-28 15:27:37 UTC,"Thanks, closing the bind9 task as invalid."
1718227,2018-03-29 00:21:24 UTC,"vlan support is native in netplan, no need for the vlan package to integrate with it."
1718227,2018-03-29 03:21:41 UTC,"ifmetric is a package that sets route metrics - which seems awfully pointless, 'metric' is already supported natively by ifupdown and by netplan.  This does not need integration."
1718227,2018-03-29 03:31:37 UTC,ifupdown-scripts-zg2 no longer exists in Ubuntu as of bionic.
1718227,2018-03-29 03:36:19 UTC,"openresolv is an alternative implementation of resolvconf.  If you are using netplan, you should be using systemd-resolved; not resolvconf."
1718227,2018-03-26 13:53:03 UTC,This bug was fixed in the package ubuntu-fan - 0.12.10
1718227,2018-03-29 03:15:15 UTC,"ifenslave is used to configure bonds, which is supported natively in netplan.  No integration required."
1718228,2017-09-20 13:47:34 UTC,I realize this package is missing a -hwe-16.04 updated version.
1718230,2019-03-19 16:28:39 UTC,"I ended in exactly the same situation today.
I did Alt+A by mistake and did not notice it until I saw all my commands being typed in all other terminals.
I also used a terminal based chat client (for IRC/jabber).
Imagine I was typing a password to connect to a SSH server, then the password would have been broadcasted to all my terms, including my chatroom..."
1718234,2017-09-28 14:16:50 UTC,This bug was fixed in the package ubuntu-themes - 16.10+17.10.20170925-0ubuntu1
1718237,2017-09-20 15:39:22 UTC,Would you be against having some 'openInNewInstance' action which would simply exec qpdfview with current pdf as an argument?
1718237,2017-11-09 13:16:47 UTC,"I'd think that fully fledged support for multiple windows is quite an enterprise. If we rely on Qt spawning, we do not have to worry about implementation details like e.g forking functionality on different platforms."
1718237,2017-10-17 05:13:23 UTC,"Aiming for independent windows, I see two options worth pursuing: Either add fully fledged support for multiple windows in a single process which would open up various future possibilities but also have a risk of regressions and probably be a bit more complicated or start a new process maybe as you suggested above. I think (efficient) forking is pretty UNIX-specific, i.e. I am not sure this would work on AmigaOS or eComStation. I think the second option could be integrated with the implementation of the moveToInstance function, e.g. add copyToInstance or something similar and given both functions the option of starting a new (independent) instance if the desired one is not already registered on D-Bus."
1718237,2017-10-16 21:28:59 UTC,"> How to exec qpdfview in platform-agnostic and installation-agnostic way?
"
1718237,2017-09-19 20:23:28 UTC,"Hello my,"
1718237,2017-10-16 18:30:51 UTC,"Hello my,"
1718237,2017-10-16 11:49:48 UTC,"I am even willing to spend some time writing the patch. Critical question here is - are you willing to accept ""Open in duplicate window"" menu entry?"
1718237,2017-10-16 20:56:49 UTC,"> How to exec qpdfview in platform-agnostic and installation-agnostic way?
"
1718238,2018-05-03 06:08:54 UTC,"I upgraded from 17.10 to 18.04 today, and I still have this problem as well.
In response to comment 21:"
1718238,2018-05-03 08:31:27 UTC,"Silly me, instead of asking questions I should have tried it myself."
1718238,2018-05-07 19:07:28 UTC,2018 May 7. Obscuring icon remains. Did fresh install last night with all updates. There is a patch on gitHub for this about 3 days ago. Has it been incorporated by Ubuntu? Does it fix the issue?
1718238,2018-05-07 19:27:23 UTC,"> There is a patch on gitHub for this about 3 days ago.
"
1718238,2018-05-07 20:16:19 UTC,I can not find it; wish I had saved it.
1718238,2018-05-07 20:24:27 UTC,Wait. Try this from Christian Persch. Commit from 5 days ago.
1718238,2018-05-07 20:28:09 UTC,"@guido Oh, I guess I found it, I guess you meant this:"
1718238,2018-05-07 20:40:02 UTC,"@guido Nope, that one is irrelevant (that icon title is something completely different, it's a legacy concept: the title of the window whenever it's iconified; plus the change is in gnome-terminal's current development series which won't appear in Bionic)."
1718238,2018-05-07 20:42:25 UTC,I'm confused. Are my URL & yours the same?
1718238,2018-05-07 20:57:43 UTC,"Egmont, by the way, that mutter patch is in Debian also since mutter is currently in sync between Debian and Ubuntu."
1718238,2018-05-10 21:41:18 UTC,Continued in bug 1770507.
1718238,2019-05-10 08:18:59 UTC,The upstream bug notes that it is an Ubuntu patch causing this bug.
1718238,2019-05-10 08:33:07 UTC,Comment #30 notes the same thing ;)
1718238,2018-05-02 18:26:38 UTC,Found this problem *again* in 18.04 with vim (not gvim) running in the gnome-terminal using default .desktop file.
1718238,2018-05-02 13:35:56 UTC,For those who still see this issue in 18.04:
1718238,2018-05-02 21:04:27 UTC,"I am on 18.04, and I see the smaller 48x48 icon as reported in 1765704 and by xprop."
1718238,2018-02-05 09:21:49 UTC,"Well, the title can be changed :) Anyway, it's not worth further discussing, rather than working on the actual bug. Let's get back to business..."
1718238,2017-10-05 03:42:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718238,2018-02-05 08:42:34 UTC,Please see the duplicate bug 1724250 for some hopefully precious investigation I've done so far.
1718238,2018-02-05 08:48:31 UTC,"(Daniel, may I please kindly recommend that next time when one of the bugs contains all the information present in the other plus much-much more then mark it as duplicate the other way around, even if chronologically incorrect? IMO that's much more useful for continuing to work on it and hopefully getting it fixed eventually. Thanks!)"
1718238,2018-02-05 09:02:53 UTC,"Yes we do do that sometimes. However there was an additional reason to keep this one other than its age; the title is much more helpful and specific. By comparison ""gnome-terminal graphic artifact"" could refer to any number of different problems."
1718238,2018-04-23 01:52:58 UTC,Confirmed by Brad and duplicate bug 1765704 that this bug is not fixed.
1718238,2018-02-06 21:58:36 UTC,"I have found that the presence of the counterpart ""utilities-terminal.png"" icons under /usr/share/icons/gnome fixes the use of the Humanity one (even though the ones under the ""gnome"" folder are unused), while removing them breaks it."
1718238,2018-02-06 22:52:16 UTC,"In the buggy case, xprop only reports one icon of size 48."
1718238,2018-02-07 12:45:16 UTC,Here's a fix to mutter.
1718238,2018-05-02 12:52:28 UTC,Issue remains for me as well 18.04 - 3.28.1
1718238,2018-02-07 16:24:46 UTC,"The attachment ""Mutter fix"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1718238,2018-02-07 23:14:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718238,2018-02-07 23:15:28 UTC,Upstream report: https://gitlab.gnome.org/GNOME/mutter/issues/23
1718238,2018-03-03 16:24:03 UTC,"It has been fixed upstream, the fix should appear in mutter 3.27.92 / 3.28."
1718238,2018-03-06 13:05:49 UTC,This bug was fixed in the package mutter - 3.27.92-1
1718238,2018-03-14 01:27:41 UTC,I still have this problem and I am running mutter 3.27.92-1.
1718238,2018-03-14 02:02:34 UTC,"Brad, sounds like you should tell upstream:
https://gitlab.gnome.org/GNOME/mutter/issues/23"
1718238,2018-02-07 13:10:16 UTC,"Daniel (or anyone else),"
1718244,2020-08-31 10:45:12 UTC,xfs_check is deprecated and has been removed from xfsprogs since 2014.
1718244,2020-08-31 10:48:00 UTC,xfs_check has been merged into / replaced by xfs_repair in 2014.
1718245,2017-09-20 20:20:27 UTC,"This is an invasive change to execute on a host as it would affect any existing configuration you have, that said, if executing in a container we can certainly try and get this going."
1718245,2017-12-09 16:20:54 UTC,There's a comment on that stackoverflow thread that current versions of Subversion honour the http_proxy environment variable. Could that be set a build time on the build server?
1718245,2018-01-18 12:40:29 UTC,"As far as Launchpad goes, this needs to be done in launchpad-buildd, and it's already filed there as bug 1668358.  I guess it may still be worthwhile to keep this bug open separately for the case of running ""snapcraft cleanbuild"" in an environment that requires a proxy."
1718246,2017-09-19 16:49:51 UTC,Please fix it with
1718246,2017-09-19 16:51:21 UTC,"P.S.
Meanwhile we will fix it today at the calchep page"
1718249,2017-09-19 17:25:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/505340"
1718254,2018-03-13 20:26:51 UTC,I filed LP: #1755585 for the 2 packages I mentioned in my previous comment.
1718254,2018-03-05 03:51:31 UTC,indicator-network and unity-greeter-session-broadcast have no reverse dependencies in bionic so maybe they should just be removed.
1718254,2017-09-19 17:31:42 UTC,"Note if everything is fixed, apart from unity-scopes-api, that is also fine, as src:unity-scopes-api & src:click can then be removed together."
1718254,2017-10-04 11:15:21 UTC,Not sure desktop is going to have time to work on this for 17.10.
1718254,2017-10-31 13:28:49 UTC,what about bionic?
1718259,2017-09-19 22:22:43 UTC,"~stub,"
1718259,2017-09-20 06:28:24 UTC,"You might be right, and the issue could have been client/subordinate side in interface:pgsql. Updates I've made to that interface since I opened Bug #1560262 may have fixed this, and switching the scope to container may now just-work."
1718259,2017-10-04 14:46:00 UTC,"Can anyone state what the actual bug here is by the way? My understanding is that the current approach of using the non-container scoped PostgreSQL relation as it is defined is correct, rather than chosing to use a different scope to the primary charm and hoping it works. I ask because I think people might be trying to fix the wrong problem."
1718259,2017-10-17 10:48:50 UTC,Let me first define a term that I am going to use:
1718259,2020-03-08 20:04:54 UTC,"Is this bug still active and needing further work, or have changes in Juju made this no longer an issue?"
1718259,2020-04-15 20:30:44 UTC,Confirmed that this is still an issue for the mysql relation at least
1718259,2017-09-19 18:37:20 UTC,"The pgsql interface is not container scoped and does not function correctly if used as a container scoped relation, which is why telegraf does not try to declare it as container scoped."
1718261,2018-02-25 08:59:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718262,2017-09-20 00:26:27 UTC,This bug was fixed in the package linux-azure - 4.11.0-1011.11
1718264,2017-09-20 00:26:27 UTC,This bug was fixed in the package linux-azure - 4.11.0-1011.11
1718269,2017-12-25 12:16:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718273,2020-01-07 21:11:53 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1718273,2020-03-08 04:17:32 UTC,[Expired for meld (Ubuntu) because there has been no activity for 60 days.]
1718275,2017-09-19 19:44:45 UTC,See bug #1718176 for initial report.
1718275,2017-09-19 21:17:15 UTC,"I created an upstream report, maybe someone can check what's wrong here..."
1718275,2017-09-19 21:47:47 UTC,"Seems I forgot the link:
https://sourceforge.net/p/nsis/bugs/1192/"
1718275,2019-05-30 17:43:29 UTC,"Upstream bug has been closed as 'invalid' without any comment. Inkscape is still extremely slow when upgrading an existing installation. I gave up upgrading from 0.92.2 to 0.92.4. It basically takes hours, even on an SSD."
1718275,2019-05-30 19:10:27 UTC,"Well, there was a comment upstream - it's possible the slowness is caused by ""Advanced Uninstall Log""."
1718275,2019-06-09 13:24:03 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape/issues/300
1718285,2017-09-19 20:41:14 UTC,"StacktraceTop:
 ?? ()
 XGetModifierMapping (dpy=dpy@entry=0x55a287624950) at ../../src/ModMap.c:41
 im_uim_init_modifier_keys () at ../../gtk2/immodule/key-util-gtk.c:333
 im_module_init (type_module=0x55a287902100) at ../../gtk2/immodule/gtk-im-uim.c:1808
 gtk_im_module_load (module=0x55a287902100) at ././gtk/gtkimmodule.c:171"
1718288,2017-09-21 14:48:18 UTC,"Looking at this some more, it may just need some better mocking in the test."
1718311,2017-09-21 16:43:38 UTC,"Review in progress for https://review.opencontrail.org/35746
Submitter: Sachin Bansal (<email address hidden>)"
1718311,2017-09-21 22:54:14 UTC,"Reviewed:  https://review.opencontrail.org/35746
Committed: http://github.com/Juniper/contrail-controller/commit/f1698209aa4e765cf9d8d51801a4c8eacb671a61
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1718311,2017-09-19 22:46:57 UTC,"Review in progress for https://review.opencontrail.org/35746
Submitter: Sachin Bansal (<email address hidden>)"
1718311,2017-09-20 20:39:42 UTC,Only affects R3.2
1718319,2017-09-21 12:37:17 UTC,"Offhand, this line is quite relevant:"
1718319,2017-09-20 00:46:30 UTC,"@Peter Matulis (petermatulis),"
1718319,2017-09-20 00:49:55 UTC,"Although I am currently looking at re-working this area a bit in such a way that the user that has been granted add-model can re-use cloud credentials from ""controller"" model."
1718319,2017-09-20 15:39:14 UTC,"Anastasia,"
1718327,2017-12-11 15:29:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718336,2017-09-20 04:02:47 UTC,I just read this on the changelog:
1718336,2017-09-20 04:19:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718345,2019-09-27 15:28:52 UTC,"Reviewed:  https://review.opendev.org/685173
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=add87accc5105124241042a5f0933b76e93648f4
Submitter: Zuul
Branch:    stable/stein"
1718345,2019-09-27 15:29:04 UTC,"Reviewed:  https://review.opendev.org/685174
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8bda3c2ed33906ab2fbacc23f5775b4e0f4b76b0
Submitter: Zuul
Branch:    stable/rocky"
1718345,2019-09-26 20:24:11 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/685174"
1718345,2019-10-22 19:52:43 UTC,This issue was fixed in the openstack/neutron 13.0.5 release.
1718345,2019-10-22 19:44:27 UTC,This issue was fixed in the openstack/neutron 14.0.3 release.
1718345,2019-09-26 20:23:49 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/685173"
1718345,2018-08-31 07:44:20 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1718345,2019-08-30 11:27:43 UTC,"Reviewed:  https://review.opendev.org/508808
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=32bfc3edeca935fc9c16b3019aa0af3091cd19e7
Submitter: Zuul
Branch:    master"
1718345,2018-08-31 07:44:32 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/508808
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1718345,2019-09-19 10:12:27 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1718345,2017-09-28 00:38:22 UTC,"@anil-venkata I did notice that when a DVR router is migrated to a CVR router, the device_owner: of the router-interface is changed from router-interface-distributed to 'network:ha_router_replicated_interface', even though Router HA is not enabled.
Should it not be just 'router_interface'."
1718345,2017-09-28 00:22:53 UTC,"yes the port-binding table is not cleared.
This is confirmed."
1718345,2017-09-20 18:21:07 UTC,"@anil-venkata where is your code calling to clean up the ml2_distributed_port_bindings.
In the case of dvr the ml2_distributed_port_bindings are called in ensure_port_bindings are set for the ports.
So might be when you migrate the routers, we should probably call the respective code to clean up."
1718345,2017-09-20 07:50:51 UTC,So it seems that this is a new bug related to the Migration where the port-binding table is not cleared.
1718351,2017-09-20 14:31:43 UTC,"2017-09-04 11:53:11.073070 | fatal: [127.0.0.1]: FAILED! => {""changed"": true, ""cmd"": [""ironic-dbsync"", ""--config-file"", ""/etc/ironic/ironic.conf"", ""create_schema""], ""delta"": ""0:00:02.059669"", ""end"": ""2017-09-04 11:53:11.038282"", ""failed"": true, ""invocation"": {""module_args"": {""_raw_params"": ""ironic-dbsync --config-file /etc/ironic/ironic.conf create_schema"", ""_uses_shell"": false, ""chdir"": null, ""creates"": null, ""executable"": null, ""removes"": null, ""warn"": true}, ""module_name"": ""command""}, ""rc"": 1, ""start"": ""2017-09-04 11:53:08.978613"", ""stderr"": """", ""stdout"": ""2017-09-04 11:53:10.957 15898 CRITICAL ironic [-] Unhandled error: ValueError: invalid literal for int() with base 10: 'ironic.sqlite'\n2017-09-04 11:53:10.957 15898 ERROR ironic Traceback (most recent call last):\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/bin/ironic-dbsync\"", line 10, in <module>\n2017-09-04 11:53:10.957 15898 ERROR ironic     sys.exit(main())\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/ironic/cmd/dbsync.py\"", line 103, in main\n2017-09-04 11:53:10.957 15898 ERROR ironic     CONF.command.func()\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/ironic/cmd/dbsync.py\"", line 47, in create_schema\n2017-09-04 11:53:10.957 15898 ERROR ironic     migration.create_schema()\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/ironic/db/migration.py\"", line 52, in create_schema\n2017-09-04 11:53:10.957 15898 ERROR ironic     return get_backend().create_schema()\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/ironic/db/migration.py\"", line 30, in get_backend\n2017-09-04 11:53:10.957 15898 ERROR ironic     cfg.CONF.database.backend).driver\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/stevedore/driver.py\"", line 61, in __init__\n2017-09-04 11:53:10.957 15898 ERROR ironic     warn_on_missing_entrypoint=warn_on_missing_entrypoint\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/stevedore/named.py\"", line 81, in __init__\n2017-09-04 11:53:10.957 15898 ERROR ironic     verify_requirements)\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/stevedore/extension.py\"", line 194, in _load_plugins\n2017-09-04 11:53:10.957 15898 ERROR ironic     self._on_load_failure_callback(self, ep, err)\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/stevedore/extension.py\"", line 186, in _load_plugins\n2017-09-04 11:53:10.957 15898 ERROR ironic     verify_requirements,\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/stevedore/named.py\"", line 158, in _load_one_plugin\n2017-09-04 11:53:10.957 15898 ERROR ironic     verify_requirements,\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \""/usr/local/lib/python2.7/dist-packages/stevedore/extension.py\"", line 214, in _load_one_plugin\n2017-09-04 11:53:10.957 15898 ERROR ironic     plugin = ep.resolve()\n2017-09-04 11:53:10.957 15898 ERROR ironic   File \..."
1718351,2018-02-02 21:27:14 UTC,I'm afraid that this is an issue outside of bifrost with ironic... or our use of sqllite during that time. I believe we since changed. If we can reproduce...
1718355,2017-09-27 05:35:45 UTC,"Reviewed:  https://review.opencontrail.org/35720
Committed: http://github.com/Juniper/contrail-fabric-utils/commit/493878af7c3c639e5eaf7ea750b7c33441ef51ab
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1718355,2017-09-20 06:53:52 UTC,"Review in progress for https://review.opencontrail.org/35720
Submitter: Ankit Jain (<email address hidden>)"
1718356,2017-12-08 21:43:17 UTC,This issue was fixed in the openstack/congress 7.0.0.0b2 development milestone.
1718356,2018-02-05 22:44:04 UTC,This issue was fixed in the openstack/zun 1.0.0 release.
1718356,2018-02-06 02:47:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541106"
1718356,2018-03-08 14:29:23 UTC,"Reviewed:  https://review.openstack.org/506142
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=45f1404c68553fd01f386522dd16841526c68dbf
Submitter: Zuul
Branch:    master"
1718356,2018-03-23 03:09:22 UTC,"Reviewed:  https://review.openstack.org/506191
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=5d162ebdda9071b9a691f3130228b51f4a808836
Submitter: Zuul
Branch:    master"
1718356,2018-03-26 21:01:17 UTC,"Reviewed:  https://review.openstack.org/553463
Committed: https://git.openstack.org/cgit/openstack/cyborg/commit/?id=ac6b70dc6a9c440250b739c9fed9a1b74d7642be
Submitter: Zuul
Branch:    master"
1718356,2017-12-07 14:32:28 UTC,This issue was fixed in the openstack/glance 16.0.0.0b2 development milestone.
1718356,2018-04-02 16:54:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/558240"
1718356,2018-04-03 20:30:51 UTC,"Reviewed:  https://review.openstack.org/558240
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=8367e442304a16687be602d4a23762d3408b9010
Submitter: Zuul
Branch:    master"
1718356,2018-04-17 18:57:38 UTC,This issue was fixed in the openstack/senlin 6.0.0.0b1 development milestone.
1718356,2018-04-19 14:14:01 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b1 development milestone.
1718356,2018-04-19 14:28:28 UTC,This issue was fixed in the openstack/trove 10.0.0.0b1 development milestone.
1718356,2018-07-14 09:25:04 UTC,"Reviewed:  https://review.openstack.org/582123
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_cinder/commit/?id=5dd4abe61adcdcc3950afd3950619c4c98b8b809
Submitter: Zuul
Branch:    master"
1718356,2018-04-20 13:51:14 UTC,This issue was fixed in the openstack/cyborg 1.0.0.0b1 development milestone.
1718356,2018-04-20 18:13:23 UTC,This issue was fixed in the openstack/barbican 7.0.0.0b1 development milestone.
1718356,2018-04-21 03:45:38 UTC,"Reviewed:  https://review.openstack.org/554819
Committed: https://git.openstack.org/cgit/openstack/karbor/commit/?id=c20e61d04221695bfd316417254649733e7ae692
Submitter: Zuul
Branch:    master"
1718356,2018-07-05 21:06:49 UTC,"Reviewed:  https://review.openstack.org/579944
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_cinder/commit/?id=83c07a4cb9960ce605a5c3fb5469f2870641e7d0
Submitter: Zuul
Branch:    master"
1718356,2018-07-12 09:24:56 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/582123"
1718356,2018-08-17 20:09:24 UTC,This issue was fixed in the openstack/karbor 1.1.0 release.
1718356,2018-11-22 09:11:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/619485"
1718356,2018-11-22 13:43:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/619571"
1718356,2018-11-28 00:34:08 UTC,"Reviewed:  https://review.openstack.org/619485
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3466832b9972002e1c9eccde9ab2392dd7363e3a
Submitter: Zuul
Branch:    stable/queens"
1718356,2018-11-28 00:50:21 UTC,"Reviewed:  https://review.openstack.org/619571
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=888cbc2970e3c06956f1fae403c07743371cae7c
Submitter: Zuul
Branch:    stable/pike"
1718356,2019-04-12 23:22:23 UTC,This issue was fixed in the openstack/neutron 11.0.7 release.
1718356,2019-04-12 23:33:12 UTC,This issue was fixed in the openstack/neutron 12.0.6 release.
1718356,2017-11-17 16:59:55 UTC,"Reviewed:  https://review.openstack.org/506145
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=b0b102b8dc5ae0327f0b772c6a9aafaa5c666f87
Submitter: Zuul
Branch:    master"
1718356,2018-04-20 13:16:30 UTC,This issue was fixed in the openstack/murano 6.0.0.0b1 development milestone.
1718356,2017-11-15 14:55:45 UTC,This issue was fixed in the openstack/ironic 9.2.0 release.
1718356,2018-02-27 23:39:23 UTC,"Reviewed:  https://review.openstack.org/506203
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=39ae2ee3a9084e0b6945f0fbec3dd735dc0efa7d
Submitter: Zuul
Branch:    master"
1718356,2017-10-27 15:58:39 UTC,This issue was fixed in the openstack/sahara 8.0.0.0b1 development milestone.
1718356,2017-11-07 00:32:23 UTC,This issue was fixed in the openstack/manila 6.0.0.0b1 development milestone.
1718356,2017-09-21 01:18:52 UTC,Why are neutron and glance part of this bug if they already fixed this? Why aren't cinder/keystone affected?
1718356,2017-09-21 07:02:32 UTC,@Matt I'll be patching both neutron and glance to include more files or to optimise the implementation. I will be adding more projects as I go through them - I ended up getting pulled into something else yesterday before completing this.
1718356,2017-09-21 12:45:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506145"
1718356,2017-09-21 12:54:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506149"
1718356,2017-09-21 13:03:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506155"
1718356,2017-09-21 13:59:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506188"
1718356,2017-09-21 14:01:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506191"
1718356,2017-09-21 14:04:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506192"
1718356,2017-09-21 14:12:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506198"
1718356,2017-09-21 14:14:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506200"
1718356,2017-09-21 14:16:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506203"
1718356,2017-09-21 14:19:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506206"
1718356,2017-09-21 14:23:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506210"
1718356,2017-09-21 15:29:33 UTC,"Can you be more specific as to what is missing from Octavia?  We already include the example config in our data_files:
https://github.com/openstack/octavia/blob/master/setup.cfg#L25-L38"
1718356,2018-02-08 17:36:15 UTC,This issue was fixed in the openstack/magnum 6.0.0 release.
1718356,2017-09-21 18:06:41 UTC,"Correct, our policy is in code and we don't use paste.  Marking invalid."
1718356,2017-10-26 21:08:51 UTC,This issue was fixed in the openstack/designate 6.0.0.0b1 development milestone.
1718356,2017-10-24 13:42:24 UTC,This issue was fixed in the openstack/keystone 13.0.0.0b1 development milestone.
1718356,2017-10-24 12:42:25 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1718356,2017-10-24 03:17:47 UTC,This issue was fixed in the openstack/cinder 12.0.0.0b1 development milestone.
1718356,2017-09-21 16:55:28 UTC,"@Michael I see that there are no sample api-paste.ini files and it seems that the default policy is in-code? I guess that Octavia does not implement any paste middleware? If so, yes - nothing needs to be done here. Apologies for the confusion."
1718356,2017-10-16 14:34:33 UTC,"Reviewed:  https://review.openstack.org/506192
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=e486a50f77ad09e04a6cb20bfc40c798d9161535
Submitter: Zuul
Branch:    master"
1718356,2017-10-27 07:31:54 UTC,This issue was fixed in the openstack/heat 10.0.0.0b1 development milestone.
1718356,2017-10-11 12:43:13 UTC,"Reviewed:  https://review.openstack.org/506149
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0502d749a6ac43167cfcbdd73bd25c542035dbbb
Submitter: Jenkins
Branch:    master"
1718356,2017-10-09 15:44:22 UTC,"Reviewed:  https://review.openstack.org/506198
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=110259750e15323a2cbc3c8fb29b9d51cc68cf7c
Submitter: Jenkins
Branch:    master"
1718356,2017-10-03 15:00:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509198"
1718356,2017-09-22 15:50:36 UTC,"Reviewed:  https://review.openstack.org/506210
Committed: https://git.openstack.org/cgit/openstack/sahara/commit/?id=873c4fed836f8f4c16469ad16478b7bbbfb0daa6
Submitter: Jenkins
Branch:    master"
1718356,2017-09-22 08:08:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506559"
1718356,2017-10-16 01:05:54 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/509198"
1718369,2017-09-21 15:29:59 UTC,"Can you give more info, like what version of Neutron this is?  Thanks."
1718369,2017-10-27 06:13:04 UTC,"openstack version: pike
neutron version: 6.5.0
[root@172e18e211e96 ~]# neutron --version
6.5.0"
1718369,2017-11-07 17:01:17 UTC,I'm sporadically experiencing a DBDeadlock as well. It doesn't necessarily happen when deleting a network. Here's an example. Note that there's a DBDeadlock immediately followed by a DBReferenceError (perhaps not surprising given the deadlock).
1718371,2017-09-20 08:36:15 UTC,Here's the full journal log of the shutdown process.
1718381,2017-11-29 10:02:06 UTC,Not seeing this on the latest 4.1.
1718386,2017-10-25 06:17:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718402,2017-09-20 11:56:54 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x55873e74e6e0, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4025
 g_object_get (_object=_object@entry=0x55873e74e6e0, first_property_name=first_property_name@entry=0x55873b95bc5c ""position"") at ../../../../gobject/gobject.c:2493
 budgie_panel_applet_at_end_of_region (self=<optimized out>, info=0x55873e74e6e0) at src/panel/budgie-panel@exe/panel.c:4030
 budgie_panel_real_can_move_applet_right (base=0x55873d4cc430, info=0x55873e74e6e0) at src/panel/budgie-panel@exe/panel.c:4181
 budgie_applets_page_move_applet_down (self=0x55873d39bdc0) at src/panel/budgie-panel@exe/settings_panel_applets.c:1662"
1718402,2017-09-20 13:04:55 UTC,"as an aside,"
1718402,2017-09-23 15:07:20 UTC,"I can't stay on ubuntu 17.10 artful. Please install in my pc ubuntu 17.04 (stable platform)
Thank you."
1718402,2018-09-01 08:01:29 UTC,Looks to be a logic issue when creating applets details with null values and then testing expecting those fields to have been filled with values.
1718402,2017-09-20 13:03:42 UTC,I am unable to reproduce this.  Please describe exactly what you are doing - with what window - what applets - moving what applet?
1718405,2017-10-22 17:56:31 UTC,It requires a lot of efforts in the current horizon implementation.
1718413,2017-09-20 12:33:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1718413,2017-09-26 08:18:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718418,2017-09-20 13:02:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1718418,2017-09-20 14:11:28 UTC,"Seems it's specific to trackpoints (thinkpad nipples), not mouse wheels, so updated accordingly and linked to upstream bug."
1718435,2017-11-17 16:31:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718436,2017-09-22 01:50:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718436,2017-09-20 14:07:31 UTC,Thanx!
1718439,2017-09-20 14:45:29 UTC,"After some brief discussion in #openstack-nova I've moved this to oslo.log. The issue here appears to be that we spawn multiple separate conductor processes writing to the same nova-conductor.log file. We don't want to stop doing this, as it would break people."
1718439,2018-01-22 15:08:17 UTC,"It sounds like the change to multiprocessing.get_logger() would be in nova, not the library. Is that right?"
1718439,2018-05-10 17:12:37 UTC,"Yeah, since we stopped calling get_logger from oslo.log I don't think we can fix this in the library.  I'm going to add Nova back to the bug so they can re-triage base on this information."
1718439,2018-06-28 22:43:28 UTC,"Ben, what do you mean when you say, ""stopped calling get_logger from oslo.log?"" I couldn't find any commits in oslo.log containing get_logger with 'git log -S get_logger'."
1718450,2020-07-04 12:19:40 UTC,libdbus-1-3:i386 (1.11.16+really1.10.22-1)
1718453,2020-01-04 05:04:48 UTC,"At this point, I think it's safe to say that implementing full multiarch support for AppStream simply isn't going to happen, at least not anytime soon. It's simply easier for app authors to provide native implementations for amd64 instead of relying on i386 compatibility.
If support was implemented fully, we would download lots of additional big metadata and run into all kinds of troubles of which app gets selected when there are ID conflicts.
Resolving all of these issues is possible, but the huge effort IMHO doesn't justify the gains. If someone else works on this, I'd assist the work, but I will unlikely work on this myself. I originally intended to, but TBH, this issue has really low priority nowadays."
1718453,2018-01-25 17:41:53 UTC,"apt does what it is told – appstream configures apt to download only the files for the native architecture, so there is no sensible action to be taken by apt and hence this task invalid."
1718453,2018-01-25 13:38:16 UTC,"There is no component files for i386 on amd64 in /var/lib/apt/lists/
If you download the corresponding dep11 files and refresh appstream cache then a search returns the right results."
1718453,2018-01-25 12:30:01 UTC,I'm removing gnome-software task because it is not a problem with this component.
1718453,2017-10-07 14:09:07 UTC,"After trying to install it gives me:
Running Steam on ubuntu 16.04 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(0)
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast"
1718453,2017-10-03 14:20:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718453,2018-01-25 18:13:27 UTC,"@donkult: The downloads for all architectures are not allowed at time, because doing so would lead to AppStream-ID collisions, and AppStream itself has no notion of architectures (yet - I played around with that a bit, but there is no definitive good solution yet)."
1718453,2017-09-20 23:23:08 UTC,This bug is likely a duplicate of https://launchpad.net/bugs/1564570
1718453,2017-09-20 23:24:19 UTC,"Oh, I missed Robert's comments. #1564570 is for non-i386 architectures."
1718453,2017-09-20 21:12:53 UTC,Linking in appstream as the reason is there is no appstream data:
1718453,2017-09-20 21:23:00 UTC,"It is there though, on i386: http://appstream.ubuntu.com/artful/multiverse/metainfo/steam.html
Maybe the multiverse sources aren't active here?"
1718453,2017-09-20 23:54:05 UTC,I tested on both amd64 and i386 as detailed in the linked post in the original description. I installed both amd64 and i386 variants of Ubuntu 16.04.3 in parallel in separate VMs and experienced (from a user perspective) the same issue. The difference being what appstreamcli returns on each...
1718453,2017-09-20 21:36:34 UTC,"Explicitly, it looks like I am missing:
archive.ubuntu.com_ubuntu_dists_xenial_multiverse_dep11_Components-i386.yml.gz"
1718453,2017-09-20 21:35:28 UTC,Looking in /var/lib/apt/lists I have:
1718453,2017-09-20 23:11:42 UTC,"Are you on a real i386 system, or on an amd64 system with i386 as foreign architecture? The latter case is not supported, which is a known issue (affects Steam and Skype)."
1718455,2017-10-25 19:22:25 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1718455,2017-10-24 12:42:04 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1718455,2017-10-12 14:47:49 UTC,"Reviewed:  https://review.openstack.org/508590
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2b0c1867dad6e92b593f16ac62b9325bcacf91a9
Submitter: Jenkins
Branch:    stable/pike"
1718455,2017-09-29 18:58:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/508591"
1718455,2017-10-12 23:37:14 UTC,"Reviewed:  https://review.openstack.org/508591
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b97c433f7c24615a81a1342e75fd42fe3c15e3d4
Submitter: Jenkins
Branch:    stable/pike"
1718455,2017-09-22 18:43:53 UTC,"Reviewed:  https://review.openstack.org/506092
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=016d3efa393f864585ecc13317e46415a5cba825
Submitter: Jenkins
Branch:    master"
1718455,2017-09-21 09:43:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506093"
1718455,2017-09-21 09:42:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/506092"
1718455,2017-09-20 20:10:49 UTC,We should have a functional scenario test for this since we had a similar bug/fix in pike:
1718455,2017-09-29 18:57:59 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/508590"
1718455,2017-10-10 23:09:33 UTC,"Reviewed:  https://review.openstack.org/506093
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=87ca0d8af0d6440a7effd4da9e47321b3a335442
Submitter: Jenkins
Branch:    master"
1718457,2017-10-05 20:37:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718461,2018-01-20 08:05:32 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1473
1718461,2017-09-21 08:02:59 UTC,"Unfortunately, this dependency comes from upstream MySQL code which only compatible with specific versions of boost. xtrabackup does is not linked against boost shared libraries, so it really doesn't matter which boost version comes as system library. To build xtrabackup with specific version of boost, you can use -DWITH_BOOST and -DDOWNLOAD_BOOST options (see details here http://mysqlserverteam.com/building-mysql-5-7/)"
1718461,2017-09-21 08:58:18 UTC,"On Gentoo Linux we remove the bundled 1.59.0 version of Boost and use the system libraries instead. We also remove the other bundled libs like lz4, libedit, zlib, etc."
1718461,2017-09-21 09:18:39 UTC,"And how do you deal with include/boost*/patches? Do you modify them to work with your system boost version? It is not xtrabackup-specific, it is upstream MySQL that carry some bugfixes to boost. Does latest MySQL 5.7 build with boost 1.65.0?"
1718461,2017-09-21 09:21:03 UTC,"Note, that neither MySQL nor xtrabackup doe not link with shared boost libraries, they only use boost header files."
1718461,2017-09-21 09:58:05 UTC,"Yeah, sorry, I thought it's linked to boost, but it's not as you say:"
1718461,2017-09-21 09:59:31 UTC,"No, we don't modify boost with those patches, we use a common boost library for all applications."
1718464,2020-01-05 17:24:00 UTC,"Upstream bug:
https://github.com/codito/gnome-pomodoro/issues/357"
1718464,2017-10-09 10:13:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718464,2017-10-09 10:17:36 UTC,"Confirmed here. Functionality-wise, the appindicator one is completely redundant. The shell one has got additional controls and a more consistent feel with the rest of the GNOME indicators."
1718474,2017-12-18 12:51:29 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1718474,2017-12-11 22:05:11 UTC,"Reviewed:  https://review.openstack.org/524688
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=950239707dbd0e4f49e5191d0f944eb92b703bb5
Submitter: Zuul
Branch:    stable/pike"
1718474,2017-12-07 23:56:57 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1718474,2017-12-01 17:46:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/524688"
1718474,2017-12-01 01:40:39 UTC,"Reviewed:  https://review.openstack.org/505708
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ea20e87ad1fd5dc6df41d0d03506c851485cf2e1
Submitter: Zuul
Branch:    master"
1718474,2017-09-20 16:26:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505708"
1718485,2017-11-15 01:10:40 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1718485,2017-11-15 01:06:54 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1718485,2017-11-01 00:20:22 UTC,This issue was fixed in the openstack/nova 14.0.9 release.
1718485,2017-10-24 12:42:30 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1718485,2017-10-24 06:20:20 UTC,"Reviewed:  https://review.openstack.org/508878
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=98cef3a7529d7e8756d39302300c921ba52246c2
Submitter: Zuul
Branch:    stable/ocata"
1718485,2017-10-02 13:22:08 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/508878"
1718485,2017-10-17 23:58:53 UTC,"Reviewed:  https://review.openstack.org/508902
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b234b8e13a6dcd97b3dbea69dcbd09e86bf80e83
Submitter: Zuul
Branch:    stable/newton"
1718485,2017-10-02 15:02:31 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/508902"
1718485,2017-10-02 13:21:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/508877"
1718485,2017-09-25 15:06:07 UTC,"Reviewed:  https://review.openstack.org/506104
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b4778065e9a53f62d8ceee5889e1f1bbb61191d6
Submitter: Jenkins
Branch:    master"
1718485,2017-09-21 10:40:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506104"
1718485,2017-10-23 10:50:51 UTC,"Reviewed:  https://review.openstack.org/508877
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c82fc7d43e8480f1fc99125cad52e9fc3db33ed3
Submitter: Zuul
Branch:    stable/pike"
1718502,2018-05-04 12:05:39 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/566297"
1718502,2018-05-31 21:29:28 UTC,This issue was fixed in the openstack/tripleo-common 6.1.7 release.
1718502,2018-05-08 20:49:05 UTC,"Reviewed:  https://review.openstack.org/566296
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=9a29b4d052ef487b057a3c8ffeea0bb5d7faf229
Submitter: Zuul
Branch:    stable/ocata"
1718502,2018-05-04 20:12:02 UTC,"Reviewed:  https://review.openstack.org/566297
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=ac5e3fc860fbbde41a347bf2fe55838228e6dc88
Submitter: Zuul
Branch:    stable/newton"
1718502,2018-05-04 12:04:47 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/566296"
1718502,2018-06-14 13:55:15 UTC,This issue was fixed in the openstack/tripleo-common 5.4.9 release.
1718502,2017-10-10 07:44:01 UTC,"Reviewed:  https://review.openstack.org/510662
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=5922c80705c455d3d1d5dcb085ec08b19dd7accd
Submitter: Jenkins
Branch:    stable/pike"
1718502,2017-10-09 19:15:31 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/510662"
1718502,2017-10-09 15:27:38 UTC,This issue was fixed in the openstack/tripleo-common 8.0.0 release.
1718502,2017-09-22 19:54:32 UTC,"Reviewed:  https://review.openstack.org/503748
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=e5d16155364c1dae2db238506f236194e2dfb1dc
Submitter: Jenkins
Branch:    master"
1718502,2017-09-20 17:49:05 UTC,Patch: https://review.openstack.org/#/c/503748
1718502,2017-10-10 17:13:52 UTC,This issue was fixed in the openstack/tripleo-common 7.6.2 release.
1718508,2017-12-02 09:56:34 UTC,"Reviewed:  https://review.openstack.org/515576
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=bc3feec75f8dc1bac6691ce8cd05a37c27aa5e42
Submitter: Zuul
Branch:    master"
1718508,2017-10-13 20:17:35 UTC,"Reviewed:  https://review.openstack.org/510878
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=22ff1cf840107663f3aeae5b870a2d4615094d14
Submitter: Jenkins
Branch:    stable/pike"
1718508,2017-10-10 17:13:41 UTC,This issue was fixed in the openstack/puppet-tripleo 7.4.2 release.
1718508,2017-10-10 13:16:17 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/510878"
1718508,2017-10-09 21:54:54 UTC,"Reviewed:  https://review.openstack.org/509834
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=2471a8669d35f8b35ed00e9365623b37e335cd79
Submitter: Jenkins
Branch:    master"
1718508,2017-10-05 16:49:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/509834"
1718508,2017-09-28 14:27:41 UTC,"Reviewed:  https://review.openstack.org/508034
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=67e1e603a6b81e7532eb2cac2e27eec1ea413d32
Submitter: Jenkins
Branch:    stable/pike"
1718508,2017-10-27 16:04:25 UTC,This issue was fixed in the openstack/puppet-tripleo 8.0.0 release.
1718508,2017-09-28 02:45:04 UTC,"Reviewed:  https://review.openstack.org/505788
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=228d7b456c6d5c4958c9add8f9021a83a4360510
Submitter: Jenkins
Branch:    master"
1718508,2017-09-23 02:04:32 UTC,"Reviewed:  https://review.openstack.org/506783
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=889da598ecaa191c183cfb543d4f2f1bcab6b920
Submitter: Jenkins
Branch:    stable/pike"
1718508,2017-09-22 21:30:47 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/506783"
1718508,2017-09-21 22:39:18 UTC,"Reviewed:  https://review.openstack.org/505781
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=2417be6fae4df4003be0471a405d09a653d29f5d
Submitter: Jenkins
Branch:    master"
1718508,2017-09-20 19:56:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505788"
1718508,2017-09-20 19:08:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505781"
1718508,2017-09-20 18:11:27 UTC,"Impact of this is no instances can be brought up at all post deployment, so this is a blocker."
1718508,2017-09-28 02:53:24 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/508034"
1718509,2020-06-10 12:18:10 UTC,"As far as I can tell, this is only ever going to be visible from a malicious client (ie somebody running telnet), and is not able to be triggered from a browser (so no actual XSS)."
1718509,2018-08-14 01:27:02 UTC,"Hello, it appears we've lost track of this issue."
1718509,2017-09-20 18:34:35 UTC,Here is a completely untested fix.
1718512,2018-04-12 16:05:42 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/560955"
1718512,2018-04-12 16:07:46 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/560955
Reason: rebase squash failure"
1718512,2018-04-19 12:25:36 UTC,"Reviewed:  https://review.openstack.org/560142
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c2dc902e39eb345ebf674ad47422f1e72ec170e6
Submitter: Zuul
Branch:    stable/queens"
1718512,2018-04-19 12:25:57 UTC,"Reviewed:  https://review.openstack.org/560143
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=757dbd17cf37aecea005dfdc954bf50bbddedd95
Submitter: Zuul
Branch:    stable/queens"
1718512,2018-04-19 22:25:28 UTC,"Reviewed:  https://review.openstack.org/560145
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=004e9acf99964ac78f85d3efbd0a04404bd9a3ef
Submitter: Zuul
Branch:    stable/pike"
1718512,2018-04-20 05:24:44 UTC,"Reviewed:  https://review.openstack.org/560146
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=878e99d1f82fbeec840b2dbab8e40c27127d88ba
Submitter: Zuul
Branch:    stable/pike"
1718512,2018-04-25 09:24:00 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1718512,2018-04-24 18:05:47 UTC,"Reviewed:  https://review.openstack.org/560162
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0d111f17c4e411a42beb6c80bc27e6455a71c48c
Submitter: Zuul
Branch:    stable/ocata"
1718512,2018-04-24 18:05:57 UTC,"Reviewed:  https://review.openstack.org/560167
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c61ec9d98b7ca22fb6b68a80a9b382251a537a83
Submitter: Zuul
Branch:    stable/ocata"
1718512,2018-04-25 09:21:10 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1718512,2018-05-02 12:01:15 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1718512,2018-04-10 22:23:18 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/560167"
1718512,2018-04-20 13:12:43 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1718512,2018-04-10 21:41:36 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/560162"
1718512,2017-09-20 19:28:40 UTC,"Note this will also be a problem for cold migrate, evacuate and unshelve."
1718512,2018-04-10 20:45:31 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/560145"
1718512,2017-09-20 18:49:09 UTC,Asking about this in the mailing list:
1718512,2017-09-20 18:31:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/505771"
1718512,2018-04-10 20:45:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/560146"
1718512,2018-04-06 20:44:53 UTC,I wrote a functional regression test for this with a cold migrate scenario and I'm unable to recreate the failure now. This is the scenario I have:
1718512,2018-04-06 21:05:12 UTC,The original IRC conversation for this starts here:
1718512,2018-04-06 21:29:34 UTC,"Looking back at mitaka, the api creates the request spec, but doesn't send it to conductor.build_instances, that just builds it's own fake request spec to pass to the scheduler; conductor passes that fake reqspec down to compute, where it's ignored. There are no request_spec.save() calls in mitaka, but there is one in newton for resize:"
1718512,2018-04-06 19:23:06 UTC,I believe this regression goes back to Mitaka: https://review.openstack.org/#/c/202675/
1718512,2018-04-06 23:38:23 UTC,"I got a recreate based on comment 7, so https://review.openstack.org/#/c/505771/ has been updated to be the functional regression recreate test, and a follow up patch with the fix will go on top."
1718512,2018-04-07 00:41:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559447"
1718512,2018-04-10 20:30:43 UTC,"Reviewed:  https://review.openstack.org/505771
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=89448bea577b30c40ce39185d14fe14f9c61a0c2
Submitter: Zuul
Branch:    master"
1718512,2018-04-10 20:39:10 UTC,"Reviewed:  https://review.openstack.org/559447
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6647f11dc1aba89f9b0e2703f236a43f31d88079
Submitter: Zuul
Branch:    master"
1718512,2018-04-10 20:39:41 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/560142"
1718512,2018-04-10 20:40:03 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/560143"
1718512,2018-04-06 21:31:49 UTC,"If that request_spec.save() is the cause of the issue, that was introduced in Newton:"
1718513,2017-09-20 18:39:43 UTC,"StacktraceTop:
 ply_animation_is_stopped (animation=0x0) at ply-animation.c:368
 on_draw (view=0x55ccc0f225a0, pixel_buffer=0x55ccc0f1b160, x=0, y=0, width=1920, height=1080) at ./plugin.c:936
 ply_pixel_display_draw_area (display=0x55ccc0f24060, x=x@entry=0, y=y@entry=0, width=width@entry=1920, height=1080) at ply-pixel-display.c:153
 view_start_progress_animation (view=0x55ccc0f225a0) at ./plugin.c:442
 start_progress_animation (plugin=0x55ccc0f22230) at ./plugin.c:786"
1718524,2017-09-21 01:23:51 UTC,"the file 2.svg does not appear to contain any text. It has only a single path as far as I can tell.
could you attach the original svg file that had text, for testing purposes?"
1718524,2017-09-21 08:05:23 UTC,"Sorry I messed up, the original attachment (now deleted) was the result of doing the ""Object to path"" operation. Here is the correct attachment. It requires you to have the font ""Arial Black""."
1718524,2017-09-21 10:46:04 UTC,"thank you for the new file.
I was not able to reproduce the problem on my machine,
Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1718524,2017-09-21 12:35:07 UTC,"I was able to reproduce (with Arial Black, on linux) : https://imgur.com/WfocPDi"
1718524,2017-09-21 13:15:16 UTC,"I'm having a hard time reproducing this bug with another font than Arial Black. I managed to get it to reproduce also with ""EB Garamond"" (attached). Could this have something to do with the font type? (I think both are TTF fonts, but I don't see the problem with all TTF fonts.)"
1718531,2017-09-21 16:36:03 UTC,Thanks for reporting.
1718533,2018-06-25 14:18:10 UTC,"> now our toughbook CF-19 touchscreens can't be calibrated
"
1718533,2017-09-20 20:45:36 UTC,"As a reference, here is one posted workaround:
https://wiki.archlinux.org/index.php/Talk:Calibrating_Touchscreen#Libinput_breaks_xinput_calibrator"
1718533,2018-06-23 02:49:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718533,2018-06-23 02:50:00 UTC,I had finally convinced an archaeological project I work with to upgrade from Ubuntu 12.04 to a newer version and now our toughbook CF-19 touchscreens can't be calibrated :(
1718544,2017-09-21 21:09:24 UTC,A way of fixing this is by adjusting the focus style in the stylesheet.css.
1718544,2017-09-22 15:53:22 UTC,"François Glais, thank you for considering this report."
1718544,2017-09-23 06:57:13 UTC,"> I meant adjusting the default style.
"
1718544,2017-09-23 18:56:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718544,2017-09-25 20:39:41 UTC,"OK, I got it."
1718544,2020-09-14 07:35:24 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1718565,2017-09-21 02:35:37 UTC,Bug 1707187 is about telling the greeter what autologin-session is so it can also make this decision. The default behaviour if the greeter doesn't specify a session should be to use autologin-session.
1718568,2018-03-08 18:56:06 UTC,artful:
1718568,2018-03-08 19:01:43 UTC,xenial:
1718568,2018-03-08 19:11:15 UTC,trusty:
1718568,2018-03-12 08:45:26 UTC,"Hey Dan! I see some autopkgtests failing for this upload for artful, I re-ran them to see how frequently those are reproducible. The systemd one is flaky, but I would like someone to take a look at the network-manager ones."
1718568,2018-03-05 12:16:37 UTC,"Hello Jeff, or anyone else affected,"
1718568,2018-03-15 08:25:38 UTC,This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu2.3
1718568,2018-03-15 08:25:44 UTC,"The verification of the Stable Release Update for isc-dhcp has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1718568,2018-03-15 08:30:17 UTC,This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.10
1718568,2018-03-15 08:32:12 UTC,This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.13
1718568,2018-03-13 22:04:29 UTC,"The only failure shown now seems to be network-manager, which is failing its 'test_no_ap' test; that appears to have been failing for a while:
http://autopkgtest.ubuntu.com/packages/n/network-manager/artful/amd64"
1718568,2018-03-05 12:15:37 UTC,"Hello Jeff, or anyone else affected,"
1718568,2017-09-21 04:07:58 UTC,Confirmed to resolve issue seen here.
1718568,2018-03-02 20:10:14 UTC,"> Is there no other more reliable way to reproduce the case that's being fixed here
"
1718568,2017-09-21 03:49:17 UTC,Confirmed that the same apparent flaw in dhclient-script appears to exist in 4.3.3-5ubuntu12.7 under Ubuntu 16.04.3 LTS
1718568,2018-03-05 12:11:55 UTC,"Hello Jeff, or anyone else affected,"
1718568,2017-10-12 13:44:30 UTC,"Hi Jeff,"
1718568,2018-02-23 18:21:23 UTC,This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu4
1718568,2018-02-27 17:10:21 UTC,"I will be accepting this, but I'm a bit worried about the test case here as it relies on a race-related occasional failure and it might be hard to test reliably. Is there no other more reliable way to reproduce the case that's being fixed here, e.g. to delay the initial tentative link-local address assignment? Probably not?"
1718568,2017-09-21 04:19:06 UTC,"The attachment ""Patch to detect no link-local address"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1718568,2018-02-27 17:17:26 UTC,"Hello Jeff, or anyone else affected,"
1718568,2018-02-27 17:19:10 UTC,"Hello Jeff, or anyone else affected,"
1718568,2018-03-01 19:17:15 UTC,"Unfortunately, this SRU was superseded by a security update."
1718568,2018-03-01 22:40:37 UTC,ok i'll recreate the debdiffs and reupload.
1718568,2018-02-27 17:14:24 UTC,"Hello Jeff, or anyone else affected,"
1718576,2018-09-08 19:58:19 UTC,"Change abandoned by Matthew Thode (<email address hidden>) on branch: master
Review: https://review.openstack.org/568910
Reason: this was done already"
1718576,2018-07-18 05:07:22 UTC,"Change abandoned by Ian Wienand (<email address hidden>) on branch: master
Review: https://review.openstack.org/506524
Reason: we had to squash this into I82dc61fac6c156a4f0d574290c7632077aa53195"
1718576,2018-07-12 17:34:58 UTC,This issue was fixed in the openstack/taskflow 3.2.0 release.
1718576,2018-06-06 23:19:54 UTC,"Reviewed:  https://review.openstack.org/568908
Committed: https://git.openstack.org/cgit/openstack/taskflow/commit/?id=4607f68ae73ebbe7296f16c7dff2fde1884ce947
Submitter: Zuul
Branch:    master"
1718576,2018-05-16 22:32:30 UTC,"Change abandoned by Matthew Thode (<email address hidden>) on branch: master
Review: https://review.openstack.org/568911
Reason: use https://review.openstack.org/#/c/567974/"
1718576,2018-05-16 17:34:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568910"
1718576,2018-04-19 20:43:49 UTC,This issue was fixed in the openstack/watcher 1.9.0 release.
1718576,2018-02-15 12:18:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544887"
1718576,2018-02-23 09:24:05 UTC,"Reviewed:  https://review.openstack.org/544887
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=c81cd675a54c535f4d7af628622e529e7e7804a2
Submitter: Zuul
Branch:    master"
1718576,2018-02-14 12:43:47 UTC,"I tagged my fix in Vitrage as 'partial-bug' because it fixes the bug for now, but we don't have tempest test with networx 2.0 yet, so if anyone pushes code that isn't compatible with networx 2.0 the bug returns."
1718576,2018-02-14 10:15:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544233"
1718576,2018-01-15 18:37:24 UTC,It looks like taskflow is the real issue here. It is relying on the nodes_iter method that was removed in networkx 2.0. See https://networkx.github.io/documentation/stable/release/release_2.0.html?highlight=nodes_iter for how to do that with networkx 2.0.
1718576,2018-01-10 03:16:01 UTC,https://github.com/powervm/pypowervm/issues/4
1718576,2018-01-10 03:15:00 UTC,"Requirement.parse('networkx<2.0,>=1.10'), {'pypowervm'})
Requirement.parse('networkx<2.0,>=1.10'), {'diskimage-builder'})
Requirement.parse('networkx<2.0,>=1.10'), {'taskflow'})"
1718576,2017-10-27 07:33:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/515625"
1718576,2017-09-21 04:53:01 UTC,dib should be ready with https://review.openstack.org/#/c/505963
1718576,2017-09-21 04:41:41 UTC,Projects that want to test their code with the new networkx can use the following review
1718576,2018-02-14 16:53:24 UTC,"Reviewed:  https://review.openstack.org/544233
Committed: https://git.openstack.org/cgit/openstack/vitrage/commit/?id=457c55d8a2b25924988441dc921a4ff884968023
Submitter: Zuul
Branch:    master"
1718589,2017-11-23 10:04:33 UTC,Same problem:
1718589,2017-11-23 10:05:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718603,2017-09-30 08:56:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718607,2019-11-18 13:35:15 UTC,The match stanza workarounds should be written like this (here with eno1 interface):
1718607,2019-02-09 05:21:29 UTC,"Would you mind explicitly describing how to add a match stanza for changing mac addresses?
Do I match for the hardware mac, then specify the new mac in an indented line? Sorry, I'm new to netplan."
1718607,2018-09-24 11:28:33 UTC,Adding a match for the original mac worked for me too.
1718607,2018-08-14 17:26:39 UTC,Adding a match for the original mac worked for me.
1718607,2018-08-01 09:42:10 UTC,"Hi,"
1718607,2018-03-12 13:41:15 UTC,"Trying this with the latest beta version of Ubuntu Bionic (`apt show nplan` returns Version: 0.33), it does not seem to work: I have /etc/netplan/01-netcfg.yaml"
1718607,2018-08-01 06:46:59 UTC,"This also applies to Ubuntu Bionic point release 18.04.1, with netplan version 0.39, even though the reference at https://netplan.io/reference#common-properties-for-all-device-types (search for ""Set the device's MAC"") now indicates that this should be possible."
1718607,2018-02-20 15:04:28 UTC,"Yes, setting mac address on bridge seems to work. Though I have issue with cloud-init on digital ocean when trying to add interface to bridge. Through it is an offtopic.
Thanks, Daniel"
1718607,2018-02-20 12:40:35 UTC,"I​t should be - the code certainly supports parsing macaddress for a
bridge, and I think the backends support it to, but I haven't tried. Please
do try it and let us know if it doesn't work."
1718607,2018-02-20 12:35:27 UTC,"Ah, ok,"
1718607,2018-02-20 12:22:23 UTC,Is it possible to set the mac address for bridge in the same way?
1718607,2018-02-20 12:18:39 UTC,"Looking at the git history, it should be supported in the version in xenial-updates. I don't know what version is in Ubuntu Core, but it looks like it was supported from 0.22 onward."
1718607,2018-02-20 10:44:45 UTC,I can test it once it got backported to 16.04 and landed in Ubuntu Core :)
1718607,2018-02-20 00:52:50 UTC,"Hi Oliver,"
1718607,2018-02-20 23:54:20 UTC,The documentation fix is now in the GitHub repo.
1718613,2018-06-04 19:24:18 UTC,"Upstream Evolution has no manpage, as far as I know. Is this an Ubuntu downstream change?"
1718613,2017-09-21 09:12:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718614,2017-09-21 17:41:56 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1718614,2017-09-21 18:25:26 UTC,"Wow - thanks @hjd - that is exactly the information I was looking for :)
I was also looking into ways of contributing, but then my available time ran out, so I'll look into it some other time (I'm way more familiar with github and git, so bazaar is rather new for me).
Feel free to close my (misplaced) ticket."
1718617,2017-09-21 14:44:24 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1718617,2020-04-22 09:16:25 UTC,"Hi - thanks for reporting this bug, i've closed this bug as part of the migration to Inkscape's new
bug tracker on GitLab."
1718631,2017-09-21 10:50:12 UTC,"StacktraceTop:
 _priv_gst_element_state_changed (element=element@entry=0x7fc36c10e0d0, oldstate=oldstate@entry=GST_STATE_PAUSED, newstate=newstate@entry=GST_STATE_READY, pending=pending@entry=GST_STATE_VOID_PENDING) at gstelement.c:2279
 gst_element_continue_state (element=element@entry=0x7fc36c10e0d0, ret=ret@entry=GST_STATE_CHANGE_SUCCESS) at gstelement.c:2382
 gst_element_change_state (element=element@entry=0x7fc36c10e0d0, transition=<optimized out>) at gstelement.c:2687
 gst_element_continue_state (element=element@entry=0x7fc36c10e0d0, ret=ret@entry=GST_STATE_CHANGE_SUCCESS) at gstelement.c:2356
 gst_element_change_state (element=element@entry=0x7fc36c10e0d0, transition=transition@entry=GST_STATE_CHANGE_PLAYING_TO_PAUSED) at gstelement.c:2687"
1718635,2017-09-21 11:14:45 UTC,If it's a bug then there's one more consequence: it's not thread-safe. If we're calling a decorated method from many parallel threads they'll be sharing the counter field.
1718635,2018-05-17 19:47:06 UTC,"This definitely seems wrong.  I think we could fix the retry_count by resetting it each call, but as you note that wouldn't be threadsafe.  Looking at this code, it might be a little tricky to fix properly because of how the decorator interacts with the loopingcall class.  It's something we need to address though."
1718641,2017-09-22 09:17:22 UTC,See also https://github.com/mcfletch/simpleparse/
1718641,2017-09-21 11:31:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718641,2017-09-21 23:55:06 UTC,*** This is an automated message ***
1718648,2017-09-21 12:01:12 UTC,keybindings defined after an upgrade from 17.04
1718658,2018-10-24 13:34:23 UTC,Note: I'm using 18.04
1718658,2018-11-08 13:53:34 UTC,"I'm using 18.04, everything up to date.
ecryptfs is used for home encryption. Everything seems to work fine, but error messages (as already noted above) appears. Not to repeat everything already said, additional note could be that the messages are not tagged where they really comes from. It is a good practice (at least) everything in the system log to be explicitly clear where it comes from (as in most cases)."
1718658,2018-12-14 09:41:27 UTC,I had updated my laptop so to Ubuntu 18.10 64bit and the message is still present for me.
1718658,2019-07-03 16:58:50 UTC,I have just encountered this issue on 18.04 with Linux 4.15.0-54-generic.
1718658,2019-01-05 11:30:42 UTC,"Trying to mount a personnal dir (not home) with ecryptfs-simple fails, with the same error messages in kern.log as comment #20. (Using Linux Mint 19, Xfce.)
The workaround in comments #26 and #30 works for me. (No sudo like in #28 : with sudo the mount works but the key sig gets added to /root/.ecryptfs . So keyctl has to be launched by thenormal user.)"
1718658,2019-01-05 11:41:31 UTC,I could automate the workaround #26 and #30 but putting the said command in my .profile
1718658,2019-02-09 22:32:37 UTC,This bug affects me too
1718658,2019-02-25 01:12:37 UTC,"Still actual in 18.04.
This looks scary."
1718658,2019-03-20 08:15:48 UTC,"Still the issue persist at present, Ubuntu 18.08 LTS.
The workaround suggested in the bug description works, but for how long I wonder?
Would you trust this bugged ecryptfs to manage sensible data?"
1718658,2019-03-20 12:43:23 UTC,"I would not trust ecryptfs anymore.
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840
Use the time to migrate your data."
1718658,2019-06-02 06:36:19 UTC,This error message is still pressent in my logs in XUbuntu 19.04 (freshly updated as of today). But the mounting finally occurs. However it is still quite annoying...
1718658,2019-07-10 00:15:40 UTC,Upgraded from Ubuntu server 16 to 18 and I too am having this issue.
1718658,2020-06-22 18:13:05 UTC,"I hate to say this, folks, but ecryptfs looks like a dead end for us. It's no longer supported by Ubuntu (the package has been moved to the Universe repo). Also, the problem at hand is caused by systemd, which is run by a man famous for releasing poorly-vetted, system-breaking software, and then refusing to fix the damage he causes."
1718658,2019-09-08 19:20:37 UTC,Still broken in disco.
1718658,2019-09-08 19:22:24 UTC,"The systemd patch I posted earlier no longer works in disco, and the workarounds posted here only partially fix the problem and only for a subset of use cases. Looks like we're back to needing a proper fix."
1718658,2019-10-26 06:19:34 UTC,"I have a completely encrypted home (auto configured) in bionic and have the same error messages in dmesg. Moreover, since a few weeks ago, the home directory sometimes gets broken in a way that all list requests (ls, browse in nautilus) hang just on the home directory (process in S state) and only a reboot solves this. I found the dmesg messages only because of these hangs which might be unrelated."
1718658,2019-11-07 03:44:32 UTC,"#34 said:
This bug affects a cryptographic (read: highly sensitive) feature, is 15 months old, a patch was proposed 12 months ago, but it is still of ""Undecided"" importance and still ""Unassigned""? Come on! Are the ecryptfs-utils and systemd packages unmaintained at Ubuntu?"
1718658,2019-11-08 18:31:28 UTC,"This affects me too. I started seeing the error in dmesg after upgrading from 16.04 to 18.04. Everything seems to work fine, but the message is scary."
1718658,2019-11-30 10:30:32 UTC,"I just upgraded from 16.04 to 18.04 and I'm seeing the same/similar issue.  I have the same messages in the log, and I have an encrypted home folder."
1718658,2020-05-11 06:04:04 UTC,"This is truly unfortunate -- my little media server started off life as an Ubuntu Server 17.04 _Zesty Zapus_ VM, but has been working for years now as 18.04.x and recently failed an upgrade to 20.04 i believe (at least in part) due to this nagging issue.  I'm not able to work around it with my limited skillset, unfortunately.  At a loss, probably going to have to rebuild my entire media server.  Just wanted to chime in that this has been a persistent issue for quite some time.  Lesson learned, will stick to LTS releases for my major appliances moving forward.  Thanks for everyone working on this!"
1718658,2020-05-26 15:47:28 UTC,"Same issue here some time after upgrading from 16.04 lts to 18.04 lts. These error messages appear after reboot:
[ 61.411306] Could not find key with description: [...]
[ 61.411344] Could not find valid key in user session keyring for sig specified in mount option: [...]
[ 61.411383] Error parsing options; rc = [-2]"
1718658,2020-06-22 17:37:02 UTC,I am getting exactly the same issue here after upgrading from 18.04 to 20.04. I use a custom folder and have some shell utilities to run the mount command with the right paramaters. Below SIG and FNEK_SIG continue to match what `ecryptfs-add-passphrase --fnek` reports (and the same as before the update). I am seeing the same in kernel logs via `dmesg` as OP reported.
1718658,2020-06-29 15:31:46 UTC,@foresto Thank you for the message & background info on systemd -- it's very helpful to know when to give up trying.
1718658,2020-10-22 06:59:10 UTC,One additional note for anyone still stuck using this trainwreck for whatever reason:
1718658,2018-10-24 13:33:56 UTC,"This started happening after installing lubuntu-desktop. Even after removing it, it is still failing to mount. After running ""keyctl link @u @s"", it works."
1718658,2019-07-31 12:28:03 UTC,Same here after upgrading Ubuntu Mate 18.04 to 19.04
1718658,2018-10-13 08:41:04 UTC,"I see the messages (starting with ""Could not find key with description"") on a fresh install of Linux Mint 19 Cinnamon."
1718658,2018-03-02 04:10:02 UTC,This doesn't happen in 18.04.
1718658,2018-05-25 03:31:04 UTC,"Something intriguing is that I updated to a 18.04 when it was still not released (I don't know if it was beta or not. I did it in March. Everything was fine. Everything mounted without any workaround with:  mount.ecryptfs_private blabla
Suddenly around April when new updates came, it went back to having this bug."
1718658,2017-09-25 12:24:59 UTC,It is Artful... Sorry!
1718658,2017-10-24 23:00:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718658,2017-11-11 01:29:10 UTC,Exact same problem here. I am using a custom ecryptfs folder (always worked for 3 years). Only way to mount it was by running ecryptfs-manager first.
1718658,2017-11-19 14:43:40 UTC,i have a fresh ubuntu 17.10 installation with an encrypted home (so all auto configured). If i log into my user account it all works fine. However i also get that error message in dmsg:
1718658,2017-11-19 14:46:30 UTC,i have to add that this message only occurs on the first login after a reboot.
1718658,2017-12-13 23:08:00 UTC,"I see the same as @Thorsten. I have an encrypted Private directory. If I log into my user account the directory is correctly mounted. However, I still see the same error message as @Thorsten via dmesg."
1718658,2017-12-29 14:57:34 UTC,"I faced the same issue after upgrading from Ubuntu 17.04 to 17.10 a day ago.
I'm having my home directory encrypted and I'm getting the same error message after every first login.
My home directory is mounted correctly though."
1718658,2017-12-29 15:33:39 UTC,"Okay, the issue with failing X server in my case was not relevant to the encryption errors and was resolved by completing the upgrade process properly:
sudo apt-get update && sudo apt-get dist-upgrade
So this one was more related to the broken upgrade process for 17.04-17.10, so please disregard this part."
1718658,2018-01-18 03:02:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718658,2018-01-18 03:05:09 UTC,"The ecryptfs-manager workaround helps the mount to succeed, but (at least in my case) the system refuses to unmount it afterward. This is a problem for those of us who open our ecryptfs volumes only for as long as they're needed."
1718658,2018-01-18 03:07:35 UTC,"This is a systemd bug, created by this commit:"
1718658,2018-01-18 03:08:14 UTC,"Here's a simple patch to disable the broken systemd feature, and restore ecryptfs functionality."
1718658,2018-07-20 13:14:33 UTC,#26 fixed this for me.
1718658,2018-01-18 04:22:45 UTC,"The attachment ""disable_system_service_session_keyrings.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1718658,2018-01-18 03:32:09 UTC,A systemd build with my patch applied is available here:
1718658,2018-05-14 09:34:54 UTC,"Ooops, no, sorry, it works (/tmp/a was missing)."
1718658,2018-05-14 09:20:43 UTC,Even a direct
1718658,2018-05-14 09:02:06 UTC,Please keep in mind that ecryptfs-mount-private and mount.ecryptfs_private are slightly different things.
1718658,2018-05-05 19:16:08 UTC,ecryptfs (private mount) still does not work under 18.04.
1718658,2018-05-16 08:09:05 UTC,"I had the same problem with Debian.
The workaround I used is creating a link from the key to the keyring"
1718658,2018-05-02 16:30:58 UTC,"Same as @stokito happened to me. Yesterday I upgraded to Kubuntu 18.04 via ""do-release-upgrade"" command from a previous install of Kubuntu 17.10 did some half a year ago. When I restart the system I see the Kubuntu Plymouth start screen but then it never arrives to the login screen (sddm). I can login normally in any of the tty's seeing my home correctly decrypted but with these errors:"
1718658,2018-04-28 17:38:24 UTC,"I upgraded from Ubuntu Mate 17.10 to 18.04 after reboot I passed GRUB then I saw logo of Ubuntu Mate and then by screen become black witout anything.
I pressed Ctrl+F1 and swithed to tty1 then logged in and it show me three last errors from dmesg and firts was:
""could not find valid key in user session for sig ""
""errorparsing options rc = -2"""
1718658,2018-04-28 09:06:45 UTC,"Same as @Thorsten and @callegar. I see the error messages but everything works fine.
I also just upgraded to 18.04 from a fresh install of 17.10 and the errors are still present."
1718658,2018-03-28 13:50:12 UTC,"I don't agree with the last comme,nt : I have a fresh install of 18.04 and get the same error when trying to recover my old savec Private directory :"
1718658,2017-09-23 00:58:12 UTC,"Hello
Can you please add a tag for the version of Ubuntu you are using? (Xenial, Zesty, Artful)"
1718658,2018-05-04 21:05:58 UTC,"Ok, so I restored my system and I got back to my Mate and all my settings are kept.
I did a lot of things, even removed ecryptfs while extracted all my home directory from it.
I removed NVidia drivers but I don't think that they caused the problem.
But only reinstalling of XServer finally resolved the problem. I did something like described here:
https://www.computersnyou.com/4945/re-install-xorg-xserver-completely-ubuntu/"
1718659,2018-07-07 04:09:18 UTC,"Thank you for taking the time to report this bug and helping to make Kubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Kubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Kubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1718659"
1718659,2017-10-23 10:18:31 UTC,"This, indeed, seems to be fixed with Qt 5.9.1, i.e., I am now on Kubuntu 17.10/Qt 5.9 where problem is gone."
1718659,2017-10-22 13:38:41 UTC," There is another test document from me (I truncated original document till crash is reproducible). Instructions:
 - place cursor in empty line #14 (before ""}"");
 - press enter -> Kate crashes"
1718659,2017-09-21 14:28:50 UTC,I get the same crash backtrace given in comment #2 here:
1718659,2017-09-21 13:32:04 UTC,I was editing .cc/.cxx/.h. Could try to make an example file an upload it here if useful.
1718659,2017-09-21 13:10:09 UTC,"Trying kate and kdevelop, I am unable to replicate the issue. Maybe it would be useful to know what types of files are being edited (i.e. .php, .js, etc...)"
1718659,2017-09-21 13:44:12 UTC,"OK, made a chimera file that does the job. It is true that in some files/cases it does not crash."
1718664,2017-09-26 11:58:39 UTC,I've added the PPA from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/ and ran
1718664,2017-09-26 13:42:05 UTC,"It looks like Qt behaves correctly here, but Kate is buggy. See https://bugs.kde.org/show_bug.cgi?id=366568, which was fixed in KDE Applications 16.12."
1718664,2017-10-05 12:21:40 UTC,"Sorry for the delayed reply: I've one PC where opening folders doesn't work in ""Brackets"" [1] as well, but I can't reproduce this issue in a clean VM, so I'll have to investigate some more."
1718666,2018-01-18 20:34:38 UTC,"Change abandoned by Samuel Gillies-Smith (<email address hidden>) on branch: master
Review: https://review.openstack.org/534582"
1718666,2018-01-17 00:09:02 UTC,I have started to work on this bug as there has not been any progress on it for a while.
1718666,2018-01-17 01:35:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534582"
1718666,2018-01-17 02:40:05 UTC,"This bug is more complicated than it initially seems, the delete functionality makes get http requests to these views."
1718682,2017-09-23 15:24:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718685,2017-09-21 15:51:50 UTC,apport information
1718685,2017-09-21 15:51:48 UTC,apport information
1718685,2017-09-21 15:51:47 UTC,apport information
1718685,2017-09-21 15:51:46 UTC,apport information
1718685,2017-09-21 15:51:45 UTC,apport information
1718685,2017-09-21 15:51:44 UTC,apport information
1718685,2017-09-21 15:51:43 UTC,apport information
1718685,2017-09-21 15:51:42 UTC,apport information
1718685,2017-09-21 15:51:41 UTC,apport information
1718685,2017-09-21 15:51:39 UTC,apport information
1718685,2017-09-21 15:51:38 UTC,apport information
1718685,2017-09-21 15:51:37 UTC,apport information
1718685,2017-09-21 15:51:36 UTC,apport information
1718685,2017-09-21 15:51:35 UTC,apport information
1718685,2017-09-21 15:51:34 UTC,apport information
1718685,2017-09-21 15:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1718685,2017-09-21 15:51:40 UTC,apport information
1718687,2017-11-25 03:20:21 UTC,Unsubscribing ~ubuntu-sponsors as there's nothing left to sponsor.
1718687,2017-09-21 15:14:44 UTC,Here is the fix of the problem:
1718687,2017-09-21 16:50:03 UTC,Thanks for reporting.
1718687,2017-11-05 17:28:29 UTC,This bug was fixed in the package discover - 2.1.2-7.1ubuntu1
1718688,2017-09-21 14:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1718688,2017-09-25 17:54:41 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1718688,2017-11-07 16:51:38 UTC,Since I don't have access to the actual Cisco hardware for testing I have been experimenting with hostapd lately.
1718695,2017-09-21 20:20:38 UTC,"The purpose of the source-file is to locate the file in which the relevant defsystem form is. Maybe the source-file of the primary system should be there? It's not clear, though: a dependency on the primary system already exists and I can imagine reasons why some programs might get confused by this partial bit of information."
1718695,2017-09-22 13:55:07 UTC,"I've adapted Declt to handle this, but it still makes sense to me that the source-file slot points to the corresponding file. The only difference with a regular system is that it wasn't hard-coded by the author of the library, but rather created automatically."
1718695,2017-09-22 14:55:32 UTC,"Using the file itself as source-file would be very confusing in other ways, too: the original meaning of source-file was a file you read to get the defsystem, but that's NOT AT ALL what you get if the file of a package-inferred-system file is loaded."
1718702,2017-10-05 14:53:44 UTC,"OK, I confirm is fixed. But you have to make sure on the system the version of Networkx is at max 1.11 (not 2.x)."
1718702,2017-09-22 06:35:56 UTC,Working! [1] fxied it. Thanks!
1718702,2017-09-21 22:39:12 UTC,This is due to networkx 2.0.  changes are in flight to fix this with a pin.  please try again with 2.9.0 when it is released shortly
1718702,2017-10-05 14:17:21 UTC,"Hello,
I am testing master and it still fails for me:"
1718703,2017-10-11 03:55:19 UTC,Then I guess it's a better idea to try different approach.
1718703,2017-10-17 04:10:56 UTC,"dmesg1, dmesg2, which are the same as LP: #1678477:
[    7.388222] usb 3-14: can't read configurations, error -110"
1718703,2017-10-14 18:25:53 UTC,Didn't work. I have 4 dmesg logs.
1718703,2017-10-11 07:20:26 UTC,"Try this:
http://people.canonical.com/~khfeng/lp1718703-3/"
1718703,2017-10-06 17:55:56 UTC,"I tried the new kernel with 4 reboots. On the first reboot, the problem was not there and everything was good. On reboots 2-4, the problem returned, and I had to unplug the keyboard at the login screen to get it to work."
1718703,2017-10-11 07:20:54 UTC,"Also, it's quite hard to fully understand the problem without full dmesg."
1718703,2017-09-23 18:23:05 UTC,Can you attach full dmesg?
1718703,2017-09-23 16:18:30 UTC,Still getting error -110.
1718703,2017-09-22 04:21:27 UTC,Please try kernel here:
1718703,2017-09-21 16:30:28 UTC,Confirmed by Piotr Sowiński (psow86)
1718703,2017-09-21 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1718703,2017-10-01 10:08:30 UTC,"Please try kernel in [1], it increased delay time."
1718704,2017-12-07 15:34:20 UTC,"I'm using Gnome on Wayland on Fedora 26. I noticed now that there was a small indication of a notification at the top of the Gnome desktop. When clicking on the ""little ball"" representing the notification I saw a message like: Deja-dup started automatic backup (I do not have the exact text because clicking on the notification made it go away). When I clicked on the notification the Backup progress window appeared."
1718704,2017-12-07 15:47:27 UTC,"However, still when you close the progress window, I see now way on how to make it appear again while a backup is already running."
1718704,2018-02-11 18:47:22 UTC,"Yes, I think you're right that the progress window can't come back once you close it...  That's not great."
1718704,2019-01-07 03:04:31 UTC,"I believe the following patch in master should fix this, by raising the progress window (if it exists) when opening deja-dup."
1718706,2019-09-19 11:53:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1718706,2017-12-14 04:49:33 UTC,This is partially solved by LP:1735025. The error from TGT is ignored and the images continue to get processed but the following is in the log:
1718706,2017-12-14 04:50:05 UTC,MAAS does not report any problems with TGT with LP:1735025 applied.
1718713,2017-09-21 16:00:07 UTC,This change was made by a bot.
1718713,2017-09-25 17:53:07 UTC,Does this bug go away if you boot back into the prior kernel version?
1718713,2017-09-25 17:53:18 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1718713,2017-09-25 18:09:42 UTC,"Hi Joseph,"
1718713,2017-09-25 22:56:15 UTC,tested 4.14. .x-x kernel. no network but flickerty not there.
1718713,2017-09-26 15:09:14 UTC,Here is vid of one flickerty session.
1718713,2017-09-27 09:07:38 UTC,"I have the same problem running the Ubuntu Beta in Virtualbox with as far as I remember 4.13.0.11. All other Ubuntu Betas (L-, X- and Mate) did use that Linux version too. I tried a fresh install from the latest second daily build of 26-9 with the same result. The symptom is a VM-screen that switches from size 4-6 times and disk and network lights of Vbox status bar died out and we are left with a black screen.
The host is Ubuntu 16.04 and Vbox is 5.1.28.
I can't create a memory dump, since CTR + ALT + Fn is catched by the Host system."
1718713,2017-09-27 09:12:15 UTC,"Forgot to mention the other Ubuntu Betas (L-, X- and Mate) have no problem and work normally."
1718717,2017-10-21 15:39:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718717,2017-10-24 05:31:24 UTC,Still comes up just after logging in to cinnamon.
1718717,2017-10-09 15:33:15 UTC,"This Bug came again just after shutdown, reboot and logging in to cinnamon."
1718717,2017-09-29 14:11:43 UTC,"Thanks for the feedback, but ""Fix released"" means that there is actually released a newer package version which fixes the problem. In your case the bug report was caused by some error on your system, so I mark the bug report as ""Invalid""."
1718717,2017-09-21 15:55:00 UTC,"StacktraceTop:
 avahi_entry_group_free (group=0x0) at entrygroup.c:242
 dnssdDeregisterInstance (srv=0x56336dce7608 <WebIFSrv>, from_callback=from_callback@entry=0) at dirsvc.c:684
 dnssdDeregisterInstance (from_callback=0, srv=<optimized out>) at dirsvc.c:670
 dnssdStop () at dirsvc.c:1297
 cupsdStopBrowsing () at dirsvc.c:270"
1718717,2017-09-28 06:59:55 UTC,Since I executed
1718717,2017-09-27 19:10:28 UTC,Principally this kind of problem got already fixed and should not occur again with the cups-daemon 2.2.4-7 package or newer. It is possible that perhaps your /usr/sbin/cupsd file got somehow overwritten by an older version.
1718717,2017-10-04 09:30:39 UTC,This bug is not fixed. It just came up again after reboot.
1718719,2020-10-07 18:48:57 UTC,Is there still an issue left here for upstream QEMU?
1718719,2020-08-04 08:18:22 UTC,"upstream can't reproduce this bug, so I wonder if the backport was incomplete and it's fixed in the current release (1.20.8), could you test again?"
1718719,2019-05-10 15:53:05 UTC,-- GitLab Migration Automatic Message --
1718719,2017-10-01 07:05:40 UTC,"Actually, this bug would affect current 1.19-branch too since the patches are backported there as well. You can test ppa:canonical-x/x-staging to verify, which has xorg-server from current stable branch."
1718719,2017-10-01 00:13:43 UTC,is the patch providing any user visible improvement? if not it would probably make sense to delay including it to next cycle
1718719,2017-09-30 16:47:31 UTC,"Now the question is should the patch be dropped or wait for a fix from upstream. I'm leaning towards the first option, since artful is about to be released."
1718719,2017-09-29 18:59:51 UTC,Upstream bug is probably https://bugs.freedesktop.org/show_bug.cgi?id=102475 ?
1718719,2017-09-29 18:47:03 UTC,"So it is likely a wayland <-> SDL thing.
@Desktop Team could you take alook into this - the repro steps in c#2 are pretty easy I'd think but none of us would know where in the UI stack to look for."
1718719,2017-09-29 17:27:50 UTC,Hi! I am running Artful on my X1 Carbon Gen3.
1718719,2017-10-06 11:05:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718719,2017-09-22 06:34:22 UTC,"Hi Mathieu,
thanks for the report but since we are up-to-date with qemu and I can't find an obvious breakage we might have introduced for this, this should go to qmeu-upstream in this case."
1718719,2017-09-01 16:43:07 UTC,the issue isn't there when using your debug command but it begins in that session if gsd-media-keys is started... I'm calling it a week now but I'm going to poke to it a bit more on monday
1718719,2017-09-01 07:15:06 UTC,"Well, what this patch does is disabling any specific grab handler if the Xwayland grab protocol is not available, by postponing the setup of those handler until Xwayland can bind to the relevant interface as advertised by the compositor."
1718719,2017-08-31 23:04:19 UTC,the patch doesn't seem to make a difference
1718719,2017-08-31 16:26:13 UTC,"Created attachment 133910
Test patch"
1718719,2017-08-30 14:57:34 UTC,"Tried reproducing the issue with the arrow keys using the current Xwayland from master with mutter/gnome-shell from master, using qemu-kvm with SDL backend (-display sdl) but failedto reproduce, all keys (including the arrow keys) work fine in the guest."
1718719,2017-08-30 13:36:16 UTC,"The Ubuntu diff is
http://launchpadlibrarian.net/334552966/xorg-server_2%3A1.19.3-1ubuntu3_2%3A1.19.3-1ubuntu4.diff.gz"
1718719,2017-08-30 12:40:12 UTC,Can you please elaborate of what exactly has been backported and the resulting patches?
1718719,2017-08-30 11:42:57 UTC,"The Ubuntu maintainer backported the recent change to add keyboard grabbing to xwayland, with that change the keyboard arrow keys stop working in kvm"
1718719,2017-09-22 06:54:14 UTC,"I wanted to write steps to reproduce, which should be as simple as:
$ wget http://cdimage.ubuntu.com/daily-live/current/artful-desktop-amd64.iso
$ qemu-system-x86_64 -m 512 -boot d -cdrom artful-desktop-amd64.iso"
1718720,2020-10-13 13:02:34 UTC,"This Bug is old but still not fixed.
There is also a ticket in the debian bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851407"
1718720,2018-11-06 11:23:05 UTC,"It is quite possible that version 1.3.0 looks and behaves differently, because the plugin code was ported to GTK3 with some changes here and there."
1718720,2018-08-19 22:52:12 UTC,Maybe related: https://bugzilla.xfce.org/show_bug.cgi?id=12702
1718720,2017-10-20 05:36:10 UTC,"I don't know of any way to make this work with the package from 17.10 / Artful, but installing the current 1.2.6-1 xfce4-sensors-plugin from 17.04 / Zesty makes the plugin work. No other changes were needed. With the plugin from Zesty the plugin output on the panel immediately changes when I change settings. I got it from: https://packages.ubuntu.com/zesty/amd64/xfce4-sensors-plugin/download"
1718720,2018-10-31 21:54:02 UTC,"Maybe I was confused. I was just setting up xfce4-sensors-plugin 1.3.0-2 Ubuntu 18.10 and noticed something. When I double-click on the plugin it opens ""Sensors Viewer"". If I want to reconfigure the plugin I need to right click on it and select ""Properties"". This opens ""Sensors Plugin""."
1718720,2020-10-13 12:58:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718726,2017-09-21 16:30:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506280"
1718728,2017-09-22 13:57:36 UTC,https://review.openstack.org/#/c/506283/
1718728,2017-12-07 14:51:05 UTC,This issue was fixed in the openstack/kolla-ansible 6.0.0.0b2 development milestone.
1718733,2017-10-04 06:42:28 UTC,could you confirm if this is still affecting you? The permissions should be correctly created upon the initial start of the container: https://github.com/openstack/openstack-helm/blame/master/nova/templates/bin/_nova-compute-init.sh.tpl#L25
1718733,2018-05-10 20:24:11 UTC,need feedback?
1718737,2017-09-21 17:38:40 UTC,"The following kern.log is a record of the kernel events. Please note that I used the widget to close the Ethernet connection, and note subsequent issues. Also note that the WiFi connection has a lease time for a nailed up connection IP address (??)"
1718740,2017-09-21 17:49:00 UTC,"Yes, since customers want to make use of the improvements of the new kernel with these preview scenarios, let's please enable CONFIG_KVM as soon as possible."
1718740,2017-10-09 19:49:15 UTC,This bug was fixed in the package linux-azure - 4.11.0-1013.13
1718743,2017-09-24 20:26:03 UTC,Merged in https://gitlab.com/inkscape/inkscape/commit/f81751abb770d0367d6c515cdcb56a7954714eab
1718743,2017-09-23 15:14:53 UTC,Improved version of the patch.
1718743,2017-09-21 18:29:16 UTC,"Seems to be a regression in master:
- working in Inkscape 0.92.2 (c522dc6d40, 2017-09-16)
- not working in Inkscape 0.92+devel (42c84a5464, 2017-09-20)"
1718743,2017-09-23 10:19:51 UTC,"I think that the most robust way to avoid this problems is to transform the duplicate clipping/masking object directly, instead of: transforming -> duplicating -> transforming back the original."
1718747,2018-07-27 07:54:05 UTC,This issue was fixed in the openstack/keystone 12.0.1 release.
1718747,2018-07-27 07:41:26 UTC,This issue was fixed in the openstack/keystone 11.0.4 release.
1718747,2018-02-06 21:19:13 UTC,"> The user side actually worries me less than the project side: deleting a project without deleting the resources in the remote services leave them unmanageable and require a system level admin to clean them up with some global scope of responsibility.
"
1718747,2018-05-02 13:43:01 UTC,"Change abandoned by Lance Bragstad (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/511062"
1718747,2018-02-19 14:57:59 UTC,"Change abandoned by Lance Bragstad (<email address hidden>) on branch: master
Review: https://review.openstack.org/506340"
1718747,2018-02-15 05:28:41 UTC,"Reviewed:  https://review.openstack.org/543379
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b6a009254f7975bf806c499874ad87746bb8cbd8
Submitter: Zuul
Branch:    stable/ocata"
1718747,2018-02-14 16:53:58 UTC,"Change abandoned by Morgan Fainberg (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/511061
Reason: Abandoning based upon IRC disucssions. this is not needed."
1718747,2018-02-12 21:18:43 UTC,"Reviewed:  https://review.openstack.org/542483
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=fb81469404f4c6e8a5f25896d155e02491c3b610
Submitter: Zuul
Branch:    stable/pike"
1718747,2018-02-12 08:28:32 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/543379"
1718747,2018-02-09 15:25:36 UTC,This issue was fixed in the openstack/keystone 13.0.0.0rc1 release candidate.
1718747,2018-02-08 23:20:57 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/542483"
1718747,2018-02-08 23:15:27 UTC,"Reviewed:  https://review.openstack.org/539347
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=62ee18b359cbb2e6a9469bdaac9057ef19de1bdf
Submitter: Zuul
Branch:    master"
1718747,2018-02-06 19:31:05 UTC,"The original behavior was bad, too.  Would have been better to fix it deliberately than as a side effect."
1718747,2017-09-21 21:26:04 UTC,"@Adam, but the error occurs when trying to delete a domain that is disabled. Notice the steps disable the domain before deleting it."
1718747,2018-02-06 17:53:11 UTC,"Heh.  Before accidentally orphaning all of the users ain a domain?  At least one more, I would say."
1718747,2018-02-06 17:57:59 UTC,Adam - deleting all the users and groups was the original behavior: http://git.openstack.org/cgit/openstack/keystone/tree/keystone/identity/core.py#n491
1718747,2017-09-21 21:10:28 UTC,"Although not explicitly in the SQL model definition, the FK is user.domain_id -> project.id is added in a migration: https://github.com/openstack/keystone/blob/2bd88d3/keystone/common/sql/expand_repo/versions/014_expand_add_domain_id_to_user_table.py#L140-L141"
1718747,2017-10-10 22:08:41 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/511061"
1718747,2017-10-10 22:08:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/511062"
1718747,2017-10-10 22:09:43 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/511063"
1718747,2017-09-21 21:01:30 UTC,"While the error message is ugly (should not 500 the server) the behavior is intentional: we put a referential constraint on there to keep from accidentally deleting a load of data if the user accidentally deletes the domain:  you have to disable the domain first, and then delete it for the same reason."
1718747,2018-01-16 13:51:30 UTC,@samuel Are you still working on the proposed fix https://review.openstack.org/#/c/511061 ? It failed Zuul and status since October 2017 has not been changed.
1718747,2018-01-30 22:29:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539347"
1718747,2018-02-06 17:07:32 UTC,"""Unable to delete domain with users in it Edit""  is the desired behavior.  Please restate the bug.  I think the problem is that if you try you get the database into an unstable state?"
1718747,2018-02-06 17:12:41 UTC,"Deleting a domain should not be a casual thing.  Once you do, all of the resources in the remote services are unmanagable. Removing the local user records, while annoying, ensures you do not accidentally destroy your entire user database by accidentally deleting a domain."
1718747,2018-02-06 17:29:24 UTC,APIs have no feelings. Nor can it read the user's mind. All it care is performing the function it is designed to do. We've already required a domain to be disabled before being deleted. I know the Hawaii missile alert freaks people out. But come-on. :-) How many safe-guards do we need?
1718747,2017-10-24 23:00:43 UTC,"Change abandoned by Tony Breeds (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/511063
Reason: This branch (stable/newton) is at End Of Life"
1718761,2017-09-21 20:25:52 UTC,apport information
1718761,2017-09-21 20:25:50 UTC,apport information
1718761,2017-09-21 20:25:51 UTC,apport information
1718761,2017-09-21 20:25:52 UTC,apport information
1718761,2017-09-21 20:25:53 UTC,apport information
1718761,2017-09-21 20:25:49 UTC,apport information
1718761,2020-04-20 18:23:54 UTC,"I hit this today, and filed bug 1873917 before dupe'ing it to this.
I'd think that the main pain points are
a.) using overlay in a container that is backed by zfs via lxd
b.) using overlay when using zfs root (https://didrocks.fr/2019/10/11/ubuntu-zfs-support-in-19.10-zfs-on-root/)"
1718761,2020-07-04 17:44:18 UTC,I'm using Focal with ZFS on root. I installed the docker snap package today and could not get the service to start. Logs show:
1718761,2020-07-05 18:13:25 UTC,"See also this upstream PR: https://github.com/openzfs/zfs/pull/9414
and the one before it: https://github.com/openzfs/zfs/pull/8667"
1718761,2020-07-13 21:44:19 UTC,"I am arriving here as I would also like to run containers (docker) over a zpool as the storage backend. In my case, I am running Ubuntu Server (Focal) on a Pi 3B, I would ideally have root on zfs but with it being a Pi, I have not done this yet. I have an externally attached USB pool for real data and have left the OS as it is on the SD card, however, as the above says, I would like to move more of my systems towards ZFS with time and use Ubuntu-based distros and containers on a lot of them, where these can't be run under illumos as VMs."
1718761,2020-09-02 15:40:20 UTC,"The proposed fixes are still Work-In-Progress, hopefully they will get merged into ZFS in the next few months."
1718761,2018-12-21 12:58:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718761,2017-09-21 20:25:48 UTC,apport information
1718761,2020-04-22 01:55:15 UTC,I ran into this exactly as smoser described using using overlay in a container that is backed by zfs via lxd.  I believe this will become more prevalent as people start to use zfs root with Focal 20.04.
1718761,2017-09-21 20:25:45 UTC,apport information
1718761,2017-09-21 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1718761,2017-09-21 20:25:24 UTC,apport information
1718761,2017-09-21 20:25:25 UTC,apport information
1718761,2017-09-21 20:25:26 UTC,apport information
1718761,2017-09-21 20:25:47 UTC,apport information
1718761,2017-09-21 20:25:28 UTC,apport information
1718761,2017-09-21 20:25:27 UTC,apport information
1718761,2017-09-21 20:25:30 UTC,apport information
1718761,2017-09-21 20:25:31 UTC,apport information
1718761,2017-09-21 20:25:32 UTC,apport information
1718761,2017-09-21 20:25:33 UTC,apport information
1718761,2017-09-21 20:25:44 UTC,apport information
1718761,2017-09-21 20:25:29 UTC,apport information
1718767,2017-09-28 19:31:48 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/508277"
1718767,2017-10-05 16:48:28 UTC,"Reviewed:  https://review.openstack.org/508277
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3fc09ed05a1b3613c5fbbc6f955dbf68889e9a3e
Submitter: Jenkins
Branch:    stable/pike"
1718782,2020-09-10 16:16:46 UTC,"I am working on 3.4.2 version, still seeing this issue"
1718782,2020-09-10 18:45:35 UTC,"Thanks for bringing this bug to the fore, Francisco."
1718782,2020-09-21 15:59:26 UTC,"I have tested this code and consent to signing off on it with my name, Mary Llewellyn and my email address, <email address hidden>"
1718782,2020-09-21 16:18:15 UTC,"Noting for whoever reviews this (which might be myself, later) that an AngularJS follow-up for this patch would be both advisable and straightforward to do, given the target to 3.5.x and the potential of also targeting this to 3.4.x."
1718790,2017-09-21 21:53:28 UTC,"It's a disaster here, but i insist, i want to try,so i ask for your assistance. Regards - Uklas."
1718790,2017-09-22 04:25:58 UTC,O.k cappuccino decaffeinato. Grazie amici.
1718790,2017-10-02 17:28:07 UTC,"O.k you know this & other problems _ Stay well, can wait"
1718790,2017-10-09 02:44:43 UTC,Nothing that we can do. I'm so sorry
1718808,2017-09-22 10:59:56 UTC,"thx Fred for the feedback. This is a probably bug introduced in 4ppa43.
Working on it."
1718808,2017-09-22 11:34:04 UTC,Should be fixed from 4ppa44.
1718811,2018-06-15 18:39:36 UTC,"Change abandoned by Tim Burke (<email address hidden>) on branch: master
Review: https://review.openstack.org/509321
Reason: Submitted against s3api as https://review.openstack.org/#/c/575818/"
1718811,2018-12-17 20:51:47 UTC,This issue was fixed in the openstack/swift 2.20.0 release.
1718811,2019-10-15 10:12:31 UTC,"The fix only handles the multi upload. What about multi delete? Multi delete with 1000 keys can take a long time, and we should send the whitespace char to keep the connection from timing out."
1718820,2017-09-22 02:13:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506444"
1718820,2017-09-22 05:37:29 UTC,"Change abandoned by zhangyangyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/506444"
1718823,2017-11-02 00:03:41 UTC,"Agreed. This needs to change in the schema to allow for it in the first place, but then the grammar already exists to handle it. We just need to add it to the `GlobalGrammarProcessor`."
1718825,2017-09-22 02:28:20 UTC,"@Canonical if the effort is little, just backport it. Thx"
1718825,2017-09-22 13:37:43 UTC,Right away I notice some commits which look to be fixes for commits in this series:
1718825,2017-09-24 01:39:07 UTC,Thanks
1718825,2017-09-28 16:14:20 UTC,It's really not clear to me whether some of the changes to arch/x86/mm/tlb.c should be applied without additional prerequisite patches. Can you please advise? Thanks.
1718825,2017-09-29 05:11:26 UTC,"@Canonical
if the backporting works is not easy, we just move it into 18.04.
If the backporting is fine for you, just do it."
1718825,2017-10-03 12:30:37 UTC,Let's defer to 18.04.
1718825,2017-10-26 02:11:16 UTC,"The changes are too invasive (they will not backport cleanly), they are not stable yet (there are still bugs being found in 4.14-rcX). The performance implications are also not well-documented across the platforms that we care about."
1718831,2018-07-19 20:45:42 UTC,In my build the settings get read from and written to:
1718831,2018-12-18 10:45:37 UTC,Hi !
1718831,2018-12-18 04:08:15 UTC,I'm going to move this issue to 6 as the quick-ish fix causes massive slowdown in routing and the fixes I can think of for faster routing are not simple.
1718831,2018-07-20 11:42:52 UTC,"Sorry about that Seth.  I misread the bug report.  I'll create a new bug
report for the magnetic pads issue."
1718831,2018-07-19 20:56:06 UTC,Hmm... Can we split off the magnetic pads issue?  This report is about connectivity not seeing collisions between pads and tracks that don't have anchor points overlapping.
1718831,2018-07-19 20:31:13 UTC,"@Wayne, I can’t reproduce the Magnetic Pads option getting reset.  Are there steps to cause it to happen?"
1718831,2018-02-20 16:40:15 UTC,Please provide demo file.
1718831,2018-07-19 18:04:29 UTC,"This is not a bug per se.  It appears that the recent options dialog work inadvertently clears or resets the magnetic pads option.  To fix this just open the pcbnew options dialog and enable the magnetic pads option.  @Jeff, you might want to take a look at the pcbnew options dialog to prevent this from happening or I see a lot more bug reports in our future."
1718831,2018-07-19 17:45:44 UTC,I just noticed this is in the 5.0 branch and as well and it makes routing really difficult.  I'm not sure when this got broken.  I'm raising the severity and the changing the milestone to 5.0.1.
1718831,2018-06-23 20:50:45 UTC,"Thanks for the heads up, Jeff;  That one is actually fixed already -- hooray! :)"
1718831,2018-06-23 20:35:42 UTC,"@Seth, there's also the related: https://bugs.launchpad.net/kicad/+bug/1571952"
1718831,2018-02-21 04:09:45 UTC,"Modified version of previous example, showing the DRC error which results when the pad of a different net overlaps the track electrically. (But does not terminate on the track)"
1718831,2018-07-19 18:06:38 UTC,I'm going to change the severity and the milestone since technically it only effect the development branch event though can effect previous versions.
1718835,2020-01-27 13:45:30 UTC,"pagerduty_nagios.pl puts new events in a queue, and periodically tries to flush the queue by sending the events to the pagerduty service. If errors prevent the queue from being flushed, the notification script will retry until successful; however, if errors affect the enqueuing (as per bug 1718833) the events are indeed lost."
1718850,2018-08-08 07:58:03 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1718850,2020-05-09 22:51:41 UTC,"Leaving the system and coming back, it was fine and the extensions worked again.  Possibly a side effect of bug 1876641 (high memory usage?)"
1718850,2020-05-09 21:30:26 UTC,"My system is currently in a state where changes in gnome-shell-extension-prefs also aren't sticking.    The toggle toggles, but extension isn't activated.  Not sure if this is a different bug or the same one."
1718850,2020-04-09 09:46:05 UTC,Ubuntu 20.04:
1718850,2020-03-09 07:02:39 UTC,@Jeremy
1718850,2019-10-12 12:27:27 UTC,This is fixed in GNOME Shell directly (try running the gnome-shell-extension-prefs tool) in Ubuntu 19.10 which will be released in a few days.
1718850,2018-12-10 18:31:30 UTC,Still happens. Ubuntu 18.10
1718850,2018-04-13 15:23:36 UTC,"FYI, I started the discussion on the GNOME Shell mailing list in october: https://mail.gnome.org/archives/gnome-shell-list/2017-October/msg00034.html
There is a pending request with patches posted in November on upstream bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=789852 and patches in Tweaks are waiting on the GNOME Shell part to be merged."
1718850,2017-09-22 12:20:40 UTC,"I believe this is actually a gnome-shell bug since we get the same behavior with
gnome-shell-extension-prefs"
1718850,2017-09-29 12:39:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718850,2017-09-28 13:35:03 UTC,Are you going to work on it?
1718850,2017-09-27 21:43:10 UTC,"Daniel, yes the extensions that are part of GNOME Classic (and installed as part of gnome-shell-extensions) have the same problem."
1718850,2017-09-27 20:36:33 UTC,"Just to be clear, the desktop team does not maintain Tweaks, so the rls-aa-incoming tag is not for us."
1718850,2017-09-27 00:08:52 UTC,"Do you mean classic or default? Because the gnome-classic session is part of package 'gnome-shell-extensions', not installed by default :)"
1718850,2017-09-26 21:41:33 UTC,"Daniel, no this is a bug for all GNOME Shell modes including GNOME Classic."
1718850,2017-09-25 19:58:40 UTC,I wonder if they appear off because we don't have package 'gnome-shell-extensions' installed by default?
1718850,2017-09-22 12:23:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1718850,2017-10-23 14:26:19 UTC,"I filed https://bugzilla.gnome.org/783104 months ago requesting the ability to disable ""system"" (enabled by the GNOME Shell mode) extensions, but the bug was closed. :("
1718858,2017-09-25 06:41:02 UTC,"The additional space is useful if you want to chroot into the partition and add stuff, like new packages, before first boot. This is a real use case when creating customized images on top of ubuntu-image output."
1718858,2017-09-22 21:37:08 UTC,"On Fri, Sep 22, 2017 at 07:18:52AM -0000, Alfonso Sanchez-Beato wrote:

> Public bug reported:
"
1718860,2017-09-22 09:17:19 UTC,Fix for this (Gary's branch); https://github.com/adglkh/ubuntu-image/pull/1
1718860,2017-09-22 16:45:47 UTC,"On Fri, Sep 22, 2017 at 07:25:12AM -0000, Alfonso Sanchez-Beato wrote:

> Public bug reported:
>
> When the size of the system data partition is specified in the gadget
> snap, like in:
>
> https://github.com/alfonsosanchezbeato/pc-amd64-gadget-
> cpc/blob/master/gadget.yaml
>
> It turns out that this is really respected: ""parted"" actually shows the
> right size, but when mounting the partition, ""df -h ."" reveals that the
> size is much less.
>
> This is because the partition is properly created, but the filesystem
> inside the partition is not filling the partition.
>
> A workaround for this is running these commands on the partition:
>
> # e2fsck -fy <part>
> # resize2fs <part>
>
> But this should not be necessary indeed.
"
1718860,2017-09-25 06:42:25 UTC,"The additional space is useful if you want to chroot into the partition and add stuff, like new packages, before first boot. This is a real use case when creating customized images on top of ubuntu-image output."
1718860,2017-09-25 08:04:55 UTC,"Besides, not sure if I agree on whether not expanding the partition/fs helps with the size. If it is the raw dd image, it does not. If we are talking about the compressed image, I am not sure if there is a great impact, as regardless of whether the extra size is included in the partition or not, it should be mostly a bunch of zeros if unused."
1718871,2018-07-24 09:33:11 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1718871,2017-10-20 08:50:32 UTC,4.1.demsg is from kernel 4.1 which works fine for s4 suspend.
1718871,2017-10-20 08:49:30 UTC,"For different kernel on http://kernel.ubuntu.com/~kernel-ppa/mainline/ and test on Ubuntu 14.04.1. All version below 4.2 works fine for S4, the kernel of 4.2, 4.3, 4.3 can't works for S4."
1718871,2017-10-13 07:23:20 UTC,"Can you find the first kernel version from [1], that introduced the regression?"
1718871,2017-10-13 05:52:26 UTC,The attach file of ap.bug is apport-cli report on 16.04.3 with kernel of 4.10.0-28-generic. This kernel have same issue for s4.
1718871,2017-09-25 15:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1718871,2017-09-26 16:10:47 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1718871,2017-09-26 09:19:18 UTC,For the newest upstream kernel of http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/linux-image-4.14.0-041400rc2-generic_4.14.0-041400rc2.201709242031_amd64.deb. The S4 test is same error.
1718871,2017-09-25 18:13:24 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1718871,2017-09-22 08:31:37 UTC,This S4-cpu-down-screen-show.pdf contains the testing screen shot and dmesg of works well testing.
1718871,2017-09-22 08:19:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1718871,2017-09-27 01:49:47 UTC,"Tested works well kernel are:
   kernel 3.13.0-24-generic of 14.04
   Kernel 3.13.0-031300-generic on 14.04 from （http://kernel.ubuntu.com/~kernel-ppa/mainline/)"
1718872,2017-10-03 05:48:33 UTC,"Hi Loic,"
1718872,2019-02-05 20:26:39 UTC,moved from https://bugs.launchpad.net/yade/+bug/1718872 to https://gitlab.com/yade-dev/trunk/issues/36
1718877,2017-10-24 12:42:23 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1718877,2017-11-15 01:06:56 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1718877,2017-10-25 19:22:33 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1718877,2017-10-04 17:40:53 UTC,"Reviewed:  https://review.openstack.org/506760
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=befcda5b2149492cf6b5c7856def238fbb9079d8
Submitter: Jenkins
Branch:    stable/ocata"
1718877,2017-09-28 07:32:07 UTC,"Reviewed:  https://review.openstack.org/506754
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6538175c08f127c20e72e1d347af3eb3d54d6838
Submitter: Jenkins
Branch:    stable/pike"
1718877,2017-09-22 19:32:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/506760"
1718877,2017-09-22 19:05:23 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/506754"
1718877,2017-09-22 17:36:34 UTC,"Reviewed:  https://review.openstack.org/506585
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0cc94bfd5934e793cb8d739e132b52fa40bcddb0
Submitter: Jenkins
Branch:    master"
1718877,2017-09-22 10:28:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506585"
1718884,2017-09-22 09:06:07 UTC,P.S.: Here's a screenshot of the behaviour.
1718884,2019-06-03 14:32:40 UTC,Thank you for your bug report. Do you still see that issue using the current version?
1718884,2019-08-03 04:17:24 UTC,[Expired for gnome-todo (Ubuntu) because there has been no activity for 60 days.]
1718886,2017-10-30 19:43:07 UTC,This bug was fixed in the package linux - 4.4.0-98.121
1718886,2017-10-18 08:56:41 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1718886,2017-10-10 13:34:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1718886,2017-09-22 09:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1718886,2017-09-22 16:19:40 UTC,"The attachment ""0001-UBUNTU-snapcraft.yaml-add-dpkg-dev-to-the-build-deps.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1718890,2017-10-09 09:34:13 UTC,"Just found this article
https://github.com/systemd/systemd/issues/5755"
1718890,2017-10-09 09:38:10 UTC,To make clear the bearing of this:
1718890,2017-12-08 14:10:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718890,2017-12-11 16:47:23 UTC,"thank you for your bug report. So the issue there is the same as in the upstream ticket, that you expect the lookups to always be done using the servers in the order of what is in resolv.conf? if so could you update the title to state that/what you believe the problem to be exactly?"
1718891,2017-09-22 15:03:59 UTC,"Yes, that seems to be it."
1718891,2017-09-22 14:18:32 UTC,similar to Bug 1618594 ?
1718891,2017-09-22 12:13:43 UTC,"Yes I am, but the underlying problem is with the eps file, not latex. The Omit text in pdf and create Latex file is also not working."
1718891,2020-09-29 15:17:06 UTC,Closing because INVALID.
1718891,2017-09-22 10:46:03 UTC,Also your file does not contain the (t1) and (t2) texts.
1718891,2017-09-22 10:30:41 UTC,"So the eps does have the text, visually, but there is no (t1) or (t2) in the .eps file when opened with gedit. This, as I have come to learn prevents psfrag from picking up the text."
1718891,2017-09-22 09:56:09 UTC,"thank you for taking the time to issue a report.
problem not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06), result attached here."
1718891,2017-09-22 11:49:23 UTC,"it looks like you are trying to output to Latex. If that is the case then you might want to try the option that says ""Omit text in pdf and create Latex file"". Unfortunately, I do not know enough about Latex to be able to help you with that option."
1718897,2018-07-24 09:33:13 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1718897,2020-05-14 12:00:22 UTC,Still broken in 18.04:
1718897,2017-09-25 16:23:20 UTC,Does manually adding a symlink like in comment #4 of bug 1702056 work around the bug?
1718897,2017-09-22 10:00:07 UTC,This change was made by a bot.
1718897,2017-09-25 16:43:28 UTC,"Yes, symlinking:"
1718922,2017-09-22 11:55:07 UTC,"I have uploaded the package to this PPA:
https://launchpad.net/~rbalint/+archive/ubuntu/scratch/+packages"
1718922,2017-09-22 13:10:34 UTC,The packaging repository is at https://git.launchpad.net/~rbalint/ubuntu/+source/gce-compute-image-packages but i did not include the URL in d/control because it may move to a better location.
1718922,2017-09-22 15:41:16 UTC,Looking at the packages - will sponsor them if all looks good. Thanks!
1718922,2017-10-05 17:16:47 UTC,"Hello Balint, or anyone else affected,"
1718922,2017-10-05 17:19:46 UTC,"Hello Balint, or anyone else affected,"
1718922,2017-10-05 17:23:58 UTC,"Hello Balint, or anyone else affected,"
1718922,2017-11-06 08:37:56 UTC,"Testing of this version has been done with the new snapshot, marking as verification-done."
1718927,2020-12-01 02:44:44 UTC,See also bug 1888598 and bug 1745866
1718927,2020-04-05 06:54:20 UTC,"I have the same issue, but the solution from justxux worked fine. Thank you"
1718927,2020-03-17 07:07:09 UTC,This bug should remain unique to the original reporter. Everyone else please open a new bug.
1718927,2019-07-30 11:59:37 UTC,"OS: Ubuntu 18.04.2
DE: Gnome Shell 3.28.2
Kernel: 4.18.0-25-generic
Nvidia driver: 430.26
Audio: Headphones (Motherboard) + Speakers (HDMI)"
1718927,2019-07-23 14:10:29 UTC,Update: The HDMI audio device is missing even after  screen off (screensaver).
1718927,2020-12-03 09:13:26 UTC,A workaround that worked for me was `pulseaudio -k`; having to do this almost every time I need audio is a big PITA though.
1718927,2019-04-24 20:12:25 UTC,Update.  It is an intermittent problem for me.  It is working again.
1718927,2019-04-24 18:03:53 UTC,I am having the same problem with Ubuntu 18.04.02 with HDMI audio.  No sound on Resume and it can't be selected as a sound source after resume.  A reboot is the only fix.
1718927,2018-04-11 01:37:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718927,2018-04-11 01:36:39 UTC,I can confirm this also happens for me. A workaround is to change the video resolution to something else and then back to what it was. That will bring back the HDMI sound device too.
1718927,2017-09-26 23:05:47 UTC,"Hi Daniel,
I have Ubuntu Gnome 16.04.3. After resuming I can change device in settings
but it gives no result - still silence. The sound is only on the speakers.
The only way to restore sound in HDMI is to reboot.
But I am not pretty sure if the problem relates to pulse audio. I
reinstalled the system and did not install pulseaudio at all. Still the
same. After resuming there is no sound in HDMI.
Regards"
1718927,2017-09-25 19:56:11 UTC,"At a guess, your system is probably reverting back to the default audio device on resume."
1718927,2019-07-15 11:00:05 UTC,"For me, after suspend/resume the HDMI audio device is missing from Sound Settings and pavucontrol."
1718930,2017-09-28 09:58:33 UTC,"I created a cluster (not cluster template) like this:
$ openstack coe cluster create --cluster-template strigazi-kubernetes-v1.8.0-beta.1 --keypair strigazi-lxplus --name strigazi-kube-deleteme-v1.8.0-beta.1"
1718931,2019-10-25 09:30:03 UTC,"@Mathieu, the issue described here was fixed, it's probably best to open a new bug (& upstream as well if possible) with a full journal log and description of your issue"
1718931,2019-10-24 22:38:31 UTC,"Hi,"
1718931,2018-08-23 08:31:18 UTC,This bug was fixed in the package gnome-shell - 3.28.3-0ubuntu0.18.04.2
1718931,2018-08-23 08:21:18 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1718931,2018-08-21 11:25:59 UTC,"Fixed in gnome-shell 3.28.3-0ubuntu0.18.04.2, as per upstream verification there's no need to perform further tests."
1718931,2018-08-06 23:51:29 UTC,"Hello John, or anyone else affected,"
1718931,2018-07-24 23:56:37 UTC,Fixed in:
1718931,2018-07-19 11:55:54 UTC,The issue was one in the gnome-shell agent and has been fixed in 3.28.3
1718931,2018-03-02 03:25:59 UTC,"Filed an upstream bug, at long last, in the Gnome bugtracker at https://bugzilla.gnome.org/show_bug.cgi?id=793977"
1718931,2018-03-02 02:57:31 UTC,"Okay, so...why isn't this a priority bugfix? I love gnome, don't get me wrong, but when I can't even autoconnect to my VPN like I did countless times in the past few years running Ubuntu on Unity without compromising the security of my system something is wrong. There needs to be an option - and a working one at that - for auto-connecting to a VPN through the Gnome NetworkManager GUI. The KDE folks fixed this ages ago with KWallet, I suspect this involves the Gnome-Keyring. This is a *very* annoying problem. Should I report the bug on the Gnome bugtracker? So frustrating when this is an extremely common problem with nobody actually looking into *why* it's happening or how to fix it. I'm afraid this one is beyond me."
1718931,2018-01-02 14:47:49 UTC,@oddtore1 12.04 is deprecated; have you considered upgrading?
1718931,2017-11-03 20:19:57 UTC,Not working for me at all.
1718931,2017-10-22 02:01:38 UTC,"Literally just toggling that one option ""Store password for all users"" in the VPN settings fixes the problem entirely. Use ""sudo service network-manager restart"" and it connects flawlessly the first time. To avoid the error loop on bootup specifically, just uncheck the box ""Make available to other users"" on the primary connection."
1718931,2017-10-22 01:49:31 UTC,"Yeah, I keep getting the ""vpn-connection[...]: Failed to request VPN secrets #3: No agents were available for this request."" error message in my syslog. I found, however, that THIS worked for me: All you have to do is go Dash->VPN->VPN Settings->connection_name_here->Identity->Password->""Store for all users"" and bingo problem solved. If nm-connection-editor says that you can't save the connection (the save box is grayed out), then...just forget the network and set up the connection again (worked for me at least). Once you have checked said auto-connect box with nm-connection-editor and ensured that the VPN password is set to ""Store for all users,"" both the primary connection AND the VPN will start successfully at the same time. See my post at https://askubuntu.com/questions/967408/how-to-automatically-connect-to-vpn-in-ubuntu-17-10/967415#967415"
1718931,2017-10-19 21:48:56 UTC,"I'm facing the same problem. In auto-mode the VPN does not manage to connect, while manual connecting to the wifi enables automatic connection on the VPN."
1718931,2017-10-19 21:46:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718931,2018-07-09 00:51:31 UTC,"Well...it has been quite some time and this bug has received absolutely *zero* attention from the Gnome Shell Gitlab here https://gitlab.gnome.org/GNOME/gnome-shell/issues/123 escalated from the Gnome Bugzilla tracker after Gnome shell development moved to Gitlab. The issue is fully present in Ubuntu 18.04 AND in the newer version of the Gnome shell and NetworkManager in Fedora 28. Before v3.26.X, auto-connect worked fine through the NetworkManager in the Gnome environment. I'm afraid to report that months later, absolutely nothing has been done to address what should be a relatively high-priority bug in the Gnome Shell. If anyone has the capabilities to reach out farther than I already have, please do so. This critical bug has been sitting idle with no attention for months, and persists across newer versions of the Gnome shell, namely 3.28.X, seemingly independent of distribution."
1718931,2017-09-22 13:11:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1718932,2017-09-25 19:52:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1718932,2017-09-25 19:52:50 UTC,"Confirmed, but I think this was by design (chosen by upstream Gnome). We have not yet changed it, or decided to change it."
1718932,2017-12-29 12:10:16 UTC,Have same problem in Firefox dialogs.
1718932,2017-12-29 18:12:43 UTC,same libreOffice and other all apps.
1718932,2019-03-08 09:27:13 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1718935,2018-01-22 15:12:25 UTC,"I'm not sure why the patch in #4 was abandoned, but if someone else wants to pick this up I think we'd be happy to have all of the journald metadata filled in."
1718935,2017-11-13 11:15:22 UTC,"Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master
Review: https://review.openstack.org/507375"
1718935,2017-09-26 06:48:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507375"
1718935,2017-09-26 09:42:28 UTC,"There is extra info that one can set. And actually, oslo.log's handler already has code to set that information, it's just never filled into the record."
1718935,2017-09-22 17:52:28 UTC,"I'm not really familiar with journald. Are there fields built into its structure for that sort of info? Or should we add it to another field, like the message?"
1718936,2017-09-22 13:00:06 UTC,This change was made by a bot.
1718936,2018-04-24 09:27:07 UTC,I just tested upgrading to 18.04 and newest stable 4.15.0-19 does not boot with default parameters.
1718936,2018-02-16 22:42:05 UTC,Has anyone tested 4.15 stable to see if it has resolved the issues for XPS 15 9560?
1718936,2018-01-22 06:27:20 UTC,The fix is easy enough. here is what you need to do.
1718936,2018-01-22 02:20:06 UTC,Thanks -- keep up the good work. Any known workarounds? as I'd like to get this machine dual-booting.
1718936,2018-01-22 01:54:12 UTC,Just tested 4.15-rc8 and it boots but the system isn't stable. Gets lockups and screen flicker.
1718936,2017-12-27 18:37:12 UTC,I also cannot boot 17.10 live USB to be able to install it.
1718936,2017-12-09 15:03:11 UTC,Just received my brand new Dell 9560 and I also cannot boot a Live Image of 17.10 from USB. If I jump out of the splash screen (Alt+F1) I see these kinds of error messages come across:
1718936,2017-11-25 04:49:50 UTC,This issue appears to still be hanging on boot for Dell XPS 15 (9560).
1718936,2017-10-14 13:58:24 UTC,"It's easier to identify the regression on mainline kernel. You only need to from 4.13-rc1, and find which -rcN is the first one that regressed."
1718936,2017-10-14 13:45:18 UTC,I have done some more testing and here are my findings:
1718936,2017-10-13 07:31:05 UTC,"Please add kernel parameter ""drm.debug=0x0e"" and boot with the drm-tip kernel. Attach the dmesg here."
1718936,2017-09-30 19:55:53 UTC,"I tried it and it is the same problem as all the previous kernels I tested
(including the latest 4.13 available in Artful)"
1718936,2017-09-30 19:54:23 UTC,"I tried it and it is the same problem as all the previous kernels I tested
(including the latest 4.13 available in Artful)"
1718936,2017-09-28 07:21:27 UTC,Please try drm-tip kernel [1].
1718936,2018-01-23 00:20:15 UTC,link textThe soln to this is to turn the nouveau driver modesettings and leave things up to the Intel board.
1718936,2017-09-27 20:50:45 UTC,"I just tested the ""blacklist=nouveau modprobe.blacklist=nouveau"" and the ""nouveau.modeset=0"" separately and both of them the machine booted off the USB stick. I had a live image running 4.12 kernel so I will test today's images (with 4.13 kernel) and report back."
1718936,2017-09-22 16:00:15 UTC,I'm curious if it works if you just remove the splash line from the command line (press F6 when booting).
1718936,2017-09-22 17:06:34 UTC,"I removed the ""splash ---"" from the boot command option and still didn't boot up. I got more error messages so please attached photon."
1718936,2017-09-22 13:04:03 UTC,"Here is a photo of the errors I get when I boot off the live CD. This is the live CD from Sep 21, 2017"
1718936,2017-09-27 23:23:43 UTC,This bug shouldn't be fixed-released. Nothing got fixed. The live image doesn't boot without the nouveau modeset kernel boot option. It shouldn't be fixed until the live image boots without any tinkering.
1718936,2017-09-22 17:30:02 UTC,"Thanks for trying,  not so easy to debug on a live session. Lets see if we can reproduce it locally."
1718936,2017-09-25 15:01:40 UTC,I have the exact same laptop and have not been able to start 17.10 here in simple testing with daily images for months. I don't think I have been able to do so with any 17.10 image. I installed the 4.13.3 Kernel and on my 17.04 install on the computer and it started up and is running now as I type this. There were quite some errors when installing regards to missing firmware but it starts at least.
1718936,2017-09-25 18:18:49 UTC,"Can you see if this issue also happens with the latest daily image?  It can be downloaded from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/"
1718936,2017-09-22 17:28:14 UTC,"Probably a nouveau bug?
Add ""blacklist=nouveau modprobe.blacklist=nouveau"" to your kernel parameter."
1718936,2017-09-26 03:12:56 UTC,"Can you add this to your kernel parameters ""blacklist=nouveau modprobe.blacklist=nouveau"" and try again."
1718936,2017-09-26 15:56:54 UTC,"I just tried adding ""blacklist=nouveau modprobe.blacklist=nouveau"" but it will not boot."
1718936,2017-09-26 17:23:11 UTC,I did that with yesterday's Ubuntu 17.10 live image and it did boot.
1718936,2017-09-27 04:24:39 UTC,It's driven by intel graphics all the time. Nouveau is the part that has more chance to hang the system.
1718936,2017-09-27 13:26:34 UTC,"I was going to add that it should run on Intel by default. I updated the image to the latest on the USB and tried again and it still hangs even with the kernel parameters. ""blacklist=nouveau modprobe.blacklist=nouveau"" It worked for you Anmar?"
1718936,2017-09-27 15:35:42 UTC,Someone suggested noveau.modeset=0 however for me that does not boot for me either. The only setting that will is nomodeset as mentioned here in the first entry.
1718936,2017-09-25 23:08:42 UTC,"I just tried today's image and I it isn't booting still. Like Joseph, I tried"
1718947,2017-11-29 17:01:48 UTC,"Reviewed:  https://review.openstack.org/523874
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=c58b727bec3561d8d283497d784a3437185924dd
Submitter: Zuul
Branch:    stable/pike"
1718947,2017-11-29 13:39:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/523874"
1718947,2017-11-25 06:07:36 UTC,"Reviewed:  https://review.openstack.org/522811
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=6a2d14d3276bb4fe289ad2dd839ffe7b73f80794
Submitter: Zuul
Branch:    stable/pike"
1718947,2017-11-24 12:29:24 UTC,"Reviewed:  https://review.openstack.org/522513
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=336404c861dfde68ab15a3f66fce714ee4f12291
Submitter: Zuul
Branch:    master"
1718947,2017-11-24 11:35:47 UTC,"Unable to register node ""rally-cddc-41GE-5jefaj3mozvx-minion-0"" with API server: Node ""rally-cddc-41GE-5jefaj3mozvx-minion-0"" is invalid: metadata.name: Invalid value: ""rally-cddc-41GE-5jefaj3mozvx-minion-0"": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')"
1718947,2017-11-23 10:18:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522513"
1718947,2017-11-02 16:35:48 UTC,"Reviewed:  https://review.openstack.org/511219
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=283c0931879acc876c7f053f561efc383b7a0da1
Submitter: Zuul
Branch:    master"
1718947,2017-10-11 12:34:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511219"
1718947,2017-09-25 06:40:06 UTC,We can remove the `<master-or-node>-<index>` part and keep only the <cluster-name>-<short-id> part here in all templates.
1718947,2017-09-22 14:11:08 UTC,"change needs to go here:
http://git.openstack.org/cgit/openstack/magnum/tree/magnum/drivers/heat/driver.py#n113"
1718947,2017-11-23 10:19:25 UTC,"Openstack (kubernetes) Cloud Provider does not accept a stack name with upper case letters, so we're transforming the generated stack name to all lower case."
1718958,2017-09-22 15:39:06 UTC,"Could you provide a link to an example kernel snap built on LP to help us track this down?  (i.e. the +snap page on launchpad.net itself, not just the build log)"
1718958,2017-09-22 16:13:04 UTC,https://launchpad.net/~p-pisati/+snap/pc-kernel/+build/83319
1719002,2017-09-26 16:16:14 UTC,"Daniel,"
1719002,2019-08-05 03:50:34 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1719002,2017-09-26 15:59:03 UTC,I'm told that the *dm tells plymouth (the boot progress screen) to stop. So that's probably what the flicker is related to.
1719002,2017-09-25 21:28:45 UTC,This bug can be marked as invalid. Installing lightdm seemed to have solved the problem.
1719002,2017-09-26 13:55:48 UTC,Can you please take a video or photo of the problem?
1719002,2017-09-25 22:21:09 UTC,This bug can be marked as invalid. Installing lightdm seemed to have solved the problem.
1719002,2017-09-25 19:50:28 UTC,"Can you clarify what you mean in ""flickerty with verbos page script""? Does that mean a VT is visible for a while (black background)?"
1719002,2017-09-26 15:07:02 UTC,"If you watch the top,left hand corner you will see one flash and then the cursor blinking between plymouth and gdm. Sometimes there is no flickerty. Sometimes there is full screen flickerty sometimes only cursor. In this video you will see one small flash of verbose code in top left , then cursor flash about 7 times."
1719005,2018-02-09 20:32:02 UTC,SubDownloader is forked at https://github.com/subdownloader/subdownloader
1719006,2017-09-22 20:00:38 UTC,this was copied from our etherpad
1719038,2019-01-22 12:14:17 UTC,"Hello, Christian.
This issue is only reproducible with KDE in the guest. Just like that."
1719038,2019-01-22 08:17:27 UTC,"Hi Gannet,
the discussion of RussianNeuroMancer with upstream ended trying to tackle the KDE resolution setting [1], but not a change in qemu/libvirt or other components of the virst-stack. Also it was reported that newer versions were less (or not)9 affected."
1719038,2019-01-21 08:29:43 UTC,"The issue still in 18.10 host and 18.04 VM. Please, look the attachment above."
1719038,2018-06-14 12:33:29 UTC,">  Is this still an issue for 16.04
"
1719038,2018-06-12 17:50:43 UTC,"Upstream bug https://gitlab.freedesktop.org/spice/spice-gtk/issues/66 was closed, but if I understood it correctly, only for 18.04. Is this still an issue for 16.04, and does the patch from comment #5 help there?"
1719038,2018-06-05 19:03:23 UTC,Moved from freedesktop to GitLab: https://gitlab.freedesktop.org/spice/spice-gtk/issues/66
1719038,2018-06-05 14:20:22 UTC,-- GitLab Migration Automatic Message --
1719038,2018-03-15 21:45:43 UTC,"> [0] https://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/commit/
I found this patch works only when qemu-guest-agent in not added to the VM, otherwise crash happens all the times while login. It shows the window which informs that ksmserver is crashed and if to click ""okay"", it quits to sddm login screen.
"
1719038,2018-03-15 21:41:32 UTC,"Also I found the previous patch works only when qemu-guest-agent in not added to the VM, otherwise crash happens all the times while to login. It show window which informs that ksmserver is crashed and if to click ""okay"", it quits to sddm login screen."
1719038,2018-03-05 14:05:12 UTC,Here is a patch which fixes the issue: https://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/commit/?id=ee8f904ab0d590c741e640e9548c472e6a58b3cc
1719038,2018-03-02 11:53:17 UTC,"(In reply to Victor Toso from comment #4)

> Have you filed the bug with (K)ubuntu? It would be good to know if they have
> patched with [0] as this was to solve bug with similar issue [1]
>
> [0] https://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/commit/
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1428340
"
1719038,2018-03-02 08:31:52 UTC,Have you filed the bug with (K)ubuntu? It would be good to know if they have patched with [0] as this was to solve bug with similar issue [1]
1719038,2018-03-01 20:42:49 UTC,"Created attachment 137737
Xorg log file with backtrace from Kubuntu 18.04 (development branch)"
1719038,2018-01-12 11:27:26 UTC,Any updates?
1719038,2018-01-12 11:26:20 UTC,Any updates?
1719038,2017-09-24 16:31:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719038,2017-09-05 22:28:03 UTC,"Created attachment 133982
Xorg log from Kubuntu 17.10"
1719038,2017-09-05 22:22:40 UTC,"Created attachment 133981
Xorg log file"
1719043,2017-11-16 18:50:11 UTC,This bug was fixed in the package mutter - 3.26.2-0ubuntu0.1
1719043,2017-11-16 18:40:12 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1719043,2017-11-07 18:56:11 UTC,I verify that the address bar works correctly now after upgrading Ubuntu 17.10 to mutter 3.26.2-0ubuntu0.1.
1719043,2017-11-07 15:58:33 UTC,"Hello Andrew, or anyone else affected,"
1719043,2017-11-04 18:18:12 UTC,"I verify that the totem regression cannot be reproduced with the new gtk+3.0 3.22.25-0ubuntu0.1 SRU. Since this bug is being fixed in mutter instead, I am closing the gtk+3.0 part of this bug."
1719043,2017-10-19 14:09:08 UTC,"Hello Andrew, or anyone else affected,"
1719043,2017-10-19 22:35:41 UTC,A regression was identified. See comments 15-16 at https://bugzilla.gnome.org/784314 which can be reproduced with
1719043,2017-09-30 20:02:43 UTC,This bug was fixed in the package epiphany-browser - 3.26.1-1ubuntu1
1719043,2017-09-26 12:45:06 UTC,"Sorry, the new version doesn't actually appear to solve the problem."
1719043,2017-09-26 12:38:09 UTC,This bug was fixed in the package epiphany-browser - 3.26.0-1ubuntu2
1719043,2017-10-26 08:49:02 UTC,This bug was fixed in the package gtk+3.0 - 3.22.24-0ubuntu2
1719045,2017-09-29 18:06:30 UTC,The test kernel seems to be pretty good so far.
1719045,2017-09-29 19:14:16 UTC,"Thanks for all the testing, Josh. I reverted the paravirtualized TLB flushing patches in the test kernel. Do you think we should spin a new kernel without it while we try to find the main cause of the problem?"
1719045,2017-09-29 19:50:06 UTC,"Josh, is there any documentation available for the Hyper-V hypercalls?"
1719045,2017-09-29 20:02:20 UTC,"Yes, let's spin one into proposed with KVM enabled and these patches reverted for SRU."
1719045,2017-09-29 20:03:34 UTC,You may also not be surprised to see this in a run I did with upstream 4.14-rc2:
1719045,2017-09-29 20:48:12 UTC,"@mhcerri: I believe the hypercalls are documented in ""Hypervisor Top Level Functional Specification v5.0b.pdf"" (https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/tlfs)."
1719045,2017-10-02 14:26:10 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-October/087336.html
1719045,2017-10-02 14:46:29 UTC,Including the rationale to the commit messages:
1719045,2017-10-03 12:41:35 UTC,linux-azure 4.11.0.1013.13 (with the reverted changes) just landed in -proposed. Can you please confirm the issue does not happen with this version?
1719045,2017-10-03 02:02:53 UTC,The kernel with the reverted changes is already in the pipeline to be published to the archive. So we can test this fix at a normal pace.
1719045,2017-10-03 14:02:22 UTC,"Yes, I've already kicked off the call for testing with the local teams and people experiencing the issue."
1719045,2017-10-03 16:27:41 UTC,Early results from @Chris
1719045,2017-09-29 15:48:51 UTC,"Also, the problem only happens when using HVCALL_FLUSH_VIRTUAL_ADDRESS_SPACE_EX/LIST_EX hypercalls."
1719045,2017-10-05 20:25:47 UTC,"Later results also look good. IB, BVT, Deployment, Perf, GPU, LTP, kdump, Docker, and Telegraf tests all passed. Please publish to updates."
1719045,2017-10-09 19:49:15 UTC,This bug was fixed in the package linux-azure - 4.11.0-1013.13
1719045,2017-10-17 11:41:35 UTC,"@jrp, should we include the following upstream fixes into the azure kernel?"
1719045,2017-10-17 23:05:24 UTC,"@mhcerri Yes, we should queue these up, but we'd like to switch our focus to 4.13 soon."
1719045,2017-10-03 02:00:11 UTC,"Thanks, Dexuan."
1719045,2017-09-29 13:07:48 UTC,Mainline doesn't cause docker to fail. I will start to check if linux-azure has some issue in TBL or in the helpers for hyper-v hypercalls.
1719045,2017-09-25 23:43:10 UTC,"BTW, issue #2 in the last comment doesn't always happen either. Sometimes a retry would succeed."
1719045,2017-09-28 18:35:31 UTC,We will check out the kernel as soon as possible. Thanks!
1719045,2017-09-28 19:37:57 UTC,Backporting the changes from upstream causes the problem to happen. I'm building the mainline kernel to test it.
1719045,2017-09-23 00:23:37 UTC,https://github.com/golang/go/blob/964639cc338db650ccadeafb7424bc8ebb2c0f6c/src/runtime/mem_linux.go has the message around the line 138:
1719045,2017-09-23 00:25:19 UTC,https://golang.org/src/runtime/mgcwork.go around line 306
1719045,2017-09-23 00:32:04 UTC,"Trying to build the go tests... and I am having trouble building it:
$ GOOS=linux GOARCH=amd64 ./bootstrap.bash
#### Copying to ../../go-linux-amd64-bootstrap"
1719045,2017-09-26 00:37:49 UTC,I'm also getting a report that if everything is recompiled with golang-1.9 this does not reproduce.
1719045,2017-09-26 01:29:39 UTC,"If I install golang-1.4 and golang-1.9 and remove golang-1.6 I can build go from source (1.4 is needed for the bootstrapping) and everything runs without error. If I have golang-1.6 installed, I get segfaults."
1719045,2017-09-26 21:33:47 UTC,"Does it happen in some specific instance? I restarted docker more than 50 times without any problem in a Standard DS15 v2 instance (20 vcpus, 140 GB memory) with the linux-azure kernel."
1719045,2017-09-27 01:42:46 UTC,"I got the issue (comment #4) with Standard_D16_v3 (16 vcpus, 64GB memory)."
1719045,2017-09-27 05:03:03 UTC,I easily (~25% docker installation fails) reproduce the issue on NC6 (gpu) vm.
1719045,2017-09-25 23:38:07 UTC,Let me add 2 more symptoms:
1719045,2017-09-27 15:03:35 UTC,"I would test with SR-IOV as well, I'm wondering if this is related to PCI passthrough."
1719045,2017-09-27 16:22:38 UTC,"I was able to reproduce it on a Standard_D16_v3 instance when I create some containers that are configured to restart with dockerd. It doesn't happen very often though, and sometimes I can't reproduce it for some time. I will try to test it on a GPU-based instance."
1719045,2017-09-28 00:53:00 UTC,I'm seeing this pretty often on Standard_D2s_v3 instances. About 1/3 of my new vm instances are failing. Please let me know if I can provide logs or testing.
1719045,2017-09-28 09:30:51 UTC,On all my azure machines using Standard_DS2_v2 - North Europe telegraf crashed with that error. I'm not using docker.
1719045,2017-09-27 15:02:41 UTC,It certainly seems to happen much more easily on GPU-based instances.
1719045,2017-09-28 15:49:07 UTC,The 4.11 base kernel for linux-azure doesn't show the problem and the same is true for linux-azure-edge (linux-azure-edge causes the failure while it's 4.13 base kernel doesn't).
1719045,2017-09-28 16:09:20 UTC,It's interesting that telegraf is also made with golang.
1719045,2017-09-28 16:33:27 UTC,Yes. Probably something in golang runtime is triggering the bug.
1719045,2017-09-28 18:07:47 UTC,Reverting the following commits seems to avoid the problem:
1719046,2017-09-23 00:22:31 UTC,Added solution to personal repo:
1719053,2017-09-23 12:00:28 UTC,"I personally tested the guided - use entire disk and set up encrypted LVM option, but I know that is not exactly your bug report."
1719053,2017-09-25 05:36:48 UTC,"After a number of experiments this weekend, I can say that the graphical installer is not COMPLETELY broken, It merely contains a fatal flaw."
1719056,2017-09-23 03:21:23 UTC,"In case it matters, affected system is an ASUS notebook with the following specs:"
1719060,2017-09-23 05:56:42 UTC,"StacktraceTop:
 _IO_vfprintf_internal (s=s@entry=0x7ffff55e0300, format=<optimized out>, format@entry=0x5620d7a6d788 ""Don't know how to handle \342\200\230%s\342\200\231"", ap=ap@entry=0x7ffff55e0470) at vfprintf.c:1643
 __GI___vasprintf_chk (result_ptr=result_ptr@entry=0x7ffff55e0450, flags=flags@entry=1, format=0x5620d7a6d788 ""Don't know how to handle \342\200\230%s\342\200\231"", format@entry=0x7ffff55e0450 """", args=0x7ffff55e0470) at vasprintf_chk.c:66
 vasprintf (__ap=<optimized out>, __fmt=<optimized out>, __ptr=0x7ffff55e0450) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:210
 g_vasprintf (string=string@entry=0x7ffff55e0450, format=<optimized out>, args=args@entry=0x7ffff55e0470) at ../../../../glib/gprintf.c:316
 g_strdup_vprintf (format=<optimized out>, args=args@entry=0x7ffff55e0470) at ../../../../glib/gstrfuncs.c:514"
1719060,2018-03-09 08:13:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719062,2017-09-24 06:19:16 UTC,"To clarify, having dig request it from systemd-resolved works.  Having dig request it directly from the server also works."
1719062,2017-09-23 22:40:59 UTC,The systemd version you have installed appears to be quite out of date. Could you please upgrade to 234-2ubuntu10?
1719062,2017-09-24 06:16:27 UTC,"I have upgraded to version 234-2ubuntu10.  It doesn't make a difference.  I double checked and requested the key (cert record) using dig and it works just fine, no malformed packet.  It's only when gpg2 requests it combined with systemd-resolved where there is a problem as far as I can tell."
1719077,2017-09-23 14:08:02 UTC,"It's possible this is a totem or gst bug. What I currently see -
1. The app-install-data warning is longstanding, bug here
  https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1716137
2. At least here 'easy-codec-install' works fine on supported local files
3. A text/html decoder missing usually refers to unsupported or unknown type
4. If one was to install gst libav, bad & ugly plugins the Guardian vids still won't work, same error about text/html"
1719077,2017-09-23 14:11:44 UTC,"Indeed, I can reproduce this. This issue affects Debian as well, and I wonder why nobody noticed it so far.
I have an idea on how to fix it."
1719077,2017-09-23 15:10:27 UTC,"Just tried latest image updated.
See no issue with local files that gst supports
As far as channels the guardian one is broken, apple trailers is ok"
1719077,2017-09-23 17:34:21 UTC,"As far as guardian videos this bug doesn't seem to have ever been fixed, if that's true it should be removed from grilo or grilo-plugins
https://bugzilla.gnome.org/show_bug.cgi?id=771215"
1719077,2017-09-24 18:13:18 UTC,"I fixed the bug mentioned in this report (the error message should be gone now and you should be able to search for mimetypes with PackageKit again).
However, it could be possible that the error described here was masking another issue with missing codecs itself (I can't test that at time)."
1719077,2017-09-25 02:08:43 UTC,"I'm not sure if this is a dupe, this bug should be only about the non working grilo plugin for guardian videos. Can't see how fixing the erroneous error message is going to change that."
1719077,2017-09-25 02:19:06 UTC,"Using as example the 1st vid shown in that channel -
quvi dump  https://www.theguardian.com/football/video/2016/sep/26/is-leicester-ready-for-the-champions-league-video
error: libquvi: while parsing media properties: /usr/share/libquvi-scripts/0.9/media/guardian.lua:91: attempt to perform arithmetic on a nil value"
1719077,2017-09-25 05:32:16 UTC,"There are two bugs here:
1. packagekit was using app-install-data to search for missing codecs
2. The Guardian Videos channel does not work"
1719077,2017-09-25 20:17:59 UTC,This bug was fixed in the package packagekit - 1.1.7-1
1719079,2017-09-24 20:26:11 UTC,Merged in https://gitlab.com/inkscape/inkscape/commit/f81751abb770d0367d6c515cdcb56a7954714eab
1719085,2018-01-24 22:27:39 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-738
1719088,2020-09-20 09:47:13 UTC,Closing because INVALID: Can't replicate.
1719089,2017-09-24 06:37:35 UTC,now gimp is 'disappeared'
1719089,2017-09-24 09:00:36 UTC,... but can be started from terminal
1719089,2020-05-18 13:54:24 UTC,Old problem about Ubuntu 17.10. Changed status to invalid.
1719099,2017-09-23 15:07:20 UTC,????
1719102,2017-11-01 16:57:50 UTC,Related: https://bugs.launchpad.net/diskimage-builder/+bug/1698551
1719102,2017-12-06 22:33:55 UTC,"I ran into this issue when following the directions for building a fedora-atomic image for Magnum. I didn't exhaustively check every version after 2.3.3, but I found that to be the last version that worked."
1719102,2017-12-06 23:52:49 UTC,I think this is related to https://bugs.launchpad.net/magnum/+bug/1699735
1719102,2017-09-23 16:06:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/506865"
1719106,2017-09-30 08:53:17 UTC,"This bug appears only with ""GNOME Classic"" session."
1719106,2017-09-30 15:51:20 UTC,Forgot to include affected gnome-shell-extensions package version:
1719106,2017-10-13 12:45:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719106,2017-12-31 18:00:28 UTC,I am also affected by this bug. Example of issue in notifications window:
1719106,2018-02-02 16:02:59 UTC,"Any news?
Also suffering from this issue. Although I haven't spent too much time (yet) poking around with settings, changing the theme didn't seem to make any improvements on the notifications colors."
1719106,2018-02-11 10:52:56 UTC,Same issue here. Is there any workaround?
1719108,2017-10-06 19:13:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719108,2017-10-09 17:35:06 UTC,"This behaviour of Chromium-based browsers is in fact standard compliant while Firefox’ isn’t: images without colour profile are supposed to be assumed to be in sRGB colour space which is converted to screen colour space which may end up looking less saturated. This is in fact a ""bug"" in the web sites and images in question and/or the colour profile setting of your display device."
1719108,2017-10-11 20:09:34 UTC,"@David F. Well, my screen is in sRGB (it's a Dell UltraSharp 4k display with 100% sRGB coverage. Also, the Chromium incognito mode has a weird issue related to the color difference, shown in the newly attached screenshot. This also was not an issue until upgrading to the latest Chromium."
1719108,2017-10-11 20:20:45 UTC,"Ironically, on my workstation where I am seeing this issue, chromium in a VM running 16.04 does not have this same issue."
1719110,2017-09-23 17:50:20 UTC,"Sorry, Raspberry Pi 3:
$ uname -a
Linux rpi3 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l armv7l armv7l GNU/Linux"
1719110,2017-09-25 14:54:54 UTC,"apt-get upgrade reported that gdb was up to date.  However, removing and re-installing gdb with apt-get got it working again."
1719122,2017-09-23 20:07:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719128,2019-07-25 01:39:56 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1719128,2018-01-20 22:11:39 UTC,Setting WaylandEnabled=false in the daemon secton of /etc/gdm3/custom.conf is a workaround.
1719128,2017-12-05 05:48:22 UTC,"This bug is effecting all users that have NVidia proprietary drivers installed (everyone using CUDA).
this should be given priority."
1719128,2017-10-28 12:04:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719128,2017-12-20 22:10:11 UTC,Confirmed this is affecting my system. Ubuntu 17.10 with proprietary Nvidia drivers. GDM3 cannot seem to auto-select non-wayland session or something. All options attempted in /etc/gdm3/custom.conf do not work.
1719128,2017-09-26 13:54:10 UTC,Actually modeset=1 is what you would use for a Wayland session...
1719128,2017-09-26 13:41:00 UTC,AFAIK this is not a bug :(
1719128,2017-09-25 21:59:35 UTC,"It may be related, error from journalctl:"
1719128,2017-09-25 19:20:09 UTC,Have you enabled Wayland support by modifying your kernel command line?
1719128,2017-09-26 15:54:05 UTC,"Ok: I use default kernel (log above) and ""default"" (from PPA) binary drivers (384.90) and I'm on Xorg (default modeset=0) and here autologin doesn't work. If Nvidia supports Xorg by default why then it doesn't work?
I've made test with wayland just out of curiosity, changed to modeset=1, rebuild initramfs, reboot logged in run nautilus and then *reverted* changes. And I've noted it here because I though it might be somehow related (I usually do this to help devs). I'm not trying to run Xorg on drivers set to wayland.
So:
- I'm on default setup and autologin doesn't work
- autologin switch gets reset after setting it to enabled and restart session
- wayland session was only test because I wanted to check it out
- autologin works when I'm on virtualbox with Xorg
- autologin options are enabled in custom.conf (gdm3)"
1719128,2017-09-25 21:42:30 UTC,"From today:
BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=4f723467-a8f6-4798-8ddd-8e69490c4bd5 ro quiet splash vt.handoff=7"
1719135,2019-11-28 10:34:47 UTC,"Hi Kai,
I came by this accidentally and searched the internet a bit."
1719141,2017-09-24 02:59:52 UTC,"This could be tied in with the notifications framework without having a remote call out to the process that kicks off the Ansible task.  That said, the Ansible playbook should be async so the Keystone process can continue and can return a value to the end user prior to the end of the playbook."
1719141,2017-09-24 14:58:44 UTC,"Since ansible does not have a listening architecture, the flow would have to start with spinning up worker process to listen to notifications.  That process could be on a separate machine from the Keystone server."
1719141,2017-10-10 19:59:40 UTC,"This sounds partially related to the shadow mapping work, or auto-provisioning [0], which seems to address the first example in the description. What would be a more specific example of the second case with LDAP?"
1719141,2017-10-14 01:46:48 UTC,"The only problem with saying it is pure notifications is that it requires an active process to kick it off.  In cases where there is no full workflow engine, the users will not have the ability to manage these tasks.  Having something in-process with Keystone but triggered from a notification would be a middle ground."
1719141,2018-06-20 15:01:36 UTC,"I think the notification route makes the approach more generic, instead of something in-process with keystone that might end up specific to a certain tooling (e.g. Ansible)."
1719143,2020-06-10 10:50:56 UTC,"NOK: 20.04, i1Display3:
gnome-control-c[22782]: calibration failed with code 1: no sensor->get_sample"
1719143,2020-05-28 12:23:08 UTC,"This happened to me just now on a fresh installation of 20.04. Exactly as reported - first attempt at calibration with a Spyder 3 fails, on the second attempt gnome-control-center crashes hard."
1719143,2017-09-25 18:20:34 UTC,"Thanks for your report. I confirm this error.
On second try gnome-control-center crashes."
1719143,2020-06-03 20:47:52 UTC,"@Carl-Eric, can you trigger it again? Could you add a 'journalctl -b 0' log from a session where you had the issue?"
1719149,2019-03-28 10:06:28 UTC,Is this still a bug? If yes - please update.
1719149,2019-05-28 04:17:21 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1719149,2020-03-17 10:44:25 UTC,With kolla-ansible stable/rocky I can confirm this bug still exists.
1719149,2020-03-17 17:31:07 UTC,Could you describe the issue in more detail? Does it mean tgtd restart kills all iSCSI targets? Something else? How to reproduce? Does the workaround above help?
1719149,2020-05-17 04:17:39 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1719169,2021-02-23 18:13:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719169,2021-02-23 18:14:51 UTC,This problem still exists on Ubuntu 18.04.5 LTS. All packages are up-to-date.
1719169,2019-06-20 15:08:59 UTC,"Ran into the same problem in a freshly installed 18.04.2, hplip 3.17.10.
Solution mentioned at #1 worked for me...
Thanks Anatoly!"
1719169,2018-09-11 17:49:57 UTC,"This comman will reinstall /etc/hp/hplip.conf:
sudo apt-get install --reinstall -o Dpkg::Options::=""--force-confmiss"" libsane-hpaio"
1719169,2020-09-29 15:52:37 UTC,Ubuntu 20.04.1 up to date on 29/9/2020 with kernel 5.4.0-48-generic
1719174,2017-09-24 10:58:21 UTC,"I add ""print(cand.record)"" before line 261 of ""debtags"" and get the offending record?"
1719174,2017-09-24 11:22:37 UTC,"Good, now how did the typo get there? It is not in the control files of the package as available online! The package is not even installed on this system here. It is also not in http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages.gz"
1719176,2017-10-15 02:11:38 UTC,Additional tests and results:
1719183,2017-09-25 03:24:02 UTC,What branch is this test failure seen.
1719183,2017-10-16 20:32:26 UTC,Moving to incomplete; please specify which branch the failure is from.
1719183,2017-10-17 07:31:44 UTC,Master branch on Pike (version 12)
1719184,2018-10-20 07:20:54 UTC,"Hello,"
1719184,2019-02-07 14:13:35 UTC,"Ok, I've just added a new merge proposal for this bug which adds category management feature inside the same screen."
1719184,2018-10-20 08:59:51 UTC,"Hi Adrien,"
1719184,2018-10-02 20:20:10 UTC,"Hello,"
1719184,2018-09-12 14:54:29 UTC,"Hello,"
1719184,2018-09-24 15:32:59 UTC,"Hello,"
1719184,2018-09-16 18:45:19 UTC,It sounds like this would perfectly match my wish :)
1719184,2018-09-16 16:26:47 UTC,"Ok, while I was making this proof of concept, I've thought about such a screen with editing capability."
1719184,2018-09-16 15:19:59 UTC,"I think the wish was for input, and not for report."
1719184,2018-09-25 20:42:09 UTC,"Since I've written my comment above, I've thought it will be better to have the 3 views editable (and so every one with all columns)."
1719185,2017-12-30 02:32:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719191,2018-04-23 04:55:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719191,2020-05-18 13:55:12 UTC,Old problem about Ubuntu 17.10. Changed status to invalid.
1719191,2018-05-01 00:03:19 UTC,"I'm experiencing this on ubuntu-18.04-live-server-amd64.iso, trying to install to FreeBSD's bhyve virtualmachine. Host system is FreeNAS-11.1-U4"
1719191,2018-04-23 05:07:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1719191,2018-04-23 04:56:39 UTC,"Unfortunately I can confirm this issue on 18.04 Bionic Daily too. amd64 UEFI install on Dell E6410 laptop, alongside Windows 7."
1719191,2017-11-08 12:27:13 UTC,"Problem disappeared installing Ubuntu 18.04 LTS ""Bionic Beaver"" - Alpha amd64 (20171108)"
1719191,2017-09-26 10:54:03 UTC,may be related to https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939
1719191,2017-10-12 18:48:29 UTC,"still same problem installing Ubuntu 17.10 ""Artful Aardvark"" - Beta amd64 (20171011)"
1719191,2017-10-12 15:44:17 UTC,"it seems a common problem also if nobody sign up on my bug.
https://ubuntuforums.org/showthread.php?t=2374046"
1719191,2017-10-06 09:45:57 UTC,At end install of recent daily (0926 and 0930) I have the following messages and then ... nothing more. After hardware power-off and restart the system works fine.
1719191,2017-09-25 06:54:25 UTC,"I have no idea about the package, the problem occurs at end of installation, system is not yet started. I see only a black screen as from attachment. May you suggest where i can look? thanks."
1719191,2017-09-24 16:36:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1719191,2017-10-13 21:24:08 UTC,"This *could* be another variation of this bug, in any event it's well known that the odds of successfully exiting a live session with gdm3 are slim to none. Also noted that the below won't be fixed in 17.10.
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939"
1719194,2017-09-29 07:10:47 UTC,Maybe it related to this issue. But auto search won't search if i have active download queue. If I manual run search from auto search window date in last search field not changed. If download queue is empty auto search work and date in last search field changed on manual run.
1719194,2018-10-29 15:37:21 UTC,"I added 8 bundles from main and all 8 bundles was added in to auto search. It started to search from ep 01 to 08 but i noticed that ep 07 didn't get in to the download queue. If i did a manual search from auto search i could see it ""collecting result"" but nothing was added to the queue. I did a foreground search and there i could see there was hits.
I then removed it from the auto search and added the bundle from search and now it was added in to queue.
So here is something that make it fail. I have no clue what it is. Probably a bug in the code..."
1719196,2017-10-19 06:24:14 UTC,"Since the fix mentioned in the previous comments is already in upstream QEMU, I'm setting the upstream status to ""Fix released""."
1719196,2017-10-19 19:03:06 UTC,I've tested with the packages from the ppa:
1719196,2017-10-19 19:08:14 UTC,will test these and report back shortly.
1719196,2017-10-19 23:49:30 UTC,"I've testing with the same packages listed in comment #28,  Confirmed that this now works.."
1719196,2017-10-20 05:09:31 UTC,"Ok, driving that into an SRU then - thanks for verifying."
1719196,2017-10-20 11:47:35 UTC,"Regression tests on the ppa are good as well, we need to double check the auto-run on proposed then to ensure this doesn't behave differently on other arches.
I cleaned up the changelog and UCA backport noise and made a proper SRU for zesty."
1719196,2017-10-26 19:49:50 UTC,I accepted this but Launchpad timed out when the SRU testing comment was being added.
1719196,2017-10-31 18:05:56 UTC,"Hello Sean, or anyone else affected,"
1719196,2017-10-27 09:48:43 UTC,"As assumed s390x passed now (so a flaky test), and as outlined before armhf we just have to give up.
Looking at the history an override might be the right thing to do."
1719196,2017-10-27 11:23:58 UTC,"Ok, Zesty actually had an override for the arm test (had to learn the placement of those for SRUs).
So only up to the verification now."
1719196,2017-10-31 22:43:42 UTC,Thanks Christian - I've now verified this. I took a stepwise approach:
1719196,2017-11-02 22:16:32 UTC,This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.7
1719196,2017-11-02 22:16:40 UTC,"The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1719196,2017-12-11 15:33:52 UTC,Regression testing has passed successfully.
1719196,2017-10-19 05:48:40 UTC,Since we wait for the zesty verification I'm setting the status to incomplete for now.
1719196,2017-10-27 06:13:10 UTC,"Thanks for the FYI Brian.
I see it in pending-SRUs as it should be.
I added the -needed tags to be ""correct""."
1719196,2017-10-19 05:48:20 UTC,"Yeah, the offending patch in RH-BZ 1422413 appeared in qemu 2.8.
So it would make sense to work with newtwon (2.6.1), and pike (2.10), but fail on Ocata (2.8)."
1719196,2017-10-04 00:50:42 UTC,"Today I ran some tests and installed a Newton Deployment on arm64, which we already know works.  I upgraded QEMU and Libvirt on one of the hypervisors from the xenial-updates/ocata cloud-archive."
1719196,2017-10-18 14:24:32 UTC,"To further reinforce what Christian said, the Newton cloud-archive also uses virtio-mmio for its address type.  (See my comment#15)"
1719196,2017-09-28 14:29:30 UTC,Running tcpdump on the guests tap device shows the dhcp request leaving and the reply coming back.
1719196,2017-09-29 17:47:17 UTC,"This may be qemu related, rather than libvirt - further investigation required - but unlikely to be a problem with neutron-gateway charm"
1719196,2017-09-29 17:49:10 UTC,I have confirmed this bug with another arm64 + ocata deployment.
1719196,2017-09-29 17:50:15 UTC,Further summary:
1719196,2017-10-02 13:41:39 UTC,"I was also able to reproduce this again on Cavium ThunderX hardware,"
1719196,2017-10-02 13:56:39 UTC,"Just to further add to comment #6, That this is not a neutron issue,  Here is the tcpdump output of the guests tap device shows the dhcp request leaving and the reply coming back. For anyways that may be curious."
1719196,2017-10-18 14:44:08 UTC,This appears to be:  https://bugzilla.redhat.com/show_bug.cgi?id=1422413
1719196,2017-10-04 00:54:20 UTC,Taken from the upgraded hypervisor
1719196,2017-09-24 15:33:54 UTC,"juju status
bundle file
vm console output
and nova service list"
1719196,2017-10-05 22:19:12 UTC,Thanks so much for doing that Sean.
1719196,2017-10-11 11:17:42 UTC,"Hi,
I was reading into this after being back from PTO (actually back next monday).
I was wondering as I tested (without openstack) just that last week with Dannf on the Rally).
And indeed it seems to work for me on Artful (which as we all know is =Ocata in terms of SW stack)."
1719196,2017-10-11 11:18:58 UTC,"Note - be careful if you mean upstream qemu/libvirt (as the bug was filed) or the packages in Ubuntu (I added tasks for these).
I try to spot both, but will be more on-track for the latter."
1719196,2017-10-11 21:30:37 UTC,"I spent some time today trying to modify the ocata xml templates produced in /etc/libvirt/qemu/<INSTANCE-ID>.xml for each of the generated instances.  Destroying & Undefining the existing instance, making some changes and redefining the xml, however it appears that nova regenerates these templates upon instance reset, thus removing any changes made to the xml template. Is there any way to disable this feature that does not require some serious modifications to the nova underpinnings?"
1719196,2017-10-17 22:45:24 UTC,The problem is with virtio-mmio.
1719196,2017-10-18 08:18:01 UTC,"So,
libvirt knew about some change and picks the right default if you do not specify it.
But if you (Openstack in this case) specify virtio-mmio as type, then it fails - is that correct?"
1719196,2017-10-18 14:23:55 UTC,"Hi,
@admcleod as discussed on IRC I realized Ocata maps to Zesty so that is qemu 2.8.
Therefore the referred patch is released in Artful, but not in Zesty."
1719196,2017-10-05 01:46:24 UTC,"I was able to gather libvirt XMLs from both Newton and Ocata Instances, see attached"
1719197,2018-05-14 11:04:04 UTC,This change was made by a bot.
1719202,2018-04-05 08:56:30 UTC,This bug is duplicate of https://bugs.launchpad.net/hplip/+bug/1748598
1719202,2018-04-05 08:53:42 UTC,"To be more precise, the OS is Debian 9.3, not 9.0 or 9.1"
1719202,2017-11-21 05:20:52 UTC,"Hi,"
1719202,2018-04-05 08:46:02 UTC,"hplip 3.17.11 and 3.18.3 do not work with Debian 9 AGAIN. What the fuck is wrong with you people?
hplip 3.17.10 works..."
1719202,2017-10-06 18:19:53 UTC,"I've found this related question: https://answers.launchpad.net/hplip/+question/452076.
it seems that the main problem is that the installer points at two ""obsolete"" packages, pyqt4-dbus and pyqt4, that know are called python-qt4-dbus and python-qt4. the solution cited in the link is to rewrite the code so the new version works. Accordingly to the author of the solution, this was working fine with debian 8.8. I don't know if it's still valid for 9.1 (i've tried to, but every time I try to run hplip-3.17.9.run it rewrite every file...)."
1719202,2018-04-05 08:47:36 UTC,"There is no ""bug reopened"" status on launchpad, how come?"
1719208,2019-01-21 14:12:12 UTC,"Follow up note: The new Permission Tree Display Entries interface allows customization of the tree. If a flag could be added to designate one of the entries as the default to that interface, that would be beneficial."
1719208,2019-04-16 15:59:39 UTC,Marking Confirmed.
1719208,2019-05-11 04:29:11 UTC,"Quick question: if the goal is to reduce the amount of times staff members open that menu, would making that dropdown's value sticky accomplish the same outcome?  That would still help staff whose administrators haven't set this setting in the Permission Tree Display Entries interface.  It would also be more flexible, in case certain OUs or workstations have different permission groups they typically use."
1719208,2019-05-13 15:37:46 UTC,"I would prefer a default setting rather than it being sticky. With stickiness, I would be very concerned that it would get changed for one user and then staff would not notice that it was changed (especially on shared workstations) and create following users with the same type. Since staff accounts are created with the same interface as patrons, this would potentially cause patrons to get assigned staff accounts, as well as creating other headaches."
1719210,2017-10-08 13:38:25 UTC,"After a few days of testing i can say using kernel 4.12 works for me, but options bt_coex_active=0 doesn't. Also the new linux-firmware  update didn't fixed it."
1719210,2017-10-08 18:09:35 UTC,Confirming this is very much *not* fixed - the last linux-firmware upload doesn't seem to have touched anything iwlwifi-related at all: https://launchpadlibrarian.net/339888041/linux-firmware_1.168_1.169.diff.gz
1719210,2017-10-08 18:53:03 UTC,"I also seem to now be having Bluetooth-unrelated issues with iwlwifi, filed in bug 1722109"
1719210,2017-10-18 12:56:45 UTC,"I have to correct my earlier statement (comment 14), the linux-firmware package update didn't fix the problem after all - it seemed to work for a while, but I was mistaken. Now, however, I've gotten it working. The correct fix is to add the following line to the end of /etc/modprobe.d/iwlwifi.conf"
1719210,2018-01-15 16:41:27 UTC,The exact manifestation of this seems to have changed (now the gnome settings UI claims that my hardware doesn't have bluetooth support at all - despite CLI bluetoothctl still being aware of it) but the basic issue still very much remains: 4.13 from artful => bluetooth inoperable; 4.10 from zesty => works fine.
1719210,2017-10-27 11:36:12 UTC,"After some testing, i experience a audio delay, when using bluetooth headset when using ""options iwlwifi bt_coex_active=0"", which doesn't happen with kernel 4.12"
1719210,2017-12-22 22:42:17 UTC,"Following response #4, I did:"
1719210,2018-01-26 21:25:11 UTC,"Adding linux-firmware as an affected package - on further investigation, it turns out that the real problem here appears to be firmware incompatibility between the Wifi and Bluetooth parts of the 8260 package."
1719210,2018-02-09 16:17:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719210,2017-10-19 14:08:18 UTC,"i also have to correct my statement
""options iwlwifi bt_coex_active=0"" and Kernel 4.13 works for me, but with 4.14 i still got wifi problems, but it's sill an RC and not default in 17.10"
1719210,2017-10-07 12:20:04 UTC,"Same issue here on a Thinkpad P50, although I don't see any iwlwifi crash in the logs. Going back to the 4.10 kernel from Zesty fixes the problem."
1719210,2017-10-04 21:44:52 UTC,"Or so I thought :-(    I got set up for bisecting again, and now I can't reproduce the problem at all."
1719210,2017-10-05 14:23:08 UTC,@ Kai-Heng Feng (kaihengfeng) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719210/comments/6
1719210,2017-10-04 22:56:36 UTC,"OK, I think I finally found the real trigger, helped by John Tanner's comment and Googling the bt_coex_active option. It's trying to simultaneously use bluetooth and a *2.4GHz* wifi network."
1719210,2017-10-04 20:59:50 UTC,"Hmm... empirically, I seem to have discovered a factor related to why this sometimes works and sometimes does not with 4.13 - for me, the bug only occurs if my laptop is booted *without* AC power applied."
1719210,2017-10-03 22:12:38 UTC,This appears to be a problem with either the kernel or the firmware for intel wifi/bluetooth chipsets. I've found that adding the following to /etc/modprobe.d/iwlwifi.conf and then rebooting seems to solve my problems:
1719210,2017-09-29 18:09:27 UTC,"I have the same problem with similar symptoms, headset connects and works, after some time, the video stops and the headset stops working, than i can't connect again, have to remove the device, reboot, turn of and on the headphones to get it working again. But the problems doesn't always occur, somtines they work normaly. I never testet ubuntu with kernel 4.12 maybe i should do that"
1719210,2017-09-28 21:33:09 UTC,I am seriously confused.
1719210,2017-09-25 03:03:42 UTC,Does this also happen to 4.14-rc1?
1719210,2017-09-25 02:38:56 UTC,Seeing similar issues with a Logitech M337 bluetooth mouse under the new 4.13.0-11 kernel.
1719210,2017-09-24 20:59:21 UTC,Mainline ppa 4.12.14 is working OK
1719210,2017-09-24 20:46:06 UTC,Lack of functionality also a problem in mainline-ppa 4.13.3 version. The following messages are logged to the journal:
1719210,2017-09-24 20:30:10 UTC,This change was made by a bot.
1719210,2017-10-06 22:32:49 UTC,"The latest linux-firmware update today, running the stock kernel 4.13.0-12-generic has fixed the problem for me (connecting to Sony SRS-XB40 speaker)."
1719214,2019-10-18 09:39:07 UTC,The charm also lacks support for storage..
1719235,2017-10-16 03:55:34 UTC,The problem still exists. Now I have not find a perfect way to resolve it.
1719235,2017-10-06 15:27:48 UTC,Since mitaka is no longer supported can you confirm that this is still a problem in later versions?
1719235,2017-09-25 05:48:01 UTC,"Set the status ""In progress"" because this report has an assignee."
1719243,2017-09-26 08:11:25 UTC,"Can you elaborate? Are you asking about building SBCL's runtime with PIC-related C-compiler options or is the question about code emitted by SBCL's compiler, or the fasl format?"
1719280,2017-09-29 14:23:56 UTC,Fix for Charm Helpers proposed to the following branch:
1719280,2017-10-02 08:43:31 UTC,Hi Tytus
1719280,2017-10-02 10:17:22 UTC,"No - charm-helpers is not part of openstack; you'll need to fork the project on github.com to your own account, create a branch on that repository, make your changes, push back to your repo copy on github.com and then raise a pull request (which will automatically pop up in the WebUI)."
1719280,2017-09-27 11:07:00 UTC,Raising charm-helpers target as well - we'll need to make this part of the HAProxy context and template for classic charm support for running with IPv6 disabled.
1719280,2017-10-02 14:11:41 UTC,"Fix for charms.openstack proposed to branch: master
Review: https://review.openstack.org/#/c/508888/"
1719280,2017-10-23 09:06:09 UTC,"Reviewed:  https://review.openstack.org/508888
Committed: https://git.openstack.org/cgit/openstack/charms.openstack/commit/?id=82ba9595fa05dc6ddccabb3242b2f9c222f74c6e
Submitter: Zuul
Branch:    master"
1719280,2017-10-02 11:01:25 UTC,Pull request created.
1719280,2017-09-27 11:03:31 UTC,The ip charmhelper has a is_ipv6_disabled() function - that information could be passed via a context to the templates so that this sort of thing can be conditionally enabled.
1719280,2017-09-27 10:05:10 UTC,"Looking at the main charmhelpers template, things work exactly the same way there as well."
1719280,2017-09-27 11:00:09 UTC,"It also breaks the dual-stack work done last cycle, which depends on this binding so I'm a little worried there are alot of moving parts in play here that might break."
1719280,2017-09-25 09:35:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507033/"
1719280,2017-09-27 10:05:23 UTC,"frontend tcp-in_{{ service }}
    bind *:{{ ports[0] }}
    bind :::{{ ports[0] }}
    {% for frontend in frontends -%}
    acl net_{{ frontend }} dst {{ frontends[frontend]['network'] }}
    use_backend {{ service }}_{{ frontend }} if net_{{ frontend }}
    {% endfor -%}
    default_backend {{ service }}_{{ default_backend }}"
1719280,2017-09-27 10:06:04 UTC,Tytus - do you see this issue with non-reactive charms as well?
1719280,2017-09-27 11:00:44 UTC,We could conditionally enable the IPv6 binding IF IPv6 is enabled on the host system - that would probably work in all use-cases.
1719280,2017-09-27 10:32:11 UTC,"It is exposed in file ""charmhelpers/contrib/openstack/context.py"" file:"
1719280,2017-09-27 10:59:19 UTC,That approach is not 100% reliable as its possible that network spaces or config provided networks might also be IPv6 subnet configurations so I'm reticent to tie this to the prefer-ipv6 feature (which I'd really like to drop from the charms as it was implemented to support IPv6 deployments in the context of a very old juju version).
1719280,2017-09-27 10:23:46 UTC,It looks like templates for other charms have been modified manually in this environment:
1719282,2017-09-25 19:14:47 UTC,"Do you have more information on the sequence of commands issued to QEMU? I see the drive-mirror invocation, but then I don't see what causes the shutdown or the BLOCK_JOB_COMPLETED event. Usually this is in response to a user command. I'm wondering if the exact sequence issued is safe."
1719282,2017-09-27 11:32:02 UTC,"In last try, vm shutdown before completing blockjob.
So i tried again and these are the exact qmp commands which i used:"
1719282,2017-10-09 18:48:00 UTC,"It *looks* to me at a glance like the sequence should be safe, but I don't have any hunches for what could be going wrong, or why."
1719282,2017-10-24 07:59:11 UTC,"There is no source or destination machine. I used drive-mirror to transfer VM Image to different physical disk on same machine (""mode"": ""absolute-paths""). After block-job-complete and shutting down vm, I start vm again with same command with different drive path pointing to mirrored image. ""-drive 'file=MIRRORED_IMAGE_PATH..""."
1719282,2019-12-23 20:56:14 UTC,"OK, so we're only talking about migrating a disk and not a whole VM, I misunderstood. However... are you using qemu *2.7*? That's quite old! Before digging into this further I need to insist that you try on a supported release, either 4.0.1, 4.1.1, or 4.2.0."
1719282,2020-02-22 04:17:23 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1719289,2020-09-20 09:36:46 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1719291,2019-10-30 07:22:36 UTC,По данной проблеме решения нет до сих пор.
1719307,2017-12-19 15:08:37 UTC,"I have looked into the Nexenta code and if it supports multipathing then it must be using discovery because looking at the driver code it relies on the cinder.volume.driver.ISCSIDriver code for the initialize connection, which uses the ""provider_location"" field from the volume that is filled by the ""_do_export"" method in cinder.volume.drivers.nexenta.iscsi.NexentaISCSIDriver."
1719307,2017-12-19 18:49:18 UTC,"Gorka, os-brick does the discovery before attaching the volume to instance. It uses the path returned by cinder in provider_location and discovers additional paths. It worked fine when I tested multipath with NexentaStor."
1719307,2017-12-15 20:14:27 UTC,It's possible they do not need any additional settings to support multipath. Hopefully someone from Nexenta can chime in here and possibly add to their documentation.
1719307,2017-12-15 21:12:34 UTC,"Hi, just as Sean said, we don't need any additional settings.
All you need is multipath tool installed on your client and enabled in nova.conf. Feel free to email me if you have any further question about using NexentaStor and cinder."
1719312,2017-10-24 11:07:02 UTC,"Whatever happened, the bug appears to be no longer present in current ubuntu release 17.10. This may well be due to Ubuntu's switch to GNOME."
1719312,2018-07-11 14:38:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719314,2019-08-21 14:19:20 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1719314,2019-08-22 11:14:18 UTC,You can close it. It was Nvidia driver issue. Now I dont have the same.
1719314,2019-08-22 11:17:43 UTC,Thanks for your reply so closing.
1719316,2017-09-25 14:16:32 UTC,"At the moment, it is not possible to run ephemeral environments with custom network configuration. Effectively, you can't run commissiong or any other epemeral environment that requires you to tag an network interface to access the network."
1719316,2019-09-19 12:04:39 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1719318,2017-09-25 13:54:19 UTC,This is mutt 1.8.3+neomutt20170609-2build1 on artful.
1719326,2019-01-01 12:27:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719329,2017-09-25 14:39:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507151"
1719329,2017-11-21 08:00:13 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/507151"
1719330,2020-08-10 02:09:39 UTC,python-volatility 2.6-1-xenial1
1719331,2018-01-23 08:52:49 UTC,"Hi Michael,
    I was able to reproduce this. The issue is very slightly different to this bug so I've raised a new bug to cover further investigation and any potential fix Bug #1744886
Liam"
1719331,2018-01-16 15:26:03 UTC,I have been unable to reproduce this issue using the current stable version of aodh ( cs:aodh-10 ).
1719331,2018-01-08 16:10:14 UTC,As of 2018-1-8 this bug persists for the aodh charm.
1719331,2017-10-26 13:02:35 UTC,"Reviewed:  https://review.openstack.org/514980
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=56b02097b4fb4066b2552fab135caefac061086e
Submitter: Zuul
Branch:    stable/17.08"
1719331,2017-10-25 09:29:55 UTC,"Fix proposed to branch: stable/17.08
Review: https://review.openstack.org/514980"
1719331,2017-09-29 17:39:19 UTC,"Reviewed:  https://review.openstack.org/507977
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=ac98ae51dcdd79d604b4dbbdd35388f513ea17ea
Submitter: Zuul
Branch:    master"
1719331,2018-01-16 15:47:54 UTC,Aodh/Keystone versions:
1719331,2017-09-29 14:05:23 UTC,"Reviewed:  https://review.openstack.org/507978
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=a2375ca7f2fe6a7c67ebf48f9fe51f4ae1445dc0
Submitter: Zuul
Branch:    master"
1719331,2017-09-27 20:40:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507979"
1719331,2017-09-27 20:39:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507978"
1719331,2017-09-27 20:39:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507977"
1719331,2017-09-26 21:12:25 UTC,I don't think that this is related to https://bugs.launchpad.net/charm-aodh/+bug/1713944
1719331,2017-09-25 15:31:09 UTC,"FWIW, I'm not 100% sure, but this might have a connection with:
https://bugs.launchpad.net/charm-aodh/+bug/1713944
since both are reactive OpenStack charms."
1719331,2017-09-29 14:10:00 UTC,"Reviewed:  https://review.openstack.org/507979
Committed: https://git.openstack.org/cgit/openstack/charm-barbican/commit/?id=d2a4ec2bc92b2d6413f4af05d11987e83bc21740
Submitter: Zuul
Branch:    master"
1719332,2017-09-25 18:54:14 UTC,This bug only happens with two or more connections configured (one ethernet and another wireless) being at least one of them flagged not to save password.
1719333,2017-11-23 13:47:40 UTC,"Reviewed:  https://review.openstack.org/507249
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=af0feeb18a4f5fb2c20fffb6d85617d1775e5844
Submitter: Zuul
Branch:    master"
1719333,2017-11-27 14:44:17 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/523137"
1719333,2017-12-16 18:44:26 UTC,"Reviewed:  https://review.openstack.org/508312
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=6857b7f3686e93805bcddae91f307c6b62aa72d6
Submitter: Zuul
Branch:    master"
1719333,2018-01-08 17:04:07 UTC,"Reviewed:  https://review.openstack.org/507250
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=2e4a6e237cf226eb61cf905a72cfb5eb3d5177f0
Submitter: Zuul
Branch:    master"
1719333,2018-01-16 10:36:00 UTC,"Reviewed:  https://review.openstack.org/533047
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=3cd84afcfc71ad41dceb15619a3c89ce21db605c
Submitter: Zuul
Branch:    master"
1719333,2018-01-12 03:15:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/533047"
1719333,2018-01-16 10:21:25 UTC,"Reviewed:  https://review.openstack.org/533038
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=f965ff615e3d4df0a2b38477d5441604cd0b85e5
Submitter: Zuul
Branch:    master"
1719333,2018-01-25 22:43:06 UTC,"Reviewed:  https://review.openstack.org/523137
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=6a27419521bae9cf6b0ca033d04ef268abebe1bd
Submitter: Zuul
Branch:    stable/pike"
1719333,2017-10-30 11:58:27 UTC,This issue was fixed in the openstack/heat 9.0.1 release.
1719333,2018-01-12 02:46:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/533038"
1719333,2017-10-27 07:31:42 UTC,This issue was fixed in the openstack/heat 10.0.0.0b1 development milestone.
1719333,2017-09-25 19:41:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/507249"
1719333,2017-09-28 21:15:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/508312"
1719333,2017-09-28 09:15:34 UTC,"Reviewed:  https://review.openstack.org/507930
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=ab46fae9cf386b9578df4dd8ff35d68b281c7c0c
Submitter: Jenkins
Branch:    stable/pike"
1719333,2017-09-27 16:58:19 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/507931"
1719333,2017-09-27 16:58:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/507930"
1719333,2017-09-27 15:42:10 UTC,"Reviewed:  https://review.openstack.org/507248
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=f1961c734e81f1e39c16b04558e17e4048c78c06
Submitter: Jenkins
Branch:    master"
1719333,2017-09-27 15:41:58 UTC,"Reviewed:  https://review.openstack.org/507206
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=49d833f9aca351102bb1c9140231b809d8b4c519
Submitter: Jenkins
Branch:    master"
1719333,2017-09-25 19:41:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/507250"
1719333,2017-09-25 16:50:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507206"
1719333,2017-09-25 19:41:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507248"
1719333,2017-09-25 16:57:37 UTC,"One issue, addressed by the patch above, is that we're loading more attribute values than we need to in the legacy path. ""show stack"" completes in ~half the time with that patch."
1719333,2017-10-04 00:25:33 UTC,"Reviewed:  https://review.openstack.org/507931
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=d00f1a40f82ba6ffec9d2fbc71822df977f7cc01
Submitter: Jenkins
Branch:    stable/pike"
1719336,2017-10-20 23:31:43 UTC,Quick fix here: https://github.com/snapcore/snapcraft/pull/1637
1719336,2017-09-25 19:24:00 UTC,"Sorry, I pasted the os-release that actually works. WITHOUT the space it crashes."
1719336,2017-09-25 19:11:35 UTC,The ID is invalid according to the specification in os-release(5)
1719338,2017-09-27 07:16:08 UTC,"On Mon, 2017-09-25 at 15:04 +0000, Ritesh Raj Sarraf wrote:

> Currently, setup.py relies on '/etc/apt/sources.list' to detect if it
> is an apt based system.
> In my opinion, this is fragile, especially given that
> /etc/apt/sources.list.d/ sub config dir model is also supported.
>
> I propose that a check on /usr/bin/apt or /usr/bin/apt-get be made
> instead. Both binaries are provided by the 'apt' pacakge.
"
1719339,2017-09-27 13:33:54 UTC,"Use simpler setup for reproducing.
Was used only qemu-system-x86_64 (without using high-level wrappers and managers of virtual machines: libvirt, virsh, virt-install, virt-manager etc..). My setup with two consoles:"
1719339,2018-07-11 01:53:23 UTC,"I'm seeing this on AWS EC2 when there's (apparently) high logging volume to the console, very similarly to https://www.reddit.com/r/sysadmin/comments/6zuqad/mongodb_aws_ec2_serial8250_too_much_work_for_irq4/"
1719339,2018-07-11 07:12:55 UTC,"On further investigation of my instance, there appeared to be no high logging volume to the console, nor anything using the /dev/ttyS0 other than agetty.  Switching from the generic kernel to the AWS kernel seems to have stabilised it."
1719339,2018-07-12 01:00:28 UTC,Further update: AWS kernel experienced the same error messages after just over 3 hours of runtime.
1719339,2020-11-10 03:05:13 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1719339,2021-01-09 04:17:54 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1719340,2018-02-12 13:51:12 UTC,This issue was fixed in the openstack/heat 9.0.3 release.
1719340,2018-01-23 13:06:19 UTC,"Reviewed:  https://review.openstack.org/535932
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=2c9032c675dd712db2b4e06264b12d8622160993
Submitter: Zuul
Branch:    stable/pike"
1719340,2017-09-25 16:50:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507207"
1719340,2017-10-27 07:31:44 UTC,This issue was fixed in the openstack/heat 10.0.0.0b1 development milestone.
1719340,2017-09-27 15:42:23 UTC,"Reviewed:  https://review.openstack.org/507207
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=9b5f66351f450a0796d46e54f23106551cc87193
Submitter: Jenkins
Branch:    master"
1719340,2018-01-19 20:47:56 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/535932"
1719348,2017-10-05 13:01:26 UTC,"You'll probably want to add a check in snapcraft/plugins/meson.py _meson_run like ""if '--prefix' not in self.options.meson_parameters"" and then meson_command.extend() to add it only if it wasn't specified. And don't forget to add it to schema['properties'] at the top of the file."
1719354,2020-07-14 14:42:59 UTC,"As part of our effort to fix languishing bugs, I'm revisiting this one and will drive it to conclusion."
1719354,2018-10-12 21:51:16 UTC,"The net_admin denial is probably caused by a bug in systemd, see https://bugzilla.opensuse.org/show_bug.cgi?id=991901 and https://github.com/systemd/systemd/pull/10085
I'd recommend not to allow that capability in the nmbd profile, and instead apply the patch to systemd."
1719354,2018-07-02 19:45:48 UTC,"Confirmed that cosmic is fine now, but there are still issues in xenial as reported, and these two in bionic:
[  132.722115] audit: type=1400 audit(1530560652.717:57): apparmor=""DENIED"" operation=""capable"" profile=""/usr/sbin/nmbd"" pid=717 comm=""nmbd"" capability=12  capname=""net_admin""
[  132.723745] audit: type=1400 audit(1530560652.717:58): apparmor=""DENIED"" operation=""sendmsg"" profile=""/usr/sbin/nmbd"" name=""/run/systemd/notify"" pid=717 comm=""nmbd"" requested_mask=""w"" denied_mask=""w"" fsuid=0 ouid=0"
1719354,2018-04-24 20:43:02 UTC,"> sudo mv /etc/apparmor.d/usr.sbin.smbd /etc/apparmor.d/usr.sbin.smbd_OLD
"
1719354,2018-04-24 13:26:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719354,2017-09-27 16:21:10 UTC,"aa-notify doesn't have an option to silence specific events - hey, it's job is to annoy^Wnotify you, so what do you expect? ;-)"
1719354,2017-09-27 13:44:33 UTC,"Mr.Christian,"
1719354,2017-09-26 18:57:24 UTC,This is fixed in AppArmor bzr since
1719354,2018-04-24 13:41:40 UTC,I run this:
1719355,2017-11-16 09:49:33 UTC,"SRU verification for Artful:
I have reproduced the problem with ubuntu-themes 16.10+17.10.20171012.1-0ubuntu1 in artful and have verified that the version of ubuntu-themes 16.10+17.10.20171115-0ubuntu1 in -proposed fixes the issue."
1719355,2017-11-29 21:37:49 UTC,"The verification of the Stable Release Update for ubuntu-themes has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1719355,2017-11-29 21:37:38 UTC,This bug was fixed in the package ubuntu-themes - 16.10+17.10.20171115-0ubuntu1
1719355,2017-11-15 17:37:10 UTC,"Hello Carlo, or anyone else affected,"
1719355,2017-11-14 22:14:04 UTC,This bug was fixed in the package ubuntu-themes - 16.10+18.04.20171114-0ubuntu1
1719355,2017-09-27 18:13:42 UTC,"Hi Laney, do you think this solution is acceptable?"
1719355,2017-09-26 06:43:05 UTC,"I considered how switchers look like in headerbar vs other places and the first does not look really right, but I understand your point."
1719355,2017-09-25 19:17:05 UTC,"Incomplete for ubuntu-themes, pending comments from Design."
1719355,2017-09-26 13:03:01 UTC,"It's not supposed to look like this, we just messed up when writing the theme somehow"
1719362,2017-09-25 16:43:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507202"
1719362,2017-11-14 12:22:50 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/519636"
1719362,2017-11-14 12:10:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/519632"
1719362,2017-11-03 18:35:58 UTC,"Reviewed:  https://review.openstack.org/507202
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ea9bf5216be60fb3fa1704cf6257adca4e634cb1
Submitter: Zuul
Branch:    master"
1719362,2018-02-26 17:35:49 UTC,"Reviewed:  https://review.openstack.org/519636
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2cfdb9c056192ff38e44fd5f03c9ede33ed09bd9
Submitter: Zuul
Branch:    stable/ocata"
1719362,2017-10-26 12:33:38 UTC,"This bug is pretty important in NFV use cases where virtual machine images have no capacity for using metadata other than config drive. We have several clouds deployed where this is an issue, and of course the potential for data corruption is there as well. There must be many users of OpenStack out there not knowing they have this particular problem and potentially still doing live migration."
1719362,2017-09-26 10:44:29 UTC,"Good question. I asked Dan Berrangé who was helping me debug this and he says not, as it can't be fixed. The correct behaviour here is not to pass the flag if we don't want to block migrate anything, which makes sense anyway."
1719362,2017-09-26 10:12:00 UTC,Should we target this to the upstream libvirt Python bindings too?
1719362,2017-10-26 12:40:27 UTC,Can't comment more on the importance of this being fixed.  Curtis's (6-curtis) point and UCs makes this a high importance bug.  If I could +2 Curti's comment I would.
1719362,2017-11-15 17:44:46 UTC,"Reviewed:  https://review.openstack.org/519632
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2486f34ec49ffdf381912d7f0fd5199ce0dfa013
Submitter: Zuul
Branch:    stable/pike"
1719366,2017-09-25 17:10:32 UTC,"StacktraceTop:
 XkbGetUpdatedMap (dpy=0x56089aaeda60, which=7, xkb=0x56089ab970a0) at ../../../src/xkb/XKBGetMap.c:580
 XkbGetMap (dpy=0x56089aaeda60, which=which@entry=7, deviceSpec=deviceSpec@entry=256) at ../../../src/xkb/XKBGetMap.c:603
 grab_ungrab (rootwin=rootwin@entry=0x56089ab07010, keyval=32, modifiers=4, grab=grab@entry=1) at bind.c:203
 do_grab_key (binding=binding@entry=0x56089ab69ae0) at bind.c:326
 keybinder_bind_full (keystring=0x56089ade2ad0 ""<Control>space"", handler=0x56089a64bfd0, user_data=0x56089ab7ef40, notify=0x0) at bind.c:584"
1719369,2019-02-19 13:51:14 UTC,is this still an issue?
1719369,2019-02-19 14:37:34 UTC,yea we do it several different places
1719369,2019-05-21 14:44:25 UTC,"copying the discussion from irc tripleo meeting:
0:02:49    chandankumar ╡ If there is no any other topic in queue I want to discuss about this blueprint
                        ╡ https://blueprints.launchpad.net/tripleo/+spec/os-client-config-switch
0:03:16       +mwhahaha ╡ meh
0:03:39             ▬▬▶ ╡ rascasoft (~rascasoft@2.229.194.155) has joined #tripleo
0:03:42       +mwhahaha ╡ so we already partially implemented that for standalone
0:03:47              ℹ  ╡ marios_|ruck is now known as marios|ruck|call
0:03:48    chandankumar ╡ since we have added support for clouds.yaml for standalone and undercloud
0:03:54       +mwhahaha ╡ we'd need to create a workflow for generating that for the overcloud
0:03:59    chandankumar ╡ I am about to start working on overcloud
0:04:07       +mwhahaha ╡ I would just generate both for now
0:04:15               ⤷ ╡ and we can remove the *rc files in a later release
0:04:30    chandankumar ╡ but the question is https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/extraconfig/post_deploy
                        ╡ current code and tht stuff resides here
0:04:51               ⤷ ╡ can we move the same
                        ╡ https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/extraconfig/post_deploy/clouds_yaml.py script to
                        ╡ python-tripleoclient
0:05:02       +mwhahaha ╡ it wouldn't be tripleoclient
0:05:05               ⤷ ╡ it would be in tripleo-common
0:05:09               ⤷ ╡ and tripleoclient
20:05:22    chandankumar ╡ and generate the clouds.yaml for stdanlone overcloud and undercloud                                                      │
20:05:25       +mwhahaha ╡ you'll want to find the existing stackrc generation and either modify it or duplicate it                                 │
20:05:41               ⤷ ╡ the underclo..."
1719369,2019-06-11 12:31:10 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/664568"
1719369,2019-06-17 08:17:16 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/665604"
1719369,2019-07-12 10:43:43 UTC,"Reviewed:  https://review.opendev.org/664568
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=3c4cb58d8162fadded40076a2e3b40a510a6e9d7
Submitter: Zuul
Branch:    master"
1719369,2019-07-15 14:13:32 UTC,"Reviewed:  https://review.opendev.org/665604
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=41d9901ef282bda16f6784be53dd1287442f671c
Submitter: Zuul
Branch:    master"
1719372,2017-09-25 17:40:42 UTC,"StacktraceTop:
 ?? ()
 XForceScreenSaver (dpy=0x55bbfd5c1900, mode=mode@entry=0) at ../../src/FSSaver.c:53
 XResetScreenSaver (dpy=<optimized out>) at ../../src/FSSaver.c:42
 gs_monitor_simulate_user_activity (monitor=0x55bbfd602740) at gs-monitor.c:195
 listener_simulate_user_activity_cb (listener=<optimized out>, monitor=0x55bbfd602740) at gs-monitor.c:287"
1719375,2018-09-10 20:47:19 UTC,"I always thought that the term ""State"" in the acquisitions module was not very idiomatic U.S. English.  Eva's suggestions of ""Status"" or ""Stage"" seems much better.  I would prefer ""Status"", because this is consistent with the terminology used elsewhere in the interface.  Eva's suggestions for ""Name"" makes sense to me as well."
1719375,2018-02-28 07:11:32 UTC,"We have tried to identify and merge inconsistent translations (it was much more complex than we expected). I summarized a list of terms that can not be merged. Currently we have identified about 14 terms, that can´t be merged due to different term used in Czech for the same English term."
1719390,2017-09-25 18:34:44 UTC,"StacktraceTop:
 gcm_prefs_calib_apply_cb (widget=<optimized out>, prefs=0x5648b0251370) at cc-color-panel.c:316
 g_closure_invoke (closure=0x5648b0786a30, return_value=0x0, n_param_values=1, param_values=0x7ffcbbc97870, invocation_hint=0x7ffcbbc977f0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x5648b064a6f0, detail=detail@entry=0, instance=instance@entry=0x5648afeb97e0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffcbbc97870) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x5648afeb97e0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffcbbc97a30) at ../../../../gobject/gsignal.c:3391
 g_signal_emit (instance=instance@entry=0x5648afeb97e0, signal_id=<optimized out>, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447"
1719390,2017-09-27 20:58:09 UTC,Wont be fixed this cycle.  Prerequisite is a colourhug.
1719390,2017-10-23 14:06:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719390,2018-12-12 15:35:45 UTC,"That's still an issue in 18.10, https://errors.ubuntu.com/problem/130164f7d8b3f8beb224091156922974a133280b"
1719405,2020-04-13 12:30:55 UTC,The XML editor has been improved a lot for 1.0. Quite a few of your points have been adressed.
1719407,2017-09-26 17:27:55 UTC,"Some background: this is pure configuration, so (luckily) locally changeable. The value currently used to sort by title is generated using the ""magical"" MARC tag ""tnf"", which we create by taking the 245$a and trimming of non-filing characters (""tnf"" stands for ""title non-filing"").  We store the ""tnf"" tag in metabib.real_full_record, and just pull that via a record attribute called ""titlesort"" with sorter=TRUE."
1719412,2017-09-25 19:48:49 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1719415,2018-02-08 14:26:53 UTC,"Can confirm, been able to reproduce"
1719440,2019-09-19 14:49:15 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1719456,2017-09-25 20:58:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719456,2017-09-28 12:41:14 UTC,Starting caffeine via the commandline produces the same error.
1719456,2017-09-28 13:00:27 UTC,"Right, it's because you're running wayland and the file .Xauthority does not exists. Either caffeine has to be fixed to run under wayland or you can swtich to an xorg session."
1719459,2020-12-05 04:17:22 UTC,[Expired for tempest because there has been no activity for 60 days.]
1719459,2020-10-05 09:09:36 UTC,tempest verify-config tool doesn't have --config-file argument anymore:
1719459,2020-10-05 09:12:33 UTC,"Given the previous comment and the facts that this is quite old bug and it's possible to point to a tempest.conf outside of the workspace using environment variables, I'm gonna mark this as Incomplete. If you feel like --config-file argument is important for the verify-config tool, please, feel free to reopen this bug."
1719459,2017-10-12 10:14:13 UTC,"Hi,"
1719459,2017-10-12 15:27:21 UTC,So while I agree there is workspace support and you can use the env vars to workaround this. I feel this is still a valid bug.
1719459,2017-10-13 08:32:04 UTC,"Yes, it would more useful, if a user can pass a config file from CLI. There was an attempt to do it, see the following bug [1], but due to the current design, this small change/addition would require a lot of big changes."
1719460,2017-09-27 14:24:43 UTC,Related patch: https://review.openstack.org/#/c/507854/
1719460,2018-04-16 19:46:41 UTC,"Reviewed:  https://review.openstack.org/507854
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a0b4116ed68cb71a9a74fee616b5036f5fda4dd2
Submitter: Zuul
Branch:    master"
1719460,2018-04-16 20:54:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561715"
1719460,2018-04-19 12:27:46 UTC,"Reviewed:  https://review.openstack.org/561715
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9cb96ab9319aea2e63c0c67cab9e5d92638bfcb2
Submitter: Zuul
Branch:    stable/queens"
1719460,2018-04-20 13:13:15 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1719460,2018-04-25 09:23:54 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1719463,2017-09-26 09:42:19 UTC,"Would really appreciate any help with this. Extreme ill health, and need to critically rely on ipads for some things. Complete deal breaker about staying with LM, if remains broken ... unable to do format/reinstall, as the libimobiledevice install would break pc/ipad connection again, and wouldn't be able to stay on Linux, as LM was also the only distro with pressure sensitivity need for using Ugee/art, which was great."
1719463,2017-09-26 09:43:39 UTC,"The ipads get their wifi connection from the machine. All wifi is enabled first through broadband modem and router, but they're working fine/no problem with internet connection. The ipads' connection broke the same moment I did the libplist3/libimobile update."
1719471,2017-10-11 09:51:19 UTC,"I see more and more ptrace changes in upstream libvirt now that 4.13 is out.
I expect signal related changes when 4.14 is there."
1719471,2017-10-11 17:52:06 UTC,signal is actually in 4.13 as well
1719471,2017-10-11 17:56:26 UTC,"I have not had time to chase this one enough to answer it, yet. It is high on the priority list but it seems that list is growing faster than I can service it lately."
1719473,2020-06-17 09:01:31 UTC,"In MaaS 2.4.2 (7034-g2f5deb8b8-0ubuntu1), I ran into a somewhat similar issue. I configured a DNS server (see attachment) in the ""Subnets"" section."
1719473,2020-06-17 15:30:13 UTC,"Comment #6 happens when the MaaS DNS IP is configured on the subnet section of the PXE network. As mentioned in [1], if the DNS IP is removed from the subnet section - hence, the default is used - then ""search <authoritative-zone>"" is configured in resolv.conf."
1719473,2020-06-02 16:52:09 UTC,Re-opening as this is certainly still a problem and the only reason fro the lack of activity is because it hasn't been worked on.
1719473,2020-02-07 16:55:57 UTC,"So I would say the current status of this is that currently there is no way to modify the domain search list of a MaaS deployed machine, with one exception. If you add a domain to the DNS tab in MaaS and then mark it as authoritative, MaaS will add that domain to the search list."
1719473,2019-09-19 14:53:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1719473,2017-10-10 17:43:53 UTC,"What we are doing is ""spoofing"" DNS for an offline deployment."
1719473,2017-10-10 14:48:23 UTC,"Hi Jeff,"
1719481,2017-10-03 01:44:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719482,2019-06-30 04:45:43 UTC,"This can't be reproduced with Inkscape 0.92.4 on Windows 10, so it will be closed."
1719482,2019-06-30 04:45:05 UTC,"As OP is no longer using Inkscape on Windows, further updates are unlikely, so this bug will be closed."
1719482,2017-11-06 10:55:55 UTC,Thanks! Let's see and hope...
1719482,2017-11-06 05:44:39 UTC,"Hi Eduard,"
1719482,2017-10-09 22:58:44 UTC,"Ah yep, that crashes too."
1719482,2017-10-09 09:00:22 UTC,"After installing mingw-w64-x86_64-gtk2 you can run the gtk-demo again:
- Open a MinGW shell (simply use the ""MSYS2 MinGW 64-bit"" shortcut)
- execute ""gtk-demo"" (it will be on your search path)"
1719482,2017-10-09 00:12:49 UTC,"Hi Eduard,"
1719482,2017-10-07 13:37:27 UTC,"Hi Tristan, yes, if even the gtk-demo crashes it is certainly not an Inkscape issue."
1719482,2017-10-05 23:06:16 UTC,Perhaps it is a GTK problem:
1719482,2017-10-05 18:24:25 UTC,"To rule out a gtk issue you you could try to run the gtk demo:
- download [1]
- copy ""gtk-demo.exe"" from the /bin directory
  to the Inkscape installation directory
- copy the share/ folder to the Inkscape installation directory
- execute ""gtk-demo.exe"" from cmd.exe"
1719482,2017-10-05 01:42:54 UTC,"The system has a NVIDIA Quadro K600. I just reinstalled the latest drivers (""385.69-quadro"") but that didn't seem to help (attached is the output). Other than that it's a pretty standard single display via DVI to a HP L2245wg monitor."
1719482,2017-09-28 11:16:10 UTC,"OK, thanks for feedback."
1719482,2017-10-05 00:44:32 UTC,"Oh, wow, that looks certainly wrong..."
1719482,2017-10-04 23:38:39 UTC,"Oh ok, here it is, starting at about 1500 because the cmd screen was full:"
1719482,2017-10-04 23:21:13 UTC,"Could you attach the full backtrace (""Type <return> to continue"")?"
1719482,2017-10-04 22:59:29 UTC,"Sorry I just looked the message more closely, it looks like the mingw64 directory should be copied to c:."
1719482,2017-10-04 22:56:15 UTC,"Forgot to mention this was for the 64 bit version, with the 64bit gdb, e.g."
1719482,2017-10-04 22:45:37 UTC,Thanks for the fast reply.
1719482,2017-10-04 22:15:45 UTC,There does not seem to be anything suspicious in the environment variables.
1719482,2017-10-04 01:41:28 UTC,Apologies for the delayed reply. Changing PATH did not help.
1719482,2017-09-28 03:34:45 UTC,"Thanks for the suggestion, but I get the same lack-of-message when running inkscape.com. Is there any other way to get an output or log?"
1719482,2017-09-26 00:38:30 UTC,"The tab issue seams real but I suspect it's only a cosmetic issue (at least we never had any similar reports and I doubt there aren't any other users whose name starts with a ""t"")."
1719482,2017-10-05 00:48:28 UTC,P.S. You can also try to redirect gdb output to a file using
1719482,2017-09-28 03:40:18 UTC,"If I try inkview.com on a svg, I get a GUI message this time from Windows just sating ""A problem caused the program to stop working correctly. Please close the program."" No more detail."
1719484,2018-01-08 18:30:21 UTC,From /usr/bin/chromium-browser:
1719487,2019-08-28 20:59:30 UTC,"Reviewed:  https://review.opendev.org/507486
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97b8cb3f5804cd39b7eb3ac2d481e43ceb52f2cf
Submitter: Zuul
Branch:    master"
1719487,2019-09-27 09:00:41 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1719487,2019-07-26 19:50:00 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: master
Review: https://review.opendev.org/672604
Reason: RIP, patch. It turns out that last context manager still has usefulness."
1719487,2019-08-28 20:59:39 UTC,"Reviewed:  https://review.opendev.org/672840
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c9de9c7779b1faf9d9542b3e5bd20da70067365
Submitter: Zuul
Branch:    master"
1719487,2019-07-24 22:17:57 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/672604"
1719487,2018-03-06 19:18:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/550212"
1719487,2019-07-26 00:12:26 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/672840"
1719487,2018-10-25 19:47:59 UTC,"Administrative: for some reason, the bug bot didn't add a link to the patch that was originally proposed for this launchpad:"
1719487,2018-10-25 19:19:30 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/550212"
1719494,2018-08-06 07:16:35 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/589030"
1719494,2018-08-07 09:15:52 UTC,"Change abandoned by Li Zhouzhou (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/589030"
1719494,2019-04-16 08:53:58 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1719494,2019-04-16 08:57:18 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/506532
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1719494,2019-06-27 19:58:11 UTC,"Change abandoned by Brian Haley (<email address hidden>) on branch: master
Review: https://review.opendev.org/506532
Reason: Already fixed in https://review.opendev.org/#/c/528535/"
1719494,2019-06-27 19:58:38 UTC,This was fixed in https://review.opendev.org/#/c/528535/
1719503,2017-12-07 14:50:54 UTC,This issue was fixed in the openstack/kolla-ansible 6.0.0.0b2 development milestone.
1719503,2017-09-26 07:39:03 UTC,here is the fix https://review.openstack.org/507337
1719503,2017-09-26 10:39:17 UTC,"Reviewed:  https://review.openstack.org/507337
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=b7bfe84a515452d0f912a2f62392d22af17cd1d5
Submitter: Jenkins
Branch:    master"
1719527,2020-07-09 17:17:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719535,2017-09-26 09:19:53 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1719535,2017-09-27 14:55:36 UTC,"Lubuntu , 17.10 Final Beta -  same as original report - During install (option: erase and use entire disk) the language of the slide show is incorrect; English instead of the chosen Icelandic language."
1719535,2017-09-27 15:04:20 UTC,"Some translations may be missing, we'll need to do a new translation export from LP and integrate them in ubiquity-slideshow-ubuntu."
1719535,2017-09-28 13:36:44 UTC,There aren't any translations for Dutch or Icelandic in the mentioned flavors (Budgie and Lubuntu). You will need to submit translations for the slideshows at https://translations.launchpad.net/ubuntu/artful/+sources/ubiquity-slideshow-ubuntu/+translations
1719537,2017-10-01 00:02:17 UTC,thx for the suggestion.
1719537,2017-10-16 03:00:38 UTC,"for 2), added the -t option in 4ppa60.
Gives flexibility to get the number of lines you want via a parameter.
e.g. ""sudo boot-info -t 50"" will display the last 50 lines."
1719538,2017-09-26 09:19:49 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1719560,2017-09-26 10:30:19 UTC,Fix on review: https://review.openstack.org/#/c/507269/
1719560,2017-11-02 23:48:32 UTC,This issue was fixed in the openstack/python-mistralclient 3.1.4 release.
1719560,2018-01-30 21:51:11 UTC,This issue was fixed in the openstack/python-mistralclient 3.2.0 release.
1719566,2017-12-05 16:52:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719567,2017-11-29 11:51:13 UTC,"Hi Karl,"
1719571,2017-10-13 07:10:11 UTC,"Hi, Mohit"
1719572,2017-09-26 14:29:38 UTC,chromium 61 has chromedriver 2.30.
1719572,2017-09-26 14:38:57 UTC,"Relevant commits appear to be https://chromium.googlesource.com/chromium/src/+/dac98ec90b237d6786e2a508d1e74a2d4012ff33 and https://chromium.googlesource.com/chromium/src/+/8a2bcc815371466a141910a09f7d844c00a09887, but they haven't been backported to the 61 branch, as far as I can tell."
1719572,2017-10-10 00:52:40 UTC,I can confirm that we are seeing the bug in chromedriver 2.30. When running automated tests on Trusty with this package we can no longer click buttons off screen. Would be nice to get this fixed.
1719572,2017-10-10 11:17:31 UTC,"The upcoming stable version of chromium (62, currently in the beta channel) has chromedriver 2.32."
1719582,2017-12-04 19:38:47 UTC,We started to discuss this in today's ironic meeting [1] but ran out of time. The discussion continued between Dmitry and Pavlo in irc [2].
1719588,2017-11-03 16:31:14 UTC,Syncing task from Mir.
1719603,2018-02-12 13:51:11 UTC,This issue was fixed in the openstack/heat 9.0.3 release.
1719603,2018-01-30 22:30:37 UTC,This issue was fixed in the openstack/heat 10.0.0.0b3 development milestone.
1719603,2018-01-20 04:14:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/536007"
1719603,2018-01-26 19:21:20 UTC,"Reviewed:  https://review.openstack.org/536007
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=27426e83306e55067e1a450ed0cce37533749a8c
Submitter: Zuul
Branch:    stable/pike"
1719603,2018-01-18 16:06:49 UTC,"For future readers, the issue here is in determining which attributes of the resource group we need to store in order to be able to supply this output:"
1719603,2018-01-18 07:56:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535207"
1719603,2017-09-28 06:48:45 UTC,I think this is bug most probably introduced by  I61d8e5deff45a648657ba685e033a00a492412f2. For nested stack validation we may not need to check for referenced_attrs (as resolving them may give us None).
1719603,2018-01-19 16:14:11 UTC,"Reviewed:  https://review.openstack.org/535207
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=aabb3392b30e4905e8b780bec4c819ec6058b2b6
Submitter: Zuul
Branch:    master"
1719610,2017-09-26 15:08:09 UTC,I've added a new branch (edge-master) to linux-azure repository with the preliminary rebase to 4.13:
1719610,2017-09-26 15:10:50 UTC,The preliminary 4.13 linux-azure is available at:
1719610,2017-09-26 19:58:45 UTC,New version rebased onto Ubuntu-4.13.0-12.13:
1719610,2018-01-09 19:07:33 UTC,This bug was fixed in the package linux-azure - 4.13.0-1005.7
1719624,2017-10-30 16:20:43 UTC,Can someone verify this bug is fixed with the kernel in -proposed?
1719624,2017-10-31 14:27:33 UTC,This bug was fixed in the package linux-azure - 4.11.0-1014.14
1719624,2017-10-05 13:47:54 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-October/087381.html
1719624,2017-10-03 15:08:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719624,2017-09-26 14:48:32 UTC,"Installing linux-image-extra-4.11.0-1011-azure_4.11.0-1011.11_amd64.deb solves this issue, however it shouldn't be necessary from the beginning."
1719624,2017-10-03 16:10:58 UTC,"Yes, let's add nls_utf8.ko to the regular kernel package."
1719635,2018-01-30 21:51:14 UTC,This issue was fixed in the openstack/python-mistralclient 3.2.0 release.
1719669,2017-09-26 19:01:08 UTC,"FWIW, the path is:"
1719669,2017-09-26 19:27:28 UTC,"To be clear on that path, the rack controller is running bare metal."
1719669,2017-10-06 12:46:28 UTC,"I've looked through the logs, but couldn't find anything obvious. It would really help knowing what the VM does. Do you think you could reproduce this with a VM that has a console?"
1719669,2017-10-30 15:41:27 UTC,"@Andres
Can you assign this back to Jason for additional triage"
1719669,2017-10-30 19:20:41 UTC,We haven't seen this again so there isn't anything I can do.
1719669,2017-10-31 15:11:05 UTC,"@Jason,"
1719669,2017-10-31 15:14:27 UTC,"Can we please leave ""cannot reproduce"" bugs as incomplete? they will expire over time if we can't reproduce them.  Marking them invalid makes them no longer show up in searches."
1719669,2019-09-19 11:54:01 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1719670,2019-07-26 00:54:36 UTC,Build was changed (merged into all branches on 2018-09-17) to not require the startup directory to be installed at all.
1719670,2017-09-26 15:40:16 UTC,"Not worth doing in 3.14, but I will add this to the 3.15 branch."
1719670,2017-09-27 07:01:26 UTC,"Careful.
This is one of the directories that are source as well as installation (configure, startup, iocBoot), so that the case of INSTALL_LOCATION != TOP has to be treated differently (install and remove on distclean) from INSTALL_LOCATION == TOP (neither install nor remove)."
1719670,2018-07-19 23:12:07 UTC,The need for this will be going away very soon.
1719682,2017-10-03 22:21:48 UTC,User experience with 'juju ssh' needs to be re-visited.
1719688,2017-10-11 13:05:45 UTC,"This is a feature request, added to wish list if someone wants to work on it"
1719688,2019-03-27 10:01:18 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/639157
Reason: Pavel and I discussed and agreed this is not necessary - it can be configured."
1719691,2017-10-19 20:51:56 UTC,"Confirmed on 17.10, that's still an issue"
1719691,2017-10-19 20:52:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1719700,2018-01-17 18:55:31 UTC,"Can you elaborate the problem more and provide logs?
From the description there is almost nothing, but there's something wrong."
1719702,2018-05-14 11:04:11 UTC,This change was made by a bot.
1719708,2018-02-26 11:57:24 UTC,"already stable/queens branch was cut with zuulv3  and about to start rocky cycle.
So we should check it with stable/queens cycle."
1719709,2017-09-27 21:57:16 UTC,"Immediate feedback: What do we do if the remote changes? That is, the VCS
moves? Or if the value is different between branches? Presumably only use
it if it has data, as well (it's possible for e.g., debian/watch to be
wrong, so I'd imagie upstreams can disappear.)"
1719714,2017-09-28 18:20:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/508261"
1719714,2017-09-28 18:20:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/508262"
1719714,2017-10-23 12:49:27 UTC,"Change abandoned by Jan Zerebecki (<email address hidden>) on branch: master
Review: https://review.openstack.org/508261"
1719714,2017-12-07 18:43:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/526477"
1719714,2017-12-28 00:18:08 UTC,"Reviewed:  https://review.openstack.org/508262
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=895e3be3fee74bf71a80e9ccad482fdd408fa42f
Submitter: Zuul
Branch:    master"
1719714,2018-01-26 00:44:28 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1719714,2018-02-02 06:41:12 UTC,"Reviewed:  https://review.openstack.org/526477
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c3eb6ea3f6f31ae9473d0d2a4fa3f7c3a590d5f2
Submitter: Zuul
Branch:    stable/pike"
1719714,2018-02-15 23:53:50 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1719715,2017-09-26 20:12:22 UTC,Answer from LP team: use distro.current_series instead. Leaving the bug open for Launchpad API cleanup.
1719715,2017-09-26 18:58:29 UTC,https://launchpad.net/+apidoc/devel.html#distro_series says the status can be:
1719715,2017-09-26 19:00:29 UTC,getDevelopmentSeries
1719724,2017-09-26 21:45:18 UTC,I believe this update should have a FeatureFreeze exception. The current version in artful is non-functional due to the broken cron scripts.
1719724,2017-09-29 21:27:44 UTC,"The Debian bugs for the issues with 1.2.2 are here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850776
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874182"
1719724,2017-10-12 15:04:56 UTC,Is this update going to make artful?
1719724,2018-01-07 00:57:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719724,2018-01-07 00:59:04 UTC,"I just hit this as well after I finally noticed that I've had no backups since 28 Oct when I upgraded to Artful. It means I have only 1 hour of history (4x15 ""frequent""s), mostly defeating the point of this package. +1 to pulling down the fix or else reverting to the version in Zesty, which did work."
1719724,2018-04-05 17:17:31 UTC,(cleaning up ~ubuntu-release bugs)
1719724,2018-04-05 17:43:09 UTC,"Most of the changes between 1.2.2 and 1.2.4 are related to fixing this bug.
""make --quiet really quiet"" and it's merge are the only things not related."
1719729,2019-07-11 04:17:53 UTC,[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]
1719729,2017-09-26 20:24:50 UTC,apport information
1719729,2019-05-11 14:51:11 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1719729,2017-09-26 20:27:00 UTC,"When running apport -p chromium-browser <this-bug-#>, I get this error in the terminal (and end up with a popup screen asking me to send bug info to the developers):"
1719729,2017-09-26 20:24:48 UTC,apport information
1719729,2017-09-26 20:24:37 UTC,apport information
1719729,2017-09-26 20:24:44 UTC,apport information
1719729,2017-09-26 20:24:42 UTC,apport information
1719729,2017-09-26 20:24:39 UTC,apport information
1719729,2017-09-26 20:24:35 UTC,apport information
1719729,2017-09-26 20:24:46 UTC,apport information
1719730,2017-11-16 19:59:22 UTC,This issue was fixed in the openstack/nova 14.0.10 release.
1719730,2017-11-16 02:26:24 UTC,"Reviewed:  https://review.openstack.org/517868
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6b7b4aa4a5d19a648556a9076f61f4e87f4710e0
Submitter: Zuul
Branch:    stable/newton"
1719730,2017-11-15 01:06:44 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1719730,2017-11-14 20:28:23 UTC,"Reviewed:  https://review.openstack.org/517860
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=96ad6043bbacf47b29d46288ca0d755541eb1d0e
Submitter: Zuul
Branch:    stable/ocata"
1719730,2017-11-06 06:53:46 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/517868"
1719730,2017-11-06 05:33:06 UTC,"Bug 1675676 has the same failure but from a different scenario, and goes back to at least Newton."
1719730,2017-10-25 19:22:23 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1719730,2017-10-24 12:42:07 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1719730,2017-10-07 05:37:22 UTC,"Reviewed:  https://review.openstack.org/509766
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d288132dca7cc76dfc6679eda17bb8fcc62577de
Submitter: Jenkins
Branch:    stable/pike"
1719730,2017-10-05 12:52:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/509766"
1719730,2017-10-05 00:58:23 UTC,"Reviewed:  https://review.openstack.org/507938
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9d6632a67d91fb3c5145c14ac38011e919d6d8c0
Submitter: Jenkins
Branch:    master"
1719730,2017-09-27 17:35:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507938"
1719730,2017-09-26 20:34:26 UTC,"Since https://review.openstack.org/#/c/469037 was made in pike, this is a regression in the pike release."
1719730,2017-11-06 05:29:05 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/517860"
1719731,2017-10-10 21:44:03 UTC,"I managed to fix the bug in XFCE power manager (following a tutorial online, just a string to edit), however the issue still persists."
1719731,2017-10-05 15:55:41 UTC,Also is there any chance that the error is linked to https://ubuntuforums.org/showthread.php?t=2371537 where I reported that I cannot connect to a specific wifi (I can on Windows 10 though) and a specific router?
1719731,2017-09-26 20:32:39 UTC,The bug is Confirmed
1719731,2017-09-26 21:00:43 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1719731,2017-10-05 15:44:50 UTC,Hello sorry for the late reply.
1719731,2017-09-26 20:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1719744,2017-11-08 02:37:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1719744,2020-03-17 10:09:18 UTC,"This is a very old bug report for an unsupported version. Does this bug exist in the latest version? Please note, that GNOME Recipes 2.0.4 is released on 2020-03-06
https://gitlab.gnome.org/GNOME/recipes/-/tags/2.0.4"
1719747,2017-09-27 02:24:06 UTC,can you correct me if my interpretation of your setup is wrong?
1719747,2017-09-27 02:27:40 UTC,"Or you could install the apparmor package, and have apparmor confinement of the snap on the fedora system."
1719747,2017-09-27 02:27:52 UTC,"Also, what is the output of 'snap version'?"
1719747,2017-09-27 21:18:14 UTC,"Thank you for your reply! You're right, the host is Ubuntu, 16.04.2. I should've mentioned that."
1719749,2017-09-26 23:11:05 UTC,"StacktraceTop:
 touch_handle_motion (data=0x555df90d8020, wl_touch=<optimized out>, time=1983443, id=<optimized out>, x=57391, y=130517) at ././gdk/wayland/gdkdevice-wayland.c:2480
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffffd8fe910, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffffd8fe9e0) at ../src/x86/ffi64.c:525
 wl_closure_invoke (closure=closure@entry=0x555df912bb10, flags=flags@entry=1, target=<optimized out>, target@entry=0x555df90d3910, opcode=opcode@entry=2, data=<optimized out>) at ../src/connection.c:935
 dispatch_event (display=display@entry=0x555df8e051f0, queue=<optimized out>) at ../src/wayland-client.c:1310"
1719753,2019-12-11 04:45:05 UTC,Migrated to:  https://gitlab.com/inkscape/inkscape-web/issues/461
1719758,2020-05-08 17:53:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719765,2017-09-27 13:51:52 UTC,I filed a bug according this issue: https://bugzilla.gnome.org/show_bug.cgi?id=788239
1719765,2017-09-27 14:24:19 UTC,thanks
1719765,2017-09-27 04:11:22 UTC,gnome calendar also affected. So can't be an evolution only bug.
1719765,2017-09-27 12:58:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1719769,2017-09-27 03:46:39 UTC,"If port's security group rules flows recreated, there will be blink (https://github.com/openstack/neutron/blob/master/neutron/agent/linux/openvswitch_firewall/firewall.py#L506)"
1719769,2018-05-11 14:33:34 UTC,This looks like a duplicate of https://bugs.launchpad.net/neutron/+bug/1708731 of which a fix has been release.  Can you confirm that in your environment?
1719769,2018-08-31 07:39:01 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1719769,2018-08-31 07:39:10 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/507725
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1719769,2017-09-27 03:23:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507725"
1719772,2017-09-27 03:37:22 UTC,I'm running Project Kde 16.04
1719772,2017-11-16 01:54:19 UTC,still not fixed in Ubuntu 18.04
1719787,2019-08-31 06:49:13 UTC,https://tox.readthedocs.io/en/latest/config.html
1719797,2018-10-23 17:56:34 UTC,"Hello Merlijn, or anyone else affected,"
1719797,2018-12-11 16:29:35 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.8
1719797,2018-12-03 23:58:27 UTC,"The verification of the Stable Release Update for fwupd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1719797,2018-12-03 23:58:18 UTC,This bug was fixed in the package fwupd - 1.0.9-0ubuntu2
1719797,2018-11-28 18:00:41 UTC,I just downgraded an XPS 9370 and then upgraded it again using gnome-software 3.28.1-0ubuntu4.18.04.8 and it works like I expected.
1719797,2018-11-21 09:03:15 UTC,"I faked it previously by manually downgrading my bios (downloading the previous version from the bios vendor, putting it on a FAT32 USB stick and using the upgrade option in the bios setup), after which the software center shows the update again."
1719797,2018-11-21 08:53:11 UTC,@ Robert - until there is another fw update I don't think I can.  Do you know of a way to mock/fake it?
1719797,2018-11-20 23:24:05 UTC,Will - can you confirm this is still fixed in 3.28.1-0ubuntu4.18.04.7 ?
1719797,2018-10-30 11:11:05 UTC,"On Bionic, I'm running:"
1719797,2018-10-29 21:34:03 UTC,"Hello Merlijn, or anyone else affected,"
1719797,2018-10-23 18:40:13 UTC,I've tested the fwupd half of this SRU (couldn't test the gnome-software as it's not yet in place).  The fwupd half works properly.
1719797,2018-10-23 16:27:48 UTC,"Hello Merlijn, or anyone else affected,"
1719797,2018-11-20 23:41:10 UTC,"Hello Merlijn, or anyone else affected,"
1719797,2018-10-15 21:04:45 UTC,"fwupd
------
This has been fixed upstream in the 1.1.3 release, so marking the development release task complete.
The 1.0.9 SRU bug for bionic is here: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999"
1719797,2017-10-22 12:52:49 UTC,There seems to be two issues:
1719797,2017-10-22 12:53:57 UTC,I'm using default Ubuntu 17.10; DE is Gnome. This happens both in Xorg and in wayland session.
1719797,2017-10-23 09:21:15 UTC,"the log has that warning
""Calling org.gnome.SessionManager.Reboot failed: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Operation was cancelled"""
1719797,2017-10-27 21:30:40 UTC,I've filed that issue upstream.
1719797,2017-10-27 21:31:09 UTC,"I suspect it to actually be gnome-session is the problem, but let's see what they say."
1719797,2018-01-25 14:58:29 UTC,That upstream issue has migrated to https://gitlab.gnome.org/GNOME/gnome-software/issues/253.  It seems Launchpad can't track it anymore.
1719797,2018-10-17 20:29:55 UTC,Change queued up for gnome-software 3.28.1-0ubuntu4.18.04.5 SRU
1719797,2018-05-21 13:45:23 UTC,"Description of problem:
When gnome-software finds a firmware update, and you hit the update button, it is unclear whether the update succeeded, and also unclear that you need to reboot your machine to actually apply the update."
1719797,2018-08-01 07:48:06 UTC,This is the actual upstream issue. The reboot failed log seems to be a red herring.
1719797,2018-09-12 13:46:10 UTC,FYI this is upstream issue https://gitlab.gnome.org/GNOME/gnome-software/issues/341
1719797,2018-09-17 12:42:25 UTC,This issue has been fixed upstream.  It requires fixes in both gnome-software and fwupd.
1719797,2018-09-17 15:44:12 UTC,"This is fixed upstream, but will require fixes in both gnome-software and fwupd."
1719797,2017-10-19 20:47:12 UTC,"Thank you for your bug report. So the issue there is that it fails to restart the machine when acking the dialog that is supposed to do that, right?
What desktop environment are you using? Could you add your syslog after getting the problem?"
1719803,2018-01-24 04:51:29 UTC,"Copy, Cut and Insert shortcuts are broken in Pix but work in gThumb."
1719803,2017-10-17 07:16:06 UTC,Last watched video frame screen covering problem has solved after kernel update:
1719803,2017-10-10 08:23:33 UTC,"Copy, Cut and Insert shortcuts are broken since Sonya update."
1719804,2017-09-27 08:31:37 UTC,Per-model basis is also nice to have. Something like:
1719804,2017-10-03 22:24:27 UTC,Both suggestions - per model and per bundle - are great. I'll add these to our wishlist and will flag it to the team.
1719809,2017-10-02 12:03:51 UTC,"I'm also trying with pure API via curl. With administrative rights I can list deleted servers but I cannot list actions for them. I get ""Instance not found"" error
curl -s -H ""X-Auth-Token:MY_TOKEN"" ""https://openstack_url:8774/v2/TENANT_ID/servers/DELETED_SERVER_ID/os-instance-actions""
I also checked DB for that. Actions for this servers are properly existing in instance actions table..."
1719809,2017-09-28 14:12:53 UTC,"One comment:
One of the questions is: Should I get list of servers for given project and period of time relying on what I get from nova.usage.get or nova.servers.list ?  It may happend that in given period of time one of the servers will be shut down and will not appear on servers.list and thus I will not be able to check  its instance-action-list (I will get error saying server with this name or id doesn't exist) to calculate shelve/unshelve and stop/start periods for further cost calculations. I hope I made myself clear and you see my point...
I think (maybe I'm missing that) there is lack of functionality allowing to ask for instance-action-list on DELETED servers......"
1719815,2017-10-03 12:19:03 UTC,"Hi there,"
1719815,2017-10-03 13:20:54 UTC,"Hi,"
1719815,2019-07-07 17:16:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669579"
1719815,2019-08-31 07:57:09 UTC,"Hello,"
1719815,2019-09-03 09:38:54 UTC,"Reviewed:  https://review.opendev.org/669579
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=f6321bfc89d904019cde54b8ff292d37a3ff2cd4
Submitter: Zuul
Branch:    master"
1719828,2018-03-16 22:03:56 UTC,"I see this too, but the process freezes up (does not respond to input) instead of crashing. I attached gdb to a process that's frozen up in this state and here's what I see:"
1719835,2017-10-09 18:00:58 UTC,This can be added. Any volunteers?
1719835,2017-10-10 09:52:51 UTC,"I wonder, this may come as an ""almost free"" feature when we use the common classifier framework (classifier descriptions support this scenario I think). Though I still have to get started on the POC code to use CCF instead of current flow classifiers..."
1719837,2019-10-28 19:26:49 UTC,hey haobing I am going to close this defect for inactivity please let us know if this is still happening can you please add a manila version that was test and all relevant logs so we can assiste you with this issue
1719846,2017-09-27 11:25:17 UTC,"More information:
administrador@conserxeria:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial
administrador@conserxeria:~$ uname -a
Linux conserxeria 4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1719846,2017-09-27 12:38:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1719860,2020-03-19 10:22:00 UTC,"I am also seeing the similar behaviourwith swift (Rocky version, EC Cluster)"
1719860,2020-03-19 17:35:22 UTC,There's a bit of info on reproducing this on the duplicate bug 1719860
1719860,2020-04-27 23:26:10 UTC,"Reviewed:  https://review.opendev.org/722128
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=69b8165cd87693f077a2385d9b6d53a7f459b098
Submitter: Zuul
Branch:    master"
1719860,2020-05-15 16:10:04 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/728491"
1719860,2020-05-18 23:22:13 UTC,"Reviewed:  https://review.opendev.org/728491
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=414ca6bb6c7ffe12a1f7c4f65526bb0bf98b4b49
Submitter: Zuul
Branch:    feature/losf"
1719864,2017-09-28 13:39:15 UTC,"The patch  https://review.openstack.org/508113 seems to fix this. The bug was in bifrost, in the yaml format"
1719864,2017-12-06 09:44:00 UTC,Cherry picked to stable/pike: https://review.openstack.org/#/c/526007
1719866,2018-01-24 22:26:12 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1447
1719870,2017-09-27 16:03:46 UTC,"PS > Get-VHD .\VM.vhdx
ComputerName            : Server1
Path                    : \VM.vhdx
VhdFormat               : VHDX
VhdType                 : Fixed
FileSize                : 107378376704
Size                    : 107374182400
MinimumSize             : 107374182400
LogicalSectorSize       : 4096
PhysicalSectorSize      : 4096
BlockSize               : 0
ParentPath              :
DiskIdentifier          : 53fd4aa7-562e-4bed-bc1c-2db71222e07e
FragmentationPercentage : 0
Alignment               : 1
Attached                : False
DiskNumber              :
Key                     :
IsDeleted               : False
Number                  :
PS > & 'C:\Program Files\qemu\qemu-img.exe' convert -O qcow2 .\VM.vhdx .\VM.qcow2
Assertion failed!
Program: C:\Program Files\qemu\qemu-img.exe
File: /home/stefan/src/qemu/repo.or.cz/qemu/ar7/block/io.c, Line 1034
Expression: !qiov || bytes == qiov->size
PS > & 'C:\Program Files\qemu\qemu-img.exe' info .\VM.qcow2
image: .\VM.qcow2
file format: qcow2
virtual size: 13G (13421772800 bytes)
disk size: 1.4G
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false"
1719870,2017-10-11 10:30:55 UTC,"Bug is reproducible with setting VHDX Fixed Logicalsectorsize to 4096bytes

>10G image created reflects as 1.2G virtual size in Qemu-img


PS F:\> new-vhd -path test.vhdx -BlockSizeBytes 134217728 -SizeBytes 10737418240 -Fixed -LogicalSectorSizeBytes 4096
ComputerName            : XXXX
Path                    : F:\test.vhdx
VhdFormat               : VHDX
VhdType                 : Fixed
FileSize                : 10741612544
Size                    : 10737418240
MinimumSize             :
LogicalSectorSize       : 4096
PhysicalSectorSize      : 4096
BlockSize               : 0
ParentPath              :
DiskIdentifier          : dfa84293-86f2-4ddf-aaff-14c04dae5df9
FragmentationPercentage : 0
Alignment               : 1
Attached                : False
DiskNumber              :
Key                     :
IsDeleted               : False
Number                  :
PS F:\> C:\temp\qemu-img\qemu-img.exe info .\test.vhdx
image: .\test.vhdx
file format: vhdx
virtual size: 1.2G (1342177280 bytes)
disk size: 10G
cluster_size: 134217728"
1719870,2020-09-26 16:57:50 UTC,Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
1719870,2020-11-26 04:17:19 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1719870,2017-09-27 12:27:29 UTC,"Command capture,"
1719889,2018-06-27 08:39:43 UTC,"Hi,
it seems there were similar issues discussed in bug 1307778
They got resolved groupds with no GID in AD, but still ended up having the issue around S-1-18-1 that you reported."
1719889,2019-01-09 14:11:39 UTC,"Also check your group mapping, using ""net groupmap list"""
1719889,2019-01-09 14:39:42 UTC,net groupmap list only shows Administrators and Users.
1719889,2019-01-10 14:07:36 UTC,"> the problem does not exist on 18.04.
"
1719902,2019-11-13 13:19:25 UTC,images are now built using tripleo-buildimage-overcloud-full-centos-7 and tripleo-buildimage-overcloud-full-rhel-8
1719902,2019-02-19 13:53:13 UTC,Is this still an issue?
1719902,2019-11-13 08:03:51 UTC,Is this still an issue?
1719902,2017-10-06 02:12:21 UTC,"Reviewed:  https://review.openstack.org/508868
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=a38e9635bb9eb8166fad6d72d881118cd3376767
Submitter: Jenkins
Branch:    master"
1719902,2017-09-27 20:20:53 UTC,"So, agreed this is not how customers would install. We have the configs in place to take a base os image [1] and install with the images provided by rhosp-director-images.rpm.   This is a much longer install and I would argue that we don't need to do it in every ci job. Keep in mind that baremetal jobs are also in place for the same reason."
1719902,2017-10-02 12:47:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/508868"
1719902,2017-10-02 12:50:49 UTC,https://review.openstack.org/508868 should be all we need to allow this to work via downstream release config files (so we dont need some downstream specific thing in the role)
1719902,2017-09-27 17:35:36 UTC,I'm not sure this is valid as it could lead to issues where packages are there and are not properly installed by the undercloud process.  Techincally the undercloud install should start from a stock (empty) image and the install process should handle everything.  If we are assuming the undercloud has software installed this might be an area where customers won't have something that we have.
1719902,2017-09-27 20:46:33 UTC,"As long as it's not the primary method for installation, we have additional jobs that cover just the install running in the same gate, and it's appropriately documented then it might be ok. The problem is that jobs that use this method will reduce our coverage and could possibly allow for regressions. Additionally as we move to trying to replace the overcloud image with a stock image this may not be beneficial in the long term."
1719915,2017-09-27 15:06:32 UTC,I cannot reproduce this on master locally. In the other hand both patches [1][2] that were hit by this failure according to logstash [3] are failing constantly for me locally. So I don't think we saw this race on the master if the any race at all.
1719915,2017-12-18 12:51:44 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1719915,2017-12-01 11:10:52 UTC,"Reviewed:  https://review.openstack.org/508872
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aabf0b0bf60c513accc32a5084bb42093b65eb31
Submitter: Zuul
Branch:    stable/pike"
1719915,2017-10-02 13:08:37 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/508872"
1719915,2017-10-02 12:03:13 UTC,"Reviewed:  https://review.openstack.org/507911
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8a435c081df1653620cff5918ea66643d3487fd7
Submitter: Zuul
Branch:    master"
1719915,2017-10-24 12:42:14 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1719915,2017-09-27 15:38:54 UTC,Nova destroys the instance object in the compute/manager [1] _before_ removes the allocation [2]. This is the root cause of the race condition at instance delete. Fortunately we have the instance.delete notification emitted[3] _after_ the allocation is deleted so we can modify the _wait_until_deleted to wait for the deleted notification as well.
1719915,2017-09-27 15:21:47 UTC,"So these race happens at the delete of the instance:
Captured traceback:
2017-09-27 13:53:01.197304 | ~~~~~~~~~~~~~~~~~~~
2017-09-27 13:53:01.197349 |     b'Traceback (most recent call last):'
2017-09-27 13:53:01.197462 |     b'  File ""/home/jenkins/workspace/gate-nova-tox-functional-py35-ubuntu-xenial/.tox/functional-py35/lib/python3.5/site-packages/mock/mock.py"", line 1305, in patched'
2017-09-27 13:53:01.197510 |     b'    return func(*args, **keywargs)'
2017-09-27 13:53:01.197625 |     b'  File ""/home/jenkins/workspace/gate-nova-tox-functional-py35-ubuntu-xenial/nova/tests/functional/test_servers.py"", line 2426, in test_live_migrate_delete'
2017-09-27 13:53:01.197676 |     b'    server, source_rp_uuid, dest_rp_uuid)'
2017-09-27 13:53:01.197786 |     b'  File ""/home/jenkins/workspace/gate-nova-tox-functional-py35-ubuntu-xenial/nova/tests/functional/test_servers.py"", line 1331, in _delete_and_check_allocations'
2017-09-27 13:53:01.197850 |     b""    'DISK_GB': 0}, source_usages)""
2017-09-27 13:53:01.197965 |     b'  File ""/home/jenkins/workspace/gate-nova-tox-functional-py35-ubuntu-xenial/.tox/functional-py35/lib/python3.5/site-packages/testtools/testcase.py"", line 411, in assertEqual'
2017-09-27 13:53:01.198019 |     b'    self.assertThat(observed, matcher, message)'
2017-09-27 13:53:01.198132 |     b'  File ""/home/jenkins/workspace/gate-nova-tox-functional-py35-ubuntu-xenial/.tox/functional-py35/lib/python3.5/site-packages/testtools/testcase.py"", line 498, in assertThat'
2017-09-27 13:53:01.198173 |     b'    raise mismatch_error'
2017-09-27 13:53:01.198220 |     b'testtools.matchers._impl.MismatchError: !=:'
2017-09-27 13:53:01.198273 |     b""reference = {'DISK_GB': 0, 'MEMORY_MB': 0, 'VCPU': 0}""
2017-09-27 13:53:01.198327 |     b""actual    = {'DISK_GB': 1, 'MEMORY_MB': 512, 'VCPU': 1}""
2017-09-27 13:53:01.198354 |     b''
2017-09-27 13:53:01.198381 |     b''"
1719915,2017-09-27 15:14:24 UTC,"OK, that is a different failure than what was posted on the bug report. This failure did hit some unrelated changes on the gate."
1719915,2017-09-27 15:08:38 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22%5Bnova.api.openstack.requestlog%5D%20127.0.0.1%20%5C%5C%5C%22DELETE%20%2Fv2.1%2F%5C%22%20AND%20message%3A%5C%22%2Fmigrations%2F1%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d
1719915,2017-09-27 16:03:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507911"
1719925,2017-09-27 15:59:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/507910"
1719927,2020-03-10 14:36:34 UTC,A workaround is to do the change to /etc/landscape/client.conf directly and just restart the landscape client. Doing it this way will not register a new copy of the client if it already exists.
1719931,2017-09-28 11:08:04 UTC,"Reviewed:  https://review.openstack.org/508066
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=efa09fafb17964126000274e5fb2317211c72df6
Submitter: Jenkins
Branch:    stable/newton"
1719931,2017-10-25 21:52:20 UTC,"Reviewed:  https://review.openstack.org/508065
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=9664b363f1172ea96e555b58b09a44f37bc027c1
Submitter: Zuul
Branch:    stable/ocata"
1719931,2017-09-28 11:37:31 UTC,"Reviewed:  https://review.openstack.org/508063
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=8aa7fc80e6c8fdcf422e24ec6b350878c0312853
Submitter: Jenkins
Branch:    stable/pike"
1719931,2017-09-28 06:46:14 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/508066"
1719931,2017-09-28 06:45:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/508063"
1719931,2017-09-28 06:38:45 UTC,Fix committed and merged https://review.openstack.org/#/c/507897
1719931,2017-09-27 18:18:47 UTC,"Reviewed:  https://review.openstack.org/507897
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=442a435c0463d1c641e62bf0fac3c8506c90349d
Submitter: Jenkins
Branch:    master"
1719931,2017-09-27 15:31:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/507897"
1719931,2017-09-28 06:46:02 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/508065"
1719933,2018-07-31 18:28:45 UTC,"Reviewed:  https://review.openstack.org/586048
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=72e4c4c8d7fb146862b899337626485dad10f15b
Submitter: Zuul
Branch:    master"
1719933,2018-09-27 12:01:34 UTC,"Change abandoned by Chris Dent (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/591042"
1719933,2018-09-27 12:01:02 UTC,"Change abandoned by Chris Dent (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/590745"
1719933,2018-09-24 14:47:06 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1719933,2018-08-10 18:37:02 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/591042"
1719933,2018-08-10 10:57:37 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/590745"
1719933,2018-08-10 09:52:43 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.
1719933,2018-08-09 22:35:35 UTC,"Reviewed:  https://review.openstack.org/588569
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=66a47b7623035cff38a12fdace9a325bbfdd9a14
Submitter: Zuul
Branch:    stable/queens"
1719933,2018-08-03 13:41:59 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/588569"
1719933,2018-07-31 03:28:29 UTC,"Sure Chris. Sorry, I was not feeling well so was on leave for last two days."
1719933,2017-10-02 14:49:18 UTC,"FYI, I've been trying to recreate this here to get the logs from a failure:"
1719933,2018-07-26 11:06:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586048"
1719933,2018-07-26 08:42:50 UTC,"It turns out that allocation write contention on resource provider generation is a relatively significant issue when launching many VMs to one or a very small number of compute nodes, as might happen in a clustered environment like the vmwareapi virtdriver."
1719933,2018-02-09 14:13:03 UTC,"We're not sure if this is a bug, or if it is, what the proper solution should be. We have a discussion about our use of generations to ensure integrity scheduled for the Dublin PTG, and this issue will be part of that."
1719933,2017-10-09 15:20:04 UTC,"Change abandoned by Jay Pipes (<email address hidden>) on branch: master
Review: https://review.openstack.org/509034"
1719933,2017-10-03 12:13:24 UTC,"I see, yes, Chris, that's a good point."
1719933,2017-10-03 10:58:04 UTC,"Isn't that retry decorator only retrying on db api errors, notably deadlock? When generation conflict happens, ConcurrentUpdateDetected is raised, which is not a db api error."
1719933,2017-10-03 00:08:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509034"
1719933,2017-10-02 22:30:14 UTC,I'll remove the no longer relevant comment in a patch shortly.
1719933,2017-10-02 22:29:57 UTC,"OK, so this is indeed invalid. We do a server-side retry on creating allocations already:"
1719933,2017-10-02 14:52:20 UTC,Gonna take this one as I'm cleaning up resource_provider.py module in a patch series right now...
1719933,2018-07-27 14:54:34 UTC,"Diga, my apologies forgetting to this before you. I had to rush to work on this because we encountered internally at work that would be solved by having a solution to it and it was a critical issue, so I rushed something out at https://review.openstack.org/#/c/586048/"
1719945,2020-02-25 14:57:52 UTC,"I see ""ERROR: Unable to find display on any available system"" when starting with Wayland. Is there and update on this issue?"
1719945,2018-11-28 23:28:52 UTC,"Currently  with hybrid systems a wayland session is presented when nvidia drivers are in use though the user is logged into wayland using the Intel gpu.
So the fact that while in wayland the user can't use nvidia-settings > prime profiles to *actually* switch back to the Intel gpu makes this bug more of an issue."
1719945,2017-10-06 04:25:31 UTC,"It's certainly possible to log out, log in to an Xorg session, and then log out again/reboot to switch to NVIDIA. *If* you know that's what you need to do."
1719945,2017-10-05 04:59:36 UTC,"While I can certainly confirm, what is the use case?
It would seem only useful when in a wayland session to switch from the intel profile to the nvidia one before rebooting to an xorg session. I guess that could save a little time/effort."
1719949,2018-01-25 09:38:50 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3745
1719959,2017-09-27 18:02:37 UTC,Looks like this issue
1719960,2017-09-27 19:49:17 UTC,"Printer: LaserJet 1018
OS: Linux Mint 18.2
hplip: 3.17.9"
1719960,2017-09-30 08:56:23 UTC,Its working today. It could be a problem with the servers.
1719960,2017-11-30 08:48:35 UTC,"Hi Bruno,"
1719964,2017-09-29 08:32:52 UTC,"Agreed - the charm knows whether its in a HA deployment, so should add the requirement for either a ceph of swift backend to the required interfaces list that's used to assess status in this scenario."
1719964,2017-09-29 08:33:08 UTC,Triaging as 'Low' as this is a usability issue.
1719966,2017-10-25 19:22:27 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1719966,2017-10-24 12:42:10 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1719966,2017-09-28 00:05:06 UTC,"Reviewed:  https://review.openstack.org/507948
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b1591d1080e4dbfbaf5351e009efa3abd11d88d4
Submitter: Jenkins
Branch:    master"
1719966,2017-09-27 19:55:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/507965"
1719966,2017-09-27 17:59:53 UTC,We were always joining on flavor in the database:
1719966,2017-09-28 06:06:50 UTC,"Reviewed:  https://review.openstack.org/507965
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bdd8b58351e9ebe69f1c5ab52bb5085e03be5202
Submitter: Jenkins
Branch:    stable/pike"
1719970,2017-09-28 18:21:03 UTC,Fix has been verified.
1719970,2017-09-28 20:59:32 UTC,This bug was fixed in the package linux-aws - 4.4.0-1037.46
1719970,2017-09-29 16:14:04 UTC,The package has been published and the bug is being set to Fix Released
1719978,2017-09-28 14:14:06 UTC,"As an example of the problem that this would solve, see
 https://gist.github.com/smoser/e917b2873aff767cb454cb0513a564a4
that was written to help someone test proposed with maas."
1719978,2019-09-19 12:04:42 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1719985,2017-10-19 20:44:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1719985,2018-05-03 00:16:33 UTC,"The gnome-software-plugin-flatpak was known to have issues in 3.26, would you be able to try again with Ubuntu 18.04 + gnome-software 3.28 ?"
1719985,2019-10-31 20:04:11 UTC,"It's not showing any updates for me in 19.10, and hasn't for quite some time."
1719985,2020-12-13 17:37:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1719986,2017-11-17 22:34:09 UTC,"This would potentially affect sites using pg_upgrade, but not those using pg_dumpall to perform the upgrade."
1719986,2017-11-18 05:07:36 UTC,"Another option would be to fork the upstream unaccent.rules file and distribute it with Evergreen, where we would then control if and when it changed."
1719998,2017-10-09 13:54:29 UTC,Thank you for the reasonable feature request.
1719998,2018-01-25 09:39:05 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2508
1720005,2020-10-30 16:33:00 UTC,Marking this as a duplicate of bug 1570072 as the fix is contained therein for the TPAC
1720005,2020-10-29 21:07:08 UTC,"Oh, good catch, I didn't realize that wasn't in the Bootstrap OPAC. I'd probably do a new bug for clarity."
1720005,2020-10-29 18:53:34 UTC,"Michele, did the work in bug 1570072 resolve this?"
1720005,2020-10-29 20:58:52 UTC,"Terran, yes, it is resolved in the TPAC, Patrons can see and update their notification preferences hold by hold for open holds."
1720005,2018-11-01 21:48:29 UTC,This should be resolved as part of the work being done for https://bugs.launchpad.net/evergreen/+bug/1570072
1720010,2018-02-03 11:32:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720028,2017-09-27 23:15:25 UTC,"Sorry, I was able to reproduce this error only three times in succession, when I first switched the GUI from two adaptive-size boxes, to a single box; the card displayed at the time had not yet shown the answer, and the pending Answer was a GIF image."
1720028,2017-09-28 00:14:44 UTC,"Second comment: I am continuing to have this problem and can two elements which must occur together: BOTH (1) Q&A are shown in a single box, AND (2) the size of non-Latin characters is increased (in my case, by 14 points; I haven't tried other sizes). If the display is two boxes, OR if non-Latin character size is not increased, then the problem does not occur."
1720028,2017-09-28 11:33:53 UTC,Can you try this version? Should be fixed there..
1720028,2017-09-28 17:12:46 UTC,"Thanks, Peter. That solved the problem."
1720036,2017-12-17 21:52:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720042,2017-09-28 02:23:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720042,2017-10-06 07:01:07 UTC,"4.4.0-1038.47 - aws
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1720042,2017-10-10 14:28:39 UTC,This bug was fixed in the package linux-aws - 4.4.0-1038.47
1720042,2017-10-11 08:34:39 UTC,The package has been published and the bug is being set to Fix Released
1720049,2017-09-28 20:11:58 UTC,This appears to be due to the removal of register_argparse_arguments from:
1720049,2017-09-28 20:13:29 UTC,keystoneauth code that registers and uses the correct environment variables:
1720050,2018-08-08 08:01:03 UTC,"Tracking in:
https://errors.ubuntu.com/problem/2bee46d654bf98b7f32986cb50b0688c07eb4f45"
1720050,2020-11-16 08:18:46 UTC,Zero crashes after 18.04 so consider it fixed.
1720050,2017-09-28 03:57:55 UTC,"StacktraceTop:
 ?? ()
 ?? ()
 g_task_return_now (task=0x5634045c2000) at ../../../../gio/gtask.c:1145
 complete_in_idle_cb (task=0x5634045b3030) at ../../../../gio/gtask.c:1159
 g_main_dispatch (context=0x563404303580) at ../../../../glib/gmain.c:3148"
1720050,2018-08-08 08:00:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720057,2018-02-26 12:33:48 UTC,The reason of the bug is clear and triaged as high.
1720057,2018-06-01 08:35:50 UTC,"Hi folks,"
1720057,2019-03-22 05:57:00 UTC,"Change abandoned by Yenuganti Vasudha (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/634197"
1720060,2017-10-10 14:29:43 UTC,In progress of making a TaaS installation document will update
1720060,2018-06-03 22:09:22 UTC,"Are you using a distro with the taas package available?
If so, install it"
1720060,2019-08-14 15:18:25 UTC,"Hello! I'm trying to deploy taas and i have found instruction:
https://docs.openstack.org/openstack-helm/latest/install/plugins/deploy-tap-as-a-service-neutron-plugin.html
But, i have deploy openstack over kolla-ansible(all-in-one). Daashboard and neutron is docker containers.
How to add Taas plugin in my case?"
1720080,2017-12-26 21:16:12 UTC,"As upstream bug mentions http://dev.mysql.com/doc/refman/5.6/en/replication-features-timezone.html: ""By default, master and slave servers assume that they are in the same time zone. If you are replicating between servers in different time zones, the time zone must be set on both master and slave. Otherwise, statements depending on the local time on the master are not replicated properly, such as statements that use the NOW() or FROM_UNIXTIME() functions. Set the time zone in which MySQL server runs by using the --timezone=timezone_name option of the mysqld_safe script or by setting the TZ environment variable. See also Section 17.4.1.15, “Replication and System Functions”. """
1720080,2018-01-25 09:00:50 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1824
1720080,2017-12-26 22:05:49 UTC,Still repeatable on 5.7
1720087,2017-09-28 07:56:22 UTC,Can you help check the devstack log and sl-api log for more information?
1720087,2017-10-23 06:11:29 UTC,Is this still a problem? Or we can close it?
1720090,2017-09-28 09:26:25 UTC,with lightdm is work fine
1720106,2020-09-21 13:01:39 UTC,Closing because INVALID: Can't replicate.
1720106,2017-09-28 11:24:37 UTC,"crash not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06).
pdf file is attached."
1720106,2017-09-29 05:53:45 UTC,"I'm also can't reproduce bug on Windows. It seems appear only in *ubuntu. I'm try it on two different computers with Xubuntu 16.04, 17.04 and in VirtualBox with xubuntu 16.04 and ubuntu 16.04.
I'm trying Inkscape 0.91 r13725 (right from ubuntu repository) and also latest version from inkscape/stable launchpad."
1720107,2018-01-20 08:05:31 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1474
1720116,2017-09-28 13:17:17 UTC,This error has shown up in last week or so.  Been running Artful for over a month.  Usually on every boot will open a command shell and update/upgrade for the latest updates then open chrome.  By then the popup box shows up indicating the an error had occurred and asking if it should be reported.  After hitting the Yes button nothing else happens.
1720116,2017-09-28 11:53:49 UTC,"In case it could help; an old solution:
https://github.com/zpydr/gnome-shell-extension-taskbar/issues/62"
1720116,2017-09-30 16:25:25 UTC,Reviewed all the available syslogs and found 2-3 of the apport-gtk failures per day from 9/22 to 9/27. Only one failure on 9/28 and none on 9/29.  Had other problems on 9/30 which required a re-install at the 9/29 build level.  Will add a comment if this problem reappears.
1720116,2017-09-29 18:14:31 UTC,Attaching the syslog text showing the sigfault and I think the corresponding crash file.
1720116,2017-09-29 15:34:40 UTC,Would you mind uploading the apport-gtk.0.crash file to the bug report? I'd like to take a look at it and retrace it.
1720116,2017-10-17 18:36:53 UTC,Looking at the apport log file again this looks suspect:
1720116,2017-09-28 19:30:49 UTC,apport-retrace needs both: python-cffi-backend & python3-cffi-backend installed to work
1720116,2017-09-28 16:49:26 UTC,Unable to run apport-retrace.  Get the following
1720116,2017-09-28 13:28:22 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1720116,2017-09-28 20:10:19 UTC,Both of these are installed
1720119,2017-10-06 11:33:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720119,2017-10-06 12:23:13 UTC,Looks like fixed with latest update of both openstack-dashboard and python-neutron-lbaas-dashboard. This can be closed.
1720126,2017-10-25 12:59:38 UTC,"Hello Pieter, or anyone else affected,"
1720126,2017-10-25 12:58:41 UTC,"Hello Pieter, or anyone else affected,"
1720126,2017-10-20 17:17:00 UTC,"On 20.10.2017 [08:24:37 -0700], Nish Aravamudan wrote:

> On 20.10.2017 [07:18:15 -0000], Jan Gutter wrote:
> > I had a look at the two proposals and could not spot any obvious
> > mistakes:
> >
> > - the correct upstream git commit has been cherry-picked
> > - I don't have any objections to attribution or log messages
> >
> > Thanks again for shepherding this one through!
>
> You're welcome, I'll upload them both today.
>
> Thank you and Monique for filing the SRU template properly!
"
1720126,2017-10-20 07:09:00 UTC,"I concur with option 2), unnecessary deviation will just cause confusion."
1720126,2017-10-20 15:24:00 UTC,"On 20.10.2017 [07:09:00 -0000], Jan Gutter wrote:

> I concur with option 2), unnecessary deviation will just cause
> confusion.
"
1720126,2017-10-19 23:59:24 UTC,I have set up two MPs with the adjustments (it looks like Monique's latest debdiffs followed path 2) from my previous comment already) to the DEP3 headers that I think make the most sense. Please take a look at them and if you approve the changes I will upload them.
1720126,2017-10-20 07:18:15 UTC,I had a look at the two proposals and could not spot any obvious mistakes:
1720126,2017-10-26 11:58:58 UTC,I tested on Trusty: iproute2_3.12.0-2ubuntu1.1_amd64.deb fixed the bug.
1720126,2017-10-20 15:24:37 UTC,"On 20.10.2017 [07:18:15 -0000], Jan Gutter wrote:

> I had a look at the two proposals and could not spot any obvious
> mistakes:
>
> - the correct upstream git commit has been cherry-picked
> - I don't have any objections to attribution or log messages
>
> Thanks again for shepherding this one through!
"
1720126,2017-10-26 12:02:15 UTC,I tested the iproute2_4.3.0-1ubuntu3.16.04.2_amd64.deb (xenial) package and this fixed the bug for me.
1720126,2017-11-07 16:37:21 UTC,A real fix for this issue has been accepted upstream and was applied to net-next branch:
1720126,2017-11-01 14:51:14 UTC,"On Wed, Nov 1, 2017 at 7:15 AM, Jan Gutter <email address hidden> wrote:

> @arges
>
> Hi, would you need any more testing from us?
"
1720126,2017-11-02 16:00:39 UTC,This bug was fixed in the package iproute2 - 4.3.0-1ubuntu3.16.04.2
1720126,2017-11-02 16:00:43 UTC,"The verification of the Stable Release Update for iproute2 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1720126,2017-11-08 15:48:46 UTC,"If someone is interested in the proper upstream fixes, please file a new bug and we will need to fix bionic and prepare a distinct SRU for the existing releases."
1720126,2017-11-08 15:54:15 UTC,I can confirm it now works with 112 VF. This is the most my hardware will support.
1720126,2017-11-08 20:18:09 UTC,The trusty upload seems to have an armhf autopkgtest regression - looks really strange and I see it failed once already. I think it might be good to run the autopkgtest suite with no triggers to see if it's an unrelated regression or not. Could anyone take a look at that?
1720126,2017-11-08 20:30:56 UTC,I'm guessing this might be a quirk of the armhf runners:
1720126,2017-12-06 20:51:47 UTC,"I don't think the Trusty armhf autopkgtest test is likely to be a regression. It doesn't appear to have ever passed before and the error looks associated with the test runner rather than iproute2 itself. Given the nature of the patch, it seems unlikely to me to be caused by this update. I think it's OK to treat this situation as if we have no operational autopkgtest for Trusty armhf. And if that were the case, we'd be releasing the SRU anyway. So I'm releasing it to free up the next iproute2 SRU we have lined up."
1720126,2017-12-06 20:53:05 UTC,This bug was fixed in the package iproute2 - 3.12.0-2ubuntu1.1
1720126,2017-11-01 14:15:49 UTC,@arges
1720126,2017-10-19 23:10:08 UTC,"On 19.10.2017 [09:35:19 -0000], Jan Gutter wrote:

> @nacc
>
> Thanks so much for the explanation. I also found
> https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Merge_Proposals_and_Reviewing
> that details a bit more of the internal processes. As relative outsiders
> to the Ubuntu process, I'd appreciate it very much if you could handle
> that part for Monique's patches. I can be on hand to answer technical
> questions if required.
"
1720126,2017-10-17 08:56:17 UTC,@nacc I built from source to verify that the one-liner is directly responsible for fixing and breaking the issue (inherent paranoia). I did test with the binaries and they worked.
1720126,2017-10-18 22:58:52 UTC,"@mvandenberg,"
1720126,2016-09-30 15:03:37 UTC,"Description of problem:
Running ""ip link show"" outputs Message Truncated several times and the resulting interface list is incomplete."
1720126,2016-10-26 10:59:36 UTC,This has been fixed upstream in either 4.5 or 4.6.
1720126,2017-01-11 02:42:06 UTC,"commit 72b365e8e0fd5efe1d5c05d04c25950736635cfb
Author: Phil Sutter <email address hidden>
Date:   Fri Mar 4 19:57:28 2016 +0100"
1720126,2017-03-24 10:32:00 UTC,If there's any interest I could probably provide access to a system exhibiting the issue (Cisco B200 with VIC1340).
1720126,2017-07-05 15:37:23 UTC,It seems that increasing the buffer size has simply pushed the problem further up. With ~95 VFs the message truncated warnings return.
1720126,2017-07-21 12:23:31 UTC,"Hi Alan,"
1720126,2017-07-25 11:17:34 UTC,"Yes, so the behaviour seems to be the same across the releases now."
1720126,2017-09-29 13:29:36 UTC,A simple one-line patch seems to solve the issue for me:
1720126,2017-09-29 13:31:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720126,2017-10-10 09:17:16 UTC,I'm unfamiliar with where to submit the fix for this bug. Am I submitting the fix to the wrong forum?
1720126,2017-10-19 09:35:19 UTC,@nacc
1720126,2017-10-10 11:25:30 UTC,This fix has been pulled into CentOS 7.3 and later
1720126,2017-10-10 11:53:00 UTC,Just a note:
1720126,2017-10-10 12:29:06 UTC,"The attachment ""[PATCH] Fix ""Message truncated"" issue with many VF's"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1720126,2017-10-12 15:33:08 UTC,Is this then fixed in Ubuntu 17.04 which has iproute2 version 4.9.0-1ubuntu1?
1720126,2017-10-12 16:23:35 UTC,"Yes, I've confirmed it's fixed there."
1720126,2017-10-12 19:53:08 UTC,@jangutter: I'm not sure why you built from source? I assume you actually tested the version in 17.04 and it worked.
1720126,2017-10-16 08:22:17 UTC,"This is a debdiff for iproute2 applicable to 3.12.0-2ubuntu1. I built this in pbuilder
and it builds successfully, and I installed it, the patch works as intended."
1720126,2017-10-17 10:12:45 UTC,"This is a debdiff for iproute2 applicable to 4.3.0-1ubuntu3. I built this in pbuilder
and it builds successfully, and I installed it, the patch works as intended."
1720126,2017-10-18 22:14:00 UTC,"On 17.10.2017 [08:56:17 -0000], Jan Gutter wrote:

> @nacc I built from source to verify that the one-liner is directly
> responsible for fixing and breaking the issue (inherent paranoia). I did
> test with the binaries and they worked.
"
1720126,2017-10-10 11:22:19 UTC,This bug has already been fixed upstream in the following commit:
1720131,2019-04-26 16:24:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720131,2019-04-26 16:27:21 UTC,"The bug prevents use of systems ""blessed"" with nvidia optimus.
It has been fixed however.
https://github.com/systemd/systemd/issues/6908"
1720146,2017-09-28 14:15:47 UTC,"We need to:
* make prometheus accessible only inside the cluster or with kubectl proxy
* make grafana accessible only inside the cluster or with kubectl proxy
* make node-exporter accessible only inside the cluster or with kubectl proxy
* we need to protect cadvisor"
1720158,2017-10-23 12:47:00 UTC,"Reviewed:  https://review.openstack.org/508191
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=2c3671b27e138658bf5ae40580ff56c5ecc9540b
Submitter: Zuul
Branch:    master"
1720158,2017-12-07 14:48:41 UTC,This issue was fixed in the openstack/kolla 6.0.0.0b2 development milestone.
1720158,2017-09-28 14:40:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/508191"
1720171,2017-09-28 22:28:27 UTC,"And while we are fixing this, this bug # 1705112 seems to be in the area \o/"
1720172,2018-11-26 09:39:41 UTC,"Hi,
    I have same error for above issue. Could you have resolve it?"
1720176,2017-09-29 15:16:28 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1720182,2017-10-02 17:48:33 UTC,"The problem is that the granular permissions the SRU and Release teams have are based solely on the queue, and not the archive.  Once a package is accepted, those queue permissions become irrelevant, and the archive admins own it."
1720182,2017-10-07 03:16:22 UTC,"I don't think it would be a particularly large overhaul at all.  xPPH.requestDeletion is an odd special case that goes through AppendArchive, which is otherwise only used by a few weird and/or legacy methods (Archive.syncSource[s], Archive.newSubscription, and Archive.removeCopyNotification).  It would be quite easy to get it to check Archive.canAdministerQueue instead, if Ubuntu would be OK with that from a policy perspective.  Doing that wouldn't affect any other methods."
1720182,2017-10-07 05:59:43 UTC,"23:58 < infinity> cjwatson: Hrm, curious.  And that would affect only deletions?  Cause the next thing Brian will complain about is overrides probably (for phasing).
23:58 < infinity> cjwatson: Fundamentally, I'm not sure if this is a thing we want a broader group having rights to without sufficient training anyway, and with said training, they can just be full AA."
1720187,2017-10-13 19:58:21 UTC,I tested this upgrade again with ubuntu-gnome-desktop in data/removal_blacklist.cfg but not in ForcedObsoletes and this also did not cause it to be removed.
1720187,2018-05-02 20:43:23 UTC,I reported bug 1768620 regarding the removal_blacklist.cfg file being out of date and dropped ubuntu-gnome-desktop from that file.
1720187,2018-04-27 08:09:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720187,2017-10-06 21:09:31 UTC,"Putting it in ForcedObsoletes did not work because ubuntu-gnome-desktop also exists in data/removal_blacklist.cfg.  Additionally, cyphermox is of the opinion that if the debian control fields are setup properly for this the autoremoval should happen anyway although it probably also needs removing from data/removal_blacklist.cfg so I'll handle that."
1720187,2017-10-06 20:43:29 UTC,"Shouldn't that simply be handled by proper dependencies across the relevant packages? If ubuntu-desktop Breaks/Replaces ubuntu-gnome-desktop, you shouldn't need to do any special handling in u-r-u."
1720187,2017-10-02 23:23:09 UTC,"The second part of this bug is actually about a string from update-manager and it uses ""flavor_name"" from UpdateManager/Core/utils.py which guesses it by looking for a package which ends with '-desktop'.  There is a lookup in the get_ubuntu_flavor_name function you could add an override for ubuntu-gnome-deskotp and SRU to 17.04."
1720187,2017-10-07 00:26:44 UTC,Did you forget to try removing it from the removal_blacklist.cfg?
1720187,2017-10-06 18:56:49 UTC,For the first part I think we can use DistUpgrade.cfg and put ubuntu-gnome-desktop in the ForcedObsoletes section for either ubuntu-gnome-desktop or it and ubuntu-desktop.  I'll test this out now.
1720188,2017-10-21 06:03:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720188,2017-10-21 06:04:23 UTC,mpv can't be close without killing the mpv process Ubuntu 17.10 running classic gnome shell profile.
1720197,2018-10-03 06:23:59 UTC,"I have made some changes to my configuration, so it's not an entirely clean test, but I *did* notice that I no longer needed to mess with gfxpayload. I guess that it's fixed?"
1720197,2018-10-02 20:02:58 UTC,"Is this still reproducible? We have changed the default gfx mode to stay ""text"" on EFI."
1720197,2017-10-13 06:19:06 UTC,Do you mean gpu-manager?
1720197,2017-10-13 02:56:47 UTC,"Oh, it might be worth mentioning - on the boots where I wouldn't see anything, adding the fbcon=map:1 parameter to the kernel command line gives a usable system - the console and X¹ both come up correctly."
1720197,2017-10-05 04:47:11 UTC,I think this one is the reversed of bug #1711452.
1720197,2017-10-03 16:00:30 UTC,This sounds like the same as bug #1711452.
1720197,2017-09-30 08:11:11 UTC,"Debian bug [1] is resolved by introducing a patch that has ""set gfxpayload=keep"" when kernel uses config ""CONFIG_FB_EFI=y""."
1720197,2017-09-29 21:13:27 UTC,System76 here.  We have also had luck with this grub flag:
1720197,2017-09-29 16:13:31 UTC,"If this work, it's probably due to buggy VBIOS."
1720197,2017-09-29 16:12:56 UTC,"Edit the Ubuntu boot entry in Grub menu, change ""gfxmode $linux_gfx_mode"" to ""gfxmode text"".
I think this can workaround your issue."
1720197,2017-09-29 15:20:48 UTC,"Yes. In all cases, GRUB itself draws fine."
1720197,2017-09-29 04:15:18 UTC,Is GRUB itself drawn on the screen?
1720197,2017-09-28 18:08:53 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1720197,2017-09-28 18:00:11 UTC,This change was made by a bot.
1720197,2017-09-30 03:22:48 UTC,"Can you attach the output of ""videoinfo"" under GRUB?"
1720197,2017-09-29 17:48:16 UTC,"You are absolutely correct; forceing “gfxmode text” appears to make
booting reliably visible."
1720203,2017-11-01 03:24:12 UTC,https://gcc.gnu.org/bugzilla/
1720207,2018-12-19 16:39:49 UTC,"list-keys only lists *local* keys, it does not show the remote keys uploaded to the store (i.e. the one you registered)."
1720207,2020-03-30 16:11:34 UTC,"We should allow list-keys to show these ""orphaned"" keys that are registered in the store but not available locally, otherwise the UX is confusing and we have hit this multiple times with customers."
1720209,2017-09-28 20:02:50 UTC,Debugging this I found that it fails in this line:
1720209,2017-09-28 20:31:20 UTC,This seems to fix it.
1720209,2017-09-28 20:32:00 UTC,This seems to fix it
1720209,2018-09-09 07:01:11 UTC,Oh thank you for this submission. I found the same solution for this problem because I was not aware someone already solved it... so for the coming 18.04 version it is fixed in: https://git.launchpad.net/~ltsp-manager/ltsp-manager/commit/?id=c1e5415d7bfdfa591bfcd057025cdcaa9c1a6be2
1720213,2018-09-03 01:48:32 UTC,"Moved to gtk, per upstream."
1720213,2018-08-31 11:10:59 UTC,This is the upstream issue:
1720213,2018-08-31 10:04:53 UTC,"It's indeed an opinion, but my one matches Merlijn's (Merlijn, I'd appreciate if you opened a bug according to Daniel's suggestion (does it really belong to mutter, rather than some more core wayland component?))."
1720213,2018-08-31 09:33:12 UTC,"> Only a few applications don't adhere to this, even on Wayland.
"
1720213,2018-08-31 08:57:55 UTC,"I disagree because this is the behavior on all other DE's, on Windows and on Mac, and on most other applications. Only a few applications don't adhere to this, even on Wayland."
1720213,2018-08-30 13:35:53 UTC,This bug is still present in Ubuntu 18.04.
1720213,2018-08-08 08:01:23 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1720213,2017-10-26 10:07:33 UTC,I can confirm the behavior.
1720213,2017-09-29 08:18:25 UTC,Buggy behavior:
1720213,2017-09-28 20:59:27 UTC,"Is the behavior the same in other apps, e.g. gedit, libreoffice writer, firefox, etc...?"
1720213,2018-08-31 01:24:35 UTC,"I don't think this bug is valid. If somekey+<delay>+Ctrl works the same as Ctrl+somekey in Xorg then that's interesting, but not normal recommended behavior. Your should always be holding the modifier (Ctrl) first."
1720222,2017-09-28 20:17:55 UTC,Thanks for your report. It is very likely because you are running wayland. Could you run the same command under X and tell us if it is still failing?
1720222,2017-09-28 21:26:24 UTC,"Confirmed - the command runs without segfault when I start a session under X, so it's only under Wayland."
1720226,2017-09-28 21:28:38 UTC,"reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1720226,2017-09-28 21:42:31 UTC,"backtrace attached, from the 0.92.x branch"
1720226,2017-09-29 09:39:33 UTC,(not reproduced on trunk/master)
1720226,2019-07-18 04:29:32 UTC,"Re-replicated above results. Likely fixed somewhere by changes to SPObject::detach (I'm guessing related to 058e95a59ccb2ab1748392acdfdbbffd516c9c81, where the link to child is removed before releaseReferences is called)"
1720228,2018-03-22 13:35:49 UTC,Hi Stefan-
1720228,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1720228,2018-03-22 12:50:12 UTC,"I have just verified the -proposed kernel, and the correction works as expected."
1720228,2017-10-02 19:02:19 UTC,PPA fix for the issue is at:
1720228,2018-03-13 20:07:47 UTC,"Khaled, any ides when this fix will be released?"
1720228,2017-09-28 20:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1720228,2018-03-19 10:56:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1720228,2017-11-28 15:04:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720234,2017-10-19 21:07:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720240,2017-09-29 09:17:44 UTC,"etcd doesn't run on the subnode by default, it is enabled by kuryr-libnetwork here:"
1720240,2017-09-29 14:07:50 UTC,"Yes, it seems the subnode's etcd is not needed because kuryr-libnetwork is using the etcd in SERVICE_HOST."
1720240,2017-09-29 05:19:55 UTC,"I think you are correct in locating the patch that triggers this, but I'm wondering how the original devstack setup is sensible. IIUC it is starting two independent etcd processes, one on each node, and then directs clients on each node to the local etcd. So the expected feature of getting some kind of coordination between the nodes won't happen. Unless we want to create a real etcd cluster, I think we should better just stop starting etcd on subnodes in order to fix this bug."
1720242,2019-09-19 14:49:18 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1720246,2017-09-28 21:56:10 UTC,"StacktraceTop:
 xkl_engine_constructor (type=<optimized out>, n_construct_properties=<optimized out>, construct_properties=<optimized out>) at xklavier.c:669
 g_object_new_with_custom_constructor (n_params=1, params=0x7fff5fcaab90, class=0x55a525602610) at ../../../../gobject/gobject.c:1699
 g_object_new_internal (class=class@entry=0x55a525602610, params=params@entry=0x7fff5fcaab90, n_params=n_params@entry=1) at ../../../../gobject/gobject.c:1779
 g_object_new_valist (object_type=94167784783040, first_property_name=first_property_name@entry=0x7fe4bda967ff ""display"", var_args=var_args@entry=0x7fff5fcaace0) at ../../../../gobject/gobject.c:2104
 g_object_new (object_type=<optimized out>, first_property_name=first_property_name@entry=0x7fe4bda967ff ""display"") at ../../../../gobject/gobject.c:1624"
1720246,2017-10-15 09:46:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720246,2020-11-10 23:36:44 UTC,"why this was marked as ""in progress""? Trace don't have full symbols and I cannot understand from the present data what could be the cause, I not understand why is marked wayland (cinnamon don't have wayland support now), is there something more expert that can explain what he discovered about this please? to understand at least if is an issue related to cinnamon, not solved or solved in new version.
Ubuntu 17.10 reached EOL and I suppose that this can be keep only if is a cinnamon issue, still present and not solved"
1720247,2019-06-14 14:08:58 UTC,"Change to sru-report prepared and tested, waiting for review."
1720247,2019-09-17 07:55:02 UTC,"This now work, as per our pending-sru page:"
1720252,2017-09-28 22:35:11 UTC,"On re-thinking, I wonder if this is a valid bug. Should the installer ask for the LVM password?"
1720252,2017-09-28 22:37:43 UTC,"This is known, while the logic could maybe be improved, this is not a problem with Lubuntu Next, or any flavor."
1720262,2018-08-08 08:01:56 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1720262,2021-02-23 23:25:09 UTC,"Hi,"
1720262,2020-06-18 01:35:34 UTC,This bug is already fixed and closed.
1720262,2020-06-17 12:02:15 UTC,"Ubuntu 20.04, I enabled two missing actions to have them in the context menu of the app in dock."
1720262,2020-02-03 14:37:09 UTC,Still in Ubuntu 19.10 the two actions (Take a Screenshot of the Current Window and Take a Screenshot of a Selected Area) are still disabled.
1720262,2019-10-13 17:04:53 UTC,"The above mentioned two buggy features (Take a Screenshot of the Current Window and Take a Screenshot of a Selected Area) are still disabled via the /usr/share/applications/org.gnome.Screenshot.desktop file in Ubuntu 18.04.3 LTS which is a supported version right now.
Actually the commented out actions have a link in comments to this issue which led me here."
1720262,2017-10-27 08:05:44 UTC,There is no easy way to have those actions filtered out for GNOME/wayland only...
1720262,2017-10-12 14:57:46 UTC,We decided to go ahead and disable the broken actions for Ubuntu 17.10.
1720262,2017-10-12 19:08:30 UTC,Ah ???!!!
1720262,2017-10-27 05:31:37 UTC,They work fine on Unity. it's a wayland problem. But why deny xorg users because of that?
1720262,2017-09-29 12:53:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1720262,2017-09-29 12:55:22 UTC,"we debugged that a bit with Didier on IRC some weeks ago, gnome-screenshot is calling the gnome-shell dbus api but gnome-shell never writes the screenshot file, seems like having the context menu open makes it fail to take the screenshot or something..."
1720262,2017-10-10 16:32:31 UTC,"This likely will not be fixed before Ubuntu 17.10 is released, but once it is fixed, it will make a good Stable Release Update candidate."
1720262,2017-10-09 02:18:38 UTC,"It's worth repeating: To take a screenshot you don't need to click on anything or to run ""Screenshot"". Just press your 'PrtScn' key at any time and an image file will appear in your Pictures directory, or home directory."
1720262,2017-10-12 17:16:36 UTC,This bug was fixed in the package gnome-screenshot - 3.25.0-0ubuntu2
1720262,2017-10-08 18:37:24 UTC,"Make sure you don't hold Ctrl key, as it saves screenshot in clipboard."
1720272,2017-10-25 10:40:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/515021"
1720272,2018-01-06 12:49:32 UTC,"Change abandoned by jinke (jin.ke@99cloud.net) on branch: master
Review: https://review.openstack.org/515021"
1720272,2019-11-20 04:17:43 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1720272,2018-09-28 11:18:51 UTC,"No activity in the bug and change abandoned, marking as incomplete"
1720278,2017-09-29 12:51:35 UTC,I found an MDM issue here
1720278,2017-09-29 12:54:59 UTC,Question: Do internet browsers use the $LANG or $MDM_LANG environment variable to show web sites the preferred language (or then the password)?
1720278,2017-09-29 15:46:43 UTC,"A colleague got an important point: What ever triggers this behavior, should take place *before* the password is hashed, so when the password is set up."
1720278,2020-06-10 23:49:23 UTC,I have also experienced this issue. I have not been able to reproduce its occurrence from scratch. I have made some small additional observations but am not sure it's appropriate to report them here. Any advice?
1720278,2020-06-11 17:01:25 UTC,"Quiet simple: I switched to Linux Mint 19.1 Tessa and didn't observed
the issue again."
1720292,2018-03-01 10:51:09 UTC,Update watcher container installation section with actual guide of docker.
1720292,2017-11-01 01:58:24 UTC,"i am sorry i am confused with https://bugs.launchpad.net/watcher/+bug/1715032.
This bug still active."
1720293,2020-12-18 15:56:46 UTC,"Replicated Inkscape 0.92+devel (bc776cf2ee, 2017-11-03) Arch, but not in 1.0.1 (3bc2e813f5, 2020-09-07) Arch"
1720293,2017-09-29 09:44:42 UTC,#0  0x00007fb5218c2bec in Inkscape::UI::Dialog::FilterEffectsDialog::update_settings_view() (this=0x7fb5078d8c00) at inkscape/src/ui/dialog/filter-effects-dialog.cpp:3074
1720298,2017-09-29 06:48:33 UTC,"Summary:
.cotcot looks like a standard FIE XML file.  Which means the workflow could be :
1) Run Check-in in Belle Poule
2) Run set up Round 1 pools.
3) Save the competition .cotcot
4) Close Belle Poule.
5) ClubKnight reads the .cotcot file.
6) ClubKnight re-exports each pool for Referee and Audience.
7) Referees score the pools in ClubKnight Referee.
8) ClubKnight saves the score data to the .cotcot file.
9) Re-open Belle Poule. and create the next round.
10) re-run steps 2 to 9) for each successive round."
1720307,2017-09-29 07:33:46 UTC,"Proposed behaviour:  Warning is displayed, asking if the new maxscore should be applied to the current pools where data has been entered.  This allows the user to amend all the Victories in one button-press."
1720311,2017-10-10 20:37:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720318,2017-10-01 09:12:07 UTC,"I'm using archlinux with i3, and this happened with all gtk3 applications."
1720318,2017-09-30 12:44:52 UTC,"Just for my clarity/info, which desktop are you running under? At least under Unity (Ubuntu) it switches automatically as I swap between Hi and Lo DPI. Do you have this problem with other gtk3 based applications, or just Terminator?"
1720318,2017-09-29 10:15:42 UTC,You don't mention what version of Terminator. I have a laptop with HiDPI and Terminator 1.91 (the latest gtk3 version) is fully HiDPI compatible. It even does the right thing when I hot plug and switch to a LoDPI external monitor.
1720318,2017-09-30 09:36:09 UTC,I'm was using 1.91
1720328,2017-09-29 09:25:31 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x5606b83079e0, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4025
 g_object_ref (_object=0x5606b83079e0) at ../../../../gobject/gobject.c:3180
 set_icon (class_group=class_group@entry=0x5606b8544700) at class-group.c:439
 _wnck_class_group_remove_window (class_group=class_group@entry=0x5606b8544700, window=window@entry=0x5606b85a8a10) at class-group.c:494
 update_client_list (screen=0x5606b8574ac0) at screen.c:1673"
1720334,2017-09-29 10:12:37 UTC,Additional Info:
1720341,2018-09-28 11:21:52 UTC,Any update on this bug?
1720341,2018-09-28 11:56:36 UTC,"Not from me, but I can try and pick it up this cycle."
1720341,2019-03-28 10:09:37 UTC,"Doug, any update?"
1720341,2019-11-20 04:17:45 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1720347,2017-09-29 15:05:53 UTC,"Fix going into charm helpers
https://github.com/juju/charm-helpers/pull/18"
1720350,2019-09-20 01:10:04 UTC,https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.173
1720350,2019-02-12 22:08:48 UTC,fixed in https://git.launchpad.net/~ddstreet/ubuntu-dev-tools/+git/ubuntu-dev-tools/commit/?id=4eb794e9f6760b5390e01df7b28088f22151f342
1720361,2017-09-29 17:12:29 UTC,"Having a plain text field that could include brief reminders or alerts for staff could be useful, too."
1720361,2017-09-29 17:06:52 UTC,+1
1720371,2019-12-09 16:50:18 UTC,https://review.opendev.org/#/c/698016/
1720371,2019-12-18 11:13:52 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/699663"
1720371,2019-12-18 12:33:50 UTC,"Reviewed:  https://review.opendev.org/698016
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=a32cddca4974b9ee43c91544be19014a9748c450
Submitter: Zuul
Branch:    master"
1720371,2019-12-18 17:49:59 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/699741"
1720371,2019-12-18 17:51:23 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/699742"
1720371,2019-12-20 19:42:49 UTC,"Reviewed:  https://review.opendev.org/699663
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=19bae1bfbd6751e84d375c5ad2ff50bd65c5fa2f
Submitter: Zuul
Branch:    stable/train"
1720371,2019-12-20 21:17:07 UTC,"Reviewed:  https://review.opendev.org/699741
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=e29501b507c4fb3e25e2ac07ab86214bbcdda24f
Submitter: Zuul
Branch:    stable/stein"
1720371,2019-12-20 21:17:16 UTC,"Reviewed:  https://review.opendev.org/699742
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=1a8ed92f5cf084f527ea78cfb349e10e2f4559e7
Submitter: Zuul
Branch:    stable/rocky"
1720371,2020-01-30 10:21:53 UTC,This issue was fixed in the openstack/kolla-ansible 7.2.0 release.
1720371,2020-01-30 10:24:08 UTC,This issue was fixed in the openstack/kolla-ansible 8.1.0 release.
1720371,2020-01-30 10:26:56 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.1 release.
1720374,2019-05-30 11:58:57 UTC,Marking the charm-ceph task wontfix as the ceph charm has been removed from support for a while now
1720374,2018-11-20 06:59:39 UTC,"Reviewed:  https://review.openstack.org/615600
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=7a362ff0a5b355f55c430e867ebbf4f1303faf2a
Submitter: Zuul
Branch:    master"
1720374,2018-11-05 16:09:21 UTC,"One more thing, it appears that setting mon_pg_warn_max_object_skew to 0 will disable the check [1]."
1720374,2018-09-26 19:10:49 UTC,It would be useful if we could also have the following exposed to the charm:
1720374,2017-09-29 14:10:25 UTC,"Was thinking about creating an action for this, but the action wouldn't persist the setting if we extended to another unit."
1720374,2018-11-05 15:59:52 UTC,"Hi James/Drew, couple of points here;"
1720378,2017-09-29 14:30:06 UTC,This change was made by a bot.
1720378,2017-09-29 14:43:08 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1720378,2017-09-29 17:52:01 UTC,Thanks for the suggestions. I will try with an upstream kernel and also add steps for reproducing
1720378,2017-09-29 18:05:33 UTC,Thanks.  I can try to reproduce this issue if you list the steps.
1720378,2017-10-02 06:43:57 UTC,Thanks jsalisbury. Ill try on another kernel now.
1720378,2017-10-02 06:54:05 UTC,I've retested with linux-image-4.4.9-040409-generic_4.4.9-040409.201605041832_amd64.deb but the image seems to persist.
1720378,2017-10-02 17:27:36 UTC,kernel-bug-exists-upstream
1720378,2017-10-10 20:31:24 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1720385,2017-09-29 17:38:30 UTC,"This sounds like a waste of GUI space for me.
However, the use case is valid."
1720385,2017-09-29 21:13:23 UTC,"The autodetection would be awesome, but I'm afraid that it's very difficult."
1720391,2017-11-03 16:43:21 UTC,Syncing task from Mir.
1720398,2020-11-23 04:48:54 UTC,Thank you for reporting this bug to Ubuntu.
1720398,2017-10-20 15:43:33 UTC,"Hi, cannot use the seafile-gui client anymore! Won't install because of this...
https://forum.seafile.com/t/seafile-gui-ubuntu-17-10/3800/5"
1720398,2017-10-04 22:12:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720398,2017-11-04 17:52:28 UTC,Hi the Seafile packages have been fixed.
1720399,2019-01-29 04:18:12 UTC,"Does ""restart"" mean ""restart Windows"" or restart something else?"
1720399,2019-01-29 04:27:11 UTC,Restart window s but holy shit man. This was a long time ago.
1720414,2017-10-03 08:25:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509107"
1720414,2017-11-21 08:25:10 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/509107"
1720416,2018-02-23 19:13:38 UTC,"For horizon, does it make sense to implementation pseudo pagination in the horizon side? In the pseudo pagination, horizon APi wrapper retrieves all data from keystone v3 API and filter projects based on marker (i.e., ID). Of course it is not perfect it might be a reasonable workaround. (Note that if keystone returns projects in a random order it makes the thing worse.)"
1720416,2018-01-08 20:47:09 UTC,I'm curious if there is any update on the performance suggestions from comment #7.
1720416,2017-10-13 22:11:55 UTC,This also seems similar to https://bugs.launchpad.net/keystone/+bug/1700852 which we landed a fix for last release. You're likely already using it if you have caching configured though.
1720416,2017-10-13 22:11:16 UTC,I'm having a whole bunch of issues with LP today. I apologize for the formatting in comment #6. This was the intended message:
1720416,2017-10-13 22:10:05 UTC,"I have a couple configuration specific questions. Do you have keystone setup to cache anything [0]? Do you notice any sort of latency with token validation at all, or is the performance hit solely with listing projects? What token format"
1720416,2017-10-12 15:57:23 UTC,"Ying, filter_data_first is a stopgap at best. I've enabled it, but unless the domain admin knows exactly what to look for, they can't see the full list and browse."
1720416,2017-10-10 04:19:56 UTC,"As you mentioned, pagination is not supported in keystone V3 at the moment. Thanks for trying to get the attention from keystone team on this. At the same time, you may want to turn on the filter_data_first setting for the projects panel in Horizon. https://docs.openstack.org/horizon/latest/configuration/settings.html#filter-data-first"
1720416,2017-09-30 07:49:21 UTC,"Also I do not see a way to make the admin account view the project => overview by default, making the Identity section the most unusable part of the entire UI."
1720416,2017-09-29 21:12:46 UTC,Aside from any rendering slowness it does not appear to me that they keystone v3 api supports paging.  So any admin with a large number of tenants is going to suffer.
1720416,2017-09-29 21:12:24 UTC,"I've added Keystone, in case this is keystone-related."
1720419,2017-09-29 17:40:45 UTC,"StacktraceTop:
 __cxa_finalize (d=0x7f668d3dafd0) at cxa_finalize.c:39
 __do_global_dtors_aux () from /tmp/apport_sandbox_iPcu3I/usr/lib/x86_64-linux-gnu/libmirclient.so.9
 ?? ()
 _dl_fini () at dl-fini.c:235"
1720435,2018-03-20 21:39:08 UTC,https://git.openstack.org/cgit/openstack-dev/pbr/tree/pbr/version.py#n408 Shows where pbr.version.VersionInfo is defined. Without more data like package versions this is hard to debug but my guess is maybe you have a very old PBR version that predates the VersionInfo object (and version.py file) existing?
1720438,2018-05-03 18:10:03 UTC,"Ok tried several graphical environments with the line ""WaylandEnable=false"" commented and uncommented, and the proprietary nvidia graphics driver, and those are the results:"
1720438,2018-05-04 02:01:39 UTC,If your backlight is wired through Nvidia then I think you may need to use the xbacklight interface. You can do it manually by installing:
1720438,2018-05-04 02:02:49 UTC,"Also, obviously, the above only works in Xorg logins."
1720438,2018-05-04 02:04:38 UTC,Note to developers: The tricky thing about this bug is that you may need a pure Nvidia system. Not a hybrid.
1720438,2018-05-03 09:31:19 UTC,Try this tutorial
1720438,2018-05-05 09:59:00 UTC,"I confirm that 'xbacklight -set 60' works (as user, no root required), in both desktop sessions: ubuntu and plasma. However, the Fn key + arrow only works on plasma."
1720438,2018-05-05 09:59:25 UTC,Probably just waiting for the gnome team to fix it is just enough.
1720438,2018-05-05 10:17:08 UTC,Switching to integrated graphics the Fn works perfectly on gnome. Also:
1720438,2019-01-23 19:07:04 UTC,xbacklight works for me at Ubuntu 18.10.
1720438,2018-05-04 02:35:00 UTC,Please try the 'xbacklight' command. And see also https://bugzilla.gnome.org/show_bug.cgi?id=688052
1720438,2018-05-03 09:28:43 UTC,I think it has to do with Unity or Wayland. If you use KDE instead it just works.
1720438,2017-09-30 14:06:33 UTC,I've managed to use a workaround to make the hotkeys work.
1720438,2018-04-08 19:38:15 UTC,Persists on 18.04 beta 2 with Nvidia driver 390
1720438,2017-10-01 21:13:33 UTC,Same problem here.
1720438,2017-10-01 21:22:23 UTC,remember to click the 'This bug affects you' link near the top
1720438,2017-10-01 21:23:25 UTC,also did you do the update-grub part? but I do think this bug needs a proper fix
1720438,2017-10-07 19:47:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720438,2017-09-29 19:57:01 UTC,I think this is more of a GNOME3 bug than a bug with the Nvidia driver
1720438,2017-10-07 20:15:53 UTC,I tried also: sudo su -c 'echo 10 > /sys/class/backlight/acpi_video0/brightness'.
1720438,2017-10-23 08:16:44 UTC,After upgrade from 17.04 to 17.10 I can only change brightness if I log in to unity desktop and from there adjust brightness setting in system settings.
1720438,2018-01-24 22:03:58 UTC,Confirmed on 17.10 and Nvidia drivers 384.111
1720438,2017-10-07 19:50:51 UTC,"@brinstar, yes I did the sudo update-grub part, and tried acpi_brightness=[native|vendor] which for me makes the Fn hot keys not working (when you press them, no brightness icon appears)."
1720438,2018-04-30 02:57:26 UTC,I'm having the same issue in 18.04 Nvidia driver 390.48. I found this workaround at the moment if anyone is interested https://askubuntu.com/a/1013767
1720456,2018-03-22 06:10:31 UTC,Kinds of a docker service issue. Daisy has fixes docker-engine version to 17.05. please try if it can help to solve this problem?
1720462,2021-02-12 14:00:44 UTC,"Hi: yes, I'm aware. What is more, as you can see in the post #9 in the bug #1714366, I've wrote: ""(...) By the way, I realized that fast backspins fail in absolute mode as well (...)"" Anyway, as far as I know, scratch DJ's tend to use relative mode."
1720462,2021-02-15 22:21:59 UTC,There's no need to make our own timecode format. Serato's is fine and widely available.
1720462,2021-02-15 22:12:24 UTC,"Ah, licenses and laws, that ""human environment programming""... I guess it is necessary as well."
1720462,2021-02-15 21:08:51 UTC,An issue with the licensing of xwax has come up so we'll probably be rewriting vinyl control from scratch for Mixxx 2.4: https://github.com/mixxxdj/mixxx/pull/3476
1720462,2021-02-15 20:59:03 UTC,"Thanks, Owen! Your suggestion to fix it sounds really good, but I understand the problem of working with a code not written by oneself (not being clever)."
1720462,2021-02-12 22:50:14 UTC,"For the other developers, although DJs usually use relative mode, in order to scratch properly the relative position of the record with the track should not ""drift"" over time.  Unfortunately the pitch information from DVS is too noisy and inaccurate for this to work without a lot of clever code."
1720462,2021-02-12 22:44:45 UTC,"If someone wanted a nicely contained programming project, cleaning up vinyl control, writing tests (!!!!) for it, and upgrading the processing would be really lovely to have.  It should even be possible to make tests that run entirely apart from the rest of the mixxx code, which would make our vinyl control code much more robust."
1720462,2021-02-12 22:43:14 UTC,"Mixxx uses xwax's vinyl code.  For that reason, any fixes for things like sticker drift would probably have to be made in xwax first, and then mixxx could benefit.  For context, I wrote the vinyl control code.  I know it's not pretty :)."
1720462,2021-02-12 01:35:24 UTC,"@bronxio This may be a stupid question, but I don't see it answered clearly, yet, neither here nor in lp:1714366, since you talked a lot about Cross and Traktor."
1720462,2021-02-11 18:23:03 UTC,"The Ms Pinky SDK is proprietary, so that doesn't help."
1720462,2021-02-11 18:13:40 UTC,"I guess Mixxx is ""hearing"" the analog wave only (direction + speed) and ignoring the digital one (timecode position). I mean, observing the propietary DVS behaviour, they keep the spin position always, so they must ""hear"" the digital one as well, even in relative mode (I guess this is the key). In this way, drifting (with or without the needle on the record) will never happen."
1720462,2021-02-11 17:39:38 UTC,"Confirmed by another user:
https://www.reddit.com/r/DJs/comments/lfh78q/new_in_mixxx_23_importing_tracks_and_cues_from/gmr7b5z?utm_source=share&utm_medium=web2x&context=3"
1720462,2018-09-21 01:07:22 UTC,"You're welcome! I think tomorrow I will be able to test Xwax in Ubuntu with another sound card that I have now, I'll give it a try."
1720462,2018-09-21 00:38:13 UTC,"Oh nevermind, I see there's much more description in Bug #1714366. Thanks for the report and videos!"
1720462,2018-09-21 00:35:45 UTC,"Or maybe, you're saying that even in relative mode in Traktor 2 / Cross, they handle needle up & drop in an ""absolute"" fashion?"
1720462,2018-09-21 00:34:08 UTC,"Thanks for the report Ambrosio, I know it's been a while, but can you confirm whether you were using absolute or relative mode? I think this is the intended behavior in relative mode."
1720462,2021-02-11 20:21:31 UTC,The main obstacle to fix this issue might be that none of the active developers is familiar with the DVS/xwax code in Mixxx. I took a quick glance at the code and don't think I will touch it ;)
1720465,2018-05-23 01:40:06 UTC,"Removing Assigned to, so that the bug can expire."
1720465,2018-05-23 05:28:29 UTC,"@3v1n0 I tried but can't yet confirm if the original reboot persistence bug is still happening, because it seems every time I test it an additional layer of problems occurs."
1720465,2018-05-26 03:45:15 UTC,"Sébastien,"
1720465,2018-05-26 06:11:32 UTC,apport information
1720465,2020-10-11 04:17:21 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1720465,2020-03-27 21:11:24 UTC,A 2017 issue still there in 2020... I have the same problem with Ubuntu 19.10
1720465,2020-08-11 10:01:30 UTC,I think this might have been fixed. Can anyone confirm?
1720465,2018-05-22 14:01:35 UTC,Is this still happening on 18.04?
1720465,2018-05-26 06:11:33 UTC,apport information
1720465,2017-11-24 04:28:28 UTC,"I created a new 17.10 VM in Parallels 13 and didn't update any packages post-installation, so I can still access the scale controls in Settings."
1720465,2017-11-24 04:38:49 UTC,"I also noticed that the first monitors.xml I attached is version 1 of the file spec, while the monitors.xml files created after I changed the scale in Settings are version 2."
1720465,2017-11-24 01:57:22 UTC,That's definitely another issue...
1720465,2017-10-16 03:12:40 UTC,Curious if this is a one off or being consistently observed.  Quite annoying in my setup since the VM gets powered on/off a fair bit and the setting refuses to stick.
1720465,2017-10-16 08:54:27 UTC,Is that still an issue with the current versions?
1720465,2017-10-22 01:57:05 UTC,"Yes, same problem using the final 17.10 release ISO freshly installed as a guest OS under Parallels Desktop 13 on a MacBook Pro host. The default session it logs me into uses X.org instead of Wayland for some reason. My host machine's native resolution is 2880x1800 (but it's detected by Artful as 3360x2100, although that's also the same resolution my old Zesty VM Unity session mis-detected it as)."
1720465,2017-10-23 07:06:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720465,2017-11-21 22:49:11 UTC,"Didn't think it needed another bug report, maybe it does, but as of today the option has simply disappeared..."
1720465,2017-11-24 02:23:43 UTC,"Once the other bug is fixed I can do that.  But right now I can't change
the scaling at all."
1720465,2017-11-23 16:57:50 UTC,This is a serious bug introduced in a minor (automatic) patch.  Any update on a fix?
1720465,2017-11-23 21:50:01 UTC,"Could somebody open a new bug about the regression, that's a new issue and more important than the original problem here."
1720465,2017-11-24 00:25:13 UTC,"No, I've not seen that possible regression reported until today."
1720465,2017-10-01 00:27:34 UTC,could be the same as bug #1716341
1720465,2017-11-22 00:12:00 UTC,"I confirm #6. First, as I have to do every time I boot into my Ubuntu 17.10 VM under Parallels 13, I went to Settings > Devices > Displays and changed my scaling to 200% so I can actually read text. Then I performed some outstanding Ubuntu software updates and rebooted when prompted. When I logged back in, the scaling controls were no longer present in Settings > Devices > Displays, so now I'm stuck with tiny text and UI."
1720472,2019-03-05 12:32:01 UTC,">lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic
"
1720472,2019-03-05 12:34:34 UTC,"""Installing mono-devel"" meaning using the suggested workaround above (twdkeule)"
1720472,2017-12-22 08:18:03 UTC,I updated Mono to 5.4.1 using their PPA (http://www.mono-project.com/download/) and the issue seems to be resolved.
1720472,2017-12-22 07:53:41 UTC,This also affects me (consistently) on Ubuntu 17.10.
1720472,2018-08-12 08:12:42 UTC,Pinta 1.6 on Ubuntu 18.04.1
1720480,2019-06-03 14:50:14 UTC,"This seem to happen now again more often.
Is it required to hit the ""Send"" button in HMC's Operating Systems Messages or can one also just hit Enter/Return after a cmd was specified?
This seems to happen more often in case just Enter/Return was used instead of ""Send"" clicked.
@IBM: Will you have a look at this again? (setting to Incomplete until receiving a answer)"
1720480,2020-05-12 12:05:17 UTC,"This still happens sporadically.
We faced it a couple of times during focal testing of d-i (with now got replaced by subiquity).
Especially when d-i asks to enter a installation password it's often the case that OS Messages doesn't refresh. Interestingly one can type blindly and hit enter and the installation proceeds - hence another indicator that it's most likely a refresh issue."
1720480,2020-11-13 15:20:11 UTC,"------- Comment From <email address hidden> 2020-11-13 10:16 EDT-------
In general it is required to hit the ""Send"" button in HMC's Operating Systems Messages to issue a command. Regarding the refresh concern we will have to get the responsible developer(s) from the IBM Z Firmware team to investigate and comment."
1720486,2020-04-15 13:04:59 UTC,we've just hit that on Rocky too.
1720486,2020-04-27 16:04:29 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: master
Review: https://review.opendev.org/670570
Reason: Fixed in https://review.opendev.org/626226"
1720486,2020-04-23 16:00:23 UTC,Found the culprit:
1720486,2020-04-17 12:17:16 UTC,"btw, I can't reproduce it on master currently"
1720486,2019-07-12 14:27:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670570"
1720486,2020-04-24 10:32:42 UTC,"So, as far as I understand - the issue should be fixed with the following versions of keystonemiddleware:"
1720486,2017-10-12 01:11:45 UTC,"Miguel, yes, it's happening with neutron master"
1720486,2017-10-09 03:08:58 UTC,"And this is a fix proposed to keystonemiddleware [1], not sure if it's the proper place for the fix."
1720486,2017-10-09 03:07:33 UTC,"api_audit_map.conf, http://paste.openstack.org/show/623044/
api-paste.ini, http://paste.openstack.org/show/623045/"
1720486,2017-10-02 21:05:52 UTC,Can you share your keystonemiddleware configuration values? How are things setup?
1720486,2017-10-02 20:52:49 UTC,Is this happening with Neutron master?
1720486,2019-05-29 21:30:55 UTC,I am also seeing this issue with a customer using Queens; downstream bug is https://bugzilla.redhat.com/show_bug.cgi?id=1708468
1720493,2020-03-08 09:17:51 UTC,Bug is still present in
1720493,2018-08-12 12:11:30 UTC,"Does seem to be a problem with ioquake3 file. I copied the ioquake3 file from usr/lib/ioquake3/ in 16.04 and pasted to usr/lib/ioquake3/ in 18.04, made sure it is executable, then it worked for me"
1720493,2018-07-01 02:31:22 UTC,Probably it's not libsdl2 2.0.6 caused bug due Ubuntu bionic has libsdl2 2.0.8 onboard.
1720493,2018-07-01 02:25:38 UTC,The same issue on Ubuntu bionic
1720493,2017-11-19 00:40:58 UTC,I used this http://www.openarena.ws/download.php?view.4
1720493,2018-01-03 03:49:16 UTC,I believe this crash to be caused by a bug in libsdl2 version 2.0.6 in Artful. See https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1722060
1720493,2017-11-18 21:24:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720493,2017-11-04 04:57:54 UTC,Apport reports that it's a ioquake bug.
1720493,2017-10-14 18:29:50 UTC,It seems like that bug https://bugs.launchpad.net/ubuntu/+source/openarena/+bug/1678320 is relevant too.
1720493,2017-10-14 18:25:20 UTC,"I don't know how to link this bug with that bug https://bugs.launchpad.net/ubuntu/+source/openarena/+bug/1651561, so I just added yakkety tag."
1720493,2017-10-12 15:09:46 UTC,Upstream version works
1720493,2017-11-18 21:25:12 UTC,Where can I find the upstream version?
1720510,2018-01-26 03:25:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720510,2017-10-17 13:29:24 UTC,Reported upstream on https://bugzilla.gnome.org/show_bug.cgi?id=789097
1720510,2018-01-25 08:18:15 UTC,I did some more testing for this bug. I can't reproduce it using Communitheme. This seems to be an Ambiance-specific issue.
1720510,2017-10-01 03:13:31 UTC,"No I don't get any errors.
Tested again.on two installations on the same hardware.
- Restarted the the computer.
 - Started Ubuntu Software from the doc
- Search for ""soft"" and the result was presented
- Closed Ubuntu Software
- Started Ubuntu Software from the doc
- Search for ""soft"" and the result wasn't presented
- Clicked outside the Ubuntu Software window and the result was shown."
1720510,2017-10-01 00:24:13 UTC,"thank you for your bug report, do you get any error displayed in the ui? trying here it works unless the snap query timeouts which blocks it to return other results but that's indicated in a notification"
1720510,2017-10-17 13:25:44 UTC,"confirmed, there is a similar problem when browsing categories described on a duplicate"
1720511,2017-10-21 21:47:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720511,2017-10-26 02:01:51 UTC,"do-apt-file-update was in zesty:
https://packages.ubuntu.com/search?suite=zesty&arch=any&mode=exactfilename&searchon=contents&keywords=do-apt-file-update"
1720511,2017-10-31 14:15:04 UTC,"Hello,"
1720511,2017-10-31 14:31:36 UTC,"Hello,"
1720511,2018-10-03 12:51:26 UTC,"I've just upgraded to Ubuntu 18.04 ""bionic"" and this problem is still present (just for the record, I know this bug is still open, there's no surprise)"
1720517,2018-06-11 21:02:32 UTC,Also happening on Ubuntu 18.04
1720517,2017-10-23 22:40:42 UTC,"encountered it after an update to 17.10 as well.
My workaround for now is to start software-properties-gtk using gksu"
1720517,2017-10-13 16:54:12 UTC,I saw this error message in the terminal from which I launched software-properties:
1720517,2017-10-01 06:51:19 UTC,"Yes, the bug is reproducible when I run ""Gnome on Xorg"".
Running Gnome on Wayland this bug does not happen."
1720517,2017-10-01 00:25:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1720519,2017-12-16 01:38:46 UTC,I experienced this bug too. #2 fixes the problem but also removes plasma-pa. When plasma-pa is reinstalled it breaks pulseaudio again.
1720519,2017-12-18 10:28:19 UTC,"I actually tried removing the module with the upgrade to PA 11.1 in Ubuntu 18.04. The release notes for PA 11.0 suggested that switch-on-connect would not be required, but my testing shows it still is needed for both Bluetooth and USB audio devices. Sorry about that."
1720519,2018-01-10 19:16:53 UTC,After upgrading from 17.04 to 17.10 I also had this issue with error:
1720519,2018-03-02 14:16:31 UTC,By commenting the lines from /etc/pulse/default.pa
1720519,2018-03-27 09:13:16 UTC,"Thank you, benvantende! Reinstalling pulseaudio has helped me too"
1720519,2018-03-27 09:25:13 UTC,"ahhh cool that helped. I have updated to 18.04 last week and did not come
across any problems any more."
1720519,2019-06-19 14:21:18 UTC,"I know that if I reinstall from scratch my Kubuntu 18.04, it would fix the issue but it is not acceptable for the reliability of Linux comparing to MacOS or Windows to have to do this."
1720519,2018-08-15 07:15:48 UTC,"I think so, yes."
1720519,2018-08-15 07:58:39 UTC,I also had this problem after upgrading to 17.10 and solved it with commenting out load-module module-switch-on-connect in /etc/pulse/default.pa.
1720519,2018-08-16 01:13:26 UTC,The error message still exists in the latest (12.2) PulseAudio:
1720519,2019-06-19 12:10:47 UTC,"It is not fixed in 18.04.
My Kubuntu 18.04 worked with no sound issue up to mid may 2019.
One morning, no longer sound !
I have tested all the solution proposed with no success...
I think It Would be useful to create another bug linked to 18.04 LTS."
1720519,2017-12-15 19:35:07 UTC,"Workaround in #4 works for me, but only for the computer-integrated speaker. Integrated microphone and also headsets don't work any more."
1720519,2019-06-20 01:29:13 UTC,Ubuntu 18.04 is actually the only current release that ships an old version of PulseAudio.
1720519,2019-06-20 01:31:16 UTC,"Also, progress on this issue is now being made upstream:"
1720519,2018-08-15 03:57:56 UTC,Are you saying this bug was fixed somewhere in 18.04?
1720519,2017-12-15 09:46:36 UTC,The workaround in #4 works-for-me.
1720519,2019-06-20 08:39:55 UTC,"Hi,"
1720519,2017-12-05 05:22:49 UTC,Attached is a patch from upstream made against Pulse Audio 12. The patch makes attempted to load an already loaded load once module non-fatal. This will enables the PulseAudio deamon to start normally under to conditions described in this bug. There will still be a warning message in the system logs however.
1720519,2017-09-30 12:46:12 UTC,"Heyla,"
1720519,2017-09-30 12:47:29 UTC,fixed myself by reinstalling pulseaudio
1720519,2017-10-02 19:31:36 UTC,"had the same problem and could only fix it by removing the line
load-module module-switch-on-connect
from
/etc/pulse/default.pa"
1720519,2017-10-03 09:32:22 UTC,"Good to know. Honestly for some weird reason the same bug re-appeared. I
had to do the same again to solve that, but also removed Discord
<https://discordapp.com/>. I vaguely remembered reading somewhere that
could cause problems. For now all is fine."
1720519,2017-10-04 06:31:41 UTC,pulseaudio 1:10.0-2ubuntu3 does only load that module once. So it sounds like some other config file is getting loaded with it in your case. Perhaps Kubuntu-specific? Can anyone with this bug search their /etc and ~/ and find out all the locations where switch-on-connect is loaded?
1720519,2017-10-06 19:17:16 UTC,This would seem to happen because start-pulseaudio-x11 tries to load module-device-manager that unfortunately conflicts with module-switch-on-connect.
1720519,2017-10-19 21:40:38 UTC,Same bug over here; commands given in #2 helped me to get audio up and running again.
1720519,2017-10-19 22:35:31 UTC,"Fixed like in #4 by commenting load-module module-switch-on-connect, but this may brake functionality with hot connecting devices."
1720519,2017-10-20 15:04:03 UTC,Possibly introduced by:
1720519,2017-10-21 16:45:53 UTC,"I'm seeing this as well on a machine with a clean 17.04 installation that was upgraded to 17.10, using KDE (sound: Intel HDA).  Steps in comment #2 fixed this problem, at least temporarily."
1720519,2017-10-21 18:00:42 UTC,"Update: After reinstalling pulseaudio, alsa-base, pulseaudio-module-bluetooth and plasma-pa (for KDE's volume control applet), the problem reappeared.  Commenting out ""load-module module-switch-on-connect"" in /etc/pulse/default.pa (see comment #4) seems to fix the issue permanently; the module still seems to be loaded due to some other means of triggering the load (see output of: pactl list modules)."
1720519,2017-10-30 17:57:58 UTC,After upgrading from 17.04 I had this issue. Neither could I connect to an external audio device via Bluetooth.
1720519,2017-11-02 10:20:13 UTC,The problem is in an incorrect interaction between KDE's KCM audio configuration module and PulseAudio's default configuration in Ubuntu:
1720519,2017-11-03 01:35:13 UTC,I agree we need a proper fix like that.
1720519,2017-11-24 15:27:25 UTC,"I have this bug now too, seems to happen every time I restart."
1720519,2017-12-05 08:20:17 UTC,"The attachment ""Upstream patch from Pulse Audio 12"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1720519,2017-10-23 16:21:48 UTC,"I had the same issue and workaround from #2 worked, thanks !"
1720520,2018-09-18 09:36:41 UTC,NB I moved to Tiger VNC which does not exhibit this behaviour.
1720520,2017-11-13 18:38:06 UTC,Any updates here? It just happened again (I had forgotten I'd opened this report).
1720520,2018-09-18 07:42:59 UTC,"Still a problem in 18.04, radio silence. :("
1720528,2017-12-31 21:58:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720532,2017-09-30 12:00:07 UTC,This change was made by a bot.
1720532,2017-10-02 17:45:33 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1720532,2017-10-03 20:48:52 UTC,I've tested with v4.14-rc3 and can confirm that the problem still exists there.
1720532,2017-10-04 11:43:12 UTC,Try latest 8265 firmwares from [1].
1720535,2021-02-02 18:10:19 UTC,This bug has been inactive for along time. Newer versions of Nova no longer use these filters anyhow. Marking this as wont fix.
1720536,2017-10-20 13:52:53 UTC,"It appears that the storage.zfs_pool_name was removed in lxd >= 2.9, see: https://github.com/lxc/lxd/blob/lxd-2.9/lxd/patches.go#L290"
1720536,2017-10-20 13:54:55 UTC,"See also the note by jamespage about the nova-lxd supporting ""ZFS storage report is very LXD 2.0.x"" and ""will need to be updated to support LXD storage pools"""
1720544,2020-08-31 12:02:19 UTC,"Cannot reproduce with Inkscape 1.0. If this is still an issue, please use our new tracker: https://inkscape.org/inbox"
1720552,2017-09-30 15:48:10 UTC,"StacktraceTop:
 gvs_tuple_needed_size (n_children=16386, children=0x2f75800, gvs_filler=0xb7e08c60 <g_variant_fill_gvs>, type_info=0x2960280) at ../../../../glib/gvariant-serialiser.c:958
 g_variant_serialiser_needed_size (type_info=0x2960280, gvs_filler=0xb7e08c60 <g_variant_fill_gvs>, children=0x2f75800, n_children=16386) at ../../../../glib/gvariant-serialiser.c:1434
 g_variant_ensure_size (value=0x2f75360) at ../../../../glib/gvariant-core.c:338
 g_variant_fill_gvs (serialised=0xbfaca890, data=0x2f75360) at ../../../../glib/gvariant-core.c:400
 gvs_variable_sized_array_needed_size (n_children=5, children=0x2f75740, gvs_filler=0xb7e08c60 <g_variant_fill_gvs>, type_info=0x27e2348) at ../../../../glib/gvariant-serialiser.c:709"
1720552,2017-10-01 23:26:47 UTC,"This doesn't look like it is a bug in appstreamcli... I am not sure what exactly went wrong there, because the GLib side looks fine as well."
1720552,2020-01-04 04:59:04 UTC,"The specific code that resulted in this issue doesn't exist in newer AppStream releases, so this sort of is ""fixed"" that way, as this issue can't be triggered anymore."
1720554,2017-10-12 23:41:29 UTC,"I updated my OS to Ubuntu 17.04.  gtk-gnutella is 1.1.8-2.  linux is 4.10.0-37-generic.  No change.  Attempting to start gtk-gnutella still fails (five times) in the same place (""Code should not have been reached..."")"
1720554,2017-12-30 03:47:35 UTC,"Updated to Ubuntu 17.10.  Same crash result, same five failures, then total abort."
1720555,2017-11-06 23:36:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720555,2017-10-25 16:06:40 UTC,"> It will be insane to move it right side.
"
1720555,2017-10-25 15:50:29 UTC,"> Maybe Unity should implement the appmenu window button like is used in Ubuntu Budgie and is optionally available in GNOME Shell.
"
1720561,2019-09-11 07:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1720561,2019-11-11 04:17:13 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1720563,2019-09-11 07:00:16 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1720563,2019-11-11 04:17:16 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1720571,2021-02-24 02:24:05 UTC,Can you retry with a new model running on a recent Juju controller?
1720571,2021-02-24 02:22:43 UTC,Note - this bug was filed in 2017 and the code to clean up security groups was added in 2018 so it may be be the issue is now fixed.
1720571,2021-02-24 04:24:30 UTC,This PR does not solve any specific issue but does enhance the destroy model robustness by gathering any remaining security groups that should have been deleted earlier and removing those along with the model.
1720571,2017-10-04 22:57:58 UTC,@anastasia-macmood I'm hitting this on all 2.2.2 models on JAAS
1720571,2017-10-04 21:26:18 UTC,"@james beedy (jamesbeedy),"
1720571,2017-10-03 23:29:44 UTC,"@james beedy,"
1720571,2021-02-24 02:21:05 UTC,I'm having trouble reproducing this using Juju 2.8.8.
1720575,2017-10-07 00:25:50 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1720575,2017-10-07 00:26:06 UTC,"Hi, it looks like you're having some kind of physical disk error or other hardware problem, based on"
1720579,2017-09-30 22:41:29 UTC,Thx so much Dokkie for investigating! Wish all bug reports were detailed like yours :)
1720580,2017-11-23 03:36:49 UTC,I do care. Do you still have this issue on v4.14?
1720580,2019-04-23 18:51:08 UTC,"Hey guys, have we some update on that?"
1720580,2018-10-26 18:59:28 UTC,"And Coenraad, if you need some help, feel free to ask."
1720580,2018-10-26 18:57:57 UTC,"thanks, Coenraad. I already was doing that, but nice tip. I am looking forward for a definitive solution."
1720580,2018-09-27 18:07:49 UTC,"hello guys, have we some good news?"
1720580,2018-07-08 22:35:57 UTC,"Let's wait for 20.04, and hope for the best."
1720580,2017-11-22 19:48:31 UTC,"Ok, I'll mark this as invalid, since nobody cares anyway."
1720580,2018-10-25 13:22:18 UTC,"    sudo rmmod r8723bs
    sudo modprobe r8723bs
    sudo iwlist wlan0 scanning"
1720580,2017-10-17 05:50:37 UTC,"I have a device with rtl8723bs, the message should be completely harmless."
1720580,2017-09-30 21:00:07 UTC,This change was made by a bot.
1720580,2017-09-30 21:11:24 UTC,The relevant part of syslog looked like this:
1720580,2017-10-01 05:24:26 UTC,Does the patch solve the issue?
1720580,2017-10-29 23:32:08 UTC,"Interesting. I get complete freezes when wifi is enabled and these errors appear.With wifi disables, and modules not loaded, it works ok."
1720580,2017-10-02 17:44:46 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1720580,2017-10-16 20:11:45 UTC,"I've applied the above mentioned patch, and rebuilt the rtl8723bs module, but the same problem persists. Also tested kernel 4.14, and, as expected, the same bug is there too."
1720580,2017-10-01 07:53:52 UTC,"Don't know, I've not tied it, and the author had this to say:"
1720582,2017-10-01 15:02:01 UTC,"Gvfs-backends is ""suggested"" by Gimp. I have asked on the Debian bug that it is moved to Depends (Or at least Recommends)."
1720585,2017-10-01 00:09:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1720591,2017-09-30 23:29:17 UTC,Fixed in 4ppa51
1720615,2017-10-01 09:20:45 UTC,"This may be a cinnamon issue, but you links to their github need updating, they don't take you to a bug reporting tool /link"
1720616,2020-04-06 17:19:16 UTC,No problem with Ubuntu 20.04. I will close this ticket.
1720616,2018-02-27 10:50:16 UTC,I have the same issue in current Bionic (prerelease) with gnome-screenshot 3.25.0-0ubuntu2.
1720616,2018-05-09 07:34:23 UTC,Ubuntu 18.04: taking a screenshot of a window now gives the expected color.
1720616,2017-11-02 21:51:58 UTC,"I found this upstream ticket: https://bugzilla.gnome.org/show_bug.cgi?id=787026
which duplicates this one: https://bugzilla.gnome.org/show_bug.cgi?id=779234"
1720616,2017-10-28 09:07:15 UTC,Maybe the same bug than #1672716 but I did not experiment it with 17.04. Only with 17.10.
1720616,2018-02-27 10:48:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720622,2017-10-01 11:00:05 UTC,This change was made by a bot.
1720622,2017-10-02 17:43:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1720622,2017-10-03 19:30:41 UTC,"I tried with Linux 4.14.0-041400rc3-generic, the problem is still there unfortunately."
1720622,2017-10-04 13:51:07 UTC,"My RX480 does not have this issue on v4.13-rc3. Here's the lspci output:
$ lspci -vvnn -s 27:00.0
27:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller])
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 58
        Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 2: Memory at f0000000 (64-bit, prefetchable) [size=2M]
        Region 4: I/O ports at e000 [size=256]
        Region 5: Memory at fe800000 (32-bit, non-prefetchable) [size=256K]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu"
1720622,2017-10-04 18:34:05 UTC,"We have mostly the same lspci output, Kai Heng. I attach a picture of the comparison."
1720622,2017-10-05 06:08:34 UTC,I opened https://bugs.freedesktop.org/show_bug.cgi?id=103102
1720622,2017-11-02 18:48:57 UTC,The bug was fixed in Linux 4.13.11:
1720622,2017-11-16 15:36:33 UTC,"Hi Hadrien,"
1720622,2017-11-16 17:27:13 UTC,"Oh, that's good news. Thank you for the feedback, Pierre."
1720635,2017-12-01 12:13:25 UTC,"Hi Larry,"
1720635,2017-11-03 12:20:04 UTC,"Hi,"
1720641,2018-04-01 19:13:21 UTC,I can confirm
1720641,2018-04-03 09:32:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720641,2018-05-27 14:44:40 UTC,"Hi Guys,"
1720641,2018-05-28 04:30:22 UTC,"The attachment ""usb_intf.c"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1720641,2018-07-28 17:15:24 UTC,Any news about this? I'm having the same problem.
1720649,2017-10-01 15:34:14 UTC,"Actuall, i also checked and reported totem bug https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1720654 , but please, consider to check all of gtk3-applications which were patched for unity de."
1720649,2017-10-09 11:59:29 UTC,"Thank you for your bug report, what desktop environment do you use? There is no menu displayed here under GNOME"
1720649,2017-10-09 17:01:14 UTC,"Yes, it is (displayed). Screenshot taken on GNOME (not ubuntu session - vanilla gnome wayland session, but i dont think it matters). Since you cant see it, make sure you disabled top bar application menu (Go to Gnome Tweaks -> Top menu section -> ""Application Menu"" switcher). If you still cant see it, make sure that ""alternative toolbar"" plugin disabled in rhythmbox. Now you should see the same rhythmbox as on the attached screenshot.
You should disable ""restore-traditional-menubar.patch"" (or fix is somehow, if you want save this menubar for unity session)."
1720649,2017-10-10 07:55:03 UTC,so you are not using the default session but the tweak tool to change things? is that required to get the issue?
1720649,2017-10-14 12:21:25 UTC,"It doesn't matter witch session I use. This bug concerns UBUNTU DEFAULT SESSION. I dont know, why you cannot understand this. I even provide info about patch, which should be disabled to fix this."
1720649,2017-10-16 14:27:46 UTC,"Ok, the confusion come from the fact that you wrote ""Standard gnome behavior"", but in fact you disable the application menu which is not the standard configuration"
1720650,2017-10-01 15:01:23 UTC,"I discovered that when restarting the computer the problem is solved. But if I repeat the process again, the fault continues until the next restart."
1720657,2020-05-22 04:17:34 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1720657,2020-05-22 04:17:33 UTC,[Expired for slick-greeter (Ubuntu) because there has been no activity for 60 days.]
1720677,2017-10-12 19:44:30 UTC,Confirmed on Windows 10 with Adwaita gtk3 theme. This should be addressed for 0.93 as it's a highly visible part of the UI.
1720677,2017-10-23 19:39:21 UTC,"I fixed the width ""a little"" in
https://gitlab.com/inkscape/inkscape/commit/8a097e957fac49ee3a34b26776d1b7738a11a308"
1720677,2017-10-23 19:40:40 UTC,Changing title to point out this also affects rulers.
1720682,2020-07-20 18:07:56 UTC,Closing this issue as part of migration of bugs to GitLab. This issue is tracked in https://gitlab.com/inkscape/inbox/-/issues/3303
1720683,2019-05-17 09:53:54 UTC,"Hi, Ubuntu 17.10 is no longer supported upstream, so closing."
1720693,2018-10-04 05:22:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720693,2019-01-15 09:17:07 UTC,"The issue sounds like it should be fixed with this kernel commit
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=bde1a7459623a66c2abec4d0a841e4b06cc88d9a"
1720697,2017-10-02 09:24:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720697,2017-10-02 13:25:56 UTC,Thanks for reporting this bug and help making ubuntu better!
1720699,2018-12-12 22:02:40 UTC,"(In reply to Dominique d'Humieres from comment #1)

> Confirmed from 4.8 up to trunk (9.0). An instrumented compiler gives
>
> f951: Warning: No location in statement
> ../../work/gcc/fortran/trans.c:1768:39: runtime error: member access within
> null pointer of type 'struct gfc_linebuf'
> f951: internal compiler error: Segmentation fault: 11
"
1720699,2018-11-03 11:43:45 UTC,Confirmed from 4.8 up to trunk (9.0). An instrumented compiler gives
1720699,2018-10-26 17:41:24 UTC,seen on all active versions (test file ends with two newlines):
1720699,2017-10-02 01:51:44 UTC,Repros in 17.04 (Hyper-V VM). Looking into 17.10.
1720699,2017-10-02 01:53:18 UTC,"I assumed you meant 17.04, anyway. The original bug was filed against 16.04."
1720699,2017-10-02 02:25:44 UTC,Also repros in 17.10 (Hyper-V VM). Additional warning in compilation now.
1720699,2017-10-02 01:04:51 UTC,please recheck with 16.04 and 17.10.
1720710,2020-04-30 16:22:24 UTC,"Done, thanks."
1720710,2020-04-22 00:44:29 UTC,"This sounds familiar, I think a fix for it may have come through recently.  Is this still reproducible on eoan or focal?"
1720710,2020-04-22 00:59:58 UTC,"I was on 16.04 back in 2017 when I wrote this. I don't see this on my 18.04 systems now. I'm OK with closing this, is that something I can do?"
1720710,2020-04-30 15:34:48 UTC,"Hi Bill, the bug status can be set to ""Fix Released"", meaning that the bug has been fixed in a version of the package available in a Ubuntu release. This seems to be the case here, as you can't reproduce the issue in Bionic. If this sounds right to you, please go ahead and change the bug status. Thanks!"
1720717,2019-10-03 17:10:45 UTC,"Hi Derek,"
1720717,2019-10-06 22:06:35 UTC,"It's just adding / changing a field, yes. Benefit is that it lets 32-bit libraries be installed at the same time as 64-bit ones, without using a vm or container, which is often useful for running legacy software. Downside is that if for some reason the package were changed to make it impossible to install both at once, then it would be hard to undo, since it would break existing installations."
1720725,2020-05-26 15:19:09 UTC,This bug was fixed in the package libsndfile - 1.0.28-8
1720726,2018-05-02 12:01:21 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1720726,2018-04-25 09:21:14 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1720726,2018-04-18 00:55:15 UTC,"Reviewed:  https://review.openstack.org/560088
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5c43e76ce02d4f4b4e5204070fe1f5f0784d0513
Submitter: Zuul
Branch:    stable/ocata"
1720726,2018-04-17 12:38:51 UTC,"Reviewed:  https://review.openstack.org/560087
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=837ac8c1d651c58f5ebd5a20b409594f7368819d
Submitter: Zuul
Branch:    stable/pike"
1720726,2018-04-10 17:11:53 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/560088"
1720726,2018-04-10 17:11:35 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/560087"
1720726,2017-12-07 23:56:47 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1720726,2017-11-14 12:37:32 UTC,"Reviewed:  https://review.openstack.org/508802
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f1a0557da4fbd7baa9196cb5c0ccdd7ebb16ecdf
Submitter: Zuul
Branch:    master"
1720727,2018-08-01 14:08:04 UTC,"Reviewed:  https://review.openstack.org/534227
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a4ffcab4cae23f1f7b3cc31f1ef922af9582ac2c
Submitter: Zuul
Branch:    master"
1720727,2018-08-02 10:06:43 UTC,"Reviewed:  https://review.openstack.org/529814
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cdb973e77dc33dcccfb8c62eed69e4b2318acd8d
Submitter: Zuul
Branch:    master"
1720727,2018-08-02 10:06:51 UTC,"Reviewed:  https://review.openstack.org/580575
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=00b923ddf37de2176168f5a525b4190dd4e04c4d
Submitter: Zuul
Branch:    master"
1720727,2018-08-07 22:15:44 UTC,"Reviewed:  https://review.openstack.org/576338
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=3b1590ff69602b33c7ff14f5fcb6099d9a26fef4
Submitter: Zuul
Branch:    master"
1720727,2018-08-07 22:15:53 UTC,"Reviewed:  https://review.openstack.org/574128
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=d38f76e68a814d99597bebb9bc60ce8a76ee4af7
Submitter: Zuul
Branch:    master"
1720727,2018-08-08 02:26:00 UTC,"Reviewed:  https://review.openstack.org/578718
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=d865155757b4c46488083c1827623d635352c62a
Submitter: Zuul
Branch:    master"
1720727,2018-08-09 09:07:05 UTC,"Reviewed:  https://review.openstack.org/530715
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=fb1dab78575a3f67eb60e6675bbd1ffcb1b32228
Submitter: Zuul
Branch:    master"
1720727,2018-08-09 09:07:13 UTC,"Reviewed:  https://review.openstack.org/580976
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=ea430ee82ec4b777b6156962f65f844ae8a23966
Submitter: Zuul
Branch:    master"
1720727,2018-08-09 15:24:12 UTC,"Reviewed:  https://review.openstack.org/530694
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=15cabc798d35a0fad854cba3886b05344263c4a9
Submitter: Zuul
Branch:    master"
1720727,2018-08-09 15:31:03 UTC,"Reviewed:  https://review.openstack.org/553738
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=507392be7de4d0c3711eb9143fcc4e9455371470
Submitter: Zuul
Branch:    master"
1720727,2018-08-09 15:31:11 UTC,"Reviewed:  https://review.openstack.org/589991
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=5b3ac1ebda160e80ba3a38c1f113f85b797572d6
Submitter: Zuul
Branch:    master"
1720727,2020-03-24 21:21:57 UTC,Looking at patches merged and related to this I'm marking that as fixed now.
1720727,2018-08-01 01:43:03 UTC,"Reviewed:  https://review.openstack.org/582498
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e82a17527d0c1a59ee92f53ba5fc6752c5034dc4
Submitter: Zuul
Branch:    master"
1720727,2018-07-09 09:34:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/580976"
1720727,2018-08-09 08:47:12 UTC,"Reviewed:  https://review.openstack.org/532792
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=dd9aec1745838c1b9a5ce252d21e0fa5e02b01bb
Submitter: Zuul
Branch:    master"
1720727,2018-06-28 07:48:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/578718"
1720727,2018-07-06 07:53:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/580575"
1720727,2017-10-05 19:33:45 UTC,Seems reasonable to tackle once bug 1468366 is released and documented.
1720727,2018-01-11 20:58:53 UTC,"As of today, only two patches are left to be merged for https://bugs.launchpad.net/neutron/+bug/1468366. Both of those patches have been +2ed. So it seems timely that we discuss the next step described in the RFE in the drivers meeting"
1720727,2018-01-19 17:17:08 UTC,This RFE was discussed in the Neutron drivers meeting. Agreed next steps are:
1720727,2018-01-25 15:11:55 UTC,"Thanks Miguel, regarding (1) the API as such has been around for a few cycles now and is mature, we have also completed the support for VM ports in the Queens cycle - so i think we are in a good position to take on logging. And being a reporting feature it can also help with usability."
1720727,2018-02-01 09:54:36 UTC,"Hi Miguel,"
1720727,2018-02-01 09:59:40 UTC,Basically our solution is similar with what Ihar said in the discussion of driver team http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-01-19-14.00.log.html#l-84
1720727,2018-08-08 18:35:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589991"
1720727,2018-03-08 21:34:12 UTC,This RFE is approved
1720727,2018-03-16 10:02:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553738"
1720727,2018-05-30 17:43:22 UTC,"Reviewed:  https://review.openstack.org/509725
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=6a1372079a7605d2205ebadbc89241f543750849
Submitter: Zuul
Branch:    master"
1720727,2018-06-09 11:34:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/573952"
1720727,2018-06-11 01:20:52 UTC,"Change abandoned by Kim Bao Long (<email address hidden>) on branch: master
Review: https://review.openstack.org/573952
Reason: I will move these chains to neutron-fwaas"
1720727,2018-06-19 03:47:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576338"
1720727,2018-06-27 10:24:00 UTC,"Reviewed:  https://review.openstack.org/574683
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=44e8c91f3c011b91865f85547e1f9fc3d9b4636c
Submitter: Zuul
Branch:    master"
1720730,2017-10-22 16:38:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720730,2019-06-27 01:46:28 UTC,Please open an issue for this feature request upstream:
1720730,2019-07-03 15:54:49 UTC,Submitted bug via github. Issue ID is 969 (https://github.com/micheleg/dash-to-dock/issues/969).
1720738,2017-10-07 00:21:15 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1720738,2017-10-07 00:23:55 UTC,"Seems like you're possibly having some sort of hardware issue or disk corruption, based on:"
1720740,2018-05-22 04:17:27 UTC,[Expired for juju because there has been no activity for 60 days.]
1720740,2017-10-04 07:33:55 UTC,"I don't believe we've ever released a Juju 2.1.4, so I'm a little curious what binary you are running. It sounds like maybe you are running from source in the 2.1 branch?"
1720740,2017-10-04 07:34:38 UTC,"We're unlikely to do another 2.1 release at this time, unless there is a specific support request that requires it."
1720740,2017-10-04 08:01:34 UTC,"Hi,"
1720742,2017-10-12 07:16:24 UTC,"Hi all,
Do you have any updates on this?"
1720742,2017-10-25 20:54:04 UTC,"RBAC sharing of resources cannot be validated through Contrail UI as of now, as from UI we ask to API Server per project details, so it will not give the details, but you can see the sharing stuff using curl command as of now like:
$curl –H “X-Auth-Token: <token>” http://<APIServer>:8082/virtual-networks”
It will return you all the projects corresponding to the project scoped token as well as shared ones."
1720746,2017-10-02 14:40:48 UTC,"Replicated issue using Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1."
1720746,2020-09-19 08:13:41 UTC,Closing because INVALID: Can't replicate (Fixed).
1720749,2017-11-17 09:38:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720751,2017-10-02 13:21:45 UTC,"Thanks for reporting this bug and help making ubuntu better! This bug is an upstream GNOME bug, do you mind opening it against bugzilla (gnome-shell component)?"
1720751,2020-02-05 01:33:23 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1720757,2018-04-21 02:15:29 UTC,I was facing same issue in Magnum 5.0.1 with Fedora-Atomic 26 1030.
1720757,2017-10-10 12:53:57 UTC,"Fixed by editing fragments/make-cert.py , function write_server_key() , adding the next line:"
1720757,2017-10-02 17:50:11 UTC,I have seen this is in swarm experimental jobs as well: http://logs.openstack.org/76/508676/13/experimental/magnum-functional-swarm/39469ee/logs/cluster-nodes/master-test-172.24.5.12/etcd.txt.gz#_Oct_02_06_46_07
1720759,2017-11-18 21:36:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720759,2017-11-18 21:37:10 UTC,"Same here - unable to get an RX-550 working in ubuntu 16.04.  Tried several kernels, all to no avail."
1720759,2018-01-13 03:45:57 UTC,it's not the fault of clinfo if there is no ICD available that supports the hardware
1720760,2017-10-02 10:26:17 UTC,Attaching second screenshot referred to in original post...
1720760,2017-10-07 12:36:33 UTC,"Seems to have gone away with recent upgrades. I can't tell exactly which as I was attempting to use wayland under amd and even under nvidia-387 (which worked fine except for a couple of random system freezes during closing windows). Back on nvidia/xorg because of that (although not exhaustively tested that *that* isn't still going to happen), and the scaling problem appears to have resolved. Guessing that was fixed upstream in 3.26.1."
1720760,2020-01-16 08:07:54 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1720761,2017-10-10 13:48:25 UTC,The tripleo patch - https://review.openstack.org/#/c/509470/  fixes this issue.
1720761,2017-10-13 06:43:50 UTC,"Reviewed:  https://review.openstack.org/510754
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=f0c17319a9d48ec63e620c3510220fb88557a0c0
Submitter: Jenkins
Branch:    stable/pike"
1720761,2017-11-03 20:17:31 UTC,This issue was fixed in the openstack/puppet-tripleo 7.4.3 release.
1720770,2020-09-12 17:58:52 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1720770,2017-10-04 19:44:07 UTC,I replaced kubuntu repository FontForge by a more recent FontForge ppa and that doesn't fix the issue. Still I am not able to cut or copy from FF and paste in Inkscape Trunk.
1720770,2017-10-02 15:55:33 UTC,"Hi Jabier,
Thanks for your reply,"
1720770,2017-10-02 16:19:39 UTC,Strangely copying vectors from Illustrator 10 (under Wine) to Inkscape still works (while Inkscape to Illustrator doesn't work).
1720770,2017-10-02 13:34:22 UTC,"HI Ivan: Is because missing cut shorcut.
Workarround, use menu for Copy/Cut."
1720770,2017-10-02 23:09:31 UTC,"To me cut socks well with the mouse
Regards."
1720774,2017-10-02 12:00:11 UTC,"Confirm the problem on Raspberry Pi3 under Ubuntu mate, core 4.4.38-v7+"
1720774,2017-11-04 10:00:26 UTC,"Hi Sergey,"
1720774,2017-11-04 18:48:46 UTC,In this image you can see a printout showing the Dotty quality.
1720774,2017-11-18 21:49:08 UTC,"Same for me, with the HP LaserJet MFP m127fn, Raspberry Pi 3, Raspbian (Stretch)."
1720774,2017-11-20 13:45:36 UTC,"Hi,"
1720775,2020-08-04 17:05:44 UTC,"I can't reproduce a problem using Pinta 1.7-development.
Can you please try 1.7-development version if problem still appears?
https://www.pinta-project.com/releases/"
1720778,2017-11-18 21:40:56 UTC,"I have the same problem with the RP3 and the LaserJet Pro MFP m127fn using stretch. I've seen similar reports for LaserJet Pro MFP m1XXXX models with no solution. Honestly, I think it's just a bad driver which HP hasn't fixed. I've heard rumors that HPLIP-3.15.9 works. But I couldn't get it working on the latest distro (Stretch). If you can try it with wheezy or jesse, it might work; but the installer kept terminating at Error Code 2 when running the Make function."
1720778,2017-11-04 10:03:43 UTC,"Hi Sergey,"
1720788,2019-11-02 14:39:38 UTC,"This bug is still present okular Version 0.24.2
Using KDE Development Platform 4.14.16."
1720788,2018-08-03 02:49:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720788,2018-08-03 02:51:19 UTC,"I also experience this behaviour (thank you for describing how to work around it!), though my educated guess is that this is an upstream problem, i.e. it should be reported to the KDE developers."
1720788,2018-10-16 17:57:58 UTC,"I experience this too, zoom gets stuck between 200%, 150% and ""Fit Width"", but I am on Manjaro Linux 18.0.0-rc Illyria."
1720794,2017-10-02 18:15:43 UTC,"You want the upstream project, not Ubuntu."
1720795,2017-11-02 23:48:31 UTC,This issue was fixed in the openstack/python-mistralclient 3.1.4 release.
1720795,2018-01-30 21:51:12 UTC,This issue was fixed in the openstack/python-mistralclient 3.2.0 release.
1720811,2017-10-04 13:19:14 UTC,I've found the following collections where the region name is referenced:
1720811,2017-10-04 21:19:55 UTC,"@Felipe Reyes,
Cloud credential names currently carry more information than they should. We are about to change that soon.
However, even now, I believe that it contains the name of the cloud, not a region (although it's possible that there are exceptions).
All other places you have mentioned will, indeed, need to be updated when/if we allow users to update region name for a bootstrapped system."
1720815,2017-10-02 15:45:53 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1720816,2018-09-06 11:10:25 UTC,"We had similar issue with openstack Queens with swarm COE, after tracing code, observed that magnum-conductor stops after connection to public discovery endpoint, while creating cluster, I enabled and changed discovery url from https to http in maganum.conf and it worked for us."
1720816,2018-07-24 10:31:33 UTC,"I do not believe the patch I proposed (#12) has been applied upstream yet.
Have you tried applying this patch locally ? Does it help ?"
1720816,2018-07-24 10:06:30 UTC,"I am facing the same issue with openstack Queens, COE is K8S, kube_masters creation is failed"
1720816,2018-01-28 22:46:21 UTC,Updated patch
1720816,2018-01-26 08:45:30 UTC,"Thanks for the patch! I have applied it and the stack creation does progress further than previous attempts, but still eventually fails. This occurs on all COEs. Progress is best with Mesos, but fails at last step OS::Heat::WaitCondition. Will keep poking around."
1720816,2018-01-23 00:57:49 UTC,"I've done some more digging today, and got a handle on what is happening."
1720816,2018-01-22 10:14:27 UTC,"I believe I am seeing the same issue where Magnum (and Heat) have resources in the ""CREATE_IN_PROGRESS"" state for a long time, and eventually timeout. I'm using devstack (stable/pike) and the Mesos COE - but I suspect this is seen with other COE's"
1720816,2019-09-22 19:14:59 UTC,I had the same issue where the K8S cluster would be up  and running but the resource will `CREATE_FAILED` because of missing notification/
1720816,2017-11-06 17:25:36 UTC,"Thanks for the reply, I'm going to try again and i'll keep you posted."
1720816,2018-01-17 19:55:06 UTC,"Have the same issue here with Openstack Ocata (from cloud-archive). Ubuntu repos for xenial (16.04 LTS) still suffer from bug reported here: https://bugs.launchpad.net/magnum/+bug/1492695 since it's not up to Magnum 5.0.0 yet, so a git clone and source code compile is necessary. Kubernetes and Swarm COEs both give result of CREATE_FAILED."
1720816,2017-10-02 15:41:27 UTC,"I'm able to login to the instances created, I see some services on the master node are not running like flanneld, etcd, docker. I tried to start them manually and expected if that will help before the timeout. But nothing helped in creating the magnum cluster."
1720816,2017-10-02 16:06:51 UTC,heat.conf file attachment
1720816,2019-05-02 06:42:30 UTC,Check if swap is disabled the cluster VMs (flavor) and Magnum and Heat configured right
1720816,2017-11-02 21:36:43 UTC,same issue. I am running Pike.
1720816,2017-11-02 22:38:21 UTC,Yeah I got the same issue on Ocata and Pike Environments.
1720816,2017-11-03 18:42:25 UTC,"After some trials, I get pass that and CREATE_COMPLETE. (maybe it is not the same issue)."
1720816,2017-10-02 16:07:35 UTC,magnum.conf in attachment
1720818,2017-10-04 18:39:04 UTC,Does not need to go to xenial-security.
1720818,2017-10-05 20:27:06 UTC,"Azure and on-prem Hyper-V results are good. IB, BVT, Deployment, Perf, GPU, LTP, kdump, Docker, and Telegraf tests all passed. Please publish to updates."
1720818,2017-10-06 06:56:35 UTC,"4.11.0-1013.13 - azure
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1720818,2017-10-06 09:44:55 UTC,No bug was tagged with verification-needed.
1720818,2017-10-09 19:49:15 UTC,This bug was fixed in the package linux-azure - 4.11.0-1013.13
1720818,2017-10-09 20:05:32 UTC,The package has been published and the bug is being set to Fix Released
1720820,2019-09-10 02:30:02 UTC,Sounds like we have a semi-permanent workaround now:
1720820,2018-08-02 01:08:59 UTC,Uninstalling gstreamer1.0-vaapi does not solve the issue for me.
1720820,2018-05-08 03:39:19 UTC,See also bug 1767312.
1720820,2017-11-14 21:42:19 UTC,"I just got hit by this bug completely randomly. I did not wanted hardware acceleration, I just wanted to play some video and got black screen. It just happened that previously I had installed ubuntu-restricted-extras which automatically installs this vaapi thing. After I uninstalled ubuntu-restricted-extras i got my picture back."
1720820,2017-11-06 02:54:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720820,2017-10-26 03:00:04 UTC,Thanks. Please try this as a workaround:
1720820,2017-10-26 10:41:07 UTC,"That's okay, I already have some workarounds as described in the initial bug report, and Totem isn't my main video player of choice anyway."
1720820,2017-10-26 03:02:45 UTC,Although if you really need hardware acceleration then just use Xorg sessions rather than Wayland.
1720820,2017-10-04 08:47:56 UTC,"$ vainfo
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.40 (libva )
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc"
1720820,2017-10-26 11:02:32 UTC,"Not that I think it brings anything new to the table, but here's a screencast demonstrating the issue."
1720820,2017-10-04 07:52:48 UTC,"It sounds like gstreamer-vaapi has found a VA driver that it thinks will work, rather than none at all which should fall back to software rendering."
1720822,2020-08-15 19:22:22 UTC,Closing because this issue is tracked over at https://gitlab.com/inkscape/inbox/-/issues/1229.
1720827,2018-06-12 00:33:46 UTC,This is also applies to communitheme.
1720827,2017-10-04 03:27:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720830,2018-10-20 10:02:35 UTC,"Change abandoned by Dmitry Tantsur (<email address hidden>) on branch: master
Review: https://review.openstack.org/508946
Reason: The oneview driver is no longer maintained, so I guess this can be abandoned."
1720830,2017-11-13 22:08:00 UTC,"Could you please provide more details. By 'validation', what are you planning on adding/coding? New methods? Or adding code to existing methods?"
1720830,2017-11-21 15:35:12 UTC,"I'm not sure that this is an RFE -- it depends on what your intent is, wrt what do you mean by 'validation'."
1720836,2018-10-24 17:55:42 UTC,This still occurs in 18.10.
1720836,2019-04-26 16:39:06 UTC,This still occurs in 19.04
1720838,2017-10-03 20:18:57 UTC,"Created attachment 360874
screenshot of where I go to keep setting the scale"
1720838,2017-10-03 21:03:10 UTC,"Thanks for reporting this.
Which mutter version is this about? Setting the ""Version"" field is welcome."
1720838,2017-10-03 22:31:58 UTC,"Hi Andre,"
1720838,2018-08-15 04:54:05 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1720841,2017-10-02 16:52:48 UTC,"the example above *should* result in BOOTHOOK and BOOTCMD appearing in /var/log/cloud-init-output.log
and also appearing on the system console."
1720842,2018-08-26 10:21:15 UTC,"From Peter's description of the problem I guessed that it was wireshark setting promiscuous state on the virtual usbmon interface that caused the keyboard to go back to working state, which I knew should also be possible via tcpdump -i usbmon3 where usbmon3 is the interface that corresponds to the usb device in question."
1720842,2018-01-29 03:18:23 UTC,"I have the same problem with device id 1c4f:0101, but I have no problem with my Win10 on the same machine"
1720842,2017-10-07 07:12:33 UTC,"Does the VID:PID remain the same before/after the ""mode switch""?"
1720842,2017-10-04 12:23:30 UTC,"Hmm, OK, I'll have a look, thanks - might be a fun weekend project. Though it sounds like a new keyboard is a better option."
1720842,2017-10-06 22:42:09 UTC,"I was just sitting down to figure out how to write a device driver, and when I loaded the usbmon module and fired up wireshark the keyboard started behaving. The first few keys were captured with the ""modified"" keycodes that the usbhid driver doesn't recognize properly, then it seems to have switched into ""normal"" mode and behaved like a regular usb keyboard. I tried it on two computers with the same result, i.e. sudo modprobe usbmon, sudo wireshark ""fixes"" the problem for some strange reason. Now if only I could figure out how to trigger the mode switch in a less annoying way that would be great."
1720842,2017-10-03 21:55:38 UTC,No improvement with kernel 4.14.0-041400rc3-generic!
1720842,2017-10-03 21:30:02 UTC,Unfortunately I can't test 4.14-rc2 since it failed to boot.
1720842,2017-10-03 06:09:23 UTC,Can you attach evtest output for Ctrl / Super / Alt key pressing?
1720842,2017-10-02 17:42:19 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1720842,2017-10-04 08:45:50 UTC,"I think you need to capture the packet, and implements a new driver by yourself, like the azio driver author did:
https://swoogan.blogspot.tw/2014/09/azio-l70-keyboard-linux-driver.html"
1720842,2017-10-02 17:00:14 UTC,This change was made by a bot.
1720846,2017-10-06 12:15:48 UTC,"discover_hosts and its return codes are described here:
https://github.com/openstack/nova/blob/master/doc/source/cli/nova-manage.rst"
1720846,2017-10-06 12:54:26 UTC,Marking as incomplete until we can recreate or get failing output from 'nova-manage cell_v2 discover_hosts'.
1720846,2017-10-06 14:15:42 UTC,"Corey, can we add logging of nova-manage cell_v2 discover_hosts to the
charm?"
1720846,2017-10-06 16:01:57 UTC,I think adding --verbose to the call would make sense for the future and should send more verbose output to /var/log/nova/nova-manage.log.
1720846,2017-10-16 23:33:47 UTC,"Reviewed:  https://review.openstack.org/509900
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=3b873932be005eb6ec2b979fe72a92ece4fe905b
Submitter: Zuul
Branch:    master"
1720846,2017-10-17 01:16:03 UTC,"Hi Jason,"
1720846,2018-05-03 18:37:05 UTC,"Hi Jason,"
1720846,2020-07-24 11:20:25 UTC,"I just hit this in a charm gate job:
2020-07-23 10:37:15 ERROR juju-log cloud-compute:22: Cell1 discover_hosts failed
b""Getting computes from cell 'cell1': ef421f8f-5182-4014-bb1f-b9a93ebec5a5\nChecking host mapping for compute host 'juju-e09d65-zaza-c69af9d26505-8.project.serverstack': 8b52ad0c-4cf8-4c7d-984b-3283de75be4f\nCreating host mapping for compute host 'juju-e09d65-zaza-c69af9d26505-8.project.serverstack': 8b52ad0c-4cf8-4c7d-984b-3283de75be4f\nChecking host mapping for compute host 'juju-e09d65-zaza-c69af9d26505-6.project.serverstack': 54d39de2-671b-4c46-b31e-4e80202e1c27\nCreating host mapping for compute host 'juju-e09d65-zaza-c69af9d26505-6.project.serverstack': 54d39de2-671b-4c46-b31e-4e80202e1c27\nERROR: Duplicate host mapping was encountered. This command should be run once after all compute hosts have been deployed and should not be run in parallel. When run in parallel, the commands will collide with each other trying to map the same hosts in the database at the same time. Error: Host 'juju-e09d65-zaza-c69af9d26505-6.project.serverstack' mapping already exists\n""
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed Traceback (most recent call last):
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/cloud-compute-relation-changed"", line 1383, in <module>
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed     main()
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/cloud-compute-relation-changed"", line 1375, in main
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed     hooks.execute(sys.argv)
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/charmhelpers/core/hookenv.py"", line 945, in execute
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed     self._hooks[hook_name]()
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/cloud-compute-relation-changed"", line 674, in cloud_compute_relation_changed
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed     add_hosts_to_cell_when_ready()
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/cloud-compute-relation-changed"", line 689, in add_hosts_to_cell_when_ready
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed     ncc_utils.add_hosts_to_cell()
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/nova_cc_utils.py"", line 954, in add_hosts_to_cell
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed     subprocess.check_output(cmd)
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   File ""/usr/lib/python3.6/subprocess.py"", line 356, in check_output
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed     **kwargs).stdout
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   File ""/usr/lib/python3.6/subprocess.py"", line 438, in run
2020-07-23 10:37:15 DEBUG cloud-compute-relation-changed   ..."
1720846,2017-10-06 12:10:47 UTC,"Additionally, we only run discover_hosts if list_cells returns 'cell1' (this is the one cell that the charms deploy). This means that 'cell1' is already in the database, and therefore the database should completely be ready to run discover_hosts at this point."
1720846,2017-10-12 01:43:41 UTC,My theory in comment #19 is invalid. The script was running in a different process than the charm and the window I was seeing was actually during the charm's execution of 'nova-manage db sync'. I confirmed that the nova-manage commands do in fact run synchronously. So there is no race in the nova-manage commands as far as I can tell.
1720846,2017-10-06 11:56:47 UTC,My previous theory is invalid. We already check if >= ocata in add_hosts_to_cell() before doing anything. In fact we check that all of the following are true to ensure that the DBs are already set up as well prior to running cell_v2 discover_hosts:
1720846,2017-10-04 19:20:49 UTC,"After looking at the code again, I'm hesitant to drop add_hosts_to_cell, at least for the upgrade path. We could probably get away with not calling it on new installs. However it's useful on upgrades from non-cellsv2 to cellsv2, where existing hosts are discovered by 'nova-manage cell_v2 discover_hosts' and existing instances are mapped to cells right after that with a call to 'nova-manage cell_v2 map_instances'."
1720846,2017-10-05 20:44:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509900"
1720846,2017-10-04 18:33:31 UTC,"FYI, we disable failed hook retries in our CI tests.  We believe that the charm should never enter a failed/error state.  So any time the application unit workload state is error, we see that as a bug."
1720846,2017-10-06 01:50:55 UTC,I can't see the crashdump right now but it looks like what is happening here is a pre-ocata release is deployed (non cells_v2) and then the compute-changed hook attempts to run a cells_v2 command.
1720846,2017-10-04 18:41:51 UTC,"Having said that, we've not encountered this error in our deploys of openstack-base onto dell r610s via MAAS 2.2.2 and Juju 2.2.4.  Curious how frequently and how reproducible this is?"
1720846,2017-10-04 18:56:31 UTC,"It seems like there's a race somewhere, whether that's in nova or the charm I'm not sure. It'd be great to capture why the command is failing ('nova-manage cell_v2 discover_hosts'). Would you be able to manually run this command next time you hit this error?"
1720846,2017-10-04 18:35:39 UTC,"2017-09-30 10:35:38 INFO juju-log cloud-compute:27: Adding hosts to cell.
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed Option ""logdir"" from group ""DEFAULT"" is deprecated. Use option ""log-dir"" from group ""DEFAULT"".
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed Traceback (most recent call last):
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/cloud-compute-relation-changed"", line 1214, in <module>
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed     main()
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/cloud-compute-relation-changed"", line 1208, in main
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed     hooks.execute(sys.argv)
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/charmhelpers/core/hookenv.py"", line 768, in execute
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed     self._hooks[hook_name]()
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/cloud-compute-relation-changed"", line 706, in compute_changed
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed     add_hosts_to_cell()
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed   File ""/var/lib/juju/agents/unit-nova-cloud-controller-0/charm/hooks/nova_cc_utils.py"", line 817, in add_hosts_to_cell
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed     subprocess.check_output(cmd)
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed   File ""/usr/lib/python2.7/subprocess.py"", line 574, in check_output
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed     raise CalledProcessError(retcode, cmd, output=output)
2017-09-30 10:35:40 DEBUG cloud-compute-relation-changed subprocess.CalledProcessError: Command '['nova-manage', 'cell_v2', 'discover_hosts']' returned non-zero exit status 1
2017-09-30 10:35:40 ERROR juju.worker.uniter.operation runhook.go:107 hook ""cloud-compute-relation-changed"" failed: exit status 1"
1720846,2017-10-04 19:37:08 UTC,"I don't know if it's helpful, but I saw multiple deployments which had `nova-manage cell_v2` errors. In that case, I found that the nova-cloud-controller charm was issuing nova-manage command before having mysql information in nova.conf."
1720846,2017-10-04 19:57:26 UTC,"Re-triaging high, as it is affecting field deployments."
1720846,2017-10-05 19:29:36 UTC,I think I see what is going on here. I'll propose a fix.
1720846,2017-10-05 19:30:18 UTC,"Thanks Nobuto, that was a helpful comment."
1720846,2017-10-04 18:58:25 UTC,Triaging as medium since this doesn't always occur.
1720858,2017-10-07 17:15:18 UTC,"""The normal behavior when there is an error on a file is to remove the user as source for that file and move on the next."""
1720858,2017-10-07 17:18:11 UTC,"Oh, and obviously it won't proceed with the next file if the file trigger that error has higher priority than the other files"
1720858,2017-10-07 17:53:35 UTC,"Normal behavior might be the wrong word, but for other types of errors that is the kind of behavior I see."
1720858,2019-12-06 19:05:53 UTC,It is not rare and it is a big deal. For me it happens every day. It depends on how much you download. When i check my download queue i can have 10 bundles that haven't been downloaded because it got stuck on one single file.
1720858,2019-12-06 20:24:50 UTC,"When this error occur it should lower the priority to ""lowest"" or even ""paused"". If it change prio it will not download the file, but it will only be one unfinished bundle instead of 10."
1720858,2020-01-22 16:59:26 UTC,It seems to be the same if the disk is full. It will not download bundles on other disk because it get stuck at the higher prio bundles even if other lower bundles are downloaded to other hard drives with enough of free space.
1720858,2020-01-24 23:19:38 UTC,"I have also noticed that if i set a bundle to ""lowest"" it won't download a bundle with ""low"" even if i try to force it to start. If it has decided to download this bundle with ""lowest"" priority, it refuse to download a bundle with ""low"" even if the user is in that bundle too (the message tell me it won't start a bundle with lowest priority if other bundles are running). It seems that the download order won't change even if there is nothing that prevent it from downloading a bundle with ""low"" priority. So i believe this is also a similar issue as this."
1720867,2017-10-30 19:54:34 UTC,This bug was fixed in the package linux - 3.13.0-135.184
1720867,2017-10-17 16:59:45 UTC,"Taihsiang Ho (Canonical Cert) has performed the routine desktop certification test plan for SRU, and reports NO REGRESSIONS from the test kernel with this patch set:"
1720867,2017-10-27 11:30:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1720871,2018-10-24 23:44:51 UTC,"I've also had Node.JS suggest that I upgrade npm. After doing that recently, my build was broken. I do not recall the version number off the top of my head, but should be able to get it if necessary. We may want to assert maximum version numbers as well."
1720872,2017-10-04 08:32:24 UTC,"Hi,"
1720872,2017-10-04 14:09:53 UTC,"Hi Thomas,"
1720872,2017-10-04 15:13:02 UTC,"Hi Dan,"
1720872,2017-10-04 15:32:51 UTC,"Thanks, Thomas!  I learn something new everyday! :-)"
1720877,2020-09-23 23:36:57 UTC,The official lighttpd wiki lists an example.
1720878,2017-10-03 22:24:54 UTC,"Now that demo.evergreencatalog.com has been updated, I tested with 3.0.0, I tested the copy tag button there. I found that that the button is disabled in Chrome, but works fine in Firefox. I'm curious if others are also getting a disabled button or if it's an issue with my browser."
1720878,2017-10-03 22:32:50 UTC,"OK, I've discovered what the problem is. I must have previously set defaults for the working copy tab on the systems where the copy tag button was disabled. At the time I set those defaults, there was not copy tag button for which to set a default. As a result, the copy tag button remain unselected in the working copy defaults interface."
1720882,2020-11-16 08:37:06 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life on April, 2019"
1720882,2017-10-02 21:26:33 UTC,"StacktraceTop:
 g_settings_backend_watch_weak_notify (data=0x0, where_the_object_was=0x56e1830) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./gio/gsettingsbackend.c:155
 weak_refs_notify (data=0x42a43d0) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./gobject/gobject.c:2636
 g_object_run_dispose (object=0x56e1830) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./gobject/gobject.c:1082
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7f64c811ca58, fn=<optimized out>, rvalue=rvalue@entry=0x7ffcd9e58060, avalue=avalue@entry=0x7ffcd9e57f40) at ../src/x86/ffi64.c:525"
1720885,2018-08-05 00:20:37 UTC,"Vishakha, if you are still able to work on this, please reassign the owner to you and proceed. Thanks!"
1720885,2019-04-11 16:08:51 UTC,"The reason is luks-volume contains LUKS header in the device, it costs 2M (512bytes * 4096sectors)."
1720885,2019-08-02 09:28:34 UTC,"If this is an Encrypted Volume, why is the volumetype lvmdriver and not LUKS?"
1720885,2019-08-02 10:22:32 UTC,I configured an LVM Backend and tried this out and this worked fine for me.
1720885,2019-08-06 07:00:54 UTC,@Eric Harney .. The /etc/cinder/cinder.conf is very much needed to understand the root cause of the problem.
1720885,2019-08-21 05:00:40 UTC,"This worked fine for me but the Duplicate of this bug i.e.,"
1720885,2019-09-16 10:45:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/682339"
1720885,2019-09-16 12:42:44 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/682355"
1720885,2019-09-16 14:10:54 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/682355
Reason: Abandoning since there are issues here that are just going to cause test failures, and needs to be proposed to master first before backporting to stein."
1720885,2018-06-21 09:10:49 UTC,Hi all
1720886,2017-10-03 09:44:55 UTC,"Reviewed:  https://review.opencontrail.org/36175
Committed: http://github.com/Juniper/contrail-puppet/commit/284e368b196bdd37b664d1def59af9d65a6f30ff
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1720886,2017-10-03 05:52:35 UTC,"Review in progress for https://review.opencontrail.org/36175
Submitter: Nitish Krishna Kaveri (<email address hidden>)"
1720889,2017-10-04 18:30:20 UTC,The hang of teh script happened while installing within a graphical session. I managed to install from within a framebuffer session i.e. a session accessed using Ctrl+Alt-F*
1720893,2019-08-08 05:03:05 UTC,"While there is no side effect on the behavior level, this is noisy enough and we should clean this up."
1720893,2019-08-08 07:11:35 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/675256"
1720893,2019-09-10 05:48:59 UTC,"Change abandoned by Akihiro Motoki (<email address hidden>) on branch: master
Review: https://review.opendev.org/675256"
1720893,2019-09-10 09:28:03 UTC,"Reviewed:  https://review.opendev.org/680996
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8343014eceb1ada33267be4e671de5690c79d117
Submitter: Zuul
Branch:    master"
1720893,2019-09-11 15:27:54 UTC,"Reviewed:  https://review.opendev.org/681034
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=86d13968d889a9d6293a517390d7f53044f5e567
Submitter: Zuul
Branch:    master"
1720893,2020-03-09 15:53:31 UTC,"Change abandoned by Walter Doekes (<email address hidden>) on branch: master
Review: https://review.opendev.org/695892
Reason: ""the goal is to fix all of those eventually"" -> no need to ignore them"
1720893,2020-03-12 15:50:43 UTC,"Change abandoned by Walter Doekes (<email address hidden>) on branch: stable/train
Review: https://review.opendev.org/693005
Reason: I abandoned the master one too"
1720901,2018-01-23 03:01:13 UTC,To clarify:
1720901,2018-01-23 03:18:07 UTC,Please try the current deb version in Ubuntu 18.04 ( 3.0.0~rc4-1ubuntu1).
1720901,2018-01-24 13:10:39 UTC,I just tested vlc 3.0.0-rc4 in a Ubuntu 18.04 live session and I can confirm that the problem is fixed there.
1720901,2018-01-24 15:40:21 UTC,"Thanks, marking as fixed again. Regarding vlc 3.0.0 in 17.10, you'll need someone who's familiar with the Ubuntu's policy on that."
1720901,2018-01-25 01:18:03 UTC,"Wait, isn't the live session Xorg, not Wayland?"
1720901,2018-08-05 01:16:32 UTC,"I have Ubuntu 18.04 and VLC 3.0.3 and I am affected by this bug.
I also think that no matter what GUI API is called, the system should allow quitting the app at worst. But not even Ctrl+Alt+Fx functions work to switch to terminal."
1720901,2018-08-24 07:38:23 UTC,"VLC media player 3.0.3 Vetinari
It freezes on fullscreen. I'm new to ubuntu so i don't really understand the threads. Can someone enlighten me. Thanks!"
1720901,2018-08-06 02:12:31 UTC,This bug is closed (the status is Fix Released). So yes you will need to open a new bug...
1720901,2018-08-08 13:56:43 UTC,I can confirm that I am experiencing the same bug again since the vlc update to 3.0.3
1720901,2018-01-23 02:05:10 UTC,Certainly as the original reporter you have the right to reopen this bug if you say it's not fixed.
1720901,2018-08-24 07:55:41 UTC,"Since the original reporter confirms the bug was fixed for a while prior to version 3.0.3, it would be best to open a new bug and mention there what version the regression occurred in."
1720901,2018-09-01 03:20:08 UTC,"New bug (same issue, on VLC 3.0.3/Ubuntu 18.04) is here:"
1720901,2018-08-05 01:18:04 UTC,So should I just duplicate this to a new bug?
1720901,2018-01-22 19:14:16 UTC,"I don't understand why that bug was marked as fixed when the standard vlc package in Ubuntu is obviously not fixed and still causing those crashes and bothering users. And I really don't see the point for opening a new bug report for the same old problem, so I just changed the status of this bug."
1720901,2018-01-24 12:14:51 UTC,"Marking as incomplete until Simon tested vlc 3.0.0 as provided by Ubuntu. FWIW, vlc 2.2.x won't see any Wayland fixes. If you use Wayland and vlc, you'll need to use 3.0.0."
1720901,2018-01-19 15:10:12 UTC,"This bug is driving me nuts, I've lost my data countless times because I always forget to *avoid* using VLC in fullscreen mode and to leave the damn position cursor alone. Sometimes I can kill vlc and save, other times it just freezes and I have to say goodbye to whatever I was working on."
1720901,2017-10-02 23:30:33 UTC,apport information
1720901,2017-10-02 23:30:34 UTC,apport information
1720901,2017-10-02 23:30:38 UTC,apport information
1720901,2017-10-26 08:25:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1720901,2017-10-26 08:25:45 UTC,vlc is being ported to wayland but whatever a client is doing gnome-shell shouldn't lock
1720901,2017-10-27 15:44:24 UTC,Created an upstream bug report for the gnome-shell: https://bugzilla.gnome.org/show_bug.cgi?id=789563
1720901,2017-10-02 23:30:36 UTC,apport information
1720901,2017-11-18 22:52:12 UTC,"Affects me a swell, Ubuntu 17.10."
1720901,2017-10-28 12:05:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720901,2017-12-25 13:05:36 UTC,I can still reproduce those system freezes with VLC 3.0.0 installed as a snap.
1720901,2017-12-17 21:19:06 UTC,This bug was fixed in the package vlc - 3.0.0~rc1-1ubuntu1
1720901,2018-01-22 05:02:41 UTC,"This bug has been marked as closed (Fix Released), rightly or wrong, already. So if you have any continuing problems it would be most helpful to open a new bug using this command:"
1720901,2017-11-20 08:31:07 UTC,upstream seems to consider it's not a gnome-shell bug that it doesn't deal with the case better and vlc just needs to be fixed
1720901,2017-10-02 23:30:31 UTC,apport information
1720901,2017-11-19 09:53:57 UTC,Temporary workaround:
1720906,2017-10-03 00:10:36 UTC,"StacktraceTop:
 get_shadow_width (window=0x0, shadow_width=shadow_width@entry=0x7fff30021ff8) at ././gtk/gtkwindow.c:6867
 _gtk_window_get_shadow_width (window=<optimized out>, border=border@entry=0x7fff30021ff8) at ././gtk/gtkwindow.c:12347
 gtk_menu_position_legacy (set_scroll_offset=1, menu=0x5629567ba2c0) at ././gtk/gtkmenu.c:4921
 gtk_menu_position (menu=menu@entry=0x5629567ba2c0, set_scroll_offset=set_scroll_offset@entry=1) at ././gtk/gtkmenu.c:5231
 gtk_menu_popup_internal (menu=0x5629567ba2c0, device=<optimized out>, parent_menu_shell=<optimized out>, parent_menu_item=<optimized out>, func=<optimized out>, data=<optimized out>, destroy=<optimized out>, button=<optimized out>, activate_time=<optimized out>) at ././gtk/gtkmenu.c:1977"
1720932,2017-10-03 06:09:24 UTC,"Can you run it with ""-x"" and do "">2&1 | tee debug.log"" and attach that?  thank"
1720932,2017-10-03 08:49:00 UTC,"Log added,"
1720932,2017-10-04 09:29:37 UTC,"I did not use -x option, because the input image is already *.qcow2"
1720959,2017-10-03 07:21:36 UTC,gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
1720961,2017-10-03 08:00:04 UTC,This change was made by a bot.
1720974,2017-10-03 08:50:10 UTC,Link to upstream bug (I could not add it to launchpad):
1720974,2017-10-03 08:54:28 UTC,Thank you for your report!
1720974,2017-10-03 09:11:04 UTC,"The ""size does not fit in an int"" error message is an apport problem and the stack trace I uploaded is perfectly correct."
1720974,2017-10-03 09:11:40 UTC,Confirmed because the upstream tracker has several duplicates of this bug.
1720976,2018-01-26 18:56:51 UTC,I have tested on artful here with a NetworkManager wired connection with static DNS and cannot reproduce the problem.
1720976,2017-11-18 13:55:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1720976,2017-10-03 20:03:14 UTC,Fresh boot of Artful (static IP via network manager and DNS should be at 192.168.1.1) -> NetworkManager has integration with systemd-resolved and thus should pass DNS information to resolved.
1720976,2017-10-06 07:35:12 UTC,"bp1@dimension:~$ nmcli
enp8s0: connected to Ethernet connection 1
 ""Broadcom Limited NetXtreme BCM5754 Gigabit Ethernet PCI Express (Precision T5400)""
 ethernet (tg3), 00:1E:4F:E9:F1:C1, hw, mtu 1500
 ip4 default
 inet4 192.168.1.5/24
 route4 169.254.0.0/16
 inet6 fe80::99f:fae5:1467:a576/64"
1720976,2017-10-06 07:40:01 UTC,Should also add that there is the same problem when I enable dhcp and let the network manager do dhcp.
1720977,2017-10-03 08:52:43 UTC,"commit 98d068ab52b4b11d403995ed14154660797e7136
Author: hayeswang <email address hidden>
Date:   Tue Mar 14 14:15:20 2017 +0800"
1720977,2017-10-07 06:14:14 UTC,I assume this is going to xenial as well
1720977,2017-10-18 08:57:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1720977,2017-10-18 08:59:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1720977,2017-10-30 06:45:20 UTC,Verified on v4.4.0-98 and v4.10.0-38. It's fixed.
1720977,2017-10-30 19:26:53 UTC,This bug was fixed in the package linux - 4.10.0-38.42
1720977,2017-10-30 19:43:07 UTC,This bug was fixed in the package linux - 4.4.0-98.121
1720983,2017-11-03 20:11:09 UTC,This issue was fixed in the openstack/tripleo-common 5.4.5 release.
1720983,2017-10-03 12:26:57 UTC,Note we no longer use the tripleo-common LP so I added the main tripleo LP to this bug.
1720983,2017-10-13 07:44:45 UTC,"Reviewed:  https://review.openstack.org/509079
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=fb9fa9844ca079d6322eaeb00564dc4bba324c3c
Submitter: Jenkins
Branch:    stable/newton"
1720985,2017-10-09 11:43:59 UTC,We are no longer using python-k8sclient.
1720985,2017-10-16 16:28:49 UTC,The Ubuntu packages patch in the python-k8sclient as the kubernetes client isn't a debian package in the Ubuntu archives.
1720985,2017-10-23 10:04:59 UTC,I'm not sure what comment #2 means. This issue in magnum is fixed since ocata [1].
1720985,2017-11-24 13:09:43 UTC,"Hello,
Coming back to this issue - using stable/pike now, kubernetes package is installed using pip, but the same happens:"
1721002,2020-07-01 20:56:08 UTC,"From the DpkgTerminalLog.txt, this actually occurred prior to the apache2 installation, appears to be an issue with plymouth and urandom being interdependent:"
1721003,2017-10-03 13:29:54 UTC,"Hello Raildo,"
1721003,2017-10-03 13:13:46 UTC,"Hi Cédric,"
1721003,2017-10-03 13:32:53 UTC,"oh and I'm speaking about IPA Vault, not the Hashicorp Vault thinggy. Of course, projects having the same name are a trend ;)."
1721003,2017-10-03 12:38:57 UTC,I guess it depends on what operations you want the novajoin user to be able to perform.
1721003,2017-10-03 12:18:38 UTC,"Hello Rob,"
1721003,2017-10-03 12:13:51 UTC,Not sure what you have in mind here. The nova interaction with IPA via novajoin is to manage IPA host entries when nova instances are created or destroyed.
1721003,2017-10-03 12:42:34 UTC,"Hmm yep. That's for the undercloud rights - for the overcloud, I think it would be a bit less ""admin"": undercloud might create a sharedVault and add the roles it creates for the hosts to that shared vault. That would be the smartest."
1721005,2017-10-07 00:10:04 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1721012,2018-01-22 17:44:27 UTC,I agree. The empty box is not intuitive.
1721012,2018-11-16 20:07:18 UTC,EG v. 3-2-0
1721012,2020-11-12 16:54:30 UTC,Noting that this is still an issue in EG 3-6-0
1721024,2017-10-03 13:36:22 UTC,"One of the use cases for copy tags is to display ""digital bookplates"", i.e., donor acknowledgments. If one is going to acknowledge a donor in the public catalog, one might want to emphasize it, so I disagree that copy tags should necessarily be styled the same as copy notes."
1721024,2017-10-03 14:04:46 UTC,I agree that the distinct classes should definitely remain so that local sites can style each element however they wish.
1721026,2018-11-16 20:16:31 UTC,Confirmed EG 3-2-0
1721026,2018-12-14 17:47:52 UTC,"Additionally, only those org units relating to the user's permissions should display on the dropdown menu.  Currently, all org units display on the menu and it is possible to select an unrelated org unit and to create a new tag type for that org unit."
1721026,2018-12-14 18:17:09 UTC,"On a related note: It is possible to select a different org unit as the owner of a copy tag type that you created for your own org unit.  Once you give ownership to a different org unit, it is not possible to edit the owner again."
1721026,2020-11-16 19:15:01 UTC,EG 3-6-0
1721031,2017-10-03 15:16:48 UTC,"Catherine,"
1721031,2017-10-04 14:15:38 UTC,"Kathy,"
1721031,2017-10-04 14:17:08 UTC,"I should also clarify that the foreign items display when you are looking at ""Bib A"" not the other bibs"
1721035,2018-02-23 18:39:20 UTC,Updated as of today.
1721035,2018-07-27 13:55:55 UTC,I noticed today that 'apt-get autoremove' in an amd64 cloud image will offer to remove grub-pc-bin.
1721035,2020-02-19 16:32:29 UTC,"well, looked at a minimal focal image and came across this again.
We could save almost a whole 1% there."
1721035,2020-02-19 16:44:24 UTC,"Running this ""apt-get autoremove --purge"" on first boot is annoying, would be nice to get rid of this as it also causes some noise when installing packages because apt reminds you to do a cleanup :)"
1721036,2019-09-01 13:49:32 UTC,"Pushed to master.  Thanks, Remington and Kyle!"
1721036,2019-04-24 18:52:20 UTC,"Here's a branch that adds the URL field in the DB, IDL and uses it as a link in the OPAC.  (NOTE: If you're applying this patch manually, not building a fresh install, don't forget to copy the IDL both to /openils/conf/ and to /openils/var/web/reports/.)"
1721036,2019-07-03 18:31:47 UTC,"To answer your question, I would think the html filter would be sufficient here."
1721048,2017-10-03 14:32:36 UTC,"This patch changes the memaslap statistics to be per-thread, avoiding the need to synchronize when updating them."
1721048,2017-10-03 14:34:26 UTC,"This patch replaces rand() with rand_r(), improving the scalability of memaslap. (The glibc implementation of rand() takes an internal lock.)"
1721049,2017-10-18 06:50:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721049,2017-10-19 18:05:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1721049,2018-02-14 01:23:53 UTC,"I submitted a patch for the ubuntu-reviews plugin within GNOME Software, https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/11, which has now been merged by Robert. Hopefully this fix will now make it into a stable ubuntu release (18.04?)."
1721049,2018-05-02 23:26:31 UTC,"This bug has been fixed with gnome-sofware 3.28, which is found in Ubuntu 18.04 (bionic)."
1721049,2019-01-02 18:08:58 UTC,I have this message from Ubuntu Software trying to write a review on a snap application. After which my report appear with reporter name 'unknown'
1721053,2019-10-01 18:57:30 UTC,"More robust functionality is needed with setting hold maximums.  To add to the issue description – while we can restrict holds per single permission group per single circulation modifier, there are multiple unmet needs for max holds configuration.  Desired functionality includes adding the ability to:  (1) set a maximum number of holds per a set of circ modifiers for a single permission group (hold limit sets – similar to circulation limit sets as suggested) – ex:  apply one max for multiple audiovisual types and (2) set a patron threshold for maximum number of holds allowed similar to patron checkout threshold – ex: Juvenile patrons limited to 25 holds"
1721053,2019-10-01 19:06:40 UTC,Confirmed in 3.3
1721053,2019-10-08 15:10:44 UTC,"Many locations want to be able to set a max holds, so any improvement to this would be welcomed."
1721061,2017-10-03 20:00:28 UTC,Looks like the updates have already landed in the repos for raspbian jessie and stretch. The fix for buster should drop through in a few days.
1721068,2017-11-20 19:02:10 UTC,I have gotten around this issue. I am not sure if there was anything found by developers in the community but I see this issue now has a milestone set.
1721068,2017-10-10 18:45:16 UTC,"is there anyone looking at this question who develops in this area of Fuel, which deals with cloud-init on newly provisioned nodes?"
1721074,2018-01-15 03:07:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721074,2018-06-21 23:49:00 UTC,"Hello there,"
1721074,2018-06-25 17:02:59 UTC,"Thanks, fix worked for me (related: https://bugs.launchpad.net/bugs/1747023 )"
1721076,2017-10-07 00:08:11 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1721076,2017-10-09 02:23:43 UTC,Sounds like bug 1639584
1721082,2017-10-10 02:14:15 UTC,This bug was fixed in the package unity - 7.5.0+17.10.20171004-0ubuntu1
1721082,2017-10-10 10:26:35 UTC,This bug was fixed in the package gnome-session - 3.26.1-0ubuntu1
1721088,2017-10-03 17:47:20 UTC,You may need to run the following from a terminal:
1721090,2018-01-18 08:29:15 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2006
1721090,2017-10-12 09:44:16 UTC,Same in Debian Stretch package
1721090,2017-10-04 09:34:29 UTC,PXC node can be started with the log_error_verbosity=2 through binary. Possibly a packaging problem.
1721090,2017-12-15 12:08:31 UTC,Any update on this issue? Affects also latest 5.7.20-18-1.stretch. I could provide some log/config files if needed.
1721092,2017-11-10 11:45:24 UTC,"Hello, can I do anything for this to progress toward a solution ?"
1721092,2018-01-26 18:41:15 UTC,This may be related to LP: #1694156.
1721092,2018-01-28 18:35:29 UTC,"Hello,"
1721092,2018-01-28 22:17:45 UTC,"Ok.  It looks, from what I can interpret of the --status output, like your /etc/systemd/resolved.conf.d/lxc.conf is not having the intended effect, and queries are perhaps being passed to the lxc dns server that perhaps should not be.  This may still be related to LP: #1694156.  Would you be able to provide a network trace, showing what queries are being sent at the time systemd-resolved is spinning?"
1721092,2018-01-29 10:59:29 UTC,"Hello,"
1721092,2018-03-04 22:02:42 UTC,"hello in bionic
i also tried to get systemd.resolve and dnsmasq working"
1721092,2018-03-05 02:02:13 UTC,"added to dnsmasq.conf cli --dns-loop-detect
this stopped the cpu overdrive .. also allowed only resolution of the containers.. lost the real world."
1721093,2018-12-05 17:55:36 UTC,I think that the splitted query got broken when we started to have ansible result printed as formatted json insteadd of one line json.
1721093,2017-12-22 00:17:45 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Make%20sure%20this%20host%20can%20be%20reached%20over%20ssh%5C%5C%5C%22%2C%20%5C%5C%5C%22unreachable%5C%5C%5C%22%3A%20true%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d
1721093,2018-02-27 16:42:35 UTC,This is actually a result of zuul.o.o losing access to zookeeper (nodepool.o.o) and then nodepool-launcher seeing the locks on the zookeeper requests being removed.
1721094,2017-10-03 17:56:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1721094,2019-06-12 11:57:09 UTC,It is reported there too: https://gitlab.gnome.org/GNOME/sushi/issues/2.
1721094,2019-06-12 11:57:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721095,2017-10-03 19:15:55 UTC,Can you please upload the competition file (.cotcot) used when the crash occurred?
1721095,2017-10-04 21:05:12 UTC,"Unfortunately, it had been open a while, and I am not sure which cot cot
file was active."
1721106,2019-09-19 12:04:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1721109,2019-03-04 22:28:49 UTC,Here's a new branch: user/sandbergja/lp1721109_update_item_status_after_holdings_changed
1721109,2019-03-07 19:39:53 UTC,"I see this working as advertised.  Pushed to master and rel_3_2.  Thanks, Jane!"
1721109,2019-03-05 01:08:31 UTC,"Just a note that I'd messed up handling some of the promises, so I force-pushed a fix to that same branch.  :-)"
1721109,2019-02-28 16:35:13 UTC,I'm going to try a BroadcastChannel-based solution to this for bug squashing week (inspired by Cesar's work here: https://bugs.launchpad.net/evergreen/+bug/1684202).
1721109,2018-08-08 16:49:01 UTC,+1 to Jane & Janet's comments
1721109,2018-05-31 18:49:22 UTC,"Oops, I meant ""what information is current, and which is out-of-date."""
1721109,2018-05-31 17:58:48 UTC,"+1 to Jane's comment.
After our upgrade to web client 3.0, not being able to see changes in Item Status has been one of our biggest frustrations. Libraries report items not being edited when the edits have happened."
1721109,2018-05-24 22:00:46 UTC,We would prefer either:
1721109,2018-01-26 15:50:31 UTC,I see value in both approaches and could also see where there might be circumstances where a user would want the two lines and others where it wouldn't be necessary. I think a checkbox to control the behavior on the screen itself would be a great solution.
1721109,2018-11-16 19:06:15 UTC,+ 1 to Jane & others
1721116,2017-10-20 07:32:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721116,2017-10-25 13:57:31 UTC,"I am seeing this with Ubuntu 17.04, using Gnome Shell."
1721117,2020-01-24 09:59:11 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1721117,2017-10-16 15:20:55 UTC,"In this morning's test of 17.10 beta 2, this extension now works:"
1721117,2017-10-05 09:36:26 UTC,Are extensions able to test if currentMode inherits from 'user'? If so then that would be a fix. If not then it sounds like mode 'ubuntu' is going to be a recurring problem in future.
1721117,2017-10-04 07:39:25 UTC,That was an overstatement; I'm just guessing. Not working on it.
1721117,2017-10-04 07:24:30 UTC,I don't know how the harcoded Ambiance theme compared to the gnome.css one can influence that. Do you mind expanding if you already had a start debugging Daniel?
1721117,2017-10-04 03:07:17 UTC,Confirmed. Looks like this might be caused by the hard-coded Ambiance theme in the panel.
1721117,2017-10-04 03:06:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721117,2017-10-05 09:31:46 UTC,Here is some analyze of those extension:
1721131,2020-08-31 19:54:57 UTC,"I'm okay with the Include Inactive box being sticky, but FWIW, our libraries are supposed to always search inactive patrons because it's one of the main ways we run across duplicate accounts. Unchecking the box should be a rarity for us."
1721131,2021-02-09 22:34:06 UTC,Removing pullrequest as there is some disagreement about what Clear Form should actually do
1721131,2020-09-01 13:54:18 UTC,"Maybe I am misunderstanding something here, but if we make the decision to revert back to the most recent sticky settings, doesn't that completely defeat the purpose of the ""Clear Form"" button?"
1721131,2020-08-31 19:38:10 UTC,I agree with Jane regarding the Home Library org unit selector. Reverting the selector to the sticky setting when using the Clear Form button makes logical sense.
1721131,2020-02-26 21:12:37 UTC,"Hello, EG 3.3.4 - Just noticed something similar, but may not be exactly the same."
1721131,2020-02-28 16:54:59 UTC,"It took me way too long to realize that an input type=""reset"" button resets all form controls after the clearForm() function is run.  Have to change that to a regular button."
1721131,2020-02-27 17:58:07 UTC,"For PINES libraries, we want Clear Form to always re-set to the consortium level. *Almost* every patron search that our staff does should be scoped to consortium level."
1721131,2018-11-06 22:02:34 UTC,"In 3.2.1, at least, performing a search with org unit set to ""Home Library"", the search only returns patrons with the home library of my workstation's."
1721131,2018-01-05 16:05:54 UTC,"I can confirm this bug as well. Also, once the org unit is set to ""Home Library"" the search returns no results."
1721131,2020-08-18 02:29:15 UTC,"Thanks for the pull request, Josh!  It definitely works as advertised; whenever I click on ""Clear Form"", the org selector goes to CONS."
1721133,2017-10-05 19:23:48 UTC,Adding a link to a discussion on IRC:
1721133,2017-10-13 16:59:40 UTC,Adding a log thread trace for an occurrence of this that happened on 10/11. This threadtrace contains references to a Jabber layer error in the osrfsys.log:
1721138,2017-10-04 21:42:06 UTC,Reassigning to gnutls26. But I'd recommend upgrading to xenial which has a gnutls version that can actually handle modern HTTPS connections.
1721138,2017-10-17 18:50:05 UTC,"Thanks Julian, I work for a company with thousands so the process of migration all the servers is a little slow but based on or security team we need to move all our HTTP traffic to HTTPS. That's the reason why I filed the bug."
1721144,2020-05-14 14:57:58 UTC,"Since bug 1740412 is released, can this bug be set to Fix Released? Or does comment #4 indicate there is still an issue?"
1721144,2019-03-08 20:55:12 UTC,The state in 3.2.0:
1721144,2017-12-28 17:33:12 UTC,See also: https://bugs.launchpad.net/evergreen/+bug/1740412
1721144,2017-10-03 22:33:02 UTC,It would be nice to be able to double-click on a line or even just hover over a line to see the full message.
1721144,2017-10-04 16:23:48 UTC,This strikes me as something that could turn into a general improvement to egGrid to provide a way to better deal with grid cells with long content.
1721147,2021-02-23 14:15:58 UTC,"This ticket becomes moot with the notes consolidation project:
https://bugs.launchpad.net/evergreen/+bug/1846354"
1721153,2017-10-21 15:22:04 UTC,SOLVED:
1721154,2017-10-04 23:19:55 UTC,"a patch like
              http://paste.ubuntu.com/25676319/ which results in (IMO) improved
              behavior as: http://paste.ubuntu.com/25676320/"
1721154,2017-10-04 23:20:22 UTC,"Note that after reading the code, we fallback to manual reading of the d/s/format file if it exists, so it's not terrible. But we should make this less noisy."
1721155,2017-11-12 17:40:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721158,2017-10-04 06:19:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721158,2019-11-24 00:02:52 UTC,"Hello,"
1721158,2020-01-23 04:19:29 UTC,[Expired for gnome-music (Ubuntu) because there has been no activity for 60 days.]
1721159,2017-10-04 09:02:01 UTC,"I've looked over the charm, and this really seems to be a Juju bug. There is a single leadership setting, and it gets set in the leader-elected hook and is never unset. The deployment would never complete unless this setting actually gets set."
1721159,2017-10-04 19:54:58 UTC,"This environment is currently running 1.25.13.  Here's a potted history, based on machine-0:"
1721159,2017-10-04 21:33:16 UTC,"@Paul Collins (pjdc), Stuart Bishop (stub),"
1721159,2017-10-27 02:20:00 UTC,"We are in the process of replacing all of these Juju 1.x environments with 2.x.  If it crops up on 2.x, we'll let you know."
1721161,2017-11-22 01:35:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721174,2017-11-19 20:56:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721175,2018-01-15 05:11:19 UTC,"Change abandoned by Nisha Agarwal (<email address hidden>) on branch: master
Review: https://review.openstack.org/509964
Reason: Abandoning the patch as the Scalable Persistent Memory feature has been released"
1721175,2017-10-06 04:10:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509964"
1721175,2018-01-15 05:10:33 UTC,"Change abandoned by Nisha Agarwal (<email address hidden>) on branch: master
Review: https://review.openstack.org/509960
Reason: Abandoning the patch as the Scalable Persistent Memory feature is released"
1721179,2017-10-08 04:06:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510324"
1721179,2018-05-02 12:02:09 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1721179,2018-02-19 17:53:35 UTC,"Reviewed:  https://review.openstack.org/513721
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d34222286b2a215744d225b24d1548f93bc8515a
Submitter: Zuul
Branch:    stable/ocata"
1721179,2018-02-15 23:53:34 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1721179,2018-03-06 11:40:29 UTC,"The commit provide a command to delete host in ""host_mapping"" table. And does not seem to solve the problem completely.
For first case:"
1721179,2017-10-24 12:41:34 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1721179,2017-10-20 12:32:23 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/513721"
1721179,2017-10-20 12:18:26 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/513717"
1721179,2017-10-19 19:54:20 UTC,"Reviewed:  https://review.openstack.org/510324
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f4f17b364e28389f22bf9c6017dd7aef918c7104
Submitter: Zuul
Branch:    master"
1721179,2018-02-01 21:38:44 UTC,"Reviewed:  https://review.openstack.org/513717
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=868ef987625d6867dc0e315af6245776fa2da18a
Submitter: Zuul
Branch:    stable/pike"
1721180,2019-09-20 12:35:46 UTC,Having the package installed by default is not sufficient for notifications to be displayed when a long-running command completes.
1721190,2018-01-25 09:38:49 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3746
1721200,2017-10-23 11:26:48 UTC,"Fix proposed to branch: stable/17.02
Review: https://review.openstack.org/514260"
1721200,2018-01-07 08:08:27 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: stable/17.02
Review: https://review.openstack.org/514260"
1721200,2017-10-26 20:57:02 UTC,copying Haw's comment in gerrit here for the stable/17.02 backport:
1721200,2017-10-20 17:41:16 UTC,"Reviewed:  https://review.openstack.org/513795
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=91490b7daf7511a717f75f62b57fc3f97cc6d740
Submitter: Zuul
Branch:    stable/17.08"
1721200,2017-10-20 16:23:47 UTC,"Fix proposed to branch: stable/17.08
Review: https://review.openstack.org/513795"
1721200,2017-10-20 09:18:49 UTC,"Reviewed:  https://review.openstack.org/513361
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=b4d8247f76bc756f504c5f98242bd0b7d3278a78
Submitter: Zuul
Branch:    master"
1721200,2017-10-05 09:14:01 UTC,It looks like there is a specific code path for a subordinate to find out information about the principle for juju 1.X:
1721200,2017-10-19 10:35:33 UTC,It's actually this non-ASCII character in the metadata.yaml file:
1721200,2017-10-05 13:42:41 UTC,<tl;dr> I really don't think this is a bug in the keystone charm.</tl;dr>
1721200,2017-10-19 20:30:37 UTC,For the keystone charm - https://review.openstack.org/#/c/513361/
1721200,2017-10-19 23:27:22 UTC,For charm-helpers - https://github.com/juju/charm-helpers/pull/25
1721202,2017-10-04 07:57:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/509367"
1721202,2017-10-05 02:48:34 UTC,"Reviewed:  https://review.openstack.org/509367
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=9762cc6ac44ed04e98eb2514775813c777404236
Submitter: Jenkins
Branch:    master"
1721205,2020-11-23 15:01:35 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1721206,2020-09-12 08:20:19 UTC,Closing because INVALID.
1721217,2017-10-16 15:47:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721223,2017-11-18 08:58:37 UTC,This bug was fixed in the package systemd - 235-2ubuntu3
1721223,2017-11-25 18:49:37 UTC,"Fwiw, this is fixed upstream now with https://github.com/systemd/systemd/pull/7167"
1721223,2018-02-22 18:36:25 UTC,"Hello Nicolino, or anyone else affected,"
1721223,2018-03-08 17:32:57 UTC,"Hello Nicolino, or anyone else affected,"
1721223,2018-03-19 14:31:12 UTC,"root@systemd-sru-xenial:~# dpkg-query -W systemd
systemd	229-4ubuntu21.1"
1721223,2017-10-23 10:10:28 UTC,"Fwiw, I reported a RFE upstream to warn if networkd is used and promote_secondaries is unset (https://github.com/systemd/systemd/issues/7163)"
1721223,2018-03-21 11:42:35 UTC,This bug was fixed in the package systemd - 234-2ubuntu12.3
1721223,2018-03-21 11:42:58 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1721223,2018-03-21 11:53:33 UTC,This bug was fixed in the package systemd - 229-4ubuntu21.2
1721223,2020-03-11 05:20:00 UTC,Want a seamless website to transfer money through mobile. You can also visit at: https://www.apponlinesolutions.com and get the resolution from our cash app technical number right away!
1721223,2018-03-19 14:21:52 UTC,"Starting with ephemeral lxd container, on a system with app/promote_secondaries set to 0:"
1721223,2017-10-13 13:48:52 UTC,"On Fri, Oct 13, 2017 at 01:22:23AM -0000, Dimitri John Ledkov wrote:

> > Can networkd be made to work without relying on this sysctl tweak? If
>
> No, as the alternative is what isc-dhcp /sbin/dhcp-client does that is
> flush current dhcp lease IP and add a new IP, meaning that networking
> is dropped =/
> Which to me is horrifying.
"
1721223,2017-10-11 20:41:28 UTC,I believe both promote_secondaries and default qdisc changes are good changes for our distribution to make.
1721223,2017-10-12 16:31:22 UTC,"What about server use cases that do not have networkd installed? There are complex network setups out there, such as HA with corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this fix were SRU'd, will all of these things in the wild cope with this sysctl change?"
1721223,2017-10-11 16:29:36 UTC,"> This update also applies other safe-looking options, which are currently also already applied via sysctls shipped in other packages
"
1721223,2017-10-06 19:35:53 UTC,Xnox pointed out that the above net.ipv4.conf.all.promote_secondaries=1 is actually a default of systemd (added in https://github.com/systemd/systemd/commit/ad8bc9ea508740074cead005aa3cfd1ba10a5dac). This looks like we will enable it for everybody via a systemd SRU.
1721223,2017-10-06 17:28:33 UTC,"Or  ""net.ipv4.conf.all.promote_secondaries=1"" in /etc/sysctl.d/50-ipv4.conf (or similar)."
1721223,2017-10-06 17:25:45 UTC,"As a workaround for now, it looks like with: ""echo 1 > /proc/sys/net/ipv4/conf/all/promote_secondaries"" on the device the problem goes away."
1721223,2017-10-06 16:57:22 UTC,"Fwiw, my current suspicion is that adding the new IP from the dhcp as a secondary IP is buggy. Secondary IPs will get removed when the kernel removes the primary IP (see kernels __inet_del_ifa() code)."
1721223,2017-10-06 16:26:57 UTC,The output if dhclient is running with the same scenario: http://paste.ubuntu.com/25686791/
1721223,2017-10-06 16:22:11 UTC,With ip monitor all: http://paste.ubuntu.com/25686763/
1721223,2017-10-06 16:14:28 UTC,"And the output of ""ip monitor eth0"": http://paste.ubuntu.com/25686711/
...
2: eth0    inet 192.168.1.130/24 brd 192.168.1.255 scope global secondary dynamic eth0
       valid_lft 120sec preferred_lft 120sec
local 192.168.1.130  table local  proto kernel  scope host  src 192.168.1.129"
1721223,2017-10-06 15:51:43 UTC,"Some more data point are the output of ""ip addr"": http://paste.ubuntu.com/25685527/"
1721223,2017-10-06 15:33:59 UTC,I spend a bit of time debugging this with xnox. Here some of the results:
1721223,2017-10-13 01:22:23 UTC,"On 12 October 2017 at 17:31, Robie Basak <email address hidden> wrote:

> What about server use cases that do not have networkd installed? There
> are complex network setups out there, such as HA with
> corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
> fix were SRU'd, will all of these things in the wild cope with this
> sysctl change?
>
> Can networkd be made to work without relying on this sysctl tweak? If
"
1721223,2017-10-07 10:20:27 UTC,"Setting snappy task to fix committed, core the ships the workaround from
https://github.com/snapcore/core/pull/60"
1721226,2017-10-05 11:15:32 UTC,https://bugzilla.redhat.com/show_bug.cgi?id=1483888#c18
1721226,2017-10-05 10:35:30 UTC,https://review.fuel-infra.org/#/c/36583/
1721231,2017-10-05 09:53:40 UTC,"Yes, of course"
1721231,2020-09-29 11:19:25 UTC,The domain awareness of the create_user method is addressed by [1] which is associated with [2] bug - therefore I marked this bug a duplicate of [2].
1721231,2018-03-19 18:27:30 UTC,"Change abandoned by Trevor McCasland (<email address hidden>) on branch: master
Review: https://review.openstack.org/531480
Reason: Abandoning my patches with no activity for eight weeks - https://etherpad.openstack.org/p/qa-queens-retrospective"
1721231,2017-10-04 12:10:02 UTC,From the code it looks like the issue exists indeed. Could you provide relevant logs?
1721231,2018-01-18 21:52:06 UTC,Tbhis looks like a dup of https://bugs.launchpad.net/tempest/+bug/1613819
1721231,2018-01-05 19:21:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531480"
1721231,2018-01-21 10:35:09 UTC,"Hi Trevor,
You might be right. I wrote the bug some time ago, and when I did, I do think I looked at that other bug, and for some reason I didn't think this was the same issue. It might have been that when the original bug was reported, there weren't cred_client subclasses per keystone version, so the problem changed a bit (or something like that)"
1721234,2017-10-04 12:20:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721234,2017-10-04 15:03:15 UTC,I also have the same problem with LXD on Solus. Current workaround : use of sudo.
1721234,2017-10-04 15:10:40 UTC,"i might be barking up the wrong tree, installing lxd version 'edge' solved the problem. It might be a problem with the snap itself instead of the snapd
see also https://github.com/lxc/lxd/issues/3892"
1721235,2017-10-04 12:33:46 UTC,"Sounds strange, you probably should not get minimize and/or maximize on panel... Have you tried with new user profile?"
1721235,2017-10-04 15:07:40 UTC,"Yes, moving ~/.config out of the way made things work. But of course it meant all settings were gone."
1721235,2020-03-17 12:53:42 UTC,Have you seen this problem again upgrading to newer versions?
1721235,2020-03-17 21:00:49 UTC,"I have not used gnome-flashback recently. From my point of view, this
bug can be closed, thanks."
1721235,2020-03-17 21:36:14 UTC,Thanks!
1721237,2017-11-07 09:36:33 UTC,"Also seeing this bug on upgrade.
Unfortunately my .config dir is masive (1gb) so I can't easily attach anything (especially without auditing it)"
1721237,2017-11-07 09:42:07 UTC,"Worth noting that I am seeing this also on any account that has been in a Unity session (even freshly created on 17.10), so I'm guessing its something set there. Hopefully that makes repro easier"
1721237,2017-10-07 12:08:12 UTC,"You're right, after removing ~/.config the bug doesn't reproduce any more. If more people report this during upgrading to beta, I still have the old .config backed up."
1721237,2017-10-06 22:38:54 UTC,Can you reproduce this with new user? Maybe also caused by some old files or something like that... I just tried in VM and I can not reproduce this problem.
1721237,2017-10-04 14:29:51 UTC,"In metacity it looks fine, no gap is created. I tried with gnome-terminal and nautilus file explorer."
1721237,2017-10-04 12:30:27 UTC,Can you reproduce that also in Metacity session?
1721237,2017-10-07 12:30:47 UTC,It is enough to move only .config? Maybe you can attach your .config dir? Before doing it check if it does not contain any important information that you don't want to make public. It might be good to understand why you had that bug.
1721240,2020-08-15 18:40:27 UTC,Not reproduced in 1.0 and master (debug build) on Windows 10.
1721248,2017-11-29 14:13:55 UTC,"Messages from totem run with --gst-debug-level=3
Test on my PC partition P9 Bionic 20171127 - installation done with NETWORK DISCONNECTED
Display Server: x11 - totem screensot OK"
1721248,2018-11-07 13:55:29 UTC,still in Ubuntu 19.04 with totem 3.26.2-1ubuntu2
1721248,2018-05-11 15:31:38 UTC,reported as https://gitlab.gnome.org/GNOME/mutter/issues/146
1721248,2018-05-08 08:15:31 UTC,"Please report this bug to the Gnome developers here:
https://gitlab.gnome.org/GNOME/mutter/issues"
1721248,2018-05-08 07:53:03 UTC,"Done some more test: the problem seems restricted to Intel HD Graphics 620 used by Luca Ciavatta https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204
and my Intel HD Graphics 630.
I still have the problem on Ubuntu 18.10:
corrado@corrado-p9-cc-0506:~$ inxi -SCGx
System:    Host: corrado-p9-cc-0506 Kernel: 4.15.0-20-generic x86_64 bits: 64 compiler: gcc v: 7.3.0
           Desktop: Gnome 3.28.1 Distro: Ubuntu Cosmic CANIMAL (development branch)
CPU:       Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Skylake rev: 9
           L2 cache: 3072 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296
           Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 802 4: 800
Graphics:  Card-1: Intel HD Graphics 630 driver: i915 v: kernel bus ID: 00:02.0
           Display: x11 server: X.Org 1.19.6 driver: i915 resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.0.2
           direct render: Yes
corrado@corrado-p9-cc-0506:~$ apt policy totem
totem:
  Installed: 3.26.0-0ubuntu6
  Candidate: 3.26.0-0ubuntu6
  Version table:
 *** 3.26.0-0ubuntu6 500
        500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status
corrado@corrado-p9-cc-0506:~$ apt policy gstreamer1.0-vaapi
gstreamer1.0-vaapi:
  Installed: 1.14.0-1
  Candidate: 1.14.0-1
  Version table:
 *** 1.14.0-1 500
        500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
        100 /var/lib/dpkg/status
corrado@corrado-p9-cc-0506:~$"
1721248,2018-02-21 01:45:02 UTC,"Starting in Ubuntu 17.10, totem (and some other apps like gnome-maps) use Wayland subsurfaces by default. This means the video (or maps) rectangle are able to redraw without redrawing the window decorations and saves a lot of CPU."
1721248,2018-02-20 17:54:22 UTC,"I have again the same problem on Ubuntu 18.04.
as before problem disappears removing gstreamer1.0-vaapi"
1721248,2017-12-01 09:18:37 UTC,Problem does not occur on a different hardware:
1721248,2017-11-30 12:29:40 UTC,"Removed gstreamer1.0-vaapi plugin
Problem solved!
thanks a lot!"
1721248,2017-11-29 14:14:56 UTC,inxi and avprobe output
1721248,2017-11-29 14:12:18 UTC,"Messages from totem run with --gst-debug-level=3
Test on my PC partition P9 Bionic 20171127 - installation done with NETWORK DISCONNECTED
Display Server: wayland - totem screensot OK"
1721248,2017-11-25 19:39:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721248,2017-11-29 14:08:33 UTC,"Messages from totem run with --gst-debug-level=3
Test on my PC partition P8 Bionic 20171127 - installation done with NETWORK CONNECTED
Display Server: wayland - totem screensot ERROR"
1721248,2017-10-05 01:46:41 UTC,"I suspect this is due to hardware acceleration (gstreamer-vaapi). We try to avoid buffer copies for the best efficiency, but that also means getting a screenshot is very difficult. The video image only exists in GPU memory and requires a lot of effort to read back. It's not surprising this doesn't quite work yet."
1721248,2017-10-05 06:47:49 UTC,Problem does not occur on ubuntu 16.04 installed in a different partition of same PC.
1721248,2017-11-29 14:10:21 UTC,"Messages from totem run with --gst-debug-level=3
Test on my PC partition P8 Bionic 20171127 - installation done with NETWORK CONNECTED
Display Server: x11 - totem screensot ERROR"
1721248,2017-10-06 19:07:48 UTC,problem does not occur (screenshot created ok) with a MPEG-4 video created by guvcview.
1721248,2017-11-24 19:49:20 UTC,"I still have the problem in Ubuntu Bionic
I ran totem under apitrace (apitrace trace --api gl totem 960x720.webm) and obtained a trace of the problem. I attach the trace hoping it will be useful. Let me know if you need more doc.
thanks"
1721248,2017-10-05 12:18:24 UTC,Problem also with cheese ... may be related?
1721248,2017-11-25 19:41:08 UTC,"I have the same issue: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204
When I opened the bug, Launchpad didn't show me this one, so I made a new one."
1721248,2017-11-25 20:03:41 UTC,"This bug seems a duplicate of https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204
Note: I always have the problem with .webm videos and sometimes with .mp4
I have some very small (200-300kB) video to reproduce the problem, if needed I may attach them (zipped?)"
1721248,2017-11-26 20:47:07 UTC,"running totem debug i see:
corrado@corrado-p6-bb-1114:~$ cd /media/corrado/dati1/linux/bugTotem
corrado@corrado-p6-bb-1114:/media/corrado/dati1/linux/bugTotem$ totem 640x480.webm --gst-debug-level=2
0:00:00.103055514  1946 0x55a593e3ef90 WARN                 basesrc gstbasesrc.c:3480:gst_base_src_start_complete:<source> pad not activated yet
0:00:00.103281487  1946 0x55a593e3ef90 WARN                 basesrc gstbasesrc.c:3480:gst_base_src_start_complete:<source> pad not activated yet
0:00:00.193641706  1946 0x7f413015ae30 WARN            vaapidisplay gstvaapidisplay_wayland.c:202:gst_vaapi_display_wayland_bind_display: wayland: get display name
0:00:00.264296079  1946 0x55a593e3ef90 WARN                   totem bacon-video-widget.c:2074:bvw_update_tags: Pipeline sent audio tags update with no changes
0:00:00.291577829  1946 0x55a593e3ef90 WARN                   totem bacon-video-widget.c:2074:bvw_update_tags: Pipeline sent video tags update with no changes"
1721248,2017-11-27 12:57:41 UTC,"Done some more test installing Ubuntu 18.04 LTS ""Bionic Beaver"" - Alpha amd64 (20171126)
on various partitions of same disk on my PC:
Problem does NOT occur with live session
Problem does NOT occur with an installation in us-english - installation default
problem DOES occur with an installation in italian - language italian locale italian
problem DOES occur with an installation in english-italian - language english locale italian
problem DOES occur with the above installation also changing locale to english:
corrado@corrado-p8-bb-1126:~$ inxi -S
System:    Host: corrado-p8-bb-1126 Kernel: 4.13.0-16-generic x86_64 bits: 64
           Desktop: Gnome 3.26.2
           Distro: Ubuntu Bionic Beaver (development branch)
corrado@corrado-p8-bb-1126:~$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=""en_US.UTF-8""
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=""en_US.UTF-8""
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=""en_US.UTF-8""
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
corrado@corrado-p8-bb-1126:~$"
1721248,2017-11-28 17:33:14 UTC,"After some more test with Ubuntu 17.10 and the last daily of Ubuntu 18.04 Bionic
On same hardware, different partitions:
If during the installation I'm connected to internet I HAVE the problem
If during the installation I'm NOT connected to internet I DO NOT HAVE the problem
Seems crazy?"
1721248,2017-10-04 13:23:21 UTC,Same problem in Wayland and x11
1721255,2019-05-13 02:05:36 UTC,"Hi, I can't reproduce this issue with current Inkscape master. As there have been many updates to Inkscape since this report, please try again with the latest version."
1721258,2017-10-04 14:26:51 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x55e8f2fda990 ""Boxes"", file=file@entry=0x55e8f2feb88a ""app.c"", line=line@entry=3283, func=func@entry=0x55e8f2fdb300 <__func__.72047> ""boxes_app_setup_default_source_co"", message=message@entry=0x55e8f49758e0 ""assertion failed: (default_connection != null)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x55e8f2fda990 ""Boxes"", file=file@entry=0x55e8f2feb88a ""app.c"", line=line@entry=3283, func=func@entry=0x55e8f2fdb300 <__func__.72047> ""boxes_app_setup_default_source_co"", expr=expr@entry=0x55e8f2fdabd3 ""default_connection != null"") at ../../../../glib/gtestutils.c:2459
 boxes_app_setup_default_source_co (_data_=0x55e8f487f620) at app.c:3283
 g_task_return_now (task=0x55e8f491c680) at ../../../../gio/gtask.c:1145
 g_task_return (task=0x55e8f491c680, type=<optimized out>) at ../../../../gio/gtask.c:1203"
1721258,2017-10-11 10:16:51 UTC,Thanks for your bug report. Confirmed on artful.
1721258,2017-10-11 10:32:37 UTC,See also https://errors.ubuntu.com/problem/51dd109d871e542ba07e9507aaf2b823f53e3287
1721258,2017-10-11 11:52:12 UTC,It actually fails to connect to the hypervisor
1721262,2019-10-08 19:33:09 UTC,The new basket functionality is great but it would nice to be able to use baskets to add the items attached to the selected records to an item bucket.
1721262,2017-10-04 17:56:58 UTC,Hi Kathy!
1721262,2017-10-04 17:24:23 UTC,Hi Sam!
1721262,2017-10-05 15:46:35 UTC,Sam & other interested parties -- I have filed bug 1721575 which has the specifications for our project with MassLNC.
1721263,2017-10-04 22:53:08 UTC,fixed in 4ppa53
1721270,2019-09-19 11:59:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1721271,2017-10-10 09:31:55 UTC,apport information
1721271,2017-12-06 22:24:33 UTC,This bug has now been resolved upstream in the latest bluetooth firmware. Ubuntu firmware (when linux-firmware is updated) will carry this fix.
1721271,2017-11-23 20:05:53 UTC,"Ah I see, yes. This issue here refers to https://bugzilla.kernel.org/show_bug.cgi?id=197137 instead, see above..."
1721271,2017-11-22 09:00:22 UTC,"I think this is the upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=197147, matches exactly my symptoms, Issue is present from kernel 4.13 upward."
1721271,2017-11-21 20:44:12 UTC,"I'm pretty convinced that the linked upstream bug is different. It's a regression between 4.13 and 4.14, but this here is a regression between 4.12 and 4.13. Also the upstream bug does not mention bluetooth at all. Could you open a new upstream bug?"
1721271,2017-10-10 09:32:04 UTC,apport information
1721271,2017-10-10 09:32:02 UTC,apport information
1721271,2017-10-10 09:32:00 UTC,apport information
1721271,2017-10-10 09:31:58 UTC,apport information
1721271,2017-10-10 09:31:57 UTC,apport information
1721271,2017-10-10 09:31:56 UTC,apport information
1721271,2017-10-10 09:31:52 UTC,apport information
1721271,2017-10-10 09:31:44 UTC,apport information
1721271,2017-10-10 09:31:50 UTC,apport information
1721271,2017-10-10 09:31:48 UTC,apport information
1721271,2017-10-10 09:31:47 UTC,apport information
1721271,2017-10-10 09:31:45 UTC,apport information
1721271,2017-10-04 15:00:08 UTC,This change was made by a bot.
1721271,2017-10-10 09:31:43 UTC,apport information
1721271,2017-10-10 09:31:41 UTC,"ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  simon      1286 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-09-30 (9 days ago)
InstallationMedia: Ubuntu 17.10 ""Artful Aardvark"" - Alpha amd64 (20170926)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
 Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp.
 Bus 001 Device 010: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20F5S0EU00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=b09604a7-81d8-4279-9464-c078eda9f057 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-12-generic N/A
 linux-backports-modules-4.13.0-12-generic  N/A
 linux-firmware                             1.169
Tags:  artful wayland-session
Uname: Linux 4.13.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 09/01/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R02ET59W (1.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20F5S0EU00
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR02ET59W(1.32):bd09/01/2017:svnLENOVO:pn20F5S0EU00:pvrThinkPadX260:rvnLENOVO:rn20F5S0EU00:rvrNODPK:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X260
dmi.product.name: 20F5S0EU00
dmi.product.version: ThinkPad X260
dmi.sys.vendor: LENOVO"
1721271,2017-10-10 09:29:35 UTC,"I have a very similar problem to the one described above by John Tanner, so I thought I would add my information here instead of opening a new bug report.
My bluetooth is not working as long as I am connected to a Wifi - I cannot pair with new devices, send or receive files. I can connect to a wireless network without any problems while having bluetooth active - but bluetooth is not working any more then.
Furthermore I noticed that my Laptop is shown as ""Bluemoon universal Bluetooth"" on my phone instead of the proper device name."
1721271,2017-10-06 09:22:11 UTC,Bug opened on bugzilla.kernel.org as I couldn't figure out the website that you linked to (mostly an incomplete wiki).
1721271,2017-10-05 16:11:35 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1721271,2017-10-04 23:55:26 UTC,Checked latest upstream kernel...bug exists
1721271,2017-10-10 09:31:51 UTC,apport information
1721271,2017-10-04 16:07:02 UTC,Further digging suggests that this bus is not present in kernel 4.12.14
1721277,2020-08-30 05:39:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu."
1721280,2018-01-28 22:44:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721280,2017-10-04 15:25:57 UTC,"StacktraceTop:
 __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135
 __new_sem_wait (sem=sem@entry=0x0) at sem_wait.c:39
 PyThread_acquire_lock_timed (lock=0x0, microseconds=microseconds@entry=-1, intr_flag=intr_flag@entry=0) at ../Python/thread_pthread.h:354
 PyThread_acquire_lock (lock=<optimized out>, waitflag=waitflag@entry=1) at ../Python/thread_pthread.h:563
 new_threadstate (init=1, interp=0x0) at ../Python/pystate.c:258"
1721280,2017-12-02 23:52:07 UTC,"I got a similar crash with some other python3 plugins.
To reproduce move your .vim and .vimrc out of the way and then:
$ mkdir -p .vim/pack/bug/start
$ cd .vim/pack/bug/start
$ (git clone https://github.com/Shougo/deoplete.nvim.git && cd deoplete.nvim && git checkout e9e45ebcf7757ca7d32003cb54a0e31bf2afadb8)
$ (git clone https://github.com/roxma/nvim-yarp.git && cd nvim-yarp.nvim && git checkout edb260a)
$ (git clone https://github.com/roxma/vim-hug-neovim-rpc.git && cd vim-hug-neovim-rpc && git checkout 0b8e70f)
$ cd
$ echo 'let g:deoplete#enable_at_startup=1' >.vimrc
$ touch x
$ vim x
Press :q
Repeat a few (sometimes it crashes everytime, sometimes repeat 10-20 times to get a crash), eventually it crashes with SEGV on exit"
1721289,2017-10-22 23:50:50 UTC,"There's also other restrictions on upgrading a charm, for example you can't rename a peer relation. This sort of thing was outside the original implementation design, and yes it will be a lot of work to implement. How much of an issue is it in practice? Does it materially affect the ability to satisfy our customer requirements or fulfil field operational requirements?"
1721289,2017-10-23 02:44:31 UTC,It's not critical as of now as far as I see it.
1721294,2018-02-14 12:32:11 UTC,The good news is the problem is reproducible.
1721294,2018-03-21 08:29:16 UTC,Yurii: can you clarify how that broke unattended upgrades?
1721294,2018-03-12 13:05:02 UTC,"For me this happened in 14.04.
I've found that root cause was PATH environment variable that lack /sbin and /usr/sbin"
1721294,2018-02-15 13:48:52 UTC,"Well, I got the debug output this time (a whole megabyte of it, split in two different emails), but unattended-upgrades succeeded, so I still don't know what the original problem was."
1721294,2018-02-13 15:49:41 UTC,"(By reading that script I've discovered the existence of APT::Periodic::Verbose.  We'll see what happens next morning with this set to ""1""!)"
1721294,2018-03-22 08:34:23 UTC,"This is a very annoying bug.  Last morning unattended-upgrade failed on a machine, so I set APT::Periodic::Verbose to ""3"" and this morning I got a very verbose email showing that it succeeded."
1721294,2018-02-13 14:49:00 UTC,Try running it with the --debug switch.
1721294,2018-02-13 11:58:43 UTC,This happened again.  Can I tweak some config file to enable verbose mode for unattended-upgrades and see if it'll fail when run from cron tomorrow night?
1721294,2017-11-15 11:55:31 UTC,"This happened again, while trying to upgrade libpq-dev libpq5 postgresql-9.3 postgresql-client-9.3."
1721294,2017-10-16 08:35:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721294,2017-10-13 16:30:14 UTC,Can you try manually running the upgrade with the verbose switch? e.g. 'unattended-upgrade -v'.
1721294,2017-10-12 07:58:32 UTC,"This happened again this morning, on a different VPS, while trying to upgrade curl libcurl3 libcurl3-gnutls linux-libc-dev."
1721294,2018-02-13 15:34:23 UTC,"The thing is, whenever I run it interactively over ssh, unattended-upgrade succeeds.  It's only the cron job that fails."
1721295,2017-10-17 19:27:29 UTC,Stub also raised this on the list. My summary comment there is:
1721295,2017-10-17 19:28:58 UTC,"Also, I do believe the code has been in flux in this area recently, because of other issues that we encountered with container scoped relations actually having too many other units in their scope."
1721298,2017-11-06 10:07:24 UTC,https://github.com/juju/juju/pull/7959
1721305,2018-02-02 12:49:49 UTC,"can you explain the whole topology?  eg. how a neutron router and external gateways are connected to the networks.
also, what's your expected behaviour for the situation?"
1721316,2019-07-03 16:53:40 UTC,This is an issue with cpe-foundation.
1721316,2017-11-08 17:18:11 UTC,"No, not fixed. Juju just hasn't closed a beta/release branch yet."
1721316,2017-10-05 12:57:51 UTC,"[7:31:46 am] <lutostag> [9:08:44 pm] <lutostag> balloons: yeah, closed is strange though, is this something that is going to happen often? (even if the same version is in release and beta it usually does not show up as closed, but rather just having the same version)
[7:31:46 am] <lutostag> [9:09:23 pm] <lutostag> for reference https://bugs.launchpad.net/cdoqa-system-tests/+bug/1721316
[7:31:46 am] <lutostag> [9:10:28 pm] <lutostag> we can write more code to parse the snap versions ""more correctly"" if you are going to do this often, just curious if it was a one-off non-standard release procedure or we can expect this in the future (and thus code to expect it and work as it should)
[7:31:50 am] <mup> Bug #1721316: juju version showing up as ""juju_↑"" <CDO QA System Tests:New for lutostag> <https://launchpad.net/bugs/1721316>
[7:32:21 am] <balloons> lutostag, howdy
[7:32:52 am] <balloons> lutostag, closing snap channels is normal, it's what I was directed to do by the snap team when i spoke about the predicament
[7:33:05 am] <balloons> a closed channel should just point to the next one down
[7:33:25 am] -*- balloons looks at the bug
[7:33:56 am] <lutostag> balloons: cool, thanks for the info, right but then we need to... https://forum.snapcraft.io/t/parsing-snap-info/2365/3 (but no worries, we can definitely do that)
[7:34:07 am] <balloons> yea, I just saw your post
[7:35:06 am] <balloons> the api is interesting..
[7:35:34 am] <balloons> i would have expected you to be able to get a beta channel, and that it would simply be the same as candidate
[7:36:18 am] <balloons> lutostag, so I agree with you that it should be on the snap side -- you shouldn't have to code for it, imho
[7:37:26 am] <lutostag> but, not too much code anyways, just checking that you will continue with the process of closing channels"
1721316,2017-10-04 19:36:15 UTC,https://forum.snapcraft.io/t/parsing-snap-info/2365
1721316,2017-10-04 18:52:30 UTC,"channels:
  stable:    2.2.4                      (2529) 25MB classic
  candidate: 2.2.5+2.2-c1f373c          (2623) 43MB classic
  beta:      ↑
  edge:      2.3-alpha1+develop-3fd2bbf (2625) 51MB classic"
1721316,2017-11-08 17:02:55 UTC,is this fixed?  haven't seen it again
1721318,2020-04-09 23:54:06 UTC,Sounds like you have added Brisk Menu to both panels.
1721318,2020-06-09 04:17:31 UTC,[Expired for brisk-menu (Ubuntu) because there has been no activity for 60 days.]
1721319,2017-10-05 01:55:45 UTC,"This feels like more of a feature than a bug. It's not only useful for testing, but a good assumption that the OSK should appear after the user has started touching the screen. You might have a physical keyboard but if it's a yoga-style laptop folded 180 degrees then you definitely want to use the OSK instead of the physical keyboard."
1721319,2017-10-06 01:00:56 UTC,"Not sure what you mean ""useful for testing"", but if in a yoga-style laptop the keyboard is still recognized as attached when completely folded that's a different issue. I suggest to create a setting to enable/disable the osk when a physical keyboard is already attached."
1721319,2017-10-06 01:44:17 UTC,"Actually I agree with this being a bug now. Encountered the problem myself last night. The OSK pops up even when touching the ""Show Applications"" icon. That's a bit much indeed."
1721319,2018-04-03 07:07:13 UTC,Didn't this get fixed in early 2018 already?
1721319,2020-03-02 11:21:16 UTC,This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
1721342,2017-10-04 17:48:56 UTC,The permission output from the kernel is correct. The kernel has a more fine grained view of permission than userspace and there is not a 1:1 mapping.
1721343,2017-10-22 13:55:15 UTC,"So, looks like a driver bug. Let's reassign to mesa, which provides the vdpau implementation for nouveau."
1721343,2017-10-21 11:08:19 UTC,"OK, I've figured out what's going on. My PC's have been using the Nouveau display driver (apparently one of my recent updates reset my active video driver(s) from the Nvidia proprietary driver to the default Nouveau open-source driver(s)). Once I downloaded, installed and activated the Nvidia proprietary driver(s) for my video card(s) VLC works as it should on my PC's. However, this means that there is still an incompatibility between VLC and the Nouveau open-source video driver."
1721343,2017-10-06 16:48:11 UTC,"I checked VLC on my Ubuntu 16.04 notebook with all recent updates -it too will not display video from my HD Homerun tuner or video from a DVD. The DVD displays video using the 'Videos' application, just not using VLC. The only computer I have tried that VLC still displays videos on is one I have not updated for about a week, which leads me to think that a recent update must have borked something - if not VLC (same version is on all my PC's) then one of the dependencies."
1721343,2017-10-06 18:09:51 UTC,"I checked VLC on an antique 64-bit server running Ubuntu 16.04 desktop. It's been a week since this machine was updated; 42 updates are available, none of which is a kernel update. VLC (version 2.2.2, same as all my other PC's) works properly and displays video as it should. The 2 machines that I've updated this week cannot display video in VLC. The 2 machines that haven't been updated have no video problems with VLC. Seems there is an update or two that is doing this to VLC."
1721343,2017-10-06 17:31:03 UTC,"OK, VLC works properly on my old 32-bit Ubuntu 16.04 laptop (both for the HD Homerun tuner and for DVD's); it hasn't been updated in about a week and has about 20 updates available. There is a kernel update as well as a bunch of *.lib files to update - if anyone needs a list of my uninstalled updates, I'll copy it out."
1721343,2017-10-19 21:10:40 UTC,Just updated my 64-bit Ubuntu PC and my 32-bit Lubuntu PC with the latest updates. VLC works perfectly on 32-bit but still no video (audio still works) on 64-bit.
1721345,2017-10-30 15:40:17 UTC,"Output of amixer -c 0 controls:
numid=15,iface=CARD,name='Front Headphone Jack'
numid=42,iface=CARD,name='HDMI/DP,pcm=10 Jack'
numid=18,iface=CARD,name='HDMI/DP,pcm=3 Jack'
numid=24,iface=CARD,name='HDMI/DP,pcm=7 Jack'
numid=30,iface=CARD,name='HDMI/DP,pcm=8 Jack'
numid=36,iface=CARD,name='HDMI/DP,pcm=9 Jack'
numid=12,iface=CARD,name='Mic Phantom Jack'
numid=13,iface=CARD,name='Speaker Front Phantom Jack'
numid=14,iface=CARD,name='Speaker Surround Phantom Jack'
numid=11,iface=MIXER,name='Master Playback Switch'
numid=10,iface=MIXER,name='Master Playback Volume'
numid=5,iface=MIXER,name='Headphone Playback Switch'
numid=4,iface=MIXER,name='Headphone Playback Volume'
numid=53,iface=MIXER,name='PCM Playback Volume'
numid=9,iface=MIXER,name='Mic Boost Volume'
numid=8,iface=MIXER,name='Capture Switch'
numid=7,iface=MIXER,name='Capture Volume'
numid=19,iface=MIXER,name='IEC958 Playback Con Mask'
numid=25,iface=MIXER,name='IEC958 Playback Con Mask',index=1
numid=31,iface=MIXER,name='IEC958 Playback Con Mask',index=2
numid=37,iface=MIXER,name='IEC958 Playback Con Mask',index=3
numid=43,iface=MIXER,name='IEC958 Playback Con Mask',index=4
numid=20,iface=MIXER,name='IEC958 Playback Pro Mask'
numid=26,iface=MIXER,name='IEC958 Playback Pro Mask',index=1
numid=32,iface=MIXER,name='IEC958 Playback Pro Mask',index=2
numid=38,iface=MIXER,name='IEC958 Playback Pro Mask',index=3
numid=44,iface=MIXER,name='IEC958 Playback Pro Mask',index=4
numid=21,iface=MIXER,name='IEC958 Playback Default'
numid=27,iface=MIXER,name='IEC958 Playback Default',index=1
numid=33,iface=MIXER,name='IEC958 Playback Default',index=2
numid=39,iface=MIXER,name='IEC958 Playback Default',index=3
numid=45,iface=MIXER,name='IEC958 Playback Default',index=4
numid=22,iface=MIXER,name='IEC958 Playback Switch'
numid=28,iface=MIXER,name='IEC958 Playback Switch',index=1
numid=34,iface=MIXER,name='IEC958 Playback Switch',index=2
numid=40,iface=MIXER,name='IEC958 Playback Switch',index=3
numid=46,iface=MIXER,name='IEC958 Playback Switch',index=4
numid=6,iface=MIXER,name='Auto-Mute Mode'
numid=3,iface=MIXER,name='Bass Speaker Playback Switch'
numid=2,iface=MIXER,name='Bass Speaker Playback Volume'
numid=1,iface=MIXER,name='Speaker Playback Switch'
numid=17,iface=PCM,name='Capture Channel Map'
numid=16,iface=PCM,name='Playback Channel Map'
numid=23,iface=PCM,name='ELD',device=3
numid=48,iface=PCM,name='Playback Channel Map',device=3
numid=29,iface=PCM,name='ELD',device=7
numid=49,iface=PCM,name='Playback Channel Map',device=7
numid=35,iface=PCM,name='ELD',device=8
numid=50,iface=PCM,name='Playback Channel Map',device=8
numid=41,iface=PCM,name='ELD',device=9
numid=51,iface=PCM,name='Playback Channel Map',device=9
numid=47,iface=PCM,name='ELD',device=10
numid=52,iface=PCM,name='Playback Channel Map',device=10"
1721345,2017-10-30 15:41:46 UTC,"I think Bass Speaker,Master and Headphone all have amp-out capability. They need PCM to be raised. PCM is analogous to a mixing console channel fader, and the former three are analogous to volume knobs on audio amplifiers."
1721345,2017-10-30 16:07:32 UTC,"That's right, what you describe is exactly what we are looking for: to use headphone change speaker volume."
1721345,2017-10-30 20:27:59 UTC,"When using a stock kernel and stock PA/Alsa configurations, the volume controls end up raising Master only without also raising PCM as PA thinks that PCM and Master are merged. This codec does not require raising Headphone volume for speakers, it only requires it when actually using headphones. The headphone scenario works perfectly out of the box. Please do not change anything with headphones as that would be a regression."
1721345,2017-10-31 08:07:48 UTC,Master should also change the speaker volume with my patch. But probably we should keep it the way it is...
1721345,2017-10-31 08:38:07 UTC,"Your patch added an extra requirement to get sound, i.e. that the Headphone volume has to be raised in order to get sound from speakers. It is not only counter-intuitive but also works against how PA operates in general. PA does not raise Headphone volume unless headphones are actually plugged in."
1721345,2017-10-31 08:38:59 UTC,"SO bettr to keep how it is, and use a PA config patch that is manually applied."
1721345,2019-06-08 16:41:24 UTC,"Still occurs with Ubuntu 19.04 on Asus ZenBook Flip 15 UX561UD.
The workaround helped."
1721345,2017-10-30 06:47:16 UTC,"It does, but teh other two channels must be raised as well."
1721345,2019-10-21 07:20:47 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/"
1721345,2019-10-21 07:50:57 UTC,"Thanks, will do, but will take a bit as I don't always have access to the machine"
1721345,2020-03-06 17:33:27 UTC,Still occurs on this Asus in 20.04 with kernel 5.4.0-15 and the -proposed -17.
1721345,2020-05-03 14:02:19 UTC,Same here.
1721345,2020-07-24 14:42:21 UTC,"I've fixed this issue on my Asus UX550VE, Ubuntu 20.04, kernel 5.4.0-42. I followed Optiman's instructions, which are supposed to ""activate bottom speakers"" using jack retasking:"
1721345,2019-10-19 21:40:37 UTC,"Still occurs on 19.10 after upgrade, on the same Asus ZenBook Flip 15 UX561UD as in comment #30.
As the upgrade replaced ""/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common"", had to reapply the workaround from comment #8 (which is kind of bearable on a machine that is has a proper admin, but sucks for normal people)"
1721345,2017-10-30 06:32:04 UTC,"Does ""Master"" change the output volume of speaker now?"
1721345,2017-10-07 14:50:54 UTC,It's actually a valid bug. The problem is that node 0x06 does not have amp-out capability. Also there's no mixer that can connect 0x06 to another node with amp-out capability.
1721345,2017-10-29 12:40:11 UTC,"> On 29 Oct 2017, at 4:48 PM, Dylan Borg <email address hidden> wrote:
>
> The provided kernel has swapped the speaker and headphone channels. The
> Headphone channel in alsamixer is controlling the laptop speakers! If
> you need some alsa dumps to aid in correctly mapping the channels do not
> hesitate to ask.
"
1721345,2017-10-04 18:00:08 UTC,This change was made by a bot.
1721345,2017-10-05 16:09:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1721345,2017-10-05 17:22:56 UTC,"NO, this is a fresh install on brand new hardware. Also I need the nvidia driver to work on thsi system which is impossible for now with the the 4.14 kernel."
1721345,2017-10-05 17:26:52 UTC,"This is the installtion output:
dylan@zenbook-pro:~/Downloads/kdebs$ sudo dpkg -i *.deb
[sudo] password for dylan:
Selecting previously unselected package linux-headers-4.14.0-041400rc3.
(Reading database ... 288569 files and directories currently installed.)
Preparing to unpack linux-headers-4.14.0-041400rc3_4.14.0-041400rc3.201710011930_all.deb ...
Unpacking linux-headers-4.14.0-041400rc3 (4.14.0-041400rc3.201710011930) ...
Selecting previously unselected package linux-headers-4.14.0-041400rc3-generic.
Preparing to unpack linux-headers-4.14.0-041400rc3-generic_4.14.0-041400rc3.201710011930_amd64.deb ...
Unpacking linux-headers-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) ...
Selecting previously unselected package linux-image-4.14.0-041400rc3-generic.
Preparing to unpack linux-image-4.14.0-041400rc3-generic_4.14.0-041400rc3.201710011930_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
Done.
Unpacking linux-image-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) ...
Setting up linux-headers-4.14.0-041400rc3 (4.14.0-041400rc3.201710011930) ...
Setting up linux-headers-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
ERROR (dkms apport): kernel package linux-headers-4.14.0-041400rc3-generic is not supported
Error! Bad return status for module build on kernel: 4.14.0-041400rc3-generic (x86_64)
Consult /var/lib/dkms/nvidia-387/387.12/build/make.log for more information.
Setting up linux-image-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
ERROR (dkms apport): kernel package linux-headers-4.14.0-041400rc3-generic is not supported
Error! Bad return status for module build on kernel: 4.14.0-041400rc3-generic (x86_64)
Consult /var/lib/dkms/nvidia-387/387.12/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
update-initramfs: Generating /boot/initrd.img-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.14.0-041400rc3-generic
Found initrd image: /boot/initrd.img-4.14.0-041400rc3-generic
Found linux image: /boot/vmlinuz-4.13.0-15-generic
Found initrd image: /boot..."
1721345,2017-10-29 16:54:49 UTC,"No, using stock pulseuadio configuration or the one I had patched will not work. I had to increase the headphone volume with alsamixer manually. Before your patch, I could change the volume by keeping master at 100% and vary the PCM channel. Thr PCM channel seems to alter the amplifier attached to the main speakers. The amplifier attached to the subwoofer has a separate channel named bass speaker in alsamixer. My pulseuadio config patch with a stock kernel allows changing volume from the GUI and hotkeys without any fuss."
1721345,2017-10-06 10:41:43 UTC,"Ok, this issue can be fixed by modified pulseaudio instead of the kernel. Will mark this as fixed. For anyone else coming across this having the same issue please add:"
1721345,2017-10-07 16:16:31 UTC,"I got a better result by changing ""volume=ignore"" to ""volume=100"", that makes ure teh Master channel is stuck to 100% so teh woofers get used."
1721345,2017-10-05 17:41:21 UTC,"The DKMS isues should be fixable by disabling ""AMD Secure Memory Encryption"" i.e. SME support in the 4.14 kernel."
1721345,2017-10-27 07:13:38 UTC,Please try the kernel here:
1721345,2017-10-27 08:39:15 UTC,"I cannot do that, the current nvidia drivers do not build against 4.14. If possible I could try a patches 4.13.9 kernel instead."
1721345,2017-10-27 15:42:32 UTC,"Ok, use this one instead,
http://people.canonical.com/~khfeng/lp1721345-4.13/"
1721345,2017-10-27 17:42:08 UTC,Is it based on a kernel that is 4.13.5 or higher? 4.13 till 4.13.4 lead to hung shutdowns on the machien in question.
1721345,2017-10-27 18:02:56 UTC,"> On 28 Oct 2017, at 1:42 AM, Dylan Borg <email address hidden> wrote:
>
> Is it based on a kernel that is 4.13.5 or higher? 4.13 till 4.13.4 lead
> to hung shutdowns on the machien in question.
"
1721345,2017-10-29 08:48:34 UTC,The provided kernel has swapped the speaker and headphone channels. The Headphone channel in alsamixer is controlling the laptop speakers! If you need some alsa dumps to aid in correctly mapping the channels do not hesitate to ask.
1721345,2017-10-29 08:52:41 UTC,"The provided kernel requires all three of Headphone,Master and PCM to be raised for sound to come put of the speakers. The stock kernel needs only Master and PCM to be raised."
1721345,2017-10-07 16:18:19 UTC,I wish anyone luck when trying to improve the status of the driver for this codec. Some aspects do feel weird such as the interplay between mixer channels.
1721356,2017-10-10 16:45:19 UTC,See also our bug triage conversation.
1721356,2018-05-03 05:01:29 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/565955"
1721356,2019-05-07 03:04:20 UTC,"Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/565955
Reason: didn't work"
1721360,2017-10-04 19:17:41 UTC,"IIRC, there's a translation mechanism that should be using hwe-16.04 instead of hwe-x when it sees it set."
1721360,2017-10-04 19:18:16 UTC,"ALso, removing the blocker tag as this doesn't seem to be a blocker anymore."
1721360,2017-10-04 19:11:34 UTC,"Thanks, set all of my machines to empty minimum kernel and that is allowing things to work now.  So, it seems like there is a missing migration to change that value?"
1721360,2017-10-04 18:20:29 UTC,"Hi Jason,"
1721360,2017-10-04 18:55:32 UTC,"streams config is here:
http://paste.ubuntu.com/25674740/"
1721360,2017-10-04 18:53:16 UTC,"Also, can you deploy the machine without Juju ? what happens when youdeploy the machine without juju."
1721360,2017-10-04 18:52:13 UTC,Is this an upgrade? Can you check what URL you are using for the streams ? Are you using v2 or v3 for the streams?
1721360,2017-10-04 18:26:27 UTC,"Is my MAAS missing an image or not? If not, and that warning is showing, then that's a bug.  If it is missing an image, then it's a bug, because it says I have images synced."
1721360,2017-10-04 19:00:05 UTC,I think I know what the issue is:
1721368,2018-08-03 13:19:56 UTC,I believe https://bugs.launchpad.net/juju/+bug/1785232 is a spin-off of this bug.
1721368,2018-07-03 11:01:22 UTC,I have proposed https://github.com/juju/juju/pull/8885 against the develop branch to resolve this.
1721368,2018-05-22 13:04:53 UTC,This bug also appears to be affecting Kubernetes deployments (CDK): https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/573
1721368,2018-05-09 12:15:15 UTC,https://github.com/juju/juju/pull/8672
1721368,2018-03-14 14:08:31 UTC,"Taking the liberty to follow up on this one: have there been any new findings lately? Also, if the issue is indeed with my_ip being populated from the machine name, can a machine be renamed from its hostname to its IP address after the fact?"
1721368,2018-01-31 04:12:53 UTC,"Offhand, I would guess the issue is that the machines were added with ""juju add-machine ssh:hostname"", and a workaround would be to do ""juju add-machine ssh:IP"".
I haven't done anything to confirm that is the case, so I could be wildly off base. But I'm guessing that the bug is in how Juju is recording what that machine is.
I'm guessing this is elevated priority because of Openstack on s390, but I'm also guessing there might be a quick workaround for people."
1721368,2018-01-08 09:23:10 UTC,2.2.4 according to the attached information
1721368,2018-01-08 09:07:12 UTC,It may be that Juju of different version exhibit different behaviors...
1721368,2018-06-26 10:05:21 UTC,This problem is not fully solved as of 2.4-rc3:
1721368,2018-01-08 08:51:02 UTC,"network-get --primary-address should always be returning an IP address (by how we define the return value of the command, because we had confusion around this in the past). Returning a hostname would be a bug in our implementation. It may be that we're doing something weird for manual provider."
1721368,2018-01-04 12:22:17 UTC,Raising a Juju task for feedback on this issue from the Juju developers.
1721368,2018-01-04 12:20:53 UTC,Hmm OK so it would appear that the Juju >= 2.0 network space support can actually return a hostname instead of an IP address for:
1721368,2018-01-04 12:17:27 UTC,Groking the code:
1721368,2017-12-05 09:45:24 UTC,"@james-page, any chance you could check on the comment from early October?"
1721368,2017-12-05 04:17:26 UTC,[Expired for OpenStack nova-compute charm because there has been no activity for 60 days.]
1721368,2017-10-04 20:48:46 UTC,"Could you provide the following output:
juju status # make sure it includes juju version information associated with model at the top
juju config nova-compute"
1721368,2017-10-05 09:07:37 UTC,"Eek, sorry. Stupid of me not to have checked on that — I did take those juju status commands right after my test stack had been resumed from suspend."
1721368,2017-10-05 08:47:06 UTC,"Looking at the status output attached, the agent for nova-compute is listed as missing/lost - which indicates that its connection to the controller is down, and as a result the juju run ops won't ever complete (as the required comms is not in place)."
1721368,2018-01-08 08:51:34 UTC,"(The intent was to have a separate field like 'primary-hostname' that would provide the hostname when it was available, and maintain separation of what could be in what field.)"
1721368,2017-10-05 08:19:54 UTC,"I've attached juju status and juju config, as requested. The juju run command is acting up in that it just hangs. I've added the --debug flag, and this is what I get:"
1721369,2017-10-17 14:26:19 UTC,"Sicne the command is issued from the Cinder CLI, I'm not seeing at first glance that as a nova problem. Triaging the bug to Cinder, but feel free to put the status to New for Nova if something is required from its side."
1721369,2017-10-17 15:29:38 UTC,Please attach the cinder logs.
1721369,2017-10-17 16:20:50 UTC,"Are you able to reproduce the issue?
I didn't see much error from the logs...the attached volume instance just got stuck at ""retyping"" status forever....
Will attach the logs later in this ticket but it is good if you can try to reproduce. Thanks."
1721369,2017-12-15 20:20:14 UTC,Attached logs don't appear to capture what was going on at the time.
1721375,2017-10-04 19:33:16 UTC,Tested it on Multi node.
1721375,2019-03-28 10:10:18 UTC,Is this still a bug? If yes - please update. Setting to incomplete.
1721375,2019-05-28 04:17:23 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1721385,2017-10-05 07:07:37 UTC,The same thing happens when I choose reboot.
1721387,2017-12-08 17:08:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721389,2018-02-17 19:55:45 UTC,"I get the same behavior on a 2010 MacBookPOro7,1 with freshly installed Ubuntu 16.04.03 upgraded to 17.10."
1721397,2017-10-05 22:28:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721398,2017-10-13 10:32:40 UTC,"thank you for your bug report, that would be a nice feature to have indeed, reading your description it's not simple that those are missing from the .deb but they are different project/sources so it would need some work to include, ideally upstream libimobiledevice would ship them which would make that easier"
1721398,2017-10-13 17:19:59 UTC,"There's also sources on the same host for the main project git server under the following names:-
https://cgit.libimobiledevice.org/idevicerestore.git/
https://cgit.libimobiledevice.org/libirecovery.git/"
1721398,2018-02-18 13:17:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721400,2018-07-24 09:33:20 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1721400,2017-11-08 04:42:47 UTC,"it does reproduce on 4.12.0-13.  Not sure exactly what kernel I was running when it was last working, but will try a few more and report back after finishing testing mainline for a separate bug"
1721400,2017-11-08 03:07:47 UTC,"As Joseph said, does this issue go away if you boot back into the prior kernel?"
1721400,2017-11-07 16:17:48 UTC,Reproduced on v4.14-rc7
1721400,2017-10-04 22:00:06 UTC,This change was made by a bot.
1721400,2017-10-05 16:07:22 UTC,Does this issue go away if you boot back into the prior kernel?
1721401,2019-08-28 05:02:47 UTC,The problems appears to be arts of gnome left over from ahanging to TWM.  The following eliminated the problem.
1721401,2019-08-27 22:00:14 UTC,I have this problem.
1721401,2019-08-28 00:28:34 UTC,"I have another 18.04.3 installation on this computer, on a WD5000, that also uses TWM.  The 27 second display does not happen.  On that system, I notice a difference in time for the very first execution of eog to the next.  The shared libs seem to have stayed loaded inbetween."
1721410,2020-09-19 07:52:03 UTC,Closing because INVALID: Incomplete.
1721410,2017-10-11 11:55:34 UTC,Can you save the file after the triangulation and upload it here?
1721410,2017-10-05 05:34:46 UTC,"cant reproduce (works here)
0.92.2"
1721415,2017-10-13 21:46:02 UTC,"Is the k8s cluster is provisioned using ansible, the please use the following knob to configure rabbit username/password."
1721424,2017-10-05 04:19:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1721424,2017-10-05 15:02:26 UTC,It'd be helpful to know which desktop environment you are using.
1721424,2017-10-05 15:38:34 UTC,the default 17.10 gnome DE
1721424,2017-10-10 00:06:18 UTC,Hello?
1721424,2017-10-10 16:06:45 UTC,@brian-murray what next?
1721424,2019-10-04 12:48:57 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1721424,2019-10-04 14:24:22 UTC,"It's inconsistent, so very hard to reproduce, but I've experienced it
intermittently at least up to 19.04. Maybe close it if it's not
reproducible, I'm not sure what is best."
1721424,2019-12-04 04:17:34 UTC,[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]
1721425,2019-08-20 10:30:14 UTC,"zesty has long been EOL, but xenial is still supported, and similarly affected."
1721425,2017-10-05 16:52:29 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1721425,2017-10-05 16:54:14 UTC,Same issue is affecting 16.04 as well as 14.04 and I see that the latter is also lacking libjs-highlight.js https://packages.ubuntu.com/trusty/rust-doc. I suppose this was introduced when rustc was backported to older releases.
1721425,2018-03-26 21:23:09 UTC,Why not just backporting fonts-open-sans to the older LTS releases?
1721427,2019-09-02 09:22:46 UTC,trusted_ssl_ca config parameter now exists
1721432,2017-10-31 05:16:23 UTC,"Reviewed:  https://review.openstack.org/510981
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=b40fcbecf4745298d29387bc54a8a9ff72925b6e
Submitter: Zuul
Branch:    master"
1721432,2018-06-18 16:07:31 UTC,"Change abandoned by Ben Nemec (<email address hidden>) on branch: master
Review: https://review.openstack.org/513500
Reason: I rebased the followup patch so it no longer depends on this one.  It obsoletes this change anyway."
1721432,2017-12-08 21:43:22 UTC,This issue was fixed in the openstack/congress 7.0.0.0b2 development milestone.
1721432,2017-10-26 21:08:47 UTC,This issue was fixed in the openstack/designate 6.0.0.0b1 development milestone.
1721432,2017-10-19 20:39:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/513500"
1721432,2017-10-19 19:39:34 UTC,"Reviewed:  https://review.openstack.org/510917
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=ef4cc46769e4ba31895a1cda8dc09a10aa6c764f
Submitter: Zuul
Branch:    master"
1721432,2017-10-05 22:47:37 UTC,"Not sure why it didn't link the new patch, but here it is: https://review.openstack.org/#/c/509919/"
1721432,2017-10-17 15:59:47 UTC,"Reviewed:  https://review.openstack.org/511026
Committed: https://git.openstack.org/cgit/openstack/oslo.context/commit/?id=e75f4c5ad91962e272d65daa770e00f70f931ecb
Submitter: Zuul
Branch:    master"
1721432,2017-10-10 20:43:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/511026"
1721432,2017-10-10 15:50:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510917"
1721432,2017-10-05 22:34:37 UTC,"Change abandoned by Ben Nemec (<email address hidden>) on branch: master
Review: https://review.openstack.org/509685
Reason: It turns out multiple projects were relying on this behavior, so let's just fix it in oslo.context.  See https://review.openstack.org/#/c/509919"
1721432,2017-10-05 04:04:31 UTC,"Hmm, removing from_dict got me past the issue I was having locally, but it seems to have broken some of the unit tests.  Will have to look deeper."
1721432,2017-10-19 15:41:05 UTC,"Change abandoned by Ben Nemec (<email address hidden>) on branch: master
Review: https://review.openstack.org/509919
Reason: Quite right."
1721432,2017-10-05 03:53:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509685"
1721452,2017-10-13 06:27:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511723"
1721476,2017-11-15 09:46:25 UTC,One blocker to get this into testflinger is that we cannot force a reboot of the device. Doing so we're losing the system and the jenkins job marks the testrun as failed (even if the checkbox session correctly resumed in the background).
1721485,2017-10-05 08:56:22 UTC,"StacktraceTop:
 allocator_slab_stack_push (allocator=0x7f30a40f4c20 <allocator>, sinfo=0x563e28f5f7d0, ix=6) at ../../../../glib/gslice.c:1252
 allocator_add_slab (allocator=0x7f30a40f4c20 <allocator>, chunk_size=112, ix=6) at ../../../../glib/gslice.c:1320
 slab_allocator_alloc_chunk (chunk_size=chunk_size@entry=112) at ../../../../glib/gslice.c:1330
 magazine_cache_pop_magazine (countp=0x563e28919058, ix=6) at ../../../../glib/gslice.c:731
 thread_memory_magazine1_reload (tmem=<optimized out>, ix=6) at ../../../../glib/gslice.c:801"
1721487,2017-10-05 11:05:13 UTC,any update on this bug senlin team?
1721487,2017-10-23 06:10:06 UTC,did you export 'OS_PASSWORD' and 'OS_USERNAME' properly before invoking the commands?
1721508,2020-07-15 13:53:39 UTC,Hi Guys!
1721510,2018-06-05 15:45:42 UTC,"Change abandoned by Pavlo Shchelokovskyy (<email address hidden>) on branch: master
Review: https://review.openstack.org/509752
Reason: ostestr is deprecated in favor of stestr"
1721514,2017-10-25 19:22:17 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1721514,2017-10-24 12:41:59 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1721514,2017-10-05 19:13:19 UTC,"Reviewed:  https://review.openstack.org/509759
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b5dca17f74b7a789e16b78178ae5874a30f3e0da
Submitter: Jenkins
Branch:    master"
1721514,2017-10-05 12:10:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509759"
1721514,2017-10-19 04:58:44 UTC,"Reviewed:  https://review.openstack.org/509818
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=888482c9b4fb8a1bc23d4758301e319b7c5bc997
Submitter: Zuul
Branch:    stable/pike"
1721514,2017-10-05 15:51:35 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/509818"
1721523,2019-09-19 14:49:21 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1721528,2017-10-05 11:57:23 UTC,Changing the OPTIONS line in /etc/default/atftpd from:
1721528,2017-10-05 12:50:18 UTC,Actually it's --verbose=5 not --verbose 5. The second form would use '5' as the tftp base dir.
1721528,2020-11-30 09:37:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721533,2017-10-05 14:40:09 UTC,"Hi,
    Thank you for the bug report. The rabbitmq monitoring was designed to be able to monitor the queues without having to escalate the privilege of the nagios user. This is achieved by a cronjob ( /etc/cron.d/rabbitmq-stats ) which runs a queue collection script ( /usr/local/bin/collect_rabbitmq_stats.sh ) which writes the queue data out to a file that the nagios check can read."
1721533,2017-10-05 16:27:47 UTC,"Hi Liam,"
1721533,2017-10-06 09:52:47 UTC,"Hi Tamas,
    It sounds like your umask probably is what is causing the issue here. I'm in two minds about whether we should make /var/lib/rabbitmq/data and /var/lib/rabbitmq/ world readable in a charm. On the one hand if the default umask and package result in directories that are more strict then you may not want the charm to come along and open them up. On the other hand the charm provides an nrpe service and, as you say, that is broken unless the perms are opened up. I think I'll get another opinion on this.
    You are quite right about the race :-) and thank you for offering to fix it. The issue has actually been reported in Bug #1569143 and the fix landed yesterday ( https://review.openstack.org/#/c/508849/ ).
    The stable version of the rabbitmq-server charm in charmstore is updated every 3 to 6 months. You can download it with ""charm pull cs:rabbitmq-server"" or deploy it straight from the charmstore with ""juju deploy cs:rabbitmq-server"". The devel version of the charm is here: cs:~openstack-charmers-next/rabbitmq-server (this version has the stats file race fix in it).
Thank you for all you feedback, it is greatly appreciated.
Liam"
1721533,2017-10-09 11:54:53 UTC,"Hi Liam,"
1721533,2017-12-09 04:17:41 UTC,[Expired for OpenStack rabbitmq-server charm because there has been no activity for 60 days.]
1721533,2018-06-01 00:28:00 UTC,I am seeing this in a foundation cloud deployment at a customer site using the rabbitmq-server charm version 70.
1721533,2018-06-04 11:18:57 UTC,"Hi Vern, the issue you are seeing is slightly different to the original bug as the nagios uses does have access to the directory in your case. The issue you are seeing appears to be fixed in v71 of the charm;"
1721534,2019-02-08 17:39:09 UTC,"Sorry, the previously attached two patches need to be applied on top of this one, which SUSE applied a long time ago already in order to avoid the ugly error pop-up under GNOME."
1721534,2019-03-08 00:13:30 UTC,"It turns out that the patch from comment #2 is wrong. If GNOME is running without systray, hp-toolbox will exit after ~15s if this patch is applied because the hplip service threads have been terminated by the failing systray."
1721534,2019-02-08 17:36:17 UTC,"At SUSE, we've had a bug report about the GNOME session logout hanging. We traced it down to this problem here, essentially."
1721535,2017-10-05 12:35:24 UTC,I enjoy your help
1721535,2017-10-05 15:35:28 UTC,What version of duplicity?
1721535,2017-10-10 14:48:57 UTC,Version 0.7.14 and 0.7.11
1721535,2017-12-11 15:43:49 UTC,"I'm fix this issue exporting gpg password before duplicity backup command
Eg: GPGPASS='gpgpassword'
PASSPHRASE=$GPGPASS /usr/local/bin/duplicity full-if-older-than 1M / --encrypt-key=gpgkey --asynchronous-upload file:///backup"
1721536,2017-10-06 10:29:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/510052"
1721536,2017-10-10 14:55:58 UTC,"The root cause is the abort call being decorated with a `fsm_transition(istate.Events.abort`, reentrant=False)`[1]; Errors like:"
1721536,2017-10-10 16:19:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510929"
1721536,2017-11-02 14:47:17 UTC,"Change abandoned by Milan Kováčik (<email address hidden>) on branch: master
Review: https://review.openstack.org/510052
Reason: not needed anymore"
1721536,2017-11-02 14:47:32 UTC,"Change abandoned by Milan Kováčik (<email address hidden>) on branch: master
Review: https://review.openstack.org/510929
Reason: not needed anymore"
1721538,2017-11-20 11:53:03 UTC,This bug was fixed in the package linux - 4.4.0-101.124
1721538,2017-11-08 12:50:32 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1721538,2017-10-05 13:49:47 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-October/087428.html
1721538,2017-11-13 14:45:28 UTC,Confirmed that the hv_network_direct module is not shipped anymore with Xenial kernel 4.4.0-101.124.
1721541,2017-10-05 13:22:55 UTC,"I forgot: I have of course tested DNS other than those of my ISP, like OpenDNS (which I currently have) or Google but always the same, even ignoring IPv6"
1721541,2017-10-05 13:51:28 UTC,"This bug looks a lot like mine (with the same network card, but another revision), with the difference that I can not find the connection via the network-manager applet https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1715013 so I do not know if they can be considered as duplicates"
1721541,2017-10-12 14:53:24 UTC,"When i lose connection and reconnect via nm-applet, I no longer have information on the IPv4 connection (everything is reported as ""unknown"") but the connection in IPv6 is indeed effective in DHCP"
1721541,2017-10-31 12:12:22 UTC,I seem to have the same problem. IPv4 connection is lost. IPv6 still has a connection. Disabling the network connection and enabling it again restores the IPv4 connection. Problem probably exists since upgrading to 17.10. Never had a problem under 17.04.
1721546,2018-02-12 21:27:35 UTC,"That is better thatn what it is now, but! What is the rationale behind not letting systemd limit the number of open files?
The limit exists in MySQL anyways, and for mysql administrator this is just an additional option that needs to be changed. I also imagine most of MySQL admins will set LimitNOFILE to Infinity anyways, and control open-files-limit."
1721546,2018-01-11 11:46:25 UTC,Is https://salsa.debian.org/rbasak-guest/mysql/merge_requests/3 acceptable to everyone? This sets LimitNOFile to 5000 based on upstream.
1721546,2018-02-16 00:40:06 UTC,This bug was fixed in the package mysql-5.7 - 5.7.21-1ubuntu1
1721546,2017-10-12 20:22:58 UTC,"This sounds reasonable to go into Debian as well, thanks. If someone can please propose and test a commit against current Debian VCS, I'll be happy to push it."
1721546,2017-10-12 19:48:29 UTC,Should this be fixed in Debian? Or at least reported there? So that it does not add to the delta?
1721546,2017-10-12 11:16:34 UTC,This can be easily circumvented manually by creating a systemd unit override file for mysql service.
1721546,2017-10-11 14:09:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721546,2017-10-13 05:00:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721551,2017-10-05 23:16:25 UTC,From Nicholas: we can update that page.
1721558,2020-09-30 00:36:44 UTC,"i think this was since fixed, no?!"
1721558,2020-05-04 10:58:15 UTC,Now it fails with:
1721558,2018-05-14 11:04:34 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1721558,2017-10-05 14:35:17 UTC,This all for xenial ADT tests.
1721558,2017-10-05 14:35:06 UTC,The command ran is of this form:
1721558,2020-01-23 13:01:42 UTC,Also very often fails in later releases:
1721566,2018-08-09 00:13:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721567,2017-10-05 15:54:14 UTC,The branch scan happened:
1721571,2019-08-06 09:29:33 UTC,"Reviewed:  https://review.opendev.org/673298
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=babcd0d6831b4596ce3f392990aecefc60ae7193
Submitter: Zuul
Branch:    master"
1721571,2019-09-13 16:05:37 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1721571,2017-10-16 15:06:41 UTC,"Change abandoned by int32bit (<email address hidden>) on branch: master
Review: https://review.openstack.org/510456"
1721571,2017-10-09 09:38:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510456"
1721571,2017-10-09 09:30:12 UTC,So should we have any idea to exactly distinguish whether the exception is really an infrastructure issue or execution timeout ?
1721576,2017-10-10 04:52:04 UTC,We actually only need one patch here. I have posted it to LKML: https://patchwork.kernel.org/patch/9995011/
1721576,2017-10-10 05:01:13 UTC,"However, when I look at the 4.11 ubuntu-azure kernel (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/log/?h=master-next), I think we need to pull more related vmbus patches from the mainline, because there are already non-trivial differences."
1721580,2017-10-10 12:11:26 UTC,Tytus
1721580,2017-10-10 12:14:43 UTC,"The issue was finally solved. I'm not sure whether it helped, but I noticed that the following state remains set even if designate is not related to rabbitmq-server:"
1721580,2017-10-10 12:16:06 UTC,hmm but why was that state set?  this still smells like a bug to me
1721580,2017-10-10 12:17:56 UTC,"From my point of view the bug can be marked as invalid, however, I would suggest to take the feedback I provided regarding log messages not being displayed, percona-cluster state checking and the above comment regarding rabbitmq-server."
1721580,2017-10-10 12:18:13 UTC,I'm guessing you removed and re-added the amqp relation maybe?
1721580,2018-03-07 12:56:17 UTC,"This is also a bug in ""charms.reactive"" library - the state is not removed if it's ""None"". I have a patch for both and will submit it shortly."
1721580,2017-10-10 11:35:33 UTC,It looks like for some reason now the designate charm is not exposing the required relation data:
1721580,2018-03-08 10:27:19 UTC,"I've opened a pull request for ""charms.reactive"" library:"
1721580,2018-03-08 10:28:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550770"
1721580,2018-11-21 19:38:32 UTC,"Change abandoned by Tytus Kurek (<email address hidden>) on branch: master
Review: https://review.openstack.org/550770"
1721580,2017-10-10 12:26:47 UTC,"James,"
1721580,2017-10-10 11:26:54 UTC,"I managed to fix the issue with ""clustered"" relation data on rabbitmq-server-tor/0 unit by manually setting it with ""relation-set"" command and there is some progress:"
1721580,2017-10-10 12:29:44 UTC,There is a state/flags issue if you remove and then re-add the amqp relation with rabbitmq-server.
1721580,2017-10-10 09:00:08 UTC,"The following part of ""rabbit_utils.py"" seems to be causing the issues:"
1721580,2017-10-06 15:25:55 UTC,I can confirm that there's no regression in the designate charm as this exact version deploys fine on some other environment. It looks like there's something wrong with this specific environment.
1721580,2017-10-06 15:40:23 UTC,What's the configuration of 'access-network' on the percona-cluster charm?
1721580,2017-10-08 19:02:25 UTC,"James,"
1721580,2017-10-09 09:12:53 UTC,"I've just redeployed on some other environment with the exact charm versions of designate, keystone, percona-cluster and rabbitmq-server and it ended up with ""'identity-service' incomplete"", so at least keystone charm version may be a partial root cause."
1721580,2017-10-09 10:02:35 UTC,"I've redeployed one more time on the other environment and it got deployed. When I was redeploying for the first time, keystone was not related to percona-cluster at the time designate tried to relate with it. So maybe the issue is that if it fails to relate for the first time, it will never relate?"
1721580,2017-10-09 10:18:01 UTC,"Relation ordering should not impact on the final state of the deployment - hook execution gets deferred in keystone until the db is configured, at which point designate will get all the information it needs."
1721580,2017-10-06 11:09:16 UTC,"It looks like the actual problem is that the ""get_remote()"" function does not return the value of the ""access-network"" parameter. I've modified the following part of the code (""hooks/relations/mysql-shared/requires.py""):"
1721580,2017-10-09 14:30:34 UTC,"It looks like ""seeded()"" function returns ""False"" for some reason:"
1721580,2017-10-09 14:38:41 UTC,Found it!
1721580,2017-10-09 15:19:29 UTC,"So it looks like the issue is environment-specific, but I can still see 2 things which could be improved:"
1721580,2017-10-10 07:38:01 UTC,"After re-creating those file both percona-cluster and keystone are no longer in the ""incomplete"" state. I'll keep debugging rabbitmq-server issue."
1721580,2017-10-10 08:43:10 UTC,rabbitmq-server fails at the following piece of the code:
1721580,2017-10-09 14:19:39 UTC,"I made a debug and on the percona-cluster side it fails at the beginning of the ""shared-db-relation-changed"" hook:"
1721580,2017-10-10 09:14:35 UTC,"It looks like rabbitmq-server-tor/2 unit is missing ""clustered"" relation data from rabbitmq-server-tor/0 unit:"
1721585,2017-11-29 17:59:00 UTC,"Encountered in Ubuntu 17.10, fresh install with update current as of today (Nov 29), while trying to install Cinnamon 3.6.2 using:"
1721585,2018-02-28 09:14:03 UTC,Encountered in Ubuntu 17.10 installing inxi with:
1721585,2017-10-22 19:53:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721585,2017-10-20 04:35:49 UTC,I am running into the same issue when I try to install *any* package using apt. It hangs at `Setting up hddtemp (0.3-beta15-52) ...` then timeouts with a plymouth-related error. Running `plymouth --ping` does indeed hang so I have attached the results with strace.
1721585,2017-10-18 19:52:02 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Please check to see if the command 'plymouth --ping' continues to hang in a terminal.  In the event that it does it would help us out if you could run it under strace e.g. 'strace plymouth --ping' so that we can determine why the process is hanging.  Thanks for your assistance!
1721585,2017-10-11 11:42:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721585,2017-10-20 07:13:38 UTC,I don't seem to have this issue anymore since I restarted Ubuntu. `plymouth --ping` doesn't hang anymore neither.
1721613,2018-02-28 17:38:52 UTC,Thanks for reporting.
1721614,2017-10-24 20:26:35 UTC,Original bug report in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1721614
1721614,2019-02-04 13:53:23 UTC,I have the same problem in both Fedora 29 and Ubuntu 18.04. Would really appreciate a fix.
1721614,2018-11-04 22:38:16 UTC,"I've been having the same problem for a while. It is exactly as gpothier described. It is really an annoyance as the only way to get back to work normally, is to basically quit Firefox and start it up again.
I'm using Fedora 28, but the problem was the same on Fedora 27. I tested Fedora 29 too. Would be really nice to have to bug fixed at some point. If can provide any more info about the problem, please let me know."
1721614,2018-06-02 16:32:47 UTC,I did a bisection and found that the problem started appearing here:
1721614,2018-05-31 20:31:07 UTC,"Following up on this report: this bug is 100% reproducible with the Ubuntu 18.04 Live usb image, so it is not a configuration/package issue on my system."
1721614,2018-05-31 15:39:09 UTC,This is still an issue in 18.04 and can be reproduced from the live image.
1721614,2017-12-19 15:37:04 UTC,"The bug is still present in v58.0b11. I'll try to give more precisions. As I wrote earlier, pop up menus appear at incorrect locations after reconfiguring monitors. As shown in the attached video, they can appear quite far away from their correct location. Maybe an important point is that the DPI settings change between configurations. One configuration is with only the internal laptop monitor at 3200 x 1800 with high DPI settings, and the other one is internal + external monitor, both at 1920 x 1080 (normal DPI settings)."
1721614,2017-10-24 20:27:09 UTC,Firefox v57 beta also affected. Reported upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1411398
1721614,2017-10-24 20:26:01 UTC,"Created attachment 8921616
firefox-bug.mp4"
1721614,2017-10-18 11:02:09 UTC,I found out that it doesn't work with my Nvidia GT430 and propritary driver 384.90.
1721614,2017-10-11 15:12:27 UTC,Starting with --safe-mode gets the burger menu working properly again.
1721614,2017-10-11 15:02:16 UTC,"But in 58.0a1 no button menu is drawn correct. Only the bookmark button toggles the bookmarklist on the left of the window (uBlock, NoScript & burger menu)."
1721614,2017-10-11 14:56:43 UTC,Tested 58.0a1 tarball -> burger menu not visible but works if you know the button position. ;-)
1721614,2017-10-11 14:50:24 UTC,"I'm affected of the ""invisible"" burger menu aswell. After click hovering over it shows there are the menu buttons below."
1721614,2017-10-11 14:41:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721614,2017-10-07 18:22:39 UTC,A precision: suspend/resume is not needed to reproduce the issue. Just disconnecting the external monitor is enough to consistently trigger the issue.
1721614,2017-10-05 18:46:04 UTC,"This video shows that the bookmark folder that should appear below the corresponding bookmark icon appears elsewhere. It also shows that the menu responds to mouse movements as if it was correctly placed: the entries are highlighted/unhighlighted as I move the mouse under the bookmark icon, where the menu should be."
1721614,2017-10-24 19:54:47 UTC,"Hi Thorsten, I think what you experience is another bug, as I don't experience your symptoms (invisible burger menu) and you don't seem to experience mine (misplaced or offset menus)."
1721618,2018-04-04 01:29:29 UTC,"We ran across another instance of this bug today, on a different system."
1721622,2020-01-06 06:53:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721622,2017-10-05 19:17:15 UTC,The size of the small font is about 1.2mm the bigger fonts are approx. 4mm
1721627,2017-10-20 06:27:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721627,2017-11-03 18:17:03 UTC,"Just tested this, today, on 17.10, and this issue appears to be fixed: locking the screen and unlocking it still shows the AppIndicator icons in the top-right, including Dropbox."
1721629,2017-10-05 20:22:03 UTC,"I originally suspected the wrong packaging branch was used for the agents, but it's unclear. Agents starting with 1.25.10 are building for the wrong arches."
1721634,2017-10-06 22:35:48 UTC,"Cannot replicate with Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1."
1721635,2017-10-05 20:56:56 UTC,"Hello,"
1721635,2017-10-06 00:23:55 UTC,"The attachment ""lighttpd.service.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1721635,2017-10-06 21:03:43 UTC,"Test packages are building here for xenial, zesty and artful: https://launchpad.net/~ahasenack/+archive/ubuntu/lighttpd-reload-1707312-1721635"
1721635,2020-09-23 21:53:57 UTC,"lighttpd 1.4.46 was released in Oct 2017, almost 3 years ago.
Is there any reason this is still open?"
1721635,2020-09-23 22:09:55 UTC,Fix discussed here never arrived into Ubuntu 16.04.
1721635,2020-09-23 22:29:22 UTC,"I am a lighttpd developer.  Most of the issues I see here can, if needed, have patches backported by me in 5-10 mins."
1721635,2020-09-23 22:44:09 UTC,The easiest fix for Ubuntu 16.04 (and probably 18.04 too) is:
1721635,2020-09-23 23:34:29 UTC,"Yes, the fix is trivial.  Someone needs to do it in those versions."
1721637,2018-04-07 14:54:34 UTC,"I started settings after installation and it worked. But when I clicked on Users tab, it freezed. So I clicked wait twice and then force close. Then I reinstalled and settings didn't work anymore."
1721637,2018-04-07 15:37:55 UTC,"David and Ales, please file new bugs since it's not clear that your bugs are the same as this bug."
1721637,2018-04-07 15:38:33 UTC,Please run this command to file the bug so that information about your system is included that can help bug triage:
1721637,2018-05-04 11:32:11 UTC,"Hello, 4 me the problem is solved after installing gnome-control-center."
1721637,2018-05-14 14:40:48 UTC,"Here is how settings is ""displayed"", when control panel is in bottom of the display."
1721637,2019-01-18 11:36:10 UTC,@Sebastian I provide more detail and info below
1721637,2018-12-12 15:30:22 UTC,What vertical space do you have? Is it that the settings dialog is too tall to fit on the screen with the dock at the bottom?
1721637,2019-01-17 18:16:06 UTC,Maybe it's an old problem but I did a fresh install of 18.04.1 yesterday and today I moved the Dock to the bottom and could not get access to Settings any more.
1721637,2019-01-18 09:29:52 UTC,"@David, your comment is not clear. You didn't have that second screen before moving the dock? When that happens, can you move the dock back to the left and then open settings? If so what config is displayed in the displays section?"
1721637,2019-01-18 12:26:49 UTC,"Thanks for the details, so yeah it seems the issue you are having is that ""ghost"" screen which is either an hardware or a kernel/driver issue but not a settings one. That's an issue but if that's what the bug is about then it should be closed as invalud from the setting side"
1721637,2021-02-20 03:07:30 UTC,"Not sure if this helps.. Same thing happened on 20.04 LTS after moving dock to bottom.. Moved my cursor way over past the right edge of my display to where I thought would be the title bar of the settings window in the imaginary second screen, dragged it back into main screen. Took me a couple click and drags to find it.  Now you can go into display settings and click ""Single Display"" under Display Mode, then click ""Built-in Display"" and hit apply. Now you can reposition dock anywhere without disappearing menu and cursor wont escape the boundary."
1721637,2021-02-20 03:10:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721637,2018-07-10 06:06:47 UTC,"(@Cleber Cassol) This is an year old issue but I had the same problem yesterday. So I did what you said, I used the dconf editor and set the dock to left and the the system settings started working again. I also had the problem where my mouse was disappearing to the right. I opened
'Settings>Devices>Displays' where I saw that the Display Mode was set to 'Join Displays' by default. I changed it 'Single Display' and now the mouse works properly. I am using ubuntu on a lenovo G580 laptop and my BIOS is inaccessible. It seems ubuntu and lenovo don't work well there have been many similar issue. Forunaely my laptop boots properly I just can't access the BIOS, many however are not so lucky..."
1721637,2018-04-05 13:53:00 UTC,I'm experiencing this as well. When I try to install gnome-control-center I get:
1721637,2018-02-07 11:33:54 UTC,"in dconf-editor everything is by default
gnome-control-center is not installed"
1721637,2018-02-07 11:34:15 UTC,back to confirmed and fix the problem
1721637,2017-10-05 20:36:45 UTC,"screenshot show modal, but i can not see it"
1721637,2017-10-21 04:10:52 UTC,"I'm having the same problem. Started soon after I changed the dock position from left to bottom. Have already tried to reinstall gnome-control-center, but to no avail. Rebooting won't help either."
1721637,2017-10-21 04:17:46 UTC,"I believe I know what's happening: it looks like Ubuntu created a virtual screen. If I put my mouse pointer to the right, it vanishes the same way it does when there's a second monitor/screen attached to the system. Don't know how it happened, though, since I haven't changed my screen resolution or displays."
1721637,2017-10-21 04:27:30 UTC,"Ok, a little workaround did restore the System Settings for me (assuming one had this problem after changing the dock position just like me):"
1721637,2018-03-20 18:52:43 UTC,"I installed Ubuntu 17.10.1 today on my laptop, and got the same problem. Opened settings and moved the dock to the bottom, and the settings window just disappeared. The answer given in the following link helped me to disable the second virtual monitor from the command line, and restored the settings window back to my normal laptop screen view:"
1721637,2017-10-22 17:01:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721637,2017-10-22 17:01:38 UTC,"Same problem, and no apparent virtual screen is present."
1721637,2017-10-22 18:01:44 UTC,"I don't know if it's related or not to the problem, but here it goes. I'm using Ubuntu 17.10 on a laptop that has a Nvidia 540M GPU and also an onboard Intel GPU. It seems Ubuntu is assigning a monitor for each (there's an unknown second monitor on my setup and I have no idea where it came from)."
1721637,2017-10-23 14:10:52 UTC,"The description and comments are a bit confusing. Does it has to do with misconfiguration of scrreens? Or a gnome-shell extension?
The screenshot in #comment1 looks right, what's the issue on it?"
1721637,2017-12-17 07:16:34 UTC,"I had the same issue. In my case it turned out that gnome-control-center had been uninstalled. I'm not sure why, but reinstalling fixed it."
1721637,2018-01-07 22:44:10 UTC,"Dear friends
I have the same problem as you had. I read all the comments but I am new to ubuntu and sometimes I don't understand what you are talking about (technically speaking). For example, what does it mean:"
1721637,2018-01-07 23:44:37 UTC,Hi!
1721637,2018-02-07 11:28:04 UTC,вот же говно
1721637,2017-10-22 17:12:45 UTC,"I have deactivated all the gnome extensions. Rebooting and the control center launch normally... So it's a workaround, before I isolate what is exactly the problem and possibly the extension (if only one is implicated)."
1721637,2018-01-10 18:44:17 UTC,"I am also experiencing this issue, when I click on settings it ""loads"" for a few seconds but nothing is displayed."
1721640,2017-10-08 17:34:32 UTC,"That is true. Currently the IMDB-plugin only finds the plot on the main film page, not on the plot-summary subpage, because the tags were changed (I suppose). I updated the PluginMovieIMDB.py. The file goes into the lib/plugins/movie folder of your griffith program folder. Tested it with a bunch of films, hope I havn't put more bugs into it than I removed."
1721640,2017-10-08 17:39:34 UTC,"This also affect the IBDBde plugin. I can send a patch for this, too. But since IMDB has canceled imdb.de, there is no much use of it, I guess. Or are there any german contents that I didn't see?"
1721640,2017-10-08 18:41:46 UTC,"Now it's working perfectly. Thanks so much, Hans! =D"
1721643,2017-10-13 08:37:54 UTC,Hi team - is anyone proposing to look at this?
1721647,2017-11-17 00:19:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721648,2019-10-25 08:50:40 UTC,Test cases can always be adjusted - no doubt about it (and also the reason why this is marred with Importance low).
1721648,2020-01-27 04:17:19 UTC,[Expired for s390-tools (Ubuntu) because there has been no activity for 60 days.]
1721648,2020-01-27 04:17:23 UTC,[Expired for Ubuntu on IBM z Systems because there has been no activity for 60 days.]
1721648,2020-10-08 00:43:49 UTC,Same behavior in 20.10
1721648,2019-10-25 08:22:30 UTC,"I run a short test :
root@m3545034:~# lsmem --v
lsmem from util-linux 2.34
root@m3545034:~# lsmem -V
lsmem from util-linux 2.34
root@m3545034:~# lsmem -v
lsmem: invalid option -- 'v'
Try 'lsmem --help' for more information."
1721648,2019-06-03 14:45:04 UTC,Waiting for an update from IBM - setting to Incomplete for now.
1721652,2017-10-17 18:08:24 UTC,"Reviewed:  https://review.openstack.org/510938
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9252ffdacf262008bc41409d4fb574ec472dc913
Submitter: Zuul
Branch:    master"
1721652,2017-10-25 19:22:08 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1721652,2017-10-24 12:41:40 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1721652,2017-10-18 22:10:55 UTC,"Reviewed:  https://review.openstack.org/511759
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1657b8721d82056cb6e9b2ec7ae7690ca215cb14
Submitter: Zuul
Branch:    stable/pike"
1721652,2017-10-17 16:53:46 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/512716"
1721652,2017-10-18 22:48:05 UTC,"Reviewed:  https://review.openstack.org/512716
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb968e18b2472b0dd7231ff3244b683d59f04cd0
Submitter: Zuul
Branch:    stable/pike"
1721652,2017-10-13 08:02:43 UTC,"Reviewed:  https://review.openstack.org/510176
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a3c556963eaf408a29b27a1f6fc44bc424e48efc
Submitter: Jenkins
Branch:    master"
1721652,2017-10-10 16:50:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510938"
1721652,2017-10-06 16:26:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/510176"
1721652,2017-10-06 15:57:33 UTC,So the functional test did not catch this because there we just stop and start the compute service but did not destroy it so some state survives. We need to enhance the functional test to reproduce the problem.
1721652,2017-10-06 15:49:32 UTC,We'll have to backport whatever the fix is to stable/pike:
1721652,2017-10-06 15:38:33 UTC,This seems like a valid bug. Unfortunately the provided functional test did not catch the reported problem.
1721652,2017-10-13 08:13:51 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/511759"
1721656,2017-10-06 17:36:12 UTC,"I have had this same problem before. Thanks for reporting it. Marking as triaged, with medium importance."
1721661,2020-01-08 18:29:28 UTC,Added Didier to this issue
1721661,2020-01-08 18:26:26 UTC,Scott who created the package initially wrote:
1721661,2019-06-24 04:23:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721669,2017-10-05 23:55:37 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fe72f8b2408 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=<optimized out>, str=0x7fe72f8aed8e ""free(): invalid pointer"", ptr=<optimized out>, ar_ptr=<optimized out>) at malloc.c:5423
 _int_free (av=0x7fe72fae4c20 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4172
 __GI___libc_free (mem=mem@entry=0x55b9230dfd0f) at malloc.c:3142
 INT_cairo_surface_destroy (surface=surface@entry=0x55b9230dfd0f) at ../../../../src/cairo-surface.c:988"
1721669,2018-04-12 17:12:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721669,2018-04-12 22:36:21 UTC,"This occurs for me on a system that had been upgraded from 17.04 to 17.10. I've now upgraded it to 18.04 pre-release and Disks's restore function is working again. It does seem to use a lot of CPU, however, but I haven't compare it with another system very scientifically."
1721670,2017-11-15 01:06:51 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1721670,2017-10-25 19:22:12 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1721670,2017-10-24 12:41:47 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1721670,2017-10-06 04:44:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/509967"
1721670,2017-10-18 09:44:50 UTC,"Reviewed:  https://review.openstack.org/511292
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=594b33469bc162174eb2e221849b2aac78a5d130
Submitter: Zuul
Branch:    stable/pike"
1721670,2017-10-11 19:41:27 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/511325"
1721670,2017-10-11 16:49:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/511292"
1721670,2017-10-11 07:30:58 UTC,"Reviewed:  https://review.openstack.org/509967
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=54cf9f5a90d745896d133669e6d1260e6adee51b
Submitter: Jenkins
Branch:    master"
1721670,2017-10-23 10:51:10 UTC,"Reviewed:  https://review.openstack.org/511325
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d7a60f8a1c51070237590d975b1acc61f4bbcfca
Submitter: Zuul
Branch:    stable/ocata"
1721674,2020-04-15 21:57:50 UTC,Please attach debug logs from simple-scan after scanning
1721676,2017-12-15 21:12:59 UTC,The snapd pull request is located here: https://github.com/snapcore/snapd/pull/3998/
1721676,2017-10-30 19:43:07 UTC,This bug was fixed in the package linux - 4.4.0-98.121
1721676,2019-10-29 18:16:05 UTC,This has been fixed and is available in snapd for multiple releases now. I'm marking it as fix released.
1721676,2017-10-30 19:26:53 UTC,This bug was fixed in the package linux - 4.10.0-38.42
1721676,2017-10-11 18:44:05 UTC,Here's the kernel test case that I mentioned in the bug description.
1721676,2017-10-18 08:59:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1721676,2017-10-06 04:56:32 UTC,The Xenial and Zesty kernel patch sets have been sent to the kernel team:
1721676,2017-10-18 23:08:48 UTC,I tested the linux kernel SRU in Xenial and Zesty using the following linux package versions:
1721676,2017-10-06 02:27:42 UTC,The kernel patches for this feature have already been released in an Artful kernel (4.12.0-13.14).
1721676,2017-10-18 08:56:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1721678,2017-10-06 22:28:48 UTC,"ARCH=`dpkg --print-architecture`
curl -L https://github.com/coreos/etcd/releases/download/${ETCD_VER}/etcd-${ETCD_VER}-linux-${ARCH}.tar.gz -o /tmp/etcd-${ETCD_VER}-linux-${ARCH}.tar.gz
tar xzvf /tmp/etcd-${ETCD_VER}-linux-${ARCH}.tar.gz -C /tmp/etcd --strip-components=1"
1721678,2018-02-14 08:12:37 UTC,Maybe needs to change for all distros in https://docs.openstack.org/install-guide/environment-etcd.html or mentions that the install-guide is mainly based on amd64 architecture.
1721678,2019-01-16 20:10:08 UTC,The current version of the page doesn't seem to have this issue.
1721678,2019-01-16 22:12:02 UTC,The issue is now on this page:
1721678,2019-02-22 19:08:04 UTC,Thanks John; I missed that.
1721678,2019-05-15 17:53:43 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659354"
1721678,2019-05-22 15:46:16 UTC,"Reviewed:  https://review.opendev.org/659354
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=0450a2f5a66bedc25a7355c1baf0bb05a41d2dc3
Submitter: Zuul
Branch:    master"
1721681,2017-10-12 19:11:33 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1721681,2017-10-12 18:54:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721681,2017-10-06 03:25:34 UTC,"StacktraceTop:
 XGetModifierMapping (dpy=dpy@entry=0x55ef9b98e100) at ../../src/ModMap.c:41
 im_uim_init_modifier_keys () at ../../gtk2/immodule/key-util-gtk.c:333
 im_module_init (type_module=0x55ef9beea4b0) at ../../gtk2/immodule/gtk-im-uim.c:1808
 gtk_im_module_load (module=0x55ef9beea4b0) at ././gtk/gtkimmodule.c:171
 g_type_module_use (module=module@entry=0x55ef9beea4b0) at ../../../../gobject/gtypemodule.c:244"
1721686,2017-10-09 02:23:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510392"
1721686,2017-11-29 22:01:08 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/510392"
1721693,2017-10-06 05:44:52 UTC,"That's strange. The colour profile is different (despite having none configured and using identical monitors). The list backgrounds look darker on the 17.10 Wayland machine I took the screenshot on, than on my 16.04 desktop I'm now viewing the image on."
1721693,2018-12-19 15:58:23 UTC,"That's more a theme issue than a settings one right? Also with the new theme in 18.10 the rows don't alternate colors, does that resolve the issue for you?"
1721702,2019-02-19 14:47:35 UTC,"I haven't seen this for a long time, so I think we could close it."
1721702,2019-02-19 13:56:02 UTC,Is this still an issue?
1721702,2018-01-08 11:41:59 UTC,"Reopening this, because it happens again:"
1721702,2018-01-03 00:48:33 UTC,"Min. TTL in tripleo-ci is enforced after https://review.openstack.org/524018
merged Dec 1.
Are there anymore DNS issues since then?"
1721702,2017-11-21 23:03:18 UTC,"rdoinfo is actually at https://review.rdoproject.org/r/rdoinfo
github.com is only a mirror but it was argued that it is more reliable than rdoproject.org hence it is used.
Alternative would be to mirror it into upstream infra but I've heard that proxy-cache for git over http will not work, any other suggestions?"
1721702,2017-11-20 20:42:21 UTC,"Some more information, github.com only has TTL of 30secods, which doesn't make it good for caching results in unbound.  we've discussed maybe setting cache-min-ttl: 300 in unbound.conf, but that could be an issue if github.com changes the DNS (maybe the CDN network) during that cache period."
1721702,2017-10-06 18:11:36 UTC,"It turns out that /var/log/unbound.log is not supposed to be used in the upstream nodepool images, rather /var/lib/unbound/unbound.log: https://review.openstack.org/#/c/510202/"
1721702,2017-11-27 21:43:22 UTC,"cache-bogus-ttl is not what we expected it to be.
It sounds like what we'd like to do doesn't exist (yet), it would be the opposite of ""cache-max-negative-ttl"" see: https://bugzilla.redhat.com/show_bug.cgi?id=1360222"
1721702,2017-10-06 18:01:06 UTC,We are not seeing any logs in unbound because the log file is configured with a selinux context that does not allow unbound to write to it:
1721702,2017-10-06 17:39:42 UTC,This happens from time to time and we need to fix the unbound.log so we can see why
1721704,2020-05-19 11:13:01 UTC,Seems that some of the general AppArmor rules needs to get updated.
1721704,2017-12-02 20:22:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721704,2019-09-06 16:58:22 UTC,"Still happening on 18.04 - slight difference - I can't get past the ""Select Printer Driver"" screen while ""Loading drivers database..."" and the swirling busy icon are up, so I don't have the printer at all."
1721704,2020-05-13 09:17:13 UTC,Still happening on 20.04.
1721704,2020-05-15 21:10:39 UTC,"Thank you for your bug report, could you take a screenshot of the dialog showing the issue and add a 'journalctl -b 0' log from the session after getting the bug?"
1721704,2020-05-19 08:47:05 UTC,Seems to be an issue with apparmor. Here is my output of 'journalctl -b 0':
1721704,2020-05-19 16:47:47 UTC,"@Till, the boot_id issue is being tracked here: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564"
1721708,2019-10-25 15:35:12 UTC,Could affect landscape-pgsql upgrade-series for the LMA stack.
1721712,2017-10-06 08:16:59 UTC,"According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858064 it has been removed when all 1024-bit root certificates have been removed, but this certificate is 4096bit, so it is obviously a mistake:"
1721712,2017-10-06 11:40:18 UTC,"Hi,"
1721730,2017-10-09 08:06:03 UTC,"To dive into this, we should collect the logs of the various participating components:
* dpm-driver
* zhmcclient
* HMC
* SE"
1721730,2017-10-09 11:10:34 UTC,"-ebf95baf5ca3'}
        Body:
2017-10-09 12:54:32,945 12405 INFO     [tempest.lib.common.ssh] Creating ssh connection to '172.24.4.12:22' as 'root' with public key authentication
2017-10-09 12:54:36,257 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 1. Retry after 2 seconds.
2017-10-09 12:54:41,757 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 2. Retry after 3 seconds.
2017-10-09 12:54:48,257 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 3. Retry after 4 seconds.
2017-10-09 12:54:55,757 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 4. Retry after 5 seconds.
2017-10-09 12:55:04,257 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 5. Retry after 6 seconds.
2017-10-09 12:55:13,757 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 6. Retry after 7 seconds.
2017-10-09 12:55:24,257 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 7. Retry after 8 seconds.
2017-10-09 12:55:35,757 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 8. Retry after 9 seconds.
2017-10-09 12:55:48,267 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 9. Retry after 10 seconds.
2017-10-09 12:56:01,787 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 10. Retry after 11 seconds.
2017-10-09 12:56:16,297 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 11. Retry after 12 seconds.
2017-10-09 12:56:31,807 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172.24.4.12). Number attempts: 12. Retry after 13 seconds.
2017-10-09 12:56:48,317 12405 WARNING  [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to root@172.24.4.12 ([Errno None] Unable to connect to port 22 on 172..."
1721730,2017-10-09 11:12:12 UTC,This is the tempest log in HMC I am able to see the partition launched in active state with login credentials displayed (Non-emergency shell mode)
1721730,2017-10-09 11:18:09 UTC,"        Body: {""server"": {""OS-EXT-STS:task_state"": ""deleting"", ""addresses"": {}, ""links"": [{""href"": ""http://9.152.151.140/compute/v2.1/servers/b0e931ba-5953-47c5-8a6d-5137a0312738"", ""rel"": ""self""}, {""href"": ""http://9.152.151.140/compute/servers/b0e931ba-5953-47c5-8a6d-5137a0312738"", ""rel"": ""bookmark""}], ""image"": """", ""OS-EXT-STS:vm_state"": ""building"", ""OS-SRV-USG:launched_at"": null, ""flavor"": {""id"": ""12345"", ""links"": [{""href"": ""http://9.152.151.140/compute/flavors/12345"", ""rel"": ""bookmark""}]}, ""id"": ""b0e931ba-5953-47c5-8a6d-5137a0312738"", ""security_groups"": [{""name"": ""tempest-TestVolumeBootPattern-1708102144""}], ""user_id"": ""2312da2e111e4229ae1d8a90d3337619"", ""OS-DCF:diskConfig"": ""MANUAL"", ""accessIPv4"": """", ""accessIPv6"": """", ""progress"": 0, ""OS-EXT-STS:power_state"": 0, ""OS-EXT-AZ:availability_zone"": ""nova"", ""config_drive"": """", ""status"": ""BUILD"", ""updated"": ""2017-09-13T10:09:49Z"", ""hostId"": ""3bdbf6fdd7747b7dbcd1371dc7ce664516d9fd0516d709618856167f"", ""OS-SRV-USG:terminated_at"": null, ""key_name"": ""tempest-TestVolumeBootPattern-1647803906"", ""name"": ""tempest-TestVolumeBootPattern-server-1535705781"", ""created"": ""2017-09-13T10:06:39Z"", ""tenant_id"": ""eb2305f88725446bbeb5e3dd138a45f2"", ""os-extended-volumes:volumes_attached"": [{""id"": ""7e20642c-4a8b-432f-83dc-262fb3c419f0""}], ""metadata"": {}}}
2017-09-13 12:12:59,379 34607 ERROR    [tempest.common.compute] Server b0e931ba-5953-47c5-8a6d-5137a0312738 failed to delete in time
2017-09-13 12:12:59.379 34607 ERROR tempest.common.compute Traceback (most recent call last):
2017-09-13 12:12:59.379 34607 ERROR tempest.common.compute   File ""/opt/stack/tempest/tempest/common/compute.py"", line 253, in create_test_server
2017-09-13 12:12:59.379 34607 ERROR tempest.common.compute     clients.servers_client, server['id'])
2017-09-13 12:12:59.379 34607 ERROR tempest.common.compute   File ""/opt/stack/tempest/tempest/common/waiters.py"", line 127, in wait_for_server_termination
2017-09-13 12:12:59.379 34607 ERROR tempest.common.compute     raise lib_exc.TimeoutException
2017-09-13 12:12:59.379 34607 ERROR tempest.common.compute TimeoutException: Request timed out
2017-09-13 12:12:59.379 34607 ERROR tempest.common.compute Details: None
2017-09-13 12:12:59.379 34607 ERROR tempest.common.compute
2017-09-13 12:12:59,442 34607 INFO     [tempest.lib.common.rest_client] Request (TestVolumeBootPattern:_run_cleanups): 400 DELETE http://9.152.151.140/volume/v3/eb2305f88725446bbeb5e3dd138a45f2/volumes/7e20642c-4a8b-432f-83dc-262fb3c419f0 0.061s
2017-09-13 12:12:59,442 34607 DEBUG    [tempest.lib.common.rest_client] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-Auth-Token': '<omitted>'}
        Body: None"
1721730,2017-10-09 11:20:38 UTC,"sometimes it fails due to this issue like unable to delete server within time ....For this I tried to
increase the 'ready_wait' parameter which means that it waits this long to start with the next process"
1721730,2017-11-13 04:34:17 UTC,"Sreeteja, as discussed reducing the prior to High, as the issue is sporadic"
1721736,2017-10-11 02:42:52 UTC,"What version are you using now? Looking at the ocata code, here's the code for the add user action: https://github.com/openstack/horizon/blob/stable/ocata/openstack_dashboard/dashboards/identity/users/tables.py#L27. Please check if the policy rules and the OPENSTACK_KEYSTONE_BACKEND setting on local_settings.py are set properly."
1721736,2017-10-10 04:29:06 UTC,"Yes. rallyadmin has the admin role to the rally project, in the rally domain."
1721736,2017-10-06 13:23:22 UTC,I am having the same issue as well.
1721736,2017-10-10 04:09:06 UTC,"Does the user rallyadmin have admin role in the project that you are trying to add users from? With rallyadmin's openrc file, can you add users to the project with CLI?"
1721738,2017-10-06 10:33:32 UTC,"StacktraceTop:
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0xc5e7, hash_table=0x55d5485a5060) at ../../../../glib/ghash.c:408
 g_hash_table_insert_internal (hash_table=0x55d5485a5060, key=0xc5e7, value=0x7f8fd4837030, keep_new_key=0) at ../../../../glib/ghash.c:1233
 g_source_attach_unlocked (source=source@entry=0x7f8fd4837030, context=context@entry=0x55d5485a00c0, do_wakeup=do_wakeup@entry=1) at ../../../../glib/gmain.c:1159
 g_source_attach (source=0x7f8fd4837030, context=0x55d5485a00c0) at ../../../../glib/gmain.c:1217
 g_task_attach_source (task=task@entry=0x7f8fd43c2d50, source=<optimized out>, callback=callback@entry=0x7f8ff6b88410 <send_message_with_reply_timeout_cb>) at ../../../../gio/gtask.c:1534"
1721738,2017-10-09 17:51:12 UTC,"From the retraced Stacktrace.txt, it looks like a client dconf thread is sending a message to the session DBus daemon which ends up trying to use a bogus GTask structure."
1721745,2017-10-14 18:21:04 UTC,"(Y PPA Manager:15737): Gdk-WARNING **: /build/gtk+3.0-Th_a5U/gtk+3.0-3.22.24/./gdk/x11/gdkwindow-x11.c:5573 drawable is not a native X11 window
/usr/bin/y-ppa-cmd: line 119: warning: command substitution: ignored null byte in input
No protocol specified
Unable to init server: Could not connect: Connection refused"
1721749,2018-03-22 01:49:25 UTC,fixed with 8.5.29-1 in bionic
1721749,2018-05-30 17:35:32 UTC,This bug was fixed in the package tomcat8 - 8.5.21-1ubuntu1.1
1721749,2018-05-30 17:35:33 UTC,This bug was fixed in the package tomcat8 - 8.0.32-1ubuntu1.6
1721749,2021-01-09 06:20:56 UTC,tomcat7 (7.0.52-1ubuntu0.14) trusty-security; urgency=medium
1721753,2018-01-25 09:18:07 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1118
1721753,2017-12-13 12:07:24 UTC,Workaround: use ignore index(organizationOID)
1721753,2017-12-13 11:52:19 UTC,Not repeatable with version 5.5
1721753,2017-12-13 11:49:43 UTC,Thank you for the report.
1721753,2017-10-12 11:35:30 UTC,"FYI: I will try to reproduce this problem some more times, it´s just taking a while because of other work. Will get back to you."
1721753,2017-10-07 09:01:03 UTC,"Hi,"
1721753,2017-10-06 11:59:03 UTC,FYI: Same result on 5.6.37-82.2
1721753,2017-11-06 12:26:37 UTC,"Ok i was able to test a bit and i don´t think that 5.6.36-82.0 or 2.6.37-82.2 are different, so lets just go with the most recent one."
1721756,2017-10-06 11:16:52 UTC,ouverture document avec   sweet home 3D
1721756,2017-10-06 11:27:34 UTC,"StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x7f3e469aa743 ""kref"", file=file@entry=0x7f3e469aa72a ""../../nouveau/pushbuf.c"", line=line@entry=727, function=function@entry=0x7f3e469aa770 <__PRETTY_FUNCTION__.6337> ""nouveau_pushbuf_data"") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f3e469aa743 ""kref"", file=file@entry=0x7f3e469aa72a ""../../nouveau/pushbuf.c"", line=line@entry=727, function=function@entry=0x7f3e469aa770 <__PRETTY_FUNCTION__.6337> ""nouveau_pushbuf_data"") at assert.c:101
 nouveau_pushbuf_data (push=push@entry=0x7f3e704ae100, bo=0x7f3e704ae340, offset=0, length=43944) at ../../nouveau/pushbuf.c:727
 nouveau_pushbuf_data (push=push@entry=0x7f3e704ae100, bo=bo@entry=0x0, offset=offset@entry=0, length=length@entry=0) at ../../nouveau/pushbuf.c:719
 nouveau_pushbuf_space (push=push@entry=0x7f3e704ae100, dwords=dwords@entry=18, relocs=relocs@entry=0, pushes=<optimized out>, pushes@entry=0) at ../../nouveau/pushbuf.c:689"
1721763,2017-12-23 20:13:14 UTC,"Yes, it is, fresh instalation of ubuntu in my notebook do this automatically."
1721763,2017-12-22 12:39:52 UTC,"is 'intel-microcode' been installed ? If not, then do and reboot."
1721763,2017-12-22 11:13:13 UTC,"Yesterday I decided to do a fresh reinstallation of ubuntu on my notebook and after having reinstalled some of the applications and daemons I use normally, I performed one of several reboots that I normally do in these processes."
1721763,2017-10-08 23:54:07 UTC,"There is another case that is very strange. The suspend mode is not working, either, since the kernel 4.12 upgrade onwards (in 4.11 it worked fine)."
1721763,2017-10-06 19:50:57 UTC,And it's all.
1721763,2017-10-06 19:49:50 UTC,out 06 16:02:47 etm kernel: nouveau 0000:01:00.0: gr: intr 00000040
1721763,2017-10-06 19:48:46 UTC,out 06 16:02:22 etm kernel: nouveau 0000:01:00.0: gr: intr 00000040
1721763,2017-10-06 19:48:03 UTC,"out 06 16:02:22 etm wpa_supplicant[1133]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
out 06 16:02:22 etm wpa_supplicant[1133]: dbus: Failed to construct signal
out 06 16:02:22 etm wpa_supplicant[1133]: Could not read interface p2p-dev-wlp3s0 flags: No such device"
1721763,2017-10-06 19:47:28 UTC,out 06 16:02:21 etm gnome-session-binary[1110]: Unrecoverable failure in required component org.gnome.Shell.desktop
1721763,2017-10-06 12:07:52 UTC,"By the way, the issue I want to relate is just that one on the sumary:"
1721763,2017-10-06 19:45:16 UTC,out 06 16:02:21 etm avahi-daemon[901]: chroot.c: open() failed: No such file or directory
1721763,2017-10-06 19:44:49 UTC,"out 06 16:02:20 etm kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080
out 06 16:02:20 etm kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080"
1721763,2017-10-06 19:44:06 UTC,"out 06 16:02:20 etm kernel: [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
out 06 16:02:20 etm kernel: [drm:intel_ddi_init [i915]] *ERROR* LSPCON init failed on port B"
1721763,2017-10-06 19:42:44 UTC,and this:
1721763,2017-10-06 19:30:38 UTC,There go some errors:
1721763,2017-10-06 19:28:00 UTC,"The ""hitting 'Esc'"" technic gaves me no much:"
1721763,2017-10-06 18:54:52 UTC,"""
Most of the time, such problem means a non responding task still running in the background.
So be sure your system is cleaned (use gtkorphan & bleachbit to clean it).
"""
1721763,2017-10-06 12:32:35 UTC,"Also note that nvidia driver have issue with wayland (see ubuntuforums u+1), so select a xorg session instead at login time."
1721763,2017-10-06 12:22:58 UTC,"Most of the time, such problem means a non responding task still running in the background.
So be sure your system is cleaned (use gtkorphan & bleachbit to clean it)."
1721763,2017-10-06 19:45:40 UTC,out 06 16:02:21 etm NetworkManager[884]: ((src/devices/nm-device.c:1452)): assertion '<dropped>' failed
1721763,2017-10-06 19:46:50 UTC,out 06 16:02:21 etm gnome-session-binary[1110]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erro ao chamar StartServiceByName para org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
1721781,2017-10-13 08:14:48 UTC,"I'm not sure it should be brought back, since there are still bugs with it, see
https://lists.freedesktop.org/archives/intel-gfx/2017-October/142787.html"
1721781,2017-10-06 13:55:26 UTC,see https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1645911
1721781,2017-10-06 21:46:41 UTC,the fw is only missing from xenial
1721781,2017-10-06 13:56:43 UTC,btw - Noticed the same error on the 4.4 kernel with i915 BPO.
1721783,2017-10-19 17:56:51 UTC,"Is that still the case? Is the issue persistent after a restart? What does ""snap list"" tell?"
1721783,2017-10-19 17:57:31 UTC,"ignore the ""snap list"" question, I didn't see at first that the right side of the screenshot was having that information"
1721783,2017-10-20 07:47:29 UTC,Now I've the opposite problem where not all the snaps installed are listed in 'installed packages'
1721788,2017-10-06 14:28:37 UTC,"The QEMU process that has the disk image open may be doing I/O that causes qcow2 metadata to be changed. Such changes could confuse the 'qemu-img' process it is was reading the metadata at the same time it was being changed, causing bad data to be printed or worse. So requiring a write lock is the 'safe' thing to do for reliability in the worst case. You can override this by passing '--force-share' arg though."
1721788,2017-10-06 14:28:48 UTC,"On 10/06/2017 09:09 AM, Jan Heidbrink wrote:

> Public bug reported:
>
> When running 'qemu-img info test.qcow2' while test.qcow2 is currently
> used by a Qemu process, I get the error
>
> qemu-img: Could not open 'test.qcow2': Failed to get shared ""write""
> lock.
>
>
> Why does displaying information about a disk image need a write lock for the file?
"
1721788,2017-10-06 14:30:14 UTC,"I've just noticed, however, that '--force-share' appears totally undocumented in both CLI help output and the man page. So that's certainly something that should be fixed"
1721788,2017-10-11 20:46:40 UTC,"This does  not only affect qemu-img only, it could not make libvirt
""<shareable>"" work either when two vms were running with share disk
image.  Is there a workaround for this situation?"
1721794,2017-10-09 12:16:40 UTC,?????????
1721794,2017-10-06 14:58:06 UTC,any help ???
1721797,2017-10-06 15:27:16 UTC,"StacktraceTop:
 pa_mutex_free (m=<optimized out>) at pulsecore/mutex-posix.c:83
 pa_threaded_mainloop_free (m=0x7f0794001390) at pulse/thread-mainloop.c:139
 pa_simple_free (s=0x7f0794001340) at pulse/simple.c:267
 pulse_connection_close (pulse_id=0x7f07ac00bc70) at pulse.c:142
 pulse_close (id=0x7f07ac00bc70) at pulse.c:269"
1721797,2018-03-21 20:39:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721801,2017-10-06 15:43:24 UTC,"forgot the paths are set like:
[mysql@galera1h1n5 galera1]$ cat start
#! /bin/bash --"
1721801,2018-01-18 08:29:16 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2007
1721803,2019-02-07 07:33:24 UTC,"This morning I was able to receive the confirmation email on a @hotmail address. However, I am still unable to receive confirmation emails on other domains with differently configured mail servers."
1721803,2019-02-07 17:24:26 UTC,I can confirm myself that having correct SPF/DMARC entries is KEY on assuring that your email does not endup ignored by most big email services around.
1721803,2019-02-07 18:00:46 UTC,It would help significantly in debugging this if we could get actual mail delivery failure logs/records. We can look at the mail server on ask.openstack.org if you can provide a recipient email address and approximate time for the expected email. Can you get that information to us? Might also help to do this synchronously on IRC as well (freenode #openstack-infra) so that we can find answers to the next questions that pop up.
1721803,2019-02-06 14:20:17 UTC,"Assuming this is about the ask.openstack.org site, our provider apparently placed the netblock for this server's IPv4 address into the Spamhaus Policy Block List recently. I have filed for an exclusion which should take effect within the next hour. https://www.spamhaus.org/query/ip/23.253.72.95"
1721803,2019-07-26 10:46:34 UTC,"still having the same problem
I just tried with google and launchpad accounts, and still not getting a verification email"
1721803,2019-07-26 13:29:54 UTC,"This time I'm unable to find the server on any obvious blacklists, but Gmail is rejecting the confirmation message addressed to you claiming ""Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked."""
1721803,2019-07-28 16:38:00 UTC,I just tried again on a email address managed by axc.nl and managed to receive the confirmation email for becoming a community member. Both the SPF record and DKIM tested out as valid so at least that has been improved.
1721803,2019-06-07 20:46:22 UTC,"Robert: Please try again when you have time. The server hosting ask.openstack.org was rebuilt a little over 2 weeks ago (on May 20), and it wasn't noticed at the time that the IP address assigned for it was covered by a Spamhaus Policy Block List entry maintained by the service provider. An exception has been added to the PBL for this address now, and any providers checking against it should hopefully cease to see it listed as disallowed (very soon at least, if not already)."
1721803,2019-02-06 10:36:17 UTC,I have tried to create an account using launchpad using 4 different email addresses and unfortunately I haven't received an email on any of the addresses.
1721803,2018-01-31 20:40:18 UTC,"Google and others require SPF/DKIM and all the modern shebang before they even start looking at incoming mail. Does the domain have all that? Also, there is IP reputation to keep in mind and since this server has come on and off RBLs, the reputation may be low."
1721803,2018-01-31 21:52:02 UTC,"Per the discussion in bug 1745512 this service is also not listed in the SPF record for openstack.org even though it is sending messages as <email address hidden> so could consider either using a valid @ask.openstack.org address (for which we could set up a corresponding MX record and mailbox somewhere), or get added to the SPF record. That SPF record ends in ""?all"" though, which per the specification should mean it just gets treated as if there were no SPF record when a sender doesn't match. Nonetheless, some receiving MTAs incorrectly treat ? (neutral) like ~ (softfail) or even - (fail) so it _may_ help."
1721803,2017-12-21 21:14:57 UTC,"I have the same error, right now"
1721803,2018-02-01 20:24:19 UTC,Since the Mailspike BL removal yesterday I'm seeing basically no rejections in the MTA log (other than for qq.com addresses). People who were previously having trouble with new account creation should try again and update here if the confirmation E-mails still don't make it through so we can dig deeper.
1721803,2018-01-14 04:57:55 UTC,"Me too, the whole login/signup is broken!!"
1721803,2018-01-15 11:54:27 UTC,"This is probably similar to or related to:
https://bugs.launchpad.net/openstack-community/+bug/1742568"
1721803,2018-01-15 13:59:41 UTC,@fungi I need your help to debug this because I have no access to the machine's logs
1721803,2018-01-15 13:23:23 UTC,The IP is not listed in Spamhaus anymore. Can you please check if now the confirmation email is sent?
1721803,2018-01-15 13:43:54 UTC,"I just tried it with a gmail address, as well as with a address that is running on my own mailserver. I didn't receive the mail to the gmail account, but now I did receive the one to my own server. So it seems like something has changed since both didn't work when I posted this bug - however gmail still declines the mail (it's also not in the spam folder there)."
1721803,2018-01-15 11:56:29 UTC,"Also possibly related, and could well be the cause:
https://bugs.launchpad.net/openstack-community/+bug/1723264"
1721803,2018-01-31 19:44:00 UTC,"The MTA logs indicate that Gmail is deferring/rejecting some messages, but Google is notoriously vague about why. Rejections from some other non-Google MTAs note that the server has become listed in the Mailspike blacklist, and per separate bug 1745512 I've put in a delisting request there. Some rejections also claim the server is covered by a Spamhaus PBL entry but their lookup form disagrees as of today at least (perhaps some MTAs are relying on very stale/cached results?)."
1721805,2018-02-20 21:30:56 UTC,This is affecting our openstack installation as well.
1721805,2018-02-20 21:33:33 UTC,It fails for us both when passed via the `OS_PASSWORD` environment variable and also when passed via `--os-password` on the command line.
1721809,2017-10-06 16:30:08 UTC,This change was made by a bot.
1721809,2017-10-06 20:04:43 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1721809,2017-10-06 21:44:15 UTC,Thanks for the answer.
1721809,2017-10-07 19:50:38 UTC,"I have the exact same problem
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852"
1721809,2017-10-26 13:00:29 UTC,cat /proc/bus/input/devices:
1721809,2017-11-05 08:03:13 UTC,"Please attach `dmesg` under Linux v4.17-rc7, thanks!"
1721809,2017-11-05 10:33:18 UTC,It should be fixed on mainline Linux.
1721809,2017-12-13 21:30:45 UTC,Sorry for my late reply.
1721820,2017-10-06 16:50:01 UTC,Problem occurs in default Unity desktop. Systray functions normally in Cinnamon desktop.
1721821,2017-10-06 16:46:31 UTC,I made an error: my system is using sddm and not lightdm (although this package is also installed).
1721821,2017-10-06 16:47:12 UTC,"My system is using sddm, not lightdm (sorry)"
1721821,2017-10-09 20:06:50 UTC,In JournalErrors.txt I found:
1721821,2017-10-09 20:09:26 UTC,"The problem seem to be a ""timed out"" problem with NetworkManager 1.8.4-1ubuntu1, not sddm."
1721821,2017-10-19 19:39:49 UTC,"I finally reinstalled my system using the Kubuntu 17.10 64 bits ISO today.
It solved the problem."
1721821,2017-10-21 03:30:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721829,2020-03-31 09:11:47 UTC,"I'm closing this, since it's too old. If this is still and issue, please reopen it."
1721829,2019-05-20 19:01:19 UTC,Was this still in the design plans?
1721829,2019-05-20 20:39:37 UTC,"Lil, is this still the case?"
1721829,2019-05-23 15:20:40 UTC,"Ever so slightly different design. If there are any metrics for the tests that were run, display a link to the results that takes the user to the tests tab with the appropriate test expanded."
1721829,2017-10-16 19:28:55 UTC,Using node.storage_test_status_tooltip will give the same message on the card.
1721831,2019-09-19 12:04:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1721833,2017-11-21 15:09:38 UTC,This will be fixed in evolution 3.26.2.
1721833,2018-02-24 05:34:48 UTC,+1
1721833,2018-02-23 15:02:45 UTC,"@jbicha; how can we get this fix delivered into Ubuntu Artful stable? - this has been fixed since Nov2017, and still yet delivered into Ubuntu 17.10"
1721833,2017-11-17 15:23:08 UTC,"It is also happening to me on X11 with Ubuntu 17.10 running vanilla Gnome Session.
The only numbers that work are 6,7,8 and 9."
1721833,2017-11-06 16:26:51 UTC,I've noticed that this problem only exists when using Wayland; it doesn't happen when using Ubuntu on Xorg or Unity.
1721833,2017-11-04 03:18:12 UTC,"""Works fine here with Ubuntu 17.10."""
1721833,2017-10-19 23:03:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721833,2017-10-19 23:03:39 UTC,I have the same issue. I could not input 1234560 (789 functioned fine). This seems to have been introduced between 3.24.5 and 3.26.1. I'm on Arch Linux with i3 as my window manager.
1721833,2017-11-06 17:27:14 UTC,"I can confirm the same as @sleepingkyoto, that 789 work fine."
1721833,2017-10-06 18:03:43 UTC,Works fine here with Ubuntu 17.10.
1721835,2018-07-24 09:33:24 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1721835,2017-10-06 20:04:15 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1721835,2017-10-06 18:00:07 UTC,This change was made by a bot.
1721835,2017-10-06 21:44:15 UTC,Haven't noticed that issue on previous kernels although I was mostly using NVIDIA GPU not integrated intel GPU as in this case.
1721836,2017-10-06 20:24:52 UTC,"The attachment ""Fix-incorrect-byval-parameter-passing.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1721838,2017-10-06 17:59:44 UTC,This bug looks like it is likely the same intent as https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1655717
1721839,2019-09-19 07:28:33 UTC,Is this still an issue on supported releases?
1721839,2018-01-17 23:45:05 UTC,Now in Bionic the only systemd problem known to me is the quoting/unquoting turnaround problem mentioned here.
1721839,2017-10-16 17:42:51 UTC,Reported this bug upstream:
1721839,2017-10-13 14:50:16 UTC,"Till, you should perhaps open a bug on systemd upstream on github since it's likely an issue there? There might have a clue about it or people who are available to debug the issue..."
1721839,2017-10-11 20:21:22 UTC,"Here is the systemd journal of plugging the printer, taken with"
1721839,2017-10-11 20:24:05 UTC,"Now I have proceeded as described in the previous comment for unplugging the printer, issuing this command with the printer still plugged:"
1721839,2017-10-11 19:42:31 UTC,"I have looked through Pitti's (upstream author) instructions of the tool, ut it seems that it only works on the already running device and that there is no way to capture the startup and shutdown sequences."
1721839,2017-10-11 11:26:17 UTC,Could you please record udevmock dump of plugging in and out a USB printer and attach the udevmock file here?
1721839,2017-10-11 11:22:57 UTC,"Given that the service is oneshot, I need a full output of the journal to see what has happened to said service."
1721839,2017-10-11 11:21:55 UTC,"This is not critical. The service is started, but the encoding/decoding of the %i name appears to be not round-trip safe."
1721839,2017-10-11 01:37:33 UTC,It seems that with a 70-printers.rules as follows at least a correct service name is generated
1721839,2017-10-10 13:14:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721839,2017-10-09 16:33:38 UTC,Some discussion with xnox on IRC helped me to get to a possible cause of the problem:
1721839,2017-10-11 19:59:15 UTC,"I have tried recording startup and shutdown now by recording with the command ""sleep 10"" and doing the manual operation (plugging/unplugging USB) during the sleep delay. Unfortunately, it does not work."
1721840,2017-10-09 07:21:38 UTC,"I'm not sure that this was ever enabled. it's documented as ""a highly experimental and dangerous device for calling *arbitrary* C functions in *arbitrary* shared libraries""."
1721840,2017-10-10 16:49:27 UTC,Your changelog entry for 2.2.1-1 suggests that it was enabled once.
1721840,2017-10-10 17:24:42 UTC,"annoyingly python2 has: ctypes.RTLD_GLOBAL  ctypes.RTLD_LOCAL, but not ctypes.RTLD_NOW"
1721840,2017-10-10 17:26:02 UTC,"I wonder if https://pypi.python.org/pypi/backports.os https://github.com/pjdelport/backports.os should grow this feature, since python3 is the future."
1721841,2019-08-19 19:40:59 UTC,Note that we don't get the ceph or ganesha logs in SOS reports because they're not in /var/log/containers (and the journal for these isn't captured either).
1721841,2019-08-28 19:46:09 UTC,As per an update to ceph-ansible 4.x [1] the ceph containers now log to /var/log/ceph [2]
1721841,2019-02-19 15:12:47 UTC,IMO: It's something which would be nice to fix to be consistent but I don't think it's pressing.
1721841,2019-02-19 13:56:25 UTC,Is this still an issue?
1721841,2017-10-10 16:35:05 UTC,This could probably be addressed with https://blueprints.launchpad.net/tripleo/+spec/logging-stdout-rsyslog
1721842,2017-10-10 22:06:05 UTC,Fixed in https://usn.ubuntu.com/usn/usn-3443-1/ and https://usn.ubuntu.com/usn/usn-3443-2/
1721842,2017-10-10 22:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1721842,2017-10-11 20:02:55 UTC,artful still needs to pull in commits 265e60a170d0a0ecfc2d20490134ed2c48dd45ab and 044215d145a7a8a60ffa8fdc859d110a795fa6ea.
1721842,2018-07-24 09:35:41 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1721843,2017-10-25 19:22:15 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1721843,2017-10-24 12:41:53 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1721843,2017-10-19 18:25:29 UTC,"Reviewed:  https://review.openstack.org/510957
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=38dbb0595072092f13c4017dc4edf811fa70fa21
Submitter: Zuul
Branch:    stable/pike"
1721843,2017-10-10 17:21:23 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/510957"
1721843,2017-10-10 20:10:01 UTC,"Reviewed:  https://review.openstack.org/510603
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0ffe03a2650a698de1b83289098ed535734b2360
Submitter: Jenkins
Branch:    master"
1721843,2017-10-10 17:14:48 UTC,Marking as high severity since this is a regression introduced in Pike.
1721843,2017-10-09 15:23:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510603"
1721843,2017-10-09 10:50:58 UTC,To be clear the regression was introduced in I03c8e8225e51fd80580772752c0b292987e34218 not in https://github.com/openstack/nova/commit/29cb8f1c459e6d23dd9303fb570cee773d9c4d02
1721843,2017-10-09 10:48:43 UTC,A possible solution is to remove the decorator from send_instance_update_notification() as the called _send_versioned_instance_update() already has the decorator. This way the legacy notification is still emitted from send_instance_update_notification in every case.
1721843,2017-10-09 10:46:48 UTC,I think the observation is correct. The if_notifications_enabled decorator is applied to early in the send_instance_update_notification call chain.
1721843,2017-10-10 17:19:01 UTC,The regression was introduced with this change: https://review.openstack.org/#/c/459923/
1721850,2017-10-06 19:37:43 UTC,Hi Sam -- I think you're probably running into the issue alluded to by Galen in comment #2 of bug 1508477.
1721850,2017-10-10 10:39:14 UTC,"Yes, I was planning to file a bug on this same issue, but I would like to expand it a bit. The hotkeys don't work in any embedded frame, which includes not only the catalog screens, but any Dojo screens.The problem with the Dojo screens should resolve themselves as Dojo is moved to AngularJS, but since the catalog will remain embedded, it would be great if we could find a solution that allows hotkey use in these screens. Also, it will take time for all of the Dojo screens to be converted, so making this improvement for those screens too would be good."
1721852,2018-03-29 15:50:42 UTC,"It seems that OpenJFX should continue to be packaged separately, just like any other Java library."
1721852,2020-09-23 18:03:17 UTC,I think this bug that I opened is invalid for both openjdk-9 and openjfx. Sorry for not closing it sooner.
1721852,2020-09-23 17:35:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1721852"
1721852,2018-11-19 11:59:03 UTC,"Samuel, that's strange. According to #1799946
in 18.10 there is an OpenJFX package for Java 11 but not for Java 8:"
1721852,2018-05-23 08:46:45 UTC,"The same problem occurs in Ubuntu 18.04 with OpenJDK 10.
There is only a package for OpenJFX for Java 8 but no package for Java 10"
1721852,2018-02-09 18:32:21 UTC,I think that openJFX should be included in openJDK.
1721852,2017-10-10 02:43:06 UTC,"The OpenJFX source tree is separate from the OpenJDK sources, but its modules are included as input into the OpenJDK build process. For the OpenJFX source tree, see here:"
1721852,2017-10-11 23:21:53 UTC,I eventually managed to build OpenJFX 9 with our openjdk-9 package. But I now realize that integrating it into the JRE isn't going to be as simple as it was for OpenJFX 8. I'll start a thread on debian-java to discuss the options.
1721852,2017-10-10 15:55:17 UTC,It seems there are still some dependencies being worked out for the build process. See:
1721852,2017-10-10 06:15:49 UTC,FYI I started working on the openjdk9 package this week.
1721852,2017-10-10 05:29:01 UTC,That would create a build dependency on openjfx. I'm not sure if I like that ...
1721852,2017-10-10 01:05:32 UTC,"The OpenJDK binaries distributed by Oracle still includes some code which isn't found in the OpenJDK sources. There is a recent announcement that this will change, however I currently can't find OpenJFX in the OpenJDK sources."
1721852,2017-10-09 23:39:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721852,2017-10-19 19:15:51 UTC,"I misunderstood what I originally downloaded from the JDK 9 General-Availability Release page (http://jdk.java.net/9/). When Java 9 was first released, that page had a link to the Oracle JDK, not to the OpenJDK. Now that Oracle has released a 9.0.1 update, the OpenJDK is different from the JDK from Oracle and is in fact missing the JavaFX support."
1721856,2017-11-01 17:57:50 UTC,63841b2a6969501de183efafc14d20175e402804 is bad.
1721856,2017-10-31 10:39:49 UTC, 9bc088ab66be8978fbc981ba9644468fa2c2fd3f is bad.
1721856,2017-10-31 19:40:48 UTC,"I built the next test kernel, up to the following commit:
e0f3e8f14da868047c524a0cf11e08b95fd1b008"
1721856,2017-11-01 05:06:42 UTC,e0f3e8f14da868047c524a0cf11e08b95fd1b008 is bad.
1721856,2017-11-01 14:28:40 UTC,"I built the next test kernel, up to the following commit:
2fcc112af37fa88f8da077d6dd3bb8e38e75adb1"
1721856,2017-11-01 14:50:25 UTC,2fcc112af37fa88f8da077d6dd3bb8e38e75adb1 is good.
1721856,2017-11-01 17:15:44 UTC,"I built the next test kernel, up to the following commit:
63841b2a6969501de183efafc14d20175e402804"
1721856,2017-11-01 20:16:26 UTC,"I built the next test kernel, up to the following commit:
2a55e98f9f76825d78a4e6ef315c35fccabf5212"
1721856,2017-10-30 20:30:50 UTC,"I built the next test kernel, up to the following commit:
9bc088ab66be8978fbc981ba9644468fa2c2fd3f"
1721856,2017-11-02 01:32:50 UTC,"I built the next test kernel, up to the following commit:
e7561f1633ac735df48c55ad09a2530e9ab9fab1"
1721856,2017-11-02 20:38:11 UTC, e7561f1633ac735df48c55ad09a2530e9ab9fab1 is good.
1721856,2017-11-02 21:16:38 UTC,"I built the next test kernel, up to the following commit:
525b8ed91671e29e187dfe02d408b11190ccf494"
1721856,2017-11-11 06:37:37 UTC,525b8ed91671e29e187dfe02d408b11190ccf494 is good (assuming that the kernel image package with the later timestamp is the one representing the commit).
1721856,2017-11-14 19:39:44 UTC,"I built the next test kernel, up to the following commit:
91d57bae08689199c8acc77a8b3b41150cafab1c"
1721856,2017-11-15 06:51:18 UTC,91d57bae08689199c8acc77a8b3b41150cafab1c is good.
1721856,2017-11-20 20:32:40 UTC,"The reverse bisect reported the following commit was the fix:
91d57bae0868 (""posix-timers: Make use of forward/remaining callbacks"")"
1721856,2017-11-20 20:45:57 UTC,"Good to know, thank you for your support. The issue is fixed in 4.13.0-16-generic of Ubuntu 17.10 as stated in #16."
1721856,2017-11-01 21:24:28 UTC,2a55e98f9f76825d78a4e6ef315c35fccabf5212 is good.
1721856,2017-10-30 19:17:26 UTC,e7bd9ba20a9ec7024a0566a93c22b9571a48939a is bad.
1721856,2017-10-19 21:13:45 UTC,"I built the next test kernel, up to the following commit:
1849f800fba32cd5a0b647f824f11426b85310d8"
1721856,2017-10-28 00:52:28 UTC, 892ad5acca0b2ddb514fae63fa4686bf726d2471 is bad.
1721856,2017-10-06 19:30:07 UTC,This change was made by a bot.
1721856,2017-10-06 20:02:55 UTC,"Can you see if this bug is fixed in upstream 4.13 or 4.10, which will tell us if the fix was already cc'd to stable."
1721856,2017-10-12 05:07:17 UTC,"> Can you see if this bug is fixed in upstream 4.13 or 4.10, which will tell us if the fix was already cc'd to stable.
"
1721856,2017-10-13 19:27:07 UTC,We can perform a reverse bisect to identify the commit that fixes this bug.  We first need to identify the last bad kernel and first good one.  Can you test the following two kernels:
1721856,2017-10-14 06:34:39 UTC,"> We can perform a reverse bisect to identify the commit that fixes this bug. We first need to identify the last bad kernel and first good one. Can you test the following two kernels:
>
> v4.11: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11
> v4.12: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12
"
1721856,2017-10-16 17:41:49 UTC,"To perform a bisect, we need to identify linear versions.  Can you test the following two kernels:"
1721856,2017-10-16 17:43:32 UTC,"It looks like you may have already tested 4.12 final per comment #6.  If so, we just need to figure out which 4.13 release candidate introduced the fix.  So if v4.13-rc1 is still bad, we would next test -rc2, -rc3, etc until we find the good version."
1721856,2017-10-17 12:17:11 UTC,v4.13-rc1 is good. Please tell me if you need support for this issue from me.
1721856,2017-10-30 18:51:44 UTC,"I built the next test kernel, up to the following commit:
e7bd9ba20a9ec7024a0566a93c22b9571a48939a"
1721856,2017-10-17 16:06:13 UTC,"There is a wiki page available that has some information on bisecting:
https://wiki.ubuntu.com/Kernel/KernelBisection"
1721856,2017-10-18 16:59:26 UTC,"The only .deb package you need to install is:
linux-image-4.12.0-041200-generic_4.12.0-041200.201710171537_amd64.deb"
1721856,2017-10-19 12:35:27 UTC,"> The only .deb package you need to install is:
linux-image-4.12.0-041200-generic_4.12.0-041200.201710171537_amd64.deb
"
1721856,2017-10-21 01:02:58 UTC," 1849f800fba32cd5a0b647f824f11426b85310d8 is good, i.e. doesn't have the bug."
1721856,2017-10-23 14:06:57 UTC,The issue is fixed with the first 17.10 kernel 4.13.0-16-generic as expected.
1721856,2017-10-23 15:32:28 UTC,"I built the next test kernel, up to the following commit:
cbcd4f08aa637b74f575268770da86a00fabde6d"
1721856,2017-10-23 18:53:28 UTC,cbcd4f08aa637b74f575268770da86a00fabde6d is good. Thanks for the kernels.
1721856,2017-10-24 15:11:10 UTC,"I built the next test kernel, up to the following commit:
1b044f1cfc65a7d90b209dfabd57e16d98b58c5b"
1721856,2017-10-24 16:12:01 UTC, 1b044f1cfc65a7d90b209dfabd57e16d98b58c5b is good.
1721856,2017-10-24 18:43:48 UTC,"I built the next test kernel, up to the following commit:
892ad5acca0b2ddb514fae63fa4686bf726d2471"
1721856,2017-10-18 09:02:01 UTC,"> The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1721856
"
1721869,2017-10-06 20:38:23 UTC,I've seen the same issues when running hardware testing. I also noticed that DNS entries for that IP address were not available. Did you see the same issues?
1721869,2019-09-19 14:49:24 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1721881,2017-12-20 04:27:24 UTC,https://github.com/mixxxdj/mixxx/pull/1428
1721881,2017-10-08 21:44:32 UTC,"> Would it make sense to ignore *rolling* beatloops that are shorter than -let's say 1 beat or ignore them generally? Manually set and normal loops by any size would still saved, of course.
"
1721881,2017-10-08 21:42:12 UTC,"It looks like the underlying issue is that Mixxx only knows a single loop per track.
Mabe this can be solved along with a new CUE editing GUI like proposed here:
https://bugs.launchpad.net/mixxx/+bug/1367171"
1721881,2017-10-08 21:53:20 UTC,"> It looks like the underlying issue is that Mixxx only knows a single loop per track.
"
1721885,2017-10-07 08:13:18 UTC,Thanks for reporting.
1721891,2017-11-20 13:04:02 UTC,"Hi,"
1721893,2018-12-11 00:00:11 UTC,This bug was fixed in the package libgnomekbd - 3.26.0-3ubuntu0.18.04.1
1721893,2018-12-10 23:59:52 UTC,"The verification of the Stable Release Update for libgnomekbd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1721893,2018-12-10 23:59:48 UTC,This bug was fixed in the package libgnomekbd - 3.26.0-3ubuntu0.18.10.1
1721893,2018-12-07 12:19:58 UTC,"Using 3.26.0-3ubuntu0.18.10.1 the command from the testcase shows the layout without segfault, also trying with the IPA ibus method works now, marking as verified for cosmic"
1721893,2018-12-07 12:59:15 UTC,3.26.0-3ubuntu0.18.04.1 resolves the segfault/shows the correct keymap as well
1721893,2018-11-27 16:56:05 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1721893,2018-11-24 07:53:50 UTC,This bug was fixed in the package libgnomekbd - 3.26.0-4
1721893,2018-11-23 10:09:26 UTC,"(the fix has been uploaded in Debian, which means disco is going to be fixed once autosyncs from Debian are turned back on)"
1721893,2018-01-26 09:13:53 UTC,The error seems like https://bugzilla.gnome.org/show_bug.cgi?id=780151
1721893,2018-01-26 09:11:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721893,2018-11-27 20:39:38 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1721896,2017-10-06 23:44:48 UTC,https://bugs.launchpad.net/ubuntu/+source/linphone/+bug/1721896/+activity
1721896,2017-10-07 18:18:57 UTC,Actually I found the solution. It seems like the black screen and the crashing are two different issues. The black screen seems to only when I debug suspend. The crashing after resume seems to be from another issue other than the GPU.
1721903,2017-10-07 01:18:02 UTC,Removing the above nvidia package immediately resolves the issue and I am able to login to a graphic session as normal.
1721903,2017-10-07 04:22:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1721903,2018-01-27 14:36:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721903,2018-06-04 14:07:37 UTC,GeForce GTX 750 Ti
1721904,2018-03-10 05:05:27 UTC,"I'm experiencing this too, although I've never used French."
1721904,2018-03-10 05:10:13 UTC,"Workaround: open the package contents (right click the .app in Finder), then go to Contents/Resources/locale, rename the ""fr"" folder to something else and rename ""en_GB"" (or your preferred language) to ""fr""."
1721909,2019-05-20 22:23:47 UTC,I have found a code for Goodix fingerprint sensor. That code is mainly written for Android devices. I have tried to compile it for Ubuntu 19.04. This code would be helpful to write a new driver. This code is written for the SPI interface. It would be useful if someone can try to rewrite this code for the USB interface.
1721909,2019-05-20 22:22:10 UTC,I have found a code for Goodix fingerprint sensor. That code is mainly written for Android devices. I have tried to compile it for Ubuntu 19.04. This code would be helpful to write a new driver.
1721909,2019-04-22 07:32:15 UTC,USB Utilities. These hypothetical units won't measure satisfaction
1721909,2019-04-22 05:56:40 UTC,"@raphaelbs, I think most of the jobs to be done to fully bring up the device should fall on libfprint as pointed out in #41. If you only want it to be listed correctly, then a new usbutils release is expected."
1721909,2019-04-19 17:21:04 UTC,@vicamo what can we do to help figure this thing out? We have a ton of Dells with this sensor in our company running Ubuntu and could really benefit from this fingerprint reader.
1721909,2019-02-03 20:35:13 UTC,Likewise: Dell Inspiron 17 7000 2-in-1
1721909,2019-04-18 14:30:08 UTC,Same issue with Dell G5 5587
1721909,2019-04-17 19:08:11 UTC,"I have the same bug on my new laptop, a Teclast F6:"
1721909,2019-04-15 08:56:19 UTC,Some more info and some experimental tools can be found in lifprint issue tracker: https://gitlab.freedesktop.org/libfprint/libfprint/issues?scope=all&utf8=%E2%9C%93&state=opened&search=27c6
1721909,2019-06-08 15:39:57 UTC,Also an issue on Samsung Notebook 9 Pro / NP950SBE-K01US.
1721909,2019-02-01 18:19:07 UTC,"Wow, lots of different devices have started shipping the same fingerprint scanner since I first raised this issue."
1721909,2019-02-01 15:23:37 UTC,"Please please please, pretty please xD"
1721909,2019-04-19 04:40:43 UTC,"This is not a kernel bug. `lsusb` from usbutils package (bionic/cosmic/disco) only read name strings from usb.ids [1] files. Upstream has merged a PR [2] to fallback to kernel sysfs attributes, and with that the names will be correctly shown."
1721909,2019-06-08 19:08:41 UTC,Thank you for the information.
1721909,2019-08-09 08:10:20 UTC,i feel terrible for you
1721909,2019-08-03 06:57:58 UTC,"Don't, it's a lost cause. I have been tracking this bug for 1.5 years now :)"
1721909,2019-08-03 07:06:44 UTC,Lol same.
1721909,2019-08-08 21:40:55 UTC,"lol, how do you think I feel? I started the bug report!"
1721909,2019-08-21 13:22:38 UTC,I have the same issue on my Dell Vostro 5581.
1721909,2019-10-15 08:49:49 UTC,"I have the same issue on my Dell Inspiron 7577
OS: Ubuntu 18.04 bionic
Kernel: 5.3.6-050306-generic #201910111731 SMP Fri Oct 11 17:34:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1721909,2019-10-17 07:48:25 UTC,Good News
1721909,2019-10-20 09:41:52 UTC,"As a usbutils bug this can be closed IMHO, the changes mentioned in #44 landed upstream and usb.ids has also been updated for better strings: https://usb-ids.gowdy.us/read/UD/27c6"
1721909,2020-03-17 06:44:30 UTC,working? or just showing the correct name in lsusb? I don't see this device loading any module in kernel to recognize and use it...
1721909,2020-04-06 02:57:38 UTC,"so it works in 19.10? crap, i just had to roll back from 19.10 to 18.04 to run ROS2"
1721909,2020-04-06 14:53:03 UTC,"I think this should not be closed.
I have :
Bus 001 Device 003: ID 27c6:538c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader
in my lsusb output, but there is no driver loaded and thus fprintd cannot be setup."
1721909,2020-04-24 20:45:03 UTC,Kubuntu 20.04 recognizes the fingerprint scanner in lsusb but not much else can be done about it
1721909,2020-05-02 13:16:26 UTC,"same here on my avita liber
Operating System: Manjaro Linux
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2
Kernel Version: 5.4.35-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM"
1721909,2020-07-30 16:52:56 UTC,try the 5.4.x or 5.6.x oem kernel (I'm running Ubuntu 20.04 LTS).
1721909,2019-02-01 14:26:40 UTC,"Same for me:
ASUS UX370UA
Linux 18.10
Kernel 4.20"
1721909,2019-08-02 17:20:32 UTC,Happens for me on new Dell Inspiron running Bionic. Hope to see some traction on this soon.
1721909,2019-01-23 17:33:12 UTC,"Please, fix the bug of fingerprint goodix
Linux 18.04.1 LTS
Kernel 4.20"
1721909,2020-05-17 16:13:10 UTC,"Goodix fingerprint device not recognized on HUAWEI Metbook D, with Ubuntu 20.04:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 0408:1020 Quanta Computer, Inc. hm1091_techfront
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"
1721909,2019-01-15 20:21:29 UTC,"Yup or install Windows 10 then clean it with a script. It's not that bad
really."
1721909,2018-06-08 08:25:33 UTC,"I confirm this bug on my Dell Inspiron 15 7577 laptop with Ubuntu 16.04 LTS.
I can spend some money or time for solving this bug :-)"
1721909,2018-05-10 13:03:20 UTC,Confirmed on bionic beaver release. Inspiron 7577
1721909,2018-04-21 15:23:12 UTC,Confirmed on bionic beaver final beta release. Inspiron 5370.
1721909,2018-04-06 19:41:31 UTC,I confirm this bug on freshly installed from scratch ubuntu 16.04 with all updates on Dell Inspiron 5570 (0810). The device description obtained the same way as in #3 matches the posted output in #3 at http://paste.ubuntu.com/26019993/
1721909,2018-03-24 11:22:40 UTC,I confirm bug at 16.04 on Dell Inspiron 15 7577 hardware.
1721909,2018-03-13 18:19:56 UTC,I confirm the bug at 17.10
1721909,2018-08-05 17:31:53 UTC,I confirm this bug on a Dell G3 15 with Ubuntu 18.04
1721909,2018-03-08 18:36:32 UTC,Changed the title because this is an issue with the kernel and not a specific machine as confirmed by vmz1net.
1721909,2018-02-25 12:29:17 UTC,"I found drivers for GF3208 on Android
Maybe that can help
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937/tree/cm-13.0/drivers/fingerprint/goodix"
1721909,2018-02-13 15:20:41 UTC,Is there anything we can do to help diagnose and fix this issue? I'm willing to do anything to get this to work. Even if it's sparing some coffee money!
1721909,2018-01-21 18:22:00 UTC,"Same here on Dell Inspiron 17 5770, running 17.10."
1721909,2017-10-13 22:46:45 UTC,"Thought I'd share my dmesg, which seems like the Goodix is being picked up - but isn't usable by anything (lsusb is still showing blank however):"
1721909,2017-11-25 12:55:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721909,2017-11-22 13:39:19 UTC,Here is the output of:
1721909,2018-03-08 18:10:56 UTC,"The same problem on my Dell Vostro 5471, 16.04
Fingerprint doesn't work, which is very disappointing."
1721909,2018-08-07 18:05:57 UTC,I confirm this bug on a Asus UX331UAL with Ubuntu 18.04.1
1721909,2019-01-16 13:15:31 UTC,Install Windows only to make a fingerprint scanner work? I beg to differ.
1721909,2018-08-23 09:45:29 UTC,I confirm this bug on a Dell Vostro 5471 14' with Ubuntu 16.04 and kernel 4.15.0-32-generic.
1721909,2019-01-15 18:17:39 UTC,"As it turns out, one could also live without it."
1721909,2018-08-20 13:47:21 UTC,Confirmed on Asus UX331UN with Ubuntu 18.04.
1721909,2018-11-16 20:44:37 UTC,Dell XPS 15 9570 (2018) Same issue:
1721909,2018-11-10 14:52:07 UTC,I have the same problem on a new Dell G3 3579 on Ubuntu 18.04.1 LTS.
1721909,2018-10-27 23:37:46 UTC,Same here with Dell XPS 9570 on Ubuntu 18.10:
1721909,2018-10-21 22:52:04 UTC,Same problem here on a brand new Dell G5 5587...
1721909,2018-10-21 14:51:17 UTC,I confirm this bug on a Asus ZenBook UX331UA with Ubuntu 18.10
1721909,2019-01-15 17:58:42 UTC,Same problem on Dell Inspiron 15 7000 2-in-1 (CPU i7-8565U)
1721909,2018-10-19 20:01:27 UTC,"Confirmed on Dell G3 3579, Ubuntu 18.10
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic
$ uname -a
Linux masked 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 27c6:5301
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 0bda:568a Realtek Semiconductor Corp.
Bus 001 Device 005: ID 8087:0aaa Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"
1721909,2018-10-19 17:01:08 UTC,Confirmed on Dell Inspiron 15 5570 with Ubuntu 18.04.1
1721909,2018-10-17 05:00:55 UTC,Confirmed on Ubuntu cosmic catlefish (beta) Dell G3 3779
1721909,2018-10-02 17:44:01 UTC,Confirmed on Ubuntu Budgie 18.10 Beta with linux kernel 4.18.0-8-generic running on Dell Inspiron 15 7577
1721909,2018-09-05 08:08:08 UTC,I confirm this bug on Dell G3 15 with Kubuntu 18.04.1 and kernel 4.15.0-33-generic.
1721909,2018-09-13 09:35:28 UTC,"Confirmed on Dell Inspiron 5570 with Ubuntu 18.04.1. (And with Arch, it's not distro-specific)"
1721909,2018-10-20 18:45:27 UTC,"Same problem on Dell Inspiron 7577 with Ubuntu 18.10
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic
$ uname -a
Linux Dell7577Linux 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 27c6:5301
Bus 001 Device 005: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 042: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset]
Bus 001 Device 041: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 007: ID 0bda:5652 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"
1721912,2020-09-18 13:29:32 UTC,"Sorry, I guess that's pretty much stale, going to close this."
1721912,2017-10-16 16:04:43 UTC,"I tried in Ocata, same issue as Logan."
1721912,2017-10-16 15:32:37 UTC,"I used the same playbook as jimmy, with the exception that I added gather_facts: yes.
Same result, no issue."
1721912,2017-10-13 06:02:23 UTC,I haven't been able to reproduce this. It seems to be working as expected after testing on an AIO.
1721912,2017-10-07 04:34:58 UTC,"The facts seem to be stored in the host ""{{ item }}"" ... see the cache:"
1721912,2017-10-16 15:35:07 UTC,I was seeing it on Ocata. I wonder if we're missing a necessary backport. Let me do some more testing on various branches and see if I can get a useful repro instruction together :)
1721914,2017-12-10 00:37:47 UTC,"Thanks, I'll check it out."
1721914,2018-03-12 22:23:45 UTC,I can confirm it’s fixed in Ubuntu 18.04
1721914,2018-02-17 07:17:32 UTC,"Oups. Yes it's ok.
Thanks"
1721914,2018-02-17 01:26:20 UTC,Just fix it OK?
1721914,2018-01-28 15:52:39 UTC,i am affected as well on Xubuntu 17.10. Although it installed fine... later I got it on my menu fully working.
1721914,2017-12-09 23:54:30 UTC,"I don't think this is caused by any previous install, I saw this on a 100% clean install of lubuntu 17.10 when I tried to install kodi"
1721914,2017-10-07 06:29:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721914,2017-12-07 16:01:07 UTC,"A prior installation was not properly uninstalled when the Ubuntu system was re-installed / recovered / rescued, etc."
1721914,2017-11-01 02:41:34 UTC,"I am having the same issue. If you need details from me, let me know."
1721914,2017-10-16 12:02:57 UTC,"For the record, both files are the same, so forcing the update won't brake anything."
1721914,2017-10-12 16:57:20 UTC,"As mentioned in the error message, the underlying bug is that the file usr/share/kodi/addons/repository.xbmc.org/addon.xml is present in both kodi-data (https://packages.ubuntu.com/artful/all/kodi-data/filelist) and kodi-repository-kodi (https://packages.ubuntu.com/artful/all/kodi-repository-kodi/filelist), so it fails when attempting to install both packages at once."
1721914,2017-10-10 07:11:18 UTC,"This problem also happened to me.
Solved with sudo apt full-upgrade"
1721914,2017-10-10 00:41:03 UTC,"Yes, it ""fixed"" the state of packages by overwriting a file from one package with a file from another package. That's just removing the symptom, not fixing the issue."
1721914,2017-10-09 23:47:40 UTC,sudo apt install -f -y fixed this issue for me.
1721914,2017-12-07 18:08:26 UTC,Thanks.
1721925,2020-07-01 22:08:54 UTC,"It appears from the log that the error actually occurs prior to apache, due to some interdependency between plymouth and urandom.  I think this is a dupe of plymouth bug 1646731"
1721929,2017-10-07 09:01:48 UTC,"Yes, that schould be easy to implement.
Do you have fun to look into it yourselves?
If yes, I can give you some hints."
1721929,2017-10-07 09:23:07 UTC,Yea I could take a stab. No promises on a timeline though.
1721929,2017-10-07 16:13:25 UTC,"We have void SetlogFeature::slotJoinWithPrevious() to join an old history with the current
The inner loop setting the played flag is at setlogfeature.cpp:214"
1721933,2018-04-12 10:02:00 UTC,"I have just checked and the substition is case-sensitive. If it works differently for you, please provide an example file, so I can investigate the problem further."
1721933,2018-04-10 17:24:38 UTC,"Should be case sensetive substitution.
1M to 1Meg and 1m to 1M"
1721933,2018-04-10 16:33:41 UTC,I mean about 1Meg doesnt changed and stay 1Meg
1721933,2017-11-04 06:21:27 UTC,"Additional:
if used standart prefixes the substitution doesn't appear."
1721933,2018-04-10 07:51:49 UTC,"Could you elaborate on ""if used standart prefixes the substitution doesn't appear""? Is it about changing 1M to 1Meg, etc?"
1721933,2018-04-10 16:47:37 UTC,"This is correct. 1M in Spice notation is 1 milliohm, which might be confusing. Therefore the substition changes 1M (which is a standard schematic notation) to 1Meg in the Spice netlist. This way 1M is treated as 1 megaohm and not 1 milliohm, which would be the case without the substitution."
1721936,2017-10-28 19:30:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721946,2017-10-13 08:30:59 UTC,"When you re-opened passwordsafe to do your import, did you open the test database again, or did you start over with a new database?"
1721946,2017-10-17 21:36:59 UTC,I opened the test database again.
1721946,2017-10-17 22:05:25 UTC,"So, for the password history settings - it turns that while they're implemented at the per-entry level, the global settings for password history (on the options tab) are not implemented.  They're on the form, but it's not connected to anything in the code (there's a comment in the code with TODO)."
1721952,2017-10-11 15:51:46 UTC,"On Sat, Oct 07, 2017 at 12:09:25PM -0000, Joan Moreau via Qemu-devel wrote:

> WHen running a QEMU guest (Windows7) on a linux x86-64 server, the network stops working after some time for any version above 2.5.1.1
>
> In 2.5.1.1, all is fine (no issue with network)
> Any version ablve (trying 2.10.1 now), the application in windows stops accessing the internet after a while
>
> THis is my starting line:
> /usr/bin/qemu-system-x86_64 -machine pc-i440fx-1.7,accel=kvm -usb -usbdevice tablet -usbdevice keyboard -enable-kvm -cpu core2duo -smp 2 -drive file=winpro.qcow,index=0,media=disk,format=qco
> w2 -m 4096 -vga vmware -vnc :3 -k en-us -device e1000,netdev=nic1 -netdev user,id=nic1,smb=/data/vps/files/,hostfwd=tcp::10053-:10053,hostfwd=tcp::3387-:3389 -rtc base=utc,clock=host -daemon
> ize
>
> Thisis my configure line:
> ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-kvm --disable-gtk --disable-xen --disable-user --enable-vnc-sasl --disable-libusb --disable-debug-info --disable-spi
> ce --enable-lzo --enable-pie --disable-werror --enable-linux-aio --enable-vhost-net --disable-tcmalloc --enable-vde --enable-nettle --disable-smartcard --enable-curl
"
1721952,2020-11-26 04:17:19 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1721954,2017-10-14 20:57:55 UTC,"thx for the report.
Fixed in 4ppa57"
1721954,2020-04-17 01:25:40 UTC,This bug still exists. I did a completely new install of Ubuntu 18.04 LTS still after installing boot-repair from your source repo this error is occuring. Please look into it. Attached is a screenshot of the device I am using and below it is the occurence of this error.
1721954,2020-05-12 06:50:48 UTC,ran into similar problem today:
1721955,2019-03-29 16:51:17 UTC,Still a problem for Ubuntu MATE 19.04 beta2.
1721955,2019-04-07 16:17:09 UTC,"Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected."
1721955,2018-04-26 07:39:54 UTC,Dear Tina!
1721955,2018-04-26 05:48:17 UTC,"My hunch is that this has to do with how the Human themes have theme definitions for GTK2 but not GTK3—other themes like this seem to be having similar problems, now."
1721955,2018-04-21 23:44:52 UTC,This bug boggles my mind. Looking at the human-theme Launchpad code page https://code.launchpad.net/~ubuntu-art-pkg/human-theme/ubuntu it looks like the code for the Human theme packages hasn’t been updated since 2011. Why would it stop working now?! Maybe a bug needs to be filed with GTK?
1721955,2018-04-01 17:06:21 UTC,"18.04 LTS with all updates, bug exists."
1721955,2018-01-03 11:28:16 UTC,"18.04 with all updates, bug is here."
1721955,2017-11-29 18:13:39 UTC,I got this bug on Ubuntu 16.04 LTS MATE while switched to the Compiz in mate-tweak. Human theme is has gray instead of orange.
1721955,2017-10-21 16:54:18 UTC,Bug exists in Ubuntu 17.10 MATE final.
1721955,2018-04-21 23:32:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721955,2017-10-07 13:10:17 UTC,Correct colors of Human-Clearlooks theme in Xenial MATE are shown on screenshot.
1721955,2017-10-07 12:55:06 UTC,You can see grey/silver window title in Human and Human-Clearlooks themes in attached screenshot.
1721958,2020-06-15 18:39:11 UTC,"Thank you, Mas Drajat, for taking the time to file a bug report.  Hopefully you've identified a way to solve this on your own.  Unfortunately, there really isn't enough detail provided for us to take action."
1721974,2017-10-10 05:46:26 UTC,The Installer has the following passwords based upon the version you are using:
1721975,2018-05-16 14:23:58 UTC,"If you could help update this, it would be really awesome - I appreciate it xiaods!  The code is correct and the doc is out of date."
1721975,2017-10-11 01:47:07 UTC,"The doc here is out of date, and needs to be updated."
1721975,2018-05-15 08:43:23 UTC,"@Pete Birley (portdirect)  which content need update, please give me a hits. i can update it."
1721976,2018-10-25 15:26:50 UTC,Please forward this feature request to the Xfce bug tracker. Thanks.
1721977,2017-10-17 17:36:43 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1721987,2019-02-01 04:26:49 UTC,After reading the Linux audio sub system documentation I discovered /sys/class/sound/hwC0D0 and hda-verb. That will hopefully do the trick.
1721987,2019-02-01 06:01:17 UTC,"Ok, I got it working without needing to recompile the kernel. Make sure that you have the alsa-tools installed on your machine. Running the attached script at runtime will send the necessary verbs to the sound card to enable the right speaker."
1721987,2019-01-16 09:06:02 UTC,I managed to re-create the recurring pattern and clean the code. I submitted a patch to alsa-dev. https://patchwork.kernel.org/patch/10764291/
1721987,2019-01-31 15:21:17 UTC,Would there be by any chance a way to send that magic sequence through the bus using a script or tool from within the terminal?
1721987,2019-02-02 20:03:02 UTC,"Hey, I tried the script solution together with the systemd service file. It works very nicely!"
1721987,2019-01-04 11:06:30 UTC,"Hi there,"
1721987,2019-02-25 09:02:29 UTC,This is my backport of Tomas Espeleta's patch to Linux 4.15.18 (linux-source-4.15.0 / 4.15.0-45.48 available on Ubuntu 18.04.2 LTS)
1721987,2019-06-15 07:15:38 UTC,"Still, the issue with the right speakers persist. I am not proficient in running or compiling scripts or programs in Linux. I am currently running Ubuntu 19.04. The strange thing I noticed is that the power switch toggle [even a soft toggle without fully turning on/off] fixes the right speaker immediately. However, whenever there is loud audio, the right speaker turns off (i don't know if its some channel or stream that turns off)."
1721987,2019-08-09 14:56:00 UTC,"This bug has been forgotten for a while, sorry for that."
1721987,2019-08-09 14:56:45 UTC,"Created attachment 284299
The patch that will be merged for 5.4 kernel"
1721987,2020-11-01 14:35:15 UTC,"I was still having problems with my Lenovo Legion laptop, this is one of the pages where I stopped in and tried everything on it, to no avail. It looks like the specific issue here was fixed, and any other info I found on the internet was not working either."
1721987,2019-02-04 22:24:16 UTC,"It never ceases to amaze me how collectively we manage to overcome these issues. Yes, your wantedby list is a great addition. The left speaker is so loud I hardly noticed the lack of stereo after waking."
1721987,2018-11-14 09:39:48 UTC,"(In reply to jcs from comment #7)

> Here is the magic sequence of CORB commands needed to enable both speakers.
> This is actually part of a much larger sequence that the Windows driver
> does, but through trial and error, this is the minimum required to make both
> speakers work.
"
1721987,2019-01-06 13:10:28 UTC,"I blindly applied the verbs sequence to master's sound/pci/hda/patch_realtek.c, and stereo it's now working perfectly. Not an expert, just a very thankful user ;)
https://github.com/tespeleta/linux/commit/761cca49e9153b7832fa3f887b875e5ad1517892"
1721987,2018-11-02 22:41:15 UTC,Obviously contacting my vendor went nowhere.
1721987,2017-10-10 19:38:00 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1721987,2018-11-12 20:52:05 UTC,"Here is the magic sequence of CORB commands needed to enable both speakers.  This is actually part of a much larger sequence that the Windows driver does, but through trial and error, this is the minimum required to make both speakers work."
1721987,2017-11-02 20:41:23 UTC,It never worked properly as far as I know.  The problem still exists with 4.14-rc7.
1721987,2017-11-07 03:28:46 UTC,"Please try kernel here,
http://people.canonical.com/~khfeng/lp1721987/"
1721987,2017-11-07 08:00:12 UTC,"FWIW, the original connection is 0x17 -> 0x0d -> 0x03. I override it with 0x17 -> 0x0c -> 0x02, which is same as ALC298_FIXUP_SPK_VOLUME. Unfortunately it didn't work for you."
1721987,2017-11-07 16:58:32 UTC,"Created attachment 260537
dmesg"
1721987,2017-11-07 16:59:59 UTC,I've filed an upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=197801
1721987,2017-11-07 05:21:27 UTC,"Hi, I get the same result with that kernel."
1721987,2018-02-25 22:37:19 UTC,"Hello, is this bug assigned to anyone? Never used bug tracker before."
1721987,2018-03-12 05:31:32 UTC,"Bump.
I am one of the aforementioned 'others'. The problem is rather annoying and hasn't been solved as of 4.15."
1721987,2018-05-17 01:21:47 UTC,Did you try the laptop-dmic parameter?
1721987,2018-06-05 06:26:52 UTC,Mee too. I can confirm the problem on 4.16.13-1-ARCH kernel.
1721987,2017-10-07 18:30:09 UTC,This change was made by a bot.
1721987,2018-06-10 07:06:15 UTC,"From the given alsa-info.sh output, there is nothing wrong there.
So it must be some vendor-specific initialization, and only Huawei knows.
Try to contact your vendor."
1721987,2017-11-07 17:02:25 UTC,"Created attachment 260539
alsa-info.sh output"
1721988,2018-07-25 10:06:21 UTC,"Hi Dariusz!
I will see to it in the coming weeks when I upgrade to 18.04. Can you tell me how I can add plymouth:debug to my kernel cmdline and will it destroy my system?"
1721988,2020-03-24 09:53:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721988,2018-12-11 06:58:20 UTC,"With Ubuntu 18.04 LTS or Ubuntu 18.10 and full disk encryption enabled, after I install the nVidia drivers I also receive the blank screen though I can type the passphrase in and it will continue to boot successfully.  What seems odd based on some past comments is adding the ""nomodeset"" parameter for me presents the splash screen as expected even with the nVidia drivers installed.  I've tested this with both the 390 and 415 drivers."
1721988,2018-12-11 06:55:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721988,2018-08-27 10:13:25 UTC,"This is now working splendid on Kubuntu 18.04 LTS, kernel parameter splash works fine with fulldisk encryption and GRUB."
1721988,2018-07-27 14:46:05 UTC,"Hi @dgadomski
Yeah, in a new installed version of Kubuntu 17.10 there is NO problem if the full-disk encryption is not ENABLED, however it also works if you do not install the Nvidia drivers for Kubuntu. This problem occurs when you decide to install Nvidia drivers for Kubuntu (as in my case) and have to set add nosplash for it to show the prompt to write your password before booting the OS."
1721988,2018-07-27 14:17:34 UTC,"Thanks @goingwc, I have managed to reproduce it here so I can use my own plymouth log. Turns out I couldn't get even 18.04 working correctly, because I had integrated GPU enabled in my motherboard settings (i7-6700K with HD 530) despite nvidia being set to ""primary GPU"". I had to disable the integrated one completely."
1721988,2018-07-24 14:51:49 UTC,"Hi,
Could anyone that has it working on 18.04 add plymouth:debug to their kernel cmdline, reboot and share the /var/log/plymouth-debug.log?"
1721988,2018-04-07 10:33:22 UTC,A slightly better workaround is this from the other bug:
1721988,2018-04-28 18:14:36 UTC,"I concur, this is fixed in Ubuntu 18.04, with one exception.  The time it takes to see the prompt to enter the encryption passphrase it considerably longer than when using the open source nouveau driver -- a good 20 seconds compared to just a couple seconds using nouveau."
1721988,2018-04-28 15:29:12 UTC,"I was previously affected by this (albeit with the 340 version) and had to do the workaround. After making a fresh install of the just released Ubuntu 18.04, it seems to no problem. Even with the same encrypted setup as before on the same machine as before, I am now prompted for the passphrase in the splash, and the boot completes as it should. So I would say that either this happens randomly, or it has been fixed in 18.04."
1721988,2018-04-07 10:23:39 UTC,Verified with Kubuntu 17.10 on a Zbook15 G3
1721988,2018-02-02 00:06:11 UTC,"I'm also experiencing this issue on 16.04 LTS with Nvidia-390, kernel 4.13.0-26-generic"
1721988,2018-01-10 00:19:52 UTC,I am also affected by this and have also been booting into recovery then resuming.
1721988,2017-11-09 10:02:27 UTC,This problem exist at least since 16.10 and i'm experience it in 17.04 also.
1721988,2017-10-21 23:33:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1721988,2018-05-03 10:27:00 UTC,"The splash works fine with fulldisk encryption if I do not install any Nvidia drivers, however if I install the latest stable Nvidia driver then this problem will also occurs to me. Changing the GRUB is one way but I find it pretty sad that we are not able to something that ruins the first impression of a OS."
1721988,2017-10-07 18:31:14 UTC,"I've just updated it to nvidia-387 and it still the same problem.
By the way, I've installed ubuntu-gnome-desktop before I did install nvidia drivers."
1721991,2017-10-07 21:29:59 UTC,let's *not* forget...
1721991,2018-04-29 18:40:58 UTC,"Can someone please change the default shebang?
It's annoying cuz my default python interpreter is anaconda3"
1721991,2020-05-09 09:01:45 UTC,"Python 3 is now supported with 1.92:
https://github.com/gnome-terminator/terminator/releases"
1721991,2019-10-03 10:39:49 UTC,"I had the same issue , using
Linux tomasim-desktop 4.18.0-25-generic #26-Ubuntu SMP Mon Jun 24 09:32:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
and terminator.
The issue came after I played with python 2.7 and python3.6 updates.
I switched the default python with
sudo update-alternatives --config python"
1721991,2020-02-04 19:44:09 UTC,Amazed that this is still a thing.  KurtB's suggestion #16 seems like a reasonable workaround for the time being.
1721991,2017-10-07 21:29:40 UTC,... or actually... I honestly don't know how much attention distros pay to the *.spec and debian/rules files shipped in the package. Maybe they do. (But also let's forget about the non-rpm/deb based ones.)
1721991,2019-08-24 18:50:13 UTC,"You can test Python3-version: https://code.launchpad.net/~hellodeargrandma/+archive/ubuntu/ppa
Porting to python3 issue is here: https://bugs.launchpad.net/terminator/+bug/1662544"
1721991,2017-10-07 21:26:47 UTC,There's a suggestion in the stackoverflow thread to install as data files rather than script.
1721991,2019-06-14 13:49:49 UTC,"This just hit me this morning. The quick and dirty hack
to get me back to work was to set the interpreter
on line 1 to:"
1721991,2017-10-07 19:57:18 UTC,"Glazing through the answers and comments in that stackoverflow thread, it seems kinda reasonable for a build system to figure out the location of the interpreter and hardcode it (traditional autoconf/automake does plenty of such things too). The only thing they forget about is if distros offer multiple setups to their users, including each of python2 and python3 being available or not independently from each other, and if both are available, toggling where the /usr/bin/python symlink points to. Their approach fails here big time."
1721991,2017-10-07 19:44:42 UTC,"In the source tree, terminator begins with ""#!/usr/bin/env python2""."
1721991,2017-10-07 19:36:43 UTC,@Egmont Your assumption with `setup.py install` modifying the shebang may be correct: https://stackoverflow.com/a/1530808
1721991,2017-10-07 19:31:34 UTC,"@Stephen Correct, I'm on stretch, but with testing repos (buster) enabled. terminator is installed via the central debian repo:"
1721991,2017-10-07 19:30:37 UTC,Ditto with Fedora Rawhide's package. Neither seems to have any releavnt patch or build step.
1721991,2017-10-07 19:21:54 UTC,/usr/bin/terminator I mean... I'm getting confused by all these terminal emulators :-D
1721991,2017-10-07 19:21:22 UTC,"On Ubuntu Artful beta's termiantor_1.91-1 package, /usr/bin/terminix starts with ""#!/usr/bin/python""."
1721991,2017-10-07 19:19:12 UTC,"It's not an Ubuntu packaging thing. 1.91 should contain the fix (in fact I think 1.90 may even contain it.) I'm taking a stab that you are on stretch (by the deb9u3 in your uname output). I've checked the debian packages, and I see no sign of a patch that would revert the fix in lp:1621156 that Egmont mentions. I can't see how you have a 1.91 version without the python version specced in the shebang line. Did your package come from the central debian repo, or are you trying to use 3rd party packages?"
1721991,2017-10-07 19:02:53 UTC,"@Egmont So it was a Ubuntu packaging issue? I'm using Debian, though."
1721991,2017-10-07 20:36:39 UTC,"All I can say is Ugh! Slightly more confusing is that the setup.py *also* has python2 in the shebang. So doesn't that mean when it runs it uses the python2 binary?... Or is something forcing the setup.py to run with python3? Looks like a solution might be that the setup.py command changes from:
./setup.py install --record=install-files.txt
to:
./setup.py install --record=install-files.txt --executable=""/usr/bin/env python2"""
1721991,2017-10-07 18:37:45 UTC,According to lp:1621156 this should be fixed... isn't it?
1722004,2017-10-09 07:36:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1722004,2017-10-10 02:31:41 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=788751
1722019,2017-10-11 01:49:38 UTC,Alvin;Thanks for the quick reply!! I am attaching the file I tried to load into inkscape. I tried to attach it to my original request. thanks Doc
1722019,2017-10-11 02:35:39 UTC,"thanks for the file. The problem appears to be caused by the fact that the release version is quite old. The file version is given as AC1006 which is AutoCAD Release 10.
    The current dxf import routine was designed to support AutoCAD Release 13 or newer.
To try to improve the format, I loaded this dxf file into QCad 3.15 and then saved it as the attached dxf file. This file loads correctly into Inkscape. (You will need to do some manual scaling to adjust the size.)"
1722019,2017-10-08 11:22:35 UTC,"- could you attach the dxf file?
- also, which version of Inkscape (see Help->About)"
1722022,2017-10-16 16:03:18 UTC,"How did you start this session?
The fourth parameter, defining the train, is completely wrong - it should just be the train and timetable reference, not the file path.
See example below."
1722022,2017-10-20 08:23:26 UTC,"Sorry for the late reply, I have finally had a chance to do some testing."
1722022,2017-10-20 08:24:42 UTC,"Just for completion, I have tested the new timetable and it does load correctly"
1722023,2017-10-10 17:35:47 UTC,I agree that the current behaviour is somewhat confusing.
1722023,2017-10-11 06:24:40 UTC,"Maybe this needs better wording, e.g. ""Which source fetched this"". The intention here is for the user to know which image source fetched the image, so that they can disable it if they don't like it, or add more like it if they like it. There is another way more prominent option ""View at XXXX"" to jump to the webpage the image is hosted on, and there is also the first option in the menu (the one with the image name as label) to open the file itself (and most image viewers from there allow you to open or browse its folder too)."
1722023,2017-10-16 04:21:29 UTC,"The option of ""View at XXXX"" does not work for all sources, when comming from the website flickr it work, but not when the image comes from Unsplash.com this is demonstrated in the two attached screenshots"
1722023,2017-10-16 04:23:20 UTC,"I could not add multiple screenshots so here is the one showing unsplash. It shows the file path, but since it comes from a website you would expect to have Variety bring you to the website page."
1722024,2020-01-24 10:01:52 UTC,Looks like the crash was fixed before 18.04.
1722024,2017-10-08 05:02:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722024,2017-10-08 04:57:55 UTC,"StacktraceTop:
 XSync (dpy=0x55794d7678a0, discard=discard@entry=0) at ../../src/Sync.c:44
 gdk_x11_display_error_trap_pop_internal (display=0x55794d775060, need_code=<optimized out>) at ././gdk/x11/gdkdisplay-x11.c:2699
 gdk_error_trap_pop_internal (need_code=1) at ././gdk/gdkdisplay.c:2345
 update_pixmap (self=0x55794fd93430) at compositor/meta-surface-actor-x11.c:157
 meta_surface_actor_x11_pre_paint (actor=<optimized out>) at compositor/meta-surface-actor-x11.c:237"
1722024,2017-10-09 02:48:04 UTC,"Tracking also in:
https://errors.ubuntu.com/problem/1594ffaee6b7d61f44507d96e5894fff66560a41"
1722027,2018-12-28 07:06:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722038,2018-01-08 15:07:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722039,2017-10-10 13:28:22 UTC,what is the newest kernel you can't reproduce the problem with? (you can use the kernel mainline PPA if you want to help testing)
1722039,2017-11-26 00:51:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722039,2017-10-12 10:41:40 UTC,"I found an alternate implementation of prime-select, and modified it slightly. With it, if I switch to intel mode , then reboot I manage to login with the integrated graphics getting used as expected."
1722039,2017-10-12 08:05:04 UTC,"Looks like libGLX is only lodable in nvidia mode, some library paths may be missing in the intel prime profile"
1722039,2017-10-12 08:04:27 UTC,list of gl libraries loadable in nvidia mode
1722039,2017-10-12 06:49:41 UTC,"For referece, the bbswitch load log:
[    4.492602] bbswitch: version 0.8
[    4.492606] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[    4.492611] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[    4.492699] bbswitch: detected an Optimus _DSM function
[    4.492708] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on"
1722039,2017-10-12 05:00:17 UTC,Could it be that the mesa GL libraries are incorrectly installed or that some library is not in the search path when redirecting calls?
1722039,2017-10-10 17:41:33 UTC,That kernel boot parameter did not work for me. Also in teh non functional intel mode I am getting fans at maximum even with the recent nvidia drivers. Some GPU switching is really going wrong in intel mode.
1722039,2017-10-10 17:28:22 UTC,Looking at: https://github.com/Bumblebee-Project/bbswitch/issues/140 indicates that this has been broken since 4.8 when new power management code was enabled for PCIE ports. They suggest using pcie_port_pm=off in teh kernel command line. I will try that whenever I can and see where that leaves me.
1722039,2017-10-10 13:58:54 UTC,"None. I cannot even try 4.14 because of some GPL symbol issue which results in the DKMS build of the nvidia driver to fail. As of now, the latest kernel series that support teh binary driver is 4.13."
1722039,2017-10-10 12:31:52 UTC,I have seen it happen with both the 4.13.4  kernel currently in artful-proposed as well as the 4.13.5 upstream kernel. I am currently on the upstream kernel since 4.13.4 has an annoying shutdown hang and 4.13.5 does not.
1722039,2017-10-12 08:04:01 UTC,list of gl libraries loadable in intel mode
1722039,2017-10-10 11:29:57 UTC,With nvidia-375 from the PPA I get the same issue + the fans at max issue as with nvidia-381.
1722039,2017-10-08 08:39:51 UTC,"Until nvidia pushed a new driver version supporting that feature, the workaround is to login on a xorg session instaed of the default wayland one."
1722039,2017-10-10 12:03:03 UTC,It could be a kernel issue. I have seen other systems not playing well with bbswitch disabling the dGPU. I'll see if I can reproduce the problem here.
1722039,2017-10-08 13:39:24 UTC,I am using X11 throughout. Wayland has not been used anywhere.
1722039,2017-10-10 10:05:45 UTC,Output when running prime-select:
1722039,2017-10-10 10:50:08 UTC,Is a version of 375 that supports 1050Ti available in the repos (ubuntu or graphics PPA)?
1722039,2017-10-10 10:29:34 UTC,"Can you reproduce the problem on the same exact system (kernel, etc.) when using the 375 driver?"
1722039,2017-10-10 10:52:26 UTC,The version of nvidia-375 I am seeing points to nvidia-384. So I cannot install nvidia-375 without breaking my system (i.e. using a .run file that wouldn't work with nvidia-prime anyways)
1722039,2017-10-10 10:55:58 UTC,Coming to think of it I have not tried nvidia 381. Should I?
1722039,2017-10-10 11:06:38 UTC,"You can remove nvidia-384 and the transitional packages for nvidia-385, then you can download 375 from the following PPA, and install the deb packages manually:
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa"
1722039,2017-10-10 11:13:03 UTC,nvidia-381 drove both my fans to max :/
1722039,2017-10-10 11:15:45 UTC,I have used force version in synaptic to use the PPA version of the packages.
1722039,2017-10-08 08:36:48 UTC,there is no wayland session for optimus devices in 17.10
1722059,2017-11-20 12:17:55 UTC,"Hi,
The error 5012 corresponds to the communication error. Can you try removing the printer, uninstall and install to check for the printer connectivity?
You can download the latest hplip driver version from : https://developers.hp.com/hp-linux-imaging-and-printing/gethplip"
1722060,2018-03-20 02:49:27 UTC,This also affects the 1.0 release of Flare (www.flarerpg.org) when compiled from source. I ran into this a couple of days ago.
1722060,2018-05-22 16:43:52 UTC,Do you confirm this is the same bug as https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1772471 ?
1722060,2018-03-26 15:53:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722060,2018-01-28 19:00:41 UTC,">I'd hesitate to call it a solution. It's a workaround at best.
"
1722060,2018-01-07 13:13:38 UTC,Quin: Is it able to detect the SDL version during runtime? Do you have a link to the upstream patch or bug report? Sounds like it might be a relevant solution for other programs too.
1722060,2018-01-09 05:13:17 UTC,"> Sounds like it might be a relevant solution for other programs too.
"
1722060,2017-10-08 18:08:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722060,2017-12-10 15:12:37 UTC,"Attaching a Debian bug watch. The bug report unfortunately has a couple of spam messages, but in shows that Debian was affected too and the issue was resolved by upgrading to sdl 2.0.7. This confirms what has also been described in bug 1720819 where other systems (for instance Arch) upgraded the sdl version."
1722060,2018-01-09 06:13:23 UTC,"I wholeheartedly agree that libsdl2 should be updated, but from the standpoint of an individual project it is bad publicity to have your program crash on startup (and why we're all kind of mad that SDL did this rewrite for a minor patch release). People often don't investigate or understand that it isn't the fault of the project, but an underlying library they know nothing about."
1722060,2018-01-08 05:12:36 UTC,Hans: https://github.com/red-eclipse/base/commit/70c19e9cf25b9e3aae9e97d391cecb8e8d24b52c
1722060,2018-01-03 06:36:44 UTC,Red Eclipse is not affected by this bug as of v1.6.0 as we've added a check for SDL v2.0.6 and disable sound output if it is detected.
1722061,2017-12-05 20:37:54 UTC,"This patch solved it for me (on wicd-curses, but the workaround in the gtk client should be similar). This might not be the best way to solve it, but it does work around the problem for now."
1722073,2020-06-05 15:50:05 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1722073,2020-08-05 04:17:40 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1722074,2018-05-23 21:16:30 UTC,"Also reproducible
$ qemu-system-x86_64 --version
QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.2)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
$ uname -a
Linux ryzen 4.16.11-041611-generic #201805221331 SMP Tue May 22 17:34:25 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ head -28 /proc/cpuinfo
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 23
model		: 8
model name	: AMD Ryzen 7 2700X Eight-Core Processor
stepping	: 2
microcode	: 0x8008204
cpu MHz		: 2161.008
cache size	: 512 KB
physical id	: 0
siblings	: 16
core id		: 0
cpu cores	: 8
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca
bugs		: sysret_ss_attrs null_seg spectre_v1 spectre_v2 spec_store_bypass
bogomips	: 7399.25
TLB size	: 2560 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 43 bits physical, 48 bits virtual
power management: ts ttp tm hwpstate eff_freq_ro [13] [14]"
1722074,2018-05-24 05:13:12 UTC,"Hi,
this is not a show stopper at all.
It is just a warning and it is fine.
It is a trade-off between the ""ease to use nested virt"" vs ""this warning"".
For example on an intel chip you'd get:
  qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm
And that as well is no issue."
1722074,2018-05-24 05:17:16 UTC,"And sorry for the status update noise, one can clearly see that I start to fail once I have to use my mouse :-)"
1722074,2019-06-15 04:17:28 UTC,How is this a bug?
1722074,2019-06-17 05:43:38 UTC,"Hi,
Ken - I think all I said in comment #2 still applies (and likely won't change)."
1722076,2017-10-08 16:23:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1722076,2017-10-09 00:26:44 UTC,"The actual issue appears to be in fonts-dejavu-extra, but it won't let me select that."
1722085,2017-11-15 18:00:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722090,2019-09-19 14:49:26 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1722096,2019-06-24 04:44:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722098,2017-11-29 11:45:42 UTC,"Hi,"
1722098,2017-11-04 10:14:46 UTC,"Hi Bernd,"
1722101,2018-03-14 16:51:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722104,2019-04-15 14:36:49 UTC,"Cannot reproduce that, it's probably too late now, but for the future, please attach full solver log with POLDEK_TRACE=1 env, like:"
1722113,2017-10-08 22:55:23 UTC,"Does our d-i path really do this? I thought it didn't but can't really
remember."
1722113,2017-10-24 04:06:43 UTC,"The only check d-i seems to perform is objecting to a password of less than 8 characters, it's totally happy with a password of '12345678'. Suspect ubiquity is a better inspiration. Would also like to talk to someone about how to design this."
1722113,2018-02-22 01:20:55 UTC,"FWIW, the code ubiquity uses is here: https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/ubiquity/validation.py#L87"
1722113,2018-02-22 01:21:18 UTC,"Given the amount of people who commented on this, we should probably do something about it!"
1722114,2018-08-22 20:02:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722118,2017-10-09 07:23:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1722118,2017-10-11 18:20:38 UTC,I reported the issue on GNOME Bugzilla:
1722118,2018-08-14 09:19:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722121,2017-10-09 13:15:21 UTC,Related to bug 1708306.
1722121,2017-11-01 22:08:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722121,2017-10-31 23:54:23 UTC,"On ""Ubuntu"", xeyes follows the mouse movement when over the desktop. On ""GNOME"" it doesn't."
1722121,2017-10-31 23:44:44 UTC,"Correctly working windows are native Wayland. Faulty windows are X11 (XWayland), you can tell by e.g. xeyes following the mouse movement."
1722121,2017-11-01 22:08:12 UTC,With the help of main gnome-terminal developer Christian (thanks!) we've noticed the following:
1722121,2017-10-31 22:34:56 UTC,"Pressing the global shortcut Ctrl+Alt+T, or pressing the Super key and typing Terminal, or launching from the left Launcher once it's been added as a favorite all launch via /usr/bin/gnome-terminal and result in a good one."
1722121,2017-10-31 22:25:56 UTC,"I can confirm this with Ubuntu's packages, as well as manually compiled VTE + gnome-terminal from git master (and hence no Ubuntu patches, no wrapper startup script)."
1722121,2017-10-31 18:17:23 UTC,"I should add that mine wasn't a fresh install of Ubuntu 17.10, but rather an upgrade from 17.04 (do-release-upgrade)."
1722121,2017-10-31 18:16:21 UTC,"I'm seeing this issue as well. I can also confirm that copying doesn't work when Terminal is opened by right-clicking the desktop and selecting Open Terminal, but DOES work when I've opened it by other means."
1722121,2017-10-31 18:08:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722121,2017-10-31 22:44:56 UTC,"Re-enabling DND (git revert 10e164d8) pretty much always causes a sudden crash as soon as I try to drag out a tab, it's impossible to test that."
1722141,2017-10-12 02:37:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511376"
1722157,2017-10-09 06:04:21 UTC,"oops, and the second line should end with ""; \"""
1722168,2017-10-19 15:05:33 UTC,That's still an issue on 17.10
1722176,2017-10-19 15:09:59 UTC,"That's still an issue, not a big deal but gives a lack of polish feeling :-/"
1722176,2017-11-13 11:51:38 UTC,This is what I did to reproduce the bug:
1722180,2017-10-11 20:34:16 UTC,"Hi Gordon,"
1722180,2017-10-11 21:15:47 UTC,"On further reflection we will need to differentiate between
* auto-created groups via web services / CSV files - should not be able to change shortname
* manually created / copied groups - should be able to change shortname"
1722180,2017-10-22 04:14:05 UTC,"I guess if we want to ensure that groups created via web services are treated differently, that should go for other settings in the group then as well and not just the short name as you can also control other settings."
1722182,2017-11-04 14:20:12 UTC,The issue remains after a complete reinstall.
1722182,2017-11-21 21:00:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722183,2017-12-05 23:00:36 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1722183,2017-12-05 23:00:16 UTC,This bug was fixed in the package gnome-software - 3.26.1-0ubuntu2.17.10.1
1722183,2017-11-17 09:19:30 UTC,"SRU verification for Artful:
I have reproduced the problem with gnome-software 3.26.1-0ubuntu2 in artful and have verified that the version of gnome-software 3.26.1-0ubuntu2.17.10.1 in -proposed fixes the issue."
1722183,2017-11-16 23:10:38 UTC,"Hello Jean-Baptiste, or anyone else affected,"
1722183,2017-10-30 02:24:43 UTC,"That upload didn't fix this problem, still investigating..."
1722183,2017-10-31 02:38:55 UTC,Note the UI didn't support cancelling in Xenial.
1722183,2017-10-31 00:55:36 UTC,Confirmed the bug is in core GNOME Software (i.e. not the snap plugin on snapd-glib).
1722183,2017-10-10 08:49:02 UTC,"Le 10/10/2017 à 05:29, Robert Ancell a écrit :

> Can you confirm if this is a new bug or an existing one?


I'd say 'new' because it cannot be done with the current version due to
another bug (There is an error when you install a second snap and g-s
thinks it is not installed so you cannot cancel)"
1722183,2017-10-10 03:29:18 UTC,Can you confirm if this is a new bug or an existing one?
1722183,2017-11-03 00:51:31 UTC,This bug was fixed in the package gnome-software - 3.26.1-0ubuntu6
1722183,2017-10-26 22:52:41 UTC,This bug was fixed in the package snapd-glib - 1.24-0ubuntu1
1722188,2017-10-09 17:23:05 UTC,"Hello Tejas,"
1722188,2017-10-09 12:12:20 UTC,"Hi Jacek,"
1722188,2017-10-09 17:38:08 UTC,"Hi Jacek,"
1722194,2018-01-27 21:31:00 UTC,"Reviewed:  https://review.openstack.org/535908
Committed: https://git.openstack.org/cgit/openstack/ironic-tempest-plugin/commit/?id=bcdb740e5d40e3dedfc73a1e6fe6b80585621fc2
Submitter: Zuul
Branch:    master"
1722194,2018-01-28 18:43:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538653"
1722194,2018-01-30 00:14:46 UTC,"Reviewed:  https://review.openstack.org/536979
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=c9677cd43ba61e737d91294b94e7ed74c282dca5
Submitter: Zuul
Branch:    master"
1722194,2018-01-30 20:39:01 UTC,"Reviewed:  https://review.openstack.org/537386
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=ccf22acb53f4357047e4e0caa658bf9801d817c4
Submitter: Zuul
Branch:    master"
1722194,2018-01-30 23:46:37 UTC,"Reviewed:  https://review.openstack.org/536980
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=00daa18fc99516b0947d2695c030871acff6d6bd
Submitter: Zuul
Branch:    master"
1722194,2018-01-31 02:26:36 UTC,"Reviewed:  https://review.openstack.org/538653
Committed: https://git.openstack.org/cgit/openstack/ironic-tempest-plugin/commit/?id=c4d1c83c1efa477624faa54a50acdac850c61341
Submitter: Zuul
Branch:    master"
1722194,2018-02-08 18:58:57 UTC,"There is one outstanding item from the spec: Ironic needs to validate that instance_info[‘traits’] is consistent with the list of traits currently associated with Ironic node... """
1722194,2018-02-12 13:55:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543461"
1722194,2018-02-15 20:59:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545118"
1722194,2018-02-16 13:42:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/545297"
1722194,2018-02-19 20:29:42 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/545118
Reason: No longer required - nova has merged the fix to bug 1748942."
1722194,2018-03-10 09:58:48 UTC,"Reviewed:  https://review.openstack.org/545370
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=c8ae2457c7fd86975d77d6bc67b50b155f602944
Submitter: Zuul
Branch:    master"
1722194,2018-03-12 09:56:05 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/551938"
1722194,2018-03-12 14:50:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/552043"
1722194,2018-03-12 16:06:44 UTC,"Reviewed:  https://review.openstack.org/551938
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=6015890adee55582330256bc10e933cba0b84cc9
Submitter: Zuul
Branch:    stable/queens"
1722194,2018-03-12 16:23:36 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/552077"
1722194,2018-03-13 16:35:40 UTC,"Reviewed:  https://review.openstack.org/552077
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=cef19cbf0a4d7b179de5d4448e247e9db1a79831
Submitter: Zuul
Branch:    master"
1722194,2018-03-29 19:20:21 UTC,"Reviewed:  https://review.openstack.org/543461
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=d1cd215c66eaa205bc63a5405835e0ef28dadc20
Submitter: Zuul
Branch:    master"
1722194,2018-04-04 11:23:04 UTC,"Reviewed:  https://review.openstack.org/545297
Committed: https://git.openstack.org/cgit/openstack/ironic-tempest-plugin/commit/?id=56399ccba1fdbff6ded31671af0d8e87175d776f
Submitter: Zuul
Branch:    master"
1722194,2018-02-16 16:00:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/545370"
1722194,2018-04-05 17:43:30 UTC,"Reviewed:  https://review.openstack.org/552043
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=f5605d13e67c71c46538bafa5f7ddc18fb7427a6
Submitter: Zuul
Branch:    master"
1722194,2018-01-25 05:20:26 UTC,"Reviewed:  https://review.openstack.org/536384
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=223e9b1faac157d78fed38ec40ac700803e8cce5
Submitter: Zuul
Branch:    master"
1722194,2018-01-25 03:49:06 UTC,"Reviewed:  https://review.openstack.org/535296
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=c1cce7eb452c228dc2633e80f2c98fd142574fa9
Submitter: Zuul
Branch:    master"
1722194,2018-01-25 05:20:14 UTC,"Reviewed:  https://review.openstack.org/532269
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=864331a94bddfd1860e0db9c6763fbf4f3ab6507
Submitter: Zuul
Branch:    master"
1722194,2017-10-09 14:01:17 UTC,"There is a spec in review for this here:
https://review.openstack.org/#/c/504531"
1722194,2017-11-14 20:31:59 UTC,"Reviewed:  https://review.openstack.org/504531
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=c912844dc5b27e89ee284bc6fe1c7ba074db1db7
Submitter: Zuul
Branch:    master"
1722194,2017-12-15 11:30:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528238"
1722194,2018-01-02 11:53:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530723"
1722194,2018-01-09 17:25:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532268"
1722194,2018-01-09 17:25:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532269"
1722194,2018-01-12 13:31:40 UTC,"Reviewed:  https://review.openstack.org/528238
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=bbff319f0226af11af3c2864ad8f678abef6dcdb
Submitter: Zuul
Branch:    master"
1722194,2018-01-16 16:44:05 UTC,"Reviewed:  https://review.openstack.org/530723
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=88a6761503e9a31ff2b776f4f462d2cf175aa1b0
Submitter: Zuul
Branch:    master"
1722194,2018-01-18 11:17:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535296"
1722194,2018-01-23 21:44:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536979"
1722194,2018-01-19 19:23:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535908"
1722194,2018-01-18 21:09:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535482"
1722194,2018-01-24 20:13:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/537637"
1722194,2018-01-24 13:53:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/537386"
1722194,2018-01-24 11:40:51 UTC,"Reviewed:  https://review.openstack.org/532268
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=2cd7232f142373b0744dd42aaf1e6ce0740a1567
Submitter: Zuul
Branch:    master"
1722194,2018-01-25 02:14:55 UTC,"Reviewed:  https://review.openstack.org/537637
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=d8a291a1e1c84df2f5f164f292c4fa80ed034078
Submitter: Zuul
Branch:    master"
1722194,2018-01-23 21:44:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536980"
1722194,2018-01-23 21:44:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536978"
1722194,2018-01-22 14:36:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536384"
1722194,2018-01-22 12:49:40 UTC,"Reviewed:  https://review.openstack.org/535482
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=c3ed7dfb9e7e878f30fbff68f066a409879b7a3b
Submitter: Zuul
Branch:    master"
1722194,2018-01-24 10:40:56 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/536978
Reason: Rolled into https://review.openstack.org/#/c/532268."
1722207,2017-11-30 01:41:42 UTC,this was fixed in the most recent kernel 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1722207,2017-10-17 22:44:07 UTC,systemd-analyze blame log after having made some adjustments to my kernel command line to support my GCN1.0 AMDGPU video card
1722207,2017-10-17 22:43:27 UTC,critical chain log after having made some adjustments to my kernel command line to support my GCN1.0 AMDGPU video card
1722207,2017-10-17 22:54:46 UTC,"Systemd journal from reboot this morning.
There are some lines mentioning the following that i remember seeing from when i had tried Debian Testing also with the 4.13 kernel (with a similar problem) that showed up in the terminal:"
1722207,2017-10-12 01:23:36 UTC,4.14-rc4 also works well
1722207,2017-10-12 00:36:44 UTC,This bug is in kernel because with kernel 4.10 working perfectly.
1722207,2017-10-09 12:16:35 UTC,Hello and thanks for the bug report!
1722207,2017-10-10 03:50:28 UTC,"Can you cycle through the virtual consoles (using ctrl-alt-f1, ctrl-alt-f7, etc.) when the shutdown process in hung and see if you can gather more information about what systemd unit is timing out? Then it would be best to open a new bug against the corresponding package."
1722207,2017-10-17 18:58:54 UTC,"I have this same bug on my Carrizo AMD A10-8700P.  When I cycle through the terminals on shutdown there is no further information to describe what is going on.  I am running 17.10 based on the October 15, 2017 daily iso.  I have also set my journal as persistent and can't see anything in there that would indicate wat is slowing it down."
1722207,2017-10-09 12:45:44 UTC,"No, I'm not using eCyptfs, by mistake I had selected that option because this was my first bug report.
Thank you for your quick reply."
1722215,2018-03-03 06:54:53 UTC,"I have the same issue on an Asus Q502LA, fresh install of Kubuntu 17.10"
1722215,2017-11-10 02:22:04 UTC,I am getting the same issue. I am on a new install of kubuntu 17.10. Is there a way you managed to resolve this?
1722215,2018-04-02 18:44:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722221,2017-10-09 12:08:35 UTC,Probably https://bugs.mysql.com/bug.php?id=84994 maybe implemented in a way which allow to solve this issue with multi-channel replication setup.
1722221,2018-01-25 09:39:06 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2509
1722222,2017-10-09 12:21:03 UTC,"BTW, it is not a nvidia-graphis-drivers-384 package related. I did remove that but it seems it did not work :-/"
1722222,2018-01-23 13:15:04 UTC,"Workaround is to boot live image, open terminal and install lvm2 via apt-get install. Then start the installer."
1722222,2018-01-23 13:58:33 UTC,"I think you miss-understood me.
How can I install lvm2 if I can't finish the installation?"
1722222,2018-05-02 08:40:24 UTC,How I fixed it was to install lvm2 by jumping to a shell before stating the installation. Then the installation does finish.
1722222,2018-01-01 20:05:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722225,2017-10-09 12:37:37 UTC,"As additional bug, (obviously) the installer does not offer option to encrypt drive, only home directory."
1722225,2017-10-23 17:52:11 UTC,"This works for me. After installing cryptsetup, clicking the encrypted drive in Caja brings up the password dialog and the disk is properly mounted. I never installed Beta 2, but both Beta 1 and the 17.10 final release worked fine here."
1722225,2020-05-22 04:17:31 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1722225,2020-05-22 04:17:32 UTC,[Expired for caja (Ubuntu) because there has been no activity for 60 days.]
1722226,2018-11-21 12:48:01 UTC,This bug was fixed in the package linux-azure - 4.15.0-1032.33
1722226,2018-11-21 12:44:45 UTC,This bug was fixed in the package linux-azure - 4.15.0-1032.33~16.04.1
1722226,2017-10-16 11:15:24 UTC,"@xnox -- the testing trigger required to force kernel installation is an ADT limitation not related specifically to the kernel testing itself.  This is currently how you specify which kernel to test, by triggering it.  It is wrong in the sense you cannot test anything against updates with this model."
1722226,2017-10-13 14:16:45 UTC,"Also see https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1721558 where regression test suite can only ever pass when linux-azure is triggered by linux-meta-azure. In all other cases the system is not upgraded to the expected kernel variant and is not rebooted into said kernel, therefore testing fails."
1722226,2017-10-13 14:15:24 UTC,This is invalid assessment / consensus.
1722226,2018-11-09 12:44:59 UTC,Moving the module to the main image package will cause no impacts and improve test results.
1722229,2017-10-10 04:10:38 UTC,Does this occur on startup or after an operation?
1722229,2017-10-10 08:49:42 UTC,"Le 10/10/2017 à 06:10, Robert Ancell a écrit :

> Does this occur on startup or after an operation?
>


On startup."
1722229,2017-10-10 10:52:41 UTC,Also this message is not displayed without the snap plugin installed.
1722229,2018-03-29 11:23:36 UTC,"This is happening in Ubuntu 18.04 updated as today, but always when searching for updates from ""Updates"" tab, or installing a .deb package."
1722230,2017-10-29 03:35:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722256,2015-06-02 10:14:57 UTC,"The menu bar is part of gnome-shell. The ""?"" you're seeing though means that the connectivity check failed."
1722256,2015-06-02 03:15:42 UTC,"Created attachment 304402
journal for this boot"
1722256,2018-02-01 21:15:11 UTC,Confirming that adding dns=default to  /etc/NetworkManager/NetworkManager.conf solved the problem for me as well - thank you Scorpius!
1722256,2018-02-22 04:02:52 UTC,This was affecting me on 17.10 as well.  Added dns=default did resolve it.  Without that there was no nameserver being set.
1722256,2018-02-22 05:00:14 UTC,"Also tracking in Ubuntu bug:
https://launchpad.net/bugs/1722256"
1722256,2018-11-11 16:47:25 UTC,Same problem here on Ubuntu 18.04. However adding dns=default to the [main] section of /etc/NetworkManager/NetworkManager.conf makes it worse. 1. The question mark shows even if connected 2. DNS does not work anymore.
1722256,2019-04-15 05:51:23 UTC,Could those having the issue add their journalctl log after triggering the bug?
1722256,2019-04-28 15:27:26 UTC,"I recently realized that the problem with the Wi-Fi icon will be resolved by adding a VPN configuration from Network Settings and connecting to it.
After that, the problem will be fixed forever. Even without connecting to the VPN.
Also, after logging off, the problem will not come back.
But restarting and shutting down the system will bring the problem back."
1722256,2019-05-13 07:01:41 UTC,"Questionmark changes back to normal after updating the system through update manager, but it happened to me at least twice, so it was not a fix that solved some connectivity issue, since the update went fine both times."
1722256,2019-07-10 10:14:49 UTC,Is this related ?
1722256,2019-07-11 01:43:07 UTC,"Sounds related, and maybe that's where the bug is. Although it's not an Ubuntu-specific issue..."
1722256,2019-07-11 13:42:02 UTC,"Hi,"
1722256,2019-07-11 13:47:07 UTC,I will gather more info next time I see this.
1722256,2019-07-21 09:58:39 UTC,"I had not seen this issue for a long time. But now I see it again.
Note that I am using Fedora 30 instead of Ubuntu, but this could very well be a non-distribution dependent issue, therefore I'm reporting here instead of opening a new issue in another bug tracker."
1722256,2019-07-21 10:02:48 UTC,"I just made a comment in Launchpad, which on second thought probably could have better been made here."
1722256,2020-03-04 13:23:34 UTC,Updated the bug link
1722256,2018-01-10 10:10:32 UTC,The problem was solved for me when I set `dns=default` in NetworkManager.conf
1722256,2017-11-01 05:59:16 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=750260
1722256,2018-01-11 01:48:31 UTC,Thanks for that. I'm seeing this bug on maybe 2/3 laptops I've tried with Ubuntu 18.04.
1722256,2017-10-10 03:08:06 UTC,apport information
1722256,2015-06-03 09:56:08 UTC,This is the same as downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1176316
1722256,2015-08-31 09:48:34 UTC,"I have a similar problem with an unexplained question mark for a wireless connection that works fine.
I seem to have this issue when I'm behind a proxy (both for wired and wireless network connections)."
1722256,2015-09-08 10:38:43 UTC,"(In reply to Bastien Nocera from comment #2)

>
> [ 3920.153840] f21v.localdomain NetworkManager[826]: <info>  Connectivity
> check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with
> 'Peer failed to perform TLS handshake'.
"
1722256,2015-09-08 14:34:09 UTC,"(In reply to Thomas Haller from comment #5)

> (In reply to Bastien Nocera from comment #2)
> >
> > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info>  Connectivity
> > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with
> > 'Peer failed to perform TLS handshake'.
>
> In this case, the connectivity check failed because of the SSL connection.
>
> It is anyway a bad idea to use https for connectivity checking.
"
1722256,2015-09-08 14:45:12 UTC,"(In reply to Bastien Nocera from comment #6)

> (In reply to Thomas Haller from comment #5)
> > (In reply to Bastien Nocera from comment #2)
> > >
> > > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info>  Connectivity
> > > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with
> > > 'Peer failed to perform TLS handshake'.
> >
> > In this case, the connectivity check failed because of the SSL connection.
> >
> > It is anyway a bad idea to use https for connectivity checking.
>
> Why? It protects the user's privacy, at least a tiny bit.
"
1722256,2017-10-23 08:18:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1722256,2015-09-08 15:27:34 UTC,"(In reply to Thomas Haller from comment #8)

> (In reply to Bastien Nocera from comment #6)
> > (In reply to Thomas Haller from comment #5)
> > > (In reply to Bastien Nocera from comment #2)
> > > >
> > > > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info>  Connectivity
> > > > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with
> > > > 'Peer failed to perform TLS handshake'.
> > >
> > > In this case, the connectivity check failed because of the SSL connection.
> > >
> > > It is anyway a bad idea to use https for connectivity checking.
> >
> > Why? It protects the user's privacy, at least a tiny bit.
>
> it's a bad idea, because it works bad with detecting captive portals.
>
> And a portal might not handle SSL connections at all (which means we would
> detect ""no-connectivity"", instead of ""portal"").
>
> If the portal does handle SSL connections it present an invalid certificate
> and the connection fails again (and to NM it's again not clear that this
> indicates ""portal"").
>
> Also, we warn now about HTTPS use:
> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/
> ?id=eab32a5252e82361a563154cd8bfc3949aaad119
"
1722256,2015-09-08 15:00:14 UTC,"(In reply to Bastien Nocera from comment #6)

> (In reply to Thomas Haller from comment #5)
> > (In reply to Bastien Nocera from comment #2)
> > >
> > > [ 3920.153840] f21v.localdomain NetworkManager[826]: <info>  Connectivity
> > > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with
> > > 'Peer failed to perform TLS handshake'.
> >
> > In this case, the connectivity check failed because of the SSL connection.
> >
> > It is anyway a bad idea to use https for connectivity checking.
>
> Why? It protects the user's privacy, at least a tiny bit.
"
1722256,2015-10-05 09:18:45 UTC,"See also:
https://bugzilla.gnome.org/show_bug.cgi?id=738694"
1722256,2017-10-10 01:32:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722256,2017-10-10 01:33:16 UTC,Confirmed. But also...
1722256,2017-10-10 03:07:50 UTC,apport information
1722256,2017-10-10 03:07:52 UTC,apport information
1722256,2017-10-10 03:08:03 UTC,apport information
1722256,2015-06-02 03:12:42 UTC,"Created attachment 304401
screen shot"
1722256,2015-10-05 09:12:31 UTC,"A question marks occurs also when you are behind a proxy, because the proxy settings are not being used when testing the connectivity. See this issue in the Fedora Bugzilla for more details:
https://bugzilla.redhat.com/show_bug.cgi?id=1184406"
1722256,2017-10-10 03:08:05 UTC,apport information
1722257,2017-11-16 03:43:37 UTC,"They're not listed because we fail to get icons for them (almost not snaps provide a local icon and we get them from the store - not available without network). GNOME Software doesn't allow apps without icons (an upstream decision, and not ideal for our case)."
1722257,2017-11-16 03:45:26 UTC,The reconnection issue is part of a wider problem we have that snapd doesn't provide any notifications of changes and GNOME Software doesn't consider network status to affect the app information. We probably need to do some workarounds in GNOME Software for this and again snapd might better handle this long term.
1722258,2017-10-10 03:09:34 UTC,apport information
1722258,2020-01-24 10:06:32 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1722258,2017-10-10 03:09:31 UTC,apport information
1722258,2017-10-10 03:09:25 UTC,apport information
1722258,2017-10-10 03:09:23 UTC,apport information
1722258,2017-10-10 01:34:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1722258"
1722258,2017-10-10 03:09:29 UTC,apport information
1722269,2017-10-22 08:04:28 UTC,apport information
1722269,2017-10-22 08:04:27 UTC,apport information
1722269,2017-10-22 07:00:32 UTC,"bbswitch is not happy:
[    4.379608] bbswitch: version 0.8
[    4.379618] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[    4.379627] bbswitch: Found discrete VGA device 0000:03:00.0: \_SB_.PCI0.RP05.D034
[    4.379640] bbswitch: failed to evaluate \_SB_.PCI0.RP05.D034._DSM {0xF8,0xD8,0x86,0xA4,0xDA,0x0B,0x1B,0x47,0xA7,0x2B,0x60,0x42,0xA6,0xB5,0xBE,0xE0} 0x100 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[    4.379648] bbswitch: failed to evaluate \_SB_.PCI0.RP05.D034._DSM {0xA0,0xA0,0x95,0x9D,0x60,0x00,0x48,0x4D,0xB3,0x4D,0x7E,0x5F,0xEA,0x12,0x9F,0xD4} 0x102 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[    4.379657] bbswitch: failed to evaluate \_SB_.PCI0.GFX0._DSM {0xA0,0xA0,0x95,0x9D,0x60,0x00,0x48,0x4D,0xB3,0x4D,0x7E,0x5F,0xEA,0x12,0x9F,0xD4} 0x102 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[    4.379658] bbswitch: No suitable _DSM call found."
1722269,2017-10-21 20:28:45 UTC,I also tried with nvidia 387 (from graphics-drivers ppa) and updates from xorg-edgers to no avail (same symptoms).
1722269,2017-10-21 20:15:54 UTC,"ok, above is an apport information with nvidia driver and no graphical boot (due to updating kernel is now -98  but symptoms are the same)"
1722269,2017-10-21 20:14:38 UTC,apport information
1722269,2017-10-21 20:14:31 UTC,apport information
1722269,2017-10-22 08:04:29 UTC,apport information
1722269,2017-10-21 20:14:29 UTC,apport information
1722269,2017-10-21 20:14:28 UTC,apport information
1722269,2017-10-21 20:14:27 UTC,apport information
1722269,2017-10-21 20:14:26 UTC,apport information
1722269,2017-10-21 20:14:34 UTC,apport information
1722269,2017-10-22 08:04:30 UTC,apport information
1722269,2017-10-22 08:04:32 UTC,apport information
1722269,2017-10-21 20:14:24 UTC,apport information
1722269,2017-10-22 08:04:35 UTC,apport information
1722269,2017-10-22 08:04:36 UTC,apport information
1722269,2017-10-22 08:04:37 UTC,apport information
1722269,2017-10-22 08:04:38 UTC,apport information
1722269,2017-10-22 08:04:39 UTC,apport information
1722269,2017-10-22 08:04:40 UTC,apport information
1722269,2017-10-22 08:04:41 UTC,apport information
1722269,2017-10-22 08:04:43 UTC,apport information
1722269,2017-10-22 08:04:46 UTC,apport information
1722269,2017-10-22 08:09:11 UTC,Here is apport information for -92 kernel with NVIDIA 387 ; this boots normally and the driver works.
1722269,2018-03-06 16:28:31 UTC,This is still happening with 4.4.0-116 !!
1722269,2018-04-22 17:01:14 UTC,I gave it a new try today with kernel 4.4.0-121 and the new NVIDIA 390.48 and... it works !
1722269,2017-10-22 08:04:31 UTC,apport information
1722269,2017-10-21 20:14:23 UTC,apport information
1722269,2017-10-22 08:04:34 UTC,apport information
1722269,2017-10-21 20:14:21 UTC,apport information
1722269,2017-10-10 20:09:37 UTC,"Following your suggestion, I switched to nouveau using the Ubuntu GUI."
1722269,2017-10-11 08:07:07 UTC,Can you do `apport-collect 1722269` under 4.4.0-97?
1722269,2017-10-11 20:51:49 UTC,apport information
1722269,2017-10-11 20:51:51 UTC,apport information
1722269,2017-10-11 20:51:53 UTC,apport information
1722269,2017-10-11 20:51:54 UTC,apport information
1722269,2017-10-11 20:51:56 UTC,apport information
1722269,2017-10-11 20:51:58 UTC,apport information
1722269,2017-10-11 20:51:59 UTC,apport information
1722269,2017-10-11 20:52:01 UTC,apport information
1722269,2017-10-11 20:52:02 UTC,apport information
1722269,2017-10-11 20:52:03 UTC,apport information
1722269,2017-10-21 20:14:22 UTC,apport information
1722269,2017-10-11 20:52:05 UTC,apport information
1722269,2017-10-09 14:00:07 UTC,This change was made by a bot.
1722269,2017-10-11 20:52:09 UTC,apport information
1722269,2017-10-21 20:14:19 UTC,apport information
1722269,2017-10-21 20:14:18 UTC,apport information
1722269,2017-10-21 20:14:16 UTC,apport information
1722269,2017-10-21 20:14:13 UTC,apport information
1722269,2017-10-11 20:52:06 UTC,apport information
1722269,2017-10-18 08:46:07 UTC,I have the same problem on 4.4.0-97 and 4.4.0-96 with a Nvidia GTX 1070.
1722269,2017-10-21 20:14:12 UTC,apport information
1722269,2017-10-13 06:29:28 UTC,"When I use apport, it usually opens a tab in my web browser to ask me to authenticate and allow access. Since I do not get to a graphical interface with -97 and nvidia, I did not see how I could process."
1722269,2017-10-13 03:30:01 UTC,"Why did you use nouveau instead of nvidia? The latter one is the one with problem, right?"
1722269,2017-10-11 20:53:01 UTC,Above is the result of apport-collect 1722269 under -97 with nouveau driver.
1722269,2017-10-11 20:52:15 UTC,apport information
1722269,2017-10-11 20:52:13 UTC,apport information
1722269,2017-10-11 20:52:10 UTC,apport information
1722269,2017-10-13 08:04:11 UTC,"I think text-based browser will do, e.g. w3m."
1722269,2017-10-10 19:34:39 UTC,Do you know if this bug also happens with the nouveau driver?
1722271,2017-10-09 14:27:37 UTC,Thanks for this detailed bug report.
1722271,2018-03-27 16:20:40 UTC,@frafu: You probably wanted to say:
1722272,2017-10-10 04:11:17 UTC,Been discussing using ODRS (https://odrs.gnome.org/) for this.
1722275,2017-10-09 14:05:07 UTC,"There is a draft spec cooking here:
https://review.openstack.org/#/c/504952"
1722277,2017-10-09 14:31:00 UTC,"Affected package is wrong.
The is a bug in launchpad that keeps adding it for some strange reasons.
I tried to add install package!"
1722280,2020-06-11 23:59:17 UTC,"Note that this is only for git.  It's somewhat unlikely that we'll be putting the amount of effort into bzr-related changes that would be needed to support the equivalent there too, and the problem was much more pressing for git given the multiple-branches-per-repository model."
1722280,2020-06-11 23:51:39 UTC,"We fixed this early last year (via a separate ""Manage permissions"" view; +sharing is only for read permissions):"
1722285,2017-10-09 14:30:07 UTC,This change was made by a bot.
1722285,2017-10-10 09:02:07 UTC,"Extra info:
In grub ""nomodeset"" is added to the kernel command line, without the MBP does not boot and seems to hang in initrd. It seems that something goes wrong within the radeon driver. With nomodeset set KMS is skipped and the radeon driver (GPU X1600) is used, Wayland isn't run, but xorg-server is run instead."
1722285,2017-10-10 19:32:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1722285,2017-10-10 22:00:39 UTC,"A test with the upstream kernel 4.14 RC4 yielded same (erroneous) result; the requested has been added. The bug status has been set to Confirmed as requested (though that state should not be set by the reporter, i.e. me)."
1722285,2017-10-11 08:01:21 UTC,Can you paste the dmesg with OOPS message?
1722285,2017-10-11 10:09:05 UTC,Could not produce a dmesg with the OOPS.
1722285,2017-10-11 10:36:36 UTC,"Don't use pm-suspend. Use `systemctl suspend` instead.
Also, file an upstream bug at https://bugzilla.freedesktop.org."
1722285,2017-10-13 15:11:16 UTC,"When the MBP is booted in BIOS legacy mode, suspend and resume work."
1722285,2017-10-13 18:31:53 UTC,This guide might be a good place to start:
1722285,2017-10-14 05:37:32 UTC,Please try kernel here:
1722286,2019-02-24 16:03:45 UTC,"It seems there is no issue filed upstream. The closest thing I'd found is:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/111
Nothing about lid-close-ac-action and lid-close-battery-action.
I'm not sure if an upstream bug issue should be filed."
1722286,2017-10-14 12:13:00 UTC,I'm attaching a proof of concept python script that restores the behaviour (in case it's useful to others).
1722286,2017-10-12 15:20:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722286,2018-08-20 20:09:18 UTC,"Can you modify this script so that it works when an external monitor is connected or the laptop is docked? gsd overrides logind, and prevents the computer from suspending in these cases."
1722295,2017-10-09 15:36:33 UTC,"Hi,"
1722298,2017-10-21 18:15:08 UTC,"Perfect , thanks Alessandro."
1722298,2018-01-24 15:53:33 UTC,"I had the same problem on Ubuntu 16.04.3 LTS, also Lenovo Ideapad 700. The fix above worked."
1722298,2018-01-19 10:50:16 UTC,Helped me. Thanks Alessandro.
1722298,2017-10-23 09:24:09 UTC,Same bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219
1722298,2017-10-22 20:24:43 UTC,"I finally got the evemu program to work, same results as above. Now that I know what module, there are lot of other reports. Looks like a longterm fix is coming from upstream. Sorry for the dupe, but thanks for helping track it down and workaround."
1722298,2017-10-21 14:31:26 UTC,Workaround solution:
1722298,2017-10-18 05:40:14 UTC,"I have the same problem, using a Lenovo Laptop."
1722298,2017-10-21 13:26:00 UTC,"I fund a problem with the peaq wmi module. I just executed rmmod peaq_wmi and now it's OK,  but I do not know anything about this module. Can you help me?"
1722298,2017-10-21 02:32:16 UTC,"I'm having the same problem, following Marius Tip theres one Input Device that keeps repeating events. Is this normal? It's really annoying, it interrupts all key holdings (even the arrow ones, ugh). The device that keeps repeating the events, and the repeated events:"
1722298,2017-10-20 12:44:28 UTC,This doesn't look like a terminal problem.  It looks like a kernel problem -- some input device is spamming fake key press events.
1722298,2017-10-19 20:18:28 UTC,"I have the same problem, using the Positivo S1991."
1722298,2017-10-18 05:40:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722298,2017-10-09 15:55:35 UTC,"I wanted to open this while my PC was still in an ""upgraded"" state, but I just did a clean install of 17.10 with today's daily image and the problem persists as reported. I can even reproduce it booting off the the install media and clicking the Try Ubuntu option. Any advice on narrowing it down is welcome."
1722298,2017-10-21 14:10:01 UTC,"""sudo rmmod peaq_wmi"" also fixed the problem for me (thanks Ronaldo!)."
1722299,2017-10-30 20:33:04 UTC,The package has been published and the bug is being set to Fix Released
1722299,2017-10-30 19:43:07 UTC,This bug was fixed in the package linux - 4.4.0-98.121
1722299,2017-10-20 18:24:01 UTC,The snap test results can be found here: https://trello.com/c/4viFAQeq/98-pc-kernel-44098103-88  No regressions found
1722299,2017-10-26 05:51:06 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-98.121/xenial-proposed-published.html"
1722299,2017-10-23 07:42:59 UTC,"4.4.0-98.121 - generic
Regression test CMPL."
1722299,2017-10-19 05:39:00 UTC,Hardware Certification have begun testing this -proposed kernel.
1722299,2017-10-30 15:50:51 UTC,"1678477 	no hardware available anymore, verified on zesty
1718886 	Kleber tried building it, has some network problems, unrelated
1720466         hard to test without a new installer
1718397	        test kernel fixed it, IBM bug
1693369 	test kernel fixed it, IBM bug"
1722303,2017-10-20 18:24:47 UTC,Results here: https://trello.com/c/fyCm7Feo/100-pi2-kernel-440107676-44  No regressions found
1722303,2017-10-25 07:09:37 UTC,Hardware Certification have begun testing this -proposed kernel.
1722303,2017-10-25 07:10:01 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1076.84/raspi2-4.4-proposed-published.html"
1722303,2017-10-30 19:46:40 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1076.84
1722303,2017-10-30 20:41:40 UTC,The package has been published and the bug is being set to Fix Released
1722304,2017-10-30 20:30:41 UTC,The package has been published and the bug is being set to Fix Released
1722304,2017-11-06 10:09:28 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1078.83
1722304,2017-10-25 09:55:42 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1078.83/snapdragon-4.4-proposed-published.html"
1722304,2017-10-25 09:55:16 UTC,Hardware Certification have begun testing this -proposed kernel.
1722304,2017-10-30 19:47:16 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1078.83
1722307,2017-10-09 15:32:52 UTC,"StacktraceTop:
 g_type_check_instance_is_a (type_instance=type_instance@entry=0x55cd73fb34a0, iface_type=iface_type@entry=94340900131696) at ../../../../gobject/gtype.c:4013
 gtk_window_set_transient_for (window=0x55cd750253c0, parent=0x55cd73fb34a0) at ././gtk/gtkwindow.c:3290
 e_credentials_prompter_impl_password_show_dialog (prompter_password=0x55cd73d85b70) at ./src/libedataserverui/e-credentials-prompter-impl-password.c:238
 e_credentials_prompter_impl_password_show_dialog_idle_cb (user_data=0x55cd73d85b70) at ./src/libedataserverui/e-credentials-prompter-impl-password.c:443
 g_main_dispatch (context=0x55cd73d82150) at ../../../../glib/gmain.c:3148"
1722313,2018-02-14 14:34:53 UTC,This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.4
1722313,2018-02-14 14:34:35 UTC,"The verification of the Stable Release Update for util-linux has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1722313,2018-02-14 14:34:29 UTC,This bug was fixed in the package util-linux - 2.30.1-0ubuntu4.1
1722313,2018-02-12 22:25:19 UTC,Update on Artful regression analysis from comment #22.
1722313,2018-02-09 20:46:04 UTC,Summary of analysis of the autopkgtest failures listed for his SRU in http://people.canonical.com/~ubuntu-archive/pending-sru.html
1722313,2018-02-09 18:37:50 UTC,Summary of analysis of the autopkgtest failures listed for this SRU in http://people.canonical.com/~ubuntu-archive/pending-sru.html
1722313,2017-12-06 12:01:30 UTC,Please could someone check the autopkgtest failures listed against this SRU in http://people.canonical.com/~ubuntu-archive/pending-sru.html?
1722313,2017-12-01 19:06:04 UTC,Verified on xenial on a P8 and a z13 zlpar.
1722313,2017-12-01 20:07:18 UTC,verified successfully in amd64 VM for zesty.
1722313,2017-11-30 19:58:50 UTC,"Hello Joy, or anyone else affected,"
1722313,2017-11-28 19:54:10 UTC,"version of package verified on artful,"
1722313,2017-11-28 19:48:30 UTC,"Sorry, comment #13 had a cut-and-paste issue."
1722313,2017-11-28 19:45:59 UTC,Generated an artful VM and verified that this is fixed in artful.
1722313,2017-11-20 15:46:21 UTC,"Hello Joy, or anyone else affected,"
1722313,2017-11-10 15:21:58 UTC,"ACK on the debdiffs, uploaded for processing by the SRU team with a couple of minor changelog changes: added bug number, fixed versioning."
1722313,2017-11-09 22:21:23 UTC,"I have also submitted a patch against recent debian version of this package to Debian. Just in case, I also noted in the debian bug thread the following:"
1722313,2017-11-09 20:01:50 UTC,"Build logs and test runs can be found in PPA at, https://launchpad.net/~j-latten/+archive/ubuntu/joyppa/+packages"
1722313,2017-10-09 16:07:51 UTC,"Comment #3 Should have read ""Common Criteria EAL2 hwclock testcase""."
1722313,2017-11-30 20:00:16 UTC,"Hello Joy, or anyone else affected,"
1722313,2017-10-09 16:01:50 UTC,"build log and tests run
https://launchpad.net/~j-latten/+archive/ubuntu/joyppa/+build/13375821"
1722333,2017-10-25 11:18:50 UTC,"4.10.0-1008.8 - gcp
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1722333,2017-10-30 19:44:19 UTC,This bug was fixed in the package linux-gcp - 4.10.0-1008.8
1722333,2017-10-30 20:40:57 UTC,The package has been published and the bug is being set to Fix Released
1722350,2017-10-13 19:57:25 UTC,"Not the precise answer to this issue, but the development MassLNC is funding with bug 1721575 will provide a mechanism for staff to add selected records from a catalog search query to a bucket."
1722363,2017-10-09 18:11:45 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1713717, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1722363,2017-10-10 09:15:41 UTC,"The duplicate bug is private and as such useless for public tracking.
I made this bug public and removed the duplicate status."
1722363,2017-10-13 02:53:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722364,2017-10-10 08:26:52 UTC,AirDC++ now uses the regular dispatch function for parsing ADC UDP commands that should fix the issue: https://github.com/airdcpp/airgit/blob/6a40613788e7ed8a7478f4f1789bbd142a98d231/airdcpp/airdcpp/UDPServer.cpp#L130-L175
1722364,2017-10-10 23:23:42 UTC,<https://github.com/airdcpp/airgit/commit/6a40613788e7ed8a7478f4f1789bbd142a98d231> makes perfect sense. a similar patch for DC++ would be very welcome. :)
1722364,2017-10-11 15:32:12 UTC,"Yeah, I took the code from AdcHub where it was public for some reason. Here's a patch for DC++."
1722364,2017-10-11 22:15:26 UTC,"what a nice patch! thanks, applied.
I especially liked the variadic template... ;)"
1722364,2017-10-12 07:00:30 UTC,"Ah right, the empty string check should have been added there as well (even though empty data seems to be currently discarded at https://sourceforge.net/p/dcplusplus/code/ci/f8540557bd5c28a9d0b3879b3e6b26f50ab670a6/tree/dcpp/SearchManager.cpp#l132). The old NMDC code was moved as it was as I don't even want to understand the logic in it....."
1722364,2017-10-16 18:35:01 UTC,Fixed in DC++ 0.867.
1722368,2018-01-18 08:29:17 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2008
1722378,2017-10-09 20:08:18 UTC,"Privilege escalation via profile is still prevented, at least.  It looks like it's just a UI check in the XUL client that disables the Save button if the user being edited is the same person logged into the client."
1722378,2019-11-07 20:34:14 UTC,Fixed for 3.3 per https://bugs.launchpad.net/evergreen/+bug/1842940
1722381,2017-10-10 18:22:02 UTC,"I would second this, when I add new staff accounts for one system, I need to give access to every branch in that system since we have staff that move around from branch to branch.  Because of the current design this is error prone since i need to pick out the 23 locations to check that are mixed in with the branches from another system.
Josh"
1722381,2017-10-10 21:31:01 UTC,We also have a large system with lots of org units and sometimes have to assign working locations when logged in as a global user.
1722383,2018-09-12 18:28:03 UTC,I am testing this bug patch.
1722383,2018-09-12 15:50:16 UTC,I've grabbed this again during bug squashing day here. Possible fix @
1722383,2018-09-12 19:00:39 UTC,Dawn confirmed the patch as not working:
1722383,2018-08-07 16:26:05 UTC,"The prior commit did not work, so I'm taking another swing at the sorting. Commit has been pushed to the above branch. Again."
1722383,2018-08-07 14:03:43 UTC,"Sandbox testing indicates that adding an orderBy filter using the ""name"" attribute does not provide alphabetical sorting. I've pushed a new commit to the above branch to try a different approach to the sorting."
1722383,2018-08-01 16:47:34 UTC,I have a potential fix at:
1722383,2018-05-30 01:33:08 UTC,Just a note that this should probably be fixed for both Evergreen/Open-ILS/src/templates/staff/t_login.tt2 and Evergreen/Open-ILS/src/templates/staff/admin/workstation/t_workstations.tt2 (aka at the main login screen and also in Administration > Workstation > Registered Workstations).
1722383,2018-08-07 17:01:21 UTC,And I'm stepping away for now. The commit history of that branch will give three examples of nonworking solutions.
1722384,2017-10-09 19:37:54 UTC,Are you saved changed value as default?
1722384,2017-10-16 20:26:03 UTC,"Yes I did, in the configuration (F2) menu : ""Enregistrer tous les réglages"" (French)."
1722384,2017-11-24 16:11:19 UTC,Once again there are misunderstandings.
1722384,2018-09-26 05:04:29 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/400
1722387,2017-10-09 20:38:01 UTC,Related to:
1722387,2017-10-18 15:57:00 UTC,"The column picker dropdown for all interfaces has a very long list of options that is not sorted in any obvious way. To improve usability, it should either be completely alphabetical or have some sort of dividers/section headers."
1722387,2018-03-13 20:56:08 UTC,Working branch user/jeffdavis/lp1752983-column-picker-sort-alpha has a fix that sorts the column picker alphabetically.
1722387,2018-03-13 21:15:44 UTC,"We talked a bit about column pickers at the hack-a-way. I was working on https://bugs.launchpad.net/evergreen/+bug/1735808 at the time, but I didn't make as much progress on it as I had hoped."
1722388,2018-03-25 15:23:43 UTC,Please try following the proposals in https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/799505 comments #2 and #4. Does it solve the problem?
1722388,2017-10-11 22:11:31 UTC,Disregard the proxy erros:
1722388,2017-10-11 13:26:55 UTC,Please check if librsvg is installed on your machine.
1722388,2017-10-10 05:59:15 UTC,"[my-hostname]$ md5sum /usr/share/shutter/resources/icons/sel_window_section.svg
0a6a63c9b572a5af934d4d4425bc8d64  /usr/share/shutter/resources/icons/sel_window_section.svg"
1722388,2017-10-10 04:27:21 UTC,Could you please run
1722388,2017-10-11 22:09:55 UTC,I do have the librsvg2 and even librsvg2-tools packages installed:
1722394,2017-10-17 18:14:40 UTC,What in the world is this:
1722394,2017-10-18 02:19:58 UTC,"Beats me, but the bug isn't actually new.  After talking to some folks at the local LUG and perusing the forums I've seen numerous cases of this issue occurring.  There are other bug reports as well, and I believe most of them have been closed as unresolved.  The gist of Canonical's stance is this:
Using btrfs to make a whole-disk volume (so that one mounts /dev/nvme0n1 instead of /dev/nvme0n1p1 or /dev/sda instead of /dev/sda1) is unsupported so this isn't a bug but could maybe be resolved with a feature request."
1722394,2017-10-25 14:01:28 UTC,I don't think that is related to this error.
1722404,2019-05-08 15:34:07 UTC,"Reviewed:  https://review.opendev.org/653894
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0ae53f2bf0a753edfacf3ed8b45bcc40b69428d1
Submitter: Zuul
Branch:    master"
1722404,2019-04-19 01:56:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653894"
1722404,2018-03-21 02:01:46 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/540145"
1722404,2018-03-17 08:02:30 UTC,"@Saulo, check https://bugs.launchpad.net/nova/+bug/1746509/comments/4"
1722404,2018-02-02 20:10:47 UTC,"HI ,"
1722404,2018-02-01 21:28:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/540145"
1722404,2017-10-25 19:22:10 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1722404,2017-10-09 20:56:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510691"
1722404,2017-10-18 22:10:04 UTC,"Reviewed:  https://review.openstack.org/512456
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=42e5b7549e8b920e682204f5745454c0680ec0fb
Submitter: Zuul
Branch:    stable/pike"
1722404,2017-10-17 17:16:51 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/511538
Reason: Turns out that this didn't really fix anything, so we won't backport it."
1722404,2017-10-17 00:56:01 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/512456"
1722404,2017-10-17 00:42:37 UTC,"Reviewed:  https://review.openstack.org/511651
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=42b70509c6e632b0553e92d8ff04cb4cecaa563c
Submitter: Zuul
Branch:    master"
1722404,2017-10-13 13:34:59 UTC,Related debugging: https://review.openstack.org/#/c/511651/
1722404,2017-10-12 17:42:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/511538"
1722404,2017-10-12 12:07:31 UTC,"Reviewed:  https://review.openstack.org/510691
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3cc3cc453dc16e22365bea597c1be5bb0be57aeb
Submitter: Jenkins
Branch:    master"
1722404,2017-10-24 12:41:42 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1722409,2017-10-10 05:12:49 UTC,"Set the status to ""In-progress"" because this report has an assignee."
1722425,2017-10-10 02:45:55 UTC,Any grid is visualization of coordinate systems by definition. Please describe your reasons to introducing of this very strange grids.
1722425,2017-10-10 09:40:55 UTC,"I have a customer requesting it?  People could develop plugins using this feature, such as those who want to label hemispheres, or labeling degrees of longitude with text or images at various levels of detail (LOD). If this can be done with coordinate systems, please fill me in on some details, as I only found grids.  How do I visualize a number (say 10, 24 or more) of great circles spanning 360 degrees in a coordinate system, if that is possible?  Please point me at a plugin, or a place in the source code I can add it.  I am a newbie at stellarium (and my customer would prefer if I did the changes, so it would be best if I could implement it in a plugin)."
1722425,2017-10-10 09:43:29 UTC,"I am going for a general feature that could implement many customer's desires.  If there isn't a demand out there, I don't think it should be implemented, but since I have a customer, it seems like there is a demand.  Perhaps present the idea to your customers, and see if they think it is a good idea?"
1722425,2017-10-10 10:40:14 UTC,"We don't have ""customers"". (Nobody pays for our work.)"
1722425,2017-10-10 14:10:33 UTC,Please look at Compass Marks plugin also.
1722425,2018-09-19 14:01:50 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/370
1722429,2017-12-11 04:17:35 UTC,[Expired for Mahara because there has been no activity for 60 days.]
1722429,2017-10-11 20:36:42 UTC,Can you give a description of what you were doing to get the messages?
1722429,2018-01-03 03:49:19 UTC,This was fixed in another bug for master mahara 18.04
1722442,2017-10-12 05:22:27 UTC,"* Normally an error like that suggest some inconsitency with cluster node.
  This can happen if there is local trx that is not replicated."
1722442,2018-01-18 08:38:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2009
1722443,2018-02-21 02:22:27 UTC,"Change abandoned by Wonil Choi (<email address hidden>) on branch: master
Review: https://review.openstack.org/510737
Reason: ok I would fix this in my configurations"
1722443,2017-10-10 04:50:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/510737"
1722444,2017-10-16 10:29:29 UTC,"I am seeing that, too. There seems to be one such entry per paste file."
1722444,2018-10-26 18:29:36 UTC,"Reviewed:  https://review.openstack.org/515291
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=0c0eae3b1eb537159f26c82647fb61cc3de8536a
Submitter: Zuul
Branch:    master"
1722444,2018-10-16 19:52:57 UTC,"same on nova-api log on the controller node.
Rocky vanilla install with latest patches applied under ubuntu 18.04
I would risk to say it would be desirable to fix the root cause rathar than just hidding the message so that it appears only on debut. Otherwise it could be missleading when researching other issues."
1722444,2017-10-13 21:24:22 UTC,This looks specific to how you're configuration is set up. Can you share how you have keystone configured at each of the services (omitting sensitive information)?
1722444,2018-03-20 23:41:39 UTC,"Is this affecting all APIs ? I have the issue with glance particularly.
Is this going to be patched for Pike as well?"
1722444,2017-12-13 10:20:42 UTC,@pshchelo Appears to be worth its own bug report.
1722444,2018-07-22 19:19:49 UTC,I have it coming from cinder-api as well:
1722444,2017-10-26 18:06:19 UTC,__file__ and here come from paste.deploy:
1722444,2017-10-26 06:40:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/515291"
1722444,2017-10-24 12:05:06 UTC,"A simple approach to fix this is to convert the warning logging to debug.I don't see a reason this should be logged and we should be OK removing it..but it anyone has concerns with it, we could change it to debug."
1722444,2017-10-24 11:53:47 UTC,"The flow where this gets logged is

>> https://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token/__init__.py#L993
>> https://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token/__init__.py#L555
>> https://github.com/openstack/keystonemiddleware/blob/stable/pike/keystonemiddleware/_common/config.py#L78
>> https://github.com/openstack/keystonemiddleware/blob/stable/pike/keystonemiddleware/_common/config.py#L58
"
1722444,2017-10-24 11:51:41 UTC,"This is seen for all the services. ""The option ""configkey"" in conf is not known to auth_token"" is seen specifically only for Panko and Gnocchi."
1722444,2017-12-06 13:57:01 UTC,"Not sure if ironic does something wrong, but it its case it seems keystonemiddleware tries to parse the whole CONF (all config options from [DEFAULT] and all sections)"
1722448,2017-10-10 05:05:34 UTC,Apport report from frozen system.
1722455,2018-12-20 09:02:05 UTC,"Thank, you too"
1722455,2018-12-19 10:28:38 UTC,@Sebastian:
1722455,2018-12-19 10:16:29 UTC,"I want to connect to an IMAP and SMTP service.
I have to enter the email address (which is something other than the login name).
Do I give the login name, I cannot forward, do I give the email address, I can forward but the login into the server fails.
""Error connecting to IMAP server
Invalid certificate.""
Ignoring brings me to SMTP
""Error connecting to SMTP server
Could not connect to <myserver>:
Connection refused"""
1722455,2018-12-18 13:27:45 UTC,What is SOGo and what do you mean 'connect to a user calendar'? If you go to settings -> online account and add e.g your google account the calendar should automatically be available in the application
1722455,2018-12-13 10:25:08 UTC,There is no error message it just does not work or allow the creation of calendars.
1722455,2017-12-10 14:51:34 UTC,"Wolf, part of why this bug was closed is because you have combined several different issues into one bug, which makes it difficult for the bug to be triaged and for a developer to fix issues."
1722455,2017-10-10 07:28:13 UTC,"Thank you for your bug report, you list different issues there"
1722455,2017-12-10 04:17:30 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1722455,2018-12-12 15:25:03 UTC,"It's still unclear chat error you get if you try to add your calendar through the online account settings, could you describe the exact steps you are using and the error you get?"
1722455,2017-12-10 10:37:26 UTC,As a workaround:
1722455,2017-12-10 10:33:29 UTC,How do you add a calendar in GNOME calendar?
1722469,2019-04-20 17:17:13 UTC,Fixed in version fastqc/0.11.7+dfsg-1 (Eoan)
1722470,2017-10-10 08:19:21 UTC,"I found something more in nova-conductor log:
http://paste.openstack.org/show/623186/"
1722470,2017-10-10 08:25:30 UTC,"After some more digging, in nova-compute.log:
http://paste.openstack.org/show/623187/"
1722470,2017-10-10 09:23:30 UTC,"After more searches, it appears it's a disk space issue on the undercloud:
InstanceDeployFailure: Failed to provision instance 0cf68149-bae6-432c-93b2-6d58d2a48661: Failed to deploy. Error: Disk volume where '/var/lib/ironic/master_images/tmpjEgvzp' is located doesn't have enough disk space. Required 5211 MiB, only 4467 MiB available space present."
1722470,2019-09-30 15:01:56 UTC,I believe this may now be addressed by this validation: https://github.com/openstack/tripleo-validations/tree/master/roles/undercloud-disk-space
1722478,2019-03-16 03:08:56 UTC,"Thanks for the tip Kai-Heng Feng. It appears this resolves the issue thus far with the two finger click issue, but it seems not to recognize the two finger scroll still however I think that should probably be a different issue."
1722478,2019-04-14 14:49:24 UTC,disregard my post. Seems to work now after I rebooted. Just tested closing the lid reopening and it works fine. I'll post on here if I find any further issues. Thanks
1722478,2019-04-14 14:44:26 UTC,"I have a T440s running 18.04.2 after I close the lid and reopen to continue session, the scrolling on my trackpad gets lagged and the pointer seems off. I have to to a restart to make things normal again. I followed the fix on comment #44 and #45 and after suspend my scroll completely stopped working. Any help or tips from the other users with T440s'?"
1722478,2019-04-11 18:29:29 UTC,kmod (25-1ubuntu3) disco; urgency=medium
1722478,2019-04-10 18:13:54 UTC,"Ok, I meant ""still present in Ubuntu 19.04"" in the last comment :D"
1722478,2019-04-10 17:57:48 UTC,"For Robin (brobert420), who in comment #69:"
1722478,2019-03-15 03:43:37 UTC,"Try removing ""blacklist i2c_i801"" from /etc/modprobe.d/blacklist.conf."
1722478,2018-12-06 10:56:20 UTC,"Thinkpad T540p, same as comment #86: reloading psmouse fixes the problem until next suspend, setting psmouse.synaptics_intertouch=0 fixes it for good.
Extra note: i2c_i801 isn't blacklisted, but does not load by itself either. Having it loaded (including before psmouse) seems to have no effect on multitouch getting messed up on resume."
1722478,2019-01-07 06:42:18 UTC,"This will be solved once LP: #1802135 is ""Fix Released""."
1722478,2019-01-07 06:26:26 UTC,"Bug affects Ubuntu 18.10 on W540 as well. Confirm psmouse.synaptics_intertouch=0 (so called) fix. Hello, guys, we're in the 21st century, perhaps you did not have time to notice?!?"
1722478,2019-04-19 13:13:27 UTC,The instructions in comments #44 and #45 totally solved this for me! Thank you.
1722478,2018-11-25 18:55:26 UTC,"Comment #44 and #45 worked fine for me. I have a Lenovo ThinkPad T440
Thaks"
1722478,2018-11-23 02:57:12 UTC,"corentin barbu, please file a new bug as Precision 7530 uses a different touchpad."
1722478,2018-11-22 22:55:55 UTC,Similar problem here on brand new Dell precision 7530 sold with Ubuntu 16.04...
1722478,2018-11-10 23:19:37 UTC,"For Ubuntu 18.04 on ThinkPad-11e, kernel version 4.15.0-38-generic:
A) comment #44 and #45 solves the issue completely.
B) comment #16 works temporarily/partially.
C) comment #63  ""blacklist i2c_i801"" does not exist in /etc/modprobe.d/blacklist.conf"
1722478,2019-03-15 02:51:31 UTC,"I can confirm this issue is still present in 18.04 with a new model W540. If anyone wants me to provide any info, please let me know what you would like. Will be glad to help."
1722478,2019-05-14 18:24:33 UTC,"I was not having any issue with two-finger scrolling on my T560 and kernel 4.18.0-18-generic. I was trying to resolve a separate problem, that the pointing stick pointing in the center of the keyboard wasn't functioning, and would in fact cause the touchpad to stop functioning if I attempted to use it. The pointing stick's function was restored by adding psmouse.proto=imps to my bootloader options. However, now my touchpad 1) refuses to send scroll events, and 2) refuses to stop emulating mouse clicks (even after it's been disabled in tweaks). I've attempted every fix on this thread, with no success. Some of them cause the pointing stick to stop working again."
1722478,2019-09-19 17:53:23 UTC,"This is getting creepier. Even though as I said in comment #66 I was able to fix this with modprobe i2c-i801, it no longer works after upgrading from 5.0.0-27-generic to 5.0.0-29-generic."
1722478,2019-06-23 22:04:01 UTC,"Hardware: Thinkpad T440s
OS/Kernel: Kubuntu 18.04/4.15.0-52-generic
Driver: mtrack"
1722478,2021-02-24 23:07:13 UTC,"Thinkpad T400 with non working two finger scroll here running Kubuntu 20.04, I just wanted to comment that none of the above solutions worked for me, but one that I found buried in a youtube video did get it to work! And I just can't leave it visible ONLY in a video, it's just not right."
1722478,2020-07-31 13:02:29 UTC,I have the same problem on my Thinkpad x240 with Ubuntu 20.04
1722478,2020-06-27 20:21:41 UTC,Also seeing the same behavior on 20.04
1722478,2020-05-09 23:24:45 UTC,"thrantir's solution works for me in 20.04, is there a way to make this automatic on wake?"
1722478,2020-04-22 09:14:26 UTC,"I got this issue on Ubuntu 20.04 too... on this laptop I had a similar problem on the 19.10, the touchpad didn't work at all after resum from suspend, i used to fix that calling"
1722478,2020-04-14 18:05:43 UTC,"I started to experience this bug now after kernel update, 4.15.0-96-generic, 18.04.4, Thinkpad-T470s."
1722478,2020-02-26 07:20:48 UTC,The bug is still present in 5.3 (from Ubuntu). I haven't had a chance to check upstream yet. Is any maintainer monitoring this ?
1722478,2019-05-14 18:29:09 UTC,"Quick follower to my own #102, it turns out that my machine simply needed to be started twice with the bootloader option psmouse.proto=imps set. The first time shook something looks in Gnome which resulted in a notification appearing about a minute after boot, ""software update made that require restart."" After the restart, when I open my Mouse & Touchpad control panel, the two-finger/edge-scrolling/tap-to-click controls have appeared (they were hidden on the first boot!) and function correctly."
1722478,2020-01-24 08:35:12 UTC,Also on 18.04.3 with 5.3.0-26-generic on a clevo p650re.
1722478,2019-12-06 17:53:06 UTC,After a reboot applied an automatic system update I applied today to my 18.04.3 LTS IBM ThinkPad X1 Carbon my mouse wasn't working!
1722478,2019-11-13 07:33:50 UTC,"With my T480 and the 5.0 ubuntu kernel, and the 5.3 in the proposed PPA, two finger scrolling does not work unless I specify psmouse.synaptics_intertouch=0
or =1
either value fixes it."
1722478,2019-10-13 00:35:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722478,2018-11-08 07:52:07 UTC,"Sorry, I messed up something last time. #16 (the modprobe thing) fixes it temporarily."
1722478,2019-10-08 06:48:55 UTC,"On my ThinkPad T580, I have the same issue. Two-finger scrolling no long works after suspend.
The problems started after the upgrade to kernel:
5.0.0-31-generic #33~18.04.1-Ubuntu SMP Tue Oct 1 10:20:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1722478,2019-09-18 09:04:56 UTC,"Just adding a quick note that I experienced this problem on a Thinkpad T480 running 18.04, after updating to 4.15.0-62-generic. Going back to 4.15.0-55-generic fixes the issue. I didn't check -58 and -60 to see how they behave, but I should do that as soon as I have time for that. Note that it may also be a different issue with the same symptoms. This is also a SynPS/2 Synaptics device."
1722478,2019-08-27 04:50:46 UTC,#44 & #45 solve the issue
1722478,2019-12-31 20:02:45 UTC,Same issue on Ubuntu 18.04.3 (kernel 4.15.0-72) with a Lenovo Thinkpad E580.
1722478,2019-10-13 00:34:31 UTC,"ThinkPad T580, trying to fix random secondary mouse button click events had me try out the xinput-xwe-18.04 package when I noticed the same problem. Randomly timed middle button clicks had not gone away."
1722478,2018-11-08 07:48:39 UTC,"It affects me too, on fresh Ubuntu 18.04 on Thinkpad X240. The two finger scrolling works until suspend/resume, after that only the three-finger one, but not without glitches. The modprobe command disables both my touchpad and trackpoint."
1722478,2017-11-15 04:08:52 UTC,Commit 6c53694fb2223746738d1d0cea71456ca88c8fb2
1722478,2017-10-25 08:24:07 UTC,also occurs on fedora: https://bugs.freedesktop.org/show_bug.cgi?id=103149
1722478,2017-10-25 06:06:14 UTC,also affects me! I am using thinkpad t440s
1722478,2017-10-24 18:45:18 UTC,"The bug affects me as well, same machine. In the mean time, to avoid rebooting, you can reload the module, as super user:
modprobe -r psmouse
modprobe psmouse
This fix the problem for me."
1722478,2017-10-23 14:46:06 UTC,"Make sure v4.9 is good and v4.10 is bad, then find the first version of v4.10-rc* that has this problem."
1722478,2017-10-23 10:27:44 UTC,"I suppose I should start at kernel 4.10, since it was working with kernel 4.9 on Debian Stretch."
1722478,2018-11-04 08:04:10 UTC,I can also confirm that this problem still exists with a fresh install of Ubuntu 18.10 with kernel 4.18.0.. I will try the psmouse.synaptics_intertouch=0 workaround.
1722478,2017-10-20 11:10:52 UTC,I have installed your kernel:
1722478,2017-10-26 23:05:55 UTC,Also affects me on a Thinkpad T440 in Ubuntu 17.10
1722478,2017-10-20 06:44:16 UTC,Please try kernel here:
1722478,2017-10-13 15:50:22 UTC,Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?
1722478,2017-10-13 15:30:23 UTC,"> Does ""synclient HorizTwoFingerScroll=1"" work?
"
1722478,2017-10-13 14:40:15 UTC,"Does ""synclient HorizTwoFingerScroll=1"" work?"
1722478,2017-10-12 19:45:41 UTC,And it's gone again :(
1722478,2017-10-11 11:53:38 UTC,Now it's back after the latest kernel update.
1722478,2017-10-11 08:54:19 UTC,"Sigh, and it broke again after this morning's updates and a reboot. Here is a list of the updates in question if it can be of any help:"
1722478,2017-10-10 08:56:40 UTC,I managed to get two-finger scrolling working after installing the Intel microcode firmware package.
1722478,2017-10-17 19:56:54 UTC,"I found a reproducible setup for this bug: I can get 2-finger scrolling to work after a fresh boot, but it stops working after resuming from suspend."
1722478,2017-10-29 11:47:56 UTC,so i tested some kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/
1722478,2017-10-20 14:47:44 UTC,You need to do a kernel bisection then.
1722478,2017-10-31 10:14:56 UTC,having the same issue with my t440p thinkpad after updating from 17.04 to 17.10...
1722478,2017-10-30 11:55:23 UTC,"First, make sure 4.11 is working."
1722478,2017-11-14 07:15:31 UTC,"Sorry for the late reply, here's the next one,"
1722478,2017-11-11 02:45:21 UTC,"Hello again, I spoke too soon. Problem went away immediately after installing `intel-microcode` but returned after suspend and resume."
1722478,2017-11-11 01:42:01 UTC,"I can confirm that the this last kernel does not work (lp1722478-bisect-1), while the previous did (fastreconnect)"
1722478,2017-11-10 23:45:23 UTC,"Hi, I am running Ubuntu 17.10 GNOME with Wayland using a Thinkpad T440 as well. Installing `intel-microcode` fixed the issue immediately. I'm assuming this is proprietary code :\"
1722478,2017-11-10 04:58:57 UTC,"hi, this kernel has the bug"
1722478,2017-11-09 07:17:58 UTC,"Use 0ab3fa57425 as good,
03b22057e8ed as bad."
1722478,2017-11-09 05:26:30 UTC,"Hi, thanks for the kernels. Unfortunately both are working fine :/ Was there another commit touching the psmouse-base.c between the good and bad commit (since i couldn't revert the commit easily)?"
1722478,2017-11-14 12:55:52 UTC,"Hi, this one is working fine for me!"
1722478,2017-11-07 11:38:05 UTC,"Hi, i have some problems reverting the commit. This is what i did:"
1722478,2017-11-09 04:16:37 UTC,"Linux kernel built with the commit:
http://people.canonical.com/~khfeng/lp1722478+fastreconnect/"
1722478,2017-10-31 10:33:13 UTC,@fgod1983
1722478,2017-10-31 11:18:54 UTC,@ kaihengfeng
1722478,2017-10-31 15:41:15 UTC,"the modprobe trick works (thank god), this helps a lot! I will see if i can install the kernel that does work and see how this works with all the rest of my laptop!"
1722478,2017-10-10 08:30:08 UTC,This change was made by a bot.
1722478,2017-11-03 09:56:49 UTC,"Hi, so i have tried it again with much more testing etc. However, i got some problems and i had to abort bisecting"
1722478,2017-11-03 19:20:48 UTC,"Also affects me (T540p) on 4.13.11-1-ARCH (arch linux default), since a recent (kernel?) upgrade. Modprobe workaround works for me."
1722478,2017-11-07 04:07:31 UTC,"Checking the commits between from a71c9a1c779f to 03b22057e8ed, this one looks very suspicious.
Can you revert this commit and see if this the culprit?"
1722478,2017-11-02 07:07:11 UTC,"Thorsten,"
1722479,2017-10-10 08:32:15 UTC,And another screenshot
1722479,2017-10-12 19:03:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722479,2017-11-03 12:40:28 UTC,To my bare eyes it seems the alpha level of top bar is ~0.3 whereas alpha level of the dock is 0.2 by default when all windows are hidden. I changed the the alpha level of the dock to 0.3 using dconf-editor and now it seems they're pretty much consistent with each other.
1722479,2017-11-06 02:02:44 UTC,Thanks but your screenshot shows the problem is now reversed (lighter panel and darker dock :).
1722487,2018-05-05 23:20:04 UTC,Bug is still present in 18.04 and eog 3.28.1
1722487,2018-01-20 04:17:41 UTC,[Expired for eog (Ubuntu) because there has been no activity for 60 days.]
1722487,2017-11-20 17:52:02 UTC,"I'm not using Ubuntu but Arch and I'm affected by the same problem like Simon.
So it seems like to be an upstream bug."
1722487,2017-10-11 09:58:02 UTC,"It usually happens when I am switching between the photos in eog and going back and forth. I have not really worked out a logic behind the error yet, but it seems to happen more with some photos than others. Once I get the error, I can just jump to the next picture and go back and it opens without problems.
I am attaching a few of the photos that failed to be displayed in eog frequently."
1722487,2017-10-10 09:02:30 UTC,apport information
1722487,2017-10-10 09:46:01 UTC,"Yes, I can reproduce the error when the photos are on my harddrive."
1722487,2017-10-10 09:12:12 UTC,Thank you for your bug report. Do you get the same issue if the photos are on your disk? Could be an i/o error on the card...
1722487,2017-10-10 09:02:29 UTC,apport information
1722487,2017-10-10 09:02:28 UTC,apport information
1722487,2017-10-10 19:08:35 UTC,Does it do it on a specific photo? or a set of photos? could you maybe share them on the bug report?
1722487,2017-10-10 09:02:26 UTC,apport information
1722493,2018-01-18 08:29:01 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-880
1722502,2017-10-14 21:24:39 UTC,fixed in 4ppa57
1722508,2017-10-10 14:52:43 UTC,"I've just checked 17.04, and it also looks fine. My guess is that something has changed in ""freetype"" when it was updated from 2.6.3 to 2.8.0, so I'm setting ""freetype"" as the package for this bug."
1722508,2017-11-13 14:06:00 UTC,"I just created two VMWare-machines to show the difference. One with a Kubuntu17.10-image, one with a KDE-Neon-image. In Kubuntu I installed the freetype-PPA to get Version 2.8.1, in KDE-Neon they stick to 2.6.1. On both I startet a Konsole-Session with Monospace-Font. The Result is attached."
1722508,2017-11-28 12:45:20 UTC,"Cool,"
1722508,2017-10-10 12:30:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1722508,2017-11-30 19:05:58 UTC,One of the primary differences in freetype-2.8 and prior Ubuntu versions of freetype is the introduction of TT_CONFIG_OPTION_SUBPIXEL_HINTING in /include/freetype/config/ftoption.h in freetype-2.7.X and later. The default value is:
1722508,2017-11-30 19:11:50 UTC,"In the first line of third paragraph of my prior post I meant to say ""(commented out)"" instead of ""(uncommented)""  So, that line should read: ""This needs to be undefined (commented out) in order for freetype-2.7 and 2.8 to render fonts identically to prior versions of Ubuntu freetype (freetype-2.6.X and earlier)."""
1722508,2017-11-30 20:29:05 UTC,"Adding the attached patch to the diff file will cause freetype-2.8 to render fonts exactly like in earlier Ubuntu versions (such as freetype-2.4.X, 2.5.X and 2.6.X)."
1722508,2017-11-30 20:41:35 UTC,"Gordon, according to earlier comments, the Qt part of this bug will be fixed before 18.04 LTS's release. Are you using Kubuntu or Qt apps?"
1722508,2017-12-01 00:21:26 UTC,"The attachment ""Patch to disable #define TT_CONFIG_OPTION_SUBPIXEL_HINTING"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1722508,2017-12-01 15:34:31 UTC,"Hello jbicha,"
1722508,2017-12-01 16:41:15 UTC,"> Its not so much that the font rendering is better or worse but that it is different than before
"
1722508,2017-12-24 11:31:36 UTC,"In german ubuntuusers forum there is an simpler solution without need to downgrade libfreetype.
https://forum.ubuntuusers.de/post/8914328/"
1722508,2018-01-05 20:16:17 UTC,"Hi Martin,"
1722508,2018-01-30 17:17:43 UTC,"I can report that the solution Martin reported works also for Monospace in Konsole-sessions.
Because it's much better than downgrading, I removed all the changes I described in #23 and it works like a charm."
1722508,2018-03-03 15:48:18 UTC,"Thanks Martin,"
1722508,2018-07-06 08:54:06 UTC,I just installed the new KDE Neon Bionic version as a VM. The Trick doesn't work there. The freetype-version is 2.8.1-2ubuntu2 like on the Kubuntu Host. Maybe the /etc/environment is ignored there. I'm just researching.
1722508,2018-08-18 09:38:12 UTC,This issue hit me when upgrading from Xubuntu 16.04 to 18.04.1.  Martin's trick above worked to bring rendering back to a pleasant state (thanks!).
1722508,2019-11-10 14:57:32 UTC,"Martins trick worked till 19.04. Since 19.10 it seems to be ignored.
Freetype now has version 2.9.1. Any ideas ?"
1722508,2017-11-11 10:16:25 UTC,Downgrade libfreetype6 to 2.6.3 as I decribed and it will be fixed.
1722508,2017-11-10 19:50:24 UTC,"In 17.10 (Gnome), when I change the font to 'Ubuntu Mono Regular', as I always do, and switch to Antialiasing LCD in gnome-tweak-tool and Hinting to Full, fonts look messy. When I do the same in Ubuntu 16.04 via unity-tweak-tool, fonts are crisp and sharp. Comparison is depicted in the attachment."
1722508,2017-11-28 12:47:40 UTC,"Then see here the correctly displayed fonts on Gmail (also downloaded from Gmail's server, no local font)."
1722508,2017-11-06 17:35:37 UTC,"In my (humble) opinion the best way to solve this thinking forward, is to upgrade to freetype 2.8.1, plasma 5.11 and adjust font queries in kdeglobals and trolltecht.conf without weight specific strings as described in this bug:
https://bugreports.qt.io/browse/QTBUG-63792
It's also nice to see that trolltech is working on it!"
1722508,2017-10-10 15:56:02 UTC,"OK, I've just compiled freetype 2.8.1 from the latest source"
1722508,2017-10-13 15:58:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722508,2017-10-13 16:17:57 UTC,"freetype 2.8.1 fixes hinting of normal fonts, but not bold."
1722508,2017-10-13 16:45:05 UTC,"That's strange because bold letters of ""Courier New"" certainly look fine with freetype 2.8.1.
Do you mind telling me which font you're using?"
1722508,2017-11-10 10:09:16 UTC,"I had the same Problem. The monospace-font in konsole looked ugly after upgrade from 17.04.
Same with freetype 2.8.1.
Then I downgraded libfreetype to 2.6.3 as HorstBort mentioned, and konsole looks nice again.
Here the description how I managed it:"
1722508,2017-10-13 18:54:35 UTC,"It seems a plasma desktop bug, window title renders fine now, but bold fonts in panel and kmail still render the ugly way."
1722508,2017-10-13 19:07:42 UTC,"The title of Konsole definitely doesn't look right, but I'm not sure I would blame FreeType for that. It could be some KDE or Qt problem."
1722508,2017-10-13 19:09:09 UTC,"Oh, totally missed your comment. That confirms it."
1722508,2017-10-13 19:14:17 UTC,"I meant to write ""fine after upgrade to plasma 5.11""."
1722508,2017-10-13 17:21:30 UTC,"I'm using Ubuntu for all Desktop fonts. Attached is a screenshot of the problem.
Title is Ubuntu 9 bold, menu is Ubuntu 9 and terminal is Ubuntu Mono 9.
This is after updating Artful's libfreetype 2.8.0 to 2.8.1 from Michael Marley's PPA."
1722508,2017-10-26 07:37:49 UTC,You may want to report the problem upstream to make some progress:
1722508,2017-10-26 08:06:23 UTC,"In the meantime the problem has been narrowed down to QFont::toString() appending too much fontstyle information.
https://bugs.kde.org/show_bug.cgi?id=376630
https://bugs.kde.org/show_bug.cgi?id=378523"
1722508,2017-10-26 09:48:51 UTC,"Yeah, I'm not sure what progress could be made at this point.
The way I see it, the issue was resolved in a new version of libfreetype (2.8.1). The only thing that is left is to propagate the fix to main Ubuntu repo."
1722508,2017-10-26 10:49:43 UTC,"No, only half of the problem was caused by libfreetype 2.8.0 (normal TT hinting) but should indeed be updated as soon as possible in Artful, the other part (bold/italics) is a Qt 5.9.x problem and needs some love from Qt."
1722508,2017-10-29 02:48:02 UTC,We can't update freetype to 2.8.1 in Ubuntu 17.10 because it will break Electron apps (LP: #1728329). But Ubuntu 18.04 LTS will likely get freetype 2.8.1 (or possibly a newer version).
1722508,2017-10-29 09:11:55 UTC,"Then, my advise would be to backport the TT hinting fix to 2.8.0 in Artful for all those not able to use 2.8.1 from ppa? Bionic is still a long way to go. Anyway, all is fine for me, so feel free to decide as you see fit..."
1722508,2017-11-01 10:50:57 UTC,"I can confirm this, originally thought it was a Java bug since that is the only place I've seen the issue - https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1729257"
1722508,2017-11-06 15:59:31 UTC,Downgrading to 2.6.3 from zesty (https://packages.ubuntu.com/zesty-updates/libfreetype6) fixed this *really* annoying issue for me.
1722508,2017-10-16 09:41:35 UTC,"I think I'm looking at a Qt problem, but still relevant for 17.10 as a whole I guess?
https://bugreports.qt.io/browse/QTBUG-63792"
1722513,2018-11-15 21:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1722513,2017-10-10 12:30:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1722513,2018-11-09 17:53:13 UTC,"Joseph Salisbury, can you please mark this for Bionic as well?
I see this remained for generic Ubuntu, but it affects all releases that use netplan."
1722513,2017-10-10 11:43:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722513,2018-11-15 20:36:44 UTC,Do we know if this is a regression?
1722523,2020-03-31 11:54:47 UTC,"Change abandoned by Spyros Trigazis (<email address hidden>) on branch: master
Review: https://review.opendev.org/632721
Reason: The magnum team is cleaning up the backlog of changes older than 30 days. Feel to restore your patch."
1722523,2018-01-15 13:11:45 UTC,"Sorry guys, I done with Magnum. I hope someone with finish this trivial fix."
1722523,2018-07-19 08:25:41 UTC,Can please someone pick up this and submit the patch?
1722523,2018-01-15 13:11:06 UTC,"Change abandoned by George Shuklin (<email address hidden>) on branch: master
Review: https://review.openstack.org/511190
Reason: I stopped working on Magnum some time ago. Anyone is welcomed to pick up this patch and continue."
1722523,2019-01-23 13:29:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/632721"
1722523,2017-10-11 09:16:51 UTC,"Change abandoned by George Shuklin (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/510908
Reason: I used a wrong branch. That was a mistake."
1722523,2017-12-19 18:36:56 UTC,"Hi folks,"
1722523,2017-10-10 12:51:23 UTC,"etcd_volume_size was added for fedora in [1] but not to coreos, should be added."
1722523,2017-10-10 12:35:38 UTC,N.B. Fedora-atomic images works fine.
1722523,2017-10-10 15:45:08 UTC,https://review.openstack.org/#/c/510908/
1722523,2017-10-11 09:15:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511190"
1722523,2017-10-10 15:07:47 UTC,I've adopted those changes to coreos driver and it worked. I'll try to send them to upstream.
1722526,2019-09-19 14:49:28 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1722528,2017-11-05 21:41:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722528,2018-01-28 20:43:00 UTC,Can we please get this bugfix into artful?
1722530,2017-10-10 13:37:02 UTC,This patch crosses Base-7.0 submodules and contains my initial experiment.
1722530,2017-10-12 08:35:39 UTC,"As someone who has thought about use of timing systems in data acquisitions, having a 64-bit tag simply to enable a life-of-facility odometer is not compelling.  When applied to secPastEpoch, the same argument suggests expanding to 64-bits unsigned.  I hope that this suggests some redundancy in these two ideas.  IMO, taking as a timestamp the time at which this counter ticks is more generally useful."
1722530,2017-10-16 16:22:52 UTC,"The epicsTimeStamp::secPastEpoch field is already unsigned so not subject to the 2038 overflow problem, and when it does hit its limit sometime after 2100 nobody should still be using CA (if they're still using EPICS). Since we don't *need* to change this (and we already have our own epoch so timestamp conversions are already required) I don't see a particular advantage to making that 64-bit."
1722530,2017-12-07 08:25:03 UTC,More input re the need for a 64bit userTag.
1722530,2018-02-26 18:23:36 UTC,"I'll try to summarize the technical part my thinking and discussions with Bruce Hill, and others in the past few weeks."
1722530,2018-02-26 20:53:50 UTC,"> C) Add another field (eg. UTAG) to dbCommon.
> ...
> except that TSEL=.TIME handling is straightforward.
"
1722530,2018-02-26 21:06:06 UTC,This sounds like adding a *lot* of complexity (i.e. risk) for implementing a feature that is required by what percentage of our users?
1722530,2018-02-26 22:49:50 UTC,"> I'm not convinced ""straightforward"" is quite the right word.
"
1722530,2018-02-26 23:59:03 UTC,"Ralph: I agree, but with pvAccess providing a user-tag I'm happy to at least consider what would have to be done to support it properly in the IOC database. I assume Michael is being asked to do something like that by SLAC. Other sites with pulsed machines may want to attach tags to their timestamps but just haven't asked, so we don't really know where this might be used if it was available."
1722530,2018-02-28 05:29:27 UTC,"Yes, our LCLS2 timing requirements specify a 64bit pulseId, so we're looking at
how to satisfy that requirement.   We'd like to be able to use the pvAccess userTag
instead of having to add it as an additional field via V4."
1722531,2018-05-09 17:55:29 UTC,This has been been fixed in curtin:
1722531,2019-09-19 12:04:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1722532,2019-09-19 12:04:52 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1722532,2017-10-10 20:57:43 UTC,An easy way to implement this would be to modify curtin to output the version to the install log.
1722534,2021-01-08 08:00:23 UTC,what can i do to get someone assigned
1722534,2021-01-11 13:35:06 UTC,@ddstreet (now subscribed) - I know you look for src:vlan is this something you have more context about?
1722534,2021-01-12 22:33:49 UTC,"oh my, ifupdown/vlan is still in use?"
1722534,2021-01-12 22:36:42 UTC,"to be clear, this could arguably be considered a bug (that ifupdown/vlan doesn't correctly handle the magic auto-vlan-id detection for qinq, even if the vlan-raw-device is specified), but as we no longer support ifupdown/vlan, i don't think Ubuntu is the place to fix this; if it would be fixed at all, it should be reported to, and fixed by, Debian."
1722534,2021-01-12 23:20:55 UTC,OK I see your points... It makes me sad. systemd.networkd is a mass and not useful for my requirements.
1722534,2021-01-13 15:26:21 UTC,"> And I really do need a config file per group of links and bridges and IPs.
> Currently I dont see a way to implement this with systemd.networkd.
"
1722535,2017-10-10 13:51:56 UTC,"Yes, I know.
It's on my list of things to fix - somewhere in the middle."
1722535,2017-10-12 08:09:12 UTC,"More importantly I just noticed that it also removed my $(TOP)/configure directories, which IIRC you had already discovered and reported."
1722535,2018-11-05 06:30:31 UTC,I believe this was fixed at some point prior to 7.0.1 .
1722535,2018-11-05 15:23:30 UTC,"Ha, I need to qualify this (really I just didn't read ""inside submodule').  I no longer see this issue because it has been superseded by another."
1722535,2018-11-05 23:42:35 UTC,"What should 'make realuninstall' do to the install directories (bin, lib, dbd, cfg, include etc.) when run in a sub-module? Deleting just the files that this sub-module installs is not an option (without a *lot* more work tracking installed files so they can later be uninstalled). The distclean target depends on realuninstall so that's why I'm asking about realuninstall."
1722535,2019-05-13 22:37:27 UTC,This was fixed with e92a9ae and included in the 7.0.2.2 release
1722535,2019-05-13 23:11:59 UTC,"Hi Mark,"
1722537,2017-10-10 13:58:21 UTC,Update: I fixed this by manually switching branch for magnumclient repo to stable/pike and running sudo python setup.py install. IMHO it should be done by devstack or magnum (both were pinned to stable/pike).
1722537,2017-10-10 15:29:42 UTC,to clarify this is a bug when using service pike and client master/queens
1722537,2017-10-10 15:41:18 UTC,Need similar patch for stable/pike: https://review.openstack.org/#/c/472550/
1722538,2019-09-19 11:59:41 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1722540,2017-10-12 08:02:12 UTC,If you want an ao record to stay invalid after processing when nothing explicitly sets its VAL field you can set that VAL field to NaN in the DB file. We could change the default value of VAL to be NaN but I'm not sure if that would be a good idea at this point.
1722540,2017-10-12 08:40:54 UTC,So in aoRecord.c you're proposing to change all:
1722540,2017-10-12 11:50:24 UTC,"Re Michael: not in all places, only when val was not written to by anything."
1722540,2017-10-16 15:48:05 UTC,So is the real issue that inside ao::process() the statement
1722540,2017-10-11 08:35:22 UTC,I'm not sure I agree.  Processing w/ VAL=0 (the default) should clear UDF.  I know I created DBs which depend on this.
1722540,2017-10-12 07:33:45 UTC,Hm.
1722542,2017-10-10 15:34:02 UTC,"Onboard uses the system's at-spi2 framework to get information about newly focused text inputs. However, this requires the applications to also make use of the at-spi2 framework so that Onboard gets informed about their events, like the focussing of a new text input."
1722547,2017-10-10 14:38:50 UTC,May be problem is more complex because it's impossible to keep simultaneously installed different versions of raspberry-kernel.
1722548,2017-10-10 14:44:21 UTC,One of the fixes will be to the file:  openstack/murano-pkg-check/blob/master/muranopkgcheck/validators/ui.py
1722548,2017-11-22 07:04:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522142"
1722552,2017-10-20 01:01:10 UTC,"pushed https://review.rdoproject.org/r/10209, WIP at the moment. testing in promoter server"
1722552,2021-02-19 15:51:37 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1722554,2017-10-17 16:35:41 UTC,We are contacting <email address hidden> for suggestions here as the community doc is unclear.
1722554,2017-10-23 10:34:52 UTC,Docker has not replied yet. We emailed also openstack-dev community
1722554,2017-10-23 16:23:32 UTC,"Even kolla_docker is using docker-py. Docker-py interacts with the local engine API not with the registry API. I'm not sure anymore where to put the code that will deal with registry. Doing it in ansible is too complicated, we have to cycle over every tag of every image, apply the criterias to select an image to remove, end then delete. Ansible is not really good at these kind of loops.
If we do it in python, either we put it in kolla docker,  and the we have to depend on kolla, or we create a module on our own"
1722558,2019-03-05 13:18:43 UTC,Is this still an issue?
1722560,2017-10-16 15:35:46 UTC,"commit 74bf8771d7dd639ee2100ffa5782263f5a4ab2aa
Author: Krunal Bauskar <email address hidden>
Date:   Wed Oct 11 18:46:47 2017 +0530"
1722560,2018-01-18 08:38:51 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-878
1722564,2017-11-29 19:09:03 UTC,I installed the version of apport from xenial-proposed and can confirm that choices greater than 9 now work.
1722564,2017-12-07 17:56:58 UTC,This bug was fixed in the package apport - 2.20.7-0ubuntu3.6
1722564,2017-12-07 17:56:24 UTC,This bug was fixed in the package apport - 2.20.4-0ubuntu4.9
1722564,2017-12-07 17:56:00 UTC,"The verification of the Stable Release Update for apport has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1722564,2017-12-07 17:55:53 UTC,This bug was fixed in the package apport - 2.20.1-0ubuntu2.14
1722564,2017-12-06 20:48:58 UTC,"The question regarding ""cloud vendor or environment"" is a couple of questions deep and I had to use single character responses to the preceding questions to get to it."
1722564,2017-12-06 13:59:07 UTC,"Full disclosure, As you can see, I ran with artful and xenial (just copied and pasted text from above). I didn't run with zesty."
1722564,2017-12-06 13:57:06 UTC,"Robie, Brian,
I went ahead and did the reproduce in the test and selected '2' in the multi-select. Heres the full console log.  My responses can be seen there alsol."
1722564,2017-12-06 11:46:50 UTC,"Brian, when you verified these, did you also check that single digit choices can also be selected as expected? Seems to me that code path has regression potential here."
1722564,2017-11-29 19:17:04 UTC,I installed the version of apport from artful-proposed and can confirm that choices greater than 9 also work there.
1722564,2017-11-29 19:14:27 UTC,I installed the version of apport from zesty-proposed and can confirm that choices greater than 9 now work.
1722564,2017-11-28 23:11:39 UTC,"Hello Scott, or anyone else affected,"
1722564,2017-11-28 23:12:09 UTC,"Hello Scott, or anyone else affected,"
1722564,2017-10-11 21:56:54 UTC,For reasons unknown to me apport-cli only reads one character.
1722564,2017-10-18 18:34:52 UTC,"Thanks for looking at this Chad. Are the variable name changes, l to s, just to make things work better with ipdb?"
1722564,2017-11-28 23:10:35 UTC,"Hello Scott, or anyone else affected,"
1722564,2017-10-19 20:55:07 UTC,"An upload of apport to artful-proposed has been rejected from the upload queue for the following reason: ""Could we, I dunno, have consistent behaviour regardless of input length and number of choices?  This is about as user-friendly as something that's not very user-friendly.""."
1722564,2017-10-24 15:35:57 UTC,"Ahh brian, sorry for this delay here, I forgot to subscribe to the bug. So those variable changes where actually because I had update apport on a zesty machine but accidentally diffed against xenial  source. I'll put up an official upstream apport merge proposal and link it here so we can proceed with a discussion."
1722564,2017-10-24 16:05:09 UTC,"On Tue, Oct 24, 2017 at 03:35:57PM -0000, Chad Smith wrote:

> Ahh brian, sorry for this delay here, I forgot to subscribe to the bug.
> So those variable changes where actually because I had update apport on
> a zesty machine but accidentally diffed against xenial  source. I'll put
> up an official upstream apport merge proposal and link it here so we can
> proceed with a discussion.
"
1722564,2017-10-19 20:25:31 UTC,Is the cloud-init apport hook being SRU'ed? If so then I'll also get an SRU for apport started.
1722564,2017-10-24 17:47:36 UTC,"Just tested on artful both above and below the prompt choice threshold of 10 and bug reporting works.  Input of ""9<enter>"" for single digits choices versus ""13<enter>"" for multi-digit choices both work now for choice prompts with long lists. Short choice list prompts retain their single character responses."
1722564,2017-11-09 18:37:52 UTC,"Hello Scott, or anyone else affected,"
1722564,2017-11-11 23:02:27 UTC,This bug was fixed in the package apport - 2.20.7-0ubuntu4
1722564,2017-11-17 18:41:46 UTC,The artful upload was superseded by a security upload. I'll get this SRU'ed shortly.
1722564,2017-11-28 15:41:00 UTC,These are now in the SRU queue again and awaiting review by a team member of mine.
1722564,2017-10-24 17:03:30 UTC,"Yeah that feels like a premature optomization as that limits your interface options significantly (to only 9 valid choices). I'm suprised there haven't been any other bugs related to this, but maybe there aren't a lot of cli use-cases out there with complex bug-reporting choices.
I've attached a branch that now readlines instance or read(1) for prompts which contain a large set of choices (> 10)."
1722564,2017-10-18 18:04:21 UTC,"This quick fix worked on my side http://paste.ubuntu.com/25715415/
allows for two char reading if choices> 10"
1722570,2017-10-11 01:16:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722570,2017-10-18 23:50:43 UTC,I'm fairly certain that this behavior did change at some point in the 17.10 process -- I believe that I used to be able to long-press the Super key and have the numbers show up.
1722570,2017-10-19 00:15:52 UTC,"For more information, I opened an bug with GNOME on this some time ago: https://bugzilla.gnome.org/show_bug.cgi?id=788159"
1722570,2017-10-19 07:08:35 UTC,"> Also, for reference, you can bring up the numbers by pressing Super+Q.
"
1722576,2017-10-13 17:31:32 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1722576,2018-09-22 18:06:54 UTC,"Note that this has been fixed upstream in [0], when the next xdg-desktop-portal-kde release is made upstream and is then imported into Ubuntu this should be fixed."
1722576,2020-07-08 12:17:50 UTC,"I haven't tracked down exactly when the changes were merged/synced from Debian to Ubuntu, but I see the typo is gone in the 19.10 packages https://launchpad.net/ubuntu/+source/xdg-desktop-portal-kde/5.16.5-0ubuntu2. (Presumably fixed earlier, but definitely fixed :) )"
1722579,2017-10-10 16:06:09 UTC,"Using bisection, I've determined that this was introduced in the following xenial commit:"
1722580,2017-11-15 02:29:09 UTC,"> Juju should be able to import those 2 info with one command using just one concatenated file or tar ball containing those 2 files. So that OpenStack dashboard can offer a button ""Download Juju Environment File"" for Juju 2 as previously worked for Juju 1.x environments.yaml.
"
1722580,2017-11-15 22:46:07 UTC,We need to consider the best approach here. Moving to 2.3.1 milestone as any fix won't make the 2.3.0 release.
1722580,2018-01-10 03:52:08 UTC,"Nobuto, one thing you can already do is:"
1722580,2018-01-25 14:59:45 UTC,"@Andrew,"
1722580,2018-01-25 15:30:58 UTC,"Hmm, looks like this one still https://bugs.launchpad.net/juju/+bug/1722551 I'm using 2.3.2-xenial-amd64, but affected."
1722580,2018-08-03 13:33:32 UTC,This request is partially addressed by https://github.com/juju/juju/pull/9015
1722580,2017-10-10 16:08:06 UTC,"cross-linking:
https://bugs.launchpad.net/cloud-archive/+bug/1714985"
1722580,2017-10-22 23:44:39 UTC,I think a good approach here is to have the add-cloud command be extended to look for an optional credentials stanza in the clouds.yaml file and import any credentials whose cloud matches the cloud that was added.
1722603,2017-10-10 19:07:26 UTC,apport information
1722603,2017-10-10 19:07:27 UTC,apport information
1722603,2017-10-10 19:07:29 UTC,apport information
1722603,2017-10-10 21:04:12 UTC,Would it be possible for you to run the following command from a terminal and attach the output(The lshw.out file):
1722603,2017-10-10 19:27:29 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1722603,2017-10-11 03:07:58 UTC,We should wait for the driver author to upstream the his work.
1722603,2018-07-24 09:35:16 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1722603,2017-10-10 19:07:31 UTC,apport information
1722603,2017-10-10 19:07:24 UTC,apport information
1722603,2017-10-10 19:07:18 UTC,apport information
1722603,2017-10-10 19:07:22 UTC,apport information
1722603,2017-10-10 19:07:23 UTC,apport information
1722603,2017-10-10 18:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1722603,2017-10-10 19:07:08 UTC,apport information
1722603,2017-10-10 19:07:10 UTC,apport information
1722603,2017-10-10 19:07:16 UTC,apport information
1722603,2017-10-10 19:07:12 UTC,apport information
1722603,2017-10-10 19:07:14 UTC,apport information
1722603,2017-10-10 19:07:15 UTC,apport information
1722603,2017-10-10 19:07:20 UTC,apport information
1722603,2017-10-10 19:07:11 UTC,apport information
1722639,2017-10-10 20:27:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1722639,2017-10-11 03:32:47 UTC,"I'm really not sure how to file a bug against Artful (17.10) rather the current stable version. I only found that I could add the ""artful"" tag to this bug report. Please is there any way to specify which Ubuntu version the bug is files against? Many thanks"
1722639,2017-10-19 13:33:21 UTC,This doesn't seem to have anything to do with the installer.
1722639,2017-10-25 00:34:31 UTC,"@Phillip Susi, should I lodge the bug report again? If not installer related please what package is responsible for this?
The very same behavior is reproducible on a Dell E6530 Latitude laptop. In this case I used the final released iso of 17.10 (and even choose ""download updates during install"")."
1722639,2019-11-23 16:52:05 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1722639,2020-01-23 04:19:19 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1722642,2017-10-11 10:14:46 UTC,"Hi,"
1722645,2017-10-10 22:01:05 UTC,"not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1722645,2017-10-11 13:20:46 UTC,"Reproduced crash/freeze on Win 8.1-64bit Inkscape 0.92.2 (5c3e80d, 2017-08-06). As noted above, removal of the bitmap allows the file to open."
1722645,2017-10-11 13:54:01 UTC,"„Did you receive a dialog window with
the heading ""Convert legacy Inkscape file""?“"
1722645,2017-10-13 01:28:26 UTC,"I located the single object using the sand bitmap in a pattern (rect11211), and changed its fill to solid. After the change, cleaning the document removed ~376 unused defs."
1722645,2017-10-13 01:43:41 UTC,"Tested another legacy document with sand pattern fill; opened without issue in  Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1-64bit."
1722645,2017-10-16 12:46:18 UTC,"I just wonder, why there is a sand pattern in this document. There
should be only plain colours. I didn´t put any special pattern in this
drawing!"
1722645,2017-10-11 11:48:51 UTC,"I'm the 'Linux' from the above report. First, memory usage soars, and then, after a couple of minutes, Inkscape loads half the file... Then it says 'Window not responding', then just closes. After this, I wasn't able to use the cursor of my mouse (clicking works, cursor doesn't appear, also cannot type). Switching VT didn't help, I never got a command prompt. Needed to hard-reset computer to get a normal behaviour again. After removing the 'sand' bitmap, the drawing worked again. 'Clean up document' did not remove unused patterns."
1722645,2017-10-11 11:49:23 UTC,(Cursor as in 'text cursor')
1722651,2017-10-11 05:21:42 UTC,"Hi, can you please provide the steps to restore the backup. Kindly upload the xtrabackup restore log if it is still available. Did you change file permissions after restoring the backup?"
1722651,2017-10-12 22:57:33 UTC,Restore steps are -
1722651,2017-12-11 12:47:28 UTC,Thank you for the feedback.
1722651,2017-12-11 23:46:31 UTC,"- same on both source and destination (5.6.28)
- size 160K
- same configuration on both. Attaching the configuration."
1722651,2018-01-25 09:38:40 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3748
1722652,2017-10-10 21:20:18 UTC,This appears to be similar to https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1693809 but focused purely on the incorrect password aspect.
1722675,2021-01-07 04:04:41 UTC,4.8 EOL
1722675,2018-05-15 14:50:01 UTC,This change was made by a bot.
1722685,2017-10-11 04:26:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1722689,2020-03-05 13:48:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722701,2017-10-11 03:23:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511095"
1722701,2017-10-11 19:06:41 UTC,I guess there's a need for saving that 0.2 second. I think it's okay to add a whitelist since we already have a blacklist. Please set a default value for OPENSTACK_NOVA_EXTENSIONS_BLACKLIST setting on local_settings to uncover this hidden gem :)
1722701,2017-10-17 21:45:17 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/511095
Reason: Abandon based on feedback."
1722706,2017-10-11 04:25:59 UTC,Core and agent binary is copied to: /cs-shared/bugs/1722706
1722706,2017-10-24 04:28:54 UTC,Crash was seen in private binary. Fixed with https://review.opencontrail.org/#/c/36716/
1722713,2017-10-11 06:50:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722713,2018-04-08 10:43:06 UTC,"Actually in my case it doesn't just spam the log but prevents the app (Sloeber Arduino IDE, eclipse-based) from running (when starting it with GTK2 (env SWT_GTK3=0, due to a HiDPI bug with GTK3):"
1722716,2017-10-11 06:58:04 UTC,"Hi Jan,"
1722720,2018-12-01 08:10:04 UTC,"Reviewed:  https://review.openstack.org/571899
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f0678b9b0965dae1ab340cd7dd9805eca1ea6e7f
Submitter: Zuul
Branch:    master"
1722720,2018-12-11 21:13:53 UTC,"Reviewed:  https://review.openstack.org/623251
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=100f842cdf82355f3d597e955e8fc17f7ef4fbe8
Submitter: Zuul
Branch:    master"
1722720,2018-12-06 16:38:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623251"
1722720,2018-12-01 20:41:54 UTC,"Reviewed:  https://review.openstack.org/586719
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=5da7333450dcee518b43bddb755d579e34bf271d
Submitter: Zuul
Branch:    master"
1722720,2018-11-29 19:36:18 UTC,"Change abandoned by Hongbin Lu (<email address hidden>) on branch: master
Review: https://review.openstack.org/620425
Reason: I have to re-spin the parent patch (https://review.openstack.org/#/c/571899/) so I incorporate releasenote there and drop this patch."
1722720,2018-02-28 11:09:02 UTC,"I'd use a separate attribute for this (like propagate_uplink_status ? or something like that), It's not admin state itself (which is something that the admin enforces)."
1722720,2018-06-06 13:28:00 UTC,"Reviewed:  https://review.openstack.org/571821
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=1f7d11cd9fcb1bb8a62dbce8951569b1147987c6
Submitter: Zuul
Branch:    master"
1722720,2018-06-01 22:47:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571899"
1722720,2018-06-01 20:37:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571821"
1722720,2018-06-01 16:01:11 UTC,"This RFE was approved in Dublin. Please see ""ML2 and Mechanism drivers"", first bullet in the Dublin PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html"
1722720,2017-10-13 08:11:29 UTC,"That could be an approach. But it needs a SDN controller or other external component to monitor/set the date-plane-status, and also it takes more time to process the failure event. Comparing to that, letting the VF follow the status of PF seems a more straightforward way. Is there any drawback for adding the 'auto' as an option of admin_state_up only for SRIOV VF port?"
1722720,2017-10-11 08:10:03 UTC,There has been added a port data plane status - https://specs.openstack.org/openstack/neutron-specs/specs/pike/port-data-plane-status.html
1722720,2018-11-27 23:55:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620425"
1722729,2018-05-17 07:14:02 UTC,"I test this questions on devstack with master version, all thing is ok."
1722740,2017-10-11 09:00:09 UTC,This change was made by a bot.
1722740,2017-10-11 19:00:07 UTC,Does this issue go away if you boot back into the prior kernel version?
1722740,2017-10-12 08:27:04 UTC,I won't be able to get to this before the weekend due to other commitments.
1722740,2017-12-12 04:17:24 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1722740,2017-12-24 18:14:06 UTC,Also happens to me very regularly with 32-bit ubuntu 17.10 on an AMD machine (AMD Turion(tm) II Neo N40L Dual-Core Processor)
1722763,2017-10-11 12:29:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1722771,2017-10-12 11:09:31 UTC,"Reviewed:  https://review.openstack.org/511209
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0184bb4798dd4660182062fe4099a07e63dd90e8
Submitter: Jenkins
Branch:    master"
1722771,2017-10-11 11:06:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511209"
1722778,2018-09-24 07:00:00 UTC,"I am having the exact same problem Bionic 18.04 x64 system kernel 4.15.0-34-generic
.
I have just had too hard reboot the system to regain control after waiting a hour of thrashing. All input devices are locked.
As my system has too remain up all day this issue needs to be resolved to avoid HDD damage."
1722778,2018-11-16 00:36:41 UTC,"Solved on my system:
On lower spec systems (4GB RAM) the default swap file in /dev/dm-1 of 1GB is insufficient."
1722778,2018-02-20 14:15:18 UTC,"Seems to be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408
Memory management issues since a commit on a kernel revision somewhere for 4.11 or 4.12. I'm sticking to 4.10.0-28 until resolved"
1722778,2019-01-22 02:50:59 UTC,I am using btrfs for both / and /home. I was originally using it only for /home (and ext4 on /); but force-resetting due to this bug would occasionally render my system unbootable.
1722778,2019-03-03 11:42:58 UTC,"I have issue and my root partition is ext4. `mount` is full of other crap I don't understand but I don't think any of it's ""real"" drives."
1722778,2018-12-11 22:51:19 UTC,"Just out of curiosity, who's is using btrfs. It doesn't matter whether you have /home or / on btrfs. I am not certain whether it plays any role, but it seems to be the common denominator in my tests."
1722778,2018-01-25 19:29:38 UTC,I tried 4.15 rc9 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/ but it still has the problem (I just waited 15 minutes before the magic sysrq sequence but I think that's enough ).
1722778,2017-10-11 12:00:10 UTC,This change was made by a bot.
1722778,2017-11-03 06:02:27 UTC,"> On 3 Nov 2017, at 12:40 PM, jeremy-list <email address hidden> wrote:
>
> I have tried a few different swappiness values.
> 60: The problem will happen about three times per day
> 10: The problem will happen about once per hour
> 90: The problem will happen about once per day.
"
1722778,2017-10-11 18:59:26 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1722778,2017-10-12 02:36:20 UTC,"My computer cannot boot the v4.14-rc4 kernel because the amd64 package is a failed build and my motherboard does not support 32 bit operating systems.
Running the v4.14rc3 mainline kernel I was unable to connect to the internet, (so could not get firefox to use enough memory to reproduce the bug), but the attached C++ program made my computer become completely unresponsive in under a second."
1722778,2017-11-03 01:13:49 UTC,Any chance of progress being made on this bug? It's become quite rare for me to get a full day of system uptime!
1722778,2018-01-24 08:09:07 UTC,"Since this bug appeared when I upgraded from zesty to artful, I reverted to 4.10.0-37 (the last kernel I had in zesty) and it had been rock-solid (it becomes unresponsive from time to time but it recovers in a few seconds).
With each kernel upgrade I try the new one but the problem is still there (though I did not try 4.13.0-31, but I don't see anything in its changelog regarding this bug).
I also tried the BFQ scheduler, (as suggested to me here  http://ubuntu.5.x6.nabble.com/Bad-memory-swap-management-in-17-10-td5160226.html) but it didn't resolve the issue.
Regarding the previous comment than ""4 GBs ram is quite small"", 4.10.0 manages quite well the same workload (I have 8Gb but four are eaten by virtualbox)."
1722778,2017-11-03 03:28:11 UTC,"Once it has happened there is no way to check RAM usage because keyboard, mouse, and network devices all become completely unresponsive. I have 3.8 GiB of RAM installed. On the occasions when I have checked RAM usage shortly before it happened: total RAM usage was 3.8GiB. I have 19.1GiB of swap space enabled, but this problem will happen when swap usage is still around 10MiB."
1722778,2017-11-03 03:47:18 UTC,What's your swappiness value?
1722778,2017-11-03 04:40:30 UTC,"I have tried a few different swappiness values.
60: The problem will happen about three times per day
10: The problem will happen about once per hour
90: The problem will happen about once per day."
1722778,2017-11-03 02:58:13 UTC,How much ram does Firefox use when this happens?
1722799,2017-10-25 18:59:04 UTC,Regression testing with OpenStack tempest has completed successfully for xenial-pike-proposed.
1722799,2017-10-30 14:49:40 UTC,"This bug was fixed in the package openvswitch - 2.8.0-0ubuntu2~cloud0
---------------"
1722799,2017-10-30 14:49:38 UTC,The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1722799,2017-10-19 19:24:05 UTC,"Hello James, or anyone else affected,"
1722799,2017-10-18 10:22:26 UTC,"Reading logs between a successful run on x86 and a failed run on s390x, it would appear that stp never sees the topology change on br0 as p2 is removed - this log message is missing from the s390x logs:"
1722799,2017-10-19 10:18:20 UTC,"Hello James, or anyone else affected,"
1722799,2017-10-18 09:21:19 UTC,"Digging into this further, it would appear that the STP convergence is taking longer on s390x; if we time warp a further 30 seconds before checking the fdb table for br0, the entry for the removed p2 device has gone."
1722799,2017-10-18 10:28:22 UTC,That might be a red herring; however I do see:
1722799,2017-10-19 12:20:24 UTC,This bug was fixed in the package openvswitch - 2.8.0-0ubuntu2
1722799,2017-10-18 16:29:11 UTC,"Bumping priority - this is blocking other SRU activity which needs a clear runway; s390x ftbfs in artful and xenial today, so we need to get this resolved."
1722799,2017-10-18 12:17:21 UTC,I was able to reproduce this issue on 2.8.0 and 2.7.1 but not in 2.5.2; some bisection later pointed to:
1722800,2017-10-11 18:23:37 UTC,"This is (sort of) working as designed, but also an upstream bug.  Libguestfs doesn't
have transparent ZFS support upstream, because AFAIK it's not possible to just mount
a ZFS filesystem on a mountpoint."
1722800,2017-10-11 18:33:49 UTC,"BTW since this is not an Ubuntu bug, but is going to require actual upstream work, it may be better to discuss on the upstream list (https://www.redhat.com/mailman/listinfo/libguestfs).  If you wish you can post on the upstream list without needing to subscribe, although your first message will be delayed for a few hours in moderation."
1722800,2017-10-12 07:48:17 UTC,"Thanks Richard, I've sent an email to the mailing list as suggested. Fingers crossed that they'll support it :D"
1722800,2018-09-19 07:59:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722819,2017-10-27 10:54:58 UTC,Anyone reading this ????
1722819,2017-11-13 23:07:34 UTC,"Hi Paul -- Yes, however, filing a ticket here is a community support mechanism on an open source agent for a commercial product (Landscape).   You are not likely to get a response on this bug unless it intersects a large user base or has regressed from previous versions.  If you would like to get support from Canonical directly, you should contact support services: https://www.ubuntu.com/support."
1722827,2019-08-06 00:49:11 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Rogan and Meg!"
1722827,2018-11-30 19:38:40 UTC,"Tested rebuilt patch. Testing steps:  added record for online resource. First, added org unit in $9 with no trailing spaces. Confirmed correct OPAC display. Added trailing space after $9 (after org unit name). Refreshed OPAC display is correct. Removed trailing space after $9 and added it before the org unit name. Refreshed OPAC display is correct."
1722827,2018-09-14 14:50:21 UTC,rebuilt patch with upgrade and pgtap test
1722827,2018-08-15 00:35:53 UTC,"OK, did some testing tonight:"
1722827,2018-05-25 18:55:56 UTC,"I am seeing inconsistent behavior with this patch, and I haven't figured out a pattern yet on why it works sometimes, but not other times."
1722827,2018-05-23 19:40:51 UTC,"Actually, hold off on the signoff. I'm having trouble getting it to display too. I'll take a closer look."
1722827,2018-08-28 18:18:45 UTC,"OK, the issue is coming from the staff client.  Sometimes (especially when there is a second space) a nonbreaking space chr(160) is getting encoded which is kind of rude of it."
1722827,2018-05-23 14:21:41 UTC,All records that I tested had a first indicator of 4 and a second indicator of 0.
1722827,2018-05-23 19:30:57 UTC,"Nothing on the Sandbox changed, but maybe it was a cache issue. Sylvia, would you be willing to add a signoff in the following manner:?"
1722827,2018-03-22 13:39:03 UTC,"Hi Jane,"
1722827,2018-03-22 15:59:07 UTC,"Thanks for the branch, Rogan!  I think that we could add something to the documentation discouraging users from creating shortnames that have whitespace at the beginning or end."
1722827,2018-05-22 20:19:57 UTC,Tested on master.
1722827,2018-08-14 21:03:02 UTC,I'll take another look at it as well.
1722827,2018-05-23 13:19:21 UTC,"Adding a note that both Meg and Sylvia were using the same Sandbox, and I have verified that the changes in the branch were made to the biblio.extract_located_uris function."
1722827,2018-05-23 14:02:11 UTC,"Just to add a data point, the xpath requirement for a located URI is:"
1722827,2018-05-23 11:57:29 UTC,"I tested on Kathy's Sandbox with the same results.  I even tried importing a record with a space in the $9, and the 856 information was not visible until the extra space was deleted."
1722836,2017-11-02 19:18:19 UTC,"One thing to point out, currently sstream's publish does not need any special priviledges (just write access to a glance and optionally a swift)."
1722838,2017-10-13 12:46:09 UTC,"it is not recognizing the sdcards installed.  when i update to the
latest kernel it will recognize only small cards.  Both of my Sandisk 64
GB and 16 GB cards are not being recognized.  As far as the sound card
when I install the latest kernel it is recognized but still no sound
which i sent an email to the author of that codex u suggested"
1722838,2017-10-13 15:31:34 UTC,apport information
1722838,2017-10-13 15:31:33 UTC,apport information
1722838,2017-10-13 14:29:25 UTC,Please attach dmesg when you plug the mmc card under linux 4.14-rc4.
1722838,2017-10-11 20:56:23 UTC,I have been able to connect to a bluetooth speaker and after changing the mode to High Fidelity Playback was able to get sound.  so Bluetooth is working awesome
1722838,2017-10-13 12:30:04 UTC,What about the Sdcard slot not working correctly
1722838,2017-10-13 03:36:57 UTC,"There's no codec support for CX2072X.
The author of CX2072X support didn't resend a new patch to address also maintainer's concern [1]."
1722838,2017-10-12 13:34:10 UTC,kernel 4.14-rc4 installed sorry forgot to add to last post
1722838,2017-10-12 13:30:19 UTC,Kernel-Bug-Exists-Upstream
1722838,2017-10-13 15:31:36 UTC,apport information
1722838,2017-10-13 12:32:00 UTC,What about the not working Sd Card Slot
1722838,2017-10-13 15:32:30 UTC,apport information
1722838,2017-10-13 18:24:25 UTC,"Okay, can you attach acpidump [1]? Thanks."
1722838,2017-10-13 15:32:33 UTC,apport information
1722838,2017-10-13 15:32:53 UTC,"couldnt get 4.14-rc4 to load and 4.14.rc3 the wifi wasnt working so the
only one i was able to install and work properly is 4.13.6.  the Sandisk
64 GB card is reconized but the 16 GB card wont read"
1722838,2017-10-13 15:51:10 UTC,These are not useful. Please attach dmesg.
1722838,2017-10-13 16:18:03 UTC,"I tried to download 4.14-rc4 but something is going on at ur file
servers.  tried both through command line and Ukuu"
1722838,2017-10-13 16:35:43 UTC,this is dmesg when Sandisk 16 GB card in slot
1722838,2017-10-13 21:42:34 UTC,Ok here you go
1722838,2017-10-14 06:39:44 UTC,"[ 3945.831863] mmc1: card 21d1 removed
[ 3954.235097] mmc1: error -110 whilst initialising SD card"
1722838,2017-10-14 13:49:24 UTC,yes it sure did
1722838,2017-10-16 03:18:03 UTC,"Is there a way you all can check out this patched kernel which fixes the
sound for this laptop."
1722838,2017-10-16 04:28:41 UTC,The sdcard issue is a tricky one - it's hard to debug without physical access to the hardware. Linux mmc subsystem doesn't print much information.
1722838,2017-10-11 20:46:58 UTC,apport information
1722838,2017-10-13 15:32:32 UTC,apport information
1722838,2017-10-11 20:46:56 UTC,apport information
1722838,2017-10-13 16:28:08 UTC,Alright this is dmesg for 4.13.6
1722838,2017-10-11 20:46:52 UTC,apport information
1722838,2017-10-11 18:57:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1722838,2017-10-11 20:45:25 UTC,apport information
1722838,2017-10-11 20:45:27 UTC,apport information
1722838,2017-10-11 20:45:30 UTC,apport information
1722838,2017-10-11 20:45:31 UTC,apport information
1722838,2017-10-11 20:45:33 UTC,apport information
1722838,2017-10-11 20:45:34 UTC,apport information
1722838,2017-10-11 20:45:36 UTC,apport information
1722838,2017-10-11 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1722838,2017-10-11 20:45:38 UTC,apport information
1722838,2017-10-11 20:45:40 UTC,apport information
1722838,2017-10-11 20:46:54 UTC,apport information
1722838,2017-10-11 20:45:44 UTC,apport information
1722838,2017-10-11 20:45:42 UTC,apport information
1722838,2017-10-11 20:45:47 UTC,apport information
1722838,2017-10-11 20:45:50 UTC,apport information
1722838,2017-10-11 20:46:36 UTC,apport information
1722838,2017-10-11 20:46:38 UTC,apport information
1722838,2017-10-11 20:46:40 UTC,apport information
1722838,2017-10-11 20:46:41 UTC,apport information
1722838,2017-10-11 20:46:43 UTC,apport information
1722838,2017-10-11 20:46:45 UTC,apport information
1722838,2017-10-11 20:46:46 UTC,apport information
1722838,2017-10-11 20:46:48 UTC,apport information
1722838,2017-10-11 20:46:49 UTC,apport information
1722838,2017-10-11 20:46:51 UTC,apport information
1722838,2017-10-11 20:45:45 UTC,apport information
1722841,2019-06-07 20:25:14 UTC,Pike and Ocata are now EOL
1722841,2018-12-05 17:09:49 UTC,Raise new bug for the timeout issue at https://bugs.launchpad.net/tripleo/+bug/1806966
1722841,2018-12-05 17:07:12 UTC,"Ok, so this message is just a warning and not the real cause of deployment failure. We shoul try to make it obvious that is just a warning and preferably eradicate it anyway."
1722841,2018-12-05 16:00:18 UTC,I see a huge number of failures with a similar message at:
1722841,2017-10-12 14:49:54 UTC,My environment is libvirt.
1722841,2017-10-12 07:05:56 UTC,"@Aneesh, thanks for report. Please note that featureset007 is running on multinode and it's not supported in any other environment - ovb or libvirt. It runs only on CI.
Which environment do you run it?"
1722841,2017-10-11 16:52:07 UTC,the tripleo-quickstart project should not be used
1722841,2018-12-05 16:39:49 UTC,that disable_upgrades_deployment flag error on master in the reference on comment #4 above [1] is non fatal afaik and the flag itself isnt' used since queens (i'd have to confirm or P maybe).
1722847,2017-10-13 12:54:55 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/511832"
1722847,2017-11-07 16:51:39 UTC,"Reviewed:  https://review.openstack.org/511832
Committed: https://git.openstack.org/cgit/openstack/cloudkitty/commit/?id=f7f800f10d289d6ee1c0f913c18522ba20e02cea
Submitter: Zuul
Branch:    stable/ocata"
1722849,2018-01-23 14:21:15 UTC,"This seems to have been fixed in newer gcc (tested with gcc 7.2 on godbolt.org).  It is difficult to be sure, since the bug is triggered by particular combinations of code and flags (I think you need just the right amount of register pressure in just the right place).  But at least for this code and for a variety of flags I could not provoke this incorrect code generation."
1722849,2017-10-23 06:49:34 UTC,"I think the -O1 is an interesting detail, but probably not an important one.  Certainly if there is no optimisation (-O0), code rarely moves around and the issue does not arrive.  The bug in gcc means that the volatile asm /can/ move around - not that it has to be moved.  Once it is free to move, the actual code generated will depend on the details of the generated code, and in particular, on the register pressure.  These details will vary for different combinations of the code surrounding the problem area, and the optimisation choices.  It appears to be just luck that this particular combination of code (and register usage) before the loop, and these particular flags, happens to result in a bad move.  Changing apparently irrelevant details in the code also stop the problem appearing - and I expect that if you have enough trials with different code combinations, you will also be able to find examples of the bug with -Os, -O2, -O3, cortex-m4, and other variations of the flags.  But you'd need plenty of patience, as combinations that trigger a dangerous move are rare."
1722849,2017-10-23 03:46:11 UTC,"An IMHO important detail is that this issue is only seen with -O, which is the same as -O1.
The issue is not seen with -O0, -O2, -O3, -Os, -Ofast or -Og."
1722849,2017-10-18 11:12:29 UTC,I didn't spot the bug or report it - credit for that goes to Miro.  I just tested it and shuffled it around mailing lists.
1722849,2017-10-18 10:41:11 UTC,"Certainly, once the bug is committed to the stable GCC branches it'll make its way into the GNU Arm Embedded Toolchain. Thanks for reporting the issue David."
1722849,2017-10-18 10:24:54 UTC,"After some discussion in the gcc mailing list, one of the developers there declared it a bug in gcc - ""asm volatile"" statements can move across normal code, but not across other asm volatiles, volatile memory accesses, or other observable behaviour.  He filed an upstream gcc bug, and also posted a patch:"
1722849,2017-10-17 00:19:51 UTC,I have tested the new CMSIS_5 code (commit 3520562) with my test case (a bit more involved than the distilled version posted in the original description in #1) and it seems to work correctly.
1722849,2017-10-16 22:29:35 UTC,"I have written a post to the gcc-help mailing list, to try to get an opinion from the gcc developers on this issue."
1722849,2017-10-16 17:57:37 UTC,"Can anyone test this
https://github.com/ARM-software/CMSIS_5/issues/261#issuecomment-336912432"
1722849,2017-10-16 11:28:34 UTC,"I have had the questionable pleasure to implement or correct macros for critical sections on several target platforms, all with the help of GCC. My thoughts on the information collected in this issue so far:"
1722849,2017-10-16 13:04:57 UTC,"Memory clobbers can be costly, and may not necessarily do what you want anyway unless you have a matching dsb or dmb instruction (which can be even more costly).  On the Cortex M0, however, these instructions are unlikely to be needed.  But for a general critical section entry/exit macro, memory clobbers are not a bad idea to match user expectation."
1722849,2017-10-13 17:56:13 UTC,"Regarding the ""intrinsic"" functions for getting the PRIMASK or for setting/clearing the PRIMASK, I should have probably used the term ""builtin functions"" for the GNU-ARM, such as the collection listed at https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html. Unfortunately, the built-in collection has no functions for getting/setting the PRIMASK or for setting/clearing it."
1722849,2017-10-13 03:21:39 UTC,"> The answer is that the ""intrisic"" functions don't help and the bug persists.
You asked for intrisics, and I pointed you to where they were. Nobody claimed they would make any difference.
"
1722849,2017-10-12 16:44:17 UTC,"The latest comment by David Brown seems to address the real issue and seems to fix the problem in my experiments. This is an acceptable fix of this ""bug"" for me, although the issue is perhaps worth documenting to help others to avoid this pitfall in the future."
1722849,2017-10-12 14:03:28 UTC,"I agree that it is surprising that ""asm volatile"" statements can be re-arranged with respect to each other, and with respect to other volatile accesses.  This seems to be a particular problem with asm statements that return outputs - ""volatile"" is used primarily to tell the compiler that you can get different outputs at different times, even if the inputs (if any) are the same.  For asm statements with no outputs, the compiler appears to assume they have a special function and should not be moved."
1722849,2017-10-12 13:32:44 UTC,I think this is a bug in CMSIS. The __get_PRIMASK () intrinsic implementation in cmsis_gcc.h needs to have a memory clobber in the inline asm statement to prevent it from being reordered.
1722849,2017-10-12 13:22:38 UTC,Adding a clobber on memory does solve the problem on this particular testcase though.
1722849,2017-10-12 13:12:57 UTC,"I have tested the code with the ""intrinsic"" functions provided in the CMSIS (header file ""cmsis_gcc.h""):
__get_PRIMASK(), __disable_irq() and __set_PRIMASK()"
1722849,2017-10-12 03:41:50 UTC,"> why there are no intrinsic functions for this?
These are available in the ARM CMSIS: __get_PRIMASK(), __disable_irq() and __set_PRIMASK().
"
1722849,2017-10-11 17:05:13 UTC,"This is very interesting, I always thought myself that volatile acted as a code barrier. However the documentation [1] explicitely states that this is not the case:"
1722849,2017-10-16 15:09:36 UTC,"Interesting that there is a difference between one and several asm statements, but without a clear statement in the GCC manual I would not dare to rely on that fact for any functionality. Of course the ""memory"" clobbering is a vital part of this solution. Since I have seen way too many bugs related to not having the ""memory"" clobbering in general critical section macros they are a must have to me, and they do take care of the ordering in a guaranteed way on simple targets."
1722850,2018-04-09 14:00:36 UTC,"Reviewed:  https://review.openstack.org/511636
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=37b85b6a399dba120de49d9056529852b2284793
Submitter: Zuul
Branch:    master"
1722850,2017-10-12 22:36:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511636"
1722850,2017-10-25 16:05:30 UTC,This was mentioned in the Denver PTG (Sept 2017) [1]:
1722850,2017-10-25 16:45:05 UTC,"Vasyl raised a good point, should we remove the ability to attach vifs via a port or port group's .extra['vif_port_id'] if the API version is < 1.28."
1722851,2019-09-19 12:04:54 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1722857,2020-09-26 16:55:53 UTC,"That sounds surprising ... according to the source code:
https://git.qemu.org/?p=qemu.git;a=blob;f=hw/usb/hcd-xhci.c;hb=v5.1.0#l3386
... QEMU already sets 0x30 as programming interface byte there. Could you please double-check whether your problem still occurs with the latest version of QEMU?"
1722857,2020-11-26 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1722871,2019-03-05 13:20:37 UTC,Is this still needed?
1722872,2017-10-11 17:59:00 UTC,I wonder if this is related to the mentioned version conflicts between UCA/mainline in http://lists.openstack.org/pipermail/openstack-dev/2017-October/123464.html
1722883,2017-10-11 19:26:04 UTC,"Also searching a bit, I found that: https://bugs.launchpad.net/ubuntu/zesty/+source/python2.7/+bug/1682934 looks similar"
1722884,2017-10-11 18:52:56 UTC,Here is a backtrace of the PS2 reset event:
1722884,2017-10-12 04:12:32 UTC,"Further to this, it appears to be a race condition with reading from the i8042 controller. I have turned on debugging of PS2 and KBD and filtered out the event that causes the issue. I have split the below up to show the valid reads for the mouse and then the sequence that triggers a reset when the keyboard is used."
1722884,2017-10-29 11:25:03 UTC,"I believe I am onto the cause of this issue, because the input events are coming from a multi threaded source (in my instance spice) keyboard and mouse input share common code paths without any thread interlocking."
1722884,2017-12-19 18:49:47 UTC,"This bug needs some attention, we just released Looking Glass which relies heavily on the relative input mode of SPICE which in turn relies heavily on the virtual i8042 controller. This project has the ability to completely eliminate the need to dual boot a Linux machine with windows and is gaining much public attention, if it wasn't for this bug it would be damn near perfect."
1722884,2020-02-21 09:15:39 UTC,I tried to look into this as well. One finding I have made is that the problem happens for -display gtk but not with -display sdl so I'm thinking it might not be reading of data from the ps2 controller that is problematic but the writing to it. I will need to investigate further.
1722884,2020-02-21 10:58:19 UTC,"I tracked this down and fixed it last year, your issue is unrelated."
1722884,2020-10-07 18:42:02 UTC,"Ok, so if this bug has been fixed, let's close this ticket."
1722886,2019-07-31 16:34:40 UTC,This bug was fixed in the package gnome-shell - 3.32.2-2ubuntu1~ubuntu19.04.1
1722886,2019-07-31 16:24:40 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1722886,2019-07-30 00:27:16 UTC,Verified here:
1722886,2019-06-27 21:12:22 UTC,This bug was fixed in the package gnome-shell - 3.32.2-2ubuntu1
1722886,2019-06-18 01:32:53 UTC,Yes it makes sense if the shell crashes then very likely you have no Xorg server to run xrandr against :)
1722886,2019-06-17 12:25:21 UTC,"Xrandr output is missing from logs currently, but in any case the configuration is something that we might try to apply anyways also outside X11, so better to have this anyways."
1722886,2019-06-17 01:54:31 UTC,I'm not sure monitors.xml is any more useful than the xrandr output we already get... unless xrandr output is missing from crash bugs?
1722886,2019-07-02 18:10:29 UTC,"Hello Marco, or anyone else affected,"
1722896,2017-10-11 21:37:06 UTC,"@Junien Fridrick (axino),"
1722896,2017-10-12 12:09:38 UTC,"I guess I can create a new user and update the credentials. I'll let you know how it goes. Also, I have updated the linked bug."
1722896,2017-10-13 18:46:56 UTC,Adding the tenant/user with the correct password allowed the model to be deleted. I still wish this would be a smoother process :)
1722896,2017-10-15 23:11:11 UTC,"We are looking at the requirements for cloud credentials management on a long-lived models. As part of this work, we will consider what to do / how to flag to the user(s) invalid or invalidated credentials."
1722896,2019-05-07 05:30:35 UTC,There are 2 parts to the fix here.
1722896,2019-05-08 15:49:18 UTC,"Isn't the model UUID that you see there the model that the controller is
running in, and not the model that is being processed? (we historically
have had a significant problem here, and its on the roadmap to work on
this.)"
1722901,2018-01-07 20:32:28 UTC,Fix commited to upstream: https://git.lxde.org/gitweb/?p=lxde/lxtask.git;a=commit;h=8274c99b34b0302a7f9c7a2bf33e38e4e61f82b1
1722901,2018-06-03 19:25:08 UTC,I don't know if it ever worked.
1722901,2018-01-03 09:30:46 UTC,Bug reported to upstream: https://sourceforge.net/p/lxde/bugs/889/
1722901,2018-01-02 21:48:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1722901,2018-01-04 16:37:41 UTC,"Looks like there's an upstream patch, too, if anyone wants to check that out."
1722904,2017-10-11 22:52:47 UTC,A better workaround is to go to the snap's +authorize page (e.g. https://code.launchpad.net/~snappy-dev/+snap/core/+authorize in this case).
1722904,2017-10-13 08:57:32 UTC,"The lost-email mystery is solved, at least:"
1722912,2017-11-15 20:34:53 UTC,Related juju bug: https://bugs.launchpad.net/juju/+bug/1722580
1722914,2017-10-17 21:57:54 UTC,From DpkgTerminalLog.txt:
1722914,2017-10-18 10:04:12 UTC,This is probably another mpd (or systemd socket?) already running. It would be useful if you could provide more detail on how you're starting mpd (initscript/systemd/as user/...) and whether this was really the first intall of mpd on your machine?
1722946,2017-10-24 12:25:28 UTC,Unable to reproduce with l2pop disabled; so guessing that the issue lies somewhere in the tunnel update code driven by l2pop rather than in the general tunnel_sync code used when its disabled.
1722946,2019-04-08 12:40:02 UTC,This might be related to bug 1823295 - I'm thinking that maybe the 3x restart of the underlying ovs daemons on package upgrade just causes confusion and dismay.
1722946,2017-10-24 12:52:34 UTC,Grepping the neutron-server logs - a good restart has:
1722946,2017-10-24 12:36:23 UTC,"When l2pop is enabled, the n-ovs-agent never makes the calls to setup_tunnel_port to reconfigure the tunnel flows AFAICT; this does not always happen so something must be getting wedged/raced."
1722946,2017-10-24 12:06:49 UTC,Worth noting that the deployment uses the l2-population driver; disabling and trying to reproduce without that
1722946,2017-10-16 16:34:46 UTC,Would be helpful to paste output of ovs-ofctl dump-flows br-int and br-tun to see whether the flows were implemented correctly or if the connectivity is dropped for other reason.
1722946,2017-10-24 10:06:44 UTC,Setting Neutron task back to new as flow data has been provided.
1722946,2017-10-24 10:18:15 UTC,This appears to be a bit tricky to reproduce; subsequent restarts of the openvswitch daemons does result in the br-tun flows being re-setup by the n-ovs-agent.
1722946,2017-10-24 10:02:49 UTC,flow dumps before and after restart.
1722946,2017-10-18 14:26:42 UTC,You can try adding 'drop_flows_on_start=True' to Your l2 agent configure file. Then when you restart l2 agent， it will try to drop all flows and rebuid them.
1722946,2017-10-24 10:04:29 UTC,br-tun looks incomplete from a flows perspective after the restart of the openvswitch daemons.
1722946,2017-10-24 10:06:21 UTC,"@wlw9001 the issue here is not a restart of the openvswitch-agent, but rather of openvswitch itself.  After a restart of the neutron-openvswitch-agent, flows are correctly restored - but that does not help with restarts of openvswitch itself."
1722948,2018-02-12 10:14:42 UTC,this problem it's in 18.04 daily
1722951,2017-12-07 08:57:28 UTC,"Reviewed:  https://review.openstack.org/517090
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=633998983c2bd69c003bc343ff65872440be5439
Submitter: Zuul
Branch:    stable/ocata"
1722951,2019-01-16 21:09:34 UTC,"Great, thanks John."
1722951,2019-01-16 20:38:23 UTC,I will be working on tagging older versions Soon
1722951,2019-01-16 20:02:24 UTC,"Hi Sam, do you know if there will be a 2.15.2 stable point release coming out that we can release for Ubuntu?"
1722951,2018-12-06 21:55:09 UTC,This bug affects ubuntu pike cloud archive version 2.15.1-0ubuntu3~cloud0
1722951,2017-11-13 09:16:21 UTC,This issue was fixed in the openstack/swift 2.16.0 release.
1722951,2017-10-16 20:06:00 UTC,"Reviewed:  https://review.openstack.org/511550
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=dc8da5bb194d0a544fb8065aa9a4c7484f605715
Submitter: Zuul
Branch:    master"
1722951,2017-11-03 20:15:25 UTC,"Fix proposed to branch: feature/deep
Review: https://review.openstack.org/517718"
1722951,2017-11-01 19:24:31 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/517090"
1722951,2017-10-20 16:00:36 UTC,"Reviewed:  https://review.openstack.org/513730
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=bb064f0b30ec083cec85e8371fe12824804779cf
Submitter: Zuul
Branch:    feature/s3api"
1722951,2017-10-20 12:54:34 UTC,"Fix proposed to branch: feature/s3api
Review: https://review.openstack.org/513730"
1722951,2017-10-12 18:42:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511550"
1722951,2017-11-04 00:25:37 UTC,"Reviewed:  https://review.openstack.org/517718
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=5c564e53966b74d6d7589c3505dd33816b3c19f1
Submitter: Zuul
Branch:    feature/deep"
1722951,2017-10-11 23:23:37 UTC,"The bug is real, but isn't PipeMutex's fault. We're letting eventlet pick the default hub sometimes. Eventlet chooses the epoll hub, and epoll doesn't play nicely with forking. (It's possible to use epoll and fork and still be correct, but eventlet doesn't make it so.)"
1722958,2017-10-29 17:05:04 UTC,@wpk http://paste.ubuntu.com/25845887/
1722958,2017-10-29 17:05:41 UTC,@wpk possibly it has something to do with https://bugs.launchpad.net/juju/+bug/1728432
1722958,2017-10-13 10:14:09 UTC,Could you show the result of 'ip a' on the machine?
1722959,2018-08-10 02:51:18 UTC,"MR sent, and the ci test passed."
1722959,2019-10-02 14:55:26 UTC,"This has been implemented, this bug can be closed."
1722959,2019-10-02 16:30:31 UTC,Go team!
1722973,2017-10-12 07:52:19 UTC,Here is the commit: https://github.com/percona/percona-xtradb-cluster/pull/554/commits/9b5b5aeecf5aaddfed1d881c4bdf2f1ce9cc5d47
1722973,2018-01-18 08:25:35 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1033
1722979,2017-10-12 03:21:40 UTC,"this only happen when one installed wireshark(and wireshark-qt) without installing wireshark-gtk, but wireshark-gtk is an optional dependency"
1722979,2018-09-15 14:45:24 UTC,What's the status of this bug?
1722979,2019-07-03 11:00:06 UTC,"Hi, can you still reproduce this issue? If so, what package and distro version? You can use this command to find out:"
1722979,2019-09-02 04:17:27 UTC,[Expired for wireshark (Ubuntu) because there has been no activity for 60 days.]
1722990,2017-11-29 10:49:51 UTC,"Hi Masood,"
1722990,2017-11-30 23:34:18 UTC,"Hi Afshan,"
1722992,2017-10-12 18:50:46 UTC,Any datasource that uses convert_vendordata is possibly affected.
1722992,2017-10-13 00:26:53 UTC,"After reading this comment, I still have a few question:"
1722992,2017-10-13 03:51:46 UTC,Added cloud.cfg for reference
1722996,2017-10-12 05:10:38 UTC,"Warning: Track node pin has invalid link 0 in C:\MSTS\OR_Simulator\ROUTES\DARv2R
2\DARv2.rdb:line 7137"
1723008,2020-10-05 07:12:14 UTC,The bright colours this bug was originally about are no longer in use.
1723026,2020-03-24 21:39:54 UTC,"According to comment #16 this RFE is only about ""adding device_id to the floating IP response"" and this is already done so I will mark it as fixed."
1723026,2018-06-18 15:20:13 UTC,"Change abandoned by Maksim Malchuk (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/576000"
1723026,2018-06-17 21:12:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/576000"
1723026,2018-04-28 17:07:12 UTC,"Reviewed:  https://review.openstack.org/533327
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c760d4f26f4b4753c80269437d2cd0b8f63dbc7c
Submitter: Zuul
Branch:    master"
1723026,2018-04-24 21:33:30 UTC,"Reviewed:  https://review.openstack.org/534882
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=24a0877d1d234830a36794388bb342d3d91b9230
Submitter: Zuul
Branch:    master"
1723026,2018-04-11 21:48:28 UTC,"Note: during the neutron driver meeting, we settled on comment #18 suggested by @Akihiro"
1723026,2018-04-06 17:29:17 UTC,This RFE was approved by the Neutron Drivers meeting.
1723026,2018-03-16 13:00:36 UTC,"In my understanding, the motivation of this RFE bug is now to retrieve floating IP information and associated port information in one API call. This sounds a reasonable request."
1723026,2018-03-08 01:55:48 UTC,"Yeah, thanks Hongbin."
1723026,2018-03-07 18:43:22 UTC,"As pointed by by Miguel, this bug proposes two features: (1) support filtering of floating IP address substring and (2) add device_id to the floating IP response."
1723026,2018-03-07 02:16:22 UTC,"So I think we still need to dicsuss and pursue the direction from Neutron driver core members in weekly driver meetings.
I will take part in the worklist then. :)"
1723026,2018-01-11 23:52:14 UTC,"For #2, I have the same question as @Miguel."
1723026,2018-01-25 20:58:34 UTC,To summarize:
1723026,2018-01-26 02:11:27 UTC,"Thanks, Miguel. That's correct."
1723026,2018-01-11 23:51:26 UTC,I can work on #1 if it is not taken. Please let me know.
1723026,2018-01-12 03:49:43 UTC,"Hi Miguel,"
1723026,2018-01-12 23:53:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533327"
1723026,2018-01-17 19:05:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534882"
1723026,2018-01-11 21:17:13 UTC,"Zhaobo,"
1723026,2018-01-22 22:16:00 UTC,Nova has deprecated all of it's floating IP related REST APIs because they are proxies to the networking service (neutron) and nova-network is deprecated. So this doesn't sound like something we'd add to nova unless I'm not understanding the request.
1723026,2018-01-22 22:18:40 UTC,"Rather than add more proxy filter parameters to the compute API like the ""ip"" filter in GET /servers, it seems like it would make more sense to add something like https://review.openstack.org/#/c/521683/ where you can filter ports with a floating IP address substring."
1723026,2018-01-22 23:35:56 UTC,"Zhaobo,"
1723026,2018-01-24 02:22:37 UTC,"Sorry for this late return, I will make it clear with zhenyu, you will receive the email from him later."
1723026,2018-01-18 23:28:48 UTC,"Zhaobo,"
1723026,2017-12-14 10:25:52 UTC,does the use case need some work on nova side as well?
1723044,2017-10-12 09:30:04 UTC,This change was made by a bot.
1723048,2017-10-12 09:42:36 UTC,"StacktraceTop:
 x_io_error (display=<optimized out>) at wayland/meta-xwayland.c:411
 _XIOError (dpy=dpy@entry=0x5639182992b0) at ../../src/XlibInt.c:1469
 _XReadEvents (dpy=dpy@entry=0x5639182992b0) at ../../src/xcb_io.c:400
 XIfEvent (dpy=0x5639182992b0, event=event@entry=0x7ffd5c228ac0, predicate=predicate@entry=0x7fdb9de51880 <find_timestamp_predicate>, arg=arg@entry=0x563918419200 ""\220\221P\030\071V"") at ../../src/IfEvent.c:68
 meta_display_get_current_time_roundtrip (display=0x563918419200) at core/display.c:1332"
1723048,2017-10-14 22:52:15 UTC,Seems to be fixed after the last update:
1723048,2017-10-14 22:55:27 UTC,"Forgot to add, #6 is about this scenario https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000 from a duplicated bug."
1723048,2017-10-17 00:40:03 UTC,"Jean-Baptiste,"
1723048,2017-12-07 18:38:18 UTC,Could you check if the patch attached to https://bugzilla.gnome.org/show_bug.cgi?id=789070  fixes the issue?
1723072,2017-10-12 15:39:21 UTC,"Crashing in this situation would not be ideal, but adding a log message about the fact that no config was found (or could be read) sounds reasonable."
1723088,2018-02-21 14:26:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1723088,2018-02-21 14:27:52 UTC,The issue should be reported on https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
1723089,2017-10-12 12:28:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1723089,2017-10-12 11:55:44 UTC,https://www3.lenovo.com/us/en/tablets/windows-tablets/miix-series/IdeaPad-Miix-700/p/88IPMX70637
1723096,2018-01-19 06:50:35 UTC,"Надо как-нибудь это исправить, но пока не критично. Там есть несколько типов движений для выбора уровня и они похоже конфликтуют."
1723105,2017-10-13 16:20:25 UTC,I was unable to recreate this issue:
1723114,2017-10-29 21:04:33 UTC,"Adding the ssh command-line option to support dss is certainly one solution but RouterOS has supported rsa since version 6.31 which was released Aug 14, 2015"
1723115,2017-11-27 19:25:54 UTC,"I've added bionic to the meta-release-lts-development file so the crash is no longer an issue, although it likely should be fixed."
1723117,2018-06-08 17:22:13 UTC,"In my system, the dock is set to hide automatically, but it does not hide and also partially covers the desktop icons. I'm using Ubuntu 18.04 64bit, everything up to date (gnome-shell-extension-ubuntu-dock version 0.9.1)."
1723117,2019-06-14 17:53:39 UTC,I can confirm this is still happening in Ubuntu 19.04.
1723117,2018-09-06 01:23:30 UTC,@eugriner:
1723117,2018-09-04 17:11:22 UTC,No one would like there icons behind the dock.
1723117,2020-05-06 12:40:57 UTC,Still happening on 20.04 LTS.
1723117,2018-04-03 12:17:07 UTC,"I think people hide the launcher because they want their apps to take most of the screen real estate, only a few people would auto-hide to have the extended desktop space."
1723117,2019-09-20 13:07:54 UTC,"Is it possible to just create an option on the right click menu to choose alignment options for the desktop icons? Like, to the left, to the right, top or bottom. That would solve this issue. Or have the dock always hide (triggered by mouse hover) when the desktop is shown."
1723117,2017-11-09 17:37:53 UTC,Still with gnome-shell-extension-ubuntu-dock: Installed: 0.8.1
1723117,2017-11-10 06:30:15 UTC,"I believe this is a feature and not a bug. Most people using auto-hide do so because they want to use their full desktop width, which includes putting icons on the left edge of the desktop. So for many/most users of auto-hide the current behaviour is probably best."
1723117,2017-10-12 16:26:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1723117,2017-10-21 18:57:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723117,2019-06-19 02:40:35 UTC,Can confirm this is still existing in Ubuntu 18.04
1723117,2017-10-21 19:19:51 UTC,Package may be gnome-shell-extension-ubuntu-dock
1723117,2017-11-07 12:19:06 UTC,SORRY! problem NOT disappeared.
1723117,2017-10-21 18:59:29 UTC,I can confirm but i don't know what package is interested
1723117,2017-11-07 12:16:47 UTC,"problem disappeared in Ubuntu 18.04
corrado@corrado-beta-4ott:~$ apt policy gnome-shell-extension-ubuntu-dock
gnome-shell-extension-ubuntu-dock:
  Installed: 0.8
  Candidate: 0.8
  Version table:
 *** 0.8 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
        100 /var/lib/dpkg/status
corrado@corrado-beta-4ott:~$"
1723119,2015-03-28 04:06:10 UTC,"Awesome, thanks! Pushed to master in:
commit 83fd4fee8697fc5da8411c99b18900d211b72d68
Author: Mikhail Efremov <email address hidden>
Date:   Fri Mar 20 20:54:38 2015 +0300"
1723119,2017-10-12 16:25:18 UTC,"The attachment ""xfce-4.12_1_fix-fallback-shutdown.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1723119,2018-08-16 09:55:22 UTC,Please forward this patch to the Xfce bug tracker. Thanks.
1723119,2018-09-19 09:25:31 UTC,"Looks like this was fixed long ago, but not in the xfce-4.12 branch."
1723119,2015-03-20 18:12:51 UTC,"Created attachment 6101
Fix 'shutdown' action in the fallback mode"
1723124,2019-06-08 04:17:33 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1723124,2019-04-08 09:51:01 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/511797
Reason: Very old"
1723124,2019-03-28 10:14:16 UTC,Is this still a bug? If yes please update.
1723124,2017-10-13 10:07:05 UTC,ansible 2.4.0 does not deploy for the same reason -
1723124,2017-10-13 09:51:14 UTC,"sorry, 2.3.1 in previous post"
1723124,2017-10-13 09:50:00 UTC,"one more way to reproduce it with ansible 2.1.1 is to set a dummy interface for controller of a choice, e.g. make tunnel_interface: ""goesnowhere99"""
1723124,2017-10-12 14:18:13 UTC,"I use separate interfaces for network/api/tunnel/neutron_external. One of my controllers only has network/api. tunnel_interface is only defined in all.yml, I don't redefine it."
1723124,2017-10-12 14:09:35 UTC,"Is using different interfaces for nodes? If yes, is tunnel_interface variable commented in globals.yml and defined for each host in inventory file?"
1723124,2017-10-12 14:04:09 UTC,looks like all.yml variable evaluation happens before switch statement in template
1723130,2017-11-06 02:45:34 UTC,"Tracking also in:
https://errors.ubuntu.com/problem/bc6e28a2367ba53b9714f5982d0034dbd45a1fd7"
1723130,2017-10-23 18:56:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723130,2017-10-17 09:00:10 UTC,"Just before the bug message I was recording the desktop according to the help guide, pressing ctrl + alt + shift + R
That video on the desktop was the first one I had problems."
1723130,2017-10-17 08:44:22 UTC,Now totem does not open. Not open with videos or without videos
1723130,2021-02-24 03:39:44 UTC,No crashes reported after 18.04 so consider it fixed.
1723130,2017-10-14 19:26:21 UTC,"Was installed
Instalados: 1.12.3-1ubuntu1
I've removed it but it still does not work"
1723130,2017-10-14 16:51:05 UTC,"On 10/14/2017 10:16 AM, José Vidal wrote:

> How can I see if gst-vappi is installed without opening totem? I can not
> open totem. I have removed Totem and then reinstalled it. It continues
> with the same problem.
>


In a terminal go
apt-cache policy gstreamer1.0-vaapi"
1723130,2017-10-14 14:16:34 UTC,How can I see if gst-vappi is installed without opening totem? I can not open totem. I have removed Totem and then reinstalled it. It continues with the same problem.
1723130,2017-10-12 14:40:57 UTC,"StacktraceTop:
 wl_proxy_add_listener (proxy=0x0, implementation=implementation@entry=0x7f368a4aae08 <wl_buffer_listener>, data=data@entry=0x56261fb10000) at ../src/wayland-client.c:469
 wl_buffer_add_listener (data=0x56261fb10000, listener=0x7f368a4aae08 <wl_buffer_listener>, wl_buffer=<optimized out>) at /usr/include/wayland-client-protocol.h:1709
 dri2_wl_swap_buffers_with_damage (drv=<optimized out>, disp=0x56261e0baad0, draw=0x56261fb10000, rects=0x0, n_rects=0) at ../../../src/egl/drivers/dri2/platform_wayland.c:872
 eglSwapBuffers (dpy=0x56261e0baad0, surface=<optimized out>) at ../../../src/egl/main/eglapi.c:1243
 _cogl_winsys_onscreen_swap_buffers_with_damage (onscreen=0x56261fb9f570, rectangles=0x7ffc260aefe0, n_rectangles=0) at winsys/cogl-winsys-egl.c:848"
1723130,2017-10-16 14:20:51 UTC,Is that happening on any video or specific to one/some?
1723130,2017-10-14 02:51:12 UTC,"Seems to happen with any number of preceding actions, those seeing should note if gst-vappi is installed. If so does removing the plugin clear up this issue?"
1723132,2017-10-12 14:30:17 UTC,"Hi,"
1723132,2019-11-20 04:17:46 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1723136,2017-10-12 14:38:29 UTC,What we need for this is sane defaults for each OS in the environment setup
1723136,2017-10-12 14:51:01 UTC,Changing the environment by swapping fedora for centos in the paths has no effect:
1723136,2017-10-12 14:53:42 UTC,OK... so changing the environment paths in the GUI... remembering to check save this environmment which is off by default... then quitting and relaunching... seems to work. Still I think there's a bug in the workflow here that should be adjusted so paths on centos are correct out of the box.
1723137,2017-10-12 14:44:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511493"
1723137,2017-10-12 22:06:14 UTC,Note: the above review is only to take the specific test out of the loop to allow someone the time to triage and fix w/o interrupting the promotion of builds.
1723137,2017-10-13 20:25:44 UTC,"Reviewed:  https://review.openstack.org/511493
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=5e35f29d711780e2e533cd354633124645346b28
Submitter: Jenkins
Branch:    master"
1723137,2019-06-07 20:28:23 UTC,Ocata is EOL
1723149,2017-10-12 17:54:26 UTC,"The profile is in complain mode, which means that apparmor is trying to learn the application behavior."
1723149,2017-10-16 15:27:06 UTC,"Thanks for you feedback.
Is this behaviour documented somewhere? I did not find it."
1723149,2017-10-18 18:25:37 UTC,"This is a regression of behavior, but not design. The original code was behaving incorrectly, and the new code inadvertently fixed the bug. However several applications and users are depending on the old behavior."
1723150,2018-10-20 21:16:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723150,2018-10-20 21:17:28 UTC,Also affects upstream Debian 10/Buster (4.18.0-2-amd64)
1723151,2017-10-12 15:24:51 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1545811, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1723153,2017-10-12 15:30:15 UTC,"StacktraceTop:
 XQueryExtension (dpy=dpy@entry=0x55ebe7f773a0, name=name@entry=0x7fa67422ea95 ""MIT-SCREEN-SAVER"", major_opcode=major_opcode@entry=0x7fff89546264, first_event=first_event@entry=0x7fff89546268, first_error=first_error@entry=0x7fff8954626c) at ../../src/QuExt.c:43
 XInitExtension (dpy=dpy@entry=0x55ebe7f773a0, name=name@entry=0x7fa67422ea95 ""MIT-SCREEN-SAVER"") at ../../src/InitExt.c:47
 XextAddDisplay (extinfo=0x7fa674430130 <_screen_saver_info_data>, dpy=0x55ebe7f773a0, ext_name=ext_name@entry=0x7fa67422ea95 ""MIT-SCREEN-SAVER"", hooks=hooks@entry=0x7fa6744300c0 <screen_saver_extension_hooks>, nevents=nevents@entry=1, data=data@entry=0x0) at ../../src/extutil.c:110
 find_display (dpy=<optimized out>) at ../../src/XScrnSaver.c:77
 XScreenSaverQueryExtension (dpy=<optimized out>, event_base_return=event_base_return@entry=0x7fff89546310, error_base_return=error_base_return@entry=0x7fff89546314) at ../../src/XScrnSaver.c:158"
1723153,2017-10-19 10:10:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723161,2017-12-12 18:39:28 UTC,This still seems to be present on current head
1723161,2020-12-07 04:17:34 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1723161,2020-10-07 18:40:07 UTC,Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
1723161,2017-10-13 20:10:20 UTC,"Hi Fam,"
1723161,2017-10-13 11:09:20 UTC,"i added some debug, and I'm seeing:"
1723161,2017-10-13 10:41:18 UTC,I can reproduce this:
1723161,2017-10-13 10:18:05 UTC,"Hi William,"
1723161,2017-10-13 09:05:52 UTC,"Hi William,
  David's fine (I'm from Red Hat)"
1723161,2017-10-12 19:24:41 UTC,"Interesting; As a test could you try removing the cdrom entry (I doubt that'll help but it's worth a go).
Also, is it possible for you to try a bisection?"
1723161,2017-10-12 20:53:36 UTC,"Hi David,"
1723162,2017-10-12 15:59:32 UTC,One line version for convenience:
1723168,2017-12-15 12:43:52 UTC,This bug seems not related to the snap package (snap: location of genes from DNA sequence with hidden markov model) but to the snapd package (part of the app packaging system developed by Canonical).
1723168,2017-12-16 12:36:46 UTC,This is rather unrelated to snapd ... it is an old known issue with gnome-terminal that it captures F1 presses by default ...
1723168,2018-01-16 07:58:26 UTC,Assigning to gnome-terminal based on the feedback from ora.
1723181,2018-07-04 14:31:04 UTC,exiting without saving after many modifications on a .jpg
1723181,2018-11-06 22:53:36 UTC,https://gitlab.gnome.org/GNOME/shotwell/commit/77514d6960f563e1cb79f8510e123ee49461d24d
1723181,2018-11-07 10:10:52 UTC,Thanks Jens!
1723181,2018-11-07 14:46:14 UTC,"I've uploaded the fix to disco and cosmic now, I'm going to do bionic a bit later while updating to 0.28.4"
1723181,2018-11-09 01:53:54 UTC,This bug was fixed in the package shotwell - 0.30.1-0ubuntu4
1723181,2018-11-09 10:40:02 UTC,"Hello Jan, or anyone else affected,"
1723181,2018-12-10 23:58:39 UTC,This bug was fixed in the package shotwell - 0.30.1-0ubuntu3
1723181,2018-11-21 10:14:33 UTC,Is there someone who was able to trigger the issue/having an hidpi screen to test the fix?
1723181,2018-12-07 11:41:34 UTC,"Using 0.30.1-0ubuntu3 on cosmic it works without visible issue/regression, the error tracker still see reports though, it might improve thing/fix some cases but there is still an issue. Setting as verification-cosmic-done on the basis that it's not a regression and might still improve things even if it's not perfect"
1723181,2018-12-07 15:17:47 UTC,0.28.4-0ubuntu1 is in the same case
1723181,2018-06-29 13:57:04 UTC,Happens to me whenever I make edits to a photo. It keeps asking me to save repeatedly even when the document has already been saved and does so again when I reopen the file (which shows the changes!).
1723181,2018-12-10 23:58:45 UTC,"The verification of the Stable Release Update for shotwell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1723181,2018-12-11 16:13:48 UTC,This bug was fixed in the package shotwell - 0.28.4-0ubuntu1
1723181,2018-11-13 18:55:29 UTC,"Hello Jan, or anyone else affected,"
1723181,2018-03-14 15:28:03 UTC,"Cropped image and used ""send to"""
1723181,2017-10-23 21:33:25 UTC,"On my computer the bug manifested itself when I merely connected a USB flash card, without displaying images. I never use Shotwell but Ubuntu 17.10 insists on opening it when I connect a flash card with photos, although my settings for photos are on “open directory” as they always were – but that is a different issue."
1723181,2017-12-06 12:53:09 UTC,Similar problem has been detected:
1723181,2017-07-17 14:59:26 UTC,"Version-Release number of selected component:
shotwell-0.26.2-1.fc26"
1723181,2017-07-17 14:59:33 UTC,"Created attachment 1299895
File: backtrace"
1723181,2017-07-17 14:59:34 UTC,"Created attachment 1299896
File: cgroup"
1723181,2017-07-17 14:59:36 UTC,"Created attachment 1299897
File: core_backtrace"
1723181,2017-07-17 14:59:37 UTC,"Created attachment 1299898
File: cpuinfo"
1723181,2017-07-17 14:59:39 UTC,"Created attachment 1299899
File: dso_list"
1723181,2017-07-17 14:59:40 UTC,"Created attachment 1299900
File: environ"
1723181,2018-01-29 12:12:15 UTC,Similar problem has been detected:
1723181,2017-07-17 14:59:42 UTC,"Created attachment 1299901
File: exploitable"
1723181,2017-07-17 14:59:46 UTC,"Created attachment 1299903
File: maps"
1723181,2017-07-17 14:59:47 UTC,"Created attachment 1299904
File: open_fds"
1723181,2017-07-17 14:59:48 UTC,"Created attachment 1299905
File: proc_pid_status"
1723181,2017-07-17 14:59:50 UTC,"Created attachment 1299906
File: var_log_messages"
1723181,2017-10-12 16:51:15 UTC,"StacktraceTop:
 g_menu_model_get_n_items (model=0x0) at ../../../../gio/gmenumodel.c:494
 gtk_application_window_update_shell_shows_app_menu (window=0x55b0b07da470, settings=<optimized out>) at ././gtk/gtkapplicationwindow.c:316
 gtk_application_window_real_realize (widget=0x55b0b07da470) at ././gtk/gtkapplicationwindow.c:683
 _g_closure_invoke_va (closure=0x55b0b05af980, return_value=0x0, instance=0x55b0b07da470, args=0x7fff28ea8670, n_params=0, param_types=0x0) at ../../../../gobject/gclosure.c:867
 g_signal_emit_valist (instance=0x55b0b07da470, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff28ea8670) at ../../../../gobject/gsignal.c:3300"
1723181,2017-10-21 13:18:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723181,2017-07-17 14:59:43 UTC,"Created attachment 1299902
File: limits"
1723199,2018-02-07 21:36:22 UTC,"Yeah, this is fallout from the upper-constraints stuff introduced in https://github.com/openstack/swift/commit/91ce1bb"
1723199,2018-02-07 21:39:03 UTC,Workaround should to have a (reasonably up-to-date) local copy of upper-constraints and pass it in via a UPPER_CONSTRAINTS_FILE env var. Haven't actually tested it though -- we might need to add that to the passenv list?
1723203,2018-06-16 21:29:52 UTC,Example of how to automate the debian installer for the pi https://www.raspberrypi.org/forums/viewtopic.php?f=50&t=216079&p=1328882#p1328882
1723203,2018-04-08 12:46:31 UTC,Somebody else has pointed out that the raspi3-firmware package is overwriting user configs - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848101 .  They didn't fix the problem.
1723203,2017-10-12 20:03:20 UTC,It would definitely be nice to actually see the patches.
1723203,2017-10-13 17:50:00 UTC,"A fat partition is required, but it doesn't have to be mounted at /boot, and it doesn't need to contain kernels.  It could have U-boot, grub2, or an efi bootloader on there for example."
1723203,2017-10-13 08:25:54 UTC,I recall that the vfat /boot partition is (was?) a requirement of the way the pi boots and reads the config.txt and kernel.  This may have now changed?
1723203,2017-10-12 23:11:13 UTC,"Suggesting a partitioning scheme is easy to do, and could be done by just modifying one file.  Similarly, installing a kernel is fairly straightforward I think with the flash-kernel package.  That already has a debian installer udeb."
1723203,2017-10-17 19:04:46 UTC,"Debian seems to be doing stuff through hooks in the raspi3-firmware package.  They copy kernels to /boot/firmware this way and generate config.txt and cmdline.txt files through this mechanism.  That's a bit rubbish if you want to change the defaults, plus you just end up with duplicate copies of all the kernels."
1723210,2017-10-22 09:16:00 UTC,I got exactly the same problem since upgraded to artful. My modem is Huawei E176 (12d1:140c) and my workaround for now is to add file /etc/udev/rules.d/99-mm-e176.rules with below content to unset ID_MM_CANDIDATE on /dev/cdc-wdm*.
1723210,2017-11-09 10:50:10 UTC,Thanks Sugree. Your workaround works for me too!
1723214,2017-10-12 18:41:04 UTC,"StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=<optimized out>) at ../../../../glib/gslice.c:539
 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=2) at ../../../../glib/gslice.c:842
 g_slice_alloc (mem_size=mem_size@entry=40) at ../../../../glib/gslice.c:1016
 g_variant_alloc (trusted=1, serialised=0, type=0x558e2c745680) at ../../../../glib/gvariant-core.c:476
 g_variant_new_from_children (type=type@entry=0x558e2c745680, children=0x558e2c747cc0, n_children=n_children@entry=2, trusted=trusted@entry=1) at ../../../../glib/gvariant-core.c:565"
1723214,2017-10-23 09:51:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723223,2019-06-15 04:17:43 UTC,[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.]
1723223,2019-06-15 04:17:47 UTC,[Expired for linux (Ubuntu Disco) because there has been no activity for 60 days.]
1723223,2019-06-15 04:17:46 UTC,[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.]
1723223,2019-06-15 04:17:44 UTC,[Expired for linux (Ubuntu Cosmic) because there has been no activity for 60 days.]
1723223,2019-06-15 04:17:42 UTC,[Expired for linux (Ubuntu Trusty) because there has been no activity for 60 days.]
1723223,2017-10-12 18:59:27 UTC,"For example, here is a autopkgtest failure that was flagged by my update to initramfs-tools package:"
1723223,2019-02-12 20:32:09 UTC,"After a discussion with vorlon, his proposal is to blacklist the ""special"" kernels so they're ignored for autopkgtests."
1723223,2019-02-12 15:51:13 UTC,https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html
1723223,2019-02-12 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1723223,2018-02-06 22:03:58 UTC,This unfortunately is not a simple fix.
1723223,2017-10-18 12:41:42 UTC,the failing test was added by bug 1385330
1723223,2019-06-15 04:17:40 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1723227,2018-01-29 17:46:35 UTC,"Exactly the same issue here on Acer Aspire E5-771G-51HQ.
Touchpad suddenly stopped to work after update to kernel 4.13 and xorg ""hwe"".
External USB mouse works properly."
1723227,2018-01-30 00:18:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723229,2019-03-20 18:08:51 UTC,There are several places in TripleO where we do validations so I think this could be confusing.
1723229,2019-03-05 13:23:57 UTC,Is this still an issue?
1723232,2019-09-19 11:59:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1723240,2017-11-09 14:08:49 UTC,"I think this has to do with how we are modeling spaces and dual-stack support. My guess is that when defining the LXD container we ask MAAS for an IP address in the requested space, but the space only defines an IPv4 subnet, so that is all we assign the container.
Even if we were assigning multiple addresses, this needs more discussion because of interactions with charms. When a given application has access to 2 addresses, what address do we advertise for other applications to interact with it. Do we give all addresses, a different address, etc. Right now our address field is a single string, so we don't have a way to expose it as a list of addresses."
1723240,2017-11-09 15:59:45 UTC,"@jameinel - Just to confirm, in the example above two of the spaces have two subnets each.  The LXD container was created specifying an IPv4-only space (mgmt), an IPv6-only space (stgfe), and an IPv4/IPv6 subnet (delvrya)"
1723243,2017-10-31 12:20:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723245,2017-12-24 20:04:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723247,2017-10-12 20:44:02 UTC,"A big hit in performance seems to be a major performance regression in gtk3 which is occuring when disabling client side decorations (CSD), see upstream bug [1]."
1723247,2020-08-04 23:26:40 UTC,"Version 1.0 of inkscape came out, is this still a bug ?"
1723247,2017-10-12 20:53:22 UTC,"As mentioned in the last comment, even when enabling CSD, performance with gtk3 in master is worse than with gtk3 in 0.92.x."
1723247,2017-10-15 23:16:08 UTC,"If the GTK3 developers ""don't give a sh*t"" as you say, if they prefer the ""decorations"" (it is a fortunate word isn't it?) over functionality, could it be high time to port the whole project to QT?"
1723247,2017-10-16 00:15:14 UTC,"First of all, I don't want any bad blood here... I was a bit rude there which was mostly the frustration talking and I'm sorry about that. GTK+ is a great project (I don't want to diminish anybody's effort) but it has its rough edges, no question (especially if you're on Windows/Mac and don't want to create the GNOME desktop). If you want a ""good"" laugh watch [1], that's how I'm feeling most of the time and while entertaining it caries a scary bit of truth."
1723256,2017-10-12 21:26:55 UTC,it's because the xdg-open feature has been integrated to snapd itself now so you shouldn't need the separate binary
1723256,2017-10-12 21:41:23 UTC,Thanks - I notice that snapd 2.28.4 is marked as (xenial-proposed) in Synaptic. Is that a correct tag for a release? Sorry I don't know the conventional terminology.
1723256,2017-10-13 09:45:28 UTC,"snapd 2.28.4 is not yet released, it only went to xenial-proposed yet which users should never have enabled permanently ..."
1723256,2019-09-26 11:03:57 UTC,"Marking as invalid because I understand the issue to have been due to having proposed enabled, and the issue itself wouldn't happen outside of that."
1723268,2017-10-12 22:41:56 UTC,"StacktraceTop:
 XkbUseExtension (dpy=0x11a70d0, major_rtrn=major_rtrn@entry=0x0, minor_rtrn=minor_rtrn@entry=0x0) at ../../../src/xkb/XKBUse.c:652
 XkbGetUpdatedMap (dpy=0x11a70d0, which=7, xkb=0x16d5620) at ../../../src/xkb/XKBGetMap.c:574
 XkbGetMap (dpy=0x11a70d0, which=which@entry=7, deviceSpec=deviceSpec@entry=256) at ../../../src/xkb/XKBGetMap.c:603
 grab_ungrab (rootwin=rootwin@entry=0x11a9020, keyval=114, modifiers=67108932, grab=grab@entry=1) at bind.c:203
 do_grab_key (binding=binding@entry=0x16d5560) at bind.c:326"
1723268,2017-10-17 23:33:11 UTC,"Confirmed this issue trying to start Kazam in Ubuntu 17.10 (beta 2), Wayland session, GNOME 3.26.1."
1723268,2017-10-17 07:07:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723272,2017-10-13 20:42:40 UTC,This looks like a duplicate of bug 1713313 but LP keeps timing out when I try to mark it as one.
1723272,2017-10-13 21:24:07 UTC,"Interesting. According to that ticket, applications require changes to PolicyKit and ultimately maybe their architecture (separation into non-graphical and graphical components) in order to run as root on Wayland. So it looks like you have two options:"
1723272,2017-10-23 20:59:00 UTC,"Thanks for reporting. It's already known - see bug 1713313.
Please mark as duplicate (I got timeout issue)."
1723272,2017-10-23 21:23:43 UTC,"@nrbrtx Yeah, Launchpad has had some timeout issue for over a week now. However ..."
1723279,2017-10-13 21:27:44 UTC,Marking as duplicate (thanks to @brian-murray for identifying the original).
1723279,2017-10-23 20:51:03 UTC,"Thanks for reporting. It's already known - see bug 1713313 and bug 1713311.
Please mark as duplicate (I got timeout issue)."
1723279,2017-10-23 21:29:07 UTC,I have been trying to mark it as a duplicate of 1713313 since 2017-10-13 ...
1723282,2017-10-17 22:53:08 UTC,"As per our discussion, there are 2 authentication mechanism in Juju:
* password-based: if Juju can find a password on your local client;
* macaroon-based: if password is not found."
1723282,2017-10-15 08:24:30 UTC,"macaroons are intentionally time limited, and will require login to be run
again from time to time."
1723282,2017-10-16 00:40:55 UTC,"@jameinel: For production & staging services, we need to monitor (with Nagios, in our case) that juju status is returning expected values in an expected time.  This means that our monitoring servers need to stay logged in permanently."
1723285,2018-05-09 22:33:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723285,2018-05-09 22:33:50 UTC,"Same here. Had 19GB free, but the snapshot took 18GB and the release-upgrade failed."
1723285,2018-05-09 23:15:55 UTC,"@martin3000 IIRC the default partition scheme is for /home to be in the root partition. Not saying you had that setup, just musing."
1723290,2017-10-13 02:08:13 UTC,I have a feeling it was to do with the automatic internet importing function. It looks like the web search does not import missing scripture and rather returns nothing.
1723290,2017-10-30 08:30:15 UTC,"Hi Bedlore,"
1723290,2017-10-31 06:33:58 UTC,"Hi Phill, pretty sure I used biblegateway.com"
1723290,2017-10-31 17:50:41 UTC,The bible remote search is not very good and is on my list to refactor but it needs to be done in conjunction with the clients.
1723293,2017-11-10 12:36:12 UTC,"Possibly related to: https://bugs.launchpad.net/openlp/+bug/1638620 ""Unexpected results from bible passage regex parsing"""
1723295,2017-10-30 08:26:22 UTC,"Hi Bedlore,"
1723301,2017-10-13 03:38:18 UTC,"StacktraceTop:
 meta_wayland_surface_ensure_inhibit_shortcuts_dialog (seat=0x55e5b2b9e680, surface=0x55e5b2ef61f0) at wayland/meta-wayland-inhibit-shortcuts-dialog.c:128
 meta_wayland_surface_show_inhibit_shortcuts_dialog (surface=0x55e5b2ef61f0, seat=0x55e5b2b9e680) at wayland/meta-wayland-inhibit-shortcuts-dialog.c:160
 zwp_keyboard_shortcuts_inhibit_manager_inhibit_shortcuts (client=<optimized out>, resource=<optimized out>, id=<optimized out>, surface_resource=<optimized out>, seat_resource=<optimized out>) at wayland/meta-wayland-inhibit-shortcuts.c:151
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffed9e2f400, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffed9e2f4d0) at ../src/x86/ffi64.c:525"
1723301,2020-01-24 10:00:12 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1723304,2017-11-17 12:28:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723310,2018-01-30 00:50:58 UTC,"@Michael Turek
This is different from the bug related by Tao Li:
https://bugs.launchpad.net/ironic/+bug/1712228"
1723310,2017-10-17 00:59:49 UTC,"@Michael
driver：pxe_ipmitool
openstack：newton
console：shellinabox
hardware-type：HuaWei
# ironic --version
1.7.1"
1723310,2018-01-29 16:03:40 UTC,@fupingxie
1723310,2017-10-16 14:34:40 UTC,"Hello fupingxie,"
1723310,2018-01-29 16:07:21 UTC,Another related bug:
1723323,2019-11-01 09:04:32 UTC,I have been experiencing the same issue with the following configuration:
1723350,2019-11-02 16:33:57 UTC,"I am trying to seed SSSD cache. The setup is working fine, I can do a successful offline authentication but once I am connected to my company network using VPN, SSSD cache is never refreshed unless I restart SSSD or replace /etc/resolv.conf symlink (I am using systemd-resolved) by a regular /etc/resolv.conf file."
1723350,2019-11-01 17:18:02 UTC,I agree. Do you have a way to reproduce this somewhat reliably?
1723350,2019-10-28 13:04:31 UTC,The code in the PR above has now been pushed can we get a new build of SSSD including it ?
1723350,2019-09-02 12:41:22 UTC,A PR which might address this was posted to the sssd mailing list: https://github.com/SSSD/sssd/pull/864
1723350,2018-10-31 21:01:21 UTC,I can confirm the same issue with Ubuntu 18.04 (used the DVD).  SSSD cannot resolve the the backend and then says it's offline.  Restarting SSSD after a reboot always resolves the issue.
1723350,2018-10-10 14:15:18 UTC,"I hit this bug too with Ubuntu 18.04. On boot sssd fails to find AD servers from DNS and then continues to query 127.0.0.1 port 53, which will never answer. The log looks like this:"
1723350,2018-09-18 16:55:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723350,2018-09-10 22:56:07 UTC,"Sorry, ""fix released"" is for the current development of Ubuntu which is 18.10. I'll add a task for bionic, and remove the artful one."
1723350,2018-07-11 07:29:15 UTC,"This also mostly applies to us:
* Bionic, installed via network installer.
* We did not configure network explicitly, AFAICT, this means networkd is used. However, we run with DHCP.
* sssd.conf uses FQDNs for the kerberos and ldap servers (I guess you meant that)?
* We also provide backup servers for both."
1723350,2018-07-11 04:27:20 UTC,I also have observed this problem on bionic for several different computers. The workaround always solves the problem; without the workaround I cannot log in. What the computers had in common:
1723350,2018-06-12 14:03:48 UTC,"After setting try_inotify to false, I see that the message that an inotify was set up does not show up anymore, but no message that polling is used instead is shown in the logs. If I understand the code correctly, that's just right - a message will only be shown if try_inotify is true and it actually fails."
1723350,2018-06-12 12:32:33 UTC,"Interesting, I setup a watch on a directory to see what happens when a symlink is changed:"
1723350,2018-06-12 12:19:19 UTC,The sssd.conf manpage from sssd 1.13.4 and 1.16.1 (xenial and bionic) says that without inotify sssd will fall back to polling resolv.conf every 5s:
1723350,2018-09-10 19:45:53 UTC,"We are seeing this too, on Bionic servers installed from netboot / PXE."
1723350,2019-11-26 14:09:02 UTC,"Hi all.
@Andreas Hasenack any progress on this :) ?
Anything we can do to help."
1723350,2020-06-02 14:46:55 UTC,bionic verification
1723350,2020-03-04 15:30:36 UTC,Same here - it is a nightmare:
1723350,2020-03-05 13:18:25 UTC,"This is still on my list, I'm just very busy with focal fossa right now, but the feature freeze is past, and now I can concentrate on only fixing bugs."
1723350,2020-05-11 17:59:08 UTC,It has been a constant problem for me in 18.04 but seems to work fine in 20.04 on the couple of computers I have tried it on.
1723350,2020-05-11 21:14:24 UTC,"Ok, I have a simple way to reproduce this, and was able to test the upstream patch. I'll polish it up and put it up for review, then prepare the SRU paperwork."
1723350,2020-05-12 19:32:49 UTC,"Just tested and eoan is affected, focal is clear."
1723350,2020-05-27 13:54:16 UTC,"> b) change the fallback polling code to keep trying, instead of giving up right away
"
1723350,2020-05-29 14:43:47 UTC,"> AFAICT, this will only happen if /etc/resolv.conf is a broken symlink.
"
1723350,2020-05-29 15:15:43 UTC,"Hello Marian, or anyone else affected,"
1723350,2020-05-29 15:16:05 UTC,"Hello Marian, or anyone else affected,"
1723350,2020-06-02 14:24:03 UTC,eoan verification
1723350,2018-06-12 07:48:50 UTC,"@renbag: It might be that in terms of timing, the DHCP server is also involved, since it defines the time network-online.target takes to start. Our setup is relatively slow, since we have a DHCP server under high load (several 10000 leases) and are using a dhcrelay in between.
Potentially, you can still force the issue to appear by inverting the workaround to force sssd to start before network-online.target."
1723350,2020-06-09 13:01:35 UTC,This bug was fixed in the package sssd - 2.2.0-4ubuntu1.1
1723350,2020-06-09 13:01:43 UTC,"The verification of the Stable Release Update for sssd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1723350,2020-06-09 13:01:53 UTC,This bug was fixed in the package sssd - 1.16.1-1ubuntu1.6
1723350,2019-11-27 14:12:16 UTC,"I'll get to it. Being able to test the fix would help a lot, since I never got it reproduced locally."
1723350,2018-06-12 07:39:14 UTC,"@renbag: Do you see ""sssd[be[896]: Backend is offline"" in ""systemctl status sssd""?
Is your backend server given as hostname / fqdn in sssd.conf?"
1723350,2018-06-11 14:17:58 UTC,"I can confirm that adding the described override, all works fine."
1723350,2018-06-11 22:21:41 UTC,"I'll test tomorrow if try_inotify=false in the [sssd] section also works around this issue, unless someone beats me to it..."
1723350,2018-05-08 18:07:47 UTC,@renbag could you please:
1723350,2018-05-08 15:24:00 UTC,"The artful machine is a workstation and has only a wired network interface managed by network-manager that gets configured by a DHCP server on our LAN.
The files you requested are not present or have little or no information:"
1723350,2018-06-12 07:26:50 UTC,"Since my last comment on this bug report (#16), I upgraded my workstation from artful to bionic. The machine also has an NVME SSD, but I do not see this sssd offline bug anymore."
1723350,2018-05-08 13:41:29 UTC,"I'll mark this as fix released for bionic then, and open up an artful task."
1723350,2018-05-08 06:29:22 UTC,"I confirmed the bug in artful, but now, with the same sssd.conf in bionic, I do not see the bug anymore."
1723350,2018-05-07 20:53:28 UTC,"Reading what I wrote in comment #4, seems like I'm contradicting myself. First I say I can reproduce the problem, but later I say that after I bring the network back up it starts working again on its own. That's exactly what I'm seeing now, i.e., no bug. Tried xenial, artful and bionic. Are you guys on a desktop by any chance, with just a wifi connection perhaps?"
1723350,2018-05-09 10:53:05 UTC,"@Andreas: thank you for your suggestions. I removed the workaround from my artful machine and did what you asked, then, after some minutes, I reactivated the workaround and did the same. All the logs are attached for comparison (the real username and domain were redacted)."
1723350,2018-05-07 20:14:38 UTC,"I also tried again in bionic, including rebooting the sssd client while the krb5 server was offline, and it automatically switched back to an online status after i restored the network on my krb5 server. I then tried this again on xenial, and there it also worked."
1723350,2018-05-07 13:54:13 UTC,"The test in comment #4 is more thorough, as it checks that sssd can detect that the network is up again on its own. Can you try that on bionic please?"
1723350,2018-03-26 18:32:10 UTC,"@Simon: Interesting – I can't reproduce the problem in 18.04 anymore. I tested a VM and a laptop using ethernet and wifi, and sssd was online on boot without any workarounds."
1723350,2018-03-20 23:08:25 UTC,Also affects Ubuntu Bionic (18.04)
1723350,2017-10-13 21:37:23 UTC,"I can confirm this is happening after a reboot, and that a simple USR2 signal fixes it, but I wonder why sssd doesn't get itself back into online mode on its own in this case."
1723350,2017-10-13 13:08:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723350,2017-10-13 13:01:57 UTC,"I confirm the bug and that the workaround solves the problem.
If the sssd configuration doesn't include:
cache_credentials = true
it is not even possible to do an Active Directory login."
1723350,2018-05-07 19:01:34 UTC,"I tried the steps in #4. As expected, login failed while the network was offline. It worked again immediately after enabling the network. So to me it seems the problem really does not occur in bionic anymore."
1723350,2018-05-09 10:54:04 UTC,/var/log/sssd/* attachment.
1723350,2018-05-08 13:43:41 UTC,"@renbag, can you share your network configuration on this artful machine? These files:"
1723350,2018-05-10 06:35:33 UTC,"The workaround is the systemd unit file written in the Bug Description.
The 'cache credentials' config option does not have any effect on the bug and for the tests I have disabled it."
1723350,2018-06-11 22:20:20 UTC,"Another issue appears to be...
When starting sssd in highest debug level, and then changing resolv.conf once by doing:
$ touch foo
$ mv foo /run/systemd/resolve/stub-resolv.conf
(that's where the link target is pointing to), I see the expected:
(Tue Jun 12 00:16:57 2018) [sssd] [resolv_conf_inotify_cb] (0x2000): Received inotify notification for /etc/resolv.conf
(Tue Jun 12 00:16:57 2018) [sssd] [monitor_update_resolv] (0x1000): Resolv.conf has been updated. Reloading."
1723350,2018-06-11 21:28:27 UTC,"Thanks for searching out this info!
I grepped through all logs for ""inot"" and found no match (only the initial inotify setup). So it seems sssd was not notified via inotify of the change.
That matches the behaviour that ""strace"" showed that ""127.0.0.1"" instead of ""127.0.0.53"" was queried."
1723350,2018-05-09 20:21:52 UTC,"The workaround you speak of, is that the sssd option to cache credentials, or the systemd unit file change to require network-online.target?"
1723350,2018-06-11 14:15:52 UTC,"Needless to say, resolv.conf is:
nameserver 127.0.0.53
search OUR.INSTITUTION"
1723350,2018-06-11 14:06:12 UTC,Is this an inotify race due to the symlink-magic of systemd-resolved?
1723350,2018-06-11 14:03:02 UTC,"That's interesting.
strace'ing the sssd_be process, it seems that it's trying to contact 127.0.0.1 as DNS server, and fails.
systemd-resolved is running on 127.0.0.53 and works just fine."
1723350,2018-06-11 13:42:32 UTC,"Argh! My fault, with the typo fixed, I see the following:"
1723350,2018-06-11 21:14:50 UTC,The inotify callback would log this:
1723350,2018-06-11 13:09:33 UTC,"I've now had a machine with actual failure and debug_level=9 in sections sssd, pam and nss.
No more information was produced, just tons of org.freedesktop.sssd.Error.DataProvider.Offline ."
1723350,2018-06-11 13:01:20 UTC,"@ahasenack: Even in case things ""work"", I observe the following:"
1723350,2018-06-11 12:16:12 UTC,"Maybe start with 6. From https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html:
""""""
To enable debugging persistently across SSSD service restarts, put the directive debug_level=N, where N typically stands for a number between 1 and 10 into the particular section. Levels up to 3 should log mostly failures (although we haven’t really been consistent especially earlier in the SSSD development) and anything above level 8 provides a large number of log messages. Level 6 might be a good starting point for debugging problems.
"""""""
1723350,2018-06-11 10:09:03 UTC,"@jakub-hrozek: When activating debug_level on some machines, which level is high enough?"
1723350,2018-05-17 10:52:58 UTC,Are the sssd logs captured with a high enough debug_level in the [sssd] section of sssd.conf? Normally sssd should detect notifications from libnetlink and reset the offline status.. It would be nice to see those and correlate with system logs..
1723350,2018-06-11 13:24:51 UTC,"I tried wiht 0x7770 now in all sections, but I don't get more info.
Now, sssd.log shows:
(Mon Jun 11 15:10:34:313118 2018) [sssd] [sss_ini_call_validators] (0x0020): [rule/allowed_sssd_options]: Attribute 'debug_devel' is not allowed in section 'sssd'. Check for typos.
for each section :-(."
1723350,2018-06-11 09:59:58 UTC,"Could somebody please add Bionic back?
We observe this on Bionic, it's pretty random, mostly machines with fast root devices (e.g. NVMEs) are affected. Backend is offline on boot and stays offline.
Since it's so random and I don't want to enable debug information on all machines we have, I can't promise that we will be able to collect debug data."
1723354,2017-10-16 16:45:13 UTC,"If someone has the time to work on this, seems like maybe it could come through the blueprint/spec process, just to make sure everyone is on the same page."
1723359,2017-10-16 13:40:24 UTC,Thanks for the bug report!
1723359,2019-01-14 13:59:52 UTC,"Hi,"
1723362,2018-01-12 00:44:09 UTC,"Actually, disregard that last comment. I never rebooted after updating snap using the ppa. I didn't think it was needed, but after a reboot this morning and running the updated software fresh I have not had a recurrence of the bug."
1723362,2018-01-19 08:38:18 UTC,"Same here, #11 fixed it."
1723362,2018-06-06 09:49:24 UTC,Is there any workaround for this issue?
1723362,2018-03-08 13:58:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723362,2018-05-05 22:54:03 UTC,"This also affects me,"
1723362,2018-06-18 13:03:42 UTC,i just went for dpkg -r gnome-software gnome-software-plugin-snap ubuntu-software as a workaround :)
1723362,2018-01-11 14:16:49 UTC,"I tried the PPA in comment #11, but just got a recurrence of this bug. Took about 12 hours before it manifested."
1723362,2018-01-25 23:08:44 UTC,"I'll try #11, but at the time of writing, syslog file is 4GB (with 90 minutes uptime), and the gnome-software process has already been killed after my machine was completely unresponsive for several minutes (SSD activity light on solid)."
1723362,2018-01-10 04:37:15 UTC,Is an SRU fixing this likely to get pushed to artful?  It bites me several times a week (it's filling my syslog with errors as I write this).
1723362,2017-11-10 17:36:34 UTC,Same issue here! Note that it also causes the syslog file to grow indefinitely and thus fills up your root.
1723362,2017-11-14 03:43:43 UTC,This is occurring in snapd-glib and is likely to be fixed in version 1.24 which is the current candidate for a SRU.
1723362,2017-11-14 23:35:53 UTC,I tried the SRU candidate and it worked for me. Thanks!
1723362,2017-10-15 16:28:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723362,2017-10-15 16:59:35 UTC,Same error shortly after boot and upgrade (could be coincidental):
1723362,2017-10-16 13:28:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1723362,2017-11-05 19:32:07 UTC,I reported the bug to Gnome. https://bugzilla.gnome.org/show_bug.cgi?id=789941
1723362,2017-10-22 21:15:18 UTC,"Me too. GIMP is not working anymore, is this issue related?"
1723362,2017-11-07 09:57:10 UTC,Thanks for sending it to GNOME
1723362,2017-11-10 17:38:34 UTC,"Oops, sorry for the unnecessary comment, I should have read this bug closer before repeating the info about syslog."
1723362,2017-10-21 13:29:35 UTC,"Any workaround to stop this for now? I deleted syslog so it won't fill my disk, but systemd-journal and syslogd eats all my cpu."
1723367,2017-10-13 10:55:04 UTC,"All I've managed to find so far by scouring logs is that bazaar.launchpad.net is asking login.launchpad.net whether the OpenID signature is valid, and login.launchpad.net is saying no.  But it's not failing for you on every request, just enough to break things.  This is very odd."
1723367,2017-10-13 12:04:41 UTC,Thank you for getting back to me so quickly.
1723367,2017-10-13 13:50:48 UTC,"Thanks; that may give us something to work with.  However, after logging out, private branch pages on bazaar.launchpad.net seem to work for me (sending me through the usual login workflow) using the same version of Chrome on Ubuntu.  (I don't have access to the particular branch in question, but picked one I do have access to instead.)  Are you using Ubuntu or some other OS?"
1723367,2017-10-13 14:08:22 UTC,We're using Windows 10 Pro Version 1703 Build 15063.674 (64-bit)
1723367,2017-10-19 15:39:43 UTC,"I tried going into Chrome's F12 Developer Menu > Application > Clear Storage for the launchpad.net sites, but it didn't help."
1723367,2017-10-23 12:11:39 UTC,"Clearing all cookies, cache and data, and allowing Chrome to save password for login.launchpad.net has helped a bit: accessing specific revision numbers is working now, with or without a trailing slash on the URL."
1723367,2017-10-24 11:08:23 UTC,"Wanted to try this myself using Chrome on Ubuntu. https://help.ubuntu.com/community/GettingUbuntu says ""Go to the Official Download Page, http://www.ubuntu.com/getubuntu/download."
1723367,2017-12-08 07:48:08 UTC,I keep getting this issue since october.
1723380,2017-11-17 13:18:51 UTC,"I had those problem, because rally try to use /etc/tempest/tempest.config(it doesn't exist) instead of created config by rally"
1723380,2019-05-16 05:25:09 UTC,"I could see a similar problem but not the exact one.
When I was trying to run a command - 'tempest run -l', I could see the following error-"
1723388,2017-10-13 10:40:11 UTC,"StacktraceTop:
 ?? ()
 call_init (l=<optimized out>, argc=argc@entry=4, argv=argv@entry=0x7ffcda862a28, env=env@entry=0x7ffcda862a50) at dl-init.c:72
 call_init (env=0x7ffcda862a50, argv=0x7ffcda862a28, argc=4, l=<optimized out>) at dl-init.c:30
 _dl_init (main_map=main_map@entry=0x563e4b1b03f0, argc=4, argv=0x7ffcda862a28, env=0x7ffcda862a50) at dl-init.c:120
 dl_open_worker (a=a@entry=0x7ffcda862570) at dl-open.c:575"
1723389,2017-10-16 16:22:22 UTC,https://github.com/autokey-py3/autokey/issues/87
1723389,2017-10-23 20:58:28 UTC,"You may try to switch to 'Ubuntu on Xorg' session on login.
Using LTS is better than become a beta tester of 17.10."
1723392,2021-01-03 07:24:50 UTC,4.4.0-2 is in hirsute-proposed (and in Debian Testing).
1723392,2019-11-20 18:11:12 UTC,"Hi Christian,"
1723392,2020-06-17 16:33:43 UTC,"Debian/Ubuntu packaging is available here (see Debian branch):
 https://github.com/raoulbhatia/rsync-bpc
 https://github.com/raoulbhatia/libbackuppc-xs-perl
 https://github.com/raoulbhatia/backuppc"
1723392,2020-02-11 20:08:11 UTC,"Hi, any chance if version 4.2 or 4.3 is going to get into Ubuntu 20.04? Version 3.3.1 is way old!"
1723392,2019-10-17 09:28:28 UTC,FYI: I pinged on the Debian ITP to get an idea if/who worked on this already and to which amount.
1723392,2019-03-19 00:09:58 UTC,Any ETA when a version will be ready to play with?
1723392,2019-08-01 22:25:04 UTC,"It's important to me that this lands by 20.04, is there anything to be done to ensure this happens?"
1723392,2019-08-02 07:38:41 UTC,"Hi Ian,
I agree that 20.04 is the right target.
I have added myself a note to revisit this bug on the earliest point changes can be taken for 20.04 (November)."
1723392,2017-10-17 12:12:39 UTC,"Surely reasonable for 18.04, but too late for 17.10.
I'll subscribe the Team to take a look after 18.04 opens up.
Especially if Debian would pick it up, but so far no movement on the referenced bug yet."
1723392,2018-01-02 16:12:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723392,2018-08-22 17:24:17 UTC,"Another important bug that is fixed in backuppc 4.1.5:
https://github.com/backuppc/backuppc/issues/176 - File names get truncated after approx. 100 characters."
1723392,2018-11-28 11:19:09 UTC,"There is Debian BackupPC packaging team now and packaging latest backuppc 4.3.x and backuppc-rsync (rsync-bpc) is on the way, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864079"
1723396,2017-10-20 19:32:54 UTC,https://github.com/vkohaupt/vokoscreen/issues/191
1723396,2017-12-14 17:14:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723399,2019-07-05 01:51:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723403,2017-10-13 13:32:14 UTC,"Thank you for your bug report, that's a known gtk/wayland issue, see https://bugzilla.gnome.org/show_bug.cgi?id=766284"
1723403,2018-05-03 08:46:11 UTC,The bug is now at https://gitlab.gnome.org/GNOME/gtk/issues/624
1723403,2018-05-03 08:55:44 UTC,Still present in 18.04.
1723403,2018-06-20 10:29:20 UTC,It happens also on Xorg to me
1723412,2017-10-13 17:05:49 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1723412,2019-04-10 11:55:14 UTC,The bug still exists in Ubuntu 19.04/disco:
1723412,2019-06-18 07:53:28 UTC,now adding a Recommends: libjvmti-oprofile0
1723412,2019-06-18 10:18:25 UTC,This bug was fixed in the package oprofile - 1.3.0-0ubuntu1
1723415,2017-10-19 03:44:01 UTC,"United, unified, multi-targeted, interactive and automotive bug-tracking system is the most important thing the Universe should have."
1723415,2017-10-13 20:23:59 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1723415,2017-10-19 03:37:47 UTC,"I did not use https://wiki.ubuntu.com/Bugs/Upstream/kernel, I just filled what I could on bugzilla.kernel.org. https://bugzilla.kernel.org/show_bug.cgi?id=197315"
1723415,2017-10-13 19:14:38 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1723415,2017-10-13 20:02:37 UTC,"Before Lubuntu 17.10 I used Lubuntu 16.04 and the bug exists there. I did ""fsck.ext4 -fck"" but it did not help. But I did not use ""fsck.ext4 -l badblocks.txt""
I can't remember a version of kernel without this error. I thought it is normal for my hdd.
As you said, I've used 4.14.0-041400rc4.201710130854 kernel for testing and the bug exists on it too."
1723415,2017-10-13 12:19:33 UTC,lspci-vnvn.log
1723415,2017-10-13 20:04:09 UTC,Thank you
1723415,2017-10-13 12:30:08 UTC,This change was made by a bot.
1723415,2017-10-13 17:16:45 UTC,"I've tried to calculate somehow what block is on sector 50868652 and I got 6291509. Badblocks program successfully recognize this block as bad. And ""dumpe2fs -b"" shows it. But this block is touched again and again. And I think that means that messages ""Programming error? block #?????? claimed for no reason in process_bad_block"" are irrelevant to this issue. And that link I've mentioned is irrelevant too."
1723417,2019-04-10 11:51:33 UTC,The same bug exists in OpenJDK-11 in disco:
1723423,2018-01-24 15:39:04 UTC,"I think the above fix introduces another issue, see https://bugs.launchpad.net/nova/+bug/1710141/comments/7."
1723423,2017-11-14 20:27:57 UTC,"Reviewed:  https://review.openstack.org/513678
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d25feca90ec4bad6ec9ececedced63b9f00b4c87
Submitter: Zuul
Branch:    stable/pike"
1723423,2017-11-15 01:10:36 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1723423,2017-10-20 09:25:55 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/513678"
1723423,2017-10-19 20:08:27 UTC,"Reviewed:  https://review.openstack.org/511844
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b25928dc0459e44c5cef8c1f16db76d779fbf556
Submitter: Zuul
Branch:    master"
1723423,2017-10-13 13:25:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/511844"
1723423,2017-10-24 12:41:43 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1723427,2019-02-20 10:28:14 UTC,@dmzoneill please ensure that the LP associated with a patch has its status correctly updated. Normally this is taken care of by gerrit but since in this case the format was nor correct on first submit the update didn't happen. I'll update this one but please remember for future patches.
1723427,2019-12-19 12:41:09 UTC,"Change abandoned by James Page (<email address hidden>) on branch: master
Review: https://review.opendev.org/636622
Reason: No response in 4 months to review feedback as requested - closing review."
1723427,2020-07-13 14:22:00 UTC,Assuming this is no longer being worked on since the patch was abandoned several months ago. I'll go ahead and remove the current assignee to allow someone else to take it on.
1723427,2019-02-13 13:14:41 UTC,Please consider:
1723431,2017-10-31 10:34:46 UTC,"Reviewed:  https://review.openstack.org/511904
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=8326d2c43c3e464f0c2e3b58bf57b4ffb9a344e7
Submitter: Zuul
Branch:    master"
1723433,2017-10-13 14:11:05 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
 QMessageLogger::fatal (this=this@entry=0x7ffca8563f10, msg=msg@entry=0x7fc520ccabd7 ""%s"") at global/qlogging.cpp:796
 init_platform (argv=<optimized out>, argc=<optimized out>, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at kernel/qguiapplication.cpp:1148
 QGuiApplicationPrivate::createPlatformIntegration (this=<optimized out>) at kernel/qguiapplication.cpp:1294
 QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at kernel/qguiapplication.cpp:1311"
1723433,2017-10-15 19:54:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723437,2017-10-13 15:27:31 UTC,The error in your log is:
1723439,2017-11-03 16:31:18 UTC,Syncing task from Mir.
1723441,2017-10-13 17:57:31 UTC,"> Can you provide more info as to what the situation was that was hard to debug with just the profile name.
"
1723441,2017-10-13 15:43:43 UTC,"Its possible, but would only be for a debug mode with correct authority. Can you provide more info as to what the situation was that was hard to debug with just the profile name."
1723445,2017-10-13 16:30:08 UTC,This change was made by a bot.
1723454,2017-10-13 19:04:37 UTC,Thanks for bug report. Backtrace is here:
1723454,2018-02-06 16:54:12 UTC,"No luck with the nullptr assumption. It segfaults on regular bodies.
I am unable to figure out what the problem is.
It is also not very reproducible, playing with the inspector can make the script pass the segfault point...
Bruno
___
code:
cerr<<""BodyContainer::erase -> reset: ""<<id<<"" ""<<(bool) body[id]<<endl;
body[id].reset();"
1723454,2019-02-05 20:25:46 UTC,moved from https://bugs.launchpad.net/yade/+bug/1723454 to https://gitlab.com/yade-dev/trunk/issues/37
1723460,2018-04-11 17:55:17 UTC,This is a problem with how some drivers are reporting link speed via sysfs.
1723461,2018-02-28 18:53:35 UTC,"As part of my work for creating a CLI UI, I implemented a basic yet functional logger, that writes log messages to the file indicated in the MOONSHOT_LOG_FILE environment variable. If the variable is empty, it does nothing, as the current logger :)."
1723462,2017-10-13 17:21:00 UTC,"I think most of this bug is about unity-greeter, except the last line mentions GDM."
1723482,2020-03-17 08:00:57 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1723482,2020-05-17 04:17:24 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1723488,2020-12-07 04:17:33 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1723488,2017-10-29 09:37:45 UTC,"The main problem is that HAX currently doesn't work properly at all on my both Windows 8.1 and Mac OS X 10.12.6 machines.
I can give other examples  if it is necessary"
1723488,2017-10-13 18:58:46 UTC,See https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-windows:
1723488,2017-10-13 18:06:54 UTC,It seems that HAX not working at all:
1723488,2020-10-07 18:39:05 UTC,Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays?
1723500,2017-10-13 19:23:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1723500,2017-10-14 18:12:02 UTC,"Yes, issue started when I upgrade from 17.04.
Latest v4.14 kernel fixed this bug, but network connection has gone."
1723513,2019-10-28 19:30:39 UTC,Is this issue still occurring? Have you been able to test this with a busy ONTAP controller?
1723520,2017-10-18 09:23:00 UTC, Debian now has been updated in unstable: https://tracker.debian.org/news/879500
1723530,2017-10-30 13:50:25 UTC,James: The PPA you had provided at Ocata worked for us. Could you push this through?
1723530,2017-10-17 07:24:05 UTC,Marking 'Incomplete' pending decision on whether trove can pop a new point release (preferable IMHO) or whether we want to cherry-pick into the package instead.
1723530,2017-10-16 17:06:44 UTC,"This package is part of the ‘universe’ section of the Ubuntu or Cloud archive.
Universe packages are maintained by the community, and the maintainers do not necessarily work for Canonical, therefore these packages are not always supported by Canonical directly.
The existing process to update packages in the Universe archive with patches, is as follows:
1. Upstream: Upstream your fix to the appropriate upstream project.
2. Debian: once your patch is ack’ed and accepted upstream, you need to request a merge of this patch to the package in Debian stable. https://www.debian.org/Bugs/Reporting use this link to report your issue and submit a fix.
3. Ubuntu: Once it is merged into Debian stable, request a merge of this package with Ubuntu. https://wiki.ubuntu.com/Debian/Bugs will provide you an overview on how to handle bugs that are reported to Debian and subsequently to Ubuntu.
- The merge request lands by default in Ubuntu's current development release (today ‘Artful’).
- If required an SRU may follow to get the changes into already released Ubuntu versions (like ‘Xenial’ or ‘Zesty’).
Work with the respective upstream maintainers (Debian and Ubuntu) is required during this process.  For critical issues we can advise you as you go through this process and help push the patches through by chasing the appropriate project contributors.
[To find out if a package is a universe package use: apt policy <package-name> or have a look at the Launchpad package page: https://launchpad.net/ubuntu/ ]"
1723530,2017-10-17 07:19:53 UTC,"As an aside, there are automatically built packages for all OpenStack services from upstream stable branches here:"
1723530,2017-10-16 19:45:53 UTC,"Actually things are a little different with regards to OpenStack packages in Ubuntu; the Debian OpenStack team has been a bit on and off over the last few years, so Ubuntu leads with OpenStack packages rather than the normal sync/merge flow with Debian, with git repositories on Launchpad for the Ubuntu package:"
1723530,2017-10-17 07:21:55 UTC,"Alternatively we can just pick the required fix into the package branch for ocata as a quilte patch.  In that case, its probably better that we raise Ubuntu tasks on bug 1671655 rather than doing a full point release (which I note that trove upstream has not done for the 7.x.x series yet)."
1723531,2019-01-19 01:55:03 UTC,"For what it's worth, it seems pretty simple to change the Non-Cataloged Types Editor into an Angular Basic Admin Page, which Bill Erickson made super-easy in the new Angular client.  These Basic Admin Pages include pagination *and* sorting, which seems like it would help out with long lists like PINES'."
1723531,2020-01-27 22:28:25 UTC,"This is now resolved in the web client (tested on 3.4.1), so marking this won't fix."
1723540,2017-12-07 20:46:00 UTC,Abandoned https://review.openstack.org/519739 - fixed the extra spacing in some logs and then was one space short in other logs.
1723540,2017-12-07 20:37:24 UTC,"Change abandoned by Ronelle Landy (<email address hidden>) on branch: master
Review: https://review.openstack.org/519739
Reason: This is an issue with some logs and not with others"
1723540,2021-02-18 16:45:49 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1723540,2017-11-14 20:08:45 UTC,Could it be that the reporter can't cut and paste??
1723540,2017-10-16 04:20:09 UTC,why was this set to alert?
1723540,2017-10-13 22:36:13 UTC,"Damn, I can't reproduce on my laptop. We need experts."
1723540,2017-10-13 22:29:18 UTC,I also need to remember what's my name.
1723540,2017-11-14 20:13:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519739"
1723554,2019-03-08 09:32:55 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1723554,2018-03-30 06:43:02 UTC,I think this is fixed in Gnome 3.28 (Ubuntu 18.04). Can anyone else confirm?
1723554,2017-10-20 03:42:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723554,2017-10-20 16:31:34 UTC,"@Daniel, thanks for the corrections."
1723554,2017-10-19 11:56:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1723554,2017-10-23 13:33:33 UTC,thanks for forwarding the issue
1723554,2017-10-20 03:41:55 UTC,"Confirmed. Although in 17.10 the default theme uses an orange border, not blue."
1723558,2021-01-08 14:30:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723559,2017-10-14 01:25:48 UTC,"StacktraceTop:
 gtk_tree_model_get_valist (tree_model=tree_model@entry=0x5633c40b2090, iter=iter@entry=0x7fff4d58e390, var_args=var_args@entry=0x7fff4d58e290) at ././gtk/gtktreemodel.c:1800
 gtk_tree_model_get (tree_model=0x5633c40b2090, iter=iter@entry=0x7fff4d58e390) at ././gtk/gtktreemodel.c:1762
 style_scheme_changed (treeview=<optimized out>, dlg=0x5633c403a430) at pluma-preferences-dialog.c:650
 g_closure_invoke (closure=0x5633c40a1be0, return_value=0x0, n_param_values=1, param_values=0x7fff4d58e5b0, invocation_hint=0x7fff4d58e530) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x5633c39d58a0, detail=detail@entry=0, instance=instance@entry=0x5633c3dc67c0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff4d58e5b0) at ../../../../gobject/gsignal.c:3635"
1723559,2020-11-20 04:17:20 UTC,[Expired for pluma (Ubuntu) because there has been no activity for 60 days.]
1723560,2017-10-14 01:43:29 UTC,"StacktraceTop:
 pa_threaded_mainloop_unlock (m=<optimized out>) at pulse/thread-mainloop.c:187
 tgvoip::audio::AudioOutputPulse::StreamWriteCallback (this=0x7fb3ac010f80, stream=0x7fb3ac019b20, requestedBytes=<optimized out>) at ./os/linux/AudioOutputPulse.cpp:286
 pa_command_request (pd=<optimized out>, command=<optimized out>, tag=<optimized out>, t=0x7fb3e4002da0, userdata=0x7fb3ac004a10) at pulse/stream.c:847
 pa_pdispatch_run (pd=0x7fb3bc00b280, packet=packet@entry=0x7fb3e400a960, ancil_data=ancil_data@entry=0x7fb3bc0013d8, userdata=userdata@entry=0x7fb3ac004a10) at pulsecore/pdispatch.c:346
 pstream_packet_callback (p=<optimized out>, packet=0x7fb3e400a960, ancil_data=0x7fb3bc0013d8, userdata=0x7fb3ac004a10) at pulse/context.c:349"
1723565,2017-10-17 00:05:43 UTC,"On 10/15/2017 10:43 PM, Daniel van Vugt wrote:

> This is probably either a bug in the GL code paths of clutter-gst, or
> gstreamer-vaapi.
>
> I don't suppose 'mpv' works for you with DVDs?
>
> ** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu)
>
> ** Also affects: clutter-gst-3.0 (Ubuntu)
>     Importance: Undecided
>         Status: New
>
> ** Changed in: clutter-gst-3.0 (Ubuntu)
>         Status: New => Confirmed
>
> ** Summary changed:
>
> - With vaapi plugin DVD_VIDEO  media renders quite poorly in wayland session
> + With gstreamer-vaapi installed, DVD video is flickering and green in a wayland session
>


While mpv isn't that suitable for dvd (dev's don't care about), it does
work ok with vaapi in wayland.
Ex. (currently muddling thru the new changes that you'll see in 0.28, a
bit of a pita. Have gotten  -
window deco but no vaapi
vaapi but no window deco
Anyway -"
1723565,2017-10-14 13:15:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723565,2017-10-16 02:43:03 UTC,"This is probably either a bug in the GL code paths of clutter-gst, or gstreamer-vaapi."
1723569,2017-10-14 04:03:01 UTC,"StacktraceTop:
 GCAL_IS_MANAGER (ptr=0x450) at ../src/gcal-manager.h:34
 gcal_manager_get_source (self=0x450, uid=0x7f7c6c080aa0 ""975163d4094bbee92398e15f414f6afde4f718a3"") at ../src/gcal-manager.c:1149
 add_source (manager=<optimized out>, source=0x7f7c6c078300, enabled=<optimized out>, user_data=0x559b69a80230) at ../src/gcal-source-dialog.c:321
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffe2d7d8290, fn=fn@entry=0x559b690a0a30 <add_source>, rvalue=<optimized out>, avalue=avalue@entry=0x7ffe2d7d81a0) at ../src/x86/ffi64.c:525"
1723569,2017-10-16 14:34:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1723569,2018-02-09 07:46:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723576,2017-10-14 05:24:21 UTC,"It appears you are supposed to import ""WebKit2"" now, but this has a different api..."
1723576,2017-10-15 09:51:43 UTC,Tested that:
1723576,2017-10-15 09:54:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723586,2017-10-14 09:11:54 UTC,"StacktraceTop:
 boxes_wizard_toolbar_set_title_for_page (self=<optimized out>, page=page@entry=4294967295) at wizard-toolbar.c:298
 boxes_wizard_set_page (self=self@entry=0x56244c722550, value=<optimized out>) at wizard.c:3906
 _boxes_wizard_page_____lambda144_ (obj=<optimized out>, _result_=0x56244ca54a10, self=0x56244c722550) at wizard.c:3692
 __boxes_wizard_page_____lambda144__gasync_ready_callback (source_object=<optimized out>, res=0x56244ca54a10, self=0x56244c722550) at wizard.c:3698
 g_task_return_now (task=0x56244ca54a10) at ../../../../gio/gtask.c:1145"
1723586,2017-10-16 22:06:55 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1723586,2018-01-09 11:49:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723588,2019-06-17 04:17:28 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1723588,2019-04-17 06:14:21 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
If yes, can you attach the output of ""lspci -nnv"" and ""lsusb"" to the report.
Thanks"
1723596,2018-01-31 12:51:46 UTC,PFA the snapshot of erroneous deployment
1723596,2017-11-20 18:29:13 UTC,Please attach full diagnostic snapshot.
1723597,2017-10-14 12:00:03 UTC,This change was made by a bot.
1723599,2017-10-14 18:03:25 UTC,The ugly plugin package shows proper info. Is it possible in the past sessioninstaller  fell  back to package info where packagekit  isn't doing that? If that's the case then why wouldn't this be packagekit's issue?
1723599,2018-02-19 20:29:28 UTC,"Still an issue in 18.04, also affects .swf"
1723612,2018-08-15 03:15:41 UTC,https://www.spinics.net/lists/platform-driver-x86/msg16304.html
1723612,2018-09-20 08:18:47 UTC,"$ gitoneline | grep ideapad | head -1
56c9bba135ab <email address hidden> 2018-08-15 13:17:48 +0300 platform/x86: ideapad: Add Y520-15IKBM and Y720-15IKBM to no_hw_rfkill"
1723612,2018-09-18 16:10:05 UTC,"My Lenovo Legion Y7000 also has no wifi. Please add it too.
$ cat /sys/class/dmi/id/modalias
dmi:bvnLENOVO:bvr8JCN44WW:bd08/13/2018:svnLENOVO:pn81FW:pvrLenovoLegionY7000:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoLegionY7000:"
1723612,2018-08-14 08:23:39 UTC,Thanks for your report. I am going to send this patch for upstream review and also think a good plan to blacklist all future ideapads. According to latest suggested design laptop vendor shall not have a physical radio switch.
1723612,2018-09-19 08:43:01 UTC,"@wxwok,"
1723612,2018-08-14 07:22:43 UTC,I thought this has been fix a long time and now find out we need Y520-15IKBM (not IKBN) as well. I assume that you need Y720-15IKBM in blacklist too. Is it?
1723612,2018-08-14 07:45:29 UTC,"I am interested in the Y520-15IKBM, but there is a Y720-15IKBM as well."
1723612,2017-10-14 15:18:39 UTC,As bypass I did a modprobe -r ideapad-laptop
1723612,2017-10-14 14:30:08 UTC,This change was made by a bot.
1723612,2017-10-16 09:43:06 UTC,Hi.
1723612,2018-08-13 13:53:34 UTC,"Any outlook when this will be fixed for Ubuntu? I see it is still not there in linux 4.18.
Suse LEAP 15 fixed this within 6 weeks after I reported it to Suse."
1723612,2017-10-16 08:43:51 UTC,"The description says ""Y720-15IKBM"" but your machine is ""Y520-15IKBM"". Can you confirm the latter one is what you want?"
1723613,2017-10-14 15:00:09 UTC,This change was made by a bot.
1723613,2017-10-14 15:03:00 UTC,"Similar bug reported here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174"
1723613,2017-10-16 17:34:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1723613,2017-10-16 17:35:02 UTC,"If the bug still exists in mainline, we can perform a kernel bisect to identify the commit that introduced this regression."
1723619,2017-12-25 18:56:56 UTC,"I stumbled upon this bug independently running Fedora 27 on Lenovo T420 with GeForce 119M, but because I plugged the monitor only after the boot I have a stacktrace with hopefully helpful dmesg log. I attached the log to the upstream bug report."
1723619,2017-10-18 09:26:07 UTC,For the record since I forgot to comment previously: kernel in #21 (mainline kernel with suspicious patch reverted) does boot fine with nouveau.
1723619,2017-10-18 20:40:00 UTC,"As discovered when testing the latest release of Ubuntu with (mainline) trees, commit 13a86519202c5d119d83640d6f781f3181205d2c seems to introduce a regression when booting with a screen attached to displayport (the system otherwise boots fine with the same kernel using an HDMI output)."
1723619,2017-10-18 20:44:35 UTC,A bug has been filed upstream here: https://bugs.freedesktop.org/show_bug.cgi?id=103351
1723619,2017-10-18 20:52:14 UTC,This appears to be a GM204.
1723619,2017-10-23 12:49:02 UTC,This issues persists in 4.14-rc6
1723619,2017-10-30 10:07:07 UTC,I just tested 4.14-rc7 and the issue is still present.
1723619,2017-12-24 23:53:04 UTC,I ran into the same issue on a Lenovo T420 with 01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [Quadro NVS 4200M] (rev a1).
1723619,2018-01-09 13:49:48 UTC,"(In reply to Nikita from comment #4)

> I ran into the same issue on a Lenovo T420 with 01:00.0 VGA compatible
> controller: NVIDIA Corporation GF119M [Quadro NVS 4200M] (rev a1).
"
1723619,2018-05-12 17:32:45 UTC,(In reply to Ilia Mirkin from comment #7)
1723619,2018-05-04 02:51:11 UTC,"This still exists on 4.17-rc3 with my GTX 980 (GM204).
Reverting 13a86519202c5d119d83640d6f781f3181205d2c gets my DP monitor working again. (My HDMI monitor works in both cases)"
1723619,2018-05-08 18:23:29 UTC,Just something I noticed... does this help? (Obviously without a revert applied.)
1723619,2018-05-09 14:36:51 UTC,"Have a similar problem. Ubuntu 18.04 with nvidia gtx 970. After the screen locks, it's impossible to wake it up. Need to disconnect and reconnect power to get it working again."
1723619,2018-06-14 14:41:24 UTC,"Could not install on GTX960 as well. Hopefully, 18.04.1 ISO installer on next July 26th will fix this issue with Nvidia DisplayPort."
1723619,2018-07-22 17:21:27 UTC,"Please try drm-tip [1] for this issue, there are some new runtime PM fixes for nouveau."
1723619,2018-09-30 15:01:30 UTC,This problem is still present within the 18.10 beta release
1723619,2019-09-18 20:45:54 UTC,-- GitLab Migration Automatic Message --
1723619,2017-10-17 19:13:32 UTC,I just tested 4.15-rc5 and the problem still persists.
1723619,2018-04-05 19:36:27 UTC,"Today's 18.04 upgrade from 17.10, using 4k or 1080 monitor with display port or with HDMI for Radeon RX 460 booting until bios,then screen flashing with jumbled colors every few seconds, shutdown displays Ubuntu logo.
Removing graphics card and using onboard HDMI for both is same as above, but shows Ubuntu loading animation, then no signal.
Starting without monitor the plugging in 1080 shows attached picture between flashing"
1723619,2017-10-17 18:01:37 UTC,"uname -r
4.14.0-rc5-lp1723619+revert"
1723619,2017-10-17 08:39:19 UTC,The previous one is good.
1723619,2017-10-17 09:33:51 UTC,"Mainline kernel with 13a86519202c5d119d83640d6f781f3181205d2c reverted:
http://people.canonical.com/~khfeng/lp1723619-revert/"
1723619,2017-10-17 12:19:23 UTC,"Unfortunately that commit says that it fixes regressions from something else, so I think it's too risky to simply revert it."
1723619,2017-10-14 16:08:03 UTC,I cannot run apport-collect because the livecd doesn't boot :(
1723619,2017-10-14 16:12:27 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1723619,2017-10-14 16:15:09 UTC,Another machine (GTX950m on an integrated screen) boots as well.
1723619,2017-10-14 16:21:51 UTC,Switching the faulty system to using HDMI + 1080p succeeded. Updating bug description.
1723619,2017-10-15 11:41:53 UTC,I think from you description you can install this system from the new ISO using hdmi.  Would you therefore be able to check out some of the interim kernels between 4.12.0-12 and 4.13.0-16 to see which of those work.  They should be available in the launchpad librarian.  Don't forget to install both linux-image and linux-image-extra when testing.
1723619,2017-10-15 20:04:51 UTC,I've done further testing as you suggested. Here's a breakdown of my findings:
1723619,2017-10-16 04:30:30 UTC,"Please try mainline kernel 4.13-rc*, so we can know which one contains the first bad commit that causes the regression."
1723619,2017-10-16 07:27:50 UTC,Tested all mainline kernels I could find for 4.13-rc*:
1723619,2017-10-14 16:09:27 UTC,"The livecd boots fine on another machine of mine with a nvidia GT 640 (so, an older generation), fromt eh same daily and same image burn."
1723619,2017-10-16 08:25:38 UTC,Do you know how you build kernel? I can build test kernels in deb format if you don't know how to make one.
1723619,2017-10-16 11:42:54 UTC,As discussed on IRC kaihengfeng and I will sync up tomorrow and bissect the problem together.
1723619,2017-10-16 14:31:32 UTC,Try kernel here: http://people.canonical.com/~khfeng/lp1723619-1/
1723619,2017-10-16 20:35:55 UTC,The kernel at #14 fails to boot.
1723619,2017-10-17 04:26:27 UTC,"But ""blacklist=nouveau modprobe.blacklist=nouveau"" can boot, right?"
1723619,2017-10-17 07:18:12 UTC,"Blacklisting nouveau allows a full boot (at a very low screen resolution, obviously)."
1723619,2017-10-17 08:03:08 UTC,"Built on commit prior to c11a93f5fd9229dc7c8b90570c75cf70bc3976c2:
http://people.canonical.com/~khfeng/lp1723619-3/"
1723619,2017-10-17 09:03:08 UTC,"Chris said 967003bb2cae121d345fd807eb757d9422229713 is good.
So the bad commit is
13a86519202c5d119d83640d6f781f3181205d2c drm/nouveau/i2c/gf119-: add support for address-only transactions"
1723619,2017-10-16 08:13:01 UTC,Then it's highly likely that the culprit is one of the following commits:
1723619,2017-10-14 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1723638,2017-10-15 15:24:39 UTC,"I just noticed that my RAW files and MOV files get corrupted 90% of the time when they are copied.
I can copy some of my files to an external device. Or I can rescue some of my files from the drives that I removed from this computer after this started. I access them via a USB interface."
1723638,2017-10-16 20:02:52 UTC,System failed to transfer file to USB memory-stick. Here is the relevant logs.
1723644,2017-10-17 08:24:35 UTC,apport information
1723644,2017-10-17 08:24:38 UTC,apport information
1723644,2017-10-17 08:24:35 UTC,apport information
1723644,2017-10-17 08:24:33 UTC,apport information
1723644,2017-10-17 08:24:37 UTC,apport information
1723644,2017-10-17 08:24:40 UTC,apport information
1723644,2017-10-19 10:40:44 UTC,Ok. I'll report back when the next kernel release launches.
1723644,2017-10-17 08:49:38 UTC,It truly might be a driver issue. Maybe an Qualcomm Atheros driver issue.
1723644,2017-10-18 17:12:18 UTC,A few days have passed but my installation still has issues. It didn't occur in Debian 9 or Debian Testing but it does in Ubuntu 17.10 and Ubuntu 17.04. Strange.
1723644,2017-10-19 05:37:26 UTC,It should be fixed with next Artful kernel release.
1723644,2017-10-24 15:21:38 UTC,"Ok, kernel version 4.13.9 fixed my issues. Hopefully the fix will land in the ubuntu kernel (currently using ukuu for doing this)."
1723644,2017-10-17 08:24:31 UTC,apport information
1723644,2017-10-17 08:24:42 UTC,apport information
1723644,2017-10-17 08:24:30 UTC,apport information
1723644,2017-10-18 17:12:42 UTC,Hopefully it won't take long to fix...
1723644,2017-10-17 08:24:28 UTC,apport information
1723644,2017-10-15 10:35:33 UTC,"Update: this also happens using wicd, but only after connecting to a network."
1723644,2017-10-15 21:56:28 UTC,Update: also affects Ubuntu 17.04.
1723644,2017-10-17 03:52:41 UTC,So it's more likely to be a driver issue.
1723644,2017-10-17 04:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1723644,2017-10-17 08:24:16 UTC,apport information
1723644,2017-10-17 08:24:17 UTC,apport information
1723644,2017-10-17 08:24:19 UTC,apport information
1723644,2017-10-17 08:24:29 UTC,apport information
1723644,2017-10-17 08:24:21 UTC,apport information
1723644,2017-10-17 08:24:22 UTC,apport information
1723644,2017-10-17 08:24:23 UTC,apport information
1723644,2017-10-17 08:24:25 UTC,apport information
1723644,2017-10-17 08:24:26 UTC,apport information
1723644,2017-10-17 08:24:27 UTC,apport information
1723644,2017-10-17 08:24:20 UTC,apport information
1723651,2019-08-26 16:56:32 UTC,"For reference, here's the Webkit bug on input type date not working in Safari on Mac OS X:  https://bugs.webkit.org/show_bug.cgi?id=119175"
1723651,2018-12-12 18:44:08 UTC,"This one should have had the pullrequest tag removed, but other things got in the way. I'm not actively working on this but may return to it at some point."
1723651,2018-07-08 22:38:47 UTC,It looks like the hint isn't displaying in Safari because it can't find the supportsType function (This error is also displays in the console in Firefox and Chrome).
1723651,2018-02-18 18:49:58 UTC,"Wish that I had a decent way to test with Safari, but I don't."
1723651,2018-02-17 16:59:23 UTC,"I asked somebody to test this in Safari earlier this week. Unfortunately, the hint did not display for them. There was just a text entry box in the form."
1723651,2018-01-02 16:53:47 UTC,I prefer #1.
1723651,2017-12-16 17:20:13 UTC,"There is already a check in the opac/parts/place_hold.tt2 template to check for the XUL client. If that is detected, then the text hint to enter the date in mm/dd/yyyy format is printed."
1723651,2017-12-13 23:54:25 UTC,I like it! What I most like about relying on the date input format is that the calendar widget changes depending on whether your are using a mobile or desktop browser. It means we don't have to worry about optimizing it for the different devices.
1723651,2018-01-20 17:37:13 UTC,I have rebased my branch on master and added a commit to do #1 from comment #3. I stole the function from quirksmode.org to check if a browser supports a particular element.
1723651,2017-11-16 13:22:14 UTC,Branch is user/dyrcona/lp1723651-html5-date-input-in-opac in the working repository.
1723659,2017-12-18 12:06:47 UTC,"This is still broken in 3.0.5, released last month."
1723659,2018-01-24 22:26:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1448
1723662,2017-10-17 13:11:05 UTC,"committed in pbienst, thanks!"
1723663,2019-08-14 04:17:21 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1723663,2019-06-14 17:03:26 UTC,What will the install time journal get us that is not in syslog and ubiquity's debug log? Are there issues that we are having a hard time debugging that the install time journal will fix? I ask as I'm trying to judge the usefulness of fixing this.
1723663,2017-10-16 23:42:42 UTC,We already copy syslog and ubiquity's debug log; I agree we should make sure we have as much debug info as possible after install.
1723663,2017-10-25 13:09:08 UTC,"Did the persistent journal get enabled by default?  Last I checked, we did not do that and just left the on disk logging to rsyslogd still."
1723670,2017-10-17 13:10:36 UTC,"committed in pbienst, thanks!"
1723678,2019-12-30 01:52:12 UTC,This bug is closed. I have reopened bug 1769116 for current releases.
1723678,2019-12-27 01:47:03 UTC,Same bug in Ubuntu 19.10
1723678,2019-11-26 04:15:13 UTC,apport information
1723678,2019-11-26 04:15:12 UTC,apport information
1723678,2019-11-26 04:15:09 UTC,apport information
1723678,2019-11-26 04:15:08 UTC,apport information
1723678,2019-11-26 18:24:05 UTC,"James,"
1723678,2019-11-26 04:15:05 UTC,apport information
1723678,2019-11-26 04:15:03 UTC,"ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-02-21 (277 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS ""Bionic Beaver"" - Release amd64 (20190210)
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
Tags:  eoan
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-11-06 (19 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True"
1723678,2019-11-26 04:04:38 UTC,"I'm getting this in 19.10, could you revisit the won't fix?"
1723678,2019-06-04 02:29:22 UTC,"The original bug here was reported against 17.10 which is now past end of life. And comment #3 while similar, is a different problem."
1723678,2019-06-03 21:28:32 UTC,"Same problem on 18.10. Every app crashes after powersave or what else it is doing, and the I have to login again in a new session."
1723678,2019-03-20 19:02:25 UTC,Ubuntu 18.04.2 up to date at 20/3/2019
1723678,2018-05-10 02:47:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723678,2019-11-26 04:15:06 UTC,apport information
1723679,2017-10-20 15:30:38 UTC,ubuntu-release-upgrader-core is a binary package provided by the source package ubuntu-release-upgrader. Launchpad tracks source packages as the code changes happen in the source package which produce the binary.
1723679,2017-10-16 15:34:39 UTC,"I accepted your offered alternative to the package I identified because you say the package I identified is not part of Ubuntu, but the list of packages (https://wiki.ubuntu.com/Bugs/FindRightPackage (as accessed 10-16-17)) lists it unless I misunderstand your version numbering."
1723679,2017-10-16 15:21:16 UTC,"I've now tentatively identified the package (I didn't see it before). You also request logs from </var/log/dist-upgrade/>, but that directory is empty even for sudo. I don't have a chat setup."
1723679,2017-10-15 00:25:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1723679,2017-10-20 00:49:25 UTC,"Correction: While this website's list of packages identified ubuntu-release-upgrader-core as the likeliest package for this report, reporting that package was refused by the website, preferring ubuntu-release-upgrader, all this was on 2017-10-16, and I had the version numbering right. I don't know enough to figure out which package or package name it should be. Thanks."
1723680,2020-01-25 23:12:09 UTC,I would have marked it for bionic only if it affected bionic too.  This should have a bionic task in addition to artful
1723680,2018-07-24 09:31:23 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1723680,2017-12-19 07:41:05 UTC,"Possibly this bug? https://bugs.freedesktop.org/show_bug.cgi?id=102435
-> Ubuntu 17.10's Mesa 17.2.2 seems to be broken"
1723680,2018-01-06 16:47:01 UTC,reply to Hosrt Schirmeier:
1723680,2017-10-28 03:31:18 UTC,Following bug reporting instructions for DRM i915 reported here:
1723680,2017-10-17 00:16:13 UTC,"Did this issue start happening after an update/upgrade?
     It started after upgrading to  17.10 artful aardvark."
1723680,2017-10-25 01:08:16 UTC,"v4.11 good
v4.12 bad"
1723680,2017-10-28 01:38:40 UTC,"bisect build                                    result
3dc38eea665f383c84cc8d858b9a7645c0b29c54        bad
72affdf                                         good
309663ab7b4f0de1540aff212fd067e3dd92acf3        bad
8ee7c6e23bb1b3c37ef27e81395db056bd7eac53        bad
ec151f31cd81cc99b957d6b528709d6ecfb25801        bad
1188bc66eb33e64ac7452b5acd62ce0395204148        good
f0a22974acbdd17b03cff4bdee880e4f08cccf6d        bad
9231da70b338b336b982c74fad4afab5b55e6534        bad
8448661d65f6f5dbcdb9c5cba185b284f2464b65        bad
cbc4e9e6a6d31fcc44921d2be41104425be8ab01        good"
1723680,2017-10-15 01:23:04 UTC,unable to run apport-collect without graphical env for browser.
1723680,2017-10-15 00:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1723680,2017-10-17 15:54:37 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1723680,2017-10-23 00:23:46 UTC,"I am unable to get useful debug info from the kernel for a bug report.  It hangs at a black screen and will not respond to any of the magic sysreq commands.  I tried the intel drm-tip too and same result.  Fully hung, can't ssh in, no console, nothing, completely wedged.  Don't want to send bug report without details."
1723680,2017-10-16 17:33:26 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1723681,2017-10-19 12:23:46 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1723681,2017-10-15 15:20:48 UTC,"Forgot to include:
Win 8.1, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1723681,2017-10-18 11:02:16 UTC,"Appears to be a duplicate of #1212136
"" ""Stroke to path"" command adds font info to style for item when it wasn't even a font to begin with"""
1723695,2017-10-17 18:56:23 UTC,The logfile says that you have many missing wagons. Install all the missing wagons and try again.
1723695,2017-10-17 23:50:11 UTC,"At first I did not realize that I have so many missing wagons so I check
them on Conbuilder and replaced them with another wagons. All good to go
and still the same with crash to desktop screen after click one of the AI
train in ALT + F9 Box. I believe that you still have to investigate this to
see why? Or I can send you a new log file to see with this. Let me know
about this."
1723695,2017-10-19 07:39:29 UTC,Please send a new log file.
1723695,2017-10-19 14:42:08 UTC,Can you give me a download link for the locomotive of the AI train where you want to jump in?
1723697,2017-10-18 18:35:16 UTC,"- confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1723701,2017-10-16 08:22:56 UTC,"To resolve the high load issue, could you please try OVS 2.7.3 or OVS 2.8.1. OVS 2.7.3/2.8.1 has a fix which should fix this issue."
1723701,2017-10-16 08:37:12 UTC,"2.7.3 of ovs/ovn stable must fix the high load. But still, I'm not sure if the ACL issue you're finding would be fixed by that (I say that because the ovn-db-sync fixes it)"
1723701,2017-10-16 08:37:33 UTC,"for
[DEFAULT]
service_plugins = trunk"
1723701,2017-10-24 03:58:54 UTC,"Thank you for the reply, settings service_plugins = trunk did not resolve the get_parent_port error."
1723701,2017-11-03 13:50:10 UTC,"@Justin, could you please repost the neutron server logs with debug enabled?
Thanks a lot!
Daniel"
1723701,2020-01-21 10:39:55 UTC,Thanks for reporting.
1723705,2020-01-24 10:01:13 UTC,"2266 reports on artful, then 2 on bionic. Sounds like it was fixed."
1723705,2018-01-29 02:18:39 UTC,"This issue is also being tracked in:
https://errors.ubuntu.com/problem/b3f30475bb4ce680bdb8c55709a9edecaf67adb2"
1723705,2017-10-15 05:42:54 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x556d4a1ff3f0, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4025
 g_value_set_object (value=0x7ffe28153830, v_object=0x556d4a1ff3f0) at ../../../../gobject/gobject.c:3880
 object_get_property (value=0x7ffe28153830, pspec=0x556d48d36b00, object=0x556d4a1fee70) at ../../../../gobject/gobject.c:1394
 g_object_get_property (object=0x556d4a1fee70, property_name=<optimized out>, value=value@entry=0x7ffe28153830) at ../../../../gobject/gobject.c:2591
 get_prop_from_g_param (priv=0x556d4a1fe480, value_p=..., name=<optimized out>, context=0x556d483aae00, obj=...) at gi/object.cpp:289"
1723705,2017-10-17 08:13:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723719,2017-10-15 11:36:32 UTC,"I do not have mpd on the machine I reported this from, but in another machine with same distro release."
1723719,2017-10-15 11:43:10 UTC,Latest version I tested was mpd 0.20.4
1723720,2017-10-15 11:51:08 UTC,"For further evidence that this question is being asked at the wrong time, consider the case where you try to register a name that is already taken:"
1723723,2017-10-15 20:49:37 UTC,When I have headphones in the sound is ok. When its playing via the laptop speakers its skipping crackling and pretty unusable.
1723725,2017-10-31 09:05:22 UTC,"The autodeletion is not mandatory? The database is deleted after each test?
https://specs.openstack.org/openstack/neutron-specs/specs/juno/remove-unit-test-autodeletion.html"
1723725,2017-11-01 11:35:54 UTC,"Even if that's the case, the codebase is not following the guidelines there. Disregarding that, for example in the case of networking-odl this has a real impact, since ODL is not part of the cleanup of that DB; but I guess this needs to be contemplated in networking-odl, given the document you pointed to."
1723726,2018-06-15 15:46:25 UTC,In addition:-
1723731,2020-11-10 03:06:14 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1723731,2021-01-09 04:17:55 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1723733,2017-10-17 10:34:16 UTC,"I can't repeat it at the moment when I want, but it repeats approximately after an hour of using Libre Office Writer."
1723733,2018-01-16 08:07:17 UTC,I've experienced the same issue -- hang while editing using Libre Office Writer.
1723737,2017-10-25 18:49:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723737,2017-11-27 09:18:46 UTC,"Are you trying to use it with an X session or with the Wayland one? If it's about X, then this will be fixed when the latest upload to Debian reaches Ubuntu. If it's about Wayland, there won't be a fix yet."
1723742,2017-10-15 13:40:28 UTC,"(1) is intended. You could wish to Ctrl-G jump to other locations.
(2) is a bit harder to solve."
1723742,2017-10-21 18:59:31 UTC,"I've added config option (and GUI option) to hiding nomenclature on the celestial body of observer (enabled by default), so, the point 1 is solved IMHO."
1723742,2018-09-26 05:06:19 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/401
1723750,2017-11-22 11:16:26 UTC,The issue still prevails in FF57.
1723750,2018-02-14 14:31:09 UTC,Same issue in FF 58.0.2
1723756,2018-12-18 12:40:20 UTC,Reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/319
1723756,2017-11-01 09:20:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723756,2017-10-15 16:50:41 UTC,"StacktraceTop:
 on_notification_dismissed (button=button@entry=0x0, user_data=0x55f652f084b0, user_data@entry=<error reading variable: value has been optimized out>) at cc-printers-panel.c:674
 on_remove_printer_timeout (user_data=<error reading variable: value has been optimized out>) at cc-printers-panel.c:693
 g_timeout_dispatch (source=source@entry=0x55f6522a23f0, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4633
 g_main_dispatch (context=0x55f65149cd10) at ../../../../glib/gmain.c:3148
 g_main_context_dispatch (context=context@entry=0x55f65149cd10) at ../../../../glib/gmain.c:3813"
1723756,2018-12-12 15:23:13 UTC,"That's still an issue in 18.10, see https://errors.ubuntu.com/problem/0aded438d4c3bdc3d33475360cc51f2aa67e9201"
1723757,2018-02-14 01:52:28 UTC,"Oops: the issue was that I tried using the same .encfs6.xml file for both. Using the one from /etc fixed the problem. Still, it would be nicer to receive a meaningful error message when this occurs to indicate the .encfs6.xml is the wrong one."
1723758,2017-10-15 16:19:47 UTC,Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=93828
1723758,2017-05-03 07:31:47 UTC,"xorg-x11-drv-nouveau-1.0.14-2.fc25.x86_64
xorg-x11-server-Xorg-1.19.3-1.fc25.x86_64"
1723758,2017-05-03 07:33:11 UTC,"Created attachment 1275841
journalctl  -b -1 | grep nouveau"
1723758,2017-08-25 10:59:18 UTC,"ago 22 15:59:43 p50.tole.es kernel: nouveau 0000:01:00.0: Xwayland[28959]: nv50cal_space: -16
ago 22 15:59:43 p50.tole.es kernel: nouveau 0000:01:00.0: Xwayland[28959]: nv50cal_space: -16"
1723758,2017-08-31 07:30:53 UTC,"BTW, I can connect via ssh from phone to laptop and 'reboot' it, so it's just the graphics layer the one frozen (it tends to happen once per day at least)"
1723758,2017-09-13 15:24:59 UTC,"The nouveau driver hangs with mythfrontend.  My system is a desktop intel i7 onboard graphics running kde plasma and a separate user (seat) running mythfrontend directly on X (not kde) using an nvidia GT240   The allows me to use my desktop system at the same time the TV is running mythtv in an adjacent room.  When the nouveau driver hangs it has no affect on the desktop system, the last frame or menu remains static on the TV even after restarting the mythfrontend application."
1723758,2017-09-21 11:14:49 UTC,Probably duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=979659 but still present in Fedora
1723758,2017-10-15 17:33:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723758,2017-01-05 18:13:12 UTC,This workarounded this issue by using nvidia 340 drivers. But after upgrade to Fedora 25 these drivers were not available for rather long period. Since there was nothing done in this bug for almost a yeat I tried to replace hardware.
1723758,2017-10-17 14:34:40 UTC,Might not have changed a thing
1723758,2017-10-17 14:51:42 UTC,According to the changelog for the hwe deb
1723758,2017-10-23 12:37:47 UTC,No lock-ups after 6 days of using HWE kernel and Xorg.
1723758,2017-10-29 11:16:14 UTC,I'm almost on day 12 of using HWE kernel and Xorg now. No lock-ups.
1723758,2017-10-31 11:21:55 UTC,Xorg crashed after 13 days 20 hours and 28 minutes of running.  The root cause is unknown to me; I can only trace it back to gnome-session-binary running out of file descriptors and crashing on a SIGSEGV which cascades until a nouveau driver message about receiving a signal occurs.
1723758,2018-03-30 11:16:59 UTC,I haven't seen this issue in a long time.
1723758,2019-05-26 08:04:09 UTC,"Hello, this happens also in ubuntu 18.04."
1723758,2020-07-10 09:04:50 UTC,I have had bug with locks up too.
1723758,2017-10-17 14:13:05 UTC,To see if this has been fixed in newer versions I am now running after having installed:
1723758,2016-12-31 12:50:21 UTC,I had to replace my graphic card now as the old one died now. So could these problems arise from memory corruption in a dying card? I have now a GTX 550ti which has not shown these error messages yet.
1723758,2019-12-04 09:10:12 UTC,-- GitLab Migration Automatic Message --
1723758,2016-12-01 20:14:54 UTC,"I tried to switch to modesetting driver, but my X sessions are crashing also. I attached crash info recently."
1723758,2016-01-22 21:10:25 UTC,"Xorg hangs randomly with nouveau driver. It could be reproduced cometimes when playing video or starting libreoffice, but not limited to. If pressing Ctrl+Alt+Backspace, monitor goes to sleep immediately. Alt+Sysrq combinations are usually working and also ssh."
1723758,2016-01-22 21:12:26 UTC,What hardware? What kernel version? What mesa version?
1723758,2016-01-22 21:19:48 UTC,"Just forgot to mention, I am running xorg-x11-drv-nouveau-1.0.12-1.fc23.x86_64
 version (latest from fedora 23 repository)."
1723758,2016-01-24 07:53:52 UTC,"Hardware:
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. EN210 SILENT
        Flags: bus master, fast devsel, latency 0, IRQ 45
        Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at d0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at e000 [size=128]
        Expansion ROM at fe000000 [disabled] [size=512K]
        Capabilities: <access denied>
        Kernel driver in use: nouveau
        Kernel modules: nouveau"
1723758,2016-04-26 01:01:05 UTC,My machine locks up several times a week.  From /var/log/messages I see:
1723758,2016-04-27 00:20:36 UTC,"Apr 26 16:54:45 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE]
Apr 26 16:54:45 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: 00100000 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 08b8 data 00040314
Apr 26 16:54:57 jschmitt-dt audit[14074]: <audit-1326> auid=1620 uid=1620 gid=1620 ses=1 pid=14074 comm=""chromium-browse"" exe=""/usr/lib64/chromium-browser/chromium-browser"" sig=0 arch=c000003e syscall=273 compat=0 ip=0x7fac2cfcd4f4 code=0x50000
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: fifo: DMA_PUSHER - ch 2 [Xorg[1253]] get 00200355b4 put 00200355e0 ib_get 00000021 ib_put 000002dc state 80004244 (err: INVALID_CMD) push 00406040
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: fifo: DMA_PUSHER - ch 2 [Xorg[1253]] get 002003566c put 0020035698 ib_get 00000023 ib_put 000002dc state 80004244 (err: INVALID_CMD) push 00406040
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD]
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: 00100000 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 0234 data 0004488c
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE]
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: 00100000 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 023c data 003048b0
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE]
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: 00100000 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 0240 data 000002f8
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD]
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: 00100000 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 0234 data 0004488c
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE]
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: 00100000 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 023c data 003048b0
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE]
Apr 26 16:55:21 jschmitt-dt kernel: nouveau 0000:02:00.0: gr: 00100000 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 0240 data 000002f7
..."
1723758,2016-05-02 18:40:37 UTC,"Created attachment 1153011
nouveau error messages"
1723758,2016-05-26 23:42:56 UTC,This is getting worse and worse.
1723758,2016-07-19 19:25:40 UTC,"Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1723758,2016-08-24 13:01:54 UTC,I think I faced this exactly same crash today on Slackware 14.2 x86 system.
1723758,2016-12-27 02:29:50 UTC,"Hi Guys,"
1723758,2016-08-24 13:03:22 UTC,"Created attachment 126001
Kernel log when crash"
1723758,2016-09-30 20:53:00 UTC,I got the same problem here with randomly occurring freezes (only mouse pointer can be moved but I can still ssh into it).
1723758,2016-09-30 20:54:28 UTC,"Created attachment 126923
dmesg output for Debian Jessie + 4.7.2"
1723758,2016-09-30 20:55:13 UTC,"Created attachment 126924
Xorg.0.log for Debian Jessie + 4.7.2"
1723758,2016-11-05 15:52:31 UTC,"Hi,"
1723758,2016-11-06 22:31:56 UTC,With newer kernel I've got new messages... If it can help.
1723758,2016-11-12 11:49:41 UTC,"Created attachment 127928
Kernel trace"
1723758,2016-11-12 11:54:22 UTC,I attached a kernel trace which may be related. I got this when:
1723758,2016-12-01 20:12:35 UTC,"Created attachment 128304
Extraction of crash info when using modesetting driver"
1723758,2016-08-24 13:02:57 UTC,"Created attachment 126000
xorg-log after crash"
1723759,2017-10-15 16:59:15 UTC,"StacktraceTop:
 WTFCrash () at ../Source/WTF/wtf/Assertions.cpp:333
 WTF::StringImpl::~StringImpl (this=0x7fbf141ee360, __in_chrg=<optimized out>) at ../Source/WTF/wtf/text/StringImpl.cpp:120
 WTF::StringImpl::destroy (stringImpl=0x7fbf141ee360) at ../Source/WTF/wtf/text/StringImpl.cpp:146
 WTF::StringImpl::deref (this=<optimized out>) at ../Source/WTF/wtf/text/StringImpl.h:610
 WTF::derefIfNotNull<WTF::StringImpl> (ptr=<optimized out>) at ../Source/WTF/wtf/PassRefPtr.h:39"
1723759,2018-07-05 04:44:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723760,2019-03-31 12:34:41 UTC,I no longer see this issue with Virtualbox and Xubuntu either. I'm removing it from our release notes.
1723760,2019-03-28 12:59:26 UTC,I haven't seen this when I have followed the 18.10 and 19.04 development.
1723760,2017-10-18 20:20:56 UTC,"I am attaching logs from /var/log/installer directory, if of any help."
1723760,2019-03-28 09:26:18 UTC,Any updates on this bug report? I don't think I'm seeing this issue with QEMU/KVM.
1723760,2017-10-18 01:46:15 UTC,"Managed to reproduce this on a Vostro V130. I'll dig in to see if I can find the exact cause, but I suspect the ""caching"" that we do when we're about to reboot to break down somehow."
1723760,2017-10-18 01:44:46 UTC,Seems like this is more likely to be casper (or plymouth) than ubiquity. Reassigning. Ubiquity has already stopped at this point.
1723760,2017-10-18 01:17:29 UTC,"Had this problem after installing Ubuntu Budgie ISO 20171017.1 (auto-resize). As I was using a Vbox VM, I just forcibly shut down the VM and started it again. The install itself was fine."
1723760,2017-10-15 18:12:26 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1723760,2017-10-18 20:08:10 UTC,"After installing Ubuntu 17.10 http://cdimage.ubuntu.com/daily-live/20171018/artful-desktop-amd64.iso on virtualbox, VM did not reboot after pressing Enter at the end of the installation process.
I had some errors that could be seen, see attached image."
1723763,2017-10-18 17:54:04 UTC,"This also happens when you copy a link to the desktop from the menu instead of just linking. The app is marked with a cautionary sign and there is a warning message indicated on the taskbar which you can't see because the mouse doesn't respond and the dialog window is not displayed. Log out, log in again and click on the desktop link and it allows you to continue after warning about the app and the warning is reset."
1723767,2017-10-21 11:13:10 UTC,I switched to Unity desktop and it started work. The problem is new Gnome desktop. I wonder if Kazam is maintained any more.
1723775,2017-10-15 18:59:48 UTC,"StacktraceTop:
 ?? ()
 QFactoryLoader::instance (this=<optimized out>, key=...) at plugin/qfactoryloader.cpp:276
 QIcon::addFile (this=0x7ffc529eb790, fileName=..., size=..., mode=mode@entry=QIcon::Normal, state=state@entry=QIcon::Off) at image/qicon.cpp:843
 QIcon::QIcon (this=<optimized out>, fileName=...) at image/qicon.cpp:565
 ScalableEntry::pixmap (this=0x561e53bc6220, size=..., mode=QIcon::Normal, state=QIcon::Off) at image/qiconloader.cpp:515"
1723777,2017-10-16 02:05:37 UTC,"Thanks for the bug report, but the driver is a kernel component so I am reassigning it."
1723777,2017-10-16 02:30:06 UTC,This change was made by a bot.
1723777,2017-10-16 17:27:09 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1723777,2017-10-16 21:37:30 UTC,Reproes with the v4.14 kernel.
1723777,2017-10-18 10:37:24 UTC,"Reassigning to powertop package for a first look - I upgraded a PC laptop to 17.10, and I am seeing two usb devices (camera and keyboard) flagged as 100% busy and major consumers of power in powertop (whereas they were not before the upgrade)."
1723786,2017-10-16 13:51:04 UTC,was that after an import? the assert is similar to https://bugzilla.gnome.org/show_bug.cgi?id=719202
1723786,2017-10-15 19:49:30 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x7f1f04ab4b0e ""arraylist.c"", line=line@entry=967, func=func@entry=0x7f1f04ab4fb0 <__func__.14320> ""gee_array_list_real_get"", message=message@entry=0x55c2c7c39520 ""assertion failed: (index < _size)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x7f1f04ab4b0e ""arraylist.c"", line=line@entry=967, func=func@entry=0x7f1f04ab4fb0 <__func__.14320> ""gee_array_list_real_get"", expr=expr@entry=0x7f1f04ab4b1a ""index < _size"") at ../../../../glib/gtestutils.c:2459
 gee_array_list_real_get (base=<optimized out>, index=<optimized out>) at arraylist.c:967
 sorted_list_binary_search (self=0x55c2c7d8d920, search=0x55c2c7af9800, equal_func=0x7f1f00d77230 <g_direct_equal>) at ./src/SortedList.vala:168
 view_collection_real_get_next (self=0x55c2c7aded60, view=<optimized out>) at ./src/core/ViewCollection.vala:752"
1723789,2017-10-16 23:04:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723789,2017-10-23 03:46:18 UTC,Same problem here!
1723789,2017-10-23 10:21:45 UTC,I think this is a Firefox problem rather than an apturl problem:
1723789,2017-10-16 19:21:04 UTC,Same problem here!
1723797,2018-04-25 21:17:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723798,2017-12-01 13:00:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723800,2018-10-30 20:54:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723800,2018-10-30 21:22:50 UTC,Also god confused by this. After trying around and reading man pages over man pages I noticed that vim-editorconfig depends on vim-addon-manager. To put it simple: the package only registers the addon but does not install it. You have to run `vim-addon-manager install editorconfig` before you can use it.
1723802,2017-12-06 19:11:39 UTC,cheers - enc is the output after running with --verbose
1723802,2017-12-06 17:19:10 UTC,"Okay, then this is a new issue... Meh.
Verbose output would definitely help:
`killall gnome-software ; gnome-software --verbose`"
1723802,2017-12-06 16:21:21 UTC,Thanks Matthias for the feedback:
1723802,2017-12-06 16:00:55 UTC,"I bet this is because GNOME Software is built with fwupd support, but the fwupd daemon is not installed.
Can you please check if the fwupd package is installed on your system?"
1723802,2017-12-06 07:58:17 UTC,damn - wrong URL - https://bugzilla.gnome.org/show_bug.cgi?id=791295
1723802,2017-10-19 22:16:59 UTC,nothing on stdout
1723802,2017-10-15 22:11:41 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1723802,2017-10-17 17:28:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723802,2017-12-06 07:57:47 UTC,also reported this on bugzilla - https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1723802
1723802,2017-10-19 15:08:31 UTC,Hi - sorry to say it is seen each time you fire up gnome-software after login.
1723802,2017-10-19 21:43:39 UTC,Do you get any error on stdout if you stop the current instance and start a new one manually instead?
1723802,2017-10-19 14:55:21 UTC,Do you get that issue every time or only once? The journal log have quite some warnings but those are probably not the same issue than the bug
1723805,2017-10-15 21:40:34 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 __GI_abort () at abort.c:90
 __libc_message (action=(do_abort | do_backtrace | unknown: 4), fmt=0x7ffdf30acb00 """") at ../sysdeps/posix/libc_fatal.c:86
 ?? () at malloc.c:5430 from /tmp/apport_sandbox_eTPgk1/lib/x86_64-linux-gnu/libc.so.6
 ?? ()"
1723805,2017-10-16 13:41:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723809,2017-10-29 15:34:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723809,2017-10-29 15:43:20 UTC,This bug cropped up a few days ago.
1723809,2018-01-07 18:31:45 UTC,This affects me as well :(. Here is the output of `systemd-analyze time`:
1723809,2018-02-07 21:00:53 UTC,I am using Ubuntu 17.10 on different machines and noticed this problem only on a machine that was upgraded from earlier Ubuntu version. It does not affect my clean 17.10 installations. Could this be affected by (incompatible) settings of previous releases?
1723809,2018-03-03 17:20:35 UTC,"Karsten Tausche, I have a clean install and the service is blocking for 8 secs."
1723809,2018-05-22 16:32:16 UTC,"Real hardware running Bionic, MSI b350m prog motherboard with R3 1300x cpu. I must use a usb ethernet due to the onboard ethernet causing PCIe issues. I thought the extended freeze I was experiencing at boot up was caused by hardware driver issues I'm debugging, since I do not even get a log blurb if I hard reset, but I just happened to notice it is this bug by disabling quiet and splash."
1723815,2018-01-09 08:41:58 UTC,Any news here? I'm experiencing the same issue. Opening directory with 150 files takes half a minute. Opening directory with 3000 files is something endless. Ubuntu 17.10 and 2 Android devices Galaxy S7.
1723815,2017-12-02 16:35:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723815,2017-10-29 17:27:51 UTC,https://gitlab.gnome.org/GNOME/nautilus/issues/91
1723815,2017-10-16 13:23:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1723822,2017-10-17 17:09:24 UTC,"There are two issues here, one with apport and another with nautilus.  The nautilus package ships an apport-package hook and it is looking for information about plugins in /usr/lib/nautilus which is not where they are stored anymore."
1723822,2017-10-17 17:13:05 UTC,The issue with apport is that if the function package_versions is called in hookutils and packages is empty there is no handling for that so then it ends up crashing when trying to create the map. Once that is fixed apport will continue to produce a problem report even though the nautilus hook is broken.
1723822,2017-10-18 07:50:10 UTC,"Right, the nautilus multiarch dir is known, it's a minor issue but should be fixed (does apport provide an easy way to get the multiarch dir from a hook?)"
1723822,2017-10-18 07:56:41 UTC,"Brian, my understanding is that nautilus reports just get such info
https://launchpadlibrarian.net/340847171/HookError_source_nautilus.txt"
1723822,2017-10-18 14:48:06 UTC,"On Wed, Oct 18, 2017 at 07:56:41AM -0000, Sebastien Bacher wrote:

> Brian, my understanding is that nautilus reports just get such info
> https://launchpadlibrarian.net/340847171/HookError_source_nautilus.txt
>
> it means they don't include some of the extra info but those details are
> not important in most report
"
1723822,2017-11-16 03:03:16 UTC,This bug was fixed in the package apport - 2.20.8-0ubuntu1
1723822,2020-10-06 13:30:41 UTC,This bug was fixed in the package nautilus - 1:3.38.1-1ubuntu1
1723827,2019-06-14 01:51:22 UTC,See my report https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1832793
1723827,2020-03-24 12:24:58 UTC,This bug was fixed in the package gnome-shell-extension-appindicator - 33-1
1723827,2017-11-05 18:35:11 UTC,For me the best workaround is to switch to MATE DE.
1723827,2017-11-02 12:17:06 UTC,appindicator also scales the telegram icon. The size is very small to see the number of unread messages
1723827,2017-10-27 11:04:43 UTC,"Also witnessing this with the JetBrains Toolbox application. The icon is super small, but seems to function correctly otherwise."
1723827,2017-10-26 10:19:19 UTC,"This also affects the Dropbox indicator-icon, which additionally features no left or right-click menu. The behaviour is not consistent with other indicator-icons - the transmission status-icon, if enabled, appears correctly and features also a menu."
1723827,2017-11-05 18:18:49 UTC,"Any workaround for this?
Icons for telegram, brightness-indicator, syspeek and classicmenu-indicator terrible small!
Transmission icon is ok."
1723827,2017-10-19 10:02:47 UTC,Seems like gnome-shell is taking the icons-size value from css. We need to do the same in gnome-shell-extension-appindicator.
1723828,2018-01-10 20:01:52 UTC,"Yes I agree that we can check on the fips host bound to create the fip namespace.
But it would be complex now, since we are creating fip namespaces based on the gateway and not on floatingIP anymore, since we are supporting the Fast path exit."
1723828,2017-11-16 02:17:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520261"
1723828,2017-10-31 20:59:10 UTC,This can be closed as a duplicate of 1723891 right?
1723828,2017-11-16 01:36:32 UTC,"This is not closed as duplicate of 1723891:
    Fip agent port is created for 1723891.
    Fip ns is created on network node for this."
1723828,2017-10-18 05:51:30 UTC,"In my opinion, the snat namespace is needed for any centralized floating IPs, not the fip namespace.
The fip namespace is needed on all in one node or dvr_no_external compute nodes.
Am I right?"
1723828,2017-10-17 17:57:19 UTC,"The fip namespace is needed for any centralized floating IPs, for example, floating IPs assigned to VMs on the dvr_no_external compute nodes.  This is by design as Swami mentioned."
1723828,2017-10-16 04:29:30 UTC,"But the fip namespace is not needed on an network only mode.
Before creating the fip namespace, checking the existing of floating ips for this node maybe can distinguish network only node and all in one node."
1723828,2017-10-16 03:14:10 UTC,This is as per design. The fip namespace gets created when gateway is enabled. This will be used for floating ip.created on an all in one node.
1723828,2017-10-18 06:22:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/512937"
1723833,2017-10-21 05:55:06 UTC,Issue resolved with today's update. Please close this bug report
1723835,2019-12-11 10:23:01 UTC,"Click once to preview multiple windows, click again to minimize all of the app's windows."
1723835,2020-11-27 03:39:22 UTC,Yes. The easiest and fastest way is sometimes to switch workspace or minimize all windows. Inconvenient.
1723835,2020-09-20 17:03:43 UTC,"See the opensource project: https://github.com/jderose9/dash-to-panel
It works as expected (also same as windows 10)"
1723835,2018-11-01 10:45:34 UTC,"Dash to Dock v63 (released on Apr 02 2018) added the new click action “minimize-or-previews”. IMHO, this is by far the most user-friendly click action of all supported ones. Unfortunately, this didn't become the default in Ubuntu 18.10. Currently, the file"
1723835,2017-10-22 22:33:03 UTC,"I agree with this, if Ubuntu wants to make life easier for users in this new desktop environment minimize on click is essential to it, dash to dock fully supports that option so I dont know why it is not included in Ubuntu dock, I am using 17.10 and I really miss that functionality, also Ubuntu needs an integrated search like the one in Unity dash because default Gnome search is anything but useful, I needed to install gnome-search-tool to have access to proper search functionality, these two things I consider essential in making new Ubuntu desktop usable, currently it is neither a copy of Unity nor vanilla Gnome so it doesnt have strengths of neither, I understand this is a transitory phase, but in my opinion Ubuntu desktop needs to be either pushed towards copying Unity as much as possible with extensions (existing or new ones) and perhaps a MacOS like search or just leave it as vanilla Gnome with Ubuntu fonts and theme. Current state is neither Unity nor Gnome which doesnt serve much purpose in the long run. App indicators dont work properly either with some applications (tiny or non existent icons) while TopIcons Plus extension on Gnome 3.26 still works flawlessly."
1723835,2017-11-08 07:29:51 UTC,"The option is available in the prefs of dash to dock or via gsettings key. The option was indeed never default behavior in Unity, but we didn't expose it in any official UI but only ccsm IIRC. I can see Tweaks growing this option, similarly than ccsm, as the code is already there, for people who want to tweak it this way."
1723835,2017-11-07 23:25:16 UTC,See https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1714286
1723835,2017-11-07 23:20:17 UTC,Minimize single windows on click was neither a default behavior in Unity dock but at least the option to do so became available. I really hope it will also become available in Canonical-Ubuntu.
1723835,2017-10-22 22:19:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723835,2017-11-08 18:17:19 UTC,"Minimize on click was introduced in Unity Tweak Tool and many users liked it, personally I see no point in classic dock that does not have that functionality, clicking constantly on minimize button requires more mouse work and effort and if I dont use minimize button, but instead use the overview, why bother with a classic dock in the first place? I believe introducing the option for minimize on click in Dock settings would make many users happy."
1723837,2017-10-16 04:11:40 UTC,"Hello
Please give kernel information (output of command: inxi -S)"
1723837,2017-10-16 13:48:35 UTC,"Hello Etienne,
I am running on real hardware and the system is compulsively kept up to date with the software updater.
Something to note however, is I switched from Compiz to Marco+Compton and I haven't been able to reproduce the bug since making the switch."
1723837,2017-11-15 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1723837,2017-11-15 19:59:38 UTC,Unable to post logs because the system is no longer installed. Note that this problem only happens on Ubuntu MATE. It does not happen in standard issue Ubuntu 17.10.
1723839,2017-12-16 04:32:31 UTC,Still a problem.
1723839,2017-10-16 15:17:55 UTC,What desktop environment are you using?
1723839,2017-10-16 15:47:19 UTC,"Was using Unity before the upgrade, now it's Gnome."
1723839,2017-12-16 04:17:29 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1723839,2017-10-16 04:23:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1723840,2017-11-07 03:54:57 UTC,"Just realized new Firefox Electrolysis
(https://wiki.mozilla.org/Electrolysis) may not be compatible with
legacy plugins/add-ons.  May have to disable the incompatible legacy
add-ons."
1723840,2017-10-27 07:49:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723840,2017-10-30 20:59:09 UTC,Also affected on Ubuntu 17.10
1723851,2017-10-16 23:25:20 UTC,"Hmm, there was recently a switch in testing frameworks used by tempest/ostestr. I just merged something that should hopefully fix the issue (https://review.openstack.org/#/c/503209/). So once that is in, try pulling the latest and reinstalling."
1723851,2017-10-17 01:51:14 UTC,"Ok. The patch seems to be working fine.
BTW .. I see these messages when I running the Defcore certified tests. These are WARNING messages...but trying to understand what these mean?"
1723851,2017-10-17 16:57:44 UTC,The test names with warning messages are the tests with aliases due to test being relocated (patch changed) or renamed. Depending on the version of Tempest that you are running.  Your test run should only locate and run one of the tests in the alias list.
1723856,2017-10-16 05:56:35 UTC,Testing with the revert https://review.openstack.org/#/c/512177/.
1723856,2017-10-16 07:20:18 UTC,So reverting 4f627b4e8dfe699944a196fe90e0642cced6278f fixes the lbaas issue and hence the heat gate.
1723856,2017-10-16 14:02:47 UTC,"Proposed patch https://review.openstack.org/#/c/512199/
It was tested on https://review.openstack.org/#/c/512201/ and it looks that it fixes this issue so revert of 4f627b4e8dfe699944a196fe90e0642cced6278f is not necessary"
1723856,2017-10-16 14:39:33 UTC,"Base on comment #3, this appears to be something fix in neutron-lbaas, so perhaps the defect is best over there."
1723856,2017-10-27 19:23:58 UTC,This issue was fixed in the openstack/neutron-lbaas 12.0.0.0b1 development milestone.
1723856,2017-11-08 17:34:42 UTC,It affected only neutron-lbaas and fix for it is already merged: https://review.openstack.org/#/c/512199/
1723856,2018-02-06 00:08:19 UTC,"neutron-lbaas bug is maintained in octavia launchpad.
Let's move the project and mark it as Fix Released."
1723856,2019-12-23 07:20:40 UTC,This is occuring in Train release.
1723869,2020-07-01 21:17:38 UTC,The issue is fixed in newer GNOME versions according to the upstream report
1723869,2017-10-16 08:45:17 UTC,Thank you for your bug report. Do you use a touchscreen? There is a report with a similar backtrace on https://bugzilla.redhat.com/show_bug.cgi?id=1438645 so it's not ubuntu specific
1723869,2017-10-16 08:47:09 UTC,or https://bugzilla.gnome.org/show_bug.cgi?id=783960 upstream
1723869,2017-10-16 07:34:06 UTC,"StacktraceTop:
 _create_touch_event (seat=seat@entry=0x55609849c040, touch=touch@entry=0x0, evtype=evtype@entry=GDK_TOUCH_END, time=time@entry=105112726) at ././gdk/wayland/gdkdevice-wayland.c:2332
 touch_handle_up (data=0x55609849c040, wl_touch=<optimized out>, serial=<optimized out>, time=105112726, id=0) at ././gdk/wayland/gdkdevice-wayland.c:2451
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffc6b1102d0, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffc6b1103a0) at ../src/x86/ffi64.c:525
 wl_closure_invoke (closure=closure@entry=0x556098e75d10, flags=flags@entry=1, target=<optimized out>, target@entry=0x556098498800, opcode=opcode@entry=1, data=<optimized out>) at ../src/connection.c:935"
1723874,2017-10-18 23:39:47 UTC,"@jibel - can you check if this also occurs on older releases? The restarting code seems to have been there for a while, any idea if this is a new issue or has always been there?"
1723874,2017-10-18 23:42:50 UTC,"The fix for this will be in snapd-glib, it was never built with the assumption that snapd would restart in the middle of a transaction... This is somewhat tricky to add because we have to be careful for things to fail fast if snapd is not installed, but handle a restart during a transaction (which may never come back)."
1723874,2017-10-25 03:58:47 UTC,I have yet to test this in a real case but this change should fix this issue:
1723874,2017-10-25 23:36:47 UTC,Fix now in ppa:ubuntu-desktop/gnome-software (snapd-glib 1.24-0ubuntu1~ppa1). For me now I can install on first attempt.
1723874,2017-10-26 04:01:27 UTC,I re-uploaded as 1.24-0ubuntu0.17.10.1~ppa1 as this is the version number that will be used in the artful SRU.
1723874,2017-10-26 08:04:03 UTC,Installed as per the instructions and confirming this works as described.  Thanks!
1723874,2017-10-26 22:52:41 UTC,This bug was fixed in the package snapd-glib - 1.24-0ubuntu1
1723874,2017-10-27 01:43:16 UTC,This appears not to be an issue in Zesty/Xenial since that didn't use snapd-glib and makes a new connection for each request.
1723876,2017-10-16 07:51:13 UTC,"Oh shoot, no support for Github style code blocks. Err, and where's the edit this bug button?"
1723878,2017-10-16 08:11:50 UTC,"StacktraceTop:
 __GI___select (nfds=24, readfds=0x7fa9fbfee750, writefds=0x0, exceptfds=0x0, timeout=0x7fa9fbfee710) at ../sysdeps/unix/sysv/linux/select.c:41
 dht::DhtRunner::doRun(sockaddr_in const*, sockaddr_in6 const*, dht::SecureDhtConfig)::{lambda()#1}::operator()() const ()
 std::execute_native_thread_routine (__p=0x7fa9fc0086e0) at ../../../../../src/libstdc++-v3/src/c++11/thread.cc:83
 start_thread (arg=0x7fa9fbfff700) at pthread_create.c:465
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95"
1723878,2018-01-10 21:51:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723879,2017-10-16 08:40:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1723879,2017-10-16 21:59:51 UTC,"The link for the upstream bug is
https://bugzilla.gnome.org/show_bug.cgi?id=758575:"
1723879,2017-10-17 08:28:27 UTC,thanks
1723880,2019-09-27 09:00:39 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1723880,2019-08-28 16:01:02 UTC,"Reviewed:  https://review.opendev.org/663851
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=27b6c18c666389ee68935f28cf340b7673879d6f
Submitter: Zuul
Branch:    master"
1723880,2019-04-23 20:06:31 UTC,Blueprint https://blueprints.launchpad.net/nova/+spec/support-specifying-az-when-restore-shelved-server should be able to address this.
1723880,2017-10-16 15:24:24 UTC,Brought this up in the operators ML:
1723880,2017-10-16 14:03:29 UTC,"Hmm, sounds legitimate. The question would be what we should do about this. Should a user expect that if they created an instance in a specific AZ and shelve offload it, that when unshelving it the instance will go back into that same AZ? We don't allow overriding an AZ on unshelve, so we'd have to use what was in the original request spec and if that AZ is now gone, do we just ignore the AZ - some might consider that an error too."
1723880,2018-02-28 10:31:13 UTC,"Hi, I encountered another similar problem, the operational steps is:
1.Remove the host compute from the nova available zone and the compute host to nova_az, before the instance in the nova available zone, the available domain changed to nova_az.
2.Shelved the instance from the nova available zone(the current instance is in the available zone of nova_az)，when the instance vm_state=SHELVED_OFFLOAD.The available zone of the instance has become nova instead of nova_az.
3.Unshelved the instance failed,The log printed is also ""No valid host found for unshelve instance""."
1723881,2020-05-19 15:49:43 UTC,"Hello,"
1723884,2017-10-16 12:35:43 UTC,"After logout-login copy works again in the terminal. I will keep an ""eye"" on it and try to determine under what conditions the ""Copy"" stops working."
1723884,2017-10-16 12:43:58 UTC,I can reproduce by:
1723884,2017-10-16 13:13:14 UTC,"The same happens if I use a PHPstorm instead of gedit in the above example. So it seems that other applications ""take over"" the  copy-paste buffer and terminal is unable to write to it."
1723884,2017-10-31 17:47:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723887,2017-10-17 12:59:41 UTC,The full text of the above run is:
1723887,2017-10-17 13:00:18 UTC,And another one:
1723887,2019-01-07 13:25:05 UTC,"Given that it's been over a year since I've seen this, I'm going to mark these incomplete"
1723887,2019-03-09 04:17:44 UTC,[Expired for OpenStack Charm Test Infra because there has been no activity for 60 days.]
1723896,2018-09-26 04:44:05 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/391
1723903,2018-01-24 22:26:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1449
1723912,2019-12-04 08:38:32 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/569771
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1723912,2018-05-21 10:21:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569771"
1723912,2018-08-31 07:41:01 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/569771
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1723912,2018-08-31 07:40:39 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1723912,2019-12-04 08:38:23 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1723917,2017-10-18 01:13:30 UTC,"Please download the package or export ""COBBLER_LOADERS_SOURCE_ASIA"" from the url below:"
1723919,2017-10-16 16:36:42 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1723919,2019-12-02 21:17:24 UTC,Currently fixed on 2.4.0+
1723925,2017-10-16 14:56:32 UTC,"Good idea.  I always use pools for my final round pools, to get classement séparés, but this is a good idea too."
1723925,2017-10-19 08:35:39 UTC,Pas de soucis. C'est noté.
1723927,2020-08-12 12:45:43 UTC,Closing due to almost 3 years of inactivity.
1723927,2017-10-17 01:41:51 UTC,"Ersek, thank you very much!"
1723927,2017-10-17 01:52:36 UTC,I success to capture the OVMF debug log.
1723927,2017-10-16 12:06:20 UTC,"On 10/16/17 13:26, chan wrote:

> Public bug reported:
>
> Hi,
>
> I started windows server 2012 DC or redhat7.0, but boot failed by UEFI, and start process stop on
> ""TianoCore"" image by looking at VNCviewer.
>
> VM using the command:(redhat7.0)
> /usr/bin/kvm -name guest=ytest,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/run/lib/libvirt/qemu/domain-40-ytest/master-key.aes -machine pc-i440fx-2.7,accel=kvm,usb=off,system=windows,dump-guest-core=off -bios /usr/share/qemu-kvm/OVMF_CODE.fd -m size=8388608k,slots=10,maxmem=34359738368k -realtime mlock=off -smp 1,maxcpus=24,sockets=24,cores=1,threads=1 -numa node,nodeid=0,cpus=0-23,mem=8192 -uuid 8cf40bd6-258a-4550-ba4e-b38230547a11 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/run/lib/libvirt/qemu/domain-40-ytest/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -chardev socket,id=charmonitor_cas,path=/run/lib/libvirt/qemu/domain-40-ytest/monitor.sock.cas,server,nowait -mon chardev=charmonitor_cas,id=monitor_cas,mode=control -rtc base=utc -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device usb-ehci,id=usb1,bus=pci.0,addr=0x3 -device nec-usb-xhci,id=usb2,bus=pci.0,addr=0x4 -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x6 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -device usb-hub,id=hub0,bus=usb.0,port=1 -drive file=/vms/hw235/ytest,format=qcow2,if=none,id=drive-virtio-disk0,cache=directsync,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,pci_hotpluggable=on,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-fdc0-0-0,readonly=on -global isa-fdc.driveA=drive-fdc0-0-0 -global isa-fdc.bootindexA=2 -netdev tap,fd=48,id=hostnet0,vhost=on,vhostfd=50 -device virtio-net-pci,pci_hotpluggable=on,netdev=hostnet0,id=net0,mac=0c:da:41:1d:67:6f,bus=pci.0,addr=0x5,bootindex=4 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/ytest.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -vnc 0.0.0.0:9 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on
>
> qemu version: 2.7.1
> edk2 version: git://git.code.sf.net/p/tianocore/edk2.git, commit: cc0b456a05f8dd1ebfb9be485465be37e96999e7
> server: ProLiant BL460c G7, CPU: Intel(R) Xeon(R) CPU X5675  @ 3.07GHz
>
> Another, last version of edk2(compiled by myself) start guest is failed,
> too. But r15214 of edk2 start guest is ok(Download from
> http://sourceforge.net/projects/edk2/files/OVMF/, OVMF-X64-r15214.zip)
>
> Thanks in Advance
>
> ** Affects: qemu
>      Importance: Undecided
>          Status: New
>
"
1723927,2017-10-17 09:06:31 UTC,"""-bios /usr/share/qemu-kvm/OVMF_CODE.fd"" is *never* a correct option to boot OVMF."
1723929,2017-10-16 12:03:42 UTC,"I proposed a patch for this, but I'm not sure this is actually as simple as this: https://review.openstack.org/#/c/510160/1"
1723929,2017-10-16 13:20:43 UTC,"hi Radomir,
all the plugins configuration should be loaded automatically.
so delete it from images and copy the plugin configuration during start the container."
1723929,2017-10-20 09:15:33 UTC,"Hi, I'm RDO release wrangler, just to say that if an endpoint is not available, corresponding plugin is not enabled. No need to delete anything whether on the image or the package.
Also we can't change package to fit Kolla use case as we have many more consumers, package has been designed to fit as many reasonable use cases including Kolla's.
Feel free to ping me or contact rdo folks through our list or irc channel (#rdo @ freenode)"
1723929,2017-10-20 09:48:28 UTC,"I think we can safely remove the whole plugin-related logic from Kolla in there, since there is no need to individually enable or disable plugins — they can be all enabled, and if the corresponding service is not available, will simply not be active in Horizon."
1723929,2017-10-20 22:47:50 UTC,"Haikel,"
1723929,2017-11-22 02:53:09 UTC,This issue was fixed in the openstack/tripleo-heat-templates 7.0.5 release.
1723929,2017-12-04 21:05:12 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0b2 development milestone.
1723939,2017-12-05 14:05:38 UTC,"Hi,
   Any other thoughts on this?  I haven't upgraded since submitting this report, but I looked through the commit history and didn't see anything that would address this.  Currently, if one node goes completely offline, puppet runs fail on the other nodes."
1723939,2017-10-18 19:38:07 UTC,I think you need commit a2e9675cda2e9152569ce4ab0f69484c03fc7c93 (I32a7a9fa4b896871929fcae847bba3481df5b517) i.e LP https://bugs.launchpad.net/puppet-pacemaker/+bug/1718186
1723939,2017-10-19 13:00:29 UTC,Thanks for the follow up.  I've got that one applied already just as a local patch.  I believe this issue is different and occurs even with that commit applied.
1723945,2017-10-17 16:06:42 UTC,"Snapd defines SNAP_ARCH with deb architectures instead of triplets. Without it defining triplets for you, you cannot use LD_LIBRARY_PATH the way you're doing it now, since the snapcraft-defined stuff is evaluated too late. You can use a remote part as well as a wrapper to get close."
1723947,2017-10-16 13:53:45 UTC,Testing my suggestion at the moment and will then upload a git entry to review and RFC from people related to these changes/packages.
1723947,2017-10-16 14:05:48 UTC,"The following change would be the ""unblocker"" for now.
I lack any better idea as after some time I'm lost in the rabbit hole of what actually goes on in this test between pcre and mariadb - I didn't reach the stack size detection that was broken last time."
1723947,2017-10-16 14:06:50 UTC,Subscribing Robie and Ondřej to get their feedback as they worked on the last related uploads.
1723947,2017-11-21 16:23:01 UTC,"+1 to skip this test, IMHO. Ondřej, can you sort this in Debian please? I'd like to avoid an Ubuntu delta."
1723947,2017-11-21 22:26:30 UTC,Looks good to me.
1723947,2018-02-01 14:39:18 UTC,mariadb-10.1 (1:10.1.29-2) unstable; urgency=medium
1723948,2018-07-17 11:06:36 UTC,"Did the advice in comment #3 help?  I've not heard any response from this for a couple of months, so I'm closing this bug as Won't Fix. If this is still and issue, please feel free to reopen the bug."
1723948,2018-04-13 09:01:49 UTC,2018-04-12 18:22 GMT+02:00 Colin Ian King <email address hidden>:
1723948,2018-04-18 10:48:05 UTC,Not sure why there is little activity on the upstream bug report.
1723948,2018-04-12 16:22:03 UTC,This stack trace was also reported in bug https://github.com/zfsonlinux/zfs/issues/6917 in log https://github.com/zfsonlinux/zfs/files/1686101/kern.log.2.gz
1723952,2018-05-10 13:35:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/567592"
1723952,2019-01-18 02:55:51 UTC,"Reviewed:  https://review.openstack.org/567592
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/commit/?id=0b47a5ecc163153ba88f8a5808f3dc7426524153
Submitter: Zuul
Branch:    master"
1723952,2019-08-22 08:42:56 UTC,Seems like this bug was already solved.
1723955,2017-10-16 13:53:55 UTC,Are those 1.9 authentication details still accurate for 2.x?
1723955,2017-10-16 14:17:05 UTC,"Issue on docs GH repo:
https://github.com/CanonicalLtd/maas-docs/issues/636"
1723955,2019-09-19 11:54:05 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1723956,2017-12-15 13:45:09 UTC,"Pretty much every single one that would do a hostname lookup it seems. Tried ping, ping6, nc, wget; they all crash."
1723956,2017-12-14 20:43:26 UTC,"Thanks, adding a systemd task to this bug for libnss-resolve."
1723956,2017-12-14 20:46:09 UTC,"btw, the bug description says 'several network applets'.  Which besides nslookup do you see this with?"
1723956,2017-12-14 01:01:19 UTC,"Thanks.  Loading busybox-static-dbgsym and retracing this with gdb, I see the following backtrace:"
1723956,2017-12-07 09:34:30 UTC,"Steve, so I just manually gather a core dump and attach it here? I assumed this is what apport is for. I uploaded the crash report using the standard crash report window that pops up when I opened the issue. Do they just go straight to /dev/null instead of the maintainers?"
1723956,2017-12-06 21:42:37 UTC,"$ busybox nslookup google.com 8.8.8.8
Server:    8.8.8.8
Address 1: 8.8.8.8 google-public-dns-a.google.com"
1723956,2017-12-14 11:22:25 UTC,"Sure, here we go. It might be worth to note that this system was installed as 12.04 or 12.10 and dist-upgraded ever since, so maybe this would explain some oddities, although in general everything works just fine."
1723959,2017-10-16 16:09:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1723967,2017-11-20 11:14:17 UTC,"Hi,
We downloaded the PDF file from link shared and the print happens successfully with the 3.17.10 driver. No errors related to PS error seen. Do you have any logs captured in your test? If yes, please share it for our analysis. hp-check -t command will list the dependencies needed, please check if you see any errors from this command output."
1723967,2017-11-20 21:53:32 UTC,"Hi Afshan,"
1723967,2017-11-20 21:55:49 UTC,The full output of hp-check -t goes here: https://pastebin.com/EAbJWKWM
1723967,2017-11-28 09:14:55 UTC,"Hi,"
1723968,2019-12-18 08:35:35 UTC,"This RFE has been solved by the Backup and restore procedure AFAIK.
I think we can close it."
1723968,2019-12-18 08:39:06 UTC,"Hi,"
1723969,2017-12-01 12:17:10 UTC,"Hi,
Can you specify the folder name (and contents) which got created by the installer? We will check and update.
Also do mention the distro details where you are trying the installer file."
1723976,2019-05-31 05:45:46 UTC,"Problem happens randomly (I had the problem 2 times) I was moving a subfolder to a different folder in the partition named 'dati1'If the problem happens again i will try with 'ubuntu-bug nautilus'
here is my filesystem:
corrado@corrado-p7-ee-0507:~$ sudo lsblk -o NAME,LABEL,SIZE,FSTYPE,UUID,MOUNTPOINT
[sudo] password for corrado:
NAME    LABEL           SIZE FSTYPE   UUID                                 MOUNTPOINT
loop0                     4M squashfs                                      /snap/gnome-calculator/406
loop1                  14,8M squashfs                                      /snap/gnome-characters/258
loop2                  53,7M squashfs                                      /snap/core18/970
loop3                   151M squashfs                                      /snap/gnome-3-28-1804/40
loop4                   3,7M squashfs                                      /snap/gnome-system-monitor/81
loop5                  1008K squashfs                                      /snap/gnome-logs/61
loop6                  35,3M squashfs                                      /snap/gtk-common-themes/1198
loop7                  53,7M squashfs                                      /snap/core18/941
loop8                  89,4M squashfs                                      /snap/core/6818
loop9                  88,4M squashfs                                      /snap/core/6964
loop10                 14,8M squashfs                                      /snap/gnome-characters/272
loop11                  151M squashfs                                      /snap/gnome-3-28-1804/47
sda                   931,5G
├─sda1                  256M vfat     07D0-8A63                            /boot/efi
├─sda2                    8G swap     c86a81fa-1d97-483c-99f8-318382983ed7 [SWAP]
├─sda3  p3-cosmic        32G ext4     23a9d5ea-581c-401d-bb72-a9ad5fb9811e
├─sda4  p4-xenial        32G ext4     fb5dda68-061f-4076-b0a8-22eac04841ae
├─sda5  p5-disco         32G ext4     54a0ad2c-dedf-4cd8-8f98-4a4943816d91
├─sda6  p6-ee-0506       32G ext4     e2830031-8105-4aa0-9d53-f2eb3e654ecb
├─sda7  p7-ee-0507       32G ext4     fc641a6d-7cd7-416e-b694-145914908f24 /
├─sda8  p8-bionic        32G ext4     92362875-3d65-4b43-8cd4-3295eb79b959
├─sda9                   16G ext4     fdc19f0e-8552-4661-a8d3-ad29597768ab
├─sda10 dati1           256G ext4     dc880632-1403-4f5e-9c42-52b41bbe1b06 /media/corrado/dati1
├─sda11 dati2           256G ext4     b10bc991-9463-4010-be04-186d562d96dc
├─sda12 dati3         187,3G ext4     d7404e13-a307-4771-a1ec-1123cf5c85b2
└─sda13 p13-dd-0306-x    16G ext4     f601b984-03e1-4134-8bad-a620a6fcd170
sr0                    1024M
corrado@corrado-p7-ee-0507:~$"
1723976,2017-10-16 14:51:54 UTC,Similar report on https://bugzilla.redhat.com/show_bug.cgi?id=1406094 which describes several users hitting the issue when doing a dnd between windows
1723976,2019-05-29 11:42:11 UTC,"I have the problem with nautilus 1:3.32.1-0ubuntu1 in Ubuntu 19.10 Wayland session
move item to a different folder with mouse does not work, it seems just ignored but no crash.
sometimes i have an error message like the one in attachment
copy+paste works fine."
1723976,2018-02-09 13:06:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1723976,2019-05-29 11:57:35 UTC,"@Corrado, the bug you submitted and which got marked duplicate from this one was a segfault error though, your ""move to a different folder is not working"" seems a different error and worth another report. Also please describe what you do exactly, if this happens on any file/folder and what filesystem you are using"
1723978,2019-09-19 12:04:56 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1723987,2017-10-17 12:16:34 UTC,The attached is what I get when I try do-release-upgrade in a terminal (my username redacted). Not sure what is causing it to fail.
1723994,2017-10-23 13:20:45 UTC,apport information
1723994,2017-10-23 13:20:47 UTC,apport information
1723994,2017-10-23 15:47:51 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1723994,2017-10-23 16:06:30 UTC,"I've been seeing this issue for a while, but only just got around to filing it.  I'll test with the upstream kernel once I'm back at my desk."
1723994,2017-10-23 19:54:47 UTC,This does reproduce with the mainline kernel.
1723994,2017-10-26 12:17:36 UTC,"On Thu, Oct 26, 2017 at 07:38:58AM -0000, Kai-Heng Feng wrote:

> What's the output of `lsusb -t` with and without the monitor USB hub?
"
1723994,2017-10-24 15:26:07 UTC,"On Tue, Oct 24, 2017 at 03:43:38AM -0000, Kai-Heng Feng wrote:

> Does this happen on older kernel or earlier Ubuntu releases?
"
1723994,2017-10-26 15:09:12 UTC,"They should work, at least at initramfs stage. You can use the keyboard to decrypt rootfs proves that."
1723994,2017-10-26 15:20:57 UTC,"On Thu, Oct 26, 2017 at 03:09:12PM -0000, Kai-Heng Feng wrote:

> They should work, at least at initramfs stage. You can use the keyboard
> to decrypt rootfs proves that.
"
1723994,2017-10-27 03:45:26 UTC,"> On 26 Oct 2017, at 11:20 PM, Dan Watkins <email address hidden> wrote:
>
> On Thu, Oct 26, 2017 at 03:09:12PM -0000, Kai-Heng Feng wrote:
>> They should work, at least at initramfs stage. You can use the keyboard
>> to decrypt rootfs proves that.
>
> I can use the keyboard to decrypt the rootfs if it's plugged in after
> boot.  If it's plugged in before boot, it doesn't work.
>
> (It also continues to work on _reboot_; it's just on a power cycle that
> it doesn't.)
>
>> Does your lsusb in #11 captured when the keyboards didn't work?
>
> I'm not sure I understand the question; could you clarify?
"
1723994,2017-10-23 13:20:43 UTC,apport information
1723994,2017-10-24 03:43:38 UTC,Does this happen on older kernel or earlier Ubuntu releases?
1723994,2017-10-23 13:20:41 UTC,apport information
1723994,2017-10-26 07:38:58 UTC,What's the output of `lsusb -t` with and without the monitor USB hub?
1723994,2017-10-23 13:20:39 UTC,apport information
1723994,2017-10-20 21:24:31 UTC,This sounds like it would be a kernel issue.
1723994,2017-10-20 21:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1723994,2017-10-23 13:20:25 UTC,apport information
1723994,2017-10-23 13:20:27 UTC,apport information
1723994,2017-10-23 13:20:28 UTC,apport information
1723994,2017-10-23 13:20:40 UTC,apport information
1723994,2017-10-16 15:48:08 UTC,"(This _probably_ isn't cryptsetup specific, but I wasn't really sure where else to file it.)"
1723994,2017-10-23 13:20:31 UTC,apport information
1723994,2017-10-23 13:20:32 UTC,apport information
1723994,2017-10-23 13:20:34 UTC,apport information
1723994,2017-10-23 13:20:35 UTC,apport information
1723994,2017-10-23 13:20:36 UTC,apport information
1723994,2017-10-23 13:20:38 UTC,apport information
1723994,2017-10-23 13:20:29 UTC,apport information
1724001,2019-08-15 09:19:53 UTC,This was fixed with Vanilla 1.8 in MAAS 2.6
1724003,2020-09-14 07:37:32 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1724005,2019-09-19 12:04:59 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1724007,2019-09-19 12:05:01 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1724008,2020-08-31 13:40:37 UTC,Removing pullrequest tag due to obscured barcode field.
1724008,2020-08-28 17:49:01 UTC,Obscured barcode field in small screen view
1724008,2020-08-28 17:48:30 UTC,No barcode field in mobile view
1724008,2020-08-28 17:48:02 UTC,"Within the patron registration screen, the barcode field is completely obscured at full resolution and mobile view.  When viewed as a small screen but not yet mobile, the field is visible but only partially and without a label."
1724008,2020-08-25 22:19:03 UTC,"Thanks for your comment Galen.  I didn't realize that the fixed position was intended to keep the save buttons at the top of the screen.  I re-did my work, this time keeping the positioning fixed.   Also adjusted the z-index value of the title, so that the datepicker doesn't render on top of the title."
1724008,2020-08-24 15:15:49 UTC,"I'm not sure about that patch - by removing the fixed position from the patron registration form's toolbar, staff users would be forced to scroll all the way back up to the top of the page to save the record.  That was a pretty big deal when the AngularJS patron registration form was previewed in 2015; see comment #14 in bug 1452950."
1724008,2020-08-21 19:44:34 UTC,"Most of the originally reported problems have been fixed along with other improvements, so I just tested Mike's small fix to the Patron Registration form title overlap problem and have signed off on it here:"
1724008,2020-08-21 19:38:16 UTC,"Sorry, Erica - I just applied the last commit mentioned to fix the overlap of the title on the Patron Registration page. (Which does work now, btw - I'll sign off shortly.)"
1724008,2020-08-18 18:27:45 UTC,I am getting a merge conflict error when I try to cherry pick this to current master.
1724008,2020-08-19 00:00:30 UTC,The reason for the conflict is because of some edits pushed to master a couple weeks ago from bug #1805860.  These edits ended up resolving most of the patron page problems described in this bug.
1724008,2020-08-17 18:58:34 UTC,"Just looked at current master without the patch and it does work better than it did before but there are still some places where there is some overlap - for instance on the patron registration page, the page title gets hidden at that intermediate size, but the fields no longer get hidden. So I think Rogan is right that improvements have been made along the way, but it's probably still worth looking at these additional improvements."
1724008,2020-08-17 17:25:54 UTC,"Jsut a note that I wasn't able to replicate the original issue as described in Firefox or Chrome.  Perhaps other issues have helped address this?  I'm not removing any tags, just noting I couldn't replicate on current Firefox and Chrome on Mac."
1724008,2020-06-29 21:52:59 UTC,"Jason Boyer,"
1724008,2020-06-26 13:09:01 UTC,I tried this out and it does address most of the AngularJS parts of the client but patron pages have a large gap at the top and all of the Angular parts of the client (/eg2/) have similar problems with the bar overlapping content when the username and workstation are compressed. Images attached for both.
1724008,2020-03-16 23:42:23 UTC,"I pushed a branch that resolves this.  By adding ""position: sticky"" to the nav-bar we keep it in the page flow, so we shouldn't have the problem of it obscuring content.  However, this change impacts many pages of evergreen.  I've checked many places and see no problems, but please let me know if this has any negative side effects."
1724008,2018-02-01 21:04:14 UTC,"This is also an issue on Checkout screen.   The check out, items out, holds, etc menu stays put and obscures the screen when scrolling.  See attached."
1724008,2018-01-18 22:40:03 UTC,This is also a problem on the patron registration / edit screen when on a monitor with a moderate resolution. Attached screenshot shows the wrapped menu item and the inaccessible fields circled in red.
1724008,2020-08-21 18:07:14 UTC,"I was going to sign off on this fix. However, I'm not sure which fix is applied. I do not see the original behavior on other databases that I've tested to compare. Unassigned myself for testing."
1724009,2018-12-20 15:29:42 UTC,This is something we've wanted for a very long time!
1724019,2020-08-17 14:25:54 UTC,"Issue and fix confirmed, now with shared sort.  Merged to 3.4 and up.  Thanks, all."
1724019,2020-08-07 20:23:16 UTC,"Thanks for pointing out that sort_aou function, Jane. I agree we don't want to repeat code if we can help it. With some help, I changed the approach so that it's now using that function.  Branch here:"
1724019,2020-07-22 16:50:06 UTC,"Thanks, Mike. The patch works for me. However, I don't think we should have two separate sorting methods depending on whether or not the org selector is in the offline client or not.  I haven't tried it yet, but it seems like we could make a few changes to egEnv's (or maybe the lovefield service's) logic to use the existing sort_aou for offline calls as well. https://github.com/evergreen-library-system/Evergreen/blob/7c3cdbbd140865e07d08952422c82605ac8c5676/Open-ILS/web/js/ui/default/staff/services/env.js#L183"
1724019,2020-04-16 20:19:42 UTC,"Thanks, Mike! Works as expected now. My signoff at:"
1724019,2020-03-09 19:11:38 UTC,I re-did this work to preserve the org hierarchy when alphabetizing. Here's the branch:
1724019,2020-02-19 23:04:02 UTC,"Noting with relation to hierarchy2 - the Angular Org Selector doesn't currently support graying out of consortium/system-level orgs, but the functionality to do so will be present with bug 1863168"
1724019,2020-02-19 21:56:46 UTC,"Although it does alphabetize now, it has lost the hierarchy - see attached screenshot where you can see, for example, that CONS is down in the middle. Removing the pullrequest."
1724019,2020-02-19 22:52:06 UTC,"It should have the same hierarchy that the org units have - consortium level first, systems alphabetical under that, branches alphabetical within their systems."
1724019,2020-02-19 22:34:52 UTC,This was done intentionally because my understanding is that was what was being requested. Could you help me understand the desired behavior?
1724019,2020-02-19 19:33:20 UTC,"I have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>."
1724019,2020-01-17 21:28:23 UTC,I've pushed a branch with a fix.
1724019,2018-05-29 16:22:28 UTC,Still not sorted alphabetically in 3.1.
1724019,2018-04-04 14:38:48 UTC,Evergreen 3.0.6
1724019,2020-02-19 22:55:13 UTC,"Here is what it currently looks like in production - the hierarchy is there, but the systems aren't in order and the branches within each system aren't in order, so it's difficult to find the one you are looking for."
1724023,2017-10-16 20:01:55 UTC,Horrendously insecure but fixes this issue too. Not recommended for fix but does work.
1724023,2017-10-16 17:38:11 UTC,Actually looks like the issue is in https://git.openstack.org/cgit/openstack/faafo/plain/contrib/install.sh. Its attempting to do it but however its intending to do it it doesn't work for ubuntu 16.04. Will update if I find a workaround.
1724023,2017-10-16 18:22:58 UTC,"using this diff on https://git.openstack.org/cgit/openstack/faafo/plain/contrib/install.sh allows faafo list to work, faafo create etc."
1724023,2017-10-16 19:53:11 UTC,The 0 byte issue is due to workers not being able to auth against the messaging server. Since Rabbitmq 3.3.x the guest user cannot connect remotely.
1724032,2018-05-22 23:46:50 UTC,"I'm able to access the ID of a patron's permission group with {{patron.profile}} on the hold shelf slip print template.  This is on 3.1.  It only gives you the id number -- not the actual name of the patron's permission group -- but if you know the IDs of the relevant permission groups, it should be enough for adding the logic you describe to the template."
1724032,2020-12-16 23:21:45 UTC,Some of our libraries would like the actual name of the patron's permission group to print on the hold slip
1724032,2020-12-17 14:29:14 UTC,I agree that the permission group name should be available to the Hold Shelf Slip template.
1724034,2017-10-17 08:36:46 UTC,This problem is down to a print setting in LibreOffice > Print > Options > 'un-tick Create single print jobs for collated output'solves this issue. But printer icon no longer appears notification area.
1724034,2020-05-22 04:17:24 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1724035,2018-10-02 20:18:47 UTC,"We don't currently support this form of full-disk encryption without the manual interventions you mentioned, and the installer currently sets up encryption is a way that things will work."
1724037,2020-08-11 05:53:18 UTC,It's probably best not to implement fractional scaling below 100% because it would have the same performance problems as Xorg fractional scaling already does.
1724037,2020-05-13 09:19:55 UTC,That's probably bug 1717453 :(
1724037,2020-05-13 09:04:33 UTC,"@Daniel van Vugt, it doesn't work on Gnome Shell."
1724037,2020-08-11 05:41:56 UTC,Ironically this is how Xorg fractional scaling already works. So it's definitely possible but we have no GUI to configure it.
1724037,2020-05-13 06:59:48 UTC,I also think this is needed. I'm on focal fossa and everything is so big. I'd imagine it's good on WQHD and above screens but it sucks on my screen which is Fulll HD.
1724037,2019-12-24 13:21:36 UTC,"Display scaling below 100% is very much required to run on lower resolution displays.
Text scaling is not enough for that."
1724037,2018-10-17 00:59:13 UTC,I believe this is about display scale (in Display settings) - not about font.  I'm also looking for a way to scale the display below 100%.
1724037,2017-10-17 02:24:47 UTC,"It is mostly possible in 17.10 already, except there is no nice GUI for the setting and icons in the dock and headerbars will refuse to scale down. Try:"
1724037,2020-05-13 07:08:03 UTC,"As a workaround, and arguably better solution, do what I do:"
1724039,2017-10-16 20:27:24 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/512406"
1724039,2017-10-18 22:10:31 UTC,"Reviewed:  https://review.openstack.org/512406
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5d5c5a5d92458d530115b3d3b8b381524b1a3a90
Submitter: Zuul
Branch:    stable/ocata"
1724039,2017-11-15 01:06:50 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1724047,2020-04-21 17:31:15 UTC,"That didn't work either. Using the ""intel"" driver with:"
1724047,2020-04-14 17:22:54 UTC,"Well, that didn't work for very long. Disabling the acceleration of the ""intel"" driver did not solve the problem for me. I tried three more changes, described below."
1724047,2020-04-05 15:55:50 UTC,I started to see the same GPU HANG error sometime this year (2020).
1724047,2020-04-05 15:25:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724047,2017-10-17 05:22:02 UTC,that hang comes from the kernel
1724047,2020-04-06 16:13:49 UTC,"I just hit another GPU HANG, this time with the ""intel"" driver instead of the ""modesetting"" driver. The kernel log file (/var/log/kern.log) shows:"
1724058,2017-10-19 09:44:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724058,2017-10-19 09:58:53 UTC,Encountered the same issue during ISO Testing. From the traceback I see this should be really simple to fix.
1724058,2019-07-26 06:36:15 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1724061,2017-10-16 19:57:21 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x7f9250341c8d ""gstaudiodecoder.c"", line=line@entry=1505, func=func@entry=0x7f9250343c70 <__func__.21898> ""gst_audio_decoder_push_buffers"", message=message@entry=0x7f91e84a57f0 ""assertion failed: (offset + len <= av)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x7f9250341c8d ""gstaudiodecoder.c"", line=line@entry=1505, func=func@entry=0x7f9250343c70 <__func__.21898> ""gst_audio_decoder_push_buffers"", expr=expr@entry=0x7f9250341fc0 ""offset + len <= av"") at ../../../../glib/gtestutils.c:2459
 gst_audio_decoder_push_buffers (dec=dec@entry=0x7f91e83d1d10, force=force@entry=0) at gstaudiodecoder.c:1505
 gst_audio_decoder_chain_forward (dec=dec@entry=0x7f91e83d1d10, buffer=0x0, buffer@entry=0x7f91e8051af0) at gstaudiodecoder.c:1652
 gst_audio_decoder_chain (pad=<optimized out>, parent=0x7f91e83d1d10, buffer=0x7f91e8051af0) at gstaudiodecoder.c:1912"
1724061,2017-10-19 21:48:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724061,2019-03-26 19:08:50 UTC,Same in 19.04.
1724068,2018-01-12 02:38:19 UTC,Me too Hp Pavilion x360:  Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298] do not have a drive to install!
1724068,2018-01-12 02:38:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724069,2018-01-23 07:34:04 UTC,"Change abandoned by Qi Peng (<email address hidden>) on branch: master
Review: https://review.openstack.org/531077"
1724069,2019-05-28 04:17:27 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1724075,2017-10-16 20:54:55 UTC,"StacktraceTop:
 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:93
 ptp_unpack_PTPTIME (str=0x59dc5469 <error: Cannot access memory at address 0x59dc5469>) at ptp-pack.c:646
 ptp_object_want (params=params@entry=0x7ff98c01c930, handle=1, want=want@entry=5, retob=retob@entry=0x7ff99f7fdc70) at ptp.c:6772
 LIBMTP_Get_Filemetadata (device=device@entry=0x7ff98c0216d0, fileid=<optimized out>) at libmtp.c:4351
 LIBMTP_Get_Files_And_Folders (device=device@entry=0x7ff98c0216d0, storage=<optimized out>, parent=<optimized out>) at libmtp.c:4532"
1724075,2018-04-06 06:10:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724078,2017-11-03 18:47:32 UTC,"For Xerox Workcentre 3225 the solution is:
1. Link the files in /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane,
2. Add the user that needs to use the scanner to the ""lp"" group.
Otherwise the ""Not a JPEG file: starts with 0x00 0x00"" issue persists."
1724078,2017-10-27 20:02:07 UTC,"xsane on Xerox WorkCentre 3225 does crash with similar message:
Not a JPEG file: starts with 0x00 0x00"
1724078,2017-10-18 23:55:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724078,2017-10-20 09:19:03 UTC,I have the trouble with a samsung scannner
1724078,2017-10-19 00:02:10 UTC,Sorry pushed enter too soon.  I can make the problem go away by changing the line in mate-panel.rc from
1724078,2017-10-20 09:52:20 UTC,Possible dupe of lp:1723422
1724078,2017-10-18 23:55:47 UTC,"I get this same message when I start the Groovy Shell, also under 17.10"
1724087,2017-10-17 15:56:07 UTC,Thanks for reporting.
1724087,2017-10-17 17:46:58 UTC,But when I try to run iexplorer.exe:
1724087,2017-10-17 18:36:12 UTC,Unfortunately we don't provide wine-gecko or -mono packages currently.  Just needs someone to do them.
1724088,2017-10-17 03:48:52 UTC,Seems to be an already open issue here: https://forum.snapcraft.io/t/weird-udev-enumerate-error/2360/20
1724088,2017-10-17 10:25:31 UTC,to try out the fix:
1724088,2017-10-17 22:36:38 UTC,I can confirm the beta update to snap core fixes the issue for me.
1724088,2017-10-18 08:00:16 UTC,switch to --beta core fix it for me too.
1724088,2017-10-25 12:28:53 UTC,switch core back to the stable and all seams ok.
1724089,2018-11-12 11:43:43 UTC,"Unfortunately, things are not that easy in practice as they might be in theory. The patch just aimlessly connects to things in a loop which can easily break."
1724089,2018-11-12 11:47:59 UTC,"Which means that currently with the patch you can be stuck indefinitely on a host, or if your lucky, your system has some global timeouts. If you do have timeouts, you need to wait N*T seconds for a timeout of T seconds and N IPv6 addresses before it falls back to IPv4."
1724092,2018-03-05 15:35:16 UTC,"I have hit this problem in the past. Personal anecdotal note: I feel like aa-logprof ""works better"" with rsyslogd vs auditd. Especially when I set /proc/sys/kerne/printk_ratelimit and /proc/sys/kerne/printk_ratelimit_burst to 0 during the duration of my profiling."
1724092,2017-10-17 00:08:10 UTC,"Hi, Seth, these entries was from dmesg. I am attaching my syslog.1 (Because I've just remove inetutils-syslogd and install rsyslog instead and that lines in dmesg (with /dev/log) are gone.)"
1724092,2017-11-11 13:17:13 UTC,I have similar issue on Kubuntu 17.10. Consider this denied message in audit log:
1724092,2017-10-16 23:13:38 UTC,"Hi Dima, are these entries in /var/log/syslog ? What do those lines look like?"
1724095,2017-10-17 08:27:49 UTC,"nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1724095,2017-11-15 21:36:04 UTC,reported upstream https://bugzilla.gnome.org/show_bug.cgi?id=790414
1724096,2019-09-04 13:46:41 UTC,The issue is that debug: true is enabling django admin which it should not do.
1724096,2019-09-03 22:42:46 UTC,"Moved to ""New"" because of comment #9"
1724096,2019-09-03 21:24:27 UTC,"Also found in v2.4.2. Adding a ""debug: true"" or ""debug:false"" entry in /etc/maas/regiond.conf triggers it. Removing it prevents it."
1724096,2019-02-12 09:58:56 UTC,"Hi Vladimir, do you have DEBUG enabled in maas? The error seems related to the django admin module, which is only enabled when debug is enabled."
1724096,2017-10-23 19:22:09 UTC,"@Dimitrii,"
1724096,2018-05-10 07:57:57 UTC,Hi!
1724096,2018-01-31 16:00:36 UTC,"Alberto,"
1724096,2017-10-28 21:51:25 UTC,I will try to reproduce it although the original environment is gone now.
1724096,2017-10-25 15:28:47 UTC,@dimitriis could you please provide the exact steps you took prior to running the user remove API call?
1724096,2017-10-23 20:46:41 UTC,It was a fresh user and fresh env - the first login screen was not passed yet at that point.
1724096,2018-10-19 04:29:39 UTC,"Hi all,"
1724098,2018-07-07 03:53:43 UTC,"Created attachment 372970
demonstration in Gnome 3.28.2"
1724098,2018-07-07 03:56:46 UTC,"Created attachment 372971
demonstration in Gnome 3.28.2"
1724098,2019-04-05 12:33:23 UTC,This bug persists on Arch Linux running Gnome 3.32.
1724098,2019-10-11 01:14:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724098,2019-10-29 08:00:24 UTC,The bug also persists in Gnome 3.34 (release) and 3.35 (master branch).
1724098,2020-02-13 03:32:59 UTC,"Maybe not. Today I did see the bug, or something like it, occur in Gnome Shell 3.35."
1724098,2020-02-12 02:05:53 UTC,Bug fixed by the new menu design in 3.35/3.36.
1724098,2020-03-10 21:41:56 UTC,"(In reply to Daniel van Vugt from comment #12)

> Bug fixed by the new menu design in 3.35/3.36.
"
1724098,2020-03-12 02:07:07 UTC,"Yes, the bug is still there :("
1724098,2021-02-23 12:30:00 UTC,This bug is fixed on my Arch Linux since Gnome Shell 3.38.1.
1724098,2017-10-20 08:42:01 UTC,I'm seeing this now myself. Maybe because I recently added a user picture to my account?
1724098,2020-02-12 02:02:57 UTC,I think this should be fixed in Gnome Shell 3.35 as the offending icons are no longer used.
1724098,2017-10-19 01:44:13 UTC,Here's a zoomed in screenshot of the issue from your video. It shows all the icons are briefly too big.
1724098,2017-10-17 22:04:13 UTC,apport information
1724098,2017-10-18 02:18:23 UTC,... or if the problem is brief then photo/video.
1724098,2014-05-16 18:43:58 UTC,"When opening the aggregate menu for the first time the speaker icon shows bigger than expected, then shortly shrinks to normal size. Unconfirmed wether it affects other icons."
1724098,2014-05-16 19:12:17 UTC,"I have recorded a video to show the problem.
https://dl.dropboxusercontent.com/u/56336/GNOME/aggregate-menu-bug.mov"
1724098,2015-02-28 01:53:09 UTC,*** Bug 740793 has been marked as a duplicate of this bug. ***
1724098,2017-10-18 10:34:02 UTC,Here is a gif of the problem. I should add that I'm using virtualbox if this is anyhow connected.
1724098,2017-08-30 13:41:40 UTC,"(In reply to Strangiato from comment #3)

> More than 3 years later and this bug is still not fixed...
"
1724098,2017-08-30 13:50:59 UTC,screencast does not capture this bug and I have no camera available to record a video.
1724098,2017-09-07 12:40:41 UTC,"Created attachment 359349
frame from the youtube video"
1724098,2017-08-30 12:50:22 UTC,"More than 3 years later and this bug is still not fixed...
It happens on 3.26 beta 2."
1724098,2017-10-17 02:33:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1724098,2017-10-17 22:04:10 UTC,apport information
1724098,2017-10-17 22:04:11 UTC,apport information
1724098,2017-10-17 22:04:12 UTC,apport information
1724098,2017-10-18 02:17:58 UTC,Thanks. Can you also provide a screenshot? I wonder if this is related to the giant icon rendering bug 1718238.
1724098,2017-09-07 12:41:43 UTC,"video in youtube
https://www.youtube.com/watch?v=1BUwDTL8GXI"
1724101,2017-10-17 08:23:53 UTC,That's reported upstream on https://bugzilla.gnome.org/show_bug.cgi?id=781910
1724104,2017-10-16 23:54:57 UTC,"StacktraceTop:
 g_settings_set_property (object=0x5612eea53c30, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at ../../../../gio/gsettings.c:590
 object_set_property (nqueue=0x5612eea48b30, value=<optimized out>, pspec=0x5612eea520f0, object=0x5612eea53c30) at ../../../../gobject/gobject.c:1439
 g_object_new_internal (class=class@entry=0x5612eea52860, params=params@entry=0x7ffc12058520, n_params=n_params@entry=2) at ../../../../gobject/gobject.c:1831
 g_object_new_valist (object_type=94639313181008, first_property_name=<optimized out>, var_args=var_args@entry=0x7ffc12058670) at ../../../../gobject/gobject.c:2120
 g_object_new (object_type=<optimized out>, first_property_name=<optimized out>) at ../../../../gobject/gobject.c:1640"
1724104,2017-10-17 09:36:37 UTC,"I don't know if this helps, but there is no search indexing at all. For example, I cannot find any of my documents directly from search. I must go to nautilus and search for it."
1724104,2018-01-21 00:09:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724128,2018-08-23 21:00:14 UTC,"There are two paths we could pursue for this:
a.) Utilize reporting mechanism (reporting.handlers.ReportHandler), which already does this in many senses.  MAAS uses this mechanism to accomplish both ""status"" events and ""pass/fail"".   This general mechanism is already in place.  To use it for vmware we would have to add some Reporter that worked for vmware."
1724137,2017-10-17 08:10:47 UTC,that looks similar to bug #1723619
1724137,2017-10-31 20:36:13 UTC,Can I do something to help solving this issue?
1724151,2019-12-18 18:45:05 UTC,The patch in #6 applied cleanly for me on ElementaryOS 5.1 Hera (Ubuntu 18.04 variant) and I can confirm that my HP Color LaserJet MFP M281fdw works great with this configuration.
1724151,2019-12-18 00:35:10 UTC,Thank you everyone for this thread. Gave me hope. Looking forward to having this committed.
1724151,2019-12-06 09:54:51 UTC,"> So I suggest you ask him.
"
1724151,2019-12-03 14:52:23 UTC,Romain Rivière (net+launchpad) wrote 49 minutes ago: 	#25
1724151,2019-12-03 13:53:22 UTC,"> The reported commits are for ArchLinux and Fedora packages. No commit has
> ever been reported here at upstream.
"
1724151,2019-12-03 10:48:43 UTC,"> Romain Rivière (net+launchpad) wrote on 2019-11-30: 	#23
>
> I don't know what happened to the fix that was committed a year ago ...
"
1724151,2019-11-30 19:31:52 UTC,"I don't know what happened to the fix that was committed a year ago, but the initial bug is still present in hplip 3.19.11 as downloaded and installed today. I found the following entry in models.dat:"
1724151,2018-09-02 10:54:22 UTC,"@karl I added a comment https://bugs.launchpad.net/hplip/+bug/1745835
It fixes the scan issue"
1724151,2018-11-12 18:24:49 UTC,@fredbcode.
1724151,2018-09-02 21:20:42 UTC,"Apparently, launchpad is unable to fetch the bug status from RedHats bugzilla. That bug is fixed for some time now"
1724151,2018-08-21 05:30:36 UTC,"The workaround, copying and renaming the section in models.dat, worked for printing but not scannin
Ubuntu 18.01"
1724151,2017-11-03 08:18:00 UTC,"Hi Dror,"
1724151,2018-03-01 07:56:47 UTC,"Since launchpad doesn't support flyspray:
Reported the bug to arch:
https://bugs.archlinux.org/task/57683"
1724151,2018-06-28 18:35:48 UTC,"Patch applied.
Still not commit to upstream."
1724151,2017-11-02 20:03:02 UTC,of course you are absolutely right that renaming *after duplication* is the correct solution.
1724151,2017-11-02 21:24:43 UTC,"thanks for the pointers. Will try at home and report. One small question. What is the difference between the different sections (ending in n,dw and c6):"
1724151,2017-11-02 23:33:23 UTC,"Hi Dror,"
1724151,2017-11-03 00:57:12 UTC,"Like Hans-Georg said, d stands for duplexer, n stands for networked, w stands for wireless and f stands for fax."
1724151,2017-11-02 19:40:56 UTC,"Actually, renaming an existing section is a bad idea because support for the existing model is lost.
Better duplicate the section and *then* rename the duplicate. I will attach a patch for that..."
1724151,2017-11-03 01:23:48 UTC,Addendum:
1724151,2017-11-04 21:08:17 UTC,"Thanks for sharing the knowledge,"
1724151,2017-11-04 20:55:29 UTC,"Dror,"
1724151,2017-11-03 01:15:11 UTC,"Meanwhile, I tested a little further with my patch and experienced two unrelated bugs in hplip which prevent proper setup after enabling some security related features using the printer's embedded web-config. (I will file separate bugs and probably fixes for those) so watch out for the following caveats (for now):"
1724151,2017-11-03 04:16:03 UTC,I tried the suggested method but no lock for me since I'm suffering from the following https://bugs.launchpad.net/hplip/+bug/1697958 as well...
1724151,2017-11-04 19:18:42 UTC,"My printer is defined on the system page (web UI) as ""HP Color LaserJet MFP M281cdw"". I used the method described by Fritz to duplicate the 277 model into my 281 model. The problem remained the same until I defined the new model as non duplex (dropped the dw from the end of the line). Attaching my working file diff to the original one to the bug. Thank you Fritz for all the off line help and the very helpful hp-setup -g (for debug) command."
1724156,2017-10-17 08:09:11 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1724156,2018-04-26 06:47:12 UTC,The bug existed in bionic 20180426 amd64.
1724156,2018-04-26 09:20:27 UTC,The bug existed in bionic 20180425.1 i686.
1724166,2017-10-17 18:37:52 UTC,"I find if I add this local mirror to the additional repositories rather than the official repositories, Update Manager does not complain. The issue for me is how to get Mint to use the additional repositories in preference to the official."
1724172,2019-10-10 14:32:00 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/687912"
1724172,2020-03-14 18:35:26 UTC,"Reviewed:  https://review.opendev.org/713033
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=53a893f7c97e35de3e9ac26101827cdb43ed35cc
Submitter: Zuul
Branch:    stable/rocky"
1724172,2020-03-13 17:18:51 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/713033"
1724172,2020-02-25 12:13:36 UTC,This issue was fixed in the openstack/nova 18.3.0 release.
1724172,2020-02-21 17:53:25 UTC,"Reviewed:  https://review.opendev.org/703103
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b874c409c11b5d83508d2f0276a9a648f72192a4
Submitter: Zuul
Branch:    stable/stein"
1724172,2020-01-17 15:25:14 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/703103"
1724172,2020-01-15 02:25:22 UTC,"Reviewed:  https://review.opendev.org/687912
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=07a938d388b03a641c677a937599cfea4e36a13a
Submitter: Zuul
Branch:    stable/pike"
1724172,2019-11-05 13:50:24 UTC,"Reviewed:  https://review.opendev.org/687873
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=52e68f121eda49dbb817404d3ab1468c2059e1a3
Submitter: Zuul
Branch:    stable/queens"
1724172,2019-10-25 23:37:46 UTC,"Reviewed:  https://review.opendev.org/687550
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=09de94e39bbcfc7f8130638e73a8248e49cb6ab7
Submitter: Zuul
Branch:    stable/rocky"
1724172,2019-10-10 12:33:21 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/687873"
1724172,2019-10-09 13:15:48 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/687550"
1724172,2019-09-27 09:03:27 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1724172,2019-08-05 22:12:18 UTC,"Reviewed:  https://review.opendev.org/512553
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4deab182ba59ee4112c28213f922c051179ba948
Submitter: Zuul
Branch:    master"
1724172,2019-06-27 17:50:28 UTC,"Reviewed:  https://review.opendev.org/512552
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2794748d9c58623045023f34c7793c58ce41447c
Submitter: Zuul
Branch:    master"
1724172,2019-06-06 06:23:46 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1724172,2019-05-31 19:26:49 UTC,"Reviewed:  https://review.opendev.org/662189
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b8f2cd689f0a747778080ba4b6e148e71eb53085
Submitter: Zuul
Branch:    stable/stein"
1724172,2019-05-30 11:23:24 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/662189"
1724172,2019-05-29 22:42:05 UTC,"Reviewed:  https://review.opendev.org/512623
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9cacaad14e8c18e99e85d9dc04308fee91303f8f
Submitter: Zuul
Branch:    master"
1724172,2018-08-09 08:09:07 UTC,"Yeah, I always thought that if the host has the same hostname then it is considered the same compute host. From nova-compute perspective it is just a nova-compute service restart that happened due to a host redeploy. The nova-compute service does not know that it was re-deployed. It sees the same nova.conf and hostname and therefore it will use the same compute node object."
1724172,2018-08-08 17:49:44 UTC,"But, will the source provider get the same uuid? Or will re-deploying the compute generate a new compute node uuid and thus a new provider in placement? I guess the compute node looking up the RT is based on hostname so as long as the service/compute wasn't deleted before the re-deploy it should still exist and use the same uuid."
1724172,2017-10-17 13:46:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/512623"
1724172,2017-10-17 09:10:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/512552"
1724172,2017-10-17 09:10:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/512553"
1724173,2018-07-02 07:26:19 UTC,@xavpaice Is anyone else with the problem also using isdct (Intel® SSD Data Center Tool for NVMe)? I have not had the problem since disabling it from running regularly. I was using it to check the wear level on regular intervals before.
1724173,2018-02-15 02:44:52 UTC,"We're also seeing this with 4.4.0-111-generic (on Trusty), and a very similar hardware profile.  The boxes in question are running Swift with a large (millions) number of objects all approx 32k in size."
1724173,2017-11-13 09:50:42 UTC,"Problem still exists on 4.4.0-97-generic. And in my attempt to reproduce it on a VM, I got a corrupt kernel instead, which sounds worse (could create some persistent damage, not just a hang)."
1724173,2017-11-28 10:45:59 UTC,"This one sets up a slower device which might be important according to IRC discussions
http://paste.ubuntu.com/26063765/"
1724173,2017-11-28 10:35:48 UTC,"Hi there was a slight issue in the repro relying on sda5, I changed that to be on shm as well.
2x800M are easy to spare. Hope it triggers with that as well."
1724173,2017-11-13 10:49:22 UTC,"tested again with a better serial console setup, and here's the text version like that screenshot:"
1724173,2018-02-15 02:42:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724174,2021-01-08 15:00:08 UTC,This has been overtaken by events.  The error is no longer taking place.
1724174,2021-01-08 14:58:55 UTC,So #5 issue is that placement isn't upgraded to train and nova-cc at ussuri tries to talk to it; hence the problem.  This was solved by: https://github.com/openstack-charmers/zaza-openstack-tests/pull/455
1724174,2021-01-19 13:41:32 UTC,"FWIW it's still happening on OSCI:
http://osci:8080/job/mojo_runner/24882/console"
1724174,2020-06-16 14:51:36 UTC,"To clarify, #3 is an OpenStack upgrade of Train to Ussuri."
1724174,2020-06-16 12:28:41 UTC,"Seems to now be always (3 times in a row) happening on bionic-train to next. Last occurrence:
http://osci:8080/view/MojoMatrix/job/mojo_runner/22848/console"
1724174,2020-06-17 16:48:55 UTC,So this is the issue:  not all of the apps are being upgraded to ussuri:
1724174,2020-05-28 13:59:25 UTC,"Happened twice recently:
http://osci:8080/view/MojoMatrix/job/mojo_runner/22587
http://osci:8080/view/MojoMatrix/job/mojo_runner/22605"
1724188,2017-10-17 10:13:46 UTC,"StacktraceTop:
 gtk_stack_set_visible_child_name (stack=0x0, name=name@entry=0x55964791052b ""installed-updates-list"") at ././gtk/gtkstack.c:1839
 get_installed_updates_cb (plugin_loader=<optimized out>, res=<optimized out>, dialog=0x55964b152330) at ../src/gs-update-dialog.c:262
 g_task_return_now (task=0x55964b158600) at ../../../../gio/gtask.c:1145
 complete_in_idle_cb (task=0x55964b158600) at ../../../../gio/gtask.c:1159
 g_main_dispatch (context=0x5596480a85d0) at ../../../../glib/gmain.c:3148"
1724188,2017-10-19 14:43:37 UTC,The stacktrace is similar to https://bugzilla.gnome.org/show_bug.cgi?id=782740
1724188,2018-04-22 16:51:50 UTC,<email address hidden>
1724188,2018-07-31 13:50:34 UTC,Upstream bug migrated to https://gitlab.gnome.org/GNOME/gnome-software/issues/177
1724188,2018-09-20 12:55:23 UTC,The particular code path only occurs when gnome-software is run with --mode=updated.
1724188,2018-09-20 12:56:29 UTC,This mode is triggered when following an update notification.
1724188,2018-09-20 13:07:26 UTC,"The crash occurs when getting historical updates and suggests the dialog was closed before this happened. The only plugin that provides these in Ubuntu is the fwupd one, so I suspect that's either not correctly handling a cancel request when the dialog is closed or GNOME Software is not generating the correct canceled error."
1724188,2018-09-20 13:30:39 UTC,errors.ubuntu.com shows this as the current #10 crash in gnome-software.
1724188,2019-06-05 13:55:45 UTC,"There has been no report since 3.30, assuming it has been resolved"
1724188,2018-09-20 12:15:38 UTC,"errors.ubuntu.com entry:
https://errors.ubuntu.com/problem/a7429d1aa03ffd472182b658004361c9985a4aca"
1724196,2019-04-24 23:07:35 UTC,"Merged it in, let's test this properly."
1724196,2019-04-22 10:13:00 UTC,Fix also needed in xfce4-power-manager:
1724196,2019-04-18 22:47:45 UTC,"Created attachment 8421
Use logind Can* methods (V3)"
1724196,2019-04-17 18:35:57 UTC,*** Bug 13699 has been marked as a duplicate of this bug. ***
1724196,2019-04-17 15:38:02 UTC,"Created attachment 8417
Use logind Can* methods (V2)"
1724196,2019-04-24 22:51:34 UTC,Simon Steinbeiss referenced this bugreport in commit e10ac91be3301c92900168855b265101ba9884e2
1724196,2019-04-17 15:19:05 UTC,"Created attachment 8416
Use logind Can* methods"
1724196,2019-04-17 15:21:56 UTC,Tested it on Arch Linux with xfce4-session-4.13.1git-5a42eda8 and can confirm it fixes bug 13699 too.
1724196,2017-10-17 12:22:57 UTC,"The attachment ""Patch to xfsm-systemd.c"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1724196,2018-08-16 09:55:03 UTC,Please forward this patch to the Xfce bug tracker. Thanks.
1724196,2018-11-03 10:40:18 UTC,Your patch will probably fix bug #13699 too.
1724196,2019-03-04 11:22:30 UTC,Can anyone take a look at this patch? Let's put it in xfce4-session 4.13.x for better testing!
1724196,2018-09-19 09:55:02 UTC,"Created attachment 7984
Patch to xfsm-systemd.c"
1724203,2017-10-17 21:19:18 UTC,I have filed an issue on github as GUI project tracks issues there - https://github.com/juju/juju-gui/issues/3284.
1724203,2017-10-18 07:53:02 UTC,"Thanks, I'll follow it there."
1724215,2017-10-25 12:51:35 UTC,Hardware Certification have begun testing this -proposed kernel.
1724215,2017-11-03 15:44:15 UTC,lp:1729362 can be fixed by enabling xenial-updates.
1724215,2017-11-03 15:47:42 UTC,"Certification-testing for Euclid kernel 4.4.0-9019 has been passed, here's the detailed test result:
https://certification.canonical.com/hardware/201702-25390/submission/124197/"
1724215,2017-11-03 16:03:29 UTC,The reason `apt dist-upgrade` doesn't install the new kernel is that the meta packages don't get updated and still point to 9018.
1724215,2017-11-28 09:17:43 UTC,"First time build, should not go to security."
1724215,2017-11-28 09:18:59 UTC,The package has been published and the bug is being set to Fix Released
1724215,2017-11-01 14:51:16 UTC,"Unable to upgrade kernel because of bug lp:1729362
So certification-testing of this kernel is currently blocked."
1724225,2017-10-17 11:50:16 UTC,"$ zim -D
INFO: This is zim 0.67
DEBUG: Python version is sys.version_info(major=2, minor=7, micro=14, releaselevel='final', serial=0)
DEBUG: Platform is posix
DEBUG: No bzr version-info found
DEBUG: Not running from a source dir
DEBUG: Set XDG_DATA_HOME to /home/trougnouf/.local/share
DEBUG: Set XDG_DATA_DIRS to [<Dir: /home/trougnouf/.local/share/flatpak/exports/share>, <Dir: /var/lib/flatpak/exports/share>, <Dir: /usr/local/share>, <Dir: /usr/share>]
DEBUG: Set XDG_CONFIG_HOME to /home/trougnouf/.config
DEBUG: Set XDG_CONFIG_DIRS to [<Dir: /etc/xdg>]
DEBUG: Set XDG_CACHE_HOME to /home/trougnouf/.cache
DEBUG: Connecting to /tmp/zim-trougnouf/primary-0.67-e63203e4
DEBUG: Dispatched command (u'-D',)"
1724228,2017-10-27 01:26:38 UTC,"Personally, I like the hint, but i wonder if we could just do:"
1724228,2017-10-18 15:17:06 UTC,Go for it.
1724232,2017-10-17 12:58:36 UTC,Using kernel 4.14.0-041400rc5-generic the problem is still present.
1724232,2017-10-17 13:00:07 UTC,This change was made by a bot.
1724232,2017-10-17 15:59:34 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1724232,2017-10-17 16:00:25 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1724232,2017-12-08 01:20:54 UTC,Hitting this with 4.13.0-17-generic
1724239,2017-10-18 04:12:48 UTC,"Yeah, HTTP 400 response is not correct in both the below cases
1. When trusts are disabled in keystone
2. trustee user does not exist."
1724239,2017-10-18 21:00:56 UTC,"If trusts_delegated_roles is set to something other than [], shouldn't heat attempt to create a trust with roles = the intersection of a) the roles on the token and b) the roles in trusts_delegated_roles? So that it would never ask for roles the user doesn't have, or roles that trusts_delegated_roles does not specify if that's being used as a filter."
1724239,2017-10-20 06:43:16 UTC,"> If trusts_delegated_roles is set to something other than [],
"
1724253,2017-10-18 14:56:02 UTC,"It seems that the issue would be due to the fact that in this CI setup, rootwrap is not configured as it should be, in particular the privsep filter."
1724253,2017-10-20 17:06:14 UTC,"Based on [1] this started cropping up on the 16th.
Either something landed, or it's related to the zuul v3 change perhaps."
1724253,2017-10-21 06:49:33 UTC,"Boden, as suggested in the description, the cause is https://review.openstack.org/#/c/505701 which landed that day."
1724253,2017-10-27 19:48:02 UTC,"I don't even think there is a bug in any meaningful sense in neutron here. The fact that bgpvpn wants to reuse the internal neutron script doesn't mean there is something wrong about neutron itself here. We can accommodate I guess, but that shouldn't be a reason to have a bug, especially 'Critical'."
1724253,2017-10-30 09:01:17 UTC,@Ihar: agreed.
1724253,2017-11-30 14:11:13 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.openstack.org/513719
Reason: done testing"
1724255,2017-10-17 14:11:04 UTC,"StacktraceTop:
 _cogl_buffer_initialize (buffer=buffer@entry=0x557cef3d1d40, ctx=ctx@entry=0x0, size=size@entry=92416, default_target=default_target@entry=COGL_BUFFER_BIND_TARGET_PIXEL_UNPACK, usage_hint=usage_hint@entry=COGL_BUFFER_USAGE_HINT_TEXTURE, update_hint=update_hint@entry=COGL_BUFFER_UPDATE_HINT_STATIC) at cogl-buffer.c:139
 _cogl_pixel_buffer_new (error=0x7fff4d813a70, data=0x0, size=92416, context=0x0) at cogl-pixel-buffer.c:88
 cogl_pixel_buffer_new (context=context@entry=0x0, size=size@entry=92416, data=data@entry=0x0) at cogl-pixel-buffer.c:119
 cogl_bitmap_new_with_size (context=0x0, width=width@entry=152, height=height@entry=152, format=format@entry=COGL_PIXEL_FORMAT_BGRA_8888_PRE) at cogl-bitmap.c:317
 clutter_canvas_emit_draw (self=0x557cef3dc5c0) at clutter-canvas.c:428"
1724255,2017-10-20 11:24:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724255,2017-10-23 21:09:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1724255,2017-11-06 02:42:42 UTC,"Tracking here also:
https://errors.ubuntu.com/problem/a0a2f89e4e2b7f369a7e64e26d496ce56625415d"
1724256,2017-10-17 15:57:52 UTC,Is the sensible-utils package installed on the system? If it is not can you install and try recreating the bug report again?
1724256,2017-10-19 15:26:03 UTC,"It is installed.  And it is probably not a surprise, but if I run with Russian locale the bug does not occur, just with LC_ALL=C."
1724256,2019-03-15 07:14:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724263,2017-10-17 14:31:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/512646"
1724263,2017-10-18 11:59:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/513007"
1724263,2017-10-24 13:50:03 UTC,"Change abandoned by Dan Prince (<email address hidden>) on branch: master
Review: https://review.openstack.org/512646"
1724263,2017-11-01 14:36:54 UTC,"Reviewed:  https://review.openstack.org/513007
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=800e0f3830837c0dc1f883b3a802a1ac7744e88e
Submitter: Zuul
Branch:    master"
1724263,2017-11-29 22:59:57 UTC,"Is this fixed by Thomas's patch, or is there still more to do?"
1724265,2018-08-03 22:24:07 UTC,I am experiencing what I think is the same problem with kernel 4.17.0-996-generic.
1724265,2017-10-18 03:52:03 UTC,"Per above comment, attached inteldrm crash log."
1724265,2017-10-18 03:19:35 UTC,"Testing with 4.14-rc5 I can enter hybrid-sleep with low memory usage but the system hangs after blanking the screen and displaying ""Snapshotting system"". In this case there are no log entries for the failure, ie the journal is truncated after initiating hybrid-sleep and then disconnecting the wifi (on NetworkManager receiving a suspend signal)."
1724265,2017-10-17 22:43:42 UTC,... except it's not a real PPA - wouldn't that have been a more natural approach? However I'll try nonetheless.
1724265,2017-10-17 22:32:24 UTC,">Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
"
1724265,2017-10-17 15:57:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1724265,2017-10-17 15:01:09 UTC,This change was made by a bot.
1724272,2017-10-18 17:04:59 UTC,"Hi,"
1724272,2017-10-19 12:54:16 UTC,"Well, the errors were these timeouts."
1724272,2018-02-05 11:53:02 UTC,"Hi ,"
1724272,2018-02-05 11:59:28 UTC,"In the log , its showing"
1724272,2018-07-16 13:09:56 UTC,I had a same issue and the problem has not resolved.
1724272,2018-07-16 14:33:20 UTC,I successfully installed openstack.
1724272,2020-11-16 03:00:02 UTC,"Have same issue on Centos7, HP DL580 gen7, packstack train."
1724273,2020-01-06 10:55:01 UTC,"Hello,
4.8.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1724278,2017-10-17 15:35:41 UTC,This may require upgrading fluentd to v0.14: https://github.com/fluent/fluentd/issues/461
1724301,2017-10-17 17:47:16 UTC,"kernel is 4.9.0-4-rpi
clamsmtp is 1.10-13+b2"
1724304,2017-10-17 21:59:43 UTC,"I'd prefer to hold off on this a while longer.  Ubuntu 12.04 is still under extended support, and it doesn't have apt(8) at all."
1724306,2019-03-26 05:45:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647657"
1724306,2019-03-26 04:53:45 UTC,"We use private registry on deployment server in production. And it is very common behavior that need to fix. Because when we want clean images on openstack node(control,compute,network,storage) , it also delete images from deployment node/private registry. This is due to using ""hosts: all"" in destroy.yaml"
1724306,2017-11-16 20:27:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520761"
1724306,2017-11-16 16:07:35 UTC,How about adding another variable like 'destroy_include_deployment_host' and adding a check for that in destroy playbook?
1724306,2017-10-27 07:08:50 UTC,"Here are two cases, in my case I like destroy images clean up all my ``kolla`` images in deployer node as I use it for building and then push to registry. But I see also a problem of removing images when operator dont want."
1724307,2018-11-20 11:12:07 UTC,"I can confirm this issue existing on 18.04, too, and it probably doesn't have anything to do with DisplayLink as I'm using a direct HDMI connection via the built-in HDMI port on a Dell XPS 15 9570. The external screen is not hDPI, sporting mere 1920x1080, so to keep the proper scaling on both I utilize xrandr to double the frame buffer and then rescale it back for the external screen, i.e.:"
1724307,2018-11-22 19:35:03 UTC,"I have the same issue on Ubuntu 18.04.1 LTS (kernel 4.15.0-38-generic) connected with DisplayLink (driver 4.4.24).  I'm connecting through Display port on a Dell Inspiron 15, and a docker D6000."
1724307,2019-07-03 11:21:55 UTC,"Same issue here. I have a brand new Dell 7300 using Ubuntu 18.04, and when I use my Asus MB16AC monitor using the USB connection with the displaylink driver, the mice pointer starts to flicker and move around. It can be used but it is very annoying. Can't find the cause. On my old computer, a Toshiba Satellite with Ubuntu 18.04 it worked just fine....:("
1724307,2019-07-24 00:41:33 UTC,"I experienced the same issue on my Dell XPS 13 (9350) running Kubuntu 18.10 (4.18.0-25-generic), KDE Plasma 5.13.5. My laptop was connected to the 2nd monitor using the VGA port on the Dell 4-in-1 adapter with the DisplayLink driver 5.2.14"
1724307,2019-07-24 01:18:14 UTC,"Stephan Fabel, could you please advise to all of the following:"
1724307,2019-07-24 01:19:16 UTC,"Quoc Khanh Le (qkle), it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux"
1724307,2019-07-24 02:04:39 UTC,"Christopher M.Penalver (penalvch), just filed a new report and subscribed you to it."
1724307,2019-07-24 06:06:23 UTC,"I have since moved on from the DELL XPS 13 and am unable to provide you
with the answers to your questions."
1724307,2019-07-26 07:17:47 UTC,[Problem fixed]
1724307,2019-07-27 17:25:34 UTC,"Stephan Fabel, this report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724307/comments/28 regarding you no longer use the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find."
1724307,2020-08-11 10:59:32 UTC,Note that I got this to stop happening by switching to the Wayland compositor.
1724307,2020-08-11 11:00:11 UTC,(The default configuration is Ubuntu vs. Ubuntu + Wayland.)
1724307,2020-08-11 11:05:02 UTC,(I might also add that the computer feels *way* more responsive and snappy with this change.)
1724307,2017-11-22 01:51:20 UTC,"Stephan Fabel, while I wouldn't say this is fully root caused, due to how debugging GUI stuff is not my focus, I'll mark this Triaged for now. However, given Ubuntu is moving away from Unity going forward as per https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/ you may want to use a GNOME based session going forward to avoid this problem."
1724307,2017-11-22 01:05:05 UTC,"I can confirm that the issue is gone completely using the ""GNOME Flashback (Metacity)"" session."
1724307,2017-11-21 00:43:30 UTC,"Here's the link to the DisplayLink Forum post:
https://displaylink.org/forum/showthread.php?p=84713#post84713"
1724307,2017-11-21 22:28:36 UTC,Original reporter's video of the issue.
1724307,2017-10-17 17:18:59 UTC,"Stephan Fabel, thank you for reporting this and helping make Ubuntu better."
1724307,2017-10-17 19:33:46 UTC,"Hi Christopher,"
1724307,2017-10-17 22:19:03 UTC,"Stephan Fabel, to follow up:
1) Are connecting the Wavlink device to the external monitor via DVI?
2) If you don't connect the Wavlink device to the laptop, do the mouse symptoms ever occur?
3) When you say it occurred with Ubuntu 17.04, 17.10, and 16.04 x64, this is you personally testing all of these on your Dell XPS 13 9360?
4) When you state Google Chrome aggrevates the issue, what do you mean precisely?
5) To confirm the symptoms, when everything is connected, the mouse flickers on both screens. However, it can disappear on both or only the laptop monitor for several minutes at a time?"
1724307,2017-10-17 22:54:39 UTC,1) The DVI connection doesn't work at all. This is through HDMI.
1724307,2017-10-21 01:11:46 UTC,"Hi all,"
1724307,2017-11-04 16:21:39 UTC,"Stephan Fabel:
1) Could you please attach a screenshot or screencast of the flickering via https://help.ubuntu.com/community/Screencast ?
2) Could you please cross post this issue upstream to DisplayLink Support following their guide at http://support.displaylink.com/knowledgebase/articles/757047-how-can-i-report-ubuntu-issues-to-displaylink ? While it may end up being root caused to a Ubuntu issue, more eyes on the problem wouldn't hurt here."
1724307,2017-11-04 15:44:31 UTC,"Wei Cai, to track your issue and hardware, it will help immensely if you use the computer the problem is reproducible with, file a new report with Ubuntu by first ensuring the package xdiagnose is installed, click the Yes button for attaching additional debugging information after running the following from a terminal:
ubuntu-bug xorg"
1724307,2017-11-05 15:21:32 UTC,"Travis Brace, it will help immensely if you use the computer the problem is reproducible with, file a new report with Ubuntu by first ensuring the package xdiagnose is installed, click the Yes button for attaching additional debugging information after running the following from a terminal:
ubuntu-bug xorg"
1724307,2017-11-21 23:01:28 UTC,"Stephan Fabel, to further root cause, could you login to a ""GNOME Flashback (Metacity)"" session (not a compiz-based or Unity session) via https://launchpad.net/ubuntu/+source/gnome-flashback and advise if the flickering persists?"
1724307,2017-11-21 00:58:40 UTC,"Stephan Fabel, to see if a WORKAROUND exists, could you please test the following and advise if the flickering still occurs:
In the GUI go to All Settings > Screen Display > for the primary monitor change Rotation from Normal to any of the following:
Clockwise
Anti-clockwise
180 degrees"
1724307,2017-11-21 02:13:54 UTC,"When I changed the rotation, the mouse cursor was visible throughout the 30 seconds it remained in that configuration. Before an after, the cursor was not visible at all on the primary screen."
1724307,2017-11-21 20:45:51 UTC,"Stephan Fabel, regarding the screencast not working, could you please provide a camera picture of the screen?"
1724307,2017-11-21 21:24:05 UTC,"Sure, here it is: https://photos.app.goo.gl/5J2X3gsqGnNi8qwv2"
1724307,2017-11-05 08:09:19 UTC,I'm having the same issue as well. With three screens the mouse has a glitch where it's like part of the screen makes a box around it. It almost seems to happen on interactions.. It's very noticable moving over tabs on a browser window.
1724316,2017-10-19 10:40:51 UTC,Yep.  There is code to prevent refreshing the macaroon if the user has changed their password since it was created:
1724316,2017-12-22 16:49:35 UTC,The snapd side change got merged.
1724316,2017-10-20 10:56:17 UTC,Snapd side changes:
1724316,2017-10-19 06:05:02 UTC,Discussion started here:
1724316,2017-10-19 03:13:53 UTC,"So further investigation, the ""cannot authenticate to snap store: "" part of the error is only added by snapd for an unexpected error:"
1724316,2017-10-18 12:11:24 UTC,"Robert, could you have a look?"
1724316,2017-10-18 09:50:30 UTC,"The ""Provided email/password is not correct."" part of the error message appears to be coming through straight from the store.  This most likely means you logged in to gnome-software using Ubuntu One credentials at some point in the past, and the credentials snapd has stored are no longer valid."
1724316,2017-10-18 08:42:25 UTC,Thank you for your bug report. I've the same issue on my artful and I'm unsure there is any graphical UI to re-enter credential at the moment?
1724317,2017-11-22 17:11:47 UTC,"Been lurking on this bug and hoped it would be fixed with the new 4.13.0-17 kernel update, which I just installed after wrestling with the unreliable apt-get mechanisms for over an hour by the way (but that's a topic for another bug) but no such luck.  This buggy beast is still hanging on shutdown with the 4.13.0-17 kernel."
1724317,2017-11-22 17:18:52 UTC,My hardware by the way is an Asus Zenbook pro laptop with the Intel dual band wireless-AC 7260  adapter and nvidia GTX 960M
1724317,2017-11-22 19:55:06 UTC,"For me everything's fine after yesterday's kernel update. Shutdown and suspend work as expected. So this bug seems to have been fixed indeed, for the Qualcomm Atheros QCA9377 chip at least."
1724317,2017-11-23 16:55:20 UTC,"hello
A saw a user with 4.13.0-17
""menuentry 'Ubuntu' --cls-uuid --set=root f0641efe-a392-4030-8271-de6b3db19912
 .........
 linux	/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=f0641efe-a392-4030-8271-de6b3db19912 ro  quiet splash pci=noaer $vt_handoff
 initrd	/boot/initrd.img-4.13.0-17-generic"
1724317,2017-11-24 11:33:35 UTC,Kernel update 4.13.0-17 fixed bug for me.
1724317,2017-11-25 15:38:57 UTC,After the kernel update I was able to shutdown succesfully two times. Without taking any further chances I'm now stuck at the poweroff again. I only see the blinking cursor on the top right corner that normally apears before the splash screen shows up. Seems to be another poweroff bug.
1724317,2021-01-09 20:45:40 UTC,I am having this same problem with Xubuntu 20.04 kernel 5.4.0-60-generic
1724317,2017-11-15 17:41:37 UTC,"@gernophil: If by a ""new kernel release"" you mean Linux 4.14, you won't see that in artful. That's not how kernel updates are done in Ubuntu. For more details see https://wiki.ubuntu.com/Kernel/FAQ."
1724317,2018-02-12 20:44:37 UTC,"SOLVED.
Starting from your suggestion, having I a rtl8723be based wifi card, I made a simple test:"
1724317,2019-11-28 14:35:36 UTC,Bug appears to have returned for Ubuntu 16.04 in kernel 4.4.0-169-generic. Also happens in 4.4.0-168.
1724317,2019-12-01 06:33:47 UTC,"Bug also possibly found on 18.04, kernel 5.0.0-36-generic; will need confirmation. (First occurrence)"
1724317,2019-12-01 06:56:24 UTC,"Power cycling does not appear to trigger the bug, as well as attempting to recreate the original circumstances (turning off wireless through system tray + shutdown)."
1724317,2020-02-12 13:36:04 UTC,I can confirm that the bug still exits in kernel: 5.3.0-28-generic (in my case with Linux Mint 19.3)
1724317,2017-11-25 15:55:34 UTC,"The new bug seems to be related to the proprietary nVidia Driver (384.90). I don't have anymore poweroff problems when I use prime-select intel. However, this is not related to this bug."
1724317,2017-11-13 16:30:10 UTC,"So, there has been a new kernel release today. Can we expect an update for this Ubuntu release or do we have to wait for the next Ubuntu version? Anything official about this bug?"
1724317,2017-10-23 14:54:47 UTC,Thank you for your swift response. That's good to hear it's not so far away.
1724317,2017-11-09 15:19:33 UTC,"I just updated to Lubuntu 17.10 and experienced this issue. I have a Qualcomm Atheros QCA9377 card, and kernel version 4.13.0-16-generic had this same issue. I reverted back to 4.10.0-38-generic and the problem went away."
1724317,2017-10-17 17:18:50 UTC,Possible affects linux-image-4.13.0-16-generic
1724317,2017-10-17 17:30:52 UTC,This change was made by a bot.
1724317,2017-10-19 05:38:02 UTC,It should be fixed with next Artful kernel release.
1724317,2017-10-23 14:02:09 UTC,This also affects me. I can't shutdown my laptop unless I hold down the power button. Happens every time.
1724317,2017-11-10 14:42:29 UTC,"> On 9 Nov 2017, at 11:19 PM, Menachem Shapiro <email address hidden> wrote:
>
> I just updated to Lubuntu 17.10 and experienced this issue. I have a
> Qualcomm Atheros QCA9377 card, and kernel version 4.13.0-16-generic had
> this same issue. I reverted back to 4.10.0-38-generic and the problem
> went away.
>
> I'm waiting for the next kernel release to see if that solves the
> problem.
"
1724317,2017-10-24 15:43:40 UTC,I just installed an newer ubuntu mainline kernel (4.13.9) and the issue is fixed as described by Kai-Heng Feng.
1724317,2017-10-23 14:43:21 UTC,Should be less than two weeks.
1724317,2017-10-29 10:16:22 UTC,Installing kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.10/ fixed the issue for me.
1724317,2017-11-02 16:48:00 UTC,Any news when the fixed kernel release will be released?
1724317,2017-11-04 20:27:23 UTC,"I have same issue,"
1724317,2017-11-06 18:12:42 UTC,The same problem on Lenovo ideapad 110.
1724317,2017-11-06 21:06:35 UTC,Its been more than two weeks now. Could you please confirm when the next kernel will be available?
1724317,2017-10-28 16:46:18 UTC,"I can confirm the bug on a Lenovo laptop. It may be the Qualcomm Atheros wireless card that is the culprit. I have a Qualcomm Atheros QCA9377 card.
I can also confirm that the newest kernel from the Ubuntu Mainline ppa (http://kernel.ubuntu.com/~kernel-ppa/mainline/), 4.13.10, seems to solve the issue. The computer shuts down as expected. I have no problem with suspend closing the lid."
1724325,2019-09-17 11:41:24 UTC,Migrated to https://github.com/widelands/widelands/issues/3497
1724331,2017-11-01 12:19:01 UTC,Should be fixed in 1.1.1 (latest upstream release)
1724331,2017-10-17 19:18:24 UTC,"Hi,"
1724334,2020-01-24 10:02:25 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1724334,2017-10-20 07:13:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724334,2017-10-17 18:27:47 UTC,"StacktraceTop:
 clutter_box_layout_allocate (layout=0x7f0fa809bb30, container=<optimized out>, box=<optimized out>, flags=CLUTTER_ABSOLUTE_ORIGIN_CHANGED) at clutter-box-layout.c:1010
 st_widget_allocate (actor=0x5634bf180650, box=<optimized out>, flags=CLUTTER_ABSOLUTE_ORIGIN_CHANGED) at ../src/st/st-widget.c:426
 st_box_layout_allocate (actor=0x5634bf180650, box=0x5634b12e3c60, flags=<optimized out>) at ../src/st/st-box-layout.c:288
 clutter_actor_allocate_internal (flags=CLUTTER_ABSOLUTE_ORIGIN_CHANGED, allocation=<optimized out>, self=0x5634bf180650) at clutter-actor.c:9973
 clutter_actor_set_animatable_property (actor=actor@entry=0x5634bf180650, prop_id=<optimized out>, value=value@entry=0x7ffc055ccfc0, pspec=pspec@entry=0x5634b0600d70) at clutter-actor.c:14988"
1724352,2017-10-18 14:55:15 UTC,From DpkgTerminalLog.txt:
1724352,2017-11-29 22:00:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724359,2017-10-27 17:14:54 UTC,"I think this is simply because in Openstack, cloud-init-generator (well, ds-identify from cloud-init) looks at dmi, doesn't find the make/model data there since there isn't (because no CONFIG_DMI), and gives up doing anything else."
1724359,2017-10-31 15:31:48 UTC,Mathieu has confirmed that a test kernel with CONFIG_DMI and CONFIG_DMIID enabled resolves the problem.
1724359,2017-11-08 13:45:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1724359,2017-11-08 19:17:45 UTC,"Verification-done-xenial, with 4.4.0-1010.15:"
1724359,2017-11-20 16:54:55 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1010.15
1724370,2019-10-06 04:17:25 UTC,[Expired for udisks2 (Ubuntu) because there has been no activity for 60 days.]
1724370,2019-10-06 04:17:23 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1724370,2019-10-06 04:17:22 UTC,[Expired for gnome-disk-utility (Ubuntu) because there has been no activity for 60 days.]
1724370,2017-10-17 21:29:28 UTC,"Finally, the kernel model from a SATA drive:"
1724370,2019-08-06 15:18:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER"
1724370,2017-10-17 21:09:25 UTC,Here is the information from an NVME drive. Note that ID_MODEL is missing:
1724370,2017-10-17 21:08:52 UTC,Here is the information from a SATA drive:
1724370,2017-10-17 21:07:56 UTC,"Attached is the current behavior, no Model is set"
1724370,2017-10-17 21:07:37 UTC,"Attached is a screenshot of the expected behavior, with a model set"
1724370,2017-10-17 21:12:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724408,2017-10-20 17:44:40 UTC,"Reviewed:  https://review.opencontrail.org/36617
Committed: http://github.com/Juniper/contrail-neutron-plugin/commit/0283a82fb7298b8cdfc3d851bec3356aeaa0b69a
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1724408,2017-10-19 17:55:15 UTC,"Reviewed:  https://review.opencontrail.org/36613
Committed: http://github.com/Juniper/contrail-controller/commit/2f793ceee3f3b86eb1cb9b08778eec86cc7e61a3
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1724408,2017-10-18 16:43:36 UTC,Notes for release notes:
1724408,2017-10-18 05:55:21 UTC,"Review in progress for https://review.opencontrail.org/36613
Submitter: Ignatious Johnson Christopher (<email address hidden>)"
1724408,2017-10-18 05:36:45 UTC,Work Around:
1724408,2017-10-18 06:03:14 UTC,"Review in progress for https://review.opencontrail.org/36617
Submitter: Ignatious Johnson Christopher (<email address hidden>)"
1724414,2017-10-18 13:13:25 UTC,"Just ensure that if you do select the unqualified hostname that the system will continue to use that hostname after a reboot.  The current situation is the result of fixing an issue in which cloud-init would select the unqualified hostname initially but the fqdn would be used after a reboot (or something like that), which was causing ugly issues with stuff that used the hostname as an identifier."
1724414,2017-10-18 13:32:05 UTC,"When we do set_hostname() and update_hostname(), we will serialize the hostname to system configuration files, which will be picked up upon next boot. I'm not aware any issues regarding reboot, unless we have bugs somewhere else or rhel distro has other unexpected behavior. Also I'm very new to cloud-init. I'm happy to test and verify any scenarios experiences developers can think out."
1724414,2019-03-06 18:26:18 UTC,"Hi, this bug is from 2017?"
1724414,2019-03-06 19:00:37 UTC,"Hi Adrian,"
1724417,2019-07-26 06:37:38 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1724417,2017-10-19 14:33:08 UTC,"Output from xenial
(hd0)   /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001
(hd1)   /dev/disk/by-id/lvm-pv-uuid-Z1IRUC-cEkY-8SOd-rIvV-4PUR-pSn4-04NHcf"
1724417,2017-10-19 14:21:50 UTC,"The order of the devices in the output of grub-mkdevicemap changed between xenial and artful
In Xenial hd0 was the first hard drive then the logical volumes
In Artful hd0 is the first logical volume the the hard drives"
1724417,2017-10-18 07:32:27 UTC,"jibel pointed me out to this bug from a few days ago that seems similar:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1722594"
1724417,2017-10-18 02:09:34 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1724420,2017-10-18 04:19:44 UTC,"The attachment ""The fix for the bug"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1724422,2017-10-18 01:52:43 UTC,Placing as High prio as this blocks backporting and releasing stable fixes.
1724422,2017-10-24 13:44:45 UTC,Its not promulgated as there is no specific HSM backend at the moment; I'd suggest we override the generated charm locations with sensible ones for the stable branch?
1724422,2017-10-24 13:45:12 UTC,Dropping priority of this bug as charms never officially got released per-say.
1724423,2019-08-27 08:55:23 UTC,This fix was verified on below version
1724423,2019-08-27 08:57:14 UTC,"===Test output===
------------[ Running job 106 / 292. Estimated time left: unknown ]-------------
--------------[ monitor/1_hdmi_PCI_ID_0x9b41 after suspend (S3) ]---------------
ID: com.canonical.certification::after-suspend-manual-monitor/1_hdmi_PCI_ID_0x9b41
Category: com.canonical.plainbox::monitor
Purpose:"
1724429,2020-06-30 04:58:14 UTC,"Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!"
1724437,2020-01-24 10:09:48 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1724440,2017-10-18 10:10:03 UTC,I have GTK 3.18.9
1724440,2017-10-18 09:51:53 UTC,Thinking about it a bit more... I've filed https://bugzilla.gnome.org/show_bug.cgi?id=789137.
1724440,2017-10-18 12:47:09 UTC,"I have no idea how it could be broken with panes, that should work even with older GTKs :)"
1724440,2017-10-18 08:13:47 UTC,I've just changed from block to I-Beam and back to block and indeed it is showing as the outline in unfocussed terminals.
1724440,2017-10-18 09:45:47 UTC,This mainly depends on VTE. It offers three modes:
1724441,2019-12-14 21:52:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724441,2018-04-23 06:56:12 UTC,"Hi Michael,
thank you for the discussion, no need to apologize - I can see your troubles and want to help.
But lets dissect the different aspects of it."
1724441,2018-04-23 04:24:36 UTC,"The attachment ""Changes needed to /etc/qemu.conf"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1724441,2018-04-23 01:31:04 UTC,"Apologies to re-open this for libvirt again, but I just had to go through the same song and dance again after upgrading to 18.04 and fixing the problem this required making some changes to the apparmour profile for libvirt. Will attach a diff of the changes in a moment."
1724441,2018-04-23 02:12:07 UTC,"The changes to the apparmour profile aren't minimal, they could probably be tightened up, but I'm not very familiar with it."
1724441,2018-02-12 03:04:46 UTC,"I managed to get this working in the end. Turns out that despite using the libvirt/qemu user session for the VMs, gnome-boxes actually uses the *system* libvirt network named ""default"" for networking so it works ""out of the box"". In reality, I had to delete that network and re-create it using virt-manager before it actually started bridging traffic to my physical connection."
1724441,2017-11-21 06:43:26 UTC,"Hey, thanks for the pointers, I've been looking into this a bit and performed the following:"
1724441,2017-10-24 08:54:57 UTC,"Hi,
thanks Michael for the report.
Looking into this from the libvirt POV."
1724441,2017-10-24 00:18:24 UTC,"Added libvirt since I can't add a NAT network to the qemu:///session using virt-manager, either."
1724441,2018-02-14 07:22:00 UTC,"Hi,
the dependency to libvirt atm is only
-> libvirt-daemon (Depend) -> libvirt-daemon-system (suggest)
And if that would be all that would be needed I'd expect that it could be changed in gnome-boxes."
1724444,2017-10-27 16:21:09 UTC,"No problem, so the error is local_endpoint cannot be NULL"
1724444,2017-11-20 16:27:18 UTC,"Sorry, no progress on my side. I suspect this is related to the containerized setup, but I'd need to setup a similar kolla setup to test."
1724444,2017-11-07 10:12:20 UTC,Any luck on this issue?
1724444,2017-10-31 10:42:01 UTC,"Yes, in my case that doesn't seem to be an issue."
1724444,2017-10-20 09:30:10 UTC,"I am not sure I will have time to test a kolla deployment soon, in the meantime can you paste the debug neutron-server.log?"
1724444,2017-10-27 10:21:41 UTC,"Sorry for late response, here is debug log :"
1724444,2017-10-18 15:39:02 UTC,Thanks for looking into the issue.
1724444,2017-10-18 15:59:31 UTC,"Thanks, reassigning to networking-sfc for further investigation, as both conf and database look good"
1724444,2017-10-18 15:14:36 UTC,"Thanks, the configuration looks OK (I was wondering if the ovs driver for SFC was correctly set).
In that case failure in port pair creation probably means some database problems, what is the result of:
neutron-db-manage --subproject networking-sfc current --verbose"
1724444,2017-10-18 14:25:10 UTC,Here is the configuration file from neutron-server container.
1724444,2017-10-18 14:00:21 UTC,"All of this happens on the server (creating port pairs does not involve the agent), so I'd guess a configuration problem?"
1724444,2017-10-18 04:18:57 UTC,From inside docker container.
1724451,2017-10-18 07:31:29 UTC,Here's the icon as it sometimes appears.
1724451,2018-07-11 17:19:02 UTC,Here is a video of the problem: https://app.box.com/s/2a6ujhu29euu11cceny2jrlrppln7hih
1724453,2020-11-20 04:17:17 UTC,[Expired for pluma (Ubuntu) because there has been no activity for 60 days.]
1724459,2018-01-25 08:34:51 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3750
1724459,2017-12-14 07:55:17 UTC,"After the test, open the tokudb_directio option. SSD can start normally, but PCIE can't start normally"
1724459,2017-10-19 03:33:31 UTC,谁来给看看
1724459,2017-12-11 12:36:22 UTC,Thank you for the report.
1724463,2017-10-19 14:29:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1724463,2017-10-19 14:30:17 UTC,Note that the issue is in the flatpak plugin which is not installed by default on Ubuntu
1724474,2017-12-15 05:49:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/528158"
1724474,2017-10-28 17:42:31 UTC,"Greetings, Looking at the specification for service management, and this proposal seems to focus around providing insight into what node maps to what conductor. The addition to it seems to be able to provide insight into the heartbeat table which is used for the hash ring. I don't necessarily see value in providing a declaration of if a conductor is absolutely up or down, however insight into if the node is considered to be part of the hash ring at that moment and then the resulting mapping information of conductor to nodes would provide a great deal of information to assist in troubleshooting."
1724474,2017-10-18 13:41:30 UTC,"Thanks for the RFE. This looks similar to ""[RFE] Add service management API"" [1], so I'm going to mark this as a duplicate. If it isn't similar, please unduplicate. If it is the same, please help by e.g. reviewing the proposed spec for that."
1724474,2017-10-19 04:16:58 UTC,"Hi Ruby, I took a peek to the spec you provided, it focused on the role of conductor service management, that is different with the proposal here.
I can help to review to see if we can get similar information in that spec, then this rfe can be covered."
1724482,2017-10-18 09:09:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1724482,2017-10-19 17:03:34 UTC,I tried a bit to look at this.
1724482,2017-11-15 06:58:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724489,2017-10-19 01:28:31 UTC,"Ah, seems to be a bug(?) in GNOME Software - it's only actually throwing away any search word less that 3 characters. So the search ""oh my"" is rejected because none of the words are long enough. ""oh my gir"" would just search with ""gir""."
1724489,2017-10-19 01:21:35 UTC,"The command line finds using these terms:
$ snap find 'oh my'
Name         Version  Developer  Notes  Summary
ohmygiraffe  1.1.0a   popey      -      oh my giraffe"
1724493,2017-10-18 09:24:59 UTC,"I did almost everything, but DIB_INIT_SYSTEM='Unknown init system', I am not able to understand the cause of error. would appriciate help:"
1724493,2017-10-18 09:33:27 UTC,I also not able to understand the following documentation:
1724493,2017-10-18 09:18:52 UTC,These are the last lines of log provided:
1724498,2017-10-23 14:10:01 UTC,"I have now raised a bug with Google / Android tools at https://issuetracker.google.com/issues/68131667
The Debian package maintainers suggested this was the bug tracker I should probably be using http://lists.alioth.debian.org/pipermail/android-tools-devel/2017q4/002864.html"
1724504,2017-10-22 20:00:58 UTC,Solution is found here:
1724513,2017-10-18 16:53:12 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1724513,2017-10-19 10:59:39 UTC,"Ah, sorry, I tested with the latest latest stable kernel: 4.13.7 (well, now the latest is .8, I'm already running that one, but haven't really tested it yet)."
1724513,2017-10-18 12:10:25 UTC,"Bear in mind I've used the mainline kernel while getting the files via apport, not the faulty one."
1724513,2017-10-18 12:08:11 UTC,apport information
1724513,2017-10-18 12:08:09 UTC,apport information
1724513,2017-10-18 12:08:08 UTC,apport information
1724513,2017-10-18 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1724523,2017-10-18 11:24:24 UTC,"Just for the record, while I do agree that this is a rare and unusual setup, it is nevertheless a perfectly valid one and there's no reason for it not to be supported."
1724523,2017-10-18 12:24:15 UTC,"The attachment ""Do not leak the parent interface's lock."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1724523,2017-10-18 16:21:28 UTC,"This setup is not that unusual, in a server/data-centre environment."
1724533,2017-10-30 19:58:29 UTC,"On mié, oct 18, 2017 at 7:35 AM, Stuart Bishop
<email address hidden> wrote:

> Public bug reported:
>
> I've built a part with the maven plugin, which 'just worked'.
>
> Looking at my stage area however, I only see paths to the java
> executable include my architecture:
>
> $ find stage -name java
> stage/usr/share/java
> stage/usr/lib/jvm/java-8-openjdk-amd64/bin/java
> stage/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
> stage/etc/ssl/certs/java
>
> Without /usr/bin/java or similar, I can't define my apps: section in
> an
> architecture independent way. Some update-java-alternatives magic or a
> symlink seems to be needed.
"
1724536,2017-10-18 11:05:56 UTC,This is the full error from the logs:
1724537,2019-09-26 11:07:03 UTC,"I don't understand: uname says you're running the 'stable' kernel, so all should be well?"
1724537,2017-10-23 05:56:14 UTC,"Hi John,"
1724537,2019-11-26 04:17:36 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1724537,2017-10-20 11:44:43 UTC,"Alfie,"
1724537,2017-10-19 16:28:18 UTC,"I did a (naive) test on my core VM. We need to add a proper spread test into our tree, I'm not sure we fully test this yet. However in my test things look ok:
""""""
root@localhost:~# snap list
Name              Version       Rev   Developer  Notes
core              16-2.28.1     3017  canonical  core
pc                16.04-0.9     20    canonical  gadget
pc-kernel         4.4.0.96.101  84    canonical  kernel
test-snapd-tools  1.0           6     canonical  -
root@localhost:~# uname -a
Linux localhost.localdomain 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
root@localhost:~# cat /proc/version_signature
Ubuntu 4.4.0-96.119-generic 4.4.83
root@localhost:~# snap revert pc-kernel"
1724537,2017-10-20 11:33:17 UTC,"Hi Michael,"
1724537,2017-10-19 15:49:29 UTC,Could you please pastebin the output of:
1724537,2017-10-19 06:48:46 UTC,"Hi Tony,"
1724537,2017-10-18 22:13:41 UTC,The description needs some more detail.
1724538,2017-10-26 11:28:39 UTC,The message means the numpy used during pandas compilation is different from the numpy at runtime. This fail is about packaging problem. On Openstack-ansible all the pip packages are mirrored and fetched on the repo_server. so I realized that pandas version 0.21.0rc1 is installed but this version is not stable. it is not compatible with numpy 1.12.0 version. I asked gnocchi channel and they suggested using pandas stable version. So I tried it and it worked.
1724538,2017-10-26 11:52:13 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/515376"
1724538,2017-10-27 07:28:11 UTC,"Reviewed:  https://review.openstack.org/515376
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_gnocchi/commit/?id=7fa88e5dec2f2828e3e0f44353932188eb9888ce
Submitter: Zuul
Branch:    stable/ocata"
1724538,2017-11-28 13:36:40 UTC,This issue was fixed in the openstack/openstack-ansible-os_gnocchi 15.1.12 release.
1724541,2017-10-22 15:56:46 UTC,"I added external_network_bridge = br-ex in l3_agent.ini, restarted l3 agent, reset router gateway, and it worked."
1724541,2017-10-24 03:25:26 UTC,"In that case, would a devstack solution suffice? i.e. detect we use legacy snat or that we are a network node, and add the external_network_bridge settings to l3_agent.ini ?"
1724543,2017-11-15 08:26:18 UTC,"Change abandoned by Anilkumar Thovi (<email address hidden>) on branch: master
Review: https://review.openstack.org/516672
Reason: committed in other review with some more changes"
1724543,2017-12-07 05:39:40 UTC,"Change-Id: I29db498a44d527dbbb917c90fae09d67c2ebbc76
https://review.openstack.org/#/c/519996/"
1724543,2017-10-26 09:44:59 UTC,This bug is related to monasca-api devstack plugin https://github.com/openstack/monasca-api/tree/master/devstack so changing it to monasca-api
1724543,2017-10-31 13:22:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/516672"
1724546,2017-10-19 07:41:03 UTC,Probably a station stop number indicated in the activity does not match with a platform in the .tdb file.
1724551,2019-11-03 03:39:30 UTC,What kind of dog we talking about?
1724562,2017-10-23 10:27:30 UTC,"3.13.0-135.184~precise1 - generic
Regression test CMPL."
1724562,2017-10-24 07:02:49 UTC,Hardware Certification have begun testing this -proposed kernel.
1724562,2017-10-25 12:54:30 UTC,Hardware Certification does not support precise test. Set it as invalid.
1724562,2017-10-31 13:31:44 UTC,The package has been published and the bug is being set to Fix Released
1724564,2017-10-25 19:50:59 UTC,"Can you test the 4.10.0-38 kernel in Zesty -proposed:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13563574"
1724564,2017-11-06 16:23:01 UTC,"Can you see if this bug also happens with the Artful kernel:
https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa2/+build/13567624"
1724564,2017-11-06 09:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1724564,2017-11-06 09:16:07 UTC,"It either worked then or I booted the wrong kernel. 4.10.0-38 and today's 4.10.0-39 are not working, so I am back to using in 4.9.45-040945 order to be able to access the machine."
1724564,2017-10-28 03:49:36 UTC,I did - the 4.10.0-38 kernel did the trick. Looks like it has been fixed in the upcoming release?
1724564,2017-10-26 16:09:16 UTC,You shouldn't need the headers .deb files.  Can you try just installing linux-image and linux-image-extra?
1724564,2017-10-26 07:56:57 UTC,The first one couldn't install:
1724564,2017-10-25 08:52:51 UTC,"Ah, I see. Yes, v4.14-rc6 allows me to enter the disk password, however wifi does not work: Ubuntu thinks the laptop has no wifi capability."
1724564,2017-10-30 17:24:13 UTC,"That is correct, -proposed is the next kernel to be released to -updates."
1724564,2017-10-24 19:42:42 UTC,The mainline kernel is the only one I can actually use.
1724564,2017-10-24 19:33:14 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1724564,2017-10-24 11:17:22 UTC,This issue is also preventing me from using paid snap applications (Hiri for access to email for work) so it is rather urgent. Any other information I can provide for this?
1724564,2017-10-20 07:01:15 UTC,It's a bit of a problem since this is blocking me from upgrading to Ubuntu 17.10.
1724564,2017-10-19 06:46:59 UTC,apport information
1724564,2017-10-19 06:46:57 UTC,apport information
1724564,2017-10-18 13:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1724564,2017-10-24 20:12:16 UTC,I see you posted you are using 4.9.45 in the bug description.  Does v4.14-rc6 also work?  It would be good to know to narrow down if we can bisect this issue and/or if its Ubuntu specific.
1724564,2017-10-19 06:46:58 UTC,apport information
1724565,2017-10-18 23:55:03 UTC,*** This is an automated message ***
1724565,2017-10-19 07:15:48 UTC,The package is ready to be uploaded to Debian upstream [1] but it needs a sponsor [2].
1724565,2017-11-12 12:34:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724565,2019-01-27 14:35:15 UTC,fzf seems to be already available upstream:
1724565,2020-07-04 17:11:12 UTC,Thanks for reporting and taking an interest in this package.
1724572,2019-08-25 20:21:44 UTC,"Hi,
Using chromium for doing a fast.com speedtest, while the test is running, clicking with the left button anywhere outside the chromium window and you will get the crash.
Sometimes just visiting fast.com, typing enter, same with speedtest.net"
1724572,2019-03-27 17:22:56 UTC,"When will this fix be completed in Ubuntu. I am running 18.04 and, because of this bug, can't use screen sharing when using Wayland."
1724572,2017-10-30 15:45:56 UTC,"vino doesn't work under wayland and should try to start in that session, did you try to start it manually?"
1724572,2017-10-30 08:40:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724572,2017-10-18 13:26:15 UTC,"StacktraceTop:
 _XSend (dpy=dpy@entry=0x558127139100, data=data@entry=0x7f2a58576f30 ""XInputExtension"", size=15) at ../../src/xcb_io.c:447
 XQueryExtension (dpy=dpy@entry=0x558127139100, name=name@entry=0x7f2a58576f30 ""XInputExtension"", major_opcode=major_opcode@entry=0x7ffe5c2962fc, first_event=first_event@entry=0x7ffe5c296300, first_error=first_error@entry=0x7ffe5c296304) at ../../src/QuExt.c:47
 get_xinput_base (dpy=0x558127139100) at ../../src/XTest.c:79
 find_display (dpy=0x558127139100) at ../../src/XTest.c:83
 XTestQueryExtension (dpy=dpy@entry=0x558127139100, event_base_return=event_base_return@entry=0x7ffe5c2963ac, error_base_return=error_base_return@entry=0x7ffe5c2963ac, major_return=major_return@entry=0x7ffe5c2963ac, minor_return=minor_return@entry=0x7ffe5c2963ac) at ../../src/XTest.c:101"
1724572,2017-10-30 15:45:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1724577,2019-04-22 02:47:08 UTC,"Hello Soras,
do you still have this issue with the latest 4.15 kernel on Xenial?
Thanks"
1724577,2019-06-21 04:17:24 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1724583,2017-10-19 08:09:59 UTC,GDM3 will certainly hide the Wayland options if any part of the Wayland start-up crashed. It catches the crash and just hides the option from you. So maybe we need to debug that and look for a hidden crash...?
1724583,2017-10-19 08:23:14 UTC,"OK, please try adding these to your /etc/environment and reboot with the BIOS setup to enable hybrid:"
1724583,2017-10-19 09:24:31 UTC,"Thank you for your responses, and I apologize if I sounded rude - I didn't meant to."
1724583,2017-10-19 09:26:40 UTC,"Correction: *those two cards are not completely separate but need to cooperate somehow (since Intel's connected to the panel while Nvidia's connected to HDMI, but they need to cooperate, for example when Intel needs to draw over HDMI when an external monitor is connected)"
1724583,2017-10-19 09:43:27 UTC,"Yes, please attach the log files."
1724583,2017-10-19 11:31:03 UTC,"Attaching mutter log; but removing lines such as these:
KEYBINDINGS: Grabbing keybinding keycode 133 mask 0x0 on 0x15a
Since it may reveal my password."
1724583,2017-10-20 08:03:28 UTC,"Ah, sorry. Please repeat the test but then also collect the output of:"
1724583,2017-10-20 08:04:09 UTC,"Sorry, make that the output of just:"
1724583,2017-10-23 09:22:33 UTC,"It worked! I switched my machine back to hybrid mode (so that both Intel and Nvidia cards are visible in lspci) and added the nouveau.modeset=0 kernel parameters. And now I am able to select the Ubuntu (wayland) option and indeed it works: XDG_SESSION_TYPE=wayland, and the About dialog shows ""Intel® HD Graphics 530 (Skylake GT2)"" as the Graphics card."
1724583,2017-10-23 09:14:19 UTC,"Daniel, thank you so much for your time investigating this, I appreciate it."
1724583,2017-10-24 05:18:38 UTC,modeset=0 sounds similar to the workaround for bug 1705369. Although the symptoms are a bit different.
1724583,2017-10-24 06:58:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724583,2017-10-31 21:29:06 UTC,I had the same problem with Intel + AMD tandem on a desktop. I solved it by adding in /etc/environment:
1724583,2017-12-10 18:12:34 UTC,"Adrian, thank you very much. Your advice saved me a lot of money."
1724583,2017-12-15 12:00:39 UTC,"I am using XPS 13 9360, it happens often that the login session goes without wayland."
1724583,2019-08-05 03:51:08 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1724583,2017-10-19 08:02:08 UTC,"I know sorry, but didn't explain myself well enough."
1724583,2017-10-23 07:47:46 UTC,I can see your system choosing to use X very early...
1724583,2017-10-19 08:00:33 UTC,I believe this is a bug in GDM3 detection algorithm which incorrectly disables Wayland support on a system which runs just fine with Wayland.
1724583,2017-10-19 07:08:45 UTC,I have switched to the Hybrid mode. Now the only session available is the Xorg-based session; About dialog shows that the Intel® HD Graphics 530 (Skylake GT2) is now being used. Could it be that it is not compatible with Wayland?
1724583,2017-10-19 07:39:04 UTC,"Thanks. I know Wayland+KMS doesn't work with NVIDIA proprietary. However, I don't use NVIDIA proprietary drivers and I don't have them installed and I don't want to use Wayland on NVIDIA proprietary. Thus, your conclusion is not right."
1724583,2017-10-19 07:44:00 UTC,"Thanks for the info on Hybrid mode - really nice! However, what I'd like is to run Ubuntu+Wayland on my Intel card only. So, I don't want to run it in hybrid mode, I don't want to run it on NVIDIA proprietary, just on the Intel card. KDE Plasma+Wayland runs fine and uses Intel only; GDM3 forces me to use Xorg for unknown reason. The only workaround is to ""set the Discrete mode in BIOS"" which only hides Intel card; then GDM3 allows me to run Wayland (on top of Nouveau). Works for me; yet I would still prefer to use just the Intel+Wayland configuration."
1724583,2016-12-07 07:42:06 UTC,"Created attachment 1228916
failed_wayland_gnome_shell_log.txt (journalctl)"
1724583,2016-12-07 07:43:50 UTC,"Created attachment 1228917
failed_gdm_log.txt (journalctl)"
1724583,2016-12-07 08:41:54 UTC,Same problem happens when the AMD card is swapped out for an Nvidia card.
1724583,2016-12-12 17:34:01 UTC,I can confirm this also happens on my system.
1724583,2017-01-02 22:12:21 UTC,Seems to be a similar problem to bug #1403512
1724583,2017-05-04 08:09:10 UTC,"Same here, workaround with radeon.modeset=0 helped with the problem."
1724583,2017-10-18 13:55:39 UTC,"Hm, there actually is /usr/share/wayland-sessions/ubuntu.desktop - could it be that gdm3 for some reason ignores this folder?"
1724583,2017-01-02 19:34:17 UTC,Same with these two cards on F25:
1724583,2017-10-18 14:16:44 UTC,Attaching my /etc/gdm3/custom.conf:
1724583,2017-10-18 17:05:42 UTC,I disagree about the duplicate status.
1724583,2017-10-18 18:36:53 UTC,"Solved! I went to BIOS and switched the Video card setting from Hybrid to Discrete. Now gdm3 offered the wayland option (or, rather, both ""Ubuntu"" and ""Ubuntu on Xorg""). I now run Wayland as confirmed by env|grep wayland:"
1724583,2017-10-19 07:25:21 UTC,"Also, hybrid support in Gnome is supposedly coming very soon:"
1724583,2017-10-19 02:16:26 UTC,Confirmed. For me this bug happens with Radeon cards (using the 'radeon' kernel module).
1724583,2017-10-19 06:23:13 UTC,"I actually have a nvidia card, and since I switched to Discrete mode in BIOS, Wayland session works properly; moreover it seems to be working on top of Nouveau (the About dialog says that Graphics is NV117)."
1724583,2017-10-19 07:23:38 UTC,Thanks. In that case this is not a bug. NVIDIA disables KMS support by default so Wayland sessions will be missing.
1724583,2017-10-18 14:08:35 UTC,"I enabled the debug logs for gdm3 in /etc/gdm3/custom.conf, but the logs are nowhere to be found: /var/log/gdm3 is empty."
1724588,2018-01-24 22:31:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1450
1724588,2017-10-20 01:39:49 UTC,https://raw.githubusercontent.com/percona/percona-toolkit/3.0/bin/pt-online-schema-change
1724588,2017-10-19 14:48:35 UTC,"Hi,"
1724588,2017-10-20 01:32:49 UTC,"Hi Carlos,"
1724589,2017-10-25 19:22:05 UTC,This issue was fixed in the openstack/nova 16.0.2 release.
1724589,2017-10-24 12:41:37 UTC,This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
1724589,2017-10-19 18:25:39 UTC,"Reviewed:  https://review.openstack.org/513198
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=842641c9b0b8f60d0e19b38ad1180078e9c4330c
Submitter: Zuul
Branch:    stable/pike"
1724589,2017-10-18 22:33:08 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/513198"
1724589,2017-10-18 16:09:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/513085"
1724589,2017-10-19 04:58:35 UTC,"Reviewed:  https://review.openstack.org/513085
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5c2b8675e3e13e32b23681153f226de93bb99628
Submitter: Zuul
Branch:    master"
1724589,2017-10-18 14:55:59 UTC,"To deal with the issue in comment #2 above, before we get here:"
1724589,2017-10-18 14:55:44 UTC,"Best way forward seems to be fixing up the allocations in here:
https://github.com/openstack/nova/blob/e11a8687aef527eee9f7c733db6cccd5b902afbb/nova/virt/ironic/driver.py#L523"
1724589,2017-10-18 14:48:50 UTC,"One thought is that the ironic driver itself could update the allocations once a flavor is migrated and has a new custom resource class. That gets tricky for anyone that has already upgraded to pike and some of their instances / nodes have migrated - the nova code would have to check the existing allocations and see if they contain the custom resource class, and we don't want to do that check on every flavor migration run (which happens when nodes are refreshed)."
1724589,2017-10-18 14:44:26 UTC,"From IRC, my way of describing the problem:"
1724589,2017-10-18 15:01:26 UTC,"(10:00:03 AM) mriedem: johnthetubaguy: one issue might be a chicken and egg with the custom RC inventory being available when we PUT /allocations/{consumer_uuid}
(10:00:20 AM) mriedem: because the inventory gets updated via the RT periodic
(10:01:01 AM) mriedem: so if i just set a custom rc on my ironic node, the periodic runs, it detects the new rc and will update inventory, but while in the driver we're migrating the instance because it's node has an rc now, if we try updating the allocation for that rc before the node RP inventory has that rc, it will fail with a 409
(10:01:07 AM) johnthetubaguy: mriedem: dang, yeah
(10:01:08 AM) mriedem: ""409 Conflict if there is no available inventory in any of the resource providers for any specified resource classes or inventories are updated by another thread while attempting the operation."""
1724590,2018-06-02 08:42:16 UTC,"Hello,"
1724590,2019-08-23 14:15:13 UTC,"Hi Guys - I'm currently trying to use IPv6 with QEMU on ARM / AARCH64 Models (Sabre-Lite / Zync SOCs) and I see this problem. The system gets an IPv6 address from the QEMU in-built router which can be used to ping the default gateway (the dhcp router itself). All this is good but not really useful as I want to communicate with a TCP6 client on the host (Windows / Linux) machine running on port 8080. I've added the co-responding port mappings (like I do with IPv4) but I never receive packets from the host OS which is this issue. So I have the following questions,
- It seems that this issue is still open and on the wishlist. Is this correct ? If so, is there any ETA to when someone will take this up ? If none, may be I can look at this ;-).. I'm currently using QEMU 3.0
- Assuming that its not working, what are the alternatives that I can use ? I understand that there is TAP-TUN Networking where the QEMU model can communicate with the hardware interface over a bridge.. This should work with IPv6.. Can you confirm ?"
1724596,2018-04-12 20:51:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724596,2017-10-19 15:19:16 UTC,"I was using the super key to search for libre office base and it came up in the results under software, so I clicked to install it and it came up with the error and suggested I submit the bug with the info it had generated.  I did this, then tried installing from command line sudo apt install libreoffice-base I think.  I can't recall at this point whether it may have said it was already installed or went through the install process.  In any event, when I used the super key to find libre office, base was now available and I have used it successfully with no problems.  Cheers"
1724596,2017-10-18 14:58:15 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ff0253d14e8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=<optimized out>, str=0x7ff0253d1870 ""double free or corruption (out)"", ptr=<optimized out>, ar_ptr=<optimized out>) at malloc.c:5425
 _int_free (av=0x7ff025603c20 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4174
 __GI___libc_free (mem=<optimized out>) at malloc.c:3144
 g_hash_table_remove_all_nodes (hash_table=hash_table@entry=0x561ef93276a0, notify=notify@entry=1, destruction=destruction@entry=0) at ../../../../glib/ghash.c:549"
1724596,2017-10-19 14:24:01 UTC,Thank you for your bug report. Was that the snap that you installed? Did the installation work?
1724609,2017-10-18 16:25:59 UTC,"StacktraceTop:
 talloc_abort (reason=0x7ff080537fa8 ""Bad talloc magic value - unknown value"") at ../talloc.c:426
 talloc_abort_unknown_value () at ../talloc.c:444
 talloc_chunk_from_ptr (ptr=0x7ff05402baa0) at ../talloc.c:463
 _talloc_realloc (context=0x0, ptr=0x7ff05402baa0, size=30, name=<optimized out>) at ../talloc.c:1749
 __talloc_vaslenprintf_append (s=0x7ff05402baa0 ""/var/cache/samba"", slen=16, fmt=0x7ff082405fa5 ""/%s"", ap=0x7ff063ffe438) at ../talloc.c:2588"
1724609,2017-10-19 13:59:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724609,2017-10-19 14:02:23 UTC,Got this error in Live session (from USB) before install of fresh 17.10
1724614,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1724614,2018-03-19 10:55:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1724614,2018-03-21 11:58:58 UTC,#VERIFICATION-XENIAL
1724614,2017-10-18 16:56:45 UTC,Do you plan on submitting an SRU request to the kernel team mailing list?
1724614,2017-10-18 17:29:38 UTC,"@jsalisbury,"
1724615,2017-10-18 17:20:22 UTC,apport information
1724615,2017-10-18 17:44:21 UTC,"'splash' isn't in /proc/cmdline, and not in /etc/default/grub. I'm reassigning this to grub-installer while I figure out if it's really done on purpose or if this is a regression."
1724615,2017-10-18 17:20:25 UTC,apport information
1724615,2017-10-18 20:41:49 UTC,"This appears to be intentional, but should be revisited. It's set in debian-cd."
1724615,2017-10-18 17:20:24 UTC,apport information
1724615,2017-10-18 17:20:22 UTC,apport information
1724615,2017-10-18 17:20:20 UTC,apport information
1724615,2017-10-18 17:20:14 UTC,apport information
1724615,2017-10-18 17:20:18 UTC,apport information
1724615,2017-10-18 17:20:17 UTC,apport information
1724615,2017-10-18 17:20:15 UTC,apport information
1724615,2017-10-18 17:20:12 UTC,apport information
1724615,2017-10-18 17:09:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1724615,2017-10-18 17:20:19 UTC,apport information
1724617,2017-11-20 11:22:26 UTC,"Hi John,"
1724618,2019-09-19 12:05:04 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1724621,2018-09-24 14:46:48 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1724621,2018-07-26 01:14:26 UTC,"Reviewed:  https://review.openstack.org/580775
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=70de423255fd01822188bb9082a0c0cc1c8ec2d0
Submitter: Zuul
Branch:    stable/pike"
1724621,2018-07-06 21:52:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580775"
1724621,2017-12-07 23:56:03 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1724621,2017-10-25 12:01:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/515034"
1724621,2017-10-18 21:52:38 UTC,"Following the discussion on the IRC channel, we have thus decided to do a follow up deletion of those instance_mappings from the nova-api database which is not done currently, once the corresponding rows are archived from the instances table using nova-manage db archive_deleted_rows."
1724621,2017-10-18 17:27:06 UTC,End users of the REST API (with appropriate policy permission) can 'nova list' deleted instances. So it's not straightforward to decide whether or not to show that the instance is mapped. It *is* mapped and it can be seen by the end user if they can list deleted instances.
1724621,2017-10-18 17:07:05 UTC,There are other related bugs like below dealing with the existence of information about deleted instances in the instance_mapping table :
1724621,2017-11-21 19:04:35 UTC,"Reviewed:  https://review.openstack.org/515034
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=32fd58813f8247641a6b574b5f01528b29d48b76
Submitter: Zuul
Branch:    master"
1724623,2018-07-19 13:17:36 UTC,cloud-init can collect relevant logs with 'cloud-init collect-logs'
1724630,2019-02-19 13:05:34 UTC,gnome-shell-extension-ubuntu-dock and gnome-shell-extension-dashtodock are two different packages. The -ubuntu-dock one is the one installed by default and the bug has already been fixed there. The fix has not yet been released in gnome-shell-extension-dashtodock.
1724630,2017-12-07 22:44:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724630,2019-01-15 16:18:17 UTC,Fix proposed upstream: https://github.com/micheleg/dash-to-dock/pull/868
1724630,2019-02-19 12:55:21 UTC,"There is a confusion between those two packages, gnome-shell-extension-dashtodock and gnome-shell-extension-ubuntu-dock. We follow the ubuntu one."
1724633,2017-11-13 07:10:03 UTC,"Reviewed:  https://review.openstack.org/513149
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d4398f715f098b9edbc0be8612b6c079a8e607af
Submitter: Zuul
Branch:    master"
1724633,2017-10-18 17:47:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/513149"
1724638,2017-10-18 17:57:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724638,2017-10-18 17:58:10 UTC,"The real fix for this bug is to fix original bug 1302416 a better way, by preventing the memory growth in the first place."
1724638,2019-11-14 04:29:04 UTC,Closing this because we took out the memory cap.
1724639,2018-01-22 19:39:40 UTC,"I like how all others list this as ""critical"" or ""high"" priority, but Ubuntu is like ""it's mostly 32-bit users, *bleep* 'em"". Shows that they're dropping 32-bit support when they don't care about critical bugs."
1724639,2018-01-20 10:58:50 UTC,"Hello,"
1724639,2018-01-20 08:46:08 UTC,"@Pawel Por don't worry about Meltdown, afaik Atom N270 CPU in your netbook is not vulnerable"
1724639,2018-01-19 19:39:44 UTC,I'm using laptop Samsung N130 and also have this issue with kernel 4.13.0-26-generic. Downgrading to kernel 4.10.0-42-generic solves the issue but this kernel is Meltdown vulnerable. I've reported my issue #1742756
1724639,2018-01-16 01:58:54 UTC,IBM Thinkpad t60 running ubuntu 16.04 LTS just got kernel update and experiencing this issue.
1724639,2018-01-13 18:15:23 UTC,"I confirm the issue with an Samsung NC10 with integrated Intel Mobile 945 GSE After a fresh install of lubuntu 16.04.3 and first Auto-Update. The current 32 Bit Desktop iso brought kernel 4.10, everything was fine. The first update installed  Kernel 4.13.0-26 which still has the defect.
GRUB_GFXPAYLOAD_LINUX=text solved the problem. Thanks for this Solution!"
1724639,2018-01-06 21:09:42 UTC,"Toshiba Portege R500 (Graphics Processor Intel GMA 950, Intel Core 2 Duo CPU U7700 @ 1.33 GHz)"
1724639,2017-12-30 08:57:09 UTC,"(In reply to Shon Vella from comment #13)

> I'm seeing the same problem on Gateway LT2030u with Intel Mobile 945 GME
> Graphics Chipset, after an autoupdate of the kernel from 4.12.9-1-default to
> 4.14.8-1-default
"
1724639,2017-12-30 04:38:04 UTC,"I'm seeing the same problem on Gateway LT2030u with Intel Mobile 945 GME Graphics Chipset, after an autoupdate of the kernel from 4.12.9-1-default to 4.14.8-1-default"
1724639,2017-11-01 17:31:50 UTC,"Hi,"
1724639,2017-11-01 17:29:54 UTC,"John, from the terminal issue command"
1724639,2017-11-01 17:08:39 UTC,"Can someone help me out how to do this edit. As I have never edited a GRUB before.I'm not even sure what the GRUB is
If I press e is this giving me the GRUB?
Where do I insert the Line GRUB_GFXPAYLOAD_LINUX=text?
Do I then Ctrl_x and go to terminal to do the sudo bit?
Or should I be editing a file from the terminal?"
1724639,2017-11-01 16:01:11 UTC,"""GRUB_GFXPAYLOAD_LINUX=text"" works with ideapad S10-2 (Atom with Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 03) after kicking out noplymouth für quiet splash."
1724639,2017-11-01 04:09:51 UTC,No the issue does not reappear
1724639,2017-11-01 13:20:00 UTC,"I have edited /etc/default/grub on my EeePC-901X as ""GRUB_GFXPAYLOAD_LINUX=text"".
Then, I rebuild grub by sudo grub-mkconfig -o /boot/grub/grub.cfg."
1724639,2017-11-01 12:24:20 UTC,"Toshiba NB100, screen resolution 1024x600, after upgrading to kernel 4.13.0-16 (from 4.10.0-37) also affected. VGA:"
1724639,2018-01-22 21:26:22 UTC,"Matti, it affects 64-bit as well.
It's a pity 4.15 is not yet in Ubuntu,
in fact even with the grub edit stuff, I need
to reboot the machine once after power-on
to get graphics X, and my CTRL key is broken,
so I can't boot without external keyboard
as I cannot even switch to a text console. :("
1724639,2018-01-23 19:02:02 UTC,"With my Ubuntu version 16.04 LTS i didn't have the problem, until recently!
I suspect with an update from kernel 4.10.x to 4.13.x
So I manually removed the kernel image and headers from version 4.13.x, thereby in fact downgrading again to the older kernel, fixing my problem.
So this confirms the statement above that kernel 4.13 is a problematic one."
1724639,2018-03-15 20:42:06 UTC,"Installing kernel 4.16 (see https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds) fixed it.
But now the wifi adapter is not found."
1724639,2018-02-10 06:46:42 UTC,"This bug affected me on my old Dell Mini 9. I hadn't used the thing in years because the battery died. I found am inexpensive battery and figured I'd make a coffee table machine putting lubuntu on it, and I had the same problem. A friend of mine and I fixed it as per this thread:"
1724639,2018-06-17 01:24:17 UTC,The issue reported in comment #108 is still present in kernel 4.15.3:
1724639,2018-06-16 11:44:55 UTC,So it looks like the bug is fixed since 4.15.3.
1724639,2018-05-27 10:04:41 UTC,"Hi,"
1724639,2018-04-25 11:03:07 UTC,"Hi,"
1724639,2018-04-02 10:08:21 UTC,"confirming that on TOSHIBA Portege, the bug has disappeared after upgrade to 18.04 beta with kernel 4.15.0-13."
1724639,2018-03-24 00:28:04 UTC,"Same problem on Gigabyte GA-T1028X
Intel® Atom™ Processor N280(1.66GHz)
Mobile Intel® GS945 Express Chipsets
Intel® GMA 950"
1724639,2017-10-31 03:39:14 UTC,"Does ""GRUB_GFXPAYLOAD_LINUX=text"" make the issue reappear?"
1724639,2018-03-15 20:16:42 UTC,"My my Lenovo has a Intel Mobile 945GM/GMS/GME integrated graphics controller.
Using ""nomodeset"" in the boot menu helps."
1724639,2018-03-13 07:17:03 UTC,Maybe same issue at Ubuntu 16.04.4 with Intel Graphic 945.
1724639,2018-03-07 14:51:12 UTC,"Sorry, but after upgrading the kernel to 4.13.0-36, the screen went bad again. Even booting with the old kernel did not work anymore. But the GRUB_GFXPAYLOAD_LINUX=text solution worked..."
1724639,2018-03-07 12:44:28 UTC,"I had the same issue on an Acer Aspire One with a fresh Lubuntu 17.10.1 install. Trying to prevent the system from continuously going to sleep I set ""HandleSuspendKey"" and ""HandleLidSwitch"" to ignore in /etc/systemd/login.conf. After that the screen problem appeared.
When I commented out the HandleSuspendKey again, everything worked fine!"
1724639,2018-02-21 13:46:57 UTC,"Hi People,"
1724639,2018-02-21 00:28:03 UTC,"I try all 4.15 kernels via UKUU on Asus EeePC-1007HE. Bug present until I apply ""grub fix"" from this thread."
1724639,2018-02-20 17:18:37 UTC,"The 'grub workarounds' DID work for me (Lubuntu 16.04 on 1000H; once I stumbled across right search keywords, they are 'easy' do/try, tho I don't understand HOW they work)."
1724639,2018-02-17 19:54:02 UTC,"""GRUB_TERMINAL=console"" in /etc/default.grub followed by ""sudo update-grub"" fixed it for me after I updated my Mum's laptop."
1724639,2018-02-15 13:28:58 UTC,"Deal all,"
1724639,2018-02-10 11:00:12 UTC,"Bug affects me on Acer Aspire One ZG5; Intel Graphics is GMA 950 however.
4.13.0-32-generic
Xubuntu 16.04.3 LTS
Grub Version 2.02~beta2-36ubuntu3.15"
1724639,2018-01-23 19:33:38 UTC,"Hi Tom,"
1724639,2017-10-31 01:23:03 UTC,"I got it working in Arch without downgrading the kernel it may work for Ubuntu as well.
Edit the grub file and comment the following entry;
GRUB_GFXPAYLOAD_LINUX=keep
Then rebuild the grub"
1724639,2017-10-28 16:25:42 UTC,Just found some sort of workaround - boot to login screen (gdm) which is 80% invisible and press Power button. Notebook going to suspend. Press Power button again - notebook waking up and screen is ok!
1724639,2017-10-30 14:02:44 UTC,@kaihengfeng
1724639,2017-10-19 12:53:11 UTC,"As I mentioned earlier, when a screenshot is taken of the corrupted screen, a perfect snapshot is produced, suggesting the frame buffer is OK and the problem lies elsewhere."
1724639,2017-10-19 12:44:17 UTC,"SUMMARY:-
Installed upscreen kernel, still got problems. See below for details:-"
1724639,2017-10-18 19:24:16 UTC,"Hi Joseph,"
1724639,2017-10-18 19:09:13 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1724639,2017-10-18 18:47:02 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1724639,2017-10-30 14:04:36 UTC,"@ Everyone confirming this bug... Please click on ""This bug affects me"" on the top of the page (right underneath the title in small and green). Thank you =)"
1724639,2017-10-18 18:09:19 UTC,Here is a photo of the problem.
1724639,2017-10-19 17:17:06 UTC,Does this also happen to 64bit version?
1724639,2017-10-12 17:33:53 UTC,The same Problem appeares on an Acer Aspire One A110L
1724639,2017-09-22 15:18:18 UTC,"(In reply to Axel Braun from comment #8)

> BTW, I noticed the same exception when booting kernel 4.12.11, but with no
> further impact
"
1724639,2017-09-22 05:10:27 UTC,"BTW, I noticed the same exception when booting kernel 4.12.11, but with no further impact"
1724639,2017-09-21 16:17:32 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=102929
1724639,2017-09-21 07:27:27 UTC,Hmm...
1724639,2017-09-20 06:09:49 UTC,"Created attachment 741173
dmesg"
1724639,2017-09-19 14:15:32 UTC,Could you attach output of dmesg?
1724639,2017-09-18 16:03:50 UTC,My graphic card is a Intel(R) Graphics 520.
1724639,2017-09-26 05:36:02 UTC,"There is indeed a difference:
 Kernel 4.13.1 throws 2 exceptions:
[    7.353528] ------------[ cut here ]------------
[    7.353698] WARNING: CPU: 1 PID: 259 at ../drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915]
[    7.353703] Modules linked in: ata_piix i915(+) serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
[    7.353757] CPU: 1 PID: 259 Comm: systemd-udevd Not tainted 4.13.1-1-pae #1
[    7.353777] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903    03/17/2009
[    7.353793] task: f4ae4700 task.stack: f4b3c000
[    7.353956] EIP: assert_planes_disabled+0x128/0x140 [i915]
[    7.353960] EFLAGS: 00010286 CPU: 1
[    7.353965] EAX: 00000046 EBX: f4bbc000 ECX: f71eb340 EDX: f71e486c"
1724639,2017-10-19 17:35:47 UTC,"Hi Kal,"
1724639,2017-10-18 18:30:07 UTC,This change was made by a bot.
1724639,2017-10-21 17:52:37 UTC,I can't add much to this apart from a small amount of personal experience.
1724639,2017-10-20 06:49:00 UTC,"You need to file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/Intel"
1724639,2017-10-30 09:13:46 UTC,"Please try the i386 build from here, http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/"
1724639,2017-10-28 17:39:30 UTC,I can confirm that this works on the Samsung NC10 too. I had to start up first in the previous version of the Kernel and set the function of the Power Button to suspend ( it was set to power off.
1724639,2017-10-28 16:13:08 UTC,"Same issue after upgrade from Xubuntu 17.04 to 17.10 32 bits on Samsung NC10.
So I still use 4.10.0-37-generic xubuntu 17.04 kernel.
But Booting on 17.10 xubuntu 32 bits live CD works."
1724639,2017-10-28 15:54:11 UTC,Have same issue on Fujitsu M2010 laptop.
1724639,2017-10-27 17:12:50 UTC,"I have the same exact issue on Acer Aspire One A110 (ZG5). In my case this happened after upgrade from 17.04 to 17.10. The workarounds are either pass nomodeset option to kernel at boot, or just choose the previous kernel (4.10 in my case). The latter solution gives me correct 1024x600 resolution and is preferred until this problem is resolved."
1724639,2017-10-26 18:26:31 UTC,My laptop is working now. I don't know how (One of them at least). I don't remember that I've done anything to it. I was using windows...
1724639,2017-10-25 18:59:07 UTC,"Can confirm! I have two laptops with Atom n270, both are affected."
1724639,2017-10-30 13:51:46 UTC,I can confirm the bug occurring after an upgrade from Lubuntu 17.04 to 17.10 on a HP Mini 5101 Netbook.
1724639,2017-10-23 08:57:43 UTC,with ideapad S10-2 noplymouth start process runs until tty1-login. After that only blueish pixels appear at the upper edge of the screen. With nomodeset edit in grub the netbook can be used. About 5(?) years ago intel 945 had similar trouble with kernel.
1724639,2017-10-23 07:02:17 UTC,Please try versions form 4.13-rc1 to 4.13-rc7.
1724639,2017-10-22 20:38:19 UTC,"Hi All,"
1724639,2017-10-22 18:47:29 UTC,"Hi All,"
1724639,2017-10-22 10:42:16 UTC,@kaihengfeng;
1724639,2017-10-22 08:42:20 UTC,"I can confirm the bug too.
After the Xubuntu update from 17.04 to 17.10, the intel mobile graphics is broken."
1724639,2017-10-21 18:38:41 UTC,The it's a regression.
1724639,2017-10-23 12:53:24 UTC,"Hi Kai-Heng,"
1724645,2019-09-27 09:10:36 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1724645,2019-07-30 18:50:22 UTC,"Reviewed:  https://review.opendev.org/637305
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bf67b3c88409d2f0b2086d363ed91394953d85ba
Submitter: Zuul
Branch:    master"
1724645,2018-09-26 14:39:11 UTC,I marked https://bugs.launchpad.net/keystone/+bug/1585472 as a duplicate of this bug
1724645,2017-10-26 02:42:38 UTC,"Reviewed:  https://review.openstack.org/513960
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=cbdc84ac7fc88e891968116db4866dc719337b16
Submitter: Zuul
Branch:    master"
1724645,2017-10-23 19:19:30 UTC,"For Federation, we can't cleanly demarcates configuration from (API) operation, as we have other third party dependencies (i.e. Apache, mellon, shibd, haproxy, etc). In other words, you can't just add a new provider, protocol, and mapping via API, and whalah things just magically work. You'll also need to adjust the 3rd party services before the data even gets to the Keystone app."
1724645,2017-10-23 18:20:17 UTC,remote_id_attribute should be added to the protocolo object such as in the create call here:
1724645,2017-10-21 19:04:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/513960"
1724645,2017-10-21 18:23:24 UTC,The workaround is to do something like this in the config:
1724645,2017-10-24 14:20:52 UTC,"The fact that we can modify both tthe Federation protocol object *AND* the Apache config means that we do not need to be able to also tweak things inside the configuration file, and right now, that config is making it impossible to the the federation protocol right.  So, yes, we need to drop the config option from the file and move it to the federation protocol, and no, that will not negatively impact our ability to make things work based on the Apache config."
1724651,2017-10-19 08:58:50 UTC,"Confirmed, it's small but quite visible"
1724651,2017-10-19 14:53:19 UTC,"This is actually a nautilus bug. In nautilus-toolbar the color ""#fdfdfd"" is hardcoded."
1724651,2017-10-27 11:24:54 UTC,"indeed, https://github.com/GNOME/nautilus/blob/master/src/nautilus-toolbar.c#L590"
1724657,2017-10-24 19:50:33 UTC,How do I go about it? Consider me being a Windows GUI having the live ISO at hand.
1724657,2017-10-25 00:05:13 UTC,"Well, I'm not clear on the limitations of live ISOs but since you were able to install linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb, it shouldn't be any harder to install the .deb for intel-microcode-3.20170707.1~ubuntu17.04.0 or newer. I suppose try rebooting first with just the updated microcode installed and validate that /proc/cpuinfo shows a newer version, and then reboot with the new kernel additionally."
1724657,2017-10-26 03:18:03 UTC,"Chatty, to be more clear, do you mean that the issue is gone with intel-ucode installed?"
1724657,2017-10-26 20:47:58 UTC,"I beliebe the new ucode is saved in the initrd which I didn't use. It mighty bei possible to for users having an existing working installation to upgrade kernel and ucode (initrd). But Surface Book users starting from scratch with the live ISO are still faced with an instant freeze which they can't solve with the tools at hand (like additional boot parameter).
So this needs to be resolved by some package maintainer responsible for that part of the live ISO. I'll be a willing prey to help testing."
1724657,2017-10-27 07:15:14 UTC,http://people.canonical.com/~khfeng/lp1724657-2/
1724657,2017-10-27 09:56:49 UTC,Last one still is an instant freeze.
1724657,2017-10-27 17:46:42 UTC,http://people.canonical.com/~khfeng/lp1724657-3/
1724657,2017-10-27 18:30:36 UTC,Another freeze. Could you please supply a bunch of kernels I can test? Could speed up the process.
1724657,2017-10-27 19:14:44 UTC,No I can't. You can't build a kernel before knowing next commit to try.
1724657,2017-10-27 19:35:08 UTC,"See comment #21. I don't have a productive Linux system. And again, I'm just extracting the plain kernel image ""vmlinuz"" from your deb and try to boot it via grub cli."
1724657,2017-10-28 23:30:57 UTC,I finally solved it by inserting intel-ucode.img (taken from archlinux-2017.10.01-x86_64.iso) as the first initrd in grub.cfg. This updates the microcode very early in the boot process. I tried this with the kernel delivered with Ubuntu 17.10 (4.13.0-generic). So updating linux-firmware is the resolution. This also solves this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1724650
1724657,2017-10-29 06:52:31 UTC,"Ok, the wifi problem is evident since more than two years (see https://bugzilla.kernel.org/show_bug.cgi?id=109681#c66)."
1724657,2017-11-01 19:34:11 UTC,Now that I found a fix does noone care anymore?
1724657,2017-12-19 11:50:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724657,2018-05-07 07:57:25 UTC,"It would be interesting to try the linux kernel v4.15, it had solved a boot freeze on my side.
See : https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200"
1724657,2017-10-24 15:39:14 UTC,"Your intel microcode is
microcode	: 0x9e
and 0xb2 or newer was needed to boot linux 4.13 without a hang at boot least for me. Try installing / upgrading the intel-ucode package."
1724657,2017-10-24 10:36:34 UTC,Your 4.12 also freezes the system. No additional output with Ben's parameters either. Hope this helps?
1724657,2017-10-25 06:44:06 UTC,I just extracted the kernel image (vmlinuz.*) and made it boot using grub club (as described in #7 and #15).
1724657,2017-10-24 08:25:09 UTC,"That's where I took my kernels from. And the earliest 4.13 in there is 4.13.0-041300rc1-generic as I already said in #3!!!
In #15 I was asking for something in between 4.12.14-041214-generic and 4.13.0-041300rc1-generic."
1724657,2017-10-18 18:50:24 UTC,Ubuntu 17.04 works just fine as you can see by this bug report.
1724657,2017-10-19 07:21:08 UTC,I pinpointed the problem a little further. I can boot any kernel up to vmlinuz-4.12.14-041214-generic. Boot freeze happens starting from vmlinuz-4.13.0-041300rc1-generic.
1724657,2017-10-24 09:21:30 UTC,Right. My apology.
1724657,2017-10-19 22:16:07 UTC,No apport with affected kernel possible due to system freeze but see two posts above.
1724657,2017-10-20 04:27:46 UTC,"SurfaceBook has a nvidia chip, right?
Can you try ""blacklist=nouveau modprobe.blacklist=nouveau"" kernel parameter?"
1724657,2017-10-20 07:53:03 UTC,My Surface Book sports a NVidia 940M (10DE:134B).
1724657,2017-10-20 16:17:39 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1724657,2017-10-19 22:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1724657,2017-10-23 03:42:17 UTC,To clarify: It still affects Arch Linux but the use of Launchpad to report arch-linux-linux bugs is not supported.
1724657,2017-10-23 04:14:11 UTC,Is it a regression in v4.13? Does v4.12 have this issue?
1724657,2017-10-23 17:12:51 UTC,"I already said four days ago that I can but any kernel up to the latest 4.12.14. Any kernel starting from 4.13 freezes at boot. So yes, it's a regression lying probably in the decompression code."
1724657,2017-10-24 01:52:10 UTC,Does adding
1724657,2017-10-24 03:37:03 UTC,Sorry I didn't notice you already mentioned that.
1724657,2017-10-24 07:16:15 UTC,"@Ben: Does not change a thing. I grub cli I type ""linux /casper/vmlinuz.efi debug earlyprintk=efi"" and then ""boot"" and system freezes immediately."
1724657,2017-10-24 07:47:03 UTC,v4.13-rc[1..7] from [1] is release between v4.12 and v4.13.
1724657,2017-10-20 16:30:54 UTC,I already tested linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb to no avail. I guess since 4.13 something in the kernel compression has been changed.
1724678,2019-04-18 07:01:58 UTC,"Hello,
do you still have this issue with other releases?
Thanks"
1724678,2019-06-18 04:17:24 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1724680,2017-10-24 08:38:17 UTC,+1
1724680,2017-10-24 08:39:44 UTC,"The issue for the metaserver is on https://github.com/widelands/widelands_metaserver/issues/14, so I'll set this back to Widelands- this will need some UI too."
1724680,2019-09-17 10:34:14 UTC,Migrated to https://github.com/widelands/widelands/issues/2082
1724685,2017-10-18 20:59:11 UTC,"Probably can't fix this until we've added microversion support, since API guidelines say you can't change return codes without a microversion."
1724685,2018-09-04 14:26:51 UTC,404 means not found.  The role assignment you requested was not found.  I don't think this is a stretch.
1724685,2018-09-04 16:59:29 UTC,"404 doesn't mean something/anything was not found. It specifically means that the requested resource (from the URI) was not found. In this case, that would be trust, which is obviously nonsensical when you're creating a trust."
1724688,2017-10-18 21:30:05 UTC,"I suppose I'll attach my ~/.gnupg/gpg.conf and ~/.gnupg/dirmngr.conf, just in case. First, here's my gpg.conf."
1724688,2017-10-18 21:30:22 UTC,And here's my dirmngr.conf.
1724698,2017-12-04 22:14:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724701,2018-01-24 22:31:43 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1451
1724701,2017-10-19 14:52:03 UTC,"Hi,"
1724703,2017-10-18 23:25:55 UTC,"StacktraceTop:
 gtk_widget_translate_coordinates (src_widget=src_widget@entry=0x55609bab4d00, dest_widget=dest_widget@entry=0x0, src_x=src_x@entry=166, src_y=src_y@entry=92, dest_x=dest_x@entry=0x7ffdf2897a2c, dest_y=dest_y@entry=0x7ffdf2897a38) at ././gtk/gtkwidget.c:6291
 _update_widget_coordinates (data=<optimized out>, gesture=0x55609bddb640) at ././gtk/gtkgesture.c:504
 _gtk_gesture_update_point (gesture=0x55609bddb640, event=<optimized out>, add=<optimized out>) at ././gtk/gtkgesture.c:611
 gtk_gesture_handle_event (controller=0x55609bddb640, event=0x55609c044e80) at ././gtk/gtkgesture.c:740
 gtk_gesture_single_handle_event (controller=0x55609bddb640, event=0x55609c044e80) at ././gtk/gtkgesturesingle.c:222"
1724703,2017-10-19 05:34:08 UTC,"This has been fixed in gtk+ trunk, but not in gtk 3-22."
1724703,2017-11-01 06:29:26 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/d2d00044a6ddec05e9b3b147cf942bd3aa56010d"
1724703,2020-01-24 10:03:53 UTC,Zero crash reports in 18.04 onward.
1724705,2018-01-30 20:11:44 UTC,"I'm still getting a ""MediaKeys"" error at https://bitmovin.com/mpeg-dash-hls-drm-test-player/ as of the Ubuntu-provided Firefox 58.0."
1724705,2018-02-17 16:18:18 UTC,"As of Firefox 58.0.2, I can reproduce this problem at https://shaka-player-demo.appspot.com/ too. Looking at the ""Asset"" dropdown on that page with the Ubuntu-provided version of Firefox, various DRM-related options are grayed out, including the Widevine options. With the downloaded-from-Mozilla version of Firefox, the Widevine options are available."
1724705,2018-08-11 14:12:10 UTC,"Using Firefox 61.0.1 provided by Ubuntu, using Ubuntu 16.04, with a new Firefox profile: https://shaka-player-demo.appspot.com/ redirects to https://shaka-player-demo.appspot.com/demo/#asset=https://storage.googleapis.com/shaka-demo-assets/angel-one/dash.mpd;lang=en-US;build=uncompiled and, after enabling DRM and waiting for the Widevine plugin to install, fails with a yellow bar at the top that says ""The WidevineCdm plugin has crashed."""
1724707,2017-10-19 09:49:56 UTC,While probably not used often this sounds like a reasonable request.
1724711,2017-10-22 06:53:00 UTC,How could I gather more info about this issue without rsyslog?
1724711,2017-10-22 06:50:48 UTC,After reboot it is not running again.
1724711,2017-10-30 22:34:12 UTC,I think it can't start because /var/run/rsyslogd.pid does not removed on shutdown.
1724711,2017-10-19 01:17:55 UTC,"Since rsyslog does not work, I replace it to inetutils-syslogd, but it seems like inetutils-syslogd has some problems with apparmor, but aa-logprof gives me nothing and says all is ok."
1724711,2017-10-21 18:48:47 UTC,Today rsyslog started fine. I don't know what the problem was.
1724720,2017-10-19 11:53:30 UTC,"running Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06), I get the following Python error message:"
1724720,2017-10-20 01:05:53 UTC,"When I export the dxf from Inventor as the AutoCAD 2013 DXF version, I still get this error:"
1724720,2017-10-20 12:05:26 UTC,Just for reference in case someone has the same issue. A workaround is to export a PDF from Inventor and import that into Inkscape. You need to un-group it a few times in order to access individual paths.
1724720,2017-10-20 12:38:12 UTC,Duplicate of https://bugs.launchpad.net/inkscape/+bug/1683063 ?
1724720,2019-04-12 11:31:26 UTC,Hi
1724720,2020-03-15 21:41:26 UTC,Same here with a DXF from Vectorworks.
1724746,2017-11-17 16:29:35 UTC,"One of the solutions is to download manually the missed package. get_extra_file usually followed by the package link that monasca-api cannot download. Use these steps to resolve the issue:
1. Download the packet: # wget package_link
2. Comment all lines related to downloaded packages in monasca-api/devstack/plugin.sh
3. Replace the variable_dst at installation line by the local file that you already download.
Example if the issue is with kafka: go to line 311 of plugin.sh and replace sudo tar -xzf $kafka_tarball_dest by sudo tar -xzf ~/kafka_2.11-0.9.0.1.tgz"
1724748,2017-10-19 06:36:58 UTC,Already reported as lp:1713313
1724748,2017-10-19 06:37:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724749,2019-06-18 04:17:25 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1724749,2019-04-18 07:03:43 UTC,"Hello,
do you still have this issue with the latest HWE kernel (4.15)?
Thanks"
1724752,2017-11-07 12:22:24 UTC,I've filed a bug at https://bugzilla.kernel.org/show_bug.cgi?id=197799
1724752,2017-11-07 08:39:56 UTC,The model is already in patch_realtek.c's quirk table:
1724752,2017-11-04 17:45:56 UTC,I've also tested it on Arch Linux but it doesn't work too. Maybe this is related to my laptop BIOS?
1724752,2017-11-03 11:32:17 UTC,I've tested this problem on the v4.14 kernel.
1724752,2017-10-20 16:19:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1724752,2017-10-19 06:55:10 UTC,I can also confirm that it affects Linux Kernel 4.10.0-37.41~16.04.1.
1724752,2017-10-19 06:33:31 UTC,apport information
1724752,2017-10-19 06:33:28 UTC,apport information
1724752,2017-10-19 06:33:27 UTC,apport information
1724752,2017-10-19 06:33:26 UTC,apport information
1724752,2017-10-19 06:33:24 UTC,apport information
1724752,2017-10-19 06:33:30 UTC,apport information
1724752,2017-10-19 06:33:20 UTC,apport information
1724752,2017-10-19 06:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1724752,2017-10-19 06:33:09 UTC,apport information
1724752,2017-10-19 06:33:11 UTC,apport information
1724752,2017-10-19 06:33:12 UTC,apport information
1724752,2017-10-19 06:33:14 UTC,apport information
1724752,2017-10-19 06:33:23 UTC,apport information
1724752,2017-10-19 06:33:16 UTC,apport information
1724752,2017-10-19 06:33:15 UTC,apport information
1724752,2017-10-19 06:33:17 UTC,apport information
1724752,2017-10-19 06:33:19 UTC,apport information
1724767,2017-10-19 08:09:31 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1724788,2020-02-21 12:08:58 UTC,This should now only be a problem with --destructive-mode when using 3.x.
1724790,2017-10-19 09:58:02 UTC,See IRC freenode #x2go on 2017/09/19
1724790,2017-10-19 10:06:41 UTC,"The problem lies within libxcomp3, which uses the environment variables NX_TEMP and TEMP to determine the temporary files directory (with a fallback to /tmp) and then tries to connect to $DETERMINED_TMP_DIR/.X11-unix/X$DISPLAY."
1724796,2017-11-17 16:33:03 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1724796,2017-11-16 06:49:02 UTC,"How would that help?
Card is working properly with OS drivers when they are loaded by Xorg DM or Xorg DE. Problem is only present during boot or if drivers are not loaded via Xorg (e.g. DM and DE are Wayland), and after Xorg loads drivers then Wayland also functions properly."
1724796,2017-11-16 04:30:52 UTC,RX580 is quite new. The easiest way to make your card work is to use AMDGPU-PRO.
1724796,2017-11-14 21:01:00 UTC,"Issue is present on 4.14.0-041400-generic kernel.
Issue was present since fresh install of Ubuntu 17.04 (don't remember what kernel version was it). Current Ubuntu version 17.10 is upgrade from 17.04."
1724796,2017-11-14 20:49:58 UTC,"Also, did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?"
1724796,2017-11-10 10:51:35 UTC,has little to do with libdrm
1724796,2017-11-13 07:13:22 UTC,"I turned on external PPA because it wasn't working. The problem is simple, image is broken until Xorg is loaded (either by choosing Xorg in GDM, or disabling Wayland for GDM). Xorg does something that fixes the picture in Wayland (and thus in GDM if GDM is running with Wayland enabled).
Some users on irc suggested that this is kernel bug, but I'm not familiar enough with how things work to confirm/test that. I just know that loading Xorg (either as session or GDM) fixes the problem for both sessions."
1724796,2017-11-10 11:00:12 UTC,This change was made by a bot.
1724796,2017-11-05 15:03:12 UTC,"I think I figured out what's happening. Kernel currently has bug for my card (rx580, or so I was told on IRC), but I have installed locally drivers which are loaded automatically on Xorg session (Drivers are from http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu). My question is is there a way to load those drivers via CMD line so I can do that before GDM or before loging into Wayland (currently I first have to login into Xorg in order for Wayland to work)."
1724796,2017-11-14 20:49:35 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1724804,2017-10-28 15:10:57 UTC,"I reproduced the duplicated ""Set marker color"" issue myself last week."
1724804,2017-10-24 21:14:00 UTC,See attached the screenshot of undo history.
1724804,2017-10-24 21:13:04 UTC,"Ok, so I dug into this deeper. Apparently, with the automatic marker coloring feature, some sort if bug has been introduced which affects arrows in transforms. I am attaching a screenshot of ridiculously long Undo history containing 58 consecutive ""Set marker color"" actions and another problematic image."
1724804,2017-10-19 12:07:30 UTC,"problem not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)."
1724811,2017-10-19 14:34:27 UTC,"The workaround for this issue is to change log-error directive in MySQL's configuration to other directory (for example, MySQL's data directory) or create an empty file with correct owner and group."
1724811,2018-01-18 08:25:22 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1131
1724820,2017-10-23 09:23:22 UTC,"Apparently the issue is no longer present in raspbian stretch, where mounting works as expected."
1724823,2017-10-19 13:04:47 UTC,I try to scan a document which includes 2 and more sheets - I get every sheet as one PDF document.
1724823,2017-10-19 17:36:38 UTC,"Have you checked your scanner with another computer?
First eliminate the obvious, because every error you see may not be a bug. My scanner works fine, and I'm using Linux Mint 18.2 it could be something else."
1724823,2017-10-19 18:19:00 UTC,Hi Joseph
1724837,2017-10-30 21:51:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724853,2017-10-19 14:52:31 UTC,"One report only so far, setting to low"
1724853,2017-10-19 14:48:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724853,2017-10-19 14:51:52 UTC,"the log has warnings
""failed to call gs_plugin_refine on packagekit-refine: failed to resolve package_ids: Operation was cancelled"""
1724854,2019-04-08 09:51:30 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/511473
Reason: Very old"
1724863,2017-11-15 00:46:01 UTC,This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-0ubuntu1~1.2
1724863,2018-07-05 02:43:07 UTC,I had this problem WITH the package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2. But found the solution here: https://elementaryos.stackexchange.com/questions/15842/bcm43142-and-linux-kernel-4-15-0-24-generic
1724863,2018-02-01 00:36:33 UTC,I tested with the kernel 4.13.0-32 and It works!!!!
1724863,2018-01-12 21:49:02 UTC,I tried to install the latest bcmwl-kernel-source and got the following ...
1724863,2017-11-15 00:46:07 UTC,"The verification of the Stable Release Update for bcmwl has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1724863,2017-11-02 23:48:43 UTC,"Hello Seth, or anyone else affected,"
1724863,2017-11-03 09:09:34 UTC,"I've tested it with kernel 4.11.0-14-generic and 4.13.0-16-generic, and it works for both: It compiles and after booting that kernel, Wifi works."
1724863,2017-10-30 16:53:44 UTC,"Actually, there are two bugs here:
 * Build for 4.11 fails, see bug 1713638 (patch included there).
 * Build for 4.13 fails: I can confirm that, but a different patch is needed. I personally can't run this kernel yet because of that bug."
1724863,2017-10-30 16:32:58 UTC,"This has already been reported months ago, see bug 1713638."
1724863,2017-10-29 12:06:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724863,2017-10-29 12:05:43 UTC,"you can now use wifi you need to enter in console commands
sudo modprobe -r b43
sudo modprobe b43"
1724863,2017-10-27 09:57:44 UTC,SRU template please.
1724863,2017-10-26 12:43:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724865,2018-01-18 18:10:30 UTC,"The verification of the Stable Release Update for broadcom-sta has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1724865,2018-01-18 18:10:26 UTC,This bug was fixed in the package broadcom-sta - 6.30.223.271-3~16.04.2
1724865,2018-01-18 12:32:45 UTC,Adding more details. I also have run the ADT tests for the following kernels to ensure there's no regressions:
1724865,2018-01-18 12:13:42 UTC,*ADT tests are passing for version 6.30.223.271-3~16.04.2 with kernel 4.13.
1724865,2017-11-30 18:03:00 UTC,This needs verification details.
1724865,2017-11-09 23:05:28 UTC,"Hello Seth, or anyone else affected,"
1724865,2017-11-02 23:38:44 UTC,"An upload of broadcom-sta to xenial-proposed has been rejected from the upload queue for the following reason: ""Where did 6.30.223.271-3~16.04.2 go?""."
1724865,2018-01-18 11:09:36 UTC,ADT tests are passing version 6.30.223.271-3~16.04.2 with kernel 4.13.
1724872,2017-12-04 12:13:06 UTC,"Hello Seth, or anyone else affected,"
1724872,2018-01-22 10:50:45 UTC,This bug was fixed in the package nvidia-graphics-drivers-340 - 340.104-0ubuntu0.16.04.1
1724872,2018-01-22 10:50:48 UTC,"The verification of the Stable Release Update for nvidia-graphics-drivers-340 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1724872,2018-01-18 12:45:56 UTC,"I have tested the version 340.104-0ubuntu0.16.04.1 and the DKMS package successfully builds and loads on kernels 4.13, which was the issue reported in this bug."
1724874,2018-02-13 12:45:59 UTC,"Hello Seth, or anyone else affected,"
1724874,2018-06-15 08:06:24 UTC,The version of rtl8812au in the proposed pocket of Xenial that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1724874,2018-05-22 20:41:26 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for xenial for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1724874,2017-12-19 23:56:16 UTC,I'd like to re-iterate that we appreciate your efforts in enabling this package for HWE users. I've rejected the upload to xenial-proposed only so that members of the SRU team don't need to continually re-check this bug.
1724874,2017-12-06 12:50:28 UTC,"> Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version.
"
1724874,2017-12-19 23:52:36 UTC,"An upload of rtl8812au to xenial-proposed has been rejected from the upload queue for the following reason: ""Please respond to the questions in comment #2""."
1724876,2019-10-27 00:29:06 UTC,Possibly related/maybe a duplicate of: https://bugs.documentfoundation.org/show_bug.cgi?id=127842
1724876,2019-09-28 21:12:54 UTC,Note: I'm running Ubuntu 18.04 with this LibreOffice:
1724876,2019-09-28 21:27:42 UTC,"FYI these are the tweaks I've made to my Ubuntu 18 installation, in case any of them triggered or shed light on the LibreOffice issue: https://electricrcaircraftguy.github.io/20190919-post_ubuntu_18_todos.html."
1724876,2019-09-28 21:36:47 UTC,Here's another screenshot showing the *massive* difference in total CPU load that I made simply by calling `pkill soffice.bin`!
1724876,2019-09-30 09:14:28 UTC,We had a similar report about high CPU usage that turned out to be a troublesome extension rather than LibreOffice itself:
1724876,2019-10-27 00:17:04 UTC,"Description:
I recently installed Ubuntu 18.04 onto a laptop and immediately put LibreOffice 6.3.1 onto it. I've had problems ever since!"
1724876,2019-10-27 00:26:27 UTC,Related (appears to be the *exact* same problem as mine!): https://ask.libreoffice.org/en/question/208712/calc-6312-macro-button-problem/
1724876,2019-10-27 00:40:06 UTC,"Marcus, here's all the extensions I have installed."
1724876,2019-09-28 21:08:00 UTC,"Exact same as TLRobb notes just above:
100% usage of one cpu core for an extended period (hours?)--no idea what it's doing, but on a slow computer with few cores it's really rendering my computer nearly unusable just to have LibreOffice open in the background with a document minimized while I do something else on the computer."
1724876,2019-10-27 00:44:45 UTC,Possibly also related--or maybe a different bug altogether? https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876
1724876,2019-10-27 07:20:08 UTC,"There are 2 described pbs in your bug:
- slowliness
- flashing buttons (indeed tdf#121963)
We must focus on 1 pb only. (1 bugtracker => 1 problem or 1 group of very related problems)
Considering the number of duplicates about flashing buttons, I propose you we focus on 1."
1724876,2019-11-06 11:10:20 UTC,"It might be a dup of tdf#121963 which has just been fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=e8720057aa0f4e612000d68f6de682f3afb8a1ea
It should be present in daily build in 24/48h, to retest."
1724876,2019-11-06 11:11:39 UTC,"Thank you for reporting the bug.
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version."
1724876,2020-07-05 03:39:23 UTC,"Dear Gabriel Staples,"
1724876,2019-12-06 13:25:39 UTC,"(In reply to Bruce Sobey from comment #8)

> Created attachment 155789 [details]
> File to Demonstrate problem with Basic Macro to Solve to target
"
1724876,2020-06-04 03:44:27 UTC,"Dear Gabriel Staples,"
1724876,2019-10-27 00:43:57 UTC,"Also, here was my work-around to try to fix the 100% cpu soffice.bin bug: https://serverfault.com/questions/953809/soffice-bin-high-cpu-usage/986039#986039."
1724876,2019-03-22 20:03:29 UTC,"I have noted the same symptoms for months; i.e. 100% usage of one cpu core with any document opened in LibreOffice for an extended period. Simple 10kB text file in Writer or large spreadsheet in Calc.
Ubuntu 18.04.2 LTS, LibreOffice 6.0.7.3 00m0(Build:3). This behavour has not improved with any main line updates from Ubuntu."
1724876,2019-11-13 15:21:25 UTC,"Created attachment 155789
File to Demonstrate problem with Basic Macro to Solve to target"
1724876,2019-02-14 08:52:54 UTC,"wil not confirm that closing and reopening the document helps. That does
not have any effect in my case."
1724876,2019-03-06 14:55:17 UTC,"This bug continues to affect me: ubuntu 18.04 LTS, LO Version: 6.0.7.3  Build ID: 1:6.0.7-0ubuntu0.18.04.2"
1724876,2018-01-03 18:36:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724876,2018-03-18 13:59:23 UTC,"FWIW, I had a few documents open, but none being actively edited.  One very long (about 300k words).
I closed several of them (including the very long one).
One that had changes needing saving, I simply saved.
CPU load dropped to almost nothing.
Sorry I didn't think to check load before saving, and after closing the long one.
In the past I've found that closing LO and reopening files also fixes the issue."
1724876,2018-03-19 10:17:07 UTC,"@Floris: please excuse the lack of feedback on that bug. Are you still affected by the issue, or did it somehow resolve itself?"
1724876,2018-03-19 10:20:56 UTC,"I can add a few notes, as it's happened a few times since I wrote the above.
On each occasion, I've had:
- several documents open in Writer
- one is moderately large (93k words)
- at least one has changes needing to be saved."
1724876,2018-03-19 10:33:47 UTC,"But some more googling indicates this is a known bug in glib2 that the developers were very actively working from Jan-Feb 2018, but maybe not finalised by Mar 2018.
https://bugzilla.gnome.org/show_bug.cgi?id=761102#c53"
1724876,2018-03-19 10:42:28 UTC,Hi Olivier
1724876,2018-03-19 10:43:58 UTC,"Hi Luke,"
1724876,2019-11-05 08:59:15 UTC,"Bug still living in V6.4.0.0alpha1 with documents created with older version.
(As also in 6.3: Other control type also affected even if not having a macro assigned.)
Not yet observed in a few very simple examples freshly created with 6.4 alpha."
1724876,2018-10-19 17:58:12 UTC,Found another non-working tip:
1724876,2019-01-02 20:49:19 UTC,Focus or no focus didn't have any effect in my case
1724876,2019-01-02 20:31:12 UTC,It seems LibreOffice is more likely to use high CPU when its windows are in the background.  Bringing one to the foreground reduced CPU usage.
1724876,2018-12-28 10:10:16 UTC,"Also affects LibreOffice 6.0.7.3 on 18.04.  In the occurrence I saw, the user had used and closed Calc but had left one Writer document open.  All documents visited were made by the user and had no macros, but in case it's relevant I should perhaps mention we have Java disabled as a workaround for bug #1702165."
1724876,2019-02-12 10:10:55 UTC,Affects me often with LibreOffice 6.0.7.3 on Ubuntu 18.04 (Build ID: 1:6.0.7-0ubuntu0.18.04.2). Only help is to shut it down and reopen the document I am working on. Very annoying.
1724876,2018-11-16 19:26:08 UTC,"If this really is an upstream bug in glib (https://gitlab.gnome.org/GNOME/glib/issues/1128) then it looks like no, this isn't being actively worked on."
1724876,2018-03-19 10:45:04 UTC,"Thanks havent googled the bug for months anymore so good to know some are
finally actively working on it!"
1724876,2018-10-19 17:58:38 UTC,Is any developer actively working on this?
1724876,2018-12-10 15:17:45 UTC,"Hello. Affected also by the same 100% CPU soffice.bin with a document containing only one page of text with no image at all, whatever I close or not other applications or software."
1724881,2017-10-26 15:16:17 UTC,"Apparently, it's related to this bug:
https://bugs.launchpad.net/elementaryos/+bug/1638968"
1724881,2018-07-08 08:47:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724881,2020-04-15 19:44:54 UTC,Any news?
1724886,2017-10-19 16:02:17 UTC,"StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x7f6d70c7e6b0 ""list_empty(&device->event_listeners)"", file=file@entry=0x7f6d70c7e56d ""libinput.c"", line=line@entry=2157, function=function@entry=0x7f6d70c7ee30 <__PRETTY_FUNCTION__.10201> ""libinput_device_destroy"") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f6d70c7e6b0 ""list_empty(&device->event_listeners)"", file=file@entry=0x7f6d70c7e56d ""libinput.c"", line=line@entry=2157, function=function@entry=0x7f6d70c7ee30 <__PRETTY_FUNCTION__.10201> ""libinput_device_destroy"") at assert.c:101
 libinput_device_destroy (device=0x55dc6bdcedd0) at libinput.c:2157
 libinput_device_unref (device=<optimized out>) at libinput.c:2167
 clutter_input_device_evdev_finalize (object=0x55dc6be15910) at evdev/clutter-input-device-evdev.c:66"
1724886,2020-01-24 10:02:44 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1724892,2020-07-03 05:02:24 UTC,DistroRelease: Kali 2017.2
1724895,2018-12-10 16:47:05 UTC,That is a different issue we're solving elsewhere. You should be able to override the UseMTU= field.
1724895,2018-12-10 16:48:53 UTC,"Clearing up bug statuses: We'll fix this for 18.04 and above, but first it needs to land in the development release. Won't Fix is for the releases before 18.04."
1724895,2018-12-10 16:52:36 UTC,Please see if this is solved by the fix for https://bugs.launchpad.net/netplan/+bug/1807273 (setting use-mtu: false)
1724895,2019-01-15 18:04:52 UTC,Marking this invalid for cloud-init per netplan symptoms 'fixed' in https://bugs.launchpad.net/netplan/+bug/1807273 look like it might be the same case here with no change to cloud-init
1724895,2019-03-28 08:08:23 UTC,"Can we have a status on this? I can also confirm that the suggested workaorund works, but this should be fixed anyhow, right?"
1724895,2019-10-03 09:56:08 UTC,Still broken on 18.04.03 (netplan 0.97).
1724895,2019-12-10 21:37:14 UTC,Any updates for bionic? We would strongly need this fixed.
1724895,2018-12-05 18:46:59 UTC,"I'm having a similar issue where setting the MTU to 1500 and using a match on mac address does not stick. This is on a EC2 T2.Medium instance. Actual configuration from a dev server:
network:
  version: 2
  ethernets:
    eth0:
      match:
        macaddress: 12:0f:ae:49:5d:06
      mtu: 1500
      dhcp4: true
      nameservers:
        search: [ devbuilds.vpc, ec2.internal ]"
1724895,2020-04-10 00:35:32 UTC,"Why does this bug title refer to ""private"" ethernet adapters?  It sounds like you're saying the problem is much more general than this."
1724895,2020-04-03 15:02:28 UTC,"@cyphermox Need to confirm this on focal daily ... we still need a ""match: macaddress"" for setting MTU.
This is really a show stopper when cloning servers with virtualization and containerization an new MAC.
Working with VLANs this is an essential setting for getting networking before config mgmt can template."
1724895,2020-04-09 06:32:12 UTC,Still broken in 20.04 beta. This is a real shame…
1724895,2020-04-09 07:26:22 UTC,What prevent the generator to use Match/Name instead of Match/OriginalName by default in .link file like it does for generated .network files ?
1724895,2019-10-23 10:34:41 UTC,Still broken on 18.04.3 with netplan 0.98-0ubuntu1~18.04.1 and systemd 237-3ubuntu10.31.
1724895,2018-10-16 22:53:29 UTC,"Logs were added for cloud-init, so marking the cloud-init task back to 'new'."
1724895,2020-11-13 16:29:23 UTC,Doing some experiments this seems to be working with netplan.io 0.100 in Groovy. No matter if 'match.macaddress' is set or not on my local eth interface.
1724895,2018-07-02 14:09:22 UTC,I have the same here.
1724895,2018-10-07 19:25:11 UTC,I just got bit by this one too.
1724895,2017-10-23 13:44:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724895,2018-01-30 13:44:08 UTC,Still happening on 0.32~17.10.1
1724895,2018-01-30 13:56:44 UTC,So the only thing I see in the logs that looks suspicious is:
1724895,2018-04-25 17:56:04 UTC,"Confirmed that this is still an issue in bionic (beta 2, all packages updated), 0.36.1."
1724895,2018-05-04 16:16:38 UTC,Apparently this was not fixed for Ubuntu 18.04 release?
1724895,2018-05-04 16:44:46 UTC,"It should work if you match by MAC address. It's a messy interaction with
udev, as I understand it. Could you try matching by MAC and seeing if that
works?"
1724895,2020-03-29 04:59:52 UTC,This bug is also affecting 20.04
1724895,2018-05-05 01:50:00 UTC,"Glad that helped. I'm confused as to why cloud-init doesn't add the mac
addresses - it does in my VMs. Let's ask them; I'll add them to the bug."
1724895,2018-05-08 16:56:47 UTC,Can you run cloud-init collect-logs in your instance and attach the tarfile (cloud-init.tar.gz in the current working directory).
1724895,2018-05-09 15:20:15 UTC,Adding requested file.
1724895,2018-05-09 23:16:28 UTC,Matching by MAC address corrects the MTU issue on both Ubuntu 17.10 and Ubuntu 18.04.
1724895,2018-05-10 00:41:36 UTC,"Hi Andy,"
1724895,2018-05-04 17:10:42 UTC,"Yup, adding a match on MAC seems to work.  It would be nice if whatever sets up the default /etc/netplan/50-cloud-init.yaml included the match on MAC?"
1724895,2018-05-10 16:34:31 UTC,"Hi Daniel,"
1724901,2018-11-07 03:16:28 UTC,"This bug reports says ""Launching 17.10"" so I guess its present in ubuntu 17.10 but my system is Ubuntu 16.04.5 and I have the same problem."
1724901,2019-07-29 08:36:01 UTC,"In #1838192 I reported observing a crash with linux-image-4.15.0-55-generic on a 16.04 LTS machine.
However the server does not crash with linux-image-4.15.0-47-generic or linux-image-4.4.0-154-generic."
1724901,2017-10-19 17:12:16 UTC,"StacktraceTop:
 RRProviderAutoConfigGpuScreen (pScreen=0x55bf0f9c6270, masterScreen=0x55bf100d7c30) at ../../../../randr/rrprovider.c:495
 xf86AutoConfigOutputDevices () at ../../../../../../hw/xfree86/common/xf86Init.c:310
 InitOutput (pScreenInfo=pScreenInfo@entry=0x55bf0e892800 <screenInfo>, argc=argc@entry=12, argv=argv@entry=0x7ffd8d73d578) at ../../../../../../hw/xfree86/common/xf86Init.c:910
 dix_main (argc=12, argv=0x7ffd8d73d578, envp=<optimized out>) at ../../../../dix/main.c:197
 __libc_start_main (main=0x55bf0e466af0 <main>, argc=12, argv=0x7ffd8d73d578, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd8d73d568) at ../csu/libc-start.c:308"
1724901,2017-10-21 11:11:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724910,2017-10-19 17:53:51 UTC,"StacktraceTop:
 _cogl_pipeline_get_authority (difference=4, pipeline=0x0) at ./cogl-pipeline-private.h:605
 cogl_pipeline_foreach_layer (pipeline=0x0, callback=callback@entry=0x7f9b72c4f9a0 <layer_cb>, user_data=user_data@entry=0x7ffea5e6b050) at cogl-pipeline.c:715
 get_first_layer_index (layer_index=<synthetic pointer>, pipeline=<optimized out>) at deprecated/clutter-texture.c:1396
 clutter_texture_get_cogl_texture (texture=<optimized out>) at deprecated/clutter-texture.c:1438
 _st_create_shadow_pipeline_from_actor (shadow_spec=0x559f0292e6c0, actor=0x559f02abeaf0) at ../src/st/st-private.c:430"
1724910,2020-01-24 10:02:58 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1724923,2017-11-06 17:57:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724923,2017-11-06 17:58:34 UTC,"Also experiencing the same issue, sometimes when they show up it's in the Bluetooth section."
1724927,2017-10-19 19:09:47 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x5559c0fbb307 ""Gvc"", file=file@entry=0x5559c0fbf748 ""gvc-mixer-card.c"", line=line@entry=168, func=func@entry=0x5559c0fbfa90 <__func__.27165> ""gvc_mixer_card_get_profile"", message=message@entry=0x5559c30f8960 ""code should not be reached"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x5559c0fbb307 ""Gvc"", file=file@entry=0x5559c0fbf748 ""gvc-mixer-card.c"", line=line@entry=168, func=func@entry=0x5559c0fbfa90 <__func__.27165> ""gvc_mixer_card_get_profile"", expr=expr@entry=0x0) at ../../../../glib/gtestutils.c:2459
 gvc_mixer_card_get_profile (card=0x5559c3afadb0) at gvc-mixer-card.c:168
 gvc_mixer_control_change_profile_on_selected_device (control=0x5559c2e032a0, device=0x5559c37fd1a0, profile=profile@entry=0x0) at gvc-mixer-control.c:540
 gvc_mixer_control_change_output (control=<optimized out>, output=<optimized out>) at gvc-mixer-control.c:597"
1724944,2018-04-10 04:48:06 UTC,"And the 2nd point is also an ""user"" problem."
1724944,2018-10-12 20:21:32 UTC,I am closing this bug. I believe the problem was that you didn't uncomment the [org/gnome/login-screen] line.
1724944,2018-10-12 20:37:05 UTC,"Ok, I'm reopening this because the default could be better. I have filed a Debian bug for input."
1724944,2018-04-09 20:52:27 UTC,"BTW: as Joris Le Blansch wrote, using dconf-editor GUI to set /org/gnome/login-screen/disable-user-list to ON has no effect and after reboot userlist is shown as before."
1724944,2018-10-12 18:58:24 UTC,this is happaning also in Ubuntu 18.04 - once user list is disbaled gdm3 (sudo systemctl restart gdm3) crashes
1724944,2018-04-09 16:23:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1724944,2018-04-09 07:54:19 UTC,Affects 18.04 as well.
1724944,2017-11-27 09:04:00 UTC,"In addition, using dconf-editor for changing this setting does not work, too."
1724944,2017-11-24 10:34:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724944,2018-04-09 19:59:27 UTC,I managed to get some journalctl entries related with the gdm starting error:
1724950,2017-11-09 09:24:40 UTC,We created a plugin for Moodle: https://moodle.org/plugins/tool_crawler Something to adapt?
1724950,2017-11-09 18:19:54 UTC,From what I can tell about the moodle tool_crawler plugin it goes and finds broken links and then alerts the admin/course admin about them.
1724950,2017-11-12 06:14:34 UTC,Links can be put into forums in Moodle by students. So it's not fully just admins.
1724965,2020-08-05 20:21:31 UTC,Removed pullrequest after discussing with Tiffany
1724965,2020-02-19 20:54:32 UTC,"Can confirm Elaine's comment:
Loan duration and Fine level displaying # code instead of text
Alert message doesn't display"
1724965,2020-02-19 20:21:40 UTC,I will check this again. THe fix may not have been on the sandbox.
1724965,2020-02-19 18:39:46 UTC,Testing https://tiffany-master.gapines.org/eg/staff/
1724965,2019-10-22 20:40:32 UTC,"Scrapped almost wholesale what I had before, since there's been a subsequent fix for the duplicating columns issue with having an autofield and a defined field show the same thing."
1724965,2019-03-08 17:23:52 UTC,Thanks Derek! Removing the pullrequest tag to keep working on it.
1724965,2019-03-07 14:59:40 UTC,"While the TCN (value and label) have been added to the 'Bucket View' tab, the current patch only addresses the 'Bucket View' tab of the item buckets interface."
1724965,2019-01-23 19:46:12 UTC,That makes sense to me.  Thanks for explaining.
1724965,2019-01-23 14:43:07 UTC,(Caveat: Please tell me if I've misunderstood anything.)
1724965,2019-01-23 14:13:14 UTC,Nice work Tiffany!  Overall it looks good to me.  Just one question: Could you explain why you removed the auto-fields setting?
1724965,2019-01-22 16:53:22 UTC,I have a patch here that returns many of the columns that were in XUL. It also puts the options in alphabetical order.
1724965,2018-11-15 20:21:54 UTC,"I think you're right, Andrea. I won't include that one since Record ID is already present. Thanks!"
1724965,2018-11-15 14:28:33 UTC,"IIRC, Document ID = Bib ID (or at least it did in my old system) but it's been a while since I've looked at XUL."
1724965,2018-05-16 20:11:32 UTC,"Another field we need in the copy bucket column picker is checkout date, it's available in the staff client."
1724965,2018-02-23 14:03:08 UTC,Received request to have Author on Column picker from library staff - I know previous comment indicated several columns missing but wanted to ensure Author was included in that list!
1724965,2018-01-04 19:59:31 UTC,"When comparing to the legacy staff client there are several fields missing from the column options. Also, it appears that the title is shown in lower case making label printing with title not what is desired."
1724965,2017-11-15 12:33:16 UTC,Due Date is also missing as a column selection.
1724965,2018-11-15 13:58:19 UTC,"While working on this, I wrote down all the available columns in XUL. There are a couple that I wonder what they are--I've never used them. Does anyone have any input on these?"
1724969,2019-07-13 21:14:14 UTC,"17.10 is long since unsupported and Lubuntu isn't even using Ubiquity anymore (well, except for 18.04, which is not supported for much longer)."
1724969,2019-07-13 23:57:44 UTC,"Thank you for taking the time to report this issue and helping to make Ubuntu better. This however is not a bug, as the issue is you are trying to install a release that is past EOL in a condition where it is needs to get extra packages (apt-install) but those packages are no longer available [where expected] due to EOL status."
1724971,2019-05-25 02:49:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724971,2017-10-19 20:47:51 UTC,"StacktraceTop:
 g_str_hash (v=0x0) at ../../../../glib/ghash.c:1882
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x7fac6843b6a0) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x7fac6843b6a0, key=key@entry=0x0) at ../../../../glib/ghash.c:1153
 osinfo_datamap_lookup (map=map@entry=0x7fac694fef90, inval=inval@entry=0x0) at osinfo_datamap.c:114
 language_code_from_raw (raw_lang=<optimized out>, lang_map=0x7fac694fef90) at osinfo_db.c:76"
1724973,2019-09-19 12:05:06 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1724973,2017-10-23 13:33:44 UTC,This really isn't an issue with the API. We provide a RESTAPI which should use unique ID's to reference objects.
1724977,2017-10-19 21:11:36 UTC,I have attached a copy of a monitor.xml file I can use that will yield this behavior.
1724977,2018-01-11 13:16:22 UTC,"Upgraded from 17.04 to 17.10, and now I am experiencing this. 3 screens, duplicate appears on the rotated second screen."
1724977,2018-01-17 11:44:04 UTC,"Happens also in Ubuntu 17.10.
Screen setup is similar to the original bug report."
1724977,2018-01-24 18:40:30 UTC,Still a problem in 18.04.
1724977,2018-01-24 18:43:28 UTC,I have this problem on Ubuntu 18.04 with Intel integrated graphics (on a Thinkpad T460s).
1724977,2018-01-31 06:39:45 UTC,"I currently have this problem after a system upgrade from 26 to 27.
I have a triple monitor setup, with the leftmost monitor set to ""portrait right"" (like most people commenting)"
1724977,2018-01-31 16:52:51 UTC,"Thanks, Evan, for the new data. Hopefully that will help narrow down the issue."
1724977,2018-02-06 01:01:56 UTC,"As a temporary workaround, selecting ""GNOME on Xorg"" at login does work with F27 and the same gnome-shell version."
1724977,2018-02-14 05:19:58 UTC,"I'm having this bug too on Debian Testing, a GTX 1080, and the proprietary drivers."
1724977,2018-02-14 07:01:59 UTC,"(In reply to Weston Reed from comment #7)

> I'm having this bug too on Debian Testing, a GTX 1080, and the proprietary
> drivers.
"
1724977,2018-02-19 01:19:28 UTC,"I am also affected by this 'feature'. I have 3 1920x1200 displays and primarily use my i7-6700hq's integrated graphics. I also have a discrete 960m; however, I don't believe it's in use. I am running Fedora 27 with Gnome 3.26.2."
1724977,2018-02-19 09:07:21 UTC,I'm also affected:
1724977,2018-01-03 15:09:41 UTC,"same problem here, 2 screens, left one set to ""Portrait right"", right one ""landscape""."
1724977,2018-03-02 02:51:41 UTC,I am also having this issue.
1724977,2018-03-12 16:46:00 UTC,I just did a dnf update and i still see the duplicate cursor when moving on the top left part of my screen.
1724977,2018-03-20 12:58:51 UTC,"Just FYI if it can help you guys in any way (I do know this is an Ubuntu forum), I'm adding a confirmation that this is not Ubuntu specific. I've also reproduced it in Fedora 27 under Wayland with 3 monitors: left horizontal, middle vertical (rotated right), right horizontal. There's algo an open bug in Fedora Bugzilla: see RedHat bug: https://bugzilla.redhat.com/show_bug.cgi?id=1513160."
1724977,2018-03-20 13:08:14 UTC,"Same here under Wayland with 3 monitors: left horizontal, middle vertical (physically rotated right, image rotated left), right horizontal. Attaching image that shows screen configuration: primary screen #3, which is the most left one (ordered 312 from left to right)."
1724977,2018-03-20 13:13:08 UTC,"Created attachment 1410471
Screen configuration with 3 monitors 3-horiz 1-vert 2-horiz"
1724977,2018-03-30 06:31:11 UTC,"This bug has moved to: https://gitlab.gnome.org/GNOME/mutter/issues/85
where it is now fixed."
1724977,2018-03-30 06:33:37 UTC,"Fix landed upstream ready for mutter release 3.28.1:
https://gitlab.gnome.org/GNOME/mutter/commit/8696a794"
1724977,2018-03-30 07:38:23 UTC,Fixed with MR!59
1724977,2018-04-07 15:15:08 UTC,Is the fix for this bug going to make it to 18.04 release?
1724977,2018-04-09 02:09:05 UTC,"Not sure. Maybe keep an eye on the version numbers in:
https://launchpad.net/ubuntu/+source/mutter"
1724977,2018-04-19 01:22:28 UTC,mutter (3.28.1-1) unstable; urgency=medium
1724977,2018-04-19 01:23:47 UTC,3.28.1 is now in Ubuntu 18.04 so this bug *should* be fixed.
1724977,2018-03-12 10:01:17 UTC,"since the last dnf update i'm back to one cursor, this is works-for-me."
1724977,2017-12-30 11:09:04 UTC,*** Bug 791888 has been marked as a duplicate of this bug. ***
1724977,2018-03-13 13:12:22 UTC,"This happens also on a ThinkPad T530 with Fedora 27, both with either the discrete (NVIDIA) or integrated (Intel) GPU enabled, but not with OPTIMUS."
1724977,2017-12-13 07:43:43 UTC,Happens on Fedora 27 as well. The problem appeared after the upgrade and was not present on Fedora 26 with GNOME 3.24.
1724977,2017-10-19 21:14:38 UTC,I have attached a photo of my screen showing this behavior.
1724977,2017-10-19 21:16:11 UTC,"Oops, I attached the wrong picture.  This one is correct."
1724977,2017-10-22 22:47:18 UTC,It could be related to this bug:
1724977,2017-10-23 13:47:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1724977,2017-10-23 17:54:08 UTC,"+1
I've just upgraded ubuntu to 17.10 and got this bug =(
I have 3 monitors (1 laptop and two 2560x1440 monitors)
first is the laptop screen, second is rotated vertically screen and next one is not rotated normal screen. when I move cursor on third screen I can see rotated reflection of cursor on second (rotated) screen. It really annoys me, because I cann't work now. =("
1724977,2017-10-23 17:54:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724977,2017-10-30 16:03:39 UTC,Could somebody having the issue open an upstream report?
1724977,2017-10-31 00:26:27 UTC,"I have a 3 screen setup on a notebook with intel graphics. The left one is in portrait view, the center one is in normal view and right is in normal view (buildin), mostly turned off.
When the mouse is in left side of the center monitor it shows also on the left monitor bottom."
1724977,2017-10-31 00:28:33 UTC,Done: https://bugzilla.gnome.org/show_bug.cgi?id=789675
1724977,2017-10-31 07:01:43 UTC,"I can confirm the exact same behaviour in my 2 monitor setup, one in portrait mode to the left and one in landscape to the right. I have just upgraded to 17.10 and, oddly enough, the problem only happens when the open source Nouveau driver is in use. If I switch to the proprietary nVidia driver, the second cursor does not appear, as expected."
1724977,2017-12-18 12:23:09 UTC,"I had the same issue after uprading from Ubuntu Gnome 17.04 to Ubuntu 17.10.
I ""fixed it"" by using Xorg instead of Wayland.
A colleague of me had the same issue in Arch Linux half a year ago. Always good to know someone who is living on the bleeding edge :D"
1724977,2017-10-31 12:56:01 UTC,"@Rafael, are you using the nouveau driver as well?"
1724977,2017-10-31 12:55:44 UTC,thanks for sending it upstream
1724977,2017-11-02 02:01:13 UTC,"I doubt this bug is driver-specific. A rotated screen might get ""software"" (GL) cursor rendering by default in Wayland sessions (I am guessing since we did the same in Mir). And the hardware cursor is used on non-rotated screens. The two should co-exist and only one display at a time, so that's no excuse, just a possible explanation."
1724977,2017-11-03 13:04:58 UTC,"Confirmed - rotated second screen causes duplicate cursor. Luckily the second one is un-rotated, so it is easy to know which is the ""real"" cursor."
1724977,2017-11-03 14:16:35 UTC,"Screenshot of the issue from one of the Ubuntu reports
https://launchpadlibrarian.net/343378172/two_mouse_cursors.jpg"
1724977,2017-11-08 21:40:53 UTC,I switched to KDE Plasma..
1724977,2017-11-14 20:36:35 UTC,Description of problem:
1724977,2017-11-14 22:18:24 UTC,"Created attachment 1352198
video demonstrating the issue"
1724977,2017-11-15 22:04:57 UTC,If I unplug one of the 2k monitors I can still reproduce if the remaining 2k monitor is in 'portrait left' but not 'landscape'. So the issue should be reproducible with two screens.
1724977,2017-11-24 11:51:28 UTC,I'm experiencing the same problem in gnome-shell 3.26.2-1 on Debian testing.
1724977,2017-11-29 22:33:06 UTC,"It also happens to me, I have two monitors and one is on 'Portrait right'.
Any hint on how to debug or provide more information?"
1724977,2017-11-29 23:03:17 UTC,Also happening here. Incidentally my third screen on the left is in portrait as well. Using the intel i915 driver and wayland
1724977,2017-12-01 15:09:52 UTC,"Same here with 3 screens on Wayland.
The second pointer appears on the monitor on the left which is set as portrait. All of the 3 screens are set to 1920x1080."
1724977,2017-11-01 20:27:25 UTC,My notebook is using the default Intel driver.
1724981,2017-10-25 00:44:23 UTC,"Yes, that's possible. Please contact our support team by phone or by creating a case through your system76 account and they'll get you taken care of."
1724981,2017-10-24 18:58:28 UTC,"The issue has shown up again after powering off and on the computer (without ever installing the patch). It is possible the cause is not related to CUDA and is an issue with the machine itself. It has 2 GPUs, in case that is relevant."
1724984,2017-10-22 14:55:00 UTC,"I've same problem, is very slow GDM."
1724991,2021-02-18 16:45:53 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1724999,2017-10-20 16:35:37 UTC,Thanks for reporting.
1724999,2017-10-20 18:49:43 UTC,"Ah, thanks for the pointer. I found a related bug in the Claws Mail bugtracker and added the link."
1724999,2017-11-07 12:33:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1724999,2018-01-23 19:10:23 UTC,"In case anyone stumbles upon this, here's a stub package which brings back the Fancy plugin:"
1725015,2017-10-19 23:06:40 UTC,"StacktraceTop:
 g_type_check_instance_cast (type_instance=0x55be5ef83ec0, iface_type=94275939770992) at ../../../../gobject/gtype.c:4057
 st_entry_get_text (entry=<optimized out>) at ../src/st/st-entry.c:1112
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x55be57348c78, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffd36c891a8, avalue=avalue@entry=0x7ffd36c890a0) at ../src/x86/ffi64.c:525
 gjs_invoke_c_function (context=context@entry=0x55be541ba800, function=function@entry=0x55be57348c60, obj=..., obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at gi/function.cpp:1033"
1725015,2020-01-24 10:03:12 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725017,2017-10-19 23:08:23 UTC,"StacktraceTop:
 g_action_map_lookup_action (action_map=0x55dd7ccb23e0, action_name=0x55dd7c76b0fc ""edit-paste"") at ../../../../gio/gactionmap.c:87
 fr_window_enable_action (window=0x55dd7ccb23e0, action_name=0x55dd7c76b0fc ""edit-paste"", enabled=0) at fr-window.c:691
 g_closure_invoke (closure=0x55dd7ce7be90, return_value=0x0, n_param_values=2, param_values=0x7ffeeda4afc0, invocation_hint=0x7ffeeda4af40) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55dd7cd32e80, detail=detail@entry=0, instance=instance@entry=0x55dd7cd645b0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffeeda4afc0) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x55dd7cd645b0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffeeda4b190) at ../../../../gobject/gsignal.c:3391"
1725017,2017-10-23 21:12:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725017,2017-10-24 11:11:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725017,2019-02-24 16:51:30 UTC,"Reported upstream on the Gnome projects' new 'bug tracker' (Gitlab) - for which no bug watch exists in Launchpad (to date):
https://gitlab.gnome.org/GNOME/file-roller/issues/31"
1725017,2019-02-25 09:46:47 UTC,Thanks!
1725055,2017-10-24 03:48:03 UTC,I tried to address the user issue part using the virtual machine version of Ubuntu 17.10. It is still the same.
1725055,2017-10-24 03:13:31 UTC,"If that could be the case, I updated the bug report to NetworkManager component of GNOME instead. https://bugzilla.gnome.org/show_bug.cgi?id=789341"
1725055,2017-10-23 12:00:53 UTC,The issue might not be in gnome-control-center but their interface could at least communicate what the error is or that there is an error to the user
1725055,2017-10-23 09:43:23 UTC,"I think this error report had a similar problem, the bug report said it is not GNOME problem: https://bugzilla.gnome.org/show_bug.cgi?id=773163"
1725055,2017-10-23 08:52:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725055,2017-10-23 09:44:10 UTC,"I think this error report had a similar problem, the bug report said it is not GNOME problem: https://bugzilla.gnome.org/show_bug.cgi?id=773163"
1725060,2017-10-25 19:29:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725062,2017-10-26 02:49:16 UTC,Anyone filed an upstream bug at https://bugzilla.gnome.org yet?
1725062,2018-01-31 02:43:37 UTC,"Jan 30
Hi to all I' new to ubuntu and linux and I dont know more than any of you guys
I just upgraded from 17.4 to 17.10 before yesterday and I had all kind of issues trying to make the
VPN to work using the Network Manager Applet and the orange on slider button won't stay on,reading all over I did found you guys, this is what I did to make it work
1- Right click on top of the 3 computers icon
2- Click the arrow next to the VPN to open the VPN settings
3- On the VPN click the + icon
4- on the identity tab Create the new connection adding the gateway
5- add the user name and the password and click the black icon on the right
   change it to use the password for all the users
6- Click advance uncheck the the 2 first and the last box
7- On security and compression I check all the box except for the last one use custom unit numbers
8-on the details tab and the others tab I left all the same it was
and turn the vpn settings on the router off,has bee on for more than an hour
IP address secure
No WebRTC leak detected
No DNS leaks detected
using express VPN
if you believe this have not cense, this is the way work for me,hope work for you
thanks"
1725062,2017-12-04 22:01:16 UTC,"update:
Storing the password for all users works only once."
1725062,2017-12-04 21:50:29 UTC,"Same problem here after upgrading.
The ""indicator"" thingie worked, as in, i can reconnect to my vpn again but now there's new behavior when I come back in the settings screen."
1725062,2017-11-23 22:53:57 UTC,I also cannot connect to a VPN:
1725062,2017-11-08 10:29:32 UTC,"> John, you need to click a black icon at the right corner on the second tab (identification in my language) right in the password field. I attached a screenshot.
"
1725062,2017-10-30 00:14:48 UTC,"heytimc, i blocked pptp connection on my router and got the same syslog errors.
So your problem is some kind of network issue. It could be your router firewall, or ISP firewall or maybe your IT department changed something or blocking it. I can only quess.
As a confirmation of my words - open gnome-terminal, type nmtui, choose connect and select your VPN connect - if will fail too, so it means it's a  network issue."
1725062,2017-10-29 23:47:59 UTC,@jingles still suffering from this; even with my firewall disabled:
1725062,2017-10-26 13:23:05 UTC,thanks for forwarding it upstream
1725062,2017-10-26 11:53:06 UTC,"Thank you for response, here is the link:
https://bugzilla.gnome.org/show_bug.cgi?id=789341"
1725062,2017-10-26 09:14:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725062,2017-10-26 01:33:10 UTC,"Tomas, I forgot to mention - workaround works for me only on saved connection. You need to create it first,save it and then choose 'save password for all users' option. If you change anything else after choosing 'save password..' option, the problem may be persist. Also i assume your problem is a little bit broader. If I right, and you need PPTP connection for RDP sessions - it won't work out of the box in Ubuntu. You need to upgrade remmina from ppa, and check 'send echo packets PPP' and check 'use these connection for these network resourses only'. Aslo i recommend to try to connect via 'nmtui' the way i mentioned above, if my workaround not working."
1725062,2018-01-31 22:21:39 UTC,"Still working but get disconnected when restart or go to sleep mode,and I able to connected back again from the icon on the top of the screen without do anything on the settings,this is a system issue no network issue"
1725062,2017-10-25 22:47:51 UTC,"The workaround https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725062/comments/2 does not work for all.
For me the VPN PPTP stopped work since Ubuntu 16.04 please fix this issue. The settings I received from my organization are:"
1725062,2017-10-20 14:53:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725062,2017-10-23 20:27:28 UTC,Possible workaround - choose 'store password for all users' in password field.
1725062,2017-10-24 18:33:54 UTC,thanks jingles!!!
1725062,2017-10-25 00:17:19 UTC,You are welcome!
1725062,2017-10-25 08:46:28 UTC,"Thanks for workaround, but still - stupid bug that is not fixed yet! :("
1725062,2017-10-26 01:26:34 UTC,"Heytimc, your problem looks like firewall block - the connection tries to establish, but it fails. You can check if you affected by this bug via terminal. Try to connect via terminal->type nmtui->choose connect->select your vpn connection. If connection fails - it some kind of network problem."
1725062,2017-10-25 14:50:26 UTC,Neither 'store password for all users' nor 'save password for all users' in found as an option in the VPN settings. There is 'Make available to other users' on the Details tab.  Is that what you mean?
1725062,2017-10-25 15:15:25 UTC,"John, you need to click a black icon at the right corner on the second tab (identification in my language) right in the password field. I attached a screenshot."
1725062,2017-10-25 15:20:57 UTC,:thumbs_up:
1725062,2017-10-25 15:48:18 UTC,Thanks for the workaround!!
1725062,2017-10-25 22:30:19 UTC,I have symptoms like these as well - I think these are the relevent syslog lines:
1725062,2017-10-25 13:16:08 UTC,"The problem is happening here too.
thanks jingles it worked"
1725068,2017-10-20 01:02:24 UTC,Similar report at https://bugzilla.redhat.com/show_bug.cgi?id=1452914
1725068,2020-01-24 10:05:19 UTC,Zero crash reports in 18.04 onward.
1725078,2020-01-24 10:08:57 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725078,2018-05-05 11:29:49 UTC,"Repository with xserver fix. Works on ubuntu 16.04, 18.04."
1725078,2018-02-02 01:41:03 UTC,Alright. I understand why software wouldn't support such combos by default. Because both keys are modifiers and not normal keys.
1725078,2018-02-02 00:52:06 UTC,"@Daniel, I can confirm that many keyboard shortcuts can't be set under Xorg either in Bionic"
1725078,2018-01-25 07:26:11 UTC,"Vasya,"
1725078,2018-01-18 11:08:55 UTC,I have no problem setting such hotkey with Unity on Ubuntu 17.04. Please assign this bug report to a correct package instead of marking it invalid.
1725078,2018-01-18 08:21:57 UTC,"This package does not set shortcuts, it simply displays them in a pop-up window similar to how Unity used to."
1725078,2017-10-21 14:18:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725078,2018-01-25 13:23:38 UTC,"I can't check because I already uninstalled 17.10 and will not install it ever again. As far as I remember, installing nvidia drivers switched to Xorg automatically, and I still couldn't assign Ctrl+Shift shortcut. I was able to assign it when I installed Unity on 17.10, but there still was an issue. Ctrl+Shift worked, but it made Ctrl+Shift+C and other shortcuts like that stop working. I am on 16.04 now and everything works just perfect."
1725081,2017-10-27 13:18:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725081,2017-11-14 16:32:06 UTC,"Not sure whether this is the same issue. Since I moved to Ubuntu 17.10 I cannot copy and paste from gedit anymore. If I open gedit, write something, and then try to paste it in Firefox it does not work. When I try to paste, I get the following line in the stderr of gedit:"
1725081,2017-11-16 09:39:56 UTC,"is that under wayland sessions only, does it work under x11?"
1725081,2017-11-16 14:01:22 UTC,"I didn't check under x11, and I'm now running Ubuntu 17.04 so I can't check it."
1725086,2017-10-20 12:09:15 UTC,"Changing to affect linux package, does not look like a firmware issue."
1725086,2017-10-20 04:07:58 UTC,Now I have rebooted and I am using the kernel version 4.10.0-37-generic and there is no error. The problem appears to be with the kernel.
1725086,2017-11-21 20:25:45 UTC,Today the kernel version was updated to 4.13.0-17.20 was installed on my notebook and the error is no longer happening. I can use my notebook with Artful's kernel normally now.
1725086,2017-10-20 03:48:09 UTC,"My system is nigh unusable now. If I disconnect the wireless, the system becomes very unstable: sudo and gksu stops working, many programs don't open and other problems."
1725086,2017-10-20 03:55:03 UTC,"I'm sorry for sending the information in chunks, but it's so unstable there's no way I can do it all at once."
1725099,2018-05-11 23:28:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725099,2018-05-11 23:30:10 UTC,"Affects me with both the i386 and x86_64 netinstall images of 18.04 — the installation process completes unusually quickly, and upon rebooting, I get dropped to a terminal login. startx is not found."
1725099,2018-05-13 03:41:52 UTC,"Update: sudo apt-get install vanilla-gnome-desktop does install everything. However, regardless of whether I also tasksel'd it, I do get an errors encountered while configuring for both vanilla-gnome-default-settings and vanilla-gnome-desktop; dpkg --audit says to dpkg --configure both to resolve it, and that seems to fix it..."
1725101,2017-10-20 03:41:35 UTC,"StacktraceTop:
 g_str_hash (v=0x0) at ../../../../glib/ghash.c:1882
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x559e881ac300) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x559e881ac300, key=key@entry=0x0) at ../../../../glib/ghash.c:1153
 get_store_snap (error=0x0, cancellable=0x559e882498d0, name=0x0, plugin=0x559e88132110) at ../plugins/snap/gs-plugin-snap.c:602
 gs_plugin_refine_app (plugin=<optimized out>, app=<optimized out>, flags=48367098, cancellable=0x559e882498d0, error=0x7fdcef495928) at ../plugins/snap/gs-plugin-snap.c:707"
1725101,2019-04-19 08:33:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725118,2017-10-20 05:24:02 UTC,"Apparently this is a known issue, see this upstream bug filed in February: https://github.com/jliljebl/flowblade/issues/329"
1725118,2017-12-11 07:42:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725118,2019-08-06 07:48:20 UTC,the desktop file from 2.0 fixes it by enforcing X11 at launch
1725131,2017-11-01 15:18:59 UTC,"Addition to my previous comment: I can still see the ""dropbox"" process on the system monitor even after the indicator crashed. But I don't have any idea on how to figure out the reason the indicator keeps crashing..."
1725131,2017-11-01 15:14:34 UTC,"I'm affected too. This bug renders Dropbox hardly usable on my desktop as without the indicator I cannot use the ""selective sync"" feature."
1725131,2017-10-30 15:52:10 UTC,same here :(
1725131,2017-10-20 12:14:42 UTC,"I have two computers and the same happens to me since ubuntu 17.10, in 17.04 all its perfec in 17.10 its broken. The indicator in 17.10 appears when I enter the desktop, and in a few minutes disappear the indicator. Also in that time if I click on the indicator does not appear the menu and remains frozen, or if it appears costs a lot and just after leaving the menu disappears the indicator."
1725131,2017-10-20 12:05:29 UTC,Indicator is not showing any recent changes to files. Plus if I click on indicator a number of times the old grey version shows.
1725131,2017-10-20 13:34:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725132,2018-04-12 01:43:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725133,2018-03-27 07:09:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725133,2018-03-28 06:14:07 UTC,"See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/87
Fixed in https://gitlab.gnome.org/GNOME/mutter/merge_requests/58"
1725133,2018-04-18 21:41:59 UTC,This bug was fixed in the package mutter - 3.28.1-1
1725136,2017-10-20 07:26:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/513635"
1725136,2017-10-26 14:05:06 UTC,"Thanks for taking care of this Chason. As you see from my review comments, there are a few more things that need to be sorted out."
1725149,2018-02-07 07:59:40 UTC,"Change abandoned by Rico Lin (<email address hidden>) on branch: master
Review: https://review.openstack.org/513636"
1725151,2017-10-25 13:23:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725160,2020-11-16 08:02:20 UTC,Zero crashes after 18.04 so consider it fixed.
1725160,2018-02-14 02:21:26 UTC,"Tracking in:
https://errors.ubuntu.com/problem/ae8fffc26dce834957d02421350f3841472b2ad7"
1725160,2017-10-23 11:12:10 UTC,"My laptop (a Clevo) has the intel hooked up to the internal pannel. All other 3 connections (one hdmi en two mini-displayports) are only hooked up to the nvidia card.
Intel can't see the 3 external connections. Nvidia 'passes through' the intel card.
This worked like a charm when running in 'discrete' mode in ubuntu 17.04."
1725160,2017-10-20 13:05:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725160,2017-10-20 08:00:47 UTC,"StacktraceTop:
 meta_monitor_manager_kms_apply_crtc_mode (manager_kms=manager_kms@entry=0x562760a4f1b0, crtc=0x562760d24a40, x=x@entry=0, y=y@entry=0, fb_id=fb_id@entry=0) at backends/native/meta-monitor-manager-kms.c:1649
 meta_renderer_native_finish_frame (renderer_native=0x562760a48550) at backends/native/meta-renderer-native.c:1801
 clutter_stage_cogl_redraw (stage_window=0x562760d04390) at cogl/clutter-stage-cogl.c:871
 meta_stage_native_redraw (stage_window=0x562760d04390) at backends/native/meta-stage-native.c:301
 clutter_stage_do_redraw (stage=0x562760a5de70) at clutter-stage.c:1121"
1725160,2017-10-20 08:14:57 UTC,"Many/most laptops with hybrid graphics don't have the discrete GPU wired to the internal screen. If that includes you then discrete-only mode might only work with an external monitor attached. Because typically the Nvidia GPU is wired to at least one HDMI/DisplayPort, but not usually the laptop panel. Usually only the Intel GPU is attached to the laptop LCD."
1725163,2017-10-20 08:06:17 UTC,I think that this might be related to:
1725163,2017-10-20 08:12:49 UTC,"Tried unplugging camera, problems are gone. Cheese is starting instantly (with camera plugged in 33 seconds), shutdown/logout are instant (with camera 25- 30 sec, didn't measure exact time).
Camera make and model: Logitech c525"
1725163,2017-10-20 10:37:11 UTC,More strangeness.  Open the users panel in control center with a webcam takes > 20 seconds.  If I rmmod uvcvideo then it opens immediately.
1725163,2017-11-08 10:39:53 UTC,Added to Trello: https://trello.com/c/1ExC3seJ/131-bug1725163-gnome-shell-freezes-for-25s-when-logout-shutdown
1725163,2018-06-08 14:29:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725168,2017-10-29 19:51:14 UTC,Thanks. A preference option would work. Suggest adjustable from 100% muted to 0%
1725168,2017-10-21 02:36:42 UTC,"I mean ""full mute"" as opposed to ""reduced level"". If a separate booth ducking option would provide this, that would be fine. Even if I'm using the existing option to not route mic to booth, still want to mute the booth monitors to avoid echo from the music. (The main/broadcast output should not mute, only reduce level.)"
1725168,2017-10-23 16:05:19 UTC,"Nice idea. How should the GUI look like for this feature?
Is a preferences option enough, that mutes booth in case talkover is switched on?"
1725168,2017-10-20 12:32:02 UTC,This is already possible with the microphone ducking feature. It would make sense to add a new option to apply microphone ducking to the booth output only if there is a use case for applying ducking to the booth output but not the master output (which is also used for broadcasting). When would that be the case?
1725168,2017-10-20 12:34:33 UTC,"I may have misunderstood the request. Do you mean that you would want the booth output to mute all output including the microphones? In that case, would it work to use the existing option to not route the microphones to the booth output?"
1725177,2017-10-20 08:21:26 UTC,We might also want to take a similar approach for the ceph charms; package updates should always be managed.
1725177,2018-07-09 01:57:08 UTC,"I believe this is addressed by bug 1383674, at least for liberty and above."
1725177,2018-07-09 02:07:41 UTC,"Oh, of course it's not fixed by bug 1383674, which was for neutron-openvswitch-agent restarts."
1725178,2017-11-07 18:49:33 UTC,"Correct, no mixing. Just select a source to send to Booth out."
1725178,2018-01-01 07:34:34 UTC,Adding additional options to the booth output seems much simpler than the aux send bus.
1725178,2017-12-28 13:47:32 UTC,An auxiliary send bus could be used like a second headphone channel.
1725178,2017-12-28 10:02:37 UTC,"To support this use case with an aux send bus, we need to allow to path booth to this bus as well. Does this fit?
The original request is more like a second headphone channel."
1725178,2017-12-28 04:47:49 UTC,"We have discussed implementing an auxiliary send bus for an unrelated purpose (using hardware effects processors), but it may also be useful for your use cases too, Inanna Moon. I think that would be better than repurposing the Booth output. That task is tracked in Bug #1740346."
1725178,2017-11-03 16:43:27 UTC,"In our case, ""Air Monitor"" will add the Talkover mix back to Headphones and Both, which was original removed to avoid Echos/Delay. Is there as use case to short time monitor the air signal with lets say a momentary switch?"
1725178,2017-10-21 02:56:56 UTC,"Ideally, have ""booth sends"" on sources like how they already have headphone sends."
1725178,2017-10-31 18:46:40 UTC,Could you describe the current setup of the booth selectors of your studio board?
1725178,2017-10-29 20:09:13 UTC,"On the radio station mix/control board, we had a selector switch to choose which output or input to send to the studio monitor. Main output, cue output (aka headphone output), ""air"" input or any of the other inputs to the board."
1725178,2017-10-23 16:11:51 UTC,Please link the related forums thread.
1725178,2017-10-20 12:30:17 UTC,What do you propose as the possible sources for the booth output? Currently it is possible to select either the master mix or the master mix without microphones.
1725178,2017-11-03 06:46:44 UTC,"The board has a Main bus and a Cue bus. Each of the primary inputs (decks, mics and aux's) can be sent to either Main or Cue. It also has a secondary input for the ""Air monitor"", which is only available to the headphone and studio/booth outputs."
1725180,2020-02-11 07:43:37 UTC,"^^^
That's only the window spread performance fix that has landed (to be released in 3.35.91). Not everything yet."
1725180,2020-03-25 02:08:17 UTC,gjs (1.63.92-1) experimental; urgency=medium
1725180,2020-03-24 19:01:57 UTC,This bug was fixed in the package gnome-shell - 3.36.0-2ubuntu1
1725180,2020-03-12 02:16:52 UTC,"Don't panic, those are just tags. The full set of fixes detailed in comment #12 ARE expected to be released in Ubuntu 20.04."
1725180,2020-02-26 08:33:25 UTC,Fixed in (you need both):
1725180,2020-02-19 01:26:47 UTC,"^^^
That's fixed in gjs 1.63.91"
1725180,2020-02-07 07:25:02 UTC,Since I've got a number of fixes coming in this area already and they are quite nearby to each other in the GUI we can treat it as a single issue. I've now listed the required fixes at the top of this bug.
1725180,2017-10-21 19:32:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725180,2020-02-05 02:58:37 UTC,But I won't make it a definite bug link. This bug is a little too vague right now...
1725180,2020-02-05 02:55:40 UTC,I think this should be resolved with https://gitlab.gnome.org/GNOME/gnome-shell/issues/1271
1725180,2018-02-12 02:10:19 UTC,There is a variety of reasons for this. I have tried to start listing (and fixing) them here:
1725180,2018-02-09 09:50:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725180,2018-01-09 09:48:35 UTC,It sounds like you're referring to gnome-shell and not Xwayland.
1725180,2020-02-07 07:21:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725181,2017-10-20 08:46:16 UTC,"StacktraceTop:
 handle_new_stream (demuxer=demuxer@entry=0x7f658c2062e0, i=0) at ../demux/demux_lavf.c:595
 add_new_streams (demuxer=0x7f658c2062e0) at ../demux/demux_lavf.c:727
 demux_open_lavf (demuxer=0x7f658c2062e0, check=<optimized out>) at ../demux/demux_lavf.c:906
 open_given_type (global=global@entry=0x561c667eaed0, log=log@entry=0x7f658c0018a0, desc=0x561c654da7e0 <demuxer_desc_lavf>, stream=stream@entry=0x7f658c001a20, params=params@entry=0x7f659b7fdaa0, check=check@entry=DEMUX_CHECK_NORMAL) at ../demux/demux.c:1288
 demux_open (stream=0x7f658c001a20, params=params@entry=0x7f659b7fdaa0, global=global@entry=0x561c667eaed0) at ../demux/demux.c:1373"
1725181,2017-10-20 09:07:45 UTC,Thanks for the bug report. Can you please also report it to the MPV authors here:
1725181,2018-01-08 06:19:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725181,2018-01-08 06:19:55 UTC,"This crash is also being tracked in:
https://errors.ubuntu.com/problem/766aa179db4a64a6aee7350a01fe4cee2de293da"
1725197,2018-10-04 18:06:01 UTC,"The same for cosmic beta
http://releases.ubuntu.com/cosmic/HEADER.html"
1725197,2018-07-30 16:03:15 UTC,A similar reference to a non-existing i386 installer is still there in Ubuntu 18.04.1
1725198,2017-10-23 18:34:09 UTC,"Indeed, specifying the aliases in the YAML no longer does anything, more information on this is here:"
1725198,2019-09-26 11:08:48 UTC,"I hope we've improved our documentation about this. I've marked the ubuntu/snapd task of the bug as Invalid as the issue isn't about the snapd package in Ubuntu. If you think there is more we should do, please let us know."
1725211,2018-04-23 19:10:05 UTC,"Reviewed:  https://review.openstack.org/555202
Committed: https://git.openstack.org/cgit/openstack/ironic-inspector/commit/?id=f257c571771a024cd36f792e80e77f4483c4162c
Submitter: Zuul
Branch:    master"
1725211,2018-03-22 08:47:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555202"
1725211,2018-03-20 13:06:23 UTC,"Reviewed:  https://review.openstack.org/553822
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=c48069bea7c925847291d62490ae67a2020ae736
Submitter: Zuul
Branch:    master"
1725211,2018-03-16 15:18:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/553822"
1725211,2018-03-16 10:44:39 UTC,"Reviewed:  https://review.openstack.org/515657
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=b2e9b6dac6c7a2f4c0755a94bdb008317c34a9df
Submitter: Zuul
Branch:    master"
1725211,2018-04-24 14:44:46 UTC,"Reviewed:  https://review.openstack.org/555610
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=6df82ee2bcc702168e80ec7c81e5573d766f9c71
Submitter: Zuul
Branch:    master"
1725211,2018-02-19 13:54:01 UTC,"Milan is no longer working in OpenStack, so this can be taken over."
1725211,2017-10-23 20:41:14 UTC,Hi Ruby!
1725211,2017-10-27 09:16:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/515657"
1725211,2017-10-20 09:48:28 UTC,"I'm good with this. Note that it will need a fix in ironic-inspector to treat ""inspect wait"" as a valid state OR we'll have to guard this new state with a microversion."
1725211,2017-10-20 09:53:35 UTC,"Good point, I'll report that briefly on inspector!
Thanks!"
1725211,2018-02-06 05:44:07 UTC,"Greetings guys, mind I ask if this work will be continued?"
1725211,2017-10-20 11:33:23 UTC,"Before inspection of a node can be triggered, inspector checks the node is in a valid provisioning state[1]. Since ironic will eventually adopt the inspect-wait state[2]."
1725211,2017-10-23 18:43:48 UTC,"Hi Milan, thx for the RFE."
1725211,2017-10-20 10:19:54 UTC,Thanks Milan sounds like a good plan!
1725217,2017-10-20 10:20:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725217,2017-10-20 10:25:46 UTC,Please also see [1]. There are efforts to package Peek for Debian [2].
1725217,2017-10-20 23:55:04 UTC,*** This is an automated message ***
1725227,2017-10-20 10:41:34 UTC,"StacktraceTop:
 g_settings_set_property (object=0x562bf0956ba0, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at ../../../../gio/gsettings.c:590
 object_set_property (nqueue=0x562bf0975570, value=<optimized out>, pspec=0x562bf096e110, object=0x562bf0956ba0) at ../../../../gobject/gobject.c:1439
 g_object_new_internal (class=class@entry=0x562bf097dcf0, params=params@entry=0x7ffd80e62850, n_params=n_params@entry=1) at ../../../../gobject/gobject.c:1831
 g_object_new_valist (object_type=94746720060176, first_property_name=first_property_name@entry=0x7f80b79f0bc0 ""schema-id"", var_args=var_args@entry=0x7ffd80e629a0) at ../../../../gobject/gobject.c:2120
 g_object_new (object_type=<optimized out>, first_property_name=first_property_name@entry=0x7f80b79f0bc0 ""schema-id"") at ../../../../gobject/gobject.c:1640"
1725236,2017-10-26 07:38:28 UTC,"I see same problem running Ubuntu 16.04 with Geforce GTX 1060 card, that is vulkan programs failing with VK_ERROR_INCOMPATIBLE_DRIVER."
1725236,2017-10-21 12:20:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725236,2017-10-21 04:25:11 UTC,"Here are some further investigations, if it can help:"
1725240,2017-11-17 19:36:15 UTC,"Reviewed:  https://review.openstack.org/514637
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=c8984ca355649a27446d8198151bf2989159b8a3
Submitter: Zuul
Branch:    master"
1725240,2018-03-07 11:51:50 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/550452"
1725240,2018-03-07 11:52:02 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/550453"
1725240,2018-03-29 12:02:28 UTC,"Reviewed:  https://review.openstack.org/550452
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=e0492844d832529df2bf1533de55c99a95592d35
Submitter: Zuul
Branch:    stable/ocata"
1725240,2018-03-29 12:03:03 UTC,"Reviewed:  https://review.openstack.org/550453
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=db0f11e5be172706a34d56eca8822fc2bdfd4de6
Submitter: Zuul
Branch:    stable/pike"
1725240,2019-03-28 10:17:27 UTC,"Doug, is there still anything to be done here?"
1725240,2019-11-20 04:17:48 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1725255,2017-10-20 12:14:23 UTC,"StacktraceTop:
 __libc_message (action=action@entry=(do_abort | do_backtrace), fmt=fmt@entry=0x7f2eb0d889e6 ""*** %s ***: %s terminated\n"") at ../sysdeps/posix/libc_fatal.c:181
 __GI___fortify_fail_abort (need_backtrace=need_backtrace@entry=true, msg=msg@entry=0x7f2eb0d8896d ""buffer overflow detected"") at fortify_fail.c:33
 __GI___fortify_fail (msg=msg@entry=0x7f2eb0d8896d ""buffer overflow detected"") at fortify_fail.c:44
 __GI___chk_fail () at chk_fail.c:28
 _IO_str_chk_overflow (fp=<optimized out>, c=<optimized out>) at vsprintf_chk.c:31"
1725259,2017-10-20 12:00:07 UTC,This change was made by a bot.
1725259,2017-10-20 16:14:40 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1725259,2017-10-22 20:35:39 UTC,Test Kernel 4.14 rc5 mainline. The bug also exist there
1725259,2017-10-24 03:59:03 UTC,Please try drm-intel-nightly [1].
1725259,2017-10-24 06:03:21 UTC,"Same problem, i will fill the bug on freedesktop"
1725259,2017-11-14 19:05:57 UTC,I tested with Debian buster and Fedora 27 and the file is playing without any GPU hangs. So the problem might be Ubuntu only. I also tested Ubuntu 18.04 (daily 13/11) and the hangs still occurs. FOr me this isn't a kernel or DRM/Intel Bug
1725268,2018-04-12 19:46:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725290,2017-10-20 13:44:41 UTC,"StacktraceTop:
 ?? ()
 wxGDIObject::IsOk (this=0x559a84241a38) at ../include/wx/gdiobj.h:49
 wxWindowBase::GetBackgroundColour (this=this@entry=0x559a84241960) at ../src/common/wincmn.cpp:1588
 wxDCImpl::InheritAttributes (this=this@entry=0x7fbf68002e30, win=win@entry=0x559a84241960) at ../src/common/dcbase.cpp:1031
 wxNativeDCFactory::CreateClientDC (this=<optimized out>, owner=0x7fbf7b7fd780, window=0x559a84241960) at ../src/common/dcbase.cpp:143"
1725290,2017-10-21 00:11:55 UTC,The fix is described here: https://bugs.launchpad.net/ubuntu/+source/codeblocks/+bug/1710424
1725291,2017-11-01 16:04:44 UTC,"The patch: https://review.fuel-infra.org/#/c/37032
was prepared to fix the issue for branch: openstack-ci/fuel-7.0/2015.1.0"
1725293,2017-10-20 14:04:15 UTC,I'm not sure if I understand the issue:
1725306,2017-10-20 14:24:14 UTC,"StacktraceTop:
 ?? ()
 llvm_pipeline_generic (middle=0x0, middle@entry=0xd1d2a0, fetch_info=fetch_info@entry=0xbf9a4cfc, in_prim_info=in_prim_info@entry=0xbf9a4d0c) at ../../../../src/gallium/auxiliary/draw/draw_pt_fetch_shade_pipeline_llvm.c:388
 llvm_middle_end_linear_run (middle=0xd1d2a0, start=0, count=<optimized out>, prim_flags=0) at ../../../../src/gallium/auxiliary/draw/draw_pt_fetch_shade_pipeline_llvm.c:541
 vsplit_segment_simple_linear (vsplit=0xc37980, icount=4, istart=0, flags=0) at ../../../../src/gallium/auxiliary/draw/draw_pt_vsplit_tmp.h:226
 vsplit_run_linear (frontend=0xc37980, start=0, count=4) at ../../../../src/gallium/auxiliary/draw/draw_split_tmp.h:60"
1725306,2020-01-24 10:04:30 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725313,2017-10-20 15:39:01 UTC,"This is on OpenStack using juju 2.2.3, fwiw"
1725313,2017-10-21 12:32:56 UTC,"This is nothing to do with the provider, all charms always strip hidden
files:
https://github.com/juju/charm/blob/v6-unstable/charmdir.go#L226"
1725313,2017-10-23 09:45:36 UTC,"Ok, thanks."
1725313,2017-10-23 14:18:00 UTC,"Ah, you're probably right. I just saw it filtering out dirs that aren't
hooks, but it was to avoid the Chmod, indeed."
1725315,2018-10-27 21:57:02 UTC,"I see the same behavior.  Ubuntu 18.10.  Gnome Shell over Wayland.  Evolution is unstable unless the ""evolution-indicator"" package is removed."
1725315,2018-10-19 07:23:46 UTC,"Still occurs in 18.10/cosmic (evolution 3.30.1-1build1, evolution-indicator 0.2.20-0ubuntu36)."
1725315,2018-04-02 13:17:58 UTC,"Can this be marked as a blocking bug for Ubuntu 18.04, so that we can get this fixed as a priority?"
1725315,2018-03-31 14:19:25 UTC,This still occurs in 18.04/bionic. The workaround of removing evolution-indicator also still works.
1725315,2019-11-02 13:21:48 UTC,I reported the bug including a proposed fix on evolution-indicator: https://bugs.launchpad.net/evolution-indicator/+bug/1851036
1725315,2017-11-14 20:58:02 UTC,"Thank you for this, José.  My machines that were crashing had the evolution-indicator package installed, and the one that never crashed did not."
1725315,2017-11-06 05:11:22 UTC,"Per comment #9, I confirm it only happens on gnome-shell on wayland mode.
I tested thoroughly over the last few days and I did not experience a single crash on gnome-shell on Xorg.Once I switch back to gnome-shell on wayland, the frequent crashes start happening again."
1725315,2017-10-27 08:07:34 UTC,"This only happens on gnome-shell on wayland mode. It is evolution indicator plugin. Unfortunately, even clicking on the checkbox to disable it (on the list of evolution plugins) crashes evolution."
1725315,2017-10-26 10:00:23 UTC,"I have just one IMAP account set up on my evolution instance, and it is neither gmail nor yahoo. Yet I have this problem. If ""second number verification"" refers to two-factor authentication, then no, my email account does not use it."
1725315,2017-10-23 14:51:50 UTC,hi there. I don t know if it is the second number verification to blame. But my evolution did not synchronise with google server. After that it crashes. But synchronising with hotmail server was not an issue.
1725315,2017-10-22 09:03:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725315,2017-10-20 14:55:22 UTC,"StacktraceTop:
 ?? ()
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x7c, hash_table=0x557e5540cb60) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x557e5540cb60, key=key@entry=0x7c) at ../../../../glib/ghash.c:1153
 lookup_cached_xatom (atom=0x7c, display=0x557e553e5000) at ././gdk/x11/gdkproperty-x11.c:76
 gdk_x11_atom_to_xatom_for_display (display=0x557e553e5000, atom=0x7c) at ././gdk/x11/gdkproperty-x11.c:109"
1725315,2017-10-27 08:13:16 UTC,Workaround: uninstall evolution-indicator package.
1725316,2017-10-20 14:44:44 UTC,"StacktraceTop:
 touch_handle_motion (data=0x55c52c992030, wl_touch=<optimized out>, time=6672261, id=<optimized out>, x=431651, y=141008) at ././gdk/wayland/gdkdevice-wayland.c:2480
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffc500c3080, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffc500c3150) at ../src/x86/ffi64.c:525
 wl_closure_invoke (closure=closure@entry=0x55c52c9b4f00, flags=flags@entry=1, target=<optimized out>, target@entry=0x55c52c9c1390, opcode=opcode@entry=2, data=<optimized out>) at ../src/connection.c:935
 dispatch_event (display=display@entry=0x55c52c96d810, queue=<optimized out>) at ../src/wayland-client.c:1310"
1725316,2017-10-23 21:07:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725316,2019-05-28 12:41:04 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1725316,2019-07-28 04:17:34 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1725317,2019-01-03 20:27:41 UTC,"After our upgrade in December, we tried leaving max_stanza_size at 65536, but also began hitting problems with ""XML stanza is too big"" in the gateway log.  This was seen in saving a large invoice, so I agree with Jason that there is still an issue with handling incoming data, in this case via the translator.  We are running OpenSRF master (~3.1)."
1725317,2017-10-20 15:06:11 UTC,I should add that we increased the max stanza size as a work around. The log messages that we shared are obviously from before making the max stanza size increase.
1725322,2017-11-20 13:23:59 UTC,"That last sentence was incorrect, Instead of ""Still this only happens with kernels released after 4.4.0-96"" you should read Still this only happens with kernels released after 4.4.0-92"""
1725322,2017-11-20 13:16:05 UTC,"Interestingly when running sudo ls, using the machine keytab, is works. So looks for me the problem is somewhere in the user kerberos ticket. Still this only happens with kernels released after 4.4.0-96"
1725322,2017-10-27 16:02:42 UTC,"mounting on a computer running 4.4.0-97 with automounter still gives ""error cannot access xx: File name too long"" but when using gvfs-mount it works perfectly."
1725322,2017-10-24 12:04:56 UTC,Also fails with kernel 4.4.94-040494-generic
1725322,2017-10-23 13:36:22 UTC,"user@somecomputer:/vol/winshare/Public$ ls -all
ls: cannot access 'Applications': File name too long"
1725322,2017-10-21 14:50:56 UTC,The server is Samba 4.6.7. Users are stored in LDAP and authenticated with Kerberos. Here are the mount options I am using:
1725322,2017-10-20 16:45:07 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1725322,2017-12-03 19:41:45 UTC,This is fixed with 4.14.3. I'm guessing f74bc7c6679200a4a83156bb89cbf6c229fe8ec0 is what did it. Thanks!
1725322,2017-10-20 15:30:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725322,2017-09-18 23:40:09 UTC,I can not reproduce this issue using current linux/master branch.
1725322,2017-10-20 16:23:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1725322,2017-09-14 15:01:57 UTC,"Created attachment 258387
SMB3.0 fs attr info query & response"
1725322,2017-09-14 15:01:39 UTC,"Created attachment 258385
SMB2.1 fs attr info query & response"
1725322,2017-09-14 15:01:16 UTC,"Created attachment 258383
SMB2.0 fs attr info query & response"
1725322,2017-09-14 05:46:38 UTC,That is SMB1.  Can you try with a SMB2 mount too?
1725322,2017-09-14 05:30:35 UTC,Both server and client are x86_64. Server is samba 4.6.7.
1725322,2017-09-14 05:24:15 UTC,"Created attachment 258363
CIFS queries and responses during mount"
1725322,2017-09-14 04:22:44 UTC,Please also try v4.13 as it contains the change 6e3c1529c39e92ed64ca41d53abadabbaa1d5393
1725322,2017-09-13 21:58:12 UTC,Which architecture do you see this on?
1725322,2017-09-10 18:59:10 UTC,"Ever since updating to 4.12.10, I have been getting ""File name too long"" messages when accessing my CIFS share:"
1725322,2017-09-14 15:04:28 UTC,"Same result with SMB2.0, SMB2.1, and SMB3.0. I've attached traces of the FileFsAttributeInformation queries and responses for all three protocol versions."
1725335,2017-10-20 16:46:42 UTC,"The old default profile from boot was never fully implemented, and never supported in Ubuntu. It was removed, because it was not ready for upstream. It would allow you to specify a profile name that would be used instead of unconfined on boot, so assigned to init. Using the grub kernel parameter
  unconfined=foo"
1725340,2019-08-14 13:01:15 UTC,"I'm changing this to won't-fix because:
- there's no requirement that a custom constructor be named MAKE-HASH-TABLE nor interface functions GETHASH,REMHASH,etc. At least one large lisp application (QPX) has been using its own hash table implementation for nearly 2 decades. Those tables have their own constructor, the point being that alternative hash-tables can be provided as a library without relying on anything builtin-in.  While a common interface would be nice-to-have, it is not a requirement.
- I recently changed GETHASH etc to be ""pure virtual"" (a la C++) mainly as an experiment and aid to debugging. So it is now in fact possible to put other algorithms behind the built-in hash-table type."
1725340,2017-10-24 21:43:00 UTC,"If hash-tables do preserve order, that's great, if that becomes intended and is tested for.  Otherwise, one can't depend on that behavior persisting.  It also won't be portable, but then neither would a :stable keyword argument."
1725340,2017-10-24 02:43:29 UTC,"There are a myriad of variations that people would like. It doesn't make sense to add one keyword that adds this option per se to the builtin tables. It would be more useful to design a pluggable hash-table architecture where GETHASH and (SETF GETHASH) dispatch to table-specific code.
[I daren't say generic in the CLOS sense. Dispatch should be fast, the way our ANSI streams dispatch]
Things people would like:
* use less memory
* use different hash strategy
* preserve insertion order
* be lock-free
Those could have totally different code behind them. If make-hash-table is the universal constructor, it likely won't have a fixed set of keywords."
1725342,2017-11-17 15:56:40 UTC,"Hi,
    Thanks for reporting this issue. We'll reproduce this issue and implement the right solution to handle the length constraints.  We'll plan to include this fix in a future release."
1725342,2017-11-20 11:28:04 UTC,Thank you for looking into this issue.
1725352,2017-10-26 08:31:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725355,2020-05-11 20:04:07 UTC,"Is this still an issue, or was this resolved by updates to MAAS or Maniacs-setup?"
1725358,2017-10-20 17:15:43 UTC,"I'm somewhat surprised that it is on, which suggests this is behaviours is probably only present on non-Intel images."
1725358,2017-10-20 17:45:32 UTC,/etc/default/grub
1725358,2017-11-01 15:58:40 UTC,Note that this does not appear to impact the trusty/arm64/efi images.
1725358,2017-11-29 00:28:03 UTC,Is there any additional information we could help provide for this?
1725377,2021-01-12 21:46:06 UTC,This should be fixed by https://code.launchpad.net/~dano6/podbird/podbird/+merge/387072
1725377,2020-05-20 12:43:38 UTC,"It would seem that the Queue table in the SQLite DB is being emptied upon quitting the app, or phone reboot"
1725377,2020-05-20 11:19:11 UTC,"Oh, somo more info in the subject:
https://forums.ubports.com/topic/4299/podbird-reignited/4"
1725377,2019-07-23 02:25:05 UTC,I can confirm this issue on latest versions of Podbird / OS
1725377,2019-07-23 02:40:34 UTC,Addendum:
1725377,2017-10-22 13:58:03 UTC,"It's a limitation of the life cycle policy, there's nothing Podbird can do when suspended so there's no way of working around it (other than exempting Podbird from the life cycle management completely). Ideally I think apps should be woken up and sent a termination signal when the user closes them to allow them to save state."
1725377,2017-10-22 00:01:06 UTC,"Thanks for the comment, Michael. That does indeed seem to be the issue. Closing in the foreground does keep the position."
1725377,2017-10-21 22:38:28 UTC,One thing to be aware of is that it's only possible for Podbird to remember your position if it's in the foreground when it's closed. Otherwise the Ubuntu Touch lifecycle policy will have suspended it and it'll have no opportunity to save the current position.
1725377,2017-10-21 15:30:23 UTC,"I'm on Mako Nexus 4 and it works as you expect in your bug report so this must be a bug with your device only.  Another question, why is this respository/project on launchpad and not on github?  Thanks!"
1725377,2017-10-22 22:31:57 UTC,Thanks again. I filed a bug here https://github.com/ubports/ubuntu-touch/issues/312
1725382,2017-10-20 17:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1725386,2019-06-10 01:17:53 UTC,"I have a proposed solution here:
https://bazaar.launchpad.net/~joe/ubuntu-touch/podbird/view/head:/app/ui/SearchPage.qml"
1725386,2020-04-13 19:54:28 UTC,Fixed by https://code.launchpad.net/~dano6/podbird/podbird/+merge/381693
1725386,2020-04-14 00:40:58 UTC,Thank you for the update.
1725386,2020-04-14 15:18:09 UTC,https://code.launchpad.net/~dano6/podbird/podbird/+merge/382136 should fix this
1725386,2020-04-14 16:06:54 UTC,"It crashes less for me with #2 workflow. It can freeze after returning from search page when you add many podcasts, but wait a bit should help (we should rewrite backend probably)."
1725388,2017-11-04 07:18:37 UTC,"Hi,"
1725388,2017-11-17 15:47:12 UTC,"Hi,
The Ubuntu 17.10 support will be available in the 3.17.11 release which is planned in month of November end. Please check for the release announcement in https://launchpad.net/ubuntu/+source/hplip and the driver can be downloaded from https://developers.hp.com/hp-linux-imaging-and-printing"
1725388,2017-10-20 17:55:54 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f99d0f124e8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=<optimized out>, str=0x7f99d0f0ee6e ""free(): invalid pointer"", ptr=<optimized out>, ar_ptr=<optimized out>) at malloc.c:5425
 _int_free (av=0x7f99d1144c20 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4174
 __GI___libc_free (mem=<optimized out>) at malloc.c:3144
 operator delete (ptr=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/del_op.cc:49"
1725388,2017-10-24 22:20:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725395,2017-10-21 13:06:50 UTC,"The tv is a 43"" 3840x2160 samsung an by chance was misdetected as a 83"" one
In this event it was working at native resolution and had the login visible."
1725395,2017-10-23 20:43:45 UTC,not an issue with the file manager nautilus
1725395,2017-10-26 13:13:56 UTC,"found a pattern,"
1725395,2017-12-02 14:40:38 UTC,when failing xrandr
1725395,2017-12-23 15:57:24 UTC,from dmesg
1725395,2017-12-23 16:12:13 UTC,"more from dmesg about amdgpu
[    1.199336] amdgpu 0000:02:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff"
1725406,2017-10-22 15:52:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725409,2017-10-20 18:39:04 UTC,Why is /boot/efi not mounted on your system?  Please attach your /etc/fstab.
1725409,2017-10-20 19:55:10 UTC,I think /boot/efi is mounted on my system as shown by lsblk so I'm not sure why I got this error.
1725409,2017-10-20 20:10:23 UTC,"The bug contents clearly show that at the time the bug report was filed, /boot/efi was mounted.  But equally clearly, the bug report shows that the grub package could not find the EFI directory at package upgrade time:"
1725409,2017-10-20 20:38:22 UTC,Attaching sanitized etc/fstab
1725409,2017-10-24 15:50:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725414,2018-12-12 14:46:02 UTC,https://errors.ubuntu.com/problem/af9c8793878a1e015adad962bfdc06c13de724d1 is similar and still in recent versions
1725414,2018-06-09 13:22:51 UTC,dupe of bug 951570?
1725414,2017-10-23 14:05:02 UTC,"The segfault is in the printers configuration page, do you remember what you were doing there?"
1725414,2017-10-22 18:15:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725414,2017-10-20 18:51:40 UTC,"StacktraceTop:
 on_get_job_attributes_cb (source_object=<optimized out>, res=<optimized out>, user_data=<optimized out>) at cc-printers-panel.c:346
 g_task_return_now (task=0x7feb180076e0) at ../../../../gio/gtask.c:1145
 complete_in_idle_cb (task=0x7feb180076e0) at ../../../../gio/gtask.c:1159
 g_main_dispatch (context=0x559cee6108e0) at ../../../../glib/gmain.c:3148
 g_main_context_dispatch (context=context@entry=0x559cee6108e0) at ../../../../glib/gmain.c:3813"
1725420,2018-01-24 22:31:44 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1452
1725437,2017-12-02 18:36:58 UTC,Try running from terminal. Does it show any error?
1725443,2017-10-20 20:26:32 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x5639fadbd920, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x5639fadbd920) at ../../../../gobject/gobject.c:3196
 g_weak_ref_get (weak_ref=<optimized out>) at ../../../../gobject/gobject.c:4369
 g_settings_backend_invoke_closure (user_data=0x7f82ec0471c0) at ../../../../gio/gsettingsbackend.c:263
 g_main_dispatch (context=0x5639fa917af0) at ../../../../glib/gmain.c:3148"
1725443,2018-01-14 14:57:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725445,2017-10-28 01:30:48 UTC,More information on this bug.  It appears to be a Wayland problem.  Things appear to work properly in Gnome with an Xorg session.
1725447,2017-11-11 22:53:50 UTC,I was able to reproduce this bug by removing the ubuntu dock from GNOME Shell 3.26.1 in distribution 17.10.
1725447,2017-11-11 22:57:57 UTC,"docky
[Info  17:57:02.221] Docky version: 2.2.1.1 Release
[Info  17:57:02.224] Kernel version: 4.13.0.16
[Info  17:57:02.224] CLR version: 4.0.30319.42000
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant ""murrine-scrollbar"", expected valid string constant
[Error 17:57:02.358] [SystemService] Could not initialize power manager dbus: 'Could not load type 'Docky.Services.SystemService\+IUPowerProxy' from assembly 'DBus.Proxies, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' because it is implements the inaccessible interface 'Docky.Services.SystemService+IUPower'.'
[Info  17:57:02.359] [SystemService]   at System.Reflection.Emit.TypeBuilder.CreateTypeInfo () [0x002dc] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Reflection.Emit.TypeBuilder.CreateType () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
  at DBus.TypeImplementer.GetImplementation (System.Type declType) [0x000e3] in <91cfe10d2aa049c9af550645dbbec075>:0
  at DBus.BusObject.GetObject (DBus.Connection conn, System.String bus_name, DBus.ObjectPath object_path, System.Type declType) [0x00001] in <91cfe10d2aa049c9af550645dbbec075>:0
  at DBus.Connection.GetObject (System.Type type, System.String bus_name, DBus.ObjectPath path) [0x0002b] in <91cfe10d2aa049c9af550645dbbec075>:0
  at DBus.Connection.GetObject[T] (System.String bus_name, DBus.ObjectPath path) [0x00001] in <91cfe10d2aa049c9af550645dbbec075>:0
  at Docky.Services.SystemService.InitializeBattery () [0x00030] in <7cbfebdf01bd437fb1e0b3e770f0dbae>:0
[Error 17:57:02.363] [SystemService] Could not initialize Network Manager dbus: 'Could not load type 'Docky.Services.SystemService\+INetworkManagerProxy' from assembly 'DBus.Proxies, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' because it is implements the inaccessible interface 'Docky.Services.SystemService+INetworkManager'.'
[Info  17:57:02.364] [SystemService]   at System.Reflection.Emit.TypeBuilder.CreateTypeInfo () [0x002dc] in <8f2c484307284b51944a1a13a14c0266>:0
  at System.Reflection.Emit.TypeBuilder.CreateType () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
  at DBus.TypeImplementer.GetImplementation (System.Type declType) [0x000e3] in <91cfe10d2aa049c9af550645dbbec075>:0
  at DBus.BusObject.GetObject (DBus.Connection conn, System.String bus_name, DBus.ObjectPath object_path, System.Type declType) [0x00001] in <91cfe10d2aa049c9af550645dbbec075>:0
  at DBus.Connection.GetObject (System.Type type, System.String bus_name, DBus.ObjectPath path) [0x0002b] in <91cfe10d2aa049c9af550645dbbec075>:0
  at DBus.Connection.GetObject[T] (System.String bus_name, DBus.ObjectPath path) [0x00001] in <91cfe10d2aa049c9af550645dbbec075>:0
  at Docky.Services.SystemService.InitializeNetworkManager () [0x0005c] in <7cbfebdf01bd437fb1e0b3e770f0dbae>:0
[Info  17:57:02.371] [ThemeService] Setting theme: Classic
[Warn  17:57:02.387] [DesktopItemService] Could not find remap file '/home/windhaj/.local/share/docky/remaps.ini'!
[Info  17:57:02.455] [DockServices] Dock services initialized.
[Info  17:57:02.639] [PluginManager] Loaded ""Trash"".
[Info  17:57:02.652] [PluginManager] Loaded ""Recent Documents"".
Cairo.Surface is..."
1725447,2017-10-28 01:30:34 UTC,More information on this bug.  It appears to be a Wayland problem.  Things appear to work properly in Gnome with an Xorg session.
1725468,2017-10-27 10:30:47 UTC,Here is a video of the bug: https://youtu.be/Lnj2_AgQ7WU
1725480,2019-01-16 22:18:27 UTC,https://errors.ubuntu.com/problem/8ae0367905ba05bf620d0194fb83f741a7e717de
1725480,2018-03-18 13:35:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725480,2017-12-23 05:39:32 UTC,"#101 0x00007ff6a284413a in rb_shell_quit (shell=shell@entry=0x560d1192d240, error=error@entry=0x0) at rb-shell.c:2548"
1725480,2017-10-23 21:02:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1725480,2017-10-23 21:02:37 UTC,Did you filter the view and then try to interact with the content while it was updating?
1725480,2017-10-20 21:12:00 UTC,"StacktraceTop:
 gtk_tree_view_get_column (tree_view=tree_view@entry=0x560d11e507d0, n=n@entry=15) at ././gtk/gtktreeview.c:12343
 get_n_columns (tree_view=tree_view@entry=0x560d11e507d0) at ././gtk/a11y/gtktreeviewaccessible.c:253
 gtk_tree_view_accessible_do_remove_column (accessible=0x560d13073050, treeview=treeview@entry=0x560d11e507d0, column=column@entry=0x560d11e4f600, id=0) at ././gtk/a11y/gtktreeviewaccessible.c:1803
 _gtk_tree_view_accessible_remove_column (treeview=treeview@entry=0x560d11e507d0, column=column@entry=0x560d11e4f600, id=id@entry=0) at ././gtk/a11y/gtktreeviewaccessible.c:1828
 gtk_tree_view_remove_column (tree_view=tree_view@entry=0x560d11e507d0, column=0x560d11e4f600) at ././gtk/gtktreeview.c:12128"
1725480,2017-12-23 04:17:53 UTC,[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]
1725486,2017-10-20 21:25:09 UTC,"StacktraceTop:
 g_type_check_instance_is_a (type_instance=type_instance@entry=0x56003f462580, iface_type=iface_type@entry=94559046120912) at ../../../../gobject/gtype.c:4013
 g_file_equal (file1=0x56003f462580, file2=0x7fb2e8001e40) at ../../../../gio/gfile.c:667
 writeback_remove_recursively (mf=0x56003e59c190, file=0x7fb2e8001e40) at tracker-miner-files.c:266
 miner_files_filter_event (fs=<optimized out>, type=<optimized out>, file=0x7fb2e8001e40, source_file=0x7fb2e8001e40) at tracker-miner-files.c:315
 filter_event (source_file=0x7fb2e8001e40, file=0x7fb2e8001e40, type=TRACKER_MINER_FS_EVENT_MOVED, fs=0x56003e59c190) at tracker-miner-fs.c:2295"
1725486,2020-03-24 14:47:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725487,2017-10-24 12:08:47 UTC,"Hey Nathanel, sure!"
1725487,2020-01-24 10:06:47 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725487,2017-10-23 19:12:59 UTC,"Hi Didier,"
1725487,2017-10-20 21:56:29 UTC,I think the GDM login screen texture was intentional for Ubuntu 17.10.
1725487,2017-10-21 02:26:48 UTC,See bugs
1725487,2017-10-23 08:33:33 UTC,Thanks a lot for those bug reports and proposed fix!
1725487,2017-10-20 22:34:17 UTC,Thanks for your response Jeremy.
1725493,2017-10-22 19:55:57 UTC,"This sounds like a good topic for the weekly horizon meeting.  It would be nice to resolve the inconsistency, but I have to admit that referring to instances of virtual machines is more natural than ""servers"" (which sound more like VM hosts)."
1725493,2017-10-26 03:25:50 UTC,"We talked about this at the weekly meeting today. It makes sense to be consistent with Nova and Openstack CLI terminology, but we have been using ""instance"" and this is not causing confusion, so it's low priority. Would love to get some feedback on this during the upcoming summit."
1725493,2017-11-15 18:00:50 UTC,"Is there any feedback from the summit forum?
I failed to find the summit forum etherpad of horizon feedback session."
1725504,2017-10-20 22:42:04 UTC,"StacktraceTop:
 g_rec_mutex_get_impl (rec_mutex=0x1200000000) at ../../../../glib/gthread-posix.c:298
 g_rec_mutex_lock (mutex=0x1200000000) at ../../../../glib/gthread-posix.c:387
 g_static_rec_mutex_lock (mutex=mutex@entry=0x560a6747eb58) at ../../../../glib/deprecated/gthread-deprecated.c:708
 fluid_settings_setnum (settings=0x560a6747eb20, name=0x7fd6b2ed7118 ""synth.sample-rate"", val=48000) at ./src/utils/fluid_settings.c:1077
 fsd_instantiate (descriptor=<optimized out>, sample_rate=<optimized out>) at fluidsynth-dssi.c:300"
1725504,2017-10-21 18:21:10 UTC,See also bug #1725781: https://bugs.launchpad.net/ubuntu/+source/qtractor/+bug/1725781
1725504,2018-05-18 15:25:04 UTC,Does it happen with 18.04 ?
1725504,2019-07-29 15:01:57 UTC,moved http://phd-sid.ethz.ch/debian/qtractor/
1725504,2019-08-06 07:38:53 UTC,"Indeed having fluidsynth-dssi installed, keeps crashing qtractor."
1725513,2017-10-20 23:57:59 UTC,"PS: Debian apparently added the udev rules in usb-modeswitch-data, version 20160803-1; see https://launchpad.net/debian/+source/usb-modeswitch-data/+changelog."
1725522,2017-10-21 20:53:11 UTC,"The bug is fixed in launchpad by Arve E. I had a look at the Swedish translation upstreams, and while the fix could be committed there, I feel that it's no point if the translation isn't also updated (it has about 100 missing or fuzzy strings). I'll take care of that during this week."
1725522,2017-10-21 13:29:39 UTC,Translation revised through Launchpad.
1725522,2017-10-21 11:08:06 UTC,Thanks for your report. I called the Swedish translators' attention to it:
1725522,2017-10-21 11:13:26 UTC,"Thanks for the bug report - I'll investigate it later tonight, and will see if it also needs to be corrected upstreams."
1725523,2017-10-20 23:49:17 UTC,Removed chosen package since this bug doesn't concern that package
1725532,2017-10-23 20:58:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725532,2017-10-29 17:09:39 UTC,I tried to file a bug report here:
1725532,2017-10-29 17:34:16 UTC,The other bug was closed.  Here is the correct one.
1725550,2020-01-24 10:04:48 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725550,2017-10-21 02:57:44 UTC,"StacktraceTop:
 js::jit::AutoWritableJitCode::AutoWritableJitCode (size=2432, addr=0x3bfbc7ffcef8, rt=0x56192994aa00, this=0x7fff9da09dd0) at ./js/src/jit/JitCompartment.h:634
 js::jit::AutoWritableJitCode::AutoWritableJitCode (size=2432, addr=0x3bfbc7ffcef8, this=0x7fff9da09dd0) at ./js/src/jit/JitCompartment.h:637
 mozilla::Maybe<js::jit::AutoWritableJitCode>::emplace<unsigned char*&, unsigned long&> (this=0x7fff9da09dc8) at ./js/src/dist/include/mozilla/Maybe.h:432
 js::jit::Linker::newCode<(js::AllowGC)1> (this=this@entry=0x7fff9da0a0b0, cx=<optimized out>, kind=kind@entry=js::jit::BASELINE_CODE, hasPatchableBackedges=hasPatchableBackedges@entry=false) at ./js/src/jit/Linker.cpp:52
 js::jit::BaselineCompiler::compile (this=this@entry=0x7fff9da0a260) at ./js/src/jit/BaselineCompiler.cpp:134"
1725550,2017-11-04 11:39:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725567,2018-01-27 13:38:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725567,2018-01-27 14:08:02 UTC,I noticed that if I double or triple click the checkbox it begins working.
1725567,2018-01-27 13:37:55 UTC,"I'm also experiencing this bug, but for me the entire window becomes gray when I using the check box and nothing happens."
1725582,2017-10-27 10:02:35 UTC,Changed package to kernel-package as it seems more related to that than the Xorg.
1725582,2017-11-30 18:56:13 UTC,Issue is fixed with kernel update 4.13.0-17-generic.
1725582,2020-03-17 08:01:08 UTC,This change was made by a bot.
1725587,2017-10-23 13:44:33 UTC,This maybe manifesting elsewhere as well [1]. If so it cropped up around 10/17/2017.
1725588,2019-02-15 18:32:29 UTC,I tested Thunderbird 60.4 in an Ubuntu 16.04.5 live session with both Ambiance and Radiance and found the tab borders to be very faint but they were there. The border of the selected tab was definitely visible but admittedly not to the extent of when using the Adwaita theme which is what I normally use. Setting back to confirmed for now.
1725588,2019-05-04 14:08:11 UTC,"Still happening in Bionic with the latest 60.6.1, with the default theme."
1725588,2019-02-15 19:26:34 UTC,100% reproducible with Xubuntu 18.04 regardless of theme (over 20 installed). Looking for an upstream report.
1725588,2019-02-15 18:50:33 UTC,"Here is a screenshot of mine - running with Ambiance.
DISTRIB_DESCRIPTION=""Ubuntu 18.04.2 LTS""
4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1725588,2019-02-13 15:57:05 UTC,"Yes - still there - but theme dependent.  Ambiance and Radiance are the same as in your image.
The Arcs (dark, darker) work, though the borders are hard to see.
High Contrast works."
1725588,2019-02-13 09:21:57 UTC,"Is this still an issue with Thunderbird 60.4, the currently supported version?"
1725588,2018-05-09 06:55:52 UTC,Setting regression bug to critical status
1725588,2018-05-09 06:55:09 UTC,What is the last version that still worked fine?
1725588,2017-10-21 10:40:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725588,2019-02-13 10:55:15 UTC,"Hey Paul,"
1725593,2017-11-01 16:30:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725604,2018-04-14 11:36:36 UTC,"After some network manager updates, my connection DSL/PPPoE is not being recognized correctly."
1725604,2017-10-21 08:50:59 UTC,"StacktraceTop:
 net_device_get_find_connection (device=0x55dd0d1a2c20) at net-device.c:165
 device_off_toggled (sw=<optimized out>, pspec=<optimized out>, device_mobile=0x55dd0d1a2c20) at net-device-mobile.c:456
 g_closure_invoke (closure=0x55dd0d2a4f40, return_value=0x0, n_param_values=2, param_values=0x7ffed7f73b60, invocation_hint=0x7ffed7f73ae0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55dd0c7fb520, detail=detail@entry=1018, instance=instance@entry=0x55dd0d22c1f0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffed7f73b60) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x55dd0d22c1f0, signal_id=<optimized out>, detail=1018, var_args=var_args@entry=0x7ffed7f73d30) at ../../../../gobject/gsignal.c:3391"
1725604,2017-10-23 20:55:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725604,2018-04-13 10:07:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725609,2017-10-27 10:35:00 UTC,"Brian, good question.  I assumed it was the upgrade but it wansn't.  I've done some digging and found this:"
1725609,2017-10-26 20:22:33 UTC,How did you go about installing the lowlatency kernel?
1725609,2017-12-27 04:17:27 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1725609,2017-10-26 20:21:10 UTC,"Oh, I think its because you did not have the lowlatency headers installed e.g. linux-headers-lowlatency."
1725609,2017-10-26 20:19:18 UTC,This is strange as from your log files we can see that the linux-headers-generic package is installed and the new linux-headers package gets installed (VarLogDistupgradeAptterm.log).
1725609,2017-10-23 08:13:51 UTC,"Thanks Geoff, your workaround worked for me!"
1725609,2017-10-21 10:58:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725609,2017-10-21 11:01:59 UTC,Thank you so much! Your workaround has helped me! As I remember the same situation was when I had upgraded from 16.04 to 17.10
1725615,2017-10-21 15:25:34 UTC,I presume you've run `sudo apt-get update` and refreshed your repository data *before* trying to install?
1725615,2017-10-21 15:26:57 UTC,"As you are using the PPA and not the repos (I can tell both by version numbers *and* your `apt-cache` output), I've marked this as ""Invalid"" against the Ubuntu repositories' nginx version, and repointed it to the appropriate project here on Launchpad."
1725615,2017-10-22 04:30:28 UTC,"I removed `deb http://ppa.launchpad.net/nginx/stable/ubuntu zesty main` from `/etc/apt/sources.list` (that would, presumably, switch ppa off?), ran `sudo apt update` and then `sudo apt install nginx-extras`. Here is the result:
```
The following packages have unmet dependencies:
 nginx-extras : Depends: libnginx-mod-http-auth-pam (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-http-cache-purge (= 1.12.1-0ubuntu2) but it is not going to be installed
                Depends: libnginx-mod-http-dav-ext (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-http-echo (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-http-fancyindex (= 1.12.1-0ubuntu2) but it is not going to be installed
                Depends: libnginx-mod-http-geoip (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-http-headers-more-filter (= 1.12.1-0ubuntu2) but it is not going to be installed
                Depends: libnginx-mod-http-image-filter (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-http-lua (= 1.12.1-0ubuntu2) but it is not going to be installed
                Depends: libnginx-mod-http-perl (= 1.12.1-0ubuntu2) but it is not going to be installed
                Depends: libnginx-mod-http-subs-filter (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-http-uploadprogress (= 1.12.1-0ubuntu2) but it is not going to be installed
                Depends: libnginx-mod-http-upstream-fair (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-http-xslt-filter (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-mail (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: libnginx-mod-nchan (= 1.12.1-0ubuntu2) but it is not going to be installed
                Depends: libnginx-mod-stream (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
                Depends: nginx-common (= 1.12.1-0ubuntu2) but 1.12.1-0+zesty0 is to be installed
E: Unable to correct problems, you have held broken packages.
```"
1725615,2017-10-22 04:33:13 UTC,"`apt-cache policy nginx-extras` now that I removed PPA repository reports:
```
nginx-extras:
  Installed: (none)
  Candidate: 1.12.1-0ubuntu2
  Version table:
     1.12.1-0ubuntu2 500
        500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
```"
1725620,2017-10-21 22:43:59 UTC,"> I expect the tab bar to be hidden when only one tab is open.
"
1725620,2017-10-21 22:49:19 UTC,... a correct sentence*.
1725620,2017-10-26 19:46:27 UTC,Thanks for reminding me about the hidden settings. For future reference: `org.gnome.Terminal.Legacy.Settings.tab-policy`
1725621,2017-10-21 22:53:12 UTC,See https://git.gnome.org/browse/gnome-terminal/commit/?id=10e164d and follow the links from there if you're interested in the details.
1725621,2017-10-21 22:45:27 UTC,It's unfortunately temporarily disabled due to an underlying GTK+ bug which might cause a crash.
1725622,2017-10-21 10:12:18 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1500179, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1725622,2017-10-21 11:01:32 UTC,"The bug https://bugs.launchpad.net/bugs/1500179 does not exist (any more).
Also, this crash happened right after upgrading to Ubuntu 17.10.  qtcreator worked find on the same machine using Ubuntu 17.04 and 16.10."
1725622,2017-10-21 11:17:54 UTC,Problem solved:
1725625,2017-10-21 10:26:21 UTC,"StacktraceTop:
 ?? ()
 brisk_menu_window_filter_section (item=<optimized out>, self=0x55c85fa30360) at src/frontend/menu-search.c:122
 brisk_menu_window_filter_apps (row=<optimized out>, v=<optimized out>) at src/frontend/menu-search.c:168
 gtk_list_box_apply_filter (box=0x55c85f9ee3c0, row=0x55c85fd2c4c0) at ././gtk/gtklistbox.c:2243
 gtk_list_box_insert (box=0x55c85f9ee3c0, child=<optimized out>, position=<optimized out>) at ././gtk/gtklistbox.c:2934"
1725625,2017-10-21 15:40:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725625,2018-04-07 02:09:38 UTC,Also affects 18.04
1725628,2018-02-21 00:10:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725631,2017-10-23 06:25:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725644,2017-11-16 07:55:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725667,2017-10-23 20:47:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725667,2017-10-24 13:37:41 UTC,Thanks
1725681,2020-11-22 09:46:28 UTC,"Dear Kees van Iwaarden,"
1725681,2020-11-22 09:48:08 UTC,Look if problem is still an issue.
1725681,2020-12-03 07:14:39 UTC,Closing bug report due to bug's nature (seems it was an amavisd-new bug) and no reply from bug reporter.
1725681,2020-12-03 07:15:49 UTC,Closed
1725686,2017-10-21 16:23:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1725686,2017-10-22 12:21:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725686,2020-01-24 10:10:08 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725687,2017-10-21 13:26:10 UTC,"StacktraceTop:
 __GI___pthread_mutex_lock (mutex=mutex@entry=0x139) at ../nptl/pthread_mutex_lock.c:67
 boost::asio::detail::posix_mutex::lock (this=<optimized out>) at /usr/include/boost/asio/detail/posix_mutex.hpp:52
 boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>::scoped_lock (m=..., this=<synthetic pointer>) at /usr/include/boost/asio/detail/scoped_lock.hpp:46
 boost::asio::detail::epoll_reactor::start_op (this=0x55abe65afb80, op_type=op_type@entry=0, descriptor=0, descriptor_data=@0x55abe6542fb8: 0x111, op=op@entry=0x7f3af0008440, is_continuation=<optimized out>, allow_speculative=true) at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:217
 boost::asio::detail::reactive_socket_service_base::start_op (this=0x7f3b2cf5dca0 <main_arena+128>, impl=..., op_type=0, op=0x7f3af0008440, is_continuation=<optimized out>, is_non_blocking=<optimized out>, noop=false) at /usr/include/boost/asio/detail/impl/reactive_socket_service_base.ipp:214"
1725690,2017-10-21 17:31:29 UTC,I too have same issue
1725690,2017-10-22 21:26:18 UTC,Same problem here. No reboot possible after install and no poweroff from the desktop. Both due to wpasupplicant.
1725690,2017-10-23 10:06:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725690,2017-10-23 11:23:39 UTC,Possible duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317.
1725690,2017-10-25 09:09:10 UTC,"Solved this by installing firmware-5.bin_WLAN.TF.1.0-00002-QCATFSWPZ-5
instead of firmware-5.bin_CNSS.TF.1.0-00267-QCATFSWPZ-1
in /lib/firmware/ath10k/QCA9377/hw1.0 and then reboot."
1725690,2017-10-28 22:06:15 UTC,I confirm that remco's solution seems to be working.
1725690,2017-10-29 10:16:14 UTC,Installing kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.10/ fixed the issue for me.
1725703,2017-11-19 22:28:29 UTC,"Here's a (probably bad) implementation I can come up with. There's still no seperation between the config, data and cache files, but it's better than nothing. It works in my simple tests and moves the folder to the new location if found in home and built with XDG.
The compatibility part look a bit awkward, probably because I don't know better."
1725703,2017-11-04 11:35:53 UTC,"> XDG does too. The average user will not care where the settings are. ...
"
1725703,2017-11-20 15:00:14 UTC,"You're right, moving the folder was a bad idea. Now the patch looks for an already existing folder and uses it if it's available. So the dotfolder is always the default.
To prevent errors on Mac and Windows I've excluded them in the CMakeLists (I hope that works that way). There shouldn't break anything on these two operating systems but I can't test it and make sure.
I've tested this again on Linux and it seems to work like expected in my little testing."
1725703,2017-11-20 19:48:45 UTC,"+#elif USE_XDG
+ homedir_(FileSystem::get_homedir()),
 #else"
1725703,2019-09-16 14:41:49 UTC,Migrated to https://github.com/widelands/widelands/issues/3217
1725703,2017-11-01 19:42:11 UTC,"> This adds more complexity to the user, than it will solve. If the user set this to the profile or as standard for every program, then it will only move the home directory elsewhere, but nothing improvable has been added.
"
1725703,2017-11-20 20:02:22 UTC,"It already has a widelands subdirectory. I had to pull it in filesystem.cc because I have no idea how to check for the home directory in application.cc in a elegant way to distinguish between ""/.widelands"" and ""/widelands""."
1725703,2017-11-01 14:17:37 UTC,"I wouldn't be against it if somebody found an elegant implementation for this for all OSses, but I won't be spending any time on this myself. I have a long list of UI, game engine and documentation improvements I'd like to implement first ;)"
1725703,2017-11-20 07:24:00 UTC,"I'm worried about how to support a patch like that - for example, if people compile with the new option and then forget that they've done it, their files won't be moved back to the default .widelands dir the next time that they compile with our compile script."
1725703,2017-10-23 19:09:50 UTC,"> - No predefined paths. The user can decide where his or her data is located.
"
1725703,2017-10-22 13:10:31 UTC,"I understand your concern, but XDG has a few key advantages over dotfiles.
- No predefined paths. The user can decide where his or her data is located.
- No cluttered home directory. Some selectors will automatically show dotfiles, finding the files you want will be easier.
- A shared storage location for data. Application data does not have to be searched for, as these are no longer located in different places. This also benefits a backup.
- Resetting the settings and keeping the application data at the same time becomes easier, as there is a clear separation.
Here's some reading about it:
- https://wiki.gnome.org/Initiatives/GnomeGoals/XDGConfigFolders
- https://ploum.net/207-modify-your-application-to-use-xdg-folders/"
1725703,2017-10-22 09:07:42 UTC,"> :). https://xkcd.com/927/
"
1725703,2017-10-22 08:13:01 UTC,"If it was only for config files, I would not care, but for savegames, replay and even wai files, it would  mean obscure location and few clicks more to get there..."
1725703,2017-10-31 23:24:52 UTC,"> Besides, setting $HOME to any other directory is fine, it is only used for initial location of your shell after login (which can be overwridden in your .profile) and the location of your .dotfiles. That is also what HOME is meant to be.
"
1725703,2017-10-21 18:37:17 UTC,"> On the other side the XDG-standard tries to apply, well, a standard.
"
1725703,2017-10-21 18:13:13 UTC,I don't like the splitting of an applications data too.
1725703,2017-10-21 17:31:15 UTC,"I forgot some stuff: XDG does not transition well to Mac OS or Windows, needs documenting since it is much more complex and can easily be expressed using symlinks."
1725703,2017-10-21 17:29:48 UTC,"I am against this. Here are my 2c: First XDG is an opinion - I for one much prefer pure dotfile directories instead of smearing everything across an entire tree. Second, Widelands has done dotfiles for > 15 years, like vim and emacs - it works well and is well tested. Third, the pain of implementing this and transitioning old directories over is substantial and the gains are minimal."
1725707,2020-11-10 03:06:44 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1725707,2018-01-22 01:28:27 UTC,"Reference:
https://github.com/novnc/noVNC/issues/431#issuecomment-71883085"
1725707,2017-10-23 08:46:19 UTC,This is nothing specific to websockets AFAIK. Even using regular VNC QEMU doesn't try to dynamically throttle data / quality settings.
1725707,2017-10-23 12:14:28 UTC,"NB, if websockify crashes, then that is a serious flaw in websockify - it shouldn't read an unbounded amount of data from QEMU, if it is unable to send it onto the client.  If websockify stopped reading data from QEMU, then QEMU would in turn stop sending it once the TCP buffer was full"
1725708,2017-10-23 08:39:58 UTC,"unsure it has to do with the placement of the menu though, the item shouldn't activate when you unpress the button"
1725708,2018-11-12 07:40:12 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725708,2017-11-28 19:13:55 UTC,"For me, this also contains the file manager (nautilus)."
1725708,2017-10-23 23:10:09 UTC,"Atm I'd put 'blame' on ubuntu themes (ambiance, radiance) while in wayland session & maybe only with gedit.
If using awaita theme this won't occur even if the bubble menu opens slightly outside header bar.
(- it seems the actual cursor position when initiating the r. click will affect where the top of the bubble menu is."
1725708,2017-10-23 08:58:45 UTC,"But the menu is definitely placed incorrectly, only for Gedit."
1725708,2017-10-23 08:58:27 UTC,"Now that you mention it, I'm not sure. It's not uncommon for some toolkits to be designed to activate a popup-menu item on button release. I didn't consider that part a bug."
1725708,2017-10-23 08:39:21 UTC,That's the same than https://bugzilla.gnome.org/show_bug.cgi?id=787139 upstream right?
1725708,2017-10-22 13:43:05 UTC,"Amending last comment, this does occur but only in wayland"
1725708,2017-10-23 05:23:36 UTC,The problem is that you don't see you're actually selecting Minimize (try holding the right button down for a while). Duplicate of bug 1717446...
1725708,2017-10-22 17:28:31 UTC,"As a workaround, if you keep the right-click pressed until you move the mouse cursor over another item in the menu, it works."
1725708,2017-10-22 14:18:42 UTC,"Sorry, forgot that I don't use wayland in practice as it's not close to ready but should when testing.
To note: this doesn't occur in a gnome session where the context menu is opened inside the header bar so maybe add ubuntu-session."
1725708,2017-10-22 13:46:27 UTC,Be more kindly next time.
1725708,2017-10-22 13:23:17 UTC,"Works absolutely fine here, maybe reporter needs a new mouse or better control of his finger on a touchpad, should be marked as invalid."
1725708,2017-10-23 05:36:45 UTC,"Sorry, that makes two separate bugs. This is no longer a duplicate. But see also bug 1717446."
1725711,2017-10-21 14:44:10 UTC,"StacktraceTop:
 zip_find_trailer (sig=101010256, size=22, zip=0x5603c1006030) at gsf-infile-zip.c:179
 zip_read_dirents (zip=0x5603c1006030) at gsf-infile-zip.c:400
 zip_init_info (zip=0x5603c1006030) at gsf-infile-zip.c:495
 gsf_infile_zip_constructor (type=<optimized out>, n_construct_properties=<optimized out>, construct_params=<optimized out>) at gsf-infile-zip.c:847
 g_object_new_with_custom_constructor (n_params=1, params=0x7ffce764ecc0, class=0x5603c1021690) at ../../../../gobject/gobject.c:1715"
1725713,2017-10-21 14:59:39 UTC,"StacktraceTop:
 _int_malloc (av=av@entry=0x7fccac7adc20 <main_arena>, bytes=bytes@entry=12) at malloc.c:3611
 __libc_calloc (n=n@entry=1, elem_size=elem_size@entry=12) at malloc.c:3438
 g_malloc0 (n_bytes=n_bytes@entry=12) at ../../../../glib/gmem.c:124
 gtk_tree_path_to_string (path=path@entry=0x5601a25ad8a0) at ././gtk/gtktreemodel.c:743
 gtk_cell_area_real_apply_attributes (area=<optimized out>, tree_model=<optimized out>, iter=0x5601a23b7920, is_expander=<optimized out>, is_expanded=<optimized out>) at ././gtk/gtkcellarea.c:1291"
1725713,2017-11-23 13:12:02 UTC,more likely an isssue in gtk+3.0 or it's python bindings
1725718,2018-03-15 17:00:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725721,2018-01-17 20:05:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725727,2018-05-15 14:50:08 UTC,This change was made by a bot.
1725728,2017-10-21 15:27:06 UTC,"Help me solve this,it affects installation of packages too in that they are installed half and its also making my machine hung a lot"
1725728,2017-10-21 17:19:15 UTC,What is this?
1725751,2017-10-21 17:09:19 UTC,"StacktraceTop:
 _g_file_is_local (file=file@entry=0x0) at glib-utils.c:1287
 fr_command_extract_files (base=<optimized out>, file_list=0x0, destination=0x0, base_dir=0x0, skip_older=1, overwrite=1, junk_paths=-536723952, password=0x0, cancellable=0x55d0e17696a0, callback=0x55d0e001c490 <archive_extraction_ready_cb>, user_data=0x55d0e1abc7b0) at fr-command.c:2374
 _fr_window_archive_extract_from_edata (window=0x55d0e19164f0, edata=0x55d0e1abc7b0) at fr-window.c:6633
 _fr_window_ask_overwrite_dialog (odata=odata@entry=0x55d0e1c4bc80) at fr-window.c:6833
 query_info_ready_for_overwrite_dialog_cb (source_object=<optimized out>, result=0x55d0e1a834f0, user_data=0x55d0e1c4bc80) at fr-window.c:6741"
1725762,2017-12-10 14:48:41 UTC,Many users are affected with this bug - see search results on AskUbuntu https://askubuntu.com/search?q=tsc_deadline+errata+0x52+is%3Aquestion
1725762,2017-10-27 17:36:56 UTC,Just tried with the Ubuntu Mate Distro and I get the same errors.
1725762,2017-10-24 10:35:32 UTC,"Just as a further check, I tried writing the image via Rufus & Etcher and got the same result with with both images.  I also tried re-downloading the image."
1725762,2017-10-23 19:33:54 UTC,17.04 Tested and loads fine.
1725762,2017-10-23 18:50:33 UTC,I will try 17.04 and let you know
1725762,2017-10-23 18:02:17 UTC,"Are you able to boot prior releases on this same machine?  Maybe give Zesty a try:
http://releases.ubuntu.com/"
1725762,2017-10-23 17:40:15 UTC,I'm unable to add log files as these errors are happening at start-up
1725762,2017-10-23 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1725762,2017-10-22 00:23:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1725762,2017-10-23 18:40:27 UTC,Hi Joseph. 16.04 boots OK. Peter
1725779,2019-02-18 16:17:58 UTC,Have the same problem when trying to use Fortinet VPN. The CLI (openfortivpn) works fine.
1725779,2018-11-30 14:57:06 UTC,I can confirm this bug. When using the nm-applet there is nog problem.
1725779,2018-11-30 15:02:11 UTC,I had a fresh Ubuntu 18.04 install and was effected by this bug. Running
1725779,2019-02-15 14:12:30 UTC,I tried
1725779,2019-02-15 15:15:58 UTC,"> sudo dpkg-reconfigure network-manager-pptp-gnome
> on my 18.04 instance with no success.
> running openvpn directly off the command line however does work.
"
1725779,2019-02-15 15:52:18 UTC,I found this to work with openvpn via the network manager:
1725779,2019-03-05 14:19:23 UTC,"I can confirm this is still an issue with ubuntu 18.04. I have both the network-manager-openvpn and network-manager-openvpn-gnome. The DNS issues are still an issue on the client side. I know this isn't my openvpn server (running on pfsense) or config files as the same config files on Windows and MACOS work and connect with no issues. This needs to be fixed since, I, the IT guy use Ubuntu 18.04, lol."
1725779,2019-12-11 15:57:12 UTC,@simongkelly if the symptom was fixed by a reboot then it is not the same issue
1725779,2019-12-11 15:59:46 UTC,"Please ignore my previous comment, I was thinking of the wrong bug!"
1725779,2019-04-22 14:06:39 UTC,"Confirming that the bug still happens on 19.04. I'm using network-manager-vpnc-gnome which has this issue. However, nm-applet does work."
1725779,2019-09-01 14:45:37 UTC,I'm also facing the same issue.
1725779,2019-09-01 14:49:29 UTC,"Just for a sanity check, I rebooted and I can now connect without passing by the nm-applet..."
1725779,2019-12-11 08:21:18 UTC,I had the same issue on 19.10 with network-manager-openconnect-gnome. It worked with nm-applet. I also found that a reboot fixed the issue.
1725779,2018-09-10 15:24:40 UTC,I'm having this problem with a clean install. I have all the following installed:
1725779,2019-03-07 14:14:49 UTC,Should we perhaps make the GNOME network setup tool depend on
1725779,2018-08-22 11:20:46 UTC,"It's very strange, but I've just execute apt update && apt upgrade, reboot. And now vpnc works fine!
My issue solved"
1725779,2018-06-01 15:59:30 UTC,Same here on 18.04
1725779,2018-08-22 10:47:13 UTC,I have clean installed 18.04 and openvpn works well. But only problem with cisco vpn. It's not connection with Ubuntu panel. But it works with nm-applet
1725779,2017-10-21 18:12:36 UTC,"FYI - anyone who needs their vpn to work right now, run nm-applet and launch from there instead."
1725779,2017-12-08 05:03:11 UTC,"Thanks Jason, I have the same problem on Ubuntu 17.10 as well. Launching VPN from nm-applet got my VPN connection working again."
1725779,2018-01-22 11:25:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725779,2018-05-02 19:23:58 UTC,Ubuntu 18.04
1725779,2018-08-22 10:48:29 UTC,"network-manager-vpnc
network-manager-vpnc-gnome"
1725779,2018-07-31 15:27:03 UTC,Same issue here 18.04 with latest updates
1725779,2018-08-15 08:56:24 UTC,Same issue 18.04
1725779,2018-05-03 21:08:24 UTC,"I am on Ubuntu 18.04, fresh install using network-manager-openvpn"
1725779,2018-08-16 15:48:03 UTC,"I'm not sure it's network-manager bug.
OpenVPN works fine, but vpnc is broken.
But in the same time it's working ok using nm-applet, so I think it's gnome bug"
1725779,2018-08-19 09:45:49 UTC,"Does installing network-manager-pptp-gnome help?
I had the same issue using openvp and installing network-manager-openvpn-gnome fixed it (though I still don't get the padlock shown, but it does connect)."
1725779,2018-08-21 10:10:52 UTC,"Has anyone tried this (or confirmed that they already have network-manager-pptp-gnome and network-manager-openvpn-gnome installed)?  It has fixed it for me, I suspect that is an issue with the upgrader.  A fresh install of 18.04 has it, but my upgraded system did not.
I do see, though, that one person with the problem has already got it installed so maybe there is more than one issue here."
1725779,2018-08-21 10:58:35 UTC,"I'm *not* seeing this issue on a clean&updated install of 18.04, while I did on an old install (upgraded every 6 months from 13.04 to 17.10/18.04). Haven't tried without updating (why would you)."
1725779,2018-08-21 12:39:27 UTC,"@geez your first para is exactly what I have seen. No problem with clean install of 18.04, but there were problems with an system upgraded from 17.10.  My comment about the upgraded system was ambiguous, it is on a system upgraded from 17.10 that I see the problem.  My suggestion is that is the upgrader that takes the system from 17.10 to 18.04 that is the problem, in not installing those packages."
1725779,2018-08-21 12:57:28 UTC,"@Colin sorry for the confusion. Indeed I (also) have the following packages installed:
i   network-manager-openvpn
i   network-manager-openvpn-gnome
i   network-manager-pptp
i   network-manager-pptp-gnome
The system that works as expected is the clean 18.04, the old installation no longer exists."
1725779,2018-08-16 15:22:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725783,2017-10-21 18:29:46 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x558871f1cc03 ""../src/nautilus-file.c"", line=line@entry=720, func=func@entry=0x558871f1f4a0 <__func__.65446> ""nautilus_file_get_internal"", message=message@entry=0x55887408e5e0 ""assertion failed: (location != NULL)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x558871f1cc03 ""../src/nautilus-file.c"", line=line@entry=720, func=func@entry=0x558871f1f4a0 <__func__.65446> ""nautilus_file_get_internal"", expr=expr@entry=0x558871f32b53 ""location != NULL"") at ../../../../glib/gtestutils.c:2459
 nautilus_file_get_internal (location=location@entry=0x0, create=create@entry=1) at ../src/nautilus-file.c:720
 nautilus_file_get (location=location@entry=0x0) at ../src/nautilus-file.c:787
 open_location_cb (view=0x558874203550, location=0x0, open_flags=(GTK_PLACES_OPEN_NORMAL | GTK_PLACES_OPEN_NEW_TAB | GTK_PLACES_OPEN_NEW_WINDOW)) at ../src/nautilus-places-view.c:96"
1725783,2017-10-24 16:37:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725803,2018-03-02 14:56:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725807,2018-05-18 07:45:15 UTC,"ignore that comment, other the theme was fixed and the icon is right in e.g nautilus"
1725807,2018-05-18 07:42:45 UTC,"the issue you describe seems in fact a theme ""bug"" like bug #1282897?"
1725807,2018-05-18 05:45:38 UTC,"@6th: the request was to report this upstream, however I have just tested it with system monitor 3.28.2 on Fedora, and it works just as it should: with upside down pyramid the highest cpu% is on top, the lowest on the bottom, and with normal pyramid the highest cpu usage is the last."
1725807,2018-05-18 00:57:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725807,2017-10-23 20:29:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725807,2018-05-18 01:19:36 UTC,"I also have this using:
Ubuntu 18.04LTS
gnome-system-monitor/bionic 3.28.1-1 amd64"
1725813,2017-10-21 19:55:15 UTC,Thanks for the report.
1725814,2017-10-24 04:46:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725814,2017-10-24 13:35:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725821,2017-10-23 21:05:02 UTC,I'm setting the bug status back to Incomplete because this should be fixed for Artful but someone needs to write a test case for it. Or we can fix it along with mutter 3.26.2 whenever that is released.
1725821,2017-10-26 22:11:34 UTC,"This fix breaks video playback in at least Firefox.  After installing the test package, playing fullscreen video in Firefox results in lots of tearing."
1725821,2017-10-27 16:51:32 UTC,This bug was fixed in the package mutter - 3.26.1-6
1725826,2017-11-20 02:49:50 UTC,"@stinger: Get a crash when opening a link with Rhythmbox. This is tracked in https://bugzilla.gnome.org/show_bug.cgi?id=790586. But, the crash mentioned in the bug description is different from that."
1725826,2017-11-19 23:56:54 UTC,Still cannot reproduce. Is it on 17.10 ? Do you have rhythmbox already open while clicking the link in firefox ? More information might help.
1725826,2017-11-16 00:38:12 UTC,"Yes, its reproducible with Firefox.
The crash occurred if i open the link with Rhythmbox, which was the default.
Now my default is Video(Totem) ;-)"
1725826,2017-11-02 14:05:40 UTC,No luck reproducing this on 17.10.
1725826,2017-10-21 20:51:42 UTC,"StacktraceTop:
 gtk_tree_view_get_column (tree_view=tree_view@entry=0x55b5d9bdc7e0, n=n@entry=16) at ././gtk/gtktreeview.c:12343
 _gtk_tree_view_accessible_changed (treeview=treeview@entry=0x55b5d9bdc7e0, tree=0x7f69800243e0, node=0x55b5dadf9cf0) at ././gtk/a11y/gtktreeviewaccessible.c:1700
 gtk_tree_view_row_changed (model=0x55b5db0e5c90, path=0x55b5db4c2560, iter=0x55b5db251780, data=0x55b5d9bdc7e0) at ././gtk/gtktreeview.c:9012
 g_closure_invoke (closure=0x55b5dae83170, return_value=0x0, n_param_values=3, param_values=0x7ffd417af8e0, invocation_hint=0x7ffd417af860) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55b5d98f0f40, detail=detail@entry=0, instance=instance@entry=0x55b5db0e5c90, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffd417af8e0) at ../../../../gobject/gsignal.c:3635"
1725826,2017-10-23 13:44:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1725826,2017-10-23 00:11:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725826,2017-10-23 13:44:36 UTC,Did you use the filter feature at the time? Was it still updating the view when you clicked?
1725829,2018-08-13 20:02:43 UTC,"I dramatically reduced the size & scope of the backup I was performing and
the issue went away (as anticipated). So I no longer have a replicable test
case. Consequently, I don't know if the underlying issue has been fixed..
sorry!"
1725829,2020-04-18 09:56:02 UTC,It's not fixed.
1725829,2017-11-23 00:04:33 UTC,"With this patch, duplicity at least wrote the full .sigtar.gz file
(2630787933 bytes), and reading it with ""tar tvfz"" produces no error.
I did not yet try to make an incremental updated on top of it."
1725829,2020-06-18 04:17:19 UTC,[Expired for Duplicity because there has been no activity for 60 days.]
1725829,2018-08-13 19:51:29 UTC,"Has this bug been fixed in a later duplicity version? I'm running into the same error on 0.7.11, also with a signature tar file of similar size."
1725829,2020-04-18 12:44:53 UTC,Please upgrade to the current version of duplicity.  This will assure that any bugs fixed since your release are available and may fix your issue.
1725829,2018-02-02 01:15:52 UTC,"One shouldn't perform calculation with ""None"".
How could I have overlooked this. I hope it is now fixed."
1725829,2017-11-20 01:45:21 UTC,I found the following passage in dup_temp.py:
1725829,2018-01-31 10:40:31 UTC,"Yes, I have recently made an incremental backup on top of the one built by the
patch.
The backup went through.
(I have not yet checked whether I can restore from it.)"
1725829,2017-10-27 02:04:39 UTC,I did a little more digging. It appears that the sigtar for the full backup is corrupt:
1725829,2017-11-18 00:50:10 UTC,"I have had the same problem, for about a year now. It used to work
previously. (I now had to switch from incremental backups
to full backups, because duplicity would crash on incremental backups.)"
1725829,2018-02-01 23:37:19 UTC,"full backup with the patch failed for me, haven't diagnosed yet."
1725829,2017-11-18 18:26:00 UTC,"My file size was very close to 2**31 as well, but I have VOLSIZE=2048 so I figured that 2G was an expected number. Haven't dug in there."
1725829,2018-01-30 21:31:34 UTC,Have you managed to make an incremental build on top of the patch? I've applied the patch locally and am testing it.
1725836,2018-08-17 04:48:39 UTC,That log appears to be from XFCE which you said does not exhibit the bug.
1725836,2018-08-17 05:28:02 UTC,"The bug shows up now even in xfce4. It did not earlier with 17.04. Now all
the managers show up the bug."
1725836,2018-08-17 12:31:44 UTC,Without 3rd monitor plugged in:
1725836,2018-08-18 13:07:38 UTC,"Daniel, Here are three more photos. Sent individually because of size
limitations."
1725836,2018-08-18 13:08:43 UTC,"On Sat, Aug 18, 2018 at 9:07 AM Peter Wallbridge <email address hidden>
wrote:"
1725836,2018-08-18 13:09:53 UTC,"On Sat, Aug 18, 2018 at 9:08 AM Peter Wallbridge <email address hidden>
wrote:"
1725836,2018-08-20 02:33:55 UTC,"Thanks. Comment #33 seems to be the most important one now. If the bug occurs in XFCE as well then this is not a gnome-shell bug. Instead it should be assigned to xorg-server, or the driver, or the kernel."
1725836,2018-08-20 03:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1725836,2018-08-20 11:42:44 UTC,Thanks Daniel. Yes it also shows up on xfce
1725836,2018-08-20 12:02:40 UTC,apport information
1725836,2018-08-20 12:02:41 UTC,apport information
1725836,2018-08-20 12:02:43 UTC,apport information
1725836,2018-08-20 12:02:46 UTC,apport information
1725836,2018-08-20 12:02:47 UTC,apport information
1725836,2018-08-20 12:02:49 UTC,apport information
1725836,2018-08-20 12:02:50 UTC,apport information
1725836,2018-08-20 12:02:51 UTC,apport information
1725836,2018-08-20 12:02:52 UTC,apport information
1725836,2018-08-20 12:02:54 UTC,apport information
1725836,2018-08-20 12:02:55 UTC,apport information
1725836,2018-08-20 12:02:56 UTC,apport information
1725836,2018-08-20 12:02:57 UTC,apport information
1725836,2018-08-20 12:02:59 UTC,apport information
1725836,2018-08-20 12:03:01 UTC,apport information
1725836,2018-08-20 12:03:02 UTC,apport information
1725836,2018-08-20 12:03:03 UTC,apport information
1725836,2018-08-20 12:03:05 UTC,apport information
1725836,2018-08-17 04:41:00 UTC,"When I use ubuntu on wayland, the third screen is displayed, but the second
screen is not and there is no keyboard or mouse  input. Have to reboot with
the screen unplugged."
1725836,2018-08-17 04:29:30 UTC,"Nothing normally
The following with the third monitor plugged in:
peterw@simulator:~$ journalctl -f
-- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline ""1024x768""x0.0   78.75  1024 1040 1136 1312  768 769
772 800 +hsync +vsync (60.0 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline ""1024x768""x0.0   65.00  1024 1048 1184 1344  768 771
777 806 -hsync -vsync (48.4 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline ""800x600""x0.0   49.50  800 816 896 1056  600 601 604
625 +hsync +vsync (46.9 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline ""1152x864""x0.0  108.00  1152 1216 1344 1600  864 865
868 900 +hsync +vsync (67.5 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline ""1280x1024""x0.0  108.00  1280 1328 1440 1688  1024 1025
1028 1066 +hsync +vsync (64.0 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline ""1920x1080""x60.0  172.80  1920 2040 2248 2576  1080
1081 1084 1118 -hsync +vsync (67.1 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (EE)
RADEON(0): failed to set mode: Invalid argument
Aug 17 00:26:53 simulator xfsettingsd[1902]: Failed to configure CRTC 118.
Aug 17 00:26:53 simulator kernel: [drm:atombios_crtc_mode_fixup [radeon]]
*ERROR* unable to allocate a PPLL
Aug 17 00:26:53 simulator kernel: [drm:drm_crtc_helper_set_config
[drm_kms_helper]] *ERROR* failed to set mode on [CRTC:41:crtc-1]
Aug 17 00:28:10 simulator xfce4-terminal[28461]:
gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed"
1725836,2018-08-20 12:02:44 UTC,apport information
1725836,2018-08-17 01:57:24 UTC,Going back to your JournalErrors.txt:
1725836,2018-08-17 01:59:05 UTC,"Separately, please also try clicking the cog wheel button on the login screen and selecting:"
1725836,2017-10-23 06:46:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1725836"
1725836,2017-10-23 12:22:44 UTC,apport information
1725836,2017-10-23 12:22:45 UTC,apport information
1725836,2017-10-23 12:22:47 UTC,apport information
1725836,2017-10-23 12:22:48 UTC,apport information
1725836,2017-10-23 12:22:50 UTC,apport information
1725836,2017-10-24 05:06:13 UTC,What exactly do you see on the third display? Is it off/sleeping?
1725836,2017-10-24 12:24:04 UTC,Hi Daniel
1725836,2017-10-26 16:10:47 UTC,SEBASTIEN
1725836,2017-10-27 02:14:05 UTC,"Peter, we're here to help. And Sebastien is right... The fastest way to a fix for you now is for you to report the bug directly on the Gnome bug tracker:  https://bugzilla.gnome.org/"
1725836,2017-10-27 05:49:19 UTC,Did it. I hope I did it correctly.
1725836,2017-10-27 06:20:53 UTC,Thanks. Perhaps we jumped the gun though...
1725836,2017-10-27 06:35:36 UTC,I see both.
1725836,2017-10-26 14:48:55 UTC,"The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725836,2018-08-16 15:28:20 UTC,"On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge <email address hidden>
wrote:"
1725836,2018-08-17 01:50:54 UTC,GPUs:
1725836,2017-10-27 07:04:37 UTC,This could be related to OpenGL texture sizes or something similar. Unity7 (Compiz) has workarounds to avoid that limitation. And Xfce avoids it by not using hardware accelerated compositing at all (last I checked). It's not surprising if only Gnome Shell hits a problem like this...
1725836,2018-08-16 15:27:57 UTC,"On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge <email address hidden>
wrote:"
1725836,2018-08-16 15:27:32 UTC,Here are three photos that might help.
1725836,2018-08-16 11:07:35 UTC,1... Output of xrandr and lspci
1725836,2018-08-16 02:33:08 UTC,Please also run:
1725836,2018-08-16 02:35:18 UTC,It appears you already provided 'xrandr' output on bugzilla. Is this still correct?
1725836,2018-08-15 10:55:16 UTC,"I am using 18.10 the bug still exists.All three displays can be displayed depending on enabling, but never at once."
1725836,2018-08-15 10:44:31 UTC,I am using 18.04 and bug still exists
1725836,2018-08-15 04:58:14 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725836,2017-10-27 07:27:23 UTC,Thanks for the info. The answer is yes
1725836,2018-08-16 02:32:23 UTC,"Great, thanks. Can you please run these two commands on the machine and send us their outputs?"
1725840,2018-01-07 00:22:32 UTC,Ping...
1725840,2017-12-24 13:43:52 UTC,Fix it with the
1725840,2017-12-28 10:25:50 UTC,"Been affected by this since my fresh 17.10 install (not an upgrade, but a clean install)."
1725840,2017-12-28 14:27:11 UTC,"This package is not used in new installs of 17.10, by design.  If you are seeing wrong behavior of /etc/resolv.conf on a new install, that is not this bug. Please file a separate bug report against the systemd package with a description of what you are seeing so that we can help you."
1725840,2018-01-08 08:56:59 UTC,"In my case it works well with WiFi network, But the Ethernet network is having the issue. In same port other machine works, but not mine. Earlier with 16:04 it used to work."
1725840,2018-12-02 20:15:06 UTC,"On Sun, Dec 02, 2018 at 11:59:42AM -0000, Paul Hewlett wrote:

> I recently did an apt update on my laptop running cosmic. DNS was very
> slow and I got the degraded to UDP message. Investigation showed that
> /etc/resolv.conf symlinked:
"
1725840,2018-01-20 22:53:42 UTC,"> Its broken for some VPN cases. Maintainer please note that some VPN application
> updates DNS with resolvconf package and removes those setting on exist. This is
> breaking the DNS resolution in some rare cases.
"
1725840,2018-03-13 02:56:16 UTC,This breaks chroot environments of 17.10 and up in a host of 17.04 and below.
1725840,2018-11-01 22:25:09 UTC,This issue is also happening in Ubuntu 16.04LTS with backports enabled. So I think there is something foobar with systemd-resolved and not resolvconf.
1725840,2018-12-02 11:59:42 UTC,I recently did an apt update on my laptop running cosmic. DNS was very slow and I got the degraded to UDP message. Investigation showed that /etc/resolv.conf symlinked:
1725840,2017-12-24 11:18:38 UTC,I recently upgraded to 17.1 and have this same issue.  Please provide a fix.
1725840,2018-01-20 01:01:23 UTC,+1 for the issue.
1725840,2017-12-22 09:10:30 UTC,"I have a similar issue on a fresh 17.10 install:
global sites are resolving OK, but local corporate sites not resolving"
1725840,2017-10-22 08:10:47 UTC,Sorry for the mistake.
1725840,2017-12-09 17:12:36 UTC,"Hello,"
1725840,2017-10-21 22:16:01 UTC,Please attach your upgrade logs from /var/log/dist-upgrade to help us try to see what has happened on your system.
1725840,2017-12-12 00:49:06 UTC,"On Sat, Dec 09, 2017 at 05:12:36PM -0000, Daniel wrote:

> Hello,
"
1725840,2017-10-22 21:06:57 UTC,"Thanks.  This log shows the correct upgrade, but unfortunately it doesn't show any obvious explanation for why /etc/resolv.conf was replaced."
1725840,2017-10-23 09:52:59 UTC,"If you need further information, please let me know."
1725840,2017-11-04 06:53:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725840,2017-10-21 23:18:03 UTC,"Preparando para desempaquetar .../013-resolvconf_1.79ubuntu4_all.deb ...
Desempaquetando resolvconf (1.79ubuntu4) sobre (1.79ubuntu1) ..."
1725840,2017-11-05 07:12:11 UTC,"On Sat, Nov 04, 2017 at 06:55:17AM -0000, Matteo Dell'Amico wrote:

> Same bug for me: /etc/resolv.conf was pointing to
> /run/NetworkManager/resolv.conf rather than
> ../run/resolvconf/resolv.conf, as fixed by dpkg-reconfigure resolvconf.
"
1725840,2017-11-18 05:08:35 UTC,I do have the same issue after upgrade from 17.4-17.10.   So do we have a FIX !!!
1725840,2017-11-22 09:29:08 UTC,"I have this same issue on a clean install of xubuntu 17.10.  My biggest issue is that it seems to return after reboot (has reoccurred twice now, i assume after applying updates or something as I have restarted more than twice).  I have previously been doing the following to fix:
sudo rm /etc/resolv.conf
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
systemctl restart resolvconf"
1725840,2017-11-28 07:27:25 UTC,"Danni, this is useful information and gives the best hope of being able to debug the problem.  Was your original resolv.conf a symlink or a real file?  Can you attach it to this bug report?"
1725840,2017-11-04 06:55:17 UTC,"Same bug for me: /etc/resolv.conf was pointing to /run/NetworkManager/resolv.conf rather than ../run/resolvconf/resolv.conf, as fixed by dpkg-reconfigure resolvconf."
1725841,2017-10-21 22:07:45 UTC,"StacktraceTop:
 WTFCrash () at ./Source/WTF/wtf/Assertions.cpp:278
 WebKit::CallbackMap::invalidate (error=WebKit::CallbackBase::Error::OwnerWasInvalidated, this=0x7fb8141da028) at ./Source/WebKit/UIProcess/GenericCallback.h:225
 WebKit::WebCookieManagerProxy::processPoolDestroyed (this=0x7fb8141da000) at ./Source/WebKit/UIProcess/WebCookieManagerProxy.cpp:76
 WebKit::WebProcessPool::~WebProcessPool (this=0x7fb7d3ffe000, __in_chrg=<optimized out>) at ./Source/WebKit/UIProcess/WebProcessPool.cpp:298
 WebKit::WebProcessPool::~WebProcessPool (this=0x7fb7d3ffe000, __in_chrg=<optimized out>) at ./Source/WebKit/UIProcess/WebProcessPool.cpp:317"
1725841,2017-10-23 08:37:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725850,2017-10-21 22:56:47 UTC,"StacktraceTop:
 journal_file_rotate_suggested (f=0x55dd07aa2190, max_file_usec=2629800000000) at ../src/journal/journal-file.c:3674
 write_to_journal (priority=4, n=25, iovec=0x55dd07aa6de0, uid=1000, s=0x7ffcd6142670) at ../src/journal/journald-server.c:673
 dispatch_message_real (s=0x7ffcd6142670, iovec=0x55dd07aa6de0, n=25, m=76, ucred=<optimized out>, tv=0x7ffcd6142330, label=0x0, label_len=0, unit_id=0x0, priority=4, object_pid=0, cgroup=0x55dd07ab94d0 ""/user.slice/user-1000.slice/session-18.scope"") at ../src/journal/journald-server.c:1068
 server_dispatch_message (s=<optimized out>, iovec=0x55dd07aa6de0, n=<optimized out>, m=76, ucred=0x7ffcd6142350, tv=0x7ffcd6142330, label=0x0, label_len=0, unit_id=0x0, priority=4, object_pid=0) at ../src/journal/journald-server.c:1188
 server_process_entry (label_len=0, label=0x0, tv=0x7ffcd6142330, ucred=<optimized out>, remaining=<synthetic pointer>, buffer=0x55dd07a47c40, s=0x7ffcd6142670) at ../src/journal/journald-native.c:306"
1725850,2017-10-23 20:24:37 UTC,"the error is
""systemd-journald.service: Watchdog timeout (limit 3min)!"""
1725850,2017-10-24 08:47:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725851,2018-07-06 08:23:38 UTC,Also can't download for the same reason. Nexus 5
1725851,2018-05-14 00:13:01 UTC,Can't download for tge same reason.  oneplus one
1725864,2017-11-22 20:38:14 UTC,Thanks for the update. Issue still seen with Calibre 3.12.0.
1725864,2017-11-02 16:51:34 UTC,Still occurring in calibre 3.11.1
1725864,2017-11-22 01:35:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725869,2017-10-24 20:38:52 UTC,Contacted <email address hidden> with details of this bug report.
1725874,2017-12-31 16:26:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725874,2017-12-31 16:29:17 UTC,Affects me too on Ubuntu 17.10. Same output of dpkg -l:
1725883,2017-10-22 08:02:15 UTC,"ccfdb158 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | FAILED    | a260a9f6  |            |             | 2017-10-22T07:52:05Z |

| 68b18716 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | FAILED    | a260a9f6  |            |             | 2017-10-22T07:52:35Z |
| c3be7de2 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:53:05Z |
| dc191a32 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:53:35Z |
| 866ead83 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:54:05Z |
| 87f3d245 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:54:36Z |
| b0bbd9fa | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:55:06Z |
| ae89a892 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:55:37Z |
| 127fcc26 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:56:07Z |
| 11bc01c5 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:56:37Z |
| 66071adb | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:57:07Z |
| bbcc478c | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:57:38Z |
| 4868f63a | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:58:10Z |
| cff6c1a6 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:58:40Z |
| 70d777f9 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:59:09Z |
| 146ec5bc | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:59:41Z |


+----------+----------------------------+-----------------------+-----------+-----------+------------+-------------+----------------------+
I met this problem again"
1725883,2017-10-23 01:31:14 UTC,"Looks like the cluster-scale-out operations are forever running.
When these operations/actions are running, cluster is locked for sure.
Please check the reason why CLUSTER_SCALE_OUT is running for so long.
On Sun, Oct 22, 2017 at 08:02:15AM -0000, yaofenghua wrote:

> ccfdb158 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | FAILED    | a260a9f6  |            |             | 2017-10-22T07:52:05Z |
> | 68b18716 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | FAILED    | a260a9f6  |            |             | 2017-10-22T07:52:35Z |
> | c3be7de2 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:53:05Z |
> | dc191a32 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:53:35Z |
> | 866ead83 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:54:05Z |
> | 87f3d245 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:54:36Z |
> | b0bbd9fa | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:55:06Z |
> | ae89a892 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:55:37Z |
> | 127fcc26 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:56:07Z |
> | 11bc01c5 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:56:37Z |
> | 66071adb | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:57:07Z |
> | bbcc478c | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:57:38Z |
> | 4868f63a | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:58:10Z |
> | cff6c1a6 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:58:40Z |
> | 70d777f9 | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:59:09Z |
> | 146ec5bc | webhook_76631dc0           | CLUSTER_SCALE_OUT     | RUNNING   | a260a9f6  |            |             | 2017-10-22T07:59:41Z |
> +----------+----------------------------+-----------------------+-----------+-----------+------------+-------------+----------------------+
> I met this problem again
>
> mysql> select * from cluster_lock;
> +--------------------------------------+------------------------------------------+-----------+
> | cluster_id                           | action_ids                               | semaphore |
> +--------------------------------------+------------------------------------------+-----------+
> | a260a9f6-33e0-44b8-90e7-5cd29889a2dc | [""68b18716-a104-4ca1-9022-af1c45a97743""] |        -1 |
> +--------------------------------------+-------------------...
"
1725883,2017-10-23 01:54:53 UTC," a260a9f6-33e0-44b8-90e7-5cd29889a2dc | [""68b18716-a104-4ca1-9022-af1c45a97743""] |        -1 |
the cluster is lock by action 68b18716-a104-4ca1-9022-af1c45a97743 ,this action is FAILED,  the lock is not released,  so the later scale_out action is running all the time, it can not get the lock."
1725883,2018-02-13 12:01:01 UTC,Can we know if the bug is still there?
1725883,2019-01-15 18:00:00 UTC,"There have been several fixes made to ensure that cluster locks are releaed.  Also, there is a action update API to cancel actions how.  So this bug should no longer happen."
1725888,2017-10-31 08:55:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725888,2020-01-24 10:07:46 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1725888,2017-10-27 02:28:19 UTC,I gave all the information needed. not incomplete.
1725888,2017-10-25 03:35:35 UTC,"Sebastian Bacher, copying between any two programs currently doesn't work unless both programs stay open. i.e., if I open a text editor and copy the contents, then close the text editor and go to another program (or the same text editor), the copied data will be gone. that's why you need a clipboard manager."
1725888,2017-10-23 19:18:55 UTC,what do you copy between what and what and how?
1725888,2017-10-23 16:11:20 UTC,I think this issue is specific to running on GNOME on Wayland.
1725888,2017-10-23 15:53:04 UTC,I have re-created it on another machine. It seems the steps neccessary to reproduce this is simply to install the operating system. Neither machine had a functional clipboard manager.
1725888,2017-10-23 15:08:02 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1725888,2017-10-23 23:04:15 UTC,"I can add this, this is a completely fresh install as of just three or four days ago via the 17.10 iso. there should be then no trace of Unity, of I am not mistaken. So i think I can attest to this being a gnome issue via wayland. again, simply installing parcellite suffices, as long as you don't mind the parcellite icon constantly being on the top right. but a clipboard manager is really a necessary thing these days if you work on your nix box like I do."
1725897,2017-10-23 15:06:22 UTC,The GNOME snaps using the framework are allowed to autoconnect so the manual connect command shouldn't be needed ... maybe gnome-system-monitor is missing from the list?
1725897,2017-10-23 19:01:55 UTC,https://forum.snapcraft.io/t/auto-connection-for-gnome-3-24-content-interface/1379/73 is relevant to the issue
1725897,2017-10-23 22:52:30 UTC,"Well I'd consider it a bug (about not being installed) because gnome-system-monitor is already installed from the Ubuntu image. (the .deb version)
For some reason Software doesn't 'see' it. Whether there are any other default installed apps that don't show in Software but the snap versions do I'd have to take a look."
1725897,2017-10-24 13:23:50 UTC,"Well, you have the deb installed not the snap so the info is correct. Anyway it's offtopic for this bug and known as bug #1711801 so better to continue the discussion in that one"
1725921,2018-03-26 07:56:19 UTC,"I filed bug 1758841, and virt-manager is the only application I found with this problem. So it might be something to fix there."
1725921,2018-03-26 02:06:08 UTC,"jibel,"
1725921,2018-03-26 05:14:26 UTC,"BTW, I think the bug there is that the menu background is light. They are meant to be dark now."
1725921,2018-03-26 15:21:51 UTC,"Hello Eldar, or anyone else affected,"
1725921,2017-10-22 06:35:39 UTC,The same issue in wayland and Xorg
1725921,2018-03-27 03:45:23 UTC,Verification succeeded in xenial using 14.04+16.04.20180326-0ubuntu1
1725921,2018-03-27 03:51:12 UTC,I can't comment about bug 1758841 right now but I assume the same will happen to xenial. Any comments about that bug should be made in bug 1758841.
1725921,2018-03-31 18:27:38 UTC,Works for me. Thanks!
1725921,2018-03-23 16:54:21 UTC,"This introduced a regression, and now there are light grey items on grey menus which are barely readable. For example this screenshot of virt-manager."
1725921,2018-03-26 15:23:31 UTC,I have accepted this package to xenial-proposed but could someone check if virt-manager is also affected with bug LP: #1758841 for that series? I would also like some other GTK apps getting tested to make sure they do not regress in xenial. Thanks!
1725921,2018-03-22 15:50:05 UTC,"Please make sure to include the SRU-required info in the description [1]. Also, I see this bug has been nominated for artful - could an artful update be published to UNAPPROVED in that case?"
1725921,2017-10-22 06:29:56 UTC,But text in menus is good
1725921,2018-03-07 08:29:02 UTC,Added a fix for xenial too.
1725921,2018-02-13 02:29:35 UTC,This bug is a simple regression. So you can also work around it by taking one step back. Just install:
1725921,2018-02-12 16:51:58 UTC,"Fix #2 (use light menu in popup):
It is need to change in file /usr/share/themes/Ambiance/gtk-2.0/gtkrc the next line:
style ""menu"" = ""dark"" {
to
style ""menu"" = ""white"" {"
1725921,2018-02-11 11:00:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725921,2018-02-11 10:53:49 UTC,"Fix:
It is need to comment (with '#') in file /usr/share/themes/Ambiance/gtk-2.0/gtkrc the next line:
widget ""*.gtk-combobox-popup-menu.*"" style ""menuitem_text_is_fg_color_workaround""
Restart buggy application."
1725921,2018-02-11 08:41:29 UTC,"Related issue
https://bugs.eclipse.org/bugs/show_bug.cgi?id=526621"
1725921,2017-10-22 06:46:25 UTC,"I see the same issue in another program kicadbom2spec (use wxwidgets).
Maybe it is wxwidgets bug"
1725921,2017-10-22 06:44:57 UTC,The same issue in dialog combo boxes
1725921,2018-04-05 07:11:14 UTC,"The verification of the Stable Release Update for ubuntu-themes has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1725921,2018-03-22 15:33:33 UTC,This bug was fixed in the package ubuntu-themes - 16.10+18.04.20180322.3-0ubuntu1
1725921,2018-04-05 07:21:14 UTC,This bug was fixed in the package ubuntu-themes - 14.04+16.04.20180326-0ubuntu1
1725941,2018-11-23 11:05:27 UTC,merge request https://gitlab.gnome.org/GNOME/gnome-shell-extensions/merge_requests/48
1725941,2018-11-23 05:10:47 UTC,Note this is not an SRU. The fix needs to land in the latest development release first (19.04).
1725941,2018-11-23 05:03:43 UTC,"Oh, upstream already has a fix proposed:"
1725941,2018-11-23 01:59:01 UTC,"Denis,"
1725941,2018-11-22 12:27:30 UTC,"The attachment ""hotcorner.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1725941,2018-11-23 05:02:21 UTC,"Also, the upstream bug report ID is gnome-shell-extensions#6"
1725941,2017-10-24 02:06:21 UTC,Someone could always attempt a proper fix and propose it upstream. If upstream don't have to do the work then they might be more accepting of a fix.
1725941,2017-10-23 08:55:11 UTC,"In fact, I'm not sure if this is this a bug with gnome-shell or with gnome-tweak-tool and the method it uses to disable hot corners."
1725941,2017-10-23 08:50:03 UTC,"The issue appears to stem from the Main.layoutManager.hotCorners[] array being empty when hot corners are disabled:
https://git.gnome.org/browse/gnome-shell-extensions/tree/extensions/apps-menu/extension.js?id=01893ca0485806f181d0401b7a6347a4adaa71de#n483"
1725941,2017-10-23 08:36:25 UTC,"Unsure what we can do if upstream is not wanting to update their extension to handle that case well just to make a point, maybe somebody should create a new one including the suggested change?"
1725941,2018-11-22 11:17:40 UTC,introduced by optional-hot-corner.patch
1725951,2017-10-22 10:21:01 UTC,"StacktraceTop:
 icalvalue_set_parent (value=0x1af00e, property=property@entry=0x0) at ./src/libical/icalvalue.c:1442
 icalproperty_free (p=p@entry=0x5650415a5000) at ./src/libical/icalproperty.c:190
 icalcomponent_free (c=0x5650415a4e00) at ./src/libical/icalcomponent.c:205
 icalcomponent_free (c=0x5650415a22e0) at ./src/libical/icalcomponent.c:212
 free_icalcomponent (comp=<optimized out>, free=free@entry=1) at ./src/calendar/libecal/e-cal-component.c:351"
1725951,2017-10-25 08:39:57 UTC,"Thank you for your bug report, could be the due to the error pointed on https://bugzilla.gnome.org/show_bug.cgi?id=789461"
1725954,2017-11-08 17:32:07 UTC,I am seeing tty's in the process list in gnome terminal but I can't access them. The screen just freezes.
1725954,2017-11-20 22:11:11 UTC,"If you are not seeing your tty's but only a frozen screen you could try this solution. It worked for me:
https://askubuntu.com/questions/162535/why-does-switching-to-the-tty-give-me-a-blank-screen"
1725954,2017-11-17 17:41:22 UTC,"The problem is not only that..
from GUI,
ctrl+alt+f3  brings up tty3
from tty3, alt+f4...f5f..f6 bring up tty4 tty 5 tty6"
1725954,2017-11-08 17:19:40 UTC,"I also have no tty's to check what is happening during boot, is this the same issue or should I file another bug?
My laptop was doing something for 5 minutes but I couldn't check the text modus by pressing ctrl-alt-F1 or any other FN."
1725954,2017-11-18 08:46:04 UTC,"I have a more positive impression about 17.10 in general and I am seeing improvement for my situation.
Since an update today I can see the tty's again when fully booted and pressing ctrl-alt-f2 but still unable to see them during slow boot.
dpkg.log:
2017-11-18 09:28:54 upgrade accountsservice:amd64 0.6.42-0ubuntu3 0.6.42-0ubuntu3.1
2017-11-18 09:28:54 status half-configured accountsservice:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:54 status unpacked accountsservice:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:54 status half-installed accountsservice:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:54 status triggers-pending dbus:amd64 1.10.22-1ubuntu1
2017-11-18 09:28:54 status triggers-pending dbus:amd64 1.10.22-1ubuntu1
2017-11-18 09:28:54 status half-installed accountsservice:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status unpacked accountsservice:amd64 0.6.42-0ubuntu3.1
2017-11-18 09:28:55 status unpacked accountsservice:amd64 0.6.42-0ubuntu3.1
2017-11-18 09:28:55 upgrade libaccountsservice0:amd64 0.6.42-0ubuntu3 0.6.42-0ubuntu3.1
2017-11-18 09:28:55 status triggers-pending libc-bin:amd64 2.26-0ubuntu2
2017-11-18 09:28:55 status half-configured libaccountsservice0:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status unpacked libaccountsservice0:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status half-installed libaccountsservice0:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status half-installed libaccountsservice0:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status unpacked libaccountsservice0:amd64 0.6.42-0ubuntu3.1
2017-11-18 09:28:55 status unpacked libaccountsservice0:amd64 0.6.42-0ubuntu3.1
2017-11-18 09:28:55 upgrade gir1.2-accountsservice-1.0:amd64 0.6.42-0ubuntu3 0.6.42-0ubuntu3.1
2017-11-18 09:28:55 status half-configured gir1.2-accountsservice-1.0:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status unpacked gir1.2-accountsservice-1.0:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status half-installed gir1.2-accountsservice-1.0:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status half-installed gir1.2-accountsservice-1.0:amd64 0.6.42-0ubuntu3
2017-11-18 09:28:55 status unpacked gir1.2-accountsservice-1.0:amd64 0.6.42-0ubuntu3.1
2017-11-18 09:28:55 status unpacked gir1.2-accountsservice-1.0:amd64 0.6.42-0ubuntu3.1
2017-11-18 09:28:55 upgrade mutter-common:all 3.26.1-2ubuntu2 3.26.2-0ubuntu0.1
2017-11-18 09:28:55 status half-configured mutter-common:all 3.26.1-2ubuntu2
2017-11-18 09:28:55 status unpacked mutter-common:all 3.26.1-2ubuntu2
2017-11-18 09:28:55 status half-installed mutter-common:all 3.26.1-2ubuntu2
2017-11-18 09:28:55 status triggers-pending gconf2:amd64 3.2.6-4ubuntu1
2017-11-18 09:28:55 status half-installed mutter-common:all 3.26.1-2ubuntu2
2017-11-18 09:28:55 status triggers-pending libglib2.0-0:amd64 2.54.1-1ubuntu1
2017-11-18 09:28:55 status half-installed mutter-common:all 3.26.1-2ubuntu2
2017-11-18 09:28:55 status triggers-pending libglib2.0-0:i386 2.54.1-1ubuntu1
2017-11-18 09:28:55 status half-installed mutter-common:all 3.26.1-2ubuntu2
2017-11-18 09:28:55 status triggers-pending man-db:amd64 2.7.6.1-2
2017-11-18 09:28:55 status half-installed mutter-common:all 3.26.1-2ubuntu2
2017-11-18 09:28:55 status unpacked mutter-common:all 3.26.2-0ubuntu0.1..."
1725954,2017-11-03 00:52:54 UTC,The fact that Ctrl-Alt-F1 now brings up the login screen is documented: https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#Ubuntu_Desktop
1725954,2017-11-01 12:05:01 UTC,I can confirm this and my screen freezes when pressing <CTRL+ALT+F3> (same behaviour up to <CTRL+ALT+F10>)
1725954,2017-10-26 13:36:41 UTC,"for me, when I make ctrl alt f3, the screen freezes and I have to make an alt f1 to return to the session"
1725954,2017-10-24 20:20:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725954,2017-11-03 12:00:24 UTC,Turns out this is the default for gdm. According to this blog post:
1725955,2020-07-06 13:22:52 UTC,The issue should be fixed with https://launchpad.net/ubuntu/+source/gnome-settings-daemon/3.36.1-1ubuntu2
1725955,2020-06-29 05:04:02 UTC,Happens for me on Ubuntu 20.04
1725955,2019-10-31 13:10:44 UTC,This started happening to me after I upgraded from Ubuntu 19.04 to 19.10. Now I get a steady spam of pop-ups and the only thing in the logs that seems related are colord messages like the one from #6:
1725955,2019-03-12 20:55:08 UTC,Could those having the issue add their journalctl log?
1725955,2019-03-12 13:08:23 UTC,Happens to me in 18.04 desktop
1725955,2019-02-27 11:44:28 UTC,It still occurs in 18.04.
1725955,2018-12-23 10:32:55 UTC,"I'm running 18.04 right now and don't have the issue, so I guess it has been resolved. Are you running 17.10 @thuerrschmidt?"
1725955,2018-12-21 23:40:09 UTC,Just a wild guess: Maybe avahi-daemon is involved somehow? For me at least these annoying messages seem to have stopped completely after throwing out the avahi-daemon service (for other reasons).
1725955,2018-02-16 06:31:02 UTC,"This notification pops up each time the network is changed (connected, disconnected), printer turned off or on, and during a daily chron job."
1725955,2017-11-01 15:20:27 UTC,"Oct 31 23:56:14 brad-ubuntu org.debian.apt[837]: 23:56:14 AptDaemon [INFO]: Quitting due to inactivity
Oct 31 23:56:14 brad-ubuntu org.debian.apt[837]: 23:56:14 AptDaemon [INFO]: Quitting was requested
Nov  1 00:01:50 brad-ubuntu systemd[1]: Started Run anacron jobs.
Nov  1 00:01:50 brad-ubuntu anacron[16049]: Anacron 2.3 started on 2017-11-01
Nov  1 00:01:50 brad-ubuntu anacron[16049]: Will run job `cron.daily' in 5 min.
Nov  1 00:01:50 brad-ubuntu anacron[16049]: Jobs will be executed sequentially
Nov  1 00:03:20 brad-ubuntu systemd[1]: dev-disk-by\x2duuid-5254FA6A54FA5069.device: Job dev-disk-by\x2duuid-5254FA6A54FA5069.device/start timed out.
Nov  1 00:03:20 brad-ubuntu systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-5254FA6A54FA5069.device.
Nov  1 00:03:20 brad-ubuntu systemd[1]: Dependency failed for /Media.
Nov  1 00:03:20 brad-ubuntu systemd[1]: Media.mount: Job Media.mount/start failed with result 'dependency'.
Nov  1 00:03:20 brad-ubuntu systemd[1]: dev-disk-by\x2duuid-5254FA6A54FA5069.device: Job dev-disk-by\x2duuid-5254FA6A54FA5069.device/start failed with result 'timeout'.
Nov  1 00:06:50 brad-ubuntu anacron[16049]: Job `cron.daily' started
Nov  1 00:06:50 brad-ubuntu anacron[16397]: Updated timestamp for job `cron.daily' to 2017-11-01
Nov  1 00:06:50 brad-ubuntu cracklib: no dictionary update necessary.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Stopping Make remote CUPS printers available locally...
Nov  1 00:06:51 brad-ubuntu systemd[1]: Stopped Make remote CUPS printers available locally.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Stopping CUPS Scheduler...
Nov  1 00:06:51 brad-ubuntu systemd[1]: Stopped CUPS Scheduler.
Nov  1 00:06:51 brad-ubuntu gsd-color[1855]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_ENVY_4520_series
Nov  1 00:06:51 brad-ubuntu gsd-color[1320]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_ENVY_4520_series
Nov  1 00:06:51 brad-ubuntu systemd[1]: Closed CUPS Scheduler.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Stopping CUPS Scheduler.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Listening on CUPS Scheduler.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Stopped CUPS Scheduler.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Stopping CUPS Scheduler.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Started CUPS Scheduler.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Started CUPS Scheduler.
Nov  1 00:06:51 brad-ubuntu systemd[1]: Started Make remote CUPS printers available locally.
Nov  1 00:06:51 brad-ubuntu colord[932]: failed to get session [pid 16648]: No data available."
1725955,2017-10-26 10:46:41 UTC,thanks for reporting it upstream
1725955,2017-10-25 18:24:44 UTC,Now the bug is reported in GNOME's bug reporter: https://bugzilla.gnome.org/show_bug.cgi?id=789490
1725955,2017-10-25 18:04:49 UTC,"Nothing shows up about it in the syslog except this, which seems to show up each time the notification comes:"
1725955,2017-10-25 11:33:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725955,2017-10-23 19:15:45 UTC,"Could you add your syslog to the bug? The notification comes from gnome-settings-daemon when detecting a new printer, the repetition is a bug for sure though"
1725955,2017-10-23 19:13:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1725955,2017-10-22 12:24:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1725955,2017-11-23 12:22:27 UTC,"I've just started working somewhere with a lot of printers and am seeing this pop up often, under Ubuntu 17.10"
1725958,2017-10-27 00:29:19 UTC,I'm not alone in suffering this critical problem:
1725958,2017-10-30 10:51:53 UTC,Eclipse works under Unity and also Ubuntu X.org. It only fails under Ubuntu so the problem is related to Wayland.
1725958,2017-10-25 10:25:09 UTC,I accidentally hit return and sent comment #4 before it was finished. The latter part should read:
1725958,2020-01-04 08:07:59 UTC,I am experiencing the same under Debian 10. It seems it is related to custom cursor themes. Using the default one (Adwaita) seems to solve the issue.
1725958,2017-10-23 08:44:23 UTC,I have filed a bug in the Eclipse project too: https://bugs.eclipse.org/bugs/show_bug.cgi?id=526357.
1725958,2017-10-22 23:56:01 UTC,Who gets to decide the bug's importance? In my view this is critical as Eclipse doesn't run at all which makes developing for 17.10 very difficult.
1725958,2017-10-25 10:20:12 UTC,"Following a power-off, reboot and installation b SoftwareUpdater of a Gnome Desktop Manager update I no longer suffer the magnified splash screen corner, the hang or Neon's stream of GTK warnings. Both versions now have an identical failure:"
1725967,2017-10-22 14:17:23 UTC,The Skip button im talking about is on the page with the slidershow where you see the installation progress bar and wait for it to finish installing.
1725967,2017-10-22 14:11:03 UTC,"Its seems like the button ""Skip"" is not using the translation if you select installa Ubuntu during boot.
But if you select try Ubuntu during boot and then start the installer inside GNOME the button uses the translation."
1725973,2017-10-22 12:33:26 UTC,"This is a good request, see also mailing list [1]."
1725973,2020-09-21 12:57:51 UTC,Closing because INVALID.
1725976,2017-10-22 12:24:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1725976,2017-10-23 13:00:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725977,2017-10-22 11:48:48 UTC,"StacktraceTop:
 g_thread_new (name=0xb717ee96 ""gmain"", func=0xb712dff0 <glib_worker_main>, data=0x0) at ../../../../glib/gthread.c:830
 g_get_worker_context () at ../../../../glib/gmain.c:5769
 g_task_thread_pool_init () at ../../../../gio/gtask.c:1977
 g_task_get_type () at ../../../../gio/gtask.c:592
 ensure_required_types () at ../../../../gio/gdbusprivate.c:246"
1725991,2017-10-22 12:58:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1725991,2017-10-26 08:04:00 UTC,"This is correct, as far as I know."
1726004,2017-10-22 15:11:39 UTC,"I think the easiest starting approach is to set initial scan only to read folders, then wait for user to select folders. Then I'll tweak further from there, till I get it how I want it. Expect a patch in a couple of days to try out."
1726004,2017-10-22 15:08:18 UTC,"Doesn't look like it will be too hard, I'll play with and see what I come up with, and submit a patch if I can work it out feasibly."
1726004,2017-10-22 14:38:44 UTC,"It's all in the mtp folder. You would basically want to implement code
to scan only the top level of each filesystem and the present the user
with a dialog to select the folders to scan from that top level.
Currently, what happens is the entire fs is scanned and used to present
that dialog."
1726004,2017-10-22 14:25:29 UTC,Well as I said I'm decent with C languages so I'll look into the source and see if I can do with it if you can point me to the right file(s) to look into
1726004,2017-10-22 14:18:06 UTC,"MTP is awful, I agree. I'd suggest you simply use one fo the wireless conenction methods instead and avoid it all together. https://manual.calibre-ebook.com/faq.html#how-do-i-use-calibre-with-my-android-phone-tablet-or-kindle-fire-hd"
1726004,2017-10-22 14:06:43 UTC,"Well I wouldn't even complain except MTP is a crap protocol to begin with and on Windows it times out during this 4 hour process and I have to start all over again. Is calibre coded in python purely or does it use otther toolkits, python I know, C variations I can manage well enough but working with Linux toolkits makes me lightheaded."
1726004,2017-10-22 13:37:37 UTC,"This is not worth the effort for me personally. If some one else wants to implement it, I will  be happy to supply any needed guidance. If so, re-open the ticket and we can discuss it."
1726018,2017-10-22 13:56:02 UTC,Marked as high since scheduled for Queens.
1726029,2019-09-26 04:17:32 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1726029,2019-07-27 10:39:34 UTC,Is this still valid? A quick google found tutorials/forum posts suggesting FreeRoute does apply KiCad's design rules.
1726029,2017-10-24 12:20:53 UTC,"On 10/23/2017 5:32 PM, שלי יוסי wrote:

> It's a shame that kicad team don't take autorauting siriuslly enough!
> It's will be much a shame if you'll take it out! I love kicad but a CAD
> software without autorauting is not much of a CAD software. It's more
> important then loading libraries on a library, which i know how effort
> you've put on that.
"
1726029,2017-10-23 21:32:31 UTC,"It's a shame that kicad team don't take autorauting siriuslly enough! It's will be much a shame if you'll take it out! I love kicad but a CAD software without autorauting is not much of a CAD software. It's more important then loading libraries on a library, which i know how effort you've put on that."
1726029,2017-10-23 12:07:53 UTC,The auto-router has not been updated since the introduction of the keep out zones and some of the other new features added to Pcbnew and I doubt it ever will be.  We really should have ripped it out years ago but some users wanted to keep it for convenience for simple boards.  You would be better served exporting your board to Spectra DSN and using FreeRoute which I believe has a much more capable auto-router.
1726029,2017-10-23 01:52:24 UTC,Very funny.
1726029,2017-10-23 01:26:22 UTC,Does it also happen on the nightlies?
1726029,2017-10-22 23:49:59 UTC,version: 4.0.7 running on windows 10.
1726029,2017-10-22 23:47:30 UTC,why you changed the status to incomplete? Why the hurry? I updated the missing info as soon as i got the mail.
1726029,2017-10-22 23:42:56 UTC,Update: The autorouter also places tracks near throuholes.
1726029,2017-10-22 23:38:34 UTC,"The latest Version: 4.0.7 stable.
I also found out that it Route tracks in keepout Area!"
1726029,2017-10-22 15:51:50 UTC,What kicad version?
1726043,2017-10-24 13:43:04 UTC,+1 on making this automatic if the openstack charms are deployed with log monitoring tools that want this feature - this would require updating the log config if filebeat or suchlike is related to the charm.
1726043,2017-10-24 13:43:30 UTC,(plus I'd like to see a spec for this work as it could do with discussion and peer review before implementation).
1726055,2017-10-23 14:15:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726055,2020-07-01 21:16:41 UTC,"The issue has been fixed in newer versions, https://gitlab.gnome.org/GNOME/evince/-/issues/1321"
1726061,2017-11-14 13:34:45 UTC,"Upon initially booting either 4.13.11 or 4.14.0 I see 1 in active_count for ACAD, and zeros elsewhere. When 4.14.0 has immediately resumed from suspend and shows additional events from the lid and the power button, I have not touched either of those in the course of attempting to suspend."
1726061,2017-11-14 14:06:17 UTC,"Perhaps this is no longer a kernel issue or at least no longer a regression. I am getting the same behavior with 4.14 and 4.13.11 and even the kernel from 17.04 . Normally when I am suspending at the end of the day I first close the laptop lid, then choose suspend from the menu on the external monitor... and that seems to work. Not sure how long the suspend menu has not worked with the laptop lid left open but today I still get it if I boot 17.04 from a different partition."
1726061,2017-11-15 04:21:29 UTC,"> On 14 Nov 2017, at 10:06 PM, Aaron Peromsik <email address hidden> wrote:
>
> Perhaps this is no longer a kernel issue or at least no longer a
> regression. I am getting the same behavior with 4.14 and 4.13.11 and
> even the kernel from 17.04 . Normally when I am suspending at the end of
> the day I first close the laptop lid, then choose suspend from the menu
> on the external monitor... and that seems to work. Not sure how long the
> suspend menu has not worked with the laptop lid left open but today I
> still get it if I boot 17.04 from a different partition.
"
1726061,2017-11-15 04:41:02 UTC,I first had to resume from suspending this morning. I ran journalctl -b before and after attempting to suspend again with the lid open. The attachment includes the lines added in between.
1726061,2017-11-17 04:37:03 UTC,"Meanwhile, since you mentioned BIOS, I checked and found that version 1.1.1 was release in August. I installed it. It didn't help."
1726061,2017-11-17 02:05:11 UTC,"Yes, it continues."
1726061,2017-11-17 04:18:54 UTC,I am not sure why power button and lid switch are not listed in wakeup_source.
1726061,2017-11-13 05:18:57 UTC,Kai-Heng
1726061,2017-11-16 04:48:24 UTC,I think it's not a userspace issue. A solution/workaround should come from kernel or BIOS/EC.
1726061,2017-11-13 02:23:23 UTC,"But that bisection may be leading toward a dead end or at least a moot point. The behavior which I am calling ""bad"" there is different from what I am currently seeing in later RCs and in 4.14.0."
1726061,2017-11-14 07:53:50 UTC,"So it may be PNP0C0D:00 (lid switch), LNXPWRBN:00 (power button), or ACAD wakes your system up."
1726061,2017-11-08 03:03:24 UTC,"It seems to be two separate issues,"
1726061,2017-11-07 14:03:50 UTC,To summarize my earlier comments: All the below relates to suspend/resume of 17.10.
1726061,2017-11-07 08:15:43 UTC,Does v4.13 (not v4.13.11) have this issue?
1726061,2017-11-05 16:37:46 UTC,"sorry, meant to say 4.13.11, not 4.3.11"
1726061,2017-11-05 16:37:17 UTC,Tested with newest mainline kernels. 4.3.11 still works fine. 4.14.rc7 still fails to come out of suspend.
1726061,2017-10-25 02:17:04 UTC,"Tested a couple more kernels and it seems that the issue I have with 4.13.4 is not present in mainline 4.13.5, nor in 4.13.9. Resume worked fine."
1726061,2017-10-24 18:39:40 UTC,"4.14-rc6 is even worse -- I can't wake the machine after suspend at all, except by rebooting with long-press of the power button."
1726061,2017-10-23 15:39:22 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1726061,2017-10-22 16:30:06 UTC,This change was made by a bot.
1726061,2017-11-13 01:29:40 UTC,Still a few rounds of bisect remaining but this is where I am now:
1726068,2019-12-18 11:01:19 UTC,"I'm still happy with the test case. It shows that the debconf socket is independent of whatever frontend is running, and hence closing the frontend can't close the debconf socket. Which means you can just use pkcon / aptdcon to test that bit."
1726068,2019-10-30 14:07:18 UTC,"An upload of packagekit to disco-proposed has been rejected from the upload queue for the following reason: ""Incomplete SRU information and no response to requests to fix it""."
1726068,2019-10-25 07:55:08 UTC,"ping, will the test case be improved?"
1726068,2019-09-27 22:03:11 UTC,"I don't think this test case is well formed, it doesn't describe how to install the packages with the named backends and it doesn't mention needing to kill the frontend or when to kill it."
1726068,2017-10-22 20:48:21 UTC,This happens if software-properties is closed on the desktop before the packages have finished installing.
1726068,2019-05-24 12:58:04 UTC,This bug was fixed in the package packagekit - 1.1.12-5ubuntu3
1726068,2018-03-19 16:51:55 UTC,"I think dangling sockets to the frontend might also be a problem with PackageKit, but I'm not sure. My idea was to have helper have a timeout and be (re)launched by systemd via socket activation, but
I don't know if that's feasible."
1726068,2019-05-24 14:32:49 UTC,This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu22
1726075,2019-08-25 00:37:05 UTC,I have reported a similar problem with another HP laptop but with ALC295 chipset
1726075,2018-12-29 21:08:31 UTC,"Same issue, HP Pavilion 15-cc178cl."
1726075,2018-05-10 20:49:03 UTC,Confirming the same issue on hp pavilion 15-cb045wm. Was not able to fix the problem with hdajackretask. Fix outlined here did not fix the issue: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183
1726075,2018-05-10 20:49:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726075,2018-01-02 21:05:30 UTC,I can confirm I'm having the same problem with a similar HP Pavilion model under Ubuntu 16.04.There is no audio from the built in speakers but pavucontrol shows audio is being played.
1726075,2017-11-17 03:37:46 UTC,I can confirm I'm having the same problem with a similar HP Pavilion model under Fedora 27. There is no audio from the built in speakers but pavucontrol shows audio is being played. Verified nothing is muted in alsamixer.
1726075,2018-01-03 23:04:40 UTC,I got my new HP Pavilion 15-cc055od laptop to play sound out of the internal speakers in Xubuntu 16.04.
1726085,2017-10-22 17:42:54 UTC,"StacktraceTop:
 _int_realloc (av=0x7fbb3c000020, oldp=0x7fbb3c0319a0, oldsize=1552, nb=1808) at malloc.c:4586
 ?? ()
 __GI___libc_realloc (oldmem=0x0, oldmem@entry=0x7fbb3c0319b0, bytes=1552, bytes@entry=1800) at malloc.c:3245
 sqlite3MemRealloc (pPrior=0x7fbb3c0319b8, nByte=1792) at sqlite3.c:20863
 sqlite3Realloc (pOld=0x7fbb3c0319b8, nBytes=1792) at sqlite3.c:24759"
1726086,2018-06-21 18:47:59 UTC,It seems there is a dependency conflict which makes it impossible to have
1726086,2018-10-31 13:05:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726116,2017-10-23 14:01:41 UTC,"The issue is rather with thunderbird not sending updates correctly, it was doing the same sometime under unity"
1726116,2017-10-24 02:32:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726116,2019-06-15 18:21:16 UTC,Still happening Thunderbird 60.7.0(64-bit) Ubuntu-GNOME 18.04.2 LTS
1726116,2019-07-30 14:10:36 UTC,Still Happening Thunderbird 60.8.0(64-bit) Ubuntu 19.04
1726118,2018-04-18 14:21:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726118,2017-10-22 19:25:05 UTC,"StacktraceTop:
 g_vfs_daemon_register_path (daemon=0x0, obj_path=0x7f64bc0153c0 ""/org/gtk/vfs/daemon/dirmonitor/5"", callback=callback@entry=0x7f64ccd71500 <register_path_cb>, user_data=user_data@entry=0x7f64ac0032b0) at gvfsdaemon.c:537
 g_vfs_monitor_new (backend=backend@entry=0x55add6a4b130) at gvfsmonitor.c:269
 do_create_dir_monitor (backend=0x55add6a4b130, job=0x7f64b8015ee0, filename=0x55add6a63b30 ""/Card/Android"", flags=<optimized out>) at gvfsbackendmtp.c:454
 g_vfs_job_run (job=0x7f64b8015ee0) at gvfsjob.c:197
 job_handler_callback (data=<optimized out>, user_data=<optimized out>) at gvfsdaemon.c:208"
1726124,2018-01-26 01:24:47 UTC,"This change in behavior is deliberate.  There are two mutually incompatible interpretations of DNS search lists provided via a VPN connection.  One is for split DNS, to say ""this is the list of domains for which you should send lookups to the accompanying DNS server"".  The other is to use it as a search list for resolv.conf.  Unfortunately, interpreting wrongly in either direction breaks client configs.  But whereas there are other ways that one can configure the behavior of resolv.conf to add search domains, the only reasonable way to configure split DNS is to do so by providing this information directly from network-manager-openvpn to systemd-resolved."
1726124,2020-10-08 16:14:59 UTC,Still an issue in 20.04 LTS
1726124,2019-11-13 21:09:18 UTC,My guess is that rls-bb-notfixing means this is not getting fixed in Bionic Beaver 18.04. Really hoping a fix can make it into the 20.04 LTS release though.
1726124,2019-04-20 17:41:09 UTC,What does that rls-bb-notfixing tag mean?  This is just a bug that won't be fixed?  Split tunnel DNS with openconnect is still completely broken in 19.04 and it would be very nice to have this working.  The last couple years of Ubuntu releases have required me to ditch systemd-resolved in order to access my company's internal services while remote.
1726124,2019-01-23 14:33:10 UTC,"So, is anyone going to fix this? It is in LTS now and causing havoc. Fwiw, I support that it should allow split resolution just like it used to do."
1726124,2018-03-06 08:29:27 UTC,We won't be able to add the option to select between the two options this cycle.
1726124,2018-02-23 19:37:16 UTC,"I would also like to chime in, that it is very useful to have the ability to append a DNS-suffix when doing short-name DNS lookups on a split-tunnel VPN connection."
1726124,2018-02-02 18:41:10 UTC,"I'm not sure why it's being asserted that these two uses are mutually incompatible, especially since I've been using them in a coordinated way forever and can still do so (at the expense of junking systemd-resolve and going back to using dnsmasq and a custom configuration, which is obviously a big pain).  I've even, in the past, used MULTIPLE VPNs, even at the same time, and it still just works."
1726124,2018-02-02 16:05:24 UTC,I hope something can be worked out before this lands in the next LTS-release. This breaks one of the most common uses of a VPN (remote work).
1726124,2018-02-02 15:59:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726124,2017-11-22 19:17:44 UTC,"Andreas: unfortunately disallowing short name lookups is not acceptable: many environments use short names in embedded URLs all over the place, and without domain search paths the entire environment is rendered completely unusable (e.g., URLs are simply https://tools/foo or https://wiki/foo or whatever; this means no cross-links work)."
1726124,2021-01-13 14:10:28 UTC,Still an issue in 20.10
1726124,2017-11-16 12:40:34 UTC,to->two
1726124,2017-11-16 12:49:22 UTC,"BTW, the long timeout you see on short name lookup failures is most likely due to LLMNR being on by default. I think this is insane and I always switch it off in /etc/systemd/resolved.conf ."
1726124,2017-10-22 19:42:42 UTC,network-manager has resolved integration and it does push search domains to resolved and they are updated in the /etc/resolv.conf.
1726124,2017-10-22 20:32:50 UTC,"Thank you for the update. I will check the code, and will try to resolve this as soon as possible."
1726124,2017-10-22 20:33:06 UTC,"Does everything work, if you route all traffic via VPN?"
1726124,2017-10-22 20:18:55 UTC,"To be clear, they are NOT updated in /etc/resolv.conf.  They ARE updated in /run/NetworkManager/resolv.conf, but that has no effect since we're not using that for resolution: instead we're using systemd-resolve."
1726124,2017-10-22 21:08:42 UTC,"I'm not sure I understand what you mean.  In a typical configuration you never send ""foo"" to the nameservice, there's always a search domain and those lookups are always tried first (because the default value for the ndots is 1).  This is handled by the libc resolver linked into every program, it's not handled by a central service."
1726124,2017-11-13 12:46:37 UTC,It would probably be a good idea to forward it to n-m upstream as well on bugzilla.gnome.org
1726124,2017-11-13 16:10:15 UTC,"Hi Sebastien, thanks for your interest.  This issue is causing me extreme pain.  I believe I'm going to have to reconfigure N-M to use the old-style dnsmasq setup and throw out systemd-resolve pretty soon."
1726124,2017-11-16 12:39:23 UTC,"Paul Smith, what you describe is information leakage and shouldn't IMHO work as you say by default."
1726124,2017-10-22 20:39:25 UTC,"Right, so it seems like NM checks the never-default setting, and doesn't push them as resolve domains =/ I will test things out to be sure."
1726143,2018-04-01 09:35:03 UTC,This bug was fixed in the package nautilus-share - 0.7.3-2ubuntu3
1726143,2018-12-20 12:29:45 UTC,This bug hits me on Ubuntu 16.04 too
1726143,2018-11-05 15:41:41 UTC,"The issue described in the topic got resolved, we don't plan to fix more in bionic at this time"
1726143,2018-07-16 04:27:30 UTC,Also need to add basic smbclient in other Ubuntu installations to get Samba printers working.
1726143,2018-04-08 10:14:52 UTC,"Changing back to confirmed, we still need to work out what to do with smbpasswd."
1726143,2018-04-01 06:02:50 UTC,With the removal of the pam-smbpass module there is no longer any syncing of Ubuntu/System accounts into Samba. This means to get password protected shares working after installing samba the user would need to run:
1726143,2017-12-14 19:09:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726143,2018-01-26 19:39:51 UTC,"I found a thread at https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2016-March/016298.html that mentions the libpam-smbpass package was removed. Guest shares can still be created through Nautilus, but password protected shares cannot. Shares can be manually created by editing /etc/samba/smb.conf, but this isn't a very GUI experience..."
1726143,2018-01-20 17:24:24 UTC,"I have the same issue. Created a fresh install of Ubuntu 17.10, changed to automatic mount options. Wanted to shared media Drive but got this notice "" Could not find package 'libpam-smbpass'."
1726143,2017-12-31 22:37:16 UTC,I'm getting this too. Just saw this post while looking to see if this has been fixed or if anyone has any work-arounds.
1726143,2017-12-14 19:09:15 UTC,I have this same issue with Ubuntu 17.10
1726143,2018-03-02 17:33:42 UTC,This is still an issue in yesterday's build of 18.04
1726145,2018-04-03 23:04:24 UTC,"Note to self: when checking for potential duplicates, ask bug reporters to check for the output of:"
1726145,2018-04-03 05:45:20 UTC,This is bug #1699772.
1726145,2017-10-23 14:12:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726145,2017-10-22 21:09:02 UTC,"StacktraceTop:
 _expand_stack_to (bottom=0xbf224fff <error: Cannot access memory at address 0xbf224fff>, bottom@entry=0xbf224000 <error: Cannot access memory at address 0xbf224000>) at ./src/hotspot/src/os/linux/vm/os_linux.cpp:673
 os::Linux::manually_expand_stack (t=0x33dfc00, addr=0xbf224000 <error: Cannot access memory at address 0xbf224000>) at ./src/hotspot/src/os/linux/vm/os_linux.cpp:686
 os::create_attached_thread (thread=0x33dfc00) at ./src/hotspot/src/os/linux/vm/os_linux.cpp:965
 os::create_main_thread (thread=0x33dfc00) at ./src/hotspot/src/os/linux/vm/os_linux.cpp:915
 Thread::set_as_starting_thread (this=0x33dfc00) at ./src/hotspot/src/share/vm/runtime/thread.cpp:988"
1726155,2017-10-23 13:49:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726155,2017-10-23 18:15:22 UTC,It seems there's a patch published. Unsure about the NM version and so if the patch applies to the Artful version of Ubuntu. Here's the bugzilla report: https://bugzilla.gnome.org/show_bug.cgi?id=772640
1726155,2020-07-02 22:35:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726155,2020-07-02 22:38:25 UTC,"The bug linked in #3 seems to be about regular connections, not VPNs."
1726155,2020-07-02 22:45:28 UTC,"Also, the ""connect automatically"" checkbox is no longer present in GNOME 3 on 20.04 LTS."
1726156,2017-10-22 22:18:56 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x7ff905e97947 ""Gtk"", file=file@entry=0x7ff905ed2a58 ""/build/gtk+3.0-Th_a5U/gtk+3.0-3.22.24/./gtk/gtkheaderbar.c"", line=line@entry=625, func=func@entry=0x7ff905ed3010 <__func__.58800> ""construct_label_box"", message=message@entry=0x55a46813b4b0 ""assertion failed: (priv->label_box == NULL)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x7ff905e97947 ""Gtk"", file=file@entry=0x7ff905ed2a58 ""/build/gtk+3.0-Th_a5U/gtk+3.0-3.22.24/./gtk/gtkheaderbar.c"", line=line@entry=625, func=func@entry=0x7ff905ed3010 <__func__.58800> ""construct_label_box"", expr=expr@entry=0x7ff905ed2b97 ""priv->label_box == NULL"") at ../../../../glib/gtestutils.c:2459
 construct_label_box (bar=<optimized out>) at ././gtk/gtkheaderbar.c:625
 gtk_header_bar_init (bar=0x55a4680fc1b0) at ././gtk/gtkheaderbar.c:2200
 g_type_create_instance (type=<optimized out>) at ../../../../gobject/gtype.c:1860"
1726156,2017-10-23 13:29:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1726156,2018-01-09 20:04:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726156,2018-01-10 02:25:42 UTC,"This issue is also being tracked in:
https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc"
1726156,2020-11-16 07:59:57 UTC,Zero crashes after 18.10 so consider it fixed.
1726159,2017-11-06 01:23:12 UTC,"> On 3 Nov 2017, at 10:11 PM, George Mathioudakis <email address hidden> wrote:
>
> I modified tlp for max performance but tlp starts only when desktop boots.
> So, kernel boot is slow.
"
1726159,2017-11-06 18:08:44 UTC,"I modified all settings ending on _BAT and some that were related to
storage/sata."
1726159,2017-11-08 06:28:35 UTC,Can you attach the output of  `cat /sys/class/scsi_host/host*/link_power_management_policy` when the issue happens?
1726159,2018-06-10 19:42:49 UTC,"I fixed the slow booting problem by editing ""/etc/hdparm.conf"" and changing ""apm_battery"" value to ""255"". Now my laptop boots normally on battery mode (same speed as plugged in AC)."
1726159,2017-11-10 09:17:12 UTC,Can you attach the output of `hdparm -I /dev/sda`? Assume /dev/sda is the SSD.
1726159,2018-06-01 06:43:20 UTC,I face the same issue on my HP ProBook 440 G4. And my laptop has the same crappy RTL8723BE WiFi chip. But the PCIe Bus Error and Wifi problems you might be facing are separate issues. The PCI bus errors can be cured by adding pci=noaer to the kernel args as mentioned by many users in the thread above. AER spams this error so much that it overwhelms your disk and so logging in becomes near impossible. Easiest option for you would be adding this kernel arg when you hit grub during boot.
1726159,2017-11-10 17:09:38 UTC,"Very Important Info: I inserted my Samsung 850 EVO 250GB SSD on my laptop's HDD slot and on battery power, with TLP off, it runs on normal speed 550MB/S Read/Write! My primary M.2 SSD ""Micron 1100 250GB"" is still running on 32MB/S Read/Write. That means Micron SSD is checking for battery/ac mode."
1726159,2017-11-11 09:31:12 UTC,"Does ""medium_power"" have the same issue for the Micron SSD?"
1726159,2018-06-01 06:22:58 UTC,"I have this error on my Asus X541U, with Ubuntu 18.04, please solve it."
1726159,2017-11-03 14:11:08 UTC,"I modified tlp for max performance but tlp starts only when desktop boots.
So, kernel boot is slow."
1726159,2017-11-10 11:23:14 UTC,I attached the output of ssd's hdparm results.
1726159,2017-11-02 06:57:55 UTC,Did you change the SATA link power management or other settings?
1726159,2017-11-09 11:49:24 UTC,"The output of host0,1,etc are all: max_performance."
1726159,2017-10-27 16:04:05 UTC,"Right, probably related to SATA link power management. Change the BAT value the same as AC value."
1726159,2017-10-27 14:25:00 UTC,"UPDATE: I installed 'tlp' Advanced Power Management package and when using the command 'tlp ac', the SSD speed gets back to normal! The option does not persist across reboots."
1726159,2017-10-26 18:09:33 UTC,"I attached the dump file ""dump.txt""."
1726159,2017-10-26 15:12:39 UTC,"Please install acpidump, then"
1726159,2017-10-26 10:32:35 UTC,"UPDATE: When the laptop is fully charged and still on AC (but not charging since it is 100% charged), the errors appear again but the SSD speed is normal (~500 Read/Write)."
1726159,2017-10-26 07:14:55 UTC,Maybe the CPU frequency is locked? Or some kernel thread slows the entire system down?
1726159,2017-10-24 13:47:59 UTC,"I blacklisted ath10k_pci by adding ""modprobe.blacklist=ath10k_pci"" as a kernel parameter."
1726159,2017-10-24 03:56:32 UTC,Can you try blacklisting ath10k_pci?
1726159,2017-10-23 20:54:51 UTC,"Device booted with the latest mainline kernel ""v4.14-rc6"" on ""Ubuntu 17.04""."
1726159,2017-10-23 15:38:33 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1726159,2017-10-22 22:30:06 UTC,This change was made by a bot.
1726159,2017-10-31 11:04:10 UTC,"Changing TLP config values did the job. But, tlp is making changes only when the desktop appears. How can I change kernel values to start on max performance? What value changes tlp does to kernel?"
1726160,2017-10-31 02:55:18 UTC,Rejected upstream: https://github.com/hadess/iio-sensor-proxy/issues/198
1726160,2018-01-25 20:39:05 UTC,"I have Lenovo Yoga 2 Pro laptop and had the same problem. After reboot (when there was login screen), screen was flickering and endless changing rotation randomly. I managed to stop this by enabling external screen (inserted miniHDMI-to-VGA cable into laptop)."
1726160,2018-10-05 05:24:08 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1726160,2018-10-05 06:23:36 UTC,Confirmed by duplicate bug 1768967.
1726160,2019-06-14 00:32:31 UTC,"Had this same problem on Acer Spin 1, with Intel Celeron CPU and Intel HD Graphics 500 (Broxton). Removing iio-sensor-proxy fixed it perfectly! Thank you!"
1726160,2019-03-12 15:49:16 UTC,"Hi sir I'm not sure about any of that, but if you click the drop down
button in the top right then click the button between the
wrench/screwdriver and the lock button and that middle button is the one
that stops the obnoxious screen rotation."
1726160,2019-04-15 02:21:03 UTC,"It looks like the fix went into systemd version 240, so it should be fixed in Ubuntu 19.04 now if you update your system..."
1726160,2019-04-15 02:45:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726160,2017-10-28 11:23:25 UTC,This bug has not occurred since removing the iio-sensor-proxy package. Opening a bug report at https://github.com/hadess/iio-sensor-proxy/.
1726160,2019-03-12 13:45:50 UTC,Problem in Elitebook 840 g2 solved by removing/purging iio sensor package after the first installation (Debian) updated to the testing version . The problem affected screen and touchpad/mouse. It seems to me that it is a unnecessary package for laptop with no position sensors is it not?
1726160,2017-10-26 20:02:26 UTC,Removed iio-sensor-proxy and I now get:
1726160,2019-01-09 01:10:22 UTC,"Hey all, there is so much technical jargon here and on that github page. I have an HP Pavilion so I'm trying to remove that iio sensor-proxy, but I'm a bit confused. Where should I be looking on that github page for directions to remove the iio sensor-proxy? Thanks!"
1726160,2017-10-26 14:26:53 UTC,"could you also use that command to tell if
gdbus introspect --system --dest net.hadess.SensorProxy --object-path /net/hadess/SensorProxy"
1726160,2017-10-26 13:12:16 UTC,"@Nevel, did you try Jeremy's workaround? Does uninstalling iio-sensor-proxy makes a difference?"
1726160,2017-10-26 12:29:10 UTC,"Tried to boot using new latest kernel (4.14.0-041400rc6), and couldn't boot at all, it hung at '[Started] Disk Manager' during every attempt to boot. Had to remove all of the 4.14...-generic and the 4.14...-lowlatency kernal packages from my pc by using ctrl+alt+f2, before it would run again on the 4.13 kernel that came in the ubuntu 17.10 release."
1726160,2017-10-25 18:28:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1726160,2017-10-24 21:31:16 UTC,I am reassigning this bug to the kernel since that's usually who the iio-sensor-proxy developer blames for issues like this.
1726160,2017-10-24 20:57:36 UTC,Unsure if same bug.  two displays - built in and external on hp laptop; 17.10.  Built in display rotates after a few mins being logged in - by 180 degrees.
1726160,2017-10-24 04:36:35 UTC,"Everytime I reboot, it rotates anticlockwise 90 and sometimes randomly it
switches to inverted screen. I tried using xandr to correct the rotation,
but nothing worked."
1726160,2017-10-24 04:12:18 UTC,"In continuing to determine issue, it seems that when waking from suspend, or logging in from power up, the orientation rotates clockwise 90*. I have had 'xrandr -o 0' orient to the right, the bottom, and the left and back to the top of the screen after closing the lid, letting it suspend itself, then reopening the lid."
1726160,2017-10-24 02:29:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726160,2017-10-23 13:47:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726160,2017-10-26 19:53:37 UTC,Before removing iio-sensor-proxy I get this:
1726163,2020-08-29 09:27:42 UTC,"> Hoping to save the next poor soul some grief :)
"
1726163,2020-08-29 09:27:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726168,2017-10-24 10:03:16 UTC,"I was waiting for the Deluge Team stable PPA to publish packages for Artful, but I'll follow your advice and go even further and adding their develop PPA. I'll update comments after some usage time."
1726168,2017-10-24 09:23:27 UTC,"The early 1.1 versions are quite buggy, could you try with latest libtorrent 1.1 stable from the develop ppa: https://launchpad.net/~deluge-team/+archive/ubuntu/develop/+build/13580853"
1726168,2017-11-07 23:42:11 UTC,"For the last 2 week of use with suggested changes, closing deluge no longer results in crash."
1726168,2017-10-24 06:37:08 UTC,What version of python-libtorrent is deluge using?
1726168,2017-10-24 08:56:31 UTC,Python-libtorrent version 1.1.1-1build2.
1726180,2017-10-23 00:37:02 UTC,I used `apt purge gstreamer*` after which the `do-release-upgrade` seems to be working.
1726180,2017-10-25 15:33:51 UTC,I've managed to boil this down to a simple test case by installing virt-viewer and nvidia-libopencl1-304 on an Ubuntu 17.04 desktop system the upgrade will fail to be calculable.
1726180,2017-10-25 15:35:01 UTC,This is the /var/log/dist-upgrade/apt.log file which contains information about the failure to upgrade.
1726180,2017-10-25 16:01:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726180,2017-10-25 16:23:03 UTC,The summary to this is incorrect or incomplete.
1726180,2018-01-02 20:10:35 UTC,Is there a workaround for this by uninstalling virt-viewer?  Will I be able to reinstall it after the upgrade?  I am not sure what the dependency issue is...
1726187,2018-01-23 18:16:56 UTC,"I am also having issues with my WiFi connection dropping out, freezing, etc."
1726187,2017-10-26 08:59:30 UTC,"@seb123 true, I wasn't sure which package to report it against.  I couldn't find the proper instructions to report kernel?-level issues."
1726187,2017-10-26 08:38:19 UTC,"could be, your reported it against network-manager though so I was suggesting to report it upstream which is a better place to discuss issues in their project"
1726187,2017-10-23 08:30:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726187,2017-10-23 06:05:30 UTC,"Correction: the wifi icon turns to question mark in the upper right corner, even though ifconfig and wifi connection selection still shows the connection as active.  The wifi off/on quickly fixes the issue."
1726187,2017-10-26 06:51:12 UTC,"@seb128, why do you think its part of GNOME? I would have thought it happens on the networking level, not UI?"
1726192,2017-10-23 21:23:09 UTC,My fault. A little to quick to hit 'x' in vi. Attached is a new syslog file that should have debug properly enabled.
1726192,2020-03-30 02:40:11 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1726192,2017-10-25 20:02:47 UTC,"Good catch. The description of the behavior is very similar. Following a review of that thread, I did some more testing. Below are the findings:"
1726192,2017-10-25 15:43:23 UTC,This one sounds similar: https://bugs.launchpad.net/ubuntu/+bug/1727356
1726192,2017-10-23 20:11:08 UTC,"syslog has
gdm-wayland-session: Unable to load file '/etc/gdm3/custom.conf': Key file contains line “More verbose logs” which is not a key-value pair, group, or comment"
1726192,2020-03-30 02:40:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726192,2017-10-23 18:16:35 UTC,"That's a pretty weird bug. Could you give details on your video cards/drivers? Also enable gdm debugging by uncommenting the debug line in /etc/gdm3/custom.conf and reboot, try to log into a wayland session and then add your syslog?"
1726192,2017-10-23 06:00:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726192,2017-10-23 05:59:48 UTC,"Confirmed on a fresh mini.iso install:
-gdm3 fails (login loop) to open a wayland session (both gnome & ubuntu)
- installing lightdm (which has some unity dependencies) allow to open a wayland session"
1726192,2017-10-23 19:16:00 UTC,My system uses Intel graphics and the default driver. The graphics details are below:
1726192,2017-10-23 04:20:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1726195,2017-10-23 13:18:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726195,2017-10-23 14:14:37 UTC,It appears to have first been reported to the GNOME team almost three years ago:
1726195,2018-06-20 18:00:09 UTC,I also have this problem with Ubuntu 18.04 running GNOME Shell 3.28.1
1726195,2020-01-24 10:08:29 UTC,"Julian, please open a new bug from the affected machine by running:"
1726213,2018-06-07 09:52:53 UTC,"Reviewed:  https://review.openstack.org/514114
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=7edf7ff66dd16d716c7b4935738ccb15f0a83aaf
Submitter: Zuul
Branch:    master"
1726213,2018-04-05 18:50:25 UTC,Upping the priority as it's impacting interoperable image import configuration.  See comments on the duplicate bug.
1726213,2018-06-07 22:16:48 UTC,This issue was fixed in the openstack/glance 17.0.0.0b2 development milestone.
1726213,2017-10-23 03:27:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514114"
1726213,2017-11-14 00:35:21 UTC,"Change abandoned by jiangpch (<email address hidden>) on branch: master
Review: https://review.openstack.org/514114"
1726224,2018-01-05 12:42:44 UTC,"Hello, Here to confirm cursor disappearance and system freeze. I have a Wacom Intuos Comic Small. Also buttons are not properly detected I have some mismatching in there (between what is shown in the settings and the one actually pressed on the tablet). Funny thing is, mismatched is not the same on Wayland and Xorg...."
1726224,2021-02-23 03:41:42 UTC,This bug should have expired last year per comment #18. If anyone still experiences similar issues then please open a new bug by running:
1726224,2020-10-07 14:15:17 UTC,Opened new bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898880
1726224,2020-09-21 02:11:06 UTC,"That's a little bit obscure. If it takes chrome-remote-desktop to trigger problems then perhaps open a new bug for that, by running:"
1726224,2020-09-19 06:01:24 UTC,I have Ubuntu 20.04.1 LTS. Window interface is Wayland. And described solution didn't work long. After half an hour cursor disappeared again. So it is obviously just coincidence that it worked.
1726224,2020-09-17 07:05:29 UTC,Note also this bug is about Wayland sessions so comment #17 should probably go somewhere else.
1726224,2020-09-17 07:03:49 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1726224,2020-02-28 03:32:02 UTC,Still not fixed in 2020. Gnome-shell and Wayland = Wacom cursor dissapears.
1726224,2018-04-07 12:39:09 UTC,"I am also experiencing this bug with my Intuos4 M. When I connect the tablet, one cursor remains where I last had the mouse, and another appears where I put down the stylus. The one where the stylus is changes appearance from arrow to ""crosshairs"" to disappearing depending on where on screen it is and over which applications."
1726224,2018-03-23 13:13:49 UTC,"I am not sure if I have the same bug with worse symptoms, or a whole different problem, but here goes:
My Intuos3 PTX-930 will not work in Ubuntu 17.10.
Under Wayland, the cursor flies randomly across the screen whenever the stylus or mouse are near the tablet, often ""collecting"" in the top left corner. It also leaves a second cursor under the control of the normal mouse/touchpad on my laptop.
Under XOrg, location is stable. BUT with either Wayland or Xorg, all input seems to include a ""touch"" or left-click action! So literally everything the cursor passes over is clicked! Programs opening, windows being opened and closed, CHAOS! In XOrg, clicking stops when I remove the stylus/mouse from the tablet's field, but in Wayland once the stylus/mouse has been near, the chaos never ends until I reboot."
1726224,2018-02-01 04:49:15 UTC,"Aside from the drop-down menu and pen button problems, I have all of the issues above while using digimend drivers and a Huion tablet; this is probably not a problem with the Gnome Wacom drivers but rather an issue with XWayland, as Casey pointed out.
Another thing worth mentioning is that on my system, after I switch off my pen with a button on the top, my regular pointer can't click anything. I need to either press alt-tab, change workspaces and switch back, or a few other options to restore the normal cursor."
1726224,2018-01-14 03:04:36 UTC,This seems to happen with applications running under XWayland. For pure Wayland applications the Wacom tablet's cursor behaves correctly.
1726224,2018-01-05 13:50:57 UTC,"Just to add some information on this on the cursor disappearance topic. If I hit the ""windows"" button the one that open the application/windows browsing of gnome shell and I move the stylus on the tablet the pointer is there. Same thing if I Alt+Tab. But I soon as I leave one or the other, cursor is not there and the only quickfix yet is unplugging and plugging back the tablet as suggested before."
1726224,2017-12-14 15:50:11 UTC,Confirm Kostas and Alessandro. Here is the output of `journalctl -e /usr/bin/gnome-shell`
1726224,2017-11-03 19:33:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726224,2017-11-08 21:48:19 UTC,Additionally if I press any of the Wacom Intuos Pen and Touch buttons the screen freezes completely and I have to restart the PC.
1726224,2017-10-23 03:58:35 UTC,The stylus pointer seems to work fine in a X.org session.
1726224,2017-10-23 04:20:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1726224,2017-10-31 09:29:30 UTC,"I have the same issue. After upgrading to 17.10 with Wayland, connecting my Wacom graphic tablet results in two independent pointers: one for the mouse and the other for the tablet pen. In the Gnome shell and in certain programs, i.e. Firefox (Firefox Quantum beta version), My Paint 1.2, the pen pointer become invisible but the pen can still draw or click buttons. I tried to check the system settings of Wacom and, when in focus of the settings window, the pointer turns visible, but if I leave the focus, it disappears again."
1726224,2017-10-31 09:44:36 UTC,Assigned also to xorg-server in case Xwayland needs a fix here.
1726224,2017-11-21 19:22:42 UTC,"I'm having these problems too. In addition, I cannot open a dropdown menu using the pen."
1726224,2017-11-01 09:27:49 UTC,"After log-in with Wacom tablet connected Gnome shows two cursors, one for the mouse and the other for the tablet's pen. I can normally control the pen's cursor. After a while the pen's cursor disappears (it is invisible, but I can still control it with the pen).
If I reset the shell with ""killall -HUP gnome-shell"" and I log in again the cursor is back."
1726224,2017-10-31 12:44:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726224,2017-11-02 12:34:56 UTC,Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=789754
1726224,2017-11-02 17:02:42 UTC,thanks
1726224,2017-11-07 11:00:13 UTC,"I wanted to add that I have the same problem too.
Additionally if I press any of the Wacom Intuos Pen and Touch buttons the screen freezes completely and I have to restart the PC.
( Using Wayland Ubuntu 17.10 )"
1726224,2017-11-08 21:47:08 UTC,"I confirm the same behaviour reported by Kostas, the system freezes if I press the buttons of the tablet."
1726224,2017-11-01 10:09:58 UTC,Additional info: the pen cursor disappears when I move in the same time both mouse and pen.
1726229,2017-10-23 04:45:14 UTC,"StacktraceTop: main (argc=<optimized out>, argv=<optimized out>) at usb_modeswitch_dispatcher.c:769"
1726229,2019-12-25 12:34:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726229,2019-12-25 12:37:51 UTC,I suspect that this bug is a duplicate of #1676763.
1726233,2018-03-11 19:45:02 UTC,I have exactly the same issue when I come back to the Desktop after playing a game in fullscreen mode.
1726233,2017-11-05 06:06:09 UTC,"A few days ago, I turned off screen locking (in system settings > desktop behaviour) and the problem hasn't happened since then."
1726233,2017-11-05 02:44:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726233,2017-10-23 06:43:31 UTC,"All 6 apps removed from panel, but still have the same symptoms.
Other than those, no widgets were added to the default Kubuntu 17.10 install (apart from setting 4 virtual desktops)."
1726233,2017-10-23 04:53:47 UTC,"This is a fresh install of Kubuntu 17.10 64bit. No widgets added to panel.
6 apps are pinned to the panel (konsole, thunderbird, firefox, dolphin, chromium, cantata)."
1726237,2017-10-23 06:26:16 UTC,"A patch to fix this issue is already up for ocata branch but it is abandon now.
Please refer, https://review.openstack.org/#/c/440876/6"
1726244,2017-10-26 10:11:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726244,2017-11-03 19:01:23 UTC,+1
1726244,2019-03-05 21:07:01 UTC,"easier workaround:
workrave --display=:0
(from the askubuntu thread referred to by OP)"
1726247,2018-01-25 16:08:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726257,2017-10-26 01:06:58 UTC,"This problem seems to be the cause of this patch
https://review.openstack.org/#/c/508366/"
1726261,2017-10-25 07:15:14 UTC,Provide proper bug description and logs
1726270,2017-10-23 07:12:14 UTC,"StacktraceTop:
 meta_monitor_manager_handle_get_current_state (skeleton=0x7efbec014ae0, invocation=0x5567b10d6e00) at backends/meta-monitor-manager.c:1362
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffe720b1550, fn=fn@entry=0x7efc108969d0 <meta_monitor_manager_handle_get_current_state>, rvalue=<optimized out>, avalue=avalue@entry=0x7ffe720b1460) at ../src/x86/ffi64.c:525
 g_cclosure_marshal_generic (closure=0x5567af4fd5c0, return_gvalue=0x7ffe720b1720, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=<optimized out>) at ../../../../gobject/gclosure.c:1490
 g_closure_invoke (closure=0x5567af4fd5c0, return_value=0x7ffe720b1720, n_param_values=2, param_values=0x5567b12f1df0, invocation_hint=0x7ffe720b1700) at ../../../../gobject/gclosure.c:804"
1726270,2017-10-24 20:56:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726270,2020-01-24 10:06:13 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1726271,2017-11-21 15:55:30 UTC,"Reviewed:  https://review.openstack.org/515717
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=f7d9d3536776771e878391c676b64d7b1372f95a
Submitter: Zuul
Branch:    master"
1726271,2017-10-27 14:11:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/515717"
1726278,2017-10-23 07:30:14 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1726283,2017-10-23 14:12:53 UTC,"Packaging issue in Debian, ignored git submodule friendsofcake/crud and patched the checks that check it is present"
1726283,2017-10-26 10:52:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726283,2017-11-01 05:59:27 UTC,@steve-gilvarry can you explain your comment? Did you figure out a workaround? I'm not familiar with how these modules are built. I'd be glad to try/test something if there are details.
1726283,2017-11-22 16:16:14 UTC,"any update on this? I can do some tests, if there is a new version available."
1726283,2017-11-29 09:32:28 UTC,The problem is this patch as it removed the packaging of the crud plugin: https://anonscm.debian.org/git/collab-maint/zoneminder.git/commit/?id=2a3db2ae513a64dce5a1123ab3a979b4785ba49e
1726283,2017-11-29 11:39:26 UTC,@Matt N. Any chance for a temporary solution by any chance? Need the damn API so bad :(
1726283,2017-11-30 22:52:09 UTC,@mmn100 thanks for fingering the patch. Perhaps the intent was to split the submodules out as separate packages?
1726286,2020-07-31 18:11:23 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1726286,2017-10-26 08:44:10 UTC,"For me it crashes whenever I open it by double-clicking its icon anywhere Gnome Shell. For some reason it runs more reliably if I start it from a terminal. (I've seen it segfault once that way too, but after running a while.)"
1726286,2017-10-26 08:28:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726286,2017-10-23 08:07:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726286,2017-10-23 08:08:14 UTC,Is it doing it on a specific font or directory?
1726286,2017-10-23 07:57:17 UTC,"StacktraceTop:
 g_type_check_instance_cast (type_instance=0x4238317839080030, iface_type=94623820557152) at ../../../../gobject/gtype.c:4052
 font_view_update_scale_factor (self=0x560f533cc2a0) at ../src/font-view.c:521
 g_closure_invoke (closure=0x560f53493530, return_value=0x0, n_param_values=2, param_values=0x7ffd18415ac0, invocation_hint=0x7ffd18415a40) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x560f530fa140, detail=detail@entry=397, instance=instance@entry=0x560f533cc2a0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffd18415ac0) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x560f533cc2a0, signal_id=<optimized out>, detail=397, var_args=var_args@entry=0x7ffd18415c90) at ../../../../gobject/gsignal.c:3391"
1726286,2017-10-23 08:43:15 UTC,"No, just opening it from (gnome) dash. Actually it crashed only once (at the very first time), last couple of opens were hassle-free."
1726289,2017-10-23 08:09:21 UTC,"There are other issues too. The Onboard shell extension was designed to trap keyboard input signals and show Onboard keyboard instead of Caribou. With GNOME 3.26, it ends up showing both. Will attach screenshot soon."
1726289,2017-10-23 10:08:23 UTC,"        //Main.keyboard.Show(global.get_current_time());
        Main.keyboard.show(global.get_current_time());"
1726289,2017-10-23 10:09:15 UTC,Sorry about the formatting mess. I don't see how to do code formatting in LP.
1726292,2017-11-10 05:56:27 UTC,Tested with locationd snap v4.2.1 (rev 163).
1726292,2017-11-10 05:56:58 UTC,This issue can be marked as Fix Released.
1726299,2018-01-28 14:34:37 UTC,+1
1726299,2018-02-03 13:19:39 UTC,I found a way to make this work!
1726299,2018-02-03 13:21:40 UTC,"Since it appears to work with the above workaround, as far as I'm concerned this bug can be closed."
1726299,2018-02-03 13:39:18 UTC,"Actually, this does work, it's just that the device I used wasn't authorized. Take a look at the comment here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726299/comments/6"
1726299,2018-11-20 20:22:29 UTC,"@whitequark I was struggling to get stuff to work with the Apple Thunderbolt 3 to 2 adapter, but when I replaced it with the Startech Thunderbolt 3 to 2 I got it working. Read about other's recommending it online as well."
1726299,2018-09-03 06:34:18 UTC,"Created attachment 278257
USB PD trace"
1726299,2018-09-01 03:52:34 UTC,"Created attachment 278223
adapter firmware (TI TPS65983)"
1726299,2018-09-01 03:53:46 UTC,"OK, I desoldered the flash and dumped the firmware. The chip is indeed a remarked TPS65983 (possibly TPS65983B, it's not entirely clear) and out of the 1 MiB flash capacity, slightly less than 70 KiB is used by the firmware. Which is still not very small but could be manageable. I've attached the firmware, have fun."
1726299,2018-09-03 08:19:12 UTC,"Created attachment 278265
UCSI trace"
1726299,2018-09-03 11:24:10 UTC,"Created attachment 278267
UCSI altmode support patch"
1726299,2018-01-27 12:18:29 UTC,I can confirm that this is not fixed in kernel v4.15-rc1.
1726299,2018-08-22 14:12:40 UTC,"Sorry, the Dell support thread link in the previous post should be [5]."
1726299,2018-01-22 18:45:40 UTC,I too would like to use a Thunderbolt 2 device using a 3-to-2 adapter.  What is the status of this problem?
1726299,2018-08-22 14:11:00 UTC,"So I've spent way too much time trying to get this adapter to work, and here's what I discovered. I have an XPS 13 9360 laptop, BIOS 2.8.2, Thunderbolt NVM 21.0, and kernel 4.17.14. The Thunderbolt security is disabled in BIOS, and all access control settings are as relaxed as possible."
1726299,2017-11-25 10:53:50 UTC,It seems that the Thunderbolt 3 to 2 adapter is not supported:
1726299,2017-11-29 15:40:36 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1726299,2016-12-06 07:25:34 UTC,"Created attachment 246931
dmesg.log"
1726299,2016-12-29 18:26:30 UTC,"Thanks, Lukas.  Help me understand the scenario here.  It looks like the adapter was hot-added.  If the firmware is responsible for configuring things behind the adapter, there must be a hook where firmware gets invoked.  Is the ACPI Bus Check event that hook?  Does that mean we must use acpiphp (not pciehp) to support these Thunderbolt devices?  I'm trying to figure out if we can log more intelligent messages for this situation.  The current stuff in dmesg is pretty hard to interpret."
1726299,2016-12-29 19:25:43 UTC,"(In reply to Bjorn Helgaas from comment #2)

> Thanks, Lukas.  Help me understand the scenario here.  It looks like the
> adapter was hot-added.
"
1726299,2017-01-03 02:30:32 UTC,"Lukas, thanks for the details and suggestions.
I just want to confirm that you think this issue should be fixed in the BIOS/uEFI, and we don't have to do anything related to the drivers?"
1726299,2017-01-03 10:28:06 UTC,"(In reply to AceLan Kao from comment #4)

> BTW, do you think will it work if I install linux on a Mac machine(which has
> proper EFI driver to handle this device)?
"
1726299,2016-12-28 14:38:38 UTC,According to the dmesg output the adapter only shows up as a USB device.
1726299,2017-01-16 04:59:44 UTC,"(In reply to Daniel Roschka from comment #6)

> (In reply to Lukas Wunner from comment #5)
> > In any case you will need this patch to make Thunderbolt work on the 2016
> > MacBook Pros (the only ones with Thunderbolt 3 so far):
> >
> https://gist.githubusercontent.com/l1k/3ffbd63ac337fa85530f6db3e9ee77e9/raw/
> > 55b2a520ee6d5e802ce599395886f378a42c89d8/0001-thunderbolt-Support-Alpine-
> > Ridge-4C-controller.patch
>
> Any plans to bring that patch upstream?
"
1726299,2017-01-16 20:16:28 UTC,"Unfortunately I currently also don't have access to Thunderbolt 3 accessories. As soon as I get my hands on some, I'll definitely try out, if they work with your patch."
1726299,2017-10-23 12:25:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1726299,2017-11-05 18:34:52 UTC,"$ sudo modprobe firewire_ohci
$ lsmod | grep firewire
firewire_ohci          40960  0
firewire_core          65536  1 firewire_ohci
crc_itu_t              16384  1 firewire_core"
1726299,2017-11-25 10:44:39 UTC,Are there any news on this topic? I want to use my Apple Thunderbolt 3 to Thunderbolt 2 adapter on a Gigabyte Z170N-Gaming 5 mainboard. I can provide the adapter to a developer if this is helpful.
1726299,2017-01-15 21:51:28 UTC,"(In reply to Lukas Wunner from comment #5)

> In any case you will need this patch to make Thunderbolt work on the 2016
> MacBook Pros (the only ones with Thunderbolt 3 so far):
> https://gist.githubusercontent.com/l1k/3ffbd63ac337fa85530f6db3e9ee77e9/raw/
> 55b2a520ee6d5e802ce599395886f378a42c89d8/0001-thunderbolt-Support-Alpine-
> Ridge-4C-controller.patch
"
1726310,2018-09-24 14:46:56 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1726310,2017-10-26 04:34:48 UTC,Set the status to In-progress because this report has an assignee.
1726310,2018-05-14 12:02:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568271"
1726310,2018-05-30 21:52:33 UTC,"Reviewed:  https://review.openstack.org/568271
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=64e76de43dc55e584c100005fa60da50dd06d352
Submitter: Zuul
Branch:    master"
1726310,2018-06-08 12:24:54 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1726310,2018-06-29 12:22:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/579135"
1726310,2018-06-29 12:33:15 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/579136"
1726310,2018-06-29 23:20:53 UTC,"Reviewed:  https://review.openstack.org/579135
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4917d4d0afab6927e0a37290c20bb986ae8f2a41
Submitter: Zuul
Branch:    stable/queens"
1726310,2018-07-08 02:06:12 UTC,"Reviewed:  https://review.openstack.org/579136
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=53fc4ab1ddfd2aba3a32936f9f49b37a6e51a198
Submitter: Zuul
Branch:    stable/pike"
1726310,2018-09-24 14:47:33 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1726314,2017-10-23 09:21:09 UTC,"StacktraceTop:
 gray_set_cell (worker=worker@entry=0x7fffcff3b2f0, ex=ex@entry=22, ey=ey@entry=0) at ./freetype-2.8/src/smooth/ftgrays.c:585
 gray_render_line (worker=0x7fffcff3b2f0, to_x=5664, to_y=0) at ./freetype-2.8/src/smooth/ftgrays.c:885
 gray_line_to (to=<optimized out>, worker=<optimized out>) at ./freetype-2.8/src/smooth/ftgrays.c:1196
 FT_Outline_Decompose (outline=outline@entry=0x7fffcff3b410, func_interface=func_interface@entry=0x7f2718de1c80 <func_interface>, user=user@entry=0x7fffcff3b2f0) at ./freetype-2.8/src/base/ftoutln.c:165
 gray_convert_glyph_inner (worker=worker@entry=0x7fffcff3b2f0) at ./freetype-2.8/src/smooth/ftgrays.c:1710"
1726319,2018-01-07 15:10:08 UTC,"Hi,"
1726319,2018-01-16 23:30:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726319,2018-09-30 06:46:21 UTC,"I can confirm the same issue is happening on 18.04, with Gnome 3.28 and KDE 1.3.1-0ubuntu0.1 amd64, after a fresh install of Gnome and KDE Connect."
1726319,2018-09-30 07:13:38 UTC,forgot to mention I am also using a Samsung S7(SM-g930f).
1726319,2018-09-30 08:15:28 UTC,uninstalling Gnome+Xorg+Wayland+KDE Connect and reinstalling again fixed the KDE issues(and other issues I was having)
1726320,2017-10-24 02:00:05 UTC,Ubuntu purple! :)
1726320,2017-11-01 10:35:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726320,2017-12-14 10:49:28 UTC,I actually think the colors are good as they are. At least the green color should be very bright because of it's unusual placement (on the top of the window instead of on the bottom). We need to draw the user's attention to it.
1726320,2017-12-15 02:13:45 UTC,"I agree, leaving the green would be fine IMHO. But let's keep this bug open because I'm sure those of us who don't mind the green too much also would not mind it changing, depending on what it changed to."
1726320,2017-12-15 09:15:04 UTC,"On Thu, Dec 14, 2017 at 10:49:28AM -0000, Merlijn Sebrechts wrote:

> I actually think the colors are good as they are. At least the green
> color should be very bright because of it's unusual placement (on the
> top of the window instead of on the bottom). We need to draw the user's
> attention to it.
"
1726327,2017-12-21 08:52:30 UTC,I'm affected too... very annoying
1726327,2017-10-27 16:51:38 UTC,This bug was fixed in the package apturl - 0.5.2ubuntu13
1726327,2017-10-23 11:29:32 UTC,"thx, probs a simple fix as in the attached branch"
1726327,2017-10-26 18:17:11 UTC,"Hello Alan, or anyone else affected,"
1726332,2017-10-23 11:54:04 UTC,"Ok. I managed to fix that by getting rid of -Werror, but now I have a new error:"
1726332,2017-10-23 11:57:46 UTC,"not a bug on the Ubuntu package, reassigning to the upstream component instead"
1726332,2017-10-23 12:27:54 UTC,Fixed by commenting out that
1726342,2017-10-23 10:07:23 UTC,"Or maybe/additionally a ""juju status"" option to filter out the output ?"
1726342,2017-10-23 21:26:15 UTC,I would recommend that they be flags to status.
1726350,2017-10-31 12:48:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726352,2018-02-01 14:50:31 UTC,"Perhaps this helps?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/comments/29
->
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/"
1726352,2019-03-08 09:31:34 UTC,"Yes, the crash stopped happening before 18.10."
1726352,2018-02-02 01:43:44 UTC,Launchpad bug 1724439 already covers that.
1726352,2018-02-01 15:48:58 UTC,"By the way, upstream appears to have a fix for this too: https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492"
1726352,2018-01-16 07:19:01 UTC,This looks like https://bugzilla.gnome.org/show_bug.cgi?id=790207.
1726352,2018-08-08 08:05:35 UTC,Looks like this was fixed in Gnome 3.28 ... let's see and this bug can auto-expire if so.
1726352,2017-12-14 10:14:07 UTC,"This issue is also being tracked in:
https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052"
1726352,2017-12-14 10:01:12 UTC,Seems monitor_rect is invalid in my own stacktrace.
1726352,2017-11-15 02:18:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726352,2017-10-23 11:27:38 UTC,"StacktraceTop:
 meta_window_move_resize_request (window=window@entry=0x55b29e7bef30, value_mask=<optimized out>, gravity=1, new_x=<optimized out>, new_y=76, new_width=<optimized out>, new_height=<optimized out>) at x11/window-x11.c:2095
 meta_window_x11_configure_request (window=window@entry=0x55b29e7bef30, event=event@entry=0x7ffc56ec6110) at x11/window-x11.c:2169
 handle_other_xevent (display=display@entry=0x55b29d182a00, event=event@entry=0x7ffc56ec6110) at x11/events.c:1456
 meta_display_handle_xevent (event=0x7ffc56ec6110, display=0x55b29d182a00) at x11/events.c:1784
 xevent_filter (xevent=0x7ffc56ec6110, event=<optimized out>, data=0x55b29d182a00) at x11/events.c:1823"
1726352,2018-01-11 06:24:42 UTC,"Fwiw, this happens every time I turn off the only monitor attached to the computer, and it loses all unsaved data, so for me it's critical - I can't use gnome-shell on that computer."
1726360,2020-05-22 04:17:25 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1726367,2017-11-29 16:50:33 UTC,"Kevin,"
1726367,2017-11-29 16:35:10 UTC,I encountered this same error and was automagically pointed here by the bug reporting software.
1726367,2017-11-07 15:54:50 UTC,"@Tim,
Well that's unfortunate you had troubles with UEFI.  After we can confirm this issue is fixed for you with the proposed fix, I think you should try to re-install with in UEFI mode again.  UEFI mode is preferable as BIOS updates will only be distributed and installed when in UEFI mode.
What problem did you run into?"
1726367,2017-11-06 22:27:19 UTC,"OK, assuming my theory is right proposed fixes available here:
https://github.com/hughsie/fwupd/pull/306"
1726367,2017-11-06 21:18:19 UTC,"OK so I've got another theory.
By chance do you have UEFI capsule updates turned off in BIOS setup?"
1726367,2017-11-07 12:14:18 UTC,"Cool, thanks for looking into it. Yes, I could not install Ubuntu 17.10 without disabling UEFI in the BIOS."
1726367,2017-11-06 19:38:37 UTC,"Yep that's the WD15 dock, thank you very much for confirming.
1. You've never performed a FW update on it in the past right?
2. How technically savvy are you with debian packaging?  If I gave you a patch to try could you apt source the package apply it and try it?"
1726367,2017-11-06 19:16:30 UTC,"It says K17A on the bottom of the dock for ""Reg Model"". It also reads WD15 elsewhere, which I think is the actual model. It is this unit: http://www.dell.com/en-us/shop/dell-business-dock-wd15-with-180w-adapter/apd/450-aeuo/pc-accessories"
1726367,2017-11-06 18:23:07 UTC,"I'm pretty sure it's a TB16 dock from looking at the traces.  Can you reliably reproduce this?  I have some suspicions, but would like to see verbose fwupd output to confirm it if possible."
1726367,2017-11-06 17:46:16 UTC,"Sorry, K17A dock?  Do you mean TB16 dock?"
1726367,2017-10-23 12:11:03 UTC,"StacktraceTop:
 fu_plugin_dell_match_dock_component (name_out=<synthetic pointer>, guid_out=0x7ffdd4b4cee0, query_str=0x6 <error: Cannot access memory at address 0x6>) at ../plugins/dell/fu-plugin-dell.c:134
 fu_plugin_dell_device_added_cb (ctx=<optimized out>, device=0x56246b6e4fa0, plugin=0x56246b6cd500) at ../plugins/dell/fu-plugin-dell.c:337
 g_closure_invoke (closure=0x56246b6b9ea0, return_value=0x0, n_param_values=2, param_values=0x7ffdd4b4d200, invocation_hint=0x7ffdd4b4d180) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x56246b5a3cd0, detail=detail@entry=0, instance=instance@entry=0x56246b57e050, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffdd4b4d200) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x56246b57e050, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffdd4b4d3d0) at ../../../../gobject/gsignal.c:3391"
1726367,2017-11-06 20:32:39 UTC,"The stack trace shows that it's a NULL pointer comparison of a substring, but it's not clear why that is happening.  I can feed your exact data from your dock into the test suite but no segfault."
1726375,2018-01-10 19:20:21 UTC,"I do have the same problem on a cheap VPS by a very popular german hosting company, so it probably affects lots of people. Here's my favorite remedy, simple and effective."
1726375,2018-01-10 19:22:50 UTC,"Oh, and here's a version that should work with even more shells."
1726380,2017-10-23 12:55:03 UTC,Upstream: https://bugzilla.gnome.org/show_bug.cgi?id=784925
1726380,2017-10-23 12:54:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726384,2020-12-16 22:29:19 UTC,This bug was fixed in the package doc-base - 0.11
1726388,2017-10-24 23:23:19 UTC,"StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()"
1726388,2017-10-24 23:23:23 UTC,Thank you for your report!
1726388,2017-10-25 08:59:03 UTC,thank you for your time and commitment good to have people like you out there.
1726388,2017-12-04 21:41:09 UTC,"How does one fix the ""no debug symbol package found for perl-base"" problem, which is preventing this from being considered a valid issue?"
1726389,2018-07-10 13:38:55 UTC,maybe duplicate to https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1778636 ?
1726389,2021-01-10 23:47:05 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1726390,2020-09-12 08:17:17 UTC,Closing because INVALID: Can't replicate.
1726393,2017-10-23 13:30:07 UTC,This change was made by a bot.
1726393,2017-10-23 14:11:23 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1726393,2017-10-27 09:39:32 UTC,Wi-fi would not connect with the latest kernel.
1726393,2017-10-30 07:42:25 UTC,I have had almost identical behavior with a completely different wifi setup. My card is the following:
1726393,2017-10-30 07:43:20 UTC,"And FWIW, I did try the generic upstream kernel. Exact same behavior."
1726395,2017-10-25 13:21:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726396,2017-11-29 06:00:36 UTC,"Hi,"
1726396,2017-11-29 11:07:57 UTC,"Hi,"
1726396,2017-11-04 07:14:57 UTC,"Hi Roary,"
1726399,2017-11-09 12:53:06 UTC,"Reviewed:  https://review.openstack.org/514315
Committed: https://git.openstack.org/cgit/openstack/ospurge/commit/?id=c2d1728deedf7e2ca03e6a55f4de59d4d3ab1dde
Submitter: Zuul
Branch:    master"
1726399,2017-11-13 13:11:30 UTC,"Reviewed:  https://review.openstack.org/518953
Committed: https://git.openstack.org/cgit/openstack/ospurge/commit/?id=af88d16028e2e266a62028fe1927c61d80c68b8c
Submitter: Zuul
Branch:    master"
1726399,2017-11-13 13:11:24 UTC,"Reviewed:  https://review.openstack.org/514319
Committed: https://git.openstack.org/cgit/openstack/ospurge/commit/?id=c1d38f741bafd4c27fd525aff79e787e78e594f2
Submitter: Zuul
Branch:    master"
1726399,2017-11-10 15:47:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/518953"
1726399,2017-11-09 18:04:00 UTC,"Reviewed:  https://review.openstack.org/514336
Committed: https://git.openstack.org/cgit/openstack/ospurge/commit/?id=b73c938a93dc90839515df1dae285e9dd492aca9
Submitter: Zuul
Branch:    master"
1726399,2017-11-09 14:50:21 UTC,"Reviewed:  https://review.openstack.org/514318
Committed: https://git.openstack.org/cgit/openstack/ospurge/commit/?id=17162e650699a92c1a510cac572835aa188d5de2
Submitter: Zuul
Branch:    master"
1726399,2017-11-09 14:40:45 UTC,"Reviewed:  https://review.openstack.org/518722
Committed: https://git.openstack.org/cgit/openstack/ospurge/commit/?id=50560fc91cb880b7065671a28e945242b4797998
Submitter: Zuul
Branch:    master"
1726399,2017-11-09 12:49:50 UTC,"Reviewed:  https://review.openstack.org/514320
Committed: https://git.openstack.org/cgit/openstack/ospurge/commit/?id=67fc801e699d8b19031b5b91c30017e6541a61d7
Submitter: Zuul
Branch:    master"
1726399,2017-10-23 14:39:00 UTC,"For type annotations, I wrote https://review.openstack.org/514336 which moves type annotations to new .pyi files to keep them."
1726399,2017-10-23 14:44:20 UTC,I finished to published my patches.
1726399,2017-10-23 14:37:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/514336"
1726399,2017-10-23 13:48:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/514320"
1726399,2017-10-23 13:44:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/514319"
1726399,2017-10-23 13:34:56 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/514318"
1726399,2017-10-23 13:26:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/514315"
1726399,2017-11-09 12:30:48 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/518722"
1726402,2020-04-06 10:02:36 UTC,"Nvidia user here, nope, it happens also with Xorg. And like in #8 I also see/don't see them randomly. For example, right now they are visible."
1726402,2020-03-11 19:33:47 UTC,"Well, more accurately, I _sometimes_ see it in Focal. The icons in the top bar come and go seemingly at random i.e. I can't currently identify what makes them disappear."
1726402,2020-03-11 19:52:35 UTC,#8 same issue here on Ubuntu 19.10.
1726402,2020-03-11 19:33:01 UTC,I still see it in current Focal.
1726402,2020-04-06 09:31:13 UTC,Does the problem only happen in Wayland sessions? (see also bug 1870795)
1726402,2018-02-18 15:39:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726402,2017-10-26 16:52:18 UTC,"""top bar"" means the bar at the top of my machine, you know, the one with the time, wifi icon, battery icon, sound icon, etc. in it."
1726402,2017-10-26 16:25:45 UTC,"When you write ""top bar"" you mean indicator?"
1726402,2017-10-26 13:19:24 UTC,Relevant:
1726402,2020-03-11 19:22:40 UTC,"This should be fixed by now, no?"
1726405,2017-10-23 13:36:11 UTC,"It's not so severe since apturl is still installed by default and seems to take precedence, meaning that apt://foo does actually still work."
1726405,2017-10-23 19:19:55 UTC,"Think these are private at the minute, but for the record"
1726405,2018-03-17 17:19:42 UTC,the issue described there has been fixed right?
1726422,2017-10-24 01:54:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514497"
1726422,2019-12-04 08:58:35 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1726422,2019-12-04 08:58:44 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/514497
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1726431,2017-10-24 14:24:51 UTC,"Thank you! (and yay for open source in education!) If you / your daughter / her class mates or the teacher have any comments or questions (other than bug reports), feel free to let us know on the forums [1], in the chat [2], on the user mailing list [3] or in the answers section here [4] (whichever you / they prefer)."
1726431,2017-10-24 06:28:18 UTC,"It is a 9th grade introduction to digital arts class.  The part of this
whole issue is my daughter is the only one in the class that is apparently
having any kind of problem. It was also a little bit of an issue that all
of the course work was written for an older version, but the teacher
""required"" the latest version even though he had not used it yet.  So far
version 91 seems to work well for my daughter, which has alleviated some
stress from her life."
1726431,2017-10-23 17:25:39 UTC,"(very) Offtopic: Jamie, that's cool that Inkscape is used for education :) What kind of class is this?"
1726431,2017-10-23 16:37:16 UTC,"As this is the program my daughter is using for a class, she has to follow
a specific set of instructions in a specific order, which is prescribed by
her instructor.  Part of each assignment she has had to date is using the
triangle in/out function which begins the problem."
1726431,2017-10-23 15:33:44 UTC,"Correction, we attempted modify a file and most of the image disappeared in
version 91 so we're still having issues.  I will keep you posted.  Attached
is the file we were trying to work with."
1726431,2017-10-23 15:28:13 UTC,"Eduard,"
1726431,2017-10-23 15:05:39 UTC,Do you have a sample file that reproduces this issue reliably? If so could you attach (part of) it?
1726431,2017-10-23 16:15:52 UTC,"OK, thanks for the example.
I can confirm this is a bug. It might be a duplicate of bug #1687514 but I'm not 100% sure, so I'll leave this one open for now."
1726432,2019-10-31 11:45:08 UTC,I can confírm this behaviour
1726432,2020-05-06 23:03:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726432,2020-05-06 23:05:15 UTC,I can confirme the issue on ubuntu 18.04 and PHP 7.2.24-0ubuntu0.18.04.4 (cli) (built: Apr  8 2020 15:45:57) ( NTS ).
1726432,2020-06-11 11:38:16 UTC,"Confirmed on ubuntu 18.04
PHP
PHP 7.2.24-0ubuntu0.18.04.3 (cli) (built: Feb 11 2020 15:55:52) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.24-0ubuntu0.18.04.3, Copyright (c) 1999-2018, by Zend Technologies"
1726432,2020-06-11 16:51:57 UTC,"upgrading to php7.4 via
sudo add-apt-repository ppa:ondrej/php"
1726434,2017-10-25 18:00:16 UTC,"I can confirm I also get errors trying this on the same versions, though my errors are different [1]. On upstream however, this is not reproducible, so it appears to be fixed going forward."
1726434,2017-10-25 18:33:34 UTC,"Ignore my paste, realized afterwards what those were :)"
1726434,2017-10-26 12:19:29 UTC,Good to know.
1726439,2017-10-23 20:32:24 UTC,"On Mon, Oct 23, 2017 at 08:09:04PM -0000, Egmont Koblinger wrote:

> Linux desktop has two copy-paste buffers, the Primary (aka. Selection)
> [usually selected with the mouse and inserted with middle clicking or
> Shift+Insert] and the Clipboard [usually Ctrl+C Ctrl+V, but also ""Copy"",
> ""Paste"" and similar menu entries].
>
> It sucks big time that Linux desktop couldn't overcome this in the past
> few decades and unify to have only one.
>
> But in the mean time you shouldn't mix the two methods and expect to
> work. It might work here and there, but don't expect it to work
> everywhere. It's not gnome-terminal to blame, but the entire Linux
> desktop world.
>
> Use either of them, but only of the two methods at a time.
>
> gnome-terminal's ""Copy Link Address"" right-click menu item copies to the
> Clipboard, while Shift+Insert pastes Primary.
"
1726439,2018-02-05 14:58:17 UTC,This continues to be a real pain in day-to-day.  Can we please fix this gnome-terminal regression?
1726439,2017-10-23 20:48:28 UTC,I can't recall gnome-terminal changing anything hereabouts.
1726439,2017-10-23 20:30:22 UTC,Missing word:
1726439,2017-10-23 15:11:34 UTC,Shift-Insert does paste what I've copied in Google Chrome (from upstream) and in gedit.
1726439,2017-10-23 15:00:01 UTC,UpgradeStatus: Upgraded to artful on 2016-12-05 (321 days ago) -> really?!
1726439,2017-10-23 14:58:22 UTC,"I've also seen this with ""Copy E-mail Address""."
1726439,2017-10-23 20:09:04 UTC,"Linux desktop has two copy-paste buffers, the Primary (aka. Selection) [usually selected with the mouse and inserted with middle clicking or Shift+Insert] and the Clipboard [usually Ctrl+C Ctrl+V, but also ""Copy"", ""Paste"" and similar menu entries]."
1726441,2017-11-09 17:44:56 UTC,Attached is a patch pulled from git that fixes this.
1726441,2017-11-10 04:30:53 UTC,"The attachment ""Swap order of function name/arguments"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1726441,2017-12-21 22:50:30 UTC,I've sponsored this but changed the maintainer to ubuntu-devel-discuss instead of an individual.  Thanks for working on it!
1726441,2017-12-21 22:53:28 UTC,Its not immediately clear to me what the test case is though. Could somebody add SRU information to the bug description? See the following for details:
1726441,2018-01-02 12:08:02 UTC,"The upload in the queue refers to bug 1728441 instead of this bug, which is wrong, so rejecting."
1726453,2020-03-12 05:55:47 UTC,Can you please try a newer Ubuntu version and tell us if the problem is still present?
1726453,2020-05-12 04:17:20 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1726462,2018-11-29 07:02:02 UTC,Still facing this issue?
1726462,2020-01-25 14:06:03 UTC,"Based on the long inactivity I assume, the problem with gate jobs got resolved. If you feel like it's not, feel free to reopen the issue again."
1726462,2018-12-13 09:47:14 UTC,"for me too, it seems cinder or test bug. need further investigation."
1726462,2018-12-13 09:46:59 UTC,I marked it as invalid for neutron as it looks that it's clearly Cinder issue
1726462,2017-10-24 13:52:34 UTC,Adding a 7 days window to the query:
1726462,2018-04-23 09:24:04 UTC,"Currently 38 hits in the last 7 days, but mostly for other jobs, so I don't think that this is related to Neutron, rather Tempest and/or Cinder."
1726462,2017-10-27 19:53:36 UTC,"There does seem to more occurrences on the 21st as well from Miguel's link, though no more since then as of now. Seems like this is recurring at least, but seems to be infrequent."
1726462,2018-11-30 12:30:13 UTC,Current count 25 hits in 7 days.
1726464,2018-09-11 10:41:48 UTC,This used to be a configurable feature in Unity... I'm not sure if this is a bug or just I can't find the option any more...
1726464,2018-04-30 11:28:13 UTC,Everyone here seems to be bothered by sticky edge and want it gone but I'm experiencing and wanting the exact opposite.
1726464,2018-09-12 01:47:06 UTC,If the problem is the Ubuntu Dock then please report a bug to its developers here:
1726464,2017-11-29 15:11:50 UTC,"Sticky edges make sense when the dock is mounted to the edge shared by two screens. However, the sticky edge remains active even with the dock is mounted to the bottom of the screen or the edge opposite the shared edge between screens. There's no reason to hang the mouse when there's no dock there. I'm experiencing this when simply moving the mouse between screens as well as dragging windows and other UI elements."
1726464,2019-01-24 03:58:21 UTC,Ghetolay
1726464,2019-06-27 18:50:27 UTC,"Had the same (or just a similar?) problem:
- auto-hide Dock enabled
- When I move the mouse between monitors the mouse sticks at the (left) dock of the right screen."
1726464,2019-08-28 10:41:04 UTC,"The fix from #17 is not working for me, because I could not find any ""Dock"" settings via the ""Activities"" ""Overview""."
1726464,2019-01-24 03:51:31 UTC,Im not sure if its barrier or sticky that comes into play. I was able to disable it on 16.04 as described above.
1726464,2017-11-12 19:44:27 UTC,Would be nice to disable sticky edges and/or the barrier while dragging a window.
1726464,2017-10-24 02:54:11 UTC,"Is this the sticky edges feature, or generally a cursor barrier problem? Are you dragging a window when the problem happens?"
1726464,2017-11-12 12:54:40 UTC,"@Rasmus: what's ""this""? You mean just allowing the user to trigger the dock by keyboard shortcut? Or is there some smarter/more optimized mouse gesture to trigger the dock in Unity?"
1726464,2017-11-05 20:23:11 UTC,This has worked in Unity for many years so it's certenly not impossible. Now I don't know the code of neither Unity nor Gnome and it may well be so that Gnome can not support it but the concept itself is very possible.
1726464,2017-11-05 16:30:53 UTC,"What about using the Super key to call up the dock, for those that need/want access to the dock?"
1726464,2017-11-05 16:28:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726464,2017-11-05 00:50:30 UTC,"This is due to the barriers that are in place to be able to trigger the dock when in autohide. Otherwise, it is virtually impossible to position the mouse in the exact pixel at the screen edge."
1726464,2017-10-28 20:24:53 UTC,I realized that this is only when I have the dock set to auto hide. With always visible it's possible to move the cursor to the other screen without issues.
1726464,2017-10-28 15:38:53 UTC,">Is this the sticky edges feature, or generally a cursor barrier problem?
"
1726464,2017-11-12 13:06:20 UTC,"In Unity it's still triggered by the mouse when placing it near the edge of
the screen. I don't know how many pixels is used but I have never felt that
it has been hard to trigger it."
1726466,2017-10-24 20:21:01 UTC,https://github.com/elementary/files/issues/187
1726466,2017-10-23 18:01:32 UTC,This needs to be raised as an issue against Files on GitHub:
1726466,2017-10-23 18:09:26 UTC,"That is, the ""Open in"" issue."
1726469,2018-05-25 13:52:47 UTC,I created some non-cataloged types in a master sandbox and they are indeed not in alphabetical order.
1726472,2017-10-23 16:50:58 UTC,please test. thanks (Be aware: version 1.1.2 nightly build!)
1726476,2018-10-05 20:58:06 UTC,"To expand on the previous comment, the issue can be resolved post boot by running update-grub which will fill out the missing values on the search line. It appears the build process is either not running update-grub or it is using a default grub template that is missing the appropriate data."
1726476,2020-04-29 19:47:43 UTC,When I set admin_pass: <password> in coud meta file it disapeared. This is a local run in kvm.
1726476,2019-11-15 16:59:41 UTC,I saw this pop up again in a lxd --vm demo yesterday - any chance we can get it addressed this cycle? :) Happy to help w/ the testing where possible..
1726476,2020-05-25 11:53:53 UTC,I also experience this using the bionic cloudinit image:
1726476,2018-07-04 10:18:35 UTC,"I've encountered this too, tracked it down to a problem in the root filesystem's grub.cfg, it contains the line"
1726476,2019-08-08 14:45:58 UTC,"This is strictly an image build issue; livecd-rootfs diverts all of grub-probe in the divert_grub() function, but it really should only do this for 30_os-prober."
1726476,2018-05-01 20:33:36 UTC,"The problem is apparently ""only cosmetic"", since the boot proceeds anyway, but it really would be nice to fix as it impacts both x86 and ARM uefi images."
1726476,2018-03-24 03:55:07 UTC,Has anyone found a way to workaround this problem?
1726476,2018-03-11 17:41:50 UTC,"changed bug title, since this isn't an ARM-specific issue"
1726476,2018-03-09 14:28:03 UTC,Also reproduced with http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-uefi1.img
1726476,2018-05-02 14:49:10 UTC,"It is cosmetic but there is work to address this.  Work was blocked on release since we were too close to GA.  The change will impact all cloud-images so this requires extensive testing, so I do not have an ETA for a fix."
1726483,2017-11-16 18:34:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726484,2017-10-23 17:05:20 UTC,"StacktraceTop:
 std::__atomic_base<int>::load (__m=std::memory_order_acquire, this=<optimized out>) at /usr/include/c++/7/bits/atomic_base.h:396
 QAtomicOps<int>::loadAcquire<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:239
 QBasicAtomicInteger<int>::loadAcquire (this=<optimized out>) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:105
 QFreeList<void, QtTimerIdFreeListConstants>::next (this=<optimized out>) at ../../include/QtCore/5.9.1/QtCore/private/../../../../../src/corelib/tools/qfreelist_p.h:240
 QAbstractEventDispatcherPrivate::allocateTimerId () at kernel/qabstracteventdispatcher.cpp:93"
1726485,2017-11-16 11:47:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726490,2017-11-04 07:21:40 UTC,Probably very easy to implement as an additional input value type. Pull request welcome.
1726497,2021-02-24 03:38:17 UTC,No crashes reported after 19.04 so consider it fixed.
1726497,2018-01-04 06:53:57 UTC,This issue is also being tracked in: https://errors.ubuntu.com/problem/c459edaa2be8280fd77029eaf8d7b26faa8083e9
1726497,2017-10-23 17:36:45 UTC,"StacktraceTop:
 wl_abort (fmt=fmt@entry=0x7f93cf3c7a50 ""Error marshalling request: %s\n"") at ../src/wayland-util.c:419
 wl_proxy_marshal_array_constructor_versioned (proxy=proxy@entry=0x55acc0f42a50, opcode=opcode@entry=0, args=args@entry=0x7ffcd315ecf0, interface=interface@entry=0x0, version=3) at ../src/wayland-client.c:653
 wl_proxy_marshal_array_constructor (proxy=proxy@entry=0x55acc0f42a50, opcode=opcode@entry=0, args=args@entry=0x7ffcd315ecf0, interface=interface@entry=0x0) at ../src/wayland-client.c:599
 wl_proxy_marshal (proxy=0x55acc0f42a50, opcode=opcode@entry=0) at ../src/wayland-client.c:696
 wl_data_device_start_drag (serial=543, icon=0x55acc1b930f0, origin=0x0, source=0x55acc1e55da0, wl_data_device=<optimized out>) at /usr/include/wayland-client-protocol.h:2551"
1726497,2018-01-04 06:53:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726515,2017-10-23 17:56:07 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1726515,2017-10-23 18:00:07 UTC,This change was made by a bot.
1726516,2018-07-01 20:29:36 UTC,I have the same bug and can confirm the following within several systems:
1726516,2020-08-31 01:34:09 UTC,The bug is still present Ubuntu 20.04.
1726516,2019-11-06 01:34:23 UTC,"Yea this is still happening, I have 18.04.2 LTS.  Actually there's another design problem with this- the little window isn't wide enough; it has to ""..."" and so I can't see the transfer rate. There's no way to adjust the size of the little mini window unlike an actual window."
1726516,2019-01-04 01:33:52 UTC,Reproduction and unexpected user experience details:
1726516,2018-12-27 00:24:46 UTC,add Ubuntu 18.10
1726516,2018-11-07 19:50:34 UTC,Still happening on Ubuntu Budgie 18.10...
1726516,2018-10-10 16:06:15 UTC,This is still happening. Ubuntu Budgie 18.04
1726516,2018-06-29 19:45:19 UTC,"I forgot to mention, that I am using Ubuntu Budgie 18.04."
1726516,2018-06-29 19:40:20 UTC,This still exists in 18.04.
1726516,2018-03-02 21:58:19 UTC,"On the System 76 customized version of 17.10 there is a ""pie"" graph symbol in the Nautilus top bar that provides access to the progress indicator."
1726516,2017-11-28 04:36:58 UTC,I filed an upstream issue: https://gitlab.gnome.org/GNOME/nautilus/issues/142
1726516,2017-10-24 20:17:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726516,2017-10-24 16:30:01 UTC,"@seb128
Yeah ofcourse the circle appears sometimes.
Although, the circle icon on the top of the window doesn't appear always (most of the time) when copying/moving large files from one media/location to another."
1726516,2017-10-23 19:08:21 UTC,"Thank you for your bug report, that's not a bug though but an upstream design decision. The copy indicator is a circle icon in the top bar, you can click on it to have the details of the copy.
The file on right clicking is another problem see bug #1632027"
1726516,2017-10-23 18:46:38 UTC,"I am having the same issue here in Ubuntu Budgie 17.10.
The indiactor (progress bar) doesnt show up when copying files (mostly large files) most of the time. Only shows up sometimes maybe by luck. Have reinstalled the system twice, yet to no avail.
Hoping it to be fixed asap."
1726516,2017-10-23 18:41:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726522,2017-10-23 18:17:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726525,2017-10-24 16:36:48 UTC,Yup. I'll leave this here for now. At some point it would be nice to have this work without the wrapper clutter.
1726525,2017-10-24 14:40:27 UTC,"Ok, I created this bug report, is this the right place ?
https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1726889"
1726525,2017-10-24 14:22:55 UTC,"Yeah, terminal.wrapper was the way I fixed the blurry icon in the past. However... The packagers for some reason think it is unnecessary, and remove it from the Ubuntu provided packages. This is why you don't have it, and why you are seeing blurry icons. You need to flag it with the packager and point to these two bug reports, and why it's needed. Or someone who understands why it happens needs to come up with a fix that works without the wrapper, but I couldn't get to the bottom of that at the time."
1726525,2017-10-24 12:33:11 UTC,Let me know if I can do other tests to identify the issue.
1726525,2017-10-24 12:28:33 UTC,"The problem doesn't happen in Xorg, but one strange thing I noticed : it is not the same icon that is used when launched with `x-terminal-emulator` and with `terminator`"
1726525,2017-10-24 09:13:36 UTC,"I checked, the links I have are :
/usr/bin/x-terminal-emulator -> /etc/alternatives/x-terminal-emulator
/etc/alternatives/x-terminal-emulator -> /usr/bin/terminator"
1726525,2017-10-23 22:36:56 UTC,Random comments/thoughts:
1726525,2017-10-24 12:31:00 UTC,Same bug as here https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1067287
1726541,2017-10-23 19:10:10 UTC,"StacktraceTop:
 gvdb_table_lookup (file=file@entry=0x7f9764006b60, key=0x7f976800bac0 ""http://www.w3.org/2000/01/rdf-schema#Resource#name"", type=type@entry=118 'v') at gvdb-reader.c:263
 gvdb_table_get_value (file=0x7f9764006b60, key=<optimized out>) at gvdb-reader.c:439
 tracker_ontologies_get_class_value_gvdb (ontologies=ontologies@entry=0x7f9770009630, uri=uri@entry=0x7f976800ba80 ""http://www.w3.org/2000/01/rdf-schema#Resource"", predicate=predicate@entry=0x7f9783b5e557 ""name"") at tracker-ontologies.c:684
 tracker_ontologies_get_class_string_gvdb (ontologies=ontologies@entry=0x7f9770009630, uri=uri@entry=0x7f976800ba80 ""http://www.w3.org/2000/01/rdf-schema#Resource"", predicate=predicate@entry=0x7f9783b5e557 ""name"") at tracker-ontologies.c:698
 tracker_ontologies_get_class_by_uri (ontologies=ontologies@entry=0x7f9770009630, class_uri=class_uri@entry=0x7f976800ba80 ""http://www.w3.org/2000/01/rdf-schema#Resource"") at tracker-ontologies.c:219"
1726542,2017-10-24 11:52:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726542,2017-10-31 18:08:42 UTC,"Ubuntu 16.10.3 LTS also confirmed for new Nvidia driver.
Ge force GT 640 PCIe SSE2, Intel core i3-4160, Asrock Z97 Extreme 6"
1726542,2017-11-02 21:55:32 UTC,Confirmed for Ubuntu 16.10.3 LTS.
1726542,2017-11-02 21:57:58 UTC,This proposes a fix: https://88plug.com/linux/nvidia-384-libegl-so-1-is-not-a-symbolic-link-solved/
1726545,2018-12-20 19:25:57 UTC,Still a problem in Ubuntu 18.04.
1726545,2019-08-12 01:59:45 UTC,"And in Ubuntu 19.04.  This is getting old.  Maybe wayland should relent from their purist stance (after all Unix always allowed root to do absolutely anything to the file system, and that's the keys to the kingdom).  Maybe Ubuntu should accept the workaround GParted implements.
But neither side wants to compromise their principals, resulting in a system that's not self-consistent."
1726545,2019-03-08 08:36:32 UTC,Still a problem in Ubuntu 18.10.
1726545,2018-02-08 18:05:55 UTC,The upstream GParted team added a work-around to version 0.30.0 to enable it to run seamlessly under Wayland.
1726545,2017-10-23 20:52:49 UTC,"Thanks for reporting. It's already known - see bug 1713313.
Please mark as duplicate (I got timeout issue)."
1726545,2017-11-10 23:53:44 UTC,For reference: Phillip reported the timeout as bug #1731268
1726545,2017-11-09 13:43:36 UTC,I keep getting a timeout as well.
1726545,2017-10-24 15:23:28 UTC,An interim fix is available in the upstream GParted 0.30.0 version.
1726545,2018-02-07 20:34:52 UTC,"Hello, I was wondering if this bug was fixed either on Gparted or on Ubuntu Wayland end? I have a workaround I would like to remove if so as its a security risk(the workaround)."
1726548,2019-02-28 09:17:11 UTC,"I have this issue on a desktop connected to a Dell 28"" at a resolution of 3840x2160 and scale of 200%. Running `gsettings set org.gnome.desktop.interface scaling-factor 1` (or `2`) doesn't do the trick."
1726548,2019-05-04 18:49:04 UTC,Same thing here. Here are before/after screenshots.
1726548,2019-06-26 21:54:54 UTC,Having the same issue here on a Dell Inspiron both when witha 4k display running at 1080p. Bug shows up with intel or nvidia graphics enabled.
1726548,2019-10-26 15:43:14 UTC,"Thinkpad X1 Carbon gen3, Ubuntu 19.04 same issue here as Daniel Zabari (danieldaz)."
1726548,2019-11-07 16:53:58 UTC,I can confirm for Ubuntu 19.10 doing
1726548,2019-12-10 19:25:53 UTC,"This was affecting me both when resuming from suspend, as well as when resuming from lock screen. I'm running a Dell XPS 13 9370 under Ubuntu 19.10, with two UHD displays connected via a dock. I wasn't necessarily seeing screen resizing so much as anything on a secondary screen was being closed."
1726548,2020-04-11 01:28:46 UTC,"Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1726548,2020-06-10 04:17:41 UTC,[Expired for ubuntu-gnome-meta (Ubuntu) because there has been no activity for 60 days.]
1726548,2020-10-03 19:36:55 UTC,"I can confirm, that this bug still exists on Ubuntu 20.04. I recently switched to Manjaro (currently 20.1.1) with the same behavior."
1726548,2020-10-06 16:52:51 UTC,"Some version of that bug exists on Ubuntu 20.04 as well. I have a 4k monitor and I have set the display scale to 200% in the Ubuntu Settings. After the monitor sleep/resume, the Google Chrome window scaling is wrong. The size of the window is the same as it was before but the contents is drawn with 100% scaling. I mean the fonts are very small. After the window is moved, the scaling is corrected to 200%. I even don't have to restart the Chrome, just a simple move or resize window operation fixes the problem."
1726548,2019-01-17 19:52:26 UTC,"Running the command @peteh-sapros suggested fixed the problem for me as well (Lenovo X1 carbon 5th gen, Ubuntu 18.04)."
1726548,2019-11-11 20:25:18 UTC,Confirming that executing
1726548,2019-01-13 20:12:40 UTC,"I was also having this problem on a System 76 laptop using Wayland with a hidpi screen (3200x1800) and scaling set to 150%. I was able to fix it by doing:
gsettings set org.gnome.desktop.interface scaling-factor 1"
1726548,2019-11-02 17:46:03 UTC,Actually `gsettings set org.gnome.desktop.interface scaling-factor 1` appears to have done the trick!
1726548,2018-10-09 17:58:41 UTC,"I'm seeing this on my Lenovo Thinkpad X1 Carbon. The window resizes very strangely, like it's zoomed in at the top left corner and then a normal size along the rest of the screen. Definitely happens with nautilus and default document viewer. Happens when I close the lid and reopen it. I attached a screenshot, figure we may as well have one."
1726548,2017-10-23 22:39:25 UTC,Just noticed that the issue seems to be only affecting certain apps (Firefox and Tilix so far) and only if the laptop is being put to sleep closind the lid.
1726548,2017-11-18 15:00:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726548,2017-11-18 15:02:39 UTC,I am seeing the same on my Thinkpad T570 with a 4k screen running at 1080p resolution.
1726548,2018-02-19 17:05:08 UTC,"I've just started noticing this behaviour as well, particularly with Firefox, after switching from Wayland to Xorg on a fresh install of 17.10, gnome-shell 3.26.2-0ubuntu0.1, 1920x1080."
1726548,2018-02-22 18:58:57 UTC,"I'm also seeing this with Ubuntu 16.04 and emacsclient -c (Emacs 24.5.1) on a Dell Precision Tower 3620 - Intel® HD Graphics 630 (Kaby Lake GT2), Samsun 28"" monitor 3840x2160 with ""Scale for menu and title bars"" set to 1.5."
1726548,2018-04-30 05:23:28 UTC,"I am experiencing this bug on Ubuntu 18.04, running on a ThinkPad T470s, after setting the 2560x1440 display resolution to 100% (no pixel doubling).  It's as if while the computer has been asleep, the display has been re-sized to 200% (pixel doubled), forcing all the existing windows to be shrunk to fit."
1726548,2017-10-23 19:25:52 UTC,"Sorry, forgot to add screen is a hdpi screen."
1726548,2018-05-08 03:12:40 UTC,Same symptoms as others: Firefox and terminal windows (at least) get resized after I leave my laptop lid closed and then wake it up again. I was able to reproduce the issue by closing the laptop lid for maybe 10 seconds and then opening it again.
1726548,2018-09-21 12:03:37 UTC,"I am also seeing this on a Thinkpad T480 running Bionic, with X-Windows. The laptop has an Nvidia optimus card, for which I've setup proprietary drivers and prime profiles using my package manager. The problem occurs with both Intel graphics and on the Nvidia gpu."
1726548,2018-07-23 17:49:51 UTC,This bug affects me as well.
1726548,2018-12-18 12:30:38 UTC,I have a Thinkpax X1 carbon gen 4 - and this is happening to me as well.
1726548,2018-06-01 14:29:35 UTC,I'm having the same problem as Zane Selvans.  Dell XPS9360 with 3200 x 1800 resolution.
1726548,2018-06-25 10:54:42 UTC,"Same experience; System76 Oryx PopOS in LoDPI mode— gvim, atom, and others were at twice the size they ought to be.  Firefox wasn't resized but it crashed trying to leave this remark."
1726550,2017-12-20 16:33:43 UTC,I tested ufw on Xubuntu 17.10 and it requires the same additional iptables rule to allow passive ftp to work.  Up until recently I was running a Ubuntu server 16.04LTS that did not have this problem.
1726550,2017-12-20 20:24:18 UTC,"Thanks for the bug and additional information! We need to adjust the documentation for this, with common examples. You asked specifically about where to put your rule. See 'man ufw-framework'. You'll likely want to add something like this to the end of /etc/ufw/before.rules, after the COMMIT line:"
1726550,2017-12-20 20:24:53 UTC,"I forgot to mention, after doing the above, run 'sudo ufw reload'."
1726550,2017-12-21 20:02:30 UTC,Glad that worked for you. :)
1726550,2018-07-24 13:45:04 UTC,"FYI, this is being worked on for an upcoming 0.35.1."
1726550,2018-12-14 21:51:33 UTC,0.36 was released without this feature. It's now planned for 0.36.1.
1726550,2019-09-21 21:50:32 UTC,I was trying to configure a RaspberryPi running Buster today for passive FTP and discovered your excellent patch above does not work any more.  My ufw version is 0.36.  I know you guys have probably been really busy with the change to nft and don't want to bug you but is there any chance you could give me a workaround for Buster like the one for Stretch until the permanent fix is in?  The rules in before.rules all look like the old iptables rules but I'm not sure whether my configuration is using nft or iptables.  I did make a syntax error in before.rules and it was caught when ufw was attempting to load.  So it is reading those rules.
1726550,2019-09-22 14:14:23 UTC,Kindly disregard my last post.  Seems there was some operator error going on.  Everything is working just fine.
1726550,2017-12-21 18:33:23 UTC,"Thanks, that works perfectly."
1726554,2017-10-23 19:57:15 UTC,"StacktraceTop:
 get_device_description (upower=0x5632143f2940, device=device@entry=0x563214458210) at xfpm-power-common.c:358
 power_manager_button_update_device_icon_and_details (button=0x563214442100, device=0x563214458210) at ../power-manager-button.c:382
 g_cclosure_marshal_generic_va (closure=<error reading variable: Cannot access memory at address 0xffffffffffffff40>, return_value=<error reading variable: Cannot access memory at address 0xffffffffffffff28>, instance=<optimized out>, args_list=<optimized out>, marshal_data=<optimized out>, n_params=<error reading variable: Cannot access memory at address 0xffffffffffffff5c>, param_types=<error reading variable: Cannot access memory at address 0x10>) at ../../../../gobject/gclosure.c:1619"
1726554,2017-10-24 14:45:28 UTC,Update -- problem has not occurred on subsequent re-boots after the first.  No other changes made to system.
1726557,2018-02-07 21:29:44 UTC,"We'd like to see patrons be able to set their own default search options for just about everything -- really, I'd like them to set defaults for everything we show on the Advanced Search screen, including Exclude electronic resources, group formats and editions, and an initial scope."
1726557,2017-10-23 20:22:41 UTC,"I agree. We've also talked here about other search preferences people may set, such as default language."
1726561,2018-04-07 08:57:49 UTC,"Hello. I am working again on this issue. pipenv is getting a lot of attention and its core team grew a lot, and is now officially endorse by Pypa, the package authority. I use pipenv with pbr everyday in our our internal packages, they both work great together but without official support of pipfile, I have to use pipenv-to-requirements [1] in order to have dependencies of libraries seen and properly handled by pbr."
1726561,2017-12-01 01:23:29 UTC,Proposal for this support: https://review.openstack.org/#/c/524436/
1726561,2017-11-04 11:11:40 UTC,"Hello. Being working with PBR and pipfile on my project, only solution so far has been to generate requirements.txt and requirements-dev.txt form the Pipfile (see as example: https://github.com/Stibbons/dopplerr)"
1726588,2017-10-23 21:05:34 UTC,This issue was fixed in the openstack/release-test 0.10.1 release.
1726588,2017-10-23 23:17:15 UTC,This issue was fixed in the openstack/release-test 0.10.2 release.
1726588,2018-05-10 17:14:03 UTC,Confirming to remove this from the untriaged list.
1726589,2017-10-23 20:55:26 UTC,"Thanks for reporting. It's already known - see bug 1713313.
Please mark as duplicate (I got timeout issue)."
1726589,2017-10-23 22:04:45 UTC,I can't. I got the same timeout error.
1726589,2017-10-23 22:09:58 UTC,Why has this been released without a fix to this bug I mean the 1713313 bug ??
1726593,2017-10-24 20:57:17 UTC,FTR we need to patch puppet-cinder as well:
1726593,2019-03-05 13:23:11 UTC,Is this still an issue?
1726595,2017-10-25 12:30:00 UTC,"Most curious. It would be of tremendous help if you could find another application that behaves like that, one that is opensource and part of the ubuntu archive preferably."
1726595,2019-08-16 07:26:07 UTC,this was fixed in libjogl2-java 2.3.2+dfsg-6
1726595,2019-08-15 14:48:28 UTC,"I have similar problem explained through attachment video, that happens when I focus opened window by through x11 forwarding using ssh and then I cannot raise up any of already opened window from the dock."
1726595,2017-10-27 02:40:38 UTC,"""wayland"" is just the protocol library, so not the right place to file this."
1726595,2017-10-26 20:34:27 UTC,"Interesting:
Exception in thread ""AWT-EventQueue-1"" com.jogamp.opengl.GLException: Caught GLException: AWT-EventQueue-1: createImpl ARB n/a but required, profile > GL2 requested (OpenGL >= 3.1). Requested: GLProfile[GL3bc/GL3bc.sw], current: 3.0 (Compat profile, compat[ES2], FBO, software) - 3.0 Mesa 17.2.2"
1726595,2017-10-25 16:10:54 UTC,"As a matter of fact, I just checked the bug happens with scilab, available in universe. Scilab returns some interesting debug info in the standard output, which O copy in the attached text file."
1726595,2017-10-24 20:00:43 UTC,"I meant in the ssh localhost test case that you showed. But still, even in the remote case, the ""X server"" would be your local machine and the X api calls from matlab would be routed to your local X server (wayland or xorg) through the ssh connection."
1726595,2017-10-25 14:18:21 UTC,"I will try. For the moment I double boot 16.04 because I need to have it working, but I can run tests on spare time. Because I couldn't find problems when not running the java machine of Matlab  I will focus on applications relying heavily on java. If you have any suggestion it would help. Thanks again for your time."
1726595,2017-10-25 11:50:05 UTC,1- Yes Matlab works as expected without going through ssh.
1726595,2017-10-24 19:10:38 UTC,"Dear Andreas,"
1726595,2017-10-24 18:35:54 UTC,"Are you using Wayland? If yes, can you try with plain Xorg? To switch to xorg, logout, and on the login screen, after clicking on your name, you will see a small gear icon. Click that to select xorg, and then continue with the login."
1726595,2017-10-25 14:41:56 UTC,"Ah, Java, I hadn't realised that. I have a couple a
I can try too with ssh -X."
1726605,2017-10-23 21:36:02 UTC,Need to remember to announce (and maybe more than once) that this is going to be removed.
1726605,2017-10-23 21:35:13 UTC,assigned to myself so that no one takes this/removes it prematurely :)
1726608,2017-11-26 12:05:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726608,2017-11-20 20:40:20 UTC,"Oh, derp.  It's not the udev rule, it's the console-setup postinst."
1726608,2017-12-29 18:17:02 UTC,"I can confirm, too, that 16.04 is affected."
1726608,2017-11-26 12:06:52 UTC,Yes - this happened to me after running debootstrap of 16.04 in a chroot.
1726608,2017-11-20 20:33:26 UTC,"The real question here is why a rule in a chroot is being executed by a udev outside the chroot.  WTF, udev."
1726608,2017-10-23 21:38:06 UTC,"I tried using Laney's kbd.c program from the other bug and it does show K_UNICODE. Additionally, passing it FIX did fix the situation."
1726608,2017-10-24 08:46:08 UTC,I'm confused. This bug was reported against 17.10 and you're saying it's already fixed? That implies Brian hadn't updated since the fix on 19 September... ?!
1726608,2017-10-24 08:35:50 UTC,"I think those series are right, although you might not be bothered about / need to care for Trusty."
1726608,2017-10-24 08:34:52 UTC,"Thanks for the report, but it's a console-setup and not a gnome-shell bug. It's changing the keyboard mode under our feet."
1726608,2017-10-24 09:12:04 UTC,"No. In the test case given, he uses packages in a chroot from an older release which don't have the fixes that were applied in artful."
1726613,2017-10-27 23:33:36 UTC,添付のスクリーンショットのように、ウィンドウの端をドラッグすると検索結果が表示されます。
1726613,2018-08-09 09:26:49 UTC,18.04でも同様の現象が起こっていましたが、7月ぐらいに修正されたようです。
1726613,2018-08-15 15:47:20 UTC,直ってなかったみたいです。
1726617,2017-10-24 13:38:57 UTC,Adding dannf for opinion on this one.
1726617,2017-10-24 13:40:31 UTC,@dannf would this best be handled with appropriate package deps for development onwards?
1726617,2017-10-24 15:30:15 UTC,"OVMF typically refers to the build of edk2 for x86 virtual machines - we ship that in the ovmf package. For aarch64, efi firmware (AAVMF, qemu-efi-aarch64) is *required* to boot a cloud image directly. The charm knows this, and makes sure the firmware is installed on arm64 compute nodes."
1726620,2017-11-30 22:58:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726620,2020-08-09 23:43:52 UTC,pdfsam-basic (3.3.4-1)
1726620,2017-10-23 22:29:49 UTC,"Should I uninstall the 3.3.2-2 version to get the update, or wait for the repository to catch up?"
1726621,2017-10-24 02:25:25 UTC,Wouldn't closing be the job of gnome-shell itself?
1726625,2018-03-26 15:13:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726625,2018-05-13 02:55:08 UTC,Filed: https://gitlab.gnome.org/GNOME/nautilus/issues/427
1726625,2018-05-13 02:55:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726625,2018-05-13 11:30:55 UTC,The bug is now at https://gitlab.gnome.org/GNOME/gtk/issues/1072
1726626,2017-11-22 07:57:33 UTC,"Do you use Broadcom's proprietary driver ""wl"" under both v4.10 and v4.13?"
1726626,2018-02-21 11:57:26 UTC,"Unfortunately I am not an advanced user to provide information like the above (I don't even understand these), but I do know that I want to help and I do know that Ubuntu 17.10 is the first (I am using ubuntu since 11.04) that I cannot afford (it is worse than windows!)."
1726626,2018-01-27 04:17:18 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1726626,2017-11-27 05:01:43 UTC,"JockeTF, please file a separate bug, thanks!"
1726626,2017-11-23 14:04:32 UTC,Just had another freeze.
1726626,2017-11-23 09:54:01 UTC,Nope.
1726626,2017-11-16 14:49:57 UTC,I'm seeing frequent freezes on kernel 4.13.0-16-generic. No issues when using 4.10.0-38-generic.
1726626,2017-10-24 18:50:08 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1726626,2017-11-09 19:44:34 UTC,This is still occurring in Artful Aardvark (Ubuntu 17.10)
1726626,2017-10-24 22:45:06 UTC,"Though I did not install until it was officially released. I dislike alphas, and betas. However I see the appeal. I just always been the type to install an official release only so I don't have to deal with these types of issues on a clearly unstable OS revision."
1726626,2017-10-24 22:39:53 UTC,"As I have said multiple people have had these freezing issues. However a lot of them have found solutions. Their solutions have not worked for me, and it appears multiple people have had this has been going on since the alpha & beta of 17.10"
1726626,2017-10-24 22:21:46 UTC," Sorry I can not test/ install the latest upstream kernel because of my wifi drivers. As you can see in order to test/ install the kernel version I have to disable, and uninstall proprietary drivers. My broadcom wireless drivers fall into that category."
1726626,2017-10-24 22:12:55 UTC," Yes it started after the upgrade to 17.10, and the prior kernel where I was not having this issue was 17.04"
1726626,2017-10-23 23:00:05 UTC,This change was made by a bot.
1726626,2017-11-10 14:47:50 UTC,Can you enable persistent systemd-journald log?
1726643,2017-10-25 00:20:40 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x55f3cda3df20 ""../src/nautilus-directory-async.c"", line=line@entry=4340, func=func@entry=0x55f3cda3e6a0 <__func__.62543> ""filesystem_info_stop"", message=message@entry=0x55f3cf86daf0 ""assertion failed: (file->details->directory == directory)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x55f3cda3df20 ""../src/nautilus-directory-async.c"", line=line@entry=4340, func=func@entry=0x55f3cda3e6a0 <__func__.62543> ""filesystem_info_stop"", expr=expr@entry=0x55f3cda3e050 ""file->details->directory == directory"") at ../../../../glib/gtestutils.c:2459
 filesystem_info_stop (directory=0x55f3cf4a5d70) at ../src/nautilus-directory-async.c:4340
 start_or_stop_io (directory=0x55f3cf4a5d70) at ../src/nautilus-directory-async.c:4670
 nautilus_directory_async_state_changed (directory=directory@entry=0x55f3cf4a5d70) at ../src/nautilus-directory-async.c:4751"
1726643,2018-03-26 15:15:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726643,2018-03-26 16:27:26 UTC,Upstream bug link:-
1726643,2018-03-26 20:16:29 UTC,thanks!
1726656,2018-08-21 09:03:37 UTC,"Hi,
I'm checking old bugs every now and then, and this one had no activity since 6 months.
Reading the comments so far it reads like a valid bug, but with too few leads to actually take action fixing or further debugging it :-/"
1726656,2020-02-06 12:08:48 UTC,@Hugh
1726656,2017-12-05 10:31:46 UTC,"I meant ""flush privileges;"""
1726656,2020-01-24 01:07:27 UTC,I can currently reproduce this - I have tried various troubleshooting steps but can't fix the issue. I'm going to just migrate to MySQL 8.
1726656,2017-10-24 10:59:05 UTC,i am having the same problem does anyone have any temporary fix?
1726656,2017-10-24 06:59:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726656,2017-10-24 06:57:56 UTC,I had the same problem. It turns out it was mysql_upgrade exiting with an 'Error occurred: The mysql.session exists but is not correctly configured. The mysql.session needs SELECT privileges in the performance_schema database and the mysql.db table and also SUPER privileges.'
1726656,2017-12-05 10:29:29 UTC,"The query Kees mentioned returned ""0"" for me as well. Did not have a duplicate user however."
1726676,2017-10-25 08:09:40 UTC,"Yes I think so, though not so urgent, and need to make sure it match Kubernetes network model."
1726679,2017-10-24 05:01:24 UTC,The error in your log is:
1726679,2017-11-11 15:50:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726683,2020-05-20 06:50:40 UTC,Oops. Just noticed it is an option in the cloud-init config docs. So you can set it using the user-data.
1726683,2020-04-27 23:56:09 UTC,"For a server installer, yes. Every question / screen that gets added is more complexity, and there's a pretty good argument for keeping servers in UTC. It's not like it's hard to change after install either."
1726683,2020-05-20 06:33:23 UTC,"Please add it as an option in the automated install at the very least.
It is an option in the debian automated installer as well as the clock set in UTC-option."
1726683,2019-02-21 14:08:46 UTC,It's not especially clear that we want to add this but leaving open for now.
1726683,2020-04-24 16:13:04 UTC,Really? You are actually in doubt about adding user configurable time zone in installer?
1726684,2017-10-25 04:54:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726684,2017-10-25 04:47:54 UTC,I have test tha mainline kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6.
1726684,2017-10-25 04:20:34 UTC,I will try to test: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6.
1726684,2017-10-25 04:05:52 UTC,apport information
1726684,2017-10-25 04:05:49 UTC,apport information
1726684,2017-10-25 04:05:47 UTC,apport information
1726684,2017-10-25 04:05:46 UTC,apport information
1726684,2017-10-25 04:05:44 UTC,apport information
1726684,2017-10-25 04:05:41 UTC,apport information
1726684,2017-10-25 04:05:42 UTC,apport information
1726684,2017-10-25 04:05:38 UTC,apport information
1726684,2017-10-25 04:05:37 UTC,apport information
1726684,2017-10-25 04:05:35 UTC,apport information
1726684,2017-10-25 04:05:33 UTC,apport information
1726684,2017-10-25 04:05:31 UTC,apport information
1726684,2017-10-25 04:05:29 UTC,apport information
1726684,2017-10-25 04:05:27 UTC,apport information
1726684,2017-10-24 18:49:22 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1726684,2017-10-24 04:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1726684,2017-10-25 04:05:40 UTC,apport information
1726686,2019-02-21 14:10:08 UTC,"We decided that we should not allow configuration of unattended-upgrades, but the other parts still remain. Marking High so we do actually do the thinking about this, even though I think it's fairly likely that the bug will be closed without further action."
1726687,2017-10-24 04:28:19 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x562ee398776e ""caja-window-manage-views.c"", line=line@entry=1519, func=func@entry=0x562ee39880e0 <__func__.59608> ""caja_window_report_load_underway"", message=message@entry=0x562ee5d31930 ""assertion failed: (slot != NULL)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x562ee398776e ""caja-window-manage-views.c"", line=line@entry=1519, func=func@entry=0x562ee39880e0 <__func__.59608> ""caja_window_report_load_underway"", expr=expr@entry=0x562ee398df42 ""slot != NULL"") at ../../../../glib/gtestutils.c:2459
 caja_window_report_load_underway (window=0x562ee4fd63b0, view=0x562ee56e09d0) at caja-window-manage-views.c:1519
 finish_loading (view=0x562ee56e09d0) at fm-directory-view.c:9540
 ready_callback_call (directory=0x562ee5baf4f0, callback=<optimized out>) at caja-directory-async.c:1414"
1726702,2017-10-24 06:01:13 UTC,"StacktraceTop:
 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:374
 memmove (__len=18446744073137404992, __src=<optimized out>, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:40
 drisw_update_tex_buffer (drawable=<optimized out>, ctx=<optimized out>, res=<optimized out>) at ../../../../../src/gallium/state_trackers/dri/drisw.c:357
 dri_set_tex_buffer2 (pDRICtx=<optimized out>, target=3553, format=8409, dPriv=<optimized out>) at ../../../../../src/gallium/state_trackers/dri/dri_drawable.c:258
 boost::function1<void, unsigned long>::operator() (a0=16777684, this=0x7f2ac0eea640 <(anonymous namespace)::bindTexImageEXT()::f>) at /usr/include/boost/function/function_template.hpp:770"
1726706,2017-10-25 09:32:25 UTC,"Speaking as the golang maintainer, this is definitely a change we want, and it's a backport from the upstream compiler that is the default in artful. Even if binaries with TEXTREL execute correctly (which they should) it is better to not have text relocations..."
1726706,2017-10-26 19:57:32 UTC,"Hello Michael, or anyone else affected,"
1726707,2017-10-26 15:54:32 UTC,apport information
1726707,2017-10-26 15:54:33 UTC,apport information
1726707,2017-10-26 15:54:28 UTC,apport information
1726707,2017-10-26 15:54:27 UTC,apport information
1726707,2017-10-26 15:54:26 UTC,apport information
1726707,2017-10-26 15:54:24 UTC,apport information
1726707,2017-10-26 15:54:23 UTC,apport information
1726707,2017-10-26 15:54:21 UTC,apport information
1726707,2017-10-26 15:54:20 UTC,apport information
1726707,2017-10-26 15:54:19 UTC,apport information
1726707,2017-10-26 15:54:29 UTC,apport information
1726707,2017-10-26 15:54:16 UTC,apport information
1726707,2017-10-24 07:03:34 UTC,"tried to get additional information via recipes in https://help.ubuntu.com/community/DebuggingSystemCrash but no luck.
- Alt-SysRq does nothing at all
- linux-crashdump was successfully installed (checked via /proc/cmdline) but there is nothing in /var/crash after powercycle
- tracing the system logfiles via ssh revealed no further information"
1726707,2017-10-24 13:18:22 UTC,Could you add your syslog after getting the issue? Is your ssh session still active after getting the bug? Could be a kernel issue...
1726707,2017-10-24 13:19:14 UTC,Does moving /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_fwupd.so away workaround the locking?
1726707,2017-10-25 08:20:12 UTC,hi sebastien.
1726707,2017-10-26 15:54:17 UTC,apport information
1726707,2017-10-26 15:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1726707,2017-10-26 15:54:12 UTC,apport information
1726707,2017-10-26 15:54:13 UTC,apport information
1726707,2017-10-26 15:54:14 UTC,apport information
1726707,2017-10-26 14:43:58 UTC,"thanks, reassigning to the kernel thenb"
1726713,2017-10-24 07:49:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514552"
1726713,2018-01-10 21:54:05 UTC,"I'm personally for this idea, however the proposed patch appears to need some work. I posted to it to raise visibility."
1726718,2017-11-06 20:53:13 UTC,"This behaviour is created by the rev 15490, fixing the bug https://bugs.launchpad.net/inkscape/+bug/1662285."
1726721,2018-06-21 23:05:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726721,2018-06-21 23:11:33 UTC,"XEmacs happens to be one of my favorite text editors and I really want to install it.  The problem is that I usually install all the bells and whistles without a problem.  In this case I'd be willing to leave something out but I don't know which item or items is causing the problem.  I'm not used to tracking down install bugs because most things I install just work, so I need some help here."
1726725,2019-06-13 06:44:06 UTC,This is very likely due to user configuration and setup. If the suggestions of Jose are attempted and this problem persists then we need to look further.
1726725,2019-05-08 07:21:17 UTC,I think with the change abandoned and this likely being caused by a configuration issue this should be closed.
1726725,2019-02-07 12:42:10 UTC,"I think this bug is related to the specific configuration you are running in haproxy
You can change the method to check by specifying
option httpchk GET / HTTP/1.0\r\nUser-Agent:\ HAProxy"
1726725,2018-11-07 08:05:15 UTC,"Change abandoned by suzhengwei (sugar-2008@163.com) on branch: master
Review: https://review.openstack.org/616054"
1726725,2018-11-07 03:30:49 UTC,"Haproxy check health with Watcher-api by acess Root.
/etc/haproxy/haproxy.cfg
listen watcher_api
  bind 10.21.1.69:10322
  balance roundrobin
  option tcpka
  #option httpchk
  option tcplog
  server host_69 10.21.1.69:9322 check inter 2000 rise 2 fall 5"
1726725,2018-11-07 03:22:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616054"
1726725,2018-02-28 10:11:53 UTC,I will setup haproxy on my own env and will report whether it is bug of watcher-api or invalid haproxy setup
1726725,2017-11-23 01:55:05 UTC,"Hi suzhengwei,
did you check ""timeout connect"" in /etc/haproxy/haproxy.cfg ?? Is it too short to wait for watcher-api to react?"
1726730,2017-11-30 12:07:29 UTC,"I'll try to update it for Bionic to closer match the upcoming kernel number.
That would at least make the upcoming LTS somewhat in sync with iproute."
1726730,2017-12-11 17:46:18 UTC,This bug was fixed in the package iproute2 - 4.14.1-0ubuntu2
1726735,2017-11-13 12:35:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726743,2017-10-24 08:00:07 UTC,This change was made by a bot.
1726743,2017-10-24 18:48:37 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1726743,2017-10-24 19:50:32 UTC,I had this on the kernels from Ubuntu 17.10 Beta onward. After a fresh install the issue still persisted.
1726743,2017-12-24 04:17:46 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1726743,2017-12-24 13:36:53 UTC,The issue is still pending for several kernel updates.
1726743,2017-12-24 14:00:06 UTC,This change was made by a bot.
1726743,2018-01-23 17:56:44 UTC,Kernel 4.13.0.31.33 still has this issue.
1726759,2020-01-18 11:52:04 UTC,It’s fixed in at least 18.04 and forward. Last tested version is 19.10.
1726760,2020-11-16 08:19:12 UTC,Zero crashes after 18.10 so consider it fixed.
1726760,2018-08-08 08:08:56 UTC,"Tracking in:
https://errors.ubuntu.com/problem/f0d0e396195066f53a0b4f65435e3c0bdc7b9294"
1726760,2018-08-08 08:08:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726760,2017-10-24 09:08:30 UTC,"StacktraceTop:
 gtk_action_observer_action_removed (observer=0x14d, observable=0x55c3437fcf80, action_name=0x55c34380df30 ""win.show-help-overlay"") at ../src/gtkactionobserver.c:155
 gtk_action_muxer_action_removed (muxer=0x55c3437fcf80, action_name=action_name@entry=0x55c34380df30 ""win.show-help-overlay"") at ../src/gtkactionmuxer.c:313
 gtk_action_muxer_action_removed_from_group (action_group=<optimized out>, action_name=<optimized out>, user_data=user_data@entry=0x55c3439144c0) at ../src/gtkactionmuxer.c:326
 gtk_action_muxer_remove (muxer=<optimized out>, prefix=<optimized out>) at ../src/gtkactionmuxer.c:763
 gtk_action_muxer_insert (muxer=0x55c3437fcf80, prefix=prefix@entry=0x7f0c27a1036b ""win"", action_group=action_group@entry=0x55c343688e30) at ../src/gtkactionmuxer.c:712"
1726762,2020-01-30 14:09:03 UTC,This has been fixed meanwhile. Codeblocks look good: https://jaas.ai/nrpe
1726770,2017-10-24 14:19:42 UTC,https://review.openstack.org/#/c/134133/ is arguably implementing the wrong default behavior.
1726770,2017-10-24 18:06:33 UTC,It seems kind of odd to me if the user asks for an unfiltered list that we would not return all the items.
1726770,2017-10-24 18:48:07 UTC,"Yeah, I strongly disagree with the idea that we should limit the list shown in the client just because other openstack projects behave that way.  That sounds like a bug, which we addressed."
1726770,2017-10-25 03:02:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514896"
1726770,2017-10-30 16:18:08 UTC,"-> Incomplete, pending more info on perf issues"
1726770,2018-05-10 20:58:59 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/514896
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns."
1726772,2017-11-29 06:35:26 UTC,"Hi Andy,"
1726772,2017-11-20 11:45:37 UTC,"I was using 17.04 at the time, but have since moved to 17.10 - I'm sure
you already know that there are issues, so I'm really looking forward to
the HPLIP release."
1726772,2017-11-29 08:57:05 UTC,"Awesome work guys, and thank you so much!"
1726772,2017-10-25 19:25:27 UTC,"installing the library by hand is a workaround, for now."
1726772,2017-11-20 11:16:07 UTC,"Hi Andy,"
1726775,2020-07-23 15:31:35 UTC,looks like you tweaked /usr/bin/python symlink point to python
1726788,2017-10-24 10:17:51 UTC,"StacktraceTop:
 adler32_z (adler=130353, buf=0x7f5168d22ff8 <error: Cannot access memory at address 0x7f5168d22ff8>, len=140728579677536) at adler32.c:107
 adler32 (adler=<optimized out>, buf=<optimized out>, len=<optimized out>) at adler32.c:139
 pkgCache::CacheHash (this=this@entry=0x2c18310) at ./apt-pkg/pkgcache.cc:252
 pkgCache::ReMap (this=this@entry=0x2c18310, Errorchecks=@0x7ffded007720: true) at ./apt-pkg/pkgcache.cc:198
 pkgCache::pkgCache (this=0x2c18310, Map=<optimized out>, DoMap=<optimized out>) at ./apt-pkg/pkgcache.cc:137"
1726790,2018-01-09 09:20:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726791,2017-10-24 10:19:54 UTC,"StacktraceTop:
 __libc_message (action=(do_abort | do_backtrace), fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=<optimized out>, str=0xb74993af ""free(): invalid pointer"", ptr=<optimized out>, ar_ptr=0xb74f17a0 <main_arena>) at malloc.c:5425
 _int_free (av=0xb74f17a0 <main_arena>, p=<optimized out>, have_lock=have_lock@entry=0) at malloc.c:4174
 __GI___libc_free (mem=0xaf63c80) at malloc.c:3144
 operator delete (ptr=0xaf63c80) at ../../../../src/libstdc++-v3/libsupc++/del_op.cc:49"
1726803,2018-10-29 21:38:54 UTC,"Hello Patrick, or anyone else affected,"
1726803,2018-11-13 16:40:10 UTC,This bug was fixed in the package shim-signed - 1.37~18.04.3
1726803,2018-11-13 16:30:10 UTC,"The verification of the Stable Release Update for shim-signed has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1726803,2018-11-13 16:11:41 UTC,"For the record the shim-signed fix alone is enough to fix the reported issue, i.e. installation failing when the nvidia module changes dirs."
1726803,2018-11-06 16:51:32 UTC,"Verified with shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1:
...
ubuntu@autopkgtest:/var/cache/apt/archives$ sudo  rm /var/lib/shim-signed/mok/MOK.der
ubuntu@autopkgtest:/var/cache/apt/archives$ sudo   update-secureboot-policy --new-key
Generating a new Secure Boot signing key:
Generating a 2048 bit RSA private key
...........................................................................................................+++
...................+++
writing new private key to '/var/lib/shim-signed/mok/MOK.priv'
-----
root@autopkgtest:/var/cache/apt/archives# echo /var/lib/dkms/zzz >> /var/lib/shim-signed/dkms-list
root@autopkgtest:/var/cache/apt/archives# env DEBIAN_FRONTEND=noninteractive update-secureboot-policy --enroll-key; echo $?
Running in non-interactive mode, doing nothing.
0
root@autopkgtest:/var/cache/apt/archives# cat > /var/lib/shim-signed/dkms-list <<EOF

> /var/lib/dkms
> /var/lib/dkms/nvidia-1
> /var/lib/dkms/r8168
> EOF


root@autopkgtest:/var/cache/apt/archives#  mkdir /var/lib/dkms/nvidia
root@autopkgtest:/var/cache/apt/archives# env DEBIAN_FRONTEND=noninteractive update-secureboot-policy --enroll-key; echo $?
Running in non-interactive mode, doing nothing.
0
root@autopkgtest:/var/cache/apt/archives#  cat > /var/lib/shim-signed/dkms-list <<EOF

> /var/lib/dkms
> /var/lib/dkms/r8168
> EOF


root@autopkgtest:/var/cache/apt/archives# env DEBIAN_FRONTEND=noninteractive update-secureboot-policy --enroll-key; echo $?
Running in non-interactive mode, doing nothing.
--- /var/lib/shim-signed/dkms-list	2018-11-06 17:47:43.490071095 +0100
+++ /var/lib/shim-signed/dkms-list.new	2018-11-06 17:47:43.490071095 +0100
@@ -1,2 +1,3 @@
 /var/lib/dkms
+/var/lib/dkms/nvidia
 /var/lib/dkms/r8168
1"
1726803,2018-10-12 18:08:17 UTC,This bug was fixed in the package shim-signed - 1.38
1726803,2018-10-09 18:05:15 UTC,"Balint, I wrote in comment #4 that changing the nvidia stack is expected on upgrades, and that we should special-case this in shim-signed to suppress the error.  Why are you proposing to change unattended-upgrades instead?"
1726803,2017-10-24 22:16:40 UTC,It appears this is normal that the nvidia packages will upgrade to pull in a newer version as a dependency.  This means we need to special-case nvidia in /var/lib/dkms/nvidia-* to avoid triggering errors in unattended upgrades.
1726803,2017-10-24 21:43:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726803,2017-10-24 19:05:16 UTC,I'm surprised to see that your nvidia stack is being switched as part of an unattended upgrade.  Reassigning to the unattended-upgrades package for further investigation.
1726803,2018-10-10 12:47:13 UTC,"@vorlon My bad, thought that a generic solution would be useful in u-u, but now I'm implementing now the special case."
1726821,2017-10-25 07:01:39 UTC,apport information
1726821,2017-10-24 13:30:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726821,2017-10-24 20:44:53 UTC,Reported upstream [1].
1726821,2017-10-25 01:46:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1726821"
1726821,2017-10-25 07:01:34 UTC,apport information
1726821,2017-10-25 07:01:36 UTC,apport information
1726821,2017-10-25 07:01:38 UTC,apport information
1726821,2017-10-25 07:02:29 UTC,"> When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected
"
1726821,2018-08-08 08:09:17 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1726826,2017-10-27 14:50:47 UTC,"Hi Paul,"
1726826,2017-10-27 12:40:32 UTC,"So, something that used to work and now does not -- the boilerplate definition of a regression, I'd think -- and the ""solution"" is to update a distro specific README file, that nobody will read?  It is your call in the end, but I have to say that doesn't improve the end-user experience any...."
1726826,2017-10-26 00:58:12 UTC,"I do not want to add any further patches to Debian's screen package which makes it differ from upstream behaviour more than it already does. (Of course, it's a different thing if issues are caused by existing patches.)"
1726826,2017-11-04 23:01:40 UTC,This bug was fixed in the package screen - 4.6.2-1
1726826,2017-10-25 06:03:19 UTC,"Please see this new section in README.Debian, which will be published with the next upload of Debian's screen package to Debian Unstable: https://anonscm.debian.org/cgit/collab-maint/screen.git/tree/debian/README.Debian#n142"
1726826,2017-10-24 13:25:44 UTC,"I'm not sure why newer versions of screen (or Ubuntu's configuration) tend to set this weird value of ""screen.xterm-256color"". The more readable value ""screen-256color"" is supported at least since Trusty 14.04 (see https://packages.ubuntu.com/trusty/all/ncurses-base/filelist), probably much earlier than that (I'm seeing forum posts about ""screen-256color"" dated 2011-ish)."
1726826,2017-10-25 20:30:42 UTC,"I _guess_ it shouldn't be that hard to patch screen to make an exception to the ""prepend 'screen.'"" rule, and convert an implicitly created ""screen.xterm-256color"" into ""screen-256color"". (I haven't checked screen's source to see how easy it would be.)"
1726842,2017-10-24 12:28:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1726842,2018-01-22 06:18:07 UTC,"Well,
How should we do this?
We cannot pinpoint this to a single package, the screen stays black, as soon as the graphics is switched.
When you upgrade from 17.04 to 17.10 on an Acer R11 you will not be able to access the device locally."
1726842,2018-01-23 04:51:15 UTC,booting Ubuntu-17.10.1 or Ubuntu-18.04 Aspire R3-131T results in a black screen right from the beginning.
1726852,2017-10-24 16:24:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1726853,2018-01-09 15:51:52 UTC,Any progress with this? I can't print anything at all.
1726853,2017-10-26 10:22:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726853,2018-01-15 12:31:59 UTC,I can't print too...
1726855,2017-10-24 16:24:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1726859,2017-10-24 13:20:41 UTC,Setting up deluged (1.3.15-2) ...
1726866,2017-10-24 13:28:22 UTC,"After recreating links in ""/"" to images in /boot (which I had removed earlier) lilo ran without complaint."
1726866,2018-01-13 16:23:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726869,2017-10-24 18:28:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726869,2017-10-24 13:42:07 UTC,"StacktraceTop:
 dbus_watch_handle (watch=0x5626036fde20, flags=1) at ../../../dbus/dbus-watch.c:758
 dispatch_func (source=source@entry=0x562603675d30, callback=<optimized out>, userdata=<optimized out>) at glib-watch.c:339
 g_main_dispatch (context=0x56260366f9b0) at ../../../../glib/gmain.c:3148
 g_main_context_dispatch (context=context@entry=0x56260366f9b0) at ../../../../glib/gmain.c:3813
 g_main_context_iterate (context=0x56260366f9b0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3886"
1726871,2017-10-26 16:41:10 UTC,"Reviewed:  https://review.openstack.org/515404
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4e93523fbce953228be276aca0f70a53fcaaad14
Submitter: Zuul
Branch:    stable/pike"
1726871,2017-12-07 23:56:46 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1726871,2017-10-26 13:14:10 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515404"
1726871,2017-11-15 01:10:35 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1726871,2017-10-24 20:48:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514825"
1726871,2017-10-24 20:13:04 UTC,"Yup the problem is right here, and it's been around since 2014:"
1726871,2017-10-26 02:41:43 UTC,"Reviewed:  https://review.openstack.org/514825
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1ca191fcc4d809c991c23dedc951bbe7206edf1d
Submitter: Zuul
Branch:    master"
1726872,2017-10-24 13:40:59 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x55848bf3b2b0, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x55848bf3b2b0) at ../../../../gobject/gobject.c:3196
 g_weak_ref_get (weak_ref=<optimized out>) at ../../../../gobject/gobject.c:4369
 g_settings_backend_invoke_closure (user_data=0x55848b86b100) at ../../../../gio/gsettingsbackend.c:263
 g_main_dispatch (context=0x55848b76fa40) at ../../../../glib/gmain.c:3148"
1726872,2018-04-02 21:42:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726888,2017-10-25 12:39:46 UTC,">Did you know Alt+` (the key above Tab) does roughly the same thing? (switches between windows of the same app)
"
1726888,2017-10-25 02:37:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726888,2017-10-25 02:39:19 UTC,Did you know Alt+` (the key above Tab) does roughly the same thing? (switches between windows of the same app)
1726889,2018-03-06 17:14:11 UTC,Any update on this ? I still get the blurry icon when I use terminator on ubuntu (16.04 currently)
1726889,2018-02-15 13:26:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726889,2017-10-24 17:09:00 UTC,"This patch seems responsible
https://anonscm.debian.org/viewvc/python-apps/packages/terminator/trunk/debian/patches/not-install-terminator-wrapper.diff?view=log"
1726889,2017-10-24 18:07:56 UTC,"Yeah, and then that gets pulled into Ubuntu, because they mostly use Debian packages. So it probably needs to be raised with Debian. Not sure that when this patch was applied they actually understood the reason for adding the wrapper."
1726895,2017-10-24 15:08:36 UTC,"StacktraceTop:
 set_para_values (layout=layout@entry=0x7fb4b8943270, base_dir=base_dir@entry=PANGO_DIRECTION_LTR, style=style@entry=0x0, display=display@entry=0x7fb4b8add6b0) at ./gtk/gtktextlayout.c:1345
 IA__gtk_text_layout_get_line_display (layout=layout@entry=0x7fb4b8943270, line=line@entry=0x7fb4b8978cf0, size_only=size_only@entry=1) at ./gtk/gtktextlayout.c:2249
 gtk_text_layout_real_wrap (layout=0x7fb4b8943270, line=0x7fb4b8978cf0, line_data=0x7fb45800a270) at ./gtk/gtktextlayout.c:1167
 gtk_text_btree_node_validate (view=view@entry=0x7fb4b8ac5000, node=<optimized out>, view_id=view_id@entry=0x7fb4b8943270, state=state@entry=0x7fb4c05a78a0) at ./gtk/gtktextbtree.c:5103
 _gtk_text_btree_validate (tree=0x7fb4b8978d50, view_id=view_id@entry=0x7fb4b8943270, max_pixels=max_pixels@entry=2000, y=y@entry=0x7fb4c05a790c, old_height=old_height@entry=0x7fb4c05a7910, new_height=new_height@entry=0x7fb4c05a7914) at ./gtk/gtktextbtree.c:5255"
1726900,2017-10-25 00:45:32 UTC,"Not reproduced here with Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1 64 bit."
1726900,2017-10-25 12:41:53 UTC,"@Tyler it seems to be a particular file that is having this problem. Can delete connectors in new files without a problem. For reference, I'm on Ubuntu 16.04, Inksacpe 0.92.2."
1726900,2020-11-21 00:28:08 UTC,Could you share that file? Do you still replicate in the latest versions of Inkscape? (0.92.5 or 1.0 or later.
1726904,2017-10-24 15:39:00 UTC,"StacktraceTop:
 _g_log_abort (breakpoint=breakpoint@entry=1) at ../../../../glib/gmessages.c:554
 g_log_writer_default (log_level=6, log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7ffea8ec4ff0, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../../glib/gmessages.c:2628
 g_log_structured_array (log_level=G_LOG_LEVEL_ERROR, fields=0x7ffea8ec4ff0, n_fields=6) at ../../../../glib/gmessages.c:1941
 g_log_structured (log_domain=0x7f8796765b2e <error: Cannot access memory at address 0x7f8796765b2e>, log_level=G_LOG_LEVEL_ERROR) at ../../../../glib/gmessages.c:1768
 ?? ()"
1726908,2017-10-24 19:22:57 UTC,Reported upstream as well on https://bugzilla.gnome.org/show_bug.cgi?id=789433
1726912,2018-04-17 19:58:46 UTC,"This would be a systemd-networkd bug, which I suspect might have already been fixed too. Reassigning to systemd."
1726912,2017-10-24 18:47:00 UTC,"this is happening on a system using 10G Intel NIC:
05:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)"
1726912,2017-10-24 21:09:38 UTC,I have verified this is reproducible on other systems with ixgbe based add in cards.
1726912,2017-11-17 22:01:04 UTC,this is actually upstream bug https://github.com/systemd/systemd/issues/6593 related to setting MTU.
1726912,2018-04-19 16:29:49 UTC,I can confirm this works in Bionic so close away
1726917,2017-10-24 20:26:57 UTC,"solved, i just discover that my /tmp was 755 instead of 1777. I don't know how it happend but once corrected it just works:"
1726917,2017-11-25 23:00:23 UTC,facing similar problem (https://drive.google.com/file/d/1vhLchDq5FCInZqqnCqSRdscedWz11XeR/view?usp=sharing) . Please help!!
1726918,2019-05-20 20:52:08 UTC,"I'm unable to replicate this on current master, but I'm not seeing any commits in the history for the two obvious files to check(staff/circ/patron/app.js and staff/services/patron_search.js) that would have resolved it. Is it possible that hatch session storage key eg.circ.last_alerted_patron was set to the specific test patron when encountering the issue?"
1726918,2019-10-21 15:33:29 UTC,I can confirm Kathy's original bug. I was not able to get this to work either in current master or in 3.2.8.
1726918,2019-10-21 17:59:34 UTC,I did a local fix for this a few years ago. I'll work it up into a proposed patch today.
1726918,2019-10-21 19:18:43 UTC,We've been using this modification for the last year or two and it works for us:
1726918,2019-10-22 14:16:16 UTC,"Thanks Terran.  When I was testing your patch, I realized that I had the library setting set incorrectly.  I had it set for 30 days, instead of 30.  If the setting is set correctly the functionality works.  Sorry about that.  Your patch may have already made it into master."
1726918,2019-10-22 17:17:25 UTC,"Heh, well, it helps if I read the actual bug report properly. The patch I submitted actually adds an alert to the patron summary bar as well onto the alert screen! I'll create a separate launchpad for this and submit my fix in case it would be helpful for people."
1726918,2019-10-22 17:19:04 UTC,Marking as invalid since the function is already working.
1726922,2020-04-25 23:23:04 UTC,"Deleting files in ~/.config is suboptimail in my case;
I have very few applications installed and already have 122 objects in .config.
It would be nice if someone [who knows] told us what variable we are to look for.
that Google seems to be the culprit in virtually all cases here, and that the applicationdoes not report itself whrn invoking this obscurity measure, fails to amaze me."
1726922,2019-02-09 17:48:49 UTC,"Thank you Mat, deleting the config files seems to have worked for me too."
1726922,2018-02-21 17:11:33 UTC,"I solved it by deleting the calendar. It's on my mobile phone, enough."
1726922,2017-11-02 09:36:18 UTC,"Well, the workaround that works for me is to toggle off the Calendar in the Search section of the system settings."
1726922,2017-11-01 14:00:44 UTC,"I'm affected by this issue and do have 2FA enabled, but using an app specific password did not fix the issue. I still get frequent popups."
1726922,2017-10-29 14:20:30 UTC,"Here is the workaround for people coming into this bug with Two Factor Auth set.  You need to generate an application specific password for the Google acct in ""Online Accounts"" from this page:  https://security.google.com/settings/security/apppasswords"
1726922,2017-10-27 10:35:37 UTC,"There is no account conversion on upgrades or anything like that, and yes it's an upstream issue if the code doesn't work as it should"
1726922,2018-01-07 08:44:20 UTC,On this page
1726922,2017-10-27 05:13:13 UTC,"Could it be that I had previously allowed me in due to having performed the second auth before the upgrade?  Aside from that, it's possible I performed the auth during the initial stages of the upgrade and don't remember now."
1726922,2017-10-27 02:03:52 UTC,"doug are you sure you didn't allow it in online accounts settings?
That's the account and authorization used by calendar, I have 2 factor authentication and when I set it up in online accounts it asked me for the second face auth.
There's no way an app can access your calendar or other info if you have two factor authentication in google."
1726922,2017-10-27 00:48:21 UTC,"I just upgraded from 17.04 to 17.10 today and am experiencing the issue as described.  One thing not previously mentioned by others: I have two factor auth enabled on my account. I was never asked for the 2nd auth, yet I still see my calendar data being updated."
1726922,2017-10-26 21:06:50 UTC,"According to the Gmail email notice I received:
""Google will continue to block sign-in attempts from the app you're using because it has known security problems or is out of date. You can continue to use this app by allowing access to less secure apps, but this may leave your account vulnerable."""
1726922,2017-10-27 09:42:10 UTC,"Doug that's exactly what the bug says and why I filled it, you are not being asked for the auth code simply because there is a bug in the login. I filled the bug, the annoyance is because the application is asking for a password it doesn't need."
1726922,2017-10-24 22:37:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726922,2017-10-24 20:17:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726930,2018-02-20 13:08:31 UTC,Please attach full dmesg if possible.
1726930,2018-02-19 17:05:19 UTC,That's because what I instructed in #15 makes laptop-mode-tools ineffective to USB hotplug events. Not something that a user would want.
1726930,2018-02-19 16:29:06 UTC,(Sorry for accidentally hitting the wrong button earlier.)
1726930,2018-02-16 04:55:49 UTC,"Not really.
The BX100 has broken LPM, it's not working under min/med power."
1726930,2018-02-07 09:28:09 UTC,"ryan,
So looks like we can only use max_power for your disk."
1726930,2018-02-15 19:00:56 UTC,https://lkml.org/lkml/2018/2/15/1184
1726930,2018-02-26 09:14:11 UTC,"As requested, booted using battery power with setting ""auto"" in /lib/udev/rules.d/99-laptop-mode.rules. Then changed setting back to ""force"" and plugged in an external USB HDD (Transcend StoreJet)."
1726930,2018-02-06 15:47:15 UTC,"I don't know how i missed this yesterday.  I installed the kernel, then change the auto to force and reboot.  I was assuming that reboot was the test.  It appears that i have the same issue after another reboot, or shut down when AC is not attached"
1726930,2018-02-06 15:18:35 UTC,"/sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/scsi_host/host0/link_power_management_policy:med_power_with_dipm
/sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/scsi_host/host1/link_power_management_policy:min_power
/sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/scsi_host/host2/link_power_management_policy:min_power"
1726930,2018-02-16 01:59:41 UTC,"It sounds like a workaround might be needed for all Crucial SSDs. More models that are problematic in low power mode are mentioned here:
  https://askubuntu.com/questions/844459/ubuntu-ssd-was-fast-is-now-extremely-slow"
1726930,2018-03-05 08:27:51 UTC,"The ""auto"" fix works for me too. Having just upgraded an old Dell Vostro v131 to 17.10, it no longer booted from battery but required the mains adaptor to be used. The change noted in #15 worked at it now boots correctly."
1726930,2018-04-24 16:00:42 UTC,The kernel fix for this arrived in Xenial/16.04 via upstream stable v4.4.125.
1726930,2018-04-13 23:43:34 UTC,This bug was fixed in the package linux - 4.15.0-15.16
1726930,2018-04-26 07:01:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726930,2018-04-27 19:12:00 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1726930,2018-05-18 19:02:36 UTC,"Removing systemd, as I believe there is nothing to be changed in systemd for this fix to land."
1726930,2018-05-18 20:00:01 UTC,I can confirm I no longer have issues.
1726930,2018-05-18 20:28:00 UTC,"Correction, it works with the force argument.
ACTION==""add"", SUBSYSTEM==""usb"", RUN+=""lmt-udev force"""
1726930,2018-05-21 07:15:51 UTC,"Ryan, thanks for the testing."
1726930,2018-05-21 07:16:24 UTC,The same patch should work for all kernel versions.
1726930,2018-02-06 05:25:14 UTC,"ryan,"
1726930,2018-05-22 00:00:38 UTC,This bug was fixed in the package linux - 4.4.0-127.153
1726930,2018-04-04 16:05:38 UTC,"@rrs

> BTW, does Ubuntu have the systemd/udevd mount propagation fix included ?
"
1726930,2018-02-05 22:57:12 UTC,I can confirm this fix worked for me.
1726930,2018-01-11 10:01:23 UTC,Works for me too with Ubuntu 17.10 on an Acer Extensa laptop (i5-6200U SkyLake). Same symptoms but changing 'force' to 'auto' as above results in successful booting from battery.
1726930,2018-02-01 01:02:54 UTC,I had the same problem since 4.9.0-4-amd64
1726930,2017-10-24 16:39:47 UTC,Possibly related: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458
1726930,2017-10-24 17:19:55 UTC,The systemd/dbus issues are possibly related to the partial fix detailed in
1726930,2017-10-24 17:24:21 UTC,systemd-resolved.service and systemd.hostnamed.service show up pretty clearly on the startup console as having problems and their logs show repeated entries of the form:
1726930,2018-02-02 06:25:57 UTC,"This kernel has workaround for CT500BX100SSD1 in #23 and Micron_M600_MTFDDAV128MBF in #24.
Use ""force"" in laptop-mode-tools to test it."
1726930,2017-10-24 19:43:35 UTC,Confirmed on a hp Spectre x360 13-4104ng.
1726930,2017-11-21 22:26:47 UTC,I can confirm bug on ASUS Zenbook UX305CA. I have laptop-mode and pm-utils installed.
1726930,2017-12-06 20:57:51 UTC,"Uninstalling laptop-mode-tools helped me, but it's useful package and it would be nice to get it back."
1726930,2017-12-07 01:15:56 UTC,"This must be an Ubuntu specific problem. I haven't encountered the problem
upstream."
1726930,2017-12-22 19:33:43 UTC,"Like timor I can confirm the bug on the same laptop (ASUS Zenbook UX305CA), too."
1726930,2018-01-03 07:27:16 UTC,This is more likely to be a kernel bug.
1726930,2017-10-24 18:19:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726930,2018-01-09 16:41:37 UTC,"This would still be a flaky device or a kernel bug. Because the mentioned laptop-mode-tools version (1.71) brought in forced execution mode, so that it could apply proper power saving values. That's pretty much it. That does not result in read only rootfs because if it logically did, it'd be seen on every machine."
1726930,2018-01-09 17:06:46 UTC,I want to confirm that changing 'force' to 'auto' for the last entry in /lib/udev/rules.d/99-laptop-mode.rules did allow me to boot successfully.
1726930,2018-01-10 06:12:08 UTC,Thanks for confirming @reckenrode. I'd appreciate if more users confirmed the same.
1726930,2018-01-11 14:14:58 UTC,"Okay. Thanks for the reports. It could very well be the flakiness in usb
devices that are causing this problem. Anyways, the best fix for this is to
contain usb execution to the runtime module only."
1726930,2018-01-11 17:51:08 UTC,"Hi, I'm using Debian Stretch on a Thinkpad X220 and had the same issue. The advice from Ritesh Raj Sarraf worked for me too and I just registered to confirm this."
1726930,2018-01-25 04:51:45 UTC,"To actually solve this, we need to disable min power LPM for faulty device in the Linux kernel. So please attach disk information if possible."
1726930,2018-01-25 14:11:38 UTC,here is my hdpram for both drives
1726930,2018-01-30 10:58:49 UTC,"I can confirm that the workaround suggested in #15 works for my Asus UX305CA, too. I attached my hdparm output..."
1726930,2018-01-31 09:21:52 UTC,"Oh cool. Reminds me of this:
https://askubuntu.com/questions/844459/ubuntu-ssd-was-fast-is-now-extremely-slow/879291#879291"
1726930,2018-01-09 16:29:06 UTC,Folks...
1726934,2018-01-01 11:46:34 UTC,apport information
1726934,2018-01-01 11:46:35 UTC,apport information
1726934,2018-01-01 11:46:36 UTC,apport information
1726934,2018-01-01 11:46:37 UTC,apport information
1726934,2018-01-01 11:46:38 UTC,apport information
1726934,2018-01-01 11:46:39 UTC,apport information
1726934,2018-01-01 13:24:06 UTC,"this is output of evtest - worked for 18 mins, but finally stopped, these are the last lines -
Event: time 1514812803.354344, -------------- SYN_REPORT ------------
Event: time 1514812803.354927, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 1868
Event: time 1514812803.354927, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 750
Event: time 1514812803.354927, -------------- SYN_REPORT ------------
Event: time 1514812803.368057, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 1872
Event: time 1514812803.368057, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 781
Event: time 1514812803.368057, -------------- SYN_REPORT ------------
Event: time 1514812803.381777, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 1883
Event: time 1514812803.381777, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 851
Event: time 1514812803.381777, -------------- SYN_REPORT ------------
Event: time 1514812803.382357, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 1888
Event: time 1514812803.382357, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 895
Event: time 1514812803.382357, -------------- SYN_REPORT ------------
Event: time 1514812803.485414, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1514812803.485414, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 1
Event: time 1514812803.485414, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1514812803.485414, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1514812803.485414, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1514812803.485414, -------------- SYN_REPORT ------------"
1726934,2018-01-01 11:46:42 UTC,apport information
1726934,2018-01-01 11:46:45 UTC,apport information
1726934,2018-01-01 11:46:47 UTC,apport information
1726934,2018-01-01 14:20:07 UTC,"currently my touchpad is detected by hid-multitouch module - and I assume I need to add ELAN1200:00 04F3:303E Touchpad to elan_i2c module instead, right?"
1726934,2018-01-01 11:46:33 UTC,apport information
1726934,2018-01-02 03:28:33 UTC,"It should be fixed by latest mainline kernel.
Currently there is a patch missing in Artful kernel."
1726934,2018-01-01 11:46:41 UTC,apport information
1726934,2018-01-01 11:46:32 UTC,apport information
1726934,2017-10-27 02:48:29 UTC,Looking at photos of the Asus Vivobook X505BA keyboard it looks like F9 (or fn+F9) is the key combo to disable/enable the touchpad.
1726934,2018-01-01 11:46:29 UTC,apport information
1726934,2018-01-01 11:46:28 UTC,apport information
1726934,2018-01-01 11:46:26 UTC,"ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  mikhail    1048 F.... pulseaudio
 /dev/snd/controlC0:  mikhail    1048 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
InstallationDate: Installed on 2017-10-22 (71 days ago)
InstallationMedia: Ubuntu 17.10 ""Artful Aardvark"" - Release amd64 (20171018)
MachineType: ASUSTeK COMPUTER INC. X505BA
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed root=UUID=346c6d11-8a1f-4d8e-bec3-523a1beb0e9b ro quiet splash
ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-22-generic N/A
 linux-backports-modules-4.13.0-22-generic  N/A
 linux-firmware                             1.169.2
Tags:  wayland-session artful
Uname: Linux 4.13.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X505BA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X505BA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.303:bd06/27/2017:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X505BA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC."
1726934,2017-12-03 04:06:12 UTC,"When this issue happens, do `apport-collect 1726934`"
1726934,2017-12-02 18:51:05 UTC,"I have the same asus x505ba, and although in latest kernel touchpad started working better, it still stops working after some time (10-15 mins)."
1726934,2017-11-03 06:57:25 UTC,"drops-r, please open a new bug for your issue."
1726934,2017-11-03 06:57:03 UTC,"drops-r,"
1726934,2017-11-03 06:37:21 UTC,"The same touchpad in Fujitsu E557 it completly not recognized. I tried with with upstream kernel 4.14.0-041400rc7-generic and after upgrade do 17.10 even 'cat /proc/bus/input/devices' doesn't show my touchpad. But after I wake up my laptop from suspend mode, magically my touchpad started works.
I: Bus=0011 Vendor=0002 Product=000e Version=0000
N: Name=""ETPS/2 Elantech Touchpad""
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input20
U: Uniq=
H: Handlers=mouse1 event17
B: PROP=1
B: EV=b
B: KEY=e420 30000 0 0 0 0
B: ABS=661800011000003"
1726934,2017-10-31 16:26:27 UTC,Testing the upstream kernel has solved my problems. My mouse is now more buttery smooth than it is on Windows. Multitouch is fully functional and no touchpad cutoffs have happened since the update.
1726934,2017-10-30 20:38:56 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1726934,2018-01-01 11:46:31 UTC,apport information
1726934,2017-10-27 02:44:57 UTC,"Please try VT switching to VT4 (Ctrl+Alt+F4), log in and retest with 'evtest'. If you continue to get no results then that's a kernel bug. Because Wayland and libinput are not part of the equation when you're testing the kernel directly."
1726934,2017-10-26 19:56:13 UTC,"Hey Daniel,"
1726934,2017-10-26 09:41:39 UTC,It sounds more like a kernel issue if the touchpad's not working at all.
1726947,2017-11-24 08:31:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726947,2017-11-24 08:36:25 UTC,I have workaround it installing manually the package from zesty
1726955,2017-10-24 17:14:46 UTC,"for some more information, 'glance' is similarly slow.
We do have a large number of images (~4500)."
1726955,2017-10-24 17:15:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726955,2017-10-24 17:22:24 UTC,"Before someone responds complaining that 4500 images is too much and that is the problem, lets compare this to another popular public cloud:"
1726957,2017-10-24 17:32:44 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/514774"
1726957,2018-01-17 19:56:27 UTC,"Change abandoned by chandu (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/514774"
1726957,2018-02-01 19:55:09 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/540113"
1726957,2019-09-12 10:49:17 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/540113
Reason: No longer maintaining ocata."
1726958,2017-10-24 17:28:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726958,2017-10-24 20:14:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1726958,2017-10-24 20:43:39 UTC,"This works fine in upstream.  It also works fine in the Desktop ISO install suggesting it is NOT an upstream problem, but something local to a mini iso origin desktop install."
1726958,2017-10-24 21:21:33 UTC,Sebastien:
1726958,2017-10-25 13:42:21 UTC,"I can confirm this bug is *not* present in upstream as I am using the newest GNOME stack on Arch Linux, and I haven't encountered this bug ever before on my system."
1726958,2017-10-31 14:44:59 UTC,Sebastien:
1726958,2017-10-31 18:01:42 UTC,Sebastien:
1726996,2018-01-24 01:43:33 UTC,Great. Please send that information upstream to the GDM developers here:
1726996,2019-08-05 03:46:01 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1726996,2018-01-23 10:07:23 UTC,"As I mentioned in comment #2, this can be worked around.  The issue is that GDM3 assumes that it can get an inotify watch and degrades ungracefully when it can't."
1726996,2018-01-22 02:26:57 UTC,"Dan,"
1726996,2017-10-24 17:55:41 UTC,"(It's also worth noting that I couldn't get to a PTY at all, so I had to restart my machine to be able to fix this.)"
1726996,2018-01-21 01:03:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1726996,2017-10-24 17:54:53 UTC,"This can be worked around by following the instructions at https://support.code42.com/CrashPlan/4/Troubleshooting/Linux_real-time_file_watching_errors, but it seems to me that GDM should handle this gracefully somehow."
1727002,2017-10-25 15:21:22 UTC,More information: https://bugs.openjdk.java.net/browse/JDK-8174808?focusedCommentId=14051330#comment-14051330
1727002,2017-12-16 21:29:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727002,2017-12-28 06:56:33 UTC,"The `jrt-fs.jar` shipped in `java-9-openjdk-headless` package is not compatible with Java 8, which is apparently necessary for some development tools that themselves run on Java 8 to be able to use the Java 9 JDK shipped in this package."
1727002,2017-12-28 07:15:09 UTC,Also relevant bug in Intellij IDEA: https://youtrack.jetbrains.com/issue/IDEA-179481
1727002,2017-12-28 07:16:27 UTC,Also relevant bug in Intellij IDEA: https://youtrack.jetbrains.com/issue/IDEA-179481
1727019,2017-10-24 19:14:56 UTC,FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'sme_me_mask'
1727019,2017-11-07 14:52:01 UTC,"I've set CONFIG_AMD_MEM_ENCRYPT=n for now, which gets the driver building again. Adding a linux task but also leaving the nvidia-graphics-drivers-384 open for now since I'm not sure what the ultimate resolution to this will be."
1727031,2017-10-24 19:47:20 UTC,"The underlying justification here is that currently, we are wasting (possibly scarce) entropy at each boot to generate a UUID whose global uniqueness provides no particular value to us because it doesn't persist across reboots (therefore you can't usefully refer to it from elsewhere anyway)."
1727031,2018-02-14 17:59:57 UTC,"For now part of this is ""fixed"" as netplan only generates UUIDs for the interfaces that really need them: only for NM, and only for VLAN devices."
1727039,2018-12-04 17:12:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727039,2019-09-05 17:17:13 UTC,"Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1727039,2019-11-05 04:17:45 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1727049,2017-11-01 20:59:07 UTC,It seems that the bug is already known by nVidia: https://devtalk.nvidia.com/default/topic/1019761/linux/no-sound-using-displayport-audio-with-375-82-384-59-and-384-69/
1727049,2017-11-12 22:45:10 UTC,Fixed on nvidia-387 (from ppa:graphics-drivers/ppa).
1727054,2018-03-21 00:07:15 UTC,A user on the forum reports the issue is not present in v0.48.
1727056,2018-07-03 13:22:01 UTC,"I've installed hplip version 3.17.7 (with libsane-hpaio, hplip-data and other needed libraries) on Ubuntu 16.04 from ppa:alindt/xenial-backports (default hplip 3.16.3 version from Ubuntu 16.04 doesn't support LaserJet MFP M227) and scanning started to work only after installing hp-plugin:"
1727056,2020-07-13 19:03:23 UTC,This is a mistake on the website which as of now is still not fixed.
1727089,2017-10-27 00:41:17 UTC,Excerpt from journal:
1727111,2017-10-25 00:40:33 UTC,"StacktraceTop:
 on_name_owner_vanished (connection=<optimized out>, name=0x7f016405d000 "":1.28"", user_data=<optimized out>) at gvfsproxyvolumemonitordaemon.c:467
 do_call (client=client@entry=0x558280206b30, call_type=call_type@entry=CALL_TYPE_NAME_VANISHED) at ../../../../gio/gdbusnamewatching.c:219
 call_vanished_handler (client=client@entry=0x558280206b30, ignore_cancelled=0) at ../../../../gio/gdbusnamewatching.c:245
 call_vanished_handler (ignore_cancelled=0, client=0x558280206b30) at ../../../../gio/gdbusnamewatching.c:243
 on_name_owner_changed (connection=<optimized out>, sender_name=0x7f0164026bb0 ""org.freedesktop.DBus"", object_path=0x7f0164062860 ""/org/freedesktop/DBus"", interface_name=0x7f0164054200 ""org.freedesktop.DBus"", signal_name=<optimized out>, parameters=0x7f016407cf00, user_data=0x1) at ../../../../gio/gdbusnamewatching.c:348"
1727111,2017-10-26 14:51:47 UTC,"The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1727122,2017-10-25 02:58:18 UTC,Can you share the original Inventor dxf?
1727122,2017-10-25 09:32:56 UTC,"Sure, here it is."
1727122,2017-10-25 13:32:15 UTC,Seems this is not isolated to Inkscape:
1727122,2017-10-25 23:09:59 UTC,"I need the text as ""Text"", not as a path because I need to change it at runtime for animation purposes."
1727122,2017-10-26 11:31:25 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1727127,2018-01-19 21:10:47 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/535965"
1727127,2017-10-30 21:53:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/516459"
1727127,2017-12-11 12:51:47 UTC,"Reviewed:  https://review.openstack.org/516459
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=b0e18270b4af43452d6c2e229aa76db7ff120980
Submitter: Zuul
Branch:    master"
1727127,2018-01-30 22:30:47 UTC,This issue was fixed in the openstack/heat 10.0.0.0b3 development milestone.
1727127,2018-02-19 19:24:33 UTC,"Reviewed:  https://review.openstack.org/535965
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=0519cd94fc3f95778e75f6fd917defa77f7d5afe
Submitter: Zuul
Branch:    stable/pike"
1727127,2018-04-30 10:05:16 UTC,This issue was fixed in the openstack/heat 9.0.4 release.
1727130,2019-09-30 02:32:59 UTC,This bug is old and has reached end of life (reported against 17.10 which is no longer supported).
1727130,2019-09-25 20:15:38 UTC,"FWIW This description perfectly describes behaviour is still present on 18.04 in X1C laptops. Specifically my X1 Carbon 5th Gen (fully firmware updated in Windows), fully software updated 18.04, has this behaviour repeatably.
It would appear related to variety of other bugs around touchpad malfunction on sleep awake in the X1C series. the modprobe -r psmouse && modprobe psmouse fix works for me."
1727130,2019-09-25 20:10:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727136,2018-07-25 18:09:13 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1727136,2018-06-29 02:04:31 UTC,17.10 also came across the issue when building the kernel and at the same time run the testing.
1727136,2018-04-10 16:36:53 UTC,Canonical any update: Skylake server requires the up-to-date glibc to get the turbo frequency
1727136,2018-03-14 21:38:47 UTC,Canonical Team any update on this?
1727136,2017-12-13 02:05:52 UTC,"yes. we need fix in 16.04. for 17.10, there is no issue."
1727136,2017-12-13 00:29:37 UTC,"Although the bug is marked incomplete, I hear you may want the fix made available in 16.04. Is this correct? Please confirm what you are hoping for so I can confirm the feasibility and plan the work."
1727136,2018-08-07 10:31:13 UTC,"yes, can be public."
1727136,2017-10-26 05:57:47 UTC,"Clarify that the counts of lvl1 and lvl2 are zero. So Ubuntu 17.10 doesn't hit this issue.
Change this bug to ""invalid""."
1727136,2017-10-26 02:09:30 UTC,"Adam Here you go developer has backported, link below:"
1727136,2017-10-25 16:38:26 UTC,Adam Point taken - following up with H.J code owner.
1727136,2017-10-25 06:44:05 UTC,Tested on Ubuntu 17.10 on Purley-4S. It has this issue.
1727136,2017-10-25 03:05:06 UTC,"The only way to really make this sort of update ""low key"" is to backport the fixes on the upstream branches and include it in an ""update to latest stable branch"" sort of SRU.  If we backport just these bits, not calling it out in the changelog wouldn't look good."
1727136,2020-05-18 15:12:25 UTC,Addendum to the previous comment: glibc version is 2.31-0ubuntu9.
1727136,2017-10-26 05:59:16 UTC,Ubuntu 16.04.3 LTS hits this issue. The glibc version is 2.23.
1727136,2020-05-18 14:33:48 UTC,"I'm having the same issue with Ubuntu 20.04, linux 5.4.0-31-generic:"
1727137,2018-01-24 22:31:44 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1453
1727142,2017-11-02 16:57:10 UTC,"Also stack abandon, if we still care about that."
1727142,2018-01-04 17:24:38 UTC,"Reviewed:  https://review.openstack.org/514476
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=1d24d47e7e4b6295fa12b6ec59efa0db5b2d79c7
Submitter: Zuul
Branch:    master"
1727157,2017-10-25 13:24:59 UTC,"Yes, that is a known issue."
1727157,2017-11-14 07:14:43 UTC,"we have done backporting and found working. after a week, the same error is coming again. but log says few books are with correct coding."
1727164,2017-10-27 08:53:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727177,2017-10-25 23:47:06 UTC,Thanks Lukasz.
1727183,2017-11-01 16:28:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727184,2018-03-15 00:59:22 UTC,I just upgraded a site from 17.08 to 17.11  and the settings for ceph disappeared entirely - we haven't used the cinder-ceph charm there.  Do you suggest what we need is a separate bug here?
1727184,2019-11-29 15:16:50 UTC,"Triaged back to low as the ceph options are in the charm, and ceph support is still baked in."
1727184,2017-10-26 12:55:53 UTC,Triaging this as Low; we won't remove ceph support in the cinder charm until this issue is resolved.
1727202,2018-01-03 12:14:56 UTC,Note for comment #22 - I also had B KVM guests and containers now - but it really hides from me today :-)
1727202,2018-04-30 13:34:51 UTC,Problem still present in 18.04
1727202,2018-01-03 12:30:33 UTC,"Has anyone actually checked that the new build of ntpd actually still works, please (eg. can sync the time)? If not, please could somebody check that?"
1727202,2018-01-03 12:49:55 UTC,"Discussion lead a bit off of that, but yes it synced for me in a KVM test."
1727202,2018-01-03 13:55:49 UTC,"The verification of the Stable Release Update for ntp has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1727202,2018-01-03 14:05:49 UTC,This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu3.1
1727202,2018-01-04 10:26:54 UTC,FYI - The curiosity of the /usr/local denials will be checked in bug 1741227
1727202,2018-01-04 11:22:44 UTC,"The most plausible explanation for enumerating /usr/local/bin/ is that ntpd has some hooks.d/ mechanism which gets called after syncing the time, and that runs a shell in between. So IMHO this should be allowed."
1727202,2018-04-30 14:01:08 UTC,"@Tim - Could you check the ntp apparmor profile if it has the change that was made in 1:4.2.8p10+dfsg-5ubuntu4 ?
It is a conffile so if depending on your former changes it might have been not updated by default."
1727202,2018-01-02 08:47:48 UTC,"While I see the non-crit ""other"" issue with opening its own binary I can not confirm the disconnected path issue in a current xenial guest."
1727202,2018-11-27 01:07:37 UTC,"Andrew, you could try adding:"
1727202,2018-11-27 01:22:10 UTC,"      I have since upgraded to 18.10 and I don't even see an apparmor profile
for ntp anymore."
1727202,2018-11-27 02:27:38 UTC,"On Tue, Nov 27, 2018 at 01:22:10AM -0000, Robert Dinse wrote:

> I have since upgraded to 18.10 and I don't even see an apparmor profile
> for ntp anymore.
"
1727202,2019-02-19 17:17:01 UTC,"Right, the disconnected flag is in the openntpd (usr.sbin.ntpd) profile, but not the journal one:"
1727202,2019-05-03 01:57:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727202,2019-07-03 13:22:48 UTC,"With chrony taking over for ntpd and the usage of openntpd dropping next to none this really became less and less important over time. It is fixed in ntpd and not affecting chrony.
For openntp it seems to be an issue but we wait for a reply to comment #34 as far as I read through the updates.
Updating tasks to reflect that."
1727202,2019-07-15 06:05:28 UTC,"I just diagnosed that openntpd on my 18.04.2 server to be broken (failing to run, the process died after the apparmor denials, no time adjustments ever happening) until I manually applied the changes mentioned in #34."
1727202,2019-07-15 06:09:13 UTC,"(Sadly the bug tracker won't let me change the status from ""Won't Fix"" to ""Confirmed"")"
1727202,2018-01-03 12:14:12 UTC,Thanks Martin for verifying!
1727202,2018-11-23 03:34:49 UTC,"Note that this also appears to affect openntpd in the same fashion, see following for log excerpt of a fresh 18.04 install with the latest openntpd installation:"
1727202,2018-01-03 12:13:47 UTC,"Hi Seth, I never checked why it does so but it puzzled me as well, but whatever it is, it is one of those issues that is a) not really critical and b) tries to hide (I spawned X/A guests and containers, no more triggering to take a look at the stack traces of the open - I'm sure it will be back when I have no time to look at it :-) => Heisenbug)"
1727202,2017-12-21 00:40:29 UTC,"Hello Martin, or anyone else affected,"
1727202,2018-01-03 03:01:02 UTC,Why does ntpd try to enumerate the contents of /usr/local/bin/? This in itself isn't so bad but it certainly is curious.
1727202,2017-10-25 14:44:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727202,2017-12-08 12:43:12 UTC,"Thanks Martin, this was missed on triage so far, I ran by today and marked it for the team to look at.
Unfortunately have no cycles atm to fix is up right away."
1727202,2017-12-13 15:56:26 UTC,As expected I could solve the issue in a test via flags=(attach_disconnected).
1727202,2018-01-03 08:17:22 UTC,"I locally ran Cockpit tests on our current Ubuntu 17.10 image and re-confirm that I got the ""disconnected path"" error. I then upgraded the ntp package to artful-proposed, and *that* violation is now gone. As others already saw, I now get a test failure on"
1727202,2017-12-14 06:57:28 UTC,I was in discussion with Kurt Roeckx on NTPsec before and the NTPsec folks as well but never had the time to continue - thanks you a lot for packaging it up Richard. I subscribed myself to 819806.
1727202,2017-12-15 11:46:58 UTC,"Thanks Christian! Indeed this is rather hard to reproduce locally, but that PR seems to address this. I'll let you know if it doesn't after it lands."
1727202,2017-12-16 23:26:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727202,2017-12-18 11:53:58 UTC,This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu4
1727202,2017-12-18 12:09:40 UTC,"The Bionic fix is about to complete now'ish.
Since this (if triggered) is effectively blocking the messages to appear in the syslog this can hide an arbitrary amount of further issues that the user then has next to no grasp on how to tackle."
1727202,2017-12-14 05:10:35 UTC,"I'm seeing the same errors with NTPsec (a fork of this ntpd, which I have packaged for Debian) on 16.04. The apparmor policy is copied from this ntp package. I'm not able to reproduce the problem at will, but it seems to happen regularly. The proposed change seems to have resolved it."
1727202,2017-12-18 18:28:12 UTC,"fwiw, I can see the error in every reboot on my artful vm when it's deployed with maas. I can also therefore verify the fix :)"
1727202,2017-12-19 07:37:35 UTC,"Thanks Andreas, yes I see it nearly everywhere as well.
Also thanks to spot that I missed to uopdate impact - done.
Discussion on the MP going on ..."
1727202,2017-12-19 10:21:53 UTC,Uploaded for the SRU team to evaluate
1727202,2017-12-28 14:31:12 UTC,"This isn't a 17.10 regression - it's been happening for a few years, e.g.:"
1727202,2018-01-02 08:18:55 UTC,Thanks Gordon for the extra info.
1727202,2018-01-02 08:20:17 UTC,"At the same time, @Martin are you going to test this with Cockpit or manually against (A-)proposed or should I do so?"
1727202,2017-12-18 18:12:40 UTC,"Can you please update the ""[Impact]"" section of this SRU?"
1727225,2018-11-12 21:02:00 UTC,"You mean the comment: ""it doesn't seem to me that there are  people who *never* want edge snapping""?"
1727225,2019-02-27 22:16:25 UTC,Great work! I doubled my bountysource contribution to the bounty for this. Hope others will contribute as well. Looking forward to see this merged!
1727225,2018-12-08 05:49:58 UTC,please add an option to disable it !
1727225,2019-02-21 05:04:07 UTC,I have exposed this as a dconf setting and submitted the change as a merge request to mutter:
1727225,2019-03-06 02:25:05 UTC,"I understand why people might want snapping enabled by default, but I also think the argument that there's little demand to disable it is a poor one."
1727225,2020-10-15 01:38:01 UTC,Fixed by https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1268
1727225,2019-03-25 01:23:29 UTC,You can monitor the progress in https://gitlab.gnome.org/GNOME/mutter/merge_requests/455
1727225,2020-04-06 09:53:06 UTC,Also tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/181
1727225,2020-04-06 09:54:21 UTC,Also tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/181
1727225,2020-05-26 09:10:41 UTC,A new fix has been proposed!
1727225,2018-11-12 18:09:22 UTC,"(In reply to anders from comment #12)

> Still no takers for this feature?
"
1727225,2019-03-22 14:00:59 UTC,"I've been wanting to disable the edge resistance as well.
Any update on this feature getting merged?"
1727225,2018-11-12 10:35:47 UTC,"Still no takers for this feature? Should be fairly easy for someone with knowledge of the code, and it now pays $215 from https://www.bountysource.com/issues/35544484-window-edge-resistance-snapping-not-tiling-no-way-to-disable"
1727225,2012-10-02 16:46:54 UTC,"I would like the edge snapping to be cancelable at use time. I often want to put windows in the upper-right corner of my monitor, and it would be nice if I could press a key to not have it title/tile the window."
1727225,2017-08-20 10:48:20 UTC,*** Bug 753279 has been marked as a duplicate of this bug. ***
1727225,2012-07-09 05:13:30 UTC,It does exist. It's under the hard-to-find key of
1727225,2012-07-09 06:38:55 UTC,"(In reply to comment #1)

> It does exist. It's under the hard-to-find key of
>
>   org.gnome.mutter edge-tiling
>
> For gnome-shell, there's:
>
>   org.gnome.shell.overrides edge-tiling
"
1727225,2012-07-11 11:03:55 UTC,"To get the problem more clear, the thing that I'm talking about is provided by file edge-resistance.c"
1727225,2017-10-25 08:16:15 UTC,"I've just realized what I was seeing is not gnome-shell being bad at redraws, but just window snapping where you wouldn't expect. Made a suggestion for improving the feature here:"
1727225,2012-07-09 04:22:12 UTC,"I know there is an option to enable or disable edge-tiling feature. But I couldn't find an option that enables or disables edge resistance/snapping features that provide specific interactions between windows, which are enabled by default. I find it very hard to work when I have many (over 5, usually) windows opened on my desktop; dragging a window feels like a game of tug-of-war. Very annoying."
1727225,2015-04-04 19:14:53 UTC,"It's been quite some time. No reports at all, so far. I don't know whether I should create another bug report with more clearer description about this issue."
1727225,2015-04-09 17:40:20 UTC,Please don't file another bug report - this is sufficient.
1727225,2017-05-26 11:15:59 UTC,"""it doesn't seem to me that there are  people who *never* want edge snapping."""
1727225,2017-05-29 12:38:51 UTC,This seems like a duplicate as well: https://bugzilla.gnome.org/show_bug.cgi?id=753279
1727225,2015-04-04 18:59:24 UTC,*** Bug 712352 has been marked as a duplicate of this bug. ***
1727236,2017-10-25 08:59:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/514962"
1727236,2017-12-05 05:46:16 UTC,"Change abandoned by junbo.li (<email address hidden>) on branch: master
Review: https://review.openstack.org/514962"
1727237,2018-03-26 17:24:17 UTC,"Dimitri,"
1727237,2018-01-29 13:11:34 UTC,"@ #19: Mathieu,
I included the '234-2ubuntu12.3~mtrudel1' from the ppa you mention to my computer.
Unfortunately no change in behavior. I am still not forwarded to the captive portal after connecting to this particular wifi.
Do you have a suggestion what I could try?"
1727237,2018-01-31 19:08:24 UTC,I too am still encountering this issue.
1727237,2018-01-31 22:00:36 UTC,"@Axel, can you record what you see on the screen as you login (I do not need to see keypresses, but maybe seeing what happens on screen as things refresh would help)."
1727237,2018-02-08 13:41:44 UTC,"@Mathieu,
Were the logs I sent you of any value to you for the debugging?"
1727237,2018-02-14 21:56:28 UTC,I can't seem to find where you sent me logs?
1727237,2018-03-26 14:53:37 UTC,"Please note this issue is now documented as a DNS violation at
https://github.com/dns-violations/dns-violations/blob/master/2018/DVE-2018-0001.md"
1727237,2018-04-12 22:02:34 UTC,"Dimitri, can you please confirm what the effect of this patch is when a user has manually reconfigured resolved to enable DNSSEC?  Does this do the right thing, or does it become a downgrade attack?"
1727237,2018-04-25 20:42:33 UTC,"OK,"
1727237,2018-04-16 08:22:43 UTC,Hmm... I've installed systemd 237-3ubuntu8.
1727237,2018-04-25 19:18:34 UTC,I freshly installed the latest Kubuntu Bionic nightly image from today night. That should be rather close to tomorrow's release.
1727237,2018-04-25 19:44:31 UTC,"On Wed, Apr 25, 2018 at 07:18:34PM -0000, Pete wrote:

> I freshly installed the latest Kubuntu Bionic nightly image from today
> night. That should be rather close to tomorrow's release.
"
1727237,2018-04-25 19:45:17 UTC,"Axel and Pete, please file new separate bugs for your issues. This particular bug is closed for Ubuntu 18.04 LTS."
1727237,2018-01-26 15:51:47 UTC,I also have been experiencing this. Connecting to WiFi network that uses any captive portal fails.
1727237,2018-08-05 17:32:00 UTC,The fix for this bug is causing me problems with name resolution on the LAN using dnsmasq as an upstream server:
1727237,2019-08-30 18:50:40 UTC,"I found the addition of the 18.04 libnss-resolve package fixed my (intermittent) problems with name-resolution failures. Earlier comments indicate this package was not installed.  The installation alters the nsswitch.conf file's hosts line to  add  ""resolve [!UNAVAIL=return]"" before ""dns""."
1727237,2018-04-13 11:24:24 UTC,This bug was fixed in the package systemd - 237-3ubuntu8
1727237,2018-01-25 14:52:10 UTC,"Xenial is affected too (systemd v229 looks to be, in general), so when SRUing we might as well push the fix there too, even if resolved is not typically used on Xenial."
1727237,2018-03-07 07:03:39 UTC,"@cyphermox,"
1727237,2018-01-18 15:53:52 UTC,Packages are in my ppa: https://launchpad.net/~cyphermox/+archive/ubuntu/sru/+packages
1727237,2018-01-18 15:56:01 UTC,"I updated the importance and status as well, this bug was not in fact Fix Committed, I checked with Dimitri. Fix Committed was set because of the proposed change to caching, but it doesn't look like it helps."
1727237,2017-10-25 10:52:41 UTC,What is the release / package version in use of systemd?
1727237,2017-10-25 11:46:42 UTC,"Yes, this is a captive portal situation on up-to-date 17.10. The captive portal popup fails with a DNS error looking for securelogin.arubanetworks.com and then hilarity ensues. Manually editing /etc/resolv.conf to use one of these DNS servers makes it all work. So the problem is systemd-resolved which is the default resolv.conf:"
1727237,2017-11-06 12:12:29 UTC,"I also experienced this problem on Ubuntu 17.10. Tried to connect to a wifi network, that utilized a captive portal, failed miserably. The DNS redirect to the captive portal would not occur. Manually overwriting /etc/resolv.conf with nameservers other than ""127.0.0.53"" got me to the captive portal login page. I spent a few hours on vacation trying to workaround this. Really unfortunate problem."
1727237,2017-11-06 12:22:36 UTC,"What is the release / package version in use of systemd?
234-2ubuntu12.1"
1727237,2017-11-21 12:46:21 UTC,The issue is with systemd-resolvd not adding the captive portal DNS after the logon. This worked fine with dnsmasq in 16.04 (and I assume 17.04).
1727237,2017-11-21 18:54:53 UTC,I thought I'd add the information from my favourite DNS debugging tool while the data may still be close to useful:
1727237,2017-11-23 18:13:52 UTC,"Checking for the state of the domain from outside a captive portal won't get much; ""securelogin.arubanetworks.com"" only exists while you're behind the captive portal, in unauthenticated mode."
1727237,2017-11-20 02:18:11 UTC,All captive portal wifi connections are failing with Ubuntu 17.10.  This was confirmed on two different captive portals which both worked just fine with other devices.  The solution was to go back to Ubuntu 17.04.
1727237,2017-11-28 00:21:23 UTC,My understanding is that systemd-resolved as shipped in Ubuntu is meant to not have DNS caching enabled at all.
1727237,2017-11-30 14:58:31 UTC,"I believe caching is enabled by default, this might be a regression in behaviour since switching to 127.0.0.53 caching resolver. It does drop caches upon every new connection / re-connection."
1727237,2018-01-17 12:51:38 UTC,I would like to test it here with our public company-network that uses securelogin.arubanetworks.com.
1727237,2017-12-01 09:54:54 UTC,"Thanks all, and Dimitri allow me to sponsor that Starbucks coffee :)"
1727237,2018-01-02 09:44:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727237,2018-01-02 10:23:27 UTC,Can we know what's the fix?
1727237,2018-01-15 20:19:00 UTC,"So, after looking at it more, it seems the issue with Datavalet is due to EDNS0-enabled queries failing to be captured and rewritten by the captive portal. It might not in fact be the same issue as for securelogin.arubanetworks.com, though the wireless hardware comes from the same manufacturer."
1727237,2017-11-27 18:55:53 UTC,"So I managed to reproduce this in a way that looks correct (Starbucks WiFi here uses Datavalet but fails in a way that looks the same: it thinks you're logged in once you clicked the ""Login"" button on the captive portal page once, but then updates DNS, but still attempts to look up secure.datavalet.io (but this is no longer resolving because we're in the public side now); and once you try to hit another site, you did not get to the ""landing"" page on the public side so it thinks you're still unauthenticated."
1727245,2017-11-28 16:01:00 UTC,"Actually, the ""Restart rsync service"" handler is supposed to enable the systemd unit..."
1727245,2017-12-26 14:30:31 UTC,Still waiting for feedback from the Ansible bug report.
1727245,2018-11-06 08:24:05 UTC,"According to the Ansible bug report, it was fixed and backported into Ansible 2.6 and 2.7."
1727256,2017-10-25 10:07:46 UTC,"Your A1 and B1 are the same norizontal split command. You haven't attached screenshots, so I can't see what you're seeing to understand your problem. In both those cases (A & B) there should be minimal (if any) zooming. You really need three panes to (Ctrl-O, Ctrl-E, Ctrl-O, Zoom) before you really start seeing the impact."
1727260,2018-04-20 13:14:20 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1727260,2018-04-23 23:19:25 UTC,"Reviewed:  https://review.openstack.org/560690
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=92bd7ea118fec4791b903871cdc95d0cd71583e2
Submitter: Zuul
Branch:    stable/pike"
1727260,2018-04-25 09:20:57 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1727260,2018-04-11 23:31:00 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/560690"
1727260,2018-03-07 23:30:27 UTC,This issue was fixed in the openstack/nova 17.0.1 release.
1727260,2017-10-25 16:19:47 UTC,"We have seen this downstream where an initial volume detach fails due to multipath ""map in use"" during the detach from the hypervisor host, after the volume was already detached from the guest. The volume remains connected in cinder (which is correct). However, when a second detach is tried, nova finds the volume already detached from the guest and assumes it was also successfully detached from the hypervisor host, which is not necessarily true. So it continues on to terminate the connection in cinder, which results in failed paths in multipathd."
1727260,2018-02-22 03:28:24 UTC,"Reviewed:  https://review.openstack.org/515008
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ce531dd1b763704b9043ddde8e80ac99cd193660
Submitter: Zuul
Branch:    master"
1727260,2018-02-21 14:57:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/546655"
1727260,2018-03-06 16:06:16 UTC,"Reviewed:  https://review.openstack.org/546655
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6a072b5c5a3ff9de7f4b42cda517ead17efe561
Submitter: Zuul
Branch:    stable/queens"
1727262,2017-10-25 10:38:46 UTC,"I want to introduce new l3 agent config options, like
HA_NETWORK_PROVIDER_NETWORK_TYPE=vlan
HA_NETWORK_PROVIDER_PHYSICAL_NETWORK=ovs"
1727269,2020-11-17 05:31:57 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1727269,2017-10-30 03:37:30 UTC,"I see, thanks. Yes it sounds like legacy X apps are the ones affected."
1727269,2017-10-28 19:06:12 UTC,"The above mentioned darker window edges in 17.10 do not appear in all windows. They appear in Firefox, Thunderbird and e.g. the Gnome Terminal (maybe this has to do with gnome-terminal being at 2.24). The window decorations in for example the file-manager are not affected."
1727269,2017-10-28 09:38:52 UTC,"In the attached screenshot one can see that there is a difference in the color of the outer pixels of the screen edge. In 17.10 there is a darker grey. Both windows were in the front, when the screenshots were taken. To me, due to the less smooth transition of colors, the screen edges in 17.10 look somewhat rough, ripped."
1727269,2017-10-27 03:04:35 UTC,"I have put your two screenshots side by side, flipped, and zoomed in. See attached."
1727269,2017-10-26 10:09:35 UTC,"Thanks for your quick reply. No, its on the Laptop screen with the correct driver for each laptop in place. Maybe I'm a little too sensitive for these cosmetic issues, the difference strikes me immediately. Maybe its just because the buttons are scaled a little bigger in 17.10. I see grey pixels inside the red close button. It looks cleaner in 16.04. Screenshots attached."
1727269,2017-10-26 02:27:00 UTC,"Also, are you looking at the laptop screens or VGA output? Just need to ask :)"
1727269,2017-10-26 02:26:11 UTC,I'm looking at both 16.04 and 17.10 on identical monitors and can't see the problem you're talking about.
1727269,2017-10-26 10:10:27 UTC,And the Screenshot for 16.04.
1727275,2017-11-01 07:34:51 UTC,"Verified with sysdig 0.8.0-1ubuntu3 on azure kernel, it works as expected.
Thanks"
1727275,2017-11-09 16:05:45 UTC,This bug was fixed in the package sysdig - 0.8.0-1ubuntu3
1727275,2017-11-09 16:05:50 UTC,"The verification of the Stable Release Update for sysdig has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1727275,2017-11-09 07:59:19 UTC,"Hi Łukasz,"
1727275,2017-11-08 20:13:47 UTC,@Po-Hsu Lin: did you do regression checking on supported kernel versions as per what was written in the [Regression Potential] field?
1727275,2017-10-31 10:29:12 UTC,"Hello Po-Hsu, or anyone else affected,"
1727275,2017-10-25 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1727275,2017-10-27 18:55:55 UTC,"Sam, so you mind testing my fix using the PPA below:"
1727275,2017-10-27 14:39:15 UTC,Package built OK: https://launchpad.net/~colin-king/+archive/ubuntu/amber/+packages
1727275,2017-10-27 14:38:51 UTC,Debdiff
1727275,2017-10-27 14:34:43 UTC,"Tested on 4.4, 4.8 and 4.13 HWE kernels on Xenial. Passes regression tests. Should work fine now on all kernels from 4.4..4.13"
1727275,2017-10-31 08:09:19 UTC,"Verified with Colin's ppa, the test has passed with the dkms."
1727276,2017-10-26 18:39:32 UTC,"could you change keyboard layout switch combination to something without
ALT (ctrl+shift) ? notify us about behavior."
1727276,2017-10-26 21:40:30 UTC,I'm using default win+space. And this problem happens only sometimes.
1727279,2017-10-25 11:01:40 UTC,"StacktraceTop:
 Constants () at ../../third_party/swiftshader/src/Shader/Constants.cpp:249
 call_init (l=<optimized out>, argc=argc@entry=11, argv=argv@entry=0x7ffc7ad71ab8, env=env@entry=0x7ffc7ad71b18) at dl-init.c:72
 call_init (env=0x7ffc7ad71b18, argv=0x7ffc7ad71ab8, argc=11, l=<optimized out>) at dl-init.c:30
 _dl_init (main_map=main_map@entry=0x559a93542e40, argc=11, argv=0x7ffc7ad71ab8, env=0x7ffc7ad71b18) at dl-init.c:120
 dl_open_worker (a=a@entry=0x7ffc7ad70540) at dl-open.c:575"
1727279,2017-10-28 03:58:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727279,2017-11-07 16:15:37 UTC,"Thank you for the report Chris. It looks like what crashed is the GPU helper process, and I assume that means you don't get hardware acceleration in the browser. Did you get that crash report shortly after launching the browser? Did you get it again since then? Could you please point chromium to ""chrome://gpu"" (in the address bar), save the resulting page and attach it here? Thanks!"
1727281,2017-10-25 13:45:28 UTC,too
1727283,2017-12-21 01:04:56 UTC,"In 3.3.2, there are patches that fix bundle operations when upgrading from ECL's asdf. Maybe they fix that issue. Or not."
1727283,2017-10-26 22:10:00 UTC,"Everything is possible. Maybe this should be done for greater compatibility with other implementations. Although my interaction with ECL maintainers suggests that they like to minimize the amount of things linked in (up to not including ASDF itself), so I'm not sure how popular that change would be."
1727283,2017-10-26 21:32:49 UTC,I guess it's then not possible for defsystem-depends-on to add those dependencies onto depends-on machinery for ecl.
1727283,2017-10-26 21:15:00 UTC,Maybe defsystem-depends-on should make it easy for the ddo dependency to declare matching runtime dependencies on depends-on.
1727283,2017-10-26 20:16:20 UTC,"OK, I installed Debian in a chroot and could reproduce your issue with its ecl 16.1.2."
1727283,2017-10-26 07:31:44 UTC,Do you have a machine on which to test that?
1727283,2017-10-26 07:32:45 UTC,"Also, what version of CFFI are you using?"
1727283,2017-10-25 16:32:52 UTC,"Not only iolib is affected, the same happens on a dependency to osicat.
asdf versions before that commit work, and since that commit this is the error for osicat:"
1727283,2017-10-26 11:43:53 UTC,"I have the most recent quicklisp distribution, but I have tested it with cffi versions 0.19 and 0.18 ."
1727290,2018-09-13 04:38:14 UTC,"This issue still exist
4.15.0-1023.24-azure
http://10.246.72.46/4.15.0-1023.24-azure/bionic-linux-azure-azure-4.15.0-Standard_A6-ubuntu_unionmount_overlayfs_suite/ubuntu_unionmount_overlayfs_suite/results/ubuntu_unionmount_overlayfs_suite.overlayfs/debug/ubuntu_unionmount_overlayfs_suite.overlayfs.DEBUG.html"
1727290,2019-11-12 17:38:20 UTC,"Hi Sam,"
1727290,2019-12-17 20:50:37 UTC,"marking fix released On 8/21/2019, the git repo was updated for this test. It properly uses the upstream version now. Since then this test has been passing on Azure."
1727290,2019-09-30 05:13:36 UTC,Passed with B-azure-hwe 5.0
1727290,2019-09-05 06:15:17 UTC,"As we have updated the upstream git repo, this bug will needs to be revisited."
1727290,2019-05-24 14:24:47 UTC,So far the previous comment has cropped up on the following instance types:
1727290,2019-05-24 14:22:43 UTC,This is affecting azure linux-azure cosmic 4.18.0-1019.19.
1727290,2018-09-12 18:42:55 UTC,"very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update."
1727290,2019-10-14 10:00:04 UTC,Passed with D-Azure 5.0
1727290,2017-10-31 08:48:20 UTC,This issue can be reproduced on 4.11.0-1014.13 azure kernel.
1727290,2017-10-30 11:33:21 UTC,"Hey Joe,"
1727290,2017-10-25 18:32:30 UTC,"It might be worth seeing if this is already fixed in mainline as well:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6"
1727290,2017-10-25 18:31:41 UTC,"Also, do you know if this issue is a regression?  If it is, we can bisect down the commit that introduced the bug."
1727290,2017-10-25 18:21:56 UTC,"Is this only happening on the linux-azure kernel, or also with the generic kernel?"
1727290,2017-10-25 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1727290,2017-10-31 10:01:21 UTC,"Verified with the oldest version in the archive: 4.11.0-1009-azure
This issue still exist."
1727291,2017-10-25 11:27:10 UTC,See also: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1536547
1727291,2017-10-25 20:36:57 UTC,Thanks for your report!
1727306,2017-10-28 10:16:31 UTC,"https://youtu.be/qqwMvxReyTA
org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name', {'name':
':1.878'}): org.debian.apt.install-or-remove-packages"
1727306,2017-10-28 00:36:18 UTC,Can you describe what you were trying to install and the method you were using?
1727308,2017-10-26 02:32:46 UTC,Do you mean keyboard layout? And can you explain the problem in more detail?
1727308,2017-10-26 09:16:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1727308,2017-10-26 12:21:13 UTC,"CAPS LOCK key I have change the keyboard layout. When you change the layout
automatically triggered and shift. In this case, if immediately after the
change of the layout to continue to print, printing will not occur. At this
time, the indicator will be displayed to change the layout."
1727308,2017-10-26 13:13:44 UTC,"The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1727308,2017-10-26 14:30:27 UTC,"https://bugzilla.gnome.org/show_bug.cgi?id=644090
https://bugzilla.gnome.org/show_bug.cgi?id=789523"
1727308,2017-10-27 08:13:01 UTC,thanks
1727308,2018-08-08 08:13:04 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1727321,2018-03-03 22:18:44 UTC,"My apologies for worrying all the subscribers, but I would like to draw attention to this bug due to approaching of the LTS release. Implementation of drag-and-drop through the launcher in Unity7 is just perfect. Thus, drag-and-drop is an important part of the workflow for users of Unity7. Many of them will migrate to the new LTS soon, and they will definitely lack the option of drag-and-drop through the Ubuntu Dock.
So it looks quite important to implement this option in 18.04."
1727321,2017-10-26 16:23:15 UTC,There is an upstream gnome-shell request about that on https://bugzilla.gnome.org/show_bug.cgi?id=644422
1727321,2017-11-03 09:58:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727321,2017-10-26 13:53:44 UTC,"This refers to any file. For example to move the file to the browser, go to
the desktop, grab a file, drag it onto the browser icon in the application
bar should activate the window of the specified application. It is
necessary to activate a hidden window and passing it any argument, for
example, the path to the file. Sometimes it is easier to transfer to the
browser of the picture than to look for it again in Explorer to add in some
field."
1727321,2017-10-26 12:11:25 UTC,"* Is this reproducible?
Yes
* If so, what specific steps should we take to recreate this bug?
Click with the left mouse button on the file while holding down drag the
icon on the panel. The panel does not react, as the icon of the application."
1727321,2017-10-26 09:15:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1727321,2017-10-26 13:16:29 UTC,what file? do you mean you are trying to dnd a file from nautilus to the launcher? what would you expect that to do?
1727328,2017-10-26 03:45:23 UTC,neutron-lbaas bug is tracked in not neutron but octavia project
1727328,2017-10-26 09:56:25 UTC,I'm not sure but AFAIK octavia migrated to storyboard some time ago so You probably report it there
1727332,2017-11-01 10:51:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727335,2017-10-25 14:06:44 UTC,This project no longer accepts bugs via launchpad.  Please use OpenStack Storyboard instead: https://storyboard.openstack.org/#!/project/907
1727337,2018-01-18 18:16:52 UTC,"The verification of the Stable Release Update for lime-forensics has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1727337,2018-01-18 18:16:48 UTC,This bug was fixed in the package lime-forensics - 1.7.2-1ubuntu1
1727337,2018-01-18 12:36:49 UTC,Adding more details. I also have run the ADT tests for the following kernels to ensure there's no regressions:
1727337,2018-01-18 12:11:04 UTC,*ADT tests are passing for version 1.7.2-1ubuntu1 with kernel 4.13.
1727337,2017-12-06 12:41:33 UTC,"Hello Seth, or anyone else affected,"
1727337,2018-01-18 11:53:57 UTC,"Hi, Robie. Thanks for the explanation on the versioning."
1727337,2017-12-06 12:41:19 UTC,"I'd prefer a version string of 1.7.2-1ubuntu0.1 to make it clear that this was an SRU (following https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging), but I'll accept 1.7.2-1ubuntu1 as it works in this particular case."
1727337,2018-01-18 11:54:14 UTC,ADT tests are passing version for 1.7.2-1ubuntu1 with kernel 4.13.
1727342,2017-10-26 15:50:38 UTC,"Octavia bugs are no longer tracked in launchpad (all Openstack projects are being moved to Storyboard).
Please open this bug in Storyboard if you want to followup with this bug.
https://storyboard.openstack.org/#!/project/906"
1727343,2018-01-18 18:04:23 UTC,"The verification of the Stable Release Update for rt-tests has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1727343,2018-01-18 18:04:19 UTC,This bug was fixed in the package rt-tests - 0.93-1ubuntu2
1727343,2018-01-18 12:48:57 UTC,"I have tested the version 0.93-1ubuntu2 and the DKMS package successfully builds and loads on kernels 4.13, which was the issue reported in this bug."
1727343,2017-11-02 23:37:10 UTC,"Hello Seth, or anyone else affected,"
1727343,2017-11-30 17:36:24 UTC,Could you add some verification details please?
1727358,2020-01-22 20:50:38 UTC,"Eric, this bug is about the linux-kvm kernel _in Ubuntu_.  If you're seeing a cloud-init issue on Centos, then please file a separate bug."
1727358,2020-01-22 20:35:01 UTC,"Ok, I got a question for all the interested folks out there;"
1727358,2019-12-12 15:39:52 UTC,"In Openstack Newton (linux-kvm) with Centos 7 (latest cloud-image) with cloud-init 19.3, the delay is observed.  I think this is due to the version that Centos ships with for python (2.7.5)."
1727358,2019-02-04 12:19:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727358,2017-10-30 17:36:59 UTC,Marking as wont-fix for cloud-init for now as that would be a workaround for the base problem that is not desired right now.  Adding linux-kvm to evaluate why this difference exists between linux-generic and linux-kvm
1727358,2017-10-28 03:24:17 UTC,"So far I've tested in GCE and Azure, and both platforms show no delays at all due to lack of entropy at boot.  Unless someone identifies a platform where this actually causes boot delays other than linux-kvm, which is presumed due to a missing kernel option, there's no point in changing anything in cloud-init or python."
1727358,2017-10-27 23:59:53 UTC,"With python3-dbg and python3.6-examples installed, here's a commandline for getting to the problematic getrandom() call."
1727358,2017-10-27 23:48:53 UTC,"This looks like a chain of decisions that are all locally reasonable but when put together may not give a sensible result.  cloud-init uses jinja2 as a sensible templating engine.  jinja2 has async handling, which relies on asyncio.  asyncio uses the multiprocessing module, which has both thread and process models; and the process model sets up a secure (true random) key to use for IPC."
1727358,2017-10-27 23:14:55 UTC,"I've tracked down the blocking use of randomness in cloud-init's python module initialization.  There are several nonblocking calls to getrandom(), which I believe should be fine; then a blocking call in the multiprocessing module."
1727358,2017-10-27 17:53:28 UTC,"this does also reproduce:
 qemu-system-x86_64 -enable-kvm  \
    -device virtio-scsi-pci,id=virtio-scsi-xkvm  \
    -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00  \
    -drive file=my.img,id=disk00,if=none,format=qcow2,index=0  \
    -device virtio-blk,drive=disk00,serial=my.img  \
    -drive file=my-seed.img,id=disk01,if=none,format=raw,index=1  \
    -device virtio-blk,drive=disk01,serial=my-seed.img  \
    -snapshot -nographic -m 768"
1727358,2017-10-26 19:03:46 UTC,Libvirt XML for the VM.
1727358,2017-10-26 19:03:14 UTC,"It really is *defaults* though, because you don't want to have any extra devices included that could throw off the boot (such as a RNG, which should not be added by default). In any case, I'll attach the xml I use as well, but I reproduce the build on a typical artful install."
1727358,2017-10-26 18:37:55 UTC,"On Thu, Oct 26, 2017 at 06:07:57PM -0000, Mathieu Trudel-Lapierre wrote:

> You can easily reproduce this by running the following image in virt-
> manager with a default setup (and optionally add a RNG device if
> necessary):
"
1727358,2017-10-27 21:23:52 UTC,"I've taken your kernel (vmlinuz-4.4.0-1009-kvm) and booted a ""normal"" cloud image with that kernel.
It hangs similarly (but for noticibly shorter time)."
1727358,2017-10-26 18:07:57 UTC,You can easily reproduce this by running the following image in virt-manager with a default setup (and optionally add a RNG device if necessary):
1727358,2017-10-25 20:24:37 UTC,"Could you run
  cloud-init collect-logs
And then attach the cloud-init.tar.gz"
1727358,2017-10-26 18:14:08 UTC,You'll want to add an additional disk to provide the metadata for cloud-init too. The exact iso file I have used is attached.
1727358,2017-10-26 01:41:51 UTC,"Please explain how you did this.
What did you download, what qemu commands did you run."
1727358,2017-10-26 01:43:12 UTC,"possibly related, but was fixed:
 https://bugs.python.org/issue25420"
1727358,2017-10-26 03:15:26 UTC,"On Thu, Oct 26, 2017 at 01:43:12AM -0000, Scott Moser wrote:

> possibly related, but was fixed:
>  https://bugs.python.org/issue25420
"
1727358,2017-10-25 23:31:52 UTC,"This is running on *minimized* images, with linux-kvm kernel; so there might well not be CONFIG_DMI. This is however not the issue (or most likely not). Tests are done in qemu, to simulate running the images in openstack for now (but they are meant to start in openstack without issues). It's simply more convient to test quickly."
1727358,2017-10-26 15:24:16 UTC,"On Thu, Oct 26, 2017 at 10:37:37AM -0000, Scott Moser wrote:

> Only via 'import random' and light usage.
"
1727358,2017-10-26 15:54:44 UTC,"You can grep through, the onlyi real function taht  uses it is 'rand_str'.
and i'm not sure really why that would be called at the point that you're
seeing the slow down."
1727358,2017-10-26 15:56:24 UTC,"You can grep through, the onlyi real function taht  uses it is 'rand_str'. and i'm not sure really why that would be called at the point that you're seeing the slow down."
1727358,2017-10-26 17:53:22 UTC,"On Thu, Oct 26, 2017 at 03:56:24PM -0000, Scott Moser wrote:

> You can grep through, the onlyi real function taht  uses it is
> 'rand_str'. and i'm not sure really why that would be called at the
> point that you're seeing the slow down.
"
1727358,2017-10-26 10:37:37 UTC,Only via 'import random' and light usage.
1727362,2017-10-25 14:27:23 UTC,"StacktraceTop:
 brasero_task_ctx_stop_progress (self=0x5643692e1fa0) at burn-task-ctx.c:1025
 brasero_task_run_loop (error=0x7ffe215150f0, self=0x5643692e1fa0) at burn-task.c:466
 brasero_task_start_items (self=self@entry=0x5643692e1fa0, error=error@entry=0x7ffe215150f0) at burn-task.c:582
 brasero_task_start (self=0x5643692e1fa0, fake=fake@entry=0, error=error@entry=0x7ffe215150f0) at burn-task.c:623
 brasero_task_run (self=<optimized out>, error=error@entry=0x7ffe215150f0) at burn-task.c:682"
1727386,2017-10-26 07:02:43 UTC,"Tried this on a second computer. Same results. Even though OpenVPN  is working regardless of error.
Error now keeps popping up in every ""apt update""."
1727386,2018-01-02 12:10:13 UTC,"After clean install the problem has not appeared.
openvpn installed without a problem."
1727394,2019-09-19 11:59:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1727397,2019-09-19 14:49:30 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1727404,2018-10-08 16:32:33 UTC,We have encountered this issue while working on snaps of Krita and kdenlive. Here is an example AppArmor denial:
1727413,2017-10-25 16:10:59 UTC,"This seems to be new to Pike and Ocata, as in Newton I see the template correctly configures dns_domain:"
1727415,2020-09-14 07:38:01 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1727417,2019-09-19 11:59:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1727419,2018-08-06 19:31:54 UTC,"This seems to be a Django error in how the form validation is handling the errors.  The verbose name for this model is ""Physical zone"" while the name of the field is ""name"".  The field name ""name"" is being capitalized for some reason by Django."
1727419,2018-09-04 15:42:22 UTC,@Newell does that mean we cannot fix it?
1727419,2018-08-03 19:23:58 UTC,Trying to save a new AZ with an already existing name gives this stacktrace:
1727423,2018-06-15 00:19:47 UTC,It's there as /usr/share/doc/pass/examples/dmenu/passmenu - would that not be enough?
1727423,2018-11-25 03:29:57 UTC,"It's not in a location where most binaries would be. Additionally, there's no documentation in the man page for `pass` about `passmenu`, whether by location or invocation. There's no output from `apt` when installing that points to the location, and I don't see it in dmenu. It might as well not exist for any *practical* use."
1727423,2018-11-25 03:30:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727425,2019-07-24 10:31:23 UTC,https://github.com/snapcore/snapcraft/pull/2539
1727428,2017-10-25 16:41:20 UTC,"StacktraceTop:
 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:62
 append_value_to_blob (value=value@entry=0x563e7e6a1b20, type=0x7fc9202c0ea8 <g_variant_type_info_basic_chars+40>, mbuf=mbuf@entry=0x7ffe119f7f80, out_padding_added=out_padding_added@entry=0x0, error=error@entry=0x0) at ../../../../gio/gdbusmessage.c:2497
 append_value_to_blob (value=value@entry=0x7fc8cc01f0f0, type=<optimized out>, mbuf=mbuf@entry=0x7ffe119f7f80, out_padding_added=out_padding_added@entry=0x7ffe119f7c48, error=error@entry=0x0) at ../../../../gio/gdbusmessage.c:2476
 append_value_to_blob (value=value@entry=0x7fc90c0100c0, type=<optimized out>, mbuf=mbuf@entry=0x7ffe119f7f80, out_padding_added=out_padding_added@entry=0x0, error=error@entry=0x0) at ../../../../gio/gdbusmessage.c:2437
 append_value_to_blob (value=value@entry=0x563e7e4510c0, type=<optimized out>, mbuf=mbuf@entry=0x7ffe119f7f80, out_padding_added=out_padding_added@entry=0x7ffe119f7e68, error=error@entry=0x0) at ../../../../gio/gdbusmessage.c:2476"
1727428,2017-10-26 13:11:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727430,2017-10-26 02:42:05 UTC,"We're also looking at allowing you to have ipv6 for lxdbr0. But we're not
sure if that will land in 2.3 or not until 2.4."
1727430,2017-10-25 16:40:50 UTC,"Some further digging in reveals that this is actually happening because I have a different lxd server configured as my default, so the lxd commands run against that remote rather than localhost."
1727435,2017-11-06 09:54:33 UTC,"This one seems the simplest one regarding the other two error message bug reports posted. However, I could use some guidance on how to fix this one if I could have the opportunity to work in this one."
1727435,2017-11-13 23:47:19 UTC,"Gustavo, this is handled in `snapcraft/internal/meta.py`, and the error in question is `snapcraft.internal.errors.InvalidDesktopFileError`. That one probably needs to be split into multiple exceptions for each use, where each give recommendations for how to fix the problem they represent."
1727443,2017-12-04 07:13:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727443,2018-09-08 06:54:12 UTC,how to fix this error. Daily I am encountering this error
1727447,2018-02-07 10:30:35 UTC,Also have this issue on my dell xps.
1727447,2017-11-03 22:29:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727447,2017-10-25 17:24:46 UTC,This is generated every second:
1727447,2018-02-08 21:34:02 UTC,"This issue is with Steam and the Steam runtime libraries. It has been present for some time https://github.com/ValveSoftware/steam-for-linux/issues/3831. The problem arises when the legacy libraries included in the Steam runtime conflict with newer software installed on the system. This issue affects all Steam users and is not specific to any distribution or spin. One can easily reproduce it simply by installing and running Steam on Arch Linux, Debian, Fedora and Ubuntu."
1727465,2017-10-25 19:40:02 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1727466,2019-08-05 03:46:17 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1727466,2017-10-31 09:58:23 UTC,"replaced Xauthority:
#!/bin/bash
gdm=`pidof gdm3`
until [ $gdm -gt 0 ] do
su - gdm -s /bin/sh
export $(dbus-launch)
export XAUTHORITY=/run/user/121/gdm/Xauthority
DISPLAY=:0
export DISPLAY
numlockx on
done
exit"
1727466,2017-10-30 19:09:36 UTC,"Dirty hack
Make sure numlockx is installed and
sudo sed -i -e 's/#WaylandEnable=false/WaylandEnable=false/g' /etc/gdm3/custom.conf"
1727468,2019-07-03 20:51:07 UTC,should be in the spreadsheet if we want to do this.
1727470,2019-12-26 18:28:22 UTC,The example from #7 looks good to me! :-)
1727470,2020-11-07 11:35:39 UTC,In proposed now
1727470,2020-11-04 12:27:54 UTC,"Not syncing this, want to get the existing upload migrated first. Which is Stuck on apt-clone regression."
1727470,2020-10-27 20:31:51 UTC,Released upstream as python-apt 2.1.15
1727470,2020-10-27 18:22:12 UTC,https://salsa.debian.org/apt-team/python-apt/-/merge_requests/52
1727470,2020-01-02 13:16:08 UTC,"Julian, feel free to let me know if you need any help, for example with testing etc. It would be great if this could be fixed before Ubuntu 20.04 (or at least 20.10) is released. :-) Thanks!"
1727470,2019-12-11 15:24:24 UTC,e.g. for the french:
1727470,2021-01-12 14:42:54 UTC,This bug was fixed in the package python-apt - 2.1.7
1727470,2019-11-30 21:32:47 UTC,Any chance this could be improved? It is really frustrating that we have to manually translate this string every time before a new Ubuntu release.
1727470,2019-08-08 15:48:24 UTC,"Possible solution would be changing the ""Cdrom with"" part to something that can be used in most languages without a translation."
1727470,2019-08-08 15:32:37 UTC,"I see that the version strings are hardcoded in data/templates/Ubuntu.info.in, for example for Ubuntu 19.10:"
1727470,2019-06-19 09:48:31 UTC,Similar issue was just fixed in ubuntu-release-upgrader (https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1727472). It would be great if the issue could be fixed in python-apt as well.
1727470,2019-04-20 13:24:28 UTC,"I didn't have time to look into the source code, but the problem is that instead of having something like ""Cdrom with %s"", there is a new translatable string with hardcoded version added every time a python-apt is released for a new Ubuntu version. You could probably make the ""Ubuntu xx.yy 'Code Name'"" string not translatable (I don't think anyone actually translates this) and use it as a part of the ""Cdrom with ..."" string."
1727470,2019-04-18 11:08:38 UTC,Any news about this?
1727470,2019-12-11 15:23:32 UTC,I guess we could have two variables CODENAME and ??? and then you can say
1727472,2019-05-09 17:14:22 UTC,Would it be possible to triage that bug report as well?
1727472,2019-06-18 18:40:33 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.8
1727472,2019-05-15 20:58:18 UTC,Thoughts:
1727472,2019-06-19 09:45:04 UTC,"Great work, thanks! Would it be possible to also fix the similar issue in python-apt (see my comment #4 in this issue)?"
1727472,2019-04-20 13:12:24 UTC,"Well, I didn't have time to look into the source code, but the problem is that instead of having something like ""<b><big>Upgrading Ubuntu to version %s</big></b>"", there is a hardcoded version that is changed every time a ubuntu-release-upgrader is released for a new Ubuntu version."
1727472,2019-04-19 15:48:27 UTC,Is there an example of how to do this that you could point me at? Thanks!
1727472,2019-04-18 11:08:46 UTC,Any news about this?
1727472,2019-05-09 17:12:43 UTC,"Steve, python-apt has the same issue, see: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1727470"
1727476,2017-11-13 10:49:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727482,2017-10-28 04:24:32 UTC,Where can I take a look at the WTF cases you mention?
1727482,2018-12-09 08:05:49 UTC,"At least part of this was fixed by changing the bounce logging from error to warning, so Nagios is not tripped."
1727484,2017-11-13 23:24:45 UTC,Yeah these could be split. The resolution is probably to assume they made a typo.
1727484,2019-04-17 11:22:22 UTC,"I had a look into the code and it seems that this is fixed already (a PluginError message that differentiate between the three cases is present), or I didn't understand the issue :)"
1727487,2018-01-25 20:19:28 UTC,"Bill, I've folded all of this into the branch that will soon be posted on bug 1744385, as the contents here are required for that work.  How (if) would you like to dispose of this bug?"
1727487,2017-10-26 16:28:48 UTC,"Branch contains enough fields (and them some) to replace reporter.simple_record and MVR (minus ""online_loc"").  Will pause here pending feedback."
1727487,2017-10-25 20:57:22 UTC,Putting together a rough cut of the upgrade script now.
1727487,2017-10-25 22:10:12 UTC,Fleshing stuff out here:
1727496,2018-06-25 16:28:19 UTC,Or bug #1775641
1727496,2018-06-25 17:02:52 UTC,"I wonder if the core of this bug is in DistributionSourcePackage.ensure.  It checks ""spph.archive.purpose != ArchivePurpose.PRIMARY"", when perhaps it should check ""not spph.archive.is_main"" instead in order to handle the partner archive correctly?"
1727496,2018-06-25 17:10:35 UTC,"This also breaks loading the bug if you manually set the desired tasks using the API, because the web UI fails to initialise the edit form.  See OOPS-77eaec93a11f050a298861668799c1ed."
1727512,2017-10-25 20:28:57 UTC,"StacktraceTop:
 ?? () from /tmp/apport_sandbox_NTfPJk/usr/lib/python2.7/dist-packages/PyQt4/QtCore.x86_64-linux-gnu.so
 ?? () from /tmp/apport_sandbox_NTfPJk/usr/lib/python2.7/dist-packages/PyQt4/QtGui.x86_64-linux-gnu.so
 QObject::inherits (classname=0x7f53e71cfd86 ""QWorkspaceChild"", this=0x56008e9cefb0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:276
 QCleanlooksStyle::polish (this=<optimized out>, widget=widget@entry=0x56008e9cefb0) at styles/qcleanlooksstyle.cpp:3920
 QGtkStyle::polish (this=<optimized out>, widget=0x56008e9cefb0) at styles/qgtkstyle.cpp:374"
1727512,2017-11-23 13:13:40 UTC,more likely an issue with the qt4 bindings
1727515,2017-10-25 20:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1727515,2017-10-25 21:10:06 UTC,"$ apport-collect 1727515
ERROR: Could not import module, is a package upgrade in progress?  Error: No module named PyQt5.QtCore"
1727517,2017-10-25 20:40:48 UTC,We filter out control chars in the zionworx importer. Perhaps we could move it out to where the xml is saved.
1727517,2017-10-25 20:40:57 UTC,http://bazaar.launchpad.net/~openlp-core/openlp/trunk/view/head:/openlp/plugins/songs/lib/importers/zionworx.py#L33
1727518,2017-11-24 11:25:42 UTC,"This has been fixed by some (recent?) updates to Ubuntu 17.10. I can't unfortunately tell which one exactly, but the issue is gone."
1727528,2018-09-07 15:41:11 UTC,"Also, if you want the bug eventually fixed (I don't think there is a bug here, but I might be wrong), answering to the questions in: https://github.com/grpc/grpc/issues/11195 and provide step-by-step instruction about how to reproduce the issue will help me in fixing it."
1727528,2019-12-05 12:59:22 UTC,I made a small example to reproduce the bug with Bionic: https://github.com/MichaelGrupp/grpc_test_bionic
1727528,2018-09-05 18:18:06 UTC,hello? anyone?
1727528,2018-09-07 15:40:27 UTC,"1) artful is EOL and unsupported, please reopen and update information in case this is an issue with cosmic, bionic or xenial."
1727528,2017-10-25 22:16:24 UTC,We also want the fix in:
1727528,2017-10-25 21:50:30 UTC,"I generated this debdiff, hope it is helpful:"
1727528,2017-10-31 09:40:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727549,2017-10-25 23:56:03 UTC,"StacktraceTop:
 XRRGetCrtcInfo (dpy=0x55abb4a22c50, resources=resources@entry=0x55abb4bef330, crtc=719) at ../../src/XrrCrtc.c:54
 init_randr15 (changed=<synthetic pointer>, screen=0x55abb4a3a020) at ././gdk/x11/gdkscreen-x11.c:466
 init_multihead (screen=screen@entry=0x55abb4a3a020) at ././gdk/x11/gdkscreen-x11.c:840
 process_monitors_change (screen=0x55abb4a3a020) at ././gdk/x11/gdkscreen-x11.c:990
 read_settings (x11_screen=<optimized out>, do_notify=do_notify@entry=1) at ././gdk/x11/xsettings-client.c:509"
1727549,2018-03-05 16:04:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727550,2017-10-29 16:44:40 UTC,"Ok update if I try to open multiple *.cpp files (no headers) it opens them in multiple gvims, but if I select multiple *.pl's no such buggy behaviour"
1727550,2017-10-29 16:47:30 UTC,I've checked the gvim.destop  file and it clearly uses %F not %f also if it was that it would be consistent across file types
1727550,2017-10-26 09:31:27 UTC,the behaviour depends of gvim and of its .desktop entry
1727558,2017-11-15 01:10:34 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1727558,2017-10-28 05:48:49 UTC,"Reviewed:  https://review.openstack.org/515540
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fc10b54f25023d7e780b110928bda3a19e4c03f0
Submitter: Zuul
Branch:    stable/ocata"
1727558,2017-11-15 01:06:48 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1727558,2017-12-07 23:56:42 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1727558,2017-11-01 00:20:05 UTC,This issue was fixed in the openstack/nova 14.0.9 release.
1727558,2017-10-28 03:05:07 UTC,"Reviewed:  https://review.openstack.org/515538
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=60d6e87cac10ff1f95a028c6176e768214ec8b77
Submitter: Zuul
Branch:    stable/pike"
1727558,2017-10-26 22:35:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515538"
1727558,2017-10-27 08:21:28 UTC,"Reviewed:  https://review.openstack.org/514339
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=24e79bcbf7790d1f4fea2cbdf066599cc746c2dc
Submitter: Zuul
Branch:    master"
1727558,2017-10-26 22:53:23 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/515543"
1727558,2017-10-26 22:44:19 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/515540"
1727558,2017-10-26 00:29:57 UTC,Patch is here: https://review.openstack.org/#/c/514339
1727558,2017-10-28 03:01:20 UTC,"Reviewed:  https://review.openstack.org/515543
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ca03fe87371d8c13fc2895f8ff3e7e1ca88cfe79
Submitter: Zuul
Branch:    stable/newton"
1727578,2017-12-26 04:38:52 UTC,"zhaobo,"
1727578,2017-12-26 02:44:09 UTC,"Thanks, YAMAMOTO. Yeah, vpn traffic usually locates on the same router, but the diagram show that we config some routes into the default router, then forwarding the specific traffic which want to access the specific cidr to the router which vpn service locates on. Does it not work for your opinion? hmmm, I have never test it, as the our product deployed like that. So..."
1727578,2017-12-26 07:53:24 UTC,"Thanks, YAMAMOTO.
I know your point and follow up, sorry. My intent is trying to limit the vpn traffic bandwidth, as the underlay network which the vpn locates on is not free. So I think we could focus on the Router's ports"
1727578,2018-04-27 22:45:07 UTC,"Reviewed:  https://review.openstack.org/531074
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=cc8b3ec9eeb2f76c5fd4f6cc8ec5f480fabee098
Submitter: Zuul
Branch:    master"
1727578,2018-01-05 14:59:29 UTC,This RFE was approved in today's drivers meeting. Let's continue the conversation in the spec
1727578,2018-01-31 02:20:03 UTC,"Wow, Thanks very much, Miguel. I just saw your latest comment. Sorry for late reply. I will focus on the spec. Thanks again."
1727578,2017-12-22 07:54:02 UTC,"i guess vpn traffic usually goes through the internet.  thus it often traverses the same neutron routers and ports as the ordinary traffic to/from the internet.
my understanding is that you want to shape only vpn traffic, right?"
1727578,2018-01-04 05:12:59 UTC,"Hi all,"
1727578,2017-12-21 02:10:06 UTC,"Hi Slawek,"
1727578,2017-12-11 09:43:54 UTC,"Oh, it's break. Please see
http://paste.openstack.org/show/628591/"
1727578,2017-12-15 03:50:40 UTC,"Hi, YAMAMOTO. I answer below:"
1727578,2017-12-06 06:56:49 UTC,"your main interest is outgoing traffic shaping, right?
what's ServiceConnection?  an equivalent of ipsec site connection?
the feature request sounds reasonable to me.
do you have an implementation idea for the reference implementations?"
1727578,2017-12-07 03:44:59 UTC,"Thanks YAMAMOTO,
Yeah, just outgoing traffic."
1727578,2017-12-08 09:52:57 UTC,what's 10.0.0.1 and 10.0.0.3 in your example?
1727578,2017-12-20 20:43:14 UTC,"Hi,"
1727578,2017-12-11 09:43:03 UTC,"                                     +-------------------+      External network
                                     |    Router         +------Internet
                                     |                   |
                                     |10.0.0.1           |
                             +-------+                   |
                             |       |                   |
                             |       |                   |
                             |       |                   |
                             |       +-------------------+
                             |
+-----------------------+    |

| VM A                  |    |
| VNIC IP: 10.0.0.4     +----+
| default via 10.0.0.1  |    |
| 10.20.0.0 via 10.0.0.3|    |
|                       |    |
|                       |    |
|                       |    |       +------------------------+


+-----------------------+    |       |     Router             |
                             |       |                        |
                             |       |                        |
                             |       |10.0.0.3                |      Internal network of
                             +-------+    RUNNING A           +------some companies
                                     |    VPN TO ACCESS       |      the deployed/planed
                                     |    INTERNAL ZONE       |      network is 10.20.0.0/24
                                     |                        |
                                     |                        |
                                     |                        |
                                     +------------------------+"
1727578,2017-12-14 10:01:12 UTC,what's 10.0.0.33?
1727578,2017-12-11 09:35:30 UTC,10.0.0.1 is the default gw for the vm port. 10.0.0.3 is the nexthop for the traffic which want to access 10.20.0.0 which is the other vpn site cidr.
1727590,2018-11-06 19:48:06 UTC,Updated the linked merge proposal.
1727590,2018-11-06 18:47:13 UTC,"> Perhaps we should always build for Ubuntu unless overridden.
"
1727590,2018-11-06 18:38:01 UTC,"I suspect that Steve found this either
a.) before the change landed making 'unstable' build on ubuntu
b.) by trying to build something with 'experimental'."
1727590,2018-11-06 16:15:41 UTC,"> We use HEAD's debian/changelog to figure out what we're building for...
"
1727590,2017-10-26 18:42:16 UTC,"On Thu, Oct 26, 2017 at 10:54 AM, Steve Langasek
<email address hidden> wrote:

> On Thu, Oct 26, 2017 at 03:01:39PM -0000, Nish Aravamudan wrote:
>> On Thu, Oct 26, 2017 at 7:24 AM, Steve Langasek
>> <email address hidden> wrote:
>> > On Thu, Oct 26, 2017 at 11:53:48AM -0000, Robie Basak wrote:
>> >> Oh. Or are you telling me it's wrong to use a *Debian* container as
>> >> opposed to an Ubuntu one, rather than any container at all? In that case
>> >> that sounds valid.
>
>> > (I have also opined that the default should be to not run the clean target
>> > for building the source package, but I understand why you disagree)
>
>> At what point did you run `git ubuntu build-source`? Was it after `git
>> ubuntu merge finish` or after the rebase onto new/debian?
>
> Following the documentation at
> <https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow#Git_workflow_for_merging>,
> I ran it after the 'git rebase new/debian' step.
"
1727590,2017-10-26 11:53:48 UTC,"Oh. Or are you telling me it's wrong to use a *Debian* container as opposed to an Ubuntu one, rather than any container at all? In that case that sounds valid."
1727590,2017-10-26 15:01:39 UTC,"Hello Steve,"
1727590,2017-10-26 14:24:25 UTC,"On Thu, Oct 26, 2017 at 11:53:48AM -0000, Robie Basak wrote:

> Oh. Or are you telling me it's wrong to use a *Debian* container as
> opposed to an Ubuntu one, rather than any container at all? In that case
> that sounds valid.
"
1727590,2019-09-29 04:12:26 UTC,Looks like the fix for this bug landed in master:
1727590,2017-10-26 11:52:50 UTC,"Technically I believe that to build a source package, you need to install build dependencies and run the clean target first (which may depend on build dependencies). This may for example produce a control from a control.in, or similar, via a build dependency. That's why we're doing this in a container by default."
1727590,2017-10-26 17:54:23 UTC,"On Thu, Oct 26, 2017 at 03:01:39PM -0000, Nish Aravamudan wrote:

> On Thu, Oct 26, 2017 at 7:24 AM, Steve Langasek
> <email address hidden> wrote:
> > On Thu, Oct 26, 2017 at 11:53:48AM -0000, Robie Basak wrote:
> >> Oh. Or are you telling me it's wrong to use a *Debian* container as
> >> opposed to an Ubuntu one, rather than any container at all? In that case
> >> that sounds valid.
"
1727593,2017-11-03 23:35:31 UTC,"Also, an FYI, I just found a corner-case bug in the edge snap (and
fixed it) for the merge finish step that was breaking our changelog
reconstruction."
1727593,2017-10-26 15:11:46 UTC,"On Wed, Oct 25, 2017 at 8:57 PM, Steve Langasek
<email address hidden> wrote:

> Public bug reported:
>
> https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow#Git_workflow_for_merging
> documents that one of the steps for 'git ubuntu merge finish' is 'git
> reconstruct-changelog new/debian'.  I'm unable to find where this
> command is supposed to come from (both 'git reconstruct-changelog' and
> 'git ubuntu reconstruct-changelog' are unknown here),
"
1727593,2017-10-26 06:01:48 UTC,"Hi Steve,
I just yesterday - hours before your bug - changed the wiki wording slightly."
1727593,2017-10-26 14:23:21 UTC,"On Thu, Oct 26, 2017 at 06:01:48AM -0000, ChristianEhrhardt wrote:

> Hi Steve,
> I just yesterday - hours before your bug - changed the wiki wording slightly.
"
1727596,2017-10-26 15:16:03 UTC,The -v issue is known and fixed in LP: #1721247.
1727596,2017-10-26 17:36:59 UTC,"On Thu, Oct 26, 2017 at 03:16:03PM -0000, Nish Aravamudan wrote:

> The -v issue is known and fixed in LP: #1721247.
"
1727596,2017-10-26 18:39:11 UTC,"On Thu, Oct 26, 2017 at 10:36 AM, Steve Langasek
<email address hidden> wrote:

> On Thu, Oct 26, 2017 at 03:16:03PM -0000, Nish Aravamudan wrote:
>> The -v issue is known and fixed in LP: #1721247.
>
>> The -sa option should be working properly, though and that's
>> surprising. Which version of the snap was this found with? If stable,
>> can you try edge?
>
> This is the stable snap.  I wouldn't normally want to track ""edge"" given the
> usual definition of ""edge"" as ""built from commit, untested"".  Would
> candidate be a reasonable channel to track to keep me fairly current?
"
1727596,2017-11-03 20:13:49 UTC,"I think the edge snap as of today should have the fix for the -sa issue, if you could test it."
1727596,2020-04-09 04:17:23 UTC,[Expired for usd-importer because there has been no activity for 60 days.]
1727625,2017-10-26 07:12:51 UTC,"StacktraceTop:
 ?? ()
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x56, hash_table=0x564d3af00320) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x564d3af00320, key=key@entry=0x56) at ../../../../glib/ghash.c:1153
 lookup_cached_xatom (atom=0x56, display=0x564d3af18000) at ././gdk/x11/gdkproperty-x11.c:76
 gdk_x11_atom_to_xatom_for_display (display=0x564d3af18000, atom=0x56) at ././gdk/x11/gdkproperty-x11.c:109"
1727628,2017-10-30 14:17:08 UTC,3.17.7 and 3.17.9 plugins are uploaded to OpenPrinting. We would be fixing the fall back HP link issue at the earliest
1727628,2017-10-30 12:39:21 UTC,"Good job, Till. Now only fixing fallback HP link remains (if plugins will be only on openprinting.org, then it will be impossible to download plugin if openprinting.org will be unaccessible)."
1727628,2017-10-30 14:30:55 UTC,Thank you Shivani.
1727628,2017-10-30 11:57:53 UTC,I got the files now and uploaded them to OpenPrinting. Now everything should return to work.
1727628,2017-11-08 07:14:39 UTC,"Till,"
1727628,2017-11-17 15:37:12 UTC,"Hi,
The PLUGIN_FALLBACK_LOCATION variable will be updated with the new hplip portal link which has the plugin files needed for installation and this change will be available as part of the 3.17.11 release before end of November."
1727628,2017-11-07 17:42:02 UTC,Can someone from HP tell to what this PLUGIN_FALLBACK_LOCATION needs to be set in order to fix alreay released HPLIP versions (and where in HPLIP to fix it)?
1727628,2017-10-30 11:19:04 UTC,"3.17.7 and 3.17.9 plugins worked before introducing new website even if they weren't uploaded to openprinting.org, because they were downloadable from fallback HP link."
1727628,2017-10-30 09:28:55 UTC,"Till,"
1727628,2017-10-29 19:21:26 UTC,"Ah ok, thank you!"
1727628,2017-10-29 18:39:52 UTC,A far as it looks for me the problem is not HP's site change. With every HPLIP release I (as the maintainer of the OpenPrinting web site) get the plugin e-mailed from a person of the HPLIP team and upload it to the appropriate place on the OpenPrinting web server. I checked and I actually got plugins for 3.17.6 and 3.17.10 (which I both have uploaded) but not for 3.17.7 and 3.17.9.
1727628,2017-10-29 18:16:04 UTC,"I agree with many of these people there is something wrong with the software, I have an old HP 1018 Laserjet that won't work either, have no idea why, but the only thing I can figure is that the driver was never installed on this OS.
It seems they somehow missed it, or forgot to load it because you can understand the newer versions of printers not having drivers, but the old ones, well that should be a no brainier i.e. included, but it's not there not even in the repository.
Somebody please explain that!  Very disappointing especially to those who went ahead and donated to this project."
1727628,2017-10-29 10:08:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727628,2017-10-26 16:35:58 UTC,"I am facing the same problem: I've updated to 17.10 and hplip complained about needing to download the plugin, yet it's unable to find any and I cannot find one manually either."
1727628,2017-10-26 08:09:28 UTC,"After more digging into it, I found out plugins disappeared for hplip-3.17.7 and hplip-3.17.9 (from 3.17 series, maybe some older releases may be missing too), which don't have plugins on openprinting.org. Can you please post these plugins on openprinting.org page too?"
1727628,2017-10-26 07:31:34 UTC,"It crashes installation of every printer, which needs proprietary plugin, which isn't on openprinting.org site - that means everyone, who has hplip-3.17.6+."
1727639,2017-10-26 08:20:29 UTC,We have had conversation about exposing errors in a more obvious way. Thank you for filing a bug \o/
1727639,2017-10-26 10:30:17 UTC,"You can do:
  juju status error"
1727639,2017-10-26 11:21:10 UTC,"Aha, that is exactly what I'm looking for."
1727639,2017-10-26 12:47:22 UTC,"As per comments above, we should update command help for clarity."
1727643,2018-02-15 23:53:49 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1727643,2017-12-15 02:50:42 UTC,"Reviewed:  https://review.openstack.org/517727
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7687dadccff52c9354033137e4f5ebdeb79b2424
Submitter: Zuul
Branch:    stable/pike"
1727643,2017-12-07 23:56:40 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1727643,2017-11-03 21:30:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/517727"
1727643,2017-11-02 20:45:50 UTC,"Reviewed:  https://review.openstack.org/511459
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=13418faa17e1034db551c8d193a7b08e8b59ef9d
Submitter: Zuul
Branch:    master"
1727643,2017-10-27 01:27:26 UTC,Set the status to In-progress because this report has an assignee and there is a patch for it.
1727643,2017-10-26 08:28:59 UTC,Fixed by:
1727653,2018-01-24 11:21:59 UTC,@Kenneth: The -v limit was suggested in comment #19.
1727653,2018-01-24 11:58:03 UTC,That does explain why you can't open more gpg threads.  Each instance of gpg will take several file handles and eats more resources.
1727653,2018-01-26 10:59:07 UTC,I cannot confirm that ulimit -s 16384 will heal the issue (suggested in #30). I have inserted ulimit -s 16384 to no avail.
1727653,2018-01-26 13:42:16 UTC,"On 26 January 2018 at 11:59, Wolf Rogner wrote:

> I cannot confirm that ulimit -s 16384 will heal the issue (suggested in
> #30). I have inserted ulimit -s 16384 to no avail.
>
> Exec=sh -c ""ulimit -v 1000000; ulimit -s 16384; ulimit -n 4096; exec
> /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor""
"
1727653,2018-01-28 10:07:14 UTC,"Sorry for the delay, I wanted to make sure my answer is accurate."
1727653,2018-01-28 10:36:17 UTC,"It's probably the -n option (number of open files).  The default is 1024
and that's way too low."
1727653,2018-01-28 11:51:47 UTC,Just adding -n 4096 or -s 16384 alone or in combination does not do the trick.
1727653,2018-01-31 14:59:06 UTC,This seems to be a regression introduced by a fix for bug #1302416.
1727653,2018-01-31 15:25:38 UTC,"Please upgrade to the current version of duplicity, 0.7.16.  This will assure that any bugs fixed since your release are available and may fix your issue.  This applies especially to duplicity versions between 0.7.03 and 0.7.14 inclusive.  There was a fix in 0.7.15 that reduced memory usage drastically, and will help with memory errors and inability to start new threads."
1727653,2018-02-11 18:34:36 UTC,I'd also be curious if this is because of duplicity <0.7.16 or because of the ulimit line we use for deja-dup-monitor. It's not clear to me if I should change the ulimit line or if we just need to update duplicity for those users affected.
1727653,2018-02-11 21:48:49 UTC,"I would bet the update will fix it.  Huge manifests go into memory, in
bulk, and in lists.  The lists stay around and if Python GC is not working
properly, the bulk reads do as well.  During processing, there were as many
as 3 copies of the manifest in memory, one bulk, one the result of re
iteration, and the other in the collection list.  That kind of misuse can
really screw up GC."
1727653,2018-02-26 20:20:00 UTC,"I think this is fixed in the latest releases, however, the OPs are not responding and I have no test case to run against.  Marking this incomplete until someone can confirm that it does not work on 0.7.17 and later."
1727653,2018-03-15 11:59:10 UTC,A few more requests then:
1727653,2018-03-07 11:09:33 UTC,Try upping your ulimit on num files from 1024 to 8192 or higher.
1727653,2018-03-30 11:56:56 UTC,From the permissions error message it looks like you tried to run that as yourself.  Try going into root and running the commands again.
1727653,2018-03-12 02:03:45 UTC,I'm unable to increase the ulimit on my system. I've added the new size in limits.conf but that does not help. Running the command manually gives me a permissions error with files open. At this point the upgrade to 0.7.17 did not help so it appears something else need to be look at.
1727653,2018-03-13 15:10:13 UTC,It's odd you would get an error on 'ulimit -n 8192'.
1727653,2018-03-13 17:18:27 UTC,"~$ ulimit -n 8192
bash: ulimit: open files: cannot modify limit: Operation not permitted"
1727653,2018-03-13 20:53:17 UTC,See this: https://superuser.com/a/1200818
1727653,2018-03-15 01:32:31 UTC,I was able to get the open files changed to 65535 using the above link. Today after I started my computer I got the same error I've been getting about not being able to create a new thread.
1727653,2018-01-24 10:58:40 UTC,"Thanks for catching that.  Was the system installed with those limits, or
had you put them in earlier?  I've never seen a distro that tried to limit
virtual memory."
1727653,2018-03-16 03:51:51 UTC,">A few more requests then:
"
1727653,2018-03-16 18:25:49 UTC,Try this then:
1727653,2018-03-17 14:45:32 UTC,Try running the command as:
1727653,2018-03-18 17:39:39 UTC,">Try this then:
"
1727653,2018-03-07 03:06:38 UTC,I'm also seeing this issue and I just purged Duplicity and then added it back with the PPA and I am still seeing the issue. I am using 0.7.17 now. What information can I provide to help fix this?
1727653,2018-01-24 06:40:33 UTC,"So, I have been experimenting. I have removed ulimit -v 100...0 out of the command line because I have unlimited limit by default. What I have added though is ulimit -s 16384 which doubles stack limit and I have also ulimit -n 2048 to double file limit. Todays backup passed without the usual exception."
1727653,2017-11-03 07:39:57 UTC,Tested 0.7.14-bzr1335-0ubuntu3-ubuntu17.10.1 and it produces the following error:
1727653,2018-01-22 17:01:35 UTC,"@Kenneth: The call stack is clearly different. Also, it does not explain the hanging threads in Duplicity and processes of GPG waiting on pipe write to return. Also, I have been running the PPA version last few months."
1727653,2018-01-23 12:40:49 UTC,"Whoops!  You are correct.  I thought you were on 0.7.10 from a previous
message."
1727653,2017-10-28 09:19:07 UTC,"I doubt this being a duplicate:
The error message differs and it only happens when deja-dup starts automatically.
When launched manually, deja-dup and duplicity work fine."
1727653,2017-10-28 10:59:42 UTC,"The first launch after a reboot is one where the memory is less fragmented, and possibly where other tasks have not started, so clean memory access is most likely.  The current manifest file reader takes in the full file at one time and breaks it apart in memory.  This worked well when there was only volume information present, but the addition of the file-changed list made this operation much more memory intensive (added in 0.7.03).  Forking a gpg task takes a good bit of memory and the error message sounds generic, so I'm inclined to lean towards memory issues."
1727653,2017-10-28 18:10:50 UTC,Please read my comment again:
1727653,2017-10-28 19:03:51 UTC,"How many open files allowed (""ulimit -n"")?  Other than memory, ""too many
open files"" has been the culprit that keeps fork from working."
1727653,2017-10-28 22:11:27 UTC,ulimit -n -> 1024 (default install)
1727653,2017-10-31 11:54:57 UTC,"You probably want to increase that.  It's an extremely low limit.  Search for ""ubuntu increase max files limit"" and you will find answers.  Don't be miserly, set it at 32K or 64K."
1727653,2017-10-31 17:26:04 UTC,"If you could, please test the latest bzr trunk version.  I just fixed a major bug that was chewing up a lot of memory.  That may help with this problem if the fix above does not work."
1727653,2017-10-31 20:52:30 UTC,Re #8: Is there a PPA for that?
1727653,2017-11-03 05:40:07 UTC,I have tested with 0.7.14+bzr1335-0ubuntu3~ubuntu17.10.1 and it still fails the same.
1727653,2017-11-03 12:11:31 UTC,"0.7.15 is coming out soon, .16 down the road.  .15 preview is in the daily builds."
1727653,2017-11-04 12:46:36 UTC,I have bumped the file limit to 8k from 4k for last night's backup and still got the same error.
1727653,2017-11-01 11:42:27 UTC,"Daily duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/daily"
1727653,2017-11-05 10:29:11 UTC,@Kenneth:
1727653,2018-01-22 07:18:25 UTC,Debugging the Python process of Duplicity shows no polling or reading from appropriate number of pipes:
1727653,2018-01-21 22:37:24 UTC,"So I have several (over 5) processes in the previously mentioned state: Duplicity with a dozen or so gpg processes under it, hanging, duplicity is being run as `usr/bin/duplicity restore`."
1727653,2018-01-18 16:29:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727653,2018-01-22 11:10:16 UTC,I think this is a duplicate of https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1730451 and that you've just run out of memory for a new thread.  Please upgrade to the newest version and try again.
1727653,2017-12-22 12:22:48 UTC,Deja-Dup and duplicity seemed to work with kernel 4.13.0-19. After that (21 and 22) the issue reappeared.
1727653,2018-01-12 17:54:41 UTC,@Kenneth #17:
1727653,2017-11-09 19:54:45 UTC,"This will work when duplicity is run from DejaDup, not when it is run from the console or from cron."
1727653,2017-11-08 06:52:06 UTC,The backup completed succesfully (while running automatically) after I changed in /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop from
1727653,2017-11-04 16:12:48 UTC,"Do you have a passphrase on the backup?  I don't see any key use, and it
looks like gpg-agent is turned off."
1727653,2017-11-07 12:19:53 UTC,From /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop (and https://git.launchpad.net/deja-dup/tree/data/org.gnome.DejaDup.Monitor.desktop.in):
1727653,2017-11-05 11:42:08 UTC,"ulimit is settable system wide, so, at the end of /etc/security/limits.conf
add the lines:"
1727653,2017-12-06 08:33:19 UTC,"Hello,"
1727658,2017-10-27 15:46:59 UTC,"What could be interesting is an option for Inkscape to have a ""shared"" INKSCAPE_DATADIR (i.e. share/inkscape) that can be placed on a network drive or similar which can be updated with additional working files (similarly to what is already possible with the inkscape folder in the user configuration directory)."
1727658,2017-10-27 09:56:37 UTC,Spot on.
1727658,2017-10-27 09:29:32 UTC,your symbols file to each pc symbols file > your symbols file to each pc symbols folder
1727658,2017-10-27 09:29:02 UTC,To it you need to copy your symbols file to each pc symbols file and restart inkscape. Is important document has title if not it not show in the dropdown.
1727658,2020-09-14 09:28:03 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1727658,2017-10-27 08:04:52 UTC,Hi Jan:
1727658,2017-10-27 08:36:01 UTC,Hej Jabiertxof
1727658,2017-10-27 07:22:17 UTC,This is a bit over my skills at the moment.
1727658,2017-10-26 10:39:53 UTC,"Shapes are here meant to be Symbols.
Sorry."
1727658,2017-10-26 16:46:45 UTC,"like symbol libraries ? See for instance https://github.com/Xaviju/inkscape-open-symbols (and the ""how to install"" section)"
1727664,2017-10-26 09:22:19 UTC,"As a collateral issue, swift-proxy/0 juju unit stopped swift-proxy service. Such unit had the VIP."
1727664,2019-04-02 14:04:04 UTC,"As this is over a year old, and lots of changes have been made, I'm setting to incomplete to see if it's still an issue.  If not, then it will expire."
1727664,2019-06-02 04:17:30 UTC,[Expired for OpenStack swift-proxy charm because there has been no activity for 60 days.]
1727679,2017-11-19 12:50:38 UTC,"So the quick summary (IIRC), is that we had a transaction which had been flagged as ""prepared"", but didn't actually have an entry in the txn-queue for every document that was referenced by the transaction.
Note that some of the changes to mgo that should be in 2.3 will at least prevent this from growing inordinately large (as txns that would cause a queue to grow >1000 long should end up immediately flagged as aborted.)"
1727679,2017-10-27 07:07:21 UTC,"This got worked around by applying this change :
db.txns.update({_id: ObjectId(""59ef3f595f5ce87b42d1e774"")}, {$unset: {""n"": 1}, $set: {""s"": 1}})"
1727679,2017-10-27 10:23:02 UTC,"That query moves the TXN from prepared (all docs should be ready to apply)
to preparing (create what needs to exist)."
1727686,2017-10-26 17:34:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727687,2017-10-26 23:06:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1727687,2017-12-10 10:46:57 UTC,Possibly duplicate of bug 1487679.
1727687,2017-12-10 16:12:49 UTC,Today my system boot offline again:
1727687,2017-12-18 14:31:14 UTC,"Today my system booted offline again.
With the same symptoms. Where should I find help?"
1727687,2017-12-23 19:36:09 UTC,"Today my system booted offline again.
With the same symptoms. Where should I find help?"
1727687,2017-12-24 12:36:26 UTC,Situation repeated yesterday and today. I purged network-manager and set up eth0 as DHCP in /etc/network/interfaces.
1727690,2018-03-09 02:23:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727692,2017-10-27 10:52:13 UTC,"Well, I gave a ppa-purge on the remmina team ppa and downgraded all freerdp files needed for remmina-rdp plugin and the problem was solved."
1727709,2017-10-26 12:27:07 UTC,"Note that this only works if ""foo"" isn't a known config, otherwise when we validate the config, we notice that it isn't valid.
The issue only happens with ""pass-through"" config values, which we usually warn on. We only accept them in case it used to be a valid value (so after upgrade, we don't fail because you used to set an item that we know ignore).
Anyway, things that aren't simple types haven't ever been valid, so we could just stript them all and refuse them."
1727709,2018-07-13 05:36:29 UTC,"@Richard Harding, John A Meinel,"
1727716,2017-11-03 13:53:26 UTC,The upstream bug appears to have be written already.
1727716,2018-01-12 01:31:25 UTC,"^^^
The above fix is scheduled for release upstream in the next preview release of gnome-shell 3.27 (3.27.2?). It doesn't appear to be backported to 3.26 but that would appear unlikely (I am guessing) due to the large number of patches involved."
1727716,2017-10-26 15:12:39 UTC,This does not appear to be a security vulnerability so I am unmarking it as Public Security.
1727716,2017-10-26 15:06:38 UTC,"This seems to be a Wayland issue. Sticky keys works for me if I log in to an ""Ubuntu on Xorg"" session, but not if I log in to ""Ubuntu""."
1727716,2017-11-03 12:28:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1727719,2017-11-01 07:55:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/516880"
1727719,2017-12-05 11:31:27 UTC,"Reviewed:  https://review.openstack.org/516880
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5de3317d68df8fdc6fdaff62baa62822c669bb93
Submitter: Zuul
Branch:    master"
1727719,2017-12-05 14:17:15 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/525620"
1727719,2017-12-07 23:55:38 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1727719,2017-12-12 21:39:44 UTC,"Reviewed:  https://review.openstack.org/525620
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fc225f16a12471bfde9d5d0d378e69fba201e58a
Submitter: Zuul
Branch:    stable/pike"
1727719,2017-12-18 12:51:23 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1727721,2019-09-19 14:46:23 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1727721,2018-07-02 08:41:38 UTC,"It appears this requires websocket support for probe and enlist before it can be moved to maas-obj-form, currently only supported via the API."
1727723,2018-09-27 09:27:06 UTC,And now? Almost 1 year later?
1727723,2020-03-15 20:21:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727723,2020-03-23 11:20:03 UTC,3.3.0 is now in focal (Ubuntu 20.04).
1727723,2020-03-23 12:16:34 UTC,Thank you!
1727723,2020-03-23 17:40:14 UTC,"I backported it for you in my PPA:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers"
1727723,2020-03-23 17:54:13 UTC,"Thank you :)
But minimizing the amount of 3rd party repos was my aim for this bug report :D"
1727731,2017-10-26 13:38:25 UTC,This is fixed in debian with:
1727731,2017-10-26 13:27:02 UTC,Screenshot attached
1727746,2018-01-20 08:05:27 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1477
1727746,2018-01-15 11:45:14 UTC,"Hello,
   To understand the problem in detail can you please send the xtrabackup version, the exact xtrabackup command and the xtrabackup backup log that is generated when the backup is ongoing. I dnot think that this could be a bug. Also checked the bugs database but could not find anything related. We can try to reproduce it though if you send the requested information and confirm if it exists."
1727746,2018-01-15 12:07:41 UTC,"Version used: innobackupex version 2.4.8 Linux (x86_64) (revision id: 97330f7)
Full command: innobackupex -u<user> -p —include='^<db_name>\.' backupex/"
1727747,2017-10-29 11:17:44 UTC,"> I might be able to adopt this. Can you give a few pointers where in the code I should focus my attention?
"
1727747,2017-10-31 17:01:02 UTC,Here is the detailed behavior I have in mind.
1727747,2017-10-31 18:22:01 UTC,"3B might be hard to understand, because we have to track, what was the reason for track #1 to be on top. This might be forgotten by the user after a while so the behaviour may feel like a bug."
1727747,2017-11-02 21:13:59 UTC,"Is there a working Visual Studio project I can use? I got a working build, but I'm hoping I can properly use an IDE for windows development."
1727747,2017-11-02 21:52:30 UTC,I am afraid not. I am on Linux using Eclipse but maybe someone else can give hints for VS.
1727747,2017-11-04 10:53:04 UTC,I'm on windows and use atom.
1727751,2018-08-29 20:18:38 UTC,"As nobuto notes, the man page says ""list of all supported stable versions""; so either the functionality or the man page needs to be updated."
1727751,2018-06-27 16:49:51 UTC,"Yes, that totally depends on the definition of the option ""--supported list of all supported stable versions"". I was confused initially, but if that's by design, we don't need to change the behavior. Sorry for the noise."
1727751,2018-06-27 16:27:49 UTC,"How is the development release of Ubuntu unsupported? It is still a supported release of Ubuntu, we work to fix bugs on it, although it may not be a stable one."
1727751,2018-06-27 08:20:07 UTC,"The attachment ""date_x_release.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1727751,2018-06-26 16:31:29 UTC,"The information actually comes from the distro-info-data package, not distro-info. What version of distro-info-data do you have installed?"
1727751,2018-06-27 04:59:27 UTC,I didn't mean that way. Let me set it back to ditro-info package and update the title and description.
1727751,2018-06-26 16:32:42 UTC,"Oh, I didn't notice how old this - it predates the SRU of distro-info-data to Artful so I'm going to set this to Fix Released."
1727751,2018-06-23 01:44:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727751,2018-06-27 05:40:17 UTC,"I think we need a condition ""date >= x.release"" like an attached diff (it's only for python though)."
1727754,2019-09-19 14:49:33 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1727756,2017-10-26 15:19:12 UTC,"patch is tracked here.
https://review.openstack.org/#/c/515444/"
1727758,2017-10-27 13:18:28 UTC,same with Qt Creator
1727758,2017-10-27 13:18:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727758,2017-10-27 15:01:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1727771,2018-07-08 08:47:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727771,2019-01-11 16:17:09 UTC,"Hello,"
1727771,2020-04-15 19:47:08 UTC,Any news?
1727771,2020-04-25 21:44:53 UTC,"This bug means lost work, so it's a bit puzzling that it hasn't received any attention."
1727771,2020-04-25 21:45:31 UTC,"BTW, it keeps on happening in 18.04."
1727787,2017-10-26 19:48:33 UTC,the fix is being discussed in
1727787,2017-10-26 19:49:03 UTC,Also moving it to snapcraft ...
1727787,2017-11-01 22:56:40 UTC,"According to the forum thread, this is due to running a classic snap on a non-Xenial release. The various solutions in the pipeline are discussed in that thread. Marking as triaged. This is also high priority."
1727793,2018-01-29 04:47:51 UTC,Thanks D Haas (uz6945) and Alvaro Aleman (alvaroaleman) for reporting. I will work on a fix for this.
1727793,2017-11-29 20:52:30 UTC,"Repro for centos 7.4 attached. Happens when following the doc at https://docs.openstack.org/kolla-kubernetes/latest/deployment-guide.html, Version: ""UPDATED: 2017-11-20 17:38"""
1727793,2017-11-24 12:29:00 UTC,Can reproduce this. With a fresh Ubuntu 16.04 /etc/hosts.
1727793,2017-11-24 12:01:01 UTC,"dangtrinhnt (OP) has documented this on his blog
(http://www.dangtrinh.com/2017/10/openstack-kolla-ansible-prechecks-error.html)"
1727793,2018-01-29 04:17:29 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1727793,2017-10-27 07:18:04 UTC,"Hi,"
1727793,2017-10-27 06:59:18 UTC,"Marked as incomplete, please add more information to try understand your issue."
1727793,2017-10-27 06:58:31 UTC,"Hi, api_interface is defined in group_vars/all too. This means if you don't specify the var in globals will always use default value in group_vars."
1727793,2017-11-22 18:55:35 UTC,"Kindly post full error that you are getting and try executing like:
kolla-ansible prechecks -vi <inventory file>"
1727795,2020-01-30 18:15:06 UTC,"Marcin, anything to do here specifically or can we close? :-)"
1727800,2017-10-26 19:31:15 UTC,I'm just curious is os-testr installed in the same python environment as stestr 1.1.0? There was a bug in stestr where the whitelist argument was being ignored which should be fixed in stestr 1.1.0. We do a straight copy of the whitelist file argument to stestr's run command:
1727800,2017-10-27 14:02:42 UTC,"yes it is, the versions are:
os-testr==1.0.0
stestr==1.1.0"
1727800,2018-03-05 20:22:01 UTC,We were able to get around issues with blacklists and whitelists by downgrading to 0.8.2
1727804,2017-10-26 23:39:32 UTC,Please note that your logs are filled with messages that look related to hardware failure; this machine looks unhappy.
1727804,2018-08-18 23:01:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727811,2017-10-28 13:23:05 UTC,This bug was fixed in the package signon-ui - 0.17+18.04.20171027+really20160406-0ubuntu1
1727816,2017-10-27 12:40:04 UTC,"Steve,"
1727816,2017-10-27 11:58:42 UTC,"TJ,"
1727816,2017-10-26 20:18:48 UTC,This is most likely a bug in the kernel.  What video driver is used for your virtualbox environment?
1727816,2017-10-27 04:51:28 UTC,"Steve, et alia:"
1727816,2017-10-26 19:48:17 UTC,The initial reports (in #ubuntu) suggest this may be an issue with plymouth
1727816,2017-10-26 19:51:01 UTC,I suspect this is the Critical bug https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1386005
1727816,2017-10-26 19:45:18 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1727824,2017-10-30 17:37:27 UTC,I think this is caused by the containers not coming up with consistent network interface naming;  the first hacluster unit appears to be trying to configure resources the other way around to the other two units
1727824,2017-11-03 07:56:31 UTC,"Reading the reference docs for the heartbeat resources we use for VIP, we can actually not configure the resources with nic and netmask - heartbeat will try to figure this out itself when the resource is promoted on a unit."
1727824,2017-11-03 08:08:22 UTC,"There is complexity here as the pacemaker resources have the interface name encoded into them; so we also need to re-jig the resource naming, which for and existing cluster would mean deleting the existing VIP resources, and then re-creating them with the new names (which is disruption to service)."
1727824,2017-11-03 08:09:48 UTC,"If we used a short hash of the VIP being configured in its name, than that would also deal with the requirement to floating IPv4 and IPv6 VIP's on the same network interfaces."
1727824,2017-11-03 08:30:39 UTC,Could we allow a new value for vip_iface of 'auto'. If set to auto then the iface is not longer passed on the ha interface and pacemaker is left to figure out the correct interface. I iface is set to an interface or is empty the old behaviour is preserved.
1727824,2017-11-03 08:32:28 UTC,Actually maybe the magic value should be 'crm_auto' to show that the interface calculation is being done outside of the charm.
1727824,2019-01-11 12:05:14 UTC,"Change abandoned by James Page (<email address hidden>) on branch: master
Review: https://review.openstack.org/531359"
1727828,2017-11-13 23:53:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727845,2018-06-14 14:29:29 UTC,"Occured when a live migration didn't finish.
The neutron ports stuck in migraging_to state.
Nova reports wrong host for the instance."
1727845,2020-11-22 04:17:25 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1727845,2020-09-22 10:39:45 UTC,"I know that this is an old bug. Between the ""Post operation of migration started"" LOG and the code that removes the migrating_to state of the port in neutron there is not much things only neutron API is queried from nova. So If the problem is still reproducible then I would suggest to look at the neutron logs and check for intermittent network failures between the compute host and the neutron APIs."
1727848,2017-10-27 21:21:43 UTC,"Thanks for reporting. I've added a bug watch (the ""also affects distribution/package"" link above the description), so that this bug will be notified when the status of the Debian bug changes."
1727850,2017-10-26 20:10:49 UTC,boot-smoke test fails:
1727850,2017-10-26 20:13:02 UTC,From journal.txt in the adt artifacts:
1727850,2017-10-26 20:14:04 UTC,When I run the systemd tests locally using autopkgtest I cannot reproduce this failure.
1727855,2018-02-15 23:53:59 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1727855,2018-04-20 05:22:11 UTC,"Reviewed:  https://review.openstack.org/516404
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ea53d9f1ea8bab797250f7add535fe16236f9a34
Submitter: Zuul
Branch:    stable/ocata"
1727855,2017-10-26 20:52:50 UTC,"In fact, the ComputeManager.rebuild_instance method doesn't even take a request_spec parameter."
1727855,2017-12-15 17:15:17 UTC,"Reviewed:  https://review.openstack.org/516400
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dc44c48943f8ce66bbbdc2050ed2dc47778cf477
Submitter: Zuul
Branch:    stable/pike"
1727855,2018-05-02 12:00:56 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1727855,2017-12-07 23:56:45 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1727855,2017-10-26 20:42:48 UTC,"The other thing is, this code in the conductor is wrong anyway since it's using the ""new"" image_ref requested for the rebuild:"
1727855,2017-10-30 17:29:14 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/516404"
1727855,2017-10-30 17:07:54 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/516400"
1727855,2017-10-27 07:44:35 UTC,Two things :
1727855,2017-10-26 21:47:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/515530"
1727855,2017-10-30 19:46:44 UTC,"Reviewed:  https://review.openstack.org/515530
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2690d6b038e200efed05bf7773898a0a8bb01d7
Submitter: Zuul
Branch:    master"
1727856,2017-10-26 21:24:43 UTC,I've smoke-tested this on AWS ENA instances -- looks fine.
1727856,2017-11-08 13:43:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1727856,2017-11-20 11:53:47 UTC,This bug was fixed in the package linux-aws - 4.4.0-1041.50
1727856,2017-11-20 12:11:54 UTC,This bug was fixed in the package linux-aws - 4.4.0-1003.3
1727861,2018-07-19 03:18:21 UTC,Does this need to be e-mailed somewhere?
1727861,2018-07-24 14:10:27 UTC,The HWE kernel has been pushed to 4.15 and the problem has disappeared (same machine). Tested again on Xenial and Bionic (which has the newer kernel) and they work fine.
1727861,2018-07-24 14:18:01 UTC,"This is fixed somewhere between kernel 4.13 and 4.15. Vague, I know, but it's a starting point. Longterm support kernels may still be affected but testing would take me an age. If I get time I'll test further."
1727861,2017-11-07 03:36:09 UTC,"A Debian user has reported this upstream.
https://bugzilla.kernel.org/show_bug.cgi?id=194639"
1727861,2017-11-07 03:23:29 UTC,"Same trace in Ubuntu Xenial on a Google Cloud image, but this time with CIFS."
1727861,2017-02-20 14:14:59 UTC,"I encountered this bug on a Debian Stretch system with an NFS 4 mount
and cachefilesd 0.10.9. NFS 4 file systems are mounted like this from
fstab:"
1727861,2017-11-07 03:31:31 UTC,"And Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751933"
1727861,2017-02-20 14:17:39 UTC,"Created attachment 254839
dmesg"
1727865,2020-09-11 14:52:29 UTC,Closing because INVALID.
1727874,2020-11-03 11:38:11 UTC,"Moreover apt-key should not be used at all since it has been deprecated with newest APT and will be removed in Q2/2022. I agree with Alistair that the key should be shipped within the effective directory /etc/apt/trusted.gpg.d/raspbian-archive-keyring.gpg directly, like the raspberrypi.org and Debian keyring packages do."
1727875,2018-01-21 10:55:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727875,2017-12-08 09:29:27 UTC,"Now I've compiled VICE from source (""manually"", with tarball from the official site etc), and the same result, crashing, with gdb reports things like this one (note, it was tested on two different machines running 17.10 both with official vice package and my own compiled one, always things like this I get):"
1727875,2017-12-09 19:11:53 UTC,"It seems there is something wrong with GLEW. At least I reported to the issue to the VICE team, and:"
1727875,2018-01-08 21:19:04 UTC,"It seems, the problem does not shows up if some compiles vice without gtk3 UI."
1727875,2018-01-21 10:58:32 UTC,"I can confirm, that the VICE binaries crash when running from the default Wayland session in 17.10. If logging in with an X.org session they will run OK."
1727877,2017-10-27 18:30:38 UTC,I installed Xonotic (3d game) benchmark to test both IGP and DGP. Here is the result:
1727877,2017-10-27 18:20:13 UTC,"Thank you Timo and Sebastien for the acknowledgement. I have filed this bug to Gnome BTS and here is the link: https://bugzilla.gnome.org/show_bug.cgi?id=789570 . Please bear with me, but I'm confused whether this needs to be reported to the wayland upstream too? Do ask if I need to run anything more."
1727877,2017-10-26 23:11:29 UTC,"The FPS I get with AMD R 520 card seems to be very low, if I run glxgears when compared to Intel Integrated graphics:"
1727877,2017-10-27 06:31:51 UTC,glxgears is not a benchmark
1727877,2017-10-27 10:48:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1727878,2017-11-13 21:27:31 UTC,I think the issue is that the config maps were not generated. Please do a ls /etc/kolla and see if anything exists. mariadb is just the first one that is checked.
1727884,2019-09-19 14:49:35 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1727887,2017-10-27 13:11:58 UTC,We already have dbus-accessibility-strict and dbus-accessibility. Snappy uses this instead of dbus-accessibility:
1727889,2017-11-11 01:30:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727889,2017-10-27 01:09:07 UTC,"When UFW is disabled, still errors (after a reboot and erasing the wine drive)."
1727893,2017-10-27 02:58:18 UTC,This isn't critical since not all clouds seem to support ICMP type rules eg AWS does but not Azure
1727897,2017-10-27 02:05:42 UTC,There seem to be other problems with enabling and then disabling Dash to Dock:
1727897,2020-09-14 07:46:58 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1727897,2017-10-27 02:06:58 UTC,I wasn't able to use ubuntu-bug because I'm on extension version 0.7.1 from artful-proposed.
1727898,2017-11-15 11:43:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727898,2018-12-30 00:03:14 UTC,This happened to me after I manually changed @ to @bad and renamed the last working @apt snapshot backup to @
1727898,2019-05-03 09:17:38 UTC,I also have this problem and confirm that just renaming /usr/bin/apt-btrfs-snapshot works as temporary work around.
1727898,2020-05-13 19:58:07 UTC,"Is any one of you NOT uuid in fstab to mount /?  Personally, I use LABEL and I believe that is what is creating this issue for me."
1727900,2018-12-07 16:32:22 UTC,"We noticed quite the same with MAAS v2.4.2 (2.4.2-7034-g2f5deb8b8-0ubuntu1). After failed commissioning the power OFF action sent to the node by MAAS automatically but MAAS was still showing these machines in power ON state. After manual power state check, MAAS updated the node status to power OFF."
1727900,2017-10-27 02:29:34 UTC,The power action should be reporting the final state of the power action. This is either the specific power driver doing the wrong thing or the whole RPC of performing power actions is wrong.
1727900,2019-09-19 12:05:09 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1727903,2018-02-13 11:59:38 UTC,"is this still an issue?
Senlin was designed to work only with keystone v3 api. We had not plan to support v2 API."
1727908,2020-03-05 06:33:37 UTC,"Agreed, the low activity could be because the bug is confirmed, reproduced and set at high priority. Most users who face the same issue (myself included) won't see any reason to add to the issue when a solution seems to be on its way."
1727908,2020-03-04 21:26:43 UTC,I saw this bug mentioned on https://discourse.ubuntu.com/t/release-bugs-for-week-commencing-monday-24th-february-2020/14540
1727908,2019-12-02 14:14:46 UTC,What this triggers in the logs:
1727908,2019-12-02 14:03:21 UTC,Video of the bug
1727908,2018-11-01 00:47:00 UTC,Temporary work-around: Rapidly clicking the checkbox will trigger the prompt for your password and make the desired change.
1727908,2020-03-10 16:14:06 UTC,"As already mentioned...

> Mouse-click/s do not work (no feedback) and produces an error in the terminal.
> Keyboard navigation and 'Enter' works fine (Authentication window appears)
"
1727908,2019-11-02 17:24:19 UTC,I am also facing this issue in Ubuntu 19.10 Eoan Ermine
1727908,2019-11-02 17:19:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727908,2019-12-02 13:49:31 UTC,"Just tested on focal. I didn't have the repo, so I added it:
```
deb http://archive.canonical.com/ubuntu focal partner
```
It correctly asked me the password and after that it was added. I deselected it to verify this bug.
Then I closed the software-properties-gtk window."
1727908,2020-03-31 19:30:10 UTC,"I see this issue in focal. Nothing happens if I try to enable or disable a source in the ""Other Software"" tab by clicking a checkbox. I get the same error message as mentioned in comment #2 if I start software-properties-gtk in terminal."
1727908,2020-05-26 20:52:11 UTC,"Hello PJSingh5000, or anyone else affected,"
1727908,2020-04-10 16:29:15 UTC,@Sebastien: I can confirm that your workaround fixes it for me. (Race condition?)
1727908,2020-04-10 18:23:45 UTC,"@Gunnar, thanks for testing! The sleep is a workaround, not a proper fix though. I would guess that something in the gtk widgets used is taking a grab which prevents the shell to be able to displays it's dialog so the proper fix would be to try to understand if that's an event or something we need to wait on before doing the call to polkit. If I don't success to find a better fix I will upload the sleep workaround"
1727908,2020-04-20 07:33:19 UTC,This bug was fixed in the package software-properties - 0.98.9
1727908,2019-08-27 13:37:34 UTC,Assigning to Seb since he's looked at it.  Please assign to me if I can help test / produce.
1727908,2020-05-26 22:38:28 UTC,Verified the test case using software-properties-gtk 0.96.24.32.13 from bionic-proposed.
1727908,2020-05-28 12:05:42 UTC,I had already applied the temporary fix as per comment #39 but I upgraded to version 0.96.24.32.13 in -proposed anyway. Attempting to check/uncheck any of the options on the 'Other Software' tab displayed a prompt to enter the 'admin' password. So I can also verify the issue will be fixed with this update.
1727908,2020-06-03 02:22:40 UTC,"The verification of the Stable Release Update for software-properties has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1727908,2020-06-03 02:23:16 UTC,This bug was fixed in the package software-properties - 0.96.24.32.13
1727908,2018-11-26 11:52:32 UTC,Work-around  : User arrow keys and press space to select
1727908,2020-04-10 09:52:58 UTC,"Ok, I'm a machine where I get the issue now"
1727908,2019-08-15 20:46:42 UTC,I encountered this same issue in a freshly installed Ubuntu 18.04 system.
1727908,2019-08-20 00:14:30 UTC,"I discovered that the Software & Updates application ""Authentication"" tab's ""Remove"" button does not work properly too. After pressing the ""Remove"" button, pkexec was called. After submitting the password for administration level, nothing happens, i.e. Trusted software keys that was selected for deletion do not get removed. Not error was shown in terminal."
1727908,2019-04-23 02:43:59 UTC,"Still present in Ubuntu 19.04, fresh install."
1727908,2018-12-07 13:03:13 UTC,"Thank you for your bug report, I can't confirm that problem neither on 18.04 nor 18.10 though, it might be specific to some configuration/theme/session. Do you use the standard ubuntu session?"
1727908,2018-12-07 14:44:14 UTC,"Sebastien, at present I can't confirm this on Xubuntu 18.04 but I still see a problem with Ubuntu 18.04 for which I have vanilla-gnome-desktop installed so using the Adwaita theme·"
1727908,2017-10-27 03:03:15 UTC,"Note, when I run software-properties-gtk from the command line, here is the output I receive whenever I click on a checkbox on the ""Other Software"" tab."
1727908,2017-10-27 11:04:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727908,2019-04-23 02:45:24 UTC,"Ubuntu version 19.04
GTK3 version 3.24.8-1ubuntu1
Gnome Shell Version 3.32.0"
1727908,2017-11-15 13:05:34 UTC,This may be a duplicate of bug 1660100.
1727908,2017-11-21 04:42:40 UTC,"After I click on the ""Canonical Partners"" on the ""Other Software"" tab, I do ~not~ see an OK button.  Also, I am not prompted to enter a password."
1727908,2017-11-21 04:43:29 UTC,"After I click on the ""Canonical Partners"" on the ""Other Software"" tab, I do ~not~ see an OK button.  Also, I am not prompted to enter a password."
1727908,2018-09-14 07:37:05 UTC,I have the same problem on at least 6 computers with 18.04.1 now.
1727908,2018-12-07 16:24:32 UTC,Using GTK_THEME=Adwaita software-properties-gtk works fine as well...
1727908,2017-10-27 11:05:15 UTC,Got the same bug in 17.10 on Ubuntu on Xorg.
1727908,2018-12-19 12:58:46 UTC,"This definitely occurs in both 18.04 & 19.04 but only in a ubuntu (gnome) session
Is not an issue in  wayland or unity(7) sessions"
1727908,2018-12-20 08:58:35 UTC,"Well, I can't trigger the issue on fresh 18.04 or 18.10 Ubuntu install with the default session, could be a timing issue and specific to some configs..."
1727908,2018-12-20 14:22:33 UTC,"This is what I get (fresh, updated 19.04"
1727908,2019-01-16 20:53:34 UTC,"the gnome-shell error is a bit weird, maybe there is an issue on this component"
1727908,2019-01-19 12:44:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727908,2019-03-20 14:16:24 UTC,"I have this issue both in 18.10 and 19.04. Using arrows and space does not work, the only workaround I've found is ""sudo software-properties-gtk"". Would be happy to provide any details that could be useful."
1727908,2019-03-20 15:28:34 UTC,"I find that primary(left-clicking) up to 15 or 20+ times _eventually_
spawns the pkexec-gui box."
1727908,2019-04-10 21:43:23 UTC,Interesting...
1727908,2019-04-10 22:17:15 UTC,"Oops, I meant to say, ""Less than *4* doesn't work, and more than 4 are not necessary."""
1727908,2018-12-07 16:35:43 UTC,"Can confirm that this is reproducible with the standard Ubuntu session in 18.04.01 and 18.10, tested both with the vanilla install with no updates and also fully updated."
1727956,2020-01-14 15:54:54 UTC,Fix Released?
1727956,2017-11-09 21:21:08 UTC,"Confirmed: having an existing LUKS or LVM install and trying to reinstall over it causes ubiquity to try to install grub to /dev/dm-0 instead of /dev/sda, which fails."
1727956,2019-02-22 09:39:32 UTC,"Hi there,"
1727958,2018-01-28 16:58:46 UTC,"It says ""Fix released"" but it was never for me and I still have the problem of white generic LibreOffice icon in dock - I'm now on Ubuntu 18.04 but was also the case on 17.10..."
1727958,2020-08-11 09:44:28 UTC,Seems this has been fixed for a while.
1727958,2019-07-26 11:27:36 UTC,Thanks.
1727958,2019-07-26 08:14:51 UTC,"Yes, bug is still present, even in Ubuntu 19. 10 :"
1727958,2019-07-26 05:52:08 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1727958,2018-12-06 12:45:49 UTC,In the above mentioned bug-report there is a patch included.
1727958,2018-12-06 12:43:15 UTC,The bug is still present in Ubuntu 18.10.
1727958,2018-04-23 11:51:38 UTC,"wrt this specific bug, given the current availability of apis this is as good as it gets. wrt ""doesn't start"", it starts fine for me and in Fedora distro generally"
1727958,2018-01-29 02:20:29 UTC,"This bug does not say Fix Released any more. It is open (""Triaged"")."
1727958,2017-10-27 10:44:43 UTC,https://bugs.documentfoundation.org/show_bug.cgi?id=100158 as well
1727958,2017-10-27 08:32:12 UTC,I'm using the default Gnome Shell.
1727958,2017-10-27 08:43:28 UTC,Thanks
1727958,2016-08-02 12:03:12 UTC,I guess we can set to NEW.
1727958,2016-12-01 07:20:09 UTC,*** Bug 104285 has been marked as a duplicate of this bug. ***
1727958,2017-02-23 17:01:15 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=779143 for my proposed change to let me at the property we need via gtk
1727958,2017-03-23 14:17:46 UTC,"Caolán McNamara committed a patch related to this issue.
It has been pushed to ""master"":"
1727958,2017-10-27 10:44:06 UTC,Thank you for your bug report.
1727958,2017-03-26 09:22:42 UTC,"(In reply to Luke from comment #5)

> Ever since
> http://cgit.freedesktop.org/libreoffice/core/commit/
> ?id=6903066822900a700ccf67ae70fa171c94644a9a
>
> Related: rhbz#1334915 tdf#100158 hack using startcenter icon under wayland
>
> When I try to launch libreoffice, nothing happens. Reverting this commit
> fixes the issue. I have reproduced this bug on both Ubuntu 16.04 and 16.10.
"
1727958,2017-10-27 07:57:36 UTC,"Are you using Gnome Shell (default in 17.10) or Unity? Only the latter has BAMF, AFAIK."
1727958,2016-05-31 09:21:46 UTC,"Hi,"
1727958,2017-03-26 05:07:50 UTC,"Ever since
http://cgit.freedesktop.org/libreoffice/core/commit/?id=6903066822900a700ccf67ae70fa171c94644a9a"
1727961,2017-10-27 07:46:32 UTC,Patch proposal to preserve class attribute
1727961,2017-10-27 08:09:22 UTC,"Patch seems correct, Thanks. Anyway there is a typo in a comment ""// remember id"" > ""// remember class"""
1727961,2017-10-28 17:28:07 UTC,Thanks. please commit or make a MR in gitlab.
1727961,2017-10-31 08:23:12 UTC,Ok I finally managed how to make.
1727961,2017-10-31 23:34:00 UTC,pushed in https://gitlab.com/inkscape/inkscape/commit/36216068dee24b54d67a35854d9160a9ec5f76dc
1727964,2017-10-27 08:10:32 UTC,"StacktraceTop:
 XRRGetCrtcInfo (dpy=0x55c92310ea10, resources=resources@entry=0x55c9231a30d0, crtc=743) at ../../src/XrrCrtc.c:54
 init_randr15 (changed=<synthetic pointer>, screen=0x55c923126020) at ././gdk/x11/gdkscreen-x11.c:466
 init_multihead (screen=screen@entry=0x55c923126020) at ././gdk/x11/gdkscreen-x11.c:840
 process_monitors_change (screen=0x55c923126020) at ././gdk/x11/gdkscreen-x11.c:990
 read_settings (x11_screen=<optimized out>, do_notify=do_notify@entry=1) at ././gdk/x11/xsettings-client.c:509"
1727970,2018-08-14 13:49:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727971,2017-10-27 08:39:03 UTC,Backtrace:
1727971,2018-09-27 12:54:40 UTC,"Same here!
Suddenly while working kontact krashed and won't come up again. kmail as well
Any clues how to solve this prob?"
1727971,2020-02-24 07:00:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1727971,2017-12-11 06:56:39 UTC,"I'm having the same problem on Kubuntu
its just suddenly start crashing,"
1727989,2017-10-27 13:21:45 UTC,"I cannot reproduce this with Terminator 1.91 on Ubuntu Artful and Unity 7 desktop. F12 always presents the guake window, even when the cursor/focus is in terminator."
1727989,2017-10-27 14:53:13 UTC,"Thank you very much for the clear explanation. Now I can understand what might be wrong. Also, I appreciate the pointer to Guake's bugtracker. I will look into that."
1727989,2017-10-28 06:16:58 UTC,I have found a work around that was described in a bug that affects guake but probably originates from wayland. The work around is simple (and I am copying from the issue):
1727989,2017-10-28 06:21:25 UTC,I can confirm that the workaround works.
1727989,2017-10-28 09:30:08 UTC,How can I use this workaround with Terminator?
1727989,2017-10-28 19:39:30 UTC,"You don't. You follow the workaround and then F12 works for all applications, including when Terminator has focus. The problem is not with Terminator. It is with GTK2/3."
1727989,2019-04-13 08:30:39 UTC,"I saw this issue is still open. It should not be, but it could have a status that says the problem is with a different system (gtk2/3 in this case)."
1727990,2017-11-14 10:59:18 UTC,Thank you very much!
1727990,2017-10-27 10:13:00 UTC,I will do my very best ;-)
1727993,2017-10-27 09:33:00 UTC,See also a related discussion on https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1042771.
1727993,2017-10-27 13:03:23 UTC,"I commented in the other bug, but will repeat myself here: ""Note that this is rather tricky. If the user disabled the evince profile, using Px means that the exec will fail with 'profile not found'. There is no way to specify 'use P if it exists, otherwise C'."""
1727998,2019-05-28 04:17:28 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1728002,2017-10-27 10:32:44 UTC,"Thank you for your bug report. Indeed that's a missing feature, note that if you use e.g hexchat as IRC client you can install hexchat-indicator and you would have a count-badge on the launchpad indicating the number of unread msgs which solves the need to poll issue as well"
1728004,2019-09-19 14:46:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1728012,2017-10-31 11:03:36 UTC,Epson 2400 photo doesn't work in Iscan (can't send to scanner). Works fine with xsane.
1728012,2017-10-27 14:05:47 UTC,I can confirm that the Epson Perfection V300 is also affected
1728012,2019-07-01 06:41:24 UTC,"@Gunnar Hjalmarsson:
in bionic I had to install libusb-0.1-4 to be able to scan with my MFC-440CN (brscan2), because it ships libusb-1.0-0 by default."
1728012,2017-10-27 11:29:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728012,2019-06-30 22:29:36 UTC,"I am having issues myself, but I think mine are related to running ubuntu
in a VM on Windows."
1728012,2019-06-30 22:10:14 UTC,"The annoyance with Brother .deb files for scanner drivers installing in /usr/lib64/sane has been mentioned multiple times above. The PPA now includes a proposed fix of that for eoan, disco and bionic."
1728012,2019-06-26 16:15:31 UTC,I have uploaded a proposed fix of sane-backends to this PPA:
1728012,2019-06-25 23:54:52 UTC,"To the extent this bug is similar to the linked Debian bug, it was fixed in Ubuntu 19.04, so I marked it as ""Fix Released"". OTOH, in that case there is a need to backport the fix to Ubuntu 18.04, and therefore I added a bionic bug task."
1728012,2019-05-08 05:04:02 UTC,"@Luca-mg: What your computer sees is the following:
 - You attach a device whose USB ID doesn't match any udev rule => the device is accessible for the root user only.
 - then you as the root user start a program that uploads something to the device.
 - the device disconnects and
 - a new device connects, this time using an USB ID there is an udev rule for. This rule tells the device is a scanner. You are in the group ""scanner"" => You can use it without root rights."
1728012,2019-07-01 08:24:54 UTC,"@renbag: Tried that, but didn't help for me."
1728012,2019-05-08 04:18:40 UTC,@ Chris Rainey: no such a thing in my system.
1728012,2019-05-07 20:06:24 UTC,"@luca.mg: have you checked for firmware updates? My Brother DCP-L2550DW can
update from the web interface in the system tools/administration tab and
there have been a few updates in the last year."
1728012,2019-05-07 19:38:34 UTC,"@ PeterPall: regarding the Epson scanner, yes it could be the firmware upload, the first root scan took time, I thought it was the scanner warming up longer than usual and not catching up, but I allowed time and it finally went through, so You may very well be right. I did not run lsusb -v, just a plain lsub, but before the root scan the scanner was detected as an epkowa driven unknown model, after the root scan it is detected with the proper model name."
1728012,2019-05-07 14:47:35 UTC,"Just a reminder to those of us using Brother DCP or MFP's: I repeatedly
find that the only way to properly install the printer and scanner drivers
is to use the ""Installer Script""(i.e. 09/13/2018
(2.2.1-1)) provided on the model downloads page(see below) and to follow
the directions given _explicitly_(to-the-letter, no exceptions)! I've tried
to install a recently updated scanner driver(i.e. 01/21/2019
(0.4.7-1)) by itself as an upgrade to the currently installed one and even
re-ran the setup command(i.e. Brsaneconfig4 -a name=(name your device)
model=(model name) ip=xx.xx.xx.xx) for my network(Wi-Fi) DCP-L2550DW, but
it does not work that way. I can't stress, enough, the apparent need to
re-run the ""Installer Script"", exactly as shown--below, in order for
everything to work!"
1728012,2019-05-07 12:30:47 UTC,"Then perhaps uploading the firmware to the scanner can only be done as root, for some reason.
Does the output of susb -v change after scanning for the first time?"
1728012,2019-05-07 11:55:58 UTC,"Hi Peter, if the above is addressed to me, the Epson scanner works for regular users after the first scan as root, I do not get the reason why, but this is it.
Thank You for stepping in."
1728012,2019-05-07 11:28:47 UTC,If the scanner can be found only by the superuser that might indicate that an udev rule that allows scanner access for ordinary users is missing. Or that this udev rule gives scanner access to an user group you happen not to be part of...
1728012,2019-05-07 09:46:59 UTC,"Hi Michael, sudo is enough for driver installation, if You did not sudo that is why install failed. Root is the real system administrator, not needed for this task."
1728012,2019-05-07 20:11:42 UTC,"Then the answer is simple: extend the udev file with the usb if of the scanner without firmware so use will give you write access to this device, too. Once that is done sane can upload the firmware, the scanner can identify itself as the model you have bought and you can scan. Seems like we should collect the Epson usb IDs somewhere..."
1728012,2019-05-07 09:31:05 UTC,"Dear Luca, I'm new to linux but to answer your question, I think I used the commandes SUDO. But what's the difference between root and sudo?"
1728012,2019-07-01 15:44:12 UTC,"I made a new attempt with bionic, and yes!!"
1728012,2019-07-02 15:39:42 UTC,Thanks @renbag. With your help I'm now confident enough to proceed with the principal bionic change.
1728012,2020-01-10 21:12:52 UTC,"Just wanted you to know the scan function on my OfficeEdge Pro5500 is
working again!   I installed the following driver from Lexmark Support
(Australia)."
1728012,2019-11-20 10:03:39 UTC,"@Miles: Yes, bug #1835220 is still open, unfortunately. Good that you found your way."
1728012,2019-11-20 05:41:21 UTC,"Ran into the same scanner issue today with a Brother MFC-6490CW under Ubuntu 18.04 (factory installed by Dell and fully updated before attempting printer/scanner install). Found pdc's post on askubuntu.com ( https://askubuntu.com/a/1054065/314730 ) first, which linked to staedtler-przyborski's symlink answer ( https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/comments/25 ). Worked a treat - thanks so much!"
1728012,2019-07-22 21:17:36 UTC,"Worked for me...
~$ uname -a
Linux hades 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
~$ lsb_release -a
LSB Version: core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic"
1728012,2019-07-22 21:15:10 UTC,"Hi,"
1728012,2019-07-21 23:48:05 UTC,"Hi Phil,"
1728012,2019-07-21 21:25:24 UTC,"Hi Lukasz,"
1728012,2019-07-01 20:11:23 UTC,"I confirm that the packages in the proposed PPA allow to scan with a Brother MFC-440CN (brscan2).
I tried booting directly from a bionic USB stick and followed the steps listed on comment #232 (except adding a libsane rule, which is not needed in my case) and additionally installed libusb-0.1-4.
Thanks to Gunnar for the fix!"
1728012,2019-07-19 18:00:58 UTC,So finally this has been fixed also in 18.04. I want to thank Steven Santos who called my attention to the problem as well as the solution.
1728012,2019-07-18 08:16:19 UTC,This bug was fixed in the package sane-backends - 1.0.27-1~experimental3ubuntu2.1
1728012,2019-07-18 08:16:07 UTC,"Normally I'd say we should wait for verification using a test case that does not involve any workarounds, but seeing the actual bug-fix I think it might be safe to release it with the testing it got already. This seems to be a logical change."
1728012,2019-07-11 15:35:33 UTC,"Hello I'm new to Linux Mint. Can any one help me with getting the scanner of Brother DCP750 to work ?
With much thanks,
Michael"
1728012,2019-07-10 17:35:52 UTC,"Samsung Xpress M2070
After installing the drivers (sudo sh install.sh)"
1728012,2019-07-09 01:24:14 UTC,"Since I have an old Brother device whose drivers are installed via brscan2, the proposed change (which adds support for drivers located in /usr/lib/sane) doesn't really apply to me. But I worked around that."
1728012,2019-07-09 00:16:31 UTC,"Hello PeterPall, or anyone else affected,"
1728012,2019-07-03 14:28:16 UTC,"I decided to break out the /usr/lib64/sane thing to bug #1835220, so we can proceed with the more important bionic fix."
1728012,2019-07-18 08:16:25 UTC,"The verification of the Stable Release Update for sane-backends has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1728012,2019-05-07 05:36:21 UTC,"Hi again, Epson Perfection 4490 Photo, new Ubuntu Mate 19.04 install, iscan-bundle-1.0.0.x64.deb.tar.gz driver, make sure to add the line 'epkowa'to the /etc/sane.d/dll.conf file first; xsane gave a 'Access to resource has been denied' message as a regular user, same with 'sudo xsane' from a terminal, what I did is:"
1728012,2019-06-30 23:47:52 UTC,I submitted <https://bugs.debian.org/931297> about the /usr/lib64/sane thing.
1728012,2019-05-07 05:08:27 UTC,"Hi Michael, are You installing as root or sudo?"
1728012,2017-11-01 19:09:31 UTC,A Test here showed:
1728012,2017-11-01 17:06:48 UTC,X-Org or wayland doens't matter. My scanner works with both (verfied).
1728012,2017-11-01 16:17:34 UTC,Are on x-org or wayland ? Can you try what happens if you switch to X-org ?
1728012,2017-11-01 16:09:55 UTC,Thats interesting. I don't need to be root to scan.
1728012,2017-11-01 15:35:11 UTC,Update: Just tried it as root. I works.
1728012,2017-11-01 15:26:38 UTC,Sorry to say that staedtler-przyborski solution did not work for me (epson V370 photo). Deb file is different in my case (iscan-perfection-v370-bundle-1.0.1.x64.deb.tar.gz)
1728012,2017-11-01 14:00:47 UTC,BRScan users can you try what happens when copy the files (libsane-brother*) from /usr/lib64/sane/ to /usr/lib/x86_64-linux-gnu/sane.
1728012,2017-11-02 03:43:49 UTC,"I did not have the 79-udev-epson.rules file, so I created one with the content you posted. My scanner works now. No root needed. Many thanks."
1728012,2017-11-01 12:02:42 UTC,Just for the record
1728012,2017-10-31 17:52:18 UTC,"Epson v370 photo doesn't work either. Purchased only 3 months ago, it was fully functionnal in zesty. Now totally unusable in artful even with libsane1 1.0.27-1~experimental2ubuntu2.1"
1728012,2017-10-31 07:09:20 UTC,Cross posting from https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352?comments=all
1728012,2017-10-29 21:49:53 UTC,"Add to list of scanner ""broken"" - Epson Perfection V300 Photo."
1728012,2017-10-27 20:05:11 UTC,Probably related: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1724078
1728012,2017-10-27 19:55:18 UTC,Forgot to mention that I use or rather attempt to use the scanner over the TCP.
1728012,2019-05-07 05:13:58 UTC,"Hi all, Brother MFC-1910W, new Ubuntu Mate 19.04 install, Brother drivers from https://support.brother.com/g/b/downloadend.aspx?c=as_ot&lang=en&prod=mfc1910w_eu_as&os=128&dlid=dlf006893_000&flang=4&type3=625&dlang=true at first the scanner was not detected, my previous workaround involving libsane-extras is not an option anymore, since the package has been pulled out. What I did is:"
1728012,2017-10-27 16:35:38 UTC,"Kubuntu 17.04
Fail to use Epson Perfection V30"
1728012,2017-11-01 11:53:34 UTC,Today I managed to bring back my dead Epson V300 alive :-)
1728012,2017-11-03 10:09:42 UTC,My Brother MFC-J220 works now with the 1.0.27-1~experimental2ubuntu2.1 packages.
1728012,2017-10-27 19:51:52 UTC,"Xerox Workcentre 3225 with the drivers version 1.00.25:00.05 that used to work very well with Zesty's libsane still not functional.
My malfunction hasn't changed a bit with the 1.0.27-1~experimental2ubuntu2.1 package.
Like before xsane crashes with the following message:
  Not a JPEG file: starts with 0x00 0x00
and/or hangs with scanning status.
mariusz:~> dpkg -l | grep sane
ii  libkf5sane-data                                 17.04.3-0ubuntu1                            all          scanner library (data files)
ii  libkf5sane5                                     17.04.3-0ubuntu1                            amd64        scanner library (runtime)
ii  libksane-data                                   4:17.04.3-0ubuntu1                          all          scanner library (data files) - transitional package
ii  libksane0                                       4:15.08.3-1ubuntu2                          amd64        scanner library (runtime)
ii  libsane-common                                  1.0.27-1~experimental2ubuntu2.1             all          API library for scanners -- documentation and support files
ii  libsane-extras:amd64                            1.0.22.5                                    amd64        API library for scanners -- extra backends
ii  libsane-extras-common                           1.0.22.5                                    all          API library for scanners -- documentation and support files
rc  libsane-hpaio:amd64                             3.16.7+repack0-1ubuntu1                     amd64        HP SANE backend for multi-function peripherals
ii  libsane1:amd64                                  1.0.27-1~experimental2ubuntu2.1             amd64        API library for scanners
ii  sane                                            1.0.14-12build1                             amd64        scanner graphical frontends
ii  sane-utils                                      1.0.27-1~experimental2ubuntu2.1             amd64        API library for scanners -- utilities
ii  xsane                                           0.999-5ubuntu2                              amd64        featureful graphical frontend for SANE (Scanner Access Now Easy)
ii  xsane-common                                    0.999-5ubuntu2                              all          xsane architecture independent files"
1728012,2017-11-03 18:45:41 UTC,"For Xerox Workcentre 3225 I have mentioned in this and the original sane bug the solution is:
1. Link the files in /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane,
2. Add the user that needs to use the scanner to the ""lp"" group.
Otherwise the ""Not a JPEG file: starts with 0x00 0x00"" issue persists."
1728012,2017-11-03 17:34:31 UTC,@ Hans Schwimmbeck
1728012,2017-11-04 19:06:32 UTC,"@staedtler-przyborski
I'm on xorg... I forgot to mention: the Brother scanner only works as root AND with xsane, simple-scan doesn't work at all."
1728012,2017-11-04 17:53:55 UTC,@luca.mg
1728012,2017-11-04 10:12:37 UTC,@luca.mg
1728012,2017-11-04 09:19:14 UTC,"I have no glue why Epson has chosen '0777', maybe it's because they upload a firmware to their scanners ..."
1728012,2017-11-04 08:50:51 UTC,PS I'm on brscan 4.
1728012,2017-11-04 08:50:25 UTC,"Thank You for Your time Hans, I do not like 0777 as well, but I was shooting in the dark. As stated, I tried
## Brother MFC-1910W
ATTRS{idVendor}==""04f9"", ATTRS{idProduct}==""035d"", MODE=""0666"", GROUP=""scanner"", ENV{libsane_matched}=""yes"" (or 0660 0664 0777 modes)"
1728012,2017-11-04 08:06:49 UTC,"I don't like MODE=""0777"" in the Epson derived example."
1728012,2017-11-04 17:47:55 UTC,"Hi staedtler-przyborski, and thank You for taking the time to further investigate the matter. Yes indeed, I did try to install the brother-udev-rule-type1 package You kindly linked, also tinkering with the various settings, and tested with a later release too, even if both weren't needed in zesty, nor in xenial (I guess that the package was required with earlier ubuntu releases), but it doesn't make any difference: the scanner is found by sane-find-scanner, but is not detected by scanimage -l, and it only works running xsane from the terminal after the 'su root' command, while 'sudo xsane' won't work at all. I'm quite sure that it's a permission issue, but I'm out of ideas as to how to fix it, and using the scanner as root is not a feasible option."
1728012,2017-11-04 07:24:37 UTC,"I can confirm that the Epson Perfection 4490 Photo scanner, iscan-gt-x750-bundle-1.0.0.x64 based, works by creating symlinks of the /usr/lib/sane/libsane-epkowa* files into the /usr/lib/x86_64-linux-gnu/sane directory by issuing the command 'sudo ln -sfr /usr/lib/sane/libsane-epkowa* /usr/lib/x86_64-linux-gnu/sane' as said above; no need to tinker with the udev rules files in my case. This doesn't look like a bug fix to me, it's a workaround, needing a user tweak, libsane1 should look for third party sane drivers (once called backends IIRC) in the ""legacy"" directories as well as in the new ones, for backward compatibility."
1728012,2017-11-04 06:52:42 UTC,Dear Hans could you please test if a more generic solution like the one provided by Epson would also work for local attached Brother Scanners ?
1728012,2017-11-04 05:28:56 UTC,"I forgot to mention that also needed is something like /etc/udev/rules.d/59-local.rules.
In my upgraded installation it has not changed since 16.04 and looks like this:
---------------
# Brother MFC-J220
ATTRS{idVendor}==""04f9"", ATTRS{idProduct}==""0259"", MODE=""0664"", GROUP=""scanner"", ENV{libsane_matched}=""yes"""
1728012,2017-11-03 21:13:01 UTC,In the meanwhile I had a look on different brscan drivers ...
1728012,2017-11-03 20:14:36 UTC,Thanks Mariusz. Can you please specify which files are in /usr/lib/sane (just to make the command below more precise) ?
1728012,2017-11-03 20:45:16 UTC,"> ls -la /usr/lib/sane/
total 40
drwxr-xr-x   2 root root  4096 Oct 27 12:10 .
drwxr-xr-x 147 root root 36864 Oct 17 15:30 ..
lrwxrwxrwx   1 root root    31 Oct 27 12:10 libsane-smfp.so -> /usr/lib/sane/libsane-smfp.so.1
lrwxrwxrwx   1 root root    35 Oct 27 12:10 libsane-smfp.so.1 -> /usr/lib/sane/libsane-smfp.so.1.0.1
lrwxrwxrwx   1 root root    50 Oct 27 12:10 libsane-smfp.so.1.0.1 -> /opt/smfp-common/scanner/lib/libsane-smfp.so.1.0.1
"
1728012,2017-11-03 20:44:54 UTC,"You are a genius! My MFC8510 and my Epson WorkForce GT-1500 now work fine...
...now we should forward this info to the sane programmers (perhaps they can make the program look in both the old and the new locations), to Debian - and to the manufacturers: Symlinks isn't hard to create in the postinstall scripts. Perhaps they will add the necessary lines."
1728012,2017-11-04 07:31:07 UTC,"The Brother MFC-1910W printer-fax-scanner, brscan4 based, does not work with the symlink trick, the scanner is detected by sane-find-scanner, but is not listed by scanimage -l, and will only work after enabling the root account and issuing the 'su root' and 'xsane' commands in a terminal; a simple sudo xsane won't work. Although it seems to me a permission issue, creating appropriate (to the best of my knowledge!) udev rules files in the /etc/udev/rules.d directory and/or in /lib/udev/rules.d directory has no positive outcome, nor editing the the /lib/udev/rules.d/60-libsane1.rules file; my attempts were using the lines"
1728013,2019-10-07 13:41:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728013,2017-10-27 11:04:28 UTC,I think I found the issue:
1728013,2017-10-27 10:44:58 UTC,I am also running NetworkManager 1.4.4-r1.
1728013,2017-10-27 10:50:00 UTC,"I see this repeatedly in the logs.  Just prior to the segfault, NetworkManager is clearing out DNS information."
1728031,2017-10-31 12:17:51 UTC,"I can reproduce the issue. I ran the latest horizon master branch f911d0dd406f60fa9df5891ff5760f2251fc96b0 by using runserver tox env (tox -e runserver). After adding ENFORCE_PASSWORD_CHECK = True to local_settings.py, I see the message ""The admin password is incorrect.""."
1728031,2017-10-31 05:50:41 UTC,"Hello Ying,"
1728031,2017-10-31 04:49:15 UTC,"Hello Sudheer,"
1728031,2017-10-31 12:20:00 UTC,"After adding an error log message to 'except' clause of user_verify_admin_password in openstack_dashboard.api.keystone, I got the following error message."
1728031,2017-10-29 21:19:36 UTC,I enabled the ENFORCE_PASSWORD_CHECK and was able to change a user's password with the admin password successfully. I use keystone v3 though.
1728031,2017-10-29 11:41:39 UTC,"Hello Ying,"
1728031,2017-10-28 22:35:01 UTC,I am not able to reproduce the issue with the master branch. What version of horizon and keystone are you using?
1728031,2017-10-30 05:32:26 UTC,"Hello Ying,"
1728039,2019-09-30 14:57:03 UTC,Which way is preferred? Setting the processes or threads to the $cpu_count?
1728039,2019-09-30 15:08:42 UTC,"@Luke, IIRC the summary from the freezing heartbeats under WSGI topic, it should be always threads=1, like processes=12 threads=1"
1728039,2019-09-30 15:18:30 UTC,"I confirm Bogdan you remember correctly:
- https://bugs.launchpad.net/nova/+bug/1829062/comments/19
- https://bugzilla.redhat.com/show_bug.cgi?id=1711794
- https://github.com/openstack/puppet-nova/blob/stable/stein/manifests/wsgi/apache_api.pp#L55-L57
- https://bugs.launchpad.net/nova/+bug/1829062"
1728039,2019-10-01 18:02:17 UTC,"Somewhat related, here's the original (and resolved) report of this problem affecting the Overcloud's performance: https://bugzilla.redhat.com/show_bug.cgi?id=1347305"
1728039,2019-10-01 19:46:24 UTC,I can confirm that this is fixed for all services in the latest version of Queens.
1728039,2021-02-12 10:05:59 UTC,I know this is an old bug and I know that the AMQP heartbeat could be lost when we have more than one thread what was reported and investigated here https://bugzilla.redhat.com/show_bug.cgi?id=1711794
1728045,2018-09-18 06:38:45 UTC,Resurrecting this bug report to mention that I also miss the time remaining but also provide a resolve.
1728045,2020-11-06 20:14:59 UTC,bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.
1728045,2017-12-18 15:42:10 UTC,I don't understand why you unlinked the GNOME bug. This has been an issue since GNOME 2 and remains an issue in GNOME 3.
1728045,2017-12-19 02:53:29 UTC,Because Gnome 2.x and Gnome 3.x are effectively different products with different designs. It may be unhelpful if the old discussion there no longer applies to the current design.
1728045,2008-06-27 07:21:39 UTC,"What exactly do you want, clearer icons or a bigger bar thing?"
1728045,2017-12-18 10:36:24 UTC,I am unlinking https://bugzilla.gnome.org/show_bug.cgi?id=540373 because it seems like that's too old to be relevant (talking about Gnome 2.x).
1728045,2008-06-26 20:07:44 UTC,"The old batt-stat applet used to allow the user to show on the battery icon a more accurate representation of battery life remaining, either in percentage or estimated time remaining."
1728045,2017-10-30 08:48:05 UTC,I never said I agree with the Gnome design choices. Just historically the Gnome 3.x people have been particularly keen to keep things minimal. I agree with you and would prefer to see time remaining.
1728045,2017-10-30 08:29:37 UTC,">I believe you can still see estimated battery time remaining if you click on the panel menu (top right?).
"
1728045,2017-10-30 08:28:03 UTC,">It might be a design choice though, to keep the panel bar ""clean"".
"
1728045,2017-10-30 05:38:44 UTC,"It might be a design choice though, to keep the panel bar ""clean""."
1728045,2017-10-30 05:37:02 UTC,This oldish bug might be talking about the same thing. I'm not sure since the architecture has changed over the years... https://bugzilla.gnome.org/show_bug.cgi?id=540373
1728045,2017-12-15 17:18:06 UTC,"Has there been any resolution to this?  Or is one underway?  When I go to the link for the bug link mentioned here (#540373), the last comment or update of any kind I see is from 2009..."
1728045,2017-10-27 14:28:44 UTC,"Oops, I didn't read your bug report carefully enough."
1728045,2017-10-27 14:27:34 UTC,"Jonathan, install the GNOME Tweaks app (gnome-tweak-tool)."
1728045,2009-03-04 15:26:16 UTC,"(In reply to comment #5)

> Also, is there any chance of GNOME doing the colours based on time remaining
> rather than percentage remaining? The indicator on my 6-hour-life Thinkpad
> turns red when it has more usable time remaining than some laptops when fully
> charged!
"
1728045,2009-01-23 04:15:20 UTC,Richard: will this new applet infrastructure work also allow more fine-grained icons for discharge? How is the work going?
1728045,2008-06-30 14:22:35 UTC,"Thank-you for the information, I'll look him up. Also thank-you for keeping the bug open and not making it a WONTFIX, I think it would improve the usefulness of g-p-m in the future, especially for laptop users."
1728045,2008-06-30 13:12:47 UTC,"We can't do this just yet. We need the new applet infrastructure work so we can add ourselves to a panel like g-p-m can do with GtkStatusIcon and also be resizable and appendable like an applet can be. Ryan Lortie is working on the new applet stuff, you'll have to ask him how it's progressing."
1728045,2008-06-27 09:32:31 UTC,Ideally both.
1728045,2017-10-27 14:38:59 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1728053,2019-01-31 23:18:55 UTC,is anyone still having the issue in bionic and test if using cp/gio copy command give a different behaviour?
1728053,2018-06-18 17:37:21 UTC,"this is apparently also a problem in Bionic-Beaver.  I started a file copy 7,633 files to a new USB stick (SSD to USB 3.1).  The copy started out like I expected, at a displayed rate of about 345MB/s.  By the time, it reached roughly 1/2 the copy began to slow and before long, it was down to about 34MB/s."
1728053,2017-11-01 11:21:37 UTC,"Comment # 4 on bug 789647 from Ondrej Holy from bugzilla.gnome.org:
https://bugzilla.gnome.org/show_bug.cgi?id=789647"
1728053,2017-10-29 14:25:51 UTC,"1) Values from the sysctl file:
/.../
vm.admin_reserve_kbytes = 8192
vm.block_dump = 0
vm.compact_unevictable_allowed = 1
vm.dirty_background_bytes = 0
vm.dirty_background_ratio = 10
vm.dirty_bytes = 0
vm.dirty_expire_centisecs = 3000
vm.dirty_ratio = 20
vm.dirty_writeback_centisecs = 500
vm.dirtytime_expire_seconds = 43200
vm.drop_caches = 0
vm.extfrag_threshold = 500
vm.highmem_is_dirtyable = 0
vm.hugepages_treat_as_movable = 0
vm.hugetlb_shm_group = 0
vm.laptop_mode = 0
vm.legacy_va_layout = 0
vm.lowmem_reserve_ratio = 256	32	32
vm.max_map_count = 65530
vm.min_free_kbytes = 34096
vm.mmap_min_addr = 65536
sysctl: permission denied on key 'vm.mmap_rnd_bits'
vm.nr_hugepages = 0
vm.nr_overcommit_hugepages = 0
vm.nr_pdflush_threads = 0
vm.oom_dump_tasks = 1
vm.oom_kill_allocating_task = 0
vm.overcommit_kbytes = 0
vm.overcommit_memory = 0
vm.overcommit_ratio = 50
vm.page-cluster = 3
vm.panic_on_oom = 0
vm.percpu_pagelist_fraction = 0
vm.stat_interval = 1
sysctl: permission denied on key 'vm.stat_refresh'
vm.swappiness = 60
vm.user_reserve_kbytes = 131072
vm.vdso_enabled = 1
vm.vfs_cache_pressure = 100
vm.watermark_scale_factor = 10"
1728053,2017-10-28 13:27:13 UTC,"Some more info:
$ cat /proc/vmstat | egrep ""dirty|writeback""
nr_dirty 0
nr_writeback 0
nr_writeback_temp 0
nr_dirty_threshold 0
nr_dirty_background_threshold 0"
1728053,2017-10-28 08:19:35 UTC,"Typically, e.g. Select a file (desktop) > drag and drop copying / moving > target USB flash drive / external USB hard disk
I do not typically use a command line"
1728053,2017-10-28 08:22:21 UTC,"Note: Previously there were no such anomalies at 16.04... After many updates and patches to the LTS version come in, I'm not sure what to do with the phenomenon.
But it is a fact that several weeks exist"
1728053,2017-10-27 16:08:50 UTC,"thank you for your bug report, is it better if you copy from another filemanager or from a commandline?"
1728053,2017-10-27 15:12:23 UTC,"dirty_background_bytes: 0
dirty_background_ratio: 10
dirty_bytes: 0
dirty_ratio: 20
dirtytime_expire_seconds: 43200
dirty_expire_centisecs: 3000
dirty_writeback_centisecs: 500"
1728053,2017-10-28 09:50:09 UTC,"The previously ""dirty"" values are original. Are these values normal?"
1728062,2020-12-22 04:21:18 UTC,This bug was fixed in the package telepathy-idle - 0.2.2-1
1728068,2020-02-02 23:58:57 UTC,"Missing header also affects Eoan (latest current).  Given the absence of LAPACKE in Bionic, the most likely explanation is that it was built with non-standard NOLAPACKE.  Worth noting that the Bionic build of lapacke appears to link to openblas, but also links to reference blas & lapack, so it's not clear if the optimized routines are used or not (or if this makes a difference)."
1728068,2020-02-02 22:52:08 UTC,"Also affects Bionic (latest LTS).
LAPACKE symbols are not exported by the so."
1728068,2017-12-29 11:13:55 UTC,It this bug tracker being reviewed by any maintainers?
1728068,2017-12-25 04:49:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728068,2017-12-29 14:39:58 UTC,I'm also waiting for a fix. I might try and patch in the next couple of weeks. Do you have any experience of that?
1728069,2017-10-27 14:51:02 UTC,I also see this in the Mir logs:
1728069,2017-10-30 04:12:32 UTC,"The log message at least, means the compositor has released the buffer too early (before compositing). Hence the client will appear to hang as new frames don't reach the screen."
1728069,2017-11-03 16:31:22 UTC,Syncing task from Mir.
1728069,2017-12-14 17:12:57 UTC,This bug was fixed in the package mir - 0.29.0-0ubuntu1
1728076,2017-11-03 17:03:55 UTC,"I looked at our state machine again,  we have the following transitions that end up in Hold, all related to trying to abort a change and its tasks:"
1728076,2017-11-03 18:41:24 UTC,Does that mean the bug Status should be Confirmed?
1728076,2017-12-06 15:55:49 UTC,Should this bug therefore be confirmed?
1728077,2017-10-27 19:29:36 UTC,"Created attachment 135133
Screenshot: filling in text into a field of the form"
1728077,2018-08-28 14:52:04 UTC,"The problem is also reproducible under the latest development version of Ubuntu 18.10 (Cosmic) (version of August 28, 2018). It also uses libpoppler-0.62.0."
1728077,2018-08-28 08:43:35 UTC,The problem still exists under Ubuntu 18.04 (Bionic Beaver). Tested with Evince and Okular.
1728077,2018-08-21 11:09:34 UTC,-- GitLab Migration Automatic Message --
1728077,2017-10-27 19:43:32 UTC,"The PDF form contains a couple of fonts -- some are embedded, some are not -- with a couple of different encodings. May be something in libpoppler goes wrong with the font encoding handling for the form's fields?"
1728077,2017-10-27 19:32:31 UTC,"Created attachment 135135
Screenshot: result after activating another field of the form"
1728077,2017-10-27 19:09:19 UTC,Evince and Okular (based on poppler) uses the wrong encoding when filling out a PDF form.
1728077,2017-10-27 19:18:56 UTC,The upstream bug is at https://bugs.freedesktop.org/show_bug.cgi?id=103492 .
1728077,2017-10-27 16:08:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1728077,2017-10-27 15:35:32 UTC,"The same problem also appears when using Okular instead of Evince. So, it is likely a problem with libpoppler."
1728077,2017-10-27 19:31:43 UTC,"Created attachment 135134
Screenshot: filling in text into a field of the form"
1728078,2017-03-26 07:29:45 UTC,"(In reply to Brad Bell from comment #10)
Here, things work as expected both under Fedora 25 and Fedora 26. To make sure that your actual session type is really ""GNOME on Xorg"", verify that your environment satisfies DESKTOP_SESSION=gnome-xorg, thanks."
1728078,2017-03-25 10:11:12 UTC,"Selecting the gear icon on the login screen, and then Xorg, worked. Thanks."
1728078,2017-10-27 16:09:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1728078,2017-03-24 20:42:39 UTC,"(In reply to Brad Bell from comment #8)
Please make sure that you run a GNOME on Xorg session under Fedora 25. The default session type is GNOME on Wayland now."
1728078,2017-10-30 03:54:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728078,2017-10-30 04:16:17 UTC,"Actually it sounds like in a Wayland world, the individual apps might have to display this information themselves. So that's also an enhancement for Gnome Terminal."
1728078,2017-10-30 03:53:59 UTC,"This feature does exist if you log into ""Ubuntu on Xorg"". Strange it's missing in Wayland logins..."
1728078,2017-03-24 15:09:12 UTC,"I am not sure if this is the same bug, but it appears to be closely related:"
1728078,2017-02-02 10:02:03 UTC,"(In reply to H.J. Lu from comment #6)
Issue appears to have been resolved for both of current Fedora 24 and Fedora 25 with the standard setup of GDM (running on top of Wayland). I have checked for Fedora 24 running inside a virtual machine:
- window geometry is shown when choosing GNOME on Xorg session.
- window geometry is not shown  GNOME (on Wayland) session.
For Fedora 25, the issue is gone both when running on bare metal and inside a virtual machine."
1728078,2017-02-01 21:49:20 UTC,"It is caused by Wayland.  After changing /etc/gdm/custom.conf to use
Xorg:"
1728078,2016-07-29 11:30:07 UTC,"Presently, I have two F24 systems which I upgraded from F22. In F22, I got correct dimensions displayed for all windows when resizing, on both systems. (gnome-terminal and gvim showed columns and rows, everything else showed width and height in pixels.)"
1728078,2016-07-29 11:25:51 UTC,Partial duplicate of Bug 1349688.
1728078,2016-07-28 23:23:27 UTC,"I'm seeing this on F24 with all windows, not just gnome-terminal."
1728078,2016-06-27 16:49:07 UTC,*** Bug 1350506 has been marked as a duplicate of this bug. ***
1728078,2016-02-24 14:28:30 UTC,"This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'."
1728078,2016-02-10 12:37:43 UTC,"Description of problem:
When resizing a gnome-terminal window in a GNOME on Xorg session, the familiar tooltip in the center of the window which displays the window dimensions is missing."
1728087,2017-11-01 14:02:30 UTC,Copy / Paste has never been implemented - it's till on my personal wishlist too. SDL has a function for it.
1728087,2019-09-17 10:14:06 UTC,Migrated to https://github.com/widelands/widelands/issues/2084
1728088,2018-02-23 11:30:44 UTC,The port is deleted:
1728088,2018-02-23 11:28:21 UTC,This is still being seen: we receive notifications about port status up/down after the port was deleted. I think we cannot guarantee the order in which we can receive notifications so logging this warning is enough.
1728088,2017-10-30 09:49:00 UTC,"The issue is not that it doesn't exist yet but that it was deleted a few seconds before that error. Actually, in those logs
For some reason, after the port was deleted in both Neutron and OVN, the mech driver receives various events from ovsdbapp that the port has transitioned to down, then to up and then back to down:"
1728088,2017-10-30 10:13:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/516234"
1728088,2017-11-01 15:39:05 UTC,"Reviewed:  https://review.openstack.org/516234
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=0dc42f3002f18c2572fc6949ac0b58b262128e15
Submitter: Zuul
Branch:    master"
1728089,2017-12-07 16:22:45 UTC,"Perhaps this goes without saying, but this bug affects those of us still using the xul staff client in 2.12 as well."
1728091,2017-10-27 16:34:25 UTC,"This project is currently not managed by the Puppet OpenStack team, I have added the Midonet Drivers team to see what's the best decision foro this."
1728093,2020-05-06 17:55:34 UTC,"After many hours of tinkering around, I made the headset with microphone to be fully recognized and working on Dell Latitude 7389! The combination was to set pin 0x21 to ""Headphones"" as Jeff metioned using hdajackretask. Then, setting the ALSA config to model ""alc256-asus-mic"" adding ""options snd-hda-intel model=alc256-asus-mic"" to /etc/modeprobe/alsa-base.conf. Unfortunately, this brakes the internal mic support, which was previously working... Hope someone finds a way to make both things work at the same time."
1728093,2020-05-07 08:13:36 UTC,Would be worth reporting to upstream alsa
1728093,2020-05-06 16:11:24 UTC,"I can confirm this still occurs in Ubuntu 20.04 on my Dell Latitude 7389 (also using ALC3253).
On a fresh install, the audio jack does not even recognize when a headset is connected at all. After following Jeff Conner suggestion on comment #5, it now recognizes them and sound output works as expected. However, mic of the headset is NOT working. I've tried a lot of combinations on hdajackretask unsucessfully. This is really a big issue for me, as headset usage is important on my daily work. I'm willing to help debbuging or anything to help make it work."
1728093,2020-07-29 00:02:07 UTC,"I tried many combinations of snd-hda-intel models and hdajackretask settings. The following fixed the problem in my Dell Latitude 7389 with Mint 19.3 and kernel 5.4.0. Now, when I plug my headset, I have two working mics (internal and headset) and the output changes to headphone."
1728093,2018-03-21 03:34:14 UTC,"I had a similar problem with my Dell Latitude 5289 using Ubuntu 17.10. After trying different things, I got it to work by using hdajackretask. I got a clue from norteo on this thread:"
1728093,2017-11-19 15:44:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728093,2019-05-14 16:22:44 UTC,"@Jeff Conner (aodhlaidir): Thanks a lot for that workaround! Did you (or anyone else) figure out how to get the audio jack to recognize a headset's microphone as well? I tried many combinations of overrides in HDAJackRetask, but nothing made headset mic work."
1728106,2017-10-27 17:30:54 UTC,"Final message after upgrading :
dpkg: des problèmes de dépendances empêchent la configuration de kubuntu-desktop :
 kubuntu-desktop dépend de xorg ; cependant :
  Le paquet xorg n'est pas installé."
1728106,2017-10-27 17:58:25 UTC,"At restart, unable to login : I can't type a key in the password field (no keyboard !)"
1728107,2018-11-15 20:17:21 UTC,"> From my testing with an avahi service file for the 8710 it seems to me that LP
> #1797501 is involved:
"
1728107,2018-11-09 13:32:56 UTC,From my testing with an avahi service file for the 8710 it seems to me that LP #1797501 is involved:
1728107,2017-12-01 18:52:04 UTC,"Hello,"
1728107,2017-11-21 18:54:21 UTC,"Hello Afshan, thank you for the response."
1728107,2017-11-21 11:52:02 UTC,"Hi Brian,"
1728107,2017-11-22 18:36:47 UTC,"Hi,"
1728110,2017-12-19 21:54:39 UTC,"Suggest handling this by setting XDG_CONFIG_HOME or HOME in the environment of the tests, pointing to a pristine directory."
1728111,2017-11-15 16:24:26 UTC,"Can Juju also document the assurances made for leadership election, when/why it is determined to be changed, etc?  This would be helpful documentation for charm authors to reference."
1728111,2017-11-07 03:59:07 UTC,I'm going to mark the Juju task invalid for now then based on John's comments above.
1728111,2017-11-15 16:20:07 UTC,"Setting Juju bug back to New; we can improve the charm but leader switching mid hook execution makes writing charms harder, so we should see if things can be improved."
1728111,2017-11-15 16:22:32 UTC,Agree with James.
1728111,2017-11-15 17:44:05 UTC,"It is taking you 2.5min to go from ""is_leader"" until we get to
""leader_set"". If it is taking that long, your system is under enough load
that we apparently are unable to guarantee keep-alives. (We need a refresh
of leadership which is done by the unit agent every 30s that extends the
leadership for another 1 minute.)
I don't know what exactly is causing it to take 2.5min, but if we can't get
a network request 1/minute then we would allow leadership to lapse."
1728111,2017-11-20 20:20:56 UTC,"I think a key thing to note here is the term ""guarantee"". I think I may have been taking too hard a line with guarantee."
1728111,2017-11-19 12:21:28 UTC,"I'm not sure that there is a logic bug in Juju, but we should understand what is going on in the system that is causing us to not refresh leadership correctly. I think the discussion around leader-elected is still relevant."
1728111,2017-11-19 13:50:43 UTC,"Could we provide a guarantee that no unit of a given application will ever consider itself a leader until a previous leader has been deposed in apiserver's view? Likewise, an apiserver should not give any leader tokens until it receives a confirmation that the previous leader has been deposed and ran that hook."
1728111,2017-11-20 09:13:26 UTC,This behavior is critical for us.
1728111,2017-11-20 19:48:29 UTC,A key problem we have here is that Juju really can't give any guarantees. I spent some time last week talking with Ryan about what Juju can and can't say at any particular point in time.
1728111,2017-10-31 11:14:45 UTC,"I think the recommendation in #15 to implement the leader-elected hook, and deal with anything missing at that point in time makes alot of sense."
1728111,2017-11-15 19:05:28 UTC,"Sorry, it's a long message but I've got meaningful stuff there (I think)."
1728111,2017-10-31 11:05:23 UTC,"Looking at the charm: https://jujucharms.com/percona-cluster/
It does have a symlink of ""leader-elected => percona_hooks.py""
but the Python code itself is hitting this line:
    try:
        hooks.execute(sys.argv)
    except UnregisteredHookError as e:
        log('Unknown hook {} - skipping.'.format(e))"
1728111,2017-11-21 07:13:01 UTC,"Tim,"
1728111,2017-10-31 08:26:37 UTC,"Side note, we do potentially have a serious issue about responding to relation data and coordination of leadership. Our statement that we guarantee you will have no more than 1 leader at any given time doesn't work well with arbitrary hooks in response to relation data changes.
Here is an example timeline:"
1728111,2017-10-31 09:49:50 UTC,"The logs show that leader-elected isn't implemented, which probably means that you can suffer from comment #13:
2017-10-27 16:35:31 INFO juju-log Unknown hook leader-elected - skipping."
1728111,2017-10-30 17:08:46 UTC,Looking at the mysql log data:
1728111,2017-10-30 17:13:14 UTC,and at the point where mysql/2 tried to write to leader storage:
1728111,2017-10-30 17:18:27 UTC,tl;dr leadership changed during the seeding of the passwords (so between a call to is-leader and leader-set) which the charm does not currently deal with so the cluster never bootstrapped.
1728111,2017-10-30 17:20:41 UTC,Adding a bug task for juju; this is a pretty small codeblock to have leadership switch between two lines:
1728111,2017-10-30 17:10:45 UTC,Something wonky went on during early unit lifecycle:
1728111,2017-10-30 20:21:01 UTC,Juju need to confirm whether or not we have leadership bouncing between units.
1728111,2017-10-31 03:10:44 UTC,"It would be good to know from the logs how long *we* think it was for those
to lines to execute. On a heavily loaded system I think we've seen things a
spike as high as 45s for a query to execute which chews up most of the
lease time. Also if there was something like a controller restart, etc."
1728111,2017-10-31 03:18:47 UTC,"(This is speculation while on a walk, not while reading through the code)"
1728111,2017-10-31 05:46:55 UTC,"""is-leader"" does refresh. You can see the details here: https://github.com/juju/juju/blob/develop/worker/uniter/runner/context/leader.go#L54."
1728111,2017-10-31 08:16:18 UTC,"So digging through the code we call
func (ctx *leadershipContext) ensureLeader() error {
...
success := ctx.tracker.ClaimLeader().Wait()"
1728111,2017-10-30 17:40:50 UTC,"I think the only way to really control for this error, is wrap every call to leader_set(...) in a try: ... except: as the leadership can change during hook execution.  i.e. even if is_leader() -> True, it's still possible for a later leader_set(...) set to fail.  It's better to catch that failure, and undo any 'leader' things the hook was doing, and then exit the hook, and the new leader unit to perform the leadership actions instead."
1728112,2017-10-27 17:41:41 UTC,"StacktraceTop:
 QList<QPostEvent>::node_copy (src=0x2ac9a28, to=0x7fe3a7681da8, from=0x7fe3972ba028, this=0x1cef150) at ../../include/QtCore/../../src/corelib/tools/qlist.h:401
 QList<QPostEvent>::detach_helper (this=this@entry=0x1cef150, alloc=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qlist.h:711
 QList<QPostEvent>::detach_helper (this=0x1cef150) at ../../include/QtCore/../../src/corelib/tools/qlist.h:725
 QList<QPostEvent>::detach (this=0x1cef150) at ../../include/QtCore/../../src/corelib/tools/qlist.h:139
 QList<QPostEvent>::end (this=0x1cef150) at ../../include/QtCore/../../src/corelib/tools/qlist.h:270"
1728112,2019-11-18 18:13:12 UTC,"Hi Joe,
Thanks for reporting this bug.
Vmpk 0.7.2-1 is now in the focal development release (to become 20.04).
I am not sure exactly how to test vmpk with MusE. Are you able to confirm if this latest version works with MusE without crashing?
Regards,
Ross"
1728112,2020-01-18 04:17:30 UTC,[Expired for vmpk (Ubuntu) because there has been no activity for 60 days.]
1728113,2021-02-09 17:01:54 UTC,"Still an issue on Release 3.6.1.  Making this Contains would be convenient for some situations and would be unlikely to find extraneous results when searching a more complete address: Pine St would find everyone who lives on Pine St, but 1945 Pine St would still find that specific address."
1728115,2018-03-21 00:33:49 UTC,This package has been waiting for testing in Artful for 90 days and is blocking the release of other makedumpfile fixes for Xenial and Artful. Please test this SRU!
1728115,2018-03-26 09:06:37 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1728115,2018-03-26 09:06:27 UTC,This bug was fixed in the package makedumpfile - 1:1.6.1-2ubuntu0.1
1728115,2018-03-21 14:48:07 UTC,"ubuntu@artful:~$ dpkg -s kdump-tools | grep Version
Version: 1:1.6.1-2ubuntu0.1"
1728115,2017-12-14 21:05:39 UTC,"Hello Thadeu, or anyone else affected,"
1728115,2017-11-21 13:24:32 UTC,Built for artful on my ppa.
1728115,2017-12-04 15:09:34 UTC,I don't see this fix in bionic yet. Could anyone first release it there? Stable updates can only be backported if they're present in the devel series.
1728115,2017-12-13 17:36:41 UTC,This bug was fixed in the package makedumpfile - 1:1.6.2-1ubuntu1
1728115,2017-11-08 00:33:05 UTC,"The attachment ""makedumpfile_1.6.1-2ubuntu0.1.diff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1728115,2017-11-07 19:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1728115,2017-10-27 18:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1728120,2017-11-03 02:40:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728120,2018-03-20 20:29:24 UTC,This bug was fixed in the package apparmor - 2.12-4ubuntu1
1728121,2019-10-01 01:41:07 UTC,This is no longer the case. Please open an issue if you see this again.
1728121,2017-10-30 19:51:27 UTC,"On vie, oct 27, 2017 at 3:38 PM, Cory Johns <email address hidden>
wrote:

> Public bug reported:
>
> I got a traceback when trying to release the charm snap from edge to
> beta: https://pastebin.ubuntu.com/25830958/
>
> It turns out that I don't actually have access yet (because my invite
> is
> pending but I never received an email nor can I find a link to the
> invite outside of the email) so it is probably related to it being an
> auth error.
"
1728128,2018-02-08 10:44:50 UTC,"I didn't even know Git would let you do this. In any case, we should probably be catching that exception and ignoring it."
1728128,2018-03-14 14:46:58 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1728132,2017-11-21 18:20:23 UTC,"Please also see the related bug, requesting 5.7:"
1728132,2017-11-30 18:54:12 UTC,This bug was fixed in the package percona-xtradb-cluster-5.6 - 5.6.34-26.19-0ubuntu5
1728132,2017-12-07 18:53:26 UTC,"Hello Ryan, or anyone else affected,"
1728132,2017-11-30 14:10:04 UTC,gcc-6 built binaries pass testing (deployment and tempest openstack tests); proposing binaries built using gcc-6 as a solution to this problem; this does not remove the requirement to move forward with pxc 5.7 built using gcc-7.
1728132,2017-11-30 12:22:26 UTC,I think we need to unblock this in the short term while work happens on 5.7; so I've built PXC packages using gcc-5:
1728132,2017-11-21 22:39:38 UTC,"As a work-around for enabling testing of OpenStack on >= Artful, we can force percona-cluster juju units to a series: xenial.  This will allow everything in the deployment, except for percona-cluster, to be validated on the later series."
1728132,2017-11-21 17:31:17 UTC,"Right now, OpenStack Charm Engineering are unable to test Bionic and Artful OpenStack clouds due to this issue, which puts us at a stand-still in preparing for the next LTS."
1728132,2017-10-27 20:28:15 UTC,Defintely a hard crash:
1728132,2017-11-02 11:10:12 UTC,Marking charm bug task as invalid - this appears to be a gcc-7 type issue.
1728132,2017-11-02 11:08:16 UTC,Hmmm:
1728132,2017-11-02 11:07:25 UTC,UNIV_UNLIKELY is a macro that hints to the compiler - I wonder whether that causes us pain with gcc-7
1728132,2017-11-02 11:04:07 UTC,Reference:
1728132,2017-11-02 11:02:53 UTC,"Looking at the backtrace, signal is being generated in this code block:"
1728132,2017-10-27 20:12:04 UTC,Additional occurrence example w/ artifacts:
1728132,2017-11-14 15:48:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728133,2017-10-27 23:09:19 UTC,"I've discovered that this issue only affects newer dnsmasq versions, and downgrading to version 2.71 will work with the configuration file generated by bifrost."
1728134,2020-09-23 13:28:13 UTC,Initial support has been released with netplan.io 0.100-0ubuntu4
1728134,2020-08-28 13:27:11 UTC,"The netplan implementation is being worked on here:
https://github.com/CanonicalLtd/netplan/pull/154"
1728134,2018-11-02 11:13:27 UTC,"Hi,"
1728134,2018-11-02 11:04:01 UTC,"I do not think that we necessarily need OpenVSwitch support in netplan.io. As daxtens pointed out, OpenVSwitch uses a persistent configuration database and thus does not fit well into the concept of netplan.io anyway."
1728134,2018-07-26 13:38:24 UTC,So it looks like there is no support in networkd for ovs: https://github.com/systemd/systemd/issues/2613
1728134,2018-06-23 06:29:28 UTC,"If it may help, I workaround that issue by declaring the interface with a single random IPv6 link-local address."
1728134,2018-06-21 18:13:44 UTC,So it seems Netplan still lacks OpenvSwitch support _and_ the ability to bring an interface administratively up at server boot. Why is it the default for new installations?
1728134,2018-01-19 09:56:32 UTC,"On the charm, we need to confirm netplan impact/to-dos regarding use of add_ovsbridge_linuxbridge via the charm's data-port (""ovs-bridge:linuxbridge) config option and use case."
1728134,2017-11-10 21:07:03 UTC,We are currently using an undesirable hack to accomplish this.  A cron task:
1728134,2017-11-10 19:05:00 UTC,"It is possible to use Open vSwitch -- after boot, run: ifconfig eno2 up ... Open vSwitch will use its stored configuration and simply carry on as if nothing happened. But there is no way to simply set an interface as administratively up using netplan (or so it seems) and allow Open vSwitch to start up as in previous versions of Ubuntu."
1728134,2017-11-02 10:19:10 UTC,AFAIK the neutron-openvswitch charm does not actually make use of /e/n/i or netplan so marking the charm bug task as incomplete/low pending further clarification of impact onto the neutron-openvswitch charm.
1728134,2017-11-01 16:12:07 UTC,"Fair enough, wanted to make sure focus wasn't focused on the charm or openstack, as neither are used."
1728134,2017-11-01 15:34:40 UTC,"Yes, we want to track this task against the charm and with the tag for other reasons.  That is not to say that the task against netplan is valid/invalid.  Both can be tasked to this bug.  Thank you."
1728134,2017-10-31 20:02:09 UTC,"Ryan, no, I'm sorry, but the tag uosci does not apply to this bug, though it may be a separate additional issue with netplan.  This has nothing to do with charms, juju, or openstack."
1728134,2018-01-19 09:57:21 UTC,Clarity on #7:  It is Bionic-Queens (Netplan only by default) that we need to exercise and assess.
1728139,2018-08-12 14:17:05 UTC,Almost certainly a problem with keymapping in your terminal emulator.  What's your terminal emulator?
1728145,2017-10-28 13:50:11 UTC,"This is a bug in GTK+, just recently fixed in git. For details, see
https://bugzilla.gnome.org/show_bug.cgi?id=789356
https://bugzilla.gnome.org/show_bug.cgi?id=789357"
1728145,2017-10-28 13:50:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728145,2017-11-17 16:06:43 UTC,"Ubuntu has just released libgtk-3-0 3.22.25 as an update to Artful, which I believe should fix this bug."
1728149,2018-04-01 17:05:46 UTC,"18.04 LTS with all updates, bug exists."
1728149,2017-10-31 21:42:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728160,2017-10-27 22:09:16 UTC,"This may dovetail into (per Steve's IRC suggestion) having the Launchpad container images being published in streams, in which case we could just use those."
1728162,2020-04-20 21:40:36 UTC,I updated the sssd documentation in the server guide: https://discourse.ubuntu.com/t/service-sssd/11579
1728164,2017-10-28 01:16:38 UTC,"I expect this is ""stray"" network-online.target.wants/ in livecd-rootfs for the ubuntu-cpc project. I *think* we don't want that to exist by default, and let systemd manage it on its own. ubuntu-cpc has that configuration file in includes.chroot/ that other flavors don't."
1728164,2017-10-30 01:14:24 UTC,"On Fri, Oct 27, 2017 at 8:16 PM, Mathieu Trudel-Lapierre <
<email address hidden>> wrote:"
1728164,2018-02-16 15:28:56 UTC,Supporting removing cloud-init from the image seems like a low priority; am I missing something that makes it more important?
1728166,2018-03-31 20:51:46 UTC,"I confirm. Same bug only on Elementary OS. Tried with Juno packages as well, same behavior: my application window works well but it has an additional ""frame"" with a trasparent background between the real window and the additional one."
1728166,2018-03-31 20:57:05 UTC,Adding additional screenshot with the correct BUG message on the console..
1728166,2018-04-01 19:28:40 UTC,Unfortunately it isn't Gala related.
1728166,2018-04-01 19:29:55 UTC,Attached the screenshot without the error (OpenBox).
1728182,2017-10-28 01:46:21 UTC,See https://bugs.mysql.com/bug.php?id=88271
1728182,2017-10-28 02:11:34 UTC,"After some research, I found that the crash/non-crash difference is in using --sql_mode= for mysqld. Thus, this is a duplicate of MS 88271"
1728182,2018-01-25 08:34:54 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3753
1728183,2017-11-27 14:33:17 UTC,"The rectangleGeometry element requires relative coordinates, and we give it an absolute position. So the clipping object exists, but is not correctly set."
1728183,2017-11-27 13:15:08 UTC,"Confirmed on Windows 7, Inkscape 0.92.2 and Inkscape 0.92+devel (66c5d5def, 2017-11-26)."
1728185,2019-10-19 16:40:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728188,2017-10-30 16:04:42 UTC,Trust store support isn't needed but it's not as easy as removing the patch since the snappy changeset is depending on code changes from the trust store one
1728188,2017-11-02 06:27:20 UTC,I'm working on PulseAudio 11.1 for bionic right now. But it sounds like dropping trust store support won't/shouldn't happen just yet.
1728188,2017-11-03 15:27:11 UTC,"@vanvugt It doesn't sound like that to me at all.  seb128 was just pointing out that the snappy patches depend on the trust-store changes to a degree.  If those dependencies can be isolated, moved to the snappy changeset, and the trust-store dep dropped, then everyone wins."
1728188,2017-11-06 02:13:51 UTC,Sounds good.
1728188,2017-11-15 13:16:48 UTC,@vanvugt Any update on this? We would like to get rid of trust-store as soon as possible and its built-in support in pulseaudio is making things blocked. We need to get rid of trust-store for the boost transition.
1728188,2017-11-16 09:32:50 UTC,Daniel is on holiday for some weeks you better don't block on him there
1728188,2017-11-16 11:34:18 UTC,I'm looking into getting rid of the trust-store integration. If it's trivial enough I might do it myself to get trust-store out of libboost's way. Looking of course to see what changes need to be left for the snappy parts to work.
1728197,2017-10-28 08:36:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1728197,2019-08-21 14:16:39 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1728197,2019-10-21 04:17:41 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1728230,2017-10-28 13:42:29 UTC,Could you clarify which extensions are affected? Potential issues with extensions can have a multitude of very different causes...
1728230,2020-09-09 08:25:49 UTC,"Closing as there has been no response. If this is still an issue, please check if it has been reported here: https://inkscape.org/inbox"
1728231,2017-12-22 21:19:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728231,2017-10-28 13:27:59 UTC,"This is also reported here:
https://github.com/keithgg/puddletag/issues/375"
1728232,2017-10-31 13:57:54 UTC,"thank you for your bug report, that seems a behaviour of the unity launcher rather than from nautilus though"
1728232,2017-10-31 20:18:43 UTC,One member had given an explanation and suggested temporary workaround.
1728232,2017-11-04 19:16:06 UTC,@Sebastien
1728234,2018-03-02 15:35:29 UTC,):
1728235,2017-10-28 14:27:50 UTC,"I just discovered that with the Maj+§ shortcut (Corresponding to °), if I try to insert an equal sign (=), guake opens too."
1728235,2017-10-28 15:29:26 UTC,"I doubt that the keyboard shortcut feature is designed to work with a single character as the shortcut. Try to involve some modifier key, e.g. <Ctrl>, <Alt> or <Super> similarly as the predefined shortcuts."
1728235,2017-11-06 14:30:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1728236,2019-10-26 13:41:31 UTC,"We don't want to include it on the ISO because it pulls quite a few other QT dependencies. However, we should better surface this issue on the documentation."
1728236,2018-11-27 22:26:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728236,2018-08-17 18:41:51 UTC,"It is mentioned in the release notes for 17.04 that an extra installation of qt5-style-plugins is needed, but that may be not easy to find."
1728236,2018-08-15 04:51:30 UTC,"I find it gives a good first impression when people install Qt applications and they look similar to the desktop. Don't know if there is room for it in the ISO, though."
1728236,2018-08-14 12:39:48 UTC,"Should ""qt5-style-plugins"" and its various dependencies be pulled in by default (as recommended package)? At least that is what Ubuntu MATE does."
1728237,2019-11-23 16:50:10 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1728237,2020-01-23 04:19:18 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1728239,2017-10-28 14:52:02 UTC,Graphics Info:
1728239,2017-10-29 22:10:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728239,2018-01-01 07:13:52 UTC,Anything new on it?
1728240,2017-11-01 15:16:46 UTC,"<a href=""https://launchpad.net/~apenner"">Alvin Penner (apenner)</a> I will try to solve it myself before 1803 release."
1728240,2017-11-01 14:59:56 UTC,thanks for the info. I think I'll wait for the next Windows update (probably 1803) before attempting a test.
1728240,2017-11-01 11:34:07 UTC,"<a href=""https://launchpad.net/~apenner"">Alvin Penner (apenner)</a> you can change the display font to ""Microsoft Yahei"" by installing Simplified Chinese Lang Pack. The bug doesn't in the old version of Windows 10. The latest Windows 10 redesigned the Microsoft Yahei font. By now, the bug only appears in inkscape, not in any apps I have installed."
1728240,2017-11-01 10:55:38 UTC,"- am not able to reproduce because I am not able to change the default font on my machine.
- using Microsoft Windows [Version 10.0.15063] Language: English (US)"
1728240,2017-10-31 07:09:32 UTC,This [0020] appears only when I set the default display font to Microsoft Yahei (updated in The latest Fast Ring version of Windows 10). but I've seen no this in other apps.
1728244,2018-10-10 14:25:18 UTC,Would be nice having it on mainline. 😅
1728244,2018-10-10 13:00:32 UTC,"Boris,"
1728244,2018-10-10 10:27:53 UTC,"Hi, Hans/Kai-Heng Feng"
1728244,2018-02-12 08:01:25 UTC,"Created attachment 274123
4.14, 4.15, 4.16... still not working."
1728244,2018-02-06 14:01:50 UTC,just wait 4.16 and see if all hid patches fixed the issue.
1728244,2018-02-06 12:55:47 UTC,"Same problem here on Chuwi LapBook Air
touchpad showing as ALPS0001:00 0911:5288 Touchpad
tried kernels 4.14.14 through 4.15.1 including discussed patches and all no goor on Arch Linux."
1728244,2017-12-22 13:14:13 UTC,"@mogio a guy on the TT forum says that 4.15 did not work for him but rolling back to 4.14.3 did. I'm not sure but I think he's using Ubuntu. 4.14.3 has also been working for me without failure (so far).  Manjaro just released 4.14.5 so I will be upgrading and testing that out soon.
See: https://techtablets.com/forum/topic/how-to-install-antergos-linux-on-the-ezbook-3-pro-v4/page/3/#post-76087"
1728244,2017-11-28 22:57:50 UTC,"Mogio, see this patch. It looks related to your button click problem perhaps: https://patchwork.kernel.org/patch/10070339/"
1728244,2017-11-28 13:06:39 UTC,"@mogio, I just noticed this in your dmesg log.
""random: fast init done""
If it means you have ""fast boot"" enabled in your BIOS you should disable that."
1728244,2017-11-28 11:21:31 UTC,"(In reply to mogio from comment #6)

> Ubuntu 16.04, Jumper ezbook 3 pro V4: patch is not working.
>
> Compiled by myself with this patch 4.14.0-041400 and tried a kernel compiled
> by a more pro user than me (here.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244).
>
> Touchpad is not working. The only semi working kernel is the
> 4.14.0-041400rc7 on mainline. Yes MOVING, Yes doubletap for clic, No buttons.
"
1728244,2017-11-13 20:55:28 UTC,here it is.
1728244,2017-11-13 20:40:43 UTC,"@mogio, you forgot the kernel param ""i2c-hid.dyndbg=+p"""
1728244,2017-11-13 19:39:47 UTC,"Created attachment 260639
dmesg >  dmesg_4.14_patch_i2c_debug"
1728244,2017-11-13 19:38:55 UTC,dmesg >  dmesg 4.14 mainline + released patch + i2c debug kernel param.
1728244,2017-11-13 15:18:48 UTC,@mogio when reporting the problem still exists you should supply the dmesg log. That will help to resolve the problem.
1728244,2017-11-13 10:44:19 UTC,"Ubuntu 16.04, Jumper ezbook 3 pro V4: patch is not working."
1728244,2018-10-11 07:00:45 UTC,"Hello,"
1728244,2018-10-14 11:22:24 UTC,"Hello,"
1728244,2019-01-12 23:55:02 UTC,Try Manjaro with kernel 4.19.xx or LinuxMint latest. There have been various fixes for touchpad in newer kernels.
1728244,2018-10-16 09:36:16 UTC,"Hi, Kai-Heng @kaihengfeng"
1728244,2019-07-05 14:42:11 UTC,"Landed to upstream as commit 807588ac92018, sru-ed to Bionic as 459448830a9b0 and Cosmic as commit 35e4595ea550f in bug 1801931. Disco or newer has it automatically."
1728244,2019-02-26 11:44:55 UTC,"elPraga, please file a new bug report, thanks!"
1728244,2019-02-23 13:47:07 UTC,Has the fix been applied in Cosmic already?
1728244,2019-02-14 16:44:55 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1728244,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1728244,2019-01-15 10:37:28 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1728244,2019-01-13 00:36:33 UTC,Linux Mint uses Ubuntu kernels so it won't work as I have tried newer kernels as well (I'm on Ubuntu 18.04) I haven't tried Manjaro but I have installed Arch free days ago and it didn't work. I guess I will have to stick to that kernel 4.14-rc7 for some time. I might give it a go with Manjaro tho.
1728244,2019-01-12 23:57:23 UTC,I don't know about LinuxMint but you can install Manjaro onto a USB destination drive and boot from that to test it out first/without touching your HDD/SD installation.
1728244,2017-11-13 10:39:24 UTC,"I compiled from source (4.14.0-041400) adding the patch and the touchpad is not working.
I tried @kaihengfeng kernel (4.13.0-17) and the touchpad is not working."
1728244,2019-01-12 23:25:49 UTC,"EZBook 3 Pro v4 Touchpad stil not working. I've tried kernels from comment #187 (v4.15.0-35) and comment #221 (v4.15.0-43.46) and both haven't worked. I have tried to reload modules for both kernels as well as suspending laptop. Nothing helps.
Kernel v4.14-rc7 from comment #3 works correct apart from hard buttons."
1728244,2018-12-20 06:56:34 UTC,"Another Bionic back port here:
https://people.canonical.com/~khfeng/lp1728244/bionic/"
1728244,2018-12-06 08:54:07 UTC,The issue should be fixed by next Bionic kernel. Should be release at January.
1728244,2018-11-10 14:15:58 UTC,"Hello,"
1728244,2018-10-19 21:39:23 UTC,"Hi Kai-Heng @kaihengfeng,"
1728244,2018-10-17 11:52:13 UTC,"Kai-Heng @kaihengfeng,"
1728244,2018-10-17 05:29:32 UTC,"Boris,"
1728244,2018-10-16 11:53:50 UTC,"@elpraga, @kaihengfeng"
1728244,2018-10-14 20:59:43 UTC,"I can now confirm that two finger scrolling is working, and tapping with two fingers works like a charm as the rightclick on Chuwi Lapbook Air."
1728244,2017-11-13 07:45:39 UTC,"This kernel includes the patch:
http://people.canonical.com/~khfeng/lp1728244/"
1728244,2017-12-18 21:47:08 UTC,4.15 is a big no. Latest drm-intel-next 4.15 hasn't the touch-pad movement working. Rolled back to the 4.14...
1728244,2017-11-12 22:18:21 UTC,"There is a potential patch (quirk) for this.  Please test it, if possible:
https://patchwork.kernel.org/patch/10046575/"
1728244,2017-11-11 13:36:48 UTC,apport information
1728244,2017-11-11 13:36:47 UTC,apport information
1728244,2017-11-11 13:36:45 UTC,apport information
1728244,2017-11-11 13:36:44 UTC,"ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
Package: linux (not installed)
Tags:  xenial
Uname: Linux 4.14.0-999-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True"
1728244,2017-11-11 13:32:36 UTC,latests daily has the trackpad not working at all.
1728244,2017-11-07 21:55:28 UTC,"Created attachment 260549
dmesg | grep .hid"
1728244,2017-11-07 20:19:20 UTC,"mich@ezbook:~$ dmesg | grep .hid
[    3.164258] hidraw: raw HID events driver (C) Jiri Kosina
[    4.305905] usbcore: registered new interface driver usbhid
[    4.305907] usbhid: USB HID core driver
[    4.308860] hid-generic 0003:045E:0023.0001: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb-0000:00:15.0-2/input0
[    6.726802] intel-hid INT33D5:00: platform supports 5 button array
[    6.869535] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator
[    6.883919] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[    6.888901] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713)
[    6.891849] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[    6.898604] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334)
[    6.901745] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/20745)
[    6.906804] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/31302)
[    6.909733] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/29952)
[    6.918193] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/22281)
[    7.524580] hid-multitouch 0018:0911:5288.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00
[  102.817373] hid-generic 0003:045E:0023.0003: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb-0000:00:15.0-2/input0
[ 1637.590908] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator
[ 1637.597193] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 1637.599518] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713)
[ 1637.600674] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 1637.604096] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334)
[ 1637.605250] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/20745)
[ 1637.608647] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/31302)
[ 1637.609845] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/29952)
[ 1637.614343] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/22281)
[ 1637.643866] hid-multitouch 0018:0911:5288.0004: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00
mich@ezbook:~$ uname -r
4.14.0-041400rc8-generic"
1728244,2017-11-06 16:26:12 UTC,4.14.0-041400rc8
1728244,2017-11-11 13:41:56 UTC,^ attachd apport. latests daily has the trackpad not working at all.
1728244,2017-11-05 12:13:19 UTC,"xinput attached, same kernel 4.14.0-041400rc7"
1728244,2017-11-04 13:44:49 UTC,"4.14.0-041400rc7 touchpad is working, A lot of tourchpad *i2c_hid i2c-SYNA3602* errors, but it is working."
1728244,2017-11-03 06:24:40 UTC,Can you attach dmesg under v4.14-rc7?
1728244,2017-11-03 00:18:06 UTC,"Ubuntu 17.10, jumper 3 pro v4, kernel 4.13.0-16 still affected. After 10 hours, I give up :D"
1728244,2017-10-31 09:07:44 UTC,Still not fixed. Updated tag.
1728244,2017-10-30 20:12:01 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1728244,2017-10-28 15:19:15 UTC,"Also, I cannot run apport-collect 1728244 right now, but I posted the log file above."
1728244,2017-10-28 15:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1728244,2017-11-13 03:50:03 UTC,Not Working Patch
1728244,2017-11-04 14:09:19 UTC,"p.s. touchpad movement is working, tap for clic is working too but the 2 buttons are not."
1728244,2017-11-11 17:36:18 UTC,"Can you attach dmesg with kernel parameter ""i2c-hid.dyndbg=+p""?"
1728244,2017-11-12 21:21:13 UTC,One or two more people reported the problem here: https://bbs.archlinux.org/viewtopic.php?id=231540
1728244,2017-11-12 00:46:05 UTC,This problem is not specific to Ubuntu.  I get the same problem on the same notebook with Manjaro and Kernel 4.13
1728244,2017-11-12 21:35:00 UTC,"Oh nice! There is a recent patch for this problem as about a week ago.
I've only applied a patch once a long time ago. Gotta go relearn how to do it..."
1728244,2017-11-12 21:20:36 UTC,"OK so it turns out I lied.  It doesn't always work on Antergos either. It seems to happen randomly and how to get it working again is also a mystery.  Resetting BIOS default does not restore it, and neither does booting into Windows - where it's not working there either. I unplugged both the power cable and the USB mouse then just kept restarting it until it mysteriously started working again.
Attached is the full dmesg logs for both working (YES) and not (NO). Here the pertinent parts:"
1728244,2017-11-12 18:25:24 UTC,"Created attachment 260625
partially working touchpad 4.14.0-041400rc7"
1728244,2017-11-12 18:16:45 UTC,"No, sorry, my bad. Too many kernels installed."
1728244,2017-11-12 17:29:01 UTC,"Yes, without refind it doesn't boot, because of GRUB."
1728244,2017-11-12 15:44:23 UTC,"@iBART, is that Ubuntu 16.04 w/4.13.11 with rEFInd?  I'm booting through rEFInd installed on my SSD partion, with my Antergos installed on SSD and Manjaro installed on an external USB drive."
1728244,2017-11-12 15:33:17 UTC,"FYI, the Manjaro dmesg log attached above was from a boot when the touchpad was NOT working."
1728244,2017-11-12 15:25:42 UTC,I tried Ubuntu 16.04 with 4.13.11 and it is not working.
1728244,2017-11-12 15:09:26 UTC,"Always working touchpad >> Antergos kernel: Linux version 4.13.11-1-ARCH
Sometimes not working >>   Manjaro kernel : Linux version 4.12.14-1-MANJARO
Attached are the dmesg logs for both."
1728244,2017-11-11 17:59:42 UTC,here sir.
1728244,2017-11-12 07:11:42 UTC,"> On 12 Nov 2017, at 2:35 PM, Brad <email address hidden> wrote:
>
> Trying it more.  It started working in Manjaro too. Then booting back
> into windows then back to Manjaro it stopped working again. So don't
> know what to make of that.  If I can get it to fail again, I'll post the
> dmesg log. Any other info you need?
"
1728244,2017-11-12 06:35:15 UTC,"Trying it more.  It started working in Manjaro too. Then booting back into windows then back to Manjaro it stopped working again. So don't know what to make of that.  If I can get it to fail again, I'll post the dmesg log. Any other info you need?"
1728244,2017-11-12 06:34:24 UTC,"> On 12 Nov 2017, at 8:49 AM, Brad <email address hidden> wrote:
>
> Antergos 17.09 Gnome works OK. So I know the touchpad is not defective.
> With Manjaro 17.05 Xfce it does not work and I get the same error message
> ""...i2c_hid_get_input: incomplete report…""
"
1728244,2017-11-12 02:35:05 UTC,"(In reply to Brad Baker from comment #2)

> I have the ezbook 3 Pro (v4). With Manjaro Xfce 17.05 the touchpad does not
> work at all, but using Antergos 17.09 the touchpad works perfectly.
"
1728244,2017-11-12 02:32:54 UTC,"I have the ezbook 3 Pro (v4). With Manjaro Xfce 17.05 the touchpad does not work at all, but using Antergos 17.09 the touchpad works perfectly."
1728244,2017-11-12 02:16:35 UTC,"If this helps, Attached is my dmesg output with boot param i2c-hid.dyndbg=+p on my notebook with Antergos installed and the touchpad working perfectly."
1728244,2017-11-12 00:49:11 UTC,"Antergos 17.09 Gnome works OK. So I know the touchpad is not defective.
With Manjaro 17.05 Xfce it does not work and I get the same error message
""...i2c_hid_get_input: incomplete report..."""
1728247,2017-10-28 15:25:40 UTC,"StacktraceTop:
 g_settings_schema_get_value (schema=0x15eaed0, key=0x1591d80 ""other-monitors-logo"") at ../../../../gio/gsettingsschema.c:967
 g_settings_schema_key_init (key=key@entry=0x7ffde0e782b0, schema=0x15eaed0, name=name@entry=0x1591d80 ""other-monitors-logo"") at ../../../../gio/gsettingsschema.c:1246
 g_settings_get_value (settings=0x14f9970, key=0x1591d80 ""other-monitors-logo"") at ../../../../gio/gsettings.c:1203
 g_settings_get_string (settings=<optimized out>, key=<optimized out>) at ../../../../gio/gsettings.c:1787
 ffi_call_unix64 () at ../src/x86/unix64.S:76"
1728247,2020-03-06 10:34:30 UTC,Closing since this is an end-of-release release.  If this can be reproduced under a supported version release then please re-raise
1728250,2017-11-04 02:05:24 UTC,"Other think that I thought that could help this is, the others EDA softwares deal with the power pin as just a graphical object (not in the components libraries) that set the wire net name."
1728252,2019-07-17 06:44:29 UTC,I would propose a more general approach here:
1728252,2019-10-13 15:19:17 UTC,"This would be a nice feature, but I would like to propose something like the output job file approach in Altium Designer, with the addition of making zip files:"
1728252,2019-10-13 16:07:31 UTC,"Yes, I good interface to automate: Gerbers + PDF schematic + some PCB layer (mechanical are usual to assembly parts) + 3D + position file + BOM (call to rum some specific BOM plugin)
And all this save in some configuration ""production configuration file"" will be nice."
1728252,2019-10-13 17:00:11 UTC,"I guess such a tool needs information from (at least) both the PCB and the schematic, so i think it needs to be an external program that drives the output generators from the other programs in the KiCAD suite."
1728252,2019-10-13 17:12:52 UTC,"I was thinking exactly on this, also thinking to integrate in some other package that I already use but Eeschema doesn't have Python API lp:1728258"
1728252,2019-10-13 19:44:28 UTC,"I believe that plot management support for Pcbnew has already been requested in another bug report.  As far as I can remember, this did not include support for schematic information.  If this request is for Pcbnew plot support only, than it most likely is a duplicate."
1728255,2017-10-28 20:57:24 UTC,IMPORTANT INFORMATION:
1728256,2018-03-30 18:53:21 UTC,Got similar behavior with windows server 2012r2 VMs.
1728256,2018-03-30 18:36:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728256,2017-11-21 21:21:02 UTC,I just reported the bug in the kernel: https://bugzilla.kernel.org/show_bug.cgi?id=197951
1728256,2017-11-21 21:09:20 UTC,"I have yet to try disabling swap, but in the 5 days since I downgraded the kernel to 4.12.12 from 4.12.13, I have not had a single BSOD. I think 4.12.13 is the culprit."
1728256,2017-11-21 20:53:02 UTC,"I am on Arch as well, using a customized kernel using the vfio patchset (in this case 4.13.11). I was having the same issue as you guys, where my Windows 10 VM with an NVIDIA card passed in was getting the CRITICAL_STRUCTURE_CORRUPTION blue screen error message after running for a while. Usually I saw this when hitting some form of memory (GPU or system RAM), and it was quick (~3 hours) to crash while mining on the GPU (as that hits the GPU memory hard)."
1728256,2017-11-15 14:07:28 UTC,I've also had the exact symptoms and issues you've described. I have also noticed that the VM would BSOD with the CRITICAL_STRUCTURE_CORRUPTION message when the host system would read VM memory from swap.
1728256,2017-11-16 05:17:45 UTC,"I'm experiencing this BSOD issue as well. I'm also on Arch x64, and the same versions of everything (though not minimal qemu--just the normal package in the main repos). I also passthru a GPU and a USB card, but not an SSD. It will happen randomly, anytime, at least once a day, and it seems like demanding games make it much more frequent. Since you're on btrfs, I'll see what happens if I downgrade the kernel to 4.12. If that doesn't work, I guess I'll try to confirm the swapoff fix, but my host only gets 4GB of RAM when the VM is running, so no swap would hurt real bad."
1728256,2017-11-14 20:47:30 UTC,"It happened again, both with the e1000 and the rtl8139 NICs under qemu 2.11.0.rc0-7-g4ffa88c99c. Kernel is the official Arch one, right now on 4.13.12."
1728256,2017-11-06 19:36:47 UTC,"Unfortunately I have bad news, but I also have (kind of) good news.
Bad news is, 2.9 is NOT stable, contrary to what I believed earlier.
Good news is, I found a correlation between the crashes and converting large video files on an SMB share with ffmpeg, so effectively copying slowly with simultaneously high CPU load. In that constellation it crashed a few times after just hours (instead of days sometimes). I suspect it might be a network related issue. I am now testing the different virtual network hardware that qemu supports (which proved to be difficult due to lack of driver support in Windows)."
1728256,2017-11-05 19:36:10 UTC,"I have a similar setup to yours, running on Ubuntu 17.10 Artful. Symptoms are the same. Did you find out what's wrong with 2.10? (Haven't tested 2.9 here)"
1728256,2017-11-16 05:22:26 UTC,"Specifically 4.12.12, because it seems that was the last version I was running before this issue started (I was on 4.12.13 when it started). I, too, can't find any other package upgrade that could have possibly been the culprit. The timing of my upgrades of any qemu or libvirt packages rule them out."
1728260,2018-05-31 00:54:28 UTC,"https://www.youtube.com/watch?v=IIVr22D8Yzw
at 49s"
1728265,2020-11-12 23:09:34 UTC,The ability to reorder Crates would also be very handy.
1728272,2019-02-25 14:40:38 UTC,"@Hildo you will not need to compile, you need to follow the instructions for advanced config  in the ""Developing/Testing"" documentation: http://docs.kicad-pcb.org/doxygen/md_Documentation_development_testing.html"
1728272,2019-02-25 14:33:57 UTC,Some bug admin here:
1728272,2019-02-25 14:17:53 UTC,"@Nick, do I have to compile by my self? (enabling some `advanced_config`)
Will it be not present at Nightly by default?"
1728272,2019-02-25 13:55:39 UTC,Fwiw this has been merged and can experimentally be tested with the advanced_config.
1728272,2018-11-23 07:42:20 UTC,"Jean-Pierre has done an excellent work rebasing the branch, but I guess it will be merged in the 6.0 development branch."
1728272,2018-12-27 14:19:17 UTC,"Same tool should be useful at ""page layout editor"" and ""Eeschema""."
1728272,2018-10-11 20:31:08 UTC,"@Orson, do you know if the branch will be rebased against master now that we have tagged 5.0.1? I would like to test this."
1728272,2018-10-11 21:36:18 UTC,"If the SVG store need some file format modification (or add of some parameters) we have to postpone.
The Eeschema file already have a `$Bitmap` tag (not a SVG) but, so far I internally studied the PcbNew files don't."
1728272,2017-10-30 09:45:27 UTC,This feature is partially implemented [1] in another branch. It needs to be finished and tested before merging.
1728272,2018-02-13 08:54:01 UTC,"There is a branch that adds SVG import [1], but most likely needs a lot of rebasing and testing."
1728272,2017-11-03 16:28:46 UTC,"I was think the feature more like in this video
https://www.youtube.com/watch?v=tc1NmWeX_yc"
1728275,2018-07-30 22:57:57 UTC,"Save the results as a binary file format on the project folder and refer it on the new Eeschema file format.
May need some change on the file format."
1728275,2018-09-20 23:56:20 UTC,"Sorry, last comment mine was a mistake posted from other issue."
1728275,2019-08-07 14:12:27 UTC,"+1 on this. Often happens also to me  to be in the need to ""squeeze"" some parts into a hierarchical sheet of a growing schematic."
1728280,2018-01-08 00:39:56 UTC,"Same bug but with a different cause
seems to be triggered by mintmenu applet faults and error handling"
1728280,2018-01-08 01:13:05 UTC,"Release Linux Mint 18 Sarah 64-bit
Kernel Linux 4.4.0-104-generic x86_64
MATE 1.14.1"
1728282,2017-10-28 19:11:57 UTC,forget to say that happens with any source.
1728290,2018-01-28 01:25:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728290,2018-04-06 16:12:17 UTC,Error occurs on every reboot
1728293,2018-04-10 14:26:58 UTC,Confirmed on Windows 7
1728299,2017-10-28 23:35:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728303,2017-11-28 09:26:29 UTC,"I have been busy for the past month, but I finally got around to try it out. Here are the results and answers to @jsalisbury's questions:"
1728303,2017-10-30 20:15:01 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1728303,2017-10-28 21:30:09 UTC,This change was made by a bot.
1728312,2017-10-29 03:36:21 UTC,Ach. I think I reported this in the wrong place.
1728312,2017-10-29 01:52:19 UTC,This is a log of debug output when Terminator failed to become transparent.
1728313,2017-10-30 04:00:07 UTC,This change was made by a bot.
1728313,2017-10-30 03:45:31 UTC,"Thanks, that's a nicely detailed bug report."
1728321,2017-11-01 18:45:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728325,2017-10-31 09:35:55 UTC,This is buggy C.
1728325,2017-10-31 10:38:05 UTC,The original code used a union.  It generates the same assembler all the same.
1728325,2020-11-10 03:11:39 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1728325,2021-01-09 04:17:56 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1728325,2017-10-29 01:15:46 UTC,I am running:
1728330,2017-10-30 15:49:14 UTC,"Hello,"
1728331,2018-02-20 20:30:26 UTC,It took ages but I eventually shook loose a tuit or two and this branch appeared: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1728331-a-t-aggregator-date
1728331,2019-09-06 21:46:22 UTC,"Pushed to master for inclusion in 3.4. Thanks, Jason and Josh!"
1728331,2019-02-27 17:08:25 UTC,"Here is a branch with my signoff.  I tested out the script with production data and it worked as described.   I also moved the script over to being processed by the makefile to set the confdir, just in case a custom one gets used.  And the script will now also get installed in the bin dir by default for installs.  I also added a note about the script to the support scripts docs."
1728331,2019-02-27 14:41:32 UTC,"I can see this feature being useful to have.  I'll test this out and write release notes.
Josh"
1728331,2018-04-02 19:18:06 UTC,"er, ""Confirmed"" rather."
1728331,2017-10-30 14:14:44 UTC,I'd prefer a --date (or better yet --duration) option to appending a day to --end-date.
1728331,2018-04-02 19:17:35 UTC,"I'd vote for this as a future feature, as written.  Putting it back to whishlist."
1728331,2018-04-02 14:41:30 UTC,"There were apparently some local issues causing me to have such trouble with this, so given the lack of interest at other sites and the fact that I've got my local issues sorted without using this patch, I'm going to mark the bug as wontfix for now."
1728336,2019-01-11 16:27:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728342,2017-11-07 02:41:29 UTC,Sounds like this might be tied to apps that disable the screensaver...?
1728342,2017-11-06 14:29:56 UTC,"gnome-control-center is only a configuration interface and not an active service, it seems the issue there has probably to do with gnome-shell itself. Could be that a problem with the compositor giving direct rendering to those softwares and not going back to the right mode again later on. In any case sounds like an upstream issue"
1728342,2017-11-06 14:28:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1728342,2018-08-09 01:58:42 UTC,"Or D55/D50 rather, in Settings > Devices > Colour"
1728342,2018-08-09 01:49:33 UTC,"That's true. Another free alternative is to look in Settings and install a ""warmer"" colour profile like ""D65""."
1728342,2019-11-23 14:57:36 UTC,Confirmed on my Ubuntu 18.04.3 to
1728342,2019-06-08 12:34:14 UTC,It happens on Ubuntu 19.04 as well
1728342,2018-09-01 20:50:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728342,2018-08-08 08:19:02 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1728342,2018-08-08 22:10:12 UTC,I can confirm this still happens on Ubuntu 18.04 and suggesting to buy a colorometer to tune the display temperature is like suggesting someone to get a car when their bike has a flat.
1728343,2017-10-29 05:41:42 UTC,"StacktraceTop:
 g_datalist_id_dup_data (datalist=datalist@entry=0x5573f34b6410, key_id=54, dup_func=dup_func@entry=0x0, user_data=user_data@entry=0x0) at ../../../../glib/gdataset.c:858
 g_datalist_id_get_data (datalist=datalist@entry=0x5573f34b6410, key_id=<optimized out>) at ../../../../glib/gdataset.c:798
 g_object_unref (_object=0x5573f34b6400) at ../../../../gobject/gobject.c:3260
 gtk_css_value_image_free (value=0x5573f6573720) at ././gtk/gtkcssimagevalue.c:32
 gtk_css_static_style_dispose (object=0x5573f7147c70) at ././gtk/gtkcssstaticstyle.c:81"
1728347,2018-03-25 17:34:08 UTC,akregator (4:17.04.3-0ubuntu1.1) tested. 2 times corrupted opml files after reboot system.
1728347,2018-01-21 04:06:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728347,2017-10-29 07:09:06 UTC,"This bug fixed in upstream.
https://commits.kde.org/akregator/d0a5f4159cddcca656ca8bbcbd6e551e3499c166"
1728347,2018-03-21 14:01:46 UTC,"Hello wens, or anyone else affected,"
1728347,2018-03-19 03:31:52 UTC,"Bionic ships with a fixed version, Artful does not."
1728347,2018-03-19 03:48:08 UTC,Uploaded.
1728353,2017-10-29 11:14:38 UTC,"repeated with LiveCD, the error appears consistently"
1728353,2017-10-29 09:36:36 UTC,"continuation of a story
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1547224"
1728354,2018-10-25 07:59:30 UTC,"> but all files are not valid
"
1728354,2018-10-29 06:30:22 UTC,"Chiming in with some answers in the last document:
* running Windows 10 latest (retracted) update (I got it somehow)
* Debian/unstable
* ntfs-3g 1:2017.3.23-2
* files should be all available offline (not on-demand)
```
# ls -l /usr/lib/x86_64-linux-gnu/ntfs-3g/
total 60
-rwxr-xr-x 1 root root 16680 Oct 29 15:16 ntfs-plugin-80000013.so
-rwxr-xr-x 1 root root 21562 Oct 29 15:16 ntfs-plugin-80000017.so
-rwxr-xr-x 1 root root  7202 Oct 29 15:08 ntfs-plugin-9000301a.so
lrwxrwxrwx 1 root root    23 Oct 29 15:12 ntfs-plugin-9000601a.so -> ntfs-plugin-9000301a.so
lrwxrwxrwx 1 root root    23 Oct 29 15:12 ntfs-plugin-9000701a.so -> ntfs-plugin-9000301a.so
```"
1728354,2018-10-29 10:07:38 UTC,"> Chiming in with some answers in the last document
"
1728354,2018-10-29 14:12:46 UTC,"Hi Jean-Pierre,
thanks for your quick response.
I realized that I was not completely correct with what I wrote. I had the files on the local drive *I*BELIEVE*, but checking the settings of OneDrive I saw that the option ""Save Space blabla on demand"" was turned on."
1728354,2018-10-29 17:29:48 UTC,"> To my surprise, I could still read all the files.
"
1728354,2018-10-30 00:30:11 UTC,"Hi Jean-Pierre,
I'll see whether it comes up again, and if yes, I'll not play around to fix it but try to send all the infos you need."
1728354,2018-10-30 08:57:15 UTC,"> Do you think this version is insufficient, and if yes, in which respect?
"
1728354,2019-10-08 14:33:35 UTC,"Hello
I discovered this problem after trying to duplicate the contents of the windows partition
with the RSYNC command"
1728354,2017-11-01 16:21:45 UTC,"> configure complains that libntfs-3g is not new enough: libntfs-3g >= 2017.3.23,
"
1728354,2017-10-29 21:30:37 UTC,"Reparse points are a way to trigger some specific processing when accessing a file. For instance a reparse point can be used to define a new patch to the file or directory, which ntfs-3g emulates as a symbolic link."
1728354,2017-12-20 21:32:13 UTC,fenris@X240:~$ ntfs-3g --help
1728354,2017-12-20 21:42:52 UTC,"fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1/src/.libs$ strings ntfs-3g | grep ntfs-plugin
/usr/local/lib/ntfs-3g/ntfs-plugin-%08lx.so"
1728354,2017-12-21 07:57:20 UTC,"> fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1/src/.libs$ strings ntfs-3g | grep ntfs-plugin
"
1728354,2017-12-21 15:50:29 UTC,"> > fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1/src/.libs$
> strings ntfs-3g | grep ntfs-plugin
>
> In the above command, you are examining what you have compiled, but the
> meaningful file is the one you are executing, and this is still not
> clear to me as your posts come from different situations.
>
> Well, I have to check everything you did...
>
> 1) please post the ntfsinfo for the OneDrive directory :
> sudo ntfsinfo -fvF /Users/fenris/OneDrive /dev/sdxx
> (replace sdxx by the partition name, like sda1)
"
1728354,2017-12-21 16:00:29 UTC,"Sorry, its was my mail client with html. Resent as below:"
1728354,2017-12-21 17:34:46 UTC,"> fenris@X240:~$ sudo ntfsinfo -fvF /media/fenris/746A024C6A020C14/Users/fenris/OneDrive /dev/sda2
"
1728354,2017-12-21 20:46:05 UTC,"fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ mkdir win
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ ls -l src/ntfs-3g
-rwxr-xr-x 1 fenris fenris 6279 Dec 19 21:33 src/ntfs-3g
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ sudo src/ntfs-3g -o ro /dev/sda2 win
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ ls -lo win/Users/fenris/OneDrive
ls: cannot access 'win/Users/fenris/OneDrive': Input/output error"
1728354,2017-12-21 21:30:29 UTC,"> ntfsinfo as per attached ntfsinfo.txt
"
1728354,2017-12-22 08:04:10 UTC,"> fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ ls -lo win/Users/fenris/OneDrive
> ls: cannot access 'win/Users/fenris/OneDrive': Input/output error
"
1728354,2017-12-22 09:39:20 UTC,"I have uploaded an update plugin version to
http://jp-andre.pagesperso-orange.fr/onedrive101-beta.zip
As this is experimental, only use it in read-only situations. It is quite possible that you have no file copy locally (they would only be in the cloud), in which case there is no much hope you could access them through ntfs-3g."
1728354,2017-12-22 16:35:31 UTC,"fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ sudo src/ntfs-3g -o ro /dev/sda2 win
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ ls -ldi win/Users/
660673 drwxrwxrwx 1 root root 4096 Oct 20 09:26 win/Users/
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ ls -ldi win/Users/fenris/
345397 drwxrwxrwx 1 root root 16384 Dec  4 13:55 win/Users/fenris/
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ sudo umount /dev/sda2
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ sudo src/lowntfs-3g -o ro /dev/sda2 win
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ ls -ldi win/Users
660673 drwxrwxrwx 1 root root 4096 Oct 20 09:26 win/Users
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ ls -ldi win/Users/fenris
345397 drwxrwxrwx 1 root root 16384 Dec  4 13:55 win/Users/fenris
fenris@X240:~/Downloads/ntfs-3g_ntfsprogs-2017.3.23AR.1$ ls -ldi win/Users/fenris/OneDrive
ls: cannot read symbolic link 'win/Users/fenris/OneDrive': Operation not supported
88997 lrwxrwxrwx 1 root root 25 Dec 21 23:19 win/Users/fenris/OneDrive"
1728354,2017-12-22 16:49:25 UTC,"after i tried #47, i managed to get OneDrive content listed  ... \0/ but still in read-only"
1728354,2017-12-19 17:39:27 UTC,"So, you have compiled ntfs-3g 2017.3.23AR.1, but probably without using the Ubuntu recommended configure options. Hence the plugins are expected in a default directory, not the one defined by Ubuntu."
1728354,2018-01-04 15:17:09 UTC,"hi Jean, any new advise / feedback you can share based on my feedback .. thanks & Happy New Year :)"
1728354,2018-01-19 16:58:03 UTC,"hi Jean,
I've tried to installed the debian package experimental. The result/output are remained the same."
1728354,2018-01-19 17:11:20 UTC,I found another sync software also having the same problem with win 10 reparse point - https://github.com/syncthing/syncthing/issues/4542
1728354,2018-01-20 07:18:58 UTC,"> I've tried to installed the debian package experimental.
"
1728354,2018-08-10 13:03:38 UTC,"Hi.
I've already install ALL ntfs-3g plugins. But many errors exists.
I've load Windows 10 now, and I can't write errors log to you now.
It's something like that:"
1728354,2018-08-11 07:11:00 UTC,"> ...something file C:\Program Files\internet explorer\xxx.dat is
> bigger than 64k... oper_save.c###. xxx.dat is 65k... and more
> and more like that...
"
1728354,2018-08-11 18:05:22 UTC,"> To backup a Windows system partition you should use a program which takes an image of it
Can you say me what the program is it? What is her name?
"
1728354,2018-08-11 18:13:42 UTC,"> sudo ntfsinfo -fv -F ""/Program Files/internet explorer/xxx.dat"" /dev/sdxx
"
1728354,2018-08-11 20:42:44 UTC,"This file is ""system compressed"", so you need the systcomp plugin to read it. It is a system dll which has three symlinks and a short name, and it also has an integrity tag."
1728354,2018-08-12 05:09:26 UTC,"> This file is ""system compressed"", so you need the systcomp plugin to read it.
Already installed.
"
1728354,2018-08-12 06:19:53 UTC,">> Which error do you get when you copy this file by a regular cp command ?
> There is no errors. Copying of this file is successfull. But FSArchiver can't save all files. The full log above.
"
1728354,2018-08-12 12:39:33 UTC,"> but saving individual Windows system files is not the way to go.
You want to say what I can't use FSarchiver backup program for making backup of my Windows 10 system and be better to use partimage for this action?
"
1728354,2018-10-07 17:55:56 UTC,any update or progress?
1728354,2018-01-04 17:38:01 UTC,"> any new advise / feedback you can share based on my feedback
You are the only user I know, having a double level of reparse points, so the only feedback I can give now has to come from you.
"
1728354,2017-12-19 16:31:59 UTC,"fenris@X240:~$ ls /usr/lib/x86_64-linux-gnu/ntfs-3g/
ntfs-plugin-9000301a.so
fenris@X240:~$ ntfs-3g --help"
1728354,2017-12-19 15:03:49 UTC,"> I've tried to follow #4
> getting confuse with ntfs-plugin-80000017.so
"
1728354,2017-12-19 14:11:22 UTC,"I've tried to follow #4 , its doesn't working. I also tried to replace the package binary:"
1728354,2017-11-01 09:08:08 UTC,"Hello Jean-Pierre, thank you for time analyzing the ntfs issue."
1728354,2018-10-25 02:29:44 UTC,"and here's the plugin info
strings $(which ntfs-3g) | grep ntfs-plugin
/usr/local/lib/ntfs-3g/ntfs-plugin-%08lx.so"
1728354,2017-11-02 08:12:11 UTC,"Hello Jean-Pierre,
installing the plugin from http://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g.html#download and installing it at the correct place did the trick! Thank you. You might consider this solution for general availability, since more and more people will have to face WIndows-10, if they want to face it at all. You may close this bug report."
1728354,2017-11-08 20:32:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728354,2017-11-08 20:43:07 UTC,I am running into the same error message. In my case it's when I try to access the OneDrive folder from linux:
1728354,2017-11-09 07:27:57 UTC,"> Case $ReparseType = '0x9000301A'
>     Return 'CLOUD_ROOT_ON_DEMAND'
> So it might be a new type of reparse point, specific for OneDrive.
"
1728354,2017-11-09 16:52:21 UTC,"I've tried to run ls on the folder on Ubuntu bash on Windows 10, and in this case it works well.
The version is even an old one (1:2013.1.13.AR.1-2ubuntu2)."
1728354,2017-11-09 20:45:51 UTC,"> I've tried to run ls on the folder on Ubuntu bash on Windows 10
"
1728354,2017-11-09 22:58:09 UTC,"This coincides with addition of on-demand files (like in windows 8 onedrive). One, obvious, solution is to roll back to Windows 10 build 17.03 or earlier (where such feature is not present) but at some point security support will end."
1728354,2017-11-10 08:29:24 UTC,Would you please do the following :
1728354,2017-11-10 21:27:54 UTC,"Same for me, I am not using on demand files.
But after following your steps I could list the files in the folder!"
1728354,2017-11-13 23:01:57 UTC,"Following your post, I was able to list and access files in my OneDrive directory. Please tell me if you need more information."
1728354,2017-11-14 09:12:14 UTC,"> Please tell me if you need more information.
"
1728354,2017-11-26 14:19:52 UTC,I have followed the steps in #13 and worked perfectly - i.e. I was able to access the files in OneDrive folder without the need to use root account.
1728354,2017-11-26 17:01:14 UTC,"> Is there a way to make the change permanent?
"
1728354,2017-11-28 16:11:47 UTC,"I have ""installed"" the module per #4 and #13 - i.e. copied onedrive/linux-64/ntfs-plugin-9000301a.so to the directory identified by:"
1728354,2017-11-29 07:37:04 UTC,"> I have ""installed"" the module...
I assume you have also recompiled and installed ntfs-3g 2017.3.23AR.1 according to recommended Ubuntu settings.
"
1728354,2017-12-05 16:01:16 UTC,"I haven't touched ntfs-3g, only copied/installed the plugin from onedrive.zip to the directory identified by strings $(which ntfs-3g) | grep ntfs-plugin."
1728354,2017-12-05 18:15:02 UTC,"> I haven't touched ntfs-3g, only copied/installed the plugin
"
1728354,2017-12-05 22:44:40 UTC,Followed the test scenario - result: OneDrive has no problem to sync after saving the file with LibreOffice.
1728354,2017-12-06 09:30:45 UTC,"> OneDrive has no problem to sync after saving the file with LibreOffice.
"
1728354,2017-12-10 16:47:07 UTC,I would say there is no problem using OneDrive folder (NTFS drive) after(!) importing the plugin from onedrive.zip.
1728354,2017-12-11 20:48:00 UTC,Good news. Thanks for reporting.
1728354,2017-12-18 21:45:38 UTC,when can we expect the patch will be in the ntfs-3g packaging :)
1728354,2017-12-18 22:11:37 UTC,"$ strings $(which ntfs-3g) | grep ntfs-plugin
/usr/lib/x86_64-linux-gnu/ntfs-3g/ntfs-plugin-%08lx.so"
1728354,2017-12-19 07:17:33 UTC,"> do i need to create the folder ntfs-3g since its not available.
Yes, when using ntfs-3g packaged by Ubuntu, you have to move the plugin to /usr/lib/x86_64-linux-gnu/ntfs-3g/ntfs-plugin-9000301a.so
"
1728354,2017-12-19 14:04:07 UTC,I've tried to follow #4
1728354,2019-10-08 14:55:33 UTC,"For example under ""Ubuntu 18.04.3 LTS""
ls -als ""/Windows1/Program Files/WindowsApps/microsoft.windowscommunicationsapps_16005.11629.20316.0_x64__8wekyb3d8bbwe"" >$HOME/ERROR1.txt"
1728354,2018-10-07 19:51:54 UTC,"> any update or progress?
"
1728354,2019-10-08 16:40:08 UTC,The same repository Under windows
1728354,2018-10-25 02:27:43 UTC,"I have compiled and installed ntfs-3g-2017.3.23AR.3, by default, i can access all directories in one drive folder, but all files are not valid, trying ls -al, shows like:
lrwxrwxrwx 1 root root    25 3月  16  2017  layout.txt -> 'unsupported reparse point'"
1728354,2019-10-08 20:27:42 UTC,"> trying to duplicate the contents of the windows partition
> with the RSYNC command
>
> rsync -a --delete --filter ""- .tmp"" --filter ""- lost+found/"" --filter
> ""- .Trash/"" > /Windows1 /mnt/sdc14 2>ERROR.txt
"
1728358,2017-10-30 07:24:54 UTC,neutron-lbaas is now maintained by the octavia launchpad. Let's forward this.
1728358,2019-05-10 21:02:29 UTC,"Change abandoned by Adam Harwell (<email address hidden>) on branch: master
Review: https://review.opendev.org/516080
Reason: Abandoning old reviews in preparation for retiring the neutron-lbaas project."
1728360,2017-10-29 14:58:12 UTC,"I'll try to investigate that. I did not manage to reproduce it with Linux Mint 18.2, maybe it only affects newest Ubuntu release."
1728361,2017-10-31 15:07:31 UTC,"sudo dpkg --configure -a
sudo apt -f install
sudo dpkg-reconfigure --force systemd-sysv
sudo dpkg --purge systemd-sysv
dpkg: проблемы с зависимостями не позволяют удалить пакет systemd-sysv:
 ubuntu-standard зависит от systemd-sysv, однако:
  Пакет systemd-sysv будет удалён.
 init зависит от systemd-sysv | upstart-sysv, однако:
  Пакет systemd-sysv будет удалён.
  Пакет upstart-sysv не установлен.
 libpam-systemd:amd64 зависит от systemd-shim (>= 8-2) | systemd-sysv, однако:
  Пакет systemd-shim не установлен.
  Пакет systemd-sysv будет удалён."
1728364,2017-11-10 17:25:56 UTC,I further tested this on a live session of Ubuntu Gnome 17.04 and Fedora 26 (Gnome 3.24) and the bug was not present there. I will test it on Fedora 27 as soon as it is released to check if the issue is related to Gnome 3.26 or Ubuntu specific.
1728364,2017-11-14 17:31:56 UTC,I tested Fedora 27 live session (Gnome 3.26) today and the bug is not present. It seems Ubuntu specific.
1728364,2018-09-19 18:48:31 UTC,Bug is still present in Bionic 18.04.1.
1728366,2017-10-29 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1728373,2017-11-15 14:08:19 UTC,"Easily reproduced in a VM.  Even more annoying is that apparently no gettys are spawned in this mode so you can't even check with systemd to see if a shutdown request has been initiated and failed for some reason, or try to initiate a shutdown from the command line."
1728375,2018-02-27 12:20:05 UTC,Why you are posting a bug for Telegram for iOS in the Ubuntu Touch tracker?
1728376,2017-12-06 22:58:42 UTC,"The default Ubuntu toolbar setup also has a ""Help"" launcher with a right click menu containing a ""Show Details"" option that goes to an App Store page with no results."
1728376,2017-12-06 22:58:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728378,2018-01-26 13:38:07 UTC,Changing the default r8169 driver for the oficial r8168 works for me.
1728378,2017-11-01 18:38:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728378,2017-12-05 14:25:34 UTC,Do you think that this error can break my VPN connection ?
1728378,2017-11-04 21:46:33 UTC,"I believe this is harmless, but not really know ;)
Attached part of bootlog file (journalctl -b), containing this error"
1728378,2017-12-12 23:25:21 UTC,This bug affects my Dell 5378 13 i7 KabyLake. New re-install of Artful.
1728381,2017-10-31 16:56:49 UTC,i have run both:
1728381,2017-11-04 21:29:56 UTC,"with the proposed package, it fails now in another file:"
1728381,2017-10-29 21:49:48 UTC,apport information
1728381,2017-10-29 13:16:11 UTC,apport information
1728381,2017-10-29 21:49:45 UTC,apport information
1728381,2017-10-29 13:16:10 UTC,apport information
1728381,2017-10-29 13:16:08 UTC,apport information
1728381,2017-10-29 21:49:47 UTC,apport information
1728385,2017-10-30 19:21:59 UTC,apport information
1728385,2018-10-07 09:37:23 UTC,Issue still exists in Ubuntu 18.04.1 LTS
1728385,2018-10-06 04:17:24 UTC,[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]
1728385,2018-08-06 07:32:47 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1728385,2017-11-06 02:17:18 UTC,"OK, thanks. This is then a simple enhancement request to reduce excessive logging, per comment #18."
1728385,2017-11-03 17:35:05 UTC,"Mentioned ""rfkill unblock all"" command actually enables bluetooth, which I'd like to keep disabled.
bluetoothd should check if device is blocked and do not try setting mode for such devices."
1728385,2017-11-03 12:50:57 UTC,I had the same issue on a Lenovo laptop. The command
1728385,2017-10-30 19:22:00 UTC,apport information
1728385,2017-10-30 19:21:58 UTC,apport information
1728385,2017-10-30 19:21:55 UTC,apport information
1728385,2017-10-30 19:21:53 UTC,apport information
1728385,2017-10-30 19:21:52 UTC,apport information
1728385,2017-10-30 19:21:50 UTC,apport information
1728385,2017-10-30 19:21:49 UTC,apport information
1728385,2017-10-30 19:21:48 UTC,apport information
1728385,2017-10-30 19:21:46 UTC,apport information
1728385,2017-10-30 19:21:45 UTC,apport information
1728385,2017-10-30 19:21:44 UTC,apport information
1728385,2017-10-30 19:21:43 UTC,apport information
1728385,2017-10-30 06:19:08 UTC,Please also try this command to stop the error message happening:
1728385,2017-10-30 06:15:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1728385"
1728385,2017-10-30 19:21:54 UTC,apport information
1728389,2018-04-22 23:10:34 UTC,As of today this is no longer an issue. Current kernel: 3.13.0-38
1728412,2017-10-30 20:17:20 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1728412,2017-11-02 04:31:22 UTC,*** Bug 774947 has been marked as a duplicate of this bug. ***
1728412,2017-11-02 04:31:02 UTC,*** Bug 786910 has been marked as a duplicate of this bug. ***
1728412,2017-10-31 06:25:54 UTC,"@Joseph it happens in a new installation. I wouldn't expect this to be in the linux kernel, but if you are convinced that the test has value, please ping me again and I'll do the upstream kernel test"
1728412,2017-10-31 21:29:23 UTC,other report https://bugzilla.gnome.org/show_bug.cgi?id=770185
1728412,2017-10-31 21:26:28 UTC,There is an upstream report about that on https://bugzilla.gnome.org/show_bug.cgi?id=786910
1728412,2017-10-31 21:25:08 UTC,the issue is likely in gnome-shell/xwayland dealing with legacy x11 softwares
1728412,2017-11-06 14:16:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728412,2017-10-31 21:29:52 UTC,"reported on Ubuntu as well, https://bugs.launchpad.net/gnome-shell/+bug/1728412"
1728412,2017-11-18 23:29:18 UTC,Can confirm this for Shell 3.26.2 and mutter 3.26.2 on Arch Linux. I can't interact with the titlebar of XWayland apps via touchscreen.
1728412,2018-05-23 01:07:01 UTC,"Thanks for the patches; moving around windows and closing them now works.  However, moving maximised windows by grabbing them from the top-bar in gnome-shell still does not work. Works on Xorg though. As of commit 235c3518."
1728412,2018-03-17 14:55:51 UTC,Not only on Arch; confirming it's also present on openSUSE Tumbleweed with Gnome 3.28
1728412,2018-04-14 16:49:39 UTC,And with Fedora. This bug has now been around for four GNOME releases...
1728412,2018-04-15 15:25:10 UTC,"The last time I looked into this, it was a whole lot more troublesome. Events on the frame came from the GDK display connection, this brought 2 series of problems:"
1728412,2018-05-15 14:08:19 UTC,https://gitlab.gnome.org/GNOME/mutter/merge_requests/78 was merged to master earlier today. And I've just cherry picked to 3.28.
1728412,2018-05-23 08:12:20 UTC,"Thanks for testing! Please file a gnome-shell issue for that, as the code allowing maximized window dragging from the top bar is there."
1728412,2018-05-26 18:10:27 UTC,"Almost 2 years since this was opened and still having this problem on both of my touchscreen thinkpads... Can't interact with the window bars at all on some applications. X220 Tablet and Yoga 20C0 both with Arch Linux, kernel 4.16.11-1-ARCH and GNOME 3.28.2-1."
1728412,2018-05-26 18:38:04 UTC,"(In reply to Carlos Garnacho from comment #18)

> Thanks for testing! Please file a gnome-shell issue for that, as the code
> allowing maximized window dragging from the top bar is there.
"
1728412,2018-05-26 20:22:31 UTC,comment #17 actually is https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/112.
1728412,2018-08-08 08:19:21 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1728412,2018-08-09 04:54:37 UTC,Still present in Ubuntu 18.04.1 LTS
1728412,2018-03-16 21:32:00 UTC,Gnome 3.28 has the same problem on Arch Linux.
1728412,2017-10-29 16:25:05 UTC,I can also reproduce it with thunderbird and kate.
1728412,2017-10-29 15:17:22 UTC,apport information
1728412,2017-10-29 15:17:35 UTC,apport information
1728412,2017-10-29 15:17:37 UTC,apport information
1728412,2016-08-21 05:42:58 UTC,"steps to reproduce
start Gnome on Wayland session from GDM login manager
open any gtk2 (gimp), qt4 (vlc player) or qt5 (qupzilla or smplayer) app
use touchscreen to drag or close the app window
nothing happens, touchscreen does no effect on window title bar"
1728412,2017-03-18 21:25:05 UTC,This problem is still present on 3.24 RC.
1728412,2017-06-17 01:10:03 UTC,Identical behaviour still seen on 3.24.2
1728412,2017-06-17 01:13:46 UTC,"Strangely enough, I see the inverse behaviour with a pen (on a Surface Pro 3) - GIMP, SMPlayer, Firefox are all movable via the titlebar with the pen, whereas e.g. Files, Evolution, gedit are not."
1728412,2017-06-17 01:18:54 UTC,"Sorry for spamming this bug... when using the pen, the close button works in all cases, but for touch, the functionality of close matches that of drag."
1728412,2017-06-17 01:28:18 UTC,"(In reply to Stephen from comment #2)

> Weirdly enough it also seems to affect Firefox, despite that having been
> built with --enable-default-toolkit=cairo-gtk3
>


Firefox gtk3 runs under xwayland."
1728412,2017-09-02 01:55:55 UTC,"I can confirm this with Firefox. If I use a theme that has its own close button, it works just fine."
1728412,2017-09-20 03:27:58 UTC,Gnome 3.26 has the same problem.
1728412,2017-10-29 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1728412,2017-10-29 15:17:12 UTC,apport information
1728412,2017-10-29 15:17:21 UTC,apport information
1728412,2017-10-29 15:17:16 UTC,apport information
1728412,2017-10-29 15:17:18 UTC,apport information
1728412,2017-10-29 15:17:20 UTC,apport information
1728412,2017-10-29 15:17:24 UTC,apport information
1728412,2017-10-29 15:17:26 UTC,apport information
1728412,2017-10-29 15:17:28 UTC,apport information
1728412,2017-10-29 15:17:29 UTC,apport information
1728412,2017-10-29 15:17:31 UTC,apport information
1728412,2017-10-29 15:17:32 UTC,apport information
1728412,2017-10-29 15:17:14 UTC,apport information
1728412,2017-10-29 15:17:33 UTC,apport information
1728422,2017-11-09 08:30:31 UTC,"With:
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial"
1728422,2017-11-11 09:25:25 UTC,"> What logs can I provide or what test can I run to help confirm this bug?
"
1728423,2018-10-08 15:08:01 UTC,"Never noticed there was a reply, nevertheless, artful is dead now so while that's now a moot point, I can't seem to reproduce that error, at least when I run that URL as an argument for dget."
1728423,2018-01-06 00:22:05 UTC,"As per discussion with Laney, merges:"
1728423,2018-06-13 16:39:21 UTC,dpkg-source: error: file /home/adconrad/dh/debhelper_11ubuntu0.1~ubuntu17.10.tar.xz has size 441208 instead of expected 441216
1728423,2018-07-23 11:58:01 UTC,What can I do to see debhelper 10.3+ in xenian-backports?
1728423,2017-11-07 23:21:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728429,2017-11-06 15:24:45 UTC,kernel-fixed-upstream
1728429,2017-10-29 16:30:10 UTC,This change was made by a bot.
1728429,2017-10-30 20:18:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1728430,2017-10-29 22:48:44 UTC,Assigning it to you per your comment in IRC. Thank you for working on the Gentoo support. As you get fixes feel free to submit merge requests and hit us up in IRC! Again thank you!
1728445,2017-10-29 21:43:38 UTC,"systemd-resolve is not part of resolvconf, it is part of systemd; reassigning."
1728445,2017-10-30 08:08:25 UTC,At least I did not install this packet manually.
1728450,2017-10-29 20:40:22 UTC,"I believe you'll find that if you change your theme to Ambiance (the default in the Ubuntu session), the Settings sidebar is tall enough to show all items without a vertical scrollbar."
1728450,2019-01-31 14:05:53 UTC,Being discussed upstream as well in https://gitlab.gnome.org/GNOME/gnome-control-center/issues/83
1728450,2019-01-31 15:57:00 UTC,This bug was fixed in the package gnome-control-center - 1:3.30.2-4ubuntu2
1728452,2017-11-10 21:30:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728455,2017-11-05 05:55:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728455,2018-08-06 07:58:35 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1728456,2017-12-24 07:11:14 UTC,The latest version is now 2.6.19.
1728462,2017-10-30 16:11:59 UTC,"Thank you for your bug report, in which situations would you expect to see badges?"
1728462,2017-10-31 10:42:49 UTC,"Getting notifications from web services. For instance I opted to get notification from YouTube and Facebook, I get notification pop down, but no badges."
1728462,2019-03-12 08:49:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728465,2018-04-12 07:45:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728467,2017-11-10 13:59:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728467,2017-11-30 14:35:29 UTC,The change was intentional.  See bug #453605.
1728467,2017-11-30 23:19:04 UTC,If the intention of the changes was to make all files executable then that was a poor decision (it does not appear that was the focus of the whatsoever...
1728467,2018-05-08 21:45:07 UTC,Not sure what the heck you all are recently taking about.
1728467,2018-05-08 18:15:40 UTC,"Udisks specifying a default mask was removed intentionally, leaving the default to the NTFS driver.  ntfs-3g defaults to all executable.  People often do have executable files on their NTFS drives and want to be able to execute them.  This has gone back and forth a few times over the years and without the execute bit, less experienced users are unable to make things work and don't understand why.  With the bit, more experienced users are... well, let's just say offended.  I think we're better off where we are, but maybe the ntfs-3g devs can chime in on why it defaults to execute on when the in kernel driver does not.  My guess is that it is intentional but we'll see."
1728467,2018-02-21 13:16:44 UTC,Could somebody report that issue upstream on https://github.com/storaged-project/udisks/issues ?
1728467,2017-12-25 23:45:03 UTC,"Thank you very much for your offer, but I have messed up my system trying to fix that and at this point I don't want to complicate matters further (17.10 is quite buggy for me)."
1728467,2017-12-24 16:01:00 UTC,"@ Matt -
here for my personal builds (16.04/18.04) i've altered source in this manner & it does what's best for me -
-static const gchar *ntfs_defaults[] = { ""uid="", ""gid="", NULL };
+static const gchar *ntfs_defaults[] = { ""uid="", ""gid="", ""fmask=0111"", NULL };"
1728467,2017-12-22 21:20:22 UTC,"In ubuntu 16.10/17.04/17.10, handling of ntfs drives has changed compared to 14.04.5.
Now, all files on an ntfs drive are marked as executable."
1728467,2018-05-08 19:59:53 UTC,"> why it defaults to execute on when the in kernel driver does not.
"
1728467,2017-12-22 21:12:53 UTC,"Please understand that this is severely affecting basic ubuntu use with ntfs drives for basic users, while bug #453605 that is said to be the reason of the misbehaviour has merely given more options to advanced users and was not intended to mess up file handling in the way it presumably did.
If it's goal ""easy way to configure the default umask for VFAT/NTFS"" has been reached, it should also be easy to set sane defaults for users that can't (nor should be required to) do it for themselves."
1728490,2018-01-11 11:05:32 UTC,"Reviewed:  https://review.openstack.org/517189
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=4696f9c8931817ece5fc2994ba37519abc5c5694
Submitter: Zuul
Branch:    master"
1728490,2017-11-02 07:23:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/517189"
1728509,2017-10-30 05:42:01 UTC,https://github.com/laurynas-biveinis/percona-server/commit/d568d390ffebd05f28e65c7917cd36eacd2707b7
1728509,2018-01-25 08:34:55 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3754
1728510,2017-10-31 21:42:22 UTC,Needs more investigation and low priority. Pushing out to 4.1.1.
1728510,2018-01-11 04:53:36 UTC,"Could you please add details about specific topology and configurations required to see this issue. With 4.1 image, I am not able to reproduce the problem on a 5 node topology with following configuration:"
1728512,2017-10-30 05:46:07 UTC,https://github.com/laurynas-biveinis/percona-server/commit/adcf40ffa8540279d71e84e643654ffcff428a44
1728512,2018-01-25 08:34:56 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3755
1728517,2017-10-30 18:30:35 UTC,Padstacks should be editable during layout time.
1728517,2017-11-26 23:14:59 UTC,"I agree this would be a nice feature. In order to implement it, I think we would need to design a padstack system in pcb. Doing so could solve several problems, but is a major undertaking."
1728529,2017-11-03 06:33:25 UTC,"hi,
stable/ocatan had this bug.
you need to edit this file."
1728535,2017-12-09 01:57:17 UTC,"Hi,"
1728535,2017-12-09 18:08:29 UTC,libvirt (the library around KVM) stores the training-labs images on your root partition (you will probably find the images in /var/lib/libvirt/images/).
1728535,2017-11-08 09:37:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518500"
1728535,2017-11-16 14:22:36 UTC,"Reviewed:  https://review.openstack.org/518500
Committed: https://git.openstack.org/cgit/openstack/training-labs/commit/?id=d1c4dd1c090fe1663e23f8e8501c0dfb49144f5b
Submitter: Zuul
Branch:    master"
1728535,2019-05-25 06:37:56 UTC,I am closing this bug. The last bug was not having enough disk space.
1728535,2017-11-03 14:42:01 UTC,"KVM has always been harder than VirtualBox (less integrated solution, differences in setup between distros), but it should not be as difficult as it appears to be in your case."
1728535,2017-10-31 10:20:43 UTC,"Regarding the default pool and network: on some distros, you have to start virt-manager once to create them. We could try to do it in our scripts, but making it work reliably on all distros would take extensive testing. I guess most users will have done that anyway (just when using libvirt/KVM for something else), but at least we could document that better."
1728535,2017-11-02 15:31:39 UTC,I am genuinely interested in the answers to my questions. Any updates?
1728535,2017-11-02 21:48:23 UTC,Sorry for the delay Roger.
1728535,2017-10-30 20:45:17 UTC,"Hi Roger,"
1728535,2017-10-30 12:07:56 UTC,"Looks like the controller VM does not boot (properly). You would see this behavior if the basedisk was broken. If, for instance, the basedisk creation fails during the distro install and you try to build a cluster anyway, the first thing you'll notice is that the disk image won't boot. The basedisk installation should end with something like this on the console:"
1728547,2017-10-30 14:52:03 UTC,Please approve the new ubuntu-drivers-common in xenial-proposed and in zesty-proposed.
1728547,2018-02-22 19:31:25 UTC,"This has been marked verification-done for xenial for a while now - is there anything preventing it from being published to xenial-updates? I'm aware of bug 1731873 as well, but this change was reverted in xenial-proposed and is not in the current version (1:0.4.17.6)"
1728547,2018-02-23 15:29:00 UTC,This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.6
1728547,2018-02-02 03:39:40 UTC,verified on BRM4-DVT1-C2H (201710-25874)
1728547,2018-02-01 18:50:46 UTC,This bug was fixed in the package ubuntu-drivers-common - 1:0.4.26
1728547,2018-02-01 15:53:56 UTC,I have pushed a fix for the test suite in Bionic.
1728547,2018-01-31 07:55:38 UTC,"@sil2100,"
1728547,2018-01-30 14:08:09 UTC,"a change referencing this bug is in the latest version for bionic, but it failed to build on some archs and is stuck in -proposed:"
1728547,2018-01-24 14:28:17 UTC,"Hello Alberto, or anyone else affected,"
1728547,2018-01-22 11:53:36 UTC,"I'm pretty sure we didn't use to build on s390x. I have added a hack to
work around that test, which should be fine, since we don't really use
ubuntu-drivers-common on s390x."
1728547,2018-01-18 14:51:01 UTC,The current ubuntu-drivers-common package in xenial-proposed fails to build on s390x:
1728547,2018-01-03 16:08:41 UTC,"Hello Alberto, or anyone else affected,"
1728547,2017-12-19 08:37:20 UTC,It's blocked on LP: #1731873 not verified. Both SRU bugs need to be verified for the update to get released (as upload has fixes for both). Please perform the tests as per what's in the Test Case in the aforementioned bug.
1728547,2017-12-19 02:48:09 UTC,"Hi, we also have verification done for xenial. Can we also land there ?"
1728547,2017-12-18 17:52:39 UTC,"The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1728547,2018-01-15 08:46:38 UTC,"verified on BRM5-DVT1-C2H (201710-25875)
Image: X35
BIOS: 0.3.2"
1728547,2017-12-12 09:03:34 UTC,"Bug 1731873 is also awaiting verification, that is another bug for ubuntu-drivers-common SRU."
1728547,2017-10-30 16:21:46 UTC,I forgot to mention the package in artful-proposed.
1728547,2017-10-31 12:13:56 UTC,This bug was fixed in the package ubuntu-drivers-common - 1:0.4.24
1728547,2017-12-18 17:52:30 UTC,This bug was fixed in the package ubuntu-drivers-common - 1:0.4.23.1
1728547,2017-11-03 07:20:56 UTC,"verified 1:0.4.23.1 with xenial on MST-EVT-C2 , it looks good."
1728547,2017-11-03 07:21:50 UTC,"verified 1:0.4.23.1 with artful on FIR5K-PILOT-C1 , it looks good."
1728547,2017-11-13 06:56:52 UTC,"@Alberto
it's verified done by #5 #6.
how's the status of further SRU process?"
1728547,2017-11-02 20:49:40 UTC,"Hello Alberto, or anyone else affected,"
1728547,2017-11-16 21:11:39 UTC,"Hello Alberto, or anyone else affected,"
1728547,2017-11-16 21:13:26 UTC,"Hello Alberto, or anyone else affected,"
1728547,2017-11-21 08:36:55 UTC,"verified on MST-EVT-C2, it works well."
1728547,2017-11-27 08:46:55 UTC,"verified on FIR5K-PILOT-C1 for zesty , it works as well."
1728547,2017-12-12 07:39:46 UTC,what's the reason we can't land this one on xenial ?
1728547,2017-11-13 10:04:54 UTC,"I have re-uploaded the sources for xenial and zesty, this time mentioning LP: #1731873, so that the upload is not rejected again."
1728548,2019-02-21 00:40:39 UTC,I also had the same problem after upgrading from 16.04 to 18.04.
1728548,2020-07-28 13:52:01 UTC,"Same problem since a week or so on
- Ubuntu 20.04.1 LTS
- 20.04.1 LTS"
1728548,2019-07-23 13:47:58 UTC,Just another failure report with Duplicity 0.7.18.2 included in Debian Buster:
1728548,2019-06-04 11:48:20 UTC,This error appears for me too when the periodic secret validation occurs. The validation takes a long time and eventually times out.
1728548,2019-04-29 18:00:54 UTC,"I added the ""unknown system error"" to the title to emphasize that this is not about ever GPG-bug, but about this issue (see comment #14)."
1728548,2019-04-08 04:16:01 UTC,"Michael,"
1728548,2019-04-07 16:24:46 UTC,"Mortimer, from comment 10: your problem is a recently fixed passphrase bug. See https://wiki.gnome.org/Apps/DejaDup/PassphraseProblems2019"
1728548,2019-04-05 10:12:06 UTC,I found my problem using
1728548,2019-04-05 09:35:43 UTC,"I have the same problem. I don't remember updating anything special, my backups just started to fail last week with the error message"
1728548,2019-02-02 08:12:51 UTC,I had the same problem after upgrading from 16.04 to 18.04.
1728548,2017-11-01 21:30:06 UTC,This happened to me as well.
1728548,2018-08-13 02:15:37 UTC,4. attached
1728548,2018-08-13 02:15:06 UTC,"1. Description:	Ubuntu 18.04.1 LTS
2. deja-dup	37.1-2fakesync1
   duplicity	0.7.17-0ubuntu1
3. attached"
1728548,2018-07-11 04:17:22 UTC,[Expired for Déjà Dup because there has been no activity for 60 days.]
1728548,2018-05-11 07:46:54 UTC,Hello everyone.
1728548,2018-05-09 10:41:49 UTC,"Sorry, I didn't."
1728548,2018-05-09 02:36:32 UTC,"Matthew & Mark,"
1728548,2017-11-02 14:58:41 UTC,"When I try ""deja-dup --backup"" on the command line, I get a message that it is a ""creating a fresh backup to protect against backup corruption. This will take longer than normal""."
1728548,2018-09-10 19:37:20 UTC,Same here on 18.04 - deleting the backupo and starting over did not help as well.
1728555,2018-01-26 11:47:10 UTC,"Reviewed: https://review.fuel-infra.org/36654
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1728556,2017-10-30 10:03:35 UTC,"StacktraceTop:
 set_startup_id (startup_id=0x2 <error: Cannot access memory at address 0x2>, backend=0x8ed8c80) at ./uniqueapp.c:191
 unique_app_set_property (gobject=0x8ef1ce0, prop_id=2, value=0xbfe3f048, pspec=0x8ef3750) at ./uniqueapp.c:300
 object_set_property (nqueue=<optimized out>, value=0xbfe3f150, pspec=0x8ef3750, object=<optimized out>) at ../../../../gobject/gobject.c:1439
 g_object_constructor (type=149963408, n_construct_properties=1, construct_params=0x8ec3640) at ../../../../gobject/gobject.c:2160
 unique_app_constructor (gtype=149963408, n_params=3, params=0x8ec3630) at ./uniqueapp.c:271"
1728556,2017-11-09 12:36:54 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1728558,2018-01-17 07:40:11 UTC,"Why the volume's status is 'available'? It should be 'attached' before step 4.
At other steps, the volume is not exist."
1728558,2018-01-09 12:28:53 UTC,"#block_device_allocate_retries=60
#block_device_allocate_retries_interval=3"
1728558,2018-01-17 08:45:37 UTC,"The volume is ""in-use"" before step 4, of course."
1728558,2017-12-07 03:12:59 UTC,"It can't be reproduced on my computer.
Please check the parameters such as block_device_allocate_retries, block_device_allocate_retries_interval in nova.conf. And then check the volume list whether there is a lastest created volume."
1728570,2019-01-07 11:39:03 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/516258
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.
Feel free to restore it again if you want to pick up and continue the work."
1728570,2017-10-30 12:07:47 UTC,As mentioned in the review of ^^ this also requires an update to the nova-compute charm README.
1728570,2018-03-12 11:23:08 UTC,Aydin asked if i could take the cinder-ceph patch off him so adding to my queue and marking WIP.
1728570,2017-10-31 08:34:18 UTC,"Reviewed:  https://review.openstack.org/516358
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=764b11c6d15aaf9177e0dba4d289f3b37cdce544
Submitter: Zuul
Branch:    master"
1728570,2017-10-30 12:06:30 UTC,Patch submitted by aydintd to https://review.openstack.org/#/c/516258/
1728570,2017-10-30 15:49:48 UTC,I submitted the patch for nova-compute README.md file here as well : https://review.openstack.org/#/c/516358/
1728573,2018-02-13 10:39:55 UTC,Any news on this? Thanks!
1728573,2017-10-30 12:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1728574,2017-10-30 11:45:12 UTC,"Empirically, if the Xwayland session is run as root then it starts successfully. (Although the socket it creates is owned by root, which isn't desirable.)"
1728574,2017-11-03 16:31:27 UTC,Syncing task from Mir.
1728574,2017-11-08 06:49:37 UTC,Long and boring root-cause and psuedo-fix on https://github.com/MirServer/mir/pull/18
1728574,2017-11-08 15:21:01 UTC,Alternative fix: https://github.com/MirServer/mir/pull/19
1728575,2019-10-27 10:26:46 UTC,"Thanks for finding the corresponding Debian report, I added a bug watch via ""Also affects distribution/package"" which makes it easier to track status changes."
1728575,2017-10-30 11:35:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728575,2017-10-30 11:48:04 UTC,"Debian has already a testing package available, please see https://packages.debian.org/search?keywords=catch"
1728575,2018-03-20 17:05:37 UTC,"Meanwhile, package and distribute version 2.2.1. Several mainstream packages use this while building and need custom code to download latest version. This should be updated frequently as it is related to build tools."
1728575,2018-06-18 11:26:55 UTC,"Meanwhile, version 2.2.3 is out. Also FreeBSD is shipping version 2, see https://svnweb.freebsd.org/ports/head/devel/catch/"
1728575,2018-11-02 15:39:24 UTC,https://github.com/catchorg/Catch2/releases/tag/v2.4.2
1728575,2020-05-16 08:46:45 UTC,"Catch has been updated to 1.12.1-1ubuntu1 i 20.04. Additionally, catch2 has been packaged as separate package and synced from Debian to Ubuntu Groovy (https://launchpad.net/ubuntu/+source/catch2)"
1728577,2017-11-15 10:12:55 UTC,"Hello Mike,"
1728577,2017-10-30 15:29:29 UTC,"basically, I need to see the detailed data backing up this statement:"
1728577,2017-10-30 15:25:55 UTC,I will go through this in more detail soon however the toplevel things here that are most applicable to us can be addresed with these features:
1728577,2017-10-30 12:11:34 UTC,"As the paste will expire, here's the same log output."
1728579,2018-01-25 08:34:58 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3757
1728581,2017-12-14 17:12:57 UTC,This bug was fixed in the package mir - 0.29.0-0ubuntu1
1728581,2017-11-03 16:37:09 UTC,Syncing task from Mir.
1728591,2018-01-23 03:27:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728591,2017-10-30 15:48:20 UTC,GNOME Shell 3.26.1 on Ubuntu 17.10
1728591,2017-10-30 15:34:18 UTC,What ubuntu version and desktop environment do you use?
1728591,2017-10-30 15:34:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1728592,2017-11-10 00:44:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728600,2019-01-22 15:55:16 UTC,"afazekas: can you point to the documentation re: ""no random port status flipping"" being allowed? External forces can sometimes take down the underlying port for example."
1728600,2020-10-26 09:39:21 UTC,"There has been a long inactivity here, so moving to Incomplete for now."
1728600,2020-12-26 04:17:16 UTC,[Expired for tempest because there has been no activity for 60 days.]
1728600,2018-12-20 05:46:20 UTC,Seems already there is one more issue: https://bugs.launchpad.net/tempest/+bug/1710845
1728600,2019-01-21 07:55:01 UTC,"Nova expected to wait for all connected port to become active on instance creation before reporting the instance active.
No additional user/tempest wait is required, no random port status flipping is allowed."
1728600,2018-12-19 08:50:53 UTC,Found below issues which are fixing this bug:
1728600,2017-10-30 16:10:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/516372"
1728600,2018-12-19 09:27:25 UTC,One more which is related to this issue: https://review.openstack.org/#/c/516372
1728602,2017-11-15 05:48:50 UTC,there seems to be no obvious correlation with node_provider etc.
1728603,2018-05-12 04:46:19 UTC,"Reviewed:  https://review.openstack.org/567630
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a16fa14ce47bd2d3a5189047e9bd330a607ef3cc
Submitter: Zuul
Branch:    stable/ocata"
1728603,2017-11-08 07:17:08 UTC,"Reviewed:  https://review.openstack.org/517390
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=64f773ab96619b97de2bc521fdfc8400fdb7bd3d
Submitter: Zuul
Branch:    stable/ocata"
1728603,2018-05-11 22:01:13 UTC,"Reviewed:  https://review.openstack.org/567625
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c72a0a7665e96219f0301525edc513dda07b320b
Submitter: Zuul
Branch:    stable/pike"
1728603,2018-05-11 02:51:58 UTC,"Reviewed:  https://review.openstack.org/567623
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=174764340d3c965d31143b39af4ab2e8ecefe594
Submitter: Zuul
Branch:    stable/queens"
1728603,2018-05-10 20:43:54 UTC,"Reviewed:  https://review.openstack.org/566367
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e3385707cb1ced55cd12b1314d8c0b68d354c38
Submitter: Zuul
Branch:    master"
1728603,2018-05-10 16:17:50 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/567630"
1728603,2018-05-10 16:00:57 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/567625"
1728603,2018-05-10 15:39:26 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/567623"
1728603,2018-05-04 17:12:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/566367"
1728603,2017-12-07 23:56:32 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1728603,2017-11-15 01:06:45 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1728603,2017-11-08 07:16:56 UTC,"Reviewed:  https://review.openstack.org/517388
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d5d81a29050966f47050f0f77001273b1aa55116
Submitter: Zuul
Branch:    stable/pike"
1728603,2017-11-15 01:10:31 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1728603,2017-11-02 18:05:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/517388"
1728603,2017-11-02 16:33:23 UTC,"Reviewed:  https://review.openstack.org/516395
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f02afc6569bd930114a4b56413dbd6becc5e7e75
Submitter: Zuul
Branch:    master"
1728603,2017-10-31 01:37:34 UTC,Reproduced with a Tempest test in the NFS job here:
1728603,2017-10-30 16:56:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/516395"
1728603,2017-10-30 16:38:37 UTC,"Oh nevermind I think I understand, the root disk in the volume isn't the same storage, the problem is that because the root disk is in a cinder volume, ""root_disk.exists()"" is False so we assume it's not shared storage and we remove the instance base directory files, which are on shared storage between the source and destination hosts."
1728603,2017-10-30 16:36:13 UTC,"I can't say I understand this really - why would the instance base directory that contains the libvirt domain xml files for the guest, which are ephemeral per compute host, be the same location as the root disk that is backed by the Cinder volume? Is the local ephemeral disk on the compute host the same NFS storage as the Cinder volumes?"
1728603,2017-10-30 14:32:49 UTC,"Yeah, it's the boot-from-volume thing that's the difference I believe."
1728603,2017-10-30 14:21:05 UTC,So we do run resize tests in the NFS job:
1728603,2017-10-30 14:12:16 UTC,"Note that we do run an NFS-based job in the nova experimental CI queue but I'd have to check if it runs any resize tests - it probably should, and those are likely broken."
1728603,2017-10-30 14:09:59 UTC,The referenced change was backported to ocata so marking this as affecting pike and ocata:
1728603,2017-11-02 18:13:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/517390"
1728605,2018-03-17 12:01:48 UTC,"Distributor ID:	Ubuntu
Description:	Ubuntu 17.10
Release:	17.10
Codename:	artful"
1728605,2018-02-10 21:43:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728613,2017-11-03 15:24:54 UTC,Syncing task from Mir.
1728617,2017-12-05 00:10:10 UTC,This bug was fixed in the package gtk+3.0 - 3.22.26-2ubuntu1
1728617,2017-10-30 15:29:47 UTC,"The patch was added in 2012 in reaction to https://bugzilla.gnome.org/show_bug.cgi?id=671305 and it should probably be removed indeed but softwares got fixed and there is no need for a distro specific behaviour there, thanks for the report"
1728635,2017-12-21 23:48:46 UTC,I can't reproduce this on commit a93ece47fd9edbd4558db24300056c9a57d3bcd4:
1728635,2020-11-10 03:13:05 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1728635,2021-01-09 04:17:56 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1728637,2017-10-30 16:15:08 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06) (32 bit build)"
1728637,2017-10-30 16:23:19 UTC,"fwiw, the same error occurs if I attempt to do this conversion outside of Inkscape, in DOS, using the command:"
1728647,2017-10-31 00:49:44 UTC,"Looks like it works here... the example shows 4 objects (text, but it could be anything) being replaced in their respective locations by 4 clones (stars) with their parent object outside the page area. Do they need to retain some scale/rotation transforms or something else?"
1728647,2017-10-30 21:54:32 UTC,"Would ""rearrange"" in the Align-Distribute panel work for you?"
1728647,2017-10-30 22:39:07 UTC,"No. Unfortunately not. In my case I have 87 (I think) squares that are already where I need them. I need to edit them all and I don't want to have to edit them one by one so I want to make 86 of them clone of the 87th square (or the 1st, depends how you look at it) so I can only edit it and the change will happen on all of them."
1728647,2017-10-31 10:36:45 UTC,"Ah! You are suggesting I create the 86 clones and then exchange positions with the objects that are already where I need the clones? Yes. This works, it is less work than what I was using but it is still quite a lot more work than what I am suggesting as a feature. Specially if you need many clones, you need to hit the exchange positions button once for each clone which if you have a lot will also have a lot of time."
1728647,2017-10-31 11:37:26 UTC,"Yes, I agree... it works, but not a one-and-done solution."
1728651,2018-04-23 11:14:46 UTC,"I'm now on 4.16.3 kernel, and while I haven't encountered freeze since moving to 4.15.13+, the WiFi connection becomes slow/unstable after few minutes. I'm not sure this is connected to the same part of code, or my HW meanwhile degraded a bit (did the 4.4 kernel work without a hitch? I may try to boot it for few days to see if it's HW issue, or still regression in kernel and wifi card driver)."
1728651,2019-12-21 07:14:35 UTC,"Rather old thread, but definitely experiencing a similar problem with the system completely freezing for about 10-15 seconds."
1728651,2018-04-05 09:07:16 UTC,"Upon upgrading to Ubuntu 18.04 beta, which runs kernel 4.15.0-13-generic and iwlwifi 8265 driver firmware 34.0.1, this problem seems to have gone away."
1728651,2019-12-21 18:59:35 UTC,"Okay, so, I remembered disabling CStates in BIOS as well as the other Intel speed throttling settings.  After re-enabling them, I've been streaming data for quite a while, and haven't had the iwlwifi driver crash."
1728651,2018-04-09 11:20:45 UTC,"Just had a system hang on 18.04 due to this. The hangs are definitely much rarer, but do happen."
1728651,2019-12-21 07:19:49 UTC,"follow up ... It [unsurprisingly] doesn't have anything to do with YT, streaming or network usage -- I had closed Firefox and was about to shut the machine when the system froze and another crash occurred."
1728651,2018-04-05 14:01:41 UTC,"On Ubuntu 18.04, the warnings in kern.log still happen, and a kernel oops is reported, but the system doesn't hang."
1728651,2018-01-21 09:51:05 UTC,"I have the same issue on the NUC7i3BN!
Is there already a bugfix available?"
1728651,2018-03-31 12:42:32 UTC,"Am suffering from the same bug on a Thinkpad T470s with an Intel 8265 wifi chip running Ubuntu 17.10, Linux kernel 4.13.0-37-generic, and iwlwifi 31.560484.0. There are multiple reports like the errors below in kern.log. After a while, the machine completely locks up. Interestingly, the system only seems to lock up when transferring files using Syncthing or Resilio Sync."
1728651,2017-12-30 22:44:20 UTC,Based on skimming https://bugzilla.kernel.org/show_bug.cgi?id=195299 I think this might be fixed upstream but didn't make it to kernel 4.13.  When will Ubuntu move to 4.14? :)
1728651,2017-12-30 22:09:06 UTC,I believe I also have this bug on a HP Envy 13-ab002na.  It is a vanilla 17.10 install.
1728651,2017-12-29 20:53:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728651,2017-10-30 16:31:03 UTC,"I don't easily see the firmware hang message in the attached files, so I'm pasting it here:"
1728651,2018-04-02 09:40:33 UTC,"I did switch to mainline kernel 4.15.13 about 10 days back, and so far no single freeze happened."
1728653,2017-10-31 12:18:14 UTC,This bug was fixed in the package evolution-data-server - 3.26.2-1ubuntu1
1728655,2017-10-31 12:18:19 UTC,This bug was fixed in the package evolution - 3.26.2-1
1728664,2017-10-30 17:25:14 UTC,Deleted journal errors attachment because it contained information not relevant to mysql.
1728681,2019-09-25 21:22:55 UTC,Marking Incomplete pending an answer to Łukasz's comment 11.
1728681,2019-09-09 09:35:28 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu7.1
1728681,2019-09-09 09:29:08 UTC,Please include some more information when changing the verification tags (for xenial here). What versions have been used for the verification? Was the test case followed correctly?
1728681,2019-09-09 09:28:04 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu3.4
1728681,2019-09-09 09:25:28 UTC,"The verification of the Stable Release Update for landscape-client has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1728681,2019-08-13 20:24:19 UTC,"Hello Kellen, or anyone else affected,"
1728681,2019-07-25 22:12:24 UTC,"I verified upgrading to the -proposed packages without data_path on bionic and disco.
They installed and upgraded cleanly with the new version."
1728681,2019-05-20 20:12:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728681,2019-07-09 16:42:50 UTC,"Hello Kellen, or anyone else affected,"
1728681,2019-06-21 20:32:38 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu9
1728681,2017-10-30 19:06:00 UTC,"Hello Andreas,"
1728681,2017-10-30 18:46:06 UTC,Do you have any idea how the config file ended up missing that configuration key? Just trying to gauge how frequent this is (hint: it's the fist time I saw this)
1728681,2019-11-12 21:52:35 UTC,"I've just verified this on xenial, with the package from xenial-proposed 16.03-0ubuntu2.16.04.7"
1728681,2019-07-19 18:52:54 UTC,"Hello Kellen, or anyone else affected,"
1728681,2019-11-13 00:08:20 UTC,This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.7
1728685,2020-09-28 12:01:42 UTC,Fix released in git-ubuntu version 1.0
1728685,2017-12-01 16:05:39 UTC,This review should also include the applied branch commits.
1728687,2017-12-21 15:09:28 UTC,"Hi Renardo,"
1728687,2017-12-29 15:29:08 UTC,"Hello Andrew, thanks for your reply. Here is the output from dumpexfat:"
1728687,2017-12-29 15:34:39 UTC,I had overlooked one thing: The root directory contained not only the four directories mentioned but also a small text file called nomo.txt. (Had added that myself.) -- Renardo
1728688,2018-01-18 08:29:00 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-885
1728688,2017-11-01 10:05:07 UTC,"commit b496ae4af8634dc38323754a3119b7defc6d5302
Merge: cfea40e 58eb07b
Author: Krunal Bauskar <email address hidden>
Date:   Wed Nov 1 15:33:35 2017 +0530"
1728688,2017-11-01 14:23:10 UTC,"Thanks for resolving this so quickly. Any chance of releasing this in the near future?
BTW, I had a quick look at http://jenkins.percona.com but couldn't find a Debian build that would include this commit."
1728688,2017-11-02 02:54:06 UTC,"Lukasz,"
1728688,2017-11-02 13:00:37 UTC,"Hi Krunal,"
1728696,2017-12-08 09:09:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728696,2018-06-01 17:38:08 UTC,This also happens using Kubuntu 18.04
1728697,2017-10-30 19:39:12 UTC,still note resolved
1728697,2020-02-14 02:13:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728709,2019-11-23 18:09:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728709,2019-11-23 18:13:06 UTC,This documentation problem still present after two years in 18.04.
1728711,2019-01-27 18:54:26 UTC,It is great that Disco is not affected by this bug.
1728711,2019-04-20 13:08:43 UTC,"Contrast is normal with all preinstalled themes on all releases - 16.04 LTS, 18.04 LTS, 18.10 and 19.04."
1728715,2018-04-01 17:01:08 UTC,"18.04 LTS with all updates, bug exists."
1728715,2019-03-29 16:50:08 UTC,Still a problem for Ubuntu MATE 19.04 beta2.
1728717,2017-10-31 12:58:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728721,2017-11-05 23:24:13 UTC,"If a unit goes into an error state, it won't be automatically removed. I don't think remove-unit likes to remove units in error either, and sadly there's no --force option. I think we do need to consider supporting ""remove-unit --force"" to allow such situations to be clean up."
1728723,2019-09-10 10:08:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728723,2017-11-01 13:18:14 UTC,This was fixed in 3.1.4-2 which was synced into ubuntu for zesty and later.
1728723,2017-10-30 21:35:44 UTC,"Looking into git, this problem seem to have been introduced with the 3.0.0 release:"
1728732,2017-10-31 22:13:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/516796"
1728732,2017-11-06 22:45:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518119"
1728732,2019-10-02 21:26:46 UTC,This bug is also fixed by https://review.opendev.org/#/c/685181/
1728732,2019-10-05 17:57:04 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/516796
Reason: Looks to be a dupe of https://review.opendev.org/#/c/518119"
1728732,2019-10-07 18:39:48 UTC,"Change abandoned by Eric Fried (<email address hidden>) on branch: master
Review: https://review.opendev.org/518119
Reason: I believe this is covered by [1]. If not, please feel free to restore and update to pass tests."
1728732,2020-04-08 11:12:10 UTC,"Reviewed:  https://review.opendev.org/685181
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1e907602e37fb55bbe5a20164db6d074f87369af
Submitter: Zuul
Branch:    master"
1728734,2017-10-30 22:27:58 UTC,"BTW, the bug was reported here:"
1728742,2018-02-02 12:46:26 UTC,Looks like there are old curtin packages there (from Jan last year):
1728742,2018-02-08 14:21:10 UTC,Excellent; thanks for testing.
1728742,2018-02-02 14:48:44 UTC,"On Fri, Feb 2, 2018 at 6:46 AM, Dmitrii Shcherbakov <
<email address hidden>> wrote:"
1728742,2018-02-07 11:38:20 UTC,"Ryan, haven't realized you've updated the package in the ppa already."
1728742,2018-02-07 15:16:06 UTC,"On Wed, Feb 7, 2018 at 5:38 AM, Dmitrii Shcherbakov <
<email address hidden>> wrote:"
1728742,2018-02-08 13:05:01 UTC,"HWE (no patch applied)
https://paste.ubuntu.com/26537602/"
1728742,2018-02-08 23:01:10 UTC,Debdiff for bionic
1728742,2018-01-30 21:34:21 UTC,"I've updated bcache-tools and curtin in ppa:raharper/bugfixes , please give those a test and see if that fixes the remaining issues."
1728742,2018-02-14 20:19:29 UTC,"The attachment ""fix_bcache_dname.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1728742,2018-02-16 14:36:29 UTC,"Ryan forwarded this to bcache-tools upstream on github.
 https://github.com/koverstreet/bcache-tools/pull/1"
1728742,2018-05-09 14:25:58 UTC,"Now that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145 is released, this work to SRU back to xenial can proceed."
1728742,2018-05-23 18:48:17 UTC,SRU: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1772044
1728742,2018-06-01 14:02:23 UTC,"This bug is believed to be fixed in curtin in version18.1-17-gae48e86f-0ubuntu1. If this is still a problem for you, please make a comment and set the state back to New"
1728742,2018-02-01 22:34:56 UTC,"On Thu, Feb 1, 2018 at 4:09 PM, Dmitrii Shcherbakov <
<email address hidden>> wrote:"
1728742,2018-02-08 23:02:08 UTC,"Debdiff for Xenial, this will need an SRU to Xenial and Trusty, probably Artful as well."
1728742,2018-02-01 22:09:26 UTC,"Ryan,"
1728742,2018-01-29 17:23:40 UTC,.
1728742,2018-02-01 19:40:16 UTC,Ran a few tests.
1728742,2018-02-01 19:59:05 UTC,"On Thu, Feb 1, 2018 at 1:40 PM, Dmitrii Shcherbakov <
<email address hidden>> wrote:"
1728742,2018-01-30 16:07:16 UTC,"The bcache-export-cached udev script did not skip cache devices and would emit a cache device dev.uuid; I'm testing a change to ignore those and that appears to get things working on my single cache, multiple backing device test-case."
1728742,2018-01-29 18:05:02 UTC,"curtin-install-cfg.yaml
https://paste.ubuntu.com/26484968/"
1728742,2018-01-29 17:56:16 UTC,Untested version of a patch to curtin to emit bcache dname's using the backing device uuid.
1728742,2018-01-27 16:35:35 UTC,Tested #6:
1728742,2017-12-01 17:57:00 UTC,"For the curtin side,  the plan is to do two things."
1728742,2017-12-01 17:53:46 UTC,A version of bcache-tools for xenial with the above workaround is available here:
1728742,2017-12-01 17:52:31 UTC,We've been poking at this for a bit and I'll summarize some things.
1728742,2017-11-19 14:24:52 UTC,I think the kernel side of it needs consideration but inherently persistent /dev/bcache<i> cannot be provided due to the fact that there is no deterministic enumeration and /dev/bcache<i> names cannot be changed afterwards (only symlinks can be created).
1728742,2017-11-10 22:32:03 UTC,See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/comments/8
1728742,2017-11-01 14:19:56 UTC,"In working on getting a udev rule fixed for bcache dname, I've filed this bug as well:"
1728742,2017-10-30 23:43:48 UTC,Copied from a private bug:
1728744,2017-11-21 17:27:24 UTC,That issue is reproduceable with also Maxwell gpu's and Skylake cpu laptops.
1728746,2018-05-01 10:31:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728746,2018-12-05 12:14:58 UTC,this bug is fixed with https://aur.archlinux.org/cgit/aur.git/tree/dont-ignore-xshape-when-saving.patch?h=easystroke-git
1728747,2017-11-11 20:24:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728753,2018-02-14 18:41:32 UTC,tested in 3.0.3 same behaviour as listed above
1728753,2019-08-29 16:14:44 UTC,tested in 3.3.2 same behavior as above.
1728753,2019-11-04 16:40:45 UTC,"See bug #1768978 for a related report, which doesn't mention ""Alert Msg"" as an option, so may be slightly different."
1728753,2019-11-04 18:52:33 UTC,"The Status column from Comment #2 is the ""Status Icon Column"", which shows if a copy has been edited and saved or not.
Josh"
1728755,2017-11-09 12:41:38 UTC,This bug was fixed in the package gnome-tweak-tool - 3.26.3-1ubuntu1
1728760,2017-11-16 17:07:50 UTC,"After upgrading from Zesty (with Docker installed) to Artful, I noticed the switch to the lowlatency kernel (since it caused me a little DKMS pain with the VirtualBox package), but otherwise paid it little mind. Later I realized that my laptop was constantly freezing up (could not even move the mouse pointer) when just one process was consuming most of a single CPU core, which had never been true before. After finding this issue, I tried booting into the generic kernel (ESC to get the Grub menu) and then removing the lowlatency kernel (image & headers). So far so good. Unclear to me whether updating `aufs-tools` at this point would make any difference, since it sounds like this change would only affect new upgrades."
1728760,2017-11-17 00:01:32 UTC,This bug was fixed in the package aufs-tools - 1:4.1+20161219-1ubuntu0.1
1728760,2017-11-07 19:30:49 UTC,"Hello James, or anyone else affected,"
1728760,2017-11-16 21:24:02 UTC,I followed the test case in the bug description and can confirm that after enabling artful-proposed in my /etc/apt/sources.list file the lowlatency kernel is no longer offered to be installed.
1728760,2017-11-07 18:50:46 UTC,"It's not the demotion of the aufs-dkms relationship from depends to recommends that triggers this, but that the 17.04 aufs-tools had no dependency at all and 17.10 adds the recommends."
1728760,2017-11-17 00:01:36 UTC,"The verification of the Stable Release Update for aufs-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1728760,2017-11-07 03:21:21 UTC,"Sorry for not responding sooner. I've attached what seem to be the most relevant files, if there's any others of interest let me know. This log message seems to be relevant:"
1728760,2017-11-07 01:32:36 UTC,"This is exactly what happened to me as well. Computer is rather powerful, so not necessarily an obvious candidate for ll kernel: 16GB, core i7, NVMe M.2 SSD."
1728760,2017-10-31 15:03:39 UTC,Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance.
1728760,2017-10-31 04:34:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1728760,2017-11-07 18:33:59 UTC,"Thanks for digging into this, this is the result of a change in the aufs-tools package."
1728763,2018-08-19 18:50:30 UTC,Any news on this one? Did you test with 18.04 yet?
1728763,2017-10-31 02:21:50 UTC,"$ lsb_release -rd
Description:	Ubuntu 17.10
Release:	17.10"
1728763,2018-01-11 13:53:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728763,2018-04-24 12:11:36 UTC,"This is now fixed for me, I noticed just now.  Dpkg tells me the package hasn't changed.  I just rebooted with a kernel upgrade to 4.13.0-39-generic, but I don't know if it that was the trigger for it starting to work again or not.  I haven't checked it for months."
1728764,2018-12-05 18:14:50 UTC,"Hi! This also affects me on Ubuntu 18.04, using the same package (gnome-screenshot/bionic,now 3.25.0-0ubuntu2 amd64)."
1728764,2018-12-07 14:53:45 UTC,Can you try starting gnome-screenshot from a command line? does it print any error when taking the screenshot or saving it?
1728764,2019-01-10 20:16:14 UTC,"Hello,"
1728764,2018-12-10 04:59:32 UTC,"My keybindings are changed, and it works now. I do believe I had changed keybindings, but I'm not 100% sure."
1728764,2018-06-14 11:43:20 UTC,"I've managed to reproduce this bug by changing the default hotkey of ""Save a screenshot of an area to pictures"" from `Shift + Print` to `Shift + Ctrl + Print`."
1728764,2018-12-09 04:10:04 UTC,From OP:
1728764,2017-12-04 14:00:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728764,2017-11-20 19:50:34 UTC,"Still buggin' out. I should add that the screen both flashes and makes the shutter sound effect, then just doesn't even try to save the file."
1728764,2018-12-09 15:16:46 UTC,The way Che described is to change keybinding and looks like a different issue? Did everyone getting the problem change their keybindings?
1728771,2017-10-31 05:01:06 UTC,I've reproduced this on a different machine using an Ubuntu mainline build of the v4.13 kernel too.
1728771,2017-10-31 15:20:20 UTC,Also reproduced with kernel 4.4.0-98-lowlatency
1728771,2018-05-31 03:26:57 UTC,This affects me when I try to run a Singularity (sandbox) container from my (encrypted) home folder. Linux 4.15.0-22-generic x86_64 on Ubuntu 18.04.
1728771,2018-05-31 03:33:36 UTC,"[ 2273.365506] BUG: unable to handle kernel NULL pointer dereference at 0000000000000030
[ 2273.365512] IP: ecryptfs_privileged_open+0x51/0x180
[ 2273.365513] PGD 0 P4D 0
[ 2273.365515] Oops: 0000 [#1] SMP PTI
[ 2273.365516] Modules linked in: ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overlay pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep dm_crypt binfmt_misc nls_iso8859_1 arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass uvcvideo crct10dif_pclmul videobuf2_vmalloc snd_hda_codec_realtek crc32_pclmul videobuf2_memops ghash_clmulni_intel snd_hda_codec_generic videobuf2_v4l2 videobuf2_core pcbc videodev media btusb btrtl snd_seq_midi btbcm btintel iwlmvm aesni_intel bluetooth snd_hda_intel snd_seq_midi_event mac80211 aes_x86_64 ecdh_generic
[ 2273.365541]  crypto_simd glue_helper snd_hda_codec snd_rawmidi cryptd snd_hda_core intel_cstate intel_rapl_perf snd_hwdep iwlwifi snd_pcm cfg80211 snd_seq rtsx_pci_ms idma64 joydev memstick virt_dma input_leds wmi_bmof thinkpad_acpi intel_wmi_thunderbolt serio_raw mei_me intel_lpss_pci snd_seq_device mei intel_pch_thermal intel_lpss nvram shpchp snd_timer snd soundcore mac_hid acpi_pad tpm_crb sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt rtsx_pci_sdmmc psmouse ptp fb_sys_fops pps_core nvme drm rtsx_pci nvme_core wmi i2c_hid video hid
[ 2273.365571]  pinctrl_sunrisepoint
[ 2273.365573] CPU: 6 PID: 29901 Comm: action-suid Tainted: G           OE    4.15.0-22-generic #24-Ubuntu
[ 2273.365574] Hardware name: LENOVO 20HH000AUS/20HH000AUS, BIOS N1UET46W (1.20 ) 02/26/2018
[ 2273.365576] RIP: 0010:ecryptfs_privileged_open+0x51/0x180
[ 2273.365577] RSP: 0018:ffffb33145e2bb48 EFLAGS: 00010246
[ 2273.365578] RAX: ffffb33145e2bb70 RBX: ffff948a0f48fe88 RCX: ffff948bf02eb780
[ 2273.365579] RDX: ffffffff926e4b40 RSI: ffffffff91cc2d53 RDI: ffffb33145e2bb68
[ 2273.365580] RBP: ffffb33145e2bbb8 R08: ffff948c405a7060 R09: ffff948aa2ca1ab0
[ 2273.365581] R10: 0000007374736f68 R11: 0000000000000005 R12: 0000000000000000
[ 2273.365582] R13: ffff948bf02eb780 R14: 0000000000000000 R15: ffff948b67ff7200
[ 2273.365583] FS:  00007f13be06d580(0000) GS:ffff948c40580000(0000) knlGS:0000000000000000
[ 2273.365584] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2273.365585] CR2: 0000000000000030 CR3: 000000026c512001 CR4: 00000000003606e0
[ 2273.365586] Call Trace:
[ 2273.365589]  ecryptfs_get_lower_file+0x7d/0xc0
[ 2273.365591]  ecryptfs_open+0x71/0x200
[ 2273.365593]  do_dentry_open+0x1c2/0x310
[ 2273.365594]  ? ecryptfs_flush+0x50/0x50
[ 2273.365596]  vfs_open+0x4f/0x80
[ 2273.365598]  path_openat+0x66e/0x1770
[ 2273.365599]  ? filename_lookup+0xf2/0x190
[ 2273.365602]  do_filp_open+0x9b/0x110
..."
1728771,2017-10-31 04:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1728781,2017-12-09 22:07:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728809,2017-10-31 06:58:31 UTC,"I forgot to give you
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 17.10
Release:	17.10
Codename:	artful
and I forget the rest"
1728809,2017-11-06 17:14:21 UTC,"$ apt-cache policy g++
g++:
  Installed: 4:7.2.0-1ubuntu1
  Candidate: 4:7.2.0-1ubuntu1
  Version table:
 *** 4:7.2.0-1ubuntu1 500
        500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status"
1728821,2017-12-24 11:49:07 UTC,I think 'shared' field should be hidden if a user has enough permission for 'shared' like [1]
1728830,2017-10-31 07:49:06 UTC,This bug relates to https://bugs.launchpad.net/horizon/+bug/1231330
1728830,2017-12-24 11:54:39 UTC,"In my understanding, firewall group is associated with a port (including a router interface?). horizon bug 1231330 mainly focuses on adding more resources like load balancer. If I understand correctly, this bug is requesting to show more information like firewall group. We need more discussion on what kind of GUI support is expected in this bug."
1728839,2018-02-15 23:58:07 UTC,for xpdf 3.04-6
1728846,2017-10-31 13:57:37 UTC,"Change abandoned by Amir Mofakhar (<email address hidden>) on branch: master
Review: https://review.openstack.org/516387"
1728867,2017-11-09 22:12:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1728867,2017-11-30 15:49:37 UTC,"As the maintainer of the mysql2 gem, I'm not able to work around this in the client application, it really needs to be fixed in the client library. Thanks for your attention!"
1728883,2017-11-07 20:24:28 UTC,"Reviewed:  https://review.openstack.org/516584
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=c3c2713c40c6f5b45143e73f57a8034514576500
Submitter: Zuul
Branch:    stable/ocata"
1728883,2017-10-31 10:27:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/516581"
1728883,2017-10-31 10:35:46 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/516584"
1728883,2017-11-01 12:27:43 UTC,"Reviewed:  https://review.openstack.org/516581
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=95e99163f1f14fab03a96330eabf0119a500dc8a
Submitter: Zuul
Branch:    stable/pike"
1728883,2017-12-11 21:48:51 UTC,This issue was fixed in the openstack/heat 9.0.2 release.
1728883,2017-12-11 21:49:17 UTC,This issue was fixed in the openstack/heat 8.0.6 release.
1728886,2020-02-12 17:20:49 UTC,https://review.opendev.org/#/c/702249/
1728886,2019-11-27 17:15:11 UTC,http://logs.rdoproject.org/openstack-periodic-master/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-7-ovb-1ctlr_2comp-featureset021-master/438fdbb/logs/stestr_results.html
1728886,2019-12-12 12:01:11 UTC,http://logs.rdoproject.org/openstack-periodic-master/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-7-ovb-1ctlr_2comp-featureset021-master/438fdbb/logs/undercloud/var/log/tempest/tempest_run.log.txt.gz
1728886,2020-03-30 10:23:12 UTC,"Based on the comments above, mainly #8, I'm closing this for Tempest as the issue got fixed in OVN in neutron project."
1728886,2020-03-30 10:21:45 UTC,"Hi Maciej,"
1728886,2019-12-19 15:44:40 UTC,I wrote this patch [0] and it fixes the issue. I think that the analysis on the bug description is not really accurate. Just by setting the OVN addresses field to 'unknown' when port security is disabled is allowing traffic on a spoofed MAC.
1728886,2020-03-27 16:06:26 UTC,I see this got fixed in neutron and the test has been passing over the last 3 months:
1728886,2020-02-21 16:41:00 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1728886,2020-03-30 08:03:48 UTC,"Hey Martin,"
1728886,2019-12-06 14:19:19 UTC,not sure what the story on this one is. @weshay the logs you point to in comment #1 are from featureset021.
1728890,2017-10-31 15:33:02 UTC,"On my syslog I have:
Oct 31 10:37:13 TimPassingham gnome-software[23426]: failed to rescan: Failed to parse /usr/share/applications/classicmenu-indicator.desktop.dpkg-new file: cannot process file of type text/plain
Oct 31 10:37:13 TimPassingham gnome-software[23426]: failed to rescan: Failed to parse /usr/share/applications/classicmenu-indicator.desktop.dpkg-tmp file: cannot process file of type text/plain
Oct 31 10:37:13 TimPassingham gnome-software[23426]: failed to rescan: Failed to parse /usr/share/applications/classicmenu-indicator.desktop file: cannot process file of type application/x-desktop"
1728890,2017-10-31 21:16:50 UTC,I tried something else.  First I killed the classicmenu-indicator process.  Then I ran it from a terminal using:
1728890,2017-11-02 14:20:01 UTC,I decided to recheck everything.
1728890,2017-11-03 15:51:09 UTC,"Another wrinkle to add to this is that the behaviour is different depending on which desktop I log in with, and there are inter-dependencies with other extensions."
1728890,2017-11-08 11:23:05 UTC,Me again...
1728890,2017-12-16 15:07:12 UTC,"I have the same problems with a fresh install of 17.10.  In both X and Wayland modes, I only have in-inline menus which are very hard to use."
1728892,2018-01-24 22:31:39 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1454
1728900,2017-11-01 15:31:06 UTC,"As Colin pointed out, this isn't a code bug, the gerrit topic URLs in the whiteboard can be updated in the blueprints in launchpad if someone cares to update them."
1728900,2017-11-02 02:02:18 UTC,"It's true that the whiteboard can be updated manually.
But why not correct the initial url to reduce the complicated and meaningless work?"
1728900,2017-10-31 12:28:18 UTC,"Eg: https://blueprints.launchpad.net/nova/+spec/migration-allocations.
I'm not sure which component affects this, so report it to find it out."
1728900,2017-10-31 11:50:08 UTC,What web page in particular is this?  As far as I can see we have nothing Gerrit-specific in our code.
1728900,2017-10-31 15:43:53 UTC,"That's just plain text editable by anyone who can edit that whiteboard.  It's not a code bug anywhere, but reassigning to nova since at least some of the people who read its bugs can presumably sort this out."
1728905,2019-08-07 19:04:24 UTC,UI has been deprecated
1728931,2017-10-31 12:51:38 UTC,$ while cmake-build-debug/bin/mir_acceptance_tests --gtest_filter=ServerDisconnect.is_detected_by_client; do :; done
1728931,2017-10-31 15:36:50 UTC,"I've not yet tracked down where, but the server is occasionally segfaulting during shutdown."
1728931,2017-10-31 16:49:51 UTC,The segfault happens when there are only two threads still active:
1728931,2017-10-31 17:01:26 UTC,"Yes, info sharedlibrary shows stub-graphics isn't loaded. And if I prevent it unloading then I can't reproduce the crash."
1728931,2017-11-03 15:25:00 UTC,Syncing task from Mir.
1728932,2017-10-31 12:45:31 UTC,https://bugs.launchpad.net/ubuntu/+source/linux/+bug/194676
1728932,2017-10-31 12:47:04 UTC,"Well, I agree that it is a security problem if the user is able to kill a process that he must not be able to kill..."
1728932,2017-10-31 13:00:11 UTC,This change was made by a bot.
1728952,2017-10-31 13:17:02 UTC,"We've been seeing this type of behavior occasionally, but it seemed inconsistent and we hadn't yet been able to pinpoint whether it was related to particular columns and/or web browsers."
1728982,2019-10-16 14:43:53 UTC,"An upload of simplestreams to xenial-proposed has been rejected from the upload queue for the following reason: ""See https://bugs.launchpad.net/charms/+source/glance-simplestreams-sync/+bug/1611987/comments/21""."
1728982,2019-09-20 09:50:16 UTC,"For Xenial SRU, please read summary at:"
1728982,2019-10-16 16:12:03 UTC,TL;DR version:
1728982,2018-04-23 13:41:54 UTC,"An upload of simplestreams to artful-proposed has been rejected from the upload queue for the following reason: ""No SRU information provided in the bug. No update from thetime. Please re-upload after the required bits are filled-in.""."
1728982,2017-11-13 21:25:44 UTC,This bug was fixed in the package simplestreams - 0.1.0~bzr454-0ubuntu1
1728982,2018-06-25 14:53:00 UTC,"This bug is believed to be fixed in simplestreams in version 0.1.0. If this is still a problem for you, please make a comment and set the state back to New"
1728982,2018-04-12 09:16:58 UTC,Could this bug be updated to include the SRU-required information in its description? Thank you!
1729000,2017-11-27 13:37:08 UTC,I'm seeing the same behaviour on 16.04.3 LTS.
1729000,2017-12-04 21:52:33 UTC,This solves a problem for me:
1729000,2018-02-16 13:59:48 UTC,"I am getting similar message at boot but not to Windows target, instead to a DELL EQUALOGIC 100E
Symptom is system hang for a few seconds during boot then it works ok"
1729000,2017-11-27 13:04:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729010,2018-03-20 07:05:34 UTC,"You need to do ""git cherry-pick 13cfc732160f7bc7e596128ce34cda361c556966"" if the commit is not included."
1729010,2018-03-20 04:04:38 UTC,"(I have confirmed that building at 13cfc732160f7bc7e596128ce34cda361c556966 does not exhibit the bug, fwiw)"
1729010,2018-03-20 04:03:23 UTC,having some trouble with the bisect:
1729010,2018-03-14 06:51:52 UTC,"If you can build/test it locally, it should be quite quick:"
1729010,2018-03-07 03:09:54 UTC,"I can, but can't promise an SLA ;)"
1729010,2018-03-07 02:29:12 UTC,"Great. We should still backport fixes to Artful though. It might be time consuming to install and test multiple kernels.
Are you up to the task? ;)"
1729010,2018-03-06 15:13:28 UTC,appears to be gone in 4.15.0-11 as well
1729010,2018-03-02 05:06:45 UTC,Thanks for your testing!
1729010,2018-03-01 04:43:45 UTC,i have not yet experienced it in v4.16-rc2
1729010,2018-03-01 02:48:55 UTC,"> On Mar 1, 2018, at 2:27 AM, Joe Barnett <email address hidden> wrote:
>
> in limited testing so far, v4.16-rc2 appears better
"
1729010,2018-02-28 18:27:54 UTC,"in limited testing so far, v4.16-rc2 appears better"
1729010,2018-02-21 06:43:54 UTC,"USB mass storage devices appear to have the same problem as the hub i was using, while usb keyboards continue to work ok even when the hub & mass storage devices fail."
1729010,2018-02-21 06:42:57 UTC,"reproduced the issue on v4.13rc3.  both rc1 and rc2 appear to be very unstable resulting in full graphical lockups.  believe I reproduced the issue on rc2 as well, but hard to tell with the general instability."
1729010,2018-03-21 03:32:01 UTC,"ok, i'm going to go with bionic's kernel."
1729010,2017-11-28 15:23:28 UTC,"I should probably test a few more suspend cycles, but so far on 4.12.0-11-generic I'm not seeing the issue"
1729010,2017-11-15 06:55:28 UTC,"> On 14 Nov 2017, at 11:29 PM, Joe Barnett <email address hidden> wrote:
>
> It did not occur on previous ubuntu releases, and didn't occur during
> the artful dev cycle either.  It seems to be on a suspend-by-suspend
> basis: after reproducing, another suspend cycle seems to ""fix"" it at
> least some of the time.
"
1729010,2017-11-14 15:29:33 UTC,"It did not occur on previous ubuntu releases, and didn't occur during the artful dev cycle either.  It seems to be on a suspend-by-suspend basis: after reproducing, another suspend cycle seems to ""fix"" it at least some of the time."
1729010,2017-11-14 08:35:33 UTC,"You were using the system from 15.10, did this issue occur in previous kernel versions?"
1729010,2017-11-13 15:30:04 UTC,Reproduced on mainline as well.
1729010,2017-11-07 16:17:11 UTC,"Reproduced on 4.13.0-12, trying mainline now"
1729010,2017-11-01 14:32:31 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1729010,2017-10-31 14:30:10 UTC,This change was made by a bot.
1729010,2018-02-22 15:27:20 UTC,"Hmm, there are several subsystems might affect xHC, so we need to bisect between v4.12 and v4.13-rc3."
1729010,2017-11-30 05:28:20 UTC,"> On 28 Nov 2017, at 11:23 PM, Joe Barnett <email address hidden> wrote:
>
> I should probably test a few more suspend cycles, but so far on
> 4.12.0-11-generic I'm not seeing the issue
"
1729010,2017-11-06 17:25:54 UTC,"its not instantly reproducible so it'll take a while to ensure it's really gone, but i'll run with my last installed kernel (4.13.0-12) for a while and see, and then also try the latest mainline 4.14 and report back"
1729012,2017-10-31 14:37:06 UTC,"I'm not sure, but this may qualify as `regression-release`, because I actually use xdg-open to open mp3 files, which worked reliably in 17.04 but is failing in 17.10 because of this `gio open` problem."
1729012,2017-11-07 13:37:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1729016,2017-10-31 23:33:15 UTC,"For what it's worth, in our upstream packages we don't have a suggests or recommends on www-browser - the Web-based configuration is an entirely optional component."
1729021,2017-11-08 13:45:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1729021,2017-11-20 16:54:55 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1010.15
1729023,2017-11-08 13:45:20 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1729023,2017-11-20 16:54:55 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1010.15
1729030,2017-11-09 09:54:24 UTC,"It's not bluetoothd (BlueZ) crashing. The log information shows the kernel crashing in 'bluetooth' which is a kernel module. This will of course cause bluetoothd to stop working properly, but the bug is not in bluetoothd, it's in the kernel."
1729030,2017-11-26 18:07:35 UTC,apport information
1729030,2017-11-26 18:07:36 UTC,apport information
1729030,2017-11-26 18:07:37 UTC,apport information
1729030,2017-11-26 18:07:38 UTC,apport information
1729030,2017-11-26 18:07:39 UTC,apport information
1729030,2018-01-07 23:38:13 UTC,My computer (Depp Precision 5510 with Ubuntu 17.10 - actually Pop!_OS - fresh install) is affected by the same kind of bug.
1729030,2017-11-26 18:07:42 UTC,apport information
1729030,2017-11-26 18:07:43 UTC,apport information
1729030,2017-11-26 18:07:34 UTC,apport information
1729030,2018-01-08 10:42:04 UTC,"Here is full dmesg.
In it there is this bug :"
1729030,2018-01-08 10:45:24 UTC,"I also comment on this bug although it is tagged as ""expired"" :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718864"
1729030,2017-11-26 18:07:40 UTC,apport information
1729030,2017-11-26 18:07:33 UTC,apport information
1729030,2017-11-26 18:07:30 UTC,apport information
1729030,2017-11-14 20:32:10 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1729030,2017-11-26 18:07:28 UTC,apport information
1729030,2017-11-26 18:07:27 UTC,apport information
1729030,2017-11-26 18:07:26 UTC,apport information
1729030,2017-11-26 18:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1729030,2017-11-26 17:37:36 UTC,dmesg output after a crash:
1729030,2017-11-20 08:48:38 UTC,This is the dmesg output before a crash. I'll add another dmesg output when I get the next crash.
1729030,2017-11-20 03:10:49 UTC,Can you provide full dmesg?
1729030,2017-11-19 19:54:00 UTC,@joseph
1729030,2017-11-26 18:07:32 UTC,apport information
1729030,2017-11-09 09:56:16 UTC,Please try a slightly older kernel or two from here:
1729030,2017-11-09 09:24:05 UTC,"I'm using stock Ubuntu 17.10, so that's bluez from the archive: bluez/artful,now 5.46-0ubuntu3 amd64 [installed]"
1729030,2017-11-08 20:22:54 UTC,@Merlijn
1729032,2017-10-31 18:17:43 UTC,"Note that after forcing a new leader (by stopping the juju agent of the current leader), the statuses did eventually become correct:
Unit              Workload  Agent  Machine  Public address  Ports  Message
ubuntu-leader/0*  active    idle   0        10.67.99.206           l-e leader: leader=ubuntu-leader/0 x=2
ubuntu-leader/1   active    idle   1        10.67.99.243           l-s-c leader: leader=ubuntu-leader/0 x=2
ubuntu-leader/2   active    idle   2        10.67.99.79            c-c leader: leader=ubuntu-leader/0 x=2"
1729033,2017-11-03 07:32:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/517559"
1729035,2017-11-21 16:24:34 UTC,"Snapshot is up to 611 MB, can I upload any way? Maybe a link for you to download is possible?"
1729035,2017-11-22 15:14:14 UTC,Here you can download the snapshot:
1729035,2017-11-03 10:27:32 UTC,No reply? :(
1729035,2017-11-20 18:27:38 UTC,"Jorge, please attach full diagnostic snapshot."
1729035,2017-12-18 10:32:35 UTC,No answers to this?
1729044,2017-11-02 14:56:46 UTC,release: stable/pike
1729044,2017-11-02 11:24:54 UTC,"Need to add more detail on this case, release version, backup driver, command or API, and the most important if you can provide, the backup-log."
1729044,2017-11-03 03:52:20 UTC,Can't reproduce this failure with stable/pikre release on my own devstack environment :)
1729044,2017-11-07 09:57:25 UTC,"The above usecase was with 1.7 TB ( ~1700GB), To simplify I tried to recreate using the 50 GB just to show the locked memory usage by cinder-backup."
1729051,2017-12-14 16:17:32 UTC,This bug was fixed in the package dkms - 2.3-3ubuntu4
1729051,2017-11-16 01:34:24 UTC,"Yes, that file is the same. What's different is https://github.com/dell/dkms/blob/master/dkms. The dkms script that's distributed with Debian/Ubuntu looks for DEBIAN_BUILD_ARCH in the control file."
1729051,2017-11-16 01:04:53 UTC,It looks the same to me.
1729051,2017-11-16 00:49:01 UTC,"I haven't because this is a Debian/Ubuntu-specific bug. IIRC
Debian/Ubuntu's file is different from vanilla dkms'."
1729051,2017-11-30 19:40:29 UTC,It's been almost a month and people are still tripping over this bug. Is anyone looking at this at all?
1729051,2017-11-10 20:37:44 UTC,"Is anyone actively looking at this? I uploaded a patch, it just needs to be tested and merged."
1729051,2017-10-31 20:34:43 UTC,"The attachment ""fix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1729051,2017-10-31 18:09:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729051,2017-11-15 21:56:16 UTC,Have you submitted it to the upstream developers of dkms on github?  The file is included there and the project can be found here:
1729064,2017-11-01 13:57:25 UTC,Thanks for filing this bug in Ubuntu.
1729064,2017-11-01 14:26:43 UTC,"It worked out of the box in artful, so the fix is somewhere in between xenial and artful."
1729064,2017-11-01 14:57:03 UTC,"On Wed, Nov 1, 2017 at 7:26 AM, Andreas Hasenack <email address hidden> wrote:

> It worked out of the box in artful, so the fix is somewhere in between
> xenial and artful.
"
1729064,2017-11-01 15:24:17 UTC,"Yes, recommends are installed by default in this out-of-the box xenial container I used. And yes, postgresql (server) is a recommends only."
1729066,2019-10-25 21:23:27 UTC,"Hello, the version in the Ubuntu repos is quite old. Please try using one of the project's officials PPA, either the Daily or the Stabel One."
1729066,2018-07-09 07:29:46 UTC,"Michael, the patch file is at the top of my message. You have to save that patch file to your computer (for example via a right-click: Save Link As…). Then on your Terminal, you change the directory/folder to that location (via the command cd, for example). Then, you can go for that patch command."
1729066,2018-07-08 00:03:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729066,2018-07-08 00:02:18 UTC,I have the same problem with QtQR.  When I try to save crash. Using Ubuntu 18.04 LTS.  I am new to Linux.  Alexander Traud  can you please supply the fix with the full sudo patch.  This is what I get when I run your fix
1729066,2018-04-06 12:26:58 UTC,"The attachment ""filename_tuple.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1729066,2018-04-06 09:34:58 UTC,"Facing the same traceback while hitting the button 'Save QRCode' in Ubuntu 17.10 and Ubuntu 18.04 LTS. Attached is a patch, which fixed the issue for me. Because Python is a scripting language, you can apply that patch directly without any recompiling:
sudo patch -p0 <./filename_tuple.patch"
1729104,2017-11-09 15:13:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729105,2017-11-20 11:53:03 UTC,This bug was fixed in the package linux - 4.4.0-101.124
1729106,2017-11-03 06:44:52 UTC,This bug was fixed in the package gnome-boxes - 3.26.2-1
1729107,2017-11-20 11:53:03 UTC,This bug was fixed in the package linux - 4.4.0-101.124
1729108,2017-11-06 18:35:33 UTC,This bug was fixed in the package dconf-editor - 3.26.2-1
1729164,2017-11-01 14:08:23 UTC,"sorry, I mean, which upstream package is at fault - Wayland or Aisleriot?"
1729164,2017-11-01 04:09:26 UTC,This looks like it is due to the stricter environment used by Wayland which is the new default display server in Ubuntu 17.10.
1729170,2018-06-27 03:46:31 UTC,"additionally, C-1 and C-n in simple-scan do nothing (they worked in 17.04 with unity but not in 17.10 and 18.04 with gnome)"
1729194,2018-01-26 18:35:27 UTC,"127.0.1.1 is not the address of systemd-resolved, as you noted; it's the address used by dnsmasq.  It sounds like your network-manager config is pointing to dnsmasq, which is no longer the default in 17.10, and should have been dropped from your config on upgrade from 16.10 to 17.04.  Can you please attach the /etc/NetworkManager/NetworkManager.conf from the affected system?"
1729194,2018-01-29 23:47:14 UTC,Here's the configuration :
1729194,2018-08-07 09:40:41 UTC,Fixed my dnsmasq systemd-resolve race with dnsmasq config.
1729194,2017-11-01 19:21:15 UTC,"Some more troubleshooting, I've found that if I manually set my nameserver to 127.0.0.53 systemd-resolver starts working again. However everytime that a wifi network connects or disconnects, it switches back to `127.0.0.1`"
1729194,2017-12-29 19:39:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729211,2017-11-01 14:50:57 UTC,Agreed that the tarballs link is dated. The document needs to be updated.
1729211,2017-12-06 11:36:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526037"
1729211,2019-06-24 09:16:37 UTC,"Reviewed:  https://review.opendev.org/526037
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=4bcb8a026c6002e546ad50686f1f1b2903785cb3
Submitter: Zuul
Branch:    master"
1729211,2019-09-25 08:41:39 UTC,This issue was fixed in the openstack/trove 12.0.0.0rc1 release candidate.
1729218,2018-04-27 17:31:24 UTC,It looks like a database is missing.
1729218,2019-04-11 06:08:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729223,2017-11-07 19:51:00 UTC,Interesting idea...
1729223,2020-09-11 15:44:22 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1729231,2017-11-22 15:16:17 UTC,Another failure on HA xenial/mitaka deployment. This time looks like an issue talking to keystone:
1729231,2017-11-28 14:44:46 UTC,"Reviewed:  https://review.openstack.org/523379
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=9b7a81664a28383db839f993027498c20f307808
Submitter: Zuul
Branch:    master"
1729235,2018-05-23 19:16:39 UTC,"Removing packages from cosmic-proposed:
 ppx-core 113.33.03-1ubuntu4 in cosmic
Comment: FTBFS; LP: #1729235, Debian bug #877507
1 package successfully removed."
1729235,2017-11-01 08:20:40 UTC,"Demoting packages to bionic-proposed:
 ppx-core 113.33.03-1ubuntu2 in bionic
 ppx-driver 113.33.03-1build1 in bionic
 ppx-optcomp 113.33.03-1ubuntu2 in bionic
 ppx-sexp-conv 113.33.03-2ubuntu3 in bionic
 ppx-type-conv 113.33.03-1ubuntu4 in bionic
 ocaml-ipaddr 2.7.0-2build2 in bionic
 ocsigenserver 2.7-1build4 in bionic
Comment: lp: #1729235, demote ppx-core and rdeps
7 packages successfully demoted."
1729235,2018-02-02 02:10:42 UTC,blocking bug not needed for uninstallable revdeps.
1729246,2019-07-17 04:17:23 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1729246,2019-05-17 17:17:13 UTC,It may be the same issue as https://bugs.launchpad.net/kolla-ansible/+bug/1712087
1729246,2019-03-28 10:18:43 UTC,Is this still a bug? If yes - please update.
1729256,2017-11-01 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1729256,2017-11-20 10:39:55 UTC,In Artful this fix was commited as part of the 4.13.10 upstream stable set.
1729256,2017-11-28 17:47:34 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1729256,2017-11-28 17:48:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1729256,2017-12-07 17:43:17 UTC,This bug was fixed in the package linux - 4.10.0-42.46
1729256,2017-12-07 17:43:39 UTC,This bug was fixed in the package linux - 4.4.0-103.126
1729256,2018-07-24 09:33:28 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1729261,2020-01-17 12:38:27 UTC,"@Marek: I don't think there is a specific reason, if you can rewrite the code to use the designateclient and solve this issue, that would be very welcome."
1729261,2019-02-11 08:37:05 UTC,"Hi,"
1729261,2018-08-09 08:07:00 UTC,"Hi,"
1729261,2018-03-20 11:16:27 UTC,So it seems the dashboard is lacking the ability to handle the chunked response it receives from the API. Compare this function that is being used in the python client
1729261,2018-07-24 05:06:14 UTC,"Hi,"
1729261,2018-03-20 10:41:28 UTC,Same bug here on PIKE
1729261,2018-03-15 09:00:08 UTC,Same here: only 20 records are accessible.
1729261,2018-08-06 12:01:47 UTC,"This bug is still open, I did try to resolve it, but failed due to lack of understanding javascript and the frameworks that are involved."
1729261,2018-03-06 13:12:17 UTC,"the same error occurs when listing zones. It always displays only the max. 20 items, all subsequent skips and the next button does not appear"
1729269,2017-11-02 05:23:09 UTC,https://github.com/eliovir/krecipes/issues/1
1729270,2017-11-01 12:33:50 UTC,"The attachment ""Xmahjongg geometry fix patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1729279,2017-11-20 13:06:27 UTC,The package has been published and the bug is being set to Fix Released
1729279,2017-11-21 18:22:33 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1079.84
1729279,2017-11-18 07:31:39 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1079.84/snapdragon-4.4-proposed-published.html"
1729279,2017-11-20 11:55:58 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1079.84
1729279,2017-11-14 04:04:45 UTC,Hardware Certification have begun testing this -proposed kernel.
1729279,2017-11-17 15:08:26 UTC,What's blocking the snap version of this being pushed to beta?  We haven't seen any uploads to beta channel for us to test this cycle
1729279,2017-11-17 15:46:52 UTC,"Chris,"
1729294,2018-04-20 05:37:30 UTC,"Reviewed:  https://review.openstack.org/519950
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=db797970c3dcdf639dbbba2326b879dbcec1a227
Submitter: Zuul
Branch:    stable/ocata"
1729294,2017-12-18 12:51:40 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1729294,2017-12-07 23:56:29 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1729294,2017-12-03 01:36:19 UTC,"Reviewed:  https://review.openstack.org/519951
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4402da85cd5fe03809989373b4670adc7beb40f0
Submitter: Zuul
Branch:    stable/pike"
1729294,2018-05-02 12:00:18 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1729294,2017-11-15 02:47:57 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/519950"
1729294,2017-11-15 01:27:35 UTC,"Reviewed:  https://review.openstack.org/517227
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=76a4e42e8bb98c8d5f30d8fef7b0fafd3976b626
Submitter: Zuul
Branch:    master"
1729294,2017-11-02 09:46:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/517227"
1729294,2017-11-02 01:59:53 UTC,"In this code, it attempts to show injection_info, while debug log message is that:""Checking root disk injection %(info)s "",can not format injection_info. So I think it should be modified here."
1729294,2017-11-01 15:28:39 UTC,"This looks correct to me, I don't really understand your point in why you think this is a bug:"
1729294,2017-11-15 02:48:41 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/519951"
1729302,2017-11-02 11:33:09 UTC,Hi.
1729302,2017-11-02 13:13:34 UTC,"It's working now, thanks <3"
1729305,2017-12-28 00:02:00 UTC,"Jason, do you have any plans to update the 1.7.0 RC1 to the official 1.7.1 build? Also, do you have any updates on whether the 1.7.x updates will be coming to the official Ubuntu 17.10 repos?"
1729305,2017-11-07 12:01:58 UTC,Thanks Jason for this one. It is working very well in Ubuntu 17.10. Tested it with all the features I need and all worked.
1729305,2017-11-02 16:47:44 UTC,"Devin,"
1729305,2017-11-02 20:16:50 UTC,"Also, if you're so inclined, I now have CouchDB 1.7.0 test packages for Artful here:"
1729305,2017-11-02 09:47:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729305,2017-11-03 00:44:40 UTC,"Awesome Jason, thank you for such a quick update. The 1.7.0 package you provided in your repo seems to be working well. While I haven't tested it extensively, it's loaded file and I can access the port."
1729312,2017-11-02 14:09:43 UTC,"thanks you Miguel for your help.
But I am confusing and I don't know exactly how to do this ?
Could you tell me if this is the suitable standard I have to consider: http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/tosca-nfv-v1.0.html ?
Is it possible to share a .yaml example I can follow to correctly write mine ?
This is the new .yaml file."
1729312,2017-11-02 15:07:32 UTC,Thanks Bob and agree with Miguel. So I would recommend taking a look at few examples as you asked here - https://github.com/openstack/tosca-parser/tree/master/toscaparser/extensions/nfv/tests/data and https://github.com/openstack/tacker/tree/master/samples/tosca-templates May be good idea that you use couple of those templates first as such and see if that works and then modify your using them as reference. Thanks!
1729312,2017-11-02 14:49:58 UTC,"Hi David,"
1729312,2017-11-02 12:02:25 UTC,"Hi David,"
1729312,2017-11-02 16:02:46 UTC,"Thank you very much for these useful examples.
Would like to share the standard that I have to consider.
This one http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/tosca-nfv-v1.0.html should be up to date or not ?"
1729312,2017-11-02 10:16:24 UTC,"Hi David,"
1729312,2017-11-01 20:23:59 UTC,"Hi David, are you using any specific release of tosca-parser? or master version? Also subscribing Bob to this bug. Thanks!"
1729312,2017-11-01 20:48:43 UTC,"Thank you for the reply.
These commands may be useful to describe my execution environment.
I highlight that I executed them few days before to setup my openstack instance."
1729312,2017-11-02 11:09:44 UTC,"Thanks Miguel for your help.
I updated my .yaml file as suggested and also changed 'VM1' by 'VDU1'.
Besides I changed 'tosca.nodes.Compute' by 'tosca.nodes.nfv.VDU'.
But I got the following error. I am wondering if the use of 'tosca.nodes.nfv.VL' is right or I have to use 'tosca.nodes.nfv.VL.ELAN'?
Kindly find bellow my new .yaml file."
1729312,2017-11-02 09:53:53 UTC,"Thanks for your support.
I uninstall tosca-parser module then I run pip command (sudo pip install tosca-parser) to re-install it.
I also update the header of my .yaml file as suggested by Bob.
Now I get a new error as described below:
    tosca = ToscaTemplate(path, parsed_params, a_file)
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/tosca_template.py"", line 101, in __init__
    self.topology_template = self._topology_template()
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/tosca_template.py"", line 120, in _topology_template
    None)
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/topology_template.py"", line 60, in __init__
    self.graph = ToscaGraph(self.nodetemplates)
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/tpl_relationship_graph.py"", line 19, in __init__
    self._create()
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/tpl_relationship_graph.py"", line 40, in _create
    relation = node.relationships
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/nodetemplate.py"", line 61, in relationships
    explicit = self._get_explicit_relationship(r, value)
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/nodetemplate.py"", line 144, in _get_explicit_relationship
    for rtype in self.type_definition.relationship.keys():
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/elements/nodetype.py"", line 89, in relationship
    relatednode = NodeType(node_type, self.custom_def)
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/elements/nodetype.py"", line 30, in __init__
    super(NodeType, self).__init__(ntype, self.NODE_PREFIX, custom_def)
  File ""/usr/local/lib/python2.7/dist-packages/toscaparser/elements/statefulentitytype.py"", line 38, in __init__
    if entitytype.startswith(self.TOSCA + "":""):
AttributeError: 'NoneType' object has no attribute 'startswith'"
1729312,2017-11-01 22:55:57 UTC,Hi David:
1729317,2017-11-02 15:00:15 UTC,This change was made by a bot.
1729326,2017-11-17 07:07:02 UTC,I'm experiencing the same error w/ a Fujifilm X-T2.
1729326,2017-11-17 07:07:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729326,2017-11-17 07:32:14 UTC,Manually installing the libgphoto2 2.5.16 package in the bionic-proposed repo fixed this issue for me. https://launchpad.net/ubuntu/+source/libgphoto2/2.5.16-1
1729326,2017-11-17 08:10:25 UTC,the patch seems like a good candidate for a SRU indeed
1729326,2017-11-17 07:16:31 UTC,It looks like this was fixed upstream:
1729340,2017-11-02 02:39:42 UTC,I agree. In fact I was wondering about the wisdom of inverting the button gradients when Marco was talking about it a couple of weeks ago...
1729340,2017-11-02 02:40:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729340,2017-11-02 20:58:05 UTC,"Additionally, taking GNOME Builder (from the Ubuntu archive) as an example: the window always uses the inverted gradient, without having to maximize it. Might be due to Builder adding another CSS class called ""workbench"" to its main window (GTK_DEBUG=interactive), throwing off GTK somehow."
1729343,2017-11-27 15:36:37 UTC,networking-odl is for OpenDaylight. I guess it's typo.
1729349,2020-10-03 04:17:17 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1729349,2020-08-03 05:52:26 UTC,"Are you still experiencing this problem? If so, can you provide more details about the problem you see and when it happens?"
1729350,2018-09-25 10:33:18 UTC,Same here.
1729357,2018-07-16 07:45:50 UTC,All updates released.
1729357,2018-02-15 12:30:59 UTC,"Thanks for the credit! I did highlight that the bug was in newgidmap in my initial report, by the way."
1729357,2018-02-15 13:03:16 UTC,"On Thu, Feb 15, 2018 at 11:30 PM, Craig Furman
<email address hidden> wrote:

> Thanks for the credit! I did highlight that the bug was in newgidmap in
> my initial report, by the way.
"
1729357,2018-02-15 13:34:41 UTC,"It's really not a problem, I'm happy to leave it as it is."
1729357,2018-02-15 14:05:53 UTC,https://github.com/shadow-maint/shadow/pull/97 is my proposed patch. It currently only deals with the immediate security issue of allowing users that don't have
1729357,2018-02-16 04:16:01 UTC,CVE-2018-7169 is assigned for this issue.
1729357,2018-02-16 08:33:35 UTC,CVE-2018-7169
1729357,2018-02-15 12:23:00 UTC,"Yes, of course. ""Craig Furman (Pivotal)"" is in the credits. I also
added Akihiro Suda (for suggesting him that it was a newgidmap bug)
and myself (for working on a fix for it), but if Craig prefers I can
just make him the only credit."
1729357,2018-02-16 08:38:46 UTC,"SUSE:SLE-12:Update is not affected, since newgidmap was only introduced with 4.2.1. We still ship 4.1.5.1."
1729357,2018-02-16 10:34:16 UTC,"Thanks for adding the patch.
SR accepted. Forwarded to Factory as SR#577204."
1729357,2018-02-16 15:03:45 UTC,"Didn't realize that we backported this feature to our SLE12 codestream. Applied the patch there, too: sr#155145"
1729357,2018-02-19 17:22:47 UTC,https://github.com/shadow-maint/shadow/pull/99 includes the allow_setgroups/deny_setgroups feature that we discussed earlier.
1729357,2018-03-12 17:08:46 UTC,SUSE-SU-2018:0662-1: An update that fixes one vulnerability is now available.
1729357,2018-03-13 02:08:07 UTC,openSUSE-SU-2018:0667-1: An update that fixes one vulnerability is now available.
1729357,2018-03-13 14:32:48 UTC,@stgraber @mdeslaur - I'd considered making a release for Ubuntu...  but this is the negative acl thing...  Your opinions appreciated.
1729357,2018-02-16 08:49:09 UTC,Fixed for Factory: sr#577189
1729357,2018-02-15 12:00:52 UTC,"On Thu, Feb 15, 2018 at 11:29:03AM -0000, Aleksa Sarai wrote:

> I've just sent a request for a CVE. I'm working on the patch now. My
"
1729357,2018-07-02 10:50:46 UTC,I think this can be closed.
1729357,2018-02-15 06:17:06 UTC,"I had a preliminary patch written, but it was getting quite complicated (shadow's codebase is much more complicated than I expected -- and the /etc/subgid parsing code is intertwined with the parsing code for all of the other /etc/... files). I am working on it though."
1729357,2017-11-07 19:20:16 UTC,"Hi,"
1729357,2017-11-02 01:18:21 UTC,"Hi Craig, interesting finding, thanks for reporting it to us."
1729357,2017-11-07 19:33:25 UTC,"Well, there is the slight problem that every single Ubuntu server install comes with newgidmap installed today so I think we do need to be careful with releasing a fix for this as there may well be users of LXC/LXD that also rely on negative groups for access control on their system."
1729357,2017-11-07 19:50:48 UTC,"@stgraber,"
1729357,2017-11-07 21:08:25 UTC,I think you could but we don't have any PAM module that lets you do that today.
1729357,2017-11-07 21:09:38 UTC,"Oh, actually, according to https://lwn.net/Articles/626665/ the setgroups file is a namespace specific knob, so flipping it to deny would actually prevent setgroups by anyone who's in the host namespace..."
1729357,2017-11-08 17:03:50 UTC,"I agree that in order to preserve the ability of unprivileged containers to call setgroups we need some root-owned config file (possibly a column in /etc/subgid, possibly a new file) that controls which users newgidmap *won't* set /proc/$pid/setgroups to deny for."
1729357,2017-11-07 21:15:20 UTC,"Thinking about this problem a bit, it certainly sounds like for the normal case we'd want newgidmap to flip setgroups to false prior to writing the map, effectively preventing this issue."
1729357,2017-11-17 16:18:03 UTC,"Thanks for replying Eric, but I'm having trouble reproducing what you've posted. I can't write the gid map until I've written deny to /prod/$pid/setgroups, not the other way around. There might be some nuance I've missed."
1729357,2018-01-15 14:39:10 UTC,"> Thanks for replying Eric, but I'm having trouble reproducing what you've
> posted. I can't write the gid map until I've written deny to
> /prod/$pid/setgroups, not the other way around. There might be some nuance
> I've missed.
"
1729357,2018-01-15 15:13:56 UTC,"> And we define flags ""allow_setgroups"" and ""deny_setgrouops"" (with
""deny_setgroups"" being the default).
"
1729357,2018-01-15 16:56:19 UTC,"This sounds acceptable to me.  Issues or (even better) PRs against
github.com/shadow-maint/shadow would be great :)"
1729357,2018-01-15 23:18:08 UTC,"Serge: I will submit a patch later today. However, I just thought that it's probably better that ""allow_setgroups"" should be ""ignore_setgroups"" and we retain the current behaviour (we don't write anything to /proc/$pid/setgroups) -- which allows a user (or runtime) to explicitly disable setgroups even if they would normally have the right to use setgroups."
1729357,2018-01-15 23:18:56 UTC,"Oh, and we should definitely get a CVE assigned IMO."
1729357,2018-02-15 03:32:51 UTC,@cyphar
1729357,2017-11-14 01:56:07 UTC,Eric W. Biederman contributed this via email:
1729357,2018-02-15 11:29:03 UTC,"I've just sent a request for a CVE. I'm working on the patch now. My current plan is that allow_setgroups will be the default for all mappings that are present in /etc/subgid -- but any ""implicit"" mappings (like mapping your own group) will be deny_setgroups by default (because that's the biggest security issue coming out of this bug -- that *any* user can drop groups, not just the ones with subgids set up)."
1729361,2017-11-01 14:56:35 UTC,"Dan,"
1729361,2017-11-01 18:29:41 UTC,"Kathy, looking briefly, I don't think so.  The log entries on that bug showing the precise 1 minute gaps do seem to indicate a timeout problem, perhaps the same as bug #1704396 (as noted)."
1729365,2017-11-04 11:24:11 UTC,I'm just a hobbyist and I don't write code with tests. So I will pass :P
1729365,2017-11-04 07:15:37 UTC,"Yes, that looks more correct. Care to send a pull request (with tests)?"
1729367,2017-11-01 15:10:33 UTC,"command line client from command line clinet ""isql"" (from unixodbc package) works"
1729368,2017-11-08 16:25:53 UTC,"I upgraded my system since them but according to /var/log/dpkg.log it was 1:17.04.9 (ubuntu-release-upgrader-gtk, -qt and -core)"
1729368,2017-11-13 10:32:33 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.2
1729368,2017-11-08 16:07:15 UTC,"Thanks for reporting this issue, the lack of an error message is specific to /var being full. Could you tell me what version of ubuntu-release-upgrader you were using. You should be able to find a version string towards the beginning of /var/log/dist-upgrade/main.log.  Thanks!"
1729371,2018-12-07 18:11:54 UTC,"Reviewed:  https://review.openstack.org/608575
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e463aa719be5446bb3cff7263274bf7d911aac0
Submitter: Zuul
Branch:    stable/rocky"
1729371,2018-10-08 05:41:45 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/608575"
1729371,2018-09-28 05:06:47 UTC,"Reviewed:  https://review.openstack.org/517108
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bf92b72ce9307e2faf220a75ca858289cf46406c
Submitter: Zuul
Branch:    master"
1729371,2017-11-15 01:10:29 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1729371,2017-11-07 01:21:30 UTC,"Reviewed:  https://review.openstack.org/517879
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=70ef1fa159c9941129827dbe93d4acc718fdb7ad
Submitter: Zuul
Branch:    stable/pike"
1729371,2017-12-07 23:56:28 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1729371,2017-11-06 05:33:01 UTC,"Reviewed:  https://review.openstack.org/517009
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d176175db456e4a312eed37ed4f5adcc06292fd5
Submitter: Zuul
Branch:    master"
1729371,2017-11-01 21:06:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/517108"
1729371,2017-11-01 15:20:17 UTC,WIP: https://review.openstack.org/#/c/517009/
1729371,2017-11-01 15:10:00 UTC,"Note that this would eventually be mitigated if there is at least one compute < Pike in the deployment since then the resource tracker will continue to create allocations in Placement during the update_available_resource periodic task. However, that won't help anyone that is doing a fresh install for pike or has upgraded all of their computes to pike, since we'll stop doing the auto-healing of allocations at that point."
1729371,2017-11-01 15:07:15 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Unable%20to%20find%20existing%20allocations%20for%20instance%5C%22%20AND%20tags%3A%5C%22screen-n-super-cond.txt%5C%22&from=7d
1729371,2017-11-06 07:59:17 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/517879"
1729380,2017-11-01 18:05:26 UTC,"Multiple worker processes would be the way to go, similar to what was done for the reconstructor [1] and is planned to be added to the replicator [2]."
1729390,2017-11-02 10:17:59 UTC,"Docs are currently very CentOS centric, so I suspect there is more todo that just charm enablement."
1729390,2017-11-02 10:18:13 UTC,Triaging as a feature request at this point in time.
1729394,2018-08-08 08:19:44 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1729394,2017-11-02 15:58:04 UTC,"Hi, Daniel."
1729394,2017-11-02 03:01:53 UTC,"Doug,"
1729394,2017-11-03 01:51:02 UTC,"Doug, yes sorry about that. There are certainly two issues."
1729394,2017-11-02 00:11:11 UTC,"Yep, that seems to be describing the same issue. They didn't mention the issue window pressing the super key and searching, but I'd imagine they have that issue too."
1729394,2017-11-01 22:05:50 UTC,seems similar to bug #1724977 / https://bugzilla.gnome.org/show_bug.cgi?id=789675
1729394,2017-11-01 21:19:55 UTC,Thanks for adding that Brian. Appreciate it. Any type of other information or data I could provide to better help developers?
1729394,2017-11-01 20:31:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1729394,2017-11-02 02:56:39 UTC,Yes let's keep the double cursor issue in bug 1724977.
1729397,2017-12-26 10:45:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729412,2017-11-18 01:50:06 UTC,I built test kernel based on the pull request above:
1729412,2018-01-09 19:07:33 UTC,This bug was fixed in the package linux-azure - 4.13.0-1005.7
1729412,2017-11-02 16:22:30 UTC,https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/arch/x86/hyperv?h=next-20171102 has a full list of changes for this area.
1729412,2017-11-02 16:20:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729412,2017-11-18 01:41:54 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-November/088330.html
1729413,2017-11-01 20:22:03 UTC,"I've raised the following review to update tox.ini and test-requirements accordingly.
 This does not add unit tests, but does allow the basic pep8 to pass and the virtualenv to build."
1729413,2017-11-02 08:14:02 UTC,"Reviewed:  https://review.openstack.org/517101
Committed: https://git.openstack.org/cgit/openstack/charm-interface-rabbitmq/commit/?id=2e153d9b70b82fc22d618c7d8762a0d55c52cfdd
Submitter: Zuul
Branch:    master"
1729414,2017-11-03 02:07:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729414,2017-11-20 21:04:42 UTC,This also appears to be the case in 16.04 LTS
1729414,2017-11-20 21:33:29 UTC,"We have rated these vulnerabilities as being ""low"" priority as the undefined behaviour doesn't affect binaries built with gcc."
1729417,2017-12-05 15:02:21 UTC,This bug was fixed in the package snapcraft - 2.35
1729417,2017-12-05 15:04:35 UTC,This bug was fixed in the package snapcraft - 2.35+17.04
1729417,2017-12-05 15:02:24 UTC,"The verification of the Stable Release Update for snapcraft has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1729417,2017-11-29 13:55:17 UTC,same issue for zesty/armhf https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/snapcraft/20171123_225031_85a92@/log.gz
1729417,2018-02-26 21:48:36 UTC,This bug was fixed in the package snapcraft - 2.39.2+18.04.2
1729417,2017-11-27 02:37:27 UTC,"I ran the tests in xenial, zesty and artful, and have been doing exploratory testing on the release.
I didn't find any blocker bugs, so this has the QA green light."
1729417,2017-11-24 15:49:47 UTC,"To land this in the -updates pocket, the following tests must pass:"
1729417,2017-11-23 15:36:33 UTC,"Hello Sergio, or anyone else affected,"
1729417,2017-11-23 15:33:44 UTC,"Hello Sergio, or anyone else affected,"
1729417,2017-11-23 15:32:05 UTC,"Hello Sergio, or anyone else affected,"
1729417,2017-11-29 13:54:23 UTC,"the xenial/armhf test timed out, here's the log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/s/snapcraft/20171124_001006_97bdb@/log.gz"
1729418,2017-11-03 22:35:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729431,2020-05-14 22:31:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729433,2021-01-26 07:23:38 UTC,I think this bug describes the behaviour on https://askubuntu.com/questions/1274365/windows-of-an-application-have-minimum-size-and-i-cant-find-the-window-anymore
1729433,2020-11-07 13:33:52 UTC,"I am experiencing this on Kubuntu 20.04.
Version: 6.4.6.2
Build ID: 1:6.4.6-0ubuntu0.20.04.1
CPU threads: 4; OS: Linux 5.4; UI render: GL; VCL: kf5;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: CL
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-52-generic
OS Type: 64-bit
nVidia GeForce GTX650Ti, driver 450.80.02"
1729433,2020-02-27 19:45:30 UTC,I'm still reproducing this on Fedora 31 with the 6.3.4.2-2.fc31 build.
1729433,2019-10-04 09:56:31 UTC,"The bug is no more present in this version.
BUT, the behavior is not really the good one : when you unmaximize the window, it doesn't come back to the previous size but to a nearly maximum size."
1729433,2019-09-16 10:14:15 UTC,"Still present in
LibreOffice Version: 6.2.6.2
Build ID: 1:6.2.6-0ubuntu0.19.04.1"
1729433,2019-09-16 02:46:12 UTC,"Dear Jean-François Fortin Tam,"
1729433,2018-11-22 08:44:39 UTC,"Thanks. I'm marking the bug fixed, per your comment. If you get a chance to test that on a 18.04 machine, please share your experience here."
1729433,2018-11-21 17:12:20 UTC,I am not able to reproduce this in 18.10. I no longer have an 18.04 machine to test on.
1729433,2017-12-16 11:26:28 UTC,See also: https://bugs.documentfoundation.org/show_bug.cgi?id=104371
1729433,2017-12-16 11:25:47 UTC,I confirm this issue on 5.4.4.1-1.fc27
1729433,2017-12-16 11:15:26 UTC,"I'm using a multi display setup. A regular display and a HiDPI display.
For some reason Libreoffice windows sometimes resize to completely minimized (only menu visible) when doubleclicking on the title bar."
1729433,2017-11-29 16:54:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729433,2017-11-01 20:27:53 UTC,This might be eligible for a `regression-release` tag since 17.04 didn't have this problem.
1729433,2017-10-31 19:16:02 UTC,"Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version."
1729433,2016-12-09 15:14:00 UTC,No repro on Arch Linux or Ubuntu
1729433,2016-12-03 05:15:04 UTC,"Description:
In Fedora 25, whether on X or Wayland, with the GTK3 version of LibreOffice, if you start your LOo app maximized, once you demaximize it it will become minuscule (something like 400x200 pixels) instead of using the last saved size."
1729433,2018-11-20 17:34:30 UTC,I cannot reproduce the issue with the latest version of LibreOffice (6.1.3.2) on Ubuntu 19.04.
1729435,2019-04-05 21:12:50 UTC,Pushed a working branch adding seed data changes and an upgrade script:
1729435,2019-10-04 14:40:58 UTC,"Pushed to master, rel_3_4, rel_3_3, rel_3_2, and rel_3_1. Thanks, Remington, Michele, and Jennifer!"
1729435,2019-09-09 16:37:44 UTC,Bill Full Details columns are now saving and are being preserved through deleting my cookies.
1729435,2019-04-12 19:41:30 UTC,I realized I neglected to add the persist key for the bills detail to the upgrade script and seed data. Force pushed to the branch linked above to correct that.
1729435,2018-12-04 14:25:08 UTC,"Good catch, Michele! It would be great if you can make the upgrade script. Until then, I'll replace the pullrequest tag with needsrepatch."
1729435,2018-11-05 21:20:54 UTC,Here's the simple fix for both grids on the bills Full Details screen:
1729435,2018-11-19 22:01:36 UTC,"I tested this on a 3.2.0 system and the fix works to save the column settings in local storage in the browser. However, bug 1750894 moved workstation settings to the database for 3.2 (Yay!). A schema change and db upgrade script is needed to store these in the database as described here:"
1729435,2018-05-24 20:30:21 UTC,Tested this on a current master sandbox. The columns won't save no matter what is deselected.
1729435,2018-05-30 13:34:39 UTC,"Similar to the fix for bug 1721145, we probably just need an appropriately named persist-key in both eg-grids in circ/patron/t_xact_details_details.tt2 ."
1729435,2018-05-29 16:28:20 UTC,Still cannot save columns in 3.1
1729435,2018-11-19 22:12:12 UTC,Also see related bug 1774707
1729437,2017-11-02 00:31:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1729437,2017-11-07 00:11:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729437,2018-02-22 13:21:51 UTC,"On a clean install of Ubuntu 17.10 I get a similar error. Installation on new hard drive works without a glitch, and the ""You must restart your machine yada yada yada...' popup appears. I then click on the restart button in the popup, the system begins the restart cycle, but goes to a black screen with a blinking text cursor (no error message). No commands work in this screen and I have to force shutdown. Then I restart the machine, and to all appearances Ubuntu 17.10 is present and working... but it makes me nervous."
1729437,2018-03-03 18:27:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729438,2018-05-23 23:57:52 UTC,"I took a look at this.  I don't have the knowledge to fix it, but I thought I'd pass along what I learned to save folks some digging:"
1729438,2019-08-12 17:34:49 UTC,Confirmed this is an issue in 3.3
1729439,2018-04-30 10:05:18 UTC,This issue was fixed in the openstack/heat 9.0.4 release.
1729439,2018-09-04 19:54:46 UTC,This issue was fixed in the openstack/heat 8.0.7 release.
1729439,2018-02-20 19:19:31 UTC,"Reviewed:  https://review.openstack.org/526803
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=9ef06ccead321fcc224ba4c33b168d2e7e746de1
Submitter: Zuul
Branch:    stable/ocata"
1729439,2018-01-30 22:30:53 UTC,This issue was fixed in the openstack/heat 10.0.0.0b3 development milestone.
1729439,2017-12-08 23:58:13 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/526803"
1729439,2017-12-08 23:57:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/526802"
1729439,2018-02-19 19:24:21 UTC,"Reviewed:  https://review.openstack.org/526802
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=0d005ffcb69b8c5be3228957f7dfb8809b811742
Submitter: Zuul
Branch:    stable/pike"
1729439,2017-12-07 07:37:42 UTC,"Reviewed:  https://review.openstack.org/516759
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=93b4551d9a1ff9194b30a079f02db691129c69b0
Submitter: Zuul
Branch:    master"
1729442,2017-11-02 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1729442,2017-11-02 20:55:42 UTC,"I built Xenial and Zesty test kernels, both with a pick of commit 88d879d29f9cc0d.  The test kernels can be downloaded from:"
1729442,2017-11-02 22:00:55 UTC,"Joe,
I will take a look."
1729447,2017-11-02 00:30:59 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1729447,2017-11-01 21:48:50 UTC,Additional info
1729447,2017-11-01 21:53:22 UTC,It is the first time I have no wired connection on this pc.
1729447,2017-11-04 19:28:20 UTC,"I chose to reinstall the 17.10 version from scratch. All the procedure went without any trouble. I have IP connection over the wire. I presume something went wrong during the upgrade process from 17.04 to 17.10, which I can not reproduce."
1729462,2018-05-13 19:29:51 UTC,"@Kuntal - I see no evidence that any code has been recently committed to Gitlab concerning this bug. If you have not committed code to the master branch then you should not mark this bug as ""Fix Committed"""
1729462,2018-05-13 19:53:58 UTC,"@apenner - I submitted the patches on the lib2geom repository which is on github, though it is my fault I would say that I never bothered to check if that request is merged or not, sorry for that."
1729462,2018-03-27 09:59:23 UTC,"Reproduced on Gentoo Linux with trunk, here is what I get :"
1729462,2018-06-19 06:58:55 UTC,Note: the exact comparisons in setCoefficients are not the cause of this crash; I wrote this specifically to work with extreme coefficient values. The exception is just exposing a problem that is happening elsewhere.
1729462,2019-05-12 00:52:17 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1729462,2018-05-14 11:03:25 UTC,"okay, thanks, I had checked the status of lib2geom, but had not checked the pull requests."
1729462,2018-03-27 09:52:46 UTC,Reproduced on linux with trunk
1729462,2017-11-02 10:06:57 UTC,I used inkscape-0.92.2-x64.exe
1729462,2017-11-02 16:49:28 UTC,"reproduced on Windows 10, trunk 64 bit build, Inkscape 0.92+devel (8a097e9, 2017-10-23)"
1729462,2017-11-02 03:11:46 UTC,"crash not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1729462,2017-11-02 09:13:35 UTC,"also, just for curiosity, does the crash go away if you disable all snapping?"
1729462,2017-11-02 09:08:10 UTC,"also, could you run it from DOS using a command like this:
C:\Program Files (x86)\Inkscape>inkscape
to see if there are any error messages in DOS?"
1729462,2017-11-02 09:03:41 UTC,"32 bit build or 64, msi or exe file?"
1729462,2017-11-02 03:41:15 UTC,"Strange, I am on Windows 10 too and it is 100% reproducible."
1729462,2017-11-03 03:14:14 UTC,"Reproduced with Win 8.1 Inkscape 0.92.2 (5c3e80d, 2017-08-06), msi installer."
1729465,2020-09-12 08:06:28 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1729470,2017-11-16 14:05:38 UTC,The problem is 'repairable' replacing .next by .__next__ in disassenbler.py.
1729473,2019-08-11 11:01:01 UTC,We are migrating issues from launchpad to inkscape manually (http://alpha.inkscape.org/bug-migration/).
1729474,2020-04-02 12:57:00 UTC,"We now track feature request at https://discourse.maas.io/c/features. Please post a topic there, since this is a non-trivial task that requires more discussion."
1729474,2019-09-19 15:04:01 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1729474,2017-11-02 00:34:45 UTC,"MAAS 2.4 has as part of its roadmap to define commissioning templates that would allow users to do things like this without having to embbed and support this in MAAS. This will be targeted to HBA’s and Firmware upgrades, but this will be reusable for other cases like this."
1729474,2017-11-02 03:00:59 UTC,"1. How can you discover, via the OS, that you have a SR-IOV card that *needs* to be enabled in the bios?"
1729474,2017-11-02 00:37:36 UTC,3. To what models does the command your provided applies to?
1729474,2018-02-15 15:07:08 UTC,Just as a quick note - it'd be extremely useful to drive racadm from MAAS for a lot of Dell related setup; most Dell setup can be remote controlled via MAAS.
1729477,2017-11-02 10:20:34 UTC,Sounds like a sensible optimization of the swift-storage charm; triaging as medium as this has the potential to benefit deployments with large numbers of objects.
1729478,2019-05-24 08:46:29 UTC,"Reviewed:  https://review.opendev.org/643162
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=edd00bee63c71ff34eaa728f7ed7fdb0efd13984
Submitter: Zuul
Branch:    master"
1729478,2019-03-13 21:51:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/#/c/643162/"
1729478,2017-11-02 10:20:52 UTC,+1
1729478,2019-01-24 08:02:27 UTC,"Please reconsider the criticality of this bug. When using LVM devices, the charm adds ""/dev/dm-X"" as device name in fstab. However, /dev/dm-X is not a stable name and can change between reboots if you have multiple VGs. With systemd, this resulted in my server dropping in a rescue shell (apparently that's what systemd does when it can't mount a filesystem in fstab)."
1729478,2018-02-26 20:31:15 UTC,"Just a little background colour on how difficult a situation this can yield.  I ran into this recently with a machine that simply had an extra disk (array B below) added, which changed the enumeration order when it was rebooted:"
1729478,2019-01-24 08:04:46 UTC,"Also, using a LV results in the mountpoint being /srv/node/dm-X, which is not ideal."
1729491,2018-04-06 16:57:09 UTC,This bug was fixed in the package apport - 2.20.9-0ubuntu4
1729491,2018-04-04 09:54:00 UTC,"Sounds like a well-founded change, only a few srings, and a notification sent to the ubuntu-translators mailing list."
1729491,2018-04-04 12:49:14 UTC,UIFe approved. Please proceed.
1729491,2018-04-04 08:01:18 UTC,Marking it as New for the UIFe tracking.
1729491,2018-04-06 09:37:30 UTC,(cleaning up ~ubuntu-release bugs)
1729491,2018-03-27 13:33:19 UTC,Current state:
1729491,2017-11-02 11:36:02 UTC,gnome-recipes is only available as a snap in Ubuntu 16.04 LTS not as a regular .deb so none of your apt commands will work. ubuntu-bug gnome-recipes won't work either.
1729491,2017-11-02 12:10:44 UTC,"I do not understand is a standard installation via software-center do not
have to independently resolve issues with installing programs? When I
download third-party *.deb packages I assume, that something can go wrong,
but when set through the GUI implies that the program should stand
correctly, or to report problems in advance.
---
Мне не понятно, разве стандартная установка через software-center не должна
самостоятельно решать вопросы с установкой программ? Когда я скачиваю
сторонние *.deb пакеты я предполагаю, что что то может пойти не так, но
когда устанавливаю через GUI предпологаю что программа должна вставать
корректно, либо сообщать о неполадках заранее."
1729491,2018-03-27 14:43:03 UTC,"Merged it into a forked bionic branch, cleaned that up a bit, ensured autopkgtests pass, and opened a merge proposal at https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207"
1729491,2018-03-27 10:04:07 UTC,"Hmm, it was not linked, but https://code.launchpad.net/~juliank/apport/snap is my WiP branch."
1729491,2018-01-25 14:38:32 UTC,"This is indeed confusing because the user installed a software in a recommended way and apport errors on ""the program is not installed"" while it is installed but not as a deb package."
1729498,2020-07-23 15:30:11 UTC,looks like you tweaked /usr/bin/python symlink point to python3
1729508,2017-11-07 10:22:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729511,2017-11-02 07:27:14 UTC,"root@nodec1:~# neutron ext-list  | grep -i tag

| tag                       | Tag support                     |


root@nodec1:~#"
1729511,2018-12-03 14:29:41 UTC,This Neutron extension https://docs.openstack.org/neutron/latest/contributor/internals/tag.html is not supported by the contrail Neutron plugin. Is it a feature request?
1729516,2018-01-26 08:38:13 UTC,While not super important I'll pick it for 18.04 as Debian unfortunately (because not too important I guess) hasn't picked it yet.
1729516,2017-11-06 14:25:58 UTC,Note: ppa is https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3026
1729516,2018-02-01 10:26:33 UTC,This bug was fixed in the package libvirt - 4.0.0-1ubuntu1
1729516,2017-11-06 14:45:04 UTC,Modifying the pre/post-inst files I found that really virtlogd is just active by this sysv accident that is left.
1729516,2017-11-06 12:33:04 UTC,"I took a little overview, these services are usually only needed for special cases (locks for e.g. net disks), and almost never configured - so this was undetected for quite a while."
1729516,2017-11-02 11:52:01 UTC,"Might be just socket activated, but I've also seen that (the super rarely a.k.a. almost never used) file /etc/default/virtlockd is missing."
1729516,2017-11-06 14:25:42 UTC,"There was a line missing for virtlockd to be properly picked up by latter dh_* calls.
Adding that in a ppa fixed the issue of the missing default conf file."
1729524,2017-11-02 08:30:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1729528,2018-01-26 03:50:56 UTC,I fixed this using a workaround..
1729528,2018-10-23 05:21:49 UTC,"Change abandoned by Christian Berendt (<email address hidden>) on branch: master
Review: https://review.openstack.org/517210"
1729528,2019-03-28 10:19:53 UTC,Is this still a bug? If yes - please update.
1729528,2019-05-28 04:17:30 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1729536,2017-12-06 08:37:35 UTC,"2017-12-06 9:15 GMT+01:00 Eric Fjøsne <email address hidden>:

> What can I do next to further investigate this in order to provide
> feedback over here in an efficient way ?
"
1729536,2017-12-06 10:08:46 UTC,"Hi,"
1729536,2017-12-08 08:30:55 UTC,"Hi Lars,"
1729536,2018-01-02 16:27:21 UTC,Apologies for my lack of feedback but those were quite busy days ...
1729536,2017-12-06 08:15:44 UTC,"Dears,"
1729536,2018-03-08 22:45:07 UTC,"@Andreas: It wasn't private before ... I don't have access to it anymore either, even when I'm logged in the portal."
1729536,2018-03-09 08:33:04 UTC,"I was told the mentioned bug is private because it contains a crash dump, and it is still open."
1729536,2018-03-16 06:44:20 UTC,"Unfortunately, we had big hopes but we experienced again this exact bug, with the exact same trace for version 5.1.21."
1729536,2018-04-10 21:46:41 UTC,"I am seeing this as well in percona-xtradb-cluster-server-5.7 (5.7.21-29.26-1.xenial) / mysqld  Ver 5.7.21-20-57 for debian-linux-gnu on x86_64 (Percona XtraDB Cluster (GPL), Release rel20, Revision 1702aea, WSREP version 29.26, wsrep_29.26)"
1729536,2018-03-08 16:48:35 UTC,The new upstream bug (88844) is unfortunately private and I can't see its state.
1729536,2018-03-16 12:21:38 UTC,"Upstream consider this bug valid, so Triaged."
1729536,2017-12-01 09:53:48 UTC,"2017-12-01 10:32 GMT+01:00 Eric Fjøsne <email address hidden>:

> I reactivated one set of optimize queries for this night and it crashed
> with the exact same backtrace. So I can confirm this is indeed related
> to this specific set. However, there is nothing fancy about them at all.
"
1729536,2017-11-30 08:33:16 UTC,"2017-11-30 9:12 GMT+01:00 Eric Fjøsne <email address hidden>:

> @Olaf: it wasn't available anymore unfortunately.
>
> After deactivating the OPTIMIZE statements and changing the TRUNCATE
> statement to DELETE FROM in our pre-production scripts, I can happily
> confirm there was no outage on our server during this night.
>
> If this can help investigating this bug in any way?
"
1729536,2017-11-03 09:55:38 UTC,"Hi Olaf,
there seem to be some related known issues in percona/mysql, see bug 1399471 for more details and follow referenced further bugs from there."
1729536,2017-12-01 09:32:20 UTC,"I reactivated one set of optimize queries for this night and it crashed with the exact same backtrace. So I can confirm this is indeed related to this specific set. However, there is nothing fancy about them at all."
1729536,2017-11-29 06:27:59 UTC,"Hi Olaf,"
1729536,2017-11-29 06:40:54 UTC,"Hi ChristianEhrhardt,"
1729536,2017-11-29 06:53:13 UTC,"They seemed similar to my limited insight to the matter, thanks for cross checking the bugs Eric!"
1729536,2017-11-03 10:21:14 UTC,"2017-11-03 10:55 GMT+01:00 ChristianEhrhardt <email address hidden>:

> Hi Olaf,
> there seem to be some related known issues in percona/mysql, see bug 1399471 for more details and follow referenced further bugs from there.
>
> I'll explicitly subscribe Lars to take a look, but as printed in the
> error message it would be great if you could file (and mention the
> number here) a bug at [1] the upstream bug tracker for mysql. They might
> have a backportable fix known already.
"
1729536,2017-11-29 07:07:44 UTC,"@Eric for the temporary downgrade you can force versions in apt (but this will stop upgrades, so ensure to unlock it later on with the same command without a version qualifier). Also you can usually only go to versions that are the latest in one of the pockets (release/updates/...).
So atm that would be 5.7.11-0ubuntu6 which is way too old I'd think.
$ apt install mysql-server-5.7=5.7.11-0ubuntu6
You also have to do the same with each dependency (to downgrade all of them)"
1729536,2017-11-29 08:33:37 UTC,"Hi,"
1729536,2017-11-29 09:46:23 UTC,"@ChristianEhrhardt
Thanks for your replies and initiatives. Much appreciated.
I did indeed notice the install package we could rollback to using apt-get install mysql-server=XXX was 5.7.11, but this version is more than a year and a half old, which doesn't sound like such a good idea."
1729536,2017-11-29 10:02:08 UTC,"2017-11-29 10:46 GMT+01:00 Eric Fjøsne <email address hidden>:

> @ChristianEhrhardt
> Thanks for your replies and initiatives. Much appreciated.
> I did indeed notice the install package we could rollback to using apt-get install mysql-server=XXX was 5.7.11, but this version is more than a year and a half old, which doesn't sound like such a good idea.
"
1729536,2017-11-30 08:12:20 UTC,@Olaf: it wasn't available anymore unfortunately.
1729536,2017-11-29 06:55:39 UTC,"Also as it seems to be confirmed by more than one reporter as regression part of the 5.7.20-0ubuntu0.16.04.1 update I'll tag it as such and add Marc who did the security update.
Maybe in the context of the CVEs there were discussions that could indicate what is failing."
1729539,2017-11-02 17:14:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1729539,2017-11-05 11:55:07 UTC,the bug in GNOME Bugzilla : https://bugzilla.gnome.org/show_bug.cgi?id=789932
1729539,2018-11-05 08:16:08 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1729539,2018-11-05 08:31:15 UTC,same bug with ubuntu 18.04.1
1729539,2018-12-14 07:48:11 UTC,it seems that it is the same bug as #1745907
1729539,2019-02-14 05:27:19 UTC,It works now since 4 days.
1729541,2019-03-05 13:32:21 UTC,Is this still an issue?
1729544,2017-11-02 13:16:34 UTC,Sorry: revno #110 of lp:~abinit-fallbacks-developers/libpsml/buildsys fixes this issue.
1729544,2017-11-02 13:15:16 UTC,Revno #110 fixes this issue.
1729544,2017-11-02 10:49:01 UTC,"Right. I renamed 'ts' from sets_m.F90 to 'test_sets', in order to be more explicit."
1729544,2017-11-02 09:58:59 UTC,"I am not able to find any mention of 'test_sets' anywhere in the 1.1.5 libPSML source tree...
Could you tell me where you found it?"
1729544,2017-11-02 11:46:05 UTC,Ah!
1729546,2019-05-07 12:50:46 UTC,"This ticket is always relevant? A patch was proposed and merged in master, so I suppose it's possible to close this ticket."
1729546,2018-01-05 20:56:43 UTC,"Reviewed:  https://review.openstack.org/528261
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=90c2eb3929d699bd3c2e25556851aba42ce2828e
Submitter: Zuul
Branch:    master"
1729546,2017-12-15 13:04:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/528261"
1729546,2019-12-18 08:36:50 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1729546,2017-11-13 13:29:44 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/519348"
1729546,2017-11-11 04:29:44 UTC,"Reviewed:  https://review.openstack.org/517025
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=0c1ac1d752aaf88832b34e165f7d147e2304ff1c
Submitter: Zuul
Branch:    master"
1729546,2017-11-02 22:29:13 UTC,We're still investigating if the ansible 2.4.1 actually fixes the issue during the upgrade workflow. I filed this bug to keep track of this patch - https://review.openstack.org/#/c/517025/ which addresses the issue.
1729546,2017-11-02 21:13:34 UTC,I believe this was identified as an issue with the ansible version. What version was used with this report?
1729546,2017-11-14 17:39:38 UTC,"Reviewed:  https://review.openstack.org/519348
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=af701f29f9b1bd0d19dc356d0071dce18f21cdf9
Submitter: Zuul
Branch:    stable/pike"
1729558,2021-02-07 00:07:06 UTC,"As far as I see, openjdk-8 (8u275-b01-1) contains this patch, so it was backported upstream."
1729558,2018-05-27 16:06:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729558,2017-11-20 09:41:19 UTC,"Patch was applied upstream,"
1729558,2017-11-08 04:31:17 UTC,"The attachment ""disabled.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1729558,2017-11-08 02:06:42 UTC,"No upstream bug yet unfortunately (OpenJDK bugtracker is restricted access as I'm sure you know).
I made a mailing list thread a few days ago here http://mail.openjdk.java.net/pipermail/swing-dev/2017-November/007904.html although haven't had any feedback aside from the patch not being attached!"
1729558,2017-11-08 01:01:32 UTC,"Patch I submitted upstream is attached, not through yet though."
1729558,2017-11-08 01:46:51 UTC,"Great, thanks. Do you have a link to the upstream bug?"
1729558,2017-11-03 09:48:13 UTC,Ok Turns out Java has some super funky code:
1729558,2017-11-03 05:48:51 UTC,"If you were testing your own install the font rendering is messed because of this bug in freetype https://bugs.launchpad.net/bugs/1722508
Downgrading to the Zesty version of freetype (as in my screenshots) fixes that issue."
1729558,2017-11-03 08:33:43 UTC,"Java looks to be using the disabled foreground colour correctly (to me, the untrained observer):"
1729558,2017-11-03 05:30:28 UTC,I think it's more the Swing/other toolkit's unique way of rendering things than GTK. Testing a native GTK-2 app (geeqie) doesn't seem to exhibit the problem.
1729558,2017-11-03 05:12:26 UTC,"Java isn’t hardcoding them, it’s pulling them from GTK. There is the possibility that it’s pulling the wrong type of element colour (sorry not sure about terminology)."
1729558,2017-11-03 02:54:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729558,2017-11-03 02:53:56 UTC,Although if you say everything was fine before the fix for bug 961679 then this is a regression and it possibly is the fault of ubuntu-themes :)
1729558,2017-11-03 02:28:50 UTC,"Confirmed. But the problem is just Java failing to pay attention to the theme correctly. It uses the right background colour, but not the right font colours. It's still using a fixed font colour that works only on lighter backgrounds. This is a bug in openjdk-8 (or netbeans itself, not sure)."
1729558,2017-11-02 10:46:42 UTC,Firefox / Libreoffice etc which I'm guessing use gtk3 show disabled items fine.
1729563,2017-11-02 13:47:40 UTC,"u1710@u:~$ cat Packages
Package: refind
Priority: optional
Section: admin
Installed-Size: 5141
Maintainer: Rod Smith <email address hidden>
Architecture: i386
Version: 0.11.2-0ppa1
Depends: debconf, efibootmgr, openssl, sbsigntool, parted, util-linux, debconf (>= 0.5) | debconf-2.0
Filename: pool/main/r/refind/refind_0.11.2-0ppa1_i386.deb
Size: 3788708
MD5sum: c5be05f0972babe5bac32b9537b80eda
SHA1: 89a16021659b154a91f40f63fb872c6da27fc26c
SHA256: 0d744ac63a4e0f6101027779206066bb93d9a58d712ec60992cd824cc314c75f
Description: boot manager for EFI-based computers
Description-md5: 9b3e73b9c1433dc9c16339776cee464c"
1729566,2020-04-16 19:55:14 UTC,"Reviewed:  https://review.opendev.org/719416
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=03784673557a0b2c5a2dba1ce06966dcd66473a8
Submitter: Zuul
Branch:    stable/train"
1729566,2020-04-14 12:56:44 UTC,"Reviewed:  https://review.opendev.org/719422
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=f174ec063676bea17e17c537282eb9eb08e89e70
Submitter: Zuul
Branch:    stable/stein"
1729566,2020-04-13 09:22:26 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/719422"
1729566,2020-04-13 09:06:56 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/719416"
1729566,2020-04-12 06:14:18 UTC,"Reviewed:  https://review.opendev.org/715494
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=628c27ce9e693902c5cabedc7f254f2a1229a195
Submitter: Zuul
Branch:    master"
1729566,2019-05-21 09:39:31 UTC,After re-generating /etc/hosts. The most important thing is the file '/etc/hosts' of the container 'nova_compute' does not refresh until the container is restarted.
1729566,2020-03-30 02:49:26 UTC,"Hi, Ross."
1729566,2019-09-30 15:11:23 UTC,We're also seeing this.
1729566,2019-03-28 10:45:48 UTC,Why not just re-run bootstrap-servers? Or do we need a more fine-grained command?
1729566,2019-03-28 10:22:12 UTC,"kolla-ansible baremetal role (bootstrap-servers) is generating /etc/hosts entries, therefore it would need some refactor to generate /etc/hosts on all servers..."
1729566,2020-04-09 18:25:28 UTC,I think the not-updated-/etc/hosts-issue could be refactored here as we are in fact fixing a more general issue while leaving name resolution broken still.
1729574,2019-09-26 11:10:20 UTC,"Sorry it's taken this long to respond to this bug! We're trying to bring our New bugs down close to zero, to catch these things early... hopefully we get better at it."
1729575,2020-04-25 09:43:49 UTC,since 18.04
1729575,2017-11-09 11:57:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729575,2017-11-03 08:53:01 UTC,"Thanks a lot Felix, I can confirm that the development version from PPA fixes the issue."
1729575,2017-11-02 19:23:40 UTC,"Speedcrunch's Debian maintainer here: packages in Ubuntu's universe don't have a dedicated maintainer, most of them are just synced automatically from Debian (before the release of an Ubuntu version). I can't upload to Ubuntu either. This bug is most likely just going to persist until the next Ubuntu release, unless someone from the MOTU team or whatever picks it up and imports the new Debian package."
1729576,2019-05-25 04:17:29 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1729576,2019-03-23 15:00:49 UTC,While snapd can read the home directory from the gecos system it is not the technical difficulty preventing the use of arbitrary home directory. This feature is currently unsupported and is listed as such on https://forum.snapcraft.io/t/limitations-in-snapd/9718
1729576,2019-03-23 07:17:50 UTC,"While true most of the time, root's home directory should actually be read from /etc/passwd"
1729576,2019-02-21 10:32:15 UTC,"Seth, it is more than just apparmor (it is actually the easiest of the parts to address; snap-confine is harder), but the issue as a whole is tractable, understood and something the snapd team plans to address in the future (perhaps someone from the snapd team can comment)."
1729576,2019-02-15 11:47:27 UTC,"Oh, since this is done inside a container please also include the command line to spawn a container, including any special changes to security that you may have applied."
1729576,2019-02-15 21:54:29 UTC,"Does snapd plan to manage /etc/apparmor.d/tunables/home.d/ for users who have moved their home directories? Or are users expected to do this themselves, since non-snap-managed profiles are affected too?"
1729576,2019-02-15 08:28:54 UTC,"btw, I've got a clean 18.10 system with recent kernel:
Linux 4.18.0-15-generic #16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1729576,2019-02-15 08:25:41 UTC,"Yeah, same with me.
$ ll /home
lrwxrwxrwx 1 root root 17 Dez 22  2017 /home -> /media/DATEN/home/
so, any workaround?"
1729576,2018-12-19 18:53:13 UTC,"All other users are complaining that the problem occurs if:
1) The /home is a symlink and not a real dir
2) The home folders are not in /home/* but somewhere else like /mnt/data1/home"
1729576,2018-11-30 17:39:48 UTC,Hello
1729576,2018-11-19 06:55:35 UTC,Same here with Ubuntu 18.04.1 LTS (GNU/Linux 3.13.0-57-generic x86_64):
1729576,2017-12-15 12:43:03 UTC,This bug seems not related to the snap package (snap: location of genes from DNA sequence with hidden markov model) but to the snapd package (part of the app packaging system developed by Canonical).
1729576,2019-02-15 11:46:35 UTC,Hello
1729577,2019-03-07 15:43:19 UTC,Design: zpl.io/bLP0DBG
1729584,2018-04-16 13:09:37 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/561611"
1729584,2018-05-02 11:59:24 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1729584,2018-04-25 09:23:55 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1729584,2018-04-25 09:21:00 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1729584,2018-04-24 18:06:13 UTC,"Reviewed:  https://review.openstack.org/561613
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1150d4a2af5b06c2df5dea053f5f7aea090c9145
Submitter: Zuul
Branch:    stable/ocata"
1729584,2018-04-20 13:13:24 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1729584,2018-04-20 05:24:15 UTC,"Reviewed:  https://review.openstack.org/561611
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b255e16bd93d9891caff8ffc84b8d7bc2991f90a
Submitter: Zuul
Branch:    stable/pike"
1729584,2018-04-17 12:49:16 UTC,"Reviewed:  https://review.openstack.org/561196
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9c66434eea245ae05a449059391515376f5a456
Submitter: Zuul
Branch:    stable/queens"
1729584,2018-04-13 11:09:04 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561196"
1729584,2018-04-16 13:11:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/561613"
1729584,2018-02-27 16:43:00 UTC,Thanks very much Logan for confirming that. We'll work to get the proposed patch [1] fixed up with proper unit test coverage and reviewed.
1729584,2017-11-20 15:37:08 UTC,The patch provided fixed the issue for me when doing virtio-scsi boot from RBD volume + config drive on Ocata.
1729584,2018-01-18 20:54:30 UTC,It seems like these 2 out of order virtio-scsi issues described above relating to secondary volumes and config drives ending up as index 0 are probably a regression introduced in https://review.openstack.org/#/q/topic:bug/1686116
1729584,2018-01-19 03:02:39 UTC,"Doing some more debugging, it looks like the disk_info['mapping'] is just processed in order:"
1729584,2018-01-26 16:22:20 UTC,Marking this as High because it's a regression.
1729584,2017-11-02 11:43:13 UTC,The issue is still present on master branch.
1729584,2018-01-26 20:14:13 UTC,"Hi Logan,"
1729584,2018-01-26 20:17:25 UTC,Sorry that formatting came out all wrong. Here's a paste of it: https://pastebin.com/nDhjDcaw
1729584,2018-02-25 17:54:04 UTC,Sorry I missed the patch you posted earlier until the bug update today.. I tested the patch and it fixes the situation in #2.
1729584,2018-01-26 17:25:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538310"
1729584,2018-04-13 10:42:39 UTC,"Reviewed:  https://review.openstack.org/538310
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2616b384e642b6eb58eef7da87b6e893f25a949e
Submitter: Zuul
Branch:    master"
1729589,2017-11-02 12:23:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/517288"
1729590,2017-11-22 05:56:49 UTC,"And also, observed that SIP2 is not connecting with kiosk via telnet port. it is working only with RAW port."
1729590,2017-12-18 09:59:10 UTC,"hi Jason,"
1729590,2017-12-11 14:07:22 UTC,"2017-12-05 18:07:23,224 TRACE   [ 3] TcpTransportProvider - TCP: 78 bytes written; 0 ms
2017-12-05 18:07:23,224 TRACE   [ 3] TcpTransportProvider - TCP: read
2017-12-05 18:07:23,225 TRACE   [ 3] TcpTransportProvider - TCP: 0 bytes read; 1 ms
2017-12-05 18:07:23,227 TRACE   [ 3] TcpTransportProvider - TCP: read
2017-12-05 18:07:23,228 TRACE   [ 3] TcpTransportProvider - TCP: 0 bytes read; 3 ms
2017-12-05 18:07:23,228 DEBUG   [ 3] SipCirculationProvider - Duration of operation: 57 ms
2017-12-05 18:07:24,136 ERROR   [27] TcpTransportProvider - TCP: Socket error = ConnectionAborted
2017-12-05 18:07:24,138 ERROR   [27] TcpTransportProvider - TCP: Socket error = ConnectionAborted
2017-12-05 18:07:24,141 INFO    [27] TcpTransportProvider - TCP: Closing connection to: 192.168.127.11:8023"
1729590,2017-12-11 14:02:14 UTC,Turn off the generation of checksums on the Kiosk.
1729590,2017-12-11 06:12:30 UTC,"hi team,"
1729590,2017-11-22 14:22:17 UTC,"Nidheesh, I think you should add a max_servers attribute in the server-params element at the top of your oils_sip.xml file. I'd set it to 10 or 20 just to be safe. It sounds like you may be running out of servers."
1729590,2017-11-22 11:48:23 UTC,"Thank you Jason,"
1729590,2017-11-22 11:32:15 UTC,"I don't believe the telnet port actually works. I've never tried it anyway. The raw port is the only thing I've ever used, and the only thing I've ever seen or heard anyone using."
1729590,2017-11-16 03:49:06 UTC,please find the configuration file and let me know if any changes needed
1729590,2017-11-14 14:55:52 UTC,"Hi, the issue between server and kiosk is having some issues. Please confirm that issue is because of character encoding."
1729590,2017-11-14 14:23:33 UTC,"Nidheesh,"
1729590,2017-11-14 07:44:00 UTC,"hi,"
1729590,2017-11-03 14:26:14 UTC,"Nidheesh,"
1729590,2017-11-03 05:49:50 UTC,"hi,"
1729590,2017-11-02 16:27:14 UTC,"Nidheesh,"
1729590,2017-11-02 15:13:33 UTC,Server and self check machine are in the same LAN but not in the same building.
1729590,2017-11-02 14:41:46 UTC,"Nidheesh,"
1729590,2017-11-22 05:55:58 UTC,"please have a look at the videos, SIP is disconnecting initially on every transaction. it is successful on the second attempt."
1729593,2017-11-02 15:33:19 UTC,This will be fixed in https://github.com/snapcore/snapcraft/pull/1638
1729602,2017-11-23 15:50:12 UTC,"What about this is invalid, precisely?  It's still happening, I can replicate at whim.  Would you like a video recording demonstrating it?  Do you require more information?"
1729602,2020-01-04 14:48:50 UTC,Fixed upstream in mate-system-monitor 1.22.1 (and Ubuntu 19.10 has 1.22.2).
1729609,2017-11-02 14:24:41 UTC,"If I disable the enp2so interface during install, the installation goes well.
How to prevent the creation of the enp2so interface? In preseed's early_command?"
1729609,2017-11-02 16:32:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1729609,2017-11-02 20:00:23 UTC,installer logs
1729609,2017-11-03 09:09:55 UTC,"During installation I can disable networking in the top bar, and than re-enable network.This way the installation goes well.
Can this be done in the preseed file?"
1729609,2017-11-04 09:09:02 UTC,"If I load a preseed file with url= kernel parameter, even an empty one, ubiquity creates two network interfaces.
If i do not load a preseed file in kernel options, network is ok."
1729609,2017-11-05 18:55:58 UTC,"Was  able to solve this by remaster the iso's installing resolvconf and ifupdown.
Then i could preseed a /etc/network/interfaces and have dns.
d-i     preseed/early_command string  echo -e ""iface `ip -o -4 r s to default | grep ^default | awk '{print $5}'` inet dhcp\nallow-hotplug `ip -o -4 r s to default | grep ^default | awk '{print $5}'`"" >> /root/etc/network/interfaces && ifup `ip -o -4 r s to default | grep ^default | awk '{print $5}'`"
1729620,2018-11-15 07:40:57 UTC,We have eventually come to a decision to use Debian 8 instead. With Debian 8 the module appears to work fine.
1729620,2018-02-28 18:37:25 UTC,"I tested this branch, and I added one commit to make various fixes. Though my understanding of OAI is limited, it seems to be working as intended. Here is my sign-off branch (2 commits):"
1729620,2018-03-28 18:08:51 UTC,"For the record, a regular bib record reingest on a database with the two OAI triggers causes this error:"
1729620,2018-05-20 08:16:49 UTC,I have tried to use the OAI module in Evergreen 3.1.1 (on Debian 9) which seems to have some parts of the original module already implemented (such as oai dababase schema).
1729621,2019-07-10 21:40:33 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1729621,2019-04-12 08:50:11 UTC,"Change abandoned by Radoslav Gerganov (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/612295
Reason: fira"
1729621,2019-03-28 03:33:28 UTC,"Reviewed:  https://review.openstack.org/612294
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=36d93675d9a6bf903ed64c216243c74a639a2087
Submitter: Zuul
Branch:    stable/queens"
1729621,2019-03-22 03:49:00 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1729621,2018-12-19 10:01:36 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1729621,2018-11-12 18:17:18 UTC,"Reviewed:  https://review.openstack.org/612293
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=732b0571cc27a8a1aba30f44c18317f13325aad3
Submitter: Zuul
Branch:    stable/rocky"
1729621,2018-10-22 09:45:13 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/612295"
1729621,2018-10-22 09:44:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/612294"
1729621,2019-10-30 16:40:21 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/529236
Reason: This was resolved in https://review.opendev.org/#/c/520024/"
1729621,2018-10-22 08:22:46 UTC,This bug affects *all* stable releases because there is race not only for vcpus_used but also for the compute stats which are used by the scheduler.  See bug #1798806 for more details.
1729621,2018-08-21 17:37:00 UTC,"Reviewed:  https://review.openstack.org/520024
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c9b74bcfa09d11c2046ce1bfb6dd8463b3a2f3b0
Submitter: Zuul
Branch:    master"
1729621,2018-07-10 07:51:13 UTC,"Change abandoned by Maciej Jozefczyk (<email address hidden>) on branch: master
Review: https://review.openstack.org/532924"
1729621,2018-01-29 23:12:46 UTC,There are more details in duplicate bug 1739349.
1729621,2017-12-22 08:06:22 UTC,Working on patch
1729621,2017-12-19 16:29:15 UTC,"To be clear, the CoreFilter isn't enabled by default, but Ram and Disk filters are."
1729621,2017-12-15 18:14:47 UTC,"Please note that Pike and Ocata schedulers are not affected by this issue, since starting in Ocata, we stop using the ComputeNode.vcpus_used value from the CoreFilter (which was deprecated/removed in Ocata) and instead use the (accurate) information from the placement API service about allocated VCPU resources for instances. Placement doesn't care or know about whether an instance is shutdown or not -- only if the instance is ""on"" the host."
1729621,2017-11-15 09:38:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520024"
1729621,2017-11-13 16:04:50 UTC,I see solutions:
1729621,2018-10-22 09:43:24 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/612293"
1729624,2019-01-19 18:28:47 UTC,I'm not able to recreate this in 3.1.2
1729625,2018-05-29 09:37:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729625,2018-05-29 10:06:49 UTC,"Confirming this in 18.04.
Krusader icon is not visible at all in bar."
1729634,2017-12-13 18:02:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729634,2017-11-02 17:04:29 UTC,"Cannot run
apport-collect 1729634"
1729634,2017-11-02 16:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1729634,2017-11-02 17:05:14 UTC,Set status to confirmed as requested in email from Ubuntu Kernel Bot
1729635,2017-11-02 16:30:16 UTC,This change was made by a bot.
1729635,2017-11-03 17:31:22 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1729635,2017-12-04 21:14:51 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1729635,2017-12-04 21:15:36 UTC,"It might also be good to test the latest mainline kernel, which is now v4.15-rc2:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc2"
1729635,2018-07-24 09:31:31 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1729638,2019-09-19 11:56:31 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1729640,2017-11-03 08:54:09 UTC,"Some actions are broken (even if the client is installed). For example, in nova we have a number of actions that refer to commands that have been deprecated and removed."
1729640,2019-09-17 08:35:53 UTC,I dropped assignment of this bug to a milestone since I believe this work should be a part of the planned refactoring of OpenStack actions (including moving them over to mistral-extra). So we may  not want to fix this bug at all.
1729648,2017-12-04 14:05:38 UTC,Do you perhaps have a more current contact address for upstream?
1729648,2018-01-18 08:37:34 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2016
1729648,2017-11-09 11:44:29 UTC,"Thanks, reported here: https://github.com/codership/galera/issues/487"
1729648,2017-11-06 09:52:41 UTC,Please check the steps to reproduce.
1729648,2017-11-06 15:11:06 UTC,Keep in mind that wsrep_autoincrement_control needs to be sane (off :) as well.
1729648,2017-11-06 15:05:55 UTC,"Also I have to mention that it is always the slave nodes that crash, not the node you run the test case on."
1729648,2017-11-06 15:04:28 UTC,Binary searching our configs for a crash found a hit: add
1729648,2017-11-09 11:14:30 UTC,Issue can be reproduced with upstream builder (Codership). You can file it with codership too so that when they fix the bug it get inherited in all variants.
1729651,2017-11-19 12:53:03 UTC,"We can investigate, but as near as we can determine this seems to be a bug in ifdown/ifup if it isn't actually doing what is written in /e/n/i"
1729651,2017-11-14 19:46:14 UTC,"That's not the problem; it happens with both bonded and non bonded
interfaces.  the first case i reported was non bonded - br-eth1.2733."
1729651,2017-11-14 19:35:29 UTC,"My suggestion would be to try larger net-bond-reconfigure-delay - set it to 30, check if the problem persists."
1729651,2017-11-13 18:21:36 UTC,"re comment #7, it was machine 0 that had the issue, with br-bond0.2736."
1729651,2017-11-13 18:32:29 UTC,Answering John's questions more thoroughly.
1729651,2017-11-03 14:24:18 UTC,ifdown/ifup the bridge gets setup properly with the parent interface. I'm not sure how many times this has happened - this is the first time we've positively identified this.
1729651,2017-11-03 14:23:10 UTC,"I don't have the original /e/n/i from that run, here are the files from a current run on the same machine with the same config (but in this case the bridge is setup properly)."
1729651,2017-11-03 13:28:54 UTC,Could you paste the original /e/n/i ? (it should be saved somewhere in /etc/network.
1729651,2017-11-03 05:33:19 UTC,"Juju does not directly drive brctl. We specifically rely on ifup to convert
/e/n/i into the running network configuration. (We chose that route so that
we can know things will also be working correctly on a reboot.)"
1729651,2017-11-02 17:07:44 UTC,Logs from the run.
1729651,2017-11-13 18:13:05 UTC,We hit this again last night.  The attached crashdump includes /etc/network.
1729661,2018-03-14 13:04:22 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/552899"
1729661,2018-03-14 12:57:50 UTC,"Reviewed:  https://review.openstack.org/547072
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=6321cf90304023c20dc6abb87e2fa20107b7051d
Submitter: Zuul
Branch:    master"
1729661,2018-03-14 13:02:00 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/552898"
1729661,2018-03-14 18:03:33 UTC,"Reviewed:  https://review.openstack.org/552899
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=c581c2af7b2bfdf60fb4467d7d5b17bed32fc85f
Submitter: Zuul
Branch:    stable/pike"
1729661,2018-08-01 12:19:04 UTC,"Reviewed:  https://review.openstack.org/585157
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=7e0d6b5477d6218467dc2692c74e4df8ea07fca6
Submitter: Zuul
Branch:    stable/pike"
1729661,2018-03-14 20:42:07 UTC,"Reviewed:  https://review.openstack.org/552900
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=707398789403293aaedc1d78ddc4a164611366c7
Submitter: Zuul
Branch:    stable/ocata"
1729661,2018-03-15 05:35:22 UTC,"Reviewed:  https://review.openstack.org/552898
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=d451edc2b83128e182e8885adf01f925ea2f98b6
Submitter: Zuul
Branch:    stable/queens"
1729661,2018-03-28 23:16:08 UTC,"Reviewed:  https://review.openstack.org/554675
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=5ca262641f5a8182d0f87c413f919c47b43b27ac
Submitter: Zuul
Branch:    stable/pike"
1729661,2018-07-18 14:04:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/583583"
1729661,2018-07-23 08:25:42 UTC,"Reviewed:  https://review.openstack.org/583583
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=0f24bb8bd45e6c3c4f1dc0fed1418c6be79525ee
Submitter: Zuul
Branch:    master"
1729661,2018-07-24 07:09:33 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/585156"
1729661,2018-07-24 07:10:01 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/585157"
1729661,2018-07-24 07:10:22 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/585158"
1729661,2018-07-31 15:15:48 UTC,"Reviewed:  https://review.openstack.org/585156
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=d0cc02fc82af1d6230ddcf8eb35f90671f40528a
Submitter: Zuul
Branch:    stable/queens"
1729661,2018-08-01 08:29:58 UTC,"Reviewed:  https://review.openstack.org/585158
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=0726f5cdfb66770db16fd373cdb2f8c8421b0924
Submitter: Zuul
Branch:    stable/ocata"
1729661,2018-03-14 13:04:50 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/552900"
1729671,2017-11-20 03:56:47 UTC,Issue seems to be inconsistent and possibly related to https://github.com/rabbitmq/rabbitmq-server/issues/714
1729671,2017-11-03 09:26:04 UTC,"Hi Nagendra,
I didn't hear of any plan to backport 3.6"
1729671,2017-11-03 15:46:53 UTC,Thanks Christian! Would update with the steps ASAP.
1729674,2018-06-25 14:56:30 UTC,"@katamo
4.14.xx is not a supported Ubuntu kernel.  I'm not sure where you pulled that kernel from, but it is not supportable."
1729674,2018-06-25 13:59:59 UTC,"@Kat,"
1729674,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1729674,2018-06-24 17:11:37 UTC,"Confirmed the following command resolved issue disconnect in transferring 25GB+ files over TB16 ethernet device via both SCP & SFTP
  `$ ethtool --offload enp14s0u1u2 rx off`"
1729674,2018-06-18 16:05:06 UTC,"Hi Mario, thanks for the pointer. Fedora stable releases are currently on 4.16.15 so that fix should be in place. I've got a TB16 at home so I can also try to reproduce this on Fedora 28 this evening."
1729674,2018-06-18 15:53:00 UTC,FYI this commit ended up landing related to this.  I would recommend to backport it.
1729674,2018-06-18 15:47:32 UTC,"I think I have the same issue with my laptop and dock (Dell TB16).
Laptop is new and installed in Fedora 28. All firmware are up-to-date."
1729674,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1729674,2018-02-28 06:55:04 UTC,"Weird, somehow it doesn't get pulled in for Xenail/Artful, I'll poke around to make the them in next kernel release."
1729674,2018-03-29 21:09:35 UTC,"Looks like this is more of a firmware issue with these docks and/or a driver issue with the 8152, so I'm throwing this back onto the queue where it was."
1729674,2018-03-29 20:20:43 UTC,Ran same tests against 4.13.0-38 on artful.
1729674,2018-03-22 19:20:49 UTC,At 6 iterations of ubuntu-17.04-server-amd64.img (4.2 gigs) I no longer see the corruptions on both 4.13.0-38 and 4.15.0-13 from xenial-proposed. Thanks!
1729674,2018-03-19 10:56:41 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1729674,2018-03-19 10:55:19 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1729674,2018-02-27 22:29:22 UTC,"Hi. I'm a user of another distro (gentoo), and found this bug while googling for a problem I'm having. I'm using a realtek-based USB3 to RJ45 gigabit adapter. This plugs directly into my laptop (not any sort of hub as with the DELL hubs above), which is a Toshiba Radius P20W-C-103, skylake based, with the following controller:"
1729674,2018-02-27 16:58:25 UTC,This also affects 16.04 (Xenial) but that isn't reflected in the ticket.
1729674,2018-03-30 05:47:13 UTC,I've already backported it:
1729674,2018-08-20 06:25:38 UTC,https://lkml.org/lkml/2018/8/20/42 There is a patch in upstream. Turn off the checksum offloading.
1729674,2019-03-02 13:21:55 UTC,Ref. bug # 1600126
1729674,2018-09-12 14:38:51 UTC,"@Tomas,"
1729674,2020-08-11 02:17:30 UTC,"(In reply to Alex Grönholm from comment #47)

> Thanks for the info (I own a WD19TB dock too) but that hardly helps with the
> TB16 problem. The WD19 series docks have working USB controllers, unlike
> TB16.
"
1729674,2020-08-10 07:54:23 UTC,"Thanks for the info (I own a WD19TB dock too) but that hardly helps with the TB16 problem. The WD19 series docks have working USB controllers, unlike TB16."
1729674,2020-08-10 02:34:02 UTC,Install via: sudo fwupdmgr install ~/Downloads/WD19FirmwareUpdateLinux_01.00.14.cab
1729674,2020-08-10 02:33:21 UTC,There is Dell TB19 firmware available that is installable via fwupdmgr on Linux: https://www.dell.com/support/home/en-bm/drivers/driversdetails?driverid=cwcf9&oscode=rhl80&productcode=dell-wd19tb-dock
1729674,2020-06-19 17:07:23 UTC,Seeing a similar issue on a Dell XPS 9300 (2020) with Linux 5.4:
1729674,2020-06-04 14:39:35 UTC,"This seems to help for me (Dell XPS13 2-in-1 7390 , kernel 5.6.15-300.fc32.x86_64) when switching (exact chain of events undetermined) between Dell DA300 (r8152 : Tx status -71) and Dell WD19TB ThunderBolt docking adapters :"
1729674,2020-03-02 12:11:42 UTC,"The same issue still happens to me on kernel 5.5.6-201.fc31.x86_64
Hardware is a Dell XPS 13 9370 with a Lenovo Thunderbolt 3 dock. My dmesg is full of these messages:"
1729674,2019-10-07 15:05:32 UTC,@oddbjornk @cristofaro
1729674,2019-09-26 08:29:05 UTC,Same here:
1729674,2019-06-21 13:05:47 UTC,"I seem to be seeing this again with the following kernel:
Linux xps15 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1729674,2019-03-29 00:43:53 UTC,"Thanks. It looks like I got this kernel version from the ""linux-signed-oem"" package: https://launchpad.net/ubuntu/bionic/+source/linux-signed-oem. I am not sure why my system is set up for that kernel package."
1729674,2019-03-28 22:26:14 UTC,"You will want to contact Dell support on that one as it appears you are
running a non- Ubuntu kernel version (it's probably Dell provided).  You
might simply need to upgrade."
1729674,2019-03-28 20:32:36 UTC,"Thanks for the work you all have done tracking this down. I am experiencing an issue with identical symptoms. I understand the problem should be fixed with 4.15+, so I may be experiencing a different bug. If anyone could help me determine that conclusively or point me in a direction that might help me fix this one, I'd really appreciate it!"
1729674,2018-02-27 16:37:33 UTC,Looks like this has been released with 4.15.0-9.10 which is available in bionic.
1729674,2019-02-28 14:23:36 UTC,cc
1729674,2018-09-13 05:04:18 UTC,"IIRC, I tested this scenario, and I didn't observe the issue on external r8152 dongle over the ASMedia xHC host."
1729674,2018-09-12 15:32:46 UTC,"Indeed, I found the mention of the pass-through only applying to the USB-C like a minute after I wrote my previous comment. Sorry for the noise."
1729674,2018-09-12 14:36:19 UTC,The issue is not unique to the integrated NIC in the dock (so the current workaround in r8152 is not sufficient). I have a r8152-based TP-LINK UE300 USB3-to-GigE dongle connected to my TB16 dock and I'm getting the same packet corruption when I don't turn off rx checksum offloading.
1729674,2018-02-22 21:39:03 UTC,"@kmously I see that you marked this fix as Fix Committed in Artful, but I do not see it in the master-next branch of artful.  I'm moving this back to In progress in artful as this does not appear to have been pushed to master-next for artful yet.  Feel free to push it back to Fix Committed when you accept or merge the patch into master-next."
1729674,2018-08-07 13:52:56 UTC,Our bug report from Launchpad:
1729674,2017-11-14 17:45:56 UTC,I am not using ipv6.
1729674,2017-08-25 17:32:15 UTC,"We both have XPS 13 9360. I had problems with Ethernet from the very beginning until I used a patched kernel. But after updating the firmware to 1.3.7 USB devices stopped working*. Now we're on 2.1.0 and they still don't work, no matter if we use the kernel patch or not. I have to have a USB hub connected directly to the laptop. The last working firmware for me was 1.3.5."
1729674,2017-08-25 16:21:59 UTC,"Well i'm not sure if they're related, but since the Ethernet device is a USB device on the hub, I would suspect them to be."
1729674,2017-08-25 16:16:47 UTC,"(In reply to Mario Limonciello from comment #12)

> @Martin
>
> Just to make sure - this is a TB16 not TB15 right?  This is sounding
> suspiciously like a hardware problem to me.
"
1729674,2017-08-25 15:55:50 UTC,@Martin
1729674,2017-08-25 13:22:26 UTC,"Martin, could you maybe try disabling RC checksum offloading and see if that helps? Then the corrupted packages should be discarded by the kernel (even if they are only corrupted during the transfer over USB). i.e. try again after running:"
1729674,2017-08-25 12:37:27 UTC,"Yes, for me, the Ethernet on the Docks is pretty broken. For example, when downloading a whole Koji build with about 13 packages, each time the download got broken at about 4th or 5th package, with (I think) a SSL handshake error. Also when downloading a Fedora ISO 4 times in a row, each of them got corrupted (md5 check just didn't pass)."
1729674,2017-08-25 12:16:55 UTC,"I'll let Martin speak for himself because it was him who complained about it to me.
I've been using kernel 4.12.8 which should have the patch included since the morning and haven't experienced any noticeable problems with the network."
1729674,2017-08-25 17:51:45 UTC,Ah OK thanks.  I just poked around the Dell forums a little bit and you guys aren't the first ones reporting this on 9360 after upgrade.
1729674,2017-08-25 12:10:12 UTC,"@Mario, I think what Jiri means is that without the patch it doesn't work well at all but even with the patch the situation is not perfect. Let me cc Benjamin, maybe we can add a test in our Fedora Hardware test suit for that. We still have the TB16 dock in Munich right now, maybe we can be of help."
1729674,2017-08-23 10:53:41 UTC,"(In reply to Christian Kellner from comment #5)

> For future reference, the mentioned patch git merged upstream, as commit
> 9da5a1092b13468839b1a864b126cacfb72ad016
> It also made it into stable, 4.12.4 I believe, as
> 5cc9b698a494827b15f74ef70a31d7911d00e52a
>
> So I think this should be fixed (or at least better) in F26, because we
> currently ship 4.12.5-300.fc26.x86_64
"
1729674,2017-08-22 12:56:22 UTC,"For future reference, the mentioned patch git merged upstream, as commit 9da5a1092b13468839b1a864b126cacfb72ad016
It also made it into stable, 4.12.4 I believe, as 5cc9b698a494827b15f74ef70a31d7911d00e52a"
1729674,2017-07-26 10:32:17 UTC,"After an initial hiccup with the LAN cable in the dock (and plugging it into a different socket), the performance is now much better (not sure if I can say it's perfect, yet) using the patched kernel.
Thanks!"
1729674,2017-07-17 20:44:12 UTC,"v5 has landed in the maintainer's tree (to target to 4.13-rcX) along with CC to stable.
https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus&id=353a73c757c0b856bb95f5e73cf41b10b685258d"
1729674,2017-06-27 16:15:03 UTC,"I added the v5 of the patch[1] to a kernel, scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=20206892"
1729674,2017-06-12 18:54:30 UTC,There is an upstream patch for the ASM1042A host controller[1] that has been reported to help with the issue (see corresponding launchpad issue[2]).
1729674,2017-06-12 18:51:16 UTC,"This is a Dell XPS 13 connected to the network via the TB16 dock.
Kernel is: Linux ag13.local 4.12.0-0.rc3.git0.2.fc27.x86_64 #1 SMP Tue May 30 19:36:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1729674,2017-08-23 16:12:50 UTC,"@Jiri,"
1729674,2017-08-25 19:23:29 UTC,"I won't be able to shortcut the process by pinging people, but I understand this is being investigated, it will just take some time."
1729674,2017-08-25 18:03:50 UTC,"We'll try to downgrade for the time being. BTW I also reported the issue to @DellCaresPRO like Barton George instructed me on Twitter. They said 10 days ago they had people looking into it, but there hasn't been any update since then, so I have no idea if someone is really looking into it and if they've made any progress, and who is ""they""."
1729674,2017-08-30 12:17:03 UTC,"Every now and then (especially when downloading large files), the ethernet simply stops working with the following log in dmesg.
Unloading the r8152 module results in gnome-shell dying. After reloading it, ethernet still doesn't work. Disconnecting the Dock in this state kills everything from GDM down to my user session."
1729674,2017-11-14 15:10:10 UTC,@Dave:
1729674,2017-11-14 07:38:38 UTC,"This issue only happens under 1Gbps speed with checksum offloading.
Turn off checksum offloading or change the speed to 100Mbps can workaround the issue."
1729674,2017-11-13 07:44:00 UTC,"Tried two other r8152 devices,
- r8152 <-> USB-C <-> Host system. No checksum issue.
- r8152 <-> Genesys Logic Hub <-> USB-C <-> Host system. No checksum issue."
1729674,2017-11-13 06:21:33 UTC,I can reproduce the issue on a TB15 (which should be the same?).
1729674,2017-11-11 18:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1729674,2017-11-10 14:44:42 UTC,"I just upgraded to 17.10, and tested out 4.14.0-041400rc8-generic.  The issue still exists in 4.14.0-041400rc8-generic. It's pretty simple to reproduce @superm1, you really should get your device partners alerted about this."
1729674,2017-11-03 12:55:45 UTC,"The asmedia host controller is what the realtek device is hooked up to.
That patch for asmedia host controller was developed specifically because
of problems with Ethernet not working at >100mbps and causing errors in the
syslog. So yeah that patch does help in that regard :("
1729674,2017-08-28 09:05:50 UTC,"(In reply to Benjamin Berg from comment #11)

> Martin, could you maybe try disabling RC checksum offloading and see if that
> helps? Then the corrupted packages should be discarded by the kernel (even
> if they are only corrupted during the transfer over USB). i.e. try again
> after running:
>
>   ethtool --offload $DEVICE rx off
"
1729674,2017-11-02 22:03:22 UTC,Going the opposite direction you may or may not have https://github.com/torvalds/linux/commit/9da5a1092b13468839b1a864b126cacfb72ad016#diff-8e88b7e83565580efd59e852f42341a5
1729674,2017-11-03 03:54:59 UTC,"That one applies pretty exclusively to asmedia devices.  I don't see how
that would affect a realtek device.  Either way, I'll try to carve out some
time to check the mainline kernel and bisect if possible.  It's pretty
straightforward to reproduce.  All I've been doing is downloading the an
ubuntu iso, and checking the md5sum of it.  If I have hardware offloading
on it will not pass the md5sum."
1729674,2017-11-02 21:22:10 UTC,Going the opposite direction it looks like 4.10.0-38-generic may be working fine.  b20cb60 may actually be a regression for rtl8153.
1729674,2017-11-02 20:56:54 UTC,For completeness the ethernet device is.
1729674,2017-11-02 20:42:31 UTC,I should have been more specific I'm on 4.13.0-16-generic which already contains that change.  Good to see you are still around watching this project.
1729674,2017-11-02 20:18:51 UTC,Does this same behavior happen in 4.14-rc7?  There's a few interesting commits that have happened since 4.10 (eg https://github.com/torvalds/linux/commit/b20cb60e2b865638459e6ec82ad3536d3734e555#diff-d45f6c5dfa1088acc4fb00e7636dbba7)
1729674,2017-09-11 13:46:40 UTC,Running kernel-4.13.0-1.fc27.x86_64.
1729674,2017-09-05 10:13:36 UTC,"It got really annoying lately. How do I downgrade to 1.3.5, please? I can't find it on the Dell website and fwupd doesn't provide anything too."
1729674,2017-08-30 13:41:16 UTC,As I understand the particular problem linked with the issue in BIOS 1.3.6/1.37 adjusts a voltage regulator (to fix something else; this was an unanticipated/undiscovered regression).  I would recommend for now to downgrade to 1.3.5 until a fixed BIOS is issued.
1729674,2017-11-02 21:52:13 UTC,I spoke too soon.  It looks like both 4.10-0-38 and 4.13.0-16-generic have issue.
1729674,2017-11-14 17:53:11 UTC,I also just went through the process of reproducing this while watching the kern.log.  Absolutely 0 messages came out.  If you find some verbose debugging you want me to turn on let me know.
1729675,2017-11-29 11:39:24 UTC,"I think the feature here is to add support for enabling the consistency group API, rather than to provide direct management of the policy.json (which I remain a -1 on)."
1729675,2018-01-04 16:06:57 UTC,"I've commented on https://review.openstack.org/#/c/525873 to this effect; enabling support for the CG API should be driven based on the storage backends that form part of the deployment, rather than being a blind configuration option that the user has to enable."
1729675,2018-07-11 03:04:23 UTC,"Change abandoned by Seyeong Kim (<email address hidden>) on branch: master
Review: https://review.openstack.org/525873"
1729676,2018-07-09 14:41:04 UTC,We just upgraded to 3.0.9 and are still unable to merge patron records in the web client. We would like for it to be an option in Group Member Details. We usually don't need to merge more than one account at a time so buckets just complicate the process.
1729676,2017-12-27 15:16:45 UTC,"+1 for adding to the user buckets and Group interface, as well.  It's a feature used by our libraries."
1729676,2017-11-03 14:12:53 UTC,Anybody know what rationale there was behind not adding that action to the web client interface?
1729676,2017-11-03 12:48:49 UTC,"Adding a link to bug 1441772, which was recently set to ""Won't Fix"" due to the lack of this action being available in this web client interface. If we add the action to the Group Member details page, we should ensure that we also address of this issue, which appeared to primarily be a UI issue."
1729676,2017-11-06 06:41:07 UTC,"I was just about to open a wishlist bug for adding the action to user buckets, so +1 for that.  Also +1 for adding the action to the Group interface."
1729680,2017-11-23 00:58:27 UTC,I've updated the bug description because this appears to be a Tyan S3992-E motherboard hardware issue. The product info for the S3992-E motherboard says it doesn't support PCI-e graphics cards:
1729680,2017-12-02 17:59:37 UTC,"The Tyan S3992-E hardware issue I encountered attempting to use an nVidia GTX1060 is that this motherboard only supports PCI Express x16 Gen1 but the GTX1060 requires Gen2/3 and is not detected by the nVidia or Nouveau kernel drivers. However, a GTX460 graphics card and a Tesla C2050 GPGPU are both detected and supported by the proprietary nVidia 384.90 driver on the same Tyan S3992-E motherboard.."
1729680,2019-04-22 02:51:14 UTC,"Hello Tony,
GTX1060 is quite new (release in 2018 Oct.) in comparison to the OS listed here (16.04 released in 2016 Apr.) and 4.10 kernel is older than the card too."
1729680,2019-06-21 04:17:26 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1729695,2018-03-19 12:03:36 UTC,"The above has nothing to do with this bug report.  Perhaps you should post
it to https://bugs.launchpad.net/bugs/1727653"
1729695,2018-03-19 07:07:53 UTC,Hello
1729695,2018-02-01 14:16:41 UTC,Ubuntu 17.10 (duplicity 0.7.12)
1729695,2017-11-20 02:12:43 UTC,I suspect this is fixed in duplicity 0.7.15 now -- by commit 1318 [1].
1729695,2017-11-19 17:10:30 UTC,"Take a look at the message in duplicity-team called ""Help with unicode
branch (for Python3 support)""."
1729695,2018-05-12 00:17:18 UTC,"I just installed Windows 10's April 2018 Update, and it looks like it enabled Fast Startup again."
1729695,2017-11-18 09:58:35 UTC,"I have the almost the same system configuration as Paul Nickerson, except that backups are stored on a separate NTFS-formatted drive, that neither Ubuntu nor Windows boots. Disabling Fast Startup solved the problem for me too. Thanks for sharing the solution!"
1729695,2017-11-18 09:14:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729695,2017-11-08 13:30:32 UTC,"I thought of something that could be a change on the system. I dual boot Ubuntu and Windows. The target disk for backups is formatted as NTFS, and Windows 10 mounts it when it boots. I just checked the Windows logs, and the second to last time I booted Windows was just before the backup started failing. Then, the last time I booted Windows was just before the backup started working again."
1729695,2017-11-08 13:08:26 UTC,"I don't know why, but the backup started working again yesterday. I did not do anything to try and fix it."
1729695,2017-11-05 04:30:23 UTC,"Ubuntu 17.04 was fresh installed in early July 2017, and I've since upgraded to 17.10 (I did not fresh install 17.10). I did not reconfigure Deja Dup before or after that upgrade."
1729695,2017-11-04 10:51:06 UTC,Hello!
1729695,2017-11-19 16:42:30 UTC,"Actually, that looks like what is happening — an error is bubbling up from the system and when trying to format it, duplicity is misconverting from/to Unicode and crashing. Possibly due to a translation."
1729704,2018-09-18 08:43:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729705,2017-11-02 23:04:58 UTC,I really like the high level idea.
1729705,2017-11-03 12:34:09 UTC,"If this is about just adding a periodic task to query the ipmi controller just like the sensors we have, I'm ok with this, if you want to do what Julia describes I think this would need a spec."
1729709,2017-11-02 22:59:47 UTC,Note that this error occurred on Ubuntu 16.04.0 KMM PPA 4.8.0 but cannot be reported for package reasons.
1729709,2017-11-02 23:59:29 UTC,"The same will happen with any version of KMM under any distribution or OS.  There is nothing KMM can do if Yahoo has decided to stop providing this data in this manner.  Consider using one of the other quote sources KMM provides.  If someone identified an alternate URL at Yahoo which works, it can be used by KMM, but probably not until version 5.0 is released."
1729709,2017-11-03 19:08:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729709,2020-07-09 15:40:06 UTC,"This should be fixed in recent 5.x versions (certainly 5.1.0, probably 5.0.8) but using the ""Yahoo Finance"" source, not just ""Yahoo"".  I'm not certain about 4.8.x."
1729709,2020-07-09 17:55:37 UTC,"There is no ""Yahoo Finance"" source in 5.0.8"
1729712,2017-11-02 23:30:27 UTC,Let me know what other information I can provide. Attached is syslog for the same period.
1729712,2017-11-02 23:32:34 UTC,Forgot to mention: The controller was running juju version 2.2.5
1729712,2017-11-02 23:49:57 UTC,Might be related to bug 1727973 ??
1729712,2017-11-02 23:52:54 UTC,I understand that it's common to need to restart this controller after an upgrade? Other than after an upgrade do you find you need to restart it at other times?
1729712,2017-11-03 05:27:42 UTC,"A few things that are notable, nothing that seems like a smoking gun:
2017-11-01 20:39:11 WARNING juju.apiserver log.go:168 http: TLS handshake
error from 91.189.90.53:43927: EOF"
1729712,2017-11-06 04:36:13 UTC,"Hi John,"
1729713,2017-11-03 02:11:46 UTC,This bug was fixed in the package gdm3 - 3.26.2.1-0ubuntu1
1729736,2018-05-14 11:34:00 UTC,"I'm experiencing the same issue on an XPS 9560 with Ubuntu 18.04 (same symptoms, same dmesg output).
Any new information required?"
1729736,2017-06-30 18:08:43 UTC,I believe including a full dmesg (from boot) would be helpful to show what may be going wrong.
1729736,2017-06-30 17:13:52 UTC,"Hello,"
1729736,2019-12-04 09:29:50 UTC,-- GitLab Migration Automatic Message --
1729736,2019-01-09 09:54:58 UTC,"Created attachment 143032
dmesg from thinkpad x1 extreme / GTX 1050 Ti on kernel 4.20 with discrete only graphics"
1729736,2019-01-09 09:53:04 UTC,"Created attachment 143031
dmesg from thinkpad x1 extreme / GTX 1050 Ti on kernel 4.20 with hybrid graphics"
1729736,2018-06-19 12:30:46 UTC,With Linux kernel 4.18.0-041800rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline :
1729736,2018-06-19 12:26:42 UTC,"With Linux kernel 4.18.0-041800rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline, graphical login fails."
1729736,2018-04-18 18:41:09 UTC,"With Linux kernel 4.17.0-041700rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline, I confirm that systematically :"
1729736,2018-04-18 18:08:09 UTC,"With Linux kernel 4.17.0-041700rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline, graphical login fails, and the machine is frozen."
1729736,2018-04-18 18:03:33 UTC,"With Linux kernel 4.17.0-041700rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline, graphical login fails."
1729736,2018-03-17 02:42:34 UTC,"With Linux kernel 4.16.0-041600rc5 from http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically fails to answer, and makes the whole machine freeze after some time."
1729736,2018-03-17 02:39:40 UTC,"With Linux kernel 4.16.0-041600rc5 from http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically fails to answer, and makes the whole machine freeze after some time."
1729736,2017-12-12 16:01:03 UTC,"With Linux kernel 4.15.0-041500rc3 from http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically fails to answer, and makes the whole machine freeze after some time."
1729736,2017-12-12 09:05:12 UTC,"@Étienne Could you please provide the information that was asked in comment #1 and comment #2 of this bug report? Adding `nouveau.runpm=0` to the kernel command line should avoid the freeze but will prevent the NVIDIA card from being suspended.
Looking at the bug report mentioned in comment #2, could you try booting with `acpi_osi=! acpi_osi=""Windows 2009""` and/or `acpi_rev_override=5` on the kernel command line (without `nouveau.runpm=0`)?"
1729736,2017-12-11 23:45:25 UTC,"With Linux kernel 4.15.0-041500rc3 from http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically fails to answer, and makes the whole machine freeze after some time."
1729736,2017-12-12 15:29:49 UTC,"Created attachment 136105
lspci for GP107M [GeForce GTX 1050 Ti Mobile]"
1729736,2017-11-28 21:51:57 UTC,At https://bugs.freedesktop.org/ :
1729736,2017-07-04 12:22:14 UTC,"With the ""new PCIe PM stuff"", if nouveau is not loaded and something else enabled automatic runtime PM (via powertop, via TLP or manually by writing ""auto"" to /sys/bus/pci/devices/.../power/control) for the Nvidia PCI devices, then indeed the problematic ACPI methods could be triggered."
1729736,2017-07-10 20:44:39 UTC,"this is because lspci reads the config file, which then triggers a full GPU wake up, which is a silly thing to do in the first place."
1729736,2017-11-03 03:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1729736,2017-11-03 12:02:27 UTC,"With nouveau enabled in Linux kernel 4.13.0-16 on GP107M [GeForce GTX 1050 Ti Mobile], 'lspci' systematically makes nouveau fail (1 CPU stuck), and returns nothing."
1729736,2017-12-04 21:22:18 UTC,"With Linux kernel 4.15.0-041500rc2 from http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically fails to answer, and makes the whole machine freeze after some time."
1729736,2017-11-12 20:32:55 UTC,Concerning the support of Nvidia GP107M [GeForce GTX 1050 Ti Mobile] by the 'nouveau' module of Linux kernels :
1729736,2017-11-13 18:39:53 UTC,I am trying to use 'nouveau' with GP107M [GeForce GTX 1050 Ti Mobile].
1729736,2017-11-03 17:16:04 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1729736,2017-11-21 23:19:11 UTC,"With following Linux kernels, 'lspci' systematically fails to answer, and makes the whole machine immediately freeze :
-  4.13.0-17 from Ubuntu 17.10 (Artful)
-  4.14.1    from http://kernel.ubuntu.com/~kernel-ppa/mainline"
1729736,2017-11-21 23:21:53 UTC,"With following Linux kernels, 'lspci' systematically fails to answer, and makes the whole machine immediately freeze :
- 4.13.0-17 from Ubuntu 17.10 (Artful)
- 4.14.1 from http://kernel.ubuntu.com/~kernel-ppa/mainline"
1729736,2017-11-27 20:38:40 UTC,"With Linux kernel 4.15.0-041500rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically fails to answer, and makes the whole machine freeze after some time."
1729736,2017-11-27 20:41:09 UTC,"With Linux kernel 4.15.0-041500rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically fails to answer, and makes the whole machine freeze after some time."
1729736,2017-11-28 03:19:19 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/nouveau"
1729736,2017-11-13 18:44:44 UTC,"With Linux kernel 4.14.0 from http://kernel.ubuntu.com/~kernel-ppa/mainline (released yesterday), 'lspci' systematically fails to answer, and makes the whole machine freeze after some time."
1729738,2018-03-28 12:03:18 UTC,"On 16.04 I have zoom working in all described situations; touchpad (two fingers), keyboard (ctrl+(+/-)). UI buttons and scrollwheel on mouse also works for me."
1729738,2018-03-28 18:43:34 UTC,"I haven't been using GPX Viewer for a while, but I've just checked it, and everything works now again. I believe that there was an issue in Ubuntu, which is already fixed now."
1729741,2017-11-13 16:17:36 UTC,"Robert, can you confirm a few things?"
1729741,2018-12-12 18:11:03 UTC,Removing myself as assignee since I'm not actively working on this and I'm not sure if it's still an issue.
1729741,2017-12-07 23:56:30 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1729741,2017-11-15 08:56:52 UTC,"1) The usage is currently by terraform which seems to call /v2/tenant-id/os-security-groups
so I guess we will have to file a bug-report there"
1729741,2017-11-13 09:59:29 UTC,"Re-opened this bug: I am not sure the fix did anything.
I applied the fix and still see the exact same thing in the neutron logs, e.g.:"
1729741,2017-11-03 14:09:52 UTC,"Depending on which API you're referring to, this would still be an issue:"
1729741,2017-11-03 16:31:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/517648"
1729741,2017-11-03 03:24:12 UTC,The problem seems to be here in the security_groups.py:
1729741,2017-11-03 13:43:08 UTC,"I think I actually reported a similar bug quite awhile ago, trying to find it."
1729741,2017-11-10 04:07:40 UTC,"Reviewed:  https://review.openstack.org/517648
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dc658dbdcf2325cf6f27d9ae61d85b835f8410f8
Submitter: Zuul
Branch:    master"
1729741,2017-11-03 03:00:38 UTC,FYI: tested with Kilo/Mitaka & Pike
1729741,2017-11-03 13:47:55 UTC,I was thinking of bug 1580621 and I did point this out in comment 1:
1729761,2017-11-09 06:48:32 UTC,"Reviewed:  https://review.openstack.org/517527
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=b72ae35044da6d02794eb5b87372de299f212f6f
Submitter: Zuul
Branch:    master"
1729761,2017-12-08 21:43:16 UTC,This issue was fixed in the openstack/congress 7.0.0.0b2 development milestone.
1729768,2017-11-03 05:58:24 UTC,Other tempest tests with similar issue :
1729768,2017-11-06 18:26:06 UTC,"Even with workaround of having a 5 sec sleep before deleting the SG(as done in bug 1621622), few tests continue to fail."
1729768,2017-11-07 20:04:02 UTC,"Can you provide audit logs immediately after the test is run?
contrail-logs --object-type config --last 10m"
1729768,2017-11-08 04:29:02 UTC,"Attached is the log-file for ""all"" cassandra logs after the test tempest.api.compute.admin.test_create_server.ServersWithSpecificFlavorTestJSON"
1729768,2017-11-08 04:29:52 UTC,"Attached is the log-file for ""all"" cassandra logs after the test tempest.api.compute.admin.test_create_server.ServersWithSpecificFlavorTestJSON"
1729768,2017-11-08 04:30:09 UTC,The SG to track would be 30ff3b58-216f-464c-9c80-fa6fef6d50e7
1729768,2017-11-03 05:06:48 UTC,"It is a timing issue, if i add a few secs sleep just before deleting the SG, it goes through fine"
1729783,2018-01-24 12:10:41 UTC,"Bonjour, la solution se trouve à cette adresse : https://forum.ubuntu-fr.org/viewtopic.php?id=1541691"
1729783,2017-11-03 12:47:52 UTC,"Merci pour ta réponse.
La version est 0.3.2 Freya (64 bits), mémoire vive 3,8 Gio et stockage 28,5 Go. J'ai acheté le PC en octobre 2016 chez Piqo avec elementary déjà installé.
Je n'ai pas de réponse à ta dernière question.
Bonne réception"
1729783,2017-11-03 10:04:16 UTC,"pouvez-vous fournir plus d'informations svp?
quelle version d'Elementary vous utilisez?
est-ce que c'est une fresh installation? ou tu l'as installé et utilisé depuis un certain temps?
combien d'espace disque as-tu réservé à / lors de l'installation?"
1729784,2017-11-03 09:43:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/517592"
1729784,2017-11-29 01:38:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/523644"
1729784,2017-12-01 01:41:07 UTC,"Reviewed:  https://review.openstack.org/517592
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ecf12a4dd132e4aa9c2e3563a41acc0ab6d13978
Submitter: Zuul
Branch:    master"
1729784,2017-12-03 12:56:08 UTC,"Reviewed:  https://review.openstack.org/523644
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ae56863746cdd69e27f2e046a81f581541508168
Submitter: Zuul
Branch:    stable/pike"
1729785,2017-11-03 12:35:46 UTC,"Thanks for bringing this to our attention, it seems the:-
http://linuxtracker.org:2710/00000000000000000000000000000000/announce
tracker is currently having problems (""Could not connect to tracker""). I'm currently trying to bring this to their attention."
1729785,2017-11-12 22:36:10 UTC,"The tracker is back up now, so the torrents should be working again."
1729787,2017-11-03 07:10:15 UTC,This is a left-over debug message that was not removed in a timely manner. It does not signify any issue and has been removed from codebase.
1729787,2017-11-03 09:14:29 UTC,"Isn't ""Fix committed"" a better status here ?"
1729787,2017-11-03 10:16:23 UTC,It's fixed in 2.3 but not 2.2.6
1729798,2017-11-03 10:37:54 UTC,"In fact, those ""missing"" packages are in the ""recommended"" section of slic3r."
1729805,2018-05-10 04:51:51 UTC,"So it's been a while, but I haven't forgotten. I've been quite busy with work unfortunately. I have a few bug fixes I've added to my personal copy but none for the above issue that's currently blocking us."
1729805,2017-11-09 07:57:06 UTC,"To correct myself above, copies and collation don't apply. The page selection (all, selection, current, ranges) could apply if the bugs on multipage support ever landed."
1729805,2017-11-09 07:49:34 UTC,"This is the dialog I'm launching, snapped from my Windows 7 box at home. There's two-ish dialogs you can launch with PrintDlg[A], this one is called the ""Print Setup"" dialog according to Microsoft."
1729805,2017-11-08 11:03:55 UTC,">> (and it may not have to do with Inkscape)
"
1729805,2017-11-08 10:59:04 UTC,testcase*
1729805,2017-11-08 10:58:14 UTC,"Though now getting what you're saying, if Python 32-bit is able to interface with the Windows 10 64-bit DLLs without barfing, then that would be a restcase to try. Especially in light of my previous comments that I thought I recalled 64-bit Inkscape shipping with 32-bit Python. I'll see about trying the extension in a 32-bit Python on my Windows 10 box outside of Inkscape."
1729805,2017-11-08 10:54:23 UTC,"I don't think so on the Unicode front, as this is Python 2.7 so I'd have to do u""stuff here"" to explicitly get Unicode but I can go check just to be sure. I don't recall off the top of my head passing in any string values. Mostly reading ones the come out of the API."
1729805,2017-11-08 10:29:12 UTC,"A third idea (not sure if it applies here either):
Might there be a Unicode vs ANSI issue (i.e. do you maybe pass an UTF8 string somewhere that is supposed to be an ANSI string which typically messes up character counts and results in strange errors?)"
1729805,2017-11-08 10:27:22 UTC,"I don't have any experience with calling WinAPI from Python, so I can't really help you there, but two ideas which might help debugging:
- Have you considered differences between 32-bit/64-bit builds?
  Not sure if this is a thing in Python but maybe some field in one of
  the structs changes size and needs to be defined differently?
- I read somewhere (and it sounds convincing) that
  ""access violation reading 0x00000044""
  might indicate we're trying to access a field of a struct
  which points to NULL (i.e. 44 bytes offset from NULL)"
1729805,2017-11-08 08:19:22 UTC,"It worked on my Windows 10 box, so I started in on PrintDlgEx(A) but so far it doesn't want to work. Just tells me I'm giving it some argument that it doesn't like. I'll keep plugging away though."
1729805,2017-11-04 17:46:59 UTC,"I get the print dialog to appear on my Windows 7 box, so I'll have to head down to my Windows 10 laser cutter PC (it's not at home) and see if I get different results. If it works there, then I can try switching from PrintDlgA to the newer PrintDlgExA function* and see if it works better for you. Otherwise if it exhibits the issue you report I may be able to fix my call to PrintDlgA. Unfortunately my weekend is pretty full, so it might be Monday before I can get that checked."
1729805,2017-11-04 17:23:53 UTC,"the problem does not appear to be related to XP. Just for curiosity, I ran this from DOS, in Windows 10, and got the output:"
1729805,2017-11-03 21:27:21 UTC,That seems like a buffer read-after-end. I may need to recheck the fields on the DEVMODE struct I use to see if one of the sets of fields I added is valid for XP. However I think the even the newer fields were added before XP.
1729805,2017-11-03 20:57:14 UTC,I do not see any hidden windows anywhere.
1729805,2017-11-03 20:51:58 UTC,"I'll check my copy again this evening, but in the mean time there is something simple you could try:"
1729805,2017-11-03 20:31:52 UTC,"- it happens with any file, even if I just draw a single line and try to print it.
- happens regardless of the settings in the ""General Settings"" panel
- I just get that single window, very quickly, no other windows and no printer dialog"
1729805,2017-11-03 19:22:02 UTC,Also your reported version of Inkscape is the same version I tested on at home and likely the same version I used when testing with my laser cutter. So I would guess this is an environment issue.
1729805,2017-11-03 19:14:08 UTC,That's odd. There's no other instructions I know of.
1729805,2017-11-03 14:08:12 UTC,"I tested this code on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1729805,2017-11-03 10:33:47 UTC,"Mh, it's arcane windows python code to me, I'm subscribing Alvin to this bug so that he could take a look at it if possible since he wrote the original code:"
1729805,2017-11-03 09:02:07 UTC,"I forgot to finish a line above. '- ""job type"" selector to print only' should read:"
1729806,2018-01-26 00:43:48 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1729806,2018-01-16 11:12:14 UTC,"Reviewed:  https://review.openstack.org/518556
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c34e37eef31add8224211b799a56d866c5013fbd
Submitter: Zuul
Branch:    master"
1729806,2017-11-30 08:59:41 UTC,"mriedem : Is is possible to add a unique constraint to these columns since they of type ""Text()"". I do not see MYSQL supporting it directly, I see some hashing solution being suggested. Is there a work around that we use in nova ?"
1729806,2017-11-08 15:04:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518556"
1729806,2017-11-03 13:39:14 UTC,"Ideally we'd just have a unique constraint across those two columns in the cell_mappings table in the API database, but I'm not sure if there is a case where we'd want more than once cell to have the same db/transport urls, probably not, especially since we don't have a concept of disabled cells."
1729821,2020-04-22 11:25:04 UTC,SMB shares still do not work - for Libreoffice 6.4 that is. The the apt-get installed version for LibreOffice6.4 does work for SMB shares.
1729821,2018-02-08 21:16:08 UTC,Not just the [snap] package. Version LibreOffice 5.4.2.2 40m0(Build:2) from standard ubuntu repositories. Also an issue with AFP shares.
1729821,2018-02-09 07:46:36 UTC,"General input/output error while accessing /run/user/1000/gvfs/smb-share:server=192.168.1.1,share=bridge/vasilisc/key.csv.
-----
LANG=C snap info libreoffice"
1729822,2017-11-04 10:20:47 UTC,"~$ sudo appstreamcli refresh-cache --verbose
.
..
..."
1729835,2019-03-05 13:33:03 UTC,Is this still an issue?
1729836,2018-01-14 12:55:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729836,2018-01-16 17:08:18 UTC,Can your provide the terminal output of running update-initramfs with the -v switch? Thanks in advance.
1729836,2018-01-19 04:42:11 UTC,"Sure, I've attached update-initramfs -v output, and confirmed that the generated initrd is unusable, both with kvm and a real computer."
1729836,2018-01-19 05:12:32 UTC,I think I figured out the cause. Basically PEBCAK..
1729836,2018-01-19 05:28:29 UTC,Logged at https://github.com/sickill/stderred/issues/63
1729840,2019-09-19 11:56:34 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1729853,2017-11-04 23:46:23 UTC,Hello all
1729860,2017-11-04 03:05:35 UTC,"terminator.py:
538         # Size the GtkPaned splitter handle size.
539         css = """"
540         if self.config['handle_size'] in xrange(0, 21):
541             css += """"""
542                 .terminator-terminal-window GtkPaned,
543                 .terminator-terminal-window paned {
544                     -GtkPaned-handle-size: %s; }
545                 """""" % self.config['handle_size']
546         style_provider = Gtk.CssProvider()
547         style_provider.load_from_data(css)
548         self.style_providers.append(style_provider)"
1729860,2017-11-04 22:14:52 UTC,"OK, So that's a little more perplexing. The only thing I can think of is the theme. Have you tried Terminator under a different theme? I recommend trying with Ambiance. Exit all Terminator windows, and under a different terminal program (i.e. gnome-terminal):
$ GTK_DEBUG=interactive terminator
Then change the the GTK+ Theme under the Visual tab and see if the handle sizing starts to work."
1729860,2017-11-04 09:58:48 UTC,"Sorry for having so little information earlier. So I updated to 1.91 manually since im on 17.04 and still not working, I didnt touch any of the python or config files at all, here is also my GTK versions"
1729860,2017-11-03 21:24:51 UTC,"Also I tried setting the wide_handle property but it doesn't seem to be working, I just changed the original handle_size property to this:"
1729860,2017-11-03 20:24:32 UTC,"In the mean time, there's a new gtk_paned_set_wide_handle (boolean), so two different width are still available in certain themes. Adwaita seems to define two different widths, Ambiance doesn't."
1729860,2017-11-03 21:12:16 UTC,"Aw that really sucks, would've been a pretty killer feature, sadly I missed the boat on that one. Any reason they decided to change it to a boolean setting instead?"
1729860,2017-11-03 20:15:30 UTC,"This possibility was removed from GTK+. Accordingly, such a warning is printed:"
1729878,2017-11-03 15:18:56 UTC,"It's possible these are just OOMkiller related, but the first few call traces seem centered around snapd and I don't notice any OOMKiller messages until towards the end of the dmesg log."
1729878,2018-08-15 14:49:05 UTC,"These stressors are expected to trigger the OOM killer.  The oom adjustment for the stressor child processes is always adjusted to make them the first processes to be OOM'd.  However, the kernel make's it choice on what gets OOM'd depending on many factors, so the stressors may end up triggering other hoggy processes to be OOM'd as well."
1729878,2018-07-24 09:33:32 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1729878,2018-03-28 08:56:16 UTC,Is this still an open bug or can it be closed now?
1729878,2017-11-13 19:54:32 UTC,I'm not able to recreate this on a smaller generic amd64 machine:
1729878,2017-11-13 19:52:40 UTC,"Because of the above, I've re-opened the kernel tasks :("
1729878,2017-11-13 19:52:12 UTC,"I'm still able to trigger problems with the ""stack"" stressor on the Xeon Phi..."
1729878,2017-11-10 23:30:24 UTC,"Given that, I'm marking the kernel tasks as invalid as this appears to be stress-ng being over aggressive."
1729878,2017-11-10 21:44:16 UTC,"Ok, I've narrowed it down to the brk and stack stressors in stress-ng.  I've recreated this on amd64, ppc64el and s390x across 4.4, 4.10 and 4.13 kernels."
1729878,2017-11-08 21:20:41 UTC,The call that invokes stress-ng looks like this:
1729878,2017-11-08 21:18:17 UTC,"Ok, so a little bit further.  This seems to be that stress-ng is triggering OOMkiller which I'm not sure it should be, unless it's just really writing a LOT of data to memory."
1729878,2017-11-06 14:54:35 UTC,"So over the weekend, I retried with 4.14.0-041400rc6-generic (since
rc7 was not successfully built when I tried this)."
1729878,2017-11-06 09:28:59 UTC,"On 3 November 2017 at 19:27, Jeff Lane <email address hidden> wrote:

> On Fri, Nov 3, 2017 at 1:13 PM, Joseph Salisbury
> <email address hidden> wrote:
>> Do you know which prior kernels did not exhibit this bug?  Was it 4.12
>> or earlier?
>
> I ""think"" it happened with 4.10 as well, but I'm not positive, I ran
> some tests before realizing I was still on 17.04 and upgrading the VM
> to 17.10.
>
>> Could you test the mainline kernel to see if this bug is already fixed upstream:
>> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7
>
> Just a heads up, no, I cant:
>
> Build for s390x failed (see BUILD.LOG.s390x):
>   linux-headers-4.14.0-041400rc7_4.14.0-041400rc7.201710292231_all.deb
>   *_s390x.deb
> \
>
> Is there a better place (internal perhaps) to get mainline builds?
>
"
1729878,2017-11-03 19:27:52 UTC,"On Fri, Nov 3, 2017 at 1:13 PM, Joseph Salisbury
<email address hidden> wrote:

> Do you know which prior kernels did not exhibit this bug?  Was it 4.12
> or earlier?
"
1729878,2017-11-10 23:25:27 UTC,Also retried on amd64 and the effect was the same:
1729878,2017-11-03 17:13:45 UTC,Do you know which prior kernels did not exhibit this bug?  Was it 4.12 or earlier?
1729878,2017-11-03 19:03:15 UTC,"This seems like stress-ng was eating a load of pages and snapd just got victimized because it was expanding it's memory when there were no free pages.  Oom killer can seem arbitrary like this, I expect there is a good reason for it."
1729878,2017-11-03 15:22:13 UTC,"I'm also not sure why we're hitting the OOM killer either, the memory config is light, but not light enough that we'd trigger this sort of thing on other systems, perhaps its s390x specific:"
1729878,2017-11-03 15:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1729878,2017-11-03 16:08:13 UTC,apport information
1729878,2017-11-03 16:08:15 UTC,apport information
1729878,2017-11-03 16:08:17 UTC,apport information
1729878,2017-11-03 16:08:18 UTC,apport information
1729878,2017-11-10 22:43:00 UTC,"So I did this on 4.4 on ppc64le with 32GB RAM and 96GB Swap:
ubuntu@entei:~$ free -lm
              total        used        free      shared  buff/cache   available
Mem:          32565         656       30603           2        1304       30503
Low:          32565        1961       30603
High:             0           0           0
Swap:         97695         342       97353"
1729878,2017-11-03 16:08:21 UTC,apport information
1729878,2017-11-03 16:08:20 UTC,apport information
1729878,2017-11-03 16:08:22 UTC,apport information
1729878,2017-11-03 16:08:23 UTC,apport information
1729878,2017-11-03 16:08:26 UTC,apport information
1729878,2017-11-03 16:09:37 UTC,"Fix your bot, guys... it tells me logs are missing and to run apport-collect which just collects the exact same logs ubuntu-bug collected the first time."
1729882,2018-04-02 07:52:36 UTC,Maintainers for apt-xapian-index are Debian QA Group <email address hidden>.
1729882,2017-11-03 16:28:39 UTC,"The attachment ""update-apt-xapian-index-dbus.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1729882,2017-11-07 00:16:57 UTC,"For those interested in applying the patch before this gets fixed, here is how to do this:"
1729887,2017-12-19 18:36:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729887,2017-12-19 19:10:45 UTC,I should mention I'm running gnome-flashback (compiz) as this might have an impact.
1729887,2017-12-20 01:58:25 UTC,"The upstream bug link is here:
https://bugzilla.gnome.org/show_bug.cgi?id=742463"
1729887,2017-12-21 15:52:30 UTC,"I'm a little bit surprised that there are not more reports like mine. This thing or some connected error cuts off my ""workflow"" on a regular basis and, like explained below, often forces me to reboot the computer."
1729887,2017-12-19 19:10:05 UTC,This just started happening to me on 17.10.  The behavior changes with the circumstances.  I've done several tests and see the following reproducible behavior:
1729890,2017-11-03 19:01:14 UTC,Apparently this happens when /tmp does not have exec. Remounting /tmp with exec provides a workaround.
1729898,2017-11-03 20:10:56 UTC,(lp:1645704 might be relevant)
1729900,2020-10-03 04:17:14 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1729900,2020-08-03 05:50:52 UTC,"Can you please tell us what kind of problem you are having, if any?"
1729901,2017-11-03 18:40:21 UTC,apport information
1729901,2020-02-05 17:50:04 UTC,Ubuntu 18.04 (overlay Unity). There is no problem on Ubuntu 18.04 (overlay Gnome).
1729901,2020-02-05 01:37:40 UTC,It sounds like it's being mistaken for Ctrl+A. What version(s) of Ubuntu are exhibiting the problem?
1729901,2020-01-30 22:03:56 UTC,This problem is still exist.
1729901,2017-11-03 18:40:48 UTC,apport information
1729901,2017-11-03 18:40:45 UTC,apport information
1729901,2017-11-03 18:40:42 UTC,apport information
1729901,2017-11-03 18:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1729901,2017-11-03 18:40:40 UTC,apport information
1729901,2017-11-03 18:40:35 UTC,apport information
1729901,2017-11-03 18:40:33 UTC,apport information
1729901,2017-11-03 18:40:31 UTC,apport information
1729901,2017-11-03 18:40:30 UTC,apport information
1729901,2017-11-03 18:40:26 UTC,apport information
1729901,2017-11-03 18:40:24 UTC,apport information
1729901,2017-11-03 18:40:23 UTC,apport information
1729901,2017-11-03 18:40:37 UTC,apport information
1729901,2017-11-03 18:40:38 UTC,apport information
1729904,2019-09-19 11:56:36 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1729909,2018-04-13 18:31:07 UTC,This issue is a duplicate of #1613397.
1729921,2020-06-10 15:00:43 UTC,Another way to reproduce that error (with swift-2.25.0):
1729921,2019-05-10 17:49:20 UTC,"Bhaskar Singhal please share your object-expirer/internal-client pipeline.  I'd like to see how they compare to the documented examples [1, 2]."
1729921,2019-05-07 07:29:09 UTC,Hitting a similar issue (without changing the encryption root secret)
1729921,2019-05-11 06:50:00 UTC,Swift version Rocky
1729925,2017-11-26 18:27:17 UTC,"FYI, 2.4 is the latest version in the code repository but the link to the latest version as a tarball is still the 2.3.1 version."
1729925,2017-11-26 18:27:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729925,2020-05-24 21:13:16 UTC,"The latest upstream version is 2.5.4 and is available in Debian unstable.  Since Ubuntu is regularly syncing from Debian and currently contains 2.5.3, is there a reason to keep this bug open?"
1729926,2017-11-05 17:08:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729926,2020-05-25 18:45:30 UTC,Thanks for taking the time to file this bug!
1729927,2021-02-12 19:57:54 UTC,"Noting that as part of the Consolidate Patron Notes work, bug 1846354, the new Notes interface does refresh the Notes counter (which is now in the tab bar above the main patron area) automatically."
1729927,2021-02-23 14:17:27 UTC,Going to go ahead and mark this as a dupe since it's being addressed elsewhere.
1729929,2019-07-19 21:23:23 UTC,"Hi,"
1729929,2019-09-18 04:17:34 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1729939,2017-11-19 12:43:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729939,2018-03-13 21:31:25 UTC,Any plans for fixing this?
1729941,2018-11-28 14:11:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729962,2019-04-23 15:29:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729962,2019-04-23 15:30:00 UTC,"I'm seeing this on 3.28.1-1, Ubuntu Bionic 18.04.2 LTS."
1729963,2019-04-25 10:59:47 UTC,"It appears the trace has changed slightly, crashes are tracked in a separate report on errors.ubuntu.com: https://errors.ubuntu.com/problem/e0e63ef80dd16f02330b92c6af9e21591b2f47f0"
1729963,2019-07-26 10:20:14 UTC,New report on errors.ubuntu.com: https://errors.ubuntu.com/problem/843d8a8ce4bc8f6301b5fde1ed97d345ef3e2bde
1729963,2018-04-11 07:29:49 UTC,Attaching here the stacktrace from the report on errors.ubuntu.com.
1729963,2019-03-05 16:20:01 UTC,"Of all the crash reports on errors.ubuntu.com since 2019-01-01 (1352 reports), it looks like the last version exhibiting the problem is 68.0.3440.75."
1729963,2018-03-14 02:40:04 UTC,I have definitely experienced it at least once by rebooting while chromium is open.
1729963,2018-04-11 07:33:49 UTC,Bug filed upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=831495
1729963,2018-03-12 19:59:47 UTC,"I can't completely confirm mine was at Chromium app shutdown, but it
probably was, as I also didn't notice it until seeing the crash icon in the
launcher. I usually shutdown a browser app when too tabs have accumulated.
It's the first instance I've noticed on Chromium, which has otherwise been
stable. I use in lieu of FF which is very unstable, and usually crashes
when trying to open a new tab."
1729963,2018-03-12 18:45:02 UTC,"It can happen at application shutdown, this has happened at least twice for me."
1729963,2018-03-12 17:44:49 UTC,"From possible duplicate bug #1755233, the user reported that « Browser did not gracefully exit », which suggests the crash happens at application shutdown."
1729963,2017-11-07 15:24:46 UTC,The stacktrace suggests a DBus connection is disconnected while processing a message:
1729963,2018-03-13 21:19:46 UTC,Duplicate bug #1755054 also strongly suggests the crash happens at shutdown (in that case when rebooting the computer while chromium is running).
1729963,2018-03-12 19:18:21 UTC,"Thanks for the confirmation Tom. Until now I didn't even know when that crash happened, this will be helpful in reproducing the issue and investigating it."
1729968,2017-11-06 14:24:58 UTC,The stacktrace matches https://bugzilla.gnome.org/show_bug.cgi?id=756973 which upstream has marked as duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=733334 which is a segfault when n-m is restarted
1729968,2018-12-12 15:07:30 UTC,"There are no error in 18.10, it seems similar to https://gitlab.gnome.org/GNOME/gnome-control-center/issues/93 which was fixed there"
1729972,2020-07-01 21:15:10 UTC,"There has been no report since 18.10, closing"
1729980,2017-11-28 15:31:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729981,2017-12-03 21:09:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729984,2018-02-17 11:45:35 UTC,"Me too, exactly the same:"
1729984,2018-08-12 18:36:09 UTC,"+1 confirmed, rebooting fixed it. I noticed that in one of the errors that popped up also. I think it was Android Studio or a system error, but it said 'if problems persist, try rebooting your machine'."
1729984,2018-06-06 15:23:22 UTC,"Can confirm a reboot fixed mine as well. Ubuntu 18.04, after installing 'adb'."
1729984,2018-06-01 14:13:32 UTC,I just got the same error. It went away after I rebooted my machine.
1729984,2018-05-17 00:31:38 UTC,Another 'Me Too' here on 17.10. Are there any workarounds for this?
1729984,2018-02-08 16:59:30 UTC,"This affects me on 17.10, but not 16.04."
1729984,2018-05-01 15:55:09 UTC,This persists in 18.04...
1729984,2018-01-04 10:42:40 UTC,I'm experiencing this issue as well when I run adb on a newly installed Ubuntu 17.10 machine:
1729984,2018-01-04 10:40:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729984,2018-05-01 15:57:38 UTC,"It may be to do with an error in the invocation, as after calling instead with a hyphen..."
1729985,2017-11-06 17:18:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729986,2017-11-03 21:54:09 UTC,possibly this upstream bug report - I need access to the error tracker to confirm
1729987,2017-12-14 05:14:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1729997,2017-11-05 20:31:52 UTC,"Tony,"
1729997,2017-11-07 21:08:19 UTC,https://forum.snapcraft.io/t/auto-connect-interfaces-on-wifi-connect/725/12
1729997,2017-11-07 17:12:57 UTC,"Ah, look at that, wifi-connect's network-manager plug isn't connected.  I would've thought we'd be able to get permission for this to autoconnect, even though it's in the public store? Have we asked?"
1730002,2017-11-07 21:03:21 UTC,Confirmed in 3.0.1
1730006,2017-11-06 14:13:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1730006,2017-11-06 14:14:37 UTC,The log has this warning
1730006,2017-11-06 16:41:10 UTC,Yes.
1730006,2018-12-12 15:08:07 UTC,"The issue seems to have been reported upstream as well, see e.g https://gitlab.gnome.org/GNOME/gnome-control-center/issues/18"
1730014,2017-11-04 10:50:06 UTC,"Hi,"
1730018,2017-11-05 02:40:32 UTC,"I got this all working, I think the docs/process just needs a little polish possibly. Let me see if I can come up with a list of suggestions after going through this many times now."
1730018,2017-11-06 13:57:34 UTC,Improving the docs are always needed! It would be great if you could come with suggestions out of your experience getting it up and running.
1730018,2019-09-19 14:46:30 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1730027,2018-03-19 14:07:53 UTC,Duplicate of bug 1022865?
1730027,2018-03-19 21:20:17 UTC,"The other bug report is mostly people complaining of errors with interactive use; mine was not interactive, but instead triggered by the cronjob. There's a chance that they're the same, or related, but it's not obvious to me."
1730032,2017-11-09 12:30:56 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1730032,2018-02-08 09:40:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730036,2017-11-09 09:41:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730039,2018-06-11 12:49:17 UTC,This is also happening to me with Ubuntu 18.04 (bionic):
1730039,2018-07-11 13:26:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730039,2019-09-05 16:10:41 UTC,"I'm still running into this problem on  18.04.2 LTS.  Is there some fix/workaround other than downgrading to an old version of java?  for a variety of other reasons, that's not an option for me."
1730039,2020-09-18 07:51:40 UTC,389-console is gone from the distro since 18.10
1730059,2017-11-16 02:02:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730059,2017-11-17 06:04:44 UTC,"Effects me on a fresh install. ""synaptic --display=:0"" didn't work but ""xhost +local:"" did as suggested in https://askubuntu.com/questions/614387/gksu-gtk-warning-cannot-open-display-0"
1730061,2017-11-04 10:26:32 UTC,"More information...
I use Brother device for printer and scanner download in internet for amd64.
Thank you !"
1730061,2020-01-26 04:17:49 UTC,[Expired for simple-scan (Ubuntu) because there has been no activity for 60 days.]
1730065,2018-02-15 11:34:09 UTC,I'm seeing an issue which I believe is also due to this bug.
1730065,2020-05-28 14:16:39 UTC,assuming it's fixed by now
1730067,2018-01-30 21:51:11 UTC,This issue was fixed in the openstack/python-mistralclient 3.2.0 release.
1730067,2019-05-10 16:40:49 UTC,This issue was fixed in the openstack/python-mistralclient 3.1.5 release.
1730069,2017-11-04 22:34:19 UTC,apport information
1730069,2017-11-04 22:34:17 UTC,apport information
1730069,2017-11-04 22:34:14 UTC,apport information
1730069,2017-11-04 22:34:11 UTC,apport information
1730069,2017-11-04 22:34:24 UTC,apport information
1730069,2017-11-04 18:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730069,2017-11-04 11:49:34 UTC,The package that first caused this problem was linux-image-4.10.0-32-generic (linux-image-4.10.0-33-generic doesnt work either)
1730069,2017-11-04 22:34:20 UTC,apport information
1730069,2017-11-04 22:34:09 UTC,apport information
1730069,2019-10-06 00:04:55 UTC,"The problems on my hardware were fixed, see:"
1730069,2017-11-04 22:34:21 UTC,apport information
1730069,2019-09-07 16:36:39 UTC,A patch was posted that solves my problem:
1730069,2019-04-23 01:02:22 UTC,"I can confirm this bug, on different hardware."
1730069,2019-04-23 00:57:03 UTC,I can confirm this bug on different hardware (a Chromebook Samsung 500C).
1730069,2017-11-16 15:01:29 UTC,"I have reported it at
https://bugzilla.kernel.org/show_bug.cgi?id=197895"
1730069,2017-11-16 15:00:18 UTC,"I have a GA-E350N-WIN8 gigabyte motherboard, after kernel commit 9479c7cebfb568f8b8b424be7f1cac120e9eea95 the amd64 kernel no longer boots (commit ab72a27da4c6c19b0e3d6d7556fdd4afb581c8ac) works."
1730069,2017-11-16 03:32:32 UTC,Huge thanks!
1730069,2017-11-15 21:59:59 UTC,"I have found the broken commit, its 9479c7cebfb568f8b8b424be7f1cac120e9eea95"
1730069,2017-11-12 21:01:57 UTC,"I can do it, but the E-350D is not the fastest CPU out there (I dont have access to any other debian boxes at the moment). It took around 1.5 hours to build the first package and it looks like it will take up to 13 more steps, so it may be quite a few days before I have the broken commit."
1730069,2017-11-11 09:51:21 UTC,"I can build kernel packages for you, but it'll be much faster if you build kernel locally:"
1730069,2017-11-10 23:49:07 UTC,I can confirm that 4.8.0-040800-generic works fine.
1730069,2017-11-04 22:34:23 UTC,apport information
1730069,2017-11-10 08:25:16 UTC,"> On 9 Nov 2017, at 7:04 PM, Patrick Mackinlay <email address hidden> wrote:
>
> Trying the amd64 kernels at
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/
>
> The last 4.8 kernel (linux-
> image-4.8.17-040817-generic_4.8.17-040817.201701090438_amd64.deb) boots
> fine. None of the 4.9 kernels I tried (v4.9.1 and v4.9-rc1) boot.
>
> So it seems that this regression was introduced in 4.9
"
1730069,2017-11-08 03:15:17 UTC,"> On 8 Nov 2017, at 6:53 AM, Patrick Mackinlay <email address hidden> wrote:
>
> All the linux kernels above 4.8 that I have tried have failed, currently
> this includes:
"
1730069,2017-11-07 22:53:06 UTC,"All the linux kernels above 4.8 that I have tried have failed, currently this includes:"
1730069,2017-11-07 08:05:47 UTC,Sorry I missed your first comment. Does it boot with linux-image-4.10.0-30-generic?
1730069,2017-11-06 22:25:08 UTC,I am afraid it doesn't boot with linux-generic-hwe-16.04-edge either.
1730069,2017-11-06 01:53:10 UTC,Please try -edge HWE stack: `sudo apt install linux-generic-hwe-16.04-edge`
1730069,2017-11-04 22:36:46 UTC,"I have run the apport-collect command, obviously this was not executed when running any of the kernels that have this issue, it was running with a working kernel, 4.8.0-58-generic."
1730069,2017-11-04 22:34:33 UTC,apport information
1730069,2017-11-04 22:34:29 UTC,apport information
1730069,2017-11-04 22:34:26 UTC,apport information
1730069,2017-11-09 11:04:56 UTC,Trying the amd64 kernels at
1730069,2019-04-23 01:03:59 UTC,"I can also add that when the kernel is started via kexec instead of via normal hardware boot, the problem does not occur."
1730069,2019-04-23 12:08:32 UTC,I've emailed the maintainers and patch authors here:
1730082,2017-11-04 16:34:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1730086,2017-11-04 23:04:45 UTC,I have performed two more experiments:
1730088,2017-11-05 00:20:55 UTC,"Hello! It's a problem with a voxel, but I can't tell what exactly without inspecting the related except.txt file."
1730088,2017-11-06 03:17:50 UTC,"The issue is with a projectile (I would guess it's related to the aircraft weapon). It's supposed to be a voxel, but there's some issue with it I can't yet tell. But maybe that's enough to find the issue."
1730088,2017-11-05 14:18:54 UTC,"Hi Alex! You're right. Yesterday, in my despair, I forgot to send you the
except. txt. I think the files you need are these. Here I attach it.
Greetings from Argentina."
1730092,2018-12-11 11:44:42 UTC,@Max: could you be a bit more specific as to which packages you reinstalled?
1730092,2017-11-04 18:37:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730092,2018-09-06 04:19:00 UTC,I got it working again on Ubuntu 18.04.1 by using Synaptic to reinstall supporting libraries like otf and m17.
1730092,2017-11-04 18:38:51 UTC,I successfully updated the package after removing vala-mode package (which I was able to reinstall subsequently)
1730099,2019-03-25 06:00:38 UTC,"Which version of SDL are you using? SDL 1.2 or SDL 2.0? If you were using 1.2, could you please try 2.0 instead? Support for SDL 1.2 has been removed now."
1730099,2019-05-25 04:17:28 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1730101,2019-03-25 05:59:20 UTC,"Which version of SDL have you been using here? SDL 1.2 or SDL 2.0? If you were using 1.2, could you please try with 2.0 instead? Support for 1.2 has been removed now."
1730101,2019-05-25 04:17:27 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1730113,2017-11-09 13:00:09 UTC,This change was made by a bot.
1730113,2017-11-09 12:30:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1730125,2017-11-04 23:38:19 UTC,elastic recheck query https://review.openstack.org/517779
1730131,2017-11-05 00:34:26 UTC,brabrabra
1730131,2017-11-05 00:34:47 UTC,hogehoge
1730134,2017-11-05 04:19:38 UTC,Comments
1730139,2017-11-05 00:36:02 UTC,under debugging
1730142,2017-11-05 05:32:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/517800"
1730145,2017-11-05 00:44:48 UTC,I now disagree
1730152,2017-11-07 13:59:09 UTC,The bug exists in ubuntu 16.04. It still exists in the mainstream kernel v4.14-rc6. I haven't tested in kernel v4.14-rc8.
1730152,2017-11-06 21:05:48 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1730152,2018-10-05 06:03:55 UTC,Still no way to fix this?
1730152,2018-01-26 08:28:31 UTC,"@sfc I installed the driver and had it loaded, however the card reader remains unassigned after reboot. Maybe I should wait for some kernel update fixing this issue. Thanks a lot for help."
1730152,2018-01-25 06:11:32 UTC,"@funicorn Yes. Put that dkms.conf in the same ampe_stor directory and use ""dkms add"" to add it. Please refer to https://help.ubuntu.com/community/DKMS and https://github.com/dell/dkms for detailed instructions."
1730152,2018-01-24 11:52:54 UTC,@sfc Could you explain a little more how exactly to use the dkms.conf file? Should I put the file in the same ampe_stor directory?
1730152,2018-11-18 13:06:26 UTC,I suppose this is a duplicate of bug #1270676
1730152,2018-01-24 08:06:17 UTC,"You could try this driver: https://github.com/josch09/ampe_stor. From the code, it seems supporting AU6601, AU6621, and AU6625, but it's not working on my envy 13 ad110tu (AU6625). It can detect the card, and get the capacity, but then many errors will occur and finally the reader dies. Maybe it will work on your device."
1730152,2018-01-23 16:08:45 UTC,Please someone write the driver for this card reader.
1730152,2017-11-08 06:21:21 UTC,"Unless someone writes driver for the card reader, it's not going to work."
1730152,2017-11-07 14:21:03 UTC,OK. I have tested it in the newest mainstream kernel v4.14-rc8. There is nothing changed.
1730152,2018-01-24 08:08:28 UTC,Also see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270676/comments/80 to install it with DKMS.
1730152,2017-11-05 03:30:08 UTC,This change was made by a bot.
1730158,2017-11-05 05:45:09 UTC,"Reviewed:  https://review.openstack.org/517787
Committed: https://git.openstack.org/cgit/openstack-dev/sandbox/commit/?id=b48276bed12337e0f9194ec904f92f95ca67c2a0
Submitter: Zuul
Branch:    master"
1730162,2019-04-17 06:18:16 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
If yes, can you attach the output of ""lspci -nnv"" and ""usb-devices"" to the report.
Thanks"
1730162,2019-06-17 04:17:30 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1730163,2017-11-08 16:01:31 UTC,"The file /etc/update-manager/release-upgrades has ""Prompt=lts"" set, while if you want to upgrade to Zesty, not an LTS, you'll need to have ""Prompt=normal""."
1730168,2017-11-06 14:05:22 UTC,"What's the expected behavior?
The documentation says:"
1730168,2017-11-12 07:29:39 UTC,"Carlos,"
1730168,2017-11-13 13:12:51 UTC,"Hi,"
1730168,2018-01-24 22:31:40 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1455
1730175,2020-10-03 04:17:16 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1730175,2020-08-03 05:51:36 UTC,"Please explain the problem you are/were facing in more detail, and whether it is still happening."
1730175,2020-10-03 12:57:43 UTC,"Now the problem is resolved after I upgraded to Ubuntu 20.04.  The issue
was that after installing any software from Ubuntu Software it used to fail
to open. Thanks for your concern."
1730178,2019-01-16 07:54:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730178,2018-06-04 20:38:17 UTC,Still does not work on clean Ubuntu 16.04.4 LTS amd64 with all updates and empty output of `debsums -s -a -c` (system integrity check passed).
1730180,2019-11-13 15:58:55 UTC,My open rails game is not continue . bug track . please continue the openrails
1730180,2018-12-17 14:41:09 UTC,hola
1730180,2017-11-06 15:41:07 UTC,Pls. attach here file Turkiyem.trk.
1730182,2017-11-07 09:03:36 UTC,no one repeat?
1730182,2017-11-07 09:04:16 UTC,no comment?
1730196,2017-11-05 14:52:08 UTC,"I believe the issue was due to the Polari IRC application. It ultimately froze, while playing the *bell* sound on loop. After restarting the laptop it works fine again, but the application my have issues running for days at  time."
1730196,2017-11-06 00:22:30 UTC,"If that is the case, I propose changing the affecting package to Polari and not Firefox."
1730196,2020-06-11 00:24:19 UTC,"So after 2+ years are there any outstanding issues still?
Can this be closed now or does this bug report still need
re-assigning and investigation?"
1730196,2020-08-10 04:17:34 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1730202,2017-11-05 16:16:19 UTC,This string is sourced from the win condition's Lua script. This can be solved though.
1730202,2019-09-16 08:47:34 UTC,Migrated to https://github.com/widelands/widelands/issues/3221
1730207,2018-08-09 16:10:27 UTC,This issue has been fixed in the master branch of the Meep git repository. Meep is now compatible with all guile versions >= 1.8.
1730207,2018-08-09 17:17:51 UTC,"Thanks for this Chris…I would guess that it means that the meep binary package that one installs with the apt package manager on Ubuntu should just work with no fuss, no bother.  Then the latest improvements can always be updated via “git clone” on the git repository."
1730207,2018-08-30 21:25:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730208,2017-11-21 13:57:18 UTC,"That solves it! Now the snap runs without the GLIBC error. A 'Namespace Gtk not available' error is showed, but its a different issue with building against Gtk that I have to look into."
1730208,2017-11-17 17:38:44 UTC,"Ah, the description implies this happens at build time, but it actually happens at run time. I believe the issue here is that you're building on 17.10, which has a newer libc than Xenial, which is what you run against. Is there a reason you're building on 17.10? If not, you can run `snapcraft cleanbuild`, which will spin up a Xenial lxd container for building, or otherwise run Snapcraft on Xenial."
1730208,2017-11-13 23:15:02 UTC,"Hey Manu, how do you have Snapcraft installed? This sounds like a problem that I believe has been fixed in master, but not yet released. Can you try installing the snap from edge and trying again?"
1730208,2017-12-14 02:27:26 UTC,"Agree with Manu on this issue, the platform that you build your snap on should not matter one bit. The whole point of running a snap is portability. Snapcraft should not even allow you to build on 17.10 without using cleanbuild if this is an issue!"
1730208,2017-11-17 17:17:29 UTC,Installed snapcraft from edge. But the same error is being displayed. Terminal output is attached.
1730209,2017-11-05 16:42:34 UTC,"Fixed this error with this command:
gconftool-2 --recursive-unset /apps/compiz-1 && gconftool-2 --type=list --list-type=string --set /apps/compiz-1/general/screen0/options/active_plungins [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,move,resize,mousepoll,regex,snap,gnomecompat,place,imgpng,vpswitch,animation,wall,workarounds,fade,session,expo,ezoom,unityshell]"
1730220,2017-11-06 17:16:46 UTC,"Yeah, in fact any abstraction (as abstractions/ubuntu-{media-players,email,bittorent-clients}) could be improved with a .d directory."
1730220,2018-02-11 12:07:15 UTC,Ping. Any ideas how could this be organized?
1730220,2018-02-25 13:20:39 UTC,I've no strong opinion about this at the moment.
1730226,2017-11-05 19:28:27 UTC,"Tried changing the grub command line to boot from the other disk of the raid set.  It gave me the same error on that disk, but the one I was using previously was mountable."
1730230,2018-03-16 11:11:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730231,2017-11-07 22:29:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1730231,2018-05-11 17:00:15 UTC,I can't reproduce this issue for MP3s but I can reproduce this issue for PNGs on Files 3.26.3-0ubuntu4 on Ubuntu 18.04. I've reported this upstream: https://gitlab.gnome.org/GNOME/nautilus/issues/415
1730231,2018-05-12 02:29:27 UTC,The correct upstream bug for this is https://gitlab.gnome.org/GNOME/nautilus/issues/117
1730231,2018-05-11 17:00:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730232,2017-12-04 10:51:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730233,2020-08-11 07:24:59 UTC,libindi1:amd64 (1.5.0+r3509~201710280916~ubuntu16.04.1)
1730234,2017-11-05 20:57:35 UTC,Откуда такие странные сведения?
1730234,2017-11-06 11:10:35 UTC,"While OP could have added some source of reference, these data seem indeed flawed."
1730234,2018-09-26 05:08:34 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/402
1730239,2018-05-24 20:17:20 UTC,The column picker options used for copy alerts could serve as an example of how to display copy notes in column pickers. The number of alerts displays in a column with a button available to display those alerts in a popup.
1730241,2018-10-10 00:04:38 UTC,"I just restarted Evolution (but did not reboot my system or make any other changes) and now Evolution is crashing for me in the identical way described here.  I literally just quit Evolution, it was running fine, and restarted it and now it just crashes with the same stacktrace shown above, a null pointer passed to g_ascii_strtoull() (will add it as an attachment) after this error:"
1730241,2017-11-07 21:38:54 UTC,"what's the output of ""glxinfo"" on your machine? it seems there that glGetString() doesn't return what it should"
1730241,2018-10-10 00:30:09 UTC,"Aha, looking at issue #109 then checking journalctl I see:"
1730241,2017-11-07 20:19:26 UTC,I resolved the problem by forcing the GL library to be taken from Mesa.
1730241,2017-11-06 21:58:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1730241,2018-10-10 00:28:19 UTC,Seems like it might be related to this: https://gitlab.gnome.org/GNOME/cogl/issues/1 which similarly was reported here: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/109
1730241,2017-11-07 20:40:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730244,2019-06-06 17:20:51 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that there was an error on your system when trying to update a package on your system due to a lack of free space on your system.  Please resolve this situation manually and try the update again.
1730257,2017-11-07 12:55:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730262,2017-11-06 10:50:19 UTC,"Hello, thank you for the time spent filling this bug report."
1730263,2021-02-09 22:08:16 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11544"
1730263,2019-05-25 04:54:29 UTC,"This is now happening:
In the case of importing a complete portfolio and the personal information contained in the XML is different than the logged in user, display it with default option = 'Replace'."
1730263,2017-11-06 06:53:30 UTC,Forum discussion in which this was discovered: https://mahara.org/interaction/forum/topic.php?id=8077
1730277,2017-11-19 12:01:24 UTC,"I've found that this bug appears only when screens are located one above the other, check out the attached screenshot.
This is also related to a problem with not being able to move windows freely on the second screen, it feels like a screen is divided into 3 panels and you can only move a window from the left panel to the right panel and then back, but you can't move it to the center panel."
1730278,2017-11-06 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730278,2017-11-06 06:19:30 UTC,"The bot was searching for ""linux"" using dpkg-query, but the problem may be related to the Linux kernel. So, I have to stop the bot as it goes to nowhere."
1730278,2017-11-06 20:58:07 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730278,2017-11-07 04:35:48 UTC,"So, I got basically the same error as before with the kernel 4.14-rc8. There is an error on the USB port from my DisplayLink dock station, but the major slowdown part is to find and mount my LVM /home volume (see the full log of journalctl -abl from the attachment):"
1730285,2018-06-22 19:15:43 UTC,I am also having this exact bug.
1730295,2019-01-15 17:57:45 UTC,Fixed in https://review.openstack.org/#/c/629689/
1730301,2017-11-07 03:31:56 UTC,I don't know whether I should fix this bug.
1730305,2017-11-13 03:10:12 UTC,Try v4.11 and v4.12.
1730305,2017-11-27 01:13:01 UTC,Any idea?
1730305,2017-11-13 00:58:16 UTC,Any update?
1730305,2017-11-06 08:29:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1730305,2017-11-21 02:23:42 UTC,Hi.
1730305,2017-11-07 05:23:19 UTC,Update:
1730305,2017-11-27 03:39:39 UTC,Can you confirm that v4.11 works while v4.12 does not?
1730305,2017-11-06 20:43:59 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730305,2017-11-06 18:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730305,2017-11-07 01:49:48 UTC,"Hi Joseph.
I don't have any bootable kernel on the machine since it's fresh installation. Can I install another kernel? If yes, could provide some instructions? Thanks."
1730317,2017-11-06 08:39:34 UTC,"i think the exported *.sql which included data should use the names from creating statement;
e.g.
CREATE TABLE `user` (
  `id` int(11) NOT NULL,
  `name` varchar(20) DEFAULT NULL,
  `lastlogininfo` json DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4"
1730331,2018-08-25 18:03:43 UTC,"For those on Bionic and who recently met the trouble, try down-grading linux-firmware to 1.73 from 1.73.1. Test."
1730331,2018-08-23 06:10:50 UTC,"I have never had problems wit heat or sleep, so I would see this issue completely unrelated."
1730331,2018-08-23 00:26:20 UTC,"I'd made precisely one change to the config on the XPS9370; which was to add deep sleep to the kernel boot parameters for grub, vis."
1730331,2018-08-19 11:18:03 UTC,"For me the firmware also crashes on a

> 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
"
1730331,2018-07-19 10:27:38 UTC,Seen on a Dell XPS 9370 with Bionic
1730331,2018-06-20 13:53:05 UTC,"I'm having still (06/2018, Ubuntu 18.04, latest linux-firmware) the issue with the crashing ath10k_pci firmware, mostly after the laptop goes to suspend mode."
1730331,2018-06-17 23:52:51 UTC,Same issue here:
1730331,2018-06-08 18:27:21 UTC,"If you still have the issue with latest linux kernel and lates linux firmware, please raise the issue to <email address hidden>."
1730331,2018-05-17 14:25:33 UTC,"I face very similar problem, but I have v2.1 hardware of QCA6174 (I assume you do not have QCA6147 neither).
I installed Kubuntu Bionic Beaver (18.04) from fresh."
1730331,2018-03-27 11:52:47 UTC,"Created attachment 1413693
dmesg output, lspci -vv, modinfo ath10k_pci"
1730331,2017-11-26 04:25:46 UTC,"Before pulling in the new firmware, I tried the upstream kernel per the wiki instructions I found in the Ubuntu wiki. The same problem existed there. Now, I am running the artful kernel with the bionic firmware files that I manually copied over as indicated above."
1730331,2017-11-26 04:23:56 UTC,"To be clear, I did this:"
1730331,2017-11-26 04:17:01 UTC,The updated firmware used in the bionic branch of the linux-firmware packages git repo seems to fix this problem entirely for me.
1730331,2017-11-14 10:07:04 UTC,Here is another confirmation of this bug:
1730331,2017-11-06 09:30:15 UTC,This change was made by a bot.
1730331,2017-11-06 09:18:11 UTC,"Since LP wrapped up the kernel messages above, here is the full kernel.log."
1730331,2018-06-08 09:59:11 UTC,Issue is present on Fedora 28 too.
1730331,2017-11-28 02:36:24 UTC,"I tried what Wren tried, but this did not fix the problem for me.  I replaced the entire QCA6147 directory, not just hw3.0.  Still no luck."
1730331,2018-08-25 18:29:32 UTC,"PS: kernel 4.15.0-33 will not work with the downgraded linux-firmware, but 4.15.0-32 and earlier will."
1730331,2018-12-19 22:41:25 UTC,"Just wanted to add a note here. I had noticed this only happened on my home network, and nowhere else."
1730331,2019-03-01 11:46:34 UTC,"Well, Fedora 29 here:"
1730331,2019-02-24 04:08:25 UTC,"linux-firmware-20190213-93.git710963fe.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report."
1730331,2019-02-19 14:02:33 UTC,"linux-firmware-20190213-93.git710963fe.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report."
1730331,2019-02-15 02:57:08 UTC,"linux-firmware-20190213-93.git710963fe.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-42cbff0fd6"
1730331,2019-02-15 01:31:09 UTC,"linux-firmware-20190213-93.git710963fe.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-f27089e66c"
1730331,2019-02-14 12:26:42 UTC,linux-firmware-20190213-93.git710963fe.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f27089e66c
1730331,2019-02-14 12:26:30 UTC,linux-firmware-20190213-93.git710963fe.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-42cbff0fd6
1730331,2019-02-14 12:22:31 UTC,The inux-firmware-20190213-93.git710963fe has a new firmware for QCA6174 so please test
1730331,2019-01-30 17:25:09 UTC,"> For the record, anyone knows how to recover the wifi driver without rebooting? I've tried reinserting the module without luck. Can you advice?
"
1730331,2019-03-01 11:51:37 UTC,Forgot to add that this is with the latest firmware from this thread: linux-firmware-20190213-93.git710963fe.fc29.noarch.
1730331,2019-01-26 21:01:11 UTC,"I will update this. Problem is back. After a while of not having any issues, they're back now with the wifi card from the other lenovo laptop:"
1730331,2019-01-01 05:44:02 UTC,"Same, XPS 15 9575 running Fedora 29
linux-firmware-20181219-89.git0f22c852.fc28.src.rpm"
1730331,2018-12-31 09:38:52 UTC,"Same here on Dell XPS 13 9370 running Fedora 29. The solution from the Arch Linux Forums[1] seems to help, i.e. running:"
1730331,2018-12-20 05:00:35 UTC,There's updated ath10k firmwares in linux-firmware-20181219-89.git0f22c852.fc28
1730331,2018-09-04 21:24:48 UTC,running firmware 1.173 the problem persists.
1730331,2018-12-11 16:37:50 UTC,I'm also seeing this occur on 18.10. These are some logs in my `/var/log/syslog` around the time of the crash:
1730331,2018-12-03 13:29:09 UTC,See also Bug #1627474
1730331,2018-11-23 16:05:07 UTC,same here: dell xps 9575
1730331,2018-10-24 13:57:31 UTC,I am also facing the same issue. I see the firmware crashed logs and the computer hangs around that time. I see this while working on the laptop i.e I don't do suspend or resume.
1730331,2018-10-04 19:49:45 UTC,I am having the same issue on a Dell XPS 9560.
1730331,2019-01-09 18:49:44 UTC,"Hi all, it's worth to mention that for me the problem is gone after a colleague, which had the same laptopt model as they are bought in batches by the company I work at, quit the job and before he returns the laptop I asked if we could switch the wifi card."
1730331,2018-09-22 05:24:34 UTC,Comment from original bug reporter:
1730331,2019-03-01 20:06:56 UTC,I am seeing this occur on 16.04 and that too only on my home network. I am using a D-Link DIR-150M router. Hope this helps in solving this bug.
1730331,2019-04-07 19:03:46 UTC,Apparently linux-firmware-20190213-93.git710963fe.fc28.noarch have a problem with Acer Swift 7:
1730331,2018-09-03 08:41:43 UTC,The deep sleep kernel command-line parameter had no discernible effect.
1730331,2019-04-01 20:43:42 UTC,"I'm having a different behaviour, problem persist but at least I don't have to reboot the system:"
1730331,2020-01-06 04:19:14 UTC,"I'm having the same problem with my LENOVO Z51-70 running openSUSE Tumbleweed, Kernel: 5.3.12."
1730331,2019-10-02 17:44:09 UTC,On Ubuntu 18.04 I'm having issues such connection drop/resets with USB device TL-WN822N-v1.1 - Atheros AR-9170 firmware
1730331,2018-09-21 19:37:08 UTC,"I'm experiencing the same thing on Dell XPS 15 9560 with:
kernel-4.18.8-200.fc28.x86_64
linux-firmware-20180815-86.gitf1b95fe5.fc28.noarch"
1730331,2019-08-27 17:34:46 UTC,"This problem happens for me, with newest firmware, newest kernel, as of today - but turns out only in the following situation:"
1730331,2019-08-07 03:26:33 UTC,Can we please re-open this bug? Because it's back!
1730331,2019-04-10 08:36:56 UTC,"I have had some success (3 suspends now and not a crash) by using a newer version of the firmware from upstream, specifically this version: https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/4.4.1.c2/firmware-6.bin_RM.4.4.1.c2-00057-QCARMSWP-1"
1730331,2019-08-28 02:01:27 UTC,"@mangoo-wpkg, that seems like valuable information upstream. Does anyone know the procedure to get it upstream, please?"
1730331,2019-08-07 03:23:47 UTC,"Created attachment 1601215
Fedora 30 ath10k firmware crash: `journalctl -b -1` for the relevant boot"
1730335,2019-12-10 01:49:07 UTC,"Change abandoned by wanghao (<email address hidden>) on branch: master
Review: https://review.opendev.org/517901
Reason: Since there isn't update for a long time, will abandon this. Please feel free to restore it if someone still work on this."
1730335,2017-11-15 03:58:05 UTC,"Thanks for opening this bug. It's a very interesting question. I'm just trying to answer it from my PoV. The message TTL is only to make sure the message could be lived until it's consumed by a client. So that's said once it's processed by a client, message TTL is not necessary to be kept as the original value. But I totally understand your point here. I will think about this and comparing the behaviours on other messaging services. Will revisit this bug soon. Thanks."
1730335,2017-11-13 06:46:25 UTC,"Change abandoned by yangzhenyu (<email address hidden>) on branch: master
Review: https://review.openstack.org/517901"
1730335,2017-11-06 09:48:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/517901"
1730335,2017-11-13 06:56:23 UTC,"But this ttl for each message may not be the same, only get a message from backend and then modify it, so there is a considerable performance consumption, so give up here to modify."
1730336,2017-11-06 10:38:28 UTC,"Hi,"
1730374,2018-03-30 11:13:42 UTC,"I no longer am using the motherboard, CPU and RAM that this happened on."
1730374,2017-12-29 21:18:04 UTC,It happened again.
1730374,2017-12-29 21:30:06 UTC,This change was made by a bot.
1730374,2017-12-13 11:59:13 UTC,It's likely that this was either fixed upstream or the root cause is from a patch that was put on the 4.13 kernels that the 4.14 kernels don't have.
1730374,2017-11-06 20:56:57 UTC,It doesn't appear the patch mentioned ever landed in mainline.
1730374,2017-11-28 11:29:57 UTC,I was unable to reproduce this on 4.13 until Nov 23 when it happened again.
1730374,2017-11-10 11:42:13 UTC,Eventually I'll have time to test the upstream kernel.
1730374,2017-11-10 11:27:25 UTC,I'd love to have time to work on this kernel bug but I have fires all over the place with 17.10.
1730374,2017-11-06 12:30:08 UTC,This change was made by a bot.
1730374,2017-11-28 11:43:45 UTC,"Installation of 4.14.2
https://gist.github.com/mettacrawler/7d60c8f51a19b506ea1cb575c2ed4032"
1730378,2017-11-06 21:53:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1730378,2017-11-07 11:19:34 UTC,"As requested, below you will find link to upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=790012"
1730386,2017-11-06 21:00:15 UTC,"Will do, and will report."
1730386,2017-11-21 16:58:01 UTC,"Happened twice in the last few days, adding the tag and changing to ""Confirmed"", as requested."
1730386,2017-11-06 13:30:08 UTC,This change was made by a bot.
1730386,2017-11-06 13:23:27 UTC,Here's what the syslog says when it hangs.
1730386,2017-11-06 20:49:39 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730395,2017-11-06 13:47:11 UTC,"currently install python-ibus from trusy-update will solve the problem. i download one from https://launchpad.net/ubuntu/trusty/amd64/python-ibus/1.5.5-1ubuntu3.2, and install the deb with dpkg, and sunpinyin setup window will show. but i think ubuntu 17.10 should include this package by default."
1730395,2017-11-09 09:32:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730395,2017-11-28 16:26:39 UTC,"@walterclozet I wish so, but on Ubuntu 17.10, I just got
<code>
$ sudo apt install python-ibus
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package python-ibus
</code>"
1730395,2017-11-29 02:33:09 UTC,"@KANGOD install python-ibus from trusy-update will solve the problem. i download one from https://launchpad.net/ubuntu/trusty/amd64/python-ibus/1.5.5-1ubuntu3.2, and install the deb with dpkg -i"
1730404,2019-04-22 03:02:51 UTC,"Hello Anton,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
Thanks."
1730404,2019-06-21 04:17:31 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1730410,2018-10-10 15:38:41 UTC,"This looks more like a feature of the window manager, rather than application-specific bugs."
1730410,2018-10-27 17:59:50 UTC,Thank you Oliver. Your advice has helped me.
1730410,2018-10-27 11:11:49 UTC,"This is indeed a mutter ""feature"".  Use 'gsettings set org.gnome.mutter auto-maximize false' to turn it off."
1730410,2018-10-10 15:39:39 UTC,(I added a mutter source package task to reflect this)
1730410,2018-10-05 21:14:23 UTC,"Almost all applications (Firefox, Nautilus, Google Chrome, PyCharm, Skype, Calendar and other) opens in maximized size if it window size was larger than some value (more than about 80% of display width and height) when application was closed."
1730410,2020-01-16 08:11:32 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1730410,2018-06-08 07:23:33 UTC,"Happens to me, too, but with all windows, not just Firefox. Ubuntu 18.4. Didn't happen with 17.4."
1730410,2017-11-10 12:56:19 UTC,Same problem here.
1730410,2017-11-20 14:57:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730410,2018-08-16 03:30:54 UTC,"Ubuntu 18.04, latest Firefox as of today, always opens up maximized. For what it's worth, it does not happen with any other apps *with the exception* of Chromium and Chrome, which both open maximized. (Intel Graphics)."
1730410,2018-05-08 16:52:05 UTC,"Ubuntu 18.04, Firefox 59.02 64 bit has the same problem. Nvidia driver 390.48 in use."
1730410,2018-06-07 20:04:12 UTC,"If the Firefox windows is larger than some limit when closed, it will open in full-screen mode next time it is opened. If smaller than this limit, the size at close will be used as the size when reopened."
1730410,2017-11-20 14:58:44 UTC,Same thing occurs for me using Ubuntu 17.10 with xorg
1730411,2018-05-16 00:30:11 UTC,That upstream bug seems to suggest there's no such problem in openbox?
1730411,2018-05-16 00:47:09 UTC,"In any case, this ideally is a WM issue, reading that upstream report."
1730411,2018-05-16 17:11:05 UTC,lxde also uses openbox and you can put different wallpapers for each monitor. When you change the wallpaper it only changes the one in which you have done the right click with the mouse.
1730411,2018-08-17 21:48:26 UTC,"I actually apparently didn't read that bug correctly. The issue is not the window manager at all. It's pcmanfm-qt. Just as with LXDE, the desktop (read: wallpapers) are managed by pcmanfm (see the --desktop switch, which we run by default)."
1730411,2018-08-17 22:01:08 UTC,"Too bad HydraPaper is GTK. We probably need something lighter. feh can certainly handle this but it's a little cludgy (CLI only) but maybe we can make a little script. There's a bunch of other options to explore, too:
https://wiki.archlinux.org/index.php/List_of_applications#Wallpaper_setters"
1730411,2018-08-21 12:43:47 UTC,"I tried all the wallpaper setter that are in ubuntu repositories: Feh, Nitrogen and Variety. Nitrogen and Feh are able to manage the 2 monitors w/o problems and variety runs in backround continuously changing wallpaper, and I couldn't find out how to manage multiple monitors.
The downside is that all of them required to kill ""pcmanfm-qt --desktop""."
1730411,2018-08-21 13:42:24 UTC,"Keep looking for a good workaround, Hans. Perhaps the cron job that checks to see if the wallpaper has changed and then uses imagemagick to make it the right size for the ""one monitor"" will solve the issue, but it's not a good permanent fix. Looking outside of pcmanfm-qt has ultimately led us right back to it. Because of that, I'm going to set the importance to wishlist."
1730411,2019-04-18 16:57:40 UTC,"I forgot adding the current workaround which is here:
https://code.launchpad.net/~hmollercl/stitchwp/+git/stitchwp"
1730411,2020-10-11 00:31:41 UTC,Solved with LXQt 0.15 in lubuntu 20.10
1730411,2018-06-07 13:43:00 UTC,"Apparently this issue also happens in gnome (I haven't used gnome since 2000 and never in 2 monitor environment). In a youtube video they recommend to use hydra-paper https://github.com/GabMus/HydraPaper/ to ""create"" the wallpaper merging the 2 images in one and use this as wallpaper."
1730417,2018-10-01 14:39:28 UTC,"Changed this to wishlist, but then realized that sylvain had set it to High."
1730417,2017-11-06 15:22:16 UTC,"The penultimate item listed isn't so much a matter of organization as a different bug where the UI is displaying tests that were normally run silently in the past and not exposed in the UI.  The ""Test Selection"" list is now listing all jobs, rather than just the jobs explicitly described in the test plan .pxu file."
1730428,2017-11-09 12:29:49 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1730444,2018-01-09 19:07:33 UTC,This bug was fixed in the package linux-azure - 4.13.0-1005.7
1730446,2017-11-06 17:00:10 UTC,This change was made by a bot.
1730446,2017-11-06 20:47:56 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1730446,2018-07-24 09:31:35 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1730455,2018-10-13 13:24:59 UTC,"Didn't test thoroughly. Worked fine with a simple test configuration. When the directory/folder contains more folders in multiple levels (ie 3-4 folders the one inside the other), with long names, fails as usual..."
1730455,2018-10-10 20:05:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730455,2018-10-12 09:48:46 UTC,"Seems that adding the version=3.0 argument mounting the share via cifs, solves the problem..."
1730456,2019-12-18 22:49:35 UTC,I am using MAAS version: 2.6.1 (7832-g17912cdc9-0ubuntu1~18.04.1) and I have the same issue.
1730456,2017-11-07 18:36:58 UTC,Can you provide 3 things:
1730456,2019-10-14 07:17:13 UTC,FWIW This is still an issue in the following environment
1730456,2019-09-19 14:53:24 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1730456,2017-11-08 15:53:09 UTC,"for item 3, attached are the cloud-init logs from the node during deployment (thanks for the pointer to /tmp/block-reboot)."
1730456,2017-11-08 15:50:40 UTC,"1: Machine event logs from a failed commissioning run:
- {created: 'Tue, 07 Nov. 2017 16:09:02', description: Incorrect password.  Check
    BMC configuration and try again., hostname: first-cod, id: 64723, level: WARNING,
  node: 8bf4sg, type: Failed to query node's BMC}
- {created: 'Tue, 07 Nov. 2017 16:08:42', description: From 'Commissioning' to 'Failed
    commissioning', hostname: first-cod, id: 64720, level: INFO, node: 8bf4sg, type: Node
    changed status}
- {created: 'Tue, 07 Nov. 2017 21:08:41', description: '''cloudinit'' running modules
    for config', hostname: first-cod, id: 64719, level: ERROR, node: 8bf4sg, type: Node
    commissioning failure}
- {created: 'Tue, 07 Nov. 2017 16:07:47', description: commissioning, hostname: first-cod,
  id: 64712, level: INFO, node: 8bf4sg, type: PXE Request}
- {created: 'Tue, 07 Nov. 2017 16:07:11', description: '', hostname: first-cod, id: 64706,
  level: INFO, node: 8bf4sg, type: Node powered on}
- {created: 'Tue, 07 Nov. 2017 16:07:06', description: '', hostname: first-cod, id: 64705,
  level: INFO, node: 8bf4sg, type: Powering node on}
- {created: 'Tue, 07 Nov. 2017 16:07:06', description: (bladernr), hostname: first-cod,
  id: 64704, level: INFO, node: 8bf4sg, type: User starting node commissioning}"
1730456,2017-11-06 23:33:39 UTC,"To be sure, I've recreated this with the following steps:"
1730456,2019-12-18 22:47:56 UTC,Is there any workaround for this issue?
1730456,2017-11-06 22:07:38 UTC,I believe the issue which is causing MAAS to mark teh machine as failed commissioning is the following:
1730456,2017-11-06 20:26:57 UTC,"Also, I AM able to reach that IP from the node itself... I re-ran this after sshing into the node once the commissioning failed: (Note, I left the keys intact as this is a test environment and security is not important, it can be completely torn down and rebuilt (and is periodically)."
1730456,2017-11-06 20:24:27 UTC,/proc/cmdline:
1730456,2017-11-06 18:04:01 UTC,here's rsyslog specifically from the node
1730456,2017-11-06 17:22:38 UTC,maas logs from the maas server:
1730456,2017-11-06 17:20:30 UTC,here are the logs from the node
1730456,2017-11-06 17:14:53 UTC,"I did notice the following in the cloud-init log, but that may be a red herring:"
1730456,2017-11-06 17:08:15 UTC,"That's a strange error, can you please attach:"
1730456,2017-11-06 22:34:54 UTC,"Yes, I was just investigating that myself and hadn't had time to update the bug yet."
1730460,2020-09-11 15:51:12 UTC,This bug was fixed in the package mutter - 3.37.91-1ubuntu1
1730460,2020-07-03 09:10:28 UTC,:O
1730460,2019-05-06 01:34:11 UTC,I would usually recommend keeping /unused/ gnome-shell tasks so that other users can find the bug more easily. Then remove the task at the end.
1730460,2019-03-19 10:28:46 UTC,"multi-monitor FPS bug for xorg, discussion moved to ---> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832"
1730460,2019-03-19 02:17:16 UTC,"dreamcat4,"
1730460,2019-03-18 13:48:13 UTC,"multiple monitors on xorg
============================="
1730460,2018-01-25 09:48:07 UTC,"Luis,"
1730460,2018-01-25 12:07:52 UTC,Roger that Daniel. I can confirm it doesn't happen on X.
1730460,2018-01-25 08:45:33 UTC,"Luis,"
1730460,2018-01-19 10:27:13 UTC,"This was happening on gnome-shell, not unity. The report says unity I gather because the crashes got so bad I had to switch back."
1730460,2018-01-19 09:33:44 UTC,"Luis, you say ""Ubuntu session (wayland)"" but the bug report says ""CurrentDesktop: Unity:Unity7:ubuntu"""
1730460,2017-11-06 21:43:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1730460,2018-01-29 02:25:21 UTC,"Alright then, let's consider https://gitlab.gnome.org/GNOME/mutter/issues/3 as the upstream bug here. Unfortunately we can't link to gitlab bugs properly from Launchpad yet."
1730463,2017-11-09 12:29:17 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1730463,2017-11-09 12:30:14 UTC,This change was made by a bot.
1730469,2017-11-08 13:39:51 UTC,"Update : the issue looks solved.
I reinstalled all packets containing gtk unity x11, then all xorg packets, and those latters seem to have fixed it."
1730469,2017-11-07 10:49:16 UTC,"From the logs linked, what I saw :"
1730469,2017-11-06 23:42:12 UTC,- a hung lightdm login
1730469,2017-11-06 23:41:37 UTC,"Adding lightdm and x logs after :
- a no graphics successful login session,"
1730469,2017-11-07 01:12:14 UTC,A few updates :
1730471,2017-11-06 18:14:25 UTC,"ok.. there is already a query for this and error 143.
https://bugs.launchpad.net/openstack-gate/+bug/1686542"
1730482,2017-11-06 19:16:32 UTC,"Review in progress for https://review.opencontrail.org/37222
Submitter: Senthilnathan Murugappan (<email address hidden>)"
1730482,2017-11-08 05:51:45 UTC,"Reviewed:  https://review.opencontrail.org/37222
Committed: http://github.com/Juniper/contrail-fabric-utils/commit/ada5754b3465116313487bd131be93d2ba30a9b4
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1730486,2018-04-07 17:47:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730488,2017-11-07 13:02:56 UTC,Update:
1730494,2018-08-19 15:10:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730494,2018-08-31 08:35:30 UTC,"Bug still present when upgrading from Ubuntu 16.04 LTS to 18.04 LTS, package is 0.6.0-0ubuntu11."
1730494,2018-12-05 12:17:09 UTC,this bug is fixed with https://github.com/thjaeger/easystroke/commit/d14b2740bf3b0ec867d7a0abe4e1f64fb6687aba which is in git master
1730494,2019-09-16 20:16:00 UTC,Can we hope for a new maintainer of this awesome project ?
1730502,2018-04-25 06:39:55 UTC,"problem does NOT occur on a different hardware:
corrado@corrado-HP-p7-bb-beta:~$ apt policy gstreamer1.0-vaapi
gstreamer1.0-vaapi:
  Installed: 1.14.0-1
  Candidate: 1.14.0-1
  Version table:
 *** 1.14.0-1 500
        500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status
corrado@corrado-HP-p7-bb-beta:~$ inxi -SCGx
System:    Host: corrado-HP-p7-bb-beta Kernel: 4.15.0-20-generic x86_64
           bits: 64 gcc: 7.3.0
           Desktop: Gnome 3.28.1 (Gtk 3.22.30-1ubuntu1)
           Distro: Ubuntu 18.04 LTS
CPU:       Dual core Intel Core i5-4210U (-MT-MCP-)
           arch: Haswell rev.1 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9578
           clock speeds: max: 2700 MHz 1: 1049 MHz 2: 1213 MHz 3: 1427 MHz
           4: 1400 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 ) driver: i915
           Resolution: 1366x768@60.00hz
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile
           version: 4.5 Mesa 18.0.0-rc5 Direct Render: Yes
corrado@corrado-HP-p7-bb-beta:~$"
1730502,2018-02-20 17:57:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730502,2018-02-20 18:01:27 UTC,"Same problem on Ubuntu 18.04. This bug seems the same as my bug
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248"
1730502,2018-11-06 18:16:46 UTC,"In addition to simply not getting any thumbnails, I saw very high CPU and RAM use by tumblerd after using Thunar to open a directory with lots of videos in it. Checking the journal, I also saw a bunch of messages saying ""kernel: i915 0000:00:02.0: Resetting vcs0 after gpu hang"". Uninstalling this package enabled thumbnail generation again, and I no longer see either of these other two issues."
1730502,2019-05-09 06:38:41 UTC,gstreamer1.0-vaapi 1.16.0-1ubuntu1 does not fix the problem
1730504,2017-11-15 10:53:20 UTC,You installed an up-to-date plugin?
1730504,2017-11-15 19:53:03 UTC,scanimage -L
1730504,2017-11-17 15:31:40 UTC,"Hi,
The Ubuntu 17.10 support has been planned in the 3.17.11 release in the month of November 2017 and it will address this issue.
Can you please check and update whether the hpaio.so files are available in the /usr/lib/sane path?"
1730504,2017-11-17 23:04:36 UTC,"> The printer is connected to the network with an ethernet cable and is reachable.
> I don't see what AirPrint has to do with the problem?
"
1730504,2017-11-22 00:16:30 UTC,Hello Jan.
1730504,2017-11-23 21:31:03 UTC,"Hello friendly helpers,"
1730507,2017-11-07 04:43:14 UTC,"in the hooks, we render the check_rabbit.py as '{}/check_rabbitmq.py --user {} --password {} --vhost {}'.format(NAGIOS_PLUGINS, user, password, vhost)"
1730507,2017-11-07 08:04:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/518276"
1730507,2020-09-15 17:18:02 UTC,"Reviewed:  https://review.opendev.org/518276
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=5558e21ea80b425cf154644d5f9e9bcf9bde32de
Submitter: Zuul
Branch:    master"
1730510,2018-01-25 09:00:52 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1825
1730511,2017-11-08 23:48:52 UTC,Please don't fork swift to implement a feature you need! Join in and help us all. :-)
1730511,2017-11-06 23:24:47 UTC,"no such api exists, not much has changed, same old tricks still work [1]"
1730511,2017-11-07 15:46:30 UTC,"Clay, thank you for this information.  Sorry about having to submit a bug ticket.  I could not pose the question."
1730513,2017-11-07 11:15:26 UTC,Artful test build restores Korganiser reminders.
1730513,2017-11-07 17:29:52 UTC,the fix in the test build for Artful worked for me.
1730513,2017-11-22 02:51:55 UTC,This bug was fixed in the package akonadi - 4:17.04.3-0ubuntu3
1730513,2018-04-02 21:11:35 UTC,"Was this ever going to get pulled into Artful? ""Reminders don't work at all"" seems like a big thing to just sit with an available fix for 5 months now"
1730513,2019-08-16 06:07:37 UTC,notifications do not work!!!!!!!!!!!
1730513,2019-11-23 10:26:17 UTC,a piece of shit
1730516,2017-11-06 22:13:25 UTC,This is on Ubuntu Xenial
1730517,2017-11-06 22:13:29 UTC,This is on Ubuntu Xenial
1730517,2017-12-16 15:50:38 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1730520,2017-11-09 12:29:03 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1730525,2018-05-22 13:36:39 UTC,I'm hitting this in 2.3.3:
1730525,2018-10-17 14:18:24 UTC,"Hello, I'm facing the same issue when deploying any node with 14.04 LTS within MAAS version: 2.3.5."
1730525,2018-04-11 13:03:09 UTC,To reproduce:
1730525,2018-06-21 17:06:10 UTC,Can this be backported to 2.3?
1730536,2017-11-12 13:37:31 UTC,This should be easy to fix with something very similar to https://gitlab.com/apparmor/apparmor/merge_requests/7. While I'm at it I'll check that google-chrome-stable works too.
1730536,2017-11-12 13:54:41 UTC,https://gitlab.com/apparmor/apparmor/merge_requests/9 fixes this bug on my Debian sid test VM.
1730536,2017-11-13 19:13:17 UTC,"I can confirm that the changes from that merge request, when manually applied on my system, fix the problem. Thanks!"
1730536,2018-03-20 20:29:24 UTC,This bug was fixed in the package apparmor - 2.12-4ubuntu1
1730536,2018-04-22 11:34:17 UTC,Fixed in AppArmor 2.12
1730538,2017-11-07 12:44:50 UTC,s/programmatic/problematic/
1730538,2017-11-07 00:41:26 UTC,"You might be able to talk to barbican with several different URLs, e.g. 127.0.0.1, localhost, <hostname>, etc. so including one of those in the secret_ref is not only unnecessary but it probably also programmatic unless you are dynamically changing the secret_ref based on how the client addressed Barbican... which would have other issues... so just avoid all that and trim down to using only the ID."
1730542,2017-11-07 01:54:41 UTC,"WHen kept the contrail package on ansible node rather than target node, faced below issue. After installing docker-py in master node, installation went through."
1730542,2018-10-23 02:56:24 UTC,Openshift customers are in 5.0 and above. The solution is well tracked in Sanity in 5.0 and above.
1730542,2017-11-08 06:54:51 UTC,Can you reproduce this issue? Need to check sshd config.
1730549,2017-11-07 02:19:08 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/518198"
1730549,2017-11-07 03:18:03 UTC,You should probably add details about what you are tring to do here and maybe also attach related Error Log.
1730549,2017-11-07 06:51:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518250"
1730549,2017-11-07 06:54:15 UTC,"Change abandoned by yangweiwei (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/518198"
1730549,2019-10-07 10:58:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686997"
1730549,2019-10-07 10:58:40 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/518250
Reason: This doesn't apply cleanly any more so I'm abandoning. Please re-open if you think this is still an issue"
1730551,2017-11-08 07:39:18 UTC,Sorry for the delay...
1730551,2017-11-08 07:40:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730559,2018-02-16 18:44:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730597,2017-11-07 07:31:07 UTC,I did not find any comment or document that tell me providing groups should be escaped from rule set.
1730597,2017-11-07 07:32:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/518269"
1730597,2018-02-05 19:23:19 UTC,"Reviewed:  https://review.openstack.org/518269
Committed: https://git.openstack.org/cgit/openstack/group-based-policy/commit/?id=b3a5b46df9d3fd1773c2783193798975063e8480
Submitter: Zuul
Branch:    master"
1730603,2020-06-23 09:08:44 UTC,"I'm not sure how/where do you want to mkv files to be ""recognized"" but mkv is among the file extensions that assoicated with video files by default.
Clicking the ""Default"" button in Settings/Search types pane should make mkv treated as a video file in the search file type groups and results."
1730606,2018-07-19 14:49:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730606,2018-01-24 21:39:15 UTC,I run the attached workaround script every 15 minutes from cron.
1730607,2017-11-21 16:37:11 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730607,2017-11-21 03:31:38 UTC,apport information
1730607,2017-11-21 03:31:36 UTC,apport information
1730607,2017-11-21 03:31:34 UTC,apport information
1730607,2017-11-21 03:31:33 UTC,apport information
1730607,2017-11-21 03:31:31 UTC,apport information
1730607,2017-11-21 03:31:30 UTC,apport information
1730607,2017-11-21 03:31:29 UTC,apport information
1730607,2017-11-21 03:31:27 UTC,apport information
1730607,2017-11-21 03:31:26 UTC,apport information
1730607,2017-11-21 03:30:39 UTC,Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-101-generic x86_64) still have a problem.
1730607,2017-11-16 22:21:27 UTC,"I'm also working a bisect for trusty in that other bug, so the link to the kernel you should test is:"
1730607,2017-11-07 10:04:35 UTC,apport information
1730607,2017-11-07 10:04:43 UTC,apport information
1730607,2017-11-07 08:42:57 UTC,https://ask.fedoraproject.org/en/question/112944/receiving-inputoutput-error-when-trying-to-mount-windows-share-in-fedora-26/
1730607,2017-11-07 08:46:28 UTC,https://www.linuxquestions.org/questions/linux-networking-3/cifs-mount-error-5-%3D-input-output-error-but-smbfs-works-456897/page3.html#post5772016
1730607,2017-11-07 21:30:08 UTC,This may be a duplicate of bug 1729337.  Can you try the test kernel I posted in that bug and see if it resolves your issue?
1730607,2017-11-07 10:04:26 UTC,apport information
1730607,2017-11-07 10:04:27 UTC,apport information
1730607,2017-11-07 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730607,2017-11-07 10:04:32 UTC,apport information
1730607,2017-11-07 10:04:33 UTC,apport information
1730607,2017-11-07 10:04:38 UTC,apport information
1730607,2017-11-07 10:04:41 UTC,apport information
1730607,2017-11-07 10:04:29 UTC,apport information
1730612,2020-10-24 00:01:23 UTC,"This is still an issue on Ubuntu 20.10, while the GNOME Shell remote-desktop / screencast support on Wayland has been enabled for Fedora and other distributions for some time now."
1730612,2021-02-21 01:26:34 UTC,"@jik, I think that you need the package gnome-remote-desktop, this has a MIR request in bug 1802614. And then another package will need to recommend it to have it installed by default, you can follow this on the Trello board here https://trello.com/c/NnUq5bHv/15-mir-gnome-remote-desktop-and-seed-recommend-it"
1730612,2021-02-21 01:13:04 UTC,"Even with that version of mutter installed I still don't see screen sharing as an option under sharing in the settings app when logged in under Wayland. Are there other packages that need to be updated before screen sharing will be available in Wayland sessions, and are there open bug tickets for those?"
1730612,2021-02-19 23:12:23 UTC,This bug was fixed in the package mutter - 3.38.3-2ubuntu1
1730612,2020-04-30 03:06:33 UTC,"Prerequisites: bug 1802533, bug 1802614"
1730612,2020-03-26 17:26:56 UTC,Link in comment #3 also shows an upstream pipewire master
1730612,2020-03-25 11:55:50 UTC,"No, pipewire is not in main. That link in comment #3 shows it is in Universe."
1730612,2020-03-25 11:38:17 UTC,"With that being true, we just need mutter built with the correct flag"
1730612,2020-03-23 01:36:47 UTC,"Not sure, but it looks like the issue in comment #1 is solved:"
1730612,2020-03-20 13:39:59 UTC,"Pipewire is packaged now, can we get it enabled?"
1730612,2017-11-07 14:33:27 UTC,We can't enable that feature until after pipewire is packaged and promoted to main.
1730618,2017-11-07 12:39:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518322"
1730618,2017-11-15 09:16:12 UTC,"ironicclient also affected, any api request may hung forever when API is not available
$ date; ironic --ironic-url http://5.2.3.4 node-list
Wed Nov 15 09:14:00 UTC 2017
The ""ironic"" CLI is deprecated and will be removed in the S* release. Please use the ""openstack baremetal"" CLI instead.
^C... terminating ironic client
$ date
Wed Nov 15 09:15:50 UTC 2017
$"
1730618,2017-11-15 12:17:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520056"
1730618,2018-01-24 09:10:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/537311"
1730618,2018-07-11 01:49:44 UTC,"Change abandoned by ya.wang (wang.ya@99cloud.net) on branch: master
Review: https://review.openstack.org/537311"
1730619,2018-06-01 17:25:40 UTC,"I think the intent behind the loopingcall classes was that the timeout applied to repeated calls to the function in question, not that it would prevent the function from running longer than the timeout.  However, the docstring does seem to indicate that both are valid, which needs to be addressed by either setting a timeout on the function call or clarifying the docstring so that there is no confusion about what the timeout applies to."
1730628,2018-08-12 14:16:20 UTC,"I'd love to get a bash completion script for tmux/byobu in Byobu.  I need one contributed under a GPL3 license, and I'd take it in a heartbeat!"
1730628,2018-08-12 15:30:21 UTC,https://github.com/dustinkirkland/byobu/pull/27
1730640,2020-04-12 20:24:08 UTC,Bug # 1872347 references this bug.
1730645,2018-09-12 16:18:36 UTC,"as mentioned in the bug-title:
try with Java 10."
1730645,2019-12-25 18:49:29 UTC,"@garimapriya89
Please do not add comments containing questions to other questions/bugs, that are not definitely about the same context.
Always start with your own new question."
1730645,2018-12-02 11:01:00 UTC,ok thanks
1730645,2018-11-30 11:41:36 UTC,"@Michelle
your question is not related to this bug topic !"
1730645,2018-09-12 15:58:52 UTC,"Hi @Raiman,"
1730645,2018-11-30 09:55:12 UTC,"Hi @Raiman,"
1730645,2018-06-13 19:20:07 UTC,"I tried that already but it gives me the following error when running SikuliX 1.1.2
https://pastebin.com/dWerkpTa"
1730645,2018-06-13 09:18:20 UTC,@sdraganov: Try with Java 10
1730645,2018-06-13 05:30:33 UTC,"Is there workaround for this bug?
Can't find Java 9 at www.oracle.com - should I download it from third party website?"
1730645,2018-06-13 19:32:35 UTC,"Seems to work fine with 1.1.3, at least with very simple script, just a single click command.
Will do more tests and will keep you posted in case something goes wrong."
1730645,2018-02-05 14:05:01 UTC,"Thanks RaiMan.  I'll give this a try.  I suspected there might be something in the scaling.  I fiddle with it a bit, but no success."
1730645,2017-11-07 11:21:21 UTC,... and here the source if someone is interested.
1730645,2017-11-07 11:15:05 UTC,attached this is a test jar
1730646,2017-11-07 11:44:09 UTC,"This is the exact error I get on a second package I am renaming:
    ""Canonical Kernel's default repository for 'linux-meta-aws in Ubuntu' is already set to ~canonical-kernel/ubuntu/+source/linux-meta-aws/+git/xenial."""
1730646,2020-10-01 05:12:48 UTC,"Ran into this today, and a few times in the past, when having to migrate private git repos for leavers."
1730652,2017-11-07 12:37:33 UTC,patch at https://review.openstack.org/517997
1730652,2017-12-07 17:41:33 UTC,"Change abandoned by Stenio Araujo (<email address hidden>) on branch: master
Review: https://review.openstack.org/517997
Reason: This is being handled by https://review.openstack.org/#/c/523943/"
1730656,2019-03-20 22:11:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730657,2018-01-14 00:13:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730657,2018-01-14 00:36:49 UTC,"I'm not sure what (else) changed between 17.04 and 17.10, but this seems to be an ordering issue between `systemd --user` and ecryptfs mounting the decrypted $HOME."
1730672,2018-11-15 03:57:55 UTC,by the way i used offline ISO for installing a fresh 18.04 .
1730672,2019-04-19 15:52:43 UTC,"Important: Low? What a joke! My computer connected to the university network via proxy, because of this bug I can not install anything from Software Center. Please fix this bug."
1730672,2019-03-06 09:12:50 UTC,I can confirm that bug for a fresh installed 18.04 working behind a corporal http/https-proxy that requires authentication.
1730672,2019-02-28 17:52:50 UTC,Using the graphical tool would also prompt you for a password to be able to apply the change to the system so it wouldn't make a difference for you?
1730672,2019-02-28 16:53:29 UTC,"@seb128, here are some details. We don't rely on the GNOME tool. We only have one machine and I manually added it to out Windows AD domain. Applying the changes to the apt.conf and environment variable works but it necessitates to insert a username a password, correct me if I'm wrong, which I find a bit counter intuitive security wise. is there a way to modified it so prompts the users for their password."
1730672,2019-02-27 16:33:56 UTC,"@daniel, could you give some specifics on your issue you are having. Can't your organisation manually modif the apt configuration or environement variable? do you rely on the GNOME tool to apply manually the configuration on each machine, or how does it work?"
1730672,2019-02-27 16:22:05 UTC,"I installed a fresh copy of 18.04 from an iso too and the issue is still persisting, the proxy issue is preventing us to deploy an important machine for our organization will there be a fix for this issue soon?"
1730672,2019-07-24 09:43:10 UTC,On my 18.04 i have copied the content of proxy.conf to apt.conf and it worked
1730672,2018-11-15 03:55:43 UTC,"this bug affects my advisor's university desktop ... i updated it to 18.04 , it was working 16.04"
1730672,2018-01-24 21:41:27 UTC,"I just upgraded from 17.04, but it's impossible to complete the upgrade because of this."
1730672,2018-06-13 00:50:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730672,2018-01-27 15:32:51 UTC,"I was able to make apt work, by manually editing the /etc/apt/apt.conf file, and removing the proxy information from there. But I am having trouble installing any snaps, and still have to find a way to make that work."
1730672,2018-01-23 21:43:37 UTC,"Same in here, it is an annoying feature. How can I contribute and fix this if no one does?"
1730672,2017-11-10 01:32:14 UTC,"Thorsten - you can workaround a few different ways. For me, it's a pain because I move from a proxy-only to a non-proxy environment as I move my workstation around."
1730672,2017-11-09 22:18:32 UTC,Importance: Low? Are you sure?
1730672,2017-11-07 21:43:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730672,2017-11-07 16:56:19 UTC,re-direct to gnome-shell.
1730672,2017-11-07 16:33:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1730672,2018-06-25 11:51:08 UTC,Can the priority level be changed to something higher? This is a pretty important issue.
1730675,2018-01-06 02:09:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730680,2018-05-03 21:55:06 UTC,I have same issue on Dell XPS 15 9560 with fresh installed 18.04. Might be related to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053  ?
1730680,2017-11-08 00:08:06 UTC,kernel-bug-exists-upstream
1730680,2017-11-08 00:07:37 UTC,kernel-bug-exists-upstream
1730680,2017-11-07 21:33:34 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730680,2017-11-07 19:49:31 UTC,apport information
1730680,2017-11-07 19:49:27 UTC,apport information
1730680,2017-11-07 19:49:24 UTC,apport information
1730680,2017-11-07 19:49:22 UTC,apport information
1730680,2017-11-07 19:49:20 UTC,apport information
1730680,2017-11-07 19:49:19 UTC,apport information
1730680,2017-11-07 19:49:15 UTC,apport information
1730680,2017-11-07 19:49:17 UTC,apport information
1730680,2017-11-07 18:00:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730680,2017-11-07 19:49:02 UTC,apport information
1730680,2017-11-07 19:49:03 UTC,apport information
1730680,2017-11-07 16:33:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1730680,2017-11-07 19:49:07 UTC,apport information
1730680,2017-11-07 19:49:10 UTC,apport information
1730680,2017-11-07 19:49:12 UTC,apport information
1730680,2017-11-07 19:49:06 UTC,apport information
1730684,2019-06-30 03:57:16 UTC,"Hi, I can't reproduce this issue with Inkscape 0.92.4. As there have been many changes since Inkscpae 0.92.2, this bug will be closed."
1730709,2020-05-18 13:54:37 UTC,"In the CI report from #7, I see that initial_client_update_done==true on both the problematic minion unit and the leader unit so I am not sure my initial comment in the bug description is valid anymore (and also considering that this value is set to true on the first client update):"
1730709,2021-01-19 14:13:16 UTC,"Seen on OSCI twice in a row on bionic-queens:
http://osci:8080/job/mojo_runner/24776/console
http://osci:8080/job/mojo_runner/24843/console"
1730709,2020-05-11 15:30:19 UTC,We are seeing this in the 20.05 release candidates:
1730709,2018-01-31 16:38:11 UTC,We hit this today in our test lab.  crashdump attached.
1730709,2018-01-05 08:53:33 UTC,I will gather more logs if I encounter this again and check unit leader elections by uniter logs.
1730709,2018-01-04 12:33:12 UTC,Dmitrii
1730709,2017-11-07 17:30:51 UTC,After redeploying rabbitmq-server it clusterized just fine:
1730710,2017-11-09 12:28:07 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1730710,2018-01-03 02:43:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730717,2017-11-18 14:26:18 UTC,The fact that 4.13.8 doesn't reproduce the bug might be another indicator that the bug was introduced by a SAUCE patch.
1730717,2017-11-23 15:28:18 UTC,Just a heads up - this apparently became much harder for me to reproduce at will. We're still seeing it in actual workloads but I'm having trouble recreating manually.
1730717,2017-12-04 13:20:23 UTC,"I would note that the kernel watchdog timeouts here are always at 20 odd seconds.  They are not increasing so whatever is occuring is progressing at least as far as the kernel is concerned.  If we assume the systemd log is still working (and it was shortly before the event when it reported reaching shutdown state) then we would expect it to be in the process of attempting to deconstruct the system before calling reboot.  Most of the deconstructors it calls are reported before calling.  There is one, cg_trim(), which is not announced.  Looking at the implementation of that it is doing a hierachical remove of the /sys/fs/cgroup hierachy.  On my system this is some 15000 files in 1300 directories.  If there was a performance issue in there we could easily spend hours in this call with nothing logged."
1730717,2017-12-07 17:26:20 UTC,"We've traced the problem to ""UBUNTU: SAUCE: exec: ensure file system accounting in check_unsafe_exec is correct."" cking has a fix which will be used for zesty and artful. I've reverted the patch in bionic since there's a fix available for golang and we do not want Ubuntu userspace to become reliant on the non-standard kernel behavior in the patch."
1730717,2018-02-16 15:42:37 UTC,"Hello Everyone,"
1730717,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1730717,2017-11-17 21:34:28 UTC,OK a few days ago apw pointed me at http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.8/ which is the mainline kernel that the artful-proposed one I identified as bad is based on.
1730717,2018-04-03 14:31:57 UTC,"Thanks that this gets into releases now.
I wonder about Bionic's status - any update on that?"
1730717,2018-04-03 14:32:47 UTC,"Also since the change was identified to be in the kernel, set qemu to Won't Fix"
1730717,2018-04-03 15:28:37 UTC,"Bionic should have been fixed for a while now, updating the status."
1730717,2018-03-19 10:58:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1730717,2017-11-16 22:56:06 UTC,The bug reporter in bug 1713751 has been unable to reproduce the bug with the 4.13.0-16-generic kernel.  He's re-testing with the original kernel that exhibited the bug to ensure he can reproduce it consistently.  If he finds that 4.13.0-16-generic is really good he really might be hitting a different bug.  I'll update this bug with that answer.
1730717,2017-11-07 17:48:49 UTC,Oh also see https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1713751 which has some superficially similar symptoms (cpu stuck on shutdown).
1730717,2017-11-10 04:21:04 UTC,"Note that if it *is* the same bug as #1713751, that reporter already mentioned that using mainline kernels (and he was hitting this on 4.10) fixed it for him, so it seems more plausible not that 4.14 has a fix, but that Ubuntu's sauce has the breakage.  Of course, they may well not be the same bug, cause the symptom itself is pretty generic."
1730717,2017-11-16 13:17:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730717,2017-11-07 18:00:24 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730717,2017-11-07 19:28:54 UTC,"Do you know if this bug is also happening with Zesty, or just Artful and Bionic(>4.13)?"
1730717,2017-11-08 11:08:05 UTC,"Out of the IRC discussions documenting potentially related issues:
- this bug: KVM: Host-Kernel: Xenial-GA, Qemu: Xenial-Ocata, Guest: Bionic
- bug 1722311 KVM: Host-Kernel: Xenial-GA, Qemu: Xenial, Guest: Artful - some relation to cache pressure
- bug 1713751 AWS: triggered by Xenial kernel update, supposed fixed but shown up again and again
- bug 1655842 Host-Kernel: Xenial-GA, Qemu: Xenial, Guest: Artful - some relation to cache pressure
These might after all just run into the same soft lockup symptom, but I thought it was worth to mention for thos enot reading the IRC log."
1730717,2017-11-08 11:41:07 UTC,"On Wed, Nov 08, 2017 at 11:08:05AM -0000, ChristianEhrhardt wrote:

> @Laney I found it interesting that you essentially only needed to start+reboot.
> I assume on the host you had other workload goes on in the background (since it is lcy01)?
"
1730717,2017-11-07 17:49:52 UTC,I tried 28 (then my quota ran out) xenial guests BTW and none of those failed.
1730717,2017-11-08 12:25:48 UTC,"On Wed, Nov 08, 2017 at 11:56:02AM -0000, ChristianEhrhardt wrote:

> Torkoal (our Jenkins node) was idle atm and Ryan reported he had seen the issues there before, so trying there as well.
> This is LTS + HWE - Kernel 4.10.0-38-generic, qemu: 1:2.5+dfsg-5ubuntu10
>
> I thought about your case since you seem just to start a lot of them and reboot,
> this shouldn't be so much different to:
> $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=artful
> $ for i in {1..30}; do uvt-kvm create --log-console-output --password=ubuntu artful-${i}-bug1730717 release=artful arch=amd64 label=daily; done
> $ for i in {1..30}; do uvt-kvm wait --insecure artful-${i}-bug1730717; done
> $ for i in {1..30}; do uvt-kvm ssh --insecure artful-${i}-bug1730717 ""sudo reboot""; done
> $ sudo grep ""soft lockup"" /var/log/libvirt/qemu/artful-*-bug1730717.log
"
1730717,2017-11-08 15:16:29 UTC,"@Laney, thanks for testing the mainline kernel.  It's promising that a fix might be in that kernel.  The time consuming part will be identifying what commit in that kernel is the actual fix.  We could perform a ""Reverse"" kernel bisect, which would required testing 12 or so test kernels.  However, it sounds like to set up a reproducer is time consuming as well."
1730717,2017-11-08 16:16:15 UTC,"On Wed, Nov 08, 2017 at 03:16:29PM -0000, Joseph Salisbury wrote:

> @Laney, thanks for testing the mainline kernel.  It's promising that a
> fix might be in that kernel.  The time consuming part will be
> identifying what commit in that kernel is the actual fix.  We could
> perform a ""Reverse"" kernel bisect, which would required testing 12 or so
> test kernels.  However, it sounds like to set up a reproducer is time
> consuming as well.
>
> The easiest thing to try next would be to test the latest upstream 4.13
> stable kernels.  It's possible the fix that is in 4.14-rc8 was also cc'd
> to upstream stable and made it's way into 4.13 thorough the normal
> stable update process.
>
> If possible to test, the latest 4.13 upstream kernel is 4.13.12 and is available here:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.12/
"
1730717,2017-11-08 18:57:46 UTC,Maybe give 4.13.0-16 a try:
1730717,2017-11-09 10:01:46 UTC,"On Wed, Nov 08, 2017 at 06:57:46PM -0000, Joseph Salisbury wrote:

> Maybe give 4.13.0-16 a try:
>
> https://launchpad.net/~canonical-kernel-security-
> team/+archive/ubuntu/ppa2/+build/13567624
>
> It could also be the bug is being triggered by a Ubuntu specific SAUCE
> patch, so it won't happen with upstream kernels.
"
1730717,2017-11-08 11:56:02 UTC,"Torkoal (our Jenkins node) was idle atm and Ryan reported he had seen the issues there before, so trying there as well.
This is LTS + HWE - Kernel 4.10.0-38-generic, qemu: 1:2.5+dfsg-5ubuntu10"
1730724,2017-11-08 16:56:21 UTC,From log:
1730724,2017-11-08 17:01:28 UTC,Thanks for taking the time to file a bug! Based on the error message I would want to ask you to try starting to the service again and see how long it takes before timeout actually exceeds. And if the mailman logs have any further output.
1730731,2017-11-09 21:55:11 UTC,"> As to your last comment, it's not pointless in 17.10, right? Which means it probably works in Debian and Ubuntu? Just not in Xenial? Does 17.04 work?
"
1730731,2017-11-08 18:29:55 UTC,Tested in a ubuntu:16.04 container with vim. As-you-type autocompletion works for a test.py with:
1730731,2017-11-07 23:52:23 UTC,"As to your last comment, it's not pointless in 17.10, right? Which means it probably works in Debian and Ubuntu? Just not in Xenial? Does 17.04 work?"
1730731,2017-11-09 04:25:54 UTC,"The attachment ""Fix API errors due to use of archive python-bottle rather than internal submodule"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1730732,2018-02-06 17:30:15 UTC,Confirmed in Web Client 3.0.3
1730734,2018-02-28 22:58:48 UTC,"In the short term, though, I'm going to disable the keepup script while I kick off a reimport run of the whitelist + phasing at 1%."
1730734,2019-11-04 22:50:30 UTC,I've drafted a specification for this as follows:
1730734,2018-02-28 23:51:16 UTC,"Just so I don't forget, we would also want to make the update-repository-alias read from the same database in order to ensure it only affected packages that we have successfully imported."
1730734,2018-02-28 22:58:14 UTC,"Note that this also affects our scripts, I'm realizing."
1730734,2017-11-08 16:08:42 UTC,"I'm not saying you should be able to get at a SourcePackageRelease directly (since it isn't exported).  I'm just using that term as a convenient abbreviation: an SPR is a (source package name, version) pair.  My comments to Robie at the rally that I thought you should import each version of a package only once were equivalent to this."
1730734,2017-11-07 21:20:07 UTC,"To be clear, here is my analysis:"
1730734,2017-11-08 15:40:51 UTC,"On Tue, Nov 7, 2017 at 11:41 PM, Colin Watson <email address hidden> wrote:

> Fundamentally, I think you should be importing a SourcePackageRelease
> (although that isn't an object exported directly on the webservice), not
> a SourcePackagePublishingHistory, and that's part of why I requested
> that the graph be changed in the first place.
"
1730734,2017-11-08 07:41:46 UTC,"Fundamentally, I think you should be importing a SourcePackageRelease (although that isn't an object exported directly on the webservice), not a SourcePackagePublishingHistory, and that's part of why I requested that the graph be changed in the first place.  As such, I would have expected the commit date to correspond to the date in the package's changelog (i.e. the date of authorship), rather than to any date of publication.  I don't think you should have a link to the publication record in the commit message, since that really just recapitulates the original problem."
1730734,2017-11-08 16:22:58 UTC,"On Wed, Nov 8, 2017 at 8:08 AM, Colin Watson <email address hidden> wrote:

> I'm not saying you should be able to get at a SourcePackageRelease
> directly (since it isn't exported).  I'm just using that term as a
> convenient abbreviation: an SPR is a (source package name, version)
> pair.  My comments to Robie at the rally that I thought you should
> import each version of a package only once were equivalent to this.
"
1730742,2017-11-07 19:40:03 UTC,"Sorry, should have mentioned: the crash also appears when launching terminator from the gui, presumably because the working directory is set to my home director in that case."
1730742,2018-05-03 23:46:20 UTC,This bug sounds like it's related: https://bugs.launchpad.net/terminator/+bug/171982
1730746,2018-03-23 16:06:33 UTC,"Thanks for having run a bisect, that really helps."
1730746,2018-03-23 19:48:29 UTC,"I tested with v4.15.0-041500.  Great news, the hang is resolved!"
1730746,2018-03-23 19:56:53 UTC,Sorry but I lost track. What was the second issue?
1730746,2018-03-23 20:35:23 UTC,"Git Bisect Log 2 - https://bugzilla.kernel.org/attachment.cgi?id=274897
This identifies a separate issue (should I file a separate bug for this?) where mounting/unmounting caused error:"
1730746,2018-03-23 20:48:26 UTC,At the end of bisect log 2 I found the following:
1730746,2018-03-23 20:56:02 UTC,Yet it appears there were numerous revisions in the `drivers/scsi` area...?
1730746,2018-03-23 14:04:37 UTC,I finally got around to bisecting.
1730746,2018-03-23 21:03:18 UTC,"As far as I can see merging Dave's tree pulled in only the following three SCSI changes:
* qed*: Utilize Firmware 8.15.3.0
* qedf: fix wrong le16 conversion
* netlink: extended ACK reporting"
1730746,2018-03-23 21:32:05 UTC,Thank you again.  Should we close this issue as duplicate / resolves elsewhere?
1730746,2018-03-23 21:35:04 UTC,This ticket has category IO/Storage; SCSI. That category does not cover mounting filesystems. I'm fine with closing this ticket and creating a new ticket if for the mount issue if necessary.
1730746,2018-07-24 09:33:37 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1730746,2019-10-08 09:38:40 UTC,"whatever you have written in you blog is knowledgeable and any one can easily understand but if you don’t mind I would like to tell everyone if anyone Having problems Like hp printer showing offline then don’t be panic we are here to support you and solve all your issues of HP printers.
for more information visit our website.
https://www.800customersupport24x7.com/hp-printer-support/"
1730746,2019-10-08 11:39:43 UTC,All the blog which is provided by you is having valuable and useful content. Many bloggers learn many things from you and enhance their writting skills. As I also write blogs and in that blogs we provide information related to Canon Printer and also provide services to resolve problems of Canon Printer.  If you have any query or need any help you can use canon printer customer support or can contact to our experts or you can visit our site:- https://www.800customersupport24x7.com/canon-printer-support/
1730746,2018-03-23 20:57:16 UTC,"(Also, to clarify, the mounting does not actually fail... it produces that error as a dialog in the GUI, but mounting does actually succeed.)"
1730746,2018-03-23 14:00:44 UTC,"Created attachment 274897
Git Bisect Log 2 - 20180323"
1730746,2017-11-14 22:09:25 UTC,Done: https://bugzilla.kernel.org/show_bug.cgi?id=197875
1730746,2017-12-07 21:40:24 UTC,My hope was that the list of PCI devices would show a PCI HBA of which the driver has been modified recently. Since that's not the case I'm out of ideas about what could be the root cause of this bug. Unless someone else has an idea about how to find the root cause of this issue I think your only option is to perform a bisect of the Linux kernel.
1730746,2017-11-07 20:30:08 UTC,This change was made by a bot.
1730746,2017-11-07 21:34:39 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730746,2018-03-23 14:00:20 UTC,"Created attachment 274895
Git Bisect Log 1 - 20180323"
1730746,2017-11-14 08:31:39 UTC,Please file an upstream bug at https://bugzilla.kernel.org/
1730746,2017-11-14 22:06:16 UTC,"When booted under kernel 4.13.x, processes (such as parted, boot-info, gparted, etc) always hang when attempting to run due to a Western Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel 4.10.x (even when all other things are the same about the system but only booted kernel is different)."
1730746,2017-11-14 22:26:27 UTC,Please provide the output of the following command after having reproduced the hang:
1730746,2017-11-09 19:53:33 UTC,"Yes, issue still exists in 4.14.0-041400rc8."
1730746,2017-11-29 14:14:44 UTC,"Created attachment 260927
Output of requested command as su"
1730746,2017-11-29 14:34:15 UTC,"Created attachment 260929
Output of requested command as su"
1730746,2017-11-29 16:36:47 UTC,So command processing got stuck. Since there are two code paths in recent kernels we need to know whether or not scsi-mq was used. Hence please provide the output of the following command:
1730746,2017-11-29 20:01:10 UTC,"> # for d in /sys/block/*; do sfx=""""; [ -e ""$d/mq"" ] && sfx="" [mq]""; echo
> ""$d$sfx""; done
> /sys/block/loop0 [mq]
> /sys/block/loop1 [mq]
> /sys/block/loop2 [mq]
> /sys/block/loop3 [mq]
> /sys/block/loop4 [mq]
> /sys/block/loop5 [mq]
> /sys/block/loop6 [mq]
> /sys/block/loop7 [mq]
> /sys/block/sda
> /sys/block/sdb
> /sys/block/sdc
> /sys/block/sr0
"
1730746,2017-11-29 20:16:11 UTC,"That's weird, there are no known queue lockup bugs in the legacy block/SCSI core layers. Is the WDC harddisk perhaps controlled by a HBA? Can you provide the output of lspci (run as root)?"
1730746,2017-11-30 16:04:40 UTC,"Created attachment 260953
Output of lspci on 4.10.x kernel"
1730746,2017-11-29 14:07:59 UTC,"Created attachment 260925
Output of requested command"
1730747,2019-11-01 21:11:07 UTC,There are improvements in this area in 2.7 but not all the cases identified are fixed. I'm going to bump it to carry it forward.
1730747,2020-04-07 12:33:44 UTC,"I'm going to assign this to Simon as he's working on updating reload-spaces with the new 2.8 abilities and a few of these should get done. We can mark those as complete and carry over specific bugs, perhaps as new ones that ""reload-spaces should support X"""
1730747,2020-04-07 13:02:30 UTC,Wooohoo!!! Thank you - @rharding & @simonrichardaon
1730747,2020-04-07 21:51:31 UTC,"On Tue, 2020-04-07 at 12:33 +0000, Richard Harding wrote:

> I'm going to assign this to Simon as he's working on updating reload-
> spaces with the new 2.8 abilities and a few of these should get done.
> We
> can mark those as complete and carry over specific bugs, perhaps as
> new
> ones that ""reload-spaces should support X""
"
1730747,2020-10-21 20:38:39 UTC,This may have been fixed by work to track spaces by internal id rather than provider id. @manadart: is this bug fixed?
1730747,2020-10-22 15:14:59 UTC,"No it isn't. We implemented functionality for users to massage space names and network topology, along with a slew of safety checks based on endpoint bindings and space constraints."
1730749,2017-11-07 21:44:21 UTC,"Does only the selection mode lead to the problem or are other modes (fullscreen, window, etc) also affected? It sounds like a duplicate of https://bugs.launchpad.net/shutter/+bug/1502263"
1730754,2017-11-07 21:46:19 UTC,Linux raspberrypi 4.9.41+ #1023 Tue Aug 8 15:47:12 BST 2017 armv6l GNU/Linux
1730760,2019-12-27 21:30:08 UTC,"`start` points to `e21fb12b6bfe76a1fbe652a5aaca7779612fe766` (""imported from WHN personal CVS"", September 2000), it does not seem to be important (and if it is, it can be properly re-created)."
1730760,2019-12-23 09:40:07 UTC,Running on a freshly created repo:
1730760,2019-12-23 11:49:07 UTC,I can confirm that deleting `start` and `tabby` solves the problem in a copy of the repository.
1730760,2017-11-08 01:07:06 UTC,You have some git option enabled that performs these checks.
1730762,2017-12-06 03:57:07 UTC,"Yes,"
1730762,2017-12-05 22:00:15 UTC,"Hello, there is still someone looking for this issue?
Thanks, Alessandro-"
1730762,2017-11-27 21:09:37 UTC,No you cannot: the system dead evenif the HD is spinning. The only way to restart the desktop is to unplug and then replug the power cable from the socket.
1730762,2017-11-27 05:00:06 UTC,"> On 23 Nov 2017, at 8:23 PM, venturia <email address hidden> wrote:
>
> Correct.
"
1730762,2017-11-23 05:35:45 UTC,"> On 21 Nov 2017, at 6:41 AM, venturia <email address hidden> wrote:
>
> I've tested all the following 64bit versions:
>
> version before 3.13 were not starting
> version 3.14 and 3.15 were starting only with x.org
> for 3.16 and above start with wayland or xorg.
>
> That said, all the 64 bit version fail in managing the suspend resume.
>
>
> Using the old 14.04.1 32 bit from CD works fine. I don't how to test all the other 32 bit version. The bios is not able to start from USB and that make everything hard to test.
"
1730762,2017-11-23 12:23:13 UTC,Correct.
1730762,2017-11-20 03:47:18 UTC,Please find the last working kernel and first non-working kernel in http://kernel.ubuntu.com/~kernel-ppa/mainline/.
1730762,2017-11-17 10:21:23 UTC,The two versions were not working.
1730762,2017-11-17 05:05:47 UTC,"> On 17 Nov 2017, at 5:14 AM, venturia <email address hidden> wrote:
>
> I've done the test as described but this didn't fix the issue.
>
> While booting I've seen some ACPI error as per the attached image
> https://photos.app.goo.gl/YTZxkq7T2N4SiBGb2
>
>
> I've tried all the different 4.14.0-041400 kernels: all of them fail in handling correctly the resume step.
>
> The main difference with the previous kernel is that the mouse seem to
> resume - I sow the red of the leds, but having the screeen black I've no
> idea about the correct functionality.
>
> Suspend/resume was working correctly in 14.04, 14.10, 15.04 32 bit
> version.
"
1730762,2017-11-16 21:14:02 UTC,I've done the test as described but this didn't fix the issue.
1730762,2017-11-14 20:02:09 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730762,2017-11-07 22:30:08 UTC,This change was made by a bot.
1730762,2017-11-20 22:41:10 UTC,I've tested all the following 64bit versions:
1730765,2019-10-21 05:39:13 UTC,"Not really, as now an icon stays in the dock even if there is no connected device which is a bit meaningless."
1730765,2019-10-21 08:18:59 UTC,That's bug 1848836.
1730765,2019-10-21 08:10:02 UTC,"The issue was resolved in Ubuntu 19.10, the dock lists devices now. If you have problems with the implementation best to open a new report describing the details"
1730765,2019-10-21 03:08:30 UTC,Isn't this fixed in 19.10?
1730765,2017-11-08 10:50:58 UTC,"It's indeed another way, Daniel = it's not the same thing all ;-)"
1730765,2018-02-28 08:59:01 UTC,"I'd say this is a regression between 16.04 LTS to 18.04 LTS. If we can't get this landed for the release, let's try and aim for 18.04.1 please."
1730765,2017-11-08 08:29:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730765,2017-11-08 02:34:57 UTC,"Confirmed, but there is another way. You can click on the clock at the top of the screen and then click on the notification to open nautilus on the device just inserted."
1730765,2018-11-13 14:47:54 UTC,"While that would be nice to have it isn't an high priority request at the moment and didn't get accounted on the features list for the disco cycle, setting as rls-dd-wontfixing then"
1730777,2017-12-12 05:01:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730777,2017-12-12 05:04:22 UTC,"I'm experiencing this problem too, though I installed Builder from GNOME Software and didn't use the ""--install-recommends"" or ""--install-suggests"" options."
1730781,2019-05-06 06:50:28 UTC,"19.04 use qemu-3.1, and so it will include the fix."
1730781,2018-07-25 23:09:10 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1730781,2018-09-04 14:59:54 UTC,qemu 2.13
1730782,2018-03-02 11:57:34 UTC,"A v9 was posted on August 31st, but there is still no progress upstream. Meanwhile, Peter Zijlstra merged 0d3d73aac2ff05c78387aa9dcc2c8aa3804405e7 (""perf/core: Rewrite event timekeeping""), which looks like would have helped with this problem."
1730782,2018-07-26 07:57:04 UTC,"the patch of this bug is under review in upstream. Once update is official, we will provide patch commit id in this bug. This bug is for tracking. Thanks for your support."
1730782,2019-03-01 03:38:57 UTC,has been fixed in 4.17
1730782,2019-03-01 12:08:02 UTC,Hi @quanxian. What commits are these? Do you want these on bionic 4.15?
1730782,2019-03-04 02:50:23 UTC,No special request for bionic. Just for 18.10 will be enough.
1730782,2019-03-04 02:51:36 UTC,no more work to be done. 18.10 has contained the patch.
1730790,2018-10-25 06:07:40 UTC,18.10 latest kernel is 4.18. All commits have been in 18.10.
1730790,2018-08-09 01:14:35 UTC,4.18-rc1
1730790,2018-08-29 06:06:47 UTC,since 18.10 will use 4.17. this feature need backportign
1730790,2018-08-09 01:13:08 UTC,"yes, please."
1730790,2018-02-24 00:16:07 UTC,Is there a list of commits we should confirm for 18.04?
1730790,2018-08-09 01:14:17 UTC,0e0162dfcd1fbe4c711ee86f24f966c318999603 0f519f0352e37e7d71bdce5559517c74a35f6e33 2da331465f44f9618abe8837d1a68405d550b66e 4749f8196452eeb73cf2086a6a9705bae479d33d 5a6c9d94e9ed7410142bc6fcb638a4db1895aa0c 927b2deb067b8b4753fc09c7a42092f43fc0c1f6 9aae1780e7e81e54edfb70ba33ead5b0b48be009 d71f11c076c420c4e2fceb4faefa144e055e0935
1730790,2018-07-25 23:07:35 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1730801,2017-11-08 01:40:39 UTC,"After checking the gpsd source page, all generated dbgsym's seem to be empty"
1730801,2018-09-03 14:42:19 UTC,"Hi,
I have not tracked when this was fixed - but it is."
1730809,2017-11-08 02:42:42 UTC,"Bumping to 2.4, since there will be changes required to support storage. With C5, EBS volumes are exposed as NVMe block devices. See: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html"
1730809,2017-11-08 04:30:01 UTC,Do we know if the Ubuntu images already support this?
1730809,2017-11-08 04:50:36 UTC,"From the linked blog post: ""The latest Amazon Linux, Microsoft Windows, Ubuntu, RHEL, CentOS, SLES, Debian, and FreeBSD AMIs all support C5 instances."""
1730809,2018-01-03 01:50:34 UTC,"This is partially addressed by https://github.com/juju/juju/pull/8253. I'm reluctant to mark this Fix Committed, because the instance type data provided by AWS is incomplete; it doesn't include C5 or M5 for all regions, even where those instance types are supported."
1730825,2017-11-08 02:19:26 UTC,test 3 times
1730825,2017-11-08 02:17:14 UTC,test report bug
1730825,2017-11-08 02:17:24 UTC,test
1730825,2017-11-08 02:19:25 UTC,"Hi, Very good report"
1730831,2017-11-08 02:38:48 UTC,"Reviewed:  https://review.openstack.org/518428
Committed: https://git.openstack.org/cgit/openstack-dev/sandbox/commit/?id=b5b60fb43502939005b62b5c61cc98e08a4a09f8
Submitter: Zuul
Branch:    master"
1730831,2017-11-08 02:32:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/518428"
1730834,2017-11-14 07:20:03 UTC,Anyone meets the same issue here?
1730834,2018-01-04 01:06:37 UTC,This is expected with the current code. See the release note: https://github.com/openstack/nova/blob/master/releasenotes/notes/ironic-driver-hash-ring-7d763d87b9236e5d.yaml#L10-L16
1730860,2019-06-03 10:18:41 UTC,they are shown during ubiquity-maybe and only-ubiquity installer modes.
1730864,2017-12-05 18:38:59 UTC,"Hi Rene,"
1730864,2017-11-28 01:42:16 UTC,"Hello,"
1730864,2017-11-28 01:38:38 UTC,"Hey,"
1730864,2017-11-27 20:03:27 UTC,Uninstalling tlp and tlp-rdw packages eliminates the error.
1730864,2017-11-27 12:49:06 UTC,"These systemd services are not running but according to tlp-stat, it's enabled.
Can you try to uninstall these packages and see if the error persists?"
1730864,2017-11-25 11:08:07 UTC,"OTOH, TLP services are not enabled according to tlp-stat -s, so does that mean my laptop is not using TLP after all?"
1730864,2017-11-25 09:21:33 UTC,Looks like TLP was installed on my laptop at initial installation time.
1730864,2017-11-24 22:28:21 UTC,"<email address hidden>,"
1730864,2017-11-18 20:54:52 UTC,I've got a similar issue on a recently purchased Dell Inspiron 5770 with an AMD Radeon 530 graphics card with openSUSE Tumbleweed.
1730864,2017-11-16 19:36:45 UTC,An interesting information: It's only with open source amdgpu driver. With amdgpu-pro it's not happening but this driver isn't compatible with Ubuntu 17.10.
1730864,2017-11-16 18:10:51 UTC,"Err. Sorry about that.
I've uploaded the correct file now."
1730864,2017-11-16 18:00:00 UTC,"(In reply to Rene Barbosa from comment #0)

> Created attachment 135524 [details]
> dmesg
"
1730864,2017-11-16 17:57:07 UTC,"Ok I did it!
https://bugs.freedesktop.org/show_bug.cgi?id=103783"
1730864,2017-11-16 17:55:34 UTC,"Created attachment 135526
modules"
1730864,2017-11-16 17:55:13 UTC,"Created attachment 135525
lspci"
1730864,2017-11-16 17:54:35 UTC,"Created attachment 135524
dmesg"
1730864,2017-11-16 04:59:48 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu"
1730864,2017-11-14 23:20:52 UTC,"Also tried to disable runpm in amdgpu and switch it off in both kernels (stock and Mainline Build).
For some reason the system is enabling it again (?) and the shutdown/reboot hangs until I force the process using Magic SysRQ."
1730864,2017-11-14 21:23:26 UTC,Kernel bug exists upstream.
1730864,2017-11-14 19:53:20 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730864,2017-11-08 04:30:09 UTC,This change was made by a bot.
1730864,2019-11-19 08:26:22 UTC,-- GitLab Migration Automatic Message --
1730864,2017-11-16 18:10:09 UTC,"Created attachment 135527
dmesg"
1730865,2020-11-09 08:51:49 UTC,"4.13 EOL, closing this bug."
1730867,2018-02-24 02:19:57 UTC,"Sorry, please disregard comment #1.  Setting this to Incomplete until we have a set of commit id's to confirm for 18.04."
1730867,2018-05-21 04:17:39 UTC,[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.]
1730867,2018-05-21 04:17:41 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1730867,2018-07-25 23:02:46 UTC,"Thanks for filing this bug.  This project is being shut down as it’s not actively monitored by any team or individual.  This bug will not be deleted but will be closed as <<Won’t Fix?>>.  If this bug is something that is still affecting a product in Ubuntu, you can take one of the following steps to report this bug correctly:"
1730867,2019-10-23 03:05:21 UTC,Merged during 5.2 window. Commit IDs and Patch Subject:
1730867,2018-02-24 02:18:34 UTC,4.15 is now available in Bionic.  Marking this Fix Released.
1730871,2017-11-08 06:12:38 UTC,"There is such a switch in Tweaks in the Power section, but you need to install the gnome-tweaks-tool package to make Tweaks available."
1730871,2017-11-17 14:16:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730871,2018-04-20 21:54:47 UTC,"Is it fixed, or why should it be closed? :("
1730871,2018-04-21 00:03:04 UTC,"You already know the reason why the upstream report was closed, don't you?"
1730872,2019-05-07 06:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730872,2019-03-25 06:26:11 UTC,"git tag --contains c221c0b0308f
v5.1-rc1
git tag --contains 2b539aefe9e4
v5.1-rc1
git tag --contains 2794129e902d
v5.1-rc1
git tag --contains b926b7f3baec
v5.1-rc1
git tag --contains 5cd401ace914
v5.1-rc1
git tag --contains c347bd71dcdb
v5.1-rc1
git tag --contains 21c75763a3ae
v5.1-rc1
git tag --contains 664525b2d84a
v5.1-rc1
git tag --contains 8fc5c73554db
v5.1-rc1
git tag --contains 730926c3b099
v5.1-rc1
git tag --contains d200781ef237
v5.1-rc1
git tag --contains 89ec9f2cfa36
v5.1-rc1
git tag --contains 9567da0b408a
v5.1-rc1
git tag --contains 51cf784c42d0
v5.1-rc1
git tag --contains 753a0850e707
v5.1-rc1
git tag --contains 93694f9630b0
v5.1-rc1
git tag --contains 21b9e979501f
v5.1-rc1"
1730872,2019-03-25 06:17:58 UTC,"c221c0b0308f device-dax: ""Hotplug"" persistent memory for use like normal RAM
2b539aefe9e4 mm/resource: Let walk_system_ram_range() search child resources
2794129e902d mm/memory-hotplug: Allow memory resources to be children
b926b7f3baec mm/resource: Move HMM pr_debug() deeper into resource code
5cd401ace914 mm/resource: Return real error codes from walk failures
c347bd71dcdb device-dax: Add a 'modalias' attribute to DAX 'bus' devices
21c75763a3ae device-dax: Add a 'target_node' attribute
664525b2d84a device-dax: Auto-bind device after successful new_id
8fc5c73554db acpi/nfit, device-dax: Identify differentiated memory with a unique numa-node
730926c3b099 device-dax: Add /sys/class/dax backwards compatibility
d200781ef237 device-dax: Add support for a dax override driver
89ec9f2cfa36 device-dax: Move resource pinning+mapping into the common driver
9567da0b408a device-dax: Introduce bus + driver model
51cf784c42d0 device-dax: Start defining a dax bus model
753a0850e707 device-dax: Remove multi-resource infrastructure
93694f9630b0 device-dax: Kill dax_region base
21b9e979501f device-dax: Kill dax_region ida"
1730872,2018-08-07 15:00:01 UTC,Thanks for the update.  Can you post a comment when it's ok to move this bug over to the linux package and make it public?
1730872,2018-08-07 10:40:00 UTC,the commit is not ready in upstream. not public. Thanks for your understanding.
1730872,2018-07-25 23:01:33 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1730872,2018-02-24 02:24:22 UTC,Is there a list of commits we should confirm for 18.04?
1730872,2018-08-09 12:44:28 UTC,"yes, I will do. Thanks"
1730883,2018-02-24 02:43:41 UTC,Is there a list of commits we should confirm for 18.04?
1730883,2018-07-26 15:38:12 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1730883,2019-03-25 06:36:05 UTC,"c221c0b0308f device-dax: ""Hotplug"" persistent memory for use like normal RAM
2b539aefe9e4 mm/resource: Let walk_system_ram_range() search child resources
2794129e902d mm/memory-hotplug: Allow memory resources to be children
b926b7f3baec mm/resource: Move HMM pr_debug() deeper into resource code
5cd401ace914 mm/resource: Return real error codes from walk failures
c347bd71dcdb device-dax: Add a 'modalias' attribute to DAX 'bus' devices
21c75763a3ae device-dax: Add a 'target_node' attribute
664525b2d84a device-dax: Auto-bind device after successful new_id
8fc5c73554db acpi/nfit, device-dax: Identify differentiated memory with a unique numa-node
730926c3b099 device-dax: Add /sys/class/dax backwards compatibility
d200781ef237 device-dax: Add support for a dax override driver
89ec9f2cfa36 device-dax: Move resource pinning+mapping into the common driver
9567da0b408a device-dax: Introduce bus + driver model
51cf784c42d0 device-dax: Start defining a dax bus model
753a0850e707 device-dax: Remove multi-resource infrastructure
93694f9630b0 device-dax: Kill dax_region base
21b9e979501f device-dax: Kill dax_region ida"
1730883,2019-03-25 06:37:07 UTC,"git tag --contains c221c0b0308f
v5.1-rc1
git tag --contains 2b539aefe9e4
v5.1-rc1
git tag --contains 2794129e902d
v5.1-rc1
git tag --contains b926b7f3baec
v5.1-rc1
git tag --contains 5cd401ace914
v5.1-rc1
git tag --contains c347bd71dcdb
v5.1-rc1
git tag --contains 21c75763a3ae
v5.1-rc1
git tag --contains 664525b2d84a
v5.1-rc1
git tag --contains 8fc5c73554db
v5.1-rc1
git tag --contains 730926c3b099
v5.1-rc1
git tag --contains d200781ef237
v5.1-rc1
git tag --contains 89ec9f2cfa36
v5.1-rc1
git tag --contains 9567da0b408a
v5.1-rc1
git tag --contains 51cf784c42d0
v5.1-rc1
git tag --contains 753a0850e707
v5.1-rc1
git tag --contains 93694f9630b0
v5.1-rc1
git tag --contains 21b9e979501f
v5.1-rc1"
1730883,2019-05-07 06:00:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730883,2019-07-04 03:28:20 UTC,duplicate with LP#1730872
1730904,2017-11-08 08:30:10 UTC,This change was made by a bot.
1730904,2017-11-14 16:55:38 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730904,2018-01-09 15:59:38 UTC,"I have installed via BIOS advanced setup last bios version, the problem persist on
Linux rogelio-K55A 4.15.0-041500rc6-generic #201712312330 SMP Sun Dec 31 23:31:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
and previous kernels"
1730904,2018-01-03 18:31:41 UTC,"the problem persist after under new kernel:
Linux rogelio-K55A 4.14.11-041411-generic #201801022143 SMP Tue Jan 2 21:44:21 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1730904,2018-01-05 03:00:32 UTC,"A quick google shows that it has BIOS version newer then your system:
https://www.asus.com/us/Laptops/K55A/HelpDesk_BIOS/"
1730904,2018-01-04 16:24:53 UTC,"the problem persist on new kernel
Linux rogelio-K55A 4.15.0-041500rc6-generic #201712312330 SMP Sun Dec 31 23:31:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"
1730904,2018-01-09 13:24:47 UTC,"ok, I downloaded new BIOS version, installed via BIOS advanced setup, and I have experimented hangs with kernels"
1730906,2017-12-15 22:03:54 UTC,"It looks like the call to glance to fetch the image did not raise an exception, yet it also did not retrieve any data."
1730913,2019-08-08 20:45:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730918,2019-06-03 16:36:48 UTC,"Change abandoned by Ritesh (<email address hidden>) on branch: master
Review: https://review.opendev.org/550418"
1730918,2017-11-13 05:45:14 UTC,"IMO, the issue is not an issue of nova.
Probably it is an issue of oslo.config."
1730918,2018-03-01 15:36:30 UTC,I think that default value should be set to empty string or None should be treated as no zone.
1730918,2018-03-07 10:05:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550418"
1730918,2018-03-01 14:57:23 UTC,"Hi,"
1730919,2017-11-09 17:24:59 UTC,Remove the bug. It was gmail security related issue. Thanks.
1730919,2018-02-13 02:01:31 UTC,"Lets keep this open until the upstream bug has been fixed. For anyone else having the same problem, this can be worked-around per the Geary FAQ:"
1730919,2019-02-17 23:03:58 UTC,"Geary 0.13 now supports OAUth2 via GNOME Online Accounts, please try connecting with that and report any issues you find here: https://gitlab.gnome.org/GNOME/geary"
1730921,2017-11-20 12:31:41 UTC,same here.
1730921,2017-11-23 08:47:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730921,2018-03-06 12:11:48 UTC,"I had the same issue. Pressing ""ctrl"" works for moving, but not resizing the windows."
1730921,2018-05-28 05:14:40 UTC,"It looks like its fine
Moving: Ctrl and then move
Resizeing: right bottom corner"
1730921,2019-08-24 19:53:30 UTC,thanks for the workaround -- that solves it for my use
1730921,2019-08-24 22:48:34 UTC,Thank you for reporting this bug to Ubuntu.
1730921,2019-10-24 04:17:33 UTC,[Expired for xpad (Ubuntu) because there has been no activity for 60 days.]
1730922,2019-09-20 04:17:41 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1730922,2019-07-21 11:13:19 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1730924,2019-10-06 12:20:14 UTC,"> acpi_call and remove/rescan the parent bridge of wifi (need to be installed)
"
1730924,2019-12-26 13:40:47 UTC,"Hi Ganapathi,"
1730924,2019-12-02 03:49:05 UTC,"Hi Verdre,"
1730924,2019-12-01 09:29:54 UTC,"Hi Ganapathi,"
1730924,2019-10-19 15:15:08 UTC,"> 1. timeout happens after a resume, if we see below message in dmesg:
>    ""mwifiex_pci 0000:02:00.0: Refused to change power state, currently in D0""
"
1730924,2019-10-18 10:10:50 UTC,"Hi Andy,"
1730924,2019-10-18 07:42:29 UTC,"(In reply to Ganapathi Bhat from comment #105)

> Created attachment 285537 [details]
> 0001-mwifiex-set-PCIE-to-PCI_D0-power-state-on-resume
>
> Hi Tsuchiya/Verdre,
>
> Could please give a try with attached change;
>
> Regards,
> Ganapathi
"
1730924,2019-10-18 04:29:29 UTC,"Created attachment 285537
0001-mwifiex-set-PCIE-to-PCI_D0-power-state-on-resume"
1730924,2019-10-17 02:50:28 UTC,"Hi verdre,"
1730924,2019-10-16 17:35:02 UTC,">> 1. Command timeout after second suspend could be recreated in my Surface 4;
more specific observation on this(you could cross check, if possible):
1. timeout happens after a resume, if we see below message in dmesg:
   ""mwifiex_pci 0000:02:00.0: Refused to change power state, currently in D0""
"
1730924,2019-10-10 13:49:47 UTC,"Created attachment 285447
firmware dump of command timeout issue"
1730924,2019-10-10 13:48:39 UTC,"Created attachment 285445
dmesg of command timeout issue"
1730924,2019-10-10 13:47:54 UTC,"Hi Ganapathi and Tsuchiya,"
1730924,2019-10-07 12:40:35 UTC,"Created attachment 285391
[PATCH] mwifiex: debugfs: add entry for device_dump"
1730924,2019-10-07 12:35:21 UTC,"> But I fail to get these in my device(I don't know why, it is a different
> problem); So, I still fail to confirm we are hitting same issue;
"
1730924,2019-12-26 13:41:02 UTC,"Created attachment 286461
attachment-14943-0.html"
1730924,2019-10-07 08:36:30 UTC,"Hi Tsuchiya/Verdre,"
1730924,2020-04-18 00:10:09 UTC,"Created attachment 288581
attachment-30418-0.html"
1730924,2020-01-06 12:15:29 UTC,"Created attachment 286651
attachment-16293-0.html"
1730924,2020-07-02 12:04:12 UTC,"Hi Ganapathi,"
1730924,2020-07-02 12:00:33 UTC,"Created attachment 290067
mwifiex crash log on SB1 with ps_on, 5GHzAP"
1730924,2020-07-02 11:57:18 UTC,"(In reply to Pali Rohár from comment #127)

> Hello!
"
1730924,2020-07-01 23:38:52 UTC,"Created attachment 290043
attachment-26841-0.html"
1730924,2020-07-01 23:38:36 UTC,Hello!
1730924,2020-04-21 17:16:01 UTC,"(In reply to verdre from comment #125)

> Hi everyone,
>
> so Tsuchiya and I have been looking into this quite a lot for the last few
> weeks and we've identified several issues and tried to find the underlying
> reasons as far as possible.
"
1730924,2020-04-21 16:34:38 UTC,"Hi everyone,"
1730924,2019-10-06 12:02:49 UTC,"Hi Verdre and Ganapathi,"
1730924,2020-04-18 00:10:07 UTC,"Created attachment 288579
attachment-30359-0.html"
1730924,2020-04-18 00:09:48 UTC,"Hi everyone,"
1730924,2020-01-13 04:12:18 UTC,"Hi Tsuchiya,"
1730924,2020-01-10 12:36:32 UTC,*if someone knows devices
1730924,2020-01-10 12:35:54 UTC,"Also, ff someone knows devices (other than Surface) that use the same 88W8897 chip (or at least similar PCIe chip like 88W8997), let me know. I want to get the device as a reference."
1730924,2020-01-10 12:28:17 UTC,"== ""mwifiex crash on idle/using"""
1730924,2020-01-10 12:24:56 UTC,Thank you for looking into this issue. Reporting current status.
1730924,2020-01-06 12:15:17 UTC,"Hi Verdre,"
1730924,2019-10-06 01:34:00 UTC,">2. could you kindly try the same use case by disabling power_save
I mean, your use case(not #1)
"
1730924,2019-12-26 13:48:07 UTC,"Sorry, last comment was sent accidentally..."
1730924,2019-10-03 18:03:33 UTC,"Created attachment 285335
systemd journal kernel log from boot until command timeout issue"
1730924,2016-03-16 06:05:09 UTC,"Hi Weng,"
1730924,2016-03-16 03:55:05 UTC,The only thing I notice so far is that:
1730924,2016-03-16 03:52:19 UTC,Actually I'm aware of that.
1730924,2016-03-15 16:35:20 UTC,"Created attachment 209311
attachment-2572-0.html"
1730924,2016-03-14 21:25:40 UTC,It becomes much worse in linux 4.5 comparing with 4.4.2.
1730924,2016-01-26 12:41:12 UTC,"I have also noticed that the issues appear as soon as I start using the wireless card heavily (downloading files, apt update, etc.). As long as I just use ping, everything is fine."
1730924,2016-01-26 12:39:25 UTC,"I have the same problem on my Microsoft Surface 3 (not Pro model), same issues (even though the rest of system is stable) and same dmesg printout.
Lspci lists the card on my tablet as: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless."
1730924,2016-01-25 22:42:37 UTC,"I have the same problem. In addition, using mwiflex_pcie on Surface Pro 4 seems to cause intermittent system crashes."
1730924,2016-01-23 02:25:07 UTC,"Created attachment 201031
A more complete log with debug flag set to 0xffffff"
1730924,2016-01-03 16:27:33 UTC,I have the same problem with mwifiex_pcie (latest git firmware) on Surface Pro 3
1730924,2015-12-22 00:14:21 UTC,"Created attachment 197961
log with firmware 15.68.7.p53"
1730924,2015-12-21 06:53:15 UTC,"Could you try following latest firmware?
http://git.marvell.com/?p=mwifiex-firmware.git;a=commit;h=495e89368ea4f59bf6f8e54e94b5e8448fadd541"
1730924,2015-12-21 06:47:45 UTC,"It's commit bbe4917 from linux-firmware git repository, not quite sure about the actual version."
1730924,2015-12-21 06:45:09 UTC,"Thanks for reporting the problem. This is a command timeout problem caused mostly due to a firmware bug.
Which firmware is being used here?"
1730924,2015-12-21 06:39:55 UTC,"Created attachment 197921
a more complete log when problem happens."
1730924,2019-10-05 18:56:27 UTC,"Hi Verdre,"
1730924,2015-12-20 03:39:56 UTC,"Wifi looks fine at first after boot, but after hours of use or even idle, it goes into a unrecoverable state (unable to send and receive) until next reboot. dmesg logs shows lots of following messages:"
1730924,2016-03-16 09:35:54 UTC,"Created attachment 209441
attachment-7733-0.html"
1730924,2016-03-24 17:29:41 UTC,"Created attachment 210651
kernel 4.5 log with debug mask 0xfffffff"
1730924,2019-12-26 13:41:01 UTC,"Created attachment 286459
attachment-14890-0.html"
1730924,2016-04-04 19:17:51 UTC,"Created attachment 211711
Log of the failure to connect."
1730924,2017-11-23 08:37:31 UTC,Testing...
1730924,2016-04-04 19:17:14 UTC,I'm experiencing a variety of problems with this driver as well.
1730924,2017-11-21 11:45:40 UTC,"Let's see, I just tested this patch, which supposedly solves the wifi controller instability, but it doesn't work for me. I'll leave the link for what it's worth."
1730924,2017-11-21 11:00:48 UTC,bug-exists-upstream
1730924,2017-11-21 10:58:04 UTC,More crashes! Problem still here.
1730924,2017-11-15 12:04:23 UTC,At the moment wifi still working... No crashes.
1730924,2017-11-15 10:15:23 UTC,"El 14/11/17 a las 17:54, Joseph Salisbury escribió:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?


No, always

>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.14 kernel[0].
"
1730924,2017-11-23 05:14:21 UTC,"Try the daily mainline kernel, http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/"
1730924,2017-11-08 10:00:10 UTC,This change was made by a bot.
1730924,2017-11-14 16:54:54 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1730924,2017-11-23 10:55:02 UTC,"Still doesn't work. The wifi is down again, taking the rest of the system with it."
1730924,2016-04-04 19:18:46 UTC,"Created attachment 211721
Log of the cmd size 0 failure mode."
1730924,2017-11-23 10:15:58 UTC,"At the moment the wifi has not fallen, but after a reboot of the system has been slow enough to start and gives me this error.
I'll keep trying to see if he can hold on."
1730924,2016-04-13 14:45:42 UTC,"Created attachment 212611
Log of a failure to connect, with debug mask set from boot."
1730924,2016-04-13 14:47:18 UTC,"Created attachment 212621
Log of a 'working' session, which has poor latency.  debug_mask ffffffff from start."
1730924,2017-11-08 09:53:06 UTC,"Tested with ""wicd"" too.
Wicd crashes when wifi goes down"
1730924,2016-04-13 14:44:56 UTC,"I've spent some time looking at the source code and trying to debug what is happening.  I'm using the kvalo wireless-drivers-next pending branch, and I've applied recent patches sent to lkml that seem valuable; but the problems persist."
1730926,2017-11-08 10:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730926,2017-11-21 09:20:53 UTC,"This test still fail with 4.4.0-101 on s2lp6g001 (zKVM).
However, I have switched to 4.4.0-98, lxc-test-unpriv failed too."
1730926,2017-11-22 03:19:38 UTC,I have found the cause.
1730938,2017-12-09 19:59:56 UTC,california should be removed from the archive. it's a Yorba project that hasn't had a release since Yorba closed. there is now gnome-calendar as a maintained package in main.
1730938,2017-12-10 21:29:29 UTC,Agreed - dead upstream and should be removed.
1730938,2017-12-10 22:18:30 UTC,"Removing packages from bionic:
 california 0.4.0-0ubuntu8 in bionic
  california 0.4.0-0ubuntu8 in bionic amd64
  california 0.4.0-0ubuntu8 in bionic arm64
  california 0.4.0-0ubuntu8 in bionic armhf
  california 0.4.0-0ubuntu8 in bionic i386
  california 0.4.0-0ubuntu8 in bionic ppc64el
  california 0.4.0-0ubuntu8 in bionic s390x
Comment: lp: #1730938: dead upstream
1 package successfully removed.
Removing packages from bionic-proposed:
 california 0.4.0-0ubuntu9 in bionic
Comment: lp: #1730938: dead upstream
1 package successfully removed."
1730939,2018-05-01 02:49:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730940,2017-11-16 20:39:09 UTC,I want to emphasise my last paragraph and add some details:
1730940,2017-11-16 21:05:46 UTC,"Hi,"
1730940,2017-11-27 22:04:04 UTC,"i just wish somebody implement an easy way to uninstall the chronically buggy programs ""cinnamon-screensaver"", ""gnome-screensaver"", ""mate-screensaver"" etc and to switch to the far more fail-proof xscreensaver."
1730940,2017-12-08 09:48:39 UTC,"ok, further testing with cinnamon-screensaver 3.6.1+sylvia"
1730947,2017-11-08 15:45:08 UTC,"doesn't work, the build then fails with"
1730947,2019-12-23 03:07:00 UTC,I hit the same bug on Gentoo with glibc-2.29-r2 and alsa-lib-1.1.8.
1730947,2017-11-08 14:00:02 UTC,"Looks like the ""#ifdef __GLIBC__"" from this commit could probably be replaced with an ""#if 0"":"
1730950,2017-11-08 13:54:51 UTC,"+ /tmp/go/bin/spread -v autopkgtest:ubuntu-18.04-amd64
2017-11-07 15:12:28 Found /tmp/autopkgtest.ywbck5/build.NfH/snapd-2.28.5+17.10/spread.yaml.
error: nothing matches provider filter"
1730958,2018-07-24 09:33:40 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1730958,2018-03-28 19:19:54 UTC,"Yes, it might be best to open an upstream bug since the current mainline kernel still exhibits the bug.  There is some info on how to do that:"
1730958,2018-03-26 18:27:38 UTC,"I've just tried with more recent kernel, but issue still exists.
Kernel: linux-image-4.16.0-041600rc7-generic"
1730958,2017-12-23 20:31:41 UTC,"not sure if it helps, but please /proc/ioports below. There is a difference between kernel 4.13 (not working) and kernel 4.5.7 (working):"
1730958,2017-12-16 09:58:30 UTC,277edbabf6fece057b14fb6db5e3a34e00f42f42 is the first bad commit
1730958,2017-12-04 21:00:50 UTC,"Thanks Joseph!
Progress is made with bisect. Only 9 steps left, but takes time with compile and testing. Hope to get there soon."
1730958,2017-12-04 19:35:28 UTC,"There is a wiki on the bisect process:
https://wiki.ubuntu.com/Kernel/KernelBisection"
1730958,2017-11-16 19:33:46 UTC,"Kernel 4.14 (latest) does NOT work correctly
Kernel 4.5.7 does work correctly
Kernel 4.6.0 does NOT work correctly"
1730958,2017-11-14 16:53:38 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1730958,2017-11-08 15:15:00 UTC,apport information
1730958,2017-11-08 15:14:59 UTC,apport information
1730958,2018-01-17 08:19:18 UTC,"Should I file an upstream kernel bug or is that automatically done? Any parts missing or anything I can try?
I’ve noticed it on two different systems and really strange that there are no #metoos...."
1730958,2017-11-08 15:14:58 UTC,apport information
1730958,2017-11-08 15:14:59 UTC,apport information
1730958,2017-11-08 15:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1730958,2017-11-08 15:14:46 UTC,apport information
1730958,2017-11-08 15:14:47 UTC,apport information
1730958,2017-11-08 15:14:48 UTC,apport information
1730958,2017-11-08 15:14:50 UTC,apport information
1730958,2017-11-08 15:14:52 UTC,apport information
1730958,2017-11-08 15:14:51 UTC,apport information
1730958,2017-11-08 15:14:54 UTC,apport information
1730958,2017-11-08 15:14:55 UTC,apport information
1730958,2017-11-08 15:14:56 UTC,apport information
1730958,2017-11-08 15:14:57 UTC,apport information
1730958,2017-11-08 15:14:50 UTC,apport information
1730960,2019-05-16 09:33:00 UTC,Doesn't seem to be an issue now we've added grouping. I'll close this and we can reopen if it becomes an issue again.
1730964,2018-01-24 22:29:24 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1456
1730965,2019-09-19 11:59:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1730968,2020-08-27 02:42:36 UTC,The latest machine details design shows a link to test that particular parameter if no tests have been run yet. The test form is then displayed with a relevant set of scripts auto-selected.
1730975,2017-11-09 10:14:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518699"
1730975,2019-10-07 10:08:52 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/518699
Reason: I agree that since this is a deprecated API, it seems wrong to make changes to it even if the changes themselves make sense. In any case, given that this effort has stalled, I'm going to abandon this. Please re-open and raise in the weekly meeting [1] or on the openstack-discuss mailing list if you think this should be addressed"
1730980,2017-11-23 16:27:44 UTC,"Do any of you know a workaround to make the windows smaller? Or can you tell me how to provide more info to help solve the problem?
Thanks!"
1730980,2017-11-08 15:40:10 UTC,"Actually the problem (very large top bar etc.) is also there when opening a new window, even if only the low resolution screen is on."
1730981,2018-01-10 21:04:15 UTC,"I gave this just a bit of thought today since someone asked me about it.  I do think we need YAOUS set for child org units as a parent org may want to search some child shelving locations but not all.  For example, a headquarters library that has a book mobile org and a tech services org as children and wants shelving locations for the bookmobile to show up.  And it may need to populate up more than one parent level."
1730990,2019-11-01 18:33:57 UTC,"YAY!!! Thank you!  This came up again this week as I have a tester who has not only removed tests from the main test run, but also from subsequent re-tests :/ SO making those cases more obvious will definitely help."
1730993,2017-11-27 02:44:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1730993,2017-11-27 02:46:57 UTC,"Same issue:
 - Lenovo X1 Carbon (5th gen) with Intel Dual Band Wireless-AC 8265 Wi-Fi 2x2 802.11ac + BT4.2 chipset
 - Ubuntu 17.10
 - Logitech MX Anywhere 2 bluetooth mouse"
1730993,2017-11-27 02:51:37 UTC,"Workaround with disabling bt_coex described here:
https://unix.stackexchange.com/questions/335329/bluetooth-mouse-stops-working-after-a-few-seconds-networkmanager-issue"
1730993,2018-01-11 13:12:38 UTC,"Same Issue,
Lenovo T470P, Thinkpad Laser Bluetooth Mouse, Ubuntu 17.10"
1731002,2021-02-12 21:10:15 UTC,More info here (testing on 3.6):
1731003,2017-11-08 16:58:59 UTC,"I confirm that it fails when using the external source.
rimraf is a devDependency, which makes me think if there's a problem installing those. But this needs debugging to actually find where the behaviour diverges."
1731010,2017-11-08 19:12:58 UTC,"Very closely related, trying to save a subscription with a blank Start Date also fails silently, except for errors in the console."
1731010,2018-02-06 17:26:11 UTC,"Tested in Web Client 3.0.3.
Subscription fails to save unless date in YYYY-MM-DD format. Fails without user-visible message. Tested both blank date and wrong format."
1731010,2017-11-08 19:13:56 UTC,"For the record, the empty start date field causes this error:"
1731010,2018-07-16 15:34:18 UTC,Update to this bug with a little clarification.
1731013,2017-11-10 16:50:07 UTC,"This should be split into two fixes, I think."
1731017,2019-09-19 11:59:52 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1731020,2017-11-17 09:33:33 UTC,"Hi Brian,"
1731020,2017-11-16 17:15:52 UTC,"Hello Suma,"
1731020,2017-11-16 10:33:50 UTC,"Hi Brian,"
1731021,2018-02-21 18:54:37 UTC,I am assigning myself to see if the vendor is still interested in testing this before it goes in.
1731021,2018-02-21 23:37:59 UTC,"If this does end up going in, I think the setting should probably be moved to be an attribute on the <login> element.  That ties the format to the specific client, rather that setting it for an entire <institution>.  Opinions?"
1731021,2018-02-28 13:31:51 UTC,"So, I was not thinking straight when I took this bug over. I don't have time to look at it right now. I'm assigning it to Dan Pearl and will ask him to do the testing with the vendor and to make the changes from Mike's comment #4."
1731021,2018-07-06 15:08:21 UTC,I am reworking Dan's branch and may just start this over.
1731021,2018-08-22 12:46:35 UTC,"And, I'm not really working on this any more."
1731021,2019-04-10 18:37:04 UTC,Kicking the dust off this one.  Will post a follow-up branch soon.
1731021,2019-04-10 19:04:50 UTC,New branch pushed:
1731021,2019-05-13 14:46:23 UTC,I have pushed another commit to this branch integrating some additional features coded by Jason Stephenson (see working/user/dyrcona/sip2-envisionware-fid) to support specifying the fee type as fine/fee/lost depending on the last billing type of each transaction.
1731021,2019-09-06 21:54:39 UTC,"Pushed to master for inclusion in 3.4. Thanks, Dan and Bill!"
1731021,2017-11-08 18:16:55 UTC,I have implementation currently in internal review.
1731021,2018-02-21 16:25:21 UTC,"As it turns out, there was no change needed to the SIP product (just the Evergreen)"
1731028,2020-09-10 02:39:37 UTC,"Meson flag added in 42.3, thanks!"
1731033,2017-11-08 19:55:05 UTC,Just in case... I'm talking about UBUNTU FRANCOPHONE PAGES...
1731034,2019-09-17 10:42:28 UTC,Migrated to https://github.com/widelands/widelands/issues/3223
1731034,2017-11-09 07:07:09 UTC,Thank them for a great tool then!
1731034,2017-11-08 20:58:25 UTC,That tool is written by some of the people in my office :).
1731034,2017-11-11 19:02:35 UTC,https://code.launchpad.net/~widelands-dev/widelands/clang-tidy-round1 has fixed:
1731038,2020-04-10 14:37:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731042,2020-12-09 15:16:37 UTC,"In 3.6.2, the TCN is displaying on the tab. The Record id may as well but is beyond the tab display area."
1731042,2021-02-17 21:26:48 UTC,"Ah, good point, Elaine!"
1731042,2021-02-17 21:07:22 UTC,I want to clarify comment #10 --- This is true when Local catalog is checked and native-evergreen-catalog records are listed.
1731042,2021-02-17 20:38:37 UTC,To review:
1731042,2020-12-09 15:18:37 UTC,Correction -- the TCN and title appear on the tab and are visible it you hover the mouse
1731042,2018-01-11 15:42:58 UTC,"Hey Chris, so it looks like the web staff's overlay record (along with others, i.e conjoined, vol tranfer) marking uses the bib record id (per line 453 of Open-ILS/web/js/ui/default/staff/cat/catalog/app.js) and it doesn't seem to check the ""cat.bib.use_id_for_tcn"" flag at all."
1731042,2018-08-08 21:17:36 UTC,"Correction to my earlier comment. What is being displayed in the TCN column for us is the value of tag 001, not the actual TCN.
Example: the TCN is m_burnham3910677
The 001 tag value is BHL1244
The record ID is 3910677."
1731042,2018-08-08 21:05:25 UTC,Still experiencing the problem for Show in Catalog in version 3.1.4.
1731042,2018-06-19 22:03:36 UTC,"It's not just the Record marked for overlay, either. It also displays the Record ID in the column labeled TCN. (And there is no option to add a column for Record ID, which would be nice if the TCN column actually displayed the TCN)"
1731042,2018-01-29 17:31:32 UTC,"To compound the TCN/Record ID confusion, in our version of 3.0.3, when you click on ""Show in Catalog"" when a native record is found, it uses the TCN to try to display the record, resulting in a null record display. The URL for the record actually uses the Record ID."
1731042,2018-01-11 17:14:05 UTC,"PINES catalogers use the TCN for records and not the record ID. In the XUL client, the TCN and not the record id is displayed in this as well as other places. We do need the TCN to display."
1731042,2020-12-09 15:01:59 UTC,"Adding voice to this that both DB ID and TCN should display since different libraries use either/or.  This problem persists in 3.4 and, I suspect up through all current releases."
1731046,2017-11-08 21:53:44 UTC,Almost functional rough-cut in progress.
1731046,2019-10-24 14:44:56 UTC,"Going to mark this as WONTFIX since most of the grids which contain translatable (mostly configuration) data now live in Angular grids, which have their own translator dialog."
1731056,2017-11-16 01:37:20 UTC,"Hi,
You can follow the instruction here to set up an OpenVPN server on Ubuntu Core.
https://docs.ubuntu.com/core/en/stacks/network/easy-openvpn/docs/openvpn-server-setup
Once the server is up and running, you can run the following command to generate .ovpn file, which can be used by client to connect to the OpenVPN server.
$ sudo easy-openvpn.add-client foo > foo.ovpn"
1731056,2017-11-16 00:01:15 UTC,"Hello,"
1731056,2017-11-11 11:49:33 UTC,"Hello Gary,"
1731056,2017-11-09 01:13:54 UTC,"Hey Rafael
   Thanks for your reporting.
   Would you mind to check if you can reproduce this issue by going through the following two steps
   1.change the owner of your .ovpn file to 'root' to overcome dac_override denied issue in the snappy.
     $ sudo chown root.root your.ovpn
   2.then connect to the OpenVPN server with sudo
     $ sudo easy-openvpn.connect-server your.ovpn"
1731056,2017-11-13 03:51:02 UTC,"Hey Rafael
    Thanks for your reply."
1731069,2017-11-09 10:55:39 UTC,"Alas the instructions to add the symbol archive don't work, as the key refuses to import on this machine:"
1731069,2017-11-08 23:32:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1731069,2017-11-09 03:25:27 UTC,Did you add debug symbol archive [1]?
1731069,2017-11-09 00:39:12 UTC,"This bug has nothing to do with the kernel, no idea why it's trying to get me to run apport-collect."
1731070,2018-02-21 14:20:14 UTC,"Thank you for your bug report, what Ubuntu version are you testing?"
1731070,2020-04-14 16:06:42 UTC,Still the same issue on latest Focal daily build iso.
1731070,2020-02-07 11:32:08 UTC,"Still happening on latest Ubuntu Focal daily image when in install-only mode. Not sure what could be wrong, the translatable string seems to be correct."
1731070,2020-01-16 13:10:53 UTC,"Sebastien, the translated string is not applied only in install-only mode. Not sure what causes the issue, other translated strings are showing without any problem. I checked it multiple times and it is the same every time."
1731070,2020-01-16 11:10:32 UTC,"I have just tried installing Ubuntu Focal from latest daily iso and the Skip button was correctly translated only when clicking ""Try Ubuntu"" on the Ubiquity main screen, then running the installer manually using a desktop icon. When I ran the installer directly using ""Install Ubuntu"" button, the Skip button was still untranslated for some reason."
1731070,2019-10-11 20:28:49 UTC,This bug was fixed in the package ubiquity - 19.10.19
1731070,2019-10-09 15:46:18 UTC,Still not fixed in 19.10.
1731070,2019-08-08 15:27:32 UTC,Removed the bionic tag because this issue is not related only to Ubuntu 18.04 and is still not fixed in the latest nightly.
1731070,2019-05-14 14:18:34 UTC,"The ""_Skip"" string is still missing in the translation template."
1731070,2020-01-16 12:47:08 UTC,"@Asciiwolf, thanks for the feedback. The edit you did is a bit unclear to me is 'not correctly applied' or 'not correctly applied in install-only mode'? I'm unsure what's the difference/why ubiquity would behave differently from a live session than it does for an ubiqity-install"
1731070,2018-05-11 09:32:44 UTC,Any chance that this could be fixed before Ubuntu 18.04.1 release?
1731070,2018-07-04 21:24:18 UTC,Still not fixed. :-(
1731070,2018-02-21 14:55:31 UTC,"As noted in the bug tags, I was testing it on Ubuntu 17.10, but the same issue is also present in Ubuntu 18.04."
1731070,2018-04-08 21:30:27 UTC,"The ""This software is subject to license terms included with its documentation. Some is proprietary."" string is still untranslated in the latest Ubuntu 18.04 Beta 2 although it is fully translated on Launchpad in my (Czech) language."
1731070,2018-04-08 22:20:51 UTC,"The ""Skip"" button is also untranslated although it is translated on Launchpad."
1731070,2019-10-10 22:01:04 UTC,It can be translated now in
1731070,2018-04-21 12:24:42 UTC,"Yep, it's fixed. :-)
But the ""Skip"" button (see comment #4) is still untranslated."
1731070,2018-04-21 13:17:28 UTC,"I see that ""Skip"" is in the template, but ""_Skip"" is not."
1731070,2018-04-26 15:32:18 UTC,"Feel free to close this issue when the ""_Skip"" string is added. I will update the Czech translation."
1731070,2018-04-26 15:59:14 UTC,"The remaining problem is that you can't, right? I changed the bug summary to reflect that."
1731070,2018-04-19 09:05:32 UTC,Is this possibly fixed now? This upload:
1731074,2017-11-08 23:48:06 UTC,This particular log comes from running dbLockTest
1731074,2018-02-25 02:44:03 UTC,Might this lock & unlock be there to prevent the destructor from completing until the last timerQueueActive thread has exited? Something like that seems most likely to me from past experience with Jeff's coding style.
1731080,2017-11-09 01:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1731080,2017-11-10 05:29:22 UTC,"I can't submit an collect report on here,it always show Error:connecting to Launchpad failed....etc,but I already connected to internet..."
1731080,2017-11-14 16:45:45 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1731080,2017-11-15 01:06:49 UTC,"Hi
No an update/upgrade, I just OS installed was complete with default kernel(4.10.0-28) ,It's only happend in BIOS is Legacy mode(UEFI PASS)"
1731080,2017-11-15 07:51:42 UTC,"File an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/other"
1731080,2017-11-15 08:45:02 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=103751
1731098,2017-11-24 19:56:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731121,2017-11-09 05:27:09 UTC,obviously wifi-ap.management-service[5723]: nl80211: Could not configure driver mode
1731121,2017-11-13 18:50:25 UTC,@Sokratis
1731122,2018-01-19 22:28:30 UTC,"How about:
64-bit PC (AMD64) desktop image
Recommended for all modern Intel or AMD PCs."
1731125,2017-11-09 06:03:23 UTC,My thought: Simply change it to help:gnome-help. I don't think we should count on a Unity docs team.
1731142,2020-05-04 12:05:26 UTC,"Change abandoned by Grzegorz Sikorski (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/713878"
1731142,2020-03-18 11:36:18 UTC,https://review.opendev.org/713628
1731142,2020-03-18 10:55:53 UTC,"OK, I'll push this to Gerrit as soon as some legal stuff pass here :D"
1731142,2020-03-18 10:18:50 UTC,"All right, see https://docs.openstack.org/kolla/latest/contributor/CONTRIBUTING.html"
1731142,2020-03-18 10:11:31 UTC,"Sorry, the typo was corrected and tested afterwards. I must have done something stupid with git."
1731142,2020-03-18 10:02:06 UTC,"Let's say I'm not entirely convinced you got it to work considering it has a typo: ""cluser_version"" in template. Otherwise looks pretty legit. Please propose to gerrit."
1731142,2020-04-05 16:40:41 UTC,"Reviewed:  https://review.opendev.org/713628
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=7408d499799e4d3a043f5e5ebf5f61c206bc0d2e
Submitter: Zuul
Branch:    stable/rocky"
1731142,2020-03-18 08:20:59 UTC,"Possibly, we are using Rocky and Ocata, haven't yet tested with further version. Let me try to refactor this piece to be idempotent."
1731142,2020-03-17 16:49:47 UTC,"Well, we can't really propose to raise the cluster version with each run."
1731142,2020-03-17 12:12:09 UTC,Please see attached patch file. This solves the issue for us.
1731142,2019-03-28 10:23:21 UTC,"Currently a workaround is to manually bump up the config version.
TODO: test on Stein (if new clusterer setup is fixing that)"
1731142,2019-02-15 13:24:49 UTC,"Same issue on rocky:
=INFO REPORT==== 15-Feb-2019::14:21:27 ===
Multiple different configurations with equal version numbers detected. Shutting down."
1731142,2018-04-07 11:55:56 UTC,I have the same issue.
1731142,2018-01-22 07:11:46 UTC,"I have the same issue. with one rabbitmq, it works fine, after I deployed other two rabbitmq, the other two cannot startup, keeping restarting."
1731142,2020-03-18 08:48:57 UTC,Now bumping of the version only occurs if anything in the configs is modified.
1731146,2017-12-05 08:04:26 UTC,This bug was fixed in the package lxd - 2.0.11-0ubuntu1~16.04.2
1731146,2017-12-05 08:04:31 UTC,"The verification of the Stable Release Update for lxd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1731146,2017-11-21 19:50:19 UTC,"Hello Stéphane, or anyone else affected,"
1731146,2017-11-09 06:47:30 UTC,Uploaded to the queue for xenial.
1731146,2017-12-05 08:04:11 UTC,"Automated testing is happy, we've seen a few hundred users using this without any bug report so far and I just did some extra manual testing including the upgrade and all looks good."
1731163,2018-01-03 17:21:52 UTC,Someone else seems to have reported this issue on kernel.org in the meantime:
1731163,2017-12-04 21:10:01 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1731163,2017-11-16 16:00:49 UTC,Testing with latest upstream kernel  4.14.0-041400 brings no change. The situation is exactly the same.
1731163,2017-11-14 20:32:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1731163,2017-11-14 10:17:19 UTC,"No, multi touch does not work any more with this parameter. Touch pad and track point are reduced to the functions of a standard mouse, I beliebe, which can also be seen in the corresponding settings dialog. Scrolling with the help of the middle track point button works though, as it is customary on ThinkPad models."
1731163,2017-11-14 07:31:15 UTC,Does the touchpad still have multi touch functionality with the parameter?
1731163,2017-11-11 10:04:43 UTC,I have the same problem. The workaround for the kernel parameter work very well.
1731163,2017-11-09 10:11:07 UTC,apport information
1731163,2017-11-09 10:11:02 UTC,apport information
1731163,2017-11-09 10:11:05 UTC,apport information
1731163,2017-11-09 10:10:59 UTC,apport information
1731163,2017-11-09 10:11:00 UTC,apport information
1731163,2017-11-09 08:26:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1731163,2017-11-09 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1731163,2017-11-09 10:10:44 UTC,apport information
1731163,2017-11-09 10:10:46 UTC,apport information
1731163,2017-11-09 10:11:03 UTC,apport information
1731163,2017-11-09 10:10:50 UTC,apport information
1731163,2017-11-09 10:10:53 UTC,apport information
1731163,2017-11-09 10:10:54 UTC,apport information
1731163,2017-11-09 10:10:56 UTC,apport information
1731163,2017-11-09 10:10:57 UTC,apport information
1731163,2017-11-09 10:10:47 UTC,apport information
1731166,2017-11-09 15:10:07 UTC,Hi Wenzhi:
1731166,2017-11-09 16:45:09 UTC,+1 @Bob
1731166,2017-11-09 16:45:39 UTC,It should work as long as they derived from valid tosca types.
1731166,2017-11-10 02:03:40 UTC,I was able to reproduce it easily with the nfv example.
1731185,2017-11-09 09:39:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/518695"
1731185,2019-08-28 13:23:42 UTC,"Change abandoned by Yuriy Taraday (<email address hidden>) on branch: master
Review: https://review.opendev.org/518695
Reason: As I understand, consensus is that this should not be done in library, and author's account has bee deactivated since posting this change."
1731188,2019-09-19 15:04:06 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1731200,2017-11-11 06:47:48 UTC,I have noticed that skypeforlinux does not show any characters except basic latin chars. strace-d the process and found out that it wants to mmap many fonts. I have added all required fonts to allowed list however there are still EACCES (Permission Denied) errors in the log.
1731200,2017-11-11 09:42:35 UTC,"Sorry, my mistake - I have copied the rules from old usr.bin.skype profile and one of them was ""deny /usr/share/fonts/** m,"""
1731200,2017-11-27 07:04:22 UTC,I've been working on skypeforlinux for some time:
1731246,2017-11-09 19:39:28 UTC,"If you have shell access to the Mailman server, you may find the script at https://www.msapiro.net/scripts/list_requests (mirrored at https://fog.ccsf.edu/~msapiro/scripts/list_requests) to be helpful."
1731249,2018-01-20 07:44:57 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1481
1731249,2017-11-14 11:59:15 UTC,"In order to understand whats going on we need some more information from you. What is exact command you were running. What is your my.cnf contents, more specifically what is innodb_page_size and how many parallel threads you are using. If page size is higher than default one, then you might be low on memory and go swapping. This line"
1731257,2017-11-09 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1731257,2017-11-09 14:11:19 UTC,The qrt failure is because we don't yet have the LSM stacking patches applied to 4.14.
1731257,2017-11-14 17:02:22 UTC,"LSM stacking patches have been applied in 4.14.0-7.9, so we'll see whether that resolves these failures."
1731257,2017-11-09 13:13:31 UTC,"Another problem, this one in the apparmor tests."
1731257,2017-11-09 13:13:00 UTC,"Error in kernel security tests, looks like a test problem."
1731261,2018-03-28 16:10:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731261,2017-11-09 13:40:05 UTC,"StacktraceTop:
 OsAbort () at ../../../../os/utils.c:1361
 AbortServer () at ../../../../os/log.c:877
 FatalError (f=f@entry=0x56304e194fa6 ""%s"") at ../../../../os/log.c:1015
 xwl_log_handler (format=<optimized out>, args=<optimized out>) at ../../../../../hw/xwayland/xwayland.c:885
 wl_abort (fmt=<optimized out>) at ../src/wayland-util.c:416"
1731261,2018-01-09 10:08:24 UTC,"It looks like this is probably a result of gnome-shell crashing. That would bring down mutter which is internal to gnome-shell breaking the connection to Xwayland, making it crash."
1731261,2018-05-23 08:04:31 UTC,"Tracking in:
https://errors.ubuntu.com/problem/c0246c524b893c42be5f92e0081d8e2f7ddfeaef"
1731268,2017-11-11 15:34:36 UTC,My OOPS ID from headers is
1731268,2017-11-09 14:37:51 UTC,Can one of those people please supply us with the OOPS ID?
1731268,2017-11-10 23:51:40 UTC,I tried it too.  There are no OOPS IDs shown when this happens.
1731268,2017-11-11 00:06:26 UTC,"Checked with Firefox develop tools, and now I see the OOPS is in the HTTP response headers:"
1731273,2018-08-09 01:59:26 UTC,I assume you mean both bionic and cosmic then.
1731273,2018-08-08 08:23:31 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1731277,2017-11-09 15:03:54 UTC,"I'm kind of hoping that moving to Sphinx for our docs toolchain will allow us to for instance have the board specific information in doc comments in each board source file, which could then be automatically assembled into the right documentation. The current manpages are autobuilt from the monolithic qemu-doc.texi, which is woefully out of date in many areas..."
1731278,2018-03-15 19:01:20 UTC,Here is a branch:
1731278,2018-03-15 18:32:33 UTC,"After deleting my browser grid settings (via eg/staff/admin/workstation/stored_prefs), on a 3.1-beta server, I'm seeing something similar to this bug on Chrome (though not the same order of columns that Kathy described).  But in Firefox I see exactly the expected columns in expected order.  Some research revealed that JavaScript sort in Firefox is stable, while it is unstable in Chrome.  This means our current column-sorting code relies on browsers to maintain sort order of ""equal"" columns during the sort process, but some browsers don't play along.  The solution is for us to explicitly track and maintain the column order that we want.  Dan Wells has a branch for this, coming soon."
1731278,2018-06-15 15:54:13 UTC,"This works for me. Because Dan had an outstanding question on the implementation, I have pushed my signoff to the working repo. I'm in favor of getting the current fix in rather than expanding the scope."
1731280,2017-11-09 14:57:11 UTC,I can confirm this behavior in current master.
1731280,2018-11-26 20:40:29 UTC,Removing milestones for lack of a pull request.
1731280,2020-05-27 23:25:16 UTC,Confirmed still an issue in 3.5 beta.
1731283,2017-11-09 14:56:40 UTC,"autopkgtest [13:37:31]: test wpa-dhclient: [-----------------------
modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.14.0-6-generic
ERROR"
1731283,2017-11-09 15:01:07 UTC,"This and other errors are related to lacking the cfg80211 module, which we do not build for s390. However we did not build it in artful either, and we currently have the same version of network-manager in artful and bionic, so it's odd that the tests are failing in bionic and not in artful."
1731283,2017-11-17 18:12:19 UTC,"Tests were previously getting skipped for s390, due to ""Restrictions: ... isolation-machine"" in the test control file. Possibly some sort of infrastructure problem detecting that the tests are running in a container."
1731283,2017-11-17 19:32:49 UTC,"Seems that s390x ADT does now run in VMs, which explains the change."
1731285,2017-11-10 00:10:07 UTC,Thanks for the report !
1731285,2017-11-10 09:05:30 UTC,My guess is the line should not be indented. I'll need to test.
1731296,2018-01-17 12:45:42 UTC,That got fixed before 17.10 iirc
1731296,2017-11-19 07:47:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731296,2017-11-19 07:47:28 UTC,I like proposal #1. Ubuntu-software is not unity specific but rather Ubuntu specific. Other desktop-shell may want to use that Ubuntu branding. If they want that they only need to provide a override in /usr/share/<other-session>/applications/ & install ubuntu-software. But only if they want. So we can dismiss #2 as it would be over-patching things.
1731296,2018-01-18 12:13:16 UTC,"Seb, I'm reopening this bug since it is still not fixed. It is not a problem for the default Ubuntu session but for every other desktop session such as Unity. I haven't fixed it yet because there are several ways to fix it and I wasn't sure which option we want."
1731301,2017-11-09 20:56:33 UTC,"I think a case could definitely be made however that for an out of bound request, where self is page=30000, providing a last link would be useful."
1731301,2017-11-09 21:11:37 UTC,"On reflection, I wonder if it wouldn't be better to preserve this behaviour (no ""last"" and ""next"" links on the last page), but ensure ""self"" points to the last page."
1731301,2017-11-09 20:47:46 UTC,"Hi Thomas, as mentioned on Slack, this is by design. A search request with an out of bound page request will always return the last page. You can programatically determine that this is the last page given the lack of a 'last' and 'next' links (assuming you meant ""last, next"" rather than ""last, prev"", as that indeed would be a bug)."
1731303,2017-11-09 16:29:01 UTC,See other promised screenshot
1731303,2021-02-12 21:33:09 UTC,"At some point the expanding issue was fixed because as of 3.6 I can drill down to see the full Issues Held table; however, I am unable to get the Place Hold link to appear, despite using a receiving template with holdable = true."
1731304,2017-11-10 18:20:01 UTC,"Also, noticing the ""Timed out waiting for a reply to message"" errors at scale even during heat stack creates."
1731305,2017-12-12 15:39:43 UTC,"I've seen this problem occur following other steps in a web client, but I haven't been able to pinpoint the series of steps. In all cases, though, the problem occurs when clicking the back button."
1731311,2017-11-09 21:24:41 UTC,"Ops, I think I was too fast with this report.
I will do another try."
1731312,2018-02-18 12:26:36 UTC,You need resolve depend* libgranite4* (*> = 0.4.1*) now.
1731312,2018-02-18 12:15:51 UTC,Step 2:
1731312,2018-01-19 11:09:36 UTC,"Try adding the elementary PPA:
sudo add-apt-repository ppa:elementary-os/stable
sudo apt-get update
sudo apt-get install com.github.babluboy.bookworm"
1731312,2018-02-15 13:28:23 UTC,"Updated the PPA, can you please check if the issue is resolved?"
1731312,2018-02-18 12:23:28 UTC,Step 3:
1731312,2018-02-18 12:10:09 UTC,"Sorry, but..."
1731314,2017-11-09 21:30:40 UTC,"Once one installs an input method using `apt install`, it is possible to:
* activate it manually using `ibus engine XXXX`. (use `ibus list-engine` for the list of XXXX);
* configure it using `ibus-setup`."
1731314,2017-11-09 21:37:48 UTC,"The methods that you configure or activate manually are not reflected in the top bar menu, nor in the Region & Language parameter panel."
1731315,2019-09-26 11:18:02 UTC,Sorry it's taken us so long to get back to you on this.
1731318,2018-12-24 17:11:39 UTC,"At System76, we've been carrying this patch for 18.04 and 18.10, to solve the issue."
1731318,2019-07-10 21:53:30 UTC,This bug was fixed in the package gnome-desktop3 - 3.28.2-0ubuntu1.5
1731318,2019-07-10 21:52:44 UTC,"The verification of the Stable Release Update for gnome-desktop3 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1731318,2019-07-10 21:52:39 UTC,This bug was fixed in the package gnome-desktop3 - 3.32.1-1ubuntu1.2
1731318,2019-07-03 16:30:55 UTC,"I tested on a System76 NVIDIA laptop that was affected by this issue, on bionic and disco with proposed enabled. The eDP displays are detected as builtin displays, as expected."
1731318,2019-07-03 09:14:23 UTC,"Hello Jeremy, or anyone else affected,"
1731318,2019-07-03 09:14:17 UTC,"Sorry, I messed up the bionic upload. Another one should be coming shortly."
1731318,2019-07-02 18:43:15 UTC,"Hello Jeremy, or anyone else affected,"
1731318,2019-07-02 18:36:56 UTC,"Hello Jeremy, or anyone else affected,"
1731318,2019-06-28 12:59:29 UTC,This bug was fixed in the package gnome-desktop3 - 3.32.2-2ubuntu1
1731318,2019-06-28 12:52:12 UTC,all nominated releases are uploaded - stable releases in the queue for review
1731318,2019-06-11 21:30:59 UTC,Please see https://gitlab.gnome.org/GNOME/gnome-desktop/merge_requests/39
1731318,2019-06-11 21:03:51 UTC,"> I have commented again to see if there is still interest in the patch upstream.
"
1731318,2019-06-11 21:01:06 UTC,"For what it's worth, what was said about the patch was that the code it was editing would be going away soon. That never happened. I have commented again to see if there is still interest in the patch upstream."
1731318,2019-06-11 20:22:49 UTC,"@Michael, please keep advertisement for your OS out of launchpad"
1731318,2019-06-11 20:03:42 UTC,"Canonical still does not carry this or many other patches we've made for Pop!_OS to improve NVIDIA support. If you want a better experience for your hardware, I'd recommend to install Pop!_OS. We've been carrying the patch you mentioned since 17.10, so it is enabled in both our 18.04 LTS and 19.04 ISOs."
1731318,2019-06-11 18:03:20 UTC,Can you confirm this patch made it into 19.04? I am running Disco and still seem to be suffering from it.
1731318,2019-01-11 17:37:22 UTC,Making a note that we are also carrying this it in the 19.04 (disco) release now.
1731318,2018-12-24 20:20:47 UTC,"The attachment ""fix_nvidia_suspend.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1731318,2017-11-09 19:18:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731318,2019-06-28 11:00:45 UTC,"Filing an MR and some light nagging managed to get it merged, thanks."
1731325,2017-11-09 19:49:29 UTC,gdb stacktrace is as follows:
1731325,2017-11-09 19:46:18 UTC,I set LD_DEBUG=all and executed the application. Attaching the output just for a reference.
1731328,2018-04-03 16:48:16 UTC,I'm also affected. Looking at the process list (ps ax) I found:
1731328,2018-04-03 19:19:16 UTC,"sorry, above comment was meant to be added to bug 1752411."
1731347,2020-11-10 03:14:00 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1731347,2020-09-03 08:18:05 UTC,"Hello！
   Has your problem been solved? I also encountered a similar problem. My ioctl() also returned an error -14(Bad address)."
1731347,2021-01-09 04:17:57 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1731359,2020-02-12 13:36:19 UTC,Now the bug-fix has migrated to the stable ppa
1731359,2019-11-12 20:55:09 UTC,Adding double quotes around the array variables on lines 1449 1459 prevents re-splitting the array contents. To reliably find errors like this use `shellcheck` for static analysis. Creating a user edited version of `dus` with the changes will allow using the modified version to create live media. Attached is a patch for the version of dus included in mkusb 12.3.6-1ubuntu2.
1731359,2020-02-06 21:51:06 UTC,"@ everybody affected by this bug,"
1731359,2019-04-27 18:14:57 UTC,And now I think it's right.  Please test.
1731359,2019-04-17 17:00:05 UTC,I am also running into this.  How does someone not familiar with the needed prereqs for the solution above fix this?
1731359,2019-04-21 02:55:50 UTC,I've got this issue too...  Is there a simple workaround until the bug is fixed?
1731359,2019-11-12 19:03:24 UTC,"Testing on kubuntu 19.10 with mkusb 12.3.6-1ubuntu2 from the ppa. ""/usr/bin/dus"" still contains the unquoted variables. which results in similar failure. See screenshot https://i.imgur.com/uqYgMFJ.png for version and lsblk output."
1731359,2017-11-14 06:57:46 UTC,Solved on my hardware.
1731359,2019-04-27 17:33:32 UTC,No. That's wrong.  He got them to have each field quoted.  I'll post that here when I get it right.
1731359,2019-04-27 17:28:21 UTC,This is not tested....
1731370,2020-07-30 13:47:19 UTC,"Pushed to master, rel_3_5, and rel_3_4. Thanks, Jason, Jane, and Elaine!"
1731370,2020-02-21 15:07:48 UTC,"I have tested this code and consent to signing off on it with my name, Elaine Hard and my email address, <email address hidden>."
1731370,2020-02-21 14:57:55 UTC,Tested on https://tiffany-master.gapines.org/eg/staff/
1731370,2019-01-16 14:09:14 UTC,"ah, wrong ticket!  durn bookmarks :)"
1731370,2019-01-16 14:08:06 UTC,"Dan, I didn't catch that you were still assigned to this ticket.  I've pushed a working branch that implements the behavior Mike proposed: collab/phasefx/lp1731370-callnumber-edit"
1731370,2018-10-09 00:35:20 UTC,"P.S. Here are two explanations of WCAG 1.4.1:
* https://www.w3.org/WAI/WCAG21/Understanding/use-of-color
* http://accessibility.psu.edu/color/colorcoding/"
1731370,2018-10-09 00:33:38 UTC,"This is great, Jason!  I realized that only using the green color to indicate new-ness would violate WCAG 1.4.1, so I added one more commit to your collab branch.  That commit adds a dashed border and a brief explanation for screen reader users."
1731370,2018-09-12 12:29:23 UTC,"New commit at
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/phasefx/lp1739087_volcopy_x_cn"
1731370,2018-08-28 20:46:08 UTC,Jane -- does the work on bug 1739087 provide enough of a visual cue here?  New vols/copies will have the x next to them for removal before saving; if you are editing you should not see the x.
1731370,2018-09-12 12:53:18 UTC,"And those 3 are in master now, so adding pullrequest for the top two commits."
1731370,2018-08-30 17:57:54 UTC,"Thanks for making this connection, Andrea!  I think that the X doesn't really intuitively indicate that it is a new volume/item, so I don't know if it would help with the confusion my colleague experienced.  Unless catalogers are specifically trained to look for the X, I could still see them seeing a new volume/item and understanding it as an existing one."
1731370,2018-08-30 19:47:27 UTC,"Hi Jane,"
1731370,2018-09-05 13:51:54 UTC,"This is where I'm at at the moment:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=9a67a0078fb001385990742c2301e7929cb918a0"
1731370,2018-09-05 13:48:26 UTC,"A little more work is needed with this; if you add a new copy to an existing call number, the new copy row isn't styled."
1731370,2018-09-05 13:16:06 UTC,I added an extra commit on top of my sign off branch for bug 1739087 that tries to address this
1731370,2018-08-30 21:40:01 UTC,That seems like a good solution!
1731371,2020-09-21 03:04:27 UTC,Thank you for reporting this bug to Ubuntu.
1731371,2020-11-20 04:19:26 UTC,[Expired for lxpanel (Ubuntu) because there has been no activity for 60 days.]
1731388,2017-11-13 18:17:39 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1731408,2018-07-26 15:36:17 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1731408,2019-03-25 06:38:03 UTC,"c221c0b0308f device-dax: ""Hotplug"" persistent memory for use like normal RAM
2b539aefe9e4 mm/resource: Let walk_system_ram_range() search child resources
2794129e902d mm/memory-hotplug: Allow memory resources to be children
b926b7f3baec mm/resource: Move HMM pr_debug() deeper into resource code
5cd401ace914 mm/resource: Return real error codes from walk failures
c347bd71dcdb device-dax: Add a 'modalias' attribute to DAX 'bus' devices
21c75763a3ae device-dax: Add a 'target_node' attribute
664525b2d84a device-dax: Auto-bind device after successful new_id
8fc5c73554db acpi/nfit, device-dax: Identify differentiated memory with a unique numa-node
730926c3b099 device-dax: Add /sys/class/dax backwards compatibility
d200781ef237 device-dax: Add support for a dax override driver
89ec9f2cfa36 device-dax: Move resource pinning+mapping into the common driver
9567da0b408a device-dax: Introduce bus + driver model
51cf784c42d0 device-dax: Start defining a dax bus model
753a0850e707 device-dax: Remove multi-resource infrastructure
93694f9630b0 device-dax: Kill dax_region base
21b9e979501f device-dax: Kill dax_region ida"
1731408,2019-05-07 06:00:24 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1731410,2020-10-07 21:40:38 UTC,"Hi, Is this still an issue? Changing the status to incomplete."
1731410,2020-12-07 04:17:48 UTC,[Expired for pcsc-lite (Ubuntu) because there has been no activity for 60 days.]
1731416,2019-09-01 12:52:35 UTC,This is a kernel issue and most likely caused by bad hardware or buggy drivers.
1731417,2018-09-13 17:48:08 UTC,"these are all the files. there are 4 different lpstat files, corresponding to 1-initial situation, 2-after hp-setup 3-after printinf a file 4-after reboot"
1731417,2018-09-12 17:37:43 UTC,"Alberto, thanks for these files, but could you please also follow the instructions of comment #4, especially for the log file of cups-browsed?"
1731417,2018-09-12 16:46:33 UTC,Attached lpstat -v output
1731417,2019-02-20 12:50:44 UTC,I'm seeing this again in Cosmic with the following versions:
1731417,2018-09-12 16:46:48 UTC,Attached printers.conf
1731417,2019-02-20 12:54:45 UTC,"the ""-after"" files are (and logs) are taken after suspening and waking up the laptop, with the printer off."
1731417,2019-05-24 20:38:05 UTC,"Where can I find and download ""cups-filters (1.23.0-1)"" right now?"
1731417,2019-04-27 13:18:17 UTC,"According to the attached log files hp-setup has created a print queue with the same name as a queue created by cups-browsed, overwriting this queue. As cups-browsed removes all the queues it created when it shuts down, it also has removed this queue."
1731417,2019-05-20 20:02:32 UTC,This bug was fixed in the package cups-filters - 1.23.0-1
1731417,2019-05-23 11:07:23 UTC,"Where can I find and download ""cups-filters (1.23.0-1)"" right now?"
1731417,2019-05-24 20:08:32 UTC,"The 1.23.0-1 version got uploaded to the development of 19.10 (Eoan). For getting it into an already released Ubuntu version, a Stable Release Update (SRU) would be needed. But note that if you are still using 18.10 (Cosmic), that in a few months (end-July) the support for Cosmic ends, so SRUs for this version do not make much sense. So I recommend you to upgrade to 19.04 (Disco) and try whether the problem still persists for you and report back here."
1731417,2019-05-27 19:33:16 UTC,"I have now backported cups-filters 1.23.0 to Cosmic. To install it, go to my PPA"
1731417,2019-04-24 07:46:43 UTC,Note that the issue persist in 19.04
1731417,2018-09-12 16:46:13 UTC,Attached avahi output
1731417,2018-01-15 16:17:20 UTC,"Added all logs. After suspend the printer is gone and lpstat -v reports ""No destinations"""
1731417,2018-09-12 14:11:17 UTC,"I'm seeing this issue again as well, on Bionic with latest packages"
1731417,2017-11-10 18:02:40 UTC,"It seems the issue is due to suspend/resume.
After resuming the system, I noticed the following entries in CUPS access_log:"
1731417,2018-01-13 13:48:04 UTC,The issue persists on bionic
1731417,2018-01-14 20:06:34 UTC,Please do the following:
1731417,2018-01-16 09:31:18 UTC,"AFAICS from the cups-browserd_log, CUPS seems to be removing the printer when avahi doesn't see it anymore (because it's been turned off).
This didn't happen before, I would only install the printer once and it'd be there forever.
I think only avahi-discovered printers should be automatically removed."
1731417,2018-01-17 13:41:38 UTC,"Updated the bug title, as it's not really related to suspend/resume"
1731417,2018-02-01 09:12:25 UTC,@Till do you have any insight on this bug?
1731417,2018-03-23 12:25:56 UTC,Please run the command
1731417,2018-09-12 15:10:14 UTC,"Anyone who still has this problem, please follow the instructions of the comments #4, #18, and #22 in this bug report and attach all the files created by this. Thanks."
1731417,2018-03-23 13:14:42 UTC,Attached output with printer powered on and bonjour enabled.
1731417,2018-03-26 09:38:23 UTC,Please doi the following:
1731417,2018-03-26 09:43:45 UTC,"Sorry, I previously attached the output from the run with bonjour disabled. This is with it enabled."
1731417,2018-03-31 21:48:57 UTC,"Thank you very much for all the files. With this I could fix two bugs in cups-browsed which caused this problem.
Fixed version on the way to Bionic."
1731417,2018-03-31 23:43:55 UTC,This bug was fixed in the package cups-filters - 1.20.2-0ubuntu1
1731417,2018-09-10 15:09:05 UTC,"I have the same problem in Ubuntu 18.04.1 with a Laserjet CP1025nw... very annoying,,, is there a fix for that bug? How can I get it?"
1731417,2018-09-11 10:51:13 UTC,"Xavier, do you have cups-filters 1.20.2-0ubuntu1 on your machine (""dpkg -l | grep cups-filters"")?"
1731417,2018-09-11 11:31:16 UTC,"Hi Till, thanks for your answer. This is the result of dpkg:"
1731417,2018-03-26 07:04:05 UTC,"I can also confirm that if I disable bonjour, the printer no longer gets removed once it's turned off"
1731423,2017-11-10 09:51:11 UTC,"I just noticed that I was still running mint 18.1 - I could have sworn I had upgraded to 18.2 already, but I must have thought of a different machine. It's strange that the update manager didn't explicitly tell me that it could upgrade - I had to find that in a menu. I think earlier versions of update manager did tell you about newer distro versions in the main window."
1731439,2017-12-01 06:03:47 UTC,"Thank you zaneb for providing the commit link:https://review.openstack.org/#/c/483574
This commit fixes the issue"
1731439,2017-12-01 08:15:37 UTC,heat panel is split out to heat-dashboard. Retargeting to heat-dashboard.
1731450,2017-11-13 18:16:35 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1731454,2019-10-11 04:17:29 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1731454,2019-08-11 15:52:02 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Firefox since that time.
1731459,2019-08-22 17:18:14 UTC,This bug was fixed in the package sane-backends - 1.0.27-3.2ubuntu2
1731459,2019-08-21 18:17:42 UTC,"@Gunnar,"
1731459,2019-08-20 15:05:10 UTC,"and eoan, of course"
1731459,2019-08-20 15:05:05 UTC,"sponsored in bionic and disco, after removing ""~ppa"" from the changelog"
1731459,2019-08-20 08:18:12 UTC,"@Ananth, @Gunnar: I wanted to cross-verify that the patch works for LiDE 200 on bionic 18.04.3 - To do this I booted from a fresh bionic live usb stick and installed the patch from ppa in the live session. However what I discovered is that this does not work on bionic AND also does not work on a disco live session (which I tried then too to make sure it is not a live session related issue)."
1731459,2019-08-19 18:18:56 UTC,"@Ananth: That was disappointing, but thanks for letting us know. The version you mentioned for bionic has the very same patch as the disco and eoan versions, so the (attempt at a) fix is already in the PPA for bionic."
1731459,2019-08-19 13:34:40 UTC,@gunnarhj I have `CanoScan LiDE 100` scanner with this problem on 18.04.3 LTS (bionic). I tried the above mentioned PPA. It does not solve the issue.
1731459,2019-08-16 19:59:01 UTC,@CoderGuy: Excellent!
1731459,2019-08-08 20:14:54 UTC,"Let's give it a try to get this fixed. I have put proposed uploads in a PPA, and asked for sponsorship to have them uploaded."
1731459,2019-08-15 15:33:24 UTC,@Simon: That's indeed good news. Then we know that this update will make a difference. Thanks!
1731459,2019-08-15 14:36:09 UTC,No worries :) I now retried and it worked perfectly - thanks!
1731459,2019-08-15 13:00:42 UTC,"@Simon: That's because I had been lazy and not uploaded to disco (since it's identical with the package version in eoan). But I just uploaded to disco, so now (i.e. in a few minutes) you should be able to do:"
1731459,2019-08-15 07:28:38 UTC,"Hey Gunnar,"
1731459,2019-08-10 13:11:47 UTC,Sure. https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends
1731459,2019-08-10 12:17:44 UTC,"I have a device, could you share a link to the PPA?"
1731459,2019-08-30 15:26:37 UTC,"Hello dbazza, or anyone else affected,"
1731459,2019-07-26 11:37:28 UTC,"Btw it's not a black band but an inverted band, that is everything in the path of the band is inverted in color."
1731459,2019-05-05 17:05:13 UTC,"Unfortunately need to add that this issue persists for me in 19.04, in my case using a CanoScan Lide 200."
1731459,2019-08-16 19:23:15 UTC,"@Gunnar,"
1731459,2019-08-30 15:28:41 UTC,"Hello dbazza, or anyone else affected,"
1731459,2019-09-02 17:57:35 UTC,I had a major crash on mu Ubuntu Budgie system and had to reinstall using a Ubuntu Budgie 18.04.3 iso. I used the god old ppa from Rolf Bensch: ppa:rolfbensch/sane-git which again solved the problem on my Canon Lide 100 scanner. Version 1.0.28 of libsane seems to do the trick.
1731459,2019-08-30 20:34:59 UTC,"@vorlon, @gunnarhj:"
1731459,2020-02-15 15:32:59 UTC,"I tried the genesys backend from the official 1.0.29 release and it works fine. Please make sure that makes it into 20.04, which right now is still the broken 1.0.27 experimental version."
1731459,2020-02-15 15:18:23 UTC,"nevermind the previous comment, it's no regression it just does not work properly with the 120"
1731459,2020-02-15 15:10:01 UTC,"Note that the released fix caused a regression on Canon LiDE 120 scanners, see https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1863424"
1731459,2019-10-11 01:08:25 UTC,"@fermulator: Thanks for confirming and, of course, for pointing at the applicable upstream fix."
1731459,2019-10-11 00:00:00 UTC,"Certainly, the PPA from `rolfbensch` has the fix (start at https://gitlab.com/sane-project/backends/issues/7#note_125319290)."
1731459,2019-09-30 08:21:09 UTC,This bug was fixed in the package sane-backends - 1.0.27-1~experimental3ubuntu2.2
1731459,2019-09-28 11:46:15 UTC,"On 2019-09-28 11:27, Jaroslav Hron wrote:

> I can report that the new packages in bionic-proposed work without
> any problem.
> Scanner- canon LiDE 200 on ubuntu 18.04.
"
1731459,2019-09-28 09:27:59 UTC,"I can report that the new packages in bionic-proposed work without any problem.
Scanner- canon LiDE 200 on ubuntu 18.04."
1731459,2019-08-30 17:48:04 UTC,"At last the change is in -proposed, so it's time for the real verification."
1731459,2019-09-17 23:17:23 UTC,"my scanner = Canoscan LiDE 100
couldn't use this scanner on 18.04 at all without getting a thick black line in the output.
not a massive issue so far as it still worked ok on a 16.04 machine we've got.
After checking back into this conversation today i tried to scan again on 18.04, issue was not resolved but then i tried the ppa mentoned above in comment #77
sudo add-apt-repository ppa:rolfbensch/sane-git
sudo apt-get dist-upgrade
tried again and bingo! black line has gone.
Thank you to everyone involved!"
1731459,2019-09-09 09:31:22 UTC,This bug was fixed in the package sane-backends - 1.0.27-3.2ubuntu1.1
1731459,2019-09-06 01:31:13 UTC,"A week has soon passed since the new version was built in bionic-proposed, but no final verification yet. @CoderGuy, any chance that you can test the bionic-proposed packages? Anybody else?"
1731459,2019-09-03 13:45:15 UTC,As regards the autopkgtest regression reports in comment #75 and #76:
1731459,2019-09-01 00:17:35 UTC,"All autopkgtests for the newly accepted sane-backends (1.0.27-3.2ubuntu1.1) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1731459,2019-08-31 21:33:13 UTC,"All autopkgtests for the newly accepted sane-backends (1.0.27-1~experimental3ubuntu2.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1731459,2019-08-31 15:43:36 UTC,"Thanks for your efforts @gunnarhj. I'm glad that the fix helps many users. If I come across any hack that solves the issue on my machine, I'll update here."
1731459,2019-08-31 10:29:51 UTC,"Thanks for testing again, @Ananth. Then we'll have to notice that the fix does not help in all cases, unfortunately."
1731459,2019-08-31 09:02:00 UTC,@gunnarhj I tested the ppa and bionic-propsed a machine with fresh clean install of bionic with CanoScan LIDE 100. The issue is *not* fixed on this machine.
1731459,2019-09-09 09:31:28 UTC,"The verification of the Stable Release Update for sane-backends has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1731459,2019-04-05 12:32:09 UTC,"Hi, my system is a Xubuntu 18.10.
The weird thing is, now it works! I don't now why. I restarded the system several times before without success, but now, everything seems to be good!
Maybe beacause I always restarted with the scanner on the USB port..
After that I pluged out the scanner and waited several starts. When I read your message now, I pluged it in again and it worksnow! Thanks."
1731459,2019-04-04 18:14:41 UTC,The PPA also worked for me (Ubuntu 18.04)
1731459,2019-04-03 13:59:02 UTC,"This ppa didn't work for me. After the update I have still this black stripe in the scan. Scanner is a ScanLide 100.
Very disappointing."
1731459,2018-05-08 21:33:35 UTC,"This problem has just arisen, with my Canon Lide 200, on a recently installed Ubuntu 18.04. The scanner worked fine with Ubuntu 16.04 and still works under Winblows."
1731459,2018-05-04 17:57:34 UTC,"It is still the same problem under (x)ubuntu 18.04 and Scanlide 100.
libsane version is here 1.0.27-1.
The whole problem is very disappointing!"
1731459,2018-04-01 07:15:03 UTC,"Excellent instructions, but too difficult for a newbe. May I hope that some official ubuntu update will fix the bug?"
1731459,2018-03-31 12:25:36 UTC,@ramas
1731459,2018-03-26 18:11:17 UTC,@ramas
1731459,2018-03-20 22:15:24 UTC,This bug is serious for me as I use my scanner everyday.
1731459,2018-03-16 02:25:58 UTC,"@genti
On 16-Mar-2018 the last commit here was 9 months ago and this still shows the rewind:
https://gitlab.com/sane-project/backends/commits/master/backend/genesys.c
So, where did you commit your precious fix?
How to achieve that this fix gets picked up by future ubuntu updates and upgrades?"
1731459,2018-03-12 21:46:14 UTC,"Yes, it's working for me with 1.0.27. I compiled from the same Git source like you. I own a CanoScan LIDE 200."
1731459,2018-03-12 01:27:24 UTC,"@genti (pashol), are you sure it's fixed? I see no evidence of a fix according to history:
 * https://gitlab.com/sane-project/backends/commits/master/backend/genesys.c"
1731459,2018-03-07 00:35:29 UTC,It is actually fixed now. If you build 1.0.27 from Git it'll be ok.
1731459,2018-03-06 23:55:47 UTC,"This is also reported on the SANE project bug report website, which includes the solution to fix this issue: https://alioth.debian.org/tracker/index.php?func=detail&aid=315752&group_id=30186&atid=410366"
1731459,2018-02-12 20:46:31 UTC,Since the update to ubuntu 17.10 the black vertical central line appears on my PC and Laptop with any scanning software independently of the configurations. The scanner works very well under Windows 10. I'm still waiting for a solution!
1731459,2018-01-16 16:51:45 UTC,"Sorry for double posting, just some demo images to present the problem."
1731459,2018-01-07 10:27:16 UTC,Very interesting fact:
1731459,2017-12-26 23:47:02 UTC,Also I went through all changes made between 1.0.25 and 1.0.27 with regards to genesys in general and more specifically gl847 (which is the chip CanoScan LiDE 100 is using) looking for anything related to colour. The only thing I was able to find was this patch changing reallocation of gamma tables: https://anonscm.debian.org/cgit/sane/sane-backends.git/commit/backend/genesys.c?id=5edb87f9ac950473f8c3a57b4071c970887d8440
1731459,2017-12-26 23:35:14 UTC,I did some testing with different colours. Maybe this helps to pinpoint what's actually going wrong.
1731459,2017-11-19 12:47:22 UTC,"Me too, works on Windows XP and Xubuntu 16.04. Not on Xubuntu 17.10 with libsane 1.0.27-1~experimental2ubuntu2.1"
1731459,2017-11-19 12:50:06 UTC,Here's the output of simple scan. (all front ends the same)
1731459,2019-04-04 17:42:47 UTC,"And you are using one of the supported systems?
I am running Ubuntu 18.04 and the ppa does the trick when I am testing."
1731459,2018-05-13 09:35:39 UTC,same problem with
1731459,2018-07-21 10:04:59 UTC,"Since ubuntu 17.10 I had always to switch to Windows 10 for using my Canon LIDE 100 because of the vertical central black line.
Before deciding to change finally my scanner, i looked again to this page and saw the remark of genti in date of 2018-03-07.
Under ubuntu 18.10 I realized the following steps without a new start:
   1) uninstall by synaptic: sane, xsane, xsane-common
   2) reinstall by synaptic: sane, xsane, xsane-common
Now my LIDE 100 is working fine using gscan2pdf without black line as the years before 17.04!
I don't know which of the three reinstalled applications resolved the problem."
1731459,2017-12-14 05:07:59 UTC,"Workaround is to install sane-backends-1.0.25 from the sane Project Site.
This version seems to work properly with LiDE 200. I did not realise any side effects at the moment using 1.0.25."
1731459,2018-08-03 19:25:38 UTC,"After uninstalling from terminal sane, xsane, xsane-common and reinstalling them the black bar just became a coloured bar."
1731459,2019-03-24 18:34:58 UTC,"Adding this ppa should resolve the issue (as it includes the patch 4354fc7f):
ppa:rolfbensch/sane-git"
1731459,2019-03-11 14:57:28 UTC,"Also note:
https://gitlab.com/sane-project/backends/merge_requests/34#note_141760446

> applied the patches 4354fc7f to sane-backends_1.0.27-1~experimental3ubuntu2 (Ubuntu 18.04 LTS) to build the package for this distro.
"
1731459,2018-07-21 17:42:28 UTC,"I'm very sorry, but I was only lucky for about 10 correct clean scans after my above described reinstalling. Then the black line reappeared immediately after scan before the correction by the software (repositioning). So the result was always ok. But then I got two errors:
   1) Warning running unpaper: out of deviation range - NO ROTATION
   2) Error running unpaper: [image@0x561bb2222ea80] Using AVStream.codec to pass codec parameters
      to muxers is depreciated, use AVStream.codecpar unstead.
      [image@0x561bb2222ea80] Encoder did not produce proper pts, making some up.
The result of the scan was then shifted horizontally about 5 cm on my paper towards the left and this didn't move even changing all various parameters. The black line disappears but the page in not complete.
So for the moment I have to go back to Windows only for scanning.
There seems an error in unpaper, software applicated immediately after the scan, because I can see the original scan with black line just before."
1731459,2019-03-11 14:55:15 UTC,"https://gitlab.com/sane-project/backends/issues/7 has been fixed!
Now to pull into ubuntu repos and backmerge fore LTS please."
1731459,2019-03-04 12:11:46 UTC,"Hi everyone,
I solved the problem for me very practicaly. I create a virtual machine (VirtualBox) with an xubuntu 16.04 to scan my documents. Yes ist takes more drivespeed then patching the code, but I think it is much easier then everything else.
It is a shame that older hardware is treated like this! The scanner is still absolutely sufficient for most of the uses!"
1731459,2019-02-28 18:38:43 UTC,Hi guys
1731459,2019-02-13 12:48:25 UTC,"Добрый день! У меня RICOH Aficio SP 100su, как мне это МФУ запустить на Mint 19.01!"
1731459,2019-01-16 21:32:32 UTC,Same problem with CanoScan Lide 200 after upgrading to Ubuntu 18.04 (before it worked fine).
1731459,2019-01-16 21:29:16 UTC,"Hi everyone,"
1731459,2018-12-01 08:31:26 UTC,Slightly updated patch instructions from above.
1731459,2017-11-19 12:43:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731459,2018-10-21 13:54:00 UTC,Same problem in Ubuntu 18.10
1731459,2018-10-06 04:19:24 UTC,"The attachment ""genesys.c.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1731459,2018-10-05 20:58:37 UTC,"FYI, @ramas (slocascio), fermulator (fermulator) and Alec B (castegere) instructions - slightly updated and automated for Ubuntu 18.04.1 (libsane1_1.0.27-1~experimental3)."
1731459,2018-10-01 18:08:55 UTC,"The checkin comment refers to flags - does that mean that there's some
configuration that can be set for our scanners to avoid this behavior?"
1731459,2018-09-30 14:59:35 UTC,Found one! upstream: https://gitlab.com/sane-project/backends/issues/7
1731459,2018-09-22 19:14:20 UTC,I've recently had the same problem of vertical black stripes on scans from my Canon imageCLASS MF244DW under Ubuntu 18.04.1. Compiling and installing sane-backends from https://github.com/kkaempf/sane-backends solved the problem.
1731459,2018-09-03 00:16:50 UTC,which is the correct project to submit this bug to upstream?
1731459,2018-08-12 21:32:21 UTC,"how do we get this fixed upstream?
submitted: https://salsa.debian.org/debian/sane-backends/merge_requests/1"
1731459,2018-08-14 02:26:26 UTC,couldn't overwrite the existing
1731459,2018-11-29 20:11:20 UTC,Also having the same problem. Compiling from git as per instructions didn't solve for me either. Not sure what I've done wrong
1731459,2018-08-14 02:31:23 UTC,(had to move the conflicting file)
1731467,2017-12-07 17:43:39 UTC,This bug was fixed in the package linux - 4.4.0-103.126
1731467,2017-12-07 17:43:17 UTC,This bug was fixed in the package linux - 4.10.0-42.46
1731467,2018-01-10 01:35:55 UTC,This bug was fixed in the package linux - 4.13.0-25.29
1731467,2017-11-29 15:16:09 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1731467,2017-11-28 17:47:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'."
1731467,2017-11-28 17:47:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1731467,2017-11-28 08:50:03 UTC,merged: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=1b1356e92b7ee81f7a83a7c5a67272f5ecbc3d38
1731467,2017-11-14 16:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1731467,2017-11-15 14:01:41 UTC,"The only relevant log files that can be provided for this issue is a HCI
trace. It is in .snoop format therefore can be viewed in wireshark."
1731467,2017-12-07 17:42:36 UTC,This bug was fixed in the package linux - 4.13.0-19.22
1731469,2019-03-05 13:36:13 UTC,Need more info on this
1731469,2019-08-07 19:03:05 UTC,UI has been deprecated
1731470,2017-11-10 12:18:36 UTC,is anybody know how to fix it? i dont have a decktop anymore...after the ALT+F2 i have input the command: plasmashell
1731470,2017-11-13 18:24:21 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1731470,2017-11-13 18:47:38 UTC,Not a documentation bug.
1731476,2018-04-07 09:55:31 UTC,"I do have the same problem,but i can cancel it."
1731489,2017-11-20 10:26:51 UTC,"Looks like it is Wayland (today).
For some strange reason it is behaving itself today as well."
1731489,2017-11-10 17:03:05 UTC,Do you use Wayland (the new default) or Xorg (the old choice)?
1731489,2017-11-10 17:24:53 UTC,"It is a server install with IIRC the ubuntu-desktop package.
So I think it is Wayland - certainly rather different from the previous versions."
1731489,2017-11-11 22:12:46 UTC,"David, friendly ping. Does
  echo $XDG_SESSION_TYPE
confirm that you're running Xorg (x11)?"
1731489,2017-11-23 16:19:59 UTC,Another related fubar.
1731489,2017-11-10 17:41:16 UTC,"The proper way of detecting Wayland or Xorg is probably:
echo $XDG_SESSION_TYPE"
1731489,2017-11-22 18:59:58 UTC,"Okay, this is a bug that occurs in Xorg(X11) then, just as we previously thought."
1731489,2017-11-22 15:16:32 UTC,"It seems that if you create a terminal window by typing CTRL+ALT+T everything is fine.
If you create one by right-clicking on the background and selecting 'Open terminal' the height changes."
1731495,2018-03-17 14:07:42 UTC,I've tried with 5.2.6 from your PPA and the problem is still there.  Wasn't sure where to get 5.2.8 from as I'm running 17.10.  Is there an Ubuntu source or should I use the Oracle site?
1731495,2018-03-18 20:33:25 UTC,"Hello, please try 5.2.8 now in my ppa :)"
1731495,2018-03-19 11:42:28 UTC,"Sorry, 5.2.8 doesn't fix it."
1731495,2018-03-20 11:51:39 UTC,Can you please open an upstream bug report and link it here?
1731495,2018-03-23 16:42:48 UTC,"yes, upstream Oracle website (right now down for maintenance)"
1731495,2018-03-24 12:46:28 UTC,Raised upstream as https://www.virtualbox.org/ticket/17636.
1731495,2019-05-31 13:28:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731495,2020-09-07 14:14:19 UTC,I'm now running virtualbox 6.1.10 on Kubuntu 20.04 and the problem seems to have been fixed.
1731495,2018-03-15 16:37:38 UTC,please test vbox 5.2.8 or similar
1731495,2018-03-23 15:55:46 UTC,"Sorry, not sure what you mean by an upstream bug report.  Do you mean via the Oracle website or somewhere else on Launchpad?"
1731500,2017-11-13 18:13:55 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1731500,2017-11-21 01:50:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731502,2019-03-18 21:04:17 UTC,"Jorge, try this:"
1731502,2017-11-13 18:08:29 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1731502,2017-11-13 18:32:17 UTC,Thanks for filing this bug in Ubuntu.
1731502,2019-03-18 20:53:50 UTC,"Thank you, Andreas for providing the information and logging the bug. However, in my case, I'm connected on a wired network so I don't understand why I'm getting this bug."
1731505,2017-11-16 15:25:09 UTC,"Noted. This has appeared already elsewhere too, but will require some work to implement in the backends. At least systemd has no way to denote that particular setup currently."
1731505,2018-02-14 18:09:21 UTC,I'm working on this in systemd upstream; should get it working soon.
1731512,2018-01-09 11:12:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731512,2018-04-07 00:06:42 UTC,"in .config/lxpanel/Lubuntu/panels/panel i set network=1 and i now have only one, on reboot as well"
1731516,2019-05-11 04:17:26 UTC,[Expired for BleachBit because there has been no activity for 60 days.]
1731516,2019-03-12 03:52:15 UTC,"If this still exists in the latest version (BleachBit 2.1), please file bug report in the new home: https://github.com/bleachbit/bleachbit/blob/master/CONTRIBUTING.md . If this bug no longer exists, it would be nice if you wrote a note to confirm."
1731516,2018-02-24 03:15:00 UTC,"I uninstalled that .deb (the one I packaged) and installed BleachBit 1.15 from the Ubuntu universe repository, and it cleaned APT too."
1731516,2018-02-23 00:14:02 UTC,"I tested the latest BleachBit (a bit newer than 1.19 beta) on Ubuntu 16.04. When I use ""sudo python bleachbit.py"" my diagnostic information looks like yours (such as LOGNAMEE, USER, and SUDO_UID). It does seem like you are root."
1731516,2018-02-23 04:32:12 UTC,"With a genuine Bionic install, libselinux1/libsepol1/libsemanage1 are required dependencies for many apps. But selinux is not installed by default (on my systems at least, but some users can need it with special use cases)"
1731516,2017-12-23 15:17:33 UTC,"BleachBit version 1.15
GTK version 2.24.31
local_cleaners_dir = /home/oem/.config/bleachbit/cleaners
locale_dir = /usr/share/locale/
options_dir = /home/oem/.config/bleachbit
personal_cleaners_dir = /home/oem/.config/bleachbit/cleaners
system_cleaners_dir = /usr/share/bleachbit/cleaners
locale.getdefaultlocale = ('en_US', 'UTF-8')
os.getenv('DESKTOP_SESSION') = None
os.getenv('LOGNAME') = root
os.getenv('USER') = root
os.getenv('SUDO_UID') = 1000
os.path.expanduser('~') = /home/oem
platform.linux_distribution() = ('Ubuntu', '18.04', 'bionic')
platform.platform = Linux-4.14.0-13-generic-x86_64-with-Ubuntu-18.04-bionic
platform.version = #15-Ubuntu SMP Mon Dec 18 19:08:44 UTC 2017
sys.argv = ['/usr/bin/bleachbit']
sys.executable = /usr/bin/python
sys.version = 2.7.14+ (default, Dec  5 2017, 15:17:02)
[GCC 7.2.1 20171205]
__file__ = /usr/share/bleachbit/bleachbit/Diagnostic.pyc"
1731516,2017-12-23 15:12:21 UTC,dino99: Could you please send me the system information in BleachBit under Help - System Information? You can post it here or email it to me directly.
1731516,2017-12-23 07:09:02 UTC,Also get that error with 1.15-2 (bionic) each time i use bleachbit 'as root' from the Applications -> System Tools menu
1731516,2017-12-22 18:05:53 UTC,Are you running with sudo/root permissions?
1731516,2018-02-24 03:09:09 UTC,I installed Ubuntu Bionic 2018-02-22 from http://cdimage.ubuntu.com/daily-live/20180222/ . This was a clean install
1731517,2017-11-13 20:34:38 UTC,For anyone else reading this...  I realize this is a feature request in the future milestone on git-ubuntu to be able to grok either and perhaps search with a list option for more discovery...
1731517,2017-11-10 20:33:44 UTC,"Thinking about it now, it may be even more useful this way."
1731517,2017-11-13 07:56:48 UTC,"What if, upon failure to find a particular source package on ""git ubuntu clone"", we did some heuristic guessing and if we get a hit, suggest in a ""X is provided by source package Y\nDid you mean: git ubuntu clone Y?"" type error message? The heuristics could include some combination of binary package namespace search, substring match, and ""dpkg -S $(which ...)""."
1731517,2017-11-10 20:00:17 UTC,Ah! I misunderstood your request -- I thought you were asking for a CLI subcommand to check if something had been imported or not.
1731517,2017-11-10 19:41:17 UTC,"Sometimes a package name is different from source package name, hence when you do"
1731517,2017-11-10 18:15:41 UTC,"Interesting idea. It's really a Launchpad query, not related directly to the git-ubuntu tooling. I mean, worst case, try to clone it and if it fails, then ... it's not there :)"
1731517,2017-11-13 12:29:46 UTC,Could be useful too.
1731522,2017-11-28 05:30:07 UTC,The bug report here is likely inaccurate. I don't exactly know where the problem is.
1731522,2017-11-28 05:31:48 UTC,"Additionally, I also looked at my nsswitch.conf file, the host line in it is:"
1731522,2017-12-04 00:44:34 UTC,This seems to be a duplicate of #1728560
1731522,2017-12-04 01:44:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731522,2018-01-26 19:48:29 UTC,"I can confirm this problem.  'dig' works because by default it's only asking for A records; but applications on ipv6-enabled clients will ask for both A and AAAA records, and if I query AAAA for this name, the response is too big to fit in a udp packet:"
1731522,2018-01-26 20:01:46 UTC,According to https://github.com/systemd/systemd/issues/6520 this can be worked around by setting DNSStubListener=yes in /etc/systemd/resolved.conf.  This is disabled by default due to <https://github.com/systemd/systemd/pull/4061>.
1731522,2018-04-05 06:06:27 UTC,"Steve, Bionic still has the default (commented-out)"
1731522,2018-04-05 08:02:39 UTC,"This has totally slipped my radar, I'm sorry."
1731522,2018-04-05 20:51:48 UTC,"Thanks Dimitri, greatly appreciated. I haven't found many problems in my testing of Bionic, but this is the juiciest one so far."
1731522,2018-04-13 11:24:24 UTC,This bug was fixed in the package systemd - 237-3ubuntu8
1731524,2019-01-08 19:11:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731524,2019-11-03 22:39:59 UTC,"I confirm it's the option ""freedesktop.org tray icon base on dbus"" in ""addon --->advanced"" that cause the problem .  running  fcitx-config-gtk3 to unchecked it   can fix the problem."
1731524,2018-04-27 17:01:26 UTC,I is not a MATE bug. I have the same on LXDE too
1731524,2018-04-19 13:09:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731524,2018-04-27 21:11:18 UTC,"Ok, fcitx not longer a problem since it gets removed during full installation process. Fcitx only exists in Live USB version."
1731524,2018-04-27 07:02:18 UTC,This CRITICAL bug has advanced to MATE 18.04 LTS release.
1731524,2018-04-27 07:09:55 UTC,"I am new to the site, I changed the status to 'Fix Released' by mistake. My bad."
1731531,2017-11-13 08:20:51 UTC,I think this might be one of the edge cases we considered before that we couldn't remember the detail more recently.
1731543,2017-11-10 20:36:13 UTC,I ended up kill -9'ing the process. and eventually it went on (not even recording an error).
1731544,2017-11-16 21:02:44 UTC,"Yep, I have one test that fails: testing.functional.test_restart.RestartTestWithoutEncryption.test_ignore_double_snapshot. It appears to be failing because gtar isn't present on my system."
1731544,2017-11-17 11:51:51 UTC,"Hmmm, that's odd.  My failing test is:
testing.unit.test_gpginterface.GnuPGTests.test_attach_fhs
but only if run with the other tests.  Runs fine by itself."
1731544,2017-11-15 21:51:39 UTC,"I have fixed this in the trunk by removing the offending files from testing/testfiles.tar.gz.  It turns out that the filename used is not valid UTF8 and 10.13 MacOS no longer allows this, nor should we.  Unicode is bad enough without intentionally breaking it!"
1731544,2017-11-11 13:12:45 UTC,fasteners is in the basic README.  Might want to start there.
1731545,2018-06-28 11:11:07 UTC,This bug is still affecting at least one BootStack customer.
1731545,2018-01-29 04:17:27 UTC,[Expired for horizon (Ubuntu) because there has been no activity for 60 days.]
1731545,2017-11-29 19:50:53 UTC,"The version of openstack deployed is ocata, however this was also tested on pike with the same result"
1731545,2017-11-29 11:40:47 UTC,Please also provide details on the version of openstack deployed; will determine whether this is a v1 or a v2 issue in the dash.
1731545,2017-11-29 11:40:16 UTC,Moving to distro; not a charm specific issue.
1731545,2017-11-29 19:51:25 UTC,"Pardon, that should be newton, not pike in the above comment"
1731550,2017-11-11 04:00:17 UTC,"I don't think that Ubuntu developers can do anything with it, they will not disable propper handling of USB dongles to allow PulseEffects work properly and solve https://github.com/wwmm/pulseeffects/issues/99"
1731550,2017-12-20 08:50:04 UTC,"This sounds like a valid bug still, but low priority if PulseEffects is not part of standard Ubuntu. So most people will never notice. We're working on the assumption that many more people want USB and Bluetooth devices to work well, than PulseEffects."
1731550,2017-11-11 03:58:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731554,2018-06-15 22:02:05 UTC,"note the intention here is to *not* break the hash abi. There are two changes that do, but they are actually unrelated (I need to clean up my MP, but ENOTIME): 1) branch name in the commit messages (this gets dropped, becuse the import functions no longer know about the branches) and 2) once we decide in the spec how to handle the order of import tag creation (e.g., if something is actually published in ubuntu before debian, we might naively expect the ubuntu one to be import and the debian one to be reimport, but that's not how the code works currently)."
1731554,2018-06-15 22:14:14 UTC,"err, wrong on that last sentence, because the applied branches can be at different history points than the unapplied branches, so it's not purely based upon the spi. I wonder if we can be smarter here, but I'm not context-switched enough."
1731555,2020-09-24 13:09:55 UTC,This was fixed in commit 061371a.
1731556,2017-11-11 01:53:22 UTC,"usually the fault lies with things that SB-ALIEN does, not the evaluator.
See also https://bugs.launchpad.net/sbcl/+bug/992362 and https://bugs.launchpad.net/sbcl/+bug/734259"
1731556,2017-11-11 23:28:54 UTC,"Well, though this works with sb-eval contrary to the case of using sb-fasteval. That reminds me of another (past) issue that was alike at sb-fasteval only: https://bugs.launchpad.net/sbcl/+bug/1722715"
1731563,2019-08-28 12:23:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731563,2017-11-13 09:36:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1731566,2017-12-11 15:34:59 UTC,"I'll try to reproduce this locally to understand what is going on, sounds bad based on the description."
1731566,2017-12-13 12:06:18 UTC,Re: But the inner PV is only for the guest to use - no?
1731566,2017-12-11 15:34:13 UTC,"> KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.
"
1731581,2017-11-11 00:26:41 UTC,I just noticed a side-effect which may help in debugging this issue...
1731581,2017-11-13 09:33:49 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1731581,2017-12-10 03:01:34 UTC,Here is the Bugzilla bug...
1731587,2017-11-11 00:47:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731587,2017-11-11 00:49:39 UTC,"This is random for me as well, but I have received this error while watching Netflix in Google Chrome."
1731587,2018-03-22 07:15:49 UTC,I get this bug ofter when I am away from the computer: on my return my session is dead :/
1731600,2017-11-16 15:23:16 UTC,"Nice catch. This is a bug in netcfg, reassigning."
1731605,2020-09-11 14:50:33 UTC,"Hi - thanks for reporting this bug, I've linked it to Inkscape's new bug tracker on GitLab, and closed it here."
1731606,2018-01-03 06:55:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731607,2017-11-19 14:17:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731608,2018-06-29 09:37:59 UTC,From https://bugs.launchpad.net/catfish-search/+bug/1731608
1731608,2018-02-02 10:25:31 UTC,I am unable to reproduce.. on today's ISO catfish happily finds the document test.hidden.txt in folder dave.p
1731608,2018-08-15 15:59:02 UTC,"There is a catfish upload in the bionic-proposed queue referencing this bug but this is not on track for inclusion in bionic-proposed. This bug lacks an SRU bug template. Please either update all bugs referenced in the changelog to include SRU templates (including test cases), or reupload dropping the bug references to the individual bugfixes and include only the reference to the microrelease exception request (https://bugs.launchpad.net/ubuntu/+source/catfish/+bug/1782735)."
1731608,2018-01-28 14:22:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731608,2018-08-13 08:32:26 UTC,"Since this bug is mentioned in the changelog of the new catfish SRU to bionic, please fill in the required SRU information into the description."
1731608,2018-06-30 02:10:36 UTC,Sean Davis referenced this bugreport in commit 8b3fe1149562195b33f73825db21e231caa5aea7
1731608,2018-06-30 02:10:54 UTC,Fixed in the above commit.
1731608,2018-07-20 06:23:52 UTC,This bug was fixed in the package catfish - 1.4.6-0ubuntu1
1731608,2018-08-15 15:58:55 UTC,"An upload of catfish to bionic-proposed has been rejected from the upload queue for the following reason: ""bugs linked in the changelog do not have SRU templates and it's unclear they should; https://bugs.launchpad.net/ubuntu/bionic/+source/catfish/+bug/1646714/comments/6""."
1731614,2018-05-23 11:24:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731628,2019-05-17 08:32:15 UTC,This is really sad. This app is completely broken and nobody cares.
1731628,2018-11-10 20:50:34 UTC,"18.04.1
Still can't add a caldav calendar.
Wonder why the importance is low, given that it makes the appliation unusable for many of us."
1731628,2018-11-16 00:00:19 UTC,I got the same behaviour in Ubuntu 18.10
1731628,2017-11-21 10:30:33 UTC,"I have a similar problem with Ubuntu 17.10. After pasting my ICS URL (from Zimbra), the Add button stays grayed out. If I use the read-only URL (offered by Zimbra, with an .html at the end) it adds the calendar but no event is shown. And when clinking at the calendar it opens it at my browser. Besides this it keeps crashing without warning in some random situations."
1731628,2017-11-21 10:16:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731628,2017-11-13 09:29:01 UTC,"On 16.04 when adding using ""add web calendar"" and copying the url it directly prompts for username/password"
1731628,2017-11-13 09:28:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1731628,2017-11-11 13:57:38 UTC,I can add the same calendar in evolution without issues.
1731628,2018-08-14 13:31:43 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=791749
1731628,2018-07-16 08:00:01 UTC,still not possible in ubuntu 18.04 with calendar 3.28.2. I also tried a posteo calendar.
1731640,2018-01-14 12:14:02 UTC,"Hi,"
1731640,2018-07-09 11:19:30 UTC,"No activity after a while - I think this is about the time remaining estimate, so not a bug, a feature request/improvement."
1731640,2018-12-06 16:03:50 UTC,NB: I could fix this by using the time estimate from ddrescue for supported versions.
1731640,2019-12-13 11:28:08 UTC,"I've fixed this, and the fix will be available in the next version, 2.1.0."
1731640,2020-04-27 17:29:01 UTC,Fixed - ddrescue's time remaining estimate is now used when on a version that provides an estimate.
1731653,2019-12-09 18:21:03 UTC,"I'm not sure what you refer to:
* tooltips are translatable
* Libary feature buttons are translatable
* compact button labels like MIXER, AUX, BROADCAST, VINYL can be considered 'global' IMO, also translations would screw up skin layouts"
1731653,2019-12-09 17:31:25 UTC,"When we agree this affects the skin settiings menu only, a separate skin settings widget would solve the issue for me."
1731653,2017-12-11 06:26:02 UTC,I'm not sure it is feasible to implement this and finish everything else before the 2.1 beta release. Is using icons where possible good enough for 2.1? That should leave most text in skins in the skin settings menus.
1731653,2017-11-12 19:18:16 UTC,Moving this back to High priority because it has to be fixed before string freeze.
1731653,2017-11-11 18:01:50 UTC,"I partly agree this is a bug:
Yes: for the skin settings menus in Deere and Tango
No: most buttons in skin itself
I don't agree it's high priority."
1731653,2017-11-11 18:17:10 UTC,"I agree that buttons are preferable to text outside of the skin settings menu. Graphic design is not one of my strengths, but if you'd like to make icons to replace text in Deere, that would be welcome."
1731653,2019-12-09 17:43:51 UTC,There is more text in the skins than just the skin settings menus. So that wouldn't fully solve the problem.
1731656,2017-11-13 10:12:43 UTC,"well, the discussion was not to automatically merge the translations to git repo, but to merge translations in jenkins workplace on every build."
1731656,2017-11-13 10:13:44 UTC,"I mean workspace, not workplace ;)"
1731656,2018-01-28 22:37:43 UTC,Im fine with that.
1731656,2018-01-28 13:03:12 UTC,"My plan for this is :
- Automatically update interface and installer translations from transifex before build for CI builds (appveyor and travis-ci)
- Automatically update interface and installer translations before nightly builds on jenkins
- DO NOT update automatically translations before release builds (release branch, 2.1 for example). For release, we want a stable translation (not necessarily the last available) manually validated and pushed into git."
1731661,2019-08-11 16:14:46 UTC,"I too am looking for the implementation of this backend. It's been more than a year. Is there any hope it can be looked into?
I can help test if needed."
1731661,2019-08-11 22:04:30 UTC,"Guy,"
1731661,2020-02-19 12:27:24 UTC,"@Kenneth-Loafman, will the team drive (now called: shared drive) support be added at all?
I would really like to know just a timeline or status for this."
1731661,2020-02-19 16:13:22 UTC,"Sorry, I need someone to step up and handle this.  I don't have the time right now."
1731661,2020-04-17 14:22:06 UTC,"Hi,"
1731661,2018-04-13 10:44:09 UTC,PyDrive now supports Team Drives (https://github.com/gsuitedevs/PyDrive/pull/111). This means adding support for Team Drives should be pretty straight forward.
1731669,2021-01-22 10:21:12 UTC,https://bugs.launchpad.net/ubuntu/+source/time/1.9-0.1
1731670,2018-03-03 02:44:02 UTC,"I have not been able to reproduce this, but will look into it as soon as my new dev system is setup (Intel NUC with Windows 7/8.1/10 multiboot)."
1731670,2019-02-08 11:06:50 UTC,I had the same problem.
1731679,2017-11-14 20:53:17 UTC,You may need to run the following from a terminal:
1731679,2017-11-20 01:30:03 UTC,This change was made by a bot.
1731679,2017-11-11 20:00:04 UTC,This change was made by a bot.
1731680,2017-11-13 10:27:22 UTC,"Hi, thanks for the report. This is likely a local configuration with your quake3 engine of choice (ioquake3) and not an issue with your data package nor with game-data-packager. It would be helpful for further diagnosis if you could report whether you get a different framerate with different data, or what framerate you are expecting: I'm guessing you are suggesting that 8-10fps is too slow for your machine, but you haven't made that clear."
1731680,2017-11-19 00:52:58 UTC,"Yes, it's too slow for my machine.
In Setup->System->Graphics>Driver_Info I see ""EXTENSIONS: Not available (core context, fixme)."
1731684,2017-11-12 16:11:14 UTC,This is the intended behaviour; not completely opaque.
1731684,2020-09-14 07:47:25 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1731685,2017-12-31 23:10:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731686,2017-11-18 21:54:44 UTC,"How do I find those unofficial packages not provided by Ubuntu, as I would love to upgrade to 17.04:"
1731686,2017-11-18 21:59:10 UTC,"Would this mean, that I have to wait for another LTS to upgrade (I'm on 16.04, so I miss 16.10)?"
1731689,2017-11-20 22:37:56 UTC,"For what it's worth, the following workaround has been successful for me on x64 installs:
1). Install the portable version of Mixxx from https://portableapps.com/node/23093
2). Install the latest x64 beta of 2.1
3). Copy the contents of the beta folder into the portable folder, for example copy c:\program files\Mixxx to A:\MixxxPortable\App\Mixxx\"
1731689,2018-01-28 13:17:10 UTC,"We have everything needed to launch Mixxx as a portable application, using command line parameters --resourcePath and --settingsPath."
1731689,2018-01-28 16:10:44 UTC,Resources are automatically taken from a res subdirectory if it exists in the same location than the Mixxx executable.
1731689,2018-08-15 23:37:59 UTC,https://github.com/mixxxdj/mixxx/pull/1780
1731693,2017-11-14 21:08:03 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1731693,2017-11-11 22:30:06 UTC,This change was made by a bot.
1731693,2017-11-28 10:02:52 UTC,"I've made some tests meanwhile with the latest 4.14 ubuntu kernel package, but could not reproduce the bug with the tests under that kernel so far, but that does not really and realiably mean anything, because"
1731700,2017-11-11 23:30:07 UTC,This change was made by a bot.
1731703,2017-11-13 09:22:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1731704,2018-01-02 20:44:35 UTC,I agree that's a weak error message.  I was testing with external drives and didn't reproduce this.  But I'm testing on Ubuntu.  I wonder if the way Fedora mounts drives is conflicting with what Deja Dup expects...
1731704,2020-08-14 16:38:20 UTC,I believe this is fixed in 42.2 — selecting a drive via Local Folder should switch you to a mountable drive setup.
1731704,2018-01-06 07:37:44 UTC,"Oh, I figured it out: I had set my storage location to ""Local Folder"", setting it to the path to the backup directory on the external drive. When I change the storage location to be the drop-down box's entry for my external drive and type in the name of my backup folder, the ""Error creating directory"" error gets replaced by the kind of error I wanted to see: ""Storage location not available - Waiting for <media> to become connected..."""
1731704,2018-01-06 02:59:11 UTC,"The same error occurs whether the backup is started manually or automatically. It also occurs when trying to restore from the backup location (if it is disconnected, of course)."
1731708,2018-01-30 11:24:37 UTC,Fixed in netcdf (1:4.5.0-2)
1731719,2019-10-13 22:42:42 UTC,This was fixed in Debian in 1.11.10-2
1731722,2017-11-20 02:55:15 UTC,Most probably the dock is set to auto-hide mode. Right click on the dock.. then click 'Latte Dock Settings' and then check the always visible option.
1731722,2017-11-20 02:56:27 UTC,"And it is 'Latte Dock', not Dock."
1731730,2017-11-12 07:08:32 UTC,"Review in progress for https://review.opencontrail.org/37437
Submitter: Ankit Jain (<email address hidden>)"
1731730,2017-11-12 16:53:54 UTC,"Review in progress for https://review.opencontrail.org/37443
Submitter: Ankit Jain (<email address hidden>)"
1731730,2017-11-14 06:06:38 UTC,"Reviewed:  https://review.opencontrail.org/37437
Committed: http://github.com/Juniper/contrail-test-ci/commit/786a4993fa0c87c0d385485dc8f2e9b833215e98
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1731730,2017-11-14 06:06:42 UTC,"Reviewed:  https://review.opencontrail.org/37443
Committed: http://github.com/Juniper/contrail-test-ci/commit/a474262288d753a959639c1b7c7ed5950aab2758
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1731730,2017-12-02 00:18:06 UTC,The changes are already there in master hence not reqd
1731733,2017-12-14 08:55:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731733,2017-12-17 07:12:16 UTC,"Hi,"
1731733,2018-03-13 18:36:46 UTC,This is connected to wayland. A workaround is to use Xorg where everything works fine.
1731733,2018-05-07 08:55:39 UTC,I'm on Xorg (Kubuntu 18.04) and I have this problem with all windows including chrome.
1731734,2017-11-12 09:39:10 UTC,"Hm, wanted to report this directly to mlayer folks, but I am not so much a fan of mailing lists. They claim to have a Bugzilla, but it seems to be down:
http://bugzilla.mplayerhq.hu/ ist nicht erreichbar [down]"
1731734,2017-11-12 09:21:55 UTC,"The following action advised in ww.mplayerhq.hu/DOCS/HTML/de/bugreports_what.html#bugreports_debug do not work... I created a comand file containing
bt
disass $pc-32,$pc+32
info all-registers
and ran
gdb mplayer --core=core -batch --command=mycommandfile > mplayer.bug
but this only resulting in
/home/xyz/core: Datei oder Verzeichnis nicht gefunden. [file not found]
./gdb-command:1: Error in sourced command file:
No stack."
1731734,2017-11-12 09:12:45 UTC,"(gdb) bt
#0  0x000000000056edf7 in fast_memcpy ()
#1  0x0000000000498119 in ?? ()
#2  0x0000000000571c7c in ?? ()
#3  0x00007ffff3c9f9b3 in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
#4  0x00007ffff3c9fc52 in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
#5  0x00007ffff3c6cf13 in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
#6  0x00007ffff3c7013d in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
#7  0x00007ffff3c70a15 in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
#8  0x00007ffff3d46363 in avcodec_decode_video2 ()
   from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
#9  0x0000000000572342 in ?? ()
#10 0x00000000004c35a1 in decode_video ()
#11 0x000000000043f5bf in ?? ()
#12 0x00000000004337d6 in main ()
(gdb) disass $pc-32,$pc+32
Dump of assembler code from 0x56edd7 to 0x56ee17:
   0x000000000056edd7 <fast_memcpy+151>:	popfq
   0x000000000056edd8 <fast_memcpy+152>:	add    (%rax),%eax
   0x000000000056edda <fast_memcpy+154>:	add    %cl,-0x7b(%rbp)
   0x000000000056eddd <fast_memcpy+157>:	rorb   %cl,-0x77(%rbp)
   0x000000000056ede0 <fast_memcpy+160>:	rorl   -0x77(%rax)
   0x000000000056ede3 <fast_memcpy+163>:	stc
   0x000000000056ede4 <fast_memcpy+164>:	mov    %rsi,%rax
   0x000000000056ede7 <fast_memcpy+167>:	je     0x56ee2d <fast_memcpy+237>
   0x000000000056ede9 <fast_memcpy+169>:	nopl   0x0(%rax)
   0x000000000056edf0 <fast_memcpy+176>:	prefetchnta 0x140(%rax)
=> 0x000000000056edf7 <fast_memcpy+183>:	movaps (%rax),%xmm0
   0x000000000056edfa <fast_memcpy+186>:	movaps 0x10(%rax),%xmm1
   0x000000000056edfe <fast_memcpy+190>:	movaps 0x20(%rax),%xmm2
   0x000000000056ee02 <fast_memcpy+194>:	movaps 0x30(%rax),%xmm3
   0x000000000056ee06 <fast_memcpy+198>:	movntps %xmm0,(%rcx)
   0x000000000056ee09 <fast_memcpy+201>:	movntps %xmm1,0x10(%rcx)
   0x000000000056ee0d <fast_memcpy+205>:	movntps %xmm2,0x20(%rcx)
   0x000000000056ee11 <fast_memcpy+209>:	movntps %xmm3,0x30(%rcx)
   0x000000000056ee15 <fast_memcpy+213>:	add    $0x40,%rax
End of assembler dump.
(gdb) info all-registers
rax            0x0	0
rbx            0x10	16
rcx            0x7ffff7f12000	140737353162752
rdx            0x10	16
rsi            0x0	0
rdi            0x7ffff7f12000	140737353162752
rbp            0x2d0	0x2d0
rsp            0x7fffffffc6f8	0x7fffffffc6f8
r8             0x7ffff7f12000	140737353162752
r9             0xb	11
r10            0xb	11
r11            0x7fffffffc780	140737488340864
r12            0x0	0
r13            0x0	0
r14            0x1	1
r15            0x7ffff7f122d0	140737353163472
rip            0x56edf7	0x56edf7 <fast_memcpy+183>
eflags         0x10202	[ IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
---Type <return> to continue, or q <return> to quit---
gs             0x0	0
st0            -nan(0x8080808080808080)	(raw 0xffff8080808080808080)
st1            -nan(0x80008000800080)	(raw 0xffff0080008000800080)
st2            -nan(0x8080808080808080)	(raw 0xffff8080808080808080)
st3            -nan(0x80008000800080)	(raw 0xffff0080008000800080)
st4            -nan(0x8080808080808080)	(raw 0xffff8080808080808080)
st5            -nan(0x8000800080008..."
1731734,2017-11-12 09:09:37 UTC,"When I rund mplayer in gdb, as instructed, I see that it is a segmentation violation."
1731734,2017-11-21 09:50:39 UTC,http://bugzilla.mplayerhq.hu/ is still down. And nobody read this bugreport either...
1731738,2017-11-12 16:25:02 UTC,Thanks for your report.
1731738,2018-07-15 18:44:50 UTC,"Hello Amr,
Thank you for submitting this bug and reporting a problem with Thunderbird."
1731738,2018-07-15 18:46:40 UTC,"Oops, I can't assign that status. I have set it to ""invalid"" instead.
Thanks
G"
1731738,2018-07-15 19:11:52 UTC,"Hi gf,"
1731738,2018-07-15 19:47:54 UTC,"Ok, Gunnar. I am sorry. My mistake."
1731738,2018-07-15 20:16:21 UTC,No problem.
1731759,2019-09-16 19:08:38 UTC,Migrated to https://github.com/widelands/widelands/issues/3226
1731762,2017-11-16 15:15:00 UTC,Here's an UGLY 8-O ... but effective :-/ workaround:
1731762,2017-11-14 13:17:39 UTC,"I'd certainly ""argue"" :-) / advocate, that the .jigdo files and
archive(s)/repository(/ies) of Ubuntu ought be such that
jigdo-lite(1) (and/or other Jigdo clients) can successfully create the
relevant target .iso files.  Even though there may have been
updates (patches / security fixes) since ubuntu-16.04.3-server-amd64.iso,
ubuntu-16.04.3-server-amd64.iso is still (at least as I'm writing this)
the most current ISO for that flavor/variant (Ubuntu-Server LTS amd64),
and ought not only be downloadable (as it is), but ought be able to
reassemble it via Jigdo (saving both clients, networks, and servers,
much bandwidth and time compared to entirely downloading the full
ISO file, which is in substantial part redundant with the earlier
ubuntu-16.04-server-amd64.iso file).
E.g. after otherwise managing to assemble/download, and then ""seed"" it
to BitTorrent - still quite popular (folks have already downloaded a
fair chunk of it from me in relatively little time) - so there's
certainly no lack of interest in obtaining the iso ... that's also
typically what folks would boot from if that's what they want to
install.
 ------------------------------------------------------------------------------

| Filename                                          Size   Download     Upload |


...

| ubuntu-16.04.3-server-amd64.iso               825.0  M   0    B/s   0    B/s |
| ^---  download succeeded!                                0.0  M   234.8  M   |


...
 ------------------------------------------------------------------------------"
1731762,2017-11-14 12:52:14 UTC,"recreate/show bug ... okay, I'm a bit late to the party on that (didn't see the
earlier comment about having recreated it 'till now), anyway, here's another
example recreating/demonstrating the bug (again, it's with the
Ubuntu archive / jigdo file, not jigdo/jigdo-lite itself):"
1731762,2017-11-13 18:57:02 UTC,My suspicion is that the jigdo file is a snapshot of the .deb files that appear on the iso and that because this is a point a release the jigdo file points to .deb files which used to exist in -updates or -security that have been superseded by newer versions. If that's correct a .jigdo file for point releases (16.04.3) is only useful for a very short period of time.
1731762,2017-11-13 18:38:27 UTC,"Ah, I was able to recreate it."
1731762,2017-11-12 14:38:07 UTC,"some more details can be found here:
https://lists.ubuntu.com/archives/ubuntu-us-ca/2017-November/002826.html
https://lists.ubuntu.com/archives/ubuntu-us-ca/2017-November/002827.html"
1731762,2017-11-12 16:18:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1731762,2017-11-14 12:26:48 UTC,"Also, similar from earlier:
https://lists.ubuntu.com/archives/ubuntu-us-ca/2014-December/002550.html
https://lists.ubuntu.com/archives/ubuntu-us-ca/2014-December/002551.html
https://lists.ubuntu.com/archives/ubuntu-us-ca/2014-December/002552.html
Also, a search, e.g. on Google, for, e.g.:
ubuntu jigdo ""Aaargh -"" ""files could not be downloaded""
also shows a fair number of folks occasionally bump into this general type of
bug with Ubuntu, jigdo, and files missing from archive/repository."
1731762,2017-11-13 17:44:21 UTC,How could I reproduce this issue? I'm not familiar with jigdo.
1731762,2017-11-12 16:34:16 UTC,"The bug isn't in jigdo itself, but Ubuntu really wants/prefers bugs be filed against package, so, ... since it's at least related ...
Also, don't know about Ubuntu, but Debian has effectively pseudo-packages for filing bugs against things that are bugs, but aren't specific to package(s), e.g. such as an issue with data on a Debian repository or web/FTP server (e.g. missing, outdated, or incorrect information, typo, ...) - and being filed againt appropriate pseudo-package, it gets routed to relevant developer(s)/team(s).
Feel free to update the Package this bug is filed against if there's more suitable Package (or pseudo-Package, or suitable way to tag or whatever) so it gets to the relevant person(s)/team(s)."
1731763,2019-02-11 22:06:07 UTC,"The post removed the spaces, use the ""ascii draw"" above:"
1731763,2019-06-06 14:57:58 UTC,That's a very nice idea! Currently I do that by hand and its very boring.
1731763,2019-06-06 15:12:16 UTC,"This will be very interesting to high frequency layouts. Should allow even place around differential track (as unique object), not just a single track."
1731763,2019-06-06 15:35:54 UTC,This is on the v6 work plan.
1731763,2019-10-13 17:30:40 UTC,"I would like to see a via stitching. I see however one little problem with this. If you have all the via's in a grid with identical spacing, then this forms a resonant structure. Adding a random (or a not-so random) offset per via tunes each segment of the two stitched ground planes to a different frequency, so the two ground planes are no longer able to resonate as a whole."
1731763,2018-11-13 10:45:24 UTC,"Could Via stitching perhaps be added as a copper zone type?
Here you already the net info, priority etc."
1731763,2019-02-09 18:17:47 UTC,@shack  I think that is a good idea.  An option in the zone settings to turn on via stitching and specify the density and grid pattern.  You would also have the ability to select which layers you want to stitch.
1731763,2019-02-11 22:04:32 UTC,"Good! Some propose of configurations:
- Border distance (use the actual measurement unit);
- Distance between two vias (use the actual measurement unit);
- Type of the via, of couse;
- Layers to connect (shall we remove the restriction of just select one layer to the Copper Zone?);
- Hole via or blind/burred via (BOOLEAN);
- Allow diagonal or just H/V vias (BOOLEAN)."
1731766,2017-11-12 15:07:48 UTC,Note: same happens using Mate instead of Cinnamon
1731768,2019-04-03 04:06:01 UTC,"Using NVidia driver v390.116, I'm also experiencing freezes. Mouse only moves but Mouse buttons and Keyboard don't work while freezed. Though after the freeze all actions are performed at once. For example if I hit Alt+Tab 3 times on freeze, nothing happens then suddenly windows switch 3 times."
1731768,2018-07-28 14:36:23 UTC,I am experiencing freezes on 18.04 with NVIDIA Driver Version 390.48. I've been forced to hard power cycle my machine at least 4 times this morning alone :(.
1731768,2018-07-17 16:33:52 UTC,I'm experiencing freezes on 18.04 with the nvidia-390 drivers.  Computer has frozen three times before lunch today.
1731768,2018-01-20 09:54:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731768,2017-12-19 00:18:13 UTC,"I'm having similar problem with 1080 and Ubuntu 16.04. Sometimes the desktop would freeze, but the mouse cursor still moves. Usually I'm able to Ctrl-Alt-F1 to a console then Ctrl-Alt-F7 to get back to the desktop. When I get back to the desktop, the desktop registered the mouse clicks that I did when it freezed. But then usually it would freeze again, so I had to switch to tty1 again and so on, until a point where I'm not able to switch to tty1 anymore. Sometimes the whole system freezes when I'm in tty1, in this case sometimes Ctrl-Alt-Del would do the job but often (esp. when in desktop) hard power down is required."
1731768,2017-11-12 15:30:28 UTC,Below are the extracts of the kern.log and xorg.log (keep in mind this probably also includes the lightdm restart.
1731768,2018-06-11 14:44:51 UTC,"Problem still persists with 18.04 running nvidia-396 drivers.
More details here https://askubuntu.com/questions/1030466/ubuntu-18-04-keeps-freezing-nvidia"
1731768,2018-01-14 22:26:00 UTC,"I've also experienced a similar issue, mouse stops working and requires switch to another console, multiple times running 16.04LTS and later (I'm currently on 17.10).  It is a major issue for those afflicted."
1731769,2017-12-10 20:08:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731769,2018-04-10 20:27:34 UTC,"This bug affects many more users. It is present in Ubuntu 18 as well as in Fedora 27 (experience / both are on my machines).
This bug reduces the acceptance by ""normal"" users even more. I do consider fixing this stupid display error  would be an important contribution to propel encryption with normal users.
Moreover: It is a bug and it devastates a great tool!"
1731769,2018-06-01 15:23:35 UTC,Since a few weeks I can see the line with the password request in Ubuntu 18.04 . Can not verify for Fedora.
1731769,2018-09-23 21:04:52 UTC,The same issue applies for Ubuntu 18.10.
1731769,2019-11-03 11:52:54 UTC,"partly solved: In Ubuntu 19.x the GUI-Plymouth does request the password - fine!
In non-silent (CLI) mode the password is requested now. Issue: Other text makes it difficult to see the password requesting line. You need to be decently familiar to the situation to identify the password request. This can not be assumed."
1731771,2017-11-14 10:19:44 UTC,Some debug information:
1731771,2017-11-12 16:01:45 UTC,Fixed some bad English.
1731771,2017-11-15 19:41:02 UTC,I opened a new bug on Github. Apparently Zim has moved there: https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/229. Moreover the bug is in pygtk and not in Zim. Pygtk bug: https://bugzilla.gnome.org/show_bug.cgi?id=790341
1731771,2017-11-12 16:07:16 UTC,"BTW, I'm using zim 0.67-1 on Archlinux. I have GNOME 3-26 and gtksourceview3 v3.24 installed."
1731775,2019-11-14 04:17:28 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1731775,2017-11-13 00:35:04 UTC,"I thought about that, but it may be desirable to not have the mic enabled at all times if it is only picking up background noise. I imagine that would be more of an issue with multiple microphones."
1731775,2019-03-27 09:51:15 UTC,My microphone (Shure SM58) does not have a switch.
1731775,2018-06-12 02:31:27 UTC,Pushing this to 2.3.0 so I can focus on the library redesign branch.
1731775,2019-03-31 09:26:19 UTC,What is the proposed solution here?
1731775,2017-11-13 00:03:32 UTC,"Can't you enable it always and use the Mic hardware switch?
How could we help the users here?"
1731779,2018-05-21 12:54:07 UTC,Just making a comment as I found your wording here so clarifying for others how these work in Traktor.
1731783,2019-06-23 12:51:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731788,2018-04-06 22:14:21 UTC,"I suppose the error about non-constant index is due to the use of `gl_FragCoord.xyy` in the expression for `index`. See https://stackoverflow.com/a/19529963/673852 for description of what may be used as an index. `gl_FragCoord` is neither a constant-expression nor a loop index, so an expression containing it can't be a constant-index-expression."
1731788,2018-09-26 04:14:13 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/387
1731788,2018-04-07 18:37:22 UTC,"> Again, do you have interest to help us here and do the required steps?
"
1731788,2018-04-07 15:51:42 UTC,"Yes, I understand gl_FragCoord cannot be used here. I just want to understand what this line does."
1731788,2018-04-07 15:26:26 UTC,"Oh, I mean `sampler1D`, of course."
1731788,2018-04-07 15:25:49 UTC,"> Does the statement ""random(vec4(gl_FragCoord.xyy,i))"" return a float?
"
1731788,2018-04-07 13:38:51 UTC,"Good find. I must admit my knowledge of GLSL is very limited, and the shader is not mine. Does the statement ""random(vec4(gl_FragCoord.xyy,i))"" return a float? Would some other mechanism to select a random int from [0..63] be applicable and deliver equal or better results?"
1731788,2018-01-30 18:39:24 UTC,"I tested on my older notebook (Geforce 580M): Indeed, v0.17.0 has this issue. Built from sources: no problem. And now I also see the issue on my Geforce 960M notebook. ( I have upgraded my Qt since November, cannot reproduce #2.)"
1731788,2017-11-14 03:20:12 UTC,"I can confirm the issue on Windows in ANGLE mode only. It's interesting, but fragment shader cannot be compiled into D3D shader and planets are always in shadow."
1731788,2017-11-13 23:35:49 UTC,"Sorry for the delay in posting my log file, the new beta came out just as I was leaving for work this morning."
1731788,2017-11-13 16:17:50 UTC,Please show log from last beta
1731788,2017-11-13 15:33:52 UTC,Thanks for your help.  Unfortunately I'm still seeing the issue in ANGLE mode with version 0.90.0.9959 on both the Mobile Intel Series 4 Express and GeForce 560 chipsets.
1731788,2017-11-13 11:44:59 UTC,Please check version 0.90.0.9959 or later.
1731788,2017-11-13 05:38:08 UTC,Obvious fix has been added as revision 9958. This fix will be available for testing in next beta.
1731788,2017-11-13 02:47:57 UTC,"The logfile is from the laptop with a Mobile Intel Series 4 Express video chipset and that requires ANGLE mode.  Forcing DX11 fails the same way as the default DX9 ANGLE mode.  I also tested on a GeForce 560 desktop for another data point.  It works fine on DX11, but failed in the same way as the laptop when forced to simple ANGLE mode.  I also tried a full un-install of 0.16.1 on the laptop (including manual deletion of any leftovers in Program Files and AppData), but planet rendering still failed after a fresh install of any beta since then.  MESA mode works but is very slow.  It's not a huge problem, I realize my hardware is old and is due for an upgrade.  I can live with 0.16.1, but will keep tinkering and report any progress here."
1731788,2017-11-13 00:49:10 UTC,"OK, there is a shader error reported in the logfile by your D3d9 shader compiler.
Is the Geforce 560 not compatible with DX11? Try with --angle-d3d11 please."
1731788,2017-11-12 19:37:15 UTC,The issue remains as of beta 0.90.0.9954.  Attached image of Saturn in Angle mode.
1731788,2017-11-14 11:10:40 UTC,"Not in shadow, just not rendered without a valid shader.
I cannot replicate it on my systems. (Maybe somebody can prepare a VM image for Qemu or VirtualBox with emulated old Intel GPU?) Does it even occur without 3D planets and self-shadowing (which the error message points at), and without nomenclature (where the bug allegedly first appeared)?"
1731788,2017-11-12 23:35:22 UTC,"Works as of 0.90.0.9956 (trunk) on a Geforce 960M in ANGLE mode.  Saturn is visible, no problem.
Maybe a logfile could help."
1731788,2017-11-13 00:06:40 UTC,Attached log file from laptop on which issue was first observed (Mobile Intel Series 4 Express video chipset) in ANGLE mode.  Behavior also seen on desktop with GeForce GTX 560 graphics with ANGLE.  Started with beta 0.90.0.9852 and all since.
1731794,2017-12-01 17:10:00 UTC,Looks like a systemd problem:
1731795,2018-08-18 23:03:28 UTC,"I will remove the milestone, because this can be done independent from a Mixxx version and there was no progress lately."
1731795,2017-11-16 16:28:23 UTC,"Yes, Mixxx should have an official YouTube channel. There are some videos, but they're all old screencasts that don't really explain how and why to use features of Mixxx or how to use a controller or turntables."
1731795,2018-04-15 00:06:33 UTC,Shoudn't we introduce a 2.1.1 milestone and assign all issues that are supposed to be fixed or finished in a following 2.1.x release? It is confusing to use the 2.2.0 milestone for this purpose.
1731795,2018-04-14 23:40:35 UTC,"Yes, that is true, but I'd like to keep it assigned to a milestone so I don't forget about it."
1731795,2018-04-14 21:51:29 UTC,This can be published at any time and does not depend on any milestone.
1731795,2017-11-13 16:33:57 UTC,"There are plenty of demo videos from users, check hilarious Juicy M
SHOWİNG HOW TO MİXXX https://www.youtube.com/watch?v=5F16Q8X0sRg"
1731795,2018-04-15 08:23:33 UTC,OK 2.1.1 and 2.2.1 are in place.
1731796,2017-11-27 18:44:08 UTC,I added an nvidia task to the bug so its maintainer can take a look to see if it's related or not.
1731796,2017-11-12 20:46:09 UTC,"The bug detection and reporting system wants to report this bug twice ;-) It's the same incident, but perhaps the actual error managed to happen twice somehow."
1731796,2017-11-25 01:18:06 UTC,"Happened again. Auto-bug reporting didn't recognize this report as similar, so created bug 1734405"
1731796,2017-11-13 11:45:32 UTC,Thanks for filing this bug in Ubuntu.
1731796,2017-11-27 18:42:58 UTC,Or nvidia
1731796,2017-11-13 11:47:48 UTC,"Sorry, it's actually gdbus that is soft locking"
1731798,2019-12-20 14:10:14 UTC,IMO this is fixed in latest unattended-upgrades version available via -updates.
1731799,2018-09-26 06:16:24 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/438
1731800,2020-08-31 16:06:36 UTC,"Closing, as this bug is out of date. I still don't use Wayland, but I see that xdg-screensaver mentions it…"
1731800,2017-11-12 21:58:26 UTC,"Thanks for this report. Exactly how to fix it will depend on how xdg-utils adapts to Wayland. At present, xdg-screensaver mentions Wayland, but since it uses xprop to get X window properties (and no other method), I don't see how it can possibly work with Wayland, which seems to have a completely different screen inhibition mechanism:"
1731801,2017-11-18 17:16:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731801,2017-11-27 09:13:45 UTC,"I've uploaded newer upstream version to Debian, it should appear in Ubuntu shortly."
1731801,2017-11-12 21:32:31 UTC,"Note: this bug is an Ubuntu bug, not a Caffeine bug. Caffeine merely happens to be hosted on Launchpad; I don't actually package it for Ubuntu; as you can see, the Ubuntu maintainer is Ubuntu MOTU Developers. Hence, marking invalid for upstream, and adding an assignment to the Ubuntu package."
1731803,2018-04-18 14:00:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731819,2017-11-13 18:30:11 UTC,Tracked via upstream ticket: http://tracker.ceph.com/issues/22120
1731819,2017-11-29 14:06:19 UTC,Work inflight upstream to fix and then backport to L and J; Ubuntu will pick those up with the next set of point releases.
1731819,2018-03-22 09:25:13 UTC,This bug was fixed in the package ceph - 12.2.4-0ubuntu1
1731828,2017-11-29 11:42:46 UTC,"I think we know what format should be used, so providing a configuration option makes little sense; lets just set the right values in the nova.conf templates for each supported release; when ceilometer does support the versioned format, we can just switch back to 'both'."
1731828,2018-04-09 07:16:09 UTC,"Change abandoned by Craige McWhirter (<email address hidden>) on branch: master
Review: https://review.openstack.org/559272
Reason: Deferring to an opinionated stance on the setting."
1731828,2018-04-05 06:00:43 UTC,"The need for this feature, for myself at least is related to this bug:"
1731828,2017-11-29 11:43:24 UTC,Which release does this impact from?
1731833,2017-11-13 06:24:31 UTC,"Network adapter is Marvel 88W8797, and solution come from: Bug #1681513 reported by Jesse on 2017-04-10"
1731840,2018-01-31 19:57:44 UTC,I'm not clear on what the issue is here.  Please provide more details.
1731849,2017-11-13 09:19:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519275"
1731849,2019-01-11 00:52:52 UTC,"Change abandoned by licanwei (<email address hidden>) on branch: master
Review: https://review.openstack.org/519275"
1731849,2019-09-30 17:36:59 UTC,https://review.openstack.org/519275 was silently abandoned but had received some review feedback so I'm not sure why it was abandoned except it didn't get any review comments on the latest patch for several months so I'm assuming the author just moved on. Someone could revive it though.
1731850,2017-11-13 09:04:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519268"
1731850,2019-05-30 15:36:12 UTC,"The patch was just on test code, which bandit shouldn't be scanning."
1731850,2019-05-30 15:36:57 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/519268
Reason: We shouldn't care about bandit scans on test code, it should be skipped:"
1731860,2017-11-13 09:13:07 UTC,"The bug report is generated from a virtualbox guest, running virtualbox 5.2 with guest additions 5.2.1."
1731860,2017-11-13 11:21:27 UTC,"Also, on the flip side;
S alone can of course not be bound to a shortcut.
A combo such as S + Alt however works fine, and this shortcut is not triggered by Alt + §, which means that the double triggering is only one way. S triggers paragraph, but paragraph does not trigger s."
1731862,2017-11-13 12:24:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1731862,2017-11-13 13:25:04 UTC,Here more info: https://ubuntuforums.org/showthread.php?t=901529&page=2&highlight=epl6200L
1731864,2018-01-27 10:26:43 UTC,"Reviewed:  https://review.openstack.org/519664
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b4608bf0b40d50834bd5ab2e50096ec6c284822
Submitter: Zuul
Branch:    master"
1731864,2017-11-14 09:10:24 UTC,As I understand the RPC function `schedule_and_build_instances` is called from https://github.com/openstack/nova/blob/master/nova/conductor/api.py#L130 . Most probably it would be enough to add profiler.trace_cls decorator to the class ComputeTaskAPI.
1731864,2017-11-19 19:50:31 UTC,"Just attached two traces obtained from the latest devstack deployment.
This focuses the test : https://github.com/openstack/nova/blob/57bf7f49cf08dbc0c0d16eb7512ecaa15978fbff/nova/profiler.py#L68"
1731864,2017-11-14 09:48:32 UTC,I maybe missed something in the nova code base but I see it on the nova.conductor.rpcapi.ComputeTaskAPI:
1731864,2017-11-13 20:34:27 UTC,"I took a look to old traces[1] (ocata - no uwsgi). If you take the first RPC in the trace (schedule_and_build_instances), you only get the receiver trace (the conductor) not the sender (the api). It's likely the issue was already here. They are also other cases in which you only get one of the two parts of the RPC (e.g see object_action compute->conductor when instance states are updated)."
1731864,2018-01-09 16:36:08 UTC,Patch is here: https://review.openstack.org/#/c/519664/
1731864,2017-11-13 15:56:11 UTC,"Confirmed, the bug is introduced after switching to uWSGI-based deployment. Besides Nova it affects also Cinder. Keystone, Neutron and Heat are not affected."
1731865,2017-11-13 10:09:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519291"
1731865,2019-10-07 16:46:17 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/519291"
1731865,2019-10-07 16:47:05 UTC,"As noted in the review, this isn't necessarily a huge issue and I'm not sure it's worth investing time on"
1731867,2017-11-13 09:31:10 UTC,"There is no relation with tzdata. sorry, this was in the submission."
1731870,2018-01-18 13:05:08 UTC,I had the same problem on Ubuntu 17.10 after installing bumblebee-nvidia.
1731870,2018-01-18 14:00:52 UTC,"@rubo77:
why not as described at https://bugs.launchpad.net/ecryptfs/+bug/1670336, comments #21 and #23?"
1731870,2017-12-30 00:39:45 UTC,"This appears to be a bug in the systemd cryptsetup helper, which has a constraint requiring a block device where no such constraint exists in cryptsetup itself.  Since Ubuntu 17.10 now uses swap files by default instead of swap partitions, this will fail."
1731870,2017-12-18 00:53:29 UTC,"Me too having this issue; on MSI GV62 7RE with i7-7700HQ, 8GB RAM, GTX 1050 ti, Crucial SSD (275GB M.2 SATA) + 1 TB rotating HD."
1731870,2017-12-12 19:57:38 UTC,"The same issue for me, and it showed up as well after installing Nvidia drivers"
1731870,2017-11-25 20:56:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731870,2017-12-03 21:59:20 UTC,"After many flashes of the screen and ~10 minutes of waiting, I gave up. No login window for me. Is there a workaround?"
1731870,2017-12-29 22:42:38 UTC,New U 17.10 on Lenovo X230.
1731871,2017-11-30 20:30:34 UTC,"remove Ubuntu projects please, it's assigned to tripleo."
1731871,2017-12-01 08:20:20 UTC,"Reviewed:  https://review.openstack.org/519422
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ce2f5b838b120b17c629bf16e877456da6ac9f2b
Submitter: Zuul
Branch:    master"
1731871,2018-01-03 22:00:56 UTC,"Reviewed:  https://review.openstack.org/519283
Committed: https://git.openstack.org/cgit/openstack/tripleo-image-elements/commit/?id=b862cd25ee4132115c7030a24ff4d6c3888b5423
Submitter: Zuul
Branch:    master"
1731873,2017-11-14 09:56:11 UTC,@Alex they haven't approved my upload yet. It's still in the queue:
1731873,2017-11-14 09:36:12 UTC,"@Alberto
what exactly version of the one proposed ?"
1731873,2019-05-09 08:33:16 UTC,no longer focus per current oem status.
1731873,2018-02-23 15:29:43 UTC,"As mentioned before, this change has been reverted from -proposed."
1731873,2017-11-16 21:11:49 UTC,"Hello Alberto, or anyone else affected,"
1731873,2018-02-22 19:26:00 UTC,Changing xenial back to triaged as this change got reverted in a subsequent upload
1731873,2017-12-21 10:39:16 UTC,"I tried AMN4-DVT1-C2 with amdgpu-pro-17.10-414273,
not so ""Enabling power saving mode for amdgpu-pro"" line in /var/log/gpu-manager.log in step 5."
1731873,2017-12-19 08:35:58 UTC,"Comments #10 and #9 on the mentioned bug do not show that the verification was done, those are automatic messages mentioning the update getting accepted into -proposed for verification. For a but to be considered verified by the SRU team, the bug needs to have its verification-needed-SERIES tag switched to verification-done-SERIES along with a comment mentioning what steps of testing have been performed on which version with what results. Sadly here none of that is present, so we cannot release the package to -updates yet."
1731873,2017-12-13 07:34:14 UTC,"based on https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1728547 #10 and #9 , the verification was done."
1731873,2017-11-16 21:13:36 UTC,"Hello Alberto, or anyone else affected,"
1731873,2018-02-23 15:29:00 UTC,This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.6
1731877,2019-08-27 15:12:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731888,2018-01-25 19:19:13 UTC,"Exact issue happens to me too. I haven't noticed it being intermittent. I think it always happens. When you resize the window it's ok. As soon as you 1-click maximize it, it happens."
1731888,2017-12-15 14:30:25 UTC,It happens to me too.
1731888,2018-01-25 19:19:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731889,2017-11-14 06:44:54 UTC,"Reviewed:  https://review.openstack.org/519313
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=01da04a0a7eff4c52bd0e35d404545f9a413b602
Submitter: Zuul
Branch:    master"
1731889,2017-11-13 11:46:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519313"
1731889,2017-12-07 23:56:18 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1731889,2017-11-16 05:13:14 UTC,"Reviewed:  https://review.openstack.org/519586
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=86ea9b8834fdd89cbd2e4fae10eb42907f8f466c
Submitter: Zuul
Branch:    stable/newton"
1731889,2017-11-14 08:49:20 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/519583"
1731889,2017-11-15 01:06:42 UTC,This issue was fixed in the openstack/nova 15.0.8 release.
1731889,2017-11-14 20:45:08 UTC,"Reviewed:  https://review.openstack.org/519585
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c8945835855ea6c8a42c269ec55cde71059bda9
Submitter: Zuul
Branch:    stable/ocata"
1731889,2017-11-14 20:26:45 UTC,"Reviewed:  https://review.openstack.org/519583
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=439349e944946d42e58469749ec8187f6015ac14
Submitter: Zuul
Branch:    stable/pike"
1731889,2017-11-14 08:54:51 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/519586"
1731889,2017-11-14 08:53:09 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/519585"
1731889,2017-11-15 01:10:28 UTC,This issue was fixed in the openstack/nova 16.0.3 release.
1731889,2017-11-16 19:59:23 UTC,This issue was fixed in the openstack/nova 14.0.10 release.
1731890,2017-12-20 11:06:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529295"
1731895,2017-11-21 07:13:43 UTC,"Sorry, admin is required in network context.
https://github.com/openstack/rally/blob/master/rally/plugins/openstack/context/network/networks.py#L29"
1731895,2017-11-23 09:54:06 UTC,"Ah, I see. Not sure why tough, now you cannot specify a network_id or empty network to spawn instances in."
1731898,2017-11-13 16:45:10 UTC,Marking as Fix Committed. Need to release as a snap before I can comfortably close this.
1731909,2017-11-16 09:51:59 UTC,could you try with the update listed in the previous comment?
1731909,2017-11-13 13:19:41 UTC,This sounds like a mutter issue.
1731909,2017-11-16 09:52:46 UTC,if that's still an issue then it would be useful to send it upstream to http://bugzilla.gnome.org (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
1731913,2017-11-14 12:14:08 UTC,apport information
1731913,2017-11-14 12:14:02 UTC,apport information
1731913,2017-11-14 12:14:05 UTC,apport information
1731913,2017-11-14 12:14:05 UTC,apport information
1731913,2017-11-14 12:14:03 UTC,apport information
1731913,2017-11-14 12:14:00 UTC,apport information
1731913,2017-11-14 12:14:07 UTC,apport information
1731913,2017-11-14 12:13:59 UTC,apport information
1731913,2017-11-13 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1731913,2017-11-14 12:13:52 UTC,apport information
1731913,2017-11-14 12:13:50 UTC,apport information
1731913,2017-11-14 12:13:53 UTC,apport information
1731913,2017-11-14 12:13:59 UTC,apport information
1731913,2017-11-14 12:13:54 UTC,apport information
1731913,2017-11-14 12:13:56 UTC,apport information
1731913,2017-11-14 12:13:58 UTC,apport information
1731913,2017-11-14 12:13:55 UTC,apport information
1731916,2017-11-24 15:44:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731916,2018-04-06 20:24:13 UTC,"The attachment ""bug-1731916-ifupdown.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1731916,2018-04-06 20:09:20 UTC,"Verified that this does indeed fix the problem.
Here is a fix to the package."
1731918,2017-12-01 15:29:26 UTC,"I have confirmed on Windows that adding a new printer works when stopping Chrome, adding the printer, then restarting Chrome.  Though stopping Chrome first is (almost certainly) not strictly necessary as long as it's restarted afterwards."
1731918,2017-11-14 15:17:32 UTC,"Hi Galen, I don't recall the reason for that change.  At a glance, I'd guess the current approach simply requires less code."
1731918,2017-11-14 15:46:14 UTC,"> BTW, I have confirmed that restarting Chrome causes Hatch to restart as
> well.  I'm wondering if you tried that before having to manually kill
> Hatch?
"
1731919,2017-11-13 13:42:40 UTC,"This might be high, but it depends on someone wanting to set a model-config, which would otherwise be invalid for the version they are currently using, and then upgrading to a version where it is supported, but the value set was not allowed.
In this case it is the type ""bool"" for a field that is actually as string.
One option is that whenever we introduce a new field, we perform validation on the config and just throw away any invalid config for fields that we have a schema for.
The intent was always that you could supply schema, and we would let you have it sit there, in case a different version of Juju supports it.
The only way I can see to rationalize the two goals is that when we *do* have a schema, we treat invalid values as being thrown away *during upgrade*, we can still validate them during ""juju model-config"" etc."
1731934,2018-08-09 11:24:02 UTC,The way these services are deployed is not part of the ML2 driver scope. This bug needs to be open against the deployment tool (e.g TripleO).
1731934,2018-08-09 11:39:17 UTC,"so I am changing the project to tripleo and set it as ""new"""
1731934,2019-02-12 13:36:35 UTC,"no, I don't have a live setup with the issue"
1731934,2019-05-19 04:17:42 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1731934,2019-02-12 13:19:02 UTC,Is it still alive?
1731935,2017-11-13 14:35:34 UTC,"Honestly, you won't be able to see all MAC addresses in the machine listing. It is too much information. You have to consider that there will be machines with multiple NIC's and showing all of them in the listing is just impossible."
1731935,2018-09-13 16:14:13 UTC,"This will not be possible until we can reliably have infinite scrolling on variable-height rows.
Possible design: zpl.io/VqEjNg7"
1731935,2019-09-19 15:04:08 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1731936,2018-11-09 17:12:14 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.openstack.org/519356
Reason: This has been up here for a long time, is in merge conflict and looks stalled. I'm going to abandon to cut down the review queue. Feel free to reopen/rebase if this is still applicable."
1731936,2017-11-14 13:59:41 UTC,"Correct, using V2.  Also, to trigger the bug, you need to use an incorrect datetime stamp. So the datetime should look something like the tempest test uses (https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_list_servers_negative.py#L115).  Your curl command would need to look more like:"
1731936,2017-11-13 14:36:59 UTC,I have submitted https://review.openstack.org/#/c/519356/ as a fix for this bug.
1731936,2017-11-14 08:10:25 UTC,looks like you are using v2 version ?
1731936,2018-02-27 16:42:06 UTC,"The same here with pike and keystone v3.
>>> Unexpected exception in API method: ValueError: Unable to parse date string u'2011/01/01' <<<
Is a 500 where there should be a 400"
1731936,2017-11-14 08:17:11 UTC,I tried on newton version and
1731938,2018-09-25 07:20:32 UTC,Will be good to see this issue addressed. I encountered this bug while running regression test for Xyce 6.9 parallel build and the error occurred in Zoltan module. I wonder whether this has an impact on other packages--for example ngspice--built with mpi options. SHould we be suspicious of openmpi packaged with Ubuntu  18.04?
1731938,2017-11-13 14:49:36 UTC,I consider this bug should have a high priority because it makes OpenMPI unusable and unreliable on Ubuntu Artful.
1731938,2017-12-24 16:10:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731938,2020-09-30 13:56:38 UTC,"When will this be fixed? Considering that Ubuntu 18.04 LTS is supported until 2023-04, the severity of this bug, and how easy it is to fix (repackage the same version of OpenMPI compiled without the not recommended --enable-heterogeneous option) it is quite disappointing that after so many years it has not been fixed as it makes the default MPI shipped with Ubuntu LTS basically unusable."
1731938,2020-02-11 09:08:40 UTC,"According to the changelog, this has been fixed in Debian with version 3.0.1~rc1-2 of src:openmpi. A fixed version of the package is available in Eoan and Focal. I agree it would be nice fix this in Bionic too; this requires a Stable Release Update (SRU):"
1731938,2019-08-02 21:02:33 UTC,"Wow, just found this bug."
1731938,2019-08-02 21:01:56 UTC,"The --enable-heterogenous was removed by Debian upstream for libopenmpi3 as a result of this bug report, but it was never applied to libopenmpi2.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886336"
1731938,2018-09-25 06:19:28 UTC,"We have just spent today hunting down a user bug report for Xyce (which uses Trilinos, and its Zoltan library) that turn out to be exactly this issue -- the user is seeing strange results from Xyce, and one of our developers tracked it to exactly the issue that MPI_Send ""to"" the same processor is not in fact received *by* that processor.   It is easily seen using a program similar to the snippet in the initial report, which I will attach.  If the program is compiled with mpicc and run with any number of processors, it will show ""BAD BAD BAD"" on every line reporting what was received by processor N from processor N, but no problem for those received by processor M from processor N with M!=N."
1731938,2019-04-26 21:39:58 UTC,Having this fixed is highly appreciated. (2x)
1731938,2019-02-19 02:33:54 UTC,"@Xavier Thanks very much, that fixes the problem for me."
1731938,2018-03-02 10:31:28 UTC,Any progress on that issue?
1731938,2019-02-18 13:36:01 UTC,@acroucher I re-tried on my side to manually build the package on Ubuntu Bionic and it failed because of the Java bindings. It is hard to know if your issue is the same without seeing your config.log. But this is on I managed to workaround that and re-build the package on Bionic.
1731938,2019-02-14 03:49:10 UTC,"I am using Ubuntu 18.04 (Bionic) and am trying to work around this bug by rebuilding the source package for openmpi, according to these instructions for Ubuntu 17.10:"
1731938,2018-09-25 14:28:13 UTC,I would just like to add that the README for OpenMPI at github has this text now:
1731938,2018-09-25 07:59:47 UTC,"I confirm this bug still exists in Ubuntu Bionic, which is annoying because it is an LTS."
1731938,2019-02-28 06:50:47 UTC,Bumping this issue as we failures with the openmpi version in bionic caused by this Friday. Having this fixed is highly appreciated.
1731938,2019-02-18 13:48:51 UTC,"There was a typo in my previous comment, so I will post here the full list of commands to re-build OpenMPI package on Ubuntu Bionic without --enable-heterogeneous"
1731940,2018-02-05 21:22:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731940,2018-08-09 08:42:59 UTC,"Same problem (since long lime ago) on Debian but a different computer (MSI GS40 6QE Phantom) tha shares the same audio hardware:
Realtek ALC898
ESS SABRE HiFi audio DAC"
1731940,2018-09-04 07:45:54 UTC,"Also affected. Using `Arch Linux`, `PulseAudio`. Motherboard model P775dm2-g. ALC898 and ESS SABRE HIFI. It has a light on that port. After booting linux, the red light disappears. However, as i plug in a headphone, it produces two short beep sound."
1731940,2019-01-28 04:31:39 UTC,Not working. Confirmed for the approach in the previous comment.
1731940,2018-12-19 06:55:08 UTC,"A possible work-around: Update the jack's description to PulseAudio, as shown:"
1731943,2018-02-08 18:39:22 UTC,Fix proposed: https://review.openstack.org/534221
1731943,2018-02-08 19:59:44 UTC,"Reviewed:  https://review.openstack.org/534221
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=4ab58eef0661b1c0b849bcd66d215f75e7004e71
Submitter: Zuul
Branch:    stable/ocata"
1731948,2018-04-04 16:11:36 UTC,I see the OVO patch was abandoned.  Is there anything left to do there?
1731948,2017-11-23 06:30:27 UTC,"Reviewed:  https://review.openstack.org/519622
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5e08a9b0e7d4f99d217ca73c6aa37e52a13c5d5a
Submitter: Zuul
Branch:    master"
1731948,2017-12-07 20:24:03 UTC,This issue was fixed in the openstack/neutron 12.0.0.0b2 development milestone.
1731948,2017-11-21 20:55:00 UTC,Added oslo.versionedobjects to the list of affected projects so that it allows to use custom registries for consuming projects.
1731948,2017-11-21 23:15:06 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/521245
Reason: as discussed with Ihar, it will not be necessary"
1731948,2017-11-13 19:30:47 UTC,IMO it is a bug because https://review.openstack.org/#/c/321001 was more like a trigger for this issue than reason of if. I think that we should fix somehow this problem and then merge again https://review.openstack.org/#/c/321001
1731948,2017-11-13 19:17:27 UTC,"Looks like https://review.openstack.org/#/c/321001 was reverted, is this still a bug?"
1731948,2017-11-14 06:13:57 UTC,"the UT failures seen on networking-midonet was probably UT-only issue, ie. lack of fixtures,
because in real deployments there is no process which uses both of neutron objects and os-vif objects. (at least for midonet deployments)"
1731948,2017-11-14 11:29:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519622"
1731950,2017-11-13 15:27:16 UTC,Some suggestions on how to address this (off the top of my head):
1731957,2018-01-05 19:13:30 UTC,"These might be helpful or related:
- https://bugzilla.redhat.com/show_bug.cgi?id=1499800
- https://bugzilla.redhat.com/show_bug.cgi?id=1501957"
1731957,2020-11-16 18:12:02 UTC,"Sounds like this is/was rather an issue with libvirt or openstack, but certainly not qemu. If the problem still persists, please report it to those projects first. Thanks!"
1731968,2019-02-13 11:06:23 UTC,I've been documenting my attempt to work around this problem here: https://stackoverflow.com/questions/47415198/missing-gl-version-from-glewinit-using-egl/54668271#54668271
1731968,2018-08-27 22:13:32 UTC,"This works when installing using the runfile method, but fails for the packaged drivers. So it definitely appears to be a packaging issue specific to Ubuntu. Confirmed to work on Fedora and Arch with 390-series drivers as well."
1731968,2018-08-04 00:41:26 UTC,"This is still a problem in 396.45 on Ubuntu 16.04. The minimal test case fails, and EGL doesn't work cleanly. Tested on clean installation with an Nvidia Titan Xp and Titan X (Pascal)."
1731968,2018-01-27 05:14:58 UTC,"Reverting this links back:
http://launchpadlibrarian.net/345111430/nvidia-graphics-drivers-384_384.90-0ubuntu0.16.04.1_384.90-0ubuntu0.16.04.2.diff.gz"
1731968,2018-01-20 10:18:14 UTC,"I confirm problems for GT640 and GT430.
Version 384.90-0ubuntu0.16.04.1 - works fine.
Version 384.90-0ubuntu0.16.04.2 - occasional crashes of applications.
Version 384.111-0ubuntu0.16.04.1 - crashes (same as previous)."
1731968,2017-11-13 16:20:49 UTC,Attaching testcase
1731968,2018-08-05 03:31:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731968,2017-11-27 20:55:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731982,2017-11-13 17:31:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1731984,2018-09-04 08:07:15 UTC,"I was debugging the tempest.api.volume.test_volumes_extend.VolumesExtendAttachedTest.test_extend_attached_volume failure in
http://logs.openstack.org/98/576798/13/check/devstack-platform-opensuse-150/fe5f155/ and I think that this bug is related."
1731984,2018-01-04 05:59:49 UTC,"Reviewed:  https://review.openstack.org/529500
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d96b6dfba03424baf8b3ddc7539347554892e941
Submitter: Zuul
Branch:    master"
1731984,2017-12-21 07:09:56 UTC,"OK, some good news I guess. Ran again against boot volume and non-boot volume. In both cases IO stopped when the command was first run (as expected) but then I was able to run it a second time and it succeeded, and other than a few second pause in IO, things resumed and everything was happy on the host."
1731984,2017-12-21 06:33:08 UTC,"Session gets deleted, then recreated:"
1731984,2017-12-21 06:47:36 UTC,Boot volume test was not good.
1731984,2017-12-21 07:06:21 UTC,Boot from volume server could not be recovered until running tgt-admin command again.
1731984,2017-12-21 08:09:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529500"
1731986,2018-05-02 12:02:02 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1731986,2018-04-20 13:14:45 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1731986,2018-04-20 00:33:43 UTC,"Reviewed:  https://review.openstack.org/545973
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb54ccf55ce9b3dbeefde03b68464bc0e450684e
Submitter: Zuul
Branch:    stable/ocata"
1731986,2018-04-02 13:18:54 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1731986,2018-03-07 23:30:30 UTC,This issue was fixed in the openstack/nova 17.0.1 release.
1731986,2018-03-06 19:40:30 UTC,"Reviewed:  https://review.openstack.org/546158
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c65dfeecaec23c0fa1cefd5f72c56faa7589216b
Submitter: Zuul
Branch:    stable/queens"
1731986,2018-03-06 16:15:23 UTC,"Reviewed:  https://review.openstack.org/546157
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=02acd2d1bc4ad6ba4863cfd35dbaa40510d8454d
Submitter: Zuul
Branch:    stable/queens"
1731986,2018-03-30 17:47:45 UTC,"Reviewed:  https://review.openstack.org/545966
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=17b9b900a249f6f432552fe27a9cdd54c1495b99
Submitter: Zuul
Branch:    stable/pike"
1731986,2018-02-20 17:27:17 UTC,"Reviewed:  https://review.openstack.org/520158
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=289d2703c75123216d0a6802f2fe5f41aa84407c
Submitter: Zuul
Branch:    master"
1731986,2017-11-13 20:12:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519464"
1731986,2017-11-15 16:01:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/520122"
1731986,2018-03-06 16:15:01 UTC,"Reviewed:  https://review.openstack.org/545961
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7ab98b5345f4a023bd209e714cd0aa60b3a31d48
Submitter: Zuul
Branch:    stable/queens"
1731986,2017-11-15 17:49:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/520158"
1731986,2018-02-19 20:03:39 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/545966"
1731986,2018-02-19 19:32:09 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/545961"
1731986,2018-02-19 20:32:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/545973"
1731986,2018-02-20 02:12:20 UTC,"Reviewed:  https://review.openstack.org/520122
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad389244ba5737d01f0c28e6704fc93b83dace9e
Submitter: Zuul
Branch:    master"
1731986,2018-02-20 14:11:05 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/546157"
1731986,2018-02-20 14:11:21 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/546158"
1731986,2018-02-19 20:23:45 UTC,"Reviewed:  https://review.openstack.org/519464
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bca425a33f52584051348a3ace832be8151299a7
Submitter: Zuul
Branch:    master"
1731994,2017-11-13 18:46:05 UTC,Is this a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1730444 ?
1731994,2017-11-14 02:53:08 UTC,"Hi Steve,"
1731994,2017-11-18 01:41:30 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-November/088330.html
1731994,2017-11-18 01:49:36 UTC,I built test kernel based on the pull request above:
1731994,2018-01-09 19:07:33 UTC,This bug was fixed in the package linux-azure - 4.13.0-1005.7
1731994,2017-11-18 01:11:25 UTC,"Hi, Josh."
1732000,2017-11-13 20:07:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/519462"
1732000,2018-02-01 21:27:42 UTC,"Reviewed:  https://review.openstack.org/519462
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=53dc0917c57243ba96845b4ba72f4069ee0d21ac
Submitter: Zuul
Branch:    master"
1732000,2018-02-09 07:13:30 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1732002,2018-05-14 22:45:29 UTC,Verification-done on artful: nplan 0.32~17.10.4
1732002,2017-11-13 19:51:44 UTC,"Yeah, i guess it is, given steps to reproduce are all in one go."
1732002,2018-06-06 01:10:38 UTC,This bug was fixed in the package nplan - 0.32~16.04.5
1732002,2018-06-06 01:09:55 UTC,"The verification of the Stable Release Update for nplan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1732002,2018-06-06 01:09:38 UTC,This bug was fixed in the package nplan - 0.32~17.10.4
1732002,2018-05-14 22:34:42 UTC,Verification-done on xenial: nplan 0.32~16.04.5
1732002,2018-05-08 21:09:05 UTC,"Hello Scott, or anyone else affected,"
1732002,2018-05-08 20:49:14 UTC,"Hello Scott, or anyone else affected,"
1732002,2018-05-08 14:48:52 UTC,This got landed in netplan.io 0.35 in bionic. The changes still should be part of a SRU.
1732002,2018-04-11 00:37:20 UTC,The MP has been moved to a github PR:
1732002,2017-11-13 19:51:19 UTC,"I can't remember if the host kernel also has changed defaults, thus host kernel might be a spanner in the works too. All of the above was tested on the same host kernel, right?"
1732002,2018-04-09 22:22:43 UTC,"I'd like to +1 what cyphermox said, the expected behavior on Ubuntu is that if you do receive a RA, you let the kernel configure it."
1732002,2018-04-09 20:11:01 UTC,"The kernel value is equivalent to not writing it out, yes; I thought it'd be better to be explicit in the config."
1732002,2018-04-09 19:54:10 UTC,"What's the point of having 'kernel'? You have a boolean here specifically because you'll likely want to override the default, whatever it might be. I'm fine with *not writing* accept-ra if that helps, but for most cases, this is just the kind of option that people should avoid touching."
1732002,2018-03-19 20:39:12 UTC,It would be nice for both nplan and networkd to accept a tri-state:
1732002,2018-04-09 22:42:16 UTC,"Guys, I'm no longer suggesting that we disable RA here.  After our
discussion I updated this bug
to indicate that we really want some way to *leave* RA alone."
1732002,2018-03-19 20:36:55 UTC,"After some discussion, it appears that networkd is kinda of making a boolean (on|off) for IPV6 RA, when it's really a tri-state (on|off|kernel)."
1732002,2018-02-26 17:05:17 UTC,"I've got a branch which would have cloud-init disable accept-ra unless cloud-init has an explicit ipv6 configuration (static or dhcp6).  This only affects the solicitation effort, ipv6 link-local is of course, unaffected as is explicit ipv6 configuration.  I believe LXD is in a position to know if it has an ipv6 enabled bridge; it could control the template to use a dhcp6 config instead of dhcp (which is ipv4) and not the unconfigured IPV6 RA, which on older releases like Xenial and Trusty won't see without configuration anyhow."
1732002,2017-11-13 19:52:22 UTC,"I wonder if cloud images need to ship an extra netplan snippet to disable ipv6 addresses by default, of if netplan default need changing, or kernel default needs changing....."
1732009,2017-11-13 19:59:35 UTC,"It may be this is not actually a bug, since (= 0.0 -0.0) is true.  Floating point operations can return slightly different values when inlined anyway."
1732009,2018-02-16 20:38:13 UTC,Another example:
1732011,2017-11-13 20:06:37 UTC,"Hello Jan,"
1732011,2017-11-14 09:32:44 UTC,"The problem with this is that i use an option in XFCE which cut the
window border and title at fullscreen. So when i use qpdfview fullscreen
the title with the current page is not shown."
1732011,2017-11-16 06:23:26 UTC,"Hello again,"
1732011,2017-11-16 11:00:26 UTC,"Yes i personally disable that as well, because i mostly use the arrow
keys + modifiers to scroll or zoom."
1732013,2017-11-13 20:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1732018,2020-08-10 02:45:44 UTC,collada-dom2.4-dp-base 2.4.4.7-ubuntu1~trusty1
1732018,2018-02-01 16:07:56 UTC,"A workaround for this problem is
pkg -i --force-overwrite /var/cache/apt/archives/libcollada-dom2.4-dp0_2.4.4+ds1-1_amd64.deb
pkg -i --force-overwrite /var/cache/apt/archives/libcollada-dom2.4-dp-dev_2.4.4+ds1-1_amd64.deb
apt-get -f install"
1732018,2018-02-01 15:53:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732020,2017-11-13 21:00:08 UTC,This change was made by a bot.
1732020,2017-11-14 20:58:15 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1732026,2018-01-15 15:35:19 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1732026,2018-01-15 17:54:38 UTC,"I believe it is a bit premature to mark this as invalid, due to an external (non ubuntu) website telling 17.04 has reached end-of life."
1732026,2018-01-16 16:19:07 UTC,"you are right, but:
- ubuntu has set 17.04 EOL itself
- btrfs is still in his early days; so not really linked to the package report
- and no one else but you has pointed that issue"
1732026,2018-01-16 16:53:01 UTC,"This should not just be closed because Zesty has become end of life, this sounds like a real bug and the update-manager code around snapshots has not changed at all recently."
1732028,2018-07-19 13:59:12 UTC,"I worked on the two messages and related boot messages:
1. the ordering cycle is about media-root, maybe the config is not yet perfect
2. timeouts on
     dev-ttyS0.device
     dev-disk-by\x2dlabel-UEFI.device
Hmm, that is:
  Dependency failed for /boot/efi.
  Dependency failed for Local File Systems.
  local-fs.target: Job local-fs.target/start failed"
1732028,2018-07-19 16:03:11 UTC,"In a discussion with smoser we decided to try just clearing /etc/fstab - it might be sufficient for our test intention and at the same time avoid the issue.
With that done we still have the following failing with timeouts:
  [ TIME ] Timed out waiting for device dev-ttyS0.device.
  [FAILED] Failed to start Journal Service."
1732028,2018-07-19 16:04:30 UTC,"Due to snapd still lopoing in this case (bug 1782602)
The sum of changes is:
$ systemctl disable snapd.seeded.service
$ systemctl disable snapd.service"
1732028,2018-07-19 18:07:45 UTC,Note to myself: WIP at https://code.launchpad.net/~paelzer/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/mask-uefi-part-to-unbreak-tests
1732028,2018-07-20 05:36:58 UTC,"2.0.874-5ubuntu5 migrated and had the first good new run.
Retriggering all those currently blocked on it ..."
1732028,2018-07-19 23:46:42 UTC,This bug was fixed in the package open-iscsi - 2.0.874-5ubuntu5
1732028,2018-07-19 13:08:10 UTC,"i attached as reference
 https://hackmd.io/E0ydu7Y7QEe-kroPb6-OOA
at some point we can improve the doc in the debian/tests directory with that."
1732028,2018-07-20 06:38:43 UTC,"\o/
All worked on the first run now, this gives some confidence that the flakyness is gone for now."
1732028,2018-07-19 18:40:32 UTC,First good run: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-ci-train-ppa-service-3325/cosmic/amd64/o/open-iscsi/20180719_180433_98a21@/log.gz
1732028,2018-07-19 12:11:13 UTC,"Running just with tgt-boot-test in interactive mode, no user-data and no extra disk.
Issue still reproducible with that."
1732028,2017-11-22 20:49:48 UTC,"Well, I tried updating /etc/fstab
 https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/fix/get-journal-publish-artifacts"
1732028,2018-07-19 11:01:03 UTC,"FYI: In Cosmic this currently blocks (and will block more soon due to python bound on it): qemu, debconf, python3, targetcli-fb, netifaces"
1732028,2018-07-19 11:00:37 UTC,"There also was a slight remaining uncertainty if this might be the detection of KVM being broken and running in nested KVm on Launchpad.
But I was able to confirm that it runs as intended in TCG mode:
   should_try_kvm = no. virt=kvm (nested kvm is finicky). set _USE_KVM=1 to force."
1732028,2018-07-19 11:00:26 UTC,I could confirm that I can run the guest that way and it uses the intended root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-b7X8g2-lun-1-part1.
1732028,2018-07-19 11:00:13 UTC,CE: Moving over some of the discussion that started on a related MP [1].
1732028,2017-11-22 22:19:17 UTC,"Bummer.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171122_204418_8ac74@/log.gz
shows"
1732028,2017-11-22 17:03:52 UTC,"It looks like:
 x-systemd.device-timeout=
might be useful
https://www.freedesktop.org/software/systemd/man/systemd.mount.html"
1732028,2017-11-22 16:57:49 UTC,"Is there a way to bump that 1m30s timeout  from the kernel command line?  Even image modification would be ok, as we're already modifying the image to insert the deb."
1732028,2017-11-22 16:56:24 UTC,"Note that this failure could just be due to slowness at this point.
The open-iscsi tests that are running are running in nested qemu with kvm disabled.  So it is quite slow to boot."
1732028,2017-11-17 15:36:29 UTC,"Another fail log at
 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171114_192057_17bf1@/log.gz"
1732028,2018-07-19 11:04:14 UTC,"It does not consume ""a lot"" of CPU but lets try still to slow it down into the error.
$ sudo apt install cgroup-tools
$ sudo cgcreate -g cpu:/cpulimited
# you might want to ensure that cpu.cfs_period_us: 100000
# e.g. Set 10% as hard limit
$ echo 10000 | sudo tee /sys/fs/cgroup/cpu,cpuacct/cpulimited/cpu.cfs_quota_us
# This was done on the Host, all tests run in the qemu guest (as on LP), move qemu in those cgroups
$ for task in $(ls -1 /proc/$(pidof qemu-system-x86_64)/task/); do echo $task | sudo tee -a /sys/fs/cgroup/cpu,cpuacct/cpulimited/tasks; done;"
1732029,2017-11-20 08:34:17 UTC,"Possible upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=197147"
1732029,2017-11-16 15:11:31 UTC,I can’t work out how to add the tag kernel-bug-exists-upstream?
1732029,2017-11-16 14:19:35 UTC,Using this kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
1732029,2017-11-14 21:12:24 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1732029,2017-11-13 22:30:08 UTC,This change was made by a bot.
1732029,2017-11-16 14:10:00 UTC,I just tried with the kernel here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732034
1732034,2017-11-16 14:06:00 UTC,"14:04:42 ~ • uname -a
Linux andrewvos-desktop 4.14.0+ #1 SMP Wed Nov 15 00:02:10 EST 2017 x86_64 x86_64 x86_64 GNU/Linux"
1732034,2017-11-13 23:00:08 UTC,This change was made by a bot.
1732034,2017-11-14 08:28:59 UTC,Can you attach output of `cat /proc/asound/card0/codec\#0` *without* using dell-headset-multi?
1732034,2017-11-15 06:45:47 UTC,"Please try the kernel here,
http://people.canonical.com/~khfeng/lp1732034/"
1732034,2017-11-15 10:36:49 UTC,How do I try that kernel?
1732034,2017-11-16 03:34:19 UTC,"- Download the deb files in the URL
- Install them via `dpkg -i *.deb`
- Reboot into the newly installed kernel."
1732034,2017-11-16 14:05:44 UTC,That works perfectly thanks!
1732034,2017-11-20 07:30:41 UTC,https://lkml.org/lkml/2017/11/20/70
1732036,2019-03-18 14:53:23 UTC,Is this still valid bug?
1732036,2018-06-25 10:58:43 UTC,Looks like a problem when using swift backend in multi-tenant-store configuration (see the related bug mentioned in the description).
1732038,2020-07-01 21:13:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1732038"
1732038,2020-08-31 04:17:33 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1732061,2018-01-20 07:44:54 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1482
1732061,2017-11-14 02:52:21 UTC,use mount nas file server
1732062,2018-01-03 08:58:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530871"
1732062,2018-01-23 07:33:48 UTC,"Change abandoned by Qi Peng (<email address hidden>) on branch: master
Review: https://review.openstack.org/530871"
1732062,2020-04-24 13:33:42 UTC,"very old, n/a"
1732064,2017-12-12 03:35:18 UTC,"OK, thanks!"
1732064,2017-12-11 15:10:59 UTC,Summary: what you were hoping for isn't currently supported in cloud-init.
1732064,2017-11-14 17:29:28 UTC,Hi! Thanks for taking the time to file a bug!
1732064,2017-12-11 10:07:54 UTC,"The origin vm is destroyed and detailed msg collect from another vm is attached
This attach is collect by:"
1732067,2020-09-18 12:20:25 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/752676"
1732067,2020-09-18 11:03:44 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/752672"
1732067,2020-06-29 08:33:10 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/738397"
1732067,2020-06-23 07:19:00 UTC,"We are seeing ingress flooding occur due to enabling this fix on other networks. We have a VLAN based network, both attached and unattached to a DVR router. In both cases, on ingress the NORMAL action at table=60 is hit."
1732067,2020-06-23 07:13:50 UTC,This fix seems to break certain other scenarios by causing flooding in opposite direction: https://bugs.launchpad.net/neutron/+bug/1884708
1732067,2020-04-24 06:11:26 UTC,Is this truly fixed? The patch doesn't seem to fix the underlying issue at hand - ingress MACs (coming from br-vlan or br-tun) are NOT learned by br-int.
1732067,2020-03-30 18:52:09 UTC,"Reviewed:  https://review.opendev.org/710183
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fdc8987f791b24119ef22c434f8877df13bcdded
Submitter: Zuul
Branch:    stable/rocky"
1732067,2020-03-23 14:45:17 UTC,I can reproduce with firewall_driver=iptables_hybrid and dvr. I attached a patch that directs only packets from the gateway to the vm ports. All other packets from tunnels will hit the NORMAL flow in table 60.
1732067,2020-03-09 23:47:21 UTC,"Reviewed:  https://review.opendev.org/709410
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0255239ed5affd65568c33ba07cd72fb0b594449
Submitter: Zuul
Branch:    stable/queens"
1732067,2020-03-12 10:26:55 UTC,"Hi, guys"
1732067,2020-03-12 10:22:34 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/712640"
1732067,2020-03-11 14:23:45 UTC,"@Peter, I have confirmed it doesn't work for the case firewall_driver=iptables_hybrid. I also find it can't learn local MAC after applied this fix patch. In addition, I also find iperf3 pps test with 16 bytes UDP packet has noticeable packet loss rate."
1732067,2020-03-11 05:32:21 UTC,"Reviewed:  https://review.opendev.org/710184
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5578c7073fd454f2df43e0d728ba2a64de87fccf
Submitter: Zuul
Branch:    stable/stein"
1732067,2020-03-10 22:04:25 UTC,"Yi Yang, I don't think the purpose of this patch is learning the MAC address. The fix is implemented by adding a flow that sends traffic destined to a MAC directly to a specific interface, thus short-circuiting the default NORMAL action which (correctly) broadcasts the traffic to all interfaces except the incoming one."
1732067,2020-03-10 13:59:37 UTC,"Hi, Yulong, has this fix patch completely fixed this bug or just partially fixed it? My colleague tried this patch, but br-int can't learn MAC yet, what's wrong?"
1732067,2020-09-21 07:37:22 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.opendev.org/752672"
1732067,2020-03-22 13:47:45 UTC,"- I execute to patch the code according to the commit:
https://review.opendev.org/#/q/efa8dd08957b5b6b1a05f0ed412ff00462a9f216"
1732067,2020-09-25 15:40:59 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/738397
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1732067,2020-11-05 02:34:00 UTC,"Reviewed:  https://review.opendev.org/759363
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=88bbb58c80b9c888371e25267715b155851d9278
Submitter: Zuul
Branch:    stable/victoria"
1732067,2020-10-07 05:17:19 UTC,"Reviewed:  https://review.opendev.org/738551
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=959d8b6d73e2a6ab1a45c9a7b0b05ae163e650fc
Submitter: Zuul
Branch:    master"
1732067,2021-02-19 08:24:21 UTC,"With all the backports, neutron/Queens still exhibits unicast flooding, although, of egress traffic that is headed towards snat port (be it centralized or DVR).
E.g., other ports on br-int, sharing the same vlan are getting egress traffic from port, which is sending packets towards MAC that is not in fdb of br-int."
1732067,2021-02-11 14:05:27 UTC,"At least from an upstream openstack/neutron source code perspective, the fix was included in the 16.3.0 tag on the stable/ussuri branch two weeks ago."
1732067,2021-02-24 07:55:47 UTC,"@Eugene, can You open new bug for that ingress traffic issue? And also can You check if that is also the thing in the master branch?"
1732067,2020-11-13 01:55:06 UTC,"Reviewed:  https://review.opendev.org/759369
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7fe3e3d1e04d206245480d28534d9ee11949a9fa
Submitter: Zuul
Branch:    stable/queens"
1732067,2020-11-12 13:42:44 UTC,"Reviewed:  https://review.opendev.org/759367
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7ce65c94786d2d144a49cb991575534d0771bb20
Submitter: Zuul
Branch:    stable/rocky"
1732067,2020-11-09 16:56:22 UTC,"Reviewed:  https://review.opendev.org/752676
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7842344a774b9cd098d07b65e410440e91cc8f3c
Submitter: Zuul
Branch:    master"
1732067,2020-10-30 21:28:01 UTC,"Reviewed:  https://review.opendev.org/759366
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7c757ad3372b5fe015ae4c5e3949c804e8515d20
Submitter: Zuul
Branch:    stable/stein"
1732067,2020-09-25 15:41:29 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/712640
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1732067,2020-10-30 21:18:00 UTC,"Reviewed:  https://review.opendev.org/759365
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c06895e8e78de06c25d36cb347313240432953cf
Submitter: Zuul
Branch:    stable/train"
1732067,2020-10-23 07:55:42 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/759369"
1732067,2020-10-23 07:52:43 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/759367"
1732067,2020-10-23 07:50:49 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/759366"
1732067,2020-10-23 07:50:28 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/759365"
1732067,2020-10-23 07:50:05 UTC,"Related fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/759364"
1732067,2020-10-23 07:49:31 UTC,"Related fix proposed to branch: stable/victoria
Review: https://review.opendev.org/759363"
1732067,2020-10-19 02:04:28 UTC,"Change abandoned by Yi Yang (<email address hidden>) on branch: master
Review: https://review.opendev.org/712640
Reason: https://review.opendev.org/#/c/738551/ has covered this, so abandon it."
1732067,2020-10-30 21:16:49 UTC,"Reviewed:  https://review.opendev.org/759364
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ef14d258eea91ef563c63334b2da1623d93418f3
Submitter: Zuul
Branch:    stable/ussuri"
1732067,2020-02-27 05:27:56 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/710184"
1732067,2021-02-11 12:17:14 UTC,Hi
1732067,2020-02-24 05:17:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/709410"
1732067,2019-07-25 12:41:08 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1732067,2019-06-23 16:41:54 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666991"
1732067,2019-04-19 06:09:07 UTC,This is also GREATLY impacting VM throughput if you have multiple VMs in the same neutron network on a hypervisor.
1732067,2019-04-19 06:08:12 UTC,"Note : an ARP request with broadcast ethernet address (ff:ff:ff:ff:ff:ff) will trigger MAC learning. This is used by VMs when the IP is not already in their MAC table. After what, they switch to unicast ARP requests, which _don't_ trigger MAC learning - so the FDB entry expires after 5 min (by default)."
1732067,2019-02-25 05:00:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639009"
1732067,2019-02-22 10:30:53 UTC,"I am also agree flooding is caused due to
- for egress trffic there is action=NORMAL
- for ingress traffic there is direct action=output:PORT
in the openflow rules."
1732067,2019-02-22 08:54:40 UTC,"After tested, It seems that this issue is caused by ovs-fw ingress flows with strip_vlan,output=<port_id> in table=81 and table=82.
When I ping VM's floatingip from outside. for example, floatingip for VM is 172.24.0.157, internal ip is 192.168.111.18/fa:16:3e:b2:c2:84, outside host IP is 172.24.0.3/e6:73:51:97:74:4e.
If outside host has no arp entry for 172.24.0.157, it will send arp broadcast, and br-int on host which VM on will update it's fdb entry."
1732067,2019-07-25 15:13:18 UTC,Is this related to bug 1837252? The symptoms seem very similar.
1732067,2019-02-20 10:55:32 UTC,"I modified the openflow, and it worked, no more flood packets.
cookie=0x85cd1a977dd54be0, duration=0.359s, table=82, n_packets=0, n_bytes=0, idle_age=518, priority=70,ct_state=+est-rel-rpl,tcp,reg5=0xd,dl_dst=fa:16:3e:80:cb:0a,tp_dst=22 actions=NORMAL"
1732067,2019-02-19 22:04:31 UTC,"This may have been resolved around the Pike timeframe, IIRC. Can you please confirm which version of OpenStack you’re using?"
1732067,2019-02-19 15:40:44 UTC,Also get the same. It looks like VM hosted on the same node as a victim VM may sniff all traffic and password/cookies/etc may then be leaked.
1732067,2019-02-15 02:11:55 UTC,"I also get the same problem, always no mac in fdb tables that cause tcp ack packet flood to other port, is there a solution for this problem?"
1732067,2018-09-21 13:21:43 UTC,"Nevermind, the fix with allowed_address_pairs only worked intermittently in our setup. I haven't successfully traced why it worked in some occasions and didn't work in others. Consider my previous advice invalid."
1732067,2018-09-20 16:06:22 UTC,"@james-denton, do you by any chance use such IP addresses inside your VMs that Neutron isn't aware of? We spotted the exact same behavior in our setup when we created Neutron ports with IP addresses A, B, C and additionally used IPs X, Y, Z inside the VMs."
1732067,2017-11-14 04:34:27 UTC,Just an update -- I was able to replicate this using neutron-openvswitch-agent 11.0.0.0rc2.dev368.
1732067,2020-02-27 05:22:24 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/710183"
1732067,2019-02-20 02:57:29 UTC,"My openstack version is Newton, can you confirm which patch solved this problem, thanks a lot !!
BTW，Not only same node‘s vm， the vms in different nodes also has this problem。"
1732067,2019-08-01 09:50:46 UTC,no this is not related to bug 1837252
1732067,2019-04-25 13:54:24 UTC,Note : I'm also seeing this behaviour with the iptables_hybrid firewall driver
1732067,2019-08-24 00:13:32 UTC,"@fungi,"
1732067,2020-02-21 16:41:08 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1732067,2020-02-18 11:18:31 UTC,This issue was fixed in the openstack/neutron 15.0.2 release.
1732067,2020-02-04 06:35:03 UTC,"Reviewed:  https://review.opendev.org/704506
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6c1cf886671df66f6790045268b1394a97caabcc
Submitter: Zuul
Branch:    stable/train"
1732067,2020-01-28 16:34:42 UTC,"Once the stable branch changes merge, this will be a class B1 report (default config value is insecure): https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1732067,2019-08-23 15:25:38 UTC,Hello:
1732067,2020-01-28 08:40:53 UTC,"Hi fungi,"
1732067,2020-01-28 08:33:11 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/704506"
1732067,2020-01-26 15:02:26 UTC,Is there any plan for backporting this fix to supported stable branches?
1732067,2020-01-28 16:29:53 UTC,"If mitigating this on some supported stable branches is going to require the operator to make configuration changes, then this is probably better handled as a security note than an advisory."
1732067,2019-12-11 14:18:00 UTC,"@James, yes, that's we called shared network. It can be used from different projects."
1732067,2019-12-06 13:26:33 UTC,"There are cases where the same network is shared across multiple tenants relying only on security groups to filter. So, I would say the broadcast of packets to all instances in the same vlan presented by this bug is less than ideal."
1732067,2019-12-06 08:35:09 UTC,"Hi Jeremy,"
1732067,2019-12-04 14:24:57 UTC,"It seems like bug 1841622 was opened for an alternative fix for this even though all the discussion about the problem happened here. The code change associated with that duplicate bug is currently active, but the bug is not marked as a suspected vulnerability like this one."
1732067,2019-12-04 08:32:51 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/639009
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns."
1732067,2020-01-26 13:34:21 UTC,"Reviewed:  https://review.opendev.org/666991
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=efa8dd08957b5b6b1a05f0ed412ff00462a9f216
Submitter: Zuul
Branch:    master"
1732067,2019-12-04 08:32:38 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1732067,2019-08-27 16:08:48 UTC,"We have an updated fix locally which can cover both enable/disable openflow security group (firewall).
I will update it to this patch set: https://review.opendev.org/#/c/666991/"
1732071,2017-11-14 17:29:25 UTC,This bug was fixed in the package courier - 0.78.0-2ubuntu1
1732082,2019-03-22 03:20:39 UTC,"'juju add-credential' operates on local cache only. It does not really matter to Juju if it is valid, besides there is no guarantee that Juju has access to the cloud to verify the credential before we have a bootstrapped system. There is no strict limitations on user - credential can be added locally before a cloud is, for example."
1732082,2019-03-22 13:50:04 UTC,I thought we do validate maas and openstack now when the credential is added with a test ping command. I'm not sure about the idea of a credential being added before the cloud is known as I think that currently errors since the cloud is require during add-credential?
1732082,2019-03-24 23:19:21 UTC,MAAS and openstack endpoints are validated during cloud addition via Ping.
1732082,2020-03-12 03:10:46 UTC,"Due to current priorities, I am not currently working on this bug, so I am un-assigning myself from it."
1732083,2017-11-16 13:03:21 UTC,"When there is a delay in getting the server response to display in grid, it may show ""No Service instances found"" message for a while but the service instances will be displayed in all cases.
Lowering the Priority as it's not affecting the functionality"
1732083,2017-11-28 14:08:15 UTC,"I am not able to reproduce issue. I am able to see service instance data without any message """"No Service instances found"""
1732095,2017-11-16 20:14:50 UTC,I can't reproduce the problem. It works well on a fresh install of ubuntu 17.10.
1732096,2019-06-04 03:54:13 UTC,"Hi, unfortunately I can't reproduce this problem with Inkscape 0.92.4. As there have been a number of fixes made, please try upgrading to the latest Inkscape version."
1732105,2019-09-16 14:08:09 UTC,Migrated to https://github.com/widelands/widelands/issues/2087
1732105,2018-04-19 04:12:06 UTC,"We should use mipmaps here, c.f. https://bugs.launchpad.net/widelands/+bug/1638356"
1732109,2019-09-16 14:01:05 UTC,Migrated to https://github.com/widelands/widelands/issues/2089
1732145,2019-04-22 02:52:05 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
Thanks."
1732145,2019-06-21 04:17:27 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1732150,2018-11-29 15:16:17 UTC,"Hi Simon,
I also ""came by"" here only every few weeks.
So I beg your pardon as I didn't realize it might be so clear.
OTOH there are a few steps needed to set this up for sure.
Thanks for pointing to the initial description of the nlnetlabs bug ."
1732150,2018-11-30 11:51:58 UTC,"To get this moving again and after Simons reply I was trying to set this up with potential copy and paste for anyone retrying.
But it doesn't reproduce the error on Bionic (where it should still happen), so please help me what is missing."
1732150,2018-11-29 14:43:54 UTC,The steps to reproduces are mentioned in [1]. One basically needs a unbound machine and 2 DNS servers that are master for a given zone. The idea is to then simulate an outage of one of the masters and see if unbound will still try to reach that dead master even after having received an answer from the surviving master. This attempt to query both causes delays because the dead one will of course never reply leading to a timeout. This bad behavior only manifested when domain-insecure was used.
1732150,2018-12-03 11:16:23 UTC,"Thanks for the hint Simon,
I have dropped the TTL to 10 and confirmed that the dig output has it as ""10"" through unbound.
Also I checked that the TTL drops per second and the query gets refreshed after those 10 sec expire."
1732150,2018-11-30 14:01:37 UTC,"I'm sorry Christian, I had the terminology wrong as you figured you need 1 master and 1 slave."
1732150,2018-08-28 06:05:12 UTC,FYI - final upstream fix was https://github.com/NLnetLabs/unbound/commit/52aeaf4924ec3f6689e6aafedbe41473d2bda992
1732150,2018-11-29 13:38:53 UTC,No feedback yet on helping how to test this which is a pre-req for the SRU process.
1732150,2018-05-21 20:47:15 UTC,Confirmed the patch from https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=2882#c7 is applied upstream.
1732150,2017-11-21 11:31:52 UTC,"Hi Christian,"
1732150,2017-11-20 09:58:33 UTC,"Hi Richard,
glad to hear that it helps."
1732150,2017-11-17 13:58:23 UTC,"Hi Christian,"
1732150,2017-11-17 12:29:08 UTC,"Hi again,
I made a ppa available to test.
Please take a look at: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3044"
1732150,2017-11-17 11:47:28 UTC,"This was fixed yesterday upstream and is not yet released anywhere.
For confidence in the change I'd prefer to wait for it to be released - not that they find issues in the fix."
1732150,2018-05-21 20:47:39 UTC,Dropping zesty as it's EOL.
1732153,2019-05-28 04:17:31 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1732155,2019-07-03 19:56:38 UTC,"It doesn't cover everything, but at least the defusedxml.lxml module is deprecated and it has been suggested libxml has been updated enough to no longer need this."
1732155,2018-03-13 17:40:21 UTC,"Reviewed:  https://review.openstack.org/519618
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=21362156125cadc0cddbffdc911d15a29c949902
Submitter: Zuul
Branch:    master"
1732155,2017-12-19 01:08:25 UTC,"Reviewed:  https://review.openstack.org/528516
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=4137c33922051546d45b6c9aa730433a401e3df1
Submitter: Zuul
Branch:    master"
1732155,2017-12-16 23:45:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528516"
1732155,2017-12-15 23:15:04 UTC,"Doesn't look like this will be an easy drop in and replace for most of the XML usage. There are a few easy replacements, but if this is really a concern, we will probably need to work with some of the driver maintainers to see how to best replace things."
1732155,2017-11-28 05:04:32 UTC,"Agreed with the class D triage, if there are no objections then let's open this bug and close the OSSA task by next week."
1732155,2017-11-15 15:42:11 UTC,"This bug is missing critical details: in particular, I don't see any mention of an actual attack vector. Is the implication that these drivers are handling untrusted XML data? And from where, the devices themselves? Who is the purported attacker, and how would this be used to their advantage? If there is no clear exploit scenario, we generally triage these sorts of reports as security hardening opportunities (class D in our taxonomy): https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1732155,2017-11-14 17:05:48 UTC,"As far as I can tell, this is constrained to a handful of Cinder drivers and their unit tests:"
1732155,2017-11-14 11:46:38 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1732155,2017-12-04 15:28:06 UTC,"As no objections were raised, I'm triaging this report as a security hardening opportunity now. Thanks!"
1732157,2017-11-17 00:39:23 UTC,"Just disable option ""Crop Image When Loaded"" in Settings --> Image processing."
1732158,2018-11-06 09:44:26 UTC,"I encountered this today when trying to upgrade a 2.4.3 controller to 2.4.4.  It is still stuck in the ""upgrade in progress"" state, hours later.  Uploaded diagnostics & logs to https://private-fileshare.canonical.com/~paulgear/lp1732158/"
1732161,2017-11-15 10:41:24 UTC,https://wiki.debian.org/Scanner
1732161,2017-11-14 11:27:18 UTC,I don't know what to do for Running scanner? Please Help.
1732161,2017-11-17 15:40:43 UTC,"Hi,
Can you provide details on the error seen during the scan initiate?
please capture the output of hp-scan -g and upload the file for review.
Thanks,
Badal"
1732165,2017-11-17 20:37:11 UTC,It seems what DBI delegates proper handling of data types to database driver and DBD/mysql.pm has this code:
1732165,2017-11-15 18:36:14 UTC,"Even for prepared statements, using placeholders in the queries, Perl driver is not respecting the binary data read from the table, in this case, the uuid field.
I ran tests even setting the filed type manually, but Perl DBI is still doing some internal conversion."
1732165,2018-01-24 22:42:13 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-405
1732165,2017-11-15 17:41:33 UTC,"There is a problem with the Perl DBI driver.
I tried to fix it or at least to find a workaround but I couldn't."
1732165,2017-11-15 18:16:40 UTC,"Carlos, can you explain what is the problem?"
1732175,2017-11-29 11:54:01 UTC,Agreed
1732177,2020-11-10 17:50:32 UTC,Which version of QEMU did you test? Does it work better with the latest version of QEMU now?
1732177,2021-01-10 04:17:40 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1732183,2017-11-14 21:34:50 UTC,"Probably not given that the release has to ready in just a few months.  Lots of moving parts, but it would help with the Unicode nonsense."
1732183,2017-11-15 10:44:03 UTC,"Thanks, Kenneth!"
1732192,2017-11-14 16:09:37 UTC,"I think to be useful, we need to be able to return interesting metrics even if things are under load. If we have some metrics that need DB access, then we should optionally skip them. Better to lose those metrics than lose visibility on the entire system."
1732207,2020-02-14 20:55:36 UTC,This has been addressed in Eoan and Focal images
1732207,2018-11-15 04:29:49 UTC,This is continuing to cause problems for new units we deploy on GCE.
1732212,2017-11-17 10:10:59 UTC,Same here:
1732222,2021-01-08 08:46:36 UTC,Any progress on this?
1732222,2018-09-01 04:01:13 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1732222,2018-05-28 18:19:49 UTC,"On 2018-05-25 22:49, David wrote:

> Still present on Ubuntu 18.04.
"
1732222,2018-05-25 20:49:47 UTC,Still present on Ubuntu 18.04.
1732222,2017-12-31 02:18:01 UTC,"On 2017-12-31 01:47, David wrote:

> Ubuntu 16.04 and above.
"
1732222,2017-12-31 00:47:04 UTC,Ubuntu 16.04 and above.
1732222,2017-12-31 00:32:56 UTC,@David and @Anthony: It would be useful to know to which Ubuntu version your observations relate.
1732222,2021-01-08 10:15:37 UTC,No.
1732222,2017-12-30 09:40:40 UTC,"If it installs all of the language packages in other languages, except for English-UK (and other non-US English locales), then it IS a bug."
1732222,2017-12-30 00:01:34 UTC,"Actually, this bug might be for gnome-language-selector.
If you have a look at your regional and language settings, it seems that so long as your chosen language is any variant of english, it suggests to install all the available language stuff (including libreoffice files) for ALL english possibilities."
1732222,2017-12-29 10:38:59 UTC,"When the user selects a different language to English-US (e.g. English-UK), all of the UK language packs should also be installed during installation. Maybe ubiquity is the focus of the bug report?"
1732222,2017-12-29 02:22:56 UTC,Perhaps this bug report is meant for the ubiquity ubuntu installer?
1732222,2017-11-14 23:24:21 UTC,"What package forms ""language support""?"
1732222,2017-11-14 20:21:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1732222,2017-12-30 21:37:35 UTC,"There is indeed an inconsistency between the installer and language-selector in this respect. The issue is reported in bug #1294858. That bug report is a bit 'noisy', but in comment #3 you find my idea for a solution and the reasons for it."
1732224,2019-09-19 11:59:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1732224,2017-11-23 09:00:36 UTC,@Lee
1732224,2017-11-15 17:08:08 UTC,@Bjorn
1732224,2017-11-15 15:52:39 UTC,"I don't think there's a problem with having the cards empty. If the controller isn't a machine, we can't run any hardware tests on it, so we will never have any metrics. However, currently the CPU and memory information is only available in the cards."
1732224,2017-11-22 17:20:12 UTC,Controllers may have metrics so we can't completely remove these cards. For example if a machine was converted to a controller or if power information was added to a controller so it could be tested.
1732226,2017-11-14 21:22:05 UTC,I remember I took a picture of the failed boot after the LM 18.2 upgrade. This is the same output after altering the firmware with the VM setting I shared about earlier.
1732227,2017-11-21 08:01:38 UTC,"Similar behavior occurs when setting the source/destination of a network policy. In a network policy/security group, for source/destination it is used ""FormHierarchicalDropdownView""."
1732237,2018-03-26 08:42:06 UTC,I can reproduce the two warnings with the testcase provided in comment #3 up to the 5-2016Q3 release but get only 1 warning (for test1) in 6-2016Q4.
1732237,2018-03-22 04:25:40 UTC,"Hi Thomas, do you still intend to look into this?
If so, please set status to something other than expired."
1732237,2018-01-22 08:55:15 UTC,"Hi Leo, this is an automated action from Launchpad as the message suggest it. My apologies but I haven't had time to have a look at it. I'll try to reproduce it on latest GCC development tree in the next week or so which will decide what is the next action."
1732237,2017-11-21 06:13:38 UTC,"I have created a minimal example for this. It has 2 functions: test1(), which does emit -Wlogical-op as expected, and test2(), where -Wlogical-op would be really nice to have.
The issue described is found in Silicon Labs EFM32 SDK, and can be seen here https://siliconlabs.github.io/Gecko_SDK_Doc/efm32gg/html/em__vdac_8c_source.html in line 197 and 203."
1732237,2018-01-21 04:17:16 UTC,[Expired for GNU ARM Embedded Toolchain because there has been no activity for 60 days.]
1732237,2017-11-15 09:42:21 UTC,"Hi Mike,"
1732237,2018-01-22 03:38:25 UTC,"Expired, why?
The testcase was provided as requested."
1732238,2017-11-14 18:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1732238,2017-11-17 15:30:06 UTC,This has been resolved with the following commits upstream:
1732238,2018-01-04 23:53:52 UTC,Example showing driver timeouts:
1732238,2018-02-14 09:37:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1732238,2018-02-14 20:16:33 UTC,Artful verification: I was able to successfully run the above stress-ng commmand w/o any errors on the console.
1732238,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1732245,2020-08-05 09:49:55 UTC,I found a work-around: disabling animations in GNOME Tweaks solves the issue and the whole Top Bar (not a ghost of it) and the Dock are visible for a very short time until the window becomes fullscreen.
1732245,2020-08-05 09:34:05 UTC,I think this bug might have already been fixed before Ubuntu 20.04 was released. So there's another reason to upgrade :)
1732245,2020-08-05 09:22:35 UTC,Thanks for the quick response!
1732245,2020-08-05 08:58:58 UTC,This bug is open again now so we don't need another report. Thanks.
1732245,2020-08-05 08:45:02 UTC,"Hey, Daniel! You sent me here from #1890281"
1732245,2019-11-21 16:38:11 UTC,Regression: when upgrading from ubuntu 19.04 to 19.10 this bug is back
1732245,2019-12-02 23:03:43 UTC,"Bug doesn't appear anymore on ubuntu 19.10, mutter packages are now at 3.34.1-1ubuntu1"
1732245,2018-04-06 13:21:46 UTC,"Note that Mutter fullscreen handling isn't fully fixed even for Xorg, see bug 1755501."
1732245,2020-08-05 02:25:53 UTC,It sounds like this bug was fixed before Ubuntu 20.04 was released. Can anyone else confirm?
1732245,2018-11-24 13:53:05 UTC,Please also see upstream reports: https://gitlab.gnome.org/GNOME/mutter/issues/397
1732245,2018-08-15 04:47:30 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1732246,2017-11-14 18:52:55 UTC,There are several reports in forums e.g. https://www.raspberrypi.org/forums/viewtopic.php?f=56&t=178073 https://ubuntu-mate.community/t/raspberry-boot/12065
1732246,2018-01-28 15:16:23 UTC,"I have reported it also but I found a solution, delete the kernel from boot that doesnt correspond to your device, for example if you have a rpi3b delete the kernel.img and if you have other rpi delete the kernel7.img and you will have space."
1732254,2017-11-15 08:09:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732254,2018-06-11 13:30:21 UTC,"I had the same problem, didn't test it for a while but now I don't see the problem any more. It seems that the bugfix from kernel 4.9.61 has made its way Ubuntu, closing this bug."
1732254,2018-06-11 15:17:09 UTC,Where can we find the evidence of this patch being backported into the current LTS kernel?
1732255,2019-09-17 10:28:56 UTC,Migrated to https://github.com/widelands/widelands/issues/2090
1732256,2019-09-17 10:29:27 UTC,Migrated to https://github.com/widelands/widelands/issues/3227
1732256,2017-11-17 07:53:28 UTC,I got some test results from AppVeyor builds from the Korean translator:
1732256,2017-11-16 17:38:13 UTC,"I'm getting he same crash with the latest AppVeyor build for 32 bit, 64 bit is fine."
1732256,2017-11-14 20:01:52 UTC,"Yes, it looks like bug 1720819."
1732256,2017-11-14 19:49:17 UTC,"This is almost certainly the SDL sound bug that is plaguing us for a while now. I cannot find it in our issue tracker, but this is a duplicate very likely."
1732256,2017-11-16 06:11:50 UTC,You could also try running Widelands with gdb for getting a backtrace:
1732260,2017-11-14 19:58:33 UTC,The workaround is not to use ThemableCheckboxSelectMultiple and to use CheckboxSelectMultiple.
1732267,2017-11-14 23:23:10 UTC,"Review in progress for https://review.opencontrail.org/37449
Submitter: Ananth Suryanarayana (<email address hidden>)"
1732267,2017-11-16 05:57:09 UTC,"Reviewed:  https://review.opencontrail.org/37449
Committed: http://github.com/Juniper/contrail-controller/commit/51f07ac6b602fd8276c636cdad4d5e31d508b4f9
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1732267,2017-11-20 21:04:15 UTC,"commit b89e149c80e165187524cf7772ffed356aa74022
Author: Ananth Suryanarayana <email address hidden>
Date:   Sun Nov 12 22:23:30 2017 -0800"
1732267,2017-11-26 04:47:16 UTC,"Review in progress for https://review.opencontrail.org/37866
Submitter: Ananth Suryanarayana (<email address hidden>)"
1732267,2017-11-28 05:24:46 UTC,"Reviewed:  https://review.opencontrail.org/37866
Committed: http://github.com/Juniper/contrail-controller/commit/0edf7958b8e33be776e2629ebcd348c0a81ec52d
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1732267,2017-11-28 19:47:30 UTC,"Review in progress for https://review.opencontrail.org/37934
Submitter: Ananth Suryanarayana (<email address hidden>)"
1732267,2017-12-10 04:28:12 UTC,"Reviewed:  https://review.opencontrail.org/37934
Committed: http://github.com/Juniper/contrail-controller/commit/092ea4f1d19401ab42947813d175f1844d405ae3
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1732268,2017-11-20 17:40:13 UTC,This is fixed in master since `Fri Oct 27 18:36:33 2017 +0200`
1732268,2017-11-14 20:30:32 UTC,"+ /tmp/go/bin/spread -v autopkgtest:ubuntu-18.04-amd64
2017-11-14 16:19:29 Found /tmp/autopkgtest.NevO5X/build.9NT/snapd-2.28.5+17.10/spread.yaml.
error: nothing matches provider filter"
1732268,2017-11-20 16:56:05 UTC,"Note that this is not a regression wrt the artful 4.13 kernel currently in bionic, so I will not block the kernel based on these failures. It would be nice if we could get some actual testing of snapd with 4.14 though."
1732269,2019-02-12 16:03:33 UTC,I too am trying to get duply/duplicity/B2 working but something is causing a 100% CPU lock-up.
1732269,2018-05-06 20:41:22 UTC,"I have the same problem as @cshelton1409, but it might not be the exact one reported in this issue. Many of my large backups fail. In my case, it looks like some sort of infinite loop where one core is utilized 100% forever, but no progress is made. Nothing relevant is recorded in the logs, even with verbosity 9."
1732269,2018-05-06 19:17:56 UTC,"I am also having nearly the exact same issue as in the description of this ticket.  I have been using duplicity 0.7.17 for the past several months, and have seen roughly half of my longer backups fail to complete.  I am using the b2 backend with 200MB sized volumes that are gpg encrypted.  The only difference for me is that when duplicity hangs, it is not using a significant amount of CPU.  The local system that is having this problem was running Ubuntu 17.10 when the issue began happening.  After an upgrade to Ubuntu 18.04, the same problem continues."
1732269,2017-12-11 15:48:17 UTC,"I did a quick diff on b2 repository, 0.7.0 & 0.7.2 should be ok, 0.7.4 - 1.1.0 are likelly to cause troubles (it maybe unrelated but they did some changes on how and when the sha1 checksum is computed and send)."
1732269,2017-12-11 12:41:08 UTC,Needs warning that b2 package should be installed at version 0.7.0.
1732269,2017-12-11 12:39:03 UTC,Thanks for the feedback.  Sometimes we screw up and it hurts everyone.
1732269,2017-12-09 18:53:45 UTC,"@kenneth-loafman
You were right; when I initially used pip to downgrade to b2 0.7.0, it left 1.0.0 in my path. After explicitly uninstalling b2 1.0.0 and then installing 0.7.0, the problem appears resolved. However, this begs a few more questions."
1732269,2017-11-30 09:08:55 UTC,"I have a very similar looking problem with the azure backend, on duplicity 0.7.12, azure-storage on 0.36.0. After 2-3 days of transfers, the backup is stuck. Last lines:"
1732269,2017-11-29 12:02:50 UTC,"It looks like you installed b2 originally from the repo, yes?  If so, pip may not be able to upgrade to 0.7.0, or will do so in a path that leaves the 1.0.0 version first on the path.  Did you uninstall the 1.0.0 version first?"
1732269,2017-11-28 23:50:11 UTC,"I confirmed the same problem occurs with python b2 version 0.7.0. Also, duplicity 0.7.14 with b2 1.0.0 works fine. It normally doesn't enter the infinite loop until after 2 or 3 volumes have been uploaded."
1732269,2017-11-16 15:54:08 UTC,I am running Linux Mint 18.2 (based on Ubuntu xenial 16.04 LTS). Full system specs are below. There is at least 12GB free memory for duplicity and it doesn't appear to be using much when it hangs. I am in the middle of a large backup right now (with 0.7.14) so I won't be able to upload a log using 0.7.15 for a couple days. I will try to get a more detailed strace too because there wasn't any useful information nor errors in the log.
1732269,2017-11-16 16:08:24 UTC,"Please try the 0.7.0 version of B2 first.  That might just save a lot of
debugging."
1732269,2017-11-28 22:54:28 UTC,Sorry for the delay. I have attached snippets of the duplicity log (verbosity 9) and an strace of the process right before it hangs in an infinite loop. Some of the names have been changed to protect the innocent. I will next test with b2 0.7.0 as suggested.
1732269,2017-11-14 21:58:52 UTC,@speedy37 -- Any idea what's going on here?
1732269,2017-11-14 23:11:24 UTC,"If it helps, here are the versions of python and b2-related packages installed on my system:"
1732269,2017-11-15 06:19:19 UTC,"No idea, I'm using my new B2 backend since a year now on about 500GB of data, no issue."
1732269,2017-11-15 14:46:32 UTC,"Try running a full backup with multiple volumes? B2 works fine for me with duplicity 0.7.14, but it fails for large backups after I upgrade to 0.7.15."
1732269,2017-11-15 15:06:13 UTC,"OK, let's see what's going on... I need some info:"
1732269,2017-11-15 15:10:58 UTC,full each month with about one hundred volumes of 1GB. I'm using https://hub.docker.com/r/speedy37/docker-duplicity/ (v0.7.11 with the new B2 backend).
1732269,2017-11-15 15:14:04 UTC,Also my b2 package version is older 0.7.0
1732269,2017-11-15 21:59:56 UTC,"Try installing B2 version 0.7.0 to see if it works, ""pip install -U
b2==0.7.0""."
1732272,2018-09-14 22:59:00 UTC,"works fine on osx now
https://github.com/mixxxdj/mixxx/commit/73d02e58bcd55ac4e0c3ce6047b28057629ddd7e"
1732272,2017-11-19 13:30:26 UTC,Will not be fixed for Mixxx 2.1.
1732272,2017-11-19 00:07:57 UTC,"@uklotzde, despite the print statements being fixed to be python3 compatible, the scons binary still needs to be called using python2 because of the util module. I agree it is a messed up situation and all of the python files need a close inspection to get them up to python3 standards."
1732272,2017-11-15 10:38:54 UTC,@Be I disagree. we curently have everything we need to build the application with scons 2.x on CI and build server.
1732272,2017-11-14 22:58:59 UTC,TODO: build/osx/OSConsX.py still contains many legacy print statements as a simple grep reveals.
1732272,2017-11-14 22:55:08 UTC,https://github.com/mixxxdj/mixxx/pull/1381
1732272,2017-11-14 22:16:43 UTC,"This should be already fixed in master:
https://github.com/mixxxdj/mixxx/pull/1361"
1732272,2018-04-23 00:09:33 UTC,SCons 3.0.1 fixed the issue with requiring python3 style print statements when running scons with python 2.7.x.
1732272,2017-11-14 22:10:15 UTC,...many legacy print statements :(
1732272,2017-11-14 22:08:19 UTC,Critical is for _application_ show-stopper bugs (i.e. crashes in the middle of a set doing normal things.)
1732272,2017-11-14 22:06:48 UTC,Next one fixed. But there are still print errors:
1732272,2017-11-14 21:59:01 UTC,"Thanks, imports fixed:"
1732272,2017-11-14 21:08:37 UTC,What happens if you remove/comment out the 'import util' line in mixxx.py?
1732272,2017-11-14 22:15:34 UTC,"If the application can't build at all, nothing about the application matters, therefore this is critical."
1732272,2017-11-14 21:08:10 UTC,https://stackoverflow.com/questions/12172791/changes-in-import-statement-python3
1732279,2017-11-24 05:52:10 UTC,"Hi Ruby,"
1732281,2017-11-24 05:46:02 UTC,"Hi Ruby,"
1732283,2017-11-20 15:07:26 UTC,"Approving this RFE, as it falls under driver feature parity category. Thanks."
1732284,2017-11-20 19:41:47 UTC,"Similar to the other rfes for drivers that don't support timeout (e.g. https://bugs.launchpad.net/ironic/+bug/1732283), I am approving this RFE as it falls under driver feature parity category."
1732284,2017-11-20 06:06:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521425"
1732289,2017-11-14 23:05:04 UTC,"Hi Alban, nice find, thanks for reporting this bug to us."
1732291,2017-11-15 10:45:21 UTC,This might be caused by the fact that during the bootstrap of the fuel master it somehow installs updated nauilgun. Since the issue disappears on 9.2 I'm setting the priority to medium.
1732294,2018-02-09 16:35:40 UTC,This issue was fixed in the openstack/neutron 12.0.0.0rc1 release candidate.
1732294,2018-02-02 16:13:28 UTC,"Reviewed:  https://review.openstack.org/520249
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=08108c41992a13c6959b717cccfe2b929e55d2eb
Submitter: Zuul
Branch:    master"
1732294,2017-11-16 18:45:25 UTC,"On 11/16/2017 07:35 AM, Brian Haley wrote:

> Sarah - is it possible for you to test my proposed change?  It's
> basically doing what you said - move the rules to the nat table
> PREROUTING chain.  Thanks.
>
"
1732294,2017-11-16 15:35:52 UTC,Sarah - is it possible for you to test my proposed change?  It's basically doing what you said - move the rules to the nat table PREROUTING chain.  Thanks.
1732294,2017-11-16 00:28:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520249"
1732294,2017-11-15 22:25:20 UTC,I'd recommend deploying the mitigation of moving the mac filtering rules to the ebtables nat PREROUTING chain rather than relying on a kernel fix.
1732294,2017-11-15 20:35:57 UTC,"Thanks for the heads up! It's our policy to go ahead and end embargoes once an issue is publicly disclosed, so we'll move forward triaging this as class C2 ""A vulnerability, but not in OpenStack supported code, e.g., in a dependency"" per our report taxonomy: https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1732294,2017-11-15 04:52:26 UTC,"Sure, it's better to be safe than sorry."
1732294,2017-11-15 04:23:29 UTC,"On 11/14/2017 07:11 PM, Tristan Cacqueray wrote:

> Contacting <email address hidden> with as much detail as can sounds like a
> good things to do, see https://www.kernel.org/doc/html/latest/admin-
> guide/security-bugs.html .
>
> IIUC, the load happen when an instance simply tries to spoof many new
> mac address? If so, that doesn't seems like something we need to keep
> under embargo and it could probably be easier to fix this issue in
> public.
>
"
1732294,2017-11-15 03:11:20 UTC,"Contacting <email address hidden> with as much detail as can sounds like a good things to do, see https://www.kernel.org/doc/html/latest/admin-guide/security-bugs.html ."
1732294,2017-11-15 02:54:34 UTC,"On 11/14/2017 05:01 PM, Tristan Cacqueray wrote:

> It sounds like a kernel bug... Neutron-coresec, could you check if the
> propose mitigation could be implemented?
>
> Sarah, maybe it would help to know what is the kernel version you are
> running?
>
"
1732294,2017-11-15 01:01:29 UTC,"It sounds like a kernel bug... Neutron-coresec, could you check if the propose mitigation could be implemented?"
1732294,2017-11-15 00:56:50 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1732294,2017-11-15 19:57:46 UTC,"On 11/14/2017 08:52 PM, Tristan Cacqueray wrote:

> Sure, it's better to be safe than sorry.
>
> For the record we do not have (yet) a hard limit on the acceptable
> duration of report embargoes. In the event we open a bug report, it will
> have to go through an embargo-exception first, as explained here:
> https://security.openstack.org/vmt-process.html#embargo-exceptions
>
> Also it's worth noting that vulnerability reporters retain final control
> over the disclosure of their findings. If for some reason they are
> uncomfortable with our process, their choice of disclosure terms
> prevails.
>
> Thanks.
>
"
1732301,2018-04-24 20:55:01 UTC,"this bug is only applicable to 3.0.3.5, other releases including 3.2.x.x are not exposed to this"
1732301,2017-11-24 20:30:24 UTC,"Reviewed:  https://review.opencontrail.org/37551
Committed: http://github.com/Juniper/contrail-controller/commit/d5f91c88bf258a7e5329154f873cda10c6cf606e
Submitter: Zuul (<email address hidden>)
Branch:    R3.0.3.x"
1732301,2017-11-15 00:07:55 UTC,Only affects 3.0.3.x
1732301,2017-11-15 21:39:25 UTC,"Review in progress for https://review.opencontrail.org/37551
Submitter: Suresh Vinapamula (<email address hidden>)"
1732302,2019-05-28 02:27:57 UTC,"I have fixed the script to check for the copy to clipboard button and verify that I should see ""1"" in the actual element instead of the row which also contains 1 in the title."
1732302,2019-05-28 02:30:00 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10047"
1732302,2019-06-08 21:06:48 UTC,"Reviewed:  https://reviews.mahara.org/10047
Committed: https://git.mahara.org/mahara/mahara/commit/b762a6d68bc9f18af9872941bb4ea92e4120dcdd
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1732313,2017-11-27 03:50:48 UTC,"From the description, it sounds like you are hitting following issue
https://jira.percona.com/browse/PXC-877"
1732313,2018-01-18 08:37:29 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2017
1732316,2018-05-02 12:05:25 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1732316,2018-02-15 23:53:55 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1732316,2018-02-24 04:49:15 UTC,"Reviewed:  https://review.openstack.org/519943
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9c26ad1717de62b3dc7b5211145091eb21e9b17
Submitter: Zuul
Branch:    stable/ocata"
1732316,2017-11-15 02:23:33 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/519943"
1732316,2018-02-05 15:45:06 UTC,"Reviewed:  https://review.openstack.org/519942
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ed11484b696e4af6f226029e88afe39277ea8e5e
Submitter: Zuul
Branch:    stable/pike"
1732316,2017-11-15 02:23:17 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/519942"
1732318,2017-11-15 10:43:20 UTC,I'm setting low importance since the upstream bug has the same.
1732320,2017-12-12 09:24:19 UTC,"[Tue Dec 12 16:31:08.031005 2017] [:error] [pid 88] Internal Server Error: /project/instances/
[Tue Dec 12 16:31:08.031056 2017] [:error] [pid 88] Traceback (most recent call last):
[Tue Dec 12 16:31:08.031069 2017] [:error] [pid 88]   File ""/usr/lib/python2.7/site-packages/django/core/handlers/base.py"", line 132, in get_response
[Tue Dec 12 16:31:08.031079 2017] [:error] [pid 88]     response = wrapped_callback(request, *callback_args, **callback_kwargs)
[Tue Dec 12 16:31:08.031086 2017] [:error] [pid 88]   File ""horizon/decorators.py"", line 36, in dec
[Tue Dec 12 16:31:08.031092 2017] [:error] [pid 88]   File ""horizon/decorators.py"", line 84, in dec
[Tue Dec 12 16:31:08.031098 2017] [:error] [pid 88]   File ""horizon/decorators.py"", line 52, in dec
[Tue Dec 12 16:31:08.031103 2017] [:error] [pid 88]   File ""horizon/decorators.py"", line 36, in dec
[Tue Dec 12 16:31:08.031110 2017] [:error] [pid 88]   File ""horizon/decorators.py"", line 84, in dec
[Tue Dec 12 16:31:08.031116 2017] [:error] [pid 88]   File ""/usr/lib/python2.7/site-packages/django/views/generic/base.py"", line 71, in view
[Tue Dec 12 16:31:08.031123 2017] [:error] [pid 88]     return self.dispatch(request, *args, **kwargs)
[Tue Dec 12 16:31:08.031130 2017] [:error] [pid 88]   File ""/usr/lib/python2.7/site-packages/django/views/generic/base.py"", line 89, in dispatch
[Tue Dec 12 16:31:08.031137 2017] [:error] [pid 88]     return handler(request, *args, **kwargs)
[Tue Dec 12 16:31:08.031143 2017] [:error] [pid 88]   File ""horizon/tables/views.py"", line 288, in post
[Tue Dec 12 16:31:08.031149 2017] [:error] [pid 88]   File ""horizon/tables/views.py"", line 223, in get
[Tue Dec 12 16:31:08.031157 2017] [:error] [pid 88]   File ""horizon/tables/views.py"", line 214, in construct_tables
[Tue Dec 12 16:31:08.031164 2017] [:error] [pid 88]   File ""horizon/tables/views.py"", line 129, in handle_table
[Tue Dec 12 16:31:08.031171 2017] [:error] [pid 88]   File ""horizon/tables/base.py"", line 1783, in maybe_handle
[Tue Dec 12 16:31:08.031193 2017] [:error] [pid 88]   File ""horizon/tables/base.py"", line 1616, in take_action
[Tue Dec 12 16:31:08.031200 2017] [:error] [pid 88]   File ""openstack_dashboard/dashboards/project/instances/tables.py"", line 621, in single
[Tue Dec 12 16:31:08.031209 2017] [:error] [pid 88]   File ""/usr/share/openstack-dashboard/openstack_dashboard/api/nova.py"", line 639, in server_confirm_resize
[Tue Dec 12 16:31:08.031216 2017] [:error] [pid 88]     novaclient(request).servers.confirm_resize(instance_id)
[Tue Dec 12 16:31:08.031222 2017] [:error] [pid 88]   File ""novaclient/v2/servers.py"", line 1755, in confirm_resize
[Tue Dec 12 16:31:08.031228 2017] [:error] [pid 88]   File ""novaclient/v2/servers.py"", line 2218, in _action
[Tue Dec 12 16:31:08.031235 2017] [:error] [pid 88]   File ""novaclient/v2/servers.py"", line 2229, in _action_return_resp_and_body
[Tue Dec 12 16:31:08.031241 2017] [:error] [pid 88]   File ""/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py"", line 294, in post
[Tue Dec 12 16:31:08.031263 2017] [:error] [pid 88]     return self.request(url, 'POST', **kwargs)
[Tue Dec 12 16:31:08.031270 2017] [:error] [pid 88]   File ""novaclient/client.py"", line 83,..."
1732320,2017-12-12 09:36:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527354"
1732320,2018-09-06 07:49:25 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/527354
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1732324,2018-01-24 22:36:01 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1457
1732326,2019-05-28 04:17:38 UTC,[Expired for kolla because there has been no activity for 60 days.]
1732326,2019-03-28 10:41:12 UTC,Is this still a bug in recent releases? If yes - please update.
1732333,2019-10-09 20:36:56 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it.
I'm closing it as ""Won't fix"", because we didn't do anything about this, but if you're still stuck there's probably a cause for this that isn't necessarily snapd itself and we can probably figure it out.
Again, sorry."
1732342,2017-11-15 05:30:31 UTC,"As far as I can tell this is broken through Bionic. I have a draft debdiff, I'm just getting some sanity checking on it before I attach it."
1732348,2017-11-15 07:23:07 UTC,"I haven't looked at the code but the change log states 'Use Option(""Inform"", ""OLDXML"") for keeping previous behaviour'"
1732348,2017-11-15 07:35:06 UTC,I'll take a look as I added this
1732355,2017-11-22 03:19:16 UTC,"We also need to solve a multi-cluster environment, where a single cluster consumes a message and other clusters cannot consume queue messages."
1732355,2017-11-21 09:55:03 UTC,"Yes, I have test it. the oslo.messaging will stop."
1732355,2017-11-15 07:04:11 UTC,"Hopefully, we can start the listener directly but current thread, the return value will be the Listener itself."
1732355,2017-11-18 03:38:30 UTC,"Before started:
http://paste.openstack.org/show/626669/"
1732358,2018-07-04 09:10:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732359,2017-11-15 07:28:47 UTC,It looks like the snap ships a symlink in meta/gui/vlc.desktop that points to a non-exiting file.
1732359,2017-11-15 15:55:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732361,2017-11-16 08:39:10 UTC,"https://errors.ubuntu.com/problem/15ca783f6a7903d6454e2849660253225d14d924
https://errors.ubuntu.com/problem/cf07c2fa3f39a98f0b52aaf20ff82faab7969129
https://errors.ubuntu.com/problem/ba56db6957c420f8db303e9e5bd63e0470414843"
1732361,2017-11-15 18:26:13 UTC,I don't recall do these end up getting bucketed? Could you provide an example? Thanks!
1732363,2019-11-10 21:12:10 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/520013
Reason: This looks abandoned so I'm going to drop it. This is also only modifying essentially tool/script code, not production runtime code, so it's very low priority to fix this IMO."
1732363,2019-11-10 21:13:18 UTC,"I'm going to invalidate this because the code being pointed out is just dev/test scripts, not production runtime code. It can be fixed if someone wants to restore and rework the patch but it's super low priority IMO."
1732363,2017-11-15 08:56:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520013"
1732368,2018-07-18 10:55:03 UTC,This bug was fixed in the package docker.io - 17.03.2-0ubuntu2~16.04.1
1732368,2018-07-10 22:49:38 UTC,"Per https://wiki.ubuntu.com/DockerUpdates, the passing autopkgtests are considered sufficient QA for docker updates and they all passed."
1732368,2018-07-05 23:04:32 UTC,"Hello Michael, or anyone else affected,"
1732368,2018-07-05 21:25:35 UTC,zesty is now EOL.
1732368,2018-07-01 21:37:58 UTC,"There is a new upload in UNAPPROVED that is waiting for review from Steve.
This version will not migrate so may as well remove it."
1732368,2018-06-29 15:15:50 UTC,Is this being tested? The package has been waiting in the -proposed pockets for 219 days now. Please perform verification in the nearest week or I will be removing it from -proposed as per SRU policy.
1732368,2018-04-10 20:51:46 UTC,"> The reason this is being done as a debconf question is because neither option is good. And *since* we are forced to ask the user to pick their poison, I consider it insufficient to ask this question only once. The question should by default be re-asked, at each package upgrade, so that the user has an opportunity to make the decision that is correct for them at that moment.
"
1732368,2018-04-03 23:33:26 UTC,"An upload of docker.io to xenial-proposed has been rejected from the upload queue for the following reason: ""See https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1732368/comments/8""."
1732368,2018-04-03 23:32:37 UTC,Comments on the debdiff:
1732368,2018-03-26 10:44:19 UTC,"I see a re-upload of docker.io for xenial (17.03.2-0ubuntu3~16.04.1) probably to address the mentioned issues. But I don't see the same upload for artful - does this mean that artful doesn't require a re-release? I would prefer forward-series to also have the same fixes, if applicable."
1732368,2017-11-30 17:38:25 UTC,Attached docker service logs where the fork/exec error can be seen. Some important times to consider:
1732368,2017-11-30 17:30:02 UTC,This fails for me on xenial after upgrading from Docker v1.13.1 to 17.03.2-ce from xenial-proposed. Here's what I did:
1732368,2017-11-21 16:40:20 UTC,"Hello Michael, or anyone else affected,"
1732368,2017-11-21 16:35:07 UTC,"Hello Michael, or anyone else affected,"
1732368,2017-11-21 16:22:51 UTC,"Hello Michael, or anyone else affected,"
1732368,2018-03-26 10:46:20 UTC,"I should have commented here before, I'm waiting for slangasek or infinity to review this one. There should be an artful upload yes but that can wait for a bit."
1732368,2018-07-18 10:55:06 UTC,"The verification of the Stable Release Update for docker.io has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1732371,2020-07-04 15:40:37 UTC,Thanks for reporting.
1732371,2017-11-15 23:55:05 UTC,*** This is an automated message ***
1732374,2019-08-11 15:29:36 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago. There have been many changes in Ubuntu and Firefox since that time.
1732374,2019-10-11 04:17:24 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1732380,2017-11-15 20:56:01 UTC,Hi Urpo
1732380,2017-11-16 07:06:43 UTC,"Hello,"
1732380,2017-11-19 06:23:09 UTC,"Robert, I think this would only go for the blocks on the dashboard page, i.e. everything below the ""Edit dashboard"" button as a user doesn't control the top part and the 3 dashboard info buttons can already be resurrected if removed."
1732381,2017-11-15 09:04:00 UTC,"Hello,"
1732381,2017-11-15 21:30:18 UTC,"Hi Urpo,"
1732381,2017-11-16 07:01:16 UTC,"Hello,"
1732381,2017-11-19 06:30:38 UTC,"Hi Urpo,"
1732381,2017-11-19 06:31:06 UTC,"As for the resetting of the homepage, the wishlist item is at #1732380."
1732385,2019-09-16 17:35:32 UTC,Migrated to https://github.com/widelands/widelands/issues/2091
1732391,2017-11-15 10:12:21 UTC,apport information
1732391,2017-11-15 10:12:20 UTC,apport information
1732391,2017-11-15 10:12:28 UTC,apport information
1732391,2017-11-15 10:12:19 UTC,apport information
1732391,2017-11-15 10:12:24 UTC,apport information
1732391,2017-11-15 10:12:25 UTC,apport information
1732391,2017-11-15 10:12:27 UTC,apport information
1732391,2017-11-15 10:12:23 UTC,apport information
1732391,2017-11-15 10:12:18 UTC,apport information
1732391,2017-11-15 10:12:15 UTC,apport information
1732391,2017-11-15 10:12:12 UTC,apport information
1732391,2017-11-15 10:10:23 UTC,apport information
1732391,2017-11-15 10:10:24 UTC,apport information
1732391,2017-11-15 10:10:25 UTC,apport information
1732391,2017-11-15 10:12:17 UTC,apport information
1732391,2017-11-15 10:12:13 UTC,apport information
1732391,2017-11-15 10:12:14 UTC,apport information
1732391,2017-11-15 10:10:26 UTC,apport information
1732395,2017-11-16 03:28:56 UTC,"It seems that If I want to deploy baremetal with local boot, the image must contain grub2 package."
1732407,2018-07-13 05:23:48 UTC,"@Richard Harding, John A Meinel,"
1732411,2017-12-15 13:19:41 UTC,Could you describe the minimal steps to reproduce the issue on top of a standard 16.04?
1732411,2017-12-12 21:24:01 UTC,"Marking the lxc task as invalid since LXC does not drop any such capabilities by default, so such failure isn't lxc's fault. It's either the user's fault (by dropping capabilities that Ubuntu/Debian consider as required) or the systemd's package fault (for not doing a capability check)."
1732411,2017-12-13 13:44:39 UTC,"From our analysis, we indeed agree with the fact that it has nothing to do with LXC (hence the report in the systemd tracker).
We believe that only the package is faulty here and should not attempt to blindly reexec systemd on upgrade."
1732411,2018-11-14 07:42:27 UTC,A fix [1] in LXC was pushed recently and actually allows systemd daemon-reexec without the cap sys_admin in a container.
1732414,2019-05-28 04:17:39 UTC,[Expired for kolla because there has been no activity for 60 days.]
1732414,2019-03-28 10:44:21 UTC,Is this still a bug in recent releases? If yes - please update.
1732424,2017-11-17 15:44:05 UTC,Will do.
1732424,2017-11-15 12:30:08 UTC,This change was made by a bot.
1732424,2017-11-17 15:30:46 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1732424,2017-11-19 23:34:20 UTC,"Hello again. I have tried to create the report you have requested... it is not at all clear to me who I should send it by mail, so I will attach it here and ask you who knows how to send it, please do so.
Thanks in advance"
1732424,2017-11-20 03:08:25 UTC,Can you attach the output of `cat /sys/power/mem_sleep`?
1732424,2017-11-20 08:37:38 UTC,"cat /sys/power/mem_sleep
[s2idle]"
1732424,2017-11-23 05:15:50 UTC,"Ok, I saw another bug you filed, it's about wifi issue."
1732424,2017-11-23 07:29:26 UTC,"no, it's not on the block list. on the other hand the problem of suspension
and hibernation is still there"
1732425,2017-11-20 02:53:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521403"
1732428,2019-04-06 01:17:31 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/524726
Reason: I'm not pursuing this."
1732428,2019-11-26 13:42:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/696084"
1732428,2019-11-26 14:06:48 UTC,"discuss was reopen here:
http://lists.openstack.org/pipermail/openstack-discuss/2019-November/011070.html"
1732428,2020-07-28 13:41:44 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/743537"
1732428,2020-09-02 14:54:25 UTC,"Change abandoned by yatin (<email address hidden>) on branch: master
Review: https://review.opendev.org/749035
Reason: In favor of https://review.opendev.org/#/c/749205/"
1732428,2020-08-17 15:30:13 UTC,"Reviewed:  https://review.opendev.org/696084
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8953a689467f8c3e996086392251de67953a45ba
Submitter: Zuul
Branch:    master"
1732428,2020-08-31 11:36:34 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/749035"
1732428,2020-09-01 08:54:06 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/749205"
1732428,2020-09-03 01:59:39 UTC,"Reviewed:  https://review.opendev.org/749205
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fe52b6c25bebdd1b459c7a59fbb8d9f6de200c9d
Submitter: Zuul
Branch:    master"
1732428,2020-07-31 14:01:17 UTC,"Reviewed:  https://review.opendev.org/743537
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ce2203456660083119cdbb7e73c1ad15e6e0a074
Submitter: Zuul
Branch:    master"
1732428,2018-09-19 16:57:57 UTC,More thoughts in the ML on my idea from comment 11:
1732428,2018-08-29 20:42:40 UTC,Removing myself as I'm not actively working on this.
1732428,2018-08-29 20:31:02 UTC,"@Sun, unshelve does not call finish_migration() so I'm not sure what you're referring to. I guess because of the relationship between resizing a server *after* unshelving it?"
1732428,2018-09-10 17:39:45 UTC,"Just thought of this, but nova does store the originally requested image_id in the request_specs table in the nova_api database - so if we needed to find that for whatever reason, we could. And then leave the instance.image_ref pointing at the actual current image that the instance is using (which could be a shelved snapshot)."
1732428,2017-12-01 16:54:09 UTC,"Looks like this was introduced with https://review.openstack.org/#/c/72407/ as maybe a way to pass the shelved image_id via the instance.image_ref field to the driver.spawn() method, but that doesn't make sense now."
1732428,2017-12-01 17:07:43 UTC,"Looking at the review comments on https://review.openstack.org/#/c/72407/, it looks like this was intentional:"
1732428,2017-12-01 17:16:28 UTC,Now I'm seeing this:
1732428,2017-12-01 16:51:12 UTC,Nice analysis.
1732428,2017-12-01 20:29:00 UTC,Thanks for the activity on this Matt. I don't think there's an obvious solution with only upsides for this problem.
1732428,2017-12-01 20:54:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524726"
1732428,2018-08-14 08:09:19 UTC,"I reproduced this bug and found that the directory of base file is stored in disk_info, which is used in finish_migration function. So, may be we can modify this parameter to rebase to original image."
1732428,2017-12-01 17:25:39 UTC,http://lists.openstack.org/pipermail/openstack-dev/2017-December/125124.html
1732445,2017-11-16 01:48:12 UTC,This bug seems to be referenced in the commit message of that change:
1732450,2017-11-16 09:32:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1732450,2017-12-06 09:57:59 UTC,This bug has now been reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=791299
1732450,2018-12-22 08:22:52 UTC,I can confirm the same behaviour persists on Ubuntu 18.10:
1732450,2019-02-17 13:12:59 UTC,I roughly understand this issue might be something to do with ubuntu-session package hard configuring the gdm login screen to use ubuntu.css?
1732450,2020-12-18 18:21:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732458,2019-07-17 17:19:24 UTC,"Reviewed:  https://review.opendev.org/521035
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5754f00ea8734a894e0c7963d46244ba7dc0dbe7
Submitter: Zuul
Branch:    master"
1732458,2017-11-17 09:27:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521035"
1732464,2020-07-24 07:56:41 UTC,Lets's Fix by ourself
1732464,2020-10-13 12:59:53 UTC,I am also having this issue with Jenkins 2.249.2.  Submitting a build using the python-jenkins module results in a 403 error from Jenkins which is behind an nginx proxy.  The same request submitted using the HTTP GET method *will* work as shown below.
1732465,2017-11-15 14:55:17 UTC,https://review.openstack.org/#/q/topic:check_ceph_status_warning_details+(status:open+OR+status:merged)
1732465,2019-05-30 12:02:51 UTC,Marking the charm-ceph task wontfix as the ceph charm has been removed from support for a while now
1732473,2017-12-15 08:59:58 UTC,"Hi all,"
1732480,2018-06-07 19:54:14 UTC,"I have not seen this one for a while. Marking it as incomplete, so it will close in 60 days (iirc) unless we can find another case."
1732481,2017-11-17 07:51:06 UTC,"Sorry for the late answer. This looks pertty valid, and I think we should do it by default, or at least wire it in the group vars to automatically do it on certain conditions, like if the security role isn't disabled. Major, an opinion?"
1732481,2017-11-20 13:37:47 UTC,So far I don't know how much impact does this configuration change have to qemu. Though it may be related to apparmor misconfigurations I received lately (eg. https://bugs.launchpad.net/nova/+bug/1728563).
1732481,2017-11-24 10:30:33 UTC,Update:
1732481,2018-05-03 05:14:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/565958"
1732481,2019-05-27 00:23:45 UTC,"Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: master
Review: https://review.opendev.org/565958"
1732482,2020-02-19 21:20:31 UTC,"I opened a bug 1863897 that is now closed as a duplicate of this one which concerned the A2HS (add to home screen) functionality of PWAs (progressive web apps). If you use the A2HS functionality it should create a desktop icon and open the PWA in a Chromium standalone window that looks similar to a desktop application. However as per this bug, it does not work."
1732482,2020-04-04 21:44:08 UTC,"If the snap chromium is connected to removable-media, the shortcut is correctly placed in ~/Desktop."
1732482,2020-04-04 21:52:55 UTC,Replacing in Exec=
1732482,2020-04-23 07:03:44 UTC,Confirmed on 81
1732482,2020-05-21 23:15:43 UTC,"Not working for me with Chromium 81, snap version, on Ubuntu 20.04. (Testing with music.youtube.com and twitter.com)"
1732482,2021-01-21 21:51:49 UTC,"@Sebastian Bacher - genuine question: does not a single person in the chromium-snap team use this feature? Because I can't think of any other reason why this regression (when compared to regular chromium) is treated like a 'wishlist' item. Please, enlighten me."
1732482,2020-08-12 22:24:31 UTC,"I added a workaround to the askubuntu post.
https://askubuntu.com/a/1266706/612"
1732482,2020-10-31 16:10:07 UTC,"The workaround is only part of the solution, the link still opens as a tab in regular chromium window rendering it useless. PWA's are still broken for now since they are supposed to launch as a separate 'application' they way it works in the non-snap version of chromium."
1732482,2020-11-24 21:25:08 UTC,"Such a shame users are being pushed towards regular Chrome, since that's the only feasible 'solution' to this bug for most users. Personally, I've completely given up on Chromium for Ubuntu 20.04+."
1732482,2019-10-30 14:25:22 UTC,"There's another problem I'm not sure if is related: even if the icon is well handled, the opened window will not show as an individual one on taskbar - it will still recognized as a window of Chromium itself with a Chromium icon. On the deb version of Chromium is works correctly."
1732482,2020-05-25 09:07:04 UTC,"As per the views on https://askubuntu.com/questions/1233058/chromium-snap-on-ubuntu-20-04-some-webapp-shortcuts-not-working-workaround/1233059#1233059, this bug affects many more people than indicated here."
1732482,2019-10-27 18:20:26 UTC,"Actually, the shortcuts were leftovers from the correctly working Chromium on Ubuntu 19.04. After I removed the shortcuts, I can't recreate them using the standard procedure anymore."
1732482,2019-08-20 15:34:21 UTC,I want to highlight that @jonny-boy's comment could be considered a separate-but-related bug. The exec path being written out in these files is not optimal. Here's one that was just used for me:
1732482,2019-10-07 10:31:27 UTC,"It looks like the problem has evolved since it was originally reported.
Desktop files are now correctly created on $HOME/Desktop/, but there are (at least) two problems with their contents:"
1732482,2019-09-30 18:11:29 UTC,Right now ~/snap/chromium/current is a symlink to a specific version of Chromium. So placing icons and desktop files there will break each time Chromium is upgraded unless the files are copied from the previous version-specific directory to the new one.
1732482,2019-08-20 15:56:45 UTC,"I did get a "".desktop"" file to work by manually copying it from ~/Desktop to ~/.local/share/applications, on Ubuntu 18.04."
1732482,2018-05-21 13:09:44 UTC,"There's a discussion on the snapcraft forum at https://forum.snapcraft.io/t/how-to-expose-desktop-files-created-by-snaps-to-the-de/2853, but no recent input on it."
1732482,2018-05-20 18:32:29 UTC,"Any news on this? I am using chromium 66.0.3359.139 (283 stable snap) under Fedora.
The create shortcuts action created a .desktop file under ~/Desktop, which is not useful when using the Gnome shell.
The Exec part in the .desktop file points to /snap/chromium/283/usr/lib/chromium-browser/chromium-browser ...
which is not the right path for my installation. I replaced the path with /var/lib/snapd/snap/bin/chromium and the chrome app is now working after moving it to .local/share/applications manually."
1732482,2017-11-16 06:00:19 UTC,Appending $HOME/snap/chromium/current/.local/share to $XDG_DATA_DIRS allows gnome shell (and likely other DEs) to see the desktop files and to launch them using the chromium snap. Need to discuss how this can be approached with the snapd team.
1732482,2017-11-15 18:06:54 UTC,"Desktop files in $HOME/snap/chromium/current/.local/share/applications/ are not very useful on a classic desktop, as gnome-shell (or others DEs) won't find them there.
We could probably modify the xdg-desktop-menu script to write to a different location. But $HOME/.local/share/applications/ won't work, because the home plug doesn't allow reading/writing to dot folders."
1732482,2017-11-15 17:51:28 UTC,"And now the shortcut for https://example.org started working, mysteriously."
1732482,2017-11-15 17:43:14 UTC,"If I add usr/bin/xdg-desktop-menu and usr/bin/xdg-icon-resource to the snap, the errors go away, and indeed a desktop file is created in $HOME/snap/chromium/current/.local/share/applications/."
1732482,2017-11-15 16:54:01 UTC,"With logging enabled, when trying to create a shortcut I'm seeing this:"
1732482,2019-10-15 09:59:34 UTC,"Another problem that was mentioned in duplicate bug #1848126 is that the icons are created in ~/snap/chromium/current/.config/chromium/Default/Extensions/*/*/icons (along with a manifest file), but they are not correctly linked in ~/.local/share/icons/hicolor/, so they cannot be seen by the desktop environment."
1732483,2019-08-07 19:01:05 UTC,UI has been deprecated
1732484,2017-11-16 23:17:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732485,2019-06-10 13:42:46 UTC,Just adding a comment to confirm that the patch is required on Ubuntu 18.04.
1732485,2017-11-15 16:21:01 UTC,"The attachment ""Patch for HTTP::Body::XForms"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1732491,2018-08-01 13:34:51 UTC,I have now found some additional issues with this logic. If I start by deploying 3 units with monitor-count=1 (which I know if wrong) what happens is that all 3 units will bootstrap independently i.e. at the point at which they have what they consider to be sufficient hosts i.e. 1 a.k.a themselves. The problem is that if I then set monitor-count=3 it remains wedged and the only way to fix it is to delete 2 units and start again. The same is also True if I have N mon units with monitor-count=N and i scale out my ceph-mon application before updating monitor-count. I think the charm should be able to manage these scenarios somehow.
1732491,2019-12-10 08:03:02 UTC,"Change abandoned by Trent Lloyd (<email address hidden>) on branch: master
Review: https://review.opendev.org/624010
Reason: already fixed by 640345 instead"
1732491,2019-12-10 08:00:37 UTC,"This was fixed by:
https://review.opendev.org/#/c/640345/"
1732491,2018-12-11 06:29:19 UTC,Fix Proposed: https://review.openstack.org/#/c/624010/
1732491,2019-12-10 08:41:20 UTC,Changing to fix released as Trent indicates that it has already been fixed in the 19.04 charms.  Thanks for confirming!
1732491,2018-12-10 07:17:01 UTC,"The problem here is that both client_relation_joined and client_relation_changed hooks (which provides ceph keys & processes broker requests to create pools etc) check for ""if ready_for_service()"" before processing those requests."
1732491,2018-08-01 14:20:44 UTC,"I suspect that the best way to manage some of these issues would be to only allow the juju leader to bootstrap, as there can be only one ;-)"
1732491,2018-08-01 13:38:51 UTC,and https://bugs.launchpad.net/charm-ceph-mon/+bug/1784860
1732491,2018-12-10 07:17:52 UTC,"I also filed a bug that if expected-osd-count is not meant (or otherwise ready_for_service check fails), there is no juju status information to convey that information to the admin:
https://bugs.launchpad.net/charm-ceph-mon/+bug/1807652"
1732494,2017-11-22 02:26:45 UTC,"$ cat /var/lib/dpkg/info/snapd.prerm
#! /bin/sh"
1732494,2018-10-28 15:40:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732494,2019-10-15 11:28:16 UTC,Looking at the pre-remove script and at what the services are it seems that whatever happened on your system somehow removed those services from systemd.
1732496,2017-11-16 09:28:57 UTC,Thank you for your bug report. Unsure about specific debugging tips but upstream (who writes the software) might have more clues if you want to report the bug to them as well on https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-calendar
1732496,2017-11-17 14:42:18 UTC,The bug is submitted to Gnome Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=790503
1732496,2017-11-17 16:43:30 UTC,Thanks for sending to GNOME
1732504,2017-11-15 17:56:00 UTC,"Travis doesn't support uploading artifacts from pull requests:
https://github.com/travis-ci/travis-ci/issues/5579"
1732506,2018-10-10 23:26:13 UTC,"Reading through this, this bug looks valid to me. Setting to Medium based on the fact that a user has to delete an ironic node out-of-band from nova while the nova instance is building in order to encounter the bug."
1732506,2017-11-15 18:45:16 UTC,"Oddly, the main exception raised in the nova ironic virt driver when things go wrong is InstanceDeployFailure, but this is not referenced anywhere outside that driver except for the class definition in exception.py."
1732506,2017-11-15 18:35:58 UTC,"Agreed, we definitely want to still allow an asynchronous instance delete during build. I think that is the scenario that InstanceNotFound was meant to cover, but it has been incorrectly overloaded by the ironic virt driver."
1732506,2017-11-15 18:07:04 UTC,"Does seem like [2] should really be raising build failed, like the previous step."
1732512,2017-11-15 19:02:52 UTC,A test kernel with the indicated patch set has received positive smoke test results from Amazon and myself:
1732512,2017-11-20 11:53:47 UTC,This bug was fixed in the package linux-aws - 4.4.0-1041.50
1732512,2017-12-07 18:25:32 UTC,This bug was fixed in the package linux-aws - 4.4.0-1005.5
1732512,2020-12-01 17:44:23 UTC,This bug was fixed in the package linux-aws - 5.8.0-1014.15
1732512,2021-01-11 14:58:42 UTC,This bug was fixed in the package linux-aws - 5.8.0-1018.20+21.04.1
1732513,2017-11-22 21:08:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732513,2017-11-22 21:10:26 UTC,For me it happens exactly the same. I have Ubuntu 17.04 and today is the first time that happens and the first time I open Virtualbox this week.
1732516,2017-11-15 19:21:06 UTC,"oh, and here's a backtrace:"
1732522,2019-02-25 19:56:33 UTC,Is this still an issue that needs cloud-init work?
1732522,2017-11-20 19:45:20 UTC,"This issue is discussed in a document at
 https://docs.google.com/document/d/14xH2Q3VH_7ArXzRPhqogfACeOI0rmEinm_Q98imNWlc/"
1732522,2017-11-17 23:39:53 UTC,"I'm landing some debug logging in MAAS to help identify if this issue is occurring; regiond.log will contain lines like ""Lease update: ..."" when MAAS receives notifications about lease changes."
1732522,2017-11-17 22:55:57 UTC,Forgot to include the relevant portion of the cloud-init logs in my comment above.
1732522,2017-11-17 18:53:31 UTC,"Ok, I'm being unclear again. This is the behavior:"
1732522,2017-11-17 18:53:41 UTC,"Ok, I'm being unclear again. This is the behavior:"
1732522,2017-11-17 18:51:38 UTC,"Argh, the IP disappeared, but the machine still holds such IP in the *PXE* interface."
1732522,2017-11-17 18:51:15 UTC,"SO this is what I noticed, after about 10 minutes of running hardware testing, the IP disappeared of the PXE interface. See screenshots attached below."
1732522,2017-11-17 22:48:21 UTC,"After triaging this issue, I think we need to discuss the proper fix with the cloud-init team."
1732524,2020-05-13 16:12:44 UTC,Sadly Firefox no longer carries the required capabilities to expose it's menus so they are accessible via the HUD.
1732524,2020-05-08 13:48:18 UTC,I would like to confirm that this bug still exists for Firefox version 76 installed in Ubuntu 20.04. I raise this concern for two reasons.
1732534,2017-11-21 16:45:31 UTC,"In theory, at least with noop, deployment across routed networks can work today, so I think it is okay for us to go ahead and update the documentation now  to indicate the risk and the basic method of operation as to how someone might wish to use it. At the same time, we can recommend use of configuration drives. I see this as a paragraph or two in the documentation and a warning box in  for the security risk that exists."
1732534,2017-11-21 08:56:16 UTC,"This looks like documentation issue, I don't think we can do anything on Nova/Neutron/Ironic side.
Metadata may be configured in two ways with routed network:"
1732534,2017-11-20 16:01:28 UTC,"I suspect this may work out of the box depending on how an installation is architected, built, and configured networking wise. Some of the nova options allows the nova service to directly perform the source lookup and translate that to an instance-id in order to return the data, alternatively neutron can service the requests by using the 168.254.169.254 address (via nat/mangle rules https://github.com/openstack/neutron/blob/master/neutron/agent/metadata/driver.py lines ~169-191) on a router or dhcp instance, and then shifts the traffic to haproxy for the metadata proxy."
1732534,2017-11-20 18:24:43 UTC,"Thank you for the input, Julia. You bring up a good point about security of the metadata service, although I would rather that we document the exposure than assume that nobody would ever want that configuration. There may be closed environments where this architecture is desired and all tenants are trusted."
1732542,2018-03-26 05:33:44 UTC,"I'm using a customised MUTINY layout with the ""MATE Menu"" and that causes ""Untitled Window"" to appear in the topmenu bar.  Would be great to have that silenced too."
1732542,2018-06-21 10:37:26 UTC,"Yeah the global menu fails to recognize some of the things like this one, hence ""nameless window"". The global menu crashes and doesn't work properly until a reboot on some applications like VirtualBox, which can mean it doesn't do well with Qt4 apps."
1732542,2020-05-22 04:17:26 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1732548,2017-11-16 15:36:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732556,2017-11-16 17:08:26 UTC,Didn't know about the lack-of-separation point.  Sounds like it'd be pushing rocks uphill to try to get that to change.
1732556,2017-11-16 18:45:40 UTC,"Thx, I'll poke at those."
1732556,2017-11-16 18:10:40 UTC,"> (1) IS there a Raspbian UNstable repo, specifically with a newer JDK? either jdk8-nightly, or jdk9? Those _might_ have intentional, or inadvertent, fixes.
"
1732556,2017-11-16 16:43:20 UTC,There are a couple of issues here.
1732556,2017-11-16 16:08:06 UTC,"> Does this happen on actual arm hardware? If not then i'm inclined to say it is a bug in whatever emulator you are using and not a bug in raspbian per-se.
"
1732556,2017-11-16 15:38:51 UTC,Does this happen on actual arm hardware? If not then i'm inclined to say it is a bug in whatever emulator you are using and not a bug in raspbian per-se.
1732556,2017-11-16 15:00:22 UTC,"for ref,"
1732559,2017-11-16 10:11:42 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1732559,2017-11-18 06:12:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732562,2018-03-29 16:16:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732562,2020-05-07 14:41:40 UTC,Just got this issue on Focal:
1732566,2017-12-26 15:06:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732566,2020-05-01 20:14:16 UTC,https://bugs.launchpad.net/ubuntu/+source/protobuf/3.6.1.3-2ubuntu5
1732574,2018-03-17 03:48:51 UTC,The cause of this issue seems to be in fact Linux kernel 4.14.0-041400rc7 :
1732574,2017-11-16 02:30:48 UTC,This attachment is the relevant XorgLog.txt
1732578,2019-12-18 08:42:15 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1732578,2017-11-16 13:46:31 UTC,https://review.openstack.org/#/c/520275/
1732578,2019-03-05 13:36:47 UTC,Is this still needed?
1732580,2017-11-16 23:57:35 UTC,"Hi Jun, I think auto-rebalancing would impact existing traffic. From operational perspective, I would prefer balancing only for newly added lrouters without touching existing lrouters automatically. What do you think?"
1732580,2017-11-17 02:46:29 UTC,"Hello Han,"
1732580,2017-11-17 02:57:43 UTC,"Hi Han,
I raise this bug based on a realistic question. When we have two gateways and already a lot of lrouters, one of the ovn-controllers is upgraded, all the gateway-ports are scheduled to the other gateway and we can only rebalancing them   manually by setting OVN NB.
What you said made sense it's not easy to distinguish between different scenarios, I will add a command to do this first, and postpone automatically balancing until thorough discussions."
1732580,2017-11-18 02:20:58 UTC,"Yes, having a command to do the rebalancing would be great."
1732580,2019-06-04 14:19:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/663046"
1732580,2020-03-26 07:57:43 UTC,"Change abandoned by Maciej Józefczyk (<email address hidden>) on branch: master
Review: https://review.opendev.org/663046"
1732582,2018-04-06 09:09:36 UTC,We should mock out the HTTP calls.
1732582,2019-09-17 08:42:01 UTC,Has already been fixed.
1732585,2018-02-27 05:04:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732592,2017-11-16 16:28:23 UTC,logs are uploaded to ubuntu-build02 shared dir bugs/173259
1732592,2017-11-27 10:36:39 UTC,"Hi Anish,"
1732593,2017-11-16 20:29:16 UTC,Looks like this fixes it:
1732593,2017-11-16 20:39:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520765"
1732593,2017-12-05 13:33:03 UTC,"Reviewed:  https://review.openstack.org/520765
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0f464e55a856477a5b77ce8ce7efacf9bc139735
Submitter: Zuul
Branch:    master"
1732593,2017-12-05 14:31:36 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/525629"
1732593,2017-12-07 23:56:13 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1732593,2017-12-15 18:40:17 UTC,"Reviewed:  https://review.openstack.org/525629
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=761b15fd00d77d5e2fd6d163ba677b3c3105f9d7
Submitter: Zuul
Branch:    stable/pike"
1732593,2018-02-15 23:53:52 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1732594,2019-09-19 11:59:58 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1732606,2019-05-03 17:14:27 UTC,"Was  fixed in Bionic
---"
1732606,2017-11-16 07:02:58 UTC,"The advisory is already public, so there's no benefit in keeping this bug report private."
1732606,2017-11-16 10:07:39 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1732606,2017-11-17 06:19:12 UTC,"The patch proposed by the Shibboleth developers is simple enough and would appear to apply to earlier versions. Indeed, the bug has already been patched in Debian stretch (2.6.0+dfsg1-4+deb9u1) and jessie (2.5.3+dfsg-2+deb8u1) which appear to be the original packages from which these derive. The Debian bug report is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881857"
1732606,2017-11-23 05:58:05 UTC,This bug was fixed in the package shibboleth-sp2 - 2.6.0+dfsg1-4+deb9u1build0.17.04.1
1732606,2017-11-23 05:58:06 UTC,This bug was fixed in the package shibboleth-sp2 - 2.6.0+dfsg1-4+deb9u1build0.17.10.1
1732606,2017-11-23 06:13:13 UTC,"opensaml2 has been fixed in all releases (see https://launchpad.net/ubuntu/+source/opensaml2) except for the devel release (bionic), which will be addresses when the debian autosync pulls 2.6.1-1 from debian."
1732612,2018-04-25 11:27:15 UTC,"Same problem here, and workaround in #10 NOT working.
I confirm the OP's analysis: ALT+PrintScreen does not generate a keyboard event. Other Keystrokes (ALT alone, PrintScreen alone) do."
1732612,2019-10-22 18:30:05 UTC,Has this been fixed? I'm using Ubuntu 18.04 with gnome desktop and the ctrl alt print screen is not always reliable. I'm using Shutter as a work around for the mean while.
1732612,2018-10-29 16:15:52 UTC,This will be fixed soon.
1732612,2018-06-15 16:02:07 UTC,"Indeed disabling sysrq seems to fix the problem, but this has worked for donkey's ages so what exactly changed?"
1732612,2018-04-25 16:34:18 UTC,"#14: Thanks, that helped even though I'm not on a laptop. Your question is valid, something must have changed that caused this issue and even though your solution helps a proper fix is still needed."
1732612,2018-04-25 11:35:16 UTC,"Oh, I there's a typo in comment #10:
Workaround (2) should be"
1732612,2018-04-25 11:28:31 UTC,Addition: This is in Unity. On the GNOME desktop everything seems to work as expected.
1732612,2018-01-16 16:42:44 UTC,"This workaround works for me, but years of muscle memory..."
1732612,2017-12-13 09:21:22 UTC,@ khurshid
1732612,2017-12-13 07:04:56 UTC,"There is also this bug 1683383, not sure if it is related. But lots key shortcuts problems started to arrive after Ubuntu removed 6 year old patch from xorg."
1732612,2017-12-13 01:38:07 UTC,"@popey, have a look at bug 1707828. It shows Ctrl+Alt+T not working due to DBus timeouts and GSD problems. Quite possibly other key combos like Alt+PrtScn could suffer a similar fate."
1732612,2017-12-12 14:31:37 UTC,Alan Pope:
1732612,2017-12-12 11:52:40 UTC,"On my Unity session on 17.10 printscreen doesn't work, neither does ALT+Printscreen (it triggers HUD), nor CTRL+ALT+T to open terminal. Seems a bunch of them don't work."
1732612,2017-12-12 11:48:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732612,2017-12-12 11:41:37 UTC,"Not sure how any of this helps, I would require somebody with graphics/keyboard stack to understand what/where has regressed."
1732612,2018-01-11 09:47:49 UTC,Workaround (1):
1732620,2017-11-16 08:30:05 UTC,This change was made by a bot.
1732620,2018-09-12 18:44:43 UTC,"very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update."
1732620,2018-09-13 04:33:28 UTC,"This bug is still valid.
http://10.246.72.4/test-results/4.15.0-34.37-generic/lodygin__4.15.0-34.37__2018-08-29_07-34-00/monotonic_time-test-suite.html"
1732620,2018-09-28 13:43:11 UTC,"Still valid for azure : 4.15.0-1008.8 / Bionic ,"
1732620,2019-09-05 06:15:53 UTC,"For the record, node lodygin is out of order."
1732623,2018-07-22 20:40:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732630,2018-01-11 12:30:37 UTC,"Change abandoned by Chason Chan (<email address hidden>) on branch: master
Review: https://review.openstack.org/520424"
1732630,2018-01-11 15:16:29 UTC,This issue was fixed in the openstack/openstackdocstheme 1.18.0 release.
1732630,2017-11-16 11:11:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/520424"
1732665,2019-12-30 04:17:45 UTC,[Expired for juju because there has been no activity for 60 days.]
1732665,2019-10-31 04:09:10 UTC,Removing from a milestone as this work will not be done in 2.3 series.
1732665,2018-03-26 09:19:33 UTC,"The work that Witold is currently doing on VSphere does not directly fix this.
Specifically, we need to change from driving the firewall from outside of the machine, to having a worker running in the agent that is already on the machine, and having it drive the local iptables firewall.
Note that an on-instance firewaller would be useful in many other cases as well, not just in vpshere."
1732665,2018-03-06 15:06:58 UTC,# juju show-machine 1
1732665,2018-03-05 15:08:38 UTC,"@merlijn-sebrechts,"
1732665,2018-02-26 08:06:21 UTC,@Merlijn Andrew no longer works at Canonical but we'll start looking again into the issue in this bug this week.
1732665,2018-02-23 16:59:15 UTC,"Andrew, any update on this? Is it the expected behavior that the firewall doesn't work?"
1732665,2018-03-15 01:54:08 UTC,"We are actively working on this right now. However, the fix will not make the point release. I am adjusting the milestone and assigning bug to the person making progress in the codebase."
1732665,2017-12-07 01:48:25 UTC,"Merlijn, Mark: it appears that there's a regression due to us now being more strict about SSH host key verification."
1732665,2017-12-06 16:25:25 UTC,"What's the root cause on this, Andrew?"
1732665,2017-11-22 12:49:09 UTC,"I fixed the DNS issues. Now I don't get the `cannot resolve hostname` issues, but I still get the ""host key verification failed"" issue."
1732665,2017-11-19 19:19:57 UTC,"That might actually explain why I see both ""cannot resolve hostname"" and ""host key verification failed"". Juju probably first tries to login using hostname, that fails, resulting in the fallback to ip address, but the host keys are associated with the hostname, not the IP so host key verification fails..?"
1732665,2017-11-19 19:15:13 UTC,"John, do you need extra information from me? You can find the full log here: http://paste.ubuntu.com/25973402/"
1732665,2017-11-19 13:06:09 UTC,It would be good to understand where we were trying to SSH that we couldn't actually resolve the hostname.
1732665,2017-11-16 10:36:29 UTC,"Also, if `external-network` is not specified during bootstrap, the logs are spammed with this:"
1732665,2017-12-11 06:26:02 UTC,"https://github.com/juju/juju/pull/8200 fixes the regression by disabling strict host key checking, and fixing some iptables-specific bits. I'd like to leave this bug open so that we can do this at the machine agent level."
1732665,2018-01-17 14:36:33 UTC,This doesn't seem to fix the firewall.
1732680,2017-11-16 12:45:10 UTC,"This test was for a crash when using KHTML engine. Konqueror now uses QtWebEngine, so I'm not sure it it still has relevance."
1732683,2017-11-29 09:09:47 UTC,"Since all of this mostly concerns printf, one way to address this would be to add another version of printf formatter to newlib-nano. Basically, to split _printf_float into _printf_double and _printf_float. _printf_float would use single precision floating point instead of double precision. Something similar could be done with scanf."
1732683,2017-11-16 13:24:13 UTC,Developing such a feature would take a big effort and a long time. As you said the compiler needs to be changed and so does the C library. All the ramifications need to be considered. One needs to consider how many people would benefit. Newlib-nano already has a mechanism to have floating point support in printf and scanf optional which provides better reward (more code saved) for less work (change in compiler is only a nice to have to automate the selection of float code).
1732683,2017-11-17 11:19:10 UTC,"Hi John,"
1732684,2017-11-16 13:06:59 UTC,"So we have two AuthorizationFailures at the same line of code:
2017-11-16 13:36:33.998 776 ERROR oslo.service.loopingcall AuthorizationFailure: unexpected keystone client error occurred: The request you have made requires authentication. (HTTP 401) (Request-ID: req-1d28d2b8-a043-4ac4-b01f-1ce15f170c1e)"
1732684,2017-11-16 15:04:10 UTC,"The error: ""2017-10-26 15:12:56.275 20618 ERROR oslo.service.loopingcall AuthorizationFailure: reason Keystone API connection failed: no password, trust_id or token found."""
1732686,2017-11-20 10:40:58 UTC,Hi Kai.
1732686,2017-11-30 23:08:50 UTC,"Glad it worked for you. For anyone who has linux-stable on git (like me), if your kernel version lacks this, it's a matter of git cherry-pick 339ee3fcbdab736adbc30b7a3d675005c61a2a40 and there you go."
1732686,2017-11-21 05:51:42 UTC,"> On 21 Nov 2017, at 2:47 AM, R.Erol <email address hidden> wrote:
>
> Kai , thank you so much!
>
> That one works nicely , i can adjust the brightness of keyboard and turn
> on and off my keyboard light.
>
> Thanks again.
>
> One last question though ; what can i do for ACPI errors?
"
1732686,2017-11-20 18:47:29 UTC,"Kai , thank you so much!"
1732686,2017-11-20 11:42:49 UTC,This one:
1732686,2017-11-20 08:29:34 UTC,Can you try the daily kernel? It has some new commits on hid-asus.
1732686,2017-12-08 11:16:38 UTC,Thanks Alexandre.
1732686,2017-11-18 17:20:10 UTC,"I'm not sure this is entirely related, but someone should try https://github.com/archerhush/linux-fx553vd/blob/master/kbd-backlight.patch"
1732686,2017-11-17 22:38:04 UTC,Hi Joseph.
1732686,2017-11-17 15:28:37 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1732686,2017-11-16 14:39:57 UTC,apport information
1732686,2017-11-16 14:39:56 UTC,apport information
1732686,2017-11-16 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1732686,2017-11-19 21:21:39 UTC,Hi Alexandre. I don't know how to try it.
1732696,2017-11-17 13:01:59 UTC,James Page <email address hidden> writes:
1732696,2019-04-01 23:43:05 UTC,The Ubuntu distro default is 'performance':
1732696,2017-11-17 10:36:47 UTC,James - do we want todo this more generally on charms that target hardware? i.e. is this applicable for ceph-osd and neutron-gateway as well?
1732701,2019-02-06 11:38:21 UTC,"Really a useful Information. I would like to add a point on this comment, If in case you are facing a problem with the printer and want information to recover the issue then do follow this link <a href=""Epson Printer Error Code 0x9d"">Best Ways To Fix Epson Printer Error Code 0x9d</a>."
1732701,2019-02-06 11:39:24 UTC,"Really a useful Information. I would like to add a point on this comment, If in case you are facing a problem with the printer and want information to recover the issue then do follow this link [url=https://errorcode0x.com/fix-epson-printer-error-code-0x9d/ ]Best Ways To Fix Epson Printer Error Code 0x9d[/url]"
1732701,2019-02-06 11:41:08 UTC,"Really a useful Information. I would like to add a point to this comment, If in case you are facing a problem with the printer and want information to recover the issue then do follow this link [url=https://errorcode0x.com/fix-epson-printer-error-code-0x9d/ ]Best Ways To Fix Epson Printer Error Code 0x9d[/url]."
1732701,2019-08-20 07:52:41 UTC,"Visible in Tina 19.2, device without bluetooth hardware runs
Aug 20 09:44:25 hp530 systemd[1047]: Started Bluetooth OBEX service.
Aug 20 09:44:25 hp530 dbus-daemon[1090]: [session uid=1001 pid=1090] Successfully activated service 'org.bluez.obex'"
1732703,2017-12-13 23:05:50 UTC,"I would accept a version of this SRU that hard-codes the choice of upstart as the init system on 14.04, because that is the only init system supported in that version of Ubuntu."
1732703,2017-12-14 00:20:05 UTC,"On Wed, Dec 13, 2017 at 6:00 PM Robie Basak <email address hidden>
wrote:"
1732703,2017-12-14 15:34:19 UTC,"> I would accept a version of this SRU that hard-codes the choice of upstart as the init system on 14.04, because that is the only init system supported in that version of Ubuntu.
"
1732703,2017-12-14 15:34:51 UTC,"We concluded that this isn't a snapd bug, except in so far as it depends on systemd."
1732703,2017-12-14 18:41:51 UTC,@I've uploaded the new package. I've tested an upgrade to Xenial to ensure there are no issues and confirm it is good to go.
1732703,2018-01-16 12:33:43 UTC,# VERIFICATION FOR TRUSTY
1732703,2017-12-13 22:53:51 UTC,"On Wed, Dec 13, 2017 at 10:34:25PM -0000, Andres Rodriguez wrote:

> FWIW, this is currently affecting customers who are running MAAS and
> require livepatch.
"
1732703,2018-01-17 02:25:18 UTC,This bug was fixed in the package maas - 1.9.5+bzr4599-0ubuntu1~14.04.3
1732703,2018-01-17 02:25:29 UTC,"The verification of the Stable Release Update for maas has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1732703,2018-04-08 22:10:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732703,2017-12-14 19:06:53 UTC,"Hello Victor, or anyone else affected,"
1732703,2017-12-13 17:59:22 UTC,I've deferred my decision as to whether to accept what's currently in the queue on this thread: https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040093.html
1732703,2017-12-13 22:34:25 UTC,"FWIW, this is currently affecting customers who are running MAAS and require livepatch."
1732703,2017-11-21 14:28:26 UTC,"Trying to enlist a machine when systemd+upstart are installed in trusty, throws this error:"
1732703,2017-11-16 14:55:05 UTC,"Hi Victor,"
1732703,2017-11-16 15:25:22 UTC,"Hi Andres,"
1732703,2017-12-13 16:58:44 UTC,"This is quite unique to maas; as no other software is getting backports with explicit features that enables systemd support on trusty. E.g. cloud-init backports are done in such a way, that when compiled on trusty, no systemd support is installed nor available."
1732703,2017-12-01 16:59:39 UTC,I can confirm that patch in #4 works on MAAS 1.9.5 on trusty.
1732703,2017-12-13 13:35:55 UTC,"Since snapd pulling in systemd was introduced in an SRU, this is a regression in a stable caused by an SRU and therefore should be considered regression-update."
1732703,2017-11-21 14:54:03 UTC,Commissioning logs: https://pastebin.canonical.com/203632/
1732703,2017-12-13 15:20:21 UTC,"15:15 <rbasak> roaksoax: in bug 1732703, I'm not sure that test for systemd is reliable. For example immediately after an upgrade from Trusty to Xenial, before a reboot, /sbin/init will be systemd but the running init system will be upstart.
15:15 <ubottu> bug 1732703 in MAAS 1.9 ""MAAS does not detect properly if Ubuntu is using upstart/systemd"" [Critical,In progress] https://launchpad.net/bugs/1732703
15:16 <rbasak> roaksoax: AFAICT, the ""correct"" way to test for systemd is its process name or something, but I can't find a good reference.
15:16 <rbasak> roaksoax: so I'm not really sure what is correct. I'll happily accept whatever a systemd-type person here says.
15:16 <cjwatson> There should be something in one of the init script layers
15:17 <cjwatson> /lib/lsb/init-functions.d/40-systemd
15:17 <cjwatson> if [ -d /run/systemd/system ]; then
15:17 <rbasak> Ah
15:17 <cjwatson> I believe that's the canonical method
15:17 <rbasak> I recalled something about something in /run but was unable to find it.
15:18 <rbasak> Thanks
15:18 <cjwatson> rbasak: Found the documentation for that - sd_booted(3)
15:19 <cjwatson> under NOTES"
1732703,2017-12-13 16:53:24 UTC,snapd will not function without systemd as a deputy init.  nothing to fix in snapd.
1732703,2017-12-13 16:54:57 UTC,Further extensive discussion at https://irclogs.ubuntu.com/2017/12/13/%23ubuntu-devel.html#t15:15
1732703,2017-12-13 16:56:12 UTC,"It is correct, in general, to check for /run/systemd/system to detect if systemd manages pid 1."
1732703,2017-12-13 14:41:25 UTC,"Actually, if snapd isn't installed by default on Trusty, perhaps it we shouldn't treat it as a regression caused by snapd as the user is explicitly pulling in snapd and therefore systemd rather than it being imposed automatically by the SRU. I'll leave it for others to decide this though."
1732711,2017-11-16 15:00:39 UTC,It seems to be affecting only the amd64 architecture.
1732711,2017-12-19 23:51:03 UTC,Also affects i386.
1732713,2017-11-16 16:21:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1732713,2017-11-16 15:06:07 UTC,Image of KVM Guest CPU usage during hang.
1732713,2017-11-30 14:43:40 UTC,It has been 2 weeks and no updates. Bumping.
1732715,2017-11-17 15:56:53 UTC,The Ubuntu One login (used for Launchpad) is an OpenID 2.0 provider. (Not OpenID Connect/OAuth unfortunately.) There is currently no way around having a separate LP/Ubuntu One account and a separate GitHub account. (Neither service allows authentication from any other.)
1732715,2017-11-16 18:21:13 UTC,"Forum software needs to be upgraded to get OAuth support. I'm working on getting access,
Wiki now has the needed plugin installed and I'm waiting on those with duplicate accounts (E-mail addresses) on the wiki to respond with which user name is their current one. (The OAuth plugin requires unique E-mail addresses.)"
1732715,2017-11-16 16:04:15 UTC,"Of course, but I'm concerned this will sit on the backburner forever if it isn't committed to a deadline."
1732715,2017-11-16 15:43:57 UTC,"Milestone doesn't apply here, silly. :) This takes place outside the code base."
1732715,2017-11-16 16:21:44 UTC,"I'm working on it now, actually. Currently researching how much can be integrated."
1732719,2018-01-29 03:54:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732720,2018-10-29 22:47:12 UTC,"Sorry, forgot to mention; If it's not obvious in the screenshot, I'm NOT using thermal relief.  Perhaps this can help narrow down where the bug is?"
1732720,2019-07-01 22:26:56 UTC,Simple N/S/E/W spokes have been added for custom pad shapes.  Even this required a complete re-write of the zone fill algorithm along with a lot of performance tuning.
1732720,2019-02-09 18:09:53 UTC,"I like the idea of adding more configurability of the thermal relief in the footprint editor.  For instance, the ability to rotate the thermal relief by 45 degrees would be useful.  Inner layer clearances versus outer layer clearances would be helpful as well."
1732720,2019-01-08 07:05:17 UTC,"I've done some more tests, to uncover the SW decision tree used here."
1732720,2019-01-08 01:23:53 UTC,">Evan Shultz (evan-shultz) wrote ...
>A smart and automatic spoke system which could work for any arbitrary number of thermals, ideally avoiding >acute angles in copper created against the pad geometry, might be universal.
"
1732720,2019-01-07 23:41:04 UTC,"@Rene
That might be limiting. For example, 8-way thermal spokes are common and would not fit 4 defined locations."
1732720,2019-01-07 23:19:20 UTC,"Maybe a more flexible way would be to be able to manually define thermal connection points already in the footprint editor. The user could place 4 special lines from somewhere inside the pad to the outside. These lines will then be used as the basis for creating the spokes.
If no lines are present then the anchor pad can still be used as a fallback for creating the thermals."
1732720,2019-01-07 22:52:28 UTC,">(jp-charras) wrote For a custom shaped pad, one cannot define a suitable shape for thermal shapes.
>Therefore only the designer can connect (by a track) this kind of pad to copper zones.
>(this is not specific to Kicad)
"
1732720,2019-01-07 22:42:12 UTC,Adding chamfered pads will solve this for many footprints. See: https://bugs.launchpad.net/kicad/+bug/1777516
1732720,2018-10-29 22:44:28 UTC,I have the same issue. Screenshot included.  I've ensured that the 3 nets are indeed correct.
1732720,2018-10-15 21:23:46 UTC,"To chip in with the above supporting this request, and showing how this is done in one ECAD tool, making custom pad shapes with thermals can be done in a relatively straightforward way."
1732720,2018-10-16 23:40:03 UTC,Ooops. Wrong screenshot. Here are custom pads on another ECAD tool with thermals as described above.
1732720,2018-03-21 17:43:35 UTC,super-thanks
1732720,2017-11-19 10:22:10 UTC,Screenshot attached
1732720,2017-12-18 20:32:18 UTC,This still seems to be an issue on (2017-12-18 revision 3c6d17026)-master
1732720,2018-07-30 23:42:50 UTC,Adjusting this wishlist title to reflect work still to do.  Thermal relief are not easy for custom pads but we can probably figure out a way to allow the user to specify how they would like the thermal reliefs to exist.
1732720,2017-12-19 10:20:50 UTC,"For a custom shaped pad, one cannot define a suitable shape for thermal shapes."
1732720,2017-12-19 22:53:27 UTC,"I think this should be ""wishlist"", not ""won't fix"". I don't really agree that you _cannot_ define such a shape, it's just very difficult. I think that if someone were to come up with a reasonable approach for it we would probably be very happy to accept a patch."
1732720,2017-12-18 20:34:15 UTC,Same problem here.
1732720,2017-12-20 11:02:46 UTC,"I would agree - and in addition, if you select no thermals then the filling is trivial."
1732720,2018-01-03 16:54:02 UTC,Setting status to wishlist for now...
1732720,2018-03-14 15:02:48 UTC,for solid planes please ?
1732720,2018-03-15 01:20:51 UTC,"Solid connection to zones has been added in commit:
https://git.launchpad.net/kicad/commit/?id=d52491c715f2888c47eaa827aa56262eb968cf61"
1732720,2017-12-19 23:05:01 UTC,"Most commercial EDA software just treats those like any other pad, and attaches a spoke to whatever edge is at the angular position the spokes are configured to be. That works fine for a lot of the usual shapes, and has to be manually corrected for some really weird shapes (which are rare)."
1732725,2017-11-16 20:20:55 UTC,"Hi Christian, can you include the mount rules from the lxd-artful_</var/lib/lxd> profile? It'd also be superb to get the mount syscall (mount or mount2 perhaps?) that systemd tried to execute."
1732725,2017-11-17 11:30:29 UTC,"Hi Seth,"
1732725,2017-11-17 12:35:26 UTC,This is how we mount it manually for the container when it has dropped CAP_SYS_ADMIN:
1732725,2019-11-09 15:17:54 UTC,This is blocking running LXD on cgroup2 only systems. Any update on this?
1732725,2020-06-01 16:25:21 UTC,Ping
1732727,2021-01-10 18:01:00 UTC,"Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1273027, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find."
1732736,2017-11-16 20:11:02 UTC,"Subscribing Jabier as he's our ""LPE guru""."
1732736,2020-09-19 07:34:56 UTC,Closing because INVALID: Can't replicate (Fixed?).
1732736,2017-11-16 20:05:47 UTC,"Crash confirmed in Inkscape 0.92.2 (55332deb0d, 2017-11-04) on Windows 10 x64.
GDB backtrace attached."
1732743,2019-09-19 11:56:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1732743,2019-09-19 13:08:58 UTC,This bug still exists in MAAS 2.6.0 (7802-g59416a869-0ubuntu1~18.04.1)
1732752,2017-12-04 06:27:17 UTC,From the recovery log
1732752,2018-01-18 08:29:06 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2019
1732754,2017-11-16 18:26:04 UTC,"I'm getting the spinny when I first perform a search. However, if I perform the same search again, it doesn't come up. My guess was that the search was performing quicker on the 2nd try than it takes to get the spinny icon going."
1732754,2017-11-16 20:05:41 UTC,Kathy's correct about the reason. The spinner does not show up unless the search takes more than two seconds to start rendering the result page.  That's an explicit timeout value in the OPAC code.
1732754,2018-01-03 15:30:34 UTC,Adding a note that this appears to happen when jquery is enabled in config.tt2.
1732766,2019-09-02 16:56:24 UTC,Upstream bug now https://bugzilla.mozilla.org/show_bug.cgi?id=1399501
1732766,2019-02-20 02:50:10 UTC,Confirmed on my Ubuntu HD630 machine.
1732766,2019-02-15 22:25:01 UTC,Can confirm issue using Fedora 29 and Firefox 65
1732766,2018-09-05 21:26:07 UTC,Also occurs on Ubuntu 18.04 updated to latest mesa and using Vega M graphics.
1732766,2019-02-20 10:39:00 UTC,Upstream bug has been marked a duplicate of #1399501 so changing
1732766,2017-11-20 06:55:12 UTC,"Could you upload your ""about:support"" page info here?
Maybe we could find somethings wrong."
1732766,2017-11-18 20:59:25 UTC,Also occurs on ubuntu 17.10.
1732766,2017-11-18 20:43:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732766,2017-12-06 06:04:48 UTC,"Sure, here's about:support from one affected machine: http://kegel.com/firefox-fishgl/ubu1710.txt"
1732766,2017-11-16 23:54:22 UTC,"Created attachment 8929233
badfish.png"
1732769,2017-12-12 11:42:47 UTC,"The system appears to have invalid init.d scripts, with invalid headers."
1732785,2017-11-17 08:48:32 UTC,This is newton openstack AFAIKs.
1732785,2017-11-17 13:11:31 UTC,Let me answer that one on behalf of Mathieu:
1732786,2017-12-05 16:31:29 UTC,It would definitely be an improvement.
1732788,2019-09-19 11:56:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1732792,2017-11-18 19:46:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732807,2020-07-18 01:08:00 UTC,Thanks for responding. I apologise for an error in my comments above. The Year tag has in all cases been correctly included in the converted file. My problem is that Grouping and Rating are not included in mp3 conversions.
1732807,2020-07-15 19:50:52 UTC,"I think the tag_whitelist - and therefore the tags stored in our ""sound_file"" objects - is only important for constructing the path based on a pattern like {artist}. Tags are copied in gstreamer and we don't have control over that."
1732807,2020-06-19 00:34:25 UTC,"I appreciate the responses dev. But I am wondering why conversion to OGG doesn't seem to be limited what the ""tag_whitelist"" settings while it is limited in MP3."
1732807,2020-06-19 00:11:45 UTC,Thanks for the response - I do appreciate you're sticking with this bug.
1732807,2020-06-18 07:23:22 UTC,"To disable tag filtering, change:"
1732807,2020-06-13 02:35:53 UTC,"Thank you for this advice. I may have done this wrong - see attached file - but added 'rating', and 'grouping', to append_tag list and neither Rating nor Grouping have a tag value in the converted mp3 files in my testing."
1732807,2020-06-11 22:51:06 UTC,"Thanks for response. As a newbie I'd appreciate advice on how to modify this allowlist - searched for a file including that name, no result."
1732807,2020-07-18 01:10:45 UTC,Sending mp3 ffprobe result
1732807,2020-06-11 15:39:40 UTC,"The tags copied are checked against an allowlist to remove unwanted tags.
So this behaviour is by design."
1732807,2020-06-09 22:45:49 UTC,Unfamiliar with this system not sure where this is up to. If fixed version available please advise where to get it.
1732807,2018-05-30 11:43:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732807,2018-04-18 21:03:06 UTC,Same thing on 18.04. Soundconverter version 3.0.0.
1732807,2020-06-12 09:47:33 UTC,You have to change the list in the source code: https://github.com/kassoulet/soundconverter/blob/py3k/soundconverter/gstreamer.py#L412
1732843,2017-11-19 16:09:12 UTC,"Review in progress for https://review.opencontrail.org/37660
Submitter: Dinesh Bakiaraj (<email address hidden>)"
1732843,2017-11-20 06:49:32 UTC,"Reviewed:  https://review.opencontrail.org/37660
Committed: http://github.com/Juniper/contrail-controller/commit/30ec99d64ad4f640a21710e3949a561e13bcad5f
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1732845,2017-11-17 08:11:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1732845,2017-11-18 16:40:00 UTC,It seems to be this one: https://bugzilla.gnome.org/show_bug.cgi?id=777467
1732845,2017-11-28 14:20:01 UTC,Change the us.xml doesn't work after login
1732850,2018-01-22 23:33:38 UTC,The patch is not correct (trying to store a string into a boolean value) but you are correct on pointing out I'm not using the API correctly; thanks!
1732850,2018-01-22 23:39:30 UTC,"commit 8c134bd0985dc529bc6b2676b0a7c884675bbe42
Author: Robert Ancell <email address hidden>
Date:   Tue Jan 23 12:39:09 2018 +1300"
1732855,2019-10-29 06:13:29 UTC,Duplicated with this LP: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1837031
1732862,2018-05-11 09:59:55 UTC,"Adam, unfortunately we didn't plan a MU for MOS7.0 since it's out of active support. Do you have a customer who is willing to get the patch for this issue?"
1732862,2017-11-22 13:13:33 UTC,9.2 in progress: https://review.fuel-infra.org/#/c/37240/
1732862,2017-12-13 10:44:07 UTC,Verified on 8.0+mu6
1732862,2018-01-18 14:43:07 UTC,Verified on 9.2+mu4
1732871,2018-03-21 09:56:34 UTC,"It did work, didn't find them initially. They were in home and not in ~/Pictures where all Ubuntu flavors store screenshots."
1732871,2017-12-09 23:46:52 UTC,"The lxsession option controls the default screen shot app, which anything else could refer to and then the screen shot application wouldn't need to be hard-coded everywhere."
1732871,2018-05-06 23:00:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732871,2018-10-31 17:29:59 UTC,"If we're considering this a bug against lubuntu-default-settings, then it does not affect cosmic or disco, as Lubuntu no longer uses scrot or, for that matter, LXDE. If you're trying to continue to use LXDE in cosmic or disco, that's fine, but since the fix involves dealing with packages outside of scrot itself, you'll have to look elsewhere for the resolution."
1732871,2017-11-21 08:49:23 UTC,Which lines need to get altered? only 250 and 317 in /etc/xdg/openbox/rc.xml ?
1732871,2017-11-17 16:23:42 UTC,"Ah, found them. The remaining bug I would like to report is that the screen shots are saved by default to ~/Pictures as is the case in other tastes of Ubuntu. Advantage is that it conforms to other Ubuntu tastes, user expectation and that it get picked up by image viewing and image manipulation applications working that directory and backup monitoring that directory."
1732871,2017-11-20 10:09:37 UTC,Thanks. I have tried adding options to ~/.config/lxsession/Lubuntu/desktop for the line with scrot but without succes. What is the best way to configure this for a complete system and not for users individually via an alias?
1732871,2017-11-17 15:37:05 UTC,"it's already there. `man scrot`. now why the print screen doesn't work
is another story. maybe file a new bug?"
1732871,2017-11-20 14:48:47 UTC,"The global files are all in /etc/xdg. Note that those are not
necessarily guaranteed to persist across version updates."
1732871,2017-11-17 17:03:43 UTC,"Yeah, that's a reasonable thing to consider. Unfortunately, `scrot`
provides no configuration options. It's certainly possible to add the
suggestions to the hotkey command, but even `man scrot` suggests doing
something like `scrot '%Y-%m-%d_$wx$h.png' -e 'mv $f ~/Pictures'` which
is a pretty clear message that they probably have little interest in
changing that."
1732871,2017-11-17 16:26:14 UTC,See also https://askubuntu.com/questions/466109/change-scrot-output-directory
1732876,2017-11-21 13:49:42 UTC,I found a solution. There was the printer driver earlier installed that I downloaded from the supplier's website. Printer model Xerox wc3210. After uninstalling the driver all work properly.
1732883,2019-12-26 09:26:10 UTC,"Hi Connor,
thanks for checking this issue."
1732883,2019-11-12 22:50:22 UTC,"Hey Sam,"
1732883,2018-09-14 04:39:47 UTC,"Stalled, I will check on the current status for the KVM smoke test, the behaviour seem a bit different now."
1732883,2018-02-09 20:01:01 UTC,The best way to work on this would be to use the following commmands:
1732883,2018-09-12 18:45:30 UTC,"Hey Sam, we still working this?"
1732883,2018-01-29 15:20:47 UTC,The debdiff is reversed (which a sponsor could work around) but is also based on 0~bzr92-0ubuntu1.1 which is already published.
1732883,2017-12-05 11:40:54 UTC,"Hi Robie,
thanks for the hint, I will try to fix this in Trusty!"
1732883,2017-11-17 10:58:25 UTC,Thank you for the report.
1732883,2018-01-30 04:03:21 UTC,"Hi Robie,"
1732897,2017-11-29 11:44:52 UTC,Any functional impact?
1732897,2017-11-29 13:29:39 UTC,It's hard to estimate.
1732906,2017-11-17 12:41:04 UTC,"StacktraceTop:
 _int_malloc (av=av@entry=0x7f5c8e27dc20 <main_arena>, bytes=bytes@entry=72) at malloc.c:3611
 __libc_calloc (n=n@entry=1, elem_size=elem_size@entry=72) at malloc.c:3438
 g_malloc0 (n_bytes=n_bytes@entry=72) at ../../../../glib/gmem.c:124
 g_closure_new_simple (sizeof_closure=sizeof_closure@entry=40, data=data@entry=0x5565e16554a0) at ../../../../gobject/gclosure.c:214
 g_cclosure_new (callback_func=0x7f5c8fe70fd0 <gtk_window_on_composited_changed>, user_data=0x5565e16554a0, destroy_data=0x0) at ../../../../gobject/gclosure.c:944"
1732910,2018-03-12 13:49:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732915,2017-11-20 05:59:27 UTC,Needs nova version and nova-api log files.
1732916,2019-04-15 09:14:57 UTC,I've created a separate bug report for libvirt support: https://bugs.launchpad.net/cloud-images/+bug/1824780
1732916,2019-04-15 09:11:51 UTC,There should also be Vagrant boxes using the libvirt (KVM) provider
1732918,2017-11-17 15:51:47 UTC,You dont' need iscsitarget-dkms on any new kernel.
1732920,2017-11-17 14:17:11 UTC,"Hi Ernie,"
1732920,2017-11-17 16:06:03 UTC,It's intermittent. Will wait next time I encounter.
1732920,2017-11-19 22:19:51 UTC,"I just tried editing an interface which was:
EN02, fabric 0, untagged, unconfigured, unconfigured"
1732920,2019-09-19 14:53:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1732927,2017-11-17 15:08:49 UTC,"Hi Ernie,"
1732927,2017-11-17 15:53:52 UTC,Start off with a subnet on fabric 0
1732927,2017-11-17 15:56:55 UTC,Correction (couldnt figure out how to edit previous comment)
1732927,2017-11-17 16:57:10 UTC,Not sure if this is related:
1732927,2019-09-19 11:56:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1732929,2017-12-16 16:14:49 UTC,Related to (if not a duplicate of) bug #1256694.
1732929,2017-12-16 17:40:01 UTC,Seems not trivial to fix...
1732929,2017-12-16 17:52:22 UTC,As a matter of fact the above still does not work fully... (still limited to characters of the systems codepage).
1732940,2019-02-07 13:59:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1732942,2019-09-19 11:56:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1732943,2019-10-07 22:51:07 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1732943,2019-10-07 00:27:14 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue still happening with the current snapd version?"
1732944,2018-02-11 18:48:40 UTC,Does this work any better in 17.10 for ya? There were quite a few changes to the remote backend support there. And it now supports using GNOME Online Accounts for webdav.
1732944,2020-08-24 21:24:19 UTC,"I’m going to assume the mentioned changes helped this. If not, please reopen. Thanks."
1732947,2018-01-10 01:12:28 UTC,This issue was fixed in the openstack/nova 14.1.0 release.
1732947,2018-01-03 14:37:42 UTC,This issue was fixed in the openstack/nova 15.1.0 release.
1732947,2017-12-18 12:51:26 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1732947,2017-12-15 16:11:06 UTC,"Reviewed:  https://review.openstack.org/526544
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=24953a95e5989f44acaf488c253230e476c2fa59
Submitter: Zuul
Branch:    stable/newton"
1732947,2017-12-14 17:55:02 UTC,"Reviewed:  https://review.openstack.org/526542
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5ec5886fe74514c65908ff3adc2ca46610b595ad
Submitter: Zuul
Branch:    stable/newton"
1732947,2017-12-14 11:35:16 UTC,"Reviewed:  https://review.openstack.org/525664
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fe5e3e7e61d879f7a28eb177e4bdbc7ead3ae4ac
Submitter: Zuul
Branch:    stable/ocata"
1732947,2017-12-11 23:59:46 UTC,"Reviewed:  https://review.openstack.org/525634
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4e36c4bd0eab2be619991ae00454906e171720b6
Submitter: Zuul
Branch:    stable/pike"
1732947,2017-12-11 22:41:31 UTC,"Reviewed:  https://review.openstack.org/525632
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c7991653a4e7cbb86656e6ba7579a86236801567
Submitter: Zuul
Branch:    stable/pike"
1732947,2017-12-07 23:55:42 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1732947,2017-12-14 17:49:18 UTC,"Reviewed:  https://review.openstack.org/525666
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=10bc4fdbc568670dfd8bec109e8b854ba8ad7949
Submitter: Zuul
Branch:    stable/ocata"
1732947,2017-12-07 23:30:44 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/526542"
1732947,2017-12-05 15:44:44 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/525666"
1732947,2017-12-05 15:44:20 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/525664"
1732947,2017-12-05 14:50:19 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/525634"
1732947,2017-12-07 23:31:14 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/526544"
1732947,2017-12-05 14:49:55 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/525632"
1732947,2017-12-05 11:31:05 UTC,"Reviewed:  https://review.openstack.org/521391
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=54407afef3b446e34c44ba5392ccbf121e266de2
Submitter: Zuul
Branch:    master"
1732947,2017-12-05 05:29:40 UTC,"Reviewed:  https://review.openstack.org/521200
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a4eebd5de7ef4b63082536718ba7b993a66d47e7
Submitter: Zuul
Branch:    master"
1732947,2017-11-19 22:32:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521391"
1732947,2017-11-17 21:57:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/521200"
1732957,2017-11-17 17:54:39 UTC,"StacktraceTop:
 visit_decref (op=0xa00000a46f40, data=0x0) at ../Modules/gcmodule.c:374
 dict_traverse (op=<optimized out>, visit=0x442f20 <visit_decref>, arg=0x0) at ../Objects/dictobject.c:3057
 subtract_refs (containers=<optimized out>) at ../Modules/gcmodule.c:399
 collect (generation=generation@entry=0, n_collected=n_collected@entry=0x7ffe080fb3d8, n_uncollectable=n_uncollectable@entry=0x7ffe080fb3e0, nofail=nofail@entry=0) at ../Modules/gcmodule.c:956
 collect_with_callback (generation=0) at ../Modules/gcmodule.c:1128"
1732962,2020-10-06 23:13:30 UTC,"The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1732962,2020-10-06 23:13:25 UTC,This bug was fixed in the package apport - 2.20.1-0ubuntu2.25
1732962,2020-10-06 23:13:41 UTC,This bug was fixed in the package apport - 2.20.9-0ubuntu7.18
1732962,2020-09-25 15:35:48 UTC,"Hello Brian, or anyone else affected,"
1732962,2020-09-25 15:33:49 UTC,"Hello Brian, or anyone else affected,"
1732962,2020-09-24 21:09:19 UTC,Also sponsored for xenial.
1732962,2020-09-24 21:01:28 UTC,Sponsored for bionic.
1732962,2020-09-22 22:03:22 UTC,Updated debdiff and made sure autopkgtest were successful on both xenial and bionic
1732962,2020-09-09 16:59:59 UTC,I'll go ahead and sponsor these today.
1732962,2019-03-05 23:09:13 UTC,This bug was fixed in the package apport - 2.20.10-0ubuntu23
1732962,2020-10-05 20:10:32 UTC,Verification completed on both bionic and xenial using proposed pockets
1732962,2018-04-13 23:13:38 UTC,"Given what Tyler said about ""magic arg ordering being dangerous"" I wonder if we could instead do that is a security update simultaneously for all releases thereby avoiding the multiple uploads and flag day transition."
1732962,2018-05-14 11:10:50 UTC,"If we do that, I'd say we built them as security updates, copy them to proposed, and then once they are fit for release, copy them to the -security in addition to -updates; so we get the usual SRU checks."
1732962,2018-02-09 09:48:51 UTC,"Um, we can do that. But I think there's a problem with containers and compatibility in forwarding messages over the socket (think new container, old host)."
1732962,2018-02-09 10:00:05 UTC,So the situation is:
1732962,2018-02-09 10:35:12 UTC,Let's just generalize that into
1732962,2020-09-25 17:04:31 UTC,"All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.18) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1732962,2018-02-09 21:44:33 UTC,"It's just a silly fill up argument so we end up with 5/6 arguments to make old clients in containers happy. And well, it easily allows you to distinguish the new commandline from the old positional style :)"
1732962,2018-02-12 17:30:08 UTC,WiP merge proposal in https://code.launchpad.net/~juliank/apport/named-arguments/+merge/337590
1732962,2018-02-14 11:00:58 UTC,"OK, so that's not all: core_pattern itself only stores 128 bytes."
1732962,2018-02-09 21:26:20 UTC,I'm sorry I think I lost something here. What does --version2 mean exactly?
1732962,2018-03-26 15:18:11 UTC,"Just to summarize the situation: It seems that if you have apport installed inside an LXC container, that apport creates reports, rather than doing the forwarding dance. Unfortunately, the core_pattern does not know about name spaces."
1732966,2019-07-19 21:06:25 UTC,"Now that cloud-init on SuSE uses the net renderer path instead of legacy, I don't think this is a bug any longer."
1732971,2017-11-17 21:47:27 UTC,"are you able to see the Bezier Tool (Shift-F6) on the left,
or the Calligraphy Tool (ctrl-F6)
or the Spray Tool (shift-F3)?"
1732971,2017-11-17 19:53:41 UTC,"- could you indicate, which OS?
- which version of Inkscape, see Help->About
- also it would be very helpful to see a screenshot, for example, this is what I get on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1732971,2017-11-17 21:19:59 UTC,"Windows 10 with Inkscape 0.92
sorry havent figured out screenshots yet..."
1732971,2017-11-18 16:33:39 UTC,Yes I can access those with the commands. I now know about the hidden menu items double arrow thanks to another user. I can now get the text tool using that but it is still no longer in the visible menu.
1732971,2017-11-18 18:15:16 UTC,"how high is your screen size? As far as I can tell, the text tool should be visible if your monitor is more than about 612 pixels high."
1732971,2017-11-19 11:58:10 UTC,I'd check the icon size in the Preferences>Interface... try a smaller setting.
1732971,2020-02-29 08:06:42 UTC,"Closing as part of migration of bugs to GitLab. Reading the comments, this doesn't appear to be a bug (OP can access the text tool via a ""hidden menu items double arrow"", implying the screen size is too small). If there is a bug, this report lacks enough info at the moment to move over to GitLab."
1732973,2018-09-18 17:22:32 UTC,"Looks like we already have some error reporting thanks to Ubuntu:
https://errors.ubuntu.com/?package=mixxx&period=year
https://wiki.ubuntu.com/ErrorTracker"
1732973,2018-01-08 03:03:55 UTC,relevant: https://github.com/JPNaude/dev_notes/wiki/Using-Google-Breakpad-with-Qt
1732973,2018-10-16 04:43:03 UTC,"VLC has been working on a backend server for sending crash reports to:
https://code.videolan.org/videolan/CrashDragon"
1732973,2018-01-08 01:13:15 UTC,"We may want to take a look at Firefox's crash reporting system. It uses Google Breakpad plus some custom GUI code around that:
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Crash_reporting"
1732973,2017-11-17 21:48:36 UTC,addressing this should be really careful with private data (especially those found in the logs like path etc...). privacy laws around the globe cover a large part of that.
1732973,2017-12-25 02:04:52 UTC,This is essential to create high quality software people can rely on!
1732973,2017-12-20 13:39:25 UTC,Any volunteers to look into this for 2.2? Sébastien?
1732973,2018-01-08 00:58:24 UTC,"google breakpad, the crash reporter used in Chrome, is pretty nice
https://chromium.googlesource.com/breakpad/breakpad"
1732976,2017-11-28 14:00:14 UTC,Thanks for review Matt. We used to describe a regression/bug in errata update in the past tense so that it implies the bug is now fixed by the errata patch.
1732976,2017-11-27 21:28:00 UTC,Thanks for the corrections! Updated impact description follows...
1732976,2017-11-28 02:16:55 UTC,The description in comment 20 looks good to me. Thanks Jeremy!
1732976,2017-11-28 04:23:03 UTC,The above impact description and the proposed disclosure date 2017-12-05 15:00 UTC looks good to me too.
1732976,2017-11-28 04:45:07 UTC,"And regarding the ERRATA, here is a proposed updated to OSSA-2017-005:"
1732976,2017-11-28 13:41:21 UTC,"@Tristan,"
1732976,2017-11-29 00:09:13 UTC,"Further deliberation on the OSSA-2017-005/CVE-2017-16239 errata should probably move to bug 1664931 since it's not security-sensitive and also not dependent on the present embargo for this report, so can go forward independently."
1732976,2017-11-27 20:16:43 UTC,Here is the stable/pike fix for the new DoS issue:
1732976,2017-11-30 00:36:43 UTC,A pre-OSSA with copies of the current patches from (and links to them in) code review has been sent to our downstream stakeholders now. Disclosure is still on track for Tuesday at 15:00 UTC.
1732976,2017-12-05 15:05:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/525643"
1732976,2017-12-05 15:22:48 UTC,"Reviewed:  https://review.openstack.org/525643
Committed: https://git.openstack.org/cgit/openstack/ossa/commit/?id=e2283a6b9e16cf055d73115f8a8349168d8cb732
Submitter: Zuul
Branch:    master"
1732976,2017-12-06 19:00:35 UTC,"Reviewed:  https://review.openstack.org/521662
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=25a1d78e83065c5bea5d8e0a017fd9d0914d41d9
Submitter: Zuul
Branch:    master"
1732976,2017-12-07 23:55:35 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1732976,2017-12-09 02:06:15 UTC,"Reviewed:  https://review.openstack.org/523214
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fed660c1189fdf4159d97badfdc8c5b35ad14f23
Submitter: Zuul
Branch:    stable/pike"
1732976,2017-12-18 12:51:24 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1732976,2017-11-29 01:50:50 UTC,"fwiw, the bug 1664931 ERRATA is proposed here: https://review.openstack.org/523649"
1732976,2017-11-27 19:01:07 UTC,"Matt: Please proceed with 521186 and its associated backports; we'll send announcements with the OSSA-2017-005/CVE-2017-16239 errata once those merge. As for 521662 I'd like to include (a link to) the stable/pike backport in a pre-OSSA once it's ready. Assuming we have a viable backport for this bug within the next couple days, I'd like to propose 15:00 UTC on Tuesday, December 5 as the disclosure date/time."
1732976,2017-11-21 18:39:45 UTC,"I'll start piecing together the impact description for this DoS, assuming you feel fix 521662 is safely backportable to all branches where the problem was introduced (I assume all the way back to stable/newton?)."
1732976,2017-11-21 17:51:52 UTC,"Yep, agreed, I'd say that holding off on applying the original ""fix"" until you can include all of the pending ones as well is the best course of action. The original issue only applies to a small number of scenarios and is somewhat theoretical in nature. The ancillary issue it brought with it is very concrete and applies to almost everyone."
1732976,2017-11-17 19:48:33 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1732976,2017-11-17 20:41:33 UTC,Dan Smith is working on a possible alternative fix for bug 1664931 here:
1732976,2017-11-17 20:43:58 UTC,"Note that at this point, https://review.openstack.org/#/c/521186/1 does not resolve DoS issue described in this separate bug."
1732976,2017-11-18 21:36:57 UTC,"I've started an etherpad to try and clarify the various issues, status on potential fixes, and options:"
1732976,2017-11-20 03:14:57 UTC,This bug description sounds a lot like a class B2 according to VMT taxonomy: https://security.openstack.org/vmt-process.html#incident-report-taxonomy .
1732976,2017-11-20 15:34:51 UTC,I think this bug probably becomes class A if we fix it by reverting the patches for CVE-2017-16239 (and then that one in turn becomes class B2).
1732976,2017-11-27 17:40:44 UTC,"@fungi, https://review.openstack.org/#/c/521662/ only goes back to stable/pike."
1732976,2017-11-20 15:40:51 UTC,"I've subscribed the direct subscribers of the earlier bug 1664931, as well as the security notes reviewers since we're discussing the possible need to document an unfixable vulnerability in stable branches."
1732976,2017-11-20 19:41:13 UTC,"Agreed, at least one of the possibilities outlined would keep bug 1664931 fixed as well as mostly addressing the regression covered by this new bug report, which is why I noted it as only a _possible_ need to document an unfixable vulnerability (i.e., if the decision ends up being to revert the CVE-2017-16239 patches instead)."
1732976,2017-11-21 15:23:09 UTC,Between Dan and myself we have fixes for the issues pointed out in this bug and the etherpad:
1732976,2017-11-21 15:54:17 UTC,"Well if this bug is affecting something that has been release, (iiuc it will be ==14.0.10, ==15.0.8 and ==16.0.3), then we need another CVE.
If this new bug is caused by the previous OSSA-2017-005, then I think we should proceed with an errata and amend the new CVE to the previous OSSA."
1732976,2017-11-21 16:06:18 UTC,From the issues outlined in comment 10:
1732976,2017-11-21 16:53:27 UTC,"Matt,"
1732976,2017-11-21 17:21:51 UTC,@zigo: I'd say *this* bug is worse than the original CVE.
1732976,2017-11-20 19:21:52 UTC,"> since we're discussing the possible need to document an unfixable vulnerability
"
1732991,2020-04-25 12:34:04 UTC,The bug is still present in the 20.04 LTS.
1732991,2017-11-18 14:12:40 UTC,Thanks. In that case it may be something related to the yelp help browser.
1732991,2019-03-08 16:49:52 UTC,The bug is still present in Bionic.
1732991,2017-11-18 10:11:40 UTC,Thanks for your report.
1732991,2017-11-18 00:26:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1732991,2017-11-18 10:53:54 UTC,"The problem persists on X.org session as well. I just noticed that the side buttons (buttons 4 and 5?) of the Logitech M705 are registered as primary button presses. That is, I can follow links by clicking the side buttons."
1732993,2017-11-19 16:20:05 UTC,"Hi Whissel,
thanks for your interest and feedback."
1732997,2017-11-18 00:26:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1732997,2017-11-18 01:09:32 UTC,"its no wonder people don't report or fix bugs.. y'all make it so hard to do so..
i have no idea what url it wants.. but here is the file in problem..
https://launchpad.net/ubuntu/bionic/armhf/bash/4.4-5ubuntu1
it is also happening with the artful file.. seeing how they are the same file."
1732997,2017-11-22 19:58:26 UTC,"here what i found in the log
this error is holding up the building of artful and bionic for the raspberry pi2
here is a link to my project
https://sourceforge.net/projects/ultimateedition-ports/files/PiFlavourMaker/"
1732997,2018-01-30 11:58:41 UTC,"Hi,
I have same error when I tried to run debootstrap --second-stage.
Anyone who have the solution?"
1732997,2018-02-09 22:00:37 UTC,and now its happening with 4.4.18 here is my debootstrap log
1732999,2017-11-17 21:32:38 UTC,"> xrandr --version
xrandr program version       1.5.0
Server reports RandR version 1.5
"
1733002,2019-03-19 23:57:52 UTC,"Comment on attachment 365256
Patch"
1733002,2019-03-20 00:37:23 UTC,"Comment on attachment 365256
Patch"
1733002,2019-03-20 01:01:49 UTC,"Comment on attachment 365256
Patch"
1733002,2019-03-20 04:53:30 UTC,"Created attachment 365306
Patch for Landing"
1733002,2019-03-20 05:44:16 UTC,"Comment on attachment 365306
Patch for Landing"
1733002,2020-04-26 21:14:57 UTC,"I can confirm that Ubuntu 20.04 suffers from the same issue. I'm still unable to link a Google Account due to being in Google's Advanced Protection Program, which requires a Security Key to authenticate. I'm able to authenticate in everything but Gnome's Online Accounts area."
1733002,2019-05-11 23:37:02 UTC,this is still broken…
1733002,2019-05-12 10:37:57 UTC,"GNOME upstream pointed out webkitgtk as the place where the works needs to happen and to https://bugs.webkit.org/show_bug.cgi?id=143491 and a fix was recently commited, hopefully it means it's going to be resolved next cycle"
1733002,2020-04-24 01:27:06 UTC,I just updated to 20.04 LTS today. In the Canonical press release for 20.04 they mention that FIDO support was integrated into this release: https://ubuntu.com/blog/ubuntu-20-04-lts-arrives
1733002,2020-11-16 05:54:33 UTC,"Confirming, it affects me at well (20.04)."
1733002,2019-03-20 06:12:03 UTC,"Comment on attachment 365306
Patch for Landing"
1733002,2019-03-19 23:45:16 UTC,"Comment on attachment 365256
Patch"
1733002,2019-03-19 22:48:01 UTC,"Created attachment 365249
Patch"
1733002,2019-02-22 01:53:42 UTC,<rdar://problem/48298273>
1733002,2018-10-29 18:08:50 UTC,"(In reply to David Waite from comment #5)

> FWIW, Edge has no intention to support U2F and only support WebAuthn.
>
> The U2F JavaScript API unfortunately doesn't fully document how to get
> access to the objects needed to use the MessagePort and u2f interface API.
>
> U2F supports CTAP1 devices, while WebAuthn supports CTAP1 and CTAP2 devices.
>
> There is an extension for WebAuthn to work with existing U2F registrations
> (such as those created via another browser, or the Safari App Extension)
> with the new API, so that users can still authenticate when a site upgrades
> from using the U2F to WebAuthn javascript interfaces.
"
1733002,2018-10-29 18:06:14 UTC,"(In reply to john+webkit from comment #4)

> Does the work on WebAuthN contain FIDO 1.0 support as well? If not, this
> ticket is probably still valid on it's own.
"
1733002,2018-10-29 07:20:48 UTC,"FWIW, Edge has no intention to support U2F and only support WebAuthn."
1733002,2018-05-26 19:28:37 UTC,"Does the work on WebAuthN contain FIDO 1.0 support as well? If not, this ticket is probably still valid on it's own."
1733002,2018-01-22 21:28:13 UTC,"(In reply to Yusuke Suzuki from comment #2)

> What is the difference from the Web Authentication[1,2]?
>
> [1]: https://github.com/w3c/webauthn
> [2]: https://w3c.github.io/webauthn/
"
1733002,2017-12-02 20:47:31 UTC,I believe I added the appropriate bugwatch to the upstream report: https://bugzilla.gnome.org/show_bug.cgi?id=791144
1733002,2017-11-21 10:52:45 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1733002,2017-02-17 05:23:32 UTC,"What is the difference from the Web Authentication[1,2]?"
1733002,2016-05-19 18:49:02 UTC,"Created attachment 279408
U2F request flow diagram."
1733002,2015-04-07 18:39:36 UTC,The FIDO Universal Second Factor (U2F) protocol is an open specification that was recently finalized.  The FINAL spec can be downloaded here: https://fidoalliance.org/specs/fido-u2f-v1.0-ps-20141009.zip
1733002,2019-03-19 23:29:50 UTC,"Created attachment 365256
Patch"
1733010,2017-11-17 22:46:14 UTC,pt-heartbeat 2.2.19
1733010,2018-01-24 22:36:42 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1458
1733010,2017-11-17 22:45:23 UTC,The same is true for --monitor
1733012,2018-01-24 22:36:49 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1459
1733021,2017-11-22 21:37:38 UTC,Waiting for the setup.
1733021,2017-11-18 00:20:21 UTC,Logs from contrail-webui-stdout.log
1733031,2017-11-18 13:20:03 UTC,You have installed the needed plugin?
1733034,2018-10-04 08:40:07 UTC,"Contrary to what's suggested in Comment #4 the issue is not solved in Pike. While the update routine is a bit different in Pike, it still jumps between both sources (actual resource usage and instance allocated memory)."
1733034,2019-06-27 14:42:39 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/523006
Reason: It's not clear to me if this is potentially already solved by change I120a98cc4c11772f24099081ef3ac44a50daf71d or if it's still an issue on master (or anything newer than pike based on discussion in the bug report). I asked for a functional recreate test of the issue back in February because the resource tracker code is hard to understand and get right since it's very tightly coupled code and the only way to really reason about it (and make sure to not regress it with later changes) is to have functional tests that run through the flow and assert whatever scenario we've had problems with. So until that happens, I'm going to abandon this and mark the bug as incomplete."
1733034,2018-06-28 10:25:27 UTC,"It would be nice if someone with review priviliges on Nova could look into the proposed patch and approve it. While this is arguably a minor issue, it's quite annoying if you look at an overview of your hosts usage and values change without any changes to their instances."
1733034,2019-08-27 04:17:25 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1733034,2018-04-02 11:12:15 UTC,Some additions to the bug description.
1733034,2017-11-27 03:01:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523006"
1733034,2017-11-20 06:04:55 UTC,Set the status to 'In-Progress' because this report has an assignee.
1733034,2018-04-02 19:16:30 UTC,"Comment #3 only valid for ocata (and maybe earlier releases?), as in pike, the same _update call is used both when saving system usage and when setting instances usage. In pike and later this will only cause constant updates of placement and compute_nodes table as it is unlikely that system and instance usages are the same."
1733035,2019-10-09 20:36:25 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it.
I'm closing it as ""Won't fix"", because we didn't do anything about this, but if you're still stuck there's probably a cause for this that isn't necessarily snapd itself and we can probably figure it out.
Again, sorry."
1733036,2019-05-01 12:35:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733036,2019-09-10 12:05:38 UTC,even when I install the xfonts-75dpi and xfonts-100dpi I do not get these fonts.
1733036,2019-09-10 12:14:32 UTC,"update: after a reboot, -adobe-helvetica-... fonts are indeed present."
1733041,2017-11-19 06:25:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733041,2017-11-18 05:22:34 UTC,"I am update 「Ruby2.4」 on PPA、and 「sudo apt install glib2.0」now.
But no boot and this error messages now."
1733041,2017-11-18 05:45:32 UTC,"I installed 「sudo apt install ruby-cairo-gobject」,
Mikutter is operated now.
This pacakges needs 「ruby-cairo-gobject」, I think it Ubuntu17.10 now."
1733048,2017-11-19 13:19:08 UTC,It does appear that we will need to update our detection script for Windows 2016.
1733048,2017-11-20 06:49:00 UTC,Look like the Get-Ram function in winrmprovisioner.go return the number of RAM stick capacity not total. So if we have 2 RAM sticks it will return 2 result.
1733048,2017-11-20 11:40:42 UTC,"The above modification work on Windows 2012, able to add machine.
However on Windows 2016 still getting the error detecting windows characteristics
Output sequence as follows."
1733048,2020-01-15 14:22:28 UTC,"Hello,"
1733048,2020-01-17 09:20:08 UTC,"For me on Server 2016 (not nano) the Output says:
amd64
8589934592
win2016nano
2"
1733066,2019-07-06 18:58:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733066,2020-07-04 11:46:58 UTC,libpng12-0:amd64 (1.2.50-2+deb8u3)
1733068,2017-12-18 00:53:16 UTC,"If you want to get more information about what's happening at the USB level, you should use usbmon (see Documentation/usb/usbmon.txt in the kernel source for instructions).  It will tell you what commands are being sent to the drive, but not which program is responsible for sending them.  Still, you can use it to compare the different Ubuntu releases."
1733068,2017-12-17 20:32:39 UTC,so far the feeling is that
1733068,2017-12-17 16:31:40 UTC,Seems that with the new kernel the disk stays awake and never even tries to go standby:
1733068,2017-12-17 15:57:22 UTC,It wouldn't be surprising to find that udisks2 is the program waking up your drive.
1733068,2017-12-17 12:46:17 UTC,"Spoke too early, drive just woke up out of the blue, after having been manually unmounted in nautilus, and forced to standby with hdparm -y (now that it works), without me re-mounting it or anything."
1733068,2017-12-17 12:41:53 UTC,"Trying 4.14.4 ((from mainline debs).
So far it looks promising: Hdparm seems now able to also query/set the status (before it was returning an error with this drive), and it's about one H since i forced it to standby and the drive is staying in standby."
1733068,2017-12-17 11:30:02 UTC,"working on it, but i was also thinking: The same value is returned in 14.04.
Can it be that 16.04 kernel does not honor that value and keeps polling at a 10minute interval?"
1733068,2017-12-16 23:04:11 UTC,first finding:
1733068,2017-12-16 22:02:40 UTC,"I have no idea which kernel versions Ubuntu uses in its releases, but the recurring Hardware Error bug should be fixed in the 4.14 kernel.  At least I think it should -- nobody has reported on whether the fix actually works, so I have no way of knowing."
1733068,2017-12-16 20:20:07 UTC,"Ok, i think i gathered some relevant evidence.
I had the drive plugged on a 16.04, and at some point i noticed it went standby (led blinking intermittently)."
1733068,2017-12-16 18:29:40 UTC,"also, on 16.04, in addition to the above messages, the drive not only does not go to standby (with the led blinking regularly), but it also does not spin down. Tested with 3 different 16.04 (2 ubuntus and one kde neon) on 2 different systems"
1733068,2017-12-16 18:19:01 UTC,"and, by the way, this is the kind of messages that flood dmesg:"
1733068,2017-12-16 17:01:56 UTC,Updated the description: I tested with 14.04 and as expected everything goes to sleep when it should and stays sleeping.
1733068,2017-12-07 14:59:11 UTC,can it be related to https://bugzilla.redhat.com/show_bug.cgi?id=1351305#c36 ?
1733068,2017-12-06 23:04:59 UTC,"Ok, so i managed to start btrace when i saw the disk sleeping and stopped after it woke up:
http://paste.ubuntu.com/26128577/"
1733068,2017-12-06 22:33:27 UTC,"oh, and 14.04 disks stay mounted (just not accessed)"
1733068,2017-12-06 22:14:38 UTC,"to compare, this is what i got on the 14.04 where unmounted  HDs stay standby"
1733068,2017-12-16 22:39:03 UTC,"Thank you Alan, for providing these valuable info.
Actually i noticed the polling by looking at dmesg. I suspected that the errors in my distribution's kernel (4.4.0 in 16.04) were somehow related to a kernel polling process with a default of 10 minutes."
1733068,2018-02-28 21:15:58 UTC,"I'm not sure why you were getting those errors, but definitely stop the udisks service.  Your blktrace shows it being accessed by the ""pool"" task.  For some silly reason, the glib thread pool library that udisks uses decides to rename its threads to ""pool"" instead of the application name."
1733068,2017-12-06 21:57:12 UTC,Thank you for the suggestion!
1733068,2017-12-06 16:45:07 UTC,You can use blktrace to see who is accessing the drive.  My first suspect would be udisksd so you might try killing that process and see if that makes it go away.
1733068,2017-11-18 16:22:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1733068,2017-11-18 19:01:23 UTC,"yes, of course there's no source package to blame. Or, at least, i donno which one it would be.."
1733068,2017-11-23 14:50:07 UTC,Nobody that is able to even reproduce this?
1733068,2017-11-23 21:51:06 UTC,"Brian, that doesn't seem a nautilus issue"
1733073,2018-03-03 09:18:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733073,2019-02-06 13:14:13 UTC,Do you still get the issue in newer Ubuntu versions?
1733073,2018-03-26 13:25:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1733078,2018-03-29 14:22:47 UTC,I can confirm this being the case in Mate 18.04 beta too. On mate community discussion it is said it is a bug in Plank iteself.
1733078,2019-03-03 01:56:20 UTC,"I can confirm, still have problem on:"
1733078,2019-03-17 14:31:39 UTC,I confirm on Xubuntu 18.04.
1733078,2020-05-16 01:31:55 UTC,I also confirm this issue on both Ubuntu Mate 18.04 (Plank 0.11.4) and 20.04 (Plank 0.11.89).
1733078,2020-04-22 09:13:38 UTC,"I don't remember what I have done but after I install libremenu(menu editor) to detect and delete some error shortcuts which don't have path to execute (also be default shortcut) that make briskmenu crash on boot, I don't get any panel icon in plank whenever I neither edit panel or press alt+F2 anymore. Hope this will help you!"
1733078,2020-04-27 22:20:23 UTC,"I have the same issue on Debian 10.3 with MATE.
Strangely enough, I have another laptop with the same setup, and I have never seen it there, I didn't even know this issue exists. Not sure if any of the apps I have installed make the difference (I don't have the above mentioned libremenu installed, i don't even see it in repos)."
1733078,2020-05-16 01:39:17 UTC,Duplicate of https://bugs.launchpad.net/plank/+bug/1694037
1733078,2020-01-19 03:25:48 UTC,"This has actually been a problem since the latter part of Ubuntu 16.04 of 2016. It thinks the panel is a App and when you left click the panel icon in plank, it minimizes it. Back then I was using Ubuntu Mate and I can concur it's still around today and has never been solved and probably never will be."
1733083,2021-01-11 01:35:13 UTC,We really should have a separate bug for each model of touchpad/laptop. Because the fixes for these issues are usually specific to each model.
1733083,2021-01-08 14:06:24 UTC,"Hi,
On my HP EliteBook 840 G2 I'm seeing the same issue. I saw the issue on Ubuntu 20.04, but upgrading to 20.10 made no difference. It was suggested[1] to switch to the 'evdev' input driver. So I installed the 'xserver-xorg-input-evdev' package and added the following file:"
1733083,2021-01-11 07:46:53 UTC,pls delete my previous post above. it was wrong here.
1733083,2017-11-21 14:34:56 UTC,"Hello folks,"
1733083,2020-04-15 12:54:43 UTC,From my side I would like to add:
1733083,2018-02-16 15:56:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733083,2018-01-09 16:08:53 UTC,"Hi Daniel, close but no cigar."
1733083,2018-01-08 04:25:06 UTC,"Hi Carlo,"
1733083,2017-11-21 14:39:15 UTC,Oh btw I forgot to say that you can get LIBINPUT_ATTR_TRACKPOINT_RANGE by using sudo evtest /dev/input/event6 with your device and seeing the maximum value that you get while moving the cursor around.
1733083,2021-01-11 01:35:40 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1733083,2021-01-11 07:43:27 UTC,"Sorry, I menat this solution (te previuos link was to general):"
1733085,2020-03-22 15:55:16 UTC,Please explain reason for marking as won't fix.
1733085,2017-11-18 15:05:33 UTC,Ubuntu Mate 17.10. Samsung NC10 netbook. Intel Atom (32-bit). 1GB RAM.
1733094,2017-12-31 12:31:09 UTC,What is the reasoning why the bug is invalid?
1733099,2017-11-29 14:26:34 UTC,Nothing specific.
1733099,2017-11-29 11:58:36 UTC,"Do you have a specific requirement to be able to change this port? I'm actually in favour of dropping all port based configuration options; we only test with the default upstream port configs, and I suspect alot of things will break if you try to change anything ATM."
1733100,2019-07-03 21:26:43 UTC,"Hello,"
1733102,2019-04-11 09:16:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733103,2017-11-18 18:44:04 UTC,"Note that on my machine (clean 16.10 install, upgraded to 17.04 and later 17.10), DNS resolution already partially broke in 17.04 (involving the switch to systemd-resolve).  With Ubuntu 17.04, DNS resolution was broken after suspending, moving to a different WiFi, and resuming the machine.  This could be manually fixed by manually running dhclient.  This does not fix the abovementioned issue, though."
1733103,2019-10-31 14:37:14 UTC,"Much has changed in systemd since 2017, please update this bug if this still happens."
1733105,2019-03-23 11:32:20 UTC,Solution: https://github.com/lanoxx/tilda/pull/365
1733105,2020-05-09 14:04:35 UTC,This should be fixed in release 1.5. If not please reopen.
1733106,2018-02-21 20:06:08 UTC,I have the same issue.
1733114,2017-11-19 05:08:25 UTC,"error is
(eviacam:1918): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported"
1733114,2017-11-19 13:57:49 UTC,Confirmed (Budgie DE)
1733121,2017-11-24 09:45:44 UTC,"Khurshid Alam - thanks, but those 2 bugs don't seem related."
1733121,2017-11-19 07:16:20 UTC,This may have something to do with patch removed from recent xorg which landed through SRU. See LP: #1683383 and LP: #1245473
1733122,2017-11-18 21:37:13 UTC,Version: 0.9.9-1
1733123,2017-12-19 22:49:29 UTC,This is when I open Basket 2.11 beta:
1733123,2017-12-19 20:26:20 UTC,"How did you close Basket? If you used Close button, try menu Basket -> Quit instead (or press Ctrl+Q). Then run 'basket --debug' from the terminal, so that debug window is displayed. I'd like to see debug window log too, so please copy it here (grab an image from Basket and copy lines starting with ""RG"" from that window)."
1733123,2017-12-18 21:49:17 UTC,How often does it work correctly and incorrectly? Can you post log from debug window for incorrect case?
1733123,2017-12-15 23:14:15 UTC,"The problem returned. I closed and opened it again, and then it happened."
1733123,2017-12-15 20:04:03 UTC,It worked.
1733123,2017-12-15 19:32:07 UTC,Please try this new build
1733123,2017-12-10 11:55:41 UTC,"Thanks for the test, this is quite strange indeed.
I'll probably make another test build with code from regiongrabber_dbg."
1733123,2017-12-10 02:10:53 UTC,I got it to start (there were still three packages missing).
1733123,2017-12-10 00:57:03 UTC,Did you install that package? Try
1733123,2017-12-09 13:35:59 UTC,This is the error that shows in the terminal:
1733123,2017-12-19 00:24:54 UTC,"It worked only when I opened it for the first time after I installed it. Then, when I close it and open it again, it goes back to the old stage."
1733123,2017-12-09 01:13:29 UTC,"It was successfully installed, but doesn't start."
1733123,2017-11-21 15:57:30 UTC,"I cannot reproduce this on Ubuntu 17.04. Can you specify more details?
- is it possible to resize the area selection frame (make it less than 960x432)?
- are you using Gnome desktop environment (default) or something different?
- what Basket version are you using?"
1733123,2017-12-09 12:10:22 UTC,"If you try to start basket from terminal, does it print any errors?"
1733123,2017-11-18 22:02:47 UTC,I'm using Ubuntu 17.10. But I also had this problem when using Ubuntu 17.04.
1733123,2017-11-30 20:53:33 UTC,Selection is limited by screen size and it seems screen size is determined incorrectly.
1733123,2017-11-30 22:19:33 UTC,This?
1733123,2017-11-21 21:12:36 UTC,"- the dark area (960 X 432) in itself in unchangeable, but I can crop any area within this area."
1733123,2017-12-01 21:52:58 UTC,RG::RegionGrabber initial size 640x480
1733123,2017-12-04 15:28:06 UTC,"So you were able to select area bigger than 960x432 this time, right? It seems screen size is actually determined correctly."
1733123,2017-12-04 23:18:40 UTC,"Yes, there was no problem selecting the whole screen with the
regiongrabber_dbg, however, the problem persists with Basket itself."
1733123,2017-12-08 20:07:25 UTC,"Hmm, interesting.
Yes, it makes sence that you have X11. Actually Wayland is not supported at the moment - it would grab a black screen."
1733123,2017-12-01 16:01:57 UTC,"You compiled the test app, now please run it
./regiongrabber_dbg
then press ""Take screenshot"", select an area and hit Enter
then copy log from main window of regiongrabber_dbg (not from terminal)"
1733125,2020-07-01 04:17:29 UTC,[Expired for openbox (Ubuntu) because there has been no activity for 60 days.]
1733125,2020-05-02 01:06:09 UTC,"My prior comment doesn't cover every case; lotuspsychje didn't list changes or prior configs, r-mazitis likewise makes no mention so it any, and wxl highlighted that the 1862756 was seemed related to graphics chipset."
1733125,2020-05-02 00:06:46 UTC,Thank you for taking the time to report this issue and helping to make Ubuntu better.
1733125,2020-05-01 13:50:33 UTC,Issue solved.
1733125,2020-05-01 11:59:53 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases"
1733125,2020-05-01 07:41:19 UTC,"I just installed LUbuntu 20.04, and I am seeing symptoms from the problem described above."
1733125,2020-03-01 13:20:42 UTC,"Hello there. I'm in Ubuntu 19.04 at the moment and I can confirm that it has the same bug (and that the bug yields to the same fix), as do some other Debian-based distros I've tried such as Siduction and TTOS. I can't comment on Ubuntu 19.10 as I haven't used it as yet."
1733125,2019-05-23 13:29:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733125,2019-05-23 13:30:56 UTC,The mentioned Workaround helped me on my physical machine running Ubuntu 18.04.
1733125,2018-09-09 03:56:00 UTC,"I will note that in relation to the workaround, this particular behavior is the way it is to resolve a problem reported in Debian. You can find the change in 3.6.1-5"
1733125,2018-09-08 13:46:55 UTC,"Yes, this happens on physical (non-VM, non-container) installation."
1733125,2018-09-08 13:34:35 UTC,reopening after auto-close. Repeating wxl's question: can anyone confirm this happens on a physical install?
1733125,2018-09-08 04:18:11 UTC,[Expired for openbox (Ubuntu) because there has been no activity for 60 days.]
1733125,2018-07-09 11:16:48 UTC,This affects Bionic as well. Uncommenting the line mentioned in comment #3 fixed this for me as well.
1733125,2018-05-21 17:41:14 UTC,"I can't confirm this in a virtual machine, at least, which doesn't say all that much. With those of you who are affected, can you confirm this does *not* occur for you in a VM? If so, I'll track someone down who's still on Artful, since I'm not seeing this in Bionic (are you?). If not, then we need more clear steps on how to reproduce the problem. All I did was open up a window and move it around and all is well."
1733125,2018-05-21 03:22:10 UTC,In my case it was a commented out line in /usr/lib/x86_64-linux-gnu/openbox-autostart
1733125,2018-02-14 23:51:56 UTC,I'm experiencing the same problem.
1733125,2018-09-28 20:35:08 UTC,"Hello,"
1733133,2017-11-19 22:43:09 UTC,Thanks for taking your time to report this bug.
1733133,2017-11-20 01:46:28 UTC,I see. That's too bad that the alarm API interferes with it. It is such a beautiful app. Thanks for replying.
1733138,2017-11-19 07:49:59 UTC,"atc@ATC:~$ rfkill list
0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no"
1733138,2017-11-29 13:02:06 UTC,"https://github.com/jurobystricky/Netgear-A6210/issues/88
find some more info from here"
1733138,2017-11-29 13:01:15 UTC,dmesg-with-wifi-opened.txt
1733138,2017-11-29 13:00:46 UTC,journalctlb-with-wifi-opened.txt
1733138,2017-11-19 08:15:23 UTC,info of debugging
1733138,2017-11-19 07:46:29 UTC,NetworkManager.state
1733138,2017-11-19 07:39:52 UTC,"atc@ATC:~$ uname -r
4.13.0-16-generic"
1733138,2017-11-19 07:45:59 UTC,NetworkManager.conf
1733138,2017-11-19 07:39:07 UTC,lsusb v
1733138,2017-11-19 07:37:51 UTC,syslog
1733138,2017-11-19 03:39:56 UTC,what the official said:
1733138,2017-11-19 03:39:06 UTC,lsmod output
1733138,2017-11-19 03:38:43 UTC,dmseg output
1733142,2018-03-04 05:10:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733142,2019-12-18 16:19:24 UTC,I believe this is fixed since then. Please reopen if you still observe the issue.
1733144,2018-01-15 15:28:33 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1733144,2018-01-20 02:42:43 UTC,Reconfirmed on powerdevil 4:5.10.5-0ubuntu1 with Ubuntu 17.10.
1733144,2018-01-20 11:19:44 UTC,"Then do a system cleanup with 'gtkorphan' & 'bleachbit' as root (select carefully the options), and reboot.
If you still get that issue, then think to use a new user profile, in case yours is borked."
1733144,2018-01-20 16:58:00 UTC,I tried booting the Kubuntu 17.10.1 Live CD and I still see the issue.
1733159,2017-11-19 08:43:24 UTC,"As far as I can see, there happens a segfault in remove-default-wordlist, which is called in postrm of wogerman.
remove-default-wordlist is part of package dictionaries-common, so this may be an issue there.
Since remove-default-wordlist is a perl script it shouldn't segfault, so this may be an issue in some included modules, maybe Debconf::Client::ConfModule, which is part of package debconf, so the issue may be located there."
1733168,2019-07-16 02:23:26 UTC,"I got another computer, same type, slightly different equipment.
The problem no linger occurs. So I think it was strongly hardware related."
1733168,2019-02-15 14:12:02 UTC,"Still, with kernel 4.15.0-45-generic and nvidia-390, the system will not resume:
Both monitors remain dark after some key was pressed to wake up from suspend, now this even happens with only one monitor."
1733168,2018-12-08 17:07:47 UTC,Still not reliable - I had apx 8 successful resumes and 2 failures yet.
1733168,2018-12-06 12:02:43 UTC,"390 is working now, will keep it under observation."
1733168,2018-06-08 03:58:07 UTC,The issue got fixed after upgrading nvidia-384 to nvidia-390
1733168,2018-04-23 09:48:32 UTC,same thing happens in ubuntu 16.04 also
1733168,2018-04-23 09:47:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733168,2017-11-19 10:10:07 UTC,"Here is a video of the incident described above:
https://www.dropbox.com/s/ipiv5uyy8jdnngl/VID_20171119_104246.mp4?dl=0"
1733175,2017-11-19 12:11:23 UTC,This bug complements dragonflow BGP-VPN implementation:  https://bugs.launchpad.net/dragonflow/+bug/1733177
1733175,2017-11-20 08:34:32 UTC,"Indeed, to realize a dragonflow implementation of BGPVPN API, the behavior needed is different than the one of the 'bagpipe' driver for BGPVPN.  The BGPVPN driver framework already has everything in place to create a dragonflow driver without any dependency on the existing 'bagpipe' driver: subclassing the BGPVPNDriver [1] class is sufficient to have access to all the postcommit hooks, and interact with bagpipe-bgp from there."
1733176,2017-11-19 21:09:02 UTC,"Thank you very much, I was not aware of this feature."
1733176,2018-02-21 09:58:12 UTC,">I just pushed a change to qpdfview's trunk that makes it possible to set a value of zero, >meaning that scheduled changes will be saved to disk immediately after UI events have been >processed. Setting it to something smaller than zero will now have the meaning of ""Never"".
"
1733176,2017-11-19 12:05:59 UTC,This is currently the case for v0.4.16 on Linux.
1733176,2017-11-19 20:53:51 UTC,"Hello Daniel,"
1733176,2018-02-21 19:34:42 UTC,"Hello,"
1733177,2017-12-25 12:08:59 UTC,Planned for Queens
1733179,2017-11-19 12:23:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521364"
1733179,2017-12-10 04:34:28 UTC,"Change abandoned by zhangchangfeng (<email address hidden>) on branch: master
Review: https://review.openstack.org/521364"
1733179,2017-12-10 04:38:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526893"
1733183,2018-01-23 13:41:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733190,2018-01-16 00:45:23 UTC,It appears that the behavior I wanted to add/move was not that of indicator-applet but rather the notification area. At least at the moment things are looking OK.
1733190,2018-02-22 04:30:59 UTC,With notification area it can be replaced kind of.
1733190,2020-05-22 04:17:29 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1733190,2020-05-22 04:17:30 UTC,[Expired for mate-indicator-applet (Ubuntu) because there has been no activity for 60 days.]
1733190,2018-01-16 00:28:38 UTC,I seem to be seeing the same thing in 17.10. Using the Traditional layout if I add indicator-applet I see no change - nothing appears to happen. Using the Redmond layout adding indicator-applet seems to add indicator-applet-complete.
1733192,2018-01-16 15:21:49 UTC,Same issue in Linux Mint version: 18.3 xfce 64-bit
1733194,2017-11-20 15:47:23 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1733194,2017-11-21 02:27:27 UTC,"I upgraded from 16.04, where I was not having this issue. I think that was running 4.10?"
1733194,2018-01-04 18:09:16 UTC,"Just a note, I have the same problem with Intel® Wireless-AC 3168 (firmware version 29.541020.0 op_mode iwlmvm) on Gentoo linux-4.14.8-gentoo-r1 in AP mode (802.11n)."
1733194,2018-06-30 08:12:52 UTC,"I have the same issue with the current Ubuntu 18.04 kernel 4.15.0-23-generic, and also with ubuntu mainline kernel 4.17.0-041700, using Intel Wireless 8260 (Firmware 34.0.1) in AP mode."
1733194,2018-08-19 01:25:33 UTC,"Created attachment 277929
dmesg"
1733194,2018-08-19 12:25:31 UTC,please report this NULL pointer exception to bugzilla.kernel.org and CC <email address hidden> to the bug.
1733194,2017-11-19 17:54:50 UTC,apport information
1733194,2018-08-19 18:03:47 UTC,"So we fail here (last line):
0000000000008e7d <iwl_trans_pcie_txq_enable>:
    8e7d:       e8 00 00 00 00          callq  8e82 <iwl_trans_pcie_txq_enable+0x5>
    8e82:       41 57                   push   %r15
    8e84:       41 56                   push   %r14
    8e86:       49 89 fe                mov    %rdi,%r14
    8e89:       41 55                   push   %r13
    8e8b:       41 54                   push   %r12
    8e8d:       49 89 cd                mov    %rcx,%r13
    8e90:       55                      push   %rbp
    8e91:       53                      push   %rbx
    8e92:       41 89 d4                mov    %edx,%r12d
    8e95:       89 f3                   mov    %esi,%ebx
    8e97:       48 83 ec 20             sub    $0x20,%rsp
    8e9b:       65 48 8b 04 25 28 00    mov    %gs:0x28,%rax
    8ea2:       00 00
    8ea4:       48 89 44 24 18          mov    %rax,0x18(%rsp)
    8ea9:       31 c0                   xor    %eax,%eax
    8eab:       48 63 c6                movslq %esi,%rax
    8eae:       66 89 54 24 02          mov    %dx,0x2(%rsp)
    8eb3:       4c 8b bc c7 08 7e 00    mov    0x7e08(%rdi,%rax,8),%r15
    8eba:       00
    8ebb:       f0 48 0f ab 87 08 8e    lock bts %rax,0x8e08(%rdi)
    8ec2:       00 00
    8ec4:       73 28                   jae    8eee <iwl_trans_pcie_txq_enable+0x71>
    8ec6:       80 3d 00 00 00 00 00    cmpb   $0x0,0x0(%rip)        # 8ecd <iwl_trans_pcie_txq_enable+0x50>
    8ecd:       75 1f                   jne    8eee <iwl_trans_pcie_txq_enable+0x71>
    8ecf:       48 c7 c7 00 00 00 00    mov    $0x0,%rdi
    8ed6:       44 89 44 24 04          mov    %r8d,0x4(%rsp)
    8edb:       c6 05 00 00 00 00 01    movb   $0x1,0x0(%rip)        # 8ee2 <iwl_trans_pcie_txq_enable+0x65>
    8ee2:       e8 00 00 00 00          callq  8ee7 <iwl_trans_pcie_txq_enable+0x6a>
    8ee7:       0f 0b                   ud2
    8ee9:       44 8b 44 24 04          mov    0x4(%rsp),%r8d
    8eee:       44 89 c7                mov    %r8d,%edi
    8ef1:       e8 00 00 00 00          callq  8ef6 <iwl_trans_pcie_txq_enable+0x79>
    8ef6:       4d 85 ed                test   %r13,%r13
    8ef9:       49 89 47 70             mov    %rax,0x70(%r15)"
1733194,2018-08-20 09:54:12 UTC,was already reported: https://bugzilla.kernel.org/show_bug.cgi?id=200855
1733194,2018-09-08 11:10:29 UTC,"I suffer from this bug too, with this card in access point mode:"
1733194,2018-08-19 01:26:29 UTC,"Created attachment 277931
iwlwifi.ko"
1733194,2017-11-19 17:54:48 UTC,apport information
1733194,2018-10-12 09:47:23 UTC,Ping? Is this still reproducible?
1733194,2017-11-19 17:54:46 UTC,apport information
1733194,2017-11-19 17:54:45 UTC,apport information
1733194,2017-11-19 17:54:44 UTC,apport information
1733194,2017-11-19 17:54:43 UTC,apport information
1733194,2017-11-19 17:54:41 UTC,apport information
1733194,2017-11-19 17:54:39 UTC,apport information
1733194,2017-11-19 17:54:38 UTC,apport information
1733194,2017-11-19 17:54:34 UTC,apport information
1733194,2017-11-19 17:54:33 UTC,apport information
1733194,2017-11-19 17:54:31 UTC,apport information
1733194,2017-11-19 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1733194,2017-11-19 17:54:47 UTC,apport information
1733194,2018-10-24 17:14:58 UTC,please re-open if you have the data we asked for.
1733194,2017-11-19 17:54:35 UTC,apport information
1733209,2019-09-03 05:38:48 UTC,"The problem disappears if, in pybridge/network/client.py in register function,
the assignment to anon is changed from:"
1733214,2020-05-24 16:12:08 UTC,"Fix S4 MK2 for Windows
https://github.com/mixxxdj/mixxx/pull/1643"
1733214,2017-11-19 19:01:04 UTC,"I don't have one of these, but I know several friends who do, so I think can spend a few days with one sometime before the 2.1 release on 31/3/2018."
1733214,2017-12-01 19:48:30 UTC,Some quick hacks to update the mapping were committed with https://github.com/mixxxdj/mixxx/pull/1400 but there is still a lot left to do.
1733214,2020-05-24 16:26:12 UTC,"No, this has not been resolved."
1733214,2020-05-24 16:13:02 UTC,@be.ing Does it now include the reqquested controls?
1733225,2019-09-16 08:48:02 UTC,Migrated to https://github.com/widelands/widelands/issues/3229
1733226,2018-06-11 07:58:50 UTC,"Hi,"
1733226,2018-06-11 20:53:37 UTC,"Hi,"
1733226,2018-06-20 20:51:08 UTC,@Yadan
1733226,2018-06-20 21:41:02 UTC,Some random thoughts based on a conversation with Chad in IRC:
1733226,2018-07-11 14:35:21 UTC,likely related to bug 1779139
1733226,2019-09-17 04:17:39 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1733231,2017-11-19 21:45:10 UTC,"Sorry, it looks like I used the tool wrong. I need a backport for Ubuntu 16.04 :( I'll try again."
1733234,2018-06-18 21:33:41 UTC,"I find this is a feature, as it enables me to choose where to place objects along the path."
1733235,2018-02-19 18:24:43 UTC,"My friend's LPD 8 is currently not working, so I probably won't be able to do this for 2.1."
1733236,2017-11-19 22:22:59 UTC,I have just tried the sort again but this time I blocked the lines I wish sorted. It worked and there was no error report doing the sort that way.
1733236,2017-11-19 22:27:04 UTC,I have just noticed that the sort is messed up. I am using indents for next actions and in same cases they have been moved away from their original topic instead of being kept together.
1733238,2017-11-24 22:56:41 UTC,It turns out that tickr is not stealing the focus. The following line in tickr_main.c is the culprit: in update_win_dims_and_loc()
1733238,2020-06-18 12:31:51 UTC,Fixed in version 0.7.0.
1733242,2019-05-16 12:55:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733243,2017-12-13 20:32:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733243,2017-12-17 09:05:35 UTC,I'm having the same Problem. Here is my Crashlog
1733243,2019-07-31 13:29:39 UTC,"It's now fixed in Gnome:
https://gitlab.gnome.org/GNOME/gnome-music/issues/121"
1733245,2018-01-22 23:08:18 UTC,"When we initially moved to GNOME Software we considered using the updates page as the primary means of updating. The issue is that GNOME Software is designed to hide a lot of the package details that update-manager shows. So we need to resolve if we:
- Are happy hiding all package details from the user
- Can modify GNOME Software in some way
- Can keep using both systems (the current state)"
1733245,2017-11-20 08:15:37 UTC,Thank you for your suggestion. That would be nice indeed but lot of work and not a priority at the moment though
1733245,2017-11-20 00:45:13 UTC,also i think three separate applications/icons to manage the software are not nice on the menu
1733245,2018-01-11 16:32:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733256,2019-10-31 04:06:52 UTC,Removing from a milestone as this work will not be done in 2.3 series.
1733270,2017-11-22 07:45:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522158"
1733270,2017-11-24 02:13:18 UTC,"Change abandoned by Masaki Kanno (<email address hidden>) on branch: master
Review: https://review.openstack.org/522158
Reason: I will move the patch to heat-tempest-plugin."
1733278,2017-11-22 07:10:07 UTC,"As discussed on the MP there is too much in flight and this isn't the approach we want to take.
Until importing is settled smoser and myself shall get access to the bastion the importer is running on."
1733281,2018-01-09 23:29:14 UTC,This bug was fixed in the package linux-azure-edge - 4.14.0-1003.3
1733281,2018-01-09 16:43:30 UTC,This issue also affects linux-azure-edge 4.14.
1733281,2018-03-19 10:57:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1733281,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1733282,2018-09-20 18:10:24 UTC,is this happening for 2.2?
1733282,2018-09-20 18:10:51 UTC,"@sblaisot, no problem if you don't have time :) we can bump this to 2.3.0"
1733283,2018-01-24 22:23:34 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1460
1733286,2017-11-30 11:41:14 UTC,"Using the current reference image
https://tarballs.openstack.org/manila-image-elements/images/manila-service-image-master.qcow2
It still appears to be a problem with this bug description，that is,
if the share export in front ,the original share instead of the new share that was created from snapshot, but if the snapshot share export in front,the snapshot share instead of the original share"
1733286,2018-02-15 16:02:13 UTC,From irc manila community meeting 15 February:
1733286,2018-02-15 16:03:00 UTC,more:
1733286,2019-03-22 15:12:43 UTC,Hey Shualli is this still an issue you are running into?
1733286,2019-05-01 15:51:10 UTC,"Has anyone been able to take a closer look at this issues, and try and re-produce it?"
1733286,2019-10-28 19:34:01 UTC,closing issues please re-open if you are still having this issue
1733286,2017-11-20 20:53:12 UTC,Thank you for the detailed report.
1733287,2017-11-22 07:50:37 UTC,not support vmxnet3
1733292,2020-10-10 02:37:08 UTC,"3 years later.
I support Wes's statement about the importance of the bug. This is a real dealbreaker."
1733292,2018-12-10 18:31:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733292,2018-12-10 18:40:58 UTC,How is this only Medium importance ?
1733295,2017-11-22 10:35:31 UTC,"Hi all,"
1733301,2017-12-11 14:14:12 UTC,"This looks like the notification area to me. Three dots at the left of the applet... the indicator applet doesn't have them.
You can check it yourself: right-click on these dots -> (menu appears) -> click on About menu item."
1733301,2017-12-13 13:58:37 UTC,See also the screenshot here:
1733301,2017-12-20 10:57:10 UTC,Thanks for your reply. I have been busy but I am willing to provide all information needed. I took a couple of screenshots to show and explain the issue I noticed.
1733301,2018-01-06 18:09:29 UTC,"Thanks, this confirms it's really mate-indicator-applet. I was also able to reproduce it with SpiderOak (see the link to UM community thread above)."
1733301,2018-01-06 18:39:03 UTC,"Can reproduce with VLC too, provided that the current icon theme doesn't have a proper size icon for it. For example, mate-icon-theme-faenza has it, so it's not reproducible."
1733301,2018-01-07 09:52:59 UTC,Update: reproduced with Mumble and Clementine in 18.04.
1733301,2018-07-15 08:18:57 UTC,I can also confirm this; there are significant amount of posts on the community website. The default theme/s and Numix theme on UM both pose similar cropped-out icons:
1733301,2018-10-06 13:43:49 UTC,"I can reproduce this in Ubuntu Mate 18.04.1 LTS with the Synology Cloud Station application. The indicator applet just shows a huge icon, and never scales it when the panel is resized."
1733301,2019-01-29 14:00:14 UTC,"I also can reproduce the original issue on Ubuntu Mate 18.10, with Synology Cloud Station. Synology Cloud Station icon is huge and will not scale. Indicator Applet Complete 1.20.1.
Same as previous report, this is not an issue on Gnome and KDE."
1733301,2017-11-21 08:35:41 UTC,I have seen this with Qt applications such as Mumble and VLC. It is also evident with Steam.
1733301,2017-12-20 10:58:44 UTC,Attaching Screenshot from Ubuntu-Mate 17.10 showing both Steam and Cloudstation Indicators
1733305,2017-12-13 14:09:28 UTC,"This seems like a nice to have - no objections to the code being written, but it wil not be a priority"
1733307,2020-04-17 01:57:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733311,2017-12-28 10:00:16 UTC,I discovered the root cause of the issue by comparing the output of `pip freeze` on both servers.
1733311,2017-12-11 19:17:08 UTC,Just started hitting this as well. Simply importing the OpenSSL library raises the AttributeError:
1733311,2017-12-28 09:44:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733311,2017-12-28 09:46:47 UTC,I experience the same issue after upgrading from 14.04.5 to 16.04.3. Other server where 16.04.3 has been installed from fresh doesn't have the issue.
1733312,2018-07-20 11:32:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733315,2017-12-19 22:39:20 UTC,Appears this is coming from somewhere in the client code.
1733315,2017-12-19 22:50:27 UTC,"Verified this command works fine with ""cinder backup-restore --volume <uuid> <backup_uuid>""."
1733315,2018-12-05 15:54:39 UTC,I have tried to reproduce the error but It seems like the CLI has been fixed. Should I close this?
1733315,2018-12-05 19:53:09 UTC,"Sofia, the example you give shows using the cinder CLI. Did you test this with the openstack client CLI?"
1733315,2018-12-12 16:14:31 UTC,"The current status of this bug is unclear.  Sofia, have you verified that this works without error on the openstack client as well as the cinderclient?  If not, that needs to be done before we can close this."
1733315,2018-12-13 05:50:25 UTC,So after digging into the matter i found out that cliff expects a list with two tuples (columns and its respective data) to display in a tabular format whereas the restore class returned VolumeBackupsRetore object as to what sean explained.
1733315,2018-12-12 16:22:03 UTC,The same problem persists in master
1733315,2019-11-11 10:30:52 UTC,Hello Team
1733315,2018-12-13 05:54:00 UTC,Proposed Fix : https://review.openstack.org/#/c/624860/
1733315,2019-11-11 16:06:46 UTC,"Hi Deepa,"
1733316,2017-11-28 05:09:22 UTC,Is it 2.4.x specific?
1733316,2018-01-20 07:40:14 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-794
1733320,2017-11-21 01:01:46 UTC,"Dear Mohammad,"
1733320,2017-11-22 06:59:38 UTC,Both stars are binary stars and Stellarium doesn't compute summary magnitude of these stars. It's definitely not just catalog issue.
1733320,2018-09-19 14:00:18 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/369
1733321,2017-11-29 09:41:07 UTC,I have opened bug 1734908 for the systemd issue.
1733321,2017-11-20 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1733321,2017-11-21 17:10:01 UTC,"The issue seems to be related somehow to systemd's systemd-rfkill.service. When fake-rfkill is loaded, the following message are logged on syslog:"
1733321,2017-11-23 15:26:17 UTC,The issue seems to be reproducible only when the VM has a single virtual CPU. I cannot reproduce it when I assign 2 or more CPUs to the VM. That would explain why we could not reproduce the issue on the host.
1733321,2017-11-24 18:34:45 UTC,This is the stack trace of the systemd-rfkill process before it gets killed by systemd after the timeout:
1733321,2017-11-28 15:03:42 UTC,It turns out that the commit mentioned on the previous comment is necessary but not sufficient to fix the issue. The testcase also needs to be fixed.
1733321,2017-11-27 12:20:52 UTC,"The systemd rfkill timeout issue is not specific to ppc64el, I was able to reproduce it in a VM with my local x86_64 laptop."
1733321,2017-11-27 14:55:52 UTC,The following systemd upstream commit fixes the service timeout issue:
1733321,2020-04-28 23:14:46 UTC,"Hello Kleber, or anyone else affected,"
1733321,2020-05-05 18:48:50 UTC,"autopkgtests pass:
http://autopkgtest.ubuntu.com/packages/network-manager/bionic/ppc64el
http://autopkgtest.ubuntu.com/packages/network-manager/eoan/ppc64el
http://autopkgtest.ubuntu.com/packages/network-manager/focal/ppc64el"
1733321,2020-05-02 04:49:05 UTC,This bug was fixed in the package network-manager - 1.22.10-1ubuntu3
1733321,2020-04-29 16:32:48 UTC,"All autopkgtests for the newly accepted network-manager (1.20.4-2ubuntu2.3) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1733321,2020-04-29 13:46:08 UTC,"All autopkgtests for the newly accepted network-manager (1.22.10-1ubuntu2) for focal have finished running.
The following regressions have been reported in tests triggered by the package:"
1733321,2020-04-29 04:41:35 UTC,"All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.5) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1733321,2020-04-28 23:26:40 UTC,"Hello Kleber, or anyone else affected,"
1733321,2020-04-28 23:12:34 UTC,"Hello Kleber, or anyone else affected,"
1733321,2020-08-18 15:24:27 UTC,This bug was fixed in the package network-manager - 1.20.4-2ubuntu2.3
1733321,2020-04-07 14:24:35 UTC,"Yep, we will get this fixed - I'll assign Seyeong work with him on it."
1733321,2020-04-03 15:51:43 UTC,"Thanks!  Could you check the rfkill code, also?  I think instead of patching the testcase, it would be better fix rfkill so the change is effective as soon as it returns; that way users won't experience this and have to add their own sleep after calling rfkill."
1733321,2020-04-03 07:28:32 UTC,"Hello, I uploaded pkg to ppa https://launchpad.net/~xtrusia/+archive/ubuntu/lp1733321"
1733321,2020-03-25 19:08:20 UTC,"@dgadomski if you have time, could you check this and upload a fixed package?"
1733321,2019-12-09 14:48:57 UTC,"Still occurring on d/e/f, e.g.:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/n/network-manager/20191208_021641_f90a7@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/n/network-manager/20191130_013521_8a691@/log.gz"
1733321,2018-08-17 04:41:11 UTC,"Artful is End Of Life, and thus, there is nothing else to sponsor; sorry."
1733321,2017-11-30 10:51:22 UTC,"Although we haven't seen the failure in Bionic yet, it might be a good idea to apply the fix on Bionic as well, which as of now has the same package version as Artful."
1733321,2017-11-29 16:55:39 UTC,This is a debdiff for Artful applicable to network-manager 1.8.4-1ubuntu3. This was built with pbuilder and the testcase shipped with the source packaged works as expected (on the environment described on this bug report only if the fix for bug 1734908 is also applied).
1733321,2020-04-07 13:48:37 UTC,"Dan, Seyeong, is one of you commited to work on a proper fix there? Can you take assignement of the bug? It would be nice to see the problem resolved and without a slap hacking if possible :-)"
1733321,2020-08-18 15:24:31 UTC,"The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1733322,2017-11-21 10:50:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1733322,2018-09-03 23:19:16 UTC,"The bug is still there for
lsb_release -rd
Description:	Ubuntu 18.04.1 LTS
Release:	18.04"
1733322,2017-11-21 10:52:12 UTC,the error and lack of proper feedback is also mentioned upstream in https://bugzilla.gnome.org/show_bug.cgi?id=785617
1733322,2017-09-24 14:38:38 UTC,"Sumary says it all. The ON/OFF switch in screen sharing tab is stuck in OFF position and is not reacting to clicks. Thus, screen sharing cannot be enabled."
1733322,2017-12-19 16:59:45 UTC,Just realized I have the same error in my syslog as Tomasz:
1733322,2017-11-22 13:18:47 UTC,"This happens to me as well.  In my case it is because I have only wired network access, but the network connection is ""unmanaged"" by NetworkManager (and does not show up on the networks page of gnome-control-center).  This in turn leads to the networks list in the sharing dialog being empty."
1733322,2017-11-22 14:34:18 UTC,thanks
1733322,2017-11-22 16:37:07 UTC,"To clarify, Emil installed Ubuntu 17.10 starting from a server install which I believe does not use NetworkManager by default. I believe the vast majority of people using Ubuntu won't be affected by this issue."
1733322,2021-01-06 11:59:37 UTC,I have been experiencing the same. Is there any workaround meanwhile?
1733322,2017-12-18 21:22:37 UTC,"I have this problem too for my wired connection only.
It is managed by Network Manager and yet it doesn't appear on the the Network List.
If I connect to a Wifi network that will appear on the list and allow me to toggle on/off."
1733322,2017-11-22 13:22:03 UTC,"Sebastien, thanks for the quick response.  I found an existing upstream bug (https://bugzilla.gnome.org/show_bug.cgi?id=788097) which, while lacking detail, seemed to match.  I linked it to this issue."
1733322,2017-12-18 21:46:26 UTC,"I have tried the workaounds listed here
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1733322"
1733333,2017-12-18 04:12:08 UTC,A tray indicator showing the UFW status would be useful; it used to be a feature but was removed.
1733333,2020-10-23 16:07:29 UTC,"Hi,
Thank you so much for the ideas, but current code is not valid or complicate for implementing them.
I'll keep them in mind if I improve Gufw in the future.
A hug"
1733338,2017-11-20 19:32:42 UTC,Do you feel like making a fix for this? :p
1733338,2017-12-25 14:32:14 UTC,"""No new downloads if speed exceeds (0 = disable)"" has the maximum value to 100 000 in the wizard but the maximum value in the settings is 90 000 KiB/s. I believe it should be 122 000 so even those users with 1000 mbit can use all their speed."
1733352,2017-11-20 17:14:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733353,2017-11-20 17:06:47 UTC,"Hello Balint, or anyone else affected,"
1733353,2017-11-20 19:34:55 UTC,"Hello Balint, or anyone else affected,"
1733353,2017-11-21 01:00:21 UTC,"The verification of the Stable Release Update for hibagent has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1733353,2017-11-21 08:17:25 UTC,"Launched a trusty instance on ec2, installed linux-aws kernel, rebooted, enabled proposed and installed hibagent (1.0.1-0ubuntu1~14.04.1). The installation was successful and installed a couple of extra new packages from main.
There are no preinst/postinst scripts thus it is inert by default, e.g. there was no hibagent running."
1733353,2017-11-21 08:25:09 UTC,"Releasing this as is. The issues you have pointed out are valid, please fill in a new bug for those and we'll be asking the maintainer to fix them with the next upload if possible."
1733353,2017-11-21 08:25:19 UTC,This bug was fixed in the package hibagent - 1.0.1-0ubuntu1~14.04.1
1733353,2017-11-21 01:00:15 UTC,This bug was fixed in the package hibagent - 1.0.1-0ubuntu1~16.04.1
1733353,2017-11-21 00:59:49 UTC,"Confirmed that installing the hibagent package from xenial-proposed works on a generic system and does not try to start the service (no postinst), and that it leaves no file debris behind on an install, reinstall, remove, purge (piuparts-like test).  This works including if 'enable-ec2-spot-hibernation' is called in the middle."
1733355,2017-11-20 16:44:36 UTC,this is a known issue upstream.
1733356,2017-11-30 03:22:13 UTC,Fixed in: https://review.openstack.org/#/c/521478/
1733366,2017-12-12 17:09:54 UTC,"I see the same thing on Ubuntu 16.04 / apport 2.20.1-0ubuntu2.14 - same apport command line (except a different PID number), same error number and everything."
1733366,2017-12-13 17:38:38 UTC,There is an errors bucket for this:
1733366,2017-12-13 19:12:20 UTC,artful fix
1733366,2017-12-13 19:02:16 UTC,The updates for this fix will need to go through security since many people are getting the package from there.
1733366,2017-12-15 06:54:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733366,2018-05-11 19:17:49 UTC,"I've uploaded the trusty apport package to the ubuntu-security-proposed ppa (https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/) for testing, and will likely release this next week. Any feedback is appreciated."
1733366,2018-05-04 18:53:43 UTC,"Thanks, Brian, reviewing now."
1733366,2018-04-20 21:19:16 UTC,The function was slightly in Trusty but the attached debdiff should fix the crash seen in the Error Tracker.
1733366,2018-04-20 20:44:38 UTC,This could use fixing for Trusty too.
1733366,2018-01-03 20:27:59 UTC,This bug was fixed in the package apport - 2.20.7-0ubuntu3.7
1733366,2018-01-03 20:27:57 UTC,This bug was fixed in the package apport - 2.20.1-0ubuntu2.15
1733366,2018-05-14 23:34:17 UTC,This bug was fixed in the package apport - 2.14.1-0ubuntu3.28
1733366,2018-01-03 20:27:52 UTC,This bug was fixed in the package apport - 2.20.4-0ubuntu4.10
1733366,2018-01-02 19:32:34 UTC,"Thanks for the updated debdiffs! They look pretty good to me but I'm wondering if was intentional that True is returned when the ""not os.path.exists()"" checks are true but the exception handler returns False when os.readlink() throws an errno.ENOENT OSError exception? IIUC, both situations occur when the namespace files don't exist but one situation returns True and the other False."
1733366,2017-12-15 23:27:13 UTC,And the xenial one.
1733366,2017-12-15 23:24:11 UTC,Here's a zesty debdiff.
1733366,2017-12-15 23:11:28 UTC,Here's an improved artful debdiff taking into account Seth's comments.
1733366,2017-12-13 19:13:23 UTC,xenial fix
1733366,2017-12-13 23:22:06 UTC,This bug was fixed in the package apport - 2.20.8-0ubuntu4
1733366,2018-01-02 20:08:15 UTC,"Ah, yes it should return True. Thanks for catching that! To be absolutely clear:"
1733366,2017-12-13 22:54:17 UTC,"To clarify, I think these patches may reduce the number of reports in the error tracker; but to eliminate the reports, the exception needs to be handled."
1733366,2017-12-13 21:00:44 UTC,Note that these fixes are susceptible to a race condition; better would handle the exception from Python. Probably returning 'false' is the right option in that case. (Assuming that's the case that then does less processing.)
1733366,2017-12-13 19:12:51 UTC,zesty fix
1733369,2017-11-20 17:25:58 UTC,"Upon further inspection, this isn't actually a tab-switching issue.  Hit Return a bunch of times, and then Ctrl-L; your prompts will ghost temporarily.  Furthermore, my blinking cursor also ghosts from time to time."
1733369,2017-11-24 10:23:18 UTC,Maybe related to bug 1726262?
1733369,2017-11-24 15:08:39 UTC,"On Fri, Nov 24, 2017 at 10:23:18AM -0000, Egmont Koblinger wrote:

> Maybe related to bug 1726262?
"
1733379,2019-02-05 07:43:09 UTC,This seems to be a duplicate of bug 1705820 and bug 1804832
1733379,2020-06-23 11:27:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733379,2018-01-21 11:35:26 UTC,"I see.
Because of that I did reinstaller the driver, letting the driver rebuilding."
1733379,2018-01-13 15:23:05 UTC,"The filename doesn't match the vermagic
filename: /lib/modules/4.4.0-104-generic/updates/dkms/8812au.ko
vermagic: 4.4.0-101-generic SMP mod_unload modversions"
1733379,2018-01-07 15:08:09 UTC,"root@ubabbu16:~# modinfo 8812au
filename:       /lib/modules/4.4.0-104-generic/updates/dkms/8812au.ko
version:        v4.3.8_12175.20140902
author:         Realtek Semiconductor Corp.
description:    Realtek Wireless Lan Driver
license:        GPL
srcversion:     5E9D12706FAF7E2BB4F284E
alias:          usb:v2357p0103d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2357p0101d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v20F4p805Bd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2001p3316d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2001p3315d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v07B8p8812d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2019pAB30d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1740p0100d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v13B1p003Fd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1058p0632d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2001p3313d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0586p3426d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E66p0022d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0B05p17D2d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0409p0408d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0789p016Ed*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v04BBp0952d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0DF6p0074d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v7392pA822d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2001p330Ed*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v050Dp1106d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp881Cd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp881Bd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp881Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp8812d*dc*dsc*dp*ic*isc*ip*in*
depends:
vermagic:       4.4.0-101-generic SMP mod_unload modversions
parm:           rtw_ips_mode:The default IPS mode (int)
parm:           rtw_usb_rxagg_mode:int
parm:           rtw_qos_opt_enable:int
parm:           ifname:The default name to allocate for first interface (charp)
parm:           if2name:The default name to allocate for second interface (charp)
parm:           rtw_initmac:charp
parm:           rtw_channel_plan:int
parm:           rtw_special_rf_path:int
parm:           rtw_chip_version:int
parm:           rtw_rfintfs:int
parm:           rtw_lbkmode:int
parm:           rtw_network_mode:int
parm:           rtw_channel:int
parm:           rtw_mp_mode:int
parm:           rtw_wmm_enable:int
parm:           rtw_vrtl_carrier_sense:int
parm:           rtw_vcs_type:int
parm:           rtw_busy_thresh:int
parm:           rtw_ht_enable:int
parm:           rtw_bw_mode:int
parm:           rtw_ampdu_enable:int
parm:           rtw_rx_stbc:int
parm:           rtw_ampdu_amsdu:int
parm:           rtw_vht_enable:int
parm:           rtw_lowrate_two_xmit:int
parm:           rtw_rf_config:int
parm:           rtw_power_mgnt:int
parm:           rtw_smart_ps:int
parm:           rtw_low_power:int
parm:           rtw_wifi_spec:int
parm:           rtw_antdiv_cfg:int
parm:           rtw_antdiv_type:int
parm:           rtw_enusbss:int
parm:           rtw_hwpdn_mode:int
parm:           rtw_hwpwrp_detect:int
parm:           rtw_hw_wps_pbc:int
parm:           rtw_max_roaming_times:The max roa..."
1733379,2018-01-07 12:43:54 UTC,"andrea there is an issue involving dkms that causes the module to be build on the old kernel source rather than the new kernel.  Open terminal and enter ""modinfo 8812au"" post the output"
1733381,2019-08-29 17:49:14 UTC,I think this bug is no longer relevant.
1733381,2017-11-21 13:24:06 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.openstack.org/521613"
1733381,2017-11-20 17:54:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/521613"
1733381,2017-11-21 12:48:38 UTC,Related bug https://bugs.launchpad.net/tripleo/+bug/1730917
1733381,2017-11-20 19:09:55 UTC,spec update https://review.rdoproject.org/r/10592
1733384,2017-11-20 18:09:43 UTC,https://github.com/linuxmint/Cinnamon/issues/7055
1733388,2020-03-24 13:33:23 UTC,"Fixed in commit e5d0781, released in 0.7."
1733388,2017-11-21 11:54:27 UTC,"17:56 <rbasak> cjwatson or wgrant: could I have your opinion on bug 1733388 please? I've identified what's going on, but am not sure which component is making the wrong assumption.
17:57 <ubot5> bug 1733388 in usd-importer ""py.test-3 test discovery hangs when importing ubuntutools.lp.lpapicache Launchpad object"" [Undecided,New] https://launchpad.net/bugs/1733388
17:57  * rbasak will be EOD in the next few minutes though, so no rush.
18:04 <cjwatson> rbasak: Well, um, I guess my opinion is that ubuntutools is distressingly and excessively magical.  We don't maintain it though ...
18:05 <cjwatson> I mean pytest also contains a lot of magic.  (I prefer less magical test runners.)
18:05  * rbasak isn't entirely sure what benefit use of this gives us over launchpadlib.launchpad. Presumably caching
18:06 <cjwatson> I guess it must be.
18:06 <cjwatson> I normally only use ubuntutools for its handy question-asking thing in my code.
18:08 <cjwatson> One perhaps reasonable fix would be to cause ubuntutools to not do the login thing for attributes that begin with '_'?
18:09 <rbasak> I suppose. I'm not very keen on this auto-login-on-getattr behaviour. But perhaps that's fundamental to the module.
18:10 <rbasak> OTOH it leads to side-effects such as UI prompts, so perhaps it's bad and it should be explicit.
18:10 <rbasak> It seems that I can work around it by not importing the Launchpad object into the module namespace.
18:11 <rbasak> So I could just leave the bug open against python3-ubuntutools for now I suppose.
18:13  * rbasak EODs
18:13 <cjwatson> Yeah, to me this sort of thing makes it not suitable for general-purpose use."
1733392,2017-11-20 20:32:28 UTC,"Damn, missed the nestedness."
1733392,2017-11-21 09:28:58 UTC,This is how it looks our nested config:
1733392,2017-11-21 10:12:59 UTC,"That actually looks like you're trying to place rabbitmq-server inside a
container inside a KVM container, which is the ""nested placement not
supported"".
If you were trying to colocate it inside the KVM, or if you were just
trying to put the rabbitmq-openstack as a host machine it might work.
I'm not positive around this, but nested *should* mean
containers-inside-containers."
1733392,2017-11-20 20:24:54 UTC,"The recent work with bundle placements may well give you what you need, but it isn't clear to me exactly what you are after."
1733392,2017-11-21 15:10:41 UTC,"John, I've copied the wrong part of the stage1, the real config is not pointing to LXD it to KVM. Alvaro explained better than me"
1733392,2017-11-29 04:38:08 UTC,"Instead of showing the current bundle YAML, how about you explain what you are deploying, and how you'd like to see it end up, and we can then show the placement directives to do that, or say it can't be done."
1733392,2017-11-29 14:18:30 UTC,"Hey Tim,"
1733392,2017-12-12 11:21:12 UTC,"It feels like the real request is for ""indexed"" placements, rather than ""nested"" placements.
However, I'd also like to understand why you need to concretely address the ""2nd"" unit of the application, rather than ""all"" units of the application.
Is there something you want to be on the first instance, but not on the 3rd?
I also wonder if this is *really* what you want. As an example."
1733392,2017-11-20 20:29:20 UTC,"applications:
  compute-baremetal:
    charm: cs:ubuntu
    num_units: 3
  special-config-charm:
    charm: special-config-charm
    num_units: 3
    to: [""compute-baremetal/0"", ""compute-baremetal/1"", ""compute-baremetal/2""]
    # to: [compute-baremetal] would probably work too
  myapp-charm:
    charm: myapp-charm
    num_untis: 3
    to: [""special-config-charm/0"", ""special-config-charm/1"", ""special-config-charm/2""]
    # to: [special-config-charm] would probably work too"
1733392,2017-11-21 11:46:10 UTC,"Hi Tim, John,"
1733394,2018-02-09 22:14:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733394,2018-02-10 00:12:10 UTC,Mines 3.26.0 - Ubuntu 17.10
1733403,2019-09-18 04:17:33 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1733403,2019-07-19 21:03:43 UTC,"Thank you for filing the bug.  I believe most of these issues in cloud-init have been resolved in newer releases.  If you're still having issues, please see if the images with more recent cloud-init are successful."
1733411,2019-09-19 11:56:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1733414,2018-01-14 10:36:58 UTC,"Hello,
   Can you please send us the exact command that you used for the backup/restore along with the versions information. Also please send us the total DB size and the complete o/p of the xtrabackup command when the backup is complete and similarly for the restore."
1733414,2018-01-20 07:44:55 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1483
1733422,2017-12-07 10:25:23 UTC,Fix commited in master in c1dc7dd75c5f43b109d06444375dad58ff49872b
1733422,2017-12-07 00:20:42 UTC,MR for this bug. https://gitlab.com/inkscape/inkscape/merge_requests/158
1733422,2017-11-22 08:11:02 UTC,"Jabiertxof:
A lot of things. I've realized that the problem it's convert the object
copied to the clipboard to paths. I've tried and work pretty well."
1733422,2017-11-20 21:56:49 UTC,The file svg only have the object copied to the clipboard (Ctrl+c) indeed. I've tried to draw a path with Bezier or Pencil Tool with form: from clipboard  o Bend from the clipboard and nothing has been drawn. Besides has created two copies of the original object.
1733422,2017-11-20 21:34:45 UTC,"Hi, thanks for report.
Please provide your inkscape version, and if posibol a SVG with the clipboard shape/item."
1733422,2017-11-21 22:59:41 UTC,"The problem is yur path is a svg:rect not a svg:path. From clipboard only work with paths, not shapes and bend from clipboard work with shapes who acept LPE (svg:rects dont acept it)."
1733422,2017-11-20 21:48:21 UTC,I've used the 0.92.2 version  with Windows 10 updated to the Fall Create Update. It's posible the bug was caused by the last update the Windows 10.
1733423,2018-11-28 07:23:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733428,2017-11-20 22:15:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521666"
1733428,2017-12-11 20:24:39 UTC,"Change abandoned by Christopher Dearborn (<email address hidden>) on branch: master
Review: https://review.openstack.org/521666
Reason: This change was already incorporate at some point in the past."
1733432,2017-11-21 17:38:46 UTC,This would be really great to have as the majority of the artefacts saved in Mahara instances is often images.
1733435,2019-04-11 07:40:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733450,2017-12-11 15:05:23 UTC,I'm setting importance to Low because there is a bunch of workarounds and the issue doesn't brake workloads.
1733450,2017-11-22 21:30:29 UTC,Created a review https://review.fuel-infra.org/#/c/37267
1733450,2017-11-22 03:11:17 UTC,"@dsutyagin, Thanks for pushing this into cinder:)"
1733450,2017-11-22 21:12:46 UTC,Here is a preliminary patch to Cinder which resolves the issue with volume creation from a 0-byte reference image.
1733450,2017-11-21 02:27:00 UTC,"Looks like it's indeed an issue in Horizon (or Glance?).
Here is how requests to Cinder API look like:
 - VM is spawn from image with Create a new Volume: http://paste.openstack.org/show/626882/
 - Create Volume is used on Images tab: - http://paste.openstack.org/show/626881/"
1733450,2017-11-21 01:37:09 UTC,"test showed that with subsequent VM boot with ""Create a new Volume"", this function (_create_from_image) is not used at all. Need to find what function is used, and somehow refer to  the same code when ""Create Volume"" is used."
1733450,2017-11-22 03:02:25 UTC,"I've made a patch for Horizon (mitaka / MOS 9.0), attached, it resolved the issue. However after I made it I realized that it's better to fix this in Cinder instead of Horizon. I'll try to make a patch for Cinder instead."
1733450,2017-11-21 02:38:50 UTC,"Also in 1st case the internal URL is used, while in second - public URL. Probably insignificant but may help find where and what is going on."
1733459,2017-11-21 19:20:56 UTC,"> 1. There is no .desktop file included with the package
    (I copied one from my Lubuntu 17.04 distro, and renamed the exec line)
    (See screenshot0)
"
1733459,2017-11-21 19:21:34 UTC,"O, and please, next time file three different bugs. This combination makes it hard to track."
1733465,2018-06-26 10:31:01 UTC,"I had same symptoms. After disabling/renabling sync a few times, etc. I got some more specific symptoms:"
1733465,2020-12-29 22:21:01 UTC,"Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1733467,2017-12-05 11:54:41 UTC,"@james beedy,"
1733468,2017-12-12 11:50:04 UTC,This is very odd:
1733487,2017-11-21 05:20:22 UTC,policykit-1 ?!  I will swear I picked debian-installer
1733492,2017-11-21 07:38:24 UTC,"Note: I'm on edge (335) at the moment, the following is the full log for"
1733492,2017-11-21 07:47:26 UTC,"Did the same with the stable snap, same result"
1733492,2017-11-21 08:03:21 UTC,"I wanted to do the same with a namspace set via --bug but I always end up at
 $ git ubuntu tag --logical --bug testnamespace1733492
 11/21/2017 09:01:53 - ERROR:HEAD is not a defined object in this git repository."
1733492,2017-11-22 03:48:40 UTC,"Submit does not know what a merge is and never pushed tags. If you need to
push tags, you should push them separately. In fact, the only thing we push
is the branch that is to be merged."
1733492,2017-11-22 03:50:21 UTC,Are you in a detached head state? Can you provide what git show HEAD says?
1733492,2017-11-24 06:56:39 UTC,"Hi Nish,
due to my console config this is already in the log.
Also as I outlined it really reproduces in 100% of the time, so someone else could try to run the same commands and check if it happens for you as well."
1733492,2017-11-29 10:21:01 UTC,"BTW I'm +1 on your suggestion of a submit ""for-merge"" option.
I even think the tags are not hard, they are the same you derive in ""git ubuntu tag"" but for the version that referenced as ""old/ubuntu"".
All of this needs the usual --bug namespace code as well as it could be <bug>/old/ubuntu.
But overall you already have all code, just need to tie it together in a new way for this."
1733498,2020-01-25 16:06:44 UTC,image.v1 is deprecated so I think this bug is not valid anymore.
1733498,2018-01-18 09:41:28 UTC,glance seems to return 204 only as per api-ref and source code
1733498,2018-03-01 05:44:02 UTC,"I seem can not reproduce this in my system(Pike version),"
1733498,2018-06-14 08:41:47 UTC,Is it still reproducible?
1733506,2017-11-21 07:48:03 UTC,"Note: The second part of title is glitch, I thought I changed it but it is still there, please ignore!"
1733511,2019-06-13 17:46:18 UTC,"Is this still a problem?  On my server, it was correctly installed as a folder."
1733511,2019-06-14 11:48:13 UTC,"Sorry this is two years ago i don't use radical at this moment thanks for
the reply best regards Carsten"
1733511,2019-08-14 04:17:17 UTC,[Expired for radicale (Ubuntu) because there has been no activity for 60 days.]
1733516,2019-10-07 00:55:51 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1733516,2019-10-07 22:47:53 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1733531,2019-10-10 10:10:45 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1733545,2017-11-21 13:56:26 UTC,Adding the following exception:
1733545,2017-11-21 14:16:20 UTC,"A possible way to repair it would be to use an synchronizer using external uuids in the OVSDB. For example, if we use the ""description"" field in the Physical_port table to store Neutron L2Gateway Connection UUID:"
1733553,2018-01-25 12:23:29 UTC,I think this is resolved in newer babel versions by this commit:
1733553,2018-01-25 12:25:29 UTC,This is probably resolvable with a pick for the 1.x maintenance branch of the commit in #1; a standalone test case would be useful for the SRU process to be initiated.
1733554,2017-11-21 15:36:38 UTC,This bug was fixed in the package ruby-em-http-request - 1.1.5-1build1
1733554,2018-03-08 15:08:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733560,2017-11-27 18:28:31 UTC,"This issue is seen when there are no records to display in the grid. In this case, it still shows ""Loading results"" though the response is fetched.
If there are records, they are displayed correctly."
1733563,2019-04-22 02:59:14 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
Thanks."
1733563,2019-06-21 04:17:29 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1733564,2017-11-21 15:53:46 UTC,"Hey Paolo, thanks for the bug. For the sake of those of us who aren't kernel pros, would you mind explaining exactly what the issue is, here? What is /lib/firmware, why would one have a kernel without it, and why is this only surfacing now?"
1733564,2017-11-21 16:06:44 UTC,"During the 4.14+ cycle, the 'make firmare_install' target was completely removed from upstream, and any invokation of that target result in an error now:"
1733564,2017-11-21 17:20:33 UTC,"Exactly the info I wanted, thank you!"
1733564,2017-11-21 17:21:34 UTC,PR available here: https://github.com/snapcore/snapcraft/pull/1750
1733569,2017-11-22 14:40:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1733569,2018-03-26 13:21:16 UTC,That's being discussed upstream in https://bugzilla.gnome.org/show_bug.cgi?id=774492
1733569,2017-11-22 00:15:56 UTC,The column change not kept is surely Bug #1152226
1733569,2017-11-21 12:29:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1733569,2017-11-22 00:11:48 UTC,"If that helps - I have
nautilus/artful,now 1:3.26.0-0ubuntu1 amd64 [installed]"
1733571,2018-03-10 05:38:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733571,2018-11-05 11:30:55 UTC,Confirmed in bionic. This seems to be a known issue and needs further investigation to see if it was fixed upstream of if there is a workaround available. maybe via gss-proxy? Have to check.
1733571,2019-11-28 14:37:26 UTC,I don't think freeipa is to blame here
1733575,2017-11-21 12:02:34 UTC,And in addition the default case as screenshot as well
1733575,2017-11-21 12:12:07 UTC,Example document:
1733575,2017-11-22 10:24:08 UTC,"I should add that it does not happen with all PDF files, but it is reproducible with the linked document."
1733575,2019-07-23 08:20:23 UTC,Confirming with evince 3.28.4 in Ubuntu 18.04
1733575,2019-07-27 06:57:23 UTC,"Upstream bug closed as issue reported against a version of evince too old for GNOME developers to consider fixing. Problem is fixed in later versions of evince, e.g. 3.32."
1733578,2020-09-27 09:43:16 UTC,"I checked to see if this is still present (which it is in Groovy). I found the underlying string in the source code which turns out to be:
""You can try ${RELEASE} without making any changes to your computer,
 directly from this ${MEDIUM}.""
(https://git.launchpad.net/ubuntu/+source/ubiquity/tree/debian/ubiquity.templates#n52)"
1733582,2017-11-22 10:26:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733582,2017-11-23 12:45:28 UTC,Thanks for filing this issue.
1733582,2017-11-21 12:40:55 UTC,The package is allready available upstream (https://packages.debian.org/sid/intel-microcode)
1733582,2017-11-21 16:06:30 UTC,This bug was fixed in the package intel-microcode - 3.20171117.1
1733603,2018-01-03 05:48:19 UTC,This affects our project as well. You can see it in the live here: https://code.launchpad.net/~otto/+recipe/mariadb-10.3-dev-daily
1733603,2018-06-06 15:29:36 UTC,Any update over this issue ?
1733603,2018-10-23 03:57:42 UTC,The following patch fixes this bug. I cannot figure out how to fork and request a merge on launchpad.
1733603,2018-11-23 22:13:49 UTC,~tintou it looks like this bug is assigned to you. Can you share with us a status?
1733603,2019-01-16 08:45:46 UTC,Was this bug resolved or Launchpad still fails with submodules?
1733603,2019-04-27 04:26:45 UTC,Is there any workaround for this? Trying to clone using the debian/rules is not working as well. Can someone enlighten me?
1733603,2019-05-17 23:23:02 UTC,It also affects a project I'm running. Is there any progress on this issue?
1733603,2019-06-02 19:20:04 UTC,Any update on this?
1733603,2020-02-16 14:32:56 UTC,"Hi, while Sergey work around is great, my issue is that when the git repository is using a different commit of the submodules, this can break code compilation. Therefore I was wondering when the patch proposed by [ezzieyguywuf] would be accepted and go to mainstream ? For now I'm using nest in order to build the packages but as soon as a new submodule commit is used, this break oackage building as a result of a compilation failure ..."
1733603,2020-09-23 16:17:12 UTC,"Is there anyone who can merge the patch proposed by [ezzieyguywuf]? It solves the bug, I attached it to this comment."
1733609,2017-11-21 17:00:06 UTC,I have migrated this to Storyboard where neutron-lbaas bugs are now tracked: https://storyboard.openstack.org/#!/story/2001297
1733609,2017-11-21 15:33:05 UTC,"I'm going to change the component to neutron-lbaas since this doesn't seem to be caused by code in neutron proper.  Looking at the lbaas code quickly, it looks like this file:"
1733617,2017-11-21 15:21:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521892"
1733625,2017-11-29 12:17:24 UTC,"It might be possible to mutate the file, rather than completely replacing it; it would be nice to understand the specific use case where this is required."
1733626,2019-07-25 01:40:04 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1733634,2018-02-26 15:17:39 UTC,"Related fix proposed to branch: feature/s3api
Review: https://review.openstack.org/548052"
1733634,2017-11-22 22:43:18 UTC,"I don't see SHA256 support in TempURL. As far as I see, it's SHA-1 only."
1733634,2017-11-27 18:07:06 UTC,"Interesting. I confirmed that TempURL SHA256 signatures do in fact work with Rackspace Cloud Files , which is based on Swift."
1733634,2017-11-29 19:58:19 UTC,"Yeah, sha256 definitely isn't supported -- the only place we even mention it in code is in the encryption-of-object-data-at-rest feature. Got any docs for the cloud files work? https://developer.rackspace.com/docs/cloud-files/v1/use-cases/public-access-to-your-cloud-files-account/#tempurl only seems to mention sha1. I'd be interested in adding support for other, stronger digests (with an eye toward deprecating and eventually getting rid of sha1-based signatures), but I'd hate to come up with an incompatible API ""just because""."
1733634,2017-12-04 23:13:14 UTC,@Tim I'll try and get the Cloud Files docs updatesd I wrote a script to test the use of sha256 in Rackspace Cloud Files and it seemed to work ( https://github.com/inflatador/ptemper ).
1733634,2017-12-05 21:55:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/525770"
1733634,2018-02-01 03:51:14 UTC,"Reviewed:  https://review.openstack.org/525770
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=5a4d3bdfc49d61ee6e333c8eb1dad4383ae9308b
Submitter: Zuul
Branch:    master"
1733634,2018-02-06 10:29:59 UTC,"Related fix proposed to branch: feature/deep
Review: https://review.openstack.org/541233"
1733634,2018-02-07 03:48:20 UTC,"Reviewed:  https://review.openstack.org/541233
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=e473955900dde31dc170bf485e718fdf65955650
Submitter: Zuul
Branch:    feature/deep"
1733634,2018-02-27 09:24:15 UTC,"Related fix proposed to branch: feature/s3api
Review: https://review.openstack.org/548193"
1733634,2018-02-27 09:25:26 UTC,"Change abandoned by Kota Tsuyuzaki (<email address hidden>) on branch: feature/s3api
Review: https://review.openstack.org/548052
Reason: This is affected by the new s3api functests added in recent. Use https://review.openstack.org/#/c/548193/ instead."
1733634,2018-02-27 12:58:01 UTC,"Reviewed:  https://review.openstack.org/548193
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=9d43f4e190802cb0cad507a65245e4dd70fda7db
Submitter: Zuul
Branch:    feature/s3api"
1733642,2018-01-09 22:16:27 UTC,"Reviewed:  https://review.openstack.org/526468
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6522d383320f5fda27635ee1ea86ea381c3858a1
Submitter: Zuul
Branch:    stable/pike"
1733642,2017-12-10 20:07:54 UTC,"Reviewed:  https://review.openstack.org/521947
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cff8b088370c9190e402ece1a9ff48eae27677f7
Submitter: Zuul
Branch:    master"
1733642,2018-02-15 23:53:51 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1733642,2017-11-21 17:03:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521947"
1733642,2018-01-26 00:44:31 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1733642,2017-12-07 17:54:05 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/526468"
1733647,2017-12-28 21:25:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733647,2017-11-21 16:56:16 UTC,"StacktraceTop:
 mem_error (format=format@entry=0x7f1b3cbabb4d ""assertion failed: %s"") at ../../../../glib/gslice.c:1472
 slab_allocator_free_chunk (chunk_size=chunk_size@entry=32, mem=mem@entry=0x55fc2307b490) at ../../../../glib/gslice.c:1354
 magazine_cache_trim (allocator=0x7f1b3ce1dc20 <allocator>, stamp=<optimized out>, ix=<optimized out>) at ../../../../glib/gslice.c:679
 magazine_cache_push_magazine (ix=<optimized out>, magazine_chunks=<optimized out>, count=<optimized out>) at ../../../../glib/gslice.c:710
 thread_memory_magazine2_unload (tmem=<optimized out>, ix=<optimized out>) at ../../../../glib/gslice.c:809"
1733655,2017-11-22 14:55:06 UTC,There is also an upstream bug on that: https://github.com/JRaspass/Cache-Memcached-Fast/issues/12
1733661,2017-11-23 14:56:10 UTC,The referred documentation needs update.
1733662,2017-12-22 22:01:24 UTC,"That one ran our test script half a dozen times without failure, albeit with the ""Error -19"" messages in the dmesg output."
1733662,2018-01-04 17:33:27 UTC,"I hope you had a good holiday, Rod.  I started up the bisect again."
1733662,2018-01-04 19:18:06 UTC,"Thanks, Joseph. My break was good; I hope yours was, too!"
1733662,2018-01-04 20:07:13 UTC,The bisect should only require testing about 2 or 3 more kernels.
1733662,2018-01-04 20:39:50 UTC,"Joseph, that one also completed six runs with no problems except the ""error -19"" messages."
1733662,2018-01-04 22:18:46 UTC,"I built the next test kernel, up to the following commit:
e6108d5475696d0deaf37b59ff704aead9c5a8a7"
1733662,2018-01-05 14:34:41 UTC,"That one completed its first run, but then crashed when bringing CPU 14 back online, with the following dmesg output:"
1733662,2018-01-05 19:33:05 UTC,"I built the next test kernel, up to the following commit:
ac2fc5adab0f4b83f01214af61c8478c6ef186f9"
1733662,2018-01-05 22:40:39 UTC,"That one completed two runs, but on the second run, dmesg included the following message at one point:"
1733662,2018-01-08 16:09:32 UTC,"The bisect reported the following as the first bad commit:
commit ac2fc5adab0f4b83f01214af61c8478c6ef186f9
Author: Vikas Shivappa <email address hidden>
Date:   Tue Aug 15 18:00:43 2017 -0700
    x86/intel_rdt/cqm: Improve limbo list processing"
1733662,2018-01-08 17:03:13 UTC,"I'm afraid that one fails, too, on the second run when bringing CPU10 back online. Here's the dmesg output:"
1733662,2017-11-21 20:44:19 UTC,"I've discovered what may be the same bug on another system -- feebas, a Cisco UCS C220 M4 (Intel Series v3), with the same CPU type (Intel Xeon E5-2640 v3). I'm attaching dmesg output from it, but on this particular run, the computer did not hang indefinitely, although it did become unresponsive for a few seconds."
1733662,2018-01-08 18:37:14 UTC,"You're right. (I've got too many kernels installed on that system!) When I tested again, it got through eight runs without problems, beyond the ""error -19"" message. Here's the uname information, just to be sure:"
1733662,2018-01-10 15:44:57 UTC,Thanks for the update.  I'll ping the author of mainline commit 24247aeeabe99eab to get some feedback.
1733662,2018-01-10 17:17:56 UTC,"Yes, it still exists. To confirm the kernel version:"
1733662,2018-01-11 00:51:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733662,2018-01-12 16:22:44 UTC,"Hi Vikas,"
1733662,2018-01-14 11:35:45 UTC,"On Fri, 12 Jan 2018, Joseph Salisbury wrote:"
1733662,2018-01-15 20:56:55 UTC,"Hi Rod,"
1733662,2018-01-16 13:09:49 UTC,"Vikas, Fenghua can you please look at that ASAP?"
1733662,2018-01-16 16:27:00 UTC,"Joseph,"
1733662,2018-01-16 16:40:26 UTC,"On 01/16/2018 08:32 AM, Shankar, Ravi V wrote:

> Vikas on vacation until end of the month. Fenghua will look into this
> issue.
>
> On Jan 16, 2018, at 5:09 AM, Thomas Gleixner <<email address hidden>
> <mailto:<email address hidden>>> wrote:
>
>>
>> Vikas, Fenghua can you please look at that ASAP?
>>
>> On Sun, 14 Jan 2018, Thomas Gleixner wrote:
>>
>>> On Fri, 12 Jan 2018, Joseph Salisbury wrote:
>>>
>>>> Hi Vikas,
>>>>
>>>> A kernel bug report was opened against Ubuntu [0].  After a kernel
>>>> bisect, it was found that reverting the following commit resolved
>>>> this bug:
>>>>
>>>> commit 24247aeeabe99eab13b798ccccc2dec066dd6f07
>>>> Author: Vikas Shivappa <<email address hidden>
>>>> <mailto:<email address hidden>>>
>>>> Date:   Tue Aug 15 18:00:43 2017 -0700
>>>>
>>>>     x86/intel_rdt/cqm: Improve limbo list processing
>>>>
>>>>
>>>> The regression was introduced as of v4.14-r1 and still exists with
>>>> current mainline.  The trace with v4.15-rc7 is in comment #44[1].
>>>>
>>>> I was hoping to get your feedback, since you are the patch author.  Do
>>>> you think gathering any additional data will help diagnose this issue,
>>>> or would it be best to submit a revert request?
>>>
>>> That stinks like a use after free. Can you run with KASAN enabled?
>>>
>>> Thanks,
>>>
>>>    tglx
"
1733662,2017-12-22 20:31:38 UTC,"I built the next test kernel, up to the following commit:
646779c79c8ab1382f81d79d346937c51746b07e"
1733662,2018-01-08 18:10:20 UTC,The uname looks like you may still be running the kernel from comment #37.  The test kernel with the revert should have a name like:
1733662,2017-12-22 01:29:38 UTC,"That one hung much like the others, with the system responding only to very basic commands (mostly bash internals), although the dmesg output continued further after the kernel bug message. Here's the dmesg output:"
1733662,2017-12-21 21:02:30 UTC,"The build from http://kernel.ubuntu.com/~jsalisbury/lp1733662/ successfully completed about six runs of the test script, albeit with the verbose dmesg output that includes the ""EDAC sbridge: Failed to register device with error -19"" messages."
1733662,2017-11-21 20:48:58 UTC,"Here's the dmesg output from another run on feebas. In this case, the system has become unresponsive via SSH, although the console remains active."
1733662,2017-12-01 20:43:58 UTC,"I've tried upgrading to the latest development kernel, from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/, and re-testing. The details of the problem have changed (but they were never 100% consistent), but the problem definitely still exists. I'm attaching dmesg output from three runs:"
1733662,2017-12-01 22:06:17 UTC,"Here are some more test runs on boldore, using different kernels, mostly from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D. The attachment is a tarball containing dmesg output associated with runs of the cpu_offlining script. An overview:"
1733662,2017-12-19 14:25:51 UTC,"When you have a chance, could you also test the current mainline kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc4/"
1733662,2017-12-19 14:26:43 UTC,"I see you already tested 4.15-rc1, but it's worth while to also test -rc4."
1733662,2017-12-19 17:37:52 UTC,"Joseph, I've just tested 4.15-rc4, and the script crashed and the system became responsive to only the simplest commands when bringing CPU 9 back up, accompanied by this out of dmesg:"
1733662,2017-12-19 19:34:01 UTC,Thanks for testing mainline.  The stack trace looks the same as prior kernels.  We should perform a regular kernel bisect to identify the commit that introduced this regression.
1733662,2017-12-19 20:20:24 UTC,"The upstream 4.14.0 kernel DOES segfault, but none of the 4.13-series kernels does. Some of the 4.13-series kernels do have ""error -19"" or ""error -22"" messages in their dmesg output, though."
1733662,2017-12-19 21:18:18 UTC,Thanks for testing.  So we now know that 4.13.0-16 has the bug but 4.13.0-10 does not.
1733662,2017-12-20 00:16:04 UTC,4.13.0-14 failed when offlining CPU 9:
1733662,2017-12-21 22:27:07 UTC,"Thanks for testing.  I'll mark that kernel as good.  I think it's safe to ignore the ""error -19"" messages during the bisect.  We just need to tell the bisect whether the kernel exhibits the original bug or not."
1733662,2017-12-20 02:07:44 UTC,"Can you next try 4.13.0-12:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13498518"
1733662,2017-12-20 14:32:13 UTC,"There was no version 4.13.0-13, so I'll start a bisect between 4.13.0-12 and 4.13.0-14.  I'll build a test kernel and post it shortly."
1733662,2017-12-20 14:41:23 UTC,"Hmm, now that I looked at the commits between 4.13.0-12 and 4.13.0-14, bug 1734327 looks similar.  I built a test kernel already for that bug, and was wondering if you could test it."
1733662,2018-01-16 18:09:33 UTC,"On Tue, 16 Jan 2018, Joseph Salisbury wrote:

> On 01/16/2018 08:32 AM, Shankar, Ravi V wrote:
> > Vikas on vacation until end of the month. Fenghua will look into this
> > issue.
> >
> > On Jan 16, 2018, at 5:09 AM, Thomas Gleixner <<email address hidden>
> > <mailto:<email address hidden>>> wrote:
> >
> >>
> >> Vikas, Fenghua can you please look at that ASAP?
> >>
> >> On Sun, 14 Jan 2018, Thomas Gleixner wrote:
> >>
> >>> On Fri, 12 Jan 2018, Joseph Salisbury wrote:
> >>>
> >>>> Hi Vikas,
> >>>>
> >>>> A kernel bug report was opened against Ubuntu [0].  After a kernel
> >>>> bisect, it was found that reverting the following commit resolved
> >>>> this bug:
> >>>>
> >>>> commit 24247aeeabe99eab13b798ccccc2dec066dd6f07
> >>>> Author: Vikas Shivappa <<email address hidden>
> >>>> <mailto:<email address hidden>>>
> >>>> Date:   Tue Aug 15 18:00:43 2017 -0700
> >>>>
> >>>>     x86/intel_rdt/cqm: Improve limbo list processing
> >>>>
> >>>>
> >>>> The regression was introduced as of v4.14-r1 and still exists with
> >>>> current mainline.  The trace with v4.15-rc7 is in comment #44[1].
> >>>>
> >>>> I was hoping to get your feedback, since you are the patch author.  Do
> >>>> you think gathering any additional data will help diagnose this issue,
> >>>> or would it be best to submit a revert request?
> >>>
> >>> That stinks like a use after free. Can you run with KASAN enabled?
> >>>
> >>> Thanks,
> >>>
> >>>    tglx
>
>
> Here is some data wiht KASAN enabled:
> https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1733662/comments/51
>
> Are there any specific logs you would like to see, or specific actions
> executed?
"
1733662,2017-12-20 17:40:05 UTC,I started a kernel bisect between v4.13.0-12 and v4.13.0-14. The kernel bisect will require testing of about 7-10 test kernels.
1733662,2017-12-20 18:07:47 UTC,"There's nothing at the URL you posted, Joseph. Do I just need to give it more time to build, or is something wrong?"
1733662,2017-12-20 18:33:12 UTC,"Sorry, the packages should be there now.  You should only need the linux-image and linux-image-extra .deb files."
1733662,2017-12-21 04:02:41 UTC,"OK, I've run tests now. The system did not crash or otherwise misbehave, but the dmesg output was quite verbose, and included ""error -19"" messages. Here's a sample (apparently for just one CPU core; this sequence was repeated quite a few times):"
1733662,2017-12-21 15:24:41 UTC,"I built the next test kernel, up to the following commit:
8d9d2235a82ea41e65eff607005ea4f334e2e503"
1733662,2017-12-21 15:47:54 UTC,"That one completed one run of the test OK, but then crashed on the second one, when bringing CPU 15 back online, with the following dmesg output:"
1733662,2017-12-21 18:41:43 UTC,"I built the next test kernel, up to the following commit:
83d4a97746e5fac08e2a1498c3649586bab953a3"
1733662,2017-12-20 14:03:58 UTC,4.13.0-12 seems to be OK; I ran it seven or eight times without a failure.
1733662,2017-12-20 15:01:16 UTC,That one failed (the script stopped running after taking CPU 9 offline) with the following dmesg output:
1733662,2018-01-16 18:34:10 UTC,"> From: Thomas Gleixner [mailto:<email address hidden>]
> On Tue, 16 Jan 2018, Joseph Salisbury wrote:
> > On 01/16/2018 08:32 AM, Shankar, Ravi V wrote:
> > > Vikas on vacation until end of the month. Fenghua will look into
> > > this issue.
> > >
> > > On Jan 16, 2018, at 5:09 AM, Thomas Gleixner <<email address hidden>
> > > <mailto:<email address hidden>>> wrote:
> > >
> > >>
> > >> Vikas, Fenghua can you please look at that ASAP?
> > >>
> > >> On Sun, 14 Jan 2018, Thomas Gleixner wrote:
> > >>
> > >>> On Fri, 12 Jan 2018, Joseph Salisbury wrote:
> > >>>
> > >>>> Hi Vikas,
> > >>>>
> > >>>> A kernel bug report was opened against Ubuntu [0].  After a
> > >>>> kernel bisect, it was found that reverting the following commit
> > >>>> resolved this bug:
> > >>>>
> > >>>> commit 24247aeeabe99eab13b798ccccc2dec066dd6f07
> > >>>> Author: Vikas Shivappa <<email address hidden>
> > >>>> <mailto:<email address hidden>>>
> > >>>> Date:   Tue Aug 15 18:00:43 2017 -0700
> > >>>>
> > >>>>     x86/intel_rdt/cqm: Improve limbo list processing
> > >>>>
> > >>>>
> > >>>> The regression was introduced as of v4.14-r1 and still exists
> > >>>> with current mainline.  The trace with v4.15-rc7 is in comment #44[1].
> > >>>>
> > >>>> I was hoping to get your feedback, since you are the patch
> > >>>> author.  Do you think gathering any additional data will help
> > >>>> diagnose this issue, or would it be best to submit a revert request?
> > >>>
> > >>> That stinks like a use after free. Can you run with KASAN enabled?
> > >>>
> > >>> Thanks,
> > >>>
> > >>>    tglx
> >
> >
> > Here is some data wiht KASAN enabled:
> > https://bugs.launchpad.net/ubuntu/+source/linux-
> hwe/+bug/1733662/comme
> > nts/51
> >
> > Are there any specific logs you would like to see, or specific actions
> > executed?
>
> No, the KASAN output is pretty clear where the issue is.
>
> Thanks,
>
> 	tglx
"
1733662,2018-01-17 20:35:19 UTC,"On 01/16/2018 01:59 PM, Thomas Gleixner wrote:

> On Tue, 16 Jan 2018, Yu, Fenghua wrote:
>>> From: Thomas Gleixner [mailto:<email address hidden>]
>> Is this a Haswell specific issue?
>>
>> I run the following test forever without issue on Broadwell and 4.15.0-rc6 with rdt mounted:
>> for ((;;)) do
>>         for ((i=1;i<88;i++)) do
>>                 echo 0 >/sys/devices/system/cpu/cpu$i/online
>>         done
>>         echo ""online cpus:""
>>         grep processor /proc/cpuinfo |wc
>>         for ((i=1;i<88;i++)) do
>>                 echo 1 >/sys/devices/system/cpu/cpu$i/online
>>         done
>>         echo ""online cpus:""
>>         grep processor /proc/cpuinfo|wc
>> done
>>
>> I'm finding a Haswell to reproduce the issue.
> Come on. This is crystal clear from the KASAN trace. And the fix is simple enough.
>
> You simply do not run into it because on your machine
>
>     is_llc_occupancy_enabled() is false...
>
> Thanks,
>
> 	tglx
>
> 8<--------------------
>
> diff --git a/arch/x86/kernel/cpu/intel_rdt.c b/arch/x86/kernel/cpu/intel_rdt.c
> index 88dcf8479013..99442370de40 100644
> --- a/arch/x86/kernel/cpu/intel_rdt.c
> +++ b/arch/x86/kernel/cpu/intel_rdt.c
> @@ -525,10 +525,6 @@ static void domain_remove_cpu(int cpu, struct rdt_resource *r)
>  		 */
>  		if (static_branch_unlikely(&rdt_mon_enable_key))
>  			rmdir_mondata_subdir_allrdtgrp(r, d->id);
> -		kfree(d->ctrl_val);
> -		kfree(d->rmid_busy_llc);
> -		kfree(d->mbm_total);
> -		kfree(d->mbm_local);
>  		list_del(&d->list);
>  		if (is_mbm_enabled())
>  			cancel_delayed_work(&d->mbm_over);
> @@ -545,6 +541,10 @@ static void domain_remove_cpu(int cpu, struct rdt_resource *r)
>  			cancel_delayed_work(&d->cqm_limbo);
>  		}
>
> +		kfree(d->ctrl_val);
> +		kfree(d->rmid_busy_llc);
> +		kfree(d->mbm_total);
> +		kfree(d->mbm_local);
>  		kfree(d);
>  		return;
>  	}
"
1733662,2018-01-16 18:59:59 UTC,"On Tue, 16 Jan 2018, Yu, Fenghua wrote:

> > From: Thomas Gleixner [mailto:<email address hidden>]
> Is this a Haswell specific issue?
>
> I run the following test forever without issue on Broadwell and 4.15.0-rc6 with rdt mounted:
> for ((;;)) do
>         for ((i=1;i<88;i++)) do
>                 echo 0 >/sys/devices/system/cpu/cpu$i/online
>         done
>         echo ""online cpus:""
>         grep processor /proc/cpuinfo |wc
>         for ((i=1;i<88;i++)) do
>                 echo 1 >/sys/devices/system/cpu/cpu$i/online
>         done
>         echo ""online cpus:""
>         grep processor /proc/cpuinfo|wc
> done
>
> I'm finding a Haswell to reproduce the issue.
"
1733662,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1733662,2018-03-20 15:16:43 UTC,I've tested kernel 4.13.0-38-generic #43-Ubuntu from artful-proposed and the problem does not occur with that kernel.
1733662,2018-03-19 10:57:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1733662,2018-03-05 20:12:49 UTC,I have similar issues on 16.04.4 with latest HWE kernel - and when double-checking against the source code I can see that this fix is now AWOL from:
1733662,2018-01-18 18:40:03 UTC,"I ran it half a dozen times with your latest kernel and it seemed fine, aside from the usual ""error -19"" messages. To be sure it's the right one, here's the kernel version information:"
1733662,2018-01-19 14:47:49 UTC,SRU request submitted for Artful and Bionic.
1733662,2018-01-17 22:59:23 UTC,"On 01/17/2018 05:55 PM, Thomas Gleixner wrote:

> On Wed, 17 Jan 2018, Joseph Salisbury wrote:
>> On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
>>
>> Testing of your patch shows that your patch resolves the bug.  Thanks
>> for the assistance!  Is this something you could submit to mainline?
> Already there :)
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d47924417319e3b6a728c0b690f183e75bc2a702
>
> Tagged for stable.
>
> Thanks,
>
> 	tglx
"
1733662,2018-01-17 22:55:41 UTC,"On Wed, 17 Jan 2018, Joseph Salisbury wrote:

> On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
>
> Testing of your patch shows that your patch resolves the bug.  Thanks
> for the assistance!  Is this something you could submit to mainline?
"
1733662,2018-01-17 22:16:53 UTC,"On 01/16/2018 01:59 PM, Thomas Gleixner wrote:

> On Tue, 16 Jan 2018, Yu, Fenghua wrote:
>>> From: Thomas Gleixner [mailto:<email address hidden>]
>> Is this a Haswell specific issue?
>>
>> I run the following test forever without issue on Broadwell and 4.15.0-rc6 with rdt mounted:
>> for ((;;)) do
>>         for ((i=1;i<88;i++)) do
>>                 echo 0 >/sys/devices/system/cpu/cpu$i/online
>>         done
>>         echo ""online cpus:""
>>         grep processor /proc/cpuinfo |wc
>>         for ((i=1;i<88;i++)) do
>>                 echo 1 >/sys/devices/system/cpu/cpu$i/online
>>         done
>>         echo ""online cpus:""
>>         grep processor /proc/cpuinfo|wc
>> done
>>
>> I'm finding a Haswell to reproduce the issue.
> Come on. This is crystal clear from the KASAN trace. And the fix is simple enough.
>
> You simply do not run into it because on your machine
>
>     is_llc_occupancy_enabled() is false...
>
> Thanks,
>
> 	tglx
>
> 8<--------------------
>
> diff --git a/arch/x86/kernel/cpu/intel_rdt.c b/arch/x86/kernel/cpu/intel_rdt.c
> index 88dcf8479013..99442370de40 100644
> --- a/arch/x86/kernel/cpu/intel_rdt.c
> +++ b/arch/x86/kernel/cpu/intel_rdt.c
> @@ -525,10 +525,6 @@ static void domain_remove_cpu(int cpu, struct rdt_resource *r)
>  		 */
>  		if (static_branch_unlikely(&rdt_mon_enable_key))
>  			rmdir_mondata_subdir_allrdtgrp(r, d->id);
> -		kfree(d->ctrl_val);
> -		kfree(d->rmid_busy_llc);
> -		kfree(d->mbm_total);
> -		kfree(d->mbm_local);
>  		list_del(&d->list);
>  		if (is_mbm_enabled())
>  			cancel_delayed_work(&d->mbm_over);
> @@ -545,6 +541,10 @@ static void domain_remove_cpu(int cpu, struct rdt_resource *r)
>  			cancel_delayed_work(&d->cqm_limbo);
>  		}
>
> +		kfree(d->ctrl_val);
> +		kfree(d->rmid_busy_llc);
> +		kfree(d->mbm_total);
> +		kfree(d->mbm_local);
>  		kfree(d);
>  		return;
>  	}
"
1733662,2018-01-17 21:59:16 UTC,"That seems to have fixed it! I've run the test script six or seven times on both kernels, with nary a hiccup (aside from the ""error -19"" messages with the 4.13 kernel). Below is the reported kernel information from both your builds, just to be sure I booted the correct kernels."
1733662,2018-01-17 20:50:19 UTC,I built Artful and mainline test kernels with the patch from tglx.  The test kernels can be downloaded from:
1733662,2018-01-18 17:00:47 UTC,I built one last Artful test kernel with the patch tglx submitted to mainline. The test kernel can be downloaded from:
1733663,2017-11-21 18:19:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/521975"
1733663,2017-11-22 11:00:01 UTC,Hi Mateusz!
1733663,2018-03-27 07:43:05 UTC,"Change abandoned by Mateusz Kowalski (<email address hidden>) on branch: master
Review: https://review.openstack.org/521975"
1733665,2017-11-22 05:10:11 UTC,"The name ""Argenis"" in the URL rang a bell, and I foun dthat we had already looked at this, but at the time we marked it as won't fix. I am taking another look at the idea of preventing links coming from Karl to fail like this."
1733665,2017-11-22 05:11:16 UTC,"Hit ""post comment"" too soon. I wish these could be edited. Here's the link to the old ticket:"
1733666,2018-03-28 23:14:09 UTC,"Another way to do this is to make engine.makeConnection take no additional parameter and make it execute its callback as is, without binding it to any object."
1733666,2018-03-28 23:25:29 UTC,That is quite similar to what I was alluding to about above. I think adding nonstandard functions to the prototype of language builtins like Object will be odd for developers who know JS well. But we can accomplish essentially the same thing with Components by changing the line in Component.prototype.connect:
1733666,2018-04-19 12:56:06 UTC,"The 2018-06-30 date is too tight for me to finish this. Unless feature freeze for 2.2 is postponed a week, I have to unassign this from me."
1733666,2018-07-07 18:07:04 UTC,"ECMAScript 2017 support including arrow functions are targeted for Qt 5.12, which will be released in November 2018. So I anticipate distributions will be packaging it in spring 2019 (for Fedora, this would be Fedora 30). I propose we start working on migrating to QJSEngine now and try using Function.prototype.bind(this) in place of arrow functions. However, it may be a good idea to hold off releasing a new XML-less mapping system and rewriting Components for that until distributions are shipping Qt 5.12."
1733666,2018-04-19 18:22:43 UTC,Then I'm retaking it :)
1733666,2018-05-27 18:19:17 UTC,"This post has some background on why QtScript has been deprecated:
http://article.gmane.org/gmane.comp.lib.qt.devel/4224"
1733666,2018-05-27 19:44:10 UTC,Good news! Work is in progress to upgrade QJSEngine to support ECMAScript 2017: https://bugreports.qt.io/browse/QTBUG-47735?focusedCommentId=398077&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-398077
1733666,2018-04-19 13:11:18 UTC,This was already assigned to 2.3 anyway. I don't think there's any need to rush it for 2.2.
1733666,2018-03-28 19:41:59 UTC,"Developers would not need to rely on external Javascript functionality.
My proposal is for Mixxx to have native support for arrow functions.
But instead of implementing it in c++, we load a well known and popular JS library."
1733666,2018-03-28 23:10:17 UTC,Other idea:
1733666,2018-03-27 08:37:23 UTC,"Although, the difference is that quickly runs babel on node, and my plan is to run it on QJSEngine. So better stick with the original plan and only add the arrow function pluguin."
1733666,2018-03-27 14:21:13 UTC,"Yes, the current way of getting ""this"" for functions passed to engine.makeConnection is basically the same as arrow functions. However, I don't think it's a great idea to bring in external dependencies to hack around QJSEngine's limitations. I think that effort would be better spent contributing the desired functionality upstream to Qt. I recognize that is likely harder, but I think it would be more sustainable. I also don't think it's a good idea to recommend developers to rely on external JavaScript tooling to write mappings. We can mention that it's a possibility, but I am afraid that setting that up would be such a pain that it would deter people from contributing mappings."
1733666,2017-11-21 19:21:11 UTC,"It seems there isn't a way to get the current ""this"" object from a C++ function that is exposed to the JS environment, which will break engine.makeConnection and engine.beginTimer. However, QJSEngine supports ECMAScript 5, which introduced Function.prototype.bind. This will require some careful planning..."
1733666,2017-12-28 03:54:20 UTC,"I am assigning this to the 2.3 milestone for now, but I'm not sure we'll get to it by then. Let's reconsider when the 2.2 beta branch is cut."
1733666,2017-12-28 03:55:08 UTC,It may make sense to implement this concurrently with Ctlra support.
1733666,2018-01-30 20:52:01 UTC,"In the worst case, can we do something in C++ that works around the ""this"" object problems?"
1733666,2018-03-27 08:19:55 UTC,"I've just discovered this: https://github.com/quickly/quickly
And essentially what they do is use Babel to transform ES6 to ES5, so maybe we can ship a full babel build..."
1733666,2018-03-25 23:43:58 UTC,"By the way, are you actively working on this / have you made significant progress? I'd like to take it otherwise."
1733666,2018-03-26 00:00:35 UTC,"> We should not artificially bind to ""this"" in makeConnection and beginTimer.
"
1733666,2018-03-26 00:03:05 UTC,"Nice, I'm working on it meanwhile."
1733666,2018-03-27 07:54:55 UTC,"I think the solution is to add support for ES6 arrow functions. Users that are new to JS will just learn to use arrow functions in makeConnection and beginTimer because that's what we'll document in the wiki. On the other hand, seasoned JS developers will already know what a arrow function does, so they will know what's going on, because Mixxx will not bind ""this"" unexpectedly anymore."
1733666,2018-03-25 23:37:21 UTC,"> It seems there isn't a way to get the current ""this"" object from a C++ function that is exposed to the JS environment, which will break engine.makeConnection and engine.beginTimer.
"
1733671,2020-12-07 21:33:58 UTC,Closing as this is addressed in master (we no longer use Mistral).
1733683,2018-02-24 20:29:13 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for artful for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1733683,2017-11-24 21:57:42 UTC,"Hello Michael, or anyone else affected,"
1733683,2017-11-24 21:57:10 UTC,"Hello Michael, or anyone else affected,"
1733683,2017-11-24 21:56:06 UTC,"Hello Michael, or anyone else affected,"
1733683,2017-11-21 19:48:53 UTC,Debdiff for artful
1733683,2017-11-21 19:45:42 UTC,Debdiff for zesty
1733683,2017-11-21 19:41:05 UTC,This is the debdiff for xenial.
1733683,2017-11-21 20:23:28 UTC,"The attachment ""ust_2.7.1-1ubuntu0.1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1733690,2018-01-02 17:44:51 UTC,"Hi,"
1733690,2017-11-28 14:08:11 UTC,CVE-2017-12130 is assigned to this issue
1733690,2018-04-13 13:13:18 UTC,This issue was made public on 1/16/18.
1733690,2018-04-13 12:18:22 UTC,Can I make this bug public?
1733690,2017-11-27 23:32:03 UTC,Thanks for reporting this issue. Has a CVE been assigned?
1733690,2018-01-02 16:38:44 UTC,Are there any updates for this issue?
1733690,2018-01-02 19:16:21 UTC,"Thanks for the response. It is reported to the author as well.  If no interest in this bug, feel free to close."
1733690,2017-11-28 16:53:32 UTC,This issue is a separate/new issue and is not related to Bug#1729668
1733694,2017-11-22 00:23:09 UTC,"The attachment ""apt-avahi-discover_timeout-fix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1733694,2020-04-25 23:40:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733701,2018-04-04 19:54:46 UTC,We'd also really like to see the ability to downgrading or rolling back upgrades.
1733702,2017-11-29 14:44:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733707,2018-06-02 04:35:48 UTC,[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.]
1733707,2018-04-03 02:49:15 UTC,I thought MATE fixes landed in December/January.
1733707,2017-12-21 12:23:29 UTC,"The attachment ""mate-support.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1733707,2017-11-25 22:59:32 UTC,Check the files I patched and added to Ambiance from Ambiant-MATE. mate-panel styling is included in mate-applications.css as far as I can tell.
1733707,2017-11-26 16:20:57 UTC,Turns out I was over complicating things and didn't realize that Ambiance and Ambiant-MATE diverged a lot when they were altered to support GTK 3.20. Here's what should be done to fix this bug in both Ambiance and Radiance in MATE:
1733707,2017-11-25 21:07:59 UTC,"I had a bit of time today to play around with this in 18.04, and looks like Ambiant-mate and Ambience issues are complementary and it's possible to fix compatibility with Unity7 and MATE, respectively, using code from each-other."
1733707,2017-11-30 20:28:47 UTC,I tried to make patches for both Ambiance and Radiance.
1733707,2017-11-25 22:25:58 UTC,"@biohazara Go to Ambiance/gtk-3.0/apps folder, and open gnome-panel.css. See how it is styled? We need specific styling for mate-panel too."
1733711,2017-12-22 08:13:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733711,2017-12-22 08:15:33 UTC,"Also tracking in:
https://bugzilla.gnome.org/show_bug.cgi?id=787260"
1733715,2021-02-12 21:15:04 UTC,It would be very helpful to have the owner of the folder listed in the drop down menu for folders.
1733718,2018-01-30 12:43:45 UTC,"Err, I meant bug 1745579 as the dupe"
1733718,2018-02-26 21:05:46 UTC,The fix for this is in xenial-proposed awaiting final SRU testing.
1733718,2018-01-30 12:43:11 UTC,"Confirming Ubuntu bug, based on dupe #1733718."
1733718,2017-11-21 23:47:07 UTC,"This seems to be affecting heroku too:
https://build.snapcraft.io/user/heroku/cli/109249"
1733718,2017-11-22 14:36:14 UTC,"yarn apparently doesn't pick up proxy configuration from the environment, and needs to be told explicitly.  I've filed a snapcraft PR to fix this (https://github.com/snapcore/snapcraft/pull/1754)."
1733727,2019-03-08 09:37:32 UTC,I can confirm that in 18.04 and Wayland this works as expected and only the frame flashes.
1733727,2018-08-08 08:26:04 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1733738,2019-04-29 14:36:09 UTC,Yingzhe is there any progress with this issues ?
1733738,2019-07-23 17:08:02 UTC,Hi Yingzhe is there any progress with this issues ?
1733738,2019-09-27 19:42:08 UTC,Bumping down the bug importance to wishlist - while this isn't part of the project's priorities at the moment; we will encourage a fix.
1733746,2017-12-07 23:56:00 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1733746,2017-12-18 12:51:30 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1733746,2017-12-01 01:43:02 UTC,"Reviewed:  https://review.openstack.org/522100
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=036a692565ef0f1c730f28ea083465fad9dc3b13
Submitter: Zuul
Branch:    master"
1733746,2017-11-22 03:31:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522100"
1733746,2017-12-01 17:45:45 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/524687"
1733746,2017-12-09 03:24:02 UTC,"Reviewed:  https://review.openstack.org/524687
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=781a963c58a7bb84077de7c3056d148afae0d303
Submitter: Zuul
Branch:    stable/pike"
1733766,2020-10-04 11:41:18 UTC,"NWChem 7.0.0 is available in Ubuntu 20.04 LTS, does that fix your issues?"
1733782,2017-12-28 09:37:22 UTC,Please find part of requested output during delay below.  It is not all the output as this is very long.  So I abbreviated by putting a (...) between beginning and end during delay.
1733782,2017-11-27 16:48:25 UTC,"Does it still show 1x1 image note in place of screenshot? I'm pretty sure this problem was fixed in 2.11, please build that version from source if possible."
1733782,2017-12-06 07:06:44 UTC,Yes it does.
1733782,2017-12-08 22:36:16 UTC,"1. Open Software & Updates and enable ""Source code""
2. Run in terminal:
sudo apt-get build-dep basket"
1733782,2017-12-09 11:03:42 UTC,Thank you for your help. Following instructions you posted installation now completes successfully.
1733782,2017-12-13 16:28:48 UTC,"Can you run the following command and see what is the output during the delay?
strace basket |& tee ~/basket_strace.log
(you might need to change ptrace_scope if it fails with Operation not permitted)"
1733782,2017-12-14 16:07:48 UTC,Sure ! Here it is:
1733782,2017-12-18 21:46:59 UTC,"This might happen because of some problem with KUniqueApplication and QDBus. Please run this command and then start Basket in parallel:
dbus-monitor |& tee ~/basket_dbus.log"
1733783,2019-11-15 00:35:11 UTC,"Reviewed:  https://review.opendev.org/502391
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=9d2df833d277331c2466e282a375f40068619216
Submitter: Zuul
Branch:    master"
1733783,2017-11-23 04:10:10 UTC,Thanks for report bug. :)
1733783,2017-11-23 07:38:25 UTC,"@zhaobo (zhaobo6)，thanks for your advice.
I have post a patch already(https://review.openstack.org/#/c/502391/),could you help me to review it if possible ? 3Q.
By the way,i have grep the neutron directory,can't find anymore to fix,if you see anyone else,please point to me,many thanks."
1733788,2018-03-01 11:03:20 UTC,"We need to complete pre_condition and post_condition and we need to move our checking logic
from helper level to action level. It should be done for all action types."
1733793,2017-11-22 14:36:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1733793,2017-11-23 10:16:13 UTC,Thanks for your immediate response. I'll try to report it on the upstream GNOME bugtracker as soon as possible.
1733793,2018-02-06 16:27:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733793,2019-06-05 07:35:51 UTC,Is that still an issue? Did you ever report it upstream?
1733793,2020-07-01 21:12:56 UTC,"no response, closing"
1733806,2017-11-29 10:02:55 UTC,"Hi Jeffery, Thanks for reminding
I will port this fix to kolla-kubernetes to verify"
1733806,2017-11-28 04:48:00 UTC,Some debug.
1733806,2017-11-28 13:49:53 UTC,This is fixed by https://review.openstack.org/#/c/492552/ in kolla-ansible.
1733806,2017-11-27 07:44:55 UTC,https://review.openstack.org/#/c/522738/
1733806,2017-11-22 20:22:15 UTC,"I also see this in stable/pike, running kolla-kubernetes."
1733806,2017-11-22 09:37:28 UTC,If not apply the patch in the above:
1733806,2017-11-27 14:42:29 UTC,Looks like libvirt TLS is enabled (listen_tls=1 in libvirtd.conf) but certificates have not been setup.
1733806,2017-11-28 09:45:14 UTC,"Doh, I was looking at the test env in comment #4."
1733827,2019-03-05 13:44:19 UTC,Is this still an issue?
1733827,2019-12-18 08:43:36 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1733829,2017-11-23 02:09:12 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1733829,2017-11-23 02:10:28 UTC,"Hello Sushil, your root filesystem is full, or very nearly full:"
1733834,2017-11-23 04:34:17 UTC,"Patch from https://lists.amavis.org/pipermail/amavis-users/2017-September/005074.html
solved part of problems- now it works for archives with latin files in it,
but still problems with cyrillic (utf8) names- messages passes UNCHECKED..."
1733834,2017-11-23 10:31:13 UTC,https://lists.amavis.org/pipermail/amavis-users/2017-November/005132.html
1733834,2017-11-24 10:32:42 UTC,"Hi sles,
Thank you for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue."
1733836,2017-11-30 19:43:32 UTC,"A change like that really should be tackled at the lowest level, and not ad-hoc by each of the consumers.  If openldap client libraries support it, the python libraries should as well. But that is an argument for the python-ldap team.  I'm not against enabling this for Keystone if you want to go ahead an write the code."
1733836,2017-11-28 20:45:48 UTC,This certainly sounds like it would be useful. I'd be curious to see what operators or users bite on this. Do you know who that would be?
1733836,2017-11-28 21:08:59 UTC,"> Do you know who that would be?
"
1733843,2017-12-07 05:15:13 UTC,fix in https://review.openstack.org/#/c/525187/16
1733843,2018-01-11 15:16:31 UTC,This issue was fixed in the openstack/openstackdocstheme 1.18.0 release.
1733850,2017-11-23 01:28:56 UTC,"Stopping supervisor-vrouter on nodei2 and nodei3 causes system-defined-node-status alarm.
But same doesn’t show up for nodei1. This was reproducible on the setup.
This is not a caching issue since the alarm doesn’t show up even after multiple stop/start of supervisor-vrouter on nodei1.
I restarted alarmgen on this node to set higher logging level but issue is not seen now."
1733850,2017-11-24 10:40:23 UTC,"removing sanityblocker as the problem was not seen on build4 of R4.1, will provide the setup in the failed state if it's reproducible again."
1733853,2018-01-05 06:58:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733853,2018-04-03 02:33:33 UTC,when the issue will be totally fixed ......
1733853,2018-04-03 02:54:11 UTC,Is this issue present on the Bionic Beaver?
1733861,2018-01-19 16:34:17 UTC,This may be related to https://bugs.launchpad.net/ironic/+bug/1743652
1733861,2018-01-24 19:38:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/537626"
1733861,2018-12-13 18:14:16 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/537626
Reason: I'm inclined to abandon this one. As various people have pointed out, it's a bit of a hack and should no longer be required. If we see cases where it would be useful, then there is probably a bug somewhere that needs addressing."
1733867,2019-05-28 04:17:41 UTC,[Expired for kolla because there has been no activity for 60 days.]
1733867,2017-11-23 06:06:08 UTC,"/etc/kolla/config/cinder-volume.conf is as follows:
[DEFAULT]
enabled_backends=rbd-1"
1733867,2017-11-23 05:55:43 UTC,"changed ceph.client.ceph.keyring to
ceph auth get-or-create client.cinder mon 'allow r' osd 'allow class-read object_prefix rbd_children, allow rwx pool=volumes,allow rwx pool=vms, allow rwx pool=images ,allow rwx pool=rbd ' >ceph.client.cinder.keyring
there is no error log in cinder_volume but still in nova_compute"
1733867,2019-03-28 10:46:41 UTC,Is this still a bug in recent releases? If yes - please update.
1733869,2017-11-22 14:09:15 UTC,Collecting some pointers I've recieved how to do this here:
1733869,2017-11-22 17:16:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522302"
1733869,2017-12-07 12:41:40 UTC,Other related patch https://review.openstack.org/522300
1733869,2018-03-08 09:21:23 UTC,"Change abandoned by Dougal Matthews (<email address hidden>) on branch: master
Review: https://review.openstack.org/522302"
1733869,2018-03-08 09:21:28 UTC,"Change abandoned by Dougal Matthews (<email address hidden>) on branch: master
Review: https://review.openstack.org/522300"
1733879,2018-04-06 09:04:33 UTC,The documentation here isn't clear. The custom action needs to be reinstalled each time it is changed. The Mistral executors then need to be restarted (which isn't ideal).
1733880,2017-11-29 12:02:54 UTC,FWIW the murano charm lacks any active development community at the moment.
1733881,2017-11-28 07:21:58 UTC,due to the nature of ubuntu-core we can not directly point to a zone file
1733881,2017-11-28 06:51:48 UTC,"I'm not sure which part of your response showed that I was ""wrong"".  Does /etc/localtime point to a zoneinfo file?  What is the content of /etc/writable/localtime?"
1733881,2017-11-27 16:26:38 UTC,"@adconrad you are wrong,
If i set my timezone via timedatectl to Europe/Berlin, I get:"
1733881,2017-11-22 15:49:56 UTC,"Oh, no, this probably isn't a systemd bug at all, this is probably due to you not having an /etc/localtime AT ALL.  Which timedatectl won't be happy about, and will list as ""n/a"".  Because you've literally not set a timezone."
1733881,2017-11-22 15:37:28 UTC,"This looks like it's probably a bug in xenial's systemd?  Not sure why anyone cares deeply about the output of ""timedatectl"", but on bionic, I get:"
1733881,2017-11-22 15:04:41 UTC,There are two issues here IMHO ...
1733884,2018-06-07 20:27:46 UTC,This issue was fixed in the openstack/neutron-lbaas 13.0.0.0b2 development milestone.
1733886,2018-01-26 00:44:21 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1733886,2018-01-10 01:12:30 UTC,This issue was fixed in the openstack/nova 14.1.0 release.
1733886,2018-01-03 14:37:40 UTC,This issue was fixed in the openstack/nova 15.1.0 release.
1733886,2017-12-19 21:07:20 UTC,"Reviewed:  https://review.openstack.org/527421
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e6498e6ef13e214b74b76fa57cb3bcb6919c2cf8
Submitter: Zuul
Branch:    master"
1733886,2017-12-18 12:51:20 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1733886,2017-12-15 16:10:56 UTC,"Reviewed:  https://review.openstack.org/526427
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9de9faa0f6080e0e01e676330eff293c3d15ffb2
Submitter: Zuul
Branch:    stable/newton"
1733886,2017-12-14 22:27:00 UTC,"Reviewed:  https://review.openstack.org/526426
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=901377b22bb92747748b25058e31d1099904c8cc
Submitter: Zuul
Branch:    stable/ocata"
1733886,2017-12-12 15:09:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/527421"
1733886,2017-12-12 00:00:03 UTC,"Reviewed:  https://review.openstack.org/526419
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6f5b3123cc3e35af7d9054c299f4c2232c8c2a3f
Submitter: Zuul
Branch:    stable/pike"
1733886,2017-12-08 19:27:32 UTC,"Reviewed:  https://review.openstack.org/523194
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9ddbaa15cb55d1245a8a63d9414d134746fc2f3c
Submitter: Zuul
Branch:    master"
1733886,2017-12-07 15:09:28 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/526427"
1733886,2017-12-07 15:04:38 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/526426"
1733886,2017-12-07 14:47:13 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/526419"
1733886,2017-11-27 19:00:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523194"
1733886,2017-11-22 15:54:58 UTC,https://blueprints.launchpad.net/nova/+spec/fix-os-quota-sets-force
1733886,2017-11-22 15:42:06 UTC,"I guess force means to update quota regardless of usage, so if I have 10 instances and the admin changes quota to 5, they have to force that. The 'reserved' piece would always be 0 starting in Pike, but otherwise the usage part still applies, so we should probably fix this in the 2.56 microversion with the ""deprecate-file-injection"" blueprint."
1733886,2017-11-22 15:01:33 UTC,"Note that 2.36 went into Newton so it does break the 'force' parameter before we made the change for counting quotas in Pike, so effectively newton and ocata are broken for this, and if we were going to fix it with a new microversion, we wouldn't be able to fix it in stable branches anyway since we can't backport a microversion."
1733889,2020-08-10 12:23:02 UTC,"Alright,"
1733889,2020-08-10 07:42:43 UTC,I reinstalled all test-vms and now it works...
1733889,2020-08-09 16:17:06 UTC,I cannot reproduce this in Focal.. and the bug description shows:
1733889,2020-08-09 15:38:31 UTC,"Hello Christoph,"
1733889,2020-08-09 13:31:41 UTC,"Sorry to ask so early, but I really need this. Do you found something?"
1733889,2020-08-07 12:04:24 UTC,"Thanks for the feedback Christoph,"
1733889,2020-08-07 11:27:36 UTC,Problem still exists for me with corosync-qdevice 3.0.0-4ubuntu1 on ubuntu 20.04:
1733889,2019-07-04 03:48:41 UTC,I'm flagging this as ubuntu-ha so I can investigate this together with the Ubuntu HA work being done. Assigned case to myself.
1733889,2018-06-26 14:10:00 UTC,Note: This needs more time or more corosync experience for a RCA.
1733890,2020-05-19 21:34:51 UTC,On Ubuntu 20.04 I had the same issue if I'm copying to clipboard an area only (Select area to Grab option).
1733890,2020-05-19 21:39:43 UTC,"Forgot to mention: I'm using X11.
Also, I've found that that option works fine if Include pointer option is checked."
1733890,2018-11-23 00:03:06 UTC,"+1 to Roland's issue. Screenshot's are not pasting as expected. I had a clipboard indicator extension for Gnome enabled. Thinking that this might have some impact I disabled it, yet pasting images from the clipboard does not work. Going to try and debug this one further."
1733890,2018-09-12 22:21:32 UTC,"I can also confirm that I am now having this same issue over the last week, as Roland above mentioned."
1733890,2018-08-30 06:51:25 UTC,"I have the exact same problem. It was working before, but some recent update must have broken something.  Running Xorg, not wayland on 18.04.  Screenshot goes through the motions, but nothing ends up in the clipboard buffer to paste."
1733890,2018-02-21 20:01:35 UTC,I can confirm that logging into Ubuntu using Xorg solves the issue for me.
1733890,2018-11-28 18:52:47 UTC,"Same as Roland except I can paste into Gmail's Compose Email, but not into GIMP or Libreoffice."
1733890,2018-02-21 13:19:09 UTC,"There is indeed a difference between xorg and wayland. If I login using an
xorg session it works."
1733890,2017-11-22 16:41:53 UTC,Sometimes it copies to clipboard but the resulting pasted screenshot is broken.
1733890,2018-01-22 22:19:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733890,2018-02-21 13:39:13 UTC,Probably a Wayland issue then and related to:
1733890,2020-01-29 12:52:32 UTC,"On Ubuntu 20.04, if you use the command line option, it does not copy, but it does copy if you use the GUI."
1733890,2018-02-21 12:40:53 UTC,I just registered to confirm that I've hit this bug as well on a fully patched Ubuntu 17.10 system. When you save the screenshot to disk the problem does not occur.
1733890,2018-02-21 13:03:05 UTC,"Maybe the issue is actually related to Wayland? Do you notice a difference
between Xorg and Wayland session?"
1733890,2018-02-21 12:53:09 UTC,I believe this problem is not caused by the Gnome screenshot program. When open an image in image viewer and copy the image to clipboard and paste the image to gimp from the clipboard buffer I get the same broken image with the grey area. This problem might be situated in the program that handles the clipboard in Gnome or whatever handles copying to or pasting from the clipboard.
1733909,2017-11-22 18:56:41 UTC,Please submit a merge request on https://gitlab.common-lisp.net/asdf/asdf/merge_requests
1733909,2018-08-17 17:06:44 UTC,Those lines don't exist in image.lisp anymore. Is this bug still relevant?
1733915,2017-11-23 07:20:40 UTC,"The current idea of the tests is that they should be runned in the Obj/Tests directory. Since this allows one to test different compiled executables.
Could you try in the Obj/Tests directory, at least I can't reproduce this?"
1733915,2017-11-23 09:38:59 UTC,"I'm running tests from Obj/, or whatever I object directory I use. Could it be related to my renaming it to something else?"
1733915,2017-12-04 09:21:12 UTC,Sorry for my late reply.
1733915,2017-12-04 09:22:00 UTC,"Ah, sorry, you already wrote that... Hmm. I can't see how/where it goes wrong..."
1733916,2017-11-23 06:22:23 UTC,"It appears that ""ldconfig"" is the program that crashes during the run of the post-installation script. I tried running ""ldconfig"" and ""ldconfig.real"" manually, and they crash too. Unfortunately, I do not have the time to debug this for you."
1733916,2020-05-09 10:43:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733916,2017-11-22 17:24:32 UTC,"Please note that the hardware errors reported for /dev/sdd in Dmesg.txt are related to USB communication problems with one of two external hard drives, which are probably irrelevant (despite these errors, the hard drive does work -- it does not contain any files related to the reported bug)."
1733916,2017-11-23 06:37:26 UTC,"A downgrade to an earlier version of the package fixes the problem, so it indeed seems to be a problem in the new package."
1733918,2017-11-23 07:27:27 UTC,"Example 1.
When running make in the TDDFT_Ge sub-directory it will run _1 first, then _2. This should be controlled by the test_tddft.mk file. However, I agree it could be updated for clarity."
1733918,2017-11-23 09:29:08 UTC,Thanks. Clarity is definitely what is needed. A few simple recommendations on how to design test cases would likely be enough.
1733918,2017-12-04 09:13:26 UTC,"Example 2 has just been fixed in 4.1, this will propagate to trunk (will let you know). Once merged you can pull into your branch."
1733918,2017-12-05 14:09:34 UTC,Feel free to merge with trunk now.
1733921,2017-11-22 23:55:04 UTC,*** This is an automated message ***
1733930,2017-11-23 19:12:03 UTC,Thank you for your great work!
1733930,2017-11-23 19:39:04 UTC,"Thanks.
Remember there is a cross-probing between Cvpcb and Eeschema: when you click on a component, the Eeschema cursor is put on this component in schematic.
Although it is not exactly what you want, it helps."
1733930,2017-11-22 19:41:03 UTC,"There already is a viewer, you just have to open it by clicking on the
toolbar button that looks like a footprint with a magnifying glass.  The
viewer is in a separate window which displays the footprint any time you
click on an entry in the footprint pane.  If you are asking for a
separate pain in the view, then that is a different issue."
1733930,2017-11-22 21:23:16 UTC,I mean additional to the footprint viewer a symbol viewer to compare the pin asignement.
1733930,2017-11-22 21:34:25 UTC,"I read this wrong.  There is no symbol viewer.  I'm sure we could add
one if someone finds the time to implement it."
1733934,2018-01-24 22:43:13 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1461
1733937,2019-12-13 14:40:02 UTC,"> It does not indicate that trash fields should be stripped performing a simple record edit.
"
1733937,2019-09-11 18:26:04 UTC,I am not seeing this behavior in 3.2. What I see is:
1733944,2017-11-27 13:42:25 UTC,"I was thinking on the status screen. Seems to be the one place everyone
looks. I am open to suggestions too."
1733944,2017-11-24 01:07:57 UTC,This is a very interesting thought.
1733944,2017-11-27 13:57:23 UTC,"We've had some discussions in the past about something like ""juju alerts""
which would be a place to put issues with your controller that don't fit
about a model. (Example, something wrong with one of the workers inside the
controller.) I think the discussions around it would be to point you to
alerts if there were any pending. But we haven't really fleshed that out
yet."
1733944,2017-11-28 14:55:57 UTC,"So, problem is that MTU on physical machine was not matched with an MTU on LXD. Juju has view of both of these, the physical machine's MTU and MTU for LXD. In fact, it configures LXD itself."
1733944,2018-01-02 18:05:16 UTC,See https://bugs.launchpad.net/maas/+bug/1733945 for the MAAS counterpart.
1733944,2018-01-10 03:12:01 UTC,It looks like the best way is to follow suggestion in comment # 4 and exit as soon as possible.
1733945,2017-12-01 20:34:45 UTC,"Hi Chris,"
1733945,2018-01-02 18:03:34 UTC,"@jason
Can you answer these for Andres"
1733945,2018-01-03 15:39:10 UTC,"It means ""the MAAS VLAN config one MTU value, but the configured interface in MAAS had a different MTU value"""
1733945,2019-09-19 14:53:29 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1733945,2019-09-20 11:44:58 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1733968,2017-12-05 11:38:54 UTC,"@Felipe Reyes,"
1733968,2017-12-05 13:07:29 UTC,"On Tue, Dec 05, 2017 at 11:38:54AM -0000, Anastasia wrote:

> Could you please clarify Juju version?
"
1733968,2017-12-05 13:21:14 UTC,"Thank you, @freyes \o/
I'll mark it as Won't Fix for juju-core and will keep it on juju."
1733968,2017-12-12 11:27:03 UTC,I believe you should be able to set --config ignore-machine-addresses=true
1733968,2018-01-11 23:39:50 UTC,We just had this affect a percona-cluster environment when the VIP for the cluster was assigned to two hosts at once due to a failure in percona clustering.  See also lp:1742811.
1733968,2018-01-13 00:13:36 UTC,"John,"
1733968,2018-01-15 18:36:58 UTC,"Felipe, thanks!"
1733968,2018-02-13 21:25:29 UTC,"During a discussion with Mario and Billy, we think we came up with what sounds like a good solution."
1733968,2020-04-12 23:18:10 UTC,"I tested juju from edge  (2.8-beta1+develop-59bbda0) with the intention to determine if maybe this issue was no longer present, but no luck, it's still there."
1733968,2020-07-30 15:01:04 UTC,https://github.com/juju/juju/pull/11853
1733968,2020-05-06 14:15:00 UTC,"This requires some significant work still, as it involves adding features that Juju doesn't currently have."
1733968,2018-01-15 18:12:52 UTC,"On Sat, Jan 13, 2018 at 12:13:36AM -0000, Dmitrii Shcherbakov wrote:

> John,
>
> There are ""secondaries"" so for VIPs there is a way to filter:
>
> 1. Linux kernel has a concept of a ""secondary"" address. If you do `ip
> route add x.x.x.x/y dev z` it loops through all addresses on an
> interface and will check if there's already an address with the same
> prefix that you are trying to add. If there is, it will mark the newly
> address as a secondary.
>
> inet_insert_ifa which contains primary/secondary flagging code (IPv4, not sure about IPv6, probably similar)
> https://elixir.free-electrons.com/linux/latest/source/net/ipv4/devinet.c#L440
>
> the flag itself
> https://elixir.free-electrons.com/linux/latest/source/include/uapi/linux/if_addr.h#L42
> #define IFA_F_SECONDARY		0x01
>
> 2. iproute2 is aware of secondaries when you do `ip addr show`
> https://git.launchpad.net/~usd-import-team/ubuntu/+source/iproute2/tree/ip/ipaddress.c?h=applied/ubuntu/xenial-updates#n1068
>
>
> 3. there's a sysctl to nuke secondaries on removal of a primary - seems to be set to 0 by default which means ""to nuke"".
>
> http://elixir.free-electrons.com/linux/v4.14.13/source/Documentation/networking/ip-sysctl.txt#L1266
> ""promote_secondaries - BOOLEAN when a primary IP address is removed from this interface promote a corresponding secondary IP address instead of removing all the corresponding secondary IP addresses.""
>
> Nuking secondaries works like this:
> https://elixir.free-electrons.com/linux/v4.14.13/source/net/ipv4/devinet.c#L326
>
>
> 3. heartbeat/IPaddr2 uses `ip addr add ...` and for our VIP use-cases it adds an address on a primary address' subnet => a secondary will be created.
> https://github.com/ClusterLabs/resource-agents/blob/v4.1.0/heartbeat/ocf-binaries.in#L29
> https://github.com/ClusterLabs/resource-agents/blob/v4.1.0/heartbeat/IPaddr2#L600
>
> And notes promote_secondaries:
> https://github.com/ClusterLabs/resource-agents/blob/v4.1.0/heartbeat/IPaddr2#L149-L156
> ""There must be at least one static IP address, which is not managed by the cluster, assigned to the network interface. If you can not assign any static IP address on the interface, modify this kernel parameter: sysctl -w net.ipv4.conf.all.promote_secondaries=1 # (or per device)""
>
"
1733976,2018-05-10 08:56:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733980,2017-11-23 21:58:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1733980,2017-11-24 00:05:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733983,2017-12-07 09:15:13 UTC,python-os-testr-0.8.2-0.20170811225902.e84d062.el7.centos.noarch and python-testrepository-0.0.18-2.el7.noarch version used https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset020-pike/f33faa6/rpm-qa.txt.gz grepped from here
1733983,2017-11-27 21:13:21 UTC,I've added os-testr for their visibility. I'm dropping this to a medium since it doesn't appear to fail anything.
1733983,2017-11-27 21:36:05 UTC,I haven't seen that warning message in a very long time. That is a feature in subunit-trace to warn about a bug we used to see quite frequently in testr: http://git.openstack.org/cgit/openstack/os-testr/tree/os_testr/subunit_trace.py#n303
1733984,2020-09-14 09:01:45 UTC,This look a bit suspicious to me:
1733984,2020-09-14 08:43:44 UTC,https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline_func_smoke/openstack/charm-octavia/751663/1/19123/consoleText.charm_build_35586.txt
1733984,2019-08-22 06:44:27 UTC,"I often see random build failures, and your observation about this being more likely to happen during concurrent builds seems plausible.  It was certainly the case for these failures as they occurred just after posting a change to rebuild all the reactive charms."
1733984,2017-11-22 22:53:52 UTC,"Once confirmed, please also add other charms to the bug tasks."
1733984,2017-11-23 02:10:09 UTC,"I am not able to replicate this: manual build and tox -e build both work. I've retriggered the build job in the CI system, and it passed successfully."
1733984,2017-11-23 07:08:10 UTC,"Further investigation reveals that these will rebuild individually, but not simultaneously, indicating an infrastructure issue."
1733991,2017-11-23 00:01:03 UTC,apport information
1733991,2017-11-23 00:01:19 UTC,apport information
1733991,2017-11-23 06:34:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1733991,2017-11-23 06:37:50 UTC,Don't use CTRL. Use only super + w. It has probably something to do with key release rather than key press. So anything with ctrl or shift is not working properly. Ubuntu recently removed that patch from latest xorg which just landed in 16.04 through xenial. See LP: #1683383
1733991,2017-11-23 09:58:23 UTC,"Confirmed indeed, Marco do you think you could have a look to see if that's a compiz/unity issue and it would be easy to resolve?"
1733991,2017-11-23 00:01:05 UTC,apport information
1733991,2017-11-23 00:01:07 UTC,apport information
1733991,2017-11-23 00:01:09 UTC,apport information
1733991,2017-11-23 00:01:11 UTC,apport information
1733991,2017-11-23 00:01:34 UTC,apport information
1733991,2017-11-23 00:01:33 UTC,apport information
1733991,2017-11-23 00:01:32 UTC,apport information
1733991,2017-11-23 00:01:30 UTC,apport information
1733991,2017-11-23 00:01:29 UTC,apport information
1733991,2017-11-23 00:01:27 UTC,apport information
1733991,2017-11-23 00:01:26 UTC,apport information
1733991,2017-11-23 00:01:25 UTC,apport information
1733991,2017-11-23 00:01:23 UTC,apport information
1733991,2017-11-23 00:01:22 UTC,apport information
1733991,2017-11-23 00:01:20 UTC,apport information
1733991,2017-11-23 00:01:38 UTC,apport information
1733991,2017-11-23 00:01:17 UTC,apport information
1733991,2017-11-23 00:01:16 UTC,apport information
1733991,2017-11-23 00:01:15 UTC,apport information
1733991,2017-11-23 00:01:14 UTC,apport information
1733991,2017-11-23 00:01:12 UTC,apport information
1733991,2017-11-28 03:54:26 UTC,"Khurshid, to be clear, the CTRL and the W were the intentional keys, the Windows (aka Super) key was the complete accident that turned this into a real annoyance. Instead of one word being deleted, entire windows are removed. (The irony of course is thanks to mosh+tmux, the word was still there once I reconnected to that computer.)"
1733991,2017-11-23 00:01:35 UTC,apport information
1733991,2017-11-23 00:01:37 UTC,apport information
1734012,2017-11-23 02:22:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522425"
1734012,2017-12-08 02:56:59 UTC,"This bug is tracked in:
https://bugs.launchpad.net/nova/+bug/1726301"
1734012,2018-01-29 09:23:27 UTC,"Change abandoned by Yikun Jiang (Kero) (<email address hidden>) on branch: master
Review: https://review.openstack.org/522425"
1734014,2017-11-23 03:00:03 UTC,"Now what? will you send me an email, what do I expect now?"
1734014,2017-11-23 02:51:56 UTC,I need some one to tell me what to do in plain English. Dumbfounded.
1734014,2017-11-23 02:56:26 UTC,This seems like the same kind of problem I have been having for a while. This is kind of the same problem I was having when my vista program died.
1734025,2018-02-09 07:13:42 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1734025,2018-09-17 08:15:13 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/603044"
1734025,2019-03-22 19:05:39 UTC,"Reviewed:  https://review.openstack.org/603044
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4d7148709c5de098141fbee12ad2e78c61e3b174
Submitter: Zuul
Branch:    stable/pike"
1734025,2019-04-26 17:16:01 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1734025,2018-02-01 08:58:38 UTC,"Reviewed:  https://review.openstack.org/522112
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ca6daf148debb9c9646fcf6db9660c830da5a594
Submitter: Zuul
Branch:    master"
1734025,2018-01-31 15:06:34 UTC,does this actually happen for non-boot-from-volume instances that have volumes attached?
1734034,2018-03-23 04:33:11 UTC,"According to the bug report you are using Wayland so Xorg has nothing to do with it (especially since gedit is affected, which rules out Xwayland too)."
1734034,2018-04-05 17:54:06 UTC,"Thank You @vanvugt. I didnt knew much about X Window System, and GTK when I feel first reported this Bug."
1734034,2018-04-06 13:07:08 UTC,"To @vanvugt, i was able to print the unicode in a window i coded on X11, since X11 use libinput, i do not think its an issue with libinput."
1734034,2018-04-09 09:44:34 UTC,To my Surprise. Unicode works on the Activities Search bar.
1734034,2018-08-08 08:26:40 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1734034,2018-08-08 10:33:31 UTC,i have checked it on Release 18.04 the issue does exisit.
1734034,2020-01-16 14:28:39 UTC,It's maybe worth reporting upstream on https://gitlab.gnome.org/GNOME/gtk/issues
1734040,2018-08-24 13:49:17 UTC,"This was fixed upstream a while back in response to you reporting it directly to them (https://anongit.mindrot.org/openssh.git/commit/?id=5db6fbf1438b108e5df3e79a1b4de544373bc2d4); that fix was in OpenSSH 7.7p1 and is thus in cosmic.  It might not be a bad idea to backport this fix to xenial and bionic, so I've opened bug tasks for that."
1734040,2017-11-24 10:19:17 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue.
1734040,2018-10-29 17:36:48 UTC,"Is there a sccenario where this can be easily triggered? I'm thinking both in terms of priority for this fix, and for an SRU test case description."
1734044,2019-08-14 02:12:05 UTC,The fix for this bug was first released in mutter version 3.27.91-real. So yes Ubuntu 18.04 onward will have the fix.
1734044,2017-10-27 13:59:37 UTC,Review of attachment 361654:
1734044,2017-10-16 10:11:05 UTC,"Created attachment 361657
ArchLinux PKGBUILD patch to include Jonas' working patch"
1734044,2017-10-18 12:59:17 UTC,"Created attachment 361801
another backtrace of the latest bug"
1734044,2017-10-17 04:17:29 UTC,"Jonas, I applied your patch from https://bugzilla.gnome.org/show_bug.cgi?id=788764#c13 and it fixed the crash. Thanks a lot!"
1734044,2017-10-16 17:58:09 UTC,For me it works now: I can reliably turn off and on the screen without gnome-shell crashing. This increases usability significantly :).
1734044,2017-10-16 15:43:17 UTC,"Could you install debug symbols, and get a full backtrace and attach that? Using gdb, that'd be the output of ""backtrace full"" on the core dump. FWIW, the new trace could be also be bug 788627 or bug 788908."
1734044,2017-10-16 15:24:33 UTC,"Created attachment 361682
backtrace of the last bug from gdb"
1734044,2017-10-16 15:21:31 UTC,"Created attachment 361681
systemd journal of crashing after applying the latest patch"
1734044,2017-10-16 12:03:45 UTC,Thanks! I will try the patch as well tonight and report back.
1734044,2017-10-16 09:08:50 UTC,"Created attachment 361654
window/wayland: Handle resizing when headless"
1734044,2017-10-12 20:55:22 UTC,"Created attachment 361462
libmutter.so null pointer dereference backtrace and regs"
1734044,2017-10-15 07:11:42 UTC,The latest changes in the gnome-3-26 branch solve these problems for me. I still have to apply the workaround in bug 788788 though. With mutter from gnome-3-26 and that workaround I can reliably switch my screen off and on without gnome-shell/mutter crashing.
1734044,2017-10-13 10:20:53 UTC,I posted a USD 100 bounty at bountysource.com to get this fixed.
1734044,2017-10-13 10:12:47 UTC,"Created attachment 361502
Trace of NULL pointer deref in meta_logical_monitor_get_scale"
1734044,2017-10-13 10:11:23 UTC,"Georg: your second trace (attachment 361462) looks more similar to mine in bug 788788. I will attach it here as well, it contains more symbols than your trace."
1734044,2017-10-13 10:01:28 UTC,"Created attachment 361499
gdb log with JS backtrace"
1734044,2017-10-13 03:58:00 UTC,"The trace looks strikingly similar indeed, but where from in Javascript it came from is harder to determine."
1734044,2017-10-12 20:38:05 UTC,Tbe problem persists with the following ArchLinux packages:
1734044,2017-10-11 06:00:54 UTC,"Created attachment 361300
Backtrace"
1734044,2017-10-10 10:27:57 UTC,Probably a duplicate of bug 788607.
1734044,2017-10-10 10:18:55 UTC,"Created attachment 361234
systemd journal excerpt including backtrace"
1734044,2017-10-16 09:07:36 UTC,*** Bug 789040 has been marked as a duplicate of this bug. ***
1734044,2017-10-11 06:00:02 UTC,"I hit the same assertion when I switch my screen off/on (Dell P2415Q HiDPI, NVIDIA Quadro 2000 using Nouveau, on Wayland). I have applied the diff of commit 6eb7d13 referenced in bug 788607. Unfortunately, this did not resolve the problem."
1734044,2017-11-10 02:27:06 UTC,"Pushed to master. Marking the ARCH patch as ""rejected"" as I can't find any better patch status for it."
1734044,2017-11-23 07:22:43 UTC,"My guess is that this maybe related to this fix?
https://bugzilla.gnome.org/show_bug.cgi?id=788764"
1734044,2017-11-10 02:23:25 UTC,"Comment on attachment 361654
window/wayland: Handle resizing when headless"
1734044,2017-11-23 09:29:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734044,2017-12-22 08:21:54 UTC,Sounds like bug 1721577 or bug 1724557. Someone please review those in detail because all three Launchpad bugs are pointing to the same upstream bug. Three in Launchpad sounds like too many.
1734044,2018-07-20 01:50:33 UTC,"Also sounds like bug 1717170, which might have been closed too early."
1734044,2018-07-20 11:27:25 UTC,This bug was reported for Ubuntu Desktop 17.10.
1734044,2019-08-13 09:28:00 UTC,Is anything happening on this issue? It's been a while ...
1734044,2019-08-13 17:02:10 UTC,Original submitter of bug replying. I don't see this crash in 18.10 for a while now. I'd be okay to close it.
1734049,2017-11-24 09:39:23 UTC,"Yes, busy with porting all of zim to gi -- see ""next"" branch on github"
1734054,2017-12-01 15:36:31 UTC,"Do you have a more full stacktrace than this, or the nova-compute log itself? This doesn't tell us much about where it originates from."
1734054,2017-12-01 15:58:19 UTC,such as name the virtual machine with a chinese name.
1734054,2017-12-01 15:56:15 UTC,I think this should be related to the name of the virtual machine. This error occurs only if I name the virtual machine with a non-ASCII encoding.
1734054,2017-12-01 15:38:27 UTC,Looks like it's coming from the logging in this method:
1734054,2017-11-24 08:11:16 UTC,Needs nova version.
1734055,2019-02-11 20:51:06 UTC,Problem solved (partially).
1734055,2017-11-23 10:07:00 UTC,Thanks Colin I will check those links.
1734055,2017-11-23 09:55:59 UTC,"I've reassigned this bug to Klavaro rather than to the launchpad.net site itself, but I'm not sure whether the Klavaro developers actually use bug tracking on Launchpad (I know nothing about Klavaro myself).  You might have more luck here:"
1734059,2021-01-26 15:53:39 UTC,"The ""config"" here should be ""as seen by Mojo"" rather than a full path. So if your deploy phase is ""deploy config=services"" you should be running ""mojo deploy-show --options config=services"". However, I can confirm if you use the full path here it does indeed wipe the contents of the file, and shouldn't."
1734059,2021-01-26 16:48:59 UTC,"The offending bit of code is line 668 of mojo/phase.py. In this case config_src is a fully qualified path, so we do `os.path.join(one_fully_qualified_path, another_fully_qualified_path)` which returns `another_fully_qualified_path` rather than `one_fully_qualified_path+another_fully_qualified_path`."
1734059,2021-02-01 11:53:22 UTC,"This has been fixed and released in the snap. The package is currently being copied from the proposed PPA to the main release PPA, so marking this bug as fix released."
1734075,2018-05-08 19:55:47 UTC,There is already javascript codes in http://git.openstack.org/cgit/openstack/os-api-ref/tree/os_api_ref/assets/api-site.js#n35 but the problem I think is that those javascript files are not loaded via index.html . http://git.openstack.org/cgit/openstack/os-api-ref/tree/os_api_ref/__init__.py#n668 describes some procedures. A stylesheet file is successfully referenced to index.html but two javascript files are not.
1734075,2017-12-05 08:55:52 UTC,We can solve this bug by adding jquery code into the docs.js file.
1734083,2017-11-23 09:28:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522496"
1734083,2017-11-24 01:45:24 UTC,"Change abandoned by liusheng (<email address hidden>) on branch: master
Review: https://review.openstack.org/522496
Reason: it is better to to use specified version in headers in future(which we will support microversion)"
1734084,2017-11-24 16:22:30 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].
1734084,2017-11-23 09:30:05 UTC,This change was made by a bot.
1734084,2017-12-04 20:15:09 UTC,"Can you also test the latest 4.13 upstream stable kernel, to see if the fix was also cc'd to stable?"
1734084,2017-11-28 14:02:33 UTC,I tested with the latest upstream v4.14 kernels and the issue appears to be fixed.
1734091,2017-11-30 11:18:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734094,2017-11-23 21:54:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1734095,2018-11-05 09:29:13 UTC,"Just to confirm I am still seeing this in 18.10.  A few more details:
If I open Software & Updates and switch to the Other Software tab and click one of the checkboxes the window loses focus but the authentication dialog does not appear (I have checked it is not under another window).  If however I click a checkbox on the Ubuntu Software tab then the authentication dialog does appear."
1734095,2019-04-24 02:27:03 UTC,I can also reproduce this reliably in Disco. I tried to enable Canonical Partner packages so I think it's easy to trigger.
1734095,2019-04-17 08:46:25 UTC,"Log attached, this is from the Disco system"
1734095,2019-04-16 19:32:07 UTC,"@Colin, can you add your journalctl log after getting the issue? I can't reproduce on any machine :-/"
1734095,2019-04-16 16:54:10 UTC,"Just to confirm I can reproduce this 100% reliably in 18.10 and in Disco, as follows.
Open Software & Updates and switch to the Other Software tab and click one of the checkboxes the window loses focus but the authentication dialog does not appear (I have checked it is not under another window). If however I click a checkbox on the Ubuntu Software tab then the authentication dialog does appear."
1734095,2019-04-24 10:15:40 UTC,Do you have any special component/application open that could grab the focus and make gnome-shell fail it?
1734095,2019-04-16 14:21:13 UTC,"Explaining the rls-dd-notfixing tagging, we reviewed the bug in our team meeting. There has been one report only so far and those warnings/similar problem exist upstream, we believe at this point that the bug is neither new nor easy to trigger and while it would be nice to fix it's not a candidate for release targetting in the current state"
1734095,2018-11-05 01:21:09 UTC,"Luis,"
1734095,2015-06-22 16:02:39 UTC,"gnome-shell periodically stops working - no response to most mouse inputs (hot corner gives animation but not change into overlay). The only indication of failure is message ""Gjs-Message: JS LOG: pushModal: invocation of begin_modal failed"" on stdout. I could not find more problems in journalctl."
1734095,2018-11-03 11:31:34 UTC,"I seem to have found a solution. Install polkit, in my case
sudo apt install lxpolkit"
1734095,2018-11-03 11:15:34 UTC,"I am having similar problem in Lubuntu 18.04 LTS. I found it originally when I run 'Software and Updates' from the menu (software-properties-gtk) and try to check/uncheck software sources. Checking/unchecking does not work. I can only see the error message ""ERROR:root:Authentication canceled, changes have not been saved"" if I run it from the command line."
1734095,2018-08-17 08:28:43 UTC,"@Darius, the point is the bug is not about gnome-software it is about software-properties-gtk.  To run it from a terminal use the command
/usr/bin/python3 /usr/bin/software-properties-gtk"
1734095,2018-08-17 06:17:47 UTC,@Colin Authorization dialog does not show up for me also and I am getting same error message in logs. I only linked second issue because I think it could be related.
1734095,2018-08-16 19:54:57 UTC,"@Darius this bug is about the Software & Updates app, which is the one that controls sources.list etc.  The bug is that it does not popup the Authorization dialog.  It seems to be in no way related to your issue."
1734095,2018-08-16 19:36:10 UTC,"I have the same problem since 17.10, running currently 18.04. Reinstalling gnome-software did not help."
1734095,2018-08-08 08:27:01 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1734095,2018-05-18 19:14:58 UTC,sorry just noticed your question a year later.
1734095,2019-04-24 11:18:51 UTC,"For myself, I have not got any other applications open, and I have not got any Gnome shell extensions enabled (according to Gnome Tweaks).
There must be something significant about the fact that it only fails from the Other Software tab, it works from the Ubuntu S/W, Updates and Developer Options tabs.
There must be something unusual about the failing systems though, but what it is remains a mystery."
1734095,2017-12-22 08:23:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734095,2016-08-24 17:35:34 UTC,it's a limitation of X that applications can break the desktop like that.  Wayland fixes it.
1734095,2016-08-24 13:07:58 UTC,"(In reply to Jasper St. Pierre (not reading bugmail) from comment #1)

> That means that some other application took an X11 grab. There's not much I
> can tell you other than to find the application that did that and figure out
> what's going on.
"
1734095,2015-08-10 23:58:17 UTC,"I see this in efi boot f23 Alpha RC-2 workstation x86_64 installed to HD
may be related to ff google callendar pop up event alerts..?
Total system freezes up  have to cold boot to recover."
1734095,2015-06-25 02:53:34 UTC,"(In reply to Jasper St. Pierre from comment #4)

> Unfortunately, debugging tools on X11 are severely limited -- there is no
> application which can tell you who took the grab. Are you able to reproduce
> it often?
"
1734095,2015-06-23 17:07:42 UTC,"Unfortunately, debugging tools on X11 are severely limited -- there is no application which can tell you who took the grab. Are you able to reproduce it often?"
1734095,2015-06-23 16:51:47 UTC,"(In reply to Jasper St. Pierre from comment #1)

> That means that some other application took an X11 grab. There's not much I
> can tell you other than to find the application that did that and figure out
> what's going on.
"
1734095,2015-06-23 01:52:47 UTC,"this is a known bug when using the Overview on Startup or alternate Jump to Overview extension. I was never wise enough to determine why or what we are doing wrong to cause this, but alas it happens depending on how you use the extension. Some talk can be found here, but we are both clueless:"
1734095,2015-06-22 19:58:22 UTC,That means that some other application took an X11 grab. There's not much I can tell you other than to find the application that did that and figure out what's going on.
1734095,2017-05-25 18:58:50 UTC,"(In reply to Ray Strode [halfline] from comment #8)

> it's a limitation of X that applications can break the desktop like that.
> Wayland fixes it.
>
> Anyway, I think Daniel Stone added the ability to print grab clients a while
> back.  digging a little, what you have to do is:
>
> $ gsettings set org.gnome.desktop.input-sources xkb-options ""['grab:debug']""
>
> then hit ctrl-alt-F11 and grab info will be sent to the journal.  You'll
> still have to use xwininfo or xlsclients or something to match up the client
> ids.
"
1734095,2019-04-24 15:31:22 UTC,"It doesn't seem to be to do with user settings as I have tried making a new user and it fails for that user also.
I can also confirm that it is ok on Wayland, which is not surprising."
1734095,2019-11-19 21:37:28 UTC,@Arnaud D this bug is specifically about the Authorization dialog in the Software and Updates app.  It is not a general problem with the mouse.  In fact it is nothing to do with the mouse at all.
1734095,2019-09-28 20:20:35 UTC,Maciej: Is this still an issue? Or can this be closed as RESOLVED OBSOLETE?
1734095,2020-11-07 12:01:35 UTC,"I think it might have been something wrong with my wireless mouse, because it also caused some issues with the window manager on Macs. I have a set of Microsoft keyboard and mouse, and when I used the mouse on Mac, it caused some issues with highlighting of menu items. When I replaced it with a different wireless mouse (but kept the keyboard), the issue was gone."
1734095,2020-10-08 11:22:09 UTC,"Created attachment 374289
Journalctl after using Ctrl+Alt+F1"
1734095,2020-10-08 11:19:19 UTC,"I'm also facing this issue on Ubuntu 18.04. When I used Dmitry workaround journalctl spitted number of stack traces and asserts, but everything started to work."
1734095,2020-10-08 10:54:29 UTC,"Hi,
Is there a chance to get this fixed or have a workaround? I'm using Ubuntu 18.04 and situation is getting worse. I berly can use my OS. If you need debug log or some other support pls let me know I can provide it."
1734095,2020-08-12 08:14:21 UTC,Is this really related to the linked gnome-shell bug?  It doesn't look related to me.  This bug is completely reproducible whereas the linked one seems to be an intermittent complete failure of the shell.
1734095,2020-08-12 06:35:33 UTC,Aaand... here I am on 20.04 with the same issue. What does software-properties-gtk use to prompt for root access - and why doesn't it work?
1734095,2020-08-11 10:02:28 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020."
1734095,2019-06-04 14:47:16 UTC,"I have this bug also in Disco...i can not update from update-manager if it is a kernel update...the window asking for credential fails to appear.
ERROR:root:Authentication canceled, changes have not been saved"
1734095,2020-02-14 14:44:27 UTC,"I am still seeing thins on a fresh Eoan install ..
https://bugs.launchpad.net/bugs/1857892"
1734095,2020-01-27 11:33:27 UTC,I don't seem to be able to change the status back to confirmed for some reason.
1734095,2020-01-27 11:30:54 UTC,I am still seeing this in 19.10 (eoan).
1734095,2020-01-24 09:49:06 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1734095,2019-12-20 10:58:30 UTC,"(In reply to André Klapper from comment #11)

> Maciej: Is this still an issue? Or can this be closed as RESOLVED OBSOLETE?
"
1734095,2019-11-19 20:04:22 UTC,"After days of fresh reinstallations and tests, I finally found what was causing this on my end and finally solved it by using a xorg configuration override 10-evdev.conf as shown on [1]"
1734095,2019-09-30 11:20:46 UTC,"It is still an issue on 19.04.
Steps to replicate:
Open Software & Updates and switch to the Other Software tab and click one of the checkboxes. The window loses focus but the authentication dialog does not appear. If however a checkbox on the Ubuntu Software tab is clicked then the authentication dialog does appear."
1734095,2020-05-28 09:14:41 UTC,"Have recently faced the same issue on Ubuntu 18.04. It occurs rather frequently, sometimes, within ten minutes. Previously, it has never occurred. Same message is printed in the logs."
1734100,2018-02-09 20:19:12 UTC,Maybe gilir can take a look at this.
1734100,2017-11-24 10:08:58 UTC,On my last post read lubuntu-default-settings where I wrote ubuntu-system-settings.
1734100,2017-12-06 15:31:04 UTC,"I have repeated the process, marking to hold lubuntu-core and lubuntu-desktop  as well before the final test to make sure they get installed together."
1734100,2017-11-24 03:47:00 UTC,I'm curious who thought adding these as direct dependencies was a good idea...
1734100,2017-11-23 13:45:31 UTC,I don't think the problem is with indicator-sound/-gtk2.
1734100,2017-11-23 11:41:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734100,2017-11-24 09:48:48 UTC,"Daniel, that is why I said to change to suggests *or* to ""add lubuntu-default-settings"", this means to put it together with other ""or"" alternatives."
1734104,2017-11-23 14:34:58 UTC,automatic autoremoval is a difficult topic with a lot of things to consider:
1734104,2017-11-23 15:47:03 UTC,"The main reason to do this is kernel cruft. We have had kernels being
flagged for removal for years now, and it's completely reliable. We
really should garden that automatically."
1734104,2017-11-23 16:20:45 UTC,"Oh right, that's another use case I forgot about. I can see cleaning them up automatically in unattended-upgrades and dist-upgrade (or well, when any new kernel is installed). I just don't want to accidentally autoremove a desktop or something :)"
1734104,2018-02-16 07:34:07 UTC,"@sabdfl I absolutely agree that unused kernels should be removed, and it is being fixed in LP: #1624644 right now."
1734104,2018-02-16 09:21:06 UTC,"Perhaps we are talking at cross purposes. My expectation is that update
would list the packages to be removed because they are no longer
dependencies of packages that were consciously installed. On that basis,
there should be no surprise to users. The messaging could point users to
a handy document to understand how they can make a package stick around
by flagging it as one they have manually / consciously installed."
1734106,2017-12-02 14:07:24 UTC,"rg@rggr:~$ sudo modprobe vboxdrv
[sudo] Mot de passe de rg :
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.13.0-18-generic
rg@rggr:~$"
1734106,2018-11-22 18:53:09 UTC,"Ubuntu crashes after update on nov 22 <<< On 4 18.0 12
impossible to restart //////
can open on recovery ;ode <<< 1st part and thenm  crashs see picture on"
1734107,2017-11-26 08:53:03 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1734107,2018-08-09 16:43:49 UTC,I attached a patch to the debian bug report that fixes the application for me on bionic.
1734109,2018-01-18 09:03:39 UTC,"The verification of the Stable Release Update for python2.7 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1734109,2018-01-18 09:03:19 UTC,This bug was fixed in the package python2.7 - 2.7.12-1ubuntu0~16.04.3
1734109,2017-12-04 16:45:31 UTC,"Hello Matthias, or anyone else affected,"
1734109,2017-12-04 15:43:51 UTC,"Hello Matthias, or anyone else affected,"
1734109,2017-12-05 08:45:46 UTC,packages successfully built. inspected the python binary for the renamed functions.
1734109,2017-11-23 11:38:19 UTC,the change is already in artful and bionic
1734111,2019-04-24 07:46:28 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel?
Thanks."
1734111,2019-06-24 04:17:20 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1734129,2018-01-09 12:33:17 UTC,Thanks Lars!
1734129,2018-01-09 11:03:41 UTC,"This is basically how upstream packaging does it (with some additional restrictions: https://github.com/mysql/mysql-server/blob/5.7/packaging/deb-in/extra/mysql-helpers#L76); if the directory already exists it isn't touched.
There are some restrictions on what the permissions on the secure-file-priv location should be (the server will log a warning if it considers the directory insecure), but the proposed change will just make it more in line with the upstream packaging."
1734129,2017-11-24 09:59:26 UTC,"Hi Sigurd,
this is present up to the latest version of mysql.
So I'm adding tasks for them as well."
1734129,2017-12-12 10:51:54 UTC,Thank you Christian! And sorry for the late follow-up.
1734129,2017-11-24 10:02:28 UTC,In general I think if one comes up with a working patch people are willing to review&test but I'd not expect dev's to jump onto this as it might cause as much trouble (e.g. fail after upgrade as it can#t start on the custom permission dir).
1734129,2017-12-12 12:27:52 UTC,"The attachment ""Diff for DEBIAN/postinst for mysql-5.*"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1734131,2018-02-13 20:20:07 UTC,Are we going to provide APIs to allow users to get/set the boot mode?
1734131,2018-02-15 10:50:34 UTC,"> Are we going to provide APIs to allow users to get/set the boot mode?
"
1734131,2018-02-15 10:51:21 UTC,https://review.openstack.org/#/c/526773/
1734131,2018-02-22 10:14:19 UTC,"This is not fixed yet, is it?"
1734132,2018-04-15 07:00:07 UTC,See also https://bugs.documentfoundation.org/show_bug.cgi?id=116941
1734132,2017-12-13 16:18:51 UTC,"Thanks! So this is not a regression introduced by 5.4.2, that's good to know."
1734132,2017-12-13 15:37:17 UTC,"I've downgraded successfully, the about dialogue shows"
1734132,2017-12-13 11:21:50 UTC,"Sorry, I should have tested that first before sharing the instructions…
There you go, with those you should be able to downgrade:"
1734132,2017-12-13 10:22:34 UTC,I'm seeing the following:
1734132,2017-12-12 16:12:42 UTC,Let's try a different approach for a clean downgrade:
1734132,2017-11-24 10:13:06 UTC,"wait a second. That string doesn't look right, i.e. Version: 5.4.2.2 does not look like it's been downgraded. I expected 5.4.1. But I can't make it show that. It seems that the libreoffice-common package is defining that version string. That is indeed a newer version here for me. Downgrading that seems to incur some other trouble:"
1734132,2017-11-24 10:03:53 UTC,Downgrading libreoffice-gtk3 to
1734132,2017-11-23 22:30:38 UTC,"FTR: when I'm not connected to the second monitor, which I have set to 200% scaling, I get the context menu as expected."
1734132,2017-11-23 20:11:13 UTC,"Yeah, definitely something wrong with menus there…"
1734132,2017-11-23 16:06:20 UTC,meh.
1734132,2017-11-23 15:44:13 UTC,Try:
1734132,2017-11-23 15:21:35 UTC,I have trouble downgrading:
1734132,2017-11-23 14:56:51 UTC,Not seeing that in my wayland session (i.e. the context menu does show up as expected).
1734132,2017-11-24 05:19:28 UTC,"That's a very good clue. So I assume if you set it to 100% scaling you get the menu as expected?
Can you try context menus in other applications (e.g. firefox, chromium-browser, gedit, and maybe a Qt-based application) and report here how they behave?"
1734142,2017-11-30 23:45:02 UTC,That's what you get when Ubuntu syncs packages from Debian experimental that are not ready for wider use yet.
1734142,2018-02-12 19:16:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734142,2018-02-12 19:18:47 UTC,in 17.10 the following error displayed -
1734150,2018-02-13 21:19:43 UTC,"Hello,"
1734150,2018-02-13 21:19:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734153,2017-11-25 20:23:57 UTC,"Sorry, I don't have a patch, I was offering to update the upstream bug if that was deemed helpful"
1734153,2017-11-25 13:41:49 UTC,"Don't hesitate to provide a patch for that!
I will be happy to apply it!"
1734153,2017-11-23 20:03:26 UTC,"I'm not exactly sure of the effect of attaching a bug watch, but I note that defect is over 3 years old, and has had no update or response. If the idea is to wait for an implementation in Debian, then some kind of update to the effect that this is now a soluble issue might be warranted? I'm happy to do that if needed..."
1734153,2017-11-23 18:44:49 UTC,Thanks for reporting.
1734154,2020-05-11 08:30:29 UTC,Horizon should validate filepath and container name in URL before invoking file related operations.
1734158,2017-11-23 17:21:25 UTC,Added UX tag as this issue might block openstack clouds users using deployed servers and trying external deployments performed with configs download mechanism.
1734167,2018-03-21 11:43:04 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1734167,2018-03-21 11:42:35 UTC,This bug was fixed in the package systemd - 234-2ubuntu12.3
1734167,2018-03-16 14:55:04 UTC,See my attached log for verification of artful.
1734167,2018-01-17 21:38:34 UTC,"Marked as fix-released.
I tested today with 20180115.1 image from bionic."
1734167,2018-01-03 19:24:22 UTC,This bug was fixed in the package systemd - 235-3ubuntu3
1734167,2017-12-16 18:01:34 UTC,"Dimitri,
What is the fix that you put in?   I assume it was to systemd ?"
1734167,2017-11-28 16:56:06 UTC,"I've verified that this is reproducible within lxc, and then filed a bug i
saw (bug 1734939) as a result."
1734167,2017-11-27 22:06:02 UTC,"We will still need something that helps ensure systemd-resolved runs we reach network-online.target;  and I suspect (though I've not validated yet) that we really want systemd-resolved to be running prior to systemd-networkd such that systemd-networkd can relay DNS configuration info retrieved from DHCP results, ala how resolvconf was hooked on networking config touching files in /run."
1734167,2017-11-27 21:12:42 UTC,I agree that systemd-resolved should be DefaultDependencies=no.
1734167,2018-02-22 18:36:55 UTC,"Hello Michael, or anyone else affected,"
1734167,2017-11-27 20:41:50 UTC,"To be clear, the suggestion that xnox made causes a ordering cycle."
1734167,2017-11-24 18:02:57 UTC,that ordering cycle is if we add 'After=systemd-resolved.service' to cloud-init.service.
1734167,2017-11-24 18:02:19 UTC,zesty does not show this problem. neither does xenial. I reflected that in the status.
1734167,2017-11-24 17:59:44 UTC,zesty does not show this problem. neither does xenial. I reflected that in the status.
1734167,2017-11-24 17:46:55 UTC,"<xnox> smoser, yeah, so like cloud-init.service should want/after systemd-resolved.service; or e.g. systemd-resolved.service should declare itself before cloud-init.service
<xnox> smoser, i think changing it in systemd unit might be better."
1734167,2017-11-24 17:36:43 UTC,"I think the primary issue is that cloud-init.service is depending on using the network fully.
cloud-init.service runs:
  After=networking.service
  After=systemd-networkd-wait-online.service
  Before=network-online.target"
1734167,2017-11-24 17:20:34 UTC,"Heres some more info that is from failed system using bionic.
$ sudo journalctl -o short-monotonic --no-pager | pastebinit
http://paste.ubuntu.com/26035621/"
1734167,2017-11-24 17:12:33 UTC,$ wget http://cloud-images.ubuntu.com/artful/20171122/artful-server-cloudimg-amd64.img
1734167,2017-11-24 16:49:49 UTC,"I'm not using the included kernel or initrd, so I decided to test without that."
1734167,2017-11-24 16:35:00 UTC,Entire command lines of how I'm doing this:
1734167,2017-11-27 20:52:36 UTC,"I suspect because in bionic/artful we're missing resolvconf package, that the systemd-resolved service ends up starting later in boot.  The systemd-resolved-update-resolveconf.{service,path} require /sbin/resolvconf to run;  this service had a path-based trigger that would get hooked whenever DHCP clients would call resolvconf to kick off a DNS update once config was available.
I suspect that systemd-networkd itself isn't poking DNS service properly after acquiring information."
1734184,2017-12-01 02:48:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734189,2017-11-24 17:07:32 UTC,"I am not quite sure also, but I think it worked in Ubuntu 12.04 and stopped working in Ubuntu 14.04 OR 16.04 (or in non-LTS releases in between). It affects Linux Mint Mate as well."
1734189,2020-01-09 01:05:06 UTC,"I am having the same issue - I use the single large 'cube' as a workaround, but sometimes my secondary monitor's contents don't render properly on the cube when rotating with the mouse."
1734201,2017-11-23 21:39:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1734201,2017-11-24 04:59:27 UTC,"This isn't a new bug, but it has been fixed in the past. I'm not sure whether to make a new bug or just link to it so it inevitably gets reopened. I'll post the link to the bug here: https://bugzilla.gnome.org/show_bug.cgi?id=746798"
1734201,2017-12-21 07:55:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734203,2017-11-24 00:21:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1734203,2020-09-09 07:47:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734212,2017-11-24 09:14:19 UTC,"Hi tenwit,
thanks for your report!
You did just right to clean up and complete the installation."
1734212,2017-11-26 20:33:38 UTC,"Yep thanks for that. I filled in the report that automatically popped up on when the system errored; I didn't want to contradict the auto-filled-in fields, I assumed it knew more about what had gone wrong than I did :)"
1734225,2020-09-28 14:09:57 UTC,While I was preparing a fix for this I realized this probably would be SRU-rejected anyway.
1734225,2020-09-28 12:41:34 UTC,"Hi,
coming by here after no movement for a while as this was forgotten.
o/ Karl :-)"
1734225,2018-03-02 21:31:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734225,2018-03-11 22:28:15 UTC,"I ran into this problem as well, and the solution (editing /etc/default/ctdb) does resolve the issue."
1734225,2018-03-21 12:32:56 UTC,Thanks for this report.
1734227,2018-01-25 19:31:40 UTC,"Hi Paul,"
1734227,2018-01-25 19:35:45 UTC,Marking incomplete for now until we can get more details on system load.
1734227,2018-02-01 22:07:09 UTC,Sounds like nova is doing it's job but not getting the information from neutron. I'm going to mark as invalid for nova unless proven otherwise.
1734227,2018-04-12 16:37:26 UTC,I believe a possible root cause for this is bug 1763442
1734229,2017-11-24 02:53:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522691"
1734235,2017-11-24 14:43:11 UTC,"Sent from Mailspring (https://link.getmailspring.com/link/local-78f2527c-9667@lindon/0?redirect=https%3A%2F%2Fgetmailspring.com%3Fref%3Dclient&recipient=1734235%40bugs.launchpad.net), the best free email app for work"
1734235,2017-11-24 15:16:13 UTC,"If we follow this style of generic exceptions it is very hard to get them consistent, and showing all the information that they should include, because exception messages are spread all over the code base."
1734238,2019-10-24 09:34:33 UTC,"Hi,"
1734238,2017-12-10 13:38:35 UTC,It's resolved on its own not sure through what update though.
1734238,2019-10-24 09:33:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734240,2017-11-24 03:15:11 UTC,"There is an exception in snapcraft/internal/errors.py called PrimeFileConflictError, that apparently should be raised in this case."
1734256,2017-11-29 13:48:05 UTC,The same issue on ubuntu 12.04 64bit
1734256,2017-12-04 09:13:25 UTC,"I bet this affects more than two people!! Could it be related to Ubuntu no longer supporting
12.04 LTS?
OK I'm tending to use 16.04 more but still find 12.04 useful, especially for any videos. The Dash is fine as long as you can remember the name of a rarely used program, scrolling all apps in the Indicator is easier than searching through the Ubuntu software."
1734267,2018-01-06 14:23:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734274,2017-11-24 15:29:50 UTC,"Gabor, the file ends up rendered (through MAAS's tempita) into yaml.
That yaml then needs to define a dictionary for 'early_commands'."
1734274,2017-11-24 15:06:36 UTC,"curtin succeeds with indentation before first line comment:
early_commands:
  #disable_reboot: touch /run/block-curtin-poweroff /tmp/block-poweroff /tmp/block-reboot
{{if third_party_drivers and driver}}
  {{py: key_string = ''.join(['\\x%x' % x for x in map(ord, driver['key_binary'])])}}
..."
1734274,2017-11-24 09:40:35 UTC,"Hi,
I'm glad to hear that you have a workaround for now.
I checked most recent in the repo, but it works for me atm.
There are no changes from r532 (what you have) to r542 (head) that would affect this."
1734274,2017-11-24 09:42:21 UTC,"Can be run to see output like:
nosetests -v --nocapture tests/unittests/test_pack.py:TestPack.test_pseudo_install_empty"
1734274,2017-11-24 09:49:46 UTC,"how does your config look like ?
don't you have the driver test like this ?"
1734274,2017-11-24 09:51:21 UTC,If you could check what the effective full generated config would be that might help to spot the root cause.
1734274,2017-11-24 10:00:52 UTC,this is the full config:  (I'm not sure what you mean by generated)
1734274,2017-11-24 13:56:17 UTC,attaching a console output of the issue
1734274,2017-11-24 14:35:08 UTC,"I had put up a merge proposal a while ago at
 https://code.launchpad.net/~smoser/maas/+git/maas/+merge/332573
that covers this basic issue.
The preseeds files in /etc/ are quite non-trivial to edit.
My solution in that mp was to empty out the maas internal sections from there
as they're not really expected to be editable anyway.
If my merge proposal above was taken it would at least be more obvious to the user what they were writing in the config.  Any complexity would have been their own additions."
1734274,2017-11-24 22:35:45 UTC,"I opened bug 1734391, updated my merge proposal and linked the mp to the bug."
1734277,2017-12-06 09:45:49 UTC,"Hello.
In order to work around this problem, we need to install the proprietary NVIDIA driver. (384.90)"
1734277,2017-11-27 08:32:14 UTC,Hello
1734277,2017-11-27 09:26:40 UTC,here a boot-info file
1734277,2017-12-06 17:36:03 UTC,This is  trace of stopping computer with X11 session  ans nvidia driver
1734278,2017-12-13 05:12:23 UTC,"amd64 build of grub2-signed 1.66.15 in ubuntu xenial PROPOSED
https://launchpad.net/ubuntu/+source/grub2-signed/1.66.15/+build/13848452"
1734278,2018-01-31 15:39:59 UTC,"The bugs identified above are not regressions from this SRU, but recurring issues due to bad configurations (broken install, plymouth --ping bug)."
1734278,2018-01-31 15:42:39 UTC,This fix for grub2-signed was already uploaded to bionic -- along with the grub2 upload.
1734278,2018-01-31 20:30:53 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of grub2 from artful-proposed was performed and bug 1745221 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1745221 (not this bug). Thanks!"
1734278,2018-02-02 14:54:07 UTC,"Can anyone help testing this fix for timers on Intel, for artful?"
1734278,2018-02-05 03:50:11 UTC,System can boot to Ubuntu desktop (artful) after installing following packages.
1734278,2018-02-05 08:57:21 UTC,This bug was fixed in the package grub2-signed - 1.85.1
1734278,2018-02-05 09:07:17 UTC,This bug was fixed in the package grub2 - 2.02~beta3-4ubuntu7.1
1734278,2017-12-06 20:22:39 UTC,This bug was fixed in the package grub2 - 2.02-2ubuntu2
1734278,2017-12-12 22:32:23 UTC,"Hello Ivan, or anyone else affected,"
1734278,2017-11-24 07:29:21 UTC,"The patch which fixed this issue has included in the upstream git repository,
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=446794de8da4329ea532cbee4ca877bcafd0e534"
1734278,2017-11-30 15:13:21 UTC,"Description of problem:
On some newer Intel silicon GRUB2 will hang when trying to boot."
1734278,2017-12-01 05:44:51 UTC,I have pinged cyphermox on irc to apply the patch in #1 to Xenial.
1734278,2017-12-05 03:15:08 UTC,Please also update http://archive.ubuntu.com/ubuntu/dists/xenial-proposed/main/installer-amd64/current/images/cdrom/debian-cd_info.tar.gz or something like for this issue on xenial.
1734278,2017-12-05 15:13:58 UTC,"That will need a d-i upload as well then, after grub is released."
1734278,2017-12-12 22:39:04 UTC,"Hello Ivan, or anyone else affected,"
1734278,2018-01-30 20:30:56 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of grub2-signed from artful-proposed was performed and bug 1746133 was found.  Please investigate that bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1746133 (not this bug). Thanks!"
1734278,2018-01-30 17:32:08 UTC,"grub2-2.02-0.43.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report."
1734278,2017-12-12 06:43:00 UTC,"For OEM project, we need grub and debian-installer packages to be SRUed (xenial-proposed) before 2018/1/5"
1734278,2018-01-23 21:37:37 UTC,grub2-2.02-22.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbcc83aa97
1734278,2017-12-22 03:36:00 UTC,"I have verified the debian-installer and grub packages, and they do fix the problem for xenial."
1734278,2017-12-21 16:54:34 UTC,"Hello Ivan, or anyone else affected,"
1734278,2017-12-19 18:16:43 UTC,"Marking bionic Fix Released; Steve uploaded a debian-installer, which was built against the new grub."
1734278,2017-12-15 03:21:04 UTC,@Brian
1734278,2018-01-02 11:14:07 UTC,This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.15
1734278,2018-01-17 20:23:17 UTC,grub2-2.02-0.43.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-f6166caf0b
1734278,2018-01-17 20:23:50 UTC,grub2-2.02-20.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbcc83aa97
1734278,2018-01-25 08:36:25 UTC,"grub2-2.02-22.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbcc83aa97"
1734278,2018-01-02 11:13:57 UTC,This bug was fixed in the package debian-installer - 20101020ubuntu451.18
1734278,2018-01-02 11:14:03 UTC,"The verification of the Stable Release Update for debian-installer has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1734278,2018-01-18 01:18:10 UTC,"grub2-2.02-0.43.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-f6166caf0b"
1734278,2018-01-18 02:11:58 UTC,"grub2-2.02-20.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbcc83aa97"
1734278,2018-01-18 19:23:00 UTC,grub2-2.02-21.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbcc83aa97
1734278,2018-01-19 16:34:28 UTC,"grub2-2.02-21.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-fbcc83aa97"
1734278,2018-01-22 17:03:45 UTC,"Hello Ivan, or anyone else affected,"
1734278,2018-01-22 17:04:48 UTC,"Hello Ivan, or anyone else affected,"
1734278,2018-01-23 20:30:55 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of grub2 from artful-proposed was performed and bug 1744874 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1744874 (not this bug). Thanks!"
1734279,2017-12-04 20:36:04 UTC,"Hello Jon,"
1734280,2017-12-06 17:13:30 UTC,"We don't want all USB drives to be mounted read-only, and I'm pretty sure this was not the case in 10.04 or older.  Your rule simply makes every scsi drive but the first one to be detected ( which may or may not be USB ) read only."
1734280,2017-12-07 08:49:42 UTC,"I'm ok with you not wanting all USB drives to be mounted read-only -- such is the default behavior of Ubuntu.  But I and the company I work for want it to be that way to comply with out security policies.  And since HAL is already deprecated, the workaround I found for recent Ubuntu versions is to use the udev rule I posted above.  Your assertion about the rule is correct and it is intended to be that way."
1734280,2018-02-26 15:18:17 UTC,"I don't think it is udisks that is mounting the other filesystems read/only, but rather that those filesystems automatically fall back to read/only when they see the media is read-only.  You should be able to see the errors in dmesg where the fs falls back to read-only mode."
1734280,2018-02-27 00:19:58 UTC,"The attachment ""Check whether the device was forced read-only"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1734280,2018-02-26 21:05:14 UTC,Please try the attached patch
1734280,2018-02-26 17:38:28 UTC,"When a device is read-only (through a hardware switch preventing it to be written to), ntfs-3g falls back to a read-only mount (since ntfs-3g 2012.1.15AR.7).
Actually, ntfs-3g falls back to read-only mount whenever it gets an EROFS from trying to open a device read-write."
1734285,2017-12-09 15:31:38 UTC,"Hi Reczey,"
1734285,2017-12-09 15:15:16 UTC,"Files in /etc/apt/preferences.d/ are read when unattended-upgrade is run and not when u-u.service is started thus it is safe to assume that configuration changes take place without restarting u-u.service.
On the other hand there are cases when u-u does not respect pinning like the one reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838920
Are all the repositories trusted on the affected systems?"
1734290,2018-03-06 17:24:54 UTC,"I added that this affects System76 PopOS which, out of the box, did not offer an option to use anything but eCryptFS for local disk encryption."
1734290,2018-02-14 23:35:48 UTC,"You can put the call to 'pam_ecryptfs.so unwrap' before pam_systemd.so in /etc/pam.d/common-session as I mentioned above, but because this is a managed file, you will get a reminder that you modified it every time a package installation makes changes to /etc/pam.d.  So a better fix is this:"
1734290,2018-02-12 15:34:41 UTC,I think I have the same problem with Syncthing.
1734290,2018-11-22 12:27:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734297,2017-11-24 09:08:09 UTC,It's likely a bug in ubuntu or a driver issue because it works again after changing the audio device in ubuntu settings and then set it again to the original audio device and restarting Clementine. I'm using a Dell Docking Station (with a DisplayLink driver) as audio device.
1734298,2017-12-14 03:22:54 UTC,"Reviewed:  https://review.openstack.org/527031
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=9209c8e088a8ce0aef7b458477e27a6559939e43
Submitter: Zuul
Branch:    stable/pike"
1734298,2019-06-10 08:13:41 UTC,"I think deployed server with custom users on OOOQ now works, e.g. in CI we have a 'zuul' user that we initally connect as. Closing as fixed, please reopen if i'm incorrect."
1734298,2017-11-24 10:28:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/522771"
1734298,2017-11-24 10:59:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/522776"
1734298,2017-11-24 11:26:16 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/522771"
1734298,2017-11-28 10:52:03 UTC,"Reviewed:  https://review.openstack.org/522874
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=fde797ca14b194f588a46256c809729c2ef0135d
Submitter: Zuul
Branch:    master"
1734298,2017-12-05 11:42:02 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/522776"
1734298,2017-12-05 11:49:11 UTC,"As a w/a for quickstart, you can create a custom overcloud deploy playbook and export OVERCLOUD_SSH_KEY for the overcloud-deploy role's environment param, like https://github.com/bogdando/oooq-warp/blob/master/playbooks/oooq-traas-over.yaml"
1734298,2017-12-11 09:32:26 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/527031"
1734298,2017-11-24 17:08:47 UTC,Related change https://review.openstack.org/#/c/522874/
1734304,2019-09-16 08:48:30 UTC,Migrated to https://github.com/widelands/widelands/issues/3232
1734304,2017-11-26 18:25:08 UTC,P.S. the test I'm running for #5 is:
1734304,2017-11-26 18:22:39 UTC,Could somebody with Valgrind powers check if WaresWorkersMap in the attached branch is indeed leaking?
1734304,2017-11-26 09:28:37 UTC,tl;dr: #1 is not our bug.
1734304,2017-11-26 07:16:52 UTC,"Yes, I think so too. I tried to find a way to exclude them from the LeakSanitizer for now, but all my attempts were ignored. I'll concentrate on the errors in our own code first and then try to find out where glXGetFBConfigs is called from."
1734304,2017-11-25 18:53:55 UTC,"This one seems to be either in libMesa or in SDL. Maybe it is also something we are doing wrong with cleaning up, hard to say."
1734304,2017-11-25 16:12:51 UTC,All testsuite scenarios are producing the same memory leak:
1734311,2018-01-15 09:56:27 UTC,How did you install magnum and configured kube_openstack_config. Looking at the code it set's subnet-id only: https://github.com/openstack/magnum/blob/master/magnum/drivers/common/templates/kubernetes/fragments/write-kube-os-config.sh#L16
1734320,2019-10-03 08:20:12 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/686347"
1734320,2019-10-03 08:15:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/686346"
1734320,2019-10-03 08:03:02 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/686345"
1734320,2019-05-30 17:19:55 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: master
Review: https://review.opendev.org/635083
Reason: we have changed the direction somewhat so this is not needed in it current form."
1734320,2019-05-30 17:13:24 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/616285"
1734320,2019-05-30 17:13:12 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/609850"
1734320,2019-05-30 17:12:58 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/609851"
1734320,2019-03-01 04:54:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640258"
1734320,2019-02-06 01:26:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/635083"
1734320,2019-01-04 15:26:08 UTC,"hi just updating this.
the os-vif fix was released in 1.13.0 but that had a file Handel leak so
1.13.1 is the minium version that should be used to receive this fix."
1734320,2018-12-14 05:40:17 UTC,"Reviewed:  https://review.openstack.org/616609
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e3dc447b908f57e9acc0378111b8e09cbd88ddc5
Submitter: Zuul
Branch:    master"
1734320,2018-12-07 21:13:46 UTC,"Reviewed:  https://review.openstack.org/612534
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=d291213f1ea62f93008deef5224506fb5ea5ee0d
Submitter: Zuul
Branch:    master"
1734320,2018-12-07 13:33:40 UTC,"Reviewed:  https://review.openstack.org/602384
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=165ed325917e5deadb274ad9c122db157c0b55b2
Submitter: Zuul
Branch:    master"
1734320,2019-04-16 08:46:37 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/640258
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1734320,2019-10-04 15:39:54 UTC,"Reviewed:  https://review.opendev.org/686345
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ffee956d44da34e38e62f82a3bc676cdd6179f48
Submitter: Zuul
Branch:    stable/rocky"
1734320,2019-10-18 12:43:59 UTC,Should this bug be reopened for os-vif now when revert https://review.opendev.org/#/c/631829 was merged?
1734320,2019-10-18 13:27:15 UTC,"there is a mitagation for this bug in all cases except when the ovs firewall driver is used with kernel ovs.
https://review.opendev.org/#/c/631829 has not been reverted and there is no plans to revert it.
it."
1734320,2020-10-23 01:22:42 UTC,"Reviewed:  https://review.opendev.org/756478
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=24dd977c2217bb10baf2cf226eab2bd0e5b47d62
Submitter: Zuul
Branch:    stable/victoria"
1734320,2020-10-07 09:51:48 UTC,"Related fix proposed to branch: stable/victoria
Review: https://review.opendev.org/756478"
1734320,2020-10-06 23:01:30 UTC,"Reviewed:  https://review.opendev.org/753314
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c8a819aff4db62e58192af0a272a7f1ce7923146
Submitter: Zuul
Branch:    master"
1734320,2020-09-25 19:29:24 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/754475"
1734320,2020-09-08 10:56:33 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: master
Review: https://review.opendev.org/748296"
1734320,2020-09-04 13:28:55 UTC,"with that said it is safe to backport the neutron patch that recnetly merged and it will have to be backported before the nova patch is but we were recommending waiting for the nova patch and any other neutron patche that might be required to merge first before starting the backports
we only want to backport a fully working solution"
1734320,2020-09-04 13:27:16 UTC,by the way while the neutron patch is now merged the nova patch to delegate the pluggin to os-vif is blocked as the neutron api seams to be sending network-vif-plugged events at the wrong time when we are evacuating nad during some other lifecycle operations like revert. so untill we figure out that the backport fo the most resent neturon patch will do nothing help adress this.
1734320,2020-08-26 20:01:05 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/748296"
1734320,2020-08-25 15:38:56 UTC,"Reviewed:  https://review.opendev.org/640258
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7fd2725cb14b81f442eb57a38755829270ff2c43
Submitter: Zuul
Branch:    master"
1734320,2019-12-18 13:57:17 UTC,"Aha think I got it, looks like the tag order is wrong:"
1734320,2019-12-18 13:36:14 UTC,"Hi Sean,"
1734320,2019-10-24 13:10:14 UTC,"yes so as i commented before
the issue is here https://review.opendev.org/#/c/640258/15/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_dvr_neutron_agent.py@404
We are not reading the correct field so once we fix that we expect it to work in the dvr case.
that is noted in the Gerrit review. the failures are all cased by the fact we try to read a filed that
does not exist this raise an error and the port does not  become acitve. we the reach the timout on the nova side and role back the vm."
1734320,2019-10-24 12:41:14 UTC,"Copying here my comment on neutron patch https://review.opendev.org/640258/: not sure the failures are related to DVR: it seems we only run full tempest set with dvr enabled (with OVS). Test failures are mostly about VM not becoming ACTIVE (stuck in BUILD), I guess due to neutron VM port not becoming ACTIVE. This should not be affected by DVR in any way. Also in ovs agent logs I see errors on ovs-vsctl operations with ports having ofport -1."
1734320,2019-10-23 01:39:09 UTC,"Reviewed:  https://review.opendev.org/686347
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=797a379c51a05fca356d2f2575bfc386b0287afd
Submitter: Zuul
Branch:    stable/pike"
1734320,2019-10-18 14:33:54 UTC,"Reviewed:  https://review.opendev.org/686346
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9b0919e64809729f4c0186e9be63b1082510bbb1
Submitter: Zuul
Branch:    stable/queens"
1734320,2018-11-08 16:36:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616609"
1734320,2018-11-07 19:59:11 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/609851
Reason: ill backport a seprerate reivew as master has chaged significantly form this version."
1734320,2017-12-07 19:04:17 UTC,(something we discussed with Armando yesterday)
1734320,2018-10-22 23:22:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612534"
1734320,2017-12-02 11:48:23 UTC,"Hi Armando, I'm also impressed by the thorough investigation. Especially the resize insight."
1734320,2017-12-02 06:02:47 UTC,"OK, I finally had some interrupted time in which I could look into this more carefully. the TL;DR summary is: the behavior is exposed in live-migrate/block-migrate/resize operations. That said, I don't believe this vulnerability is serious at least under default conditions. Here's why:"
1734320,2017-11-29 23:45:36 UTC,"Hi Tristan,"
1734320,2018-11-07 19:57:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/616285"
1734320,2017-11-29 17:01:43 UTC,"I used a Pike-based deployment as a testing platform and I can confirm that the resize operation exposes the same behavior as live/block migration (as reported in this report), i.e. the port connected to the VM shows up without a local VLAN tag on the target host."
1734320,2017-11-29 09:03:35 UTC,Agree lets see if we can reproduce without admin credentials.
1734320,2017-11-28 15:12:51 UTC,"That's why I am trying to verify that the resize operation has the same behavior, because if that's the case, the user is very much in control!"
1734320,2017-11-28 14:55:38 UTC,"@Paul, well I tend to agree this is a vulnerability (class A according to the VMT taxonomy: http://security.openstack.org/vmt-process.html#incident-report-taxonomy ). However, since a malicious user can't control the condition of exploitation, other VMT member may disagree with issuing an advisory for this issue."
1734320,2017-12-02 17:23:20 UTC,"I didn't mean that console would be a requirement for the exploit, and indeed I overlooked the two-NICs scenario. Thanks for your feedback...I feared I was missing something ;)"
1734320,2017-11-28 14:54:35 UTC,Block migration would also be affected by the same behavior.
1734320,2017-11-28 05:41:07 UTC,"Thanks Armando for the prompt feedback. I've subscribed nova-coresec to discuss the scope of this vulnerability, in particular the issue #2."
1734320,2017-11-28 05:19:09 UTC,"Today I was looking at this a bit to see if 'resizing' would expose the same behavior, as that is available to regular users. I shall be able to find more time tomorrow to assess what's going on pike and ocata."
1734320,2017-11-28 05:14:01 UTC,"@Tristan: perhaps looping in the nova project is not a bad idea, and yes, you're right that migration can only be performed by an admin according to the default policy.json."
1734320,2017-11-28 05:02:47 UTC,Should we subscribe the Nova project for the issue #2 (Order of creation)?
1734320,2017-11-24 18:49:17 UTC,The other thing that surprised me about this is that there are rules forwarding traffic to the port when it doesn't have a VLAN tag. Is the behavior of the NORMAL action to flood to all untagged ports as if they were trunks carrying all VLANs?
1734320,2017-11-24 17:36:31 UTC,My fear is that this vulnerability might be present on releases newer than Newton.
1734320,2017-11-24 17:31:37 UTC,Looking.
1734320,2017-11-24 13:19:21 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1734320,2017-11-28 08:28:53 UTC,@Tristan: yes nova live-migration is by default an admin only operation. But forcing the port-down can be done by a user aswell. Then it's just waiting for an admin to do a live-migration of a instance. We live-migrate instances regularly to empty a compute node and patch the compute node.
1734320,2017-12-04 12:57:19 UTC,Hardening both locations doesn't fix the issue. It brings the time window back to a couple of seconds.
1734320,2017-11-29 23:27:35 UTC,"Thanks Armando,"
1734320,2017-12-05 22:54:14 UTC,"Ihar, I agree with your assessment, thanks for pushing this forward; I am a bit uneasy about the implications of adding a drop rule for normal actions on br-int for the reasons you've stated (maybe that breaks Tap as a Service or SFC or other stuff?). We should also make sure that the change on the os-vif side will not break things like OVN/ODL or other drivers that rely on OVS because I don't believe there's any local VLAN tagging involved for those. Have you considered these scenarios?"
1734320,2018-10-19 16:30:21 UTC,Note a CVE has been issued for this bug in on 2018-07-27  http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14636
1734320,2018-10-11 23:12:18 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/609851"
1734320,2018-10-11 23:09:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/609850"
1734320,2018-10-10 20:29:34 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: master
Review: https://review.openstack.org/602432
Reason: this should not be needed"
1734320,2018-01-09 22:00:11 UTC,Backporting for neutron seems simple: the patch applies cleanly to stable/ocata which is the oldest version upstream supports.
1734320,2018-01-09 21:47:25 UTC,"In nova, there is also some code in nova/network/linux_net.py (specifically, class LinuxOVSInterfaceDriver) that seems to have plug() method that calls add-port and would benefit from dead tag setting too, but I failed to find a place where this code is hooked into actual services, so I wonder if this code is not some dead end that will be cleaned up in due course after os-vif switch. I will leave it up to nova team to decide."
1734320,2018-01-05 20:32:39 UTC,"This is the neutron piece of the puzzle to make ovs agent mark all untagged ports as dead. I am considering adding a new functional or fullstack test for the scenario too, but posting what I have for now to start review."
1734320,2018-01-05 20:07:36 UTC,"I tried to reach out to Matt (Nova PTL) via email, so far no luck. I think their involvement is crucial here."
1734320,2017-12-05 21:27:49 UTC,I agree with Gerhard on the fact that hardening on neutron side won't completely eliminate the issue in nova/neutron setup. We should also have a fix on os-vif side where we enforce dead tag on newly created ports. AFAIU os-vif may not have been used before recent releases of Nova so the fix may need to be both in os-vif and nova stable branches.
1734320,2017-12-13 17:11:03 UTC,"If the issue is considered widespread, easy enough to exploit and able to do a sufficient amount of damage or obtain sensitive information with some certainty, then we would want to keep this report privately embargoed while fixes are developed, attached to this bug and tested/reviewed locally by the bug's subscribers. Once working fixes for master are identified and backports are created and attached to this bug for all supported stable branches, we will get a CVE identifier assigned, propose a disclosure schedule and provide advance notice and copies of the patches privately to downstream stakeholders."
1734320,2017-12-02 06:40:15 UTC,Thank you Armando for this thorough investigation.
1734320,2017-12-06 07:10:18 UTC,"Thanks, that makes sense."
1734320,2017-12-06 21:11:37 UTC,Thanks to everybody who has helped in diagnosing this issue. It seems we have two sets of actions:
1734320,2017-12-06 21:30:09 UTC,Please subscribe anyone you think may be able to help identify a safe solution.
1734320,2017-12-12 09:26:57 UTC,"[root@primary ~]# ovs-vsctl show
a6b77a09-2647-47d7-8815-ef4d4f689ce8
    Bridge br-int
        fail_mode: secure
        Port ""tap5a27427b-22""
            Interface ""tap5a27427b-22""
        Port br-int
            Interface br-int
                type: internal
        Port ""patch-br-int-to-provnet-d556080a-799f-4621-bb2d-d4ac9b8bb32e""
            Interface ""patch-br-int-to-provnet-d556080a-799f-4621-bb2d-d4ac9b8bb32e""
                type: patch
                options: {peer=""patch-provnet-d556080a-799f-4621-bb2d-d4ac9b8bb32e-to-br-int""}
        Port ""tapa4e1ef4d-40""
            tag: 4095
            Interface ""tapa4e1ef4d-40""
        Port ""tap4b56611b-99""
            tag: 4095
            Interface ""tap4b56611b-99""
        Port ""tap473919fe-31""
            tag: 4095
            Interface ""tap473919fe-31""
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port ""patch-provnet-d556080a-799f-4621-bb2d-d4ac9b8bb32e-to-br-int""
            Interface ""patch-provnet-d556080a-799f-4621-bb2d-d4ac9b8bb32e-to-br-int""
                type: patch
                options: {peer=""patch-br-int-to-provnet-d556080a-799f-4621-bb2d-d4ac9b8bb32e""}
[root@primary ~]# ip netns exec ovnmeta-a4e1ef4d-47ce-4b92-8043-70d88237eff1 ssh cirros@10.0.0.4
cirros@10.0.0.4's password:"
1734320,2017-12-07 18:52:27 UTC,I subscribed Miguel Angel Ajo from networking-ovn team to assess whether proposed os-vif fix would break them.
1734320,2017-12-07 19:05:28 UTC,"This ^ would of course imply that instead of having one/two places to patch (os-vif + maybe neutron), we will have three (neutron -> nova -> os-vif)."
1734320,2017-12-07 21:34:55 UTC,"Hi,"
1734320,2017-12-08 17:29:06 UTC,Miguel: my request from comment #26 definitely applies to you as well. Please subscribe anyone you think may be able to help identify a safe solution.
1734320,2017-12-11 09:39:45 UTC,"Sorry, I didn't know that I had permissions to add more people, I did it with numan, but I will verify now that I'm back from PTO"
1734320,2017-12-13 16:40:25 UTC,"@Tocayo Miguel Ajo,"
1734329,2018-01-12 03:16:15 UTC,"We see this in OpenStack-Helm, and have reverted to MariaDB 10.1 until this is resolved: https://review.openstack.org/#/c/533044/"
1734329,2018-03-13 04:23:02 UTC,"Currently, the version of mariadb in the barbican-dogtag-devstack-functional-fedora-27 is 10.2.12. And there is a bug for this version. That why devstack cannot upgrade Barbican database. The bug was fixed at 10.2.13 [1]. So we just need to wait for fedora27 using this version."
1734329,2018-04-20 03:58:04 UTC,"Reviewed:  https://review.opencontrail.org/42211
Committed: http://github.com/Juniper/openstack-helm/commit/94b2d9580cfaf0efdb2f74e80d3f9f623058dc00
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    R5.0"
1734329,2018-04-20 03:57:32 UTC,"Reviewed:  https://review.opencontrail.org/42067
Committed: http://github.com/Juniper/openstack-helm/commit/dca1f14a130a46d5805aa1d267a2116a589b7db2
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1734329,2018-03-05 08:55:54 UTC,"Created PS:
https://review.openstack.org/#/c/549490/"
1734329,2018-03-03 17:39:51 UTC,Problem disapear in MariaDB 10.2.13.
1734329,2018-01-15 19:16:57 UTC,"I hit this on Jan 15, 2018 with a fresh devstack deployment on Fedora 27."
1734339,2017-12-05 18:17:51 UTC,"For https://bugs.launchpad.net/ubuntu/+source/git/+bug/1729075/comments/5, a 'nopcre2' build profile would be good enough and would follow the spirit of https://wiki.debian.org/BuildProfileSpec#Derivative_specific_profiles."
1734339,2017-12-05 18:16:25 UTC,Example where this would be useful: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1729075/comments/5
1734339,2017-12-05 18:35:53 UTC,"Jonathan, this is kind of a placeholder wishlist bug. If you want this implemented, you'll need to discuss it more broadly (perhaps on the ubuntu-devel/debian-devel mailing lists)."
1734339,2017-12-05 18:37:27 UTC,"ubuntu-devel is moderated to official Ubuntu Developers, so feel free to ping in #ubuntu-devel if you need an email you send there pushed through the moderation queue."
1734346,2018-05-24 11:13:02 UTC,"> it's not necessarily possible for patches-applied import to work
"
1734346,2018-03-06 05:15:16 UTC,"I believe this is the same thing dgit does, but I need to refresh my memory to be sure."
1734346,2018-05-24 11:13:27 UTC,(I realise that this is perhaps contrary to the subject line of this bug)
1734352,2019-12-18 08:44:13 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1734355,2017-11-24 16:43:03 UTC,"StacktraceTop:
 pa_queue_pop (q=<optimized out>) at pulsecore/queue.c:104
 prepare_next_write_item (p=0x7f9a94000bb0) at pulsecore/pstream.c:591
 do_write (p=p@entry=0x7f9a94000bb0) at pulsecore/pstream.c:743
 do_pstream_read_write (p=0x7f9a94000bb0) at pulsecore/pstream.c:247
 dispatch_defer (m=0x7f9ad0042d60) at pulse/mainloop.c:680"
1734371,2017-11-24 18:34:37 UTC,"Reproduced against 7e79017 in an artful VM, with only the following workaround applied. So this affects master and isn't a regression in my feature branch."
1734371,2017-12-04 10:19:19 UTC,Yeah I see this too. Will dig into it.
1734381,2017-11-24 23:55:03 UTC,*** This is an automated message ***
1734388,2017-11-24 22:09:08 UTC,Can you please elaborate on what you mean by accent keys?
1734388,2017-11-25 15:27:05 UTC,"So, specifically, the characters that I can not type are: ~ ^ ` ´ ¨"
1734388,2017-11-28 09:04:31 UTC,"This looks very similar to https://github.com/sergiusens/telegram-snap/issues/4.
I can still reproduce the issue with the telegram snap (version 1.1.23), but I'm not seeing the problem with the libreoffice snap. I wonder why it's affecting libreoffice on your system."
1734388,2017-11-29 01:13:17 UTC,"I use Linux Mint, which, as you may know, relies on Ubuntu 16.04 with x11."
1734388,2017-11-29 01:59:38 UTC,"Hello Mr. Tilloy! I'm Gabriel (the guy who reported the accent bug in
LibreOffice snap version)."
1734391,2019-09-19 11:56:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1734392,2017-11-25 00:21:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1734403,2017-12-05 04:56:17 UTC,Will do. I guess I need to learn how to write bugs in the proper place.
1734403,2017-12-04 21:54:13 UTC,"Bugs in the greeter are tracked in GitHub, please report the issue there: https://github.com/elementary/greeter"
1734410,2018-03-21 11:35:31 UTC,"Next time, please provide some information about what and how was tested when setting verification-done for an update. It is not enough to just set the tag. The SRU team needs to be made aware of what has been tested and how, if the test case was followed as expected. The more verbose the better."
1734410,2017-12-12 10:54:02 UTC,"These did not make v235, I guess you meant v236. Description updated."
1734410,2018-03-20 00:10:17 UTC,@cbrauner
1734410,2018-02-22 18:37:09 UTC,"Hello Christian, or anyone else affected,"
1734410,2018-01-03 19:24:22 UTC,This bug was fixed in the package systemd - 235-3ubuntu3
1734410,2018-02-21 12:58:26 UTC,I'm slightly perplexed if this is needed in xenial or not.
1734410,2020-06-01 16:26:22 UTC,"There is no /sys/fs/cgroup/unified on xenial, closing."
1734410,2018-10-08 15:23:17 UTC,If the systemd version doesn't support hybrid cgroup layout on xenial then fine but I thought it did. But please make sure that Xenial doesn't have anything mounted on /sys/fs/cgroup/unified.
1734410,2018-10-08 15:09:51 UTC,"I'm confused about this backport to xenial, given that xenial's mount-setup.c does not try to neither mount nor use /sys/fs/cgroup/unified."
1734410,2018-03-21 11:56:43 UTC,"Sorry for the brevity before. I tested this with systemd 23{5,6}
inside xenial and artful containers which is really the only case
where it matters."
1734410,2018-03-21 11:43:06 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1734410,2018-03-21 11:42:35 UTC,This bug was fixed in the package systemd - 234-2ubuntu12.3
1734414,2018-01-22 11:35:45 UTC,I confirm. Looks like a regression. Mint 18.3 Cinnamon 64 bit
1734424,2017-11-25 21:16:32 UTC,"Issue solved. I have really no clue to why. I switched to xubuntu, no change. I tried to switch off either monitor, no change. I checked all usb plugs, no change. I moved the mouse transmitter to another port, and then it all worked. I put it back into the old port, everything works. Lets see a few days, it may have been electrical contact."
1734428,2020-06-04 18:13:11 UTC,I was unable to recreate this with a kvm virtual machine on 18.04 or 20.04.
1734428,2017-11-25 09:03:59 UTC,"Checked back a few releases, working ok in xenial, zesty and artful"
1734428,2020-06-04 17:46:14 UTC,Bug 203385 has some comments on it also regarding Ubuntu 18.04.
1734429,2017-11-25 09:15:26 UTC,Here what I wrote
1734430,2017-11-25 15:20:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734430,2018-05-31 08:07:34 UTC,"This bug affects previous Ubuntu releases. To circumvent this issue, choose ""Try Ubuntu"", add a terminal and unmount /isodevice
sudo umount -lfd /isodevice"
1734430,2018-05-31 08:10:47 UTC,"In my previous post, change ""add a terminal"" by ""open a terminal"""
1734435,2020-09-11 10:23:35 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1734441,2017-11-25 15:22:04 UTC,"Of course, do not use static_cast instead! I never suggested that."
1734441,2019-09-17 10:25:01 UTC,Migrated to https://github.com/widelands/widelands/issues/3233
1734441,2017-11-25 18:52:45 UTC,:thumbsup: agreed! Just wanted to make sure that we are on the same page.
1734441,2017-11-25 13:38:36 UTC,That is a bit misleading and potentially dangerous.
1734445,2017-11-27 15:56:49 UTC,"It seems to me that this Ubuntu-specific direction be moved out of the vanilla admin guide entirely , and if it were still relevant to Ubuntu's horizon packaging that it be documented on Ubuntu's site."
1734447,2017-11-26 17:03:37 UTC,"This also affects BN_mod_add(-0, -0, 10) (result should be 0, but is 10)"
1734452,2018-04-23 09:49:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734452,2018-06-08 03:56:26 UTC,The issue got after upgrading nvidia-384 to nvidia-390
1734452,2018-04-23 09:50:35 UTC,"i can see only prime profiles, application profiles and nvidia-settings configuration. This is happening in ubuntu 16.04"
1734456,2017-11-27 17:58:00 UTC,"Thanks for the clarification. I can confirm that the circular handles of a circle do not snap in Inkscape 0.92.2, even when all snap buttons have been activated."
1734456,2017-11-27 00:47:43 UTC,I think what you mean is that you cannot snap the circular handles that can be used to determine the opening angle of the circle segment / arc ?
1734456,2017-11-27 16:41:00 UTC,"Excuse me, yes, I mean the opening and closing points of a segment, arch, full circle or ellipse.
As may be derived from the attached image, there are cases where the ability to snap the radius of a circle in other directions than left or up, can be instrumental to the creation of an object."
1734456,2017-11-27 16:53:54 UTC,"I edited the description, for clarity, and to add a mention that the ability to snap is also missing when rotating the start and end points around the center point."
1734456,2018-01-01 20:23:59 UTC,Located mentions of the same issue / missing feature from 2012:
1734456,2020-09-11 14:43:03 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1734462,2017-12-06 11:10:21 UTC,It looks like it's a missing dependency. If you install ruby-cairo-gobject then it works.
1734463,2019-04-22 02:58:07 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
Thanks"
1734463,2019-06-21 04:17:28 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1734467,2017-11-25 18:56:45 UTC,upstream debian python3-sha3 is not broken in this way :
1734467,2018-02-20 17:15:58 UTC,"with python3-sha3 update now in bionic, this is resolved in bionic at least."
1734472,2017-11-25 19:41:02 UTC,"StacktraceTop:
 do_syscall_WRK ()
 vgPlain_do_syscall (sysno=sysno@entry=62, a1=<optimized out>, a2=a2@entry=5, a3=a3@entry=0, a4=a4@entry=0, a5=a5@entry=0, a6=0, a7=0, a8=0) at m_syscall.c:931
 vgPlain_kill (pid=<optimized out>, signo=signo@entry=5) at m_libcsignal.c:350
 vgPlain_kill_self (sigNo=5) at m_signals.c:1572
 shutdown_actions_NORETURN (tid=1, tids_schedretcode=VgSrc_FatalSig) at m_main.c:2207"
1734473,2018-07-13 10:18:50 UTC,"I have the same issue on Ubuntu Mate 18.04, but Super + L is working."
1734473,2020-05-22 04:17:43 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1734474,2020-11-09 22:46:02 UTC,"This change on current head-of-git, which is effectively just reverting the logic-change part of commit cb5ef3fa1871522a08, is sufficient to allow the n800 image to boot again.
But that commit was trying to fix a bug, so we probably need to look more carefully at the logic rather than just reverting it..."
1734474,2017-11-25 20:48:39 UTC,UPD: Maemo will boot on the second attempt if I reset the emulator manually.
1734474,2017-11-25 22:03:03 UTC,"That's a regression, but unfortunately the n800 boards aren't really maintained (I don't have any test images to hand, and the hardware is long-gone these days). You could try a git bisect to see what commit broke, if you want to investigate."
1734474,2020-11-05 13:17:56 UTC,"Oops, I should have asked for the image to reproduce with back in 2017 when this bug was first filed :-(  I don't suppose you still have it ?"
1734474,2020-11-10 15:13:15 UTC,"Should be fixed by this patch series:
https://<email address hidden>/"
1734474,2020-11-09 22:32:06 UTC,Bisection thinks commit cb5ef3fa1871522a08 is the cause.
1734474,2020-11-09 22:01:45 UTC,Thanks. I can confirm that there's been a regression since 1.2.0 that's still not fixed in master.
1734474,2020-11-09 20:08:34 UTC,It's available here: https://4pda.ru/forum/index.php?showtopic=870847
1734477,2018-01-09 01:52:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734481,2017-11-25 20:57:39 UTC,"(screenshot was taken in Inkscape 0.92+devel (b071ae7561, 2017-11-25) on Windows 10 but I doubt it matters)"
1734481,2020-09-14 06:04:38 UTC,Closing because INVALID.
1734481,2020-09-17 20:21:43 UTC,This issue was about something else - please be careful when closing issues.
1734484,2017-11-26 00:20:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1734489,2018-01-08 18:05:07 UTC,"If the translation I get from google is correct, this is not related to chromium-browser:"
1734490,2017-11-26 19:38:42 UTC,"[    4.710462] WARNING: CPU: 1 PID: 168 at /build/linux-2JtliJ/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915]
[    4.710466] Modules linked in: i915(+) psmouse ahci r8169 i2c_algo_bit libahci drm_kms_helper pata_acpi ssb syscopyarea sysfillrect sysimgblt mii fb_sys_fops drm video
[    4.710508] CPU: 1 PID: 168 Comm: systemd-udevd Not tainted 4.13.0-17-generic #20-Ubuntu
[    4.710518] Hardware name: LENOVO 2957                            /Mariana2, BIOS 1ACN16WW(V1.07) 06/05/2009
[    4.710526] task: f61b2700 task.stack: f63fc000
[    4.710698] EIP: assert_planes_disabled+0x128/0x140 [i915]
[    4.710703] EFLAGS: 00010296 CPU: 1
[    4.710707] EAX: 00000046 EBX: f4d54000 ECX: 000002c2 EDX: 00000000
[    4.710712] ESI: 00000001 EDI: 00000001 EBP: f63fdbac ESP: f63fdb90
[    4.710716]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[    4.710721] CR0: 80050033 CR2: bfbba8fc CR3: 34c1eac0 CR4: 000006f0
[    4.710725] Call Trace:
[    4.710904]  intel_disable_pipe+0x45/0x220 [i915]
[    4.711081]  i9xx_crtc_disable+0x68/0x3c0 [i915]
[    4.711146]  ? drm_connector_list_iter_next+0x71/0xa0 [drm]
[    4.711201]  ? drm_atomic_add_affected_connectors+0xe8/0x100 [drm]
[    4.711377]  intel_crtc_disable_noatomic+0xb5/0x2a0 [i915]
[    4.711548]  ? intel_modeset_setup_hw_state+0xa31/0xc30 [i915]
[    4.711720]  intel_modeset_setup_hw_state+0xa5e/0xc30 [i915]
[    4.711895]  intel_modeset_init+0x4d1/0xe90 [i915]
[    4.712057]  ? intel_i2c_reset+0x3b/0x50 [i915]
[    4.712279]  ? intel_setup_gmbus+0x1e1/0x270 [i915]
[    4.712450]  i915_driver_load+0xa66/0x12d0 [i915]
[    4.712470]  ? acpi_dev_found+0x6c/0x80
[    4.712631]  i915_pci_probe+0x3a/0x70 [i915]
[    4.712652]  pci_device_probe+0xc2/0x160
[    4.712668]  driver_probe_device+0x2b9/0x410
[    4.712679]  __driver_attach+0x99/0xe0
[    4.712690]  ? driver_probe_device+0x410/0x410
[    4.712700]  bus_for_each_dev+0x57/0x90
[    4.712711]  driver_attach+0x19/0x20
[    4.712720]  ? driver_probe_device+0x410/0x410
[    4.712730]  bus_add_driver+0x187/0x230
[    4.712739]  ? 0xf8ca3000
[    4.712750]  driver_register+0x56/0xd0
[    4.712758]  ? 0xf8ca3000
[    4.712768]  __pci_register_driver+0x33/0x40
[    4.712939]  i915_init+0x4c/0x51 [i915]
[    4.712963]  do_one_initcall+0x46/0x180
[    4.712977]  ? kvfree+0x45/0x50
[    4.712987]  ? kmem_cache_alloc_trace+0x13d/0x1a0
[    4.712996]  ? do_init_module+0x21/0x1cc
[    4.713006]  ? do_init_module+0x21/0x1cc
[    4.713017]  do_init_module+0x50/0x1cc
[    4.713027]  load_module+0x1533/0x1aa0
[    4.713042]  ? kernel_read_file+0x26e/0x2a0
[    4.713057]  SyS_finit_module+0x8a/0xe0
[    4.713072]  do_fast_syscall_32+0x71/0x150
[    4.713086]  entry_SYSENTER_32+0x4e/0x7c
[    4.713094] EIP: 0xb7fbacf9
[    4.713097] EFLAGS: 00000296 CPU: 1
[    4.713102] EAX: ffffffda EBX: 00000012 ECX: b7db3a71 EDX: 00000000
[    4.713107] ESI: 0197fc70 EDI: 019713e0 EBP: 00000000 ESP: bfbc1e9c
[    4.713112]  DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b
[    4.713118] Code: ff 83 c4 10 e9 44 ff ff ff 57 68 e8 80 c5 f8 e8 6c 14 52 d3 0f ff 58 5a e9 30 ff ff ff ff 75 f0 50 68 20 81 c5 f8 e8 55 14 52 d3 <0f> ff 83 c4 0c e9 3..."
1734490,2017-11-25 23:00:08 UTC,This change was made by a bot.
1734490,2017-11-25 22:57:39 UTC,Booting with 'nomodeset' allows system to boot into graphics mode.
1734490,2017-11-26 19:39:37 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=102929
1734490,2017-11-29 15:57:25 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1734492,2017-11-25 23:02:51 UTC,Would be nice to have a open file dialog box to upload local Snaps and also a URL box to do remote download.
1734493,2017-11-26 18:03:14 UTC,Can we tell Qt to render translated strings without having the layout reversed?
1734493,2017-11-26 19:20:58 UTC,"Yes, since QT 4.7 it is independent from the string directions:
http://doc.qt.io/qt-4.8/qwidget.html#layoutDirection-prop"
1734496,2017-12-12 14:49:35 UTC,"Interesting... I still can't easily test right now, but if you try to mount the device manually, possibly from an live disk (`mount /dev/sdXX /path`), does the right subvol get mounted?"
1734496,2017-11-26 03:03:18 UTC,So I think I know why this doesn't work under Ubuntu and it's related to the mount options Ubuntu sets by default for btrfs for a new installation.
1734496,2017-12-12 14:23:42 UTC,"I tested your workaround with Ubuntu 16.04 with no luck.
1- remove subvol=@
2- also add the same root ID with
UUID=ce4d5d13-5ec7-4b2f-b519-569e04729d1e /.snapshots     btrfs   subvol=@/.snapshots 0       1
as OpenSuSE fstab.
3- btrfs subvolume set-default (SNAP NUMBER) /
any help? I need to rollback as easy to do in OpenSuSE."
1734496,2018-02-15 19:01:37 UTC,"I think I have found a way but it is more of a hack. When I remove:
rootflags=subvol=${rootsubvol}
from the line GRUB_CMDLINE_LINUX=""rootflags=subvol=${rootsubvol} ${GRUB_CMDLINE_LINUX}"" in the file /etc/grub.d/10_linux I can boot from the rw snapshot snapper makes when I issue the command:
sudo snapper rollback 38
You will have to do an update-grub before the snapper rollback command to write the new cfg file.
This method will most likely fail if an update replaces the 10_linux file and I don't know how safe it is considering it is not officially supported."
1734496,2018-05-18 07:50:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734499,2017-11-26 11:19:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734499,2017-11-30 12:33:06 UTC,"Got the same error but in my case the backup had already been running for a while when suddenly a window was shown:
Backup Failed
InvalidBackendURL: missing // - relative paths not supported for scheme invalid: invalid://"
1734499,2018-01-19 16:13:11 UTC,"This should be ""fixed again"" in 37.1-0ubuntu1, see bug #1715582."
1734499,2018-04-23 14:52:01 UTC,I still have this problem in Ubuntu 18.04 (with the backup I made on 17.10 (if I recall correctly)).
1734499,2019-05-02 21:53:51 UTC,"In which case the fix is not relevant for this bug, since I was backing up to a USB stick, not a server?
I can't reproduce this bug now because I did a new full backup to workaround the problem, but it seems  other people are affected in any case, so perhaps someone affected could provide more details about this bug if I can't."
1734499,2019-04-29 18:14:45 UTC,Hello Ads2000.
1734499,2018-04-30 19:02:49 UTC,Removing the bug this was marked a dupe of ( bug 1715582 ) because I still have this issue on 18.04 (albeit without the 'gio+' prefixes in the title.
1734500,2018-08-12 17:06:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734500,2017-11-29 21:23:06 UTC,Anyone with a dual monitor setup (regardless of whether either monitor is physically rotated) should be able to test if they observe this problem after setting one monitor rotate-setting to Clockwise.  I don't know whether it can be observed on a single-monitor system.
1734501,2021-01-10 23:49:12 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1734504,2017-11-28 19:34:00 UTC,"Even if we stored the flavorid in the migrations table and returned that out of the migrations API, the flavorid doesn't tell you much - and the flavor for that flavorid might be deleted for really old migration records. This is why we did microversion 2.47 https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id42 where the full embedded flavor is returned for the GET /servers/detail response, and I'm not advocating that we store the full flavor information in the migrations table."
1734504,2017-11-28 19:15:39 UTC,"The problem isn't in novaclient, it's in the server code that creates the migration record. It's recording the old/new instance type ids using the internal primary keys for the flavor, rather than the flavorid which is the user-facing id for a flavor:"
1734504,2017-11-28 01:37:24 UTC,"nova migration-list return flavorid instead of instance_type_id.
I will upload a patch set to fix it."
1734504,2017-11-28 19:20:25 UTC,"From what I can see, nothing else in the code relies on the migration.old/new_instance_type_id fields, only the REST API, so we store the entirely wrong thing and return it out of the REST API."
1734504,2017-11-28 19:23:15 UTC,"We probably can't get the old/new flavor information off the instance either, because the migration.instance_uuid record points at an instance but the old/new flavor in that instance might no longer match that specific migration record, e.g. if I have resized an instance twice, from flavor A->B and then flavor B->C, there would be 2 migration records pointing at the same instance but the first migration can't get the old/new flavors off the instance because the current old/new flavors on the instance record are B/C, not A/B."
1734504,2018-02-05 02:26:54 UTC,"I would like to fix this question.
Do I need to submit a blueprint first?"
1734504,2017-12-11 02:05:19 UTC,Yea，I got it. I will advise operation and maintenance personnels to obtain resize flavor by ceilometer.
1734504,2017-11-29 09:02:59 UTC,Nova emits instance.resize notifications with full flavor information[1]. So an external system listening to those notifications can create a history of resizes. The instance.resize.start is emitted with the original flavor and the instance.resize_finish.end is emitted with the new flavor information.
1734504,2017-11-29 05:35:17 UTC,"If we pull the old/new_instance_type fields out from the response, what channels do users get one old/new flavor inforation for an special resize operation?"
1734504,2017-11-29 05:29:42 UTC,"As far as I am concerned, operation and maintenance personnel always use ""nova migration-list"" to look for information of resize failure."
1734508,2018-06-19 10:58:00 UTC,"This was fixed by this commit, as the api_handler is only started after the graph is ready:"
1734513,2018-02-15 23:38:43 UTC,Most likely the same as bug 1718238 / https://gitlab.gnome.org/GNOME/mutter/issues/23 .
1734515,2018-04-16 12:42:39 UTC,"This isn't working for me.  I disabled this module:
### Should be after module-*-restore but before module-*-detect
# load-module module-switch-on-port-available
from the /etc/pulse/default.pa"
1734515,2017-11-26 12:23:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1734515,2018-04-16 12:46:09 UTC,"If I knew exactly which package this applied to, I'd be more than happy to file a bug.  The problem is I have no idea, and all my searches turn up the same thing.  Nothing specific.  Just like this one, he ""disabled the module"", which module?  He also disabled it in ""/etc/pulseaudio/default.pa"" I don't have a ""/etc/pulseaudio"" directory, it's just ""/etc/pulse""  I'm not sure which package is causing this, and I would just like to know how to fix it.
If you could direct me to the proper package, and/or bug already submitted I'll be glad to go there."
1734520,2019-02-22 12:06:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734527,2019-07-07 04:17:22 UTC,[Expired for juju because there has been no activity for 60 days.]
1734527,2019-05-07 10:47:28 UTC,Could you please verify if the performance kill-controller is better on 2.6?
1734540,2017-11-26 16:00:04 UTC,This change was made by a bot.
1734541,2020-06-19 05:08:58 UTC,See for workaround:
1734541,2018-05-25 17:07:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734541,2020-08-13 05:34:48 UTC,Note this was also reported in bug 1637710 back in 2016
1734541,2018-05-25 17:08:25 UTC,I confirm this issue is affecting me too.
1734541,2018-05-25 17:15:42 UTC,"Sorry, this are my system specs:"
1734541,2018-06-10 05:12:57 UTC,"Ich bin ebenfalls davon betroffen.
I confirm this issue is affecting me too."
1734541,2019-01-08 16:34:36 UTC,Still happens with Ubuntu LTS 18.04. I can provide additional info if needed.
1734541,2019-02-12 11:50:04 UTC,"The bug seems to be present in 16.04.5, too."
1734541,2020-04-13 09:38:04 UTC,"Still an issue as of today 2020-04-13, for Ubuntu 18.04."
1734541,2020-04-13 09:39:15 UTC,"Also don't rely on the ""affects me"" counter above, as for non-power-users this bug is subtle and undetectable in most cases, leaving them unsafe without knowledge."
1734548,2017-11-30 14:25:42 UTC,I can confirm that.
1734564,2017-12-03 20:47:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734568,2019-04-17 19:23:19 UTC,wpa still has a build-dependency on android-headers.
1734568,2017-12-11 22:11:49 UTC,Would you consider adding src:android to this list as well?
1734568,2017-12-11 22:19:32 UTC,"Will, can you confirm whether these removals are wanted?"
1734568,2017-12-12 12:34:46 UTC,"+1 to remove.
Checked with folk who know more about the Android side of things, and they're OK for these to get removed as well."
1734568,2019-01-04 14:44:22 UTC,"Julian, could you look into dropping the android-headers stuff from the wpa package?"
1734568,2019-09-04 16:39:24 UTC,"Removing packages from eoan:
 android-headers 23-0ubuntu4 in eoan
  android-headers 23-0ubuntu4 in eoan amd64
  android-headers 23-0ubuntu4 in eoan arm64
  android-headers 23-0ubuntu4 in eoan armhf
  android-headers 23-0ubuntu4 in eoan i386
  android-headers 23-0ubuntu4 in eoan ppc64el
  android-headers 23-0ubuntu4 in eoan s390x
  android-headers-19 23-0ubuntu4 in eoan amd64
  android-headers-19 23-0ubuntu4 in eoan arm64
  android-headers-19 23-0ubuntu4 in eoan armhf
  android-headers-19 23-0ubuntu4 in eoan i386
  android-headers-19 23-0ubuntu4 in eoan ppc64el
  android-headers-19 23-0ubuntu4 in eoan s390x
  android-headers-21 23-0ubuntu4 in eoan amd64
  android-headers-21 23-0ubuntu4 in eoan arm64
  android-headers-21 23-0ubuntu4 in eoan armhf
  android-headers-21 23-0ubuntu4 in eoan i386
  android-headers-21 23-0ubuntu4 in eoan ppc64el
  android-headers-21 23-0ubuntu4 in eoan s390x
  android-headers-22 23-0ubuntu4 in eoan amd64
  android-headers-22 23-0ubuntu4 in eoan arm64
  android-headers-22 23-0ubuntu4 in eoan armhf
  android-headers-22 23-0ubuntu4 in eoan i386
  android-headers-22 23-0ubuntu4 in eoan ppc64el
  android-headers-22 23-0ubuntu4 in eoan s390x
  android-headers-23 23-0ubuntu4 in eoan amd64
  android-headers-23 23-0ubuntu4 in eoan arm64
  android-headers-23 23-0ubuntu4 in eoan armhf
  android-headers-23 23-0ubuntu4 in eoan i386
  android-headers-23 23-0ubuntu4 in eoan ppc64el
  android-headers-23 23-0ubuntu4 in eoan s390x
Comment: Ubuntu-specific, unmaintained and unused; LP: #1734568
1 package successfully removed."
1734568,2019-01-09 18:14:17 UTC,This bug was fixed in the package wpa - 2:2.6-21ubuntu1
1734568,2019-09-04 16:38:44 UTC,The wpa build-dependency is gone now.
1734568,2019-04-17 19:25:34 UTC,"Removing packages from disco:
 android-src-vendor 7-0ubuntu1 in disco
  android-src-vendor 7-0ubuntu1 in disco amd64
  android-src-vendor 7-0ubuntu1 in disco arm64
  android-src-vendor 7-0ubuntu1 in disco armhf
  android-src-vendor 7-0ubuntu1 in disco i386
  android-src-vendor 7-0ubuntu1 in disco ppc64el
  android-src-vendor 7-0ubuntu1 in disco s390x
Comment: Ubuntu-specific, no uploads since 2014, unmaintained; LP: #1734568
1 package successfully removed."
1734568,2019-04-17 19:21:24 UTC,"Removing packages from disco:
 android-audiosystem 1.8+13.10.20130807-0ubuntu1 in disco
  libandroid-audiosystem-asound2 1.8+13.10.20130807-0ubuntu1 in disco armhf
  libandroid-audiosystem-asound2 1.8+13.10.20130807-0ubuntu1 in disco i386
  libwaudio1 1.8+13.10.20130807-0ubuntu1 in disco armhf
  libwaudio1 1.8+13.10.20130807-0ubuntu1 in disco i386
  libwaudio1-dev 1.8+13.10.20130807-0ubuntu1 in disco armhf
  libwaudio1-dev 1.8+13.10.20130807-0ubuntu1 in disco i386
Comment: Ubuntu-specific, no uploads since 2013, unmaintained; LP: #1734568
1 package successfully removed."
1734569,2017-12-07 06:35:19 UTC,"Wow, interesting! I find it slightly surprising that I can't recall any real world bug caused by this potential issue, but your reasoning makes sense to me. I guess hardware with enough PCI stuff may be uncommon, or non-existing at all."
1734571,2017-12-20 12:42:19 UTC,"I regret that we can't help you with this. Open Rails cannot recover from a missing ""track node"" and the route *.trk file must be repaired."
1734571,2017-12-20 12:39:19 UTC,I have edited your title to remove the extra information.
1734571,2017-12-20 12:38:18 UTC,"Please do not put all that information in the title. It's impossible to read and spams the main bug list. You've already attached the log below, it doesn't need to be in two places."
1734585,2017-11-27 22:11:33 UTC,Can you create a patch in the neutron repo for this?  The file is at ./doc/source/install/environment-networking-controller-ubuntu.rst
1734585,2017-11-27 22:38:40 UTC,"BTW, 17.10 still has ifup/ifdown, so this is more of an optional configuration method."
1734592,2017-11-27 04:28:49 UTC,"   +------------------------------------------------------------------------------------------------------------------------------------+
  >|0x42ad90        vmov.i32       d16, #0 ; 0x00000000                                                                                 |
   |0x42ad94        str    r2, [r1, #8]                                                                                                 |
   |0x42ad98        str    r2, [r1, #12]                                                                                                |
   |0x42ad9c        str    r2, [r3, #2000] ; 0x7d0                                                                                      |
   |0x42ada0        str    r2, [r3, #-2120]        ; 0xfffff7b8                                                                         |
   |0x42ada4        mov    r12, #1                                                                                                      |
   |0x42ada8        vstr   d16, [r0, #-8]                                                                                               |
   |0x42adac        b      0x42a54c                                                                                                     |
   |0x42adb0        add    r7, r7, #12288  ; 0x3000                                                                                     |
   |0x42adb4        add    r4, sp, #8                                                                                                   |
   |0x42adb8        ldrb   r3, [r7, #356]  ; 0x164                                                                                      |
   |0x42adbc        mov    r1, #0                                                                                                       |
   |0x42adc0        mov    r0, #1                                                                                                       |
   |0x42adc4        strb   r3, [r4, #-5]!                                                                                               |
   |0x42adc8        bl     0x42df90                                                                                                     |
   |0x42adcc        mov    r1, r4                                                                                                       |
   |0x42add0        mov    r0, #2                                                                                                       |
   |0x42add4        bl     0x42df90                                                                                                     |
   |0x42add8        mov    r12, #1                                                                                                      |
   |0x42addc        b      0x42a54c                                                                                                     |
   |0x42ade0        ldr    r3, [pc, #1184] ; 0x42b288                                                                                   |
   |0x42ade4        add    r3, pc, r3                                                                                                   |
   +------------------..."
1734592,2017-11-27 14:47:16 UTC,Possibly due to this --enable-neon in debian/rules?
1734592,2017-11-27 13:11:29 UTC,"retroarch:
  Installed: 1.3.6+dfsg1-1
  Candidate: 1.3.6+dfsg1-1
  Version table:
 *** 1.3.6+dfsg1-1 500
        500 http://mirrordirector.raspbian.org/raspbian stretch/main
armhf Packages
        100 /var/lib/dpkg/status"
1734592,2017-11-27 12:35:26 UTC,vmov is determinately a vfp instruction.
1734592,2017-11-27 04:35:00 UTC,I'm not OP but I looked in to this with OP on IRC :)
1734592,2017-11-27 04:32:38 UTC,"Attribute Section: aeabi
File Attributes
  Tag_CPU_name: ""6""
  Tag_CPU_arch: v6
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-1
  Tag_FP_arch: VFPv3
  Tag_Advanced_SIMD_arch: NEONv1
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_rounding: Needed
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_enum_size: int
  Tag_ABI_VFP_args: VFP registers
  Tag_CPU_unaligned_access: v6"
1734592,2017-11-30 19:49:18 UTC,"I just had a chat with the retroarch guys on IRC, unfortunately it seems they do not have a mailling list."
1734592,2017-12-03 03:10:32 UTC,The new package returns the following error on my machine:
1734592,2017-11-27 13:12:36 UTC,"retroarch:
  Installed: 1.3.6+dfsg1-1
  Candidate: 1.3.6+dfsg1-1
  Version table:
 *** 1.3.6+dfsg1-1 500
        500 http://mirrordirector.raspbian.org/raspbian stretch/main armhf Packages
        100 /var/lib/dpkg/status"
1734594,2018-01-16 02:24:11 UTC,My Feitian USB token also stopped working with the same error as the OP after the upgrade to artful.
1734594,2017-12-19 20:58:04 UTC,I am having the same issue with opensc 0.17.0-1 package and Feitian ePass2003 token. I compiled an old version (OpenSC 0.15.0) for temporary use for now.
1734594,2018-06-17 00:56:38 UTC,Upstream issue (fixes were merged): https://github.com/OpenSC/OpenSC/issues/1073
1734597,2018-11-09 08:12:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734597,2018-11-09 10:58:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1734598,2017-11-27 04:30:57 UTC,"On the analytics docker I also see:
root@sspt-ubuntu6-vm7(analytics):/# contrail-status
== Contrail Analytics ==
contrail-alarm-gen            initializing (ApiServer:Config[Config sync failed] connection down)
contrail-analytics-api        active
contrail-analytics-nodemgr    active
contrail-collector            active
contrail-query-engine         active
contrail-snmp-collector       active
contrail-topology             active"
1734598,2017-11-27 10:23:37 UTC,"I am not sure if 1734598 impacts functionality needed by CSO, as it relates to only monitoring of contrail services."
1734601,2019-10-01 15:10:28 UTC,We found the bugfix:
1734601,2018-03-23 09:46:00 UTC,Reproduced on stable/pike deployment
1734601,2019-02-11 08:47:21 UTC,"same here on queens
Versions:
designate 6.0.1
horizon 13.0.1"
1734601,2019-10-11 14:00:48 UTC,"Bug fixed in upstream:
https://review.opendev.org/#/c/687519/
https://github.com/openstack/designate-dashboard/commit/a0582cfc5e2a7904204f83f9f8f7c5579c149ecf"
1734602,2017-12-04 22:09:25 UTC,This issue was fixed in the openstack/puppet-cinder 12.1.0 release.
1734602,2019-05-16 23:02:59 UTC,This issue was fixed in the openstack/puppet-cinder 11.6.0 release.
1734602,2017-11-27 06:20:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523024"
1734602,2018-03-08 16:59:47 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/550924"
1734602,2017-11-30 18:32:49 UTC,"Reviewed:  https://review.openstack.org/523024
Committed: https://git.openstack.org/cgit/openstack/puppet-cinder/commit/?id=88322e25d9adca56fdeac2d6ff3724b982f7c06b
Submitter: Zuul
Branch:    master"
1734602,2018-03-12 08:58:26 UTC,"Reviewed:  https://review.openstack.org/550924
Committed: https://git.openstack.org/cgit/openstack/puppet-cinder/commit/?id=8265644242bb1986746187d38f644a4327b84cc9
Submitter: Zuul
Branch:    stable/pike"
1734606,2017-11-27 15:09:24 UTC,"use kolla ocata  (centos-source) install .
the sahara services are on the same node of the mysql/mariadb server."
1734606,2017-11-27 14:38:38 UTC,"I think it's a question about the performance of the database,
Because when I created 20 nodes, it' successful, but created 30 nodes, failed.
there is no specific description of the environment and configuration."
1734606,2017-11-27 10:16:01 UTC,"Can you please share more details about the environment? Please specify:
- how the environment was configured (apparently kolla is involved, but it is not clear exactly how)
- which version (master?)
- the information about the cluster that it's being created"
1734610,2021-01-28 14:53:18 UTC,"Hi, have you tried the daily PPA? https://code.launchpad.net/~dnax88/+archive/ubuntu/gweled"
1734610,2021-01-28 14:54:03 UTC,Probabily it's a duplicate of bug #1850082
1734619,2017-11-27 19:18:49 UTC,Crash seems to be due to failed assert in bool cass::cql::CqlIfImpl::IsTableStatic() at cql_if.cc:2009 as checked from ubuntu-build02. Can you please investigate further. Thanks
1734619,2017-11-28 03:42:43 UTC,"Cassandra was down at the time of crash due to some provisioning issue hence the accesses to db were failing. I think, contrail-control is expected to restart in such cases?"
1734624,2018-06-01 15:17:54 UTC,"I would like that very, very much, Jan! It would help people understand what's going wrong."
1734624,2018-06-04 20:52:17 UTC,"I implemented a first try for the more detailed error message, see"
1734624,2018-06-01 23:31:29 UTC,"Whoah, that's a lot of investigation that you've done there (and even on different systems, that's awesome :) )"
1734624,2018-06-01 23:01:44 UTC,"OK, I will implement it."
1734624,2018-06-01 05:05:08 UTC,I did so in TexText:
1734624,2018-06-01 05:09:29 UTC,Forget the post above! (How can I delete /edit it?)
1734624,2018-05-31 22:15:07 UTC,"Jan, can you clarify which versions exactly are incompatible?"
1734624,2017-11-28 13:27:53 UTC,"just some further info:
problem not reproduced on Windows XP, Inkscape 0.92.2 (unknown), built on Aug 23, 2017."
1734624,2017-11-28 11:40:23 UTC,Closing...
1734624,2017-11-28 11:39:43 UTC,Thank you for the help.
1734624,2017-11-28 10:29:38 UTC,"Sorry, typo above (and I still hate launchpad for not being able to edit posts):
-> compatibility issue of pstoedit with newer versions of *GHOSTSCRIPT*"
1734624,2018-05-31 22:18:04 UTC,We could add the info to the error message in Inkscape's Render/LaTeX extension (which could check for the versions).
1734624,2017-11-28 08:09:19 UTC,"One more piece of information: I have removed the two files from ~/.config/inkscape/extensions/ and tried: Extensions -> Render -> Latex ... In the dialog box I wrote $1$ and clicked Ok. This yielded the following error:
=========================================================================
 *** WARNING - the DELAYBIND command has been deprecated, and will be"
1734624,2017-11-28 06:46:23 UTC,Thank you. Will do.
1734624,2017-11-28 10:28:37 UTC,"I'd say this is a compatibility issue of pstoedit with newer versions of Python as the warning messages try to explain:
- ghostscript has deprecated (or rather) removed the DELAYBIND command
- pstoedit uses said DELAYBIND command when calling ghostscript"
1734624,2017-11-27 12:59:36 UTC,Thank you for the quick reply.
1734624,2018-05-30 00:47:53 UTC,This issue regains relevancy for Inkscape again due to Ubuntu 18.04 shipping with an incompatible ghostscript/pstoedit version.
1734624,2018-05-30 01:07:43 UTC,"Forum discussion:
https://forum.inkscapecommunity.com/index.php?topic=1163.0"
1734624,2018-05-30 19:58:04 UTC,"For the TexText extension, someone has taken up development again. I've linked them to this report - and now I'll link the report back to them:
https://inkscape.org/en/~jcwinkler/%E2%98%85textext?c=1807"
1734624,2018-05-31 16:38:49 UTC,Because of this ghostscript+pstoedit incompatibility I implemented the pdf2svg backend in TexText.
1734624,2017-11-27 12:15:31 UTC,"- thank you for submitting this report.
- as far as I can tell, the files textext.py and textext.inx are not part of the standard Inkscape installation. Could you indicate where you got these files, or could you attach them for testing purposes?
- also, have you ever been able to successfully run this extension on earlier versions of Inkscape (which version)?"
1734624,2017-11-27 13:26:39 UTC,thanks for the files. I was not able to reproduce the problem since I do not have the appropriate software installed. The best I could do is the error message below.
1734625,2018-04-20 13:14:41 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1734625,2018-04-02 13:09:02 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1734625,2018-03-29 03:31:27 UTC,"Reviewed:  https://review.openstack.org/543116
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d49a6b8999c4b4986ea0ac0ce9f1dca2c076ee17
Submitter: Zuul
Branch:    stable/queens"
1734625,2018-03-06 15:58:24 UTC,"Reviewed:  https://review.openstack.org/543113
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=852de1ee7302bbc818a01510d72b6bafddea4cbe
Submitter: Zuul
Branch:    stable/queens"
1734625,2018-02-10 15:23:41 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/543116"
1734625,2018-02-10 14:55:09 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/543113"
1734625,2018-02-10 14:35:36 UTC,"Reviewed:  https://review.openstack.org/531280
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f66bd7369a86b1833cd146de67c4337ea150f087
Submitter: Zuul
Branch:    master"
1734625,2018-02-07 05:30:20 UTC,"Reviewed:  https://review.openstack.org/531266
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cf375d2ef3fe1d98369714413f3fff692a6f7201
Submitter: Zuul
Branch:    master"
1734625,2017-12-04 15:04:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525231"
1734625,2017-12-07 03:54:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526263"
1734625,2017-12-08 00:37:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526557"
1734625,2017-12-09 06:27:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526823"
1734625,2017-12-28 00:17:57 UTC,"Reviewed:  https://review.openstack.org/525231
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c647865bf6d0c7048d5414564161f6303e7bc5ae
Submitter: Zuul
Branch:    master"
1734625,2018-01-04 22:48:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531258"
1734625,2018-02-10 14:37:22 UTC,"Reviewed:  https://review.openstack.org/531299
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ab4efbba61fb0dd0266e42e48555f80ddde72efd
Submitter: Zuul
Branch:    master"
1734625,2018-01-05 00:01:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531266"
1734625,2018-01-05 06:11:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531299"
1734625,2018-01-17 06:59:49 UTC,"Reviewed:  https://review.openstack.org/526263
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0cbe9b23332155da7fab826077352b4adac483b6
Submitter: Zuul
Branch:    master"
1734625,2018-01-31 00:29:52 UTC,"Reviewed:  https://review.openstack.org/526557
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a326b03339123d79e71edfaca3215def3756b9ae
Submitter: Zuul
Branch:    master"
1734625,2018-02-06 04:05:47 UTC,"Reviewed:  https://review.openstack.org/526823
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6079b722cbfc96dfab884a8350d8ade67e3fb840
Submitter: Zuul
Branch:    master"
1734625,2018-02-06 08:23:11 UTC,"Reviewed:  https://review.openstack.org/531258
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5d928ae2e00ac55582210a8df5afe6e3f45ff2bb
Submitter: Zuul
Branch:    master"
1734625,2018-01-05 02:34:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531280"
1734629,2018-01-25 14:47:00 UTC,fixed in bionic
1734632,2019-10-04 04:25:28 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1734632,2019-04-22 03:01:19 UTC,"Hello guys,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
Thanks"
1734632,2018-01-21 13:56:18 UTC,This still happens with Ubuntu 17.10 and kernel `4.13.0-30-generic`.
1734632,2017-12-09 19:39:27 UTC,Hi!
1734632,2017-12-07 11:12:29 UTC,Same here 4.10.0-40-generic
1734632,2017-12-05 12:55:47 UTC,"I have the same problem.
kernel 4.10.0-40-generic"
1734632,2017-11-29 22:16:22 UTC,"I have the same problem.
kernel 4.10.0-40-generic"
1734632,2017-11-29 17:10:07 UTC,"Hi, yes I have the same problem."
1734632,2017-11-29 16:32:14 UTC,I'm having this same isuue too.
1734632,2017-11-27 17:20:18 UTC,"Hello,
Yes, we confirm this problem.
It was a problem with the kernel previous to 4.10.0-38.
With the kernel 4.10.38 it was solved, but it goes back with the kernel 4.10.0-40.
Thanks"
1734632,2017-11-27 17:11:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734632,2017-11-27 10:03:34 UTC,"Hi, same problem here: after suspend the pointer goes to the upper right part of the screen and is not usable. Reload module psmouse solves the problem."
1734632,2018-01-22 10:55:34 UTC,"Hi there,"
1734632,2018-01-09 18:13:50 UTC,"Hello,"
1734653,2017-12-07 00:06:15 UTC,1) Remark about the aperture of the cracks:
1734653,2017-12-05 00:59:38 UTC,"Hi Bruno,"
1734653,2017-12-06 21:10:13 UTC,"Ok, I finally got some time to digest this. Thank you for pointing this
out, Bruno, it may have pretty severe impacts on DFNFlow simulations."
1734653,2019-02-05 20:24:50 UTC,moved form https://bugs.launchpad.net/yade/+bug/1734653 to https://gitlab.com/yade-dev/trunk/issues/38
1734653,2017-12-06 10:52:52 UTC,"> we should use directly crackAperture*crackArea as Vo in dV/Vo, no?
"
1734653,2017-12-11 10:53:09 UTC,"Hi Luc,
Please keep this discussion for the bug only.
Bruno"
1734653,2017-12-08 19:27:04 UTC,I believe we are somehow converging.
1734653,2017-12-08 13:56:25 UTC,"Q1 - I think it is possible to define a relevant geometry for multiple cracks; it is just the intersection of one tetrahedron with multiple polygonal faces. I think the problem of multiple fracture planes crossing one edge is very special, I would escape it on the basis that you can't break another time something that is already broken, so 2 planes = 1 crack locally if the two planes intersect."
1734653,2017-12-07 19:36:04 UTC,"You are right, we probably mixed up a few things... Sorry for that."
1734653,2017-12-07 15:33:46 UTC,">I am particularly confused by [3]
"
1734657,2018-01-02 19:01:00 UTC,ocfs2-tools is also affected
1734657,2017-11-27 12:44:59 UTC,"12:38 <rbasak> cpaelzer: based on the code I think that's a valid bug
12:39 <rbasak> It needs an rmtree in debian/ if it already exists first
12:39 <rbasak> I can't remember why we aren't using dpkg-source -x already but IIRC there's a good reason"
1734657,2017-11-27 10:34:51 UTC,"I could not more details with ""--keep-build-env"", but since it is reproducible I think the bug is good for you to take a look at."
1734657,2018-01-02 19:02:11 UTC,Also affects ocfs2-tools.
1734670,2019-07-29 14:30:40 UTC,the UI has been been removed
1734671,2019-09-17 07:15:38 UTC,Migrated to https://github.com/widelands/widelands/issues/3235
1734673,2017-11-27 19:03:42 UTC,A list of participants would be awesome in any case. Especially if the username gets pasted into the editbox if you click on one - that will make whispering easier too.
1734673,2019-09-17 07:22:03 UTC,Migrated to https://github.com/widelands/widelands/issues/3236
1734680,2020-01-06 10:55:49 UTC,"Hello,
4.10.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1734685,2018-12-04 08:59:01 UTC,"Your report isn't really helpful. Can you please be a bit more elaborating on what the issue is? Yes, the packages website doesn't offer downloading arm64 packages, mostly because they don't live in the main archive and thus would require a different link.  That's a known issue.  Apart from that your report doesn't make much sense to me unfortunately."
1734700,2019-07-03 20:39:08 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822841 is what downgraded keyutils from a Recommends to a Suggests
1734700,2017-11-27 14:22:47 UTC,"After some more tests I found that package
keyutils
is not installed anymore on my newer systems > 16.04. After installing package keyutils mount.cifs is mounting via kerberos ticket again! So there is a dependency for package keyutils in relevant packages missing and should be added!"
1734700,2019-05-31 23:13:35 UTC,"In my case, I resolve using param ""vers=1.0"""
1734700,2020-09-23 09:22:38 UTC,Problem is still present in ubuntu 20.04.1 fresh install : keyutils is missing and triggers this error when mounting with cifs:
1734700,2021-02-21 10:53:31 UTC,I can also confirm that installing the keyutils package fixes the problem (on Ubuntu 20.04).
1734700,2020-11-24 05:28:06 UTC,I can confirm that cifs-utils has a dependency on keyutils package.
1734700,2020-09-23 12:58:19 UTC,"@xavee, what kind of authentication are you using when mounting the cifs share? Can you also share the last entries of dmesg when you attempted mount fails, and ubuntu details (release, cifs-utils package version, etc)."
1734700,2018-06-01 13:35:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734700,2020-04-24 18:47:20 UTC,Thanks for getting back to us with this info.
1734700,2020-04-24 18:35:42 UTC,Hm. Nevermind I checked with smbclient and the share was actually removed from the Windows box... Maybe by one of the Microsoft upgrades. After sharing it the mounting worked properly. Thanks for the smbclient hint and sorry for the noise.
1734700,2020-04-24 18:26:04 UTC,"Please find the syslog output if cifs debug enabled below. The share was accessible on Monday 20 at least, I was running focal already, but I've been upgrading regularly. Not sure which package update broke it (I've changed the name of the share below manually):"
1734700,2020-04-24 12:33:04 UTC,"> mount error(2): No such file or directory
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
"
1734700,2020-04-24 07:00:48 UTC,Suddenly mounting a cifs partition fails:
1734702,2018-01-08 09:57:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734702,2018-01-08 12:03:35 UTC,"This bug affects my Lubuntu 17.10 (64-bit) system, which has version 5.26.0-8ubuntu1 of the perl and perl-doc packages. I noticed the bug immediately upon checking for it after Zanna (https://launchpad.net/~rose-anna-bleasdale / https://askubuntu.com/users/527764/zanna) reported experiencing it in Ubuntu MATE 17.10. Until this bug is fixed, I suggest the workaround of setting the PAGER environment variable to ""less"" so that the proper configuration for less is used; other full workarounds are also effective (see below)."
1734711,2017-12-28 14:53:31 UTC,Agreed. Especially since double clicking is supported in the regular patron search function.
1734713,2018-03-15 15:32:07 UTC,After having a look this issue happens in bagpipe driver when there are two router interfaces plugged on a subnet.  The typical case where this arises is when there are both an IPv4 x.y.z.1 interface and an IPv6 x:y:z::1 interface.
1734713,2017-12-04 14:51:32 UTC,I have the same problem when I update a BGPVPN. For instance if I change just the name.
1734713,2018-03-15 15:33:39 UTC,Note that the issue does not occur anymore with bagpipe_v2 driver (available since Queens)
1734714,2017-11-27 18:41:53 UTC,"Tracing SB-C::TWO-ARG-DERIVE-TYPE show some extremely large bignums are being computed.  I suggest type propagation give up if the bignums get too big, and just widen to INTEGER."
1734714,2017-11-27 17:37:42 UTC,Simplified example:
1734714,2017-11-27 19:54:41 UTC,Even simpler:
1734724,2017-12-20 15:47:44 UTC,Submitted https://review.openstack.org/529171 to openstack/devstack-plugin-sheepdog to see if that fixes the out of space issue.
1734724,2017-11-27 17:24:47 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Insufficient%20free%20space%20for%20volume%20creation%20on%20host%5C%22%20tags%3Ascreen-c-sch.txt.gz%20build_name%3Asheepdog
1734727,2017-11-30 05:27:36 UTC,"Hi Jesse,"
1734727,2017-12-04 21:38:18 UTC,"Thanks Afshan, after updating, when I start hplip in GUI mode, it says ""No system tray detected on system. Unable to start."""
1734727,2017-11-29 20:37:03 UTC,"Thanks for the reply Afshan. Can I use the Ubuntu software updater program to update HPLIP to 3.17.11, or do I need to download the latest driver from somewhere else?"
1734727,2018-11-16 04:17:38 UTC,[Expired for hplip (Ubuntu) because there has been no activity for 60 days.]
1734727,2018-09-16 21:43:33 UTC,"Hello Jesse,
Thank you for submitting this bug and reporting a problem with hplip.  You made this bug report some time ago and Ubuntu and hplip have been updated since then."
1734727,2017-11-29 09:44:28 UTC,"Hi Jesse,"
1734735,2019-05-24 11:20:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734736,2018-04-16 11:48:55 UTC,"Hi Shakhova,"
1734736,2018-04-26 15:05:25 UTC,"Hi,"
1734757,2018-03-19 10:55:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1734757,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1734757,2017-11-27 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1734758,2017-12-12 11:33:01 UTC,"So I'm curious what feedback we're missing.
Is it that the machines didn't appear to be in error. Is it possible to show the ""juju status"" output for the machine that failed to provision? I would expect that we did report an error for it, although 'conjure-up' may not know what to do with that."
1734758,2017-11-30 16:30:13 UTC,Hi @anastasia-macmood
1734758,2017-11-30 11:46:02 UTC,"It looks like the actual issue might be using ""--config vpc-id=X"" rather
than ""--model-default vpc-id=X"" so that both the controller instances and
newly created models will both use the vpc.
That said, it also does appear like we should be surfacing the provisioning
error in a better way, if the machine really does only stay in ""pending""."
1734758,2017-11-29 18:48:41 UTC,for reference: https://github.com/conjure-up/conjure-up/issues/1241 for supporting providing vpc-id's and other model configurations for juju
1734758,2017-11-29 18:29:22 UTC,"Note: I asked for this bug to be filed here (rather than on conjure-up, where we have a different aspect of this issue filed to work on) because Juju failed to provision the machine but never updated the machine status from ""pending."""
1734759,2018-08-08 14:34:49 UTC,This is still present in bionic (gnome-shell 3.28.2-0ubuntu0.18.04.1).
1734759,2018-08-08 08:27:21 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1734759,2017-12-22 09:00:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1734761,2017-11-27 20:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1734761,2017-12-12 13:09:29 UTC,All these options have been enabled as modules in the unstable kernel tree.
1734761,2017-11-27 20:49:46 UTC,Not relevant for this bug.
1734762,2018-02-02 17:26:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734774,2017-11-27 23:00:12 UTC,"Hi,
A related bug in Eucalpytus is
 https://eucalyptus.atlassian.net/browse/EUCA-13331"
1734774,2017-11-27 23:18:11 UTC,"Scott,"
1734774,2018-01-25 16:58:55 UTC,"Hi John,
sorry for the slow reply.
  Cloud-init identifies ""the real amazon"" via
 http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html"
1734774,2018-01-25 17:04:45 UTC,"It appears there is nothing for cloud-init to do here, that Eucalyptus will likely make a change to look like ec2 so cloud-init wouldn't know any difference."
1734774,2018-09-21 06:39:43 UTC,"Just to be clear... If there is some way that we can identify that cloud-init is running on eucalyptus, we'll happily take patches or doc."
1734774,2018-09-21 18:03:08 UTC,"Hi All,"
1734786,2017-11-28 13:05:22 UTC,"And I believe that PHP, when parsing ini, is reading value as INT instead of BOOL, that is why ""off"" leads to an empty value instead of 0. It also displays the value as INT in phpinfo(), i.e. 1/0 instead of On/Off."
1734786,2017-11-28 12:47:21 UTC,"I believe it's this issue upstream, filed in 2010: https://bugs.php.net/bug.php?id=52168"
1734786,2017-11-28 13:02:41 UTC,"This is not that bug. The problem here is with setting value, not with getting it."
1734788,2017-11-28 13:10:31 UTC,"Whatever the root cause is, oslo_messaging 5.17.1 doesn't have this issue."
1734788,2017-11-28 14:57:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523431"
1734788,2017-11-30 08:01:43 UTC,"Reviewed:  https://review.openstack.org/523431
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=c38857e1101027a734a35f4e80bc4084fabc034b
Submitter: Zuul
Branch:    master"
1734788,2017-11-30 09:07:24 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/524099"
1734788,2017-11-30 09:07:44 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/524100"
1734788,2017-12-04 09:03:49 UTC,"Reviewed:  https://review.openstack.org/524099
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=221664faa128557fa1eb415837675a55a1560131
Submitter: Zuul
Branch:    stable/pike"
1734788,2017-12-04 10:29:29 UTC,This issue was fixed in the openstack/oslo.messaging 5.34.1 release.
1734788,2017-12-04 16:43:34 UTC,"Reviewed:  https://review.openstack.org/524100
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=e1ac7f8862425e5a8f9b96e28234a0b59e579dbd
Submitter: Zuul
Branch:    stable/ocata"
1734788,2017-12-11 21:42:54 UTC,This issue was fixed in the openstack/oslo.messaging 5.30.2 release.
1734788,2017-12-21 22:47:02 UTC,This issue was fixed in the openstack/oslo.messaging 5.17.3 release.
1734788,2018-02-01 14:58:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734790,2018-03-22 17:14:47 UTC,Not applicable to 5.0.
1734790,2018-05-18 18:03:45 UTC,"Review in progress for https://review.opencontrail.org/43163
Submitter: Ramprakash R (<email address hidden>)"
1734790,2018-05-21 23:12:53 UTC,"Reviewed:  https://review.opencontrail.org/43163
Committed: http://github.com/Juniper/contrail-server-manager/commit/87b2028e608abda9a9671d6be0ab5afa5abe318d
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1734790,2017-11-28 19:33:33 UTC,"WA: Manually update /etc/neutron/api-paste.ini per
https://github.com/Juniper/contrail-controller/wiki/RBAC#etcneutronapi-pasteini"
1734790,2018-05-18 16:49:14 UTC,"Reviewed:  https://review.opencontrail.org/43126
Committed: http://github.com/Juniper/contrail-ansible/commit/7173e576b12a4f3374838695bb053bbc99429eba
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1734790,2018-05-17 17:24:15 UTC,"Review in progress for https://review.opencontrail.org/43126
Submitter: Ramprakash R (<email address hidden>)"
1734790,2018-05-16 00:21:44 UTC,Is this for newton or Ocata?
1734790,2017-12-01 14:40:55 UTC,Releasenotes:
1734791,2017-12-19 14:52:40 UTC,"I have the same problem, but with gpg-agent, which also reverse-depends on graphical-session-pre.target."
1734791,2017-12-19 14:48:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734792,2018-04-12 12:13:24 UTC,"Not only qemu-x86_64, but also:"
1734792,2019-11-13 10:04:50 UTC,9bdfa4d23f43 linux-user: add memfd_create
1734805,2017-11-28 05:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1734805,2017-11-29 15:42:06 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1734805,2017-11-30 16:30:35 UTC,apport information
1734805,2017-11-30 16:30:36 UTC,apport information
1734805,2017-11-30 16:31:43 UTC,apport information
1734805,2017-11-30 16:31:45 UTC,apport information
1734805,2017-11-30 16:31:46 UTC,apport information
1734805,2017-11-30 16:37:35 UTC,"Just tested, this issue exists in v4.15.0-041500rc1-generic too"
1734805,2017-12-02 12:30:06 UTC,Where i have to add it?
1734805,2017-12-01 02:48:50 UTC,Does blacklist nouveau helps?
1734805,2017-11-30 16:30:33 UTC,apport information
1734806,2017-12-26 12:12:53 UTC,Ubuntu Seeds does not have a Launchpad page for Bug Reports.
1734806,2018-02-18 13:56:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734810,2018-11-04 12:20:50 UTC,"Windows installs are still acting abnormally slow on the latest Gnome Boxes flatpaks in Ubuntu 18.10.
I'll try to get my CLI parameters and add it to the bug."
1734810,2018-05-23 10:22:16 UTC,"If you don't provide the CLI parameters, there's no way we can help here, sorry. So marking this as ""invalid"" for the QEMU project."
1734810,2018-02-20 09:38:21 UTC,I am constantly running Windows 10 and Windows Server 2016 and I don't experience specific slowdowns.
1734810,2018-02-20 03:04:27 UTC,Any news or fixes?
1734810,2018-02-20 06:21:43 UTC,Which command line parameters are passed to QEMU? Is your system able to use KVM (e.g. did you enable virtualization support in your BIOS)?
1734810,2018-11-08 16:50:50 UTC,"And for the CLI parameters, you could run this in a console window for example, after starting your guest:"
1734810,2018-11-08 16:48:31 UTC,At least please try to answer my questions in comment #3: Is virtualization enabled in your BIOS? Is KVM enabled on your system (i.e. are the kvm.ko and kvm_intel.ko or kvm_amd.ko modules loaded)?
1734810,2018-11-08 16:44:02 UTC,"Jeb, if you open a bug against QEMU here, we expect some information how QEMU is run. If you only interact with Gnome Boxes, then please only open a bug against Boxes - best in their Bug tracker here: https://bugzilla.gnome.org/ ... I guess nobody of the Boxes project is checking Launchpad, so reporting Boxes bugs here in Launchpad does not make much sense."
1734810,2018-11-08 13:53:38 UTC,"Sorry if this sounds dumb, where do I find my CLI Parameters for my Windows VM?"
1734811,2017-12-06 16:52:53 UTC,You can use `byobu-select-backend` to switch between screen or tmux.  I don't think there are many fundamental differences if you don't use advanced features such as pane splits.
1734811,2017-12-06 23:39:12 UTC,"A workaround is to disable the byobu status line as follows
echo -e 'set -ug status-left\nset -ug status-right' >>$BYOBU_CONFIG_DIR/profile.tmux"
1734811,2017-12-06 16:02:18 UTC,I tried removing all informations as well. Is it possible to make byobu default to using screen? What is the pros/cons anyway?
1734811,2017-12-06 15:49:54 UTC,"This bug affects one of my ""real"" computers.  The affected computer was upgraded from Lubuntu 17.04 to 17.10 not long ago.  I tried to remove/reinstall byobu and its dependencies but it doesn't solve the problem.  Interestingly, the bug also exists in a freshly installed Ubuntu 17.10 lxd instance on that computer."
1734811,2017-12-06 07:26:36 UTC,"I can add that ""screen"" works. And it - AFAIK - both screen adn byobu uses tmux."
1734811,2017-12-06 04:13:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734811,2017-12-06 18:50:54 UTC,Good to know. Thank you.
1734811,2017-12-06 22:04:29 UTC,"If I downgrade tmux from 2.5-3 to 2.3-4 (the version in Ubuntu 17.04), then byobu does not ever get killed after detaching."
1734817,2018-08-07 20:35:09 UTC,"gnome-terminal is a long complicated story (see the link from comment 5 if you care), BUT one of the 3 or so reasons we removed the global menu mnemonics was that even if we enabled them, Alt+F didn't work. I can no longer recall for sure, but I think Alt+F stopped working for us when we ported to GMenu (the first link here from comment 3)."
1734817,2018-08-07 23:46:47 UTC,Sure is a complicated story.
1734817,2018-08-07 16:41:21 UTC,"Note, Alt+F10 will still work."
1734817,2018-08-07 16:36:44 UTC,"Ah, It's because of this: https://bugzilla.gnome.org/show_bug.cgi?id=792978"
1734817,2018-08-05 23:35:42 UTC,"I re-checked, indeed on my system, the ALT+F doesn't work for me. This is on Bionic 18.04 LTS, which I hope to stick with for some time."
1734817,2018-08-05 17:06:46 UTC,Gedit: Alt+F works for me (I am on cosmic using 3.28.1)
1734817,2018-08-05 03:17:14 UTC,Updating this report for Ubuntu 18.04.
1734817,2017-11-28 08:11:29 UTC,"For me, Gedit and Evince are working fine. Do they show horizontal menu-bar? Gnome apps doesn't usually have menu-bar. Ubuntu patches few to show menu-bar (file, edit etc) under unity. But if a app doesn't have file menu, naturally ALT+F won't work."
1734827,2017-12-06 04:14:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525870"
1734827,2017-12-14 22:03:12 UTC,"Reviewed:  https://review.openstack.org/525870
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=2c12395ef313a4d380034a9e65b0f6af027ac022
Submitter: Zuul
Branch:    master"
1734827,2017-11-28 17:38:07 UTC,"Thanks Hironori. I think the API will be fairly straightforward, and changes in API require a spec."
1734827,2017-11-28 08:23:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/523335"
1734827,2017-12-04 16:31:41 UTC,"Reviewed:  https://review.openstack.org/523335
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=044a6a04a24fec949b4b7036ba5403944114ac98
Submitter: Zuul
Branch:    master"
1734836,2017-11-28 17:36:28 UTC,Some addition here:
1734836,2017-11-29 08:29:35 UTC,"Indeed, exactly the same problem here (behind proxy).
Imho we should stop multiple internet requests for upgrading OS, except official repositories...."
1734836,2017-11-29 12:44:19 UTC,"Same issue for upgrade of LinuxMint Mate edition 18.2 to 18.3 behind a proxy.
Tried to solve the issue as https://bugs.launchpad.net/linuxmint/+bug/1734836/comments/1 did but same result."
1734838,2017-11-28 11:57:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523395"
1734838,2017-11-28 09:19:04 UTC,"The reason may be that, rbd image can not be deleted if it is in use by an instance, because it is a rbd snap, and an instance system disk is a cloned volume from the snap in rbd pool, if we call glance to delete the snap, ""HTTPConflict: 409 Conflict: Image 9a993e71-71ca-490e-b3cb-0b4dca2e574c could not be deleted because it is in use: The image cannot be deleted because it is in use through the backend store outside of Glance. (HTTP 409)"" will be returned."
1734838,2018-01-12 12:48:33 UTC,"Reviewed:  https://review.openstack.org/523395
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3e766e5bd429c6119c077b8be02360ae1e1ec8bd
Submitter: Zuul
Branch:    master"
1734838,2018-01-15 01:37:01 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/533439"
1734838,2018-04-02 13:19:05 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1734838,2018-03-08 15:43:36 UTC,"Reviewed:  https://review.openstack.org/533439
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=43c42b6f691b0c97a1ef626d29a7d08a9a240f4f
Submitter: Zuul
Branch:    stable/pike"
1734838,2018-01-26 00:43:39 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1734845,2019-10-15 13:46:42 UTC,"I believe this was traced to people using snapd inside privileged LXD containers, thus mixing kernel sandbox configuration from the host with the guest. The guest was using different version of snapd than the host but was confined by the host's apparmor profile for snap-conifine. Over time snap-conifne started to use a new directory for locks and stopped working."
1734851,2017-11-28 16:35:28 UTC,Wow. That's an interesting setup.
1734851,2017-12-01 17:35:08 UTC,"Now, I'm using Enchanting on Linux and it works."
1734851,2017-12-02 16:10:48 UTC,Is that within a VM as well?
1734851,2017-11-28 10:04:53 UTC,I'm using linux (16.04.3) but I installed Enchanting on Windows XP with Virtualbox
1734852,2020-11-09 08:51:56 UTC,"4.13 EOL, closing this bug."
1734856,2018-01-02 07:38:00 UTC,Thanks for sorting out the Artful test already bssrikanth.
1734856,2018-01-02 07:59:59 UTC,"------- Comment From <email address hidden> 2018-01-02 02:58 EDT-------
Thanks for the clarification. Yes verification being done using host levels: artful, xenial and zesty."
1734856,2018-01-02 08:49:18 UTC,"Ok, so are all three artful, xenial and zesty done already or are we waiting on xenial and zesty to complete?"
1734856,2018-01-02 09:40:04 UTC,"------- Comment From <email address hidden> 2018-01-02 04:38 EDT-------
(In reply to comment #35)

> Ok, so are all three artful, xenial and zesty done already or are we waiting
> on xenial and zesty to complete?
"
1734856,2018-01-02 10:53:52 UTC,This bug was fixed in the package slof - 20170724+dfsg-1ubuntu0.1
1734856,2018-01-02 10:53:55 UTC,"The verification of the Stable Release Update for slof has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1734856,2018-01-02 12:20:07 UTC,"------- Comment From <email address hidden> 2018-01-02 07:17 EDT-------
on xenial still i am seeing the issue.
Machine details:
1)kernel level
root@ltc84-pkvm1:/var/lib/libvirt/images# uname -a
Linux ltc84-pkvm1 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:48 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux"
1734856,2018-01-02 12:30:05 UTC,"------- Comment From <email address hidden> 2018-01-02 07:24 EDT-------
(In reply to comment #38)

> on xenial still i am seeing the issue.
> Machine details:
> 1)kernel level
> root@ltc84-pkvm1:/var/lib/libvirt/images# uname -a
> Linux ltc84-pkvm1 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:48 UTC
> 2017 ppc64le ppc64le ppc64le GNU/Linux
>
"
1734856,2018-01-02 12:50:28 UTC,"------- Comment From <email address hidden> 2018-01-02 07:42 EDT-------
Does this proposed xenial slof fix dependent on kernel used on host?   or the proposed slof fix should work on both xenial kernel 4.4.x or 4.10.x?"
1734856,2018-01-02 13:06:00 UTC,"It is mostly independent to the kernel, the fix by Nikunj just needs the new Slof to be on the host."
1734856,2018-01-03 07:20:21 UTC,"------- Comment From <email address hidden> 2018-01-03 02:12 EDT-------
Tested, it  is working fine in both xenial and zesty."
1734856,2018-01-03 07:20:24 UTC,------- Comment (attachment only) From <email address hidden> 2018-01-03 02:16 EDT-------
1734856,2018-01-03 07:20:25 UTC,------- Comment (attachment only) From <email address hidden> 2018-01-03 02:16 EDT-------
1734856,2018-01-03 08:04:47 UTC,"verification done on
1. artful
2. xenial
3. zesty
results in comment 32, 45, 46"
1734856,2018-01-03 08:13:09 UTC,"Thank you Srikanth (and Team since I saw so many people update the bug).
This is already released for Artful, the SRU Team should soon release it for X/Z as well now."
1734856,2018-01-03 12:13:50 UTC,This bug was fixed in the package slof - 20151103+dfsg-1ubuntu1.1
1734856,2018-01-03 12:15:00 UTC,This bug was fixed in the package slof - 20161019+dfsg-1ubuntu0.1
1734856,2018-01-01 05:19:59 UTC,"------- Comment From <email address hidden> 2018-01-01 00:15 EDT-------
Since artful verification is done, is zesty verification really needed here? https://www.ubuntu.com/info/release-end-of-life says zesty end of life is 2017. I see verification-needed-xenial was added and then removed.  I think we can verify this fix on xenial rather than zesty. Any comments?"
1734856,2018-01-02 13:09:02 UTC,"------- Comment From <email address hidden> 2018-01-02 08:05 EDT-------
Prudhvi gave the system access and I have replied the proposed slof and restarted the guest. It seems working fine with xenial.  Guest booted successfully showing all 49 disks."
1734856,2018-01-01 05:10:03 UTC,"------- Comment From <email address hidden> 2018-01-01 00:08 EDT-------
According to https://bugs.launchpad.net/ubuntu/+source/slof/+bug/1734856/comments/32"
1734856,2017-12-14 09:42:06 UTC,"Thanks for the info Nikunj.
That means we can likely soon pick it up as a sync from Debian again.
But for now can fix it by picking your changes."
1734856,2017-12-26 03:09:57 UTC,"------- Comment From <email address hidden> 2017-12-25 22:03 EDT-------
(In reply to comment #27)

> -----------------------------------------------------------------------------
> ----------------------
> I could able to recreate the issue;
>
> Initially added upto 32 boot order disks apart from primary disk(boot order
> 1), and not able to recreate it. However with one more disks added with boot
> dev, could able to create the reported issue.
>
>
>
>
>
> Applied artful proposed fixes and could not able to see the reported issue
> fixed.
> Help needed to apply artful-proposed fix.
>
> Applied artful proposed fixes and could not able to see the reported issue
> fixed.
> Help needed to apply artful-proposed fix.
>
> Applied artful proposed fixes and could not able to see the reported issue
> fixed.
> Help needed to apply artful-proposed fix.
"
1734856,2017-12-13 13:40:59 UTC,@Nikunj - do you happen to know if Alexey is planning an official release soon that would include this fix?
1734856,2017-12-13 14:47:31 UTC,"I tried to verify the case and fix myself which is a prereq for good steps to reproduce for the SRU anyway.
I came up with test steps based on what was initially reported.
$ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=ppc64el label=daily release=bionic
$ uvt-kvm create --password=ubuntu cpaelzer-bionic release=bionic arch=ppc64el label=daily
$ for i in {1..20}; do
  h=$(printf ""\x$(printf %x $((98+$i)))"");
  echo ""<disk type='file' device='disk'><driver name='qemu' type='qcow2'/><source file='/var/lib/uvtool/libvirt/images/cpaelzer-bionic-t$i.qcow'/><alias name='virtio-disk0'/><target dev='vd$h' bus='virtio'/></disk>"" > disk.xml;
  qemu-img create -f qcow2 /var/lib/uvtool/libvirt/images/cpaelzer-bionic-t$i.qcow 1M;
  virsh attach-device artful-testguest disk.xml;
done
$ virsh console <guest>
# in guest then
$ sudo reboot"
1734856,2017-12-13 11:43:53 UTC,Thanks for the ping Nikunj!
1734856,2017-12-13 11:09:57 UTC,"------- Comment From <email address hidden> 2017-12-13 06:03 EDT-------
Patches commited:"
1734856,2017-12-04 14:34:57 UTC,"Marking as ""incomplete"" until patch lands upstream."
1734856,2017-11-29 07:45:46 UTC,"Also linked up the GH issue and the SLOF project in general.
We should get auto-updates once resolved, but to be sure @nikunj please feel free to ping here once the discussion on the patch concludes and is committed upstream."
1734856,2017-11-29 07:39:53 UTC,"Thanks for the bug, I see the patch is under active discussion atm.
Lets take a look to integrate once that discussion concludes."
1734856,2017-11-29 06:59:41 UTC,"------- Comment From <email address hidden> 2017-11-29 01:56 EDT-------
Patch under discussion upstream"
1734856,2017-12-13 14:47:19 UTC,"Hi,
I don't want to wait too long, so while waiting for an answer I made a ppa available that should be tested to confirm this fix is good (for bionic).
Please test on Bionic from ppa: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3079"
1734856,2017-12-13 14:53:41 UTC,"Tried the base 2 + 2x20 = 42 disks.
Still working for me as-is."
1734856,2017-12-13 18:04:26 UTC,@paelzer you need to have boot order in each of these disk
1734856,2017-12-14 07:30:30 UTC,"It was still working with 20 disks and boot index, but 48 made it.
Thanks Nikunj for the bood index hint."
1734856,2017-12-14 08:57:24 UTC,"@paelzer Had a discussion with Alexey, he has created a release label"
1734856,2017-12-30 03:09:59 UTC,"------- Comment From <email address hidden> 2017-12-29 22:02 EDT-------
I could able to recreate the issue with UBU17.10(artful) as host, running with xenial, zesty, and artful as guest VMs, where guest crashed if we try to add more than 36 disks with ""boot order=1"" (this is what the observation in my testing)."
1734856,2017-12-15 08:40:50 UTC,"My former tests focussed on the testcase.
I deployed a fresh power8 system and ran some more tests on the proposed change but found no issues - that said going on."
1734856,2017-12-15 10:35:00 UTC,"On my test environment with the extracted slof.bin from the DEB package, I do not see the issue."
1734856,2017-12-18 08:09:33 UTC,"I saw the new upstream release, over the next time this will be picked up by Debian and we make it a sync again then.
For now I pick the fix as tested from the ppa into Bionic.
Once that migrated I'll look at the SRUs into X-A."
1734856,2017-12-18 09:37:29 UTC,This bug was fixed in the package slof - 20170724+dfsg-1ubuntu1
1734856,2017-12-25 20:18:44 UTC,"------- Comment From <email address hidden> 2017-12-25 15:10 EDT-------
I'm unable to get this fix applied to artful guest VM thought slof packages are updates.
----------------------------------------------------------------------------------------------------------------------------------
I could able to recreate the issue; Initially added upto 32 boot order disks apart from primary disk(boot order 1), and not able to recreate it."
1734856,2017-12-25 20:15:59 UTC,"Applied artful proposed fixes and could not able to see the reported issue fixed.
Help needed to apply artful-proposed fix."
1734856,2017-12-25 20:15:40 UTC,"Artful validation:
---------------------------------------------------------------------------------------------------
I could able to recreate the issue;"
1734856,2017-12-21 00:38:35 UTC,"Hello bugproxy, or anyone else affected,"
1734856,2017-12-21 00:37:20 UTC,"Hello bugproxy, or anyone else affected,"
1734856,2017-12-21 00:35:01 UTC,"Hello bugproxy, or anyone else affected,"
1734856,2017-12-19 09:18:09 UTC,Tests good - MPs open for packaging review
1734856,2017-12-18 13:30:02 UTC,Doing another bigger check set on Xenial and then opening up the MPs for review.
1734856,2017-12-14 09:44:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734856,2017-12-18 13:29:17 UTC,MPs for the packaging change in X/Z/A up for review and linked in the bug.
1734872,2020-05-28 07:39:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/731452"
1734872,2019-11-11 15:40:26 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1734872,2020-05-28 08:38:19 UTC,"Change abandoned by Yongjun Bai (bai.yongjun@99cloud.net) on branch: stable/pike
Review: https://review.opendev.org/731452"
1734872,2019-09-09 09:17:26 UTC,This issue was fixed in the openstack/kolla-ansible 6.2.2 release.
1734872,2017-11-28 11:43:37 UTC,"During deploy and reconfigure, kolla-ansible always attempts to create a cell [1]. The corresponding nova-manage command uses the DB and MQ connection strings as the uniqueness check for cells [2]. Therefore, if either of these changes, create_cell will create a new cell."
1734872,2019-06-05 18:36:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/663398"
1734872,2019-06-13 18:56:07 UTC,"Reviewed:  https://review.opendev.org/663398
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=19b8dbe460315c5da23c33aa57c967d75d7f2018
Submitter: Zuul
Branch:    master"
1734872,2019-06-13 18:59:03 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/665212"
1734872,2019-06-13 19:01:22 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/665214"
1734872,2019-06-17 09:14:23 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/665618"
1734872,2019-06-18 10:01:55 UTC,"Reviewed:  https://review.opendev.org/665212
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=3458a7b28ac0cfec9f1106ab1e3a2b83873fe97a
Submitter: Zuul
Branch:    stable/rocky"
1734872,2019-09-09 09:18:21 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.2 release.
1734872,2019-06-18 10:02:03 UTC,"Reviewed:  https://review.opendev.org/665214
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=f6cfee3201d0067ee500dd507924038315ac6efd
Submitter: Zuul
Branch:    stable/queens"
1734872,2019-07-18 00:37:40 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc2 release candidate.
1734872,2019-06-18 09:59:47 UTC,"Reviewed:  https://review.opendev.org/665618
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=f9948e0a31e02457db186c27e874175cb9685932
Submitter: Zuul
Branch:    stable/stein"
1734874,2018-05-15 14:50:14 UTC,This change was made by a bot.
1734877,2017-11-28 12:30:46 UTC,When i removed packages related to plymouth from the image. Then the image booted up properly.
1734881,2018-01-24 22:37:45 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1462
1734883,2020-09-28 12:01:33 UTC,Fix released in git-ubuntu version 1.0
1734883,2018-03-06 05:20:47 UTC,I *think* git_repository.commit_tree_hash could shortcut this.
1734888,2018-03-06 05:21:28 UTC,I think this is doable.
1734889,2018-02-08 09:04:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734891,2019-05-12 10:28:13 UTC,"https://errors.ubuntu.com/problem/b602a0d844bdf5a495f5843d042e2f2b9dbb58d0  seems the corresponding error report, there has been no issue with > 3.26 so far, maybe it's fixed in Disco?"
1734891,2018-04-09 13:42:16 UTC,The duplicate has to do with protected zip and the included nautilus archive managing feature
1734891,2018-04-09 13:35:39 UTC,"My bug #1762400 got marked as a duplicate for this one, but I don't have Dropbox installed."
1734891,2018-03-26 13:11:52 UTC,The upstream comments suggests it might be due to the dropbox plugin
1734891,2017-11-28 14:54:46 UTC,"Hello,"
1734891,2017-11-28 14:48:09 UTC,"Hello,"
1734891,2017-11-28 14:41:18 UTC,"StacktraceTop:
 nautilus_list_model_get_all_iters_for_file (model=0x0, file=file@entry=0x5592976258c0) at ../src/nautilus-list-model.c:722
 nautilus_list_model_get_first_iter_for_file (model=<optimized out>, file=file@entry=0x5592976258c0, iter=iter@entry=0x7fff82c013d0) at ../src/nautilus-list-model.c:739
 nautilus_list_view_scroll_to_file (file=0x5592976258c0, view=0x559296e074b0) at ../src/nautilus-list-view.c:3447
 list_view_scroll_to_file (view=<optimized out>, uri=<optimized out>) at ../src/nautilus-list-view.c:3474
 view_ended_loading (view=<optimized out>, self=0x5592970ce330) at ../src/nautilus-window-slot.c:2560"
1734892,2017-11-30 17:13:50 UTC,"We might be able to detect and back this out, or retry the boot sequence."
1734895,2018-03-10 15:53:17 UTC,Can you precise the SoundConverter version please ?
1734895,2018-03-10 15:12:06 UTC,Added a trace in order do help finding the bug:
1734897,2017-11-28 18:32:53 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1734906,2020-04-09 04:17:20 UTC,[Expired for usd-importer because there has been no activity for 60 days.]
1734906,2017-11-28 23:55:49 UTC,"Though I suppose that the snap gives us fixed dependency versions, so perhaps we want imports themselves to run from the snap for hash stability. In the long term, tests should ensure this though."
1734906,2017-11-29 04:28:19 UTC,"The point is that which git-ubuntu you use is by PATH. there is no sense in
running the scripts ""from"" the snap because they are not in the snap."
1734917,2019-10-24 14:30:28 UTC,This issue was fixed in the openstack/cinder 12.0.10 release.
1734917,2019-09-27 09:03:32 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1734917,2019-10-04 08:51:58 UTC,This issue was fixed in the openstack/cinder 14.0.2 release.
1734917,2019-04-22 05:05:25 UTC,"@raghavendra., can you look into this case ?  we have 2 cases related to the same issue i guess.."
1734917,2019-08-19 15:10:59 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677232"
1734917,2019-08-21 18:33:28 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/677800"
1734917,2019-08-21 18:33:50 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/677801"
1734917,2019-08-21 20:47:24 UTC,"Reviewed:  https://review.opendev.org/677232
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9e122f11661b766b2fe2c3a12bab35ef6e14f3f1
Submitter: Zuul
Branch:    master"
1734917,2019-08-22 14:54:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/678037"
1734917,2019-10-04 13:00:17 UTC,This issue was fixed in the openstack/cinder 13.0.7 release.
1734917,2019-09-12 09:57:35 UTC,"Reviewed:  https://review.opendev.org/677800
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=25a9b4027ab9f61180519983376e4b34d4799412
Submitter: Zuul
Branch:    stable/stein"
1734917,2019-10-03 22:15:22 UTC,"Reviewed:  https://review.opendev.org/678037
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9d4e3674dbba71182122557fa1bb04c3afdf9f91
Submitter: Zuul
Branch:    stable/queens"
1734917,2019-09-20 04:17:01 UTC,"Reviewed:  https://review.opendev.org/677801
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=df7fd514a77734e5d57a56d5c0f34d0245efc86c
Submitter: Zuul
Branch:    stable/rocky"
1734922,2017-11-28 16:19:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1734939,2020-08-25 19:31:07 UTC,"This bug is believed to be fixed in cloud-init in version 20.3. If this is still a problem for you, please make a comment and set the state back to New"
1734939,2020-07-10 18:23:27 UTC,This bug was fixed in the package cloud-init - 20.2-94-g3d06abc2-0ubuntu1
1734939,2020-06-04 16:37:22 UTC,https://github.com/canonical/cloud-init/pull/367
1734947,2019-03-05 13:45:16 UTC,Is this still needed?
1734950,2018-03-14 14:48:34 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1734959,2021-01-23 20:50:20 UTC,Our representation of complex types is not (and I think has never been) able to represent
1734959,2017-11-28 22:23:04 UTC,"(typep (complex 1 4) '(or (complex (integer 1 2)) (complex (integer 3 4))))
returns T incorrectly."
1734959,2021-01-23 15:59:59 UTC,"OK, if we don't upgrade in upgraded-complex-part-type then yes things are wrong.  Probably half of the system thinks that we do upgrade, and half doesn't (and another half is just confused)."
1734959,2021-01-23 15:53:44 UTC,"And our upgraded-complex-part-type doesn't upgrade anything, so it can't be claimed that it has the same representation."
1734959,2021-01-23 15:36:41 UTC,"> (COMPLEX <x>) means the complex type whose elements match <x>, and all other types of the same representation
"
1734959,2021-01-23 15:23:25 UTC,"the COMPLEX type is a bit weird, though: (COMPLEX <x>) means the complex type whose elements match <x>, and all other types of the same representation -- it's a bit like an array type.  I'm not claiming that the COMPLEX type algebra is bug-free, but I don't think any of these examples is strictly speaking wrong."
1734959,2019-11-02 17:24:05 UTC,Negation types suffer as well
1734967,2017-11-29 14:37:24 UTC,"Thomas,"
1734967,2017-11-29 14:05:45 UTC,"I'll set this bug as affecting php package, since this tzdata change is modifying the behaviour of php timezone."
1734967,2017-11-29 14:31:34 UTC,"Just to be clear, this isn't a bug based upon comment 1 but new tasks were opened in comment 2?"
1734967,2017-11-29 13:45:13 UTC,"Hi Thomas,"
1734967,2017-12-04 16:48:33 UTC,"I have started a dialogue on the TZ mailinglist to perhaps have the
change (WGT/WGST at least) reverted. That's my goal anyway, so we'll see
how it goes."
1734967,2017-11-29 14:44:43 UTC,Took from Ubuntu php7 source code :
1734967,2017-12-03 12:04:06 UTC,"Hi guys,"
1734967,2017-11-30 15:25:39 UTC,I have compile the php upstream source code from : https://github.com/php/php-src
1734967,2017-11-30 16:46:34 UTC,At code inspection I have strong believe this commit is the one changing the behaviour between comment #2 (America/Sao_Paulo) and comment#6 (UTC)
1734967,2017-11-30 18:52:36 UTC,I'll try to do more testing to conclude my assumption and see if anything else is needed.
1734967,2017-12-04 16:10:26 UTC,"The more I look into this the more I start to think it may not be a php bug as I first guess.
php is relying on tzdata package so it should follow what tzdata bundle has in hand."
1734967,2017-12-01 12:54:32 UTC,"Nish,"
1734967,2017-12-01 12:55:29 UTC,I just notice a new version of php in debian was release --> 7.1.12-1 (sid)
1734967,2017-12-01 13:05:28 UTC,"Same thing with new php pkg release in debian/unstable (php - 7.1.12-1).
It still displays America/Sao_Paulo"
1734967,2017-12-01 13:32:38 UTC,"Does the Ubuntu php build use the bundled tzdata? A lot of stuff comes from
the system not the source (e.g, pcre iirc)"
1734967,2017-12-03 00:21:53 UTC,"Nish,"
1734967,2017-12-01 03:38:19 UTC,Is this already fixed in proposed (MRE to latest upstream php 7.0 and 7.1)?
1734975,2019-07-10 16:43:33 UTC,"I've updated the man page from fx57 to fx68. please include the attached
new version"
1734975,2018-02-26 10:59:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1734975,2017-12-04 11:17:20 UTC,"finally noticed the attachment button, apologies for cluttering the bugreport"
1734975,2017-12-04 11:15:54 UTC,"I made a small adjustment to the man page (dropped mozilla(1) from ""see also"") --> https://bugzilla.redhat.com/attachment.cgi?id=1362629"
1734975,2017-11-30 15:37:20 UTC,"I've written a man page, starting from Fedora's. see--> https://bugzilla.redhat.com/attachment.cgi?id=1360974"
1734980,2019-09-19 14:46:33 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1734980,2018-04-23 18:51:35 UTC,I'm unable to reproduce this issue. It may have been related to the OS itself.
1734980,2017-11-29 00:27:31 UTC,"14:05 < tyhicks> roaksoax: I can verify that at least the `apt autoremove --purge maas` command in your paste doesn't remove the /dev/shm/squid-cf__metadata.shm
                 file
14:06 < tyhicks> mode 600, owner proxy:proxy
14:12 < tyhicks> roaksoax: `chmod a+rw /dev/shm/squid*.shm` ""fixes"" the errors and allows the squid proxy to start
14:13 < tyhicks> roaksoax: the squid proxy from the snap is running as the 'nobody' user, which is why it can't open the shared memory files left behind by the
                 deb (mode 600, owner proxy:proxy)
14:13 < tyhicks> roaksoax: imo, the bug is in the deb not removing those files upon purge
14:14 < tyhicks> jdstrand: ^ thanks for throwing out that idea"
1734983,2018-01-25 21:16:26 UTC,Fix minor regression in Docker plugin (explained in comment #20) for Trusty [lp1734983-trusty-docker.debdiff]
1734983,2018-01-29 15:43:22 UTC,I just did a new upload of sosreport in TXA to cover the minor regression found in the Docker plugin.
1734983,2018-01-29 15:47:00 UTC,Mark the bug to verification-failed-$RELEASE for now until the Docker plugin fix land in -proposed.
1734983,2018-02-01 11:26:54 UTC,"Hello Eric, or anyone else affected,"
1734983,2018-02-08 08:54:24 UTC,"The verification of the Stable Release Update for sosreport has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1734983,2018-02-01 14:50:03 UTC,"I verified the new Docker plugin fix in sosreport 3.5-1 in -proposed and everything is fine now. No more docker plugin errors in sos_logs and no errors in the output, and I verified the data collected looks good:"
1734983,2018-02-08 08:54:18 UTC,This bug was fixed in the package sosreport - 3.5-1~ubuntu17.10.2
1734983,2018-01-25 21:15:44 UTC,Fix minor regression in Docker plugin (explained in comment #20) for Xenial [lp1734983-xenial-docker.debdiff]
1734983,2018-02-08 08:57:03 UTC,This bug was fixed in the package sosreport - 3.5-1~ubuntu16.04.2
1734983,2018-02-08 09:09:03 UTC,This bug was fixed in the package sosreport - 3.5-1~ubuntu14.04.2
1734983,2018-02-01 11:36:38 UTC,"Hello Eric, or anyone else affected,"
1734983,2018-01-25 21:15:10 UTC,Fix minor regression in Docker plugin (explained in comment #20) for Artful [lp1734983-artful-docker.debdiff]
1734983,2018-02-01 11:35:06 UTC,"Hello Eric, or anyone else affected,"
1734983,2018-01-22 14:14:13 UTC,lp1734983-bionic-docker.debdiff
1734983,2017-11-28 19:53:09 UTC,* autopkgtest result (All manual autopkgtest runs (pre-SRU )passed)
1734983,2017-11-28 21:01:39 UTC,Found a severe regression in that it appears many packages = lines no longer work which prevent automatic package detection. Bionic is also affected.
1734983,2017-11-28 21:09:35 UTC,I can reproduce the situation as well with sosreport upstream and v3.5 debian package that I have built for pre-SRU testing.
1734983,2017-11-28 21:21:55 UTC,"Seems like something is broken in the ""package="" mechanism behaviour.
The no longer running plugins that we have identified coincide with recent package add commit :"
1734983,2017-11-28 21:32:24 UTC,Upstream issue - https://github.com/sosreport/sos/issues/1155
1734983,2017-12-07 13:39:21 UTC,Here's the debdiff fixing the regression found by Bryan Quigley.
1734983,2018-01-03 22:39:37 UTC,"v3.5 sponsored for AZXT, waiting for SRU verification team to approve to start building in -proposed."
1734983,2018-01-04 16:06:08 UTC,sil2100 has rejected the first upload and kept the second which include the (LP: #XXXXX) syntax in d/changelog.
1734983,2018-01-22 15:30:51 UTC,"After talking to sil2100 (SRU verification team) even if sosreport was found in zesty-proposed before its EOL, we won't continue the backport in Zesty."
1734983,2018-01-04 16:48:09 UTC,"Hello Eric, or anyone else affected,"
1734983,2018-01-03 22:57:33 UTC,"For SRU,"
1734983,2018-01-04 16:55:52 UTC,"Hello Eric, or anyone else affected,"
1734983,2018-01-04 16:50:18 UTC,"Hello Eric, or anyone else affected,"
1734983,2018-01-16 21:46:07 UTC,Marked Zesty as invalid as it reached end of like on Jan 13 2018.
1734983,2018-01-16 21:47:22 UTC,"Testing done for Trusty, Xenial and Arful with no errors noticed."
1734983,2018-01-16 23:02:38 UTC,"Ran 3.5 version for Trusty, Xenial, and Artful.  No problems appear to have been introduced by this version."
1734983,2018-01-16 23:24:48 UTC,"Ran 3.5 version for Trusty, Xenial, and Artful on a VM that was MAAS-deployed. I have not been able to discover any issues. I also installed it on a bare-metal server running Xenial with no problems as well."
1734983,2018-01-19 20:00:47 UTC,Did an in-depth on Xenial comparing new and old sosreport output and didn't find anything amiss.
1734983,2018-01-04 16:53:59 UTC,"Hello Eric, or anyone else affected,"
1734983,2018-01-22 14:04:52 UTC,1 minor regression found in the docker plugin execution.
1734983,2018-01-15 22:17:11 UTC,"I tested installing the new package in trusty, xenial, zesty and artful in LXD containers. I ran sosreport with the -a option and I didn't notice any errors. Made a few spot checks. LGTM."
1735000,2018-08-10 10:08:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735009,2019-10-04 08:56:30 UTC,This issue was fixed in the openstack/nova 19.0.3 release.
1735009,2019-10-30 14:17:47 UTC,This issue was fixed in the openstack/nova 17.0.13 release.
1735009,2019-09-27 17:48:44 UTC,"Reviewed:  https://review.opendev.org/680871
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e8f418909eb0f6c319e28d6a1eac0471a0a9cee8
Submitter: Zuul
Branch:    stable/rocky"
1735009,2019-09-27 09:01:09 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1735009,2019-09-08 15:13:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/680873"
1735009,2019-09-08 15:09:02 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/680871"
1735009,2019-09-08 14:58:01 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/680869"
1735009,2019-09-07 23:08:28 UTC,"Reviewed:  https://review.opendev.org/523559
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1819718e798fb904644391badc3beb40c181ac39
Submitter: Zuul
Branch:    master"
1735009,2018-08-18 01:29:17 UTC,"Ordinarily this would be High because it was a regression, but it's been regressed so long I'm setting it to Medium."
1735009,2017-11-28 22:51:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523559"
1735009,2019-10-10 09:08:17 UTC,This issue was fixed in the openstack/nova 18.2.3 release.
1735009,2019-10-18 00:18:20 UTC,"Reviewed:  https://review.opendev.org/680873
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=81056d1293ef47ae47cd5f89a7b7937dedf43c3c
Submitter: Zuul
Branch:    stable/queens"
1735010,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1735012,2017-11-29 09:46:55 UTC,"No, I agree. I ended up checking the same pages that you linked by starting with the fill property definition."
1735012,2017-11-29 00:42:43 UTC,"When looking into the SVG specification, I cannot find that 'fill: transparent' is valid SVG code:
https://www.w3.org/TR/SVG/painting.html#SpecifyingPaint
https://www.w3.org/TR/SVG/types.html#ColorKeywords"
1735012,2017-12-01 17:10:59 UTC,"Sorry, just a user here. But I know that SVG compatibility is very important here."
1735014,2017-11-29 00:22:33 UTC,"The attachment ""just_get(): return exit code of scp and cp"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1735023,2017-11-30 23:14:37 UTC,"If you look in /var/cache/apt/archives after installing Ubuntu you'll notice that the packages were in fact downloaded, they just have not been installed."
1735023,2017-11-29 00:23:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1735024,2017-12-11 22:41:55 UTC,"Thanks
Link: https://bugzilla.kernel.org/show_bug.cgi?id=198143"
1735024,2017-12-07 06:02:01 UTC,"Please file an upstream bug at https://bugzilla.kernel.org/
Product: ACPI
Component: Config-Other"
1735024,2017-11-29 18:34:48 UTC,"Of course,
installed 4.15.0-041500rc1-generic kernel from upstream."
1735024,2017-11-29 15:41:43 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1735024,2017-11-29 00:30:08 UTC,This change was made by a bot.
1735024,2018-08-17 17:42:09 UTC,"I have the same issue with an old DELL Dimension C521, after a little debugging I've found that the problematic component is the PCI, it booted using:"
1735028,2017-11-30 23:12:47 UTC,"trying to force modprobe, I get"
1735028,2018-04-06 05:56:39 UTC,Any updates on this bug ? I recompiled the module but same problem exists. Updating the kernel will help?
1735028,2017-11-29 01:12:11 UTC,"oh, yes all kernels affected. (22) up to (46)"
1735036,2017-11-30 20:55:46 UTC,They're not shortcuts like those others you mentioned (they are shortcuts to control the scroll bar actually)
1735036,2017-11-30 13:36:52 UTC,"OK, I understand what you are saying. The focus is changed by my clicking, and so the keyboard events don't go to the list of files anymore."
1735036,2017-11-30 00:41:13 UTC,"This happens because by clicking a column you've focused the column (It does this so they can be re-ordered.)  The key navigation is fine, you just need to click in the view to re-focus it."
1735040,2017-11-30 06:55:26 UTC,"Hi,"
1735058,2020-09-12 07:45:56 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1735064,2017-11-29 04:27:46 UTC,"In senlin-engine num_engine_workers env, must stop all running thread."
1735064,2020-03-09 07:20:06 UTC,I met the same problem in ocata. How did you solve it?
1735066,2018-01-24 22:37:44 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1463
1735071,2019-02-08 18:53:25 UTC,"That's still an issue but it seems to work if started with
$ GTK_IM_MODULE=xim gnome-software"
1735071,2018-12-12 22:11:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735071,2019-09-24 07:55:04 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.12
1735071,2019-09-18 11:43:30 UTC,Confirmed in bionic that gnome-software 3.28.1-0ubuntu4.18.04.12 shows search after pressing Ctrl-F.
1735071,2019-04-18 15:39:36 UTC,Fix proposed upstream: https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/199
1735071,2019-05-28 17:18:19 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu4.19.04.1
1735071,2019-05-13 23:52:04 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu5
1735071,2019-05-20 14:45:15 UTC,"Ok, so I have some trouble with the SRUs addressing this bug. Per SRU policy [1], we in generall only should only aim for fixing 'high-impact bugs'. This bug seems to be marked with an importance of Low, which normally isn't per-se good SRU material (if it was bundled with some other, high-importance changes, the story would be slightly different). That being said, the issue does seem to be quite annoying and getting it fixed can improve the overall user-experience for our LTS users."
1735071,2019-05-20 14:45:31 UTC,[1] https://wiki.ubuntu.com/StableReleaseUpdates#When
1735071,2019-05-20 14:47:03 UTC,"Hello Scott, or anyone else affected,"
1735071,2019-05-20 14:54:00 UTC,"Actually, I don't see an upload for bionic for fixing this bug. The task was already set to 'Fix Committed' - where is the bionic fix committed? Is it in the current bionic gnome-software already?"
1735071,2019-05-20 21:15:37 UTC,"It's committed in the disco packaging repository, but not uploaded. I planned on bundling that change with other changes in an SRU."
1735071,2019-09-17 14:05:37 UTC,"Hello Scott, or anyone else affected,"
1735071,2019-05-27 11:52:00 UTC,"Installing 3.30.6-2ubuntu4.19.04.1 and restarting gnome-software, then ctrl-F does display the widget"
1735071,2019-05-10 14:24:51 UTC,It was fixed on https://gitlab.gnome.org/GNOME/gnome-software/commit/62153c4a
1735071,2019-05-02 07:54:41 UTC,On Ubuntu 19.10 gnome-software 3.30.6-2ubuntu3 Ctrl+F does not open the search bar but closes it if already open by click on the magnifying glass icon.
1735071,2019-05-28 17:08:18 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1735074,2018-06-03 03:18:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571952"
1735075,2017-11-29 05:19:18 UTC,ok
1735079,2018-05-15 00:18:42 UTC,I would also like to use an official Ubuntu box using vagrant on Hyper-V.
1735080,2018-02-21 11:17:54 UTC,Should be fixed by https://review.openstack.org/#/c/521822/
1735080,2018-02-21 11:17:10 UTC,"Change abandoned by Rabi Mishra (<email address hidden>) on branch: master
Review: https://review.openstack.org/523701"
1735080,2017-11-29 06:44:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523701"
1735082,2021-01-10 04:17:40 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1735082,2020-11-10 17:52:18 UTC,Can you reproduce the problem with the latest official upstream version of QEMU?
1735087,2017-12-04 07:03:34 UTC,Issue regarding empty value in the partition array is fixed.
1735087,2017-11-29 07:11:44 UTC,"Further debugging of code, led me to the below function in “cs:ceph-osd-249” charm"
1735088,2017-12-19 04:23:02 UTC,Had to boot to 4.10.0.42 or 4.14.0-11 to get command to run. Issue seen on both 4.13.0-17-generic and 4.13.0-19-generic.
1735088,2018-07-20 10:44:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735092,2018-10-05 07:41:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735092,2019-09-11 15:53:35 UTC,how to fix it:
1735096,2020-03-31 11:54:41 UTC,"Change abandoned by Spyros Trigazis (<email address hidden>) on branch: master
Review: https://review.opendev.org/523837
Reason: The magnum team is cleaning up the backlog of changes older than 30 days. Feel to restore your patch."
1735096,2017-11-30 11:59:17 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/524151"
1735096,2017-11-30 12:01:42 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/524152"
1735096,2017-11-30 13:23:33 UTC,When you boot a fedora atomic image without magnum. Do you see the same problem?
1735096,2020-03-31 11:54:14 UTC,"Change abandoned by Spyros Trigazis (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/524151
Reason: The magnum team is cleaning up the backlog of changes older than 30 days. Feel to restore your patch."
1735096,2020-03-31 11:55:10 UTC,"Change abandoned by Spyros Trigazis (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/524152
Reason: The magnum team is cleaning up the backlog of changes older than 30 days. Feel to restore your patch."
1735098,2018-01-06 07:12:36 UTC,"There is no mechanism to distinguish between a private repository you can't see and a non-existent repository over HTTPS. I don't think this is solveable in the general case. I guess we could special-case a lp-user passed (or inferred) that matches gitubuntu.lpuser (which is supposed to be your LP username)? In that case, we could assume you don't have inaccessible repositories? Still seems fragile."
1735098,2017-11-29 08:19:49 UTC,"Setting prio to low as it:
- isn't nice but doesn't break anybody
- I don't have a good suggestion what would be better"
1735099,2019-09-15 17:51:40 UTC,The linked github repository doesn't break out whatever the fix is to the rtsx_pci driver is. Therefore it is all but impossible to figure out what was changed.
1735099,2017-11-29 09:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1735099,2019-09-16 09:52:52 UTC,"Austin, thanks for confirming that repository solves the issue for you. I'll try to make a diff of the original commit to that repository against the Linux mainline driver at the same date, maybe we can be lucky and it'll make the required change clear so we can test it in Ubuntu and then get it into mainline kernel."
1735099,2019-09-15 18:59:03 UTC,"Just wanted to update, I am the user TJ is referring to. The issue was resolved after running ""sudo update-initramfs -u"" after the commands in the readme of the linked github repository as detailed here: http://baby-panda.github.io/linux/RTS5229_driver/"
1735099,2017-12-04 21:00:57 UTC,"Thank you for providing a patch, and making Ubuntu better."
1735099,2017-11-30 17:52:17 UTC,And I also confirm that with my patched driver it works.
1735099,2017-11-30 17:35:48 UTC,"[  206.772216] mmc0: cannot verify signal voltage switch
[  206.905871] mmc0: new ultra high speed SDR104 SDXC card at address e624
[  206.922669] mmcblk0: mmc0:e624 AGGCE 59.5 GiB
[  206.925214]  mmcblk0: p1
[  207.035917] mmcblk0: error -110 sending stop command, original cmd response 0x0, card status 0x800b00
[  207.144193] mmcblk0: error -110 sending stop command, original cmd response 0x0, card status 0x800b00
[  207.248391] mmcblk0: error -22 sending status command, retrying
[  207.248501] mmcblk0: error -22 sending status command, retrying
[  207.352460] mmcblk0: error -110 sending status command, aborting
[  207.638463] mmc0: cannot verify signal voltage switch
[  207.873795] mmcblk0: error -22 sending status command, retrying
[  207.873882] mmcblk0: error -22 sending status command, retrying
[  207.977983] mmcblk0: error -110 sending status command, aborting
[  207.977994] print_req_error: I/O error, dev mmcblk0, sector 24
[  208.186497] mmcblk0: error -110 sending status command, retrying
[  208.188696] mmc0: tuning execution failed: -22
[  208.188703] mmcblk0: error -22 sending status command, retrying
[  208.290773] mmcblk0: error -110 sending status command, aborting
[  208.290786] print_req_error: I/O error, dev mmcblk0, sector 24
[  208.290794] Buffer I/O error on dev mmcblk0, logical block 3, async page read
[  208.543367] mmcblk0: error -110 sending status command, retrying
[  208.545617] mmc0: tuning execution failed: -22
[  208.545624] mmcblk0: error -22 sending status command, retrying
[  208.647564] mmcblk0: error -110 sending status command, aborting
[  208.647576] print_req_error: I/O error, dev mmcblk0, sector 124735360
[  208.856057] mmcblk0: error -110 sending status command, retrying
[  208.858352] mmc0: tuning execution failed: -22
[  208.858359] mmcblk0: error -22 sending status command, retrying
root@zibrixnb:/home/zibri# uname -a
Linux zibrixnb 4.15.0-041500rc1-generic #201711262030 SMP Mon Nov 27 01:32:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
root@zibrixnb:/home/zibri#"
1735099,2017-11-29 15:40:01 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1735099,2017-11-29 09:13:57 UTC,https://github.com/Zibri/Realtek-rts5229-for-4.4-kernel
1735099,2017-11-29 09:13:27 UTC,"Nevermind, I successfully compiled the module on 4.13 kernel...
But can I ask what is wrong in the main kernel module?
Can someone fix it?"
1735099,2019-09-16 10:07:35 UTC,Just to be clear the device Austin is dealing with is:
1735111,2018-01-24 22:37:48 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1464
1735111,2017-11-29 09:07:44 UTC,"How to reproduce:
I'm starting master-slave setup from:"
1735120,2017-12-15 12:51:38 UTC,[sorry - it posted without me finishing for some reason]
1735120,2017-12-12 11:34:46 UTC,"I think I'd rather just have the stdout/stderr always pointed to a single file (eg, /var/log/juju/jujud-machine-0-errors.log) or something to that effect.
Having a different log rotation mechanism mostly just complicates the system. (you have to somehow sighup juju itself to allow it to reopen its file handles, without also restarting all of the 1000s of units that are actively communicating with juju.)"
1735120,2017-11-29 18:56:30 UTC,"That seems like a plausible solution, although it might be awkward trying to debug and not knowing where in the log file a given panic happened (note that a panic print doesn't necessarily imply a restart - the HTTP handler prints panic stack traces too AFAIR). Another possibility might be to move log rotation out of juju into another program that reads juju's and writes it to the appropriate file, rotating/compressing logs as appropriate."
1735120,2017-11-29 14:37:03 UTC,"That would make sense. Not too hard to test if you leave a controller running at DEBUG or TRACE log level and fill up the log file. (You can add a lot of empty models, or deploy a lot of dummy charms to one machine if you want to speed it up a bit.)"
1735120,2017-11-29 12:44:19 UTC,"I definitely killed the right process, but when I tried to reproduce the issue again, I didn't see it."
1735120,2017-11-29 11:34:00 UTC,"(just to complete, I also see the traceback using 2.3rc2)"
1735120,2017-11-29 11:27:24 UTC,"I tried doing a -QUIT to the exec-start.sh process, but that seemed to just ignore the kill.  I can see it being easy to try to kill the wrong process, given:
root      3341  3337  0 11:24 ?        00:00:06 /var/lib/juju/tools/machine-0/jujud machine --data-dir /var/lib/juju --machine-id 0 --debug"
1735120,2017-11-29 11:22:36 UTC,"I did a quick test, bootstrapping juju 2.2.6 on lxd, and I can't reproduce this.
I see the traceback in the machine-0.log file as expected
...
goroutine 3501 [select, 1 minutes]:
github.com/juju/juju/worker/catacomb.(*Catacomb).add.func2(0xc420a9f4a0, 0x7ff97c6216d0, 0xc4208b1320, 0xc4208b13e0)
        /tmp/tmpwONtpt/juju-core_2.2.6/src/github.com/juju/juju/worker/catacomb/catacomb.go:181 +0x152
created by github.com/juju/juju/worker/catacomb.(*Catacomb).add
        /tmp/tmpwONtpt/juju-core_2.2.6/src/github.com/juju/juju/worker/catacomb/catacomb.go:187 +0xe1"
1735120,2017-12-15 12:46:24 UTC,"> Having a different log rotation mechanism mostly just complicates the system. (you have to somehow sighup juju itself to allow it to reopen its file handles, without also restarting all of the 1000s of units that are actively communicating with juju.)
"
1735135,2017-11-29 09:55:03 UTC,"I tried changing the composition (originally on OpenGL 3.1), but it does not seem to affect this."
1735154,2018-09-27 15:40:31 UTC,This issue was fixed in the openstack/ovsdbapp 0.12.2 release.
1735154,2019-02-12 09:17:48 UTC,"Change abandoned by Miguel Angel Ajo (<email address hidden>) on branch: master
Review: https://review.openstack.org/602490"
1735154,2019-02-12 09:16:53 UTC,"Change abandoned by Miguel Angel Ajo (<email address hidden>) on branch: master
Review: https://review.openstack.org/602397
Reason: Not needed anymore"
1735154,2018-10-26 15:47:21 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/603354"
1735154,2018-09-27 15:40:21 UTC,This issue was fixed in the openstack/ovsdbapp 0.10.2 release.
1735154,2018-09-20 10:41:04 UTC,Finally!
1735154,2018-04-13 13:30:15 UTC,"This bug still shows up, adding more info after some investigation:"
1735154,2018-09-13 17:06:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/602397"
1735154,2018-09-25 21:07:52 UTC,This issue was fixed in the openstack/ovsdbapp 0.13.0 release.
1735154,2018-09-13 22:27:07 UTC,"After almost getting blind debugging and comparing against the working case, I can see that when the traffic to the FIP is not working, there's no SNAT entry for the gateway:"
1735154,2018-09-13 22:49:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/602490"
1735154,2018-09-14 03:34:30 UTC,"Change abandoned by Miguel Angel Ajo (<email address hidden>) on branch: master
Review: https://review.openstack.org/602449
Reason: in favor of https://review.openstack.org/#/c/602490/1"
1735154,2018-09-17 16:18:11 UTC,Confirmed through logs that the gateway port at least is not present in the router after I analyzed other logs:
1735154,2018-09-13 20:41:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/602449"
1735154,2018-09-17 16:34:38 UTC,You nailed it down dude!!! :)
1735154,2018-09-18 10:37:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/603354"
1735154,2018-09-18 10:26:41 UTC,"Also, the problematic router gets created while another router is getting created at the same time:"
1735154,2018-09-18 10:29:20 UTC,"Sep 14 22:08:58.665604 ubuntu-xenial-rax-dfw-0002028832 neutron-server[345]: DEBUG ovsdbapp.backend.ovs_idl.transaction [-] Running txn n=1 command(idx=0): AddLRouterCommand(ma
y_exist=True, columns={'external_ids': {'neutron:gw_port_id': u'b26d240d-e5f1-452a-b42b-2d74b815799c', 'neutron:router_name': u'tempest-TestSecurityGroupsBasicOps-router-184247
8056', 'neutron:revision_number': '2'}, 'enabled': True, 'options': {}}, name=neutron-780c5403-d1f2-44a3-9c98-9153cce6caec) {{(pid=467) do_commit /usr/local/lib/python2.7/dist-
packages/ovsdbapp/backend/ovs_idl/transaction.py:84}}"
1735154,2018-09-18 10:24:05 UTC,More debugging.
1735155,2020-01-06 10:56:35 UTC,"Hello,
4.10.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1735160,2019-05-29 08:46:05 UTC,"Ok, let's forget about that SRU, it's a priority anymore and it would need work, deleting the protobuf buggy upload from xenial-proposed"
1735160,2019-05-29 08:41:04 UTC,"httmock was in xenial/NEW but I'm going to reject it, the livepatch UI work changed since that bug was started and we are not targetting Xenial anymore at this point, the SRU has been sitting there for over a year so I'm just going to wontfix for now and delete the uploads from xenial-proposed"
1735160,2019-02-25 15:49:26 UTC,"@Brian - it was already meant to be marked verification-failed per comment #33 , so IMHO there is no hope anymore to get this verified.
Further there is work incoming for ua-tools in Xenial (and Trusty), for that I'd really appreciate if this could be removed from proposed even sooner than after 15 days - to have some clarity on the versions we will work with."
1735160,2019-02-20 07:34:27 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for xenial for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1735160,2018-03-22 12:00:32 UTC,@sil2100 I see them both here (https://launchpad.net/ubuntu/artful/+queue) and here (https://launchpad.net/ubuntu/xenial/+queue)
1735160,2018-06-13 17:48:44 UTC,@sil2100  can you take another look into this?
1735160,2018-04-11 17:26:54 UTC,"@sil2100 please find attached an updated debdiff for protobuf. I just replaced this line:
TestGetAndDeserialize('optional_uint32', 1 << 31, long)"
1735160,2018-03-22 15:27:03 UTC,"@azzar1 the protobuf package I have accepted into xenial-proposed FTFBS for some architectures. Could you take a look at that? I didn't look at those yet at all, maybe they just need a re-build."
1735160,2018-03-22 13:53:46 UTC,"Hello Andrea, or anyone else affected,"
1735160,2018-03-22 12:28:42 UTC,"Ok, those are NEW packages. Just by looking at the UNAPPROVED queue and the bug description it was not clear (although I should have just looked up the source - but on the other hand there was no reason if I didn't see an upload). Maybe it would be best if it was made clear that py-macaroon-bakery is a NEW package for those series. Anyway, this is now noted. Thanks!"
1735160,2018-03-22 11:16:03 UTC,"Ok, this bug is confusing me. I do not see py-macaroon-bakery in either the xenial nor artful queues. There is also no httmock for xenial as well. I can take a look at the xenial pymacaroons and protobuf, but I guess we're still missing the py-macaroon-bakery uploads which seem to be very important."
1735160,2018-09-13 18:43:36 UTC,"Marked verification-failed for clarity due to the build failures.  Andrea, are you blocked on sponsorship for fixing protobuf?"
1735160,2018-03-16 11:19:31 UTC,@azzar1 You marked this bug as verification-failed-artful - does it mean the pymacaroons package is broken? Usually when a package is marked as -failed it is a sign for the SRU/AA team to remove the package from -proposed - is this the case here? Your comment implies as if we're just waiting for another part of the fix instead.
1735160,2017-11-29 18:13:09 UTC,Please find attached the proposed debdiff to add python3-protobuf.
1735160,2017-11-29 18:59:11 UTC,I've also created a testing ppa: https://launchpad.net/~azzar1/+archive/ubuntu/bug-1735160
1735160,2017-12-11 16:23:51 UTC,"The attachment ""protobuf.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1735160,2017-12-13 14:38:04 UTC,"py-macaroon-bakery cannot be imported as it is (otherwise we'll need to update the version of protobuf and python3-nacl in xenial, breaking all applications already using it). Please find attached the proposed debdiff."
1735160,2017-12-18 03:07:24 UTC,"I feel like an ack/nack from the SRU Team before sponsoring would be preferred, given that this is a bit of a special case. Subscribed."
1735160,2018-01-09 11:38:54 UTC,"Andy asked me to have a look, so here's my initial feedback."
1735160,2018-01-09 15:02:38 UTC,"pymacaroons does have one potentially-interesting backward-incompatible change, which is that Caveat.caveat_id and Macaroon.identifier are now bytes rather than str.  I think the only place this is at all likely to cause a problem in xenial is in snapcraft, and it's definitely worth checking whether ""snapcraft login"" still works."
1735160,2018-01-09 15:28:17 UTC,"""snapcraft login"" seems to work fine here."
1735160,2018-03-16 14:44:49 UTC,@sil2100 pymacaroons packages works fine. But can you please take care of the other ones too. They've been waiting in the queue for quite some time.
1735160,2018-01-09 15:32:26 UTC,"On Tue, Jan 9, 2018 at 12:38 PM, Iain Lane <email address hidden> wrote:"
1735160,2018-03-22 12:05:18 UTC,"Hello Andrea, or anyone else affected,"
1735160,2018-01-10 13:34:51 UTC,Splitted in 3 patches.
1735160,2018-01-12 12:21:00 UTC,"Should all be uploaded now, thanks! Please check what I did for py-macaroon-bakery in artful (https://launchpadlibrarian.net/353259789/py-macaroon-bakery_0.0.6-1_0.0.6-1~ubuntu17.10.1.diff.gz) in case I messed it up somehow."
1735160,2018-01-10 11:26:35 UTC,Please find attached the updated protobuf.debdiff. As suggested I applied the following patches and it seems to work just fine:
1735160,2018-01-17 17:05:07 UTC,"> The problem is that if you upgrade from Xenial to Zesty or (soon) Artful and we haven't SRUed the fixes then users could either become unfixed or in some cases (didn't check / don't remember for this bug) package versions might go backwards.
"
1735160,2018-01-17 17:17:21 UTC,"On Wed, Jan 17, 2018 at 05:05:07PM -0000, Robie Basak wrote:

> > The problem is that if you upgrade from Xenial to Zesty or (soon)
> Artful and we haven't SRUed the fixes then users could either become
> unfixed or in some cases (didn't check / don't remember for this bug)
> package versions might go backwards.
>
> Worse, a user may not receive future security updates for the package in
> Artful.
"
1735160,2018-02-08 10:17:42 UTC,Any news on this?
1735160,2018-02-28 00:21:16 UTC,"Hello Andrea, or anyone else affected,"
1735160,2018-03-15 10:46:37 UTC,"python3-pymacaroons works properly, but python3-macaroonbakery is not in proposed yet so I cannot mark this bug as verification-done."
1735160,2018-01-11 10:54:25 UTC,Uploaded protobuf to the Xenial SRU queue. I fixed some things from your diff:
1735160,2018-01-11 14:06:07 UTC,Uploaded py-macaroon-bakery and pymacaroons to the queue (unapproved and new respectively). I'll look at the 17.10 stuff after lunch.
1735160,2018-01-11 12:19:43 UTC,Oh I removed the python3 patch from the series but the not actual file.
1735167,2018-12-03 21:03:51 UTC,"A user at askubuntu has found that deinstalling `fonts-noto-color-emoji` ""solves"" the problem with emacs crashing on an emoji https://askubuntu.com/questions/1076735/emacs-crashes-on-pasting-the-unicode-symbol/1098111#1098111"
1735167,2018-09-19 22:31:37 UTC,The emacscrashfile also crashes my 18.04 LTS emacs 24.5.1.
1735167,2018-09-19 22:16:44 UTC,"I find that “⛔” will crash my 18.04 LTS emacs 24.5.1, see https://askubuntu.com/questions/1076735/emacs-crashes-on-pasting-the-unicode-symbol"
1735167,2018-09-19 22:14:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735167,2017-11-29 12:56:15 UTC,Added package name emacs24
1735169,2017-12-11 09:18:00 UTC,Hey Sam!
1735169,2018-02-09 10:00:45 UTC,"I really like the idea, please post a spec for it."
1735175,2018-10-16 18:26:32 UTC,Is there any plan to implement this or is there any work around?
1735178,2018-02-16 13:35:50 UTC,I just saw this bug report. Please report bugs upstream in the future. Does this issue still occur with the latest version of tilda?
1735178,2018-02-16 16:46:49 UTC,Hey Sebstian. Sorry for that. Next time will directly report upstream.
1735186,2018-09-26 05:10:00 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/403
1735188,2017-12-07 23:55:49 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1735188,2017-12-01 15:45:32 UTC,"Reviewed:  https://review.openstack.org/524157
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b1aa3ed01769f75b2fff16fb4e77269686c061b3
Submitter: Zuul
Branch:    stable/pike"
1735188,2017-11-30 12:26:46 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/524157"
1735188,2017-11-29 15:43:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/523914"
1735188,2017-11-29 15:22:37 UTC,"> 16.0.0 to 17.0.0
"
1735188,2017-12-18 12:51:33 UTC,This issue was fixed in the openstack/nova 16.0.4 release.
1735188,2017-11-30 12:21:40 UTC,"Reviewed:  https://review.openstack.org/523914
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e727437b0ccdcc15e8ccd9b7a7c232a878dadd2d
Submitter: Zuul
Branch:    master"
1735192,2018-02-16 12:15:37 UTC,"Since the file locates in https://git.openstack.org/cgit/openstack/openstack-resource-agents/ , the file needs to be fixed IMO."
1735192,2018-01-02 19:43:33 UTC,"This looks like a bug in the HA guide, which should be in the openstack-manuals project. Adding openstack-manuals to this report for further clarification."
1735192,2018-02-19 10:47:35 UTC,"Yes this is correct, I have done a bad job of maintenance here. I should have some time to address it at the PTG next week."
1735192,2019-05-21 12:20:32 UTC,seems not related to openstack-manuals
1735202,2017-12-26 15:32:16 UTC,What exactly would Ubuntu pick up from Microsoft? Ubuntu doesn't offer Microsoft Office or the Microsoft Edge web browser.
1735202,2017-11-30 14:52:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1735202,2017-11-30 16:10:48 UTC,"Really?
All I am asking for is compatibility to pick up handed off websites and
documents from my mobile devices using my signed in Microsoft account"
1735202,2019-02-08 04:42:33 UTC,"This feature should work with Microsoft's new open source Graph API, as long as it's implemented and integrated into the OS (or software)."
1735204,2019-11-27 15:09:16 UTC,Try:
1735205,2017-11-29 16:13:46 UTC,"OK so this is not a quick fix (and its release day tomorrow so I don't want to land a largish change into nova-cc right now);  my recommendation for right now is that you fork the charm and update the template as needed to define the required alias keys;  once we have a thought through solution via configuation, we'll land in master, backport to stable 17.11 and you'll them be able to switch back to the mainline stable charm."
1735205,2017-11-29 16:43:48 UTC,"This is not a field critical bug. Lorenzo, please re-evaluate the criteria and prioritize accordingly."
1735205,2018-01-18 14:35:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535350"
1735205,2018-10-10 16:27:58 UTC,"Reviewed:  https://review.openstack.org/535350
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=630a07013f5d1402df7b2c70870c463398fe9450
Submitter: Zuul
Branch:    master"
1735207,2018-03-15 00:52:27 UTC,"Hm, for some reason the merge proposal for this didn't get linked. This landed in MAAS 2.4."
1735207,2017-12-01 17:19:12 UTC,I agree the bug priority should stay high but it doesn't need to be covered under the field high SLA. It doesn't match the criteria.
1735207,2017-11-30 13:58:46 UTC,By unobvious I meant that the path from seeing the symptom to deciding where the problem is and how to fix is not obvious.
1735207,2017-11-29 18:00:31 UTC,As per the bug report from Jeff:
1735207,2017-11-29 16:24:02 UTC,My apologies for this omission on the initial report.
1735207,2017-11-29 16:09:28 UTC,Escalating to high (has unobvious workaround)
1735213,2018-05-11 22:09:31 UTC,"I provided the OS version, but forgot to mention the OS name, which is FreeBSD."
1735213,2020-09-12 06:50:16 UTC,Closing because INVALID: Fix Released.
1735218,2018-04-06 10:29:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735218,2017-11-29 17:06:24 UTC,This will most likely also be triggered in the case when a self-signed CA is used to sign an https proxy server certificate.
1735221,2017-11-29 17:30:17 UTC,Marking as confirmed.  Bug was originally reported by me and confirmed by Andrea Buntz Neiman.
1735221,2018-06-05 18:40:24 UTC,Confirming that this is still an issue in 3.1
1735221,2019-08-09 16:34:51 UTC,This issue continues in 3.3
1735221,2020-06-23 20:52:06 UTC,Confirmed bug is still present in 3.5
1735224,2018-02-06 04:14:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735228,2018-01-06 07:08:57 UTC,"-devel branches being out of date is unrelated, most likely; as it is a known issue with the importer right now (being out of date). I'll try and reproduce this next week."
1735228,2017-11-29 18:54:43 UTC,This fixes the call to derive_source_from_changelog()
1735250,2017-11-29 19:33:35 UTC,"This is an issue with the SQLAlchemy hybrid_property.expression use in the user ref, where .expression is returning Password.password."
1735250,2017-12-04 02:18:56 UTC,"Strange, I can't reproduce with Master branch (backend is Mysql)"
1735250,2017-12-04 14:29:06 UTC,"wangxiyuan,"
1735250,2017-12-06 09:34:35 UTC,"Still can't reproduce
use keystone stable/pike branch and postgresql: psql (PostgreSQL) 9.5.10"
1735250,2017-12-06 21:45:56 UTC,the test case that first hit this issue (and can consistently reproduce in our environment) was doing password update operations for admin users (those assigned an admin role).
1735250,2018-10-29 03:18:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613830"
1735250,2019-03-21 14:55:53 UTC,This issue was fixed in the openstack/keystone 15.0.0.0rc1 release candidate.
1735250,2018-10-29 02:55:14 UTC,This error happens if Sqlalchemy lib's version < 1.1. Bump its version to >=1.1 can solved this problem.
1735250,2018-03-20 06:58:27 UTC,Hey i am not able to reproduce the bug with Pike environment .
1735250,2018-02-16 20:03:30 UTC,"Sorry, missed that discussion."
1735250,2018-02-16 19:53:51 UTC,"Lance, yes in our testing and the results I discussed with you guys on IRC, we were using the keystone admin account. The Keystone admin account has an admin role on the admin project. I have not attempted to reproduce this with other accounts."
1735250,2018-02-16 19:42:42 UTC,Marking incomplete while waiting on an answer to Lance's clarification question.
1735250,2018-11-27 21:56:24 UTC,"Reviewed:  https://review.openstack.org/613830
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bc6b2f1b0b70b9906d5d1ccade1e82b48f87fa38
Submitter: Zuul
Branch:    master"
1735250,2018-01-02 19:49:07 UTC,"The same hashing process should take place regardless of creating a new user or updating the password for an existing user by an admin. Kam, are you saying you can only recreate this using the admin override?"
1735250,2018-10-29 02:57:12 UTC,"sqlalchemy log:
https://docs.sqlalchemy.org/en/latest/changelog/changelog_11.html#change-a2c32a48b7c0700784bb0b7a87dd1f3f"
1735264,2017-11-29 20:17:21 UTC,I would not change the default of not doing anything at all.
1735264,2017-11-30 13:18:57 UTC,"I just remembered another use case where the agent should monitor and terminate a process, see https://bugs.launchpad.net/juju/+bug/1638332/comments/4"
1735264,2017-11-30 07:04:22 UTC,"> any suggestion where this could fit?
"
1735264,2017-11-29 21:13:34 UTC,"On Wed, Nov 29, 2017 at 08:17:21PM -0000, Dmitrii Shcherbakov wrote:

> I would not change the default of not doing anything at all.
>
> I agree that it helps debugging such charm issues (encountered that
> myself - they are really annoying to debug) but I am more inclined to
> ""warn on runs for too long"" rather than ""kill on runs for too long"".
"
1735271,2018-02-09 17:01:47 UTC,"linux-firmware for bionic has been rebased onto upstream commit 2aa2ac2e9c09f09b0cfb6fc320c1e2d281530fa0 and now includes this merge. Changing status to fix committed, I will be uploading a new linux-firmware for bionic soon."
1735271,2018-01-16 07:59:28 UTC,"Updated Netronome firmware is present upstream as of (merge) commit bc2164d5ed78.
This includes:
* Flower firmware for flow offload, including hardware offload of OvS using TC flower
* CoreNIC 2.0, previously Core NIC 1.0. CoreNIC firmware allows Netronome SmartNICs to provide features similar to more traditional, non-SmartNICs."
1735284,2020-04-30 04:17:06 UTC,"Yes, I'd say Swift is definitely interested in being compatible here, it's mainly a matter of havine time to implement it. There have been some other S3-related features (like versioning) that saw more interest so got implemented first, as well as other Swift-related bugs and features."
1735284,2020-03-18 21:35:36 UTC,"Oh hey, they started documenting it!"
1735284,2019-01-18 19:57:28 UTC,"Apparently I can't mark this ""Won't Fix"" for swift3, but any fix will appear in s3api, and won't be backported."
1735284,2019-01-18 19:55:06 UTC,:-(
1735284,2018-11-06 17:59:06 UTC,So the feature seems legit/supported:
1735284,2020-04-28 18:34:42 UTC,Any idea if there will be progress on getting this added to Swift?
1735285,2018-01-04 16:58:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/531200"
1735285,2018-01-18 17:39:48 UTC,"Reviewed:  https://review.openstack.org/531200
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=04d7e2d80d4cfe0d3a2cae477d9e09b6dc1071a2
Submitter: Zuul
Branch:    master"
1735285,2017-11-29 20:58:58 UTC,"Note: on the machine I tried this on, I modified the Barbican policy to allow any user to access ""creator"":"
1735288,2018-02-20 15:56:48 UTC,My current solution is to not use netplan at all.
1735288,2018-01-10 19:45:21 UTC,I can see the benefit in having that particular feature for the really complex features in wpasupplicant.
1735288,2018-05-29 10:19:29 UTC,"First of all, thank you very much for the netplan!"
1735288,2020-05-15 07:26:01 UTC,"Complex authentication, such as 802.1x and WPA Enterprise (incl. Phase 2/MSCHAPv2) are supported natively in netplan as of v0.99."
1735291,2018-01-22 23:15:11 UTC,"Re-assigning to the greeter. LightDM doesn't interact with fonts in any way, so it's more likely something related to the greeter doing this."
1735296,2017-12-12 10:50:19 UTC,"Correct, purging resolvconf is only supported ""out of the box""/""just works"" in 17.10 and up, as resolvconf/libnss-resolve there have the correct maintainer scripts to do the tansition."
1735308,2017-11-29 23:05:07 UTC,"(for all these documentation issues, no bug triage is needed. They are just meant as reminders for https://gitlab.com/inkscape/inkscape-docs/documentation)"
1735310,2019-05-15 16:26:39 UTC,I'm seeing this on 3.3 using Chrome on a MacBook Pro.
1735311,2017-12-01 20:23:11 UTC,"Hi Dimitrii,"
1735311,2017-12-01 21:29:35 UTC,See the attachment - reproduced on a different environment.
1735311,2018-08-13 20:20:38 UTC,"Hi Dmitrii,"
1735311,2019-10-21 12:53:41 UTC,"I cannot reproduce this on the latests master, Dmitrii can you confirm it is still an issue?"
1735311,2019-09-19 15:16:50 UTC,Still reproducible with 2.6.1.
1735311,2019-09-19 14:53:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1735311,2018-10-13 04:18:15 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1735311,2018-08-13 21:56:45 UTC,"Hi Andres,"
1735311,2017-12-01 21:24:22 UTC,"Andres,"
1735316,2017-12-04 03:55:21 UTC,Thank you for your kind attention.
1735316,2017-11-30 00:59:04 UTC,When have time i put a extra optional parameter to hide the knot. Also you can set it default off in 0.92+devel
1735316,2017-12-06 23:36:58 UTC,Dome MR. https://gitlab.com/inkscape/inkscape/merge_requests/157
1735318,2018-07-23 21:21:26 UTC,"I think the netplan python wrapper needs help, what you can do is:"
1735318,2018-02-05 16:37:58 UTC,"Use Case 3:
  I'm a sysadmin with lots of server where network config is generated by scripts. Such scripts should be able to validate that the generated file is valid before deploying it."
1735318,2018-01-10 19:27:45 UTC,Yes! This ties in to other future feature ideas too. Triaging.
1735318,2018-07-22 23:46:43 UTC,I think this is now provided by 'netplan try' in Bionic.
1735318,2018-07-23 00:39:42 UTC,Use case 1 is covered by netplan try. Use case 2 and 3 are not.
1735318,2018-07-23 06:44:44 UTC,"Usecase 2 can be covered with netplan generate --root-dir: create foo/etc/netplan, put the files in there, and do 'netplan generate --root-dir foo'. I think that might cover case 3 as well?"
1735318,2018-07-23 20:56:43 UTC,"I would have expected it to fail with a message about the incorrect YAML:
https://paste.ubuntu.com/p/dv3dgjjQVJ/"
1735318,2018-07-24 01:58:22 UTC,"OK, so we've basically landed in the territory of LP: #1701434."
1735318,2018-07-24 03:47:28 UTC,It looks like at least some of this changed between Bionic and Cosmic - here with a netplan 0.39:
1735321,2017-11-30 02:01:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524038"
1735321,2017-12-27 15:16:36 UTC,"Reviewed:  https://review.openstack.org/524038
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4fd51617fb408fa389baa1aed10db3a06cc1539b
Submitter: Zuul
Branch:    master"
1735321,2018-01-22 10:36:33 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/536297"
1735321,2018-02-15 23:53:33 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1735321,2018-02-08 18:17:01 UTC,"Reviewed:  https://review.openstack.org/536297
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=863515187575b9630c02f7318b94bd2ef9a6f4a9
Submitter: Zuul
Branch:    stable/pike"
1735321,2018-01-26 00:44:27 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1735323,2017-12-01 11:18:45 UTC,"Hi Manoj, is melissaml to add all releasenote?"
1735329,2020-03-26 09:08:51 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/525335
Reason: The patch is stale with negative review. Feel free to restore it (or ping gibi on IRC to do so) if you are still working on this."
1735329,2017-12-01 15:19:54 UTC,"The API should return a 409 in this case I think. It already does return a 409 in other cases, so I think that's a good fit."
1735329,2017-11-30 21:54:05 UTC,Awaiting for someone to triage this report as I am not sure if this is a valid bug.
1735329,2017-11-30 07:06:47 UTC,Set the status to 'In-Progress' because this report has an assignee.
1735329,2017-12-04 22:14:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525335"
1735329,2017-12-01 15:34:19 UTC,"I'm not sure what the default http response timeout is for apache or uwsgi, but keep in mind that the default rpc_response_timeout is 60 seconds, so if we wait for the MessagingTimeout to handle this, we might have already timed out the response to the actual client."
1735329,2017-12-04 22:26:12 UTC,"Hi Matt,"
1735333,2017-11-30 11:51:55 UTC,"Hi, can you do a couple things:"
1735335,2017-12-07 01:39:55 UTC,"Hi Hongbin,
I've already fixed the bug by patch:
https://review.openstack.org/523283"
1735335,2017-12-06 21:14:36 UTC,"Kevin, this bug looks valid. Any reason you marked it as invalid?"
1735343,2018-02-15 23:53:47 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1735343,2017-12-21 19:46:36 UTC,"Reviewed:  https://review.openstack.org/526465
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fa36ccefd28d13435babc5b5fea428db4d372a7b
Submitter: Zuul
Branch:    stable/pike"
1735343,2017-12-09 07:24:19 UTC,"Reviewed:  https://review.openstack.org/524088
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e51a14bc93fc8a0661a3dfab548bad8c19ff2085
Submitter: Zuul
Branch:    master"
1735343,2017-12-07 17:32:34 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/526465"
1735343,2017-11-30 07:34:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524088"
1735343,2018-01-26 00:44:25 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1735346,2017-12-01 21:42:14 UTC,"according to the Debian issue, there is a Python3 port available"
1735346,2017-12-06 14:57:06 UTC,"seems fine to demote, unsure why it's in supported-desktop-extra but that's ancient and doesn't make much sense nowadays"
1735346,2019-02-18 09:41:49 UTC,now demoted
1735346,2018-05-25 23:12:10 UTC,"------------------------------------------------------------
revno: 2680
fixes bug: https://launchpad.net/bugs/1735346
committer: Dimitri John Ledkov <email address hidden>
branch nick: ubuntu.cosmic
timestamp: Sat 2018-05-26 00:11:41 +0100
message:
  The command line tool for torrents is called trasmission-cli
diff:
=== modified file 'supported-desktop-extra'
--- supported-desktop-extra	2018-04-24 16:21:11 +0000
+++ supported-desktop-extra	2018-05-25 23:11:41 +0000
@@ -22,10 +22,6 @@
  * icc-profiles-free
  * vim-gnome"
1735346,2018-05-25 23:10:20 UTC,"And we already have transmission seeded in the desktops. Which is a lot nicer client. I thought it can be a server too, no?!"
1735346,2018-05-25 23:07:47 UTC,What is deployed on torrent.ubuntu.com should not be taken as the best example of how to deploy torrent trackers =)
1735346,2017-12-11 09:14:34 UTC,Best guess as to why it's in main would be that Ubuntu uses it as the torrent tracker (http://torrent.ubuntu.com:6969/)
1735346,2019-10-16 18:20:18 UTC,"Removing packages:
        bittornado 0.3.18-10.3 in eoan
                bittornado 0.3.18-10.3 in eoan amd64
                bittornado 0.3.18-10.3 in eoan arm64
                bittornado 0.3.18-10.3 in eoan armhf
                bittornado 0.3.18-10.3 in eoan i386
                bittornado 0.3.18-10.3 in eoan ppc64el
                bittornado 0.3.18-10.3 in eoan s390x
                bittornado-gui 0.3.18-10.3 in eoan amd64
                bittornado-gui 0.3.18-10.3 in eoan arm64
                bittornado-gui 0.3.18-10.3 in eoan armhf
                bittornado-gui 0.3.18-10.3 in eoan i386
                bittornado-gui 0.3.18-10.3 in eoan ppc64el
                bittornado-gui 0.3.18-10.3 in eoan s390x
Comment: (From Debian) RoQA: removal triggered by the Python2 removal; Debian bug #939180
Remove [y|N]? y"
1735346,2017-11-30 07:58:13 UTC,"dead upstream, last maintainer upload in Debian in 2010. Maybe better to demote."
1735347,2020-04-22 16:08:17 UTC,"Actually, I think the plymouth issue is a side effect.  I notice from the dpkg history log that immediately prior to this issue, PHP was upgraded, including mod-php.  There is a known issue with mod-php upgrades failing, and I suspect that is the root cause here:"
1735347,2018-02-13 20:25:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735348,2017-12-04 14:42:04 UTC,This bug was fixed in the package byobu - 5.123-0ubuntu2
1735348,2017-11-30 07:28:41 UTC,in it's current form the dependencies are broken by just installing python and python3-newt.
1735350,2018-05-25 16:21:42 UTC,"$ seeded-in-ubuntu bzr
bzr's binaries are not seeded."
1735350,2017-12-04 12:58:46 UTC,breezy will become the bzr port to Python3
1735353,2017-11-30 08:07:27 UTC,"WIP patch from Dan Smith:
https://review.openstack.org/#/c/523187/"
1735355,2019-03-27 13:16:14 UTC,Note: security is OK with dropping from main. sust-eng did not respond.
1735355,2019-05-01 15:57:01 UTC,This bug was fixed in the package heartbeat - 1:3.0.6-9ubuntu1
1735355,2019-04-29 09:39:15 UTC,"Right, so either we need pacemaker 2 or we need to port heartbeat to python3."
1735355,2019-03-25 15:23:43 UTC,Deprecation notice: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.0
1735355,2019-03-25 15:01:37 UTC,"Heartbeat has been abandoned since 2015 (ref http://www.linux-ha.org/wiki/Site_news), and so should be dropped from Ubuntu. The new messaging layer to use is corosync https://www.clusterlabs.org/corosync.html"
1735363,2019-09-28 12:13:31 UTC,"Yes the OS defines it, but first within Debian we still have quite a few
packages calling ""python"" and expecting python2, we are still chasing them
down."
1735363,2019-09-29 01:05:56 UTC,"Ah, thank you for explaining, Mattia!"
1735363,2019-09-30 15:05:53 UTC,"> Maybe you could add a cmake option to let the user
> select the python binary?
"
1735363,2019-10-01 10:35:21 UTC,"> * Would you expect the shebang to be adjusted for python3 as well
"
1735363,2019-10-04 21:07:28 UTC,"I think that, apart from the build process, there is only this bit that would need to be chnaged.  So I'm currently doing this, but I'd love to be able to specify that at build time (or for inkscape to detect it by itself, as I suggested above):"
1735363,2020-04-28 00:40:26 UTC,"fixed in latest groovy package:
https://launchpad.net/ubuntu/+source/inkscape/1.0~rc1-3"
1735363,2020-05-02 11:34:45 UTC,Will Inkscape version 1.0 with this fix also go into updates or backports for Focal?
1735363,2020-05-03 09:39:27 UTC,"@mpredotka please file what you are seeing (with as many details as possible) in a different bug, this is totally unrelated."
1735363,2020-05-02 18:20:17 UTC,Now I've installed the stable version from snapcraft. The effects seems to work but the interface looks like old Windows :/
1735363,2020-05-03 09:43:52 UTC,@pander
1735363,2020-05-03 10:02:31 UTC,Thanks for the extra information. I will use the PPA.
1735363,2020-05-05 08:52:12 UTC,Which PPA offers Inkscape 1.0 build for Focal?
1735363,2020-05-05 10:45:27 UTC,"It's going to be the stable one, when the issues with the build failures (due to tests ...) are fixed. No ETA, hopefully within the next couple days."
1735363,2020-05-09 11:50:44 UTC,it's now available in https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable?field.series_filter=focal
1735363,2019-09-28 11:59:28 UTC,"Doesn't the OS define what 'python' refers to?
Are there many other programs that still need Python2 and don't label it as such?"
1735363,2020-05-02 18:10:02 UTC,I've recently installed Ubuntu 20.04 and Inkscape on it. Turns out number of effects from Extensions menu does not work. I can only see a dialog box for a split second and nothing happens. I believe this bug is the problem. So what are the options for the latest Ubuntu LTS users?
1735363,2019-09-28 11:32:51 UTC,"So it seems that in the current 1.0 beta1, there are 6 calls to `python` in the various CMakeLists.txt that I had to patch to use python3."
1735363,2019-06-24 13:14:01 UTC,"Yes, when 0.92.5 is released. Is there an ETA on that?"
1735363,2019-09-26 22:14:19 UTC,So I guess you'll need to update your article. There is nothing about that in the linked release notes draft.
1735363,2017-12-01 17:03:13 UTC,"For the person who wants to work on this:
Some (a lot of?) work on this has already been done by su_v:
https://gitlab.com/su-v/inx-fork"
1735363,2017-12-06 04:47:22 UTC,"Matthias, I dropped the usb seed and I did a tasksel upload that I think dropped the usb task. I don't see any reverse-depends for the inkscape in main. Can you figure out why inkscape is still in main but is not showing up on the component mismatches report?"
1735363,2017-12-06 11:03:18 UTC,now demoted
1735363,2017-12-11 15:29:05 UTC,"While I think it is fine for Inkscape to not be in main, there is a snap for it, if there are those who want to still see it in main another possible solution is to split out the Python extensions. They're independent and could be a separate package with a recommends."
1735363,2018-01-05 14:39:06 UTC,@Hachmann - Thanks for the gitlab link to su_v's work.  Do you know what the status of the fork is?  Is there a wiki page/bug report tracking the migration?
1735363,2018-01-09 23:55:42 UTC,"@valavanisalex Sorry, I don't know much about it. su_v is often around on IRC, please ask her there about the status or send her an email. As far as I know, there is no other place tracking this."
1735363,2018-01-10 01:20:45 UTC,"I'd second Ted's suggestion of splitting out python code to a separate package, that's something we've been pondering doing for other reasons already."
1735363,2018-01-10 01:55:26 UTC,"The main → universe move as I see it has more of a logistic change: theoretically speaking, as long as it is in main Canonical could be called upon providing commercial support if any customer asked for it, as well as providing security patches if any security breach appeared, etc.
At any rate, yes, nothing to be concerned about: actually using a Ubuntu desktop without universe is just plain impossible anyway."
1735363,2019-09-26 22:24:08 UTC,"Yes, we still support Python 2, although the preference is to use Python 3 together with Inkscape 1.0."
1735363,2018-01-10 02:15:24 UTC,"Thank you for the explanation, Bryce and Mattia! But until 2020, this should be solved, as far as I understand, regardless of this? We've only got 2 hackfests until then... time flies."
1735363,2018-01-10 02:39:22 UTC,"One thing we'd need to consider is that some more or less basic Inkscape functionality currently relies on Python extensions, e.g.
- Several templates
- Help links
  although I already wondered if this was even really necessary -
  I assume there are better solutions available to open a link from GTK
- Export/Import extensions
  They are not strictly Inkscape core but a lot of users are not aware
  they might be running an extension to export to their favorite format."
1735363,2018-04-08 20:03:07 UTC,"Some work has been done on this by doctormo during the Hackfest, as far as I understand.
However, the Python3 port has been combined with moving extensions out of the main repo for that branch, so not sure about compatibility and usefulness with/for current Inkscape versions."
1735363,2018-04-08 17:53:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735363,2019-04-29 19:35:48 UTC,Inkscape 0.92.5 as well as Inkscape 1.0 will be compatible with Python 3:
1735363,2019-06-23 19:46:40 UTC,https://bugs.launchpad.net/inkscape/+bug/1735363/comments/14: Inkscape 0.92.5 as well as Inkscape 1.0 will be compatible with Python 3.
1735363,2019-06-25 15:22:21 UTC,What is the ETA for 0.92.5?
1735363,2019-09-26 22:12:07 UTC,"As far as I know, Inkscape 1.0 has not dropped support for Python 2.7, but aims to keep supporting old third-party extensions, so users can still use them, even if their maintainer hasn't updated them yet."
1735363,2019-06-25 22:47:49 UTC,"Last month. [Meaning: sorry, no idea, it was due much earlier, but hasn't been released yet, will probably be before August]"
1735363,2019-09-26 21:53:15 UTC,"I'm working on communications regarding the sunsetting of Python 2.x [0] The way I understand & have phrased my understanding[1] of Inkscape's plans is: Inkscape's LTS 0.92.x line aims to continue supporting Python 2.7 but Inkscape 0.92.5 will also support Python 3, and the 1.0 line will drop support for Python 2. And, as I understand it, Inkscape hopes to release 0.92.5 and 1.0 this calendar year, but that's a hope, not a firm commitment."
1735363,2019-09-10 16:57:44 UTC,"> However the idea for Inkscape (at least the ""LTS"" branch 0.92.x) is to support both, python2 and python3,
"
1735363,2019-08-08 13:37:58 UTC,*** This bug has been marked as a duplicate of bug 1737934 ***
1735363,2019-08-05 20:25:23 UTC,"I see... so some distros basically want to push towards Python 3 but are too afraid to do it ""properly"" by also switching the target of ""python"". ;-)"
1735363,2019-08-05 20:07:24 UTC,"The problem is that in the Linux world there is no real, final, decision on what to do with the name ""python"". So, at least in Debian/Ubuntu, we have no plans on having /usr/bin/python to ever
 point to anything that is not Python 2.  In Arch Linux, the situation is the opposite instead…"
1735363,2019-07-30 17:00:21 UTC,"What's the problem with calling ""python"" (without version number)?"
1735363,2019-04-29 17:07:55 UTC,I was trying to get rid of Python2 packages on my system and I've found that Inkscape depends on Python2.
1735363,2019-07-30 14:34:27 UTC,"There are still a few calls to ""python ... i18n.py"" in share/*/CMakeLists.txt, so the build system still requires python2."
1735368,2018-05-25 23:40:20 UTC,Demotion was commited.
1735368,2019-02-18 09:45:14 UTC,this is demoted now. Is there a python3 equivalent needed?
1735368,2019-02-20 07:20:48 UTC,This was demoted already in cosmic and no one minded.  It was *only* being held in main via the server-ship seed but was not used via the installer so did not belong in server-ship anymore.  There is no python3 replacement in the archive. We should consider this resolved.
1735369,2017-12-06 15:12:05 UTC,(sorry hit enter by mistake)
1735369,2018-01-31 10:28:45 UTC,libglade2 is now demoted.
1735369,2017-12-06 15:31:41 UTC,"the binary is in main because of the seed ""* Extra-Include: *-dbg *-debug *-dev *-doc *-docs gir1.2-* *-examples"" and could be overriden with an extra-Exclude"
1735369,2017-12-06 15:12:45 UTC,(we could also split the script to a new binary and put that one to universe but that seems more work that necessary)
1735369,2017-12-06 15:09:24 UTC,"libglade2-dev depends on python for a small ""libglade-convert"""
1735370,2019-02-21 08:36:41 UTC,livecd-rootfs has been moved to use python3-vmdkstream instead of (python2) vmdk-stream-converter in disco.
1735370,2018-05-25 16:19:33 UTC,We should go ahead and upload this in ubuntu.
1735370,2017-12-07 17:04:02 UTC,"Upstream fix is needed for vmdk-stream-converter:
https://github.com/imcleod/VMDK-stream-converter/pull/3"
1735370,2017-11-30 17:52:57 UTC,"vmdk-stream-converter needs to be converted to python3 first, then livecd-rootfs can switch, too.
I'm writing a patch for the former to be applied in Debian."
1735370,2017-11-30 17:49:08 UTC,"This is only used for vmdk-stream-converter, which lists itself as python2-only; so vmdk-stream-converter needs to be fixed first.  Balint, any chance this is something you would want to look at as part of the dependency clean-up work?"
1735370,2019-02-18 19:40:02 UTC,This bug was fixed in the package vmdk-stream-converter - 0.2-4ubuntu1
1735370,2017-12-07 19:21:43 UTC,Waiting a week for upstream & Debian to accept/review the proposed patches.
1735376,2018-05-25 23:44:17 UTC,"zenmap was demoted to universe
nmap itself does not depend on python"
1735383,2017-12-02 21:50:59 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1735383,2017-11-30 10:30:08 UTC,This change was made by a bot.
1735383,2017-11-30 10:54:45 UTC,appendet the longer debug output. without splash and quiet at kernel parameters
1735383,2017-11-30 11:42:47 UTC,"I now can limit the error to Intel HD Graphics 630 (used in i7 7700) ubuntu 17.10 (maybe also 16.04, had sometimes same trouble with it & unity) AND Xen 4.9. the package I compiled my selfe for 16.04."
1735383,2017-12-04 14:39:04 UTC,"I can confirm that the bug stays the same with the kernel released today.
uname -r: 4.15.0-041500rc2-generic
I plugged in a second monitor into the intel HD Graphics 630 and the GUI crashed as described before."
1735383,2017-12-05 07:14:57 UTC,"The attached script...
I was sure that I did attached it..."
1735395,2017-11-30 11:20:13 UTC,assigning ubuntu-desktop: can it be removed from the seed?
1735395,2017-12-01 08:56:03 UTC,now removed from the seed
1735395,2017-11-30 12:46:32 UTC,confirmed it's fine to unseed
1735395,2017-11-30 11:56:25 UTC,+1 on remove from seed.  Thanks.
1735403,2017-12-01 08:55:25 UTC,now removed from the seed
1735403,2017-11-30 12:01:20 UTC,+1 to remove.  Thanks.
1735406,2017-12-04 02:56:29 UTC,Set the status to 'In Progress' because this report has an assignee.
1735406,2017-12-04 03:23:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525034"
1735406,2019-10-07 14:01:05 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/525034"
1735406,2019-10-16 04:52:52 UTC,Is this bug still being worked on?
1735410,2017-12-19 16:45:23 UTC,"I'm marking this bug as 'bitesize' as it looks like an issue that is easy to fix and suitable for newcomers in Ubuntu development. If you need any help with fixing it, talk to me about it."
1735415,2018-04-11 03:45:07 UTC,Was fixed in lightdm 1.25.1
1735415,2017-12-11 03:29:59 UTC,"Thanks for the fix!
https://github.com/CanonicalLtd/lightdm/commit/8283fc7b84e456760172f042bafc5827b6fcf29e"
1735417,2017-12-04 05:23:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525053"
1735417,2017-11-30 17:10:45 UTC,"Greetings Nisha,"
1735417,2018-01-05 05:46:17 UTC,"Hi Julia,"
1735419,2017-12-14 08:53:08 UTC,The bug is also tracked on the xfce bugtracker: https://bugzilla.xfce.org/show_bug.cgi?id=14073
1735419,2017-12-14 05:57:30 UTC,I confirm this observation. I never saw this issue in Ubuntu main edition that uses the GNOME daemon.
1735419,2017-12-13 20:44:49 UTC,"Someone discussed about this issue on the Chromium bugs list, and thinking that it might be a Chromium issue, I raised the problem again."
1735419,2017-12-10 12:10:50 UTC,I agree. They are very hard to read that way. :-(
1735419,2017-12-10 10:13:17 UTC,"I've waited for ages to finally have native notifications from Chrome, and now they're horrible because of the hyperlinks not being treated well."
1735419,2017-12-10 10:10:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735419,2018-08-21 10:07:11 UTC,"Support for this feature was added in version 0.4.2, but the URL parser still needs some improvement (work in progress)."
1735420,2018-03-27 10:51:06 UTC,Sorry for the delay - got a bit distracted by other topics.
1735420,2019-06-17 19:41:03 UTC,"Since we already reached the stabilization phase of xenial/16.04 with .5 (and .6), with the focus on stability and security, and because this is not a really bug, rather than 'nice to have' to _not_ show /dev/kvm in case already running virtualized on KVM (because nested KVM is not supported on s390x), I'm now going to change this Bug to Won't Fix.
In anybody objects please leave a comment ..."
1735420,2019-06-05 07:07:40 UTC,Lowering importance to Low due to currently different focus.
1735420,2018-03-21 19:30:48 UTC,"I noted a difference between the two configs.  The v4.10-rc3 config has the KVM module built in.  However, the v4.10-rc2 config has KVM built in for the config file, but was still set to module in the annotations file."
1735420,2018-03-19 20:52:36 UTC,"Since we don't know the commit that would solve this off hand, we can perform a ""Reverse"" bisect to identify that commit."
1735420,2018-03-20 22:07:14 UTC,"Yeah,  I couldn't find anything specific in v4.10-rc3 either.  I'll start a reverse bisect to see which commit that points to.  It will take testing of about 7 or so test kernels."
1735420,2018-03-20 21:21:15 UTC,"Well, does not seem to be in:"
1735420,2018-03-20 20:22:28 UTC,"There was only one commit that sticks out between 4.10-rc2 and v4.10-rc3, it is kvm and s390 related:"
1735420,2018-03-20 16:46:21 UTC,I tried some more:
1735420,2018-03-20 16:36:50 UTC,Doesn't seem to be in - kvm device still there:
1735420,2018-03-20 15:41:33 UTC,"Can you see if the patch is in v4.10-rc1:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/"
1735420,2018-03-20 14:29:49 UTC,Mainline Kernel 4.8 does not seem to have the patch included:
1735420,2018-03-14 07:58:26 UTC,So I just did a brief test - stock kernel first and then the modified one:
1735420,2018-03-13 21:55:54 UTC,"Frank, Is there a way to test a test kernel I built?  I built a Xenial test kernel with a back port of commit a411edf1320e (""KVM: s390: vsie: add module parameter ""nested"""")."
1735420,2018-03-09 09:49:17 UTC,"jsalisbury, this is a kernel module option which could have been set via modprobe.d files, but kvm mobule on s390x is compiled in, hence always loaded. hence in later kernels compiled in default is changed to not create nested kvm devices by default. hence this needs to be resolved as a cherrypick of upstream kernel change. -- says xnox from my laptop"
1735420,2018-03-08 10:42:48 UTC,This may be something that needs to be done outside of the kernel?  There could be a udev rule that needs updating?
1735420,2017-11-30 14:03:38 UTC,"So can it be avoided (with reasonable effort) that /dev/kvm is created in the xenial kernel, too?"
1735420,2018-03-20 22:11:33 UTC,"Hmm, it could also be a config change that is needed.  The 4.10-rc2 kernel uses the 4.9.0-2.3 configs and the 4.10-rc3 kernel uses the 4.10.0-0.2 config.  I'll compare those two as well."
1735420,2017-11-30 13:45:10 UTC,Note that the KVM kernel side in Xenial does not support nested at all. The confusion is caused by the fact that something seems to create /dev/kvm even when running in a KVM VM. Nested KVM support in the kernel was added (but disabled by default) around Zesty (4.10 kernels).
1735424,2017-12-01 15:33:33 UTC,"Since the solution is known this is set to triaged.
Also updated the title, I think my comment explains all that is needed as well as being a workaround until then."
1735424,2017-11-30 14:11:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735424,2017-12-01 15:32:03 UTC,"Hi Mathias,
thank you for your report - it is an interesting one."
1735424,2018-11-20 19:16:45 UTC,"I see the same, plus one more, apparmor denials on a fresh up-to-date bionic system where I just install ""mysql-server"":
[ter nov 20 15:30:58 2018] audit: type=1400 audit(1542741161.387:263): apparmor=""DENIED"" operation=""open"" namespace=""root//lxd-bionic-mysql_<var-lib-lxd>"" profile=""/usr/sbin/mysqld"" name=""/sys/devices/system/node/"" pid=15939 comm=""mysqld"" requested_mask=""r"" denied_mask=""r"" fsuid=165536 ouid=0
[ter nov 20 15:30:58 2018] audit: type=1400 audit(1542741161.391:264): apparmor=""DENIED"" operation=""capable"" namespace=""root//lxd-bionic-mysql_<var-lib-lxd>"" profile=""/usr/sbin/mysqld"" pid=15939 comm=""mysqld"" capability=2  capname=""dac_read_search""
[ter nov 20 15:30:58 2018] audit: type=1400 audit(1542741161.403:265): apparmor=""DENIED"" operation=""open"" namespace=""root//lxd-bionic-mysql_<var-lib-lxd>"" profile=""/usr/sbin/mysqld"" name=""/sys/devices/system/node/"" pid=15943 comm=""mysqld"" requested_mask=""r"" denied_mask=""r"" fsuid=165647 ouid=0"
1735430,2018-04-18 22:10:57 UTC,"Reviewed:  https://review.openstack.org/525309
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=44912b5fefd94d3cbff1e308fecb0589e7928932
Submitter: Zuul
Branch:    stable/ocata"
1735430,2017-11-30 17:43:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524263"
1735430,2017-12-01 14:04:38 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/524618"
1735430,2017-12-02 06:26:38 UTC,"Reviewed:  https://review.openstack.org/524263
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=112cd9cd1f31e091920e2f55fb213f78152dfd37
Submitter: Zuul
Branch:    master"
1735430,2017-12-07 23:55:48 UTC,This issue was fixed in the openstack/nova 17.0.0.0b2 development milestone.
1735430,2018-02-28 17:54:14 UTC,"Reviewed:  https://review.openstack.org/524618
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=20531dbf89c77b6c63ad43285ccde20f176b6b23
Submitter: Zuul
Branch:    stable/pike"
1735430,2018-04-02 13:19:12 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1735430,2017-12-04 21:00:59 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/525309"
1735430,2018-05-02 12:05:13 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1735435,2017-12-03 11:24:05 UTC,Does Google treat 404 and 410 status codes differently? https://www.youtube.com/watch?v=xp5Nf8ANfOw
1735435,2019-09-06 08:15:18 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/276
1735435,2017-12-01 19:29:54 UTC,"Yes, I know that cool URIs don't change, but there is no on-site content ta is equivalent for those particular pages. We could redirect them all to https://wl.widelands.org/wiki/TranslatingWidelands/#the-transifex-glossary though."
1735435,2017-12-01 16:28:29 UTC,I guess HTTP 410 ('Gone') is something you are looking for.
1735435,2017-12-01 14:25:15 UTC,"The best would be an HTTP header PERMANENTLY_DELETED, but I couldn't find one. So, your approach should do it."
1735435,2017-12-01 12:39:40 UTC,"HTTP 301 is fine. But linking to the wiki's main page isn't that good imho, because HTTP 301 is used for redirects. From my understanding a HTTP 301 should be returned if the address has changed, say an Article 'TranslationDutch' is moved to 'TranslDutch', but the content of the article is still valid and should be crawled. In this case this would be wrong, because we don't want the content to be crawled. But i do not understand much of this ;)"
1735435,2017-12-01 10:07:38 UTC,"Maybe this: https://en.wikipedia.org/wiki/HTTP_301 and link to the wiki's main page, or a user specified page instead if one is given?"
1735435,2017-12-04 10:29:34 UTC,410 is exactly what I was looking for :)
1735439,2018-06-19 16:23:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735439,2017-11-30 15:45:58 UTC,"For those struggling with this issue, a workaround is to call ""texindy -C utf8"" or, if using imakeidx, using ""\makeindex[options=-C utf8]"" (obviously, as long as your document is indeed utf8). Using XeLaTex/LuaLaTeX also works, because both also force utf8."
1735444,2018-01-19 04:51:09 UTC,"Changes for cinder-glance token has been merged and submitted
https://review.openstack.org/#/c/526611/"
1735444,2017-12-11 16:26:18 UTC,"Work in progress cinder blueprint for the same issue
https://blueprints.launchpad.net/cinder/+spec/use-service-tokens"
1735444,2017-12-05 05:57:07 UTC,"This seems to be a classic case of user token getting expired in the middle of a long running operation . User passes a valid token to cinder and makes a REST call but by the time the token reaches glance, it has expired. OpenStack has support for something called service tokens to aid in this. This has been implemented in nova for calls to cinder  (for eg. user makes rest api call to nova and nova uses that user token to cinder). As we know, while making REST api call, user token is passed as part of the header named 'X-Auth-Token' . With the service token support, another header named 'X-service-token' gets passed which has service user token passed along with the user token. Within the operation , when the user token expires, the call still continues if the service token is present. This support is enabled in keystoneauth1 library."
1735446,2018-11-27 18:01:47 UTC,Disco now has version 3.7.8-4ubuntu1 and it depends on Python3
1735446,2018-05-29 15:03:50 UTC,"In a related topic, Artful, Bionic and Cosmic have version 3.6.10, which has reached end-of-life on May 1st, 2018:
http://www.rabbitmq.com/news.html#2018-03-08T01:00:00+00:00"
1735446,2018-05-25 22:56:34 UTC,Is this assigned to anybody?
1735452,2018-01-24 22:37:46 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1465
1735453,2018-11-11 01:45:50 UTC,"The patch has been merged to the upstream codebase, however, it seems that currently the snaps in the edge channel is outdated and isn't featuring the latest revisions' builds."
1735453,2019-08-13 14:29:00 UTC,Backported in https://gitlab.com/inkscape/inkscape/commit/1a1d78ad89f8a7f3509d4464da2769e64909dec0
1735453,2017-11-30 15:55:53 UTC,"> Be penetrated with multiple error messages
"
1735453,2017-11-30 16:24:26 UTC,Replying to @eduard-braun2:
1735453,2017-12-01 16:54:00 UTC,Not reproduced on Linux Mint 16.04 with 'normal' installation of Inkscape 0.92.2.
1735453,2017-12-06 09:52:03 UTC,"Yup, it's definitely related to the snap."
1735453,2017-12-08 02:11:23 UTC,Subscribing Ted Gould to the report... perhaps there's something that can be done?
1735453,2018-11-09 07:53:41 UTC,I filed a possible fix to this bug: https://gitlab.com/inkscape/inkscape/merge_requests/414
1735453,2019-08-13 14:10:28 UTC,"From what I can see, the fix was merged ( https://gitlab.com/inkscape/inkscape/merge_requests/414 ) as mentioned above, but on my Ubuntu 18.04 LTS system with the latest ""Stable"" version of the Snap installed (0.92.4), this issue still exists."
1735453,2019-08-13 14:25:05 UTC,"The patch has been applied to master branch, not to 0.92.x."
1735458,2017-12-02 05:11:32 UTC,This bug was fixed in the package nfs-utils - 1:1.3.4-2.1ubuntu4
1735459,2017-11-30 18:21:00 UTC,"So yes and no. This is working exactly as the kernel presents this to apparmor, and there is nothing we can do about it at the moment."
1735459,2017-11-30 18:27:33 UTC,"To further explain, apparmor must do path construction post symlink resolution to avoid certain symlink based attacks. So apparmor is trying to resolve the /proc/<pid>/ns/ path post symlink resolution."
1735464,2018-11-18 18:51:56 UTC,"Hi Helana,"
1735464,2017-11-30 21:57:28 UTC,"Hello!
Thank you very much for your answer.
I suppose I am using the 5.0.0-1 version, the one shown on the ubuntu
software center."
1735464,2017-11-30 21:42:04 UTC,"Hi Helena,"
1735478,2018-02-13 20:22:15 UTC,"Discussed this briefly with Julia [1]. Looks like we have some ideas, they ought to be flushed out, so I'd like a spec."
1735490,2019-05-24 21:47:52 UTC,I have also staff feedback that they would welcome indication about preferences being saved.
1735508,2020-04-30 04:47:50 UTC,I was able to build and install an rpm just now on fedora core 32 with the latest release of pasaffe (0.56).
1735536,2018-12-30 03:20:28 UTC,This is also happening when you redeploy any machine that gets the same IP address as one that has been released. The errors are quite difficult to associate with this problem (known_hosts file).
1735546,2017-11-30 23:49:41 UTC,"Adding this issue here, as in the past we saw linked issues between netvsc reload and mtu change."
1735546,2017-12-04 18:45:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735546,2017-12-05 00:26:56 UTC,I can't reproduce the issue with 4.13.0-1004-azure-edge (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=azure-edge-next&id=21d8a99f88af972684618521cf19adafe24dc566)
1735546,2018-01-09 19:07:33 UTC,This bug was fixed in the package linux-azure - 4.13.0-1005.7
1735546,2017-12-12 15:46:23 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-December/088827.html
1735546,2017-12-07 19:00:47 UTC,"@mhcerri
Thanks for the explanation! I built the kernels directly from the git repo and I didn't use the binary packages (I thought they should be the same). What's your repro-rate? Yesterday as Chris tested linux-azure-edge 4.13.0-1004.4 + my pull request, the repro rate was only ~1%, meaning we have to do ""unload/reload netvsc"" several hundred times to repro the hang or the calltrace. Previously without the pull request, Chris mentioned it was much easier to repro the issue. So it looks to me the bug is timing-sensitive, and somehow my pull request made it difficult to repro it."
1735546,2017-12-07 13:59:48 UTC,"Ok. I've tested it again using gen1 VMs and I got the same results. Both linux-azure and linux-azure-edge show the problem, but for both cases I need to unload, load and unload the driver again to trigger the issue."
1735546,2017-12-05 00:29:03 UTC,"BTW, I tested ""modprobe -r hv_netvsc; modprobe hv_netvsc"" and ""ip link set dev eth0 mtu 3000; ip link set dev eth0 mtu 4500"" with 4.13.0-1004-azure-edge on WS 2016 (Version 1607, OS build 14393:1943)."
1735546,2017-12-07 11:55:44 UTC,@decui
1735546,2017-12-06 18:51:46 UTC,Right now only Generation 1 VMs are used in Azure.
1735546,2017-12-06 21:27:22 UTC,"@mhcerri
I only tested Gen1 VM (4.13.0-1004-azure-edge) on my local Hyper-V host (WS 2016), and couldn't repro the issue, i.e. reloading hv_netvsc and changing MTU worked fine."
1735546,2017-12-06 18:39:08 UTC,"Also, which specific builds of linux-azure and linux-azure-edge are you using? Are you using any versions from http://kernel.ubuntu.com/~mhcerri/azure/?"
1735546,2017-12-06 18:32:15 UTC,"Dexuan,"
1735546,2017-12-06 17:46:05 UTC,"This is indeed very odd.  Examining both code bases, we don't see any significant difference.  The source code is the same, as well as the configs and the module inclusion lists.  We're checking if we can reproduce bug 1736283."
1735546,2017-12-06 17:22:39 UTC,"Hrm, interesting.  Thanks for the note, I'll circle around with the team here to see what the discrepancy might be."
1735546,2017-12-05 19:40:32 UTC,@leann Actually I'm not sure if the pull request in bug 1736283 can fix this bug. It looks 4.13.0-1004-azure-edge has already fixed this bug somehow.
1735546,2017-12-05 19:21:50 UTC,"After having had a chat with Josh Poulson @Microsoft, it is believed that the pull request in bu https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1736283 should likely resolve the issue seen here.  We will post a test kernel in bug 1736283."
1735546,2017-12-06 19:13:50 UTC,I couldn't properly verify the problem on azure. If I execute:
1735546,2017-12-07 11:56:42 UTC,@decui
1735546,2017-12-06 21:43:27 UTC,"@mhcerri
FYI: I'm not using any kernel from http://kernel.ubuntu.com/~mhcerri/azure/."
1735546,2017-12-06 21:37:20 UTC,"@mhcerri
I'm using https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/, e.g. for 4.13.0-1004-azure-edge, I mean: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=azure-edge-next&id=21d8a99f88af972684618521cf19adafe24dc566."
1735554,2017-12-01 00:30:37 UTC,"I agree with Adam, this is not a current security bug. This is likely a Class B3 or Class D [1] and can be made public. The feature that is impacted is at best experimental / not fully implemented as Adam said.
I would like to have another core-sec weigh in though."
1735554,2017-11-30 21:58:33 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1735554,2017-12-01 16:13:53 UTC,I agree with Adam and Morgan's assessment. Adding Luke Hinds as Sec-PTL for further input.
1735554,2017-12-05 03:58:15 UTC,"To mark this as fixed, we should update the cloudsample to clearly dileneate between the two versions.  If someone is using cloud sample, they probably don't need is_admin_project, and we can just remove it."
1735554,2017-12-01 17:50:37 UTC,"Since we have some consensus this is not a vulnerability in a production-ready feature of any released versions, I've switched the report to public and triaged our security advisory task won't-fix accordingly."
1735554,2017-12-01 16:29:14 UTC,"If it relies on a feature not yet landed, I see no reason not to go public."
1735559,2017-12-01 23:03:38 UTC,Looks like a lot of time is spent in here initially.
1735559,2017-12-02 05:56:17 UTC,Out of curiosity - how big is the string?
1735559,2017-12-04 18:43:58 UTC,"It looks like the carrierdata, geodata, and tzdata directories contain files with very large hard-coded dictionaries (as mentioned before). Excluding them allows bandit to run in a reasonable amount of time."
1735564,2018-09-14 15:31:59 UTC,"Thanks Roger.
I was hoping to disable the Windows shortcut keys only while the
Inkscape window was active but not when other windows are active.
A less desirable but still useable option would be to disable
shortcut keys whenever Inkscape was running but its window was not
necessarily active.
I don't want to globally disable shortcut keys--they're really handy
which is why I use so many of them.
Thank you for your suggestion.
Kelly Butler"
1735564,2018-09-14 07:59:59 UTC,"Hi Kelly,
As i understand you, you want to disable windows shortcut keys. I can help in this. You need to just follow steps given below
1. Click windows> type run> type regedt32 and enter
2. Now navigate to System\CurrentControlSet\Control\Keyboard Layout
3. Now edit the value and set the binary value 00000000000000000300000000005BE000005CE000000000 and enter
4. Close the all apss and restart your computer.
Your windows shortcut keys are disabled.
I am attaching you the final steps of the process."
1735564,2017-12-01 18:59:53 UTC,"Hi Hachmann,
Thanks for the reply.
As a rank beginner, I'd prefer not to alter Inkscape's UI. Maybe
later if I get proficient. I assume that Inkscape's programmers had
good reasons for the choices they made and I don't want to
second-guess them at this point. As for disabling Windows keyboard
shortcuts, I was able to google up instructions for disabling Winkey
+ X type shortcuts but they involved registry editing, reboots, etc.
Besides, I don't use Winkey shortcuts. For example I have a
Shift-Ctrl-J keyboard shortcut to start Notepad on a text file that's
a daily journal for me. Shift-Ctrl-L brings up a frequently used
Excel spreadsheet. And I have about twenty more of these Shift-Ctrl
type shortcuts. At this point I have to edit each pertinent shortcut
and disable the shortcut key feature. I have not yet found a way to
easily and collectively disable such shortcuts during Inkscape
sessions and re-enable them afterwards. Ideally, Inkscape itself
could be configured to disable them while an Inkscape window was open.
Kelly"
1735564,2017-12-01 16:52:49 UTC,What does Windows documentation say about this?
1735566,2019-10-21 14:49:10 UTC,Tested with an item that was checked-out and one that was in-transit.  Works as advertised.  Signed-off at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1735566_deleted_copy_not_ideal-signoff
1735566,2020-01-21 16:59:45 UTC,"Issue and fix confirmed.  Thanks, All!  I've merged to 3.3 and up."
1735566,2019-10-17 18:19:28 UTC,Here is a branch that resolves this for AngularJS (note that the Angular experimental catalog will also need a similar fix): user/sandbergja/lp1735566_delete_copy_not_ideal_status
1735566,2019-08-02 11:27:18 UTC,"He have this issue too, in the Evergreen 3.3.2"
1735566,2019-06-19 19:27:29 UTC,We also have this issue that staff have asked for a solution. Hoping one is coming
1735566,2018-11-28 14:38:06 UTC,Confirming that this is still an issue on 3.2 version running at Evergreen Indiana. Staff without the COPY_DELETE_WARNING.override are prompted to attempt with another account that might have this permission without explanation as to the root cause.
1735566,2020-01-10 18:21:18 UTC,Works as advertised.
1735566,2020-01-21 16:49:34 UTC,For Angular:  bug #1860460.
1735568,2020-07-27 13:21:16 UTC,"Thanks for looking at this Jane! I tested the display in FireFox on our 3.4.3 test system and don't see the issue you are seeing. I asked another person to look at this and they did not see that issue either. She has a smaller screen than I do and we both changed font size and resolution, still with no issue. FireFox browser version 78.0.2."
1735568,2017-12-01 13:16:13 UTC,"Confirmed, just saw this yesterday on 3.0.0"
1735568,2019-09-26 18:54:02 UTC,I can confirm this happens on version 3.2.5 and 3.2.8.
1735568,2019-11-21 18:21:29 UTC,"I have a branch that addresses this issue and bug 1830443. Usability is also improved. Colors were tested using the Chrome extension Colorblindly, a colorblindness simulator. Attaching a screenshot of the style changes. Marking bug 1830443 as a duplicate since this branch fixes both."
1735568,2020-02-19 22:55:32 UTC,Tested on https://bugsquash.mobiusconsortium.org/eg/staff/
1735568,2020-02-19 22:56:14 UTC,"I have tested this code and consent to signing off with my name, Elaine Hardy, and email, <email address hidden>"
1735568,2020-07-18 14:45:10 UTC,"Thank you for this fix, Christine.  It works well for me in Chrome.  However, in Firefox, I can only see the first digit of the MARC tags (see attached screenshot)."
1735568,2020-07-29 17:49:00 UTC,"I'm also not seeing an issue with the display of the tag on Chrome or on Firefox on Windows or MacOS at various viewport sizes, so for the moment I'll chalk that up as a one-off glitch. I've gone ahead and pushed this to master, rel_3_5, and rel_3_4.  Thanks, Christine and Elaine!"
1735568,2020-07-29 17:54:49 UTC,See also bug 1889459 about replicating the background color scheme to the Angular MARC editor.
1735568,2019-05-24 12:21:07 UTC,Our librarians confirmed this behavior testing Evergreen 3.3.0
1735575,2019-09-12 09:37:34 UTC,This issue was fixed in the openstack/python-openstackclient 4.0.0 release.
1735575,2017-11-30 22:57:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524420"
1735579,2019-05-07 20:14:46 UTC,"It turns out that Pike luminous 12.2.4 uses 'overall_status', but Queens luminous has 12.2.11 which uses 'status'."
1735579,2019-05-07 17:03:17 UTC,This appeared on my cloud I was upgrading today.
1735579,2019-05-03 11:59:05 UTC,"Reviewed:  https://review.opendev.org/656764
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=caa1cd8d6a2859a8d33abedd4a5f409591aa005e
Submitter: Zuul
Branch:    master"
1735579,2019-04-02 11:00:07 UTC,"Reviewed:  https://review.openstack.org/648941
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=8e4fe5729583bd6a229d2688ea53f0198483b279
Submitter: Zuul
Branch:    master"
1735579,2018-09-19 03:42:11 UTC,"Also important to add - OSDs that are up, but not 'IN'"
1735579,2019-05-30 11:58:46 UTC,Marking the charm-ceph task wontfix as the ceph charm has been removed from support for a while now
1735588,2019-10-22 19:38:44 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/342211
Reason: This looks dead and I'm not sure if it's still needed given I4484e63c97bd1cdde3d88855eabe7545784f365e landed."
1735588,2019-09-27 09:00:48 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1735588,2019-09-25 09:02:06 UTC,This issue was fixed in the openstack/compute-hyperv 9.0.0.0rc1 release candidate.
1735588,2019-08-19 21:45:02 UTC,"Reviewed:  https://review.opendev.org/470775
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1eec451b1ba254ec4c43c77f79b0d2809d6cb9a5
Submitter: Zuul
Branch:    master"
1735588,2018-07-03 08:09:19 UTC,"Change abandoned by Claudiu Belu (<email address hidden>) on branch: master
Review: https://review.openstack.org/557974"
1735588,2018-05-18 15:45:00 UTC,"Reviewed:  https://review.openstack.org/561581
Committed: https://git.openstack.org/cgit/openstack/oslotest/commit/?id=8241dd624f8ca481fe15a44f7d3fed10be7ae937
Submitter: Zuul
Branch:    master"
1735588,2018-04-26 16:11:31 UTC,"Reviewed:  https://review.openstack.org/557923
Committed: https://git.openstack.org/cgit/openstack/oslotest/commit/?id=6baff0eda4edbd8163426a2ac774514cabf99a3a
Submitter: Zuul
Branch:    master"
1735588,2018-04-02 10:58:22 UTC,"Reviewed:  https://review.openstack.org/557368
Committed: https://git.openstack.org/cgit/openstack/oslotest/commit/?id=bb78b84c3fc8485e590f2c925c07731a9740a852
Submitter: Zuul
Branch:    master"
1735588,2018-01-25 19:40:21 UTC,"Change abandoned by Matthew Edmonds (<email address hidden>) on branch: master
Review: https://review.openstack.org/535806
Reason: abandoning in favor of https://review.openstack.org/#/c/447505"
1735588,2018-03-28 20:58:06 UTC,"Reviewed:  https://review.openstack.org/447505
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1f0638f943a7b490db3cf9a60423ebae859682cc
Submitter: Zuul
Branch:    master"
1735588,2017-12-01 01:31:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524438"
1735588,2018-01-08 23:15:37 UTC,"Reviewed:  https://review.openstack.org/524438
Committed: https://git.openstack.org/cgit/openstack/oslotest/commit/?id=0bde35899a10875891f0592961c01e9fbb854738
Submitter: Zuul
Branch:    master"
1735588,2018-01-09 15:12:43 UTC,This issue was fixed in the openstack/oslotest 3.2.0 release.
1735588,2018-01-11 19:27:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532947"
1735588,2018-01-12 16:16:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/533230"
1735588,2018-01-17 10:55:41 UTC,"Reviewed:  https://review.openstack.org/533230
Committed: https://git.openstack.org/cgit/openstack/oslotest/commit/?id=5d3196781bc3b51eee04f4ed7a77af0c9fdbcaba
Submitter: Zuul
Branch:    master"
1735588,2018-01-19 16:06:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535806"
1735588,2018-03-30 10:48:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/557923"
1735588,2018-01-22 17:21:09 UTC,"Reviewed:  https://review.openstack.org/532619
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=823b162c6a02083f6ae6f6ce27150c039687993d
Submitter: Zuul
Branch:    master"
1735588,2018-01-25 20:24:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/538022"
1735588,2018-01-26 00:30:24 UTC,This issue was fixed in the openstack/networking-hyperv 6.0.0 release.
1735588,2018-02-02 12:20:23 UTC,"Reviewed:  https://review.openstack.org/539908
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=26c91401ee8f203d74261a6b0c67196173ef57d6
Submitter: Zuul
Branch:    master"
1735588,2018-03-08 23:51:05 UTC,This issue was fixed in the openstack/os-win 4.0.0 release.
1735588,2018-03-17 02:59:33 UTC,"Reviewed:  https://review.openstack.org/538022
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9c7d6123e3e66fd8b182af548273df9e7d66ee36
Submitter: Zuul
Branch:    master"
1735588,2018-03-21 16:37:01 UTC,"Reviewed:  https://review.openstack.org/539954
Committed: https://git.openstack.org/cgit/openstack/compute-hyperv/commit/?id=d19606a82809f2a909d20b102166880b65d74b1f
Submitter: Zuul
Branch:    master"
1735588,2018-03-28 15:20:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/557368"
1735588,2018-01-25 13:20:48 UTC,"Reviewed:  https://review.openstack.org/532947
Committed: https://git.openstack.org/cgit/openstack/networking-hyperv/commit/?id=d5b72f4250ce3a60fb85f751c99fbba88a71ced0
Submitter: Zuul
Branch:    master"
1735620,2017-12-01 03:54:13 UTC,Looking at the review.. I only see CI repos in the changes. AFAICT delorean should not be building any packages for this change. https://review.openstack.org/#/c/523903/
1735620,2019-11-13 08:05:13 UTC,Is this still an issue?
1735620,2017-12-01 09:03:51 UTC,"The issue is in the tripleo-quickstart-extras playbook, see [1]. All changes in the dependency matrix are using ""master"" as a release, so artg_release is set to master by the playbook (see [2]) and DLRN is configured to use master as a release instead of Newton or Ocata."
1735654,2017-12-05 05:59:05 UTC,"Due to this issue i was not able to login into desktop of ubuntu.
Error : error in session start"
1735654,2017-12-04 23:08:06 UTC,Do you have any idea why aptdaemon installed different versions of amd64 vs x86 libpulse0 packages?
1735654,2017-12-04 23:06:39 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1735667,2017-12-07 09:12:37 UTC,"This is not an issue for new style jobs that use the ansible role: https://github.com/openstack/tempest/blob/master/roles/process-stackviz/tasks/main.yaml#L12, since it uses subunit directly, and the role that produces subunit accounts for both testr and stestr: https://github.com/openstack-infra/zuul-jobs/blob/master/roles/process-test-results/tasks/main.yaml"
1735667,2017-12-07 09:06:48 UTC,I think we can keep both testrepository as well as stestr as projects having stable branches they uses testr. so it will help not to break anything.
1735677,2020-12-11 10:08:28 UTC,"I am going to close this bug base on comment #3 from Teodor, and the fact the bug 1727544 is now fix-released."
1735677,2017-12-01 15:49:44 UTC,Works fine now. Syslog is clean. Thank You very much. I plan to reinstall system once again so I can do some testing if any additional feedback will be helpful.
1735677,2017-12-01 14:49:07 UTC,"An AMD laptop?
Please try kernel here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727544/comments/35"
1735677,2020-09-01 05:38:20 UTC,"Dear Teodor and Kai-Heng,
I got the same problem myself when using AntiX19.2 64bit with my Lenovo Ideapad 320.
I am very beginner in Linux and was wondering how to try that kernel. I mean in step by step command if you don't mind. Touchpad is not working since I run live USB."
1735681,2017-12-01 09:23:12 UTC,"One of affected packages should be ""mesa-utils"". But I don't know how to change it for the above package field."
1735681,2017-12-06 04:23:09 UTC,"We will need more information about the package version and opengl version, to ensure it's using right hardware accel but not software rendering."
1735681,2017-12-06 08:33:26 UTC,sos report
1735681,2017-12-06 08:36:08 UTC,"reports of ""apport-cli xserver-xorg-video-amdgpu"""
1735719,2018-02-15 23:53:20 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1735719,2017-12-01 14:21:05 UTC,"This is because the compute node for that host in that cell is not deleted and since it was mapped once, it is marked as 'mapped' again, so the discover_hosts routine ignores it, for performance / efficiency reasons."
1735719,2017-12-01 15:21:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524641"
1735719,2017-12-09 07:24:30 UTC,"Reviewed:  https://review.openstack.org/524641
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8ad36d15e404bf0dce90bed57f8aa91a350ed341
Submitter: Zuul
Branch:    master"
1735719,2017-12-13 01:54:20 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/527560"
1735719,2018-02-08 18:17:37 UTC,"Reviewed:  https://review.openstack.org/527560
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f0525e8f15fc29f99ccb1a3fcf8de09d5e827015
Submitter: Zuul
Branch:    stable/pike"
1735719,2018-01-26 00:44:12 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1735724,2021-02-17 20:13:26 UTC,Are modern versions of Neutron still sufficiently vulnerable to this to warrant publication of an advisory once it's closed? Is a fix similar to the abandoned https://review.opendev.org/527210 still needed?
1735724,2021-02-24 23:36:36 UTC,"We continue to see this on Rocky where, often times, routers created are missing the REDIRECT rule in iptables for metadata-proxy."
1735724,2018-10-17 02:36:20 UTC,"Reviewed:  https://review.openstack.org/598979
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e55ff3ec35566a718a325b198fc45b890d129d24
Submitter: Zuul
Branch:    stable/queens"
1735724,2018-08-31 14:30:46 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/598980"
1735724,2018-08-31 14:30:31 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/598979"
1735724,2017-12-01 13:27:41 UTC,A possible solution would be moving the iptables rules installation for metadata right after the namespace gets created or right before we plug the ports to br-int instead of doing it in the AFTER_CREATE router notification handler.
1735724,2017-12-05 21:40:52 UTC,"This bug has a security edge (metadata requests leaking to outside / metadata responses reaching us from the outside), so I marked it accordingly. The bug will stay in public since it was reported like that in the first place."
1735724,2017-12-05 21:41:54 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1735724,2017-12-11 18:47:54 UTC,"https://review.openstack.org/#/c/524406/ is a partial fix for this issue, I just added the bug to the commit message later so it hasn't added a link here."
1735724,2017-12-11 18:48:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527210"
1735724,2018-03-28 21:57:42 UTC,"Reviewed:  https://review.openstack.org/524406
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=69419778276a722c3f376046d1e0cc7fc4684e99
Submitter: Zuul
Branch:    master"
1735724,2018-10-20 02:07:44 UTC,"Reviewed:  https://review.openstack.org/598980
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6a8a1f81aea35933996494674157454e7abfb1ee
Submitter: Zuul
Branch:    stable/pike"
1735724,2018-08-31 07:45:21 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1735724,2018-08-31 07:45:31 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/527210
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1735730,2019-11-14 01:38:39 UTC,"Fedora bug closed, reported as working"
1735733,2017-12-03 12:44:11 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1735733,2019-07-02 06:25:33 UTC,Fixed in the following commits:
1735735,2017-12-01 20:40:55 UTC,"DuplicateSignature:
 Setting up libc6-i386 (2.23-0ubuntu9) ...
 Setting up libc6-i386 (2.23-0ubuntu9) ...
 dpkg: error processing package libicu55:amd64 (--configure):
  package is in a very bad inconsistent state; you should"
1735754,2018-11-13 16:05:10 UTC,Confirmed - fix pushed here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=9e92fbbf185607d4ae0cd16f98efa49286ed35df
1735754,2019-05-22 19:50:51 UTC,"Pushed to master. Thanks, jane and Sam!"
1735754,2018-11-13 16:06:48 UTC,Rather - http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/slink/LP1735754_advanced_search_valign
1735765,2017-12-02 17:54:43 UTC,"I've already spotted this one, and have a fix waiting."
1735768,2019-10-03 21:43:24 UTC,Fixed this bug's status; fixes were released a while back.
1735768,2019-08-06 01:12:30 UTC,"Pushed to master, rel_3_3, and rel_3_2 (it didn't apply cleanly to rel_3_1). Thanks, Jane!"
1735768,2018-11-10 22:54:33 UTC,Force-pushed some more changes.
1735768,2018-11-10 20:37:40 UTC,Started a branch to take care of this here: user/sandbergja/lp1735768_add_labels_to_opac_inputs
1735768,2017-12-01 15:01:15 UTC,Related bug in the Web client: https://bugs.launchpad.net/evergreen/+bug/1615800
1735768,2019-08-02 14:51:43 UTC,Works for me. Signoff branch is user/gmcharlt/lp1735768_signoff.
1735779,2019-04-03 13:30:24 UTC,The bug is in the `docutils` dependency. That package is on sourceforge and the GH mirror is out-of-sync since ages.
1735780,2018-03-08 13:19:46 UTC,"I see similar error[1] (rocky version), but when I run tempest in loop it fails after few iteration."
1735780,2017-12-01 16:04:43 UTC,"As far as I know, this test is passing in upstream CI at the moment, so which release of nova are you hitting this on, what is the setup involved, etc?"
1735780,2017-12-01 16:06:46 UTC,Recent pass upstream:
1735780,2017-12-01 16:07:56 UTC,"Oh I see, yeah, the test passes but we get errors in the logs:"
1735780,2017-12-01 16:21:56 UTC,"(10:08:04 AM) mriedem: lyarwood: https://bugs.launchpad.net/nova/+bug/1735780
(10:08:06 AM) openstack: Launchpad bug 1735780 in OpenStack Compute (nova) ""n-cpu logs error ""is not a valid LUKS device"""" [Undecided,Confirmed]
(10:08:10 AM) mriedem: http://logs.openstack.org/26/515426/1/check/legacy-tempest-dsvm-neutron-full/e6ac116/logs/screen-n-cpu.txt.gz#_Dec_01_14_06_49_142977
(10:17:18 AM) lyarwood: mriedem: looking
(10:19:08 AM) lyarwood: mriedem: so that's normal, search for cryptsetup below that and you can see we format and then open it correctly
(10:19:27 AM) mriedem: lyarwood: :(
(10:19:36 AM) mriedem: i guess that's why it's a stacktrace at debug rather than error?
(10:19:45 AM) mriedem: which is i think a thing i've seen with privsep before
(10:20:13 AM) lyarwood: https://github.com/openstack/os-brick/blob/master/os_brick/encryptors/luks.py#L150-L161
(10:20:36 AM) lyarwood: mriedem: yeah I think so"
1735780,2018-01-31 10:42:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539487"
1735780,2018-05-10 20:58:54 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/539487
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns."
1735788,2017-12-01 16:49:21 UTC,Contact : <email address hidden>
1735790,2018-01-22 16:12:48 UTC,"I'm not sure what the ""required"" flag does for ""options"". I could see throwing an error at the point where they are registered if we've already loaded data and the option isn't included."
1735790,2018-06-06 18:00:44 UTC,"I'm inclined to think required was intended for cli opts, but we should either document that or make it work for config file opts as well."
1735791,2018-12-11 19:52:58 UTC,Confirmed in version 3.1.6
1735792,2017-12-05 13:41:33 UTC,"Spoke to Ian Main, this work is not yet ready to move forward."
1735792,2018-02-21 20:15:50 UTC,Dropping to high as this is not a critical issue.  It is a tech-debt issue however.
1735798,2018-01-09 20:47:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735798,2018-01-09 23:18:25 UTC,The problem occurs when I use network-manager to initiate the VPN.
1735798,2018-01-09 23:34:35 UTC,"I have figured this out as well. It would be nice to be able to use
gnome-network-manager though."
1735800,2018-08-28 14:46:28 UTC,This has happened to users in the wild:
1735804,2018-05-23 10:53:51 UTC,This is Interesting.
1735804,2018-12-09 16:26:04 UTC,I am compiling trunk-2018.02b and getting the same error as James. I can compile by uncommenting the  line
1735804,2019-02-05 20:24:08 UTC,moved from https://bugs.launchpad.net/yade/+bug/1735804 to https://gitlab.com/yade-dev/trunk/issues/39
1735804,2019-05-08 15:59:31 UTC,"Hi, I just fixed this. https://gitlab.com/yade-dev/trunk/commit/24b894d9e586a8eb70a7e5f1c2f4a16a0899d1ef"
1735805,2017-12-03 11:45:32 UTC,No more after the computer spent a night in sleep.
1735805,2017-12-02 16:10:01 UTC,"Could you please attach the project that causes the bug (or, if it is
simple, a screenshot of it?)"
1735808,2018-06-22 00:10:35 UTC,Related bug: https://bugs.launchpad.net/evergreen/+bug/1778083
1735812,2018-01-15 15:17:58 UTC,"That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml"
1735812,2018-01-22 02:50:52 UTC,Re-opening as GNOME Software don't have any architecture information about snaps. So it is possible to show snaps that aren't available for your system.
1735812,2018-01-22 22:57:18 UTC,"Actually snapd might be doing the architecture matching for us, so it needs investigation to see if the problem still occurs."
1735818,2019-03-19 07:29:26 UTC,The last log ends with:
1735818,2017-12-01 19:50:34 UTC,"Unfortunately, the coredump will only be useful with the exact version of your binary."
1735818,2017-12-01 20:27:23 UTC,"Version from log: unofficial-git-97c51d8 (Release)
Package version: widelands-bzr r8520-1 (built from https://aur.archlinux.org/packages/widelands-bzr with makepkg)"
1735818,2018-08-22 15:11:33 UTC,Can you still reproduce this?
1735818,2019-03-19 06:32:49 UTC,"The last compatible Widelands version for the savegame is r8746, but I haven't managed to hit the crash yet. If I can take a wild guess, maybe a ship is trying to deliver wares while the port is being destroyed. We have fixed crashes from wares delivered by land this week, and that might also be it."
1735818,2019-01-09 21:37:15 UTC,"Since no one reported similar segfaults, i mark this bug as 'incomplete' and removed the milestone."
1735818,2019-01-12 04:27:07 UTC,"I may have recently come across this bug playing build 19. When I destroy an enemy port, approximately one time in six the game will crash. Has happened with various ports. Sometimes the game behaves, others it does not."
1735818,2019-01-12 09:07:13 UTC,"Since we have build 20 close to release, i think build 19 is out of scope these days."
1735818,2019-01-15 23:51:59 UTC,"Will do, cheers."
1735818,2019-03-17 04:17:28 UTC,[Expired for widelands because there has been no activity for 60 days.]
1735818,2019-05-19 04:17:22 UTC,[Expired for widelands because there has been no activity for 60 days.]
1735823,2017-12-01 19:56:35 UTC,"Discussion and troubleshooting from #openstack-infra:
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-12-01.log.html#t2017-12-01T19:05:52"
1735823,2019-05-21 11:27:01 UTC,"Reviewed:  https://review.opendev.org/524748
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2a8c0c800ba2107a94597761677007ed660a40a1
Submitter: Zuul
Branch:    master"
1735823,2018-03-12 22:59:47 UTC,"Reviewed:  https://review.openstack.org/524727
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ec5c27a8afec53f167d30d8f81e23c1b42465d54
Submitter: Zuul
Branch:    master"
1735823,2017-12-08 20:23:31 UTC,"Oops, comment #12 meant bug 1737214."
1735823,2017-12-01 22:43:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/524748"
1735823,2017-12-01 22:36:16 UTC,Similar issue in the libguestfs mailing list:
1735823,2017-12-01 22:17:39 UTC,Well we know we aren't setting the force_tcg settings properly:
1735823,2017-12-01 22:05:15 UTC,We reproduced the issue in https://review.openstack.org/#/c/524710/ with the debug logs.
1735823,2017-12-01 22:03:51 UTC,Can see guestfs threads hung when n-cpu shuts down here:
1735823,2017-12-01 20:58:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/524727"
1735823,2017-12-01 20:14:51 UTC,This is the change that originally made us run guestfs in a thread pool to inspect it's capabilities:
1735823,2017-12-01 20:13:27 UTC,"(2:07:07 PM) dmsimard: In EL7 the version of guestfs is libguestfs-1.36.3-6.el7_4.3.x86_64 .. in Ubuntu... I'm not seeing it installed?
(2:08:08 PM) mordred: dmsimard: it's possible that feature isn't enabled in the ubuntu jobs? (which would also explain why we only see the problem on non-ubuntu)
(2:08:36 PM) mriedem: no we do file injection on ubuntu jobs too
(2:08:37 PM) dmsimard: mordred: devstack jobs on centos and ubuntu would run a different set ? /me looks
(2:08:40 PM) mriedem: http://logs.openstack.org/10/523910/1/check/legacy-tempest-dsvm-neutron-full/8cd6149/logs/etc/nova/nova.conf.txt.gz
(2:08:47 PM) mriedem: inject_partition = -1
(2:09:03 PM) mriedem: http://logs.openstack.org/10/523910/1/check/legacy-tempest-dsvm-neutron-full/8cd6149/logs/dpkg-l.txt.gz
(2:09:08 PM) mriedem: ii  libguestfs0:amd64                   1:1.32.2-4ubuntu2                     amd64        guest disk image management system - shared library
(2:09:14 PM) mordred: ah. k
(2:09:34 PM) mordred: darn. I was hoping it was more ammunition against the feature. /me goes back to other things
(2:11:53 PM) openstackgerrit: Jeremy Stanley proposed openstack-infra/puppet-mailman master: Enable modules before starting Apache  https://review.openstack.org/524718
(2:11:55 PM) fungi: mordred: ^
(2:11:57 PM) dmsimard: mriedem: so there's a delta between 1.32.2 in Ubuntu and 1.36.3 in CentOS... and opensuse has 1.32.4"
1735823,2017-12-01 20:11:59 UTC,"Tracing the logs on one of these failures, we get here:"
1735823,2017-12-08 20:23:02 UTC,Bug 1737207 is related and I have a separate patch for that.
1735823,2017-12-01 20:16:26 UTC,This is a devstack change which will enable guestfs debugging so we can hopefully get some more information when we see this type of failure:
1735826,2018-02-01 16:46:55 UTC,I tested it with the latest 4.15 kernel - without success.
1735826,2017-12-04 12:50:32 UTC,"probably needs some fix in udev/systemd, but you might first report it to libinput upstream on bugs.freedesktop.org"
1735826,2017-12-04 20:48:53 UTC,"Thanks. I reported it on bugs.freedesktop.org, too."
1735826,2017-12-05 08:41:00 UTC,"great, please share the link here so that we can track it"
1735826,2017-12-05 14:00:12 UTC,"Bug-report on Bugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=104087"
1735826,2018-01-30 17:18:38 UTC,looks like the kernel would need to be fixed first
1735826,2018-01-30 20:30:40 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1735828,2020-01-21 22:47:47 UTC,I pushed a branch with this feature.
1735828,2018-01-02 16:14:12 UTC,This appears to be a duplicate of https://bugs.launchpad.net/evergreen/+bug/1691861
1735828,2018-01-02 19:25:50 UTC,"Elaine,"
1735828,2019-04-16 18:58:56 UTC,"There are some important actions missing from the Item Bucket menu that are available in Item Status, including Checkin Items, Renew Items and Update Inventory.  These are all options staff use for inventory and various special projects.  Sometimes you can flip a workflow and the items can be scanned or uploaded into Item Status, actions taken, and then moved to a bucket, but sometimes the actions are needed for items already in a bucket.  We would like to either have Show Status restored to the Item Bucket action menu as it is in the XUL client, or have all the same options in both menus."
1735828,2020-02-20 18:52:23 UTC,"Alternate suggestion: ""Open in Item Status"""
1735828,2020-07-11 12:44:47 UTC,"Works well for me.  Thanks, Mike, Tiffany, New Devs Group, and all others who worked on this."
1735828,2020-02-20 23:09:41 UTC,"The text has been modified to say ""Open in Item Status"". This is the branch with the work:"
1735828,2020-02-20 19:28:50 UTC,"I'm okay with ""Show Status of Selected Items"" if everyone else is, but I think ""Open in Item Status"" makes it clearer that it's going to be opening a new tab / interface (as opposed to, say, showing the copy status on the same page)."
1735828,2020-02-20 19:18:14 UTC,"Sorry, Terran I didn't see your message til now.  If we want to change the text to something else let me know.  Happy to follow up with this quick change!"
1735828,2020-02-20 19:14:49 UTC,"Thanks, Mike! I have removed the needsdiscussion tag and put the signedoff tag back."
1735828,2020-02-20 19:00:06 UTC,"I changed the text to read ""Show Status of Selected Items"".  Many other options use the phrase ""Selected Items"", so it's consistent with the rest of the menu."
1735828,2018-01-02 19:43:25 UTC,"Thanks -- I read so many bugs this morning, I was getting them confused."
1735828,2020-02-20 18:30:52 UTC,"I have a small nit to pick with this change. The new option is ""Show Selected Items"" which doesn't tell me much from looking at the code or even in the interface."
1735828,2020-02-19 20:55:13 UTC,"I, along with the New Developers Working Group, tested this code on the feedback fest server."
1735828,2020-02-20 20:26:51 UTC,"I agree that ""Open in Item Status"" is clearer"
1735829,2017-12-02 15:34:49 UTC,"Fixed in https://github.com/FabricioS/libim7/commit/5ed56e8db92.
libim7 now supports python3.
I would appreciate feedbacks on python2."
1735835,2019-06-18 15:12:41 UTC,"The record buckets UI de-dupes records to ensure you don't have duplicate records when adding to pending already, but the copy buckets don't appear to have the same functionality. I erred on the side of working with how both UIs already functioned when adding items to pending. That may be worth opening a new bug for, if it's not intentional."
1735835,2019-06-18 14:33:45 UTC,"Thanks, Kyle.  Any reason the records are de-duped as they are moved but not the copies?  Minor nit, console.log(recs) should be console.debug (or removed)."
1735835,2019-05-20 17:56:48 UTC,"I've pushed a branch here adding the new action ""Move selected Records/Copies to Pending Records/Copies:"" https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1735835-transfer-bucket-contents-to-pending"
1735835,2018-09-10 21:43:29 UTC,Unchanged in 3.2 beta
1735835,2018-08-06 12:01:13 UTC,Confirmed in 3.1.4
1735835,2017-12-14 15:49:41 UTC,Confirmed in v.3.0.1.
1735835,2019-06-25 14:21:19 UTC,"Thanks, Kyle.  Updated patch merged to 3.2 and above."
1735838,2019-09-19 12:00:00 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1735838,2017-12-01 21:55:40 UTC,"This is not really an error. It is becuase MAAS is already executing another power action in the machine and whle that happens, we lock and prevent you from executing another action."
1735838,2017-12-01 21:09:33 UTC,see traceback in regiond.log
1735838,2017-12-01 21:07:00 UTC,logs
1735841,2017-12-15 03:16:31 UTC,I was able to identify the source of the issue and the software where this bug occurs.
1735844,2018-03-02 17:28:20 UTC,"In the screenshot you sent, which VLANs is the space supposed to be in?"
1735845,2017-12-05 04:53:39 UTC,"Bonjour Laurent,"
1735847,2019-09-10 17:51:12 UTC,Given that this is a step in the right direction I've gone ahead and committed these changes to 3.1 to master. Another thing to consider in the future re: Michele's comments is whether we want to have the requesting patron's information even made available to the transit template at all. That's a discussion we can have in another bug.
1735847,2018-09-13 21:08:55 UTC,The fix changes the hold_transit_slip from this:
1735847,2018-03-30 19:19:01 UTC,I went ahead and committed the change to the xul client as well. Same git link above.
1735847,2019-09-11 14:49:25 UTC,"I think making it impossible to include the requester's information might be a step too far, as there's the potential for internal paging within a corporate library or the like to need it."
1735847,2017-12-01 22:34:03 UTC,Branch here:
1735847,2019-09-10 17:54:06 UTC,"Forgot to mention, thanks Blake and Dan!"
1735847,2019-05-23 18:08:04 UTC,Works as advertised.
1735860,2017-12-04 09:31:12 UTC,We have this code
1735860,2020-05-14 13:37:07 UTC,"I'm going to close, given my comment #1. AFAIK this is done."
1735863,2017-12-07 00:39:25 UTC,"The data presented in comment #6 is interesting, but still inconclusive."
1735863,2019-09-27 07:31:55 UTC,Is this still happening? If so what version of the snap is currently being used?
1735863,2017-12-04 18:05:28 UTC,"just sent off a new deploy, and whats odd is that I see the dhcp error in the logs, but this time, my lxd containers all deployed successfully"
1735863,2020-03-28 04:17:25 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1735863,2017-12-03 18:04:10 UTC,dhcp leases and conf
1735863,2017-12-03 18:01:46 UTC,"$ juju status --format yaml | pastebinit
http://paste.ubuntu.com/26106373/"
1735863,2017-12-03 17:58:53 UTC,@andreserl @mpontillo
1735863,2017-12-02 01:01:53 UTC,"The MAAS API allows reserved ranges to be used for allocation, but only if specifically requested. MAAS on its own should not allocate from a reserved range as shown."
1735863,2017-12-02 01:00:58 UTC,"actually, two errors on my part. There are no containers and they are machines."
1735863,2017-12-02 00:51:45 UTC,"Also, please attach your dhcpd.conf"
1735863,2017-12-02 00:50:36 UTC,"@james,"
1735863,2017-12-04 18:06:18 UTC,"geh, ignore #9, wrong bug"
1735863,2020-01-27 14:03:07 UTC,"This bug is still affecting MAAS 2.6 where if I enable DHCP on a custom range in a subnet (e.g. 10.0.30.180 - 10.0.30.254) before powering on any compute nodes to be added and commissioned, they will take an IP from the reserved range the first time they run for commissioning (like 10.0.30.180 10.0.30.181 etc.), but when deploying they will get an IP outside the range (e.g. 10.0.30.3 10.0.30.4)."
1735872,2017-12-13 17:08:37 UTC,"It might be worth considering demoting the package - added a bug for that, looking for feedback
before I make it an official request.
https://bugs.launchpad.net/ubuntu/+source/system-config-kickstart/+bug/1738046"
1735872,2018-02-02 18:49:02 UTC,system-config-kickstart has been demoted to universe. I am keeping this bug open since it still needs to be ported way from pygtk which will be removed from the Ubuntu archives in a future Ubuntu release.
1735875,2017-12-05 06:41:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735889,2018-02-19 06:06:42 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1735889,2017-12-16 22:10:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735889,2017-12-05 00:08:20 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1735900,2018-02-14 03:44:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735908,2017-12-02 12:30:03 UTC,This change was made by a bot.
1735908,2017-12-02 21:41:42 UTC,You may need to run the following from a terminal:
1735908,2017-12-03 06:03:41 UTC,"FYI the PC is pretty old, it's COMPAQ nc8000 and during original installation I had to use additional parameter FORCEPAE"
1735911,2018-12-04 08:38:59 UTC,"I am uncertain how this is related to the packages website, or an issue with it.  Your report unfortunately doesn't contain enough information to help you further."
1735913,2017-12-11 23:49:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735913,2017-12-14 03:01:03 UTC,This appears to be a compiler bug. Not a problem with the nvidia driver itself.
1735916,2018-12-05 14:45:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735922,2017-12-05 00:50:06 UTC,"I just noticed something else strange about this bug.  It seems to be dependent on the number of taskbar applications exist.  I found myself in the system state such that the system tray was blurry; I opened a 6th application and the system tray immediately got sharp.  I repeated the transition (from 5 to 6 applications) several times; Each time as I dropped below 6 application, the system tray got blurry, and it got sharp again when I started up the 6th application."
1735929,2018-04-10 19:59:38 UTC,This bug was fixed in the package gnome-session - 3.28.1-0ubuntu1
1735929,2018-04-13 15:14:51 UTC,"Is there anything left to land here? I just installed the 2018-04-13 desktop iso, and while ~/.config has correct permissions, ~/.local does not."
1735929,2017-12-05 01:48:09 UTC,"Oh, that's an interesting possibility. Thanks."
1735929,2018-04-14 16:26:25 UTC,Hello.
1735929,2018-04-14 16:37:45 UTC,"Hi daniel,"
1735929,2018-04-24 13:31:41 UTC,"I tested the 2018-04-21 daily image, and the permissions on ~/.config and ~/.local are OK now."
1735929,2018-04-19 13:34:58 UTC,This bug was fixed in the package xorg-server - 2:1.19.6-1ubuntu4
1735929,2018-04-06 14:12:00 UTC,Change attached to the upstream bug
1735929,2017-12-05 01:37:11 UTC,"Hello Seth, thank you for your answer.
It is so strange. As far as I know it was done so all users could access ~/Public directory and this does not apply to the directories like .config and .local which could contain private information and application settings.
~/.cache folder still contains 700.
I had correct permissions for those folders before (for example 14.04, 16.04):
/home
----/user1 (755)
--------/Public (755)
--------/.config (700)
--------/.local (700)
--------/.cache (700)
In normal circumstances .config and .local folders will be created by xdg-user-dirs-update utility with 700 permissions. Is it possible that xdg utility doesn't execute correct?"
1735929,2017-12-05 00:37:08 UTC,"Hell User2233, this is an intentional design choice to enable users to share with each other. If this isn't appropriate for your environment you can modify the DIR_MODE variable in /etc/adduser.conf to set the permissions as desired."
1735929,2018-04-15 10:09:28 UTC,Hi Marc.
1735929,2018-03-29 14:05:53 UTC,"The weird version is no-go, bionic-proposed is not supposed to be used, it's a pocket designed for packages testing and validation, if you opt in for that you should know what you are doing. It's easy enough to go back, just install dconf-server/bionic libdconf1/bionic etc for all the dconf binaries you need"
1735929,2017-12-05 10:39:28 UTC,"On Ubuntu MATE 17.10 I can confirm ~/.config is drwxr-xr-x
However with a new user ~/.cache is drwxrwxr-x and ~/.local is drwx------"
1735929,2018-03-29 13:19:32 UTC,Next proposal:
1735929,2017-12-05 12:07:30 UTC,This is definitely a regression compared to previous releases and needs investigation.
1735929,2017-12-05 14:59:20 UTC,I can reproduce this issue with the 17.10 desktop installer.
1735929,2017-12-05 15:15:11 UTC,"With the 17.04 installer, only .local seems to be affected."
1735929,2017-12-05 15:26:50 UTC,Looks like 16.04 is unaffected.
1735929,2017-12-05 15:35:57 UTC,"Here is one:
http://bazaar.launchpad.net/~ubuntu-desktop/session-migration/trunk/view/head:/src/session-migration.c#L270"
1735929,2017-12-05 16:11:20 UTC,"Here's another:
https://git.gnome.org/browse/dconf/tree/service/dconf-gvdb-utils.c#n177
https://git.gnome.org/browse/dconf/tree/service/dconf-keyfile-writer.c#n210"
1735929,2017-12-05 17:02:52 UTC,"and another:
https://git.gnome.org/browse/gnome-session/tree/gnome-session/gsm-util.c?h=gnome-3-26#n99"
1735929,2018-01-19 07:58:10 UTC,"Didier, could you have a look to the session-migration part of the issue?"
1735929,2018-03-29 13:42:36 UTC,This bug was fixed in the package d-conf - 0.26.0-2ubuntu3
1735929,2018-04-13 15:30:22 UTC,Here's another:
1735929,2018-01-23 18:11:59 UTC,This bug was fixed in the package session-migration - 0.3.3
1735929,2018-03-29 12:36:47 UTC,"Also, this is why I try suggesting really strongly to you guys not to run -proposed during the development cycle because these kind of removals happen."
1735929,2018-03-29 12:27:15 UTC,"dino99, we can't easily just set the version higher since the autopkgtest issue is triggered by 0.26.1 and higher versions."
1735929,2018-01-19 08:23:36 UTC,"Sure, will have a look on the directory creation permission"
1735929,2018-03-29 12:21:01 UTC,"Yeah but that tweak is quite dirty: try to downgrade from 0.26.1-3ubuntu2 to 0.26.0-2ubuntu3, and you are proposed to remove half of the packages list."
1735929,2018-03-29 11:59:00 UTC,"No, that was ""dconf"" (rename) and that never migrated to bionic due to armhf autopkgtest issues, I deleted that version to land that fix, the update can be uploaded again if someone figures out the test issues"
1735929,2018-03-29 09:10:23 UTC,d-conf (0.26.0-2ubuntu3) bionic; urgency=medium
1735929,2018-03-07 10:31:33 UTC,Any further progress on these issues?
1735929,2018-02-02 14:31:32 UTC,Related bug in ubuntu-mate-welcome: bug 1745929
1735930,2017-12-08 10:49:07 UTC,"@Lars / Robie - I set triaged, but please confirm that this is on any of your task lists to be picked up."
1735930,2018-02-21 07:43:48 UTC,"The ""post"" operation for mysql-systemd-start has actually been removed completely in the bionic merge; The systemd unit now uses the --daemonize option (server process forks when ready) and Type=forking"
1735930,2017-12-08 10:49:56 UTC,I know a merge is currently ongoing but not yet complete for Bionic - maybe it could be picked up there.
1735930,2017-12-08 10:48:37 UTC,"This totally LGTM
minimized showcase"
1735944,2018-07-20 06:58:40 UTC,"Hmm, that's really odd. I'm sorry you haven't had a solution yet."
1735944,2018-04-09 11:19:26 UTC,Putting the gateway in quotes does not help. Still the same way.
1735944,2018-04-09 07:14:21 UTC,"The IPv6 should be in quotes when entering with gateway.
Hope this should work"
1735944,2018-02-26 14:56:55 UTC,"I think this is ""just"" a syntax issue. Try quotes around the IPv6 address in gateway6. :/"
1735944,2017-12-11 01:37:35 UTC,I would really like to know what needs to be done to fix this. I get the same on every install and updates are quite tedious waiting for it to time out on IPv6 addresses.
1735953,2018-09-02 06:02:52 UTC,There's a hacky workaround to disable quotas that makes the error vanish from the logs. Not sure of sideeffects.
1735953,2017-12-03 04:20:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1735953,2017-12-04 16:06:54 UTC,"Are you using btrfs, zfs and/or xfs on the server where the exported share is?"
1735953,2017-12-05 09:20:44 UTC,"Yes, it's on a btrfs partition in line with the samba bug."
1735953,2017-12-07 02:46:04 UTC,"I was mistaken about the cause of this bug. It appears that some default setting has changed, and cifs mounts need uid and gid options passed explicitly. In previous Ubuntu versions, I could mount cifs with just credentials provided I set the owners of the mount point and remote files correctly, a one-time detail. In Ubuntu 17.10, if I fail to pass uid,gid to cifs mount options, it's mounted as root:root and the only access is by everyone permissions or if I'm root."
1735953,2017-12-07 11:42:15 UTC,"When you use the uid/gid options, do all files in the share get owned by that uid/gid?"
1735953,2017-12-07 11:43:17 UTC,"Oh, and I meant to add that this NAS is using btrfs"
1735953,2018-09-02 05:27:32 UTC,Same bug on 18.04 samba + btrfs.
1735953,2019-11-18 21:42:36 UTC,"The ""sys_path_to_bdev() failed for path [.]!"" error has already been posted upstream 5 years ago (https://bugzilla.samba.org/show_bug.cgi?id=10541), yet this error still shows up. It doesn't do harm in my setup, but it's annoying and clutters the logs. I've done some Google-Fu on this matter and I think I've found the root cause and an easy workaround."
1735969,2020-02-05 01:29:35 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1735969,2017-12-22 09:13:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735969,2017-12-22 09:17:01 UTC,Windows move to the back (bottom of the stack) without being touched or asked to.
1735976,2017-12-03 12:26:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1735976,2017-12-08 08:45:43 UTC,Thank you!
1735976,2017-12-08 06:43:20 UTC,"I remove my objections to the boot routine. It was a hardware problem.
This morning things were so bad that I decided to switch monitors.
I unplugged the VGA connectors from both monitors, and swapped them.
The ""new"" configuration was much better, with no turning off of the monitor.
The next step was to switch back. Again all was well.
Conclusion: a hardware problem, probably one of the pins in the VGA connector was intermittent."
1735976,2017-12-07 07:51:13 UTC,Thank you!
1735976,2017-12-07 07:17:17 UTC,"While this is not a security issue, it is an issue which may cause hardware damage.
Turning the monitor on and off 10+ times during a boot can't add health to the monitor itself."
1735976,2017-12-04 07:19:02 UTC,Thank you for your feedback.
1735976,2017-12-04 05:28:58 UTC,"Thanks for connecting my question
https://answers.launchpad.net/ubuntu/+question/661125
to this bug. I do agree that there seems to be a connection."
1735979,2017-12-03 12:26:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1735981,2017-12-03 22:46:54 UTC,I also have no success with
1735981,2017-12-03 10:59:41 UTC,"And just double-checked, works under Windows."
1735981,2017-12-03 10:40:42 UTC,"Hi, this is the excerpt from the journal from ModemManager and NetworkManager"
1735981,2017-12-03 22:07:21 UTC,"So mmcli will show me that the modem is alive,
but still the issue that I don't get an IP. Thoughts ?"
1735981,2019-10-24 20:23:43 UTC,Works with Philipp Hufnagl's workaround.
1735981,2018-09-06 05:07:10 UTC,"Hi, just an update, no connectivity out-of-the-box
with 18.04:"
1735981,2018-04-13 14:17:12 UTC,"Steffen Neumann,"
1735981,2019-10-24 20:31:10 UTC,Workarount badpractice works! Thank you!
1735981,2018-03-19 16:43:12 UTC,"I can confirm that the workaround above by Philipp Hufnagl
indeed does the job. I am writing this comment from aboard a train ;-)
The connction setup is not very robust, and sometimes
fails at Simple connect state (4/8): Wait to get fully enabled"
1735981,2018-02-23 23:25:12 UTC,workaroud:
1735981,2018-02-23 23:23:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735981,2018-01-17 06:15:06 UTC,"Even after a few apt dist-upgrades over time, no change.
dmesg has as last two lines"
1735981,2019-11-09 14:38:14 UTC,"Hi, just want to update that the problem still exists under 19.10 live system.
I couldn't test whether the 77-mm-huawei-net-port-types.rules fix works,
since I only have a live-USB system where I can't add the file early enough."
1735981,2018-09-06 06:05:30 UTC,And then I changed the file below and now have a working connection:
1735986,2017-12-03 12:27:22 UTC,apport information
1735986,2019-10-25 11:08:10 UTC,"Same issue for me on Ubuntu 19.10 and Wayland. Laptop screen (primary) is 1080p at 100%, one external display is 4K at 200%. Opening Chrome and moving it to the external display has no effect: it stays super small."
1735986,2018-05-01 12:35:30 UTC,Upstream report https://gitlab.gnome.org/GNOME/gnome-control-center/issues/17
1735986,2018-03-19 02:25:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735986,2018-01-11 00:46:27 UTC,"I just installed a fresh install of Ubuntu artful (17.10) yesterday, on a Dell XPS 13 9630, and am affected by the same issue."
1735986,2018-01-11 00:38:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735986,2017-12-03 12:27:24 UTC,apport information
1735986,2017-12-03 12:27:23 UTC,apport information
1735986,2020-04-23 12:44:44 UTC,"This is affecting me on Ubuntu 20.04. My first monitor is 1080p, and my second monitor is 2K. Everything is small on the 2K monitor, and I'm trying to fractionally scale the display to 125%. This results in the display automatically going to 200% instead of 125%. The display crashes when I subsequently turn off fractional scaling."
1735986,2020-04-28 07:41:53 UTC,"Dale, it sounds like you're experiencing a different issue like maybe bug 1870736 and/or bug 1873403."
1735988,2017-12-03 14:33:19 UTC,"This is how the window looks like.
I am using Czech as my default language."
1735991,2018-08-10 08:27:18 UTC,"I resolved the issue by setting proper Page Size (62 x 38 mm) in CUPS and glabels. My QL-570 is now working with the latest driver version 1.4.2-3+b1 from Ubuntu. I attached the glabels template for reference. It is also possible to print smaller labels (same width, different height) without adjusting the printer settings. Perfect!"
1735991,2018-02-06 18:21:05 UTC,"To clear things up, I was referring to Page Size in CUPS when saying Media Size."
1735991,2018-02-06 18:41:28 UTC,I attached the log file for a failed print job from /var/log/cups/error.log. I am not entirely sure I was using driver version 1.4.2-2 at the time. Maybe this helps though.
1735991,2017-12-03 21:57:40 UTC,The most common issue which can cause this is setting the Page Size incorrectly in the driver. You'll get the red flashing light if the intended page size doesn't match the label.
1735991,2017-12-04 08:08:18 UTC,"I tried with several applications like LibreOffice.
I tried with the function ""print test page"" directly from cups admin.
What is strange is that cups indicates that jobs are completed."
1735991,2017-12-18 22:52:03 UTC,"Clean Print Head doesn't apply to the QL driver. ""cleaning"" the heads requires either a cleaning card or a bit of manual work (can't remember if the 570 is like a Zebra printer; the instructions should be in the manual)."
1735991,2017-12-18 22:52:46 UTC,Another thought - can you also post the Brother part number of the labels you're using please? (then I can look that up and make sure your page size is right)
1735991,2017-12-19 12:12:06 UTC,"I used 62mm label width
I add the screenshot"
1735991,2017-12-19 12:19:58 UTC,"I use DK22205 labels.
How can I check what is send to the printer and what is the answer from it ?"
1735991,2018-01-22 17:18:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735991,2018-02-06 18:47:37 UTC,Not sure what happened to the attachment. Gonna try again.
1735991,2018-02-06 17:35:38 UTC,I have the exact same problem with my Brother QL-570 label printer.
1735991,2017-12-19 12:05:49 UTC,"what I meant was that with the function ""Clean Print head"" I have a ""normal"" error while here cups tells me jobs completed and the printer blinks red.
I have try also with glabels and the driver was working well with the previous version on trusty : printer-driver-ptouch (1.3-8).
now printer-driver-ptouch (1.4.2-2)."
1735993,2017-12-03 13:50:05 UTC,"I've realized the new window that is created when you open the external disk unit DOES have an icon on Launcher, which gets selected when it has focus and correctly shows the triangle(s) indicating its existing window(s). But it is separated from Nautilus' main Launcher icon."
1735996,2018-09-20 18:11:11 UTC,"Due to lack of progress, marking Triaged and clearing assignee. Feel
free to revert if it is in fact still in progress :)."
1735996,2017-12-28 04:57:56 UTC,"Uwe or Daniel, would one of you like to assign yourself to take this up for 2.2?"
1735996,2017-12-07 23:45:27 UTC,I won't be able to complete this in time. It turned out that the caching and hashing needs to be changed to implement this properly. Maybe has more dependencies with https://github.com/mixxxdj/mixxx/pull/996 than expected.
1735996,2017-12-04 07:27:44 UTC,"Both issues are unrelated, although targeting overlapping parts of the code."
1735996,2017-12-03 20:20:48 UTC,"The rejected PR for the cover hash might be related.
https://github.com/mixxxdj/mixxx/pull/996"
1735996,2017-12-03 14:02:43 UTC,Should IMHO be fixed before releasing 2.1.0.
1735997,2017-12-08 14:33:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1735998,2018-02-03 14:39:05 UTC,"Ok. I don't have any problem having ""unity-settings"" on universe without removing gsettings from ""ubuntu-settings"". They won't collide. They both set same settings for unity any way."
1735998,2017-12-08 03:31:42 UTC,"> But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings.
"
1735998,2017-12-08 06:26:07 UTC,@Jeremy
1735998,2017-12-08 16:28:51 UTC,"Ok, I see how you need a unity-settings binary package for #4. But I still don't see why you need to remove gsettings overrides from ubuntu-settings. And I think almost all customizations except #4 could go in the ubuntu-settings package."
1735998,2018-02-02 15:40:29 UTC,@Jeremy
1735998,2018-02-02 17:50:47 UTC,@khurshid
1735998,2018-02-02 18:14:17 UTC,"> Is there any specific reason to carry unity specific gsettings overrides in ubuntu-settings? Unity is not a default desktop anymore nor it is installed in the default live iso.
"
1736001,2018-09-17 13:13:06 UTC,"Vector icons* for the Preview button scale with the line height.
BPM lock and 'Played' checkbox still remain at their original size."
1736001,2020-03-29 21:57:04 UTC,"fix for Search bar:
https://github.com/mixxxdj/mixxx/pull/2400"
1736011,2017-12-15 07:23:46 UTC,I have the same error after a clean install (today) of 17.10 using nvidia 384.98 driver in an xorg gnome session. I presume the screensaver failure is responsible for a failure to switch users.
1736011,2017-12-08 13:15:24 UTC,"I was getting this error on Ubuntu 17.10 on a Mac Pro 2,1 and was also having problems with soft lockups associated with errors saying ""CPU#x was stuck for 22s"" (where x was the CPU number). When I removed gnome-screensaver, both issues stopped. However, when I reinstalled gnome-screensaver, the bug here (CRITICAL: Unable to create a DBus proxy for GnomeScreensaver) started happening again but the CPU lockups did not."
1736011,2019-12-08 13:27:32 UTC,"So I still see this bug on several machines here that runs Ubuntu 20.04 with Gnome Flashback. And I suspects this bug causes Updatemanager to fail sometimes when the system autostarts it while the screensaver is activated. (The program is running minimized, but unable to unminimize. You have to close/kill it and manually start it)"
1736011,2019-06-12 01:38:26 UTC,"David, see bug 1832138."
1736011,2019-06-11 13:54:24 UTC,"I posted too soon.  It turns out that in my case the error was a red-herring.  I loaded a backed up VM without the latest Ubuntu updates and I am able to log in fine even though the syslog still contains the error:
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1"
1736011,2019-06-11 13:13:35 UTC,Same issue after an update this morning on Ubuntu 18.04.  Running Ubuntu in a VMWare Workstation.  My login screen never appears after startup.
1736011,2019-06-03 21:17:42 UTC,Same problem on ubuntu 18.10. Everything crashes when the screen timouts or goes in powersaving who knows. Every app closes and I have to login again.
1736011,2017-12-22 07:41:40 UTC,"For me problem happens when using two monitors with ""high"" resolution 3840x2160 (had two older monitors until yesterday). I use a Lenovo x260 and a dock. Machine freezes. From my logs"
1736011,2019-04-10 11:45:43 UTC,I no longer see this bug in Ubuntu 19.04/disco.
1736011,2018-04-08 13:45:34 UTC,"I also see those error messages on 2 systems.  Compared to other people:
 - it has nothing to with the locale (I use en_US.UTF-8 for everything)
 - my systems use an Intel GPU (not NVidia)
 - I do not use a HiDPI screen (only FullHD)
 - I have no delay when logging in"
1736011,2018-03-17 17:13:04 UTC,"Same here (Ubuntu 17.10):
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1"
1736011,2018-01-12 21:25:22 UTC,I too have the error displayed in the original bug.
1736011,2018-01-11 01:51:36 UTC,"hamid,"
1736011,2018-01-10 10:05:54 UTC,"vanvugt,"
1736011,2018-01-10 09:44:00 UTC,"dino99,"
1736011,2017-12-03 16:57:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736011,2018-08-20 01:36:29 UTC,"Indeed, removing all extensions should be the first thing to check when dealing with gnome-shell bugs."
1736011,2019-04-28 06:34:01 UTC,"lsb_release -a gives me :
LSB Version:	core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic"
1736011,2018-08-18 14:41:36 UTC,"Can everyone clear their gnome-shell extensions and check this isn't the cause of the issue? If so, I think we need a better way of handling extension crashes."
1736011,2018-12-07 11:16:29 UTC,"I can confirm the bug on an HP Laptop.
I got no gnome-shell extensions installed
I don't find it in the login, but I feel there's a quite long delay after logging in and before the desktop starts"
1736011,2018-12-07 14:31:00 UTC,"I still have the same issue on my Desktop PC, now running 18.04, fresh install (not upgrade from the  17.10 that had this issue), it takes a good ~8-10 seconds for my desktop to show after hitting enter on the login prompt."
1736011,2019-01-31 01:35:37 UTC,+1
1736011,2019-03-11 23:06:20 UTC,"It says the sender of this error is gnome-session-b? who's that? where's the code that generates this error? I'm on 18.10, upgraded from 18.04"
1736012,2020-07-01 21:12:35 UTC,"thank you for your bug report, that does sound like a local corruption rather than a package bug though"
1736014,2017-12-04 03:01:57 UTC,Branch was merged. Thx!
1736014,2017-12-04 00:38:25 UTC,"Made a branch that also fixes the strings:
https://gitlab.com/inkscape/inkscape/merge_requests/147"
1736014,2017-12-03 19:52:52 UTC,Attached a possible solution.
1736014,2019-05-17 13:55:18 UTC,"As this was only ever in master, closing as fix released."
1736014,2019-06-20 03:37:45 UTC,Capitalizing the H just to get the bug credited correctly ;-)
1736024,2018-09-11 13:49:55 UTC,"Still valid with 0.92+devel (8a74b4bce4, 2018-09-10)"
1736028,2017-12-03 20:51:43 UTC,"System uname: Linux-4.14.3-gentoo-x86_64-Intel-R-_Core-TM-_i7-3770K_CPU_@_3.50GHz-with-gentoo-2.4.1
KiB Mem:     8134984 total,   1112276 free
KiB Swap:    1048572 total,   1048572 free
Timestamp of repository gentoo: Sun, 03 Dec 2017 14:47:52 +0000
Head commit of repository gentoo: 5298e145f0830b5426ae8ee293d16f61ccd1a80f"
1736028,2017-12-05 00:55:13 UTC,Looks like these crashes are gcc-7 related. The tests are passing when percona-server was built with gcc-6.4.0.
1736028,2017-12-05 14:57:43 UTC,"While https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=190b8440424d0684880808bb8d6587078a7357ef fixed building against GCC-7, percona-server isn't GCC-7 compatible yet:"
1736028,2017-12-05 15:01:25 UTC,"Created attachment 508258
build.log"
1736028,2017-12-05 15:43:32 UTC,The bug has been referenced in the following commit(s):
1736028,2017-12-05 19:57:08 UTC,"If someone else is wondering how to ""use package.env file to switch to <gcc-7.x for this package"", the following has worked for me:"
1736028,2017-12-18 16:51:16 UTC,">=dev-db/percona-server-5.6.38.83.0 now works with gcc-7.
"
1736028,2018-01-25 08:40:18 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3761
1736038,2017-12-04 01:57:44 UTC,"Quick note on 2:
What I described (window can not grow large than the screen) is actually the desired behavior, see [1]. If it grows larger for you that seems to be a bug - as we ""do everything correct"" as far as I see it might be yet another gtk3 bug though (content scaling in gtk3 is a mess - most of the stuff does not work at all for practical purposes and upstream won't acknowledge it)."
1736038,2017-12-04 01:53:08 UTC,"Let's see if we can address this properly in this bug (usually it's much better to file one issue per bug, otherwise some will fall into oblivion and the bug will linger forever):"
1736038,2017-12-04 02:31:13 UTC,Sorry for the low quality report...
1736042,2021-01-10 04:17:42 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1736042,2020-11-10 17:54:55 UTC,Have you ever tried the suggestions from Liang Yan ?
1736042,2017-12-08 22:42:08 UTC,"This looks not a QEMU bug to me. You may drop ""-curses"" first, and run again. Once get inside, change grub file(/etc/default/grub) by uncomment GRUB_TERMINAL=console. It should work then. If still not, then blacklist vga16fb and add ""fbcon=map:99 text"" in grub command line. Remember to run update-grub after change configure file."
1736042,2017-12-04 12:08:45 UTC,And it still happens on:
1736042,2017-12-04 12:00:48 UTC,"I want a fix ;) and I do expect qemu to get it faster then Ubuntu.
So I set up Ubuntu Zesty(to fullfill dependencies) and build qemu:
QEMU emulator version 2.10.1 (v2.10.1-dirty)
and... it's still there."
1736042,2017-12-04 07:18:41 UTC,"Please always use the latest version of QEMU (currently v2.10, soon v2.11) when reporting bugs to the upstream QEMU project - we don't support old versions like v2.5 any more. So I guess you wanted to report a bug agains v2.5 in Ubuntu instead and I changed the target of this bug accordingly."
1736046,2017-12-21 08:03:26 UTC,Confirmed. Although many would argue this is a nice bug to have.
1736046,2017-12-21 08:02:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736050,2017-12-13 22:47:36 UTC,"It's still unclear to me what ""binding"" means and is used by Juju. I think it's the endpoint of the provided relation (per above, ""network-get nrpe-external-master"")."
1736050,2017-12-14 03:02:39 UTC,"If there are no spaces, nor bindings specified, juju should report the address that would be used to contact the API servers."
1736050,2017-12-12 12:08:57 UTC,"Is this a case of ""without setting a specific binding, we end up selecting an arbitrary IP that you feel is incorrect""?
I suppose it could be ""when guessing what IP to use, prefer the IP associated with the default gateway"".
I think its still guessing, rather than doing something the user explicitly requested. It could be a more educated guess, but I'd like to make sure we have a way for the user to be specific before we do lots of work on heuristics that will always be wrong some of the time."
1736050,2017-12-04 22:45:51 UTC,"Even with 'network-get', the IP address returned is clearly wrong:"
1736050,2017-12-04 21:19:59 UTC,I would think it would return the source IP used for the default route (as per above it would be '10.222.128.23').
1736050,2017-12-04 12:45:21 UTC,"How are we to tell what address is ""wrong"" vs ""right"" when all addresses
are private. (10.220.254.1 is certainly an RFC 1918 address.)"
1736065,2018-01-03 06:24:19 UTC,"Reviewed:  https://review.opencontrail.org/38601
Committed: http://github.com/Juniper/contrail-ansible-internal/commit/f26b2123923153fec3d93a71814121a33c475952
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1736065,2018-01-02 05:09:16 UTC,"Review in progress for https://review.opencontrail.org/38600
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1736065,2018-01-01 21:53:35 UTC,"Review in progress for https://review.opencontrail.org/38598
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1736065,2018-01-03 00:06:00 UTC,"Review in progress for https://review.opencontrail.org/38601
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1736065,2018-01-02 05:12:48 UTC,"Review in progress for https://review.opencontrail.org/38601
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1736065,2018-01-02 23:55:51 UTC,"Review in progress for https://review.opencontrail.org/38598
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1736065,2018-03-10 18:38:33 UTC,Not valid for mainline due to micro-services architecture
1736065,2018-02-28 22:13:59 UTC,Container structure has changed in R5.0. It's microservices based with no support for systemd etc.
1736065,2018-01-03 10:56:10 UTC,"Reviewed:  https://review.opencontrail.org/38598
Committed: http://github.com/Juniper/contrail-ansible-internal/commit/3920798a9a546a6978731e0f3571a317e1a8f7e5
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1736067,2016-12-23 23:59:52 UTC,"Over a period of almost six days, the xfce4-indicator-plugin has grown to take up about 1.6 GiB of memory (RSS). 2.4 GiB has been seen on a previous instance of the process."
1736067,2016-12-24 10:20:49 UTC,"Hi,"
1736067,2016-12-27 05:01:17 UTC,"(In reply to Andrzej from comment #1)

> Hi,
>
> Can you provide information on version of the plugin and names of the
> indicators displayed in it (in ""known indicators"" list)?
"
1736067,2018-02-23 03:08:58 UTC,Currently at 2.3Gb ram up 11 days(ubuntu Studio)
1736067,2018-08-18 20:55:26 UTC,Which Ubuntu release exactly? Please test with 18.04 also.
1736076,2017-12-04 11:41:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525161"
1736076,2018-11-05 06:22:43 UTC,"Change abandoned by Xinran WANG (<email address hidden>) on branch: master
Review: https://review.openstack.org/525161"
1736081,2018-01-24 22:37:49 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1466
1736084,2017-12-04 09:34:22 UTC,(the example in comment #3 is missing the top line: @define-color border-grey #444;)
1736084,2017-12-04 09:13:10 UTC,The first snippet you showed doesn't do anything for me (not even for other GNOME windows).
1736084,2017-12-04 09:32:49 UTC,"As a demonstration that the first snippet does work for at least some apps on my 17.10 system, please find attached a screenshot showing part of a gedit window loaded after making gtk.css look like this:"
1736089,2017-12-27 07:10:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736111,2017-12-18 09:37:55 UTC,"Change abandoned by paresh sao (<email address hidden>) on branch: master
Review: https://review.openstack.org/525128
Reason: No need of this patch"
1736111,2017-12-04 10:34:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525128"
1736112,2018-09-25 20:25:42 UTC,For some reason the problem seems to be solved in Ubuntu 18.04.
1736122,2017-12-13 14:33:05 UTC,"Правильно я понимаю? У тебя есть диск, он отформатирован в нормальную файловую систему (ext4, xfs, и.т.п). На нем лежат CUE файлы и аудио к ним. И ты примонтировал его через файловый менеджер (dolphin, GNOME/Files, Thunar и.т.д.) или из консоли в /media/XXXX. И что, остальные программы видят файлы на диске, а flacon нет? Очень странно, программа использует стандартные функции для чтения файлов, ей плевать на каком диске лежат файлы, если они видны в системе она должна их показать."
1736122,2017-12-13 13:01:49 UTC,"Добрый день,"
1736122,2017-12-05 04:02:44 UTC,"What do you mean by ""see the SATA hdd""? The flacon isn't a program for CD ripping, it works with the audio files."
1736142,2017-12-20 10:19:03 UTC,Confirmed on Gnome Shell too. And looking at the source code I can't find an icon at all. In fact I can't see any icons present in the PulseAudio source :)
1736146,2017-12-04 13:26:07 UTC,"StacktraceTop:
 list_del (item=<optimized out>) at ../../../../src/util/list.h:91
 pb_slab_reclaim (slabs=slabs@entry=0x55d99bb03328, entry=0x0) at ../../../../src/gallium/auxiliary/pipebuffer/pb_slab.c:58
 pb_slabs_deinit (slabs=slabs@entry=0x55d99bb03328) at ../../../../src/gallium/auxiliary/pipebuffer/pb_slab.c:247
 si_destroy_context (context=context@entry=0x55d99bafc8b0) at ../../../../../src/gallium/drivers/radeonsi/si_pipe.c:99
 si_create_context (screen=screen@entry=0x55d99baf1d60, flags=flags@entry=0) at ../../../../../src/gallium/drivers/radeonsi/si_pipe.c:382"
1736156,2018-01-25 08:40:21 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3762
1736157,2017-12-04 14:57:40 UTC,"DNS resolution suspiciously stops working after a restart of unbound that occurs ~5 seconds before:
http://logs.openstack.org/07/472607/145/check/tripleo-ci-centos-7-containers-multinode/ae132c1/job-output.txt.gz#_2017-12-02_23_21_33_419832"
1736157,2017-12-04 15:17:13 UTC,Sagi sent a patch to remove the restart of Unbound: https://review.openstack.org/#/c/525228/
1736157,2017-12-04 14:50:18 UTC,"Within the same job, DNS resolution will work and suddenly stop working."
1736173,2017-12-05 14:55:11 UTC,Adding a link to an IRC discussion for those seeking more information:
1736174,2019-07-19 21:01:51 UTC,Thank you for filing the bug.  Is this bug still affecting you?
1736174,2018-05-14 11:38:54 UTC,"I am currently preparing CentOS 7.5 Cloud Init images for my Linux trainings and am also affected by this bug. It might also be good to be able to disable this flaky auto detection, as there is already a config option `preserve_hostname` for preserving the hostname."
1736174,2018-05-14 12:42:57 UTC,The check of course also fails when using cloud-init to adapt a cloud-init image where cloud-init initially has been run:
1736174,2018-05-14 12:19:57 UTC,I'm not sure how to get this reviewed by a contributor.  It doesn't look like my bug report has had any action as it is still status New.
1736174,2019-07-23 20:08:00 UTC,"It does not appear there has been any change to the source.
We continue to patch this internally in our environment."
1736174,2018-05-14 12:09:15 UTC,"Your work-around appears to work, thanks Albert."
1736176,2018-10-15 19:44:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736176,2020-03-04 18:26:34 UTC,"Hi,
is it possible to make ScrollLock key to be settable as Left/Right/Up/Down keys."
1736176,2019-09-22 21:10:54 UTC,"Please, make this option configurable, because as for now after so many years i can't use LibreOffice :("
1736176,2018-12-27 17:36:28 UTC,*** Bug 120869 has been marked as a duplicate of this bug. ***
1736176,2018-11-14 07:59:22 UTC,"Yes - this is really a bizarre thing, because before there was no problem with it."
1736176,2018-11-14 05:30:47 UTC,"(In reply to Vladimir from comment #22)

> ... and when i diceded to google it - what i saw? Proposal to change default
> befaviour of so many distros and DEs instead of adding a simple option?
"
1736176,2018-11-14 00:14:25 UTC,"This is sooo unbelivable that this stupid bug is still not fixed!
I was suffering from it so many times, and when i diceded to google it - what i saw? Proposal to change default befaviour of so many distros and DEs instead of adding a simple option?"
1736176,2018-10-15 19:55:55 UTC,"Ubuntu 14.04 LTS with LibreOffice 6.0 from PPA is affected.
Ubuntu 16.04 LTS with LibreOffice 6.0 from PPA is affected.
Ubuntu 18.04 LTS seems to be affected too."
1736176,2018-10-15 19:54:43 UTC,"ScrollLock behavior should be configurable.
I use ScrollLock LED as indicator of alternative keyboard layout:"
1736176,2018-09-30 16:53:55 UTC,*** Bug 120206 has been marked as a duplicate of this bug. ***
1736176,2018-07-19 00:44:19 UTC,"(In reply to kolrac from comment #11)

> If, however, developers decided to add such an option I think it
> should be disabled by default and the decision to enable it should be left
> to distro maintainers and/or the end users in order to avoid confusing the
> huge majority of the user base.
"
1736176,2017-10-04 13:38:01 UTC,"Seems reasonable, it was also requested in bug 46200 comment 31 and in bug 111627 (which also seems to be about a bug, but needs more details from the reporter).
I'm not sure why the feature should be deactivated by default, though, that needs further reasoning. CCing the others who requested this before."
1736176,2017-10-04 13:46:55 UTC,"In debian, in a multi language config it should be disabled by default as debian uses scroll lock like this by default. On other distros it shouldn't."
1736176,2017-10-04 14:47:01 UTC,"Hi,"
1736176,2018-08-21 04:51:22 UTC,(In reply to kolrac from comment #11)
1736176,2017-10-05 07:25:59 UTC,What I understand is that Shay wants to reconfigure the shortcut. For other functions that's done via tools > customize (greatly improved for 6.0) where .uno:ScrollLock should be bound to .key:ScrollLock (or whatever this is labeled internally). And this assignment can be removed or redefined.
1736176,2017-10-05 14:04:34 UTC,"(In reply to Heiko Tietze from comment #4)

> What I understand is that Shay wants to reconfigure the shortcut. For other
> functions that's done via tools > customize (greatly improved for 6.0) where
> .uno:ScrollLock should be bound to .key:ScrollLock (or whatever this is
> labeled internally). And this assignment can be removed or redefined.
"
1736176,2017-11-14 21:23:44 UTC,"I didn't know how to point that I have this issue for 5.4.1.2 release and then I changed ""Version"" to 5.4.1.2, but I forgot what was the previous version pointed, sorry. (Something like 5.3.1 or something..)"
1736176,2017-11-19 11:15:28 UTC,"LED indication of the keyboard layout is the default for Debian based distros which is a significant percentage in terms of number of users. So I don't see why LibreOffice should make its default configuration conflicting with all these systems.
Besides, as is was pointed out, it is just a third way to scroll. It is an open question how many people prefer this one."
1736176,2017-10-04 12:30:28 UTC,"Hi,"
1736176,2017-11-19 11:42:31 UTC,"(In reply to Sergey from comment #7)

> So I don't see why LibreOffice should make its default configuration conflicting
> with all these systems.
"
1736176,2017-11-30 16:42:58 UTC,Scroll Lock option is needed.
1736176,2018-01-08 14:22:11 UTC,"This is not the disturbing of a normal feature: some people assigned a feature to the Scroll Lock key  because of a bug in X11 and Wayland which prevents the key from working as expected. The normal feature, as originally intended, is to modify the behavior of arrow keys and that’s what LO Calc now does."
1736176,2018-02-13 08:42:35 UTC,Would be nice if the option gets predefined depending on the system capability whether scroll lock is available or not.
1736176,2018-02-15 15:31:49 UTC,Availabilty still doesn't tell anything about whether it behaves as expected or is unexpectedly abused by some Window manager or other means as an LED indicator activating the lock.
1736176,2018-02-15 15:58:02 UTC,"An option scroll behaviour with 3 choices would solve the problem:
* keyboard (as read from desktop system)
* on (permanent on)
* off (permanent off)"
1736176,2018-03-07 01:23:46 UTC,*** Bug 116250 has been marked as a duplicate of this bug. ***
1736176,2018-03-07 13:20:00 UTC,"Changing the bug title because a configurable option is a possible fix, not the problem itself; and also to avoid dupes being created (like bug 116250)."
1736176,2018-07-19 00:18:19 UTC,Don't see why this easyhack needs much evaluation. It's known which commit ( http://cgit.freedesktop.org/libreoffice/core/commit/?id=453de3473cf6f383c71466a1ed15e28b844ed7e5 for bug 46200 ) changed the behaviour; so the only thing that is needed is to take a new configuration into account when evaluating the value of bool bScrollLock in ScCellShell::ExecuteCursor. I am sure that Heiko could assist with the new configuration option bits.
1736176,2017-11-19 12:52:03 UTC,"(In reply to Heiko Tietze from comment #8)

> (In reply to Sergey from comment #7)
> > So I don't see why LibreOffice should make its default configuration conflicting
> > with all these systems.
>
> When a user wants to configure the scroll key him or herself, why not? By
> default it will be empty, of course.
>
> Removing UX, dev please add scrollkey to customization.
"
1736177,2018-01-20 07:44:50 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1486
1736177,2017-12-18 17:39:37 UTC,And the info i provided:
1736177,2017-12-15 14:40:24 UTC,"Hi, still unable to reproduce with select queries on my test case, gave 900 seconds as you did:"
1736177,2017-12-04 15:43:38 UTC,"Hi,
Could you please specify the version of xtrabackup and MySQL server and provide my.cnf?
Also any other info to help understand and reproduce the issue will be appreciated."
1736177,2017-12-04 18:21:41 UTC,"xtrabackup version 2.4.8
planning to upgrade to 2.4.9 before end of year."
1736177,2017-12-04 18:29:22 UTC,"I have seen this in the past when it has tried to kill the same query twice, but that was not the case with the 1st example i sent. here is another example , but tried to kill a query that it has already killed:"
1736177,2017-12-08 10:54:56 UTC,"Hi,
Sorry for late reply.
I have tested with PXB 2.4.9 + PS 5.7(an ordinary server) and could not reproduce the segfault with repeated killing. Do you have some another info which can help to reproduce this issue?"
1736177,2017-12-08 16:30:51 UTC,"Seems to happen when killing long running queries
Have another example of the issue:"
1736177,2017-12-18 14:42:12 UTC,"Now it looks like yours, but still no success to reproduce:"
1736177,2017-12-15 15:58:51 UTC,"it seems like you are running a different command than I am running? I'm not getting this message:
Waiting 1 seconds for queries running longer than 900 seconds to finish
What command are you running?"
1736177,2017-12-18 22:52:43 UTC,Actually not.
1736177,2017-12-14 17:52:00 UTC,"Any update on this. This is happening on all our databases. Happens every time it has to kill long running query(s).
Another example from today:"
1736179,2018-02-02 05:45:49 UTC,"Hi Patrick,"
1736179,2020-11-20 09:21:34 UTC,"@Nishitha Antony (ni301701).
I am not the bug reporter but got here with the same problem. Your solution works! Thanks a lot!"
1736195,2017-12-07 19:33:18 UTC,The package has been published and the bug is being set to Fix Released
1736195,2017-12-06 10:43:12 UTC,"3.13.0-137.186~precise1 - generic
Regression test CMPL."
1736206,2017-12-05 08:11:17 UTC,"Hi, you can override config files values."
1736215,2017-12-05 22:53:28 UTC,"As suggested to Patrick in IRC, this can be worked around by partitioning with gpt rather than MBR."
1736221,2018-03-12 13:25:07 UTC,I agree with Didier - 3.18.3 has still
1736221,2018-03-12 11:17:14 UTC,3.18.3 lost:
1736221,2017-12-12 07:27:50 UTC,HPLIP 3.17.11 also includes compiled library files:
1736221,2017-12-07 12:56:06 UTC,"Thank you, Badal!"
1736221,2017-12-07 08:37:23 UTC,"Hi,"
1736221,2017-12-05 08:06:25 UTC,"Sorry for misunderstanding - would you mind removing these binaries (not whole tarball)? Because they must not be there (all operating systems should build all these binaries by themselves - because they can have different configurations for compiling hplip) - they seems like leftovers after package testing and it only creates more work for package maintainers, whose need to delete these files."
1736222,2020-11-23 06:45:40 UTC,"I just installed Ubuntu 20.10 on a machine that was running Pop!os 20.04 and 20.10 (a fairly new AMD Ryzen desktop system, different to the machine I had the problem on earlier, which was a laptop). Not 24 hours later, this problem again. I thought there was something wrong with Team app ('bloody microsoft') but then my next meeting in Google Meet had the same problem. And YouTube."
1736222,2020-10-13 05:23:47 UTC,"Is this relevant?  Looks it might have been swept under the rug?
https://bugzilla.mozilla.org/show_bug.cgi?id=1252732"
1736222,2020-09-11 01:31:31 UTC,"I started having issue's with sound being off as it were, I tried different browsers and headphones and was starting to think it was just me... then I notice in the sound settings - application tab that I had 5 speech-dispatchers going and upon doing a Google on them landed here."
1736222,2020-08-29 00:17:20 UTC,My sound control panel reports three speech-dispatcher entries in Volume Levels. I don't know why.
1736222,2020-08-23 06:49:36 UTC,I will try this workaround/config change: https://github.com/brailcom/speechd/issues/198#issuecomment-619605269
1736222,2020-08-23 06:36:37 UTC,This bug started affecting me in the past week although I've been on 20.04 since launch. I have removed the packages including orca.
1736222,2020-05-24 19:14:31 UTC,"I have the same experience as Comment #14 - on a fresh install of 20.04 LTS, this problem randomly (at least it seems random) occurs and is fixed by killing speech-dispatcher."
1736222,2020-06-29 09:41:55 UTC,"I have the same problem.  Killing speech-dispatcher fixes this, but I want to keep it available."
1736222,2018-02-26 12:17:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736222,2018-06-05 19:58:53 UTC,"I'm still getting this with Ubuntu 18.04, with Intel sound and HDMI output."
1736222,2018-07-03 16:12:37 UTC,"Workaround: when I hear the distorted sound, I open a terminal and issue this command"
1736222,2018-07-04 19:06:41 UTC,My comment above about extra processes is described in Bug #1496542
1736222,2019-03-02 00:28:34 UTC,This is also affecting me. I am running an Alienware R4 i7 with an 1070gt gpu.
1736222,2019-03-23 08:46:54 UTC,This affects Ubuntu 18.10 as well. Gets triggered every time while a YT video is playing and i open a website in firefox in special reading view.
1736222,2019-03-31 18:40:08 UTC,"Yup. I have just diagnosed this as well on Cosmic. Suddenly, it started while I was watching film on Netflix in browser. I looked around and noticed three new speech-dispatcher processes connected to pulseaudio. I kept the film running and issued `killall speech-dispatcher` and the distortion stopped immediately."
1736222,2019-04-06 19:47:57 UTC,"For those affected by this who want or need speech-dispatcher, another workaround may be to disable timer-based scheduling for PulseAudio."
1736222,2020-06-30 10:06:21 UTC,Could someone having the issue report it upstream on https://github.com/brailcom/speechd/issues ?
1736222,2019-04-21 17:57:05 UTC,"18.04.2 LTS (Bionic Beaver) Gets triggered every time any sound is playing and I need any screen reading (like a website in firefox in special reading view)
It feels like the existing previous sound output gets used as input for mixing with the screen reader... with the added pronlem that at least 3 screen reader processes are created, thus adding 3 echoes that constitute the noise..."
1736222,2019-04-21 21:29:52 UTC,It may be that it's fixed in most recent version. I am atm using OpenSUSE Tumbleweed and it's the first time since 3-4 years that i do not get this error.
1736222,2019-04-22 09:59:37 UTC,"I was wrong, speech-dispatcher is just not installed on TW by default."
1736222,2020-04-04 08:04:06 UTC,This bug is still present on 20.04 beta I installed yesterday. I was playing a song on Youtube and it became distorted as I started to read a New York Times article. Removing speech-dispatcher fixed the issue once again.
1736222,2020-05-13 12:04:26 UTC,"I'm experiencing this issue on my desktop and my laptop, both of which are running 19.10. The problem went away when I removed speech-dispatcher. I'm going to upgrade to 20.04 later today and will report back on whether that solves the problem."
1736222,2020-05-15 09:35:50 UTC,"Yes, problem persists in a fresh install (not upgrade) of 20.04 LTS. Fixed when killing or removing speech-dispatcher."
1736228,2017-12-04 19:51:35 UTC,Related bug talks about yet another location for vendcodes: https://bugs.launchpad.net/evergreen/+bug/1713138
1736231,2017-12-16 15:27:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736231,2017-12-04 20:12:55 UTC,"not  a bug first hand - it might be that the bionic repo must catch up -
we moved the configuration files a little bit. Could you please attach a
strace of the panel start?"
1736231,2017-12-05 21:02:02 UTC,Well If I add applets to the panel they become after the first login but I will need to strace a new user. So that supports what alf is saying.
1736231,2017-12-06 01:21:06 UTC,"https://pb.5id.eu/DOJw -- erm, really"
1736231,2017-12-04 21:10:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1736236,2017-12-05 16:37:27 UTC,"Eventually, I managed to avoid that by inheriting from osc_lib.command.command.Command instead of ShowOne."
1736240,2018-08-22 10:30:24 UTC,Marking as Won't Fix for apt. Can fix in update-manager and/or install a hook on the live image that prevents upgrades on live sessions.
1736240,2017-12-12 11:42:22 UTC,"Well, it was an update-manager update. I'm not sure why the user triggered one, but probably a high-level graphical tool should not allow that. For APT, it does not make sense to prevent people from upgrading itself. That said, livecd tools could create a pre-install hook that fails with ""This is a live system, it does not support upgrades""?"
1736240,2017-12-12 10:46:03 UTC,"Hm, posibly an apt bug, we should not be upgrading livecd sessions."
1736240,2017-12-12 10:45:28 UTC,"cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file or directory
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1"
1736254,2019-03-05 13:45:52 UTC,Is this still an issue?
1736254,2017-12-06 02:14:15 UTC,"It seems that this issue may go a bit beyond the problem in Bug #1697722. A workaround to Bug #1697722 (https://bugzilla.redhat.com/show_bug.cgi?id=1460460#c9) and the solution in the patch set at https://review.openstack.org/#/c/474196/ is to add ""fqdn_<lowercase_network_name>: {get_attr: [NetHostMap, value, <lowercase_network_name>, fqdn]}"" to the controller-role.yaml in /usr/share/openstack-tripleo-heat-templates/puppet/."
1736272,2017-12-04 22:55:57 UTC,This is all about increasing the signal to noise ratio so that these emails don't simply get ignored.  Notification via email is tricky in and of itself given our time pressures and the amount of spam all of us receive.  If SMEs in the various DFGs stop working on their original jobs to chase one of these issues only to find that it's e.g. a timeout due to a slow node or an infra scheduling problem then they are less likely to come back and do the right thing the next time they get such a notification.
1736277,2017-12-04 23:17:15 UTC,"$ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 1241:1503 Belkin Keyboard
Bus 005 Device 002: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 050d:845a Belkin Components F7D2101 802.11n Surf & Share Wireless Adapter v1000 [Realtek RTL8192SU]
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"
1736277,2017-12-06 22:29:12 UTC,Another screen photo of a similar but more detail back trace when resuming first time this morning from overnight hibernate.
1736277,2017-12-09 06:55:52 UTC,"It is the speed of the memory modules that is causing resume from hibernate problem. I had them clocked at 2.933GHZ (design speed is 3.2GHZ). I put the speed down to 2.8GHZ. Now with two resume from hibernate tests, worked well. First test was just the OS and desktop running. Second test was with the flight sim X-Plane 11 running and using a high amount of memory. It resumed alright but quite slow.
Before clocking down the memory, I had done a memtest on it running for 4 hours +. There were no errors running at 2.933GHZ. I used to notice some small other problems with it at that speed, like on restart, the computer would sometimes pause or partially freeze after closing all the OS down but pausing at the UEFI screen, although the screen stayed black. If I did ctrl alt delete it would power on self test beep then continue to restart properly. Another thing that sometimes happened when the computer was shut down for quite a long time, on start it would nearly reach the UEFI screen then momentarily shutdown about 3 times in a row. Finally on fourth start it succeeded.
So I'm not certain if this might be more of a bug with the UEFI BIOS. Not Mint 18.3."
1736277,2017-12-04 23:15:03 UTC,The kernels I have this bug with are: 4.4.0-53 and 4.11.0-14 also tried with 4.13.0-16 and 4.13.0-17
1736277,2017-12-06 22:16:09 UTC,"Here is a syslog file. On the date of this syslog (Dec 7) I had resumed from hibernate, let the system go to suspend after 1 hour time inactivity, reformatted a backup partition (sda3) from btrfs to ext4, tried another hibernate and resume, no success. It contains some relevant information especially where it reads ""cut here"" in two places."
1736277,2017-12-06 22:23:31 UTC,"In my last comment I should have wrote ""cut here"" in twenty two places."
1736282,2018-01-13 09:30:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736283,2017-12-05 01:21:07 UTC,"To resolve the above 3 issues, I created this pull request based on Ubuntu-azure-edge-4.13.0-1005.5 (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=azure-edge-next&id=ec62f77bbe0697ce128f71fac4fc45c99b6f40d1)."
1736283,2017-12-05 01:25:01 UTC,"BTW, the 19 commits in the pull request is on this branch:
https://github.com/dcui/linux/commits/decui/azure-edge-next-Ubuntu-azure-edge-4.13.0-1005.5-20171204"
1736283,2018-01-09 19:07:33 UTC,This bug was fixed in the package linux-azure - 4.13.0-1005.7
1736283,2017-12-12 15:45:23 UTC,https://lists.ubuntu.com/archives/kernel-team/2017-December/088813.html
1736283,2017-12-06 18:13:32 UTC,"Tested with similar suites, but at different times."
1736283,2017-12-06 17:53:15 UTC,"Oddly enough, @decui in bug 1735546 noted in comment #6 of that bug that they are unable to reproduce this issue with the linux-azure-edge kernel.  This is odd because at this point in time, both the 4.13 based linux-azure and 4.13 based linux-azure-edge should be identical.  We have examined both repos and see no significant different.  The source code is the same, as is the configs and module inclusion lists.  We'll see if we can reproduce."
1736283,2017-12-06 17:21:32 UTC,A test kernel for is available at the following.  Please test and let us know your results.
1736283,2017-12-05 19:23:08 UTC,Thanks for the pull request.  We'll work on getting a test kernel created and post it here when we have it.
1736283,2017-12-05 01:51:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736289,2017-12-05 08:36:41 UTC,Can you post us exact backup command you used along with configuration options (my.cnf) in place to check further. Thanks.
1736289,2017-12-06 07:47:20 UTC,"This is the mysql server configuration file information:
----------------------------------------------------------------------------------------------
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html
# *** DO NOT EDIT THIS FILE. It's a template which will be copied to the
# *** default location during install, and will be replaced if you
# *** upgrade to a newer version of MySQL."
1736289,2018-01-20 07:44:51 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1487
1736294,2017-12-05 07:38:15 UTC,"Also need to ""install -o www-sync -d /var/log/repository-sync"""
1736294,2017-12-05 02:52:54 UTC,Hacky workaround: cd /var/lib/juju/agents/unit-ubuntu-repository-cache-*/charm/lib/; ln -s ../vendor/backoff*/backoff .
1736294,2017-12-05 02:56:06 UTC,"This is actually because 'upgrade-charm' differs from 'install' so the commands to set up backoff aren't run. Arguably, 'upgrade-charm' should really be just 'install'."
1736294,2020-07-09 06:07:01 UTC,"With the reactive rewrite, backoff is now pulled in via wheelhouse"
1736322,2017-12-11 09:48:39 UTC,"Patch to fix this issue:
https://review.openstack.org/#/c/525473"
1736323,2017-12-05 06:30:04 UTC,This change was made by a bot.
1736323,2017-12-05 20:56:45 UTC,You may need to run the following from a terminal:
1736323,2017-12-09 05:56:22 UTC,I ran the commands that were recommended in the email by Joseph Salisbury and my computer still cannot update
1736336,2018-04-20 00:07:48 UTC,"Reviewed:  https://review.openstack.org/562255
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=01a76a09513a1e1c6fa55826be2e7e26ff5f4e82
Submitter: Zuul
Branch:    stable/queens"
1736336,2018-04-18 11:49:51 UTC,"Reviewed:  https://review.openstack.org/529083
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=7c3a9c83da0b673b293131db74f6ca35613a1815
Submitter: Zuul
Branch:    master"
1736336,2018-04-19 14:01:51 UTC,This issue was fixed in the openstack/glance 17.0.0.0b1 development milestone.
1736336,2018-04-10 13:59:24 UTC,Change proposed to master: https://review.openstack.org/#/c/529083/
1736371,2018-01-18 00:40:22 UTC,"Second you here. In most cases, a user has his mobile phone on him. There are also cases when one user has more than one computer and it's quite a hustle to keep all these devices in sync. One of the Apple's advantages is everything is in sync. I can see Ubuntu team bringing Syncthing as a default server/client for syncing its files across multiple devices. Even user-specific config files could be stored for back-up on the mobile phone. And next time, on a fresh install, config files are retrieved from the phone, everything is back the way it was. Really neat and convenient. Syncthing has an android client. I think it is an opportunity Ubuntu should take advantage of."
1736371,2018-01-18 00:30:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736373,2017-12-09 09:20:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526831"
1736373,2017-12-09 03:41:44 UTC,"Update port action, only when the ironic node is active and maintenance is True, we can update the port."
1736373,2017-12-09 15:07:11 UTC,"Greetings, I've added this to the weekly meeting agenda, and it should be discussed in the ironic team meeting on December 11th."
1736373,2020-06-25 07:27:14 UTC,"Change abandoned by Riccardo Pittau (<email address hidden>) on branch: master
Review: https://review.opendev.org/526831
Reason: obsolete"
1736373,2018-02-08 15:33:47 UTC,"Looks like we discussed in ironic team meeting [1], but I honestly don't know what was decided :-("
1736374,2017-12-05 12:26:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1736386,2017-12-21 06:34:24 UTC,"Yes. It looks like there is a race condition somewhere between ""destroying metadata""<->""exposing disk to conductor""->""do partitioning on conductor side"". I added disk-wait after destroying metadata step and it works for me now. Created new issue for ""No partition with UUID...""  https://bugs.launchpad.net/ironic-python-agent/+bug/1739421 because this one is about partx. Thanks!"
1736386,2017-12-20 19:29:11 UTC,"I looked at the logs and I can't help but wonder if what is occuring is the bock device is still locked via the iscsi connection and it has not been fully disengaged and released, which would be required to read the new partition table."
1736386,2017-12-06 11:45:23 UTC,"Proposed fix did not help. Now partx is called 3 times but it keeps returning ""failed to read partition table"" message and the partition is not found. But the conductor detected the partition and then passed it's UUID to ironic-agent a moment ago."
1736386,2017-12-05 12:21:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/525577"
1736395,2019-11-19 20:47:45 UTC,"Reviewed:  https://review.opendev.org/518525
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0e3d395313e15f4e0f8c39244d2292cd87df240d
Submitter: Zuul
Branch:    master"
1736397,2017-12-19 17:50:16 UTC,"Ok, I checked the latest version of opengcs in the NEW queue and it looks much better. The repacking is unfortunate, but I understand the rationale and approve of it (especially that now it's well explained in the README.source file)."
1736397,2018-02-01 09:39:27 UTC,ftbfs on 32bit archs
1736397,2017-12-05 23:55:03 UTC,*** This is an automated message ***
1736397,2017-12-11 08:27:55 UTC,"Hello Balint! I was looking at your package from the NEW POV (as part of training) and I have some questions/potential things that might be good to fix. This is not yet a formal review, I guess someone more experienced might follow up and do a full review."
1736400,2017-12-07 02:12:44 UTC,"I confirmed how does this problem occurs.
Ryu (app/ofctl/api.py) uses the call stack to load the dependent-app('ryu.app.ofctl.service').
When ovs_ryuapp.py be compiled to pyc, the call stack changed and missed the stack of ovs_ryuapp.
So, the dependent-app will not be assigned to ovs_ryuapp, then the ofctl would not be loaded.
This may be the bug of Ryu, and NOT compile the ovs_ryuapp.py to pyc may avoid this problem."
1736400,2017-12-05 12:57:13 UTC,Removing the private setting since this doesn't describe a security bug.
1736412,2017-12-05 13:41:33 UTC,"If these fonts are not installed, xfm crashes on tree view of path /usr/share/doc ."
1736416,2017-12-08 14:52:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736416,2018-08-21 11:25:21 UTC,Possibly a duplicate of bug 1744667.
1736418,2018-01-25 08:40:20 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3763
1736418,2017-12-05 14:38:19 UTC,"here is screenshot with diff over ""strings"" output of percona-release*.rpm"
1736425,2017-12-28 11:02:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736462,2017-12-08 16:35:43 UTC,"Hi Jake,"
1736462,2017-12-08 16:47:29 UTC,"the bug I opened is solved, the new bug is not, have you not seen this
compilation error before?"
1736462,2018-11-18 18:48:55 UTC,"Hi Jake,"
1736462,2017-12-07 20:14:34 UTC,"Hi Arthur,"
1736462,2017-12-07 17:12:30 UTC,"Hi Jake,"
1736499,2018-10-24 14:23:09 UTC,Hi. I got this bug too. How's it going?
1736499,2018-01-19 10:36:47 UTC,"Hi Matt,"
1736509,2018-03-27 14:54:11 UTC,"Hello,"
1736509,2017-12-11 08:22:00 UTC,"Hello François,"
1736509,2017-12-09 17:15:08 UTC,"Sorry for the delay, I haven't had time yet to reproduce your problem in an Ubuntu Xenial virtual machine."
1736510,2018-01-11 19:02:57 UTC,"Thanks for the patch and reporting this bug, Dr. Jens Harbott. It seems like a reasonable patch, however I think we may want to use After=network-online.target"
1736510,2017-12-07 13:12:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736510,2017-12-07 13:55:15 UTC,Proposed patch: https://git.launchpad.net/~j-harbott/ubuntu/+source/neutron/commit/?id=287059e2c3816480d669eabb7b3243c379420aba
1736511,2017-12-18 17:49:35 UTC,"------- Comment From <email address hidden> 2017-12-18 12:47 EDT-------
I agree that it would be nice to have the same behavior as on x86, i.e. try out all potential boot devices until you hit a good one. However, KVM hast to comply with the machine architecture, and for IBM Z that currently means you can specify only one boot device and you have to edit the machine definition after an installation."
1736511,2020-01-23 11:43:07 UTC,The same request by RH would be https://bugzilla.redhat.com/show_bug.cgi?id=1653554
1736511,2020-04-28 09:04:12 UTC,Request for Enhancement / RFE:
1736541,2017-12-06 14:58:40 UTC,"I was looking for documentation of ""refresh"" part and did not find it. Nor did I find a link to where the full set of docs is. So yes, this feels improvable."
1736541,2017-12-06 09:25:10 UTC,"Agreed. However, note the docs talk exclusively about what's under ""result"", not the whole response -- things outside of ""result"" are documented elsewhere. There's a bunch of missing things in the doc, but it's not a completely different beast."
1736556,2017-12-05 18:02:34 UTC,"I didn't notice initially but just did.  The entry in /etc/fstab is bogus, containing a LABEL=METADATA but the disk here is LABEL=config-v2."
1736556,2017-12-05 19:37:42 UTC,Can you attach:
1736556,2017-12-05 19:59:37 UTC,"blkid output was above. and as I said in my first comment the entry in /etc/fstab is wrong.
there is no LABEL=METADATA device.  So 'mount' *should* fail, but I would have expected it to exit non-zero."
1736562,2018-02-22 14:19:26 UTC,"Strange.  There was an IO error trying to update the EFI variables.  I'm not sure if it matters or if it is just odd, but the system tried to install the 32 bit grub even though you appear to have a 64 bit system."
1736562,2018-04-19 06:20:06 UTC,"This has happened to me on two occasions, once on an Apple Macbook 2009 and once on an Intel NUC, both using Mate 18.04 Beta 2."
1736562,2018-04-19 06:15:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736565,2020-05-18 20:15:28 UTC,"We are still seeing this issue in 3.4. On a test server, I was able to download 1000 items, but got an internal server error with 1500 items."
1736565,2018-11-15 19:37:11 UTC,"We are also running a test server on 3.1.7, and a user with 995 items in circ history is able to download successfully. I'm not sure if something has changed, or if the download was successful because our test server isn't busy. Attaching log entries for the successful attempt as well."
1736565,2018-11-15 19:35:51 UTC,"We are still seeing this problem on our production server running Evergreen 3.0.9. As an example, a user with a circ history of 1031 items gets an internal server error. Attaching log entries for that attempt. User id has been replaced with xxxxxxx."
1736565,2018-05-23 20:22:15 UTC,We are seeing this on our 2.12.4 system. This is the error in the gateway.log:
1736565,2017-12-05 18:46:50 UTC,Adding a note that the code from bug 1208875 should already be applied since it was added as a fix for the 2.12.4 release.
1736565,2020-01-14 17:02:50 UTC,We are still seeing this problem on 3.2 - a patron with around 700 items is unable to download.
1736567,2017-12-05 18:56:11 UTC,"Apparently, it didn't like my locate parameters, which were auto-generated at the time of OS installation. It looked like this:"
1736570,2017-12-05 20:22:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1736582,2017-12-06 03:07:23 UTC,I'm getting the same result with Juju 2.3-rc2.
1736582,2018-01-09 05:04:46 UTC,"This turned out to not be that you *can't* bootstrap, but that we don't give good feedback as to what is failing. I don't think it makes sense to prioritize this for 2.3, unless we see more people hitting it."
1736582,2017-12-12 06:39:17 UTC,"The only ports we should need access to on the controller are 17070, 37017
and 22."
1736582,2017-12-11 12:51:05 UTC,"The particular port is 37017 because that is the port we use for Mongo to
communicate with other mongos. However, I wouldn't think that would be
necessary for just bootstrap. Although we might be connecting to the local
mongo via its ""external"" IP address because of differences once you do have
a replicaset. (eg, you could connect to localhost:37017, but as soon as you
have a replica set, you want to actually use 192.168.0.1:37017, so we
default to using 192.168.0.1:37107, and maybe that interacts poorly with
firewalls.)"
1736582,2017-12-06 04:00:14 UTC,I was able to workaround this by opening all ports on the machine. I tried just opening 17070 but that wasn't enough.
1736583,2020-04-07 09:07:05 UTC,Also experienced this bug
1736583,2017-12-06 15:09:43 UTC,"Sorry, that was supposed to be Evince 3.24.0 on Ubuntu 17.04."
1736583,2017-12-05 20:45:37 UTC,This was using Evince 3.24.0 on Ubuntu 17.10.
1736583,2020-08-31 04:17:32 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1736583,2020-07-01 21:11:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1736583"
1736583,2018-01-22 14:50:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736585,2017-12-06 07:21:38 UTC,We are not looking into reports from LeakSanitizer right now.
1736585,2019-09-16 19:10:34 UTC,Migrated to https://github.com/widelands/widelands/issues/3240
1736593,2018-02-20 13:42:29 UTC,"I am glad to report that the problem has been resolved.  The issues I saw with 4.13.0-35.39 during verification appear to be KPTI-related.  After upgrading to 4.13.0-36.40, all is well."
1736593,2017-12-05 22:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1736593,2018-02-14 09:38:19 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1736593,2018-02-14 15:53:12 UTC,Thank you. We will be testing this new kernel at Packet and will report results.
1736593,2018-02-14 17:04:30 UTC,"On Wed, Feb 14, 2018 at 8:53 AM, Edward Vielmetti
<email address hidden> wrote:

> Thank you. We will be testing this new kernel at Packet and will report
> results.
"
1736593,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1736593,2018-02-19 18:14:05 UTC,"Thanks Dann. Scott is testing this and has found an additional issue, but we're not sure yet whether it's directly related or independent. He'll file a more detailed report or open another Launchpad as appropriate."
1736601,2017-12-06 06:41:58 UTC,Latest version: https://git.gnome.org/browse/gparted/log/
1736601,2018-07-16 15:11:37 UTC,The upstream bug report is now on Gitlab.  See:
1736603,2018-09-18 13:26:28 UTC,This was fixed upstream today. Do we want to ask for a Feature Freeze Exception for this port?
1736604,2020-04-29 03:02:57 UTC,This bug was fixed in the package ibus-unikey - 0.7.0~beta1-0.1
1736618,2018-03-01 19:09:50 UTC,This bug was fixed in the package debconf - 1.5.66
1736618,2018-01-07 23:13:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736620,2018-02-02 19:58:18 UTC,"graphviz has been demoted to universe, but I'm still keeping the bug open since eventually, gtk2 will be removed from Ubuntu."
1736621,2019-02-21 20:14:12 UTC,This bug was fixed in the package ubuntukylin-meta - 0.35
1736625,2017-12-06 01:00:07 UTC,This change was made by a bot.
1736629,2017-12-10 07:23:59 UTC,"Each time I attempt to run 'sudo apt --fix-broken install' a new file is listed prior to 'Operation not permitted' eventually my wireless settings were broken, and I was unable to access the internet through eth0 as it disappeared. I ended up booting into a previous kernel 4.13.0-18 and my network configuration allowed internet access.  I'm unable to delete the kernel due to the unmet dependencies, and I'm unable to update other packages due to the unmet dependencies. So I'm not sure where to go from here."
1736629,2017-12-06 01:30:03 UTC,This change was made by a bot.
1736629,2017-12-06 20:47:33 UTC,You may need to run the following from a terminal:
1736629,2017-12-06 21:21:02 UTC,"didn't work.
confirmed"
1736629,2017-12-08 15:25:35 UTC,"This morning, software updater popped up and the red disc was not in the status area. I ran the update which failed again for same reason."
1736629,2017-12-09 22:49:15 UTC,"Just now, I tried synaptic pkg mgr again,broken filter, which still gave the 'no file name' error on linux headers. But it took the ...headers... .19 package of the broken list this time. I was able to reload mark all/unfiltered updates and apply successfully.
Then I ran software updater which asked for a restart, did it, ran updater again--up to date.
Thanks!"
1736631,2018-03-01 10:19:24 UTC,I thought I answered this already: did you try to create an HDP 2.4 cluster using Ambari 2.4.2 or Ambari 2.2.1.0?
1736631,2018-09-24 18:07:26 UTC,Exact same error when creating an HDP 2.5 cluster with Ubuntu/Ambari 2.4.2.0.
1736631,2018-09-24 19:29:54 UTC,"We are not using Launchpad anymore, we moved to storyboard. Please check the updates in the corresponding story:"
1736636,2017-12-20 09:27:59 UTC,"It  gives error when you try to make instance with non bootable volume :
Block Device 44be9b74-eecd-4c57-af70-31079a227bf5 is not bootable. (HTTP 400) (Request-ID: req-3b408624-17ea-446d-9e8f-0112679b6136)."
1736636,2017-12-21 10:14:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529532"
1736636,2018-09-06 07:49:46 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/529532
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1736636,2017-12-06 08:51:27 UTC,"The url of get volume snapshots is true,so change the project to cinder
e.g. http://10.180.207.25/volume/v2/06ceeae716e041e8b3acb53622b350bc/volumes/detail?bootable=1&status=available"
1736650,2017-12-13 17:10:19 UTC,discussed in ML2 meeting today.
1736650,2017-12-07 05:47:18 UTC,"note: midonet and linuxbridge use the same interface naming rules. (TAP_PREFIX + truncated uuid)
it seems nothing prevents an agent to update status of ports which actually belong to another mech driver.
probably we should use agent-id or (host-id, mech) pair to identify port binding."
1736650,2017-12-06 23:55:17 UTC,I've been digging into the code and it works like this.
1736664,2019-09-13 05:46:38 UTC,"yeah, ubuntu-bug would at least upload the ShellJournal file which hopefully contains the JS trace (as we've enabled it by default in ubuntu)"
1736664,2019-06-20 07:01:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736664,2019-09-04 09:53:42 UTC,I don't think we'll be able to close this bug any time soon because any error message logged directly from JavaScript will have the same stack trace.
1736664,2020-01-16 23:18:09 UTC,https://errors.ubuntu.com/oops/89b39b4a-38b3-11ea-b8ae-fa163e102db1 https://errors.ubuntu.com/oops/9d568826-30e1-11ea-a775-fa163ee63de6
1736664,2020-01-16 23:28:14 UTC,"I have created a more specific bug report, for a crash triggered from the file browser in the Discord app, here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664"
1736664,2020-01-17 01:32:13 UTC,"^^^
Looks like a typo. See bug 1860052 instead."
1736665,2020-01-15 19:15:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736665,2017-12-06 21:26:22 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1736665,2020-01-15 19:15:42 UTC,I wonder if https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1859838 would be a duplicate of this.
1736665,2020-01-15 19:59:38 UTC,'d like to first rule out that this is not a duplicate of the following bug:
1736670,2017-12-06 08:00:08 UTC,This change was made by a bot.
1736674,2020-10-26 21:54:16 UTC,"Treating this as a security hardening opportunity, no advisory needed."
1736674,2018-03-19 05:43:10 UTC,This issue was fixed in the openstack/neutron 11.0.3 release.
1736674,2018-03-14 20:04:40 UTC,This issue was fixed in the openstack/neutron 10.0.5 release.
1736674,2018-01-24 23:40:31 UTC,This issue was fixed in the openstack/neutron 12.0.0.0b3 development milestone.
1736674,2018-01-12 09:43:15 UTC,"Reviewed:  https://review.openstack.org/531747
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=df8412b3e834bbe38f32e9748a1f1116e0920e2e
Submitter: Zuul
Branch:    stable/ocata"
1736674,2017-12-06 08:11:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/525934"
1736674,2018-01-08 13:20:12 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/531747"
1736674,2017-12-13 19:23:30 UTC,"Solution here would be to expose iptables_manager from core agent into extensions. We should introduce an ""API"" object for l2 extension manager, like what we have for OVS, and pass it into qos driver where it then would be used."
1736674,2017-12-13 13:56:27 UTC,"So it looks that there is kind of race condition here.
First instance of IptablesManager object is created in iptables_firewall driver and it applies wanted SG rules in filters table.
But than another instance of IptablesManager is created in LB qos driver and when ""delete_dscp_marking"" method is called it tries to remove QoS related rules from iptables. That works fine but as this second instance of IptablesManager don't have any rules in ""filters"" or ""raw"" tables it cleans it in _apply_synchronize method."
1736674,2017-12-12 16:54:37 UTC,This is now called with the patch identified: https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/linuxbridge/agent/extension_drivers/qos_driver.py#L106-L110
1736674,2017-12-10 11:19:12 UTC,"That log message points to https://review.openstack.org/449710 and reverting that patch seems to revert the issue, but I fail to see the error in that patch."
1736674,2017-12-10 07:42:11 UTC,"Seems this is related to qos, see the line here http://logs.openstack.org/34/525934/1/check/neutron-tempest-plugin-scenario-linuxbridge/1ce5729/logs/screen-q-agt.txt.gz#_Dec_06_08_47_50_693519"
1736674,2017-12-14 13:55:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527965"
1736674,2017-12-06 10:29:03 UTC,Logs for create/delete in test patch:
1736674,2017-12-13 20:30:46 UTC,@Ihar: thx for this tip. I was looking at l2 extension api little bit and it looks that it should one quite easy to fix it this way (I hope so). I will soon push a patch to review for that
1736674,2017-12-06 08:27:53 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1736674,2017-12-18 14:18:49 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/527722"
1736674,2017-12-19 09:14:49 UTC,"Change abandoned by Jens Harbott (frickler) (<email address hidden>) on branch: master
Review: https://review.openstack.org/525934
Reason: https://review.openstack.org/527965 seems to be working fine ... modulo gate instabilities"
1736674,2018-01-05 19:20:09 UTC,"Reviewed:  https://review.openstack.org/527965
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cbee0f9f88ff34f70ff19590471b5405e06ff2a9
Submitter: Zuul
Branch:    master"
1736674,2018-01-08 12:38:37 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/531735"
1736674,2018-01-12 08:36:12 UTC,"Reviewed:  https://review.openstack.org/531735
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b0f7be9c7651e9e49f548bb798cf9979b896e691
Submitter: Zuul
Branch:    stable/pike"
1736680,2018-10-05 09:50:21 UTC,I likewise encountered this problem after upgrading from Ubuntu 16.04 to 18.04.  Duplex printing works fine from other applications.  I currently have Firefox 62.0.3 installed.
1736680,2018-08-28 10:19:25 UTC,Duplex printing in Firefox broke after upgrading from 16.04 to 18.04. I did not altered CUPS configuration during this upgrade.
1736680,2018-08-28 10:15:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736680,2018-11-20 20:21:32 UTC,18.10 and still not working
1736683,2017-12-06 13:38:53 UTC,"It happens the same with wired and wireless interfaces, with or without airplane mode on."
1736683,2018-03-09 17:04:22 UTC,This is on gnome:
1736683,2017-12-06 11:59:00 UTC,"Can you please run nutty in debug mode and provide the output here for analysis.
Please run wired and wireless interfaces to see if the wireless one works."
1736683,2017-12-06 13:26:17 UTC,"I've renamed the network interface but it's the same.
Wired interface:
nutty --debug
** (process:4717): DEBUG: nutty.vala:156: Nutty Application running in debug mode - all debug messages will be displayed
[INFO 14:21:13.860417] Application.vala:154: Nutty version: 0.9
[INFO 14:21:13.860444] Application.vala:156: Kernel version: 4.13.0-17-generic
(nutty:4717): Gtk-DEBUG: Connecting to session manager
[WARNING 14:21:13.895490] [GLib] Invalid file descriptor.
[FATAL 14:21:13.896673] [GLib-GObject] g_object_ref: assertion 'G_IS_OBJECT (object)' failed
[FATAL 14:21:13.896695] [Gtk] gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
[WARNING 14:21:13.918509] nutty.vala:1248: Error encountered in execution of sync command [/sbin/ifconfig -a eth0]: eth0: error fetching interface information: Device$
[WARNING 14:21:29.961681] [GLib] Invalid file descriptor."
1736683,2018-02-25 15:26:26 UTC,"Looks like /sbin/ifconfig -a eth0 is not working. Can you provide the output of the following command:
/sbin/ifconfig -a"
1736683,2018-02-26 20:24:36 UTC,Here are 2 new screenshots. There is no such interfaces tab.
1736683,2018-02-26 21:27:08 UTC,Thanks for your patience in debugging this. By Interfaces Tab I actually meant the Info Tab (my bad). Here are some next steps:
1736683,2018-02-27 19:59:57 UTC,I'm running plasma in case it has something to do.
1736683,2018-02-28 12:54:29 UTC,Nutty was developed for Gnome - not sure how it will work for Plasma. Although I thought the difference will only be in the look and feel. But seeing your logs it does not look like it is even printing enough debug - I have added a sample log of opening nutty in debug mode and doing some activities like a few clicks on the Info tab and the Devices tab.
1736683,2018-03-14 21:22:21 UTC,"I see that this bug is pretty common for Gtk apps, but not sure what is causing the same:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1675364"
1736690,2018-06-14 09:01:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736692,2019-11-20 04:17:50 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1736692,2019-08-25 05:38:49 UTC,"I ran into this when rebuilding a controller node, where we have controller001 and controller002 running fine and controller003 is being rebuilt.  All 3 controllers have ceph_mon deployed."
1736692,2019-07-02 11:22:21 UTC,... multinode file for the previous post
1736692,2019-07-01 22:26:34 UTC,"This ""Fetching Ceph Keyrings"" has been a show stopper for us.
We found a singular combination of component versions that finally worked for us but we are now stuck with this ceph problem.
Unlike as many have mentioned in several places, this problem is not necessarily related to a failed deploy.
The problem happens every time we do kolla-ansible stop then deploy."
1736692,2018-09-28 11:35:10 UTC,"destroy currently remove all kolla config files, containers, volumes and images. Are you still having the issue?"
1736696,2018-07-26 08:57:39 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.0 release.
1736696,2018-01-03 16:55:56 UTC,"Reviewed:  https://review.openstack.org/526046
Committed: https://git.openstack.org/cgit/openstack/osc-lib/commit/?id=7ef94d2cf33b0078245c469888cf32f1ac0ef6d1
Submitter: Zuul
Branch:    master"
1736696,2017-12-21 03:52:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529464"
1736699,2020-12-31 14:33:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736701,2017-12-07 10:01:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1736703,2019-08-12 11:29:23 UTC,Works perfectly with Ubuntu 18.04 as well as 19.10 for me.
1736706,2017-12-06 16:06:11 UTC,"Just after this error, there is another error:"
1736706,2017-12-06 16:17:17 UTC,"So there are concurrent operations stepping on each other, an update and a delete:"
1736706,2017-12-07 03:45:05 UTC,I think this is probably due to current issue with the replace workflow in convergence where we don't take any lock when doing prepare_for_replace and probably be fixed by https://review.openstack.org/#/c/516459/.
1736710,2017-12-06 15:20:22 UTC,Update: A manual installation via Juju models succeeds so this seems to be exclusively related to Landscape Autopilot.
1736716,2017-12-06 12:30:17 UTC,Cinnamon 18.2
1736716,2017-12-06 17:30:14 UTC,"Non responsive, I can not close this box."
1736716,2017-12-06 19:11:09 UTC,"Resolved, right clicking on volume icon got rid of, end of, thanks."
1736717,2017-12-18 13:12:16 UTC,"Uploaded python-cliff without python3-unicodecsv depends; I'd rather see the unicodecsv python module dropped in Debian first, so maybe you could raise a bug report there as well?"
1736717,2017-12-18 15:12:32 UTC,This bug was fixed in the package python-cliff - 2.9.1-0ubuntu2
1736719,2017-12-12 13:49:08 UTC,It makes sense to me.
1736721,2017-12-06 17:34:24 UTC,"You need samba 4.7 - it's in bionic(18.04).
Try http://cdimage.ubuntu.com/ubuntu/daily-live/current/"
1736722,2020-09-11 11:03:16 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1736722,2017-12-06 13:18:36 UTC,and the result after move (matching the three points ...
1736723,2018-01-05 18:00:05 UTC,"UPDATE: with recent upgrades the problem mentioned in the Subject of this bug disappeared, i.e. the theme is no longer reset to Ambiance even when the second monitor is initialised in the wrong resolution."
1736723,2017-12-07 15:26:45 UTC,"Could this be related to which monitor was declared by the BIOS to be ""primary""? This guess is based on the fact that it seems to be unpredictable, i.e. sometimes it boots in the correct resolution (and the top panel is correct ""Radiance"") and sometimes in the wrong resolution (and the top panel is reset back to ""Ambiance"")."
1736727,2018-12-05 15:55:25 UTC,"Reviewed:  https://review.openstack.org/554523
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=ff0f33a3fa65e71815f204a9ade3f5532a5ffb7a
Submitter: Zuul
Branch:    stable/ocata"
1736727,2018-01-05 18:35:26 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/531465"
1736727,2017-12-06 14:14:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526079"
1736727,2018-03-20 12:22:31 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/554523"
1736727,2018-01-11 21:37:40 UTC,This issue was fixed in the openstack/os-vif 1.8.0 release.
1736727,2018-08-02 21:46:06 UTC,"Reviewed:  https://review.openstack.org/531465
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=5f7ad5283ce2d1ae99184e06824d6e6f70b83ae9
Submitter: Zuul
Branch:    stable/pike"
1736727,2018-12-10 04:49:22 UTC,This issue was fixed in the openstack/os-vif 1.7.1 release.
1736731,2017-12-15 14:05:40 UTC,"Not sure how we're going to fix that properly, because to use `nova-manage cell_v2 update_cell` we need the cell_uuid, and looks like the only way to get it is to parse the tabular output of `nova-manage cell_v2 list_cells`..."
1736731,2017-12-12 16:20:19 UTC,The fix for this will need to be ported back all the way to Ocata.
1736731,2017-12-12 13:48:17 UTC,"It looks reasonable to me to update if they have the same name by default, but I'd like others to step in too."
1736732,2017-12-06 14:47:04 UTC,"Fix seems to be to remove ""MenuBar=Disabled"" from ~/.config/quasselrc"
1736732,2017-12-06 14:17:12 UTC,"moon127@moon127-UX305CA:~$ dpkg -l | grep quassel
ii  quassel-client                             1:0.12.4-2ubuntu2                                          amd64        distributed IRC client - client component
ii  quassel-data                               1:0.12.4-2ubuntu2                                          all          distributed IRC client - shared data"
1736742,2017-12-08 08:33:01 UTC,This is from log when restarting prometheus-openstack-exporter service
1736752,2017-12-06 15:54:31 UTC,"Currently, the error code returned by the store is 'already_owned'. Matias will split it in a new error code, called 'revoked_name', so we can show different errors for those two conditions in an easier way."
1736752,2017-12-06 15:55:32 UTC,"MP for the new code in the store already proposed:
https://code.launchpad.net/~matiasb/software-center-agent/revoked-name-error-code/+merge/334827"
1736752,2017-12-06 16:23:34 UTC,"TThis is for future work, when we get another review on the store error messages:"
1736752,2017-12-06 15:58:52 UTC,"sergiusens | matiasb elopio nessita we could switch to using the messages from the store, I think register is still based on the old code
sergiusens | we should probably add a task to look at this"
1736762,2017-12-07 15:05:57 UTC,Today another test with a LAN connection between RPi 3B and the router. This time the sound aborts after 33min.
1736765,2018-01-27 13:30:33 UTC,I'm not going to let a postinst script mess with files in a user's home dir.
1736765,2018-07-07 04:09:23 UTC,"Thank you for taking the time to report this bug and helping to make Kubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Kubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Kubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1736765"
1736765,2018-01-27 13:15:53 UTC,"Hi again,"
1736765,2017-12-07 14:18:44 UTC,Same problem here. Clearing the cache solved the problem. It also solved the issue trying to open de settings dialog with the latest latte-dock update.
1736765,2017-12-06 20:43:24 UTC,"Deleting cache actually helped. Latte Dock works again.
It crashed every time right on startup.
Thanks a lot!"
1736765,2017-12-06 19:56:24 UTC,in case this is a cache issue:
1736765,2018-01-28 10:36:20 UTC,"I am not sure this is Latte responsibility, it sounds more as a plasma or qt responsibility to keep the cache consistent... Currently, Latte isnt touching the cache in any way..."
1736765,2018-02-06 09:08:20 UTC,@rikmills a kubuntu user discovered a Latte crash from the master version because we were using PlasmaComponents3.ComboBox in the settings window... This crash is appearing only with kubuntu distro... the infos can be found here: https://github.com/psifidotos/Latte-Dock/issues/855
1736770,2017-12-06 19:19:36 UTC,"Here is syslog from booting using the commands in the bug description:
https://paste.ubuntu.com/26127285/"
1736770,2017-12-06 19:01:33 UTC,"This looks a bit like a hardware (or kernel driver) issue, the problem happens much earlier than where the system appears to stop, you're just getting that because the install fails in general, so it throws you back to the main menu."
1736770,2017-12-06 19:08:55 UTC,"@cyphermox, thanks for looking. I added Linux to get their look at it as it does look like the kernel rev changed between the last successful ISO and the current failing ISO:"
1736770,2017-12-06 19:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1736770,2017-12-11 22:21:54 UTC,There are messages in that syslog pointing to a refusal from busybox tar to unpack some symlinks.  There has been a new merge of busybox from unstable after the datestamps in those logs.  Are the symptoms still the same with the current daily image?
1736770,2017-12-11 22:36:57 UTC,"It looks like the installer is getting further now, however, failing on kernel package install:"
1736770,2017-12-13 18:22:21 UTC,"I take this back, it is still an issue with the amd64 ISO:
https://paste.ubuntu.com/26178135/"
1736773,2017-12-06 21:50:13 UTC,"The *good* news is that external consumers like K8's are using the old API's as well, and there's no facility in gophercloud (yet) to expose the mv to utilize this anyway.  This should not be something that's consumed anywhere yet."
1736773,2017-12-06 18:53:53 UTC,We should probably mark this as a public security issue.
1736773,2017-12-06 19:01:02 UTC,"Since this report concerns a possible security risk (based on IRC discussion in #openstack-cinder), an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1736773,2019-04-01 12:38:41 UTC,Marking the advisory task won't-fix since there were no objections to classifying as B1 (per comment #10).
1736773,2017-12-07 17:58:55 UTC,"I think that's correct. I got to looking at the [cinder] config options for nova and today you can't configure a specific user like you can for some of the other services that nova talks to, like neutron. So even if we added an admin_or_owner by default policy rule to cinder, we'd have to add support to nova for configuring a specific user and backport that as well."
1736773,2017-12-07 17:36:13 UTC,"Given that analysis, it sounds highly likely we can't safely backport fixes to stable branches for such an issue and so would be a class B1 report per our report taxonomy: ""A vulnerability that can only be fixed in master, security note for stable branches, e.g., default config value is insecure"" https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1736773,2017-12-07 17:15:41 UTC,We talked about this at length in the nova/cinder cross-project meeting today:
1736773,2017-12-07 16:14:36 UTC,"One other wrinkle here is there are cases for standalone Cinder where you may want non-admin to be able to get this data.  So, is there a way that this can be set with a policy?"
1736773,2017-12-07 16:12:41 UTC,"(10:07:52 AM) mriedem: looks like this is a policy check on updating an attachment https://github.com/openstack/cinder/blob/master/cinder/volume/api.py#L2075
(10:08:38 AM) mriedem: comparing to os-initialize_connection, there is a policy rule on that too https://github.com/openstack/cinder/blob/master/cinder/volume/api.py#L782
(10:08:52 AM) ildikov: ok, so what does it depend on whether or not to use admin context to get those details?
(10:09:02 AM) mriedem: https://github.com/openstack/cinder/blob/master/cinder/policies/volume_actions.py#L164
(10:09:30 AM) mriedem: same as https://github.com/openstack/cinder/blob/master/cinder/policies/attachments.py#L37
(10:09:44 AM) mriedem: but there isn't a policy rule for listing/showing attachment details
(10:09:52 AM) jungleboyj: Would be good to fix that with a policy setting so if there are people who want that exposed we can still get it.
(10:10:13 AM) ildikov: ah, ok, yeah
(10:10:18 AM) mriedem: ildikov: the issue is that i, as a non-admin user, can create a volume and attach it to an instance,
(10:10:30 AM) mriedem: and then get the details, as a non-admin, about the storage connection
(10:10:40 AM) mriedem: including target IP and credentials
(10:11:01 AM) mriedem: as i said, this has always been a problem with os-initialize_connection as far as i can tell
(10:11:28 AM) mriedem: the main difference is there was never a CLI for initializing a connection to get the connection_info back, but the REST API was always there for anyone that knows how to use curl
(10:11:42 AM) mriedem: there is a CLI for listing and showing volume attachment details"
1736773,2017-12-07 01:39:25 UTC,"@John, I got to thinking about this. How is this any different than the os-initialize_connection volume action API which we are using today (old style attach)? That returns the connection_info document in the REST API response and contains credentials just like we're seeing in the attachment list/get response. Both are scoped to a specific volume, and should be restricted to the owner (or admin) for that volume."
1736773,2017-12-06 19:35:56 UTC,"Note that this API was added in Ocata (Cinder v3.27). Nothing in OpenStack is using this API yet so no attachments would come back outside of testing (nova is working on using this in Queens). However, anything using Cinder standalone (k8s?) could be affected."
1736773,2017-12-06 18:47:51 UTC,Details of the call:
1736774,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1736774,2018-02-14 09:37:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1736774,2018-02-14 19:15:07 UTC,Marking failed due to LP: #1749040
1736774,2018-02-20 11:04:55 UTC,"Hi,"
1736774,2018-02-20 19:25:24 UTC,Verified:
1736785,2017-12-06 19:47:31 UTC,"$ ncal -w -b -3
   November 2017         December 2017          January 2018
Su Mo Tu We Th Fr Sa  Su Mo Tu We Th Fr Sa  Su Mo Tu We Th Fr Sa
          1  2  3  4                  1  2      1  2  3  4  5  6
 5  6  7  8  9 10 11   3  4  5  6  7  8  9   7  8  9 10 11 12 13
12 13 14 15 16 17 18  10 11 12 13 14 15 16  14 15 16 17 18 19 20
19 20 21 22 23 24 25  17 18 19 20 21 22 23  21 22 23 24 25 26 27
26 27 28 29 30        24 25 26 27 28 29 30  28 29 30 31
                      31"
1736794,2018-03-20 05:19:07 UTC,"This is a duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=191601, which also contains a script that might be able to reset your card without a reboot."
1736795,2017-12-06 20:19:23 UTC,"I was following along with the ""Ensure it's working"" steps here:
  https://jujucharms.com/openstack-base/50"
1736795,2017-12-06 20:18:00 UTC,"Following along this guide:
https://jujucharms.com/openstack-base/50"
1736795,2017-12-06 20:18:08 UTC,"Following along this guide:
  https://jujucharms.com/openstack-base/50
I hit errors in the ""Accesing your instance"" section."
1736795,2018-02-07 18:17:15 UTC,https://github.com/openstack-charmers/openstack-bundles/pull/54
1736796,2017-12-06 23:20:19 UTC,UPDATE.  I managed to fix the access to the system settings via $ sudo apt-get install --reinstall unity-control-center
1736796,2018-01-12 22:58:09 UTC,"I've got the same problem here. (Took some time to find out, what the actual button was called.)
Couldn't find any problem solver so far. Do you have any further update on that issue?"
1736798,2018-07-26 14:21:34 UTC,"I am also observing this kind of problem. In my case, the instance died but was removed independently of juju. It seems that it's not possible to remove the model now (I waited for 2 hours before giving up)."
1736798,2017-12-12 12:04:34 UTC,probably high as this affects things like JAAS ending up with lots of models that can't be cleaned up.
1736799,2017-12-15 10:19:56 UTC,So the mismatch between the standard library and the compiler is resolved? I'll check asap
1736799,2017-12-14 20:58:11 UTC,"Ok, I added wildcard support to the exception mechanism in the contamination checker, thanks to ""jelly"" on irc. This made it practical to add exceptions for the files in gcc-arm-none-eabi. The stretch version is now uploaded and should hopefully be included in the next update run. I'm still working on the buster one."
1736799,2017-12-13 22:36:59 UTC,"Thanks, alot. I appreciate you looking into this!"
1736799,2017-12-13 21:36:12 UTC,Well you are the first person i've seen complain about it.
1736799,2017-12-13 19:25:09 UTC,Any updates on this bug? It's really a dealbreaker for many people on Raspbian
1736808,2017-12-06 21:52:03 UTC,The `apport-bug` output had some sensitive information in it so i pruned it a little.
1736808,2017-12-06 21:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1736808,2017-12-08 15:29:59 UTC,"I built a test kernel with a revert of commit 8db6c34f1dbc8. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1736808"
1736808,2018-10-22 16:09:21 UTC,It looks like the bug was fixed upstream here:
1736808,2018-10-22 16:06:02 UTC,"I think I just ran into this bug on bionic. I was building a yocto distribution like this user here:
https://www.spinics.net/lists/linux-unionfs/msg05363.html"
1736808,2018-07-24 09:33:43 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1736808,2017-12-08 18:13:42 UTC,Thanks for looking at this!
1736814,2017-12-07 15:02:38 UTC,"Building the toolchain from source on the raspberry pi zero will probably take multiple days, but i‘ll see what i can do."
1736814,2017-12-07 12:00:38 UTC,"You could try building the toolchain from source. The instruction we provide should work for building on ARM as well. Just make sure to use --skip_steps=mingw32 when invoking install-sources, build-prerequisites and build-toolchain and do not install the mingw related packages."
1736814,2017-12-07 10:14:02 UTC,"Hello,
I am using the raspberry pi zero w with raspbian. For that reason i can not use the Linaro package, which only supports armV7 (atleast i didn’t see anything else).
Thanks"
1736814,2017-12-07 10:07:10 UTC,"Hi Stephan,"
1736814,2017-12-07 09:01:52 UTC,Would Linaro (http://www.linaro.org/downloads/) be an option? arm-linux-gnueabihf may be the one you're looking for.
1736814,2020-02-26 16:53:15 UTC,I have some preliminary binaries for Aarch64 and armhf:
1736832,2019-09-19 14:53:35 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1736864,2017-12-07 06:20:02 UTC,Hi! This looks like a problem on line 244 (my fix for 1720210) which checks enabled_keys is empty or not.
1736864,2017-12-08 04:41:05 UTC,"Also, when tabulating the keys,
wouldn't it be good to show keys that are registered but not on the machine as '(not usable)' on the table? Currently, only the keys on the machine are displayed on the table."
1736864,2017-12-08 05:07:10 UTC,"sangbum: your comments sound correct to me, but I would like to get this triaged by somebody who knows more about keys than me."
1736864,2017-12-08 04:38:41 UTC,"Ah, ignore #1. Maybe the scenario can be classified like this:"
1736874,2017-12-07 06:49:16 UTC,https://review.openstack.org/#/c/525540/
1736874,2017-12-20 02:55:10 UTC,"Change abandoned by wanghongxu (<email address hidden>) on branch: master
Review: https://review.openstack.org/525540"
1736889,2017-12-07 13:39:38 UTC,Please provide output of the command:
1736889,2017-12-07 14:32:51 UTC,"$ inxi -A
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-17-generic"
1736889,2018-07-26 18:08:35 UTC,I can reproduce this in 18.04 amd64.
1736889,2018-07-26 18:09:08 UTC,"...and my inxi -A output:
Audio:     Card-1 Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel
           Card-2 NVIDIA Device 0fbc driver: snd_hda_intel
           Card-3 Midiplus driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.15.0-29-generic"
1736889,2018-10-01 13:44:27 UTC,"I can replicate this too in 18.04.
All updated."
1736889,2019-06-03 23:55:36 UTC,I also find this happening in 18.04.2.  inxi -A output:
1736896,2017-12-07 09:02:51 UTC,"On 12/07/2017 12:43 AM, Fabian Grünbichler wrote:

> Public bug reported:
>
> parser.conf is currently not extensible via a snippet or include
> mechanism (there is an ""Include"" config directive, but it just sets the
> search path(s) for include statements in profiles).
>
> I'd like to introduce such a mechanism (see https://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=883682 for concrete use case, but I think it is a
> good idea in general).
>
> taking a quick look at the existing parser code makes it seem like it
> should not be too hard by reusing process_config_file..
>
> there are two possible semantics:
> - parse snippet/extension config files after main parser.conf is completely parsed
> - parse snippet/extension config files recursively while parsing parser.conf
>
> I'd prefer the former, in any case it should be clearly documented.
>
> if this is something you'd be interested in I'd just spin up an initial
> draft patch, and we could continue from there..
>
"
1736899,2017-12-07 08:52:12 UTC,This problem was not present in 1.3.? version of the program.
1736899,2017-12-17 19:30:22 UTC,It works on my system. What is your Gtk+ version?
1736899,2017-12-17 21:30:58 UTC,"ii  libgtk-3-0:amd 3.18.9-1ubun amd64        GTK+ graphical user interface lib
ii  libgtk2.0-0:am 2.24.30-1ubu amd64        GTK+ graphical user interface lib
ii  libgtk2.0-0:i3 2.24.30-1ubu i386         GTK+ graphical user interface lib"
1736902,2018-10-24 19:02:47 UTC,"@Lance, keystone team is the maintainer of pyCADF"
1736902,2018-01-02 20:07:50 UTC,Thanks for the report. Do you have a link to the exact specification in question?
1736902,2018-01-03 08:27:50 UTC,you'll know the CADF spec: http://www.dmtf.org/sites/default/files/standards/documents/DSP0262_1.0.0.pdf
1736902,2018-01-08 20:20:14 UTC,The report makes sense but I'll wait for a maintainer of the pyCADF project to set the importance.
1736911,2018-02-26 17:56:20 UTC,The complication with a new API is the (significant) work need to teach frameworks like eg. asyn how to handle it.
1736911,2018-02-28 19:27:19 UTC,"@bhill I'm sure you're aware that the pvAccess userTag is current defined as an int32 in pv/timeStamp.h, so you'll also need to propose that it be widened to make it 64-bit (I would support making it unsigned as well if we do decide to change it). This will have knock-on effects and require changes to other modules which may trigger some push-back, so if that's your plan please create an issue (on Github) against both the pvDataCPP and pvDataJava modules to start that discussion."
1736911,2018-02-28 17:56:48 UTC,"> What I like about adding a userTagProvider() API is that it wouldn't affect modules like asyn
"
1736911,2018-02-28 06:33:54 UTC,"I like the idea of having a userTag in pvAccess, the question is how do we make use of it?
Currently, it's up to EPICS engineers to make sure the userTag gets updated when needed.
Even if we make our drivers V4 aware, it only allows setting userTags in those specific V4
objects.   It doesn't allow modules like pvaSrv or pva2pva to set the userTag appropriately
when publishing dbRecord's via pvAccess."
1736911,2018-02-26 17:55:15 UTC,"Well damn, db_access.h could I think be worked through.  However, struct epicsTimeStamp is also used by the channelarchiver file (de)serialization code.  So a change would break archiver file compatibility."
1736911,2018-02-26 17:18:41 UTC,"Modifying epicsTimeStamp would require splitting it into 2 separate definitions or the result would break the CA API and wire protocol. All of the dbr_time_* structures in db_access.h use an epicsTimeStamp, so every existing CA client binary is expecting the current definition and would break if is changed."
1736911,2018-02-24 22:17:53 UTC,My $0.02 is to add a member to struct epicsTimeStamp rather than add a whole new API.
1736912,2018-03-09 17:33:12 UTC,"Reviewed:  https://review.openstack.org/550916
Committed: https://git.openstack.org/cgit/openstack/puppet-keystone/commit/?id=af006954b96ae12951403e8e49b66264929933f4
Submitter: Zuul
Branch:    stable/pike"
1736912,2019-05-16 23:04:49 UTC,This issue was fixed in the openstack/puppet-keystone 11.6.0 release.
1736912,2018-01-25 19:42:54 UTC,This issue was fixed in the openstack/puppet-keystone 12.2.0 release.
1736912,2018-01-02 02:56:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530670"
1736912,2018-03-08 16:57:34 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/550916"
1736912,2018-01-03 22:23:30 UTC,"Reviewed:  https://review.openstack.org/530670
Committed: https://git.openstack.org/cgit/openstack/puppet-keystone/commit/?id=a55b9e4efe956fded7030baddc0f6a342be1d76d
Submitter: Zuul
Branch:    master"
1736915,2019-07-19 20:57:16 UTC,"Hi,"
1736921,2018-01-25 09:00:54 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1827
1736932,2017-12-16 22:32:17 UTC,"I've realized that the problem is that the ""updates available"" count now includes updates that are not automatically selected for installation, whereas before upgrading these updates did not affect the status of the panel icon."
1736939,2018-01-26 17:29:40 UTC,"Neal has pushed an update to 2.30. From what Zyga reported, things looked very good."
1736939,2017-12-22 16:03:32 UTC,"We recently improved the situation. The problem is that classic snaps do not work on distros that do not use the /snap directory. The current snapd (definitely in edge but I think at least candidate as well) will detect this and show instructions what to do:
""""""
fmt.Errorf(i18n.G(""classic confinement requires snaps under /snap or symlink from /snap to %s""), dirs.SnapMountDir)
""""""
Or is there a different classic issue?"
1736939,2017-12-22 16:28:40 UTC,On my fedora system I have /snap symlinked to /var/lib/snapd/snap
1736939,2017-12-22 17:15:49 UTC,"The problem on Fedora needs further investigation. Given how classic snaps are packages, this may easily be a problem with the snap itself."
1736939,2018-01-03 08:17:06 UTC,Maciej just committed a fix for classic confinement on Fedora and similar systems. https://github.com/snapcore/snapd/pull/4432
1736939,2018-01-26 17:12:57 UTC,What's the plan for this fix landing? I'm keen to be able to test this on Fedora 27.
1736939,2018-01-03 08:18:53 UTC,Opened a PR https://github.com/snapcore/snapd/pull/4432 that should address the problem on Fedora and other distributions where snapd libexedir is different from /usr/lib/snapd.
1736939,2018-01-19 18:50:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736939,2020-02-21 11:59:15 UTC,"This is not a snapcraft bug, but a runtime one"
1736939,2019-10-29 21:37:15 UTC,I am marking the snapd task as WONTFIX as we cannot adjust snapd without breaking the format and existing classic snaps. The workaround with the symbolic link is now well-documented but cannot be shipped in the Fedora package for policy reasons. I don't believe there is anything more we can do.
1736939,2018-05-07 06:29:02 UTC,Fedora policy disallows us from adding /snap automatically. Please create the symlink manually.
1736939,2018-05-02 18:40:12 UTC,"error: cannot install ""sublime-text"": ""classic confinement requires snaps under /snap or symlink from /snap to /var/lib/snapd/snap"""
1736939,2018-05-02 18:35:18 UTC,I just installed Fedora 28 and installed snapd and now if I try to install a classic snap I see that error.
1736939,2018-03-27 10:12:33 UTC,This appears to now be fixed! Thanks
1736939,2018-01-19 17:08:48 UTC,"We've tested classic snaps on Ubuntu 14.04, Ubuntu 16.04, Ubuntu 17.10, Ubuntu 18.04 (daily), Debian 9, Solus, elementary, OpenSUSE, Arch Linux, KDE Neon, Atergos, Linux Mint, Manjaro and Fedora 27."
1736940,2019-01-04 07:41:51 UTC,"For the most curious:
https://github.com/sonicnkt/wpkg-gp/issues/2#issuecomment-451371444"
1736940,2019-01-04 06:38:03 UTC,"It would be good to take into account the comments from here:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1697817"
1736940,2019-01-03 10:22:00 UTC,sudo smbstatus -b
1736940,2017-12-17 19:36:01 UTC,"Hi  Andreas,"
1736940,2017-12-17 17:34:41 UTC,"Here I used windows 10 home to access a samba server on ubuntu 16.04. At the moment this snapshot was taken, I had wordpad on windows open a file in the ubuntu share (/home/ubuntu):"
1736940,2017-12-08 09:21:14 UTC,"Hi Gonzalo,
first of all thank you that seems to be an issue and your help to make Ubuntu better is appreciated. We need to sort out if the change is acceptable as an SRU thou."
1736940,2017-12-08 13:16:39 UTC,"Hi Christian,"
1736940,2017-12-11 11:54:17 UTC,Sample output of smbstatus:
1736940,2017-12-13 11:59:50 UTC,Taking a look.
1736940,2017-12-13 12:49:17 UTC,"I can see something similar from an ubuntu artful client if I force protocol SMB3:
andreas@nsnx:~$ smbclient //10.0.100.215/ubuntu -U ubuntu%ubuntu -m SMB3
WARNING: The ""syslog"" option is deprecated
Domain=[XENIAL-SAMBA-SMBSTATUS-1737534] OS=[] Server=[]
smb: \>"
1736940,2017-12-13 15:32:38 UTC,Here is the other script I used during the migration.
1736940,2017-12-13 15:58:47 UTC,"Sorry, I can't debug those scripts. I don't know why all your users show up as nobody/nogroup in smbstatus, maybe you have a force user setting in smb.conf or something like that?"
1736940,2017-12-13 16:31:01 UTC,"Hi Andreas,"
1736940,2017-12-17 20:54:12 UTC,"> I have set up a complete VM with Ubuntu 16 LTS and I can reproduce the issue
> with two newly created users.
"
1736940,2017-12-13 15:31:47 UTC,"Hi Andreas,"
1736940,2017-12-13 17:07:00 UTC,"But you can only reproduce it with windows 10 as the client, right? Not with smbclient and protocol SMB3?"
1736946,2018-01-22 09:44:33 UTC,The bug still occurs when an invalid vnic is returned by neutron. The code from Matt does not address it
1736946,2018-01-12 09:54:40 UTC,"Reviewed:  https://review.openstack.org/529697
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=96acf3db0bc9ecaddb04fc9effc4b9ca1553103d
Submitter: Zuul
Branch:    stable/pike"
1736946,2017-12-19 15:23:30 UTC,Newton is basically end of life at this point (we were actually supposed to do that in October I think).
1736946,2017-12-19 09:40:24 UTC,"Change abandoned by garyk (<email address hidden>) on branch: master
Review: https://review.openstack.org/526356
Reason: https://review.openstack.org/#/c/528835/"
1736946,2017-12-19 01:55:02 UTC,This was regressed in newton: https://review.openstack.org/#/c/364005/
1736946,2017-12-19 00:58:29 UTC,This should be fixed by https://review.openstack.org/#/c/528835/.
1736946,2017-12-07 12:33:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526356"
1736946,2017-12-22 13:33:19 UTC,"Reviewed:  https://review.openstack.org/528835
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f8747407fc6ac0dd2669065a79094dd2c284a4b2
Submitter: Zuul
Branch:    master"
1736946,2017-12-21 20:59:21 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/529697"
1736946,2017-12-21 21:15:08 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/529703"
1736946,2018-05-02 12:04:37 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1736946,2018-03-23 02:12:33 UTC,"Reviewed:  https://review.openstack.org/529703
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f70119c842958e730d64db44d6684c1501ea3049
Submitter: Zuul
Branch:    stable/ocata"
1736946,2018-02-15 23:53:42 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1736946,2018-01-26 00:43:41 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1736947,2018-03-12 10:51:08 UTC,"rdma-core is on 17.0-1 in latest Debian and Ubuntu Bionic 18.04.
This includes there fix as also outlined by bdrung."
1736947,2018-01-29 12:03:08 UTC,"what is ""16.0 release"" ?
you mean something like Ubuntu 16.04 or 16.10 ?"
1736947,2018-01-29 09:37:20 UTC,The patch mentioned in https://www.spinics.net/lists/linux-rdma/msg57490.html is part of the 16.0 release.
1736947,2017-12-26 10:18:34 UTC,could this be related ?
1736947,2017-12-07 13:58:27 UTC,"For several reasons I had to scrap the machine and rebuild with different hardware, I couldn't afford such long boot time, so I can't run the apport-collect command."
1736947,2017-12-07 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1736947,2018-03-08 09:01:26 UTC,To clarify: The patch mentioned in https://www.spinics.net/lists/linux-rdma/msg57490.html is part of the rdma-core 16.0 release. Therefore this fix will be included in Ubuntu 18.04 (bionic).
1736952,2017-12-07 13:33:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/526382"
1736952,2017-12-07 17:51:39 UTC,"Reviewed:  https://review.openstack.org/526382
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=a77ba0de6a5ab51e1c1b06967242804017f202fe
Submitter: Zuul
Branch:    master"
1736952,2017-12-07 13:31:03 UTC,"Set to Low, since this test:
1. Doesn't look like it's testing anything Dragonflow specific
2. Issue probably originates in Neutron, or is incorrect API invocation. ( https://review.openstack.org/#/c/526362/ )"
1736953,2017-12-08 01:46:22 UTC,I believe the issue is related to masked objects not appearing in PDF.
1736953,2017-12-07 16:41:00 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1736956,2018-09-06 07:43:22 UTC,"This option could be done even without the need to add a field to footprint format.
I wrote a suggestion here:
https://bugs.launchpad.net/kicad/+bug/1766323
This could be done in a non modal dialog callable from the 3D viewer menu, to let directly user interaction and 3d view update…
The list of 3d models visibility/transparency could be saved in a preference file in the project folder or just dropped when the file is closed, to avoid extra settings.
That would help in better check enclosure requirements, particularly for mechanical purposes."
1736956,2017-12-11 15:08:12 UTC,Even add this ability to full opacity in the board 3D viewer to highlight PADs and others details that the user may to check.
1736956,2017-12-12 10:15:09 UTC,What do you mean in #2? You can hide the board body.
1736956,2018-01-06 20:27:33 UTC,Why do you not make mymodel.wrl transparent? I just made a component in Freecad that has some faces transparent.
1736956,2018-08-02 15:13:44 UTC,"I believe the reason not to make the model transparent would be if you dont always want it transparent.
fx a box around your PCB would be nice to adjust anywhere from gone to semitransparent to fully visible"
1736956,2019-11-12 16:19:13 UTC,I agree this would be very useful indeed for testing fit of PCB (and mounted parts) inside an enclosure.
1736957,2017-12-27 17:03:19 UTC,It is also happening in OpenSUSE Tumbleweed
1736957,2017-12-09 03:13:51 UTC,This should be fixed in breezy.
1736959,2017-12-09 14:01:58 UTC,"Hi please add a bit more information.
What is the exact ISO you are using, we have a few available.
Please provide the link to the one you downloaded."
1736959,2017-12-19 22:03:57 UTC,"Hi,
I do hope these fixes make it more clear.  I agree about the whole Red Hat Debian thing, I experienced the same change.  Debian was much more inviting and easier to install/use, but Ubuntu changed everything... it became the easiest OS to install of any."
1736959,2017-12-19 17:56:43 UTC,"Hi Israel,"
1736959,2017-12-18 13:29:45 UTC,These are the OBI specific issues ONLY:
1736959,2017-12-14 13:24:00 UTC,turned out to be ToriOS1.0 not booting correct somehow causing all kinds of odd issues
1736959,2017-12-14 03:00:38 UTC,"Hi Israel,"
1736959,2017-12-19 22:10:37 UTC,"I just tried adding a panel to the bottom and it worked fine.
It may be simply that that older ISO is a bit messed up.  I did it from a fresh install from a very recent ISO I built (earlier this morning).
So I do not think that this issue is an issue anymore.  Can you post the output of
apt show jwm-settings-manager"
1736959,2017-12-11 17:15:33 UTC,"I have tested the gparted/obi feature in the ToriOS Debian Jessie 1.5 ISO.  So I cannot fix this unless you provide me more information, as it appears to fully work"
1736965,2018-12-04 15:56:39 UTC,Resetting the tags to verification-done as per the discussion in https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
1736965,2018-12-05 18:47:48 UTC,This bug was fixed in the package netplan.io - 0.40.1~18.04.3
1736965,2018-11-26 19:23:24 UTC,"Hello Colin, or anyone else affected,"
1736965,2018-11-06 18:13:46 UTC,This bug was fixed in the package netplan.io - 0.40.1~18.04.2
1736965,2018-10-09 17:22:00 UTC,Verification-done with netplan.io 0.40.1~18.04.1 on bionic:
1736965,2018-10-04 18:24:44 UTC,"Hello Colin, or anyone else affected,"
1736965,2018-09-28 16:33:35 UTC,"Hello Colin, or anyone else affected,"
1736965,2018-09-18 23:13:39 UTC,This bug was fixed in the package netplan.io - 0.40
1736965,2018-07-20 06:07:13 UTC,"Hi,"
1736965,2018-11-06 18:14:43 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1736965,2018-06-12 15:27:44 UTC,umask 027 is (obviously) sufficient to lead to the issue.
1736965,2018-05-11 14:15:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1736965,2018-10-23 21:59:45 UTC,"Hello Colin, or anyone else affected,"
1736965,2018-10-29 20:57:15 UTC,Verification-done on bionic using netplan.io 0.40.1~18.04.2:
1736967,2019-05-29 14:58:41 UTC,"Pushed to master, along with a follow-up that adds release notes. Thanks, Sam and Rogan!"
1736967,2019-05-23 20:10:23 UTC,sign off pushed to user/rogan/lp1736967_signoff
1736967,2019-01-02 19:17:23 UTC,Fix based on Roger's idea pushed here:
1736973,2017-12-07 16:28:24 UTC,"So I uninstalled Inkscape and reinstalled it.  I loaded a font.  It is not showing the font correctly on the screen!!!  It is still showing the old font (that had the same name) on the screen when I type, but the correct font when I click on the ""Text & Font"" option!!"
1736973,2017-12-08 01:22:13 UTC,This is mostly a windows issue... deleted fonts aren't really deleted. There are zombie copies of the font still hidden in the directory.
1736973,2017-12-08 02:04:07 UTC,(cross linking to question asked by same user: https://answers.launchpad.net/inkscape/+question/661481)
1736973,2019-06-21 12:52:25 UTC,Closing in favour of more comprehensive report in bug 1773601.
1736973,2018-03-28 21:34:46 UTC,"Deleting
  %localappdata%\fontconfig\cache
has no effect whatsoever."
1736973,2017-12-13 01:30:23 UTC,"FWIW I'm not able to reproduce this issue (Windows 10 x64). If I delete a font from ""C:\Windows\Fonts"" it's typically gone. Only exception were some font's with non-ASCII characters in file name I experimented with some time ago."
1736985,2018-10-26 19:39:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613675"
1736985,2018-11-07 10:09:48 UTC,"Reviewed:  https://review.openstack.org/613651
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=7e1b53625990bb08425645cb92f36e16bd67db7f
Submitter: Zuul
Branch:    master"
1736985,2019-06-21 21:32:04 UTC,"Reviewed:  https://review.opendev.org/613675
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=b3e84aafc0302b1a87754f438696794076ba844f
Submitter: Zuul
Branch:    master"
1736985,2017-12-07 16:27:03 UTC,will have to fix devstack's https://bugs.launchpad.net/devstack/+bug/1736988 first so as not to break the gate.
1736985,2018-10-26 17:34:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613651"
1736988,2017-12-22 20:56:24 UTC,"@Andrea It's because DevStack is using deprecated keystonemiddleware options. DevStack needs to stop using those options before keystonemiddleware can remove them (which has a separate defect, as linked in the description)."
1736988,2018-01-08 20:21:04 UTC,"Either way - it's possible to clean those up, too."
1736988,2018-01-03 15:07:46 UTC,"oh, then I probably just scanned too quickly and missed that. So it must be something else using the old property/-ies that we still need to track down."
1736988,2018-01-02 20:41:22 UTC,"The link to lib/cinder in devstack is using inicomment, which appears to just comment out lines in ini files. If that is the case, couldn't we just remove those line?"
1736988,2017-12-21 09:15:18 UTC,"It's not clear to me why this was filed as devstack? The link provided points to keystonemiddleware unit tests, so those options need to be removed from there."
1736988,2018-03-19 13:54:34 UTC,I'm not seeing those deprecation warnings in more recent results: http://logs.openstack.org/95/551495/4/check/openstack-tox-py27/80fa734/job-output.txt.gz
1736991,2020-12-15 19:40:27 UTC,Tested this on the 3.6 system and the behavior still exists. Marking Confirmed.
1736995,2017-12-15 20:44:20 UTC,Thanks Kenn.
1736995,2017-12-15 00:18:50 UTC,"Verfied this with
(1) PXC 5.7.20 (not released yet) standalone (wsrep disabled) as async master
(2) A 2-node PXC 5.7.20 cluster (Nodes N!, N2) with N! as async slave"
1736995,2017-12-15 00:58:13 UTC,Also verified on 5.6.37
1736995,2017-12-15 03:00:21 UTC,"Note: Re-reading the bug, I believe the behavior should end up as:
'dave' appears on async master
'dave' is not on N1
'dave' is not on N2 <-- change from current behavior"
1736995,2018-01-18 08:26:00 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-904
1737002,2019-12-18 08:44:43 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1737005,2018-01-04 03:12:04 UTC,"Behavior was explained and confirmed by comment #2. Proposed kernel parameter works for me. Adding logs seems not helpfull to me, confirming anyway."
1737005,2017-12-07 18:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1737005,2017-12-07 19:20:47 UTC,The Ubuntu mainline kernel build unfortunately currently does not have apparmor set as the default LSM. This is due to some config changes done when adding the LSM stacking patches (Ubuntu tries to keep the configs as close as possible). Addressing this is wip and should land with the next revision of the LSM stacking patches
1737005,2018-01-04 09:38:02 UTC,"Klaus,"
1737006,2017-12-07 19:04:40 UTC,"NVM this was actually my bad, I had the default browser as konqueror (which isnt compatible). Switched it to Firefox and it works just fine"
1737006,2017-12-09 09:58:15 UTC,Hello and thank you for sending your problem.
1737013,2017-12-12 13:46:24 UTC,"Both make sense. There was also the idea of wiring with group vars, but if it's possible to avoid a group var for that, that's even better."
1737013,2017-12-12 13:46:54 UTC,(Or at least I am suprised everyone is using cinder-backup as user)
1737022,2018-01-04 12:27:02 UTC,"Marking this as 'wishlist'; we have a similar 'expert use only' feature in other charms as these type of things allow users to shoot themselves in the foot quite spectacularly.  I'd rather see proposal for features which can be expressed as specific configuration options or just good, sane best practices!"
1737022,2017-12-07 19:42:28 UTC,"As a workaround, I forked this charm and added the following to get the custom-config:"
1737022,2017-12-08 23:14:51 UTC,"Wouldn't it be easier/cleaner to just create a new file and put it in /etc/mysql/conf.d/ directory, if extra configuration (outside of scope of the charm) is needed?"
1737022,2018-01-07 22:08:37 UTC,"Change abandoned by james beedy (<email address hidden>) on branch: master
Review: https://review.openstack.org/526493
Reason: per comments, there is a better way for this configuration to be accomplished."
1737033,2017-12-07 21:21:41 UTC,apport information
1737033,2017-12-12 23:24:00 UTC,I noticed that kernel 4.4.0-104 is in proposed while poking around for something else. I've installed it on my virtualbox test mule and it's working. I can mount Ceph without any issues.
1737033,2017-12-12 23:54:59 UTC,"After briefly testing to make sure things looked sane, I pushed the update out via our internal repo. No problems so far, but I'll post here if anything comes up."
1737033,2017-12-13 09:54:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1737033,2017-12-13 09:59:10 UTC,"Please note that we are re-spinning Xenial kernels to release a fix for this issue faster, so the dates from comment #25 don't apply for this bug."
1737033,2017-12-07 21:21:39 UTC,apport information
1737033,2017-12-13 15:43:09 UTC,Thanks @davecore and @benjamin-long for verifying the fix!
1737033,2017-12-07 21:21:40 UTC,apport information
1737033,2017-12-12 07:23:55 UTC,"Hi Benjamin,"
1737033,2017-12-07 21:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1737033,2017-12-13 15:39:18 UTC,I also confirm the kernel 4.4.0-104.127 in xenial-proposed fixes the issue. I am able to mount my CephFS filesystem normally. Benjamin also confirmed the kernel works for him in comments #26 and #27. I am changing the tag to verification-done-xenial. Thanks!
1737033,2017-12-11 14:41:50 UTC,"As soon as the package hits proposed, I'll test it. Will this bug be updated when it's ready?"
1737033,2017-12-14 17:13:11 UTC,This bug was fixed in the package linux - 4.4.0-104.127
1737033,2017-12-08 17:08:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737033,2017-12-08 20:35:52 UTC,I tested a kernel without the following commits from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728739 and I was able to mount the CephFS filesystem successfully:
1737033,2017-12-07 21:24:15 UTC,"Please note that while the apport report is from a virtualbox VM, this is happening across my entire network. All my workstation are having the same issue, and all are 'fixed' by booting with the previous kernel."
1737033,2017-12-07 21:21:51 UTC,apport information
1737033,2017-12-07 21:21:49 UTC,apport information
1737033,2017-12-07 21:21:48 UTC,apport information
1737033,2017-12-07 21:21:47 UTC,apport information
1737033,2017-12-07 21:21:45 UTC,apport information
1737033,2017-12-07 21:21:44 UTC,apport information
1737033,2017-12-07 21:21:43 UTC,apport information
1737033,2017-12-08 02:15:20 UTC,4.4.0-101 is the one they upgraded from. I'm not seeing 4.4.0.102 anywhere. It's not in the available package list of the machine I'm in front of right now.
1737033,2017-12-08 02:29:23 UTC,"Good to know, thanks!
We do have some ceph related change from 4.4.0-101 to 4.4.0-103
https://launchpad.net/ubuntu/+source/linux/4.4.0-103.126"
1737033,2017-12-08 14:38:04 UTC,"On the running system after you rollback to the previous kernel, can you paste your /etc/fstab for the filesystems that failed to mount and the corresponding lines from mount -v? I assume the issues are with nfshome and officeshare:"
1737033,2017-12-08 14:50:27 UTC,"I built a test kernel with a revert of commit ff467fd.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1737033"
1737033,2017-12-08 16:18:25 UTC,"Hi Joseph,"
1737033,2017-12-08 16:22:59 UTC,I forgot to mention that I was still able to reproduce the bug with the kernel you built with a revert of commit ff467fd from http://kernel.ubuntu.com/~jsalisbury/lp1737033
1737033,2017-12-08 16:58:35 UTC,"David,"
1737033,2017-12-08 02:02:48 UTC,"Hello,
for the ""previous kernel"", do you mean 4.4.0-102 or 4.4.0-101?
Thanks"
1737039,2019-11-01 12:51:42 UTC,"Seems this goes back to https://bugs.launchpad.net/cirros/+bug/1312199 , I'll ping smoser."
1737046,2018-02-06 06:16:19 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=104960
1737046,2017-12-10 10:21:11 UTC,"Reuben Lifshay, to clarify, what happens when you switch from libinput to evdev in the daily image?"
1737046,2017-12-14 02:53:27 UTC,I tested with evdev with the same daily image and it doesn't work there either.
1737046,2017-12-10 07:33:31 UTC,It appears as if the daily image was using libinput.
1737046,2017-12-09 14:34:54 UTC,"Reuben Lifshay, one may test libinput by unintalling xserver-xorg-input-evdev, and installing xserver-xorg-input-evdev and installing xserver-xorg-input-libinput."
1737046,2017-12-09 08:50:18 UTC,"That, I am not sure on. I didn't change anything, so I was using whatever the default is on the daily ISO. I'll look into that when I get a chance and see what I was using and if the other changes anything."
1737046,2017-12-09 05:07:37 UTC,"Reuben Lifshay, to clarify, have you tested libinput as an alternative to evdev, or was libinput tested when using the daily ISO?"
1737046,2017-12-08 23:28:46 UTC,The mouse is a Razer Naga Chroma. Here is the relevant section from usb-devices:
1737046,2017-12-08 04:47:39 UTC,"Reuben Lifshay:
1) Regarding the mouse you acquired recently with a tilt wheel, could you please:
 1a. Advise to the full manufacturer, and model?
 1b. Plug it in, and post the results uncompressed when executing via a terminal:
usb-devices
2) Could you please provide the xev log you produced as per the Bug Description?"
1737046,2017-12-08 01:28:06 UTC,"I vaguely recall it working a long time ago, but I have not used a mouse with a tilt wheel in a long time and only just recently acquired another mouse with a tilt wheel. I just tested with 14.04 though and it is broken there in addition to 16.04."
1737046,2017-12-08 00:42:18 UTC,"Reuben Lifshay, thank you for reporting this and helping make Ubuntu better."
1737046,2018-01-28 17:23:44 UTC,"Reuben Lifshay, this problem should be reported upstream. Could you please post this to:
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg
Component: Input/libinput
Version: 7.7"
1737060,2017-12-08 00:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1737060,2017-12-08 14:05:22 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1737060,2017-12-08 21:27:11 UTC,kernel-fixed-upstream
1737083,2018-01-07 16:07:32 UTC,"PS: something is strange here, I just removed the _usr_bin_epiphany.1000.crash from the /var/crash directory, and now the ""Web"" launcher from the lxpanel menu works."
1737083,2017-12-15 04:27:13 UTC,"FYI, the attached is `/var/crash/_usr_bin_epiphany.1000.crash`."
1737083,2018-01-07 15:49:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737083,2017-12-08 03:39:55 UTC,apport information
1737083,2017-12-08 03:39:58 UTC,apport information
1737083,2017-12-08 16:19:10 UTC,I don't understand what could be wrong here. epiphany-browser depends on epiphany-browser-data which includes the org.gnome.Epiphany.lockdown gsettings schemas.
1737083,2017-12-08 17:10:41 UTC,"could you add the output of
""$ cat /proc/`pidof epiphany-browser`/maps""
to the bug"
1737083,2017-12-08 20:26:50 UTC,"in fact since the binary doesn't start that's not going to work, could you start gedit and does that on it for example?"
1737083,2017-12-08 03:39:52 UTC,apport information
1737083,2017-12-08 03:15:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1737083"
1737083,2017-12-14 03:21:49 UTC,Sorry to respond so late. What file do want me to open and get its content?
1737083,2018-01-07 15:59:32 UTC,"Hi,"
1737083,2017-12-08 03:39:54 UTC,apport information
1737087,2017-12-08 23:14:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737100,2017-12-08 06:02:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526599"
1737113,2020-05-07 07:50:42 UTC,"The original PR is here:
https://github.com/mixxxdj/mixxx/pull/2750
the backport is here:
https://github.com/mixxxdj/mixxx/pull/2759"
1737113,2020-04-09 20:30:07 UTC,That is confusing. I think it would make sense to invert one of them.
1737113,2020-04-09 20:12:08 UTC,"I poked around a bit in the enginetalkover code, just to find out that the Strength knob works exactly the opposite in AUTO mode than it does in MANUAL mode:
MANUAL strength=0 > max music ducking, strength=1 > no ducking
AUTO strength=0 > no ducking, strength=1 > max ducking"
1737113,2017-12-20 13:35:28 UTC,"Manual ducking lowers the volume of everything but the mics by the amount determined by the ducking Strength knob. If you want to adjust how much the music is reduced in volume, turn the Strength knob."
1737113,2017-12-14 18:06:39 UTC,Thanks for reporting this bug.
1737113,2020-05-07 07:48:41 UTC,I think we should backport your fix to 2.2 as well.
1737135,2017-12-18 09:34:09 UTC,provide this crash log for d05 board
1737135,2017-12-10 20:05:21 UTC,"The lack of an informative error there is clearly a bug. Can you try again, switch to vt2 and look at /var/log/installer/subiquity-debug.log?"
1737135,2018-02-13 06:05:09 UTC,       An error occurred during installation
1737135,2018-02-13 16:26:31 UTC,"Canonical does not plan to support the live server installer for arm64 servers in 18.04. The builds are out there for testing, but not planned for release."
1737140,2019-05-10 08:37:28 UTC,"Closing as there has been no response for 30 days. If this is still an issue with the latest Inkscape version, please file a new report here with details: https://inkscape.org/report. Thank you!"
1737140,2017-12-13 00:42:41 UTC,Do you happen to have multiple keyboard layouts set-up on your system?
1737153,2017-12-08 12:38:36 UTC,"The minified version is to be considered as a .o file, ie the result of a compilation. Therefore it as nothing to do in a source tree."
1737153,2017-12-10 05:13:12 UTC,"Looking at https://wiki.debian.org/Javascript/Policy I see a ""could""."
1737153,2017-12-08 12:11:43 UTC,We include both minified and non-minified for this specific reason.
1737154,2017-12-08 12:07:30 UTC,Thanks for reporting this. Please use an older version of RedNotebook for the time being.
1737155,2017-12-13 15:11:03 UTC,"Now I've been watching more carefully, this does not just apply to the file chooser window and the system monitor. It applies to many (all?) dialogue windows with a multi-column internal layout, e.g. print."
1737155,2017-12-08 12:08:00 UTC,"Thinking back, the event that possibly made this bug disappear could have been...:"
1737168,2018-01-22 18:23:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737170,2018-04-10 07:45:23 UTC,"In bug 1761405 there's a workaround to avoid notifications being sent in the first place. Would be trivial-ish to add as a config option, at least in the 18.02 charms."
1737170,2018-07-18 14:13:38 UTC,https://review.openstack.org/#/c/583580
1737170,2018-09-19 10:04:45 UTC,"This bug is also affecting the event.sample, alarm.all.sample and metering.sample queues."
1737170,2019-01-09 12:14:03 UTC,"Reviewed:  https://review.openstack.org/583580
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=77b6175c1cfccd5cb78ef2de14bf70c4283b5cbc
Submitter: Zuul
Branch:    master"
1737170,2018-04-05 08:16:29 UTC,Filed bug 1761405 upstream.
1737170,2018-04-04 14:31:04 UTC,"I think it's a reasonable feature request of the rmq charm, to allow users to use charm config and/or charm actions to manage operations of queues, including TTLs and purges."
1737170,2018-01-04 12:02:33 UTC,I think setting the TTL policy is an OK workaround; note that this type of reconfiguration in the event that ceilometer is or is not deployed would be covered by the service discovery spec (which although specified remains unimplemented to date).
1737170,2018-04-06 06:10:38 UTC,"Note that if you want the TTL to apply to versioned notifications as well (in the workaround in the OP), you should use ""^(versioned_)?notifications.*"" as regexp."
1737174,2017-12-08 13:37:09 UTC,"I suspect that during any stack-update where docker-puppet.py reruns for rabbitmq we are running ""rabbitmqctl -q list_users"", the problem is just usually not seen since rabbitmq had been previously started."
1737174,2017-12-08 13:37:54 UTC,"We noop'd the rabbitmq_user resource in https://review.openstack.org/#/c/524751/, but apparently that is not working for some reason."
1737174,2021-02-19 15:51:39 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1737187,2019-07-30 08:16:28 UTC,Do you still experiencing this issue?
1737187,2018-02-20 13:30:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737187,2019-02-08 05:38:59 UTC,Is this still considered an issue?
1737187,2019-07-30 09:41:19 UTC,"Hi,"
1737187,2019-07-30 17:15:44 UTC,"No, I believe it's resolved."
1737187,2019-09-29 04:17:50 UTC,[Expired for linux-aws (Ubuntu) because there has been no activity for 60 days.]
1737191,2018-01-30 01:01:37 UTC,This issue was fixed in the openstack/os-net-config 8.2.0 release.
1737194,2018-01-25 16:16:24 UTC,"On 25 January 2018 at 15:58, John Arbuckle <email address hidden> wrote:

> I did try to build at commits 306ec6c3cece7004429c79c1ac93d49919f1f1cc
> and e689f7c668cbd9d08f330e17c3dd3a059c9553d3. Both failed to build on my
> Mac OS X system. Here is the error message I usually saw:
>
>   LINK  qemu-io
> Undefined symbols for architecture x86_64:
>   ""_use_rt_clock"", referenced from:
>       _bdrv_acct_start in block.o
>       _bdrv_acct_done in block.o
> Undefined symbols for architecture x86_64:
>       _qemu_clock_get_ns in qemu-timer.o
>   ""_use_rt_clock"", referenced from:
>       _bdrv_acct_start in block.o
>       _bdrv_acct_done in block.o
>       _qemu_clock_get_ns in qemu-timer.o
"
1737194,2017-12-08 18:41:59 UTC,"If you do two identical installs with qcow2 and raw, do you see any differences with qemu-img compare afterwards that might indicate what could possibly have gone wrong?"
1737194,2017-12-08 20:21:55 UTC,"> On Dec 8, 2017, at 1:41 PM, John Snow <email address hidden> wrote:
>
> If you do two identical installs with qcow2 and raw, do you see any
> differences with qemu-img compare afterwards that might indicate what
> could possibly have gone wrong?
"
1737194,2018-01-25 07:53:41 UTC,"Hi,"
1737194,2021-01-16 04:17:51 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1737194,2020-11-16 18:13:14 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1737194,2018-01-27 00:39:08 UTC,I have installed Windows 95 OSR 2.5 in QEMU using the qcow2 format. So far there hasn't been any major problems that prevent Windows from booting.
1737194,2018-01-26 17:03:35 UTC,"> On Jan 26, 2018, at 9:51 AM, David Lindsay <email address hidden> wrote:
>
> Hi John & others:
>
> (3 separate things.)
>
> 1: Image formats
>
> Regarding qcow, unfortunately there is no change if I use this format.
>
> - Windows 3.1 initially hung at ""Starting MS-DOS...""; upon restart it
> crashed when it decided it couldn't find COMMAND.COM (a frequent failure
> mode I forgot to mention).
"
1737194,2018-01-26 14:51:34 UTC,Hi John & others:
1737194,2018-01-25 17:07:53 UTC,"On 25 January 2018 at 16:43, John Arbuckle <email address hidden> wrote:

>> On Jan 25, 2018, at 11:16 AM, Peter Maydell <email address hidden> wrote:
>> If you configure with --disable-tools does it manage to build,
>> or does it just go on to fail to link the main QEMU binary
>> with the same error?
"
1737194,2018-01-25 16:43:41 UTC,"> On Jan 25, 2018, at 11:16 AM, Peter Maydell <email address hidden> wrote:
>
> On 25 January 2018 at 15:58, John Arbuckle <email address hidden> wrote:
>> I did try to build at commits 306ec6c3cece7004429c79c1ac93d49919f1f1cc
>> and e689f7c668cbd9d08f330e17c3dd3a059c9553d3. Both failed to build on my
>> Mac OS X system. Here is the error message I usually saw:
>>
>>  LINK  qemu-io
>> Undefined symbols for architecture x86_64:
>>  ""_use_rt_clock"", referenced from:
>>      _bdrv_acct_start in block.o
>>      _bdrv_acct_done in block.o
>> Undefined symbols for architecture x86_64:
>>      _qemu_clock_get_ns in qemu-timer.o
>>  ""_use_rt_clock"", referenced from:
>>      _bdrv_acct_start in block.o
>>      _bdrv_acct_done in block.o
>>      _qemu_clock_get_ns in qemu-timer.o
>
> If you configure with --disable-tools does it manage to build,
> or does it just go on to fail to link the main QEMU binary
> with the same error? (We've had some issues in the past I think
> where configure put libraries on the main binary link line but
> not on the tools link lines, so maybe worth a try...)
>
> thanks
> -- PMM
>
"
1737194,2018-01-25 16:37:14 UTC,"> # WinNT 4 Terminal Server
>
> Most of the time, NTLDR will fire up normally. But every so often...
>
>   SeaBIOS (version rel-1.7.3-117-g31b8b4e-20131206_080705-nilsson.home.kraxel.org)
>
>   Booting from Hard Disk...
>   A disk read error occurred.
>   Insert a system diskette and restart
>   the system.
>
> (NB. You're seeing the old SeaBIOS version included with e689f7c, which was the first buggy commit.)
>
> If NT gets past this point without erroring out (ie, it makes it to the boot menu), the rest of the system is 100% fine and there are no other disk I/O issues whatsoever. For example, on QEMU 2.9.0 I was able to enable disk compression, answer ""Yes"" to ""Compress entire disk now?"" and have the process fully complete. No hitches.
>
"
1737194,2018-01-25 15:58:11 UTC,"> On Jan 25, 2018, at 2:53 AM, i336_ <email address hidden> wrote:
>
> Hi,
>
> I've been experiencing various disk I/O issues with Windows NT too, as
> well as with Windows 3.1. I think `-M isapc` may be to blame somehow.
>
> I've documented my experiences over at
> https://bugs.launchpad.net/qemu/+bug/1745312.
>
> That report contains information on how to lift out and build the
> before-and-after QEMU commits that I think relate to this being broken.
> John Arbuckle, perhaps you could run through that and see if you
> continue to have issues.
>
> I was initially going to post that report as a comment in this thread,
> until I realized I was having I/O issues on multiple operating systems.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737194
>
> Title:
>  Windows NT 4.0 fails to boot from qcow2 installation
>
> Status in QEMU:
>  New
>
> Bug description:
>  Windows NT 4.0 will not boot from an installation more than once if
>  installed in a qcow2 image file. A quick fix to this problem is to use
>  the qcow format instead.
>
>  Steps to reproduce this issue:
>
>  Create the image file:
>  qemu-img create -f qcow2 winnt4.qcow2 1G
>
>  Boot from a Windows NT 4.0 Workstation CD:
>  qemu-system-i386 -hda winnt4.qcow2 -cdrom /dev/cdrom -boot d -m 128 -cpu pentium -vga cirrus
>
>  During the installation process you have the choise between FAT and
>  NTFS. You can pick anyone.
>
>  After finishing the installation the guest will reboot to install
>  additional items. Once this is done the guest will be bootable. Eject
>  any CD media from QEMU and reboot. You will then see Windows NT 4.0
>  booting up to the desktop. Go to ""Start->Shut down"" to shut down. Then
>  when Windows is ready quit QEMU.
>
>  Now try to boot using this command:
>  qemu-system-i386 -hda winnt4.qcow2 -boot c -m 128 -cpu pentium -vga cirrus
>
>  The BIOS screen will display an error message:
>
>  For NTFS:
>  Booting from Hard Disk...
>  A disk read error occurred.
>  Insert a system diskette and restart
>  the system.
>
>  For FAT:
>  No bootable device.
>
>  Additional information:
>  qemu-system-i386 version: 2.10.1
>  qemu-img version: 2.10.92 (v2.11.0-rc4-dirty)
>
>  If you don't have a Windows NT 4.0 Workstation installation CD, you may download one from here:
>  https://winworldpc.com/product/windows-nt-40/40
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1737194/+subscriptions
"
1737201,2018-05-02 12:04:24 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1737201,2017-12-08 22:42:22 UTC,"Note that the patch that this failed on is failing for some other weird issues with locked up guestfs and eventlet thread switching, so maybe that is doing something strange here."
1737201,2018-04-02 13:19:06 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1737201,2017-12-08 16:17:06 UTC,"For some reason I'm only seeing this in one change right now, so maybe I just got unlucky but does seem like something we need to handle regardless:"
1737201,2017-12-08 21:15:32 UTC,The code that's blowing up was added in Newton: https://review.openstack.org/#/c/325923/
1737201,2017-12-08 22:40:44 UTC,"I'm not really sure how this can happen. The test creates a server and asserts it has an interface (port) and then it attaches another port but without requesting any specific network or port, it wants nova to allocate a port from the network available to the project, which there should be one otherwise allocate_for_instance would raise an exception and we wouldn't get to the notification code. I wonder if https://review.openstack.org/#/c/403568/ could be causing issues here where we store the info_cache on the instance in memory and maybe that is empty somehow because of this empty request, but as noted, we should be building the info cache from existing networks on the instance if none are requested."
1737201,2017-12-14 10:16:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527920"
1737201,2017-12-19 22:24:11 UTC,"Reviewed:  https://review.openstack.org/527920
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=553f2edde596348ca5447588c5a0b06f3b6be286
Submitter: Zuul
Branch:    master"
1737201,2018-01-08 13:07:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/531745"
1737201,2018-04-18 22:00:24 UTC,"Reviewed:  https://review.openstack.org/531746
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6a2882bb7bfabe0a694222c1e821fbe08fa26edf
Submitter: Zuul
Branch:    stable/ocata"
1737201,2018-01-26 00:43:54 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1737201,2018-02-28 17:26:18 UTC,"Reviewed:  https://review.openstack.org/531745
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4eff70621146d0ddca19b8e22c76d8ee3d043aed
Submitter: Zuul
Branch:    stable/pike"
1737201,2018-01-08 13:11:01 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/531746"
1737207,2018-05-02 12:01:40 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1737207,2018-04-20 13:14:04 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1737207,2018-04-18 21:53:54 UTC,"Reviewed:  https://review.openstack.org/548314
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1291d45418138d28f67873c6e47aa740e48ff80f
Submitter: Zuul
Branch:    stable/ocata"
1737207,2018-04-02 13:09:26 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1737207,2018-03-29 03:58:54 UTC,"Reviewed:  https://review.openstack.org/548312
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=13b598d371e7d0a67a953a87666d2e6adbc38372
Submitter: Zuul
Branch:    stable/pike"
1737207,2018-04-02 13:18:47 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1737207,2017-12-08 21:04:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526772"
1737207,2018-02-27 14:03:35 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/548289"
1737207,2018-02-27 15:06:37 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/548312"
1737207,2018-02-27 15:16:58 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/548314"
1737207,2018-03-28 17:47:17 UTC,"Reviewed:  https://review.openstack.org/548289
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=088bf6df8ee332f1c24493430003a5bf1b77b2ce
Submitter: Zuul
Branch:    stable/queens"
1737207,2018-02-28 17:26:33 UTC,"Reviewed:  https://review.openstack.org/526772
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6839630e86d958dcda8585664586754d419363a7
Submitter: Zuul
Branch:    master"
1737212,2017-12-08 20:25:11 UTC,"The attachment ""webex.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1737212,2017-12-08 22:20:30 UTC,"additionally to applying the above patch it is required to add ""--enable-webex-token"" to DEB_CONFIGURE_EXTRA_FLAGS before build."
1737212,2017-12-08 23:46:24 UTC,Agreed. I would love to get away from a Windows VM just for Jabber. Please port to Ubuntu.
1737212,2020-05-21 17:26:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737214,2018-03-30 17:47:29 UTC,"Reviewed:  https://review.openstack.org/539541
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e521616afd14e6eedc0d3bfca0adf2179f4e05c2
Submitter: Zuul
Branch:    stable/pike"
1737214,2018-04-02 13:19:02 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1737214,2018-02-09 07:14:04 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1737214,2018-01-31 13:31:14 UTC,"Reviewed:  https://review.openstack.org/526748
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7c30da13842469e641d171b6008a57d5db8c5d5e
Submitter: Zuul
Branch:    master"
1737214,2017-12-08 18:18:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526748"
1737214,2018-01-31 14:07:40 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/539541"
1737225,2017-12-08 18:36:46 UTC,"The pip installation goes through `check_call` so I'm not sure why stdout seems to be eaten. The workaround is to create a venv in the build environment and try installing the package by hand, where you'll see the real failures."
1737226,2017-12-08 18:54:55 UTC,Forgot to mention that I'm able to connect to both phone and speakers using an external usb bt adapter. It's inconvenient though.
1737226,2017-12-08 18:58:30 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1737226,2017-12-08 19:00:06 UTC,This change was made by a bot.
1737226,2017-12-13 09:15:58 UTC,"With 4.15.0-041500rc2.201712031230 the speakers start playing for ca 2 seconds, then the playback source (youtube/soundcloud) fails. I need to disconnect the device to be able to play sound again from internal speakers. Attaching syslog."
1737226,2017-12-14 09:38:00 UTC,"And to answer your question - it is a fresh install on a new machine, didn't work before."
1737226,2017-12-18 05:46:55 UTC,"Maybe this?
https://bugzilla.kernel.org/show_bug.cgi?id=197147"
1737226,2017-12-25 17:16:31 UTC,Yes! BT worked fine when wi-fi was turned off. The workaround helps fix it. Thanks everyone!
1737226,2017-12-25 17:19:20 UTC,Duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=197147
1737228,2018-09-07 04:36:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737248,2019-03-08 08:37:45 UTC,Problem still persists in Ubuntu 18.10.
1737248,2019-01-07 16:43:09 UTC,"Still having this problem:
corrado@corrado-p13-dd-1107-x:~$ apt policy gparted
gparted:
  Installed: 0.32.0-1ubuntu1
  Candidate: 0.32.0-1ubuntu1
  Version table:
 *** 0.32.0-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
        100 /var/lib/dpkg/status
corrado@corrado-p13-dd-1107-x:~$"
1737248,2018-01-19 22:28:34 UTC,"well, this is bad decision because it simply broke gparted!
workaround (switching to gnomedisk...hahaha) it not helping or fixing any problem with gparted and wayland."
1737248,2017-12-08 21:06:17 UTC,I respectfully disagree with this decision.
1737248,2017-12-09 01:31:36 UTC,This bug was fixed in the package gparted - 0.30.0-3ubuntu1
1737249,2018-05-30 13:44:31 UTC,"Similar to the fix for bug 1721145, we probably just need an appropriately named persist-key in both eg-grids in reporter/t_edit_template.tt2 ."
1737249,2018-12-20 19:42:19 UTC,NOTE: This needs an upgrade script (add this persist key to config.workstation_setting_type) because of the change to server-side settings. Thanks to Michele Morgan for the tip (see https://bugs.launchpad.net/evergreen/+bug/1729435/comments/5).
1737249,2020-01-23 13:04:45 UTC,Confirming this behavior still persists in v3.2 (customized versions for Evergreen Indiana) and 3.4.1 on public demo server hosted by Equinox.
1737249,2020-06-03 20:33:49 UTC,"Confirming that the report template editor columns cannot be saved in v3.5 (customized version for Sitka Evergreen). I can change the column widths but the setting are not saved. I do not receive any message however, the changes are just not saved."
1737249,2020-09-02 17:24:08 UTC,Pushing this to add more heat.
1737269,2018-01-25 14:55:29 UTC,fixed in bionic
1737271,2017-12-08 23:56:26 UTC,At least these links have been widely published (they're in the Ubuntu Font released documentation):
1737274,2017-12-09 00:05:12 UTC,This is what the site used to look like:
1737278,2017-12-09 00:44:10 UTC,"There did not seem to be anything private in the coredump, hence marking as public."
1737279,2017-12-21 08:07:44 UTC,"For comparison, the whole directory /etc/dconf/db/gdm.d/ does not exist in a fresh installation of Ubuntu 18.04."
1737279,2018-03-26 20:22:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737279,2018-05-11 11:55:38 UTC,Removing /etc/dconf/db/gdm* and restarting gdm solved the issue. Those files were last changed on 2013.10.28.
1737279,2019-08-05 03:44:23 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1737282,2017-12-10 05:27:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737283,2017-12-09 16:54:07 UTC,It seems in fact that the above description is just the tip of the iceberg and what really needs doing is to install newer versions of dependent python packages as described here:
1737285,2017-12-09 10:36:07 UTC,"Looks like it was removed from 17.10 with the following message:
""(From Debian) ROM; obsoleted by squashfs and initramfs (...)""
See https://launchpad.net/ubuntu/+source/cramfs/+publishinghistory and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800316 for more details."
1737285,2017-12-09 11:55:22 UTC,"The problem (of course) being that a lot of embedded IoT devices still use it, meaning that if you want to pick them apart or modify them, it's needed."
1737285,2019-06-17 06:50:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737285,2019-06-17 06:51:18 UTC,Still needed for embedded development in bionic.
1737285,2020-01-06 18:08:31 UTC,Still needed for development purposes in bionic or focal
1737285,2020-03-24 00:29:15 UTC,Still needed for development purposes in bionic & focal.
1737285,2020-08-11 02:18:03 UTC,"So annoying. If it helps anyone, I updated the source code so they will compile on Ubuntu 20.04."
1737290,2017-12-10 01:04:19 UTC,"Some further information: The first time Open Rails is run after installation is no problem. When it runs it creates a log file that has no owner. There is no way to change permissions to allow Open Rails, or the system administrator, to access the file. There is no way to change the owner. Deleting it appears to remove it, but when Open Rails is restarted it still is denied access.The operating system is Windows 7 Ultimate 64-bit. The computer is an AMDA10-5800K running on a Gigabyte GA-F2A75M-HD2 motherboard with 8GB RAM."
1737290,2017-12-10 01:43:31 UTC,"Sorry, I just realized I had not mentioned, this was Open Rails 1.2.3766, downloaded from Open Rails on 20171209."
1737304,2017-12-09 17:02:30 UTC,This is what happens:
1737304,2017-12-11 03:46:31 UTC,"Thank you for the detailed explanation.
Didn't know if it's the way it's supposed to be, since not all implementations treat it the same way."
1737304,2020-10-10 00:20:11 UTC,LC_CTYPE no longer affects sbcl.
1737311,2017-12-09 13:51:36 UTC,"similar to Bug 616469?
https://bugs.launchpad.net/inkscape/+bug/616469"
1737311,2017-12-09 15:29:51 UTC,"I suppose it might similar but I used some pretty big shapes.
Thing is, after cutting holes in one of the loops, the outset distance got reduced, which is strange seeing how the preferences have a dedicated setting for generic outset distance."
1737311,2018-10-16 17:56:33 UTC,"I have also weird behavior with outset and inset. My workaround is to use dynamic offset because my shapes are not complicated but I have tested in previous releases 0.48 and was ok.not so weird shapes. I encourage you to solve as soon as you can. You are doing a great job.
This has been comented in the inkscape Facebook page."
1737311,2018-10-16 18:02:22 UTC,I forgot to say that I am using Inkscape 0.92.3 in Windows 10. I have also kde Neon machine if you need more info let me know it
1737320,2018-08-12 17:51:16 UTC,"Works fine with MATE's Marco, but not with xfwm4 (18.04)."
1737320,2018-08-12 17:51:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737320,2018-09-18 09:42:40 UTC,"The update-manager actually disables resizing for its window -> self.set_resizable(False), so I do not think that this is a bug in xfwm4."
1737320,2019-03-28 17:46:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737334,2019-02-26 16:13:31 UTC,"This bug is still present to this day, and I just had it in Debian 10 Buster and only way to start ""pdfchain"" is to run it with ""sudo""."
1737334,2018-02-16 20:39:34 UTC,"in addition to this report that is being ignored, it seems if it is ran with ""sudo"" it will work fine but ""sudo"" should not be needed."
1737334,2018-05-09 02:43:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737336,2017-12-17 13:47:59 UTC,https://cgit.kde.org/kdepimlibs.git/?h=KDE/4.14 is dead upstream
1737351,2020-06-25 09:42:54 UTC,"Cada vez que se instala un nuevo programa o actualización, informa que la instalación (o desinstalación) no se completó.
Los programas se instalan y funcionan correctamente.
Con el único que hay problemas es con Spotify"
1737351,2018-02-20 08:33:27 UTC,.
1737351,2019-08-02 22:24:27 UTC,-
1737351,2019-08-21 09:08:55 UTC,.
1737351,2019-09-20 14:20:54 UTC,"No entiendo, siempre se produce el mismo error y no se soluciona?"
1737351,2019-12-18 13:07:49 UTC,...?
1737351,2019-12-18 15:12:43 UTC,looks like a corruption/local problem rather than a package bug
1737351,2020-04-22 10:10:47 UTC,.
1737351,2020-07-05 11:08:06 UTC,"Cada vez que se instala un nuevo programa o actualización, informa que la instalación (o desinstalación) no se completó.
Los programas se instalan y funcionan correctamente.
Con el único que hay problemas es con Spotify"
1737351,2020-12-18 12:32:48 UTC,.
1737355,2019-07-23 09:06:24 UTC,This was released a while ago https://review.opendev.org/#/c/470188/
1737357,2017-12-09 21:47:47 UTC,An attachment shows a successful internal interface (svi0) and address discovery. The address is configured in /e/n/i:
1737357,2017-12-11 16:27:03 UTC,"I'm not sure what the proper fix would be, but at least there's enough information so that we can investigate further."
1737357,2019-09-19 11:56:54 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1737377,2017-12-11 19:11:14 UTC,"Hello Christian,"
1737377,2017-12-11 15:36:06 UTC,"Hi Simon,
we are currently shuffling around responsibilities for iproute so extra latencies might occur :-/."
1737378,2018-06-26 18:21:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737389,2017-12-10 10:01:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/526919"
1737389,2017-12-14 15:11:18 UTC,"Change abandoned by Yushiro FURUKAWA (<email address hidden>) on branch: master
Review: https://review.openstack.org/526919
Reason: move to https://review.openstack.org/#/c/524125/"
1737392,2017-12-11 10:48:37 UTC,Hi Raiman. Good morning. Do you need any other details or help?
1737392,2017-12-11 11:35:31 UTC,No thanks. Just have to dive into it later ;-)
1737423,2018-04-20 10:02:15 UTC,apport information
1737423,2018-04-20 10:02:14 UTC,apport information
1737423,2018-04-20 10:12:55 UTC,"addaed tag kernel-bug-exists-upstream
regards"
1737423,2018-05-08 05:28:33 UTC,Can you try v4.17-rc3?
1737423,2018-05-08 08:23:41 UTC,"Will use the computer saturday 12, will make the test (may be sunday)"
1737423,2018-05-13 14:59:53 UTC,Hello
1737423,2018-05-15 14:25:42 UTC,"in file
/var/lib/dpkg/info/linux-image-4.17.0-041700rc4-generic.prerm"
1737423,2018-05-15 14:40:55 UTC,Attempted to try v4.17-rc5
1737423,2018-05-29 16:17:32 UTC,"Looks like the RAM size is correctly detected:
[   10.572891] nouveau  [  DEVICE][0000:03:09.0] BOOT0  : 0x04a100a1
[   10.572897] nouveau  [  DEVICE][0000:03:09.0] Chipset: NV44A (NV4A)
[   10.572903] nouveau  [  DEVICE][0000:03:09.0] Family : NV40
[   10.579195] nouveau  [   VBIOS][0000:03:09.0] checking PRAMIN for image...
[   10.579208] nouveau  [   VBIOS][0000:03:09.0] ... signature not found
[   10.579213] nouveau  [   VBIOS][0000:03:09.0] checking PROM for image...
[   10.900540] nouveau  [   VBIOS][0000:03:09.0] ... appears to be valid
[   10.900544] nouveau  [   VBIOS][0000:03:09.0] using image from PROM
[   10.900760] nouveau  [   VBIOS][0000:03:09.0] BIT signature found
[   10.900767] nouveau  [   VBIOS][0000:03:09.0] version 05.44.a2.10.01
[   10.913241] nouveau  [ DEVINIT][0000:03:09.0] adaptor not initialised
[   10.913253] nouveau  [   VBIOS][0000:03:09.0] running init tables
[   10.931444] nouveau  [     PFB][0000:03:09.0] RAM type: DDR2
[   10.931448] nouveau  [     PFB][0000:03:09.0] RAM size: 256 MiB"
1737423,2018-05-16 05:48:06 UTC,Sorry didn't notice that you use i386 instead of AMD64.
1737423,2018-05-16 10:06:50 UTC,Hello
1737423,2018-05-16 15:36:56 UTC,Found some document about size determination in pci devices
1737423,2018-04-20 10:02:11 UTC,apport information
1737423,2018-07-03 20:14:32 UTC,"upgraded to 16.04
now kernel is (standard 16.04) 4.4.0-130-generic(i686)"
1737423,2018-08-10 08:22:42 UTC,"Made a test yesterday, to see if the ""normal update"" has an effect
Result was kernel panic, as previous
see attached screen capture"
1737423,2018-08-10 08:25:20 UTC,"-Version-
Kernel		: Linux 4.4.0-131-generic (i686)
Compiled		: #157-Ubuntu SMP Thu Jul 12 15:49:15 UTC 2018
Distribution		: Ubuntu 16.04.5 LTS"
1737423,2018-05-15 14:46:37 UTC,Hello
1737423,2018-04-20 10:02:09 UTC,apport information
1737423,2018-04-20 10:02:06 UTC,apport information
1737423,2018-04-20 10:02:07 UTC,apport information
1737423,2017-12-10 22:53:34 UTC,"Difficult to determine package
-could the driver itself (nouveau or proprietary)
-could be false information given by the kernel to the driver..."
1737423,2017-12-10 20:24:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1737423,2017-12-11 16:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1737423,2017-12-11 20:24:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1737423,2017-12-16 22:26:08 UTC,"This computer is installed in a secondary house, and it is not planned to use it before March 2010"
1737423,2018-04-20 10:02:08 UTC,apport information
1737423,2018-04-20 09:59:16 UTC,installed v4.15-rc3 and booted
1737423,2018-04-20 10:01:53 UTC,apport information
1737423,2018-04-20 09:10:19 UTC,installed v4.15-rc3 and booted
1737423,2018-04-20 10:01:56 UTC,apport information
1737423,2018-04-20 10:01:58 UTC,apport information
1737423,2018-04-20 10:01:59 UTC,apport information
1737423,2018-04-20 10:02:00 UTC,apport information
1737423,2018-04-20 10:02:02 UTC,apport information
1737423,2018-04-20 10:02:03 UTC,apport information
1737423,2018-04-20 10:02:04 UTC,apport information
1737423,2018-04-20 10:01:54 UTC,apport information
1737427,2018-01-23 08:16:20 UTC,Thanks for the report. I've opened a PR addressing this: https://github.com/snapcore/snapd/pull/4520
1737428,2019-07-05 17:21:24 UTC,Any news or progress on these issues now that we are a year and a half into this bug?
1737428,2020-10-02 15:41:45 UTC,https://www.freedesktop.org/software/systemd/man/systemd.network.html#VRF=
1737428,2020-05-06 07:31:53 UTC,"On Tue, May 05, 2020 at 06:04:28PM -0000, Billy Olsen wrote:

> @bjornt Are you going to copy it over to the MAAS discourse feature set
> then?
"
1737428,2020-05-05 18:04:28 UTC,@bjornt Are you going to copy it over to the MAAS discourse feature set then?
1737428,2020-05-05 07:46:43 UTC,"This sounds great, but it's not a bug report. It's a feature request. For MAAS, we track feature requests at https://discourse.maas.io/c/features, so I'm going to mark this bug report as Invalid for MAAS."
1737428,2019-07-05 18:36:30 UTC,"Sandor,"
1737428,2019-03-16 00:45:43 UTC,BUMP! +1000 for this feature. We need vrf support in MAAS to be able to use it with in bgp/vrf stack. @dmitriis thank you for the thorough write up and detailed explanation of the problem/solution here!
1737428,2017-12-10 20:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1737428,2018-01-29 09:07:07 UTC,"It would be good to have a clearer discussion of what issues you are
running into with routes. There are several ways that we *could* tackle the
issue. Static Routes was the mechanism that we started modeling because
that was the ask from the field (because, as-I-understand, that was the
solution they were using manually).
There have been discussions about enabling things like BGP. It would be
possible to push heavier on the modeling aspect, and give ways to model
routing as part of the network and space model, and then have Juju tracking
and updating those (eg, route traffic from this space to that space via
these gateways)."
1737428,2018-01-26 15:42:17 UTC,I'd like to chime in and add that this is something that we've been missing in our Juju and MAAS deployment of OpenStack.
1737428,2018-01-08 02:57:21 UTC,Marking as Incomplete Wishlist as per 'maas'
1737428,2017-12-21 15:25:29 UTC,"Andres,"
1737428,2017-12-11 15:04:06 UTC,"Hi Dimitrii,"
1737428,2018-01-30 07:16:39 UTC,"John,"
1737428,2017-12-10 20:14:23 UTC,For Ubuntu kernel this is a backport request.
1737429,2017-12-24 13:35:00 UTC,"For information, the upstream bug is now fixed for the yet-to-be-released versions 2.2.4 and 2.3.0."
1737429,2017-12-13 21:06:07 UTC,"For reference, the upstream bug is https://www.lyx.org/trac/ticket/10847"
1737429,2017-12-13 18:27:37 UTC,"You are welcome. By reporting bugs, you help us making is amazing."
1737429,2017-12-13 18:19:25 UTC,Aha.  Thanks for your responsiveness and thanks very much for this amazing software!
1737429,2017-12-13 10:25:33 UTC,"The bug is now fixed in our master branch (it was a tough one to track). Eventually, it should be backported to upcoming 2.3.0 and 2.2.4 versions."
1737429,2017-12-12 05:23:56 UTC,"Here is a screen capture.
After making one match (of two possible), I move the cursor to the main window and type ctrl-z."
1737429,2017-12-12 16:11:52 UTC,"OK, I can reproduce now. The issue is not about replacement itself, but about using Undo while the cursor is inside an inset in one of the two document areas of the advanced search panel. I'll try to see what I can do from there."
1737429,2018-04-26 21:37:10 UTC,LyX 2.2.4 and LyX 2.3.0 have been released. The bug is fixed upstream.
1737429,2017-12-11 09:24:49 UTC,"I also tried to reproduce it, even with the ubuntu-provided binary, but did not succeed. There is something that we are missing. I see however that the ubuntu binary is built with -fstack-protector and I presume that it can catch things that we do not routinely see."
1737429,2017-12-11 02:30:14 UTC,"Christopher, thank you very much for taking the time to report this issue and to give details on how to reproduce. I've tried several times and I cannot reproduce. Can you make a screencast? If not, please answer the following questions: After writing ""ccc"", do you put the cursor at the top? Or after you search you first click on ""Yes"" in the ""wrap search"" dialog? Do you do the search before you click in the replace box and type ""\abc""? Do you do anything (e.g. click in the main text area?) after you make the substitution and before you execute the ctrl-z? If you do ctrl-z with the cursor in the advanced find, then it undoes the last edit to the advanced find window. If you do it in the main workarea, it undoes the substitution."
1737429,2017-12-12 16:14:55 UTC,"Concerning your comment below the video, actually you do not move the (blinking) cursor to the main window, only the mouse cursor. Therefore the undo command goes to the place where the blinking cursor is, in the ERT inset."
1737432,2018-03-08 20:56:40 UTC,Is this the same bug as https://bugs.launchpad.net/ubuntu/+source/golang-1.10/+bug/1743598 ?
1737432,2018-03-09 05:58:57 UTC,"Yes, it is exactly the same."
1737432,2018-03-02 19:31:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737432,2018-03-02 19:32:18 UTC,For reference: https://groups.google.com/forum/#!topic/golang-nuts/B7sZrDhhWfw
1737436,2017-12-11 14:42:21 UTC,"I believe we also need to change curtin, since it doesn't allow specifying the partition table type for the boot disk."
1737436,2018-06-29 21:34:26 UTC,"Curtin allows specifying[1] both.  For bootable GPT, you just need a bios_grub partition"
1737436,2018-09-21 13:59:55 UTC,"This seems to only apply to the device flagged as bootable.
I was investigating why half of my RAID1 uses MBR and the other half uses GPT and this seems to be the reason."
1737436,2019-09-19 11:56:57 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1737437,2017-12-11 05:49:00 UTC,It would be great if someone could help us distributing Mixxx bundled as a flatpak. This would make Mixxx independent of distribution release cycles and we would have more control over the bundled dependencies.
1737437,2017-12-13 12:19:56 UTC,I've discussed this with one colleague of mine and he said that it's possible to use QT4. But you need to bundle it with Mixxx. Not sure here if it's allowed by licence.
1737437,2017-12-28 03:18:31 UTC,See also: AppImage packaging (Bug #1621181)
1737437,2019-09-27 10:31:31 UTC,"aaaaha, we have one already, yaaay!"
1737444,2018-12-14 12:36:47 UTC,This still reproduces on git master:
1737449,2018-01-04 01:11:57 UTC,"Because the things are complicated enough, I have issued a Blueprint for this.
https://blueprints.launchpad.net/nova/+spec/libvirt-qemu-numa-support"
1737457,2018-03-01 09:59:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737458,2017-12-12 10:39:54 UTC,There appears to be a trigger loop:
1737460,2017-12-11 09:10:33 UTC,libvlc-bin failing to process is not the first error. It already bails out on systemd. But to me that looks like dpkg is incorrectly detecting libgdk-pixbuf2.0-0:amd64 -> libgdk-pixbuf2.0-0:i386 as a cycle. So let's reassign to dpkg.
1737464,2017-12-11 14:38:36 UTC,This was discussed on the mailing list as well:
1737465,2019-08-29 13:15:39 UTC,"Reviewed:  https://review.opendev.org/676257
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=677c95280b21eb6628a7758f173cb98c4e3572c2
Submitter: Zuul
Branch:    stable/stein"
1737465,2019-08-29 13:15:29 UTC,"Reviewed:  https://review.opendev.org/676256
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=30552298410605ef5710fd564f5e46e5b0df0597
Submitter: Zuul
Branch:    stable/stein"
1737465,2019-08-13 17:41:11 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/676257"
1737465,2019-08-09 23:04:29 UTC,"Reviewed:  https://review.opendev.org/663387
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=426a303ee4cb848e75b9ed2acc498479c651c539
Submitter: Zuul
Branch:    master"
1737465,2019-06-05 17:35:14 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/663388"
1737465,2019-06-05 17:34:56 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/663387"
1737465,2019-06-05 15:26:17 UTC,Some related changes:
1737465,2018-11-06 19:01:46 UTC,"I've pushed some related changes for this bug am removing myself as assignee since I think we still have some known performance issues during scheduling, specifically around this method to get all host states from all cells, and for each compute (host state) getting the aggregates and instances from each cell db per host:"
1737465,2018-10-25 19:50:40 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/571928"
1737465,2018-07-24 21:19:10 UTC,"Reviewed:  https://review.openstack.org/569247
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91f5af7ee7f7140eafb7237875f6cd6ea1abcd38
Submitter: Zuul
Branch:    master"
1737465,2019-08-13 17:40:57 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/676256"
1737465,2018-05-30 10:00:49 UTC,"Reviewed:  https://review.openstack.org/570083
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bfb9d3f179607c25f91d77585f97df6d0704c253
Submitter: Zuul
Branch:    stable/queens"
1737465,2018-06-02 13:21:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/571928"
1737465,2018-04-05 20:39:28 UTC,"Sorry for getting to this so long after it was opened. What do you mean by, ""Because cellv2 have disable instance info cache.""? I don't notice anything in the code that is deliberately disabling the instance info cache in the HostManager."
1737465,2018-04-05 21:07:58 UTC,"To be clear, if the cache was disabled, it was unintentional and it is a bug."
1737465,2018-05-10 06:53:16 UTC,"This is a performance issue. Compute instances info just used by affinity filter.
Anti affinity will judgment the instance whether it belongs to the current computing node. The current code is to determine if the instance uuid is in the instances of the compute node.
We can determine if the current instance exists. If it exists, we get the host it belongs to. Then we judge in anti- affinity whether the host name of the compute node is the same as the instance host name."
1737465,2018-05-17 17:18:08 UTC,"By ""Because cellv2 have disable instance info cache."" I assume you mean you have disabled the track_instance_changes configuration option, correct?"
1737465,2019-08-12 12:55:52 UTC,"Reviewed:  https://review.opendev.org/663388
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3a69fdb333e80f5ad2e025a9823b11483fad55c2
Submitter: Zuul
Branch:    master"
1737465,2018-05-17 18:42:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569218"
1737465,2018-05-17 18:48:11 UTC,"You said, ""So there's a performance issue even we don't use affinity filter policy"" - are you actually not using any of the ServerGroup(Anti)AffinityFilter or SameHost/DifferentHostFilter filters? If so, we could potentially short-circuit the HostManager._get_instance_info() method to not even pull instances from the database if an affinity filter is not enabled."
1737465,2018-05-17 20:10:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/569247"
1737465,2018-05-19 02:34:14 UTC,"Reviewed:  https://review.openstack.org/569218
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a1a335f19a986a593487a802d7b9448f7efc5bab
Submitter: Zuul
Branch:    master"
1737465,2018-05-23 00:14:06 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/570083"
1737465,2018-05-17 17:21:17 UTC,"By the way, ""track_instance_changes"" doesn't really have anything to do with cells v2 unless you have a split MQ deployment where the scheduler and compute services (which are in the cells) are on different MQs - because then the computes can't RPC cast to the scheduler topic ""at the top"" of the deployment, as discussed here:"
1737466,2017-12-12 00:33:03 UTC,"Sorry for wasting your time; this ticket can probably be closed. After spending a few days with the Flatpak backend, I don't think it should be installed or made the default yet. I'm going to continue to polish it upstream. If and when it's ready, I'll open a new ticket."
1737466,2017-12-11 04:34:58 UTC,"This should go to upstream, not us."
1737466,2017-12-11 04:46:37 UTC,"In fact, I did start upstream: https://bugs.kde.org/show_bug.cgi?id=387719"
1737466,2017-12-11 05:13:38 UTC,"Created an internal ticket in Phab for Kubuntu, but no promises, and if it lands it will be part of any other backports update."
1737466,2017-12-11 05:22:27 UTC,"Thanks, I'll follow along in https://phabricator.kde.org/T7566. We can close this here if that would make your life easier."
1737508,2018-04-24 07:40:56 UTC,"""kolla-ansible genconfig"" don't be used to generating confimaps anymore,
use a below command.
ansible-playbook -e ansible_python_interpreter=/usr/bin/python -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla ansible/site.yml"
1737509,2018-05-06 12:37:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737510,2017-12-11 09:53:04 UTC,Is it probably related to this very old report:
1737510,2017-12-11 09:54:51 UTC,And there should be SynCthing in title :(
1737511,2017-12-12 20:21:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737511,2017-12-14 17:13:11 UTC,This bug was fixed in the package linux - 4.4.0-104.127
1737511,2017-12-14 18:40:53 UTC,The package has been published and the bug is being set to Fix Released
1737513,2017-12-11 10:13:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527046"
1737513,2018-01-26 00:43:28 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1737513,2018-09-24 14:47:18 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1737513,2018-06-04 14:27:58 UTC,This issue was fixed in the openstack/nova 16.1.4 release.
1737513,2018-01-16 17:38:10 UTC,"Reviewed:  https://review.openstack.org/527046
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=82c823bcec5850f6876308ebcdbcb37312bf763f
Submitter: Zuul
Branch:    master"
1737513,2018-04-30 19:39:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/565288"
1737513,2018-04-26 17:52:38 UTC,@Lee Yarwood: Are you planning on backporting the fix for this bug to Pike in Nova?
1737513,2018-05-20 21:21:47 UTC,"Reviewed:  https://review.openstack.org/565288
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f8498c41cdfec2acde62a1da1abce917ac882c7d
Submitter: Zuul
Branch:    stable/pike"
1737515,2017-12-14 17:14:45 UTC,This bug was fixed in the package linux-aws - 4.4.0-1044.53
1737515,2017-12-14 18:44:20 UTC,The package has been published and the bug is being set to Fix Released
1737519,2017-12-14 17:17:25 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1080.88
1737519,2017-12-14 18:37:02 UTC,The package has been published and the bug is being set to Fix Released
1737520,2018-04-05 08:35:01 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1088.93
1737520,2017-12-15 08:57:35 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1082.87
1737520,2017-12-15 10:32:06 UTC,The package has been published and the bug is being set to Fix Released
1737526,2017-12-11 14:06:35 UTC,"Hi, Could you please specify a version of xtrabackup you are using ?"
1737526,2017-12-11 14:17:08 UTC,"Hi, it's the latest, 2.4.9-1"
1737526,2018-01-20 07:44:58 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1488
1737532,2017-12-12 10:51:54 UTC,"For what it is worth, I was able to produce an i386 snap using a container based on the ubuntu:xenial/i386 LXC image.  This also avoided all the cross compilation issues related to build-packages selection."
1737535,2017-12-11 13:39:39 UTC,"Hi Felipe,"
1737535,2017-12-12 15:42:44 UTC,"olá,"
1737535,2019-11-14 02:29:44 UTC,Should be fixed in 19.10 or by using the snap.
1737536,2018-04-06 09:11:49 UTC,"A detailed answer to this problem is provided here:
https://www.spinics.net/lists/linux-media/msg131388.html
In summary, these ""complex"" webcams need drivers both in kernel space and user space, and it will take some time before they are supported under linux.
If ubuntu devs can help to speed up the development of these drivers, this would be appreciated!"
1737536,2017-12-11 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1737536,2017-12-11 15:42:37 UTC,"After some research, it seems the webcams depend on a new intel driver which will be released in kernel 4.16:
https://<email address hidden>/msg122619.html"
1737545,2017-12-21 10:31:16 UTC,solved with CONFIG_CEILOMETER_INSTALL=n into answer file
1737556,2018-08-07 01:05:21 UTC,Here's what I think is happening:
1737556,2018-08-07 02:04:37 UTC,I found a non-interactive workaround but it requires you to ignore errors from the workaround command.
1737556,2018-08-07 13:50:44 UTC,Some feedback from the sgdisk author on this scenario is below. Would the Ironic team be interested in simply changing Ironic's behavior based on the return code of the sgdisk -Z?
1737556,2018-08-08 14:11:44 UTC,https://review.openstack.org/#/c/589831/
1737556,2018-10-29 15:10:24 UTC,This issue was fixed in the openstack/ironic-python-agent 3.4.0 release.
1737556,2018-10-30 06:14:33 UTC,I found the fix info of this problem in   ironic-python-agent 3.4.0 release is :
1737556,2018-08-03 15:40:56 UTC,I also ran into this. I have run the following 4 times but they still fail cleaning.
1737561,2017-12-18 10:12:12 UTC,Can you share some details on what you're building? A YAML snippet would be great.
1737561,2017-12-18 10:41:39 UTC,"Indeed, the :target architecture PR is relevant; I've commented there to suggest a different default for stage-packages and addition of :host and :build architecture tags; thanks!"
1737564,2017-12-11 15:41:02 UTC,"P.S. Debian Stable has already updated to xymon_4.3.28-2
Ref: https://packages.debian.org/search?keywords=xymon"
1737564,2017-12-11 16:16:46 UTC,"> P.S. Debian Stable has already updated to xymon_4.3.28-2
"
1737564,2017-12-11 23:05:59 UTC,">> P.S. Debian Stable has already updated to xymon_4.3.28-2
"
1737569,2018-11-06 12:39:20 UTC,"$ git describe --contains 873f76aa7a613a93cbcca8337580e4669654243f
3.5.1~104"
1737569,2017-12-11 15:55:32 UTC,Upstream Github issue: https://github.com/sosreport/sos/issues/1103
1737569,2018-06-14 14:14:01 UTC,"We are slowly discussing to integrate sosreport v3.6 into Ubuntu, but it first need to be officially release upstream."
1737574,2017-12-11 17:42:39 UTC,"usb_modeswitch 2.2.5  2015-07-17
usb_modeswitch 2.2.6  2015-11-01
usb_modeswitch 2.3.0  2016-01-13
usb_modeswitch 2.4.0  2016-06-13
usb_modeswitch 2.5.0  2017-01-17
usb_modeswitch 2.5.1  2017-08-06"
1737576,2019-10-10 13:58:48 UTC,The snapcraft help for push-metadata has been improved
1737582,2017-12-11 16:43:30 UTC,"Ubuntu versión is:
#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:        14.04
Codename:       trusty"
1737582,2017-12-15 09:12:31 UTC,We had to reinstall Ubuntu keeping the VG in order to make it work again.
1737591,2018-09-28 01:27:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737591,2018-09-28 01:29:09 UTC,A solution is documented here:
1737591,2018-10-02 09:32:23 UTC,This bug was fixed in the package ubuntu-mate-artwork - 18.10.1
1737592,2017-12-21 21:53:29 UTC,"Testing a zfsroot deploy without zfs present, curtin will trigger an install of the full linux-image-generic package during the install deps check."
1737592,2018-01-17 16:49:45 UTC,"closer.
still need artful to be updated. but seems like next build would do that."
1737592,2017-12-11 19:29:19 UTC,"Adding this to maas-images would look like this:
 http://paste.ubuntu.com/26165463/"
1737592,2017-12-11 18:45:24 UTC,As a work around you can specifically add the zfs module (if its in your kernel) with:
1737592,2018-01-10 14:32:06 UTC,"Well, I went looking to verify this. We got builds out of artful and xenial today (20180109)."
1737594,2017-12-12 13:52:22 UTC,Here is a picture of how it sees.
1737594,2019-01-03 19:28:12 UTC,"Is there a way to change this from Wishlist to ""High Bug""?  This issue makes it virtually impossible to route a board that has a 2 BGAs that are lined up.  (One on the top and one on the bottom)"
1737598,2017-12-11 19:10:35 UTC,"StacktraceTop:
 open_restricted (path=0x0, flags=526338, data=0x7eff758459a0 <driver_context>) at ../../src/xf86libinput.c:2212
 evdev_device_create (seat=seat@entry=0x55ce84e8a820, udev_device=udev_device@entry=0x55ce860a9e80) at ../src/evdev.c:1901
 path_device_enable (input=input@entry=0x55ce84ea3870, udev_device=udev_device@entry=0x55ce860a9e80, seat_logical_name_override=seat_logical_name_override@entry=0x0) at ../src/path-seat.c:156
 path_create_device (libinput=libinput@entry=0x55ce84ea3870, udev_device=udev_device@entry=0x55ce860a9e80, seat_name=seat_name@entry=0x0) at ../src/path-seat.c:230
 libinput_path_add_device (libinput=libinput@entry=0x55ce84ea3870, path=0x55ce85450440 ""/dev/input/event16"") at ../src/path-seat.c:351"
1737598,2017-12-26 01:43:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737604,2017-12-12 08:21:16 UTC,This proposed patch avoids the delimiter confusion and seems to address the other 'gotchyas' relating to multiple delimiters mentioned in the code comments.
1737604,2017-12-12 08:23:32 UTC,"The attachment ""parse_grub_menu - avoid delimiter confusion"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1737606,2019-02-11 09:39:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737606,2017-12-11 19:57:51 UTC,"StacktraceTop:
 fstatfs64 () at ../sysdeps/unix/syscall-template.S:84
 FcFStatFs (fd=fd@entry=23, statb=statb@entry=0x7f9f80ea96a0) at fcstat.c:370
 FcIsFsMtimeBroken (dir=dir@entry=0x7f9f7802c270 ""/usr/share/fonts"") at fcstat.c:428
 FcStatChecksum (file=file@entry=0x7f9f7802c270 ""/usr/share/fonts"", statb=statb@entry=0x7f9f80ea98d0) at fcstat.c:335
 FcDirCacheProcess (config=config@entry=0x7f9f780e74e0, dir=dir@entry=0x7f9f780f8280 ""/usr/share/fonts"", callback=callback@entry=0x7f9fec2ea190 <FcDirCacheMapHelper>, closure=closure@entry=0x7f9f80ea99e0, cache_file_ret=cache_file_ret@entry=0x0) at fccache.c:200"
1737606,2018-02-26 14:12:44 UTC,Crash again.
1737622,2018-01-25 09:34:53 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2512
1737623,2017-12-12 00:23:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1737623,2017-12-12 00:53:00 UTC,"I tried to use ""python3"", which is the install name, and it was rejected. I also tried to do a search for the package and didn't turn up anything."
1737625,2020-11-23 16:49:11 UTC,"I just talked to Dave Gilbert from upstream QEMU.  Overall, as I implied in comment#2, this gnarly issue requires specialized debugging, digging deep into the bowels of QEMU, 'virtio-blk' and 'virtio."
1737625,2018-01-09 14:15:06 UTC,"From another occurrence (reported by Lee Yarwood on IRC; as part of stable/pike), the full error from the source QEMU log"
1737625,2018-01-09 14:18:18 UTC,Not sure if we have a reliable reproducer here.
1737625,2020-11-23 15:44:19 UTC,"Fast forward more than two-and-a-half years, another hit[1] upstream (in Zuul):
---------------------------------------------------------------
2020-11-20 14:25:11.589+0000: starting up libvirt version: 6.0.0, package: 0ubuntu8.4~cloud0 (Openstack Ubuntu Testing Bot <email address hidden> Tue, 15 Sep 2020 20:36:28 +0000), qemu version: 4.2.1Debian 1:4.2-3ubuntu6.7~cloud0, kernel: 4.15.0-124-generic, hostname: ubuntu-bionic-ovh-bhs1-0021872194
LC_ALL=C \
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
HOME=/var/lib/libvirt/qemu/domain-10-instance-0000001a \
XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-10-instance-0000001a/.local/share \
XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-10-instance-0000001a/.cache \
XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-10-instance-0000001a/.config \
QEMU_AUDIO_DRV=none \
/usr/bin/qemu-system-x86_64 \
-name guest=instance-0000001a,debug-threads=on \
-S \
-object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-10-instance-0000001a/master-key.aes \
-machine pc-i440fx-4.2,accel=tcg,usb=off,dump-guest-core=off \
-cpu qemu64 \
-m 128 \
-overcommit mem-lock=off \
-smp 1,sockets=1,cores=1,threads=1 \
-uuid 2c468d92-4b19-426a-8c25-16b4624c21a4 \
-smbios 'type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=22.1.0,serial=2c468d92-4b19-426a-8c25-16b4624c21a4,uuid=2c468d92-4b19-426a-8c25-16b4624c21a4,family=Virtual Machine' \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=32,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc \
-no-shutdown \
-boot strict=on \
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \
-blockdev '{""driver"":""file"",""filename"":""/opt/stack/data/nova/instances/_base/61bd5e531ab4c82456aa5300ede7266b3610be79"",""node-name"":""libvirt-2-storage"",""cache"":{""direct"":true,""no-flush"":false},""auto-read-only"":true,""discard"":""unmap""}' \
-blockdev '{""node-name"":""libvirt-2-format"",""read-only"":true,""cache"":{""direct"":true,""no-flush"":false},""driver"":""raw"",""file"":""libvirt-2-storage""}' \
-blockdev '{""driver"":""file"",""filename"":""/opt/stack/data/nova/instances/2c468d92-4b19-426a-8c25-16b4624c21a4/disk"",""node-name"":""libvirt-1-storage"",""cache"":{""direct"":true,""no-flush"":false},""auto-read-only"":true,""discard"":""unmap""}' \
-blockdev '{""node-name"":""libvirt-1-format"",""read-only"":false,""cache"":{""direct"":true,""no-flush"":false},""driver"":""qcow2"",""file"":""libvirt-1-storage"",""backing"":""libvirt-2-format""}' \
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=libvirt-1-format,id=virtio-disk0,bootindex=1,write-cache=on \
-netdev tap,fd=34,id=hostnet0 \
-device virtio-net-pci,host_mtu=1400,netdev=hostnet0,id=net0,mac=fa:16:3e:43:11:f4,bus=pci.0,addr=0x3 \
-add-fd set=2,fd=36 \
-chardev pty,id=charserial0,logfile=/dev/fdset/2,logappend=on \
-device isa-serial,chardev=charserial0,id=serial0 \
-vnc 0.0.0.0:0 \
-device cirrus-vga,id=video0,bus=pci.0,addr=0x2 \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 \
-object rng-random,id=objrng0,filename=/dev/urandom \
-device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x6 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg tim..."
1737636,2017-12-14 14:33:29 UTC,Sorry for the late reply. Managed to finish the drawing triggering this crash without the exact pattern fill.
1737636,2020-09-11 07:45:16 UTC,Closing because INVALID.
1737636,2017-12-11 23:27:41 UTC,Upon further testing a 600px/600px tile converted to a pattern fill also crashes with 2048% zooming.
1737636,2017-12-12 12:17:00 UTC,"crash not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06) (32 bit build)"
1737645,2018-08-21 15:10:01 UTC,"Then I assume you filed a bug report on bugs.kde.org so we can find out what went wrong and fix it, right? ;)"
1737645,2018-08-21 14:46:15 UTC,I added flatpack to plasma-discover and it bricked discover completely.
1737645,2018-02-02 00:52:57 UTC,"I am the non-technical user who tried to install a flatpak package and had it fail, and didn't know why. I assume this is the reason, so +1 from me on fixing it!"
1737645,2018-02-02 00:51:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737649,2017-12-12 01:18:26 UTC,"Oh, examining DuplicateSignature attachment I now realize the source of the issue. In my server I'm using redis as session storage for PHP and thus have disabled completely systemd service to cleanup php sessions on file."
1737664,2018-08-29 21:17:24 UTC,A few thoughts on this:
1737665,2017-12-13 01:08:25 UTC,Could you please add Information on Inkscape version and OS?
1737665,2017-12-13 06:15:48 UTC,I am using Inkscape 0.92  and Windows 10 for PC.
1737668,2017-12-20 18:02:27 UTC,Ok error i found is in this line
1737668,2017-12-20 15:10:28 UTC,"1. I am currently using scons to compile on ubuntu 16(as mentioned in the documentation) .
2. What does milestone means ?
3. The references mentioned above are for the constructors not their implementation."
1737668,2017-12-19 07:17:32 UTC,"Which IDE are you using on which OS?
Normally this should help you to navigate through the code.
Did you follow the wiki link above?
A quick fix would be to disable the iTunes feature if the user does not give a valid folder after the first pop up.
Something like a second pop up
""No ITumes library found. The iTunes feature will be disabled an can be reanabled in Library preferences'"
1737668,2017-12-18 18:10:30 UTC,"So thats what i wish to know, in which file have the functions being called ? Like in src/library/itunes/...... the object itunes is defined but where is it actually used ?"
1737668,2017-12-18 18:05:16 UTC,"Yes, and that popup needs to be shown at some point for the iTunes feature to work. The problem is that it is shown at a time when it is not expected and is likely to interrupt use of Mixxx."
1737668,2017-12-18 17:50:48 UTC,"As far as I have understood it, the issue states that an unwanted pop up flashes on screen as soon as we click on iTunes option . Correct ?"
1737668,2017-12-18 09:10:22 UTC,"I think you are misunderstanding the issue here. There is not an error occurring here. The problem is a usability issue. An unsuspecting user who clicks on the iTunes feature will have a dialog pop up and interrupt their use of Mixxx. Perhaps enabling the option to show the iTunes library in the preferences should require locating the iTunes library. Otherwise, if the user does not select a valid iTunes library location, the iTunes feature should not be shown in the library."
1737668,2017-12-18 08:58:17 UTC,Can someone please help me locate the functions called because it doesn't look like there is any error in definition ?
1737668,2017-12-14 20:17:58 UTC,"Cool, thank you very much."
1737668,2017-12-14 19:24:49 UTC,"i wish to pick this issue , need some help (new in community)"
1737668,2017-12-15 20:41:29 UTC,I think there is some duplication or non re-initialization of some statement due to which such error is occurring. Will post  as soon as i find it out .
1737671,2018-04-06 05:11:45 UTC,This is still a problem.
1737671,2018-07-05 05:45:37 UTC,So maybe it's caused by userspace... you can try older Ubuntu in http://old-releases.ubuntu.com
1737671,2018-07-04 14:42:13 UTC,"Apparently this isn't related to kernel anymore. Booting on an older kernel doesn't help. It used to before, but now it doesn't matter which kernel I boot on - the drive still isn't detected. :-("
1737671,2018-07-04 14:00:08 UTC,This change was made by a bot.
1737671,2018-07-04 13:56:51 UTC,"This bug appears to have returned sadly, in kernel 4.4.0-130"
1737671,2018-06-12 04:34:55 UTC,This issue appears to have been fixed now in kernel 4.4.0-128
1737671,2020-09-27 18:24:52 UTC,"I think I am also affected by this issue. Can I do any support/testing to find a solution?
My Blu-ray burner is not detecting Blu-ray discs any more. And only Blu-ray discs (tried several) are affected, DVD for example works fine."
1737671,2018-03-25 04:17:33 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1737671,2018-01-11 06:38:20 UTC,The problem still exists in kernel 4.4.0-109.
1737671,2018-01-10 05:57:05 UTC,The problem still exists in kernel 4.4.0-108.
1737671,2017-12-18 14:09:14 UTC,"Hi all,"
1737671,2017-12-15 17:39:52 UTC,"Hi Joseph,"
1737671,2017-12-12 21:00:14 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1737671,2017-12-12 07:30:08 UTC,This change was made by a bot.
1737671,2018-01-23 06:05:00 UTC,The problem still exists in kernel 4.4.0-112
1737675,2017-12-14 09:41:41 UTC,"Hi,"
1737675,2017-12-15 14:50:03 UTC,"Hi Badal,"
1737678,2017-12-14 09:49:36 UTC,"Hi,"
1737678,2018-01-02 14:30:31 UTC,I would like to mention there are other licensing issues - e.g.:
1737678,2018-03-12 11:18:36 UTC,3.18.3 still has these files.
1737692,2017-12-18 13:04:38 UTC,Versioned depends is:
1737692,2017-12-18 13:05:17 UTC,This is fixed in Queens and Pike.
1737702,2020-11-16 08:18:19 UTC,Zero crashes after 18.04 so consider it fixed.
1737702,2017-12-20 07:15:24 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/6beead7e96eaeffc4ef77511ca7b9e70982af8c0"
1737702,2017-12-12 09:26:10 UTC,"StacktraceTop:
 icaltimezone_get_utc_offset (zone=0x1, tt=0x7ffd708df390, is_daylight=0x0) at ./src/libical/icaltimezone.c:841
 icaltimezone_convert_time (tt=tt@entry=0x7ffd708df390, from_zone=from_zone@entry=0x1, to_zone=to_zone@entry=0x7feb6b8c4420 <utc_timezone>) at ./src/libical/icaltimezone.c:808
 icaltime_convert_to_zone (tt=..., zone=0x7feb6b8c4420 <utc_timezone>) at ./src/libical/icaltime.c:981
 icaltime_compare (a_in=..., b_in=...) at ./src/libical/icaltime.c:737
 cal_obj_remove_duplicates_and_invalid_dates (occs=<optimized out>) at ./src/calendar/libecal/e-cal-recur.c:2712"
1737702,2017-12-20 07:14:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737713,2018-02-18 07:06:07 UTC,"I have the same problem
enviroment: ubuntu 16.04, openstack/pike (installed by kolla source)"
1737713,2018-02-18 07:34:13 UTC,"for me helps next workaround
I use kolla containers
1. login to manila_share as root
# docker exec -it --user root manila_share bash
2. mount cephfs as manila user
mkdir /etc/manila/cephfs
mount -t ceph 1.2.3.4:6789:/ /etc/manila/cephfs -o name=manila,secret=XXX
3. chown
chown manila:manila /etc/manila/cephfs
umount /etc/manila/cephfs"
1737713,2018-06-19 10:36:20 UTC,I can confirm this issue on my side as well. The suggestion from Sergey works for me.
1737713,2018-06-19 11:05:00 UTC,Should this bug be assigned to kolla?  iiuc the issue appears to be one of permissions and ownership on a bind mount in a kolla container.  Or am I missing something?
1737713,2018-06-19 11:59:16 UTC,"Yes, it seems like mine was entirely related to kolla. Sorry for posting it here."
1737713,2018-06-19 12:24:27 UTC,"Thanks, Eugene!"
1737713,2019-03-12 12:40:39 UTC,This bug affects Kolla-Ansible:
1737715,2021-01-08 12:22:19 UTC,As it stands I think the fix for barbican is pretty trivial as only the actions use the old `from_state`. *But* the functional test coverage is so poor in the barbican charm that I would be reluctant to land the change without improving if first.
1737715,2018-05-18 09:19:26 UTC,Reactive charms are not (yet) broken so pushing down to a medium priority.
1737715,2020-07-23 06:41:44 UTC,A recent search shows that this has been overtaken by events.  No from_state present in the repo.
1737715,2020-07-23 06:43:12 UTC,A recent search shows that this has been overtaken by events.  No from_state present in the charm.
1737718,2017-12-18 04:29:33 UTC,"After I unsuspend I cannot connect to WiFi network, but if I remove the USB adapter, wait a few minutes, then plug it in again, I can select the WiFi network and the Adapter will successfully re-connect. That's my work-around for now. But the parallel Mint 17.3 xfce system doesn't require that I do anything except awaken from suspension (as it should be)."
1737737,2017-12-12 16:09:31 UTC,It looks like you have packages installed from some PPAs which are causing the failure to calculate the upgrade.
1737737,2017-12-16 01:06:54 UTC,Thank you for your answer Brian.
1737741,2017-12-12 15:36:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1737741,2017-12-14 09:26:00 UTC,The Bug has been filed upstream here
1737741,2019-01-16 22:24:18 UTC,Upstream is https://gitlab.gnome.org/GNOME/rhythmbox/issues/1618
1737750,2018-08-08 17:10:02 UTC,"As others report, this has now happened with two attempted updates to kernel 4.15.
In one case the updater reported errors as it tried to load the update but then improperly ignored the errors and the update - known to be wrong - was then finalized and grub was updated to use the known wrong files.
Why put out the error notification if it is then ignored?"
1737750,2018-09-06 21:04:07 UTC,"For those who wants to participate
Call For Testing: Ubuntu with nVIDIA graphic cards
https://discourse.ubuntu.com/t/call-for-testing-ubuntu-with-nvidia-graphic-cards/7774"
1737750,2018-08-22 02:51:53 UTC,I used nvidia-bug-report.sh to report this bug to nvidia. (I had to email to an address reported by the script.)
1737750,2018-08-21 20:18:05 UTC,"While it is true that nvidia dropped support for 304 ( and maybe 340) the existing level of 304 and 340 work fine, so why not include in 4.15 as is? 4.15 is a requirement for the latest Ubuntu and Linux Mint releases so this prevents otherwise good computers from upgrading.
Further if I upgrade my computer to a new graphics card, how to if that card will not be obsolete next year."
1737750,2018-08-21 18:10:21 UTC,Bugs of nvidia-340 have been marked as duplicate of this bug. Should they be separated?
1737750,2018-08-20 11:01:11 UTC,Is there a bug bounty somewhere that I can contribute to?
1737750,2018-08-21 15:52:14 UTC,"The problem here is that nvidia drop maintining 304.x, so they will not update the 304 driver with the kernel 4.15 standard. Currently there are some patches that fix the issue but in the future we don't know.
Remember that nvidia304 is propietary and thus w/o nvidia there is no much we can make but pinning the Kernel so it doesn't update to 4.15 or above."
1737750,2018-09-14 00:30:03 UTC,There is a chance for fixing this (nvidia-340) or it is a lost case?
1737750,2018-08-16 12:01:07 UTC,And again with today's updates. 8 months and still no fix. What a mess.
1737750,2018-08-08 23:31:00 UTC,"I thought the whole point of an LTS release is that nothing major breaks?
Really disappointing to do an apt-get update and break my laptop :(
I have a GeForce 310M and this is the only supported driver.
What is the likelihood that the patch from comment #2 will make it into the mainstream patch cycle for 16.04 repositories?"
1737750,2018-08-21 15:58:34 UTC,"Here is nvidia release info for the latest driver 304.137 released in 2017-9-19:
https://www.nvidia.com/Download/driverResults.aspx/123709/en-us
Last bullet in ""release highlights says:
""Removed support for checking for and downloading updated driver packages and precompiled kernel interfaces from nvidia-installer. This functionality was limited to unencrypted ftp and http, and was implemented using code that is no longer actively maintained."""
1737750,2018-09-24 03:12:45 UTC,With the attached patch nvidia-340.104 module may be build with both kernels linux-generic-hwe-16.04 4.15.0 and linux-generic 4.4.0
1737750,2020-04-02 06:13:18 UTC,"Hello,"
1737750,2018-10-01 21:52:47 UTC,I ran into this bug *again* with today's updates and STILL need to boot the 4.13 kernel to get into my system. Could someone *pretty please* apply the patches Max proposed? Thank you!
1737750,2018-10-23 07:24:06 UTC,"I'm done with this. Took out the nVidia card today, only to run into the same old performance problems (i.e. no smooth video playback) with the i915 driver (which were the initial reasons to switch to nVidia). Even without the card, I'm still running into this bug. Guess I have to manually remove the nVidia drivers as well. What a mess. AMD here I come."
1737750,2018-11-24 21:00:42 UTC,"@Andy Dufresne (adufray): thank you very much for the great description of how to apply Seth's patch, and of course, thank you very much Seth Forshee for providing the patch!"
1737750,2018-11-24 23:32:23 UTC,"... but do not upgrade to Ubuntu 18.10, as its XServer comes with a new ABI version that nvidia-304 refuses to work with, and ignoring ABI incompatibility screws up the display (at least with my Geforce Go 7600). I guess this won't be possible to patch without NVidia themselves releasing a new version of the driver (which they won't)."
1737750,2019-01-05 16:50:25 UTC,"3Wouter Depuydt, would the same work for 340.107-0ubuntu0.18.04.1? Doesn't apt report about broken dependencies later?"
1737750,2019-01-05 17:28:53 UTC,"Max, how does end user apply the patches?"
1737750,2019-01-13 06:00:46 UTC,nvidia-340 from bionic-updates seems to work with linux 4.18.0-13-generic installed as a dependency of package linux-generic-hwe-18.04. It didn't work with 4.15.0-43-generic last time I tried. Even with the newer kernel there is Bug #1811402.
1737750,2019-01-26 02:20:08 UTC,"Dear Seth, thanks for your incredible work."
1737750,2019-02-12 16:39:43 UTC,Word to the wise:
1737750,2019-03-26 15:31:14 UTC,"Seth thank you for the work you have done and are doing on this.  Andy of post 13, thank you for the walk through on your web site.   I was about to patch and install for my Geforce 7900 GS on Mint 19.1 using the 4.15.xxx kernel using Andy's guide, successfully."
1737750,2019-05-29 01:48:14 UTC,Hi.
1737750,2018-09-24 03:19:55 UTC,DKMS patch to compile nvidia-340.104 for 4.15 kernel that should be more convenient to read than debdiff. It is based on other sources mentioned in comments to this bug.
1737750,2018-08-05 11:45:16 UTC,"I've got same issue on Linux Mint 18.3 x86_64 (Ubuntu 16.04 based) with nvidia-340 ""340.104-0ubuntu0.16.04.1"", and for me very helps debdiff patch of Seth Forshee from this bug report: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1737751. I also forced to find and add another one patch for kernel 4.14, because it is not exist anymore in current nvidia-340 sources, but mentioned in Seth patch."
1737750,2018-10-29 19:24:21 UTC,"Hi dear Xenial ubuntu 16.04 LTS maintainers. You broke Nvidia drivers with hwe kernel 4.15. AS it is a LTE please stop wasting time on bug fixing and just import the debian strech stable packages that are fixed for kernel 4.15 and above. see:
https://metadata.ftp-master.debian.org/changelogs//non-free/n/nvidia-graphics-drivers-legacy-304xx/nvidia-graphics-drivers-legacy-304xx_304.137-0~deb8u1_changelog"
1737750,2018-07-27 14:03:53 UTC,"I've encountered this bug on the past TWO kernel updates of my Xubuntu 16.04.4 (now .5) system that uses an Nvidia card. Initially I found that falling back to the previous kernel was a satisfactory workaround. This morning, I tried using the ""Additional drivers"" system setting to change from the Nvidia driver to the noveau driver -- and that has worked perfectly so far. This might be a possible recommended solution. I had originally switched from noveau to the proprietary driver because noveau didn't work properly, but that was several years ago and it has obviously gotten much metter!"
1737750,2018-07-27 14:06:26 UTC,s/metter/better/!!!
1737750,2017-12-14 15:03:35 UTC,Note that I've compile tested the attached fix but don't have hardware to do run-time testing.
1737750,2018-02-23 04:04:33 UTC,"I can confirm Seth's findings, as well as the fact it functions."
1737750,2018-02-23 13:26:32 UTC,"It's been suggested that this driver should be removed as it's not longer maintained (bug 1748000), so I'm not sure what the fate of this patch will be."
1737750,2018-03-07 04:58:04 UTC,"it is maintained by nvidia, i submitted a report to them ."
1737750,2018-03-07 05:35:16 UTC,build reject for this patch in the driver
1737750,2018-03-07 05:36:31 UTC,"thank you google and duck duck gogo, i found the patch instructions here"
1737750,2018-04-13 17:56:05 UTC,Could a ppa be created for the easy distribution of the patched version?
1737750,2018-04-13 19:36:26 UTC,I'd love to have it too. It controlled the heating on my laptop better than any other version.
1737750,2018-05-10 21:46:34 UTC,Could some friendly soul provide instructions on how to apply the patch from comment #2 ?
1737750,2018-05-28 02:13:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737750,2018-06-03 02:19:19 UTC,"@jfrantzius and others, I wrote a quick blog post to document the steps required to apply Seth's wonderful patch:"
1737750,2018-06-03 18:42:23 UTC,I really appreciate your doing this.  I am trying it right now and the patch process just stops.  I looked at the combined patch file and it seems to end with an unterminated left parenthesis.  Does the file end prematurely?
1737750,2018-06-04 19:51:19 UTC,With offline help from @audfray I got this to work.  Really appreciate the help.
1737750,2018-06-04 15:53:49 UTC,"When you say the patch process just stops, does it print out any kind of message? The patch should end with this line, which is just contextual information:"
1737750,2018-06-03 18:46:39 UTC,"And, the build process failed with Unable to build the NVIDIA kernel module.  Sigh."
1737750,2018-07-03 12:02:32 UTC,"So even while this bug has been known to exist for more than half a year, it still managed to slip into the automatic updates of an LTS (16.04) release: https://bugs.launchpad.net/bugs/1779687"
1737750,2018-07-03 22:16:08 UTC,How to solve this? Is anyone working on it? Is it enough do downgrade the kernel?
1737750,2018-07-03 22:36:55 UTC,Patch and compile the driver as explained in the link from comment #13
1737750,2018-07-04 08:37:03 UTC,"Downgrading the kernel is sufficient too, aka if you boot with kernel version 4.13.0 through GRUB, and then remove everything related to 4.15.0, the driver will work fine."
1737750,2018-07-06 22:18:33 UTC,"I was hoping this would have been fixed with today's updates, as the xorg update mentioned something in the terms of 'prevent nvidia regression'. But alas, still need to manually boot kernel 4.13 to get beyond lightdm."
1737750,2018-07-20 22:37:37 UTC,"I think this bug describes my failure. I am using Linux Mint Cinnamon 18.3 w NVIDIA-340.104
Using the latest kernel at the time, 4.15.0-24 cinnamon crashes at boot. Also with 4.15.0-20, the kernel that comes with LM 19 and Ubuntu 18.04 I understand. I just tried the new 4.15.0-29 and have the same failure. I get a message in xorg.log that the nvidia driver failed to load, see the syslog for more error messages, but I find nothing there."
1737750,2018-07-20 23:06:46 UTC,"Not an authority, but I don't think it will be fixed. Patch and compile the driver as explained in the link from comment #13 and then use any kernel you like."
1737750,2018-07-22 05:33:58 UTC,"This bug started to show up in Xenial with linux-generic-hwe-16.04, and not just linux-generic-hwe-16.04-edge, as the former was updated to version 4.15.0.29.51 in xenial-security:"
1737750,2018-07-22 19:37:16 UTC,"I have hardware (nVidia GeForce 8400M GS) for a runtime test.
The card is supported upstream by the 340.x branch until 2019 [1].
The release notes of the latest released patch (340.107-0) seem to be mention that they resolved the problem [2].
The patch is available and packaged for Ubuntu, currently only for 18.10 ""Cosmic Cuttlefish"" [3]."
1737750,2018-07-24 10:12:29 UTC,"A 'backport' of ""nvidia-340_340.106-0ubuntu3_amd64.deb"" from Bionic should do the trick as this is fixed by NVidia in nvidia-340.106:
http://www.nvidia.com/Download/driverResults.aspx/130042/en-us
""Release Highlights: Fixed a compatibility problem between the nvidia.ko's Page Attribute Table (PAT) support and the kernel Page Table Isolation (PTI) patches."""
1737751,2017-12-14 15:32:34 UTC,Attaching update to fix dkms build with 4.15. I have compile tested this but lack hardware to do run-time testing.
1737752,2018-02-22 15:48:03 UTC,This bug was fixed in the package linux - 4.15.0-10.11
1737752,2018-01-15 16:39:33 UTC,I'm also getting this issue.
1737752,2018-01-15 17:39:35 UTC,"Never mind, I installed the driver manually via the .run file downloaded from  http://www.nvidia.com/Download/index.aspx?lang=en-us"
1737752,2017-12-14 19:05:31 UTC,Among other issues this is also failing to link because some of the dma-mapping api has now caused an indirect dependency on a GPL-only export. Adding a linux task for this issue.
1737752,2017-12-14 21:32:08 UTC,"Attaching an update to fix issues with 4.15, along with a fix for an issue that was missed when updating for 4.14. Note that the following kernel patch from the Ubuntu unstable tree is also needed in order to build with 4.15:"
1737761,2018-02-21 13:57:23 UTC,I've pushed the same fix into bionic pre-ZFS 0.7.0. So it's now fixed in bionic.
1737761,2017-12-12 13:34:01 UTC,Working on the fix right now for 4.15
1737761,2018-02-19 23:57:03 UTC,The SRU of this to Artful is waiting on the release of the fix for Bionic.
1737761,2018-02-20 03:57:23 UTC,The fix for Bionic is not required as Bionic will be using version 0.7.x of ZFS (userspace + kernel) once the 4.15 kernel is released.  I am working on a different 'reverse' compat fix for Bionic that will allow 0.7.x userspace of ZFS to support the older 0.6.x ZFS kernel driver.
1737761,2018-02-20 15:58:31 UTC,"Hello Seth, or anyone else affected,"
1737761,2018-02-20 15:59:51 UTC,"Hello Seth, or anyone else affected,"
1737761,2018-02-20 20:21:21 UTC,"Successfully tested with the ubuntu autotest ZFS regression tests (ubuntu_zfs_smoke_test, ubuntu_zfs_fstest, ubuntu_zfs_xfs_generic and ubuntu_zfs_stress)."
1737761,2018-02-21 15:21:50 UTC,This bug was fixed in the package zfs-linux - 0.6.5.11-1ubuntu6
1737761,2018-02-27 14:56:11 UTC,This bug was fixed in the package zfs-linux - 0.6.5.11-1ubuntu3.1
1737761,2018-02-27 14:56:16 UTC,"The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1737761,2018-03-01 23:58:58 UTC,This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu19
1737761,2018-04-05 13:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1737761,2018-04-23 09:21:59 UTC,This bug was fixed in the package linux - 4.13.0-39.44
1737762,2019-08-31 12:04:20 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1737762,2019-10-31 04:17:33 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1737763,2017-12-17 18:59:43 UTC,"It cant find the file named service_resources.yml in any of:
/etc/kolla, /etc/kolla-kubernetes, /usr/local/lib/python2.7/dist-packages/etc/kolla, /usr/local/lib/python2.7/dist-packages/etc/kolla-kubernetes"
1737764,2017-12-12 13:45:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527401"
1737764,2017-12-14 15:11:25 UTC,"Change abandoned by Yushiro FURUKAWA (<email address hidden>) on branch: master
Review: https://review.openstack.org/527401
Reason: move to https://review.openstack.org/#/c/524125/"
1737770,2017-12-12 14:37:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527416"
1737770,2017-12-14 15:11:11 UTC,"Change abandoned by Yushiro FURUKAWA (<email address hidden>) on branch: master
Review: https://review.openstack.org/527416
Reason: move to https://review.openstack.org/#/c/524125/"
1737771,2018-01-04 12:41:08 UTC,I can see why this happens - the private-address is only set when the -joined hook runs on the relation - https://github.com/openstack/charm-interface-bind-rndc/blob/master/requires.py#L30
1737771,2018-01-04 12:44:43 UTC,Note sure about #2 - the bind configuration files should be updated in the event that the IP address of the Designate DNS masters change - and bind should be restarted if that happens.
1737771,2017-12-12 14:37:25 UTC,"One more note is that after the upgrade when removing and re-adding the relation between designate and designate-bind applications the private-address of designate-bind units changes and thus, bind9 needs to be manually restarted on designate-bind units."
1737772,2017-12-12 22:30:42 UTC,"Reassigning to gnome-software, which should take care to not let the debconf frontend die while dpkg is still running."
1737772,2018-01-17 08:02:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737778,2020-04-14 05:06:15 UTC,"Nope, that's not valid. Browsers also don't render the file. That's because
Additional requirements apply in order for the ‘id’ attribute to be valid in XML documents, as defined in the specification for the relevant version of XML. A stand-alone SVG document uses XML 1.0 syntax [xml], which specifies that valid ‘id’ values are XML name tokens (https://www.w3.org/TR/SVG2/struct.html#Core.attrib) and https://www.w3.org/TR/xml/#NT-Name lists the allowed characters for the first and subsequent letters of an ID."
1737778,2020-05-06 21:16:18 UTC,Thank you very much for pointing me to the correct spec! I will follow this much more restrictive spec when generating SVG.
1737782,2017-12-12 15:52:56 UTC,"Here's the full testcase including:
- the .tex file used to create the pdf with pdflatex
- the MATLAB .m file used to create figure.tex
  with the ""matlab2tikz"" script"
1737784,2017-12-12 17:16:19 UTC,https://support.google.com/accounts/answer/6010255
1737784,2017-12-12 16:11:45 UTC,"I see, it's Google blocking access from Evolution because it is known to have security issues."
1737784,2017-12-12 16:12:01 UTC,"(unless Google is wrong, of course)"
1737795,2017-12-13 16:14:32 UTC,"There are several desktop icon bugs that were introduced in 18.3
1) Some of the system icons (i.e. computer, home, network, trash and mounted volumes) are overlaid on top of each other when you boot or log-in.
2) Pressing F5 (which is supposed to refresh the desktop) causes more of them to be overlaid on top of each other, until they all share the single icon position at the top left of the screen.
3) ""Align to grid"" now aligns to a much more compact grid, which is far less readable because it crams the icon descriptions into icon images.
Items 1 and 2 indicate that there wasn't even a modicum of testing before this new version was released. Item 3 indicates poor design and/or programming."
1737795,2017-12-13 16:18:01 UTC,"Also
4) Saving a (new) file to the desktop, which used to create an icon in the first OPEN position (left-to-right, top-to-bottom), now overlays the icon before the open position."
1737808,2020-06-23 20:14:49 UTC,This is no longer an issue in the experimental catalogue in 3.5 and so should be resolved long term when the current catalogue is replaced.
1737809,2017-12-14 10:57:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527933"
1737809,2018-07-31 02:13:10 UTC,"Change abandoned by Feilong Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/527933"
1737821,2019-09-19 11:56:59 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1737823,2017-12-12 20:45:18 UTC,This behavior also appears on Circulation > Check Out
1737826,2017-12-12 20:58:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737826,2017-12-12 23:55:02 UTC,*** This is an automated message ***
1737828,2017-12-19 09:12:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737830,2018-01-17 21:58:16 UTC,"sounds like valid bug.
thanks for detalied bug report."
1737831,2017-12-13 00:24:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1737831,2017-12-17 19:42:16 UTC,MTU size adjustment works with Kernel v4.14.7
1737831,2018-01-13 17:02:45 UTC,MTU size adjustment is not working with Kernel 4.13.0-26-generic #29~16.04.2-Ubuntu.
1737831,2019-10-04 04:25:45 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1737832,2017-12-13 04:52:30 UTC,"it would want to be a controller level facade, and thus ultimately implemented by JEM for JAAS.
As such the response probably also needs to include information about ultimately what controller the model is running."
1737846,2017-12-13 14:32:03 UTC,Don't consider this as a bash bug. It's a misunderstanding by myself of the pipeline operation.
1737856,2018-02-15 23:53:41 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1737856,2018-01-26 00:44:01 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1737856,2018-01-10 01:12:21 UTC,This issue was fixed in the openstack/nova 14.1.0 release.
1737856,2018-01-09 11:55:09 UTC,"Reviewed:  https://review.openstack.org/530982
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=808d36475103e373f1deb3344b6829ce68d6cdd5
Submitter: Zuul
Branch:    stable/newton"
1737856,2018-01-09 04:23:19 UTC,"Reviewed:  https://review.openstack.org/530981
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b00b2fe9be4394e7c9cf73c168d435a2333d12f6
Submitter: Zuul
Branch:    stable/ocata"
1737856,2018-01-05 19:23:52 UTC,"Reviewed:  https://review.openstack.org/530980
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=344029b94ad7ff4667403a851d33c3ddb4e97b4b
Submitter: Zuul
Branch:    stable/pike"
1737856,2018-01-03 17:39:19 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/530980"
1737856,2018-01-03 17:48:34 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/530981"
1737856,2017-12-14 01:17:46 UTC,"Reviewed:  https://review.openstack.org/527564
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1706e3989157f912bce99beb99c75216a064eb2d
Submitter: Zuul
Branch:    master"
1737856,2017-12-13 02:32:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527564"
1737856,2017-12-13 00:38:54 UTC,This code was introduced in https://review.openstack.org/#/c/356137/ in newton so we'd have to backport that far if we can before newton end of life.
1737856,2018-01-03 17:49:59 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/530982"
1737856,2018-05-02 12:04:31 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1737858,2017-12-13 11:29:38 UTC,"yes, I am using the image generated from sahara-image-elements but with below change in diskimage-create.sh:"
1737858,2017-12-13 09:13:47 UTC,This seems interesting: org.apache.hadoop.fs.swift.snative.SwiftNativeFileSystem not found
1737863,2020-07-15 05:13:12 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/741085"
1737863,2018-01-08 20:58:08 UTC,I suppose we could add a section to the administrator guides [0] that explains role inheritance and how it works. I don't see any documentation describing inheritance outside of the one query parameter in the API reference.
1737863,2017-12-13 20:51:31 UTC,"That makes sense I was only looking at the one under roles, and missed the detail down on the other one."
1737863,2017-12-13 11:47:12 UTC,"It is included here:
https://developer.openstack.org/api-ref/identity/v3/index.html#list-role-assignments"
1737863,2018-01-02 21:01:27 UTC,"Based on the first comment, is there anything to clarify in the documentation for this bug?"
1737866,2018-10-09 06:38:37 UTC,sucessfully to verify xenial-proposed/ocata/main 2.6.3-0ubuntu0.17.04.1~cloud0
1737866,2018-10-08 08:22:14 UTC,"This bug was fixed in the package openvswitch - 2.6.3-0ubuntu0.17.04.1~cloud0
---------------"
1737866,2018-10-08 10:48:15 UTC,This bug was fixed in the package openvswitch - 2.5.5-0ubuntu0.16.04.1
1737866,2018-10-08 12:24:56 UTC,The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1737866,2018-10-08 12:24:57 UTC,"This bug was fixed in the package openvswitch - 2.5.5-0ubuntu0.16.04.1~cloud0
---------------"
1737866,2018-10-09 06:33:31 UTC,Failed to verify trusty-proposed/mitaka/main 2.5.5-0ubuntu0.16.04.1~cloud0 since trusty doesn't use systemd as default
1737866,2018-10-15 13:56:23 UTC,I've moved mitaka back to Triaged since this is only fixed so far in the systemd init file.
1737866,2020-10-02 12:45:43 UTC,"Hello Xav, or anyone else affected,"
1737866,2018-10-15 13:59:22 UTC,"Re the trusty-mitaka failure, from comment in http://upstart.ubuntu.com/wiki/Stanzas#limit it looks like this should fix it - https://pastebin.ubuntu.com/p/PMmQTNQsxZ/"
1737866,2020-07-20 07:39:07 UTC,I've committed the trusty/mitaka nofiles fix for the upstart unit to the git repository for OVS.
1737866,2020-09-29 19:37:35 UTC,"Hello Xav, or anyone else affected,"
1737866,2020-09-30 01:18:59 UTC,"All autopkgtests for the newly accepted openvswitch (2.5.9-0ubuntu0.16.04.1) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:"
1737866,2018-10-08 08:22:13 UTC,The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1737866,2021-01-13 17:08:14 UTC,This bug was fixed in the package openvswitch - 2.5.9-0ubuntu0.16.04.2
1737866,2018-10-15 13:58:53 UTC,Note that this is fixed in xenial (mitaka) but not in trusty (mitaka) because trusty uses upstart.
1737866,2018-10-08 08:21:18 UTC,"This bug was fixed in the package openvswitch - 2.8.4-0ubuntu0.17.10.1
---------------"
1737866,2018-10-05 10:44:08 UTC,Regression testing for xenial + UCA/pike-proposed
1737866,2018-10-05 12:20:29 UTC,xenial + UCA/ocata-proposed
1737866,2017-12-13 09:59:49 UTC,This needs fixing in the systemd units for ovs; raising packaging tasks.
1737866,2017-12-29 15:13:57 UTC,"Hi, this is affecting a production environment running xenial+ocata. Could we have an ETA for the systemd config to land Xenial packages?"
1737866,2018-01-26 14:30:52 UTC,I've uploaded fixes to bionic; will do SRU's for Xenial->Artful once that's into the release pocket and the current 2.8.1 ovs stable release is through.
1737866,2018-10-08 08:21:16 UTC,The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1737866,2018-08-15 02:31:50 UTC,Any update on when we might land an SRU for Xenial?
1737866,2018-08-17 02:39:04 UTC,"Subscribed field-high because we have an active environment (more?) that are are affected by this using Xenial/Ocata, and we really need that SRU released."
1737866,2018-08-17 04:36:19 UTC,"As restarts of OVS are service impacting, I was holding off on uploading this fix until we had point releases for OVS - which we now do."
1737866,2018-02-02 17:07:02 UTC,This bug was fixed in the package openvswitch - 2.8.1-0ubuntu3
1737866,2018-08-22 08:38:13 UTC,uploaded to xenial for SRU team review
1737866,2018-09-12 12:49:51 UTC,"> Subscribed field-high because we have an active environment (more?) that are are affected by this using Xenial/Ocata, and we really need that SRU released.
"
1737866,2018-09-12 13:02:00 UTC,"Hello Xav, or anyone else affected,"
1737866,2018-09-19 10:16:56 UTC,"I have verified openvswitch-switch=2.5.5-0ubuntu0.16.04.1, it looks good to me."
1737866,2018-10-01 10:19:30 UTC,"Hello Xav, or anyone else affected,"
1737866,2018-10-02 10:25:57 UTC,looks like the upload to pike proposed didn't update this lp but it is defo there:
1737866,2018-08-22 08:34:16 UTC,"Hello Xav, or anyone else affected,"
1737874,2017-12-13 11:45:40 UTC,"Machine  State    DNS            Inst id  Series  AZ       Message
0        down     10.10.191.158  gqsre7   xenial  default  Deployed
0/lxd/0  pending                 pending  xenial           failed to start machine 0/lxd/0 (failed to bridge devices: bridge activaction error: bridge activation failed: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: "" (32-)/4 ""
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2
Bringing up bridged interfaces failed, see system logs and /etc/network/interfaces.new
RTNETLINK answers: File exists
), retrying in 10s (10 more attempts)
0/lxd/1  pending    pending  xenial    starting
0/lxd/2  pending    pending  xenial    failed to start machine 0/lxd/2 (failed to bridge devices: bridge activaction error: bridge activation failed: ifdown: interface intf0 not configured
RTNETLINK answers: File exists
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: "" (32-)/4 ""
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2
Bringing up bridged interfaces failed, see system logs and /etc/network/interfaces.new
RTNETLINK answers: File exists
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: "" (32-)/4 ""
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2
), retrying in 10s (10 more attempts)
0/lxd/3  pending                 pending  xenial           starting
0/lxd/4  pending                 pending  trusty           starting
1        down     10.10.191.159  b4gqkw   xenial  default  Deployed
1/lxd/0  pending                 pending  xenial           failed to start machine 1/lxd/0 (failed to bridge devices: bridge activaction error: bridge activation failed: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: "" (32-)/4 ""
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2
Bringing up bridged interfaces failed, see system logs and /etc/network/interfaces.new
RTNETLINK answers: File exists
), retrying in 10s (10 more attempts)
1/lxd/1  pending                 pending  xenial           starting
2        down     10.10.191.162  mb7rnt   xenial  default  Deployed
2/lxd/0  pending                 pending  xenial           starting
2/lxd/1  pending                 pending  xenial           starting
2/lxd/2  pending                 pending  xenial           starting
2/lxd/3  pending                 pending  xenial           failed to start machine 2/lxd/3 (failed to bridge devices: bridge activaction error: bridge activation failed: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: "" (32-)/4 ""
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2
Bringing up bridged interfaces failed, see system logs and /etc/network/interfaces.new
RTNETLINK answers: File exists
), retrying in 10s (10 more attempts)
2/lxd/4  pending                 pending  xenial           starting
3        down     10.10.191.161  tfswrn   xenial  default  Deployed
3/lxd/0  pending                 pending  xenial           starting
3/lxd/1  pending                 pending  xenial           starting
3/lxd/2  pending                ..."
1737879,2018-02-20 16:30:28 UTC,I'm sorry but what is the exact problem ? Is that because the instance unexpectedly crashed ?
1737882,2017-12-13 09:59:47 UTC,"Thanks for the bug report. Unfortunately the akita and spitz models are pretty much unmaintained these days, so if this is important to you you'll need to investigate the cause of the problem yourself, especially given that more recent kernels work."
1737890,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1737890,2017-12-13 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1737890,2018-01-22 19:13:51 UTC,This bug was fixed in the package linux-oem - 4.13.0-1017.18
1737890,2018-03-19 10:57:28 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1737890,2018-03-26 07:11:36 UTC,"Verified on OptiPlex 3060, BT works fine after suspend/resume."
1737896,2018-02-23 19:10:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737896,2018-02-23 19:12:22 UTC,"release I86
xubuntu 16.04"
1737943,2020-02-11 07:33:55 UTC,This issue has been fixed a long time ago. Unable to say which cycle though.
1737947,2017-12-13 12:12:53 UTC,Hey Mark!
1737947,2017-12-13 15:00:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527706"
1737947,2017-12-13 19:34:03 UTC,"Thanks for the reply Milan. The multithreading option might help to some extent - it would at least allow ironic's polling to succeed, even if the /continue API still blocks on the firewall config."
1737947,2017-12-14 10:43:08 UTC,"Change abandoned by Milan Kováčik (<email address hidden>) on branch: master
Review: https://review.openstack.org/527706"
1737950,2018-01-25 09:34:56 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2514
1737959,2017-12-13 12:03:01 UTC,I had pip installed `progressbar3` which was available in ~/.local/lib. snapcraft is a classic snaps and therefore was picking up the pip installed version which causes this issues. Removing the pip install progressbar3 resolves the issue.
1737960,2018-07-12 08:07:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737961,2017-12-13 12:28:47 UTC,"While these should perhaps not be tied together, keep in mind that the KiCad Library Convention (KLC), http://kicad-pcb.org/libraries/klc/ , states that all text sizes should be kept at 0.050"" (1.25mm). Bigger text size anyway tend to create problems with the standard pin spacing on a 100 mil (2.54mm) grid and is not approved. ""S3.2 - Text fields should use a common text size of 50mils""."
1737961,2017-12-13 13:55:38 UTC,"These are Library Conventions for KiCad library repository and should not be forced on libraries that are not supposed to be part of this repository.
There are different sets of requirements for EE drawings and some of them (like GOST) are completely different from KLC.
For example, GOST operates under 5mm pin spacing and uses common text sizes of 1.8, 2.5, 3.5, 5.0 (and more) millimeters."
1737961,2017-12-13 23:09:23 UTC,It must take some really big sheets for a 100-pin MCU project then.
1737961,2017-12-14 08:13:18 UTC,"Not really. You just brake MCU symbol into several pieces and place them on separate A3 pages.
Actually, it makes schematics generally easier to read."
1737961,2017-12-14 11:00:50 UTC,This is somewhat related to an older outstanding bug - https://bugs.launchpad.net/kicad/+bug/1095245
1737961,2017-12-14 13:00:40 UTC,"Err... I'm not sure.
I just want them to not be enormous xD"
1737965,2017-12-15 09:10:51 UTC,It seems a bug of LVM for Ubuntu 14.
1737968,2017-12-21 10:34:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737973,2018-02-08 16:01:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737975,2017-12-13 18:03:47 UTC,"Hello,"
1737975,2017-12-14 11:09:47 UTC,"Hi,"
1737975,2017-12-21 20:59:04 UTC,"Hello again,"
1737976,2019-11-23 00:48:15 UTC,"Not sure if that applies here, but ""fe80::a8bb:ccff:fedd:eeff"" is not a valid ipv6 address on this machine."
1737976,2020-09-23 13:56:47 UTC,released as of netplan 0.100
1737976,2020-08-28 08:12:58 UTC,I proposed a fix for this issue here: https://github.com/CanonicalLtd/netplan/pull/161
1737976,2018-06-14 22:52:20 UTC,"thats again bad news with netplan :(
really need this!"
1737976,2018-01-01 13:04:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1737981,2017-12-25 12:09:28 UTC,"Must be done for Queens, since this blocks upgrade."
1737981,2017-12-25 12:11:07 UTC,i.e. blocks bug 1712586 ( https://bugs.launchpad.net/dragonflow/+bug/1712586 )
1737981,2020-06-23 17:22:22 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/527716"
1737984,2017-12-13 14:36:01 UTC,"14:35 <rbasak> cpaelzer: thank you for the report. I'm not sure about hash-abi-break because a change to pristine-tar won't change the main imported commit graph, but a change to upstream/ might. So I'll tag it for now."
1737984,2018-01-06 07:05:24 UTC,I'll try and dig into this next week.
1737984,2018-01-08 19:34:56 UTC,I just did the following:
1737984,2020-04-08 14:11:11 UTC,"> I'm not sure about hash-abi-break because a change to pristine-tar won't change the main imported commit graph, but a change to upstream/ might. So I'll tag it for now.
"
1737985,2017-12-13 14:51:10 UTC,"Hi Robert,
Part of the issue here is that prefix and suffix are displaying by default. They can easily be removed using the column picker. I signed off on the code that added those fields, but I've been planning to remove them as defaults as part of my work on bug 1735808."
1737985,2017-12-13 15:27:32 UTC,"Kathy,"
1737987,2017-12-13 14:24:23 UTC,Log file attached
1737994,2018-08-30 17:50:50 UTC,Fixed in stable r18766 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18766>.
1737994,2018-07-13 18:50:32 UTC,r18731 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18731) is part of this bug's fix.
1737994,2018-08-31 00:27:10 UTC,This is now code-complete in Launchpad: we have the ability to make this change globally.  I'm not yet doing so because we'd like to have some kind of QA of the set of snaps that Launchpad builds (or at least a reasonable sample) to make sure that we aren't wildly regressing them by switching to the snap.
1737994,2018-03-23 23:15:10 UTC,"The initial work here seems OK, but this is only part of the fix; we still need to do more work to present the state in the UI and to roll it out by default."
1737994,2017-12-13 15:22:57 UTC,"<sergiusens> cjwatson btw, mind if we work on switching snapcraft to use the snap for lp buidlers?
<cjwatson> sergiusens: I don't mind, but how were you planning to go about it?
<cjwatson> it's a bit involved
<sergiusens> cjwatson oh, then step one would be to get an idea of how involved it is :-)
<sergiusens> I had the impression it would be more about testing that s/apt install snapcraft/snap install snapcraft --classic/ was working as expected on staging
<cjwatson> sergiusens: we need to make it be a switch, not just change it in the code (which is harder to roll back, harder to experiment with on particular snaps, etc.); and probably as part of the same chunk of work we need to add channel control
<cjwatson> sergiusens: which means it needs to be propagated down from the LP buildd-manager, and probably needs data model changes
<sergiusens> cjwatson up to LP or even build.snapcraft.io ?
<sergiusens> I'll write up the proposed set of steps on the forum
<cjwatson> sergiusens: not build.snapcraft.io IMO.  We can flip the switch eventually but it needs to be controlled
<cjwatson> sergiusens: IMO the steps are: (1) design data model in LP (possibly taking into account where core is installed from too, at least for the future?) (2) add option to snap build type in launchpad-buildd to cause it to install snapcraft as a snap (3) LP database migration to add whatever new columns we need (4) implement new data model and API changes in LP, and adjust the build args sent to builders (5) possible UI changes
<cjwatson> sergiusens: ordering is important because builders, DB migrations, LP code are all deployed independently so we need to ensure the right kind of compatibility"
1737994,2018-03-13 11:46:48 UTC,"2018-03-12 18:49:08,832 INFO    2209-83-1 applied just now in 0.0 seconds"
1737994,2018-03-12 19:08:59 UTC,r13808 in db-stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-stable/revision/13808) is part of this bug's fix.
1737994,2017-12-13 15:24:11 UTC,"Sergio, assigning this to you since you said you were planning to work on it.  Let us know if that turns out not to be viable."
1737994,2018-03-22 18:00:59 UTC,Fixed in stable r18579 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18579>.
1737995,2017-12-14 08:30:57 UTC,"Hi Sam,"
1737995,2017-12-14 22:25:50 UTC,The description is pulled into the page as the alt tag
1737995,2017-12-27 02:31:56 UTC,Option 2 sounds a bit more flexible as it would allow you to change the description if needed rather than always having to take the one that's in the files area.
1738000,2020-10-09 21:49:02 UTC,This was fixed with the related branch above and confirmed it is still fixed. Marking fix released.
1738001,2017-12-13 15:37:25 UTC,Deleting the rect in the mask and undoing applies the mask
1738021,2020-03-05 16:13:54 UTC,Commenting to add heat and subscribing
1738021,2020-01-16 23:07:32 UTC,"We use serial records for publications issued on regular basis. We also have serial or open entry records for graphic novels. When a hold is placed on the order record or monograph record as Tiffany mentions above, we also manually change the hold to a part level hold on the serial record and put it in the hold queue according to the date it was placed. The original hold is cancelled with a note explaining cancelled to help with fulfillment."
1738021,2020-01-16 16:37:02 UTC,"In the use case sited by Michele, I would make the holds for the 1st disc (or 1st volume of a print publication) since it is from acquisition."
1738021,2020-01-16 16:20:46 UTC,We don't currently do parts on AV items so I can't speak to DVDs. I'd guess you'd just do it on the first disk?
1738021,2019-05-23 18:18:15 UTC,Commenting to add more heat.  This issue keeps cropping up as we're using acquisitions and parts more and more.  It's very tedious to have to cancel and replace 20-30 holds over and over for on-order items because the library couldn't guess whether their holdings would be parted or not when they ordered it.
1738021,2020-01-15 21:18:10 UTC,"This seems like going from more specific to less specific types of holds would be easy.  Item level to title level, part level to title level."
1738025,2017-12-13 16:11:29 UTC,"StacktraceTop:
 g_str_hash (v=0x0) at ../../../../glib/ghash.c:1882
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x55f9f9785f60) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x55f9f9785f60, key=key@entry=0x0) at ../../../../glib/ghash.c:1153
 _g_daemon_vfs_mountspec_get_uri_scheme (spec=0x55f9f979b470) at gdaemonvfs.c:531
 g_daemon_file_has_uri_scheme (file=0x55f9fa2fe190, uri_scheme=0x7f1c4a041461 ""mms"") at gdaemonfile.c:136"
1738025,2017-12-14 02:38:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738025,2017-12-14 02:40:17 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/b6bdd53dfb82772c52f94ada5dd629fb48ba155e"
1738028,2018-04-18 18:38:55 UTC,Why is this not appropriate for 2.1.1? We haven't released it yet. :)
1738028,2018-03-24 09:06:33 UTC,"I have to free that up for now, because I cannot reproduce this."
1738028,2018-03-19 14:52:45 UTC,What is the status of this? It is marked as In Progress but there is no open pull request. Should we push it back to 2.2?
1738028,2018-01-17 17:48:58 UTC,Possible duplicate? https://bugs.launchpad.net/mixxx/+bug/1300664
1738028,2017-12-20 01:01:53 UTC,Default (long delay)
1738028,2017-12-20 00:15:30 UTC,"If this is latency-dependent, why does the CPU meter not indicate a problem? (Mine is very low in the green even while the problem manifests.)"
1738028,2017-12-20 00:27:30 UTC,Which engine clock do you use?
1738028,2017-12-16 12:38:36 UTC,"By doing a git bisect I was able to locate the cause of the buffer underflows in the networkclockref branch, i.e. https://github.com/mixxxdj/mixxx/pull/894."
1738028,2017-12-15 13:45:31 UTC,"I didn't notice any more drop outs at 10 ms:
https://github.com/mixxxdj/mixxx/pull/1415"
1738028,2017-12-14 06:44:03 UTC,Might the drop outs be caused by theses recent changes?
1738028,2017-12-14 06:16:09 UTC,I also noticed the following warnings and audible pauses in the sound just today:
1738028,2017-12-13 16:15:28 UTC,This usually indicates the latency is set too low.  Where do you have it?
1738028,2017-12-17 17:08:03 UTC,"Unfortunately I cannot confirm this. :-/
My Setup:"
1738030,2017-12-13 20:58:20 UTC,"@thumper Dead on! When '--bootstrap-constraints' is used, the constraints are only applied to the controller."
1738030,2017-12-13 20:44:57 UTC,"Based on the above, I'm marking this as invalid for MAAS."
1738030,2017-12-13 19:51:38 UTC,I *think* that the constraints set at bootstrap time do apply to the entire default model and the controller model.
1738030,2017-12-17 23:26:06 UTC,Online docs issue is tracked here: https://github.com/juju/docs/issues/2336.
1738030,2017-12-13 18:53:56 UTC,whats interesting here http://paste.ubuntu.com/26178307/
1738030,2017-12-13 17:53:51 UTC,"$ juju deploy ubuntu -n 9 --to zone=openstack-a,zone=openstack-b,zone=openstack-c
Located charm ""cs:ubuntu-10"".
Deploying charm ""cs:ubuntu-10""."
1738030,2017-12-13 16:42:18 UTC,"Hi James,"
1738030,2017-12-13 18:57:08 UTC,"correction, machine 7"
1738034,2018-07-23 15:58:07 UTC,"> You keep saying these random behaviors. But I am unable to
> reproduce any of them on 18.04 & 18.10. Can you explain, how to reproduce in a concise way?
"
1738034,2018-07-23 04:32:46 UTC,"> NOPE, because sometimes it does go back to normal without any action.
> Both becoming red and going back to normal are COMPLETELY UTTERLY RANDOM.
"
1738034,2018-07-22 11:01:32 UTC,"Oh, and by the way, often it does not even become red in the first place when some sound starts playing while the volume is muted."
1738034,2018-07-22 10:56:27 UTC,"> sound indicator couldn't possibly cover all scenarios why music has stopped playing
"
1738034,2018-07-22 10:52:21 UTC,"> That is expected behavior. It turns red only to notify user that volume is muted
"
1738034,2018-07-20 12:30:56 UTC,"Sorry for my deleted comment, since you said ""it's most likely THE issue with..."" I thought you were referring to some specific issue that you failed to mention. I assume you meant ""most likely AN issue with""."
1738034,2018-07-20 04:44:39 UTC,It's most likely the issue with icon-theme issue. For me it turns red or blue depending or icon-theme. See https://i.imgur.com/zWYqIrl.png
1738034,2018-06-11 10:36:34 UTC,"I don't know why the fuck this was changed to incomplete (leaving aside the idiotic policy of ""incomplete"" bugs automatically expiring)."
1738034,2018-06-11 04:17:26 UTC,[Expired for indicator-sound (Ubuntu) because there has been no activity for 60 days.]
1738034,2018-04-11 14:48:55 UTC,"The error is due to not having ""accountsservice-ubuntu-schema"". But I can't reproduce the error. Could be a issue with icon theme."
1738034,2018-07-20 19:58:07 UTC,"> The issue is that the icon doesn't go back to normal and REMAINS red when the sound is finished playing.
"
1738036,2018-08-03 06:17:05 UTC,"I have opened bash file of cherrytree
$sudo vim /usr/bin/cherrytree
Then modify
#!/usr/bin/python
to
#!/usr/bin/python2.7"
1738036,2017-12-18 13:36:26 UTC,"Corrected this by changing Sha-Bang on /usr/bin/cherrytree
-- #! /usr/bin/python
++ #! /usr/bin/python2.7"
1738036,2017-12-13 16:36:56 UTC,SEE ALSO: <https://bugs.launchpad.net/ubuntu/+source/wxglade/+bug/1738041>
1738036,2017-12-18 13:04:36 UTC,"BAHHH!  DEPENDS python:any (< 2.8), and I have set python3 as default python."
1738042,2018-08-05 20:25:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738046,2017-12-13 17:06:01 UTC,"Oh, additionally this is an Ubuntu specific package and not in Debian."
1738046,2017-12-13 17:23:43 UTC,"system-config-kickstart has no reverse dependencies. It is in main because it is listed in
supported-sysadmin-desktop in the platform seeds. It was added there in 2005 by cjwatson and Jeff Waugh (~jdub)."
1738046,2017-12-13 17:27:17 UTC,"The other two packages in supported-sysadmin-desktop aren't in Ubuntu any more either so I think we should just remove the supported-sysadmin-desktop file. (If we do want to keep system-config-kickstart in main, we can list it in the supported file in the ubuntu seed.)"
1738046,2017-12-13 20:11:18 UTC,Added Colin and Jeff so they can give feedback.  Worth keeping this? (In main?)
1738046,2018-01-22 19:39:35 UTC,I think it makes sense to just remove supported-sysadmin-desktop and not add this back to main.
1738046,2018-01-23 11:37:15 UTC,"cjwatson said ""I'd rather not remove it (I still hope to find some time to fix it up a bit), but it can be moved to universe"""
1738046,2018-01-23 15:51:56 UTC,I've gone ahead and dropped system-config-kickstart from the seed.
1738048,2019-10-10 10:18:22 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1738052,2017-12-14 11:34:29 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06), using the command:
inkscape a.svg b.svg -g --verb=EditSelectAll --verb=SelectionSimplify --verb=FileSave --verb=FileClose --verb=FileQuit"
1738058,2017-12-14 09:20:44 UTC,That sounds like a bug.
1738058,2018-04-30 17:54:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738063,2018-01-15 10:43:10 UTC,@corey.bryant actually I see in http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/mitaka_versions.html that 1.10-1~cloud0 was uploaded but it failed to build (and weirdly is reported as existing in -proposed even though it is not). I also note that the N/O/P builds are are in -staging but not -proposed.
1738063,2018-01-16 16:32:44 UTC,There was a hash mismatch in the cloud archive with ocata and pike having the same versions. That's been fixed and the packages are now syncing to proposed.
1738063,2018-01-15 10:35:05 UTC,@corey.bryant thanks I will test those today. Don't forget that we also need to make Trusty Mitaka UCA parity with Xenial (which has 1.10-1)
1738063,2018-10-01 13:39:27 UTC,Newton is end of life.
1738063,2018-01-18 18:25:27 UTC,swift-plugin-s3 1.10-1~cloud1 is available now in mitaka-proposed.
1738063,2017-12-15 19:53:01 UTC,"Reviewed:  https://review.openstack.org/528221
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=37cfb1c504f1dbde40ff619b654355352618c939
Submitter: Zuul
Branch:    stable/17.11"
1738063,2018-01-12 22:08:50 UTC,"Hi Edward,"
1738063,2017-12-15 09:25:14 UTC,"Reviewed:  https://review.openstack.org/527763
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=a256263c79236be8adc0ea5176c0e4512c5a135b
Submitter: Zuul
Branch:    master"
1738063,2017-12-14 13:01:47 UTC,Raising tasks for the UCA; Queens is already underway.
1738063,2017-12-13 21:21:37 UTC,And it seems that Trusty Mitaka UCA will also fall foul to this until the UCA packages are updated.
1738063,2017-12-13 21:20:09 UTC,And more issues... It seems that since Newton->Pike UCA do have newer deps such as python-keystonemiddleware it is not be (easily) possible to fix this properly for those versions. So I can and will fix for Kilo -> Mitaka but I will have to leave Newton -> Pike as they are for now and hopefully Queens will be released with working config.
1738063,2017-12-13 20:57:55 UTC,"Ok so there is an added issue here in that successive releases of ubuntu have newer versions of swift-plugin-s3 BUT the Ubuntu cloud archive does not (until Queens which has 1.12-1). So, I will need to modify my patch so that the same config is used until Queens and change at a later time for prior Xenial UCA releases should this ever get resolved."
1738063,2017-12-13 19:18:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527763"
1738063,2017-12-15 10:26:00 UTC,"Fix proposed to branch: stable/17.11
Review: https://review.openstack.org/528221"
1738065,2018-10-15 19:09:50 UTC,"I'm running Mint 19 in VirtualBox, and I have a 20 GB virtual disk. After several weeks, it stopped working and would only boot to tty1. It turns out that /dev/sda1 was 100% full, and /timeshift was using about 9.8 GB (half the disk). As soon as I deleted the snapshots, everything started working again (in fact, the login screen immediately appeared, even before I logged out tty1)."
1738065,2018-10-16 09:28:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738065,2018-10-16 09:28:13 UTC,"Timeshift is available for other distros (Ubuntu, Arch), so it'll probably affect them too."
1738065,2018-10-16 10:15:46 UTC,Bug communicated at Github's TimeShift project: https://github.com/teejee2008/timeshift/issues/332#issue-370534345
1738071,2017-12-14 01:05:03 UTC,ELT on a small list called a lot of times would still incur the cost of additional checks.
1738071,2017-12-13 21:11:20 UTC,"It's not easy to do efficiently, and this doesn't lead to an any unsafe situations."
1738071,2017-12-13 21:37:17 UTC,"This came up in mutation testing.  I'm mutating valid forms by randomly inserting fragments of other valid forms, looking for situations that would cause SB-INT:BUG to be thrown by the compiler, or the compiler to outright crash (the previous bug with ASH/etc. running out of memory came up this way too).   For this to work, errors should be catchable.  I can get around it here by using timeouts, so this is not critical, but in general I'd prefer all problem to show themselves quickly."
1738073,2018-02-14 09:38:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1738073,2018-02-14 20:14:23 UTC,"artful verification:
ubuntu@starbuck:~$ dmesg | grep xlp9xx
[   46.890471] ipmi_ssif: Trying SPMI-specified SSIF interface at i2c address 0x10, adapter xlp9xx-i2c, slave address 0x0"
1738073,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1738078,2020-01-10 05:58:24 UTC,"Hi, a MP for this bug is here:"
1738078,2018-04-20 16:09:23 UTC,This is particularly relevant when attempting to deploy to LXD containers.
1738083,2018-01-26 00:43:55 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1738083,2018-01-05 21:53:03 UTC,"Reviewed:  https://review.openstack.org/528094
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=66a7508728fc7cc9f221702b0fe511ddf7f378ab
Submitter: Zuul
Branch:    stable/pike"
1738083,2018-02-15 23:53:48 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1738083,2017-12-14 21:53:22 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/528094"
1738083,2017-12-14 02:24:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527836"
1738083,2017-12-14 21:48:23 UTC,"Reviewed:  https://review.openstack.org/527836
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c66ae65775bb9d885fac059847063fee70617bc5
Submitter: Zuul
Branch:    master"
1738083,2017-12-13 21:29:59 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22DBDeadlock%5C%22%20AND%20message%3A%5C%22u'INSERT%20INTO%20traits%5C%22%20AND%20tags%3A%5C%22screen-placement-api.txt%5C%22&from=7d
1738086,2017-12-15 21:59:48 UTC,"The error ""DatabaseError: no such table: moz_favicons"" was fixed today in Git commit fc8e1ddb17b96e9819bd545aec744cb57bfb1da0"
1738086,2017-12-16 02:33:32 UTC,"How long will it be, before seeing an updated version of Bleachbit for Mint to download?"
1738086,2017-12-16 02:34:23 UTC,"Sorry, forgot to say, not just download, but in the Download Manager in Mint to download?"
1738094,2018-02-15 23:53:45 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1738094,2018-01-31 12:52:21 UTC,"Reviewed:  https://review.openstack.org/528226
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=51660619c45f8afe0ea539bf88d5b1bcd60ac535
Submitter: Zuul
Branch:    stable/ocata"
1738094,2018-01-31 12:51:51 UTC,"Reviewed:  https://review.openstack.org/528225
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=922c95a03dd9c8a5500f37aa433f450647cd7bfb
Submitter: Zuul
Branch:    stable/pike"
1738094,2018-01-26 00:43:51 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1738094,2018-01-10 01:12:26 UTC,This issue was fixed in the openstack/nova 14.1.0 release.
1738094,2017-12-19 15:01:03 UTC,"Reviewed:  https://review.openstack.org/528338
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e4e7b8da563e1fe4c2713dad55788f5ba3a86057
Submitter: Zuul
Branch:    stable/newton"
1738094,2017-12-19 10:28:32 UTC,"Reviewed:  https://review.openstack.org/528332
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f0ff43c79c02689a118dc8100187c19b5c21238
Submitter: Zuul
Branch:    stable/ocata"
1738094,2017-12-15 18:41:16 UTC,"Reviewed:  https://review.openstack.org/528012
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=40d74339082fe0eb1ce9216e89cf6e65a39e6968
Submitter: Zuul
Branch:    master"
1738094,2017-12-15 16:49:48 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/528338"
1738094,2018-01-03 14:37:37 UTC,This issue was fixed in the openstack/nova 15.1.0 release.
1738094,2017-12-15 16:41:32 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/528330"
1738094,2017-12-14 15:03:53 UTC,Related patch: https://review.openstack.org/#/c/527799/
1738094,2017-12-15 16:44:08 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/528332"
1738094,2017-12-14 17:01:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528012"
1738094,2017-12-14 20:03:59 UTC,"Reviewed:  https://review.openstack.org/527799
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94fd36f0582c5dbcf2b9886da7c7bf986d3ad5d1
Submitter: Zuul
Branch:    master"
1738094,2017-12-15 10:32:41 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/528225"
1738094,2017-12-14 15:08:36 UTC,Introduced in newton:
1738094,2017-12-15 10:33:03 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/528226"
1738094,2017-12-15 10:42:54 UTC,"Related fix proposed to branch: stable/newton
Review: https://review.openstack.org/528228"
1738094,2017-12-15 16:28:42 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/528228"
1738094,2017-12-18 21:21:47 UTC,"Reviewed:  https://review.openstack.org/528330
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9adf97c0132c3e0d34bbb2e33b59c6e5b00bec57
Submitter: Zuul
Branch:    stable/pike"
1738097,2020-03-17 01:11:14 UTC,"Settings schema 'org.gnome.sensors-applet' is not installed. Not a gnome-panel problem, for some reason user had sensors applet without schema file."
1738098,2020-09-21 03:04:57 UTC,Thank you for reporting this bug to Ubuntu.
1738098,2020-11-20 04:19:27 UTC,[Expired for lxpanel (Ubuntu) because there has been no activity for 60 days.]
1738101,2017-12-14 00:19:55 UTC,"Small file which can not be edited in inkscape.
Delete the clone (bottom right), and the master's (left) line parameters can be editied again."
1738101,2020-01-06 20:58:36 UTC,"Closing because I can't replicate this in current master, neither with your file nor the steps given. You can't directly change the stroke style of a group, that is expected and has nothing to do with cloning."
1738106,2020-08-12 16:51:43 UTC,Confirmed on Ubuntu 20.04
1738106,2020-08-15 12:10:43 UTC,Yesterday I have migrated my laptop from Ubuntu 18.04 to Ubuntu 20.04. By default Ubuntu 18.04 does not have dark theme. Users wanted to have dark mode were required to install third party theme from third party web site. Now in Ubuntu 20.04 dark mode is there included in default installation. Users now don't need to do anything - see ubuntu_appearance_settings.png attachment.
1738106,2020-08-17 01:53:49 UTC,I think we might be able to check https://developer.gnome.org/gtk3/3.2/GtkSettings.html#GtkSettings--gtk-application-prefer-dark-theme to select better icons. Some of the upcoming GTK3 changes will also make it easier for custom themed icons to override the default icons.
1738123,2019-01-07 11:43:13 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/530867
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.
Feel free to restore it again if you want to pick up and continue the work."
1738123,2018-01-02 21:19:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530801"
1738123,2018-01-03 08:47:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530867"
1738123,2018-01-04 16:47:20 UTC,"@gnuoy: We just realized that even hacking in this update to the /etc/neutron/plugins/ml2/openvswitch_agent.ini file, it fixes ovs agent, but does not fix neutron-l3-agent."
1738123,2018-01-04 17:07:47 UTC,I'd probably just push the timeout value into the DEFAULT section of the neutron.conf file; if it applies to both n-ovs-agent and n-l3-agent thats fine.
1738123,2018-01-04 17:31:01 UTC,popping this into neutron.conf will affect outages for conf changes in additional services I'd rather not impacted.
1738123,2019-01-07 11:42:23 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/530801
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.
Feel free to restore it again if you want to pick up and continue the work."
1738123,2020-05-27 12:11:48 UTC,"I'd like to rekindle this and update it for the more modern neutron. The config in the description of this bug refers to the older OFAgent driver which has been replaced since Newton with the ""native"" driver and therefore the config needed is:"
1738128,2018-01-24 22:37:48 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1467
1738128,2017-12-19 16:13:15 UTC,"Fix commited.
https://raw.githubusercontent.com/percona/percona-toolkit/3.0/bin/pt-query-digest"
1738133,2017-12-14 18:31:30 UTC,"when I contacted Adacore abot this issue, I got the following answer:"
1738133,2017-12-15 21:15:40 UTC,"For the record, I downloaded the tar.gz version from adacore website (http://mirrors.cdn.adacore.com/art/591c6d80c7a447af2deed1d7) and I don not experiment this problem with it."
1738133,2018-05-08 07:16:22 UTC,"This looks like a duplicate of an existing Debian bug.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810314"
1738135,2017-12-14 08:15:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527891"
1738135,2018-01-23 07:29:56 UTC,"Change abandoned by chao liu (<email address hidden>) on branch: master
Review: https://review.openstack.org/527891
Reason: The error message is handled by the ""try...catch"" statement"
1738135,2018-01-23 12:18:37 UTC,"The patch was abandoned, so let's clear the assignee."
1738135,2018-08-16 14:36:44 UTC,Same issue on queens :
1738152,2020-10-27 02:43:31 UTC,"That's correct, the suite might be failing with different cases on different releases.
And sometimes the test was not started because of the HW issue."
1738152,2019-11-12 19:31:24 UTC,"Hi Sam & Sean,"
1738152,2018-09-13 08:03:48 UTC,"This issue still exists:
http://10.246.72.4/test-results/4.4.0-136.162-generic/fozzie__4.4.0-136.162__2018-09-12_19-13-00/xfstests/results/xfstests.xfs/debug/xfstests.xfs.DEBUG.html"
1738152,2017-12-14 09:30:04 UTC,This change was made by a bot.
1738152,2018-09-12 18:45:52 UTC,"very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update."
1738156,2017-12-14 09:51:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738164,2019-03-26 19:22:31 UTC,"Thanks for uploading the fix for this bug report to -proposed.  However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process.  You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential.  Thanks in advance!"
1738164,2019-04-04 00:35:42 UTC,"Hello Olivier, or anyone else affected,"
1738164,2019-02-20 09:49:12 UTC,"@robert-ancell, I addition of this interface to the ubuntu-master, ubuntu-3-30, and ubuntu-3-28 branches as well as snap-store.  Can you please include this in your next round of SRUs for cosmic, bionic and xenial?  I wasn't sure which branch to use for xenial."
1738164,2019-04-04 04:14:48 UTC,Tested gnome-software 3.28.1-0ubuntu4.18.04.9 and the u2f-devices interface control is shown.
1738164,2019-02-19 09:32:53 UTC,"I'm not sure whether u2f being auto-connected is acceptable from a security standpoint, I'll ask Jamie and if it is, I'll request the auto-connection."
1738164,2019-02-15 19:01:54 UTC,This works now with core and chromium on the stable branches.
1738164,2019-01-29 17:35:31 UTC,I used your instructions to successfully authenticate with https://salsa.debian.org/ using the Chromium snap. Thanks! I believe my device is also a  Yubikey 4.
1738164,2019-02-20 09:29:03 UTC,Tentative request for auto-connection: https://forum.snapcraft.io/t/auto-connecting-the-u2f-devices-interface-for-the-chromium-snap/10052
1738164,2019-04-04 12:45:05 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu3
1738164,2019-01-29 15:36:49 UTC,"I've published revision 579 to the candidate channel with the u2f-devices plug.
To test this you will need to do the following:"
1738164,2019-04-11 08:09:16 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1738164,2019-04-25 13:57:12 UTC,"An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: ""Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.""."
1738164,2019-05-14 08:00:09 UTC,"Hello Olivier, or anyone else affected,"
1738164,2019-05-14 21:51:12 UTC,Tested gnome-software 3.20.5-0ubuntu0.16.04.12 and the u2f-devices interface control is shown.
1738164,2019-05-30 10:03:31 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.12
1738164,2019-10-31 17:17:21 UTC,"I'm still facing this problem. I just switched to 19.10 and the snap package has been installed. It does not work.
I tried to do the ""snap connect chromium:u2f-devices"" but this will not solve the problem."
1738164,2019-11-06 14:00:30 UTC,"Christoph, is your device a Yubikey? If not would you mind filing a new bug report with all the details by running `ubuntu-bug chromium-browser` ?"
1738164,2019-11-06 15:46:20 UTC,"Nevermind, I hadn't realized you had filed bug #1851211 already. Let's continue the discussion there."
1738164,2019-04-11 08:09:06 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.9
1738164,2019-01-28 06:32:22 UTC,https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=413294d8a3e7ce271fe050670ab99d43972ce6df
1738164,2019-01-28 06:29:18 UTC,"Jamie added a u2f-devices interface to snapd, and I successfully tested it with chromium and a YubiKey 4 (using https://demo.yubico.com/webauthn/registration)."
1738164,2018-12-01 01:40:45 UTC,This isn’t mentioned in the bug so thought I’d just document it here:
1738164,2018-05-16 10:34:09 UTC,It appears that apparmor is blocking u2f requests :
1738164,2018-05-16 11:17:35 UTC,It looks like the raw-usb interface might help here. I'll rebuild the snap with it and will post instructions on how to test.
1738164,2018-05-16 12:56:36 UTC,"@Chris: can you try the following, and report whether this addresses the issue:"
1738164,2018-05-18 11:15:05 UTC,It no longer throws an apparmor denied message but it doesn't work.....
1738164,2018-05-18 17:22:22 UTC,"Do you get more useful debug information if you run the snap with the ""--enable-logging=stderr"" parameter?"
1738164,2018-07-19 03:29:44 UTC,with chromium --enable-logging=stderr
1738164,2018-07-19 03:31:37 UTC,the proprietary google chrome does find the yubikey / gnubbie
1738164,2018-07-27 23:32:59 UTC,"I can confirm the bug is still present, tested with 67.0.3396.99 (367) and  68.0.3440.75 (383). I couldn't test with raw-usb as it seems this channel doesn't exist anymore."
1738164,2018-08-16 17:33:43 UTC,"I have the same issue, my Yubikey is the yibikey neo 4 model, it does support U2F. after installing Ubuntu 18.04.01 I followed yubico's instructions: https://support.yubico.com/support/solutions/articles/15000006449-using-your-u2f-yubikey-with-linux"
1738164,2018-08-08 09:26:35 UTC,"@Sami: I have re-opened the candidate/raw-usb-test channel and updated it to the latest stable release. Please test with the instructions in comment #3, run chromium with --enable-logging=stderr, and in another terminal window please run ""journalctl -f"" and share any relevant denials. Thanks!"
1738164,2018-08-20 10:05:13 UTC,"Thanks for the feedback Alejandro. So it looks like the raw-usb interface doesn't help indeed, what chromium needs read access to to access your key is the following:"
1738164,2018-08-20 10:09:56 UTC,I asked @jdstrand on the snapcraft forum: https://forum.snapcraft.io/t/fido-u2f-authentication-fails-in-chromium-snap-build/6130/4
1738164,2018-09-09 15:37:59 UTC,I am experiencing the same thing with both firefox and chromium snap packages.  Google Chrome install works perfectly. Really annoying to have to revert to .deb if there is a snap package available.
1738164,2018-09-19 10:13:03 UTC,We can add this to browser-support:
1738164,2018-09-19 10:15:47 UTC,The actual rules would be:
1738164,2018-09-19 10:50:31 UTC,"jdstrand, I've added those rules, and the denials go away, but I'm afraid it still doesn't work. There doesn't seem to be any denials, but it's like chrome just doesn't see it."
1738164,2018-10-25 09:56:35 UTC,"I'm testing with a brand new Yubikey 4, and after adding the rules in comment #16, I was seeing more denials which prompted me to add the following two rules:"
1738164,2018-10-25 10:00:43 UTC,Could the hidraw interface (https://github.com/snapcore/snapd/blob/master/interfaces/builtin/hidraw.go) be of any help here?
1738164,2018-08-16 17:40:23 UTC,Sorry forgot
1738165,2018-04-03 12:05:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738177,2018-01-11 09:26:32 UTC,I'm also encountered with this error and I might possibly find the cause. You can see bug #1742643 for more details.
1738182,2017-12-14 11:48:54 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1738182,2020-07-27 10:58:07 UTC,"Hi, thanks for the report."
1738183,2017-12-14 13:31:27 UTC,"Hi Andreas,"
1738183,2019-09-19 11:57:02 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1738188,2017-12-21 17:43:23 UTC,"Good catch, it would be nice to fix that."
1738192,2018-01-08 16:03:28 UTC,"Is this bug only about the warning or is something actual broken? From the code I assume the former, so setting priority to low."
1738192,2018-01-08 16:21:26 UTC,Thanks - it's only about the warning which could cause confusion. Nothing is broken.
1738194,2018-02-12 14:22:56 UTC,I just ran into this today:
1738195,2017-12-14 13:22:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/527956"
1738195,2018-01-28 11:08:25 UTC,"Reviewed:  https://review.openstack.org/527956
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=c3383413877f63f8423c4a73924fd6a3e07364ed
Submitter: Zuul
Branch:    master"
1738199,2018-05-08 17:47:33 UTC,"Huh?  syslog *is* copied there.  Or did you mean the systemd journal, which last I checked we don't even write to disk by default."
1738199,2017-12-14 21:51:44 UTC,"Yes, probably. Curtin copies its log to /root/curtin-install.log too, maybe that should be /var/log/installer/curtin-install.org too."
1738203,2017-12-14 13:23:29 UTC,"Small update, vncserver is started with:"
1738203,2018-01-29 13:51:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738203,2018-01-29 17:13:51 UTC,"Actually, i think i solved it:"
1738203,2018-08-22 15:10:45 UTC,Not a bug in Xfce.
1738207,2017-12-14 21:53:34 UTC,added KDE relevant information and Platform info
1738207,2017-12-15 15:40:40 UTC,idk -- the Xid error occus thru chromium so I will change it back to chromium ...
1738209,2017-12-14 14:32:00 UTC,"(Also note that these are very much active, as after submitting the bug:

> db.txns.find({""o"": []}).count()


6508
)"
1738209,2018-07-13 05:24:44 UTC,"@Richard Harding, John A Meinel,"
1738210,2017-12-21 14:33:46 UTC,cleanbuild test fix https://github.com/snapcore/snapcraft/pull/1807
1738210,2020-05-12 12:37:59 UTC,We alread build with --use-lxd on Travis
1738216,2020-07-28 13:40:37 UTC,I think we can safely close this - I have not had any time to work on it and probably won't for the foreseeable future.
1738216,2019-08-21 14:12:55 UTC,"Change abandoned by Donny Davis (<email address hidden>) on branch: master
Review: https://review.opendev.org/611977
Reason: This can be abandoned."
1738216,2018-10-19 22:42:36 UTC,Guess I will give this another go round
1738216,2017-12-14 14:50:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/527980"
1738216,2018-07-31 17:00:45 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.openstack.org/527980
Reason: Abandoning this patch per the TripleO Patch Abandonment guidelines (https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html). If you wish to have this restored and cannot do so yourself, please reach out via #tripleo on freenode or the OpenStack Dev mailing list."
1738216,2017-12-15 03:27:12 UTC,commit message fixed
1738216,2018-10-19 22:34:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611977"
1738219,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1738219,2018-04-03 07:08:22 UTC,"Since the Xenial backport was verified, setting the Artful one accordingly."
1738219,2018-03-19 11:23:21 UTC,I tested the proposed Kernel in Xenial and it is working for me
1738219,2018-03-19 10:57:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1738219,2018-03-19 10:56:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1738219,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1738219,2017-12-15 12:11:25 UTC,I tested the packages on Xenial:
1738219,2017-12-14 17:04:55 UTC,"I built Xenial, Zesty, Artful and Bionic test kernels, all with a cherry pick of commit bbfcd77631573ac4a9f57eb6169e04256a111bc1.  The test kernels can be downloaded from:"
1738219,2017-12-14 16:15:57 UTC,I tested now with Kernel 4.4.0-103-generic + the patch from commit bbfcd7 and it works for me
1738219,2017-12-14 15:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1738219,2017-12-15 15:09:39 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088930.html"
1738220,2018-01-18 20:23:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738226,2017-12-14 15:55:40 UTC,"StacktraceTop:
 strncpy (__len=4, __src=0x7f871800d930 ""{gv}\207\177"", __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106
 g_strndup (str=0x7f871800d930 ""{gv}\207\177"", n=4) at ../../../../glib/gstrfuncs.c:426
 g_variant_type_dup_string (type=type@entry=0x7f871800d930) at ../../../../glib/gvarianttype.c:446
 g_variant_type_info_get (type=type@entry=0x7f871800d930) at ../../../../glib/gvarianttypeinfo.c:741
 g_variant_alloc (trusted=1, serialised=0, type=0x7f871800d930) at ../../../../glib/gvariant-core.c:477"
1738226,2018-02-04 20:13:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738238,2017-12-14 17:09:48 UTC,Branch here: http://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/csharp/lp1738238_hatch_on_fedora
1738238,2019-05-22 21:35:04 UTC,"As is, this bug will be superseded by bug #1817932, which moves the Java/JavaFX dependency fetching to a script which puts the dependencies in the Hatch directory with a well-known name.  The script should be compatible across Linux flavors where 'curl' is installed."
1738238,2020-01-05 17:12:49 UTC,"FWIW, I confirmed on Fedora 31 that running the ""./fetch-deps.sh linux && ./hatch.sh compile"" method with the current version of Hatch works (as long as the branch for bug # 1858344 has been applied)."
1738238,2020-01-05 21:15:05 UTC,"Agreed.  Marked ""Won't Fix""."
1738243,2018-04-16 22:20:52 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.openstack.org/560138"
1738247,2017-12-14 17:43:07 UTC,Neutron Server Logs
1738251,2018-11-20 17:10:37 UTC,"I can reliably reproduce with LibreOffice 6.1.3.2 on disco.
This is a known upstream problem: https://bugs.documentfoundation.org/show_bug.cgi?id=98561."
1738251,2017-10-23 14:14:56 UTC,** Please read this message in its entirety before responding **
1738251,2016-03-09 17:16:37 UTC,Writer does not copy certain information from a webpage.
1738251,2016-03-09 19:10:24 UTC,Confirmed.
1738253,2019-10-18 06:25:28 UTC,"By chance this is fixed with the latest changes. In the 2.2 branch?
Can you restart?"
1738253,2019-09-22 15:02:24 UTC,"when I run with --developer I only see this when opening a controller script:
Warning [Engine]: underflowHappened code: 6
Warning [Engine]: underflowHappened code: 24"
1738253,2019-09-20 06:08:02 UTC,Is there something logged in mixxx.log when the  buffer underflow happens?
1738253,2019-09-19 23:43:27 UTC,"Edit
also happens when I open controller scripts in MyController > Scripts"
1738253,2018-10-23 20:31:57 UTC,"play/load state doesn't matter, or if a file in that folder is loaded/playing."
1738253,2018-10-22 15:45:27 UTC,"Does it matter if the file you open is playing / loaded in a deck, or can it be any file?"
1738253,2018-10-22 15:23:02 UTC,"still happens with Bionic and 4.16.18-rt12
2.3.0-alpha-pre (build master r6553)"
1738253,2018-03-30 15:49:11 UTC,"> Do you have any idea when this became an issue?
IIRC it appeared 2017-11/12.
"
1738253,2018-03-30 14:25:38 UTC,Tested on 4.15.12-301.fc27.x86_64 (and various other Fedora non-RT kernels)
1738253,2018-03-30 14:06:23 UTC,"Has anyone tried with a stock kernel? In any case, this sounds like a job for valgrind or something."
1738253,2018-03-30 12:28:23 UTC,This is with the realtime patched version of Linux from PlanetCCRMA (4.14.12-300.rt10.1.fc27.ccrma.x86_64+rt).
1738253,2018-03-30 12:00:31 UTC,@be does it happen with a regular kernel or did you try a PREEMPT RT one?
1738253,2018-03-30 11:11:08 UTC,"I can reproduce this. Does anyone have an idea what is going on? If we cannot fix this issue very soon, then I propose removing ""Open in File Browser"" from the track context menu. It is not an essential feature, just a nice thing to have."
1738253,2017-12-21 15:55:26 UTC,The underflows and drop outs doesn't seem to be caused by track or source related changes. We need to keep an eye on this issue during the beta.
1738253,2017-12-15 13:44:34 UTC,"Edit: Thread ""priority"" and not ""dependency"" inversion, of course ;)"
1738253,2017-12-15 13:42:07 UTC,https://github.com/mixxxdj/mixxx/pull/1415
1738253,2017-12-15 13:11:21 UTC,It turned out that both issues are not directly related. The main reason for the sluggish behaviour during batch analysis seems to be a dependency inversion between the analysis and the UI thread.
1738253,2017-12-15 09:50:38 UTC,Maybe related to https://bugs.launchpad.net/mixxx/+bug/1738227
1738253,2018-03-30 13:46:47 UTC,This happens with any kind of disk io activity. I often notice buffer underflows when using Mixxx to play background music while executing an rsync backup. Even when mirroring disks that neither contain the OS nor any music files or the library database.
1738253,2019-10-20 10:05:38 UTC,"I built 2.2 and with a moderate latency setting there's no underflow anymore with ""Open file in browser"" but it still happens when I attempt to open loaded script files from within Mixxx for the first time in a Mixxx session."
1738259,2018-01-22 19:16:44 UTC,This bug was fixed in the package linux-meta-lts-xenial - 4.4.0.111.95
1738259,2018-01-10 14:42:30 UTC,There are microcode packages available in the security team PPA here:
1738259,2018-01-10 14:22:07 UTC,"Intel released microcode updates https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File
I think all microcode-20180108.tgz needs critically fast SRU."
1738259,2018-09-15 03:53:53 UTC,This microcode forced update bricked my Samsung APU until I could flash the bios back using DOS to a clear flag state. This should be down-graded until better ucode tools are available. It fails on AMD-K1-1500 APU and AMD-A12 with Radeon ATI GPUs. I was forced to downgrade to x32-bit machine just to fix this. It also locks up the USB-ports making them unusable for reboot over USB. This leaves most users confused. (amd64 ucode 3.20180524.1) why is this update also on my Intel machines?
1738259,2018-07-31 08:09:09 UTC,+1 to @explorer09.
1738259,2018-07-02 23:14:07 UTC,"Look like my comment gets ignored.
In short: Please revert this and fix it properly. Don't let linux-image-generic package depend on amd64-microcode or intel-microcode! Change the relationship to ""Recommends"" instead!"
1738259,2018-06-14 12:16:31 UTC,This bug was fixed in the package linux-meta - 4.15.0.23.25
1738259,2018-06-12 16:55:06 UTC,"@sdeziel, I agree 100%."
1738259,2018-06-07 13:47:32 UTC,"@rlaager, for the VM case, considering that QEMU/KVM only supports a few watchdog devices, I think it would make sense to ship this i6300esb driver in linux-image-virtual directly."
1738259,2018-06-06 06:04:28 UTC,This is particularly annoying for me too.
1738259,2018-06-04 22:44:49 UTC,Agree with Explorer09. Why are my Intel systems now getting AMD microcode packages and why are my AMD systems getting Intel microcode packages?? This is a bug.
1738259,2018-05-26 00:25:30 UTC,"Um, excuse me. When I check the updates on my Ubuntu Trusty machine, I found out it now asks for new install of the amd64-microcode package. May I ask why? My CPU is not AMD's but Intel's, and it seems that amd64-microcode had no use for me. Why does the linux-image-generic package hard depend on it?"
1738259,2018-05-22 00:02:46 UTC,This bug was fixed in the package linux-meta-oem - 4.13.0.1028.33
1738259,2018-05-21 23:58:54 UTC,This bug was fixed in the package linux-meta-oem - 4.15.0.1006.8
1738259,2018-05-08 19:43:28 UTC,This bug was fixed in the package linux-meta - 4.13.0.41.44
1738259,2018-05-08 19:41:08 UTC,This bug was fixed in the package linux-meta-hwe - 4.13.0.41.60
1738259,2018-05-08 19:38:35 UTC,This bug was fixed in the package linux-meta - 4.4.0.124.130
1738259,2018-06-11 15:08:08 UTC,This bug was fixed in the package linux-meta - 4.15.0.23.25
1738259,2018-05-08 19:36:56 UTC,This bug was fixed in the package linux-meta - 3.13.0.147.157
1738259,2018-05-08 19:37:57 UTC,This bug was fixed in the package linux-meta-lts-xenial - 4.4.0.124.104
1738259,2018-01-09 20:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1738259,2018-01-22 19:09:13 UTC,This bug was fixed in the package linux-meta - 4.13.0.31.33
1738259,2018-01-22 19:09:39 UTC,This bug was fixed in the package linux-meta - 4.4.0.112.118
1738259,2018-01-22 19:10:25 UTC,This bug was fixed in the package linux-meta - 3.13.0.141.151
1738259,2018-01-25 16:42:01 UTC,This bug was fixed in the package linux-meta-hwe-edge - 4.13.0.31.33
1738259,2018-01-22 19:14:24 UTC,This bug was fixed in the package linux-meta-hwe - 4.13.0.31.51
1738259,2018-03-25 15:12:45 UTC,"How can this be marked as various ""Fix Released"" when the kernel depend was reverted??
Also note that ubuntu-drivers-common removed the micocode detection based on these so-called changes."
1738259,2018-03-25 15:37:46 UTC,Zesty EOL reached
1738259,2018-03-25 20:41:02 UTC,"Indeed, this was reverted and does not appear to have re-landed yet; resetting the bug state."
1738259,2018-04-20 12:24:20 UTC,"linux-meta-lts-xenial should be nominated for trusty, not xenial"
1738259,2018-05-07 14:58:12 UTC,This bug was fixed in the package linux-meta-hwe-edge - 4.15.0.20.42
1738259,2018-02-02 18:45:46 UTC,This bug was fixed in the package linux-meta - 4.13.0.32.34
1738263,2019-10-16 22:38:37 UTC,"So the latest Disco Kernel (Bionic HWE 5.0.0-31-generic) seems to have fixed all the issues with the touchpad. I can now touch the touchpad with all 5 fingers and it doesn't lock up and require me to restart the multitouch-hid module.
It also seems that this version of the kernel also fixed the keyboard issues where the brightness Fn keys work as well as the keyboard brightness, airplane mode and sleep mode."
1738263,2018-03-19 07:55:12 UTC,Thanks for your testing. So at least this is fixed in upstream kernel.
1738263,2019-05-09 07:52:02 UTC,"Luke, please test this kernel:
https://people.canonical.com/~khfeng/lp1738263/"
1738263,2019-05-03 06:07:47 UTC,I did figure out a way to start the touchpad to work again after I lock it up using 5 fingers to lock it up:
1738263,2019-05-03 05:30:43 UTC,"So I updated to Disco with the touchpad on the Asus GL702VD and for the most part, it works, I can right click and left click and use 2 fingers to scroll, however, while I tail the /var/log/syslog I get a bunch of the following errors that repeat, where with the 4.18 kernel these are suppressed:"
1738263,2018-03-15 23:53:58 UTC,"So, I read in a thread that someone was having something similar happen to them and they built the 4.14 kernel and this fixed the issue. I decided to pull and build the Bionic kernel from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic and install that on my Artful laptop and now everything appears to be working normal. The touchpad is fully responsive and working as it should.
I will continue to test throughout the weekend, but it looks like the current 4.15.0-10-generic kernel does fix the elan touchpad issue on the GL702VD."
1738263,2017-12-15 07:26:43 UTC,Looks like the guy is me.
1738263,2018-03-01 20:22:23 UTC,"Hello,"
1738263,2017-12-15 16:05:57 UTC,By the way the ID of this trackpad is: ELAN1200  04F3:3090
1738263,2017-12-14 20:43:47 UTC,"there is no need for logs because I checked them all and there is no clue about the cause.
ANYWAYS, a guy with the same problem on a simlar notebook solved by patching 2 kernel modules."
1738263,2017-12-14 19:00:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1738263,2018-03-02 05:00:18 UTC,"@Luke,"
1738266,2020-05-14 14:14:06 UTC,I'm expanding this bug to include more column labels in the same grid that would benefit from better names. These are:
1738266,2020-05-14 18:29:06 UTC,Related bug #1802169
1738274,2017-12-14 20:19:01 UTC,"Attaching second relevant UI screenshot,  The absence of an ""along guide g <id>"" option is noted."
1738274,2017-12-16 17:00:19 UTC,Agree that the CAD-like parametric placement would be handy.
1738274,2017-12-16 17:01:47 UTC,PS: no need to sign up for dropbox... click the no-thanks/view button.
1738281,2017-12-15 11:13:23 UTC,Just quick approve the revert commit
1738281,2017-12-15 10:45:50 UTC,A revert for the previous commit: https://review.openstack.org/#/c/528202
1738289,2018-03-19 08:39:40 UTC,Upstream bug report is here:
1738296,2017-12-17 21:02:36 UTC,Looks like they moved repo to github.  New links.
1738296,2018-04-24 19:58:27 UTC,This bug was fixed in the package meld - 3.18.0-6
1738297,2017-12-15 00:20:45 UTC,"Good/bad news, I can reproduce this issue. Steps:"
1738297,2017-12-15 19:38:41 UTC,Two additional findings:
1738297,2018-02-21 04:19:06 UTC,"Chris, thank you for all of the detailed information. It helps a lot for us to debug things."
1738297,2018-02-21 22:13:46 UTC,"Melanie, thanks for taking a look."
1738297,2018-04-11 20:00:58 UTC,Quick update: I've upgraded this cloud to Pike. Now seeing less concerning behavior.
1738297,2020-04-24 08:20:56 UTC,I'm happy the main root cause is fixed (deleting the source disks).
1738297,2020-04-24 08:22:20 UTC,Marking the bug status as WONTFIX since I don't want to consider this bug resolved by the Ussuri release.
1738316,2017-12-15 03:43:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/528153"
1738316,2019-06-06 21:45:12 UTC,"Change abandoned by Julia Kreger (<email address hidden>) on branch: master
Review: https://review.opendev.org/528153
Reason: Abandoning as this has not been updated in over a year."
1738317,2018-05-31 04:53:42 UTC,"Change abandoned by Kevin Zhao (<email address hidden>) on branch: master
Review: https://review.openstack.org/533604"
1738317,2018-01-31 01:39:17 UTC,"Change abandoned by Kevin Zhao (<email address hidden>) on branch: master
Review: https://review.openstack.org/533525"
1738317,2018-01-15 07:37:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533525"
1738317,2018-01-15 10:44:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533604"
1738319,2017-12-15 10:39:21 UTC,"This seems to be a Word-""feature"" (or a feature of any RTF capable application for that matter)."
1738319,2017-12-15 10:51:18 UTC,Interestingly behavior differs between Word 2016 (produces proper <tspan>s in a single <text> element) and Wordpad (produces individual <text> elements grouped together).
1738319,2017-12-15 11:40:14 UTC,"Thanks for that Eduard. I suspected something like this as I found another
website and was able to cut and paste pi as one long string eventually -
but then Inkscape failed to print - all I got was a blank page! It sems
I'll just have to avoid pi."
1738330,2020-04-18 10:50:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738330,2020-04-18 10:53:53 UTC,I have the same error with version 19.10 on VirtualBox 6.1.2
1738334,2018-02-14 23:37:55 UTC,"Hi,"
1738334,2018-03-15 02:26:24 UTC,This bug was fixed in the package linux - 4.15.0-12.13
1738334,2018-03-01 07:46:27 UTC,Call traces for this bug on D05 for kernel 4.15.0-10-generic which tested on 1 March 2018 on 18.04 daily build
1738334,2018-03-01 07:43:41 UTC,Hawei team just tested and verified this bug on 4.15.0-10-generic kernel on D05 server.
1738334,2018-03-01 02:24:01 UTC,"Hi Fred,"
1738334,2018-03-01 02:06:12 UTC,hi daniel
1738334,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1738334,2018-02-14 09:38:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1738334,2017-12-15 08:40:47 UTC,This patch need to merged and fixed for the release 16.04.04. The final SRU4 windows is 8 Dec. to 6 Jan 2018.
1738334,2018-01-23 00:46:01 UTC,I have talked to the kernel team about this and updated Fred off-line.
1738334,2018-01-22 12:01:50 UTC,"whether this patchset will merge into ubuntu 16.04.4 version or not? this patchset will important for our DO5 board, Can you check it please?"
1738334,2018-01-04 02:10:27 UTC,This patch have been accepted to be merged in in kernel V4.16. Please refer to:  https://lkml.org/lkml/2017/12/25/24
1738334,2017-12-15 08:42:57 UTC,Notes and some more detail for this bug/patch:
1738334,2018-01-23 01:04:04 UTC,"It is good to update to ""Fred"" (Xin Wei) off-line and thank you very much
for it."
1738334,2017-12-15 08:05:47 UTC,"Confirmed - the symptom is a kernel splat about ""Attempting to execute userspace memory"" triggered by Xorg with LR in ttm_bo_vm_fault - see attached screenshot (sorry!)"
1738334,2017-12-15 06:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1738335,2017-12-16 08:34:31 UTC,I was able to figure out with the sound.
1738335,2017-12-15 06:18:59 UTC,So i attached Sound Files for train.
1738337,2017-12-21 01:21:50 UTC,"i oslo have the same problem, in dvr envirentment, sometimes it will lost ovs flow for l2 pop on compute node"
1738337,2019-02-22 20:25:57 UTC,This could be a duplicate of https://bugs.launchpad.net/neutron/+bug/1813817 and https://bugs.launchpad.net/neutron/+bug/1716321.
1738337,2019-01-29 16:09:54 UTC,I am also observing this behavior. It occurs when attempting to live-migrate a handful of VM's in rapid succession to the same host. This quick and dirty script is able to make the issue appear:
1738337,2017-12-22 09:28:35 UTC,@Ann Taraday never use L3 HA
1738337,2017-12-22 09:05:16 UTC,">>3.use ml2/ovs, no special configuration
You use DVR as I see, do you use L3 HA as well? They are special configurations actually.
I still missing some information from the report:
You create a network and a vm  - then something happened (what do you notice?) and in logs there were these errors.
"
1738337,2017-12-22 03:15:11 UTC,"yes, I know the patch and it can fix the some problem. Now it never occur the following error logs when merged in September in our public cloud."
1738337,2017-12-22 02:12:53 UTC,"@Zachary Ma, it is caused by this patch:https://review.openstack.org/#/c/503517/"
1738337,2017-12-21 02:14:06 UTC,"@shihanzhang, we meet the same problem that it lost ovs flow for in dvr envirentment sometimes.
It is very bad for our china telecom public cloud.
Do you find the reason ?"
1738337,2017-12-19 09:21:54 UTC,it may be a potential bug
1738337,2018-01-03 12:42:33 UTC,"176302 2017-12-26 18:53:25.187 11925 DEBUG neutron.plugins.ml2.rpc [req-37d49036-2d6d-4548-9bed-2fa880fcd77a - - - - -] Update DVR po       rt a8f7751a-0564-4e11-9dc5-553b732c51a7 at host 10e131e78e34 status to active. update_port_status_to_active /usr/lib/python2.7       /site-packages/neutron/plugins/ml2/rpc.py:278
176303 2017-12-26 18:53:25.194 11921 DEBUG neutron.wsgi [-] (11921) accepted ('10.131.78.148', 60032) server /usr/lib/python2.7/site-       packages/eventlet/wsgi.py:883
176304 2017-12-26 18:53:25.196 11921 INFO neutron.wsgi [-] 10.131.78.148 ""OPTIONS / HTTP/1.0"" status: 200  len: 251 time: 0.0011199
176305 2017-12-26 18:53:25.228 11925 DEBUG neutron_lib.callbacks.manager [req-37d49036-2d6d-4548-9bed-2fa880fcd77a - - - - -] Notify        callbacks [] for port, before_update _notify_loop /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:167
176306 2017-12-26 18:53:25.238 11925 DEBUG neutron.plugins.ml2.plugin [req-37d49036-2d6d-4548-9bed-2fa880fcd77a - - - - -] The update       d value of port a8f7751a-0564-4e11-9dc5-553b732c51a7 is True. _update_individual_port_db_status /usr/lib/python2.7/site-packag       es/neutron/plugins/ml2/plugin.py:1759
176307 2017-12-26 18:53:25.425 11925 DEBUG neutron.db.api [req-37d49036-2d6d-4548-9bed-2fa880fcd77a - - - - -] Retry wrapper got retr       iable exception: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched. wrapped /usr/lib/       python2.7/site-packages/neutron/db/api.py:128
176308 2017-12-26 18:53:25.425 11925 DEBUG oslo_db.api [req-37d49036-2d6d-4548-9bed-2fa880fcd77a - - - - -] Performing DB retry for f       unction neutron.plugins.ml2.plugin.update_port_statuses wrapper /usr/lib/python2.7/site-packages/oslo_db/api.py:152
176309 2017-12-26 18:53:25.567 11925 DEBUG neutron_lib.callbacks.manager [req-37d49036-2d6d-4548-9bed-2fa880fcd77a - - - - -] Notify        callbacks [] for port, before_update _notify_loop /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:167
176310 2017-12-26 18:53:25.571 11925 DEBUG neutron.plugins.ml2.plugin [req-37d49036-2d6d-4548-9bed-2fa880fcd77a - - - - -] The update       d value of port a8f7751a-0564-4e11-9dc5-553b732c51a7 is False. _update_individual_port_db_status /usr/lib/python2.7/site-packa       ges/neutron/plugins/ml2/plugin.py:1759
176311 2017-12-26 18:53:25.817 11925 DEBUG neutron.plugins.ml2.db [req-37d49036-2d6d-4548-9bed-2fa880fcd77a - - - - -] For port a8f77       51a-0564-4e11-9dc5-553b732c51a7, host 10e131e78e34, got binding levels [<neutron.plugins.ml2.models.PortBindingLevel[object at        5d4f510] {port_id=u'a8f7751a-0564-4e11-9dc5-553b732c51a7', host=u'10e131e78e34', level=0, driver=u'openvswitch', segment_id=u       '4f9fde68-f2ce-43cc-bab3-097721affb3c'}>] get_binding_levels /usr/lib/python2.7/site-packages/neutron/plugins/ml2/db.py:106"
1738337,2017-12-19 06:21:08 UTC,"Then the second one fails because the revision_number does not match, because we use compare-and-swap mechanism."
1738337,2017-12-15 07:19:04 UTC,"[root@10e131e73e121 ~]# grep -rin ""standardattribute"" /var/log/neutron/server.log
83922:2017-12-15 10:07:05.128 65701 DEBUG neutron.db.api [req-fe4da6c8-763f-41fa-9dac-537863c11740 - - - - -] Retry wrapper got retriable exception: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched. wrapped /usr/lib/python2.7/site-packages/neutron/db/api.py:128
84013:2017-12-15 10:07:05.325 65703 DEBUG neutron.db.api [req-2632a1a7-f65e-45d9-be7b-ab4ce3c7372b - - - - -] Retry wrapper got retriable exception: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched. wrapped /usr/lib/python2.7/site-packages/neutron/db/api.py:128"
1738337,2017-12-15 08:17:47 UTC,"Can You provide some more details about:
* what You was doing when it happend?
* what version of OpenStack You are using?
* what Neutron configuration do You have?"
1738337,2017-12-19 03:36:52 UTC,@Slawek Kaplonski (slaweq)
1738337,2017-12-19 09:07:09 UTC,"[root@10e131e73e121 ~]# grep -rin ""standardattri"" /var/log/neutron/server.log
87580:2017-12-19 10:08:57.725 33834 DEBUG neutron.db.api [req-b6dec2c3-cc8a-4f0a-b8d8-aecac3d205c3 - - - - -] Retry wrapper got retriable exception: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched. wrapped /usr/lib/python2.7/site-packages/neutron/db/api.py:128
165658:2017-12-19 15:52:53.345 33832 DEBUG neutron.db.api [req-4846cd7b-94f2-4334-9324-df87a390d862 - - - - -] Retry wrapper got retriable exception: UPDATE statement on table 'standardattrbutes' expected to update 1 row(s); 0 were matched. wrapped /usr/lib/python2.7/site-packages/neutron/db/api.py:128"
1738337,2017-12-19 04:07:33 UTC,"Also, when I asked if you see anything actually failed, I am asking failures like being unable to create network."
1738337,2017-12-19 04:05:16 UTC,"Did you see anything fail?, i.e. can you still attach a network to the created VM and do ping?"
1738337,2017-12-19 05:47:08 UTC,"@Lujin Luo yes, I can still create network. Because @_retry_db_errors will try 10 times at most.
But I will occur the ""doesn't match"" log several days， and I wanna know you how to solve it?"
1738337,2017-12-19 06:13:27 UTC,"We still need to know after executing which commands, you started to see such error logs. Without knowing that, there is no way we can tell for sure. As I said, it may be a potential bug, or it may be what's expected as this is how we avoid race conditions."
1738340,2018-01-04 06:24:16 UTC,"I pushed a patch.
https://review.openstack.org/#/c/531081/"
1738372,2018-03-15 19:18:56 UTC,"Had an engineer run into this while using ocata devstack + heat, will look into further."
1738372,2018-02-16 11:43:56 UTC,This issue is preventing HEAT service is not being able to build for devstack-stable/ocata release. Hence only
1738372,2018-02-16 09:53:59 UTC,"Ubuntu 16.04.3 LTS, the latest supported version of oslo.polcy is 1.18.0."
1738372,2018-03-16 14:41:08 UTC,"I was able to duplicate this, it seems like there may be an issue with the heat devstack plugin, when running devstack (stable/ocata) it originally checks out stable/ocata heat, but once it hits the devstack plugin it will checkout master heat, and then hit:"
1738372,2018-02-05 18:59:30 UTC,2018-02-04 15:56:11.463 | ++/opt/stack/heat/devstack/lib/heat:init_heat:263 /usr/local/bin/heat-manage db_sync
1738372,2018-02-04 16:18:43 UTC,This error still exists in oslo.policy v1.18.0 while building devstack stable/ocata on ubuntu 16.04.3
1738372,2018-01-08 21:03:51 UTC,It looks like you're missing or have an old version of oslo.policy. The DocumentedRuleDefault object was added to oslo.policy in version 1.29.
1738372,2018-02-16 09:44:53 UTC,yes @Gage Hugo
1738382,2017-12-18 23:56:24 UTC,"Hello, this machine may have significant hardware issues. I don't know what to suggest but pay attention to the log entries as they are made, which hardware you're using at the moment, etc."
1738383,2018-01-20 07:45:00 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1489
1738400,2020-09-01 14:02:35 UTC,A backport of https://github.com/hashicorp/vagrant/pull/9338 could resolve this and allow bionic to launch Focal and later vagrant boxes.
1738400,2019-05-17 13:40:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738400,2021-01-09 14:50:35 UTC,A workaround is to download and install the deb file from https://www.vagrantup.com/downloads
1738400,2018-05-22 08:25:16 UTC,"Yes, right - thank you!"
1738400,2018-05-05 12:01:15 UTC,I have the same issue with 'ubuntu/bionic64' (v20180426.2.0) on MacOS 10.11 / Vagrant 1.9.8 / VirtualBox 5.1.30
1738400,2018-05-20 10:41:02 UTC,I've just checked v20180518.0.0 with the same result.
1738400,2018-05-21 12:42:55 UTC,I think those commands and files are no longer installed by default and it looks like vagrant is still trying ot use them.
1738400,2018-01-17 12:39:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738400,2018-04-19 18:04:20 UTC,Are you still seeing this today?
1738403,2017-12-15 13:00:49 UTC,It appears that this issue concerns all Linux bridges:
1738406,2019-05-20 19:37:32 UTC,"Out of curiosity, what is the status of this? I was hit with https://bugs.launchpad.net/tripleo/+bug/1692976 and had to start from scratch by deleting the .quickstart folder."
1738406,2019-09-04 20:38:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680177"
1738406,2020-07-03 09:04:06 UTC,"Change abandoned by Oliver Walsh (<email address hidden>) on branch: master
Review: https://review.opendev.org/680177"
1738410,2017-12-15 13:21:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738410,2018-01-24 10:06:15 UTC,"Thanks for your report. I cannot confirm on Ubuntu, the resolution is correct. Could you please attach a screenshot?"
1738410,2018-03-20 17:26:02 UTC,see screenshot
1738426,2017-12-28 20:27:53 UTC,"I don't know if this is in the direction of a solution but, adding the [nova] section with interface = admin changes the error to what is in the attached log. Commenting out the following lines in my cinder.conf returns the old error during migration."
1738426,2017-12-21 19:40:28 UTC,"Thank for providing that for me. I'll take a look at what I can accomplish with that. I look forward to seeing that extra documentation, if you can find it."
1738426,2017-12-15 19:13:28 UTC,"Check that you have the [nova] section in cinder.conf set right? From the log it appears this fails since we are unable to figure out where nova is, which is required in order to move a volume that is attached."
1738426,2017-12-18 14:03:30 UTC,The configuration file did not come with a [nova] section and I cant find a [nova] in any of the reference configuration files. Can you link to documentation on this section or provide an example configuration file that includes it?
1738426,2017-12-20 15:42:22 UTC,"I'm still looking for documentation describing it, but you can search for the [nova] section in the sample config to find the available options:"
1738428,2018-03-22 11:20:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738429,2017-12-15 15:24:50 UTC,"StacktraceTop:
 log_assert_failed_realm.constprop.207 (text=<optimized out>, file=<optimized out>, line=<optimized out>, func=<optimized out>, realm=LOG_REALM_SYSTEMD) at ../src/basic/log.c:809
 safe_close (fd=5) at ../src/basic/fd-util.c:77
 safe_close_pair (p=<optimized out>) at ../src/basic/fd-util.c:93
 manager_close_idle_pipe.lto_priv.894 (m=<optimized out>) at ../src/core/manager.c:343
 manager_free.part.18 (m=0x55b2a25fd170) at ../src/core/manager.c:1121"
1738429,2017-12-19 00:13:46 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1738434,2021-01-10 04:17:45 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1738434,2020-11-10 18:01:33 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1738436,2020-02-25 08:26:34 UTC,This has been fixed already.
1738436,2019-09-30 12:00:23 UTC,Is this still an issue?
1738436,2018-05-07 21:56:16 UTC,"I just re-tested this in MAAS 2.4. Using the ""Disable DHCP"" option on the VLAN being relayed disables DHCP relaying. This is by design, and I do not think it was any different on MAAS 2.3. Can you be more specific about the expected vs. actual steps and which details pages you were using when you saw this behavior?"
1738436,2019-04-03 13:23:59 UTC,Will be fixed in 2.6 UI changes
1738438,2017-12-17 17:32:48 UTC,You have inserted the start time as 10.45. This is a wrong format. You must insert it as 10:45.
1738438,2017-12-17 21:32:21 UTC,"Hi Carlo,  Thank you so much for your prompt reply and help. I do feel a
bit of a 'Donkey' now - I have been blaming Microsoft for their recent
update and the language has been quite descriptive!  and we will not
mention the several hours of trying to fathom it out.  How remiss and crass
stupid I am.  I will learn from that one.  Having said that - I have been
using MSTS since 2004 and Open Rails for about three years now.  I have
built three routes for MSTS/Open Rails which are still going and this is
the first time I have had to ask for help so I suppose I have not done too
bad."
1738439,2017-04-28 18:30:42 UTC,With version 1.2.1 there are no more tooltips displayed. Version 1.1.2 worked fine.
1738439,2017-05-23 08:29:42 UTC,"Filed a bug in GNOME's bug tracker about this, maybe they can fix it in Gtk3:"
1738439,2017-11-09 22:38:27 UTC,The workaround is to set the update the update interval > 0.5s for now
1738439,2017-12-23 21:15:54 UTC,Pushed this workaround in https://git.xfce.org/panel-plugins/xfce4-systemload-plugin/commit/?id=364956da514590ceac30c6443f1f421461bcdfa7
1738439,2018-11-29 16:53:11 UTC,*** Bug 14746 has been marked as a duplicate of this bug. ***
1738439,2018-11-29 17:30:12 UTC,The minimum might need to be bumped to 600 ms. 500 ms cuts a bit too close and doesn't work for me.
1738439,2018-11-29 17:45:38 UTC,Thank you very much!
1738459,2018-01-04 15:37:41 UTC,"TO-DO
update a ci-centos job to use a non-stack user and add validation to ensure the stack user is not created on the virthost."
1738459,2018-01-22 19:22:07 UTC,"I
Complications:
- cannot use current deployer's user when deploying on localhost (=$VIRTHOST), need to specify a different user as it gets removed and recreated:
    * e.g. if you deploy (run oooq) as 'deployer' user, you have to specify ssh_user and non_root_user as something else like 'user1'
    * This is mainly because of teardown (kills all processes for user and recreate the user) - WAD
- ssh_user and non_root_user are used interchangeably in the code
- {{ working_dir }} is interchangeably used as /home/{{ ssh_user }} or /home/{{ undercloud_user }} for two different purposes across oooq and oooq-e sources:
    * /home/{{ ssh_user }}: deployer user's home dir at $VIRTHOST
    * /home/{{ undercloud_user }}: undercloud user's home at undercloud machine"
1738459,2017-12-21 16:58:24 UTC,"                                                                                                                                                      │······························································
[stack@rdo-ci-fx2-02-s5 ~]$ ls /home/                                                                                                                 │······························································
stack  test1  test2  whayutin                                                                                                                         │······························································
[stack@rdo-ci-fx2-02-s5 ~]$  oooq launched as test1 and as test2, however vms are launched as stack?"
1738461,2017-12-15 18:01:30 UTC,Here is a workaround: https://github.com/snapcore/snapcraft/pull/1808
1738476,2017-12-19 03:21:52 UTC,Sounds like a typo in your nvidia driver:
1738476,2018-01-21 17:48:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738482,2018-11-07 12:21:17 UTC,"I have fixed this issue in my environment by using pexpect instead of the default paramiko backend, i.e.
pexpect+scp:// etc.
But it would be awefully nice if you fixed the paramiko backend!"
1738482,2018-11-07 12:22:21 UTC,"By the way, this is on Ubuntu 18.04.1, with duplicity 0.7.17"
1738482,2019-01-21 16:28:48 UTC,Try this:
1738482,2019-01-31 08:22:23 UTC,I have the same problem on a fresh ubuntu 18.04.
1738485,2019-09-16 18:21:20 UTC,Migrated to https://github.com/widelands/widelands/issues/1066
1738489,2020-05-11 20:17:21 UTC,"I'm pretty sure it's been resolved, but I don't recall by what. Certainly I've not seen it recently."
1738489,2020-05-11 20:04:21 UTC,"Is this still an issue, or was this resolved by updates to MAAS or Maniacs-setup?"
1738490,2018-01-02 02:50:05 UTC,That's because rootfs has systemd-backlight@.service to restore/save the brightness value. Probably a good idea to do the same for initramfs.
1738490,2017-12-20 21:01:57 UTC,"Unfortunately I can't test with the upstream kernel, as I'm using a ZFS root vol and the ZFS modules don't build against that kernel."
1738490,2017-12-15 22:00:06 UTC,This change was made by a bot.
1738490,2017-12-18 15:42:37 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1738497,2017-12-15 23:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1738497,2018-02-14 09:38:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1738497,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1738500,2020-03-31 13:04:38 UTC,I just hit this issue with an Ubuntu 20.04 daily build. I noticed it when I tried to split my Terminator shell. I used ibus-setup to change the emoji shortcut to something else.
1738500,2019-04-03 05:48:43 UTC,"Since it's related to workarounds people have suggested: tried to use ibus-setup like a lot of people have suggested, and got:"
1738500,2019-01-22 21:48:21 UTC,"> This is a very windows-ish solution, i.e. it can not be a part of an ""after intallation"" script, since I don't know how to do it from terminal by issueing a command.
"
1738500,2019-01-11 09:44:15 UTC,For everyone who wants a command line solution:
1738500,2019-01-05 03:10:17 UTC,I reported the gimp issue at https://gitlab.gnome.org/GNOME/gimp/issues/2137 and it's believed that Ctrl+Shift+E should work just fine for Export except when a text field is currently selected. So there shouldn't really be any interference.
1738500,2018-11-13 20:28:01 UTC,Also affects Hyper https://github.com/zeit/hyper began to experience when updated to 18.10
1738500,2018-10-21 22:16:31 UTC,"found it here: https://askubuntu.com/a/1039039/342747
Finally! Thank very much @jbicha!"
1738500,2018-10-21 22:11:09 UTC,@jbicha oh so this is an actual feature-not a bug? can it be turned off?
1738500,2018-10-20 23:49:17 UTC,@capaj
1738500,2018-10-20 22:46:10 UTC,"I have upgraded to 18.10 and I started getting an issue with CTRL+SHIFT+E. On 18.04 it worked just fine. Now when I use it input boxes and text areas across the whole system start acting weird-most of them will contain letter ""e"" as soon I focus them. The letter cannot be removed-not with backpace, not with a delete. This is madness!"
1738500,2018-09-21 09:20:29 UTC,"for reference if others hit the same issue:
```
* launch ibus-setup,
* select emoji tab,
* change the shortcut or remove it
```"
1738500,2018-09-01 13:53:38 UTC,"Who knows, which of the bionic packages provides this Emoji Choice, since that package is the presumable cause of this CONCEPTUAL BUG."
1738500,2018-09-01 14:00:56 UTC,I forwarded the gimp issue to https://gitlab.gnome.org/GNOME/gimp/issues/2137
1738500,2018-09-01 13:42:41 UTC,I just found a temporary work around:
1738500,2018-09-01 13:37:23 UTC,"Minor TYPO correction: accidentally I wrote ""Ctrl-Alt-e shortcut"", but naturally ""Ctrl-Shift-e shortcut"" is in question, at least in my ""bionic / gimp"" case (fresh install, no unreliable history)."
1738500,2018-09-01 13:17:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738500,2018-09-01 13:14:44 UTC,"I have exactly the same problem:  the important Ctrl-Alt-e shortcut is diverted to bring up a very childish ""Emoji Choice"" window, while in GIMP this Ctrl-Alt-e is frequently needed, since if we want to slightly alter a just scanned *.PNG file and save it back, than this is the OFFICIAL SHORTCUT of ""Export As ..."" menu item ""since the Big Bang"".  Who at all thinks that he or she is allowed to divert important shortcuts?  Where it can be configured back, preferably from a bash terminal?"
1738500,2017-12-21 23:32:44 UTC,"Yeah, the '@' symbol is a 'prompt' like when entering unicode you first see an underlined 'u'. I wasn't even getting the '@' because my 3.18 Gtk is too old for this feature. Apparently this shortcut they've hijacked is also an emacs command. My dilemma is; do I wait and see if the Gnome shortcut gets changed, or do I try and find an alternative now?"
1738500,2017-12-21 22:58:09 UTC,"Stephen,"
1738500,2017-12-21 22:54:19 UTC,"Stephen,"
1738500,2017-12-17 01:25:00 UTC,More info:
1738500,2017-12-17 01:14:10 UTC,"This may be why:
https://developer.gnome.org/gtk3/3.22/GtkIMContextSimple.html"
1738500,2020-06-15 17:17:02 UTC,https://askubuntu.com/questions/1046418/how-do-i-disable-emoji-input-in-ubuntu-mate-18-04
1738500,2018-09-21 09:08:23 UTC,"I have the same issue with vscode and terminator, many other apps also using crtl+shift+e"
1738501,2019-05-29 07:08:04 UTC,"No, that didn't help at the time.  I remember when there were a single slot left, I had to retry multiple times - eventually it did work."
1738501,2018-12-23 16:13:14 UTC,"Quick question here:  Does it solve the problem if you set a number that is lower or equal to the number of available computes that have available resources ?  IE: You have 6 computes with available resources and you use ""--max-count 6"" or ""--count 6"" ?"
1738507,2020-11-10 18:02:10 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1738507,2021-01-10 04:17:47 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1738516,2017-12-16 13:31:28 UTC,sorry.  I just used wrong cloud.yaml.  It works correctly for v1.9.0 now.
1738516,2018-06-13 07:02:00 UTC,"i got a similar problem, ""MountVolume.SetUp failed for volume ""mariadb-config"" : configmaps ""mariadb"" not found"", what did you mean about ""wrong cloud.yaml"" ?"
1738526,2018-01-01 11:00:42 UTC,So seems like you are hitting the following Percona-Server bug that PXC has inherited from PS.
1738526,2017-12-30 04:24:11 UTC,"2017-12-29T17:53:31.538067+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140290300778240 has waited at row0ins.cc line 2540 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7f9d9cec2810 created in file buf0buf.cc line 1456
a writer (thread id 140299334051584) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0sel.cc line 3519
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-29T17:53:31.538220+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140299701008128 has waited at row0ins.cc line 2540 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7f9d9cec2810 created in file buf0buf.cc line 1456
a writer (thread id 140299334051584) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0sel.cc line 3519
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-29T17:53:31.538257+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140288321341184 has waited at row0ins.cc line 2540 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7f9d9cec2810 created in file buf0buf.cc line 1456
a writer (thread id 140299334051584) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0sel.cc line 3519
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-29T17:53:31.538290+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140288658458368 has waited at row0sel.cc line 3519 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7f9d9cec2810 created in file buf0buf.cc line 1456
a writer (thread id 140299334051584) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0sel.cc line 3519
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-29T17:53:31.538322+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140288359913216 has waited at row0ins.cc line 2540 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7f9d9cec2810 created in file buf0buf.cc line 1456
a writer (thread id 140299334051584) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0sel.cc line 3519
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-29T17:53:31.538354+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140299689912064 has waited at ..."
1738526,2017-12-30 04:08:58 UTC,"@Krunal Bauskar
Thanks.
I had set innodb_thread_concurrecy=0.
My DB server crash again.
I reload The new error log when crashed."
1738526,2017-12-20 05:44:22 UTC,1. Can you re-run the test with innodb_thread_concurrecy=1 or default? Check the related issue here https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1722560.
1738526,2017-12-16 13:51:17 UTC,"--------
FILE I/O
--------
I/O thread 0 state: waiting for completed aio requests (insert buffer thread)
I/O thread 1 state: waiting for completed aio requests (log thread)
I/O thread 2 state: waiting for completed aio requests (read thread)
I/O thread 3 state: waiting for completed aio requests (read thread)
I/O thread 4 state: waiting for completed aio requests (read thread)
I/O thread 5 state: waiting for completed aio requests (read thread)
I/O thread 6 state: waiting for completed aio requests (read thread)
I/O thread 7 state: waiting for completed aio requests (read thread)
I/O thread 8 state: waiting for completed aio requests (read thread)
I/O thread 9 state: waiting for completed aio requests (read thread)
I/O thread 10 state: waiting for completed aio requests (write thread)
I/O thread 11 state: waiting for completed aio requests (write thread)
I/O thread 12 state: waiting for completed aio requests (write thread)
I/O thread 13 state: waiting for completed aio requests (write thread)
I/O thread 14 state: waiting for completed aio requests (write thread)
I/O thread 15 state: waiting for completed aio requests (write thread)
I/O thread 16 state: waiting for completed aio requests (write thread)
I/O thread 17 state: waiting for completed aio requests (write thread)
Pending normal aio reads: [0, 0, 0, 0, 0, 0, 0, 0] , aio writes: [0, 0, 0, 0, 0, 0, 0, 0] ,
 ibuf aio reads:, log i/o's:, sync i/o's:
Pending flushes (fsync) log: 0; buffer pool: 0
52951804 OS file reads, 524334224 OS file writes, 418517499 OS fsyncs
0.10 reads/s, 16384 avg bytes/read, 2.60 writes/s, 2.60 fsyncs/s
-------------------------------------
INSERT BUFFER AND ADAPTIVE HASH INDEX
-------------------------------------
Ibuf: size 1, free list len 23, seg size 25, 1641981 merges
merged operations:
 insert 1563573, delete mark 111936, delete 245
discarded operations:
 insert 0, delete mark 0, delete 0
Hash table size 13279583, node heap has 607 buffer(s)
Hash table size 13279583, node heap has 28998 buffer(s)
Hash table size 13279583, node heap has 24111 buffer(s)
Hash table size 13279583, node heap has 16608 buffer(s)
Hash table size 13279583, node heap has 353 buffer(s)
Hash table size 13279583, node heap has 95 buffer(s)
Hash table size 13279583, node heap has 2257 buffer(s)
Hash table size 13279583, node heap has 25195 buffer(s)
78987.75 hash searches/s, 1185.09 non-hash searches/s
---
LOG
---
Log sequence number 364038702679
Log flushed up to   364038702492
Pages flushed up to 363137869116
Last checkpoint at  363052510229
Max checkpoint age    5216728781
Checkpoint age target 5053706007
Modified age          900833563
Checkpoint age        986192450
0 pending log flushes, 0 pending chkp writes
328680730 log i/o's done, 2.60 log i/o's/second
----------------------
BUFFER POOL AND MEMORY
----------------------
Total large memory allocated 55889100800
Dictionary memory allocated 7103506
Internal hash tables (constant factor + variable factor)
    Adaptive hash index 2459228992      (849893312 + 1609335680)
    Page hash           6640792 (buffer pool 0 only)
    Dictionary cache    219576834       (212473328 + 7103506)
    File system         1178240         (812272 +..."
1738526,2018-01-18 08:20:26 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2021
1738526,2017-12-16 09:41:24 UTC,"Some of error log:
2017-12-16T14:38:33.715465+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140306330285824 has waited at row0sel.cc line 3519 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7fa47dece170 created in file buf0buf.cc line 1456
a writer (thread id 140306187093760) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0ins.cc line 2540
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/
BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-16T14:38:33.715616+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140318148892416 has waited at row0row.cc line 989 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7fa47dece170 created in file buf0buf.cc line 1456
a writer (thread id 140306187093760) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0ins.cc line 2540
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/
BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-16T14:38:33.715672+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140306241517312 has waited at row0sel.cc line 3519 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7fa47dece170 created in file buf0buf.cc line 1456
a writer (thread id 140306187093760) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0ins.cc line 2540
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/
BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-16T14:38:33.715745+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140316150900480 has waited at row0sel.cc line 3519 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7fa47dece170 created in file buf0buf.cc line 1456
a writer (thread id 140306187093760) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0ins.cc line 2540
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/
BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-16T14:38:33.715792+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140315453392640 has waited at row0sel.cc line 3519 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7fa47dece170 created in file buf0buf.cc line 1456
a writer (thread id 140306187093760) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0ins.cc line 2540
Last time write locked in file /mnt/workspace/percona-xtradb-cluster-5.7-redhat-binary/label/centos6-64/rpmbuild/
BUILD/Percona-XtraDB-Cluster-5.7.18-29.20/storage/innobase/include/mtr0mtr.ic line 153
2017-12-16T14:38:33.715838+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 1403154..."
1738526,2017-12-16 09:31:13 UTC,"mysql> show global status like 'wsrep%';
+----------------------------------+----------------------------------------------------+

| Variable_name                    | Value                                              |


+----------------------------------+----------------------------------------------------+

| wsrep_local_state_uuid           | 5c018094-5273-11e7-9d82-6a3ed29232e8               |
| wsrep_protocol_version           | 7                                                  |
| wsrep_last_committed             | 334670600                                          |
| wsrep_replicated                 | 1179227                                            |
| wsrep_replicated_bytes           | 698270839                                          |
| wsrep_repl_keys                  | 4480593                                            |
| wsrep_repl_keys_bytes            | 62966970                                           |
| wsrep_repl_data_bytes            | 559833341                                          |
| wsrep_repl_other_bytes           | 0                                                  |
| wsrep_received                   | 17969                                              |
| wsrep_received_bytes             | 143974                                             |
| wsrep_local_commits              | 1179227                                            |
| wsrep_local_cert_failures        | 0                                                  |
| wsrep_local_replays              | 0                                                  |
| wsrep_local_send_queue           | 0                                                  |
| wsrep_local_send_queue_max       | 14                                                 |
| wsrep_local_send_queue_min       | 0                                                  |
| wsrep_local_send_queue_avg       | 0.006466                                           |
| wsrep_local_recv_queue           | 0                                                  |
| wsrep_local_recv_queue_max       | 2                                                  |
| wsrep_local_recv_queue_min       | 0                                                  |
| wsrep_local_recv_queue_avg       | 0.000223                                           |
| wsrep_local_cached_downto        | 333491374                                          |
| wsrep_flow_control_paused_ns     | 0                                                  |
| wsrep_flow_control_paused        | 0.000000                                           |
| wsrep_flow_control_sent          | 0                                                  |
| wsrep_flow_control_recv          | 0                                                  |
| wsrep_flow_control_interval      | [ 141, 141 ]                                       |
| wsrep_flow_control_interval_low  | 141                                                |
| wsrep_flow_control_interval_high | 141                                                |
| wsrep_flow_control_status        | OFF                                                |
| wsrep_cert_deps_distance         | 56.274508                                          |
| wsrep_a...
"
1738526,2017-12-16 09:30:26 UTC,"DB version:mysqld --version
mysqld  Ver 5.7.18-15-57 for Linux on x86_64 (Percona XtraDB Cluster (GPL), Release rel15, Revision 7693d6e, WSREP version 29.20, wsrep_29.20)"
1738526,2017-12-16 09:13:53 UTC,"Hi,How to upload the error.log and trace file?"
1738526,2017-12-16 08:59:57 UTC,Percona XtraDB Cluster crash(2 nodes)
1738526,2017-12-16 13:44:36 UTC,"0 lock struct(s), heap size 1136, 0 row lock(s)
---TRANSACTION 551787966, ACTIVE 942 sec inserting, thread declared inside InnoDB 5000
mysql tables in use 1, locked 1
1 lock struct(s), heap size 1136, 0 row lock(s)
MySQL thread id 717917, OS thread handle 140315486152448, query id 3160890469 10.103.22.58 developer update
insert into pay_record(orderid,payamount,paystatus,paychannel,paytype,createtime,innerorderid,merchantid) values ('p1513406072466741022237',5.0,1,1,6,'2017-12-16 14:34:32','ed2c5258-c34f-4942-8192-5fd8b15f164b',102)
---TRANSACTION 551787961, ACTIVE 942 sec inserting, thread declared inside InnoDB 5000
mysql tables in use 1, locked 1
1 lock struct(s), heap size 1136, 0 row lock(s)
MySQL thread id 718615, OS thread handle 140306289600256, query id 3160889798 10.103.22.177 developer update
insert into pay_record(orderid,payamount,paystatus,paychannel,paytype,createtime,innerorderid,merchantid) values ('p1513406073232468181579',2.0,1,1,6,'2017-12-16 14:34:33','1e9fc20c-e366-40b6-bace-52bde7e04e38',102)
---TRANSACTION 551787948, ACTIVE 942 sec inserting, thread declared inside InnoDB 5000
mysql tables in use 1, locked 1
1 lock struct(s), heap size 1136, 0 row lock(s), undo log entries 1
MySQL thread id 718240, OS thread handle 140306187093760, query id 3160889454 10.103.22.176 developer update
insert into pay_record(orderid,payamount,paystatus,paychannel,paytype,createtime,innerorderid,merchantid) values ('p1513406071869846623684',4.0,1,1,6,'2017-12-16 14:34:31','dbe8a48a-8b24-4466-be2e-15588a09e37d',102)
--------
FILE I/O
--------"
1738529,2019-11-21 22:42:59 UTC,"Reviewed:  https://review.opendev.org/695447
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_trove/commit/?id=8330de8cb6163d9ef2250f3855c87cebc3d621ed
Submitter: Zuul
Branch:    stable/train"
1738529,2019-11-21 17:31:11 UTC,"Reviewed:  https://review.opendev.org/695448
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_trove/commit/?id=d9fed6ebe0c376d0420fa666403b4731af4a6de2
Submitter: Zuul
Branch:    stable/stein"
1738529,2019-11-21 14:32:29 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/695448"
1738529,2019-11-21 14:32:16 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/695447"
1738529,2019-11-21 14:26:23 UTC,"Reviewed:  https://review.opendev.org/694077
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_trove/commit/?id=04aa9a527ab50b6370db2a26459c355d55d67d3c
Submitter: Zuul
Branch:    master"
1738529,2019-11-13 14:03:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/694077"
1738529,2018-01-17 20:06:54 UTC,My installation also fails on the same step (os_trove : Get trove service net id) but in my case I see that it uses `external_vip_address` instead of `internal` for endpoint (as IP address above http://192.168.122.11:9696...) which is not reachable in my case.
1738529,2017-12-17 20:09:47 UTC,"I take my last comment back. I went through configuring networks and adding dbaas and also adding a flat network from openstack, and I still get the following error:"
1738529,2017-12-16 09:58:29 UTC,"Sorry, guys, I totally ignored this:
https://docs.openstack.org/openstack-ansible-os_trove/pike/configure-trove.html"
1738529,2018-06-26 19:05:22 UTC,"I got it to work by adding
endpoint_type: ""{{ trove_service_net_endpoint_type }}""
to the task:"
1738530,2017-12-19 00:45:33 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1738530,2017-12-19 01:00:07 UTC,This change was made by a bot.
1738534,2018-02-18 04:17:24 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1738534,2019-06-23 10:44:59 UTC,"This bug affects a lot of users including me , any fix ?"
1738534,2018-06-20 12:26:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738534,2017-12-19 09:11:54 UTC,"It may have been as early as the upgrade to 16.04.  I remember having some performance/overheating issues at that time so I disabled intel_pstate for a while; but I never fully diagnosed the issue.  The 17.10 install was a fresh install though, I wiped the system."
1738534,2017-12-16 12:00:07 UTC,This change was made by a bot.
1738534,2017-12-17 10:34:27 UTC,"As a workaround, I created a post-resume script that runs the above commands at /lib/systemd/system-sleep/throttle-workaround.  It works in the first scenario, but not if the full power cycle was done on battery power."
1738534,2017-12-16 11:48:32 UTC,"Just tried another scenario.  If I do the full power cycle while on battery power, then it boots up with turbo disabled and frequency locked.  This command then seems to work (cpupower then reports turbo is active/supported):"
1738534,2017-12-18 18:39:56 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1738536,2017-12-17 19:31:54 UTC,These kinds of bugs should have been in 1.4.2. Please upgrade and try again.
1738544,2019-01-21 22:22:26 UTC,"I have same problem
fresh install of Ubuntu 18.10 64bit with stock Gnome 3.30.1
using ClassicMenu Indicator v0.10.1 installed via Ubuntu app store with default settings
It makes the menu completely unusable if there are enough categories listed on main menu (only a few pixels of scrollable area are visible)."
1738545,2019-08-06 15:36:34 UTC,With current QEMU (and in particular with 4.1.0 rc3 or later with commit 5bfce0b74fbd5d5308 that fixes sigaltstack) go binaries work OK. I think we must have fixed this mmap issue  at some point between when this bug was reported and now (or possibly the go runtime was made a bit more forgiving of QEMU's eccentricities).
1738545,2019-08-06 16:33:01 UTC,"Oh, that's interesting. I will verify this and if it indeed works, I will enable Go binaries for sh4 in Debian."
1738545,2019-08-06 16:49:25 UTC,"I haven't tested sh4 specifically, but arm (subject of this bug report) definitely works, as does arm64."
1738545,2019-08-07 11:12:53 UTC,"I can confirm that the issue has been resolved on arm. Unfortunately, on sh4, the Go binaries are still crashing, albeit differently now. I verified that they work fine on real sh4 hardware."
1738545,2019-08-07 11:32:58 UTC,"Could you file a separate bug for the sh4 case, then, please (with repro instructions)?"
1738545,2019-08-16 05:08:49 UTC,"I'm marking this bug as ""fix released"" now since the Arm problem has been fixed. If there is something else to do for sh4, please open a new bug as suggested by Peter."
1738555,2019-09-17 09:48:34 UTC,Migrated to https://github.com/widelands/widelands/issues/1693
1738561,2017-12-16 20:16:36 UTC,The fix wasn't correct and crashed OR. Fixed correctly in x.4006.
1738561,2017-12-16 18:32:22 UTC,Fixed in x.4005.
1738564,2017-12-16 19:07:27 UTC,"On some machines I'm using a 'no change backport' from artfull:
 3.26.2-1~ubuntu16.04.1~c42.ppa1 from  ppa:dirk-computer42/c42-backport-gnome3"
1738564,2017-12-16 22:01:28 UTC,JournalErrors.txt has been deleted – see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738581
1738565,2018-01-05 20:56:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738566,2018-05-14 19:22:13 UTC,As mentioned above you can check it out at https://github.com/RedHatter/diodon-gnome-indicator and give us feedback how it works for you.
1738566,2018-05-14 05:32:01 UTC,What is the latest status of getting a Diodon icon up in Gnome Shell on Ubuntu 18.04?
1738566,2018-02-03 20:19:09 UTC,New diodon-gnome-indicator version using libdidodon directly. Note: requires the latest code from diodon master.
1738566,2018-01-28 18:38:14 UTC,"I was able to find a workaround for that first issue (though look at the comments, maybe we should consider moving to construct blocks in libdiodon?) but have run into another issue that is causing much more difficulty."
1738566,2018-01-27 21:36:25 UTC,"Unfortunately, Gjs is having trouble interfacing with libdiodon.so. When initializing a new class constructors are never called."
1738566,2018-01-27 12:54:42 UTC,As an explanation directly using ZeitgeistClipboardStorage works as it then connect to the D-Bus Service of Zeitgeist.
1738566,2018-01-27 04:36:19 UTC,Never mind. Using ZeitgeistClipboardStorage should work. The issues where due to the poor reading of the source.
1738566,2018-01-27 04:22:02 UTC,I originally had trouble accessing libdidon from Gjs but I've got that worked out now. Still one issue though. How do I access the Controller instance from libdiodon without being a plugin?
1738566,2018-01-22 19:41:46 UTC,Great!
1738566,2017-12-17 09:53:22 UTC,I am not able to reproduce this on my 17.10 machine. The icon appears as normal running version 1.7.0.
1738566,2017-12-27 19:56:56 UTC,Seems fixed to me. Maybe add a line to the -h help or the man page (or both).
1738566,2017-12-16 19:30:28 UTC,Have you already tried running newest version 1.7.0 which I have just released?
1738566,2017-12-17 07:26:55 UTC,"I tried it, but it makes no difference."
1738566,2017-12-18 06:50:07 UTC,"With Diodon running in one terminal, when I start another one in a 2nd
terminal, the diodon clipboard list pops up.
The menu bar shows 5 entries for Firefox, 2 entries for terminals, keyboard
language, clock & date, wifi, volume, and battery level.
There is nothing on the menu bar for Diodon."
1738566,2018-01-17 19:46:46 UTC,I made a GNOME Shell extension for Diodon a little while ago. Required a plugin to Diodon exposing the api as a DBus service.
1738566,2017-12-21 03:27:29 UTC,Yeah! It works again!
1738566,2017-12-19 19:30:04 UTC,It seems that you use classic Gnome and not the Ubuntu Gnome.
1738566,2017-12-21 03:29:16 UTC,Is there a way to detect this and warn the user?
1738566,2017-12-26 18:10:24 UTC,"I do not think so. Even if there wouldn't be a good spot to put such a warning, as there is basically no indication that Diodon is running."
1738572,2018-02-02 13:27:02 UTC,This also happens for me when I scale the font in GNOME 3 on Ubuntu 17.10.1.
1738572,2017-12-21 20:41:59 UTC,"I'm going to dive into the source next week and play around, see if I can get some more information or perhaps get it to work."
1738572,2017-12-21 20:28:06 UTC,"Note: This originated as a question <https://answers.launchpad.net/terminator/+question/661805> and as I already stated there, I don't have a clue with this one. So I'm throwing this out to the self-interest and knowledge of everyone else."
1738572,2017-12-16 20:25:08 UTC,The commands I use for changing the font DPI in XFCE are:
1738576,2017-12-17 09:43:15 UTC,"Hi Ankur,"
1738585,2017-12-16 23:31:32 UTC,Please add information on Inkscape version and OS used.
1738585,2020-09-13 18:29:35 UTC,Closing because INVALID: Can't replicate.
1738590,2017-12-17 00:43:57 UTC,"I tried briefly to implement this in https://github.com/mixxxdj/mixxx/pull/1254 but was not successful because I am not familiar with the master sync code. Daniel, would you like to implement this for 2.1? IMO there is no rush to do it and we can merge it after the beta release."
1738590,2017-12-20 03:24:56 UTC,"Owen, would you like to take this up after https://github.com/mixxxdj/mixxx/pull/1254 is merged?"
1738590,2018-08-18 23:20:09 UTC,This is a feature not a bugfix. I'll move it to 2.3.0
1738591,2021-01-12 21:51:47 UTC,"Should be fixed by https://code.launchpad.net/~dano6/podbird/podbird/+merge/387072
Let me know if not"
1738594,2020-01-06 11:12:56 UTC,"Hello,
4.10.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1738601,2020-02-19 09:00:41 UTC,"from 1863814
All banks use their own layout in CSV export - some have multiline headers and footers, some only have a sing-line header. Number of columns and their order is different as well as delimeters, date and number formats."
1738601,2019-04-20 21:42:26 UTC,https://github.com/profiler/HB_Convert
1738601,2019-03-02 08:31:06 UTC,"As we are here focused on CSV, I more think about some external mapping file to could be share and enable to map any csv format to HB fields."
1738614,2018-01-09 03:04:30 UTC,"While LXD may indeed have an issue, it is Juju's responsibility to make things work even against flakey substrates."
1738614,2019-06-19 09:31:37 UTC,So I'm running into this a lot with the new python-libjuju integration tests.
1738614,2018-09-04 14:33:18 UTC,"It looks like we've hit this in our CI
http://10.125.0.203:8080/job/nw-updateseries-amd64-lxd/428/console"
1738614,2018-06-04 16:16:14 UTC,What version of Juju and LXD?
1738614,2018-06-04 15:10:23 UTC,"I think I am hitting this bug, or at least a variant of it. I am trying my best to configure a lxd deployment that use directory backed storage. If I create 10 concurrent models, ~50% fail with:"
1738614,2018-01-11 02:41:23 UTC,Here's my understanding.
1738614,2018-01-09 01:51:06 UTC,Juju is not actually the culprit here. lxd is actually allowing the race conditions against its own internal sqlite database and its communication with lxc. An issue has been opened.
1738614,2018-01-05 00:29:28 UTC,See reference implementation: https://github.com/juju/juju/pull/8257
1738614,2018-01-03 03:57:38 UTC,"It might be good to note that a machine level mutex is probably not a solution here
and for a pair of reasons:"
1738614,2018-01-03 03:47:46 UTC,"Hello John,"
1738614,2017-12-19 04:43:57 UTC,I tried doing just 5 in parallel at the same time (rather than 10) and I still had about a 10% failure rate.
1738614,2017-12-17 10:18:30 UTC,"If I add the models 1 at a time, none fail. It seems to have something specifically to do with adding them in parallel."
1738614,2018-01-09 02:51:16 UTC,Marking as Invalid for 'juju' as per comment # 6. Please track the issue as per a linked github project.
1738622,2018-01-08 21:33:36 UTC,"Hi, Alvin."
1738622,2017-12-17 16:38:42 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1738622,2020-09-21 12:38:15 UTC,Closing because INVALID.
1738630,2018-08-18 19:47:52 UTC,I've run into the same problem.
1738630,2018-08-16 20:06:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738632,2017-12-18 17:49:24 UTC,"The patch was reverted upstream, so I'll do the same in bionic."
1738632,2017-12-17 15:16:36 UTC,"This looks to be due to a change in behavior regarding the hard RLIMIT_STACK value on setuid. Previously the hard limit of RLIM_INFINITY would have been preserved across the setuid exec, now it has been limited so that values greater than 8MB (including RLIM_INFINITY) are clamped down to that value. This is no doubt due to 04e35f4495dd ""exec: avoid RLIMIT_STACK races with prlimit()."" The test expects the hard limit to always be RLIM_INIFINITY."
1738632,2017-12-17 15:05:54 UTC,"  ======================================================================
  FAIL: test_02_stack_limit (__main__.KernelASLRCollisionsTest)
  Process stack is normal size
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File ""./test-kernel-aslr-collisions.py"", line 69, in test_02_stack_limit
      self.assertEqual(-1, stack[1])
  AssertionError: -1 != 8388608"
1738638,2017-12-17 16:22:38 UTC,This is just one example of how that can failure.  Very easy to generate other defective lambda lists that cause unhandled errors to be thrown.
1738638,2017-12-18 23:46:16 UTC,There are also problems with malformed MACROLET.  If those are not fixed with this ticket I'll open another one.
1738638,2020-12-13 17:36:00 UTC,fixed in https://sourceforge.net/p/sbcl/sbcl/ci/77038b9a9d068db532224f32c408ed8b65ae8a92/
1738653,2018-04-30 10:05:04 UTC,This issue was fixed in the openstack/heat 9.0.4 release.
1738653,2018-04-18 10:07:27 UTC,"Reviewed:  https://review.openstack.org/558826
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=3ac0bbedccb50e4e5b6bad663a872985d908e82a
Submitter: Zuul
Branch:    stable/pike"
1738653,2018-04-04 13:54:24 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/558826"
1738653,2018-03-26 21:57:05 UTC,"Reviewed:  https://review.openstack.org/543063
Committed: https://git.openstack.org/cgit/openstack/heat-tempest-plugin/commit/?id=2cff12bceb4b568cd8673c9ffa5668d37fcc9da9
Submitter: Zuul
Branch:    master"
1738653,2018-03-26 20:23:21 UTC,This is waaaay easier to debug now:
1738653,2018-08-13 15:25:58 UTC,This issue was fixed in the openstack/heat-tempest-plugin 0.2.0 release.
1738653,2018-02-12 08:25:50 UTC,"Change abandoned by Rabi Mishra (<email address hidden>) on branch: master
Review: https://review.openstack.org/531079"
1738653,2018-02-10 01:23:34 UTC,Fix: https://review.openstack.org/#/c/543063/
1738653,2018-02-10 01:20:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/543064"
1738653,2018-02-09 08:23:58 UTC,https://review.openstack.org/#/c/531079/
1738653,2018-02-23 17:59:16 UTC,"Reviewed:  https://review.openstack.org/543064
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=e4d2452f2f669e8c709cda5043c9ab67d40a4f2f
Submitter: Zuul
Branch:    master"
1738661,2017-12-18 08:53:37 UTC,Thanks for taking your time to report this and help making Ubuntu better.
1738661,2019-11-23 13:01:38 UTC,Looks like this is fixed now. The version in the Debian bug report got added to Ubuntu 18.04 in an update. I just tested with visualvm 1.4.2-2~18.04.1 and Java11 which starts without issues and seems to work as expected.
1738671,2018-05-24 00:55:42 UTC,Pushed fix in 1733995
1738675,2018-08-12 11:44:17 UTC,I fixed this bug in version 2.1.6 (git commit a73783d34fb09ba89df96c7c5b1e5d63fb3949b3).
1738675,2018-08-12 11:21:34 UTC,"I can confirm the crash with version 2.1.5 (18.04.1), but not with version 2.2.0 (18.10 daily)."
1738675,2018-08-11 20:36:29 UTC,*This previous testing was done in a Virtual Box virtual machine in 18.04.1 LTS with the latest updates.
1738675,2018-08-11 20:22:07 UTC,Yes.
1738675,2018-08-11 18:10:31 UTC,Is this crash reproducible with version 2.1.5?
1738675,2018-08-11 20:32:23 UTC,"I also did some more testing and found that just deleting a last search entry, where all others are deleted, would cause the program to crash."
1738676,2019-04-10 22:11:49 UTC,"I opened this issue against gnome-shell, upstream.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159"
1738676,2020-05-24 11:38:34 UTC,Still an issue in 20.04
1738676,2020-02-08 05:37:06 UTC,"With 18.04 LTS, if you login with flashback, the volume slider in the sound settings as well as the volume slider that drops down when clicking the speaker indicator behave backwards even when natural scrolling is off."
1738676,2019-04-11 00:38:36 UTC,"For reference, here are the upstream bugs:"
1738676,2019-04-11 00:34:33 UTC,This bug is still being tracked in bugzilla.
1738676,2019-01-28 15:04:40 UTC,Could someone report hat one upstream?
1738676,2018-08-07 01:57:22 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1738676,2018-08-08 03:07:02 UTC,"SCROLLED WINDOWS AND NATURAL SCROLLING
-----------------------------------------------------------"
1738676,2018-08-08 02:23:32 UTC,This issues is still present in Ubuntu 18.04.
1738676,2017-12-23 18:48:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738676,2017-12-18 13:48:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1738676,2019-01-26 03:07:53 UTC,Issues is still present in 18.10. (I do see that the cosmic and disco tags were added).
1738685,2018-03-20 21:28:03 UTC,The whitespace is there because the `git log` output prefixes commit messages with whitespace to format them nicely. Reading the manpage for git log I am not immediately finding any way to prevent it from doing that. When writing the commit message you should left align your Sem-Ver: api-break entries.
1738685,2018-03-20 21:55:40 UTC,Marking incomplete per Clark's request for more details.
1738685,2018-03-20 23:14:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/554730"
1738685,2018-04-03 23:55:32 UTC,"Reviewed:  https://review.openstack.org/554730
Committed: https://git.openstack.org/cgit/openstack-dev/pbr/commit/?id=183b445c0f8eb84568df6e07cf34dcc3e1935cec
Submitter: Zuul
Branch:    master"
1738698,2017-12-18 15:07:37 UTC,Hi there.
1738730,2017-12-20 10:10:32 UTC,"Update: Problem still exists on the fresh release, 7-2017-q4-major."
1738730,2017-12-20 10:31:31 UTC,"Update: The problem also exists on the first official 5 branch release, 5.2 (5-2015-q4-major). Now I'm trying to isolate the change from 4.9 to 5.2, with my non-existing GCC infrastructure knowledge :) I feel like I'm entering adark cave with full of bats :)"
1738730,2017-12-20 15:04:48 UTC,Just tested with the latest release. GCC: (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204
1738730,2017-12-20 16:52:26 UTC,"Hi John,"
1738730,2017-12-20 17:18:07 UTC,"My guess is, the nop is there to make sure the literal pool is word-aligned.
As for the bug, our hope is that the guys from GNU ARM Embedded pick it up and report upstream. I don't think there is a point for you to try and pinpoint the exact commit that introduced it."
1738730,2018-10-05 13:33:04 UTC,"Hi Thomas,"
1738730,2017-12-20 17:56:42 UTC,"By the way, could you click on ""affects me"" link to heat the issue up? This way the team may give it a better priority?"
1738730,2018-10-01 07:06:05 UTC,"Hi,"
1738730,2018-10-05 12:12:46 UTC,"Hi Murat,"
1738730,2017-12-20 09:25:51 UTC,"I've found the holy grail. Problem is happening if you are using a pointer to a struct. Normally, while accessing to that struct members, nothing is wrong, it accesses word by word. But if you declare a pointer to that struct and do your business with it, problem arises and GCC starts using byte by byte method even while unaligned access is enabled."
1738730,2017-12-20 17:47:45 UTC,"Today, I really tried, but fell short. Meld is still open for the source directories, 4.9 and 5.2."
1738730,2017-12-19 19:08:46 UTC,"I guess the problem lies under the -fpack-struct option. No matter unaligned access state is, the compiler switches one byte at a time mode with seeing -fpack-struct option."
1738730,2017-12-19 15:50:13 UTC,"I think you should try to construct a minimal example demonstrating the problem. Who knows, maybe you'll find something in your setup that causes this."
1738730,2017-12-19 12:32:05 UTC,"Hi Leo, yes I was going to revise the project and put pragma's for the necessary structs. But this still does not clarify what bothers me, byte by byte method is used even with enabled unaligned access. What's worse is, this creates issues on the real hardware, with an unknown cause, not just making the final image longer."
1738730,2017-12-19 11:24:40 UTC,"New tools can reveal old problems, in this case the use of -fpacked-struct on the entire project.

> Note: I need packed structs for serializing communication and storage.


We all do. Use #pragma pack(push, 1) and #pragma pack(pop) in the affected header files."
1738730,2017-12-19 06:55:20 UTC,"And additionally, why is still accessing words one byte at a time even unaligned access is enabled? This behavior is correct on 4.9 but not correct on 5 and 6 branch."
1738730,2017-12-18 21:14:47 UTC,"John,"
1738730,2017-12-18 15:47:07 UTC,"-fpack-struct must be responsible for this. Why would you want this option anyway? If you really insist, you might want to have a look at the option ""-munaligned-access"" as well. The manual says "" If unaligned access is not enabled then words in packed data structures are accessed a byte at a time."""
1738730,2017-12-18 14:47:09 UTC,"Sure,"
1738730,2017-12-18 14:34:53 UTC,Maybe you should show us the declarations of the structure and the variable in your code. Compiler options too.
1738730,2017-12-18 14:23:30 UTC,Couldn't find something definite. Just have seen this one:
1738730,2017-12-18 13:10:48 UTC,"Changes in major compiler version number are known to change the way some pragmas, attributes and so on are interpreted. You should examine your code and see if anything in the changelog from gcc 4 to gcc 5 affects it."
1738730,2017-12-18 12:58:27 UTC,"Could be. I'm switching back and forth between 4.9 and 5.4, using the same options. The thing is, why the newer versions try to access a 32bit variable byte by byte on a 32bit CPU? Let's say they have their own causes. So why is the functionality broken when accessing one byte at a time?"
1738730,2017-12-18 12:45:12 UTC,Looks like the compiler is accessing NVM_SPI->CTRL one byte at a time. There must be something in the declaration of NVM_SPI->CTRL and maybe in the compiler command line options that make it do it.
1738736,2020-06-23 09:56:57 UTC,Has there been any progress on this.
1738736,2019-05-08 08:09:15 UTC,It appeared for me after upgrade to Cosmic (did not have it before). And on both desktop PC and laptop.
1738736,2019-01-11 18:43:35 UTC,I can confirm on my side that it's still there after I also upgrade to Cosmic.
1738736,2019-01-11 10:00:16 UTC,I also have this issue with Cosmic (4.18.0-13) and also with the latest upstream kernel:
1738736,2018-10-28 00:16:41 UTC,I have the same flooding of /var/log/syslog about every 200 msecs with:
1738736,2017-12-18 08:55:36 UTC,Side note :
1738736,2018-01-03 14:04:33 UTC,"FYI, still got it with ""4.13.0-21-generic""."
1738736,2017-12-18 18:40:50 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1738736,2017-12-18 08:30:06 UTC,This change was made by a bot.
1738736,2018-01-28 20:17:56 UTC,Ok I finally got the time to test it on upstream kernel.
1738737,2017-12-18 14:48:59 UTC,monkey patch:
1738738,2018-02-05 20:23:35 UTC,"Yes I am +1 on this as well, it is a common use case where DSCP marks are used to convey some information (for example a L4-L7 classification) and enabling some filtering on that is good.  I did file [1] referenced in the description above with this intent. Now I think the API is at a point to start looking at this."
1738738,2020-03-24 21:23:17 UTC,Regarding current status of neutron-fwaas project I'm going to mark this one as won't fix for now.
1738738,2018-03-22 23:23:34 UTC,This RFE is approved
1738738,2018-01-25 21:55:35 UTC,"The FWaaS team indicated recently in regards to another RFE that they consider the V2.0 API stable enough to start adding features. I will move this RFE to the confirmed stage, based on German's feedback above and will ask other FWaaS team members to chime in"
1738738,2017-12-22 13:46:58 UTC,is fwaas v2 already stable?  otherwise adding new features might not be a good idea for now.
1738738,2017-12-19 03:24:15 UTC,"Hi Lujin, this is probably an RFE, but I guess the Driver team would be best to comment on it, if it can be accepted as a feature or would be treated as a simple bug fix. Thats why I didnt put the [RFE} in the title yet.
I am waiting for one of the Driver Team core members to comment on this.
FWIW this is an RFE from FWaaS team"
1738738,2017-12-19 01:17:04 UTC,"Is this a request for RFE? If so, could you please add [RFE] at the beginning of the title and bring it to Neuton team IRC meeting?"
1738738,2017-12-18 14:43:56 UTC,Having more L7 type filtering is definitely on the roadmap so this is a good feature.
1738738,2017-12-23 03:13:50 UTC,"Point noted, but implementation would be at a later stage, if there is a spec required for it."
1738750,2019-09-16 17:54:31 UTC,Migrated to https://github.com/widelands/widelands/issues/1694
1738751,2018-05-31 08:58:50 UTC,"I can confirm that. I had these problems in 1.1.1 and updated to 1.1.2. The behavior is the same. Running Sikulix under Linux, Debian 9 stretch."
1738751,2018-06-02 13:06:59 UTC,any more concrete information on specifics?
1738751,2017-12-18 11:20:13 UTC,"ok, tested with your code in 1.1.2:"
1738751,2018-03-13 16:18:51 UTC,"This problem persists in 1.1.2 release, just updated sikuli from 1.1.1 where this problem didn't exist (for me).
My code is exactly the same as before, since i imported the project in release 1.1.2 i get the error on save:
""[error] IDE: A non-IOException-problem when trying to save null
Error: null"""
1738751,2017-12-18 10:40:01 UTC,cannot reproduce this (the save problem) with 1.1.2.
1738751,2017-12-18 10:02:13 UTC,"at runtime
 running SikuliX: /Applications/Sikuli/SikuliX.app/Contents/Java/sikulix.jar -r /Users/Jeff/Desktop/SikuliScripts/Labrynth/Alt_Lab/From_Input_auto.sikuli
[error] script [ /Users/Jeff/Desktop/SikuliScripts/Labrynth/Alt_Lab/From_Input_auto.sikuli ] stopped with error at line --unknown--
[error] Error caused by: IndentationError: ('unindent does not match any outer indentation level', ('/Users/Jeff/Desktop/SikuliScripts/Labrynth/Alt_Lab/From_Input_auto.sikuli/From_Input_auto.py', 417, 8, '        else:\n'))"
1738751,2017-12-18 10:51:00 UTC,The Offending Code
1738766,2017-12-19 06:53:08 UTC,"I have to say this is not a fatal error and that the process continues. Although you can see the errors in the logs, they are being ignored."
1738773,2018-02-14 14:20:50 UTC,This bug was fixed in the package linux-firmware - 1.157.16
1738773,2018-02-09 15:47:21 UTC,@Amitkumar : Polite ping :) Are you able to verify this fix?
1738773,2018-02-14 14:20:56 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1738773,2017-12-18 12:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1738773,2018-01-26 09:48:19 UTC,"Hello Amitkumar, or anyone else affected,"
1738774,2018-11-02 16:06:17 UTC,"Please notice bug 121130. [Nevertheless, I support to release the svg-themes as soon as possible.]"
1738774,2018-12-21 11:47:43 UTC,Definitly true but only when the renderer give us the same quality as the png one.
1738774,2019-02-15 13:32:08 UTC,*** Bug 122536 has been marked as a duplicate of this bug. ***
1738774,2019-02-15 13:32:32 UTC,*** Bug 123480 has been marked as a duplicate of this bug. ***
1738774,2019-11-29 12:39:43 UTC,Changing priority to 'high' since the number of duplicates is 5 or higher
1738774,2019-11-29 13:25:32 UTC,"(In reply to andreas_k from comment #24)

> Definitly true but only when the renderer give us the same quality as the
> png one.
"
1738774,2020-01-18 11:53:34 UTC,"This is still an issue, and due to HiDPI getting more and more common, Ubuntu should really look into this to give users a good experience with the setups."
1738774,2020-02-04 22:09:44 UTC,"Just updated to Version: 6.4.0.3 (x64)
Build ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8"
1738774,2020-02-05 10:44:19 UTC,"(In reply to Matt from comment #29)

> Not sure if my comment belongs here or a related issue.
"
1738774,2020-02-20 21:14:06 UTC,"SVG icons are rendered blurry on macOS, so adding bug #130678 as a dependency"
1738774,2020-04-25 06:52:02 UTC,"> Just updated to Version: 6.4.0.3 (x64) Build ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8
"
1738774,2020-04-25 06:55:03 UTC,"Created attachment 159915
Breeze SVG icons in HiDPI screen (LO 6.4.2.2 in Ubuntu 20.04/Arch/Fedora 32)"
1738774,2020-06-17 00:23:40 UTC,This is the typical chicken-egg problem: LO's SVG rasterizer / icons broken => default to PNG. Everybody uses PNG (and some complain about blocky icons in HiDPI) => nobody fixes the LO's SVG rasterizer / icons. Some more background info is in bug 133877 comment 11.
1738774,2020-06-17 02:09:45 UTC,"In general I think people with high DPI screens would prefer to use SVG icons and live with or report a small number of bugs with a small number of mid-rendered icons then live with 100% of all icons being pixelated and ugly. Perhaps making the SVG renderer default only for high DPi users of SVG-compatible icon themes would make everyone happy: high DPI users get nicer icons overall, while devs get more user eyeballs (and bug reports, and potential contributors) using the SVG renderer."
1738774,2020-06-17 09:06:33 UTC,"(In reply to Jan-Marek Glogowski from comment #34)

> This is the typical chicken-egg problem: LO's SVG rasterizer / icons broken
> => default to PNG. Everybody uses PNG (and some complain about blocky icons
> in HiDPI) => nobody fixes the LO's SVG rasterizer / icons. Some more
> background info is in bug 133877 comment 11.
"
1738774,2020-07-01 05:23:38 UTC,"Just for your information. As an icon designer and mauntainer now all icon themes have SVG versions. So I would say its safe if in some point we reach perfect SVG support, than the PNG version can be removed or moved to the extension sites."
1738774,2020-07-25 07:18:29 UTC,*** Bug 131946 has been marked as a duplicate of this bug. ***
1738774,2020-08-12 11:16:10 UTC,"In Debian Sid/unstable with GNOME 3.36.4 and LibreOffice 7.0.0, I switched the icon theme from *Elementary* to *Elementary (SVG)*, and the icons still look blurry on a HiDPI monitor connected over HDMI."
1738774,2020-09-02 19:42:42 UTC,"Created attachment 165049
Blurry Elementary SVG toolbar icons"
1738774,2020-09-02 19:45:08 UTC,"(In reply to moosetrax from comment #40)

> Created attachment 165049 [details]
> Blurry Elementary SVG toolbar icons
>
> Blurry SVG icons with LibreOffice 7.0.0.3 on Cinnamon 4.2.4 at resolution
> Cinnamon 4.2.4.
"
1738774,2021-01-16 12:31:38 UTC,Confirming blurry SVG (as well as PNG) icons.
1738774,2018-10-31 03:03:14 UTC,*** Bug 105489 has been marked as a duplicate of this bug. ***
1738774,2018-10-28 12:13:37 UTC,*** Bug 120851 has been marked as a duplicate of this bug. ***
1738774,2018-08-16 17:08:21 UTC,Also related: https://bugs.documentfoundation.org/show_bug.cgi?id=115439
1738774,2018-03-07 16:51:51 UTC,*** Bug 105778 has been marked as a duplicate of this bug. ***
1738774,2018-02-24 18:18:09 UTC,Hi
1738774,2018-02-24 18:57:06 UTC,It would be really awesome if the svg support would work perfect but we are not there. As long as the png files look better they have to be generated.
1738774,2018-02-25 07:40:49 UTC,There are still a few issues but there is light at the end of the tunnel http://nabble.documentfoundation.org/Re-minutes-of-ESC-call-tt4229391.html#a4229645
1738774,2018-02-26 11:51:49 UTC,"Well, for me (on Windows) the SVG Rendering was perfect, but I tested only a few Icons that were available in the Tango-Set (I only deleted the PNGs where SVG where present). So, absolutely possible, that some icons don't render right, when there are attributes missing in the SVG."
1738774,2018-02-26 21:10:37 UTC,Tested the svg icon theme on linux work really good for me. In Virtualbox I had problem on a linux guest system. don't know why.
1738774,2018-02-26 21:17:07 UTC,(In reply to andreas_k from comment #5)
1738774,2018-02-27 01:05:06 UTC,"Yes, gtk3 backend has issues (because we use his way of doing HiDPI), which I know how to resolve (already did a proof-of-concept) but I need some spare time to implement it properly. The issue is described in ESC minutes..."
1738774,2018-03-07 16:49:36 UTC,*** Bug 115912 has been marked as a duplicate of this bug. ***
1738774,2018-03-07 16:51:05 UTC,*** Bug 105489 has been marked as a duplicate of this bug. ***
1738774,2018-08-16 16:46:31 UTC,Please also see https://bugs.documentfoundation.org/show_bug.cgi?id=114235.
1738774,2018-02-04 13:08:45 UTC,"Description:
In the current Icon-Sets there are already some Icons that exist in png AND svg versions. During my research for Bug 114699 I noticed, that the png versions can be deleted and LibO then uses the svg-versions of those Icons. Result is, that those Icons looks WAY better (perfectly sharp, no alias) then the upscaled png-versions."
1738774,2018-03-07 16:51:56 UTC,*** Bug 105950 has been marked as a duplicate of this bug. ***
1738774,2018-03-07 16:52:05 UTC,*** Bug 106682 has been marked as a duplicate of this bug. ***
1738774,2018-03-07 16:52:09 UTC,*** Bug 110356 has been marked as a duplicate of this bug. ***
1738774,2018-03-07 16:52:14 UTC,*** Bug 110457 has been marked as a duplicate of this bug. ***
1738774,2018-03-07 16:52:17 UTC,*** Bug 114444 has been marked as a duplicate of this bug. ***
1738774,2018-06-06 10:10:01 UTC,"Dear Tomaz Vajngerl,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assigned it back to yourself if you're still working on this."
1738774,2018-06-08 12:34:46 UTC,*** Bug 117158 has been marked as a duplicate of this bug. ***
1738774,2018-06-18 07:43:00 UTC,*** Bug 117846 has been marked as a duplicate of this bug. ***
1738774,2018-08-09 01:40:42 UTC,Wasn't work just done to introduce new icons in 6.1?  Would it have made sense to work this as part of that?
1738774,2018-08-16 13:46:29 UTC,"Sorry for the lack of feedback until now, Paul."
1738774,2018-08-16 16:44:34 UTC,"On 08/16/18 15:46, Olivier Tilloy wrote:"
1738774,2018-03-07 16:52:00 UTC,*** Bug 106191 has been marked as a duplicate of this bug. ***
1738780,2017-12-19 02:49:56 UTC,"The charm can certainly default these to the same value, and allow it to be overridden if explicitly added to the config."
1738781,2017-12-25 10:29:31 UTC,Hello
1738781,2017-12-18 13:25:02 UTC,journalctl -xe
1738781,2017-12-18 13:11:58 UTC,systemctl status Networkmanager.service
1738781,2017-12-18 13:10:54 UTC,manual copy of the network restarting command
1738781,2017-12-18 13:09:36 UTC, good ping
1738809,2017-12-18 15:23:39 UTC,They don't look much better on 100% either.
1738812,2018-01-11 17:39:35 UTC,"what behavior would you expect in that case, @haoqingchuan-28?"
1738812,2018-01-13 05:40:17 UTC,"@Antoni Segura Puimedon, thank you for your question."
1738812,2018-03-14 09:45:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/552856"
1738812,2018-03-21 18:08:07 UTC,We should set it dependant on the tunnelling for the net (1500 for vlan provided networks).
1738812,2018-03-26 18:51:27 UTC,"Reviewed:  https://review.openstack.org/552856
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=c00513bb6418b69e57cd4e9ae3823409f3574579
Submitter: Zuul
Branch:    master"
1738821,2018-04-12 12:55:59 UTC,"1:6.0.3-0ubuntu1 is now in bionic, it should have libreoffice-startcenter.desktop back."
1738821,2018-04-12 09:13:55 UTC,"Thank you Olivier.
Remark #8 seems to be OK.
Hope this correction in next update."
1738821,2018-04-09 13:58:53 UTC,"> If you look at libreoffice-common_6.0.3-1_all.deb from
> packages.debian.org, it contains
> /usr/share/applications/libreofice-startcenter.desktop.
> Why is the version on launchpad different ?
"
1738821,2018-04-09 13:35:03 UTC,"According to https://wiki.debian.org/AppStream/Guidelines#How_to_exclude_.desktop_files_from_the_metadata, all that's needed to fix this bug is to add the following entry to libreoffice-startcenter.desktop:"
1738821,2018-04-09 13:34:06 UTC,"If you look at libreoffice-common_6.0.3-1_all.deb from packages.debian.org, it contains /usr/share/applications/libreofice-startcenter.desktop.
Why is the version on launchpad different ?"
1738821,2018-04-07 11:47:42 UTC,"I do totally agree with Tim comment.
The startdesktop is an essential feature of libreoffice suite. For example, it is the best user-friendly interface to choose a template or to open a recent document, using the big preview window.
If it is placed in libreoffice-common or libeoffice meta package is not relevant; it needs to be somewhere.
It was previously in libreoffice-common as does xsltfilter. I don't understand what has changed to justify such discussion."
1738821,2018-04-09 11:31:35 UTC,"This is just mirroring the debian packaging. Perhaps this is a bit drastic, though."
1738821,2018-04-04 19:20:51 UTC,"Please forgive me, but I am not quite clear whether this bug report suggests that the startcenter desktop should no longer exist or not, or whether it should just be in a different package."
1738821,2018-03-14 11:56:51 UTC,"Fixed in debian, and backported: https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=c830674e04ed0b080308057e0dedf87c4a655f67"
1738821,2018-03-08 14:40:26 UTC,Reported against debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892364
1738821,2018-04-09 13:33:36 UTC,Reverted: https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=79c4e00dcfcde9c5fa5baf1ac4a40f1ff49c8a5d
1738831,2017-12-19 08:14:30 UTC,"In addition it is perfectly possible to create a stack using this template and the command:
`$ openstack stack create -t heat/templates/default.yaml.template mystack`"
1738834,2018-06-26 10:31:35 UTC,"But that should be done in postinst:
129         # Force virtlockd to reexec if enabled
130         if [ -d /run/systemd/system ]; then
131           ! systemctl is-active -q virtlogd || systemctl reload virtlogd.service >/dev/null
132           ! systemctl is-active -q virtlockd || systemctl reload virtlockd.service >/dev/null
133         fi"
1738834,2018-07-19 11:45:29 UTC,Discussions revealed that it might also be interesting to check the status of the virtlogd.socket before the update.
1738834,2018-07-18 12:01:55 UTC,"Hmm, maybe another package of that upgrade pack restarts it which it should not do."
1738834,2018-07-18 09:04:02 UTC,This happens during the unattended-upgrade at night. The libvirt-bin is then not fully upgraded/installed.
1738834,2018-06-26 10:40:44 UTC,Here after an install of libvirt-daemon-system (which has the snippet to reload)
1738834,2018-06-26 10:27:10 UTC,"For that it has:
  ExecReload=/bin/kill -USR1 $MAINPID
defined and would do the right thing."
1738834,2018-06-26 10:24:51 UTC,"This was it:
The virtlogd daemon has the ability to re-exec() itself upon receiving SIGUSR1, to allow live upgrades without downtime."
1738834,2018-06-26 10:14:36 UTC,Another way to hit this upgrade path is Xenial using libvirt and then upgrading to Cloud-Archive Pike (Artful based).
1738834,2018-03-28 13:04:13 UTC,"It looks like there is no other scenario for this upgrade to happen naturally between the versions 1.3.1 and 3.6.0 other than a release upgrade in ubuntu, right? And that would require a reboot at the end."
1738834,2018-02-12 12:26:42 UTC,Could it be related to https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1583009
1738834,2017-12-18 17:01:30 UTC,"Looking at postinst, I see virtlogd is reloaded. I have checked that reload trigger a reexec (like expected). Therefore, I don't know why this is not enough. I should investigate more on this."
1738834,2018-06-26 10:25:25 UTC,From http://manpages.ubuntu.com/manpages/bionic/man8/virtlogd.8.html
1738838,2017-11-14 16:55:35 UTC,"Created attachment 363624
lib: Remove last users of ""Properties"" D-Bus wrapper"
1738838,2017-11-14 16:55:41 UTC,"Created attachment 363625
lib: Remove fd.o Properties API glue"
1738838,2017-11-14 16:55:47 UTC,"Created attachment 363626
lib: Fix possible race when creating adapters or devices"
1738838,2017-11-14 16:55:52 UTC,"Created attachment 363627
lib: Always send ""default-adapter-powered"""
1738838,2017-11-14 16:58:35 UTC,"Attachment 363618 pushed as b5a6455 - lib: Remove unneeded include
Attachment 363619 pushed as 899eb7d - lib: Remove never used FDO_PROPERTIES_INTERFACE constant
Attachment 363620 pushed as 215acf6 - lib: Indent and document gtk_tree_store_new() call
Attachment 363621 pushed as 17983ac - lib: Use GDBusObjectManager
Attachment 363622 pushed as 9319001 - lib: Remove creation of intermediate GDBusProxies
Attachment 363623 pushed as 27e88fc - lib: Simplify Properties setting
Attachment 363624 pushed as 61f5ad5 - lib: Remove last users of ""Properties"" D-Bus wrapper
Attachment 363625 pushed as afccb57 - lib: Remove fd.o Properties API glue
Attachment 363626 pushed as 9c6d93a - lib: Fix possible race when creating adapters or devices
Attachment 363627 pushed as dbe815a - lib: Always send ""default-adapter-powered"""
1738838,2017-11-14 17:01:50 UTC,Which leaves us with attachment 351968. I have trouble understanding in which case this could happen now. Can you file a new bug if this is still needed?
1738838,2017-11-15 10:45:24 UTC,"Oh, right. Attachment 351968 was just my way of to not duplicate the icon override logic."
1738838,2017-12-19 08:30:21 UTC,Sounds like maybe you need the fix (firmware) from bug 1729389. Please try that...
1738838,2018-02-15 12:52:02 UTC,*** Bug 775376 has been marked as a duplicate of this bug. ***
1738838,2018-06-06 09:01:31 UTC,Maybe it's https://bugzilla.gnome.org/show_bug.cgi?id=789110 ?
1738838,2018-04-10 12:41:31 UTC,Same bug on Ubuntu 18.04 / Thinkpad P51.
1738838,2018-06-06 09:04:02 UTC,"Another fix is on the way, specifically for gnome-shell:
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/118"
1738838,2018-11-21 20:10:32 UTC,"Was moved to https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/118, closing."
1738838,2018-11-22 14:36:06 UTC,Same/very similar problem in 18.10.
1738838,2020-01-17 03:47:59 UTC,Please reopen this bug. The above link is not a bug.
1738838,2020-01-17 03:50:48 UTC,Confirmed the same bug is still in gnome-shell master (version 3.35).
1738838,2020-05-28 05:51:18 UTC,"This bug existed yesterday on my Ubuntu 20.04. I probably had suspended the laptop. A couple of days ago, it was working fine even after suspending the laptop."
1738838,2021-01-18 09:12:29 UTC,"It is 2021, Ubuntu 20.04 LTS on a Dell Inspiron 15R 5537 with Intel Wireless-AC 7260HMW card installed."
1738838,2018-02-16 04:08:12 UTC,"OK, if not https://bugzilla.gnome.org/show_bug.cgi?id=775376 then maybe https://bugzilla.gnome.org/show_bug.cgi?id=782530"
1738838,2017-11-14 16:55:24 UTC,"Created attachment 363622
lib: Remove creation of intermediate GDBusProxies"
1738838,2017-11-14 16:55:29 UTC,"Created attachment 363623
lib: Simplify Properties setting"
1738838,2017-05-16 11:48:38 UTC,"Created attachment 351968
lib: Force custom icon code override to run"
1738838,2017-05-11 18:58:52 UTC,"Because of the method that the dbus proxies are created there is currently a race condition. When an adapter is added it can have an initial ""Powered"" state of off which is turned on immediately afterwards. However, the signal connect to get the update only happens later."
1738838,2017-05-11 19:03:39 UTC,"Created attachment 351663
lib: Rework adapter and device proxy registrations."
1738838,2017-05-16 09:15:35 UTC,Review of attachment 351663:
1738838,2017-05-16 11:48:04 UTC,"Created attachment 351966
lib: Rework adapter and device proxy registrations."
1738838,2017-05-16 11:48:15 UTC,"Created attachment 351967
lib: Always send ""default-adapter-powered"""
1738838,2017-05-16 11:49:01 UTC,"There, that is all logical changes split out."
1738838,2017-05-16 12:27:56 UTC,"I won't have time to review this in the short-term, but a dbusmock regression test which shows the problem before, and shows it fixed afterwards would be really useful."
1738838,2017-10-17 16:50:14 UTC,"Created attachment 361759
Inconsistency in the bluetooth menu"
1738838,2017-05-16 17:23:35 UTC,"The patch might be hard to read as it changes all the property accessors, but really it all boils down to the two questions:
 * Is it correct to use GDBusObjectManagerClient to keep track of the objects?
 * Is it good to use GObject properties on the Adapter1/Device1 proxies (instead of manually driving a DBus properties interface proxy)?"
1738838,2017-10-17 17:01:34 UTC,"Created attachment 361761
2. bluetooth: Be consistent when determining whether Bluetooth is off"
1738838,2017-10-17 17:13:36 UTC,Review of attachment 361760:
1738838,2017-10-17 17:39:40 UTC,Review of attachment 361761:
1738838,2017-10-17 19:20:09 UTC,"Comment on attachment 361760
1. bluetooth: Add missing 'BluetoothHardwareAirplaneMode' to D-Bus interface"
1738838,2017-10-17 19:27:40 UTC,"(In reply to Florian Müllner from comment #4)

> Review of attachment 361761 [details] [review]:
>
> > otherwise we risk showing inconsistent states in each place if.
>
> I'd be interested in how that sentence continues :-p
"
1738838,2017-11-14 16:55:01 UTC,"Created attachment 363618
lib: Remove unneeded include"
1738838,2017-11-14 16:55:07 UTC,"Created attachment 363619
lib: Remove never used FDO_PROPERTIES_INTERFACE constant"
1738838,2017-11-14 16:55:13 UTC,"Created attachment 363620
lib: Indent and document gtk_tree_store_new() call"
1738838,2017-10-17 17:01:17 UTC,"Created attachment 361760
1. bluetooth: Add missing 'BluetoothHardwareAirplaneMode' to D-Bus interface"
1738838,2017-11-14 16:55:18 UTC,"Created attachment 363621
lib: Use GDBusObjectManager"
1738844,2017-12-19 21:34:02 UTC,"Mike, Thanks for the feedback, but I don't understand your comment about using the value of the depth field vs the id.  Could you suggest an example I could look at, or go into more detail when you have time."
1738844,2017-12-19 16:25:08 UTC,"Here is a sort clause that tries to keep the default hprox behavior by default, but if the circ.hold_hprox_depth library setting is set for the copy owning location then use that as the depth."
1738844,2017-12-19 17:36:41 UTC,"Josh,"
1738853,2017-12-18 23:14:54 UTC,I try to do a grep time ago but we need a multiplatform solution... a forced title tag convention could also help
1738853,2017-12-18 22:05:16 UTC,"Then I'd prefer the file name cleanup... converting _ to spaces, or similar, and not load a name from the set at all. This name change is irritating."
1738853,2017-12-18 21:22:29 UTC,"Its a bug without good solution. to get correct name need to parse all symbols files on load, what slow a lot each time open inkscape if have a lot of symbols. We cam mitigate it with the name of file similar or equal to the title."
1738853,2017-12-18 21:23:01 UTC,I'm in favor to mark it as won't fix
1738859,2020-10-07 12:43:05 UTC,I think I may have a similar issue:
1738859,2020-10-07 12:37:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738859,2017-12-18 19:03:28 UTC,"Alright, it seems that the problem was in ""layout: ru,us,us"". When I switched to ""layout: us"" my gnome settings stopped affecting input so I switched it to the following:"
1738866,2017-12-20 19:28:44 UTC,if someone wants to fix this: https://github.com/openstack/aodh/tree/master/doc/source/install
1738866,2018-03-06 21:33:24 UTC,I guess I'll give it a shot
1738867,2017-12-31 11:55:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1738868,2017-12-18 20:03:51 UTC,"Terminal output (as plaintext).
See attached."
1738868,2017-12-18 21:05:00 UTC,"20:57:xx GMT (& UTC): Official bug report sent to Nautilus Mailing list <email address hidden>. Subject: '[BUG REPORT] Nautilus refuses to open on command, even as sudo.'"
1738868,2019-02-06 13:06:04 UTC,"closing following upstream, the requested info needed to debug the issue were not provided"
1738882,2017-12-20 18:10:51 UTC,"Confirmation, or even bringing up the overlayed record, as in XUL client, would be most helpful."
1738882,2018-12-07 01:03:13 UTC,"Hi all -- would simply opening up the overlaid record in a new tab (https://bugs.launchpad.net/evergreen/+bug/1805856) be sufficient?  Or is there more feedback that is necessary, especially in case where the overlay fails?"
1738882,2019-03-04 20:48:51 UTC,Having a new tab open when overlay is successful is fine. An error msg for failure is better.
1738889,2017-12-19 20:25:48 UTC,It's MULTI-PROCESSOR related.
1738910,2018-01-01 05:47:58 UTC,wsrep_init that is responsible for galera library initialization has failed. Can you share the log file. It should have a possible reason for failure.
1738910,2018-01-08 22:31:56 UTC,Thanks for looking into it. See the mysqld error logs from both nodes for 2017-12-20 to 2017-12-29.
1738910,2018-01-16 10:42:29 UTC,As per the original comment server startup failed. Log files doesn't hint any server startup failure.
1738910,2018-01-18 08:20:15 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2022
1738943,2018-01-20 07:40:09 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1490
1738949,2017-12-19 20:30:07 UTC,This change was made by a bot.
1738956,2018-01-06 07:04:44 UTC,We can leverage `git rev-parse --show-toplevel` if our current code is unable to find a repo at the dir.
1738956,2018-01-06 06:59:09 UTC,I believe none of our code currently handles being in a subdir of a git repo.
1738957,2018-01-10 13:40:03 UTC,"Note: xenial fails the same way IFF you have the tarball around which explains comment #1.
I'd assume Robie had one tarball around but not the other on the report."
1738957,2018-01-10 16:15:09 UTC,"On 10.01.2018 [13:40:03 -0000], ChristianEhrhardt wrote:

> Note: xenial fails the same way IFF you have the tarball around which
> explains comment #1.
"
1738957,2018-01-06 05:07:51 UTC,"Interestingly, I get the backtrace when linting either xenial or zesty."
1738957,2018-01-06 06:46:55 UTC,"Ok, I think I figured out the problem, the fetch_orig_from_pristine_tar logic, which is undergirded by gbp-buildpackage, is using the current branch to determine what to extract. There is no support for using a changelog from a different treeish."
1738961,2017-12-19 07:59:23 UTC,I believe you have already filed this bug but can't check it right now.
1738961,2017-12-19 08:26:54 UTC,"I didn't see it against any bugs tagged ""lint"". Perhaps I missed it while tagging previously. Separately there's bug 1706364 about checking SRU paperwork, but I think that's distinct from this one."
1738961,2017-12-19 08:48:39 UTC,Ah perhaps I was confusing it with that bug.
1738963,2017-12-19 09:25:50 UTC,https://docs.openstack.org/masakari/latest/ would be the correct link.
1738963,2018-02-06 06:56:01 UTC,"Change abandoned by Anilkumar Thovi (<email address hidden>) on branch: master
Review: https://review.openstack.org/529299
Reason: Not required"
1738963,2018-04-11 08:49:36 UTC,This issue is addresed in patch https://review.openstack.org/#/c/559047.
1738968,2018-08-21 11:13:47 UTC,Should be simple enough for me to try out bzr launchpad workflows.
1738968,2018-08-21 15:28:28 UTC,Setting back to 'In Progress' since this hasn't been merged to trunk yet.
1738972,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1738972,2018-03-30 18:57:41 UTC,Dup:
1738972,2018-03-19 10:57:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1738972,2017-12-19 09:10:50 UTC,patch sent
1738972,2017-12-19 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1738972,2018-01-14 22:07:37 UTC,"Started getting regular BSOD (Windows 2012R2) in KVM after 16.04 LTS HWE hypervisor upgrade to 4.13.
Workaround: have had to regress KVM back to 4.10"
1738975,2017-12-19 09:10:16 UTC,patch set sent
1738975,2018-03-19 10:57:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1738975,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1738981,2018-03-11 21:37:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551811"
1738981,2018-04-29 19:42:20 UTC,Tracked by: https://storyboard.openstack.org/#!/story/2001938
1738986,2020-06-23 17:20:56 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/564500"
1738986,2020-06-23 17:23:01 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/529359"
1738986,2018-06-03 10:59:49 UTC,"Reviewed:  https://review.openstack.org/529982
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=e32364e80d7e870d153d9b7a3295a1761cc90697
Submitter: Zuul
Branch:    master"
1738986,2020-06-23 17:21:14 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/530028"
1738986,2020-06-23 17:21:01 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/567528"
1738986,2018-05-10 09:13:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/567528"
1738986,2017-12-24 13:14:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/529982"
1738986,2018-04-26 13:15:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/564500"
1738986,2017-12-20 15:38:23 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/529358"
1738986,2017-12-20 15:38:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/529359"
1738986,2018-05-06 13:25:07 UTC,"Reviewed:  https://review.openstack.org/529358
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=c3280d5ca52455a1fb98ce40d5a682cea65a2f77
Submitter: Zuul
Branch:    master"
1738986,2018-01-10 15:54:38 UTC,"Reviewed:  https://review.openstack.org/503538
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=03f391c429dddddc8b460f0e13949016fc52dd82
Submitter: Zuul
Branch:    master"
1738986,2017-12-25 11:22:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/530028"
1738988,2017-12-20 16:11:44 UTC,"Hi,"
1738988,2018-08-06 07:04:33 UTC,I don't believe #1713313 is an actual bug: Giving noone with root access access to the GUI is part of one of the major features wayland was created for: Hindering a gui application from spying on the screen or the keyboard input of another application.
1738991,2017-12-19 10:40:57 UTC,"After talking with Anastasia and John, and looking through code a bit, it is quite likely that credentials were loaded from from the environment as a file path and then a `juju update-credential` was run. This would cause the file path and not it's contents to be stored and result in the errors we are seeing in this bug's description. If you reload your credentials by putting the credentials file in `$JUJU_DATA` and then re-run `juju update-credential` you may be able to work around this issue."
1738991,2017-12-19 11:58:24 UTC,"We believe that this might already be fixed in current versions of Juju, but that we need a way to help people get off of old versions that were affected by this.
This is mostly opened as a way to track the conversation around this. There may not be anything we can do for this bug specifically, because it is simply an issue of older controllers."
1738991,2017-12-19 22:54:59 UTC,Updating $JUJU_DATA/credentials.yaml and running juju update-credential is the first thing I tried; I tried with multiple client versions between 2.0.3 and 2.3.1.
1738991,2017-12-19 22:56:35 UTC,Further debug logs at https://pastebin.canonical.com/205864/ show the same general symptoms.
1738991,2017-12-20 16:04:38 UTC,https://github.com/juju/juju/pull/8247
1738991,2017-12-20 16:05:46 UTC,"Hi Paul,"
1738991,2018-05-04 19:59:00 UTC,I ran update-credentials and still get the errors described here using Juju 2.3.7.
1738991,2018-05-06 16:49:34 UTC,"Hello Jamon,"
1738993,2018-01-11 20:02:59 UTC,We are looking to release 2.3.2 early next week.
1738993,2018-01-11 19:28:35 UTC,I know this was only just committed so not trying to rush it but curious when could we expect to see a release with this in it.
1738993,2018-01-08 02:31:22 UTC,https://github.com/juju/juju/pull/8265
1738993,2018-01-08 01:04:56 UTC,"Kevin, the error message is incorrect of course (the model can't exist already during bootstrap!), but it did point to the cause. There's a transaction failure in mongo caused by us not escaping the dots in the region name."
1738993,2018-01-07 19:48:10 UTC,"Hi, any more data needed to track or fix this?"
1738993,2017-12-19 22:37:39 UTC,"Hi, to clarify this whole story a bit:"
1738993,2018-01-14 14:55:00 UTC,This sounds nice. Thanks for your effort! I'll try it as soon as it's released.
1738993,2017-12-19 21:46:01 UTC,"Hi, just reran the same with juju 2.2.8"
1738993,2017-12-19 21:42:21 UTC,rerun with juju 2.2.8
1738993,2017-12-19 14:49:31 UTC,"Is there anything about ""datastore"" that is causing us to re-use the same
block disk between runs?"
1738993,2017-12-19 14:48:54 UTC,"Is there any chance that the VM's disk was not clean? I know we saw similar
failures in MAAS when it would re-use a machine that had been a controller
previously, and the disk was not wiped."
1738993,2017-12-19 12:31:50 UTC,Tested with various combinations: CLI Version 2.3.1
1738993,2017-12-19 21:46:44 UTC,"The datastore is clean, I manually deleted the leftovers from juju-vmdk upload after each unsuccessful run."
1738997,2017-12-19 10:59:07 UTC,Fixed by:
1739000,2018-01-06 00:25:16 UTC,"Robie, I'm assigning to you, as it's related to the empty directory support."
1739000,2018-01-15 05:19:03 UTC,Affected: collectd
1739000,2018-09-21 07:47:34 UTC,I think this is fixed by cbb0f52. If not then please revert the bug status.
1739000,2020-09-28 12:01:41 UTC,Fix released in git-ubuntu version 1.0
1739013,2017-12-28 14:16:54 UTC,"Reviewed:  https://review.openstack.org/529063
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ec040527368a13cdc5ed427b21692be5bb2f28b6
Submitter: Zuul
Branch:    master"
1739013,2018-01-23 21:47:25 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/536981"
1739013,2018-01-23 22:30:28 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/536995"
1739013,2018-01-26 00:43:47 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1739013,2018-01-30 19:32:27 UTC,"Reviewed:  https://review.openstack.org/536981
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1558893de1e3af49fdeafd1c0d7e4c21ccbeb064
Submitter: Zuul
Branch:    stable/pike"
1739013,2018-02-05 12:48:45 UTC,"Reviewed:  https://review.openstack.org/536995
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b47656272ca04c0b26554886e4302ad7d6f6a50e
Submitter: Zuul
Branch:    stable/ocata"
1739013,2018-02-15 23:53:32 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1739013,2018-05-02 12:04:12 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1739013,2017-12-19 13:30:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529063"
1739022,2017-12-20 02:23:51 UTC,apport information
1739022,2017-12-28 19:03:39 UTC,I would like to opine specifically that if $XDG_DATA_DIRS is specifically not what the shell expects -- for example it might contain a corrupted character from translating between fish arrays and bash arrays -- Gnome Shell on Wayland will not start.
1739022,2017-12-22 09:34:51 UTC,I'm not sure how to reproduce this easily. It seems related to snaps and other system changes. Certainly the rest of us have bash as our default shells and it's not a problem for other people. So setting low priority for now.
1739022,2017-12-20 02:26:09 UTC,Uploaded the information. Thanks.
1739022,2017-12-20 02:23:50 UTC,apport information
1739022,2017-12-20 02:23:47 UTC,apport information
1739022,2017-12-20 02:23:45 UTC,apport information
1739022,2017-12-20 02:21:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1739022,2017-12-20 02:23:48 UTC,apport information
1739023,2017-12-19 18:23:13 UTC,"cloudinit/sources/DataSourceAzure.py -> ifconfig used only in freeBSD block
tools/mock-meta.py -> ifconfig in comment"
1739031,2017-12-19 14:22:14 UTC,Please attach the cinder logs. The backend driver is likely hitting an error that is not causing the status to go to error.
1739056,2017-12-19 15:56:32 UTC,"Known issue/limitation. You can easily disable this by turning off the DBus, or you can change your launcher command to use the ""-u"" flag."
1739056,2017-12-19 16:42:21 UTC,"Perhaps there's some way that could be the default action, or at least some sort of notification could be given upon install?  People used to terminator on ubuntu could run into some bad issues with this.  I was using terminator for hours after upgrading to 17.10 not realizing I was editing and saving files on dozens of servers that were open in other workspaces."
1739075,2018-05-11 10:08:25 UTC,Parallel execution can be achieved by using different projects per test_ method.
1739078,2017-12-29 19:04:31 UTC,"If you were going to do this, I think you'd want a back to back comparison of where Alembic gets you and where your test script gets you, so that you know you have a precisely equivalent environment.  Alternatively, you could run Alembic once and then snapshot the resulting schema to a script which you use for subsequent creates.  Having a script that stands alone is asking for it to get out of date."
1739086,2018-04-15 08:51:13 UTC,"@dino99, it is not helpful to set to incomplete status without actually asking the reporter or anybody affected a question.  We're not here to close the biggest number of tickets, we're here to fix bugs.  I'm saying this as co-maintainer of wondershaper in Debian, just in case you wondered."
1739086,2018-03-27 04:17:42 UTC,[Expired for wondershaper (Ubuntu) because there has been no activity for 60 days.]
1739086,2018-06-14 08:12:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739086,2018-01-25 16:35:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739086,2018-01-25 16:56:44 UTC,"wondershaper is very old, not maintained since Mon, 11 May 2015
http://repo.or.cz/lartc.git"
1739097,2017-12-22 07:28:45 UTC,"I subscribe @chipaca - looking at the code, I think what the message is saying is: ""The 'atom' snap that used to track the 'edge' channel is no longer doing that"". However it looks a bit misleading so I think we need to improve it."
1739097,2017-12-22 07:32:37 UTC,I created https://github.com/snapcore/snapd/pull/4420 for this.
1739097,2018-05-14 09:28:06 UTC,Sorry I missed this back then.
1739097,2018-05-14 09:29:39 UTC,(BTW the code has since been changed to not show the message when sideloading unless you also specify a channel then)
1739097,2019-11-26 10:12:25 UTC,https://github.com/snapcore/snapd/pull/4420 has been merged in 2018 so marking as fix released.
1739099,2017-12-19 16:20:02 UTC,"Sorry for the poor bug report. I should have added, using Mate 16.04, Caja 1.12.7"
1739102,2017-12-19 20:40:28 UTC,apport information
1739102,2017-12-19 20:40:30 UTC,apport information
1739102,2017-12-19 20:40:32 UTC,apport information
1739102,2017-12-19 20:40:34 UTC,apport information
1739102,2017-12-20 18:39:40 UTC,The issue is still present on the latest mainline kernel (4.15-rc4).
1739102,2017-12-20 18:21:23 UTC,"The issue occurs from a clean install of 17.10 and a currently updated 17.10.
Kernel 4.12 and back seem to work without issue, so I'm guessing it's related to the 4.13 kernel."
1739102,2018-02-22 20:30:51 UTC,"Sorry for the delay.
The input issues first crop up in 4.13-rc1. I also noticed that the latest 4.16-rc2 doesn't seem to be affected by the issue."
1739102,2018-01-02 02:46:29 UTC,You need to do a kernel bisection then.
1739102,2017-12-19 20:40:25 UTC,apport information
1739102,2017-12-20 17:57:57 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1739102,2017-12-19 20:40:23 UTC,apport information
1739102,2017-12-19 20:40:02 UTC,apport information
1739102,2017-12-19 20:40:19 UTC,apport information
1739102,2017-12-19 20:40:17 UTC,apport information
1739102,2017-12-19 20:40:15 UTC,apport information
1739102,2017-12-19 20:40:14 UTC,apport information
1739102,2017-12-19 20:40:12 UTC,apport information
1739102,2017-12-19 20:40:09 UTC,apport information
1739102,2017-12-19 20:40:06 UTC,apport information
1739102,2017-12-19 20:40:04 UTC,apport information
1739102,2017-12-19 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1739102,2017-12-19 16:19:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1739102,2017-12-19 20:40:21 UTC,apport information
1739108,2018-06-12 13:28:37 UTC,This issue was fixed in the openstack/django_openstack_auth 3.6.1 release.
1739108,2018-05-28 17:11:23 UTC,"Reviewed:  https://review.openstack.org/568545
Committed: https://git.openstack.org/cgit/openstack/django_openstack_auth/commit/?id=ddcfe7a6d4db1b476254b556057756eadd7b097d
Submitter: Zuul
Branch:    stable/pike"
1739108,2018-01-26 00:31:22 UTC,This issue was fixed in the openstack/horizon 13.0.0.0b3 development milestone.
1739108,2018-01-20 07:20:43 UTC,"Reviewed:  https://review.openstack.org/530488
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=54365d7ef1007b3c8373ecb4e591c7f899dbeb98
Submitter: Zuul
Branch:    master"
1739108,2017-12-29 17:34:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530488"
1739108,2017-12-20 21:29:02 UTC,"The fix is to remove https://github.com/openstack/horizon/blob/master/openstack_auth/policy.py#L184-192. Those lines are wrong. The default for policy should be to allow, not block."
1739108,2017-12-20 21:04:45 UTC,"https://review.openstack.org/#/c/527668/ sync the policy file from the latest master of keystone repo.
After applying this, you cannot see ""Modify Quitas"" menu in the project panel.
""Modify Quotas"" allowed() method refers to is_cloud_admin() [1], so at least I believe is_cloud_admin() does not work with the latest policy file."
1739108,2017-12-19 16:40:42 UTC,"There were some discussions around this in the team meeting last week [1][2].
[1] http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-12-13-20.00.log.html#l-157
[2] http://eavesdrop.openstack.org/irclogs/%23openstack-horizon/%23openstack-horizon.2017-12-13.log.html#t2017-12-13T21:00:58"
1739108,2017-12-20 21:33:53 UTC,"The other option is to look for a ""default"" rule definition. If not present, allow. If present evaluate against it. This is closest to current behavior and leaves the option for operators to set a ""default"" rule in horizon's copy of the policy file."
1739108,2017-12-20 20:14:57 UTC,"The default behavior for policy in horizon is that if the rule is not defined, the policy engine in horizon returns True which means the action is allowed. I see nowhere that value is overridden. I'm not sure you have found the root of the problem."
1739108,2017-12-19 16:44:04 UTC,One idea is to make the policies used by is_cloud_admin() and is_domain_admin() configurable. We can use 'admin_required' as a default value. It behaves in a backward-compatible way.
1739112,2020-12-12 04:26:50 UTC,"decreasing the importance of all ""malformed-source"" bugs"
1739219,2017-12-19 18:10:32 UTC,Do you still see a port tagged as 'network:dhcp' in the device_owner field with that IP?  Or do you see the other dhcp agents get notified when the 4th is removed?
1739219,2017-12-20 08:43:09 UTC,"Indeed I still had a network:dhcp port corresponding to the dhcp agent that was removed. So I deleted the port from the network, and that fixed the problem!"
1739219,2019-05-01 15:40:40 UTC,"I think this is a more significant bug than it might appear. In an environment with multiple dhcp-agents offering multiple dns servers per tenant network, this bug means that taking any agent offline - for maintenance, or rolling updates, or any number of other common operational scenarios - will result in instances continuing to rely on a now-unavailable DNS server. If they're unlucky enough to have that server listed first in their resolv.conf, this will produce real performance problems as every DNS request has to time out before the next server will be tried."
1739219,2019-07-01 06:33:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668359"
1739230,2017-12-21 15:36:17 UTC,"The extension seems to work well here. :)
Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1, 64bit"
1739230,2017-12-20 13:37:54 UTC,Thank you very much for your support.
1739230,2018-01-30 14:21:55 UTC,"Sorry for the delay: yes, I confirmed that the extension just works well. Thank you very much. :)"
1739230,2017-12-20 01:28:25 UTC,The initial request was to have the ability to add comment nodes at arbitrary positions in the document and not a single comment at the top (on the form of a new button 'add comment node' aside the existing button 'add new element node).
1739230,2017-12-19 19:02:15 UTC,What would be the use case for this functionality (or rather what part are you missing that could not be covered in a better way by one of the metadata fields available in the document properties)?
1739230,2017-12-20 02:43:45 UTC,Thanks for clarifying.
1739244,2018-11-21 18:44:44 UTC,Variants:
1739253,2017-12-20 09:06:47 UTC,"FWIW the cloud mentioned was indeed upgraded from Icehouse to Mitaka, and is running trusty"
1739253,2018-01-11 19:46:16 UTC,This appears to be fixed upstream as of Newton via bug https://bugs.launchpad.net/nova/+bug/1646255 for which the following patch was provided:
1739253,2018-01-11 19:53:34 UTC,I took a look at the code for Mitaka and while the patch won't cherry-pick cleanly a backport of the patch should be doable with some adjustments.
1739254,2017-12-19 18:34:45 UTC,That information is already available and slime takes advantage of it.
1739270,2017-12-27 19:34:29 UTC,"Confirmed -- most likely related to AppArmor, will continue to investigate."
1739270,2017-12-28 02:49:16 UTC,not sure why it didn't autoconfirm with comment above
1739270,2018-04-04 21:39:38 UTC,Same here:
1739277,2019-07-31 16:45:19 UTC,"That approach works much better, Bill, thanks. I've pushed a commit to implement it into the Angular Holdings View UI, and another to make the changes need to implement(as well as implementing it) into the AngJS Holdings View UI. Branch is here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/khuckins/lp1739277-org-select-class-callback"
1739277,2021-02-12 17:22:55 UTC,Rebased version here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/khuckins/lp1739277-org-select-class-callback-v2
1739277,2020-09-24 19:29:03 UTC,This one needs to be rebased before testing.
1739277,2020-02-18 13:30:57 UTC,"This works with the Angular version, but only in the AngJS version if the Experimental catalog is turned on."
1739277,2019-07-30 16:16:08 UTC,"Hi Kyle, I have reviewed the branch and have a suggestion about how we apply the styling the individual org units."
1739277,2019-06-26 17:45:05 UTC,I've pushed a branch here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1739277-bold-owning-libraries-in-holdings
1739277,2019-07-19 20:25:50 UTC,I've pushed in a separate branch an update providing the same functionality to the eg2 Angular client: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1739277-holdings-view-owning-libraries-not-marked-angular
1739277,2018-01-02 15:53:04 UTC,"After almost eight years in the Evergreen community, I'm still learning about features in the xul client. I never realized that the library dropdown in holdings maintenance bolded the branches that owned a copy of the title. Confirming that we don't see the same behavior for the 'show holdings at or below' library dropdown menu in the web client's holdings view."
1739288,2019-09-13 15:02:02 UTC,Here is a branch that adds a summary to the end of the bad barcodes list.
1739288,2020-07-24 20:37:39 UTC,"Pushed all the way to rel_3_4. Thanks, Jane, Josh, and Rogan!"
1739288,2020-01-10 18:40:00 UTC,Sign off pushed to user/rogan/lp1739288_report_invalid_barcodes_in_item_status_signoff
1739288,2019-11-07 15:24:44 UTC,I added a screen shot of the list of bad barcodes and summary.
1739288,2019-11-07 15:22:10 UTC,"Jane, this looks good and works well for me."
1739288,2019-10-26 16:59:01 UTC,"Thanks for this, Josh!"
1739288,2019-08-30 04:21:02 UTC,"Jane, I like your solution to this issue, I marked a couple other bugs as being duplicates of this one.  I like how you show them as they come up and not as a popup at the end."
1739288,2019-08-30 13:23:13 UTC,I just tested this out and it works great.  The only thing that may be nice would to be to have a final summary of the load in the case that there are bad barcodes.
1739288,2019-08-19 20:05:32 UTC,"For your viewing pleasure, here's a gif of my proposed solution."
1739288,2019-08-19 19:59:55 UTC,Here's a branch that does this: user/sandbergja/lp1739288_report_invalid_barcodes_in_item_status
1739288,2019-06-26 18:58:57 UTC,"We are also seeing files stop loading when it encounters a deleted item. THe file might have several hundred items but if the deleted item is 10th from the bottom (the file loads from the bottom), only 9 items load."
1739288,2019-04-01 19:12:11 UTC,"Elaine noted that if all items in the file have been deleted, nothing happens when the file is loaded to the item status screen.  I find that even if my file contains some undeleted items, along with some that have been deleted, nothing happens.  The file never loads and the progress bar never goes away."
1739288,2018-01-26 14:01:56 UTC,"If the file has a space before the barcode, the barcodes will also fail to load. However, if you manually enter a barcode with a space either before or after, it does scan as expected."
1739288,2018-01-26 13:39:01 UTC,"Not sure if this is should be a separate bug or not. If the file of barcodes has a space after a barcode, the web client reads the space as part of the number and does not return it, it fails as if it were not present. The XUL client ignores the space and loads the file."
1739288,2019-08-20 14:07:50 UTC,Love it!!
1739292,2019-08-19 18:25:16 UTC,Re-tested.  Looks good.  Merged to 3.2 and up.
1739292,2019-05-22 11:46:33 UTC,Confirmed in Evergreen 3.0
1739292,2019-05-22 11:52:34 UTC,Correction: confirmed in Evergreen  3.3.0
1739292,2019-07-11 15:42:57 UTC,I've pushed a branch here:
1739292,2019-07-15 20:37:37 UTC,"Thanks, Mike.  Looks great to me.  I've pushed a sign-off branch:"
1739297,2020-09-12 05:11:48 UTC,Closing because INVALID: Can't replicate.
1739297,2017-12-21 13:34:36 UTC,"Reproduced with Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1 64-bit."
1739297,2017-12-21 14:02:29 UTC,"Not reproduced with a newly created document.
with Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1 64-bit."
1739300,2017-12-20 00:20:02 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1739300,2017-12-20 09:47:44 UTC,packages linux-libc-dev and libc6-dev rather than build-essential; but these are not packages in ubuntu?!
1739300,2017-12-20 12:38:24 UTC,">packages linux-libc-dev and libc6-dev (..) these are not packages in ubuntu?!
"
1739300,2017-12-20 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1739300,2017-12-20 16:09:37 UTC,"Thx, Hans Joachim.
Problem with ubuntu-bug was, that i did not know the package to put this on."
1739300,2018-02-28 22:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1739300,2018-05-24 12:25:07 UTC,"due to the nature of the issue i have encountered, i am unable to run
apport-collect 1739300
and have changed the bug status to 'Confirmed' (for the second time)."
1739300,2018-05-24 12:30:31 UTC,"Setting the status to Confirmed, though i am the reporter.
This is slightly inconsistent. Brain hurts."
1739300,2018-07-02 11:45:21 UTC,please take this further or close it.
1739310,2019-09-07 22:19:51 UTC,"I was haunted by this bug for several years, yet I was not able to google the solution, because I am not a native English speaker and I did not know the English world ""crackling"" (shame on me) and I was not able to describe the sound degradation properly to Google."
1739310,2019-04-20 23:03:59 UTC,"I never used this feature, so I just uninstall with ""apt-get remove speech-dispatcher"". It's not a problem to me, but I reported the bug for 2 reason:"
1739310,2019-04-20 17:10:19 UTC,tI've had this problem for a number of years on a range of Ubuntu distros; I'm currently working from an Ubuntu install that I switched over to Xubuntu after some graphics issues with the standard window manager.
1739310,2018-06-26 04:03:58 UTC,I have the same issue on Xubuntu 18.04 and Debian Stretch. It occurs on a fresh install while watching a video in Firefox. Restarting Pulseaudio does fix the issue for me as well.
1739310,2018-06-26 03:54:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739310,2019-01-20 20:48:03 UTC,"Affects also Xubuntu 18.10, while playing MP3 in Audacious (no other application playing any sound). I discover 3 instances of speech-dispatcher in Pavucontrol, when distortion/crackling occurred. Stop playing, wait 10 seconds and resume playing helps to recover normal sound, but speech-dispatcher instances are still there."
1739316,2018-02-02 12:34:10 UTC,"OK, I took the liberty to specify that this bug affects the kerning of U+0320 a.k.a. ""curled Beta""."
1739316,2020-09-10 15:32:49 UTC,"Indeed the attachment ""Fixed version"" is a patch. Please check if you're satisfied with it."
1739316,2017-12-20 00:19:38 UTC,"The attachment ""Fixed version"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1739322,2018-02-07 13:49:25 UTC,apport information
1739322,2018-02-07 13:49:21 UTC,apport information
1739322,2018-02-07 13:49:22 UTC,apport information
1739322,2018-02-07 13:49:23 UTC,apport information
1739322,2018-02-07 13:49:24 UTC,apport information
1739322,2018-02-07 13:49:08 UTC,apport information
1739322,2018-02-15 15:25:04 UTC,"A new xorg version has been installed yesterday 14.02.2018.
I could make a video of the problem on my screen before that installation, and have joined it.
The bug as posted is still active with the new version.
It is not easy to reproduce. Sometimes it comes often, sometimes not.
Open and close several windows, switch between tasks..., or verify source code.
So long I remember, this bug appeared before september 2017. No problem in year 2016.
On the video one can see that abnormal blinking stops on next going into sleep state."
1739322,2018-02-15 18:16:43 UTC,Pierre Wilch:
1739322,2018-02-16 00:02:31 UTC,"Christopher M. Penalver,"
1739322,2018-02-16 00:20:22 UTC,Pierre Wilch:
1739322,2018-02-18 01:29:28 UTC,"Christopher M. Penalver,"
1739322,2018-02-07 13:49:20 UTC,apport information
1739322,2018-02-07 16:16:47 UTC,Pierre Wilch:
1739322,2018-02-07 13:49:17 UTC,apport information
1739322,2018-02-07 13:49:06 UTC,apport information
1739322,2018-02-07 13:49:15 UTC,apport information
1739322,2018-02-07 13:49:14 UTC,apport information
1739322,2018-02-07 13:49:13 UTC,apport information
1739322,2018-02-07 13:49:12 UTC,apport information
1739322,2018-02-07 13:49:11 UTC,apport information
1739322,2018-02-07 13:49:09 UTC,apport information
1739322,2018-02-07 13:49:07 UTC,apport information
1739322,2018-02-18 14:10:16 UTC,"Pierre Wilch, given this issue only happens when using Unity, I'll reassign to Unity so a specialist may review."
1739322,2018-02-07 13:49:04 UTC,apport information
1739322,2018-02-07 13:49:03 UTC,apport information
1739322,2018-02-07 13:49:02 UTC,apport information
1739322,2018-02-07 03:47:03 UTC,"Pierre Wilch, thank you for reporting this and helping make Ubuntu better."
1739322,2018-02-07 13:49:16 UTC,apport information
1739323,2018-09-28 16:13:29 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/539013
Reason: Looks dead. I'm cleaning up old changes to get ready for ocata-em."
1739323,2018-05-02 12:04:42 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1739323,2017-12-20 14:41:20 UTC,You aren't by chance running with some multiple scheduler thread workers patch are you?
1739323,2018-02-15 23:53:43 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1739323,2017-12-20 14:39:37 UTC,There is nothing else in the HostManager code that modifies the host_state_map so I don't see how it could be getting modified concurrently.
1739323,2018-01-29 20:12:58 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/539013"
1739323,2018-01-13 00:54:17 UTC,"Reviewed:  https://review.openstack.org/529635
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=52679374a404b14578c834f47d6d4d35e85df2e1
Submitter: Zuul
Branch:    stable/ocata"
1739323,2018-01-09 23:09:41 UTC,"Reviewed:  https://review.openstack.org/529626
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b6a1a192955da3d18f50dfa3130c95fc15d7a66a
Submitter: Zuul
Branch:    stable/pike"
1739323,2017-12-21 20:49:56 UTC,"Reviewed:  https://review.openstack.org/529352
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d72b33b986525a9b2c7aa08b609ae386de1d0e89
Submitter: Zuul
Branch:    master"
1739323,2017-12-21 16:22:18 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/529635"
1739323,2017-12-21 15:40:00 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/529626"
1739323,2017-12-20 15:24:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529352"
1739323,2017-12-20 14:45:30 UTC,I think the HostManagerChangedNodesTestCase unit tests would have also caught a breakage here.
1739323,2017-12-20 00:51:52 UTC,I assume your second to last link was this?
1739323,2017-12-20 00:53:48 UTC,Correct!
1739323,2017-12-20 00:54:13 UTC,Looks like this has been around since Grizzly:
1739323,2017-12-20 00:55:16 UTC,https://github.com/openstack/nova/commit/4660333d0d97d8e00cf290ea1d4ed932f5edc1dc#diff-978b9f8734365934eaf8fbb01f11a7d7L624
1739323,2018-01-27 17:17:03 UTC,"Reviewed:  https://review.openstack.org/533371
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c98ac6adc561d70d34c724703a437b8435e6ddfa
Submitter: Zuul
Branch:    master"
1739323,2017-12-20 14:36:06 UTC,"Actually I'm not sure how you're hitting this, unless a concurrent thread is modifying the host_state_map dict at the same time."
1739323,2018-01-26 00:43:45 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1739323,2018-02-08 18:36:37 UTC,"Reviewed:  https://review.openstack.org/539005
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bf65fdd59ea7d12f7420fcfe2602a5f00cc61055
Submitter: Zuul
Branch:    stable/pike"
1739323,2018-01-29 19:23:50 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/539005"
1739325,2018-07-05 23:08:45 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/580525"
1739325,2017-12-20 01:23:54 UTC,Here is a prettier form of the json:
1739325,2017-12-20 01:26:36 UTC,Yeah the workaround is to set this in nova.conf:
1739325,2018-01-22 10:45:14 UTC,@Mohammed Naser: Do you have any data about which OpenStack version was deployed when the Flavor in question was created? Also do you have any data about which OpenStack version was deployed when the Instance in question was created from this Flavor?
1739325,2018-01-25 02:42:28 UTC,"I had the same thing happen in my environment.
The environment was upgraded to Pike all they way back from Juno (one by one, over time).
The flavor was created ~2014 on whatever was stable then."
1739325,2018-01-29 14:37:03 UTC,@Daniel: Thanks for the extra info. I will check the data migrations affecting the flavor data during upgrade.
1739325,2018-02-22 19:35:11 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/529194"
1739325,2018-06-07 10:19:10 UTC,This is also visible in tssurya's environment. I'm wondering if we can implement a nova-manage heal-instance-flavor command for these environment as I'm not sure I will be able to find the root cause why the disable field is missing from these flavors.
1739325,2018-07-05 23:33:16 UTC,"Reviewed:  https://review.openstack.org/579925
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8df21c1e5fc46f2774a7653e1c9a4c2ac0b5dbfd
Submitter: Zuul
Branch:    master"
1739325,2018-07-03 16:25:44 UTC,"Looking at juno-eol code, I came across what I think might result in ""ValueError: Field `disabled' cannot be None""."
1739325,2018-07-03 17:05:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/579925"
1739325,2018-07-05 23:04:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/580522"
1739325,2018-07-05 23:05:18 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580523"
1739325,2017-12-20 01:21:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529194"
1739325,2018-07-08 05:01:49 UTC,"Reviewed:  https://review.openstack.org/580522
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b2146b02a943c784b6c6fe19ec9e5247bd8e503d
Submitter: Zuul
Branch:    stable/queens"
1739325,2018-09-26 10:43:47 UTC,This issue was fixed in the openstack/nova 15.1.4 release.
1739325,2018-09-24 14:47:24 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1739325,2018-09-24 14:46:50 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1739325,2018-08-28 15:25:00 UTC,"Reviewed:  https://review.openstack.org/580525
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2164c964ae009eb01b5271e41103cce9e92c1b6
Submitter: Zuul
Branch:    stable/ocata"
1739325,2018-08-28 13:27:54 UTC,I've reported a new bug for the is_public issue:
1739325,2018-08-28 13:23:59 UTC,"Same issue, very old instances wouldn't have the embedded flavor.is_public field stored because of this whitelist:"
1739325,2018-08-27 15:19:25 UTC,"Same for the ""is_public"" field. This is also missing."
1739325,2018-07-30 16:07:38 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1739325,2018-07-25 14:35:45 UTC,"Reviewed:  https://review.openstack.org/580523
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=06387be5907f3b9f05bded85ff3d3bec132fb60b
Submitter: Zuul
Branch:    stable/pike"
1739336,2019-12-04 08:55:42 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/583130
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1739336,2018-10-04 15:32:34 UTC,"Reviewed:  https://review.openstack.org/583122
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=183c24d2d05cc31f0fdbedcdc3e4980eff2f8867
Submitter: Zuul
Branch:    master"
1739336,2018-10-04 10:55:24 UTC,"Reviewed:  https://review.openstack.org/583120
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=fa36d935317886b9afc3779833724f56ed1c960a
Submitter: Zuul
Branch:    master"
1739354,2018-06-06 18:12:36 UTC,It looks like this is actually in the backwards_compat group: https://github.com/openstack-dev/pbr/blob/ee26945cb3b290983a4b6d71bec2ed5aaf163989/pbr/util.py#L131
1739364,2019-11-01 09:27:50 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1739364,2020-01-01 04:17:27 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1739368,2017-12-20 07:54:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529254"
1739368,2019-04-05 21:17:03 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/529254"
1739375,2018-01-20 07:40:08 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1491
1739375,2017-12-21 07:20:40 UTC,Before it dies:
1739375,2017-12-20 14:10:48 UTC,"Hi,
Could you please paste the output of dmesg, to see the OOM killer message?"
1739380,2018-09-10 05:27:18 UTC,Seeing this with a 2.3.8 to 2.4.3 upgrade: https://pastebin.canonical.com/p/nDJsp6gt66/
1739380,2018-01-13 04:42:13 UTC,"Looking at the code to dial Mongo, I think it is correct:
  c, err := net.DialTimeout(""tcp"", addr, opts.Timeout)
  if err != nil {
   logger.Warningf(""mongodb connection failed, will retry: %v"", err)
   return nil, err
  }
  if tlsConfig != nil {
   cc := tls.Client(c, tlsConfig)
   if err := cc.Handshake(); err != nil {
    logger.Warningf(""TLS handshake failed: %v"", err)
    if err := c.Close(); err != nil {
     logger.Warningf(""failed to close connection: %v"", err)
    }
    return nil, err
   }
   c = cc
  }"
1739380,2018-01-13 04:27:19 UTC,"As a summary comment, my first guess is that if we get an error during TLS negotation, we are failing to close the underlying socket."
1739380,2020-02-26 22:34:19 UTC,Marking as Won't Fix for 2.3 and 2.4 series since we are not planning to make any further releases in these series at this stage.
1739380,2018-01-13 04:26:50 UTC,"For the file handle issues, digging through the log file from bug #1742604"
1739380,2018-01-11 20:21:43 UTC,"Unfortunately this also happened with 2.2.9, so it wasn't the iterators, but is something else."
1739380,2018-01-04 02:07:38 UTC,https://github.com/juju/juju/pull/8255
1739380,2018-01-03 00:20:34 UTC,"I'm guessing, quite wildly I must add, that during the upgrade process, we get the credentails for every model for potential model upgrades."
1739380,2018-01-03 00:18:33 UTC,Did a quick search of the state package on the 2.2 branch. The following functions aren't closing the iterator:
1739380,2017-12-20 13:32:58 UTC,"Indeed, if there are 20k file handles open to Mongo something very odd is going on internally. The mgo socket pool that is meant to keep a certain number of connections open is limited to 4000 connections."
1739380,2018-09-04 22:17:31 UTC,"We haven't heard of this problem for a while, it is possible that it has been fixed inadvertantly."
1739401,2017-12-20 12:25:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1739406,2017-12-21 20:34:58 UTC,"So at a guess you have a few 3rd party plugins installed that are *NOT* delivered as part of Terminator. One of these is more than likely still trying to operate using gtk2 style imports. Find it and disable it and the menu will probably start working again. As the message says, look for imports referencing gobject, instead of GObject. Of course, even better would be to check for an update from the original dev, and if one doesn't exist, perhaps even provide a fix to them. Note that simply changing the import is unlikely to work on it's own. The code will very likely need other changes."
1739410,2018-05-26 13:39:47 UTC,I miss too the list of all available compression codecs in the advance tab. Just wish could also add also a little bar to easily set compression speed vs ratio
1739416,2017-12-20 16:21:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1739417,2020-08-27 06:35:42 UTC,"can't not reproduce this issue in 20.04,
but I did observe this issue in 14.04"
1739417,2019-12-02 18:32:07 UTC,Comment #2 is spam for some website about printer errors.
1739417,2018-08-21 06:54:16 UTC,Method 1: I suggest you run Printer troubleshooter and check if it helps.
1739431,2018-02-26 14:29:24 UTC,"The repository is correct, but you need to add the correct keys.
That is not possible via config at the moment, I think, I added the key via ssh
# wget -q -O- 'https://download.ceph.com/keys/release.asc' | sudo apt-key add -
Greetings,"
1739442,2017-12-20 16:17:38 UTC,"Even when the volume-type is associated to an encryption-volume-type detailing the method of encryption expected to be present within the volume, at least for front-end encryption?"
1739442,2017-12-20 15:33:23 UTC,"I don't think Cinder is the right place for this. Cinder provides block storage, optionally with an image written to it. It should not ever be responsible for formatting a volume."
1739442,2018-01-04 19:10:02 UTC,"Sean, just to reiterate, the end user is still presented with a RAW block storage from the volume. Any formatting that I'm suggesting take place here is of the encryption layer around said volume that is not visible to end users. c-vol already does this when copying image data into an encrypted volume FWIW."
1739446,2018-03-29 21:36:07 UTC,+1 for Jacek's suggestion. this would then mean:
1739446,2018-01-11 17:31:32 UTC,So maybe something like this:
1739446,2018-01-11 17:28:29 UTC,"For SRE like myself I think those would help:
* log URL it tried posting to and reason it failed (timeout, connection refused, host not found, 500 response). This information would be useful for troubleshooting
* remove ""SUCCESS"" from ""SUCCESS: no cache found"". It's in caps so stands out. If I understand it correctly this SUCCESS is not that relevant here
* I think ""attempting to read from cache"" and ""no cache found"" messages are ""INFO"" or similar rather than ""WARNINIG"" but I may be misunderstanding them."
1739446,2018-01-09 15:23:57 UTC,"Jacek,
Do you have a suggestion on what they should say ?"
1739451,2019-10-10 10:21:53 UTC,the tests now check for the existence of the package before installing it.
1739451,2018-01-15 14:58:43 UTC,This is indeed something we are doing in the tests - do you have a suggestion how to detect linux-oem ? Then we can skip this step easily.
1739453,2018-04-02 13:19:08 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1739453,2018-03-30 17:47:11 UTC,"Reviewed:  https://review.openstack.org/530794
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cedcef7ecb9673530ca0241c2976dfd862c4f75a
Submitter: Zuul
Branch:    stable/pike"
1739453,2018-01-26 00:43:44 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1739453,2018-01-02 20:20:44 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/530794"
1739453,2017-12-27 11:11:13 UTC,"Reviewed:  https://review.openstack.org/529397
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3491f3d6f2334b80c364deeb21d65004262c2846
Submitter: Zuul
Branch:    master"
1739453,2017-12-20 18:49:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529397"
1739453,2017-12-20 17:32:44 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Unable%20to%20replace%20resource%20claim%20on%20source%20host%5C%22%20AND%20tags%3A%5C%22screen-n-super-cond.txt%5C%22&from=7d
1739453,2017-12-20 17:26:13 UTC,"Ah, okay, I think it's this: If db deadlock happens after at least one trip through the loop at https://github.com/openstack/nova/blob/609ddc2244bf9ba84d66cced52e7d4e2987ec669/nova/objects/resource_provider.py#L2061 then a member of the allocs list will have a .id attribute the next time the method is tried."
1739453,2017-12-20 17:20:54 UTC,"This is tres bizarre. In order for AllocationsList._set_allocations to throw ObjectActionError from that line, the incoming Allocation objects need to have an 'id' field, which ought to be impossible. More details to come."
1739453,2017-12-20 17:08:23 UTC,"I'm not sure how this happens, or if https://review.openstack.org/#/c/528089/ might fix this."
1739458,2017-12-20 17:27:59 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
 QMessageLogger::fatal (this=this@entry=0x7ffc10d9a9e0, msg=msg@entry=0x7f2d9755ac28 ""Cannot mix incompatible Qt library (version 0x%x) with this library (version 0x%x)"") at global/qlogging.cpp:796
 QObjectPrivate::QObjectPrivate (this=<optimized out>, version=<optimized out>) at kernel/qobject.cpp:215
 QSvgRendererPrivate::QSvgRendererPrivate (this=0x55a023938540) at qsvgrenderer.cpp:110
 QSvgRenderer::QSvgRenderer (this=0x7ffc10d9aa90, filename=..., parent=0x0) at qsvgrenderer.cpp:137"
1739458,2017-12-21 15:50:20 UTC,"Sorry, but I don't care enough right now about a new kernel, moreover yesterday qt switched to .2 to .3 minor release, this caused various crashes."
1739458,2017-12-21 15:50:34 UTC,Reopen if you still have this issue after updating bionic
1739466,2017-12-20 21:25:02 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1739466,2017-12-20 18:30:07 UTC,This change was made by a bot.
1739466,2017-12-22 18:37:45 UTC,"Thank you, everything now work fine!
I download the latest mainline kernel v4.15-rc4."
1739468,2018-11-22 16:53:24 UTC,I see this when I try to install Microstack snap on Bionic
1739468,2017-12-21 01:47:47 UTC,Thanks for the bug report. Those messages appear to be from 'gnome-shell-extension-appindicator' so reassigning there.
1739468,2017-12-29 14:57:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739468,2018-04-29 10:33:43 UTC,"This code in gnome-shell-extension-appindicator-17.10.3 doesn't make sense, because the ""reset"" function doesn't do anything:"
1739468,2018-06-21 23:15:21 UTC,"This is pretty bad.  I see 8-10 messages per second in /var/log/syslog.  That makes it difficult to see anything else, potentially causing a security issue."
1739468,2018-07-27 08:46:47 UTC,I could get the messages to stop by selecting quit on some cpu/network monitoring icon at the top right.
1739468,2018-09-04 17:58:00 UTC,This problem is compounded by the fact that rsyslog is duplicating journal logging. Getting huge log files.
1739468,2018-10-21 00:24:44 UTC,"gnome-shell[11642]: [AppIndicatorSupport-WARN] Item :1.91/org/ayatana/NotificationItem/chrome_app_indicator_1 is already registered
gnome-shell[11642]: [AppIndicatorSupport-WARN] Attempting to re-register :1.91/org/ayatana/NotificationItem/chrome_app_indicator_1; resetting instead"
1739468,2019-09-14 23:12:07 UTC,"@kenjo (ken-kenjo) found the solution for me.  The error shows up every second in syslog.  However, when I quit the Gnome shell extension 'System Load Indicator 0.4', it stops."
1739468,2019-12-08 03:30:53 UTC,"Why is this low importance when anyone who has this issue should be quiting the application rendering it useless, seems pretty high to me. What else could possibly trump this?"
1739468,2020-03-11 18:55:32 UTC,This has been fixed upstream v32 version and released in ubuntu with version 32-1
1739482,2017-12-20 20:56:42 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22VolumeBackendAPIException%3A%20Bad%20or%20unexpected%20response%20from%20the%20storage%20volume%20backend%20API%3A%20Create%20export%20of%20volume%20failed%20(Failed%20to%20create%20iscsi%20target%20for%20volume%5C%22%20AND%20tags%3A%5C%22screen-c-vol.txt%5C%22&from=7d
1739482,2018-12-14 05:17:08 UTC,"Reviewed:  https://review.openstack.org/624809
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=206f980cc2f09610ffb86cfc7728222fd39eee4f
Submitter: Zuul
Branch:    master"
1739482,2018-12-13 18:06:59 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/624809
Reason: Must have done it too quickly."
1739482,2018-12-13 18:05:58 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/624809
Reason: Quick recheck"
1739482,2018-12-12 20:57:12 UTC,This could be related to the root issue in bug 1763712 where lvchange is taking nearly 60 seconds to complete. cinder-backup calls cinder-volume initialize_connection using an RPC call so it is a very similar failure.
1739482,2018-07-10 16:13:39 UTC,"In this case, we might want to consider leveraging the new heartbeat capability in oslo.messaging. See how nova is using that here for potentially long RPC calls during live migration:"
1739482,2018-07-10 16:37:01 UTC,Update query:
1739488,2018-05-02 21:44:16 UTC,Still present in 18.04 final release.
1739488,2018-04-18 06:24:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739488,2018-04-18 06:39:15 UTC,"As of 2018-04-17, this is still present in 18.04 beta."
1739491,2018-01-04 12:24:32 UTC,I think that the stonith support has gradually bit rotted since its original implementation against a much older version of MAAS that is currently in 16.04.
1739494,2017-12-20 22:34:47 UTC,"The offending version of libseccomp2 is still in xenial-proposed, but snapd on most architectures statically links against it. Unfortunately the bug for the libseccomp2 SRU is still in verification-needed: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1682102."
1739494,2019-12-10 08:56:39 UTC,The snapd package is installable again on powerpc. We install only a transitional package there though because we cannot support powerpc due to the lack of upstream powerpc support in the go compiler (only gccgo is supported).
1739505,2019-09-30 09:15:22 UTC,"Tested fixed package from proposed (as per Testcase) on Bionic and Disco, and can verify that the segfault is fixed and output correct."
1739505,2018-02-23 14:21:24 UTC,"bsd-csh is still segfaulting on the ""eval"" command in the 18.04 daily snapshot."
1739505,2018-02-23 14:22:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739505,2018-10-21 23:41:34 UTC,This worked in 16.04:
1739505,2019-04-18 03:15:02 UTC,I've run into this myself in Ubuntu 18.04 and 18.10.
1739505,2019-07-26 06:23:38 UTC,"I've found the cause of the problem. It can be fixed by grabbing the
latest csh sources from OpenBSD and removing one of the Debian patches."
1739505,2019-07-26 07:25:21 UTC,I've submitted a report for this same bug on Debian 10.
1739505,2019-09-21 11:55:25 UTC,This bug was fixed in the package csh - 20110502-4ubuntu1
1739505,2019-09-24 18:29:44 UTC,"Hello timobaumann, or anyone else affected,"
1739505,2019-09-24 18:31:02 UTC,"Hello timobaumann, or anyone else affected,"
1739505,2019-05-30 09:08:16 UTC,"I can confirm this bug is present, and more serious than what you think ..."
1739505,2019-10-03 08:08:27 UTC,This bug was fixed in the package csh - 20110502-4ubuntu0.19.04.1
1739505,2019-10-03 08:08:33 UTC,"The verification of the Stable Release Update for csh has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1739505,2019-10-03 08:57:12 UTC,This bug was fixed in the package csh - 20110502-3ubuntu0.18.04.1
1739506,2017-12-21 21:55:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739516,2017-12-21 18:12:27 UTC,"This is true that hostname is not set before networking comes up.
I would like to fix this, but there are a couple things to consider
a.) network datasources
   currently there are some datasources that run only after networking comes up. As it is right now it is ""too late""to read the hostname from the network metadata service and then update the system hostname before dhcp would run."
1739516,2017-12-21 22:18:28 UTC,"For a and d, sure if finding out what the hostname needs to be involves having the network up, there's nothing that can be done to avoid this."
1739516,2018-06-19 17:52:24 UTC,I just stumbled over this bug as well.
1739519,2017-12-29 20:01:26 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1739521,2017-12-22 16:32:45 UTC,problem solved by removing opencv2 dependency from manifest.xml in phidgets ros package
1739530,2017-12-21 04:26:38 UTC,"i try like what you said, this is the result not complete because i can only copy some of them,"
1739530,2017-12-21 04:07:33 UTC,There is apparently some corruption in the list's request.pck file resulting in a held message with a non-numeric request ID.
1739530,2017-12-21 04:11:32 UTC,"In my prior comment, 'LIST_HOST' is the cPanel list name. In this case 'marketing_ccsindo.com'."
1739530,2017-12-21 04:59:54 UTC,The entries that begin with things like
1739534,2017-12-21 22:29:28 UTC,Thank you! Using the full'export' line in the terminal worked! It now seems like the extended mouse up/down issue is resolved.
1739534,2017-12-21 08:17:11 UTC,to switch a Terminal session to Java 8 (which must be installed ;-):
1739545,2017-12-21 08:23:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529504"
1739545,2020-03-18 08:47:16 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/529504
Reason: This is a pretty old patch with negative review. Feel free to restore it (or ask gibi on irc to restore it) if you still working on it."
1739551,2017-12-24 00:13:52 UTC,Try running
1739560,2018-09-12 18:48:08 UTC,"very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update."
1739560,2017-12-21 08:30:05 UTC,This change was made by a bot.
1739560,2018-09-13 07:44:45 UTC,"This is still valid,
http://10.246.72.4/test-results/3.13.0-158.208-generic/ms10-35-mcdivittB0-kernel__3.13.0-158.208__2018-09-12_11-15-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html"
1739560,2019-09-05 06:17:26 UTC,"With the libhugetlbfs updated recently, this will need to be revisited."
1739560,2020-07-24 20:45:04 UTC,"I have not seen this occur on the -aws nitro backed arm64 instances.  Giving that mcdivitt is EOL, killing off this bug."
1739563,2019-06-14 02:39:54 UTC,"Change abandoned by renminmin (<email address hidden>) on branch: master
Review: https://review.opendev.org/529517"
1739563,2017-12-21 09:12:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529517"
1739570,2018-01-02 16:11:21 UTC,You may need to run the following from a terminal:
1739570,2017-12-21 09:00:04 UTC,This change was made by a bot.
1739576,2018-01-09 15:24:37 UTC,"In a case like rescue, we need to ensure we trigger DHCP for a node upon IPA exit, but that too is ramdisk dependent since the commands and environment vary. I'm -1 to adding code into IPA to attempt to trigger DHCP when the ramdisk could have different constraints."
1739576,2018-01-23 05:58:08 UTC,"Change abandoned by yuan liang (<email address hidden>) on branch: master
Review: https://review.openstack.org/529535"
1739576,2018-01-08 16:06:49 UTC,"I don't quite agree with this. Network configuration vastly differs depending on the way IPA is built. For example, IPA built with diskimage-builder have the dhcp-all-interfaces element included, so all interfaces try to DHCP. Running dhclient may have unpredictable results there. I think it should be solved by every build method separately. Could you please update the bug accordingly?"
1739583,2019-06-07 20:26:00 UTC,Ocata has been EOL for a while
1739587,2017-12-21 10:20:54 UTC,"Just ignore it:
The reason might be, that you are currently working on a smaller screen, than that where the shots where taken."
1739588,2019-06-14 02:40:03 UTC,"Change abandoned by renminmin (<email address hidden>) on branch: master
Review: https://review.opendev.org/529539"
1739588,2017-12-21 10:28:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/529539"
1739592,2017-12-21 20:53:26 UTC,CENTOS 7 package
1739593,2018-02-19 14:42:01 UTC,So at this point I think we're just waiting for review of the stable/pike fix and then a similar fix backported to stable/ocata? Looks like we can probably get moving on CVE assignment from the VMT end in that case. Thanks!
1739593,2018-05-02 12:00:33 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1739593,2018-04-20 14:05:37 UTC,"Reviewed:  https://review.openstack.org/539893
Committed: https://git.openstack.org/cgit/openstack/ossa/commit/?id=c5f504bf1d2769191467b6a9749a1bb440750991
Submitter: Zuul
Branch:    master"
1739593,2018-04-20 05:25:05 UTC,"Reviewed:  https://review.openstack.org/561604
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0225a61fc4557c1257383a654f0741f7ef2ddeac
Submitter: Zuul
Branch:    stable/ocata"
1739593,2018-04-17 20:52:38 UTC,"Reviewed:  https://review.openstack.org/543569
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5b64a1936122eeb35f37a09f9d38159e1a224c58
Submitter: Zuul
Branch:    stable/pike"
1739593,2018-04-16 12:31:36 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/561604"
1739593,2018-04-12 16:57:40 UTC,"CVE-2017-18191 is already reserved for this and can, I suppose, be included in that release note already. You're right that OSSA numbers have historically been assigned at the time of publication so I would consider either amending the release note later and not blocking the patch on it, or we can attempt to work out some sort of coordination mechanism for earlier OSSA assignment."
1739593,2018-04-12 16:20:20 UTC,"I'm +1 now on the stable/pike backport https://review.openstack.org/#/c/543569/ - my +2 is pending discussion about a 'security' release note in the patch that mentions the CVE / OSSA which isn't yet published, and sounds like we might have a chicken-and-egg with that until the stable/ocata backport is proposed?"
1739593,2018-04-25 09:21:06 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1739593,2018-02-11 01:22:27 UTC,"If swapping encrypted volumes is already unusable in stable, then I don't see any significant concerns with making it safely unusable. Sounds far less likely to introduce regressions in stable too."
1739593,2017-12-21 11:33:54 UTC,"I think the priority here is that the user loses their data. The DoS potential is real, but relatively inefficient. I think we could use a CVE to communicate the problem to users, but I don't think this particular issue is important enough to jump through secrecy hoops while we work on the data-loss bug."
1739593,2017-12-21 13:42:23 UTC,"Agreed, the data loss bug is of much higher importance than the potential DoS, just wanted to ensure VMT members were at least aware of the possibility for this to be used maliciously. If there are no further concerns or objections then I'm fine with early disclosure so we can fix this as a priority, in the open."
1739593,2017-12-21 14:24:33 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1739593,2017-12-21 16:04:31 UTC,"Given Matthew and Lee are both suggesting we switch to our public workflow in hope of getting the data loss problem solved in a more timely manner (at the expense of disclosing a somewhat inefficient DoS risk), I've gone ahead and subscribed ossg-coresec reviewers to get their input first."
1739593,2017-12-21 16:10:54 UTC,Have these problems have existed since the introduction of LUKS support? Or did the ability to perform a volume-update/swap_volume come later? Are all currently supported stable branches (let's say back to stable/ocata anyway since stable/newton is likely to finally get EOL'd by the time this is fixed) at risk from this?
1739593,2017-12-21 16:30:57 UTC,Yes this has been an issue since the introduction of the LUKS encryptors and is present all the way back to stable/ocata (and stable/newton FWIW).
1739593,2018-01-04 18:31:49 UTC,Any additional thoughts on this? I'd like to open this up and get the bug fix in sooner rather than later if possible.
1739593,2018-01-04 18:47:38 UTC,"I know it's been holiday time for a lot of people, but given it's been two weeks at this point and we've got some consensus from the reporter and another core reviewer as well as some of the VMT, I'm going ahead and switching this one to our public workflow ending the embargo."
1739593,2018-01-04 20:20:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531233"
1739593,2018-01-15 15:56:50 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.openstack.org/531233
Reason: ca323b87fa85a454fca9d46ada3677f18fe50022"
1739593,2018-01-15 16:21:45 UTC,Lee: Is https://review.openstack.org/460243 aimed at solving this instead now?
1739593,2018-01-15 17:28:07 UTC,"Yes, the refactor in https://review.openstack.org/460243 will resolve this."
1739593,2018-01-22 16:07:22 UTC,data loss bugs are critical.
1739593,2018-02-12 17:13:09 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/540861"
1739593,2018-02-12 18:15:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/543569"
1739593,2018-01-25 15:37:46 UTC,Related BZ where swap volume won't work with native LUKS encrypted volumes if you're using new enough libvirt/qemu:
1739593,2018-01-26 00:43:23 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1739593,2018-01-31 06:08:19 UTC,"Backport to stable branches doesn't seems trivial, is this planed to be fixed in stable/pike and stable/ocata?"
1739593,2018-01-31 10:19:42 UTC,I wanted to give the master change sometime to bed in and while there are conflicts there don't appear to be any show stoppers AFAICT. I'll try to post something for review in the coming week so other stable cores can review.
1739593,2018-02-01 10:30:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/539893"
1739593,2018-02-05 14:00:34 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/540861"
1739593,2018-02-05 15:51:31 UTC,"Rather than backport these libvirt driver changes to stable branches, which are non-trivial refactors of the code, why can't we just put something in the stable branches that explicitly fails a swap volume of encrypted volumes? If swapping encrypted volumes doesn't work until queens, and only then if you're not using native luks encryption, it seems OK to just deny the operation outright in stable branches as a resolution to this bug for pike and ocata."
1739593,2018-01-22 22:21:46 UTC,"Reviewed:  https://review.openstack.org/460243
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd3eb60c2c00bcccfa9ccd4bf9d1a96ae7a5cd88
Submitter: Zuul
Branch:    master"
1739607,2018-05-30 22:01:56 UTC,A related bug with additional information about columns missing in Bills is https://bugs.launchpad.net/evergreen/+bug/1662535
1739607,2019-01-08 12:41:17 UTC,Here is a screen shot of the Checkout/Renewal Library with junk in the column
1739607,2019-04-19 19:46:29 UTC,"On the 3.2 patron bills screen, I am not seeing a problem with the Owning Library. I am still seeing that the Circulation Library is blank if the Checkout/Renewal Library is chosen, however the Checkout/Renewal Library column is filled in with the appropriate data."
1739607,2019-08-01 22:50:18 UTC,"I took a look at today's master, and found the following:"
1739607,2019-08-21 17:40:22 UTC,Here is a branch for this: user/sandbergja/lp1739607_missing_columns_in_patron_record
1739607,2019-10-01 18:34:01 UTC,Looks good to me so it's been pushed to rel_3_1...master; thanks Jane and Josh!
1739607,2019-09-13 21:31:09 UTC,"Hello, signoff branch at user/stompro/lp1739607_missing_columns_in_patron_record_signoff"
1739609,2018-01-10 13:22:36 UTC,An additional field that's requested for cataloging workflows:
1739609,2018-10-29 15:26:54 UTC,I looks like Copy Status was added via bug 1743782.
1739609,2019-11-12 16:23:48 UTC,Confirmed that parts is still not available as a column in EG 3.3.4.
1739609,2019-11-21 20:06:20 UTC,"As far as adding Monographic parts goes, I found that because of the work done by Kyle in bug 1789256, it is as simple as adding the same <eg-grid-field entry as listed in that bug to get Monographic parts added to the check in grid."
1739609,2020-01-07 14:35:14 UTC,Tested on Evergreen 3.4.1. This looks good to me.
1739609,2020-01-19 13:21:10 UTC,"Looks good to me, too.  Thanks, Josh and John!  I've added this to master, rel_3_4, and rel_3_3."
1739613,2017-12-21 16:19:14 UTC,"The attachment ""rdist-6.1.5-15.filesys.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1739615,2017-12-21 14:30:03 UTC,This change was made by a bot.
1739615,2020-01-09 06:43:19 UTC,"4.13 EOL,
please feel free to open a new bug if you're still encounter this issue with newer releases."
1739620,2021-02-18 16:45:56 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1739620,2018-01-23 17:40:31 UTC,I verified a couple logs on oooq jobs don't have undercloud/var/log/swift so I am testing a quick fix to post-deploy script just like https://review.rdoproject.org/r/#/c/11010/4/openstack-swift.spec
1739624,2017-12-24 01:15:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739624,2019-08-28 04:29:59 UTC,Removed from Ubuntu
1739624,2019-08-28 04:29:52 UTC,https://bugs.launchpad.net/ubuntu/+source/lernid/+bug/1739622
1739628,2019-09-10 02:20:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739628,2019-09-10 02:22:08 UTC,I've been using this as a workaround.
1739629,2017-12-21 17:12:49 UTC,"Hi,"
1739629,2020-04-02 12:31:46 UTC,Per previous comment the issue has been fixed since 18.0.0 release.
1739629,2017-12-21 23:44:03 UTC,"FWIW, quick patch up at https://review.openstack.org/#/c/529722/"
1739629,2017-12-21 17:23:25 UTC,Why is that test not excluding the udpated_at column?
1739629,2017-12-21 17:20:26 UTC,"I agree that it makes no sense to compare the original list against the retrieved list and include the updated_at field in that comparison, since that's likely to change internally to Cinder if anything updates the volume between the original fetched list and the next query (a periodic task could update the volume for some reason between those two calls)."
1739629,2018-03-01 16:50:16 UTC,This issue was fixed in the openstack/tempest 18.0.0 release.
1739634,2018-10-29 13:08:10 UTC,Yaru doesn't have unity specific styles (yet). See here: https://github.com/ubuntu/yaru/issues/701
1739635,2018-12-12 15:49:14 UTC,"Why yes, it is generally the same, except I submitted 12 months ago, heh ;P"
1739635,2018-12-12 14:50:52 UTC,"Thank you for your bug report, that upstream feature request seems similar https://gitlab.gnome.org/GNOME/gnome-control-center/issues/94"
1739635,2018-12-12 18:33:02 UTC,"GNOME is using gitlab.gnome.org, Ubuntu is distributing their softwares and contributing improvements/fixed but the better place to discuss changes is upstream"
1739644,2018-01-09 20:26:10 UTC,"I believe we used reporter.super_simple_record (so for author: tags 100a, 110a, 111a) here as a placeholder until Display Fields are ready.  The XUL client is essentially using MODS via MVR's (which we want to get rid of)."
1739644,2018-01-10 21:42:38 UTC,"Not being an expert on MARC specs or cataloging, and given the feedback I've gotten... I'll probably just venture to say that instead of perhaps making things confusing (IMO) by stuffing 7xx field names under a label of ""author"" in the webclient when technically it's not an ""author""...  might it be more appropriate to instead  maybe just add another display field or column for those names found in the 7xx...?"
1739644,2018-01-10 14:11:31 UTC,"I prefer not displaying the added entry (7xx) fields if there is no 1xx field. Many bib records with no 1xx field are visual material titles, so there really isn't a need to display a name access point. For print titles with editors, while it would be nice to display those, I don't really see it as necessary."
1739644,2018-01-09 20:27:00 UTC,Following up on what Jason said I think this is the correct behavior.  If we had an additional fall through I'd vote for a statement of responsibility from the 245 before using added entries.  Just my .02 dinars.
1739644,2018-01-02 15:24:29 UTC,The author also does not display as expected for these records on the Items Out interface. I didn't check others.
1739644,2018-05-17 12:25:14 UTC,"Since there can be a large number of 7xx fields, I don't know that having a column for them would help. Visual material and sound recording records can have more than 10 7xx fields."
1739646,2018-06-19 12:01:23 UTC,"Reviewed:  https://review.openstack.org/561284
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=763fd62464e9a0753e061171cc1fd826055bbc01
Submitter: Zuul
Branch:    master"
1739646,2019-02-15 02:18:12 UTC,"Reviewed:  https://review.openstack.org/603910
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8e65a5eb11515cfe70f8e6850b842cd594af6a5
Submitter: Zuul
Branch:    master"
1739646,2018-09-24 14:47:39 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1739646,2018-09-24 14:47:03 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1739646,2018-07-30 16:08:22 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1739646,2018-07-04 14:54:35 UTC,"Reviewed:  https://review.openstack.org/563719
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8392c7f2656ae624877e3df539681c0a8f8b4926
Submitter: Zuul
Branch:    stable/ocata"
1739646,2018-06-29 08:52:28 UTC,"Reviewed:  https://review.openstack.org/563700
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0bf75621bbd25d4ce8a3588f112cf714891556eb
Submitter: Zuul
Branch:    stable/pike"
1739646,2018-06-25 03:00:11 UTC,"Reviewed:  https://review.openstack.org/563692
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7bcd581c78bb5916bf4b52e213322e7b56283572
Submitter: Zuul
Branch:    stable/queens"
1739646,2018-04-24 17:39:42 UTC,"Sounds like we've got consensus on class B1, so I'll mark the OSSA task won't fix, add a new OSSN task, switch the bug type to just public rather than public security and add the security bugtag instead."
1739646,2018-09-26 10:43:53 UTC,This issue was fixed in the openstack/nova 15.1.4 release.
1739646,2018-04-24 14:27:36 UTC,"It's only considered ""fixed"" from an advisory standpoint if, upon upgrading, the default behavior changes to solve the vulnerability. If operators need to alter their configuration as well, then this requires a bit more narrative and is the realm of a security note. Look at it this way... upgraded or new installations will continue to expose the vulnerability described here, as the default configuration is insecure. The plan is for it to be ""fixed"" (default behavior changes) at some point in a future release."
1739646,2018-04-13 15:12:38 UTC,Per comment 3:
1739646,2018-02-16 14:57:35 UTC,"Yes, given seemingly low impact, I'll subscribe the OSSG core security reviewers and if no further objections in the next few days we can switch this to public as a class B(1 or 2) report."
1739646,2018-02-16 02:40:23 UTC,"If this is not something that needs to be embaroged by the security team, could we open this up then as I'd like to discuss potential solutions openly."
1739646,2018-01-22 14:46:35 UTC,"This sounds like a class B1/B2 according to VMT's taxonomy ( https://security.openstack.org/vmt-process.html#incident-report-taxonomy ). Unless a backward compatible fix can be proposed to stable branches, then I suggest we subscribe the ossg-coresec group and create an OSSN task."
1739646,2018-01-22 13:57:50 UTC,Hope everyone enjoyed their holidays!
1739646,2017-12-22 09:29:25 UTC,"I believe instance_type.disk == 0 is paleolithic in OpenStack terms. It recall it causing me headaches round about Havana, at least. Pretty sure it just affects everybody."
1739646,2017-12-21 17:50:42 UTC,"As far as how far back this goes in nova, I'm sure it impacts at least all of the currently supported upstream stable branches. I don't know at what point instance_type.disk==0 was introduced though, that would require some digging."
1739646,2017-12-21 17:49:15 UTC,mnaser: I'm OK with doing the backward compatible thing by default too.
1739646,2018-04-13 16:20:06 UTC,"I was working on a backward-compatible fix for this today, should have the patch posted in the next hour or so, but now that this is public is there any reason to not just post that to Gerrit and duplicate bug 1758278 against this?"
1739646,2017-12-21 17:38:52 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1739646,2017-12-21 17:38:02 UTC,"As much as I would like us to default to enforce, I think there will be existing installation which will break as I am willing to bet that there are people who rely on this (as a matter of fact, I know some of our customers do this because it's easier than creating and deleting volumes)."
1739646,2017-12-21 17:33:57 UTC,Adding mdbooth given his background in the nova block device and imagebackend code.
1739646,2017-12-21 17:25:16 UTC,I've added Matt to this bug as he has helped discuss the details of this issue and figure out parts of it.
1739646,2018-04-13 16:29:47 UTC,"Oh, thanks, I guess if there are stable backports coming after all we can keep it as a class A report. Once there are backports linked from Gerrit I'll whip up an impact description and request a CVE assignment for this."
1739646,2018-04-13 17:54:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561284"
1739646,2018-04-23 16:21:23 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/563692"
1739646,2018-04-23 17:06:06 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/563700"
1739646,2018-04-23 17:49:21 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/563719"
1739646,2018-04-23 17:50:17 UTC,Backports are all posted:
1739646,2018-04-23 23:43:06 UTC,"It looks like the proposed patches don't actually engage the security protection they introduce, requiring an admin to make a policy configuration change before their environment will be protected from the issue described here. Am I interpreting that accurately, or misreading?"
1739646,2018-04-24 13:38:41 UTC,"> It looks like the proposed patches don't actually engage the security protection they introduce, requiring an admin to make a policy configuration change before their environment will be protected from the issue described here. Am I interpreting that accurately, or misreading?
"
1739646,2018-04-13 15:50:39 UTC,"Ahh, yes there were no subsequent objections to switching this bug to public, so I'll do that now and triage as a class B1 report. The security notes editors may want to consider drafting an OSSN related to this when it gets fixed in master."
1739646,2018-04-24 17:20:27 UTC,Got it. Thanks for your patience in describing the differences. With that I've removed the -W on the change on master and it should be ready for review from the nova trolls.
1739657,2017-12-26 21:41:17 UTC,"I think using the custom command and formatter is the expected way to do this, although I can see how it's not as ideal if you consider some of the standard formatters to still be useful."
1739657,2017-12-21 18:28:51 UTC,"Now I have a custom command class that inherits from cliff.Command and cliff.TableFormatter.
This solution works fine for me, but I've lost possibility call different formatters"
1739665,2018-04-03 13:49:21 UTC,"I'll ping the release team to ack the FFE:
To make it easier, the change is really just ""giving names to formerly undefined bits""
=> https://git.qemu.org/?p=qemu.git;a=commit;h=aff9e6e46a343e1404498be4edd03db1112f0950"
1739665,2018-03-01 06:39:40 UTC,"KVM patch has been merged in kernel 4.16-rc1.
Commit id:
80fef315a74d79d765dbf58d9481843a364c50d6"
1739665,2018-03-02 05:49:36 UTC,"The Qemu patch for AVX512_VNNI cpu feature has been merged into Qemu release in last Nov, Qemu 2.12 release, master branch."
1739665,2018-03-22 16:50:58 UTC,Confirmed that qemu in bionic does not have that commit yet. Subscribing ubuntu-server for consideration.
1739665,2018-03-23 05:53:54 UTC,"Hi,
For Qemu this needs a a feature freeze exception for the qemu change was identified after 1st of March.
Sorry, I missed the update with the upstream sha for a bit, otherwise I'd have marked it as FFE earlier, but IMHO it is no problem.
The patch is rather small and does not imply extra danger IMHO."
1739665,2018-04-03 14:48:36 UTC,"FFe for qemu approved, you can proceed now. Will any similar FFe be required for xen as well?"
1739665,2018-04-03 15:04:08 UTC,"It would be required for Xen as well if it will be done, but I didn't hear on Xen in regard to this so I don't know."
1739665,2018-04-05 08:48:28 UTC,PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3225
1739665,2018-04-09 18:07:50 UTC,This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu6
1739665,2018-04-10 07:23:41 UTC,"There wasn't a xen commit listed (and we didn't bump the xen version so we haven't picked it up by accident).
I'd assume this is a Won't Fix for 18.04 and might appear sometime later."
1739665,2018-04-10 10:01:16 UTC,"Due to time constraints and because we would deviate further and further away from Debian, we are not planning to update the Xen version for Bionic."
1739665,2018-04-13 23:43:34 UTC,This bug was fixed in the package linux - 4.15.0-15.16
1739665,2018-06-15 09:04:51 UTC,Dropping server subscription as the remaining (xen) task is incomplete still
1739666,2017-12-21 19:52:15 UTC,"It may not be a popular suggestion and I certainly don't want to see it used for anything like it was back in the JSPAC days, the simplest fix would be to just require jQuery and use it where we're currently using simple.js and it's cousins. (field validation would be simpler and more structured, for one.)"
1739666,2018-01-25 20:12:24 UTC,We found another instance where enabling jquery broke something in the catalog. The limit to available and group formats & editions checkboxes on the search results page sometimes do not work when you deselect them. See bug 1745190.
1739666,2018-01-03 15:42:02 UTC,See also related bug 1732754. The opac spinner also doesn't work when jquery is enabled.
1739672,2017-12-21 21:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1739672,2018-04-10 19:57:22 UTC,"ubuntu@foufoune:~$ lsb_release -rd
Description:	Ubuntu 17.10
Release:	17.10
ubuntu@foufoune:~$ apt-cache policy systemd
systemd:
  Installed: 234-2ubuntu12.3
  Candidate: 234-2ubuntu12.3
  Version table:
 *** 234-2ubuntu12.3 500
        500 http://azure.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     234-2ubuntu12.1 500
        500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages
     234-2ubuntu12 500
        500 http://azure.archive.ubuntu.com/ubuntu artful/main amd64 Packages"
1739672,2018-02-24 17:23:23 UTC,This bug was fixed in the package systemd - 237-3ubuntu3
1739672,2018-01-05 00:15:20 UTC,"avahi is zeroconf or IPv4LL, which is RFC 3927; whilst LLMNR is RFC 4795. In many aspects LLMNR is like mdns, yet the two are distinct and resolve different things quite differently, when inspected closer."
1739672,2018-01-04 22:58:55 UTC,Workaround:
1739672,2018-01-04 17:30:33 UTC,Interesting; the first thing I tried when triaging this was to edit /etc/nsswitch.conf as follows:
1739672,2018-01-04 17:06:34 UTC,"> The dns resolution from systemd-resolve is fast; the llmnr one is not.
> We currently have llmnr resolution enabled by default. ...it's a feature?!
"
1739672,2018-04-10 19:33:49 UTC,"I'm seeing this on Artful as well, in Azure cloud."
1739672,2018-01-04 17:01:12 UTC,"$ time systemd-resolve -p dns not-a-real-hostname
not-a-real-hostname: resolve call failed: No appropriate name servers or networks for name found"
1739672,2018-01-04 14:58:13 UTC,"$ systemd-resolve --status
Global
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test"
1739672,2018-01-04 14:57:13 UTC,The issue is with the systemd resolver not with glibc.
1739672,2018-01-02 15:06:29 UTC,"$ time ./test not-a-real-hostname
Trying to resolve: not-a-real-hostname
    getaddrinfo errno: No such file or directory
    getaddrinfo() return value: -2 (Name or service not known)"
1739672,2017-12-22 00:03:40 UTC,"I just tested with the Xenial kernel and Bionic userspace and observed that the bug still occurs, so marked Invalid for 'linux'."
1739672,2017-12-21 21:59:19 UTC,"One way to tell if this bug is due to the kernel, is to boot with some prior kernel versions and see if the bug goes away."
1739672,2017-12-21 21:13:26 UTC,"Note: I doubt this bug is in the kernel itself; I initially attempted to file it under glibc at first, but for some reason the `linux` package was selected."
1739672,2018-01-17 20:43:56 UTC,"yes, but I'm not uploading systemd until after the build-farm is open."
1739672,2018-01-17 14:30:14 UTC,"Hi,"
1739701,2017-12-22 22:29:16 UTC,"Thanks, I'll add this to the TODO list."
1739701,2017-12-22 15:07:32 UTC,"Please, insert in any RNB-note attached picture (above) without changing it`s name (name in Russian) - it do not show in RNB..."
1739701,2017-12-22 15:05:33 UTC,Sample picture
1739701,2017-12-22 14:44:29 UTC,"Relative paths are planned, but not fully supported yet. Non-ASCII names
should be supported. If you have a counterexample, please share it here."
1739701,2017-12-22 14:20:44 UTC,"Excuse me :( - I move RNB-files and move pictures(!), but do not change picture`s path in RNB-notes..."
1739701,2017-12-22 07:52:22 UTC,"Could you please post a small example export HTML file and the path to
where the picture is located? Does the path contain non-ASCII characters?"
1739708,2018-08-12 14:10:44 UTC,Looks good!  Thanks.  Fix committed.
1739712,2017-12-31 14:45:07 UTC,"Found the source of the problem, when using a project with 60fps for video with 25fps video is clipped. In particular for video made in simplescreenrecorder"
1739714,2018-09-06 04:46:40 UTC,The same with my kdenlive
1739714,2018-05-03 10:26:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739721,2017-12-27 06:36:32 UTC,"we may should add ""when"" to creating database tasks."
1739739,2019-09-17 07:00:22 UTC,Migrated to https://github.com/widelands/widelands/issues/3244
1739739,2017-12-27 16:02:48 UTC,"Default resources get important if a map designer wants to to remove them from the map. E.g. make a lake a real dead lake, with no fish. Or make an area of the map without water."
1739739,2017-12-26 10:35:35 UTC,"I'm wondering, do we even need the default resources in the current form? For new maps they could simply be set automatically while placing the terrain, they don't need to differ from normal resources, so they can also be altered and be removed. If older maps need them I'd rather put the effort into making a compatibility mode. I think someone already suggested something like that in the forum."
1739741,2017-12-22 13:17:57 UTC,Following Process works totally:
1739741,2017-12-22 13:04:16 UTC,"hp-plugin
=> re-installed the plugin just to be sure"
1739741,2017-12-22 11:16:40 UTC,Set up this queue:
1739741,2017-12-22 09:55:29 UTC,Cups says:
1739744,2018-02-05 15:15:16 UTC,You can specify the net-id like:
1739745,2018-04-02 09:52:43 UTC,A friend told me about this bug: he's constantly using Browse/Computer and not the actual library. He describes pretty much the same: waveforms get slower and slower (choppier) over time. It's not reproducible so far.
1739745,2018-03-19 14:54:08 UTC,"poelzi, is this fixed now?"
1739745,2020-05-09 01:12:30 UTC,"So we can assume this is fixed, nice."
1739745,2018-04-02 11:40:02 UTC,"With the current build I'm running the problem seems gone. At least after 2-3 days it does not happen anymore, I also analyzed like 2k songs, which also often triggered the problem.
Ronso0: Your friend using a recent master or the last release (beta ?). I think you need master for the fix"
1739745,2017-12-22 17:44:41 UTC,"I'll add stats reporting to TrackCache, just in case."
1739745,2017-12-22 17:11:17 UTC,Are all your tracks analyzed? Maybe TrackCache is leaking?
1739745,2017-12-22 15:17:26 UTC,"Probably a duplicate of:
https://bugs.launchpad.net/mixxx/+bug/1738227"
1739745,2017-12-22 10:47:07 UTC,Probably caused by analysis and already reported. I'm currently working on this issue:
1739752,2020-02-26 13:28:49 UTC,But the resolving work well.
1739752,2020-02-26 09:39:06 UTC,The thing is that it still not updating nameservers from subnet details to resolv.conf file
1739756,2018-02-27 04:32:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739759,2018-01-25 15:00:07 UTC,Fixed in bionic
1739759,2018-03-06 09:35:24 UTC,"The crash is occurring cleaning up a GsApp object after a plugin operation has completed. I've looked down code-paths to try and find what could have corrupted the object but not finding anything standing out. It seems possible this might be due to multiple threads accessing data. In 3.22 a lock was added to the data, but this is a major change that can't be backported. It smells like the sort of issue where - have multiple threads - threads interacting badly - add locks - problem goes away (but root cause not found)."
1739759,2018-03-06 09:36:04 UTC,I investigated the possibility of backporting gnome-software 3.22 to Xenial but the dependencies are too new to be able to do that.
1739761,2018-05-15 11:29:53 UTC,"Hello,
is there any action that I need to take on my side?
Thanks"
1739761,2018-06-01 09:54:59 UTC,"I can confirm that the Precise deployment is now working with our MaaS 2.3.3-6498, curtin (18.1-17-gae48e86f-0ubuntu1~16.04.1)"
1739761,2018-04-30 22:39:33 UTC,"Upon some investigation, it seems that the precise streams are not being
correctly generated, that may be causing MAAS to try to isntall a root tgz
instead of a precise squashfs image."
1739761,2017-12-22 12:56:33 UTC,Hi There.
1739761,2018-04-30 14:27:18 UTC,"Po-Hsu,"
1739761,2018-04-26 10:31:40 UTC,"Tested today, the deployment still not working."
1739761,2018-02-07 02:22:28 UTC,"This is fixed in curtin in trunk at commit
 063b9fe57e4ace5ed938598be6d900840d9e9bcc
daily archive has sufficient version now.
 https://code.launchpad.net/~curtin-dev/+archive/ubuntu/daily"
1739761,2018-02-06 16:58:54 UTC,"The maas-images changes are in lp:maas-images trunk now.  Although as mentioned above, they are not needed.  I will plan to mark maas-images as fix-released when there is a squashfs image in http://images.maas.io/ephemeral-v3/daily/precise/ ."
1739761,2018-02-01 19:57:45 UTC,bug 1746345 will cover the creation of 'a' above.  I've put a MP up for maas-images such that running it will create the squashfs image but that will be used only for testing.
1739761,2018-02-01 19:50:10 UTC,"The reason that maas 2.3 cannot already deploy precise is because of changes
in how the ephemeral environment (used for installation) is booted.
MAAS now provides kernel and initramfs over pxe and the root filesystem
over http ('root=http://....' via the cloud-initramfs-rooturl package).
Previously maas used iscsi root for providing the root filesystem."
1739761,2018-01-30 21:48:43 UTC,I opened bug 1746348 to cover curtin support of for mounting and copying filesystem image as a installation source.
1739761,2018-01-02 14:44:19 UTC,You cannot use MAAS 2.3 to deploy Precise. You need to use MAAS 2.2 or lower.
1739761,2017-12-23 19:57:08 UTC,"Hello Andres,"
1739761,2018-04-26 19:00:23 UTC,Why doesn't the ephemeral environment have the zfs module?
1739761,2018-04-27 02:25:05 UTC,"We really probably should make it so that the modprobe is not fatal.
Obviously if you're trying to install zfs it would be fatal, but otherwise
we should go on."
1739761,2018-04-27 02:49:57 UTC,We're using the MaaS image from https://images.maas.io/ephemeral-v3/daily/
1739761,2018-04-30 15:53:15 UTC,"Hi Scott,
thanks for the handy script, here is my image version:
ubuntu/precise amd64/hwe-p 20170424.1 daily True
ubuntu/precise amd64/hwe-q 20170424 daily True
ubuntu/precise amd64/hwe-r 20170424 daily True
ubuntu/precise amd64/hwe-s 20170424 daily True
ubuntu/precise amd64/hwe-t 20170424 daily True
ubuntu/precise i386/hwe-p 20170424 daily True
ubuntu/precise i386/hwe-q 20170424 daily True
ubuntu/precise i386/hwe-r 20170424 daily True
ubuntu/precise i386/hwe-s 20170424 daily True
ubuntu/precise i386/hwe-t 20170424 daily True"
1739761,2018-04-27 14:07:37 UTC,"On Thu, Apr 26, 2018 at 9:25 PM, Scott Moser <email address hidden> wrote:

> We really probably should make it so that the modprobe is not fatal.
> Obviously if you're trying to install zfs it would be fatal, but otherwise
> we should go on.
"
1739761,2018-04-26 14:25:20 UTC,Can you attach curtin install logs ?
1739761,2018-04-26 16:57:08 UTC,"Hello Ryan, here is the log from the MaaS server UI:
https://pastebin.ubuntu.com/p/qRB39w4mfV/"
1739761,2018-04-30 06:23:48 UTC,"How do I check the image version on my MaaS server?
Tried to navigate through the UI, didn't see any. Or if I will need to check it directly on the server?
Thanks"
1739762,2018-03-06 13:13:37 UTC,Upstream bug: https://gitlab.gnome.org/GNOME/gnome-software/issues/285
1739768,2017-12-22 12:57:26 UTC,Ignore my recommendation - didn't realize that test was being done within an else block for internal interfaces only. I just added a simple test to get it working for both external/internal:
1739768,2018-01-06 14:24:21 UTC,"Thanks for reporting this and the analysis, James!  Indeed our test environments and customers environments for ASR1K and CSR are HA pairs."
1739768,2018-08-21 19:25:39 UTC,Lower priority due to recommended HA configuration.
1739770,2018-01-31 14:16:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739772,2017-12-22 12:48:08 UTC,"before crashing, there are many access denied by server due to the password modified for the user.
i don't know whether it matters or not. I will try to reproduce the bug ."
1739772,2018-01-14 12:59:25 UTC,"Hello,
    Looking at the crash report it is unclear what was happening just before the crash. Can you please add the complete error log so we can check what was happening when the instance crashed. It would be great if you give us some more information like queries being executed during the time.
    I also double checked the backtrace and looking into the bugs database its a possibility that you could be hitting https://bugs.launchpad.net/percona-server/+bug/1686340 which has been confirmed.
    Can you please provide requested information or try to reproduce it in your environment."
1739772,2018-01-25 08:40:23 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3769
1739778,2018-02-24 10:09:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739790,2019-07-15 16:08:34 UTC,"Foundations does not support live-build directly as a tool for building images, but only as an implementation detail of builds driven by livecd-rootfs and ubuntu-cdimage."
1739790,2019-07-15 15:21:33 UTC,"Thank you very much for replying to my bug report, I really appreciate it."
1739790,2017-12-24 14:55:31 UTC,"Hi, quick update, I tried live-build on debian and it worked without any issues, so it seems to me that the ubuntu build is definitely broken."
1739790,2019-07-15 07:45:24 UTC,Thank you for your bug report.
1739790,2020-12-03 06:49:47 UTC,"@ regolith-linux
Please tell me where I can find latest updates to ubuntu-defaults-builder, because I don't see any commits at https://code.launchpad.net/ubuntu/+source/ubuntu-defaults-builder since 2017 :("
1739790,2020-12-03 06:02:35 UTC,"As of late 2020, there are updates to ubuntu-defaults-builder (FYI)."
1739790,2020-07-03 14:13:32 UTC,"It seems ubuntu-defaults-image from ubuntu-defaults-builder package was a recommended tool for building custom Ubuntu derivative, but this tools is not updated since 2017 :(, see
https://launchpad.net/ubuntu/+source/ubuntu-defaults-builder"
1739790,2019-07-15 16:23:24 UTC,"Thank you for your reply Steve,"
1739790,2019-07-15 05:55:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739791,2020-01-01 04:17:31 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1739791,2019-11-01 10:28:59 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1739791,2018-01-15 10:58:21 UTC,"Oh and I've tried with both the libinput driver and the old synaptics drivers on both wayland and Xorg. In every case, the problem persists."
1739791,2018-01-15 10:57:11 UTC,Same problem here:
1739791,2017-12-22 16:20:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1739792,2017-12-22 16:20:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1739792,2017-12-22 16:10:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739793,2017-12-22 16:20:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1739793,2019-02-06 11:31:46 UTC,"Thank you for your bug report, in the futur please try to stick to one report by issue."
1739793,2017-12-22 16:11:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739794,2017-12-22 16:09:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739794,2017-12-22 16:20:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1739805,2019-11-25 23:23:01 UTC,"Sorry this got overlooked for a while...
We're not doing this on purpose, we're just not enough people and don't have enough free time to clean up the bugtracker. (FYI Eric, who previously reviewed and commented on the patch left the project so this is simply a leftover.)"
1739805,2020-01-17 12:37:53 UTC,"> With the patch applied, on the General tab of Xfce Power Manager, there should be a ""Brightness step count"" field and an ""Exponential"" checkbox next to it.
"
1739805,2020-01-17 12:05:24 UTC,"(In reply to haarp from comment #34)

> Where are the settings to be found? I can't find anything new in the Power
> Manager's setting screen. I ended up manually adding them with the settings
> editor.
"
1739805,2020-01-15 18:55:17 UTC,"Thank you, Timothy Lee. This was long needed. I've applied attachment 8653 from comment 25 on top of xfce4-power-manager-1.6.5. I couldn't apply the newer patches due to the aforementioned code style changes."
1739805,2020-01-05 23:48:12 UTC,"Thanks for updating the patch and sticking to the coding style.
I only had very few places with odd spaces to fix (but I acknowledge that the source code is still quite messy and inconsistent in this respect, so it's hard to stick to a ""correct style"")."
1739805,2020-01-05 23:45:59 UTC,Timothy Lee referenced this bugreport in commit c866cf9faec6333e60f6b55a56b92ec9494747f3
1739805,2019-12-27 14:31:20 UTC,"The lowest one is a black screen for me too and the next one is already mid-bright on my Dell XPS 13. While I don't mind having the possibility to turn the screen brightness off completely, for many years I was also adding ""xbacklight -dec 1"" to the keyboard shortcuts, just to be able to dim my display more, when needed."
1739805,2019-12-13 23:17:45 UTC,"Created attachment 9307
Adjustable brightness steps with support for exponential step sizes"
1739805,2019-12-02 19:48:25 UTC,"Sorry, I completely missed the slider on the pop-up menu."
1739805,2019-12-01 22:57:10 UTC,"I started to look into this patch - could you rebase it one last time on top of master? (Please note that it mostly fails to apply because I cleaned up the code formatting in the sourcecode - no more tabs, 2 spaces instead.)"
1739805,2019-06-19 14:21:40 UTC,"Created attachment 8653
Adjustable brightness steps with support for exponential step sizes"
1739805,2019-12-01 23:27:55 UTC,"Nvm, I rebased it myself."
1739805,2019-06-15 13:49:28 UTC,@Timothy Lee Could you provide a patch for the actual master branch?
1739805,2016-07-29 10:49:42 UTC,"(In reply to Timothy Lee from comment #10)

> Created attachment 6754 [details]
> Adjustable brightness steps
"
1739805,2016-07-28 11:17:11 UTC,"Created attachment 6754
Adjustable brightness steps"
1739805,2016-07-28 11:16:07 UTC,"I've finished implementing the brightness step count functionality.  In addition to the git repository, I'm attaching a patch."
1739805,2016-05-06 20:09:17 UTC,"I wonder if you could make the increments logarithmic? I.e. 1, 2, 4, 6, 16. etc. On my screen, with linear steps the gaps are too large at the low levels (ie, the screen gets too bright too quickly) but then at the high levels there are too many steps needed to get to full brightness."
1739805,2016-03-08 00:20:06 UTC,"I believe the panel plugin doesn't need to be updated, since changing the number of keyboard controllable steps doesn't affect current brightness -- it only affects future brightness adjustment made by keyboard."
1739805,2016-03-07 17:35:38 UTC,"Ugh, that's what I get for commenting before coffee. For the panel plugin you'll want to do something similar what the brightness_min_level does in the panel-plugins/power-manager-plugin/power-manager-button.c Hope I'm not too confusing."
1739805,2016-03-07 06:30:29 UTC,"Timothy, nice work. Now that you have a configuration option in the settings UI, you can react to that in the power manager plugin as well. If we do it in the backlight, you'll need to create a step_switch variable in the struct then, install it in the class_init
http://git.xfce.org/xfce/xfce4-power-manager/tree/src/xfpm-backlight.c#n313"
1739805,2016-03-06 09:57:20 UTC,I've made an attempt to add this feature.  The code can be found on the brightness-step-count branch at:  <email address hidden>:timothytylee/xfce4-power-manager.git
1739805,2016-01-24 19:10:34 UTC,*** Bug 12299 has been marked as a duplicate of this bug. ***
1739805,2015-07-18 17:45:48 UTC,I just saw there is something called:
1739805,2015-07-11 07:58:05 UTC,The following lines in common/xfpm-brightness.c seem to be the cause of the course brightness steps.
1739805,2016-07-29 12:56:07 UTC,I've added an option to toggle exponential step sizes.
1739805,2015-07-11 06:19:37 UTC,When using FN key and arrows there are only 10 increments in the screen brightness settings. The lowest one is a black screen and the next one is already mid-bright for me. So basically it is not possible to set a low screen brightness level.
1739805,2016-07-29 12:59:47 UTC,This patch is applicable to the master branch of xfce4-power-manager at http://git.xfce.org/xfce/xfce4-power-manager/
1739805,2016-07-29 18:24:58 UTC,thanks
1739805,2016-08-30 07:42:02 UTC,Ping.  Any comments on the patch?
1739805,2017-01-14 11:09:31 UTC,The latest versions (up to 1.6) still have the original code with the brain-dead step increment.
1739805,2017-01-22 08:41:41 UTC,"Works even better with a smaller decrement value, so you can access in-between values."
1739805,2017-12-03 18:16:15 UTC,"Yes, please @maintainer integrate this into the next update : )"
1739805,2017-12-22 20:20:16 UTC,"The attachment ""Change brightness step number to 30 instead of 10"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1739805,2018-05-12 12:42:40 UTC,"Created attachment 7728
Adjustable brightness steps with support for exponential step sizes"
1739805,2018-08-18 12:43:17 UTC,Please forward this patch to the Xfce bug tracker. Thanks.
1739805,2018-08-29 07:22:36 UTC,Wow that is a godawful amount of patching for a simple 2-line fix. Are you sure there's not an NSA backdoor embedded in there somewhere? ;)
1739805,2019-06-11 18:14:33 UTC,"@majest I guess the bulk of the patch is the added config options in the GUI, please don't spread FUD (even ironic FUD)."
1739805,2016-07-29 12:56:56 UTC,"Created attachment 6757
Adjustable brightness steps with support for exponential step sizes"
1739805,2019-06-19 13:39:31 UTC,"Created attachment 8652
Adjustable brightness steps with support for exponential step sizes"
1739807,2018-02-14 09:38:13 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1739807,2018-02-14 20:27:43 UTC,artful verification - I've completed the iozone test on a filesystem atop a disk connected to a hisi sas controller w/o error.
1739807,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1739809,2017-12-23 17:12:33 UTC,Interesting.
1739809,2017-12-22 19:35:10 UTC,"Not reproduced with
- Inkscape 0.92.2 (c522dc6d40, 2017-09-16)
- Inkscape 0.92.2 (4c1f5bf829, 2017-12-22)
- Inkscape 0.92+devel (f589e1fdc7, 2017-12-22)"
1739809,2017-12-22 19:35:28 UTC,(all of the above on Windows 10 x64)
1739809,2017-12-23 01:15:24 UTC,"It takes a second Ctrl-Z for the crash to happen. The size change doesn't always appear to be visible (just drew two circles, and didn't see that - but then, I also got no error message at all)."
1739809,2017-12-23 01:16:13 UTC,(not sure what else I could describe even more precisely... - let me know if you have a question.)
1739809,2017-12-23 12:48:59 UTC,"- crash reproduced on Windows 10, Inkscape 0.92.2 (4c1f5bf, 2017-12-22) (32 bit build)
- crash is quite random, I got it maybe 3 times out of 10 tries (using rectangle and ellipse)"
1739809,2017-12-23 13:29:37 UTC,"Either I'm still using different steps (tried at least ten times now) or it's dependent on other factors, but I did not see any unexpected behavior once so far..."
1739809,2017-12-23 17:17:22 UTC,"Btw. I've always wanted to know how that bisecting works: If I ever wanted to do that, are there any instructions somewhere that explain how to do 'partial compiling' - as it hopefully doesn't need all program parts to be recompiled every time? (probably it's something simple, such as 'just run make again'...) Or perhaps someone has a script for that already?"
1739809,2017-12-24 00:34:23 UTC,"I think my comment about ""memory corruption""  might have been unclear - I was not referring to physical damage to your RAM but ""corrupted memory"" in the sense that writing to an invalid pointer can cause a program to corrupt its own memory. This is something that can be hard to debug as it can cause crashes in completely unrelated areas of code (that's why I asked if the crash/backtrace is always the same)."
1739809,2017-12-24 01:28:12 UTC,"Thank you, Eduard, for both explanations. Indeed, it seems that deb packages from previous commits are available via ppa - didn't know :) (here: https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable-daily/+builds?build_text=&build_state=built) Could work if used on a VM (I don't like to mess up my system...)."
1739809,2020-09-12 04:58:51 UTC,Closing because INVALID: Can't replicate.
1739833,2017-12-23 00:20:28 UTC,"The attachment ""libnssldap_runlevel5.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1739836,2018-04-09 06:08:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739836,2018-01-15 21:43:29 UTC,This may be related - from RedHat platform
1739836,2017-12-22 22:09:08 UTC,I apologise if initial category for this bug is incorrect. I couldn't match with my read understanding of the categories.
1739849,2018-01-17 12:38:19 UTC,there is probably a depends/recommends missing for polkit prompt to work as they should
1739849,2018-01-09 12:11:24 UTC,"A workaround is to install snap by command line as it doesn't require logging.
sudo snap install snap-name"
1739849,2018-01-09 11:30:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739849,2018-01-22 23:01:32 UTC,"The recommends should probably be on the snapd package, as the client doesn't know that Polkit is in use / directly interact with it."
1739852,2018-05-05 03:44:38 UTC,UPDATE 5.05.18
1739868,2018-02-08 19:00:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739875,2019-06-15 04:17:35 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1739875,2019-04-15 14:27:02 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1739885,2018-03-10 23:50:46 UTC,"Traceback (most recent call last):
  File ""/usr/bin/gtk-recordmydesktop"", line 43, in <module>
    main()
  File ""/usr/bin/gtk-recordmydesktop"", line 40, in main
    tr=rmdSimple.simpleWidget()
  File ""/usr/lib/python2.7/dist-packages/recordMyDesktop/rmdSimple.py"", line 509, in __init__
    self.__subWidgets__()
  File ""/usr/lib/python2.7/dist-packages/recordMyDesktop/rmdSimple.py"", line 88, in __subWidgets__
    self.image=sT.GtkThumbSelector(self,self.values[5],self.hidden,2000)
  File ""/usr/lib/python2.7/dist-packages/recordMyDesktop/rmdSelectThumb.py"", line 69, in __init__
    self.__subsample__(sroot,self.wwidth,self.wheight,self.root,self.factor)
  File ""/usr/lib/python2.7/dist-packages/recordMyDesktop/rmdSelectThumb.py"", line 79, in __subsample__
    im2.put_pixel(k/stride,i/stride,im1.get_pixel(k,i))
AttributeError: 'NoneType' object has no attribute 'get_pixel'"
1739889,2019-04-20 16:38:30 UTC,"Hello Michael, thank you for your contribution to Ubuntu!"
1739893,2018-02-01 19:11:39 UTC,"Exact same problem here, with ods files (did not try odt)."
1739893,2018-02-01 19:14:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739893,2018-03-20 10:25:50 UTC,"Hi, I had exact the same problem and solved it by installing the unoconv converter (apt install unoconv).
Hope that helps, cheers"
1739893,2018-11-16 13:15:31 UTC,"I had the same problem in Ubuntu 18.04.1 with latest Updates to now, Gnome 3.28.2, 64 Bit System."
1739893,2020-04-07 23:18:29 UTC,"Daniel (2-ubuntuone-4)'s solution works for me as well!!
Thank you, much obliged!"
1739893,2020-04-25 09:54:04 UTC,"I had the same problem on Ubuntu LTS 18.04, desktop freeze and had to either do REISUB or Ctrl+alt+F2 to switch to a terminal and reboot the machine (restarting gnome service didn't work for me)."
1739897,2018-10-15 17:32:07 UTC,Thanks for the confirmation rogonow.
1739897,2018-08-08 22:16:57 UTC,Does this issue affect the latest stable release (6.0.6) on Ubuntu 18.04 ?
1739897,2018-10-08 04:19:09 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1739897,2018-10-14 16:50:35 UTC,Yes
1739897,2018-10-17 15:24:49 UTC,"Olivier, could you do that for me please?"
1739897,2019-08-13 04:17:34 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1739897,2018-10-17 16:40:34 UTC,"@rogonow: the report is lacking detailed steps to explain how to reproduce the issue, I can see the screenshot but I'm not sure how you got there. Maybe attach a test document that demonstrates the problem, rather than just a screenshot?"
1739897,2018-10-23 08:22:46 UTC,I tought deeply about it: I can't set the background color near the borders. The borders itself have height.
1739897,2019-06-13 21:14:44 UTC,"Tested with:
Version: 6.0.7.3
Build ID: 1:6.0.7-0ubuntu0.18.04.6
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: nl-BE (en_US.UTF-8); Calc: group"
1739902,2019-06-17 04:17:31 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1739902,2019-04-17 06:18:45 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
Thanks"
1739903,2017-12-30 00:19:31 UTC,same here on a completely fresh install on a new machine
1739903,2017-12-24 13:00:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739905,2017-12-23 19:30:07 UTC,This change was made by a bot.
1739914,2017-12-29 08:04:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739934,2018-01-02 09:39:44 UTC,Thanks for your report. As you figured out it happened because mythbuntu is no longer supported [1]  and it was the only desktop metapackage installed on your system.
1739934,2017-12-24 04:04:05 UTC,"system needed another ""apt dist-upgrade"" before ""do-release-upgrade"" would succeed. The solution became clear after seeing this in main.log and investigating the package:"
1739934,2017-12-24 07:18:22 UTC,background info:
1739938,2017-12-24 10:45:49 UTC,thank you for taking the time to issue a report.
1739938,2017-12-25 22:40:24 UTC,"I'm not quite sure what you mean - but what I am doing is working on
several Inkscape files at the same time but to my knowledge I only have one
program open, ie I open Inkscape and then open 1-4 Inkscape files, now I am
not sure if that opens the program multiple times or just multiple files.
I guess I never thought of it before since I thought programs can work on
several files at once."
1739942,2019-10-03 08:59:40 UTC,"4.13 is no longer supported, please feel free to open a new bug with newer releases."
1739942,2017-12-24 09:00:04 UTC,This change was made by a bot.
1739946,2017-12-25 05:53:48 UTC,"If *I'd* have to rank them by preference, my preferred provided would be Google Drive (supporting Google photos might also be interesting, IMO, though you can access Google Photos though the drive API if the user enabled Photos integration), with Dropbox being second."
1739946,2017-12-24 22:44:54 UTC,"Hi,"
1739947,2019-05-26 16:49:43 UTC,"Building for win64 is now possible with appveyor, or on a dev setup."
1739947,2018-03-22 20:19:52 UTC,This is essential a matter of packaging openlp for 64-bit windows. So far we have not done this because we prefer to only have one installer for windows to make things simple for users.
1739948,2018-05-28 13:20:50 UTC,"In order to find French(Belgian) keyboard in the first list, you have to  install ""french"" first, as a supported language (bottom button ""Managed Installed Languages"").
Then you will see every french options like ""French(Canada)"", ""French(Belgium)"", etc in the main list of inputs."
1739948,2019-10-25 00:55:39 UTC,"Hmm.. This conversation seems to be about a confusion about the Settings GUI, not an IBus bug, and since the problem seems to be resolved, I closed it."
1739948,2018-12-24 10:33:17 UTC,"I actually had the same issue while trying to add the Belgian keyboard. I had to reload gnome-shell to get the Belgian input method despite I had several other French ones, and the Belgian regional settings."
1739948,2018-01-17 15:38:46 UTC,I could find the missing keyboard layout by typing this in the terminal: gsettings set org.gnome.desktop.input-sources show-all-sources true
1739948,2017-12-24 10:06:56 UTC,Here are my input sources
1739950,2018-01-04 00:38:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/531042"
1739950,2018-01-04 00:38:11 UTC,This is likely the fix:
1739950,2018-01-04 00:37:45 UTC,Like this for Queens:
1739950,2018-01-04 00:37:28 UTC,"I think https://docs.openstack.org/pike/configuration/ is supposed to pull in the compute configuration based on the structure and redirects, and it should go here:"
1739950,2017-12-25 01:38:51 UTC,There are the following documents.
1739950,2018-02-15 23:53:40 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1739950,2018-01-09 22:15:12 UTC,"Reviewed:  https://review.openstack.org/531042
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=694d264bb82e6cf2573c601fbca06de0e57393c0
Submitter: Zuul
Branch:    stable/pike"
1739956,2020-01-08 14:37:38 UTC,"I get the same error in Linux Mint 19.3. The only buttons at the top right corner of the application are minimize and close (X), there are no Maximize or Restore buttons, no matter what I do. Even right-clicking on the top of the application, the Maximize option is grayed out, there is a Resize option but it doesn't solve the issue. The problem is that the bottom of the application is never visible so I can't see the progress bar and, if I want to uncheck any of the files to transfer, I can't ""reach"" the checkbox for any of the images in the bottom row to uncheck these (I can scroll up and down if I have more rows of images that can appear in the screen but the bottom row is always cut off)."
1739956,2017-12-24 16:00:54 UTC,"Thanks for your bug reports. Try closing the side panels, and you should be able to resize the window. Let me know how you get on."
1739956,2017-12-24 17:56:49 UTC,"Hi Damon,
I've found the way to close the left panel but not the right panel. I can change its width but I've not found the way to *close* it."
1739956,2017-12-24 18:32:14 UTC,"Click on the right vertical buttons to switch panels, or open/close them. For example if the Destination panel is open, click on the Destination button to close it."
1739956,2018-11-22 01:09:31 UTC,I'm seeing this too even on a larger screen. I have 1600 x 900 and the lower section of the window disappears off the bottom of the screen.
1739956,2018-11-22 02:08:30 UTC,I did some more testing on this and found that the .conf is updated after closing and shows the smaller window height in the Main Window section. However when reopened it returns to the default height of 930.
1739956,2020-01-09 02:13:28 UTC,"In Manjaro, the previous application window size is never remembered, the bottom of RPD is not visible but it does have the Restore button at the top which maximizes the application (resizes it to fill the window meaning that the bottom becomes visible). However, after exiting and restarting RPD, you have to maximize the application again."
1739956,2020-01-09 04:30:37 UTC,Sorry I will not have time to investigate problems with window positioning or state for several months.
1739956,2020-01-29 11:49:58 UTC,Unfortunately the problem of the window being too big for tiny screens is not properly fixed.
1739956,2020-04-13 16:21:41 UTC,"Linux Mint 19.3, closing side panels fixed the issue."
1739956,2020-04-13 17:32:48 UTC,Julian I assume you are running a recent version of Rapid Photo Downloader? It seems it works as it should now because the Qt developers fixed something in Qt; nothing changed in Rapid Photo Downloader. The install.py script automatically installs the latest version of Qt.
1739966,2019-09-03 06:14:08 UTC,Is this something I could help fix? It will make deploying my application difficult. Please let me know!
1739966,2017-12-24 14:59:42 UTC,"It looks like libgstpythonplugin.so is explicitly deleted in the debian/rules, presumably because it doesn't currently load due to the wrong PYTHON_LIB_LOC being set at compile time."
1739966,2017-12-24 15:10:23 UTC,"It looks like this can be fixed by adding ""--with-libpython-dir="" to the configure_flags in debian/rules to set the correct architecture dependent library path."
1739969,2017-12-24 18:09:26 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1739969,2018-01-04 10:16:26 UTC,Also Affects Xubuntu daily ISO for BB
1739970,2017-12-24 18:55:49 UTC,"reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1739970,2017-12-24 23:21:34 UTC,"Alvin,"
1739970,2017-12-24 19:08:09 UTC,"probably related to the fact that the viewbox has zero width in the document.
The viewbox is given as:
   viewBox=""-3240000 0 0 1100""
 I would suggest manually editing the viewbox attribute to give it a size consistent with the page dimensions"
1739976,2018-08-21 19:24:57 UTC,this is allow priority issue - because it is recommended that the plugin be used in an HA configuration (this bug occurs only in a single ASR configuration).
1739984,2018-03-02 19:03:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1739984,2017-12-25 01:02:02 UTC,Thanks in advance
1740006,2017-12-25 08:26:41 UTC,Here the package info and a screenshot:
1740012,2019-09-16 14:01:49 UTC,Migrated to https://github.com/widelands/widelands/issues/2094
1740012,2018-01-05 11:44:32 UTC,Agreed - especially since it's impossible to change the sound options in the editor.
1740016,2020-12-29 22:21:59 UTC,"Please note we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1740016,2018-01-06 22:46:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740018,2018-01-05 11:45:27 UTC,Sounds good to me :)
1740018,2019-09-16 14:02:25 UTC,Migrated to https://github.com/widelands/widelands/issues/2095
1740019,2018-01-03 07:50:27 UTC,"> Please file an upstream bug
"
1740019,2018-01-03 04:21:59 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu"
1740019,2017-12-25 15:05:47 UTC,apport information
1740019,2018-01-02 21:28:01 UTC,"> Did this issue start happening after an update/upgrade?
"
1740019,2017-12-25 15:05:56 UTC,apport information
1740019,2018-01-02 17:41:57 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1740019,2017-12-25 15:05:53 UTC,apport information
1740019,2017-12-25 15:05:52 UTC,apport information
1740019,2017-12-25 15:05:51 UTC,apport information
1740019,2017-12-25 15:05:50 UTC,apport information
1740019,2018-01-02 21:49:58 UTC,Output (with postfilters applied) is available at https://imgur.com/a/BDOQR
1740019,2017-12-25 15:05:49 UTC,apport information
1740019,2017-12-25 15:05:48 UTC,apport information
1740019,2017-12-25 15:05:45 UTC,apport information
1740019,2017-12-25 15:05:44 UTC,apport information
1740019,2017-12-25 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740019,2017-12-25 11:19:21 UTC,"Tried other acpi flags, but none boot."
1740019,2017-12-25 15:05:55 UTC,apport information
1740019,2017-12-25 15:05:54 UTC,apport information
1740031,2017-12-25 16:18:45 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1740031,2017-12-26 13:43:53 UTC,"Hello
I found the cause and a way around the problem but it does not suit me at all."
1740031,2019-07-14 14:30:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740049,2020-01-02 04:17:36 UTC,[Expired for guake (Ubuntu) because there has been no activity for 60 days.]
1740049,2019-11-02 21:23:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1740049"
1740049,2017-12-27 09:24:51 UTC,"Could not reproduce, can you please add a step by step?"
1740051,2018-01-04 12:57:01 UTC,"Hello,"
1740051,2018-01-09 23:14:58 UTC,"Hello,"
1740051,2018-01-02 17:41:28 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1740051,2017-12-25 22:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740055,2020-04-01 14:49:16 UTC,Closing because INVALID: CAN'T REPLICATE.
1740055,2017-12-26 14:58:48 UTC,"I'd try updating to the latest Inkscape version (.92.2).  Your version is many years old now.
https://inkscape.org/en/release/0.92.2/"
1740068,2017-12-26 07:35:53 UTC,Strange that this was not caught with functional tests.
1740068,2017-12-26 04:31:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530053"
1740068,2018-06-11 09:39:23 UTC,"Change abandoned by junbo (<email address hidden>) on branch: master
Review: https://review.openstack.org/530053"
1740074,2018-01-02 13:18:57 UTC,"Probably related to bug #1153706.
Might even be a duplicate, the other bug only mentions percentages in combination with gradientUnits=""userSpaceOnUse"" (which is not the case here), though."
1740091,2019-09-11 03:23:21 UTC,"Reviewed:  https://review.opendev.org/655837
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=520005b13dc47bf78db33a526c1947e4b2c0d681
Submitter: Zuul
Branch:    master"
1740091,2019-04-26 07:32:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655838"
1740102,2018-03-21 12:51:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740105,2018-05-29 10:30:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740106,2019-10-23 13:56:42 UTC,"I too have the
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached
problem, but it only affects one user."
1740106,2018-09-28 22:01:46 UTC,"If this happens again, check to make sure your locale is set properly - https://ask.fedoraproject.org/en/question/92248/why-does-gnome-terminal-crash-is-my-locale-ok/?answer=95006#post-id-95006"
1740106,2018-04-11 12:01:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740106,2019-06-29 06:29:09 UTC,"i have recently installed chrome remote desktop too, and nautilus and terminal stopped working.
running this solved the terminal issue for me, as suggested in this [0] duplicate question:"
1740106,2018-10-02 11:06:41 UTC,I found that this issue could also be triggered by chrome-remote-desktop
1740106,2019-02-24 13:07:46 UTC,I confirm that removing chrome-remote-desktop and rebooting fixed the issue for me too.
1740106,2018-10-02 11:28:47 UTC,While remote connection is enabled for chrome-remote-desktop
1740111,2018-02-05 11:49:38 UTC,"I tried to replace pyinotfy to inotify according to the discussion with Doug.
But, the same error was occurred."
1740111,2018-01-09 08:22:05 UTC,"I sent a mail about this issue to openstack-dev ML.
As a result, Doug Hellmann replied to me and presented the policy to fix.
(Thanks!)"
1740111,2017-12-26 10:27:57 UTC,"""watch_log_file"" is a configuration value of oslo.log.
So I added oslo.log to affects project."
1740111,2017-12-27 02:58:22 UTC,"Additional Infomation:
I could launch masakari-api and nova-compute after applying the patch[1] to my environment.
[1]: https://github.com/seb-m/pyinotify/pull/117/files"
1740116,2019-06-08 19:44:09 UTC,"Hello
I have exactly same problem in Ubuntu 19.04 and Toughbook CF-19
5.0.0-16-generic
Because touchpad is detected as mouse i'm unable disable click while touching touchpad (i want use only hardware keys)
This is make so hard to use, slightly touch while moving finger cause text to be selected or item to be selected and moved... that make word processing or simple tasks very inefficient."
1740116,2018-01-22 03:39:06 UTC,"> On 22 Jan 2018, at 4:16 AM, Apicultor <email address hidden> wrote:
>
> Which model string did you add? ""FJC6001"" for the touchpad, or the model
> string of the machine itself?
The DMI string of the machine.
"
1740116,2018-01-21 20:16:42 UTC,"Which model string did you add? ""FJC6001"" for the touchpad, or the model string of the machine itself?"
1740116,2018-01-19 03:52:24 UTC,"FWIW I just added your model string in drivers/input/mouse/lifebook.c, struct dmi_system_id lifebook_dmi_table[]."
1740116,2018-01-18 22:10:55 UTC,"Unfortunately this didn't fix the problem. The mouse pointer moves much more slowly, and it's being detected as a touchpad by xinput, but the control panel still only offers mouse pointer speed and no touchpad options."
1740116,2018-01-11 09:29:45 UTC,Please try http://people.canonical.com/~khfeng/lp1740116/
1740116,2018-01-09 18:41:14 UTC,apport information
1740116,2018-01-09 18:41:13 UTC,apport information
1740116,2018-01-09 18:40:54 UTC,apport information
1740116,2018-01-09 18:41:10 UTC,apport information
1740116,2017-12-26 12:22:52 UTC,[    4.450585] input: PS/2 Generic Mouse as /devices/platform/i8042/serio2/input/input9
1740116,2017-12-26 12:23:37 UTC,Removing specificity to kernel-package
1740116,2017-12-27 09:30:06 UTC,This change was made by a bot.
1740116,2018-01-01 12:52:23 UTC,"This might be a duplicate of bug 1708852, but the upstream kernel 4.14.9 does NOT fix the issue."
1740116,2018-01-02 16:33:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1740116,2018-01-06 22:39:25 UTC,Linux machine 4.15.0-041500rc6-generic #201712312330 SMP Sun Dec 31 23:31:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1740116,2018-01-06 22:39:37 UTC,Issue still exists upstream; tagging and confirming.
1740116,2018-01-09 06:27:19 UTC,Please run `apport-collect 1740116`.
1740116,2018-01-09 18:40:53 UTC,apport information
1740116,2018-01-09 18:40:55 UTC,apport information
1740116,2018-01-09 18:40:58 UTC,apport information
1740116,2018-01-09 18:40:59 UTC,apport information
1740116,2018-01-09 18:41:01 UTC,apport information
1740116,2018-01-09 18:41:12 UTC,apport information
1740116,2017-12-26 16:23:06 UTC,More info:
1740116,2018-01-09 18:41:02 UTC,apport information
1740116,2018-01-09 18:41:03 UTC,apport information
1740116,2018-01-09 18:41:04 UTC,apport information
1740116,2018-01-09 18:41:05 UTC,apport information
1740116,2018-01-09 18:41:07 UTC,apport information
1740116,2018-01-09 18:41:08 UTC,apport information
1740116,2018-01-09 18:41:09 UTC,apport information
1740123,2018-02-08 15:22:26 UTC,"You can create the group, but then if you boot an instance with that group, the instance will fail because there is no policy."
1740123,2018-01-25 02:27:16 UTC,I don't see anything in the REST API schema validation or code that requires that policies are provided. I don't know if there is a good reason for creating a server group without any policies though.
1740125,2020-09-13 18:23:44 UTC,Closing because INVALID.
1740125,2019-02-03 08:18:27 UTC,"confirmed on Windows 10, Inkscape 0.92.4 (5da689c313, 2019-01-14)"
1740130,2018-01-02 09:12:27 UTC,It seems mailspring mail client snap is doing this.
1740130,2019-09-27 09:51:59 UTC,"Please raise this issue with the author of a particular snap. You can obtain information about the contact point, if one was set, via ""snap info mailspring"". While localization support in snaps is far from perfect it is possible to do things correctly."
1740130,2018-01-23 07:16:36 UTC,desktop-exports from snapcraft-desktop-helpers calls xdg-user-dirs-update https://github.com/Ubuntu/snapcraft-desktop-helpers/blob/master/common/desktop-exports#L90 Maybe that's what triggering the problem.
1740130,2018-01-01 11:58:46 UTC,"*which* snap? snapd doesn' do this; you must have a devmode, classic, or snap with the 'home' interface that's doing this."
1740133,2017-12-26 21:57:26 UTC,"I met with the same issue to launch clusters when using the HDP 2.4.
The image is generated from the sahara-image-elements script and openstack version is pike as well."
1740133,2018-01-17 11:09:56 UTC,"This looks like https://bugs.launchpad.net/sahara/+bug/1672218, which may be reopened. Can you please check if the logs on the ambari node (ambari-server.log, etc) reports the same error?"
1740143,2018-01-02 13:06:41 UTC,"> Apparently the original patch didn’t send for linux stable branch.
"
1740143,2018-07-27 23:27:55 UTC,"Hi, patch author here. You can ask BTRFS maintainers by mailing to the <email address hidden> mailing list. Also, the patch author email address is in the commit itself, for quick questions. :-)"
1740143,2018-01-02 17:24:01 UTC,"What I am saying is that this patch is already in 4.14 kernel, I verified that myself. Which means it was already pulled into stable branch. Now it needs to be backported."
1740143,2018-01-02 17:14:17 UTC,"> On 2 Jan 2018, at 9:06 PM, Vasya Pupkin <email address hidden> wrote:
>
>> Apparently the original patch didn’t send for linux stable branch.
>
> I don't know exactly what you mean, but 4.14 kernel has this patch. It's
> easy to verify by changed messages (""enabling ssd optimizations"" vs
> ""enabling SSD mode”).
"
1740143,2018-01-02 04:31:22 UTC,"> On 27 Dec 2017, at 12:45 AM, Vasya Pupkin <email address hidden> wrote:
>
> This backport request does not miss anything. Also, the apport-collect
> 1740143 doesn't seem to do anything after opening this bug page in
> ELinks.
"
1740143,2017-12-26 16:45:12 UTC,"This backport request does not miss anything. Also, the apport-collect 1740143 doesn't seem to do anything after opening this bug page in ELinks."
1740143,2017-12-26 16:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740147,2021-01-15 19:07:41 UTC,This would be really handy for libraries who close temporarily during renovations and Covid exposures.
1740159,2020-04-15 20:05:28 UTC,"Thank you for your bug report, looks like you are using elementary OS, not Ubuntu, please report the issue to them"
1740159,2020-04-15 19:47:25 UTC,Any news?
1740163,2018-01-04 00:13:45 UTC,apport information
1740163,2018-01-02 05:00:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740163,2018-01-04 00:13:21 UTC,apport information
1740163,2018-01-04 00:13:44 UTC,apport information
1740163,2018-01-04 00:13:20 UTC,apport information
1740163,2018-01-04 00:13:19 UTC,apport information
1740163,2018-01-04 00:13:42 UTC,apport information
1740163,2018-01-04 00:13:17 UTC,apport information
1740163,2018-01-04 00:13:40 UTC,apport information
1740163,2018-01-04 00:13:41 UTC,apport information
1740163,2018-01-04 00:13:36 UTC,apport information
1740163,2018-01-04 00:13:35 UTC,apport information
1740163,2018-01-04 00:13:35 UTC,apport information
1740163,2018-01-04 00:13:37 UTC,apport information
1740163,2018-01-04 00:13:34 UTC,apport information
1740163,2018-01-04 00:13:32 UTC,apport information
1740163,2018-01-04 00:13:31 UTC,apport information
1740163,2018-01-04 00:13:30 UTC,apport information
1740163,2018-01-04 00:13:29 UTC,apport information
1740163,2018-01-04 00:13:28 UTC,apport information
1740163,2018-01-04 00:13:27 UTC,apport information
1740163,2018-01-04 00:13:25 UTC,apport information
1740163,2018-01-04 00:13:24 UTC,apport information
1740163,2018-01-04 00:13:39 UTC,apport information
1740163,2018-01-04 00:13:22 UTC,apport information
1740169,2018-04-15 17:34:02 UTC,") Is this something that started to happen after an update? If so, which?"
1740169,2018-04-12 04:17:20 UTC,[Expired for libcec (Ubuntu) because there has been no activity for 60 days.]
1740169,2018-02-10 04:21:34 UTC,lg webos tv. I never selected xorg package...
1740169,2017-12-27 00:20:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1740169,2018-02-07 03:26:05 UTC,"ill, thank you for reporting this and helping make Ubuntu better."
1740169,2018-02-09 01:42:38 UTC,apport information
1740169,2018-02-09 01:42:40 UTC,apport information
1740169,2018-02-09 01:42:41 UTC,apport information
1740169,2018-02-09 01:42:43 UTC,apport information
1740169,2018-02-09 01:42:45 UTC,apport information
1740169,2018-02-09 01:42:46 UTC,apport information
1740169,2018-02-10 12:11:16 UTC,"ill:

>""lg webos tv.""
"
1740169,2018-02-09 01:42:48 UTC,apport information
1740169,2018-02-09 01:42:50 UTC,apport information
1740169,2018-02-09 01:42:52 UTC,apport information
1740169,2018-02-09 01:42:53 UTC,apport information
1740169,2018-02-09 01:42:55 UTC,apport information
1740169,2018-02-09 03:00:33 UTC,"ill, given this is issue is HDMI CEC related, there is no evidence this has anything to do with xorg. Despite this:"
1740169,2018-02-09 01:42:49 UTC,apport information
1740171,2017-12-26 21:54:56 UTC,Please see: https://bugs.launchpad.net/appmenu-qt/+bug/838115 for an equivalent solution on qt4.
1740172,2018-01-02 12:56:11 UTC,"@Ken:
Could you please add information on the exact version (and edition!) of Windows used?
Also please add he precise error messages of both installers (e.g. attach screenshots)."
1740172,2017-12-27 21:38:30 UTC,Some versions of Win10 do not allow installations outside of the Win App Store. Others may require using developer tools.
1740175,2018-03-15 08:26:29 UTC,"I can confirm the same behaviour:
Can't suspend Asus Laptop. It blocks and I continue to see the pointer of the mouse, but everyhing is blocked. Can't resume and it's impossible performe any action."
1740175,2018-02-21 01:11:01 UTC,"The issue is with suspend. It suspends perfectly if I just boot up and immediately try it. If I work on a project in vs code for a couple hours, it almost always freezes."
1740175,2018-03-08 19:35:07 UTC,"Yes, suspend had no issues on 16.10."
1740175,2017-12-26 21:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740175,2018-03-09 04:10:03 UTC,"16.10 use linux kernel v4.8.
Do you still have linux kernel v4.8 in your grub menu? Please try if that one works."
1740175,2017-12-26 21:35:15 UTC,apport information
1740175,2017-12-26 21:35:20 UTC,apport information
1740175,2018-01-02 17:38:03 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1740175,2018-01-04 01:48:20 UTC,"One observation that i've made: upon powering on, if I attempt to suspend after little to no activity, ie: quickly going through Chromium, the system is almost always able to suspend and resume thereafter. During periods when i'm doing projects that last a couple hours using Sublime Text, CLion, or Pycharm, etc, suspending and resuming will often not work. Not sure if this is meaningful or if this has any randomness to it."
1740175,2018-01-04 09:03:31 UTC,Please follow the instruction in https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
1740175,2018-01-04 00:00:43 UTC,"Upgraded to v4.15 kernel; used systemctl suspend today and couldn't resume ~ the screen and hard drive ""suspended"", but the hard drive was still running (with my laptop, a blue light indicates the hard drive is on)."
1740175,2018-01-05 04:41:15 UTC,"> On 5 Jan 2018, at 7:54 AM, Matt G <email address hidden> wrote:
>
> So, 'echo freeze | sudo tee /sys/power/state' seems to work quite
> smoothly. Is there any reason NOT to use this from here on out instead
> of 'systemctl suspend'. Could quite well solve my issue.
>
"
1740175,2018-01-05 14:12:21 UTC,"I did a number of the steps in the link provided for debugging to the best of my ability (i'm pretty new). Last night I had an issue with shutdown: after running a stop job on mysql community server the system froze on 'reboot: Power down'. I just properly turned off the i915 driver and updated grub, so i'll see if that has any impact."
1740175,2018-01-07 02:03:25 UTC,"I was able to fix the stop job on shut down, but I froze again on 'reboot: Power down' - it looks like the hard drive is turning off but the screen stays on."
1740175,2018-02-05 08:05:25 UTC,"This bug is crippling on an Ubuntu laptop and the importance should be raised.  Without the ability to recover from hibernation, there's no way to travel with your laptop and maintain your session during travel.  This means having to shutdown and then restore all development VMs, IDEs, running services, etc each time you need to begin work again."
1740175,2018-02-07 07:16:30 UTC,So is it about suspend or hibernate? The original description didn't mention hibernate at all...
1740175,2018-02-22 09:38:40 UTC,"You were using 16.10, did the suspend work in 16.10?"
1740175,2018-01-04 23:54:44 UTC,"So, 'echo freeze | sudo tee /sys/power/state' seems to work quite smoothly. Is there any reason NOT to use this from here on out instead of 'systemctl suspend'. Could quite well solve my issue."
1740180,2019-05-07 08:56:04 UTC,"Created attachment 9063156
youtube 1080play video -errors console.png"
1740180,2019-03-21 17:26:40 UTC,apport information
1740180,2019-03-22 08:40:08 UTC,"Reproducible using Firefox Nightly 68.0a1 (2019-03-22) on Windows 10 x64.
""SecurityError: Permission denied to get property ""href"" on cross-origin object"" error appears in the browser console."
1740180,2019-03-21 17:26:39 UTC,apport information
1740180,2019-05-07 07:31:34 UTC,"Created attachment 9063147
console errors - FarmVille 2 -  .png"
1740180,2019-05-07 07:32:13 UTC,"Created attachment 9063148
console errors - FarmVille 2.png"
1740180,2019-05-07 07:32:39 UTC,"Created attachment 9063149
console errors -Slotomania .png"
1740180,2019-07-02 12:43:23 UTC,Reproducible in the Latest Nightly 69.0a1 (2019-07-01).
1740180,2020-08-05 15:09:41 UTC,"i was able to reproduce this issue on Nightly 81.0a1 on Ubuntu 18.04, also on beta 80.0b3 and 79release."
1740180,2019-11-05 14:59:18 UTC,This is still happening on latest Nightly 72.0a1 on Ubuntu 18.04
1740180,2020-01-14 18:49:39 UTC,This issue was reproducible on Windows 10 with Firefox Nightly version 74.0a1 (2020-01-14) (64-bit). Marked as affected and all platforms.
1740180,2020-02-18 12:37:01 UTC,This issue was reproducible on Mac OS 10.14 with Firefox Nightly version 75.0a1 (2020-02-17) . Marked as affected.
1740180,2020-03-17 15:08:41 UTC,"Hi,"
1740180,2020-04-15 18:28:24 UTC,"Hi,"
1740180,2020-10-15 15:39:59 UTC,"Hi,"
1740180,2020-10-15 16:16:24 UTC,"Change the status for beta to have the same as nightly and release.
For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#missing_beta_status.py)."
1740180,2019-03-21 17:26:37 UTC,apport information
1740180,2019-09-12 08:50:39 UTC,"Mozilla/5.0 (X11; Linux i686; rv:71.0) Gecko/20100101 Firefox/71.0 - Build ID: 20190911215306.
This issues is still reproducible on the latest Nightly 71.0a1 on Ubuntu 16.04 i686."
1740180,2019-03-21 17:26:36 UTC,apport information
1740180,2018-06-30 18:41:27 UTC,apport information
1740180,2019-03-21 17:26:33 UTC,apport information
1740180,2017-06-07 00:30:45 UTC,Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0  (20170606100219)
1740180,2017-06-07 14:23:52 UTC,Is this bug 1370237?
1740180,2017-06-07 17:39:24 UTC,The game is not loading even when delete the mentioned file (pluginreg.dat) in the profile folder and restart Nightly.
1740180,2017-06-14 16:14:17 UTC,WFM on Linux 64: I get the ask-to-activate prompt and can use it successfully.
1740180,2017-06-14 16:17:04 UTC,I spoke too soon: I am seeing this get stuck right at the end of the loading screen. I'm going to reach out on our partner list.
1740180,2017-06-14 16:31:23 UTC,"This bug 1370743 has been filed about the same problem, although its reproducibility scenario at the time was a bit different."
1740180,2017-06-14 16:32:06 UTC,"Err sorry, I meant bug 1317995."
1740180,2017-06-14 16:36:50 UTC,"We worked with Adobe on gug 1317995 with async drawing, and that appears to be fixed in the latest Flash updates."
1740180,2017-12-07 13:32:06 UTC,I've noticed that this bug is now reproducing on Windows 10 using 52.5.2 esr - build 2.
1740180,2017-12-27 09:05:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740180,2017-12-27 14:08:34 UTC,"Hi Eduardo,"
1740180,2018-01-31 14:36:07 UTC,Also reproducible on Windows 10 x64 on the Firefox Nightly 60.0a1(2018-01-31)(64-bit)
1740180,2018-06-30 17:30:29 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version.
1740180,2019-03-21 17:26:34 UTC,apport information
1740180,2018-06-30 18:41:18 UTC,apport information
1740180,2017-12-27 09:09:11 UTC,The game doesn't load completely but firefox keeps ok to me.
1740180,2018-06-30 18:41:22 UTC,apport information
1740180,2018-06-30 18:41:25 UTC,apport information
1740180,2018-06-30 18:41:20 UTC,apport information
1740180,2018-06-30 18:41:30 UTC,apport information
1740180,2018-06-30 18:41:32 UTC,apport information
1740180,2018-06-30 18:41:34 UTC,apport information
1740180,2018-06-30 18:41:35 UTC,apport information
1740180,2018-06-30 18:41:36 UTC,apport information
1740180,2018-06-30 18:41:39 UTC,apport information
1740180,2019-01-09 09:16:25 UTC,"Reproducible on DevEdition 65.0b9 on Ubuntu 18.04 (x64). The string (SecurityError: Permission denied to access property ""href"" on cross-origin object) appears multiple times in the browser console."
1740180,2018-06-30 18:41:24 UTC,apport information
1740180,2019-02-19 22:56:34 UTC,Mozilla/5.0 (Windows NT 6.1; rv:67.0) Gecko/20100101 Firefox/67.0 (20190219094627)
1740180,2019-03-21 17:26:29 UTC,apport information
1740180,2019-03-21 17:26:31 UTC,apport information
1740180,2018-06-30 18:41:28 UTC,apport information
1740180,2018-06-30 18:41:29 UTC,apport information
1740181,2017-12-26 22:11:31 UTC,"This has not been targeted to a Mahara release yet as this is additional, nice-to-have work and not needed for 18.04."
1740188,2017-12-28 06:05:02 UTC,"I have just tried the activity, and the signal at mt Vic clears ok for me in both v1.2, and the latest beta version of OR."
1740193,2018-01-13 06:05:11 UTC,Replacing the nested QCheckBox/QWidgetAction with pAction->setCheckable(true); in WTrackTableView::slotPopulateCrateMenu() seems to fix the keyboard navigation.
1740193,2020-10-22 16:29:57 UTC,"Is this fixed with recent stylesheets for all menus on Windows, too?"
1740193,2018-03-22 16:14:58 UTC,"When the Crates menu is first shown, no item is highlighted so it seems like navigating with the arrow keys would not work. However, pressing the up and down arrows does actually work."
1740193,2018-03-22 16:12:53 UTC,"I just tested this again and it actually does work, just not quite as expected. The active crate is indicated by a dotted border around the name and crates can be selected/unselected with the space bar. This is unexpected because the background color of the item in the menu does not change when it is selected. I will see if I can fix that."
1740193,2018-03-22 13:10:33 UTC,"I think you may have been working with the wrong widgets, David. Perhaps intercepting arrow key up/down events from the m_pCrateMenu and using QMenu::setActiveAction could work."
1740193,2018-03-18 22:38:32 UTC,"So, here's the things I've tried:"
1740193,2018-01-22 04:51:08 UTC,"I tried to replicate the bug, but for me the menu behaves like it should. The checkable solution I tried first, but it does not allow the tristate option which is required for correct behavior."
1740193,2018-01-08 05:11:19 UTC,Probably caused by https://github.com/mixxxdj/mixxx/pull/1341 or https://github.com/mixxxdj/mixxx/pull/1427
1740193,2017-12-28 14:12:25 UTC,"Hi Ray, we have not started working on this yet. We will change the status of this bug to In Progress when we have. I understand this is a big usability issue so this is definitely on our radar to fix soon."
1740193,2017-12-28 09:47:01 UTC,Testing the latest version of mixxx x64 2.01 alfa this problem still remains.
1740198,2018-01-01 08:43:46 UTC,looking at the code it seems still valid. i guess this can't be fixed without some kind of reservation mechanism.
1740200,2018-03-15 13:21:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740201,2020-03-18 14:31:04 UTC,Can you post screenshot/image with problem? And ideally one with how it should look if that is possible.
1740201,2017-12-27 01:50:52 UTC,"I should say that I do not believe compiz itself is responsible for applying this background, which appeared after an update that did not include compiz. However, it does not seem there is anywhere else to do anything about it: removing the packages that were updated do not remove the background, but leave it ""default black""; attempting to change the root window background with utilities like hsetroot and xsetroot proved similarly useless. I've set everything to how it was before and back again many times over, but this will not go away. It would seem the only solution is to change how compiz renders the cube to prevent this from happening."
1740201,2020-03-14 23:02:14 UTC,"This bug came back, since I have been unable to compile gnome-settings-daemon-compat to resolve it."
1740201,2020-03-16 13:11:36 UTC,What session are you using?
1740201,2020-03-17 00:32:53 UTC,"gnome-settings-daemon-compat is actually some parts of gnome-settings-daemon 3.6.1, repackaged as ""gnome-fallback-[component]-helper"". In particular, the background, media keys, and automount plugins were packaged this way. This was, at one time, used by GNOME Fallback, Unity, and other DEs to replace functionality that had gone missing from gnome-settings-daemon."
1740209,2018-01-29 19:13:55 UTC,"i'm sorry, what are you trying to achieve here? to get all alarms against a single resource?"
1740209,2018-07-30 11:39:03 UTC,"Yes, I want to get all alarms which belong to one resource by add resource into the query condition."
1740210,2018-09-10 21:35:11 UTC,"Specifically, created_at and updated_at are formatted differently to start_date, end_date, and event times."
1740231,2018-09-12 06:35:34 UTC,"Unfortunately this won't make it to the bionic kernel. For 4.15, as a temporary solution, please try https://launchpad.net/~wenchien/+archive/ubuntu/rtl8821c ."
1740231,2018-01-11 07:13:29 UTC,An update from Realtek to address an AP switching issue.
1740231,2018-01-22 19:13:51 UTC,This bug was fixed in the package linux-oem - 4.13.0-1017.18
1740231,2018-02-08 08:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740231,2018-08-19 20:52:40 UTC,This is still broken in 18.10 and 18.04. Are there any plans to fix for 18.10? I can test if you give me instructions.
1740231,2019-04-10 08:09:14 UTC,thank you
1740231,2019-05-15 10:44:11 UTC,I filed a new bug to track the SRU status: #1829220
1740232,2017-12-27 09:40:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530207"
1740232,2019-06-13 10:06:39 UTC,This issue was fixed in the openstack/python-openstackclient 3.19.0 release.
1740238,2020-01-14 04:17:19 UTC,[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.]
1740238,2019-11-14 04:30:43 UTC,Has this been seen on 18.04+?
1740238,2018-02-16 09:01:45 UTC,I currently see the same on one PC. I will retest this whenever I found the time to upgrade the computer to 17.10 or 18.04.
1740238,2018-02-16 08:56:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740238,2018-01-02 20:14:54 UTC,"This sounds annoying, sorry!  The version of deja-dup in Ubuntu 17.10 has reworked a bit of the external drive detection code, I wonder if that would work any better for you.  (Not suggesting that you upgrade to a non-LTS necessarily, but just holding out hope that 18.04 will improve this for you when you eventually do an upgrade.)"
1740242,2020-01-02 04:17:51 UTC,[Expired for guake (Ubuntu) because there has been no activity for 60 days.]
1740242,2019-11-02 21:50:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1740242"
1740258,2020-03-24 12:43:36 UTC,Is CONF.scenario.img_dir still important to glance? I'm wondering how the situation here changed over the last 2 years.
1740258,2018-01-04 12:26:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531142"
1740258,2018-01-04 11:50:19 UTC,"sounds reasonable,
propose a patch on gerrit and continue the discussion there."
1740258,2018-01-22 08:55:04 UTC,"Change abandoned by Colleen Murphy (<email address hidden>) on branch: master
Review: https://review.openstack.org/531142
Reason: I'll abandon for now, I can help with a better solution in a few weeks"
1740258,2018-01-04 11:16:09 UTC,"> if it become undeprecated for a second, it cannot be removed for more than 6~12 month
"
1740258,2018-01-04 10:52:32 UTC,"The issue is, if it become undeprecated for a second, it cannot be removed for more than 6~12 month,
if we really want to remove those options we should not do that. I have no issue with keeping those options but in this case the  https://bugs.launchpad.net/tempest/+bug/1393881 needs to be invalidated."
1740258,2018-01-12 00:00:40 UTC,"Tempest has the same stability guarantees as other projects. It just doesn't have a rest api. But for config, library interfaces, CLIs, or any other declared stable interface or end user facing bit it follows the same policy as any other project."
1740258,2018-01-04 15:41:09 UTC,The problem here is it's going to be a switchover with no warning when it happens. The deprecation was set to warn users that there is going to be a backwards incompatible change in the future on that option. img_dir is used in one place:
1740258,2018-01-04 16:47:00 UTC,"> The problem here is it's going to be a switchover with no warning when it happens.
"
1740258,2020-07-24 10:17:25 UTC,"The following patch ensures in tempest that there is at least one release which accepts both behaviors, for more details check the patch: https://review.opendev.org/#/c/710996/"
1740264,2020-03-02 03:22:56 UTC,"The hostgroups config item only takes effect for when the hosts are exported via export_nagios_definitions, this is not sent across relations at this stage.  We could clear that up by changing the documentation, or better yet add the information to the relation data and update Nagios to include hostgroups in the definition.  Since I'd prefer to see the hostgroups info available, as it's useful for operational work, I'll re-mark this as wishlist for the new feature."
1740273,2018-03-12 03:12:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740274,2020-01-13 17:52:35 UTC,Still true for Zorin OS 15.1 on my machine.
1740274,2019-09-20 09:58:29 UTC,I have the same problem on my machine
1740278,2017-12-27 17:35:18 UTC,"for example https://design.ubuntu.com/font/#navigation-closed
potential solution: soft hyphen in HTML (<wbr> vs. &shy;)"
1740279,2018-01-12 10:36:27 UTC,Since my last message the issue I've written about seems to come and go randomly.
1740279,2017-12-28 10:20:45 UTC,"The issue had occurred a number of times since upgrading to 17.10 on both my Laptop and PC, so I thought it was prudent to report it; especially as it concerns the keyring. The issue appears to have resolved itself on my PC and laptop, unfortunately I can't explain why. I am happy to provide further information if that helped."
1740289,2018-01-02 16:32:12 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1740289,2017-12-27 19:00:07 UTC,This change was made by a bot.
1740289,2018-01-15 18:41:44 UTC,"Also, I just wonder why I'm actually seeing this error printed during boot even when the 'quiet splash' options are in the cmdline. I would expect everything to be silenced-out completely in such case."
1740289,2018-04-23 01:05:35 UTC,"It's not exactly the same, but I see the following during reboot, when testing Xubuntu 18.04 daily ISO (2018-04-21), on VirtualBox 4.3 installed on a trusty system."
1740289,2018-04-23 02:07:19 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1740289,2018-03-12 14:15:19 UTC,I know this is about Ubuntu but I have exact same issue using an Arch Linux x86_64 installation with kernel 4.15.6 on another computer if that can help to rule out anything.
1740289,2018-01-15 18:40:06 UTC,"I saw the exact same messages when running bionic installed through latest cdimage builds of ubuntu. It's visible on boot almost every time (although once I noticed it was not present in the boot logs and dmesg, so it might not be reproducible 100% of the time)."
1740294,2017-12-27 19:25:46 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f34a4910e98 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f34a4910f10 ""free(): invalid next size (fast)"", action=3) at malloc.c:5006
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3867
 __GI___libc_free (mem=<optimized out>) at malloc.c:2968
 g_bytes_unref (bytes=0x210c030) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gbytes.c:310"
1740302,2017-12-28 14:59:24 UTC,After some more testing it looks like this is a duplicate of bug Bug #1176347 back from 2013.  It exists in 16.04 but not in 17.10.
1740302,2017-12-27 20:41:28 UTC,This is my first bug report please let me know if I did anything wrong or if I can provide any more info to be helpful.  Thank you!
1740311,2019-04-04 18:40:22 UTC,Is there a way to enable 'bold is bright' in terminator right now? A config option either for terminator or vte?
1740311,2018-09-07 16:18:40 UTC,"FYI: vte-0.56 / gnome-terminal 3.32 (March 2019) will flip the default of ""bold is bright"" to false. That is, unless you add a config option or a hardwired call to re-enable it, terminator users will see a somewhat different (more logical, but maybe a bit unusual) behavior."
1740311,2018-03-15 14:17:02 UTC,"> Does it mean that in the future there will be no way to disable bold text while keeping bright text?
"
1740311,2018-03-15 10:02:57 UTC,"> vte_terminal_{get,set}_bold_is_bright: Whether escape sequences such as \e[1;35m switch to bright colors in addition to bold (legacy behavior) or switch to bold and leave the color intact (new behavior, required for solarized, base16 and similar modern color schemes). (And while at it, we've removed ""Allow bold text"" from gnome-terminal's UI, and will probably start deprecating its API in about a year. I see no sane reason for this option to exist.)
"
1740318,2019-08-12 19:57:46 UTC,"I am adding a personal example of a software that I used and had this feature.
Check that I can create a full PDF with the schematic and simulation in just one page."
1740318,2018-07-30 22:59:13 UTC,"Save the results as a binary file format on the project folder and refer it on the new Eeschema file format.
May need some change on the file format."
1740320,2020-06-10 16:47:20 UTC,"> before that can i get the log url's placed in above comments. As i can't open them now.
"
1740320,2018-01-04 00:18:14 UTC,"You might be the person who I was talking with about this issue in IRC. I pushed a couple of debug patches to see if we can see the same thing in our CI testing, but I haven't dug into the logs yet:"
1740320,2018-01-04 00:22:57 UTC,The test does show the issue:
1740320,2018-01-04 00:31:30 UTC,In this case it's not even close:
1740320,2018-01-04 01:50:35 UTC,Yes I think you are the one I spoke to in IRC. I added a patch that was suggested by you in our environment and so far its been good. I am sharing that below here:
1740320,2020-06-04 13:22:15 UTC,"hi
i'm new to bug fixing , i'm likely to assign this bug to me ,before that can i get the log url's placed in above comments.  As i can't open them now."
1740320,2020-07-08 10:21:31 UTC,Here is a local reproduction of the warning log :
1740320,2020-07-13 11:36:42 UTC,i tried to reproduce the bug using same script but not able to reproduce in my setup
1740320,2020-07-15 12:01:55 UTC,"After running script for a num of times , i could reproduce only once."
1740321,2019-08-07 19:53:12 UTC,"I saw that was codded some icons:
1. Current probe: should be placed at the wire with the correct direction
2. Power probe: should be placed at the part/component
3. Voltage probe: should be place at wires
4. Differential voltage probe (same as 3 with additional in the label): should be place in two part, the first click to the (+) (positive, labeled as the `name_string+'(+)'`) and the second click to place the (-) (negative, labeled as the `name_string+'(+)'`)"
1740321,2017-12-27 23:43:53 UTC,"https://www.youtube.com/watch?v=MfQP_CK1Geg
To exemplify the power probe, not not like this video, but using as the videos before to plot in the graph results.
The point here: the power probe have to placed on the component."
1740321,2019-02-08 08:28:12 UTC,"I would really appreciate the current probe in the near future if the power probe is more complicated to implement.
Maybe also a good thing would be a possibility to type in formulas to display like the power probe mentioned in the bug report/feature request. That could be done in the ""Add Signals"" window (like Cadence PSpice)"
1740321,2019-02-08 19:21:15 UTC,"The power probe could be implement as ""sum of each pin voltage multiplied by the current fluxing to inside"".
As exemplo a resistor:
            ____
i1-> (1)---|____|---(2) <- i2"
1740321,2019-02-13 15:17:20 UTC,"In Addition to the Placements of the current probes, I think, due to the nature of spice, they can only be placed on the component pins, but that's what I have expected."
1740321,2019-08-05 22:50:06 UTC,Current probe has been implemented.
1740321,2019-08-12 19:38:35 UTC,Allowing the probes to be attached to the wires (not just in pins) allow to measure the situation attached (check the red arrow).
1740321,2019-08-12 19:31:40 UTC,"May be a opinion, and I never used LTSpice. Which appear to allow the use of current/voltage probes only in the components pins.
https://www.youtube.com/watch?v=6QzTZDm0guM
(I was trying to in install and give a ride but LTSpice is'not a Linux software...)"
1740321,2019-08-08 13:29:45 UTC,I _never_ thought I'd say this but I like LTSpice's user interface here. :)
1740321,2019-08-08 11:56:33 UTC,+1 for the LTSpice behavior.
1740321,2019-08-08 09:54:55 UTC,"I prefer the LTspice-like behaviour, and I think most people will expect it because of the LTspice market share."
1740321,2019-08-08 06:35:17 UTC,"@Hildo, that's another way to do it, but then you need 3 tools.  I much prefer LTSpice's method of switching automatically to the current probe over pins."
1740321,2019-08-05 22:50:42 UTC,"Fixed in revision a96158e26bf975f6cd068239b42ca10e5bd0fcba
https://git.launchpad.net/kicad/patch/?id=a96158e26bf975f6cd068239b42ca10e5bd0fcba"
1740321,2019-02-14 16:08:58 UTC,"Yes @Urs, usually yes."
1740335,2018-05-28 15:47:49 UTC,"I'm not sure, but I think many VST plugins are distributed in both VST2 and VST3 versions."
1740335,2018-05-28 14:13:29 UTC,"VST API documentation is available at https://github.com/steinbergmedia/vst3_doc . Inconveniently it is not hosted online anywhere as far as I can tell, so to read it you need to download that Git repository and view it locally. From a quick glance at the documentation, VST seems much more complex than LV2 and lilv."
1740335,2018-05-28 15:09:32 UTC,"Are there actually many VST3 plug-ins out there? VST2 and VST3 are not compatible.
Is there a killer plug-in, that Mixxx needs in VST2 or VST3?"
1740338,2018-04-13 07:25:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740345,2017-12-28 15:06:26 UTC,This bug was fixed in the package epiphany-browser - 3.26.5.1-1ubuntu1
1740346,2017-12-28 09:58:40 UTC,Related: bug #1097070 bug #1430464
1740349,2017-12-29 21:01:15 UTC,"could you indicate what kind of Inkscape error message you are getting, if any?
the message you quote in the first post does not appear to be an Inkscape message."
1740349,2017-12-28 11:40:33 UTC,"could you attach the eps file here, for testing purposes?"
1740349,2017-12-28 12:02:13 UTC,for testing only
1740349,2017-12-28 12:45:35 UTC,"problem not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1740349,2017-12-29 19:49:12 UTC,"@Alvin , thanks for testing.
Can anybody confirm on Linux? as I'm having problem with 0.92.2 on Linux x86_64. Thanks."
1740349,2017-12-30 14:15:07 UTC,"> $ inkscape 2525.eps
> 2525.eps:1: parser error : Start tag expected, '<' not found
> ÅÐÓÆ
> ^
"
1740363,2018-01-08 20:10:14 UTC,Probably the same problem I reported in https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1741977
1740365,2017-12-28 07:54:45 UTC,To release this we need to make skin text translatable: Bug #1731653
1740365,2017-12-28 08:24:26 UTC,"Careful here, investigate possible cross-platform issues first."
1740365,2017-12-28 08:39:56 UTC,"Sorry, it has been a long time since I have used macOS, so I forgot how that works. Maybe we could use an #IFDEF to keep a few menu items on macOS like File > Quit... or does macOS add that automatically?"
1740365,2017-12-28 10:09:05 UTC,"I like the way Firefox has solved the issue.
Hide the menu bar by default and show it by ""Alt"" all dayli items are arrange under a gear menu widget."
1740365,2018-01-14 21:11:15 UTC,"I do use the menu bar but I have to agree that it is annoying in fullscreen.
A setting for the menu bar behaviour would be the best decision from my view."
1740365,2020-10-18 01:30:06 UTC,--whooopsy wrong bug--
1740365,2020-10-18 01:29:35 UTC,https://github.com/mixxxdj/mixxx/pull/3184
1740365,2020-06-03 23:17:12 UTC,"Here is the relate Gnome Guide:
https://gitlab.gnome.org/GNOME/Initiatives/-/wikis/App-Menu-Retirement"
1740365,2020-05-05 13:37:33 UTC,"That would be a quick hack that doesn't actually solve the problem. The menu bar should be removed entirely after moving the few features that are only accessible there to other parts of the main window. Those features are:
  * Rescan Library
  * Full Screen
  * Preferences
  * the whole Help menu"
1740365,2020-05-05 13:23:56 UTC,"I would love to have the feature to mask/unmask the menu bar in full screen with the Alt key like in Firefox or Atom.
It would help to save some space on small screens and remove unnecessary informations during live sets when features are already available on the skins."
1740368,2019-02-09 22:04:16 UTC,"@Alec: what do you mean (example) by:
""Try to set child sub-categories to expense + income leads to strange behaviours without any warning"""
1740368,2019-01-28 08:27:49 UTC,Until this bug/feature is fixed could you please update the documentation?
1740368,2018-02-14 13:15:53 UTC,"For me, the suggestion makes sense.  You can have a category ""Housing"", with sub-category ""Leasing"" (income) and ""Repairs"" (expense)."
1740368,2018-01-14 21:06:29 UTC,"My idea was to define for example some subcategory structure like:
- Actions
- Actions/Buy
- Actions/Sell
- Actions/Dividens"
1740368,2018-01-03 17:51:16 UTC,"has there is a hierarchical (and so logical link, I must say no to this.
But this converge towards a co-worker suggestion to have some kind of equity category : so not expense or income, but which should be equal to 0 (or close to) at last like professional fee, or health which can have expense and income."
1740368,2019-02-10 09:56:32 UTC,Change of behaviour implemented.
1740372,2018-06-12 02:31:17 UTC,Pushing this to 2.3.0 so I can focus on the library redesign branch.
1740372,2020-03-05 19:13:51 UTC,"The way Traktor does it is really elegant. I guess this works well for mouse and controller usage, but we should also consider touch screens where fingers might cover the parameter name.
We could show the value in a small popup, using the tooltip mechanisms for placing it appropriately (left or right)."
1740372,2017-12-28 21:27:00 UTC,"This would be extremely helpful for sync'ed paramters like Echo's Time.
Until now I didn't dare to touch these knobs when Sync is On because it's lacking the feedback when snapping to a value."
1740372,2017-12-28 08:48:46 UTC,"For effect parameters, we should create a way for effects to specify human readable formats of their values, for example dB, percentage, or beat fraction."
1740375,2018-09-09 20:43:14 UTC,This is related https://bugs.launchpad.net/mixxx/+bug/911743
1740375,2017-12-28 08:56:05 UTC,Anyone want to volunteer to implement this for 2.2? It would be a nice complement to the library redesign.
1740385,2019-07-14 02:31:22 UTC,"Unfortunately, 17.10 has long since reached end of life. If the bug is still relevant, please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER"
1740396,2018-01-03 17:55:23 UTC,When people blacklist failed nodes they typically update the hostname map with dummy names like so:
1740396,2018-01-03 08:13:18 UTC,Should affect https://github.com/openstack/tripleo-validations/tree/master/validations tree
1740397,2019-09-16 14:30:19 UTC,Migrated to https://github.com/widelands/widelands/issues/1695
1740398,2018-01-02 11:00:35 UTC,"Hi,
I've found a workaround, but I still not know why my change makes it work.
In fact, I'm using a deployment tools calls Kayobe which enable me to easily deploy OpenStack.
An inventory file is generated automatically, and the deployment is based on it.
Then went I change the node order (list of node) the deployment work fine, but if i change it no deployment no longer works.
I'm thinking that Kolla try to bootstrap Ceph cluster using predefined order (in ceph.conf, with the list of node) which is not the real order (the one provided by my inventory file)."
1740399,2018-01-02 11:00:37 UTC,"Hi,
I've found a workaround, but I still not know why my change makes it work.
In fact, I'm using a deployment tools calls Kayobe which enable me to easily deploy OpenStack.
An inventory file is generated automatically, and the deployment is based on it.
Then went I change the node order (list of node) the deployment work fine, but if i change it no deployment no longer works.
I'm thinking that Kolla try to bootstrap Ceph cluster using predefined order (in ceph.conf, with the list of node) which is not the real order (the one provided by my inventory file)."
1740401,2020-12-29 22:22:40 UTC,https://wiki.gnome.org/Apps/GTG is the new location for the foreseeable future!
1740405,2018-01-04 09:52:13 UTC,"It depends to the old CPU . It needs kernel installation with> force PAE<. In Updates it is impossible to switch. ""Linux Mint"" installation tells while updating, not to install the new Kernel. It will not work (no PAE-CPU). - So the System will work perfekt.
 In my case I abandon this old notebook. In competition to my PC it is deadly slow.
Thanks for your helping, and excuse my delay. it's not easy to me, to write this in english. Please excuse mistakes.
a.b."
1740405,2018-01-02 16:28:59 UTC,You may need to run the following from a terminal:
1740405,2017-12-28 16:30:03 UTC,This change was made by a bot.
1740406,2017-12-28 20:21:42 UTC,"The attachment ""lightdm-check-close-status.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1740415,2017-12-31 02:38:51 UTC,"Before I started having problem, I was able to take a photo or clip art upload into inkscape.  Would click on the photo then click on trace bitmap.  and say how many color there were.  From there I press ok.  Then get rid of original photo.  Click on the photo ungroup it.  Then I would have for ex two layer.  For photo I choice the best layer, save then up load it into cricut design space to be cut out.  If it clip art and I wanted to have color  I would usually save the black color layer and then fill in the spaces to reproduce the art again, then dowload into design space to be cut.What is happening now when I click on the photo, I go and click design space and nothing happening at all.   After trying remove and reload inkscape now all my svg even ones that I did not convert in inkscape are no longer opening in cricut design space."
1740415,2017-12-30 13:07:08 UTC,"could you provide detailed steps to reproduce the problem?
- including:
1. which files did you begin with, provide samples
2. which specific operation did you perform
3. what was the expected outcome
4. what was the actual outcome"
1740415,2017-12-30 12:46:38 UTC,"Correct they all converter,  but now no matter what I put in Inkscape clip art or photo trace  bitmap doesn’t work at all. Plus the old svg and even ones I had down from someone else are not going in design space,  it say file not expected. Thank you for your help."
1740415,2017-12-30 04:35:09 UTC,"as far as I can tell, these files all consist exclusively of paths, meaning that they have already been successfully converted."
1740415,2017-12-29 14:18:20 UTC,"not sure why, but I am not able to download any of your attachments.
similarly I am not able to open them, either, when I double click on them in the webpage"
1740415,2017-12-29 14:05:30 UTC,"I use inkscape to convert photo and clip are into svg file so I can cut them in design space on my criciut.  it just stop working while i converting photo for a project.  Trace bitmap doesn't come up at all.  attach are some photo that used in inkscape and some svg files I have made.  The one save in my computer are not dowloading into design space at all now since I try removing and adding inkscape back onto my computer.
   On Thursday, December 28, 2017, 11:40:48 AM PST, Alvin Penner <email address hidden> wrote:"
1740415,2017-12-28 19:34:04 UTC,"- problem not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1740415,2017-12-31 10:56:46 UTC,"thank you for the bitmap files. I tried the trace bitmap on both of them and both appear to work normally as far as I can tell. (using Windows 10 and Inkscape 0.92.2 (5c3e80d, 2017-08-06))"
1740415,2017-12-30 03:32:44 UTC, Hopefully this works
1740421,2017-12-29 09:29:12 UTC,"debug and have a look at the BufferedImage returned by
vnc.capture(tLocked).getImage()"
1740421,2017-12-29 15:00:48 UTC,The BufferedImage looks the same as the second image in the attached distorted.png
1740421,2018-02-26 19:03:16 UTC,I have found a way to bypass this issue:
1740421,2018-03-06 15:06:00 UTC,"@Julian
Could you give it a test?"
1740421,2018-03-08 17:21:41 UTC,"Verified in 1.1.2 2018-03-10
The issue has been fixed, I can no longer reproduce it."
1740426,2020-01-07 22:18:45 UTC,The epics integer types from epicsTypes.h are the same on all architectures:
1740426,2020-01-07 00:24:54 UTC,Considering the fact that issues related to these constructs are popping up again and again I would also like to see this addressed.
1740426,2020-01-07 02:42:58 UTC,"> I've been in the habit of using '%lld' and '%zu' to print 'long long' and 'size_t' respectively.
> However, the windows world needs '%I64d' and '%Iu' instead.
> It would be nice to have compatibility macros for this.
"
1740426,2020-01-07 14:53:05 UTC,"Mark, you're right, MSVC supports %z for size_t (which is certainly preferred over the Microsoft-specific %I). This is supported at least since VS 2015 (https://docs.microsoft.com/en-us/cpp/c-runtime-library/format-specification-syntax-printf-and-wprintf-functions?view=vs-2015#size-prefixes-for-printf-and-wprintf-format-type-specifiers). But I'm not aware of a sane portable way of writing"
1740426,2020-01-12 02:41:11 UTC,"> Because of the promotion rules these should use the unmodified printf()
> format specifiers %d/i/o/u/x except for the 64-bit types which need the
> %ll modifier, even when building for Windows.
Rather than making assumptions about the mapping to platform-dependent types we should leave these things up to the standard library. Also technically long long is part of C99/C++11.
"
1740434,2017-12-28 23:44:39 UTC,"I got the program to load, but it takes some work and I have to do it in terminal.  Sometimes I have to use ""sudo apt-get remove parcel-tracker && sudo apt-get purge parcel-tracker && sudo apt-get autoremove"" in order for it to work and it will only load in terminal.  I also have a problem were USPS will not work and displays errors in the terminal.  I do not know what is going on but these problems just started all the sudden after I tried to clone my drive with a drive cloner that failed to clone the drive.  Every thing else is fine except my parcel tracker.  I do not know why the very latest version  will not load and why I am getting these errors unless I use the command I listed and then run it from terminal or use the older version and just launch it in terminal.  IF i used the icon it will not work and oif I use the newest version it will not work at all and give me that error unless I remove and reinstall and run from terminal right after."
1740434,2017-12-29 11:05:42 UTC,"It seems that your parcels list became corrupted.
Try to execute in your terminal: ""gsettings reset-recursively net.launchpad.parcel-tracker"""
1740438,2017-12-28 22:30:06 UTC,This change was made by a bot.
1740438,2018-01-02 17:02:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1740438,2018-01-02 19:55:10 UTC,This issue has been present since I installed a fresh copy of Xubuntu 17.10 about 3 weeks ago.
1740438,2018-01-03 06:43:24 UTC,"Please try this Linux kernel:
http://people.canonical.com/~khfeng/lp1740438/"
1740438,2018-01-04 05:21:12 UTC,"kaihengfeng, it seems to happen a little less often with the linked kernel, but I'm still experiencing the error. I have copied my dmesg output below."
1740438,2018-01-12 09:19:50 UTC,"Before sending the patch to upstream, can you try [1] again? Thanks!"
1740438,2018-01-06 18:02:01 UTC,I tested the above kernel over 15 reboots and the mouse activated successfully every time. Great work! You're a legend. Let me know if you need any additional information.
1740438,2018-01-04 07:29:33 UTC,"Please try this kernel:
http://people.canonical.com/~khfeng/lp1740438-2/"
1740441,2018-03-27 02:17:56 UTC,I suddenly can't remember how to make the tags appear. But I do remember the appearance of this bug.
1740441,2018-03-26 12:56:30 UTC,Could you add a screenshot to the bug? The external one you are referencing to is not valid
1740441,2018-01-29 10:18:11 UTC,"updated, I'll open a new title for other bugs."
1740441,2018-01-29 03:43:04 UTC,I feel this bug is covering too many different unrelated issues. So it would be difficult to track and resolve.
1740441,2018-01-02 09:40:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740441,2018-01-02 09:40:36 UTC,"Thanks for the bug report. Ideally we should have one bug report per bug, so please see if you can split this bug up with some separate bug reports."
1740458,2018-04-03 10:41:47 UTC,"I solved it by configure it follow below:
trove_auth_url = http://controller:5000/v3"
1740458,2018-04-03 10:02:28 UTC,I also have the problem with the queen version.
1740459,2018-01-25 08:44:58 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3770
1740459,2018-01-12 02:40:16 UTC,"This bug fixed in 5.6.38, 5.7.20.
https://github.com/mysql/mysql-server/commit/9414c7035020a1915db56101aa7929d8b4069d83#diff-8c78bfc758be72b7df2306f1d9984c47"
1740462,2018-01-02 16:59:53 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1740462,2017-12-29 06:00:07 UTC,This change was made by a bot.
1740462,2018-03-04 04:17:40 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1740462,2018-04-13 20:40:12 UTC,"I've just experienced same problem on 17.10, 4.13.0-38-generic"
1740463,2018-01-08 05:57:59 UTC,"Change abandoned by wangjun (<email address hidden>) on branch: master
Review: https://review.openstack.org/530700
Reason: It's a big project to realize a new storage project.Eventhough, this patch can work."
1740463,2018-01-02 07:21:26 UTC,this patch works in my environment
1740463,2018-01-02 07:20:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530700"
1740463,2018-01-02 06:01:03 UTC,who can merge it to master?
1740463,2018-01-02 05:59:45 UTC,"tesora already fixed it. the code link is:
https://github.com/Tesora-Release/tesora-trove/tree/master/trove/common/strategies/storage"
1740466,2017-12-29 07:53:39 UTC,Hi there!
1740470,2018-01-24 22:29:29 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1468
1740470,2017-12-29 09:36:40 UTC,pt-archiver 3.0.5
1740470,2017-12-29 08:12:31 UTC,my mysql server version is MySQL5.6.30，binlog_format=row
1740479,2019-11-05 04:17:28 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1740479,2017-12-29 12:45:59 UTC,Thanks for reporting.
1740479,2019-11-05 04:17:30 UTC,[Expired for llvm-toolchain-4.0 (Ubuntu) because there has been no activity for 60 days.]
1740479,2019-09-05 09:27:59 UTC,"Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019."
1740484,2018-01-24 15:09:21 UTC,This may be EFI bios related / amdgpu.ko kernel driver dpm powerplay related.
1740484,2018-02-07 03:27:58 UTC,"If the bug is specific to ""Wayland"" sessions then this is a bug in the 'eglnative' backend of package 'mutter' (used by gnome-shell)."
1740484,2018-08-15 05:00:09 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1740484,2018-03-24 11:00:31 UTC,"I'm a bit in doubt where to provide updates for this bug, as it is also reported for:"
1740484,2018-02-07 08:37:51 UTC,Created mutter issue #22:
1740488,2018-01-17 02:20:56 UTC,"Hello, this may be a symptom of hardware failure or it might be a simple case of corrupted file, it's hard to know what happened."
1740489,2017-12-30 23:55:36 UTC,compiz --replace has no effect.
1740489,2017-12-30 06:39:03 UTC,I can not reproduce. Please try a fresh live usb if you can reproduce.
1740500,2017-12-29 13:31:32 UTC,Thanks Pope! I also faced this issue while registering the name (instantnews).
1740507,2018-01-11 05:39:07 UTC,"Hi Antony,"
1740507,2018-01-02 13:56:42 UTC,Can someone at HP tell which package is needed here?
1740507,2018-10-15 21:48:22 UTC,"root@fanta-Lenovo:~# uname -a
Linux fanta-Lenovo 4.15.0-36-generic #39~16.04.1-Ubuntu SMP Tue Sep 25 08:59:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1740507,2018-12-21 16:48:43 UTC,"Nearly a year later since the OP, and still receiving this error message. Running Ubuntu Studio 16.04.5 LTS on my end."
1740507,2018-12-04 09:53:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740508,2019-06-30 16:02:04 UTC,"Bug won't expire due to bug watch.
Closing for same reason as upstream bug was closed - no response from reporter."
1740508,2019-05-24 17:35:29 UTC,"Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Upstream report was closed ""RESOLVED INCOMPLETE"" on 2018-01-18 due to lack information."
1740508,2017-12-29 14:41:57 UTC,"(edit) #2: Short URL: https://goo.gl/GhNUyW
(Also seen under the 'Attachments' list)"
1740508,2017-12-29 14:40:55 UTC,"See 'example site source code + css.'
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1740508/+attachment/5028738/+files/https%3A_www.kraken.zip"
1740510,2017-12-29 15:20:07 UTC,I've had a lot of difficulty understanding the documentation and I'd like to offer some suggestions.
1740512,2018-04-17 19:33:37 UTC,"That would be a nice option, but that would be a separate feature."
1740512,2018-04-17 15:29:21 UTC,Would you also want to add noise-canceling to the mic processing channel to remove spillover from the main/monitor mix?
1740513,2018-03-19 13:52:35 UTC,"No, I didn't, and I don't have time for this for 2.1. So yeah, let's push it back.."
1740513,2018-03-19 13:26:46 UTC,"ronso0, have you been working on this? If not, we can push it back to 2.2."
1740513,2018-01-26 22:47:10 UTC,"I'll start to fix this as soon as those PRs are merged:
LateNight https://github.com/mixxxdj/mixxx/pull/1489
Shade https://github.com/mixxxdj/mixxx/pull/1459"
1740513,2018-04-23 20:08:19 UTC,"I started something in this direction
https://github.com/mixxxdj/mixxx/pull/1642"
1740513,2018-11-04 02:37:23 UTC,https://github.com/mixxxdj/mixxx/pull/1848
1740521,2017-12-30 11:56:50 UTC,"This effects all effect with a group delay.
Basically all fidlib based filter suffer this problem. The biquad based EQs are also effected when not at unity.
We may add a group delay reporting facility and compensate the dry pass accordingly but unfortunately the group delay is also frequency depending for all non Bessel EQs
So we need a kind off all pass filter for compensation."
1740522,2018-05-16 02:55:30 UTC,"If this bug is a problem for you then please ask the gdm developers to prioritize it here:
https://bugzilla.gnome.org/show_bug.cgi?id=792236"
1740522,2018-05-12 17:58:22 UTC,"I have the same problem after upgrading ubuntu from 17.10 to 18.04. And GUI doesn't start.
What should I do?"
1740522,2018-03-19 06:58:16 UTC,I have this bug on Ubuntu 18.04. My log for gdm3:
1740522,2018-01-08 08:32:58 UTC,That is highly likely unrelated to the log messages we're talking about. Please ensure your two issues have two different bug reports.
1740522,2018-01-05 02:02:05 UTC,Next step: Please report the issue to the GDM developers using this link:
1740522,2018-01-05 01:57:39 UTC,"Thanks. Confirmed, but it doesn't seem to be causing any serious problem right now (?)"
1740522,2018-01-04 10:49:07 UTC,It would be an easy fix if the assertion message printed the backtrace of the apps calling in glib.
1740522,2018-01-04 10:26:24 UTC,"I also saw many comments about this via the web, but didn't see any bugs people could track the situation with."
1740522,2018-01-04 01:56:03 UTC,Probably both are true... A quick google shows many apps experiencing that same assertion failure.
1740522,2018-01-03 15:21:50 UTC,"According to the Logs application, the sender of the message was gdm3, so it seemed a reasonable guess."
1740522,2018-01-02 09:43:47 UTC,Sounds like a problem with gnome-terminal:
1740522,2018-01-05 10:57:02 UTC,"> but it doesn't seem to be causing any serious problem right now (?)
"
1740527,2018-09-03 01:27:02 UTC,Possibly related issue: https://bugs.launchpad.net/evergreen/+bug/1789982
1740529,2019-03-13 21:06:35 UTC,Looping back to this. Bump
1740529,2019-03-25 15:53:35 UTC,"It seems like this could be a really nice feature to have as a workstation setting.  Not only would some staff members get really excited about being able to create their own color scheme, but different users have issues with different colors and color combos, and it would be great if they could adjust according to their individual needs."
1740536,2018-01-02 06:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740544,2018-06-05 07:46:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/572287"
1740544,2018-01-01 04:32:01 UTC,"yes, with migration_policy as 'on-demand'(this is what test do) it has to be admin user. This is fixed in your patch - https://review.openstack.org/#/c/530508/"
1740544,2018-01-01 04:34:00 UTC,++ tempest in this bug to add a test the retype with 'never' migration policy.
1740544,2018-01-03 16:50:01 UTC,This may be related to bug 1698224.
1740544,2018-01-07 01:32:00 UTC,"Reviewed:  https://review.openstack.org/530508
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=65e4f9b9d1f0c61636895cc133062bf0a6263848
Submitter: Zuul
Branch:    master"
1740544,2018-07-03 06:48:05 UTC,"Reviewed:  https://review.openstack.org/572287
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=a3a67d476132fe5f55020cf2dc1f672c17be6eb3
Submitter: Zuul
Branch:    master"
1740544,2020-10-26 10:52:46 UTC,Unassigning due to a long inactivity.
1740550,2017-12-29 22:41:52 UTC,hipdnsproxy has not been updated for Python 3.
1740550,2017-12-29 22:56:18 UTC,"To elaborate, the ""except IOError, ioe:"" syntax is obsolete in python3 and we should use ""except IOError as ioe:"" instead. This, however, is not the only issue and simply changing this syntax will not make it work."
1740550,2017-12-30 18:42:38 UTC,Should #! /usr/bin/env python2.7 be added so it knows which interpreter to use?
1740551,2017-12-30 01:17:21 UTC,Skins show the short names but the full names and descriptions are shown in tooltips.
1740551,2017-12-29 22:12:53 UTC,german translation
1740551,2017-12-30 01:16:05 UTC,"Effects and effect parameters now have short names separate from their full names. Both can be translated. If you'd like to contribute to translation, details are on the wiki: https://mixxx.org/wiki/doku.php/internationalization"
1740551,2017-12-30 14:32:55 UTC,Different issues are mixed up here:
1740551,2017-12-30 22:18:27 UTC,"A related issue is that we have no length limit for the rendered text in Transiflex.
My idea to use a reference rendered text like ""Lorem ipsum"" to compare with the rendered translation is a stucked discussion. Should we introduce this?"
1740556,2020-04-09 20:35:35 UTC,Sounds like the same crash as bug 1786822
1740561,2021-01-14 13:39:22 UTC,"I have this controller. With all Mixxx versions I have used (2.2, 2.3-beta, 2.4-alpha), I'm happy with how this controller works with Mixxx. If there's some guidance (wiki documentation?) how to update Mixxx legacy code to current best practices, I can give it a try."
1740567,2017-12-30 04:50:25 UTC,"I mistake 「ttf-arphic-uming」⇒「fonts-arphic-uming」.
Changed Packages names now."
1740576,2018-03-16 08:57:48 UTC,The following workaround works for me:
1740576,2018-03-16 08:55:37 UTC,This is independent of paparazzi.
1740576,2018-03-16 08:54:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740576,2018-02-26 08:48:52 UTC,It seems that the package that contains ocamlbuild has not being updated accordingly?
1740578,2020-04-12 20:22:49 UTC,This bug was fixed in the package xfce4-taskmanager - 1.2.3-0ubuntu1
1740578,2019-04-24 20:23:56 UTC,"The tooltip is no more, the information is now shown in a statusbar that can be shown or hidden (shown by default)."
1740578,2019-04-24 20:22:59 UTC,Simon Steinbeiss referenced this bugreport in commit a18b8bd3c357af82fd68e1e11a046d7727b02c51
1740578,2019-04-21 14:14:29 UTC,"Created attachment 8437
proposed patch"
1740578,2019-04-03 01:10:55 UTC,I can still reproduce this with 19.04.
1740578,2018-08-13 23:05:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740578,2017-12-30 08:53:47 UTC,Hovering over a process shows a key to colours used to show when the state of process is changing.
1740578,2019-11-01 10:18:30 UTC,"@ochosi, Can you release a new xfce4-taskmanager version? We can pull it into 20.04 and cleanup one of these papercut bugs :)"
1740587,2017-12-30 10:52:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/530535"
1740587,2017-12-30 10:52:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/530536"
1740587,2018-08-09 13:13:46 UTC,This issue was fixed in the openstack/networking-generic-switch 1.2.0 release.
1740587,2018-01-06 12:44:15 UTC,"Reviewed:  https://review.openstack.org/530536
Committed: https://git.openstack.org/cgit/openstack/networking-generic-switch/commit/?id=6c2e671d3db958305009f8a1cfe9d7ece81117ec
Submitter: Zuul
Branch:    master"
1740587,2018-01-05 16:19:09 UTC,"Reviewed:  https://review.openstack.org/530535
Committed: https://git.openstack.org/cgit/openstack/networking-generic-switch/commit/?id=a4631e15baa4a0294cf031ec85b64a13dd4b14bc
Submitter: Zuul
Branch:    master"
1740587,2018-01-05 16:13:28 UTC,"Reviewed:  https://review.openstack.org/530534
Committed: https://git.openstack.org/cgit/openstack/networking-generic-switch/commit/?id=3ac398a481c8f715b8b47cfc623a3935daa9ba70
Submitter: Zuul
Branch:    master"
1740587,2017-12-30 10:52:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/530534"
1740590,2017-12-30 18:12:37 UTC,First: You should _not_ use tools like as bleachbit.
1740590,2017-12-30 12:00:04 UTC,This change was made by a bot.
1740592,2017-12-31 12:53:23 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1740594,2018-01-16 21:40:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740594,2017-12-30 16:18:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1740595,2020-08-24 18:06:30 UTC,This should no longer be a problem with Snapcraft 4.x (or 3.x)
1740600,2018-08-07 04:40:12 UTC,A possible workaround is described at https://askubuntu.com/a/1042998/68491 :
1740600,2018-08-07 04:38:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740627,2019-08-28 04:29:38 UTC,Lernid was removed from Ubuntu after 18.04 per https://bugs.launchpad.net/ubuntu/+source/lernid/+bug/1739622
1740632,2018-02-01 15:36:36 UTC,"I removed the update, because I need the printer. So, I can't do what you ask. If the update doesn't work I'll have to remove the update and reinstall 17.01. More then a days work. Can't use USB to install Linux, doesn't see the port. I purchased a 14.01 USB, but HP is one of the computers that need to update the BIOS.Have 17.01 on CD, which works. Tried to copy USB to CD can't get it to do it.Should have ""where to download too"" when downloading Linux.
Really believe Microsoft is the problem when it's installed won't let you change OS.
When I get around to trying upgrade again I will let you know.Thanks for all your help."
1740632,2018-02-01 12:32:18 UTC,"Hi Fred,"
1740632,2018-01-11 14:52:03 UTC,"There is no error file. The driver for the printer loads some as it does in 17.04, but receive no Y/N at the end to finish loading. If I up date to 17.10 and it doesn't work I have to reload 17.04 by formatting my computer, I lose all my internet links. I will suffer with the desktop not working and the blinking screen for now. If the manufactures would fix the BIOS I could put in an earlier version of Linux. Thank you."
1740632,2018-01-11 12:30:14 UTC,"Hi Fred,
It would be helpful if you can upload the error.log file and the error details you see in the terminal for further analysis as we are not able to reproduce this issue in lab.
Thanks,
Nishitha"
1740632,2018-01-04 19:27:58 UTC,"I upgraded to 17.10 and printer is not recognized. When I put the the driver 3.17.11 in the terminal, it loads, but doesn't go to the Y/N. Which it does on the 17.04 version, then loads the rest and works. Can't send you what loads in terminal, reinstalled 7.04. Which still has the problem with the desktop not work properly. I have 14.01 on a USB, but the BIOS don't work. I have the 17.04 on a CD which works. Tried to get 14.01 on a CD won't work.I have emailed HP numerous times since September 3rd, when Hp was suppose to get back to me. Thanks ahead."
1740632,2018-01-04 13:02:04 UTC,"Hi Fred,
Can you give more details on this query?
1. 17.01 is the distro version where you are testing this scenario?
2. Please specify the distro name and version you are checking this scenario.
3. What is the error you are getting for this scenario?
4. Please upload the error.log file"
1740634,2017-12-30 22:09:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1740635,2019-06-12 10:02:44 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1740635,2017-12-31 00:20:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1740637,2019-11-03 18:07:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740637,2019-10-26 11:05:19 UTC,Is this still planned for the 20.04 cycle?
1740637,2019-12-18 12:58:31 UTC,This bug was fixed in the package libappindicator - 12.10.1+18.04.20180322.1-0ubuntu5
1740640,2018-03-19 15:34:55 UTC,Thanks for the followup.
1740640,2017-12-31 14:56:51 UTC,Some more info:
1740640,2017-12-31 15:03:31 UTC,"Killing the fcitx process removes the keyboard icon from indicator-appmenu-complete, thus preventing the situation that leads to the system going unresponsive."
1740640,2018-03-19 08:33:24 UTC,I believe this issue was caused by mate-hud and is now resolved. Can you confirm?
1740640,2018-06-30 07:35:35 UTC,"Killing fcitx from a terminal window (Ctrl + Alt + F2) ""unfreezes"" the session but the desktop is still frozen (no right click), and it stops one from being able to add keyboard layouts etc."
1740640,2018-10-22 22:01:33 UTC,"Using Ubuntu Mate 18.04.1 ISO I’m experiencing the above bug as well. Removing the input applet from the panel let me continue using the live ISO, but isn’t a fix."
1740642,2018-01-11 12:23:00 UTC,"Hi Benjamin,
We tried to reproduce the issue in printer HP-officejet-pro-8610 as we don't have the printer officejet_7100_series in our lab. We will try to find the printer model you reported this issue and update our findings."
1740642,2018-01-11 16:14:45 UTC,"Hello Nishitha,"
1740650,2018-04-21 10:27:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740654,2017-12-31 06:26:39 UTC,"StacktraceTop:
 XInternAtom (dpy=dpy@entry=0x1d768e0, name=name@entry=0x7ffe62c55590 ""HIME_ADDR_ATOM_hime"", onlyIfExists=onlyIfExists@entry=0) at ../../src/IntAtom.c:174
 get_hime_addr_atom (dpy=dpy@entry=0x1d768e0) at ../im-addr.c:73
 hime_im_client_reopen (hime_ch=hime_ch@entry=0x0, dpy=dpy@entry=0x1d768e0) at hime-im-client.c:89
 hime_im_client_open (disp=0x1d768e0) at hime-im-client.c:289
 get_im (context_xim=0x24ab190) at gtkimcontexthime.c:147"
1740662,2018-03-02 15:17:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1740666,2018-03-05 19:50:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740666,2018-01-02 06:00:09 UTC,This change was made by a bot.
1740666,2018-01-02 08:58:44 UTC,I can read hw clock:
1740666,2018-01-07 04:57:30 UTC,journalctl output after resume: https://paste.ubuntu.com/26337345/
1740666,2018-02-01 03:35:09 UTC,I think LP: #1744988 is the same bug as this one.
1740666,2018-01-02 05:54:58 UTC,Does this system have hardware clock?
1740666,2018-04-05 11:41:22 UTC,#1744988 bug not resolved this for me.
1740667,2020-06-23 17:21:22 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/560794"
1740667,2018-04-29 08:50:47 UTC,"Reviewed:  https://review.openstack.org/560793
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=dc8610a2bcefbd4ca46710a0df0446b2cf4df438
Submitter: Zuul
Branch:    master"
1740667,2018-04-29 08:37:28 UTC,"Reviewed:  https://review.openstack.org/560792
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=d083aa621178d283a98d9f0a7d57d7b412a68b4b
Submitter: Zuul
Branch:    master"
1740672,2017-12-31 13:08:48 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1740674,2019-09-16 08:44:19 UTC,Migrated to https://github.com/widelands/widelands/issues/3247
1740682,2017-12-31 13:08:47 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1740686,2017-12-31 15:08:52 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1740687,2018-07-25 23:36:09 UTC,I installed dokuwiki_0.0.20160626.a-2.1_all.deb manually (from the cosmic repo) to get it working. There is an important bug fix in that version that hasn't yet been released to bionic.
1740687,2018-07-25 21:19:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740691,2018-04-28 12:45:47 UTC,This affects me in 18.04 after release as well.
1740691,2018-01-02 16:34:21 UTC,Hello
1740692,2018-04-17 16:12:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740695,2018-01-01 14:37:51 UTC,Here are the things I can think of :
1740695,2017-12-31 17:37:50 UTC,100% bit-to-bit reproductible build under windows using MSVS seems an impossible goal because the executable itself contain (at least) the build date.
1740695,2017-12-31 17:50:52 UTC,Someone made tool to fix that: https://github.com/jasonwhite/ducible
1740695,2018-05-27 17:30:03 UTC,"I'm all for reproducible builds, but this is feasible for 2.2? It's quite a big project -- particularly b/c our dependencies need to be reproducible and we have a lot of dependencies."
1740698,2018-03-14 19:20:16 UTC,"Reviewed:  https://review.openstack.org/530890
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=4c9120434458d17298fa38a32dfcc76c72697e56
Submitter: Zuul
Branch:    master"
1740698,2018-02-09 16:34:00 UTC,This issue was fixed in the openstack/networking-ovn 4.0.0.0rc1 release candidate.
1740698,2018-01-03 10:17:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/530890"
1740698,2018-01-03 01:23:35 UTC,"For openvswitch specifically, min. required version dep could be documented in
https://github.com/openstack/networking-ovn/blob/master/requirements.txt#L8"
1740698,2018-01-02 20:51:46 UTC,"Fix released: https://review.openstack.org/#/c/530721/
I sent the patch before I saw this bug so missed the ""Closes-Bug"" tag."
1740698,2018-01-02 15:10:19 UTC,"You could argue that networking-ovn shouldn't have such strict OVS version requirements. We might be imposing unfriendly requirements from distros and operators, not to mention that the required version is not discoverable / documented."
1740698,2018-01-02 09:11:33 UTC,The reason for the failure is because of this patch - https://review.openstack.org/#/c/527680/9 which Emilien pointed out in the bug report.
1740698,2018-01-02 08:52:07 UTC,Looking into why its failing.
1740698,2018-01-01 19:15:08 UTC,tempest.scenario.test_network_basic_ops.TestNetworkBasicOps
1740698,2018-01-26 00:03:09 UTC,Reintroduced in https://review.openstack.org/#/c/528746/19/networking_ovn/ovsdb/commands.py@1034
1740698,2018-01-01 13:58:32 UTC,can you specify which test fails?
1740698,2017-12-31 23:03:06 UTC,"Reviewed:  https://review.openstack.org/530593
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=2f14e6d3ad15c71f6919bfdebfdd1208ab8b2503
Submitter: Zuul
Branch:    master"
1740698,2017-12-31 17:43:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/530593"
1740698,2018-04-19 14:11:14 UTC,This issue was fixed in the openstack/networking-ovn 5.0.0.0b1 development milestone.
1740698,2018-03-20 13:29:42 UTC,"<< Since it's a new issue new bug can be opened for it.

>> https://bugs.launchpad.net/tripleo/+bug/1757134
"
1740698,2018-03-16 13:23:58 UTC,"<<< This time it's SSH issue, keys are not injected into instance, so SSH via key fails:-

>>>


Looking further i found that SSH keys are injected but not that which are provided by ovn metadata(or passed during vm creation) but by metadata agent running for rdocloud."
1740698,2018-03-16 05:37:59 UTC,"After reverting it we are having a new issue both in master and queens:-
https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset030-master/36ddc06/undercloud/home/jenkins/tempest/tempest.html.gz
https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset030-queens/a55e13e/undercloud/home/jenkins/tempest/tempest.html.gz"
1740698,2018-01-05 21:08:06 UTC,"Followup fix https://review.openstack.org/531425
Alternatively, we have prepared https://github.com/rdo-common/openvswitch/pull/5 to update OVS 2.8.1 based RPM in RDO deps repo, before upstream 2.8.2 is released."
1740698,2018-01-24 23:39:08 UTC,This issue was fixed in the openstack/networking-ovn 4.0.0.0b3 development milestone.
1740705,2021-01-25 07:47:12 UTC,What kind of problem do you encounter when trying to reinstall Ubuntu? Does it still happen?
1740711,2018-08-14 09:42:44 UTC,Please point the fix for this issue
1740711,2019-03-10 09:51:03 UTC,Hi jethro.sun
1740711,2018-11-22 11:30:50 UTC,packstack completed...
1740711,2018-11-21 15:13:53 UTC,Was able to kill the old one and the puppet run continued. No neutron server got started but after starting it manually it came up. Still think there is something wrong here.
1740711,2018-11-21 15:11:14 UTC,Looking I already have a neutron server running (since previous puppet run) and also a hanging systemctl
1740711,2018-11-21 15:05:29 UTC,Waiting for neutron to start...
1740711,2018-11-21 14:45:37 UTC,"My packstack pike run on a newly install CentOS 7.5.1804 is also stuck.
Using the --allinone option. 32GB machine."
1740711,2018-08-14 09:41:30 UTC,Am still facing this issue . can anybody suggest me the solution . Tried to check the logs located in the
1740711,2018-01-08 20:21:55 UTC,"Hi Javier,"
1740711,2018-01-08 18:18:37 UTC,"The error from the last log is very likely a transient network issue, I've just tested it and the package mentioned in it (python-zmq) can be downloaded."
1740711,2018-01-02 17:20:30 UTC,I manage to get a physical node and test the installation again. Now the ``packstack --allinone`` failed directly. Any ideas?
1740712,2017-12-31 23:08:50 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1740712,2018-03-01 19:48:25 UTC,The test instructions are flawed; you need to have an existing install on the disk to resize.
1740726,2018-05-15 07:46:39 UTC,"Reviewed:  https://review.openstack.org/538629
Committed: https://git.openstack.org/cgit/openstack/charms.ceph/commit/?id=c84b7b9449de7e81c42f33658ef43f6f156a8fa5
Submitter: Zuul
Branch:    master"
1740726,2018-01-04 14:39:08 UTC,I have a patch in progress: https://review.openstack.org/#/c/530814/
1740726,2019-08-20 20:58:43 UTC,"Change abandoned by Chris Sanders (<email address hidden>) on branch: master
Review: https://review.opendev.org/530814"
1740734,2018-01-17 05:38:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740736,2018-04-21 02:04:14 UTC,I took lm-sensors out of the bug title because lm-sensors 1:3.4.0-4 works fine with an updated it87 driver.
1740736,2018-01-01 11:26:35 UTC,"A recent mobo/chipset also need to use a recent kernel: here at least 4.13
https://www.mjmwired.net/kernel/Documentation/hwmon/it87"
1740736,2018-01-01 12:34:16 UTC,"@dino99 look at the sources, it8686 is _not_ supported in the link you mentioned, the driver needs updating, independently of using kernel 4.10, 4.13 or future."
1740736,2018-01-01 14:05:48 UTC,"here is the patch that include it8686
https://lkml.org/lkml/2017/6/11/3"
1740736,2018-01-01 14:10:15 UTC,A Debian example  https://urfoex.blogspot.co.uk/2017/04/ryzen-on-linux-running.html
1740736,2018-01-02 21:51:54 UTC,"@dino99, quick notes:"
1740736,2018-01-13 09:26:24 UTC,"I'm now running kernel 4.13.0-26-generic and, as expected, my fan sensors are getting detected but _not_ supported by it87 driver (chipset 0x8686)."
1740736,2018-01-16 16:28:30 UTC,"What about testing with kernel 4.14.13 or 4.15.rc8 to know if that driver has been added?
 ( kernel.ubuntu.com/~kernel-ppa/mainline/ )"
1740736,2018-01-21 10:06:32 UTC,If 0x8686 is not in the sources https://github.com/torvalds/linux/blob/v4.15-rc8/drivers/hwmon/it87.c it won't simply work...
1740736,2018-02-21 16:59:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740736,2018-04-23 03:15:54 UTC,Is there anyone trying to upstream this?
1740736,2019-09-09 08:00:17 UTC,"Emanem, can you confirm if the latest kernel is working now?"
1740736,2019-09-18 14:11:15 UTC,IT8686E does not work on X470 motherboard and upstream 5.2.15 kernel. There has been no upstream movement around `linux/drivers/hwmon/it87.c` since 2 years.
1740736,2019-11-18 04:17:32 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1740737,2018-01-01 11:16:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740737,2018-01-01 11:16:03 UTC,Also seemly the same or similar issue reported at:
1740737,2019-02-17 20:04:52 UTC,"Git commit dab5abcd2172155c511e0666d867c37382829226 by Andrius Štikonas, on behalf of Jiva Totin.
Committed on 17/02/2019 at 20:00.
Pushed by stikonas into branch 'master'."
1740737,2017-09-07 00:11:54 UTC,"Hello!
I've tried to create a .torrent with KTorrent but it seems impossible.
1. UI says ""File or directory to create torrent from"" but actually it allows adding only directories (folders)
2. Actually the only recognized folder is user's /home; When I reach to my prepared folder (for example /home/<username>/Desktop/<folder_name> it can ""see"" only /home/<username>/."
1740739,2018-01-03 09:09:26 UTC,"I think the best plan of attack would be to test against source port IDs (reg6) rather than IP addresses. This raises the problem that reg6 must always be set to the correct value. This is mostly correct, except for a few apps:"
1740739,2018-01-31 14:19:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/539546"
1740739,2018-02-05 12:22:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/540841"
1740739,2018-02-05 13:54:28 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/540855"
1740739,2018-02-07 05:19:05 UTC,"Reviewed:  https://review.openstack.org/540841
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=66a02d146218a0affca2dbf2d3da8f27f6000e2d
Submitter: Zuul
Branch:    master"
1740739,2018-02-14 14:51:49 UTC,"Reviewed:  https://review.openstack.org/540855
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=45b22a21b15831b1cec8193390e87717f8e161b0
Submitter: Zuul
Branch:    master"
1740739,2018-02-27 17:42:07 UTC,"Reviewed:  https://review.openstack.org/539546
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=e1a15a07e51bf6590591e4010d52dfa1bb8f8e9f
Submitter: Zuul
Branch:    master"
1740740,2018-01-01 12:49:21 UTC,"If truename* isn't idempotent (assuming no race condition with filesystem changes), then that's a bug in UIOP indeed — a bug that may or may not be due to an underlying bug in SBCL."
1740751,2018-04-13 08:33:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740751,2019-11-21 19:39:27 UTC,"In case it helps, I don't believe I've encountered this bug using Ubuntu 18.04. I only use LTS releases so I can't speak for any other versions."
1740756,2019-02-06 16:59:29 UTC,Patch attached.
1740756,2020-12-14 00:03:50 UTC,Applied https://sourceforge.net/p/sbcl/sbcl/ci/7991d1db3bcd549c04761fc1a81bbcafe8828595
1740767,2018-01-20 21:36:25 UTC,Probably same problem: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1743995
1740767,2018-01-22 09:59:10 UTC,The problem must have been related to one or more specific packages which were blocking the upgrade. I have removed a number of packages and the problem went away.
1740771,2018-01-01 18:29:43 UTC,also I have
1740771,2020-02-11 18:13:59 UTC,"On 2/11/20 11:16 AM, Imre Péntek wrote:

> as far as I can tell this bug is not present in 19.10 (fixed)
>


No, clearly never fixed and still an issue in 20.04."
1740771,2020-02-11 16:17:43 UTC,note to self: check my home ubuntu if I have any alias set for mpv
1740771,2018-01-02 11:03:04 UTC,Is it possible for you to test mpv 0.27?
1740771,2018-01-03 02:37:00 UTC,"It appears Imre is using a wayland session. And starting in Ubuntu 17.10, mpv uses pure Wayland by default. This means any X11 screensaver fix is probably irrelevant."
1740771,2018-01-03 08:23:23 UTC,"It looks like support was added as part of the wayland rewrite in 0.28:
https://github.com/mpv-player/mpv/commit/68f9ee7e0b3fdddfa42fa11a15d9ae84460d5e19"
1740771,2020-02-11 18:48:25 UTC,"nonetheless I do not experience the core issue (screensaver activating, and the unability to temporarily disable it while an mpv playback is running)"
1740771,2018-01-03 08:33:37 UTC,"That's the one, thanks. We'll need to wait for v0.28"
1740771,2018-01-08 06:22:55 UTC,"Upstream bug to track:
https://github.com/mpv-player/mpv/pull/4945"
1740771,2018-02-16 22:21:36 UTC,"As I mentioned elsewhere it's not solely a matter of mpv-0.28+, support for the protocol needs to be in mutter also.
A workaround for current wayland/mpv users is to start mpv with gnome-session-inhibit, i.e
gnome-session-inhibit mpv /path/to/file
(- at least in 0.28, may also work in 0.27"
1740771,2018-02-19 01:44:51 UTC,Yes. And for some reason I thought it was already in mutter. But I can't find it now. So mutter also needs fixing.
1740771,2018-02-24 00:50:44 UTC,"forgot to mention I did file a mutter bug though it wouldn't appear to be something forthcoming soon..
https://gitlab.gnome.org/GNOME/mutter/issues/20"
1740771,2018-05-23 05:53:50 UTC,"A fix for mutter/gnome-shell is now pending:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/111"
1740771,2020-02-11 18:20:32 UTC,"List of some mpv issues with gnome wayland, the window deco is somewhat mitigated by the new osc overlay that will, by default show in the absence of window deco.
https://github.com/mpv-player/mpv/wiki/FAQ#i-use-gnome-wayland-and-i-have-xyz-problem"
1740771,2020-07-24 19:15:21 UTC,This is still an issue in Focal in Wayland. Screen blanking occurs during video playback.
1740771,2020-02-11 16:16:40 UTC,as far as I can tell this bug is not present in 19.10 (fixed)
1740771,2018-08-22 02:59:04 UTC,mpv (0.29.0-1ubuntu1) cosmic; urgency=medium
1740772,2018-01-01 18:33:52 UTC,The attached patch should fix the problem.
1740772,2019-10-04 04:17:18 UTC,[Expired for rpl (Ubuntu) because there has been no activity for 60 days.]
1740772,2019-08-04 17:37:02 UTC,"Hi Finog,"
1740772,2018-01-01 20:21:48 UTC,"The attachment ""rpl.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1740774,2018-01-02 18:53:18 UTC,Yes is a last year commit.
1740774,2018-01-02 10:54:23 UTC,must have been fixed recently:
1740774,2018-01-02 10:36:42 UTC,backtrace attached:
1740774,2018-01-02 10:33:28 UTC,"reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06) if I specify the Ellipse Shape for the Bezier tool"
1740774,2018-01-01 19:30:53 UTC,thank you for taking the time to issue a report.
1740791,2018-01-01 21:52:31 UTC,PPA:
1740791,2018-04-13 15:18:02 UTC,I'll have a look at the problem this weekend.
1740791,2018-04-13 10:10:36 UTC,"I have problem with sstp-cliebt package installtion in ubuntu 18.04 .
sudo apt install sstp-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:"
1740791,2018-01-02 23:55:04 UTC,*** This is an automated message ***
1740791,2018-01-01 22:09:23 UTC,"The PPA
https://launchpad.net/~eivnaes/+archive/ubuntu/network-manager-sstp"
1740791,2018-01-01 21:50:54 UTC,"Packaging branch for this software is located here:
  bzr branch lp:sstp-client-package"
1740792,2019-01-24 04:59:44 UTC,"I agree with Wolf. To me login and unlock are the same (login is first unlock and unlock is any subsequent unlock), and I expect the setting to not ask for a password to apply in both cases."
1740792,2018-12-10 16:48:03 UTC,"Being a more or less ""normal"" user, I find this behaviour highly unexpected."
1740792,2018-03-03 10:29:21 UTC,Ubuntu 18.04 dev.
1740792,2018-01-18 22:29:34 UTC,"To a normal user I'm pretty sure that it would be a UX issue, even though technically it's different between login and unlock, UX wise it isnt. If a user reboots or suspends the computer they wouldn't expect it to behave differently, a lot of people don't even understand the difference between a system suspend and shutdown. Please reconsider the priority of this issue. Thanks!"
1740792,2018-01-18 15:23:33 UTC,"Thank you for your bug report, that's not really a bug or a new behaviour, automatic login is about login not about unlock. In any case not a control center issue"
1740792,2018-01-18 12:04:53 UTC,"I've got this issue as well.  Automatic login, no requirement for a password on the screen lock. When resuming from suspend, the password is required.  The user account used for this is not an administrator user.  Fresh install, no changes."
1740792,2018-01-18 11:52:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740793,2018-01-02 23:55:03 UTC,*** This is an automated message ***
1740793,2018-01-01 22:09:04 UTC,"The PPA:
https://launchpad.net/~eivnaes/+archive/ubuntu/network-manager-sstp"
1740793,2018-01-01 22:08:10 UTC,The debian package is in the branch of the project. I can move this to a separate repository if needed. Builds for Artful Aandverk and Bionic
1740810,2019-04-28 04:19:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740815,2018-01-11 02:08:52 UTC,The dead model still persists in mongo (as per #5) - there are no entries in db.cleanups and looking at the logs there is:
1740815,2018-01-04 06:33:10 UTC,"It's certainly not being ""removed quickly thereafter"" (i.e. it is still in the database today) - I suspect there's a secondary issue resulting in it not being cleaned up."
1740815,2018-01-04 06:05:50 UTC,"... and after re-reading your comment, maybe we're in violent agreement? I read ""query that is listing..."" as the client code. But perhaps you meant the mongo query?"
1740815,2018-01-04 06:03:21 UTC,"@thumper, I'm not convinced there's any value in showing it to the user in its Dead state. Once it's Dead, it should be removed quickly thereafter. If it's not, there's nothing a user can do with it, and its presence doesn't block anything else."
1740815,2018-01-04 03:02:55 UTC,We do disallow it except for this exact case.
1740815,2018-01-03 23:41:04 UTC,"Thanks for the debugging everyone. I agree, having two models with the same owner and name seems very wrong. I thought we disallowed that - I'll look into it."
1740815,2018-01-03 13:56:17 UTC,"The problem appears to be as follows - the models collection definitely contains two models that have the same controller, same owner and same name. One of these has a life of 2 (dead), whereas the other has a life of 0 (alive):"
1740815,2018-01-03 12:41:55 UTC,I just tripped over the same model on the production controller.
1740815,2018-01-03 04:38:01 UTC,"@axwalk: Trace logs for juju status on both models uploaded to https://private-fileshare.canonical.com/~paulgear/lp1740815/  The first one is called tracelog.txt.gz, the 2nd is tracelog-settings-not-found.txt.gz.  Please let us know if you want a separate bug about the 2nd symptom.  It feels like the same problem, though, because it's intermittent."
1740815,2018-01-03 04:29:34 UTC,"We have a 2nd model on the same controller exhibiting similar problems, but with a different message:"
1740815,2018-01-02 07:35:42 UTC,"As far as I can tell, the only way we would get that error message is if:"
1740815,2019-05-07 01:50:32 UTC,"Since the reporting of this bug more than a year ago, there were a few changes both in the model destruction (from 2.6 onwards) and checking of model names/UUID from (2.5)."
1740815,2018-01-04 06:43:43 UTC,"Using the Juju API, AllModels returns the dying model. DumpModels fails with a bogus error message when passed the dying model. And to retrieve the lifecycle state, you seem to need to call ModelInfo but this fails with a permission error when given the dying model. There seems to be a lot of code that doesn't cope with them correctly, so seems best to filter them out as soon as possible."
1740815,2019-07-06 04:17:29 UTC,[Expired for juju because there has been no activity for 60 days.]
1740817,2019-09-04 22:02:07 UTC,Testdrive was removed from Ubuntu
1740824,2018-01-03 17:18:56 UTC,"Ok, let describe why this is a bug and why it is essential."
1740824,2018-02-15 23:53:38 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1740824,2018-02-02 04:44:23 UTC,"Reviewed:  https://review.openstack.org/531481
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e2fdda2f6b5cf38d942618e3b5fc3e33564e407f
Submitter: Zuul
Branch:    stable/pike"
1740824,2018-01-26 00:43:37 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1740824,2018-01-05 19:29:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/531481"
1740824,2018-01-05 17:06:30 UTC,"Reviewed:  https://review.openstack.org/489951
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6f54f5c1e37a42b395ca793f869b73aa902602ed
Submitter: Zuul
Branch:    master"
1740827,2018-02-06 18:00:01 UTC,"Today same error with ""tar 1.29""  :-("
1740827,2018-01-19 16:42:23 UTC,Here we go:
1740827,2018-01-17 19:35:38 UTC,"Hi,"
1740827,2018-01-17 18:13:08 UTC,"Backup fails also with a
- new profile created
- other external drive
- other connection (USB3 instead of eSATA)"
1740827,2018-01-09 10:12:58 UTC,And something very strange happened:
1740827,2018-01-09 10:08:41 UTC,After a successfull run last week i got this error again
1740827,2021-02-22 20:44:40 UTC,The patch is very simple:
1740827,2018-01-30 17:45:38 UTC,If i downgrade tar to version 1.29 i get a warning but finished successfully!
1740840,2018-01-03 09:10:48 UTC,"Also, this is not happening every time. After enough re-runs none of the tests will fail and the whole suite will succeed. I am trying to use Bileto with a more debug-enabled package to try and identify the reason for why the mkfs.ext4 call actually fails."
1740840,2018-01-02 10:09:12 UTC,"A few things to consider: first, I still need to see how this test actually passes on xenial as we should have sudo issues there as well (can't remember here how it's working there)."
1740840,2018-01-03 14:52:53 UTC,"Ok, checked what's happening with mkfs on armhf. This is the error:"
1740840,2018-01-04 16:14:02 UTC,"In-between investigating this issue, I would like to actually check if the earlier ubuntu-image also suffered from the same problem (as we still had the test_save_resume there). This would give me some leads. Problem is: ADT infra is down, so I'll have to wait a bit for that to happen."
1740844,2018-04-05 13:51:54 UTC,"I've tried to apply that patches, but it didn't work.
I made a little change in isilon_api.py adding the following line in the initialization in order to define the parameter 'zone'. Without that i got error message stating that the object IsilonApi doesn't have the parameter 'zone':
def __init__(self, api_url, auth, verify_ssl_cert=True, zone='System'):
   self.host_url = api_url
   self.session = requests.session()
   self.session.auth = auth
   self.verify_ssl_cert = verify_ssl_cert
   self.zone = zone   <<<<<<<<<<<<<<<<<<<<<<<--------------- added line"
1740844,2018-04-05 14:13:31 UTC,"I forgot, I changed also isilon.py file at line 385 with the following in order to read from manila.conf file the zone name"
1740844,2018-04-09 07:41:37 UTC,"Hi, thanks for your help. We have this working ""hacked"" into ROSP10, but with an far older Version. Maybe we missed sth. during patch generation."
1740844,2019-03-22 15:01:21 UTC,Is this still issue still happening?
1740844,2019-05-01 16:25:19 UTC,Has anyone had the time to see if this is still occurring?
1740844,2019-05-01 16:41:42 UTC,"Helen, please route this one within EMC as appropriate.  Someone needs to make a call whether the issue is still valid and if so whether there are plans to fix it."
1740844,2019-05-01 16:44:51 UTC,"As far as I can see, the access zone is still not upstream. We worked around the issue and modified the following three files (until now we did not create new patches/pull requests)."
1740844,2019-05-02 10:26:00 UTC,Please assign to Shaun Edwards.  Thank you
1740844,2020-04-04 00:40:43 UTC,"Expiring this bug since there's been no fix proposed, and the driver seems to be unmaintained. Feel free to report another bug and reach out to the vendor in case they are interested in pushing a fix."
1740848,2018-05-15 17:27:08 UTC,I'll try to contact someone from Polish KDE team again
1740848,2018-01-02 10:34:10 UTC,Screenshot of the menu mentioned.
1740848,2018-01-03 15:29:12 UTC,As far as I know KDE do not translate system on Launchpad. However I tried to contact somebody who perhaps can help. I have no right to edit and correct a KDE translation.
1740848,2018-05-15 17:05:20 UTC,The problem is still present in Ubuntu 18.04
1740854,2018-01-15 14:56:08 UTC,We added s390x autopkgtest support in snapd 2.30 - so this should work now.
1740860,2018-01-02 12:35:35 UTC,Could you try:
1740860,2018-01-08 11:48:27 UTC,"Dear Nick Papior,"
1740860,2018-01-08 12:05:37 UTC,Thanks for your feedback.
1740860,2018-01-11 02:57:54 UTC,"Dear Nick Papior,"
1740860,2018-04-06 06:54:55 UTC,Could you try with the latest 4.0 commit:
1740863,2018-04-03 11:46:59 UTC,bug #1760795 could be the fd leak issue leading to this error
1740867,2018-01-03 13:05:50 UTC,"Reviewed:  https://review.openstack.org/530718
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=a644ed7a671d1556be0e9d71f1b2c9e1d8224f79
Submitter: Zuul
Branch:    master"
1740867,2018-01-22 11:23:34 UTC,"Not a bug, per se, so setting to Wishlist."
1740869,2018-07-28 09:20:52 UTC,"The same bug affects me on Ubuntu 18.04 LTS when debugging C++ applications using CLion. The fact that the popup can remain hidden in the background but it blocks mouse clicks against all applications (including the foreground ones) is a huge issue, and there is no known workaround for the problem. How do core devs use their own system for application development?"
1740869,2018-07-07 05:51:33 UTC,"To update my own workaround, I have switched to LXDE for now (installed lubuntu-desktop). It's pretty drastic, but it completely sidesteps mutter."
1740869,2018-06-28 19:41:36 UTC,"I'm getting the same problem debugging Unity Editor. It is unusable. As I start going through breakpoints in Rider, I have to continually switch back to the Unity editor window to say keep waiting. Is there really no other workaround than to recompile the window manager?!"
1740869,2018-06-14 14:45:56 UTC,"It appears that the dialog is system-wide modal. Is that really necessary? If so, it should also appear on top of *every* window stack in the system, not just the stack containing the offender."
1740869,2018-04-16 08:07:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740869,2018-06-07 07:46:02 UTC,"Hi
same problem here Ubuntu 18.04 QtCreator 4.6.1"
1740869,2018-04-16 08:13:12 UTC,"It also affects me when I'm debugging with QtCreator using Ubuntu 18.04, this is very annoying.
When the window appears, it is not possible to click anywhere except that window (also if it is in background), and it is not possible to disable or increase the timer for non responding applications, as pointed here: https://askubuntu.com/questions/412917/how-to-increase-waiting-time-for-non-responding-programs"
1740869,2020-04-23 20:07:30 UTC,I am very grateful to whoever fixed this. Thank you. Really appreciated. 👍
1740869,2018-06-07 08:10:40 UTC,"same problem here
ubuntu 18.04 qtcreator 4.6.1
it looks like it steals mouse clicks because keyboard shortcuts still work"
1740869,2019-06-12 02:22:55 UTC,Now tracking in bug 1832426 :(
1740869,2019-04-11 01:00:42 UTC,Upstream fix was released in 3.30.1
1740869,2019-06-06 09:33:24 UTC,This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.1
1740869,2018-08-15 08:32:23 UTC,Same issue. Ubuntu 18.04.1 + Visual Code while debugging OpenGL app. Please increase the priority.
1740869,2018-08-27 20:54:29 UTC,"Same case: 18.04 debugging Unity3D on VSCode. Really annoying, renders debugger almost useless. I suggest making at the very least PING_TIMEOUT_DELAY (as reported here: https://askubuntu.com/a/701991 ) user configurable through a text file, and preferably add the possibility of configuring it on a per-process name basis. We can't just be switching WM in order to debug. This is ridiculous."
1740869,2018-11-29 23:32:13 UTC,Still running into this. It's impossible to debug. Ubuntu 18.0.4.1 gdb debugging large application.
1740869,2019-02-14 13:20:57 UTC,Same issue. Ubuntu 18.04.1 + Visual Code while debugging OpenGL app. Please increase the priority.
1740869,2019-02-17 13:16:51 UTC,Same issue. Ubuntu 18.04.1 + Visual Code while debugging OpenGL app. Please increase the priority.
1740869,2019-03-13 09:35:37 UTC,"Same issue while debugging C++ application. Ubuntu 18.04.01 + gcc 8.2.0 + Qt creator 4.5.2.
Please increase the priority"
1740869,2019-03-13 10:02:02 UTC,Would be worth reporting upstream on gitlab.gnome.org if that hasn't been done yet
1740869,2019-03-19 14:36:43 UTC,"Marking as not fixing for release.  That doesn't mean this won't be fixed, just that we won't block release on waiting for it to get fixed.  This will be picked up in the 19.10 cycle for fixing."
1740869,2019-03-19 14:36:59 UTC,Added to Trello: https://trello.com/c/42jbJczE/286-bug1740869-something-is-not-responding-window-is-constantly-showing-when-debugging-a-program
1740869,2019-06-06 09:33:38 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1740869,2019-03-27 16:23:00 UTC,This has already been fixed both in Disco and Cosmic. The commit to be SRUed in Bionic is this one: https://gitlab.gnome.org/GNOME/gnome-shell/commit/b3045cb964459d050c280a4a4958131cfa24ebfb
1740869,2018-07-03 11:48:39 UTC,When working with Qt Creator 4.6.2 it happens too and it just makes debugging unusable.
1740869,2019-04-11 07:27:22 UTC,"Three commits got backported upstream to gnome-shell-3.28 related to the close dialog, but after the git snapshot that is being SRUed now to Bionic. The fix to this bug is there.
https://gitlab.gnome.org/GNOME/gnome-shell/commits/gnome-3-28"
1740869,2019-05-28 21:39:22 UTC,"Hello Vaclav, or anyone else affected,"
1740869,2019-06-01 02:33:45 UTC,"$ apt-cache policy gnome-shell
gnome-shell:
  Installato: 3.28.4-0ubuntu18.04.1
  Candidato:  3.28.4-0ubuntu18.04.1
  Tabella versione:
 *** 3.28.4-0ubuntu18.04.1 100"
1740869,2019-03-27 16:43:09 UTC,"Andrea, if you want to prepare a merge proposal against bionic we can merge it in the VCS for now and then when I prepare the new SRU for bionic with other fixes land it... As you wish"
1740874,2018-01-15 20:54:44 UTC,"Fixed it by usingsynaptic package manager to reinstall affected header. Confirmed repair by running sudo apt-get install linux-headers-generic, which no longer showed an error."
1740874,2018-01-15 20:38:08 UTC,I tried running the the suggested fix as follows:
1740874,2018-01-02 16:36:24 UTC,You may need to run the following from a terminal:
1740874,2018-01-02 14:00:05 UTC,This change was made by a bot.
1740879,2018-01-02 15:24:20 UTC,Thanks for reporting these doc issues.
1740879,2018-01-02 14:59:28 UTC,"I see that this is already fixed in the latest version of the docs:
https://docs.openstack.org/cliff/latest/user/sphinxext.html#preparation"
1740881,2018-01-04 19:36:50 UTC,"@kasper, this issue must be due to the conversion from a python string to a wxString because I can load your footprint with the kicad footprint viewer (see attached image).  Anyone else have any ideas why the python unicode string is not being properly converted to a wxString?"
1740881,2018-01-03 22:56:19 UTC,Or maybe clearer:
1740881,2018-01-03 19:55:51 UTC,"I thought python unicode strings had to be prepended with a u''.  At least that is what the documentation https://docs.python.org/2/howto/unicode.html would suggest.  As long as wxWidgets was built with unicode support, it should accept unicode strings directly.  If a wrapper has to written to support this, it could be a while before it's fix as we really do not have a python scripting developer."
1740881,2018-01-03 21:36:46 UTC,"Oh, indeed. Since I am not writing my paths manually, I can't prepend a u'' so my actual issue is with `os.walk` which seems return undecodable bytes."
1740881,2018-01-03 22:40:26 UTC,On second thought:
1740881,2018-01-04 22:21:56 UTC,"Yeah, it seems like the problem is restricted to the Python bindings"
1740881,2018-01-04 12:04:03 UTC,Thanks for re-opening. It also crashes on otherwise valid foorprint libraries if there is unicode in the path:
1740881,2018-01-03 23:30:18 UTC,I guess this could be an issue with the swig interface files for this function. I guess we can not reject it entirely.
1740881,2018-01-03 22:42:07 UTC,Last line should be:
1740882,2018-02-16 02:05:13 UTC,Added snapd so they can add testing so this doesn't break again (or implement split initrd)
1740882,2018-01-09 12:04:54 UTC,https://github.com/snapcore/snapcraft/pull/1839
1740882,2018-01-02 15:41:45 UTC,"And indeed, the attached patch fixes it - can i have any confirmation about this?"
1740887,2020-11-16 18:15:21 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1740887,2021-01-16 04:17:51 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1740887,2018-01-07 18:16:38 UTC,"I had to switch back to the following installer ""2016-03-03: New QEMU installers. Fixed, first version with support for Raspberry Pi 1 and 2."" for having a working version with the ""-M raspi"" option."
1740887,2018-01-07 17:25:15 UTC,I've got th exact same crash under Windows 10 64 bits with QEMU emulator version 2.10.95 (v2.11.0-rc5-11692-g50cdacc703-dirty)
1740889,2018-01-02 17:12:05 UTC,Thanks for filing.  Would you mind filing this report upstream though?  It's an upstream issue and should be debugged there: https://github.com/hughsie/fwupd/
1740889,2019-09-24 15:03:53 UTC,"Lots of people have used the logitech plugin now, and it's definitely functional.  Any other corner cases, please open new bugs, preferably upstream (https://github.com/fwupd/fwupd)."
1740889,2018-10-15 21:06:14 UTC,The Logitech plugin was re-written in fwupd 1.1.2.  can you please re-retry this again?
1740889,2018-04-16 13:47:01 UTC,A comment on the upstream bug indicates this is still a problem in Ubuntu 18.04 beta 2 which contains fwupd 1.0.6.
1740889,2018-02-26 15:58:22 UTC,"Per upstream bug, they would like this checked on the 1.x.x release or master.  Can you please try that?"
1740894,2019-03-05 13:26:14 UTC,I will try it out on bionic in a few hours
1740894,2019-03-06 16:37:54 UTC,I can confirm that xkb-data 2.23.1-1ubuntu1.18.04.1 fixes this issue for me on bionic.
1740894,2019-03-06 17:17:34 UTC,When can we expect a release of the proposed xkb-data?
1740894,2019-03-07 10:03:55 UTC,This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1.18.10.1
1740894,2019-03-07 10:04:01 UTC,"The verification of the Stable Release Update for xkeyboard-config has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1740894,2019-03-07 10:08:27 UTC,"Tagged bionic-failed, what sort of testing was done? Did we get the systemd change? Or is the regression described earlier in the discussion is still problematic?"
1740894,2019-03-07 20:29:49 UTC,Thank you for taking the time to verify this stable release fix.  We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE).  Please remove the verification-done tag and add one for the release you have tested the package in.  Thank you!
1740894,2019-04-10 22:01:48 UTC,Works on 18.10 x64 for me...
1740894,2019-04-13 11:29:31 UTC,"Confirm that it also works with Cosmic on the Asus ZenBook Flip UX561UD from my comment #1
xkb-data 2.23.1-1ubuntu1.18.10.1"
1740894,2019-09-02 04:53:39 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.26
1740894,2019-07-05 08:24:33 UTC,"Comment #38 has verified xkb-data 2.23.1-1ubuntu1.18.04.1 on bionic and it is the latest piece to fix this issue on bionic.
I also confirmed xkb-data 2.23.1-1ubuntu1.18.04.1 does fix this issue on bionic."
1740894,2019-07-05 08:35:25 UTC,"Please hold on the release of xkb-data 2.23.1-1ubuntu1.18.04.1 for bionic-updates.
There is some regression by a temporary workaround in OEM projects."
1740894,2019-07-24 03:59:09 UTC,"I checked Dell XPS 13 9370 with Ubuntu 18.04.2 and xkb-data 2.23.1-1ubuntu1.18.04.1.
It also needs to apply https://github.com/systemd/systemd/commit/8cc9fefe2e3e0b0d2c235e8b26abc82c4106c5f6 to systemd or the airplane mode will always be enabled when keeping pressing WiFi hotkey."
1740894,2019-07-24 14:07:14 UTC,@Shih-Yuan Lee: I added a systemd task and the rls-bb-incoming tag.
1740894,2019-07-31 09:32:02 UTC,I have made https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/370808 for bionic.
1740894,2019-08-23 00:18:09 UTC,"Hello Jeremy, or anyone else affected,"
1740894,2019-08-29 12:45:44 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.26) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1740894,2019-09-02 06:15:49 UTC,xkb-data 2.23.1-1ubuntu1.18.04.1 needs to be released with systemd 237-3ubuntu10.26 on bionic or it will cause the regression on most Dell laptops with WiFi hotkey.
1740894,2019-09-02 06:21:43 UTC,This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1.18.04.1
1740894,2019-06-12 21:32:56 UTC,Switched back to verification-failed-bionic since comment #42 has not been addressed.
1740894,2019-03-05 12:10:34 UTC,anyone willing to test it on bionic?
1740894,2019-02-09 22:10:49 UTC,I can confirm that xkb-data 2.23.1-1ubuntu1.18.10.1 fixes this issue for me on cosmic
1740894,2018-11-23 14:56:13 UTC,"@SRU team, undo the previous request, we are going to backport the required systemd changes"
1740894,2018-10-30 17:23:04 UTC,"A few weeks ago I submitted the similar Bug #1791367 for airplane mode key not working on Asus ZenBook Flip UX561UD. We did some tests updating xkb-data via ppa by Gunnar Hjalmarsson (gunnarhj). This update worked on the Asus, but broke the airplane mode key on Dell XPS 15 9575 2-in-1 where it had worked out-of-the-box with Cosmic and xkb-data 2.23."
1740894,2019-02-10 09:45:11 UTC,And I can confirm that it is fixed on Disco as well
1740894,2018-10-29 18:49:54 UTC,"Hello Jeremy, or anyone else affected,"
1740894,2018-10-29 18:48:38 UTC,"Hello Jeremy, or anyone else affected,"
1740894,2018-10-25 11:42:01 UTC,Change uploaded to bionic and cosmic
1740894,2018-10-24 14:53:05 UTC,That sounds great!
1740894,2018-10-30 20:34:09 UTC,"@Mario: Yeah, history seems to repeat itself."
1740894,2018-10-24 14:05:51 UTC,"It looks like we are missing that commit in xkeyboard-config
https://cgit.freedesktop.org/xkeyboard-config/commit/?id=39927132"
1740894,2018-10-24 11:02:55 UTC,Is that still an issue in bionic or cosmic? If so do you know what needs to be changed in gnome-settings-daemon?
1740894,2018-01-03 18:55:57 UTC,This bug was fixed in the package libxkbcommon - 0.8.0-1
1740894,2018-01-02 17:09:30 UTC,This may also be the cause of https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1722034
1740894,2018-01-02 17:06:10 UTC,"In artful and later, a number of kernel drivers send KEY_RFKILL - which is being ignored by the userspace handling code."
1740894,2018-01-02 17:05:05 UTC,"Attached is an alternative script which sends KEY_WLAN, which does trigger Airplane Mode, as expected."
1740894,2018-01-02 17:04:49 UTC,"Attached is a test script that should trigger Airplane Mode in GNOME, but does not. The code in gnome-settings-daemon looks for XF86RFKill, but the key is not identified as such."
1740894,2018-10-24 12:54:11 UTC,"Yes, this is still an issue. Please see the above scripts. I am not aware of why gnome-settings-daemon does not receive the keypress and trigger airplane mode, if those X11 packages are up to date."
1740894,2018-10-30 21:21:21 UTC,"@Gunnar: Sure, happy to sacrifice my airport key :)
New bug #1800727 for the XPS."
1740894,2018-11-09 14:23:47 UTC,"@Mario, could you copy the list of devices from ""sudo evemu-record"" and a log of the record from the keyboard after pressing the key once?"
1740894,2018-11-05 15:09:30 UTC,"@Mario, does disable/enabling airplane mode works if done from gnome-control-center (the wifi panel has the control)?"
1740894,2018-10-31 23:50:25 UTC,This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1.18.10.1
1740894,2018-11-06 18:05:35 UTC,"@Sebastien: That's the thing, on the Dell XPS 15 9575 there IS a regression with xkb-data 2.23.1-1ubuntu1.18.10.1."
1740894,2018-11-06 18:08:01 UTC,"To be clear, the above debugging output is with xkb-data 2.23.1-1ubuntu1.18.10.1 installed and therefore the DISabling of airplane mode by the dedicated key being broken"
1740894,2018-11-07 10:25:40 UTC,"Sorry but it's still a bit confusing to me so taking a step back
- on a stock XPS with the non-SRU version, what keycode do you get in xev
- on a stock cosmic what happens when you use the key
- does that command works to get out of airplane mode?"
1740894,2018-11-07 22:16:31 UTC,@Sebastian:
1740894,2018-11-07 22:47:44 UTC,As an additional check I once more installed the SRU version (and rebooted):
1740894,2018-11-09 12:37:29 UTC,"Ok, so after some debugging the fix is working but it hits a bug on some Dell laptops"
1740894,2018-11-09 16:00:00 UTC,"I believe the issue was originally created by that systemd change,
https://github.com/systemd/systemd/pull/8762"
1740894,2018-11-09 19:25:55 UTC,@Sebastien: Thank you very much. With the SRU version installed (I hope that's right):
1740894,2018-11-09 19:45:56 UTC,And your fix helps:
1740894,2018-11-13 18:53:31 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of xkeyboard-config from cosmic-proposed was performed and bug 1800727 was found.  Please investigate that bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed-cosmic"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1800727 (not this bug). Thanks!"
1740894,2018-11-21 09:41:44 UTC,"@SRU team, can you delete that SRU from proposed? it's a behaviour change and would need to at least land with systemd corresponding changes and that might still impact some configs, we better do those changes in disco and revisit later for bionic/cosmic if needed"
1740894,2018-11-23 14:28:56 UTC,"@SRU team, actually we will cherrypick more things into systemd, to make systemd & xkeyboard-config play nice with each other, as is destined to be upstream and in disco."
1740894,2018-11-05 23:12:43 UTC,@Sebastien:
1740894,2018-11-06 15:06:27 UTC,"Thanks for the data Mario, seems like it's not the backend then but that there is a bug in the key handling. Unsure we can describe it as ""regression"" though, the feature was not working at all, now it's half working.
Or was it something that is currently working on cosmic and which isn't now?"
1740896,2018-01-15 14:51:50 UTC,"Reviewed:  https://review.openstack.org/533529
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=798180361fb317ef478fa603a0bd310c1583b47b
Submitter: Zuul
Branch:    stable/pike"
1740896,2018-01-15 10:20:25 UTC,"Reviewed:  https://review.openstack.org/531690
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=2a60e56d412c07317fbf3b82de691574d8e7e77b
Submitter: Zuul
Branch:    master"
1740896,2018-01-15 08:00:14 UTC,"<<< Update: After removing the livenessProbe as suggested by ykarel on irc, the dashboard pod has stopped crashing
>>> This was just to check how kubectl apply behaves without liveliness."
1740896,2018-01-15 07:53:35 UTC,"Change abandoned by yatin (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/533346
Reason: Fixed here: https://review.openstack.org/#/c/533529/"
1740896,2018-01-15 07:42:15 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/533529"
1740896,2018-01-13 08:26:06 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/533346"
1740896,2018-01-11 13:54:13 UTC,The following output is from a devstack Pike deployment:
1740896,2018-01-08 07:36:28 UTC,"Update: After removing the livenessProbe as suggested by ykarel on irc, the dashboard pod has stopped crashing. This is how it looks now: http://paste.openstack.org/show/640751/"
1740898,2018-09-14 14:33:29 UTC,"Still occurs in 3.2 beta 1, even with new UPC search box."
1740900,2018-02-24 03:05:05 UTC,The problem is that phpmyadmin does not add mysql server packages when installing it without first having mysql server installed. I had assume that it would and the default configuration method assumes a localhost mysql server
1740900,2018-02-24 02:52:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1740928,2019-12-19 18:08:25 UTC,I don't think there is currently any formal interest in supporting fedora in full. We added some temporary support while we waited for CentOS8 but it's unlikely to be a 1:1
1740928,2018-10-25 19:15:52 UTC,"Reviewed:  https://review.openstack.org/606944
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=309524b75aa252f52f915b020fe5856a4f524c52
Submitter: Zuul
Branch:    master"
1740928,2018-10-03 11:02:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/607530"
1740928,2018-10-01 13:03:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/606944"
1740928,2018-10-01 12:51:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/606943"
1740928,2018-09-28 20:21:22 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.openstack.org/605642"
1740928,2018-09-28 20:21:16 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.openstack.org/605643"
1740928,2018-09-27 10:52:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605643"
1740928,2018-10-01 13:08:09 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/605643
Reason: Abandon in favour of Ifa18a4c70c59a4617ac80988af137770b246ad71 in order to avoid breaking builds."
1740928,2018-10-01 13:05:04 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/605642
Reason: Abandoned in favour of Ifa18a4c70c59a4617ac80988af137770b246ad71"
1740928,2018-09-27 10:52:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605642"
1740928,2018-01-12 16:02:33 UTC,OK... so to support Fedora we will use this bug as the RFE to add a job in RDO-Cloud that validates and runs CI on tq/tqe w/ baseos Fedora.
1740928,2018-01-05 01:53:57 UTC,"Per the suggestion of Sergii Golovatiuk, I had originally set the check to be"
1740928,2018-01-02 19:50:56 UTC,The primary README for the TripleO-Quickstart project even mentions Fedora:
1740928,2018-01-02 19:47:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/530793"
1740928,2018-10-03 10:47:17 UTC,"Reviewed:  https://review.openstack.org/606943
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=ee2885fcbe71fe3a7363b830d9ea1b2a01e67cf9
Submitter: Zuul
Branch:    master"
1740928,2018-05-09 11:10:34 UTC,"Change abandoned by Sagi Shnaidman (<email address hidden>) on branch: master
Review: https://review.openstack.org/530793
Reason: According to TripleO policy of patch abandonment https://github.com/openstack/tripleo-specs/blob/master/specs/policy/patch-abandomment.rst, this patch is abandoned. If you would like to continue to work on it, please ask for restoration either on #tripleo in Freenode IRC, or openstack dev mailing list - <email address hidden> with [TripleO] in subject. Thanks."
1740928,2018-10-10 14:48:05 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/607530
Reason: Closing because the same change is now contained into https://review.openstack.org/591540"
1740930,2018-01-03 05:33:01 UTC,This bug is fixed in 4.8.20.
1740935,2018-01-02 20:45:34 UTC,"The only thing in maas.log at this time is already included, are you looking for a different log file than /var/log/maas.log or do I need to enable more verbosity somehow?"
1740935,2018-04-13 13:22:17 UTC,Yes that was the process.
1740935,2019-09-19 14:53:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1740935,2019-01-24 10:00:41 UTC,"Problem appears to be resolved in MAAS 2.5.0 (7442-gdf68e30a5-0ubuntu1~18.04.1), installed via Launchpad (ppa:maas/next).  I'm successfully able to bootstrap and deploy a rabbitmq-server charm to my LXD-based MAAS.  (Using Bionic.)"
1740935,2019-01-23 14:50:20 UTC,Problem persists in MAAS 2.4.2 (7034-g2f5deb8b8-0ubuntu1).
1740935,2019-01-23 13:33:03 UTC,Apologies; I should have provided more detail.
1740935,2019-01-23 13:28:08 UTC,I'm also able to reproduce this.
1740935,2018-04-27 00:09:12 UTC,"I thought I had already stated this, but just in case.
This can be reproduced by installing MAAS in a LXD with https://github.com/chris-sanders/maas-lxd"
1740935,2018-04-27 00:01:40 UTC,/var/log as requested
1740935,2018-04-27 00:01:18 UTC,I've just rerun this operation.
1740935,2018-04-04 12:56:11 UTC,"Ok, so if I understand correctly:"
1740935,2018-03-21 13:35:06 UTC,"Yes, I've just relaunched the machine I previously tested this with and nothing has changed. I'm not sure why there would be an expectation that anything changed, MAAS still reports version: 2.3.0 (6434-gd354690-0ubuntu1~16.04.1). I'm now running juju 2.3.4 but as previously demonstrated the juju version doesn't appear to be relevant since this is a regression between MAAS 2.2.2 and 2.3.0."
1740935,2018-03-21 12:59:42 UTC,"Hi All,"
1740935,2018-01-02 21:20:14 UTC,I've just re-run this while watching all 3 of the maas log files.
1740935,2018-01-02 20:34:55 UTC,20:10:05 ERROR juju.cmd.juju.commands bootstrap.go:519 failed to bootstrap model: cannot start bootstrap instance: unexpected: ServerError: 400 BAD REQUEST (Failed to render preseed: 'NoneType' object has no attribute 'url')
1740937,2020-11-26 11:34:42 UTC,here's how we do that:
1740940,2018-01-03 13:28:29 UTC,"Before No valid host message there is failing request to Neutron:
Request to http://172.16.2.12:9696/v2.0/ports/3d9c5064-0e54-4213-826e-eab6f273c2ea.json timed out"
1740940,2018-10-12 16:41:56 UTC,This seems to be caused by RDO Cloud since a good number of hours by now. See https://logs.rdoproject.org/38/610038/3/openstack-check/tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-pike-branch/d5bd381/logs/undercloud//home/zuul/overcloud_deploy.log.txt.gz
1740940,2018-10-12 16:52:56 UTC,Recreated as https://bugs.launchpad.net/tripleo/+bug/1797600 to avoid confusion with older occurence.
1740940,2018-10-14 15:08:07 UTC,please review this bug w/ the CI team.
1740941,2018-02-17 08:14:04 UTC,"Hello
I have the exact same issue. That package used to work fine last year, I actually use it for self control purposes so as I am the only user on my desktop I apply it to my own profile. The problem I know have is that as of today i am unable to log back in. Is their a work around for me to get back control of my machine. I am on a critical deadline for a job interview, I have to deliver a case study and really need access back asap to finish this job. I would be very grateful if you could get back to me. I can open a terminal window, but I am still unable to log back in.
Thanks again for your help"
1740950,2020-05-11 16:03:57 UTC,Note: the Attachment API issue is being tracked by https://launchpad.net/bugs/1736773
1740950,2018-01-02 22:24:40 UTC,"I believe I've found the issue, and it's a regression in the 3.27 Cinder volume attachment_update API:"
1740950,2018-01-03 00:35:17 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1740950,2018-01-03 18:14:59 UTC,"@Jeremy - correct. It's not yet released (tagged). I reported as a private security bug before I realized the root cause, so I'm OK with making this public so we get visibility and a fix before Queens GA."
1740950,2018-01-04 15:16:13 UTC,"In that case, I'll triage it as a Class Y (""only found in development release"") report from the VMT's perspective. If it lingers past Queens release day, we can revisit the advisory task."
1740950,2018-03-01 11:33:32 UTC,"Discussed this at the Rocky PTG, agreed to add a policy rule to cinder to only show host_name if using an admin-scoped token. The cinder team needs to talk to the glance team about any impacts this might have on cinder-backed glance storage."
1740950,2019-11-14 20:38:58 UTC,Note that I can also call GET /v3/{project_id}/attachments/{attachment_id} on any volume attachment to my server as a non-admin and get the connection_info dict details about the host and volume backend that the volume is attached to.
1740950,2020-03-16 13:33:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/713231"
1740950,2020-05-11 08:23:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/726751"
1740950,2018-01-03 02:13:52 UTC,"Just to clarify, this is only affecting openstack/nova master after change 330285 merged? If so, and it gets fixed before Queens releases, the VMT wouldn't normally issue an advisory as no stable releases are impacted. In that case, it may also make sense to switch to a public workflow so the embargo process doesn't slow down design discussions and patch review."
1740950,2020-05-21 11:23:00 UTC,"Reviewed:  https://review.opendev.org/726751
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9d5c340130ac056e7558468cc61872db65140c9b
Submitter: Zuul
Branch:    master"
1740954,2018-01-02 22:56:43 UTC,"Hi,"
1740956,2020-08-04 09:24:25 UTC,"Closing as this bug report system is no longer used and there is not enough info to reproduce. If this is still an issue, please check the listed bugs here: https://inkscape.org/report"
1740967,2018-01-03 01:15:05 UTC,"Note that ""-u"" _is_ referenced in: https://help.ubuntu.com/community/ReportingBugs"
1740967,2018-01-03 03:28:41 UTC,"Someone suggested that -u is deprecated, which means this might be a documentation fix ..."
1740972,2018-01-03 02:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740972,2018-01-17 17:47:00 UTC,Please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740971/comments/3 for more info on this.
1740972,2018-01-23 13:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1740972,2018-02-02 09:03:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1740972,2018-02-12 08:47:33 UTC,This bug was fixed in the package linux-oem - 4.13.0-1020.21
1740972,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1740972,2018-03-19 10:58:11 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1740990,2018-01-03 11:07:59 UTC,"not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1740990,2018-01-04 11:02:15 UTC,From what I understand you're not experiencing a bug but the effects of Inkscape using the bottom left corner as origin in the UI whereas the SVG specification uses the top left corner as origin.
1740990,2020-09-21 12:36:10 UTC,Closing because INVALID: Duplicate issue.
1740990,2018-01-04 15:11:15 UTC,"Thank you very much for your feedback, as well as that by Eduard Braun.  I
was unaware of the transformation being added, that seems like an easy fix
on my end as i usually change the document properties at the outset of the
design and there usually is not anything on the file at the start.  Thank
you for taking the time to review my bug and to respond with a workaround.
Ian Anderson"
1740990,2018-01-04 11:21:38 UTC,"oops, did not respond soon enough, in any event this is a duplicate of previous issues."
1740990,2018-01-04 03:44:16 UTC,"You are correct, changing the page size does not change the object
location.  The issue relates to the origin referenced in the XML Editor.
To reproduce the issue follow these steps:
Open Inkscape.
*File > Document Properties*
Using the ""Custom Size"" option change the ""Height"" to a smaller number than
the default (my default is 297mm and I often need to work with something
around 200mm).  Enter a value smaller than the original value and press
enter, close the ""Document Properties"" window.
Create any rectangle using the ""Create Rectangles and Squares"" tool.
Open the XML Editor (Shift+Ctrl+X) or *Edit > XML Editor *
Select the rectangle and change the attribute ""y"" to 0 (Placing the objects
top left corner at the 0 mark on the canvas).  (References are made to the
top left hand corner for both the objects and canvas as I'm working with
SVG files, the rulers do not reflect this, a miner annoyance but not a
serious problem.  Still XY coordinates as used by the XML Editor always
reference the origin at the top left hand corner regardless of the rulers
used.)  To enable the change to the attribute press ""set"".
The object now moves up to the top of the previous page, outside the canvas
defined when we altered the document properties."
1740990,2018-01-04 11:16:45 UTC,"thanks for the detailed explanation.
behavior confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1740990,2018-01-04 11:07:15 UTC,In any case this can probably be marked as a duplicate of bug #996349...
1740999,2018-01-25 07:41:43 UTC,"Hi Oleksiy，my machine is Lenovo ThinkSystem SR650 7x06,and it has Lenovo SAS 530-8i RAID,it only provide drivers for Windows,Redhat,SuSe and ESXI.
I have installed Fuel 11.0 as master using Redhat driver and it works,but the slave nodes can't not install by PXE."
1740999,2018-01-11 14:19:33 UTC,"Hi fiscan, Can you provide more information?"
1741007,2018-02-23 18:37:06 UTC,Keystone v3 API does not support pagination. horizon needs to paginate in horizon side.
1741020,2019-03-11 20:49:01 UTC,Can you reproduce this is bionic?
1741020,2018-04-16 09:39:41 UTC,That's a known problem that was fixed upstream.  But I think it still affects the version in artful.
1741023,2018-07-24 16:54:11 UTC,"This seems to be valid.
Also noticed, this holds similar with ""openstack server create --security"" instead of --security-group parameter."
1741045,2020-05-13 21:40:33 UTC,"unsure, you are the one who reported an issue/request for change, do you think you request has been addressed or do you still think changing would be better?"
1741045,2020-05-12 15:57:29 UTC,"I had already changed the resample-method to soxr-mq, and am satisfied with the result. I don't know how to judge which is better, auto or soxr-mq?"
1741045,2020-05-11 14:04:42 UTC,Upstream bug comment
1741045,2018-07-30 10:16:36 UTC,-- GitLab Migration Automatic Message --
1741045,2018-05-02 01:30:56 UTC,That seems to show speex-float-1 performing quite well: https://imgur.com/a/jtIEj
1741045,2018-05-01 12:58:35 UTC,http://comments.gmane.org/gmane.comp.audio.pulseaudio.general/21051
1741045,2018-01-04 07:49:20 UTC,"I suggest changing the default resample-method to speex-float-10, instead of speex-float-1, which is the current default now, in /etc/pulse/daemon.conf."
1741045,2018-01-04 02:12:36 UTC,"It appears the default of speex-float-1 is chosen by upstream (?... although commented out):
https://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/daemon/daemon.conf.in"
1741045,2020-05-31 16:45:14 UTC,"I changed the resample-method to soxr-hq, and I'll be testing it for some time. According to the manpage of pulse-daemon.conf ""the Soxr resamplers generally offer better quality at less CPU compared to other resamplers, such  as  speex"". So far I think it gives better sound quality than speex-float-1 and auto."
1741045,2020-05-12 12:31:18 UTC,"Well, how are you supposed to know, which resample method is actually used?"
1741046,2018-02-27 16:17:46 UTC,Received the same error when upgrading from Linux Mint 18.2 to 18.3.
1741046,2018-02-27 16:16:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741047,2020-05-14 17:16:50 UTC,GNOME Software now supports uninstalling of unused dependencies on both Bionic and Focal.
1741047,2018-01-04 00:52:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741047,2018-01-25 15:11:10 UTC,"Thanks for your report. Unfortunately there is no way for gnome-software to know what a third party installer installed, and it's the responsibility of the installer to remove what it installed on the system.
I'm closing gnome-software task. Your request is still valid though for the steam installer."
1741052,2018-02-15 10:40:00 UTC,https://review.openstack.org/#/c/523879/
1741057,2018-03-09 09:32:59 UTC,Hi Vince.
1741057,2018-03-08 20:14:43 UTC,"Hi Manfred,"
1741057,2018-01-15 19:03:37 UTC,"Possibly, I'll add it as feature request.
RTF is indirectly supported, if you edit the 'conf' file of the personal commentary module."
1741057,2018-01-15 18:18:07 UTC,"Ok, excellent, the issue I was seeing is resolved in this build."
1741057,2018-01-15 17:59:52 UTC,Hi Vince.
1741057,2018-01-15 17:46:37 UTC,"Hi Manfred,"
1741057,2018-01-15 17:08:49 UTC,"Hi Vince.
I'm not certain which version you are using.
In any case, development has moved to GitHub: https://github.com/mdbergmann/Eloquent"
1741060,2018-07-13 15:32:54 UTC,"openjdk-9 has vanished from later releases, so this is never likely to be fixed. openjdk-11 seems to install correctly though I haven't tested it thoroughly."
1741060,2018-01-12 15:50:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741060,2018-07-14 00:32:14 UTC,The Artful package doesn't suffer from this issue.
1741060,2018-07-13 14:48:38 UTC,Similar: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1770646
1741062,2018-02-15 10:39:27 UTC,https://review.openstack.org/#/c/526101/
1741074,2020-05-05 14:27:06 UTC,"@anonymouse67: see comments #2, #5, #6 and #7 in this bug."
1741074,2020-10-27 10:27:07 UTC,"One suggestion discussed in https://forum.snapcraft.io/t/allow-classic-confinement-for-postman-agent/19228 is to use a content interface to allow third-party snaps to write to ~/snap/chromium/common/chromium/NativeMessagingHosts/. Whether it’s a good idea from a security perspective is open for discussion, and it wouldn't solve all the problems discussed here, but it could be part of the solution to enable third-party native host connectors."
1741074,2020-06-15 09:01:27 UTC,"Download firefox from its website, just run it from it's unzipped directory"
1741074,2020-06-15 08:50:12 UTC,Any changes on this bug (since 2018)? Maybe at least workaround?
1741074,2020-05-21 09:26:14 UTC,"Nope, never mind gnome-tweaks. Removed Chromium snap and installed Google Chrome. Problem goes away."
1741074,2020-05-21 08:22:43 UTC,"Harrumph: not impressed. Was working fine this morning, then an update landed me with the snap version."
1741074,2020-05-07 12:44:23 UTC,"This ""connector"" issue is also presents on firefox snap v77.0b2 (64-bit) Ubuntu 20.04 and has not addressed yet."
1741074,2020-05-04 16:15:25 UTC,"@osomon, could you point me to an existing forum post or start a new one summarizing what accesses would be necessary to manage gnome shell extensions? I couldn't find one searching, but if there's not one we should open one to try and discuss with snapd architects. Thanks"
1741074,2021-02-24 09:59:31 UTC,"Hi team, is there any news about this 3y old bug? It would be nice to know if it is something that will be worked on or not even if the timeline indicates towards not."
1741074,2020-03-29 10:35:48 UTC,This also affects the browserpass extension for the pass (passwordstore.org) password manager
1741074,2020-04-09 21:35:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741074,2019-11-13 01:24:04 UTC,Chromium is now incapable of managing extensions for Ubuntu's primary desktop environment? This issue is tolerable only because Google Chrome is not affected. Is Google somehow behind this apparent reluctance to remedy the problem?
1741074,2019-11-05 21:56:22 UTC,This bug is still present in Kubuntu 19.10. Poor Chromium...
1741074,2019-10-26 12:43:48 UTC,"zebul666, please take time to read:"
1741074,2019-10-26 11:55:48 UTC,How and why that snap has been rolled out in 19.10 while we have less feature with it ?
1741074,2019-10-07 13:36:31 UTC,"Unlikely. There are a number of higher priority issues with the chromium snap that we're focusing on now, and the plan to transition from the deb to the snap in 19.10 still holds."
1741074,2019-11-25 14:03:54 UTC,It's been reported that the GooPG extension doesn't work because it uses native messaging (https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179/207).
1741074,2019-09-16 18:20:24 UTC,This is really frustrating and 19.10 is coming up fast which I understand will switch everyone over to snap based chromium making extensions.gnome.org unusable for everyone. Any chance of switching back to non-snap based chromium if this issue isn't resolved before then?
1741074,2019-07-04 15:22:48 UTC,"Also, the connector talks to the org.gnome.Shell.Extensions D-Bus API, for which there doesn't exist a snapd interface, so one would need to be written, and I'm pretty sure it wouldn't qualify for auto-connection given the level of privilege it would expose (listing installed extensions, install and uninstall extensions)."
1741074,2019-05-07 20:47:10 UTC,I've toyed with an unpacked example extension that talks to a native host connector (a simple python script that listens to messages and echoes all it receives).
1741074,2019-05-07 20:51:58 UTC,"chrome-gnome-shell wouldn't work like that unmodified, because the connector has external dependencies (it's a python3 script that imports GLib and Gio)."
1741074,2018-08-10 15:31:26 UTC,Similar report for the Plasma/Browser Integration (https://community.kde.org/Plasma/Browser_Integration): https://forum.snapcraft.io/t/call-for-testing-chromium-62-0-3202-62/2569/65.
1741074,2018-01-03 15:55:54 UTC,stracing the snap reveals that /usr/bin/chrome-gnome-shell cannot be found in the context of the snap:
1741074,2019-11-25 14:04:55 UTC,"And from duplicate bug #1853835, the KeePassXC-Browser extension (https://chrome.google.com/webstore/detail/keepassxc-browser/oboonakemofpalcgghocfoadofidjkkk) doesn't work for the same reason: https://github.com/keepassxreboot/keepassxc-browser/issues/405."
1741074,2020-01-06 23:39:42 UTC,2020-01-06 : https://forum.ubuntu-fr.org/viewtopic.php?pid=22202596#p22202596
1741074,2020-01-23 00:59:58 UTC,"KDE Connect is also affected by this. I'm wondering though, unable to find the answer online, why was the transition to snap-based chromium made?"
1741074,2020-01-23 07:07:50 UTC,"(I think) It makes development easier, you don't have to build it for every Ubuntu version in support, or any Linux OS, it contains specific libraries you know won't cause issues with the app."
1741074,2020-02-20 21:30:36 UTC,"I want to add this affects Firefox + the KeepassXC extension too. I agree that NativeMessaging is kind of a crutch, but if there is no way to make this work safely a snap interface needs to be implemented that applications from inside / outside of snap can use. There is demand for this kind of interface, so maybe devising a ""correct"" way of doing this and communicating it to the application / plugin developers would be a good thing...
At the moment I work around by installing firefox from repo and ignore the issue, but some day this might not work anymore. I'm kind of worried that I upgrade to Ubuntu 20.04 and Firefox is not available from repo anymore :/"
1741074,2020-02-29 07:38:36 UTC,Hi! Any update on this please? This is an extremely frustrating issue that makes me consider switching from Ubuntu to something else.
1741074,2020-03-14 14:20:28 UTC,This is still an issue on 20.04
1741074,2019-03-19 18:13:37 UTC,"Is there any news about this bug?
To this day I still can't use plasma-browser-integration"
1741079,2019-01-16 00:16:08 UTC,"Hi there, I recently ran into a similar issue when using Queens Senlin/Neutron/Designate. The DNS record cannot be cleaned in Senlin node deletion since Neutron tries to search the record with admin context. After some days of debugging, here is what I found and hopefully can help you guys and bring up a discussion about what should be the right fix:"
1741079,2019-01-16 21:42:13 UTC,Thanks @Miguel A Nova bug is filed here: https://bugs.launchpad.net/nova/+bug/1812110 and I'll try to make a patch.
1741079,2019-01-16 18:36:14 UTC,"The issue was really introduced by this change https://review.openstack.org/#/c/308389/, which was intended to fix https://bugs.launchpad.net/neutron/+bug/1572593. Problem is that the fix is only a partial fix for the bug and it's a consequence of using four different OpenStack projects (Neutron, Nova, Designate and orchestration like Heat or Senlin) in the creation and deletion of the VM and its port:"
1741079,2018-04-30 14:16:19 UTC,More debugging:
1741079,2018-04-23 18:21:56 UTC,In addition to 3rd Miguel question:
1741079,2018-04-27 15:06:56 UTC,"O.k., I added a statement logging the context of the ""list_zones"" call to designate-api. When I just create the port (with DNS attrs) and delete it again directly, the recordsets are properly created and deleted again at the same time. The call to ""list_zones"" uses the ""demo"" user with whom all CLI commands are executed."
1741079,2018-04-25 09:54:34 UTC,Just noticed that there is an error in the Neutron server log for the deletion event. It looks like Neutron is using the wrong auth context for the deletion:
1741079,2018-04-25 09:46:18 UTC,"O.k., I can reproduce this without Heat, simply by doing:"
1741079,2018-04-24 19:58:12 UTC,I went through https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.html#use-case-3-ports-are-published-directly-in-the-external-dns-service
1741079,2018-04-24 14:23:22 UTC,"Dr. Jens Harbott,
1. No, we follow use case #3 -  ""Ports are published directly in the external DNS service""."
1741079,2018-04-23 13:35:18 UTC,Some more questions:
1741079,2018-03-17 04:17:23 UTC,[Expired for neutron because there has been no activity for 60 days.]
1741079,2018-01-15 14:23:11 UTC,"Hi Miguel,"
1741079,2018-01-09 01:22:35 UTC,We need more information as Miguel commented.
1741079,2018-01-05 17:10:19 UTC,"Hi Mark,"
1741079,2018-01-04 12:45:38 UTC,"Hi,
Thank you for your quick reply."
1741079,2018-01-03 17:31:20 UTC,"Just to be clear on the situation, let's clarify something. Port data is being sent by Neutron to Designate, correct? If that is the case, we are talking about external dns integration."
1741079,2018-04-25 10:11:05 UTC,"1. Yes devstack stable/ocata as well as master now.
2. vxlan, after devstack created network ""private"" with ID 42, edit /etc/neutron/plugins/ml2/ml2_conf.ini with vxlan_range = 100:1000 to make sure that 42 matches criteria for use case 3.
3. IPs are auto assigned from the subnets, see output below.
4. Sure:"
1741079,2018-04-25 09:55:42 UTC,Thank you for you your update.
1741079,2018-04-30 13:14:34 UTC,"One more thing to note: The error in q-svc happens during instance deletion. There seems to be no action towards designate happening when the port is deleted after that, in contrast to what happens when the port is deleted without having been attached to an instance."
1741079,2018-04-27 14:23:37 UTC,"Thank you for your reply, please try to filter Designate logs by two req's:"
1741079,2018-04-27 14:05:40 UTC,"The designate logs in master don't have useful information, they only show the request finding 0 zones."
1741079,2018-04-25 12:02:15 UTC,Thank you for your update.
1741080,2018-01-03 16:30:06 UTC,This change was made by a bot.
1741083,2018-01-03 17:07:59 UTC,"The test case would be something like:
a defsystem-depends-on b.
b is modified.
b is loaded and now up-to-date (in the same image, without loading a).
Next time a is loaded, a.asd should be re-loaded because b was modified, but isn't."
1741094,2019-11-01 20:50:50 UTC,Compilation and smoke testing of the *.py scripts is now in place.
1741095,2018-01-22 08:38:54 UTC,Experienced the same problem when installing wine.
1741095,2018-01-22 08:39:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741100,2018-01-03 22:27:25 UTC,"I'm a bit confused here, bandit doesn't require hacking to run, it should only be used for testing via testenv.  Also Bandit follows other OpenStack projects in terms of setting limits for the requirements, and hacking seems to be in line with both keystone[0] and nova[1].  I'm not sure what the reasoning is for the current cap at below 0.14.0 but I can look into it."
1741100,2019-01-27 13:51:46 UTC,"Update: upstream issue is fixed, bandit on pypi is at 1.5.1. Could we bump and clean?"
1741100,2018-01-03 18:43:01 UTC,This is the only package requiring old version of dev-python/hacking. Please look into the possibility of making it work with newer versions.
1741100,2018-02-15 07:01:28 UTC,Fixed with https://review.openstack.org/#/c/533071/
1741100,2019-01-28 05:10:56 UTC,"should be good now, had to update 90 or so packages though."
1741100,2018-01-03 18:44:59 UTC,...which in turn requires ancient dev-python/flake8.
1741105,2018-01-04 09:35:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741105,2018-01-07 02:49:32 UTC,"For what it's worth, and I'm not sure if this is related...  But I believe this package is failing to install because the efi partition it is looking for may not be found if secure boot is disabled?
I have secure boot disabled on this laptop, which is required for proprietary nVidia drivers."
1741105,2018-01-04 15:55:06 UTC,"there was a problem while installing this package on my Desktop
AMD FX(tm)-8150 Eight-Core Processor × 8
AMD BARTS (DRM 2.49.0 / 4.10.0-42-generic, LLVM 5.0.0)
64bit
DistroRelease: Ubuntu 16.04.5"
1741107,2019-10-21 08:58:54 UTC,"I have a similar set up and issue.
I've plugged in my headphones and the ""dongle"" into my headhpone and mic jacks on my sound blaster Z.
No sound when I first install Kubuntu.  I default to using headphones."
1741108,2020-04-23 13:49:44 UTC,I fixed that in all occurrences I could find in the 20.04 server guide. Should be published automatically.
1741108,2018-01-13 18:38:04 UTC,The only issue is that it is documented with the wrong case.  This would only cause an issue if someone would be adapting this guide to use a tool other than ldapmodify to make the changes.  I'm sorry if this seems excessively pedantic.
1741108,2018-01-05 16:12:57 UTC,"So, is there a problem with the Ubuntu Serverguide or not?"
1741108,2018-01-05 14:55:54 UTC,"That is what I was referring to, sorry that """" wasn't very clear. ;)"
1741108,2018-01-04 12:18:02 UTC,"http://www.openldap.org/doc/admin24/guide.html#olcSyncrepl indeed uses olcSyncrepl (lower-case r), but examples further down (http://www.openldap.org/doc/admin24/guide.html#N-Way Multi-Master) use olcSyncRepl :)"
1741111,2019-09-06 09:44:34 UTC,"@Jeff
I understand that you suggest that 'silent' type should produce only the return code (and reports on the filesystem if any)."
1741111,2019-09-06 09:47:12 UTC,'silent' in Checkbox means no urwid interactive screen. More like 'no interaction' than 'no output'. I guess it's better to introduce a new value that will introduce truly silent run; too many launchers are already configured to run as 'silent'.
1741114,2018-01-04 00:51:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741114,2020-03-18 02:52:40 UTC,This looks fixed to me... Do you reproduce still?
1741114,2020-05-22 04:17:48 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1741128,2018-06-27 08:03:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741128,2018-11-02 15:23:57 UTC,"This bug was fixed upstream almost a year ago. It would be nice to see this addressed in Ubuntu 16.04 LTS, which is still on libmagic1 version 5.25."
1741131,2018-01-03 22:29:19 UTC,"The python plugin refers always to self.sourcedir. It should instead refer to self.builddir, which the base plugin updates to point to source-subdir if present."
1741131,2018-01-05 02:33:00 UTC,This affects the sawtooth snap: https://github.com/elopio/sawtooth-core/blob/snapcraft/snap/snapcraft.yaml
1741133,2018-03-30 22:02:33 UTC,"This definitely happens to me too, for as far back as I can remember. It still happens in version 0.92.3."
1741133,2020-05-04 14:39:27 UTC,Closing as part of the bug migration of issues to GitLab
1741147,2018-02-16 22:44:23 UTC,"I also remember that Samsung app, though I barely used it, and I can't remember how reliable it was."
1741147,2018-01-04 05:10:13 UTC,Cool idea! Uwe and I discussed the possibility of doing a collaborative GSOC project with MusicBrainz with one of the MetaBrainz developers at the GSOC Mentor Summit. I think this project would fit that idea really well. :)
1741147,2018-01-04 15:30:34 UTC,"YES! The dynamic organization of a library based on metadata is much more powerful than statically dropping tracks into just crates and playlists. Sharing, exchanging, and enriching this metadata with others and from different sources provides so many chances for exploring and discovering unknown possibilities."
1741147,2018-01-05 01:35:04 UTC,Awesome. Musicbrainz already has the capacity for some relationships between different entities. Definitely the covered by/cover of is there.
1741147,2018-01-05 07:17:17 UTC,I would love to have something like this as well. Can this also be a data base for our long dream to have a track suggestion feature?
1741147,2018-01-06 07:26:42 UTC,Possibly related: ListenBrainz scrobbling Bug #669273
1741147,2018-02-16 10:52:51 UTC,http://www.rcharlie.net/sentify/
1741147,2018-01-07 07:24:10 UTC,"Musicbrains also has a ""collections"" feature, which would I guess be equivalent to playlists, except that it doesn't have an order. Might be a worthwhile feature request to musicbrainz to have playlists/orderable collections though."
1741147,2018-02-16 10:22:31 UTC,"Collections are equivalent to crates, since as you said they are unordered."
1741147,2018-03-06 21:26:22 UTC,"Ah, the private crates could be stored as private collections on musicbrainz, which would make a lot of sense."
1741147,2018-03-06 21:22:18 UTC,"On further thought, I think this would need to be enabled on a white-list basis for crates (or crate trees, when the nested crates feature is implemented. I have a bunch of utility crates that allow be to group tracks in a way that is not useful for a global database (like ""tracks for <friend>"", or ""broken files"", or ""recommended by <blah>""). These would need to be excluded. With nested crates, it would make sense to have the ability to include all crates in a tree (e.g. grenre:* or mood:*)."
1741147,2018-02-01 01:26:28 UTC,Added a playlist request to musicbrainz: https://tickets.metabrainz.org/browse/AB-329
1741161,2018-01-11 01:12:51 UTC,"At first, I think changing into _find_instance makes sense, but what if someone want to delete the databases inside a cluster? Can we add some logics like when users want to delete the database inside a cluster, just raise OperationNotSupported exception? Just some quick thoughts here."
1741161,2018-01-11 08:22:59 UTC,"This question needs to be divided into two stages, and I now have only the experience of mongodb and mariadb galera, which are two different forms of clustering.
mariadb galera can perform database and user operations on any node in the cluster, but mongodb can only be performed on mongos nodes.
1. Into _find_instance not a wrong amendment, but the feeling is not perfect, can be used to transition.
2. We can enhance this functionality by parsing the datastore of the cluster when it is determined that the cluster is passing in and then looking for a suitable database schema for each of these operations but this requires having all kinds of clusters supported by trove experience of"
1741164,2018-01-05 00:35:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741166,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1741166,2018-03-19 10:58:13 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1741166,2018-02-22 15:48:03 UTC,This bug was fixed in the package linux - 4.15.0-10.11
1741166,2018-02-12 08:47:33 UTC,This bug was fixed in the package linux-oem - 4.13.0-1020.21
1741166,2018-02-02 09:03:00 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1741167,2018-01-04 04:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1741167,2018-01-04 15:27:16 UTC,"Can you see if the 4.15-rc6 kernel has the same issue:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc6"
1741167,2018-01-05 08:56:25 UTC,"Yes, mainline kernel 4.15-rc6 kernel has the same issue for arch i386: Fails to boot."
1741170,2018-01-04 04:58:08 UTC,"I do not know if this is relevant, but there a kernel message which seems suspicious to me:"
1741170,2018-01-05 09:01:46 UTC,"Function get_unused_callno issues ""Out of call numbers""
And Function __find_callno issues ""No more space"" if the former fails
So this is no usual out of (disk) space or such."
1741170,2018-01-05 09:24:08 UTC,"I'm really no asterisk expert but there are two cases:
a) you are really out of numbers (not a bug, just as it is)
b) asterisk thinks you are out of numbers due to a bug e.g. not freeing unused correctly"
1741170,2018-01-05 09:24:15 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1741172,2018-01-09 17:31:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741185,2018-01-04 06:54:21 UTC,"To solve this problem, please install qemu-kvm-ev before install openstack-nova-compute"
1741190,2019-11-28 04:31:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741206,2018-01-04 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1741206,2018-02-02 09:02:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1741206,2018-02-12 08:47:33 UTC,This bug was fixed in the package linux-oem - 4.13.0-1020.21
1741207,2018-01-04 09:46:13 UTC,"Hi Adler,
I lack an env to repro but looking through search engines I think you want to check what the guest has in:"
1741207,2018-01-05 13:46:54 UTC,excec bit is set.
1741207,2018-01-08 07:47:55 UTC,"Odd, even the poweron-vm that fails on boot works in this retest."
1741207,2018-01-10 16:43:31 UTC,I added
1741207,2018-01-11 06:27:36 UTC,"maybe tmp is cleaned afterwards?
I didn't check yet when vmware is calling these."
1741207,2018-03-14 14:13:55 UTC,I tried a bit with this script but I never got any Data into the Log File.
1741207,2018-06-26 11:42:38 UTC,"Glad that you have no issue anymore, even thou we don't really know what the reason was :-/"
1741214,2018-01-08 08:31:14 UTC,"Ah, I overlooked raw option! Sorry, you're right of course."
1741214,2018-01-07 07:19:39 UTC,"Thanks for the patch, I think you should remove the if 'JPEG' condition, it's also required for raw scans."
1741214,2018-01-11 12:34:26 UTC,"Hi,
We tried to reproduce the reported issue in lab and it is reproducible. We will discuss this with HP program management team for incorporating this fix in the next release and keep you posted on the updates.
Thanks,
Nishitha"
1741214,2018-08-28 10:12:20 UTC,"The change was taken over upstream in an improved form (or reinvented), hence this issue can be closed now..."
1741230,2018-02-08 18:17:15 UTC,"Reviewed:  https://review.openstack.org/532504
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=50d8a07b3fa2fd8ee605691ee4f6148dd3a18a5f
Submitter: Zuul
Branch:    stable/pike"
1741230,2018-01-26 00:43:35 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1741230,2018-01-10 11:42:25 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/532504"
1741230,2018-01-09 21:23:48 UTC,"Reviewed:  https://review.openstack.org/530965
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8bc7b950b7c0a3c80cdd120fe4df97c14848c344
Submitter: Zuul
Branch:    master"
1741230,2018-01-04 15:30:37 UTC,With cpu_mode = custom + cpu_model = cortex-a53 (lowest nominator in AArch64) Nova errors out.
1741230,2018-01-04 15:08:51 UTC,https://bugzilla.redhat.com/show_bug.cgi?id=1430987 also has interesting information on this issue.
1741230,2018-01-04 14:38:37 UTC,Reported at libvirt upstream: https://bugzilla.redhat.com/show_bug.cgi?id=1531076
1741230,2018-01-04 11:11:07 UTC,https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1673467 has long description of issue
1741230,2018-01-04 10:34:26 UTC,snippet from nova-compute.log
1741230,2018-02-15 23:53:37 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1741240,2018-01-10 19:02:34 UTC,"I have nothing against it, but the configuration of NTP requires magic in new places (at least for the NetworkManager backend, since NM doesn't do NTP by itself). For the networkd backend this is relatively straightforward."
1741254,2019-05-24 13:21:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741255,2018-02-20 20:29:42 UTC,"I tried 17.10.1-server-amd64 today and the problem still there.
I'm not able to select / change the keyboard during the installation!
Which results in the wrong keyboard been set!"
1741277,2018-01-04 15:28:25 UTC,"15:25 <rbasak> I suppose the real intention of my bug is ""not all platforms running cloud-init make the system hostname resolveable by default""
15:26 <rbasak> I'd consider it resolved as soon as that is true."
1741277,2018-04-24 20:31:56 UTC,"On Tue, Apr 24, 2018 at 05:50:13PM -0000, Jeremy Bicha wrote:

> > The only case where nss-myhostname actually makes sense is if you have
> a read-only /etc, which is not true here.
"
1741277,2018-04-24 17:50:13 UTC,"> The only case where nss-myhostname actually makes sense is if you have a read-only /etc, which is not true here.
"
1741277,2018-01-04 18:00:47 UTC,"> We could have lxd always ensure the entry in /etc/hosts. That won't
conflict with cloud-init, and will resolve my problem.
"
1741277,2018-01-04 18:00:19 UTC,"I agree with Robie, yes we can fix lxd to modify file contents in the guest more than it already does.  But that is quite hacky.  It would be equivalent to having cloud-init set manage_etc_hosts to localhost on lxd."
1741277,2018-01-04 17:57:32 UTC,"On Thu, Jan 04, 2018 at 05:41:40PM -0000, Robie Basak wrote:

> On Thu, Jan 04, 2018 at 05:25:54PM -0000, Steve Langasek wrote:
> > AIUI lxd is setting /etc/hostname, but is not adding the Ubuntu-standard
> > entry (127.0.1.1 hostname.domain hostname) to /etc/hosts; so that should
> > be fixed in lxd.
"
1741277,2018-01-04 17:41:40 UTC,"On Thu, Jan 04, 2018 at 05:25:54PM -0000, Steve Langasek wrote:

> AIUI lxd is setting /etc/hostname, but is not adding the Ubuntu-standard
> entry (127.0.1.1 hostname.domain hostname) to /etc/hosts; so that should
> be fixed in lxd.
"
1741277,2018-01-04 17:25:54 UTC,"We have repeatedly rejected nss-myhostname as a solution in Ubuntu; it adds additional runtime complexity for an issue that had been serviceably addressed by configuring /etc/hosts in tandem with /etc/hostname.  The only case where nss-myhostname actually makes sense is if you have a read-only /etc, which is not true here."
1741277,2018-01-04 15:54:11 UTC,marked as cloud-images as that is where the change for nss-myhostname would be made (i think).
1741277,2018-01-04 15:29:52 UTC,"Scott pointed out that on a ""proper"" cloud, the hostname is resolveable by DNS because that's the name given to the instance by the cloud. This isn't the case on lxd though, for example. And I'm not sure that it makes sense to round trip local hostname lookups through the network in the ""proper"" cloud case anyway."
1741277,2018-01-04 15:52:38 UTC,"fwiw, its sudo that is causing the roundtrip.
you can certainly come up with reasons to pay a round trip.  the infrastructure then can make changes and each system magically picks them up.  its the reason we don't ship /etc/hosts files around anymore."
1741279,2018-01-09 01:29:31 UTC,"The way to test the theory that the problem is the aforementioned code in boot.py would be to specify the relay VLAN (using the API, so that you don't have to define the dynamic range). This can be done using the CLI as follows:"
1741279,2018-01-09 00:29:46 UTC,I found a section of code I'm suspicious about.
1741279,2018-01-08 19:57:02 UTC,"I think it's worth a try; we need to do more to narrow down the cause. I've looked at the code path which returns the preseed, and didn't see anything that looked like it could cause something like this."
1741279,2019-09-19 11:57:04 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1741279,2018-01-10 23:31:39 UTC,"Marking Incomplete since we could not determine the cause of the issue after another hour-long triage session. (I still believe it has to do with the PXE request, but that has not been proven nor disproven.)"
1741279,2018-01-09 18:55:41 UTC,"Commissioning could initially change the VLAN, but would later reset the interfaces to what was found via DHCP. That's why I think running 'Testing' would be a good test."
1741279,2018-01-09 18:54:36 UTC,If it was the PXE booting problem why does it only happen during deployment? This doesn't happen during commissioning at all.
1741279,2018-01-09 17:36:33 UTC,"If an external DHCP server is setting options to allow machines to PXE boot from MAAS, this will look very similar to a DHCP relay - except the MAAS DHCP server will not actually see the DHCP
request, only the PXE request. Your example shows that the network configuration changes as follows:"
1741279,2018-01-09 15:25:30 UTC,* He is not using a DHCP relay at all.
1741279,2018-01-08 18:29:12 UTC,"So far it's been difficult to reproduce this issue; I set up a similar topology (including an unmanaged network) and hit a different issue[1], though so far it looks unrelated."
1741279,2018-01-08 18:55:29 UTC,I think we should really be looking into if its even possible during a get-curtin-config for it to actually change the interface configuration. Seems like it shouldn't be possible but something is changing it.
1741281,2018-01-04 19:34:37 UTC,So this is strictly spoken a feature request.
1741281,2018-01-04 17:25:35 UTC,"With the Tracks feature it's working, I noticed this when going through my 2017_playlist where I wanted to hide stuff i wouldn't play with Mixxx"
1741281,2018-01-04 17:03:55 UTC,"I cannot confirm this. I see the ""Hide from Library"" item in the track context menu. This does not show up in all library features though. Can you try again with the Tracks feature?"
1741285,2018-01-17 02:56:31 UTC,"Hello, Meltdown mitigations are available in:"
1741285,2018-01-04 19:01:00 UTC,https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown
1741287,2018-01-13 10:55:31 UTC,"i start synaptic
i install adb and fastboot
i open a bash shell
i type: michael@ubuntu:~$ sudo adb sidelo*** Error in `adb': free(): invalid next size (fast): 0x0000563ec3d551b0 ***"
1741290,2020-03-29 21:48:21 UTC,https://github.com/mixxxdj/mixxx/pull/2611
1741291,2018-01-17 04:59:04 UTC,"Hi mhhli,"
1741291,2018-01-05 10:37:03 UTC,"Hi @hongbin
Here is my answers."
1741291,2018-01-05 07:56:39 UTC,"Also, what is the output if you add ""--debug"" flag to the command:"
1741291,2018-01-05 07:54:08 UTC,"Hi @mhhli,"
1741301,2019-10-19 08:38:59 UTC,wxhexeditor 0.24+repack-1 is now available in Ubuntu 19.10 (https://bugs.launchpad.net/ubuntu/+source/wxhexeditor/0.24+repack-1)
1741301,2018-10-25 04:30:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741310,2019-07-08 16:05:46 UTC,Backport for Queens sent upstream: https://review.opendev.org/669708
1741310,2019-07-08 14:15:00 UTC,This was fixed on 2018-05-03.
1741310,2018-01-04 19:51:45 UTC,"At shardy's suggestion, I'm attaching a tarball copy of all the custom env files. They are pretty innocuous, and don't do any get_file on large external files."
1741310,2019-07-10 13:24:52 UTC,There is already a fix in for Queens so all supported OpenStack releases address this issue.
1741314,2019-02-23 10:40:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741315,2018-01-05 15:05:07 UTC,"Reading other comments, my guess is that DE choice might matter for this bug (e16 wm here)."
1741315,2018-01-05 10:26:18 UTC,"similar to Bug 1589121 ?
https://bugs.launchpad.net/inkscape/+bug/1589121"
1741315,2018-01-05 14:44:05 UTC,It is similar though I have no clue if it's the same.
1741315,2018-02-08 08:20:54 UTC,"I had the same problem with inkscape on my friend Ubuntu 17.10.
The problem occured while I had turned doublecmd on.
My friend replaced doublecmd with krusader."
1741315,2018-03-07 16:09:03 UTC,"Same results under opensuse leap 42.3.
Reproducible crash as depicted above.
Inkscape 0.91 r13725
OpenSuSE Leap 42.3"
1741315,2018-09-28 15:31:26 UTC,"On pc Debian testing x86-64, with master sources updated today, I don't reproduce this.
It's been fixed with https://gitlab.com/inkscape/inkscape/commit/d8d99efc5a827e7cedbc228fbfe536bc5e5ed9fb"
1741317,2018-01-04 18:50:46 UTC,This is wishlist.  Just noting it here so I don't forget later.
1741317,2018-01-04 22:23:26 UTC,Remember the microwave toolbox tools.
1741317,2018-01-04 22:42:28 UTC,"@nickoe, you are right, one can backend a shape description file into a parametric necking but that's not really the idea here.  I am envisioning having two traces of different widths be connected by a taper item.  This is a logical extension of teardrops (see attached image), so I'm just noting here for my v6 list."
1741319,2018-01-25 09:44:38 UTC,My initial hunch was something was wonky with the cpu configuration in nova; however:
1741319,2018-01-25 09:49:00 UTC,"""Missing CPU model name"" is bubbling up from libvirt's pre-migration checks."
1741319,2018-01-25 09:52:40 UTC,"Dann - does this work in releases prior to pike?  Reading the nova code, not a huge amount has changed in this area, so I'm wondering whether this is a bug somewhere in the virt stack @ pike."
1741319,2018-01-25 15:59:27 UTC,"James - I never tried it with earlier releases. However, prior to pike, there was the additional reason that QEMU didn't yet support save/restore of these guests at all. See LP: #1710019."
1741319,2018-01-31 20:18:14 UTC,Live migration test: https://github.com/openstack/tempest/blob/master/tempest/api/compute/admin/test_live_migration.py
1741319,2018-02-05 21:13:53 UTC,"The issue is that the XML does not contain the CPU model type, following is what is actually being passed."
1741319,2018-02-06 17:00:44 UTC,"While I agree for cpu-compare needing a cpu to compare.
I happen to migrate guests like http://paste.ubuntu.com/26530819/ all the time which have none as well."
1741319,2018-02-07 08:14:21 UTC,"aarch64 does not have cpu_model = ""host-model"" funtionality which would be required for it."
1741319,2018-02-07 08:16:38 UTC,"Since Aarch64 architectures doesn't provide CPU models, but since we compare CPU models when migrating, that's why we have that issue."
1741319,2018-02-07 08:28:39 UTC,"Anyway, I feel we should amend https://docs.openstack.org/nova/latest/user/feature-classification.html and https://docs.openstack.org/nova/latest/user/support-matrix.html to tell what ARM64 can support."
1741322,2018-01-07 05:30:10 UTC,"As a follow up, I have successfully made a telescope connection via NexRemote. After stepping down versions of Stellarium, vs 17 to 15.1 while trying various connection settings I finally connected with vs 15.1, which I believe was the first version I was using before trying to upgrade to vs 17. In  any case, the connection type I finally used was not “indirect” as is suggested for a remote software connection, but rather a “direct” connection. I had to set my mount type (Nexstar) and configure the port setting. I used the current NexRemote virtual port (Com 2) for the port setting.
By the way, this type of connection did not work on any subsequent versions of Stellarium. Neither direct or indirect. My memory is a little rusty but I believe I had made the this same “direct” connection months before and thought it was odd then too but it worked so what did I care. So there you have it! I know I didn't fix anything but maybe this will offer some clues. I can't code but I sure can hack.. ;-)"
1741322,2018-01-05 09:19:18 UTC,"v0.17 introduced INDI telescope support. We unfortunately cannot test the necessary changes this move brought in, because we (2-3 active developers) do not have the telescope mounts required. You can try to run your telescope now via INDI. Hopefully the old functionality can also be restored (or checked again what happened)."
1741322,2018-01-05 16:42:16 UTC,"Georg, thank you for your answer. I will try the INDI connection. If this doesn’t work maybe I can try an earlier version of Stellarium.
Can you tell me what becomes of this issue, will the status remain open until hopefully it can be addressed, or do I post another bug report at a later date?
Thank you for your help.
-Scott"
1741322,2018-01-05 21:29:49 UTC,"Sorry about that, text was cut off; complete Log text file now attached."
1741322,2018-01-05 18:55:45 UTC,"No, this bug report will stay in open state, but it is unclear when we can deal with it. I have a small NexStar compatible mount, so when it really does not work, I am affected myself, bothered and annoyed by this fact and will be possibly motivated enough... But my time budget is limited, so it may be February or June. I spend considerably more time developing this simulation than getting starlight :-( If INDI does not work for you, V0.16.1 should have the same connectivity options as 0.15."
1741322,2018-01-05 21:14:51 UTC,"I am attaching the log here if it helps. The log shows attempted
connection, external local, with NexRemote loaded and running. I did try
INDI connection but that did not work either - not included in log.
Thank you for your support - Scott"
1741322,2018-09-26 04:47:02 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/392
1741322,2018-01-05 18:57:29 UTC,"I assign this bug to myself just to remember, but if anybody else want to solve it, I am not unhappy."
1741331,2018-01-10 19:27:12 UTC,"Ok, this is not a bug!
i am not surre how to remove it from here, or if it should be removed.
the bottom line, is that my interfaces file has an extra line whcih actually brought the ethernet interfaces on the Host level."
1741337,2018-01-04 20:30:55 UTC,Previous discussion in IRC:
1741346,2018-01-05 19:33:10 UTC,Thanks for reporting.
1741347,2018-05-24 20:51:36 UTC,"> Attributes like circulate?, reference?, etc. are true/false rather than yes/no.
"
1741347,2018-04-25 22:23:42 UTC,I can confirm that the above issues are all still present in 3.1.
1741347,2018-02-08 16:54:10 UTC,Author and title are normalized and should be as appears in MARC record
1741348,2018-01-11 21:00:53 UTC,sudo apt-get install compizconfig-settings-manager
1741348,2018-01-11 20:43:59 UTC,where would one find that?
1741348,2018-01-11 18:13:24 UTC,"This is known bug, you have to use CompizConfig Settings Manager to change that."
1741351,2018-01-15 16:52:24 UTC,"I had something similar happen to my server, but instead of being rewritten to localhost, it lost the port number. See https://launchpad.net/bugs/1743142"
1741351,2019-09-19 11:57:07 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1741355,2018-01-04 22:48:17 UTC,I'd love to see this work properly. Sadly my touchscreen device is running Linux which doesn't really handle gestures well _anyway_ :(
1741364,2018-01-08 21:56:13 UTC,Note there is a patch for this issue in another bug:
1741364,2018-01-08 21:51:21 UTC,"lyarwood has pointed this out before in IRC, but I wanted to mention it again here for clarity: the difference in those disks is one is an ephemeral disk based on the libvirt rbd imagebackend code in nova, and that one gets its values from nova.conf. The other is a volume and nova gets the config values from the cinder connection_info which gets refreshed during the live migration here:"
1741365,2021-01-25 07:46:07 UTC,Please explain in more detail what problem you are/were experiencing.
1741372,2018-01-18 02:00:02 UTC,"Hi Feng,"
1741372,2018-01-17 06:09:20 UTC,"Hi, zoralab, Sorry for the late reply.
Does 'apt-get update' still get that warning?
I test here and all works fine."
1741373,2020-03-24 15:26:44 UTC,Marking as Incomplete while waiting for the requested info.
1741373,2018-11-29 07:38:50 UTC,Any update on this?
1741373,2018-06-14 10:38:48 UTC,Do You have link to failed job? I would like to check logs from it
1741373,2018-03-01 06:23:58 UTC,"Thanks for reporting this.
I'm not sure what causes this, so let's look at it together."
1741373,2020-05-24 04:17:21 UTC,[Expired for tempest because there has been no activity for 60 days.]
1741374,2018-01-05 03:33:59 UTC,I know there isn't a cue point on Samplers. So I guess reload or return to the start.
1741374,2018-01-05 03:28:20 UTC,Go back to the start of the Sampler. I meant cue not queue.
1741374,2018-01-05 02:12:59 UTC,"What do you mean by ""re-queue""? Go back to the cue point? What skin are you using?"
1741374,2018-01-05 07:23:44 UTC,I can confirm that I cannot see The CUE point in the sampler over view. But the sampler actually use it. The play button is goto_cue_and_play and the right click is the original cue button form the decks.
1741374,2018-01-05 12:46:29 UTC,"I'm currently using Dark Metal on my broadcast computer via 2.0, I testing 2.1 on a different computer using Latenight that comes with it. I can use either."
1741374,2018-01-05 21:38:30 UTC,"It seems DarkMetal does not use the right Control for the sampler play button then. The sampler play button should play from the sampler's cue point. If any of the official skins do not do that, please let us know."
1741374,2018-01-05 23:55:54 UTC,Yep! I see that. I can let Jorge know on the forum.
1741377,2018-01-08 15:40:49 UTC,"I would like to see a spec on this RFE. Please whoever will be working on it, submit a spec as explained in https://docs.openstack.org/ironic/latest/contributor/code-contribution-guide.html#ironic-specs-process"
1741377,2018-01-10 09:25:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/532468"
1741381,2018-07-26 15:30:20 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1741381,2018-08-09 01:00:24 UTC,"code is not ready now, just keep private. Thanks"
1741381,2019-05-06 09:00:20 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1741381,2019-12-24 04:18:02 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1741382,2018-01-05 07:29:51 UTC,"Good idea, please file this to a separate bug."
1741382,2018-01-05 04:22:42 UTC,Well you don't have elapsed or estimate time in Auto-DJ. Sure one could estimate in their head based on the timestamp adding up the times of songs and hope they have the time right or close.
1741382,2018-01-05 03:26:01 UTC,Oh and while in auto-dj mode after it plays the Sampler Auto-DJ continues with the next song.
1741382,2018-01-05 04:09:34 UTC,Wouldn't this use case be better served by putting the estimated time a track will play in the AutoDJ playlist (Bug #1575985)?
1741382,2018-01-05 04:26:31 UTC,"Something else to go with this with a timer is Setting start and stop times for Auto-DJ.  Stop at 10:00 for Bob's show, Start at 12:00 at the end of Bob's show. It would also have to disconnect and reconnect the encoders."
1741384,2018-01-06 01:29:16 UTC,"Ok I'm sorry if I""m wasting your time with these things. I guess I'm excited that you are so on it."
1741384,2018-01-06 00:46:00 UTC,The master level meter indicates the level of the broadcast signal.
1741384,2018-01-05 07:28:19 UTC,"Which software does it? Do you know which protocol is used?
How do you wish to see this info in Mixxx?"
1741384,2018-01-05 13:05:10 UTC,I know SAM Broadcaster does. SAM combines from all servers into one. I currently have to use 3 websites via a webpage with all 3 on one page. I can give you the URL privately.
1741384,2018-01-05 14:53:21 UTC,"http://support.spacialaudio.com/wiki/SimpleCast
Hier is the Sam manual."
1741384,2018-01-05 14:54:21 UTC,.. a kind of statistics ...
1741384,2018-01-05 15:29:16 UTC,Here is how I got the data. http://bluegrassjams.org/sc2.php
1741384,2018-01-06 00:27:32 UTC,I just thought of something that goes along with this. A visual (VU Meter) showing the level of the signal that is Recording/Broadcasting. Nothing worse than having a volume turned down somewhere (external mixer) and broadcasting silence. A VU Meter would show you the level of the broadcast audio.
1741384,2018-01-05 15:39:39 UTC,"By the way, SimpleCast is now SAMcast and they have a 7 day free trial after which it's $199 just to do the encoders and gather stats. https://spacialaudio.com/sam-cast/"
1741400,2018-02-21 12:55:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546587"
1741404,2018-01-20 04:41:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741407,2018-01-09 01:11:00 UTC,I found the problem in pike branch. But I checked the master branch and the code is the same.
1741407,2018-01-08 20:44:35 UTC,Is this happening in master branch?
1741413,2018-03-08 04:03:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741416,2018-01-07 00:20:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741422,2020-06-25 10:02:18 UTC,"Change abandoned by Riccardo Pittau (<email address hidden>) on branch: master
Review: https://review.opendev.org/531336
Reason: inactivity"
1741422,2018-01-09 15:19:02 UTC,"I kind of feel like this might be a feature that may be enabling some deployments to work, but it also seems like the right time and go-ahead and formalize the expectation for the operator. Comments posted to the proposed change as well."
1741422,2018-01-09 15:05:26 UTC,https://review.openstack.org/#/c/531336 is the current patch associated with this issue.
1741425,2019-05-23 22:48:28 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/661129"
1741425,2018-01-08 03:03:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531638"
1741425,2018-02-07 03:24:05 UTC,"Reviewed:  https://review.openstack.org/531638
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=51dd510636c817d2f7b5cb0b3c967fb604de87bb
Submitter: Zuul
Branch:    master"
1741425,2018-02-08 01:15:31 UTC,We had to revert the fix for this bug because it broke the generic driver. This bug will remain open until a correct fix is merged.
1741425,2018-02-08 23:33:20 UTC,This issue was fixed in the openstack/manila 6.0.0.0rc1 release candidate.
1741425,2018-10-16 03:52:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/610875"
1741425,2019-05-23 22:49:10 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661130"
1741425,2019-05-24 03:00:51 UTC,"Change abandoned by Manuel Rodriguez (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/661129
Reason: cherry picking from stein"
1741425,2019-05-24 22:28:00 UTC,"Change abandoned by Manuel Rodriguez (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/661130
Reason: Tom, I didn't remove the release notes, I cherry picked the whole patch. So I'm not sure how it happened, I'll abandon this and try once again."
1741425,2019-05-30 20:24:44 UTC,"Change abandoned by Manuel Rodriguez (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/661130
Reason: I just realized this patch was reverted in commit b70b85386ab6380a80e8a8dd30a9b273481f11e5, even if I apply it, it didn't work, the work around was to increase the default 25 images returned by glance in the glance config with: limit_param_default"
1741425,2019-09-19 14:58:08 UTC,Hey sapd anyone update on this bug it looks like we have had some abandoned on stein? Do you need any help getting this fixed?
1741425,2020-06-25 16:26:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/738061"
1741425,2020-07-01 02:24:27 UTC,"Reviewed:  https://review.opendev.org/738061
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=1982b90c07612d1e54f4b26ee3924096e964a504
Submitter: Zuul
Branch:    master"
1741439,2018-01-15 09:29:24 UTC,I think we can handle this in a better way. Please look at the updated patch. We should not hardcode the paths in the code. Better to provide them as configuration params.
1741439,2018-01-12 07:41:02 UTC,The location of isolinux.bin can be set with the [DEFAULT]/isolinux_bin config parameter to avoid this error.
1741439,2018-01-08 09:29:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531700"
1741439,2020-06-25 10:04:22 UTC,"Change abandoned by Riccardo Pittau (<email address hidden>) on branch: master
Review: https://review.opendev.org/531700
Reason: inactivity"
1741443,2018-01-05 11:12:31 UTC,I just noticed 2 nics is defined on the requirements right above that. I think the only thing that needs to be clear is what network the 2nd nic should be connected to.
1741443,2020-12-10 21:51:21 UTC,This has been since clarified in the Quick Start guide:
1741450,2020-12-10 21:55:36 UTC,"Copy inventory files to current directories is fine, they don't have to be in /etc/kolla."
1741451,2018-01-12 09:02:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741456,2018-05-07 08:14:02 UTC,"Please comment on storyboard, we don't use launchpad anymore:
https://storyboard.openstack.org/#!/story/1741456"
1741456,2018-05-06 14:21:04 UTC,"Now, I find if I use haproxy or I deployment network node on other computer which is no sahara_engine or sahara_api, this error will be hadppen, I think the command 'ip netns exec qrouter-fakerouter nc 10.0.0.2 22' will not exec, because  there is no ip netns on the computer which sahara service run.
I find not only ssh but also http will exec the command(http port is 8080). but if I use the qdhcp namespace, I can exec the command correctly.
Could someone fix it ?"
1741456,2018-01-05 12:04:35 UTC,Thanks.
1741456,2018-01-05 11:29:23 UTC,"I don't know how DVR works or what does change in the network setting, but you can redefine proxy_command from sahara.conf. Check sahara/utils/remote.py:"
1741457,2019-05-28 04:17:42 UTC,[Expired for kolla because there has been no activity for 60 days.]
1741457,2019-03-28 10:53:15 UTC,"Is this still an issue (has the documentation improved)? If yes - please update, otherwise bug will be expired in 60 days."
1741459,2019-07-27 10:56:54 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1741459,2018-02-05 09:57:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741459,2019-09-26 04:17:35 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1741463,2018-11-02 12:49:39 UTC,I'm still seeing this issue. But I found out that I can work around this issue by setting the container config security.nesting to true.
1741463,2019-12-15 04:17:37 UTC,[Expired for Snappy because there has been no activity for 60 days.]
1741463,2019-10-15 11:21:50 UTC,If you were running a privileged container before then this is not supported. Snapd doesn't operate (but does not detect the presence of) a privileged container.
1741463,2018-01-09 11:54:13 UTC,"The edge channel doesn't work. It seems the failing part is actually ""flags"" so (presumably) ""ro, remount"". We are investigating if this is a bug in the parser/kernel. We never used remount flag before."
1741463,2018-01-09 11:45:17 UTC,"This appears to be fixed in master already, with the following code in snap-confine.apparmor.in"
1741463,2018-01-09 11:20:36 UTC,"Looking more, there are some DENIALS in the host syslog:"
1741463,2018-01-05 15:25:57 UTC,"This seem to be related to my local setup. The above was using my desktop. When I tried the same on my laptop I was able to install maas. The setup of the laptop and desktop is similar, though."
1741467,2018-04-25 04:48:41 UTC,apport information
1741467,2018-04-25 04:48:40 UTC,apport information
1741467,2018-04-25 04:48:32 UTC,apport information
1741467,2018-04-25 04:48:18 UTC,apport information
1741467,2018-04-25 04:48:14 UTC,apport information
1741467,2018-04-24 22:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1741467,2018-04-25 04:48:38 UTC,apport information
1741467,2018-04-25 04:48:34 UTC,apport information
1741467,2018-04-25 04:48:36 UTC,apport information
1741467,2018-04-25 04:49:43 UTC,apport information
1741467,2018-04-25 04:49:04 UTC,apport information
1741467,2018-04-25 04:48:53 UTC,apport information
1741467,2018-04-25 04:48:50 UTC,apport information
1741467,2018-04-25 04:48:47 UTC,apport information
1741467,2018-04-25 04:48:44 UTC,apport information
1741467,2018-04-25 04:48:43 UTC,apport information
1741469,2019-09-15 17:09:20 UTC,Migrated to https://github.com/widelands/widelands/issues/1067
1741472,2018-01-31 06:52:15 UTC,"Oh we tried both it doesn't matter - the error is (almost) the same.
the for-merge case just happened to be the one I grabbed the log."
1741472,2018-01-29 23:31:05 UTC,The fix for the nnewer issue is part of #1741472
1741472,2018-01-29 11:56:59 UTC,"I know this is in progress, but juts FYI recent edge still fails, but with slightly different error messages:"
1741472,2018-01-30 21:09:08 UTC,"On Mon, Jan 29, 2018 at 3:31 PM, Nish Aravamudan
<email address hidden> wrote:

> The fix for the nnewer issue is part of #1741472
>
> On Mon, Jan 29, 2018 at 3:56 AM, ChristianEhrhardt
> <email address hidden> wrote:
>> I know this is in progress, but juts FYI recent edge still fails, but
>> with slightly different error messages:
>>
>> $ git ubuntu build-source --verbose --sign --for-merge
>> 01/29/2018 12:54:13 - DEBUG:Executing: git config gitubuntu.lpuser
>> 01/29/2018 12:54:13 - DEBUG:Executing: grep -q ""* -ident"" /tmp/review/ubuntu-fan/.git/info/attributes
>> 01/29/2018 12:54:13 - DEBUG:Executing: grep -q ""* -text"" /tmp/review/ubuntu-fan/.git/info/attributes
>> 01/29/2018 12:54:13 - DEBUG:Executing: grep -q ""* -eol"" /tmp/review/ubuntu-fan/.git/info/attributes
>> 01/29/2018 12:54:13 - DEBUG:Executing: git config gitubuntu.lpuser
>> 01/29/2018 12:54:13 - DEBUG:Executing: sh -c ""dpkg-parsechangelog -l- -n1 -SVersion""
>> 01/29/2018 12:54:13 - DEBUG:Executing: git status --porcelain
>> 01/29/2018 12:54:13 - DEBUG:Executing: sh -c ""dpkg-parsechangelog -l- -n1 -SVersion""
>> 01/29/2018 12:54:13 - DEBUG:Executing: sh -c ""dpkg-parsechangelog -l- -n1 -o1 -SVersion""
>> 01/29/2018 12:54:13 - DEBUG:Executing: sh -c ""dpkg-parsechangelog -l- -SSource""
>> 01/29/2018 12:54:13 - DEBUG:fetch_orig_from_parent_dir(source=None) failed
>> 01/29/2018 12:54:13 - DEBUG:fetch_orig_from_cache(source=debian) failed
>> 01/29/2018 12:54:13 - DEBUG:Executing: pristine-tar list
>> 01/29/2018 12:54:13 - DEBUG:Executing: pristine-tar list
>> 01/29/2018 12:54:14 - WARNING:No pristine-tar data found for 0.12.9~17.10.1
>> 01/29/2018 12:54:14 - DEBUG:fetch_orig_from_pristine_tar(source=debian) failed
>> Traceback (most recent call last):
>>   File ""/snap/git-ubuntu/352/bin/git-ubuntu"", line 11, in <module>
>>     load_entry_point('gitubuntu==0.6.2', 'console_scripts', 'git-ubuntu')()
>>   File ""/snap/git-ubuntu/352/lib/python3.6/site-packages/gitubuntu/__main__.py"", line 243, in main
>>     sys.exit(args.func(args))
>>   File ""/snap/git-ubuntu/352/lib/python3.6/site-packages/gitubuntu/buildsource.py"", line 103, in cli_main
>>     default_rem_args=default_rem_args,
>>   File ""/snap/git-ubuntu/352/lib/python3.6/site-packages/gitubuntu/build.py"", line 707, in cli_main
>>     retry_backoffs=args.retry_backoffs,
>>   File ""/snap/git-ubuntu/352/lib/python3.6/site-packages/gitubuntu/build.py"", line 493, in main
>>     retry_backoffs,
>>   File ""/snap/git-ubuntu/352/lib/python3.6/site-packages/gitubuntu/build.py"", line 1203, in fetch_orig_and_build
>>     tarballs = entry.mechanism(changelog, entry.source)
>>   File ""/snap/git-ubuntu/352/lib/python3.6/site-packages/gitubuntu/build.py"", line 345, in fetch_orig_from_launchpad
>>     for spi in versions_published:
>>   File ""/snap/git-ubuntu/352/lib/python3.6/site-packages/gitubuntu/source_information.py"", line 444, in launchpad_versions_published
>>     (self.pkgname, self.dist_name))
>> gitubuntu.source_information.NoPublicationHistoryException: Is ubuntu-fan published in debian?
"
1741478,2018-01-08 14:04:25 UTC,This is not totally unexpected - we need to decide what to do about it. When we started the work on 14.04 the agreement was to focus on server use-cases. If we need to support full GUI snaps there will be extra work/investigations that we need to do.
1741478,2018-01-08 14:03:39 UTC,I tested this a few times and indeed it is not working. Since brave is a regular snap (not classically confined) whatever is causing this is much more subtle and may relate to IPC with system services. It needs more investigation to understand.
1741484,2021-01-16 04:17:41 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1741487,2018-01-05 16:20:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1741488,2018-02-18 17:33:24 UTC,"By the way, I circumvented this by explicitly setting ZFS_POOL_IMPORT=""rpool"" in /etc/default/zfs"
1741489,2018-02-27 18:15:34 UTC,"We are facing the same issue.
We have two nodes with multipath enabled with related labels  KOLLA_CEPH_OSD_BOOTSTRAP and KOLLA_CEPH_OSD_CACHE_BOOTSTRAP."
1741489,2019-06-21 11:07:13 UTC,I'm having the same issue with stable/stein. I'll try the patches but kolla's patch is failing.
1741489,2019-06-21 11:10:04 UTC,Ignore previous output and see below for the right one.
1741489,2019-05-22 10:23:48 UTC,"hi wangwei
I try to https://review.opendev.org/#/c/599962/ (try with 2 way)
normal to deploy but ceph osd is 0 up and openstack show disk capacity is 0"
1741489,2019-05-08 01:31:57 UTC,These two commits supports iscsi disks and multipath disks.
1741489,2019-02-07 07:41:33 UTC,Is this still an issue for recent k-a versions (and OpenStack releases)?
1741489,2018-03-02 10:37:57 UTC,I have the same issue on a Dell VRTX with a PERC8 controller.
1741489,2018-02-28 17:59:39 UTC,"Looking at the find_disk.py(https://github.com/openstack/kolla/blob/master/docker/kolla-toolbox/find_disks.py) script, I saw that kolla is looking for the candidate device under block subsystem using pyudev. Mapper-devices are not listed under this subsystem, indeed they are not discovered. Using labels directly on storage devices, such as /dev/sdb or /dev/sdc entails a duplicate storage device as result of find-disk function.
I'm still looking for a way to list multipath disk using pyudev."
1741489,2019-05-23 06:39:36 UTC,hi hotkhwan:
1741489,2019-07-11 07:25:38 UTC,hi hotkhwan
1741489,2019-06-10 04:33:53 UTC,"hi wangwei
I follow two patches the Bootstrapping Ceph OSDs has fail
kolla version 8.1.0.dev76
kolla-ansible version  8.1.0.dev130"
1741505,2018-01-05 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1741505,2018-01-06 09:55:04 UTC,"Hi Joseph, no this issue has not occurred on any other Ubuntu kernels up to 4.14. In particular, 4.13 works fine and is much more stable (does not hangs and has no issues with the periphery unlike 4.14).
It seems all the required information that could be provided was provided from my side as the attachment on the initial reporting of this bug."
1741505,2018-01-05 20:28:59 UTC,This is the mainline kernel that can be used for testing.  Are you also seeing this issue with supported Ubuntu kernels?
1741514,2018-01-05 19:09:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1741525,2019-09-19 14:53:41 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1741525,2018-05-09 21:23:30 UTC,"Hi Jason,"
1741527,2019-09-19 14:53:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1741540,2018-01-12 02:09:04 UTC,"I'm not sure if this is really a bug with the charm. Pretty sure when I looked at it, it's by design that the plugin doesn't inform PagerDuty to avoid flapping (clearing, and triggering alerts etc.)."
1741540,2020-04-26 04:17:33 UTC,[Expired for Nagios Charm because there has been no activity for 60 days.]
1741540,2020-02-26 03:11:32 UTC,"Need to know if this is consistent with alerts going from CRITICAL to OK without flapping.  If they're going from CRITICAL to WARNING, or flapping is detected, then the notification won't be sent."
1741540,2018-01-12 02:10:41 UTC,(that's in reference to alerts going from CRITICAL back to WARNING)
1741540,2018-01-11 21:23:52 UTC,Just heard that an alert from a warning state on a site that cleared in nagios but didn't get resolved automatically in pagerduty happened.
1741581,2018-01-15 19:40:27 UTC,Fixed upstream: https://cgit.freedesktop.org/libreoffice/core/commit/?id=35ad7482af49ab80d348b619b6d420ee170d3e5d
1741581,2018-01-08 15:36:48 UTC,"Bug reported upstream, where the apparmor profiles are maintained: https://bugs.documentfoundation.org/show_bug.cgi?id=114915."
1741581,2018-01-06 00:57:21 UTC,And a corresponding bug in the AppArmor project in case we wish to handle it there instead:
1741584,2018-01-08 18:03:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741586,2018-10-24 05:12:06 UTC,"Yes, i am having the same problem. First I thought there was something spooking it, but there is absolutely nothing running. Did we figure out what the problem was? I really use and like this program, is the fix scheduled any time soon?"
1741588,2018-01-09 19:47:40 UTC,"Polarr is a Snap, but the bug I intended to report here is that on 16.04, none of the items in the category list display or are clickable. The screenshot attached to the original bug report illustrates the problem. I couldn't say for sure whether Polarr is in the list or not because each of the apps display as a box with an ellipsis inside: no icon or text. One weird thing I when switching between categories is that none of the items in the list for each category render or are clickable, but there are different amounts of items in each category. I know I had an internet connection because I was on a video call."
1741588,2018-01-09 00:57:55 UTC,Is Polarr a Snap? Snaps don't currently work with categories (https://forum.snapcraft.io/t/mapping-snap-store-sections-to-xdg-sections)
1741588,2018-01-09 00:58:26 UTC,See also bug 1665126
1741588,2018-01-09 20:17:09 UTC,Thanks for the clarification!
1741588,2018-01-17 12:31:20 UTC,Thank you for your bug report. I can't confirm that on a xenial uptodate system here. Does it happen on a fresh login or only after some steps (maybe interacting with a snap in some way)?
1741588,2018-01-17 22:02:11 UTC,"It happened on a fresh login for all categories in the software store on 16.04. I upgraded my 16.04 machine to 17.10, but I could wipe the OS partition and reinstall 16.04 this weekend to test if the software store still has the same problem with displaying categories."
1741589,2018-04-18 11:43:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741589,2018-04-18 11:45:53 UTC,"I can confirm the problem.  For me, nothing changes whether or not I install the libcanberra-gtk libs."
1741590,2021-02-16 00:43:34 UTC,"Don't believe this is the case these days, we're using reactive and ensure directory exists."
1741596,2018-01-22 19:56:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741596,2018-01-06 06:05:38 UTC,I am more than happy to contribute code patches to Compiz to fix this! Please let me know and I'll work on that.
1741596,2018-01-22 20:01:26 UTC,AskUbuntu thread for reference: https://askubuntu.com/questions/587045/screen-tearing-in-chrome-while-watching-netflix-in-full-screen-on-14-04-lts
1741610,2018-01-09 23:42:32 UTC,no -signed packages in esm.
1741610,2018-01-10 02:01:44 UTC,The package has been published and the bug is being set to Fix Released
1741612,2018-01-10 06:31:52 UTC,The package has been published and the bug is being set to Fix Released
1741614,2018-01-06 12:12:28 UTC,"trove-dashboard does not provide a documentation at now.
What the horizon team can do seems just to drop trove-dashboard related documentation."
1741614,2018-01-06 13:16:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/531549"
1741614,2018-01-25 21:25:43 UTC,"Reviewed:  https://review.openstack.org/531549
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=77ed0e3db2b72b215051b80da3f7577ff6f474a6
Submitter: Zuul
Branch:    master"
1741614,2018-02-09 07:19:43 UTC,This issue was fixed in the openstack/horizon 13.0.0.0rc1 release candidate.
1741616,2018-01-06 20:35:20 UTC,"On 2018-01-06, Kim B. Heino wrote:

> Commit d3ab0dc8674e5 added decode() calls to ""locale -a"" parsing.
> decode() without any parameters equals to decode('utf-8', 'strict'),
> which will generate UnicodeDecodeError for non-UTF-8 input.
>
> RHEL7's ""locale -a"" outputs such non-UTF-8 line:
>
> fran<E7>ais
"
1741619,2018-01-08 13:01:50 UTC,"Hi Stefan,
Arch Linux is not supported distro for HPLIP drivers. Can you please confirm on which distro version you downgraded to 3.17.10 and it worked? Ideally the 3.17.10 hplip driver will not work in Arch Linux."
1741619,2018-01-08 14:20:35 UTC,"Hi Shivani,"
1741619,2018-01-22 09:59:19 UTC,"Hi Stefan,"
1741619,2018-10-06 16:00:04 UTC,"Hi,"
1741619,2018-10-06 16:34:08 UTC,"I just removed the ubuntu package and installed hplip 3.18.9 from https://developers.hp.com/hp-linux-imaging-and-printing/gethplip.
The problem still exists."
1741621,2018-01-08 01:40:03 UTC,https://devtalk.nvidia.com/default/topic/1028016/patch-for-compiling-v384-98-modules-with-linux-v4-14-9-/
1741621,2018-01-09 11:31:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741636,2018-01-07 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1741636,2018-01-06 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1741636,2018-01-06 17:49:06 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1741636,2018-01-29 23:04:08 UTC,"Hi Guys I appreciate your effort to help me, but the computer is dead."
1741636,2018-01-09 06:28:58 UTC,"Hello,"
1741636,2018-01-07 12:41:59 UTC,"It's impossible to use the window terminal, once the computer doesn't work at all."
1741646,2018-01-09 21:32:58 UTC,The package has been published and the bug is being set to Fix Released
1741646,2018-01-09 20:11:02 UTC,This bug was fixed in the package linux-aws - 4.4.0-1047.56
1741652,2018-01-09 21:33:54 UTC,The package has been published and the bug is being set to Fix Released
1741652,2018-01-09 21:03:53 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1082.90
1741653,2018-04-05 08:35:01 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1088.93
1741653,2018-01-09 21:04:48 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1084.89
1741653,2018-01-09 21:34:18 UTC,The package has been published and the bug is being set to Fix Released
1741655,2018-03-20 05:29:42 UTC,tested it on artful and 16.04 LTE. On 16.04 LTE the kernel from comment #6 working since mid of January without any problems.
1741655,2018-01-06 16:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1741655,2018-01-06 17:47:39 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1741655,2018-01-06 19:37:51 UTC,"4.15-rc6 is functional:
# lsmod | grep kvm
kvm_intel             200704  0
kvm                   581632  1 kvm_intel
irqbypass              16384  1 kvm
# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used"
1741655,2018-01-11 23:11:37 UTC,I built a test kernel with a pick of commit 8a1b439.  The test kernel can be downloaded from:
1741655,2018-01-15 09:04:52 UTC,The Problem exists now also in 16.04 LTS with the HWE Stack and the newest 4.13 kernel series with kpti.
1741655,2018-01-15 09:11:17 UTC,"Kernel is working, please fix also the HWE for 16.04 with the patches"
1741655,2018-01-16 03:40:12 UTC,"That build is also working for me:
$ uname -a
Linux localhost 4.13.0-25-generic #29~lp1741655 SMP Thu Jan 11 19:45:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsmod | grep kvm
kvm_intel             200704  24
kvm                   585728  1 kvm_intel
irqbypass              16384  21 kvm
$ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used"
1741655,2018-01-16 05:59:07 UTC,The server works now over 20 hours with approx 10 vm's without any problems. so i think the problem is solved for me. let's hope it's included fast in the 4.13 packages of hwe
1741655,2018-02-10 13:57:50 UTC,"Latest 4.13 lowlatency kernel in 16.04.3 (xenial), still has the regression."
1741655,2018-03-15 20:53:37 UTC,After installing HWE stack and getting to 16.04.4 and updating kernel to 4.13.0-36 I still get this issue. So yes latest Xenial 16.04.4 still has it.
1741655,2018-03-19 10:58:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1741655,2018-01-19 15:05:20 UTC,"SRU request submitted for Artful and Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089404.html"
1741655,2018-03-21 11:41:29 UTC,"Yes proposed works like it should.
There's one thing I'd like to know, though. If the fix was in upstream such little time after the regression was introduced, why are we still having the regression in ubuntu after so long?"
1741655,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1741655,2018-06-20 14:28:53 UTC,"This has been fixed for some time, so when can we expect this to be in an updated Bionic kernel?"
1741655,2019-10-03 08:21:22 UTC,"This fix can be found in 4.15 Bionic since Ubuntu-4.15.0-9.10:
phlin@tangerine:~/ubuntu-bionic$ git tag --contain 8a1b43922d0d1279e7936ba85c4c2a870403c95f
Ubuntu-4.15.0-10.11
Ubuntu-4.15.0-11.12
Ubuntu-4.15.0-12.13
Ubuntu-4.15.0-13.14
Ubuntu-4.15.0-14.15
Ubuntu-4.15.0-15.16
Ubuntu-4.15.0-16.17
Ubuntu-4.15.0-17.18
Ubuntu-4.15.0-18.19
Ubuntu-4.15.0-19.20
Ubuntu-4.15.0-20.21
Ubuntu-4.15.0-21.22
Ubuntu-4.15.0-22.24
Ubuntu-4.15.0-23.25
Ubuntu-4.15.0-24.26
Ubuntu-4.15.0-25.27
Ubuntu-4.15.0-26.28
Ubuntu-4.15.0-27.29
Ubuntu-4.15.0-28.30
Ubuntu-4.15.0-29.31
Ubuntu-4.15.0-30.32
Ubuntu-4.15.0-32.35
Ubuntu-4.15.0-33.36
Ubuntu-4.15.0-34.37
Ubuntu-4.15.0-35.38
Ubuntu-4.15.0-36.39
Ubuntu-4.15.0-37.40
Ubuntu-4.15.0-38.41
Ubuntu-4.15.0-39.42
Ubuntu-4.15.0-40.43
Ubuntu-4.15.0-42.45
Ubuntu-4.15.0-43.46
Ubuntu-4.15.0-44.47
Ubuntu-4.15.0-45.48
Ubuntu-4.15.0-46.49
Ubuntu-4.15.0-47.50
Ubuntu-4.15.0-48.51
Ubuntu-4.15.0-49.52
Ubuntu-4.15.0-49.53
Ubuntu-4.15.0-50.54
Ubuntu-4.15.0-51.55
Ubuntu-4.15.0-52.56
Ubuntu-4.15.0-53.57
Ubuntu-4.15.0-54.58
Ubuntu-4.15.0-55.60
Ubuntu-4.15.0-56.62
Ubuntu-4.15.0-57.63
Ubuntu-4.15.0-58.64
Ubuntu-4.15.0-59.65
Ubuntu-4.15.0-59.66
Ubuntu-4.15.0-60.67
Ubuntu-4.15.0-62.69
Ubuntu-4.15.0-63.70
Ubuntu-4.15.0-64.73
Ubuntu-4.15.0-65.74
Ubuntu-4.15.0-66.75
Ubuntu-4.15.0-9.10
...."
1741664,2018-04-09 15:46:22 UTC,"Seems to be working in Manjaro/Arch, I can't confirm Debian; I'm assuming if it works there, this issue can be closed, but I can't figure out how to close it :)"
1741664,2018-01-07 23:17:13 UTC,I get the same error and Gweled never starts.
1741664,2018-01-14 00:27:03 UTC,"It happens with librsvg > -2:2.40.19-1 fails with segfualt, same error as others. Here is the segfault info:
[code]gweled[pid#]: segfault at 1f8 ip 00007f8ea91ca901 sp 00007ffd45cb8cb0 error 4 in libc-2.26.so[7f8ea9148000+1ae000][/code]"
1741664,2018-02-05 03:11:19 UTC,"This is caused by a librsvg bug [1], but it also exposes a bug in Gweled's error handling (GError pointer must be set to null before being used). A patch that works around the librsvg bug and fixes the error handling is attached."
1741664,2018-02-05 06:01:16 UTC,"I can confirm the patch works - I wasn't able to patch the package as I have something messed up in my makepkg.conf that prevented makepkg from finding the correct file to patch however, I manually edited the lines in <[build directory]/gweled/src/gweled-0.9.1/src/sge_utils.c> according to the patch and reran makepkg (without the edited patch info) and have am once again playing gweled :)"
1741664,2018-02-05 07:57:37 UTC,"This is a more defensive patch that should work regardless of how librsvg chooses to proceed -- whether it allows only path, only URI, or both."
1741664,2018-02-05 15:24:46 UTC,Arch Linux bugreport: https://bugs.archlinux.org/task/56919
1741664,2018-02-07 09:43:24 UTC,"The librsvg bug that triggers this has been marked fixed and will be in librsvg 2.42.3. Once that reaches users, they should see this issue disappear."
1741665,2018-01-06 18:45:52 UTC,"On further thought, I am doubting that we should bother users with the choice between scanning and scanning + analysis. With analysis, scanning, and database transactions each in their own proper threads and not hanging the GUI, I think we could just replace the automatic scan on first start with automatic scan + analysis. If the user wants to cancel analysis part way through, they could click a cancel button in the library GUI."
1741665,2018-01-22 07:33:22 UTC,"We have to consider, that the beatgrid and waveforms took a significant HD space.
So I am in doubt that analyzing by default is a good choice."
1741665,2018-01-06 18:53:02 UTC,Related: Bug #1741676 (add tracks to library as scanner is running)
1741671,2021-01-19 04:17:48 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1741671,2021-01-19 04:17:46 UTC,[Expired for nvidia-graphics-drivers-340 (Ubuntu) because there has been no activity for 60 days.]
1741671,2021-01-19 04:17:45 UTC,[Expired for nvidia-graphics-drivers-304 (Ubuntu) because there has been no activity for 60 days.]
1741671,2020-11-19 20:10:51 UTC,"Hi Po-Hsu Lin,"
1741671,2020-11-09 14:13:22 UTC,Hi
1741671,2018-01-21 18:38:37 UTC,Martin's solution worked for me
1741671,2018-01-30 20:40:02 UTC,"Last week the fixed version of nvidia-340 (340.104-0ubuntu0.16.04.1) that resolves this bug has landed in xenial-updates. Just as the previous comments and people before me, this fixed the reported issue."
1741671,2018-01-25 18:16:36 UTC,It still doesn't work with Xinerama.
1741671,2018-01-22 05:25:31 UTC,I solved it with this:
1741671,2018-01-20 20:55:40 UTC,"Martin's solution worked for me on 16.04.3 LTS with kernel 4.13.0-26.29~16.04.2 giving me nvidia-340 340.104-0ubuntu0.16.04.1
Thanks!"
1741671,2020-11-09 08:36:27 UTC,"Hello,
this bug report is quite old, do you still have this issue with the nvidia driver with latest kernel?
Thanks"
1741671,2018-01-15 21:22:36 UTC,Bug and workaround https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1741671/comments/14 confirmed on older NVidia ION machine with nvidia-340 on kernel 4.13.0-26.
1741671,2018-01-11 20:54:52 UTC,"going back to 4.10 works. Otherwise, everything appears as normal except I can't login to any of my user accounts (local machine, ubuntu usernames). Logging in appears to work, and then I'm back to the login screen again."
1741671,2018-01-11 20:46:21 UTC,"nVidia GeForce GTX 750Ti
Ubuntu 16.04 LTS Desktop amd64"
1741671,2018-01-11 18:42:35 UTC,This is really bad for one of my computers.
1741671,2018-01-11 09:00:31 UTC,I also have a Geforce 9800 GT and am equally frustrated by the apparent gpu driver vs latest linux kernel conflict.  This may fall on nvidia to update their drivers to include a 4.13 patch.  Last update for 304.104 was September 2017.
1741671,2018-01-11 08:50:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741671,2018-01-11 08:36:19 UTC,Resorted to boot with old kernel image from GRUB menu as a workaround. I hope this gets fixed soon.
1741671,2018-01-11 04:39:57 UTC,"Confirmed!
Same as previous user."
1741671,2018-01-10 18:35:15 UTC,Confirmed!
1741671,2018-01-10 16:41:25 UTC,Same as previous user.
1741671,2018-01-12 23:31:21 UTC,"Looks like it's already been fixed in xenial-proposed**. As a workaround until the new version appears in the main repos, open a terminal (Ctrl + Alt + T) and type:"
1741671,2018-01-10 14:30:23 UTC,Same problem (as determined by automated reporting which dumped me here).  Occurred during the Meltdown Security update of 16.04.03 install to Kernel 4.13.
1741671,2018-01-10 14:13:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741671,2018-01-13 06:17:59 UTC,Thank you - I can confirm that installing nvidia-340 from xenial-proposed resolved this for me.
1741671,2018-01-13 06:20:07 UTC,Possible duplicate of #1724872.
1741671,2018-01-13 09:21:33 UTC,"Martin's solution worked for me on 16.04.3 LTS with kernel 4.13.0-26.29~16.04.2 giving me nvidia-340 340.104-0ubuntu0.16.04.1
Thx!"
1741671,2018-01-13 11:44:00 UTC,"Martin's solution worked for me on 16.04.3 LTS with kernel 4.13.0-26.29~16.04.2 giving me nvidia-340 340.104-0ubuntu0.16.04.1
Thx! Grazie"
1741671,2018-01-13 18:02:31 UTC,Martin's solution worked for me on 16.04.3 LTS
1741671,2018-01-13 19:13:53 UTC,Confirmed!
1741671,2018-01-13 21:29:13 UTC,Martin's solution solves it for me on Ubuntu 16.04.3
1741671,2018-01-14 12:37:46 UTC,I solved the 340.120 issue with kernel 4.13.0-26-generic Ubuntu 16.04.3 LTS ....
1741671,2018-01-15 07:07:16 UTC,I fixed a problem using this commands:
1741671,2018-01-11 23:46:07 UTC,"Started having the same issues today after updating to the linux-image-4.13.0-26-generic.
Had to remove the binary driver, and switch to the X.Org version temporarily."
1741671,2018-01-16 22:29:20 UTC,Martin's solution worked for me
1741677,2018-01-06 19:50:20 UTC,"This bug notes that problem exists, nothing more. It's ofcourse upstream."
1741677,2018-01-06 19:19:04 UTC,"Same on 16.04 LTS, 17.04, 17.10 and 18.04 LTS."
1741677,2018-01-06 19:39:10 UTC,Why reporting stuff like that in Ubuntu bug tracker as a package bug?! It's an upstream feature request.
1741677,2018-01-06 20:06:33 UTC,"The reason why I'm asking is that noting that the ""problem"" exists here in Ubuntu bug tracker as a package bug seems to be an act of questionable usefulness to me."
1741677,2018-01-06 20:13:11 UTC,"I understood you, Yury.
Thanks a lot for your efforts on Midnight Commander. It is great program for daily use. It stays stable, fast and reliable."
1741677,2018-01-06 20:22:59 UTC,"No problem, you're welcome and thanks!"
1741683,2018-07-12 06:32:03 UTC,"I vote for A
We can it do step by step. The first step in Tango, graying out are nice once you get used to it. We only need to tweak the experiences for first time users.
An additional overlay text ""configure headphones"" will do the trick.
Please not that we don't have tooltips with touch devices."
1741686,2018-01-06 21:08:51 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1741688,2018-01-07 12:09:49 UTC,"I copy past my answer on the KiCad forum,"
1741693,2020-01-26 21:46:31 UTC,The bug has been closed via the following commit(s):
1741693,2020-01-26 21:25:17 UTC,The bug has been referenced in the following commit(s):
1741693,2020-01-26 21:25:03 UTC,need bug 706412 so we can remove 1.1.0
1741693,2020-01-26 20:24:20 UTC,The bug has been referenced in the following commit(s):
1741693,2020-01-26 20:23:55 UTC,"install/test, commit, same as always."
1741693,2020-01-26 14:39:25 UTC,The real fun is that flake8/pep8 has no value for gentoo users.
1741693,2020-01-26 13:35:04 UTC,Please describe your process of stabilising 1.1.0 in commit a1c41da8f24305702c1e29b4fc3b69b78d6977ec.
1741693,2020-01-26 13:23:27 UTC,This is fun.
1741693,2018-01-06 21:46:58 UTC,"yep, hacking is kinda bad about it, I've taken to patching it out of the ebuilds test-requirements.txt as a mater of course."
1741693,2018-01-05 21:54:45 UTC,"hacking-0.10.3.ebuild:	~dev-python/pep8-1.5.7[${PYTHON_USEDEP}]
hacking-0.13.0.ebuild:	~dev-python/pep8-1.5.7[${PYTHON_USEDEP}]
hacking-0.9.2.ebuild:RDEPEND=""~dev-python/pep8-1.5.6[${PYTHON_USEDEP}]
hacking-0.9.6.ebuild:RDEPEND=""~dev-python/pep8-1.5.6[${PYTHON_USEDEP}]"
1741693,2018-01-06 13:05:48 UTC,Also:
1741696,2019-09-18 04:17:32 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1741696,2019-07-19 20:54:04 UTC,Thanks for filing the bug.
1741700,2018-01-07 02:47:46 UTC,Checked and found the same behaviour on Ubuntu. Hence rI don't think it's a bug in Linux Mint.
1741700,2018-01-07 05:09:46 UTC,A bit more information: Seems like this package (texinfo) isn't installed in Debian by default.
1741704,2018-02-05 11:49:44 UTC,"To clarify, this happens when the focus animation is set to fade and windows overlap one another."
1741704,2018-01-21 19:27:10 UTC,Here's a video: https://youtu.be/0awlKwX6rcE
1741706,2018-01-07 07:11:29 UTC,"It looks there is already a Cue type JUMP definition (in class Cue, enum CueType -- src/librray/dao/cue.h). I am wondering if this somehow serves a similar purpose as the proposal. However, I was not able to find any references to the JUMP cue type in the code."
1741706,2018-01-08 08:37:40 UTC,"Please someone correct me if I'm wrong, but JUMP cue point was intended to be: when track reaches point A, jump to point B on the same track."
1741706,2018-01-08 13:56:42 UTC,"It was:
https://bugs.launchpad.net/mixxx/+bug/673515
https://bugs.launchpad.net/mixxx/+bug/730577"
1741706,2018-01-08 15:31:10 UTC,"Yes, this is very similar to https://bugs.launchpad.net/mixxx/+bug/673515. The only difference is it affects the main decks, not just the AutoDJ. However, please feel free to mark it as duplicate."
1741706,2018-01-08 16:15:37 UTC,Is there a use-case to use these cue points without Auto DJ?
1741706,2018-01-09 02:03:19 UTC,there is a similar function in traktor (its called fade-in/fade-out cue points). my guess is this was added to help automating the process (vs the hands-on type of users).
1741706,2018-01-09 04:55:53 UTC,"It would be pretty nice to have an ""align cue-points"" function that allows you to select a cue-point on deck X, and then another cue point on deck Y, and have Deck Y shifted into alignment with deck X immediately (not waiting for the first cue to hit)."
1741706,2018-01-09 07:06:46 UTC,"Ah I understand, so this is no duplicaze, right?"
1741706,2018-01-11 06:44:38 UTC,"Yes, this affects two tracks, the first one having the fade-out cue and the second with the fade-in cue point."
1741710,2018-01-07 07:08:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1741710,2018-01-07 11:22:26 UTC,Unable to reproduce here in a VM with latest daily.
1741712,2018-01-07 07:57:28 UTC,"Unless it is in a Kubuntu specific tool not translated by KDE, then localisation for KDE applications is handled upstream at:"
1741712,2018-01-07 08:08:52 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1741715,2018-01-08 08:47:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741715,2018-01-08 08:48:49 UTC,"Thanks for the links. You can find the official page for that crash (they are all the same crash) here:
  https://errors.ubuntu.com/problem/3a8ac3d35871bbe4e73e3e32a2bb33ed33894114"
1741715,2018-01-08 08:51:41 UTC,This appears related to bug 1710245. Only slightly different.
1741718,2020-11-10 14:33:33 UTC,Verified same issue occurs on latest qemu.
1741720,2020-09-19 04:52:49 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1741722,2018-01-07 11:50:27 UTC,"I tried this on the latest 18.04 daily, with no crash or freeze. What version are you testing?"
1741723,2020-07-09 08:28:44 UTC,"Reviewed:  https://review.opendev.org/739275
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=2e500d38c2f4c6779dd06f5a841e1b268055e7ab
Submitter: Zuul
Branch:    master"
1741723,2019-09-27 14:30:56 UTC,"Change abandoned by Alex Kavanagh (tinwood) (<email address hidden>) on branch: master
Review: https://review.opendev.org/685331
Reason: neutron-gateway isn't actually an API charm and so doesn't need this change!"
1741723,2018-01-07 18:40:22 UTC,"charm-helpers:
https://github.com/juju/charm-helpers/pull/84"
1741723,2018-01-08 21:30:22 UTC,Modified to include an ability to supply a jinja2 template as a drop-in and use the same variables as in policy.json template file.
1741723,2018-01-30 17:38:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539269"
1741723,2018-02-02 09:39:14 UTC,"Reviewed:  https://review.openstack.org/538688
Committed: https://git.openstack.org/cgit/openstack/charms.openstack/commit/?id=1ca4bd0ab941f6c7aebf86bdf5ff47fdc1d2d3e2
Submitter: Zuul
Branch:    master"
1741723,2018-03-08 23:52:57 UTC,openstack-dashboard is a bit unique as it needs to have many per-service policy files and they need to be in sync with individual policy files for other charms.
1741723,2019-01-07 11:44:26 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/531614
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.
Feel free to restore it again if you want to pick up and continue the work."
1741723,2020-07-07 11:24:02 UTC,"Reviewed:  https://review.opendev.org/738745
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=d21648e67106c48e222a3f698eeb2255593326dd
Submitter: Zuul
Branch:    master"
1741723,2020-07-07 10:20:59 UTC,"Reviewed:  https://review.opendev.org/739274
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=7bec3ddee6163a566d2a9c0aaadacc1be27be9a7
Submitter: Zuul
Branch:    master"
1741723,2019-01-22 12:31:50 UTC,A customer asked asked making changes in the policy.json on the cinder and openstack-dashboard charms to enable consistency groups and consistency group snapshots.
1741723,2020-07-03 18:27:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/739274"
1741723,2019-11-07 18:53:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/693407"
1741723,2019-11-07 15:59:28 UTC,"Reviewed:  https://review.opendev.org/693162
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=98de623820f58dc562ba770431e3464193d15a27
Submitter: Zuul
Branch:    master"
1741723,2019-11-06 13:31:48 UTC,"Note that swift software doesn't (yet) support the oslo.policy Enforcer class, which means that policy.d overrides aren't possible with it (yet)."
1741723,2019-11-06 11:49:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/693162"
1741723,2019-10-14 19:56:17 UTC,"Reviewed:  https://review.opendev.org/685982
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=6ee32006e54f67e7415a042f00b3489ddbcd113a
Submitter: Zuul
Branch:    master"
1741723,2019-10-08 14:22:43 UTC,"Change abandoned by Alex Kavanagh (tinwood) (<email address hidden>) on branch: master
Review: https://review.opendev.org/686006
Reason: OpenStack dashboard requires a much more complex set of policy overrides than the system in charm-helpers can support.  It'll require a completely different approach, but can be based on the existing code."
1741723,2019-10-08 08:26:35 UTC,"Reviewed:  https://review.opendev.org/685973
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=97152f55a1f045484ad3fde69a99a84fce8f349b
Submitter: Zuul
Branch:    master"
1741723,2019-10-08 08:26:13 UTC,"Reviewed:  https://review.opendev.org/679420
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=186769cc056f4306111c1c26e899dd4697ff468f
Submitter: Zuul
Branch:    master"
1741723,2019-10-08 08:24:30 UTC,"Reviewed:  https://review.opendev.org/685376
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=697ca00bcf29c6a6f3dbca4b13c16a87804592ab
Submitter: Zuul
Branch:    master"
1741723,2019-10-08 08:23:55 UTC,"Reviewed:  https://review.opendev.org/685726
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=f7f6fa295c82ea88953ec08695c68c04694fc1a5
Submitter: Zuul
Branch:    master"
1741723,2019-10-01 14:38:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/685982"
1741723,2019-10-01 13:56:54 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/685973"
1741723,2019-11-21 17:06:19 UTC,"Reviewed:  https://review.opendev.org/689469
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=1b1e7c583c68a166ba2b826b7fd2606e10d358ce
Submitter: Zuul
Branch:    master"
1741723,2020-07-03 18:34:53 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/739275"
1741723,2019-11-22 09:45:32 UTC,"Reviewed:  https://review.opendev.org/693407
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=5e3e942cd88db2fe6c15fa2182a64796944b9b51
Submitter: Zuul
Branch:    master"
1741723,2020-04-27 09:08:34 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: master
Review: https://review.opendev.org/539269"
1741726,2018-01-25 20:14:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538018"
1741726,2018-01-25 06:02:13 UTC,"yes, I think I missed an important part of it. as it does not have any issue with sqllite. But there are issue with mysql database."
1741726,2018-01-24 10:31:01 UTC,Emmm... I think the description is not fully correct. I tried to create an artifact on my devstack with dozens of custom fields of all types and then I was able to delete it without any issue.
1741727,2018-01-09 21:35:51 UTC,The package has been published and the bug is being set to Fix Released
1741727,2018-01-09 20:10:00 UTC,This bug was fixed in the package linux - 4.4.0-108.131
1741737,2019-03-11 02:56:21 UTC,"Hi, I can't reproduce this problem on Inkscape 0.92.4, it doesn't change into a single color fill for me."
1741737,2018-01-08 00:03:04 UTC,Thanks for your reply.
1741737,2018-01-07 15:54:24 UTC,thank you for taking the time to issue a report.
1741737,2019-05-13 03:12:38 UTC,"Closing as there has been no response for 30 days. If you have a similar issue with the latest Inkscape version, please file a new bug here: https://inkscape.org/report. Thank you!"
1741758,2018-01-07 17:31:36 UTC,"Suse Linux released a new samba-krb-printing package, as CUPS still doesn't resolv this problem : https://bugzilla.suse.com/show_bug.cgi?id=899118"
1741765,2018-03-05 17:45:37 UTC,I think Kubuntu has never had the try option.  Never understood why.
1741765,2018-01-07 17:08:57 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1741767,2018-01-24 12:59:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741767,2020-12-04 04:34:10 UTC,"Dear Bug Submitter,"
1741767,2020-11-19 19:09:13 UTC,Are people still seeing this? I do not observe this behavior on Kubuntu 20.10 with muon 5.8.0. Could it have been a packaging issue just on Neon?
1741767,2019-08-20 15:52:35 UTC,"I confirm it to be happening on Kubuntu 18.04 LTS
But Muon is flawless on KDE Debian Buster."
1741767,2019-04-15 10:47:22 UTC,I feel the need to resurrect this bug report since the problem seems to have resurfaced (actually quite a while ago).
1741767,2019-04-01 18:33:04 UTC,Also seen on 19.04 beta.
1741767,2018-03-18 14:50:18 UTC,Launched Muon from terminal
1741767,2018-02-22 09:29:01 UTC,"Git commit e4f2a1f79741c930802acab7150fa6b96240bed6 by Carlo Vanini.
Committed on 22/02/2018 at 09:27.
Pushed by vanini into branch 'master'."
1741767,2018-02-19 19:59:32 UTC,"Thank you for reply, Carlo!"
1741767,2018-02-19 16:31:46 UTC,"Muon checks the modification time of `/var/lib/apt-xapian-index/update-timestamp`, `/var/lib/dpkg/status` and `/var/cache/apt/pkgcache.bin`. Only if the timestamp of the index is older than any of the other two, then the index is rebuilt."
1741767,2018-02-14 20:24:12 UTC,"Steps to reproduce:
1. Install Muon on Ubuntu 16.04 LTS and launch it
2. Click ""Check for updates""
3. Wait for ""Rebuilding Search Index"" to finish
4. After some time open Muon again (without 'apt-get update', 'aptitude update').
5. Get 'Rebuilding search index' message with background process /usr/sbin/update-apt-xapian-index and high CPU load and high temperature as the result."
1741767,2018-02-12 21:10:23 UTC,"Dear maxy, could you please look to this bug?"
1741767,2018-02-12 20:59:36 UTC,"Its unbelievable - I opened Muon, tried to make search, then it Rebuilt index, I can't make new search query.
I closed Muon, entered failed (second) query. It shown results. But Rebuilding Search Index again."
1741767,2020-12-05 07:20:19 UTC,"Contrary to earlier experiences, I do not see this behaviour anymore with Muon 5.8.0 under KDE Neon 5.19.4 (based on Ubuntu 18.04) and 5.20.4 (based on Ubuntu 20.04)."
1741767,2020-12-05 10:22:22 UTC,"Apologies, I incorrectly set the status to 'reported' when in actuality the bug is most likely gone by now! Therefore setting the status to 'resolved, worksforme'."
1741768,2018-03-31 11:51:21 UTC,Still fails with 59.0.2+build1-0ubuntu0.16.04.1. Does anyone care about their users' security at Canonical?
1741768,2018-01-09 15:15:25 UTC,"Hi, I'm one of the Firefox developers working on our FIDO U2F device support."
1741768,2018-01-09 15:27:55 UTC,"Hi jc-moz,"
1741768,2018-01-24 17:57:27 UTC,Still fails with 58.0+build6-0ubuntu0.16.04.1.
1741768,2018-08-22 21:27:57 UTC,"Still fails on Ubuntu 18.04.1 with 61.0.1+build1-0ubuntu0.18.04.1, while it works under chromium-browser 68.0.3440.106-0ubuntu0.18.04.1."
1741768,2020-01-30 23:59:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741768,2020-01-31 00:03:01 UTC,"Tested this today, via the github site, and both authentication and the registration of a new key fails. Logging I can find related to this in /var/log/syslog is:"
1741768,2020-01-31 13:23:00 UTC,"That does imply AppArmor is the issue with that denial; `authenticator-rs` requires hidraw access to the relevant devices. https://github.com/amluto/u2f-hidraw-policy is the package used by other linuxes, I don't know the equivalent for Debian."
1741770,2018-01-09 03:30:08 UTC,This change was made by a bot.
1741771,2018-01-07 17:18:20 UTC,thanks don't really understand these things
1741775,2018-01-07 19:22:02 UTC,"This situation can only arise on a system which already had systemd-resolved configured at install time, then had resolvconf installed on top of it.  The real question is, why are you installing resolvconf? It should no longer be needed in 17.10."
1741775,2018-01-07 20:55:53 UTC,I searched through /var/log/apt history files and resolvconf gets sucked in as a dependency when I install the proprietary vpn-unlimited application from Keepsolid.
1741775,2018-01-08 18:40:18 UTC,"On Sun, Jan 07, 2018 at 08:55:53PM -0000, Warren wrote:

> I searched through /var/log/apt history files and resolvconf gets sucked
> in as a dependency when I install the proprietary vpn-unlimited
> application from Keepsolid.
"
1741781,2020-05-10 09:23:20 UTC,I can still confirm this bug with 2.3 alpha on ubuntu Xenial
1741781,2018-01-09 21:56:04 UTC,I notice also that after restart in fullscreen mode the first key press for F11 is ignored. Maybe this is related.
1741797,2018-01-08 08:18:18 UTC,"The attachment ""updated seconds value using milliseconds"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1741797,2018-01-08 04:49:29 UTC,"this patch makes the symptoms occur way less frequently.  The crashes still happen(though I haven't been able to confirm it's the same crash) but on the upside, the debug message gives a value other than 0 for seconds now."
1741797,2018-01-08 02:04:35 UTC,with debug symbols:
1741817,2018-01-19 08:22:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535665"
1741817,2018-01-17 14:23:04 UTC,"Confusing state is caused by nova-compute. When nova-compute restart ,it will set all instances with task_state[rebuilding] to error. And then nova-compute handle rpc to rebuild, and raise this error. I think this is proper because nobody know instance's true state with state rebuilding in db. I will optimize the process of exception handling."
1741818,2018-01-18 08:20:19 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2023
1741818,2018-01-08 05:03:51 UTC,Thanks for reporting the issue.
1741819,2018-01-08 06:52:18 UTC,https://github.com/juju/juju/pull/8266
1741827,2018-01-14 11:01:45 UTC,"I'm seeing the same results:
docker logs 229ca1a9e9d7"
1741844,2018-01-23 21:51:38 UTC,"I agree that this is undesirable, but I see no way to avoid this for CA put w/o callback.  The protocol doesn't define a completion ack. message.  So the fact that the client gets the CA exception message at all is a side-effect of the second get.  And handling of exception message has always been a weak point of CA implementations."
1741844,2018-09-05 11:36:36 UTC,"Core Group review at ESS: You should get any exceptions from the ca_put() before the second ca_get() [new value] returns, so MD's logic is probably sufficient."
1741846,2018-01-12 12:47:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741846,2021-01-09 22:44:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1273534, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1741860,2019-06-24 14:59:49 UTC,"------- Comment From <email address hidden> 2019-06-24 10:49 EDT-------
Yes. kdump-tools.cfg file still carries the offset of ""@128M"" in it while the request
here is to drop this so as to fallback to kernel default. Note that the kernel
default right now is 128M but that may change"
1741860,2019-11-11 15:56:41 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1741860,2019-11-11 15:57:55 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.3
1741860,2020-01-14 14:18:10 UTC,"Hello bugproxy, or anyone else affected,"
1741860,2020-01-16 18:20:15 UTC,"------- Comment From <email address hidden> 2020-01-16 13:15 EDT-------
With kdump-tools version 1:1.6.3-2~16.04.2 on Xenial,
crashkernel parameter offset is dropped (in
/etc/default/grub.d/kdump-tools.cfg file) making sure
the default offset enforced by the kernel is used."
1741860,2019-06-24 14:06:48 UTC,Is this issue even reproducible on Disco or Eoan? Looks like there are fixes that could have landed for this issue in 18.10. Can IBM please confirm this is an issue in Disco and Eoan?
1741860,2019-04-04 11:48:05 UTC,"Hi Mamatha, well, as you can see from Launchpad comment #6:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1741860/comments/6
we are still waiting for the feedback from IBM about the validation mentioned in comment #5:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1741860/comments/5"
1741860,2018-08-07 06:09:45 UTC,"------- Comment From <email address hidden> 2018-08-07 02:01 EDT-------
(In reply to comment #10)

> It has already been changed to @128M on bionic. For 18.10, I will drop, and
> consider backporting it to previous versions if necessary. I will backport
> the @128M change to xenial and artful as soon as the versions in -proposed
> move to -updates or are dropped.
>
> Cascardo.


Sure I will validate and update the bug ASAP.."
1741860,2018-11-12 15:27:47 UTC,Were you able to perform the validation described in comment #5?
1741860,2019-11-11 15:56:26 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1.3
1741860,2018-03-08 16:33:27 UTC,"It has already been changed to @128M on bionic. For 18.10, I will drop, and consider backporting it to previous versions if necessary. I will backport the @128M change to xenial and artful as soon as the versions in -proposed move to -updates or are dropped."
1741860,2018-02-28 09:41:01 UTC,Can you verify using makedumpfile + kdump-tools from artful-proposed?
1741860,2018-02-28 06:29:55 UTC,"------- Comment From <email address hidden> 2018-02-28 01:27 EDT-------
*** Bug 163566 has been marked as a duplicate of this bug. ***"
1741860,2018-01-22 18:31:23 UTC,"------- Comment From <email address hidden> 2018-01-22 13:19 EDT-------
(In reply to comment #0)

> ---Problem Description---
> A default offset of 128MB is enforced for crashkernel by kdump-tools utility
> overriding the kernel default.
>
> While the kernel default offset for crashkernel is also 128MB, that may
> change
> and the right thing to do would be to let the kernel decide on the offset of
> crashkernel in the default scenario..
>
> Get rid of ""@128M"" in kdump-tools.cfg file
>
>
> Contact Information = <email address hidden>
>
> ---uname output---
> na
>
> Machine Type = na
>
> ---Debugger---
> A debugger is not configured
>
> ---Steps to Reproduce---
>  # cat /etc/default/grub.d/kdump-tools.cfg
> GRUB_CMDLINE_LINUX_DEFAULT=""$GRUB_CMDLINE_LINUX_DEFAULT
> crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:
> 4096M@128M""
"
1741860,2019-04-04 11:19:27 UTC,"------- Comment From <email address hidden> 2019-04-04 07:18 EDT-------
Any update on this? is this fix is integrated?"
1741860,2019-10-25 13:01:58 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.3) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1741860,2020-01-29 03:50:17 UTC,This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.2
1741860,2019-06-24 11:59:32 UTC,"------- Comment From <email address hidden> 2019-06-24 07:52 EDT-------
Sorry. Couldn't validate this on 18.10 -proposed. Can we have it on
eoan-proposed for validation and SRU to stable release.."
1741860,2019-07-24 22:04:40 UTC,"Hi Hari and Mamatha,"
1741860,2019-07-25 06:29:26 UTC,"------- Comment From <email address hidden> 2019-07-25 02:21 EDT-------
(In reply to comment #20)
[...]

> If everything looks okay on your end, I will proceed with SRU'ing this fix
> to the other Ubuntu releases.
"
1741860,2019-07-25 19:51:16 UTC,Attaching .debdiff to this comment for SRU sponsorship consideration into Xenial.
1741860,2019-07-25 19:51:49 UTC,Attaching .debdiff to this comment for SRU sponsorship consideration into Bionic.
1741860,2019-07-25 19:52:21 UTC,Attaching .debdiff to this comment for SRU sponsorship consideration into Disco.
1741860,2019-07-25 19:52:48 UTC,Attaching .debdiff to this comment for SRU sponsorship consideration into Eoan.
1741860,2019-07-26 00:22:22 UTC,"The attachment ""makedumpfile_1.6.3-2_16.04.1ubuntu1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1741860,2019-10-25 11:00:32 UTC,"------- Comment From <email address hidden> 2019-10-25 06:56 EDT-------
On disco, with kdump-tools/makedumpfile package version 1:1.6.5-1ubuntu1.3
kernel offset is being used by default as expected."
1741860,2019-08-28 13:43:22 UTC,"Hello bugproxy, or anyone else affected,"
1741860,2019-08-28 13:50:31 UTC,"Hello bugproxy, or anyone else affected,"
1741860,2019-08-29 11:50:13 UTC,"------- Comment From <email address hidden> 2019-08-29 07:43 EDT-------
I verified that the offset (looking at /etc/default/grub.d/kdump-tools.cfg file) is removed
on -bionic with kdump-tools package version 1.6.5-1ubuntu1~18.04.2"
1741860,2019-08-20 16:24:14 UTC,This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu1
1741860,2019-10-23 13:56:35 UTC,"Hello bugproxy, or anyone else affected,"
1741860,2019-10-23 13:59:54 UTC,"Hello bugproxy, or anyone else affected,"
1741860,2019-08-29 13:00:47 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1741860,2019-10-01 15:07:45 UTC,"On 9/30/19 7:47 AM, Andrew Cloke wrote:

> Following f2f discussions, next step is to re-upload new version of
> makedumpfile.
>
"
1741860,2019-09-30 13:47:06 UTC,"Following f2f discussions, next step is to re-upload new version of makedumpfile."
1741860,2019-09-17 13:55:36 UTC,The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.
1741860,2019-10-23 15:31:47 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1741860,2019-08-30 06:19:57 UTC,"------- Comment From <email address hidden> 2019-08-30 02:18 EDT-------
Resolved with makedumpfile/kdump-tools version 1.6.5-1ubuntu1.1 on Disco"
1741863,2018-01-08 10:08:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1741875,2018-01-12 16:19:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/533233"
1741875,2018-06-06 11:20:55 UTC,"Change abandoned by Christian Schwede (<email address hidden>) on branch: master
Review: https://review.openstack.org/533233
Reason: No longer needed."
1741875,2019-07-08 17:23:16 UTC,I have tested and verified that this is no longer an issue when using config-download on >= Queens.
1741883,2020-01-25 12:03:18 UTC,Fixed a few versions ago. Closing.
1741887,2018-01-08 20:18:56 UTC,Next kernel is ready:
1741887,2018-03-08 09:18:22 UTC,I noticed this bug was still open.  I built a test kernel with a revert of commit c6c70f4455d.
1741887,2018-01-08 21:03:40 UTC,Looks like the failure there is due to the following commit in the linux kernel:
1741887,2018-01-08 20:59:00 UTC,Kernel in #27 was good.
1741887,2018-01-08 20:47:52 UTC,Next kernel is ready:
1741887,2018-01-08 20:36:06 UTC,Kernel in #25 is good.
1741887,2018-01-08 20:32:10 UTC,Next kernel is ready:
1741887,2018-01-08 20:22:27 UTC,Kernel in #23 is good.
1741887,2018-01-08 20:07:45 UTC,Kernel in #21 is bad
1741887,2018-01-08 19:52:20 UTC,Kernel in #19 is bad.
1741887,2018-01-08 12:40:38 UTC,Just tried with v4.15-rc7 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ and the problem persists.
1741887,2018-01-08 15:26:36 UTC,I started a kernel bisect between v4.10 final and v4.10-rc1. The kernel bisect will require testing of about 13 test kernels.
1741887,2018-01-08 15:34:35 UTC,Kernel from #2 is good.
1741887,2018-01-08 15:47:15 UTC,Next kernel is ready:
1741887,2018-01-08 15:51:27 UTC,Kernel from #4 is good.
1741887,2018-01-08 16:04:29 UTC,Next kernel is ready:
1741887,2018-01-08 16:08:05 UTC,kernel from #6 is bad.
1741887,2018-01-08 16:21:25 UTC,Next kernel is ready:
1741887,2018-01-08 16:25:54 UTC,kernel from #8 is good.
1741887,2018-01-08 16:37:13 UTC,Next kernel is ready:
1741887,2018-01-08 17:36:14 UTC,kernel in #10 is bad.
1741887,2018-01-08 18:01:46 UTC,Next kernel is ready:
1741887,2018-01-08 19:58:36 UTC,Next kernel is ready:
1741887,2018-01-08 18:29:29 UTC,"comment #14 should read the ""Next"" test kernel and not ""first""."
1741887,2018-01-08 18:07:02 UTC,Kernel in #12 is good.
1741887,2018-01-08 18:28:18 UTC,"I built the first test kernel, up to the following commit:
601109c5c74a10e6b89465cb6aa31a40d1efc8e3"
1741887,2018-01-08 18:47:09 UTC,Kernel in #14 is good.
1741887,2018-01-08 19:00:30 UTC,Next kernel is ready:
1741887,2018-01-08 19:05:33 UTC,Kernel in #17 is bad
1741887,2018-01-08 19:44:10 UTC,f1ef09fde17f9b77ca1435a5b53a28b203afb81c was good.
1741890,2018-01-08 12:51:42 UTC,Fixed upstream in FileZilla version 3.30.0
1741892,2018-01-08 13:14:33 UTC,"Also, the error when pushing to such a repo could maybe be improved ? ""fatal: remote error: Permission denied."" isn't super helpful."
1741900,2018-09-03 08:00:59 UTC,I've filed https://bugs.launchpad.net/snapcraft/+bug/1790455 for the CI case.
1741900,2018-09-03 07:58:34 UTC,I just saw this:
1741902,2018-01-12 22:10:58 UTC,"As I already mentioned, I am aware that nautilus is triggering the problem. However, no program should be able to bring down the desktop by doing bad UI operations. Period."
1741902,2018-01-11 17:52:40 UTC,"Well, I don't know how drag & drop works so I can not say that it is bug in X server. I would start by reporting / re-assigning this bug to nautilus especially if it is only app that causes this problem."
1741902,2018-01-09 02:24:51 UTC,I thought Metacity is the component that has to deal with inter-application interaction. Seems I am wrong?
1741902,2018-01-08 14:07:08 UTC,Please add critical as bug results in system state forcing users to hard reboot with potential data loss.
1741902,2018-01-08 17:34:41 UTC,Why do you think that Metacity is the one who freezes? Have you tried other window managers and/or sessions and this happens only with Metacity?
1741902,2018-01-15 21:47:00 UTC,"From your bug:
""Windows can still be bought to front by clicking them, but never gain focus and no application (besides nautlilus I guess, which is stalled) receives clicks or keystrokes."""
1741908,2018-01-08 15:08:00 UTC,This issue seems to be limited to a GNOME/Wayland session. The content window persists as expected in a GNOME/Xorg session.
1741908,2018-01-23 08:26:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741911,2018-01-11 11:47:05 UTC,"Reviewed:  https://review.openstack.org/532741
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=604bbe5f339a1dccf06bc655b9c33ec170587137
Submitter: Zuul
Branch:    master"
1741911,2018-01-10 17:39:59 UTC,"This is currently breaking the Magnum gate, see [1]. I've been looking at the code, and what I've found is:"
1741911,2018-01-10 17:53:14 UTC,"Yeah, this is how we fixed in pifpaf and gnocchiclient. Just pass a string to DriverCommandManager."
1741911,2018-01-10 21:28:39 UTC,What behavior do you expect when the namespace is set to None? Just that no plugins are loaded?
1741911,2018-02-08 17:35:44 UTC,This issue was fixed in the openstack/magnum 6.0.0 release.
1741913,2020-10-15 14:47:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741913,2020-10-15 14:10:38 UTC,https://github.com/twisted/twisted/commit/169fd1d93b7af06bf0f6893b193ce19970881868
1741913,2020-10-15 14:02:10 UTC,https://twistedmatrix.com/trac/ticket/9410
1741913,2020-10-15 14:01:01 UTC,Same situations observed on MAAS (DEB install):
1741913,2019-09-19 11:57:08 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1741913,2020-10-15 17:49:02 UTC,# Test package available on my PPA:
1741913,2020-10-20 16:53:12 UTC,@MAAS - let's monkey patch Twisted with the fix from upstream
1741913,2020-10-15 20:09:22 UTC,"With this test package I want to see if the 'traceback' will disapear and if this will also solve the MAAS UI telling ""X rack controllers are not yet connected to the region. Visit the rack controllers page for more information"" despite that everything else look good (network, firewall rules, nc test, ...)"
1741913,2020-10-15 14:13:11 UTC,It also seems like this has the effect for the impacted user I'm currently helping to always have this message in the UI:
1741923,2019-09-19 14:46:37 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1741929,2019-01-03 18:20:01 UTC,Just came across this today in 3.0.
1741931,2019-12-10 19:36:53 UTC,I don't believe you'll ever get this bug fixed by just complaining about it here. Get someone assigned or do something yourself. That's how I think open source should work. A patch is above.
1741931,2019-12-10 15:24:49 UTC,"```
(evolution:3214): module-plugin-lib-WARNING **: 16:19:11.599: can't load plugin '/usr/lib/evolution/plugins/liborg-jylefort-mail-notification.so': /usr/lib/evolution/plugins/liborg-jylefort-mail-notification.so: undefined symbol: camel_message_info_uid"
1741931,2019-12-10 14:20:19 UTC,"Same problem here
Ubuntu Mate 18.04"
1741931,2019-12-07 23:45:51 UTC,"@evanblack- I had stopped using Thunderbird a while back and went to online mail suites. I have recently started to try Evolution because of the integrations it offers with low overhead. It is unfortunate that such a basic feature is not functioning for so long. Ubuntu replaced TB now with Evolution, so hopefully we will see some of these core functions returned."
1741931,2019-08-07 18:15:41 UTC,"Yes, see above. It’s not in the repos though."
1741931,2019-08-07 17:24:56 UTC,Has anyone found a solution or a workaround?
1741931,2018-05-07 16:51:46 UTC,And the mail-notification package...
1741931,2018-05-07 16:51:05 UTC,"I just noticed that my patch file is kinda back to front. So if you decide to use it, it will tell you that the file is already patched. But if you specify the option -R (""patch -R -p0 < mail-notification.diff""), things should work. My bad xD
Anyways, here are patched deb packages."
1741931,2018-05-07 16:18:35 UTC,"Lol for the ""I am very skilled""
I'm (obviously) also not very skilled, at least I never really learned how
to create patch files correctly. But at least I know for a fact that the
patch I created was for the plugin source, not for the shared object file
which you tried to patch. I think (don't quote me on this) that you have to
patch the source by going into the source main directory and running ""patch
-p0 < mail-notification.diff"". I can try creating a binary diff, just tell
me if you need it."
1741931,2018-05-07 00:14:23 UTC,"I meant to say ""not very skilled"" :)"
1741931,2018-05-07 00:13:34 UTC,"Hi Team,"
1741931,2018-02-08 20:25:43 UTC,"The attachment ""Fix old function names"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1741931,2018-05-29 08:08:38 UTC,"hi
i have ubuntu 18.04
mail-notification:
  Instalovaná verze: 5.4.dfsg.1-14ubuntu2
mail-notification-evolution:
  Instalovaná verze: 5.4.dfsg.1-14ubuntu2"
1741931,2018-02-08 19:29:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741931,2018-02-08 18:02:21 UTC,"It seems I'm onto something. I changed the source files I got from apt, and I get a new message saying that the symbol camel_message_info_message_id was unavailable. I think I might be able to fix this"
1741931,2018-08-02 10:27:49 UTC,"I have the same versions as Launchpad user marun1 above.
I'd also like to know if this will be fixed.
More than half a year has passed since the bug was reported."
1741931,2018-02-07 19:44:11 UTC,"I suspect the cause of this problem to be a function rename. I'm not 150% sure, but I think camel_message_info_uid got renamed to camel_message_info_get_uid. Can anyone confirm this? I tried recompiling the mail notification plugin but the build system is kinda broken and the source code I tried compiling is already 6 years old."
1741931,2018-01-25 18:52:35 UTC,"Same here. Also Ubuntu 17.10, same command line output"
1741931,2018-10-16 14:47:42 UTC,"Still broken as ever in ubuntu 18.04
With the lack of plugins for the latest thunderbird, evolution seems to be about the only real alternative."
1741931,2019-03-20 04:47:38 UTC,Any updates on this? Thanks.
1741931,2018-02-08 19:28:23 UTC,"Ok, chased those function names down and changed them all, and now the plugin loads successfully. However, a new error has arisen, which is that once I select ""evolution"" as the mail provider for mail-notification, it tries to embed a table with the available mail folders using a GtkSocket, which is not available when using wayland."
1741931,2019-12-07 20:02:32 UTC,Same as reported in most recent replies for me. Using 18.04 and the patches listed above are outdated thus do not correct the issues here.
1741935,2018-01-15 03:40:55 UTC,"I did the production release last week and it seems to have worked fine, so we are set with that preliminary."
1741935,2018-01-08 17:17:14 UTC,"Here's a ticket for today's 1PM discussion. I suspect we'll make individual tickets. The last bullet, for example, is a whopper."
1741935,2018-01-08 19:01:55 UTC,My notes from the call just now:
1741935,2018-01-15 20:06:48 UTC,Done: https://bugs.launchpad.net/karl4/+bugs?field.tag=distlist <https://bugs.launchpad.net/karl4/+bugs?field.tag=distlist>
1741948,2020-01-22 10:25:49 UTC,"Affects me too. Interestingly, it works sometimes, but sometimes not. I have not been able to track down what causes it to fail."
1741948,2020-01-24 18:21:05 UTC,I'll just put some notes here for future possible use.
1741948,2020-01-24 17:08:07 UTC,It seems the space is requested by the calendar widget. But this still has plenty of whitespace.
1741948,2020-01-24 10:20:32 UTC,"As far as I understand, this is not a problem with gnome-shell, unless one wants to remove all limitations."
1741948,2020-01-22 14:54:49 UTC,Just read that other bug. So this is a ten year old bug that nobody has bothered addressing. IMHO there is no reason for that limit. Everything Evolution would need to show with the side bar visible is still viewable with a smaller width. The limit seems completely arbitrary.
1741948,2020-01-22 14:42:44 UTC,"It is the ""side bar"". If this is visible, Evolution refuses to go below a certain width (which is just larger than half my screen). Then maximize-right does not work. How do I remove the size limit with the ""side bar"" active?"
1741948,2020-01-24 18:40:00 UTC,"That last Boolean value answers ""can this child be made smaller than its requisition""?"
1741948,2020-01-22 10:24:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741948,2018-06-25 17:16:10 UTC,This should be moved to gnome-shell instead; see https://bugzilla.gnome.org/show_bug.cgi?id=636416
1741948,2018-06-04 19:22:40 UTC,What is your screen size? I am afraid that the Evolution window needs a certain minimum width and if that width is more than 50% of your screen width this might fail? (Just a theory!)
1741956,2018-01-09 19:25:00 UTC,The package has been published and the bug is being set to Fix Released
1741956,2018-01-08 20:53:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741956,2018-01-09 19:11:00 UTC,This bug was fixed in the package linux-gcp - 4.13.0-1006.9
1741977,2017-08-14 12:59:18 UTC,"Do you still need a test for verification? Or do you have such hardware
yourself around somewhere?"
1741977,2017-06-05 19:09:13 UTC,"Description of problem:
Lack of USB3 xhci patch makes SANE quite unusable with USB3 hardware;
example with Fujitsu fi-6130 (theoretically fully supported by SANE):"
1741977,2017-06-05 19:11:14 UTC,"Created attachment 1285126
sane-backends-1.0.24-usb3-xhci.patch"
1741977,2017-06-05 19:15:08 UTC,"Created attachment 1285127
Patch for sane-backends.spec"
1741977,2017-06-05 19:21:34 UTC,Cross-filed ticket 01863749 on the Red Hat customer portal.
1741977,2017-06-06 07:44:23 UTC,"Hi Robert,"
1741977,2017-06-06 10:11:21 UTC,RHEL 7.5 would be fine.
1741977,2017-07-19 07:06:55 UTC,"Robert,"
1741977,2017-07-19 11:48:42 UTC,"Robert,"
1741977,2017-07-31 13:46:41 UTC,Upstream accepted manpage patch as commit 56398ead607d8bcb9deef7ca3f4d7f78478f1b4c
1741977,2017-08-14 12:54:21 UTC,"Created attachment 1313099
Proposed patch"
1741977,2017-08-14 12:58:25 UTC,"(In reply to Zdenek Dohnal from comment #8)

> I think it would be better to include upstream commit
> 1207ce5a40664c04b934bd0a6babbc1575361356 too. It uses environment variable
> SANE_USB_WORKAROUND, which setting to 1 enables workaround, which is in your
> proposed patch. It could minimize impact for other users. Its usage will be
> explained in man page sane-usb(5). Do you agree, Robert?
"
1741977,2017-07-19 07:15:55 UTC,Upstream issue for adding SANE_USB_WORKAROUND usage into man page https://alioth.debian.org/tracker/index.php?func=detail&aid=315792&group_id=30186&atid=410366
1741977,2017-08-14 13:03:31 UTC,"Yes, would you mind testing it? I do not have such HW unfortunately."
1741977,2019-07-08 16:32:06 UTC,I only started investigating but SANE_USB_WORKAROUND=1 does definitively not work for me. However so far I had not been able to communicate with the scanner (even after removing / reinserting USB cable) so I cannot be 100% sure if this is the same issue. The second part of the issue shown is 100% identical. Due to lack of experience with the xerox debug output it may be a different issue.
1741977,2018-08-31 18:41:37 UTC,We could count aproximately how many scanners are broken NOW since SANE 1.0.27 by disabling Linux USB3 workaround by default vs how many scanners could be broken by setting SANE_USB_WORKAROUND=1
1741977,2018-08-31 09:38:54 UTC,"@Mantas > The question is - is there a scanner out there that uses USB3 natively, and how would this workaround would affect those scanners? If there is no effect - workaround can be enabled by default."
1741977,2018-08-31 08:11:32 UTC,"I don't understand why Linux USB3 workaround which was added in version 1.0.25 is disabled by default in SANE 1.0.27 :(
Maybe Ubuntu developers should patch SANE to enable SANE_USB_WORKAROUND=1 by default on all computers with USB 3.x ports?
Anyone knows if SANE_USB_WORKAROUND=1 variable could cause any problems? If not, then why don't set this by default?"
1741977,2018-08-31 07:30:08 UTC,It seems the best solution for now is to add SANE_USB_WORKAROUND=1 line to /etc/environment:
1741977,2018-07-02 19:46:35 UTC,"Can also confirm the same problem with SCX-3400 model. Printing and scanning worked in all versions before 17.10, and scanning stopped working since then. I also have Debian Testing at home - it doesn't have this problem at all."
1741977,2018-05-10 20:10:26 UTC,I upgraded 17.10 to 18.04 and the problem remains the same :-(. I also did a new installation of 18.04 from scratch and that one isn't working either.
1741977,2018-05-02 15:46:24 UTC,Could you test if scanning works on your Samsung SCX-3200 multifunction in Ubuntu 18.04 (Bionic) ?
1741977,2018-05-02 15:42:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1741977,2018-04-10 13:47:21 UTC,"Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA."
1741977,2019-07-08 21:22:40 UTC,@Reinhard: The upgrade to 1.0.27 in Ubuntu came with several concurrent issues:
1741980,2019-05-23 18:12:55 UTC,Tested and works perfectly.  Signoff branch is at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1741980_opac_flesh_copy_tag_label-signoff
1741980,2019-04-24 13:45:02 UTC,Here's a branch that fetches the data needed and adds it to the OPAC display.
1741980,2019-05-23 19:49:20 UTC,"The copy tag type was originally intended more for staff use, and I think there's at least one user of them that would be surprised if the type labels started displaying unexpectedly."
1741980,2019-09-06 16:52:28 UTC,"Pushed to master for inclusion in 3.4. Thanks, Remington, Garry, and Kyle!"
1741980,2019-07-03 19:40:08 UTC,"I have tested this code and consent to signing off on it with my name, Kyle Huckins and my email address, <email address hidden>."
1741980,2019-05-28 15:20:09 UTC,Here's a branch with a second commit that does what Galen suggested.  I've also included a release note to notify libraries about this change.
1741982,2018-01-08 20:45:49 UTC,"StacktraceTop:
 view () at ../../ui/views/view_tracker.h:22
 SendMouseCaptureLostToActiveView () at ../../ui/views/controls/menu/menu_controller.cc:2536
 OnMouseReleased () at ../../ui/views/controls/menu/menu_controller.cc:735
 OnMouseEvent () at ../../ui/views/widget/widget.cc:1218
 DispatchEvent () at ../../ui/events/event_dispatcher.cc:191"
1741994,2018-01-09 11:02:16 UTC,How is it possible I get different linker layouts when I use linker from prebuilt tarball and linker built from source invariant tarball?
1741994,2018-01-09 08:54:54 UTC,"Hi Pavol,"
1741997,2018-05-23 16:33:26 UTC,"After reverting the code, the cross-references display, so it looks like it is indeed an issue with this branch."
1741997,2018-05-23 15:02:33 UTC,We added this code to a server with a production database that previously displayed cross-references and were unable to get any cross-references to display. We will be reverting the code on that server to determine if it's an issue with this code or an existing bug in Evergreen.
1741997,2018-05-18 15:53:05 UTC,"I'm having trouble testing this branch, not necessarily because of the code in this branch, but because I've been able to get cross-references to display even without the page on my test systems. I've tried in master, a recent pull of 3.0, and in 3.0.1 (checking to ensure that no new code has broken this display). I've also tried on clean installs and upgraded databases. Given that I see other 3.0.x catalogs that are successfully displaying cross references, I have to believe I am missing a step in getting them to display. I've linked authorities, linked bibs to authorities, and enabled the global flag to show related references."
1741997,2018-05-16 18:23:09 UTC,"I'm going to test this branch as we do need these fixes for our browse search. However, I have a couple of questions:"
1741997,2018-01-08 23:18:05 UTC,"Galen,"
1741997,2018-01-08 22:49:42 UTC,Patches are available in the user/gmcharlt/lp1741997_browse_fixes branch:
1741997,2019-02-22 20:52:04 UTC,Commenting here since it's related to the search.bib_is_visible() function proposed in Galen's branch...
1742000,2018-08-20 00:30:04 UTC,"Hi Robert, I haven't forgotten you.
Are you still in Ubuntu 16.04, or did you upgrade to 18.04? Not that you have to upgrade; I just thought I would check with you.
My next step is to try to replicate it on my own computer. I now have three different versions of Thunderbird installed in containers - that's what took me so long to get back to you. I wanted to check your version before I try to replicate it.
Take care
:)
G"
1742000,2018-07-15 19:05:29 UTC,apport information
1742000,2018-07-15 19:05:28 UTC,apport information
1742000,2018-07-15 18:48:30 UTC,"Hello Robert,
Thank you for submitting this bug and reporting a problem with font size in Thunderbird.  You made this bug report some time ago and there have been several versions of Ubuntu and Thunderbird since then."
1742000,2018-07-15 19:05:19 UTC,apport information
1742000,2018-07-15 19:05:20 UTC,apport information
1742000,2018-07-15 19:05:22 UTC,apport information
1742000,2018-07-15 19:05:23 UTC,apport information
1742000,2018-07-15 19:05:25 UTC,apport information
1742000,2018-07-15 19:05:26 UTC,apport information
1742000,2018-07-15 19:05:26 UTC,apport information
1742000,2018-07-15 19:41:38 UTC,"Hi Robert. Thanks for the update and the apport info. I'll look at next steps now.
Take care
:)
G"
1742000,2018-07-15 19:05:21 UTC,apport information
1742000,2018-07-15 19:05:30 UTC,apport information
1742000,2018-07-15 19:06:20 UTC,"Hi, yes the problem still exists."
1742000,2018-07-15 19:05:28 UTC,apport information
1742004,2020-09-22 04:17:20 UTC,[Expired for OpenStack neutron-api charm because there has been no activity for 60 days.]
1742004,2020-09-22 04:17:20 UTC,[Expired for OpenStack keystone charm because there has been no activity for 60 days.]
1742004,2020-09-22 04:17:19 UTC,[Expired for OpenStack nova-cloud-controller charm because there has been no activity for 60 days.]
1742004,2018-01-18 15:54:11 UTC,This bug may reflect Tytus' comment in Bug#1737776:
1742004,2018-01-12 22:48:43 UTC,Lowering priority as we have been unable to reproduce.
1742004,2018-01-12 11:21:30 UTC,"I've tried a number of strategies; test setups to try to replicate this, but no luck yet."
1742009,2018-01-19 01:00:50 UTC,"[‎1/‎18/‎2018 4:34 PM] Kamlesh Parmar:
sarath, do you have this setup? https://bugs.launchpad.net/juniperopenstack/+bug/1742009
Its a sanity blocker
We saved this conversation. You'll see it soon in the Conversations tab in Skype for Business and in the Conversation History folder in Outlook.
[‎1/‎18/‎2018 4:59 PM] Sarathbabu Narasimhan:
hi Kamlesh, though seen twice,  this not seen later image and let me remove sanityblocker and keep monitoring
[‎1/‎18/‎2018 4:59 PM] Kamlesh Parmar:
ok thanks"
1742011,2018-01-09 00:30:13 UTC,Finally the proof that it is the one mystic unicode character:
1742011,2018-01-14 23:16:42 UTC,Can reproduce the problem in artfull and bionic.
1742011,2018-01-13 15:48:11 UTC,Simple test case:
1742011,2018-01-09 14:11:10 UTC,Having a second look I found the mitigation cleaning up the filename with the help of: `tr  --delete --complement '[:print:]`
1742011,2018-01-09 00:29:00 UTC,"find -D search -name ""*4""
consider_visiting (early): ""."": fts_info=FTS_D , fts_level= 0, prev_depth=-2147483648 fts_path=""."", fts_accpath="".""
consider_visiting (late): ""."": fts_info=FTS_D , isdir=1 ignore=0 have_stat=1 have_type=1
consider_visiting (early): ""./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr\303s_du_Jazz-1734575236.mp4"": fts_info=FTS_NSOK, fts_level= 1, prev_depth=0 fts_path=""./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr\303s_du_Jazz-1734575236.mp4"", fts_accpath=""ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr\303s_du_Jazz-1734575236.mp4""
consider_visiting (late): ""./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr\303s_du_Jazz-1734575236.mp4"": fts_info=FTS_NSOK, isdir=0 ignore=0 have_stat=0 have_type=1
consider_visiting (early): ""."": fts_info=FTS_DP, fts_level= 0, prev_depth=1 fts_path=""."", fts_accpath="".""
consider_visiting (late): ""."": fts_info=FTS_DP, isdir=1 ignore=1 have_stat=1 have_type=1"
1742011,2018-01-09 00:27:19 UTC,For the case that the unicode character has been lost – here the hexdump:
1742019,2018-01-09 16:59:15 UTC,"Is this actually an error, or just a warning? In other words, does this error break barbican? Or is the old 'orders' table just used instead of creating a new one?"
1742019,2018-06-06 18:39:00 UTC,"Change abandoned by Douglas Mendizábal (<email address hidden>) on branch: master
Review: https://review.openstack.org/531696
Reason: Abandoning patch due to lack of activity for months.  Feel free to re-submit if needed."
1742019,2018-01-10 01:20:11 UTC,"I install barbican with rpm. barbican service functions normally
but sometime  log shows that gunicorn.error begining with ""Auto-creating barbican registry DB""
this error does not break barbican
when I set ""db_auto_create = False"" in barbican.conf, it disappears.
It doesn't happen every time, i feel strange about it
so adding some judgement in database upgrade script may be a good way"
1742022,2018-01-24 22:17:58 UTC,This issue was fixed in the openstack/neutron-lbaas-dashboard 4.0.0.0b3 development milestone.
1742023,2018-01-09 16:04:21 UTC,Found the log attached.
1742023,2018-01-09 14:46:24 UTC,Where do I find the log file?
1742023,2018-01-09 14:03:09 UTC,"If you're using the same codec for recording and broadcasting but only broadcasting has this issue, then I think there is an issue with Mixxx's connection to the broadcasting server. What type of connection are you using (Icecast 2, Icecast 1, or Shoutcast 1)? Could you attach the mixxx.log file from when this happens?"
1742023,2018-01-09 13:34:53 UTC,"Do you have a way to test the encoder. If not take a look at MyRadioStream.com. I think you can set up a test stream server, connect the encoder and listen right on the webpage.  This is what we use to test."
1742023,2018-01-09 13:26:04 UTC,MP3 for broadcasting and recording MP3.
1742023,2018-01-09 04:45:28 UTC,"Hmmm, that is weird. What codecs are you using for broadcasting (MP3 or Ogg Vorbis) and recording (WAV, AIFF, FLAC, MP3, or Ogg Vorbis)? You can check in the preferences pages for Live Broadcasting and Recording."
1742023,2018-01-09 04:19:57 UTC,Ok I went and rebooted everything made sure I was using the right skin.
1742023,2018-01-09 02:53:34 UTC,It is difficult to give detailed help without knowing what sound card and mixer you are using.
1742023,2020-05-10 09:39:35 UTC,https://github.com/mixxxdj/mixxx/pull/2743
1742023,2018-01-09 15:46:39 UTC,https://mixxx.org/wiki/doku.php/finding_the_mixxx.log_file
1742024,2020-02-16 21:32:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742029,2018-02-19 17:19:01 UTC,"Reviewed:  https://review.openstack.org/532380
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=1567a19b527fe672f417984e83f8d22bfa8a9d56
Submitter: Zuul
Branch:    master"
1742029,2018-03-12 14:27:39 UTC,"Reviewed:  https://review.openstack.org/531949
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=93fcfe7134c68cb8549b36a2d4f53f70e84087b0
Submitter: Zuul
Branch:    master"
1742029,2018-06-07 20:55:44 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b2 development milestone.
1742036,2018-01-09 04:28:14 UTC,This is due to the export code also calling Validate.
1742036,2020-04-16 04:30:33 UTC,If you call dump-model with --simplified does it still give all you need?
1742040,2018-01-09 05:07:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532011"
1742063,2018-04-21 05:32:20 UTC,ubuntu 18.04 desktop dev @ 21/4/2018
1742063,2018-01-27 10:30:39 UTC,"@ #5 dino my system has a fast samsung ssd 850 pro with swappiness 10 and preload...
still systemd takes too long to boot compared with 16.04 with unity"
1742063,2018-01-27 10:21:38 UTC,Related report: lp:1728181
1742063,2018-01-27 10:11:16 UTC,My system output:
1742063,2018-01-27 09:14:19 UTC,Some ideas: https://askubuntu.com/questions/826819/how-to-speed-up-your-boot-on-ubuntu-16-04
1742063,2018-01-27 09:10:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742063,2018-01-27 09:10:15 UTC,"As many users, you hit that network mess:
https://www.linuxquestions.org/questions/linux-newbie-8/networkmanager-wait-online-service-4175594791/"
1742063,2018-01-27 08:47:48 UTC,"Is it possible to disable braille service support by default, as the regular user doesnt really use that?"
1742063,2019-05-17 10:27:39 UTC,I fresh installed 18.04.2 with kernel 4.18 and now its finally fixed
1742078,2018-01-11 22:12:57 UTC,"Can you provide some more details about how you did the installation?  I believe the RDO distributions create a 'glance' user on the system who owns the service, so the logs should be owned by the 'glance' user."
1742089,2020-08-04 02:06:34 UTC,"The log shows the ""unknown"" VGA monitor is connected to the modeset driver, so that's the xorg-server package..."
1742093,2018-01-10 08:06:49 UTC,"AFAIK, without the extension, you can set the ip_allocation attribute to ""none"", but you can't read it with REST call."
1742093,2018-01-10 07:07:01 UTC,I can understand the requirement but ip_allocation is originally subset of segments extension. Although it seems that we can use ip_allocation of port without the extension now. I guess that we should use the feature with segments extension.
1742098,2018-03-07 08:22:34 UTC,"Verified on 9.2-mu-5 (proposed):
/usr/lib/python2.7/site-packages/cobbler/action_reposync.py file patched"
1742098,2018-02-07 12:49:50 UTC,"Reviewed: https://review.fuel-infra.org/37796
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0"
1742098,2018-02-06 16:13:47 UTC,"Fix proposed to branch: 9.0
Change author: Denis V. Meltsaykin <email address hidden>
Review: https://review.fuel-infra.org/37796"
1742098,2018-01-13 05:17:18 UTC,sla2 for 9.0-updates
1742101,2018-09-20 06:48:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742102,2018-08-29 21:03:04 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/568953"
1742102,2018-06-27 15:36:29 UTC,"On discussing with Dan Smith, the related denial of service condition described in this report has been a known risk since the introduction of the feature and generally falls below the threshold for broad publication in an advisory. The related fixes merged back as far as stable/pike will mitigate it (or can be tuned to greater extremes to do so if necessary) and are accompanied by a security release note. Since this report is already public, I'm going to mark this as a security hardening opportunity (class D in our VMT report taxonomy[*]) with no OSSA task needed. If there is a strong objection that an advisory is needed, then we can revisit publishing one."
1742102,2018-06-12 11:22:02 UTC,"Reviewed:  https://review.openstack.org/573239
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=43a84dbc1ebf147d43451610b76c700a31e08f4b
Submitter: Zuul
Branch:    stable/queens"
1742102,2018-06-07 14:06:43 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/573248"
1742102,2018-06-25 06:23:25 UTC,"Reviewed:  https://review.openstack.org/573248
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bdb5c3b4057b8b3c1ba27c70e237e5fa71064694
Submitter: Zuul
Branch:    stable/pike"
1742102,2018-06-07 05:22:25 UTC,"Reviewed:  https://review.openstack.org/572195
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91e29079a0eac825c5f4fe793cf607cb1771467d
Submitter: Zuul
Branch:    master"
1742102,2018-01-10 01:16:32 UTC,"We discussed this a bit in IRC, and this is a failure after we've created the port and when we go to plug the VIF for the instance, that fails. Neutron doesn't send any information with the network-vif-plugged event, just that it failed."
1742102,2018-01-10 01:20:02 UTC,"My point is we could add a whitelist of exceptions that shouldn't count to disabling a compute but we need to know what it is, rather than just generically ignore VirtualInterfaceCreateException since that could be any number of failures."
1742102,2018-01-18 15:34:33 UTC,"same bug with create 100 instances on volume (root disk is a volume). If quota volume is 10 max, you have 90 fails and nova disable 9 computes."
1742102,2018-01-23 19:47:52 UTC,"The volume create over limit is a good example. Regardless of this bug with the auto-disable stuff, it would probably be in our best interest to do a quota check in the API when we know nova is going to create the volume (which happens late in the compute service) and then we could fail fast in the server create API if we know we don't have enough volume quota for the boot from volume request. We already do a port quota check in the API during server create, so it seems we should also do that for volumes."
1742102,2018-02-09 06:46:39 UTC,"we can refer to https://review.openstack.org/#/c/520158 to add the check for volume quota , the utils function can be reused to get cinder quota limits"
1742102,2018-02-14 05:55:10 UTC,I made quota of volme to 1 then try
1742102,2018-04-12 00:38:38 UTC,"I'd like to pick this up and take care of it, but we need to have a discussion at the ideal resolution for this bug."
1742102,2018-04-12 00:57:33 UTC,Some more discussion about this bug in IRC with mnaser:
1742102,2018-05-16 19:44:08 UTC,I'm trying to think of a simple way to at least mark some failures as not something to be counted against the consecutive build failure count. The easy case is volume overquota when booting from volume and nova is trying to create a volume. We handle that OverQuota here and raise BuildAbortException:
1742102,2018-05-16 19:50:59 UTC,"Alternatively we could add a new build_results enum value like ""failed-not-misconfig"" and skip calling _build_failed() in that case, but that just bakes more dependent logic into the hooks code that has been deprecated since Mitaka."
1742102,2018-05-16 20:21:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568953"
1742102,2018-05-31 22:46:00 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1742102,2018-06-07 13:56:13 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/573239"
1742102,2018-05-31 23:25:43 UTC,Yes; both.
1742102,2018-06-04 19:48:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/572195"
1742102,2018-06-01 19:27:35 UTC,"One simple tactical fix for this would be to change the default on the consecutive_build_service_disable_threshold config option to essentially disable it by default, so that people upgrading to that or installing openstack for the first time don't hit this, and then document in the option itself the scenarios in which it might be OK to enable it while working on a more strategic fix (like if you're spreading instead of packing (default) in the scheduler, then this is less of an issue). Since it's a more advanced feature and obviously has unintended consequences, it should be something operators need to opt into."
1742102,2018-05-31 22:48:10 UTC,Is this affecting pike and queens?
1742106,2018-01-10 20:45:07 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1742106,2018-01-09 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742106,2018-01-09 10:44:38 UTC,apport information
1742106,2018-01-09 10:44:39 UTC,apport information
1742106,2018-01-09 10:44:41 UTC,apport information
1742106,2018-01-09 10:44:43 UTC,apport information
1742106,2018-01-09 10:44:44 UTC,apport information
1742106,2018-01-09 10:44:45 UTC,apport information
1742106,2018-01-09 10:44:47 UTC,apport information
1742106,2018-01-09 10:44:48 UTC,apport information
1742106,2018-08-30 18:28:55 UTC,I'm getting what appears to be the same error after gaming for a couple hours. About 8 of 16 cores softlock. My Dmesg mentions my amdgpu as well.
1742106,2018-01-16 20:30:06 UTC,Can you see if the fix in mainline was already cc'd to stable and in the latest upstream 4.4 kernel?  It can be downloaded from:
1742106,2018-01-09 10:44:51 UTC,apport information
1742106,2018-01-09 10:44:54 UTC,apport information
1742106,2018-01-12 01:18:07 UTC,"Thanks Joseph, with the 4.15-rc7 kernel, the system seems stable after 16 hours. With the 4.4 kernel, the lockups reproduce within 1-2 hours of running the workload."
1742110,2018-01-09 11:05:33 UTC,"Tested with the mainline kernel 4.15.0-041500rc7, this issue still exist.
Log can be found here: https://pastebin.ubuntu.com/26352444/"
1742110,2018-01-09 11:00:08 UTC,This change was made by a bot.
1742114,2018-01-09 11:31:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532165"
1742114,2018-01-23 07:36:30 UTC,"Change abandoned by Qi Peng (<email address hidden>) on branch: master
Review: https://review.openstack.org/532165"
1742121,2018-01-10 20:20:26 UTC,"lxml can't do anything about this, since this would need to be handled in the parser of libxml2. Larger line numbers are stored only in text nodes, many of which are discarded (in fact, the most important ones) if whitespace nodes are removed."
1742134,2018-01-09 12:26:30 UTC,"StacktraceTop:
 g_wakeup_new () at ../../../../glib/gwakeup.c:161
 g_cancellable_make_pollfd (cancellable=cancellable@entry=0x563a36a6a930, pollfd=pollfd@entry=0x7f9763215558) at ../../../../gio/gcancellable.c:405
 g_socket_condition_timed_wait (socket=0x7f974c31d3d0, condition=<optimized out>, timeout=<optimized out>, cancellable=0x563a36a6a930, error=0x7f97632156b8) at ../../../../gio/gsocket.c:3940
 g_socket_connect (socket=0x7f974c31d3d0, address=address@entry=0x563a3796f120, cancellable=cancellable@entry=0x563a36a6a930, error=error@entry=0x7f97632156b8) at ../../../../gio/gsocket.c:2595
 g_socket_connection_connect (connection=connection@entry=0x563a36b80770, address=address@entry=0x563a3796f120, cancellable=cancellable@entry=0x563a36a6a930, error=error@entry=0x7f97632156b8) at ../../../../gio/gsocketconnection.c:160"
1742134,2018-01-14 23:18:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742134,2018-04-05 09:58:40 UTC,It could be a duplicate of bug 1760795
1742136,2019-03-13 14:53:57 UTC,Why do we need ironic-inspector-tests? They only have unit tests for ironic-inspector..
1742136,2019-03-12 17:13:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642828"
1742136,2020-01-15 20:24:38 UTC,"Change abandoned by Trevor Vardeman (<email address hidden>) on branch: master
Review: https://review.opendev.org/642828
Reason: Not sure if its fixed already, but I'm marking to scrap this ancient review"
1742139,2019-11-13 09:28:26 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/694021"
1742139,2020-01-13 17:15:23 UTC,"Reviewed:  https://review.opendev.org/694021
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=c0fbe50583cc940894f8929e94c8b554898a470b
Submitter: Zuul
Branch:    master"
1742141,2018-01-09 16:02:27 UTC,"If we build in /tmp/foo, will the directory from awstats be in /tmp or /tmp/foo?"
1742141,2018-01-09 17:35:59 UTC,You mean hsperfdata_root? It should be in /tmp.
1742141,2018-01-09 18:04:34 UTC,"On Tue, Jan 9, 2018 at 9:35 AM, Andreas Hasenack <email address hidden> wrote:

> You mean hsperfdata_root? It should be in /tmp.
"
1742141,2018-01-23 01:27:24 UTC,"On Thu, Jan 18, 2018 at 5:59 AM, Robie Basak <email address hidden> wrote:

>> It is pretty easy for me to do what you're
> suggesting, and I think the code used to do it (i'll look in the
> logs), but Robie asked me to remove the indirection, because it ...
> was annoying?
>
>> And confirmed, you can blame Robie:
> https://bugs.launchpad.net/usd-importer/+bug/1723172
>
> My issue was merely that the name was previously unpredictable. I'd be
> fine with /tmp/build/ for example. Or /tmp/git-ubuntu-build/ if we're
> worried about ""build"" colliding. That's be simpler and more robust I
> think?
"
1742141,2018-01-18 13:59:52 UTC,"> It is pretty easy for me to do what you're
suggesting, and I think the code used to do it (i'll look in the
logs), but Robie asked me to remove the indirection, because it ...
was annoying?
"
1742141,2018-01-11 14:01:30 UTC,"Also affected collectd:
 $ git ubuntu clone collectd
 $ cd collectd/
 $ git ubuntu build-source --verbose --sign
Same issue:
01/11/2018 14:59:11 - DEBUG:Executing: /snap/bin/lxc file pull ready-dassie/tmp/collectd_5.7.2-2_source.changes ready-dassie/tmp/collectd_5.7.2-2.debian.tar.xz ready-dassie/tmp/collectd_5.7.2-2.dsc ready-dassie/tmp/hsperfdata_root ready-dassie/tmp/collectd_5.7.2-2_source.buildinfo ..
01/11/2018 14:59:11 - ERROR:Command exited 1: /snap/bin/lxc file pull ready-dassie/tmp/collectd_5.7.2-2_source.changes ready-dassie/tmp/collectd_5.7.2-2.debian.tar.xz ready-dassie/tmp/collectd_5.7.2-2.dsc ready-dassie/tmp/hsperfdata_root ready-dassie/tmp/collectd_5.7.2-2_source.buildinfo ..
01/11/2018 14:59:11 - ERROR:stdout:
01/11/2018 14:59:11 - ERROR:stderr: error: Can't pull a directory without --recursive"
1742141,2018-01-09 20:26:46 UTC,"And confirmed, you can blame Robie:
https://bugs.launchpad.net/usd-importer/+bug/1723172"
1742141,2018-01-09 20:11:57 UTC,Confirmed (pasted here for better formatting as well: https://pastebin.ubuntu.com/26355174/)
1742156,2018-04-27 13:02:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742159,2020-08-05 04:17:43 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1742159,2020-06-05 16:57:13 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Unfortunately you gave us no indication as to which release of Ubuntu was affected.
1742159,2018-01-09 16:22:49 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1742160,2018-01-09 19:12:05 UTC,NVM 384.111 seems to fix this.
1742160,2018-01-09 14:36:03 UTC,"Here is the make log of this install. Sadly it not overwrote the craash report due to a file already existent, so I can not provide that."
1742160,2018-01-11 14:38:49 UTC,384.111 fixed me too.
1742160,2018-01-09 14:48:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742162,2018-04-19 22:12:32 UTC,This issue was fixed in the openstack/designate-dashboard 7.0.0.0b1 development milestone.
1742182,2018-11-17 21:19:41 UTC,"Have same problem while running BOINC on
CPU: E6400
MOBO: P35 Neo3
Gpu: Geforce GT220
wifi card:linksys WMP54G (works only with 32bit os)
Linux info:
Linux Peppermint
Peppermint 9 Nine [4.15.0-23-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)]
(32 bit os)
after system restart its connects automaticaly to wifi but after a while drops connection"
1742182,2018-12-30 17:26:51 UTC,Wicd solved my problem
1742187,2018-01-10 05:19:06 UTC,"This is stuck...
Can be used to move this issue forward
https://review.openstack.org/#/c/356263/"
1742187,2018-01-10 02:27:31 UTC,This is bug in openstack client. I'm not sure that we need to fix neutron client.
1742188,2020-02-26 16:40:35 UTC,"For windows 64-bit you can also use the complementary xPack GNU Arm Embedded GCC distribution, it closely follows Arm releases:"
1742188,2020-02-26 16:28:12 UTC,"Hi Erlkoenig,"
1742193,2020-10-27 14:43:48 UTC,The bug (No wallpaper) still present on 20.04.1 when Nemo on Flashback.
1742193,2020-02-16 01:29:23 UTC,Thanks @Norbert. Confirming this bug is still present in the latest 18.04 release and your workaround still fixes it.
1742193,2018-06-26 18:52:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742193,2018-01-10 15:02:43 UTC,"Here is complete and working solution. `nemo-desktop` is fully-functional on Ubuntu(""Unity"") and GNOME FlashBack session:"
1742193,2018-01-10 11:51:14 UTC,gsettings set org.gnome.gnome-flashback desktop-background true
1742193,2018-01-10 09:53:33 UTC,Without killing `nautilus-desktop` and after launching `nemo-desktop` both them control desktop - I have two sets if icons with background.
1742193,2018-01-10 05:16:54 UTC,Flashback also uses gnome-settings-daemon. May be that's why it can't work. What happens when you restart gnome-settings daemon?
1742193,2020-10-27 15:08:22 UTC,"On Ubuntu 20.04 if you want use 3rd party desktop app you need to disable builtin desktop functionality in gnome-flashback. You can do that with:
gsettings set org.gnome.gnome-flashback desktop false"
1742193,2020-10-30 00:27:38 UTC,Thanks Alberts. I'd been trying to figure that out for some time now.
1742198,2018-01-18 08:20:08 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-2024
1742198,2018-01-09 17:13:40 UTC,Tested on latest Perocna  XtraDB Cluster 5.7 on latest RHEL 7
1742198,2018-01-10 09:08:43 UTC,fix came during merge
1742198,2018-01-10 10:46:21 UTC,"Thank you for a very quick reaction, perfect!"
1742217,2018-01-09 19:38:34 UTC,"Thanks for your report, and especially for your recipe to reproduce. I'm pretty sure this is an upstream bug, so please report it and future similar bugs upstream. If you think for some reason the bug is Ubuntu-specific, then report it here."
1742217,2020-01-08 08:45:37 UTC,"This bug has been fixed recently upstream:
https://www.lyx.org/trac/ticket/3136"
1742218,2018-01-24 22:29:27 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1469
1742237,2018-01-18 17:28:33 UTC,"It seems that you should double-check the EC2MetadataIp value that Heat takes from quickstart inventory vars, see network_environment_args and use_resource_registry_nic_configs that enables the former. If you configure networking via custom tht templates, look there instead."
1742237,2018-01-10 12:24:10 UTC,"It seems that
OS::TripleO::DeployedServer::ControlPlanePort: ../deployed-server/deployed-neutron-port.yaml"
1742237,2018-01-10 18:12:34 UTC,"Could be. After changing that, deleting the existing failed overcloud stack and retrying the deployment i got a different error. The overcloud deploy command now executed with the --debug option produced the output http://paste.openstack.org/show/642463/"
1742237,2018-01-11 17:23:53 UTC,"The failed software deployment's resources.NetworkDeployment should be analyzed then,
perhaps the commands like:"
1742237,2018-01-16 15:59:09 UTC,"I did some steps similar to above, looks like the issue may be related with discovering or pinging the $METADATA_IP http://paste.openstack.org/show/645737/ ?"
1742237,2018-01-18 21:53:53 UTC,"The value I currently have for EC2MetadaIP is the undercloud API IP. From the overcloud VM:
curl 192.168.24.1:8000
{""versions"": [{""status"": ""CURRENT"", ""id"": ""v1.0"", ""links"": [{""href"": ""http://192.168.24.1:8000/v1/"", ""rel"":  curl 192.168.24.1:8080
<html><h1>Not Found</h1><p>The resource could not be found.</p></html>[root@overcloud ~]"
1742237,2018-01-24 00:20:08 UTC,EC2MetadataIP should be your undercloud ip. The variable might be correctly set. However the failure is at the NetworkConfig stage. The error could be related to any other network config parameter issues. We might need to see if the packets for ping are being received on undercloud node. Mostly this could be the network setup.
1742237,2018-01-25 15:59:40 UTC,"Is the ping happening from inside of one of the containers deployed in the overcloud guest VM? I did the steps here http://tripleo.org/install/advanced_deployment/deployed_server.html#testing-connectivity (ping, curl the undercloud IP 192.168.24.1) and everything worked as mentioned above. See traces and ip config here http://paste.openstack.org/show/653451/"
1742250,2018-01-10 10:34:50 UTC,"I tried this on Ubuntu 16.04, started on GCE and it didn't seem to repro there.  When I add a veth, systemd units are added but they all seem to be cleaned up when the veth is removed."
1742250,2018-01-09 19:06:37 UTC,"As a workaround, running"
1742252,2018-01-10 10:02:54 UTC,The package has been published and the bug is being set to Fix Released
1742252,2018-01-10 08:06:31 UTC,This bug was fixed in the package linux - 4.4.0-109.132
1742252,2018-01-10 07:39:31 UTC,Needs regression USN; should go to -security pocket.
1742266,2018-01-09 19:59:47 UTC,"Confirmed. Also, it doesn't show anything on the checkout receipt for the non-cat items."
1742267,2018-01-09 20:09:56 UTC,"Is my understanding that snpacraft already uses the account info endpoint to check if the user has signed the ToS, this same endpoint can be used to check if the profile is complete."
1742269,2018-01-10 02:26:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742299,2018-01-17 23:30:11 UTC,You will need to link the bug to the pull request by doing adding a commit message of the form mentioned here:
1742299,2018-01-11 18:12:23 UTC,"Sure, will do! Just cleaning up a couple more edge cases I found while testing on my hardware"
1742299,2019-09-19 11:57:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1742299,2018-01-12 02:35:14 UTC,Thanks! Hope I did this correctly: https://code.launchpad.net/~cberner/maas/+git/maas/+merge/336024
1742299,2018-01-11 20:27:33 UTC,"@cberner, to expand on Newell's comment about the contributor agreement, it is available here:"
1742299,2018-01-11 19:56:39 UTC,"Christopher,"
1742299,2018-01-11 02:16:00 UTC,"Christopher,"
1742299,2018-01-10 00:04:15 UTC,"Let me know if you have any feedback on this fix. First time contributing to MAAS, so hope I did it right"
1742301,2018-01-09 22:59:47 UTC,Here's the traceback:
1742302,2018-02-02 04:47:28 UTC,"Ok, just bootstrapped a Artful system, looks like you should remove nvidia-381 and use nvidia-384."
1742302,2018-02-02 10:37:15 UTC,Is nvidia-390 working? I am using the latest kernel but cannot install nvidia-390
1742302,2018-02-02 14:35:51 UTC,"> On 2 Feb 2018, at 6:37 PM, Bharata Kalbuaji <email address hidden> wrote:
>
> Is nvidia-390 working? I am using the latest kernel but cannot install
> nvidia-390
"
1742302,2018-02-11 05:28:20 UTC,"I can confirm Kai-Heng Feng's comment, installing apt package nvidia-384 works fine."
1742302,2018-01-10 17:23:45 UTC,I had the same issue at first. What worked for me was to make sure the following was installed:
1742302,2018-01-10 21:02:04 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1742302,2018-02-01 21:30:35 UTC,See make.log
1742302,2018-01-09 23:30:07 UTC,This change was made by a bot.
1742302,2018-01-10 03:09:07 UTC,Not sure if this is related. Caught this before I upgraded. System is now freezing and I can't use an old kernel as I get the following:
1742302,2018-01-10 15:13:51 UTC,"Still the same in 4.13.0-26. Ubuntu 16.04.3, cannot boot into desktop after kernel upgraded, boot into the previous kernel it all works again."
1742302,2018-01-10 17:31:15 UTC,Above should have said linux-headers-4.13.0-26-generic like the rest of the packages.
1742302,2018-02-01 21:29:32 UTC,"No didn't work:
dkms install nvidia-381/381.22 -k 4.13.0-25-generic"
1742302,2018-01-10 17:25:44 UTC,I run Linux Mint so it might be a little different. Not sure if Ubuntu has the driver-manager package.
1742302,2018-01-26 23:24:43 UTC,"OK, just installed the nvidia driver from http://de.download.nvidia.com/XFree86/Linux-x86_64/384.111/NVIDIA-Linux-x86_64-384.111.run by hitting ctrl+alt+F2 after booting into login screen to switch to a console, login to root, stop lightdm, execute the nvidia update. There were some errors during install but now I have"
1742302,2018-01-17 10:06:21 UTC,I have an Nvidia GTX 1060 3gb and after upgrading to kernel 4.13.0-26 I could not log into desktop.
1742302,2018-02-01 05:17:09 UTC,"Can `sudo dkms install nvidia-381/381.22 -k 4.13.0-25-generic` build the driver correctly?
If not, please attach the make.log in its error message."
1742302,2018-01-13 21:00:08 UTC,"Some additional information:  when installing to a bare new installation of 16.04.3 LTS upgraded to the new kernel (4.13.xxx), installation of NVIDIA's CUDA 9 packages fails due to a module build failure, similar to the description of bug 1742160 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1742160"
1742302,2018-01-13 20:49:01 UTC,I confirm this with 4.13.0-26.  Does not occur after reversion to 4.10.0-42 or earlier kernels.
1742302,2018-01-12 23:06:16 UTC,I have fixed the problem by installing nvidia driver 390.12.
1742302,2018-01-12 10:16:53 UTC,"The same happens with driver 340 and 384. Older kernels work fine.
For now I have disabled nvidia's driver, and the open-sourced driver works."
1742302,2018-01-11 07:24:03 UTC,Possible duplicate bug 1742160
1742302,2018-01-11 05:37:42 UTC,This seems to be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742095 on which I found a workaround for the DKMS build process.
1742302,2018-01-11 03:21:09 UTC,I also installed and booted 4.15-rc7 and attempted to install nvidia-387 and got another crash in the DKMS build process.
1742302,2018-01-11 03:09:11 UTC,"I tested with the mainline kernel4.15rc7, problem still not fixed, still can't boot into desktop. I tried reinstalling the Nvidia driver in kernel 4.10 but build for 4.15 has error, I did it with synaptic and the window closed too soon for me to catch the error message."
1742302,2018-01-11 02:51:28 UTC,This bug is also occurring for me when installing nvidia-387 off Nvidia's 16.04 repository when using 4.13.0-26-generic. Attached is /var/lib/dkms/nvidia-387/387.26/build/make.log.
1742302,2018-01-21 13:39:51 UTC,"For what it's worth, I'm using a GeForce GT 620 and Ubuntu 17.10 and I can't see the KDE login screen.  I get a black screen but when I forcefully shut the computer down, I get the KDE logo as if I'm being logged out."
1742302,2018-01-17 21:11:20 UTC,"Same thing happened to me. When I tried to reboot with previous kernel the mouse and keyboard would disappear. Removing Nvidia driver got me back to the desktop.
In my case original nvidia drivers was the cause and switching back to open source nouveau helped. First, I removed all stuff from nvidia:"
1742302,2018-01-18 15:42:22 UTC,"Any solution to this problem yet? Does installing any other version of Ubuntu helps? I was in process of installing Tensorflow with GPU support when I faced this situation. If anyone has found a solution, kindly let us know."
1742302,2018-01-26 23:02:25 UTC,"I have the same problem. Since 4.13.0-25 I can't login into desktop. Here is my dkms status output:
root@sam:~# dkms status
bbswitch, 0.8, 4.11.8-041108-generic, x86_64: installed
bbswitch, 0.8, 4.13.0-17-generic, x86_64: installed
bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
bbswitch, 0.8, 4.13.0-25-generic, x86_64: installed
bbswitch, 0.8, 4.13.0-31-generic, x86_64: installed
bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed
nvidia-381, 381.22, 4.13.0-17-generic, x86_64: installed
nvidia-381, 381.22, 4.13.0-21-generic, x86_64: installed"
1742302,2018-01-26 06:44:34 UTC,Please attach the output of `dkms status`.
1742302,2018-01-24 00:55:32 UTC,"I just upgraded the kernel to 4.13.0-31 but the problem still persists. I am using Kubuntu 17.10 and after I reboot, I can not start the X server. If I try to start it, it shows message that it can not find opengl 2. Any idea how to fix this? I install the nvidia driver via repository."
1742302,2018-01-23 17:25:07 UTC,"I know it might sound stupid, but how do I get a terminal session as I am not able to log in under X11 at all when this issue occurs. It boots straight away into bios."
1742302,2018-01-23 16:03:42 UTC,"I spoke too soon!  The recent 4.13.0-31 kernel appears to have fixed the problem for me, at least."
1742304,2020-07-20 04:05:53 UTC,"By changing a bit the script find_lang_stgs.sh on one of the patches, I got a file with all language strings, no file path or line, just the language strings. I filtered that to get only the strings that were repeated 3 or more times. For this I used the command
awk '{a[$0]++}END{for(i in a){if(a[i] > 2){print a[i] i}}}' sorted_strings.txt"
1742304,2019-04-29 03:57:13 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9902"
1742304,2018-01-11 00:31:27 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/8418"
1742304,2018-01-09 23:08:37 UTC,This needs to be case sensitive as the case does matter at times.
1742305,2018-01-17 23:52:44 UTC,"Wow, that was fast :) Thank you, Marc!"
1742305,2018-01-17 23:17:55 UTC,Fixed in https://gitlab.com/inkscape/inkscape/commit/abc7ea9287dcbcd4b8b8a1ff98b3d1e19c2ee226 :)
1742328,2018-03-29 21:03:40 UTC,"Also we can so a simplify to the original path, whats your opinion?"
1742328,2018-01-12 20:57:09 UTC,Is because original path is too comlex and happends in some types of interpolation. Seems hard to fix in a high level. Need a 2Geom work.
1742328,2018-03-29 21:29:01 UTC,"I don't really know, sorry. Depends on what it would look like. Probably for many cases that would be a viable solution."
1742329,2018-01-12 21:04:18 UTC,"Seems happends randomly, perhaps only in first stroke"
1742329,2018-01-12 21:21:18 UTC,"Yes, I couldn't always reproduce."
1742335,2018-01-11 16:55:59 UTC,It was not a crash after all. Linux was working fine all along. It was an update to my AV receiver [ Marantz NR1504 ] that blacked the video. Apparently the change in the receiver was awaiting a reboot of the Linux system to decide to black the video. When I took the Linux system to another monitor - or directly to my Vizio P65 TV - Linux is fine on the latest kernel - 4.13.0-26. At least this is the latest kernel that I'm offered at the moment. The system is on LM 18.2.
1742338,2020-01-25 18:22:07 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1742338,2018-01-10 04:21:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1742338,2020-03-26 04:17:43 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1742342,2020-07-06 15:00:43 UTC,"Between filing this bug and 2.8.0, juju has added --agent-stream to upgrade-juju and upgrade-controller."
1742343,2018-01-25 21:50:36 UTC,"Reviewed:  https://review.openstack.org/531025
Committed: https://git.openstack.org/cgit/openstack/osc-lib/commit/?id=2b74586d3c9b3dff9e4993cadf5a7a6ad92d744f
Submitter: Zuul
Branch:    master"
1742348,2019-10-01 01:50:58 UTC,This is being handled in snapd
1742365,2020-07-31 05:43:20 UTC,Ubuntu 14.04 reached end of standard support in April 2019:
1742389,2018-01-10 08:08:37 UTC,At least as a quick fix I added these object methods to VNCScreen (latest nightly 1.1.2):
1742390,2019-03-16 07:51:30 UTC,Fixed in https://bazaar.launchpad.net/~openlp-core/openlp/trunk/revision/2692
1742390,2018-01-11 20:00:52 UTC,"It's not being told which encoding to decode from, so it presumes ascii. Even if we don't use chardet, we should at least ask it to decode from UTF-8."
1742403,2018-01-10 09:18:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742403,2018-01-10 09:43:47 UTC,Patched nm-config-connectivity-*.postinst to not fail if force-reload fails.
1742403,2018-01-10 16:20:42 UTC,"The attachment ""network-manager_1.8.4-1ubuntu4.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1742403,2018-01-29 15:54:31 UTC,This bug was fixed in the package network-manager - 1.8.4-1ubuntu4
1742403,2018-01-30 20:31:16 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of network-manager from artful-proposed was performed and bug 1746258 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1746258 (not this bug). Thanks!"
1742403,2018-01-15 17:01:13 UTC,"Hello Jean-Baptiste, or anyone else affected,"
1742409,2020-10-22 19:55:14 UTC,closing since the package is removed from Ubuntu
1742422,2019-12-22 13:42:40 UTC,This has been fixed in opendkim version 2.10.1-2 (Ubuntu 16.04).
1742426,2018-12-20 18:06:27 UTC,Solution
1742426,2018-03-16 01:58:34 UTC,"ZOWEETEK cheapo sub wifi dongle from Amazon stopped working after ubuntu update.
downloading and running the autoinstall for this driver got me going again rtl8821AU_linux_v4.3.14_13455.20150212_BTCOEX20150128-51.tar.gz
I'm running 32 bit 16.04"
1742426,2018-02-03 03:41:42 UTC,I have documented the patch needed to fix this issue in my last comment in this thread: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1637059
1742426,2018-02-01 16:33:14 UTC,I downloaded the driver while using kernel v4.10 and booted in v4.13 and followed the steps. no success. also no ethernet port.
1742426,2018-02-01 13:25:20 UTC,"Might be a silly question, but did you try installing driver why running kernel v4.10 instead of v4.13? I have plugged in the network cable, booted to v4.13 and installed rtl driver. Rebooted. This worked for me, although this way after each kernel upgrade manual installation will be needed (again)."
1742426,2018-01-31 23:58:38 UTC,"I've attempted to follow the solution,but it has not worked for me. I still need to boot form v4.10 instead of v4.13"
1742426,2018-01-31 22:35:56 UTC,"Yes, see
https://askubuntu.com/questions/994779/broken-wifi-rtl8812au-after-16-04-update-to-kernel-4-13-0-26"
1742426,2018-01-30 05:32:28 UTC,I am hitting the same issue; any suggested workaround?
1742426,2018-01-11 16:15:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742427,2018-06-12 10:27:40 UTC,"The original problem this bug was about is gone. Actually, now that the multicache went in, we would instead install CACHEDIR.TAG in the cache-loc (/etc/apparmor.d/cache.d/CACHEDIR.TAG). It will apply recursively to all the actual cache sub-directories."
1742430,2018-01-11 15:44:54 UTC,Shuaili Wang:
1742430,2018-01-23 12:46:46 UTC,"Goutham Pacha Ravi:
This bug isn't isolated to this test.
The bug appears in other tests,they are
manila_tempest_tests.tests.api.admin.test_share_instances.py
manila_tempest_tests.tests.api.admin.test_share_snapshot_instances.py
manila_tempest_tests.tests.api.test_metadata.py
manila_tempest_tests.tests.api.test_metadata_negative.py
manila_tempest_tests.tests.api.test_rules.py
manila_tempest_tests.tests.api.test_rules_negative.py
manila_tempest_tests.tests.api.test_shares.py
manila_tempest_tests.tests.api.test_shares_actions.py
manila_tempest_tests.tests.api.test_shares_negative.py"
1742430,2018-09-06 02:06:27 UTC,"There is a similar bug：https://bugs.launchpad.net/manila/+bug/1743472
This problem has been solved. https://review.openstack.org/#/c/540070/"
1742430,2018-09-27 15:49:24 UTC,This issue was fixed via 540070 as indicated in the previous comment.
1742448,2018-01-11 02:07:39 UTC,"Hi,"
1742448,2018-01-11 04:21:31 UTC,"The attachment ""qt5-qtgui-bug886807.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1742453,2018-02-04 08:15:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540633"
1742453,2018-07-26 08:57:44 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.0 release.
1742456,2018-01-10 16:21:54 UTC,"On 10.01.2018 [14:55:30 -0000], ChristianEhrhardt wrote:

> Public bug reported:
>
> While debugging a MP I reviewed I found that -v is somewhat ignored in
> submodules.  I assume this is to some extend since 0c515af9
>
> Although without the history on that I'm not sure which way you want to
> solve it.
>
> But as an example any logging of level info/debug in
> gitubuntu/build.py does not get out.
> Found while running:
> git ubuntu lint -v paelzer/lp1734207-fix-mulsipsk-zesty
"
1742456,2018-01-11 08:16:53 UTC,"I did not spot other cases affected yet, I happened to find the same message I missed hear in ""git ubuntu export-orig -v"" so I knew not all cases are broken.
But I don't have a list of affected subcommands :-/"
1742456,2018-01-11 16:27:24 UTC,"On Thu, Jan 11, 2018 at 12:16 AM, ChristianEhrhardt
<email address hidden> wrote:

> I did not spot other cases affected yet, I happened to find the same message I missed hear in ""git ubuntu export-orig -v"" so I knew not all cases are broken.
"
1742467,2018-06-27 12:53:40 UTC,We/I probably need to redo the analysis of the requests that the resource tracker is making these days. I forget whether it will have changed or not.
1742467,2018-01-10 15:41:36 UTC,Nice write up from cdent in the mailing list awhile ago on this same issue:
1742467,2018-02-12 12:10:05 UTC,"""The call to ""GET /resource_providers/37bef394-ca42-4926-8899-68e986f66abf/allocations"" should only happen"""
1742467,2018-01-10 16:01:24 UTC,"The call to ""GET /resource_providers/37bef394-ca42-4926-8899-68e986f66abf/allocations"" should only happen, I think, if there are any ocata computes in the deployment or if this is running on a compute host with the ironic driver."
1742467,2018-01-10 15:46:10 UTC,As for the two GET calls to /inventories every periodic task run:
1742467,2019-03-22 03:44:38 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1742467,2018-06-27 18:48:23 UTC,"Pulling aggregates in the compute starting in Rocky might be necessary solely for the provider tree saying if there are shared providers in the tree, like for shared storage. But that's not all teased out yet I don't think, i.e. we haven't really tried testing things out with shared storage modeled like that in placement in a multi-node CI environment like in a ceph job. There was something the other day I was commenting on that won't work with shared storage too, that had to do with move operations, it might have been these types of TODOs:"
1742467,2018-11-08 14:31:48 UTC,"https://review.openstack.org/#/c/615606/ and the series of changes above it are probably relevant to this bug, since I think now if you disable that refresh the compute will stop pulling aggregates on every periodic."
1742467,2019-01-21 16:40:14 UTC,"Reviewed:  https://review.openstack.org/615677
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=deef31729bd54f3747b7adba4132f148559c2242
Submitter: Zuul
Branch:    master"
1742469,2018-03-19 16:05:09 UTC,Unsubscribing field high.
1742472,2018-01-10 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742472,2018-01-10 16:22:09 UTC,"Cannot work out how to login via console-based browser, and as stated in the original report, the app port output is probably not relevant."
1742472,2018-01-10 17:50:49 UTC,"Kernel 4.4.0-108.131 also failed with corresponding config, and was fixed by setting CONFIG_KVM_GUEST=y (which set CONFIG_KVM_DEBUG_FS=y) although I cannot trace the error:"
1742482,2018-04-25 02:55:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742482,2018-02-01 17:39:44 UTC,"Hi Daniele,
I have reported your bug to the authors of the program: it seems that there is no relationship between bluefish and the incidence that you report (Please read this https://bugzilla.gnome.org/show_bug.cgi?id=792974). Can you reproduce the error with version 2.2.10? If you can, please provide more information. Otherwise, close the bug."
1742482,2018-02-06 05:16:09 UTC,"Hello Innocent,"
1742482,2018-02-06 17:28:38 UTC,"Hi Daniele,"
1742482,2018-02-07 04:33:24 UTC,"Added Nautilus as affected package, removed Bluefish. Thanks"
1742482,2018-04-25 07:34:56 UTC,Could you add a file example to the bug?
1742482,2020-11-14 18:02:45 UTC,The bug is still there in Ubuntu 20.10. I'm even almost certain it was fixed and re-appeared recently.
1742482,2019-11-23 18:52:32 UTC,Ubuntu 19.10
1742482,2019-11-23 18:46:29 UTC,"Not only Firefox, also Chrome and Opera are x-scheme-handler/ftp handlers."
1742482,2019-02-06 12:52:42 UTC,it's also discussed on https://gitlab.gnome.org/GNOME/nautilus/issues/713
1742482,2019-02-06 12:51:02 UTC,That's discussed upstream on https://gitlab.gnome.org/GNOME/glib/issues/1414 and basically their opinion is that firefox shouldn't claim to be a x-scheme-handler/ftp handler
1742482,2018-02-07 17:09:20 UTC,"Hi Daniele,"
1742488,2018-06-26 13:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742488,2018-06-26 13:09:00 UTC,"Hi,
the own website [1] still calls it ""should be considered a work in progress. As such it is not a complete product nor should it be considered one. Extra care should be taken when testing and configuring a system to use the KVMGT project""."
1742490,2018-01-10 18:25:51 UTC,"@kyrofa, 2.35 as far as I know."
1742490,2018-01-10 18:08:37 UTC,"That seems to be using the snapcraft docker image, right? What version of snapcraft is in there these days?"
1742495,2018-01-10 17:39:54 UTC,"When I set the ""Message Index Preference"" ""Convert Dates To Localtime""
Dates in the Format ""Wed Jan 10 06:55:20 EST 2018"" alpine shows the date as ""01/10/2001"""
1742497,2018-10-16 01:52:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742499,2018-01-13 21:43:33 UTC,"> Hearing that issue would not help any more than seeing the meter for the Record/Broadcast signal indicating no input signal.
"
1742499,2018-01-13 16:42:16 UTC,I mean test server.
1742499,2018-01-13 01:09:08 UTC,"> The streaming sound may get broken by a loose connection or such between your mixer output and Mixxx's recording/broadcasting input. If we have the proposed PFL position,you can listen to the broadcast sound, and are able to hear such issues.
"
1742499,2018-01-13 01:29:52 UTC,Had an idea tonight to save me from having to load and unload 2.0 and 2.1.0.  I installed 2.1.0 on another computer which is also connected to the same mixer.
1742499,2018-01-13 22:08:42 UTC,"> When hearing the sound you can Identify a clipped signal in an early stage, where the signal level in Mixxx is still green for example.
"
1742499,2018-01-13 16:41:47 UTC,"I downloaded the latest beta after my show today. Tried a few songs and recorded. No stuttering, no clipping.  I will try and use the beta for my show on Wednesday at 10:30 AM complete with encoders. I may try the test encoder later. Confidence is HIGH!"
1742499,2018-01-13 22:52:12 UTC,"> If the signal is clipping and Mixxx's meters do not show it, then the meters are broken.
"
1742499,2020-04-21 12:20:32 UTC,"I think the Broadcast Pfl is a valid request. Though, the name PREflight implies there's a volume control or a mute switch for the broadcast signal, before it's sent to outputs, which there isn't."
1742499,2020-04-21 07:11:34 UTC,"> Why would someone use a valuable pair of sound card outputs and an input channel on their mixer for this instead of routing a deck to the mixer? The mixer already has its own PFL bus. Using two different PFL buses, one in software and one in hardware would be confusing.
"
1742499,2020-04-21 07:23:51 UTC,"I understand your use case, but that is a very esoteric setup. I am concerned that if we added such a feature to the UI it would confuse far more people than would have any use for it."
1742499,2020-04-21 07:32:54 UTC,I do think a meter for the record/broadcast input would be helpful though.
1742499,2020-04-21 09:55:07 UTC,"> I do think a meter for the record/broadcast input would be helpful though.
"
1742499,2020-04-21 13:28:35 UTC,I do think adding a broadcasting section to skins could be helpful.
1742499,2020-04-22 02:08:44 UTC,"At least in the Tango skin, the tool bar, even at minimum window width, has plenty of room to add a PFL button between the Broadcast button and the clock. (I like how compact Tango is and the amount of functionality it manages to ""cram"".)"
1742499,2018-01-13 00:49:19 UTC,"Ron, how do you preview single decks? Which Mixxx outputs are connected to your external Mixer?"
1742499,2018-01-15 00:06:24 UTC,"> Actually the mixxx VU meter cannot even distinguish a clipping signal from a signal which is properly levelled to ADC full scale both have samples with value 65535.
"
1742499,2018-01-12 23:49:26 UTC,"Ron, how do you preview single decks? Which Mixxx outputs are connected to your external Mixer?"
1742499,2018-01-10 22:47:08 UTC,Windows Direct Sound. VU-meters were not maxed out they looked fine. I can see the clipping on the recorded waveform via audacity. Maybe add a slider in the record section. I would normally run it at about 75%. I can always add volume to what's recorded after the fact but I can't eliminate clipping.
1742499,2018-01-12 20:48:16 UTC,You will be able to listen the stream that is passed through the Recording/Broadcasting input before it is encoded for broadcasting. It is basically the same what you can see in the proposed side-stream VU-Meter.
1742499,2018-01-11 20:44:04 UTC,"> Any ideas on the stuttering issue? 2.0 doesn't have it.
"
1742499,2018-01-11 20:29:37 UTC,"Be, you are probably right the Record/Broadcast input is pretty useless without an VU-Meter. I think we made the mistake not actually using it during the verification."
1742499,2018-01-11 20:15:24 UTC,I'm sure your correct on that so it's probably not needed. It can always be added at a later date if needed. How about VU-Meter? Something visual?
1742499,2018-01-11 15:42:56 UTC,"I am not sure a gain or volume control for the record/broadcast signal would be useful. If you are using the Record/Broadcast input and the signal is coming into your sound card clipping, there is nothing Mixxx can do to make it not clipping. The level needs to be adjusted before that in hardware, preferably at the sound card input, or if there is no gain control there, at the mixer's output. If your sound card does not have a meter for this input, seeing a meter in Mixxx would help. I think we should break feature freeze for 2.1 to add that meter so users do not keep getting confused, but we would have to break string freeze too to add a tooltip for it. :/ Regardless, I'll be sure to mention this issue in the manual, so thanks for reporting it."
1742499,2018-01-11 14:17:17 UTC,YES! Very true and like I said give us a volume control for that signal as well.
1742499,2018-01-11 06:17:18 UTC,"Are you using the Record/Broadcast input in the Sound Hardware Preferences? If so, then the signal from that input is used unmodified for recording and broadcasting and the master meters in Mixxx do not tell anything about that. I realize now that there is no meter for this signal available in Mixxx, but perhaps we should add one."
1742499,2018-01-11 04:43:58 UTC,I reinstalled 2.1.0 I was able to get rid of the clipping with system levels and again my master levels were fine. The rumbling is gone for now. I think it's a combination of input / output settings but I don't know. However now nothing going out on the encoder however I can see the meta data. Also it still stutters whenever you do anything on the PC.
1742499,2018-01-11 21:16:14 UTC,Reverting back to 2.0?  Mainly because of the stuttering problem. When in Auto-DJ it is really bad when the next song is loading. Also bad if I search for a song using Windows file manager. Click a folder in the tree. etc.
1742499,2018-01-11 02:47:45 UTC,However it's not clipping except on the recording and broadcasting. and the meter is not maxed out.
1742499,2018-01-11 01:59:44 UTC,"> Maybe it's just over driving everything.
"
1742499,2018-01-10 21:22:46 UTC,The recorded track is clipping a lot. Does the Master VU-Meter indicate that as well?
1742499,2018-01-10 17:45:19 UTC,As you see my mic blocks the wave forms which I have become to rely on. Maybe when the silence killer and end cue's I wont need the waves but for now I need them.
1742499,2018-01-11 21:06:00 UTC,"I don't understand why you think adding a meter for the Record/Broadcast input would be a big feature creep. It just requires adding an EngineVumeter to EngineMaster, finding a place to show it in the skins (probably next to the recording and broadcasting buttons), and adding a tooltip."
1742499,2018-01-11 21:21:20 UTC,"I did not mean to use rout the signal though the engine like the aux channels. I mean, there is no difference between Aux and other input if you look at the hardware, so they should feature the same controls. Only a VU meter is not enough."
1742499,2018-01-12 22:52:31 UTC,"> And at what point in the process would that come into play?
"
1742499,2018-01-11 21:35:50 UTC,Stuttering happens overall. Not only sound but visual on the waveform as well. I can provide an example later.
1742499,2018-01-11 21:56:55 UTC,We need PLF and a gain as well.
1742499,2018-01-11 22:01:52 UTC,"It is small, because you want it. A small change is to comment the Recording/Broadcast input in the Hardware preferences. But let's discuss pro and cons of merging a solution instead."
1742499,2018-01-11 22:14:06 UTC,What would be the use cases for a PFL button or gain knob for the Record/Broadcast input? I cannot think of any. I think they would only add to users' confusion.
1742499,2018-01-11 22:16:38 UTC,"> My last test I didn't get any sound to the encoder but did to the recorder.
"
1742499,2018-01-11 22:32:25 UTC,"I don't know why, but my line on-board line input is to low. I have to crank up the gain to 6 dB."
1742499,2018-01-11 21:40:07 UTC,"Please keep discussion about separate issues in separate bugs. It is difficult to stay organized if bugs contain multiple unrelated discussions. If you would like to have a more freeform discussion, Zulip ( https://mixxx.zulipchat.com/ ) may be a better place for that than the bug tracker."
1742499,2018-01-12 04:00:39 UTC,"Okay, so there would be a use case for a gain knob in case the mixer and sound card both provide an inadequate amount of gain. But I am pretty sure there is no use case for adding a PFL button to the Record/Broadcast input. Mixxx's PFL is not used with an external mixer, so it would not be useful. Also, the signal is already being monitored on the speakers from the mixer's main output, so there would not be a point to listening to it in headphones."
1742499,2018-01-12 07:09:19 UTC,"I think it is not a big deal to pass the signal to pfl. And it may save the user for a broken show in odd cases.
He can always very everything is ok with a single mode click, so let's at least consider this.
A good or maybe better alternative would be to listen the sidechain stream in headphones."
1742499,2018-01-12 13:35:08 UTC,"Also, the signal is already being monitored on the speakers from the mixer's main output, so there would not be a point to listening to it in headphones."
1742499,2018-01-12 13:55:19 UTC,"> I don't even have speakers attached to the computer. only headphones attached to the mixer.
"
1742499,2018-01-12 14:25:26 UTC,"Ron has the perfect use case for the Pfl button though. Only on pair of headphones, no speakers, plugged into the Mixxx pfl channel he can listen to everything without pluging the headphones around."
1742499,2018-01-12 15:29:09 UTC,"To be honest, I'm thinking about this and I don't know how the PFL would work via software. On headphones via mixer I'm listening the final product before hitting the encoders. Which is a mix of Mixxx and anything that I add via the mixer ie mic's, phone calls, promo hits etc. Maybe others could use the Pre Fader Listen?  And at what point in the process would that come into play?"
1742499,2018-01-11 21:47:03 UTC,"> I mean, there is no difference between Aux and other input if you look at the hardware, so they should feature the same controls. Only a VU meter is not enough.
"
1742500,2018-01-30 19:35:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742502,2018-02-15 00:07:04 UTC,"Joe,"
1742502,2018-02-14 22:13:03 UTC,Can you see if this bug still occurs with the 116 kernel in -proposed?
1742502,2018-01-24 17:18:54 UTC,"112 kernel has the same issue.  Adding nopti allows it to boot.
What's different: It stops after zswap loading."
1742502,2018-01-10 19:23:32 UTC,Additional info in hopes it proves useful.
1742502,2018-01-10 17:51:34 UTC,booting on 109 with nopti works! Good call Leann.
1742505,2018-01-18 08:26:36 UTC,Test packages for Artful and Xenial in:
1742505,2018-01-16 06:32:37 UTC,Marking kernel tasks as confirmed as we have at least one related bug which we have confirmed is fixed under 4.15 (and looks like an easy pick for 4.13).
1742505,2018-01-18 08:25:56 UTC,I've re-tested with the proposed changes upstream; MTU is correctly set to 65000 for all tunnel types including GRE on 4.4 kernels; the kernel fix for bug 1743746 is required for support on >= Artful or if the HWE edge kernel is in use on Xenial.
1742505,2018-01-16 06:31:08 UTC,Mirroring some of the thread on the ovs dev ML:
1742505,2018-01-15 12:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742505,2018-01-13 14:50:10 UTC,Eric Garver:
1742505,2018-01-12 12:33:50 UTC,Pinged upstream dev mailing list for openvswitch for feedback
1742505,2018-01-17 12:14:59 UTC,Reference bug 1743746 for MTU hardware limitation in 4.13 kernel
1742505,2018-02-22 13:14:22 UTC,"This bug was fixed in the package openvswitch - 2.8.1-0ubuntu0.17.10.2~cloud0
---------------"
1742505,2018-02-22 13:14:20 UTC,The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1742505,2018-02-21 14:44:16 UTC,"The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1742505,2018-02-21 14:44:03 UTC,This bug was fixed in the package openvswitch - 2.8.1-0ubuntu0.17.10.2
1742505,2018-02-19 15:55:21 UTC,successfully tested with bug 1743746
1742505,2018-02-05 13:20:08 UTC,"Hello David, or anyone else affected,"
1742505,2018-02-02 17:07:02 UTC,This bug was fixed in the package openvswitch - 2.8.1-0ubuntu3
1742505,2018-02-02 14:27:44 UTC,Tested OK on Xenial with Pike UCA:
1742505,2018-01-30 09:09:05 UTC,"Hello David, or anyone else affected,"
1742505,2018-01-29 18:07:37 UTC,"Hello David, or anyone else affected,"
1742505,2018-01-25 15:13:09 UTC,@james-page When will the 2.8.1 release be?
1742505,2018-01-20 10:25:03 UTC,I've uploaded the fixes for this issue to bionic (currently in proposed awaiting builds across all archs) and for artful (stacked ontop of the current 2.8.1 stable release in proposed).
1742505,2018-01-18 08:55:21 UTC,Leaving the kernel bug tasks open for now; there is an underlying issue in the kernel specific to GRE tunnel ports where the MTU passed during new device creation is not being used; the fixes to OVS workaround this issue rather than actually resolving it.
1742505,2018-01-16 09:41:25 UTC,ovs-dev ML thread:
1742505,2018-01-17 07:26:46 UTC,Simple reproducer:
1742510,2018-01-18 20:55:28 UTC,"I'm going to add this as a wishlist item which we typically do for feature requests, as adding this back would technically be a new feature."
1742510,2018-01-10 19:15:14 UTC,FYI:
1742510,2018-01-18 20:52:32 UTC,Development seems to be picking back up: https://github.com/openstack/neutron-vpnaas/commits/master
1742510,2018-06-29 08:37:05 UTC,"Change abandoned by Trent Lloyd (<email address hidden>) on branch: master
Review: https://review.openstack.org/551168
Reason: VPNaaS support will note be re-integrated at this time"
1742510,2018-09-20 16:17:14 UTC,vpnaas is back under the OpenStack governance from what I can see:
1742510,2019-02-25 08:06:05 UTC,"This was rejected by the OpenStack team until VPNaaS had good upstream support for 3 releases. Will look at resubmitting then. Given that it was re-added to ""Stadium"" in Queens, I will aim for resubmitting this in the T release timeframe."
1742512,2018-01-12 15:36:08 UTC,This is a duplicate of https://bugs.launchpad.net/evergreen/+bug/1722380 but I'll mark that one as a duplicate since this one has more discussion.
1742512,2018-01-12 13:38:59 UTC,"Proposed solution would be to add an Angular filter to check the age in the template, then add a div below the birthdate stating if the patron is a minor based on an ngIf check of the of the age."
1742512,2018-01-12 14:17:53 UTC,Hi Sam!
1742512,2018-01-12 14:52:19 UTC,"I think using the juvenile flag is a much better solution, as is having the notice be part of the administrative settings. And placing the notice in the summary sidebar would be consistent with current behavior, which makes a note of ""juvenile"" below the patron's name."
1742512,2018-01-12 15:37:17 UTC,"In the xul client, purple text saying ""(Juvenile)"" appeared below the patron name along with alerts, notes, etc."
1742512,2018-01-12 15:48:30 UTC,"Sorry, I didn't read comment #1 closely enough and misunderstood the kind of alert being suggested. If it were just something added to the display, I don't think an additional setting is required. I was envisioning more of a popup alert that staff needed to click through. Sorry for the noise!"
1742512,2018-01-12 17:31:17 UTC,"No worries! I've been having issues with precise language for the past week, and was thinking in terms of ""Bootstrap lets you format an a div element with an alert class to make it stand out"" and later realized ""That really sounds like I mean a Javascript alert."""
1742519,2018-06-08 02:24:22 UTC,"I have previously used SoundConverter to convert flac to mp3 (CBR, Insanely High) for better compatibility. Could this error have come from my previous preference settings? I have not tried to convert from flac to opus in a fresh install of SoundConverter."
1742520,2018-03-02 17:44:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549299"
1742523,2019-08-05 14:41:14 UTC,"I believe we are backporting translation changes, so I've pushed this to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jane and Jason!"
1742523,2019-08-01 16:54:07 UTC,Add my signoff here:
1742523,2018-05-19 04:42:07 UTC,"Haha never mind; I didn't have the ""Charge item price when marked damaged"" library setting set to true.  I'm adding the pull request tag so that others can help to test this."
1742523,2018-05-19 04:11:23 UTC,I created a branch for this here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/sandbergja/lp1742523_making_mark_damaged_strings_translatable
1742524,2018-05-10 13:38:11 UTC,I've been able to duplicate the same issue in 3.0.7 and hearing from another user that it is happening for them too.
1742524,2018-03-08 21:00:54 UTC,"Follow up - actually, it seems to be ignoring the printer set in Hatch as well as the printer setting in the drop down on the page."
1742537,2018-01-10 21:23:15 UTC,@jsalisbury
1742537,2018-01-10 21:19:51 UTC,apport information
1742537,2018-01-10 21:19:50 UTC,apport information
1742537,2018-01-10 21:19:50 UTC,apport information
1742537,2018-01-10 21:19:48 UTC,apport information
1742537,2018-01-10 21:19:48 UTC,apport information
1742537,2018-01-10 21:09:23 UTC,Does this bug go away if you boot back into the prior kernel?
1742537,2018-01-10 21:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742537,2018-01-10 20:51:41 UTC,I believe this is unrelated to the KPTI patches as the same stack trace is appearing in our non-updated machines.
1742537,2018-01-10 21:19:53 UTC,apport information
1742539,2018-01-29 13:18:58 UTC,"I think that living trees can also die, and a simple solution might litter a map with dead trees over time. This assumption needs to be confirmed though."
1742539,2018-01-29 18:36:23 UTC,"> 3. Allow foresters to plant a saplings that will replace dead trees (I'm in favor, but it needs an engine change)
"
1742539,2018-01-30 10:56:47 UTC,"So, have permanent dead trees, but allow trees to auto-seed on top of them?"
1742539,2018-01-30 13:17:26 UTC,"The thing with the snowman is fine for me. A player may never notice this, at least because a snowman is a rare used element."
1742539,2019-09-16 17:36:06 UTC,Migrated to https://github.com/widelands/widelands/issues/2096
1742550,2018-01-31 00:17:58 UTC,Seems like a useful information to see :-)
1742550,2018-02-08 05:05:49 UTC,"With further look into this, it seems that the most useful information for your use case would be to see application endpoints, i.e. not 'mysql' but 'mysql:juju-info'."
1742550,2018-02-08 15:34:55 UTC,"Anastasia,"
1742550,2018-02-09 02:19:49 UTC,"@Jason Hobbs (jason-hobbs),"
1742550,2018-02-09 02:38:34 UTC,The other places where model-level spaces information may reside is status:
1742550,2018-02-15 08:12:27 UTC,"If we did that, would it be clearer if we put it into real columns:
https://pastebin.ubuntu.com/p/P2hsMkz9mK/"
1742550,2018-02-15 09:52:11 UTC,"@Jason Hobbs,"
1742550,2019-01-24 08:27:25 UTC,PR that introduces new 'show-application' and including binding information is: https://github.com/juju/juju/pull/9662
1742553,2020-08-20 17:09:13 UTC,"I have tested this fix and agree to signing off on it with my name, Dawn Dale and email <email address hidden>."
1742553,2018-12-11 17:55:45 UTC,Confirmed in Evergreen 3.2.1
1742553,2020-05-06 17:12:58 UTC,Here is a branch with a fix. It's ready for review.
1742558,2018-01-10 22:20:55 UTC,See also my answers here:
1742560,2019-11-04 22:18:58 UTC,Are there any plans to correct the Xenial's package?
1742563,2018-03-01 06:32:33 UTC,need backporting. I add new tag kernel-da-key
1742563,2018-02-24 02:55:48 UTC,Is there a list of commits we should confirm for 18.04?
1742563,2018-03-02 00:14:33 UTC,"hi, Joseph Salisbury
we will do full test on 18.04 beta release. we just make sure this commit should be merged into 18.04 since Melhow is expected to be supported in 18.04 and we don't want our release(18.04) miss this commit."
1742563,2018-03-01 13:07:30 UTC,I built a Bionic test kernel with commit f919dde0772a894c693a1eeabc77df69d6a9b937.  The test kernel can be downloaded from:
1742563,2018-03-01 06:14:42 UTC,"Merged in v4.16-rc1.
Commit id:
f919dde0772a894c693a1eeabc77df69d6a9b937"
1742563,2019-10-03 08:29:50 UTC,Could be found in B/E
1742564,2018-01-10 23:01:36 UTC,It appears that the following is better than a reboot:
1742565,2018-11-22 17:36:38 UTC,"The abovementioned PR was rejected and closed, I don't think there was any other solution on the table. Re-opening."
1742565,2018-01-11 15:41:58 UTC,https://github.com/snapcore/snapd/pull/4477
1742565,2018-01-10 23:01:33 UTC,"I second this request, it's a constant paper cut."
1742573,2018-02-27 00:50:26 UTC,Because of that problem I could not only not upgrade the kernel but couldn't install any software at all.
1742586,2018-01-15 16:08:57 UTC,"I have the default number of kernels installed with unattended upgrades & autoremove, so 3. I have configured xz compression, which normally stops this. /boot is undersized due to this install being done with a Xenial pre-release (before the default /boot size was increased). I don't know what changed that had apport flag this as a new bug."
1742586,2018-01-15 15:44:54 UTC,"Yes, this is due to running out of space in /boot."
1742586,2018-01-12 17:31:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742589,2018-01-11 02:59:42 UTC,"Ok, changing the affected package to unity-control-center then. But from your description it's not apparent to me that it's really a bug. I'd recommend you to also seek support at e.g. <https://askubuntu.com>."
1742589,2018-01-11 02:10:33 UTC,"Hi
I install ubuntu 16.04.3 LTS on my laptop and desktop i dont know. I just
download from following link.
https://www.ubuntu.com/download/desktop
Previously i install same version and wifi works fine. However some minor
performance issues were there. Later on i install ubuntu again but now
wireless network option is totally disappeared in system settings. Only
wired connection is shown."
1742589,2018-01-11 01:50:21 UTC,Not a documentation bug.
1742601,2018-02-19 10:46:39 UTC,"It might be related to MTU. I'm not sure what causes it but setting iperf segment size explicitly to some value lower than your interface's MTU helped.
For server, try iperf -s
For client, try iperf -c %server% -M 1350"
1742602,2020-05-29 15:40:15 UTC,After reinstalling to 20.04 this bug no longer affects me.
1742602,2019-11-15 14:43:23 UTC,I am also affected. Running Ubuntu 18.04 MATE i686 with 1 VGA and 1 DP.
1742602,2018-07-24 09:31:45 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1742602,2018-07-23 01:04:47 UTC,"Sorry about not finishing the bisection. I was dubious about the prospect of finding a nice clean patch to cherry pick in that drm-intel branch. But this is superseded now by the upgrade of linux-generic-hwe-16.04 to 4.15, which does not have the same issue."
1742602,2018-06-18 16:31:51 UTC,Would it be possible for you to test the latest 4.15 upstream stable kernel?
1742602,2018-06-18 11:38:22 UTC,"The blank screen problem is still present in my case on Ubuntu 18.04 using a Dell 5570 machine.
Upgrading to kernel 4.17.2-041702 has solved the problem."
1742602,2018-04-03 06:54:37 UTC,"Looks like this is occurring on hybrid graphics systems. Not only Ubuntu, Arch, Fedora all affected by this bug.
I have two Dell Latitude 5580 and Dell Latitude e5570 laptops. One has Intel+Nvidia hybrid graphic system and other one has Intel+ATi hybrid graphic system. Both having the same issue HDMi goes to sleep immediately after X server starts.
The only desktop environment I found fixed this is Linux Mint Cinnamon and Mate both initially had the issue but after updating issue is gone. Looks like the bug is in the kernel."
1742602,2018-02-20 01:03:21 UTC,"FYI this is also happening for me, LTS 16.04.3 + HWE (kernel and xorg pkgs),
Thinkpad x270 w/ Integrated Graphics Chipset: Intel(R) HD Graphics 620."
1742602,2018-01-26 08:44:43 UTC,"The blank secreen problem still standing in 4.13.0-32 kernel too.
Linux Mint, 18.2, Cinnamon"
1742602,2018-01-17 00:41:59 UTC,"I can perform the bisect and build the kernels for you.  Can you first test 4.13 final to confirm it has the bug?  If it does, I'll start a bisect between 4.13 final and 4.14-rc1."
1742602,2018-01-19 11:57:32 UTC,"Thanks for all this good testing Tim and Joseph.
If I can help to keep things moving while Tim is travelling, let me know, although might need a little guidance initially... if there are some good instructions you can point me to on how to get the test kernel in and to boot...
Tim: to your observation I see the issue (assuming it is the same one) with a VM with no dual monitor.  But I do see the issue fix itself and reappear based on the screen resolution.  Perhaps does that observation shed any further light on it or fit with your external monitor results?"
1742602,2018-01-17 01:37:43 UTC,aae3dbb4776e7916b6cd442d00159bea27a695c1: fixed
1742602,2018-01-17 01:10:04 UTC,"I started a ""Reverse"" kernel bisect between v4.13 final and v4.14-rc1. The kernel bisect will require testing of about 13 test kernels."
1742602,2018-01-17 00:51:35 UTC,4.13.0-041300 (4.13 final): broken
1742602,2018-01-16 23:09:46 UTC,"4.14-rc1 does fix the issue. So that just leaves 12600 commits to choose from, according to git log v4.13-rc7..v4.14-rc1. I guess I would need to recompile the kernel for each bisection iteration? Are we looking for a drm/i915 commit? There's not quite so many of those (281)."
1742602,2018-01-16 18:32:13 UTC,"We can perform a ""Reverse"" kernel bisect to identify the exact commit that fixes this issue.  We first would need to narrow down the versions a little further."
1742602,2018-01-15 00:14:00 UTC,I booted various mainline kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
1742602,2018-01-14 08:48:48 UTC,I have just had the same issue.
1742602,2018-01-11 09:52:30 UTC,I also have the same problem:
1742602,2018-01-11 05:34:33 UTC,Here's the packed apport file.
1742602,2018-01-20 15:21:54 UTC,I built a test kernel up to including:
1742602,2018-01-11 05:29:21 UTC,"I ran apport-collect, selected ""keep"", and edited the resulting file to remove private information. But I couldn't find any way to upload such a file to an existing bug report."
1742602,2018-01-11 04:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742602,2018-01-17 14:36:17 UTC,"I built the next test kernel, up to the following commit:
bf1d6b2c76eda86159519bf5c427b1fa8f51f733"
1742602,2018-01-17 20:37:30 UTC,bf1d6b2c76eda86159519bf5c427b1fa8f51f733: fixed
1742602,2018-01-17 22:00:03 UTC,"I built the next test kernel, up to the following commit:
edc2988c548db05e33b921fed15821010bc74895"
1742602,2018-01-17 23:30:30 UTC,edc2988c548db05e33b921fed15821010bc74895: fixed
1742602,2018-01-18 16:17:56 UTC,"I built the next test kernel, up to the following commit:
e5fa05b96b02f45a91a364d2121451a4da05cd84"
1742602,2018-01-18 22:17:37 UTC,e5fa05b96b02f45a91a364d2121451a4da05cd84: fixed
1742602,2018-01-18 23:16:31 UTC,"I built the next test kernel, up to the following commit:
b9c55b6e2cc4369b0688961fa5de0e057f3ec0c4"
1742602,2018-01-19 05:59:48 UTC,b9c55b6e2cc4369b0688961fa5de0e057f3ec0c4: fixed
1742602,2018-01-19 10:19:57 UTC,"In other words, I'd like packaged kernels for 2d62c799f8ffac4f7ffba6a4e7f148827dfc24c7 and 5771a8c08880cdca3bfb4a3fc6d309d6bba20877 . The expectation is that that will confirm that the fix came from drm-intel. Assuming that's confirmed then we would have to do a bisection of the drm-intel-next branch back to the merge base (whatever that is). Maybe the tag v4.12-rc3?"
1742612,2018-01-11 06:41:50 UTC,"Oh, ignore the retracer. It's just complaining that the stacktrace is from my -O0 nostrip build. The attached stacktrace is fully symbolic."
1742612,2018-01-11 06:25:36 UTC,Thank you for your report!
1742612,2018-01-11 06:25:31 UTC,"StacktraceSource:
 #0  0x00007f1c0ea8f0bb in ?? ()
 #1  0x000000000a392400 in ?? ()
 #2  0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()"
1742612,2018-03-14 23:56:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742613,2018-01-22 19:13:51 UTC,This bug was fixed in the package linux-oem - 4.13.0-1017.18
1742613,2018-01-11 06:37:06 UTC,Driver source code is GPLv2 licensed.
1742613,2018-01-11 06:34:12 UTC,rtk-btusb and firmware released by Realtek for 0bda:b00a.
1742613,2018-02-08 08:30:14 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742613,2018-01-11 06:33:12 UTC,rtk-btusb and firmware released by Realtek for 0bda:c024.
1742614,2018-04-09 05:00:39 UTC,"I installed according to a bug fix posted elsewhere to get my WiFi going on my Toshiba Satellite to work, which it does now.  It never worked before the patch with 16.04 LTS."
1742614,2018-01-12 18:16:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742614,2018-01-12 03:00:03 UTC,Looks like a duplicate of bug 1713638. So you might have better luck installing 'bcmwl' instead of 'broadcom-sta'.
1742615,2018-01-12 04:12:21 UTC,"Thanks, I can confirm it works as you describe too. However, if storage was added to the first unit *after* the initial deploy (using add-storage), the second unit does not implicitly get storage and will fail as I describe. So yes, a --storage flag on add-unit would be useful."
1742615,2018-01-11 10:01:24 UTC,"> juju deploy cs:postgresql --storage=250G
>
> If I need to add a second unit with 'juju add-unit postgresql', there will be no attached storage > and setup will fail; an attempt will be made to replicate the database, and it will fail due to lack of space.
"
1742621,2020-06-23 17:22:51 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/532788"
1742621,2018-01-22 11:23:58 UTC,Planned for Queens (If we make it)
1742621,2018-01-11 12:06:46 UTC,"I think the initial condition of the neutron DB should be defined in more details.
Is there already existing network configuration, what is the initial plugin responsible for Neutron DB was population. Do we assume ML2 plugin? What are enabled mechanism drivers? Does it matter?"
1742621,2018-01-11 09:55:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/532788"
1742622,2018-01-11 07:30:04 UTC,This change was made by a bot.
1742632,2018-01-11 14:13:32 UTC,"Reproduced in Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1 64bit."
1742632,2020-04-01 14:18:19 UTC,Closing because INVALID: NOTABUG
1742637,2018-01-24 16:28:50 UTC,The above PR should fix things transparently for g-s (and our own cli).
1742637,2018-01-24 16:13:36 UTC,https://github.com/snapcore/snapd/pull/4532
1742637,2018-01-24 11:24:26 UTC,I would suspect snapd needs to passthrough
1742637,2018-01-22 01:55:55 UTC,"That should say ""provided by snapd"""
1742637,2018-01-22 01:55:06 UTC,The metadata provided by snap is:
1742637,2018-01-17 12:23:45 UTC,"Evan, wasn't the conclusion of the discussion the other day that ""Company name"" was the wrong information to display?"
1742637,2018-02-14 14:33:47 UTC,Unfortunately we need to revert this again because the display name can be changed in arbitrary ways by the developer. So it could be used to present misleading information.
1742649,2018-01-23 20:33:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/536959"
1742649,2018-01-23 20:20:39 UTC,I'll push up a change for the docs and I've tagged this with low-hanging-fruit so someone that wants to work on the suggestion from comment #1 can do so. It would be similar to how the --until-complete option works with the nova-manage db archive_deleted_rows command works.
1742649,2018-01-23 20:06:47 UTC,"Alternatively, a --verbose option could be added to the command so you could at least see it's making progress by printing out each instance that is being mapped while it's running."
1742649,2018-01-23 20:06:00 UTC,"This is a one time operation when you're upgrading to a cells v2 deployment, so while it's unfortunate it took this long in a large cloud with several thousand instances, I'd consider this lower priority to resolve with code at this point unless the change is trivial. Therefore option 3, better documentation of the command and it's option itself, is probably what I'd lean toward."
1742649,2018-01-11 10:03:52 UTC,"Actually, it would be useful to be able to say map all the instances using this batch size, eg:"
1742649,2018-01-27 10:37:14 UTC,"Reviewed:  https://review.openstack.org/536959
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2890d8db67012d7c33c40a1e36a66766740b8f8f
Submitter: Zuul
Branch:    master"
1742655,2018-01-15 15:25:10 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/533704"
1742655,2018-01-30 01:02:58 UTC,This issue was fixed in the openstack/tripleo-common 8.4.0 release.
1742655,2018-01-11 12:57:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532808"
1742655,2018-01-15 15:23:14 UTC,"Reviewed:  https://review.openstack.org/532808
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=49cb3b2e052bda379d35c6141874a332e983fa8c
Submitter: Zuul
Branch:    master"
1742655,2018-01-24 12:48:29 UTC,"Reviewed:  https://review.openstack.org/533704
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=786f3d6f7ef7e2dc33e534cfc33600ec4dc35f23
Submitter: Zuul
Branch:    stable/pike"
1742655,2018-02-12 14:08:18 UTC,This issue was fixed in the openstack/tripleo-common 7.6.9 release.
1742659,2018-01-11 14:02:17 UTC,"Confirmed in Win 8.1 64 bit, Inkscape 0.92.2 (5c3e80d, 2017-08-06)."
1742659,2018-01-12 04:16:48 UTC,Thank you for your testing.
1742659,2018-01-11 16:42:13 UTC,"Right now I'm using Linux Mint 17.1 64 bit, Inkscape 0.92.2"
1742663,2018-01-16 03:43:31 UTC,"Reviewed:  https://review.openstack.org/532811
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=bb9fd2c61a9ab41c57f427e13cd6a8bae391049e
Submitter: Zuul
Branch:    master"
1742663,2018-01-11 13:21:17 UTC,"Ok further information, this is a regression since https://review.openstack.org/#/c/462211/"
1742663,2018-01-11 13:16:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532811"
1742663,2018-01-11 11:31:20 UTC,"For reference, this is the class I was attempting to execute - https://review.openstack.org/532801"
1742663,2018-01-11 11:25:05 UTC,"To clarify, I was trying to use the following environment file:"
1742663,2018-01-11 11:18:14 UTC,"Confirmed by inspection, I think this got broken in the refactor to use ansible to drive the deploy steps, looking into a fix, but containers make this harder as we now have two places where step_config is defined, one that's consolidated into /var/lib/tripleo-config/puppet_step_config.pp (we can add the missing puppet code here easily I think), and then in the per-service docker/services/file for docker_config."
1742671,2018-01-15 17:07:45 UTC,"Yes, this does seem to be the same issue as https://sourceforge.net/p/net-snmp/mailman/message/35379818/
Sorry for opening a duplicate."
1742671,2018-01-14 16:07:35 UTC,"While running the commands that triggers the server hang I see a bunch of connects, but the same is true for the working walks."
1742671,2018-01-14 15:12:24 UTC,"I must admit, I'm not a net-snmp expert and I wonder if <email address hidden> is dead htese days - otherwsie I'd recommend to report there as well to get support from developers focussed on it."
1742671,2018-01-14 15:05:35 UTC,"Hi Tom,
thank you for your report.
First of all I can confirm your issue."
1742675,2018-02-08 19:37:46 UTC,"I can confirm that kernel 4.13.0-33.36 work ok on my hardware (Asus Zenbook UX305) and this kernel has applied all patches for Spectre+Meltdown.
The same result with kernel 4.15.2 from Canonical mainline ppa. So you have choice - vanilla kernel or Ubuntu kernel."
1742675,2018-02-15 17:56:56 UTC,Sadly issue returned with kernel 4.13.0-35. As i can see from changelog some Spectre patches have been changed to different approach to fix this issue. So this is probably reason for this behavior.
1742675,2018-02-15 20:37:44 UTC,Also lates vanilla 4.15.3 works OK so it looks like 100% problem with Ubuntu kernel patches.
1742675,2018-02-22 11:43:05 UTC,I updated again this morning and installed the latest 4.13.0-36-generic kernel. Unfortunately it still panics on boot. I've attached another slo-mo video.
1742675,2018-03-02 20:15:16 UTC,"I'm author of this bug report.
The bug has been resolved by the recent upgrade."
1742675,2018-06-14 11:31:37 UTC,Attached is a transcription of the latest kernel boot panic.
1742675,2018-06-14 10:24:13 UTC,"I am still experiencing the same bug. I regularly pull down the latest updates with apt update and apt dist-upgrade, and if a kernel update is included then I always test it."
1742675,2018-02-08 03:01:32 UTC,"Upgrading to kernel 4.13.0-33.36 from ppa:canonical-kernel-team/ppa solved the issue.
No need to use ""acpi=off"""
1742675,2018-06-18 15:53:15 UTC,"Another data point, 4.13.0-45 crashes on boot even with acpi=off. It looks like a different call trace though, which I can transcribe on request if anyone thinks it will help."
1742675,2018-06-21 03:52:18 UTC,Maybe try the -hwe-edge kernel instead?
1742675,2018-06-21 14:11:48 UTC,"Thanks for the suggestion @kaihengfeng. I installed linux-generic-hwe-16.04-edge, which gave me a working 4.15.0-23-generic after a reboot."
1742675,2018-03-04 15:16:50 UTC,Here is a new bug report for a new bug caused by recent updates that fixed #1742675:
1742675,2018-01-29 21:01:36 UTC,Sorri for unintentional misinformation about kernel 4.14.0-17. In fact it has patches for Meltdown. But not for Spectre.
1742675,2018-01-21 16:54:05 UTC,ad #16:
1742675,2018-01-27 20:04:16 UTC,"ad #28:
you need to use the canonical-kernel-team/unstable PPA!!!!!"
1742675,2018-01-11 14:00:19 UTC,This is affecting me as well. I had to connect up a monitor and keyboard to see what's happening - it's a kernel panic on boot. Machine is a Dell Precision T5500.
1742675,2018-01-11 14:00:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742675,2018-01-11 14:40:06 UTC,"I noticed that Dell BIOS A09 was ancient, so I upgraded to a (slightly) newer version, A16 from 2013. It still crashes with 4.13.0-26-generic but the panic message is different."
1742675,2018-01-16 12:05:04 UTC,"I suppose, the following 2 bugs are related to the fact that I work under linux-image-extra-4.10.0-42-generic. Both appeared in Phpstorm only recently after this main bug:
a) Once some PHP files edited through Phpstorm were cached somewhere deeply in Ubuntu. So, when i ran them through local webserver older versions were loaded. The bug was resolved by restarting Ubuntu.
b) Now there is continuous bug. Phpstorm performs some indexing operations with files continously and some part of UI are blinking."
1742675,2018-01-16 19:53:53 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1742675,2018-01-16 20:43:57 UTC,I prefer to avoid testing it on working computer.
1742675,2018-01-18 20:51:20 UTC,"I have a Dell Optiplex 960 that exhibits a reboot during boot with 4.13.0-26 with no kernel panic message (though 4.10.0-42 works fine).  I managed to get console dump via serial, which had no information."
1742675,2018-01-18 21:38:14 UTC,"Using ukuu, I tried 4.14.13-041413.201801101001 and it too fails without acpi=off."
1742675,2018-01-19 01:26:12 UTC,"I have the same issue, an automatic upgrade to 4.13.0-30-generic and now I can't boot.  Just kernel panics right away.  If I boot with 4.10.0 it works fine.  I'm also attaching a screenshot of my kernel panic message."
1742675,2018-01-19 11:42:50 UTC,It still fails for me with acpi=off.
1742675,2018-01-21 11:36:12 UTC,"for me,lubuntu,16.04, 32 bit installation, no kernels 4.13 and 4.14 boot, neither without or with acpi=off. Without acpi=off, boot stops right after leaving the grub menu; with acpi=off after the message ""starting to show plymouth boot screen""."
1742675,2018-01-21 12:02:37 UTC,"Question for experienced Ubuntu developers/sysadmins/users:
how long such bugs like this one usually stay non-fixed?"
1742675,2018-01-28 17:37:55 UTC,I can confirm that kernel 4.14.0-17 runs also on my hardware (in fact even without any additional boot options).
1742675,2018-01-18 11:10:22 UTC,@jsalisbury
1742675,2018-01-21 15:34:02 UTC,Similar thing in my situation - all kernel including linux-image-4.13.0-25-generic work OK on my Asus Zenbook UX305FA but linux-image-4.13.0-26-generic makes my laptop almost unusable (everything is many times slower) and any newer version up to current  linux-image-4.13.0-30-generic hang during start. On plymounth screen it boots up to progress bar and hangs just before showing mouse pointer (comparing to normal boot).
1742675,2018-01-21 19:42:42 UTC,"I've tried your 5 options with linux-image-4.13.0-30-generic but without luck.
On the other hand I've tried mainline 4.14.14 (compiled today) and as all mainline kernels it works without problems."
1742675,2018-01-22 09:16:18 UTC,ad #19
1742675,2018-01-22 19:39:55 UTC,"Yes, probably differences in results due to different hardware."
1742675,2018-01-22 21:27:14 UTC,3 additional tests:
1742675,2018-01-22 22:19:41 UTC,After standard system update to 4.13.0-31 the problem still persist.
1742675,2018-01-23 11:48:11 UTC,ad #22 and 23:
1742675,2018-01-23 20:25:40 UTC,"Since it is probably due to Meltdown+Spectre patches we've probably missed additional parameter - intel microcode used to build initramfs. It has changed 2018-01-08 to new one but was changed back to old one yesterday because many users reported boot and stability problems. It for sure affects boot and generally ""behavior"". So to be sure that i use correct microcode i've updated to lates on as of today and regenerated all initramfs files fo all installed kernels doing:"
1742675,2018-01-26 22:36:53 UTC,"I am affected as well: cannot boot from kernels 4.13.0-26 and 4.13.0-31 even when acpi=off. Reverted to 4.10.0-42.
Lubuntu 16.04 32 bit on Intel NUC 5PPYH."
1742675,2018-01-27 14:48:23 UTC,I am also affected - all version of 4.13 released so far do not boot.  I also have reverted to 4.10.0.42.  Xubuntu 16.04.3 installed on Dell e6430 laptop Intel/nVidia Graphics no dual-boot.  I would echo the sentiments of an earlier poster - how can this continue through 3+ releases with no resolution in sight?
1742675,2018-01-27 20:02:35 UTC,ad #27:
1742677,2018-11-23 08:58:26 UTC,"Back to ""confirmed"", as the PR wasn't landed after all."
1742677,2018-01-15 09:50:38 UTC,I followed up in https://github.com/snapcore/snapd/pull/4486
1742682,2018-03-12 17:32:41 UTC,"I created the patch. This is temporary solution, but it's works."
1742682,2018-03-12 17:33:38 UTC,Sorry. https://pastebin.com/ckzw4uwU
1742682,2018-03-23 15:07:54 UTC,Newest kernel solve this problem.
1742682,2018-03-23 17:12:33 UTC,"Tamas, do you know how new kernel makes it working? To what specific version of kernel are you referring?"
1742682,2020-03-30 07:10:17 UTC,"This seems to be a duplicate of [0], which is indeed caused by a kernel bug fixed somewhere between 4.4.0-176 and 4.8.0-58. See comment #21 on [0]."
1742687,2018-01-11 14:12:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742687,2018-08-15 20:33:01 UTC,This has been fixed for some time in snapd.
1742687,2018-03-21 20:56:36 UTC,could we close this one?
1742687,2018-01-22 09:55:21 UTC,https://github.com/snapcore/snapd/pull/4495
1742687,2018-01-17 06:02:00 UTC,Marking AppArmor task as invalid. DBus now implements DBus activation mediation and so the mediated service needs to be updated when specifying peer_label with an activated service.
1742687,2018-01-16 07:55:48 UTC,Seb pointed at https://cgit.freedesktop.org/dbus/dbus/commit/?id=dc25979eb which provides a possible fix/workaround (in https://forum.snapcraft.io/t/spotify-cannot-open-url/3341/12).
1742687,2018-01-15 15:17:05 UTC,"Adding apparmor since this may be related to libapparmor. zyga will provide more details, but essentially, when userd is not running (ie, dbus activation is used) and a snap tries to use userd to open a url, there is this denial:"
1742687,2018-01-15 15:04:39 UTC,Doing some testing it looks like an activation issue.
1742687,2018-01-11 14:14:40 UTC,https://forum.snapcraft.io/t/spotify-cannot-open-url/3341/7
1742689,2018-01-13 10:10:50 UTC,Thanks
1742689,2018-01-11 13:40:57 UTC,"Maybe you have seen this?
Menu: Edit>Resize page to drawing or selection. (Shift+Ctrl+R)"
1742689,2018-01-13 12:05:20 UTC,Might help if you add a screencast of what you have in mind.
1742689,2020-09-19 07:04:52 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1742689,2018-01-16 18:26:46 UTC,Hi all
1742689,2018-01-16 18:00:19 UTC,I suspect it's the 'page' area. Clarification would be helpful.
1742690,2018-01-23 19:18:47 UTC,This bug was fixed in the package collectd - 5.7.2-2ubuntu1
1742690,2018-01-11 13:19:29 UTC,Reported upstream as https://github.com/collectd/collectd/issues/2647
1742690,2018-01-11 13:19:15 UTC,"Interim fix is by adding
  CFLAGS += -Wno-cpp"
1742706,2018-01-24 18:43:31 UTC,"Change abandoned by Major Hayden (<email address hidden>) on branch: master
Review: https://review.openstack.org/532838"
1742706,2018-01-11 14:43:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532838"
1742721,2018-03-14 11:15:01 UTC,This bug was fixed in the package linux - 4.13.0-37.42
1742721,2018-03-09 07:39:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1742721,2018-02-20 15:52:49 UTC,When can I expect this change to come to 16.04?
1742721,2018-01-16 10:33:50 UTC,linux-image-4.13.14-041314-generic_4.13.14-041314.201801152042_amd64.deb fails to boot.
1742721,2018-01-17 14:14:19 UTC,Thanks for testing.  I'll submit an SRU request to have this commit included in the next release.
1742721,2018-01-15 20:27:20 UTC,linux-image-4.13.14-041314-generic_4.13.14-041314.201801151947_amd64.deb boots up without issues.
1742721,2018-01-15 20:11:59 UTC,"I built the next test kernel, up to the following commit:
c52278a636018cb8fa39b2538c6da5d35e6515f7"
1742721,2018-01-15 13:35:18 UTC,linux-image-4.13.14-041314-generic_4.13.14-041314.201801112308_amd64.deb boots up without issues.
1742721,2018-01-12 14:44:57 UTC,"My kernel version is linux-image-4.13.0-26-generic, reboot to old kernel linux-headers-4.10.0-42-generic works."
1742721,2018-01-12 14:37:20 UTC,"I got similar issue, the kernel encountered NULL dereference to null error."
1742721,2018-01-12 03:18:49 UTC,Latest update of Lubuntu 16.04.3 LTS 32-bit to kernel 4.13.0-26-generic on old Acer Aspire One corrupts the initial login screen.  Some of the screen appears properly on the right hand side - the remaining screen is random/changing black and white pixels.  The machine still boots kernel 4.10.0-42-generic with no problem.
1742721,2018-01-15 20:54:39 UTC,"I built the next test kernel, up to the following commit:
274f1097b2041506a6a3ab21c1d3a01897b34b65"
1742721,2018-01-11 23:23:46 UTC,"I built the next test kernel, up to the following commit:
0f003bb5010fd9a2dc71809183370656c94eca34"
1742721,2018-01-11 19:58:15 UTC,"I built the next test kernel, up to the following commit:
8604c6181edd1a62a6bf1f07261b547e6a74afe1"
1742721,2018-01-11 19:04:30 UTC,linux-image-4.13.14-041314-generic_4.13.14-041314.201801111630_amd64.deb fails to boot.
1742721,2018-01-11 17:07:45 UTC,"I started a ""Reverse"" kernel bisect between v4.13.14 and v4.14.15. The kernel bisect will require testing of about 4-6 test kernels."
1742721,2018-01-11 16:00:04 UTC,This change was made by a bot.
1742721,2018-01-16 17:54:34 UTC,The reverse bisect reported commit 16808dcf605e6302319a8c3266789b76d4c0983b as the fix.
1742721,2018-01-17 10:42:32 UTC,I can confirm that linux-image-4.13.0-25-generic_4.13.0-25.29~lp1742721_amd64.deb and linux-image-extra-4.13.0-25-generic_4.13.0-25.29~lp1742721_amd64.deb boot up fine.
1742721,2018-01-11 20:31:17 UTC,linux-image-4.13.14-041314-generic_4.13.14-041314.201801111932_amd64.deb also fails to boot.
1742721,2018-01-19 15:17:56 UTC,"SRU request submitted for Artful and Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089407.html"
1742726,2018-01-16 17:18:07 UTC,http://people.canonical.com/~kernel/status/adt-matrix/xenial-linux-meta-gcp.html
1742726,2018-01-22 19:57:13 UTC,The package has been published and the bug is being set to Fix Released
1742726,2018-01-22 19:14:52 UTC,This bug was fixed in the package linux-gcp - 4.13.0-1007.10
1742726,2018-01-16 17:32:02 UTC,No regression found on regression tests.
1742734,2018-07-17 20:27:25 UTC,"Can somebody look at this? I'm unable to launch an instance on Queens deployed by kolla-ansible. I get the kvm permission denied error as well. I tried changing the ansible role to user=root group=kvm, but that didn't work. I changed user=root group=kvm on the compute host /etc/libvirt/qemu.conf, but that didn't work either."
1742734,2018-01-13 23:55:34 UTC,What I am trying to say is that the settings in the file:
1742734,2018-01-13 23:06:31 UTC,Why is this marked 'incomplete'?
1742734,2018-01-11 23:11:05 UTC,Fixed image can be pulled from iimraann/kolla-centos-binary-nova-compute:pike
1742736,2018-01-17 12:20:50 UTC,"Thank for your bug report, indeed that would be a nice improvement"
1742736,2018-01-11 16:31:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742744,2018-01-11 18:40:50 UTC,fixed in https://github.com/systemd/systemd/pull/7857 (tested)
1742747,2018-07-10 07:51:15 UTC,"Change abandoned by Maciej Jozefczyk (<email address hidden>) on branch: master
Review: https://review.openstack.org/532924"
1742747,2018-01-29 13:36:54 UTC,The problem is actually more complicated now due to the issue detailed in this thread:
1742747,2018-01-11 17:57:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532924"
1742747,2018-02-27 16:43:11 UTC,Ok after some conversation on IRC - I don't want to touch the if-logic for now.
1742747,2018-01-29 16:06:45 UTC,I'm ok with change to watch aggregation metadatas first and then use the policy.
1742764,2018-01-24 14:34:01 UTC,Fixed on 4.15-rc9
1742764,2018-01-23 01:05:20 UTC,In 4.13.0-31-generic does not work either.
1742764,2018-01-11 18:42:38 UTC,apport information
1742764,2018-01-16 18:19:59 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1742764,2018-01-11 18:42:34 UTC,apport information
1742764,2018-01-11 18:42:33 UTC,apport information
1742764,2018-01-11 18:42:31 UTC,apport information
1742764,2018-01-11 18:42:30 UTC,apport information
1742764,2018-01-11 18:42:29 UTC,apport information
1742764,2018-01-11 18:42:26 UTC,apport information
1742764,2018-01-11 18:42:25 UTC,apport information
1742764,2018-01-11 18:42:24 UTC,apport information
1742764,2018-01-11 18:42:28 UTC,apport information
1742764,2018-01-11 18:42:20 UTC,apport information
1742764,2018-01-11 18:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742764,2018-01-11 18:42:35 UTC,apport information
1742764,2018-01-11 18:42:36 UTC,apport information
1742764,2018-01-11 18:42:22 UTC,apport information
1742766,2019-10-24 03:10:56 UTC,"When config software to use mysql
exception"
1742767,2018-01-14 20:05:35 UTC,"Found this:
https://askubuntu.com/questions/994315/virtualbox-crash-on-kernel-4-13-0-26"
1742767,2018-01-11 20:20:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1742767,2020-06-20 04:17:19 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1742767,2020-04-20 07:43:46 UTC,it might be fixed with vbox in -updates pocket
1742776,2018-01-11 19:16:40 UTC,I'll add castellan to the affected projects depending on which direction I fix it from.
1742778,2018-01-12 16:13:41 UTC,"It turns out that we were constructing multiple qemu ""vlans"" which aren't actual 802.1q vlans but rather something akin to network hubs w.r.t to which devices see which packets."
1742785,2019-03-13 21:23:03 UTC,I wonder if this is fixed now in 3.2+ from bug 1750894 ?
1742789,2018-11-16 16:23:29 UTC,"@vt, can you see if this issue occurs with the upstream 4.20-rc2 kernel?  It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc2"
1742789,2019-08-28 18:40:04 UTC,"FWIW, this just happened again while trying out the latest mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline"
1742789,2019-06-26 12:51:19 UTC,Hi !  I have tried kernel version 5 and 4.20. The same error. Latest kernel I can use is 4.4.0.137.
1742789,2018-11-14 08:39:57 UTC,"I have the same issue and I have tried latest kernels, but this is not fixed. I would appreciate if you could help me on this issue."
1742789,2019-06-27 09:53:32 UTC,"The issue is solved. At least I found solution. Seems message ""[Errno 28] No space left on device"" was
absolutely correct. The problem was only to find correct device.
1) Usually RAM of domain0 for the XEN has very small size. It was 512M in my case.
2) Ram-disk and especially /run file-system has size as % from the domain0 RAM, in my case it was just near 50K and it is not enough to unpack new kernel images."
1742789,2018-02-26 16:42:26 UTC,"Alright, I think I'm starting to narrow down the issue.  I was able to use apt-get and install kernels up to linux-image-4.4.0-112-generic.  I'm even able to install the latest, if I uninstall package 'linux-generic' and manually install linux-image-4.4.0-116-generic, e.g.,"
1742789,2018-01-11 20:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1742789,2018-01-11 20:43:54 UTC,apport information
1742789,2018-01-11 20:43:55 UTC,apport information
1742789,2018-01-11 20:43:57 UTC,apport information
1742789,2018-01-11 20:43:58 UTC,apport information
1742789,2018-01-11 20:43:59 UTC,apport information
1742789,2018-01-11 20:44:01 UTC,apport information
1742789,2018-01-11 20:44:02 UTC,apport information
1742789,2018-01-12 02:53:42 UTC,Can you see if the 4.4.0-104 kernel boots?  It can be downloaded from:
1742789,2018-01-12 03:38:32 UTC,"Sure, 4.4.0-104 kernel gave the same message as 4.4.0-109-generic and
didn't boot as well."
1742789,2018-01-12 15:43:25 UTC,Thanks for testing.  That suggests this bug is not due to the PTI security patches.
1742789,2018-01-12 17:11:57 UTC,Thanks for your help on this issue.  4.15-rc7 also fails to boot.
1742789,2018-03-09 09:16:08 UTC,Is it possible that you are really running out of disk space?
1742789,2018-01-11 20:44:00 UTC,apport information
1742789,2018-02-26 15:58:31 UTC,"Alright, I'm thinking something else is the issue, since after manually installing 4.4.117 it also boots?"
1742789,2018-02-26 15:47:29 UTC,"Yes, when I select 4.4.0-15 from the GRUB menu it boots."
1742789,2018-01-15 20:40:33 UTC,"Is you select 4.4.0-15 from GRUB menu it boots, correct?"
1742793,2018-01-12 20:51:56 UTC,"by the way: The hardware of this computer allowed for perfect suspend/resume under 14.04, with kernel 3.13.xxx and nvidia-304 and 340"
1742793,2020-01-06 11:12:36 UTC,"Hello,
4.13.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1742798,2018-01-11 22:27:55 UTC,"there is code in snapd that would produce a better error message for 402, sounds when this was coded that was the expectation to get that in some case, but I was not directly involved,"
1742798,2018-01-15 10:05:27 UTC,Adding the snapstore for better status codes.
1742800,2018-01-11 22:03:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/532990"
1742800,2020-02-19 22:50:07 UTC,"Change abandoned by Adrian Turjak (<email address hidden>) on branch: master
Review: https://review.opendev.org/532990"
1742804,2021-01-04 13:38:53 UTC,"I get it too, but on a fresh Kubuntu 20.10!"
1742804,2018-01-14 23:57:42 UTC,"I tested it again with the regular Gnome-based Ubuntu desktop, and it exhibits the same bug, so i changed the title accordingly. It seems there is no connection to the flatpak problem."
1742804,2020-04-23 13:20:39 UTC,This is fixed in now.
1742804,2020-04-24 15:36:03 UTC,"Hi, sorry this was reported before I subscribed to systemd bugs."
1742804,2020-05-03 10:36:34 UTC,"> status: 	Unknown → Fix Released
"
1742804,2020-07-02 21:45:28 UTC,"> > status: Unknown → Fix Released
>
> Still affects me too. I don't see fix released for Bionic.
"
1742804,2021-01-12 20:45:26 UTC,"> I get it too, but on a fresh Kubuntu 20.10!
"
1742810,2019-11-01 21:01:51 UTC,"I'm not certain which specific part of the code this bug is referring to needing fixed, but here's the current state of mktemp usage in the usd-importer repo:"
1742810,2018-01-12 20:02:14 UTC,"On Thu, Jan 11, 2018 at 10:53 PM, ChristianEhrhardt
<email address hidden> wrote:

> If context of the execution dir is breaking us we would want/need fully
> context depleted environments - like containers. But that pretty fast
> gets pretty heavy as we already see on build.
"
1742810,2018-01-12 06:53:53 UTC,If context of the execution dir is breaking us we would want/need fully context depleted environments - like containers. But that pretty fast gets pretty heavy as we already see on build.
1742813,2021-01-28 16:15:47 UTC,It appears that this is likely to have been fixed as of the victoria release (according to https://review.opendev.org/c/openstack/glance/+/754748 and https://review.opendev.org/c/openstack/glance/+/756865/1#message-daaca94a08228abfa2b6f41b21255a416cc42c4c).
1742813,2018-01-11 22:55:46 UTC,"In the Tasks and Images controllers, when an API request comes in, a task is created and a spawn_n is called on the 'tasks_eventlet_pool'. In the pike devstack, these tasks remain stuck in pending. I added a waitall() right after the spawn_n() call, and the tasks run to completion. This happens whether the taskflow engine is being run in serial or parallel mode. It does not occur when glance is run in the screen-based devstack."
1742813,2018-02-22 15:21:33 UTC,"Matt is correct, it's not a screen thing.  The key thing is that everything works when you run Glance in its eventlet server mode.  I've got a patch up to make this the default in devstack: https://review.openstack.org/#/c/545483/"
1742813,2018-03-05 11:55:22 UTC,I'm thinking we might be able to use a different executor with the taskflow engine to fix this. I have an attempt at that here: https://review.openstack.org/#/c/549743/1
1742813,2018-01-11 23:21:14 UTC,"Just a clarification devstack doesn't use screen anymore, it hasn't been the default for local use since early in Ocata (and even earlier for the gate), when it was deprecated, and all screen support was removed early in Pike. The bug here is not because of how the service is launched (screen vs systemd) it is because starting in pike glance api is not being with the standalone eventlet server anymore."
1742815,2020-07-04 11:51:13 UTC,libpng12-0:i386  1.2.50-2+deb8u3
1742818,2018-01-12 00:03:49 UTC,The error message is:
1742818,2018-01-12 00:30:04 UTC,This change was made by a bot.
1742818,2018-01-12 00:55:16 UTC,"Thanks Seth,"
1742818,2018-01-17 03:34:17 UTC,"Yes, I think that would get you to the point of finding out if this workaround lets you continue or not."
1742819,2018-01-11 23:41:15 UTC,"the route was running fine all day.
then it just stopped.
thanks
jim"
1742819,2018-01-18 14:04:43 UTC,The PRR is known for being unreliable. It has several issues in it's files. This may or may not be an OR problem.
1742819,2018-01-18 21:28:18 UTC,"hi mark,
i removed the route and re-installed it again.
so far its working.
thank you"
1742821,2018-01-12 00:07:37 UTC,I attempted to do this locally in a devstack environment and I was not able to reproduce this at all. Setting the number of processes to launch to 10x the number of cores did not cause anything to fail. (I eventually exhausted all of my VM's memory but then the OOMkiller just killed things)
1742823,2020-09-10 14:21:54 UTC,Closing because INVALID: Incomplete.
1742828,2018-11-12 11:25:49 UTC,Also affects me. I've rewritten the whole bug report to improve it.
1742828,2020-06-14 02:44:55 UTC,Closing as part of migration of bugs to GitLab. Issue was opened here: https://gitlab.com/inkscape/inkscape/-/issues/359
1742828,2019-01-24 00:48:31 UTC,"Just discovered that the values I published a few hours ago are dependent to the Custom size and Scale (Document Properties). Not sure why and how but here is what I used, so that you can reproduce the bug:
Width 36 in, Height 24 in, and Scale x and Y: 1.00"
1742828,2019-01-23 21:08:07 UTC,"Same bug found with Inkscape 0.92.4 (latest as of today), running Windows 10 Pro."
1742830,2020-09-18 15:28:14 UTC,Closing because INVALID.
1742830,2018-03-05 01:08:00 UTC,"(to keyboard shortcut documentation, that is)"
1742830,2018-03-05 01:07:28 UTC,Added in https://gitlab.com/inkscape/inkscape-docs/documentation/commit/79b9dc1c4be8f9fe00910aca30d95b26f3d747a8
1742830,2018-01-12 23:56:08 UTC,"Using the up/down arrows for ""search next"" without a button is bad user interface design. If there would be a button like in any other program, the user experience would be so much better."
1742830,2018-01-12 19:49:41 UTC,"- : collapse currently selected element.
+ : also expands, but not the full tree, only the next level."
1742830,2018-01-12 19:48:23 UTC,"This isn't documented anywhere - unless you're asking for arrows being added to the interface, maybe?"
1742830,2018-01-12 19:21:57 UTC,"Use up / down arrows. As long as the Find field is open, they will jump to the next result."
1742852,2020-05-01 17:43:04 UTC,"Hi everybody,"
1742852,2018-12-09 21:14:18 UTC,"Hi,"
1742852,2018-11-23 10:59:41 UTC,"Re above comment, the UX533 also has the ALC294. I should have made this clear in that comment."
1742852,2018-11-22 22:43:13 UTC,"Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485, as I'm seeing the same symptoms, with the same temporary improvement enabling the power save as described above."
1742852,2020-05-01 17:22:43 UTC,"Hi everyone!
Asus Zenbook UX533FTC has the same problem with Ubuntu 20.04 with Windows 10 in dual boot."
1742852,2018-05-12 02:32:47 UTC,"I'm having the same issue. It seems we have the same laptop, based on what you attached.
I think I have found some interesting details about this bug:
1) In my case, i'm dual booting with windows 10, the problem only occurs after booting into windows and then rebooting into ubuntu. A shutdown + start straight to ubuntu fixes the problem (I think this is why your sound came back). So, although this is a workaround, there is definitely something wrong. I describe the problem here in more detail https://askubuntu.com/q/1032543/172846
2) I think the problem is the windows Realtek drive putting the sound card in some kind of stand-by state that the linux driver cannot wake up from. Some people have reported with similar problems that downgrading the windows Realtek driver fixes the issue, but to me it is still clear that the problem is the linux driver not waking up correctly the device, not the windows driver using a feature intended to save power
3) With this idea that the problem is power-saving, I enabled the power-save feature in the linux driver: `echo 10 >/sys/module/snd_hda_intel/parameters/power_save`
If I wait 10 seconds and then trigger a sound (i'm using a terminal's bell), the sound now works, it sounds weird at first (crackling) but it keeps improving after like 2 seconds where it sounds AFAICT normal, but then 2 seconds later the volume starts to decrease like when speakers are running out of battery until sound is completely gone again. So it seems the linux drivers are somewhat capable of waking up the sound card, but not permanently"
1742852,2018-04-10 19:34:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742852,2018-01-12 23:01:31 UTC,the sound came back 24h after with no changes done... I have no clue...
1742852,2020-05-01 14:18:52 UTC,"Hi there.
Asus UX563FD has the same problem on Ubuntu 20.4 with Windows dual boot."
1742852,2018-12-20 06:32:30 UTC,Kernel version 4.19.10 has the fix.
1742852,2020-05-01 14:17:18 UTC,"Hi there.
Asus UX563FD has the same problem on Ubuntu 20.4 with Windows dual boot."
1742852,2020-05-02 18:41:54 UTC,"Asus Zenbook UX533FTC, Ubuntu 20.04 fresh install, dual boot with Windows 10. Same was on Ubuntu 19.10 (dualboot). I already live half a year without sound on my laptop. Can uninstalling Windows to single-boot Ubuntu can help?"
1742852,2020-05-07 23:52:04 UTC,"Hi! I have an Asus Zenbook UX331 with Linux Mint 19.3 Kernel version 5.3.0-51 and dual-boot with Windows 10. This laptop has the same audio device (ALC 294) as this thread is about. My problem is that the audio speakers sound kind of clunky and distorted after dual-booting from Windows to Linux. A fully shutting down and then booting in linux solves the issue but I need to boot on W10 first as I use Asus Battery Health Charging to cap my battery percentage on 60 so I can keep my laptop plugged in.
I've tried many workarounds and possible fixes but the only way I could fix this was uninstalling Realtek Audio Device and High Audio Definition Device on Windows 10. Altough this is not a permanent fix as it sometimes doesn't work (probably because windows reinstall this drivers when it detect they aren't installed) and I have no sound in Windows without this drivers.
I would be more than happy to provide further info about my system in order to know what is really happening."
1742852,2020-05-08 06:18:25 UTC,"Update! I think I've solved the issue following this comment https://askubuntu.com/a/811461/815718.
I've installed both pulseaudio-equalizer and also-oss and after that it seems audio start working correctly after dual-booting on both Linux and Windows. Hopes this solve my issue definitely (as I am not 100% sure this was the solution that worked, need further testing) and that it helps other people trying this solution!"
1742862,2018-02-06 14:08:20 UTC,"Hi Bill,"
1742862,2018-01-14 18:49:13 UTC,I was able to work around this by disabling quotas on the btrfs volume.
1742865,2020-10-12 07:41:35 UTC,"since I migrated to 18.04 Fn keys all work, Flip screen and Touch keyboard work"
1742865,2020-10-12 07:14:23 UTC,This is two separate issues:
1742865,2020-10-12 07:39:37 UTC,"Hello Daniel,"
1742872,2018-06-08 09:47:28 UTC,"Change abandoned by chenxiangui (<email address hidden>) on branch: master
Review: https://review.openstack.org/533105"
1742872,2018-01-12 07:18:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533105"
1742876,2018-01-15 04:37:14 UTC,"Test 1:
With /etc/systemd/system/epmd.socket as
-----------------------------------
[Unit]
Description=Erlang Port Mapper Daemon Activation Socket"
1742876,2018-02-13 12:59:49 UTC,I found that:
1742876,2018-01-13 15:14:32 UTC,I'll try changing the above file to default and retry on Monday.
1742876,2018-02-19 03:01:26 UTC,But the service does not start on system startup. Any advice?
1742876,2018-02-19 02:54:13 UTC,"Yes this works. Service starts as expected.
On my configuration, /etc/systemd/system/epmd.socket.d/ was not available, so I had to create it."
1742876,2018-01-13 15:12:21 UTC,"The /etc/hosts file contains controller and localhost entries, and they are correct.
Had done the installation twice after reformatting. Could only start rabbitmq after editing the /etc/systemd/system/epmd.socket file. First time set the line as
    ListenStream=:::4369
Then it worked. But wanted to specify the IP so the second time edited as in the first post."
1742876,2018-01-12 17:37:31 UTC,"I can't reproduce this problem on SLES-12-SP3. Did you add all necessary entries to your `/etc/hosts` file? I found that if those entries are not correct, then rabbitmq refuses to start."
1742879,2020-04-11 16:05:49 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1742879,2018-01-12 23:50:23 UTC,"Thanks, using the Objects panel works. However, the workflow is so-so and it would be more intuitive if it ""just works"" when highlighting in the XML editor."
1742879,2018-01-12 16:30:49 UTC,"NB: the above also works with just the Find tools, once nested object(s) are ""found"", selecting them in the Objects panel allows direct transform in the viewport."
1742879,2018-01-12 16:28:05 UTC,"I can replicate this behavior. However, I suggest using the Objects panel in conjunction with the XML editor to control objects in the viewport."
1742885,2018-03-03 08:30:24 UTC,"This is actually documented:
http://lxml.de/FAQ.html#how-do-i-use-lxml-safely-as-a-web-service-endpoint"
1742888,2018-02-22 00:55:30 UTC,"Change abandoned by zhufl (<email address hidden>) on branch: master
Review: https://review.openstack.org/533128
Reason: Yes with Tempest change, this bug no longer exists, so just keep it as is"
1742903,2020-06-16 21:14:53 UTC,"The needrestart package has some sophisticated logic to detect whether the system needs to be booted to get an updated microcode applied (needrestart -w is how it can be invoked directly to report on microcode status). The needrestart package is a bit much to be included as a dependency or even a recommends for the intel-microcode package, but re-using some of the logic might be appropriate."
1742903,2018-01-12 15:51:28 UTC,This will be taken care of because the microcode will be pulled in as a dependency on the kernel containing mitigation patches and that will require the reboot.
1742903,2018-01-12 16:48:27 UTC,"For awareness, the kernel team is preparing updates including a package dependency on the intel-microcode.  We have not pushed that out yet due to reported regressions with the intel-microcode updates:"
1742903,2018-03-22 15:35:55 UTC,"but it may need to be more smart; e.g. check the new microcode revisions vs currently loaded; to see if there was an update to microcode for this system, actually"
1742903,2018-03-22 17:04:28 UTC,"On Thu, 22 Mar 2018, Dimitri John Ledkov wrote:

> but it may need to be more smart; e.g. check the new microcode revisions
> vs currently loaded; to see if there was an update to microcode for this
> system, actually
"
1742903,2018-03-26 08:50:13 UTC,Something like:
1742903,2018-03-26 12:07:39 UTC,"On Mon, 26 Mar 2018, Dimitri John Ledkov wrote:

> Something like:
>
> [[ `iucode_tool -s $(sudo iucode_tool --scan-system=2 2>&1 | sed
> 's/.*\(0x.*\)$/\1/') -l /lib/firmware/intel-ucode/ | sed -n 's/.* rev
> \(0x....\),.*/\1/p'` -eq `sudo cat
> /sys/devices/system/cpu/cpu0/microcode/version` ]] || echo 'Trigger
> reboot'
>
> should be good enough.... with bashism... as the kernel file is 0x1f,
> yet the tool reports 0x001f.
"
1742903,2018-03-26 15:59:18 UTC,"On 26 March 2018 at 13:07, Henrique de Moraes Holschuh
<email address hidden> wrote:

> On Mon, 26 Mar 2018, Dimitri John Ledkov wrote:
>> Something like:
>>
>> [[ `iucode_tool -s $(sudo iucode_tool --scan-system=2 2>&1 | sed
>> 's/.*\(0x.*\)$/\1/') -l /lib/firmware/intel-ucode/ | sed -n 's/.* rev
>> \(0x....\),.*/\1/p'` -eq `sudo cat
>> /sys/devices/system/cpu/cpu0/microcode/version` ]] || echo 'Trigger
>> reboot'
>>
>> should be good enough.... with bashism... as the kernel file is 0x1f,
>> yet the tool reports 0x001f.
>
> Bashisms aren't a problem, as long as the script declares to be a bash
> script.  Those numbers have to be properly parsed, so using bash is a good
> solution.  They are guaranteed to be 32-bit, too, which doesn't get in
> the way (bash math is 32-bit).
>
> The use of --scan-system=2 is a problem (slow when there are many CPUs,
> requires a kernel module to be loaded), and I don't understand why the
> whole dance to feed its output to iucode-tool -s.  Looks like just
> ""iucode_tool -S"" would do what is required *and* handle systems in
> mixed stepping configurations better...
>
"
1742903,2019-01-17 16:17:27 UTC,"I don't think this is high anymore.
Kernel now depends and pulls in microcode packages, and kernel does trigger reboot require notification.
Imho, it is sufficient enough to require reboot from the kernel alone. Since there are frequent enough kernel updates."
1742910,2018-01-12 11:11:56 UTC,Confirmed on Fedora 25 as well.
1742910,2018-01-12 11:12:21 UTC,The issue seems to be that the threads are all stored in the mainwindow which isn't always there.
1742911,2018-01-19 00:24:09 UTC,"Reviewed:  https://review.openstack.org/531213
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=ec5244fd24694c7c0daf7da9b26708b52944a6c9
Submitter: Zuul
Branch:    master"
1742911,2018-02-06 19:11:45 UTC,"Reviewed:  https://review.openstack.org/531841
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=165d55ff2ea45dee700d87176bdb0f164ae513fa
Submitter: Zuul
Branch:    master"
1742911,2018-02-06 19:11:55 UTC,"Reviewed:  https://review.openstack.org/531842
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=44da50594d3a5b5709bacaed2f0ec3ccb40e104c
Submitter: Zuul
Branch:    master"
1742911,2018-02-07 14:15:45 UTC,"Reviewed:  https://review.openstack.org/531843
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=6be85498dcf5c89d66e3e2370677a9a3681ef311
Submitter: Zuul
Branch:    master"
1742911,2018-02-07 14:27:15 UTC,"Reviewed:  https://review.openstack.org/531932
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=68b31f13b6094567cc81af8b30d043d81254f4bd
Submitter: Zuul
Branch:    master"
1742911,2018-02-15 18:24:45 UTC,"Reviewed:  https://review.openstack.org/532601
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=60d347e561cb5985ff1aa6b297fa795b88376680
Submitter: Zuul
Branch:    master"
1742911,2018-02-10 14:45:40 UTC,"Reviewed:  https://review.openstack.org/531845
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=c5a02c3edb3049b77a50fc5e80f371eb7c631887
Submitter: Zuul
Branch:    master"
1742911,2018-02-13 15:00:41 UTC,"Reviewed:  https://review.openstack.org/532292
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=4a4d401abc4681834d16d833b145cdd94ca7f24c
Submitter: Zuul
Branch:    master"
1742911,2018-02-13 16:23:02 UTC,"Reviewed:  https://review.openstack.org/532293
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=006e43b6d1bdc7b04f8d2928f8ff07e481eaf8ae
Submitter: Zuul
Branch:    master"
1742911,2018-02-13 21:25:02 UTC,"Reviewed:  https://review.openstack.org/532294
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=cef653e276cfade4b33e602f90cc876fb2255b52
Submitter: Zuul
Branch:    master"
1742911,2018-02-15 11:16:48 UTC,"Reviewed:  https://review.openstack.org/532295
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=aab67dd41672c7231796293bf9020c0be489f6ea
Submitter: Zuul
Branch:    master"
1742911,2018-02-15 16:46:36 UTC,"Reviewed:  https://review.openstack.org/532600
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=cbe561335baf4f41542c33690eae6c49dd06acb8
Submitter: Zuul
Branch:    master"
1742911,2018-02-21 14:12:27 UTC,"Reviewed:  https://review.openstack.org/532602
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=db86e67747e9ef933ffa738f89c17deb01b9b737
Submitter: Zuul
Branch:    master"
1742912,2019-12-05 16:01:16 UTC,"I installed gnome-terminal and got 'unconfined'. So I could view the home directory of another user, but if the directories had no permissions for Other group, I could not view the contents in guest session. So I think a better solution than disabling guest sessions is to make proper default permissions for directories under /home directory."
1742912,2018-02-17 23:26:11 UTC,I just posted this:
1742912,2018-03-01 21:58:50 UTC,Please note that the simple test ( cat /proc/self/attr/current ) can be misleading.
1742912,2018-03-01 22:45:53 UTC,"I figured out why the simple test didn't work - when I first installed Ubuntu 18.04, gnome-terminal wouldn't accept any keyboard input, I assumed it was just a pre-alpha bug and installed terminator.  Installing terminator switched itself to the default including launching with ctrl-alt-t , and terminator does get apparmor restricted.    When I paste in ""cat /proc/self/attr/current"" into a gnome-terminal it shows unconfined."
1742912,2019-12-04 22:56:20 UTC,"I tested this on Xubuntu 18.04.3, and xfce4-terminal gives the expected output (like xterm as well). I do not see how this should depend on the terminal application used. I guess it is pretty safe to use guest session in Xubuntu."
1742912,2020-11-02 21:33:41 UTC,The result on Ubuntu 20.04.1 is 'unconfined'.
1742921,2018-07-15 12:45:56 UTC,"Thanks for putting this feature request into an issue. I don't plan to implement this feature, but I'm marking the issue as confirmed and I will accept a pull request that adds this feature."
1742921,2019-04-29 19:28:46 UTC,"I've had a go at this, with html.parser. Patch attached (unfortunately I'm less successful trying to get bzr and launchpad working)."
1742921,2019-07-21 16:38:02 UTC,"Patch updated for Beautiful Soup 4,8,0"
1742921,2019-07-21 19:59:39 UTC,"Chris,"
1742921,2019-07-22 19:20:57 UTC,Great to see it committed. Thanks for finishing it off. I knew the patch wasn't 100% ready but as the  idea turned out to be relatively simple to implement thought it was worth trying to get it going.
1742921,2019-09-12 09:41:27 UTC,"""we use the target parser interface, which doesn't provide any access to this information."""
1742921,2019-10-05 21:36:31 UTC,I filed a feature request with lxml here: https://bugs.launchpad.net/lxml/+bug/1846906
1742925,2018-04-11 13:37:37 UTC,the symbol toolbar doesn't work on ubuntu 18.04 as well
1742925,2018-04-11 13:38:55 UTC,minor issue: equalx doesn't appear in gnome-search
1742936,2018-01-12 20:20:43 UTC,I looked at this with Ihar for a while today and didn't find any smoking gun in the log files.
1742936,2018-01-12 21:16:54 UTC,"Re: #1, Upstream policy will not allow CI jobs to be stopped for investigation.
However you can you use the recreate script to produce the exact same environment in RDO-Cloud"
1742936,2018-01-12 22:09:26 UTC,Tried https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset016-master/b09f8f0/reproducer-quickstart.sh
1742936,2018-01-16 00:54:14 UTC,Note that we hit it in pike promoted repo as well: http://logs.openstack.org/80/533380/10/check/tripleo-ci-centos-7-scenario001-multinode-oooq-container/4c7b30c/
1742936,2018-01-16 06:24:30 UTC,"Reviewed:  https://review.openstack.org/533380
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=fa02a8f8633b682ba2042ac7fb26d76453cfe65a
Submitter: Zuul
Branch:    stable/pike"
1742936,2018-01-17 17:24:18 UTC,"This bug first appeared on 10th of January, trying to get a diff of changes from the builds on 9th"
1742936,2018-01-18 22:12:56 UTC,I posted https://review.openstack.org/535488 and https://review.openstack.org/535491 to collect more info on failure. We should hook them into tripleo gate and see if they reveal anything interesting. How do we achieve that?
1742936,2018-01-22 23:48:12 UTC,"Reviewed:  https://review.openstack.org/536395
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=5c900a50a4e3087e8e95b8fcd3e9f1acaaa02172
Submitter: Zuul
Branch:    master"
1742936,2018-01-19 17:17:48 UTC,"Nevermind my latest comment here, it was for another similar issue in barbican plugin."
1742936,2018-01-18 23:18:13 UTC,"apetrich mentioned a ceph issue [1] might be connected to this today in IRC. If that is the issue, the following from [2] might help. If it's not a ceph-mon issue, then disregard."
1742941,2019-08-05 14:14:58 UTC,"Also, removing ""18.10"" from the title, as this release has EOLed."
1742941,2018-08-20 13:55:36 UTC,"IBM, 18.10 feature freeze is on the 23rd of Aug, any news on the upstream status of this patch?"
1742941,2018-04-02 13:00:20 UTC,"------- Comment From <email address hidden> 2018-04-02 08:58 EDT-------
(In reply to comment #45)

> IBM, Can you please update this bug when this patch lands upstream?
"
1742941,2018-03-05 15:10:43 UTC,"IBM, Can you please update this bug when this patch lands upstream?"
1742941,2018-01-30 07:41:20 UTC,this is not yet committed upstream (2018-01-30).
1742941,2019-08-05 14:14:00 UTC,<email address hidden>: has there been any outcome from the upstream talks with Mark Adler?
1742941,2018-01-18 03:59:45 UTC,"------- Comment From <email address hidden> 2018-01-17 22:56 EDT-------
code submitted upstream: https://github.com/madler/zlib/pull/335"
1742941,2018-01-12 13:29:55 UTC,"------- Comment From <email address hidden> 2018-01-12 08:22 EDT-------

>'ve created the following which hopefully contains all the features
> required to be upstream friendly.
>
> https://github.com/grooverdan/zlib/commits/power_crc32_c_version
>
> Most importantly compared to the previous PR, it contains the right crc32
> constants.
>
> If you see anything that upstream/distros or anyone else might nit about
> then please tell me (on github or here). The upstream isn't very active so
> presenting something idea on day one is my goal.
>
> Note 1: no clang currently due to...
>
> Note 1a: crc32_vpmsum: __builtin_pack_vector_int128 and
> __builtin_crypto_vpmsumw/__builtin_crypto_vpmsumd - need to review
> https://github.com/racardoso/crc32-vpmsum/commit/
> 97210b9188916eb46377b5eb927ae337948bf016 properly (sorry Rogerio, from
> memory it needs to compile fail for clang BE rather than generate wrong
> results).
>
> Note 1b: clang - no __builtin_cpu_supports (
> https://bugs.llvm.org/show_bug.cgi?id=35898 ) so I might fall back to
> getauxval
>
>
> Is there an better define than __powerpc__ to check in configure to detect
> Power8+ only?
>
> Other suggestions welcome.
"
1742941,2018-01-12 13:20:20 UTC,Default Comment by Bridge
1742941,2019-04-08 23:09:29 UTC,"------- Comment From <email address hidden> 2019-04-08 18:59 EDT-------
Significant background talks are taking place with Mark Adler about the maintenance of zlib for arch specific performance."
1742941,2018-08-20 18:59:33 UTC,"------- Comment From <email address hidden> 2018-08-20 14:53 EDT-------

> IBM, 18.10 feature freeze is on the 23rd of Aug, any news on the upstream
> status of this patch?
"
1742941,2019-04-08 14:27:47 UTC,"Looks like this patch is still waiting to be merged upstream, looking at this link: https://github.com/madler/zlib/pull/335 Could you please advice if this is being considered to be merged upstream by the maintainer?"
1742941,2020-02-07 03:20:37 UTC,"------- Comment From <email address hidden> 2020-02-06 22:14 EDT-------
Where we are up to is there is a small amount of progress in the zlib-devel (https://zlib.net/mailman/listinfo/zlib-devel_madler.net) however nothing explicit on or off list about merging arch specific patches (from any architecture vendor)."
1742941,2020-03-02 12:57:51 UTC,"The crc32 performance optimization for P8 were added to zlib version 1.2.11.dfsg-2ubuntu1 (thx to doko) and landed already in proposed:
""zlib | 1:1.2.11.dfsg-2ubuntu1  | focal-proposed  | source""
Hence changing the status of this ticket to Fix Committed."
1742941,2020-03-10 23:04:17 UTC,This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu1
1742943,2018-01-12 14:48:26 UTC,"Searched the web for the problem, seems like it's been broken for the last six years:"
1742954,2018-05-08 08:29:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742956,2018-01-12 16:00:41 UTC,"I've upgraded two computers from 17.04 to 17.10, and in both cases quassel hid the menu. So it might be that something in the version change causes it to happen."
1742956,2018-01-12 14:29:46 UTC,"(sorry for the bmp, shutter decided that was to be the new default.)"
1742956,2018-01-12 14:45:23 UTC,"> I've just upgraded to artful, and quassel has no menu bar with which to access the menu items. Tapping alt doesn't help.
"
1742956,2018-01-12 14:53:22 UTC,"Thanks, that works for me too. That is not discoverable, however. Unless you can get to the keyboard shortcuts. Which are in the menu."
1742956,2018-01-12 15:08:11 UTC,"On 12/01/18 14:53, Robin Sheat wrote:

> Thanks, that works for me too. That is not discoverable, however. Unless
> you can get to the keyboard shortcuts. Which are in the menu.
>
> In addition, no menu is a bad default.
"
1742956,2018-01-15 16:58:20 UTC,"The menu can also be re-enabled from the context menu in the chat view, i.e. right clicking the chat background.
This bug report is of course still valid, though."
1742957,2018-02-08 13:21:16 UTC,This issue was fixed in the openstack/bifrost 5.0.0 release.
1742957,2018-01-12 14:37:08 UTC,Cloud-init version selection: https://github.com/number5/cloud-init/blob/ubuntu/0.7.9-0ubuntu2/cloudinit/sources/helpers/openstack.py#L172
1742957,2018-02-02 21:04:12 UTC,"Mark's change to fix this recently landed, marking fix committed."
1742957,2018-02-03 15:29:51 UTC,Here's the review for the (merged) fix: https://review.openstack.org/#/c/533196/.
1742962,2018-05-02 12:04:00 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1742962,2018-02-15 23:53:27 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1742962,2018-02-09 07:13:53 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1742962,2018-01-31 13:32:05 UTC,"Reviewed:  https://review.openstack.org/536936
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b5006d45af0df1720053c8f7870369022447a2f
Submitter: Zuul
Branch:    stable/ocata"
1742962,2018-01-30 20:43:33 UTC,"Reviewed:  https://review.openstack.org/536934
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=274e2e61187030332d5d427d2272b48a26a0012a
Submitter: Zuul
Branch:    stable/pike"
1742962,2018-01-23 19:19:35 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/536936"
1742962,2018-01-23 19:17:45 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/536934"
1742962,2018-01-27 17:16:24 UTC,"Reviewed:  https://review.openstack.org/533210
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d4377c2d537ea998ed96cc8d7071877eefab994f
Submitter: Zuul
Branch:    master"
1742963,2018-01-12 15:29:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533212"
1742963,2018-02-21 20:49:10 UTC,This was a regression in Queens due to privsep.
1742963,2018-02-21 21:01:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/546778"
1742963,2018-02-21 22:38:58 UTC,"Reviewed:  https://review.openstack.org/533212
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1f5fe3190bf2e0987945a6ef9ec430673c9fa736
Submitter: Zuul
Branch:    master"
1742963,2018-02-22 08:18:25 UTC,"Reviewed:  https://review.openstack.org/546778
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5a646d82bad6a71da28296e3ab06dc5ce2c0f716
Submitter: Zuul
Branch:    stable/queens"
1742963,2018-02-22 18:28:00 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc3 release candidate.
1742963,2018-04-20 13:15:00 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1742970,2018-01-12 15:55:29 UTC,"It's really nerving, because I couldn't work on the GUI and had to make a hard shutdown.
I use this system for my students."
1742970,2018-01-12 16:15:38 UTC,Thank you for your fixing
1742972,2018-01-13 04:11:52 UTC,"Hi, Mark"
1742972,2018-01-13 08:34:14 UTC,"Hi Zhangfei,"
1742972,2018-01-13 08:36:02 UTC,I can't actually see installation instructions for Grub in the inspector install guide. It does have instructions for UEFI via iPXE.
1742972,2020-01-30 18:16:34 UTC,"Mark, I believe this got fixed in the meantime."
1742972,2020-01-31 09:33:01 UTC,"I think it was fixed for iPXE, but not grub."
1742972,2018-01-14 08:52:20 UTC,"Hi,"
1742972,2018-01-14 01:51:46 UTC,"Hi, Mark"
1742973,2019-12-09 03:09:32 UTC,"Hello,
this kernel (4.13) has reach its end-of-life.
Please feel free to open a new issue with a newer kernel.
Thank you."
1742973,2018-01-15 11:18:58 UTC,I can confirm this issue having Yoga 500 ISK (Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz).
1742973,2018-01-14 14:40:54 UTC,I have the same issue on my Yoga 11e 3rd gen. The touchscreen still works but no kb/trackpad.  Everything works when using the 4.10.0 kernel.
1742973,2018-01-13 14:11:39 UTC,Updated my son's Lenovo Yoga 11e and the bug just hit his machine as well.
1742973,2018-01-12 21:02:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1742973,2018-01-12 21:02:27 UTC,"I also encountered this issue on a Lenovo ThinkPad 11e. I also encountered this issue when upgrading to 17.10, which is also on 4.13."
1742974,2018-03-06 11:20:14 UTC,"Hi Nishitha,"
1742974,2018-03-06 10:46:54 UTC,"Hi Zdohnal,"
1742976,2018-01-12 17:18:36 UTC,here's a sequence of operations that shows the problem:
1742976,2018-01-12 16:34:47 UTC,"Huh, I just realized if I run `snapcraft logout`, ~/.config/snapcraft/snapcraft.cfg is actually still there, but only contains my staging login now."
1742977,2018-10-29 12:32:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/613917"
1742997,2019-09-24 07:45:04 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1742997,2019-07-29 20:20:18 UTC,Note that this bug occurs on all versions of GNOME Software.
1742997,2019-07-29 20:10:44 UTC,I've managed to find a bug that stops apps appearing in the installed list when they are *reinstalled*.
1742997,2019-05-06 14:57:02 UTC,"On a fresh installed Ubuntu 19.10 Eoan with Gnome software 3.30.6-2ubuntu3
I installed: synaptic, gparted, Gnome-tweaks, stellarium, GIMP
then I Switch to the ""Installed"" tab and:
ONLY Gnome-tweaks and stellarium are visible as installed
also closing and restarting Gnome software does not change the situation
killing gnome software and restarting solves the problem"
1742997,2019-04-09 01:21:53 UTC,"I was reproducing this, but when I added instrumentation it started working. It does reproduce in a VM, so will keep investigating. The code that adds the installed apps to the installation page seems fairly robust, so not sure what might be breaking it."
1742997,2018-11-07 15:42:12 UTC,"Can still reproduce on bionic, not on cosmic. Killing gnome-software and running it again is enough to ""fix"" the issue (because the list of installed applications is being refreshed at startup)."
1742997,2018-08-08 13:12:39 UTC,I can reliably observe the issue on bionic. Not on cosmic.
1742997,2018-08-08 12:32:18 UTC,Can someone test if this still an issue?
1742997,2019-09-18 11:47:27 UTC,Confirmed in bionic that gnome-software 3.28.1-0ubuntu4.18.04.12 after removing and re-installing moon-buggy it shows in the installed page.
1742997,2018-01-17 15:01:35 UTC,Could be an issue in the aptd plugin or the aptcc packagekit backend...
1742997,2018-01-17 12:56:44 UTC,"I am using Ubuntu 18.04 with gnome-software-3.26.3-2ubuntu1. I am not sure if this is an upstream issue, it does not happen on any of my Fedora machines."
1742997,2018-01-17 12:19:20 UTC,what Ubuntu serie and gnome-software version are you using?
1742997,2018-01-17 12:18:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1742997,2019-07-29 20:22:00 UTC,https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/291
1742997,2019-09-17 14:05:52 UTC,"Hello AsciiWolf, or anyone else affected,"
1742997,2019-09-24 07:55:04 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.12
1742998,2018-01-18 09:44:06 UTC,"4.4.0-10011.11 - aws
Regression test CMPL."
1742998,2018-01-22 19:17:03 UTC,This bug was fixed in the package linux-aws - 4.4.0-1011.11
1742998,2018-01-22 20:02:16 UTC,The package has been published and the bug is being set to Fix Released
1743001,2018-01-18 09:47:33 UTC,"4.4.0-1049.58 - aws
Regression test CMPL."
1743001,2018-01-22 20:02:53 UTC,The package has been published and the bug is being set to Fix Released
1743001,2018-01-22 19:16:12 UTC,This bug was fixed in the package linux-aws - 4.4.0-1049.58
1743001,2018-01-16 17:07:56 UTC,http://people.canonical.com/~kernel/status/adt-matrix/xenial-linux-meta-aws.html
1743002,2018-01-29 16:01:02 UTC,The package has been published and the bug is being set to Fix Released
1743002,2018-01-29 14:55:36 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1017.22
1743002,2018-01-29 14:18:31 UTC,Regression tests results are good.
1743002,2018-01-16 17:05:47 UTC,http://people.canonical.com/~kernel/status/adt-matrix/xenial-linux-meta-kvm.html
1743007,2018-01-16 17:01:17 UTC,"Hello Mike, I really wouldn't want to see a new UI for this, at least for the pull list portion of it.  One of my goals is for it to work without any new instructions/training being needed for staff.  They already run their pull list on a regular basis so this could be rolled out easily."
1743007,2018-01-12 18:16:52 UTC,"Josh,"
1743008,2018-01-15 21:35:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533803"
1743008,2019-02-25 21:40:02 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/533803"
1743008,2018-01-23 19:20:16 UTC,"Sean, I let the ibm storage driver team know about this and assigned it back there. Thanks."
1743008,2018-01-15 21:41:18 UTC,Drivers should not be using names for volume identification.
1743017,2018-03-16 15:36:21 UTC,duplicate of #1720205
1743017,2018-01-12 18:20:14 UTC,Attached text file containing the diagram.
1743026,2018-01-15 18:44:32 UTC,"Just a note the patch in #2 is most likely not correct, just a way for me to narrow down the problem. Perhaps we missed a patch (or there is a fix) that makes nbd_is_connected to the correct thing."
1743026,2018-01-12 19:30:23 UTC,"This patch seems to fix the issue:
```
diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index 5f807a6..b761971 100644
--- a/drivers/block/nbd.c
+++ b/drivers/block/nbd.c
@@ -98,11 +98,6 @@ static inline struct device *nbd_to_dev(struct nbd_device *nbd)
        return disk_to_dev(nbd->disk);
 }"
1743026,2018-01-12 19:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743026,2019-01-15 12:14:12 UTC,"there is a way to workaround it, use partprobe"
1743027,2019-12-15 11:11:34 UTC,I have this same problem on Ubuntu 19.10 on ThinkPad X1 Carbon 7th gen.
1743027,2018-11-02 05:31:34 UTC,"Within the 4 computer I have running Ubuntu, only one, my Toshiba Satellite Laptop with the current 4.15 Kernels available from the Ubuntu 16.04.5 and 18.04.1 Repositories fails to create the /dev/rtc device... NOTE: The 3 other Ubuntu Machine are not effected by this CONFIG_WDAT_WDT Bug..."
1743027,2018-10-30 18:36:24 UTC,"Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: Sony Corporation
        Product Name: SVS13A3W9ES
        Version: C60BRBTW
        Serial Number: 54528306-0000358
        UUID: E6F5C740-64C8-11E2-A592-3C0771848C83
        Wake-up Type: Power Switch
        SKU Number: 54528306
        Family: VAIO"
1743027,2018-03-12 17:10:24 UTC,A bug has been filed with the kernel developers here: https://bugzilla.kernel.org/show_bug.cgi?id=199033
1743027,2018-03-06 14:29:23 UTC,The issue is caused by CONFIG_WDAT_WDT which driver is stealing the RTC resources before the RTC driver is probed. Disabling CONFIG_WDAT_WDT will solve that issue.
1743027,2018-03-02 08:00:26 UTC,Can you do a kernel bisection?
1743027,2018-02-13 14:45:48 UTC,"Just tested again, and the problem still exists in kernel 4.16.0-041600rc1-generic.  I'll be sending that update to the kernel maintainers as well."
1743027,2018-10-30 18:35:33 UTC,This also affects my system in Ubuntu 18.04 LTS - very annoying!
1743027,2018-01-25 18:56:32 UTC,Here is the link to the email sent to the maintainers list: https://marc.info/?l=linux-rtc&m=151683917607842&w=2
1743027,2018-01-23 14:19:16 UTC,apport information
1743027,2018-01-23 14:19:17 UTC,apport information
1743027,2018-01-23 14:19:20 UTC,apport information
1743027,2018-01-23 14:19:21 UTC,apport information
1743027,2018-01-23 14:19:22 UTC,apport information
1743027,2018-01-23 14:19:24 UTC,apport information
1743027,2018-01-23 14:19:25 UTC,apport information
1743027,2018-01-23 14:19:27 UTC,apport information
1743027,2018-01-23 14:19:28 UTC,apport information
1743027,2018-01-23 14:19:29 UTC,apport information
1743027,2018-01-23 14:19:30 UTC,apport information
1743027,2018-01-23 14:19:31 UTC,apport information
1743027,2018-02-09 22:46:22 UTC,"Still no response from the kernel team.  After a week, I tested the newest daily build of the kernel, and the problem still exists.  Sent a follow-up email with that info, and haven't heard anything."
1743027,2018-01-25 00:17:04 UTC,I've followed the instructions in the Wiki page and sent the email to the maintainers.  I will update when I hear back from them.
1743027,2018-01-24 20:44:06 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1743027,2018-01-24 16:08:59 UTC,"Hi Joseph,"
1743027,2018-01-23 21:34:42 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1743027,2018-01-23 14:30:08 UTC,This change was made by a bot.
1743027,2018-01-23 14:19:35 UTC,apport information
1743027,2018-01-23 14:19:34 UTC,apport information
1743027,2018-01-23 14:19:32 UTC,apport information
1743029,2018-01-12 19:39:56 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f01fb3974e8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=<optimized out>, str=0x7f01fb397820 ""double free or corruption (!prev)"", ptr=<optimized out>, ar_ptr=<optimized out>) at malloc.c:5425
 _int_free (av=0x7f01e8000020, p=<optimized out>, have_lock=0) at malloc.c:4174
 __GI___libc_free (mem=<optimized out>) at malloc.c:3144
 operator delete (ptr=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/del_op.cc:49"
1743029,2018-01-24 09:46:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743033,2018-06-27 12:38:58 UTC,Unassigned. No activity during a few months.
1743041,2018-01-13 10:40:09 UTC,"Same as ""Bug 102929 - Kernel 4.13.1 breaks screen output"" at https://bugs.freedesktop.org.  Will probably be fixed in kernel 4.15."
1743041,2018-01-13 16:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743041,2018-03-13 05:44:07 UTC,Dupe of lp: #1724639?
1743041,2018-01-13 00:21:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1743041,2018-01-18 13:54:09 UTC,I tested the latest upstream kernel (v4.15-rc8) and the bug still exists.
1743041,2018-01-17 22:36:40 UTC,"OK, I'll do that."
1743041,2018-01-16 19:50:00 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1743041,2018-01-13 20:12:47 UTC,Can't run apport-collect as bug renders system inoperable.
1743041,2018-01-22 08:58:02 UTC,I've just tested 4.15-rc9 generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/.  It works now.
1743043,2020-07-02 11:09:00 UTC,"@Sebastien: No, I've not noticed the bug for a long while. It must have been fixed in later Ubuntu versions somehow."
1743043,2020-07-01 21:11:09 UTC,"Thank you for your bug report, is that still an issue in newer ubuntu versions?"
1743043,2018-02-28 14:29:15 UTC,thanks
1743043,2018-02-28 13:42:35 UTC,I filed it here: https://bugzilla.gnome.org/show_bug.cgi?id=793914
1743043,2018-01-18 15:20:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1743043,2020-07-02 14:45:57 UTC,"Thanks, closing the report then since it probably has been fixed by an update"
1743053,2018-01-16 19:30:48 UTC,I built a test kernel with commit db5ff909798e.
1743053,2018-01-13 00:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743053,2018-01-13 00:11:32 UTC,"No longs, this is an upstream fix from the vendor."
1743053,2018-01-16 18:09:37 UTC,I'll built a test kernel with commit db5ff909798e from linux-next.
1743053,2018-01-16 18:39:57 UTC,"I'll double check, but I don't think it's needed in linux-image-azure.  Do you have a link to the test kernel packages?"
1743053,2018-01-31 23:48:12 UTC,"Hi,"
1743053,2018-02-01 19:18:10 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089837.html"
1743053,2018-02-06 20:09:50 UTC,This bug was fixed in the package linux-azure - 4.13.0-1009.12
1743053,2018-02-08 00:26:25 UTC,"FYI, we are looking for this in the default Xenial kernel as well.  There are some bare metal systems in use that wouldn't be able to use the Azure kernel."
1743053,2018-02-08 00:51:15 UTC,"Yes, the SRU request noted in comment #7 is for Xenial and Artful."
1743053,2018-02-14 09:38:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1743053,2018-02-14 09:42:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1743053,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1743053,2018-02-21 18:58:26 UTC,This bug was fixed in the package linux - 4.4.0-116.140
1743070,2018-07-05 15:26:43 UTC,"Actually, this happens no matter the version of the gfortran compiler. I tried compiling it with gfortran 7 and 8, and have always this same error."
1743070,2018-07-19 08:46:23 UTC,"Hi I got the same error (see below) with gcc 4.4.7 (Red Hat 4.4.7-4).
However Roberto compiled it with gcc 5.4.0 (Ubuntu 16.04.10)."
1743070,2019-03-21 18:52:33 UTC,I was compiling libPSML and I ran on the same error.
1743070,2019-10-01 14:28:13 UTC,"I have released a new package version (libpsml-1.1.8) which uses a simpler declaration for the
EMPTY_ASSOC_LIST entity."
1743075,2018-01-13 06:25:39 UTC,attaching eng file as well
1743079,2018-08-02 03:51:31 UTC,I also have this bug on Ubuntu 18.04.1.
1743079,2018-08-02 03:55:37 UTC,"Snapd is not installed so I believe the bug is in Apparmor.
We are currently running Apparmor ""2.12-4ubuntu5 amd64"""
1743079,2018-01-18 16:07:27 UTC,"Dear IT worker,"
1743079,2018-03-20 04:17:24 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1743079,2018-08-21 06:52:48 UTC,"Hello,"
1743079,2018-08-21 00:59:13 UTC,"Snapd is not installed in our environment, it is explicitly removed if present."
1743079,2018-01-15 14:23:29 UTC,"Could you please try to ""sudo mkdir /var/lib/snapd/apparmor/snap-confine.d"" and see if this error goes away once this directory is created?"
1743079,2018-08-21 00:54:14 UTC,Typo in the line above.  Fix was:
1743080,2018-01-15 21:19:19 UTC,"Dear IT worker,"
1743087,2018-01-13 09:47:43 UTC,"StacktraceTop:
 ?? ()
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x73, hash_table=0x55f49487b110) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x55f49487b110, key=key@entry=0x73) at ../../../../glib/ghash.c:1153
 lookup_cached_xatom (atom=0x73, display=0x55f494867130) at ../../../../../gdk/x11/gdkproperty-x11.c:76
 gdk_x11_atom_to_xatom_for_display (display=0x55f494867130, atom=0x73) at ../../../../../gdk/x11/gdkproperty-x11.c:109"
1743093,2018-04-19 14:16:28 UTC,It appears you had a network problem that prevented downloading packages during the install.  Please try again.
1743094,2018-06-05 23:48:32 UTC,"Have a same bug on desktop PC
Motherboard HB7-Plus, 16Mb RAM, Intel i7-4770 3.4 CPU"
1743094,2018-06-05 23:42:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743094,2018-06-04 15:57:14 UTC,Is there any update on this issue? Hibernation works with kernel 4.10 but I can't keep using that forever...
1743094,2018-06-02 12:30:47 UTC,Small update to #139
1743094,2018-05-31 08:49:50 UTC,I can't wake from standby with linux-image-4.15.0-22-generic
1743094,2018-05-30 12:35:11 UTC,I have a variant of this problem that I can not find anywhere else:
1743094,2018-05-23 23:52:20 UTC,"Intel on Entroware laptop for me so hardly a driver problem (but maybe not even the same bug)
efficient diagnosis procedure welcomed."
1743094,2018-05-25 11:34:38 UTC,Re-installing the nouveau and nvidia drivers didn't work for me sadly. The problem persists.
1743094,2018-05-24 11:27:45 UTC,I have Nvidia graphics and I am using the Nvidia drivers so it isn't just a nouveau driver problem. But it may be worth re-installing the nvidia drivers again to see if that solves the problem for me.
1743094,2018-05-23 21:44:40 UTC,"Hmm, in a somewhat disheartening turn of events, I thought I'd try installing the nvidia proprietary driver on my workstation (that's what I had installed on 16.04, when suspend/resume worked).  ...And now, suspend/resume works perfectly (and quickly) on the workstation.  So maybe this is a nouveau bug?  Is everyone else having problems using nvidia graphics hardware with the nouveau driver?"
1743094,2018-05-23 20:51:42 UTC,"This is still a problem in bionic as well.  I just did a clean install on a workstation which exhibits the problem, but I also have a laptop which was upgraded from 17.10, which has not ever exhibited the problem."
1743094,2018-05-15 11:45:27 UTC,"On freshly installed bionic.
When suspending from a text tty I can see a couple of lines at resume (mostly related to wifi and icc profile in ~/.local/share/icc), then it hangs after a couple of seconds."
1743094,2018-06-06 02:05:20 UTC,I manually install 4.13.0-21 from here https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13870500 and hibernate began to work!
1743094,2018-05-28 13:48:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743094,2018-06-06 10:08:24 UTC,Update to #138:
1743094,2019-03-19 19:57:06 UTC,"18.04 didn't exhibit the problem for me (HP Elitebook 820 G3), but I have had it since the upgrade to 18.10."
1743094,2018-06-06 20:13:30 UTC,I manually install 4.17.0-041700-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/ and hibernate is working very fine!
1743094,2018-05-15 11:35:02 UTC,apport information
1743094,2020-11-09 08:38:20 UTC,I am closing this bug as this issue seems to be fixed.
1743094,2019-05-01 00:09:05 UTC,"@EDEMPCO I haven't had the issue since I updated to Ubuntu 18.04 (or stopped using the 4.13.x series on 16.04). Are you using the kernel provided by the distribution? Can you try running one of the 4.10.x kernels to see if that fixes it? Also are you sure you have this specific bug, and not any of the many other hibernation bugs?"
1743094,2019-04-30 23:15:40 UTC,"Since 18.04 is the latest LTS, how does this change get distributed to those of us who rely on the LTS to be upgraded and effective until the next LTS? In other words, how and when does it get integrated into 18.04LTS?"
1743094,2019-04-30 01:54:20 UTC,"Linux: 5.0.0-13-generic
intel-microcode: 3.20190312.1"
1743094,2019-04-29 01:42:25 UTC,Fixed since upgrading from 18.10 (4.18) to 19.04 (5.0) on the same configuration.
1743094,2018-06-06 11:46:36 UTC,"Just to clarify above comment from hans005: from what I can read here his problem (#138, #145) was a completely different issue: standby with nvidia GPU."
1743094,2019-02-26 02:19:09 UTC,"I've been dealing with this issue since December 2018. It acted to me like a graphic problem, so I posted a bug #1807264 as a video crash. No help or comment on the bug report. In the hopes that a new kernel will help, I'm continually upgrading to the newest. No luck, so far. I would be satisfied to be able to turn off hibernation/suspend completely, but there is no help with that either. This needs to be addressed."
1743094,2018-10-28 21:52:28 UTC,"I have installed the ""edge"" hwe packages as denoted in these two comments:"
1743094,2018-07-24 09:33:48 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1743094,2018-07-09 09:04:41 UTC,"Using a HP ZBook Studio G3 Mobile Workstation, hibernation works for me again using the HWE kernels on Linux 16.04."
1743094,2018-06-20 00:00:48 UTC,"Confirmed with a Lenovo V570 that using the generic HWE 16.04 edge kernel restores hibernation ability. I needed to install both linux-image-generic-hwe-16.04-edge"" and ""linux-headers-generic-hwe-16.04-edge""."
1743094,2018-06-19 20:59:57 UTC,"Sorry, the correct package in the post above is called ""linux-image-generic-hwe-16.04-edge""."
1743094,2018-06-19 20:57:54 UTC,"Now, there is a solution for all people on Ubuntu 16.04."
1743094,2019-01-07 10:08:27 UTC,Please fix this bug soon. It affects many distributions based on Ubuntu and there are no workarounds available for Ubuntu 18.04. I have attached my system details. I couldn't find any relevant logs in syslog or pm logs which leads to failure in hibernation.
1743094,2018-05-15 11:34:58 UTC,apport information
1743094,2018-01-13 11:45:54 UTC,apport information
1743094,2018-05-15 11:34:51 UTC,apport information
1743094,2018-01-16 11:49:07 UTC,"Hi there,
I face the same problem: 4.13.0-26-generic causes freeze on resume from hibernation.
The 4.10.x kernel series works flawless on my Medion Core i3 Notebook."
1743094,2018-01-15 14:58:40 UTC,"I'm experiencing the same problem with kernel 4.13.0-26-generic, 4.10 series works fine."
1743094,2018-01-15 08:05:44 UTC,Can also confirm that 4.13.0-26-generic causes the computer to fail to resume from hibernation. Downgrading to 4.10.0-42-generic fixes the problem.
1743094,2018-01-13 11:46:04 UTC,apport information
1743094,2018-01-13 11:46:03 UTC,apport information
1743094,2018-01-13 11:46:01 UTC,apport information
1743094,2018-01-13 11:46:00 UTC,apport information
1743094,2018-01-13 11:37:05 UTC,kernel 4.4.0-109 (with kaiser patch against meltdown) does also function all-right.
1743094,2018-01-13 11:45:59 UTC,apport information
1743094,2018-01-16 13:55:55 UTC,4.13.0-30.33 (available in artful-proposed) appears to have fixed it for me.
1743094,2018-05-15 11:34:53 UTC,apport information
1743094,2018-01-13 11:45:57 UTC,apport information
1743094,2018-01-13 11:45:56 UTC,apport information
1743094,2018-01-13 11:45:56 UTC,apport information
1743094,2018-01-13 11:45:54 UTC,apport information
1743094,2018-01-13 11:45:53 UTC,apport information
1743094,2018-01-13 11:45:52 UTC,apport information
1743094,2018-01-13 11:45:51 UTC,apport information
1743094,2018-01-13 11:45:50 UTC,apport information
1743094,2018-01-13 11:45:59 UTC,apport information
1743094,2018-01-13 11:45:58 UTC,apport information
1743094,2018-01-16 22:45:56 UTC,"tested hibenate-resume cycles with a couple of other 4.13 kernels:
4.13.0.16 - works
4.13.0.21 - works
4.13.0.25 - broken
4.13.0.30 - broken (from Canonical Kernel Team PPA)"
1743094,2018-01-13 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743094,2018-01-20 13:53:59 UTC,"Same issue here: when trying to resume from hibernation, my laptop screen stays black and I have to force kill it.
Been scrolling through the logs, but there seems to be no data between when I started hibernation and after I restarted my laptop after the force-kill."
1743094,2018-01-26 07:26:43 UTC,I can confirm the issue on (but not necessarily limited to) 4.13.0-31 and 4.13.0-32 (that I just got 15 minutes ago while upgrading).
1743094,2018-01-26 10:53:26 UTC,I can confirm that issue is still present with the kernel 4.13.0-32.
1743094,2018-01-26 11:05:48 UTC,Also still failing under kernel 4.13.0-32.
1743094,2018-01-26 14:38:18 UTC,"                       | systemctl hibernate  | systemctl hybrid-sleep | s2disk
-----------------------+----------------------+------------------------+---------
4.13.0-25              :          ??          :           ??           : broken
4.13.0-31              :          ??          :           ??           : broken
4.13.0-32              :        broken        :           ??           : broken
4.14.15-041415-generic :         work         :         broken         :   ??"
1743094,2018-01-26 23:53:08 UTC,Looking at Dirk Bachmann's comment #23 I did a:
1743094,2018-01-27 00:42:31 UTC,"User confirmed on IRC that ""nopti"" allowed 4.13.0-25 to resume from hibernation."
1743094,2018-05-15 11:34:41 UTC,apport information
1743094,2018-05-15 11:34:43 UTC,apport information
1743094,2018-05-15 11:34:46 UTC,apport information
1743094,2018-05-15 11:34:47 UTC,apport information
1743094,2018-01-24 11:30:33 UTC,Same issue affects me after updating to kernel 4.13.0-31.
1743094,2018-05-15 11:34:49 UTC,apport information
1743094,2018-01-25 19:23:59 UTC,Same issue with a Lenovo Y580 on 16.04.3 LTS with 4.13.0-26. I agree that this is a very important bug that should be solved soon.
1743094,2018-01-19 20:03:24 UTC,"If I knew how I might be able to bisect. I found some info on the issue (see links), I think I can compile a kernel if I knew the options that the kernel I used was compiled with. I'm not really a programmer so if I have to read through (too much) code I will fail. Is there a link for Ubuntu standard kernel compiling?"
1743094,2018-01-20 15:23:36 UTC,"Same issue here, fresh install of stock Ubuntu 17.10(.1) on a ThinkPad X1 Carbon gen5, kernel 4.13.0-25-generic, with LUKS-encrypted swap partition sitting alongside the root partition.  The same hardware/setup worked fine on Zesty but as we know, that just went EoL."
1743094,2018-01-20 20:05:57 UTC,"Same issue with a Lenovo W520 on 16.04.3 LTS with 4.13.0-26. The quite fresh 4.14.13 kernel (Canonical Kernel Team PPA) solves this ""resuming from hibernation"" problem. I agree that this is a very important bug that should be solved soon."
1743094,2018-01-20 21:04:48 UTC,"Kernel 4.14.13 fixes the issue for me too.
(installed as outlined by http://linuxg.net/install-kernel-4-14-on-ubuntu/)"
1743094,2018-01-21 15:58:43 UTC,"I found part of the kernel log describing the failed boot.
Line 642 seems relevant:"
1743094,2018-01-22 12:40:38 UTC,4.13.0-30.33 (available in artful-proposed) don't work for me
1743094,2018-01-23 13:31:12 UTC,"I can also confirm that with 4.13.0-30, hibernate did not work, but installing 4.14.13-041413-generic works perfectly."
1743094,2018-01-23 23:44:33 UTC,"I can confirm that my Laptop freezes on resume from hibernate with Kernel 4.13.0-25 and 4.13.0-31. Last working Kernel version is 4.13.0-21 .
My Laptop is Lenovo Thinkpad T470."
1743095,2020-07-21 04:05:29 UTC,Please explain what kind of problem you are experiencing.
1743095,2020-09-19 04:17:28 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1743099,2018-11-24 05:50:09 UTC,"After using the new canvas more I have gotten more used to the new clicking twice on an object/trace and using the D and G keys for moving traces. I wish they still worked when move parts as they did before. I have found using a track pad with the new set up is VERY hard. I usually get frustrated and find the mouse quickly, which is't great for quick edits or when working on a project for short lengths of time."
1743099,2018-02-20 18:03:12 UTC,"Since this is a Legacy regression I'm marking it as Medium.  If we decide we want to drop support for it then we can mark it as Won't Fix, but we need to start making these decisions in preparation for dropping Legacy support."
1743099,2018-02-20 20:50:17 UTC,"There's no reason to implement it as it's done in the legacy tools. It just isn't useful at all, except for some rare cases (where you drag to the opposite direction compared to where every track points to - i.e. almost never). It just creates new segments which require severe fixing, it's easier to draw new tracks."
1743099,2018-07-10 23:19:13 UTC,"From ""bson"" on the kicad.info forums:"
1743099,2019-06-16 11:47:27 UTC,Yes. Adding drag/grab footpring is a good idea. Dragging is a good feature. In some situations it saves time.
1743099,2018-10-08 17:47:25 UTC,"I'm going to agree with Jeff here. I use Kicad mainly for single sided, etch at home boards. Being able to ""nudge"" and fine tune part/track placement at once is very useful for gaining a little extra breathing room for etching the board."
1743099,2019-03-27 09:53:40 UTC,"I am also glad that this has been milestoned.
Please consider this important, it is really missing and makes laying out a complex board much more dificult."
1743099,2019-02-10 12:04:35 UTC,"I'm glad to see this has been milestoned. About the way it's planned to work: I don't know what would be the simpliest way to implement this or how to integrate it with the existing code, but from the user's point of view the way it behaves could be a bit different and simpler than the normal pushing and shoving traces. The above mentioned ""nudging"" would probably be good provided that it doesn't move traces around objects. I can't say for sure before the feature is implemented and testable, but most probably I would use it to make the design to fit into smaller space or to make space for new components. In these cases I would prefer it to make as small changes to the overall design as possible."
1743099,2018-11-24 09:09:37 UTC,@jwatte: your comments don't seem to be related to this bug report.
1743099,2018-11-24 05:08:37 UTC,"Currently, when I start a new board, and import all of the schematics, it's very hard to click on a footprint and drag it to separate it out, because there's a 75% chance I accidentally clicked a label or value or pad or something. Especially given that the automatic spread overlaps label text with other footprint outlines."
1743099,2019-06-16 06:26:01 UTC,"The lack of this feature is a massive oversite. It’s such a fundamental feature, I’m always amazed KiCAD doesn’t have it in the modern canvas. I still switch back to leagscy just to nudge things. The fact that the legacy implantation is so awkward is also frustrating.  I sincerely hope this is high on someone’s list to address. The very first version of Protel for Windows I bought (that ran on Windows 3.1) had this feature from the very start. Please add this feature and make it useful.  If the developers could add push and shove routing to KiCAD, surely this should be a walk in the park."
1743100,2019-10-04 04:24:53 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1743100,2018-01-25 19:26:59 UTC,"4.13.0-31-generic boots for me and behaves as expected (no issues)  However, variant one is still active:"
1743100,2018-01-24 20:32:21 UTC,I have problems with 4.13.0-31 as well :/
1743100,2018-01-16 16:41:05 UTC,The 4.13.0-30-generic kernel will also NOT boot.
1743106,2018-02-03 14:06:36 UTC,"John,"
1743106,2018-01-31 04:06:25 UTC,Zones as a placement directive is something I'm interested in supporting. (IIRC we already support this in most places.)
1743106,2018-04-05 04:17:34 UTC,[Expired for juju because there has been no activity for 60 days.]
1743109,2018-01-13 21:37:54 UTC,There is IMHO no need to unify the interface completely. But it is a good idea to consider the use cases and optimize the interface for the target use cases of the skin.
1743109,2018-01-13 23:58:18 UTC,"> because THE CUE of a track has nothing to do with the CUE of the sample
What do you mean? I can set CUE in the deck, then drag the track to a sampler and it will start playing from that exact CUE.
Btw, I thinkk I found a bug: if you load a track to a sampler, the play position in the sampler's overview is at the track's beginning, but it will play from CUE nevertheless.
"
1743110,2018-01-13 14:32:59 UTC,"It is not possible for our group of my students to work normally with our system.
We an only work after recovering the system.
So, I would appreciate it very much, if you would help us as soon as possible with a working upgrade."
1743111,2018-01-13 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743111,2018-01-14 03:37:30 UTC,Does this bug go away if you boot back into the 4.13.0-21 kernel?
1743111,2018-01-23 09:45:12 UTC,Installed the version 4.10.0-42-generic; installation went perfect. I got an update message and updated to 4.13.0-26-generic. I can see the system running but the screen shows only some lines and a small peace of a window in the right part of the window. The system does not react on the keyboard. I am running Lubuntu 17.10 on a Samsung Nc10 notebook. If is not possible to generate an error report as requested.
1743111,2018-02-12 22:56:09 UTC,I am running Lubuntu 16.04.3 on a Acer Aspire One AOA150/ZG5.
1743112,2018-01-13 14:43:44 UTC,"StacktraceTop:
 QByteArray::reallocData (this=this@entry=0x7f92eab450a8, alloc=1, options=options@entry=...) at tools/qbytearray.cpp:1732
 QByteArray::reserve (asize=0, this=0x7f92eab450a8) at ../../include/QtCore/../../src/corelib/tools/qbytearray.h:500
 normalizeTypeInternal (t=0x7f92eab450c8 "")"", e=e@entry=0x7f92eab450c8 "")"", fixScope=fixScope@entry=false, adjustConst=adjustConst@entry=true) at ../../include/QtCore/5.9.1/QtCore/private/../../../../../src/corelib/kernel/qmetaobject_moc_p.h:100
 qNormalizeType (result=..., templdepth=<optimized out>, d=0x7f92eab450c8 "")"") at kernel/qmetaobject.cpp:1266
 QMetaObject::normalizedSignature (method=method@entry=0x7f932b983328 ""2opened()"") at kernel/qmetaobject.cpp:1328"
1743112,2018-02-04 21:13:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743120,2018-03-08 14:45:37 UTC,"Reviewed:  https://review.openstack.org/533752
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5f881ff030c119b50bf1929b9829f52493ac447c
Submitter: Zuul
Branch:    master"
1743120,2018-01-15 18:17:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533752"
1743120,2018-01-16 13:01:41 UTC,"I messed up the bug reference, so there's also:
 https://review.openstack.org/#/c/533797/"
1743120,2018-01-16 12:57:31 UTC,"This going to be fairly complicated to make much headway on, unless the resource_provider objects are moved out from under nova/objects. __init__.py there registers all those objects, each of which imports things from all over the nova hierarchy. One notable example are the ec2 objects which import nova/api/ec2/ec2utils which imports dogpile so it can memoize some operations (are they ever called?)."
1743120,2018-03-08 15:17:03 UTC,"Reviewed:  https://review.openstack.org/533797
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ef6f4e4c8ec82e2c9f9988fe2e04591ee01220e6
Submitter: Zuul
Branch:    master"
1743120,2018-10-05 12:11:30 UTC,We can call this done now that openstack/placement exists
1743124,2018-01-13 15:21:02 UTC,"hummm...  ""failed"" and not ""faled""  :-)"
1743134,2018-04-09 15:04:23 UTC,I can't reproduce this using Pluma 1.20.1-2ubuntu1 on Ubuntu MATE 18.04 daily.
1743134,2018-04-09 16:46:54 UTC,"I have only 1.20.1-0ubuntu1 even with enabled proposed updates and Main server on todays daily ISO (http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/bionic-desktop-amd64.iso, md5 = fe4e959dbd49658b5fa5155029e3488c)."
1743134,2018-04-10 08:50:28 UTC,I installed latest 1.20.1-2ubuntu1.
1743134,2019-01-28 11:13:12 UTC,I see
1743134,2019-03-29 16:52:06 UTC,Still a problem for Ubuntu MATE 19.04 beta2.
1743134,2019-10-05 16:42:39 UTC,Still happens on 19.10.
1743135,2018-04-25 16:29:11 UTC,"I have the same problem with my Acer One D250. Started the same way at the same time.
I have holding down the shift key on bootup. It has been working if I boot to kernel
4.10.0-40. Others may also work. A little inconvenient but I have been able use the computer."
1743154,2018-01-14 10:25:19 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1743158,2018-01-14 12:54:31 UTC,apport information
1743158,2018-01-13 21:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743158,2018-01-19 03:14:58 UTC,"> On 19 Jan 2018, at 4:38 AM, Andrea <email address hidden> wrote:
>
> Ok, tomorrow I'll read that post and try to fix my issue. In case of
> failure what do you suggest me to do?
"
1743158,2018-01-18 20:38:48 UTC,"Ok, tomorrow I'll read that post and try to fix my issue. In case of failure what do you suggest me to do?"
1743158,2018-01-18 17:23:21 UTC,"Hmm, probably same as LP: #1653456."
1743158,2018-01-18 14:34:06 UTC,"Hello Kai, here you are the result of the command"
1743158,2018-01-14 12:53:30 UTC,apport information
1743158,2018-01-16 19:47:51 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1743158,2018-01-14 12:54:32 UTC,apport information
1743158,2018-01-14 12:53:32 UTC,apport information
1743158,2018-01-18 03:51:45 UTC,"Please attach the output of `udevadm info -e`?
Thanks."
1743159,2018-03-03 19:43:25 UTC,"Hello,"
1743159,2018-04-01 09:35:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743159,2018-03-01 04:41:33 UTC,"There are too many errors at this point with this os, so upgrading to 16.04 from 14.04. All data has been removed from the pc and stored on an external disk. am-utils continues to fail any install or upgrade processes, even though it has been replaced. (03-01-2018)"
1743162,2018-03-02 15:23:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743168,2019-06-18 07:46:01 UTC,"Changing the configuration of 01-rewrite.conf.j2, with the one present here works:
https://review.openstack.org/#/c/518490/15/ansible/roles/common/templates/conf/filter/01-rewrite-0.14.conf.j2"
1743191,2020-05-26 15:20:18 UTC,"Just to clarify my last comment, and in absence of updates, if I launch the VM as:"
1743191,2020-03-06 13:24:54 UTC,"Ah, it's a special serial console boot iso.  I was trying the normal NetBSD-<version>-amd64.iso."
1743191,2020-03-06 09:55:02 UTC,"@kraxel-redhat: This issue bisects to commit d6728f301d7e6e31ba0ee2fa51ed4a24feab8860 (""add serial console support"").  seabios.git/master + ""[PATCH] sercon: vbe modeset is int 10h function 4f02 not 4f00"" still has the issue."
1743191,2020-03-06 09:22:43 UTC,"Gerd Hommann wrote:

> Workaround: add ""-vga none"" to the qemu command line.
"
1743191,2020-03-06 09:21:28 UTC,"@kraxel-redhat,"
1743191,2020-03-06 09:04:25 UTC,"Workaround: add ""-vga none"" to the qemu command line."
1743191,2020-03-06 08:48:29 UTC,"Possibly related thread:
""Do we need a cpu with TSC support to run SeaBIOS?""
https://<email address hidden>/msg11726.html"
1743191,2020-03-05 21:37:57 UTC,Reverting to Seabios 1.10 (version rel-1.10.3.0-gb76661dd) fixes this problem.
1743191,2020-03-18 20:12:45 UTC,"On Fri, 6 Mar 2020 at 13:24, Gerd Hoffmann <email address hidden> wrote:

> So one option is to turn off seabios sercon: ""qemu -nographic -machine
> graphics=on"".
"
1743195,2018-01-14 15:11:38 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1743195,2018-01-15 19:15:29 UTC,Fixed in upstream: https://gitlab.com/muttmua/mutt/blob/master/contrib/smime.rc
1743195,2020-07-22 21:02:20 UTC,This has been resolved.
1743198,2020-06-23 17:22:42 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/531908"
1743199,2018-01-14 11:36:04 UTC,"Hi, same here..."
1743199,2018-01-14 11:58:15 UTC,I removed the package and the error is gone. But I cannot install the package again:
1743199,2018-01-14 12:00:32 UTC,"Hi; same problem occurred to me: I'm running ""Raspbian GNU/Linux 9 (stretch)""
on a ""Raspberry Pi 2 Model B Rev 1.1""."
1743199,2018-01-14 14:15:12 UTC,What is the output of
1743199,2018-01-14 14:26:18 UTC,"python3-scrollphathd:
  Installed: (none)
  Candidate: 1.1.0
  Version table:
     1.1.0 500
        500 http://archive.raspberrypi.org/debian stretch/main armhf Packages"
1743199,2018-01-14 14:28:55 UTC,"facing the same problem as above. Above one is the output of apt-cache policy python3-scrollphathd.
i am trying to download opencv on raspbian pi2 model b."
1743199,2018-01-14 14:42:17 UTC,Same problem here. The output on my Pi3 was
1743199,2018-01-14 15:45:21 UTC,These are raspberry pi foundation packages and it looks like the issue has already been reported to them at https://github.com/RPi-Distro/repo/issues/100
1743199,2018-01-15 11:59:36 UTC,"Solution found here:
https://www.raspberrypi.org/forums/viewtopic.php?t=202523"
1743199,2018-01-16 01:36:36 UTC,"While the two versions of the file (for python2 and python3) /usr/bin/scrollphathd_api are different, I have chosen to ignore the fact that the python2 version may not work. It's moot here because I don't have the hardware display hat that this supports."
1743200,2019-05-17 16:56:19 UTC,yes please also need it :((
1743200,2020-12-10 14:55:54 UTC,"Hi Jessica, there is currently no plan to backport Netplan >= 0.100 to Bionic. If you need this urgently, please open a new bug report explaining your rationale."
1743200,2020-12-03 15:37:17 UTC,Any chance of a backport to bionic?
1743200,2019-05-13 16:37:11 UTC,Is there any plan to implement this?
1743200,2020-11-12 14:10:13 UTC,"Hi Bruno, you can call `dpkg -l | grep netplan` to see the installed version. Netplan 0.100 is available in Ubuntu Focal 20.04 LTS."
1743200,2020-09-23 13:25:02 UTC,"netplan 0.100 has now been released, including this feature."
1743200,2020-08-04 07:55:34 UTC,Support for IP address labels has been merged upstream and will be part of the next netplan.io release: https://github.com/CanonicalLtd/netplan/pull/89
1743200,2020-06-30 07:39:29 UTC,As a clarification on this topic:
1743200,2020-05-26 14:44:51 UTC,We have that as an item on the current netplan development backlog.
1743200,2020-05-15 10:59:06 UTC,its not just ifconfig that uses interface labels. many programs use them for mapping which ip they bind to.
1743200,2020-04-25 20:40:45 UTC,BTW: ifconfig is deprecated for at least 10 years now: https://lists.debian.org/debian-devel/2009/03/msg00780.html
1743200,2018-09-19 12:08:07 UTC,"This is called an interface label, the iproute2 syntax is as follows:"
1743200,2020-04-05 19:14:22 UTC,"+1
thought i learn netplan on my new server and use a second IP, project ended here"
1743200,2020-03-28 23:00:20 UTC,+1
1743200,2020-01-30 09:24:52 UTC,+1 I have also stumbled onto this via various searches.
1743200,2020-01-22 14:35:49 UTC,+1. Its insane that a configuration option thats been around for years was skipped.
1743200,2020-01-22 03:21:21 UTC,"+1 Also, why is this a ""Wishlist""?  This is BASIC FUNCTIONALITY that has been in linux since the 1990's!  This is a functional defect."
1743200,2020-01-15 12:17:54 UTC,+1
1743200,2019-11-07 14:34:55 UTC,+1
1743200,2020-11-10 18:01:09 UTC,How I can see the current version of netplan that I'm using since that `netplan info` doesn't bring version number and is it already available on Ubuntu 20.04.1 (server)?
1743200,2020-04-13 16:34:07 UTC,I am affected by this bug.
1743202,2018-01-14 16:14:32 UTC,"Thanks a lot. I have been carefully following the semver doc of pbr ([1])
that give some example of alpha/beta:
""If the alpha portion does not match, the sort order is dev < a < b < c.
Example: 1.0.0.dev8 < 1.0.0.dev9 < 1.0.0.a1.dev3 < 1.0.0.a1 < 1.0.0.b2 <
1.0.0.c1 < 1.0.0."""
1743202,2018-01-14 10:16:03 UTC,"Reproduce with:
```
git clone https://github.com/Guake/guake
cd guake
make dev
make release-note-news
```"
1743202,2018-01-14 15:17:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533424"
1743202,2018-01-14 15:22:53 UTC,"The guake repository has pre-release tags that don't match the pattern reno is searching for. I've proposed https://github.com/Guake/guake/pull/1067 to set the regex and that seems to fix the problem. The patch submitted against reno improves the debug output from the command, but isn't needed to fix the issue."
1743202,2018-01-14 16:15:03 UTC,"Thanks a lot. I have been carefully following the semver doc of pbr ([1]) that give some example of alpha/beta:
""If the alpha portion does not match, the sort order is dev < a < b < c. Example: 1.0.0.dev8 < 1.0.0.dev9 < 1.0.0.a1.dev3 < 1.0.0.a1 < 1.0.0.b2 < 1.0.0.c1 < 1.0.0."""
1743202,2018-01-14 16:36:15 UTC,"Ah, yes, we should fix that documentation. Thanks for the pointer. I'll add pbr to this bug and update the title."
1743202,2018-01-15 16:18:41 UTC,"Reviewed:  https://review.openstack.org/533424
Committed: https://git.openstack.org/cgit/openstack/reno/commit/?id=32b5405d0e8bcbee7048aac1247fc95619a08f07
Submitter: Zuul
Branch:    master"
1743202,2018-03-14 14:47:38 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1743202,2018-07-30 17:18:28 UTC,Looks like the pbr docs have been updated to reflect this.
1743204,2018-01-17 13:43:48 UTC,"I blacklisted the package ""linux-image-extra-4.13.0-25-generic"" in 50unattended-upgrades and at least unattended upgrades runs to completion without any errors."
1743204,2018-01-14 10:56:13 UTC,"Attempting to remove the linux-generic package Synaptic Package Manager also reported ""package is in a very bad inconsistent state"" and failed."
1743204,2018-01-14 11:00:07 UTC,This change was made by a bot.
1743204,2018-01-14 11:02:45 UTC,Attempting to upgrade the package Synaptic Package Manager failed again with:
1743204,2018-01-17 08:38:30 UTC,"OK, done that.
I then did 'sudo apt-get update' which started off fine but after some ""W: Possible missing firmware' messages the process stalled without using CPU.
Please see attached terminal log"
1743204,2018-01-14 18:43:58 UTC,"From ""https://askubuntu.com/questions/675296/changing-ownership-operation-not-permitted-even-as-root""
looks like ""file has the immutable flag set in its extended attributes""
so I reckon it's a problem to be resolved by the package maintainer... or someone who knows better, please help...
If I can do anything to help, just let me know."
1743204,2018-01-17 21:15:23 UTC,There is one file in /usr/lib/x86_64-linux-gnu/wine/ which lsattr says has the immutable flag set:
1743204,2018-01-17 20:10:52 UTC,I tried to install wine again and got more errors - see the attached terminal log. The base problem seems always to be a authorisation issue. e.g.:
1743204,2018-01-17 14:55:51 UTC,I also blacklisted it in '/etc/apt/apt.conf.d/01autoremove' and apt update now also runs to completion without any errors.
1743204,2018-01-16 19:45:29 UTC,You may need to run the following from a terminal:
1743208,2018-10-01 00:46:28 UTC,note: with no sign of a fix for this bug in sight I am adding the following lines to my .profile file in my home folder to force a particular frequency and governor after a shell login:
1743208,2018-09-27 19:41:17 UTC,"I get this error randomly.
I have no idea what causes it.
Python update?
Kernel update?
Its seems random."
1743214,2021-01-16 04:17:52 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1743214,2020-11-16 18:17:34 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1743214,2018-01-15 04:39:21 UTC,It looks like this bug affects only QEMU for Windows.
1743214,2018-01-14 22:53:14 UTC,"On Sun, 14 Jan 2018, Stefan Weil wrote:

> Zoltan, did you run the test with KVM enabled?
>
> I‌ get a crash when I run the image with latest QEMU on Linux with TCG.
"
1743214,2018-01-14 14:03:52 UTC,I used QEMU 2.11 for Windows from Stephan Weil (http://qemu.weilnetz.de/). I have Windows 10 (v1709) x64.
1743214,2018-01-14 13:24:57 UTC,"On Sun, 14 Jan 2018, MVoloshin wrote:

> Hello, I used to run OS/2 Warp 3 on QEMU with the following command
> line: qemu-system-i386 -vga cirrus -soundhw sb16 -hda os2warp3v2.img
> -boot c. It runs OK on QEMU 2.10, but immediately gives TRAP 0006
> (invalid opcode?) on QEMU 2.11 (see screenshot).
>
> If it is important I have Fixpack 40 and GRADD installed in OS/2.
> Here is the image:
> https://drive.google.com/open?id=15umPecy7JlPLKUP6520MB_87CfrCDWO5
"
1743216,2018-11-07 13:50:40 UTC,"The verification of the Stable Release Update for xdg-utils has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1743216,2018-08-31 19:08:53 UTC,"The ProcCmdline.txt file in this bug report, and some of its duplicates (I didn't check them all), are quite strange."
1743216,2018-11-07 13:50:34 UTC,This bug was fixed in the package xdg-utils - 1.1.2-1ubuntu2.3
1743216,2018-11-06 08:38:52 UTC,I performed the verification with xdg-utils 1.1.2-1ubuntu2.3 from bionic-proposed and the test case in the description. I get the same crash (https://errors.ubuntu.com/oops/8f6e9f06-e19e-11e8-a0af-fa163e6cac46)
1743216,2018-10-25 09:30:21 UTC,I installed xdg-utils 1.1.2-1ubuntu2.3 from Ubuntu:18.04/bionic-proposed.  We will see if it still crashes or not.  Thank you Iain for your work.
1743216,2018-10-23 20:38:54 UTC,Normally I would query the Error Tracker database to figure out if this is resolved but information about the version of xdg-utils installed does not appear in the crash reports there.
1743216,2018-10-23 13:45:47 UTC,Would somebody like to verify this upload?
1743216,2018-10-18 19:10:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743216,2018-10-02 23:31:24 UTC,"Hello Carlos, or anyone else affected,"
1743216,2018-10-02 21:35:22 UTC,This bug was fixed in the package xdg-utils - 1.1.3-1ubuntu2
1743216,2018-10-02 10:33:30 UTC,"OK, I think I understood it properly and these uploads (which are waiting in the queues currently) should fix it."
1743216,2018-08-31 21:21:30 UTC,The perl code is actually from xdg-screensaver.
1743216,2018-02-19 16:55:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743216,2018-01-14 12:39:58 UTC,"StacktraceTop:
 _dbus_abort () at ../../../dbus/dbus-sysdeps.c:93
 _dbus_warn_check_failed (format=format@entry=0x7f67696eb7c8 ""arguments to %s() were incorrect, assertion \""%s\"" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n"") at ../../../dbus/dbus-internals.c:281
 _dbus_warn_return_if_fail (function=function@entry=0x7f67696ea1b0 <__func__.5319> ""dbus_message_iter_append_basic"", assertion=assertion@entry=0x7f67696e94b8 ""_dbus_check_is_valid_utf8 (*string_p)"", file=file@entry=0x7f67696e9a1d ""../../../dbus/dbus-message.c"", line=line@entry=2754) at ../../../dbus/dbus-internals.c:936
 dbus_message_iter_append_basic (iter=0x55e5b0ba6530, type=type@entry=115, value=value@entry=0x7ffd7fe845b0) at ../../../dbus/dbus-message.c:2754
 XS_Net__DBus__Binding__Iterator_append_string (my_perl=<optimized out>, cv=<optimized out>) at DBus.xs:1543"
1743216,2018-11-06 14:44:38 UTC,"I confirm that since I installed xdg-utils 1.1.2-1ubuntu2.3 from Ubuntu:18.04/bionic-proposed, I have not gotten any crashes."
1743216,2018-11-06 09:47:10 UTC,"Actually I did a mistake when I updated xdg-screensaver. with $window_name set at the right location there is no more crash with the version from proposed.
Marking as verification-done"
1743226,2018-01-14 14:04:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533421"
1743226,2018-09-06 07:47:14 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/533421
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1743231,2018-10-03 23:29:44 UTC,This bug was fixed in the package docker-compose - 1.21.0-3
1743231,2018-04-17 23:47:39 UTC,Hi.
1743239,2018-01-15 15:10:54 UTC,"There is no bug, my setup was not correct: my overcloud image didn't have the ceph packages installed."
1743244,2020-08-31 04:17:31 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1743244,2020-07-01 21:10:26 UTC,"it doesn't sound like a problem with the evince pdf viewer though, reassigning"
1743244,2020-07-01 21:10:07 UTC,"Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1743246,2020-08-18 04:17:19 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1743246,2020-06-18 04:46:18 UTC,Please run this command to send us more information about your audio problems:
1743247,2018-01-17 12:47:10 UTC,"~$ pip --version
pip 9.0.1 from /usr/local/lib/python3.5/dist-packages (python 3.5)
~$ pip2 --version
pip 8.1.1 from /usr/lib/python2.7/dist-packages (python 2.7)
~$ pip3 --version
pip 9.0.1 from /usr/local/lib/python3.5/dist-packages (python 3.5)"
1743247,2018-01-16 00:31:11 UTC,"Thanks. The main advantage of sticking with apt is unattended-upgrades makes it easy to be sure security updates are applied automatically. I’m not familiar with a similar solution for pip, and it sounds like “upgrade everything” isn’t that straightforward (according to https://github.com/pypa/pip/issues/3819)."
1743247,2018-01-15 16:50:06 UTC,"Duplicity runs on many distros and needs close to 30 packages if you were to supply them all at install time.  The basic install is around 15.  I have found that some distro's, Ubuntu included, lock the version of the package and will not update it except to fix a critical error.  I recommend pip because it supplies the most current version as well as allowing easy regression to a previous version of a Python package.  If you wish to use apt to get the B2 package, I see no harm, but I have not tested against whatever version they supply."
1743247,2018-01-17 10:22:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743247,2018-01-17 10:18:14 UTC,"The pip command didn't work for me, and nor did the pip2 equivalent. The same b2 missing backend message always comes up, despite pip ostensibly having installed the required backend as requested (at least, without error meassages). Downgrading to 0.7.06-2ubuntu2 works, but that's a pretty old package!"
1743247,2018-01-17 12:28:51 UTC,"0.7.15 included a rewrite of the b2 backend to be much faster.  The rewrite uses the official b2 API, not web access, thus the need for the package."
1743247,2018-01-17 23:21:36 UTC,Same issue here.
1743247,2019-09-17 00:42:14 UTC,This bug report was originally against the PPA package (0.7.16-0ubuntu1ppa1347~ubuntu16.04.1) and not those included in Ubuntu's repositories.
1743247,2019-09-15 13:45:57 UTC,"If pip is the recommended installation method, and apt packages aren't complete or tested, should https://launchpad.net/~duplicity-team/+archive/ubuntu/ppa be marked as deprecated?"
1743247,2019-09-14 15:19:53 UTC,"I marked this as Won't Fix.  Duplicity runs on many distros and needs close to 30 packages if you were to supply them all at install time. The basic install is around 15. I have found that some distro's, Ubuntu included, lock the version of the package and will not update it except to fix a critical error. I recommend pip because it supplies the most current version as well as allowing easy regression to a previous version of a Python package. If you wish to use apt to get the B2 package, I see no harm, but I have not tested against whatever version they supply."
1743247,2019-09-14 14:11:20 UTC,"Solution that worked for me on macOS, for anyone searching:"
1743247,2018-08-22 13:45:59 UTC,I think it's this issue: https://github.com/henrysher/duplicity/issues/14#issue-283710635
1743247,2018-08-18 19:41:11 UTC,Can anyone tell me what's going on here or how I can workaround this problem?
1743247,2019-09-15 15:54:12 UTC,"Actually, no.  The latest and best duplicity versions are in the ppa package.  Ubuntu, and others, lock the version when a release is made.  For example, version 0.7.19 is the current version in the ppa, but it's not in any apt repository.  Instead, much earlier versions are there and do not get fixes or improvements, so I normally recommend upgrading using the duplicity ppa with apt."
1743247,2018-06-29 14:44:50 UTC,"You may want to always specify pip2 since pip could be symlinked to pip2 or pip3.  The install would not fail, but if pip --> pip3, then duplicity would not have it available in Python2."
1743247,2018-06-26 21:11:27 UTC,I'm using duplicity 0.7.17.
1743247,2018-06-26 21:07:41 UTC,"Same issue here, on Mac OS 10.11.6 and on Debian 9.
Reinstalling duplicity for me didn't the trick."
1743247,2018-01-17 23:26:12 UTC,Reinstalling duplicity after installing b2 (pip install b2) apparently did the trick.
1743247,2018-01-17 23:19:24 UTC,"I solved my problem; b2 was failing to import because of a missing ""backports.functools_lru_cache"""
1743247,2018-01-17 13:18:17 UTC,"Here's what ""pip2 install b2"" gives (each time I run it):"
1743250,2018-01-15 01:29:46 UTC,What are you looking for in the way of support? Presumably you want to be able to subscribe UTF-8 encoded addresses with non-ascii. Do you also want to allow non-ascii list names?
1743250,2018-01-15 06:12:47 UTC,"On Mon, Jan 15 2018, Mark Sapiro wrote:"
1743250,2018-01-15 20:49:11 UTC,It would be good to submit this issue at https://gitlab.com/mailman/mailman/issues/ for Mailman 3.
1743250,2018-01-16 06:17:36 UTC,"Ok, done."
1743251,2018-01-14 21:27:15 UTC,Thanks for your report!
1743252,2018-02-19 11:01:51 UTC,"Well, it's for Ubuntu packaging, right?
The problem I see is that the upstream documentation provides Ubuntu installation too, so it really depends on the package versions :("
1743252,2018-02-14 14:00:10 UTC,"I'm not sure what the behavior is in oslo.config if you have multiple config files, I assumed it would merge them."
1743252,2018-01-24 17:06:52 UTC,"You are right. Maybe this is a result of upgrading from Newton to Pike, which I did.
Since placement is mandatory in Pike I updated nova.conf then I always found placement authentication errors in the logs saying that user/password were invalid."
1743252,2018-01-23 20:01:55 UTC,"Well, to be fair, it's listing two config files:"
1743255,2018-01-14 22:28:23 UTC,"Cover art will at least be initialized/updated when you load a track from the library. I've added this feature during the development of 2.1. Embedded cover art has to be changed with an external editor and manually reloading it was tedious. So maybe we already have the functionality for lazily loading cover art, at least partially."
1743257,2020-02-29 15:08:26 UTC,Fixed in Focal.
1743258,2020-02-29 15:07:17 UTC,Fixed in Focal.
1743259,2020-06-18 04:49:41 UTC,"Please tell us if you still experience this problem, particularly if you experience it with a newer version of Ubuntu."
1743259,2020-08-18 04:17:20 UTC,[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]
1743259,2018-01-21 21:22:20 UTC,"I tested this on a non-Libreboot (i.e., stock Lenovo BIOS) ThinkPad X200s. Exactly the same problem."
1743259,2020-06-18 04:48:50 UTC,"The attached files suggest 3D acceleration is working, fundamentally. Though this might be an issue specific to Compiz/Unity."
1743259,2020-08-18 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1743266,2019-08-10 04:17:17 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1743266,2019-06-10 09:41:42 UTC,"I have set this to incomplete, because it was magically fixed.
If it occurs again, please reopen it and attach the recent mixxx.log."
1743266,2019-06-02 10:26:18 UTC,"Since Benis can no longer reproduce, @fabio: are you still seeing this crash with macOS 10.13.6 and mixxx 2.2.1?"
1743266,2019-02-25 19:05:35 UTC,"For the record I haven't seen this issue since I last commented, and I've been using GLSL the whole time."
1743266,2019-02-25 16:44:16 UTC,"Fabio, what GPU are you using?"
1743266,2019-02-25 07:21:39 UTC,"Debug [Main]:
GLWaveformRendererSignalShader::loadShaders Warning [Main]: QString::arg: Argument missing: ""Q"" , 0 Warning [Main]: QString::arg: Argument missing: ""IN"" , 0 Warning [Main]: QString::arg: Argument missing: ""OUT"" , 0 Warning [Main]: QString::arg: Argument missing: ""C"" , 0 Warning [Main]:"
1743266,2019-02-25 07:11:35 UTC,Please post the mixxx.log file from a crashing run. https://www.mixxx.org/wiki/doku.php/finding_the_mixxx.log_file
1743266,2019-02-25 03:11:12 UTC,I have the exact same problem!
1743266,2018-12-29 23:08:15 UTC,"OK I have set it to ""Invalid"" for now. Feel free to reopen it if the issue is back."
1743266,2018-09-11 18:42:44 UTC,"Also, neither of those other bugs seem to be related to loading tracks."
1743266,2018-12-29 22:29:29 UTC,"For whatever reason, I can't reproduce this any more. Not really sure what combination of things accounts for that but I am more than happy to see the back of it."
1743266,2018-01-15 07:33:01 UTC,Mixxx is able to hang the OS? That sounds very strange!
1743266,2018-01-15 18:44:47 UTC,"I've attached the log file again following the latest crash, hopefully more revealing this time. Unfortunately I can't run a backtrace because it hangs my entire system and I can't get access to any other apps etc."
1743266,2018-01-15 19:25:56 UTC,This type of problem can usually be traced back to a failing hard drive (where the OS is blocking waiting on the drive to read a bad sector.) Can you start up in Recovery mode and use Disk Doctor to check the drive for errors?
1743266,2018-01-15 20:48:25 UTC,"The Fiplab app you mean? I don't currently have it, will look into it if I get a chance. It seems a bit odd that something so specific would be caused by an SSD fault though."
1743266,2018-01-16 23:30:13 UTC,"Sure, but it also seems odd that a user-land application could cause the OS itself to hang. :) Unless there's a kernel bug in the version of the OS you have (are you on the latest?) that the Qt framework Mixxx uses is doing just the wrong thing to trigger. While it may not be the HD specifically, this type of thing is usually a hardware or driver problem. (Spinning HDs just tend to be the first hardware components to fail.)"
1743266,2018-01-16 23:31:21 UTC,"Oh, that reminds me, in case it's a video driver problem, try changing the waveform rendering option in Mixxx's preferences to Software (or None) before you try to load a track and see if that helps."
1743266,2018-01-17 11:04:11 UTC,"Can not confirm this crash with latest 2.1.0-beta1 (build 2.1 r6484) on macOS 10.13.2.
Tested with a Macbook way older than yours."
1743266,2018-01-18 23:58:43 UTC,"Thanks for the detailed report.
Still can not reproduce the crash with having RGB (GLSL) selected on my old machine with Intel HD Graphics 3000:"
1743266,2018-01-19 18:56:50 UTC,Crash file attached.
1743266,2018-12-29 22:30:13 UTC,"There isn't a 'Can't reproduce' or 'Fixed itself' status, but if somebody wants to close this, feel free."
1743266,2018-01-19 20:45:24 UTC,Ugh the more I try to reproduce this the weirder and less consistent it seems to get.
1743266,2018-09-11 17:15:45 UTC,"Having looked at a couple of similar bugs - https://bugs.launchpad.net/mixxx/+bug/1789059 and https://bugs.launchpad.net/mixxx/+bug/1791510 - it's occurred to me I wasn't that descriptive when I said this hangs my entire system. It freezes the GUI (with the exception of the mouse cursor, though eventually that succumbs too), but if a track is playing the audio will continue for maybe a minute before the system quits and takes me to (for some reason) the login screen..."
1743266,2018-09-11 18:37:58 UTC,"I am doubtful this is the same as either of those bugs. In neither of those bugs does the cursor freeze or the system restarts. However, it is plausible that all these bugs have related causes."
1743266,2018-10-17 14:11:10 UTC,"I finally got backtraces for Bug #1789059 and those were related to loading tracks. However, the deadlocks were in /usr/lib64/libX11.so.6 not Qt or Mixxx, whereas the backtrace in comment #11 here indicates the crash is related to OpenGL, so these do seem to be separate bugs. I am a bit confused by the backtrace mentioning com.apple.GeForceGLDriver considering the machine does not have an nVidia GeForce GPU."
1743266,2018-10-17 18:37:00 UTC,This is the 'About this Mac' dialog.
1743266,2018-10-17 18:38:26 UTC,"This, on the other hand, is the System Report, which suggests I do in fact have a GeForce graphics card. Slightly misleading.."
1743266,2018-10-17 18:39:43 UTC,"Be, in answer to your question, yes. I haven't yet found a build or release where this doesn't come up."
1743266,2018-10-17 19:40:26 UTC,"Well this is interesting, I've used gfxCardStatus to force either integrated (ie Intel) or discrete (ie NVIDIA) graphics before I launch Mixxx. I can't get it to crash while it's forced to use the integrated GPU, however I tried to load one track with the discrete GPU forced and it promptly crashed."
1743266,2018-10-17 20:07:18 UTC,"Thanks for testing this further. It's not clear to me whether the bug is in Mixxx's OpenGL code or the nVidia driver. If the problem is in the driver, we still might be able to work around it in Mixxx."
1743266,2018-10-19 14:09:50 UTC,Bumping the milestone back to 2.3.0 unless someone steps up to fix this now.
1743266,2018-04-26 04:17:22 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1743266,2018-01-18 21:31:45 UTC,"Hi everybody, thanks for all the tips etc. Managed to narrow this down some more, appears to be related to two things: a video/graphics issue of some kind, and files that *aren't* being loaded for the first time."
1743269,2018-01-17 20:15:30 UTC,"Excellent! Hope the commits are included soon in the coming updates.
Thanks!"
1743269,2018-01-15 00:00:06 UTC,This change was made by a bot.
1743269,2018-01-16 19:43:00 UTC,"We can perform a ""Reverse"" kernel bisect to identify the commit that fixes this bug in mainline.  We first need to identify the last kernel version that had the bug and the first kernel that did no."
1743269,2018-01-16 21:05:05 UTC,Tested:
1743269,2018-01-17 18:10:29 UTC,"I built a test kernel with two commits 7d5905dc14a and b29c6ef7bb.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1743269"
1743269,2018-01-17 18:38:01 UTC,You welcome! I'm happy to help!
1743269,2018-01-17 20:01:55 UTC,Thanks again for testing.  I'll submit an SRU request to have these two commits included in the Ubuntu kernel.
1743269,2018-01-19 15:42:23 UTC,"Submitted SRU request for Artful and Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089416.html"
1743269,2018-03-19 10:56:46 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1743269,2018-03-22 16:11:25 UTC,I have tested the kernel in -proposed and the problem is solved.
1743269,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1743269,2019-10-03 08:24:10 UTC,Patch can be found in 4.15 Bionic as well.
1743284,2018-01-17 09:12:01 UTC,i could not reproduced the same error on my environment
1743284,2018-01-31 02:42:01 UTC,"@Deepak Mouryam, You have to remove the entire physical network segment, just the vlan range."
1743285,2019-09-19 16:56:36 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.opendev.org/533553
Reason: We now do this"
1743285,2018-01-15 08:16:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533553"
1743288,2020-07-01 21:08:22 UTC,"Thank you for your bug report, it does sound like a local corruption rather than a bug though"
1743291,2018-01-17 03:46:05 UTC,"Hello, this machine has some hardware issues:"
1743292,2020-09-11 05:12:41 UTC,Closing because INVALID.
1743292,2018-01-17 05:34:07 UTC,I've tried what you said and yes it works. Thank you.
1743292,2018-01-15 10:28:25 UTC,"problem not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1743293,2020-05-29 16:15:31 UTC,I believe I have run into the same issue with valgrind 3.7.0-6+rpi6 (current as of the date of this post.) Usage on Raspberry Pi OS results in thousands of errors reported for code that does not report errors on X86 platforms. I have performed the following tests.
1743293,2018-01-15 15:25:22 UTC,To the best of my knowlage valgrind upstream doesn't support armv6. Years ago I was pointed to a patch that made it work on armv6 and applied it in raspbian.
1743301,2018-01-16 12:52:50 UTC,PR addressing the problem: https://github.com/snapcore/snapd/pull/4494
1743301,2018-01-16 06:47:43 UTC,"[01:46 haris ~]$ cat /etc/os-release
NAME=Korora
VERSION=""26 (Bloat)""
ID=korora
ID_LIKE=fedora
VERSION_ID=26
PRETTY_NAME=""Korora 26 (Bloat)""
ANSI_COLOR=""0;34""
CPE_NAME=""cpe:/o:kororaproject:korora:26""
HOME_URL=""https://kororaproject.org/""
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
1743301,2018-01-16 06:36:48 UTC,"Let me take this for a spin. IIRC Korora is based on Fedora, so snapd should work as long as it works on Fedora."
1743301,2018-01-15 11:50:46 UTC,your Korona kernel is missing features ...
1743301,2018-01-16 12:06:30 UTC,It's a bug in snapd. I'll look into fixing this.
1743303,2018-01-15 06:36:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533505"
1743324,2018-01-15 08:43:05 UTC,The issue was first mentioned on isc-bugs. The response I got is:
1743334,2018-01-15 10:36:18 UTC,"Cheers - looks like a new version (0.31) was just uploaded to unstable. Should we wait a minute for that to sync + migrate and backport that one instead? (If so, would you mind testing that one too please?)"
1743334,2018-01-15 19:05:46 UTC,Sure.
1743337,2020-11-16 18:18:41 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1743337,2021-01-16 04:17:53 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1743339,2019-04-11 20:06:55 UTC,"I might experience the same problem, here is the stacktrace:"
1743339,2020-01-05 18:23:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743349,2018-01-16 16:20:43 UTC,Created https://jira.percona.com/browse/PT-248 to track this issue.
1743349,2018-01-17 08:11:54 UTC,"Is my account transferred there (to JIRA)?
I can access, but cannot comment (is that expected behaviour?).
Regards."
1743349,2018-01-24 22:23:32 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1471
1743350,2018-01-17 07:43:22 UTC,Accidentally uploaded the wrong a.out; my bad. Here's the right one.
1743354,2018-01-24 12:41:30 UTC,"Are all your shares on zfs? Or, more importantly, all shares where this problem happens?"
1743354,2018-01-15 13:07:45 UTC,the problem occurs randomly so I think it's a race condition or so
1743354,2018-01-23 12:25:01 UTC,Thanks for filing this bug in Ubuntu.
1743354,2018-01-23 16:22:28 UTC,2018-01-23 13:25 GMT+01:00 Andreas Hasenack <email address hidden>:
1743354,2018-05-31 11:41:36 UTC,i have also  'nt acl support = No'  in samba config
1743354,2018-05-31 10:13:38 UTC,"yes , give acccess to all solve the problem.
No i I do not use acl , ( for each shared folder two groups of users are
associated. A group for rw and one for ro . Groups used  in samba [valid
users] and [  write list ]
in addition I force the creation of all ifle with the same owner and group
([force user]  [force group ] )
Reading  logs I thought it was related to acl, so I disabled them. Since I
disabled them, it seems to me  that the problem has not occurred again.
(from pool history  2018-02-06.18:37:04 zfs set xattr=off pool_z2_samba )"
1743354,2018-05-30 18:22:20 UTC,"In another comment you said you had to chmod files so the user would get access, correct? Are you using, or relying on, posix ACLs? If yes, did you enable that support in the zfs datasets you are exporting?"
1743354,2018-05-30 07:39:39 UTC,"@ahasenack
Yes. Unfortunately we still have about 2000 clients with windows xp.
But I can not verify if the situation described in the bug has occurred.
I doubt, because our average user is very obtuse and therefore usually calls helpdesk to restore files"
1743354,2018-01-24 09:23:12 UTC,"moreover all shared files are owned by local user nobody and all shares
have  option force user nobody. See a share config example:
[Staff]
comment = Staff DAI
path = /samba/shares/DAI/groups/dip_staff
shadow:format = %Y-%m-%d_%H.%M.%S--5d
shadow:sort = desc
shadow:snapdir = /samba/shares/DAI/.zfs/snapshot
shadow:basedir = /samba/shares/DAI
shadow:localtime = yes
valid users = @dai_dip_staff_ro,@dai_dip_staff_rw
write list  = @dai_dip_staff_rw
force user = nobody
force group = dai_quota"
1743354,2018-05-29 20:05:17 UTC,I wonder if this from the 4.3.12 release notes is relevant:
1743354,2018-01-24 13:27:46 UTC,2018-01-24 13:41 GMT+01:00 Andreas Hasenack <email address hidden>:
1743354,2018-01-24 09:27:47 UTC,"moreover all shared files are owned by local user nobody and all shares have  option force user nobody. See a share config example:
[Staff]
comment = Staff DAI
path = /samba/shares/DAI/groups/dip_staff
shadow:format = %Y-%m-%d_%H.%M.%S--5d
shadow:sort = desc
shadow:snapdir = /samba/shares/DAI/.zfs/snapshot
shadow:basedir = /samba/shares/DAI
shadow:localtime = yes
valid users = @dai_dip_staff_ro,@dai_dip_staff_rw
write list  = @dai_dip_staff_rw
force user = nobody
force group = dai_quota"
1743354,2018-05-30 07:33:26 UTC,----------------------------------------------------------------
1743358,2018-01-15 11:30:07 UTC,This change was made by a bot.
1743358,2018-03-27 11:29:09 UTC,"This bug is not specific to  Kernel 3.13.0-139: it is present on at least 3.13.0-143 as well. For completeness hardware still as of today:
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: M5461 [HDA ULI M5461], device 0: ALC880 Analog [ALC880 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: M5461 [HDA ULI M5461], device 1: ALC880 Digital [ALC880 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0"
1743358,2018-03-27 12:00:29 UTC,Further research seems to suggest that the bug forces a reset of Sound Settings to: 'Play Sound Through - Dummy Output' which I am unable to reset as there are no other output options offered.
1743358,2018-04-12 17:15:20 UTC,Took kernel 3.13.0-144 9/4/18. PC booted every day. No other settings altered. Sound suddenly back when boot pm 12/4/18.
1743358,2018-04-12 18:07:09 UTC,"Sound lasted for approx 2 hours [pm 12/4/18] then ceased. PC running throughout: no settings altered, no programming changes."
1743364,2018-01-22 19:56:32 UTC,The package has been published and the bug is being set to Fix Released
1743364,2018-01-22 19:16:37 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-111.134~14.04.1
1743364,2018-01-22 18:58:35 UTC,"Setting automated-testing to 'Fix Released', no regression found on amd64 and i386."
1743364,2018-01-16 17:50:04 UTC,Regression tests results for 4.4.0-110.133~14.04.2 didn't show any regression (tests not finished yet for 4.4.0-111.134~14.04.1).
1743364,2018-01-19 06:56:26 UTC,"4.4.0-111.134~14.04.1 - generic
Regression test CMPL."
1743366,2018-01-16 07:03:42 UTC,Iain is working on re-enabling the use of systemd user sessions we had under Unity
1743366,2018-01-16 03:09:00 UTC,"We discussed on IRC that this is because *no* systemd units are being activated; the user session is not being run under systemd.  This is a regression vs. unity, and should be considered a bug in the desktop session as a whole."
1743367,2018-01-22 19:57:48 UTC,The package has been published and the bug is being set to Fix Released
1743367,2018-01-22 19:15:15 UTC,This bug was fixed in the package linux-euclid - 4.4.0-9023.24
1743381,2019-08-23 11:48:23 UTC,Version 1.5.7+dfsg1-2 mitigates this problem by defaulting to the X11 backend when available.
1743381,2019-08-14 13:52:14 UTC,"Known problem under Wayland, you can force the X11 backend as a workaround:"
1743385,2018-01-31 16:29:57 UTC,Filed it here at the request of the Juju Core team :)
1743385,2018-01-31 01:24:41 UTC,"I am not sure if this is the best place to report bug or make suggestions for gomaasapi as although we, as Juju, are interested in it and are using it, it feels like this may not be solely on Juju team."
1743386,2018-01-31 01:26:15 UTC,"I am not sure if this is the best place to report bug or make suggestions for gomaasapi as although we, as Juju, are interested in it and are using it, it feels like this may not be solely on Juju team."
1743386,2020-06-02 10:39:58 UTC,@petevg: this would be needed for Juju tagging MAAS with unit/services feature we talked about last week
1743386,2020-06-01 16:11:03 UTC,Can someone mark this as Triaged+Wishlist on the gomaasapi side?
1743386,2018-01-31 06:05:39 UTC,Should we be adding https://bugs.launchpad.net/gomaasapi ?
1743398,2018-01-15 15:21:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533701"
1743399,2018-01-17 11:32:22 UTC,I forgot to mention:
1743399,2018-03-01 14:24:28 UTC,"I thought I had mentiond this already, but apparently I haven't.  For me the redraw issues only occur with this kernel (and newer), if the output is rotate (left/right)."
1743399,2018-01-17 11:34:53 UTC,hibernate also does not work with kernel 4.13.0-26:
1743399,2018-01-17 14:15:08 UTC,"That's exactly what I observed. With the 4.10 kernel, everything works well."
1743399,2018-01-23 13:31:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743399,2018-01-23 13:39:38 UTC,Also the same issue with an Atom.
1743399,2018-02-20 08:57:56 UTC,"The originally linked .png's are expired=gone.
Are they what is reported here: https://bugs.launchpad.net/bugs/1724639 ?"
1743399,2018-02-20 09:46:17 UTC,"On Tue 2018-02-20 (08:57), J. Janel wrote:

> The originally linked .png's are expired=gone.
"
1743399,2019-10-04 04:26:13 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1743399,2018-01-16 18:21:47 UTC,WiFi problem with 4.13.0-26 generic:
1743401,2018-01-17 15:54:32 UTC,"Sorry I didn't think about this before, but I gave the non-ASAN version of the application a spin with valgrind 3.13 and it doesn't report any memory errors with it - so it's possible this is either something valgrind won't catch or a false positive by ASAN."
1743401,2018-01-19 23:35:13 UTC,I rebuild the package without optimizations got some more data. The ASAN out now matches the gdb one
1743405,2018-01-15 16:14:44 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/533721"
1743405,2018-01-15 16:17:03 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/533722"
1743405,2018-04-17 20:16:03 UTC,"Reviewed:  https://review.openstack.org/533721
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=5e16c93cfddc7cd0e45910c1ad4571a67846e5c7
Submitter: Zuul
Branch:    stable/pike"
1743405,2018-05-02 20:08:43 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/565892"
1743405,2018-06-01 15:33:54 UTC,The fix is not yet merged for ocata.
1743405,2018-05-02 20:10:12 UTC,"Change abandoned by Pierre Blanc (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/533722
Reason: The cherry-pick from pike is on this new review: https://review.openstack.org/#/c/565892/"
1743406,2018-02-26 20:57:58 UTC," Hi,
yes it's the same issue. make your bug as duplicate of #1751846.
I noticed that your bug affects me too"
1743406,2018-05-21 16:18:50 UTC,works fine on 32 bits
1743406,2018-02-26 20:40:51 UTC,"While examining other bug reports, it sounds like my bug report may be the same thing that you're describing? https://bugs.launchpad.net/compiz/+bug/1751846"
1743411,2018-05-21 16:17:33 UTC,"works fine if ubuntu 32 bits
reproduced only on 64 bits"
1743418,2018-01-22 20:03:46 UTC,The package has been published and the bug is being set to Fix Released
1743418,2018-01-22 19:13:51 UTC,This bug was fixed in the package linux-oem - 4.13.0-1017.18
1743422,2018-01-16 14:40:16 UTC,I was also able to reproduce it on 17.10 _on metal_.
1743422,2018-01-23 14:19:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743422,2018-01-16 19:31:27 UTC,Screenshot of the compizconfig-settings-manager Unity launcher settings
1743422,2018-01-16 14:35:34 UTC,"Mh, such values are quite hard to define depending on hardware in use (for example a touchpad could be slower than a regular mouse or a trackpoint)..."
1743422,2018-01-17 07:01:31 UTC,"For me it works well. Also default values are selected carefully so that user need to apply little bit of pressure with pointer to reveal the launcher. Otherwise it may reveal accidentally, for example when you try to copy text from left most side of full-screen application."
1743423,2018-08-11 13:00:21 UTC,This problem was returning intermittently.  I am now moving on to a more recent release of Ubuntu so I no longer have am rebooting this particular OS version.
1743423,2018-01-23 00:20:34 UTC,"Not sure if I have the same issue, but if I let my system go to sleep/suspend at the login screen, when I resume I cannot click in the password prompt and thus cannot type my password to login.  For some reason the mouse will not give the password prompt text box focus."
1743424,2018-01-24 08:43:58 UTC,"Hi,"
1743424,2018-02-01 12:34:44 UTC,Hi Shinguz
1743424,2018-01-24 09:51:15 UTC,Hello Shivani
1743424,2018-02-01 17:59:12 UTC,See attachments...
1743427,2018-02-05 22:50:26 UTC,"Hans Matros, to see if this is resolved upstream, could you use the latest kernel 4.15.1 without the WORKAROUND?"
1743427,2018-01-22 19:32:38 UTC,Thanks for your support. I have created an upstream bug report:
1743427,2018-01-18 06:35:36 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/radeon"
1743427,2018-01-17 16:04:01 UTC,"Thanks this kernel version can boot the system, but the performance of the UI have a problem. Everything lags and also with youtube video's there are a lot of frame drops."
1743427,2018-01-16 21:07:59 UTC,Dear Kai-Heng Feng!
1743427,2018-01-16 04:53:16 UTC,"Please try this kernel, http://people.canonical.com/~khfeng/lp1743427/"
1743427,2018-01-15 18:06:13 UTC,apport information
1743427,2018-01-15 18:06:09 UTC,apport information
1743427,2018-01-15 18:06:08 UTC,apport information
1743427,2018-01-15 18:06:07 UTC,apport information
1743427,2018-01-15 18:06:06 UTC,apport information
1743427,2018-01-15 18:06:05 UTC,apport information
1743427,2018-01-17 05:25:50 UTC,"Can you test the mainline kernel?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc8"
1743427,2018-01-15 18:06:04 UTC,apport information
1743427,2018-01-15 18:06:03 UTC,apport information
1743427,2018-01-15 18:06:02 UTC,apport information
1743427,2018-01-15 18:06:00 UTC,apport information
1743427,2018-01-15 17:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743427,2018-01-15 18:06:10 UTC,apport information
1743427,2018-01-15 18:06:15 UTC,apport information
1743427,2018-01-15 18:06:16 UTC,apport information
1743427,2018-01-15 18:06:11 UTC,apport information
1743429,2018-01-24 11:28:01 UTC,I thought from mpt's guidance we wouldn't be supporting animations for screenshots https://forum.snapcraft.io/t/restrictions-on-screenshots-and-videos-in-snap-listings/3087/2
1743429,2018-01-17 14:52:11 UTC,thanks
1743429,2018-01-17 12:17:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1743435,2018-01-30 12:52:32 UTC,This keeps happening pretty often.
1743436,2018-01-16 06:03:34 UTC,"Reviewed:  https://review.openstack.org/533728
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=6d9fdaa2c8609ce49487a7ef92464bcc0418e0e8
Submitter: Zuul
Branch:    master"
1743444,2019-10-04 04:26:04 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1743444,2018-01-15 21:26:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743447,2018-03-07 16:40:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743447,2018-02-20 20:23:57 UTC,I managed access /dev via initramsf and the UUID from the installation doesn't match the ones listed in /dev/disk/by-uuid/...
1743447,2018-02-20 19:28:50 UTC,I tried the daily desktop 18.04 2018-02-19 yesterday and it does work now. I am able to unlock the encrypted disk and do a normal installation ...
1743447,2018-04-10 08:39:58 UTC,I have the same issue but with an upgraded installation
1743450,2018-12-12 03:55:13 UTC,"Mmm, we are getting an error running gsa-sync on staging. Will need to fix that first."
1743450,2018-12-07 19:18:00 UTC,I'll be ready for that on Monday.
1743450,2018-12-06 11:31:53 UTC,"Carlos, we should make sure we do this part before Nat goes away for Christmas. Meaning, the part where he creates a new distribution list on GSA *testing* and it syncs correctly to karlstaging."
1743450,2018-11-21 12:56:01 UTC,"Yes, I think you’re right that this is the right place to start. Let’s make sure we have a petri dish that we trust before beginning."
1743450,2018-11-21 05:32:17 UTC,"Paul, do you think this is where we need to start to work on this?"
1743450,2018-02-02 21:56:12 UTC,"We're back to making this the next priority. We have several tickets open we can work on, so plenty of work for Feb."
1743452,2019-08-31 23:10:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743452,2018-05-10 12:26:49 UTC,"This also breaks the Go extension of Visual Studio Code: https://github.com/Microsoft/vscode-go/issues/1636#issuecomment-387962213
A tool used by it, gopkgs, uses filepath.Walk (actually a parallel implementation of it, but it's the same issue) to list the packages in GOROOT, but filepath.Walk does not follow symlinks."
1743452,2018-03-29 19:17:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743456,2018-12-12 03:53:57 UTC,"Instead of SQL, the plan is to push logging info to graylog, then use its extractors, dashboards, and alerts to process it."
1743457,2018-12-12 03:51:41 UTC,"This will require adding this specific information to the logs, so that it can be extracted by graylog."
1743458,2018-12-19 10:04:57 UTC,This issue was fixed in the openstack/nova 16.1.7 release.
1743458,2018-07-10 15:22:22 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/581399"
1743458,2018-11-07 22:19:28 UTC,"Reviewed:  https://review.openstack.org/587249
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5ddcda02a8500ef88ee22b2cabf6d23527ad8de8
Submitter: Zuul
Branch:    stable/pike"
1743458,2018-07-30 23:15:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/587249"
1743458,2018-07-30 23:14:49 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/587248"
1743458,2018-07-30 17:55:53 UTC,"Reviewed:  https://review.openstack.org/581399
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e57f66a26daf858d1348c8406108a33a323b7b2e
Submitter: Zuul
Branch:    stable/queens"
1743458,2018-07-30 17:55:43 UTC,"Reviewed:  https://review.openstack.org/581398
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0f253ea9c5f3f3d97bc049f00d1bcdf2761f0736
Submitter: Zuul
Branch:    stable/queens"
1743458,2018-07-30 16:08:34 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1743458,2018-07-10 15:22:07 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/581398"
1743458,2018-11-07 22:19:19 UTC,"Reviewed:  https://review.openstack.org/587248
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2460d0ef9438026b1691697022a86030b9f2d21e
Submitter: Zuul
Branch:    stable/pike"
1743458,2018-06-27 22:06:52 UTC,"Reviewed:  https://review.openstack.org/533805
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=abd01a757b8a83d714a6ab8b5085e7cc1b4a2c5c
Submitter: Zuul
Branch:    master"
1743458,2018-06-27 22:06:40 UTC,"Reviewed:  https://review.openstack.org/533804
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d16d0d553b20fd45a83cf7c68bc477b97aece9a1
Submitter: Zuul
Branch:    master"
1743458,2018-05-07 11:03:11 UTC,"It appears this also affects VLAN tags, which should be exposed through the metadata service but are not."
1743458,2018-01-15 21:43:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/533805"
1743458,2018-01-15 20:17:12 UTC,"I believe this is happening because in _build_device_metadata [1], we only consider <interface> elements in the libvirt XML, whereas PF passthrough appears as a <hostdev> element."
1743458,2018-09-24 14:47:21 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1743463,2018-01-15 21:13:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/533799"
1743463,2018-01-18 19:43:37 UTC,"Reviewed:  https://review.openstack.org/535330
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4db37df648adeb425d6dcc21138dae74e8558e5a
Submitter: Zuul
Branch:    master"
1743463,2018-01-18 13:52:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/535330"
1743463,2018-01-17 18:16:47 UTC,"Reviewed:  https://review.openstack.org/533799
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=602437216f56b3a27addaec11c14002e7e3a8443
Submitter: Zuul
Branch:    master"
1743463,2018-01-15 21:14:03 UTC,Trace of the error:
1743470,2018-01-18 07:03:28 UTC,Problem already resolved in Caja 1.19.3 https://github.com/mate-desktop/caja/issues/904#issuecomment-357980717. This was a duplicate of issue https://github.com/mate-desktop/caja/issues/880
1743470,2018-01-15 21:40:32 UTC,Reported also here https://github.com/mate-desktop/caja/issues/904
1743471,2018-03-18 18:26:51 UTC,"I got the same problem but nautilus-actions-config-tool may work if you log out and then log in on ""Ubuntu on Xorg"""
1743471,2018-02-22 16:16:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743479,2019-10-10 22:25:25 UTC,"No official Linux drivers available for Validity Sensors: 138a:0097 as of October 11, 2019 on Ubuntu 18.04."
1743479,2019-09-01 13:01:21 UTC,"No official Linux drivers available for Validity Sensors: 138a:0097 as of September 1, 2019 on Ubuntu 18.04"
1743479,2018-07-25 16:37:14 UTC,I second that. For Ubuntu 18.04 LTS. Same hardware on Lenovo X1 Yoga.
1743479,2018-07-25 16:34:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743479,2019-08-27 04:45:16 UTC,Same problem with same device on 19.04 using a Thinkpad X1 Carbon 5th generation.
1743479,2019-03-13 11:45:56 UTC,"Hi,
same for Ubuntu 18.04 LTS and Debian 10 testing."
1743479,2019-06-25 18:28:23 UTC,"I'd like to request this as well.  Ubuntu 18.04.  Tested the ""prototype"" on my T470 on Ubuntu 16.04 before I upgraded and it worked as well.  Would be outstanding to have fingerprint functionality on this thing."
1743479,2020-02-21 10:46:20 UTC,I have the same issue on my Lenovo T570 laptop which has been certified for Ubuntu as well.
1743479,2020-04-27 02:03:36 UTC,"Same Bug. ""Could not access any fingerprint readers. Please contact your system administrator for help"" when trying to enable Fingerprint login under the user settings in Ubuntu 20.04"
1743479,2020-04-27 09:43:53 UTC,For different reasons I switched to Manjaro. On that distribution I installed a package that got the fingerprint scanner working. The package is: https://aur.archlinux.org/packages/libfprint-vfs0097-git
1743479,2020-11-25 15:06:17 UTC,Drivers requests are upstream bugs and as such should be redirected to the official wiki
1743489,2018-03-29 08:50:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743489,2018-07-30 22:38:00 UTC,I have a similar situation: wifi will randomly disappear. Some bits from the logs:
1743489,2018-07-30 22:38:35 UTC,"And I'm on Ubuntu 18.04. I think I saw it on Ubuntu 17.10 as well, but happens reasonably frequent now, every few days."
1743489,2018-08-01 04:00:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743489,2018-08-06 07:20:19 UTC,It's very similar to the behaviour described here: https://bbs.archlinux.org/viewtopic.php?id=231159
1743493,2018-01-31 13:17:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539526"
1743493,2018-09-06 07:49:14 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/539526
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1743494,2018-03-21 23:18:28 UTC,This issue was fixed in the openstack/os-vif 1.10.0 release.
1743494,2018-01-16 04:25:09 UTC,Gerrit review: https://review.openstack.org/#/c/531674/
1743494,2018-01-18 12:55:37 UTC,"Reviewed:  https://review.openstack.org/531674
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=84688a22db22039f5566c1439c3983db23672a45
Submitter: Zuul
Branch:    master"
1743494,2019-10-30 14:18:57 UTC,This issue was fixed in the openstack/os-vif 1.9.2 release.
1743494,2018-05-03 16:31:06 UTC,"Reviewed:  https://review.openstack.org/554917
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=b026d54016c714a09aab9de0afd264a17d125dcd
Submitter: Zuul
Branch:    stable/queens"
1743494,2018-03-21 13:13:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554917"
1743495,2020-01-06 11:10:13 UTC,"Hello,
4.13.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1743495,2018-01-26 18:28:44 UTC,I tested mainline ( http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/linux-image-4.15.0-041500rc9-generic_4.15.0-041500rc9.201801212130_amd64.deb ) as I have been asked to do on other kernel issues. The problem persists.
1743495,2018-01-22 21:10:35 UTC,Problem still present in newly issued 4.13.0-31-generic
1743495,2018-01-16 04:09:41 UTC,lspci output of device from 4.10
1743495,2018-01-16 04:03:22 UTC,Attaching dmesg output from booting 4.13 with the card inserted. Some xhci messages may be of interest.
1743499,2018-02-13 20:26:12 UTC,I'm not sure that this needs a spec -- depends on the approach taken to do this and how complicated it may be. So either add a spec or update the description with more details as to what this concurrency entails.
1743509,2018-03-19 05:57:09 UTC,"Reviewed:  https://review.openstack.org/554111
Committed: https://git.openstack.org/cgit/openstack/puppet-designate/commit/?id=72afdccb8f3d174bacd110db9f5e42774140c3b0
Submitter: Zuul
Branch:    stable/pike"
1743509,2018-03-16 22:38:15 UTC,"Reviewed:  https://review.openstack.org/534214
Committed: https://git.openstack.org/cgit/openstack/puppet-designate/commit/?id=bae7521e56aa32404e66b61a5b00b4bb3724ae79
Submitter: Zuul
Branch:    master"
1743509,2018-03-19 03:42:03 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554106"
1743509,2018-03-19 03:53:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554111"
1743509,2018-01-16 09:52:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534214"
1743509,2018-03-19 05:59:37 UTC,"Reviewed:  https://review.openstack.org/554106
Committed: https://git.openstack.org/cgit/openstack/puppet-designate/commit/?id=0ad1e9d20cc81c86beb5dc2b77d8cca4ce90f87e
Submitter: Zuul
Branch:    stable/queens"
1743509,2018-03-29 00:11:00 UTC,This issue was fixed in the openstack/puppet-designate 12.4.0 release.
1743509,2018-04-19 21:00:10 UTC,This issue was fixed in the openstack/puppet-designate 13.0.0 release.
1743509,2019-05-16 23:03:23 UTC,This issue was fixed in the openstack/puppet-designate 11.6.0 release.
1743510,2018-01-16 07:25:40 UTC,"StacktraceTop:
 gdu_application_ensure_client (app=app@entry=0x5555a0f2b190) at ../src/disks/gduapplication.c:123
 gdu_application_ensure_client (app=0x5555a0f2b190) at ../src/disks/gduapplication.c:294
 gdu_application_activate (_app=<optimized out>) at ../src/disks/gduapplication.c:289
 g_closure_invoke (closure=0x5555a0f267a0, return_value=0x0, n_param_values=1, param_values=0x7ffd877131a0, invocation_hint=0x7ffd87713120) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x5555a0f27120, detail=detail@entry=0, instance=instance@entry=0x5555a0f2b190, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffd877131a0) at ../../../../gobject/gsignal.c:3673"
1743510,2019-02-08 15:15:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743515,2018-01-16 09:52:26 UTC,Tested on an unprivileged bionic container on a xenial host. Everything seems to work for me.
1743515,2019-09-19 14:46:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1743515,2018-04-10 20:31:50 UTC,I have been trying to reproduce this with latest master that includes https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/342811 which I believe was the actual cause of this issue.
1743515,2018-01-25 14:45:22 UTC,"FWIW, the xenial host was configured following the instructions of [1]. This means I was using a confined container giving some extra permissions."
1743521,2020-02-22 06:45:36 UTC,Fix not work after reboot again
1743521,2018-01-23 08:48:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536717"
1743521,2018-08-01 03:12:18 UTC,"Change abandoned by JiWei (17366060309@163.com) on branch: master
Review: https://review.openstack.org/536717"
1743526,2018-01-16 08:32:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534179"
1743534,2018-01-17 23:55:04 UTC,*** This is an automated message ***
1743534,2018-01-17 18:24:32 UTC,Thanks for reporting.
1743537,2018-01-16 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743547,2018-01-26 09:50:53 UTC,"My problem with this bug, besides the error it gives on installing/updating/... of any software, is that I'm running an LTS that's supposedly still active/valid/supported, and the package already seems to have a non-responding email address..."
1743547,2018-01-26 21:40:00 UTC,"OK...
I did some digging;
 - the package seems to be without a maintainer...
 - the server seems to be unreachable
 - yes, hearse.krollmark.com resolves to an IP 198.22.63.14
 - no, even 60 hops is not enough to trace to it; after 10ge12-1.core1.det1.he.net (in I presume Detroit, MI, USA) there's one more IP number, and dark holes all the way down...
 - ""resolved"" the issue by removing the hearse package; neat idea, but unmaintained, and not essential for playing the game..."
1743548,2020-09-11 06:12:57 UTC,Closing because INVALID: Fixed >=1.0.
1743557,2020-06-18 04:44:40 UTC,Can you explain in different words what kind of problem you are experiencing?
1743557,2020-08-18 04:17:18 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1743558,2018-01-16 13:03:53 UTC,"Maybe we should use the linux admin tools to set a user's password, instead of generating a hash of our own. That way we won't be bypassing any local password policy set by an admin, for example."
1743558,2018-01-16 13:09:31 UTC,"Instead of:
        result, output = self.call_popen([""usermod"", ""-p"", crypted, username])"
1743558,2018-02-28 00:08:20 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu1
1743558,2018-01-29 19:43:16 UTC,"Turns out python(2)-passlib is in main, so all we need is to invoke a component-mismatch to have python3-passlib moved to main too. This does not involve a MIR. Thanks ack for pointing that out, I hadn't realized python-passlib was in main."
1743559,2020-01-06 11:12:07 UTC,"Hello,
4.13.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1743564,2018-01-25 00:19:19 UTC,Duplicate of https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1731294
1743564,2018-01-25 00:20:56 UTC,"Sorry, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842"
1743565,2018-05-01 16:46:59 UTC,Tested on 3.1
1743565,2020-04-21 12:32:34 UTC,Persists in 3.5
1743571,2018-01-23 07:38:29 UTC,"Change abandoned by Qi Peng (<email address hidden>) on branch: master
Review: https://review.openstack.org/534332"
1743571,2018-01-17 02:16:08 UTC,reson:
1743571,2018-01-16 14:42:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534332"
1743581,2019-06-24 04:17:21 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1743581,2019-04-24 07:58:36 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
If you need nomodeset to boot, you might want to install the proprietary video driver for your system.
Thanks"
1743587,2018-01-17 16:12:02 UTC,"Reviews happen upon push, not release. As a result, `snapcraft push` is the one that needs to report the review failure. Or are you saying that you simply don't think this deserves an error exit code?"
1743587,2018-01-17 07:16:52 UTC,Thanks for your bugreport.
1743587,2018-01-17 16:22:38 UTC,Yes. I'd expect snapcraft release to fail because it's unreviewed. But snapcraft push - well it does push the revision to the store succesfully. Review fails. But that seems a different issue. And even though the exit code is non zero it will have that revision in the store now.
1743588,2018-01-17 07:15:54 UTC,Could you please attach the exact error message that you see in the journal to this bugreport? This way we can check the udisks2 source more easily to see what exactly it is doing.
1743588,2018-01-18 09:25:12 UTC,@Michael: Thanks. We will line up a fix for this.
1743588,2018-01-18 08:01:06 UTC,Adding morphis who did the last uploads of this package.
1743588,2018-01-17 07:34:13 UTC,"Sure.
Jan 17 10:32:40 localhost.localdomain systemd-udevd[2023]: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1.
Jan 17 10:32:40 localhost.localdomain udisks2.udisksd[1345]: (udisksd:1345): udisks-CRITICAL **: [1345]: Error creating directory /etc/udisks2: Read-only file system [udiskslinuxdrive.c:244, configuration
Jan 17 10:32:39 localhost.localdomain kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk"
1743588,2018-01-22 12:32:03 UTC,https://code.launchpad.net/~kzapalowicz/snappy-hwe-snaps/+git/udisks2/+merge/336423
1743588,2018-01-18 08:00:47 UTC,"Thanks, this message is helpful! I looked at this and it seems udisks2 wants to create this dir if missing. We have two options:
1. ship the empty dir in the core snap
2. modify the udisks2 snap to set PACKAGE_SYSCONF_DIR to /var/snap/udisks2/current/etc
I think the later is preferable because this will make udisks2 actually able to store configuration there too."
1743592,2020-02-25 13:58:39 UTC,"On Tue, Feb 25, 2020 at 01:41:42PM -0000, T Jeske wrote:

> Will it log as ::ffff:10.1.2.3 if IPv6 is disabled on the system?
"
1743592,2021-01-12 15:06:34 UTC,@Nikita
1743592,2021-01-11 19:47:44 UTC,"I found this thread when trying to simplify automated nginx installation on Ubuntu 20.04. In my case, IPv6 is disabled with ipv6.disable=1, which breaks a fresh nginx installation from proceeding with ""nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)"". Specifically, apt fails when trying to install nginx, which break the automation workflow."
1743592,2020-04-06 12:17:30 UTC,"It is one thing to ipv6/conf/all/disabled=1, that is still supported. But ipv6.disable=1 should not be supported in any way. It is in direct conflict with modern software and proper deployments which should default to IPv6, in accordance with IETF BCP177."
1743592,2020-03-25 18:37:07 UTC,"Dan Streetman (ddstreet) wrote on 2020-02-21:

> For those coming here because their installation or upgrade of the 'nginx' package fails
> due to their system using ipv6.disabled=1, you need to edit the file...
"
1743592,2020-02-25 13:41:42 UTC,Will it log as ::ffff:10.1.2.3 if IPv6 is disabled on the system?
1743592,2019-10-22 02:13:00 UTC,"Debian proposal patch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=942817;filename=0001-Allow-nginx-to-start-on-ipv6-disabled-system.patch;msg=15"
1743592,2020-02-21 10:23:19 UTC,"For those coming here because their installation or upgrade of the 'nginx' package fails due to their system using ipv6.disabled=1, you need to edit the file ""/etc/nginx/sites-enabled/default"" and remove or comment out this line:"
1743592,2020-02-20 01:53:23 UTC,This change would break IPv6 support for nginx on all of my ISO spins. It's also doubly aggravating that edits to nginx.conf drive apt up the wall asking for 3 way merges; so I simply stopped editing nginx.conf and moved to using nginx/conf.d for *everything* because it kept breaking unattended-upgrades.
1743592,2020-02-20 00:40:44 UTC,"IPv6 should not be completely disabled on any system. This is not in keeping with Best Current Practices. See RFC 6540 (BCP 177). If an admin has manually disabled IPv6 on their system, it is their responsibility to also disable any services listening on IPv6 by default. This ""fix"" is antithetical to a modern Internet."
1743592,2020-02-19 22:15:25 UTC,"So from now on my IPv6-only installs will not work? That's just great, let's go back to 1992, when IPv6 did not exist yet."
1743592,2020-02-19 21:27:48 UTC,T Jeske:
1743592,2020-02-20 12:01:31 UTC,"Hm. After thinking about this a little, perhaps there is a way to have cake and consume it justly.
Since `ss` is now being used to check ports, I suggest a postinst check with `ss -6` to see if the icmp6 entry exists or not. If it does not exist, write a marker file out on disk that ipv6-appears-disabled. Check the marker during each postinst and select between the two ""default"" conditions automatically. Duplicate the `sites-available/default` with an additional copy `sites-available/default-ipv6`, with the inverse listen commented out, and the appropriate sites-enabled symlink. If either symlink is removed, the postinst doesn't recreate it."
1743592,2020-02-19 21:06:48 UTC,Opting for #1 is a stupid idea.
1743592,2019-11-02 22:15:10 UTC,This bug was fixed in the package nginx - 1.17.5-0ubuntu1
1743592,2019-10-28 01:34:13 UTC,"If I understand the situation correctly, my subjective opinion is that I don't think a ""fix"" for this is suitable for an SRU, but I welcome discussion if you disagree."
1743592,2019-10-26 19:35:17 UTC,"@teward, sound good I'll let you drive the focal upload since you were already in the middle of it and include solution #1 in it."
1743592,2019-10-26 19:22:07 UTC,"I am in favor of solution #1, and will drive this for Focal.  However, I have no call in whether this is accepted by the SRU team for SRU."
1743592,2019-10-23 13:56:29 UTC,So IMHO there is 2 ways to fix this:
1743592,2019-10-22 02:12:12 UTC,"Debian bug discussion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817"
1743592,2020-02-20 03:00:07 UTC,This will be reverted in an upload tomorrow.
1743592,2020-02-24 14:54:57 UTC,"On IRC, Simon suggested this:"
1743592,2020-02-20 12:24:28 UTC,Thomas Ward:
1743592,2020-02-20 12:35:44 UTC,Addition: Actually I think the best solution would be to test for IPv6 at runtime and produce just a warning instead of failing. Same for systems where IPv4 is disabled but the config still contains the IPv4 directive.
1743592,2020-02-20 17:27:00 UTC,"Using a single ""listen [::]:80 default_server ipv6only=off;"" seems to do the right thing in all situations: IPv4-only, IPv6-only or dual-stack."
1743592,2020-02-20 18:56:39 UTC,"Upon additional discussion among the Server Team, we have come to this conclusion:"
1743592,2020-02-21 06:21:07 UTC,To clarify what just happened:
1743594,2020-03-31 22:59:18 UTC,"I've tested on NRPE rev. 63(the latest release), the bug should be fixed already.
Could you confirm that the current release is working?
Thanks"
1743594,2020-03-30 08:01:38 UTC,"Reproduced with Juju 2.7.4-bionic-amd64, nrpe rev 42."
1743594,2020-01-30 14:43:04 UTC,Can still be easily reproduced with Juju 2.7.1
1743595,2019-11-20 04:17:29 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1743595,2018-01-16 19:54:57 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1743595,2018-01-16 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743599,2018-01-16 16:26:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534372"
1743599,2018-01-16 17:34:26 UTC,"Change abandoned by Major Hayden (<email address hidden>) on branch: master
Review: https://review.openstack.org/534372
Reason: Nevermind. This doesn't help with the bug. Something else is wrong."
1743599,2018-01-18 15:38:27 UTC,"Change abandoned by Major Hayden (<email address hidden>) on branch: master
Review: https://review.openstack.org/534372"
1743600,2018-01-17 01:32:26 UTC,"For comparison, what does it look like in Adwaita?"
1743603,2018-05-18 12:06:46 UTC,@Lance @Colleen it sounds to me like this is a valid issue with a couple potential solutions:
1743603,2018-11-16 21:46:31 UTC,"@Matthew,"
1743603,2018-01-16 17:19:29 UTC,"Warning message is triggered only if some service makes a call to keystone, but in case of non-keystone service calls like nova calling cinder, the request is going through 'authtoken' middleware[0] in paste pipeline which initializes keystonemiddleware.auth_token.BaseAuthProtocol[1] by loading 'service_token_roles', 'service_token_roles_required'[2] from cinder.conf file ."
1743603,2018-01-24 04:35:26 UTC,"It sounds like the workaround here is to define those configuration values in nova's authtoken section, right?"
1743603,2018-03-01 03:17:29 UTC,"I think we should remove the warning log from keystonemiddleware.
The service token is from nova to keystone, and the keystone service does not contain this parameter. And keystone service just authenticates the token wether it is user token or service token. If the keystonemiddleware judge the token is allowed expired and then the keystone service authenticate the token with 'allow_expired' parameter."
1743603,2018-03-04 16:05:25 UTC,"prashkre - just to clarify, in nova.conf's [keystone_authtoken] section you have service_token_roles_required set to true (which should suppress this log warning), and this message is appearing in the nova logs anyways?"
1743603,2018-03-16 19:45:29 UTC,"Given Colleen's response, is there anything left to do for this? I suppose we could clarify documentation or the log warning to be more clear per the last bit of comment #4."
1743603,2018-03-20 12:43:13 UTC,"Still waiting for clarification on my question to prashkre. Also re-reading prashkre's description, if the warning is appearing in the keystone log rather than the nova or cinder log that is really unexpected."
1743603,2018-03-21 13:47:20 UTC,"cmurphy - I see the warning message in keystone log. My environment has service token settings under [keystone_authtoken] section in nova.conf and cinder.conf as well. As explained through execution flow in bug description, warning message is being triggered because of not passing argument value at [0] for ""service_token_roles_required"" param by loading it from the conf, it should be something like at [1]"
1743611,2020-03-27 15:39:50 UTC,"Jason- Not working on this today, no. Unassigned myself, but may still work on it later."
1743611,2020-03-27 14:35:22 UTC,"Jeff, are you still/currently working on this?"
1743611,2019-12-23 16:40:20 UTC,Bumped to High since it has so much heat.
1743611,2019-12-16 22:37:17 UTC,I have pictures in case they'd be useful.
1743611,2019-04-16 00:56:49 UTC,"Thanks for taking this on, Jeff. It would be great if your version is more noticeable than the XUL version was. Maybe a little icon next to the input that provides the tooltip or popover on focus?"
1743611,2019-04-15 17:19:48 UTC,"In addition to the weeding scenario Terran mentioned above, this information is also useful when making ad-hoc decisions to reorder an item that has been declared lost/damaged."
1743611,2018-06-22 16:43:28 UTC,Confirmed this information is still missing in 3.1.
1743615,2018-04-28 06:31:01 UTC,I prefer the option to see the logs after installation.
1743615,2018-01-16 20:30:38 UTC,"I guess this is kind of poor experience. I don't think it's safe to say ""remove media now"" while subiquity is running as all the disk mounts are still set up at this stage. OTOH, if we skip straight to the casper ""remove medium and reboot"" screen, that might be a bit abrupt and doesn't give the user a chance to look at logs etc. Maybe that's OK though."
1743615,2018-07-22 23:09:46 UTC,Basically I don't think we can solve this entirely but perhaps we can think of a way to make it less jarring for the user.
1743621,2020-09-12 07:02:22 UTC,So older without more users with this issue
1743621,2018-01-17 19:50:15 UTC,"Dmitry, any idea?"
1743621,2018-01-17 20:59:16 UTC,I'm not sure if there may be any regression potential but bug 1295783 may be worth a look.
1743621,2018-01-19 10:50:39 UTC,"Alberts: the problem is that all settings-related categories in gnome-flashback-applications.menu exclude X-GNOME-Settings-Panel, which gufw.desktop has."
1743622,2020-02-24 20:48:40 UTC,Perhaps addressed by the Hatch Omnibus patch? https://bugs.launchpad.net/evergreen/+bug/1830391 or just a fluke on my part?
1743622,2018-06-26 21:01:22 UTC,Confirmed in Evergreen 3.0.8
1743622,2019-03-14 15:08:14 UTC,Confirmed in Evergreen 3.1.9
1743622,2019-10-31 18:44:42 UTC,Confirmed in 3.3.4
1743622,2019-10-31 20:26:01 UTC,"That seems to fix it, I edited core.bundle.js and found the correct ""o._remotePrint()"" and changed it to ""u._remotePrint()"" where I think u = service... so service._remotePrint() in print.js instead of egHatch._remotePrint()."
1743622,2020-01-30 15:32:45 UTC,"I agree, Josh.  These few lines in print.js do look pretty suspicious to me: https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/web/js/ui/default/staff/services/print.js#L186"
1743622,2020-02-24 20:45:32 UTC,"I was curious if anyone has simply tested ""Reprint Last Receipt"" on Evergreen 3.4 with Hatch enabled lately."
1743622,2020-02-27 20:34:52 UTC,"Odd. I get that same error on 3.2.8 but not on 3.4.2. I am also on Chrome, (forgot to mention that earlier)."
1743622,2020-02-27 19:41:13 UTC,I confirmed that Reprint Last Receipt still isn't working for us on 3.4.2 in Chrome. This is what I see in the browser console:
1743630,2018-01-21 21:53:52 UTC,Confirmed.  The only way to close it is by clicking the dropdown toggle button on the right side of the dropdown menu.
1743638,2018-02-27 23:00:07 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1743638,2018-02-23 14:38:54 UTC,"The verification of the Stable Release Update for debian-installer has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1743638,2018-02-21 17:23:51 UTC,Verified:
1743638,2018-05-14 08:31:33 UTC,This package has not yet been tested. Looks like there was some issue with the reviewing tool that caused the tags not being properly set - please test the artful upload of linux-firmware please.
1743638,2018-04-30 17:29:47 UTC,"Hello dann, or anyone else affected,"
1743638,2018-04-04 09:28:24 UTC,This bug was fixed in the package linux-hwe-edge - 4.15.0-13.14~16.04.1
1743638,2018-02-28 08:22:59 UTC,This bug was fixed in the package linux-firmware - 1.157.17
1743638,2018-02-14 09:37:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1743638,2018-02-14 09:42:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1743638,2018-02-14 19:12:18 UTC,artful/linux verification:
1743638,2018-02-17 17:39:55 UTC,"Hello dann, or anyone else affected,"
1743638,2018-02-19 15:39:05 UTC,This bug was fixed in the package linux-firmware - 1.171
1743638,2018-02-21 10:01:46 UTC,"Hello dann, or anyone else affected,"
1743638,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1743638,2018-02-21 18:58:26 UTC,This bug was fixed in the package linux - 4.4.0-116.140
1743638,2018-02-21 18:59:14 UTC,This bug was fixed in the package linux-hwe - 4.13.0-36.40~16.04.1
1743638,2018-02-22 15:48:03 UTC,This bug was fixed in the package linux - 4.15.0-10.11
1743638,2018-02-23 14:38:45 UTC,This bug was fixed in the package debian-installer - 20101020ubuntu451.22
1743638,2018-02-19 15:38:59 UTC,This bug was fixed in the package debian-installer - 20101020ubuntu530
1743646,2018-07-30 01:05:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586914"
1743652,2018-01-16 21:19:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/534441"
1743652,2018-01-24 19:41:20 UTC,"Thanks for linking this to https://bugs.launchpad.net/nova/+bug/1733861 Julia. FYI, I've proposed a work around for this issue: https://review.openstack.org/#/c/537626/."
1743652,2018-01-25 03:54:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/537737"
1743652,2018-02-05 19:43:20 UTC,"Change abandoned by Julia Kreger (<email address hidden>) on branch: master
Review: https://review.openstack.org/537737"
1743652,2018-02-08 01:04:07 UTC,"Reviewed:  https://review.openstack.org/534441
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=4f79cb3932f2518ab3f06b86ceea065cbb399e8c
Submitter: Zuul
Branch:    master"
1743652,2018-02-08 14:15:59 UTC,This issue was fixed in the openstack/ironic 10.1.0 release.
1743652,2018-02-21 17:25:47 UTC,We are about to revert this fix due to regressions it causes :( See https://bugs.launchpad.net/ironic/+bug/1750785
1743656,2018-01-16 21:54:38 UTC,honestly we don't often update that code... https://review.openstack.org/#/c/532696
1743663,2018-01-16 23:30:28 UTC,The automated part of the report wasgenerated using the command ubuntu-bug rhythmbox
1743670,2018-02-01 12:48:49 UTC,Hi Harold Hiner
1743670,2018-02-01 14:42:36 UTC,I can confirm that this issue is seen in Fedora 27 with 3.17.11 hplip version.
1743674,2018-02-12 22:16:50 UTC,This is dependent on the generic BIOS interface work: https://bugs.launchpad.net/ironic/+bug/1712032.
1743674,2018-02-12 22:34:07 UTC,"On Feb 12, on irc, ET time: 17:29 TheJulia: w/r/t irmc bios configuration, I'm good with it as it implements what is in the bios spec (at least, that is the idea)."
1743674,2018-01-17 03:08:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534595"
1743680,2019-05-28 21:27:40 UTC,Tested the TinyMCE editor and did not ind any issues.
1743684,2020-06-08 08:16:38 UTC,If this is still a problem then please tell us what app or command you were using to copy. And how you can tell the files are different.
1743684,2020-08-08 04:17:22 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1743686,2018-01-17 18:28:35 UTC,Unless `computer://` uri is invalid these days this is bug in nautilus.
1743686,2018-01-19 13:32:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743686,2018-01-19 13:36:54 UTC,nautilus computer:// opens for me. But the file-system under it doesn't work.
1743686,2018-08-17 00:39:30 UTC,It seems to me that the most sensible approach would be to just remove the Computer button from the Places menu. Then you'd just open Home and select Other Locations. I think that would be more in keeping with the latest Nautilus redesign.
1743688,2018-02-08 20:26:11 UTC,This issue was fixed in the openstack/congress 7.0.0.0rc1 release candidate.
1743688,2018-03-19 08:09:24 UTC,"Patch for devstack has been abandoned, please update if there is still an issue with devstack."
1743688,2018-11-26 07:31:34 UTC,marked invalid for Tempest.
1743688,2018-11-26 07:32:29 UTC,For Devstack - We need to move the non tempest owned service availability setting on devtsack plugins side and remove those from devstack.
1743688,2018-11-26 07:57:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619973"
1743688,2018-11-26 08:38:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619984"
1743688,2018-11-26 09:04:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619985"
1743688,2018-11-27 08:24:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620255"
1743688,2019-09-25 08:45:59 UTC,This issue was fixed in the openstack/aodh 9.0.0.0rc1 release candidate.
1743688,2019-04-14 22:08:34 UTC,"Reviewed:  https://review.openstack.org/620002
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=0e40e57c1ab2e8468016d4d877a91ce3a06df40a
Submitter: Zuul
Branch:    master"
1743688,2018-11-29 00:06:23 UTC,"Reviewed:  https://review.openstack.org/620255
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=6611df0e2da0abc96979c52da0013535abf79428
Submitter: Zuul
Branch:    master"
1743688,2018-12-04 11:50:35 UTC,"Reviewed:  https://review.openstack.org/619984
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=d5d9342beeff5c8ac655073b8986feb6b91a9f25
Submitter: Zuul
Branch:    master"
1743688,2019-02-26 11:37:46 UTC,Octavia and other tempest plugins are also facing same issue bug#1817154.
1743688,2019-02-26 11:47:11 UTC,Note: we are facing these issue because service_available config option is registered by tempest plugin repo which is separate repo from service. So registration of config option and setting value is happening via separate repo.
1743688,2020-01-20 13:45:14 UTC,"Reviewed:  https://review.opendev.org/619973
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=f0dd9996cc635709276f51e4d94c5ebbf5d5b49f
Submitter: Zuul
Branch:    master"
1743688,2018-11-26 10:22:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620002"
1743688,2018-02-05 12:36:12 UTC,"Reviewed:  https://review.openstack.org/533133
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=aa779c5bd46649d9b672e1112c9e65ec857cde66
Submitter: Zuul
Branch:    master"
1743688,2018-01-30 08:26:42 UTC,"Change abandoned by Ghanshyam Mann (<email address hidden>) on branch: master
Review: https://review.openstack.org/536723
Reason: doing it on plugin side."
1743688,2018-02-01 09:12:26 UTC,"As per comment above, not a Tempest bug. Marking as ""incomplete"" on Tempest"
1743688,2020-02-10 04:33:48 UTC,"Reviewed:  https://review.opendev.org/620000
Committed: https://git.openstack.org/cgit/openstack/panko/commit/?id=a725f644120f94f03c575915c70e0f44c7114687
Submitter: Zuul
Branch:    master"
1743688,2018-01-17 05:28:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534624"
1743688,2018-01-17 11:14:15 UTC,"Yea, this is issue at least for congress plugin tests. let me describe from where issue started and what can be potential fix:"
1743688,2018-01-17 11:44:35 UTC,thanks for adding discussion.
1743688,2018-01-23 08:52:05 UTC,In Devstack TEMPEST_SERVICES had been made local variable (https://review.openstack.org/#/c/281788) to move all tempest supported services in devstack setting only.  - I9c24705e494689f09a885eb0a640efd50db33fcf
1743688,2018-01-23 09:11:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536723"
1743688,2018-01-23 09:14:22 UTC,"Seems like devstack patch would not be enough as aodh tempest plugin register aodh as ""aodh_plugin"" in service_available which is being used same way in congress tempest plugin."
1743688,2018-02-02 02:21:16 UTC,"Reviewed:  https://review.openstack.org/536753
Committed: https://git.openstack.org/cgit/openstack/congress-tempest-plugin/commit/?id=e58b0eb52d6c3794820e33e60bd208328c3a1380
Submitter: Zuul
Branch:    master"
1743688,2018-01-23 09:34:48 UTC,"Change abandoned by Anusha Ramineni (<email address hidden>) on branch: master
Review: https://review.openstack.org/534624"
1743688,2018-01-23 10:11:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/536745"
1743688,2018-01-23 10:26:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/536753"
1743688,2018-01-23 10:29:25 UTC,"Change abandoned by Ghanshyam Mann (<email address hidden>) on branch: master
Review: https://review.openstack.org/536745
Reason: not needed as fixed in https://review.openstack.org/#/c/536753/"
1743688,2018-01-23 13:49:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/536830"
1743688,2018-01-25 10:45:23 UTC,"Reviewed:  https://review.openstack.org/536830
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=b3539b9fd58b4dd34759bc913e50d95561e451e4
Submitter: Zuul
Branch:    master"
1743688,2018-01-27 14:16:03 UTC,"Reviewed:  https://review.openstack.org/536741
Committed: https://git.openstack.org/cgit/openstack/telemetry-tempest-plugin/commit/?id=8bccc06c2bc71798f532f4ba6bc873c5e5dbb896
Submitter: Zuul
Branch:    master"
1743688,2018-02-01 08:08:08 UTC,"As per discussion on IRC and review, below is the agreed plan"
1743688,2018-01-23 10:00:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536741"
1743688,2019-03-22 01:09:46 UTC,This issue was fixed in the openstack/congress 9.0.0.0rc1 release candidate.
1743688,2019-03-22 16:25:58 UTC,This issue was fixed in the openstack/trove 11.0.0.0rc1 release candidate.
1743699,2020-07-07 19:27:49 UTC,"Hello Hai,
I see there was some change here. Can someone put this in perspective ? i.e. what does:
tags: 	removed: wishlist
mean...?"
1743699,2020-07-18 17:20:44 UTC,"The ""wishlist"" tag was only removed because it is redundant with the Wishlist ""Importance"" state. That doesn't mean we don't want this! We definitely still do. Work is in progress here:"
1743699,2018-04-13 12:58:25 UTC,Related to: https://bugs.launchpad.net/mixxx/+bug/991717/comments/8
1743699,2020-07-19 10:09:14 UTC,Thanks for the reply!
1743699,2020-07-19 12:50:42 UTC,"Multi-value properties are not yet supported by Mixxx, neither internally nor for file tags. The special case handling for genres is a temporary workaround."
1743699,2020-07-19 13:04:25 UTC,"The approach in https://github.com/mixxxdj/mixxx/pull/2656 is to use a custom JSON format to serialize/deserialize arbitrary, user-defined faceted tags. This is much more flexible than the limitations of standardized tags such as genre."
1743699,2020-07-19 13:09:59 UTC,"Again, thanks for the input.
From a subjective point - I would only/mostly be interested in reading, not writing, but not sure that is something that works for others...
So I get your point needing to support all formats & i/o ops."
1743699,2020-07-19 13:18:06 UTC,"Re Be ""use a custom JSON format to serialize/deserialize arbitrary, user-defined faceted tags. This is much more flexible than the limitations of standardized tags such as genre.""
All for flexibility - if it allows data serialization from, as well as back into standard & custom tags (across a variety of formats) as well.
i.e. not the Pioneer route of database tags that lock users in, and can not be stored within files, in order to stay as software agnostic as possible...
c."
1743703,2020-07-01 21:07:46 UTC,"Thank you for your bug report, that sounds like https://gitlab.gnome.org/GNOME/evince/-/issues/862"
1743731,2018-01-18 06:00:48 UTC,Swift can happily handle any utf-8 & url encoded path for an object name
1743731,2018-01-18 06:06:21 UTC,"ok, so it doesn't upload anything at all"
1743731,2018-01-18 06:08:47 UTC,end of the last comment seems truncated:
1743731,2018-01-18 06:18:47 UTC,"FWIW, I expect openstackclient just needs something like https://github.com/openstack/python-swiftclient/blob/3.4.0/swiftclient/client.py#L206-L213"
1743733,2018-01-28 04:30:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743736,2019-03-14 10:00:15 UTC,"The same for me: this worked before in Ubuntu GNOME 16.04, and for me bug appeared in Ubuntu 18.04. The extension mentioned by @david23 works for me as a workaround."
1743736,2018-12-27 22:47:23 UTC,I have the same problem. Fresh install Ubuntu 18.04.
1743736,2018-11-20 16:03:19 UTC,"Same problem here.
Ubuntu 18.04
Nvidia proprietary drivers v415
LightDM (because gdm3 failing to handle multiple monitors in my laptop)"
1743736,2018-11-14 09:48:48 UTC,"Confirm, it also affects me in my two display desktop environment.  Will it be fixed ?"
1743736,2018-07-24 09:48:32 UTC,"@David: thanks for the link to the extension you saved my life :) works like a charm! sry, for noobing around, found the ""affect me"" button now. thanks & best regards!"
1743736,2018-11-07 23:17:36 UTC,"This bug still exists! Using the plugin circumvents the issue though.
I am on Ubuntu 18.10 btw."
1743736,2018-06-14 10:18:34 UTC,"I can confirm it as well. Occurred after upgrade to 18.04 (X and Wayland), worked fine with 16.04 (on Gnome). Unfortunately this is a core feature to my workflow, is there a workaround?"
1743736,2018-05-24 06:45:15 UTC,"I can confirm the bug. However, the bug reported on gnome's bugzilla is very old. I've been using ubuntu gnome 16.04 for the last two years and everything worked fine. I've seen this bug for the first time trying out ubuntu 17.10, so I would conclude it's either related to ubuntu's customization of gnome, or to gnome versions >3.18"
1743736,2018-01-18 09:37:16 UTC,It seems this one is reporting the issue: https://bugzilla.gnome.org/show_bug.cgi?id=652580
1743736,2018-01-18 02:10:45 UTC,Thanks for the bug report. I've not seen this problem reported before so please look at the upstream bug list to see if you can find it there:
1743736,2018-07-23 09:25:13 UTC,"@Alexander: as a first step, you may click on ""this bug affects me"" so that it gains visibility."
1743739,2018-06-04 19:21:02 UTC,"If this is reproducible and if your machine allows and if this still happens in 3.28, could you provide valgrind logs? Something like:"
1743739,2018-06-21 11:37:08 UTC,"Hi, I have not hit this agaoin on Ubuntu 18.04; perhaps it has been fixed. I will let you know if I notice this on any of my current installations."
1743742,2020-07-29 11:14:57 UTC,"Moving to Confirmed as the cidr is hardcoded in the code which is not ideal. There is a partial fix for the issue, mentioned above, however it's incomplete - although it removed the hardcoded values, it changed the nature of the tests (see the comments in the review) which is not a wanted outcome. I'll move this to Confirmed until someone picks this up."
1743742,2018-01-17 10:51:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/534721"
1743742,2020-06-09 14:47:44 UTC,Moving back to new due to a long inactivity. We should discuss what we wanna do with this.
1743746,2018-01-19 18:12:53 UTC,Thanks!
1743746,2018-02-02 14:29:17 UTC,Appreciate the kernel team has been pretty busy the last few months; is there an ETA on when this fix might make it into the 4.13 kernels?  I know we've pushed the HWE kernel version forward for xenial - so any OpenStack deployments using HWE with GRE tunnels will hit this problem.
1743746,2018-01-19 15:55:24 UTC,"Submitted Artful and Bionic SRU requests:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089420.html"
1743746,2018-02-14 09:38:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1743746,2018-01-18 08:02:37 UTC,Hi Joseph
1743746,2018-01-17 18:14:45 UTC,"I built a test kernel with commit cfddd4c.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1743746"
1743746,2018-01-17 12:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743746,2018-01-18 16:08:10 UTC,"Thanks for testing, James.  I'll submit an SRU request for this commit to be included in the Ubuntu kernel."
1743746,2018-02-14 11:24:23 UTC,LGTM to artful-proposed:
1743746,2018-02-15 15:13:46 UTC,"disregard that last comment, it was caused by a buggy script"
1743746,2018-02-15 15:12:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1743746,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1743747,2019-09-16 14:02:53 UTC,Migrated to https://github.com/widelands/widelands/issues/2097
1743754,2018-01-24 18:49:34 UTC,This issue was fixed in the openstack/tripleo-heat-templates 7.0.8 release.
1743754,2018-01-23 03:37:49 UTC,"Reviewed:  https://review.openstack.org/536547
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ebf01289ce7b311ae6b18eb7c3bb11d46f7cc4b4
Submitter: Zuul
Branch:    stable/pike"
1743754,2018-01-22 20:04:39 UTC,The backport of Icf4a64ed76635e39bbb34c3a088c55e1f14fddca had an indentation error which caused the command to be ['/docker_puppet_apply.sh'] instead of '/docker_puppet_apply.sh'
1743754,2018-01-22 20:02:35 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/536547"
1743754,2018-01-22 18:47:02 UTC,Visible: here : http://logs.openstack.org/91/535291/2/check-tripleo/tripleo-ci-centos-7-ovb-containers-oooq/83e97f2/logs/overcloud-controller-0/var/log/journal.txt.gz#_Jan_22_16_55_14
1743754,2018-01-19 09:11:00 UTC,"IIUC, it should be fixed now?"
1743754,2018-01-19 14:23:54 UTC,"As I can see, Featureset022 is still failing for the merged backport, so that was prolly not a (full) fix."
1743754,2018-01-18 13:31:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/535326"
1743754,2018-01-18 13:29:32 UTC,A backport of https://review.openstack.org/#/c/522405/2/common/deploy-steps-tasks.yaml is missing
1743754,2018-01-18 08:51:36 UTC,"From https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset022-pike/9ecbf75/undercloud/home/jenkins/failed_deployments.log.txt.gz we get:
[localhost]: FAILED! => {\n    \""(outputs.stderr|default('')).split('\\n')|union(outputs.stdout_lines|default([]))\"": [\n        \""stdout: afa20bff30e1663b155ee691722de43051c4cf0d37fc697601ef7cf577487535\"", \n        \""\"", \n        \""stderr: \"", \n        \""stdout: 4de8c7231a0f500fb3ef74b5f539ba2b3db160115d13264df65a241137566622\"", \n        \""stdout: \"", \n        \""sequence item 33: expected string, list found\"", \n        \""Traceback (most recent call last):\"", \n        \""  File \\\""/usr/lib/python2.7/site-packages/cliff/app.py\\\"", line 400, in run_subcommand\"", \n        \""    result = cmd.run(parsed_args)\"", \n        \""  File \\\""/usr/lib/python2.7/site-packages/cliff/command.py\\\"", line 137, in run\"", \n        \""    return_code = self.take_action(parsed_args) or 0\"", \n        \""  File \\\""/usr/lib/python2.7/site-packages/paunch/cmd.py\\\"", line 75, in take_action\"", \n        \""    labels=labels\"", \n        \""  File \\\""/usr/lib/python2.7/site-packages/paunch/__init__.py\\\"", line 54, in apply\"", \n        \""    return builder.apply()\"", \n        \""  File \\\""/usr/lib/python2.7/site-packages/paunch/builder/compose1.py\\\"", line 66, in apply\"", \n        \""    (cmd_stdout, cmd_stderr, returncode) = self.runner.execute(cmd)\"", \n        \""  File \\\""/usr/lib/python2.7/site-packages/paunch/runner.py\\\"", line 33, in execute\"", \n        \""    LOG.debug('$ %s' % ' '.join(cmd))\"", \n        \""TypeError: sequence item 33: expected string, list found\"", \n        \""  File \\\""/usr/bin/paunch\\\"", line 10, in <module>\"", \n        \""    sys.exit(main())\"", \n        \""  File \\\""/usr/lib/python2.7/site-packages/paunch/main.py\\\"", line 39, in main\"", \n        \""    return myapp.run(argv)\"", \n        \""  File \\\""/usr/lib/python2.7/site-packages/cliff/app.py\\\"", line 279, in run\"", \n        \""    result = self.run_subcommand(remainder)\""\n    ], \n    \""failed_when_result\"": true\n}\n\tto retry, use: --limit @/var/lib/heat-config/heat-config-ansible/caf3f47b-95fa-43e7-89da-89b80047ee1e_playbook.retry\"
1743754,2018-01-17 16:19:31 UTC,"Overcloud hosts are not accessible by SSH, we can't fetch logs from there: https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset022-pike/9ecbf75/quickstart_collect_logs.txt.gz"
1743754,2018-01-17 16:14:50 UTC,how can we debug this one if we don't have overcloud logs?
1743754,2018-01-18 19:52:39 UTC,"Reviewed:  https://review.openstack.org/535326
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=56448dafeda8db1916b2a65fd19bd70c7e6ff176
Submitter: Zuul
Branch:    stable/pike"
1743755,2019-09-17 10:15:38 UTC,Migrated to https://github.com/widelands/widelands/issues/2098
1743757,2019-09-17 07:12:01 UTC,Migrated to https://github.com/widelands/widelands/issues/3250
1743761,2018-01-17 13:12:45 UTC,segue video do erro ocorrendo mesmo apos a atualização existe outra e o problema persiste
1743761,2018-01-18 17:53:27 UTC,resolvi o problema instalando o lubuntu mas a maquina anteriormente possuia o ubuntu 16.04 lts com unity (acho ser alguma incompatibilidade com video intel)
1743761,2018-01-17 12:40:41 UTC,segue imagem apos a atualização e erro apresentado
1743761,2018-01-17 12:14:34 UTC,segue imagem
1743761,2018-01-17 12:26:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1743762,2018-01-17 20:39:39 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1743762,2018-01-17 23:08:42 UTC,Here's a debdiff for Xenial.  It is my understanding that Trusty can get a fakesync from Jessie.
1743762,2018-01-18 00:10:29 UTC,Debian is working on patches for all of its stable repositories. See https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2018-January/thread.html for details.
1743762,2018-01-18 00:23:12 UTC,"The attachment ""CVE-2018-0486.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1743762,2018-01-18 00:40:44 UTC,This bug was fixed in the package xmltooling - 1.5.3-2+deb8u2build0.14.04.1
1743762,2018-01-18 00:40:45 UTC,This bug was fixed in the package xmltooling - 1.5.6-2ubuntu0.1
1743762,2018-02-05 19:48:49 UTC,I am unsubscribing ubuntu-security-sponsors for now since there is no artful debdiff to review. Please subscribe ubuntu-security-sponsors again once an appropriate debdiff is available. Thanks!
1743765,2018-02-18 12:01:05 UTC,This is probably related to #1747966
1743765,2018-01-17 14:51:17 UTC,"New toolchains can reveal old bugs.
Start by generating and comparing .map files for the builds."
1743765,2018-01-19 07:19:47 UTC,Sounds like you found a bug in a GitHub project and you are using the wrong bug tracker to report it.
1743765,2018-01-19 08:04:21 UTC,"Why would this be a bug in the project and not GCC? Earlier versions of GCC work fine, Keil works fine, I haven't tried IAR but they have a project for that too so I assume it also works fine, the only one with a problem and a 9KB smaller filesize is GCC 7 so I'm more inclined to believe it's a problem with GCC unless shown otherwise."
1743765,2018-01-19 08:21:05 UTC,"It could be a GCC bug, of course. But don't expect GCC people to start looking for it in the files that you posted. I've had my share of debugging GCC output with LTO enabled and high optimization level. I must say, it's not easy. Someone familiar with this GitHub code would be more appropriate for this kind of work. In the end, it could still end up being a bug in the code, not GCC. The fact that it works with other compilers doesn't prove anything."
1743765,2018-01-19 09:45:17 UTC,"Hi Jamie,"
1743765,2018-01-23 13:54:30 UTC,"Since the code works when LTO is disabled, the most likely cause is code or data that is not being linked because its use cannot be traced back to main().  In C, all code other than the library start up routines is expected to be called directly or indirectly from main().  LTO traces this to see what code is actually used, and to drop code and data that can't legally be accessed from C.  You might need to add ""externally_visible"" attributes to certain functions, or use ""keep"" in the linker file, in order to avoid dropping such code.  Likely candidates include interrupt functions, ""naked"" functions, and parts of context switch routines in an RTOS."
1743766,2018-01-17 22:14:56 UTC,Can you see if the 3.13.0-136 kernel has this bug as well?  It is pre pti patches and can be downloaded from:
1743766,2018-01-19 14:43:02 UTC,"So test results:
3.13.0-136 kernel has same bug.
Tried 4.4.0-109 kernel and it works fine without bugs."
1743766,2018-01-17 16:21:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1743766,2018-01-17 18:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743766,2018-01-18 14:46:04 UTC,Due to company security policy we can`t send report via apport-collect.
1743768,2018-01-18 17:10:31 UTC,(Forgot to say: Thank you for coming over and helping us out here!)
1743768,2018-01-18 17:09:45 UTC,"Lazur, I'm having a hard time imagining this all without pictures. For the effect you describe in the first paragraph of comment #5 - would it look 'realistic' in that use case, for an object like a flat ring?"
1743768,2018-01-18 15:30:43 UTC,"From the ""inner"" shadow I'd expect an effect simulating that the filtered object was carved or pressed below the screen surface and the shadows wouldn't go over its boundaries however I'm not sure about the original intention.
For that purpose it doesn't work either."
1743768,2018-01-18 15:01:52 UTC,Thanks for investigating this!
1743768,2018-01-18 13:06:54 UTC,"Hi. Not sure what should be expected from the ""drop shadow..."" filter. They generate a straightforward filter chain in the filter editor. Only thing that's odd about it is the panel claiming a px blur value while it uses a gaussian blur filter primitive which is percentage based."
1743768,2018-01-18 10:25:31 UTC,"Thanks!
It even affects the ""outer"" options (to a lesser extent). As in that case a shadow is always rendered it's harder to spot, though."
1743768,2018-01-18 03:29:08 UTC,"I've asked Lazur to take a look, maybe he can even find a solution that makes the filter behave more like you expected it to work. Btw. this also affects the other 'inner' filter."
1743768,2018-01-18 21:21:38 UTC,"Made a simple screen capture playing with the dropshadow filter:
https://youtu.be/17uQOd-TOrc"
1743768,2018-03-04 22:28:23 UTC,"Lazur, that video is 22 minutes long - is there a specific part of it that helps with this bug report, or were you really just playing around?"
1743772,2018-01-18 11:49:10 UTC,It seems that this happens when there is a version mismatch between sdk and client. Upgrading python-openstackclient to 3.13.0 solves the issue for me.
1743774,2018-05-08 22:32:10 UTC,"This bug also mention on KDE bugs:
https://bugs.kde.org/show_bug.cgi?id=375467
You can subscribe on it and, if this bug will be fixed, you take notification (but also notification for new comments)"
1743774,2019-09-10 01:54:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743779,2020-02-26 22:39:58 UTC,Marking as Won't Fix for 2.3 series since we are not planning to make any further releases in this series at this stage.
1743779,2018-05-08 13:47:46 UTC,"removing the milestone as nobody seems interested enough in having 2.3 work with LE, and are happy to have it be 2.4"
1743779,2018-03-26 04:33:31 UTC,Not sure if this is needed for 2.3 or whether fixing it in 2.4 was sufficient.
1743779,2018-03-26 04:30:17 UTC,Did we intend to backport this change to 2.3 series?
1743779,2018-03-26 04:29:33 UTC,https://github.com/juju/juju/pull/8427
1743779,2018-01-30 12:47:46 UTC,"Note, this doesn't actually affect JAAS as they aren't using Lets Encrypt based certificates anymore."
1743779,2018-01-30 12:47:03 UTC,"To support this, we would need to expose port 80 and have a mux that can respond to the http challenge that Lets Encrypt is now generating.
We would also need to expose port 80 for controller machines.
If we are going to do that, we should probably also give a redirect from http:80 to https:17070 for all other requests on port 80, which gives a nice user experience when they do have their own DNS names. Then it redirects them to the GUI on the right port."
1743784,2019-01-19 18:21:51 UTC,Confirmed in 3.1.2.
1743785,2018-01-17 13:58:27 UTC,"Addressed by:
https://code.launchpad.net/~benokolie/charm-openstack-service-checks/+git/charm-openstack-service-checks/+merge/335653"
1743791,2018-08-20 05:56:55 UTC,"Change abandoned by Hunt Xu (<email address hidden>) on branch: master
Review: https://review.openstack.org/535290"
1743791,2018-01-18 11:04:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535290"
1743791,2018-01-17 14:30:49 UTC,"There are two things to be fixed/added:
  - No notification is sent when router gateway port's IP address changes to another valid IP address in the same network, even to different subnet.
  - No validation is performed in VPNaaS extension for such a change."
1743796,2018-01-17 14:54:24 UTC,"....substitute ""check-in"" for ""check-out"" in the above. I have not had enough coffee."
1743796,2018-07-16 19:30:47 UTC,"Confirming as we have had multiple requests to have ""Retrieve Last Patron Who Circulated Item"" open in a new tab."
1743797,2018-01-18 07:49:03 UTC,putting 'radeon.modeset=0' to kernel options is what disables all hw acceleration
1743797,2018-02-14 00:15:23 UTC,"Sorry, can you be a bit more specific on how to get the update history? I tried a couple of commands but neither got me the package update history. Really, I know almost nothing about getting around Ubuntu."
1743797,2018-02-13 17:29:42 UTC,Greta Regan:
1743797,2018-02-13 13:22:36 UTC,"It happened after upgrading from 14.04 to 16.04. I did this when prompted by Software Updater, so presumably it was the first version of 16.04 released through Updater. It didn't happen right after, or soon after, that upgrade, and I don't think there were any updates to 16.04 in the days immediately before the problem started. - I can't swear to that, as, naturally, I wasn't paying that much attention to all the little updates one gets almost every day."
1743797,2018-02-10 12:19:45 UTC,I've attached the complete file of the boot recording.
1743797,2018-02-09 22:46:43 UTC,"I've attached a boot recording - all went smoothly this time. I trimmed it down to just the boot log itself. It may look like I cut off the start of the log, but I didn't. I have the complete file, though, if needed, including what happens after the boot (not much visibly). If it's not clear enough or you think I've missed something you need at the top or bottom of the screen, I can have another go."
1743797,2018-02-12 21:23:40 UTC,Great Regan:
1743797,2018-02-09 12:19:43 UTC,"I'm using a camera to record the video, that's not causing problems - aside from having to experiment a bit to get a clear shot of the log. The problems have been with the boots themselves. But, I'll do as you say. I'll try later today - when I can do without the laptop for awhile, as even after I reverse the changes to the grub it's taken some time to get it working properly (or at all) again."
1743797,2018-02-08 21:38:41 UTC,Greta Regan:
1743797,2018-02-08 21:00:25 UTC,"I've had trouble trying to capture a boot log with the settings requested in the last posting. Different things have happened on different attempts, including the boot stopping dead. I'll try for a couple of more days to see if I can get a complete log to post."
1743797,2018-02-06 20:22:00 UTC,"Greta Regan, in order to obtain necessary debugging logs, could you please remove your WORKAROUND and capture the logs following https://wiki.ubuntu.com/DebuggingKernelBoot ?"
1743797,2018-01-18 22:05:45 UTC,"I installed 'linux-generic-hwe-16.04', as suggested, but there's no change. Perhaps because the radeon.modeset=0 is still in my system - but I can't find where. My boot sequence no longer shows radeon.modeset=0, but it came up when I ran dmesg | egrep | 'drm|radeon'. I've included both outputs below."
1743797,2018-02-09 17:26:08 UTC,"Greta Regan, if reproducible in a live environment you could use instead http://cdimage.ubuntu.com/daily-live/current/ if this is more convenient, so you don't have to undo the WORKAROUND on your install."
1743798,2019-07-27 08:10:54 UTC,This exact same issue has happened to me as well. I attempted to run a livecd of Ubuntu 19.04 on a HP g72 notebook PC and came across this exact error.
1743798,2019-10-28 11:31:37 UTC,"I have the very same issue with a ThinkPad P53, two days old, and Ubuntu 19.10.
The kernel panic looks the same."
1743798,2019-10-28 11:31:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743799,2018-01-22 20:18:41 UTC,"This bug also affects hogplum, a Dell PowerEdge T610, running Ubuntu 14.04 with a 3.13.0-140 kernel. Here's the uname data from it:"
1743799,2018-01-23 17:41:02 UTC,A further update: This problem does NOT occur under Artful on the Dell PowerEdge T610 with the following kernel:
1743799,2018-01-17 20:13:16 UTC,"I was unable to reproduce this problem on the Dell T110; however, I did notice that it failed the test at the point where the T710 rebooted. (""Stress test for UEFI miscellaneous runtime service"")"
1743799,2018-01-17 18:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1743799,2018-01-17 19:44:15 UTC,"I've managed to isolate this to the fwts ""uefirtmisc"" test:"
1743799,2018-01-17 19:52:56 UTC,"I tried running apport-collect, as requested by the Ubuntu Kernel Bot, but it didn't work; it tried to open a (text-based) browser, but that hung on ""Opening socket...."", presumably because the system in question is behind strict firewalls in 1SS."
1743799,2018-01-17 17:04:25 UTC,"I've done more testing. The problem occurs beginning with the 3.13.0-139 kernel; the 3.13.0-138 kernel is unaffected. The 4.4.0-109 kernel also has the problem, but I've not tested others in this series. Links to relevant test results:"
1743803,2018-01-29 03:39:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743803,2018-03-27 02:12:20 UTC,I think I saw this was fixed in 18.04. Can anyone else verify?
1743803,2018-03-27 02:15:52 UTC,"Yes, now fixed in 18.04."
1743803,2018-03-27 19:27:53 UTC,I can still reproduce this bug. You have to switch between windows to see it. See the attached screencast.
1743803,2018-03-27 19:43:55 UTC,"Yes, window must be out of focus to reproduce."
1743803,2018-03-27 19:44:37 UTC,"Yes, window must be out of focus to reproduce."
1743812,2018-07-24 09:31:49 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1743812,2018-01-17 16:30:08 UTC,This change was made by a bot.
1743812,2018-01-17 17:14:23 UTC,"We still wait for the compiler fixes
https://www.phoronix.com/scan.php?page=news_item&px=GCC-7.3-Release-Imminent"
1743812,2018-02-15 17:07:53 UTC,"Hello,"
1743812,2018-03-01 11:13:51 UTC,Virtualbox is tracked in bug 1736116
1743828,2018-01-17 17:29:00 UTC,"root@raminfp:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.10
DISTRIB_CODENAME=artful
DISTRIB_DESCRIPTION=""Ubuntu 17.10"""
1743845,2018-01-22 17:42:27 UTC,"Reviewed:  https://review.openstack.org/534858
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=a531eec15cc1a7208aad86b7496886879d5ef141
Submitter: Zuul
Branch:    master"
1743847,2018-01-27 16:59:17 UTC,"Change abandoned by Edward Hope-Morley (<email address hidden>) on branch: master
Review: https://review.openstack.org/535248
Reason: no longer required since c-h already synced (commit e99e430)"
1743847,2018-01-17 18:00:31 UTC,This line specifically is what is breaking things - https://github.com/juju/charm-helpers/commit/1cca8e4fe357b17f7685704e9fbde4415c4f60a0#diff-935a00f40074c3c59d617c88f71e42efR489
1743847,2018-01-17 18:16:39 UTC,https://github.com/juju/charm-helpers/pull/93
1743847,2018-01-18 09:39:57 UTC,Patch: https://review.openstack.org/535248/
1743848,2018-01-17 18:13:24 UTC,from /var/crash/
1743848,2018-01-17 18:13:52 UTC,from /var/crash/
1743848,2018-01-17 18:15:08 UTC,just in case... :)
1743848,2018-01-22 15:51:42 UTC,An updade on kernel versions.
1743848,2020-01-06 10:59:46 UTC,"Hello,
4.13.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1743848,2018-01-29 12:36:35 UTC,I was advised to rephrase the description of the bug.
1743850,2020-07-10 04:17:17 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1743850,2018-01-17 19:41:32 UTC,We did not change anything according to broadcasting during the beta.
1743850,2018-01-17 19:56:26 UTC,Here's my log file
1743850,2018-01-17 20:00:48 UTC,Here is my settings for one encoder.
1743850,2018-01-17 20:02:16 UTC,Here's the other encoder
1743850,2018-01-17 23:39:05 UTC,"Warning [ShoutOutput 'The Bluegrass Jamboree New']: Streaming server made error: -3
Warning [ShoutOutput 'The Bluegrass Jamboree New']: ShoutConnection - processConnect() error: -3 ""No error""
Debug [ShoutOutput 'The Bluegrass Jamboree New']: Unloaded libmp3lame
Debug [ShoutOutput 'The Bluegrass Jamboree New']: ShoutConnection - processConnect() returning false
Warning [ShoutOutput 'The Bluegrass Jamboree New']: Streaming error:  ""No error
Please check your connection to the Internet and verify that your username and password are correct."""
1743850,2020-05-10 09:31:48 UTC,Can you still reproduce the issue with Mixxx 2.2?
1743855,2018-01-23 12:07:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743859,2018-01-17 22:06:03 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1743859,2018-01-17 19:30:06 UTC,This change was made by a bot.
1743865,2018-04-04 16:25:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743865,2018-04-16 12:25:34 UTC,Confirmed on Artful. This does not reproduce on Bionic with the new mongodb/mongo-tools 3.6. So I presume this is fixed on Bionic.
1743866,2020-04-12 04:17:27 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1743866,2018-01-25 07:19:43 UTC,I still can NOT confirm any cover loss! Nevertheless by analyzing the code I've done some minor improvements and optimizations:
1743866,2018-01-23 16:47:34 UTC,"I am trying to re-analyze my songs, as told in forum.
When i dropped about 200-300 songs, there now after analysis many, plenty of songs
which cover art column is now empty."
1743866,2018-01-22 21:03:18 UTC,i am talking track(library) window column covert art. not talking files.
1743866,2018-01-18 14:02:39 UTC,"These files have been in library, and i reset grid bmp info. and re analyzed."
1743866,2018-01-18 14:01:56 UTC,"Mixxx dont remove cover art from file, it just show an empty column in track (library) window.
and it didnt reloaded if try to use load metadata from file ""command"".
cant remember how i managed get it back."
1743866,2018-01-18 06:35:36 UTC,What type of file is affected?
1743866,2018-01-18 06:29:00 UTC,Have you assigned a custom cover before? Does the file have embedded cover art?
1743866,2018-01-18 19:22:12 UTC,"Mixxx won't touch the embedded cover art, even if you enable metadata export."
1743875,2018-01-17 22:54:21 UTC,"There were a number of changes during the .91-.92 transition made to respect more closely the CSS changes, but it would seem that in some cases IE and Edge are not compliant :/"
1743884,2018-03-01 10:03:12 UTC,"The verification of the Stable Release Update for grub2 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1743884,2018-03-01 10:03:13 UTC,This bug was fixed in the package grub2 - 2.02~beta3-4ubuntu7.2
1743884,2018-02-15 21:20:45 UTC,"Verified by:
  - MAAS installing a Cavium ThunderX2 Sabre
  - Removing /etc/default/grub.d/50-curtin-settings.cfg (which forces on console mode)
  - Commenting out the HIDDEN settings from /etc/default/grub
  - sudo dpkg-reconfigure grub-arm64-efi (enable NVRAM variables - MAAS disables this)
  - reboot - verify that the GRUB menu does *not* appear
  - upgrade to -proposed GRUB packages
  - verify that GRUB menu *does* appear now"
1743884,2018-03-05 09:28:48 UTC,"The released fix for this introduced a regression (LP: #1752767), so I'm reverting while we seek a better fix."
1743884,2018-02-15 10:24:01 UTC,"Hello dann, or anyone else affected,"
1743884,2018-02-06 17:53:17 UTC,This bug was fixed in the package grub2 - 2.02-2ubuntu6
1743884,2018-01-18 20:27:38 UTC,"Posted a patch upstream for feedback:
  http://lists.gnu.org/archive/html/grub-devel/2018-01/msg00010.html"
1743884,2018-01-17 21:41:53 UTC,I've found that the offending line in /boot/grub/grub.cfg is:
1743884,2018-02-15 10:32:47 UTC,"Hello dann, or anyone else affected,"
1743886,2018-01-17 21:41:40 UTC,"To clarify: this is a bug in urllib3 as bundled in python-pip, that shows up only when PyPI is unavailable.  Pybuild sets https_proxy=https://127.0.0.1:9/ to forcefully make PyPI unavailable during the package build."
1743886,2018-05-24 00:11:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743886,2018-05-27 14:46:52 UTC,This also effects ubuntu 16.04
1743886,2019-07-25 10:06:14 UTC,4 floor ++
1743888,2018-09-26 20:17:11 UTC,I have a feeling this may be fixed as of 3.0.12. See related bug: https://bugs.launchpad.net/evergreen/+bug/1776917
1743888,2018-06-19 21:26:12 UTC,"I've confirmed this bug because I can duplicate this in 3.0.8. However it doesn't happen every time, and I think the bug is actually something else."
1743888,2018-05-24 19:00:35 UTC,Just tested this on a current master sandbox and I am able to apply multiple payments without refreshing.
1743888,2018-07-16 19:34:31 UTC,See https://bugs.launchpad.net/evergreen/+bug/1780283 for more on workflow described in my previous comment.
1743913,2018-01-18 18:43:45 UTC,"Yes, the symptoms are similar (two of those even were reported by me). Thanks for researching, Eduard!"
1743913,2018-01-18 10:21:48 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)
confirmed on Windows 10, Inkscape 0.92+devel (0beb22f, 2017-12-29)"
1743913,2018-01-18 16:59:40 UTC,"Thanks for testing, Alvin!"
1743913,2018-01-18 02:16:59 UTC,Additional: seems this path has been created with the measure tool. The user describes it like this:
1743913,2018-01-18 17:53:13 UTC,"It seems we have a lot of very similar issues:
- bug #1475875
- bug #1565174
- bug #1653694
- bug #1687514
- bug #1726431"
1743920,2018-01-18 09:54:48 UTC,"I'm not 100% sure about the analysis provided in the bug report, I think this other patch [1] may be the cause or at least related, but without complete logs of the attach operation in Nova is difficult to be sure."
1743920,2018-01-19 01:23:11 UTC,"Here is a full log for this, FYI: http://publiclogs.emc.com/534075/2/Dell_PS_iSCSI/1039/"
1743920,2018-01-19 11:17:33 UTC,"I've found a solution for this issue on Dell PS:
1. create a 'gate keeper' volume on Dell PS array.
2. map the volume to server.
3. create a FS on the volume.
4. mount the FS"
1743924,2018-01-18 11:54:04 UTC,"I've just downloaded both Peppermint 8 Respin ISO's (32bit and 64bit) from our website and checked both the SHA256 checksums and he GPG signatures against the masters we hold, and both ISO's checked out as being the originals digitally signed by me. I can only assume it's something on your system. Is your system UEFI and have you ever had Elementary installed ?"
1743924,2018-01-18 15:04:26 UTC,Hi Mark.
1743936,2018-05-08 22:20:03 UTC,"The verification of the Stable Release Update for distro-info-data has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1743936,2018-05-08 22:19:56 UTC,This bug was fixed in the package distro-info-data - 0.18ubuntu0.9
1743936,2018-01-18 04:20:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1743936,2018-01-19 20:29:33 UTC,Is this negatively impacting something or could we just wait a week for distro-info-data to be correct?
1743936,2018-01-18 18:00:38 UTC,"More info that the 13th was the right date.
 https://lists.ubuntu.com/archives/ubuntu-announce/2018-January/000227.html"
1743936,2018-01-18 17:26:09 UTC,from the dupe i just filed.
1743936,2018-01-22 21:23:11 UTC,It would be worthwhile to fix this in Debian and Bionic though.
1743951,2018-01-25 14:49:28 UTC,"Note, that ""description-file"" differs from ""long_description"" in that ""description-file"" is name of a file to read the description from in contrast to content itself in ""long_description""."
1743952,2018-01-18 18:18:33 UTC,"Could it be you have keyboard shortcuts enabled and accidently activated 'mute' for a deck or for Master, or vinyl  passthrough or alike?"
1743952,2018-01-18 20:20:28 UTC,Nah I have nothing like that setup. I'm completely new to Mixxx and have talked to others who have been using it for a while. They've had no issues and just used the straight download. I'm not using any external interfaces either. Because like I said......the deck just kills it's self after about 5 minutes of use. Won't load anything
1743952,2018-01-18 21:48:49 UTC,"Which version of Mixxx are you using on which OS?
By luck this issue is solved in the recent 2.1 beta."
1743952,2018-01-18 22:27:05 UTC,"Windows 10
and the latest released version 2.0. I just can't figure out why it's doing this.....lol"
1743952,2020-02-29 04:17:18 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1743956,2018-01-22 06:23:23 UTC,apport information
1743956,2018-01-22 06:23:25 UTC,apport information
1743956,2018-01-22 06:23:26 UTC,apport information
1743956,2018-01-22 06:23:29 UTC,apport information
1743956,2018-01-22 06:23:37 UTC,apport information
1743956,2018-01-22 06:23:32 UTC,apport information
1743956,2018-01-22 06:23:33 UTC,apport information
1743956,2018-01-22 06:23:36 UTC,apport information
1743956,2018-01-22 06:23:21 UTC,apport information
1743956,2018-01-22 06:25:24 UTC,"Hi Khurshid,
Done for using `apport-collect 1743956`, please check. Thanks."
1743956,2018-01-22 06:23:30 UTC,apport information
1743956,2018-01-22 06:23:20 UTC,apport information
1743956,2018-01-22 06:23:12 UTC,apport information
1743956,2018-01-22 06:23:16 UTC,apport information
1743956,2018-01-22 06:23:15 UTC,apport information
1743956,2018-01-22 06:23:10 UTC,apport information
1743956,2018-01-22 06:23:08 UTC,apport information
1743956,2018-01-22 06:23:07 UTC,apport information
1743956,2018-01-22 06:23:05 UTC,apport information
1743956,2018-01-22 06:23:01 UTC,apport information
1743956,2018-01-22 06:22:59 UTC,apport information
1743956,2018-01-22 06:22:57 UTC,apport information
1743956,2018-01-19 13:39:13 UTC,I can't reproduce it. This seems to be a problem with your graphics. Use `apport-collect 1743956` for more information.
1743956,2018-01-18 10:26:30 UTC,"Ubuntu 16.04, please save as link for mp4 video file. I'm not sure why I cannot play on the web view, thanks."
1743956,2018-01-18 07:29:42 UTC,Which Ubuntu version? And your mp4 file is playable.
1743956,2018-01-22 06:23:18 UTC,apport information
1743959,2020-03-25 09:56:28 UTC,Then，what is the future plan? Senlin and placement default port is still 8778
1743959,2018-01-29 02:29:19 UTC,No. I was trying to give you a brief background on this. We haven't got cycles to (re-)solve it so far. The plan is to debug senlin service so that it doesn't rely on a particular port. By that I mean enabling users to access senlin service at a url like this:
1743959,2018-01-26 01:38:28 UTC,"Unfortunately, yes. This issue has been identified last year and the solution was to have every service deployed using service path on a single port on the web server. However, later on, RDO insists it will continue to use port based service deployment and they want nova placement API to use 8778 port..."
1743959,2018-01-26 01:50:05 UTC,"So what is the plan for Senlin API port?  Your response is ambiguous in that you acknowledge the issue and also make no commitment to address it.  Should I read your response as ""won't fix""?"
1743972,2018-01-18 06:54:32 UTC,"There are not 23 machines, but `juju controllers` says that there are:"
1743972,2018-01-31 01:39:41 UTC,"--refresh is necessary as we, by default, do not go back to the server for this information. We actually cache it on the client side for a quick response. --refresh option essentially tells to go to the server (controller) to get this information."
1743972,2018-01-18 07:03:48 UTC,Using --refresh solved it.  But why is this necessary?
1743973,2018-01-18 12:47:52 UTC,"Sorry, can you clarify what the error is you are seeing. I'm not sure I'm following."
1743973,2018-01-22 03:48:49 UTC,"there is no error,only in the table of cinder.volumes ,the volume_type_id is null,when i create a vm,so the command cinder show retrun volume_type is None too.
*************************** 1. row ***************************
                 created_at: 2018-01-18 03:01:12
                 updated_at: 2018-01-18 03:08:42
                 deleted_at: NULL
                    deleted: 0
                         id: 3f6fbaa3-5761-4ddd-8d15-153ca51ae7eb
                     ec2_id: NULL
                    user_id: e436ff259ec5464797795780ca1ce0f3
                 project_id: bb5416577889426eac3466eaef5b2ca6
                       host: node6@ms5520#ms5520
                       size: 20
          availability_zone: nova
                     status: in-use
              attach_status: attached
               scheduled_at: 2018-01-18 03:01:12
                launched_at: 2018-01-18 03:08:19
              terminated_at: NULL
               display_name:
        display_description:
          provider_location: macrosan uuid:0x00b34201-8a180066-1d359606-d7d7e1d4
              provider_auth: NULL
                snapshot_id: NULL
             volume_type_id: NULL
               source_volid: NULL
                   bootable: 1
          provider_geometry: NULL
                   _name_id: NULL
          encryption_key_id: NULL
           migration_status: NULL
         replication_status: disabled
replication_extended_status: NULL
    replication_driver_data: NULL
        consistencygroup_id: NULL
                provider_id: NULL
                multiattach: 0
            previous_status: NULL
               cluster_name: NULL
                   group_id: NULL"
1743973,2018-02-09 08:05:27 UTC,"I think this is not a problem, if you want to have a default volume type, you can set this default volume type in the cinder.conf configuration file, set default_volume_type = <volume_type_name>, the volume you create will be accompanied by a volume type id."
1743981,2018-01-18 15:34:33 UTC,how would you enforce a restriction? a threshold can be any value depending on context.
1743986,2018-01-19 06:30:42 UTC,"My gut says that there is probably a difference in Mongo 2.4 vs 3.2 and
what we could do. I believe 2.4 only supports ""repairDatabase"" to squish
everything, vs ""compact"" which can target specific collections.
I suppose in either case, backups should already be isolated in its own
database.
Going a little bit further, though. There is some concern if you were
removing lots of backups. We wouldn't really want to compact between each
removal. (I have 30, delete one, compact 29GB, delete another, compact
28GB, delete another, 27GB... etc.)
""juju remove-backup"" doesn't yet support multiple backups to be removed. I
think it should.
I also wonder if it should take an optional flag about compacting the
database. (We could default it to compact and just allow you to specify
--no-compact, potentially)"
1743986,2018-01-19 07:17:41 UTC,Good thoughts. One nitpick though :
1743986,2018-01-19 07:19:00 UTC,"Heh, although https://docs.mongodb.com/v3.2/reference/command/compact/ does say ""On WiredTiger databases, this command will release unneeded disk space to the operating system."" and WT appeared in 3.0"
1743986,2018-01-19 10:34:20 UTC,"mgopurge has code that switches between compact and repairDatabase based on
version, which makes me think that compact didn't actually do what we want
on 2.4. I haven't personally investigated it."
1743986,2018-02-08 14:38:27 UTC,"Juju should not be storing backups in the database by default, in my opinion.
We had a lot of issues dealing with customers that do regular backups (on a weekly/monthly basis), and the disk usage rapidly goes up in such situations."
1743986,2018-02-09 08:18:14 UTC,"I'd like to second Marios sentiment here. The disk space usage can be quite unexpected, and the effect is exacerbated by the fact that space is not automatically free'd in mongodb. In fact, I have a juju 1.25.13 env here where even after deleting backups and running db.repairDatabase() (which is the documented way of freeing up disk in mongodb) the disk space that has been used is not reclaimed. And on the other hand, having backups of a database in the same database doesn't provide much benefit in a disaster recovery scenario."
1743992,2019-07-03 17:18:22 UTC,Accessing live environments is not part of our triage workflow anymore.
1743998,2018-05-09 18:16:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744007,2020-05-20 12:38:59 UTC,Mojo now supports python3.
1744007,2018-01-18 09:10:03 UTC,Octal expression syntax changed for Py3.  Numbers with leading zeros are now invalid.
1744007,2018-01-18 10:27:07 UTC,We are taking a limited spike on evaluating the depth of work to make mojo py3-only compatible.  Branches linked.
1744007,2018-01-18 12:17:06 UTC,Related bug (mojo tests are failing at upstream trunk):  https://bugs.launchpad.net/mojo/+bug/1744048
1744009,2021-01-16 04:17:54 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1744009,2018-01-18 09:39:17 UTC,"When I checked the source code, I think the problem is that on Microsoft Windows bind() can not use a multicast address."
1744009,2020-11-16 18:21:34 UTC,"Have you ever tried to suggest your change as a patch to the qemu-devel mailing list? See:
https://wiki.qemu.org/Contribute/SubmitAPatch"
1744012,2018-01-22 20:19:14 UTC,We are working on a patch for Heat: https://review.openstack.org/#/c/533426/ which should address this bug.
1744012,2018-01-22 20:25:05 UTC,"The patch above add support for 'network', 'port' and 'v4/v6-fixed-ip'. The 'auto' mode is not yet supported in Zun side and the CLI help text is inaccurate (which should be fixed). We have a BP to track the auto-allocated network feature: https://blueprints.launchpad.net/zun/+spec/auto-allocate-network . Once it is implemented, we will push another to Heat to support that."
1744012,2018-01-24 08:35:02 UTC,Ah I did not see that there was a WIP patch before raising the issue. Then I will eagerly await for the patch to be finished and merged upstream. Thanks!
1744014,2020-12-03 12:42:54 UTC,Mariadb backuprs are implemented with https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/755261
1744015,2018-01-18 09:48:59 UTC,"IMHO, it would be nice if the Desktop install supported all the VPN plugins out-of-the-box. Users shouldn't need to hunt for plugin packages to install."
1744032,2018-01-31 16:14:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539584"
1744032,2018-03-07 16:29:51 UTC,"Reviewed:  https://review.openstack.org/539584
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b80c245ba529ab603910b5c0e2fa466bf0b6a146
Submitter: Zuul
Branch:    master"
1744032,2018-03-07 17:00:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550529"
1744032,2018-03-08 15:17:31 UTC,"Reviewed:  https://review.openstack.org/550529
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e2d08409f168aadef9223fae5fedfea27d74623d
Submitter: Zuul
Branch:    stable/queens"
1744032,2018-04-02 13:09:19 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1744032,2018-04-20 13:14:58 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1744049,2018-01-18 12:30:07 UTC,This change was made by a bot.
1744049,2018-01-18 13:21:36 UTC,"Looks like this was a result of the nvidia-384 dkms driver not working well with the 4.13.0-30.33 kernel in -proposed.  Once we removed this driver, the kernel was able to boot properly with fully functional keyboard/touchpad and wifi."
1744053,2018-04-30 17:09:24 UTC,"Hi
When i upgrated Unbuntu From 16.04LTS to 17.10,
i had the same error message :"
1744053,2019-09-08 22:36:11 UTC,"dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  desktop-file-utils -> bamfdaemon
 packages' pending triggers which are or may be unresolvable:
  man-db: /usr/share/man
  doc-base: /usr/share/doc-base
  libc-bin: ldconfig
  bamfdaemon: /usr/share/applications
  desktop-file-utils: /usr/share/applications
  mime-support: /usr/share/applications
  gconf2: /usr/share/GConf/gsettings"
1744053,2018-01-19 00:54:17 UTC,"Hi Rick, this auto-submitted bug is for another separate issue on your computer -- triggers looping during package installation."
1744055,2018-10-17 13:10:41 UTC,"Hello alpha23,"
1744055,2018-09-24 01:16:38 UTC,Does anyone have the Freezer UI working in Queens' Horizon?
1744055,2018-08-13 01:32:15 UTC,"Derek, your modification did not work.  I just received a different error:"
1744055,2018-10-23 22:58:55 UTC,"Derek, Florian,"
1744055,2018-06-15 03:55:57 UTC,"To clarify, the above was with stable/queens"
1744055,2018-06-15 03:40:11 UTC,Any update on this?
1744055,2018-05-16 20:43:27 UTC,"I tried a couple of things, but still didn't get it to work."
1744055,2018-03-07 16:20:22 UTC,This is also affecting the ubuntu stable/pike version.
1744055,2018-07-13 06:40:25 UTC,"In my case, I'd modified the parameter OPENSTACK_KEYSTONE_URL = ""{{ keystone_internal_url }}"" in the file local_settings of horizon to OPENSTACK_KEYSTONE_URL = ""{{ keystone_internal_url }}/v3"" to solve the freezer api call
 https://github.com/openstack/kolla-ansible/blob/stable/queens/ansible/roles/horizon/templates/local_settings.j2#L209"
1744062,2018-08-09 15:30:05 UTC,I will now test the final piece which is xenial-queens-proposed (but since that's the exact same version as the already tested bionic-proposed I don't expect anything to be different).
1744062,2018-07-30 16:05:26 UTC,"The verification of the Stable Release Update for keepalived has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1744062,2018-07-30 16:15:31 UTC,This bug was fixed in the package keepalived - 1:1.3.9-1ubuntu0.18.04.1
1744062,2018-08-05 23:46:44 UTC,Any news on the xenial SRU of keepalived for this bug?  It's not showing up in http://people.canonical.com/~ubuntu-archive/pending-sru per https://wiki.ubuntu.com/StableReleaseUpdates#Reviewing_procedure_and_tools.
1744062,2018-08-06 12:47:56 UTC,I've just asked for a review in #ubuntu-release.
1744062,2018-08-06 13:57:00 UTC,"Hello Corey, or anyone else affected,"
1744062,2018-08-09 15:27:46 UTC,I've tested the xenial-proposed package with Openstack Mitaka and confirm that it now behaves in the same way as 1.3.9 from Bionic i.e. if I kill the neutron state change agent then keepalived:
1744062,2018-08-15 01:06:31 UTC,This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu0.16.04.1
1744062,2018-08-21 12:32:48 UTC,"This bug was fixed in the package keepalived - 1:1.3.9-1ubuntu0.18.04.1~cloud0
---------------"
1744062,2018-08-20 14:35:46 UTC,Tested trusty-mitaka-proposed as above and confirm it is good (and behaves in the same way).
1744062,2018-08-21 12:25:38 UTC,The verification of the Stable Release Update for keepalived has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744062,2018-08-21 12:25:41 UTC,"This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu0.16.04.1~cloud0
---------------"
1744062,2018-08-21 12:32:47 UTC,The verification of the Stable Release Update for keepalived has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744062,2019-10-28 08:08:04 UTC,another related lp bug #1818614 to address multiple master problem mentioned in the comment #29
1744062,2020-06-23 20:05:45 UTC,It appears this is fixed in keepalived and no longer needs fixing in neutron. Please feel free to reopen this bug if that is not the case.
1744062,2018-07-25 17:38:59 UTC,I've uploaded keepalived 1:1.2.24-1ubuntu0.16.04.1 to the xenial review queue where it is awaiting SRU team review. This xenial fix is paired with https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1783583.
1744062,2018-08-17 13:09:58 UTC,"Hello Corey, or anyone else affected,"
1744062,2018-07-25 14:27:07 UTC,I've deleted the keepalived versions from ocata-staging and pike-staging. We should be able to fix this in xenial with a new stable point release and patch backport.
1744062,2018-08-10 08:25:54 UTC,Tested xenial-queens-proposed as above and confirm it is good (and behaves in the same way).
1744062,2018-07-16 14:01:55 UTC,"Hello Corey, or anyone else affected,"
1744062,2018-01-24 09:44:20 UTC,I have some thoughts in my mind for this problem as below:
1744062,2018-07-25 10:59:39 UTC,"Ok I have now completed testing the bionic-proposed keepalived package with Openstack Queens and am happy that it resolves the problem of ensuring that keepalived will teardown routes, vips, evips etc when it comes back up and transitions from master to backup. My test comprised of deploying Queens with 3 gateways, creating 100 users/projects each with 1 router, creating some instances with floating ips then forcibly killing both the keepalived and neutron-keepalived-state-change processes associated with a particular router for which i have an instance with a fip. I then observed that the qrouter ns interfaces for that router were definitely unconfigured and the vrrp transition happened as expected. This is in contrast to e.g. keepalived 1:1.2.19-1ubuntu0.2 available with all Xenial releases of Openstack for which I consistently see the qrouter interfaces remain configured on > 1 gateway."
1744062,2018-02-08 19:13:52 UTC,FYI:  Unsubscribing field SLA based on re-triage with Kiko R.
1744062,2018-02-08 19:16:03 UTC,I do think this issue is still of high importance to OpenStack's overall scale and resilience story.
1744062,2018-02-14 14:33:48 UTC,FYI: Resubscribing field SLA.  It was not raised as critical by Kiko R.; I raised it and it's still an active ongoing problem on a customer site.  Please do not unsubscribe again without discussion with the correct people.
1744062,2018-02-14 15:11:19 UTC,Downgrading to Field High - I think the Critical part is tracked in LP #1749425
1744062,2018-02-16 11:17:50 UTC,"Just as another thing to consider - the deployment where this is happening also experienced bug 1749425 which resulted in packet loss; the networks between network/gateway units is also made via OVS, so if OVS was dropping packets due to the large number of missing tap devices, its possible this was also impacting connectivity between keepalived instances for HA routers, resulting in active/active nasty-ness."
1744062,2018-03-20 22:18:47 UTC,"@cgregan I think this is really a situation where the desired scale/density is at odds with the fundamental design of neutron HA routers.  It's not something to address in the charms or in the packaging.  As such, I'd consider this a feature request, against upstream Neutron, and I don't have an assignee for that."
1744062,2018-03-26 15:22:44 UTC,We experience the same issue although we have a smaller environment with only around 40 Neutron router running HA (two agents per router) over three physical controllers running Ocata on Ubuntu 16.04
1744062,2018-03-02 14:28:15 UTC,We need an assigned engineer to meet the requirements of Field High SLA. Please assign
1744062,2018-01-23 17:03:29 UTC,"This bug falls under the Canonical Cloud Engineering service-level agreement (SLA) process, as a field critical bug."
1744062,2018-05-11 02:40:27 UTC,VRRP heart beat lose may cause the multiple active router behavior. The underlying connectivity is key point for this. A monitoring for such behavior is also necessary.
1744062,2018-07-03 12:47:13 UTC,As reported by Xav in https://bugs.launchpad.net/ubuntu/+bug/1731595:
1744062,2018-07-03 13:51:38 UTC,It appears the following commits are required to fix this for keepalived:
1744062,2018-07-03 15:50:02 UTC,Moving back to New for neutron for the time being since we think this may be fixed in keepalived.
1744062,2018-07-03 15:54:01 UTC,"I've uploaded new versions of keepalived to cosmic, bionic (awaiting SRU team review), pike-staging, and ocata-staging. I need to confirm with other cloud archive admins that this is ok to backport to pike/ocata cloud archives prior to promoting to pike-proposed/ocata-proposed. In the mean time if you'd like to test the ocata fix (where this was initially reported) you can install from the staging PPA:"
1744062,2018-07-03 16:28:57 UTC,This bug was fixed in the package keepalived - 1:1.3.9-1ubuntu1
1744062,2018-07-09 12:04:20 UTC,"Hello Corey, or anyone else affected,"
1744062,2018-07-13 04:14:04 UTC,Subscribed field-high.  This is affecting production environments.
1744062,2018-04-12 10:10:41 UTC,Our environment is experiencing the same behavior.
1744064,2018-01-21 14:58:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536136"
1744064,2018-08-09 13:15:26 UTC,This issue was fixed in the openstack/ironic-python-agent 3.3.0 release.
1744073,2018-01-21 15:56:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536139"
1744075,2019-03-21 17:29:11 UTC,This issue was fixed in the openstack/puppet-openstacklib 14.4.0 release.
1744075,2019-05-16 23:06:48 UTC,This issue was fixed in the openstack/puppet-openstacklib 11.6.0 release.
1744075,2019-03-05 13:18:38 UTC,"Hi,"
1744075,2018-07-18 17:38:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583675"
1744075,2018-08-02 13:47:51 UTC,"I was experimenting in this patch but I'm not sure this is the right approach. I'll poke around again and get some feedback, so we can move forward."
1744075,2018-08-02 12:56:47 UTC,"So, are we abandoning the ""PYTHONIOENCODING"" fix? What was the issue with it? Do we have a better way of fixing this?"
1744075,2018-07-30 20:30:51 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/583675
Reason: feel free to restore, I was just experimenting here."
1744075,2018-12-20 15:27:54 UTC,"So, apparently, it's more due to puppet than python.
More specifically, there's a ""puppet-openstacklib"" package that gives some provider for openstack.
It also provides a small lib that parses the CSVs from openstack CLI, and map the content to some simple object."
1744076,2018-01-18 14:41:37 UTC,apport information
1744076,2018-01-18 14:41:38 UTC,apport information
1744076,2018-01-18 14:41:39 UTC,apport information
1744076,2018-01-18 14:41:41 UTC,apport information
1744076,2018-01-18 14:41:45 UTC,apport information
1744076,2018-01-18 14:41:47 UTC,apport information
1744076,2018-01-18 14:41:48 UTC,apport information
1744076,2018-01-18 14:41:51 UTC,apport information
1744076,2018-01-18 15:20:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1744076,2018-01-19 09:44:21 UTC,Seb:
1744076,2018-01-19 09:51:17 UTC,/var/log/syslog extract showing bluetoothd/network-manager-ofono interaction.
1744076,2018-01-18 14:41:46 UTC,apport information
1744076,2018-01-18 14:41:36 UTC,apport information
1744076,2018-01-18 14:41:32 UTC,apport information
1744076,2018-01-18 14:41:32 UTC,apport information
1744076,2018-01-18 14:41:17 UTC,apport information
1744076,2018-01-18 14:41:18 UTC,apport information
1744076,2018-01-18 14:41:19 UTC,apport information
1744076,2018-01-18 14:41:34 UTC,apport information
1744076,2018-01-18 14:41:23 UTC,apport information
1744076,2018-01-18 14:41:24 UTC,apport information
1744076,2018-01-18 14:41:21 UTC,apport information
1744076,2018-01-18 14:41:26 UTC,apport information
1744076,2018-01-18 14:41:27 UTC,apport information
1744076,2018-01-18 14:41:28 UTC,apport information
1744076,2018-01-18 14:41:30 UTC,apport information
1744076,2018-01-18 14:41:31 UTC,apport information
1744076,2018-01-18 14:41:25 UTC,apport information
1744079,2019-04-03 12:43:08 UTC,"Hello Matthew, or anyone else affected,"
1744079,2019-04-03 12:42:21 UTC,"Hello Matthew, or anyone else affected,"
1744079,2019-03-26 04:18:48 UTC,"Reviewed:  https://review.openstack.org/631372
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e485938f5e7b2f7f9c69f97b6c1b58b3de8d68ec
Submitter: Zuul
Branch:    stable/pike"
1744079,2019-03-22 03:49:11 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1744079,2019-01-25 03:40:18 UTC,"For stable/pike
https://review.openstack.org/#/c/530743
https://review.openstack.org/#/c/631372"
1744079,2019-01-07 10:58:21 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744079,2019-01-16 19:55:15 UTC,"Hua, have you attempted to get the pike and ocata patches backported upstream? If possible we need to get them upstream first for affected releases."
1744079,2019-01-07 12:05:07 UTC,"This bug was fixed in the package nova - 2:18.0.3-0ubuntu1~cloud0
---------------"
1744079,2019-01-07 12:05:05 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744079,2019-01-07 10:58:26 UTC,"This bug was fixed in the package nova - 2:17.0.7-0ubuntu1~cloud0
---------------"
1744079,2019-04-03 14:33:25 UTC,A new version of nova has been uploaded to the xenial unapproved queue where it is awaiting SRU team review: https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=nova
1744079,2019-01-24 07:12:47 UTC,"Change abandoned by Zhang Hua (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/631372"
1744079,2019-04-10 22:26:34 UTC,Successfully verified pike-proposed nova 2:16.1.7-0ubuntu1~cloud2 and ocata-proposed nova 2:15.1.5-0ubuntu1~cloud3
1744079,2019-04-26 17:15:54 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1744079,2019-04-16 15:16:56 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744079,2019-04-16 15:16:58 UTC,"This bug was fixed in the package nova - 2:15.1.5-0ubuntu1~cloud3
---------------"
1744079,2019-04-16 15:17:36 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744079,2018-12-19 20:48:28 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1744079,2019-04-16 15:17:38 UTC,"This bug was fixed in the package nova - 2:16.1.7-0ubuntu1~cloud2
---------------"
1744079,2019-04-30 20:28:33 UTC,"Hello Matthew, or anyone else affected,"
1744079,2019-05-02 17:30:59 UTC,"Hello Matthew, or anyone else affected,"
1744079,2019-05-06 09:52:23 UTC,Successfully verified xenial-proposed nova 2:13.1.4-0ubuntu4.4
1744079,2019-05-06 10:45:50 UTC,Successfully verified mitaka-proposed nova 2:13.1.4-0ubuntu4.4~cloud0
1744079,2019-05-15 11:52:34 UTC,This bug was fixed in the package nova - 2:13.1.4-0ubuntu4.4
1744079,2019-05-15 14:33:55 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744079,2019-05-15 14:33:56 UTC,"This bug was fixed in the package nova - 2:13.1.4-0ubuntu4.4~cloud0
---------------"
1744079,2019-04-15 14:33:46 UTC,"Reviewed:  https://review.openstack.org/631376
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b0030ea2273840bd428070b2f23e755a30d2a35
Submitter: Zuul
Branch:    stable/ocata"
1744079,2018-12-19 10:01:48 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1744079,2018-11-27 10:20:40 UTC,Successfully verified queens-proposed nova 2:17.0.6-0ubuntu2~cloud0
1744079,2018-12-18 19:42:39 UTC,This bug was fixed in the package nova - 2:18.0.3-0ubuntu1
1744079,2018-01-22 12:33:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536351"
1744079,2018-08-29 11:42:16 UTC,"Reviewed:  https://review.openstack.org/536351
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e2cc275063658b23ed88824100919a6dfccb760d
Submitter: Zuul
Branch:    master"
1744079,2018-09-13 22:15:13 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/602477"
1744079,2018-09-13 22:15:28 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/602478"
1744079,2018-11-05 16:20:42 UTC,"The attachment ""lp1744079_xenial.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1744079,2018-11-05 16:57:52 UTC,"I've uploaded new versions of nova with the fix for this bug to the disco, cosmic, and bionic unapproved queues."
1744079,2018-11-07 23:35:01 UTC,This bug was fixed in the package nova - 2:18.0.1-0ubuntu3
1744079,2018-11-13 17:58:49 UTC,"Hello Matthew, or anyone else affected,"
1744079,2018-11-13 18:01:07 UTC,"Hello Matthew, or anyone else affected,"
1744079,2018-11-19 14:41:15 UTC,"Hello Matthew, or anyone else affected,"
1744079,2018-12-03 14:46:34 UTC,"Hi Hua, would you also be able to verify cosmic-proposed and bionic-proposed? Those will need to be verified before queens-proposed can be promoted. Thanks."
1744079,2018-12-05 19:06:18 UTC,This hasn't been tested yet on cosmic-proposed and we have a stable point release of nova to get out so we're going to have to combine this fix with the stable point release. That means this is going to have to live in cosmic-proposed (and rocky-proposed) for another 7 days minimum.
1744079,2018-12-05 20:00:58 UTC,"Hello Matthew, or anyone else affected,"
1744079,2018-12-18 21:43:07 UTC,This bug was fixed in the package nova - 2:17.0.7-0ubuntu1
1744079,2018-12-07 13:23:56 UTC,This hasn't been tested yet on bionic-proposed and we have a stable point release of nova to get out so we're going to have to combine this fix with the stable point release. That means this is going to have to live in bionic-proposed (and queens-proposed) for another 7 days minimum.
1744079,2018-12-07 11:20:00 UTC,"Hello Matthew, or anyone else affected,"
1744079,2018-12-17 20:00:20 UTC,"@Hua, we'll have to fix this in pike and ocata before it can be fixed in mitaka."
1744079,2018-12-14 05:01:43 UTC,"Reviewed:  https://review.openstack.org/602478
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b2c7483003789ecaa0eea8afb49b783934bbf0f
Submitter: Zuul
Branch:    stable/queens"
1744079,2018-12-13 11:46:49 UTC,"Hi Corey, could you pls nominate this fix to xenial as well? we have a customer using xenial-mitaka, I have uploaded a debdiff 'lp1744079_xenial.debdiff', many thanks."
1744079,2018-12-13 11:41:21 UTC,Successfully verified rocky-proposed nova 2:18.0.3-0ubuntu1~cloud0
1744079,2018-12-13 09:36:41 UTC,Successfully verified queens-proposed nova 2:17.0.7-0ubuntu1~cloud0
1744079,2018-12-18 19:32:39 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1744079,2018-12-13 07:28:59 UTC,Successfully verified cosmic-proposed nova 2:18.0.3-0ubuntu1
1744079,2018-12-12 09:49:52 UTC,"Hi Corey, sorry for the late reply because I am just back from my pto today, I will verify them ASAP."
1744079,2018-12-12 01:09:28 UTC,"Hello Matthew, or anyone else affected,"
1744079,2018-12-11 19:58:59 UTC,"Hello Matthew, or anyone else affected,"
1744079,2018-12-07 18:12:10 UTC,"Reviewed:  https://review.openstack.org/602477
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c1c373291a93ad6304ff03ea09fea24a5cb5fd0
Submitter: Zuul
Branch:    stable/rocky"
1744079,2018-12-13 08:03:47 UTC,Successfully verified bionic-proposed nova 2:17.0.7-0ubuntu1
1744080,2018-02-16 16:33:05 UTC,see also - https://bugs.launchpad.net/evergreen/+bug/1329837
1744081,2018-01-18 21:05:28 UTC,"@Richard Harding,"
1744081,2018-01-18 21:16:43 UTC,"Spoke off-line and we'd need to try all versions of Juju as this environment was destroyed. Potentially, this could be happening in all supported Juju 2.x..."
1744082,2018-03-03 22:09:59 UTC,I'm having the same issue. gparted was working fine. I restarted my pc and somehow it was uninstalled when i turned my pc back on. I installed it and tried running it and the same thing happened.
1744082,2018-09-02 13:01:50 UTC,"I'm getting the ""Unit -.mount does not exist, proceeding anyway."" message with Linux Mint 19 (Ubuntu 18.04 base), but gparted starts without any other problems."
1744082,2018-05-28 15:37:15 UTC,after getting 18.04 LTS with the latest updates GPartes works again :-)
1744086,2018-01-18 16:12:40 UTC,Why not just turn off the effect or turn down the dry/wet knob?
1744086,2018-01-18 18:14:31 UTC,"It's about quickly cutting the effect, while being able to quickly bring it back, or kill a deck in case the effect distorts, clips or just disturbs.
Interaction with Dry/Wet knob -like any knob- is way slower that a button or crossfader cut.
When I turn off the effect, resurrecting an echo tail is possible but way to complicated."
1744086,2018-01-18 19:19:07 UTC,"Ok, so we actually running into the situation that Traktor also has, the need to configure the routing. We want originally avoid this. It would be great, if we can add rons0's valid use case in a smarter way.
From this point of view, it is a regression compared to Mixxx 2.0"
1744086,2018-01-18 20:05:54 UTC,Echo on QuickEffect knob lacks the echo trail because it's pre-fader.
1744086,2018-03-05 12:50:55 UTC,Post Fader should mean Post CHANNEL fader but still Pre CROSSFADER. This would solve the problem above. It's the way physical mixing desks with effects work such as the Pioneer DJM range or Numark with the Chaos Pad built it and is what any seasoned DJ will expect to experience.
1744095,2018-01-28 15:12:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744095,2018-04-02 19:01:16 UTC,"For me, it crashes as g_variant_new_object_path: assertion 'g_variant_is_object_path (object_path)' failed."
1744095,2018-01-18 15:20:34 UTC,"StacktraceTop:
 g_variant_is_trusted (value=0x0) at ../../../../glib/gvariant-core.c:607
 g_variant_builder_add_value (builder=0xbfbd1fec, value=0x0) at ../../../../glib/gvariant.c:3490
 g_variant_valist_new (str=str@entry=0xbfbd2060, app=app@entry=0xbfbd2078) at ../../../../glib/gvariant.c:5196
 g_variant_new_va (format_string=<optimized out>, endptr=0x0, app=0xbfbd2078) at ../../../../glib/gvariant.c:5372
 g_variant_new (format_string=0x501caa ""(o@a{sv})"") at ../../../../glib/gvariant.c:5307"
1744097,2018-06-28 07:48:40 UTC,"I had the same problem and tried to work around it by disabling TLS, but that just got me another problem:
error creating self-signed certificates: open /var/run/kubernetes/apiserver.crt: read-only file system"
1744097,2018-07-06 06:07:12 UTC,"I think this got fixed with:
https://github.com/openstack/magnum/commit/393e70f0b0b12fe45b0271f2c2e53391d462076d#diff-07f834394f6e5c442202c71ea8e9e0c3"
1744098,2019-07-25 02:28:29 UTC,"FWIW, there is a ubuntu-xenial-postgresql/install.d/31-fix-init-script that changes the pidfile...however it is either not being run or overwritten later, as the built image (as indicated above) has the wrong pidfile."
1744098,2019-07-17 06:45:55 UTC,"FWIW - manipualating the devstack generated image to fix the systemd unit file, then re-uploading it, results in a guest in ACTIVE state after launching a new instance. So we need to figure out how to apply those existing fixes during the guest image build."
1744098,2018-02-05 13:29:57 UTC,This bug is resolve by this commit: https://review.openstack.org/#/c/534667/
1744098,2018-01-23 16:26:34 UTC,"Change abandoned by Ga?tan Trellu (<email address hidden>) on branch: master
Review: https://review.openstack.org/535369
Reason: Already fixed there: https://review.openstack.org/#/c/534667/"
1744098,2018-01-18 15:31:01 UTC,https://review.openstack.org/#/c/535369/
1744098,2019-07-17 03:00:53 UTC,I'm seeing exactly this issue on a devstack setup (master from last week) that makes a xenial guest. I note that the systemd unit file: /lib/systemd/system/postgresql@.service has:
1744099,2019-10-30 12:11:42 UTC,"とりあえずfonts-takaoをインストールすればこのバグは回避できますね。
デフォルトのフォントがTakaoフォントになりますが。"
1744099,2020-02-23 07:14:07 UTC,これなんとかしたいですよね……
1744099,2020-03-19 22:13:53 UTC,"この問題、Fedora 32 betaでは直ってますね。
(添付画像はFedora 32 betaのGeditのプラグイン一覧です)"
1744099,2020-04-17 12:07:45 UTC,すみません、Fedora 32 betaの件は私の勘違いでした。UbuntuでもNoto Sans CJK JPをインターフェースのフォントとして設定するとFedoraと同じように表示されますね…
1744100,2018-01-26 17:18:09 UTC,I want to add that I would not want this to automatically clear -- I just successfully used this while transferring several vol/copies across several bib records attached to an incorrect owning library to the correct owning library. It was very efficient for my initial choice on a title record to be retained since they all belonged to the same library and I did not have to choose it repeatedly.
1744110,2018-01-22 14:13:01 UTC,Review for this bug:
1744110,2018-01-23 10:02:38 UTC,"Change abandoned by Ali Sanhaji (<email address hidden>) on branch: master
Review: https://review.openstack.org/535386
Reason: Duplicate of: https://review.openstack.org/#/c/534234/"
1744119,2020-05-14 09:53:54 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/728004"
1744131,2018-01-18 18:51:36 UTC,Thanks for your report!
1744138,2018-02-07 02:35:27 UTC,I have a similar configuration and was getting an installation error as well.
1744141,2018-01-19 10:52:37 UTC,"Fail over is only triggered when the master unit is removed (juju remove-unit pgsql-ha/7). This was a deliberate design decision, as I did not want automatic failover but for it to be explicit and under operator control. Also, at the time, there was no regularly triggered hook that would allow the charm to detect a failed master and react."
1744141,2018-01-19 15:12:52 UTC,"Yes you are right.. the cluster was 2 nodes, when I removed the master unit it goes to failover the secondary and raised it to master."
1744153,2018-01-18 21:56:35 UTC,+1
1744153,2018-01-19 14:12:41 UTC,I suppose it may be worth creating an OUS for forbidden characters (initially populated with []{}();:\/ at least) so that installations can be more or less strict without code changes. Personally I'd be happy to hard code that list and allow others to be added but I'm open to ideas.
1744153,2020-03-31 17:12:40 UTC,"Here's a little something that you can run to see if you have user names in the database that differ only in case.  We have a few hundred such duplicates, though a handful look like duplicate patrons who used the same user name, once in uppercase and once in lowercase."
1744155,2020-06-15 05:50:52 UTC,Please explain in more detail what kind of problem you are encountering.
1744155,2020-08-15 04:17:16 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1744163,2018-01-18 21:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1744163,2018-01-18 21:21:48 UTC,"Is there a kernel trace in the logs from the hang?  I'd like to see if this is related to bug 1733662, which has a test kernel here if you want to try it:"
1744163,2018-01-18 21:41:02 UTC,"kernel: [  242.381420] INFO: task kworker/u129:0:6 blocked for more than 120 seconds.
kernel: [  242.417101]       Not tainted 4.15.0-041500rc8-generic #201801142030
kernel: [  242.447495] ""echo 0 > /proc/sys/kernel/hung_task_timeout_secs"" disables this message.
kernel: [  242.482715] kworker/u129:0  D    0     6      2 0x80000000
kernel: [  242.482729] Workqueue: writeback wb_workfn (flush-8:0)
kernel: [  242.482731] Call Trace:
kernel: [  242.482744]  __schedule+0x291/0x880
kernel: [  242.482747]  schedule+0x2c/0x80
kernel: [  242.482751]  io_schedule+0x16/0x40
kernel: [  242.482756]  get_request+0x2a4/0x7f0
kernel: [  242.482761]  ? wait_woken+0x80/0x80
kernel: [  242.482765]  blk_queue_bio+0x128/0x440
kernel: [  242.482767]  generic_make_request+0x11f/0x300
kernel: [  242.482769]  submit_bio+0x73/0x140
kernel: [  242.482770]  ? submit_bio+0x73/0x140
kernel: [  242.482836]  xfs_submit_ioend+0x87/0x1c0 [xfs]
kernel: [  242.482861]  xfs_do_writepage+0x377/0x690 [xfs]
kernel: [  242.482868]  write_cache_pages+0x209/0x4d0
kernel: [  242.482891]  ? xfs_vm_writepages+0xf0/0xf0 [xfs]
kernel: [  242.482913]  xfs_vm_writepages+0xbe/0xf0 [xfs]
kernel: [  242.482915]  do_writepages+0x48/0xe0
kernel: [  242.482919]  ? check_preempt_curr+0x2d/0x90
kernel: [  242.482920]  ? ttwu_do_wakeup+0x1e/0x140
kernel: [  242.482924]  __writeback_single_inode+0x45/0x330
kernel: [  242.482926]  ? __writeback_single_inode+0x45/0x330
kernel: [  242.482927]  ? try_to_wake_up+0x59/0x480
kernel: [  242.482929]  writeback_sb_inodes+0x1e1/0x510
kernel: [  242.482932]  __writeback_inodes_wb+0x67/0xb0
kernel: [  242.482934]  wb_writeback+0x26b/0x300
kernel: [  242.482937]  wb_workfn+0x180/0x410
kernel: [  242.482939]  ? wb_workfn+0x180/0x410
kernel: [  242.482943]  process_one_work+0x1ea/0x410
kernel: [  242.482945]  worker_thread+0x32/0x410
kernel: [  242.482948]  kthread+0x11e/0x140
kernel: [  242.482949]  ? process_one_work+0x410/0x410
kernel: [  242.482951]  ? kthread_create_worker_on_cpu+0x70/0x70
kernel: [  242.482956]  ret_from_fork+0x32/0x40"
1744163,2018-07-24 09:31:53 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1744165,2018-01-18 23:52:37 UTC,https://review.openstack.org/535498
1744165,2018-01-19 13:29:26 UTC,This issue appears when the guest agent is started by the root user.
1744168,2018-01-19 06:44:14 UTC,Spaces in exec parameter is against free desktop specification. Also a script should not contain spaces in its name. You need to fix your code. Nothing to be fixed here.
1744168,2018-01-20 15:09:25 UTC,"Hmm... Khurshid, do you mean that executable cannot be placed into directory containing spaces? If that's the case I would prefer the library to report an error rather than creating ill-formed file. Or maybe it should be checked in Unity. Or maybe both. But silent creation of such a file looks quite weird. Imagine, you hit ""Lock to Launcher"" and it simply doesn't work."
1744168,2018-01-22 07:15:16 UTC,"Executable can only placed in either /usr/bin, /usr/local/bin or /$HOME/bin. None of that contains spaces."
1744171,2020-12-29 22:23:25 UTC,El proyecto se encontra en https://wiki.gnome.org/Apps/GTG ahora.
1744179,2018-05-15 14:50:20 UTC,This change was made by a bot.
1744181,2018-01-24 12:08:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744182,2018-01-23 19:55:42 UTC,"2018-01-18 06:40:01.738 7 ERROR nova.compute.manager [instance: b4b7cabe-f78b-40d9-8856-3b6c213efd73] VimFaultException: An error occurred during host configuration.
2018-01-18 06:40:01.738 7 ERROR nova.compute.manager [instance: b4b7cabe-f78b-40d9-8856-3b6c213efd73] Faults: ['PlatformConfigFault']"
1744182,2018-02-01 22:26:31 UTC,Can you please upload log /var/log/vmware/vpxd/vpxd.log from vcenter (10.200.110.73)?
1744182,2018-02-14 13:20:21 UTC,"Setting to Incomplete until the reporter provides the asked log.
Reporter, please set the status back to 'New' once you provide it."
1744182,2018-02-23 02:15:33 UTC,"Sorry. Too late.
There is /var/log/vmware/vpxd/vpxd.log for vcenter (10.200.110.73)
2018-02-23T02:03:20.994Z info vpxd[7FFA26997700] [Originator@6876 sub=vpxLro opID=1d797aaa] [VpxLRO] -- FINISH lro-697
2018-02-23T02:03:20.994Z info vpxd[7FFA26997700] [Originator@6876 sub=Default opID=1d797aaa] [VpxLRO] -- ERROR lro-697 -- CustomFieldsManager -- vim.CustomFieldsManager.addFieldDefinition: vim.fault.DuplicateName:
--> Result:
--> (vim.fault.DuplicateName) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    name = ""com.vmware.vsan.clustermembers24"",
-->    object = 'vim.CustomFieldsManager:CustomFieldsManager'
-->    msg = """"
--> }
--> Args:
-->
--> Arg name:
--> ""com.vmware.vsan.clustermembers24""
--> Arg moType:
--> ""vim.ClusterComputeResource""
--> Arg fieldDefPolicy:
-->
--> Arg fieldPolicy:
-->
2018-02-23T02:03:20.996Z info vpxd[7FFA26997700] [Originator@6876 sub=vpxLro opID=12643e04] [VpxLRO] -- BEGIN lro-698 -- CustomFieldsManager -- vim.CustomFieldsManager.addFieldDefinition -- 52f42b19-fdbd-73e5-5e78-746ba8302c8e(52e26d8a-5738-7648-e9e0-6a3d8ea050a3)
2018-02-23T02:03:20.996Z info vpxd[7FFA26997700] [Originator@6876 sub=vpxLro opID=12643e04] [VpxLRO] -- FINISH lro-698
2018-02-23T02:03:20.996Z info vpxd[7FFA26997700] [Originator@6876 sub=Default opID=12643e04] [VpxLRO] -- ERROR lro-698 -- CustomFieldsManager -- vim.CustomFieldsManager.addFieldDefinition: vim.fault.DuplicateName:
--> Result:
--> (vim.fault.DuplicateName) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    name = ""com.vmware.vsan.clustermembers25"",
-->    object = 'vim.CustomFieldsManager:CustomFieldsManager'
-->    msg = """"
--> }
--> Args:
-->
--> Arg name:
--> ""com.vmware.vsan.clustermembers25""
--> Arg moType:
--> ""vim.ClusterComputeResource""
--> Arg fieldDefPolicy:
-->
--> Arg fieldPolicy:
-->
2018-02-23T02:03:21.012Z info vpxd[7FFA242CA700] [Originator@6876 sub=vpxLro opID=7323820a] [VpxLRO] -- BEGIN lro-699 -- CustomFieldsManager -- vim.CustomFieldsManager.addFieldDefinition -- 52f42b19-fdbd-73e5-5e78-746ba8302c8e(52e26d8a-5738-7648-e9e0-6a3d8ea050a3)
2018-02-23T02:03:21.012Z info vpxd[7FFA242CA700] [Originator@6876 sub=vpxLro opID=7323820a] [VpxLRO] -- FINISH lro-699
2018-02-23T02:03:21.012Z info vpxd[7FFA242CA700] [Originator@6876 sub=Default opID=7323820a] [VpxLRO] -- ERROR lro-699 -- CustomFieldsManager -- vim.CustomFieldsManager.addFieldDefinition: vim.fault.DuplicateName:
--> Result:
--> (vim.fault.DuplicateName) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    name = ""com.vmware.vsan.clustermembers26"",
-->    object = 'vim.CustomFieldsManager:CustomFieldsManager'
-->    msg = """"
--> }
--> Args:
-->
--> Arg name:
--> ""com.vmware.vsan.clustermembers26""
--> Arg moType:
--> ""vim.ClusterComputeResource""
--> Arg fieldDefPolicy:
-->
--> Arg fieldPolicy:
-->
2018-02-23T02:03:21.013Z info vpxd[7FFA242CA700] [Originator@6876 sub=vpxLro opID=202e9994] [VpxLRO] -- BEGIN lro-700 -- CustomFieldsManager -- vim.CustomFieldsManager.addFieldDefinition -- 52f42b19-fdbd-73e5-5e78-746ba8302c8e(52e26d8a-5738-7648-e9e0-6a3d8ea050a3)
2018-02-23T02:03:21.013Z info vp..."
1744182,2018-08-17 07:41:37 UTC,"The vpxd log is from 2018-02-23 but the Nova failure occurred on 2018-01-18, so this log is not useful."
1744182,2018-08-23 20:30:12 UTC,I'm going to set this to Incomplete since Rado has asked for more information from the bug reporter to investigate this further.
1744182,2018-01-19 00:42:37 UTC,This error occurred when I created the virtual machine.Can someone help me?
1744190,2018-01-19 02:47:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/535580"
1744190,2018-01-22 01:49:31 UTC,"Reviewed:  https://review.openstack.org/535580
Committed: https://git.openstack.org/cgit/openstack/python-senlinclient/commit/?id=7a764c9bd8ad639a49e1a977d3ad1d6ed481f33b
Submitter: Zuul
Branch:    master"
1744190,2018-01-22 05:14:07 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/536203"
1744190,2018-01-22 05:15:01 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/536204"
1744190,2018-01-23 06:02:23 UTC,"Reviewed:  https://review.openstack.org/536203
Committed: https://git.openstack.org/cgit/openstack/python-senlinclient/commit/?id=a08a5b1df1be88f85d3e557905ac69775c9a01a3
Submitter: Zuul
Branch:    stable/pike"
1744190,2018-01-23 06:03:59 UTC,"Reviewed:  https://review.openstack.org/536204
Committed: https://git.openstack.org/cgit/openstack/python-senlinclient/commit/?id=5167e8d2822cb6aceef10a31033573429344e556
Submitter: Zuul
Branch:    stable/ocata"
1744214,2018-02-01 05:13:55 UTC,Do you see the same issue if you boot Bionic live CD/USB in VBox?
1744214,2018-01-24 22:00:45 UTC,I needed to reinstall Ubuntu and the problems I attached earlier no longer apply.
1744214,2018-01-22 20:18:49 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1744214,2018-01-19 06:21:14 UTC,I also get the attached screenshot when attempting to boot into recovery mode.
1744214,2018-01-24 19:01:46 UTC,"I tried installing and testing the mainline kernel, but I encountered issues with the linux-image not generating. I also tried to install openssh-server and ssh while on 4.10.0-19-generic and I get errors that dpkg failed processing 4.13.0-25 with the new modules. I have tried uninstalling this same kernel and I encounter similar errors by dpkg."
1744214,2018-01-19 06:30:10 UTC,This change was made by a bot.
1744215,2019-09-12 12:49:24 UTC,tripleo-ui has been removed from kolla images - see https://review.opendev.org/#/c/662846/
1744215,2019-04-10 13:47:24 UTC,Building the image for centos/source still fails for me.
1744215,2019-03-29 11:25:45 UTC,Not blocking gate - decreasing priority.
1744215,2019-03-28 09:45:48 UTC,"It's been in skipped images (https://github.com/openstack/kolla/blob/a911010054ef514cdc28aad71f0a6869a830dd87/kolla/image/build.py#L103) for over a year, I think we should decrease priority (not Critical)."
1744215,2019-03-26 10:24:30 UTC,Do we need to do anything about this in kolla?
1744215,2018-02-21 20:35:23 UTC,Looks like https://review.openstack.org/#/c/539187 is the revert.
1744215,2018-01-30 11:02:57 UTC,The cause of the build failures was the fact that the tripleo-ui-latest.tar.gz file wasn't being updated on merges.  This has now been fixed.
1744215,2018-01-20 11:21:07 UTC,"Reviewed:  https://review.openstack.org/535633
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=ec0950b20937c67d75b5bab712dd2b57d8be7af5
Submitter: Zuul
Branch:    master"
1744215,2018-01-20 01:43:08 UTC,I just found out that tripleo-ui-7.4.7.tar.gz was published on the day when we upgraded our upstream check/gate jobs to nodejs8.  I'll keep looking.
1744215,2018-01-19 11:31:15 UTC,Looking at http://tarballs.openstack.org/tripleo-ui/ tripleo-ui-latest.tar.gz matches tripleo-ui-7.4.7.tar.gz. How is tripleo-ui-latest updated? We have merged the changes which fix reported issue yesterday.
1744215,2018-01-19 06:55:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/535633"
1744215,2018-07-25 09:11:32 UTC,How can I verify that this has been fixed?  What is the gate that the original report refers to?
1744215,2018-08-24 15:59:12 UTC,Dropping from critical as this is no longer affecting any gates. The revert is still pending over in Kolla
1744220,2018-01-22 10:01:49 UTC,"On further investigation, this seems to be limited to low-RAM units."
1744223,2018-06-01 14:41:38 UTC,"@Hunt Xu,"
1744223,2018-06-08 14:18:06 UTC,"@Hunt Xu,"
1744223,2018-05-18 20:10:06 UTC,We discussed this RFE during today's Drivers meeting. We want to make sure that the scope is only to be able to update external_v6_ip. Please confirm
1744223,2018-02-16 12:25:20 UTC,"i'm not sure if i understand use cases.
do you want to keep a vpn service without site connections for some reasons?
otherwise you can remove the vpn service, update the router gateway, and then re-create a vpn service, right?"
1744223,2018-05-18 10:32:01 UTC,"Hey guys, sorry for the late response."
1744223,2018-02-09 09:38:49 UTC,"@yamamoto, I am working on this. My idea is to only update the external_v*_ip of vpnservices upon ipsec-site-connection creation/updating/deleting. The external_v*_ip would be None if the vpnservice is not used by any ipsec-site-connections. Thus operations of the router gateway won't be blocked."
1744223,2018-05-18 13:40:38 UTC,Let's bring this up to the drivers meeting
1744223,2018-02-08 12:34:25 UTC,"do you have a suggestion how to improve it?
add local_address field to ipsec-site-connection?"
1744223,2018-05-11 13:47:36 UTC,"@Hunt Xu,"
1744225,2020-02-26 08:29:51 UTC,support for odl was dropped
1744234,2018-01-25 08:57:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744243,2018-01-29 23:22:32 UTC,"With 2.3.2, a container-networking-method value of """" is permitted, however I end up with a container unusable by juju."
1744243,2018-02-28 03:43:32 UTC,Upgrade bugs like this are actually fairly high priority.
1744244,2018-01-22 19:09:28 UTC,This bug was fixed in the package linux - 4.4.0-112.135
1744244,2018-01-22 20:01:39 UTC,The package has been published and the bug is being set to Fix Released
1744244,2018-01-22 08:19:42 UTC,fix confirmed spec-ctrl cpu flag is now visible inside kvm guest
1744244,2018-01-22 18:08:57 UTC,Setting regression-testing to 'Fix Released' based on test results from previous version (4.4.0-111.134) reported on bug 1743362.
1744244,2018-01-22 18:15:07 UTC,Setting automated-testing to 'Fix Released' based on the test results from the previous version (4.4.0-111.134).
1744259,2018-01-22 15:04:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536392"
1744259,2018-03-13 08:39:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/552437"
1744259,2018-06-15 09:21:57 UTC,"Change abandoned by Shubhendu Poothia (<email address hidden>) on branch: master
Review: https://review.openstack.org/552437
Reason: as V1 driver is being deprecated, this should be of no consequence."
1744259,2018-10-16 10:32:13 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/536392
Reason: Cleaning up changes that seem to be abandoned or are older than two months. If you think this was an error and the change is still relevant, please be free to restore it. Sorry for any inconvenience that I might have caused by this."
1744264,2018-01-19 09:55:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535695"
1744264,2018-07-31 06:52:53 UTC,"Change abandoned by feng.shengqin (<email address hidden>) on branch: master
Review: https://review.openstack.org/535695"
1744275,2020-09-18 01:19:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744275,2018-01-19 10:35:59 UTC,confirmed with ubuntu-mate 18.04
1744278,2018-01-19 17:06:45 UTC,"The problem is likely that the heat_init_spec.rb defines a lot of ""shared_examples_for"" but it never uses the companion ""it_should_behave_like"" construct. Metaphorically speaking, that's like defining a function but never calling it."
1744278,2018-01-19 10:56:18 UTC,"I think this is rather a rspec or ruby bug, we can't do much to fix that until those dependencies resolved"
1744298,2018-01-22 18:36:42 UTC,Setting automated-testing to 'Fix Released' based on the test results from the previous version (4.13.0-30.33~16.04.1).
1744298,2018-01-22 18:42:42 UTC,Setting regression-testing to 'Fix Released' based on test results from xenial/linux 4.13.0-31.34 (bug 1744294).
1744298,2018-01-22 19:14:18 UTC,This bug was fixed in the package linux-hwe - 4.13.0-31.34~16.04.1
1744298,2018-01-22 19:58:52 UTC,The package has been published and the bug is being set to Fix Released
1744305,2018-01-19 12:10:27 UTC,"StacktraceTop:
 set_filter (filter=0x55d8f8c41050 ""ip or ip6"") at capture/capctl.c:701
 on_filter_entry_changed (user_data=0x0, cbox=0x55d8f8cc1740) at pref_dialog.c:481
 confirm_changes () at pref_dialog.c:57
 on_ok_pref_button_clicked (button=<optimized out>, user_data=<optimized out>) at pref_dialog.c:438
 g_closure_invoke (closure=0x55d8f8d55f20, return_value=0x0, n_param_values=1, param_values=0x7fffdaa3a7f0, invocation_hint=0x7fffdaa3a770) at ../../../../gobject/gclosure.c:804"
1744309,2018-01-22 18:31:50 UTC,Setting regression-testing to 'Fix Released' based on test results from Trusty 3.13.0-141.190 tests (bug 1744308).
1744309,2018-01-22 19:48:13 UTC,The package has been published and the bug is being set to Fix Released
1744310,2018-01-31 13:55:49 UTC,"I've fond, that no neutron-l3-agent agent is deployed on compute nodes in case of VPNaaS option enabled. This is the reason, why instances has no connectivity to the outside world and floating IPs aren't accessible."
1744310,2018-04-04 21:50:01 UTC,"Did you enable ""enable_neutron_provider_networks"" as well in global.yaml file with dvr ?"
1744322,2018-10-03 08:31:25 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/607498"
1744322,2018-10-04 21:09:54 UTC,"Reviewed:  https://review.openstack.org/607498
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=8ff498ccb6c2f2894bfc70dfee930101411c276f
Submitter: Zuul
Branch:    stable/rocky"
1744322,2018-09-21 12:48:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604351"
1744322,2018-10-02 17:48:47 UTC,"Reviewed:  https://review.openstack.org/604351
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=18d22f1835e6949fa84f0bc44e28495de62d25f8
Submitter: Zuul
Branch:    master"
1744322,2018-03-26 09:21:10 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/556457"
1744322,2018-02-04 16:50:07 UTC,"Reviewed:  https://review.openstack.org/534826
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=bba2ec19bdbf7599d0322d0270c00a57b864fec2
Submitter: Zuul
Branch:    master"
1744322,2018-02-03 03:00:12 UTC,"Reviewed:  https://review.openstack.org/535295
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=a19d6185187e805ab6be4fc7522c18a9794f3680
Submitter: Zuul
Branch:    master"
1744322,2018-02-03 02:37:14 UTC,"Reviewed:  https://review.openstack.org/534828
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=1f4e2514791035df06ac1111b1b8f1ebe62d1f47
Submitter: Zuul
Branch:    master"
1744322,2018-03-27 03:04:14 UTC,"Reviewed:  https://review.openstack.org/556457
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=384e615e816d3ffaa022cfd22ff41d99e977f5be
Submitter: Zuul
Branch:    stable/pike"
1744325,2018-05-02 12:04:06 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1744325,2018-02-15 23:53:30 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1744325,2018-02-05 19:36:25 UTC,"Reviewed:  https://review.openstack.org/536904
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=83fd8ac0bfd3d9e5dd4ad48bfcb845d80095b845
Submitter: Zuul
Branch:    stable/ocata"
1744325,2018-01-30 20:01:41 UTC,"Reviewed:  https://review.openstack.org/536897
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=22a39b8f9b76d5f330a3f185e7d40f208a6a47f3
Submitter: Zuul
Branch:    stable/pike"
1744325,2018-01-29 16:56:28 UTC,https://review.openstack.org/#/c/538961/ is related.
1744325,2018-01-26 00:43:21 UTC,This issue was fixed in the openstack/nova 17.0.0.0b3 development milestone.
1744325,2018-01-23 18:53:59 UTC,This bug exists in newton but newton is EOL upstream so it won't be fixed there.
1744325,2018-01-23 17:03:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/536904"
1744325,2018-01-23 16:45:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/536897"
1744325,2018-01-22 16:09:04 UTC,"I wouldn't say this is critical. It's a change, yes, but it's similar to what we always had as a bug when trying to rebuild a volume-backed instance with a different image up until Queens when we finally made that an error in the API because it's not supported in the compute service. I think we can just mark the instance ERROR in this case and let the user rebuild the instance with a valid image to get it out of ERROR state, but just leave the instance properties as the API set them without trying to get the conductor manager code to roll everything back."
1744325,2018-01-22 09:19:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536268"
1744325,2018-01-22 04:07:29 UTC,I think we also need restore original image metadata and set server status to ERROR.
1744325,2018-01-19 15:47:59 UTC,That's IMHO a very critical bug that we need to tackle ASAP
1744325,2018-01-24 05:19:41 UTC,"Reviewed:  https://review.openstack.org/536268
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d03a890a34f632adc9a19a33c8a5aebbccec50e4
Submitter: Zuul
Branch:    master"
1744328,2018-02-05 18:53:41 UTC,This bug was fixed in the package nss - 2:3.35-2ubuntu2
1744328,2018-01-29 14:56:13 UTC,"I followed the suggestion to take a look at Fedora, and it really is public there."
1744328,2020-10-19 09:22:30 UTC,FYI since comment #6 not a lot happened in Debian other than other bugs being merged.
1744328,2018-01-30 09:06:35 UTC,"Discussion spun forward - TL;DR:
- we have time for the nss-pem changes and tjaalton will drive those in debian
- for our current need we might not even want to move the libs
  - but instead provide symlinks (least invasive change for now until Debian decided on our bug)"
1744328,2018-01-19 14:47:49 UTC,"From IRC discussion:
[13:20] <cpaelzer> xnox: hey I'd need your help/guidance on libnss that you touched recently
[13:20] <cpaelzer> it has headers like /usr/include/nss/hasht.h which are backed by a .so in a subdir /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
[13:20] <cpaelzer> those are usually not meant to be direct includes, but it has symbols for it and everything
[13:21] <cpaelzer> it currently breaks the change of a lib usage that is not in main to use nss for this instead
[13:21] <cpaelzer> so I wonder if that lib should maybe not be in the subpath, but actually directly in /usr/lib/x86_64-linux-gnu/
[13:22] <cpaelzer> xnox: slangasek pointed out that you touched it recently, so we had some hope you might have a hint on this
[13:22] <cpaelzer> as it seems not really to be ment for dlopen only (symbols/headers available ""normally"")
[13:23] <cpaelzer> I'm on sprint, so latency to reply is high, but it would be great to hear your insight on this
[13:24] <xnox> cpaelzer, i will look into it. It does seem odd.... unless like libnss.so itself knows how to dlopen extra things.
[13:24] <xnox> can't recall anything special around it, off the top of my head.
[13:27] <cpaelzer> xnox: thanks for taking a look
[13:28] <cpaelzer> xnox: if it is meant to be internal only ok, but if not making it properly public would be great
[14:55] <xnox> cpaelzer, i am failing to understand what it is; but on e.g. Fedora, they have a separate source package nss-softokn which does have binary packages nss-softokn-freebl[-devel] which does ship those libs as normal public libraries; they also have some dracut snippets to include those into initramfs....
[14:55] <xnox> they have .chk files and can be used in FIPS mode
[14:55] <xnox> not sure about /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so what that one is yet, as it does not appear to be anywhere.
[14:57] <xnox> oh maybe that one is in the base nss package, one sec."
1744328,2018-01-29 16:19:32 UTC,"Suggested a fix to Debian, but also to hear if there is any known background why it was split up that way.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888764"
1744328,2018-01-29 14:41:19 UTC,"For the block in proposed I proposed
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-mask-389-ds-base/+merge/336779"
1744328,2018-01-29 14:00:58 UTC,All archs fail like https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/3/389-ds-base/20171221_085018_38cf2@/log.gz
1744328,2018-01-29 14:00:33 UTC,"Whatever we do, there is one in proposed for a while already which blocks on autopkgtest of 389-ds-base."
1744328,2018-01-30 08:52:57 UTC,"It seems this has some (non encouraging) history:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855879
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732201"
1744330,2019-06-25 16:07:39 UTC,4.15 is in bionic.
1744333,2018-04-12 22:27:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744341,2020-02-05 16:52:18 UTC,Rebased branch pushed:
1744341,2018-11-19 18:18:19 UTC,"Michele, one reason we retain the copy maps for frozen holds is the maps are used to calculate hold queue position.  When the maps don't exist, the holds are ignored when calculating queue positions for holds in the same queue."
1744341,2020-02-05 16:36:53 UTC,See duplicate bug 1861719 for how this affects patrons viewing their suspended holds in the catalog.
1744341,2018-01-19 16:25:36 UTC,New targeter option and release notes pushed:
1744341,2018-01-19 16:04:11 UTC,"Jason, my only concern was requiring the hold targeter run longer, particularly since frozen holds don't *need* to be constantly retargeted.  If the consensus is it's worth it to avoid adding a new targeter option, I have no objections to always retargeting frozen holds."
1744341,2018-01-19 15:59:46 UTC,"Bill, I like the idea, but I have a question:"
1744341,2018-11-19 16:43:47 UTC,Here's another question related to this bug. Should suspended holds have copy maps at all?
1744343,2018-04-19 18:21:41 UTC,Partman is tripping up somehow:
1744349,2018-02-02 16:25:44 UTC,This is really twisting my brain.
1744349,2018-02-18 18:04:50 UTC,"OK, maybe we should just ignore this issue until we have a quotas-in-keystone implementation. :D"
1744359,2018-01-29 17:56:31 UTC,"Brian, is there anything remaining in neutron? You used ""Partial-Bug"" for a neutron fix."
1744359,2018-03-19 08:04:17 UTC,"Seems like this has been an issue in Neutron, please reopen if there is still some issue with devstack."
1744359,2018-01-29 22:09:53 UTC,"Akihiro - yes, I don't think there is more in neutron, I thought there was at the time or I would have used closes-bug instead.  We should now have slightly better logging in this area."
1744359,2018-01-27 22:36:20 UTC,"Reviewed:  https://review.openstack.org/536919
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f74b39c57dbb306dd3bb9a68cc44491d54b7988a
Submitter: Zuul
Branch:    stable/pike"
1744359,2018-01-19 19:42:27 UTC,"So I tested using log-tag in the haproxy conf file, and it does help differentiating things in /var/log/haproxy.log since all the haproxies will log there."
1744359,2018-01-22 22:10:56 UTC,"Reviewed:  https://review.openstack.org/535948
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=703ff85b8262997f209e7666396c5d430d3baa34
Submitter: Zuul
Branch:    master"
1744359,2018-01-19 21:22:10 UTC,I guess having haproxy prefix is backwards compatible enough to allow it to slip like that.
1744359,2018-01-19 20:56:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/535948"
1744359,2018-01-19 20:53:24 UTC,"So I think these are logged, they're just not where we expect them to be.  I noticed that when running journalctl in devstack:"
1744359,2018-01-23 18:22:11 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/536919"
1744361,2018-02-09 07:13:23 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1744361,2018-02-09 09:52:35 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/542748"
1744361,2018-02-09 09:10:27 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/542738"
1744361,2018-02-09 10:28:25 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/542767"
1744361,2018-02-09 05:18:56 UTC,"Reviewed:  https://review.openstack.org/541442
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aaf37a26d6caa124f0cc6c3fe21bfdf58ccb8517
Submitter: Zuul
Branch:    master"
1744361,2018-02-16 00:27:40 UTC,"Reviewed:  https://review.openstack.org/542738
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5a10047f9dd4383f6ec9046d392f26c93f8420d4
Submitter: Zuul
Branch:    stable/queens"
1744361,2018-02-28 18:29:14 UTC,"Reviewed:  https://review.openstack.org/542748
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e06ad602f3ef98c505e49078dd225dde2a79e2a1
Submitter: Zuul
Branch:    stable/pike"
1744361,2018-03-15 09:51:42 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/542767"
1744361,2018-05-02 12:03:43 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1744361,2018-02-15 23:53:21 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1744361,2018-02-06 20:39:48 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/541442"
1744361,2018-01-26 01:34:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/538103"
1744361,2018-02-04 22:15:18 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/540680"
1744361,2018-02-04 18:23:58 UTC,"Reviewed:  https://review.openstack.org/540555
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=83ffc76edd360929925fc4bb66e5dcbf8254a30e
Submitter: Zuul
Branch:    stable/pike"
1744361,2018-02-02 23:42:58 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/540555"
1744361,2018-02-02 23:23:59 UTC,"Reviewed:  https://review.openstack.org/540168
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=236bb54493385bcfe2034e8b0fd7a387fa66635a
Submitter: Zuul
Branch:    master"
1744361,2018-02-02 21:46:14 UTC,We'll also have to backport the nova change to stable/pike since we merged this which caused the regression:
1744361,2018-02-02 06:02:15 UTC,"Reviewed:  https://review.openstack.org/538103
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ea939b792279595e37b80fff3d44c1e712d4fc7
Submitter: Zuul
Branch:    master"
1744361,2018-02-01 22:30:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540168"
1744361,2018-02-01 22:21:00 UTC,I think I found the answer. It looks like this was already documented in our code in a different place [1]:
1744361,2018-02-01 20:40:01 UTC,"Looking at a new set of logs for the same bug today, I found that the message in n-cpu [1]:"
1744361,2018-01-26 01:52:56 UTC,"Unfortunately the log link from comment 0 is a ""File Not Found"" today because of zuul issues, but in examining the code I think what's happening is we're waiting for a plug event for a different vif['id'] than the one we're receiving from neutron."
1744361,2018-01-25 22:37:35 UTC,"nova-compute isn't ignoring the event due to the instance state, it's just logging the current state of the instance when it got the event."
1744361,2018-01-25 22:31:52 UTC,I wonder if this is related to https://review.openstack.org/#/c/400384/.
1744361,2018-02-05 23:45:17 UTC,"Reviewed:  https://review.openstack.org/540680
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9f9e0912101f28d4a3706b16f194b4f17ae60c2
Submitter: Zuul
Branch:    stable/ocata"
1744362,2020-04-28 03:45:58 UTC,"The root cause of the issue is hostname/DNS resolution fails for auth-URLs & few other service URLS (magnum,heat etc).
Generally while configuring the OpenStack services we use ""controller"" instead of the IP, like example:"
1744362,2018-01-22 06:20:49 UTC,"We should check and support configuring deploy_auth_url to public
Just for reference deploy_auth_url is being taken from here:- https://github.com/openstack/heat/blob/bdddeee60212627b3beed41ca5ef5be56fd05b50/heat/common/context.py#L222-L233"
1744362,2018-07-06 05:42:01 UTC,I had the same problem with a k8s cluster.
1744362,2018-11-21 20:50:17 UTC,This was fixed in here:
1744365,2020-04-25 13:36:07 UTC,seems to work ok in focal
1744370,2019-08-02 21:21:45 UTC,"Strongly related bug for 18.04 with an explanation of what is hanging but referencing plymouth's ""splash"" which this system doesn't use:"
1744370,2019-08-02 19:36:35 UTC,Just re-discovered my own report here whilst trying to solve another occurrence of the same issue 18 months later.
1744370,2018-01-19 19:06:11 UTC,apport information
1744370,2018-01-19 19:06:13 UTC,apport information
1744370,2018-01-19 19:06:12 UTC,apport information
1744370,2018-01-19 19:06:09 UTC,apport information
1744370,2018-01-19 19:06:16 UTC,apport information
1744370,2018-01-19 19:06:07 UTC,apport information
1744370,2018-01-19 19:05:59 UTC,apport information
1744370,2018-01-19 19:06:01 UTC,apport information
1744370,2018-01-19 19:06:02 UTC,apport information
1744370,2018-01-19 19:06:08 UTC,apport information
1744370,2018-01-19 19:06:05 UTC,apport information
1744370,2018-01-19 19:06:03 UTC,apport information
1744370,2018-01-19 19:06:06 UTC,apport information
1744374,2018-01-21 11:28:37 UTC,"So, we shouldn't actually be filling up disk very much, because
a) we can't talk to the database, so that isn't filling up
b) we should be rotating our log files to a maximum size."
1744375,2018-01-19 20:01:45 UTC,Might be able to enhance slo to accept some content-md5 query param -- have it
1744379,2018-01-19 20:00:08 UTC,This change was made by a bot.
1744379,2018-01-22 20:16:30 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1744379,2018-01-23 00:39:48 UTC,"> Did this issue start happening after an update/upgrade?
"
1744379,2018-01-24 09:40:55 UTC,"I tried kernel 4.15.0-rc9 and had the same kind of hard lockup. The system wouldn't react to mouse or keypresses after some idle time. The log is attached (the kernel was upgraded on Jan 24-th). There are many errors about soft lockups in the log, although the backtraces are different from 4.13."
1744379,2018-01-24 09:42:12 UTC,Is it possible that the lockups are caused by the buggy microcode update from Intel? Did Canonical revert the microcode update?
1744379,2018-01-24 19:51:29 UTC,"The errors in the kernel log don't appear with kernel version 4.10.17. However, I still get lockups with that kernel as well."
1744379,2018-01-25 09:52:14 UTC,"Just for the record, I have found the problem that caused the lockups. It was the nvidia driver ForceCompositionPipeline parameter in xorg.conf. Without it the hangs no longer happen, but the warnings are still present in the log."
1744380,2018-04-27 22:05:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744386,2019-05-23 21:53:25 UTC,I've now backported Jane's patch to rel_3_2 and rel_3_1. Thanks!
1744386,2019-04-08 20:15:18 UTC,Pushed to master for great justice.  Thanks Jane!
1744386,2018-06-15 19:57:38 UTC,Here's the new bug I created for the sorting of entries within each stat cat dropdown: bug #1777184
1744386,2019-04-09 14:51:55 UTC,"I updated the search to sort first by library, then by statistical category, then sort entires within the categories."
1744386,2018-06-15 18:41:27 UTC,"I actually interpreted this bug to be about the contents of each stat cat dropdown, which I guess are technically the stat cat ""entries"".  So I see two separate issues here:"
1744386,2018-01-22 16:57:52 UTC,Confirmed in EG 3.0.  It is preferable that the order of statistical categories in the web client replicate that of the xul client.
1744386,2018-05-20 16:11:30 UTC,Screenshot from my branch
1744386,2018-05-20 16:10:56 UTC,I created a branch to fix this here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/sandbergja/lp1744386_alphabetize_stat_cats_in_volcopy
1744386,2018-06-15 19:29:57 UTC,It was about the order of stat cats in each dropdown
1744389,2018-05-22 18:44:37 UTC,Tested on master sandbox. Only the Leader is showing.
1744389,2018-06-26 17:46:05 UTC,Confirmed in 3.1
1744390,2018-04-03 19:47:56 UTC,"To clarify, PINES system libraries have headquarter libraries and subordinate branches. Since cataloging occurs at HQ libraries, most PINES catalogers use workstations assigned to the HQ library. While I refer to HQ above, it is better to say workstation library."
1744393,2018-01-22 17:52:28 UTC,"Percona can't auto-restore from a all-node power failure, a manual intervention is needed."
1744393,2018-08-30 01:32:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597969"
1744393,2019-07-10 19:05:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670163"
1744393,2019-07-11 15:00:24 UTC,"Reviewed:  https://review.opendev.org/670163
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=b97a0971c22f129b71674a22a65080a65c96af76
Submitter: Zuul
Branch:    master"
1744393,2019-07-19 15:21:48 UTC,"Reviewed:  https://review.opendev.org/670675
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=b8c2213dfbd4ae417be95a8ce1b1c973eee9e55c
Submitter: Zuul
Branch:    master"
1744393,2020-07-13 14:13:01 UTC,Since the action patch is landed but this LP is being kept open i'l' clear the current owner since it doesn't actually have one for the remaining tasks.
1744393,2021-02-23 17:05:50 UTC,"Setting to triaged; it's actually had work done with it, and is blocked on xenial packages at the moment.  This bug may eventually time-out on xenial."
1744393,2019-07-12 23:20:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670675"
1744398,2018-01-19 22:30:06 UTC,This change was made by a bot.
1744402,2018-06-18 23:45:18 UTC,"Reviewed:  https://review.openstack.org/573621
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=92a103bdbaaab7bb31dcac6711a8364ca38a2397
Submitter: Zuul
Branch:    stable/queens"
1744402,2018-06-18 23:45:09 UTC,"Reviewed:  https://review.openstack.org/573624
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e8a9cc1ea9d058871ef108b72b7c58e81f9003d8
Submitter: Zuul
Branch:    stable/pike"
1744402,2018-06-18 23:44:59 UTC,"Reviewed:  https://review.openstack.org/573625
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=69cab95e0204c1615f04c6bb4995668edab04f10
Submitter: Zuul
Branch:    stable/ocata"
1744402,2018-06-08 08:41:38 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/573624"
1744402,2018-06-08 08:42:08 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/573625"
1744402,2018-04-04 10:19:00 UTC,"Looks that it happens again: http://logs.openstack.org/22/557122/4/check/neutron-fullstack/185813b/logs/testr_results.html.gz
I will investigate there"
1744402,2018-04-29 17:15:11 UTC,"No hits in last few weeks: http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C%22neutron-fullstack%5C%22%20AND%20message%3A%5C%22hasn't%20been%20spawned%20in%2020%20seconds%5C%22
I will close this bug report now"
1744402,2018-02-06 11:25:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/541242"
1744402,2018-02-07 05:07:40 UTC,"Reviewed:  https://review.openstack.org/541242
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=685596f89c02711410bd6b650a12264ca99145fe
Submitter: Zuul
Branch:    master"
1744402,2018-06-08 08:40:42 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/573621"
1744402,2018-03-25 08:46:30 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/556155"
1744402,2018-03-26 16:18:37 UTC,"Reviewed:  https://review.openstack.org/556155
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1e49eab25080ff82002604a8f38eafbfa9a4f9b9
Submitter: Zuul
Branch:    master"
1744402,2018-03-25 08:42:24 UTC,After unmark this test as unstable it starts failing from time to time again. For example: http://logs.openstack.org/34/555834/3/check/neutron-fullstack/b74983d/logs/testr_results.html.gz
1744422,2018-01-20 16:29:30 UTC,What happens if you use a different font?
1744422,2018-01-23 00:23:17 UTC,"I tried several fonts: sans-serif, Times, Times New Roman, Courier. All show the same behavior."
1744422,2018-01-23 02:25:26 UTC,"I suspect that Times etc. don't contain the anchor at all, you can check this in the glyphs list or in the font viewer software of your choice. If a font does not contain a character, the fallback font is used. Perhaps the macports version uses a different fallback font..."
1744430,2018-01-25 08:44:57 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3773
1744432,2018-01-20 06:12:12 UTC,Initial investigation reveals that network_segments has been deleted before calling delete_network_postcommit.
1744443,2018-01-25 10:28:30 UTC,"Documentation update is more than sufficient, instead of code change. Will propose it when having spare cycles."
1744443,2018-01-25 09:56:54 UTC,Most configuration options assume you're not running with apparmor enforcing (as most of then pre-date the introduction of this feature).
1744443,2018-01-20 10:17:34 UTC,"I didn't notice the restriction, since I somehow used /srv/ceph by nature. But this time I just wanted to use some generic names (/srv/storage) since some of the bcache mount points are used for Swift."
1744445,2018-01-20 10:21:33 UTC,"thank you
is it possible to having contact in dutch lagues"
1744449,2020-06-15 05:50:19 UTC,"Please explain what kind of problem you are experiencing, if you are still experiencing any problems at all."
1744449,2020-08-15 04:17:14 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1744455,2018-12-12 07:13:10 UTC,"try  log in database ，use nova_api ,DELETE from resource_providers where uuid='5841aceb-452b-44b2-b96d-653c394a543c'！"
1744455,2019-03-17 23:38:07 UTC,There're constraint on one of the columns... this will fail.
1744457,2019-10-18 18:29:12 UTC,Reason: the Debian policy
1744457,2019-10-18 16:38:42 UTC,"Alternatively, systemd-cron could add a Provides: cron, which is what bcron does."
1744457,2019-10-18 16:20:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744457,2019-10-18 16:37:41 UTC,"ubuntu-standard should depend on cron-daemon (a virtual package provided by cron, bcron, systemd-cron), instead of depending on cron directly."
1744459,2018-08-10 19:55:24 UTC,-- GitLab Migration Automatic Message --
1744459,2018-01-20 20:24:17 UTC,"Insofar as this may be considered a bug instead of a feature, it is a bug in either your window manager, Wine, or Steam. There's nothing xscreensaver can do about it."
1744459,2018-01-21 14:02:27 UTC,On locking the screen with XScreenSaver I noticed that a popup window from a chat was able to show up and thus leaking private information. On reporting this against XScreenSaver it seems that the X-Server does not provide the ability to uniquely claim the top drawing area in a way that all other applications can't draw on top of it anymore to counter such issues.
1744459,2018-01-21 14:04:04 UTC,That is unfortunate that there is currently no way to do this as I consider this leaking of private information after locking the screen as a security issue. But I think this needs to be solved by the X-Server instead so I have created a feature request there: https://bugs.freedesktop.org/show_bug.cgi?id=104715
1744465,2018-01-20 20:05:27 UTC,This bug has been verified upstream.
1744465,2018-08-29 03:06:14 UTC,"Upstream bug report now showing as ""RESOLVED FIXED""
Cannot check with reporter as no longer uses LP.
Tested Ok in Ubuntu 18.04 and Firefox 61.
Marking ""Fixed Released"" to close."
1744472,2018-01-20 16:22:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1744472,2018-01-20 21:07:57 UTC,Added faulty package
1744479,2018-01-20 16:41:30 UTC,"Why did searches not find the upstream bug for me. It would have saved a lot of time:
https://github.com/hashicorp/vagrant/issues/8250"
1744481,2018-01-20 19:09:17 UTC,"I know it's not a bug fix, but - could this be backported? It's something nice and small :)"
1744481,2018-01-20 23:45:49 UTC,Backporting sounds straightforward.
1744481,2018-01-21 00:21:56 UTC,"YES! (had that idea, too, but thought it wasn't possible due to some restriction - so it does not really need to add up to 360 with an integer number of steps?)"
1744481,2018-01-21 03:15:58 UTC,I'm with the combo box idea. There might be people who might want to put in values other than what's listed.
1744481,2018-01-21 05:12:10 UTC,"Actually, I have a better idea, can we have such a combo box that it'll be easily accessible within Inkscape window without going into preference?"
1744481,2018-01-21 19:39:22 UTC,"Can someone from the devs comment on the '360° needs to be divisible by the number' thing? Is that a hard requirement for some reason, or is it just there because it makes the most sense (I tend to agree, because that way, you have a way to return to a fixed state - but people who change it to something that doesn't fit might also be able to add the numbers up themselves....)"
1744481,2018-01-21 19:48:34 UTC,"the value stored in the prefs is currently an integer that is ""180°/angle"" but it can be changed to a float, there are just 2 dozen places where to fix it."
1744481,2018-01-20 18:02:22 UTC,"Well, indeed."
1744494,2019-02-19 15:56:58 UTC,We were encountering the same issue recently in openstack-ansible queens.  Looks like it was fixed in https://bugs.launchpad.net/glance-store/+bug/1606268 in master and rocky.
1744510,2018-01-22 20:08:57 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1744510,2018-01-22 03:30:10 UTC,This change was made by a bot.
1744510,2018-05-08 10:05:00 UTC,"> On May 8, 2018, at 5:42 PM, Jonathan Kamens <email address hidden>
> wrote:
>
>> Does the mouse movement work again after you click its button?
>
> No.
>
> Do you think I am an idiot?
No. It's quite normal for a runtime suspended USB mouse.
"
1744510,2018-01-22 03:14:47 UTC,"This sounds like a kernel problem, and at least very likely not caused by Xorg. So reassigning to the kernel."
1744510,2018-05-08 05:15:08 UTC,Does the mouse movement work again after you click its button?
1744510,2018-04-19 12:05:29 UTC,"1) Just tested bionic, same behavior."
1744510,2018-05-08 09:42:47 UTC,">Does the mouse movement work again after you click its button?
"
1744510,2018-04-18 12:30:09 UTC,This change was made by a bot.
1744510,2018-01-23 14:21:30 UTC,"I am using the nvidia driver for my graphics card. It sounds like I can't do that with an upstream kernel build? Is that correct? Well my X server automatically use the open-source Nouveau drivers if the nvidia driver isn't in the kernel, or do I need to reconfigure something manually?"
1744510,2018-03-25 04:17:38 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1744510,2018-04-18 16:45:39 UTC,"I can see
[   24.500827] hid-generic 0003:1BCF:0535.0005: input,hiddev1,hidraw3: USB HID v1.00 Mouse [2.4GHZ  RF ONLY MOUSE] on usb-0000:00:14.0-8/input1"
1744510,2018-04-18 12:07:26 UTC,Please help me with the test you want me to do and I will gladly do it.
1744510,2018-04-18 12:02:48 UTC,I asked for assistance with the test you asked me to perform back in January. Can you help?
1744515,2018-01-21 00:52:59 UTC,"This also affects the 'Unity' login option, which uses compiz."
1744515,2018-01-21 02:31:07 UTC,"The 'Show Repaint' plugin in compiz showed that most of the screen was not getting repainted. Disabling 'Framebuffer object' under OpenGL, in ccsm (CompizConfig Settings Manager), caused the whole screen to be repainted but CPU usage of compiz stayed the same. If Workarounds > 'Force full screen redraws (buffer swap) on repaint' was enabled, CPU usage without Framebuffer object was the same, but with both on, CPU usage of compiz was ~3% higher (from 13% to 16% with CPUs at lowest frequency)."
1744515,2018-01-21 08:02:59 UTC,"Problem does not happen when booting from linux kernel 4.8.0-34-generic; CPU usage is slightly higher than Metacity, no significant kworker threads."
1744515,2018-04-24 03:44:23 UTC,"Confirmed to not be (just) a compiz bug because it also affects Wayland, which doesn't use compiz. Using Bionic beta with kernel 4.15.0-15-generic."
1744516,2018-01-21 13:38:56 UTC,Update: After installing manually this kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.14-xenial/ problem was solved.
1744520,2018-01-21 08:27:33 UTC,I can't reproduce it. But most likely a graphics/xorg issue.
1744530,2018-01-24 22:23:31 UTC,Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1472
1744538,2018-01-21 12:43:04 UTC,"It might be more accurate to revise the description to ""one node paths having no size..."""
1744538,2018-01-21 11:39:32 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06),
using the attached file"
1744538,2018-01-21 07:35:35 UTC,"I guess the better fix is for Inkscape to not keep 1-node paths around, but I'm not sure."
1744543,2018-01-21 08:30:07 UTC,This change was made by a bot.
1744543,2018-01-22 20:13:32 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1744543,2018-01-23 00:40:02 UTC,"Tested, and if anything the %CPU of kworker threads is even higher, often staying around 65% in 'top'."
1744544,2020-03-20 04:37:28 UTC,"Please describe the kind of problem you are, or were, experiencing."
1744544,2020-05-20 04:17:16 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1744546,2018-01-29 20:48:17 UTC,OK very good. The last release of the kernel resolve the problem of boot.
1744546,2018-01-29 21:53:59 UTC,Sorry.
1744546,2018-01-29 20:57:47 UTC,I precise that I boot on the daily ubuntu 18.04 with the release kernel 4.15
1744546,2018-01-27 10:35:01 UTC,kernel-bug-exists-upstream
1744546,2018-01-22 20:12:53 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1744546,2018-01-21 12:33:14 UTC,"I precise that I have a MSI GL62 7RD. The problem is known for many users.
Example : https://askubuntu.com/questions/991653/ubuntu-17-10-wont-install-on-msi-gl62m-7rdx-laptop"
1744546,2018-01-21 12:29:46 UTC,I can't access to the terminal. The system is blocked.
1744546,2018-01-21 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1744546,2018-01-27 10:26:42 UTC,"With the last kernel (4.15 rc9) I no longer have the message of Error ""The bug is tpm_crb MSFT0101:00: [firmware bug] acpi region does not cover..."""
1744554,2019-05-08 14:16:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744562,2018-01-21 14:43:20 UTC,"Another example is to set UEFI as the default boot mode since some models have BIOS(Legacy) boot mode by default. Plus, boot-order=PXE."
1744562,2018-01-25 10:31:17 UTC,"Hey Nobuto,"
1744562,2019-09-19 14:53:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1744564,2019-07-21 11:29:01 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1744564,2019-09-20 04:17:50 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1744572,2018-01-21 20:58:08 UTC,"Bonjour,"
1744579,2019-07-09 01:41:27 UTC,"Since the bug was filed a lot of work continues to be done in the area.
Right now, there is not one TestUpdateApplicationsUnits but 3:"
1744582,2019-02-06 13:29:08 UTC,"/usr/bin/ptrepack in python3-tables tries to use python2 (/usr/bin/python), which will not work if python-tables is not installed. Same for pt2to3, ptdump and pttree. nctoh5 is missing, though the man page is present. It's also absent when I install to a 3.7 virtualenv. The other commands are present and run with python3 in the VE."
1744582,2018-05-29 07:20:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744582,2019-02-11 21:02:27 UTC,In the current package version 3.4.4-2 (unreleased Ubuntu 19.04) /usr/bin/pt2to3 and /usr/bin/ptrepack use python3.
1744584,2018-01-22 13:28:38 UTC,I think it would be reasonable to add an Always-on exclude of ~/snap/*/*/.cache maybe. Doesn’t help for snaps that put their cache somewhere else... but that will get the majority of good actors.
1744584,2018-01-22 14:26:53 UTC,The ~/snap/*/*/ structure is currently hardcoded and I'm not aware that any package changes this. So the idea of always excluding ~/snap/*/*/.cache is sensible.
1744584,2018-01-22 16:04:05 UTC,"mvo, that’s good. But I’m also leery of assuming what apps do with their own space. Not everyone is going to use .cache. But I’m sure that gets the majority."
1744584,2018-01-24 03:02:40 UTC,"OK, I've committed a patch in upstream master that excludes ~/snap/*/*/.cache and uploaded a cherry-picked patch to bionic."
1744584,2018-01-27 12:52:56 UTC,Michael thank you very much. This is so awesome. It will simplify significantly using snaps as currently we need to pay careful look whenever they are updated to exclude them from Deja Dup.
1744584,2018-12-28 20:44:13 UTC,This has been released upstream with version 38.0
1744584,2019-10-15 11:18:55 UTC,I'm closing the snapd side of the issue. Thank you for improving deja-dup everyone!
1744586,2018-01-21 18:46:29 UTC,Solution:
1744587,2018-02-03 21:53:46 UTC,"I was having all kinds of problems installing hplip from source.
I upgrade my distribution using sudo do-release-upgrade -d"
1744587,2018-02-03 21:54:28 UTC,Feel free to close this.
1744587,2018-01-29 16:59:37 UTC,"> Anyone have any ideas on how I can install ........
"
1744587,2018-02-01 10:24:55 UTC,"Hi Edward,"
1744587,2018-01-21 20:21:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1744599,2018-02-21 01:51:32 UTC,This bug was fixed in the package docker.io - 17.03.2-0ubuntu3
1744599,2018-07-18 10:55:03 UTC,This bug was fixed in the package docker.io - 17.03.2-0ubuntu2~16.04.1
1744599,2018-01-22 17:20:35 UTC,Thanks for taking the time to file a bug!
1744599,2018-01-22 18:49:08 UTC,"This was fixed upstream in 17.04+ (https://github.com/docker/docker/pull/30519) -- I could've sworn we backported the patch, but apparently not!  (I'll go work on getting that applied now)"
1744603,2018-01-21 22:02:45 UTC,"Sorry forgot to add, this is a new install of 17.10 on 1/20/2017"
1744606,2018-01-24 15:39:45 UTC,"I think this might be a good idea, but what is the solution when the time shew is way off?"
1744606,2019-09-19 15:04:12 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1744608,2018-01-22 00:21:32 UTC,"I've done some more research and came to a better understanding of the 'on' syntax.
Looks like post 2.38 the 'on' keyword is going to be supported for 'sources'.
Based on a closer examination of that work."
1744608,2018-01-22 22:05:28 UTC,I was pondering my suggested enhancement overnight and it occurs to me that the whole 'on' syntax is a little restrictive.
1744608,2018-01-22 22:43:12 UTC,"We're slowing adding that syntax to more and more properties. Today it's limited to build- and stage-packages, as well as source, with more to come. Note however that the `environment` keyword is currently just a passthrough to snapd, so we'll need to process that a bit more if we enable the grammar there."
1744608,2018-01-22 23:21:24 UTC,I don't quite see why this would affect snapd.
1744613,2018-11-03 08:35:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744616,2018-01-22 01:04:53 UTC,Please see https://forum.snapcraft.io/t/running-systemd-commands-inside-a-snap/3591/3 for a little more context
1744616,2018-05-07 09:44:09 UTC,"I have confirmed this and described why this happens on the forum. Not sure what the solution would be though (apart from patching systemd but even then, unsure how exactly)."
1744619,2019-05-17 09:32:55 UTC,This bug was fixed in the package unity-control-center - 15.04.0+19.04.20190209-0ubuntu4
1744619,2019-03-05 12:12:18 UTC,"I had the branch, I will rebase and open a merge-request later."
1744619,2019-03-04 15:02:46 UTC,What's the status or porting unity-control-center? We are going to drop that deprecated lib next cycle
1744619,2018-04-11 14:15:25 UTC,Debian's network-manager-applet 1.8.10-4 has dropped libnm-gtk-dev and libnm-gtk0.
1744619,2018-03-04 23:01:01 UTC,I am letting all of these migrate now except for openvpn. There are reports in Debian of problems with the new openvpn version so I want someone that uses that to check it first.
1744619,2018-02-26 14:48:34 UTC,I had to let network-manager-l2tp and -pp2p migrate because it was blocking NetworkManager 1.10 from bionic.
1744619,2018-04-18 21:53:26 UTC,And Debian is now dropping libnm-util-dev and libnm-glib-dev.
1744619,2018-02-21 18:35:52 UTC,"Khurshid, any progress on unity-control-center?"
1744619,2018-02-23 10:33:46 UTC,I haven't finished porting but close. But we don't have time for testing.
1744619,2018-01-23 15:54:15 UTC,That was discussed on IRC and there are some details in the upstream report (https://bugzilla.gnome.org/show_bug.cgi?id=779776)
1744619,2018-01-23 15:55:08 UTC,"Changing the title to reflect what I think the changeset is about, let me know if you think it's not an accurate summary"
1744619,2018-03-05 14:00:38 UTC,"Actually, it appears like the Debian problem was because some users hadn't updated their gnome-shell yet. Since Ubuntu 18.04 already has the updated gnome-shell, let's let this last plugin in now."
1744619,2018-02-15 18:13:58 UTC,"Khurshid, I apologize for changing this bug without adding a comment to explain myself."
1744619,2018-02-15 22:23:03 UTC,Thanks. I will wait for these transitions to finish first.
1744619,2018-02-15 17:44:25 UTC,"Jeremy, why u-c-c is not affected any more? If we want to compile u-c-c with lbnma we will still have to port it along other nertwork-manager-* packages."
1744619,2018-02-15 22:35:00 UTC,You're welcome to work on this bug before those transitions happen. :)
1744620,2018-01-22 14:52:19 UTC,Is PXE booting with ipv6 failing for you?
1744620,2018-01-23 14:21:11 UTC,"Yes, I have tested ironic over one IPv6 network, it failed in PXE booting. When I change dhcp options to bootfile-url which will be updated to neutron port, it boots ok."
1744620,2018-01-23 15:03:58 UTC,"Thanks zhengyong,"
1744620,2018-03-14 12:58:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/552897"
1744620,2019-01-11 13:09:32 UTC,"Change abandoned by Harald Jensås (<email address hidden>) on branch: master
Review: https://review.openstack.org/552897
Reason: I have not had time to look into this for a long time."
1744622,2019-04-01 06:55:20 UTC,"Change abandoned by zhengyong (zhengy23@163.com) on branch: master
Review: https://review.openstack.org/540649"
1744622,2018-01-23 14:01:02 UTC,"Actually it raises InvalidIPv4Address exception before I chang code in https://github.com/openstack/ironic/blob/master/ironic/dhcp/neutron.py#L157 to Line 163
which is:
if ip_address:
    if netutils.is_valid_ipv4(ip_address):
        return ip_address
    else:
        LOG.error(""Neutron returned invalid IPv4 address %s."",
                   ip_address)
        raise exception.InvalidIPv4Address(ip_address=ip_address)"
1744622,2018-01-22 16:59:40 UTC,"I would've expected this situation to raise an InvalidIPv4Address exception [0]. Not sure why it didn't. That aside, it looks like there indeed does need to be some modification to allow for IPv6 when using PXE and UEFI. [1]"
1744622,2018-02-04 14:01:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540649"
1744625,2018-01-26 00:16:17 UTC,This issue was fixed in the openstack/freezer-web-ui 6.0.0.0b3 development milestone.
1744625,2018-01-22 05:10:05 UTC,"It looks like a bug about a horizon plugin. Which horizon plugin provides ""Disaster Recovery dashboard""?"
1744629,2019-06-28 14:25:59 UTC,"FWIW, here is a list of ""stylish"" skip links: https://knowbility.org/blog/2019/skip-links-gallery/"
1744639,2018-01-22 16:19:34 UTC,"The following patches were skipped because they were already applied:
 * ext4: fix data exposure after a crash
 * bpf: don't let ldimm64 leak map addresses on unprivileged
 * xen-blkback: don't leak stack data via response ring
 * sctp: do not peel off an assoc from one netns to another one
 * scsi: lpfc: Add missing memory barrier"
1744639,2018-01-22 16:20:20 UTC,"The following patch had to be applied manually (using 'patch') since 'git am' didn't work - however, no code changes were required:
 * igb: close/suspend race in netif_device_detach"
1744639,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1744640,2018-01-30 05:41:36 UTC,"Hi Mike,"
1744641,2018-09-21 01:49:06 UTC,"I've had issues with this before. We should verify all 3 platforms can suspend/resume gracefully, ideally handling reconnecting to audio interfaces, controllers, broadcasting, etc."
1744642,2018-01-24 09:49:11 UTC,Hello! There are OpenStack requirements that define filtering by tags: https://specs.openstack.org/openstack/api-wg/guidelines/tags.html#filtering-and-searching-by-tags
1744649,2018-01-24 01:18:57 UTC,Same as bug https://bugs.launchpad.net/devstack/+bug/1540328.
1744657,2018-01-22 08:59:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744657,2018-01-22 07:40:37 UTC,"StacktraceTop:
 XGetScreenSaver (dpy=0x55c1a201a900, timeout=timeout@entry=0x7ffe362832d8, interval=interval@entry=0x7ffe362832dc, prefer_blanking=prefer_blanking@entry=0x7ffe362832e0, allow_exp=allow_exp@entry=0x7ffe362832e4) at ../../src/GetSSaver.c:44
 disable_builtin_screensaver (unblank_screen=0, watcher=<error reading variable: value has been optimized out>) at gs-watcher-x11.c:539
 watchdog_timer (watcher=<error reading variable: value has been optimized out>) at gs-watcher-x11.c:609
 g_timeout_dispatch (source=source@entry=0x55c1a21638d0, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4633
 g_main_dispatch (context=0x55c1a2024fd0) at ../../../../glib/gmain.c:3148"
1744657,2018-01-22 17:10:46 UTC,Just got the same error again.
1744669,2018-01-23 19:03:01 UTC,Further to this snapcraft cleanbuild doesn't work either. I'm not sure how I am supposed to use this on a mac.
1744669,2018-01-25 15:27:24 UTC,"Do you have the ""lxc"" installed? The client is needed, just like on Linux-based systems."
1744670,2019-08-12 12:47:10 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/675891"
1744670,2021-02-04 10:42:13 UTC,This issue was fixed in the openstack/horizon 16.2.1 release.
1744670,2020-10-15 12:07:08 UTC,"Reviewed:  https://review.opendev.org/710174
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=68d4c5e78db61ea401ee89c84a69676e26a636a1
Submitter: Zuul
Branch:    stable/train"
1744670,2020-02-27 02:55:27 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/710174"
1744670,2018-10-24 19:15:24 UTC,I am not sure what is happening here that is causing the certificate information to not be passed down. It seems like cinderclient is using requests directly (in Pike). And whatever else is calling keystoneauth is not passing the cert value to keystoneauth. If the cert values are not passed to keystone auth it is not possible for KSA to understand where to get the cert information from.
1744670,2019-11-19 19:25:11 UTC,"Reviewed:  https://review.opendev.org/675894
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=285c51f7e1b27a786fa9684abdc489998285b4e2
Submitter: Zuul
Branch:    master"
1744670,2019-12-16 19:10:26 UTC,This issue was fixed in the openstack/horizon 17.1.0 release.
1744670,2019-08-12 13:21:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675894"
1744670,2019-09-05 14:14:28 UTC,"Reviewed:  https://review.opendev.org/675891
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=4a3a2c3c9a89ccff4e64d3da96de5b0af4303840
Submitter: Zuul
Branch:    master"
1744689,2018-02-24 02:31:11 UTC,"@Denis
    Yes, all nodes have enough free disk space. We find the issue key is that all nodes will send some service logs to Fuel node. If env have too many nodes, Fuel node can not process so many service logs."
1744689,2018-02-07 14:12:29 UTC,Is there enough free disk space on nodes? On Fuel Master node?
1744692,2019-09-27 09:04:01 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1744692,2020-01-06 10:24:39 UTC,This issue was fixed in the openstack/cinder 13.0.8 release.
1744692,2019-11-28 15:14:02 UTC,This appears to be breaking boot from volume:
1744692,2019-10-24 14:30:12 UTC,This issue was fixed in the openstack/cinder 12.0.10 release.
1744692,2019-10-11 14:05:29 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/688131"
1744692,2019-10-07 21:23:39 UTC,"Reviewed:  https://review.opendev.org/682097
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b886d093d782301829afb42e6476b0f5a4678fba
Submitter: Zuul
Branch:    stable/rocky"
1744692,2019-10-04 08:51:52 UTC,This issue was fixed in the openstack/cinder 14.0.2 release.
1744692,2019-09-13 16:02:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/682097"
1744692,2019-12-02 14:57:38 UTC,I think comment #18 comes from a downstream patched up version of queens carrying patches that aren't on upstream queens.  The same failure may or may not reproduce on upstream Cinder.
1744692,2019-09-11 15:05:10 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/681515"
1744692,2018-05-26 19:37:17 UTC,"I have got this problem too. NFS storage, Queens, openstack-cinder-12.0.1-1.el7.noarch"
1744692,2019-09-12 15:35:36 UTC,"Reviewed:  https://review.opendev.org/681515
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=247c6607156da6f4403c4826c7d2e09720c43e8d
Submitter: Zuul
Branch:    stable/stein"
1744692,2018-05-28 07:18:25 UTC,"@livelace: Not sure it makes much of a diff but you might add your me too to the bug heat tracker (top of page, fire icon)"
1744692,2018-05-28 12:43:12 UTC,"By searching the cinder code, I found the snapshot object that is being used in the method is a temporary object made via namedtuple, and that means the OVO attribute '_context' is missing since it's made [1].  I don't have an environment by hand, not sure this change can fix the error."
1744692,2018-05-28 13:27:10 UTC,"@tommylike: I did a quick&dirty test run, collections stumbled over ValueError: Field names cannot start with an underscore: '_context' .
I should be able to take a closer look at this tomorrow..."
1744692,2019-10-14 20:57:47 UTC,"Reviewed:  https://review.opendev.org/688131
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=772897cad777716e55216f59d0e11ec191b31c80
Submitter: Zuul
Branch:    stable/queens"
1744692,2018-05-29 10:19:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/570885"
1744692,2018-05-29 10:20:57 UTC,@tommylike: I created a change at https://review.openstack.org/#/c/570885/ for bringing this forward. Please see my comments in that change.
1744692,2019-09-05 00:08:09 UTC,"Reviewed:  https://review.opendev.org/570885
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=78f2101fc5a84e81132e6c2adc89cfe681018d77
Submitter: Zuul
Branch:    master"
1744692,2018-05-29 01:35:51 UTC,"Thanks, @Silvan Kaiser, if that so, we still can get the ``_context`` attribute via snapshot.volume._context。"
1744699,2019-06-30 18:47:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744701,2018-01-22 11:47:43 UTC,"Although，the scene that running unit test in the same node with the swift installation is unfrequent.But I think if we do some improvements to the unit test cases ,we will save a little time of those guys who encounter this situation."
1744701,2018-01-22 18:44:35 UTC,It's feasible to track down any current tests that coincidentally call dump_recon_cache and make sure the test properly configures recon_cache_path to a tempdir...
1744716,2018-01-22 15:03:56 UTC,Perhaps the issue is in this line: https://github.com/openstack/magnum/blob/stable/ocata/magnum/drivers/common/templates/kubernetes/fragments/configure-kubernetes-minion.sh#L51
1744719,2018-12-12 14:33:19 UTC,That's still an issue https://errors.ubuntu.com/problem/f31496b5c1b8747327b33133de1fb483c0abce0b
1744719,2018-01-22 14:32:27 UTC,"StacktraceTop:
 g_dbus_object_get_interface (object=0x0, interface_name=0x7fd2ca0971c0 ""org.gnome.OnlineAccounts.Account"") at ../../../../gio/gdbusobject.c:149
 goa_object_peek_account (object=0x0) at goa-generated.c:24246
 on_notification_closed (button=button@entry=0x0, self=0x56284c3587a0, self@entry=<error reading variable: value has been optimized out>) at cc-online-accounts-panel.c:911
 on_remove_account_timeout (user_data=<error reading variable: value has been optimized out>) at cc-online-accounts-panel.c:937
 g_timeout_dispatch (source=source@entry=0x56284cddd1f0, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4633"
1744728,2018-01-22 16:36:06 UTC,"Thank you for the bug.
I think this is more an usability issue than defect.
The drop down menu is only a filter to display the files.
Did you try to explicited name the file *.m3u8"
1744735,2018-02-05 06:45:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744738,2018-01-22 16:06:57 UTC,jdstrand suspects it might be a missing /var/lib/snapd/apparmor/snap-confine.d directory. If that dir is missing inside the container the profile fails to load.
1744738,2018-01-22 16:13:58 UTC,The other line of investigation is https://irclogs.ubuntu.com/2018/01/09/%23ubuntu-devel.html#t03:34
1744738,2018-01-31 15:18:08 UTC,"FYI, https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1746463 is the bug for https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1744738/comments/2"
1744758,2018-02-01 14:08:11 UTC,"This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.6~cloud1
---------------"
1744758,2018-02-01 14:08:11 UTC,The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744758,2018-02-01 14:05:07 UTC,Wrong paste for development charms above.
1744758,2018-02-01 14:03:47 UTC,Regression testing on xenial-ocata-proposed was successful:
1744758,2018-01-24 12:35:43 UTC,"\o/ Great, thanks for verifying Lee. This needs to spend a little bit more time in proposed and get some regression testing and then we'll promote to ocata-updates."
1744758,2018-01-24 08:54:37 UTC,"Thanks Corey, Christian, the new build WORKSFORME!"
1744758,2018-01-23 19:30:09 UTC,"Hello lyarwood, or anyone else affected,"
1744758,2018-01-23 15:14:56 UTC,Thanks Christian. I'll prep a PPA for Ocata and report back here when it's ready.
1744758,2018-01-23 15:10:58 UTC,"This was created by:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=680d2f49dad425395de627a31006cb84848cfa65"
1744758,2018-01-23 14:30:50 UTC,"Comparing 'pull-lp-source libvirt artful' vs 'pull-lp-source libvirt zesty', I'm seeing artful has the following in the configure script and zesty doesn't:"
1744758,2018-01-23 13:54:19 UTC,A couple of things to note about the failing code path.
1744758,2018-01-23 13:18:52 UTC,"Since archives of Zesty are gone this is hard, you can't install packages anymore you don't have yet. The closest are Artful and Xenial.
But Lee already tested 3.6 which is more or less what is in Artful."
1744758,2018-01-23 13:00:11 UTC,I just checked and we don't patch libvirt for the Ocata cloud-archive backport. Do we know if this worked on Zesty? Any chance we still can test Zesty now that it's EOL?
1744758,2018-01-23 12:40:12 UTC,So the issue only appears with the Ocata UCA repo that provides the 2.5.0-3ubuntu5.6~cloud0 build. Why we are installing this in the OpenStack CI upgrade jobs between Pike and Queens is beyond me but something we should be able to correct outside of this bug.
1744758,2018-01-23 07:05:38 UTC,I subscribe the cloud-archive as well so that our OpenStack folks are aware of this as well.
1744758,2018-01-23 07:04:05 UTC,"Hi,
first of all thanks Lee for the update and your help to spot and fix another issue."
1744758,2018-01-23 18:31:36 UTC,"Lee, thanks very much for the recreate details. I was able to recreate the error you were seeing, and also tested successfully with libvirt installed from ppa:corey.bryant/xenial-ocata-bug1744758."
1744760,2018-01-22 17:00:08 UTC,This change was made by a bot.
1744760,2018-01-22 20:07:53 UTC,You may need to run the following from a terminal:
1744760,2018-01-22 20:50:45 UTC,"sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-108 linux-headers-4.4.0-108-generic linux-headers-4.4.0-109 linux-headers-4.4.0-109-generic linux-image-4.4.0-108-generic linux-image-4.4.0-109-generic linux-image-extra-4.4.0-108-generic
  linux-image-extra-4.4.0-109-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  linux-generic linux-headers-4.4.0-112 linux-headers-4.4.0-112-generic linux-headers-generic linux-image-4.4.0-108-generic linux-image-4.4.0-109-generic linux-image-4.4.0-112-generic linux-image-extra-4.4.0-112-generic
  linux-image-generic
Suggested packages:
  fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools
Recommended packages:
  thermald
The following NEW packages will be installed:
  linux-headers-4.4.0-112 linux-headers-4.4.0-112-generic linux-image-4.4.0-108-generic linux-image-4.4.0-109-generic linux-image-4.4.0-112-generic linux-image-extra-4.4.0-112-generic
The following packages will be upgraded:
  linux-generic linux-headers-generic linux-image-generic
3 upgraded, 6 newly installed, 0 to remove and 22 not upgraded.
9 not fully installed or removed.
Need to get 113 MB of archives.
After this operation, 432 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-4.4.0-112-generic amd64 4.4.0-112.135 [21.9 MB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-extra-4.4.0-112-generic amd64 4.4.0-112.135 [36.0 MB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-generic amd64 4.4.0.112.118 [1,786 B]
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-generic amd64 4.4.0.112.118 [2,530 B]
Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-headers-4.4.0-112 all 4.4.0-112.135 [9,925 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-headers-4.4.0-112-generic amd64 4.4.0-112.135 [775 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-headers-generic amd64 4.4.0.112.118 [2,506 B]
Get:8 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-4.4.0-108-generic amd64 4.4.0-108.131 [21.9 MB]
Get:9 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-4.4.0-109-generic amd64 4.4.0-109.132 [21.9 MB]
Fetched 113 MB in 3s (28.5 MB/s)
Selecting previously unselected package linux-image-4.4.0-112-generic.
(Reading database ... 153184 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-112-generic_4.4.0-112.135_amd64.deb ...
Done.
Unpacking linux-image-4.4.0-112-generic (4.4.0-112.135) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-112-generic_4.4.0-112.135_amd64.deb (--unpack):
 unable to stat './lib/firmware/4.4.0-112-generic' (which I was about to install): Unknown error 4094
dpkg-deb: error: subprocess paste was killed by sign..."
1744762,2020-09-21 18:18:35 UTC,I assume from Mike's last comment that this one needs additional work? Removing pullrequest tag for the time being.
1744762,2018-01-22 17:24:37 UTC,"Added a 3.1 target, since this bug does not affect EG proper, because no existing code uses this filter."
1744762,2018-01-22 17:17:41 UTC,http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1744762-lineitem-state-filtering-api
1744762,2018-01-22 17:43:28 UTC,"Kyle, that missing ""+"" is just wrong, but it looks like it should work, if only incidentally, because ""jub"" is the core class of the query.  I'm actually surprised that the in-list version doesn't work, but perhaps there is some subtle difference in the implicit-equals and the implicit-in-list code that's allowing the former to work in what amounts to an extra (useless) ""AND"" nesting but not the latter."
1744766,2018-01-23 11:56:59 UTC,This is to some extent by design.
1744769,2018-03-07 13:52:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744783,2018-05-02 03:07:08 UTC,"I am not able to reproduce the described behavior in master. If I import a record with cat.bib.use_id_for_tcn enabled, the OCLC record is imported with the Evergreen bib id as the TCN. If I disable that setting, the TCN is set to the OCLC record id."
1744809,2018-04-20 17:30:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744817,2018-01-22 22:15:53 UTC,"This happens only when the drive is not mounted. Then I'm asked for a password to decrypt it, and then I get the error on the screen."
1744828,2018-01-23 06:29:23 UTC,Google translate says;
1744830,2020-11-13 11:13:14 UTC,"This is no longer reproducible on bazaar.launchpad.net, so IMO you can remove the workaround from Breezy."
1744830,2018-05-18 15:34:04 UTC,"On Fri, May 18, 2018 at 09:30:26AM -0000, Colin Watson wrote:

> OK, even if it isn't a 200, I agree there's something wrong here.
>
> I think this must be in either bzr-git or dulwich, since that's what
> implements the ""pretend this is a git repository"" bit.  Jelmer, you
> implemented this in the first place - was it your intent that it should
> provide this feature on bazaar.launchpad.net, or is this an
> accidentally-enabled thing that we should just turn off?


Ah, I didn't realize that was on."
1744830,2018-01-26 15:05:33 UTC,"Hmm, is this reproducible?  I admit I haven't tried with {bzr,brz}-git, but with curl I get:"
1744830,2018-05-18 09:30:26 UTC,"OK, even if it isn't a 200, I agree there's something wrong here."
1744830,2018-05-18 04:17:23 UTC,[Expired for Launchpad itself because there has been no activity for 60 days.]
1744830,2018-03-04 18:31:37 UTC,"I can also reproduce it with git itself, it gets stuck:"
1744830,2018-05-18 09:30:45 UTC,"(Last comment should read ""even if it isn't a 500"")"
1744852,2018-02-28 08:43:30 UTC,"Mainline Kernel 4.15.5 works WELL.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.5/"
1744852,2018-02-13 04:06:04 UTC,Mainline Kernel 4.15.3 works WELL.
1744852,2018-02-13 03:55:54 UTC,Mainline Kernel 4.15.2 works WELL.
1744852,2018-02-04 10:25:41 UTC,"After Upgrading kernel 4.15.1, also Works WELL."
1744852,2018-01-24 02:23:34 UTC,"Correction.
W: Possibel -> W: Possible"
1744852,2018-01-30 09:54:33 UTC,4.13.0-32.35~16.04.1 has also same problem.
1744852,2018-01-23 05:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1744852,2018-01-30 10:11:16 UTC,I used UKUU to upgrade kernel from 4.15-rc9 to 4.15.
1744852,2018-01-24 02:19:26 UTC,I used UKUU to upgrade kernel 4.15.0-rc9.
1744852,2018-01-23 06:30:54 UTC,"I installed already linux-hwe using by ""sudo apt-get install --install-recommends linux-kernel-hwe-16.04 xserver-xorg-hwe-16.04'
then, I booted with linux-hwe kernel 4.13.0-31 to do apport-collect."
1744852,2018-01-23 21:27:49 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1744858,2018-01-30 14:48:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744870,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1744877,2018-01-23 07:40:35 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 __GI_abort () at abort.c:90
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f53d1f264e8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=<optimized out>, str=0x7f53d1f22e7c ""d pointer"", ptr=<optimized out>, ar_ptr=<optimized out>) at malloc.c:5425
 _int_free (av=0x7f53d2158c20 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4174"
1744882,2020-10-21 12:21:03 UTC,Marking the Kilo task wontfix as it has been EOL for a long time.
1744882,2018-04-11 16:04:52 UTC,Regression testing for trusty-mitaka has successfully passed:
1744882,2018-02-25 15:25:54 UTC,This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu2
1744882,2018-02-23 21:42:31 UTC,Testing has completed successfully for ocata-proposed between regression testing successfully and the following results testing qemu/libvirt with microcode updates: https://paste.ubuntu.com/p/X45Gghqvkk/
1744882,2018-02-22 13:14:52 UTC,"This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3.4~cloud0
---------------"
1744882,2018-02-16 15:52:56 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1744882,2018-02-15 18:57:31 UTC,Regression testing with tempest successful on pike-proposed:
1744882,2018-02-15 17:42:26 UTC,Regression testing with tempest successful on ocata-proposed:
1744882,2018-01-23 08:09:43 UTC,"Set up the initial set, leaving the security SRUs for Marc to share is intentions."
1744882,2018-02-09 16:23:06 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1744882,2018-02-08 13:41:32 UTC,Actually this particular change will be in 2.11.1 which should be released next week and then follow 2.11 into bionic.
1744882,2018-02-08 13:14:34 UTC,qemu 2.11 is in proposed
1744882,2018-02-07 16:02:38 UTC,This bug was fixed in the package qemu - 2.0.0+dfsg-2ubuntu1.38
1744882,2018-02-07 15:52:37 UTC,This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.20
1744882,2018-02-07 15:52:35 UTC,This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3.4
1744882,2018-01-23 08:51:30 UTC,"I asked about the latter in [1], as I might have missed a major change of plans."
1744882,2018-01-23 08:31:34 UTC,"Hmm, I haven't seen any submission of these to qemu-stable yet.
Was the plan revised?"
1744882,2018-02-09 16:23:12 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1744882,2018-02-22 13:14:51 UTC,The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1744883,2018-01-26 10:29:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744885,2018-01-29 05:48:58 UTC,"> Returning value was added to ""_get_config_from_profile()"" by the following patch:
> https://review.openstack.org/#/c/535476/3/openstack/connection.py
>
> So there is a possibility that this bug was already solved in the latest OpenStack-SDK.
I tried above the patch.
As a result, this issue is not resolved.
"
1744899,2018-01-27 23:06:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744899,2018-01-28 00:41:36 UTC,"Same error.
Plenty of space on the drive."
1744899,2020-05-09 15:37:54 UTC,"For anyone else stumbling upon this bug with a similar error message, it's possible you're out of inodes."
1744900,2018-01-23 09:22:48 UTC,my hwinfo - lenovo x230
1744901,2019-08-21 13:40:26 UTC,"Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1744901,2019-10-21 04:17:37 UTC,[Expired for usb-creator (Ubuntu) because there has been no activity for 60 days.]
1744907,2018-01-23 12:26:57 UTC,Update: Failed tempest test in last run of fs20 passed:- https://review.rdoproject.org/jenkins/job/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset020-master/607
1744907,2018-05-02 04:43:04 UTC,Seen again:- https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset020-queens/f7a11fa/undercloud/home/jenkins/tempest/tempest.html.gz
1744907,2018-04-17 06:33:31 UTC,Seeing the failure in fs20 queens last run:- https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset020-queens/165b64e/undercloud/home/jenkins/tempest/tempest.html.gz
1744907,2018-01-23 10:40:40 UTC,"This is a race that failing negative testcase [1] is supposed to catch
# Disallow creating another image when first image is being saved
and failing test taking longer is an indication that another image is created when it should not."
1744907,2018-02-21 20:48:23 UTC,Since this is not currently failing consistently I think it's a High bug. If it starts failing consistently we need to figure out a plan to address it and should raid the priority.
1744907,2018-02-21 20:49:09 UTC,The quality of this tests is still uncertain. It has passed the last three attempts where tempest was executed [1].  It passed twice on the 20th and once on the 21st.
1744907,2018-01-23 20:36:06 UTC,"Agreed, test_create_second_image_when_first_image_is_being_saved appears brittle as it expects the first image is still busy being created when the second image create is attempted and expects to fail the second image create."
1744917,2018-01-24 07:27:47 UTC,below the mail from systemd. I've attached a rule and will attach another rule to include in 18.04
1744917,2018-01-24 07:28:46 UTC,Realflight interlink rule
1744921,2018-01-31 13:38:33 UTC,https://github.com/snapcore/snapcraft/pull/1900
1744922,2018-01-23 15:57:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1744938,2018-01-24 09:45:16 UTC,The exchange of road images happens only on a up/down move of the map. Seems like the map turnaround is somehow involved:
1744938,2019-09-16 19:06:57 UTC,Migrated to https://github.com/widelands/widelands/issues/3252
1744940,2018-01-24 09:32:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744941,2018-08-17 12:10:51 UTC,Or well any snap could for example ship a wrong .desktop file and make gnome-software not to work...
1744941,2018-08-17 12:09:51 UTC,"> Does it actually cause crashes for Xenial users in practice? If not, what's the justification for SRUing it?
"
1744941,2018-08-17 05:14:59 UTC,Unsubscribing sponsors as there's nothing left to sponsor.
1744941,2018-04-26 10:07:05 UTC,"> Malformed .desktop files might causes crashes...
"
1744941,2018-04-12 09:29:47 UTC,Does this bug indeed also affect artful? If that's the case then we'd need it prepared and uploaded for artful before getting the xenial one accepted.
1744941,2018-04-09 21:00:04 UTC,"seb poked me about this, and now it is uploaded for xenial, thanks!"
1744941,2018-04-12 10:11:50 UTC,"On Thu, Apr 12, 2018 at 09:29:47AM -0000, Łukasz Zemczak wrote:

> Does this bug indeed also affect artful? If that's the case then we'd
> need it prepared and uploaded for artful before getting the xenial one
> accepted.
"
1744941,2018-01-23 16:25:47 UTC,"The attachment ""Debdiff for xenial package"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1744941,2018-03-15 15:58:56 UTC,This bug was fixed in the package appstream-glib - 0.7.7-1
1744941,2018-02-21 09:30:41 UTC,Thanks.
1744941,2018-01-24 20:04:59 UTC,"Wrong project, this is not in AppStream, but appstream-glib (thanks for the patch though! :-) )"
1744946,2018-01-23 15:50:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1744946,2018-01-23 16:39:18 UTC,I filed a bug report with GNOME:
1744968,2018-02-09 16:47:46 UTC,"To clarify: we need this SRU to land before we can make further updates to nplan, since nplan will start installing an /etc/network/interfaces file containing just a comment pointing to the new location of configurations in a netplan world, but that file might confuse juju."
1744968,2018-02-09 17:07:04 UTC,"Hello Nicholas, or anyone else affected,"
1744968,2018-02-14 17:23:00 UTC,"I tested juju 2.3.2 and found it working, able to bootstrap, deploy, bash completion all work. I deployed a bionic controller and workload as well without any apparent issues."
1744968,2018-02-15 18:18:50 UTC,This bug was fixed in the package juju-core - 2.3.2-0ubuntu0.16.04.1
1744968,2018-02-15 18:18:54 UTC,"The verification of the Stable Release Update for juju-core has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1744968,2018-02-16 19:43:48 UTC,This bug was fixed in the package nplan - 0.33
1744968,2019-05-16 20:05:00 UTC,Netplan SRU backport with these changes has already happened and the juju updates are now done via snaps AFAIK. Closing as Fix Released (Xenial has at least juju 2.3.7 in archive).
1744968,2018-01-23 16:28:56 UTC,"This affects netplan too in xenial (and by the same token, I'll land this SRU fix to artful as well)."
1744973,2019-02-07 09:43:02 UTC,Hi Mistral team !
1744973,2018-04-06 08:47:05 UTC,Can you tell us which version of Mistral this is?
1744975,2018-01-23 16:52:30 UTC,Thank you for the assistance in advance.
1744979,2018-01-24 14:08:41 UTC,"How much should GRUB_DEFAULT be set to for example start 4.4.0-112 kernel automatically when booting?
Different descriptions do not give a clear answer to which ""menuentry"" counts and which one does not ...
https://pastebin.com/G23aHrMn and
https://pastebin.com/g4hr6Ltf"
1744979,2018-01-24 09:02:10 UTC,Sorry this missed ...
1744979,2018-01-24 08:59:57 UTC,"After installing the proposed kernel:
sudo update-grub
[sudo] csola48 jelszava:
GRUB beállítófájl előállítása…
Figyelem: A GRUB_TIMEOUT beállítása egy nem nulla értékre, ha a beállított GRUB_HIDDEN_TIMEOUT többé nem támogatott.
Megtalált linux lemezkép: /boot/vmlinuz-4.10.0-42-generic
Megtalált initrd lemezkép: /boot/initrd.img-4.10.0-42-generic
Megtalált linux lemezkép: /boot/vmlinuz-4.10.0-40-generic
Megtalált initrd lemezkép: /boot/initrd.img-4.10.0-40-generic
Megtalált linux lemezkép: /boot/vmlinuz-4.4.113-0404113-lowlatency
Megtalált initrd lemezkép: /boot/initrd.img-4.4.113-0404113-lowlatency
Megtalált linux lemezkép: /boot/vmlinuz-4.4.113-0404113-generic
Megtalált initrd lemezkép: /boot/initrd.img-4.4.113-0404113-generic
Megtalált linux lemezkép: /boot/vmlinuz-4.4.0-112-generic
Megtalált initrd lemezkép: /boot/initrd.img-4.4.0-112-generic
Megtalált linux lemezkép: /boot/vmlinuz-4.4.0-109-generic
Megtalált initrd lemezkép: /boot/initrd.img-4.4.0-109-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
kész"
1744979,2018-01-24 08:10:26 UTC,"/boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#"
1744979,2018-01-23 21:33:57 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1744979,2018-01-23 18:26:28 UTC,apport information
1744979,2018-01-23 18:26:27 UTC,apport information
1744979,2018-01-23 18:26:24 UTC,apport information
1744979,2018-01-23 18:26:26 UTC,apport information
1744979,2018-01-23 18:26:21 UTC,apport information
1744979,2018-01-23 18:26:22 UTC,apport information
1744979,2018-01-23 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1744979,2018-01-23 18:26:14 UTC,apport information
1744979,2018-01-23 18:26:15 UTC,apport information
1744979,2018-01-23 18:26:23 UTC,apport information
1744979,2018-01-23 18:26:17 UTC,apport information
1744979,2018-01-23 18:26:18 UTC,apport information
1744979,2018-01-23 18:26:19 UTC,apport information
1744979,2018-01-23 18:26:20 UTC,apport information
1744979,2018-01-23 18:26:16 UTC,apport information
1744985,2018-08-03 08:09:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588468"
1744985,2018-08-15 07:45:09 UTC,"Change abandoned by Chang Liu (<email address hidden>) on branch: master
Review: https://review.openstack.org/588468
Reason: There is a better solution."
1744988,2019-10-03 08:26:22 UTC,Patches could be found in Bionic.
1744988,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1744988,2018-03-21 07:50:57 UTC,"My apologies, I was not aware of this. After your message I have started testing the proposed kernel and can verify it is working as expected."
1744988,2018-03-19 10:57:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1744988,2018-02-01 19:00:31 UTC,"SRU request for Artful submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089834.html"
1744988,2018-01-31 17:11:02 UTC,"Sorry, you can ignore the request in comment #5.  I missed all the kenrels you tested in the bug description."
1744988,2018-01-31 19:03:19 UTC,"I built a test kernel with the three commits: da4ae6c, b511203 and 4b5b212"
1744988,2018-01-31 17:09:50 UTC,"Can you see if this bug still occurs with the latest HWE kernel for Xenial, which is 4.13 based?"
1744988,2018-01-31 11:17:35 UTC,"I have created patchfile, tsc.patch, which applies the upstream patchwork done by Len Brown to the 4.13.0-31-generic Kernel. This resolves the time issues we are having."
1744988,2018-01-24 16:18:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1744988,2018-01-23 17:38:28 UTC,"Although probably obvious, the mainline kernels that I tested have all been downloaden from http://kernel.ubuntu.com/~kernel-ppa/mainline/"
1744988,2018-02-01 10:33:22 UTC,I am running your build on two servers for about an hour now. Timing is stable on the both of them.
1744988,2018-01-24 16:19:11 UTC,Wow!! I've been searching for this problem for quite some time!!
1744989,2018-02-06 17:50:56 UTC,Sorry for the delay in responding.  Finally had a chance to check if the issue is still occurring in the nightly build.
1744989,2018-01-23 21:21:27 UTC,"CI builds for Windows are at
https://ci.appveyor.com/project/inkscape/inkscape/history"
1744989,2018-01-23 21:08:14 UTC,"Is there a nightly Windows build available?  I checked on Ubuntu, and it seems like the issue does not appear there."
1744989,2018-01-23 18:26:45 UTC,Likely related (if not a duplicate of) bug #170356.
1744989,2018-01-23 19:32:01 UTC,"There's nothing that needs clarification but maybe I should've been clearer:
Test a nightly build an check if disabling anti-aliasing solves / works around your issue. (If you don't want to test that's fine, too, but don't expect your issue becoming any more likely to be solved then...)"
1744989,2018-01-23 18:55:52 UTC,"I don't think that this is the same issue as #170356.  That bug seems to be related to how Cairo handles antialiasing of shapes which are flush against eachother (Each division is anti-aliased separately, leading to a thin line of transparency running between them when rasterized)."
1744992,2018-01-23 18:11:18 UTC,Proposed fix: https://review.openstack.org/536917
1744992,2018-01-26 00:16:16 UTC,This issue was fixed in the openstack/freezer-web-ui 6.0.0.0b3 development milestone.
1744995,2018-01-23 19:00:06 UTC,This change was made by a bot.
1744999,2020-02-27 07:30:11 UTC,It is already fixed in https://review.opendev.org/#/c/680603/.
1745002,2018-01-23 19:47:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/536944"
1745002,2018-01-23 19:48:49 UTC,puppet-neutron patch for configuring endpoint_type: https://review.openstack.org/#/c/536942/
1745002,2018-01-25 06:47:51 UTC,"Reviewed:  https://review.openstack.org/536942
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=ae730fb95bba7303baedf8fa5fc764e43cdefee5
Submitter: Zuul
Branch:    master"
1745002,2018-01-30 13:56:13 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/536944
Reason: Gate resets is causing issue to land a critical patch (538346) - I need to clear the gate until 538346 is merged. Please do not restore this patch, I'll take care of it."
1745002,2018-02-08 07:06:28 UTC,"Reviewed:  https://review.openstack.org/536944
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=966f4a7092c22aefee63a26f67a93aaca1b71bfe
Submitter: Zuul
Branch:    master"
1745002,2018-03-03 11:42:53 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0rc1 release candidate.
1745002,2018-01-23 19:14:11 UTC,We aren't configuring this at all at the moment so the current value reflects the neutron's default value.
1745003,2018-01-28 23:36:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/538694"
1745003,2018-01-31 08:15:56 UTC,"Reviewed:  https://review.openstack.org/538694
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=9363e0b0a14acf0ed9abc0e5d1f939131655ae03
Submitter: Zuul
Branch:    master"
1745003,2018-01-27 22:34:27 UTC,"Also happening under py27, now that those tests are no longer blocked by the eventlet issue."
1745003,2018-01-25 03:24:09 UTC,"Reviewed:  https://review.openstack.org/536939
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=5517049c0f40e930361ad9a77d15b708a919fcb6
Submitter: Zuul
Branch:    master"
1745003,2018-01-23 19:33:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/536939"
1745003,2018-01-28 23:25:12 UTC,"Update: still not sure why it only started failing recently, but here's some more info:"
1745005,2018-01-24 07:05:03 UTC,Is this a new problem or has this always been the case?
1745007,2018-02-21 19:40:26 UTC,"@Khaled: I don't see these patches in artful/master-next, so I'm going to move back the artful task back to ""In Progress"". Can you confirm if these will be integrated for the next cycle, or if I should resubmit?"
1745007,2018-02-21 19:53:00 UTC,"Scratch that - I see these changes queued on the master-next-backlog branch, moving back to Fix Committed :)"
1745007,2018-03-19 10:58:19 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1745007,2018-03-19 21:16:04 UTC,Verified:
1745007,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1745009,2018-09-06 03:33:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745010,2018-01-25 00:12:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/537709"
1745011,2018-02-05 10:18:49 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-112.135~14.04.1
1745011,2018-02-05 11:42:34 UTC,The package has been published and the bug is being set to Fix Released
1745011,2018-01-31 08:05:00 UTC,No bug was tagged with verification-needed this time.
1745011,2018-02-05 09:42:36 UTC,Skipping certification-testing. The current cert test result looks good. http://people.canonical.com/~hwcert/sru-testing/current/trusty-4.4-proposed.html.
1745011,2018-01-31 08:03:46 UTC,"4.4.0-112.135~14.04.1 - generic
Regression test CMPL."
1745016,2018-04-10 06:20:50 UTC,"Reviewed:  https://review.openstack.org/536957
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=638db5864776e91cc622eec4cbbb6303c6c3f148
Submitter: Zuul
Branch:    stable/ocata"
1745016,2018-01-23 20:29:07 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/536957"
1745016,2018-04-23 21:50:48 UTC,This issue was fixed in the openstack/tripleo-heat-templates 6.2.13 release.
1745023,2018-01-23 20:58:55 UTC,I have not noticed the alpha value of the object in the previous attachment was lowered so here is another screenshot.
1745023,2018-01-24 02:06:35 UTC,"If you could attach the svg file as an example, that could help."
1745023,2018-01-24 07:26:22 UTC,"Here is the .svg file. I decided not to remove any layers, but the affected objects are on the layer ""bal""."
1745023,2018-01-24 07:36:06 UTC,"I also have to add, that this object was made out of two combined paths and copied from another Inkscape project. Previously I noticed this bug appearing with a duplicated layer, where only the duplicate displayed such behaviour (it also contained combined paths, including the object from the attached file)."
1745023,2018-01-24 21:30:27 UTC,"Can you remember how it could have happened that the blend filter was added?
Was the object copied from a layer with that filter?"
1745023,2018-01-26 21:44:45 UTC,"No, I did not use filters at all and do not know how this could have been added, unless there is a way for it to happen accidentally. I know well the tools I use in this program and certainly wouldn't activate what I don't need. Ubuntu Unity HUD tool wasn't used as well."
1745024,2018-01-25 00:12:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/537708"
1745025,2018-01-23 21:18:26 UTC,"So it looks like the value of params is run through the SAFE::reval() function, which seems to try to evaluate the value as perl code?"
1745025,2018-01-23 21:33:25 UTC,"I don't know about ""cool"", but I can confirm that it is intentional."
1745025,2018-01-24 20:30:01 UTC,"Mike, if you know of any examples of how it can be used in a useful manner please pass them on.  I'm happy to try and add some documention on the params, but I cannot think of an example of using a perl code as the value that would be useful.  Could you define a perl function as the value and then use it in your template like params.branchweblink(shortname)?
Thanks
Josh"
1745028,2019-06-25 04:37:23 UTC,"I think since this report was written, the experience has changed dramatically. I cannot even find the wording that you have seen in our codebase."
1745030,2019-06-27 07:47:22 UTC,"There is a more general report that describes lack of tab completion, delete keys, etc. I'll mention arrow keys there as well as I suspect that all of these will be addressed at the same time and will mark this report as its duplicate."
1745033,2018-01-27 08:56:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745035,2018-01-23 22:14:55 UTC,"So I think the issue is we did not untar the component tarball. It works with my bug-fixes-3 branch, so I'm narrowing that down."
1745044,2018-01-24 09:26:30 UTC,Thanks for your report. This is intended and a security feature of wayland. Meanwhile you can select 'Ubuntu on Xorg' in the logging screen to start xorg instead and screen capture applications should work.
1745044,2018-01-24 09:33:48 UTC,Hi. Screencasting and screenshotting is quite different in Wayland logins compared to X11 of the past.
1745045,2018-01-28 22:33:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745045,2018-01-28 22:37:22 UTC,Attaching output of manual dkms build (dkms build -m spl -v 0.6.5.6 spl)
1745045,2018-04-05 21:42:38 UTC,I have the issue since kernel 4.13.0-37
1745045,2018-04-21 04:26:16 UTC,I think I have same problem. I was trying to install zfsutils on Xenial Ubuntu Studio with the low-latency kernel.
1745045,2018-04-21 04:30:28 UTC,"Here is the terminal output w error message - installation of libzfs2linux, then zfs-fuse, then zfsutils-linux on Xenial Ubuntu Studio with 4.13.0-38-lowlatency"
1745045,2018-04-24 21:10:51 UTC,I have been having a similar problem and it seems to be due to vfs_getattr having been changed in the kernel to take 4 arguments.  It seems that later versions of spl will work with the new vfs_getattr.  (But I have no idea how to use the later version)
1745049,2018-01-25 22:35:20 UTC,"I was able to save the results of:
apport-bug linux --save linux.report"
1745049,2018-01-25 21:59:25 UTC,The bug in the kernel disables my nvidia video driver as well as disabling wifi and usb networking.  I have no access to the internet so I can not submit an apport-collect.
1745049,2018-01-25 06:09:30 UTC,This bug affects kernel 4.13.0.31 and nvidia drivers
1745049,2018-01-25 06:08:06 UTC,"I found out that the 4.13.0.31 kernel was from the artful security repo.   When I use 'dkms status' it shows that the bumblebee and nvidia kernel modules appear to be present.   I just tried booting with the 4.14.0.31 kernel again.  This time it did not crash.  However, it appeared that my graphics card lost its' capability and the screen was drawing windows very slowly.  I lost my ability to change the screen resolution.  I think there is something wrong with kernel 4.13.0.31."
1745049,2018-01-25 06:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745049,2018-01-24 04:16:26 UTC,"I have just tested my laptop by installing the mainline kernel 4.14.15.   It boots fine and bumblebee works fine.  So it looks like this upstream kernel work OK with bumblebee.  Incidentally, I found out that I need to install libelf-dev in order for kernel modules to get built successfully with this upstream kernel."
1745060,2018-02-07 00:10:08 UTC,Installing gnome-shell-extensions is not required to replicate this bug.
1745060,2018-04-02 08:29:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745060,2019-03-20 05:47:34 UTC,"any update?, poor user experience..."
1745062,2019-09-25 23:07:25 UTC,"Actually, the content for snap try is bind-mounted (or at least it is now, I'm not sure if that was the case when this was first reported or not I think it has always been that way but I'm not sure)."
1745063,2018-01-25 20:41:31 UTC,Good to know!
1745063,2018-01-24 16:16:31 UTC,Thanks!
1745063,2018-01-24 16:22:16 UTC,"Interesting, thanks!"
1745063,2018-01-24 15:37:45 UTC,"I haven't tested it, but it probably does"
1745063,2018-01-24 15:29:34 UTC,I'm not sure how the advanced search screen handles filtering by pub date. Does it eliminate anything that doesn't have a pub date that it can understand?
1745063,2018-01-24 15:16:08 UTC,How do you see this working (or how does your discovery layer handle it) if there are records with no date? Either the old standard n.d. or  [date of publication not identified]. Also for those dates with ? -- 192?
1745063,2018-01-24 15:04:52 UTC,This would be helpful for our libraries as well.
1745063,2018-01-24 15:59:53 UTC,"By default (though based on configuration) pub dates with ""unknown"" markers are normalized to the start of the unknown range for date1 and to the end for date2.  So, a date1 of ""199?"" becomes ""1990"", and a date2 of the same becomes ""1999""."
1745066,2018-01-24 01:35:15 UTC,And updated doco for the install hook
1745066,2019-09-25 23:11:43 UTC,Does `snapctl set` during a hook still cause the installation of a snap to hang for you? I cannot reproduce this behavior with snapd 2.42.
1745066,2019-11-25 04:17:40 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1745067,2018-03-01 19:06:12 UTC,"On 3/1/18 8:50 PM, AlekseyK wrote:

> What will be the correct rule here?
"
1745067,2018-02-28 22:44:03 UTC,"If it works in complain mode, this means the problem is missing rules, but not deny rules (deny rules are enforced even in complain mode)."
1745067,2018-03-01 17:29:18 UTC,"On 2/28/18 11:23 PM, AlekseyK wrote:

> sudo journalctl -f | fgrep DENIED
>
> shows nothing.
"
1745067,2018-03-01 18:12:32 UTC,"Thank You. While trying to enable video in a call, prints following:"
1745067,2018-03-01 18:48:32 UTC,"I have updated my profile to fix Skype on OpenSUSE [0]. Tested on KDE
and GNOME. I am not sure if webcam should work though... Skype does see
device name, though I can't get video at all even with Cheese, probably
VirtualBox USB forwarding issues or whatever."
1745067,2018-03-01 18:50:38 UTC,What will be the correct rule here?
1745067,2018-03-01 19:07:46 UTC,I've added 3 lines from You profile related to video:
1745067,2018-03-03 13:54:57 UTC,">Vincas Dargis (talkless) wrote 5 hours ago:
>Maybe that line with kde5-open is the culprit.
"
1745067,2018-03-01 19:33:31 UTC,">Vincas Dargis (talkless) wrote 22 minutes ago:
>Line 164-165:
After these lines works correctly now! Thank You very much!
"
1745067,2018-03-02 17:51:46 UTC,"On 3/1/18 9:33 PM, AlekseyK wrote:

>> Vincas Dargis (talkless) wrote 22 minutes ago:
>> Line 164-165:
> After these lines works correctly now! Thank You very much!
>
"
1745067,2018-03-02 19:15:14 UTC,My profile with lines 164-165 from Yours works. I tried Yours but seems apparmor does not reload/restart profile. I did by instructions in Your repo:
1745067,2018-03-02 19:38:46 UTC,"On 3/2/18 9:15 PM, AlekseyK wrote:

> Still using my profile. Only restarting PC helps. How to correctly
> switch/reload profile?
"
1745067,2018-03-02 21:55:44 UTC,"With Your profile camera does not work - no error, no DENIED message related to /dev/* - just black square. Also Your profile allows full access to HOME dir even with removed removing ""#include
<abstractions/user-download>"" which is unacceptable to me. Will use mine. Thanks for Your suggestions - helped much!"
1745067,2018-03-03 08:05:20 UTC,"On 3/2/18 11:55 PM, AlekseyK wrote:

> With Your profile camera does not work - no error, no DENIED message related to /dev/* - just black square. Also Your profile allows full access to HOME dir even with removed removing ""#include
> <abstractions/user-download>"" which is unacceptable to me. Will use mine. Thanks for Your suggestions - helped much!
"
1745067,2018-03-03 12:08:07 UTC,"I have tried my profile on openSUSE KDE & GNOME liveCDs. Sometimes I do get dark video from camera, but it's enough to restart Skype ant it works. Not sure what could be the issue here."
1745067,2018-02-28 21:23:05 UTC,sudo journalctl -f | fgrep DENIED
1745067,2018-03-01 19:16:36 UTC,With Your complete profile video does not work also:
1745067,2018-02-28 21:06:20 UTC,Output attached.
1745067,2018-02-28 16:47:41 UTC,"On 2/28/18 3:07 PM, AlekseyK wrote:

> Hi, Vincas
>
> Now I'm trying to use Your new usr.bin.skypeforlinux profile.
> skypeforlinux won't start with it - runs only in complain mode. How to
> solve? Help me please! Thanks!
"
1745067,2018-02-28 20:05:42 UTC,"On 2/28/18 8:50 PM, AlekseyK wrote:

>> Vincas Dargis (talkless) wrote 39 minutes ago:
>> I can't comment if I do not see DENIED messages in your kernel log.
> How to see it? Seems /var/log/messages is missed in openSUSE.
"
1745067,2018-01-24 17:08:22 UTC,"Please consider upgrading to newer Skype, as 4.3 is unsupported."
1745067,2018-01-24 17:09:06 UTC,"Oh, bug report has marked ""openSUSE"". I did not test that profile there. I could do that though."
1745067,2018-01-24 19:35:30 UTC,Thanks! Prefer to use 4.3 as do not know how new skypeforlinux works and spy after me or my data. I like how current skype profile works - it just blocks everything for skype - it even does not see my home dir content. I know it is unsupported however it still works fine and have better functionality comparing to newest one.
1745067,2018-01-25 18:44:39 UTC,"On 1/24/18 9:35 PM, AlekseyK wrote:

> Thanks! Prefer to use 4.3 as do not know how new skypeforlinux works and
> spy after me or my data. I like how current skype profile works - it
> just blocks everything for skype - it even does not see my home dir
> content. I know it is unsupported however it still works fine and have
> better functionality comparing to newest one.
>
> However if Your skypeforlinux profile also blocks everything for skype -
> it is good, could give it a try it in the future.
"
1745067,2018-01-25 21:11:01 UTC,">New usr.bin.skypeforlinux uses ""abstractions/user-download"" that does allow to read and write into >$HOME (as it's common download directory for various programs), also allows Downloads and Desktop
>directories [0].
"
1745067,2018-01-26 17:38:40 UTC,"On 1/25/18 11:11 PM, AlekseyK wrote:

>> New usr.bin.skypeforlinux uses ""abstractions/user-download"" that does allow to read and write into >$HOME (as it's common download directory for various programs), also allows Downloads and Desktop
>> directories [0].
>
> Terrible. Not acceptable. Could You fix old usr.bin.skype profile
> please?
"
1745067,2018-01-26 17:59:52 UTC,"https://askubuntu.com/a/938239/130585
download.skype.com/linux/skype-ubuntu-precise_4.3.0.37-1_i386.deb"
1745067,2018-01-31 09:49:35 UTC,"Strange, today skype started normal in enforce mode. :) So will stay on 4.3 for now."
1745067,2018-02-28 20:11:14 UTC,"On Wed, Feb 28, 2018 at 06:50:14PM -0000, AlekseyK wrote:

> >I can't comment if I do not see DENIED messages in your kernel log.
> How to see it? Seems /var/log/messages is missed in openSUSE.
"
1745067,2018-01-31 13:46:08 UTC,"Sorry, wrong messge. It still crashes like before (just did not restart to check)."
1745067,2018-02-28 11:48:01 UTC,One more line added here for correct work:
1745067,2018-02-28 13:07:35 UTC,"Hi, Vincas"
1745067,2018-02-28 16:53:36 UTC,"Found some solution here: https://askubuntu.com/a/1010702/130585, only have problem with web camera."
1745067,2018-02-28 17:32:41 UTC,">Vincas Dargis (talkless) wrote on 2018-01-26:
>What distribution and desktop are you running? I'm using KDE on two
>Debian machines, also tested on Ubuntu VM.
"
1745067,2018-02-28 18:00:07 UTC,"On 2/28/18 7:32 PM, AlekseyK wrote:

>> Vincas Dargis (talkless) wrote on 2018-01-26:
>> What distribution and desktop are you running? I'm using KDE on two
>> Debian machines, also tested on Ubuntu VM.
>
> As I said: openSUSE.
"
1745067,2018-02-28 18:15:10 UTC,"On 2/28/18 7:32 PM, AlekseyK wrote:> Profile mentioned here:
https://askubuntu.com/a/1010702/130585 blocks

> access to home dir. I've added only this line:
>
> owner @{HOME}/Download/Skype/{,**} rw,
"
1745067,2018-02-28 18:50:14 UTC,">Vincas Dargis (talkless) wrote 39 minutes ago:
>I can't comment if I do not see DENIED messages in your kernel log.
How to see it? Seems /var/log/messages is missed in openSUSE.
"
1745067,2018-02-28 18:51:26 UTC,"> This is simply a decision author can take.
I understand this. However skype is terrible thing and such ""protection"" does nothing.
"
1745067,2018-02-12 23:20:59 UTC,"I have fixed You profile, now all works just fine, appeared not too complex. :)"
1745072,2018-10-08 20:53:41 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1745072,2019-03-22 03:49:09 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1745072,2018-09-20 19:57:56 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604203"
1745072,2018-09-20 19:26:06 UTC,"Reviewed:  https://review.openstack.org/533168
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eefb20e4658e17f91fa76b74fef6ff899babe51b
Submitter: Zuul
Branch:    master"
1745072,2018-10-03 01:13:43 UTC,"Reviewed:  https://review.openstack.org/604203
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dba00dbe11361a12d2602dd9601ee365a0755051
Submitter: Zuul
Branch:    stable/rocky"
1745072,2018-01-24 02:39:22 UTC,"Sorry for the wrong order of operations here, I committed the fix to this here:"
1745091,2019-06-02 04:17:31 UTC,[Expired for OpenStack rabbitmq-server charm because there has been no activity for 60 days.]
1745091,2019-04-02 14:17:15 UTC,This is over a year old.  Setting this to incomplete to see if it has occurred again; if not then it will expire.
1745092,2018-10-09 09:17:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745105,2018-01-24 07:41:53 UTC,"Interesting idea. Since this would be a design change, please submit it to the upstream developers here:"
1745105,2018-01-24 07:42:40 UTC,"When done, please let us know the ID of your newly created bug."
1745105,2018-01-29 13:54:41 UTC,Ticket created: https://bugzilla.gnome.org/show_bug.cgi?id=793003
1745105,2019-03-18 15:04:31 UTC,"Note that 'enter' seems to validate the change on windows as well. Using Esc does undo the change though, which can be used even if your screen isn't working"
1745113,2018-02-27 00:54:07 UTC,Because of that problem I could not only not upgrade the kernel but couldn't install any software at all.
1745114,2020-08-29 14:32:53 UTC,This bug was fixed in the package libvirt - 6.6.0-1ubuntu2
1745114,2020-08-07 07:31:13 UTC,"Turns out this isn't as complex as I thought.
It was meant to work anyway but broken inadvertently in 2017 by eba2225b."
1745114,2019-07-02 11:58:38 UTC,"I might have asked at a bad time of day, document it here
@jjohansen/jdstrand (now subscribed to the bug):"
1745114,2018-08-21 06:12:10 UTC,"FYI - until we can make this work, please do realize that at least the global abstraction libvirt-qemu got a local override in Cosmic that can be used to extend rules for all guests without having to bother with conffile prompts later on."
1745114,2019-07-04 05:49:01 UTC,I got these:
1745114,2018-08-21 06:08:47 UTC,"As I assumed the old (cron) and new (virt-aa-helper call) cleanup code makes the libvirt-<uuid> files unusable.
Also all old approaches wanted to avoid cluttering /etc/apparmor.d/libvirt/* to not loose overview.
Best (not fastest, but best) solution would really the ""include if avail"" once available in apparmor."
1745114,2018-08-15 18:09:29 UTC,"Actually I'm stupid, the base file being /etc/apparmor.d/libvirt/libvirt-<uuid> is providing exactly that already.
I need to check if that would survive a lifecycle of destroy/undefine/define and such (I think recent versions remove it), but we should check before adding another."
1745114,2018-08-09 04:46:04 UTC,"Split bug 1786019 for the non ""if exists"" code"
1745114,2018-08-09 04:45:49 UTC,"The code is not in Cosmic, so not considering this this cycle yet"
1745114,2018-06-11 08:07:05 UTC,"Check if we could use this tech to also provide something like a conf.d directory for virt-aa-helper.
E.g. tools that use other image paths could drop conf files - need to check wildcard support on the include thou if that is possible."
1745114,2018-01-25 06:43:47 UTC,"Just now possible:
- Needs apparmor 2.12.1, 2.11.2, and 2.10.4
- So libvirt needs hard dependency on that
- New syntax is like:
  include if exists (<...>|""..."")
  so just like regular includes with ""if exists"" between the include and the path"
1745114,2018-08-21 06:11:06 UTC,"I summarized it in another bug nicely (I think), quoting it here to be on the main bug as well:"
1745115,2018-01-24 08:46:15 UTC,"StacktraceTop:
 wl_abort (fmt=fmt@entry=0x7fd2ada085b0 ""dup failed: %s\n"") at ../src/wayland-util.c:419
 wl_closure_marshal (sender=sender@entry=0x561a2cab0f30, opcode=opcode@entry=0, args=args@entry=0x7ffd6ea6b670, message=message@entry=0x7fd2adc0ba90 <wl_shm_requests>) at ../src/connection.c:584
 wl_proxy_marshal_array_constructor_versioned (proxy=proxy@entry=0x561a2cab0f30, opcode=opcode@entry=0, args=args@entry=0x7ffd6ea6b670, interface=interface@entry=0x7fd2adc0bac0 <wl_shm_pool_interface>, version=1) at ../src/wayland-client.c:651
 wl_proxy_marshal_array_constructor (proxy=proxy@entry=0x561a2cab0f30, opcode=opcode@entry=0, args=args@entry=0x7ffd6ea6b670, interface=interface@entry=0x7fd2adc0bac0 <wl_shm_pool_interface>) at ../src/wayland-client.c:599
 wl_proxy_marshal_constructor (proxy=proxy@entry=0x561a2cab0f30, opcode=opcode@entry=0, interface=0x7fd2adc0bac0 <wl_shm_pool_interface>) at ../src/wayland-client.c:733"
1745115,2018-01-24 09:20:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745118,2018-01-29 00:04:42 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1745118,2018-01-31 16:18:45 UTC,It looks like the same issue occurs on Intel Core 2 Duo CPU P9400 @ 2.40Ghz with i686 Xubuntu with Kernel linux-image-4.13.0-32-generic.
1745118,2018-02-01 10:45:34 UTC,"I had bisected this issue and I had reported upstream on 19 Jan:
https://bugzilla.kernel.org/show_bug.cgi?id=198529."
1745118,2018-02-02 15:17:55 UTC,"SRU request sent to the kernel team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089895.html"
1745118,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1745118,2018-02-16 16:52:37 UTC,Same problem here when trying to use kernel 4.13.0-32-generic on a Macbook Pro. Reverting to the previous kernel on this machine 4.10 is my current only choice/solution.
1745118,2018-02-21 10:08:59 UTC,"Node fozzie, onza, onibi (these three nodes are affected by this bug) can boot with the proposed 4.13.0-36-generic #40~16.04.1-Ubuntu i386 kernel."
1745118,2018-01-26 04:19:34 UTC,"Hi William,
I got your kernel verified on 4 affected system with 3 different CPU (ES-2403, X3430, X3470), I can boot the system with your 4.13.0-31 kernel."
1745118,2018-02-14 09:37:46 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1745118,2018-01-25 10:17:11 UTC,"I've only been able to reproduce this on systems with an Intel IOMMU. Disabling the IOMMU in the firmware (usually labelled ""VT-d"") lets the latest 4.13 i386 kernel boot. It's also reproducible in qemu if you give it an IOMMU, eg. ""-machine q35 -device intel-iommu""."
1745118,2018-01-24 09:59:44 UTC,apport information
1745118,2018-01-24 09:59:42 UTC,apport information
1745118,2018-01-24 09:59:41 UTC,apport information
1745118,2018-01-24 09:59:40 UTC,apport information
1745118,2018-01-24 09:59:38 UTC,apport information
1745118,2018-01-24 09:59:37 UTC,apport information
1745118,2018-01-24 09:59:36 UTC,apport information
1745118,2018-01-24 09:59:35 UTC,apport information
1745118,2018-01-24 09:59:34 UTC,apport information
1745118,2018-01-24 09:59:32 UTC,apport information
1745118,2018-01-24 09:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745118,2018-01-24 09:59:31 UTC,apport information
1745123,2018-03-06 15:07:47 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1745123,2018-01-25 22:19:55 UTC,The kernel OOPS is easily reproducable with the following c program and kernel 4.13.0-31-generic
1745123,2018-07-24 09:31:56 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1745123,2018-01-24 23:46:18 UTC,Just confirming this bug with the same exact versions in Linux Mint:
1745123,2018-01-24 09:30:14 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745123,2018-01-25 16:25:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745123,2018-01-24 17:49:52 UTC,ElasticSearch doens't log anything itself. There's just this in journalctl -xe
1745134,2018-01-24 19:34:28 UTC,Me too.
1745134,2018-01-25 08:33:37 UTC,I confirm that rolling back the kernal fixes the problem.
1745134,2018-01-24 16:10:39 UTC,Can confirm I'm also affected by this bug:
1745134,2018-01-24 17:36:40 UTC,Same here.
1745139,2018-03-08 18:49:05 UTC,There is a link to the RSS feed in the right hand column: https://www.openstack.org/blog/?feed=rss2
1745139,2018-03-09 04:29:43 UTC,Thanks. I filed this issue prior to noticing the link you mentioned. Adding the type attribute to the link would still be helpful for autodiscovery.
1745143,2020-02-05 17:04:35 UTC,As we are dropping the support of PPA. We won't fix this PPA related issue.
1745143,2020-01-03 10:35:47 UTC,@alm
1745143,2018-12-06 21:26:44 UTC,"Can this get a higher Importance? A lot of embedded developers
have to deal with multiple embedded toolchains, including AVR
and ARM. Today, the only solution is to not install gnu-arm-embedded
and to unpack a tar file instead."
1745143,2019-03-09 12:50:38 UTC,"As a workaround to make gcc-avr from the Ubuntu repository co-exist with the latest gcc-arm-embedded, I added the following diversions to move the files installed by gcc-avr to /usr/lib/gcc/avr/5.4.0:
dpkg-divert --package gcc-arm-embedded --divert /usr/lib/gcc/avr/5.4.0/libcc1.so --rename /usr/lib/libcc1.so
dpkg-divert --package gcc-arm-embedded --divert /usr/lib/gcc/avr/5.4.0/libcc1.so.0 --rename /usr/lib/libcc1.so.0
dpkg-divert --package gcc-arm-embedded --divert /usr/lib/gcc/avr/5.4.0/libcc1.la --rename /usr/lib/libcc1.la
dpkg-divert --package gcc-arm-embedded --divert /usr/lib/gcc/avr/5.4.0/libcc1.so.0.0.0 --rename /usr/lib/libcc1.so.0.0.0"
1745143,2019-01-09 09:46:12 UTC,"Hello,
It would be very useful if this could be fixed soon-ish. Whereas the gcc-arm from standard ubuntu-16.04 worked great, the one in 18.04 does not and the ARM guys recommend installing the ARM pushed version from a PPA. Sure I would like to have the one in the ubuntu repositories to work, but it does not generate working binaries for me."
1745143,2018-12-07 15:39:37 UTC,"Hello,
it would be highly appreciated if this could be fixed soon. In the meantime, is there a definite work-around without corrupting neither AVR nor ARM builds?
Is the ""--force"" hack producing valid builds for either platform?"
1745143,2018-09-19 00:05:58 UTC,"My bad, yes indeed. I checked the File listing for the all packages and gcc-avr is the only one having libcc1 in /usr/lib. All other GCC native and cross-compilers have it in another path. I still think that we should have things under /usr/lib/gcc-arm-embedded instead of /usr/lib to avoid that sort of issues."
1745143,2018-08-31 12:53:50 UTC,Uneable to install gcc-arm-embedded_7-2018q2 to Ubuntu 18.04.1 LTS
1745143,2018-09-12 10:35:21 UTC,"The problem only occurs when installing several toolchains from PPA or tarball since Ubuntu-provided toolchain have their own path. The solution would require to put the relevant files in a path specific to the toolchain being installed. Beside the work needed to do the change and test it, it makes the PPA a bit more different from our tarball release which is not a very desirable feature. You can avoid this issue by installing from tarball since this can be extracted into any directory."
1745143,2018-09-12 15:59:40 UTC,"> The problem only occurs when installing several toolchains from PPA or tarball...
"
1745143,2018-03-04 19:26:05 UTC,"Hi ,"
1745143,2018-03-06 13:14:27 UTC,"Hi Nabil,"
1745143,2018-01-26 10:07:45 UTC,"Hi,"
1745143,2018-09-06 22:22:09 UTC,Probably not the best solution. But I managed to get around this issue by force installing gcc-avr:
1745143,2018-09-06 16:34:47 UTC,I see the same error when trying to install `gcc-avr` on a Ubuntu-18.04 system with `gcc-arm-embedded` already installed.
1745143,2018-09-06 22:42:20 UTC,"Definitely non-ideal, but a reasonable workaround in the short term. FWIW I did it in the opposite order (uninstalling gcc-arm-embedded, installing gcc-avr, installing gcc-arm-embedded with --force-all hack) -- in my case, it's more important that my ARM installation work reliably than it is my AVR one do so."
1745148,2019-05-03 16:24:11 UTC,"The attachment ""fix SIGSEGV when entering non-ASCII characters"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1745148,2019-05-03 14:38:00 UTC,"tcsh's Char type is signed, but its input handling doesn't check for negative values, such as those created when non-ASCII characters are sign-extended.  Attached is a patch that addresses the reported problem (tested on 18.04).  Fixing the bigger issue of unsafe signed type promotion is left as an exercise for the reader."
1745149,2018-01-24 14:34:54 UTC,"Looks like a Nova problem. We need the logs from this, but my assumption is the Cinder volume is indeed attached and therefore in-use, so Cinder is working as expected."
1745149,2020-09-28 13:53:58 UTC,"This is actually invalid, failure during spawn should actually result in the volume remaining attached and in-use as happens now. We could call _disconnect_volume when we hit an error during attach_encryptor but I believe we should also clean this up when the instance is destroyed anyway."
1745149,2020-03-26 09:23:04 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/549469
Reason: This patch is stale. Feel free to restore it (or gibi on IRC to do so) if you are still working on this."
1745149,2018-01-26 09:54:02 UTC,"IMO, we should unreserve volume if the volume is root disk when fail to boot an instance from volume."
1745149,2018-03-03 14:07:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549469"
1745149,2018-01-26 01:12:38 UTC,"I think the second thought is better, which really covers all possible failures and rollback the volume to normal status."
1745149,2018-01-25 20:26:43 UTC,"On second thought, it might be best to catch all Exception during the encryptor attach attempt and just re-raise that. Because if the encryptor attach fails for any reason, we need to disconnect the volume."
1745149,2018-01-25 20:09:35 UTC,"Adding more notes on what I think needs to be done. I did some digging and found that what's happening is the volume is connected to the instance in the libvirt driver, *then* it tries to attach the encryptor and the encryptor attach fails because the fixed_key config option hasn't been set. So the instance spawn fails but the volume remains connected. We need to try-except around the encryptor attach attempt and disconnect the volume before re-raising."
1745149,2018-01-25 19:18:52 UTC,"This looks valid to me. During the boot process, it's failing to attach the volume because CONF.key_manager.fixed_key = None. We should handle that exception and roll back the volume status via Cinder calls as things are getting cleaned up."
1745149,2018-01-25 14:59:59 UTC,"From nova-compute:
=================="
1745149,2018-01-26 01:13:13 UTC,"If this is OK, I will try to fix it."
1745149,2018-01-26 09:45:03 UTC,"After disconnect volume, the volume will keep in ""reserved"" status. Not only this case, in fact once instance build abort(like bind port fail), the status of volume will be set to ""reserved"". I'm really not sure whether it's our expected status or not."
1745155,2020-01-21 07:13:28 UTC,This bug was fixed in the package ocfs2-tools - 1.8.6-2ubuntu1
1745155,2019-12-09 13:06:31 UTC,"Frank,"
1745155,2019-12-08 04:38:50 UTC,Change has been accepted upstream:
1745155,2019-11-29 15:07:15 UTC,This is the upstream suggestion:
1745155,2019-11-21 19:02:40 UTC,Eoan needs fixing for the s390x migration for its next SRU.
1745155,2019-11-21 19:01:20 UTC,"Alright, time has come. I need to fix focal for the s390x merge as s390x is not supported:"
1745155,2019-09-06 03:27:34 UTC,As:
1745155,2019-09-23 18:01:34 UTC,"Talking to @paelzer, we both agreed that whitelisting architectures is the best alternative, instead of having a little/big endian test added to the test, adding complexity and a bigger delta to be maintained."
1745155,2019-09-04 11:02:16 UTC,I got this when doing a fix for LP: #1840958.
1745155,2019-09-04 11:51:30 UTC,Based on:
1745155,2019-09-06 03:28:17 UTC,The merge request:
1745155,2019-09-06 02:28:04 UTC,"(gdb) bt
#0  0x000002aa0001baa4 in ocfs2_image_mark_bitmap (ofs=0x2aa0005a2c0, blkno=236353) at image.c:254
#1  0x000002aa00007678 in traverse_extents (ofs=0x2aa0005a2c0, el=0x2aa0007a8c0) at o2image.c:117
#2  0x000002aa00007faa in traverse_inode (ofs=0x2aa0005a2c0, inode=10) at o2image.c:317
#3  0x000002aa00007474 in traverse_group_desc (ofs=0x2aa0005a2c0, grp=0x2aa00077c00, dump_type=2, bpc=4) at o2image.c:76
#4  0x000002aa00007876 in traverse_chains (ofs=0x2aa0005a2c0, cl=0x2aa00076cc0, dump_type=2) at o2image.c:155
#5  0x000002aa00007e7c in traverse_inode (ofs=0x2aa0005a2c0, inode=12) at o2image.c:291
#6  0x000002aa00008f38 in scan_raw_disk (ofs=0x2aa0005a2c0) at o2image.c:633
#7  0x000002aa000096fc in main (argc=3, argv=0x3fffffffc18) at o2image.c:780"
1745155,2019-09-04 14:30:19 UTC,"Weird,"
1745155,2019-09-06 02:31:19 UTC,"With that, and after talking to some other engineers, we decided it is best, instead of whitelisting little endian arches, make the build process to fail whenever this can occur, which, right now, after investigation, is only related to how bitmaps are disposed in the imgfile (and mapped using (char *) w/out any endian converstion)."
1745158,2018-01-24 14:32:00 UTC,"StacktraceTop:
 gtk_application_impl_set_menubar (impl=0x0, menubar=0x0) at ../../../../gtk/gtkapplicationimpl.c:132
 gtk_application_set_menubar (application=0x564af64a1390, menubar=menubar@entry=0x0) at ../../../../gtk/gtkapplication.c:1121
 application_set_menubar (model=model@entry=0x0) at ./src/Application.vala:103
 library_window_switch_to_page (self=self@entry=0x564af6a59b80, page=page@entry=0x564af71fab80) at ./src/library/LibraryWindow.vala:1219
 library_window_on_sidebar_entry_selected (selectable=<optimized out>, self=0x564af6a59b80) at ./src/library/LibraryWindow.vala:1335"
1745158,2020-04-09 13:42:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745159,2018-08-31 07:44:36 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1745159,2018-08-31 07:44:46 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/537407
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1745159,2018-01-30 12:33:12 UTC,"IIUC, it prevents using two networks with different network types with macvtap driver."
1745159,2018-01-24 14:49:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/537407"
1745159,2018-01-30 13:06:39 UTC,exactly!
1745165,2018-07-26 11:40:24 UTC,Multiple package install failures like:
1745165,2018-07-26 11:42:45 UTC,Moving bug task to dpkg as this is not an issue that's specific to python-asn1crypto on this install.
1745169,2018-01-24 17:48:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745169,2018-01-24 22:39:35 UTC,"In addition to the other fun with 4.13, it also includes the Meltdown changes in 4.13.0-1004, and Spectre changes in 4.13.0-1006. Have you tried other kernels in the 4.13 line?"
1745169,2018-01-25 20:14:16 UTC,"Is this a 100% repro? If yes, can you check if adding the ""nopti"" kernel parameter can fix the issue?"
1745169,2018-01-26 15:51:26 UTC,"A new round of kernels was released last night, including Linux-azure-4.13.0-1007... are you still seeing this trace?"
1745169,2018-01-26 16:36:27 UTC,"Thanks for the update, I will try it on next Monday."
1745169,2018-01-26 20:21:39 UTC,"Issue went away after I upgraded.
4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linu"
1745169,2018-01-29 13:17:31 UTC,"I retried this morning, and problem solved!
Thanks"
1745170,2019-07-03 17:33:42 UTC,We're tracking this through the capacity spreadsheet.
1745174,2020-01-06 11:13:36 UTC,"Hello,
4.13.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1745176,2019-02-21 20:14:12 UTC,This bug was fixed in the package ubuntukylin-meta - 0.35
1745176,2018-01-24 21:35:50 UTC,This bug was fixed in the package ubuntu-budgie-meta - 0.25
1745176,2018-01-24 20:36:47 UTC,This bug was fixed in the package ubuntu-mate-meta - 1.212
1745177,2018-01-25 16:25:23 UTC,"I think this is not likely a duplicate. It appears in Xubuntu 16.04. And I am not talking about the details box during downloading or installing, but especially when it has displayed available updates."
1745185,2018-05-01 14:24:58 UTC,"This occurs with all mysql versions when upgrading, also on cloud instances. Can confirm that the solution works for mysql 5.6 and 5.7 as well. Other affected users discussing the solution can be found here: https://askubuntu.com/a/762775/762848"
1745185,2019-11-18 19:44:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745185,2018-10-31 23:55:12 UTC,https://salsa.debian.org/mariadb-team/mysql/commit/7fae702b6c3b6347008ec9b73a92cba6804111bc is a possible fix but I think there might be other commits needed as well.
1745185,2018-05-01 14:20:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745185,2018-10-31 18:39:06 UTC,"Trusty doesn't have systemd, but upstart. There the steps were:
- disable updates and security in /etc/apt/sources.list
- install mysql-server-5.5
- use mysql command line to connect and create a test database
- stop mysql: stop mysql
- disable mysql: echo manual | sudo tee /etc/init/mysql.override
- reboot to confirm mysql won't start automatically (yes)
- re-enable updates and security in sources.list
- apt dist-upgrade"
1745185,2018-10-31 18:27:34 UTC,"This is what I used to test:
- disable updates and security in /etc/apt/sources.list
- install mysql-server-5.7 (or whatever version is shipped in that release of ubuntu)
- use mysql command line to connect and create a test database
- stop mysql: sudo systemctl stop mysql
- disable mysql: sudo systemctl disable mysql
- re-enable updates and security in sources.list
- apt dist-upgrade"
1745185,2018-10-31 23:54:10 UTC,"The Xenial failure sounds very much like bug 1592669, which looks like it was fixed post-Xenial and hasn't had a fix backported (it's somewhat invasive but probably SRU-able if done with care)."
1745188,2018-01-24 17:25:57 UTC,"StacktraceTop:
 mpfr_assert_fail (filename=filename@entry=0x7fe4f8b5d6b0 ""../../src/init2.c"", linenum=linenum@entry=52, expr=expr@entry=0x7fe4f8b5d098 ""p >= 2 && p <= ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))"") at ../../src/mpfr-gmp.c:305
 mpfr_init2 (x=x@entry=0x7fffef865540, p=p@entry=1) at ../../src/init2.c:52
 mpc_init3 (x=x@entry=0x7fffef865520, prec_re=prec_re@entry=64, prec_im=prec_im@entry=1) at init3.c:27
 mpc_pow_usi_naive (z=z@entry=0x55f8ffbc8400, x=x@entry=0x55f8ffbc8460, y=y@entry=3, sign=sign@entry=-1, rnd=rnd@entry=0) at pow_ui.c:31
 mpc_pow_usi (z=0x55f8ffbc8400, x=0x55f8ffbc8460, y=3, sign=-1, rnd=0) at pow_ui.c:77"
1745188,2018-01-25 06:54:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745188,2018-01-25 07:56:41 UTC,Thanks for your report.
1745188,2018-01-25 08:02:53 UTC,confirmed by installating libmpc3 1.1.0-1 from bionic-proposed;
1745188,2018-01-25 08:17:19 UTC,This is because the precision is set to 1 in libmpfr 4.0.0 (in bionic-proposed) and 2 in libmpfr 3.1.6
1745188,2018-02-20 10:37:59 UTC,"Hello,"
1745188,2018-02-20 10:45:17 UTC,"<< reposting my previous comment in the aligned format as there seems to
be no option to edit it >>"
1745188,2019-01-10 14:19:18 UTC,"There are no report from 3.28 or newer, seems to be resolved"
1745190,2018-05-01 19:39:36 UTC,I am seeing the same behavior with the Show Results from All Libraries checkbox.
1745190,2018-01-25 20:11:35 UTC,This problem also seems to occur with the Group Formats & Editions checkbox.
1745190,2018-01-25 20:10:09 UTC,"This appears to be another case, similar to the one reported in bug 1739666, where enabling jquery breaks some of our existing javascript functions."
1745191,2018-01-25 00:23:44 UTC,"The attachment ""A fix for this bug"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1745191,2018-03-05 19:48:06 UTC,ping?
1745191,2018-03-28 23:35:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745191,2019-12-12 13:52:25 UTC,"Thank you for your bug report and patch and sorry for the lack of reply. The fix is included in Ubuntu from newer versions now, closing the bug"
1745192,2018-01-24 18:07:58 UTC,"This is arguably a proposal to change behavior somewhat, so I marked it with 'rfe' tag for drivers team to chime in before we recommend someone to pursue it."
1745192,2018-02-02 13:16:52 UTC,"this sounds like a variation of the old topic.
that is, how to handle the different set of features among ml2 drivers. (sg, qos, ...)
unfortunately we don't have a clear answer yet as far as i know.
port-binding time failure might not be very user-friendly. i don't think of any better alternative though."
1745192,2018-03-30 14:52:07 UTC,"Approved. There was some discussion in the drivers meeting about improving the error reporting to the users when drivers fail the binding, but it was considered tangential to the RFE. Worth exploring anyhow"
1745196,2018-01-24 20:29:39 UTC,"Yes, it fails somewhere above 200000 parameters.  That makes me wonder why call-arguments-limit and lambda-parameters-limit are so much higher."
1745196,2018-01-24 20:07:16 UTC,(apply #'/= list) is a nice way to blow the stack.
1745196,2018-11-17 00:30:17 UTC,"Granted that >2 arguments is not a typical case, the argument list can be sorted and each consecutive pair compared for inequality.  This is O(n log n) rather than O(n^2), though it does require n additional cons cells; it is slower but less space overhead than a hash table."
1745196,2018-01-24 19:48:33 UTC,Are 60 argument calls to /= as frequent and useful as large arrays?
1745196,2018-01-24 19:40:27 UTC,"It's more than the mandated minimum value of call-arguments-limit, but the actual value of that constant in my 64 bit SBCL is 4611686018427387903."
1745196,2018-01-24 19:21:50 UTC,Who calls /= with 60 arguments? That's even more than call-arguments-limit.
1745196,2018-01-24 19:55:23 UTC,"Specifically for /=?  Probably not (although (apply #'/= list) is a nice way to ask if there are any duplicates in list.)   The general (apply fn list) idiom occurs with many n-ary builtins, and it would be nice to be able to apply it to arbitrary lists.  I know this is not completely portable."
1745198,2019-09-19 11:57:14 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1745203,2018-11-15 10:07:23 UTC,"Not just opening the grbjob, but opening all the gerbers directly."
1745203,2018-11-13 23:36:03 UTC,"*Read GeberViwer canvas on ""Pcbnew"" word"
1745203,2018-11-13 23:34:53 UTC,"Yes, still some, using the GERBERs that I attached on"
1745203,2018-11-13 21:16:38 UTC,"Do we still have a performance issue when switching canvases in GerbView, or can this be closed?"
1745203,2018-09-12 12:22:50 UTC,The process bar feature is duplicated at https://bugs.launchpad.net/kicad/+bug/1780123
1745203,2018-03-03 03:07:04 UTC,"@Jon, yes, the progress bar is Low priority."
1745203,2018-03-03 02:47:53 UTC,What problem do you see when you switch graphical modes?
1745203,2018-03-02 00:18:23 UTC,"I tried in my older machine, same software (OS) configuration:
1) Yes!
2) I saw the process bar (maybe it could be in the bottom toolbar of GergerView, but works nice);
3) Still this issue of switching graphical modes."
1745203,2018-03-01 20:22:42 UTC,"Not a leap year. :-D
Report from 201803011436+ce1bd4c~62~ubuntu16.04.1:
1) Open the file attached in this issue is ok now, much better. Thanks;
2) I didn't see the process bar (maybe because the Job GERBER file was considered not to long?);
3) The problem still when I switch between the graphical modes in the preferences menu."
1745203,2018-02-28 17:26:50 UTC,"@Hildo could you please try the next nightly (29-Feb) and let me know what you think?  There is now a progress bar for long file loads, and many other small issues have been fixed."
1745203,2018-02-05 12:04:37 UTC,"@Evans, I opened a a different bug relating this (https://bugs.launchpad.net/kicad/+bug/1747409). How can I do the stack trace for help you?"
1745203,2018-02-02 10:46:38 UTC,"Thanks @Jon Evans, the #1 is really fixed.
But #2, now (20180202540+b420845~61ubuntu16.04.01), happens in all Modern Canvas (Accelerated and Fallback) for all GEBERs that I have, even GerbView now is not just freezing but closing.
In Legacy graphics mode all is fine."
1745203,2018-01-29 14:14:58 UTC,"#1 is fixed, #2 is still open, so setting back to Confirmed"
1745203,2018-01-29 07:13:54 UTC,"Fixed in revision 14abe8723db6fddfa6c6207688fec2c36a7cc818
https://git.launchpad.net/kicad/patch/?id=14abe8723db6fddfa6c6207688fec2c36a7cc818"
1745203,2018-01-26 11:48:28 UTC,"@Jon,
Do your best. You are one of your GAL specialist, and we have very few GAL specialists."
1745203,2018-01-25 22:08:18 UTC,"@crafyjon, I agree if the (1) and (2).
Sure, the size of the board (quantity of track and vias) create a long gerber file, is understandable that will be slower than ""common"" designs (also the  3D generation in pcbnew is quite slow because this).
So, fix (1) and the menu is priority of the issue (my point of view). And if some enhancement of Geberview could be done, will be nice to future user that try large designs (but this is a enhancement, not a bug fix, so can be treated more calmly)."
1745203,2018-01-25 20:49:20 UTC,FYI I think there are two things to tackle here:
1745203,2018-01-25 10:34:32 UTC,"In modern fallback and legacy works normally. Now that I test, I saw that even after the files be loaded (in other graphical mode), just change the graphic mode to modern-accelerated causes the same issue."
1745203,2018-01-25 10:31:51 UTC,"@jean, I agree selecting all the GERBERs files (not the gbrjob) works normal (sure, after I have to load the drills).
I am using modern accelerated mode."
1745203,2018-01-25 07:53:08 UTC,"I confirm loading these files is *very* slow in OpenGL mode, and fast in other modes (Legacy or Cairo) (W7 32bits)."
1745203,2018-01-25 02:09:24 UTC,"Are you using legacy graphics or modern (accelerated or fallback)?
I will check on my machine later and see if it has the same issue.
Thanks"
1745203,2018-01-24 23:25:59 UTC,"I just tested now other PC (same OS and KiCad compilation). Same behavior, slow load and the menu problem."
1745203,2018-01-24 23:23:10 UTC,"I don't if is related with the graphical card. I just tested now other PC (same OS and KiCad compilation). The gbrfile is loaded well, just the menu that I highlighted still strange."
1745203,2018-02-04 17:10:08 UTC,"Hi Hildo, if you are getting closing (crash?) please open a new bug with a stack trace if possible.  I will consider this bug to track the issue that OpenGL canvas is slow to load when you give it lots of complicated files, but if you are actually getting a crash that is a different bug."
1745203,2018-01-24 22:56:30 UTC,"Are you able to share your gerber files (either here, or in private email to one of the developers?)   After the freeze, does it eventually start working?"
1745206,2018-03-03 05:36:26 UTC,This bug was fixed in the package gtk3-nocsd - 3-1ubuntu1
1745206,2018-03-03 04:49:30 UTC,Uploaded.
1745206,2018-02-28 17:21:44 UTC,I think Ubuntu should distro-patch it util it get accepted. Subscribing ubuntu-sponsors. See https://community.ubuntu.com/t/gnome-3-28-status/4141/24
1745206,2018-01-25 00:23:54 UTC,"The attachment ""improve-session-detection.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1745206,2018-01-25 02:25:46 UTC,Is this effectively an explanation/duplicate of bug 1745070?
1745206,2018-01-26 09:08:52 UTC,bug 1745070 should be duplicate of this bug. I already send this bug link to debian.
1745211,2019-11-04 22:24:17 UTC,"Bingo.  We experienced a brief LP outage over the weekend, which the new watchdog detected and correctly resolved by restarting the service.  So the new code is successfully handling the error condition now."
1745211,2019-11-01 21:43:05 UTC,"I suspect this is probably adequately addressed now by commit 5d104bce612db56f3274c667ee7b008da5e68c18 (LP: #1838954), which adds a watchdog that will kill and restart the process if it gets hung.  There's some delay in the restart for giving LP a chance to restore itself."
1745211,2018-01-25 12:51:23 UTC,"If libcurl is used at some point, it has a parameter to kill the connection if it the transfer speed is below a certain threshold."
1745215,2018-01-24 20:36:21 UTC,I think it would make sense not to inlude all the clients. since they will never be used anyway.
1745215,2018-01-29 07:55:14 UTC,"Please be aware we are refactoring things to prevent the need of building wheels, and just installs things in venvs."
1745215,2018-01-29 07:56:08 UTC,"Major, because you're assigned on this, could you have a look at what can be done on heat side? Else I will do it."
1745215,2018-01-29 12:57:04 UTC,"I'll gladly unassign myself, JP. I wasn't aware of that work to avoid building wheels anyway."
1745215,2018-02-20 21:55:22 UTC,Opened a heat bug: https://bugs.launchpad.net/heat/+bug/1750674
1745215,2018-02-20 22:09:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/546319"
1745215,2018-02-20 22:11:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/546331"
1745215,2018-03-07 13:42:43 UTC,"Change abandoned by Major Hayden (<email address hidden>) on branch: master
Review: https://review.openstack.org/546319"
1745215,2018-03-07 13:42:48 UTC,"Change abandoned by Major Hayden (<email address hidden>) on branch: master
Review: https://review.openstack.org/546331"
1745243,2018-01-25 00:24:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1745245,2018-01-27 00:16:05 UTC,The triage for now is to ensure that clients send an etag with the request. This will enable the object servers to validate the computed checksum against a known baseline and fail if it doesn't match.
1745245,2018-01-25 18:56:08 UTC,For replicated objects this isn't currently easy to solve.  For EC and encryption the MIME/chunked packing protocol supports the proxy sending metadata after the object body which the object-server should consider before the finalize.
1745247,2018-01-26 22:03:10 UTC,For linux-azure: https://lists.ubuntu.com/archives/kernel-team/2018-January/089627.html
1745247,2018-01-26 22:12:40 UTC,"Anywhere where you've patched for Meltdown. If PCID is not visible to the guest, there's a TLB flush on every syscall, even when it's not necessary."
1745247,2018-01-26 22:27:30 UTC,Will this patch land for 4.15? Otherwise I will include it to bionic too.
1745247,2018-01-29 17:18:18 UTC,"Xenial and trusty kernels do not support TLB flush via Hyper-V hypercalls, thus the fix is not necessary on those kernels."
1745247,2018-01-29 17:19:39 UTC,The same is true for artful.
1745247,2018-02-06 20:09:50 UTC,This bug was fixed in the package linux-azure - 4.13.0-1009.12
1745247,2018-01-26 21:49:41 UTC,Josh. Is that intended to be included in both the custom kernels as well in the regular kernels?
1745248,2018-01-25 09:06:03 UTC,"To be fair, one is being done inside a SHELL and the other would have to be
changing our prompts from being ""Scanf()"" to something that would probe for
every character typed, and work in a much more interactive fashion."
1745249,2018-01-25 20:42:03 UTC,"Thanks, Elaine. Your finding is very helpful already. :-)"
1745249,2018-01-25 20:18:35 UTC,"Thanks, Elaine, for testing it."
1745249,2018-03-01 14:29:34 UTC,"I am also seeing this behavior in 3.0.3 when searching multiple sources. My search had 271 total hits.  The interface should be showing 10 rows, but I'm seeing 21.  When I page forward using the arrow (next to actions), I see a Total Hits of 27, but only 10 display.  When I use the page dropdown, the message is No Items to Display."
1745249,2018-01-25 17:10:35 UTC,page 2
1745249,2018-01-25 19:06:31 UTC,"I am definitely not seeing the issue with OCLC. Whether I look at 5 or 100 rows, it maintains the correct numbering as I page through. We do not use any other bib source."
1745249,2018-01-25 20:28:41 UTC,"We only use OCLC as a source, so I can't test that for you."
1745249,2018-01-25 17:10:04 UTC,"I searched various targets for different terms with various result sizes (from a few to a few hundred, up to thousand). I tried all the Rowxx. It does not seem these parameters matter."
1745249,2018-01-25 14:50:34 UTC,I am not seeing this behavior when retrieving records from OCLC. Row numbering is consistent for me.
1745250,2019-05-26 19:30:46 UTC,Tagged as snacked-sized as the code change may be small but the initial testing will probably be an effort
1745250,2020-02-11 02:51:44 UTC,This was fixed in another patch: https://bugs.launchpad.net/mahara/+bug/1772792
1745256,2018-12-03 05:21:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745256,2018-12-03 05:23:04 UTC,I get the same error on loading 'wl' (and the exact same 19 unknown symbols in dmesg) from installing bcmwl-kernel-source on Xenial.
1745258,2018-01-25 00:35:46 UTC,This bug/behavior appeared in 17.10.
1745258,2018-01-25 04:22:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1745259,2018-01-25 00:41:39 UTC,"StacktraceTop:
 query_seat_path (listener=0x55a578341070) at gs-listener-dbus.c:2220
 init_seat_path (listener=0x55a578341070) at gs-listener-dbus.c:2278
 gs_listener_init (listener=0x55a578341070) at gs-listener-dbus.c:2296
 g_type_create_instance (type=<optimized out>) at ../../../../gobject/gtype.c:1866
 g_object_new_internal (class=class@entry=0x55a57834d620, params=params@entry=0x0, n_params=n_params@entry=0) at ../../../../gobject/gobject.c:1797"
1745259,2018-01-25 06:03:34 UTC,I couldn't apt-get remove light-locker because I would have to remove lubuntu-desktop.  I ended up switching my window manager to lightdm.
1745259,2018-02-09 15:56:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745259,2019-07-29 16:43:08 UTC,"I have automatic lock disabled in power manager, yet light-locker crashes with SIGTRAP (5) (Trace/breakpoint trap) when I resume from sleep. Why does it use the breakpoint signal? That should be reserved for the debugger to use. Why is it running when I have requested no locking of the session?"
1745259,2019-10-01 18:40:01 UTC,I see this error when i xrdp to my ubuntnu server 18.04 after i have installed lubuntu-desktop over it.
1745260,2018-02-06 20:09:50 UTC,This bug was fixed in the package linux-azure - 4.13.0-1009.12
1745260,2018-01-26 19:23:24 UTC,"We should apply it to the azure 4.13 kernel (and beyond), but I think we will jump azure-edge to 4.15 as soon as it GAs and seems stable in hopes of switching linux-azure to 4.15 as the next bump. This way linux-azure for 16.04 and 18.04 will be the same."
1745260,2018-01-26 19:11:55 UTC,Josh. Should that patch also be applied to the 4.14 azure-edge kernel?
1745260,2018-01-26 19:19:18 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-January/089621.html
1745261,2018-01-26 18:37:34 UTC,It was requested to enable CONFIG_SCSI_MQ_DEFAULT=y.
1745261,2018-01-26 18:59:39 UTC,"Yes, I didn't have a separate bug for that, but it is in the case that is the parent feature request of this LP and the other one."
1745261,2018-01-26 19:12:00 UTC,Josh. Does that Josh. Should that patch also be applied to the 4.14 azure-edge kernel?
1745261,2018-01-26 19:19:21 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-January/089621.html
1745261,2018-02-06 20:09:50 UTC,This bug was fixed in the package linux-azure - 4.13.0-1009.12
1745262,2018-01-25 00:57:21 UTC,dhcp-agent log
1745264,2020-08-27 17:55:46 UTC,"A error message could be improved: ""Authentication failed: macaroon has expired or is invalid."""
1745271,2018-01-25 09:11:53 UTC,"Does this also happen in xterm? If so then this is a bug in bash, not gnome-terminal."
1745271,2018-01-25 20:31:30 UTC,"Nope, not happening in xterm."
1745271,2018-01-25 23:16:59 UTC,I've reproduced your issue (using the exact same prompt string as yours). It's also buggy for me in xterm. I'm pretty sure it's a readline or bash issue.
1745271,2018-01-25 23:37:50 UTC,"Oh, sorry about that. Apparently, xterm uses a different value for PS1 than gnome-terminal by default. It seems that this issue only happens when color escape sequences are involved, which is why it didn’t happen for me in xterm. However, when I manually set xterm to the same value as in gnome-terminal, I also got the issue in xterm."
1745279,2018-02-01 11:09:34 UTC,"Hi Mendes,"
1745298,2018-01-25 06:34:36 UTC,Any other logs for this? :D
1745298,2018-01-26 10:28:25 UTC,I found this error log at the first time.
1745312,2018-01-29 13:37:35 UTC,"On Thu, Jan 25, 2018 at 07:18:52AM -0000, i336_ wrote:

> Public bug reported:
>
> [Headsup: This report is long-ish due to the amount of detail I've
> stumbled on along the way that I think is relevant to include. I can't
> speak as to the complexity of the actual bugs, but the size of this
> report should not suggest that the reproduction process is particularly
> headache-inducing.]
"
1745312,2018-01-30 07:10:38 UTC,"QEMU ignores the CHS numbers in VMDK images. From the report, it seems VirtualBox uses it."
1745312,2018-01-30 19:56:51 UTC,"Can you post your commandline for the MSDOS 6.22 issue? NT is known to have a few problems and may be out of scope for what I can help with, but I was under the assumption that MSDOS 6.22 was well-behaved in QEMU."
1745312,2018-04-30 18:06:29 UTC,I have a similar bug: 1674114
1745312,2019-08-01 18:19:22 UTC,"Can confirm the DOS issue is present.  Here are some steps to recreate:
wget http://www.freedos.org/download/download/FD12CD.iso
apt-get install mbr fdisk parted dosfstools qemu-system-x86
# dd if=/dev/zero of=dos.img bs=512 count=1032192
# losetup /dev/loop0 dos.img
# fdisk -u=cylinders /dev/loop0
command: x
expert: h
heads: 16 (you can try different values, 16, 32, 64, 128, 255)
expert: c
cylinders (default 1024):
expert: r
command: c
DOS compatibility flag is set...
command: n
select: p
partition (default 1):
first cylinder (default 1):
last cylinder (default 1024):
command: a
command: t
selected partition 1
type: 6
command: w
# partprobe /dev/loop0
# install-mbr -f /dev/loop0
# mkdosfs -F 16 /dev/loop0p1
# qemu-system-i386 -drive file=/dev/loop0,cache=none,format=raw,index=0 \
-drive file=FD12CD.iso,cache=none,media=cdrom,if=ide,format=raw,index=1 -boot d \
-machine isapc
--------
qemu comes up
""install to harddisk""
select your preferred language
""yes - continue with the installation""
drive C does not appear to be formatted
""yes - please erase and format drive c:""
lbacache flush write error 0c80/chs#0001
...
etc etc etc."
1745312,2019-12-23 21:35:46 UTC,"I will try to debug as time permits, but the priority of MS-DOS bugs is not ... measurable with casual tools. However, there are a lot of other IDE bugs on my plate that are very important! so I am hoping to grab a bunch of IDE bugs at once, but no promises here."
1745322,2018-02-01 09:48:23 UTC,Fixed by https://review.openstack.org/#/c/539146/
1745336,2018-01-25 10:12:08 UTC,"StacktraceTop:
 gtk_application_impl_uninhibit (impl=0x0, cookie=292583089) at ../../../../gtk/gtkapplicationimpl.c:148
 simple_scan_scanner_scanning_changed_cb (scanner=<optimized out>, self=0x559463b3f150) at src/simple-scan@exe/simple-scan.c:1678
 _simple_scan_scanner_scanning_changed_cb_scanner_scanning_changed (_sender=<optimized out>, self=0x559463b3f150) at src/simple-scan@exe/simple-scan.c:512
 g_closure_invoke (closure=0x559463da82b0, return_value=0x0, n_param_values=1, param_values=0x7ffdaf00e090, invocation_hint=0x7ffdaf00e010) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x559463da7d40, detail=detail@entry=0, instance=instance@entry=0x559463c4ceb0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffdaf00e090) at ../../../../gobject/gsignal.c:3635"
1745336,2018-01-26 08:31:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745336,2018-06-01 02:53:32 UTC,I've experienced a bug with a similar stack trace. I've attached my ~/.cache/simple-scan/simple-scan.log file.
1745338,2018-02-22 15:48:03 UTC,This bug was fixed in the package linux - 4.15.0-10.11
1745338,2018-02-22 14:16:25 UTC,This bug was fixed in the package linux - 3.13.0-142.191
1745338,2018-02-21 18:58:26 UTC,This bug was fixed in the package linux - 4.4.0-116.140
1745338,2018-02-14 09:41:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1745338,2018-02-20 10:59:33 UTC,"Verified that latest Trusty, Xenial and Artful kernels build on canonica-kernel-team/ppa has urgency=medium on the changelog."
1745338,2018-02-14 09:50:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1745338,2018-02-14 09:37:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1745338,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1745340,2018-02-09 07:13:17 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1745340,2018-06-16 18:29:07 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/564320
Reason: I don't have the resources to finish this backport and we're on Queens, abandoning.."
1745340,2018-04-25 19:14:47 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/564320"
1745340,2018-02-07 05:07:07 UTC,"Reviewed:  https://review.openstack.org/538003
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b92e3bc95fd69759031b7439b7f8392926910cc2
Submitter: Zuul
Branch:    master"
1745340,2018-01-25 19:05:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538003"
1745340,2018-01-25 14:07:49 UTC,"Nova should be explicitly adding USB host controllers, rather than relying on arch specific defaults in this area. That libvirt enabled USB by default on x86 is considered a mistake, so hasn't been copied on other architectures. Even on x86 it is better for Nova to explicitly add USB host controllers, since the default host controller model is USB1 which is a very poor choice."
1745340,2018-01-25 13:55:43 UTC,https://bugzilla.redhat.com/show_bug.cgi?id=1538637 reported for libvirt
1745340,2018-01-25 12:06:54 UTC,Change of libvirt defaults can handle that without nova changes.
1745340,2018-01-25 10:53:39 UTC,Keyboard presence is probably also assumed.
1745340,2018-01-25 10:36:01 UTC,You're going to want to modify this function:
1745340,2018-01-25 10:28:11 UTC,"host information:
- architecture: aarch64
- distribution: Debian/stable
- libvirt version: 3.10.0
- nova version: Queens (2018.01.21 HEAD)"
1745342,2018-02-12 15:46:36 UTC,"The touchscreen works for John with the upstream 4.12 final kernel found here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/"
1745342,2018-02-12 15:33:21 UTC,"I just tried suspending with the 4.15 kernel, the touchscreen does not work after resume either."
1745342,2018-02-12 15:18:43 UTC,"Well, that's quite unfortunate."
1745342,2018-02-12 10:18:05 UTC,"Nice hypothesis! Sadly, with
Linux flimsy 4.15.0-9-generic #10~lp1745342 SMP Mon Feb 12 16:02:41 CST 2018 x86_64 x86_64 x86_64 GNU/Linux
it didn't work, but there's chatter in dmesg about it: Attaching in case it's useful."
1745342,2018-02-12 08:39:37 UTC,"First, kudos to Joseph, my guesswork is based on his hard work."
1745342,2018-02-11 19:56:05 UTC,"Disappointing news I'm afraid: with the bottom half,"
1745342,2018-02-09 21:43:53 UTC,"I'm bisecting through the config files manually.  I have two test kenrels, one should be good and one should be bad.  The test kernels are available here:"
1745342,2018-02-08 21:14:24 UTC,Thanks for testing.  Those are the config changes that stick out.  Next I'll try manually bisecting through the config file to figure out which one it is.  I'll have another test kernel shortly.
1745342,2018-02-08 16:51:07 UTC,"I have another test kernel to try:
http://kernel.ubuntu.com/~jsalisbury/lp1745342"
1745342,2018-02-12 15:48:01 UTC,"It might also be good to capture the same output from upstream v4.13-rc1, since the touchpad does not work with that kernel.  We can then do a diff of the two."
1745342,2018-02-07 21:54:51 UTC,"Hello,"
1745342,2018-02-07 21:18:03 UTC,"I have one more test kernel to try:
http://kernel.ubuntu.com/~jsalisbury/lp1745342"
1745342,2018-02-06 22:58:34 UTC,Hello!
1745342,2018-02-06 21:17:27 UTC,"Can you give the following kernel a try:
http://kernel.ubuntu.com/~jsalisbury/lp1745342"
1745342,2018-02-06 18:58:52 UTC,Hello again! Sorry for the delay.
1745342,2018-02-05 17:30:26 UTC,Thanks for testing.  I'll have to review some of the other config differences between 4.13.0-10 and 4.12.0-13.
1745342,2018-02-03 16:40:46 UTC,"There seem to be two kernels there, so I tried them both: the touchscreen didn't work with either of them."
1745342,2018-02-08 20:52:17 UTC,"flimsy:~$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342ConfigHAVEGENERICRCUGUP SMP Thu Feb 8 16:13:18 UTC  x86_64 x86_64 x86_64 GNU/Linux
flimsy:~$"
1745342,2018-02-12 17:08:34 UTC,"I put the two configs on http://people.canonical.com/~john/lp1745342/
Including a diff at http://people.canonical.com/~john/lp1745342/config-4.12.0-13_to_4.13.0-041300rc1.html"
1745342,2018-02-15 12:51:37 UTC,So let's focus on 7139.
1745342,2018-02-12 20:36:02 UTC,With
1745342,2018-07-24 09:31:59 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1745342,2018-02-20 13:24:21 UTC,Do you also lose the keyboard dock in v4.13?
1745342,2018-02-19 13:03:07 UTC,"Yes, I can confirm that with the 4.15.0-9 kernel with which the touchscreen works, if I disconnect the keyboard dock I need to power cycle (not just reboot) the machine to get it back."
1745342,2018-02-18 16:42:03 UTC,do you need other type of logs?
1745342,2018-02-15 15:18:04 UTC,"Kai, I don't use the 7139 with a keyboard dock. I have a keyboard dock on my 7140, and I can use it with my 7139 to test. I'll do that this evening and report back."
1745342,2018-02-15 13:18:59 UTC,"sorry for the delay but I'm having busy days, tonight or tomorrow I will send you the logs of dmsg. I have the 7139 model."
1745342,2018-02-02 22:56:46 UTC,"Comparing your two dmesg logs, I can see that the touchscreen is identified in the good dmesg, but nothing in the bad one.  Here's the message from the good one:
[    3.296644] input: SYNA7500:00 06CB:3AF0 as /devices/pci0000:00/INT33C3:00/i2c-9/i2c-SYNA7500:00/0018:06CB:3AF0.0002/input/input10
[    3.298646] hid-multitouch 0018:06CB:3AF0.0002: input,hidraw0: I2C HID v1.00 Device [SYNA7500:00 06CB:3AF0] on i2c-SYNA7500:00"
1745342,2018-02-14 13:11:32 UTC,"I apologize if you missed this, but I have moved on to Fedora 27. I'm
afraid I'm unable to help you with Ubuntu issues. The keyboard issue isn't
a problem for me anymore."
1745342,2018-02-14 09:19:32 UTC,@redx dmesg from after re-plugging the keyboard a few times might help?
1745342,2018-02-13 22:21:27 UTC,"On Feb 13, 2018 14:15, ""redx"" <email address hidden> wrote:"
1745342,2018-02-13 19:06:53 UTC,"I have tested the patch and the touch is detected correctly, but if I detach and then reattach the dock keyboard, the keyboard stops working until i reboot the tablet."
1745342,2018-02-13 18:31:06 UTC,The 7139 came back from suspend ~20 minutes later just fine.
1745342,2018-02-13 18:11:42 UTC,"Please attach the output of `cat /sys/firmware/acpi/tables/DSDT` for both 7139 and 7140, so we can see what their _STA methods look like."
1745342,2018-02-13 18:08:16 UTC,[  +0.000000] Linux version 4.15.0-9-generic (root@Ryzen) (gcc version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)) #10~lp1745342+3 SMP Wed Feb 14 00:02:23 CST 2018
1745342,2018-02-13 17:56:19 UTC,I'll try that in a moment.
1745342,2018-02-13 17:36:45 UTC,"Actually, there's a great hint:"
1745342,2018-02-13 14:06:05 UTC,"I moved on to Fedora 27. The bug is present in Fedora 27 as well. It was
not present in Fedora 26. It's the same story with Ubuntu....through bug
was not there in 17.04 but showed up in 17.10."
1745342,2018-02-13 09:29:52 UTC,https://people.canonical.com/~john/lp1745342/4.15.0-9.10~lp1745342+2/
1745342,2018-02-13 03:34:18 UTC,"Yea, but is its ACPI device alive? Please attach `dmesg` and `udevadm info -e`."
1745342,2018-02-12 18:30:57 UTC,"Okay, please try this,
http://people.canonical.com/~khfeng/lp1745342-acpi/"
1745342,2018-02-02 14:31:49 UTC,Here you go.
1745342,2018-02-01 08:00:30 UTC,Happy February!
1745342,2018-02-02 00:32:47 UTC,Nevermind comment #44.  I see that is already posted to the bug.  I'll see if I can see which config change could have caused this withing needing a bisect between those two versions.
1745342,2018-01-31 15:52:30 UTC,"$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311413 SMP Wed Jan 31 14:14:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-01-31 14:54:24 UTC,"I built the next test kernel, up to the following commit:
e442cbf910c71fba5926cf757dd7f8fcce22fc5f"
1745342,2018-01-31 06:48:04 UTC,"$ uname -a
Linux flimsy 4.12.0-041200-generic #201801302226 SMP Tue Jan 30 22:28:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-01-31 03:03:13 UTC,"I built the next test kernel, up to the following commit:
892ad5acca0b2ddb514fae63fa4686bf726d2471"
1745342,2018-01-30 22:12:23 UTC,"$ uname -a
Linux flimsy 4.12.0-041200-generic #201801302050 SMP Tue Jan 30 21:06:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-01-30 21:37:50 UTC,"I built the next test kernel, up to the following commit:
1b044f1cfc65a7d90b209dfabd57e16d98b58c5b"
1745342,2018-01-30 20:31:39 UTC,"$ uname -a
Linux flimsy 4.12.0-041200-generic #201801261837 SMP Fri Jan 26 18:39:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-01-30 20:22:34 UTC,"I built the next test kernel, up to the following commit:
cbcd4f08aa637b74f575268770da86a00fabde6d"
1745342,2018-01-26 18:24:35 UTC,Sorry for the delay :-) was at the doc's.
1745342,2018-01-26 17:11:47 UTC,"I built the next test kernel, up to the following commit:
1849f800fba32cd5a0b647f824f11426b85310d8"
1745342,2018-01-26 15:53:01 UTC,"$ uname -a
Linux flimsy 4.12.0-041200-generic #201801261443 SMP Fri Jan 26 14:46:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-01-26 15:18:58 UTC,I started a kernel bisect between v4.12 final and v4.13-rc1. The kernel bisect will require testing of about 7-10 test kernels.
1745342,2018-01-25 21:45:16 UTC,Linux flimsy 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1745342,2018-01-25 20:28:00 UTC,"Can you test v4.12 final to see if it also does not have the bug.  4.12.14 and 4.13-rc1 are not linear, so that's why we also need to test 4.12."
1745342,2018-01-25 17:26:42 UTC,With
1745342,2018-01-25 15:39:59 UTC,We can perform a kernel bisect to identify the commit that introduced this regression.  We first need to identify the last kernel version that did not have the bug and the first kernel version that did.
1745342,2018-01-25 13:20:02 UTC,"$ uname -a
Linux flimsy 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 02:31:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-01-25 12:24:00 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1745342,2018-01-25 11:00:09 UTC,This change was made by a bot.
1745342,2018-02-02 14:17:36 UTC,The lspci and dmesg attached to the bug are from when the touchscreen is not working.  Can you boot a kernel where the touchscreen does work and collect that info?
1745342,2018-01-31 17:16:41 UTC,At some point somebody will figure out how to do newton-raphson instead of bisect.
1745342,2018-01-31 16:45:45 UTC,Eventually one of these test kernels should work and narrow down the bisect :-)
1745342,2018-01-31 19:19:28 UTC,"$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311805 SMP Wed Jan 31 18:06:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-02-02 00:31:46 UTC,"Thanks for testing those two.  That really points at a config change.  Can you post the output from the following, so I can see the hardware info:"
1745342,2018-02-01 21:38:02 UTC,Linux flimsy 4.12.0-13-generic #14-Ubuntu SMP Sat Sep 2 15:52:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
1745342,2018-02-01 20:21:34 UTC,"Sorry, your right.  These are mainline kernels, so there is no -extra package."
1745342,2018-02-01 20:00:39 UTC,"with the one from 4.12/zesty-remote,"
1745342,2018-02-01 19:51:23 UTC,"Ah, ok then, I'll give it a try."
1745342,2018-02-01 19:21:46 UTC,"Do you need the headers file for something?  To test the kernel, you should only have to install the linux-image and linux-image-extra .debs."
1745342,2018-02-01 18:25:40 UTC,The linux-headers deb seems to be truncated in that one.
1745342,2018-01-31 18:20:36 UTC,"I built the next test kernel, up to the following commit:
fdd050b5b3c96813ae6756ed68157d32ba31b9f2"
1745342,2018-02-01 17:33:53 UTC,"Hmm, ok. I'm using a fit remote to artful for that build.  Let me try building the kernel using Zesty or Xenial remote."
1745342,2018-02-01 17:57:02 UTC,"Can you give the following kernel a try:
http://kernel.ubuntu.com/~jsalisbury/lp1745342/4.12/zesty-remote"
1745342,2018-02-01 15:42:59 UTC,"I built the next test kernel, up to the following commit:
9bddeb2a5b981507cbe2d7bdb545c32f204109c7"
1745342,2018-02-01 02:08:56 UTC,"I built the next test kernel, up to the following commit:
03ea8ad78cfb2910862c8dfcd2a627fc04097db2"
1745342,2018-01-31 23:36:20 UTC,I just confirmed that
1745342,2018-01-31 23:10:10 UTC,"I built the next test kernel, up to the following commit:
edea55abb86ff67afda96120d6254290e7a75d9e"
1745342,2018-01-31 22:17:29 UTC,"$ uname -a
Linux flimsy 4.12.0-041200rc2-generic #201801312121 SMP Wed Jan 31 21:23:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-01-31 21:47:54 UTC,"I built the next test kernel, up to the following commit:
b040ad9cf6a169cc000a5324fcada695dfa1f4b3"
1745342,2018-01-31 21:01:06 UTC,"$ uname -a
Linux flimsy 4.12.0-041200rc5-generic #201801311949 SMP Wed Jan 31 19:50:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745342,2018-01-31 20:47:16 UTC,"I built the next test kernel, up to the following commit:
a104c9f22c7d073d4ae308ca36383ce5cc4631cc"
1745342,2018-01-31 19:48:22 UTC,"To build these kernels, I use a script called mainline-build-one, which is in the kteam-tools repository[0]."
1745342,2018-02-01 16:15:34 UTC,"With the kernel in the 4.12 directory,"
1745346,2018-08-14 16:36:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745346,2015-07-07 02:52:26 UTC,"Thanks André, merged as http://git.xfce.org/apps/mousepad/commit/?id=720cf91f7b21864b4d3bb0ce18d96cfa719877ca"
1745346,2015-07-07 01:47:26 UTC,"Created attachment 6369
Improved patch"
1745346,2015-07-07 01:13:33 UTC,"Created attachment 6368
Quick patch"
1745346,2015-07-07 00:57:26 UTC,I tried looking into a bit but I haven't yet installed the sources for the GtkSourceView version on my machine.
1745346,2015-07-07 01:01:00 UTC,"I'm taking a look at this, so far this is where the crash happens:"
1745346,2015-07-07 01:06:46 UTC,"Ahhh ... it's a special base language definition, not a real language:"
1745346,2015-07-04 17:26:33 UTC,"Mousepad crashes when I click on ""Document"" > ""Type de fichier"" > ""Others"" > ""Defaults"""
1745346,2015-07-04 18:09:07 UTC,"Confirmed, it does it here to. I have no idea what file type ""Defaults"" is supposed to be. Will have a look and see why it's crashing."
1745346,2015-07-07 00:37:48 UTC,"Yeah, this crashes here when the editor is not empty.
GtkSourceView:ERROR:gtksourcecontextengine.c:5902:update_syntax: assertion failed: (state->context != NULL)
Aborted (core dumped)"
1745354,2020-11-24 16:47:33 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1745354,2021-01-24 04:17:30 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1745359,2019-09-16 08:45:11 UTC,Migrated to https://github.com/widelands/widelands/issues/3254
1745364,2018-03-19 10:55:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1745364,2018-03-21 09:55:39 UTC,"I have tested this with the kernel bpf self-test, and it passes."
1745364,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1745374,2018-01-26 17:18:22 UTC,"Ah funny, it's because we think it's a top-level entry, which we don't
modify :) I'll give it a think."
1745383,2018-10-04 09:49:06 UTC,This bug was fixed in the package hplip - 3.18.7+dfsg1-2ubuntu1
1745383,2018-10-03 14:29:50 UTC,I ahve checked through the whole source code and found 40 wrong calls of QmessageBox().
1745383,2018-10-03 14:31:13 UTC,Here is the full patch.
1745383,2018-10-02 16:22:21 UTC,"The attachment ""hplip-qmsgbox-typos.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1745383,2018-10-02 14:43:58 UTC,"Hi,
This bug is caused by typo in QMessageBox constructor call. The patch im attaching fixes this bug and some other occurences of typos like this."
1745383,2018-02-01 11:53:57 UTC,"Hi,"
1745383,2018-10-02 20:00:08 UTC,Thanks for the patch.
1745384,2018-01-25 14:54:20 UTC,"StacktraceTop:
 mem_error (format=format@entry=0x7f89900c8b4d ""assertion failed: %s"") at ../../../../glib/gslice.c:1472
 slab_allocator_free_chunk (chunk_size=chunk_size@entry=16, mem=<optimized out>) at ../../../../glib/gslice.c:1354
 private_thread_memory_cleanup (data=0x7f89440008c0) at ../../../../glib/gslice.c:785
 __nptl_deallocate_tsd () at pthread_create.c:301
 __nptl_deallocate_tsd () at ../sysdeps/unix/sysv/linux/exit-thread.h:36"
1745384,2018-01-26 08:16:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745392,2018-02-06 12:24:50 UTC,"Thank you for your bug report, you would perhaps have more chance to get the issue looked at by reporting it upstream as well on https://github.com/storaged-project/udisks/"
1745409,2018-02-16 11:57:58 UTC,"Note that you're checking the the 'ipmitool' utility is present on the undercloud node, while it has to be present in the ironic-conductor containers on the overcloud."
1745409,2018-12-29 13:47:55 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/545084
Reason: This patch has no activity for a while, per policy, we abandon it. Feel free to re-open if you think you're working on it."
1745409,2021-02-19 15:51:42 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1745412,2018-01-29 17:44:42 UTC,It does not happen in the gate so far. I set the priority to medium.
1745412,2018-01-29 17:44:11 UTC,"It might be related to the level of parallel test. Recently I did not hit this issue, but I hit a similar issue when running partial test set a couple of years ago. How many CPU cores do you have in your local env? The CI env has eight cores according to the log."
1745418,2018-01-25 16:08:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745418,2018-04-13 15:18:02 UTC,The problem is also present on Ubuntu 18.04 x64.
1745418,2020-02-04 02:50:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1745418,2020-04-04 04:17:34 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1745418,2020-04-04 04:17:35 UTC,[Expired for mesa (Ubuntu) because there has been no activity for 60 days.]
1745419,2019-09-24 13:12:02 UTC,This is in version 0.5.1-5.
1745421,2018-02-08 08:24:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745421,2018-02-08 08:28:08 UTC,Same problem on 16.04 LTS with HWE kernel.
1745421,2018-02-08 08:39:34 UTC,Some good news: new version 1.4
1745421,2018-02-20 01:59:09 UTC,"As @9d9 reports in comment #5, there is a working updated script in https://github.com/magnific0/wondershaper"
1745421,2018-08-17 17:32:49 UTC,"I'm having a little trouble reconciling where exactly to request the change, but I think the upstream package source is from github and I just logged an issue there:"
1745421,2018-01-25 21:32:08 UTC,"@9d9 I don't understand why you mark it as incomplete. How can I complete it? Maybe the solution is to remove the package but until then, the bug is there."
1745421,2018-01-25 17:03:51 UTC,"wondershaper is very old, not maintained since Mon, 11 May 2015
http://repo.or.cz/lartc.git"
1745425,2019-07-02 19:57:53 UTC,Still a problem on EG 3-2-4
1745425,2020-10-06 21:18:20 UTC,Affects workflow.
1745426,2012-07-01 16:05:24 UTC,"Currently xfce-settings hardcodes touchpad multi-tap gesture buttons, and provides no way to disable that behavior."
1745426,2015-01-31 14:12:13 UTC,*** Bug 10608 has been marked as a duplicate of this bug. ***
1745430,2018-01-25 22:35:15 UTC,I believe this issue was introduced in EG 3.0.2
1745430,2018-01-25 22:50:22 UTC,This also happens when a new subscription is created.
1745438,2018-01-25 18:51:54 UTC,Could you please add information on your OS?
1745438,2018-01-25 19:08:15 UTC,Gentoo Linux here with customized fonts.conf that makes my favourite fonts preferred everywhere (nothing crashes tho).
1745438,2018-01-25 21:53:22 UTC,Hiding ~/.config/fontconfig/fonts.conf makes it work. Attaching it.
1745441,2018-01-26 08:55:21 UTC,"If you can remind me of the process, I'm pretty sure I could patch this"
1745442,2018-02-19 15:49:59 UTC,"Reviewed:  https://review.openstack.org/545317
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_server/commit/?id=e37352356343e07f0ad2f348ce2001784d8f50de
Submitter: Zuul
Branch:    stable/queens"
1745442,2018-03-12 12:47:33 UTC,This issue was fixed in the openstack/openstack-ansible-galera_server 17.0.0.0rc2 release candidate.
1745442,2018-05-03 22:02:53 UTC,This issue was fixed in the openstack/openstack-ansible-galera_server 18.0.0.0b1 development milestone.
1745442,2018-11-10 01:46:56 UTC,"Change abandoned by Damian Cikowski (dcdamien) (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/538071"
1745442,2018-01-25 23:59:41 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/538071"
1745442,2018-02-16 14:26:35 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/545317"
1745443,2018-01-30 13:54:14 UTC,Can't you allow 'dnsmasq' user to access /var/lib/neutron/dnsmasq?
1745443,2018-01-31 12:38:43 UTC,Using `--group=neutron` instead of `--user=neutron` would be better. Group has only read access to the config files and afaik that's all dnsmasq needs here.
1745446,2018-03-23 20:04:00 UTC,I'm seeing this same behavior in 3.0.4.
1745446,2018-05-01 19:43:53 UTC,I am sharing a screenshot of the web client search with limit to available checked -- I did hit 'search' again to overcome bug 1745190.
1745446,2018-05-01 19:47:25 UTC,adding to above comment that we are in 3.0.6
1745457,2018-03-08 17:09:09 UTC,"Can confirm that issuing a full set of reads on all cores (0-47 in my case) successfully unwedged the display. The display continues to update properly some 16 hours later, though no reboot has occurred."
1745457,2018-02-06 19:41:36 UTC,I was able to temporarily work around the symptoms I saw by doing throwaway reads of the /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq files.
1745457,2018-02-06 13:58:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745457,2018-02-06 19:58:03 UTC,More info:
1745464,2018-07-24 09:32:04 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1745464,2018-03-06 15:58:02 UTC,"Jim/Christine,"
1745464,2018-03-06 15:08:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1745464,2018-01-25 21:18:10 UTC,apport information
1745464,2018-01-25 21:18:09 UTC,apport information
1745464,2018-01-25 19:35:54 UTC,"There is no output from lspci -vvnn, so not uploading lspci-vvnn.log."
1745464,2018-01-25 21:18:06 UTC,apport information
1745464,2018-01-25 21:18:04 UTC,apport information
1745464,2018-01-25 21:18:03 UTC,apport information
1745464,2018-01-25 21:18:02 UTC,apport information
1745464,2018-01-25 21:18:00 UTC,apport information
1745464,2018-01-25 20:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745464,2018-01-25 21:18:07 UTC,apport information
1745467,2020-02-29 15:11:22 UTC,"azure-cli is not available in bionic anymore.
However it will again be available in Focal. The upstream package is unfortunately of very low quality - it vendorizes the entire Python stack including the interpreter and its libraries, without any meaningful security SLA. It should not be used in production in my opinion."
1745467,2020-03-02 12:06:52 UTC,"Note also that the plugin system depends on being able to arbitrarily pull pip packages, bypassing any QA or security SLA that might be offered by your distribution. When I tried to package this in Debian I was modifying the plugin system to use apt/dpkg instead for plugins by default but this was met with hostility towards the modification from Microsoft. It's a shame but I eventually dropped the package from Debian (which I see you picked up bluca)."
1745475,2018-01-26 10:44:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745481,2018-01-28 20:12:03 UTC,"Hello,
this is due to a known problem with libpng :"
1745488,2018-02-21 21:21:15 UTC,"Successful runs on xenial (using dev autopkgtests):
- amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-snapcraft-daily/xenial/amd64/s/snapcraft/20180220_140404_01073@/log.gz
- arm64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-snapcraft-daily/xenial/arm64/s/snapcraft/20180220_211402_01073@/log.gz"
1745488,2018-02-26 21:48:36 UTC,This bug was fixed in the package snapcraft - 2.39.2+18.04.2
1745488,2018-02-26 22:26:01 UTC,"The latest snapcraft released to the stable distros was 2.35. So, in order to accept this update, the following tests need to be executed:"
1745488,2018-02-27 20:16:34 UTC,"I have been running the tests to verify this SRU. I found no blockers, so I'm marking this as verified. Please, continue with the release process."
1745488,2018-02-28 15:56:30 UTC,"We cannot successfully work on an artful release as:
1- snapcraft is mostly designed to build on a host that matches a current ""base"" (today, the only base is ""core"" which is 16.04 based).
2- artful will most likely not have a base.
3- artful experienced the glibc bump which caused built snaps on artful to be non functional when snapped (given the base mismatch).
4- bionic has experimental fixes to patch binaries and libc6 inclusion logic which has not reached the release pocket yet and is a prerequisite if we ever want this to work on artful"
1745488,2018-02-28 22:39:29 UTC,This bug was fixed in the package snapcraft - 2.39.2
1745488,2018-02-28 22:39:32 UTC,"The verification of the Stable Release Update for snapcraft has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1745488,2018-03-01 01:32:55 UTC,This new version of snapcraft appears to break all builds on s390x...
1745488,2018-03-01 01:55:09 UTC,A fix was uploaded to Xenial and will be rushed to -updates once built and published.
1745488,2018-03-01 04:19:03 UTC,And fix released to updates.
1745488,2018-02-02 00:35:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745488,2018-02-22 16:53:22 UTC,"Hello Sergio, or anyone else affected,"
1745490,2018-01-26 03:01:55 UTC,The actual UoM is l/rpm. So it is suggested that use of gal/h or l/h is not appropriate.
1745492,2018-07-20 02:49:36 UTC,I believe this is solved by bug #1743529 backporting kexec-tools from bionic.  What's the right way to close this?
1745497,2019-11-17 20:02:40 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1745505,2018-04-27 17:26:31 UTC,[3698105.633667] frontend[30228]: segfault at 0 ip 0000564fab9c2fa4 sp 00007ffe77529ed0 error 6 in perl[564fab93e000+1f7000]
1745508,2018-01-26 00:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745508,2018-01-29 19:07:25 UTC,"I built a test kernel with commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745508"
1745508,2018-02-01 17:07:16 UTC,Hi Joseph
1745508,2018-02-01 18:35:30 UTC,"Submitted Artful SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089829.html"
1745508,2018-03-19 10:57:46 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1745508,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1745509,2018-01-26 09:21:26 UTC,"Specifying collaborators (why are they called “recipients”?) is the main thing you can do on this page, so I think this button should be a primary button, Vanilla green."
1745510,2020-04-11 20:59:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745516,2020-11-16 08:05:52 UTC,Zero crashes after 18.04 so it must have been fixed somewhere.
1745516,2018-03-27 08:13:38 UTC,"And in:
https://errors.ubuntu.com/problem/329cefc225879c7c018b3492d959b2accf4a03c1"
1745516,2018-01-29 03:55:30 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/af59d8248a84adcefb2be929a34d7b9bbfe831c2"
1745516,2018-01-26 01:03:55 UTC,https://gitlab.gnome.org/GNOME/gnome-shell/issues/5
1745516,2018-01-26 00:59:39 UTC,"StacktraceTop:
 g_type_check_instance_cast (type_instance=0x556a0956f8a0, iface_type=93913860973376) at ../../../../gobject/gtype.c:4058
 st_label_get_text (label=0x556a0c13aa70) at ../src/st/st-label.c:313
 append_actor_text (desc=0x556a0b693400, actor=0x556a0c13aa70) at ../src/st/st-widget.c:2178
 st_describe_actor (actor=0x556a0c13aa70) at ../src/st/st-widget.c:2243
 ffi_call_unix64 () at ../src/x86/unix64.S:76"
1745516,2018-01-26 07:46:45 UTC,Thanks for your report. Do you have any step to reproduce this crash?
1745518,2018-01-26 10:27:23 UTC,"You're right, we install the association into ""HKCR"" [1], i.e. for the current user..."
1745526,2018-08-12 14:08:41 UTC,What version of Byobu?  What distro?
1745528,2019-10-15 11:17:10 UTC,Hello
1745528,2019-10-15 11:38:53 UTC,"In Discover we show the backend where packages come from in some places.
It would work fine either coming from the packaging or from a URL and we'll ship it."
1745528,2019-10-16 13:32:34 UTC,I'll ask someone if there's an icon we can use for this purpose. Thank you for the clarification.
1745529,2018-09-24 14:47:13 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1745529,2018-06-11 15:19:10 UTC,This issue was fixed in the openstack/nova 15.1.3 release.
1745529,2018-06-08 12:25:19 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1745529,2018-06-04 14:27:54 UTC,This issue was fixed in the openstack/nova 16.1.4 release.
1745529,2018-06-04 13:52:17 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1745529,2018-05-29 17:37:39 UTC,"Reviewed:  https://review.openstack.org/569650
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f521e03f8e1524f5abfef6497b5b1a57daba7ced
Submitter: Zuul
Branch:    stable/queens"
1745529,2018-05-31 04:34:47 UTC,"Reviewed:  https://review.openstack.org/569651
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ce740643686bcf4ed8a1e089082547cf8fcef8fc
Submitter: Zuul
Branch:    stable/pike"
1745529,2018-05-11 01:51:52 UTC,"Reviewed:  https://review.openstack.org/541660
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d5901f613cf98f61b5253a1568b22af1d9dd1a08
Submitter: Zuul
Branch:    master"
1745529,2018-05-20 17:24:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/569650"
1745529,2018-05-31 15:26:57 UTC,"Reviewed:  https://review.openstack.org/569655
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e0534442b531c3f89c9c19d95491dcddd5b0fe41
Submitter: Zuul
Branch:    stable/ocata"
1745529,2018-05-20 17:53:24 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/569655"
1745529,2018-05-20 17:45:25 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/569651"
1745531,2020-05-20 12:53:41 UTC,"Hi,"
1745531,2018-02-15 07:43:30 UTC,This bug was fixed in the package preseed - 1.62ubuntu1.2
1745531,2018-02-15 07:43:21 UTC,This bug was fixed in the package debian-installer - 20101020ubuntu318.43
1745531,2018-02-15 07:37:16 UTC,This bug was fixed in the package preseed - 1.71ubuntu1.2
1745531,2018-02-15 07:37:13 UTC,This bug was fixed in the package debian-installer - 20101020ubuntu451.19
1745531,2018-02-12 02:06:13 UTC,I have tested the following mini.iso and can confirm they work for me
1745531,2018-02-08 13:24:24 UTC,"Hello Hua, or anyone else affected,"
1745531,2018-02-08 12:08:05 UTC,"Hello Hua, or anyone else affected,"
1745531,2018-02-08 08:52:43 UTC,This bug was fixed in the package debian-installer - 20101020ubuntu523.2
1745531,2018-02-08 08:52:39 UTC,"The verification of the Stable Release Update for preseed has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1745531,2018-02-08 08:52:36 UTC,This bug was fixed in the package preseed - 1.71ubuntu5.1
1745531,2018-02-06 07:06:59 UTC,"Hello,"
1745531,2018-02-02 07:10:48 UTC,"I have tested the following mini.iso, it works for me."
1745531,2018-02-01 21:34:03 UTC,"Presumably this works in bionic but I don't see any information (its not required for the SRU process) indicating that it is fixed. However, I'd like to see Artful verified before accepting it into other releases."
1745531,2018-02-01 20:38:09 UTC,"Hello Hua, or anyone else affected,"
1745531,2018-02-01 20:31:54 UTC,"Hello Hua, or anyone else affected,"
1745531,2018-01-31 14:22:56 UTC,I have also uploaded d-i for T/X/A which will be needed after the preseed build for the mini.iso for instance. It is now waiting on the SRU verification team approval for the new packages to start building in $RELEASE-proposed.
1745531,2018-01-31 14:09:42 UTC,I have uploaded preseed for T/X/A. It is now waiting on the SRU verification team approval for the new packages to start building in $RELEASE-proposed.
1745531,2018-01-29 18:48:55 UTC,This bug was fixed in the package preseed - 1.71ubuntu7
1745531,2018-01-26 12:52:48 UTC,"""d-i"" debdiff for Trusty [lp1745531-lp1743787-di-trusty.debdiff]"
1745531,2018-01-26 11:30:45 UTC,"I'll take care of the ""d-i"" bit to force a rebuild of the mini.iso once Joshua's preseed patch is uploaded in affected releases."
1745531,2018-02-07 14:18:24 UTC,"Hello Hua, or anyone else affected,"
1745531,2018-02-07 14:17:37 UTC,"Hello Hua, or anyone else affected,"
1745534,2020-03-13 05:00:10 UTC,This change was made by a bot.
1745535,2020-01-06 07:51:13 UTC,"Change abandoned by Jeffrey Zhang (<email address hidden>) on branch: master
Review: https://review.opendev.org/538160"
1745538,2019-11-22 20:35:04 UTC,i think i might have clicked the wrong link
1745538,2019-04-19 02:29:52 UTC,GitHub equivalent for organizations and teams would be appreciated as well
1745540,2018-01-26 06:07:19 UTC,I think this is NOT a dnscrypt-proxy problem but getHostByName implementation issue. Since it MUST send DNS-over-TCP request after truncated UDP reply:
1745541,2018-05-11 19:24:48 UTC,"Note,
Another option would be to use the 'AuthorizedKeysCommand' in newer ssh versions.
see a partially-done solution based on that in 'lp-authorized-keys' at
 https://gist.github.com/smoser/8ac8a9cf081a76d9ae16b52f6afd04da"
1745541,2018-01-26 04:42:07 UTC,"Better yet, a daemon could be created to automatically do this once an LP user changes the keys on their account."
1745542,2018-01-26 04:37:38 UTC,"(This is Raspbian Stretch, last 'apt update' @ Fri Jan 26 04:37:10 UTC 2018)"
1745546,2018-01-30 02:45:57 UTC,"I solved it.
I changed dhcp_driver from neutron.agent.linux.dhcp.Dnsmasq to vmware_nsx.plugins.dvs.dhcp.Dnsmasq.
And I changed from ovs_integration_bridge to dvs_integration_bridge.
Neutron-openvswitch-agent is not used."
1745555,2018-01-31 05:49:55 UTC,"Thanks for the report. I've assigned it to the OSSN project, which seems like the group owning the security guidelines."
1745555,2018-01-31 10:01:19 UTC,Thank you Tristan for reassigning it. I only opened it in OSSA because the file is in that repository.
1745555,2018-01-31 10:25:10 UTC,"Create a patch set
https://review.openstack.org/#/c/539483/"
1745555,2018-01-31 11:19:26 UTC,"Just realised Tristan created one (suggestion 3).
I have no strong feelings either way, Tristan's is probably easier to get the wording/intent correct.
https://review.openstack.org/#/c/539420/"
1745555,2018-09-09 04:22:36 UTC,"Change abandoned by Tristan Cacqueray (<email address hidden>) on branch: master
Review: https://review.openstack.org/539420
Reason: Fixed by another change"
1745557,2018-10-11 01:50:42 UTC,I too am having live migration issues with a Kolla 6 Queens deployment. Has a fix progressed any further?
1745557,2018-01-26 09:39:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538201"
1745557,2018-04-14 00:33:29 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.openstack.org/538201"
1745559,2018-02-21 11:45:51 UTC,"Reviewed:  https://review.openstack.org/538166
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=a98295f19de87c38ef3accdb7a282c3e8d92dbbc
Submitter: Zuul
Branch:    master"
1745559,2018-03-01 16:51:33 UTC,This issue was fixed in the openstack/kolla-ansible 6.0.0.0rc1 release candidate.
1745559,2018-01-26 07:23:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538166"
1745560,2018-01-26 08:00:06 UTC,This change was made by a bot.
1745568,2020-08-10 01:46:26 UTC,gmic (2.1.9)
1745573,2018-10-14 15:15:11 UTC,Here is discussion of the 4.4.0-53 resolution https://forums.linuxmint.com/viewtopic.php?t=249705
1745573,2019-01-23 12:57:15 UTC,but I will say that after installing  monodoc gnome-keyring-manuel my machine shutdown correctly.
1745573,2019-01-23 12:56:39 UTC,It would be nice if we could get some history on what prompted a self-described newbie to installed monodoc gnome-keyring-manuel. Did god appear bofore hime and offer him golden plates with the library name engraved on them? Did he have to  receive divine guidane from aa guru on the mountain? Pedigree and history are important when announcing  solution so we have context on  it.
1745573,2019-01-23 04:08:04 UTC,problem was not present in 4.10.28 but re-appeared in 4.10.38
1745573,2019-01-23 04:05:11 UTC,This issue has popped up in linux for over ten years an in dozens of kernal versions. It get fixed and then get broken again and agin and again.
1745573,2018-11-12 22:02:53 UTC,"I had this since updating to 18.3,(newbie)I went to software manager & installed monodoc gnome-keyring-manuel-after 2 restarts-problem solved!"
1745573,2018-10-14 15:13:32 UTC,https://bugs.launchpad.net/bugs/608162 is an much earlier reference to the same issue
1745573,2018-10-14 15:11:54 UTC,I have tracked this issue popping up like a mushroom for years. I can track an incidence all the way back to 2014. It seems to have been resolved in Kernel 4.4.0-53 but re appeared again in subsequent kernels. Also Skype for linux. removing the keyring daemon package removes skype for linux due to dependencies. THis issue needs to have a deep dive to clearly understand the issue and get a final fix I have had issues on all 18.x versions.
1745573,2018-06-24 13:51:13 UTC,I reviewed some of trouble-shooting suggestions in this and other forums but nothing I read/tried provided a resolution.
1745573,2018-04-04 01:40:53 UTC,"I've installed Mint 18.3 updates on 3 different Computers. This issue didn't exist with Mint 18.3 release. It came with some update during the last months. This is clear for me now, but no chance to find the bug source…"
1745573,2018-03-25 20:11:56 UTC,"ADDITIONAL ADVICE
Trying out the Session Manager applet on my PC first, I realised I never saw the ""gnome-keyring-daemon not responding"" error. In fact even after the normal Menu > Shut Down action displayed the error, cancelling then using the Session Manager applet always gave a clean, quick, shut down."
1745573,2018-03-25 19:59:51 UTC,"This problem is the same in Linux Mint. I've made a new installation of 18.3 and installed ALL the available updates until today 2018-03-25. Running the system with 1TB HDD (BTRFS format), 8GB RAM and 2.4Ghz. The only solutions until now are for me:"
1745573,2018-02-19 17:55:35 UTC,Same issue here.
1745573,2018-02-04 18:30:21 UTC,Systemlog when this event happens (It takes about 3 minutes before the system shuts down)
1745573,2018-02-04 15:58:09 UTC,Linux-Mint Cinnamon 18.3
1745573,2018-07-05 02:59:10 UTC,"Jake I tried you suggestion to remove ""gnome-keyring 3.18.3-Oubuntu2"" from the Synaptic Package Manager."" and it did not work. I am new to linux and I am running LM cinn 18.3 cinn ver 3.6.7 under linux kernel 4.15.0-24-generic. this is the last update as of 4july18.
If you need more info email me here <email address hidden>. Thx much."
1745573,2018-03-24 14:36:51 UTC,"Try to shutdown anyway, Not shutdown properly, freezing forever."
1745592,2019-08-14 10:40:25 UTC,"Grafana does not correctly display `ram-allocation-ratio` on the dashboard because it uses values from prometheus-openstack-export which are set statically
https://git.launchpad.net/~prometheus-charmers/prometheus-openstack-exporter-charm/+git/charm-prometheus-openstack-exporter/tree/config.yaml"
1745601,2018-02-02 09:43:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745604,2019-10-11 14:49:11 UTC,"Issue still exists in hplip 3.19.8 (Fedora 30, hplip-3.19.8-2.fc30.x86_64)."
1745607,2018-05-28 12:20:28 UTC,"@Daniel, a couple of comments on your patch:"
1745607,2018-01-26 13:28:40 UTC,Please add version information and a screenshot.
1745607,2018-01-26 13:38:44 UTC,"Application: kicad
Version: no-vcs-found-bf44d39~61~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.13.0-26-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009"
1745607,2018-05-27 22:17:55 UTC,"I have changed the order of the file name and the application title for Kicad, PCBNew, EESchema, Gerbview and the footprint editor"
1745607,2018-05-29 10:11:53 UTC,"Hello Jeff, thank you for the Review! I'll fix it and submit a new patch."
1745607,2019-04-09 16:44:43 UTC,"@Daniel, the source tree is now open for 6.0.  Could you rebase your two patches so I can apply them?  Thanks, Jeff."
1745607,2019-04-09 18:36:47 UTC,"I tried to rebase the .patch files but apparently the HEAD changed so much, git is unable to apply them. Looks like i have to redo the changes"
1745607,2019-07-03 14:45:43 UTC,"Hi Daniel, any update about this patch for V6.0?
Thanks a lot for your work!"
1745607,2019-11-24 23:37:07 UTC,"The probably correct way to handle this 'simple' (it is never simple) problem is erasing all the stuff and just have a single utility function that returns the correct string, always good."
1745607,2018-05-30 00:01:09 UTC,"Fixed review findings: Usage of non-ascii characters, used string constructor, code formatting"
1745608,2018-01-26 13:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745608,2018-01-26 13:09:09 UTC,"It's a kernel panic rendering the system unusable, so I can't run any diagnostic commands."
1745608,2018-01-29 16:08:18 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1745608,2018-01-29 17:51:07 UTC,"Got something similar:
[ 2570.763287] PANIC: double fault, error_code: 0x0
[ 2570.764564] Kernel panic - not syncing: Machine halted.
[ 2570.765428] CPU: 0 PID: 22272 Comm: as Not tainted 4.15.0-041500-generic #201801282230
[ 2570.767059] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-20171110_100015-anatol 04/01/2014
[ 2570.768815] Call Trace:
[ 2570.769263]  <#DF>
[ 2570.769643]  dump_stack+0x63/0x8b
[ 2570.770251]  panic+0xe4/0x234
[ 2570.770787]  df_debug+0x2d/0x30
[ 2570.771342]  do_double_fault+0xa1/0x130
[ 2570.772031]  double_fault+0x22/0x30
[ 2570.772583] RIP: 0010:clear_page_erms+0x7/0x10
[ 2570.773303] RSP: 0018:ffffb98e428d78a0 EFLAGS: 00010246
[ 2570.774242] RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000001000
[ 2570.775515] RDX: ffff90327df4c500 RSI: ffffdb5084a10fc0 RDI: ffff90332843f000
[ 2570.776837] RBP: ffffb98e428d79b8 R08: 0000000000000000 R09: ffffdb5084a11000
[ 2570.778144] R10: 0000000000000000 R11: ffffb98e428d7cc0 R12: ffff90333ffd2d00
[ 2570.779437] R13: ffffb98e428d79c8 R14: 00000000014280ca R15: ffffdb5084a10fc0
[ 2570.780712]  </#DF>
[ 2570.781098]  ? get_page_from_freelist+0xf0d/0x1400
[ 2570.781958]  ? try_to_wake_up+0x59/0x480
[ 2570.782709]  __alloc_pages_nodemask+0xfb/0x280
[ 2570.783652]  alloc_pages_vma+0x88/0x1f0
[ 2570.784354]  __handle_mm_fault+0x938/0x11e0
[ 2570.785128]  handle_mm_fault+0xb1/0x200
[ 2570.785814]  __do_page_fault+0x257/0x4d0
[ 2570.786528]  do_page_fault+0x2e/0xd0
[ 2570.787171]  do_async_page_fault+0x51/0x80
[ 2570.787902]  async_page_fault+0x2c/0x60
[ 2570.788589] RIP: 0010:copy_user_enhanced_fast_string+0xe/0x20
[ 2570.789624] RSP: 0018:ffffb98e428d7cd8 EFLAGS: 00050206
[ 2570.790584] RAX: 00007f5c60aff010 RBX: 0000000004a26f00 RCX: 0000000000000010
[ 2570.791858] RDX: 0000000000001000 RSI: ffff9033289bcff0 RDI: 00007f5c60aff000
[ 2570.793076] RBP: ffffb98e428d7ce0 R08: ffffb98e428d7e50 R09: ffffdb5084a26f00
[ 2570.794161] R10: 0000000000000040 R11: ffffb98e428d7cc0 R12: 0000000000001000
[ 2570.795252] R13: ffffb98e428d7e88 R14: ffff9033289bc000 R15: 0000000000001000
[ 2570.796339]  ? copyout+0x26/0x30
[ 2570.796867]  copy_page_to_iter+0x10c/0x2f0
[ 2570.797521]  generic_file_read_iter+0x44b/0xbe0
[ 2570.798239]  ? page_cache_tree_insert+0xe0/0xe0
[ 2570.798969]  nfs_file_read+0x6e/0xc0 [nfs]
[ 2570.799667]  __vfs_read+0xee/0x160
[ 2570.800262]  vfs_read+0x8e/0x130
[ 2570.800817]  SyS_read+0x55/0xc0
[ 2570.801358]  entry_SYSCALL_64_fastpath+0x24/0x87
[ 2570.802156] RIP: 0033:0x7f5c614b4260
[ 2570.802768] RSP: 002b:00007ffc41b1b638 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
[ 2570.804043] RAX: ffffffffffffffda RBX: 00007f5c61781b20 RCX: 00007f5c614b4260
[ 2570.805242] RDX: 0000000000100000 RSI: 00007f5c60ada010 RDI: 0000000000000003
[ 2570.806445] RBP: 0000000000100010 R08: 00000000016bf380 R09: 0000000000000054
[ 2570.807645] R10: 00007f5c61db8700 R11: 0000000000000246 R12: 0000000000101000
[ 2570.808845] R13: 00007f5c61781b78 R14: 0000000000001000 R15: 0000000000000040
[ 2570.810251] Kernel Offset: 0x2d400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 2570.812045] ---[ end Kernel panic - not syncing: Machine..."
1745608,2018-01-29 17:56:53 UTC,Trying linux-image-4.4.0-98-generic next which should be the last known-good kernel according to the cached packages in /var/cache/apt/archives - assuming that it's only related to a kernel upgrade...
1745608,2018-01-29 18:47:25 UTC,"That's weird:
[ 2691.471972] PANIC: double fault, error_code: 0x0
[ 2691.477488] Kernel panic - not syncing: Machine halted.
[ 2691.478724] CPU: 1 PID: 31425 Comm: cc1 Not tainted 4.4.0-98-generic #121-Ubuntu
[ 2691.479962] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-20171110_100015-anatol 04/01/2014
[ 2691.481621]  0000000000000086 dbc9cc8a876ccdc2 ffff88013fc84e80 ffffffff813fb2c3
[ 2691.483041]  ffffffff81cb9bfd ffff88013fc84f18 ffff88013fc84f08 ffffffff8118df77
[ 2691.484325]  0000000000000008 ffff88013fc84f18 ffff88013fc84eb0 dbc9cc8a876ccdc2
[ 2691.485654] Call Trace:
[ 2691.486077]  <#DF>  [<ffffffff813fb2c3>] dump_stack+0x63/0x90
[ 2691.487057]  [<ffffffff8118df77>] panic+0xd3/0x215
[ 2691.487880]  [<ffffffff81060d5d>] df_debug+0x2d/0x30
[ 2691.488677]  [<ffffffff8102fb8c>] do_double_fault+0x7c/0xf0
[ 2691.489620]  [<ffffffff81846238>] double_fault+0x28/0x30
[ 2691.490537]  [<ffffffff81407d07>] ? clear_page_c_e+0x7/0x10
[ 2691.491487]  <<EOE>>  [<ffffffff811987f4>] ? get_page_from_freelist+0x454/0xa50
[ 2691.492736]  [<ffffffff8119f491>] ? pagevec_lookup_tag+0x21/0x30
[ 2691.493743]  [<ffffffff8119b8e3>] ? write_cache_pages+0x123/0x510
[ 2691.494756]  [<ffffffff81199b79>] __alloc_pages_nodemask+0x159/0x2a0
[ 2691.495826]  [<ffffffff811e4fad>] alloc_pages_vma+0xad/0x250
[ 2691.496775]  [<ffffffff811bf54f>] wp_page_copy.isra.56+0x38f/0x550
[ 2691.497802]  [<ffffffff81199b79>] ? __alloc_pages_nodemask+0x159/0x2a0
[ 2691.498890]  [<ffffffff811c0ea8>] do_wp_page+0xd8/0x6c0
[ 2691.499881]  [<ffffffff810b5403>] ? update_curr+0xe3/0x160
[ 2691.501148]  [<ffffffff811c2734>] handle_mm_fault+0xcf4/0x1820
[ 2691.502373]  [<ffffffff810bab5c>] ? set_next_entity+0x9c/0xb0
[ 2691.503540]  [<ffffffff8106b577>] __do_page_fault+0x197/0x400
[ 2691.504769]  [<ffffffff8106b847>] trace_do_page_fault+0x37/0xe0
[ 2691.505859]  [<ffffffff81063f29>] do_async_page_fault+0x19/0x70
[ 2691.507364]  [<ffffffff81846868>] async_page_fault+0x28/0x30
[ 2691.508921] Kernel Offset: disabled
[ 2691.518757] ---[ end Kernel panic - not syncing: Machine halted."
1745608,2018-02-18 08:28:08 UTC,Any updates on this?
1745616,2018-01-26 22:15:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745619,2020-03-28 17:55:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745619,2018-02-03 02:01:53 UTC,I had a similar problem on Fedora 26 which seems to have gone away after I killed the evolution-calendar-factory process.
1745620,2018-01-29 13:05:57 UTC,"In addition, the issue still happens when upgrading chromium to 64.0.3282.119-0ubuntu1"
1745620,2018-01-30 11:00:04 UTC,"I sequentially type ""buwei"", but 'i' is loss outside the chromium inputbox."
1745620,2018-01-30 11:25:50 UTC,"Can you check whether chrome (as downloaded from https://www.google.com/chrome/browser/desktop/index.html) is also affected?
If so, would you mind filing a bug upstream at https://crbug.com and link it here?
Thanks!"
1745620,2020-02-04 15:26:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745620,2018-01-29 17:43:22 UTC,"Would you mind grabbing a screencast of the issue? I'm not familiar with pinyin input, and I'm not sure I'm setting it up correctly, nor do I know what I should be observing… Thanks!"
1745623,2018-07-13 20:11:25 UTC,"We have a library that is very interested in this feature, and I'm planning to develop this in time for 3.2."
1745623,2018-07-13 20:29:30 UTC,"In addition to the (I think) obvious ou setting to active this, I think there ought to be a user setting to disable it. There are some folks (myself among them) who deliberately read a book more than once. I wouldn't want the system nagging me every time I checked out an item  for the second, third, or fourth time."
1745623,2018-07-13 20:33:20 UTC,"+1 to Jason's remarks about settings, both OU and patron."
1745623,2018-07-13 20:51:19 UTC,+1 to Jason's suggestions from me as well.
1745623,2018-07-13 22:52:55 UTC,+1 to this feature and to the settings
1745623,2018-07-13 22:55:39 UTC,"To clarify: This will only be for the patrons who have opted to have their circulation history saved, is that correct? (We require patrons to opt in to store circ history, and staff do not see what the patrons' circ history is even if they opt in.)"
1745623,2018-07-26 20:54:03 UTC,"Maybe we should ask patrons to opt in instead of making it possible for them to opt out.  As Terran noted, staff are currently unable to see patron circ history.  This feature will require exposing new data to staff."
1745623,2018-07-26 21:30:12 UTC,"The problem I have with options that require the patron to opt in from the catalog is that we have many people that never use the catalog and never will.  And even if they do use the catalog, and check their account, they will never find the option to opt in unless staff are right there next to them, showing them where to click or clicking for them."
1745623,2018-07-27 13:37:10 UTC,+1 to opt in instead of opt out.
1745626,2020-08-20 07:33:27 UTC,"Folco, please have a read at https://review.opendev.org/#/c/704478/ -- i believe it may have prematurely closed. If you can dig a little bit we could avoid a new surprise."
1745626,2020-08-18 14:36:43 UTC,"Could not reproduce this on centos8, but for some reason in my rhel8 job I hit this bug."
1745626,2018-02-02 17:57:56 UTC,"> if there's some way we can know the canonical path to dib-block-device and others without this that would be good
"
1745626,2020-04-13 12:50:36 UTC,This behaviour also breaks diskimage-builder installed via pipx
1745626,2018-01-29 05:12:17 UTC,"I'd be willing to consider any patches on this.  I don't particularly like this either but people run the binary straight out of the virtualenv and get just as confused when it all breaks with weird tracebacks because it can't find the other binaries it needs.  I remember at the time we looked around for other solutions, such as pkgutil but didn't really find anything that worked quite the same."
1745626,2020-08-18 12:42:40 UTC,Clearly this needs a patch because venv become the recommended method of creating virtualenv in python since 3.x was released many years ago. It is not a bug in venv that causes this failure.
1745627,2018-09-29 10:55:07 UTC,"We also currently conflate locked with ""footprint not from schematic"".  Good idea or bad?"
1745627,2018-09-29 14:12:50 UTC,I think bad.  Mostly because there are at least two user cases that directly conflict when a footprint doesn't exist on the schematic:
1745627,2018-11-01 15:24:25 UTC,(Copied and continued from another report)
1745627,2018-11-02 10:40:44 UTC,"I read the report thread linked to above. It seems ""locking"" isn't an easy word. To clarify a bit, there are at least three things which can be considered here:"
1745627,2018-12-10 15:06:58 UTC,Bumping priority given how often this issue comes up.
1745627,2019-04-30 07:44:51 UTC,"A have been made aware that my request [1] for a specialized flag only handling ""this footprint has no symbol on purpose and should not be removed on update"" could be related. I am however not certain if these two requests should be combined as i fear it might derail or at least balloon either request."
1745627,2019-04-30 14:23:47 UTC,I like keeping things as simple as possible (but not simpler).
1745627,2020-03-29 17:48:15 UTC,Footprint locking is primarily used for mechanical parts/constraineds (Location) by us.
1745636,2018-01-26 20:38:49 UTC,"Hello, thanks for the feedback, I'm using a mainline:
4.15.0-041500rc9-lowlatency, but I just installed it because i thought that
could resolve the wifi card problem. The wifi bug exists either on the
ubuntu kernel and the 4.15.0-041500rc9-lowlatency."
1745636,2018-01-29 16:02:55 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1745636,2018-02-16 15:06:15 UTC,apport information
1745636,2018-02-16 15:06:18 UTC,apport information
1745636,2018-02-16 15:08:32 UTC,"Hi, I have just executed the apport command, I'm now on a clean installed ubuntu 17.10 without the latest  upstream kernel."
1745636,2018-02-16 15:45:54 UTC,Does the airplane mode hotkey work for you?
1745636,2018-02-16 16:27:33 UTC,The key doesn't have any effect on linux... on Windows (dual boot) I can switch normally.
1745636,2018-02-20 14:33:20 UTC,Only if I change the volume level or other keys.. when I press the wifi key nothing shows up.
1745636,2018-02-16 15:06:13 UTC,apport information
1745636,2018-02-21 08:26:55 UTC,"(In reply to Wolgan Ens from comment #0)

> language. The wifi switch button on the keyboard is always with the red
> light and I can't change it by pressing.
"
1745636,2018-02-21 12:05:57 UTC,"(In reply to Wolgan Ens from comment #3)

> rfkill can't be enabled by rfkill and there is no bios settings related to
> the issue, on a Windows system the wifi works properly. Thank you.


@@correction-------
wifi can't be enabled***"
1745636,2018-02-22 06:38:20 UTC,"Do you see ""Received unknown event"" in dmesg after you pressed the airplane mode hotkey?"
1745636,2018-02-22 12:11:13 UTC,"No message comes from the terminal when press the hotkey (only the wifi one), the other events are detected normally."
1745636,2018-03-26 09:10:30 UTC,Wondering if this is a regression? Can you try older kernel like v4.4?
1745636,2018-06-06 15:25:04 UTC,*** Bug 199919 has been marked as a duplicate of this bug. ***
1745636,2018-01-26 16:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745636,2018-02-21 12:05:24 UTC,"rfkill can't be enabled by rfkill and there is no bios settings related to the issue, on a Windows system the wifi works properly. Thank you."
1745636,2018-02-16 15:06:12 UTC,apport information
1745636,2018-02-20 13:06:50 UTC,"Run ""sudo acpi_listen"" then press the hotkey, do you see anything?"
1745636,2018-02-16 15:06:08 UTC,apport information
1745636,2018-01-30 15:31:33 UTC,"$ uname -a
Linux wolgan-ubuntu 4.15.0-041500rc9-lowlatency #201801212130 SMP PREEMPT Mon Jan 22 02:38:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1745636,2018-01-30 15:57:59 UTC,"Hello, I have opened a bug on bugzilla.kernel.org.
Thank you very much for your supporting."
1745636,2018-02-05 12:20:01 UTC,"Hello buddy, there is something more that I need to/can/may do about the
bug?"
1745636,2018-02-05 14:56:25 UTC,"The wifi is blocked:
Hard blocked: yes"
1745636,2018-02-16 15:05:55 UTC,apport information
1745636,2018-02-16 15:05:57 UTC,apport information
1745636,2018-02-16 15:06:10 UTC,apport information
1745636,2018-02-16 15:05:59 UTC,apport information
1745636,2018-01-30 15:30:38 UTC,"Hello, I just installed the Ubuntu 17.10 and my wifi doesn't work
properly. I can't enable it through the GUI. Sorry about my poor
report, I don't have to much detail and English is not primary
language. The wifi switch button on the keyboard is always with the red light and I can't change it by pressing."
1745636,2018-02-16 15:06:01 UTC,apport information
1745636,2018-02-16 15:06:03 UTC,apport information
1745636,2018-02-16 15:06:05 UTC,apport information
1745636,2018-02-16 15:06:06 UTC,apport information
1745636,2018-02-16 15:06:07 UTC,apport information
1745636,2018-02-16 15:06:00 UTC,apport information
1745645,2020-10-05 15:24:41 UTC,"This is an ongoing issue that continues to cause consternation among our end users, especially when shelving location projects involve multiple branches and were perhaps not planned out with full consideration of consequences or completed.  Because these shelving locations do not show up in the editor any longer, it confuses staff who don't know where they showed up from or what to do with them."
1745645,2018-01-29 14:18:26 UTC,"You can delete a shelving location that has deleted holdings still attached, so we do still regularly return data on deleted shelving locations (circ stats primarily).  If the SLs are going to be fully purged, then we'll need a way to dump those holdings to another reportable location as part of the SL deletion process."
1745645,2020-10-05 15:23:51 UTC,"Would it be possible to modify definition(s) used by reporting to allow for filtering out deleted shelving locations from the ""in list"" values displayed? This way staff could select to allow deleted locations if they needed to find material that had been deleted in the past, or, only show items/locations that are not deleted."
1745648,2018-01-26 17:42:13 UTC,"If it's the case, then this would be a critical bug. However, it looks to me like LACP rate is being properly handled, values are 'slow' or 'fast', and an integration test exists to validate that."
1745648,2018-01-26 17:58:30 UTC,"Ok, this is a bug in tests/generate.py, and a missing step to sanitize the string (check for the correct values of 'slow' or 'fast') in parse.c."
1745648,2018-01-26 18:03:52 UTC,"You're right.  It looks like the unittest passes because it switched to a
string which is passed through.
But the value of 10 in the tests/generate.py for lacp-rate isn't right and
looks like parse is not validating
the string value."
1745651,2018-02-03 15:46:49 UTC,apport information
1745651,2018-02-24 08:37:50 UTC,Tags: added: kernel-fixed-upstream
1745651,2018-02-24 08:25:32 UTC,Sorry for delay in responding. I was traveling away from system with problem.
1745651,2018-02-08 17:03:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1745651,2018-02-03 17:05:26 UTC,After following the emailed instruction to run apport-collect 1745651 the thought occurred that perhaps you needed that to be run immediately after power-up & login when the problem occurs. The system had been up for several days when the log files were collected.
1745651,2018-02-03 15:46:54 UTC,apport information
1745651,2018-02-03 15:46:51 UTC,apport information
1745651,2018-02-03 15:46:50 UTC,apport information
1745651,2018-02-03 15:46:48 UTC,apport information
1745651,2018-02-03 15:46:44 UTC,apport information
1745651,2018-02-03 15:46:46 UTC,apport information
1745651,2018-02-03 00:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745651,2018-02-03 15:46:37 UTC,apport information
1745651,2018-02-03 15:46:38 UTC,apport information
1745651,2018-02-03 15:46:39 UTC,apport information
1745651,2018-02-03 15:46:47 UTC,apport information
1745651,2018-02-03 15:46:41 UTC,apport information
1745651,2018-02-03 15:46:40 UTC,apport information
1745651,2018-02-03 15:46:45 UTC,apport information
1745651,2018-02-03 15:46:43 UTC,apport information
1745651,2018-02-03 15:46:43 UTC,apport information
1745658,2020-03-25 11:08:15 UTC,This issue was fixed in the openstack/python-openstackclient 5.1.0 release.
1745658,2018-01-31 19:41:34 UTC,"Change abandoned by Hongbin Lu (<email address hidden>) on branch: master
Review: https://review.openstack.org/538331
Reason: Fixed in: https://review.openstack.org/#/c/511983/"
1745658,2018-01-26 19:48:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538331"
1745658,2018-01-30 13:07:51 UTC,"For a short term solution, I think adding a check to OSC sounds better, as a change in neutron response needs a micro-versioning from the perspective of API-SIG but it still take time (at least in Rocky)."
1745658,2018-01-30 13:05:23 UTC,"is_default is a boolean attribute, so I think ""None"" is a reasonable solution."
1745658,2018-01-27 09:26:46 UTC,"I don't think it is a valid bug. Please see
http://specs.openstack.org/openstack/neutron-specs/specs/mitaka/get-me-a-network.html"
1745658,2018-01-30 19:19:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539303"
1745661,2018-01-29 08:52:05 UTC,"Bonjour Amadou,"
1745664,2018-08-14 14:48:03 UTC,Some one else responded that installing ncsd (nis caching service) also solved the problem.
1745664,2018-08-14 14:55:36 UTC,"Apparently a note was added to the systemd NEWS notes, noting this incompatibility and asking distro maintainers to either override IPAddressDeny or install ncsd."
1745664,2018-08-14 15:02:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745664,2018-08-14 15:05:48 UTC,This appears to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1774417
1745664,2018-08-15 01:24:10 UTC,It's not that clear to me. I would prefer to keep this bug open at least. Not just because it's older but also because it's much better documented with a stack trace and link to errors.ubuntu.com.
1745664,2019-05-14 17:56:39 UTC,"Can confirm that NSCD installation eliminated lag, reference comment #22."
1745664,2018-08-13 12:06:07 UTC,Sorry I did not respond earlier.
1745664,2019-05-15 15:51:34 UTC,Importance -> Medium as there is a workaround available.
1745664,2019-11-14 20:26:09 UTC,And this also helps here? https://github.com/systemd/systemd/issues/9431#issuecomment-412195708
1745664,2019-11-14 20:47:43 UTC,In /etc/systemd/system/systemd-logind.service comment out IPAddressDeny=Any
1745664,2019-11-14 23:30:46 UTC,Installing ncsd worked well for me as well.
1745664,2018-08-15 12:59:46 UTC,Agreed. I don't know if it technically qualifies as a duplicate.  But I suspect its caused by the same systemd change.
1745664,2018-08-10 20:27:55 UTC,One user on the github issue has reported that setting IPAddressDeny= for systemd-login fixed these crashes. I did the following steps and am waiting to see if the crashes stop.
1745664,2018-08-14 14:48:27 UTC,Woops nscd
1745664,2018-06-29 01:33:31 UTC,Nothing was done. The comment:
1745664,2018-01-26 18:54:45 UTC,"StacktraceTop:
 __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26
 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=100000, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=100007, address=0x7ffc27302060) at pm_getport.c:106
 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=100007, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154
 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=100007, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136"
1745664,2018-05-16 21:13:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745664,2018-07-17 14:18:45 UTC,"Joe, Could you try the recommendation posted on the github link?  I'm going to try to find time to test on my system as well."
1745664,2018-06-14 13:33:46 UTC,A second one of our systems is having the __libc_connect crashes.
1745664,2018-06-14 13:39:53 UTC,Neither of my systems crash when logging into a nis account.
1745664,2018-06-15 01:47:09 UTC,"Tracking in:
https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3"
1745664,2018-05-21 13:30:44 UTC,I am getting this crash report pretty consistently.  A lot of my problems have been clumped under this bug https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238?comments=all as it was the first one I ran into.
1745664,2018-06-25 15:08:37 UTC,Installed ubuntu 17.10 and so far no crashes (almost a week).  Really wish someone would help determine whats going wrong in 18.04.
1745664,2018-06-26 01:53:22 UTC,The error report (comment #10) confirms this crash only occurs in Ubuntu 18.04. However it's also not that common (only 137 reports globally). It's pretty unlucky if this is blocking you :(
1745664,2018-06-26 01:59:00 UTC,"All,"
1745664,2018-06-26 13:59:11 UTC,"Daniel, Thanks for the response.  I'm struggling to track down this issue since it locks up my machine and no logs or errors appear to be created."
1745664,2018-06-26 14:23:31 UTC,Posted https://github.com/systemd/systemd/issues/9431
1745664,2018-06-28 12:17:10 UTC,Daniel - please explain what was done to resolve.
1745664,2018-06-20 13:24:27 UTC,My computer continues to crash on a daily basis.  It locks up and reboots. And this error report pops up.  I've no idea how to track this down.
1745666,2019-09-17 09:54:07 UTC,I believe this is the solution until they fix the service:
1745666,2019-07-24 18:31:49 UTC,"@snabb (Janne) #7 or @ljh48332 (Luke) just detected this again in latest release and will present a workaround that solves it even with continuous Ubuntu/Debian/Gnome updates. Could you give some insight into why this service is kept and not removed completely? Even the Gnome threads state it should be removed. Most people probably are not aware of the problem but it is a severe bug from a performance, data integrity and hardware perspective."
1745666,2019-04-01 15:21:15 UTC,"This bug came back again in latest ubuntu, this time a new symptom occurred. Gnome extensions are also regularly disabled for some reason. Removing gsd-housekeepin still works."
1745666,2019-01-20 01:21:05 UTC,"This bug came back in recent updated after using workaround #5 by Janne. Didn't notice at first, then severe system slowdowns and odd power behaviour started to occur. 100% Fan on etc. Killing my disk long term as well. I detected it when the gsd-housekeepin service crashed and Ubuntu notified this."
1745666,2018-12-06 22:59:21 UTC,"I'm not sure if this is related or if this helps troubleshoot, but my system will randomly go unresponsive and needs to be hard rebooted. May or may not be related to this bug."
1745666,2018-12-06 22:57:46 UTC,Same issue here. Ubuntu 18.04 Kernel4.15.0-42-generic Dec 06 2018
1745666,2018-11-15 09:55:09 UTC,The same is happening on 18.04.1 kernel 4.15.0-39-generic @ 15/11/2018
1745666,2018-10-24 17:25:13 UTC,Problem exist in 18.10 as well after upgrade.
1745666,2018-10-08 09:40:38 UTC,"#journalctl -b | grep gsd-housekeepin | wc -l
100067"
1745666,2018-10-10 07:33:26 UTC,"I just tried to report this bug for Bionic, it informed me the package was not installed when i used fn+alt f2 ubuntu-bug gsd-housekeepin."
1745666,2018-10-02 16:05:56 UTC,"Nope, the message persists even with fs.inotify.max_user_watches=524288"
1745666,2018-10-03 08:05:37 UTC,"In 15 hours 6000 new messages occur.
#journalctl -b | grep gsd-housekeepin | wc -l
12000"
1745666,2018-01-26 19:26:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745666,2018-03-14 20:32:27 UTC,"on Bionic gnome too, for me it says:"
1745666,2018-03-24 08:02:24 UTC,"With gsd 3.28.0-0ubuntu1 on bionic, the errors are like:"
1745666,2018-03-24 08:43:00 UTC,Temporary workaround:
1745666,2018-01-26 19:26:17 UTC,Also seen on Bionic with a gnome xorg session.
1745666,2018-04-08 17:05:57 UTC,Also affects Ubuntu 18.04 bionic (beta2 right now).
1745666,2018-06-23 21:09:43 UTC,"Same here, for Permission Denied, on Bionic. Occurs once every hour."
1745666,2018-09-29 05:30:11 UTC,I think this bug i filed might be a duplicate of this: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795111
1745666,2018-10-01 05:53:39 UTC,"I'm fairly sure this is related to changes in fs.inotify.max_user_watches (""Too many open files""). I recently got a bunch of warnings in misc code editors about low values. Took me a while to understand the max_user_watches had reverted back to the default value of about 8000. I.e., some update probably changed my setting, which was much higher before, without permission. I haven't touched that setting for years."
1745666,2018-04-06 02:42:32 UTC,The errors as of #4 are still seen
1745671,2019-07-19 20:49:32 UTC,Thanks for filing the bug.  The ifupdown eni parser in eni.py does not handle reading multiple stanzas of the same interface; however it _is_ support in eni; so this is a bug in the eni format parser.
1745671,2018-01-26 19:49:00 UTC,"The implementation doesn't seem to like this, though:"
1745671,2018-01-26 19:46:12 UTC,I'm bringing this upstream ...
1745671,2018-01-26 19:38:14 UTC,"Hi,"
1745671,2018-01-26 16:21:13 UTC,Tested with cloud-init-0.7.9-20.el7.x86_64
1745671,2018-01-26 16:04:26 UTC,"Description of problem:
Configuring metadata network-interfaces with ""iface eth2 inet6 static"" breaks all networking on cloud-init instance. This only works when configuring a sub interface."
1745671,2018-01-26 19:44:20 UTC,I'm bringing this upstream ...
1745671,2018-01-26 18:30:53 UTC,I don't believe this is intended to work. Did defining the interface twice previously work for the customer?
1745674,2018-01-26 20:11:15 UTC,"StacktraceTop:
 ?? () from /tmp/apport_sandbox_qxC8y5/usr/lib/x86_64-linux-gnu/libcups.so.2
 process_new_notifications (user_data=0x55b372629070) at gsd-print-notifications-manager.c:916
 emit_signal_instance_in_idle_cb (data=0x7fce0001b4e0) at ../../../../gio/gdbusconnection.c:3720
 g_main_dispatch (context=0x55b3726279d0) at ../../../../glib/gmain.c:3148
 g_main_context_dispatch (context=context@entry=0x55b3726279d0) at ../../../../glib/gmain.c:3813"
1745676,2018-01-26 21:10:56 UTC,Same on 18.04 LTS on GNOME FlashBack session and MATE session.
1745676,2018-01-27 10:33:36 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1745692,2018-01-26 23:07:33 UTC,I don't know if this need to go to the kernel team instead of systemd. Apport decided that systemd is the right place.
1745696,2018-01-27 00:05:53 UTC,You might disregard and close this bug.  I probably have my understanding of basicfilesystems/no_swap inverted.
1745699,2019-03-08 04:20:15 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1745704,2018-01-27 01:57:10 UTC,"StacktraceTop:
 _int_malloc (av=av@entry=0x7f1158000020, bytes=bytes@entry=257) at malloc.c:3843
 _int_realloc (av=av@entry=0x7f1158000020, oldp=oldp@entry=0x7f1158018790, oldsize=oldsize@entry=144, nb=nb@entry=272) at malloc.c:4627
 __GI___libc_realloc (oldmem=0x7f11580187a0, bytes=bytes@entry=256) at malloc.c:3246
 g_realloc (mem=<optimized out>, n_bytes=256) at ../../../../glib/gmem.c:159
 g_array_maybe_expand (array=0x7f11f8105060, len=len@entry=1) at ../../../../glib/garray.c:793"
1745708,2018-08-21 00:26:15 UTC,"I’m facing the same problem, and it seems to work in Chromium too, although the coordinates of the second textPath are incorrectly calculated in this last browser."
1745713,2018-02-02 09:30:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745713,2018-02-12 02:49:51 UTC,"see also:
 #1742573 package linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 (https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1742573)
and
 #1745113 package linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 (https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1745113)"
1745713,2018-02-27 00:50:55 UTC,Because of that problem I could not only not upgrade the kernel but couldn't install any software at all.
1745715,2019-03-28 10:54:28 UTC,Is this still an issue in recent releases? If yes - please update.
1745715,2019-05-28 04:17:44 UTC,[Expired for kolla because there has been no activity for 60 days.]
1745715,2019-12-11 20:49:32 UTC,"Hi Michael :-) This is an issue for me. After a restart to the keystone container , docker logs shows:"
1745715,2019-12-12 09:26:49 UTC,"James, I have seen that kind of error before. Normally it happens if one of the hosts fails but the rest continue. Because we use run_once for the keystone bootstrap task, it can end up executing on on a node that has previously failed and therefore does not have config.json generated. Try scrolling up in the logs and looking for 'failed' or 'fatal'."
1745725,2020-11-21 00:20:46 UTC,"Same problem still in 2020! Un-B-lievable!!!
Linux Mint 18.3 sylvia,  xfce"
1745725,2018-06-14 09:23:52 UTC,My affected xfce4-terminal version: 0.8.6
1745725,2018-10-18 12:06:44 UTC,This is caused by a bug in GTK+ and it has been fixed in at least version 3.20.8 of GTK+.
1745725,2018-03-15 17:59:47 UTC,"Additionally, it seems that after some time (about 5 minutes) the entire xfce4-terminal process is killed. So if you have other terminal windows open and functional beside the frozen one they all suddenly disappear."
1745725,2018-10-18 12:10:00 UTC,Related:
1745732,2018-01-27 18:43:40 UTC,Thanks for reporting.
1745732,2019-02-27 14:45:19 UTC,"Fixed in bionic, I don't think this is worth a backport effort..."
1745736,2018-01-31 02:04:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745737,2018-12-12 10:03:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745740,2018-10-03 12:45:07 UTC,How was this system installed? Was it installed in BIOS mode and then changed to UEFI?
1745740,2018-01-29 20:54:11 UTC,This may be a duplicate of bug 1743908
1745740,2018-01-27 14:00:07 UTC,This change was made by a bot.
1745740,2018-01-29 15:20:45 UTC,Can we get versions of grub2/grub2-signed off the box
1745743,2018-01-27 21:12:36 UTC,How and why did you install the apt-config-auto-update package?  update-notifier-common is part of all Ubuntu images by default; and apt-config-auto-update has an undeclared conflict with this package.
1745754,2018-02-02 23:47:31 UTC,This may be a duplicate of bug 1744722 but its hard to tell without any log files.
1745754,2018-02-06 02:17:56 UTC,I don't believe it has anything to do with  non standard 3rd party apt sources. I had disabled all of them other than the bone stock ubuntu sources. Also I had no issue upgrading at all after i fixed the location of the servers to the archives. This is simply a complaint that there is no upgrade path other than manually changing repositories to the archives on a now unsupported release. It is bad human ergonomics :)
1745754,2018-01-27 17:25:02 UTC,"Sorry, didn't realize it put it in the wrong place. Thank you for moving it to where it needs to be."
1745754,2018-01-27 16:43:19 UTC,"We do need to move the files off archive.ubuntu.com for space reasons on mirrors, but (1) that's not actually done by Launchpad as such, but by Ubuntu's end-of-life processes, and (b) this is the kind of thing that ought to be handled by the distribution's upgrade tools.  I've heard a few developers talking recently about the need to improve this.  Reassigning over to ubuntu-release-upgrader."
1745757,2018-01-28 16:13:29 UTC,"I'm not an expert, but I tried running the current GitHub source through a debugger."
1745757,2020-10-28 10:07:33 UTC,"I filed a separate Issue on GitHub: https://github.com/plougher/squashfs-tools/issues/50
I believe the problems were fixed in these two commits:"
1745757,2020-10-28 10:57:12 UTC,"Tested the mksquashfs command in version 4.4 (2019/08/29) on Ubuntu 20.04.
It now says: Not enough or invalid arguments in pseudo file definition ""/ f 444 root root echo"""
1745758,2018-01-27 17:00:03 UTC,This change was made by a bot.
1745758,2018-01-29 19:24:27 UTC,You may need to run the following from a terminal:
1745758,2018-01-29 20:10:43 UTC,Ok I opened a terminal and
1745758,2018-01-29 20:12:09 UTC,NOTE:  just fyi but a google search earlier before I filed the bug showed others getting this also
1745761,2020-03-09 12:27:58 UTC,"Hi,"
1745770,2018-01-27 20:20:48 UTC,"The attachment ""arpon.png"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1745772,2020-01-15 21:41:23 UTC,"Hi, I can't seem to reproduce this anymore with snapd and lxd as a snap:"
1745772,2018-06-14 06:26:04 UTC,I can confirm this. Snaps are not working out of the box in Xenial or Bionic lxd containers. Same behavior with and without squashfuse installed.
1745772,2018-06-14 06:35:00 UTC,It works as expected if the non-default security.nesting config item is set to true:
1745781,2018-01-27 22:59:29 UTC,Confirmed in master and 0.92.x branch - seems we're only redrawing as a response to mouse input events...
1745784,2018-02-02 12:47:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1745784,2018-02-03 01:26:04 UTC,The trigger loop is detected between gnome-icon-theme and bamfdeamon. So reassigning there.
1745795,2018-06-04 03:27:15 UTC,This issue was fixed in the openstack/python-openstackclient 3.14.2 release.
1745795,2018-03-21 02:00:50 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/538539
Reason: Looks like Dean fixed this in https://review.openstack.org/#/c/550105/"
1745795,2018-01-30 15:16:15 UTC,Trying to sort out next steps in the ML:
1745795,2018-01-29 15:45:30 UTC,"Reviewed:  https://review.openstack.org/538541
Committed: https://git.openstack.org/cgit/openstack-dev/grenade/commit/?id=fce6befbb50fdc774f16fa963dd51e2bb8eedd63
Submitter: Zuul
Branch:    master"
1745795,2018-01-28 01:50:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/538537"
1745795,2018-01-28 02:20:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/538541"
1745799,2018-01-28 04:26:12 UTC,"StacktraceTop:
 OsAbort () at ../../../../os/utils.c:1361
 AbortServer () at ../../../../os/log.c:877
 FatalError (f=f@entry=0x55df4a60cfa6 ""%s"") at ../../../../os/log.c:1015
 xwl_log_handler (format=<optimized out>, args=<optimized out>) at ../../../../../hw/xwayland/xwayland.c:885
 wl_log (fmt=<optimized out>) at ../src/wayland-util.c:406"
1745799,2018-03-23 13:57:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745799,2019-01-21 18:52:56 UTC,"I created bug #1795760, which describes a Xwayland-abort and got the status duplicate of 1745799."
1745799,2019-01-21 20:21:33 UTC,"The attachment ""error9_patch.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1745799,2019-01-22 01:43:44 UTC,"Gert,"
1745800,2018-01-31 05:33:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745806,2018-02-05 16:53:19 UTC,"Reviewed:  https://review.openstack.org/540870
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=bd60ada44ae1948ef668fdf145879b5b215ae2f4
Submitter: Zuul
Branch:    master"
1745806,2018-02-05 14:35:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540870"
1745806,2018-02-05 13:38:28 UTC,"in the docs[1], there's a step that says: systemctl start openstack-gnocchi-api.service. can you run systemctl status openstack-gnocchi-api.service to check status? or journalctl to read logs?"
1745806,2018-02-02 23:07:04 UTC,"I have experienced this also. I followed the Pike guide for ceilometer and I get
Unable to establish connection to http://controller:8041/v1/resource_type/ceph
when i try to run ceilometer-upgrade --skip-metering-database
I do not use ceph in my openstack and i do not see anything in the ceilometer.conf that mentions ceph so it is not clear where this comes from."
1745806,2018-01-29 04:16:57 UTC,what does gnocchi-api logs say? you should probably paste your gnocchi.conf and ceilometer.conf files if you aren't able to find the error in gnocchi-api
1745806,2018-02-05 13:40:20 UTC,"if you're wondering why it references ceph, it's becasuse ceilometer will create resource types (schemas) for all the possible resources it can theoretically monitor whether you enable them in ceilometer or not."
1745810,2018-02-02 12:47:25 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1745810,2018-02-05 18:59:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745814,2018-01-30 09:30:24 UTC,Re: #5
1745814,2018-01-29 19:45:00 UTC,Apport also aborts with an error:
1745814,2018-02-12 10:14:02 UTC,"It seems this bug is fixed in the mainline kernel, since I installed Kernel 4.15, the problem did not reappear again."
1745814,2018-01-29 17:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745814,2018-01-28 10:54:02 UTC,Regarding the package: The problem is that I have no idea what causes the crash because there is no error message. That is why I filed the report for Ubuntu in general. I hope that is ok.
1745814,2018-01-28 08:24:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1745814,2018-01-29 19:44:34 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1745823,2020-02-18 10:09:16 UTC,Addressed by https://review.opendev.org/#/c/708327/
1745829,2018-01-28 13:12:39 UTC,Other alternatives:
1745829,2020-03-12 12:19:14 UTC,"build radiotray-ng for my 20.04 development install. works as it should. had to convert my old bookmarks.xml to the new json setup.
would recommend to change to radiotray-ng, too."
1745829,2018-01-28 13:15:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745832,2018-01-28 13:12:39 UTC,Other JPEG pictures (from Panasonic GX80 and Olympus PEN E-PL7 for example) are OK.
1745832,2018-01-28 13:14:04 UTC,eog opens the picture from the Google Pixel 2 without problem.
1745832,2018-01-28 13:22:22 UTC,I have attached 3 sample picture files from the Google Pixel 2 now.
1745832,2018-01-28 13:29:55 UTC,"StacktraceTop:
 _dbus_abort () at ../../../dbus/dbus-sysdeps.c:93
 _dbus_warn_check_failed (format=format@entry=0x7fdb2a9cb7c8 ""arguments to %s() were incorrect, assertion \""%s\"" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n"") at ../../../dbus/dbus-internals.c:281
 _dbus_warn_return_if_fail (function=function@entry=0x7fdb2a9ca1b0 <__func__.5319> ""dbus_message_iter_append_basic"", assertion=assertion@entry=0x7fdb2a9c94b8 ""_dbus_check_is_valid_utf8 (*string_p)"", file=file@entry=0x7fdb2a9c9a1d ""../../../dbus/dbus-message.c"", line=line@entry=2754) at ../../../dbus/dbus-internals.c:936
 dbus_message_iter_append_basic (iter=iter@entry=0x7fff372b8270, type=type@entry=115, value=value@entry=0x7fff372b8260) at ../../../dbus/dbus-message.c:2754
 append_cache_item (obj=0x55a8fb839430, data=0x7fff372b8400) at ../atk-adaptor/adaptors/cache-adaptor.c:203"
1745834,2018-01-29 15:02:03 UTC,"Ok, it turns out that it's a bit more complicated than just having sudo in AUTH_TYPES. That will work to get a plugin installed but then hp-doctor also requires some further adjustment."
1745834,2018-01-29 19:51:59 UTC,"Please ignore ""...left without any means to install a plugin..."""
1745834,2018-02-02 08:38:57 UTC,"Hi,"
1745834,2018-02-02 19:14:08 UTC,Thank you for the reply Shivani. It is always good to have engagement with the team at HPLIP.
1745835,2018-03-01 08:27:30 UTC,"should be merged with:
#1724151"
1745835,2018-03-01 08:27:45 UTC,I mean https://bugs.launchpad.net/hplip/+bug/1724151
1745835,2018-08-31 16:44:02 UTC,Yes there is a typo bug here
1745845,2018-03-19 17:38:24 UTC,Gluster's built-in NFS server is deprecated. The preferred method is to use NFS-Ganesha instead: https://docs.gluster.org/en/latest/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/
1745845,2020-01-06 17:50:42 UTC,I can confirm this is still present in Ubuntu 19.10 MATE
1745845,2020-01-06 17:50:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745856,2019-07-16 16:57:10 UTC,I think mega://user.name%<email address hidden>/Folder should be mega://user.name%40gmail.com:@mega.nz/Folder - colon after .com and before @mega.
1745862,2019-06-05 07:00:19 UTC,I have the same problem.I don't know how to fix it.
1745866,2018-12-13 03:21:16 UTC,See also bug 1707611.
1745866,2018-04-14 15:22:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745866,2018-02-01 01:18:58 UTC,Interesting. That suggests the kernel is negotiating the audio at the same time as the display signal. It also suggests that the same negotiation does not occur if the TV is already connected when turned on.
1745866,2018-01-30 18:04:51 UTC,apport information
1745866,2018-01-31 17:29:58 UTC,I have Sound when I switch to tty1 (STRG+ALT+F1) and back to tty7.
1745866,2018-01-30 18:04:56 UTC,apport information
1745866,2018-01-30 18:04:55 UTC,apport information
1745866,2018-01-30 18:04:54 UTC,apport information
1745866,2018-01-30 18:04:52 UTC,apport information
1745866,2019-06-05 19:29:51 UTC,"Hi
i'm currently having a similar issue. Maybe its related.
It want audio output is switched to hdmi if the cable is plugged in.
module-switch-on-connect is loaded (its shown if i use pactl list) but nothing happens.
I also use nvidia proprietary driver. I noticed that NO udev event is generated if the cable is plugged in. I checked with udevadm monitor."
1745866,2018-01-30 18:04:49 UTC,apport information
1745866,2018-01-30 18:04:39 UTC,apport information
1745866,2018-01-30 18:04:46 UTC,apport information
1745866,2018-01-30 18:04:45 UTC,apport information
1745866,2018-01-30 18:04:44 UTC,apport information
1745866,2018-01-30 18:04:42 UTC,apport information
1745866,2018-01-30 18:04:41 UTC,apport information
1745866,2018-01-30 18:04:40 UTC,apport information
1745866,2018-01-30 02:39:53 UTC,Yes the command should eventually print an https:// URL which you can copy into a web browser on a different machine.
1745866,2018-01-29 18:34:03 UTC,I found a workaround:
1745866,2018-01-29 04:22:34 UTC,Maybe bug 1707611?
1745866,2018-01-29 04:20:16 UTC,"Hi,"
1745866,2018-01-30 18:04:48 UTC,apport information
1745866,2018-01-29 17:23:36 UTC,"It is a server installation. I have only ssh connection to the system.
I tried to run ""apport-collect 1745866"" but I can't log in with the terminal browser.
Is there a way to make this via ssh?"
1745867,2018-01-29 13:35:04 UTC,"I use a behringer NOX101 to fade between two laptops if I use some (everything else is made from mixxx).
I do not know whether it is a norm, it scales from -20 to 10 but the steps are different. (-20,-10,-7,-4,-2,0,2,4,7,10 - Unit unknown)
I do not request something very exactly - it is not nessecary for me to implement this exactly in Mixxx, the discussion in the bug linked in #2 is for that problem."
1745867,2018-01-28 21:42:21 UTC,"Yes, it should be switch able. The best between Norm resets, since it should be a reliable meter and not a toy ;-)"
1745867,2018-01-28 19:51:25 UTC,"Or is this Bug a duplicate of:
""Make VU Meter norm conform""
https://bugs.launchpad.net/mixxx/+bug/1429760
I would love to have this peace of code replaced with a reliable instrument."
1745867,2018-01-28 19:42:36 UTC,"You can change the
<PeakHoldTime>
and
<PeakFallTime>
keys for the volume meters in your favorite skin to a lower value."
1745867,2018-01-28 21:06:44 UTC,Would it be possible to make this setting switchable somewhere else? I believe I am not the only person who is interested in changing the behaviour of the vu meters.
1745869,2018-01-29 16:40:58 UTC,From Mainlog.txt:
1745879,2018-12-07 11:01:22 UTC,"Hi,"
1745880,2019-12-11 04:54:43 UTC,I still can't make it work.  But I must be doing it wrong.
1745880,2018-01-29 04:46:44 UTC,Seems to work fine here.
1745883,2018-01-28 22:43:32 UTC,"BTW, this has long been fixed upstream in Mnemosyne, which is now at version 2.6."
1745895,2020-11-23 09:08:29 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1745895,2021-01-23 04:18:32 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1745897,2018-02-24 03:05:23 UTC,Is there a list of commits we should confirm for 18.04?
1745897,2018-07-26 15:45:26 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1745897,2018-08-07 10:34:15 UTC,the commit is not ready in upstream. not public. Thanks for your understanding.
1745897,2019-06-17 08:58:30 UTC,"commit 119906afa5ca610adb87c55ab0d8e53c9104bfc3
Author: Zhang Yi <email address hidden>
Date: Mon Apr 22 08:48:48 2019 +0800"
1745898,2018-02-24 03:05:20 UTC,Is there a list of commits we should confirm for 18.04?
1745898,2018-05-01 09:33:12 UTC,14c73f997a5e 243f29fe449b 459d0ddb079c 78727137fdf4 8d0d8ed3356a bc6ba8085842 bca811a7fd5a
1745898,2018-05-01 09:33:56 UTC,"243f29fe449b libnvdimm: add an api to cast a 'struct nd_region' to its 'struct device'
8d0d8ed3356a nfit: fix region registration vs block-data-window ranges
78727137fdf4 nfit, address-range-scrub: fix scrub in-progress reporting
14c73f997a5e nfit, address-range-scrub: introduce nfit_spa->ars_state
459d0ddb079c nfit, address-range-scrub: determine one platform max_ars value
bc6ba8085842 nfit, address-range-scrub: rework and simplify ARS state machine
bca811a7fd5a nfit, address-range-scrub: add module option to skip initial ars"
1745898,2018-07-26 15:44:58 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1745898,2018-08-09 00:57:13 UTC,"yes, we can"
1745904,2018-01-29 07:31:46 UTC,From dpkg.log
1745905,2020-12-01 08:51:47 UTC,"For the record, a good explanation on where this topic is at this time in cinder: http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019122.html"
1745905,2019-03-06 18:21:59 UTC,"Since keystone does everything for services to consume this today, we might be able to fix this with documentation that describes how services convert project IDs from URL to consuming scope from tokens."
1745905,2018-04-09 14:03:39 UTC,"This is certainly going to be a discussion we'll need to have with other projects that rely on endpoint formats like this. Ideally, it would be good to generalize the policy enforcement code for that service to work with the new system scope format. After that, it might be possible for operators to remove the project IDs from their endpoint definitions. Eventually, projects should be able to remove code that parses the URL for a project ID."
1745907,2018-01-29 07:29:03 UTC,Thanks for your report. It seems you're running Wayland. Does it work under Xorg (select the session Ubuntu on XOrg on the login screen)?
1745907,2018-01-29 07:40:04 UTC,"@jibel: I can not try that, as XOrg does not work on my system. Is XOrg a requirement to use LibreOffice or Gedit?"
1745907,2018-01-29 07:47:32 UTC,No it is not a requirement but there are some issues with Wayland and copy paste between application could be one of them.
1745907,2018-01-29 18:06:30 UTC,"> LibreOffice -> Firefox: Not text pasted
"
1745907,2018-02-07 08:31:39 UTC,Both source and target remains to be open at the same time in order to make clipboard work. Wayland unfortunately does not store the clipboard after source application closes.
1745907,2018-02-07 09:18:33 UTC,I forgot to mention in the bug description that I did not close any of these applications during the test.
1745907,2018-04-09 04:17:24 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1745907,2018-11-16 08:44:48 UTC,I can confirm this bug - I am running Wayland. Sometimes random applications does not store copied content into the clipboard. Their restart can solve it.
1745907,2018-12-14 07:46:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745908,2019-02-12 09:37:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745912,2021-01-04 11:51:30 UTC,"A patch was applied in Debian to fix this build failure with GCC-10:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957008"
1745912,2021-01-04 17:25:22 UTC,"OK - 2.0.1+repack-1.1 is in proposed and builds on everything but the s390x architecture, even though it built fine in Debian on that architecture."
1745913,2018-01-29 08:49:13 UTC,"Although fixing this is trivial, it does require to add a module to the requirements. OSX is not a supported platform, thus I think there shouldn't be a need to adapt it --specially when it's trivial to run the tests on a docker or VM under OSX"
1745914,2018-07-05 04:04:52 UTC,Also needs check that the setting for skins to be applied exists (though it would be hard automating that it looks right.)
1745914,2018-08-31 01:24:18 UTC,The bug has been fixed by
1745920,2019-02-08 02:09:19 UTC,would trying to query the metadata url work?
1745920,2018-12-04 16:04:16 UTC,Just for reference for anyone reading along. I've had some email exchange with Ed and we are making progress on this.  We'll probably end up with some sort of filesystem path that contains information indicatingi the system is running on packet.
1745920,2018-11-30 15:56:57 UTC,Our internal ticket on this issue says in part:
1745920,2019-02-08 02:13:36 UTC,the metadata url for packet is https://metadata.packet.net/metadata
1745920,2018-07-09 15:22:28 UTC,"@Simos,
As for current status here, there is nothing that cloud-init can do to ""detect""
that it is running on packet.net.   At least not that I can see.  As a work
around, you can run:
 dpkg-reconfigure cloud-init
then remove ec2 from the list, and :
  rm -Rf /var/lib/cloud/instance/warnings"
1745920,2018-07-09 11:34:40 UTC,Any updates on this one?
1745920,2018-02-28 02:48:42 UTC,"Adam,
Sorry for the slow reply."
1745920,2018-02-05 22:00:43 UTC,"Hey Scott,"
1745920,2018-02-05 21:45:12 UTC,"Hi,
Thanks for taking the time to file a bug."
1745920,2018-11-30 14:52:41 UTC,I am listening @smoser - drop me a note at <email address hidden> and I can help get this sorted out.
1745924,2018-01-29 06:28:24 UTC,"By the way, I was invoking Heat API by using openstacksdk.
Because Heat is not handling version negotiation when api path ""/api/v1"" is invoked, the ""orchestration"" service cannot be successfully registered to openstacksdk. From client side, the effect is ""heat is not installed or down""."
1745941,2018-01-31 03:04:16 UTC,"Upon further investigation (thank you, axwalk), in ""utils/cert"" package, NewLeaf is requiring key to be an rsa.PrivateKey but it doesn't seem to do anything RSA-specific. So, when/if we do decide to change it, it may not be too hard :)"
1745959,2018-02-01 07:23:46 UTC,"Our MaaS server is still affected by bug 1739761
Please feel free to set this task to Invalid."
1745959,2018-02-06 09:58:06 UTC,"3.2.0-133.179 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html"
1745959,2018-02-19 18:03:06 UTC,The package has been published and the bug is being set to Fix Released
1745963,2018-02-02 12:44:29 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1745964,2020-08-09 23:42:04 UTC,pdfsam-basic 3.3.3-1
1745965,2018-01-30 13:15:02 UTC,"Nevermind. Doing some research I found out that, ONLY IN MY CASE (not for normal Ubuntu image), the system-root is mounted on /overlay. This was done to preserve the root modification, so during the boot that /overlay is copied into the /. The problem is that in order to update the kernel and run dpkg, this tries to install everythin in / while the real system-root is in /overlay. I have tried to do a chroot overlay and execute the dpkg from there but it also fails. I will be able to try with the new kernel as I figure out how to fix this situation."
1745965,2018-02-01 08:07:33 UTC,"So, finally, I got installed some drivers which were failing and the Kernel stopped complaining."
1745965,2018-01-30 11:29:12 UTC,"So after installing the new kernel and selecting it in the GRUB menu, the system boots in initramfs shell.  I installed the 32 bits generic version... May this be another bug? Because this should generate the initrd and the other needed parts executing the dpkg -i *.deb, shouldn't it? Best regards"
1745965,2018-01-29 12:13:01 UTC,"I have executed apport-collect 1745965 but a desktop graphic interface I ccould not get any result. If there is another way of getting a file or something, please, tell me and I will provide any needed log.
Best regards.
Iván."
1745965,2018-01-30 08:23:19 UTC,"Hello Joseph,
First of all, I want to thank you for your fast response.
I am using a base image that is used by my company, so no update was performed.
I will try with the latest v4.15 kernel[0] and see what happens."
1745965,2018-01-30 10:36:50 UTC,"Well. After trying to install the kernel v4.15 kernel[0], the system boots in initramfs . Seems as if there was not any initrd, so I get stuck in this point by the moment."
1745965,2018-01-29 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1745965,2018-01-29 20:28:13 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1745970,2019-06-20 17:59:34 UTC,This is available via the generate-root-ca-cert action now.
1745970,2018-04-24 10:15:07 UTC,I'd rather see this done via easyrsa (in out mini-bootstrap CA deployment part).
1745977,2018-12-05 10:56:48 UTC,"Reviewed:  https://review.openstack.org/575190
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=604819b29c0bd43969747d32f6e3d818b3cbece7
Submitter: Zuul
Branch:    master"
1745977,2018-05-02 12:01:55 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1745977,2018-04-20 13:14:35 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1745977,2018-04-02 13:18:52 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1745977,2018-02-25 15:29:44 UTC,"Reviewed:  https://review.openstack.org/545989
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e0c1d461af0701adb94e6974f363e12395ed0162
Submitter: Zuul
Branch:    stable/ocata"
1745977,2018-03-08 17:19:43 UTC,"Reviewed:  https://review.openstack.org/545988
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1407079d4008c6304799dd83f5bf4ba505d8e438
Submitter: Zuul
Branch:    stable/pike"
1745977,2018-02-19 22:54:51 UTC,"Reviewed:  https://review.openstack.org/543970
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ba8a35825a7ec839b2d0aab7559351d573130ab
Submitter: Zuul
Branch:    master"
1745977,2018-02-19 21:38:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/545989"
1745977,2018-02-19 21:37:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/545988"
1745977,2018-02-19 21:36:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/545987"
1745977,2018-02-19 21:18:53 UTC,"It looks like this was a regression caused by this change, which was backported to stable/ocata:"
1745977,2018-02-13 15:33:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543970"
1745977,2018-02-22 08:18:37 UTC,"Reviewed:  https://review.openstack.org/545987
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=619754f5c836ed1b58c807138836e6cf5a4e6904
Submitter: Zuul
Branch:    stable/queens"
1745977,2018-02-22 18:28:06 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc3 release candidate.
1745982,2018-02-09 16:27:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1745984,2018-01-29 21:55:13 UTC,The error in your log is:
1745984,2019-12-18 18:02:50 UTC,Unattended-upgrades is expected to detect changed conffiles which did not happen here for some reason.
1745984,2020-02-17 04:17:32 UTC,[Expired for unattended-upgrades (Ubuntu) because there has been no activity for 60 days.]
1745986,2020-11-01 17:51:43 UTC,This bug was fixed in the package sanlock - 3.8.2-1
1745988,2018-02-08 10:44:23 UTC,"Change abandoned by Jiri Stransky (<email address hidden>) on branch: master
Review: https://review.openstack.org/539261
Reason: We should do https://review.openstack.org/#/c/540798/"
1745988,2019-06-10 08:15:54 UTC,"We no longer have the `overcloud update stack` command, closing."
1745988,2018-01-30 17:06:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539261"
1745988,2018-02-08 10:44:18 UTC,"Change abandoned by Jiri Stransky (<email address hidden>) on branch: master
Review: https://review.openstack.org/539267
Reason: We should do https://review.openstack.org/#/c/540798/"
1745989,2018-01-29 13:54:54 UTC,"linux-firmware/artful-updates,artful-updates,now 1.169.2 all [installed,automatic]
  Firmware for Linux kernel drivers"
1745989,2018-01-29 14:00:07 UTC,This change was made by a bot.
1745989,2018-01-29 20:27:46 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1745989,2018-01-29 21:35:07 UTC,"Sorry, I guess that would be useful information."
1745989,2018-01-29 21:51:18 UTC,apport information
1745989,2018-01-29 21:51:19 UTC,apport information
1745989,2018-01-29 21:52:01 UTC,This is not fixed in the mainline kernel.
1745990,2019-01-09 16:12:58 UTC,The issue has been reported upstream as well on https://bugzilla.gnome.org/show_bug.cgi?id=778548
1745990,2019-01-08 12:16:14 UTC,same in Ubuntu 18.04.1 LTS
1745999,2020-12-17 19:12:36 UTC,"Same for me!
I installed okular from snap in UBUNTU 20.04.1
Okular cannot open files stored in /tmp – for example downloded from Firefox
I removed okular from snap folder and reinstalled it with synaptic.
Now it works like ever!
So I guess that the snap-version of okular is buggy?!"
1745999,2020-07-04 06:40:08 UTC,I removed snap-version and replaced by distribution-version (20.04) and anything works well!
1745999,2020-07-04 06:25:43 UTC,Exactly the same bug with me after installing Ubuntu 20.04 recently. Okular installed  by snap.
1745999,2020-01-17 10:14:30 UTC,This bug also affects me. I know older versions did not have this bug (non snap). Not sure what's happening.
1745999,2019-05-15 10:23:30 UTC,I also have this bug.
1745999,2019-05-15 10:29:23 UTC,"By the way, Okular will neither open a pdf if I navigate to it from my home folder by way of symbolic link to another drive."
1745999,2020-12-17 19:36:20 UTC,"The okular snap is not maintained by anyone in Ubuntu, so commenting in this bug is just shouting into the void, as no-one here can fix it. Please use the upstream KDE bug to comment."
1745999,2019-05-13 14:22:26 UTC,Numpty user scratches around in the dirt looking for some incy little nut that pinged off when he tried to attach some widget.
1745999,2018-12-09 11:25:56 UTC,"As the one year anniversary is approaching and this bug still exists, I want to redirect potential visitors of this page to this askubuntu answer where I found valuable information: https://askubuntu.com/a/20161/548635"
1745999,2019-04-22 06:40:49 UTC,"#!/bin/sh https://goo.gl/MzS6NE
TMP=/home/or/media/folder nohup thunderbird &"
1745999,2019-05-13 13:33:31 UTC,What has Thunderbird got to do with it?
1745999,2018-01-28 23:59:10 UTC,"I installed okular on Ubuntu 17.10 via snap (“sudo snap install okular”). The okular snap seems to use “strict” confinement and is thus unable to access files outside the user’s home directory even for reading. However, for a “viewer”-type application like okular, this is very problematic:"
1745999,2018-01-29 00:15:47 UTC,Where did you download that snap package from?
1745999,2018-01-29 00:18:15 UTC,"(In reply to Albert Astals Cid from comment #1)

> Where did you download that snap package from?
"
1745999,2018-01-29 14:04:08 UTC,"Yes, but the devil's in the details. Snaps and Flatpaks are indeed supposed to be universal packages, but who packages them? Since this is a packaging but, that piece of information ins important. If we the developers package them, then we're responsible for the packaging. But if Ubuntu (or someone else) packages them, then they're responsible for the packaging."
1745999,2018-01-29 12:30:21 UTC,"I’m sorry, but I was under the impression that the point of snaps was to have “universal” packages, which work on any distribution and are not customized for any particular one. “snap info okular” gives me the following output:"
1745999,2019-04-15 22:07:29 UTC,"This bug report seems to correctly diagnose the issue, which is of course a major problem for a file ""viewer""-type application."
1745999,2018-01-29 04:14:10 UTC,Sounds like an issue with how the Snap is packaged. I'd recommend reporting this to Ubuntu.
1745999,2018-06-28 04:30:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746017,2018-02-12 08:47:33 UTC,This bug was fixed in the package linux-oem - 4.13.0-1020.21
1746017,2018-02-12 09:32:39 UTC,The package has been published and the bug is being set to Fix Released
1746017,2018-02-09 11:49:53 UTC,"Cert testing is on hold until we're back on normal SRU cycles, so I'll just mark this task invalid this time."
1746019,2018-01-29 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746019,2018-01-30 16:31:38 UTC,"== Artful stock kernel ==
Fails to upgrade CAP file."
1746019,2018-01-30 17:10:57 UTC,== Artful with patched kernel - upgrade FW ==
1746019,2018-01-30 17:43:39 UTC,Bionic has this kernel patch under the 4.14 tags.
1746019,2018-03-19 10:56:50 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1746019,2018-03-27 17:29:57 UTC,-- Stock 17.10 kernel --
1746019,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1746028,2018-01-29 17:47:52 UTC,"Are you sure that what you're seeing is not simply some hinting functionality applied by your PDF viewer? From what I can tell the geometric shapes are identical, so any difference in appearance is a characteristic of the renderer."
1746028,2018-01-29 17:50:55 UTC,"P.S. The example images in the question seem to suggest something else is going wrong there, as the geometric shape seems to change significantly (text becomes a lot larger in the second screen-shot)."
1746028,2018-01-30 02:22:01 UTC,"Hi Eduard,"
1746032,2018-02-27 12:21:51 UTC,"Reviewed:  https://review.openstack.org/539008
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2efe3f6b8844bd328bbe12eeac3fae10be159542
Submitter: Zuul
Branch:    stable/ocata"
1746032,2018-02-20 20:26:14 UTC,"Reviewed:  https://review.openstack.org/539003
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=834adeae9a3ff1bb87f22066131d48230ef96b69
Submitter: Zuul
Branch:    stable/pike"
1746032,2018-05-02 12:03:54 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1746032,2018-01-30 19:27:30 UTC,"Reviewed:  https://review.openstack.org/538961
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4a2c9a4887a219a6d4dfe83c430b040713fc4109
Submitter: Zuul
Branch:    master"
1746032,2018-01-29 16:54:02 UTC,This will also be an issue in newton but we're waiting to end of life newton so we won't fix this upstream there.
1746032,2018-02-09 07:13:33 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1746032,2018-04-02 13:19:04 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1746032,2018-01-29 19:36:51 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/539008"
1746032,2018-01-29 19:18:39 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/539003"
1746033,2018-01-29 16:36:54 UTC,"Possible solutions here are the
a) assert that cleaning should be done
b) make IPA abort if it senses duplicate partition UUID's
c) make IPA clear duplicate partition UUID's during install"
1746033,2018-02-05 15:55:52 UTC,"> assert that cleaning should be done
"
1746039,2018-08-25 16:37:16 UTC,https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Utopic/Deja-Dup
1746039,2018-11-05 14:31:50 UTC,Ok. I've added deja-dup to my Xubuntu 18.04 installs and I can confirm that it integrates well and works. Seems to me like it would be a safe addition to the Xubuntu desktop recommends.
1746039,2019-03-28 17:32:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746039,2019-11-14 21:09:17 UTC,"As a rule of thumb, Long Term Support releases are not normally times for making significant changes to the seed.  Based upon a quick look at the task sets in aptitude we see that Ubuntu, Ubuntu Kylin, and Ubuntu MATE carry deja-dup in their seeds while none of the other flavors do.  To consider adding this to the Xubuntu seed we need to consider it against the Xubuntu Strategy Document's criteria.  See: https://docs.xubuntu.org/contributors/xsd.html"
1746041,2018-05-21 22:59:39 UTC,"Hello, any feedback? At least, is there someone who agrees (or not) with the above-mentioned small issues regarding the Inkscape built-in 'nudge RGB' filter?"
1746043,2019-03-05 21:48:29 UTC,"Actually disregard that, it seems that this is a XUL issue and the other one is webclient."
1746043,2019-03-05 21:46:50 UTC,This might be related to / a duplicate of bug 1774268
1746043,2018-01-29 17:21:08 UTC,The only time we've seen this happen is when the patron unchecks notification boxes at the time of hold placement.
1746043,2018-05-21 14:58:14 UTC,"We have had a rash of this happening also since our upgrade to 3.0.  Prior to our upgrade this happened from time to time however, since our upgrade there have been too many to assume it's just patron's unchecking them by mistake."
1746043,2018-01-29 17:45:11 UTC,I agree this is usually true but we have had quite a rash of this happening since December. Too much to be a coincidence? No one else has mentioned it so no one else is seeing the same behavior?
1746050,2018-02-23 00:07:18 UTC,"Hi Ritam,
We have indicated the upgrade steps, Please close this bug."
1746054,2018-01-30 11:57:42 UTC,According to this table of markers - http://lad.dsc.ufcg.edu.br/multimidia/jpegmarker.pdf - markers FF02..FFBF are reserved. So why they are important for this util enough to reject file?
1746054,2020-10-20 13:00:57 UTC,Preemptive clarification: this wasn't an issue of either of grey or I trying to steal bug migration points from each other. (see https://alpha.inkscape.org/bug-migration/ where we track points)
1746054,2020-10-20 06:14:39 UTC,Closing because INVALID: Fix Released.
1746054,2020-10-19 22:22:05 UTC,"This was fixed in 0.92.5, and the issue was tracked in Gitlab (our new bugtracker, which we're slowly migrating issues to) with https://gitlab.com/inkscape/inkscape/-/issues/632"
1746054,2018-09-20 18:03:07 UTC,"Affects me too. I tried to re-save the test image with default osx viewer app -- without making changes to the size, and it helped. So, assuming it happens pretty rarely, it's just some bad jpg files, and re-saving should help. But in a long-term, it would be nice to have a fix."
1746054,2018-09-09 14:45:48 UTC,"Affects me too on Manjaro, it is not an ubuntu-specific problem with Inkscape 0.92"
1746054,2018-01-30 09:38:09 UTC,Error reporting code checked into master.
1746054,2018-01-29 22:05:44 UTC,"I don't use Ubuntu, just have to use it sometimes, as my web-service works on it and uses inkscape to produce PDFs. So I can't find a solution myself, I don't understand anything relative :)"
1746054,2018-01-30 09:29:34 UTC,The relevant code is in src/display/cairo-utils.cpp: Pixbuf::create_from_file()
1746054,2018-01-29 18:17:19 UTC,"Can you link those images by dragging/dropping them onto the canvas? Or does this fail, too?"
1746054,2018-01-29 21:33:47 UTC,"Well, that's helpful... :-/
I had suspected GdkPixbuf and had hoped to get some more helpful error message."
1746054,2018-01-29 20:36:20 UTC,Could you check the console if there is any helpful debug output?
1746054,2018-01-29 18:58:01 UTC,No. Drag-and-drop failed too
1746054,2018-01-29 20:53:19 UTC,"If you mean terminal, it has one line after image fail - ""GdkPixbuf loader failed"""
1746061,2019-06-08 04:24:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746063,2018-01-30 08:06:45 UTC,low frequency in releases newer than 16.04
1746065,2018-01-30 07:45:20 UTC,It only affects xenial.
1746073,2018-01-30 09:18:54 UTC,"I've checked the juju code. We would need to run something similar to 'openstack boot'. The juju code uses a nova client from gopkg.in [1]. The only function, I saw available looks to be the one that juju code uses[2]. This function is 'RunServer'[3]. It accepts different sort of options [4], and none of them seem to be helpful here,they are more related to 'openstack server create' command. I've read the nova client API from GoPkg and couldn't find what we need."
1746073,2018-01-31 03:47:31 UTC,"The goose client used by Juju doesn't expose the config necessary to enable block device mapping.
From what I can see here https://developer.openstack.org/api-ref/compute/, there's several possible configuration options when using the start instance API:"
1746073,2018-01-31 14:23:22 UTC,"On Wed, Jan 31, 2018 at 03:47:31AM -0000, Ian Booth wrote:

> The goose client used by Juju doesn't expose the config necessary to enable block device mapping.
> >From what I can see here https://developer.openstack.org/api-ref/compute/, there's several possible configuration options when using the start instance API:
>
> ""block_device_mapping_v2"": [{
>     ""boot_index"": ""0"",
>     ""uuid"": ""ac408821-c95a-448f-9292-73986c790911"",
>     ""source_type"": ""volume"",
>     ""volume_size"": ""25"",
>     ""destination_type"": ""volume"",
>     ""delete_on_termination"": false,
>     ""tag"": ""disk1"",
>     ""disk_bus"": ""scsi""}]
>
> It wouldn't be practical to specify all of these using constraint
> syntax.
"
1746073,2018-01-31 16:39:52 UTC,"Juju doesn't support launching instances backed by EBS volumes either, yet."
1746073,2019-06-02 18:17:55 UTC,upvote for this from me - although our use case is slightly different; we need volume backed disks so that we can do backups from Cinder and also dynamic volume resize.  So our block would look like this:
1746073,2019-06-04 03:52:54 UTC,"We discussed using the ""root-disk-source"" constraint that was added for vSphere as the openstack way to specify ""volume"" backed disks."
1746073,2019-06-14 22:02:14 UTC,"@thumper,"
1746073,2019-06-17 01:16:38 UTC,"Yes, that should already work. If it doesn't please let us know."
1746073,2019-06-17 01:38:47 UTC,https://github.com/juju/juju/pull/10296
1746073,2019-06-19 18:50:26 UTC,"Tim,"
1746073,2018-02-01 13:41:58 UTC,I just found this:
1746079,2018-01-29 20:01:11 UTC,"StacktraceTop:
 ?? ()
 gtk_css_static_style_compute_value (style=0x5572929ce350, provider=0x55728fa51760, parent_style=0x0, id=0, specified=0x55728faf1b20, section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237
 _gtk_css_lookup_resolve (lookup=lookup@entry=0x557292effe00, provider=provider@entry=0x55728fa51760, style=style@entry=0x5572929ce350, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122
 gtk_css_static_style_new_compute (provider=0x55728fa51760, matcher=matcher@entry=0x7fff8c3c5d20, parent=parent@entry=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195
 gtk_css_node_create_style (cssnode=0x557292d939a0) at ../../../../gtk/gtkcssnode.c:371"
1746081,2018-02-07 08:16:38 UTC,This bug was fixed in the package chrony - 3.2-2ubuntu2
1746081,2018-01-31 07:03:23 UTC,"there is /etc/defaults/chrony in later versions of it.
But even that is no more working since the native systemd service does not consider it."
1746081,2018-01-31 16:13:32 UTC,Thanks for checking this out!  I'll look at your fix and incorporate similar.
1746081,2018-01-31 09:27:21 UTC,Tested proposed fix on test ppa https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3115/+packages working fine picking up DAEMON_OPTS from /etc/default/chrony now.
1746083,2018-01-29 19:57:05 UTC,"If I clipboard the document, close Lyx entirely, open it (but without opening the failure document), and paste my clipboard into a fresh document, I can export.  Here is the log of a successful export."
1746083,2018-01-29 19:52:54 UTC,This is the progress log from my failed export.
1746089,2020-10-09 21:35:45 UTC,"Scott, marking this as a duplicate of bug 1602843 and I have a fix in flight."
1746090,2018-01-29 20:47:59 UTC,It's a wiki - feel free to change the link yourself.
1746090,2020-10-02 09:20:53 UTC,I updated links in the wiki.
1746098,2018-01-30 20:09:54 UTC,I started looking at this and found that right now an SMS carrier is required to place a hold due to a DB consistency check.  If sms_phone is not null then sms_carrier must be not null.
1746098,2018-01-31 13:57:25 UTC,"Hmm, how do we handle changing pickup locations between a location that needs sms_carrier and one that doesn't.  Or rather between a location that doesn't require sms_carrier and one that does.  I guess the trigger could re-enter the default sms_carrier setting if switching, otherwize just remove sms_notify for that hold.  Switching pickup lib does happen, but usually by accident and not very often in my experience."
1746103,2018-03-04 15:20:59 UTC,"When I export this, I also see an error around the periphery where the escaping traces are. They appear to be broken."
1746103,2018-03-04 15:12:29 UTC,A possibly related bug? bug # 1753260
1746103,2018-03-04 15:43:52 UTC,"Hi Chad,"
1746105,2018-04-23 14:47:53 UTC,"[Master], num_samplers cannot be decreased, only increased. If you load a skin with 64 samplers or there are 64 samplers in your samplers.xml file, num_samplers will be set to 64."
1746105,2018-04-23 19:06:58 UTC,then we might introduce another variable which shows the actually supported/visible samplers in a skin?
1746105,2018-04-23 21:16:29 UTC,I don't think that's a good idea for the long term. Skins supporting different number of samplers is an ugly short term hack around the dramatic increase in startup and shutdown times when the number of samplers in the skin is increased.
1746105,2018-06-02 15:33:14 UTC,"If I load Deere (16 samplers) and read '[Master],num_samplers' in Developer Tools it still says ""64"".
What's the point of [Master],num_samplers in skin manifest then?"
1746105,2018-06-02 15:48:03 UTC,That is probably because you have 64 samplers saved in ~/.mixxx/samplers.xml
1746105,2020-11-02 20:01:08 UTC,"No, skin.xml says ""[Master],num_samplers"">16
the sampler.xml has 16 samplers loaded, I even removed the empty node 17-64.
Sample applies when I load a similiar custom sampler banks."
1746105,2018-04-22 19:36:38 UTC,"I tried to fix this, adding
""<attribute config_key=""[Master],num_samplers"">4</attribute>""
to skin.xml does not help.."
1746108,2018-03-16 13:33:21 UTC,Same problem on my T60. So I'm not alone with this. Phew! :D
1746112,2020-04-09 20:34:30 UTC,This is probably coming from GTK. Not sure if there will be a workaround but it's something to look into
1746112,2020-12-29 20:07:22 UTC,This is fixed in the GTK3 branch of Pinta.
1746117,2018-01-29 22:48:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539037"
1746117,2018-01-30 14:24:10 UTC,"Change abandoned by Pierre Blanc (<email address hidden>) on branch: master
Review: https://review.openstack.org/539037
Reason: You perfectly right, we have this package in trusty. I did this change for xenial"
1746117,2018-01-30 14:26:09 UTC,"Finally we have this package for trusty.
You can close this bug."
1746121,2018-03-27 20:48:44 UTC,"Good point, Eva.  Could you share a link to some good Czech-language documentation of the various MARC fields?"
1746121,2018-03-27 19:34:09 UTC,"I would appreciate ""MARC Field Help"" too. Just one note: the linking to field documentation should be configurable (e.g. in the Czech Republic we use MARC documentation in Czech)."
1746121,2018-03-27 20:33:51 UTC,"Getting translated tool tips depends on various national libraries or cataloging centers having translations available on the web. Currently, we can get English from the Library of Congress and French from Library and Archives Canada (LAC-BAC)."
1746121,2018-03-27 20:04:09 UTC,Adding a link to related wishlist bug 1746025 -- Add tooltips to MARC Editor.  Would be nice to see tooltips restored in the web client as well as adding link-outs to more extensive info.
1746125,2020-04-04 12:29:26 UTC,"I am having this issue , not sure what to do , the solution solved in the first moment to change the container networking , in the first deployment is solved, but int he second total new deployment not working. any glue?"
1746125,2020-04-06 01:43:50 UTC,"Are you sating that you add a new model and the container-networking-method is not ""local"" as wanted?
There's a juju model-defaults command which allows you to set up default config for any newly created model. You can bootstrap with these default values, or you can set them after bootstrap, eg"
1746125,2020-04-06 14:54:08 UTC,"When I used local in the first deployment it was working yes,,
it the second ... no and third ,no, I am not sure what to do ,"
1746125,2020-04-06 15:48:13 UTC,in a secondary deployment isolated:
1746125,2020-04-07 01:09:43 UTC,"Looking a bit further, using fan on AWS is necessary for container networking, so ""local"" is not something that's guaranteed to work."
1746128,2019-12-19 06:01:41 UTC,libdbusmenu-qt (0.9.3+16.04.20160218-1ubuntu1) bionic; urgency=medium
1746128,2019-12-19 05:29:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746133,2018-02-28 13:27:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746134,2018-09-17 09:17:11 UTC,New code has been released as cs:ntp-29 (candidate channel).  I'll update once I have some performance comparisons to report.
1746134,2019-03-11 05:10:36 UTC,"I've completed several performance tests and have come to the conclusion that auto_peers' use of the peer relation is a fundamental performance bottleneck.  To that end, I'm going to submit an MP to deprecate that feature until a better-performing implementation can be created."
1746134,2019-03-15 07:00:25 UTC,"I've pushed https://code.launchpad.net/~paulgear/ntp-charm/+git/ntp-charm/+merge/364236 to mark auto_peers as deprecated, built cs:~nt​p-team/ntp-23 (candidate channel) and started a CI run, but CI seems a bit borked, so I'm leaving this as fix committed for now."
1746134,2018-03-26 02:01:50 UTC,"I'm trying to optimise this along with the changes for chrony support in
bionic.  I've optimised out a relation-set from the relation-changed
hook, but I'm not hopeful of further performance improvements without
some abuse of update-status as a config-changed caching mechanism.  Once
I have the new code in place I'll do some performance comparisons and
note the results here."
1746135,2018-01-30 13:46:47 UTC,Maybe you have seen the Tweak Tool? Not as customizable as Autodesk's soft tool but same idea I think.
1746135,2018-01-30 16:12:43 UTC,"If a Gaussian curve is enough, it's also worth mentioning Alt + Drag on selected nodes."
1746135,2018-01-30 22:14:31 UTC,"The thing with the tweak tool is the curves and shape can be radically altered to the point where there is two path rather than one after manipulating one path. Furthermore, it doesn't preserve the same amount of vertexs. So, there seem to be a need for soft selection tool for certain tasks."
1746135,2020-09-11 04:05:55 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1746142,2018-02-06 16:19:52 UTC,"Please also see the bug triage conversation of Feb 6th, 2018."
1746142,2018-01-30 09:29:18 UTC,"I am fine with introducing consistency.
To avoid issues, I think it would be best to have it as an optional future default if the user doesn't exist yet."
1746146,2007-07-11 12:36:50 UTC,"Created attachment 91616
Original JPG Image"
1746146,2019-06-30 10:47:20 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=455883
1746146,2019-06-30 10:41:14 UTC,Upstream bug is a duplicate of 455883 so changing
1746146,2018-05-31 12:53:04 UTC,*** Bug 793049 has been marked as a duplicate of this bug. ***
1746146,2018-01-31 07:45:13 UTC,Thanks for forwarding to GNOME
1746146,2018-01-31 04:54:34 UTC,Filed upstream as: https://bugzilla.gnome.org/show_bug.cgi?id=793049
1746146,2018-01-31 04:05:49 UTC,"If you look at the right edge of the image, opposite to the ""C"", the rest of the ""C"" as it fades out can be seen - but the dark area is to the left, not the right."
1746146,2018-01-30 10:17:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1746146,2018-01-30 02:50:26 UTC,"If you look at the right edge of the image, opposite to the ""C"", the rest of the ""C"" as it fades out can be seen - but the dark area is to the left, not the right."
1746146,2017-11-19 19:25:43 UTC,Issue still existing with eog 3.26.1.
1746146,2010-10-17 13:01:56 UTC,"One more thing that came up in the downstream discussion: Most users don't care about a physical rotation of the image, just changing the orientation flag in the EXIF data and thereby changing how the image is displayed would be enough. This ""rotation"" is obviously always lossless and does not depend on the image size. The only problem here is that some applications (e.g. the gnome desktop background) ignore this flag..."
1746146,2010-10-16 17:29:21 UTC,"Marcel, such a dialog might indeed be a solution. Not sure yet, if we should act proactively (width%8 != 0 -> not lossless) or whether we should still try to save and check if libjpeg complains (it can be configured to do so since v7) until showing the dialog. We likely need to change how saving works to implement either variant though."
1746146,2010-10-16 12:37:17 UTC,"Created attachment 172489
original and padded (200% zoomed)"
1746146,2010-10-10 21:11:43 UTC,"From the JPEG FAQ:

> In particular it is possible to do 90-degree rotations and
> flips losslessly, if the image dimensions are a multiple of the file's
> block size (typically 16x16, 16x8, or 8x8 pixels for color JPEGs).
"
1746146,2009-03-29 10:43:36 UTC,*** Bug 577142 has been marked as a duplicate of this bug. ***
1746146,2007-08-19 19:11:52 UTC,"Hmm, I don't think this is a problem with libjpeg but with lossless jpeg transformations in general. It could be what Alan Horkan talks about in bug 338138 comment 9 (first paragraph). Rotating the image would apparently require trimming the image to a multiple of 16.
The question is: Can we detect this and warn the user (and possibly let him decide what to do)?"
1746146,2007-08-11 04:40:38 UTC,"I can reproduce it as well. These pixels are not really wrong, but they correspond to the opposite row (or column). If this is inside libjpeg we should report it against it."
1746146,2007-07-11 15:36:24 UTC,"Indeed.
This appears to be related to the lossless JPG transformations as it is reproducible with jpegtran."
1746146,2007-07-11 12:42:36 UTC,Bug noticed on Ubuntu Feisty 7.04 / EOG 2.18.1 and also replicated on Ubuntu Dapper 6.06 / EOG 2.14.3.
1746146,2007-07-11 12:37:43 UTC,"Created attachment 91617
Image showing error at the last line"
1746146,2010-10-16 21:18:10 UTC,*** Bug 603304 has been marked as a duplicate of this bug. ***
1746146,2007-07-11 12:35:15 UTC,"Please describe the problem:
Rotate a jpg photo left and save it. The last line of the new picture will display incorrect pixels."
1746157,2020-01-06 01:34:56 UTC,"I realise that now that - to quote my first post - 'set[ting] the dock to appear when the pointer was held against a screen edge' is precisely what the 'pressure reveal' option is meant to do. However, on my system (and, now, plank 0.11.4.34), that option does not work. Worse: it if does not work, then one loses the ability to see one's plank and, thus, to disable the faulty 'pressure reveal'. Worse yet, there is no config file. So how to ever see my dock again? I discovered `plank --settings`. Others won't."
1746157,2020-04-14 00:08:40 UTC,I really wish this problem would be fixed.
1746164,2018-01-30 06:09:30 UTC,Thanks for the suggestion. It sounds like this may fix bug 405294 for some users.
1746164,2018-02-02 04:38:41 UTC,"> On Feb 2, 2018, at 10:05 AM, Daniel van Vugt <email address hidden> wrote:
>
> It sounds like maybe @peterpall isn't doing what @kaihengfeng asked:
>
>  btcoex_enable=0 bt_ant_diversity=1
>
> But at the same time it also sounds like @kaihengfeng is trying to solve
> the wrong problem, judging by comment #20. Actually it sounds like the
> fix @peterpall needs is just:
"
1746164,2018-02-02 04:56:57 UTC,"""to let WiFi use two antennas when BT is off"" is indeed nice to have too, yes."
1746164,2018-01-30 05:56:01 UTC,The patch that resolves the problem.
1746164,2018-02-02 05:33:28 UTC,"> On Feb 2, 2018, at 1:14 PM, PeterPall <email address hidden> wrote:
>
> I had tried all combinations:
>
> - btcoex_enable=0 and bt_ant_diversity=1 does help a little bit with bluetooth. But not much
"
1746164,2018-02-02 05:34:02 UTC,"> On Feb 2, 2018, at 12:56 PM, Daniel van Vugt <email address hidden> wrote:
>
> ""to let WiFi use two antennas when BT is off"" is indeed nice to have
> too, yes.
>
> However this bug is titled ""Enable Bluetooth-Wifi coexistence by
> default"". So it sounds like we need both:
>
>  btcoex_enable=1 bt_ant_diversity=1
>
> The problem we aim to solve here is fixing Bluetooth performance, not
> fixing wifi performance.
"
1746164,2018-02-02 05:41:37 UTC,"It should be ""This will be a regression for people who only use WiFi but not Bluetooth""."
1746164,2018-02-02 05:59:38 UTC,"> Do you see ""Set BT/WLAN RX diversity capability” in dmesg? Your wireless
> chip doesn’t support bt_ant_diversity if you don’t see this message.
Seems like my wireless chip doesn't support it: My dmesg starts with probing the CPU on starting the kernel but doesn't contain this message.
"
1746164,2018-02-02 06:07:21 UTC,"> On Feb 2, 2018, at 1:59 PM, PeterPall <email address hidden> wrote:
>
>> Do you see ""Set BT/WLAN RX diversity capability” in dmesg? Your wireless
>> chip doesn’t support bt_ant_diversity if you don’t see this message.
> Seems like my wireless chip doesn't support it: My dmesg starts with probing the CPU on starting the kernel but doesn't contain this message.
>
> => I would be happy with btcoex_enable=1 without using bt_ant_diversity=1.
> Hope that this method isn't a regression for wifi-only users. While bluetooth is in use it enhances wifi performance a lot for me.
"
1746164,2018-02-02 06:33:05 UTC,Cool! Thanks a lot!
1746164,2018-02-08 05:29:54 UTC,https://lkml.org/lkml/2018/2/8/5
1746164,2019-05-10 04:38:30 UTC,I am also facing the same issue.
1746164,2019-06-11 12:06:51 UTC,Any update how to solve this problem
1746164,2019-06-11 16:20:25 UTC,"Write ""options ath9k btcoex_enable=1"" to some config file under ""/etc/modprobe.conf.d/""."
1746164,2018-02-02 02:05:06 UTC,It sounds like maybe @peterpall isn't doing what @kaihengfeng asked:
1746164,2018-02-01 16:55:12 UTC,"In my case this configuration results in
 - a bluetooth hangs, but only if the WiFi is far away and only about once every minute. But the connection losses I experienced with btcoex_enable=0 bt_ant_diversity=0 are nearly gone.
 - and changing the file in mplayer causes a short audio hang."
1746164,2018-02-02 05:14:56 UTC,I had tried all combinations:
1746164,2018-01-31 07:22:33 UTC,This option should be default in kernel side instead of use a modprobe conf file. I'll send a patch to enable it.
1746164,2018-01-30 06:17:15 UTC,"Interestingly, it appears Intel enables bt_coex for their chips by default:"
1746164,2018-01-30 06:23:13 UTC,"Also, if all you would like to change is kernel parameters:"
1746164,2018-02-01 06:05:47 UTC,"I guess what we want is btcoex_enable=0 bt_ant_diversity=1.
From what I can understand, bt_ant_diversity is the one that can use BT's antenna to be WiFi's RX antenna when BT is off."
1746164,2018-01-30 06:46:59 UTC,I currently run the newest vanilla kernel using an Acer Aspire S7 with an Intel chipset. Still my patch is needed on my system.
1746164,2018-01-30 06:48:00 UTC,The corrected version of my patch (finally containing all files).
1746164,2018-01-30 06:49:19 UTC,...or do we want to mark this bug as duplicate of bug 405294?
1746164,2018-01-30 07:06:47 UTC,Please keep this bug about fixing the issue for ath9k wifi only.
1746164,2018-01-30 06:30:05 UTC,This change was made by a bot.
1746164,2018-01-31 02:16:49 UTC,That probably won't help. The link in comment #5 seems to show the ath9k source in Linus' tree is still defaulting to btcoex_enable=0 bt_ant_diversity=0.
1746164,2018-01-31 05:00:23 UTC,"Daniel,"
1746164,2018-01-31 05:13:52 UTC,I'm using the mainline build right now - and I still need to module parameter in order to have more than 1 minute of bluetooth audio at a time => We should send this patch.
1746164,2018-01-31 05:15:58 UTC,"Kai,"
1746164,2018-01-31 05:17:09 UTC,"We should indeed default to the configuration that is reliable. And if people want to switch to the less reliable, but faster, option then they still can."
1746164,2018-01-31 05:45:34 UTC,"The user won't probably want to do that:
 - The new default reduces the Wifi Speed only while bluetooth is actually trying to send (which isn't too often if the user isn't currently listening to Bluetooth audio) and
 - If Bluetooth/Wifi coecistence isn't enabled Bluetooth (when trying to send on the same frequency as the WiFi) tends to make the Wifi packet impossible to read => The WiFi packet has to be retransmitted => WiFi might get even slower than with Bluetooth-WiFi coexistence enabled.
 - Also since I have enabled Bluetooth-Wifi coexistence my wifi connection has stopped dropping from time to time => my guess is that if Bluetooth can send while WiFi does, this destroys packets and this happens to happen with every packet for a while the connection WiFi might drop as the Bluetooth one might in this case."
1746164,2018-01-30 20:37:40 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1746164,2018-01-31 06:54:16 UTC,Right. So we agree your patch should be applied by default to ath9k. Just as coexistence is enabled by default for Intel wifi. Unless someone more familiar with ath9k has a (better) reason otherwise...
1746165,2018-01-30 08:03:30 UTC,"Well noted, thanks for the reminder! I've moved the issue there and will try to tackle it this week: https://github.com/canonical-websites/developer.ubuntu.com/issues/341"
1746184,2019-01-14 22:01:41 UTC,Clearing the assignee due to inactivity.
1746187,2018-01-30 10:02:13 UTC,"use the commnad  ""#openstack zone list --all"" could list the ptr zone;
use the command ""#designate record-list 0.168.192.in-addr.arpa. --all-tenant"" could list the ptr record;"
1746187,2018-01-31 14:52:10 UTC,@miaoyuliang that is a neutron doc.
1746187,2018-02-01 01:43:05 UTC,"could designate doc add a link to the page of DNS Integration with neutron,or just like the ""Configure the Compute service to use the Networking service"" in neutron doc?
what we need is a combination of designate and neutron,or designate would be work lonely"
1746209,2020-10-01 21:09:59 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/755653"
1746209,2020-09-25 16:01:04 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.opendev.org/754444"
1746209,2020-05-11 18:16:06 UTC,"Reviewed:  https://review.opendev.org/724862
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f5b6dc603c5f6f72ab35ef21ab9e35ec982e3219
Submitter: Zuul
Branch:    stable/queens"
1746209,2018-07-02 20:04:14 UTC,"Reviewed:  https://review.openstack.org/539509
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e91fc7da82755358ae6523842d19968f3ac269de
Submitter: Zuul
Branch:    master"
1746209,2018-05-03 11:21:19 UTC,"Reviewed:  https://review.openstack.org/539508
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8bbad196a7f6a6e2ea093aeee87dfde2154c9358
Submitter: Zuul
Branch:    master"
1746209,2020-05-01 14:56:31 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/724862"
1746209,2018-03-07 23:30:29 UTC,This issue was fixed in the openstack/nova 17.0.1 release.
1746209,2018-03-06 17:01:44 UTC,"Reviewed:  https://review.openstack.org/546085
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6b11eb794f5881c9c8ed284b2edfa4c31ed62b2b
Submitter: Zuul
Branch:    stable/queens"
1746209,2018-02-20 09:13:37 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/546085"
1746209,2018-02-20 00:52:00 UTC,"Reviewed:  https://review.openstack.org/539506
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5895566a428be4c30c31ae94070282566a6cc568
Submitter: Zuul
Branch:    master"
1746209,2018-01-31 12:10:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/539509"
1746209,2018-01-31 12:09:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/539508"
1746209,2018-04-20 13:14:54 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1746209,2018-01-31 12:09:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539506"
1746232,2018-01-31 12:16:57 UTC,This crash looks very similar to #1301649. However is does not require the system to go into power save.
1746232,2018-01-31 12:25:55 UTC,The file name above should read radeon_ring.c. I thought you used to be able to edit comments on here!
1746232,2018-01-31 12:30:07 UTC,This change was made by a bot.
1746232,2018-02-04 17:43:49 UTC,I have raised this bug at https://bugzilla.kernel.org/show_bug.cgi?id=198669
1746237,2018-02-05 17:13:21 UTC,"The file /var/log/syslog is dated 16.09 yesterday, so I presume no entries."
1746237,2018-02-05 17:06:32 UTC,"Right, so I did the following:
0) Printed the file and verified I currently have no problem. Time about 16.40
   You will see that in the log.
1) Change log level to debug2
2) cd ~/hp/hplip-3.17.11
   reverse changes I made to Mode10.cpp (So now I am using the code as supplied.)
   make
   sudo make install
   sudo service cups stop
   sudo service cups start"
1746237,2018-02-02 04:59:38 UTC,"Hi,"
1746237,2018-02-05 17:07:34 UTC,"Right, next the log file"
1746238,2018-02-01 08:10:41 UTC,Thanks for submitting this bug report.
1746238,2018-02-01 09:31:53 UTC,"This has always confused me, I'll be honest. Cinder considers the provisioned backend capacity to be the total allocated volume size on a backend (including non-Cinder volumes), as underlined by https://github.com/openstack/cinder/blob/12.0.0.0b3/cinder/scheduler/host_manager.py#L121-L124"
1746244,2018-01-30 14:00:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1746248,2019-09-17 10:13:31 UTC,Migrated to https://github.com/widelands/widelands/issues/2099
1746250,2018-02-02 12:44:08 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1746250,2018-02-02 13:04:19 UTC,The error is not specific for liferea (I don't know yet which package is responsible for debpython and friends):
1746255,2018-01-30 14:15:05 UTC,"Seems reproducible, one of the id's to check logs is:"
1746268,2019-12-30 19:14:28 UTC,"In our implementation, we modified our print template defaults to capitalize the titles as such:"
1746271,2018-04-07 14:09:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746271,2020-08-28 14:53:03 UTC,"Bionic shipped with 1.2.4-1 so it has the fix, as such marking as fix released."
1746273,2018-02-07 07:00:07 UTC,"Same problem with latest kernel.
I was just able to see the message ""loading initial ram..."" before the reboot..."
1746273,2018-01-30 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746273,2018-01-30 20:31:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1746273,2018-02-07 06:57:59 UTC,"Same problem with kernel 4-15.
I just see ""loa"
1746273,2018-01-30 16:43:38 UTC,"Unable to add any report : just after the grub menu, the system reboot to the bios."
1746275,2018-02-01 15:56:02 UTC,"I don't know if this helps, but I've discovered that in command line mode (inkscape -C -e ...) inkscape can export a correct-looking PNG of this image in a fraction of a second."
1746276,2018-01-30 17:06:02 UTC,Thanks for reporting.
1746276,2018-01-30 18:41:50 UTC,Thanks for the info.
1746276,2018-01-30 23:55:03 UTC,*** This is an automated message ***
1746277,2018-01-31 02:49:28 UTC,It appears you are experiencing the old 25 second dbus timeout delay at least...
1746277,2021-01-09 22:54:02 UTC,"I have the same bug after upgrading Focal:
https://askubuntu.com/questions/1301972/hotkeys-respond-lag-updating-notification-area-player-lags-wi-fi-icon-update-s"
1746277,2021-01-09 22:57:59 UTC,"I'm getting those strange log lines:
Jan 10 00:55:08 user-Lenovo-ideapad-320S-15IKB org.freedesktop.Notifications[3468614]: org.kde.knotifications: WaitForName: Service was not registered within timeout
Jan 10 00:55:08 user-Lenovo-ideapad-320S-15IKB dbus-daemon[2433]: [session uid=1000 pid=2433] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
Jan 10 00:55:08 user-Lenovo-ideapad-320S-15IKB unity-settings-[2886]: Failed to connect to proxy"
1746277,2021-01-09 23:09:13 UTC,"With ""unity-settings-daemon --debug -r"" for changing screen brightness, I'm getting
(unity-settings-daemon:3474363): libnotify-WARNING **: 01:08:12.601: Failed to connect to proxy
(unity-settings-daemon:3474363): media-keys-plugin-WARNING **: 01:08:12.603: Failed to get old screen percentage: Timeout was reached"
1746277,2021-01-09 23:27:09 UTC,Figured it out: running /usr/lib/notification-daemon/notification-daemon solves the issue.
1746278,2018-02-16 18:27:29 UTC,"We have also had these issues and can confirm especially the last one - right click and open in a new tab opens the Home page instead of whatever action you were clicking on.  Ours was reported from Item Status screen, so it's definitely more than one screen."
1746278,2018-05-23 20:05:46 UTC,I can confirm that these are still issues in 3.1.
1746278,2019-08-20 13:26:19 UTC,I can confirm the problem in 3.3.2
1746280,2018-01-31 10:34:20 UTC,Try with live usb if you can reproduce.
1746289,2018-01-30 17:37:33 UTC,"That label change is probably premature; there was a FIXME asking about it in the code that made the change.  The real point is that those settings should only affect the XUL client (and maybe some Dojo interfaces), and that a new set of settings exist that affect the web client.  When the XUL client goes away, so should those associated settings."
1746289,2019-08-19 08:05:40 UTC,"The ""Deprecated: Format Dates with this pattern"" setting (possibly unintentionally) affects the date format in the calendar widget."
1746297,2018-01-30 17:37:59 UTC,https://redmine.darktable.org/issues/11982
1746317,2018-02-06 20:48:50 UTC,"Yes, that worked. I think deleting the ~/packstackca directory really did it. I did not think to delete that one since it is on the system running the packstack script rather than the conroller node."
1746317,2018-02-02 20:51:45 UTC,"Hello Javier,"
1746317,2018-02-05 17:54:42 UTC,"The answer file looks ok, I have retested with the same SSL parameters and everything worked fine for me, so maybe the issue is in those leftover files you mentioned."
1746317,2018-01-30 22:35:05 UTC,The problem seems to be that packstack is not creating /etc/pki/tls/certs/packstack_cacert.crt
1746317,2018-01-30 21:35:51 UTC,"Ah, it is a CA file. Changing the entry in /etc/httpd/conf.d/15-horizon_ssl_vhost.conf to:"
1746317,2018-02-02 17:24:08 UTC,"Hi Father,"
1746317,2018-01-30 19:22:32 UTC,"manually creating the certifcate with ""openssl req -x509 -sha256 -newkey rsa:2048 -keyout packstack_cacert.key -out packstack_cacert.crt -days 1024 -nodes"" and moving the files to the proper locales still did not work."
1746322,2018-01-31 16:56:42 UTC,No USN needed
1746322,2018-01-31 17:25:02 UTC,This bug was fixed in the package linux-aws - 4.4.0-1050.59
1746322,2018-01-31 18:01:03 UTC,The package has been published and the bug is being set to Fix Released
1746323,2018-02-01 21:40:46 UTC,"Yup, definitely agree, and it's not just network_data.json, but everything in the metadata / config drive response."
1746323,2018-02-01 21:41:46 UTC,Related ML thread:
1746324,2018-01-31 18:00:35 UTC,The package has been published and the bug is being set to Fix Released
1746324,2018-01-31 17:25:20 UTC,This bug was fixed in the package linux-aws - 4.4.0-1012.12
1746324,2018-01-31 16:57:08 UTC,No USN needed.
1746326,2018-04-06 15:40:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746340,2019-12-19 02:04:07 UTC,"Hi Lucas, do you have tried with new SSD? I don't think this is the hw issue. My SSD Power Cycles is only 807. Eventually, if not having any other solution, i think i will buy new SSD, do you know which type of SSD would work properly with linux?
Smartctl output:
sudo smartctl -t long -a /dev/nvme0n1p2
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.0.0-37-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org"
1746340,2019-12-18 18:20:01 UTC,"Hi trong luu, I didn't test it, but I think that it depends on the way VMware virtualizes access to the disk. There may be multiple ways, one of which will work."
1746340,2019-12-18 13:01:55 UTC,"Hi Lucas, is it ok if installing window and using ubuntu in VMware?"
1746340,2019-12-18 10:29:16 UTC,"After running cat /sys/module/nvme_core/parameters/default_ps_max_latency_us command and output is 0.
sudo nvme get-feature -f 0x0c -H /dev/nvme0n1p2
get-feature:0xc (Autonomous Power State Transition), Current value:00000000
 Autonomous Power State Transition Enable (APSTE): Disabled
 Auto PST Entries	.................
 Entry[ 0]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 1]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 2]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 3]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 4]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 5]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 6]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 7]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 8]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[ 9]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[10]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[11]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[12]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[13]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[14]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[15]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[16]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[17]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[18]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[19]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
 Entry[20]
 .................
 Idle Time Prior to Transition (ITPT): 0 ms
 Idle Transition Power State   (ITPS): 0
 .................
..."
1746340,2019-12-18 10:06:15 UTC,"Hi
try:"
1746340,2019-12-18 09:59:21 UTC,"Hi Juan, i have tried with your suggest many time but the problem still happens. I also tried with nvme_core.default_ps_max_latency_us=0 but no hope. I'm not sure the APST be disabled. How to check APST status when system booted?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/core.c#n2282"
1746340,2019-12-18 09:46:08 UTC,"For anyone struggling with this hideous bug, try the following:"
1746340,2019-11-28 02:15:08 UTC,"Hi tronglx,"
1746340,2019-12-18 04:24:12 UTC,"Hi trong luu, for me the error happened every day, which is why I ended up using Qubes. It's the only way that I could find except for Windows"
1746340,2019-12-18 04:09:11 UTC,The error still happens.
1746340,2019-12-07 03:24:18 UTC,"I switched to recovery mode and run: mount -o remount,rw /. The problem no longer appears, it seem be fixed."
1746340,2019-11-28 03:03:21 UTC,"Thank Lucas,
It just happened to my laptop. I will try find out the solution."
1746340,2019-12-19 02:19:15 UTC,"Hu trong lu. I indeed bought a new SSD because I thought mine was faulty. However I bought one of the same brand (Samsung). I didn't have the idea of buying another brand. Anyways, the brand new SSD also has the problem."
1746340,2019-11-28 02:00:24 UTC,"Thank Lucas, do you have tried with arch linux? Qubes OS is very strange with me. I'm developer and os community is very importance."
1746340,2019-11-27 15:19:21 UTC,"Hi tronglx, the only way I found was to install Qubes OS"
1746340,2019-11-27 15:01:00 UTC,"Hi lucas, i have the same problem. My laptop is matebook x pro 2018 and nvme LITEON CA3-8D512. My working is on linux and it is an unpleasant experience. Currently, when issue occurs, i power off/on my laptop (one times or more) and it can work normally in a few hours. Do you have any another suggest about linux distributions?"
1746340,2019-12-18 09:14:25 UTC,"I think other SSD type is last option. But, i really want find out root cause of the problem. As my understanding, system booted up with Opts: errors=remount-ro. Then something went wrong, system switched to ro mode to protect file system. Do you have checked system log, have any abnormal log? NVME is becoming more and more popular. This is the big problem with linux user."
1746340,2019-12-19 02:29:53 UTC,"Thank Lucas, i think i will buy another type of SSD. Do you have any suggestion?"
1746340,2020-02-13 05:39:32 UTC,"Craigums Carlonious,"
1746340,2019-12-19 04:04:40 UTC,"Thank you. My SSD is LITEON CA3-8D512, not Samsung. So, would i buy another type of SSD? non nvme?"
1746340,2020-05-03 18:49:18 UTC,"I thought I could help in some way with more information. By the way, I've found the solution and my SSD works fine right now. You may want to take a lookt at https://bugzilla.kernel.org/show_bug.cgi?id=201685. Comment #294 (https://bugzilla.kernel.org/show_bug.cgi?id=201685#c294), in particular, helped me to solve the problem."
1746340,2020-03-09 12:57:57 UTC,"Ramon,
Please file a separate bug since it's platform specific."
1746340,2020-03-07 17:03:51 UTC,"I also had this problem of it working for a year, then I update it and it stops working. Then I roll back the kernel and it won't work again"
1746340,2020-03-07 13:17:33 UTC,"I have a Dell Inspiron 14 5000 Series-5480. The most strange thing is that I bought my laptop about 1 year ago and I've installed Ubuntu 18.04.1 with kernel 4.15.0-65-xxx (default installation) and everything worked as expected. However, the same problem happened with any other kernel version (including 4.17.0-041700-generic)."
1746340,2020-03-06 20:55:03 UTC,"Ramon, which hardware is yours? Razer?"
1746340,2020-03-06 19:34:48 UTC,"BTW, pcie_aspm=off and nvme_core.default_ps_max_latency_us=5500 didn't work."
1746340,2020-03-06 19:06:38 UTC,Hello all!
1746340,2019-12-19 02:37:28 UTC,"The other 2 good brands I know are Corsair and WD Black. Don't buy Samsung, the majority of people with this problem have Samsung"
1746340,2020-02-25 09:06:54 UTC,"No I have a laptop from a XMG, it is a German brand."
1746340,2020-02-24 08:40:01 UTC,an update on this:
1746340,2020-02-14 06:38:19 UTC,"Hi Kai-Heng Feng, please note that after I installed Qubes, I never ever had the problem again. It may be useful in the debug process, and maybe the way Xen, PCIe and Linux work together in Qubes can give a hint on what's happening. Thank you for all your help to this day."
1746340,2020-02-14 05:24:56 UTC,Can you please attach `sudo nvme id-ctrl /dev/nvme0`?
1746340,2020-02-13 17:39:30 UTC,"Hi, yes I also am trying to install onto the razer blade stealth like a lot of the other people above which have the SAMSUNG MZVLB256HAHQ-00000 nvme ssd. Getting the I/O Error and have tried most of the fixes mentioned above, but no luck, and I would rather continue using Windows instead of Qubes."
1746340,2020-02-13 05:17:23 UTC,"It's 2020, is there still no solution to this problem? Getting this error with ubuntu 18 LTS and 19"
1746340,2019-12-19 04:23:00 UTC,Thank Lucas.
1746340,2019-12-19 04:12:12 UTC,"non nvme SSDs are pretty slow, like 8 times slower. Stick with NVME and if nothing works install Qubes"
1746340,2020-02-24 20:47:07 UTC,"Juan, which hardware you're on? Razer?"
1746340,2019-11-17 16:08:44 UTC,I have exactly the same drive:
1746340,2019-11-17 16:25:10 UTC,"Hi Juan, what computer you are in?"
1746340,2018-02-08 02:19:19 UTC,"I added an USB wireless receiver to use internet to download things so I can see if something happens. I installed more system updates through the ubuntu software updates. Is this ok? The kernel will still be yours, rigtht?"
1746340,2018-01-30 23:21:14 UTC,apport information
1746340,2018-01-30 23:21:11 UTC,apport information
1746340,2018-01-30 23:21:09 UTC,apport information
1746340,2018-01-30 23:21:07 UTC,apport information
1746340,2018-01-30 23:21:06 UTC,apport information
1746340,2018-01-30 23:21:04 UTC,apport information
1746340,2018-01-30 23:21:02 UTC,apport information
1746340,2018-01-30 23:21:01 UTC,apport information
1746340,2018-01-30 23:20:59 UTC,apport information
1746340,2018-01-30 23:20:58 UTC,apport information
1746340,2018-01-30 23:20:57 UTC,apport information
1746340,2018-01-30 23:20:55 UTC,apport information
1746340,2018-01-30 23:20:54 UTC,apport information
1746340,2018-01-30 23:20:51 UTC,apport information
1746340,2018-01-30 23:20:50 UTC,apport information
1746340,2018-01-30 20:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746340,2018-01-30 20:29:32 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1746340,2018-01-30 23:21:16 UTC,apport information
1746340,2018-01-30 23:23:02 UTC,"Which kernel should I install exactly, and how to? Don't feel safe to download from http"
1746340,2019-10-11 07:23:39 UTC,"Hi, I didn't find the root of the problem, **BUT**..."
1746340,2018-01-31 05:15:37 UTC,"Uhh sans the ""less"", thanks."
1746340,2018-02-08 02:15:45 UTC,"After installing everything, I rebooted to use the new kernel. I then installed updates on the machine to see if the problem would happen (easier way to make it happen is on the moment I try to update). After the update, wireless stopped working. Restarted many times and still not working."
1746340,2018-01-31 05:15:22 UTC,This is a known issue for Samsung NVMe.
1746340,2018-02-08 02:06:19 UTC,I downloaded again and it seems that this time it wasn't corrupted.
1746340,2018-02-07 21:28:25 UTC,Thanks. What's a 'PCI reset for NVMe device after resume'?
1746340,2018-02-06 14:34:13 UTC,"Initially I noted that it'd happen after opening the lid of the notebook, so yes. But now after I install Ubuntu it immediately starts looking for software updates and that's when the problem happens for the first time, when I haven't even had time to close the notebook to suspend it."
1746340,2018-02-06 05:44:13 UTC,Does the issue happen after system suspend?
1746340,2018-02-06 03:46:00 UTC,"I found a guy with same problem as mine and had a Razer Blade Stealth, but he didn't post anything more after that. And he was in a thread with you. I also found some people with this same problem on the same SSD. Together with the fact that I had no problem on windows (ore than 24hrs of usage by now) I think it can be fixed in the kernel."
1746340,2018-02-05 20:44:32 UTC,I searched and found nothing.
1746340,2018-02-05 14:52:57 UTC,"I am not familiar with Windows, is there anyway to check its APST table? I'd like to see if deepest power state is enabled or not."
1746340,2018-02-07 09:19:06 UTC,Please try [1]. It will do a PCI reset for NVMe device after resume.
1746340,2018-02-05 05:42:27 UTC,"On debian (4.9) I didn't notice the issue but I didn't use much. HOWEVER, when I do apt-get upgrade on debian I do get the issue. It just updated the kernel file, didn't run the new kernel (a boot would have to happen)."
1746340,2018-02-05 05:29:52 UTC,"So you have the issue on Linux v4.15 with nvme_core.default_ps_max_latency_us=0, but not on v4.9?"
1746340,2018-02-04 08:26:49 UTC,"Problem persists with 4.15.0-041500-generic, just happened"
1746340,2018-02-04 08:16:43 UTC,I just installed 4.15.0-041500-generic
1746340,2018-01-31 05:38:47 UTC,"Thank you for your answer. I'm desperated. I just installed debian therefore I'm not going to able to do it right now, but I have output from the last time I was using Ubuntu."
1746340,2018-02-04 05:55:10 UTC,"Hi! I managed to install ubuntu again, these are the outputs you asked for the ms tie of 0 milliseconds:"
1746340,2018-02-03 23:19:34 UTC,"Hi. I've been trying to install Windows 10 in order to try to update my SSD firmware, but I'm getting an error:"
1746340,2018-01-31 06:01:53 UTC,Kai-Heng
1746340,2018-02-05 05:45:17 UTC,I forgot to mention that I reinstalled windows and everything is fine. Even did a benchmark test on the SSD and I'm downloading lots of files to test
1746349,2018-09-07 06:54:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746350,2018-07-08 12:07:08 UTC,"I have attached a sample to this issue. The minor lines are the lines at the end of some of the verses which just contain (repeat). The major/minor text option is on a per-line basis, rather than formatting specific parts of text, meaning either the whole line is in the main colour or the alternative colour."
1746350,2018-07-07 11:44:31 UTC,"I have been having this same issue - it appears to be related to minor words (which show as different coloured text on the display screen, and non-bold text on the operator screen) as all other files are importing properly."
1746350,2018-07-07 15:03:35 UTC,"Hey,
I wrote the WoW importer, but unfortunately I no longer have access to WoW anymore! Would you be able to send several songs without any of the mentioned formatting, and then modify the songs to include the formatting. Do not change anything else, do not edit the text in any way, just add the formatting to some of the lyrics. I'll take a look to see what I can do."
1746355,2018-06-28 06:48:35 UTC,update ?
1746357,2018-02-06 06:38:50 UTC,"Kai-Heng, it seems you have a bug. Both videos play fine here with firefox or VLC or Totem."
1746357,2018-02-06 05:21:36 UTC,"Unfortunately, I can't play any video you attached"
1746357,2018-02-05 22:42:10 UTC,"Bib, the issue you are reporting is an upstream one. Could you please report this to them via https://bugs.freedesktop.org/enter_bug.cgi?product=DRI :
Component: DRM/Radeon"
1746357,2018-02-05 20:00:52 UTC,Another shoot. Should I remove the 2 previous ones?
1746357,2018-02-05 19:57:01 UTC,"The (bad) Artist, v4.15.1. This is awful, how can you get info from this. I set resolution to highest possible and enabled auto-stabilization.
Don't we have in linux something like the /debug option of windows NT boot.ini that allows to dump boot to a serial port ?"
1746357,2018-02-05 16:51:20 UTC,"Bib, could you please attach a video of when removing the boot options while using the latest kernel 4.15.1 (4.15 is slightly older)?"
1746357,2018-02-05 16:23:44 UTC,Just tried : bootloop in K4.15 without radeon.dpm=0
1746357,2018-02-06 07:04:54 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=104963
1746357,2018-02-01 16:49:40 UTC,Bib:
1746357,2018-02-05 14:46:21 UTC,I think you should try latest mainline kernel first. There are lots of radeon fixes since v4.10.
1746357,2018-01-30 22:00:08 UTC,This change was made by a bot.
1746357,2018-01-30 23:03:47 UTC,"Bib, thank you for reporting this and helping make Ubuntu better."
1746357,2018-02-01 10:45:41 UTC,"News : please note that when creating the new stick over the existing one I wasn't prompted to create persistent storage (maybe the disk-creator used the one previously created, I don't know, but a new dummy folder on the desktop in the daily-bionic live once first booted as a check for this question didn't survive next reboot, so I assume the whole key is read only)."
1746357,2018-01-31 10:05:24 UTC,"I can't boot the system: after selecting the live USB as the boot drive, a message displays 1s repetitive ~CRC32~* or something like that. Then I have to type TAB key (nothing on screen drives to this action). Once TAB key was pressed, I select ""live"" option, then the system reboots in seconds. I also tried ""help"" but before I can read the whole F2-F10 that keep scrolling up out of the screen at the same rate the ~CRC32~ did, the installer takes some option the reboots on its own. I also tried F4 but nothing helpful happened."
1746357,2018-01-31 08:29:00 UTC,"Hi Christopher.
Will a live test be enough ?"
1746357,2018-02-01 09:11:03 UTC,"1)Captures attached
2)I'll give a try to this and report."
1746357,2018-01-31 18:57:39 UTC,Bib:
1746368,2018-03-21 14:58:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746369,2018-01-30 23:35:00 UTC,"The build works again after applying this patch (also attached):
--- pbzip2.cpp
+++ pbzip2.cpp
@@ -1220,7 +1220,7 @@ int producer_decompress(int hInfile, OFF_T fileSize, queue *fifo)
                        // give warning to user if block is larger than 250 million bytes
                        if (fileData->bufSize > 250000000)
                        {
-                               fprintf(stderr, ""pbzip2:  *WARNING: Compressed block size is large [%""PRIuMAX"" bytes].\n"",
+                               fprintf(stderr, ""pbzip2:  *WARNING: Compressed block size is large [%"" PRIuMAX "" bytes].\n"",
                                                (uintmax_t) fileData->bufSize);
                                fprintf(stderr, ""          If program aborts, use regular BZIP2 to decompress.\n"");
                        }
@@ -1829,7 +1829,7 @@ void *fileWriter(void *outname)"
1746382,2018-01-31 00:51:32 UTC,Meant to paste this:
1746386,2018-02-08 14:14:34 UTC,"Yeah I've hit this before too, it's due to the newish nova dependency on the whereto library that depends on pcre."
1746386,2018-02-08 17:31:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/542340"
1746386,2018-02-13 21:54:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544108"
1746386,2018-02-14 07:31:20 UTC,"Reviewed:  https://review.openstack.org/542340
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6c2353bfe820e344376b5f68bd0e6055a8a6d421
Submitter: Zuul
Branch:    master"
1746386,2018-02-16 05:57:13 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc2 release candidate.
1746386,2018-04-20 13:14:48 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1746386,2018-02-16 04:52:15 UTC,"Reviewed:  https://review.openstack.org/544108
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a790ff8ff08ca9d2ddcdd42ad690b81bf5038ee4
Submitter: Zuul
Branch:    stable/queens"
1746394,2019-05-14 21:39:11 UTC,"I'm hitting this issue on Fedora 30 after an in-place upgrade.  Using gnome-boxes, I click on a virtual machine to open the console viewer and it crashes after a hang.  Terminal output looks like this:"
1746400,2018-01-31 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746403,2018-02-06 17:59:50 UTC,"Thanks for logging the issue, Brett. Unfortunately, for historical reasons, both `<project root>/snapcraft.yaml` and `<project root>/snap/snapcraft.yaml` are valid locations. The problem here is that Snapcraft isn't doing a good job of determining which it actually is. When you run snapcraft from within the snap directory, it thinks it's the former, when it actually needs to be run as the latter. We can do some heuristics to try and reason it out, though: check for the presence of a `hooks` directory, a `gui` directory, a `plugins` directory, etc. (things that typically go in the `snap` dir). If they're found, we can reasonably determine that snapcraft is being run in the wrong area."
1746407,2018-02-06 09:24:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746411,2018-02-15 15:12:18 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1746411,2018-02-21 19:08:44 UTC,This bug was fixed in the package linux-oem - 4.13.0-1021.23
1746411,2018-01-31 06:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746411,2018-02-09 06:43:33 UTC,I guess a subset of the patches is needed for bionic too
1746411,2018-02-09 07:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746413,2018-02-02 12:43:12 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1746419,2018-02-14 20:06:35 UTC,"I believe this is systemd intentional to not change bond parameters if the bond already exists. It is assumed that something else has already created the bond, and thus networkd should not be ""updating"" the params. Despite networkd creating the bond in the first place..."
1746419,2018-02-15 00:09:13 UTC,"Right, so netplan should tell networkd to tear down the bond first?"
1746419,2018-05-24 07:06:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746419,2018-05-24 09:01:38 UTC,networkd does not have a toggle to tear down the bond first =/ or to force changing the parameters of it. Maybe a toggle like that should be added to really-really reload all the settings.
1746419,2018-07-23 10:10:46 UTC,"Netplan could delete the bond, which would then be recreated by networkd with all parameters applied."
1746419,2018-07-24 01:45:31 UTC,"Should it though? That will, for example, terminate any tcpdump processes bound to the bond, it will disrupt currently running connections, etc. Maybe we could do it but we'd want to put it behind a --force option or something, I think."
1746419,2018-02-14 18:03:40 UTC,"Sounds like this is a bug in systemd, since it's what will deal with the actual devices."
1746420,2020-08-24 04:17:16 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1746420,2020-06-24 05:22:14 UTC,"Please let us know if you still experience this problem, and if so whether any processes are using high CPU or lots of memory."
1746429,2019-07-30 03:29:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746438,2020-11-18 08:19:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746438,2018-02-19 18:19:35 UTC,"I can confirm that removing intel-microcode package restores suspending to ram functionality.
Also see: https://askubuntu.com/questions/967561/xps15-fails-to-suspends-after-upgrade-to-ubuntu-17-10"
1746446,2018-03-19 17:33:12 UTC,"Sometime ago I had this : https://review.openstack.org/#/c/472681/
Maybe it's time to resurrect it."
1746447,2018-01-31 12:28:36 UTC,Is the pool presence causing any faulty behavior?
1746447,2018-01-31 14:24:39 UTC,Pool presence not causing any faulty behavior but why to add such entries in neutron db which is not been used and added during exception.
1746447,2018-01-31 16:34:18 UTC,neutron-lbaas is now maintained by the octavia team. Forwarding the bug to octavia.
1746447,2018-02-01 03:40:09 UTC,"Note, all LBaaS related projects have moved to using OpenStack storyboard (all projects are being migrated).
https://storyboard.openstack.org"
1746447,2018-02-01 03:40:22 UTC,"Closing this bug as I have moved it to neutron-lbaas in storyboard.
https://storyboard.openstack.org/#!/story/2001511"
1746448,2018-02-01 03:21:22 UTC,"Note, all LBaaS related projects have moved to using OpenStack storyboard (all projects are being migrated).
https://storyboard.openstack.org"
1746448,2018-01-31 16:32:24 UTC,neutron-lbaas is now maintained by the octavia team. Forwarding the bug to octavia.
1746448,2018-02-01 03:24:42 UTC,"This bug is invalid and will not be moved to Storyboard.
Allowing HTTP health monitors is by design. There are applications where a ""health"" page is exposed via HTTP on hosts using HTTPS for the main customer traffic. For example an HTTP health monitor with a check URL of /healthcheck."
1746450,2018-01-31 16:33:21 UTC,neutron-lbaas is now maintained by the octavia team. Forwarding the bug to octavia.
1746450,2018-02-01 03:15:36 UTC,"Closing this bug as I have moved it to neutron-lbaas in storyboard.
https://storyboard.openstack.org/#!/story/2001510"
1746450,2018-02-01 03:19:21 UTC,"Note, all LBaaS related projects have moved to using OpenStack storyboard (all projects are being migrated).
https://storyboard.openstack.org"
1746463,2018-04-03 14:37:37 UTC,This bug was fixed in the package linux-gcp - 4.13.0-1012.16
1746463,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1746463,2018-03-19 10:57:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1746463,2018-03-06 17:30:05 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1001.1
1746463,2018-02-27 19:59:11 UTC,"Since this is going to be fixed in 'linux' and 'linux-gcp', adding tasks for those."
1746463,2018-02-27 19:54:39 UTC,"Add a snapd task so that when the https://launchpad.net/ubuntu/+source/linux-gcp is Fix Released, snapd can re-enable the tests/main/lxd test on GCE."
1746463,2018-02-27 19:52:33 UTC,Here are more details on the snapd test failure: https://forum.snapcraft.io/t/lxd-issue-due-to-snap-confine-apparmor-profile/4203/18
1746463,2018-02-27 20:54:40 UTC,"FYI, the following kernels are also affected (all 4.13 based):
* linux-azure
* linux-hwe
* linux-hwe-edge
* linux-oem
* linux-raspi2"
1746463,2018-02-27 19:21:16 UTC,"This is affected snapd spread tests in GCE, where they have a xenial userspace and 4.13 kernel:"
1746463,2018-02-02 00:05:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746481,2019-01-12 01:54:23 UTC,"Good comment - I was not satisfied with my code, because things became too complicated and fragile...
But my stance is the same as before - this is not bug, because the basic economy works as intended and designed, but only an improvement, though reasonable improvement but the change is not straightforward..."
1746481,2019-09-17 07:35:34 UTC,Migrated to https://github.com/widelands/widelands/issues/1699
1746481,2019-01-12 09:35:35 UTC,So implementing this is a feature and were in feature freeze ...
1746481,2019-01-11 10:38:59 UTC,"hm, your last comment on the merge proposal is to delete it?"
1746481,2019-01-09 21:41:31 UTC,What is the state of this bug report?
1746481,2018-02-03 22:31:10 UTC,"OK, it was not that difficult at the end and the branch is ready, please test it, and especially saving/loading before the basic economy is loaded."
1746481,2018-01-31 14:48:29 UTC,"Yes, there is something like can_start_working(), but whole setup needs periodical check of all productionsites to see if all needed are staffed, moreover, some of them might had been upgraded in the meantime. Also savegame would be affected, because now it saves list of remaining building. So yes, can be done, but not in handful of lines..."
1746481,2018-01-31 14:22:15 UTC,"ProductionSite::working_positions_[].worker is what you're looking for - I don't know if there is a public function to access this, you might have to add one."
1746481,2018-01-31 12:29:19 UTC,"Well, basic economy was intended as it is now - to make sure that some critical buildings are built before AI runs out intitial critical building material. What you suggest is a step further and some complication to the code. But makes sense, of course.... Now, if AI gets some building, it is scratched from a list of remaining/missing buildings."
1746481,2019-01-09 22:19:34 UTC,In fact I don't remember:) looks like ready for testing...
1746483,2018-02-26 16:35:04 UTC,"Hi!
Is it possible that this will also fix https://bugs.launchpad.net/nova/+bug/1655030 ?"
1746483,2018-02-16 05:57:14 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc2 release candidate.
1746483,2018-02-16 04:52:38 UTC,"Reviewed:  https://review.openstack.org/543594
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ed959b94ee8a211a270d9d89a6021e76a16bf31f
Submitter: Zuul
Branch:    stable/queens"
1746483,2018-02-16 05:00:19 UTC,"Reviewed:  https://review.openstack.org/543595
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4c6443c0b5579853f4b87eb8302d24aca99dddab
Submitter: Zuul
Branch:    stable/queens"
1746483,2018-03-21 13:37:14 UTC,"Reviewed:  https://review.openstack.org/543602
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3ff30f407c36264641ea8a1bfe8849d9e7a75f0e
Submitter: Zuul
Branch:    stable/pike"
1746483,2018-02-16 05:00:31 UTC,"Reviewed:  https://review.openstack.org/543596
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c1dfe464bbe2c1a5b0e306285a86c814ceff9e80
Submitter: Zuul
Branch:    stable/queens"
1746483,2018-03-21 21:42:52 UTC,"Reviewed:  https://review.openstack.org/543603
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb723851707d6a764cb8154343087affc19e5db0
Submitter: Zuul
Branch:    stable/pike"
1746483,2018-05-02 12:02:15 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1746483,2018-04-02 13:18:58 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1746483,2018-04-17 16:01:18 UTC,"Reviewed:  https://review.openstack.org/543634
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3f3ccfff8e123fc35306b982cab46b55980739e5
Submitter: Zuul
Branch:    stable/ocata"
1746483,2018-04-17 16:05:45 UTC,"Reviewed:  https://review.openstack.org/543635
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=88c51bde8c47b14e2750c5eb48f9c37b3a1c2ef7
Submitter: Zuul
Branch:    stable/ocata"
1746483,2018-04-17 16:05:57 UTC,"Reviewed:  https://review.openstack.org/543636
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8430cbbc972740a80a774278b4f645b193dbdfa9
Submitter: Zuul
Branch:    stable/ocata"
1746483,2018-04-20 13:14:39 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1746483,2018-03-21 21:43:37 UTC,"Reviewed:  https://review.openstack.org/543604
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f510e2e7f00f612ad636f4e7fcc188d64285a889
Submitter: Zuul
Branch:    stable/pike"
1746483,2018-02-12 21:59:41 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/543636"
1746483,2018-02-11 22:17:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543263"
1746483,2018-02-12 21:59:06 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/543634"
1746483,2018-02-01 21:38:19 UTC,There are probably two ways to handle this:
1746483,2018-02-11 21:16:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/543257"
1746483,2018-02-11 21:22:03 UTC,It looks like this was likely regressed in Mitaka with this change:
1746483,2018-02-11 21:32:03 UTC,"In debugging a functional test that recreates the failure, I got this:"
1746483,2018-02-11 22:17:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/543264"
1746483,2018-02-12 21:59:26 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/543635"
1746483,2018-02-12 18:08:43 UTC,"Reviewed:  https://review.openstack.org/543263
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0a7427dc58eeb271646a962604106e0e84b870b6
Submitter: Zuul
Branch:    master"
1746483,2018-02-12 18:08:19 UTC,"Reviewed:  https://review.openstack.org/543257
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f9667b7a92ffef4329380e39c64cf314203b06e
Submitter: Zuul
Branch:    master"
1746483,2018-02-12 19:49:48 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/543594"
1746483,2018-02-12 19:50:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/543595"
1746483,2018-02-12 19:50:22 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/543596"
1746483,2018-02-12 20:17:39 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/543602"
1746483,2018-02-12 20:17:57 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/543603"
1746483,2018-02-12 20:18:12 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/543604"
1746483,2018-02-12 18:09:02 UTC,"Reviewed:  https://review.openstack.org/543264
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=60bbec15ed319ce703d49667b2649289639a86da
Submitter: Zuul
Branch:    master"
1746483,2018-02-01 21:34:17 UTC,"Hmm, it appears that the IsolatedHostsFilter doesn't take into account that when you boot from volume, there doesn't need to be an image provided to the server create request, and therefore the RequestSpec likely won't have an image, or at least an image with an id, since the root disk is going to have the volume which has the OS image in it."
1746484,2019-08-12 11:58:08 UTC,"all armhf builds look good (i think tests are enabled and would FTBFS), please re-open if i'm wrong."
1746486,2018-09-04 20:02:09 UTC,"Any update ?  i just found this issue also in watcher-dashboard , still present in queens ( maybe in rocky also , but I haven't check yet )"
1746486,2018-09-04 20:06:47 UTC,same symptoms :
1746505,2021-02-18 16:46:00 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1746508,2018-07-26 13:36:25 UTC,"Tested in 3.1.3
When adding a tag to MARC record, the cursor focus does not jump to the new tag as in 3.0.1"
1746508,2019-05-24 21:35:50 UTC,I have tested cursor focus in 3.3.0
1746508,2019-05-28 14:54:39 UTC,"Thanks, Eva! I've marked it Won't Fix since it's no longer a problem."
1746508,2018-04-30 18:45:57 UTC,Confirmed in 3.1
1746508,2018-06-24 15:13:40 UTC,"Just a note that it's very unintuitive to add a subfield delimiter and not be able to immediately add the subfield code.  When creating a new subfield a, I'm really used to doing <CTRL + D> then <b>, not <CTRL + D> then <Tab> then <b>.  Unfortunately, if I do <CTRL + D> then <b>, it typically results in losing the data in the previous subfield, too. :-("
1746509,2018-04-20 13:13:09 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1746509,2018-04-02 13:18:35 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1746509,2018-04-02 13:09:03 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1746509,2018-03-29 18:50:54 UTC,"Reviewed:  https://review.openstack.org/555923
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a6310ddc4ec2eeef39a51dd5a2fa86ae9c4b972
Submitter: Zuul
Branch:    stable/pike"
1746509,2018-03-29 18:50:42 UTC,"Reviewed:  https://review.openstack.org/555058
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=26870a01ac2644e79233239b1a6d09050572420f
Submitter: Zuul
Branch:    stable/pike"
1746509,2018-03-28 20:57:01 UTC,"Reviewed:  https://review.openstack.org/555915
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=22b2a8e4645e15990a0f130a8866746497c5b5ee
Submitter: Zuul
Branch:    stable/queens"
1746509,2018-03-28 20:56:41 UTC,"Reviewed:  https://review.openstack.org/555914
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=07a1cbb5a113e9abe497445cb5960b8412823bdd
Submitter: Zuul
Branch:    stable/queens"
1746509,2018-03-23 21:29:57 UTC,"Reviewed:  https://review.openstack.org/555093
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b1ed92c7af01a9ac7e122a541ce1bdb9be0524c4
Submitter: Zuul
Branch:    master"
1746509,2018-03-23 21:15:16 UTC,"Reviewed:  https://review.openstack.org/555092
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=464985a4d58f45ee6a5e8f8705cdcdddcd365038
Submitter: Zuul
Branch:    master"
1746509,2018-03-23 20:20:40 UTC,"This should be High actually, for the Pike version of the bug, because anyone upgrading from Ocata -> Pike will hit this and be unable to list instances."
1746509,2018-03-23 20:06:55 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/555923"
1746509,2018-03-21 23:32:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555093"
1746509,2018-03-23 20:02:55 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/555914"
1746509,2018-02-01 20:46:50 UTC,"This was fixed in queens and backported to stable/pike, but we'd need to also backport https://review.openstack.org/#/c/512456/ to stable/ocata (newton is end of life upstream)."
1746509,2018-03-23 20:03:21 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/555915"
1746509,2018-02-01 20:59:55 UTC,A backport gets tricky because we don't have https://github.com/openstack/nova/commit/a5f800b02477e767883ed661e4b0f827d6debe54 in ocata.
1746509,2018-02-02 20:14:21 UTC,"Hi Mike ,
I read the https://bugs.launchpad.net/bugs/1722404 and there is point that bug was fixed at nova 16.0.2 release , but I am running nova 16.0.3 and still have same problem . If you need more information let me know ."
1746509,2018-02-09 02:16:00 UTC,"Hi Andrea Franceschini ,"
1746509,2018-02-08 16:03:45 UTC,"Hello Saulo,"
1746509,2018-03-21 21:35:55 UTC,I've reproduced this behavior in a functional test: https://review.openstack.org/555058
1746509,2018-03-21 21:36:43 UTC,Note that this is only reproducible on stable/pike -- the same bug does not exist after that.
1746509,2018-03-21 22:03:00 UTC,"Going to add a detailed explanation of what's going on here, now that I've traced through all of it."
1746509,2018-03-21 23:32:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/555092"
1746509,2018-03-21 23:33:39 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/555058
Reason: Able to reproduce the same bug on master with:"
1746509,2018-03-21 21:13:55 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/555058"
1746510,2018-02-22 22:18:47 UTC,"Reviewed:  https://review.openstack.org/547094
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=de39220cac079da6e14d6742b2d69b04002e5303
Submitter: Zuul
Branch:    stable/queens"
1746510,2018-06-01 03:12:59 UTC,"After upgrade to eventlet 0.23, I can see below error"
1746510,2018-06-01 03:11:50 UTC,"@Spyros, we probably should consider to close this bug because https://github.com/eventlet/eventlet/issues/172#issuecomment-379421165 has been merged and I have verified it locally and it works."
1746510,2018-02-22 19:44:08 UTC,"Reviewed:  https://review.openstack.org/547016
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=1eb9bf16f5d60c5024b76fdc6691f0dc82e05a81
Submitter: Zuul
Branch:    master"
1746510,2018-02-08 14:22:00 UTC,"Reviewed:  https://review.openstack.org/542198
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=710192a63fd36186e9669cc2ac00dca2cc4fcc81
Submitter: Zuul
Branch:    master"
1746510,2018-02-22 14:49:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/547016"
1746510,2018-02-22 14:41:23 UTC,"The client also breaks the kubernetes scale manager, disabling it until the bug is fixed."
1746510,2018-02-08 14:01:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/542198"
1746510,2018-02-07 14:54:49 UTC,"Reviewed:  https://review.openstack.org/529098
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=cf8468394027ffb1db420a72312b6a9f59b78381
Submitter: Zuul
Branch:    master"
1746510,2018-02-22 18:26:01 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/547094"
1746514,2018-04-20 18:17:39 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/563212"
1746514,2018-08-01 18:36:39 UTC,"Reviewed:  https://review.openstack.org/587810
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=dc7c5a1a2c2f7090a5d82eee273eabc911b3ed4a
Submitter: Zuul
Branch:    stable/pike"
1746514,2018-08-01 12:48:10 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/587810"
1746514,2018-04-23 20:41:43 UTC,"Reviewed:  https://review.openstack.org/563212
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=32d5a88a0e61d3af1930b221551cc318edb2f13f
Submitter: Zuul
Branch:    stable/pike"
1746514,2018-02-10 13:04:07 UTC,"Reviewed:  https://review.openstack.org/539615
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=5defc7a8c4287c05562cbece4314b1760e616a08
Submitter: Zuul
Branch:    master"
1746514,2018-01-31 15:48:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539579"
1746514,2018-02-08 07:06:37 UTC,"Reviewed:  https://review.openstack.org/539579
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ec08df30afdc638bffc6c957a8965812daf64d9e
Submitter: Zuul
Branch:    master"
1746514,2018-01-31 17:44:00 UTC,These patches should take care of enabling panko expirer:
1746514,2018-01-31 17:42:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539615"
1746514,2018-01-31 17:22:10 UTC,"Change abandoned by Pradeep Kilambi (<email address hidden>) on branch: master
Review: https://review.openstack.org/539592"
1746514,2018-02-09 06:03:01 UTC,"Reviewed:  https://review.openstack.org/539592
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=9b0ff39ad59a0b7d81fe5ea2c5bd413bb8ab4bf0
Submitter: Zuul
Branch:    master"
1746514,2018-01-31 16:43:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539592"
1746519,2018-03-15 10:57:42 UTC,"Erik's solution works for me, but every time when i call ""apt upgrade"" the file with hundreds of #padding will be created again."
1746519,2018-02-19 08:44:40 UTC,"Can confirm Erik's solution works ... thanks a lot, you saved me HOURS or DAYS!"
1746519,2018-02-10 11:18:59 UTC,Unfortunately not here:
1746519,2018-02-18 02:35:59 UTC,"I was running into the same/similar error. Inside of /var/lib/dpkg/updates one of the files appeared to be stopping my update process. The contents of the file was,"
1746519,2018-02-08 08:54:04 UTC,"Unfortunately I encountered the same problem. Tried to run it for two hours but after that it remained stuck, so I ctrl+C-ed and then the same error messages showed."
1746519,2018-02-01 20:11:35 UTC,"Exactly the same problem here, updates/installations via the package management system are no longer possible."
1746519,2018-02-01 10:58:53 UTC,It does not work.
1746519,2018-01-31 17:08:05 UTC,You may need to run the following from a terminal:
1746519,2018-01-31 14:00:04 UTC,This change was made by a bot.
1746519,2018-02-10 08:18:36 UTC,I was facing the same issue. After running apt-get autoremove is was resolved/gone.
1746524,2018-02-07 14:34:12 UTC,It looks like you are missing the fixes introduced in https://review.openstack.org/#/c/538979/ . One of the fixes is to only run db_helper.configure_db on the leader.  Can you retry with the latest version of the charm please?
1746524,2018-02-07 15:02:51 UTC,"We hit this again on February 3rd, running the version of the percona cluster charm from tip. The change you reference landed on the 1st."
1746524,2018-02-07 15:07:33 UTC,"Agreed, the more recent crashdump has the new version of the charm."
1746524,2018-02-07 15:32:25 UTC,"I am wondering if this really is a deadlock. The charm error message explicitly mentions a deadlock but the mysql error.log seems to show the cluster becoming split, replication then being disabled then the failed transaction. Also, although the client reports ""Deadlock found when trying to get lock; try restarting transaction"" the mysql error log says ""Check wsrep connection state and retry the query"""
1746524,2018-02-07 17:00:29 UTC,As with Bug #1747498 the percona cluster seems to be getting into a partitioned state. Both supplied crash dumps show errors like the following:
1746524,2019-06-02 04:17:32 UTC,[Expired for OpenStack percona-cluster charm because there has been no activity for 60 days.]
1746527,2018-10-15 20:23:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746528,2018-01-31 20:42:10 UTC,"> I love dark backgrounds, but they are also very hard to pull off design-wise.
"
1746528,2019-09-06 07:54:36 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/123
1746528,2018-01-31 14:38:15 UTC,I have attached a desaturated screenshot. Both the titles and the links (especially visited links) are indeed hard to distinguish.
1746528,2018-01-31 17:22:20 UTC,"I guess what really gets us into trouble here is that we have both dark and light backgrounds. I love dark backgrounds, but they are also very hard to pull off design-wise."
1746528,2018-01-31 16:09:27 UTC,"Yes, i encountered this also a few weeks ago by using the Web Accessibility Evaluation Tool (WAVE)"
1746531,2018-05-02 12:02:49 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1746531,2018-02-05 23:51:52 UTC,"Reviewed:  https://review.openstack.org/540274
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0cac8fac751736aa3c0d89b298abe550d6157531
Submitter: Zuul
Branch:    stable/ocata"
1746531,2018-02-05 22:27:20 UTC,"Reviewed:  https://review.openstack.org/540871
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c0aca1d333628f9174e8db53674787e281e7e0d7
Submitter: Zuul
Branch:    stable/pike"
1746531,2018-02-05 14:44:38 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/539880
Reason: Closing this out, unfortunately you used a fresh Change-Id for this backport resulting in my attempt to update the commit message locally creating a fresh change under https://review.openstack.org/#/c/540871/ . Gerrit isn't going to allow us to use the correct Change-Id here now so I'm going to close this out. My apologies for this, I really didn't mean for this to happen."
1746531,2018-02-15 23:53:19 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1746531,2018-02-02 06:57:57 UTC,"Change abandoned by Ameed Ashour (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/539878
Reason: moved to https://review.openstack.org/#/c/540274/"
1746531,2018-02-02 06:56:26 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/540274"
1746531,2018-02-01 21:26:23 UTC,"Reviewed:  https://review.openstack.org/539654
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eba33a0e2d8aace6fbc889026fb80dc2c208bc8d
Submitter: Zuul
Branch:    master"
1746531,2018-02-01 10:05:08 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/539880"
1746531,2018-02-01 09:57:51 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/539878"
1746531,2018-01-31 20:02:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539654"
1746531,2018-02-05 14:37:26 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/540871"
1746531,2018-02-09 07:13:29 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1746533,2018-01-31 16:30:10 UTC,This is not a neutron bug. The affected project is changed to horizon.
1746533,2018-01-31 18:04:04 UTC,"If we add a logic to check a case reported here, we need to replicate the neutron logic. The neutron logic is found here: https://github.com/openstack/neutron/blob/f5e7cff7026488acf779909479a82c927a871a20/neutron/db/l3_db.py#L628-L644"
1746533,2018-02-05 08:57:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540765"
1746533,2018-09-06 07:49:19 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/540765
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1746537,2020-05-13 21:38:51 UTC,"I'm having trouble replicating this. My process is to go to the Holdings View, select a number of holdings, and hit ""Edit Volumes."" Is it possible this is issue is no longer present, or are others able to confirm the bug?"
1746537,2020-05-14 11:37:32 UTC,It has been fixed. Batch apply is present in edit volumes again. It was fixed some time ago.
1746550,2018-02-01 15:36:08 UTC,"I've fixed that using the same ceph-auth-key for both cinder and nova ceph-user, that way, when nova tries to attach a volume using cinder-ceph-user and nova-libvirt-secret it will match and work."
1746550,2018-02-01 15:38:35 UTC,The best solution is to create a nova class or a generic libvirt-secret to store ceph key for both nova/cinder ceph-user and use that uuid in cinder::backend::rbd::rbd_secret_uuid
1746551,2018-02-05 18:28:26 UTC,Bug also reported here: https://bugs.freedesktop.org/show_bug.cgi?id=104953
1746551,2018-02-05 18:13:47 UTC,The problem occurs with the new mainline kernel (4.15.0-041500-generic #201802011154 SMP Thu Feb 1 11:55:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux). Here are the related dmesg lines:
1746551,2018-01-31 17:07:26 UTC,Does this bug go away if you boot back into the prior kernel version?
1746551,2018-02-01 08:09:03 UTC,"I tried to downgrade to an older kernel by removing the newest image, but unfortunately some modules failed to load and I then had only 640x480 resolution (fb). Re-installing the newer kernel image did not fix this. Any advice?"
1746551,2018-02-02 17:36:14 UTC,"I finally re-installed the system.
Because of another bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736017) I have to run 4.15 on this machine."
1746551,2018-01-31 17:00:06 UTC,This change was made by a bot.
1746555,2020-03-12 17:32:30 UTC,"I'm unable to replicate this issue in Inkscape 1.1-dev (12e2a09, 2020-02-19), Windows 10. Inkscape renders the file identically to the ""expected.png"" file."
1746558,2018-04-30 10:36:33 UTC,"Reviewed:  https://review.openstack.org/539590
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5fe3a01b604c29b0961d19b44a873cca78891381
Submitter: Zuul
Branch:    master"
1746558,2018-06-08 12:25:28 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1746558,2019-02-18 17:32:56 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/637594"
1746558,2019-03-13 21:03:25 UTC,"Reviewed:  https://review.openstack.org/637594
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b7237a9e6c9567f2f2b8753be1cdc274951a9451
Submitter: Zuul
Branch:    stable/queens"
1746558,2019-03-24 23:04:15 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1746561,2019-03-24 23:04:13 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1746561,2018-06-08 12:25:26 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1746561,2019-02-18 18:00:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/637599"
1746561,2018-04-30 10:36:51 UTC,"Reviewed:  https://review.openstack.org/539617
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fdea8b723ba5a25ea9dc0917401fbb1401e05ee3
Submitter: Zuul
Branch:    master"
1746561,2019-03-13 02:18:29 UTC,"Reviewed:  https://review.openstack.org/637599
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6933c880b8cea760c1e930b320b3d44b1e7e1b53
Submitter: Zuul
Branch:    stable/queens"
1746564,2019-10-08 09:19:07 UTC,"This was fixed at some point (I'm not sure at which release), on 2.41:"
1746566,2018-08-09 14:07:05 UTC,"I will test this on 3.0. If it backports cleanly there, it should backport cleanly to 3.1, since it is closer to master/3.2."
1746566,2018-08-09 14:15:43 UTC,I dropped the 3.0 series target from this one because there is a conflict with Open-ILS/web/js/ui/default/staff/services/grid.js when cherry-picking/merging.
1746566,2018-08-09 14:02:53 UTC,+1 from me on backporting if it merges cleanly.
1746566,2018-02-09 16:11:11 UTC,code branch for this feature is here:
1746566,2018-07-11 17:05:40 UTC,"Picked to master and targeted to 3.2-beta.  Thanks, Cesar and Galen!"
1746566,2018-03-27 18:59:46 UTC,The branch user/gmcharlt/lp1746566_row_limits contains a signoff of Cesar's patch plus a follow-up patch that adds the allowAll feature to the Items Checked Out and Other/Special Circulations patron grids.
1746566,2018-02-07 22:18:06 UTC,Equinox has been contracted by PaILS to create this option for the grids noted above.
1746566,2018-08-08 21:29:29 UTC,Requesting that this be backported to 3.1 and 3.0 if it does so cleanly
1746576,2018-01-31 20:20:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1746579,2018-03-04 18:20:29 UTC,It seems that this bug related to kvm qxl implementation. I've got the same behavior as you only once after rebooting from graphical.target.
1746579,2018-03-06 10:10:06 UTC,"Evgeniy, when you'll try, please, choose Ukrainian for localization and Ukrainian for keyboard layout during installation as I did it."
1746579,2018-03-06 06:47:53 UTC,"I'll try to experiment on several hosts, when I have free time. Maybe, at the weekend."
1746579,2018-03-05 22:34:23 UTC,Recently I've been installed 18.04 on my host system. A boxes in VM still is. So it is not because of Virtio/QXL/KVM.
1746579,2018-03-04 21:37:14 UTC,Take a look at the screenshot. It's your initrd.img. And I have no issues with it.
1746579,2018-03-04 21:33:07 UTC,initramfs with provided initrd.img
1746579,2018-03-04 18:37:20 UTC,Tried KVM with Virtio instead of QXL. The same issue.
1746579,2018-03-04 18:34:29 UTC,But in 16.04 which is also in KVM there is no such issue.
1746579,2018-03-04 18:28:25 UTC,Are you wanna say that Cyrillic not displaying correctly in VM's because of KVM QXL ?
1746579,2018-03-04 18:03:56 UTC,Here it is.
1746579,2018-03-04 18:28:17 UTC,Try VirtualBox instead KVM.
1746579,2018-03-04 17:10:08 UTC,"Please, see attachments."
1746579,2018-03-03 10:13:17 UTC,"I think you didn't get the framebuffer working. Please, reboot and show us the result of:"
1746579,2018-03-03 16:37:30 UTC,"$ locale
LANG=uk_UA.UTF-8
LANGUAGE=
LC_CTYPE=""uk_UA.UTF-8""
LC_NUMERIC=""uk_UA.UTF-8""
LC_TIME=""uk_UA.UTF-8""
LC_COLLATE=""uk_UA.UTF-8""
LC_MONETARY=""uk_UA.UTF-8""
LC_MESSAGES=""uk_UA.UTF-8""
LC_PAPER=""uk_UA.UTF-8""
LC_NAME=""uk_UA.UTF-8""
LC_ADDRESS=""uk_UA.UTF-8""
LC_TELEPHONE=""uk_UA.UTF-8""
LC_MEASUREMENT=""uk_UA.UTF-8""
LC_IDENTIFICATION=""uk_UA.UTF-8""
LC_ALL="
1746579,2018-03-03 16:41:17 UTC,"$ setupcon --current-tty
It changes the font, after which Cyrillic symbols become displaying normally. But it should display them normally with initial font too. Also this changes saves only till next reboot."
1746579,2018-03-04 10:57:49 UTC,I've installed Kubuntu under KVM and see no issues:
1746579,2018-03-04 13:30:33 UTC,">$ LANG=C apt policy keyboard-configuration
>keyboard-configuration:
>  Installed: 1.178ubuntu1
>  Candidate: 1.178ubuntu1
>  Version table:
> *** 1.178ubuntu1 500
>        500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
>        500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages
>        100 /var/lib/dpkg/status
I have the same already. But the boxes after booting in VM still is. And the framebuffer is OK too.
"
1746579,2018-03-04 17:36:12 UTC,"Ok, obviously /scripts/init-top/console_setup doesn't work. I'll try to setup up an Ukranian version. Please, share your current /boot/initrd.img"
1746579,2018-03-04 14:53:23 UTC,It will be difficult to cope with it remotely :)
1746579,2018-03-04 16:14:42 UTC,"You can add this line in the /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT=""break=init"""
1746579,2018-02-11 08:25:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746579,2018-03-04 13:43:32 UTC,$ cat /etc/default/console-setup
1746579,2018-03-04 15:15:58 UTC,"Recently I've reinstalled Kubuntu 18.04 too from daily image by 03.03.2018. While installation I've chose ukrainian locale. As a result - white boxes in VT's, the same as on previous installation.
Just a moment, I'l try to check what you've suggested."
1746579,2018-03-04 15:43:50 UTC,">Add the 'break=init' command to your kernel line and continue booting. You'll get the initramfs command line.
Can't get initramfs. Please, see the video:
"
1746582,2018-03-09 17:23:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746582,2018-03-09 17:26:27 UTC,If it helps I was trying to install vagrant when this happened. Output (of a second attempt) below:
1746582,2018-05-07 18:27:14 UTC,"Same with me. But already lvm2 (2.02.176-4.1ubuntu3)
I was trying to install vagrant."
1746582,2018-05-08 05:54:30 UTC,"After that any ""apt install"" and also ""apt upgrade"" happens with this error."
1746582,2018-05-08 15:19:31 UTC,I think I have found possible flow to reproduce the issue and workaround to fix it:
1746582,2018-05-11 08:25:57 UTC,"In my case this bug happened after upgrading from 17.10. Have an LVM partition on a secondary HDD that would no longer mount, and while trying to fix fstab started to get the error."
1746582,2018-06-13 18:49:18 UTC,"I have this same issue with Ubuntu Budgie 18.04 LTS, this worked so far, apt purge lvm2 then apt install lvm2. Now I can update and install."
1746582,2018-07-30 05:08:55 UTC,"I just encounter the same issue, in my case, i run the following commands to solve it temporarily:"
1746582,2018-08-31 03:51:03 UTC,Thanks.
1746582,2019-01-29 21:02:39 UTC,Thanks @Chengkinhung (chengkinhung)
1746582,2020-03-19 03:44:33 UTC,Thanks to Yevhen (yevhen.b) I fixed it by
1746582,2020-06-01 02:36:25 UTC,Thank you Yevhen (yevhen.b). It works.
1746582,2018-05-08 18:36:22 UTC,"In my case I have installed gnome-boxes before, lvm2 was installed as dependency. Then I removed gnome-boxes and made apt autoremove. I think after that the issue appeared for me."
1746585,2019-04-01 05:33:13 UTC,Please try uninstalling 'timidity' and all 'timidity' related packages. Then reboot.
1746585,2019-04-05 18:39:15 UTC,"Hi Daniel,"
1746585,2019-06-05 04:17:26 UTC,[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]
1746593,2018-02-02 12:13:39 UTC,"Hi Art,"
1746593,2018-02-12 02:40:10 UTC,"Hi. I found a fix on the ask fedora forum. It was necessary to issue the command
lpadmin -p HP_LaserJet_1018 -o usb-unidir-default=true (as root) and powercycle the printer."
1746593,2018-02-05 12:01:49 UTC,"The CUPS usb backend and the hp backend give two different, independent methods for enumerating a printer on the USB bus. Neither works for you but the printer is known to work. That implies there is a fundamental problem and you perhaps have a poorly USB bus."
1746593,2018-02-05 02:17:44 UTC,"Interesting idea.
I think this is because I had removed the old entry with hp-setup -r."
1746593,2018-02-02 18:03:19 UTC,"Hi Nishitha,
Thanks for the suggestion, I had not thought to wipe out the old printer queue."
1746593,2018-02-04 21:42:06 UTC,"Thanks for the response. Here are the outputs you requested ( I have interpreted a bit..). It appears that the normal OS commands find the printer but the hp software does not.
It is possible that there was an OS change between fedora 24, where the printer worked, and fedora26."
1746593,2018-02-04 15:23:03 UTC,"> Bus 002 Device 026: ID 03f0:4117 Hewlett-Packard LaserJet 1018
"
1746593,2018-02-03 00:33:19 UTC,"Additional information: lsusb returns
Bus 002 Device 012: ID 0cf3:3002 Qualcomm Atheros Communications AR3011 Bluetooth
Bus 002 Device 026: ID 03f0:4117 Hewlett-Packard LaserJet 1018
Bus 002 Device 009: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 002 Device 007: ID 04b4:8329 Cypress Semiconductor Corp. USB To keyboard/Mouse Converter"
1746593,2018-02-04 23:19:17 UTC,"hp-probe didn't work, which is not too surprising; hp-setup didn't either. More perturbing is that lpinfo doesn't show the device. There should be a line beginning ""direct usb://....""."
1746594,2018-02-23 12:33:04 UTC,"Also getting this in another branch now, with snap r360:
(release-18.01)andreas@nsnx:~/git/packages/landscape-client$ git push ahasenack release-18.01
Everything up-to-date
(release-18.01)andreas@nsnx:~/git/packages/landscape-client$ git st
On branch release-18.01
nothing to commit, working tree clean
(release-18.01)andreas@nsnx:~/git/packages/landscape-client$ git ubuntu lint
02/23/2018 09:31:34 - WARNING:Not linting a remote-tracking branch, assuming no namespace for branches and tags. Pass --lint-namespace if this is incorrect.
Traceback (most recent call last):
  File ""/snap/git-ubuntu/360/bin/git-ubuntu"", line 11, in <module>
    load_entry_point('gitubuntu==0.6.2', 'console_scripts', 'git-ubuntu')()
  File ""/snap/git-ubuntu/360/lib/python3.6/site-packages/gitubuntu/__main__.py"", line 243, in main
    sys.exit(args.func(args))
  File ""/snap/git-ubuntu/360/lib/python3.6/site-packages/gitubuntu/lint.py"", line 213, in cli_main
    verbose=args.verbose,
  File ""/snap/git-ubuntu/360/lib/python3.6/site-packages/gitubuntu/lint.py"", line 790, in do_lint
    pkg_remote_branch_string,
  File ""/snap/git-ubuntu/360/lib/python3.6/site-packages/gitubuntu/lint.py"", line 634, in do_change_lint
    repo.maybe_quiltify_tree_hash(commitish_string),
  File ""/snap/git-ubuntu/360/lib/python3.6/site-packages/gitubuntu/git_repository.py"", line 2360, in maybe_quiltify_tree_hash
    return self._maybe_quiltify_tree_hash(commit_hash)
  File ""/snap/git-ubuntu/360/lib/python3.6/site-packages/gitubuntu/git_repository.py"", line 2253, in _maybe_quiltify_tree_hash
    regenerated_pc_path,
  File ""/snap/git-ubuntu/360/usr/lib/python3.6/shutil.py"", line 309, in copytree
    names = os.listdir(src)
FileNotFoundError: [Errno 2] No such file or directory: '.pc'"
1746594,2018-02-23 13:26:45 UTC,"Also affects build-source, see bug 1751254 for details."
1746594,2018-03-19 06:12:36 UTC,"bug 1751254 was for ethtool.
BUt it seems to be a wider issue.
I wanted to reproduce something else, but hit it with hello today."
1746594,2019-09-29 04:03:34 UTC,"This looks like it was fixed, and is a dupe of lp #1801168"
1746594,2018-02-23 13:27:21 UTC,By breaking two functions now I marked it crit until triaged and understood at least.
1746596,2018-02-01 12:38:26 UTC,"I'd check the Interface page of the Preferences dialog to ensure there is a number >0, in the MRU maximum selector."
1746596,2019-05-28 05:52:31 UTC,"Hi, as this bug hasn't had any response for over 60 days and I haven't been able to reproduce this, this bug will be closed."
1746603,2018-04-17 13:19:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746603,2018-04-17 13:26:00 UTC,"Now recurs with every software upgrade (perhaps because it failed before).  Upgrade fails and times out.
Does not appear to affect system functioning - I have wireless printer but no network otherwise.
First happened within a week or so of 31 March 2018."
1746603,2018-04-25 10:59:05 UTC,happened today again with avahi update.
1746611,2019-09-20 15:45:34 UTC,"I think this bug has been fixed with the development in bug #1739292 which added the record summary area to the bib record display when merging records. The deleted indication is there as it is part of the record summary area.
We have the fix for #1739292 on our training server and I can confirmed the bright red deleted.
Release 3.2.8"
1746611,2020-01-28 13:43:12 UTC,"Confirmed that the fix for this is included in bug # 1739292, I'll mark it fix released to match. Thanks for pointing it out Janet!"
1746611,2019-03-14 16:38:41 UTC,Thank you! This one has been bugging me for a long time. :)
1746611,2018-11-29 17:45:05 UTC,"Okay, added tags again and included 'regression', forgot to save them the first time. :("
1746611,2018-07-23 20:11:49 UTC,One thing I like about merging records in the web client is that you can *select* records to merge while in the xul client it's merge *all* records. Being able to select is nice because you may have forgotten to remove merged records before adding new ones to a bucket.
1746611,2019-03-14 16:17:01 UTC,"I'll grab this one after bug #1776736 is merged, so I can build atop it / avoid merge conflicts."
1746611,2018-11-05 17:46:35 UTC,Also added tag cataloging and webstaffclient.
1746611,2018-11-05 17:45:19 UTC,I added tag regression as this behavior exists in the xul client and but is lost in the web client. Hopefully regressive behavior is addressed sooner.
1746613,2018-02-02 23:50:48 UTC,"This is not a bug with the software which upgrades a system from one release to another, rather its with the kernel."
1746613,2018-02-14 20:28:30 UTC,"4.15 is not yet in xenial-updates, so it is risky to test it in a production computer."
1746613,2018-02-14 10:33:24 UTC,Tested with 4.15.3-041503-generic and now hibernation works.
1746613,2018-02-06 16:05:46 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1746613,2018-02-04 05:26:31 UTC,apport information
1746613,2018-02-04 05:26:30 UTC,apport information
1746613,2018-02-04 05:26:29 UTC,apport information
1746613,2018-02-04 05:26:28 UTC,apport information
1746613,2018-02-04 05:26:27 UTC,apport information
1746613,2018-02-04 05:26:26 UTC,apport information
1746613,2018-02-04 05:26:25 UTC,apport information
1746613,2018-02-04 05:26:21 UTC,apport information
1746613,2018-02-04 05:26:20 UTC,apport information
1746613,2018-02-04 05:26:19 UTC,apport information
1746613,2018-02-04 05:26:18 UTC,apport information
1746613,2018-02-04 05:26:17 UTC,apport information
1746613,2018-02-04 05:26:16 UTC,apport information
1746613,2018-02-04 05:26:15 UTC,apport information
1746613,2018-02-03 00:00:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746613,2018-02-04 05:26:24 UTC,apport information
1746613,2018-02-04 05:26:23 UTC,apport information
1746614,2018-02-01 04:45:00 UTC,"Right there are several potential privilege barrier points, that a policy transition could work for"
1746614,2018-01-31 23:03:07 UTC,The usual steps are:
1746614,2018-01-31 23:20:13 UTC,"On 2018-01-31 05:56 PM, ChristianEhrhardt wrote:

> The hard part might be on which event to trigger the transition from one
> to another segment of a profile - but for now this is just about the
> feature request, not yet the implementation.
"
1746625,2018-05-04 12:15:03 UTC,"Please update to the latest bug fix 0.17 release.
There are a few minor enhancements in the mix, but this contains mostly fixes for bugs and crashes."
1746627,2018-03-07 14:28:10 UTC,We would need to add a new handler to listen to events and update the records.
1746627,2021-01-10 05:44:51 UTC,"I am not able to reproduce this bug on devstack master
(designate commit e8c901c32318a4f6bec7cb4f6d95fcc48c57ad73)"
1746627,2021-01-11 00:19:55 UTC,Sorry been a while since I reported this and memory fading but it looks like you're unsetting the PTR manually and not replicating the bug?
1746627,2021-01-14 15:18:05 UTC,"ok, I tried below (i.e. without unsetting)"
1746627,2021-01-15 00:52:33 UTC,"OK nice, so looks like this bug is fixed"
1746627,2021-01-18 07:34:36 UTC,"No, there is another bug I believe."
1746627,2021-01-19 15:44:18 UTC,"I have potential fix for problem mentioned in last comment, but its in neutron."
1746627,2021-01-20 05:15:26 UTC,Raised PR https://review.opendev.org/c/openstack/neutron/+/771556
1746627,2021-01-23 09:28:42 UTC,"As I mentioned in the patch, combining neutron dns-integration with the designate PTR functionality is not supported, so if this is the issue, the bug is invalid. I actually think that we should deprecate and drop the designate support for that in order to avoid such conflicts."
1746629,2020-10-27 14:32:48 UTC,"Thanks for the review Christian. I've slightly updated the description now, libaacs0 is needed to access protected discs so non crypted ones should be fine even without it installed. I don't have a drive on any of my machines to try if some of the datas are correctly fetched without the library on protected disks though"
1746629,2020-10-26 07:41:17 UTC,"[Summary]
This looks ok from a MIR POV and you have my Ack IF you can outline a reasonable
use case that benefits from libbluray WITHOUT also promoting libaacs0.
Please do to in a comment on this bug."
1746629,2019-08-20 12:48:58 UTC,I will review this now; but I expect it might need security review as well.
1746629,2019-05-28 13:50:25 UTC,"didrocks asked if this was still relevant, and the answer is yes, it's not a high priority for us but it would still let a bit of delta (in a debian/rules file, in Debian, so not an ""Ubuntu"" delta but a feature delta), so reviewing would be good"
1746629,2018-04-03 12:46:00 UTC,"the package ftbfs. see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893227"
1746629,2018-06-07 18:08:08 UTC,"it's not just building the package with OpenJDK-8, it can't run with OpenJDK-10/11.  So better disable the java parts for now?"
1746629,2018-04-03 14:18:52 UTC,"Matthias, thanks for you comment. My originally request is specifically that we *not* include the Java packages in main to keep things simple. So that issue shouldn't affect us since openjdk-8 is still in universe so is ok for a Build-Depends."
1746629,2018-04-03 12:47:15 UTC,libbluray (1:1.0.2-3) unstable; urgency=medium
1746629,2018-03-28 10:46:38 UTC,desktop-packages has been subscribed to it now
1746629,2018-03-26 15:23:09 UTC,libbluray is missing a bug subscriber.
1746629,2019-05-16 18:51:43 UTC,The issue with OpenJDK 11 was fixed.
1746634,2018-02-15 23:53:18 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1746634,2018-02-01 01:09:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539755"
1746634,2018-02-09 07:13:28 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1746634,2018-02-05 22:12:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/541036"
1746634,2018-02-13 17:32:10 UTC,"Reviewed:  https://review.openstack.org/541036
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6d1877bf1da098b3be17fbd2dd5e53eecd2f048c
Submitter: Zuul
Branch:    stable/pike"
1746637,2018-02-01 20:40:37 UTC,Which release of nova are you using?
1746637,2018-02-02 00:54:16 UTC,Ocata and Queens，two release of nova all have this problem.
1746638,2018-05-02 21:37:19 UTC,"This bug has been affecting me since around 2012 or so, when I was using Arch linux (still installed btw). Same graphics chip as OP's. Upgraded ubuntu MATE to 18.04 a week ago, and today the freeze happened again. This time, I intentionally wanted to test if it was fixed, and found out that it still was not. It is random as OP said, but easily reproducible by launching any application involving accelerated 3D. So today I wanted to turn on the 3D spectrum in VLC, and the screen became garbage like on the pic below :"
1746638,2018-03-27 16:08:05 UTC,"Christopher M. Penalver,"
1746638,2018-04-28 16:52:01 UTC,"Christopher M. Penalver,"
1746638,2018-04-28 20:34:51 UTC,Diogo Gomes:
1746638,2018-04-28 20:53:33 UTC,"Christopher M. Penalver,"
1746638,2018-04-29 02:26:58 UTC,This log contains the mentioned error:
1746638,2018-04-29 02:31:21 UTC,Updates of same issue for Ubuntu 18.04:
1746638,2018-05-02 21:40:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746638,2018-11-18 07:29:46 UTC,Same problem on LinuxMint TARA fresh install.
1746638,2018-06-20 18:58:54 UTC,"I can confirm I'm having the same problem. This problem arised to me since Debian Jessie. The workaround was to install Nvidia proprietary drivers, but support for nvidia-304xx was dropped on Xorg 1.20.
Adding ""NvMSI=0 NvPCIE=0"" to kernel boot line seems to make crashes less predictable.
The only workaround is to boot with ""nouveau.noaccel=1"" but this make any graphical application unusably slow.
Back to Windows."
1746638,2018-06-21 10:54:03 UTC,"I'm not switching back to Windows, so any possible fix is welcome to test on my machine!
Any devs around?"
1746638,2018-02-14 16:44:42 UTC,"Christopher M. Penalver,"
1746638,2018-11-23 16:15:10 UTC,"Same problem for me with Lubuntu 18.04 System freezes at random times. Screen is then completely filled with non-sens signs. Graphic card is NVIDIA GeForce 6150SE nForce 430. Driver is Nouveau.
Thanks beforehand for your help."
1746638,2019-03-06 01:50:26 UTC,This has been happening to me for 3-4 years.  I'm nearly ready to trash the AMD Athlon.... Please Please fix this...
1746638,2020-09-17 00:02:12 UTC,"This happens to me too. Note: when X is NOT running, the kernel still locks up. This appears to be a kernel driver issue and not an X issue."
1746638,2020-10-14 14:07:32 UTC,I don't use any flavor of Ubuntu anymore and do not have this hardware to test.
1746638,2018-05-04 19:59:06 UTC,"Here is my lspci output, please tell me what else I can attach."
1746638,2018-02-03 04:22:48 UTC,"I had a full copy of kern.log, I attached it."
1746638,2020-10-15 01:40:44 UTC,"OK ""Won't Fix"" because the original reporter can no longer contribute to the bug. If anyone else still experiences similar problems then please open new bugs."
1746638,2018-02-01 20:51:38 UTC,"Diogo Gomes:

>""I add the last 10min of kern.log before crash happen. Please tell me if is useful.""
"
1746638,2018-02-01 01:58:15 UTC,"Diogo Gomes, thank you for reporting this and helping make Ubuntu better."
1746638,2018-02-01 21:01:25 UTC,"Diogo Gomes:

>""Al information is complete for the 16.04 LTS""
"
1746638,2018-02-01 02:23:23 UTC,"1) I have this files in /var/crash but I think that is not related:
_usr_bin_gnome-disks.1000.crash     _usr_bin_gnucash.1000.uploaded  _usr_bin_nautilus.1000.upload
_usr_bin_gnome-disks.1000.upload    _usr_bin_lutris.1000.crash      _usr_bin_nautilus.1000.uploaded
_usr_bin_gnome-disks.1000.uploaded  _usr_bin_lutris.1000.upload     _usr_lib_xdg-desktop-portal_xdg-desktop-portal.0.crash
_usr_bin_gnucash.1000.crash         _usr_bin_lutris.1000.uploaded   _usr_lib_xdg-desktop-portal_xdg-desktop-portal.0.upload
_usr_bin_gnucash.1000.upload        _usr_bin_nautilus.1000.crash"
1746638,2018-02-01 02:32:13 UTC,"Christopher, I changed to new because I answered to your questions, please tell me if you need something more to be completed."
1746638,2018-02-01 02:49:40 UTC,">""3) Can you explain what log do you need?""
"
1746638,2018-02-01 03:13:14 UTC,"dmesg is empty, xorg logs are already uploaded."
1746638,2018-02-01 03:21:45 UTC,"Diogo Gomes, to advise, you would need to reproduce the freeze/crash then upload the logs. Just uploading logs without this is useless."
1746638,2018-02-01 03:52:22 UTC,"These are the logs, when the system crashes, I can't use the system. These are the logs after reboot after the crash."
1746638,2018-02-01 04:03:45 UTC,Diogo Gomes:
1746638,2018-02-01 05:34:23 UTC,"Christopher M. Penalver,"
1746638,2018-02-01 05:37:17 UTC,"Sorry, launchpad do not update and I didn't see my and your message (it's why it's duplicated)."
1746638,2018-02-01 05:48:10 UTC,I found the older kern.log with the error:
1746638,2018-02-01 16:15:18 UTC,"Diogo Gomes, please stop changing the Description, adding packages to this report, subscribing me to bugs when I didn't ask, etc."
1746638,2018-02-01 16:28:47 UTC,Sorry but I change and add because is the same bug that I have since 2016. Maybe I need to wait 2 more years or change distro...
1746638,2018-02-01 16:43:43 UTC,"Diogo Gomes, to advise, nobody has enough information to debug or root cause any of the reports at this point because all the logs on all reports don't include useful information. However, developers who know what is a duplicate of what submit patches to fix the issue."
1746638,2018-02-01 16:59:22 UTC,"Once again, it's impossible capture before reboot. The system crashes tottally."
1746638,2018-02-01 17:16:25 UTC,"Diogo Gomes:

>""I tested in live and crashes and do not stored any logs, it's the reason why I didn't upload.""
"
1746638,2018-02-01 20:33:10 UTC,I add the last 10min of kern.log before crash happen.
1746638,2018-02-01 20:48:04 UTC,"I upload a possible ""screenshot"" of the crash."
1746643,2018-08-20 18:31:39 UTC,This issue was fixed in the openstack/zun 1.0.1 release.
1746643,2018-07-30 15:55:09 UTC,This issue was fixed in the openstack/zun 2.0.0 release.
1746643,2018-02-10 03:52:06 UTC,"Reviewed:  https://review.openstack.org/542604
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=36434135152ab9dea0be088888dd20c7e0d94e4a
Submitter: Zuul
Branch:    master"
1746643,2018-02-10 18:07:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/543134"
1746643,2018-02-13 02:21:11 UTC,"Reviewed:  https://review.openstack.org/543134
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=376939c492f55bd2a77263ded43a05cba934d861
Submitter: Zuul
Branch:    stable/queens"
1746643,2018-02-09 05:55:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/542604"
1746647,2018-02-01 03:47:57 UTC,Need to get juju-check merged before fixing this.
1746647,2018-02-01 03:57:13 UTC,"Actually, this seems to happen on any 1.25 model."
1746650,2018-02-13 15:21:48 UTC,I think this is going to be specific to trusty deployments
1746650,2018-02-13 15:50:50 UTC,Reproduce:
1746650,2019-11-29 15:28:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/696721"
1746650,2019-12-02 15:42:50 UTC,"Reviewed:  https://review.opendev.org/696721
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=db8ba4d9381b3098cff95d805232eadf37f99760
Submitter: Zuul
Branch:    master"
1746651,2019-05-13 14:15:51 UTC,"This bug has been hanging on for a while without further activity, and the is_bootstrapped routine has been updated since the bug was filed. Marking this as Low, and I think the best plan is to set aside some time to verify that the issue no longer affects us, and close."
1746652,2018-02-04 15:17:11 UTC,"In reference to number 2 above. I went back and reread the help manual. I now see that when selecting Save As from the File menu, Templates shows up as one of my places (I use Thunar file manager and it shows on the left). When selected, it appears to save the file in /usr/share/inkscape/templates/ folder. Again, this was not super obvious because my eyes don't always look at the places option when saving a file. I compared some other software packages to see how they handle this:"
1746652,2018-02-01 15:08:30 UTC,Thank you for the response. I think that blog entry is out of date.
1746652,2018-02-01 12:35:12 UTC,"Hi,
The default.svg file opens each time Inkscape opens a new document. Users can save a custom version with settings for size, units and more."
1746652,2018-02-01 04:24:33 UTC,"I know the properties can be changed in the document properties box, but there is no way to change which properties are the default at program launch."
1746652,2018-02-02 00:39:51 UTC,I attempted to create a new document to save as a template with my preferred settings. I cannot overwrite the default.svg file without changing permissions on the /usr/share/inkscape/templates/ folder. This means that I cannot create and save any template and have it stored in the templates folder without changing permissions of that folder.
1746656,2018-02-01 05:01:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746656,2020-05-25 02:16:35 UTC,If this bug affects you then please report it upstream to Xwayland at:
1746656,2020-11-09 02:19:55 UTC,It looks like any call to wl_log will hit the same bucket:
1746658,2018-02-02 12:42:37 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1746658,2018-03-21 04:43:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746669,2018-02-01 06:58:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539834"
1746669,2018-07-27 16:26:43 UTC,This issue was fixed in the openstack/python-heatclient 1.16.1 release.
1746674,2018-04-20 13:13:33 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1746674,2018-04-02 13:18:32 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1746674,2018-04-02 13:09:01 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1746674,2018-03-30 02:34:59 UTC,"Reviewed:  https://review.openstack.org/557622
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=461e42dcc4831083c46f4ff9763807862aab9b4a
Submitter: Zuul
Branch:    stable/pike"
1746674,2018-03-29 15:56:07 UTC,"Reviewed:  https://review.openstack.org/557621
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2dc4d7a366efe11acb1099eca13bd3f3c2af9012
Submitter: Zuul
Branch:    stable/queens"
1746674,2018-03-29 06:48:16 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/557621"
1746674,2018-03-29 06:50:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/557622"
1746674,2018-02-01 08:50:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/539865"
1746674,2018-02-01 10:13:57 UTC,"> This causes errors when deploying VMs with multi numa nodes with `cpu_thread_policy=isolate`.
"
1746674,2018-02-08 02:21:24 UTC,"@stephen
I updated the Bug Description adding the traceback"
1746674,2018-03-27 16:27:13 UTC,"Reviewed:  https://review.openstack.org/539865
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=24d9e06ec68dfd0ead9bc56ad186e7b4e0acd8fb
Submitter: Zuul
Branch:    master"
1746674,2018-02-01 11:55:45 UTC,"> Any chance we could get a sample traceback?
"
1746681,2018-02-15 13:23:31 UTC,The parameter scope is not handled by the workbooks API so we can ignore it for this bug
1746681,2018-04-20 16:14:04 UTC,This issue was fixed in the openstack/python-mistralclient 3.4.0 release.
1746684,2018-02-02 12:42:28 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1746685,2018-02-01 20:17:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540122"
1746685,2019-08-17 02:42:08 UTC,"Reviewed:  https://review.opendev.org/540122
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=cb308119160d5af7db9b65a7ab2225bb07edb614
Submitter: Zuul
Branch:    master"
1746685,2019-08-21 22:16:01 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/677848"
1746685,2019-08-22 05:18:33 UTC,"Reviewed:  https://review.opendev.org/677848
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=6204a2bc571a51e91f97ad4342b8ae216aaf6f36
Submitter: Zuul
Branch:    feature/losf"
1746685,2019-10-03 16:34:57 UTC,This issue was fixed in the openstack/swift 2.23.0 release.
1746685,2018-02-01 20:03:23 UTC,"I'm inclined to set SLO's bulk-deleter's max_deletes_per_request to a big number. Not equal to SLO's max_manifest_segments, but something big enough that, even if your current max_manifest_segments is less than its historic high, your users can still delete any SLO manifest that they have."
1746686,2018-02-11 08:48:07 UTC,"I met this error too. Even with [blue, red] --> [red] --> [red, blue] but the result still [blue, red]"
1746698,2019-06-11 22:57:56 UTC,"> dbus[25970]: Unable to set up transient service directory: XDG_RUNTIME_DIR ""/run/user/114"" not available: No such file or directory
"
1746698,2019-06-11 23:05:37 UTC,"This looks to me more like an ordinary test timeout. The test starts 5 threads each performing 100 D-Bus method calls, and waits for 500 method calls or 5 minutes, whichever happens soonest; and in the log quoted, it took slightly more than 5 minutes to fail. Perhaps this timeout is just set too short?"
1746701,2018-03-24 15:19:39 UTC,Same here on Ubuntu Bionic with kwin-x11=4:5.12.3-0ubuntu2.
1746701,2018-03-24 15:18:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746702,2018-02-01 12:25:05 UTC,"The attachment ""implemented delete-all"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1746702,2018-02-09 19:27:30 UTC,Setting back to In Progress per http://wiki.ubuntu.com/Bugs/Status
1746702,2018-03-07 06:06:50 UTC,Unsubscribing the sponsors team as mvo should really review and bake this into upstream.
1746702,2018-03-12 08:42:26 UTC,There was a mistake in the previous version of the patch overriding delete-older-than instead of creating new command delete-all.
1746710,2018-04-26 13:48:15 UTC,"I hope that the fix in https://github.com/ubuntu/snapcraft-desktop-helpers/pull/103 will land soon, this is totally not acceptable in an LTS release."
1746710,2018-05-01 11:15:11 UTC,Just to clarify the situation: here https://github.com/ubuntu/snapcraft-desktop-helpers/issues/92#issuecomment-385644966 one of the desktop helper maintainers says that to solve the problem snaps must be rebuilt using the latest desktop helper. This because snapcraft-desktop-helpers is a build tool and so the fix can't be propagated to existing snaps.
1746710,2018-05-08 13:12:53 UTC,"Aren't the packages hosted more or less centrally? Isn't it possible to rebuild most snaps automatically? This is a serious usability issue appearing on an LTS, after all. Snaps are heavily promoted in the Ubuntu 18.04 Software Center. This should not be ignored, at least for default or promoted apps."
1746710,2018-05-10 00:11:46 UTC,"Still happening in 18.04. Since I have the Spanish version, it leads to multiple redundant directories, but with different names like ""Documents"" and ""Documentos"", ""Descargas"" and ""Downloads"", etc. Is a really annoying issue."
1746710,2018-05-10 12:23:06 UTC,I discovered when the problem happens. When we open a snap program and access the files.
1746710,2018-05-11 08:10:32 UTC,"The solution is to contact the snap maintainer, for example for VLC https://snapcraft.io/vlc -> Contact Jean-Baptiste Kempf (VLC)."
1746710,2018-05-11 19:09:44 UTC,It's a little bit funny that snap team couldn't
1746710,2018-08-09 13:32:11 UTC,Same problem.
1746710,2018-06-18 19:18:56 UTC,I have the same problem.
1746710,2018-04-26 09:12:36 UTC,"This bug will likely be a larger problem in 18.04. Some of the default applications of a standard Ubuntu installation seem to be snap packages. Some of them, like gnome-logs and gnome-characters, reveal the bug. It is quite annoying indeed."
1746710,2018-08-16 14:44:16 UTC,I added snapd again as portals should solve this
1746710,2018-08-21 06:10:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746710,2018-08-21 08:51:33 UTC,"Sergio, see comment from Seb above. It's the launcher, and rebuilding apparently solves the problem. We won't pack the launcher in snapd."
1746710,2020-02-21 12:08:16 UTC,"This was a bug on the launcher which lived outside of Snapcraft.
That said, future bugs occurring with the gnome extension, introduced in Snapcraft 3.8, would indeed be Snapcraft (the tool) bugs."
1746710,2018-05-13 22:12:40 UTC,This problem occurs with all the snap packages I've opened. This occurs only when the program is first opened and the event does not repeat itself again when I reopen the program.
1746710,2018-04-25 13:07:35 UTC,is snapcraft a better target then?
1746710,2018-04-29 17:28:49 UTC,"This problem persist on ubuntu 18.04
I am using portuguese Brazil translate for my system"
1746710,2018-04-09 16:14:41 UTC,That's a problem in the desktop launcher and https://github.com/ubuntu/snapcraft-desktop-helpers/pull/103 should resolve the issue
1746710,2018-02-01 22:14:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746710,2018-02-01 22:19:40 UTC,"Same bug on Spanish language, 16.04, 4.13.0-32-generic, unity."
1746710,2018-02-03 16:30:33 UTC,"Same here on Ubuntu 17.10 (Gnome) with snap package of Spotify. Once I start Spotify I have all default home folders duplicated (one directory named in English, one named in Italian)."
1746710,2018-04-25 09:10:29 UTC,Marked as invalid for snapd (it's not a snapd bug)
1746710,2018-02-11 14:21:52 UTC,"Also confirmed in Ubuntu 16.04.3 LTS 4.13.0-32-generic #35~16.04.1-Ubuntu SMP, (it-IT language)."
1746710,2018-02-12 15:42:57 UTC,Could somebody post about that on https://forum.snapcraft.io ?
1746710,2018-02-13 07:53:06 UTC,Happened already: https://forum.snapcraft.io/t/snap-does-not-respect-directory-settings/3274
1746710,2018-02-14 15:52:25 UTC,"this bug makes using snaps ""ugly"" on non-default locales, bumping the severity due to that"
1746710,2018-02-15 06:05:04 UTC,"fwiw, flatpak doesn't suffer from this"
1746710,2018-02-03 20:42:18 UTC,Also happens in snaps on elementary  https://www.reddit.com/r/elementaryos/comments/7u4349/double_home_dir_folders/?st=jd7tqi3y&sh=ec62efa6
1746710,2018-02-16 20:54:30 UTC,Stil no resolution? It's annoying!
1746710,2018-02-23 15:28:01 UTC,I can confirm this on elementary OS 0.4 Loki (based on Ubuntu 16.04)
1746710,2018-03-16 17:17:08 UTC,"Testing Xubuntu 18.04, this happens as well.
Linux Xubuntu-18-04 4.15.0-12-generic #13-Ubuntu SMP Thu Mar 8 06:24:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1746710,2018-03-26 13:09:46 UTC,"Still there on a fully updated Ubuntu 18.04 install (italian language), definitely a very annoying bug."
1746710,2018-04-09 11:52:08 UTC,Can someone affected list the set of snaps that they have that may be causing this? We can track this down to the specific snap and then figure out what is causing the issue.
1746710,2018-04-09 11:52:35 UTC,"Ah, I see mailspring is enough to reproduce this."
1746710,2018-02-15 21:41:13 UTC,I can confirm this on
1746710,2018-04-09 12:15:40 UTC,Also affects Ubuntu 18.04 beta.
1746716,2019-03-14 10:57:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746716,2019-03-14 10:58:43 UTC,Fixed upstream: https://github.com/tinyproxy/tinyproxy/issues/136
1746716,2019-03-14 11:19:16 UTC,"Please, note that it is possible to install cosmic package onto bionic. Updating the version for bionic is stressless."
1746725,2019-09-05 14:49:56 UTC,The OS bug doesn't exist in Ubuntu Bionic which is what we use for gate so while it would be nice to have https://review.openstack.org/#/c/476239/ we don't need it for our test infrastructure.
1746725,2019-03-22 14:59:51 UTC,Hey Rodrigo is this issue still occurring?
1746725,2019-03-22 15:09:53 UTC,"Hi Jason,"
1746725,2019-03-24 16:46:34 UTC,Thanks Rodrigo...Are there any plans to see if https://review.openstack.org/#/c/476239/  can be merged?  Is this a wishlist item or something can remain on as a backlog item for manila?
1746726,2018-02-01 22:00:39 UTC,Does not need to go to the security pocket.
1746726,2018-02-06 20:09:50 UTC,This bug was fixed in the package linux-azure - 4.13.0-1009.12
1746726,2018-02-06 21:01:34 UTC,The package has been published and the bug is being set to Fix Released
1746728,2018-08-08 12:30:26 UTC,"It was not fixed in Debian, the correct status is ""Won't Fix""."
1746728,2018-03-27 17:14:53 UTC,Done.
1746728,2018-03-10 23:53:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746728,2018-03-10 23:56:58 UTC,"Confirmed - after I uninstall VLC via (Gnome) software, usr/bin still contains files called ""vlc"" & ""vlc-wrapper""."
1746728,2018-02-01 17:20:11 UTC,"No, really not a vlc bug."
1746728,2018-03-27 15:53:53 UTC,"According to the specifications, the binary should be included in the same package as the .desktop and the AppStream metadata."
1746738,2020-07-06 21:08:55 UTC,"Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1746738,2020-09-05 04:17:25 UTC,[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.]
1746747,2018-03-06 20:24:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550238"
1746747,2018-03-07 14:59:38 UTC,Going to have to abandon this one; virtually all of the changes from comments in reviews 531479/539254 cause assertion errors in the various tests. May revisit in future but will leave unassigned for now.
1746747,2018-03-07 15:00:13 UTC,"Change abandoned by Russell Tweed (<email address hidden>) on branch: master
Review: https://review.openstack.org/550238"
1746752,2018-02-01 17:33:54 UTC,"Oh, I'm afraid this is just a duplicate of the annoying #1731294"
1746759,2018-06-07 18:51:42 UTC,"""Package runs unit tests for py2/3 as part of package build."""
1746759,2018-09-25 13:43:28 UTC,"This would be openstack-team - per discussion with james page:
[15:41] <cpaelzer> hi 1746759 should get a look by you
[15:41] <cpaelzer> it was denied and directed to us
[15:41] <cpaelzer> but it really is openstack
[15:42] <jamespage> it is - the feedback is fixed."
1746759,2018-09-25 13:44:20 UTC,Python 3 packages have now been enabled as part of this package.  Unit tests run against default py2/py3 versions.
1746759,2018-10-09 13:15:33 UTC,"This should be ready for re-review, since Doko probably did quite a bit of it in the past we want to avoid re-doing the same and assigned the review to him in the MIR team meeting."
1746762,2018-03-03 11:42:26 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0rc1 release candidate.
1746762,2018-02-13 23:58:32 UTC,"Reviewed:  https://review.openstack.org/540164
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=2adb2b6f57e031b70cb49cf3586fb204e6919d33
Submitter: Zuul
Branch:    master"
1746762,2018-02-01 21:30:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540146"
1746762,2018-02-08 07:49:19 UTC,"Reviewed:  https://review.openstack.org/540146
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=92c7d6880b95938cb6a47ff7a4a339aab61bf255
Submitter: Zuul
Branch:    master"
1746762,2018-02-01 22:14:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540164"
1746762,2018-02-12 22:18:59 UTC,"Reviewed:  https://review.openstack.org/540127
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=094e594d4009b79668b214c0c176eb5b01ce211c
Submitter: Zuul
Branch:    master"
1746762,2018-02-01 20:31:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540127"
1746765,2018-02-02 15:24:56 UTC,"It also FTBFS with the current gnu-efi, so my suggestion is to just disable the EFI integration on arm64."
1746765,2018-02-02 15:25:53 UTC,"At least for now, so we don't block stuff."
1746765,2018-02-02 23:26:41 UTC,"With new gnu-efi, the invalid relocation appears to be in side the gnu-efi crt object code. It seems to me that possibly fixes in either toolchain or gnu-efi, may resolve systemd build failure."
1746765,2018-02-06 09:41:51 UTC,this is now fixed in binutils
1746766,2018-12-03 20:05:35 UTC,"After Jeff Godin asked about this bug in IRC today (), I decided to remove its duplicate status with bug bug 1766716. While that other bug does rectify this behavior, it does so only in Evergreen 3.2 and later releases. This issue is still open in Evergreen 3.1."
1746766,2018-11-15 22:17:20 UTC,"Marked as duplicate, as it is fixed in the Rewrite."
1746766,2018-06-01 13:12:12 UTC,"Jane, I think you're right. The Emergency Closing branch includes a new AngularJS app for managing Closed Dates, which seems to sort by closed date. I'm just reading the code, so I haven't tested anything."
1746766,2018-06-01 20:39:05 UTC,I can confirm that the rewrite of Closed Dates Editor (as part of Emergency Closing Handler) now shows closings in date order.  That code is currently targeted for the 3.2 release.
1746766,2018-05-31 18:54:02 UTC,Confirming that this is still an issue in 3.1 and that I can't see any significance to the order either.
1746766,2018-05-31 21:02:06 UTC,Just a note that I think this is fixed by the new emergency closing feature?  https://bugs.launchpad.net/evergreen/+bug/1766716
1746773,2018-02-19 03:33:13 UTC,"This is due to a change in GNOME 3.22 which started ordering search results by ""match value"" (essentially a value indicating how well the result matches the search terms). This is generated by a bitfield of metadata items that matched the search terms. Snap doesn't provide this, so the snap results were getting ordered by the fallback sorting field - the app id."
1746773,2018-02-01 22:31:02 UTC,Confirmed that snapd is returning skype before spreedme so must be some re-ordering going on in GNOME Software...
1746773,2018-02-19 03:36:19 UTC,"Actually, I misread the code - the match value is between 0 - 100, but I'm still investigating how it's generated."
1746774,2018-02-07 13:24:15 UTC,"Oops, closed the wrong bug."
1746774,2019-10-07 00:54:15 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1746774,2019-10-07 12:04:27 UTC,Tests look to be passing now with 4.15 kernels.
1746774,2018-02-07 13:23:44 UTC,"The failures here are no longer happening, so closing. Current test failures reported on bug 1746774."
1746781,2018-02-01 18:11:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540075"
1746781,2020-03-04 09:18:08 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.opendev.org/540075"
1746783,2018-02-02 17:08:04 UTC,Thank you Brin for your suggestion but I think the command did not work for me or maybe I did not do it well.
1746783,2018-02-02 19:22:59 UTC,"My major problem is how to create physical and logical volumes for my LVM partition which in this case is /dev/sda5. When I use pvcreate and vgcreate with /dev/sda5, it always says the partition is in use despite deleting and creating another one. I think this is why I am getting the error 'Can't open /dev/sda5 exclusively.  Mounted filesystem?' Do you guys know how to handle this?"
1746783,2018-02-01 21:04:37 UTC,I want to add that I have separate nodes for compute and storage.The storage node has only one disk only have a disk as shown below:
1746783,2018-02-01 20:05:37 UTC,"Thank you Sean for the quick response. I saw the error 'Class LVMISCSIDriver cannot be found' in the log file  before I created the trouble ticket but when I changed it to 'LVMVolumeDriver' as stated in the installation guide, cinder-volume status is showing 'Down' on my controller node."
1746783,2018-02-01 18:55:49 UTC,Looks like you may have a configuration error:
1746783,2018-02-02 09:07:48 UTC,"Do not know your real environment configuration, try to configure your lvm.conf file open try to add sda5 global_filter inside? as in the following example:"
1746787,2018-02-01 18:56:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540090"
1746787,2018-02-02 21:36:09 UTC,"Hi Joe, thanks for reporting. Could you clarify what is expected and what went wrong here?"
1746787,2018-02-06 13:55:19 UTC,"Change abandoned by Joe Talerico (<email address hidden>) on branch: master
Review: https://review.openstack.org/540090"
1746788,2018-02-01 19:18:55 UTC,"Approving this RFE, as it falls under driver feature parity category."
1746800,2018-02-02 15:49:30 UTC,"In my mind, when you limit by copy location, you're trying to find materials that have had that copy location applied to it. If the record has no copies, then the copy location has not been applied. I would support removing empty records from copy location limited searches."
1746800,2019-08-23 22:20:54 UTC,"Limiting a search down to a specific shelving location should not return empty records. While I try to keep these cleaned up, there are always bibs waiting for items, and it is confusing to staff and patrons. Our current Evergreen version is 3.1.11"
1746800,2018-02-02 16:55:07 UTC,"I don't see catalogers filtering by copy location very often when looking for an existing record to attach holdings, so I don't see removing empty records from those results to hamper cataloging workflow. Perhaps if they thought the title was already in their holdings, but I don't think they would expect to retrieve an empty record in that case."
1746800,2018-02-02 15:11:51 UTC,"I haven't heard of staff confusion in years -- at least, I haven't seen helpdesk tickets or had questions sent to me about them in a very long time. I think staff in PINES are aware enough of the empty records that they know what they are. To me, it is a matter of staff education that would be assisted by having that color cue back."
1746800,2018-02-02 14:53:27 UTC,"Elaine, do you know if it's common in PINES to limit searches to a specific shelving location while expecting to see these records? That seems to be the only time we hear of staff confusion and hiding empty records when searching at a copy location would be a smaller change than trying to add an option to enable / disable empty records in searches altogether."
1746800,2018-02-02 14:17:27 UTC,"As long as it is an option. PINES catalogers depend on being able to find records with no holdings attached in a staff client search. At one time, there was a color cue (the record was highlighted in gray in the retrieved search list) for those records so that staff could easily tell what they were, lessening confusion for circ staff. We would like that color coding back."
1746800,2018-02-02 13:52:11 UTC,"If this is a public search, I believe this could be similar to bug 1745233. We're still seeing issues with copy location searching here."
1746800,2018-02-02 13:50:01 UTC,Sorry - Should never have made it launch pad so it seems. Am I mis-remembering or was there talk in the past to add an option to exclude non-transcending bibs with no holdings from results in the staff client?
1746800,2018-02-02 13:16:24 UTC,Provided it is the staff client and not the public....
1746800,2018-02-01 20:49:04 UTC,"Unless I'm misunderstanding you, this is exactly as expected -- they're entirely empty records, so they're supposed to show up in staff searches.  Otherwise, staff would not be able to find them to catalog items or add LURIs.  Am I missing something?"
1746800,2018-02-02 13:15:32 UTC,That is expected behavior for the reasons you state. It is a feature and not a bug.
1746804,2018-02-01 21:00:24 UTC,"While some implementations seem color specification in the way your file uses, it's not valid according to SVG specification:
  https://www.w3.org/TR/SVG11/types.html#DataTypeColor"
1746804,2018-02-01 21:47:07 UTC,"Thanks for the follow up. I was reading that, and it wasn't clear to me if alpha is supported or not. They say the range of values accepted is consistent with a 32bit signed integer. Nowhere in the document is mentioned alpha or opacity."
1746804,2019-05-13 01:36:12 UTC,"It's not exactly the most clear, but in the technical definition of 'color' it states that there must only be 3 or 6 hex digits, which means it is not for defining alpha. As a result, closing this bug."
1746808,2018-02-01 21:07:46 UTC,The current setup we have is using dir type and this is more generic so it would work for everyone. We can change it to use disk and point to the right dev.
1746808,2019-07-03 17:17:38 UTC,we use bcache now.
1746809,2018-05-15 12:11:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746810,2018-02-20 21:25:18 UTC,I'm turning this bug report into a feature request for a middle ground between all-interchangeable and none-interchangeable.
1746810,2018-02-02 20:03:13 UTC,The software updates them because you (or whoever created the symbol) said the units were interchangeable.
1746810,2018-02-02 19:38:52 UTC,The problem is that I don't want to reset existing annotation. This is how I got this. I had older project that I did modifications to and after annotation I saw weird changes. But if it where only similar units not power unit I wouldn't notice. Perhaps its not terribly bad because schematic would work anyway or I would see this during layout.
1746810,2018-02-02 18:25:17 UTC,"I opened this in a recent build so it re-mapped the symbols, but the bug still reproduces."
1746810,2018-02-02 19:01:53 UTC,"Be sure we need some sort of ""third way"" to handle parts that have some units interchangeable and some not."
1746810,2018-02-02 18:53:48 UTC,Oh I see now. I would argue that none of them are interchangeable once you set them in schematic. Often I choose units based on pinout so output of one opamp is near other in quad package. Also as you state power units will make this a problem.
1746810,2018-02-02 18:36:44 UTC,"It reorders them because the Opamp_Quad_Generic-Device has the all-units-are-not-interchangeable flag un-set.  (Yes, that's a double negative.  I don't know why we do that.)"
1746810,2018-02-02 19:10:46 UTC,"The new symbol file format will allow for this with any combination by
using an inheritance scheme.  The symbol library file format will be the
""easy"" part.  It will take considerably longer to modify the symbol
editor support this."
1746812,2018-02-01 23:11:07 UTC,"oh ... I did'nt rebase that patch since a long time.
This is probably why it built 8.1.1-0 version of rpm, which is not an update of 8.2.0.0. *facepalm*"
1746812,2018-02-01 22:56:33 UTC,So for the instack-underclod change:
1746812,2021-02-18 16:46:03 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1746812,2018-02-01 22:09:25 UTC,let me know if you still think there is an issue.
1746812,2018-02-01 21:32:43 UTC,Another change: https://review.openstack.org/#/c/533364/
1746812,2018-02-01 22:39:15 UTC,"Hmm, so we have in yum log:
Feb 01 16:47:58 Installed: instack-undercloud-8.2.0-0.20180131215127.5dd4e93.el7.centos.noarch"
1746812,2018-02-02 09:06:03 UTC,"Confirmed, once patches was rebased it worked as expected."
1746812,2018-02-01 22:08:59 UTC,ya.. the right rpm ended up on the system..
1746813,2018-02-01 23:06:14 UTC,"Hmm... perhaps one part thought it was there, and another part didn't? That's my best guess at the moment."
1746813,2018-02-01 23:04:35 UTC,I don't think it got as far as actually creating the VM in which to keep.
1746831,2019-09-19 14:46:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1746837,2018-02-02 01:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746837,2018-02-06 16:00:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1746837,2018-02-06 17:36:23 UTC,"Confirmed to be not working on upstream kernel v4.15!
My ethernet adapter also stops working on upstream kernel v4.15, but I guess that's another issue."
1746837,2018-02-23 11:49:24 UTC,"My mistake, it does' work on upstream kernel 4.15, although the ethernet adapter does break."
1746837,2019-10-03 11:42:40 UTC,I am using 4.15.0-65-generic x86_64 and the reader is not working. I am getting
1746837,2019-10-03 11:44:10 UTC,"07:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01)"
1746837,2019-10-03 12:23:26 UTC,Please follow instructions in comment #2 to try mainline kernel builds at https://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ .
1746837,2019-10-03 12:29:38 UTC,"On bionic, you may also want to try linux-oem-osp1 package, which has kernel driver rtl841l identical to current mainline kernel."
1746837,2020-10-20 21:31:49 UTC,"I'm still experiencing this issue on kernel 5.4.0-51-generic. The driver is missing, and the reader fails to recognize some types of SD cards."
1746839,2019-03-20 17:20:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746839,2019-05-12 14:36:37 UTC,"The issue looks like the one that got fixed upstream with that commit
https://github.com/intel/dleyna-server/commit/2a09e2b1"
1746840,2018-02-02 01:16:37 UTC,"after ""fresh install"" not free"
1746840,2018-02-02 12:42:01 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1746862,2018-02-02 04:17:21 UTC,This can be observed in the version in artful and from git sha ab9d26eab904880abd10158700dae57923044f49.
1746863,2019-03-22 03:48:12 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1746863,2018-12-19 10:04:53 UTC,This issue was fixed in the openstack/nova 16.1.7 release.
1746863,2018-11-09 23:18:17 UTC,"Reviewed:  https://review.openstack.org/599841
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1a266633e1077fe4a9101bb456a69ab89689be4b
Submitter: Zuul
Branch:    stable/pike"
1746863,2018-11-09 16:46:39 UTC,"Reviewed:  https://review.openstack.org/599840
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aa1966a70eb38bba1c7c3f88a77a2f2ea5fcc75f
Submitter: Zuul
Branch:    stable/pike"
1746863,2018-09-24 14:46:54 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1746863,2018-09-24 14:46:49 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1746863,2018-09-13 23:30:20 UTC,"Reviewed:  https://review.openstack.org/599732
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3051a0d5d5639b451d6da5e9f490332399b18c54
Submitter: Zuul
Branch:    stable/rocky"
1746863,2018-09-20 21:33:55 UTC,"Reviewed:  https://review.openstack.org/599766
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ab939372cd0488a0a4e2a8a1764a42eff2e329c5
Submitter: Zuul
Branch:    stable/queens"
1746863,2018-09-20 21:33:44 UTC,"Reviewed:  https://review.openstack.org/599765
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c35f29001a2ce036b7281a125cb5077e0dddc605
Submitter: Zuul
Branch:    stable/queens"
1746863,2018-09-13 22:05:16 UTC,"Reviewed:  https://review.openstack.org/599731
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9dbe8cd5d31c8f63765d239392b0c0f38ee674d1
Submitter: Zuul
Branch:    stable/rocky"
1746863,2018-09-04 18:18:31 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599732"
1746863,2018-09-04 20:45:53 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/599840"
1746863,2018-09-04 20:46:12 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/599841"
1746863,2018-02-02 05:49:34 UTC,I was wrong about any lazy-load of instance_group.hosts happening in a scheduler filter. It was occurring in nova/scheduler/utils.py in the setup_instance_group method which is called before select_destinations in conductor.
1746863,2018-07-10 14:45:19 UTC,It seems [anti-]affinity doesn't work at all with cells_v2. https://bugs.launchpad.net/nova/+bug/1746863
1746863,2018-07-24 02:48:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/585073"
1746863,2018-02-02 05:47:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540258"
1746863,2018-09-04 18:18:13 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599731"
1746863,2018-09-04 19:42:40 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/599765"
1746863,2018-09-04 19:42:58 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/599766"
1746863,2018-08-23 22:50:35 UTC,"Reviewed:  https://review.openstack.org/585073
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f2c4993b1748d679bce8de6ffc672490ef3fa49
Submitter: Zuul
Branch:    master"
1746863,2018-08-28 16:32:14 UTC,"Reviewed:  https://review.openstack.org/540258
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=14f4c502f92b10b669044e5069ac3b3555a42ee0
Submitter: Zuul
Branch:    master"
1746865,2018-03-05 11:40:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746865,2018-07-13 16:18:03 UTC,"My apologies, I did not see this report when I created a duplicate issue (https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1781002 Bug #1781002 )."
1746865,2018-07-24 03:39:38 UTC,"Same here.
Also after a dist-upgrade from 16.04 to 18.04:"
1746866,2020-10-22 19:56:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu."
1746869,2018-02-13 07:27:57 UTC,Another failure instance from a different run - http://ci.jujucharms.com/blue/organizations/jenkins/github-merge-juju/detail/github-merge-juju/40/pipeline
1746869,2019-07-09 02:29:32 UTC,The test no longer exists in Juju codebase.
1746871,2018-06-11 08:20:28 UTC,"The attachment ""needrestart-2.6-fix-erroneous-assignation-in-if-statements.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1746871,2018-06-11 08:09:50 UTC,I gave a quick look at the `/usr/sbin/needrestart` and the problem seems to be with one (or two) erroneous `if()` statements that performs an affectation to the `$value` instead of doing a regexp match test.
1746871,2018-04-10 11:24:16 UTC,"This also affects other services containing a dot in the name, like php7.0-fpm.service, which gets truncated to ""0-fpm.service"" which obviously can't be found."
1746871,2018-04-10 11:31:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746878,2018-02-02 12:41:38 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1746884,2018-03-26 18:12:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746884,2018-03-26 20:15:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1746901,2018-02-09 09:51:14 UTC,"3.13.0-142.191~precise1 - generic
Regression test CMPL."
1746901,2018-02-22 14:40:55 UTC,The package has been published and the bug is being set to Fix Released
1746911,2019-08-20 15:41:52 UTC,"Fixed in revision 375e8a2f978270c6da1b98693859a6b75d4ba21e
https://git.launchpad.net/kicad/patch/?id=375e8a2f978270c6da1b98693859a6b75d4ba21e"
1746921,2018-07-10 12:09:12 UTC,"We are using gpg 2.2.4 in bionic+ and libgcrypt 1.8.1 in bionic, and 1.8.2 in cosmic; so that's fixed. Now, you say 1.8.2 once and 1.8.1 the other time, so I'm not sure if the problem is resolved in bionic or not - I think it mostly is?"
1746921,2018-07-17 08:09:06 UTC,libgcrypt 1.8.2 has the fixes. That 1.8.1 was a typo on my part. The problem is not fixed in bionic.
1746921,2018-12-02 20:36:51 UTC,Is there no interest in fixing this bug in an LTS release? We are avoiding using GnuPG on our Ubuntu LTS servers due to this bug.
1746943,2018-02-06 09:17:01 UTC,I tried psproc-ng from https://launchpad.net/ubuntu/+source/procps/2:3.3.12-1ubuntu2/+build/10452812
1746943,2018-03-15 14:56:46 UTC,"Could you provide instructions to reproduce that don't require Fedora or docker, please?"
1746943,2019-09-23 14:37:57 UTC,Still waiting for repro instructions (eg attaching a binary that doesn't run under QEMU).
1746943,2019-11-23 04:17:24 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1746949,2018-02-02 09:33:34 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=778926 might be related
1746949,2018-02-02 09:33:56 UTC,This is a known issue for software-rendered windows that update rapidly. There are several reasons for it so also several possible solutions...
1746949,2018-02-05 09:37:09 UTC,"The following commit fixes the issue for 90%:
https://git.gnome.org/browse/vte/commit/?id=809e79770"
1746955,2020-01-24 17:54:10 UTC,Hittin the same problem in the middle of time-critical task. I am working with Arduino based board and an arm based board. Can't even uninstall gcc-arm-embedded. I am using Ubuntu 18.04
1746955,2018-12-05 00:33:51 UTC,This bug still exists in cosmic.
1746955,2018-09-06 16:49:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746955,2019-03-26 16:13:16 UTC,I also have the same issue.
1746970,2018-02-06 15:56:45 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1746970,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1746970,2018-03-21 11:06:43 UTC,I verified kernel from -proposal (Ubuntu 17.10 (GNU/Linux 4.13.0-38-generic x86_64)) and it works as expected.
1746970,2018-03-19 10:58:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1746970,2018-02-18 22:16:00 UTC,I can also confirm that the Kernel posted in #20 resolves the issue with my Emulex Zephyr-X FC adapter.
1746970,2018-02-16 16:01:54 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/090259.html"
1746970,2018-02-14 09:28:03 UTC,"Joseph Salisbury, I tested your kernel and it works as expected, no bug.
Thanks!"
1746970,2018-02-13 20:58:10 UTC,"I built a test kernel with commit 2877cbffb79.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746970"
1746970,2018-02-13 12:00:56 UTC,Adding https://github.com/torvalds/linux/commit/2877cbffb79ed121a6bcc5edbe629d3aba36cd29
1746970,2018-02-07 12:16:48 UTC,Installed latest upstream kernel. And it works.
1746970,2018-02-02 11:30:19 UTC,apport information
1746970,2018-02-02 11:30:12 UTC,apport information
1746970,2018-02-02 11:30:17 UTC,apport information
1746970,2018-02-02 11:30:16 UTC,apport information
1746970,2018-02-02 11:30:15 UTC,apport information
1746970,2018-02-02 11:30:14 UTC,apport information
1746970,2018-02-02 11:30:13 UTC,apport information
1746970,2018-02-02 11:30:11 UTC,apport information
1746970,2018-02-02 11:30:09 UTC,apport information
1746970,2018-02-02 11:30:08 UTC,apport information
1746970,2018-02-02 11:30:07 UTC,apport information
1746970,2018-02-02 11:23:58 UTC,"Hi, I confirm the bug on direct attach."
1746970,2018-02-02 11:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1746970,2018-02-02 11:30:18 UTC,apport information
1746970,2018-02-02 11:30:10 UTC,apport information
1746973,2018-02-23 18:17:15 UTC,The image create form was re-implemented as AngularJS. I think this is a feature gap in the angularJS form.
1746981,2018-02-02 16:20:40 UTC,"The attachment ""Fixed version of Gentium Plus Italic"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1746983,2018-08-09 15:28:00 UTC,This issue was fixed in the openstack/virtualbmc 1.4.0 release.
1746983,2018-02-05 10:18:32 UTC,"the change was not auto-linked to this bug: https://review.openstack.org/#/c/540368/
assigning myself manually"
1746984,2018-02-02 16:28:13 UTC,"ubuntu@k8s-client:~$ juju version
2.3.1-xenial-amd64"
1746984,2020-12-02 04:17:16 UTC,[Expired for juju because there has been no activity for 60 days.]
1746984,2018-02-02 15:43:37 UTC,"Gary,
Which version of juju are you using?
Are any compute and/or network availability zones configured in the OS deployment?
Can you try specifying the external network by UUID instead of name?"
1746984,2018-02-02 21:48:57 UTC,To my knowledge the config is now up and running.
1746984,2018-02-02 17:39:40 UTC,"I'd suggest bootstrap --config external-network=<ext net UUID> --config
network=<private net UUID>, and if you have more than the default model,
also use --model-default"
1746995,2018-02-05 12:19:30 UTC,Do you have strace output for the getcwd system call before the failure?  That would be helpful.
1746995,2018-02-05 13:30:31 UTC,I do now:
1746995,2018-02-07 15:53:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1746995,2018-02-08 01:33:53 UTC,"Hi,"
1746995,2018-02-08 09:52:51 UTC,"Hi,"
1747002,2018-02-02 14:23:17 UTC,Review https://bugs.launchpad.net/charms/+source/ceph-radosgw/+bug/1747002
1747002,2018-02-07 21:11:39 UTC,"Note, the config duplicates are exact duplicates, so no change in behavior expected if they're removed."
1747002,2018-02-07 21:13:26 UTC,Seems like perhaps we should start running yamllint as part of tox. We could propose a change for that and see what others think.
1747002,2018-02-09 12:29:53 UTC,"I think that would be a good test.
YAML files are easily broken by accident since they are sensitive to hidden whitespace mismatches. (python legacy)
Happens easily when you edit a file."
1747002,2018-02-09 12:46:45 UTC,Review: https://review.openstack.org/#/c/540396
1747023,2018-09-09 17:09:51 UTC,The suggested fix doesn't seem to work on 18.04.
1747023,2018-06-25 17:02:31 UTC,"Thanks, fix worked for me (related: https://bugs.launchpad.net/bugs/1721074 )"
1747023,2018-06-21 23:48:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747023,2018-06-21 23:48:33 UTC,"Hello there,"
1747030,2018-02-02 16:21:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1747030,2018-02-02 20:39:37 UTC,Inappropriate.
1747030,2018-02-03 06:14:47 UTC,Seem as if it doesn't have to do with mounting and unmounting?
1747030,2018-02-03 06:35:27 UTC,EDIT: NOT A BUG - SCREENCAST LASTS FOR ONLY 30s MAX
1747034,2020-06-25 08:36:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747037,2018-04-09 20:19:29 UTC,"Fixed in revision 5ef715f3d3c795327013ec8a9543891d479179c3
https://git.launchpad.net/kicad/patch/?id=5ef715f3d3c795327013ec8a9543891d479179c3"
1747037,2018-04-09 18:06:56 UTC,"I have the bug that it finds the field with the contents however it does not replace it. Hitting ""replace"" or ""replace all"" does nothing."
1747037,2018-02-03 19:02:20 UTC,"Yeah, I probably wasn’t clear enough.  Pcbnew now has a Change Footprints on the Edit menu which allows you to say which Footprints you want to change (those matching value, matching footprintID, etc.).  If we had a Change Symbols equivalent in Eeschema, then you wouldn’t need to use S&R."
1747037,2018-02-03 17:35:47 UTC,"This is actually changing the symbol library name of the schematic
symbol using S&R rather than the edit schematic symbol dialog which
means they have to be changed one symbol at a time."
1747037,2018-02-03 17:14:41 UTC,"This is Exchange Footprints for Symbols, right?  Why would we want to go to Find/Replace for that?"
1747037,2018-02-02 18:47:50 UTC,"It IS *not* a field from the component, this is also a fact."
1747037,2018-02-03 06:48:29 UTC,"On 02/02/2018 03:42 PM, Franck78 wrote:

> my initial concern was just to get rid of the *RESCUE-* components
> created after a lib upgrade.
"
1747037,2018-02-02 20:42:48 UTC,my initial concern was just to get rid of the *RESCUE-* components created after a lib upgrade.
1747037,2018-02-02 19:25:39 UTC,"On 02/02/2018 01:53 PM, Seth Hillbrand wrote:

> Hi Franck-
>
> Please remember that people are volunteering their time to help you.
>
> It sounds like you would like a new feature in Eeschema where you can
> globally update one Library Symbol with another.
>
> Right now, you can edit the symbol one at a time, and change the symbol,
> which will adjust the line you are pointing to.  But this is one symbol
> at a time.
>
> We could change this ticket to a feature request for a global symbol
> search/replace.  But it can't fall under the Find/Replace dialog for the
> reason Wayne mentioned.
>
"
1747037,2018-02-02 18:53:04 UTC,Hi Franck-
1747037,2018-02-02 18:28:19 UTC,"For god's sake, can you adopt the users's viewpoint ???"
1747037,2018-02-03 16:32:14 UTC,Thank you for the explanation Wayne.
1747037,2018-02-02 16:59:02 UTC,"This is not a field.  Fields begin with F.  You are pointing to the name
of the symbol in the library.  Change that to a name that doesn't exist
in any library and you will break your schematic."
1747040,2018-02-02 16:40:21 UTC,"Ah, this is with 2.3.2, forgot to add that."
1747040,2019-09-30 13:03:44 UTC,I suspect that this related more to the cmd package from juju than juju itself. But I need to take a further look into it.
1747040,2019-10-04 09:38:22 UTC,"The place where this can be changed in juju would be here:
https://github.com/juju/juju/blob/develop/cmd/juju/commands/plugin.go#L77"
1747040,2019-10-04 09:57:32 UTC,PR for discussion open: https://github.com/juju/juju/pull/10683
1747042,2020-01-06 21:38:51 UTC,"PaILS learned from Equinox that this bug may be effecting the display of some volume level holds.
The holds still fill, they just don't display."
1747049,2020-01-30 14:50:40 UTC,This is a bug in charmhelpers that has been fixed here: https://github.com/juju/charm-helpers/commit/dba22844
1747053,2019-05-13 06:46:48 UTC,"Looking at the bundle + trace provided in the initial bug description, I suspect that the differing IPs between the errors, and the VIP that the percona charm is configured with will be a core issue."
1747053,2019-07-13 04:17:57 UTC,[Expired for OpenStack cinder charm because there has been no activity for 60 days.]
1747053,2019-07-13 04:17:56 UTC,[Expired for OpenStack heat charm because there has been no activity for 60 days.]
1747053,2019-05-13 06:20:23 UTC,"Jason / Ashley,"
1747053,2018-03-08 21:16:15 UTC,"No, we've hit it on non dnsHA runs too: https://solutions.qa.canonical.com/#/qa/bug/1747053"
1747053,2018-03-08 20:57:23 UTC,"This only is occurring in our DNS-HA runs, right?"
1747053,2018-04-18 15:23:27 UTC,We hit this bug again.  It is running xenial-pike with stable charms.
1747053,2018-02-06 18:33:42 UTC,"Hit this again, this time from a cinder unit."
1747056,2018-03-05 18:08:17 UTC,We need to pull in a SeaBIOS update with this fix applied to resolve this
1747056,2020-12-01 10:40:20 UTC,"The SeaBIOS update mentioned by Daniel has been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=0b8f74488e50f"
1747056,2018-02-05 12:32:25 UTC,I bisected seabios and found this seabios change to be the cause of the problem
1747060,2018-02-21 11:58:22 UTC,"This has been an interesting discussion. Next time, Martin - purchase a less expensive machine. ;)"
1747060,2018-02-20 16:21:15 UTC,"Hi Brian,"
1747060,2018-02-20 15:33:39 UTC,"Hello Martin,"
1747060,2018-02-20 10:13:05 UTC,"Hi Brian,"
1747060,2018-02-16 20:15:03 UTC,"In an earlier post Martin said
  > No such info is in the manual, at least I couldn't see it."
1747060,2018-02-16 15:16:37 UTC,"I would divide it into 2 groups:
1) supported by device
2) supported by hplip"
1747060,2018-02-15 11:02:38 UTC,I suppose all us should have read the documentation first and saved ourselves some work.
1747060,2018-02-14 14:44:29 UTC,"Hi again,"
1747060,2018-02-02 19:19:56 UTC,What does
1747060,2018-02-08 15:26:32 UTC,@Nishitha
1747060,2018-02-09 20:36:09 UTC,These 24/48 hour lags in reponse are tedious.
1747060,2018-02-03 13:22:45 UTC,"Not sure if this will help, but:
$ lsusb|grep Hewlett
Bus 003 Device 002: ID 03f0:9f17 Hewlett-Packard"
1747060,2018-02-03 18:19:13 UTC,"> Here's output of sane-find-scanner (with sudo):
"
1747060,2018-02-03 13:14:12 UTC,"Hi brian_p, thanks for having a look into the issue.
Here's output of sane-find-scanner (with sudo):"
1747060,2018-02-06 18:56:35 UTC,"Hi brian_p,
sorry for a bit long time to replay."
1747060,2018-02-07 13:16:28 UTC,"Thanks for the detail, Martin."
1747060,2018-02-08 05:42:03 UTC,"Hi Martin,"
1747060,2018-02-04 12:49:41 UTC,"> (I use Debian but, AIUI, Ubuntu and Mint use the same packages).
"
1747081,2020-04-17 11:03:42 UTC,"snap    2.44.3+20.04
snapd   2.44.3+20.04
series  16
ubuntu  20.04
kernel  5.4.0-24-generic"
1747081,2020-02-18 11:43:26 UTC,"snap    2.43.2
snapd   2.43.2
series  16
ubuntu  18.04
kernel  5.3.0-40-generic
i m facing same problem all the sanps i download from software center can not be accesed directly fro my application or from home screen"
1747081,2019-10-26 12:54:14 UTC,"Hi,"
1747081,2019-09-20 08:55:24 UTC,So this sounds like a problem that I fixed in the following PR:
1747081,2019-03-25 13:17:40 UTC,"Hey,
i can report the same bug. For me only some snap apps are influenced by the bug while others still show the icons. My system is configured like this:"
1747081,2019-03-06 19:18:04 UTC,"I am using fish shell (on wayland), and installing the `bass` plugin and adding this to `~/.config/fish/config.fish` worked for me:"
1747081,2019-02-24 05:46:27 UTC,I have the same problem on Ubuntu 18.10 with Gnome 3.30.2
1747081,2018-04-01 15:55:48 UTC,I have the same problem on Ubuntu 17.10 with gnome 3.26.2 on wayland
1747081,2018-02-02 23:12:35 UTC,"No worries,"
1747081,2018-02-02 22:35:20 UTC,"Sorry, I missed that you pointed out Ubuntu 18.04. Might also be worth mentioning which desktop environment you're using (Gnome?)."
1747081,2018-02-02 22:33:44 UTC,"Could you run `snap version` and post the output here? Add any other information you think might be pertinent such as distro (ubuntu?) release number of distro, system architecture (x86, amd64...), kernel version...."
1747081,2019-03-06 19:20:48 UTC,"I’m zsh, you can add"
1747081,2018-04-23 18:12:28 UTC,I have the same problem on Ubuntu 16.04.4 with Xfce.
1747084,2019-09-19 11:57:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1747085,2018-02-03 06:17:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747097,2018-04-24 09:53:15 UTC,We reverted the implementation in https://github.com/snapcore/snapcraft/commit/77770452be681b5b3703eba61b654c0ce2ef7664
1747097,2018-03-07 08:02:47 UTC,https://github.com/snapcore/snapcraft/pull/1959
1747099,2018-02-08 19:24:15 UTC,What's the content of /etc/grub.d/30_os-prober_proxy?
1747101,2018-02-03 03:07:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540568"
1747101,2018-07-26 08:57:40 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.0 release.
1747101,2019-05-16 12:43:39 UTC,"Faced this bug in Queens, cherry-picked the patch to stable/queens:"
1747104,2018-02-03 03:38:46 UTC,i need to solve this problem
1747104,2018-02-07 07:31:50 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1747105,2018-02-14 09:17:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747106,2018-02-04 23:49:58 UTC,"OK, so I renamed to test.hpgl, and get this:"
1747106,2018-02-05 00:06:12 UTC,"I see the disclaimer, and inkscape will open the hpgl file that it created, and not the others."
1747106,2018-02-05 00:09:18 UTC,"Some work, some don't."
1747106,2018-02-03 12:00:52 UTC,could you attach the .hpgl file for testing purposes?
1747106,2018-02-04 10:24:17 UTC,"for hpgl files, it is necessary that the extension must be .hpgl, otherwise Inkscape will not recognize this file as being hpgl."
1747115,2019-03-17 07:29:58 UTC,Remote access does not work as well e.g. by using the Windows client SaneTwain
1747115,2018-12-08 18:31:24 UTC,"Finally, the following is what works for me:"
1747115,2019-12-02 13:09:37 UTC,"Hi,
having the same issue here I found out that the rule in /lib/udev/rules.d/99-saned.rules should set the GROUP to ""scanner"" rather than ""saned""
e.g. replace
ENV{libsane_matched}==""yes"", GROUP=""saned""
by
ENV{libsane_matched}==""yes"", GROUP=""scanner""
It solve the problem on my system."
1747115,2018-12-01 15:54:38 UTC,I've just tried to configure scanbd under Ubuntu 18.10 and ran into same trouble.
1747115,2018-12-08 12:51:49 UTC,I made the next step.
1747115,2018-03-31 07:12:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747115,2018-04-16 09:37:40 UTC,"Thank you for your report and sorry for your troubles.  The Debian bug you referenced is not what you are experiencing, though, since Chris confirmed this was gone in the package that was eventually uploaded as 1.4.4-2"
1747116,2018-02-03 07:32:20 UTC,"StacktraceTop:
 WebKit::WaylandCompositor::Surface::flushPendingFrameCallbacks (this=this@entry=0x7fbaab0f3ec8) at ./Source/WebKit/UIProcess/gtk/WaylandCompositor.cpp:258
 WebKit::WaylandCompositor::Surface::setWebPage (this=0x7fbaab0f3ec8, webPage=0x0) at ./Source/WebKit/UIProcess/gtk/WaylandCompositor.cpp:181
 WebKit::AcceleratedBackingStoreWayland::~AcceleratedBackingStoreWayland (this=0x7fbaab0ff2b8, __in_chrg=<optimized out>) at ./Source/WebKit/UIProcess/gtk/AcceleratedBackingStoreWayland.cpp:61
 WebKit::AcceleratedBackingStoreWayland::~AcceleratedBackingStoreWayland (this=0x7fbaab0ff2b8, __in_chrg=<optimized out>) at ./Source/WebKit/UIProcess/gtk/AcceleratedBackingStoreWayland.cpp:62
 std::default_delete<WebKit::AcceleratedBackingStore>::operator() (this=<optimized out>, __ptr=<optimized out>) at /usr/include/c++/7/bits/unique_ptr.h:78"
1747116,2018-02-06 21:23:45 UTC,Forwarded upstream: https://github.com/lwindolf/liferea/issues/603
1747116,2018-02-26 15:09:03 UTC,This is a regression in Webkit and reported upstream: https://bugs.webkit.org/show_bug.cgi?id=183091
1747118,2018-05-15 14:50:32 UTC,This change was made by a bot.
1747119,2018-05-01 14:07:21 UTC,It sounds like this orville-write package is broken and should probably be deleted.
1747134,2018-02-05 09:40:25 UTC,"Correct the fix commit info. But applying this patch to v4.13, the issue still exists. It may have more dependencies."
1747134,2018-03-02 19:48:21 UTC,"As bionic already ships a v4.15 kernel, this should be fixed in bionic."
1747134,2018-04-17 15:56:22 UTC,"I built an Artful test kernel with a back port of commit 947134d9b00.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1747134"
1747134,2018-04-17 22:04:32 UTC,A Xenial test kernel is now also available.  Xenial required commit 70b8301f6 as a prerequisite.  The xenial test kernel can be downloaded from:
1747134,2018-07-24 09:33:53 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1747138,2018-03-11 18:19:50 UTC,This happened to me upgrading from Artful.
1747138,2018-02-09 15:25:26 UTC,This happened to me on a do-release-upgrade update from Xubuntu 17.10.
1747138,2018-02-06 15:19:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747149,2019-08-23 08:24:14 UTC,In our production we are using the SAML2 SSO login.
1747149,2019-09-20 09:52:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/683347"
1747149,2019-10-29 15:23:19 UTC,"Reviewed:  https://review.opendev.org/683347
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a11aa7ff62c15d7bf15367106f933ef0ae5d4521
Submitter: Zuul
Branch:    master"
1747149,2019-11-21 10:24:50 UTC,This issue was fixed in the openstack/horizon 17.0.0 release.
1747149,2020-03-25 11:29:35 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/714920"
1747149,2020-04-29 05:22:29 UTC,"Reviewed:  https://review.opendev.org/714920
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a1afb5046721ab57fc0af9d62400c4a21647e1f4
Submitter: Zuul
Branch:    stable/train"
1747167,2020-05-23 17:26:25 UTC,Changing bug's status to fix released as recent releases are no longer affected
1747167,2018-02-20 11:36:50 UTC,Also got this issue in production.
1747167,2020-05-23 17:04:40 UTC,This problem is not reproducible in stable/train:
1747167,2020-05-23 17:25:03 UTC,"OK, maybe not a duplicate, but changed workflow for recent releases:"
1747175,2018-11-06 01:21:59 UTC,"My problem is with Intel on board sound. alsamixer shows as:
[PCH            ]: HDA-Intel - HDA Intel PCH                               │
│                      HDA Intel PCH at 0xdc240000 irq 127                     │"
1747175,2018-06-19 18:46:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747179,2018-02-03 18:32:54 UTC,This is a gif that shows what the warp pin tool does.
1747179,2020-09-06 15:01:43 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1747179,2018-02-17 16:58:02 UTC,"Exuse me mr. Brynn that's not what I mean. I know gimp can make gifs, its the bone system figures I want."
1747179,2018-02-10 17:22:21 UTC,"I don't think it would cost that much money to make, it's just like a path effect. A real cool one."
1747179,2018-02-05 14:37:25 UTC,'kay :)
1747179,2018-02-10 17:20:26 UTC,I don't think it will cost that much money to make at all. It's just like a path effect. A real cool one.
1747179,2018-02-04 17:52:51 UTC,"Zech, do not add me back in again as a subscriber. That's more than impolite, I have unsubscribed twice already. Stop it."
1747179,2018-02-04 17:31:37 UTC,What's an illustrating software without animating... Like this...https://goo.gl/images/zTWsuA
1747179,2018-02-03 18:52:26 UTC,This is a gif that shows transforming an object with warp pin tool.
1747179,2018-02-03 18:39:47 UTC," I know it sounds like you can do the same with editing nodes, but with editing nodes you could lose the original shape of an object. With warp pin tool you can't"
1747179,2018-02-03 18:36:30 UTC,This is a gif that shows what the pin tool does
1747179,2018-02-04 20:22:32 UTC,Sorry about that. Just pretend this whole thing never happened.
1747179,2018-02-05 23:47:19 UTC,Animation for Inkscape is a lllooong standing request.  This page has info about how you can currently animate images which were made in Inkscape.  https://inkscape.org/en/learn/animation/
1747180,2018-02-03 18:55:22 UTC,"StacktraceTop:
 pkgPolicy::GetPriority (this=0x562a931ea5d0, Ver=..., ConsiderFiles=<optimized out>) at /build/apt-ke47OC/apt-1.2.24/apt-pkg/policy.cc:384
 pkgPolicy::GetCandidateVerNew (this=this@entry=0x562a931ea5d0, Pkg=...) at /build/apt-ke47OC/apt-1.2.24/apt-pkg/policy.cc:239
 pkgPolicy::GetCandidateVer (this=0x562a931ea5d0, Pkg=...) at /build/apt-ke47OC/apt-1.2.24/apt-pkg/policy.cc:136
 pkgDepCache::Init (this=this@entry=0x562a931ee2f0, Prog=Prog@entry=0x7ffdbc95b530) at /build/apt-ke47OC/apt-1.2.24/apt-pkg/depcache.cc:158
 pkgCacheFile::BuildDepCache (this=this@entry=0x7ffdbc95b2f0, Progress=Progress@entry=0x7ffdbc95b530) at /build/apt-ke47OC/apt-1.2.24/apt-pkg/cachefile.cc:189"
1747180,2018-02-03 19:57:15 UTC,"Thanks for your bug report. I made it public as it does not contain any sensitive information. I'm not entirely sure why this is happening, but I might dig into it a bit later."
1747181,2018-04-24 18:11:13 UTC,This issue was fixed in the openstack/glance 16.0.1 release.
1747181,2018-04-19 14:01:54 UTC,This issue was fixed in the openstack/glance 17.0.0.0b1 development milestone.
1747181,2018-04-09 15:18:43 UTC,"Reviewed:  https://review.openstack.org/559752
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=5326f644439f5b7c81a8da12189af52dec6f33b1
Submitter: Zuul
Branch:    stable/queens"
1747181,2018-04-08 08:01:58 UTC,"Reviewed:  https://review.openstack.org/559505
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=57310ad88f64214869ab1962184e74583e0845b6
Submitter: Zuul
Branch:    master"
1747181,2018-04-07 22:07:39 UTC,Change proposed to master: https://review.openstack.org/#/c/559505/
1747181,2018-04-09 14:36:53 UTC,Cherry-pick to stable/queens: https://review.openstack.org/#/c/559752/
1747181,2018-04-06 13:39:16 UTC,May want to backport this to stable/queens and stable/pike
1747181,2018-04-06 13:28:08 UTC,"Domain names in keystone are *supposed to be* case sensitive (though for a while they weren't *actually* case sensitive in v3).  See this keystone bug report for details and date of the fix:
https://bugs.launchpad.net/keystone/+bug/1229093"
1747181,2018-03-20 00:13:48 UTC,"I guess the advantage of using *_domain_id is that they'd be UUIDs and not case-sensitive (not sure about that, though -- I thought the domain_name was case insensitive)."
1747198,2018-02-03 22:34:42 UTC,One way around this is to run `ssh localhost` in the terminal window then it works.
1747198,2018-02-04 13:24:34 UTC,"VTE no longer does utmp logging. This was an upstream change made almost three years ago at https://bugzilla.gnome.org/show_bug.cgi?id=747046, and is clearly not going to get reverted by upstream."
1747200,2019-10-15 11:16:20 UTC,"I'm re-assigning this to subiquity which is, hopefully, the right place for this issue."
1747210,2018-02-04 00:03:30 UTC,pylint-django updated their tests in https://github.com/PyCQA/pylint-django/commit/7162194195074f3b7b2d126ab740edf254898a7e - similar changes might be needed for these plugins.
1747212,2018-07-10 06:32:04 UTC,"Can we close this bug in favor of
Bug #1779472, making the mute controls persistent?"
1747212,2018-07-10 13:38:32 UTC,"I disagree. What do you think about the incosistency

> Mic inputs are off per default, and can be enabled by ""Talkover"".
"
1747212,2018-07-14 22:05:49 UTC,"All channels have a mute control, even Mics have it.
Mixxx also has a routing button: [Auxiliary1],""master"" that can be used instead of ""mute"" here.
""mute"" is the equivalent to Kill for the volume slider. It was considered to use musically the same way to mute the sound instantly without any fading."
1747212,2018-07-14 22:07:26 UTC,I have just discovered that mute does not work for PLF which is correct. So the control is useless in Deere. I will file a bug.
1747212,2018-07-15 01:05:50 UTC,"> I have never seen a ""enable"" button on hardware mixers though, but there are some with a mute controls.
"
1747212,2018-07-15 06:25:34 UTC,"That works as well for me.
So we ditch the persistence idea from https://bugs.launchpad.net/bugs/1779472 ?"
1747212,2018-07-19 14:27:35 UTC,"I had second look at the skins, without the volume slider, replacing the mute button, by the master enable control, does make most sense.
So I think I we should adjust the skins to either mute or disable aux on skin load the bug is fixed."
1747212,2018-07-19 15:17:55 UTC,https://github.com/mixxxdj/mixxx/pull/1755
1747216,2018-06-11 10:54:29 UTC,"Hi Charles,"
1747216,2018-04-29 13:31:47 UTC,"PCB's base unit is nanometers (nm), pcb default units is 0.01 mil (cmil)."
1747221,2018-06-27 08:04:52 UTC,"Hey, did you make any progress with this problem?"
1747221,2018-02-04 02:28:39 UTC,"There are no errors on the commandline when opening, ""saving"" or closing the files, only upon closing the application:
(gottengeography:32113): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed"
1747231,2020-02-27 23:15:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747232,2018-06-14 11:57:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747232,2018-06-14 12:07:10 UTC,"I confirm this issue. The settings of the screenshot directory are saved correctly. The settings of the screencast directory is not saved.
It's really uncomfortable."
1747245,2018-02-04 11:32:46 UTC,nothing to say...
1747252,2018-03-19 16:32:06 UTC,"I have not seen that for a while.
I think more or less since Mixxx does not crash any more."
1747252,2018-10-19 16:08:06 UTC,"@Be, you have already confirmed it. Why it is incomplete and scheduled for disposal now?"
1747252,2018-10-19 16:29:54 UTC,"Sorry, I was a bit hasty in changing the state of this. No one has identified how to reproduce this yet, but yes, I have seen it occur multiple times."
1747252,2018-03-12 22:14:39 UTC,"I have run into this bug a few times lately. I have not figured out how to reproduce it. When it happens, the play button LED on my controller that is connected to the play_indicator Control does not light up."
1747252,2018-03-19 11:05:01 UTC,"Has anyone figured out how to reproduce this reliably? Does anyone have an idea of what may be happening here? If no one has looked into this, let's change the milestone to 2.2."
1747261,2018-02-07 07:24:04 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1747262,2018-02-11 02:32:32 UTC,"confirmed, same problem here"
1747263,2018-02-04 14:40:29 UTC,The below commit has been confirmed as the fix for this:
1747263,2018-02-14 09:38:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1747263,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1747273,2018-02-08 17:00:51 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1747273,2018-02-06 19:10:40 UTC,This bug also affects me
1747273,2018-02-09 13:23:15 UTC,"> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
"
1747273,2018-02-10 07:58:51 UTC,Does change the value of /sys/class/backlight/thinkpad_screen/brightness change the brightness?
1747273,2018-02-10 14:11:18 UTC,The directory `/sys/class/backlight` is empty.
1747273,2018-12-09 06:04:52 UTC,"I can reproduce this bug on my ThinkPad p51, this is a new bug in 18.10. Any progress?"
1747273,2018-04-17 15:39:54 UTC,ping Michael and Urschl
1747273,2018-06-17 04:17:32 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1747273,2018-09-26 20:46:11 UTC,"I did some testing: deactivated the dedicated graphics in the bios, booted to ubuntu 18.04 and 18.10 (installed parallel) and both worked. Though with the dedicated graphics enabled (nvidia) the brightness does not work..."
1747273,2018-12-09 06:30:06 UTC,This change was made by a bot.
1747273,2019-03-07 06:31:42 UTC,Does this still happen on an up-to-date system?
1747273,2019-10-25 14:14:41 UTC,"This still happens in a fresh install of 19.10 with discrete-only graphics (Nvidia enabled, Intel disabled in BIOS) and with the nvidia driver."
1747273,2018-02-10 14:51:18 UTC,"Not familiar with Thinkpad laptops, does it only show backlight sysfs with thinkpad-acpi.brightness_enable=1?"
1747273,2018-02-05 18:50:39 UTC,apport information
1747273,2018-02-05 18:50:33 UTC,apport information
1747273,2018-02-05 18:50:36 UTC,apport information
1747273,2018-02-05 18:50:38 UTC,apport information
1747273,2018-02-04 16:21:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1747273,2018-02-05 18:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1747273,2018-02-05 18:50:21 UTC,apport information
1747273,2018-02-05 18:50:23 UTC,apport information
1747273,2018-02-05 18:50:24 UTC,apport information
1747273,2018-02-05 18:50:25 UTC,apport information
1747273,2018-02-05 18:50:32 UTC,apport information
1747273,2018-02-05 18:50:27 UTC,apport information
1747273,2018-02-05 18:50:29 UTC,apport information
1747273,2018-02-05 18:50:30 UTC,apport information
1747273,2018-02-05 18:50:31 UTC,apport information
1747273,2018-02-05 18:50:34 UTC,apport information
1747273,2018-02-05 18:50:26 UTC,apport information
1747273,2018-02-05 18:50:35 UTC,apport information
1747276,2018-02-23 11:30:41 UTC,It is an AMD GPU.
1747276,2018-02-13 17:39:28 UTC,The debian bug report suggests this happens only with AMD GPUs.
1747276,2018-02-09 07:16:56 UTC,I found an upstream bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885920  Does the workaround listed in it's description work for you?
1747276,2018-02-07 16:50:51 UTC,It does work on X.org indeed. But not wayland.
1747276,2018-02-07 16:46:21 UTC,This is not fixed as long as it does not work correctly on Wayland.
1747276,2018-02-09 14:58:24 UTC,">It seems like we just need to wait for Firefox 59 for Wayland support.
"
1747276,2018-02-07 04:10:55 UTC,"Two firefox processes remain on the process list (ps -e) but they never produce a window, and are killable with sudo kill -9 <pid>"
1747276,2018-02-07 15:27:20 UTC,Is this bug Gecko related? All three share Gecko as their HTML layout engine.
1747276,2018-02-04 17:59:58 UTC,"Cannot use apport either as it fails with ""firefox has been upgraded since you reported"" error since I have not done any upgrades at that time."
1747276,2018-02-04 18:23:54 UTC,Happens even with a clean profile.
1747276,2018-02-07 16:31:09 UTC,Firefox and Libreoffice are working again for me after the latest updates.  Possibly as a result of:
1747276,2018-02-05 09:55:15 UTC,"Apport output for thunderbird(manually entered again, the lines which are identical are eliminated):
thunderbird 1:52.6.0+build1-0ubuntu1
Tags: bionic wayland-session
Extensions: none (apport fails to detect)"
1747276,2018-02-05 15:20:19 UTC,Happens even in a live cd or a fresh install produced from it.
1747276,2018-02-05 08:46:08 UTC,"Apport output for firefox(manually entered here as apport fails):
firefox 59.0~b5+build1-0ubuntu0.18.04.1
Bug
AddonCompatCheckDisabled: False
Apport: 2.20.8-0ubuntu8
amd64
Audio: irrelevant as not a sound related bug
BuildID: 20180201215627
Channel: Beta
Desktop: GNOME
Extensions: Dark Mode, IPFS companion, Greasemonkey (apport fails to list them)
Plugins: Flash
DistroRelease: 18.04
InstallationMedia: irrelevant as the system is fully upgraded over it three times
ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
Tags: third-party-packages bionic wayland-session-beta-channel"
1747276,2018-02-05 21:35:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747280,2018-02-11 18:38:39 UTC,Fixed in: https://review.openstack.org/#/c/540678/
1747280,2018-03-13 21:40:21 UTC,This issue was fixed in the openstack/python-zunclient 1.2.0 release.
1747282,2018-06-05 18:23:01 UTC,This issue was fixed in the openstack/python-zunclient 1.4.0 release.
1747282,2018-02-04 19:38:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540678"
1747282,2018-02-05 02:33:25 UTC,"Reviewed:  https://review.openstack.org/540678
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=0124bcf77333d85c4c937b3dca565e4e6902f4a8
Submitter: Zuul
Branch:    master"
1747296,2018-02-04 21:52:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747296,2018-04-20 02:20:39 UTC,Why do we not upgrade this package to a version where this bug does not appear as it makes Tor for me unusable?
1747296,2018-02-26 19:01:32 UTC,"The workaround is to download the bionic package, it installs on ardvark w/o failed dependencies."
1747302,2018-02-06 07:22:55 UTC,Lack of translation needs to be fixed in different way case by case.
1747302,2018-02-06 09:41:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541204"
1747302,2018-02-06 14:30:53 UTC,"Reviewed:  https://review.openstack.org/541126
Committed: https://git.openstack.org/cgit/openstack/heat-dashboard/commit/?id=01828789e23ca75fca0c0a29d811dfbb7e2f35ba
Submitter: Zuul
Branch:    master"
1747302,2018-02-07 01:24:44 UTC,"Reviewed:  https://review.openstack.org/541204
Committed: https://git.openstack.org/cgit/openstack/heat-dashboard/commit/?id=62a93c9b8056da5c969347a0ab7bd53755f7dc82
Submitter: Zuul
Branch:    master"
1747302,2018-02-09 21:57:09 UTC,Thank you very much for the quick action to fix this.
1747302,2018-02-09 22:01:22 UTC,"My apologies -- I have overlooked the comment #2:
   But only three simple words need translation in canvas, ""Edit"", ""Connect"", and ""Back"". Maybe we
   don't want to spend much time to solve this part."
1747307,2018-02-06 19:04:27 UTC,apport information
1747307,2018-02-06 19:04:25 UTC,apport information
1747307,2018-02-06 19:05:02 UTC,apport information
1747307,2018-02-06 19:05:00 UTC,apport information
1747307,2018-02-06 19:04:59 UTC,apport information
1747307,2018-02-06 19:04:57 UTC,apport information
1747307,2018-02-06 19:04:56 UTC,apport information
1747307,2018-02-06 19:04:55 UTC,apport information
1747307,2018-02-06 19:04:53 UTC,apport information
1747307,2018-02-06 19:04:52 UTC,apport information
1747307,2018-02-06 19:04:50 UTC,apport information
1747307,2018-02-06 19:04:47 UTC,apport information
1747307,2018-02-06 19:04:46 UTC,apport information
1747307,2018-02-06 19:08:48 UTC,"I followed the instructions in the comment above with ""apport-collect 1747307"", however, I opened the bug for network-manager, I'm not sure why there are two reports, one for network-manager and one for linux."
1747307,2018-02-06 19:04:45 UTC,apport information
1747307,2018-02-06 19:04:42 UTC,apport information
1747307,2018-02-06 19:04:41 UTC,apport information
1747307,2018-02-06 19:04:40 UTC,apport information
1747307,2018-02-06 19:04:38 UTC,apport information
1747307,2018-02-06 19:04:37 UTC,apport information
1747307,2018-02-06 19:04:36 UTC,apport information
1747307,2018-02-06 19:04:35 UTC,apport information
1747307,2018-02-06 19:04:34 UTC,apport information
1747307,2018-02-06 19:04:33 UTC,apport information
1747307,2018-02-06 19:04:31 UTC,apport information
1747307,2018-02-06 19:04:29 UTC,apport information
1747307,2018-02-06 19:04:43 UTC,apport information
1747307,2018-02-05 03:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1747307,2018-02-06 19:04:26 UTC,apport information
1747311,2018-02-07 07:22:06 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1747311,2021-01-10 18:01:43 UTC,"Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1273027, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find."
1747312,2018-02-05 08:28:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747312,2019-04-15 10:10:52 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates.
1747312,2019-06-15 04:17:23 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1747322,2020-01-06 11:00:00 UTC,"Hello,
4.13.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1747330,2018-02-05 06:19:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540722"
1747333,2018-02-05 02:43:53 UTC,This problem looks very similiar to https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543794
1747333,2018-02-05 22:18:05 UTC,"These are not AppArmor messages. AppArmor messages clearly say apparmor=""DENIED"" or apparmor=""ALLOWED"" or similar."
1747335,2018-02-06 10:02:02 UTC,"Change abandoned by Spencer Yu (<email address hidden>) on branch: master
Review: https://review.openstack.org/540702
Reason: Duplicated with https://review.openstack.org/#/c/541062/"
1747335,2018-02-05 03:04:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540702"
1747344,2018-02-05 04:16:23 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/540709"
1747344,2018-02-27 10:13:09 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/540709
Reason: @Takashi, docs and low-risk changes are fine in stable regardless of phase. The problem here is the change is not a backport, as Sylvain pointed out. Given there have been no updates, I'm going to abandon this."
1747344,2020-05-01 19:03:26 UTC,This bug was actually fixed in https://review.opendev.org/#/c/420060/
1747347,2018-02-05 04:34:18 UTC,This cloud is running juju 2.2.4-xenial-amd64
1747347,2018-08-07 04:45:22 UTC,Moved logs to pastebins for easier perusal.
1747347,2018-08-07 04:47:01 UTC,"Further to the above, this problem is still occurring and causing rabbitmq crashes.  Juju unit logs show this on leader: https://pastebin.canonical.com/p/m4WcRrnhDr/ and this on non-leaders: https://pastebin.canonical.com/p/hs9NKfZ59z/"
1747347,2019-05-13 06:25:38 UTC,"Is it possible to get a reproducer bundle? Alternately, would a bundle like:"
1747357,2018-02-19 20:18:51 UTC,"This will be due to the way we update the controllers file atomically, but writing a new temp file and moving into place. We should look into this a bit deeper."
1747357,2018-02-20 08:34:31 UTC,"It seems like it would be possible to do a chown while we're creating the
temporary file (make sure it has the same owner and permissions as the
original file before we rename it into place)."
1747362,2018-06-06 05:36:40 UTC,fix merged:https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/398396
1747374,2018-02-08 12:20:26 UTC,"Reviewed:  https://review.openstack.org/540766
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=9c095cc4db3eccb6c2fefc6df01e46af0925cc01
Submitter: Zuul
Branch:    master"
1747374,2018-02-10 18:03:24 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/543133"
1747374,2018-02-11 06:16:36 UTC,"Reviewed:  https://review.openstack.org/543133
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=aec9681c44c1f03d4efa12734fadfa2f06197862
Submitter: Zuul
Branch:    stable/queens"
1747374,2018-07-30 15:55:10 UTC,This issue was fixed in the openstack/zun 2.0.0 release.
1747374,2018-08-20 18:31:40 UTC,This issue was fixed in the openstack/zun 1.0.1 release.
1747377,2018-04-15 10:37:42 UTC,Duplicate of https://bugs.launchpad.net/kazam/+bug/1500083
1747382,2018-02-05 10:04:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747382,2018-02-05 09:32:23 UTC,"root@cloud-nine-141:/var/lib/cloud#  lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu Bionic Beaver (development branch)
Release:	18.04
Codename:	bionic"
1747382,2018-02-05 10:01:33 UTC,"root@cloud-nine-141:/var/lib/cloud# apt-cache policy cloud-init
cloud-init:
  Installed: 17.2-13-g6299e8d0-0ubuntu1
  Candidate: 17.2-13-g6299e8d0-0ubuntu1
  Version table:
 *** 17.2-13-g6299e8d0-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status"
1747384,2018-05-10 15:17:18 UTC,"I can't close this as invalid, but with a ceph config change rgw accepts and uses the `/v1/a/c/o` format."
1747384,2018-02-05 09:56:30 UTC,"I guess it's either a ironic bug, or swiftclient bug. Looks you've got the answer. Hope someone from swiftclien team would work on it :)"
1747384,2018-05-09 14:35:14 UTC,https://github.com/openstack/python-swiftclient/commit/4c955751d340a8f71a2eebdb3c58d90b36874a66#diff-65fb059e01befb2bd60268c230a0c989R103
1747384,2018-05-09 15:07:09 UTC,"/v1/container/object is not a valid Swift URL for temporary URLs. (Pedantically, it *is* a valid url, but it refers to an account named ""container"" and a container named ""object"".) Temporary URLs must refer to a specific object or a set of objects with a common prefix. This requires the signed URL to be of the form `/v1/{acct}/{container}/{object or prefix}`."
1747384,2018-05-09 15:08:08 UTC,tempurl client usage docs: https://docs.openstack.org/swift/latest/middleware.html#client-usage
1747388,2018-02-05 11:25:23 UTC,"Ok so the charm is a convenient place to hotfix this for an impacted deployment, but the right place to fix this is actually in the udev package so switching the bug task to the right target."
1747390,2018-05-02 06:35:20 UTC,Similar issue while upgrading Ubuntu Mate from 16.04 to 18.04.
1747394,2018-02-05 10:42:01 UTC,"StacktraceTop:
 xmlHashLookup3__internal_alias (name3=0x0, name2=0x0, name=name@entry=0x7ff8c4013030 ""http://www.w3.org/2001/XMLSchema-datatypes"", table=0x7ff8c4009f00) at ../../hash.c:765
 xmlHashLookup__internal_alias (table=0x7ff8c4009f00, name=name@entry=0x7ff8c4013030 ""http://www.w3.org/2001/XMLSchema-datatypes"") at ../../hash.c:448
 xmlRelaxNGParseData (node=0x7ff8c403a370, ctxt=0x7ff8c4008c40) at ../../relaxng.c:3648
 xmlRelaxNGParsePattern (ctxt=ctxt@entry=0x7ff8c4008c40, node=node@entry=0x7ff8c403a370) at ../../relaxng.c:4961
 xmlRelaxNGParsePatterns (ctxt=ctxt@entry=0x7ff8c4008c40, nodes=0x7ff8c403a370, group=group@entry=0) at ../../relaxng.c:5539"
1747394,2018-02-05 11:25:33 UTC,"Hi Sosha,
the crash itself is in libxml2 so I add a bug task for that."
1747404,2020-08-09 22:39:17 UTC,contact:   https://get.slack.help/hc/en-us
1747404,2019-09-25 06:10:32 UTC,This issue has resolved itself and I haven't seen it happen in any current Ubuntu releases. Ubuntu 17.10 is also no longer supported so I guess this can be closed.
1747415,2020-02-18 19:04:54 UTC,"We used this setting to turn off holds for a location who is going through a short term no notice closing.
Patrons who had the location pre-existing as their preferred pickup location see that it looks ok, but then the hold simply doesn't go through.  Desired behavior would be an error message Hold Not Placed library is not a pickup location.  Perhaps with a suggestion to select another pickup location."
1747416,2018-02-12 15:45:50 UTC,the corresponding e.u.c report is on https://errors.ubuntu.com/problem/d3f3e3ff370d0cf25934939053f8c1c7b0781489
1747416,2018-02-12 14:48:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747416,2018-02-12 15:40:13 UTC,"Those reports are a bit confusing, it's like the gsettings schemas didn't include the new emojs key but the ibus package installed is the new/correct version and there doesn't seem to be a local installation taking over it in the procmaps table ... Could anyone having the issue help debugging?"
1747416,2018-02-05 12:55:33 UTC,"StacktraceTop:
 g_settings_set_property (object=0x560dfb6a1750, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at ../../../../gio/gsettings.c:590
 object_set_property (nqueue=0x560dfb71cd60, value=<optimized out>, pspec=0x560dfb6dcee0, object=0x560dfb6a1750) at ../../../../gobject/gobject.c:1439
 g_object_new_internal (class=class@entry=0x560dfb727b10, params=params@entry=0x7ffd35404e20, n_params=n_params@entry=1) at ../../../../gobject/gobject.c:1831
 g_object_new_valist (object_type=94618053194976, first_property_name=first_property_name@entry=0x7f93a102bbc0 ""schema-id"", var_args=var_args@entry=0x7ffd35404f70) at ../../../../gobject/gobject.c:2120
 g_object_new (object_type=<optimized out>, first_property_name=first_property_name@entry=0x7f93a102bbc0 ""schema-id"") at ../../../../gobject/gobject.c:1640"
1747435,2018-02-05 14:13:39 UTC,Right after opening the bug I saw that it is already fixed in master... Sorry.
1747441,2018-02-14 06:54:31 UTC,The bug seems to be corrected in 4.13.0-33. Please mark the bug as attended from -33. / Gunnar
1747441,2019-04-17 06:08:20 UTC,"Hello Gunnar,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?
Thanks"
1747441,2019-06-17 04:17:27 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1747445,2019-06-01 05:50:08 UTC,"Hi, seems the router information in context should be inside the ""network"" key:
""context"": {
        ""network"": {
          ""router"": {
            ""external_gateway_info"": {
              ""network_id"": 6e077c4c-f081-470a-8d9c-3260bd597350
            }
          }
        }
      }"
1747450,2021-01-10 18:44:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1581312, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1747457,2018-07-09 04:25:28 UTC,"We could alternatively provide a different value for affinity, because it
wouldn't be available for things that aren't lxd containers. I don't really
like that LXD uses ""cpu=X"" to mean something very different (IMO) to
""cpu=X-Y"" (a count, vs an explicit enumeration of cpu identities.)"
1747457,2018-03-08 15:58:10 UTC,I discussed this with @thumper and model-config is not an option.
1747457,2018-02-07 05:32:49 UTC,This is not something that we have plans to address immediately. It may be addressed at the time when we do more comprehensive work on inheriting container properties.
1747457,2018-07-08 17:11:41 UTC,The first support for LXD constraints has been committed to the develop and 2.4 branches.
1747458,2019-09-19 11:57:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1747458,2019-09-20 11:45:44 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1747458,2018-02-05 16:44:18 UTC,How long did you wait to make the determination that the service crash wasn't noticed by MAAS?
1747459,2018-02-05 16:43:10 UTC,How long did you wait to make the determination that the service crash wasn't noticed by MAAS?
1747459,2018-02-05 16:55:22 UTC,I believe there is a 30 second delay.
1747459,2018-02-05 17:06:29 UTC,"Ok, I waited 19 minutes, which isn't never but it's never-ish."
1747459,2018-02-05 17:17:00 UTC,19 minutes seems long enough ;-)
1747459,2018-02-21 00:14:18 UTC,I can confirm this is also the other way around.
1747459,2018-04-10 20:25:55 UTC,I have been trying to reproduce this with latest master that includes https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/342811 which I believe was the actual cause of this issue.
1747463,2017-02-15 20:41:34 UTC,"The BIOS is really primitive, there is nearly nothing regarding HW that can be changed :-/. I can continue to use iommu=off, it seems to be fine.
Thanks"
1747463,2018-05-15 08:03:32 UTC,Adding Tom.
1747463,2018-06-21 18:15:50 UTC,4.18 rc1 + mem_encrypt=off
1747463,2018-06-21 18:14:45 UTC,4.18 rc1
1747463,2018-06-21 18:14:03 UTC,The attached screenshots are the result of booting 4.18 rc1 kernel
1747463,2018-05-16 17:16:18 UTC,"@Peridot,
Request from Upstream:"
1747463,2018-05-16 11:59:03 UTC,I tested with 4.17 rc4 and the problem persists
1747463,2018-05-15 14:48:11 UTC,"@Peridot,  I know you responded that the current mainline kernel still exhibits the bug on IRC.  However, could you also add that test result to this bug report for upstream tracking?"
1747463,2018-05-15 14:47:13 UTC,"On 05/15/2018 09:08 AM, Tom Lendacky wrote:

> On 5/15/2018 7:34 AM, Nath, Arindam wrote:
>>
>>> -----Original Message-----
>>> From: Joseph Salisbury [mailto:<email address hidden>]
>>> Sent: Tuesday, May 15, 2018 5:40 PM
>>> To: Nath, Arindam <email address hidden>
>>> Cc: <email address hidden>; Bridgman, John
>>> <email address hidden>; joro@8bytes.org; amd-
>>> <email address hidden>; <email address hidden>; <email address hidden>;
>>> Suthikulpanit, Suravee <email address hidden>; Deucher,
>>> Alexander <email address hidden>; Kuehling, Felix
>>> <email address hidden>; <email address hidden>; <email address hidden>;
>>> <email address hidden>; Lendacky, Thomas
>>> <email address hidden>
>>> Subject: Re: iommu/amd: flush IOTLB for specific domains only (v2)
>>>
>>> On 05/15/2018 04:03 AM, Nath, Arindam wrote:
>>>> Adding Tom.
>>>>
>>>> Hi Joe,
>>>>
>>>> My original patch was never accepted. Tom and Joerg worked on another
>>> patch series which was supposed to fix the issue in question in addition to do
>>> some code cleanups. I believe their patches are already in the mainline. If I
>>> remember correctly, one of the patches disabled PCI ATS for the graphics
>>> card which was causing the issue.
>>>> Do you still see the issue with latest mainline kernel?
>>>>
>>>> BR,
>>>> Arindam
>>>>
>>>> -----Original Message-----
>>>> From: Joseph Salisbury [mailto:<email address hidden>]
>>>> Sent: Tuesday, May 15, 2018 1:17 AM
>>>> To: Nath, Arindam <email address hidden>
>>>> Cc: <email address hidden>; Bridgman, John
>>>> <email address hidden>; joro@8bytes.org;
>>>> <email address hidden>; <email address hidden>;
>>> <email address hidden>;
>>>> Suthikulpanit, Suravee <email address hidden>; Deucher,
>>>> Alexander <email address hidden>; Kuehling, Felix
>>>> <email address hidden>; <email address hidden>; <email address hidden>;
>>>> <email address hidden>
>>>> Subject: iommu/amd: flush IOTLB for specific domains only (v2)
>>>>
>>>> Hello Arindam,
>>>>
>>>> There is a bug report[0] that you created a patch[1] for a while back.
>>> However, the patch never landed in mainline.  There is a bug reporter in
>>> Ubuntu[2] that is affected by this bug and is willing to test the patch.  I
>>> attempted to build a test kernel with the patch, but it does not apply to
>>> currently mainline cleanly.  Do you still think this patch may resolve this
>>> bug?  If so, is there a version of your patch available that will apply to current
>>> mainline?
>>>> Thanks,
>>>>
>>>> Joe
>>>>
>>>> [0] https://bugs.freedesktop.org/show_bug.cgi?id=101029
>>>> [1] https://patchwork.freedesktop.org/patch/157327/
>>>> [2] http://pad.lv/1747463
>>>>
>>> Hi Arindam,
>>>
>>> Thanks for the feedback.  Yes, the latest mainline kernel was tested, and it is
>>> reported the bug still happens in the Ubuntu kernel bug[0]. Is there any
>>> specific diagnostic info we can collect that might help?
>> Joe, I believe all the information needed is already provided in [2]. Let us wait for inputs from Tom and Joerg.
>>
>> I could take a look at the issue locally, but it will take me some really long time since I am occupied with oth...
"
1747463,2018-05-15 12:34:59 UTC,"> -----Original Message-----
> From: Joseph Salisbury [mailto:<email address hidden>]
> Sent: Tuesday, May 15, 2018 5:40 PM
> To: Nath, Arindam <email address hidden>
> Cc: <email address hidden>; Bridgman, John
> <email address hidden>; joro@8bytes.org; amd-
> <email address hidden>; <email address hidden>; <email address hidden>;
> Suthikulpanit, Suravee <email address hidden>; Deucher,
> Alexander <email address hidden>; Kuehling, Felix
> <email address hidden>; <email address hidden>; <email address hidden>;
> <email address hidden>; Lendacky, Thomas
> <email address hidden>
> Subject: Re: iommu/amd: flush IOTLB for specific domains only (v2)
>
> On 05/15/2018 04:03 AM, Nath, Arindam wrote:
> > Adding Tom.
> >
> > Hi Joe,
> >
> > My original patch was never accepted. Tom and Joerg worked on another
> patch series which was supposed to fix the issue in question in addition to do
> some code cleanups. I believe their patches are already in the mainline. If I
> remember correctly, one of the patches disabled PCI ATS for the graphics
> card which was causing the issue.
> >
> > Do you still see the issue with latest mainline kernel?
> >
> > BR,
> > Arindam
> >
> > -----Original Message-----
> > From: Joseph Salisbury [mailto:<email address hidden>]
> > Sent: Tuesday, May 15, 2018 1:17 AM
> > To: Nath, Arindam <email address hidden>
> > Cc: <email address hidden>; Bridgman, John
> > <email address hidden>; joro@8bytes.org;
> > <email address hidden>; <email address hidden>;
> <email address hidden>;
> > Suthikulpanit, Suravee <email address hidden>; Deucher,
> > Alexander <email address hidden>; Kuehling, Felix
> > <email address hidden>; <email address hidden>; <email address hidden>;
> > <email address hidden>
> > Subject: iommu/amd: flush IOTLB for specific domains only (v2)
> >
> > Hello Arindam,
> >
> > There is a bug report[0] that you created a patch[1] for a while back.
> However, the patch never landed in mainline.  There is a bug reporter in
> Ubuntu[2] that is affected by this bug and is willing to test the patch.  I
> attempted to build a test kernel with the patch, but it does not apply to
> currently mainline cleanly.  Do you still think this patch may resolve this
> bug?  If so, is there a version of your patch available that will apply to current
> mainline?
> >
> > Thanks,
> >
> > Joe
> >
> > [0] https://bugs.freedesktop.org/show_bug.cgi?id=101029
> > [1] https://patchwork.freedesktop.org/patch/157327/
> > [2] http://pad.lv/1747463
> >
> Hi Arindam,
>
> Thanks for the feedback.  Yes, the latest mainline kernel was tested, and it is
> reported the bug still happens in the Ubuntu kernel bug[0]. Is there any
> specific diagnostic info we can collect that might help?
"
1747463,2018-05-15 12:10:03 UTC,"On 05/15/2018 04:03 AM, Nath, Arindam wrote:

> Adding Tom.
>
> Hi Joe,
>
> My original patch was never accepted. Tom and Joerg worked on another patch series which was supposed to fix the issue in question in addition to do some code cleanups. I believe their patches are already in the mainline. If I remember correctly, one of the patches disabled PCI ATS for the graphics card which was causing the issue.
>
> Do you still see the issue with latest mainline kernel?
>
> BR,
> Arindam
>
> -----Original Message-----
> From: Joseph Salisbury [mailto:<email address hidden>]
> Sent: Tuesday, May 15, 2018 1:17 AM
> To: Nath, Arindam <email address hidden>
> Cc: <email address hidden>; Bridgman, John <email address hidden>; joro@8bytes.org; <email address hidden>; <email address hidden>; <email address hidden>; Suthikulpanit, Suravee <email address hidden>; Deucher, Alexander <email address hidden>; Kuehling, Felix <email address hidden>; <email address hidden>; <email address hidden>; <email address hidden>
> Subject: iommu/amd: flush IOTLB for specific domains only (v2)
>
> Hello Arindam,
>
> There is a bug report[0] that you created a patch[1] for a while back. However, the patch never landed in mainline.  There is a bug reporter in Ubuntu[2] that is affected by this bug and is willing to test the patch.  I attempted to build a test kernel with the patch, but it does not apply to currently mainline cleanly.  Do you still think this patch may resolve this bug?  If so, is there a version of your patch available that will apply to current mainline?
>
> Thanks,
>
> Joe
>
> [0] https://bugs.freedesktop.org/show_bug.cgi?id=101029
> [1] https://patchwork.freedesktop.org/patch/157327/
> [2] http://pad.lv/1747463
>


Hi Arindam,"
1747463,2018-05-14 19:46:50 UTC,"Hello Arindam,"
1747463,2018-05-14 16:17:50 UTC,"Can you see if this bug still exists in current mainline:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc5/"
1747463,2018-05-14 14:44:58 UTC,"The patch mentioned in the upstream bug report and comment #25 never landed in mainline.  I tried to apply it to Bionic, but it does not apply cleanly.  I'll work on back porting it.  I'll post a test kernel shortly.  We can then update upstream with testing results."
1747463,2018-02-10 13:37:56 UTC,"I don't see the patch is in upstream Linux though, so still worth a try."
1747463,2018-02-10 08:58:32 UTC,"The upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=101029 makes reference to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683184 which is marked as fix released, just a heads up."
1747463,2018-02-10 06:04:40 UTC,"Looks like there's a patch but not upstreamed yet,
https://patchwork.freedesktop.org/patch/157327/"
1747463,2018-06-21 18:16:32 UTC,4.18 rc1 + mem_encrypt=off
1747463,2018-02-09 19:03:26 UTC,Though with iommu=soft it boots on both kernels with IOMMU and AMD-v enabled in the BIOS
1747463,2018-06-21 18:17:16 UTC,4.18 rc1 + mem_encrypt=off
1747463,2019-03-21 08:59:30 UTC,"Hi,
  I still encounter a same issue concerned to ext4 fs corruption using linux kernels 4.19.16... 4.20.27 on HP laptop 17-ak041ur (2 pcs on hand)."
1747463,2019-07-12 08:05:49 UTC,"No, only pci=noats works"
1747463,2019-05-27 08:10:36 UTC,"I have the same issue on Radeon 570 4gb, Ryzen 1700, MSI Tomahawk on 18.04."
1747463,2019-04-11 09:43:57 UTC,"Created attachment 282309
dmesg for HP laptop 17-ak041ur with amdgpu.runpm=0 kernel parameter"
1747463,2019-04-11 09:41:37 UTC,"(In reply to Alex Deucher from comment #25)

> Does booting with amdgpu.runpm=0 on the kernel command line help?
"
1747463,2019-04-10 15:54:07 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=110360
1747463,2019-04-10 15:50:08 UTC,Does booting with amdgpu.runpm=0 on the kernel command line help?
1747463,2019-04-09 10:27:14 UTC,"I have also had this problem - MSI Tomahawk Arctic B350, ryzen 1700, vega 56 gpu
ubuntu 19.04 - ignores bios setting, attempts to boot, kernel panic with lots of AMD-Vi: Completion-Wait loop timed out"
1747463,2019-04-08 12:09:28 UTC,"(In reply to Nikolai from comment #17)

> Hi,
>   I still encounter a same issue concerned to ext4 fs corruption using linux
> kernels 4.19.16... 4.20.27 on HP laptop 17-ak041ur (2 pcs on hand).
>
>   Laptop configs are A6-9220 radeon r4 5 compute cores 2c+3g, 4G RAM, 200GB
> Intel SSD (1st laptop) or 500GB Toshiba HDD (2nd laptop)
"
1747463,2019-04-07 09:12:28 UTC,"I have the same issue, but with a Ryzen 7 1700 with the following setups:"
1747463,2019-03-26 14:24:06 UTC,"Created attachment 282037
lspci for HP laptop 17-ak041ur"
1747463,2019-03-26 14:23:13 UTC,"Created attachment 282035
lspci -v for HP laptop 17-ak041ur"
1747463,2019-03-26 13:08:31 UTC,(In reply to Nikolai from comment #17)
1747463,2019-03-21 13:53:40 UTC,"Created attachment 281949
HP laptop HW config via dmidecode"
1747463,2019-03-21 13:53:07 UTC,"Created attachment 281947
HP laptop dmesg output while IOMMU turned on, but no LAN cable"
1747463,2019-03-21 13:51:35 UTC,"Created attachment 281945
HP laptop dmesg output with plenty of errors while LAN cable present"
1747463,2018-06-21 18:55:08 UTC,"All the tests were done with iommu turned off and SVE turned on in the bios, and it does not boot without iommu=soft"
1747463,2018-02-09 19:02:04 UTC,And with the mainline kernel
1747463,2018-02-10 13:55:55 UTC,"I agree, I just meant that that bug might also be useful with debugging. It was closed because zesty reached EOL."
1747463,2018-02-09 17:44:16 UTC,Is AMD-V enabled in BIOS?
1747463,2017-06-30 16:38:48 UTC,Patch: https://patchwork.freedesktop.org/patch/157327/
1747463,2017-06-30 15:59:08 UTC,Same issue persists on HP 15-ba028ur using latest mainline kernel. (4.12-rc7)
1747463,2018-02-09 19:01:27 UTC,AMD-v was not enabled but with it enabled booting without iommu=soft results in a crash that only lasts about a second and then loses HDMI connection. This is with the Ubuntu Kernel
1747463,2017-02-13 20:32:12 UTC,"Created attachment 254739
drm-next-4.11-wip:  boot into emergency mode - crash after modprobe amdgpu"
1747463,2017-02-13 03:25:42 UTC,"Stock kernels have very little amdgpu driver code, see kernel.org and click diff. You have very new amd gpu so Use the command:
git clone -b drm-next-4.11-wip git://people.freedesktop.org/~agd5f/linux"
1747463,2017-02-10 18:39:04 UTC,"Created attachment 254697
logged using netconsole - 4.10.0rc6, gpu turned off using acpi_call  -> crash"
1747463,2017-02-10 18:37:59 UTC,"Created attachment 254695
logged using netconsole - 4.10.0rc6 with  iommu=off, gpu turned off using acpi_call"
1747463,2018-02-05 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1747463,2017-02-10 18:36:11 UTC,"I tried kernel 4.10.0-rc6-amd64 from Debian experimental archive and the result is very similar. To minimize harm on filesystem I booted into emergency mode with read-only file-system and tried to switch off GPU using ACPI call. There is some warning during call, but something happened :)"
1747463,2017-02-09 12:07:28 UTC,Do you have the amdgpu firmware installed?
1747463,2017-02-08 21:09:53 UTC,"Created attachment 254661
crash logged using netconsole"
1747463,2017-02-08 20:52:17 UTC,"Created attachment 254651
/proc/cpuinfo"
1747463,2017-02-08 20:48:42 UTC,"Created attachment 254641
lspci -vvv"
1747463,2017-02-08 20:37:02 UTC,"Created attachment 254631
iommu=off - no crash"
1747463,2017-02-08 20:35:58 UTC,"Created attachment 254621
nomodeset - no crash"
1747463,2017-02-08 20:32:58 UTC,"Created attachment 254611
crash logged using netconsole"
1747463,2017-02-09 23:34:15 UTC,"Doubt the problem is in the amdgpu driver. What about bug in the amd_iommu?
I think this because I tried to switch off external GPU using acpi_call module.
The following command was successful:"
1747463,2018-02-05 18:02:19 UTC,apport information
1747463,2017-02-14 07:56:09 UTC,"Comment on attachment 254739
drm-next-4.11-wip:  boot into emergency mode - crash after modprobe amdgpu"
1747463,2018-02-05 18:02:22 UTC,apport information
1747463,2018-02-09 17:23:13 UTC,"I found it also boots with IOMMU turned on in the bios as long as you set iommu=soft, both with the ubuntu kernel and the mainline kernel."
1747463,2018-02-09 11:25:38 UTC,When I exit the above pictured initram prompt I get a full crash.
1747463,2018-02-09 11:24:18 UTC,this is the result of booting with the upstream kernel with IOMMU turned on in the bios
1747463,2018-02-05 18:02:20 UTC,apport information
1747463,2018-02-05 18:02:40 UTC,apport information
1747463,2018-02-05 18:02:39 UTC,apport information
1747463,2018-02-05 18:02:35 UTC,apport information
1747463,2018-02-08 17:01:19 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1747463,2018-02-05 18:02:33 UTC,apport information
1747463,2018-02-05 18:02:30 UTC,apport information
1747463,2018-02-05 18:02:29 UTC,apport information
1747463,2018-02-05 18:02:27 UTC,apport information
1747463,2018-02-05 18:02:25 UTC,apport information
1747463,2018-02-05 18:02:24 UTC,apport information
1747463,2018-02-05 18:02:23 UTC,apport information
1747463,2018-02-05 18:02:34 UTC,apport information
1747464,2019-05-15 02:49:42 UTC,still a pain in the *** every ***ing kernel bump on ec2
1747464,2020-10-09 19:26:21 UTC,"Hi, going through old bugs right now."
1747464,2020-02-06 23:20:46 UTC,"Many packages uses ucf to identify config changes, which can trigger prompts like this during upgrade.  In theory these are to prevent overwriting local changes, but in practice there can be false-positives depending on how the package implements ucf.  In the case of openssh, for example, it uses a list of md5sums of ""known stock"" config files to clue itself in on ignorable changes (see LP: #1861472)."
1747464,2018-11-27 15:56:26 UTC,"Ubuntu-devel-discuss Digest, Vol 144, Issue 13 responded that my problem could be caused by this bug. It would be Ubuntu 18.04 on DigitalOcean, the symptom being that apt updates were attempting to overwrite php.ini and asking about GRUB. I have no more information, this is FYI, feel free to close."
1747464,2019-09-11 20:08:11 UTC,The only thing that has helped without interaction is thus far is from this comment <https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1323772/comments/5>:
1747466,2018-02-12 22:22:43 UTC,"TheJulia sez: I'm good without a spec as long as there are not any additional mechanics to reach out to swift. If it works like the existing client for generation then \o/. Reaching out might require more, and even with some lightweight client driven mechanics, I don't think it really needs a spec, it is just an additional capability in my mind."
1747466,2018-02-12 22:37:18 UTC,"I'm good with this, with similar caveats to TheJulia in comment #1. There is no API change, and I don't think we need a config change. (Hmm, if a config change is needed, then we need to discuss...)"
1747475,2018-02-06 17:35:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541382"
1747475,2018-02-06 14:40:37 UTC,I don't think zuul test the clustering.
1747476,2018-02-07 16:38:22 UTC,I'm on kubuntu bionic daily. Somewhere along the line something depends on the non python3 version it seems.
1747476,2018-02-07 16:08:42 UTC,Which release of Ubuntu is this? The depends for apport are correct in bionic and have not change recently as far as I know.
1747482,2019-10-08 15:13:43 UTC,"Hello,"
1747484,2018-02-07 04:25:27 UTC,"Updates:
I just confirmed, The master branch as of 2 February have changed the document(help) and new document explicitly mentioned ""enable_new_services"" is for only nova-compute."
1747484,2018-02-05 18:36:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/540962"
1747485,2021-02-12 21:46:05 UTC,"As of 3.6, this appears to be default to workstation the first time this interface is retrieved."
1747485,2021-02-12 21:47:39 UTC,"(also it is behaving correctly in the sense that if you go to the interface for the first time and it defaults to BR1, only BR1's subscriptions are displaying)"
1747494,2018-03-06 10:21:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747496,2018-06-07 14:48:30 UTC,"Reviewed:  https://review.openstack.org/553072
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f02b3800051234ecc14f3117d5987b1a8ef75877
Submitter: Zuul
Branch:    master"
1747496,2018-06-26 07:30:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/578010"
1747496,2018-07-08 04:25:00 UTC,"Reviewed:  https://review.openstack.org/578010
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=127dd738c0ec67f3559774bae83dd8872e616991
Submitter: Zuul
Branch:    stable/queens"
1747496,2018-03-14 21:07:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553072"
1747496,2018-04-23 16:11:38 UTC,"Please Sean, reassign yourself to the bug. It seems that I can't do that for you."
1747496,2018-02-06 11:20:46 UTC,ill try an fix this week or before the ptg if i get delayed.
1747496,2018-02-05 19:45:48 UTC,"the simple fix is to add a new fucntion to the desinger.py and invoke it here
https://github.com/openstack/nova/blob/58328627f56379f1fd80ffbfca186262d578bc9f/nova/virt/libvirt/vif.py#L239"
1747496,2018-03-12 17:56:39 UTC,FYI i am just getting around to starting this. i have set up a dev env to reporduce and will be working on the libvirt driver xml change first which is back portable followed possibly by delegating the plugin to os-vif which is not backportable.
1747497,2018-02-05 19:41:23 UTC,"StacktraceTop:
 g_settings_set_property (object=0x55e71ed278d0, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at ../../../../gio/gsettings.c:590
 object_set_property (nqueue=0x55e71ed21370, value=<optimized out>, pspec=0x55e71ed11b10, object=0x55e71ed278d0) at ../../../../gobject/gobject.c:1439
 g_object_new_internal (class=class@entry=0x55e71ec81ab0, params=params@entry=0x7ffc3f1a6ee0, n_params=n_params@entry=1) at ../../../../gobject/gobject.c:1831
 g_object_new_valist (object_type=94451137348496, first_property_name=<optimized out>, var_args=var_args@entry=0x7ffc3f1a7030) at ../../../../gobject/gobject.c:2120
 g_object_new (object_type=<optimized out>, first_property_name=<optimized out>) at ../../../../gobject/gobject.c:1640"
1747498,2018-02-07 14:48:35 UTC,This looks to me like an underlying network issue. The error in the charm occurred at 08:16:06. The mysql/0:/var/log/mysql/error.log shows mysql terminating at this time with an error that appears to be synonymous with a split brain ( https://severalnines.com/blog/become-mysql-dba-blog-series-troubleshooting-galera-cluster-issues-part-1 ).
1747498,2018-02-07 17:00:59 UTC,I think https://bugs.launchpad.net/charm-percona-cluster/+bug/1746524/comments/6 applies to this bug too
1747498,2019-05-13 06:32:18 UTC,"Given the lack of updates or response to @gnuoy's observation about networking / percona network partitioning, I'm marking this as incomplete unless we have a new reproducer where we don't see these issues."
1747498,2019-07-13 04:17:55 UTC,[Expired for OpenStack percona-cluster charm because there has been no activity for 60 days.]
1747499,2018-02-05 21:23:23 UTC,"The position of the Security Team has been consistent that kernel live patching allows users to defer reboots, it does not allow users to avoid them.  Because not all security fixes are included in live patches, and because correlating the live patch CVEs to the kernel deb CVEs requires knowledge that's external to the packages themselves, hiding the 'reboot required' message will give users a false sense of security about their system."
1747499,2018-02-06 11:44:39 UTC,I think we can agree that the MOTD messaging gets confusing. The best way to fix it is the question.
1747499,2020-05-15 01:56:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747499,2020-05-15 03:26:22 UTC,"Actually, I think there's more to it. Here are some thoughts"
1747499,2020-05-15 03:43:43 UTC,I agree with comment #4.
1747499,2020-05-15 15:43:22 UTC,Here are some extra details about the status of livepatch when a kernel upgrade is required.
1747499,2020-07-07 16:36:11 UTC,I think the problem is that external tools just simplistically look at /var/run/reboot-required to decide whether to reboot and I don't think we can expect them to be fixed just to handle livepatch.
1747501,2020-06-23 17:22:01 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/547290"
1747510,2018-02-05 20:53:46 UTC,I think we may also need to do this for neutron-lib
1747519,2018-02-07 00:31:41 UTC,This is a side-effect of how presence is currently implemented.
1747526,2018-06-10 23:33:21 UTC,In PNS::JOINT::IsLineCorner() we have:
1747526,2018-04-30 19:27:11 UTC,"Brand new nightly r10202 still does the same.
The connecting point of two different width track is ""virtually unmovable"".
Would you check this report?
It's only my mania to make tracks wider where there is spare space.
E.g I prefer 8 mil tracks coming from of 0.5mm pitch part to continue as 12 or 20 mil tracks.
It's more fail-safe when manual soldering too long/too hot."
1747527,2020-07-23 08:56:30 UTC,Can confirm the same on Firefox 78.0.2
1747528,2018-02-06 22:51:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541482"
1747528,2019-05-14 20:18:45 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.opendev.org/541482
Reason: This patch has been stale for awhile now. Moving it to abandoned to clean-up the queue. If this patch is still active, please push an update to it."
1747534,2018-02-08 23:26:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/542485"
1747534,2018-08-31 07:43:39 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1747534,2018-08-31 07:43:48 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/542485
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1747542,2018-02-06 00:03:06 UTC,Here ya go:
1747542,2018-05-17 14:42:16 UTC,"I'm really going to test it this time, I promise. :)"
1747542,2018-05-23 19:08:47 UTC,"Looks like we're using LOST and not LONGOVERDUE, so there's no way for us to really test this."
1747542,2019-08-02 15:03:08 UTC,Works for me. Signoff branch is working/user/gmcharlt/lp1747542_signoff.
1747542,2020-07-24 13:57:21 UTC,"Pushed to rel_3_4, rel_3_5, and master. Thanks Chris and Galen!"
1747543,2018-02-06 12:52:56 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-February/090022.html
1747543,2018-02-21 19:09:21 UTC,This bug was fixed in the package linux-azure - 4.13.0-1011.14
1747548,2019-08-14 12:36:12 UTC,@ivve - please provide the regiond.log that will show the traceback to help diagnose the issue.
1747548,2020-02-25 09:49:28 UTC,It's not possible to see what's going on with the attached regiond.log.
1747548,2019-08-14 08:35:35 UTC,"Hi, I'm seeing this on 2.6.0 during deployment of 1 machine (at a time)."
1747548,2020-05-28 04:17:16 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1747548,2020-03-28 15:08:41 UTC,"Hello,
I've recently installed snap maas 2.7 and encounter the same problem:
2020-03-28T13:23:50+00:00 S4 cloud-init[1090]: Failed installing package(s) for smartctl-validate (id: 98, script_version_id: 1)
2020-03-28T13:24:55+00:00 S4 cloud-init[1090]: request to http://192-168-1-0--24.maas-internal:5248/MAAS/metadata/2012-03-01/ failed. sleeping 1.: HTTP Error 500: Internal Server Error
2020-03-28T13:24:55+00:00 S4 cloud-init[1090]: request to http://192-168-1-0--24.maas-internal:5248/MAAS/metadata/2012-03-01/ failed. sleeping 1.: HTTP Error 500: Internal Server Error"
1747548,2019-04-03 22:24:43 UTC,I'm seeing this on 2.5.2
1747548,2018-02-06 01:14:56 UTC,Attaching cloud-init-output.log file for commissioned machine.
1747548,2018-02-06 01:17:09 UTC,"I've also noticed if I run it a few times it sometimes eventually completes, so I'm wondering if this is some kind of timing issue, or race condition or something."
1747548,2018-02-06 01:14:12 UTC,"> Can you confirm that your storage devices have been discovered successfully?
"
1747548,2018-02-06 00:18:58 UTC,"Hi Brad,"
1747548,2018-04-23 18:11:54 UTC,"Hi Brad,"
1747550,2018-08-30 05:26:06 UTC,"Change abandoned by Eric Xie (eric_xiett@163.com) on branch: master
Review: https://review.openstack.org/541084"
1747558,2018-08-25 22:01:33 UTC,"I tested some more JPG images from two different Android smartphones and I experiencing the same problem. These smartphones were upgraded some weeks ago and I think the problem is related to its Android version. Old JPG images are ok, but newer not."
1747558,2018-08-25 21:23:51 UTC,I'm sorry! Browsers use also libjpeg8 because they use libgdk-pixbuf2.0-0 and ...
1747558,2018-08-25 21:14:55 UTC,"The string ""Premature end of JPEG file"" showed by gimp and imagemagick utilities (identify, convert) is present on libjpeg8 code (taken from http://ijg.org/files/)"
1747558,2018-08-23 19:58:41 UTC,I tried many viewers. Some of them worked. I configured eog (Eye of Gnome) as my default viewer as work-around.
1747558,2018-08-23 17:08:37 UTC,Lubuntu 16.04 LTS 64 bit up-to-date
1747558,2018-04-21 08:16:52 UTC,"This bug also affects Lubuntu Bionic amd64 (64-bit), soon released as Lubuntu 18.04 LTS."
1747558,2018-08-25 21:39:27 UTC,"I found that, in fact, libjpeg8 is only a dependency package for libjpeg-turbo8."
1747558,2018-04-16 14:00:44 UTC,This bug affects my Lubuntu 16.04 LTS (32-bit) and its default gpicview. But it also affects ristretto (with the same complaint)
1747558,2018-04-16 13:54:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747558,2018-04-16 13:18:52 UTC,"As of Lubuntu 18.04 32bit beta 2, the attached image file now opens fine in mtpaint, but still refuses to open in Lubuntu's default image viewer, with the same error message as above."
1747558,2018-02-23 14:05:11 UTC,"It seems this bug affects more than one program in the Lubuntu daily build (same build as initial bug reported from). When I try and open the same JPG image file (attached to this bug report) in mtPaint 3.40, an error message simply says 'cannot open file'."
1747558,2018-04-21 07:56:33 UTC,Interesting idea. Any ideas on how we might isolate / identify the library in question to test further?
1747562,2018-02-15 23:53:14 UTC,This issue was fixed in the openstack/nova 16.1.0 release.
1747562,2018-02-09 04:54:58 UTC,"Reviewed:  https://review.openstack.org/542270
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=307975ae4818ea5a510cfcb01bdb1f37fa563109
Submitter: Zuul
Branch:    stable/pike"
1747562,2018-02-08 15:50:04 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/542270"
1747562,2018-02-09 07:13:15 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc1 release candidate.
1747562,2018-02-06 03:44:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541116"
1747562,2018-02-07 05:08:29 UTC,"Reviewed:  https://review.openstack.org/541116
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=26de90a14d527ae18dd6cd39d4fdf589dd449fb6
Submitter: Zuul
Branch:    master"
1747567,2018-02-06 04:10:58 UTC,"StacktraceTop:
 g_datalist_id_dup_data (datalist=0x557b511cda70, key_id=59, dup_func=dup_func@entry=0x0, user_data=user_data@entry=0x0) at ../../../../glib/gdataset.c:858
 g_datalist_id_get_data (datalist=<optimized out>, key_id=<optimized out>) at ../../../../glib/gdataset.c:798
 g_weak_ref_set (weak_ref=weak_ref@entry=0x557b51216a70, object=object@entry=0x0) at ../../../../gobject/gobject.c:4427
 g_weak_ref_clear (weak_ref=0x557b51216a70) at ../../../../gobject/gobject.c:4332
 g_settings_backend_invoke_closure (user_data=0x557b50f68c80) at ../../../../gio/gsettingsbackend.c:275"
1747571,2018-02-06 05:19:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541130"
1747571,2020-05-28 16:20:10 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: master
Review: https://review.opendev.org/541130
Reason: Project retirement"
1747576,2018-02-07 07:20:58 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1747576,2018-02-07 08:15:35 UTC,Please give a solution for solving this bugs....
1747591,2018-05-11 06:29:16 UTC,we need add a functional test for it if possible ...
1747591,2018-05-11 09:16:18 UTC,"In wsgi code, we have handler about this:"
1747597,2018-02-08 17:15:13 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1747597,2018-02-06 08:56:00 UTC,apport information
1747597,2018-02-06 08:56:01 UTC,apport information
1747597,2018-02-09 07:39:03 UTC,"I installed the 4.15.0-041500-generic kernel, and the machine failed to reboot, unfortunately this is a remote machine."
1747597,2018-02-23 09:26:33 UTC,"I've got 4 computers running ubuntu.
2 computers affected, and 2 computers unaffected. The two affected computer are using btrfs."
1747597,2018-02-09 15:10:37 UTC,"As requested, I added the tag kernel-bug-exists-upstream and changed the status to confirmed"
1747597,2018-02-19 09:59:49 UTC,4.16.0-041600rc2-generic is also affected.
1747597,2018-02-19 13:41:36 UTC,"I'm trying to bisect the bug, but I have some problem doing it."
1747597,2018-02-06 08:55:59 UTC,apport information
1747597,2018-02-09 15:07:26 UTC,"using the 4.15.0-041500-generic kernel, the total process count was very high (473) just after the boot, perhaps something to do with the raid array resync."
1747597,2018-02-06 08:55:58 UTC,apport information
1747597,2018-02-06 08:55:54 UTC,apport information
1747597,2018-02-06 08:55:55 UTC,apport information
1747597,2018-02-06 08:55:57 UTC,apport information
1747597,2018-02-06 08:45:37 UTC,"apport-collect 1747597 fails with ""Bad bot, go away!"""
1747597,2018-02-06 08:55:50 UTC,apport information
1747597,2018-02-06 08:55:51 UTC,apport information
1747597,2018-02-06 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1747597,2018-02-06 08:55:53 UTC,apport information
1747597,2018-02-06 08:55:55 UTC,apport information
1747597,2018-02-06 08:55:52 UTC,apport information
1747599,2018-02-06 08:30:29 UTC,"More feedback, when using the library asociation dialog, if you right click in the new symbol box the symbol library browser appears but it does not have any kind of search funciton. It would be lovely to reuse the same dialog as in the add component command, reducing the codebase and increasing the functionality."
1747599,2018-09-29 13:30:15 UTC,"The usability issues were fixed for 5.1, and the menu location & text improved to make finding it easier."
1747601,2018-08-10 06:23:20 UTC,"Someone has fixed it recently.
Refer to https://bugs.launchpad.net/cinder/+bug/1578036"
1747601,2018-08-10 03:16:07 UTC,"@maestropandy, did you backup a volume which is in-use? If you want to do a incremental backup of a in-use volume, at last, it will do a full-backup now."
1747601,2018-02-06 11:55:34 UTC,"This works in master just fine, and the only fix we have added to the Ceph backup driver since the latest stable/pike is the problem when you delete one of the backups [1] that is still waiting for reviews for the Pike backport."
1747601,2018-02-07 10:33:06 UTC,"@gorka : For ocata, if i want, after doing commit changes https://github.com/openstack/cinder/blob/stable/ocata/cinder/backup/drivers/ceph.py#L587 will work ? Seems, but it was abandoned being back ported."
1747601,2018-02-09 10:49:59 UTC,"I think it would work, and I don't think there will be any compatibility issues, but you can test this in a lab setup and validate that the basic creation and deletion works as expected."
1747601,2018-08-10 03:16:55 UTC,"BTW, is your backup driver ceph?"
1747624,2020-03-19 08:13:21 UTC,I also faced with this bug... I working on ubuntu 19.10 with phpstorm. On press ctrl+alt+A I expect file added to git. But actual I see the terminator window..
1747629,2018-02-06 20:56:12 UTC,"It seems an Out of Memory issue on [2]. Last Host Sys Info said 7925 MB used, 57 MB free [3]"
1747629,2018-02-06 21:25:09 UTC,"This is an Ansible error reported in many places by many people, outside of openstack-ansible, and long before Ansible 2.4 https://github.com/ansible/ansible/issues/12239"
1747629,2018-02-07 10:00:31 UTC,Meanwhile I can confirm the error on a Ubuntu 16.04 VM with 8 GB of RAM. Will test with other Ansible versions.
1747629,2018-02-08 10:54:13 UTC,"OSA master is using currenly ansible 2.4.2.0.
I had the same experience with 2.4.3.0
In ansible 2.5.0a1 I've got
ERROR! Unexpected Exception, this is probably a bug: module 'ansible.playbook.play_context' has no attribute 'MAGIC_VARIABLE_MAPPING'
+ ansible -m setup -a gather_subset=network,hardware,virtual hosts
Variable files: ""-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables_translations.yml -e @/etc/openstack_deploy/user_variables.yml ""
to see the full traceback, use -vvv
++ exit_fail 347 0
++ set +x
ERROR! Unexpected Exception, this is probably a bug: module 'ansible.playbook.play_context' has no attribute 'MAGIC_VARIABLE_MAPPING'"
1747629,2018-02-08 11:17:12 UTC,"Yeah we are not ready for 2.5 yet, but I didn't expect a RAM issue for our translations deploy until 2.4 appeared. That's what I meant. Probably worth digging deeper in why the memory is higher up for this deploy, and how can we reduce it."
1747629,2018-02-17 13:24:34 UTC,"There are some memory fixes promised in 2.4.4.0 https://github.com/ansible/ansible/issues/31673 but one project https://github.com/iiab/iiab/pull/671 reverted to 2.4.2.0, since it turned out 2.4.3.0 was aggravating memory problems"
1747629,2020-09-18 13:30:33 UTC,"Doesn't happen now, so marking as resolved"
1747630,2018-10-02 06:59:27 UTC,"One more thing, I can see this issue on our lab HW, onibi with i386 Precise."
1747630,2018-02-06 10:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1747630,2018-09-12 18:54:28 UTC,"very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update."
1747630,2018-09-13 08:45:43 UTC,This issue can be reproduced on that specific system here.
1747630,2018-09-13 10:47:09 UTC,"Note that I just found that this test is a bit flaky, the fail rate for this is about 50%
Just like bug 1717856"
1747630,2019-08-06 00:34:44 UTC,"Okay, the reason this test (and bug 1717856) fail sporadically is that ASLR in precise for i386 has very low number of random values for vdso and shared library offsets, when ulimits are set such that unlimited stack sizes are allowed:"
1747630,2019-08-06 00:36:49 UTC,"That said, at this point, I don't believe we are likely to fix this for 3.2 kernels, so adjusting the QRT test may be in order."
1747630,2019-11-13 00:05:42 UTC,Precise ESM reached end of life in April 2019.
1747637,2020-04-19 01:36:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747637,2020-10-15 17:24:19 UTC,Thanks for your report! I could confirm it using the latest daily build ISO for groovy.
1747641,2018-03-15 13:22:51 UTC,"Don't mix upstream and Ubuntu packages. To fix remove it completely and purge it, and install it again"
1747641,2020-06-23 13:02:28 UTC,"Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!"
1747646,2019-02-07 21:43:18 UTC,"Giving up after 5 attempts. Error: gdata-service-error-quark: Authentication required: {
 ""error"": {
  ""errors"": [
   {
    ""domain"": ""global"",
    ""reason"": ""authError"",
    ""message"": ""Invalid Credentials"",
    ""locationType"": ""header"",
    ""location"": ""Authorization""
   }
  ],
  ""code"": 401,
  ""message"": ""Invalid Credentials""
 }
}
 (4)"
1747646,2019-02-12 21:08:50 UTC,"I can confirm, same issue here."
1747646,2019-02-13 21:53:37 UTC,"I had the same problem. I didn't figure out the cause of this issue, but found a very simple solution. The credentials had expired, so I needed to go to Settings > Online Accounts and select my Google account and log in again. After a few minutes the back-up restarted automatically and finished successfully."
1747646,2019-03-09 20:28:36 UTC,The bug affects me even after I log out and log in again:
1747646,2019-03-09 20:35:01 UTC,System information:
1747646,2019-03-12 22:25:30 UTC,I have the same error while recovering a ~ 20 GB backup from Google Drive.
1747646,2019-04-02 23:02:53 UTC,<email address hidden>       is Francis
1747646,2019-01-07 02:19:09 UTC,I moved the above bug to GVFS: https://gitlab.gnome.org/GNOME/gvfs/issues/360
1747646,2019-04-09 12:25:02 UTC,"I did get a full backup completed; however, there are a few details I need help working through."
1747646,2019-04-09 12:36:28 UTC,"I attempted to run a daily backup to supplement the failed backup.  Oddly enough, the program recognized the original backup and attempted to build on it rather than clearing the volume and starting fresh.  It did fail with this message:"
1747646,2019-04-12 17:17:12 UTC,`snap install deja-dup --classic --beta` fixed it for me
1747646,2019-11-14 01:57:29 UTC,"Alright, the switch to our own keys seems to have fixed this. I’ll close the remaining tasks on this bug."
1747646,2020-05-31 21:09:43 UTC,"Using the default (apt) deja-dup with the online accoutns in ubuntu 18.04.
I found out a workaround for this. If you keep the session open manually by reading a file over and over you can reset the timer described here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/360"
1747646,2019-02-07 21:41:48 UTC,I am also facing this problem.
1747646,2019-04-05 15:49:39 UTC,I have prepared a new beta release of deja-dup that might fix this issue. The 39.x series has switched from GNOME's Google keys to our own keys and from the GIO duplicity backend to the pydrive one. Which may alleviate some of these issues (on the presumption that part of it is that the GNOME key's quotas are being hit or how GIO is re-authorizing).
1747646,2019-01-05 19:41:50 UTC,"Possibly, but I also notice that the gio backend doesn't implement _retry_cleanup(). Since re-running the same duplicity command can continue successfully without needing to re-start goa-daemon, I suspect there's something that could be done there to re-authenticate the connection."
1747646,2019-01-05 15:26:50 UTC,I suspect this is an issue with gnome-online-accounts and how it is driving the authentication. I've filed an upstream bug: https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/36
1747646,2019-01-01 02:39:51 UTC,"The bit about a possibly locked file can safely be ignored. For whatever reason, the PDF in question had mode 260."
1747646,2018-02-07 12:15:08 UTC,I tried today using duplicity (followed this guide https://6ftdan.com/danielpclark/2016/04/21/encrypted-linux-backup-with-google-drive-and-duplicity/) and everything went fine.
1747646,2018-02-11 18:01:02 UTC,Ah that blog post is using a different duplicity backend than deja-dup is using. Can you try something for me?
1747646,2018-02-12 14:51:33 UTC,"Hi,"
1747646,2018-04-30 10:07:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747646,2018-05-23 11:48:04 UTC,Bumping this... I will gladly pitch in $10 to whoever fixes this. This bug affects me and I really would love to see it solved. I can help with any diagnostics.
1747646,2018-07-28 12:50:22 UTC,"I noticed that I encounter this error when I am connecting via a VPN service, and do not encounter this error when I am not. If the reason is that Google rejects authenticating from suspicious IPs with the kind of authentication deja-dup and GNOME's online accounts use, I don't know if the team can do anything about it."
1747646,2018-09-10 08:41:42 UTC,"This happens to me to. I am not using a personal google account but a corporate one.
After 5 or 10 minutes I get an authentication error.
I am on ubuntu 18.04 using deja-dup 37-1 and duplicity 0.7.17"
1747646,2018-07-28 13:40:07 UTC,I would like to retract my report: my backups appear to not have completed.
1747646,2018-12-18 00:03:03 UTC,"This bug seems to not have been fixed yet. Nobody seems to have posted its solution on the internet.
Description : I have a weekly backup scheduled. I do this on my google drive of my gmail account."
1747646,2018-12-31 20:48:33 UTC,"Getting the same error on ubuntu-gnome 18.10 but I can see the backup files in google-drive. I don't know which part of the backup has failed
Giving up after 5 attempts. Error: gdata-service-error-quark: Authentication required: {
 ""error"": {
  ""errors"": [
   {
    ""domain"": ""global"",
    ""reason"": ""authError"",
    ""message"": ""Invalid Credentials"",
    ""locationType"": ""header"",
    ""location"": ""Authorization""
   }
  ],
  ""code"": 401,
  ""message"": ""Invalid Credentials""
 }
}"
1747646,2018-12-31 22:40:51 UTC,"I'm seeing exactly the same thing today on Fedora 29. It works fine on a new laptop with very little to back up, but a few gigs in to backing up my desktop I get the same error reported by the last two commenters."
1747646,2018-12-31 23:48:03 UTC,"Actually, slightly different. Probably not meaningfully so, but here it is just in case:"
1747646,2019-01-01 00:59:42 UTC,"The same error happens with Duplicity on the command line, but it sucks less because resuming works."
1747646,2018-09-29 02:25:44 UTC,Perhaps the OAuth token is expiring during long backup jobs and needs to be renewed? Not sure what it is based on because our times vary widely.
1747650,2018-02-16 05:15:56 UTC,"Reviewed:  https://review.openstack.org/543489
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a564fe1ac260381e786202ec1ea4de903b9cadc0
Submitter: Zuul
Branch:    stable/queens"
1747650,2018-04-20 13:14:51 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1747650,2018-02-16 05:57:16 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc2 release candidate.
1747650,2018-02-12 15:25:12 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/543489"
1747650,2018-02-07 09:25:04 UTC,This bug was opened following the discussion on IRC : http://eavesdrop.openstack.org/meetings/nova_cells/2018/nova_cells.2018-01-24-21.00.log.html#l-215
1747650,2018-02-06 11:43:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541246"
1747650,2018-02-09 17:55:34 UTC,"Reviewed:  https://review.openstack.org/541246
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ea6757092df85b6cce38980ae5b7f54b76657e01
Submitter: Zuul
Branch:    master"
1747651,2018-02-06 12:17:16 UTC,I understand this only happens with a specific file? Can you attach the file in question?
1747651,2019-06-11 03:15:36 UTC,Closing as there has been no response for more than 60 days.
1747664,2018-02-06 17:14:04 UTC,This branch fixes call number editing as long as all copies being edited are on the same bib. When copies from multiple bibs are being edited the call numbers aren't available. If that's a workflow that staff want to have available a more in-depth change is required.
1747664,2018-02-06 18:55:44 UTC,We can edit call numbers across bib records in the XUL client under item status (from the actions for catalogers menu). The copy bucket interface in the XUL client doesn't have edit call numbers functionality -- you have to transfer them to item status (which you can't do in the web client).
1747664,2018-02-06 21:00:26 UTC,"And it's apparently not as fixed as I thought. My patch isn't counting the number of bibs correctly anyway, so it only allows call number editing for single items. I suppose that's a good incentive to get moving on the ability to be able to edit any number of items and calls regardless of bibs involved."
1747664,2018-11-26 20:51:38 UTC,Removing milestones due to lack of pull request.
1747664,2020-06-05 19:11:17 UTC,"I pushed a branch that lets you edit call numbers from a copy bucket.  In the ""actions"" menu there's now an option ""Edit call numbers"":"
1747664,2020-08-18 12:35:25 UTC,I was able to successfully edit call numbers across multiple bib records in http://angular-acq-test.evergreencatalog.com/.
1747664,2020-08-18 21:41:11 UTC,"Pushed to master, rel_3_5, and rel_3_4. Thanks, Mike and Elaine!"
1747664,2020-08-19 16:25:02 UTC,I was able to edit the call number for items on different bib records within an Item Bucket.
1747675,2020-09-11 05:37:33 UTC,Closing because INVALID: Fix released 1.0.x
1747686,2019-04-25 20:59:34 UTC,I think the intended behaviour (and how it used to be) is:
1747686,2019-04-26 12:52:49 UTC,"@Jeff, yes.  The hot key should always immediately perform the tool action at the current cursor location.  This should always be the default hot key behavior for any tool in all of the editors."
1747686,2019-04-25 18:19:15 UTC,"@Wayne, they need to be consistent.  Are we OK with this behaviour for PCBNew as well?"
1747686,2019-04-25 20:48:48 UTC,"If you take a vote from an outsider:  W hotkey for startWire (immediate starting wire from actual mouse position), and Shft-W or Ctrl-W (or no accelerator/hotkey just context menu and icon on the right menubar)  for drawWire. I think I'd seldom or never use this switch-to-draw-track-but-don't-start-now function."
1747686,2019-05-10 13:11:21 UTC,"Just my 2 cents about the hotkey/accelerator behavior, we discussed a bit about that on IRC with John Beard and thought about the notion of ""infix"" (as in Cadence tools) which is equivalent of the ""W"" behavior as intended by Wayne."
1747686,2019-04-25 19:58:39 UTC,"BTW, there are two actions in the new eeschema stuff: startWire and drawWire.  The first starts drawing a wire immediately (and is hooked up to the context menu).  The second selects the wire tool, and starts a wire if the tool was already selected (and is hooked up to the W hotkey)."
1747686,2019-04-24 13:23:59 UTC,"@Paul, yes, the new behaviour makes it consistent with PCBNew: pressing W the first time selects the tool; pressing it again starts a wire."
1747686,2019-04-24 03:14:46 UTC,It looks like the bug below is relevant again. Pressing W once no longer starts the wire - the tool must already be active for a wire to be placed.
1747686,2018-02-14 11:16:44 UTC,"Ahh ok, I see what you mean now."
1747686,2018-02-14 10:42:58 UTC,"I created it to reduce clutter in the bug database.  These are mostly bugs that aren't worth fixing on their own, but should be fixed automatically by the GAL canvas."
1747686,2018-02-14 10:14:44 UTC,"Mmm, why do we need this?  Please use the gal and eeschema tag instead."
1747686,2019-04-24 14:00:06 UTC,"@Jeff, this is not the correct behavior.  The 'W' key press should
enable the wire tool and immediately start drawing a wire at the current
cursor position.  A separate Ctrl-W (or is it Shift+W?) entry should
only enable the wire tool.  All this does is add an extra steps that are
not necessary.  If users are more comfortable constantly switching
tools, that's fine.  What we should not do is force users to do so.
That is the entire reason for existence of hotkeys.  Hotkeys are not
menu accelerators even though we have used those terms interchangeably
in the past.  Please fix this when you get a chance and make sure all
tools ported to the new framework maintain the behavioral differences
between hotkeys and accelerators as closely as possible."
1747687,2018-04-19 20:58:05 UTC,This issue was fixed in the openstack/heat-dashboard 1.1.0 release.
1747687,2018-02-23 14:50:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547468"
1747687,2018-03-08 05:49:55 UTC,"Reviewed:  https://review.openstack.org/547468
Committed: https://git.openstack.org/cgit/openstack/heat-dashboard/commit/?id=1a39ac27477d1d10f8b447107504868f90909595
Submitter: Zuul
Branch:    master"
1747687,2020-06-17 07:19:52 UTC,"As this fix was shipped upstream more than two years ago, I'm marking it fixed for the Ubuntu package as well"
1747688,2018-02-06 15:18:13 UTC,"Hi Junien,"
1747688,2018-02-07 06:41:51 UTC,"The use case is that I need this information to decide if I must create a /boot/efi partition or not (see also related bug 1747685, which got marked as a duplicate of bug 1591336)"
1747688,2019-09-19 14:53:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1747688,2019-09-19 15:20:36 UTC,Still an issue in 2.4.2 (7034-g2f5deb8b8-0ubuntu1)
1747692,2018-05-07 14:23:16 UTC,"It looks like ubiquity tried to resize an existing ext2 filesystem smaller than its minimum and after that failed, ubiquity kind of drove partman off the rails."
1747693,2019-10-04 23:39:42 UTC,"Reviewed:  https://review.opendev.org/541420
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=de5bce6ea23e16c976b64fdf5b0daf06c540eb8b
Submitter: Zuul
Branch:    master"
1747693,2020-09-17 15:01:35 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/752488"
1747693,2019-09-17 05:17:02 UTC,"Reviewed:  https://review.opendev.org/682378
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aae96dc1aca011a49e05aee4c5df0b587bbfea78
Submitter: Zuul
Branch:    master"
1747693,2019-09-16 14:50:59 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/682378"
1747693,2018-02-06 19:46:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541420"
1747696,2018-02-06 17:26:59 UTC,"I think the export re-uses the settings previously set via UI, so that might be a possible workaround for you."
1747701,2018-02-08 17:11:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1747702,2018-02-06 15:56:47 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f73b48b04e8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=<optimized out>, str=0x7f73b48acf23 ""realloc(): invalid old size"", ptr=<optimized out>, ar_ptr=<optimized out>) at malloc.c:5425
 _int_realloc (av=av@entry=0x7f7380000020, oldp=oldp@entry=0x7f7381cda4a0, oldsize=oldsize@entry=724235115076526096, nb=nb@entry=2177745088) at malloc.c:4574
 __GI___libc_realloc (oldmem=0x7f7381cda4b0, bytes=bytes@entry=2177745072) at malloc.c:3245
 g_realloc (mem=<optimized out>, n_bytes=2177745072) at ../../../../glib/gmem.c:159"
1747702,2018-04-03 18:29:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747704,2018-02-08 17:11:12 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1747704,2018-02-09 11:10:00 UTC,"I personally do not know. I know that on previous versions of Ubuntu, the mouse worked fine, albeit was on a different PC and different hardware, so I unfortunately cannot say for certain.
If you'd like more debugging info or any more info from me, please let me know, and I will get around to trying your kernel suggestion ASAP."
1747704,2018-02-09 11:17:12 UTC,"PS: I unfortunately don't have alot of time today to try this, so I want to make sure I type in the commands and text right if I do go ahead with trying this. I hate to ask, but are you able to help me and show me what I need to type in the Terminal to hop on the latest build and to revert back if necessary?"
1747704,2018-02-09 11:28:27 UTC,"Oh wait, I found the issue.
The mouse was not completely recognized. It was not in pairing mode. (LOL)"
1747705,2018-02-09 14:32:41 UTC,"Hi, thanks for the good bug report.
I believe that you should be able to override the datasource provided config
in user-data.  Try providing user-data as:"
1747705,2018-03-02 10:06:17 UTC,"HI,"
1747705,2018-03-02 14:44:51 UTC,"Shota,
The change that put that behavior in was
 https://git.launchpad.net/cloud-init/commit/?id=e626359a6ea"
1747705,2018-03-02 14:51:39 UTC,"I can't remember the exact details, but I believe that this change was landed to support a CloudStack deployment that didn't support SSH keys at all.  In my ignorance of the broader CloudStack ecosystem, I assumed that this was true of all CloudStack deployments, so setting it in the data source made sense (so that people would be able to access their instances somehow)."
1747706,2021-02-07 21:44:08 UTC,"FWIW, works fine for me in bionic"
1747711,2018-08-21 01:50:44 UTC,"What does ""file --mime-type"" return for dynamic libraries?"
1747711,2018-11-03 12:27:24 UTC,"Electron applications using Electron 4.0.0 beta/nightly are effected by this bug making it impossible for developers to create Linux applications and have it easily work using that version, doesn't effect applications developed Electron 3.0.6 latest but this is a seriously annoying bugs that will cause issues with Linux users and needs to be patched."
1747711,2018-05-15 14:30:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747711,2019-01-24 07:12:59 UTC,">>> So for mime types to distinguish, ""file"" needs to grow reporting of the INTERP presence."
1747711,2019-01-24 06:55:16 UTC,">>> Yes, this is very much a bug. While ELF position independent executables are ELF shared objects, they weren't being recognized as executables by desktop launchers. So they wouldn't run."
1747711,2018-08-20 11:12:02 UTC,"And I don't think this is a bug because technically an ELF position independent executable IS a ELF shared object, right?"
1747711,2018-02-18 04:26:10 UTC,"I've had a discussion with Christos Zoulas, the root maintainer of ‘file’, and they will make the necessary changes in due course. Whether this will be noticed by all the forks and re-implementations such as xdgmime in Gnome, I don't know."
1747711,2018-05-15 15:00:55 UTC,"Has this been fixed upstream? Looking at the changelog, there has been a related change, but I'm not sure if it resolves the issue yet, it now says they're both executables."
1747711,2018-08-20 11:01:25 UTC,"Looks like the upstream fix makes many dynamic libraries wrongly detected as 'pie executable's.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906727"
1747711,2018-02-17 22:44:33 UTC,This is (sort of) a bug in file. The problem is not being able to distinguish between shared objects and PIE binaries. (The latter have INTERP ELF sections and can be run directly.)
1747711,2018-02-16 20:01:54 UTC,It is also an issue on bionic:
1747720,2018-02-06 17:42:28 UTC,Looks like the same with umount
1747720,2018-05-15 14:38:08 UTC,"Yes, I get the same thing:"
1747720,2018-05-16 07:14:35 UTC,"Reviewed:  https://review.openstack.org/568649
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=bd4378a74fd6678bed121a43609f142569915c9d
Submitter: Zuul
Branch:    master"
1747721,2018-02-08 02:19:40 UTC,Same problem: https://bugs.launchpad.net/python-openstackclient/+bug/1701079
1747721,2018-02-22 22:38:44 UTC,Ran into this today as well:
1747721,2018-04-05 18:51:39 UTC,related-fix (workaround) for manila: https://review.openstack.org/#/c/556351
1747721,2020-04-30 18:20:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/724726"
1747721,2020-05-18 21:44:33 UTC,"Reviewed:  https://review.opendev.org/724726
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=5998d04e79c52c5048ab251247b4f00d5b761067
Submitter: Zuul
Branch:    master"
1747731,2019-03-08 04:20:24 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1747731,2019-03-08 20:09:13 UTC,This issue was fixed in the openstack/python-aodhclient 1.2.0 release.
1747731,2018-11-09 07:09:04 UTC,This issue was fixed in the openstack/python-openstackclient 3.17.0 release.
1747735,2019-10-10 10:25:51 UTC,"It's not a snapd bug, so I've set it to Invalid."
1747743,2018-02-06 19:52:57 UTC,apport information
1747743,2018-02-06 19:52:59 UTC,apport information
1747743,2018-02-06 19:53:00 UTC,apport information
1747747,2018-02-06 20:45:47 UTC,"This seems like something that will come out of the effort we have underway to standardize callback payloads using payload event objects [1]. Some of this work is already underway [2], and will continue in the Rocky time-frame. IMHO it seems best to just ensure the payloads are proper when changing to the payload objects as part of this work."
1747747,2018-02-06 19:50:35 UTC,and this not just for L3 resources but all resources inclusive of L2 and L3.
1747748,2018-04-28 06:35:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747752,2018-05-06 13:11:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747754,2018-02-13 17:05:14 UTC,"After the bug triage, we validated the fact an upgrade task should be done to prevent this from happening."
1747754,2018-02-13 17:04:20 UTC,"We started a discussion about this bug in our bug triage of 2018/02/13. No consensus reached on the method to solve it, nor to the status."
1747755,2019-02-14 00:56:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636797"
1747755,2019-09-06 18:06:38 UTC,"Change abandoned by Cam J. Loader (cjloader) (<email address hidden>) on branch: master
Review: https://review.opendev.org/636797"
1747755,2019-02-13 21:36:51 UTC,"Change abandoned by Cam J. Loader (cjloader) (<email address hidden>) on branch: master
Review: https://review.openstack.org/636756
Reason: wrong place to do this"
1747755,2019-02-13 21:02:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636756"
1747755,2018-02-13 16:48:25 UTC,"It was discussed during triage, and it happens on all nodes. In O/P we don't remove uca in pip_install role , we just add the new one."
1747755,2018-02-13 16:45:09 UTC,"Maybe a log of the change of repo should help, and a log of the user_*.yml variables too."
1747755,2018-02-13 16:43:35 UTC,On which nodes does this happen?
1747759,2018-12-10 14:47:26 UTC,Anything missing for a promotion into Main?
1747759,2018-10-18 20:54:13 UTC,"Didier, ITPs posted:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911335"
1747759,2018-10-18 06:20:08 UTC,"@Till-kamppeter: yes, but not now. Ideally, could you file ITP's to Debian, mentioning that those should be maintained under the Debian Printing Team umbrella. The best would be if you maintained the packages in Debian yourself, which I could just mentor (upload for you)."
1747759,2018-10-17 20:54:23 UTC,"jbicha, I did not think about that yet, and did not know about the freeze on Debian."
1747759,2018-09-13 17:20:23 UTC,The cpdb-libs is hanging on the autopkgtest for arm64 only (rest OK).
1747759,2018-09-13 13:48:06 UTC,"stuck in -proposed for 21 days:
http://autopkgtest.ubuntu.com/packages/c/cpdb-libs/cosmic/arm64"
1747759,2018-10-14 03:17:48 UTC,"Till, by the way, are you going to try to get these packages into Debian too? The deadline for new packages to enter Debian for the Buster release is early February."
1747759,2018-06-22 18:46:40 UTC,cpdb-libs 1.1.2-0ubuntu2 uploaded with all the needed fixes.
1747759,2018-06-22 17:16:24 UTC,"cpdb-libs 1.1.2 uploaded, with autopkgtest and symbols files added."
1747759,2018-06-19 13:04:07 UTC,I have now modified the upstream code to use dynanically allocated buffers or snprintf() whatever is more appropriate in each situation.
1747759,2018-06-07 19:05:47 UTC,Please address the following issues:
1747759,2018-08-15 14:25:45 UTC,"Doko pointed out on IRC that the armhf autopkgtest is hitting some failures, https://autopkgtest.ubuntu.com/packages/cpdb-libs/cosmic/armhf which needs to be sorted out"
1747760,2018-09-13 17:24:19 UTC,This package will need seeding as there is no package yet using it.
1747760,2018-10-16 13:35:01 UTC,"jbicha, no, cups-ipp-utils provides utilities for developing of IPP-related software, whereas cpdb-backend-cups is a software module (backend) to add CUPS support to generic print dialogs which use the cpdb-libs library."
1747760,2018-06-07 19:10:39 UTC,Please address the following issues:
1747760,2018-06-19 13:03:59 UTC,I have now modified the upstream code to use dynanically allocated buffers or snprintf() whatever is more appropriate in each situation.
1747760,2018-06-22 17:15:00 UTC,cpdb-backend-cups 1.0.1 uploaded.
1747760,2018-09-13 13:46:26 UTC,this looks ok now. does it need seeding or a dependency somewhere?
1747760,2018-10-14 14:27:58 UTC,Does this mean we will no longer need to install cups-ipp-utils by default?
1747762,2018-06-07 19:12:39 UTC,that looks fine. waiting for cpdb-libs now before promotion.
1747764,2018-02-06 21:47:26 UTC,"Hey Jason,"
1747764,2018-02-06 21:53:55 UTC,"4. How long was it from the time the network partition was confirmed to the time the machine attempted to boot?
5. After the machine failed to boot, did the rack controller continued providing DHCP ?
6. Did the rack controller at all fully disconnected for *all* regions?"
1747764,2018-02-06 21:59:01 UTC,I see in the logs this:
1747764,2018-02-06 22:03:43 UTC,It is designed to stop DHCPD if the rack controller cannot talk to any region controllers. Just because you prevented the rack controller from talking to the region over HTTP did you prevent the RPC connections? That is a different port.
1747764,2018-02-06 22:12:24 UTC,"I've attached a drawing of my setup, I hope that helps.  10.245.31.4
(everitt) is the isolated controller in this test."
1747764,2018-02-06 22:13:58 UTC,"On Tue, Feb 6, 2018 at 3:47 PM, Andres Rodriguez
<email address hidden> wrote:

> Hey Jason,
>
> The information you provide is not enough for us to determine the
> configuration that you have. Since you now have a set environment, it
> would be ideal to have a graph or something that show us how you are
> configuring your MAAS HA environment, as it is difficult to understand
> without having a picture of how things are physically connected.
>
> That said. I have a few questions. As I understand, you have 1 rack
> controller isolated from the *VIP* of the region controller. I guess
> this means that rackd.conf points to the VIP. But:
>
> 1. Can the rack controller connect to the region controllers directly ?
"
1747764,2018-02-06 22:18:38 UTC,"I blocked all IP traffic between the isolated system and the other two
systems, so it couldn't talk either via RPC or HTTP.  dhcpd never
stopped on the isolated system, and is still running right now."
1747764,2018-02-06 22:23:04 UTC,"To be clear, to simulate the network partition by blocking traffic, I ran ""/sbin/iptables -I INPUT -s 10.245.31.4 -j DROP"" on 10.245.31.1 and 10.245.31.3."
1747764,2018-02-06 22:31:56 UTC,"IMHO, based on the logs from rackd.log it seems that after the rack is unable to connect, there are a lot of tracebacks due to unhandled errors. These unhandled errors could be blocking the code that stops dhcpd."
1747765,2019-06-10 15:01:54 UTC,Thanks!  I've just installed it on one of my Xenial servers for testing...  I'll let you know how it goes...
1747765,2019-06-03 16:12:23 UTC,"Hello Bo, or anyone else affected,"
1747765,2019-06-04 08:55:52 UTC,"Verified for bionic.
apt-cache policy cups-daemon
cups-daemon:
  Installed: 2.2.7-1ubuntu2.6"
1747765,2019-06-04 09:05:00 UTC,Verified for disco:
1747765,2019-06-04 09:13:43 UTC,Verified for cosmic:
1747765,2019-06-04 15:14:29 UTC,Despite some build failures for i386 and s390 which I believe are not related to the scope of the change I have successfully verified it for amd64.
1747765,2019-06-10 14:45:01 UTC,This bug was fixed in the package cups - 2.2.7-1ubuntu2.6
1747765,2019-06-10 13:25:03 UTC,"The verification of the Stable Release Update for cups has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1747765,2019-06-10 13:35:04 UTC,This bug was fixed in the package cups - 2.2.10-4ubuntu2
1747765,2019-06-10 14:42:59 UTC,This bug was fixed in the package cups - 2.2.8-5ubuntu1.4
1747765,2019-06-03 16:11:15 UTC,"Hello Bo, or anyone else affected,"
1747765,2019-06-10 14:57:14 UTC,This bug was fixed in the package cups - 2.1.3-4ubuntu0.9
1747765,2019-06-10 13:24:43 UTC,Thank you for verifying all the test cases!
1747765,2019-06-03 16:05:03 UTC,"Hello Bo, or anyone else affected,"
1747765,2019-05-30 11:13:48 UTC,SRU proposal for Xenial.
1747765,2019-06-03 15:50:30 UTC,"Thanks for the SRU! The upload looks good, but could I request that the new packages are tested against the PreserveJobHistory Yes/No values additionally to the 'seconds' case? As an additional safety check."
1747765,2019-05-30 07:29:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747765,2019-05-30 07:33:23 UTC,This has been fixed in 19.10 for cups 2.2.10-6 (backport from upstream).
1747765,2019-05-30 08:19:29 UTC,SRU proposal for Disco
1747765,2019-05-30 08:19:59 UTC,SRU proposal for Bionic
1747765,2019-05-30 08:23:19 UTC,"The patch doesn't apply cleanly to Xenial, working on backport."
1747765,2019-05-30 08:22:38 UTC,@sponsors: Eoan already has the fix from Debian.
1747765,2019-06-03 15:55:32 UTC,"Hello Bo, or anyone else affected,"
1747765,2019-05-30 12:21:23 UTC,SRU proposal for Cosmic.
1747765,2019-05-30 13:06:16 UTC,"I have sponsored the Xenial SRU now, but the one for Cosmic is missing the addition of the patch to debian/patches/series."
1747765,2019-05-30 14:03:45 UTC,"Thanks Till. I've fixed cosmic debdiff, sorry about the mistake."
1747765,2019-05-30 18:22:11 UTC,"SRU for Cosmic sponsored, thanks."
1747765,2019-05-30 09:57:02 UTC,Sponsored SRUs for Bionic and Disco.
1747769,2018-02-16 16:14:34 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/090261.html"
1747769,2019-12-27 09:21:50 UTC,c96f5471ce7d and its following fix has been applied to Bionic.
1747769,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1747769,2018-03-19 10:57:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1747769,2018-02-09 01:19:45 UTC,"The attached file 'Command output' contains the same terminal output as is pasted in the comment, but whitespace hasn't been munged."
1747769,2018-02-08 18:21:25 UTC,"I built a test kernel with commit c96f5471ce7d.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1747769"
1747769,2018-02-09 01:16:17 UTC,"Yes, this build fixes the bug."
1747769,2018-02-06 22:36:50 UTC,I think logfiles are irrelevant to this cherry-pick request.
1747769,2018-02-06 22:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1747769,2018-02-09 01:17:44 UTC,"# uname -a; dd if=/dev/xvda iflag=direct bs=16384 of=/dev/null & DD_PID=$!; sleep 1 && ./getdelays -di -p $DD_PID; kill $DD_PID; wait
Linux hostname-redacted 4.13.0-32-generic #35~lp1747769 SMP Thu Feb 8 17:37:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[1] 9578
print delayacct stats ON
printing IO accounting
PID	9578"
1747771,2020-08-12 05:36:00 UTC,python3-devedeng 4.7.0-1
1747775,2018-02-07 05:50:58 UTC,"I think they are not running since https://review.openstack.org/#/c/348569/7/, where we've added the below."
1747775,2018-02-07 19:12:27 UTC,I already submitted a patch to remove the Rackspace ones: https://review.openstack.org/#/c/541475/
1747778,2018-02-06 23:39:51 UTC,"Indeed, this is something we'd like to do."
1747780,2018-04-11 09:45:57 UTC,Got this as well because I tried selecting a file for user theme that was not .zip (was .tar.gz). Converted file to .zip and was able to successfully install.
1747780,2018-02-13 08:19:55 UTC,happened to me as well - sorry i do not have anything helpful to say
1747780,2018-03-30 13:41:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747781,2018-02-23 18:15:29 UTC,"IIUC horizon does not support hierarchical project at now. It is worth tackled as a blueprint. From this observation, I mark this as wish-list."
1747794,2018-02-07 23:54:50 UTC,"Great, thank you!"
1747794,2018-02-07 15:45:58 UTC,"Fix has been now merged in:
https://github.com/snapcore/snapd/pull/4632#issuecomment-363806226
bug status can be changed to ""fix committed"""
1747794,2018-02-07 14:03:36 UTC,"I can confirm this is bug in avahi-observe interface and it requires patch in interface definition
here is fix
https://github.com/kubiko/snapd/commit/4179adcfb027e1a57ed15c0a76b71043e255c177"
1747797,2018-03-01 02:27:32 UTC,"Thank u for the bug report, but unfortunately, trove is not translation target any more because of https://review.openstack.org/#/c/511813/ ."
1747802,2018-04-24 02:21:31 UTC,That was in an artful VM running bamfdaemon 0.5.3+17.10.20180208-0ubuntu1
1747802,2018-05-09 11:32:57 UTC,Please re-tag once you have detailed what verification was performed.
1747802,2018-04-26 09:33:13 UTC,"What testing was performed on this version? For example, did you test that an application with security profile gets a correct desktop file?"
1747802,2018-04-23 10:09:02 UTC,What testing has been has been performed on this package? On what versions?
1747802,2018-03-01 23:49:10 UTC,This bug was fixed in the package bamf - 0.5.3~bzr0+16.04.20180209-0ubuntu1
1747802,2018-03-01 23:39:11 UTC,"The verification of the Stable Release Update for bamf has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1747802,2018-02-20 13:19:21 UTC,@3v1n0 can you also test the artful version?
1747802,2018-02-20 01:17:19 UTC,"Brian, it was just rebuilt by bileto because I forgot to untick bamf from a rbuild, so nothing changes from previous testing."
1747802,2018-03-23 21:16:37 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of bamf from artful-proposed was performed and bug 1752153 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed-artful"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1752153 (not this bug). Thanks!"
1747802,2018-02-09 17:19:48 UTC,"Hello Marco, or anyone else affected,"
1747802,2018-02-08 16:32:43 UTC,Can confirm that test-case works in xenial after updating:
1747802,2018-02-08 14:30:12 UTC,"Hello Marco, or anyone else affected,"
1747802,2018-02-08 13:13:24 UTC,Artful backport coming also in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3137/+packages
1747802,2018-02-08 10:53:11 UTC,"Hello Marco, or anyone else affected,"
1747802,2018-02-08 10:51:35 UTC,"I'm wondering if it makes sense to also get this released for artful? Unity is not the default experience but the package is still available, so in theory someone upgrading from xenial to artful and insisting on staying with Unity as his shell might experience a regression."
1747802,2018-02-07 16:39:35 UTC,This bug was fixed in the package bamf - 0.5.3+18.04.20180207.2-0ubuntu1
1747802,2018-02-19 23:48:10 UTC,Why was the 20180209 version of the package created? Does it too need testing?
1747809,2018-02-16 02:38:41 UTC,"Since this seems to be a Plasma issue rather than a Kubuntu/ubuntu issue, the useful place to report this situation is bugs.kde.org."
1747809,2018-02-15 00:52:53 UTC,And this is the same issues reported for ArchLinux:
1747809,2018-02-14 23:14:22 UTC,Still the same bug persists after today's update to Plasma 5.12.1 / KDE 5.43.0:
1747809,2018-02-10 22:02:27 UTC,The same set of problems with 5.12 update is currently being discussed / debugged on KaOS list:
1747809,2018-02-07 19:06:22 UTC,"Non functional desktop after upgrade to 5.12 in Kubuntu 17.10
- Windows without frames, borders and buttons, Latte dock frozen, etc ..."
1747809,2018-02-07 03:43:51 UTC,"$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 17.10
Release:        17.10
Codename:       artful"
1747809,2018-02-08 03:17:40 UTC,More things which stopped working:
1747818,2019-05-28 20:20:42 UTC,There is already a Behat Feature file for Participation that has scripts for the above - this may be a duplicated bug.
1747823,2018-09-13 04:21:38 UTC,09/12 11:27:53 DEBUG| utils:0153| [stdout] noresv-preserve-resv-page (2M: 64):	FAIL	Steal reserved page
1747823,2018-02-07 04:30:06 UTC,This change was made by a bot.
1747823,2018-09-12 18:55:55 UTC,"very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update."
1747823,2019-11-13 00:11:39 UTC,This is still an issue: http://10.246.72.4/test-results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_10-32-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html
1747824,2018-04-24 02:59:05 UTC,"In reply to Paul, here is the output you asked for:"
1747824,2018-04-23 19:53:36 UTC,"I've just found the root cause for this is tmux. If fp ide is run on an xfce terminal it doesn't crash, but under tmux on the same xfce terminal it does."
1747824,2019-03-13 13:02:06 UTC,"Hi, I think problem is fp parses process stat files."
1747824,2018-07-02 12:30:04 UTC,"Can you please try this one?
https://launchpad.net/ubuntu/+source/fpc/3.0.4+dfsg-20~build1"
1747824,2018-04-23 17:58:45 UTC,"And for me, on a Debian buster system, it works without issue."
1747824,2019-03-13 13:04:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747824,2018-04-23 17:45:00 UTC,"Just tried with the 3.0.4+dfsg-18 packages, still the exact same thing."
1747824,2018-02-10 10:30:51 UTC,"Got the new fp-ide update, version 3.0.4+dfsg-15ubuntu3, still crashing just the same."
1747824,2018-04-23 17:57:35 UTC,Can you please give us the outcome of
1747824,2018-04-01 00:42:32 UTC,"Made a clean installation of Ubuntu 18.04, fully updated, installed fp-ide, still crashes all the same."
1747824,2018-04-01 00:17:35 UTC,"Just tried with the 3.0.4+dfsg-16 packages, still the exact same thing."
1747828,2018-02-07 04:49:44 UTC,Core file for:
1747828,2018-02-07 05:00:08 UTC,This change was made by a bot.
1747828,2018-09-12 19:00:36 UTC,"very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update."
1747828,2018-09-13 04:19:18 UTC,"09/12 11:27:57 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64):	FAIL	Killed by signal ""Bus error"" due to overcommit"
1747828,2019-11-13 00:13:17 UTC,This is still an issue: http://10.246.72.4/test-results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_10-32-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html
1747830,2018-02-07 05:10:17 UTC,"Can we just suggest user to add the IFL statement into profile, then all the userids can include it."
1747830,2018-02-07 05:27:38 UTC,"maybe, through API input might provide better flexiblity ? don't yet, anyway, will provide some update after the busy season of release 1.0.0"
1747836,2019-04-30 07:21:14 UTC,Hi!
1747836,2018-02-09 01:47:24 UTC,"OK, a generic fix is very tricky."
1747836,2018-02-07 16:50:46 UTC,I don't think this bug is unique to Octavia. Since I953a52e9b165d3ea4fb2fc57ceea8083c7f8f30c we try to translate properties *after* loading their stored values from the database while deleting a resource: http://git.openstack.org/cgit/openstack/heat/tree/heat/engine/resource.py#n1995
1747836,2018-02-07 16:39:08 UTC,"Wait, why are we trying to resolve property values at delete time, when we should be using the cached value?"
1747836,2019-04-30 07:47:56 UTC,"On Tue, Apr 30, 2019 at 1:00 PM Gauvain Pocentek <
<email address hidden>> wrote:"
1747836,2018-02-07 06:13:42 UTC,Also please add details in the bug description rather than using paste.
1747836,2018-02-07 06:09:33 UTC,That's because you deleted the resources using octavia api before deleting the stack. Pool property translation is wrapping the HttpNotFound as ValueError. We should handle this though.
1747836,2018-02-07 06:19:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541558"
1747847,2020-06-05 10:01:41 UTC,"I noticed that failure too, tested it manually on trusty amd64 with both 64-bit and 32-bit binary, and with 3.2 kernel, and it worked fine. I'll try the whole suite on a precise VM and see if I can reproduce it."
1747847,2020-06-05 08:41:47 UTC,"Issue can be found on Precise 3.2 i386
3.2.0-145.192"
1747847,2019-11-13 00:15:43 UTC,This is still an issue: http://10.246.72.4/test-results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_08-59-00/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-security.py.DEBUG.html
1747847,2018-02-07 07:00:14 UTC,This change was made by a bot.
1747847,2018-09-12 19:01:23 UTC,the reporting bug has been marked invalid and doing the same here.
1747847,2018-12-05 06:18:55 UTC,The original bug report was closed due to its quality and it's been tear-down into small pieces in multiple bug reports.
1747850,2019-11-13 16:59:42 UTC,Just confirmed we are still affected by this: http://10.246.72.4/test-results/3.13.0-174.225-generic/ms10-35-mcdivittB0-kernel__3.13.0-174.225__2019-10-04_08-59-00/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-security.py.DEBUG.html
1747850,2018-12-05 06:45:28 UTC,"The original bug report was closed due to its quality and it's been
tear-down into small pieces in multiple bug reports."
1747850,2018-09-12 19:02:04 UTC,"the reported bug was marked invalid, doing the same here"
1747850,2018-08-10 08:33:56 UTC,Test renamed to test_130_config_debug_rodata
1747850,2018-02-07 07:30:06 UTC,This change was made by a bot.
1747854,2019-03-28 10:56:05 UTC,"Can you please post:
kolla-ansible version used
kolla-ansible error log
docker logs <failing container>"
1747854,2019-05-28 04:17:46 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1747854,2018-05-30 04:19:48 UTC,Does ovs-dpdkctl.sh exist under kolla-ansible/tools/ ?
1747873,2018-02-07 10:00:43 UTC,apport information
1747873,2018-02-07 12:32:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1747873,2018-02-07 10:00:50 UTC,apport information
1747873,2018-02-07 10:00:48 UTC,apport information
1747873,2018-02-07 10:00:47 UTC,apport information
1747873,2018-02-07 10:00:45 UTC,apport information
1747873,2018-02-07 10:00:52 UTC,apport information
1747873,2018-02-07 10:00:42 UTC,apport information
1747873,2018-02-07 10:00:38 UTC,apport information
1747873,2018-02-07 10:00:32 UTC,apport information
1747873,2018-02-07 10:00:40 UTC,apport information
1747873,2018-02-07 10:00:36 UTC,apport information
1747873,2018-02-07 10:00:34 UTC,apport information
1747874,2018-02-07 09:50:41 UTC,"In fact it should be set to “plugins=cloudbaseinit.plugins.common.setuserpassword.SetUserPasswordPlugin” ,this is the error described in cloudbase-init/doc/plugins.rst，the problem should be fixed."
1747874,2018-02-07 09:58:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/541643"
1747874,2019-06-10 11:45:44 UTC,"Reviewed:  https://review.opendev.org/541643
Committed: https://git.openstack.org/cgit/x/cloudbase-init/commit/?id=1189ac5dd270473abc68483f1a93000260f1bee3
Submitter: Zuul
Branch:    master"
1747875,2018-02-07 21:28:06 UTC,"You can check from within the extension whether the $SNAP environment variable is set.
It's a bit of a suboptimal user experience, but at least that would provide feedback to the user."
1747875,2018-02-07 16:11:51 UTC,"OK, but I don't think including the hundreds of MB of LaTeX packages could be an option."
1747875,2018-02-07 14:43:44 UTC,"The way snaps work, they are strictly confined with apparmor that prevents access to the host system. There are interfaces that, when connected, allow partial access to some of the host's features, but to my knowledge none of them allow executing random binaries in /usr/bin/."
1747875,2018-02-07 12:21:28 UTC,Is it not possible to simply allow the access to the /usr directory?
1747875,2018-02-07 11:20:28 UTC,"Given that TexMaths is configurable and lets the user change the path to the latex binary, I guess one option would be to ship latex within the snap. That might not be very user-friendly, as I'm not convinced the extension would find it without the user telling it where to look for it. And we need to check how much bigger the resulting snap would be with a latex installation."
1747881,2019-08-15 01:48:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747884,2018-10-30 07:49:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747890,2018-04-02 19:36:34 UTC,This bug was fixed in the package linux-azure-edge - 4.15.0-1005.5
1747890,2018-02-21 19:09:21 UTC,This bug was fixed in the package linux-azure - 4.13.0-1011.14
1747890,2018-03-20 15:29:04 UTC,This bug was fixed in the package linux-azure - 4.15.0-1002.2
1747891,2019-01-31 10:41:55 UTC,[Maybe also related](https://askubuntu.com/questions/1114350/ubuntu-18-04-1-freezes-when-connecting-to-a-second-screen)? I have added some syslog errors if that helps anyone solve the issue.
1747891,2019-08-19 14:57:52 UTC,I get this error from the sessiom of GDM3:
1747891,2018-05-01 14:27:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747891,2018-09-30 15:01:58 UTC,This bug also appears in Arch linux 4.18.10 running gdm 3.30.1 on X11 (xorg server 1.20.1).
1747892,2018-02-07 11:47:00 UTC,This can be reproduced with 4.14 kernel too (4.14.0-1004-azure-edge)
1747892,2018-04-09 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1747892,2018-09-18 14:48:50 UTC,Still reproducible with azure : 4.15.0-1024.25
1747893,2018-02-07 15:53:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1747895,2018-02-07 15:55:31 UTC,"Reviewed:  https://review.openstack.org/541690
Committed: https://git.openstack.org/cgit/openstack/vitrage/commit/?id=324ab02b6abc26ec6a51d7a4be723afd6b2d2e14
Submitter: Zuul
Branch:    master"
1747901,2018-02-07 12:27:27 UTC,La traducción automática me convierte el segundo paso a paso cuando quiero decir path (trayecto en español).
1747904,2018-02-17 10:21:25 UTC,"Change abandoned by Qiming Teng (<email address hidden>) on branch: master
Review: https://review.openstack.org/543767"
1747904,2018-02-14 15:09:05 UTC,Yes - this is absolutely a bug. The underlying issue is that while we create proxy objects for each official type and then also add them to the connection for every alias so that both:
1747918,2018-02-07 14:40:35 UTC,Workaround: Settings -> Options -> Application -> Style -> change Plastique into GTK+
1747927,2018-02-07 17:30:53 UTC,As I asked in https://bugs.launchpad.net/maas/+bug/1743249/comments/65:
1747927,2018-02-07 18:19:16 UTC,"Steve,"
1747927,2018-02-07 23:03:31 UTC,"On Wed, Feb 07, 2018 at 06:19:16PM -0000, Jason Hobbs wrote:

> Steve,
"
1747936,2018-05-15 04:04:45 UTC,This issue was fixed in the openstack/nova 16.1.3 release.
1747936,2018-05-09 22:01:17 UTC,"Reviewed:  https://review.openstack.org/553829
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=68a21ec1d88b523e2583dcda8e948e753b9f9cbb
Submitter: Zuul
Branch:    stable/pike"
1747936,2018-04-02 13:09:13 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1747936,2018-04-20 13:13:40 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1747936,2018-03-21 14:48:57 UTC,"Reviewed:  https://review.openstack.org/553496
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6401d1e3c8966f5c9b9106d2e3918c766ce8b48a
Submitter: Zuul
Branch:    stable/queens"
1747936,2018-03-15 17:17:20 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/553496"
1747936,2018-03-16 15:36:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/553829"
1747936,2018-02-09 18:01:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/542964"
1747936,2018-03-18 01:52:55 UTC,"Reviewed:  https://review.openstack.org/542964
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dc2d15129d1a86a841e3dc1ccab250c30d34c540
Submitter: Zuul
Branch:    master"
1747937,2020-03-05 00:50:05 UTC,The only work around at the moment it to toggle the backup flag (dashboards_backup_schedule) off and on again
1747937,2020-03-17 06:21:31 UTC,I will work on this one.
1747938,2018-02-07 15:40:37 UTC,"StacktraceTop:
 XQueryExtension (dpy=dpy@entry=0x5643c9019900, name=name@entry=0x7fc67a40d8d8 ""XFree86-VidModeExtension"", major_opcode=major_opcode@entry=0x7ffd1fe806c4, first_event=first_event@entry=0x7ffd1fe806c8, first_error=first_error@entry=0x7ffd1fe806cc) at ../../src/QuExt.c:43
 XInitExtension (dpy=dpy@entry=0x5643c9019900, name=name@entry=0x7fc67a40d8d8 ""XFree86-VidModeExtension"") at ../../src/InitExt.c:47
 XextAddDisplay (extinfo=0x7fc67a60f170 <_xf86vidmode_info_data>, dpy=0x5643c9019900, ext_name=ext_name@entry=0x7fc67a40d8d8 ""XFree86-VidModeExtension"", hooks=hooks@entry=0x7fc67a60f100 <xf86vidmode_extension_hooks>, nevents=nevents@entry=0, data=data@entry=0x0) at ../../src/extutil.c:110
 find_display (dpy=<optimized out>) at ../../src/XF86VMode.c:80
 XF86VidModeQueryExtension (dpy=<optimized out>, event_basep=event_basep@entry=0x7ffd1fe80788, error_basep=error_basep@entry=0x7ffd1fe8078c) at ../../src/XF86VMode.c:97"
1747952,2019-11-08 00:42:30 UTC,This is commands to go through upgrading the various models though? So not sure what you mean command to '--upgrade-models' ?
1747953,2020-09-10 14:20:04 UTC,Closing because INVALID: Support request (fulfilled).
1747953,2018-02-08 13:50:26 UTC,"Wow! Thanks'.
Too bad that this is not the default."
1747953,2018-02-08 16:55:36 UTC,The setting can be made the tool's default by unchecking the box in the Node tool preferences (double-click on tool).
1747953,2018-02-08 12:52:58 UTC,"This seems to be a function of the setting in Preferences for the Node Tool: ""Deleting nodes preserves shape"". (preserve-mode active will change node type)"
1747958,2020-02-20 14:32:50 UTC,"I just confirmed with efibootmgr 17 in focal that this works properly.
I tested both the (-t) and (-T) arguments."
1747966,2019-12-20 13:55:42 UTC,9-2019-q4: bug is still present.
1747966,2018-10-05 16:03:24 UTC,I'm also still seeing this issue on the 7-2018-q2-update version
1747966,2018-12-19 17:05:24 UTC,"I have experienced this issue as well and workaround (fix?) is to put libs between -Wl,--whole-archive -Wl,--no-whole-archive during link stage"
1747966,2019-01-29 09:20:22 UTC,Still experiencing this issue with 8-2018-q4-major
1747966,2019-03-07 15:51:09 UTC,I can confirm that this is still broken in 8-2018-q4-major.
1747966,2019-08-02 12:17:13 UTC,Is this still broken in the 8-2019-q3-update?
1747966,2019-08-06 04:42:54 UTC,"Yes, the bug is still there :\"
1747966,2019-09-08 13:50:05 UTC,"I happily found an alternative fix, after poking around in the gcc function attributes there exists function attributes that mark the function as an interrupt and theirs many of them depending on which processor your targeting."
1747966,2019-12-21 13:52:03 UTC,"Hm, probably this bug has too low priority that nobody works on fix it as it can be workarounded by parameter order. Nothing to wonder, on avr-gcc the internal compiler push-reload error, that I and other users on avr freeaks encountered, was fixed after 3 years ago when leaping from gcc 4.x to gcc 8.x."
1747966,2020-11-14 10:21:38 UTC,"There is a fix in upstream binutils:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=0e6a3f07f50723d1831291492b96fdf74bcbdc11"
1747966,2020-02-15 18:51:43 UTC,Yeah I was happy at first when I enabled lto only to find out that it stripped out all my ISRs :(
1747966,2020-10-17 08:27:41 UTC,"Well the same happens with 9.3 and without lto.
Somehow the ISR's are not filled in by the linker and are kept as the weak defaults.
I really don't know."
1747966,2020-11-02 01:07:49 UTC,"Hm, nobody use ISRs to findout and fix it? Or what special keyword to use in declaration?"
1747966,2020-11-02 03:06:36 UTC,"I did a quick test on 2020-q2 and it behaves same as 2019-q4 in my case
(with order
$(NAME)-$(CORE).axf: $(STARTUP) $(OBJS)
it works with lto enabled)"
1747966,2018-07-16 09:07:13 UTC,"Right, the Ubuntu PPA was built during Q3 which is why it shows Q3. That's actually our 7-2018Q2 toolchain as shown by the output of apt-cache. Alright so you still encounter the bug, adjusting the status of this bug accordingly."
1747966,2020-11-14 14:03:04 UTC,"Good news, hope it will be updated soon. I'm not familiar with gcc/binutils compiling, if someone elese will recompile it let us know, please."
1747966,2020-12-27 21:38:02 UTC,"I experienced a similar case when linking against libopencm3. Since libopencm3 has lots of symbols just reordering the library in front of the obj files did lead to lots of linker errors. In this case adding a linker group helped: `-Wl,--start-group -lopencm3_stm32f0 $(OBJS) -Wl,--end-group`. However, ordering the library before the obj files is still needed despite the linker group."
1747966,2021-02-07 11:30:45 UTC,"Compiling and linking with -flto works for me with GNU Arm Embedded Toolchain 10-2020-q4-major and 9-2020-q2-update if I use:
  'arm-none-eabi-gcc-ar' instead of 'arm-none-eabi-ar'
  'arm-none-eabi-gcc-nm' instead of 'arm-none-eabi-nm'
  'arm-none-eabi-gcc-ranlib' instead of 'arm-none-eabi-ranlib'"
1747966,2019-12-21 20:41:55 UTC,"Sigh, it get even worse. The new GCC 9.2.1 with -lto option did make inline my custom timer_init function some wrongway that my code doesn't work. When I mark this function with __attribute__ ((noinline)) or when I change order of init_xx functions in my main() it gets working. I don't want more bad surprises so I rather reverted back to older GCC."
1747966,2018-07-15 21:26:37 UTC,"This is the output of apt-cache:
sudo apt-cache policy gcc-arm-embedded
gcc-arm-embedded:
  Installed: 7-2018q2-1~bionic1
  Candidate: 7-2018q2-1~bionic1"
1747966,2018-08-30 05:43:17 UTC,"I have the same issue, but to me it seems even worse using 7-2018-q2-update on windows: Even without LTO the order of the objects is relevant (the weak symbols must be last) and with LTO I can't get the correct symbols linked at all."
1747966,2018-07-13 12:28:42 UTC,The version is 7-2018q2-1~bionic1 on Ubuntu 18.04. Where do you see the 7-2018-q3-update? Can you show the output of apt-cache policy gcc-arm-embedded?
1747966,2018-02-08 09:29:33 UTC,Thanks for the report. Is the isr section kept if you drop the -flto?
1747966,2018-07-15 21:25:06 UTC,"Hi Thomas,"
1747966,2018-02-08 11:17:25 UTC,"Hi, sure if I remove -flto option the ISRs are not dropped from binary even without use of any mentioned attributes. But the section itself is listed in LST file:
Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .isr_vector   00000188  08000000  08000000  00010000  2**0
                  CONTENTS, ALLOC, LOAD, READONLY, DATA"
1747966,2018-02-18 11:52:14 UTC,"Got exactly the same problem.
My project doesn't have any interrupt vectors assigned in the resulting binary.
Using ""-fno-lto"" the project is built correctly but I loose the benefits of LTO.
With GCC v6 the LTO is working fine with the same code / project."
1747966,2018-02-18 14:34:30 UTC,">Dominik Vogel
Hi, good that it's confirmed by other person, maybe it will get more attention. BTW do you include any STM32 header files for ISR definitions? My project is for STM32L476 and I use only basic Cube headers with registers definitions but not any c file.
"
1747966,2018-02-20 17:25:12 UTC,Same here. I'm using an STM32F103 and only use the Register definitions from the Cube-Library.
1747966,2018-02-20 23:07:40 UTC,"OK, it might be possible that only STM32 header users suffer this problem. Can someone else confirm that GCC is not throwing his ISR with LTO and post some details about his ISR definitons?"
1747966,2018-02-21 09:38:05 UTC,"Hi GLX,"
1747966,2018-02-21 16:57:30 UTC,"OK, i tried it and the only change is that some new lines appeared in LST file:"
1747966,2018-02-08 10:52:59 UTC,"Thanks for report. Can you please confirm if the same project works on GCC6 without modification? If yes, it looks a regression or behaviour change in GCC7"
1747966,2018-03-02 15:10:11 UTC,"Hi Bernd,
thank you to let us know. I can confirm that your workaround also works for me.
I simply changed a line in my Makefile:"
1747966,2018-03-02 15:18:06 UTC,"Sorry, I meant
from:
$(NAME)-$(CORE).axf: $(OBJS) $(STARTUP)
to:
$(NAME)-$(CORE).axf: $(STARTUP) $(OBJS)"
1747966,2018-03-02 18:29:22 UTC,Works for me too! Thanks for the hint / workaround Bernd.
1747966,2018-04-23 16:43:31 UTC,"Hi Tejas,"
1747966,2018-04-24 09:05:18 UTC,"As mentioned by Maxim, this should be fixed in 7-2017Q4 release. Can someone confirm?"
1747966,2018-05-05 19:46:38 UTC,"I was experiencing this bug as well and can add that gcc-arm-none-eabi-7-2017-q4-major from https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads still exhibits this problem.
I needed to put startup before sources for -flto to work, thanks for the work-around!"
1747966,2018-07-12 23:24:57 UTC,"Hi All,"
1747966,2018-03-02 10:00:04 UTC,"This is the same bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83967"
1747968,2018-05-31 00:32:56 UTC,Confirmed this in 3.1
1747968,2019-08-12 19:39:04 UTC,Confirmed this is still an issue in 3.3
1747968,2020-04-09 00:53:24 UTC,Confirmed still an issue in 3.5
1747969,2018-03-07 09:34:54 UTC,Renamed bug to match my current understanding of the issue.
1747969,2018-02-13 16:57:04 UTC,"After a conversation with @jamespage, we agreed that it was better practice to simply inject values into the neutron.conf file, rather than adding complexity to the charm by proliferating configuration files."
1747969,2018-02-07 17:33:46 UTC,"I am grabbing this bug, as I am working on a fix right now."
1747970,2018-02-07 18:57:27 UTC,"Yes, I confirm this is the patch we need for the Enhanced Session mode."
1747970,2018-02-08 12:36:20 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-February/090082.html
1747970,2018-02-14 13:31:18 UTC,"Josh, should this change also be applied to the generic kernels?"
1747970,2018-02-21 19:06:02 UTC,"Any other backports needed, Marcelo and Josh?"
1747970,2018-02-21 19:09:21 UTC,This bug was fixed in the package linux-azure - 4.13.0-1011.14
1747979,2018-04-19 22:13:02 UTC,This issue was fixed in the openstack/osc-placement 1.1.0 release.
1747979,2018-02-08 07:41:04 UTC,"Hi Fan,"
1747979,2018-02-08 04:57:12 UTC,"Hi Ameed,"
1747979,2018-02-08 04:29:00 UTC,"Hello Fan,"
1747980,2018-05-06 13:11:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1747980,2018-05-07 05:14:31 UTC,"Qt Virtual Keyboard is not supposed to be used under X session, the one that comes with Qt 5.9 at least. You can enable it by setting a global environment variable but better not do that. Under X it's more of a nuisance rather than something helpful. Consider a different solution. Status should be set to ""Invalid""."
1747982,2018-02-11 18:28:01 UTC,"Your instinct to install python-gi seems correct. It should provide ""gi.repository"" which is what I assume the problem is from that error message."
1747982,2018-02-14 06:23:04 UTC,"Hello Mike,"
1747982,2019-11-14 01:27:32 UTC,This was a packaging error that must be fixed in 19.10 at least. Certainly it is fixed in the snap version. Closing this ticket.
1747985,2018-03-08 21:56:38 UTC,Created related blueprint: https://blueprints.launchpad.net/nova/+spec/volume-multiattach-enhancements
1747985,2018-02-08 17:00:39 UTC,"The next problem is hit in the n-api create code. During multi-instance create, for each instance, the method _validate_bdm is called on the common volume. When this is called for the first instance, it calls _check_attach_and_reserve_volume, which calls cinder to do an attachment_create to reserve the volume. So far so good."
1747985,2018-02-07 21:32:21 UTC,"It looks to me that the multiattach feature wasn't fully taking care of all the corner cases, including the multiple create call."
1747992,2019-09-20 08:10:30 UTC,I believe this bug is related to an area that is being fixed now (related to switching the risk level). I'll ask my colleagues who work on this to update this bug.
1747992,2019-09-20 08:25:05 UTC,Hmm.. I'll take a look. It might be the status reporting getting confused by the changes.
1747998,2018-02-15 04:14:37 UTC,"I thought we had a bug already for this, but the only one I could find was https://bugs.launchpad.net/juju/+bug/1705767."
1747998,2018-02-15 04:15:09 UTC,"If you rebootstrap, the new juju will see the spaces that MAAS has after the update. 'reload-spaces' currently only really supports adding new spaces or new subnets."
1747998,2019-04-14 16:27:00 UTC,"Hello,"
1748019,2018-02-09 21:27:12 UTC,"I reproduced with lxml 4.0.0 and 3.7.2 packages from fedora, but I didn't reproduce with pip installed lxml, so maybe this is distribution build specific"
1748019,2018-02-09 23:04:49 UTC,I filed a Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1544019
1748019,2018-02-10 17:24:14 UTC,The PyPI wheels are manylinux1 builds (PEP 513) but statically link the latest libxml2 and libxslt versions (at the time of their creation). That's probably why they do not conflict with the external libraries.
1748019,2018-02-10 17:45:03 UTC,"I'll close this as ""won't fix"", since it's been documented for years. Unless someone finds a better way to work around this, static builds will be the way to handle it.
http://lxml.de/installation.html#using-lxml-with-python-libxml2"
1748019,2018-02-23 19:07:38 UTC,I think libvirt can be extended here to workaround the conflict with something like:
1748019,2018-02-24 08:56:14 UTC,"I agree that this can be done in some places, and it would probably improve the situation."
1748019,2020-08-05 06:54:54 UTC,"The situation should have improved with the fix for
https://bugs.launchpad.net/lxml/+bug/1880251"
1748021,2018-03-09 04:53:52 UTC,"Ah, OK - I just tried two brand new VMs with Ubuntu 17.10. On one I left everything as default, which gives an ext4 filesystem. On the other I changed it to use btrfs, but otherwise left it as defaults."
1748021,2018-02-19 22:17:46 UTC,"After some discussion in https://forum.snapcraft.io/t/ubuntu-image-no-space-left-on-device/4092, I tried adding this line to my /etc/fstab:"
1748021,2018-02-19 02:41:08 UTC,"I've just tried again, using a kernel and gadget snap that I've compiled myself, I still get the same error:"
1748021,2018-02-08 02:43:59 UTC,"I've tried too with a different assertion, e.g. the dragonboard from ""https://assertions.ubuntu.com/v1/assertions/model/16/canonical/dragonboard"""
1748021,2018-03-07 14:59:22 UTC,"I am unable to reproduce your issue on any of my machines - I have tried on 16.04 ubuntu-image 1.3+16.04ubuntu2 deb, ubuntu-image snap 1.3+snap1 from beta and on 17.10 I have tried ubuntu-image 1.3+17.10ubuntu1 deb. In all cases the pi3 image builds correctly without any issues. I also have no explicit mount point present for /tmp during the runs."
1748021,2018-02-07 23:28:03 UTC,"On Wed, Feb 07, 2018 at 11:06:24PM -0000, seanlano wrote:

> I tried the deb package available in 16.04, and also tried it on a
> different 17.10 machine again from the deb package - still I get the
> same problem, ""No space left on device""
"
1748021,2018-02-07 22:06:04 UTC,"I should mention too, I installed it as a classic snap:"
1748021,2018-02-08 02:42:33 UTC,"Tried with just ""sudo ubuntu-image snap -c stable cm3.model"", still the same result:"
1748021,2018-02-07 23:06:24 UTC,"I tried the deb package available in 16.04, and also tried it on a different 17.10 machine again from the deb package - still I get the same problem, ""No space left on device"""
1748030,2018-02-08 18:32:19 UTC,"I've received requests from my community to restrict access to/hide interfaces where they are unable to affect changes.  From their perspective, it is much more clutter that they have to navigate around and/or misleading them to expect that they can make changes."
1748034,2018-03-30 20:12:19 UTC,Looking at the line numbers from the stack trace this appears to be from a previous version(6db74f). I've landed fixes since then to scriptset.py. I think this is a duplicate of LP:1751946 which has landed in master and 2.3. Could you please try to reproduce with the latest master/2.3?
1748034,2018-03-30 20:17:05 UTC,If you can reproduce it with master can you please provide a new stack trace?
1748034,2019-09-19 11:51:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1748036,2018-02-09 14:36:09 UTC,apport information
1748036,2019-08-05 07:13:10 UTC,"Yes, ~/.pam_environment is still not parsed in Ubuntu 19.04."
1748036,2019-08-05 03:51:36 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1748036,2019-06-05 13:25:59 UTC,I don't understand why this is not getting fixed. This bug means that a user with encrypted home directory can't have different locale settings than the system defaults.
1748036,2018-04-24 15:51:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748036,2018-02-09 14:39:44 UTC,"This is from a freshly installed virtual machine, for the purposes of this bug."
1748036,2018-02-09 14:36:07 UTC,apport information
1748036,2018-02-09 14:36:11 UTC,apport information
1748036,2018-02-08 02:54:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1748036"
1748036,2018-02-09 14:36:12 UTC,apport information
1748037,2018-07-02 09:18:14 UTC,I think:
1748037,2018-11-20 15:04:34 UTC,"This also affects nrpe checks because:
* directory perms
drwxr-x--- 11 ceph ceph 4096 Nov 10 12:22 /var/lib/ceph"
1748037,2019-05-30 11:55:10 UTC,Marking the charm-ceph task wontfix as the ceph charm has been removed from support for a while now
1748037,2018-07-02 09:17:19 UTC,Actually I'm wondering whether ch does do the right thing:
1748037,2018-02-08 01:18:18 UTC,Recreatable issue:
1748037,2018-07-02 09:15:09 UTC,The charms.ceph code for single osd upgrades (which I think is being used in this path) should deal with this:
1748042,2018-02-12 09:20:22 UTC,"Unfortunately this crash is not informative by itself, could you please provide more logs? A diagnostic snapshot would be even better."
1748042,2018-02-14 18:33:58 UTC,Asked Anatolii to fetch and provide data to you
1748042,2018-02-14 18:47:47 UTC,"Folks, Diag snapshot is useless. @Denis, let me know what exact logs is necessary"
1748042,2018-03-22 09:17:37 UTC,If you say it's under load then you should provide at least rabbimqctl report. Even better would also be screenshots from management plugin with messages rate graphics.
1748065,2019-12-06 04:49:45 UTC,@Mark
1748065,2020-08-13 14:46:01 UTC,Related: https://bugs.launchpad.net/kolla-ansible/+bug/1891364
1748065,2020-04-28 19:37:16 UTC,So one issue is the real problem is hidden. Second issue is the real problem of which may be multiple. Let's treat this bug report as fixing 'hiding problem' and then create some separate issues if applicable (as for mariadb we could only add retries there).
1748065,2020-04-28 19:35:07 UTC,So secondary1 never got keystone fernet nor ssh - primary keystone fernet docker logs:
1748065,2020-04-28 19:32:43 UTC,But there was also an earlier Mariadb failure (docker daemon communication error) so secondary1 was removed from run.
1748065,2020-04-28 19:31:03 UTC,"Task: keystone : Initialise fernet key authentication
Tags: keystone
Host: primary
Time: 2020-04-28 18:33:36"
1748065,2020-04-28 19:30:44 UTC,"Got this in CI on Train (pre upgrade to Ussuri):
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_a30/690920/18/check/kolla-ansible-centos8-source-upgrade-ceph-ansible/a30b33e/primary/ara-report/ara-html/"
1748065,2019-11-18 10:35:35 UTC,"Hi @Yang, just to be clear, when you are deploying the new host B, are you using kolla-ansible --limit <host B> ?"
1748065,2020-03-14 18:42:53 UTC,"I'm seeing this exact error on a fresh install (after calling destroy and cleaning up ceph) using train:
TASK [keystone : Initialise fernet key authentication] ************************************************************************************************************************************************************************************************************************
FAILED - RETRYING: Initialise fernet key authentication (10 retries left).
FAILED - RETRYING: Initialise fernet key authentication (9 retries left).
fatal: [n5.smcstaff.org]: FAILED! => {""msg"": ""The conditional check 'fernet_create.stdout.split()[2] == 'SUCCESS' or fernet_create.stdout.find('Key repository is already initialized') != -1' failed. The error was: error while evaluating conditional (fernet_create.stdout.split()[2] == 'SUCCESS' or fernet_create.stdout.find('Key repository is already initialized') != -1): list object has no element 2""}"
1748065,2019-09-10 09:14:19 UTC,Is there someone able to fix this?
1748065,2019-09-10 09:13:45 UTC,"It looks like at least one cause of this issue is when adding a new controller, it does not have a copy of the fernet key repository. If this node becomes the first node in the keystone group, then the task ""Initialise fernet key authentication"" will create a new key, but presumably fail in some unexpected way."
1748065,2019-11-13 09:39:30 UTC,@Mark
1748065,2019-09-09 21:12:05 UTC,This is still broken in stein and happened to me first when I added a control+compute node to an existing cluster. The mentioned workaround to make the new node first in the list of controllers worked. After the deployment I put the new node last again in the controller group and ran the reconfigure task to make sure all nodes know the desired configuration. Not sure that last step was necessary though.
1748065,2019-08-26 05:40:14 UTC,"We ended up having to change the order of the controllers specified in the multinode inventory file, which solved our issues.  The inventory file was returned to its original state after controller001 was re-deployed successfully.  So it appears that changing the order of the controllers in the multinode inventory file isn't too much of an issue, with the requirement that the first controller listed is a ""working"" node."
1748065,2019-08-25 23:15:53 UTC,"We needed to re-install our controller001 and ran into this issue when running ""deploy""."
1748065,2018-06-04 18:47:48 UTC,I have similar issue on Ocata
1748065,2018-02-27 08:12:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548182"
1748069,2019-06-06 11:39:46 UTC,"Logging appears to be working now, so I'm resolving this. Feel free to re-open."
1748097,2018-02-19 03:57:18 UTC,"Many thanks,"
1748097,2018-02-16 12:58:05 UTC,I reopened it.
1748097,2018-02-19 12:30:14 UTC,"> The behaviour I would suggest is that once a port (and not a network) is selected, the possibility of setting up security group is disabled.
"
1748097,2018-02-15 08:35:42 UTC,This is the intentional behavior of nova API.
1748097,2018-02-16 04:17:30 UTC,Please reopen.
1748103,2019-12-17 17:47:55 UTC,https://<email address hidden>/
1748103,2020-11-17 04:25:27 UTC,Still visible in Xenial 4.4.0-1118.132 AWS c5.metal
1748103,2020-10-13 09:21:23 UTC,"Based on comment #16, bump the timeout threshold to 240 second and resubmit to the upstream.
https://marc.info/?l=kvm&m=160258047509783&w=2"
1748103,2021-02-18 04:18:06 UTC,Seen with linux-oracle 4.15.0-1065.73~16.04.1.
1748103,2020-10-09 19:17:10 UTC,spotted on Bionic/azure-4.15 : 4.15.0-1097.107 : amd64
1748103,2020-04-23 11:54:49 UTC,"On E-KVM, the apic test will take about 1 minute to run:"
1748103,2020-03-25 04:42:44 UTC,Passed on E 5.3 AMD64
1748103,2020-03-24 04:55:57 UTC,"Failed on T-4.4 / X-4.4 AMD64
Passed on X-4.15 / B-4.15 AMD64"
1748103,2019-12-18 17:16:42 UTC,affects 4.15.0-1052.52	linux-kvm
1748103,2019-12-16 16:41:35 UTC,"In general this test fails usually across all clouds/metals Should be a higher priority to get this fixed,"
1748103,2020-10-13 07:01:38 UTC,"Looks like it will take about 40 seconds to run on Azure Standard-D48-v3, bump the timeout threshold to 60 or 90 should be able to solve this bug."
1748103,2019-09-24 14:49:41 UTC,Affects Oracle Disco 5.0.0-1003.4
1748103,2019-08-30 09:36:43 UTC,Didn't see this on B-OEM-OSP1 / Disco.
1748103,2019-03-28 12:33:11 UTC,Also have seen this in the following Azure instances
1748103,2019-03-27 07:01:24 UTC,Can be seen on generic kernel as well.
1748103,2018-04-09 11:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748103,2018-02-08 06:40:14 UTC,apport information
1748103,2018-02-08 06:40:12 UTC,apport information
1748103,2018-02-08 06:40:11 UTC,apport information
1748103,2019-11-08 09:23:06 UTC,Passed with B-Azure-5.0 Standard_F32s_v2
1748104,2018-02-08 06:32:22 UTC,https://review.openstack.org/#/c/534108/
1748105,2021-02-18 04:11:05 UTC,Seen with linux-oracle 4.15.0-1065.73~16.04.1.
1748105,2020-10-09 22:15:35 UTC,Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64
1748105,2020-04-24 09:01:00 UTC,"Typo in #8, recommended to bump it up to 900 seconds"
1748105,2020-04-24 07:53:58 UTC,3 more tests shows it will finish around 80 ~ 110 seconds on that azure instance (with Bionic 4.15 Azure)
1748105,2018-04-09 11:00:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748105,2019-11-29 11:33:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748105,2019-03-29 11:56:30 UTC,Spotted on X-KVM.
1748105,2020-04-24 04:45:36 UTC,It needs about 90 second to run on Azure Standard_D48_v3
1748107,2019-05-29 07:27:27 UTC,Spotted on AWS i3.metal with X-4.15 AWS kernel
1748111,2018-04-09 11:00:20 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748113,2018-04-09 11:00:25 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748115,2018-02-23 14:27:21 UTC,"Thinking more broadly, I'd suggest that this bug highlights an overarching concept..."
1748119,2019-06-16 16:08:50 UTC,"Hit the same crash with Debian Buster/testing and created upstream issue:
https://gitlab.gnome.org/GNOME/simple-scan/issues/109"
1748119,2018-02-08 07:18:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748132,2019-01-23 23:13:06 UTC,"Change abandoned by Miguel Lavalle (<email address hidden>) on branch: master
Review: https://review.openstack.org/542106
Reason: Given lack of follow up, abandoning this patch. The author can restore it if he wants to continue working on it"
1748132,2018-05-02 03:07:21 UTC,@ Miguel Lavalle (minsel)
1748132,2018-04-27 15:35:10 UTC,@Guoshuai Li
1748132,2018-04-27 14:22:57 UTC,"We deemed this as a good starter RFE. As such, it will be advertised in the next Neutron weekly meeting so new contributors can implement it"
1748132,2018-04-27 14:21:18 UTC,"After further discussion during today's drivers meeting, we have decided to approve this RFE"
1748132,2018-04-23 05:51:01 UTC,"@Akihiro
I am sorry, I am not clear about your question.
The default IP address of a router gateway will be assigned from an external network. I just hope that users can economize it.
This is not by modifying the default value, but through a new parameter of the API: {'external_ fixed_ips' ：[]}"
1748132,2018-04-20 14:28:49 UTC,"maybe a provider can give users an incentive to save ips. eg. make them pay for each ips.
anyway it's better to have a clarification from the submitter."
1748132,2018-04-20 14:26:04 UTC,@Guoshuai Li
1748132,2018-04-13 14:19:19 UTC,@Guoshuai Li
1748132,2018-03-12 04:51:16 UTC,@Miguel Lavalle @Brian Haley
1748132,2018-03-10 02:06:28 UTC,"I'm sorry, I haven't tried yet.
I will try next week."
1748132,2018-03-08 21:32:44 UTC,"@Guoshuai Li,"
1748132,2018-02-17 01:37:27 UTC,"Thanks Brian.
I did not notice the subnet service types, I think this is a good solution. I will try behind.
The difference between these two solutions lies in the physical network requirements. Multiple subnets may require multiple gateways or static routing or routing protocols. I think my thoughts may seem simpler."
1748132,2018-02-16 14:57:56 UTC,"Another way to save public IP addresses is to use subnet service types, https://docs.openstack.org/ocata/networking-guide/config-service-subnets.html - using that you would have multiple subnets on the external network, but some can only be used for certain types of ports.  That way a floating IP subnet could use global addresses, but a router gateways could use private addresses.  That way it is still possible to verify reachability of each router since it has an IP, which would not be possible with this proposed change."
1748132,2018-02-16 14:32:53 UTC,neutron patch https://review.openstack.org/#/c/540806/
1748132,2018-02-16 12:30:43 UTC,it sounds reasonable to me.
1748132,2018-02-10 04:58:18 UTC,"Yes, I really think so, because there is no default snat ip, so I can only rely on floating IP."
1748132,2018-02-09 17:34:14 UTC,This sounds a reasonable request.
1748132,2018-02-09 05:20:07 UTC,"yes, it's new feature...
Brian wants me to describe this."
1748132,2018-02-09 04:31:28 UTC,"Ah, I see. So you want to get floating IP. However it's new feature not bug."
1748132,2018-02-09 04:29:04 UTC,Why do you want router with external_gateway_info without external_fixed_ips? Is it useful external_gateway_info without external_fixed_ips?
1748132,2018-02-08 09:32:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/542106"
1748135,2018-03-07 16:48:27 UTC,"Since we are using all proposed for ruby I don't need to explicitly select vargant.
Also the recent rebuild made the old trigger target unavailable."
1748135,2018-03-07 13:31:54 UTC,"Due to ruby transition we need all proposed to get ruby in all of its variety for 2.5.
Hopefully the rest in proposed is not having issues, utherwise this will become a very long list of triggers."
1748135,2018-03-07 11:04:15 UTC,Again ...
1748135,2018-02-21 07:59:42 UTC,"Vagrant 2 still did not migrate.
So it blocks qemu again - new links to trigger the test of vagrant-mutate (done for qemu) against the new working vagrant version."
1748135,2018-02-08 09:37:28 UTC,"I discussed with Pitti, via adding the extra trigger of vagrant this will work.
So we will retry the tests originally triggered by distro-info and qemu but with &trigger=vagrant%2F2.0.2%2Bdfsg-2 appended."
1748139,2018-02-09 09:13:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/542739"
1748153,2018-03-09 14:15:55 UTC,This is a horizon issue. Retarget it to horizon.
1748156,2018-03-09 14:16:29 UTC,This is a horizon issue. Retarget it to horizon.
1748157,2018-04-06 15:15:14 UTC,The above issue is reported against bug 1761757
1748157,2018-04-07 01:01:01 UTC,"I reviewed thunderbolt-tools version 0.9.3-1 as checked into bionic. This
shouldn't be considered a full security audit but rather a quick gauge of
maintainability."
1748157,2018-04-07 22:09:29 UTC,Thanks for the review!
1748157,2018-04-09 07:50:15 UTC,"@Seth, Thanks for the MIR review. I removed the duplicated udev rules - bug 1762187 so I think we're now good to go."
1748157,2018-04-10 00:55:05 UTC,"On Sat, Apr 07, 2018 at 10:09:29PM -0000, Yehezkel Bernat wrote:

> I'd like to get a bit more details about some of the comments to
> understand what steps I can take to improve it. Please let me know if
> you prefer to take this discussion to another medium.
"
1748157,2018-09-13 20:27:48 UTC,reconfirmed with Seth that this is good to go.  Please add it to a seed  or as a dependency to some package.
1748157,2018-04-10 22:44:55 UTC,"On Tue, Apr 10, 2018 at 05:12:22AM -0000, Mario Limonciello wrote:

> > Did I get the interpretation of these rules correct?
> At a glance it looks like what you thought, but dig a little deeper.
> If it's not in the ACL it exits.
"
1748157,2018-04-06 03:24:42 UTC,One of the udev rules files appears to be untranslated:
1748157,2019-08-05 10:38:05 UTC,"@ping, has this MIR been completed?"
1748157,2019-08-05 11:49:01 UTC,"@cking - yes the comments by Seth and the later update of Doko a year ago are clear.
This is ready to land just someone needs to add a dependency or seed change to pull it in."
1748157,2019-08-05 11:49:37 UTC,"Per [1] this means ""In Progress"" until such a seed/dependency change is done."
1748157,2018-04-10 05:12:22 UTC,"> Did I get the interpretation of these rules correct?
At a glance it looks like what you thought, but dig a little deeper.
1. The rule calls tbtacl add (https://github.com/intel/thunderbolt-software-user-space/blob/master/tbtacl/tbtacl.rules.in#L2)
2. tbtacl add calls authorize: https://github.com/intel/thunderbolt-software-user-space/blob/master/tbtacl/tbtacl.in#L117
3. Authorize looks if it's in the ACL: https://github.com/intel/thunderbolt-software-user-space/blob/master/tbtacl/tbtacl.in#L66
"
1748157,2018-03-27 20:12:55 UTC,"(Sorry, I meant: https://gitlab.freedesktop.org/bolt/bolt/issues/78)"
1748157,2018-03-28 08:56:11 UTC,"Bolt upstream has contacted the thunderbolt-tools upstream about using the same ACL before starting writting their code but never got a reply on the topic apparently, let's see what they say but bolt is providing desktop integration and a command line utility and they plan to have the networking part integrated to network-manager so it should be a full solution for Ubuntu Desktop installations."
1748157,2018-03-20 14:53:51 UTC,Assigning to security as per the description...
1748157,2018-03-26 23:44:22 UTC,"Mario, thanks for the feedback. I'll try to get to the Intel Thunderbolt tools in time for the Bionic release."
1748157,2018-03-26 07:02:24 UTC,At the time Colin and I discussed getting thunderbolt-tools into Debian and then eventually into Ubuntu (& of course main via this MIR) bolt's GUI wasn't available yet and bolt was still under some pretty heavy development.
1748157,2018-03-21 10:47:51 UTC,"My 2 cents:
I think bolt and thunderbolt-tools must agree on the ACL (device whitelist for auto-approve on next connection) location and format and then I assume they can co-exist happily without stepping on each other's toes. Even if both try to authorize the same device on connection, it shouldn't matter much as the final result is that the device is authorized and ready to use."
1748157,2018-03-21 10:29:30 UTC,"AFAIK, Bolt (https://christian.kellner.me/2017/12/14/introducing-bolt-thunderbolt-3-security-levels-for-gnulinux/) will allow us to provide UI for managing security levels for Thunderbolt connected devices.  It uses the Intel provided sysfs devices for configuration.  If thunderbolt-tools also uses those devices, then the two should be able to co-exist, but I can see that there might end up being a fight over who owns the settings.  From a desktop perspective we want the UI provided by the GNOME Shell extension and Bolt so that users don't have to drop to a command line to configure their devices."
1748157,2018-03-20 19:17:26 UTC,"Will, can you provide some advice?"
1748157,2018-03-20 18:57:18 UTC,"@Seth, thunderbolt-tools was requested by Dell to be part of Ubuntu Bionic, I believe it's for some specific Dell laptops, but I can't provide any more specific details as Mario from Dell is on vacation right now."
1748157,2018-03-20 18:47:53 UTC,"Seems like ""bolt"" was handled before my MIR, which is perplexing as my request was for a Dell requested package that was filed earlier back in 2018-02-08 where as bolt was filed in 2018-02-27.  I'm not sure about bolt, this seems to be a Ubuntu package and not one that is in Debian."
1748157,2018-03-20 18:32:11 UTC,This appears to be duplicating functionality from bolt: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1752056
1748157,2018-03-27 20:11:48 UTC,"Seth,
It was disabled as the project is now handled at freedesktop's GitLab.
I opened an issue there: https://github.com/intel/thunderbolt-software-user-space/issues/60"
1748157,2018-02-08 15:52:46 UTC,Logs N/A for this type of bug.
1748157,2018-02-08 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748158,2018-02-08 17:50:30 UTC,"Flags in the config file are applied globally. The earliest-version flag in the config file is probably only useful for projects without branches, or with different configuration files on each branch. If you want to stop scanning on a particular branch, it is possible to set the earliest-version value in the sphinx directive triggering the scan of that branch. That might be more appropriate for your use case."
1748158,2018-03-14 14:48:40 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1748159,2018-03-14 14:47:46 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1748161,2018-05-28 11:26:35 UTC,s/MRE/MPs/
1748161,2018-05-28 11:26:23 UTC,"mimeo was already done, the two regular armhf fails are part of an MP now that we have a ""normal"" SRU update again.
Linking MRE to this bug ..."
1748161,2018-05-30 14:56:45 UTC,"Related MPs just all got merged.
Thanks!"
1748161,2018-05-28 12:38:38 UTC,"This is a tradeoff of effort vs gain - and in the past discussions were back and forth on trying to fix pgsql-common to make the lxd based tests work OR to hint them on britney.
While in a perfect world we'd prefer the former for now I proposed the latter.
Armhf is not a major target for postgresql and there never was an issue on armhf exclusive so far and on newer release this is fixed.
Also this isn't backportable that well to Trusty, and to do this only for Xenial feels wrong.
Really lets mask the known issues and be good."
1748161,2018-02-14 11:34:56 UTC,"Notes:
[12:29] <rbasak> cpaelzer: one note: when you do the next postgresql MRE, get the SRU reviewer to accept postgresql-common and want for binaries to be published before accepting the others
[12:29] <rbasak> Then the dep8 test will definitely run against the new one.
[12:30] <rbasak> (I don't think a versioned dependency relationship is needed here)
[12:30] <rbasak> s/want/wait/
[12:31] <pitti> that's not true
[12:31] <pitti> dependencies are satisfied from relelase/-updates as far as possible
[12:31] --> milardovich (~milardovi@190.193.40.124) has joined this channel.
[12:32] <pitti> you either need a versioned test dependency, or explicitly trigger the test to run against p-common in -proposed
[12:32] <rbasak> Oh.
[12:32] <pitti> (the latter appears better to me)
[12:32] <rbasak> OK we'll do an explicit trigger
[12:32] <rbasak> Thanks
[12:32] <pitti> i. e. see it fail, re-trigger armhf tests against p-common in -proposed, that should succeed and also validate the p-common SRU
[12:33] <pitti> although bumping the test dep in postgresql's d/tests/comtrol isn't wrong
[12:33] <cpaelzer> just as I did last week with some other migrations
[12:33] <rbasak> I generally shy away from bumping versioned deps to reflect bug fixes on the other side
[12:33] <pitti> (except the typoed file name, of course - tpying is hrad!)
[12:34] <rbasak> Seems like a recipe to madness
[12:34] <pitti> yeah, and breaks the clean backports, too
[12:34] <pitti> so I think manual trigger for that one round is just fine
[12:34] <rbasak> Yep"
1748161,2018-02-14 07:36:47 UTC,"List of past MRE updates were to a different extend always the same discussions on test fails came up - to provide the reasonability to add these hints.
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676"
1748161,2018-02-08 11:29:37 UTC,"I'm not sure on the bug tasks, but the MPs will certainly go on the queue of the SRU Team where they are at the right place."
1748161,2018-02-08 11:27:31 UTC,Linked two MPs which - if merged - will eliminate the ususal suspects and leave the actual real cases for discussion on each MRE/SRU activity.
1748161,2018-02-14 11:08:40 UTC,"We abandoned the trusty change and reduced the xenial change to mimeo.
On the next MRE we want to bundle backporting
- https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-common.git/commit/?id=fc40fc34ce
- https://salsa.debian.org/postgresql/postgresql-common/commit/07ea2e63241c9806
in postgresql-common and upload it together with the actual MRE"
1748162,2018-02-08 11:10:04 UTC,Demonstration here: https://github.com/stephenfin/reno-bug-1748162
1748162,2018-02-08 11:15:33 UTC,There's another variant available here: https://github.com/stephenfin/reno-bug-1748162-2
1748162,2018-02-08 17:39:19 UTC,"This is happening because the commit *is* on both branches and that commit isn't tagged so reno isn't recognizing it as the base of a branch. In OpenStack we always branch at a tag, but I guess that's not the case for the project you're looking at."
1748162,2018-03-14 14:48:47 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1748164,2018-02-08 17:47:05 UTC,"Have you tried setting earliest-version within the sphinx files? That should cause reno to stop scanning the branch when it sees that tag, which will mean scanning less of the history."
1748164,2018-03-14 14:48:54 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1748171,2018-02-08 11:45:11 UTC,"I assume you mean ""dolphin"" the file manager, not ""dolphin-emu"" the gamecube / wii emulator."
1748171,2018-02-08 12:12:08 UTC,"Yes, by dolphin I mean file manager.
Sorry for inconvenience"
1748174,2018-03-27 14:31:44 UTC,Can you reference any other cross platform app where this behavior is implemented?
1748174,2018-03-28 18:56:34 UTC,"@Nick
Don't know any, probably altium, which does support the space pilot I believe. But I never used altium and probably never will."
1748174,2018-03-27 16:25:14 UTC,@Maarten-
1748174,2018-02-14 15:29:35 UTC,"In short how the function could work:
1)	Hold down a hotkey
2)	Move your mouse to pan the schematic or board layout"
1748174,2018-02-13 16:13:37 UTC,"Thank you, but I don't understand what new navigation method you are suggesting."
1748174,2018-02-08 12:46:13 UTC,"Hi Nick, thanks for your response, I think you did not completely read my suggestion ;-)   I've added the kicad version."
1748174,2018-02-08 12:34:12 UTC,You can pan by using the scroll wheel and either shift or ctrl.
1748174,2018-02-08 12:32:25 UTC,Please add version information.
1748179,2018-04-23 08:12:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748179,2018-04-23 08:22:41 UTC,"Same issue here with a Dell wireless scanner. I don't think the hardware matters, as the images are scanned fine by Simple Scan, and I can save the scanned pages individually as PNG files."
1748182,2018-03-20 15:13:28 UTC,Firefox 58から、Ubuntuのパッケージ版でもEmojiOneMozillaが組み込まれるようになりました。
1748182,2018-03-21 01:41:13 UTC,"Ubuntu 16.04と18.04のFirefoxで確認してみました。
以前のように全部が白黒の絵文字ではなく、
色付きの絵文字と白黒の絵文字が混在した状態になっていますね。
スクリーンショットを添付します。"
1748182,2018-03-21 06:20:11 UTC,"> 色付きの絵文字と白黒の絵文字が混在した状態になっていますね。
"
1748182,2018-03-21 07:31:00 UTC,そうですね、Firefoxの開発ツールで確認した所、DejaVu Sansと表示されました。
1748182,2018-03-21 07:47:57 UTC,余談ですが、上記のlocal.confを18.04に入れると、添付ファイルのようにカラー絵文字が表示されます。
1748192,2018-02-20 23:47:59 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1748197,2018-02-12 12:04:12 UTC,Bionic support available with cs:cassandra;channel=edge
1748197,2018-02-15 11:14:34 UTC,Currently failing on OpenStack with:
1748200,2018-03-27 10:38:49 UTC,Verified on 9.2-mu5-proposed
1748200,2018-03-21 12:03:08 UTC,"For MOS9.x release:
https://review.fuel-infra.org/#/c/38102/"
1748200,2018-03-22 08:29:26 UTC,"Reviewed: https://review.fuel-infra.org/38102
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0"
1748205,2019-05-05 02:28:30 UTC,I'm the author of this suggestion so I thought I'd provide a status update.
1748205,2019-05-06 11:45:32 UTC,"@Brian, all two way communication between the board and schematic editors happen using the ExpressMail() and KiwayMailIn() methods derived from the KIWAY base class."
1748205,2018-02-09 00:51:10 UTC,"To try a proof of concept for integration with PCBNew.
1) Prepare an argv, arc style array with the parameters set as per the command line version.
2) Assuming the root schematic and PCB name are the same as the project name: save whether a schematic is open, close whatever schematic is open. Close the file in PCBNew.
3) Call RenumKiCadPCB as an external function with the standard argc, argv c style array.
4) If no error returns, open the PCB file and open the last schematic (assuming one was open) which was open before invoking RenumKiCadPCB."
1748205,2018-02-08 18:29:58 UTC,I am sorry but I keep getting a bounceback from my email.
1748205,2018-02-08 15:32:26 UTC,Thanks. I'll try track that down.
1748205,2018-02-08 15:03:10 UTC,"On 08/02/18 15:46, Brian Piccioni wrote:

> I don't know how else to ask this but I wrote a c program RenumKicadPCB
> which renumbers reference designations on the PCB geographically and
> back annotates the schematic. A few bugs have come up and have been
> fixed. It is very fast and flexible, works with nested sheets, and so
> on. You can select various numbering schemes, different top and bottom
> ref designations, and so on.
"
1748205,2018-02-08 17:51:55 UTC,"This would be a great feature for KiCad but I'm less than thrilled about using an external executable to do it.  I would prefer that this be integrated into the board editor.  Given that we have support for passing information between the schematic and board editors, using an external tool doesn't really fit into what most users expect from KiCad.  I'm not flat out rejecting it but it will take a lot of convincing to make me accept another external executable when I'm trying to find the time to eliminate the external executables that we already have."
1748206,2018-03-21 13:04:06 UTC,"For MOS9.x release:
https://review.fuel-infra.org/#/c/38103/"
1748206,2018-03-22 08:25:03 UTC,"Reviewed: https://review.fuel-infra.org/38103
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0"
1748206,2018-03-27 10:39:34 UTC,Verified on 9.2-mu5-proposed
1748213,2020-05-24 21:45:31 UTC,Has no one found a better solution for this in the last 2 years? The official documentation makes no reference to if these other values are reasonable or not: https://www.raspberrypi.org/documentation/configuration/config-txt/video.md (under lcd_rotate)
1748220,2018-02-08 21:40:25 UTC,"I'll add a check at 'info' level to the review-tools for now. This will not block anything but will give the store something to look at if it chooses to. The store may want additional support from the tools on this, which is fine, and we can discuss that if/when the store implements its portion."
1748224,2018-02-08 16:07:41 UTC,Thanks for reporting this Dmitry. I'm good with approving it.
1748224,2018-02-12 22:09:12 UTC,"+1, don't think spec is needed here."
1748224,2018-02-12 22:09:22 UTC,jlvillal and TheJulia are good with approving this w/o a spec.
1748227,2019-10-11 15:04:42 UTC,"EG 3.3
I just spotted a super simple way to address part of this from looking at the credit card payment page.  The part where we make it easier to set preferences/defaults for notification preferences from the place hold screen."
1748227,2018-02-13 20:02:41 UTC,"What if, during the hold placement process, the system checks to see if different notification options were used for this hold than are set in their default - if so, it asks it then adds a message to the hold confirmation screen with a link to the hold notification preferences page?"
1748227,2018-11-01 21:48:37 UTC,This should be resolved as part of the work being done for https://bugs.launchpad.net/evergreen/+bug/1570072
1748227,2019-10-11 16:15:03 UTC,"Working branch that adds links to streamline setting/changing email address from place hold form.
user/stompro/lp1748227_hold_simple_change_email
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1748227_hold_simple_change_email"
1748254,2020-07-28 13:15:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748260,2018-10-23 15:38:30 UTC,Has anyone been able to confirm that this problem is indeed fixed after 3.0.3?
1748260,2018-02-08 18:50:11 UTC,"This sounds like a duplicate of bug 1745190, or very close to that -- however, Terran you identify a wrinkle that the original report doesn't (CONS level search vs. scoped search).  If I have a chance today or tomorrow I'll look into both a little further."
1748260,2018-02-08 18:54:07 UTC,"Terran,
There were a number of fixes related to availability that were added to 3.0.3. bug 1730758 was one. Despite its title, it was not restricted to Located URIs, but was also related to any record with a bib source (in our case, all records). Also bug 1736419, where I mentioned a limit to available problem down in the comments that appeared to be fixed by the time we were done merging all of the fixes."
1748260,2018-02-08 18:58:32 UTC,"Thanks Andrea and Kathy, I was looking at the others and this one seemed to be slightly different to me. Glad to know it's fixed in 3.0.3!"
1748260,2020-12-17 23:34:02 UTC,This is no longer a problem - marking Won't Fix
1748260,2018-10-23 19:37:43 UTC,I searched on our test server running 3.2:
1748265,2019-05-22 19:53:54 UTC,I tested Bill's patch along with the changes that he made in my original patch and everything works perfectly.  A signedoff branch of Bill's patch is at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1748265-hold-list-sms-carrier-signoff
1748265,2019-05-29 15:14:02 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Garry, Dawn, and Bill!"
1748265,2019-03-08 15:43:36 UTC,"Thanks Gary, Thanks Dawn."
1748265,2018-09-13 19:35:30 UTC,I just found out the patch was not applied when I tested.  I will test again.
1748265,2018-09-14 17:01:54 UTC,"I have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>"
1748265,2018-09-13 19:18:23 UTC,I tested this and I still do not see the SMS carrier as an option in the dropdown list of the column picker on the holds screen in the patron account.  Please let me know if I am not looking in the correct place.
1748265,2018-06-03 20:05:39 UTC,Proposed patch at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/LP1748265_sms_carrier_in_patron_holds_list
1748265,2018-09-13 19:34:19 UTC,"We may have been seeing a problem with our test server when we tested this, we will try again."
1748265,2018-09-12 18:30:05 UTC,I am testing this bug patch.
1748268,2018-02-10 13:30:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748273,2018-02-08 20:33:22 UTC,Can you please share the output of the following commands?
1748273,2018-02-09 02:30:52 UTC,"I tryed again. The dialog is not freezed but the problem is that the folders in top left are not working (for exampled, downloads) but the ones in the bottom left are working (like the other Downloads link)"
1748273,2018-02-09 16:38:44 UTC,"Right, I'm seeing the problem too."
1748273,2018-02-13 14:35:12 UTC,"+1, the same issue"
1748273,2018-02-09 16:59:07 UTC,Bug report against the snapcraft-desktop-helpers: https://github.com/Ubuntu/snapcraft-desktop-helpers/issues/23
1748277,2018-02-13 17:59:14 UTC,I've pushed up a branch here that should resolve this: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1748277-patron-reg-long-field-doc
1748277,2019-05-22 20:13:10 UTC,"Patch didn't apply, but I was able to rebase it:"
1748277,2019-05-22 20:15:51 UTC,"I note that with this patch, when you edit a new patron, the action bar is no longer fixed, though it remains fixed when you are editing an existing patron."
1748277,2019-05-22 20:20:02 UTC,"Also, perhaps eg-help-popover should be used nowadays; the existing mechanism for displaying field documentation predated that directive."
1748277,2020-01-15 18:22:12 UTC,+1 to using the eg-help-popover instead
1748277,2021-02-09 22:41:08 UTC,Removing pullrequest as this would be better served with  eg-help-popover
1748280,2018-07-12 19:52:41 UTC,arm64 maps to AARCH64.
1748280,2018-07-12 17:40:35 UTC,"On the surface, it seems like this is something we could check for in the libvirt driver and skip the soft reboot timeout cycle if ARM64. The question I have is, which architecture fields does ""ARM64"" map to in nova? ARMV6 or ARMV7 or ARMV7B or AARCH64 or all of them? Or one that I missed? [1]"
1748280,2018-07-03 22:56:22 UTC,This affects systemd-fsckd autopkgtest
1748280,2018-07-03 22:56:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748280,2018-02-14 08:31:40 UTC,"This looks like breaking autopkgtest, at least for unattended-upgrades:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/u/unattended-upgrades/20180213_054128_4e1c0@/log.gz
...
autopkgtest [05:40:32]: test test-systemd.py: [-----------------------
bash: line 1:  5110 Killed                  /tmp/autopkgtest.wwbI8q/build.hcW/src/debian/tests/test-systemd.py 2> >(tee -a /tmp/autopkgtest.wwbI8q/test-systemd.py-stderr >&2) > >(tee -a /tmp/autopkgtest.wwbI8q/test-systemd.py-stdout)
autopkgtest [05:40:32]: test process requested reboot with marker InstallOnShutdown
autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...
File missing : /var/log/unattended-upgrades/unattended-upgrades.log
InstallOnShutdown did not run
autopkgtest [05:41:03]: test test-systemd.py: -----------------------]
autopkgtest [05:41:04]: test test-systemd.py:  - - - - - - - - - - results - - - - - - - - - -
test-systemd.py      FAIL non-zero exit status 1
..."
1748280,2018-02-15 08:27:29 UTC,Maybe not using the --nova-reboot until it is fixed could make the test bed work for u-u and other packages.
1748287,2018-04-22 08:50:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748287,2018-04-22 09:20:26 UTC,"I observe the same behavior with Nemo 3.6.5-1 amd64, Ubuntu 18.04, GNOME 3.28.1, theme Adwaita (default).
When I write this it makes me think to change the theme: bingo! the renaming selection is normal with Ambiance or Radiance."
1748287,2018-05-06 17:05:00 UTC,"I now have Lubuntu Next 18.04, and also have Nemo version 3.6.5-1, and still have the same issue."
1748296,2021-01-14 04:26:40 UTC,I hit this today on QEMU head. The problem appears to crop up when:
1748297,2018-02-14 18:18:42 UTC,"We've made substantial changes to the core protocol, so older clients should not be able to work with newer servers, and newer clients will not work with older servers. However, the newest client version should of course not crash when entering an old server, it should just disconnect."
1748298,2018-02-09 17:08:23 UTC,Stracing the app reveals what the problem is:
1748298,2018-02-09 17:24:23 UTC,"The same operation (opening a template file) succeeds with libreoffice installed as a deb, and the template is read-only too. The major difference between the two is that in the case of the deb the error code when trying to open the file in write mode is EACCES, whereas for the snap it's EROFS. I guess libreoffice handles those two situations differently."
1748305,2018-02-08 23:18:33 UTC,"Review in progress for https://review.opencontrail.org/39601
Submitter: <email address hidden> (<email address hidden>)"
1748305,2018-02-23 05:19:46 UTC,"Reviewed:  https://review.opencontrail.org/39601
Committed: http://github.com/Juniper/contrail-controller/commit/0a5c9a50145b9b4378f6494a851d6e2ed05be4ef
Submitter: Rudra Rugge (<email address hidden>)
Branch:    R2.21.x"
1748311,2018-02-14 10:11:47 UTC,This may be related to https://bugs.launchpad.net/kicad/+bug/1728272 where there is an old branch for testing. I am not sure if this includes direct scaling in pcbnew or not.
1748311,2019-02-25 12:36:19 UTC,"Yes, completly the same feature.request (I had reported the above)."
1748311,2019-02-25 22:56:41 UTC,Yes that is correct. My suggestion will probably be covered if we have support for SVG items that are resizable and can be put on any board layer.
1748311,2019-03-04 09:52:27 UTC,Duplicate of https://bugs.launchpad.net/kicad/+bug/1817565 and https://bugs.launchpad.net/kicad/+bug/1786787 ?
1748317,2019-12-03 11:37:06 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version.
1748317,2020-02-02 04:17:27 UTC,[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]
1748324,2018-02-09 22:46:20 UTC,This is actually typical pip behavior if sub-dependencies aren't all specified with hashes which was the case here. This can be closed.
1748327,2018-04-02 13:19:00 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1748327,2018-03-15 16:58:54 UTC,"Reviewed:  https://review.openstack.org/542856
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91a66c2381cd9d365824080009df7c55f19e07ad
Submitter: Zuul
Branch:    stable/pike"
1748327,2018-04-20 13:14:43 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1748327,2018-02-16 05:57:15 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc2 release candidate.
1748327,2018-02-09 00:33:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/542508"
1748327,2018-02-09 14:40:05 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/542856"
1748327,2018-02-09 13:22:05 UTC,"Reviewed:  https://review.openstack.org/542508
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b516c48fdfbc1b54cd55f17b1a446c5c7d661f11
Submitter: Zuul
Branch:    master"
1748327,2018-02-16 04:52:27 UTC,"Reviewed:  https://review.openstack.org/543507
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3eef6b88a7d21c1b1e5b4399d255b3b17688b778
Submitter: Zuul
Branch:    stable/queens"
1748332,2018-02-09 02:22:14 UTC,"I suspect that since you provided no network configuration to the bridge, then it is considered unconfigured. networkctl seems to confirm."
1748332,2018-02-09 02:40:49 UTC,"Actually it might be nice in this case to, in fact, bind the carrier to eth1."
1748332,2018-02-09 18:37:05 UTC,I can confirm that this is a workaround (specifying an address to configure the bridge with):
1748332,2018-02-09 19:18:43 UTC,"This also affects VLANs, I think I've seen cases in which they would remain down if there is no configured address."
1748332,2018-03-17 02:02:20 UTC,Do we have another workaround ?
1748332,2018-04-12 19:38:48 UTC,"As E. MAS (erwan-mas) wrote, it is very common setting, and in case of virtualization, container, etc if we need to define IP address on host, it is a security leak, because with that IP address from the virtual OS can access the host, that is a big problem."
1748332,2018-07-11 06:07:39 UTC,I've ran into this issue too and have been looking around for a workaround.
1748342,2018-02-12 04:50:49 UTC,"Hi,"
1748342,2018-02-09 02:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748346,2020-07-26 13:46:04 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1748346,2020-09-25 04:17:19 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1748373,2018-02-13 17:46:52 UTC,Done. The upstream kernel appears to have fixed this bug. Thank you!
1748373,2018-02-13 16:30:08 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1748373,2018-02-09 17:20:38 UTC,apport information
1748373,2018-02-09 17:20:37 UTC,apport information
1748373,2018-02-09 17:20:35 UTC,apport information
1748373,2018-02-09 17:20:34 UTC,apport information
1748373,2018-02-09 17:20:33 UTC,apport information
1748373,2018-02-09 17:20:32 UTC,apport information
1748373,2018-02-09 17:20:31 UTC,apport information
1748373,2018-02-09 17:20:30 UTC,apport information
1748373,2018-02-09 17:20:20 UTC,apport information
1748373,2018-02-09 17:20:27 UTC,apport information
1748373,2018-02-09 17:20:26 UTC,apport information
1748373,2018-02-09 17:20:25 UTC,apport information
1748373,2018-02-09 17:20:23 UTC,apport information
1748373,2018-02-09 17:20:22 UTC,apport information
1748373,2018-02-09 17:20:19 UTC,apport information
1748373,2018-02-09 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748373,2018-02-09 08:25:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1748373,2018-02-09 17:20:29 UTC,apport information
1748378,2019-07-09 01:53:16 UTC,"Since this report was filed, the test was fixed as I cannot get it to fail locally under stress."
1748389,2018-02-09 08:26:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/542711"
1748389,2018-02-09 10:04:51 UTC,"I think this was not the case for neutron lbaasv2 api, atleast with the CLI what I can see."
1748389,2019-12-24 00:41:43 UTC,"Change abandoned by liyi (<email address hidden>) on branch: master
Review: https://review.opendev.org/542711"
1748393,2018-02-09 10:36:06 UTC,apport information
1748393,2018-02-09 10:36:19 UTC,apport information
1748393,2018-02-09 10:36:17 UTC,apport information
1748393,2018-02-17 19:15:28 UTC,Thanks for the reply and sorry that it took a bit longer to find time for testing.
1748393,2018-02-09 10:36:12 UTC,apport information
1748393,2018-02-09 10:36:10 UTC,apport information
1748393,2018-02-09 10:36:08 UTC,apport information
1748393,2018-02-13 16:31:26 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1748393,2018-02-09 10:36:05 UTC,apport information
1748393,2018-02-09 10:36:14 UTC,apport information
1748393,2018-02-09 10:36:00 UTC,apport information
1748393,2018-02-09 10:35:57 UTC,apport information
1748393,2018-02-09 10:35:53 UTC,apport information
1748393,2018-02-09 10:35:50 UTC,apport information
1748393,2018-02-09 10:35:48 UTC,apport information
1748393,2018-02-09 10:35:46 UTC,apport information
1748393,2018-02-09 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748393,2018-02-09 10:36:02 UTC,apport information
1748395,2018-02-09 09:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748395,2018-02-09 11:41:31 UTC,Verified with older kernel (3.13.0-117-generic) on the same amd64 system and this issue still exist.
1748395,2020-01-06 07:45:10 UTC,Precise ESM ends April 2019. Closing this bug.
1748398,2018-02-09 09:16:24 UTC,"On amd64 this looks to be a race between creating disk partitions and having usable devnodes created by udev (wait, check?):"
1748398,2018-02-09 09:19:19 UTC,On s390x the test case still(!) does not handle the fact that there is no grub used:
1748408,2018-03-31 06:16:27 UTC,"For how long do the Xenial HWE kernels stay in the ""proposed"" ?"
1748408,2018-03-23 15:37:11 UTC,Proposed kernels show the same improved behaviour as the earlier test kernels.
1748408,2018-03-19 17:36:47 UTC,"Running the -proposed kernel on two machines now, will provide the results in a couple of days."
1748408,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1748408,2018-03-19 11:42:40 UTC,Together with the new Artful kernel there was also a new HWE kernel that is based on the new Artful kernel (4.13.0-38.43~16.04.1). Verification can be done with that kernel as well. Just the automatically generated messages are for the base kernels where the patch was applied to. The HWE kernel is a backport of the Artful kernel right now.
1748408,2018-03-19 11:21:15 UTC,@Stefan: I haven't reproduced the issue on Artful and I don't have an environment to do so. The original issue is for the HWE kernel on Xenial and only for that I can perform verification.
1748408,2018-03-19 10:58:34 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1748408,2018-03-09 08:14:12 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090701.html"
1748408,2018-03-07 10:48:36 UTC,"The slow leak will probably be tolerable for the time being, having those two patches added to the kernel would surely be a pretty valuable step that I think should be done now. My target still is Xenial with the hwe kernel, though. If you need to go via Artful to fix that, well, go ahead."
1748408,2018-03-07 09:33:50 UTC,Do you think an Artful SRU request should be sent for commits 2b9478 and 62b4c66?  Or would you like to investigate the slow memory leak further?
1748408,2018-03-06 09:54:05 UTC,"The test kernel solves the issue in the same way as my own kernel earlier, i.e. we still seem to have a very slow running memory leak with this kernel. I'm also seeing this slow leak when I replace the in-tree i40e driver by an upstream version (2.3.4), so either it is unrelated or contained in both."
1748408,2018-02-27 18:09:16 UTC,"I built a test kernel with commits 2b9478 and 62b4c66. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1748408"
1748408,2018-02-26 15:55:27 UTC,"After running for a couple of days, it seems that we are still seeing the slow memory leak similar to what was noticed in >= 4.14 earlier with the patched kernel. But it won't be possible for me to bisect at that rate."
1748408,2018-02-26 08:38:48 UTC,I have a significant memory leak after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series for Ubuntu 16.04 server with Ethernet controller Intel X710 for 10GbE SFP+
1748408,2018-02-09 14:22:28 UTC,"Thanks for the update.  I requested testing of the mainline kernel to see if there is a commit in mainline that fixes the bug, which we could backport back to 4.13."
1748408,2018-02-22 05:56:17 UTC,"Reading the thread further, we seem to need two patches, see https://www.spinics.net/lists/netdev/msg462051.html, so I'm going to add bc6d6fd2f916a0794ae4c44b28e14e2d172e05e0 into the build, too.
Will try that on top of b32038eb34ee42fd8056f99f88652270f6667996 (tag: Ubuntu-4.13.0-32.35)."
1748408,2018-02-21 20:37:46 UTC,"I built a test kernel with commit 2b9478ffc550f1.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1748408"
1748408,2018-02-21 18:25:51 UTC,A colleague found that this seems to be a known issue:
1748408,2018-02-21 15:47:49 UTC,"Sorry for the delay, bisecting took longer than planned, but I now have the result:"
1748408,2018-02-20 16:16:40 UTC,"@Dr. Jens Harbott, Just let me know if you need assistance with the bisect between 4.11 and 4.12.  I can build the kernels for you.  I would say the next step would be to test the 4.12 release candidates to narrow down the issue further.  4.12-rc1 is available here:"
1748408,2018-02-19 22:09:36 UTC,"Oh and I have also experienced random, unexplained OOM crashing of squid process recently on two separate machines (one i386 and one amd64) which seem to coincide in time with the upgrade from kernel 4.10 to 4.13"
1748408,2018-02-19 22:06:52 UTC,"Hi guys. I'm experiencing problems with 4.13.0-36 on a cloud server (x64) with dynamic ram management. The server is provisioned to use up to 12GB of RAM, but it got so bad that only 1GB was visible, causing everything to a halt while swap usage went through the roof. Could it be related?"
1748408,2018-02-12 10:32:58 UTC,So here are the first results:
1748408,2018-02-09 14:23:24 UTC,"Ok, nevermind the aufs issue, I got that resolved. Should have some results with mainline kernels in a couple of days."
1748408,2018-02-09 13:53:06 UTC,"@Joseph: I did test 4.15.2, but some things are failing, in particular docker because of lacking AUFS support, so I need to build a kernel myself I guess, which will take a bit."
1748408,2018-02-09 12:24:51 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].
1748408,2018-02-23 07:31:44 UTC,"O.k., confirming that this series of patches fixes the issue:"
1748409,2018-02-22 12:59:24 UTC,i'm looking for a workaround.
1748409,2018-02-20 03:53:39 UTC,"no surprise the installed bionic uses the same static ip address i gave for the mini.iso to use.  same issue on desktop and laptop.  for the desktop i expect i can just populate /etc/network/interfaces and uninstall NetworkManager.  i don't think that's a good solution for the lappy tho.  can anybody clue me to a workaround, to fix/complete my laptop bionic configuration?  i think ssb is the broadcom wifi driver module, when running bionic it's already listed in lsmod but only eth0 shows up in the network applet or /sys/class/net, when running trusty the lappy wifi works, APs are listed and it connects to my modem just fine, seems likely i can just copy some missing bit of configuration from the trusty install, but what?"
1748409,2018-02-09 12:30:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1748415,2021-01-19 17:16:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1646694, so it is being marked as such."
1748417,2018-02-09 10:37:14 UTC,seems more appropiate to file as question
1748421,2018-03-18 09:54:49 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1748429,2019-09-28 15:58:48 UTC,Hi there! No this is no longer happening on new LO snap installations :)
1748429,2018-02-09 11:49:27 UTC,"Regarding the icon path, that's expected: if the icon was set to ""libreoffice-writer"", the deb package for libreoffice wasn't installed, and the current theme didn't have an icon for libreoffice-writer (on my setup only the HighContrast theme has one), then the shell wouldn't be able to display an icon for the app. Snaps can't install icons under /usr/share/icons/, and the shell isn't aware of icons shipped inside snaps."
1748429,2018-02-09 11:55:45 UTC,What theme does the rest of your desktop use?
1748429,2018-02-09 12:04:47 UTC,GTK Community theme (https://github.com/Ubuntu/gtk-communitheme)- I see - changing to ambiance did the trick. Now the snap uses the ambiance gtk theme.
1748429,2018-02-09 14:59:05 UTC,"> The theme matching works only for ambiance?
"
1748429,2018-02-09 15:01:57 UTC,"> Regarding the icons, most debs - if not all - use the free desktop
> spec. And it works very well with Humanity icon set (which inherits
> hicolor in it's index) 99% of the apps work with relative icon paths,
> even if they are snaps. (this is just a user impression, I got no
> deeper understanding of how this works)
"
1748429,2018-02-09 15:02:52 UTC,I have updated the title of the bug to refer to the issue with themes only.
1748429,2019-08-24 13:45:33 UTC,"Is there any update for this bug? This is unbearably ugly on other Linux distros not having Ambiance etc, especially on KDE"
1748429,2019-09-24 14:24:40 UTC,Is this still an issue? Please run `snap connections` and ensure that the following appears in the output:
1748429,2019-09-28 17:23:41 UTC,"Awesome, thanks for confirming :)"
1748441,2019-10-07 00:46:27 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1748441,2019-10-07 22:43:49 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1748441,2018-02-14 14:59:46 UTC,"Also
    i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/s/snapd/20180214_134917_2ab53@/log.gz"
1748444,2018-02-09 16:24:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1748444,2018-02-16 03:50:04 UTC,"------- Comment From <email address hidden> 2018-02-15 22:48 EDT-------
*** Bug 164712 has been marked as a duplicate of this bug. ***"
1748444,2018-05-08 16:52:22 UTC,I can't find this linux-power package on packages.ubuntu.com nor see how it conflicts with cpufrequtils.  And why is that package ppc only?
1748447,2018-04-12 22:34:17 UTC,"!!!!!!!!!!!!!!!!!!!!!!!!!
Ubuntu 18.04 !!! On ubuntu Standard 18.04."
1748447,2018-04-12 22:33:50 UTC,"!!!!!!!!!!!!!!!!!!!!!!!!!
Ubuntu 18.04 !!! On ubuntu Standard 18.04."
1748447,2018-02-26 19:22:53 UTC,This bug was fixed in the package ubuntu-mate-settings - 18.04.8
1748447,2018-02-26 17:39:49 UTC,The upstream issue is here:
1748447,2018-02-13 05:28:56 UTC,"Yes, it is mate-hud. A 'killall mate-hud' brings back the desktop."
1748447,2018-02-10 14:07:08 UTC,"I've checked if it's the same behavior as Matt described in <a href=""https://bugs.launchpad.net/bugs/1734271"">bug #1734271.</a>
I can't reproduce his behavior. The desktop works again with no limitations. I supposed that the freezing event is dependent on other input conditions. I'll check if my problem is reproducible."
1748447,2018-02-09 16:24:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1748447,2018-02-09 15:01:56 UTC,"There is another behavior: Audacious remember its current song position, when the problem occurs (as if Audacious would gone to pause mode). Audacious plays all songs again while I do nothing after the problem occurs. When I re-login Audacous doesn't remember all played songs before I logged out, it starts playing at the song position I described first."
1748447,2018-02-09 14:33:45 UTC,"Here are all my installed programs, maybe this helps.
Additionally installed by hand are:
- audio-recorder (compiled by myself)
- renoise software
- VMware Workstation 12.5.8 (patched for the current kernel)
- some Mate themes
- some fonts"
1748447,2018-02-10 17:35:32 UTC,The freeze event occurs again. I pressed [Ctrl]+[Alt]+[left mouse button]. Programs are callable from an icon of the desktop or panel but not from the menu. I can switch to the text terminal with [Ctrl]+[Alt]+[F1] and switch back again to the desktop but other typed characters in a text line are ignored. The /var/log/syslog messages at this time shows:
1748452,2018-08-29 12:44:30 UTC,Also looks like this would have caught https://review.openstack.org/#/c/597427/
1748453,2018-04-18 11:21:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748453,2018-04-18 11:22:59 UTC,"Occurred whilst trying to reinstall CUPS using these commands:
sudo apt purge cups cups-client cups-bsd
sudo apt purge hplip hpijs printer-driver-gutenprint"
1748464,2018-08-03 03:45:00 UTC,"Thanks, Kathy.  I have opened a new bug #1783151"
1748464,2018-07-23 15:47:39 UTC,"Mike's explanation in comment #1 matches up with the behavior I've seen for various alerts in the web client, not just the inactive barcode alert. I think it makes sense for the alert to only show when you first retrieve the patron and not show again unless you've moved on to another patron and returned."
1748464,2019-04-05 14:04:53 UTC,"We are currently using 3.1.6 and had a question about retrieving a patron account with two different barcodes from a recently migrated library. When I tested in the web client, I was able to retrieve the account with the inactive barcode (both by patron search and using the checkout function) without any alert message displaying in either case. The checkout entry box was active for checkout, so there was absolutely no indication that the account was retrieved with an inactive barcode."
1748464,2018-07-23 15:35:22 UTC,"Dawn,"
1748464,2019-01-15 19:47:36 UTC,Issue still present on latest release
1748464,2018-02-12 13:27:17 UTC,"Mike and John,
    The most common reason why a barcode appears as Inactive is because it was lost. Though far less common, sometimes patrons report a library card stolen. In both cases staff needs to know immediately if someone tries to use the older barcode so this particular alert is on par with a Blocked alert in terms of importance. It needs to appear immediately when the record is retrieved."
1748464,2018-02-09 18:25:33 UTC,"Mike,"
1748464,2018-02-09 16:26:04 UTC,"John, does this still happen if you search for and load a different user between the two searches for the same user via an inactive barcode?  Does simply hard-refreshing (shift-reload) the page between the searches make the alert work as expected? If those are true, I suspect this is happening because the user object and state info are cached in (probably) the patron service, so the alert page is marked as already ""seen"" for the current user.  If that's the case, I'm not surprised that the alert doesn't show on the second search+selection of the same user with an alert.  And, if that's the case, I'm not sure that's a bug since the client has already alerted the staff to the, um, alert.  I'd think of that as an enhancement over the XUL version, but would like to hear front-line opinions!"
1748464,2018-07-23 15:21:08 UTC,This may be a separate request but holds can be placed with an inactive card without any notification. Staff would like to see an alert when an inactive card is used anytime.
1748465,2018-02-19 12:43:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748465,2018-03-23 20:19:27 UTC,Reverting unexplained bug closure; please provide an explanation of what fixed the bug if this change is incorrect.
1748469,2018-03-08 17:59:20 UTC,This issue was fixed in the openstack/tripleo-heat-templates 5.3.10 release.
1748469,2018-02-21 12:58:01 UTC,"Reviewed:  https://review.openstack.org/542816
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7582128434f220c747d98c02626399de22a218c3
Submitter: Zuul
Branch:    stable/newton"
1748476,2018-02-20 09:43:01 UTC,Regression tests results were successful.
1748476,2018-02-21 19:09:21 UTC,This bug was fixed in the package linux-azure - 4.13.0-1011.14
1748476,2018-02-21 20:37:40 UTC,The package has been published and the bug is being set to Fix Released
1748478,2018-02-13 08:42:59 UTC,"4.13.0-1011.15 - gcp
Regression test CMPL."
1748478,2018-02-21 19:09:04 UTC,This bug was fixed in the package linux-gcp - 4.13.0-1011.15
1748478,2018-02-21 20:38:08 UTC,The package has been published and the bug is being set to Fix Released
1748481,2018-02-21 19:08:44 UTC,This bug was fixed in the package linux-oem - 4.13.0-1021.23
1748481,2018-02-21 12:34:09 UTC,We rely on the test result from Cert. team.
1748481,2018-02-21 20:30:37 UTC,The package has been published and the bug is being set to Fix Released
1748487,2018-02-12 20:04:31 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=198767
1748487,2018-02-12 19:44:16 UTC,"The commit was at one point applied upstream, but it seems it caused problems and was later reverted in commit 00c611def8748a0a1cf1d31842e49b42dfdb3de1. Your best bet is likely to file a new bug at bugzilla.kernel.org (developers may be ignoring new comments on closed bug reports)."
1748487,2018-02-27 11:50:56 UTC,same errors seen with 4.15.5 (4.15.0.11)
1748487,2018-02-09 17:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748487,2018-03-26 13:01:22 UTC,"Upstream thinks its solved now:
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/?h=linux-next"
1748487,2018-02-11 05:05:54 UTC,The acpi-support package has nothing to do with kernel patches.
1748487,2018-04-06 02:33:24 UTC,Still getting these errors with 4.15.0-15
1748495,2018-02-10 18:39:45 UTC,I can't reproduce this problem. It looks like the patch you linked to has merged. Is this still an issue?
1748495,2018-03-14 14:49:01 UTC,The bug tracker for reno has moved to storyboard: https://storyboard.openstack.org/#!/project/933
1748498,2018-02-09 17:28:40 UTC,"come to think of it, the mini.iso dhcp facility didn't work (separate bug filed), and i installed successfully after manual network configuration in mini.iso, so perhaps the installed system is also configured for static ip."
1748498,2018-02-09 20:25:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1748500,2018-02-20 23:55:05 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1748500,2018-02-20 23:56:01 UTC,"Hello, this machine is spewing Machine Check Events. I strongly recommend installing the mcelog tool and keeping a very close eye on the /var/log/mcelog file. This might represent hardware issues. (Perhaps as simple as a clogged heatsink, perhaps failing hardware.)"
1748501,2018-02-09 20:52:58 UTC,"Thanks for reporting. I've marked the xenial-backports project as also affected, so that this will show up in the list of requested backports. For more information on the backport process, please see https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport."
1748501,2018-08-28 11:04:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748503,2018-02-09 18:05:33 UTC,"Here is the strace output for ""eject -v -X sr0"" for comparison"
1748507,2018-02-15 13:49:30 UTC,"Reviewed:  https://review.openstack.org/544625
Committed: https://git.openstack.org/cgit/openstack/sahara/commit/?id=2729aeea218a33f25b369619bfc6dc42be265b59
Submitter: Zuul
Branch:    stable/queens"
1748507,2018-02-15 12:30:40 UTC,"Reviewed:  https://review.openstack.org/544622
Committed: https://git.openstack.org/cgit/openstack/sahara-image-elements/commit/?id=5a8a042c4a3779221850e1f42271091d515f00b7
Submitter: Zuul
Branch:    stable/queens"
1748507,2018-02-14 20:00:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544625"
1748507,2018-02-14 19:57:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544622"
1748507,2018-02-14 19:27:23 UTC,"Reviewed:  https://review.openstack.org/529442
Committed: https://git.openstack.org/cgit/openstack/sahara/commit/?id=e97e0abb2b15da0e0f7400c26ad75cb10afe319b
Submitter: Zuul
Branch:    master"
1748507,2018-02-14 18:25:01 UTC,"Reviewed:  https://review.openstack.org/543471
Committed: https://git.openstack.org/cgit/openstack/sahara-image-elements/commit/?id=6229ee0de96f7e6846815335bc198c1f24897d95
Submitter: Zuul
Branch:    master"
1748510,2019-10-15 11:13:58 UTC,As was explained above apparmor and the sandbox in general doesn't pretend to change UNIX permissions that access(2) is based on. Unless we plan to do library or syscall intercepts I don't think we can fix it.
1748510,2018-02-12 07:03:08 UTC,"My guess would be that `test` does a stat() and checks st_mode against provided flags, so it's like only reading the metadata. The actual blocking/sandboxing happens on calls that have side effects on the real data, eg. open()."
1748510,2018-02-13 00:16:32 UTC,"AppArmor intentionally does not mediate access(2) and similar system calls. While it might be feasible to give results for files, giving results for a directory would be error-prone."
1748518,2018-07-24 09:22:43 UTC,"Does this issue appear in LibreOffice 6.0.6 installed from ppa:libreoffice/libreoffice-prereleases ?
If yes, then please report this issue at https://bugs.documentfoundation.org and add link to bugreport here (click on +Also affects project)"
1748518,2018-06-04 14:07:01 UTC,Old bug in upstream libreoffice with the same symptoms: https://bugs.documentfoundation.org/show_bug.cgi?id=34814
1748518,2018-02-09 21:47:18 UTC,Note that this affects both 5.4.4.2 from the stable channel and 6.0.0.3 from the candidate channel.
1748528,2018-02-15 18:32:28 UTC,You can also use a label in loop control to change the item displayed:
1748534,2018-04-03 14:11:47 UTC,"Confirmed using 0.12.0, too, against a Pike deployment of Glance."
1748534,2018-04-04 00:13:48 UTC,proposed a fix https://review.openstack.org/#/c/558461 under review for this
1748534,2018-04-26 19:40:35 UTC,This issue was fixed in the openstack/openstacksdk 0.13.0 release.
1748537,2018-02-14 21:04:08 UTC,"We are experiencing this as well.  I am actually seeing 403 errors, and it appears the OpenLibrary API is blocking LWP at the user-agent level.  Here are some quick tests which make me believe this:"
1748537,2018-02-14 22:40:55 UTC,"Thanks, Josh.  I don't think we are hitting the rate limit, since it claims to be IP based, and requests from the same IP with a different UA string work fine, while our regular access has been down for days.  We have also experienced recently that LoC blocks requests with an ""LWP"" UA string, so this is apparently becoming more common as a basic means to block scripted harvesters/attacks."
1748537,2018-02-14 21:31:13 UTC,"The open library covers page does mention rate limiting resulting in 403 Forbidden responses.
https://openlibrary.org/dev/docs/api/covers"
1748538,2019-09-19 11:57:21 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1748542,2019-09-19 11:57:23 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1748543,2018-09-28 10:45:22 UTC,@nanook:
1748543,2019-07-10 22:31:23 UTC,"I still have not upgraded motherboard bios / microcode as last attempt failed, but now, without microcode from Ubuntu being installed but with a 4.18.0 kernel I still have installed because networking breaks with 5.0.x kernels on this machine, overclocking is again working."
1748543,2019-05-09 00:56:08 UTC,"      No, I have not."
1748543,2019-05-09 00:34:16 UTC,CPU microcode can be also be updated by the motherboard firmware. Have you upgraded your motherboard firmware recently and/or installed uefi capsules?
1748543,2019-05-09 00:17:13 UTC,"Just to report the situation has gotten worse with Disco Dingo, now i7-6850 will not overclock even with microcode purged.  Further, I have determined it is NOT a kernel issue because it will not overclock on the old kernel either.  So I have no idea what Canonical has done but I'm NOT a happy camper."
1748543,2018-10-09 22:56:53 UTC,"      Asus, my motherboard vendor flat out lies.  They say the i7-6850 on the
x99 platform is not vulnerable, yet it does test vulnerable to Spectre version
2 using the meltdown-specter.sh test script."
1748543,2018-10-01 19:56:14 UTC,@pragyan:
1748543,2018-09-29 23:54:18 UTC,"      Unfortunately, the new Microcode did not fix the overclocking issue on
an i7-6850k on an Asus X99A board.  Before and After of /proc/cpuinfo are
attacked as files."
1748543,2018-09-28 17:12:55 UTC,"From reports elsewhere in the Internet, made by Microsoft Windows users with KB4100347 installed. Behavior in Linux might be slightly different."
1748543,2018-09-28 10:54:12 UTC,      I will test this weekend.
1748543,2019-09-11 00:44:15 UTC,"At this point I compiled a mainline 5.1.0 kernel, both networking and overclocking are working with it."
1748543,2018-09-27 00:19:58 UTC,"      I am an overclocker with i7-6850k, specifically I have it on an Asus
board with all six cores running at 4.3 Ghz and reliably at that.  How do I
obtain this particular micorocode to test?  The last one caused the CPU to
run at 3.6 Ghz with microcode installed so it is running without microcode
form Linux and just what Asus supplies."
1748543,2018-09-25 22:50:37 UTC,"      Last time I queried Asus they told me their Microcode was not vulnerable
but the test script says it is."
1748543,2018-09-26 21:23:33 UTC,"Henrique
Do you have any reported issues with Ubuntu Bionic Beaver that ships with Intel's latest OS loadable microcode package 20180807a?
Thank you"
1748543,2018-02-10 02:31:54 UTC,"Robert, you have a -K part, which officially ""doesn't forbid"" overclocking as far as I know, and this is the only reason I have not immediately closed this bug as invalid."
1748543,2018-02-10 02:34:48 UTC,"(for the record: this bug should be set to ""won't fix"", as in ""**can't** fix"", but I don't have the required permission to set the ""won't fix"" state on the bug report)."
1748543,2018-02-10 03:30:06 UTC,"      I did get a recent BIOS upgrade from Asus, it now shows non-vulnerable
for both variants of Spectre and for Meltdown with 3.13.0-33 kernel, so I'm
good, don't know how this might impact folks with other motherboards."
1748543,2018-09-24 11:19:42 UTC,For the record:
1748543,2018-09-24 18:19:14 UTC,"      Not sure why that would be as expected, Intel specifically sold the
'K' part to have unlocked multiplier.  Any firmware upgrades ought to retain
the features people paid for."
1748543,2018-09-27 00:01:23 UTC,"On Wed, 26 Sep 2018, <email address hidden> wrote:

> Do you have any reported issues with Ubuntu Bionic Beaver that ships with Intel's latest OS loadable microcode package 20180807a?
"
1748543,2018-09-25 20:01:39 UTC,Canonical can you confirm:
1748543,2018-09-26 11:39:19 UTC,@pragyan:
1748543,2018-09-26 12:11:12 UTC,Looks like I should add:
1748543,2018-09-25 17:31:19 UTC,"On Mon, 24 Sep 2018, Robert Dinse wrote:

> Not sure why that would be as expected, Intel specifically sold the
> 'K' part to have unlocked multiplier.  Any firmware upgrades ought to retain
> the features people paid for.
"
1748544,2018-04-02 13:18:43 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1748544,2018-04-02 13:09:21 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1748544,2018-03-29 18:50:30 UTC,"Reviewed:  https://review.openstack.org/550498
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=685f174eaa2086166b04dcb6b49bb0b1a7c23642
Submitter: Zuul
Branch:    stable/pike"
1748544,2018-03-28 20:59:19 UTC,"Reviewed:  https://review.openstack.org/550489
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ed7fc11459eb5a69088630e5ea4d12e441f80f2
Submitter: Zuul
Branch:    stable/queens"
1748544,2018-03-07 15:17:54 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/550498"
1748544,2018-03-07 01:55:43 UTC,"Reviewed:  https://review.openstack.org/543032
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=715a3cadb07fb92cc11542cfb5001844122b6f60
Submitter: Zuul
Branch:    master"
1748544,2018-02-20 21:49:46 UTC,I was able to test the proposed patch with devstack by booting an instance with an ubuntu cloud image with hw_qemu_guest_agent=yes and then installing the qemu-guest-agent in the instance.
1748544,2018-02-09 21:57:46 UTC,Related tempest change is here: https://review.openstack.org/543029
1748544,2018-02-09 21:39:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543032"
1748544,2018-04-20 13:13:56 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1748544,2018-03-07 14:44:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550489"
1748548,2018-07-26 12:58:12 UTC,"Change abandoned by Rabi Mishra (<email address hidden>) on branch: master
Review: https://review.openstack.org/547027
Reason: Fixed in https://review.openstack.org/#/c/530956/"
1748548,2018-02-22 15:29:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547027"
1748548,2018-02-22 12:49:14 UTC,"RDO heat-distgit patch series around dropping cloudwatch is
https://review.rdoproject.org/r/#/q/topic:drop-cloudwatch"
1748548,2018-02-22 13:41:35 UTC,"@Alan,"
1748552,2018-10-25 22:40:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748565,2018-11-20 11:22:17 UTC,Same issue on latest Manjaro and Intel 7260. Bluetooth is unusable cause of this.
1748565,2018-11-12 17:34:24 UTC,"I'm experiencing the same issue on Debian 8 ""Jessie"" with a backported Kernel 4.18 and latest Intel Firmware for my Wireless card."
1748565,2018-11-12 14:22:42 UTC,I also have the issue in Fedora 27 on Dell Inspiron 15 5570 with Qualcomm bluetooth (hciconfig -a hci0 shows that)
1748565,2018-11-08 16:24:29 UTC,"I've just installed Blueberry on Arch Linux 4.18.17.a-1-hardened and I get this bug as well.
dmesg shows several 'not cmd complete' followed by an input remap. I have only ever seen the message pop up when the Blueberry device manager is open. Last format (read: last week) I used Blueman and did not have this issue so the fault may lie in Blueberry. Skipping still occurs without Blueberry open but no errors are logged."
1748565,2018-11-08 10:36:33 UTC,"I confirm that too on Dell Precision 5530 (Intel Corporation Wireless-AC 9260) and Manjaro Cinnamon, Kernel 4.19.1
But it only occures if i have Bluetooth device discovery open and then only all 16s! So it must be related to that.
BT Headset is working anyway but sometimes interrupted but recovering."
1748565,2018-11-04 12:00:36 UTC,"Confirming the issue on Dell Vostro 5468 with Intel Bluetooth adapter (8087:0a2a), OS Ubuntu 18.04.1, kernel version. 4.15.0-36-generic. Audio output appears to clog and tear second after log line shows in dmesg. This goes for 4-5 seconds, after which playback continues normally for another ~10 seconds."
1748565,2018-11-01 11:49:40 UTC,"Hello,
just installed Ubuntu 18.10 on a Lenovo E485 and got this error."
1748565,2018-10-31 07:16:09 UTC,"Hello,
Has anybody checked Ubuntu 18.10?"
1748565,2018-10-30 19:15:59 UTC,"Same issue here with Fedora 28 and 29, using Gigabyte x470 Gaming 7 motherboard with an Intel Wifi and Bluetooth chipset."
1748565,2018-10-27 04:13:37 UTC,"dmesg
https://paste.pound-python.org/raw/Z0A2xHsgA3ePo8rmIL7L/"
1748565,2018-10-27 04:08:37 UTC,Same here with rtl8723de 4.18.16 latest rtl_bt firmware.
1748565,2018-10-22 12:43:41 UTC,"This Bug seems to affect even basic HCI functionality:
""hcitool inq"" is never returning in my case. dmesg gives me said error message.
I have tried two different USB-Bluetooth Dongles:"
1748565,2018-09-26 21:39:01 UTC,"I am facing the same trouble.
I can't air with some devices.
My card is :"
1748565,2018-09-12 01:49:31 UTC,"Everyone, if you would like this bug fixed then the most effective place to discuss it is directly with the Bluetooth/kernel developers here:"
1748565,2018-09-11 21:53:54 UTC,"WRT comment #46: Installing brcm/BCM20702A1-0b05-180a.hcd from winterheart had no effect on this or any other Bluetooth anomalies I've observed except eliminating the ""Direct firmware load"" error."
1748565,2018-09-08 13:21:16 UTC,"Ok, you didn't actually read my log output and assume things. The log message disappears completely WHEN my Bluetooth starts working. The actual opposite of your argument. I.e., the message only appears when my machine is ""unhealthy"". The message does not occur concurrently at all."
1748565,2018-09-07 06:37:38 UTC,I don't think so.
1748565,2018-08-23 01:26:58 UTC,Bug 1788383 is a duplicate of this one.
1748565,2018-10-27 04:17:22 UTC,"sudo lsusb -vvv
https://paste.pound-python.org/raw/vfIi8iqFxDaI5Mofjruq/"
1748565,2018-11-26 09:57:18 UTC,"I got a similar problem: many ""Bluetooth: hci0: last event is not cmd complete (0x0f)"" in dmesg and the sound from the bluetooth speaker is distorted (but connected)."
1748565,2018-09-07 06:20:38 UTC,"""So it would be most helpful if anyone is experiencing actual problems to report those in a separate bug."""
1748565,2019-01-18 06:31:13 UTC,Observing the issue on Fedora 29 Cinnamon. I have Lenovo T440P laptop on which I am trying to connect my Bluetooth headsets (Sony MDR-XB650BT).
1748565,2018-08-22 01:36:50 UTC,This bug is not related to playback failures. Please log a NEW bug for that by running:
1748565,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1748565,2019-04-23 21:35:02 UTC,This bug was fixed in the package linux - 4.18.0-18.19
1748565,2019-04-19 17:44:51 UTC,Hi all!
1748565,2019-04-16 15:54:21 UTC,"Hello Cristian and everyone involved,"
1748565,2019-04-04 18:04:30 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1748565,2019-04-04 18:02:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1748565,2019-03-29 06:18:43 UTC,"^^^
Is that implying the fix is in proposed?"
1748565,2018-12-01 14:12:38 UTC,"$ tail -f /var/log/syslog
Dec  1 21:28:26 localhost kernel: [  683.235091] Bluetooth: hci0: last event is not cmd complete (0x0f)"
1748565,2019-03-27 08:04:01 UTC,That commit fixes the issue for me.
1748565,2019-03-27 02:10:04 UTC,Comment 24 suggests to me that this bug should be closed (?). Because it seems to eliminate the possibility of the message appearing with (0x0f).
1748565,2019-03-27 01:41:51 UTC,"Specifically, instances of:"
1748565,2019-03-27 01:36:10 UTC,"> it's the only method to further debug hardware/firmware problems on lot of platforms
"
1748565,2019-03-26 20:10:21 UTC,Why this have changed importance Medium->Low while it's the only method to further debug hardware/firmware problems on lot of platforms ?
1748565,2019-02-01 21:28:33 UTC,Should this be added to the stable series too?
1748565,2019-01-21 01:45:13 UTC,"As I suspected, the error:"
1748565,2019-01-18 16:34:43 UTC,"I'm having the same issue on my Dell 7559 with Intel Dual Band Wireless-AC 8265 (Wi-Fi/BT combo) since forever (around two years ago). Mouse and keyboard works. However, I cannot connect my phone, headset or bluetooth speaker. I'm using 4.20.3-arch1-1-ARCH with Gnome Shell 3.30.2."
1748565,2019-01-18 07:22:11 UTC,"The ""last event is not cmd complete"" is in most/all cases a red herring, so please don't focus on that. There's a patch in mainline that will remove it for all valid situations (i.e. when the command completed with command status instead of command complete): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1629db9c75342325868243d6bca5853017d91cf8"
1748565,2019-03-27 02:11:52 UTC,I have verified the fix is in Ubuntu 19.04 disco.
1748565,2018-08-21 16:34:51 UTC,Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) and I am unable to play anything via bluetooth. Speaker gets connected but can not play audio.
1748565,2018-08-22 11:26:28 UTC,"Hello,"
1748565,2018-07-30 01:51:45 UTC,The message:
1748565,2018-04-20 07:15:22 UTC,"[27656.334177] usb 1-7: USB disconnect, device number 5
[27712.841243] usb 1-7: new full-speed USB device number 11 using xhci_hcd
[27712.990551] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b
[27712.990556] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[27712.993366] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[27712.994365] Bluetooth: hci0: Device revision is 16
[27712.994367] Bluetooth: hci0: Secure boot is enabled
[27712.994369] Bluetooth: hci0: OTP lock is enabled
[27712.994370] Bluetooth: hci0: API lock is enabled
[27712.994372] Bluetooth: hci0: Debug lock is disabled
[27712.994375] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[27712.994850] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[27714.572396] Bluetooth: hci0: Waiting for firmware download to complete
[27714.572400] Bluetooth: hci0: Firmware loaded in 1543294 usecs
[27714.572517] Bluetooth: hci0: Waiting for device to boot
[27714.584421] Bluetooth: hci0: Device booted in 11674 usecs
[27714.584469] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
[27714.587439] Bluetooth: hci0: Applying Intel DDC parameters completed
[27719.936384] Bluetooth: hci0: last event is not cmd complete (0x0f)
[27735.811353] Bluetooth: hci0: last event is not cmd complete (0x0f)
[27751.680367] Bluetooth: hci0: last event is not cmd complete (0x0f)
[27766.592465] Bluetooth: hci0: advertising data len corrected
[27769.863398] Bluetooth: hci0: last event is not cmd complete (0x0f)"
1748565,2018-04-20 07:03:47 UTC,I think this is related to suspend.
1748565,2018-04-14 21:43:23 UTC,"I'm also getting the same error: ""Bluetooth: hci0: last event is not cmd complete (0x0f)""
The message always appears as Bluetooth audio starts to skip."
1748565,2018-03-29 11:47:33 UTC,"confirming, imac 27 late 2013
Bluetooth: hci0: last event is not cmd complete (0x0f)"
1748565,2018-03-28 14:07:08 UTC,Confirm that issue too. Message is only printed when Bluetooth controller is discovering for devices.
1748565,2018-03-14 07:57:03 UTC,"Seeing similar messages with 4.16-rc4
[   17.617214] Bluetooth: hci0: BCM: chip id 90
[   17.620448] Bluetooth: hci0: BCM: features 0x0f
[   17.626236] Bluetooth: hci0: BCM4324B5
[   18.320710] Bluetooth: hci0: BCM (002.006.006) build 1170
[...]
[   59.373938] Bluetooth: hci0: last event is not cmd complete (0x0f)"
1748565,2018-03-12 19:57:11 UTC,"Created attachment 274695
bluetooth pcap during pair"
1748565,2018-03-12 19:56:24 UTC,"Hello,"
1748565,2018-03-09 11:09:30 UTC,"i can confirm this issue. bluetooth is working fine (keyboard & mouse).
however makes my console unusable since the message appears every couple of secs."
1748565,2018-03-07 22:43:14 UTC,"My problem was related to a faulty Bluetooth device. Sorry about the noise, please disregard. Thanks!"
1748565,2018-03-06 02:13:18 UTC,Still incomplete awaiting an answer to comment #5.
1748565,2018-02-16 02:06:10 UTC,Are you experiencing problems with bluetooth audio?
1748565,2018-02-15 13:07:07 UTC,"Hello Daniel,"
1748565,2018-02-15 07:15:51 UTC,"Is bluetooth working for you? I mean are you only reporting the log message, or is bluetooth also not working?"
1748565,2018-02-12 20:28:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748565,2018-02-09 23:38:57 UTC,"Hello,"
1748565,2018-02-06 17:24:54 UTC,"Created attachment 274025
#lspci -vvnn"
1748565,2018-02-06 17:21:41 UTC,"Created attachment 274023
dmesg_4.15.1-041501-generic.txt"
1748565,2018-08-06 10:30:27 UTC,"I can confirm that I also get this message while using my bluetooth headphones. Bluetooth is working fine. This message makes my TTY console sessions completely unusable. For example when I'm editing a file using nano or vi the message is written on top of the file, wherever my cursor was."
1748565,2018-04-20 16:51:24 UTC,"In my case I have the same issue
4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1748565,2018-04-23 01:34:06 UTC,I recommend anyone who wishes to contribute to this bug do so in the upstream bug where the Bluetooth developers are: https://bugzilla.kernel.org/show_bug.cgi?id=198699
1748565,2018-03-06 02:11:42 UTC,Confirmed this bug occurs with other bluetooth dongles too.
1748565,2018-05-03 23:04:21 UTC,"Hey, this is actually a 18.04 _show stopper_!"
1748565,2018-05-01 10:12:30 UTC,I've the same issue with Airconsole Pro 2.0
1748565,2018-07-28 06:42:03 UTC,"I second comment #14 - that's what happens on my device, too."
1748565,2018-06-19 06:17:33 UTC,"Alexey, see comment #23."
1748565,2018-06-15 11:49:18 UTC,I have the same issue on the fresh install of Ubuntu 18.04
1748565,2018-05-27 06:26:37 UTC,"This bug is not about Bluetooth failing. This bug is only about the kernel log message, which seems to happen even when everything is apparently working."
1748565,2018-07-28 06:45:58 UTC,"I.e. - most of the time, after having suspended my computer, it will not connect to bluetooth and I have to reboot. So this bug _is_ about Bluetooth failing. At least until after a reboot. You could say, it's about ""suspend"" failing."
1748565,2018-05-26 12:45:16 UTC,"In my case the error actually effects my ability to pair with several devices,
my card is
Bus 001 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
I can see the device from older distributions."
1748565,2018-05-26 12:35:43 UTC,"I also see that there are many devices I cannot pair to, e.g. my Bambo slate, it is discovered fine on my other pcs but just does not appear in the devices list as I make it discoverable and run"
1748565,2018-06-19 06:05:26 UTC,I can't make the headset microphone work and I see this in dmesg when I try to switch the profile from A2DP to HSP/HFP in settings. The profile isn't switching though.
1748565,2018-05-18 09:50:49 UTC,This error can be ignored as code is same as before message was changed from debug to error. We need to figure out if this code should also handle Command Status event.
1748565,2018-05-18 08:23:11 UTC,"Hi All,"
1748565,2018-05-18 01:27:29 UTC,Kernel 4.16.8 on lenovo t410 -- same issue
1748565,2018-05-16 01:52:50 UTC,Confirm this issue too.
1748565,2018-05-13 13:40:19 UTC,"Created attachment 275957
image1de678.PNG"
1748565,2018-05-04 01:35:16 UTC,This is probably not a showstopper. You are confusing Bluetooth bugs for a probably harmless bluetooth log message. This but is about the latter.
1748565,2018-05-13 13:40:18 UTC,"Created attachment 275955
imagea50acc.PNG"
1748565,2018-05-13 13:33:44 UTC,For me it happens in my laptop with a ath3k bluetooth:
1748565,2018-05-24 15:22:27 UTC,I've been running 18.04 on a MacBook Pro (early 2011) and my Bluetooth Ultrathin Touch Mouse worked just fine as did my touchpad for the past month or so.
1748586,2018-05-22 07:32:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748586,2019-01-09 07:57:51 UTC,I commented about resolution last year.
1748596,2018-11-23 14:43:47 UTC,"Marking Ubuntu content ""Invalid"" as not an official Ubuntu/Canonical snap"
1748596,2018-02-12 16:57:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748596,2018-02-15 00:15:27 UTC,"Anyway, Luis, you can also install the package from the ppa, if you prefer. It has less issues with file access etc.:"
1748596,2018-02-15 00:12:42 UTC,"The OP has entered this bug report twice.
Marking the first one as a duplicate, because more people seem to be following this one."
1748596,2018-02-14 23:59:27 UTC,"This is a known issue, and will be fixed for 0.92.3"
1748596,2018-02-12 17:15:00 UTC,"But export is broken, tried to import DXF from librecad package (/usr/share/librecad/library/elektro/electric_appliances/elk43.dxf), saved it to SVG, then opened SVG and tried to export as DXF."
1748596,2018-02-12 17:08:47 UTC,"I'm sorry for the noise, import works normally."
1748596,2018-08-13 14:34:34 UTC,I believe this is fixed in master. If you want to try the snap from the master branch (there may be other bugs there) you can do:
1748596,2018-02-12 12:27:42 UTC,"you might also consider asking a question at a location like this:
https://askubuntu.com/search?q=inkscape+snap"
1748596,2018-02-10 10:42:23 UTC,"- could you attach the svg file you are trying to export to dxf?
- also, which version of Inkscape, see Help->About
- also, could you attach any error messages you are receiving?"
1748596,2018-02-11 21:33:26 UTC,Where can I report this for Linux?
1748596,2018-02-11 19:46:10 UTC,"appears to be a duplicate of
https://bugs.launchpad.net/inkscape/+bug/1729896"
1748596,2018-02-11 18:49:01 UTC,"Hi, yes i did all that you says, but i get this message:
""Failed to import the numpy or numpy.linalg modules. These modules are
required by this extension. Please install them and try again.""
one library is missing. The inkscape.snap not come with this module, but
the inkscape flatpak did.
[image: Imágenes integradas 1]"
1748596,2018-02-10 19:34:53 UTC,"thanks for the file.
- I know that in the past there were sometimes, on some OS, more than one dxf output routine. Did you choose the one that says File Type = Desktop Cutting Plotter (DXF R14)?
- on output there should be a popup dialog that looks like this. did you get this dialog?
- if you get this dialog, try the settings shown on the bitmap, to see if it makes any difference"
1748596,2018-02-10 14:21:22 UTC,"I am using linuxmint 18.3
64 bits
cinnamon desktop"
1748596,2018-02-10 14:11:14 UTC,"Hi,
1.Version about inkscape Inkscape 0.92.2 (30a58d1, 2017-08-07)
2. Message error "" The file / home / amiel / Documents / inkscape forms /
example.dxf could not be saved.""
3. File"
1748596,2018-02-11 22:23:31 UTC,"I have added on Ubuntu under the bug report, not sure if this will make a difference or not."
1748597,2018-02-10 08:07:21 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1748597,2018-02-10 10:11:42 UTC,"Thanks, I've updated the description to outline the impact, and attached the two patches from the upstream Debian package that should be applied."
1748597,2018-02-10 12:29:05 UTC,"The attachment ""0001-x86_64-Use-sigprocmask-from-signal-frames.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1748597,2018-02-11 04:25:39 UTC,"I've attached debdiff's for trusty and xenial, if that's helpful."
1748598,2020-08-21 04:24:01 UTC,"I've changed the hplip-3.x/installer/distros.dat file as follows, mnanually checked that python-qt4 and python-qt4-dbus were installed, followed #9 and installed successfully in Debian 10.5"
1748598,2020-08-08 00:39:25 UTC,"I'm running into the same issue.  I tried the custom install as you describe, but it does not prompt me about GUI Qt4, it just skips from asking Network/JetDirect I/O to asking about GUI Qt5... and if I proceed it still ends up complaining about missing pyqt4 and pyqt4-dbus."
1748598,2020-03-19 17:45:08 UTC,"Dear faheemezani,
Thanks for this steps. Is actually helped in fixing the issues.
However, you forgot few critical steps in between within the process.
Bellow are what i have added in addition to yours."
1748598,2019-05-30 22:47:17 UTC,"I had the same issue with HPLIP 3.19.5 in a Debian 9.9: after installing the missing packages, the issue was still there."
1748598,2019-03-30 10:06:27 UTC,"Hello. I have this problem with Debian Stretch 9.8, that is to say the hplip installer fails do to missing package dependencies ""pyqt4-dbus"" & ""pyqt4-dbus"". These packages are in fact installed, but are currently named ""python-qt4"" & ""python-qt4-dbus""."
1748598,2019-08-28 02:24:17 UTC,"I ran a HPLIP 3.19.6 script on my Debian 10.0 and encountered the same error. Despite attempting to install ""python-qt4-dbus"" and ""python-qt4"", the same persists. Trying to install ""pyqt4-dbus"" and ""pyqt4"" packages also ended up futile because they were not recognized."
1748598,2018-02-12 07:27:47 UTC,"Hi, Afshan,"
1748598,2018-02-10 08:28:15 UTC,With this
1748598,2019-02-01 10:24:15 UTC,"I came here only to say that these people are freaking stupid. Is amazing the answer after telling whit the issue is, and is amazing how only with a single name changing in a package you can have all your freaking work completely messed up. We need some heroes that solve this stupid issue of missing packages because a stupid 4 characters changing."
1748598,2018-02-12 05:44:22 UTC,"Hi Josep,"
1748598,2018-02-11 11:39:20 UTC,I suppose Debian 9.2 should be registered too. Or even better: Support any Debian 9.x with an unique profile.
1748610,2018-02-19 06:06:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748612,2018-02-12 09:49:45 UTC,"This is intentional, more or less. The -D logfile is for the debug logs enabled with -d, not for strace. I think if we wanted to support redirecting strace output to a file we might need to have an extra argument, to avoid breaking existing users."
1748612,2018-02-12 10:04:35 UTC,"If this is not for strace, then why when I launch qemu as subprocess (example: from a python script)
with option -strace -D <file> it creates a log file called <file>-strace? Seems like a bug to me.
Anyway, I understand you don't want to break the current behavior, is there any chance this gets added in the near future?"
1748612,2018-02-12 10:38:54 UTC,"If you use -D <file> it will create a file named <file>, which will contain any logs created via the qemu_log subsystem (which might be nothing at all, depending on what the guest does). I don't know where the ""-strace"" part would come from unless you specified it as part of the filename."
1748612,2018-02-12 10:48:18 UTC,"I will check that again, pretty sure I saw that.
Anyway any chance there is an option/fix for that?
Today it is impossible to differentiate strace output with program's stderr output, and it is causing trouble while used in scripts."
1748612,2020-11-23 09:56:04 UTC,"I think this has been fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=4b25a50674de41e72f6b3003"
1748619,2018-05-27 02:36:51 UTC,same issue
1748619,2018-06-06 12:45:43 UTC,same issue here.
1748627,2018-02-10 14:34:37 UTC,"Note that, because snaps are self-contained, the answer to ""list files in installed snap"" is simply to find /snap/<snapname/current/."
1748630,2018-02-10 17:39:16 UTC,this should be easily achievable via:
1748633,2018-02-13 12:26:25 UTC,"yeah, well, i simply think the sheer amount of returned data will make it useless to standard endusers (compared to apt-file which will return a handfull of packages due to the different design of the packaging format)"
1748633,2018-02-13 00:28:24 UTC,"On Sat, Feb 10, 2018 at 05:34:48PM -0000, Oliver Grawert wrote:

> something like a ""snap find-file npm"" could give you 1000s of useless
> results (simply every node based snap in the store), you would simply
> end up with massive duplication.
"
1748633,2019-10-09 20:48:16 UTC,"I can see the use case here, but I tend to agree with @ogra that it is not as useful as for debs and the sheer quantity of the output will make it difficult to actually do anything useful with the output. Setting as wishlist for now, if there are additional use cases for this feature, please feel free to comment on this bug or create a post at forum.snapcraft.io where we can discuss this with snapd architects."
1748633,2018-02-13 12:43:09 UTC,"also ... while in deb packages you will have a guarantee what the ""libz.so.1.2.3.4"" binary contains, how will you know that the 8474583754 returned ""libz.so.1.2.3.4"" form a"
1748633,2018-02-10 17:34:48 UTC,"this apt behaviour might conceptually not be feasible for snaps, do not forget that snaps usually ship their dependencies included ..."
1748634,2018-02-10 14:40:40 UTC,From https://bugs.scribus.net/view.php?id=10505:
1748635,2018-02-14 01:30:38 UTC,I see that your `interfaces` file contains lines like:
1748635,2018-02-14 08:10:58 UTC,"Thank you, yes, this appeared to clear the issue."
1748635,2018-02-14 08:13:56 UTC,Perhaps the error message could have shown the offending line?
1748635,2018-02-20 13:28:25 UTC,/e/n/i does allow multiple interfaces on the one line for auto - per the man page - and netplan should support migrating that. I've added it to my list of migration bugs.
1748639,2020-03-26 04:17:26 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1748639,2018-02-12 20:29:59 UTC,"As suggested somewhere (cannot find the source but it was on a old version of ubuntu), and with the help of https://wiki.ubuntu.com/DebuggingKernelBoot, I first boot on text mode and system was blocked just after something like 'reached target bluetooth'."
1748639,2020-01-25 15:46:34 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1748639,2018-02-11 20:47:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748644,2018-02-15 13:18:47 UTC,"Yeah that's fine, I kept thinking 'anti-aliased' but wasn't sure it was the right word! I regret not using it originally xD"
1748644,2018-02-12 16:06:20 UTC,"Can you (re)install the libreoffice deb packages and test whether they are also affected by this font issue, or if it's snap-specific?"
1748644,2018-02-12 16:29:42 UTC,"```
Start-Date: 2018-02-06  12:54:02
Commandline: apt install ubuntu-communitheme-session
Requested-By: adam (1000)
Install: suru-icon-theme:amd64 (18.04~wip1+201712220331+8f664ee~ubuntu17.10.1, automatic), gnome-shell-communitheme:amd64 (18.04~wip1+201801311959+420cb11~ubuntu17.10.1, automatic), communitheme-sounds:amd64 (18.04~wip1+201801311039+fb3c6da~ubuntu17.10.1, automatic), gtk-communitheme:amd64 (18.04~wip1+201802032115+a6ca20f~ubuntu17.10.1, automatic), ubuntu-communitheme-session:amd64 (18.04~wip1+201801311959+420cb11~ubuntu17.10.1)
End-Date: 2018-02-06  12:54:08"
1748644,2018-02-12 16:44:01 UTC,"Restarted and it's broken again, hmm."
1748644,2018-02-12 16:45:53 UTC,"Oh, and it's a snap-specific problem because the problem doesn't exist in the Deb."
1748644,2018-02-13 00:42:39 UTC,"I've figured it out - it's because after installing the communitheme and removing it, I logged into a standard Wayland session rather than the standard Xorg one, the bug is actually that the fonts are broken in the snap on a Wayland session"
1748644,2018-02-13 00:56:38 UTC,This seems to be a bug in gnome-clocks 3.26.1 (43) as well
1748644,2018-02-14 15:19:00 UTC,"Confirmed. To my untrained eye this doesn't look like thinner fonts (I've compared two screenshots and the same text in the about dialog takes up exactly the same width), but rather like they're not antialiased under wayland."
1748665,2018-09-25 00:00:18 UTC,"""who would"", not ""would would"", sorry. (Can't edit comments?!?!?)"
1748665,2018-09-24 23:51:19 UTC,"I forgot to mention that my modern version has always contained 148 ""RS"" links to easily get to the corresponding section in Robert Strandh's more barren version."
1748665,2018-02-10 21:31:23 UTC,"That stuff is intended to help one more easily understand the structure of the document and determine at a glance where they are and how to go to where they want to go, but sure, I'll add some further options to the preferences page (https://clos-mop.hexstreamsoft.com/preferences/) to make it possible to have a more barren look."
1748665,2018-02-10 20:29:01 UTC,"I find it a bit too busy, a lot of links, arrows, headings. I get lost. I've found the old alu.org page easier to read, can you maybe make a lite version?"
1748667,2020-05-28 14:17:36 UTC,me neither
1748669,2018-02-12 21:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748669,2018-02-12 22:36:26 UTC,error makes any data collection impossible
1748669,2018-02-13 18:59:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1748671,2018-02-10 22:08:29 UTC,apport information
1748671,2018-09-29 01:01:10 UTC,"I've encountered the same error, on Mint 19 - based on Ubuntu 18.04 - with kernel 4.19.0-041900rc4-generic."
1748671,2018-02-21 18:58:26 UTC,This bug was fixed in the package linux - 4.4.0-116.140
1748671,2018-02-14 14:27:13 UTC,"The -proposed kernel 4.4.0-116.140 fixes the issue, thanks!"
1748671,2018-02-14 09:42:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1748671,2018-02-12 18:25:55 UTC,"apw's test kernel (https://people.canonical.com/~apw/lp1748671/fix-not-xenial/) fixed the problem, thanks!"
1748671,2018-02-12 17:21:25 UTC,"I could reproduce with kernel 4.4.0-115.139. Removing dnsmasq's Apparmor profile doesn't change anything.
Once the artful container boots, the host's dnsmasq (lxd-bridge) hangs (state D) and stracing it showed absolutely nothing."
1748671,2018-02-10 22:08:31 UTC,apport information
1748671,2018-02-10 22:08:27 UTC,apport information
1748671,2018-02-10 22:08:26 UTC,apport information
1748671,2018-02-10 22:08:24 UTC,apport information
1748671,2018-02-10 22:08:12 UTC,apport information
1748671,2018-02-10 22:08:22 UTC,apport information
1748671,2018-02-10 22:08:20 UTC,apport information
1748671,2018-02-10 22:08:19 UTC,apport information
1748671,2018-02-10 22:08:18 UTC,apport information
1748671,2018-02-10 22:08:16 UTC,apport information
1748671,2018-02-10 22:08:15 UTC,apport information
1748671,2018-02-10 22:08:13 UTC,apport information
1748671,2018-02-10 22:08:23 UTC,apport information
1748671,2018-02-10 22:00:19 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748678,2018-05-06 17:47:03 UTC,"I think the bug is still present upstream following more thorough usage. It seems sensitive to ambient light levels; using the computer in a darkened room (night) causes more intense and regular symptoms. It seems related to a bug I swear I filed a few years ago but didn't get any traction with, but I can't find any references to it. I recorded a video showing the screen flickering back then which I shared to show the physical manifestation - it's the same machine with similar behaviour but not as pronounced: https://youtu.be/zSP2EIAkkJg"
1748678,2018-02-11 00:30:07 UTC,This change was made by a bot.
1748678,2018-02-13 18:13:50 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1748678,2018-02-18 01:21:28 UTC,"I've tentatively marked it as fixed upstream, but as the bug occurs sporadically I might not have tested long enough to recreate the conditions which trigger the bug. I don't have reliable reproduction steps (read: any steps) so I will continue testing the upstream kernel in case I do hit it."
1748678,2018-02-18 18:08:04 UTC,"Further, I've managed to cause two system lock-ups, which I do not have logs for because the lock-ups were so severe that the logging system didn't record the kernel logs before death. I therefore cannot attribute those two lockups to this issue for now. I've set-up netconsole now to try to gather logs from these lock-ups so that I can definitively attribute or rule them out."
1748681,2018-02-25 02:06:09 UTC,"I noticed that if I launch version 2.1.4 from the terminal it tells me: WARNING:menulibre: getDefaultMenuPrefix() 'No menu prefix found, MenuLibre will not function properly.'"
1748681,2018-02-27 11:15:43 UTC,"I managed to get MenuLibre running on Solus MATE. I am able to confirm the bug that you are seeing, but not able to determine what is causing it."
1748681,2018-02-25 00:34:29 UTC,"@Sean, do you mean you saw the same problem as me or that you weren't able to open it?"
1748681,2018-03-29 08:29:14 UTC,"I'm using Solus with Mate 1.20. The menu prefix recognition works fine, however the problem exists in how menulibre reads the information. I use a patch in order to trick menulibre and use gnome-applications.menu even in a MATE session. Another workaround is to copy /usr/share/xdg/menus/gnome-applications.menu into ~/.config/menus/mate-applications.menu in order to trick menulibre again."
1748681,2018-02-23 06:17:01 UTC,"I also experience anomalies using this with MATE. I do not believe it is fully MATE compatible. I do not experience what you state, but I have issues with folder placement not matching and order of menu items."
1748681,2018-02-24 00:54:15 UTC,@bwat47 I was unable to get MenuLibre running in Solus MATE.
1748689,2018-06-27 15:44:39 UTC,I see this on 4.13.0-45-generic of Ubuntu 16.04 HWE kernels.
1748689,2018-06-17 15:33:19 UTC,Also confirming on 4.15.0-23. Any updates?
1748689,2018-05-30 21:39:40 UTC,Also confirmed on 4.15.0-22:
1748689,2018-06-29 20:51:23 UTC,Looks like it's potentially been fixed upstream:
1748689,2018-06-12 19:10:21 UTC,Any update on this issue? Having it happen pretty consistently on my 16.04 machines.
1748689,2018-10-09 16:24:28 UTC,Can we test this once  18.04.2 has been released?
1748689,2018-02-12 10:36:14 UTC,apport information
1748689,2019-07-17 15:51:30 UTC,I am seeing this ioctl error on my console screen (before login).  It fills the screen because I have a crontab job running that mounts an SMB share temporarily.
1748689,2019-07-17 15:54:19 UTC,"Whoops, my bad.  The error code I see is slightly different than this one.  Sorry."
1748689,2019-07-17 16:11:27 UTC,"Sorry I cannot delete my messages above but in case someone else has same scenario as me, you might be able to keep the error from displaying by adding ""vers=2.0"" in your mount options.  At least that is the version I needed to specify for Windows 2008 and I do not see the errors anymore upon mounting."
1748689,2018-02-12 10:36:10 UTC,apport information
1748689,2018-05-30 21:36:32 UTC,"I can also confirm on Xenial running 4.15.0-13:
user@host:~$ dmesg | tail
[ 1331.150999] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1331.197478] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1331.245486] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1631.292647] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1631.335005] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1631.374513] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1931.420138] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1931.467038] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1931.506586] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5"
1748689,2019-02-04 22:04:27 UTC,BUMP
1748689,2018-05-01 06:31:12 UTC,I confirm on kernels 4.15.0.19 and 4.15.0.20.
1748689,2018-02-12 10:36:12 UTC,apport information
1748689,2018-02-13 17:59:45 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1748689,2018-02-15 01:54:16 UTC,It appears the issue is not occuring in 4.16-rc1
1748689,2018-02-12 10:36:16 UTC,apport information
1748689,2018-02-12 10:36:18 UTC,apport information
1748689,2018-02-12 10:36:20 UTC,apport information
1748689,2018-02-12 10:36:22 UTC,apport information
1748689,2018-02-12 10:36:23 UTC,apport information
1748689,2018-02-11 03:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748689,2018-02-12 10:36:27 UTC,apport information
1748689,2018-02-12 10:36:25 UTC,apport information
1748689,2018-02-12 10:36:33 UTC,apport information
1748689,2018-02-12 10:36:35 UTC,apport information
1748689,2018-02-12 10:36:29 UTC,apport information
1748689,2018-02-12 10:36:31 UTC,apport information
1748696,2018-02-11 08:12:54 UTC,"Havn't tested this in Manila environment, but it may also exist in Manila as Cinder and Manila share most of the same codes here."
1748696,2018-02-11 08:16:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543205"
1748696,2018-02-15 17:09:29 UTC,From xyang:
1748696,2020-09-23 16:05:25 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/543205
Reason: I agree with Zhao that this is the role of the update_stats call. While we can try to be preemptive in updating the capacity on create calls, it isn't until the create call succeeds (or fails) that the actual capacity is impacted. Due to the async nature of this, we need to stick with the periodic stats updates."
1748697,2020-01-30 19:22:25 UTC,"Reviewed:  https://review.opendev.org/695220
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4921e822e73383af0c8da4c5e3acfaa021eafe68
Submitter: Zuul
Branch:    master"
1748697,2019-12-05 20:14:31 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/676022
Reason: I'm just going to drop this backportable workaround option. If some really needed this we could think about it as a stable-only change but this is a really latent bug that not many have cared much about fixing so not a high priority to backport and introduce the complexity that this brings. I'll drop this and focus on the master-only traits-based solution in https://review.opendev.org/#/c/695220/."
1748697,2019-11-20 15:30:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/695220"
1748697,2019-08-12 21:31:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676022"
1748697,2019-08-13 17:28:26 UTC,"Change abandoned by Jing Zhang (<email address hidden>) on branch: master
Review: https://review.opendev.org/675025
Reason: replaced by https://review.opendev.org/#/c/676022/1"
1748697,2019-08-02 01:04:23 UTC,"My apologies for comment #5, the VMs I had issues with are created with the ""different host"" rule, I was not aware of that."
1748697,2019-08-01 01:51:31 UTC,I have the same issue as described in the ticket and in comment #3:
1748697,2018-09-27 16:54:39 UTC,"In my opinion, there is no point to do cold migration on the same host. Unless there is really a special need where particular resources such as some pCPUs should be freed. Even on such case, resize with new flavor can be used to rescue."
1748697,2018-09-27 07:50:27 UTC,Just to confirm that it is not always necessary to disable all the other hosts in order to reproduce the problem.
1748697,2018-03-22 08:40:36 UTC,"Hi,sylvain-bauza, in some cases instance will be set to ERROR state when migrate failed (such as UnableToMigrateToSelf),we can simply return the error to upper layer (operater or user) to avoid make user run reset to restore instance status since no changes to guest at all."
1748697,2018-02-13 14:09:39 UTC,Some Nova virt drivers support migrating to the same host (VMWare at least). That's why it's not meaningless to accept migrating to a same host.
1748697,2019-08-07 04:17:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675025"
1748697,2019-08-12 19:40:50 UTC,"> 2、disable all hosts except the host which the vm is located
"
1748699,2018-02-17 08:07:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748699,2018-03-10 16:15:23 UTC,"Hi anyone,"
1748700,2018-02-11 05:10:02 UTC,Hello! Thank you for your help in solving my problem.
1748700,2018-03-03 04:51:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748702,2018-02-11 06:19:01 UTC,This is currently on the sync blacklist: https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt#L63
1748702,2018-02-12 21:09:21 UTC,"The existing acpi-support package in Ubuntu is a native package that has always been maintained in Ubuntu, Debian has never been upstream to Ubuntu for it.  To drop this blacklist, I would want an affirmative review of the delta from someone to confirm that the Debian changes are correct to include (i.e. this should be treated as a merge, not as a sync)."
1748702,2019-06-17 04:17:45 UTC,[Expired for acpi-support (Ubuntu) because there has been no activity for 60 days.]
1748712,2018-02-14 18:40:06 UTC,"I think it's likely that this is a subtle/rare bug with postgresql (the transaction should have failed!?), but it could have been something to do with the way MAAS was setting up transaction isolation (IIRC, there were a lot of database transaction related bugs being worked on back then)."
1748712,2018-02-14 14:16:27 UTC,"Based on the date of that event, it was when MAAS 2.0rc1 was put out for testing. This could be related to a pre-release version issue, where the constraint was add before MAAS 2.0 went final."
1748712,2018-02-14 00:02:48 UTC,The commit that corresponds to migration 131 changes the Event model in the following relevant way:
1748712,2018-02-11 09:33:06 UTC,Deleting that event row allowed the upgrade to proceed:
1748712,2018-02-14 00:13:00 UTC,"After checking a MAAS 2.3 install, I see that there is indeed a foreign key constraint that should prevent events from being inserted for invalid nodes."
1748712,2018-02-11 09:31:27 UTC,Digging in there is an old record for what must be an old node:
1748714,2018-02-25 11:47:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748719,2018-02-11 13:39:58 UTC,"so it looks like the path contains the directory where the bibles are stored and file contains a pathobject consisting on only a name, the name of the bible db."
1748719,2018-02-11 13:22:45 UTC,Hmm.. the bibles are a little messed up...
1748720,2018-02-11 12:59:35 UTC,"hmm... I don't know where that should be done...
It looks like the migration to not include the web remote, didn't actually update the ftw."
1748723,2018-02-11 12:29:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1748723,2018-03-13 13:54:01 UTC,You can try Fumatic driver which is recommended by default:
1748723,2018-03-13 13:55:06 UTC,P.S. Also not forget to remove HPLIP before trying Fumatic.
1748723,2018-03-15 16:02:13 UTC,"Remove your print queue and re-plug your printer. Does this make it work? What is the output of the command ""lpstat -v"" after that?"
1748723,2018-05-15 04:17:27 UTC,[Expired for hplip (Ubuntu) because there has been no activity for 60 days.]
1748740,2018-04-04 14:44:24 UTC,Confirmed on Pike too.
1748740,2020-04-08 15:51:43 UTC,So we've reworked docs in rocky and it do not contain running tasks with tags. Additionally new script has beed introduced with https://review.opendev.org/#/c/706491/ which allows to add compute node with a single command.
1748744,2020-05-14 18:28:10 UTC,We rolled this out earlier this week.
1748747,2018-02-11 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748747,2018-02-13 17:54:23 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1748747,2018-03-18 08:36:50 UTC,"Joseph, since I am using the laptop as main working device I am very reluctant to switch from the ubuntu custom kernel to mainline and let the machine die willingly. I got a pointer via AskUbuntu (https://askubuntu.com/questions/961278/how-to-prevent-shutdown-when-one-of-two-batteries-is-empty) that UPower is likely to be the real culprit (https://forums.lenovo.com/t5/Linux-Discussion/How-to-get-dual-battery-to-switch-without-powering-off-in-Linux/td-p/3890605)."
1748747,2018-03-18 08:54:46 UTC,Apparently it is known for quite a while (read 6 years) that UPower has some problem with dual battery systems: https://bugs.freedesktop.org/show_bug.cgi?id=55278
1748748,2018-02-11 18:03:27 UTC,Yet another follow-up:
1748748,2018-02-11 12:32:11 UTC,Another follow-up:
1748748,2018-02-11 12:28:33 UTC,"Following up on my report, if I try to start it as root instead of as a normal user it starts, but I get:"
1748751,2018-02-12 05:52:51 UTC,"Promotion jobs are also failing:- https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-centos-7-master-containers-build/5bdf909/undercloud/home/jenkins/undercloud_install.log.txt.gz
https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset020-master/0571077/undercloud/home/jenkins/undercloud_install.log.txt.gz"
1748751,2018-04-20 16:14:05 UTC,This issue was fixed in the openstack/python-mistralclient 3.4.0 release.
1748751,2018-02-14 10:03:56 UTC,"@Sagi Fix is neither commtted nor released in tripleo, it is in mistralclient hence I've set tripleo part of this bug to Invalid."
1748751,2018-02-14 10:18:54 UTC,Workaround in RDO was to jump over upper-constraints before new mistraclient release: https://review.rdoproject.org/r/12184
1748751,2018-02-12 16:18:04 UTC,Patch in mistralclient here: https://review.openstack.org/543460
1748751,2018-02-14 16:17:54 UTC,This issue was fixed in the openstack/python-mistralclient 3.3.0 release.
1748756,2020-11-19 14:50:49 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1748756,2020-11-21 23:30:46 UTC,"The QEMU project doesn't implement new target architectures or board models on demand based on wishlist requests; they're a lot of work to do. Instead we simply code-review and incorporate board models and architectures as and when people decide to write them and submit the patches. So there's really no point in having a 'wishlist' bug in the bug tracker saying ""support for board X would be nice"", because it will never happen, unless by the coincidence that somebody happened to implement and submit it to us anyway."
1748757,2018-06-01 18:30:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748759,2018-06-27 14:51:09 UTC,could reproduce the issue with Inkscape 0.92.3 in Debian Testing.
1748759,2019-05-21 03:29:41 UTC,"Can reproduce with Inkscape 1.0alpha (d666cd1a10, 2019-05-16) from master. Paths do not snap to correct place on grid."
1748759,2018-06-27 18:28:37 UTC,could reproduce the issue with Inkscape 0.92.3 in PureOS Green.
1748765,2018-02-14 04:09:00 UTC,"Rapid Photo Downloader handled the situation as expected: when it encountered a file that was named as a jpg, and it couldn't download it because of missing metadata, it reported an error."
1748765,2018-02-14 04:21:47 UTC,Thanks for your response!
1748767,2018-02-12 14:18:13 UTC,"I'm not able to confirm this on 3.0.3. I tested with a patron record having preferences set for email, phone and sms notifications. When placing a hold in the xul client, all notification methods were appropriately saved in the hold."
1748767,2018-02-12 14:40:26 UTC,"It is happening randomly. Hold shelf slips are printing without hold notification type information even though it appears in the patron record. If only a few patrons were affected, we would assume the information was removed by staff or patrons for specific holds. But it is happening enough to make it obvious that this is a deeper issue."
1748769,2018-02-11 18:10:47 UTC,Thanks for reporting.
1748773,2020-01-16 16:35:22 UTC,"Another example:
https://manpages.ubuntu.com/manpages/eoan/en/man7/pmp-check-aws-rds.py.7.html"
1748774,2018-06-08 10:01:37 UTC,An unhandlable error occured
1748780,2018-10-04 10:04:02 UTC,"This is the warning message
Some code accessed the property 'application' on the module 'application'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway."
1748780,2018-10-04 10:06:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748781,2018-02-11 19:23:49 UTC,This is the SVG of cpu time spent.
1748781,2018-02-11 19:24:17 UTC,"I wasn't able to reproduce this, I think I had to get lucky with what connection was killed, and even then I'm not sure what was going on."
1748781,2018-02-13 03:06:36 UTC,"So looking through the code, one thing comes to mind. If the channel under
Changes() was closed, then I think the loop would wake up, but only see an
empty list, and thus would issue no Get() requests and thus never find an
error and just loop calling Changes() over and over.
Theoretically if Changes was closed it should be trying to kill the tomb so
the Dying side should trigger and shut down.  But if we missed that, there
is nothing in this loop that would notice an error."
1748781,2018-03-14 09:52:33 UTC,"I was able to reproduce this today with Juju 2.3.4 while following the steps from here:
https://bugs.launchpad.net/juju/+bug/1747368/comments/2"
1748787,2018-02-25 14:16:01 UTC,The pitivi is freezing with some *. mpg files.
1748787,2018-08-20 10:26:07 UTC,"The traceback has been fixed upstream, see https://gitlab.gnome.org/GNOME/pitivi/issues/2192"
1748787,2018-08-29 09:39:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748787,2018-08-29 09:40:32 UTC,I was not able to complete a render after this crash.  I did not try reloading the program and trying again.
1748790,2018-02-16 09:32:05 UTC,@stgraber - is lxcfs part of what you do stable upgrades for anyway? And if so will this be fixed by backports - or is this not meant to be backported for some reasons?
1748790,2018-02-16 15:54:49 UTC,"Yes, we'll have a new lxcfs bugfix release out in the next month or so which will include those fixes."
1748792,2018-02-12 01:17:32 UTC,@Robert-  How would you want to move a group of a wire + label?  Maybe this is a bug but it feels like a feature because you can always hit 'Tab' to drag the group.
1748792,2018-02-12 12:22:22 UTC,"I can not confirm this on windows with (2018-01-24 revision 7a2d9dff6)-makepkg, release build and (2018-02-12 revision ed127e866)-makepkg, release build."
1748792,2018-02-15 16:33:37 UTC,"I'll update to the latest and try again. If it still happens, I'll post a video link."
1748792,2018-02-15 16:42:30 UTC,"Confirmed on (2018-02-14 revision 6afdf1cf8)-makepkg, release build."
1748792,2018-02-15 16:45:52 UTC,"When grabbing a group consisting of one end of a wire plus a label, I certainly don't expect the wire to detach itself at the other end. Note that I am ctrl-clicking, not just clicking, so this is a grab, not a move."
1748792,2018-02-15 17:35:14 UTC,"Ah, I see the issue."
1748792,2018-02-16 01:16:42 UTC,"OK, I see the issue now. It was just very surprising to me that grabbing both would result in a move behavior."
1748797,2018-02-16 20:41:42 UTC,"Good idea, thanks! I've opened an upstream gnome-terminal bugreport about it:
https://bugzilla.gnome.org/show_bug.cgi?id=793521"
1748801,2018-03-07 18:03:57 UTC,kernel-fixed-upstream
1748801,2018-03-07 18:06:22 UTC,Excellent!... no more Problem!... thanks for the help!... Bye!.. Kind of Regards!...
1748801,2018-02-12 02:00:09 UTC,This change was made by a bot.
1748801,2018-02-13 17:51:59 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1748804,2018-03-12 03:48:57 UTC,"I found the way to fix/work around this issue. It turns out that you need to do the following steps to move forward:
1.) remove docker version 1.17.05 or 1.12 and install 17.03:
# yum remove docker*
# yum instally -y docker-engine-17.03*
2.) install the kubernetes packages:
# yum install -y ebtables kubeadm kubectl kubelet kubernetes-cni git gcc
3.) validate that you are doing this:
kubelets must be started with --network-plugin=cni and have --cni-conf-dir and --cni-bin-dir properly set in your 10-kubeadm.conf file:
/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
*Not sure if this is different from what is automatically installed via yum or not as I was monkeying with all the settings, but I removed the --network-plugin for a while and it caused problems, so I put the settings from the below link.
4.) follow the steps for canal on github for version 1.7+ from here with the modifications in the kolla-kubernetes install guide:
https://github.com/projectcalico/canal/tree/master/k8s-install#for-kubernetes-17
$ kubectl apply -f https://raw.githubusercontent.com/projectcalico/canal/master/k8s-install/1.7/rbac.yaml
$ curl -L -s https://raw.githubusercontent.com/projectcalico/canal/master/k8s-install/1.7/canal.yaml -o canal.yaml
$ sed -i ""s@10.244.0.0/16@10.1.0.0/16@"" canal.yaml
$ kubectl apply -f canal.yaml
5.) Once you've completed the above, your canal should get to 3/3 and start passing dns checks as well (though DNS would pass before this)."
1748812,2018-05-14 01:43:37 UTC,"From comment 40 in upper stream bug - https://bugzilla.gnome.org/show_bug.cgi?id=767317#c40
Upgrade to higher version(1.8) of NM should fix this. However xenial is stuck in 1.2.6... So I think 18.04 upgrade can fix this - which NM is 1.8.10."
1748812,2018-04-14 17:48:16 UTC,I wasn't able to reproduce it with liveUSB and only one Wi-Fi connection. Will try to add more connections (few openvpn probably)
1748812,2018-04-13 21:11:57 UTC,"Hi Kai-Heng!
I still see this bug. I'll try to reproduce it with liveUSB"
1748812,2018-04-13 04:57:49 UTC,"I got XPS 9360 at hand, but unfortunately I can't reproduce the issue."
1748812,2018-02-12 09:47:42 UTC,"Dell XPS 13 9360 should be preloaded with kernel 4.4 + the generic xorg package instead of LTS Enablement Stacks [1].
But your system looks like LTS Enablement Stacks are installed according to the dpkg.log in comment #10.
Did you install LTS Enablement Stacks by yourself?"
1748812,2018-02-13 04:43:55 UTC,"Kai-Heng Feng, yes"
1748812,2018-02-13 03:11:18 UTC,Is this 100% reproducible?
1748812,2018-02-12 17:01:27 UTC,"Kai-Heng Feng, just closing the lid."
1748812,2018-02-12 09:18:39 UTC,"I guess something went south when NM is signaling ""wireless-enabled"" signal. The culprit can be either NetworkManager or NetworkManager-Applet."
1748812,2018-02-15 23:53:04 UTC,"One more detail: this bug is for wireless networks only. Looks like wired works as expected (please see ""Dell docking"" on screenshot)"
1748812,2018-02-12 06:43:35 UTC,Could you also provide `lspci -nnk > lspci.log`?
1748812,2018-02-12 08:12:30 UTC,Sure. Please find it in attachment
1748812,2018-02-12 04:13:19 UTC,`Uname: Linux 4.15.0-041500rc9-generic x86_64` is not the kernel that Ubuntu supported.
1748812,2018-02-12 04:20:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748812,2018-02-12 04:20:30 UTC,So what does it look like before restart?
1748812,2018-02-12 03:53:42 UTC,Here is how nm-applet looks after restart (killall nm-applet && nm-applet &)
1748812,2018-02-12 04:29:14 UTC,"Shih-Yuan Lee,"
1748812,2018-02-12 04:31:46 UTC,"Kai-Heng Feng, you can see screenshot before restart in original bug description:"
1748812,2018-02-12 04:47:02 UTC,"It looks like it is a preloaded Ubuntu system.
Could you help to provide some logs as the followings?"
1748812,2018-02-12 04:21:40 UTC,The same here:
1748812,2018-02-12 05:02:08 UTC,Yes it's Dell XPS 13 that comes with Ubuntu 16.04 preinstalled. But I have the same issue on Lenovo T530 where I installed Ubuntu manually.
1748814,2018-04-25 12:47:13 UTC,"A short-term fix for this bug would be to remove the combined flag as a default for the subject class, so that negated searches work properly for Evergreen catalogs."
1748815,2018-04-23 02:16:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748825,2019-02-22 04:58:33 UTC,"Reviewed:  https://review.openstack.org/633371
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=d0a7940981bb123bfc12d4ed2d24a4bf50e513e4
Submitter: Zuul
Branch:    master"
1748833,2018-08-31 04:35:47 UTC,https://reviews.mahara.org/#/c/8650/
1748833,2020-04-01 17:40:06 UTC,There is already a first version of this idea available at https://reviews.mahara.org/#/c/8650/ but it needs more work before it can be considered for core.
1748839,2018-12-09 15:14:45 UTC,Could be a good idea to report it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/
1748839,2018-12-09 12:28:44 UTC,"I am facing the same issue with my ubuntu 18.04. My PC gets connected to unprotected wifi easily, however it shows activation error while trying to connect to a protected wifi."
1748839,2018-12-04 22:06:39 UTC,"I would have expected something in dmesg. After test, check timestamps of other logfiles in /var/log - maybe you then find a log which contains useful information."
1748839,2018-11-30 15:17:29 UTC,How to activate log to understand what blocks the wifi connection ?
1748839,2018-11-29 14:24:47 UTC,Then it really looks like a bug. It would be good to have logfiles for both cases to compare them.
1748839,2018-10-05 19:34:59 UTC,@VascoT: Delete the configuration and reconnect to the wifi doing the configuration from fresh.
1748839,2018-11-21 10:05:35 UTC,@Vivien: Most probably they did not tell you the correct settings - please verify with the responsible IT admin that you are using the correct settings.
1748839,2018-11-21 09:14:40 UTC,I m still unable to connect to WPA2 Enterprise Network after installing all the apt updates with Ubuntu 18.10.
1748839,2018-10-04 11:07:48 UTC,"With the newest packages on 18.04 I can still not connect to eduroam. In system-settings -> network, when I click on eduroam a round ""progress"" thing starts to rotate, but no question is asked for credentials. Also no log messages are showed in syslog or kern.log. How to debug this issue?"
1748839,2018-10-01 19:20:37 UTC,Bug is also happening on 18.10
1748839,2018-12-17 14:28:54 UTC,"OK, how'd this slip through?  No WPA options anywhere? Only 2 WEP options.  2 new installs, on different machines, I can not connect to my WPA (TKIP+AES) network wirelessly!!!"
1748839,2018-11-29 13:58:48 UTC,"@Martin: On the same PC, it is impossible to connect to WiFi with Ubuntu 18.10, but it works with a bootable USB key Ubuntu 16.04.05"
1748839,2018-12-17 14:36:06 UTC,Bug #1761003 also may be related.
1748839,2019-05-07 02:44:48 UTC,Hi... I have this problem in ubuntu 19.04 right now. Any clue? Thanks
1748839,2019-03-23 14:16:07 UTC,"I have the same problem on Ubuntu 16.04 LTS
WiFi works perfectly from home (WPA2/WEP)
Does not connect to WPA2 Enterprise with PEAP. Checked with IT department , they could not solve it."
1748839,2019-03-23 15:27:30 UTC,"Use Firefox to connect to the hotspot is working for me .. need to find out
how to rejig the Ubuntu hotspot connector to use firefox .. might just be a
browser negotiation issue."
1748839,2019-04-11 08:04:39 UTC,"Confirmed the same problem, ubuntu 18.04.2 LTS AMD64, when trying to connect to ""eduroam"" in several sites in several countries."
1748839,2019-04-25 14:24:28 UTC,Nothing helpful in this post but can confirm this issue still exists in 19.04. :(
1748839,2019-04-30 16:59:32 UTC,I confirm the issue in 19.04. I just upgraded from 16.04. I used to get in fine on eduroam not anymore.
1748839,2019-05-06 11:38:59 UTC,I confirm this bug on 19.04. Wifi worked well on Ubuntu 16.04. Why doesn't Ubuntu go back to whatever worked in 16.04?
1748839,2019-05-07 03:18:28 UTC,"Think it has something to do with the browser used for hotpot
If anyone can find what confi controls in network manager for what browser to use (suspect chromium because it exhibits same behavior and is default install, but Firefox works) can find way to change configuration to use working browser
Maybe have time to look after finals"
1748839,2019-10-24 09:39:46 UTC,I have the problem despite I tried to forget the network and tried connecting again.
1748839,2020-01-23 02:57:09 UTC,"I have this same issue. What's very curious though is that I can connect to my work's network with Fedora 29+ (28 didn't work) as well as Arch/Manjaro based distros but not any Ubuntu version (including most recently 19.10) I can't. Just get repeated authentication failures. It's something to do with wpa_supplicant (or downstream) rather than anything upstream like network manager.
For instance using wpa_supplicant on fedora 28 to connect manually it goes through the error but in"
1748839,2020-01-23 02:59:57 UTC,"Note that the problem also occurs in all debian distros including the most recent testing (but again not fedora 29+/arch ones). I feel like if we can find the difference in how the MSCHAPV2 or etc is handled, we can solve this pesky bug."
1748839,2020-02-04 11:48:04 UTC,"I also have the problem with 18.04.4 LTS (up to date at time of writting). It seems to be related to the Wifi infrastructure since the problem appeared for me a few months ago (running successfully from May 2018 to Oct 2019).
However many other devices can connect successfully to the Wifi Infrastructure so there should be an incompatibility with it.
The problem is with the following Auth: WPA2 Enterprise, PEAP, No CA check, automatic PEAP version, MSCHAPv2."
1748839,2018-09-27 07:59:38 UTC,It is still an issue for me. The wifi authentication works perfectly with Eduroam (that requires a CA certificate) that is not the case with the other Wifi network (without CA certificate but all the same for the other settings).
1748839,2019-01-21 04:43:30 UTC,"Looking at the dmesg | grep wlp2s0 can also put some light on this.
Apparently, TX Power Saver causes connection loss for networks with PEAP authentication."
1748839,2018-09-26 07:34:26 UTC,"Fixed for me, I didn't do anything different or change anything, I guess one of the Ubuntu updates must've fixed it"
1748839,2018-04-05 11:32:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748839,2018-09-25 10:13:40 UTC,"I am glad that I could help somehow. I had the issue with a wifi provided by a Ubiquity AaccessPoint. I am pretty sure that there was no update on that in the meantime as it was a new install and configuration (however I am not the admin on that net and I have no details).
In the meantime I got an update on openvpn, bind9, dnsutils, liblwres160, libdns-export1100, libdns1100 - which maybe could have an impact (just wild guessing from the library names). No kernel update in the meantime, I am on 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48.
I am pretty sure that in my case it was only because although I tested with a few different settings on my first attempts, the solution was just using the correct settings (fitting the Access Point configuration)."
1748839,2018-09-25 11:13:06 UTC,I m still unable to connect to WPA2 Enterprise Network after installing all the apt updates
1748839,2018-05-01 16:03:38 UTC,"Same problem here, standard WPA2 works fine but not WPA2/PEAP.
Worked fine in 17.10."
1748839,2018-05-02 08:37:41 UTC,"Just an update, I was in a different office location today using WPA2 / PEAP and wifi connected right away. Same business, NW engineers tell me infrastructure is exactly the same in both locations - so mystery - phone Android connected perfectly but laptop did not (in other building)!
So pity the assignee as it maybe tricky to replicate."
1748839,2018-05-02 16:04:15 UTC,"I tried downgrading network-manager and wpasupplicant to the artful versions.
Still can't authenticate."
1748839,2018-05-02 16:19:41 UTC,This could be related https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1761003
1748839,2018-05-10 14:28:48 UTC,Also happens on 17.10
1748839,2018-05-15 15:33:32 UTC,Also got it. Up
1748839,2018-05-22 17:10:07 UTC,"This affects me as well. I consider this a security issue because the enterprise I'm connecting to only offers this encryption or no encryption, so until this is fixed, my network traffic is unencrypted. And that's sad."
1748839,2018-05-25 10:28:23 UTC,This affects me as well. And can't connect to my company tools.
1748839,2018-06-01 07:28:46 UTC,"Same problem here in Kubuntu 18.04.
The authentication layer works fine, but for some reason it fails in configuring the network."
1748839,2018-06-15 09:38:56 UTC,Same issue with Ubuntu 18.04 on a Dell XPS 15 9560.
1748839,2018-06-18 07:42:24 UTC,I have the same issue with (a clean/full wipe/ fresh install) Ubuntu 18.04 on a Dell XPS 15 9550.
1748839,2018-06-18 17:38:39 UTC,"Same issue on a Lenovo T480s.
I tried to apply this without any success : https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c"
1748839,2018-06-20 09:30:38 UTC,same here. A fix would be highly appreciated.
1748839,2018-05-01 09:32:44 UTC,"This affects me too, 18.04 WPA2/PLEAP  connect via phone tether OK but fails as above directly, worked fine under 17.10"
1748839,2018-06-27 09:20:49 UTC,"A potential fix has been proposed in my askubuntu quesion:
https://askubuntu.com/questions/1046810/cannot-downgrade-wpa-supplicant-to-fix-wifi-connection-to-a-corporate-network-w"
1748839,2018-09-25 09:42:24 UTC,"@mwildam : Due to your comment on that it might be resolved, I also checked the bug again.
For me this issue is now also resolved."
1748839,2018-09-25 08:24:02 UTC,"In my case I was able to solve the problem by changing some settings:
Security: WPA & WPA2 Enterprise
* Authentication: Protected EAP (PEAP)
* No certificate is required: Checked
PEAP version: Automatic
* Inner authentication: MSCHAPv2"
1748839,2018-09-17 22:56:24 UTC,@BrettSkogen - thanks for reporting back. I was going to try the OpenSSL downgrade myself but haven't had the time. I'd be curious to see what you find out by looking at the update-crypto-policies command. Let us know what you find out. Going to take a look at it myself now.
1748839,2018-09-17 22:44:04 UTC,"I can tell you something that doesn't work, to hopefully save you some
time. One of the earlier comments on this bug suggested that the issue was
being caused by support for 3DES being removed from Bionic Beaver. I
downloaded the source code for OpenSSL 1.1.0i, and compiled the code with
the option to enable weak ciphers. My install of OpenSSL now supports 3DES,
but I am still unable to connect to WPA2 Enterprise WiFi networks. I
downloaded the source code for the update-crypto-policies command that
Fedora uses. It looks like it is just a bunch of perl scripts. I am going
to look at what the LEGACY scripts do to see if I can figure out exactly
what option they are using on Fedora to work around this issue.
Unfortunately I haven't been able to look through all of the scripts yet."
1748839,2018-09-17 12:12:10 UTC,"I also ran into this issue after upgrading from 16.04 to 18.04.
Any updates on this?
What's the Ubuntu equivalent of the Fedora workaround for this? ($ update-crypto-policies --set LEGACY)
If it is not available, is it possible to make a fix by downgrading openSSL? If so, can you please explain the steps?"
1748839,2018-09-14 20:29:46 UTC,"I wanted to try the
  update-crypto-policies --set LEGACY
but I am using Ubuntu 18.04.1 and I could not find an equivalent command."
1748839,2018-06-26 15:54:14 UTC,Same problem here. Eduroam cannot be connected. Please solve!
1748839,2018-09-14 15:19:44 UTC,Kernel log for the previous attempts.
1748839,2018-09-14 18:01:15 UTC,Any updates on this? I ran into this issue after upgrading from 16.04 to 18.04.
1748839,2018-07-25 06:13:33 UTC,Update:
1748839,2018-07-24 13:44:30 UTC,This affects all academic users that uses eduroam to connect to the internet. Please fix. Eduroam did work with ubuntu 17.10
1748839,2018-09-14 15:18:02 UTC,"Dell Precision 7520, I also cannot connect to WPA2/PEAP WIFI. Here are my logs - I tried to connect to two slightly different configured wifi networks using that PEAP (I never heard of that before)."
1748839,2018-08-22 18:03:55 UTC,"I tried downgrading wpa-supplicant (mentioned by Lauwie), and it did not help this."
1748844,2018-03-05 08:23:26 UTC,Occurred again this morning and an automated bug report brought me back here.
1748844,2018-03-05 08:27:50 UTC,This morning the second automated bug report prompted me to create +bug1753393
1748844,2018-03-12 09:28:06 UTC,Seems simple enough to recreate this each time I restart the machine.
1748844,2018-03-19 10:21:37 UTC,Occurred again today.  New report raised at +bug1756839
1748844,2018-04-03 07:38:46 UTC,Happened again today.  Raised #1760792 this morning to see if the trace will work.  If it does not I shall try adding more -dev packages to see if the backtrace can be brought about.
1748844,2019-11-20 02:17:38 UTC,Target machins is Ubuntu 16.04:
1748846,2018-02-14 09:38:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1748846,2018-02-21 13:30:05 UTC,Verified the fixes to solve the issue on 4.13.0-36-generic.
1748846,2018-02-21 18:56:18 UTC,This bug was fixed in the package linux - 4.13.0-36.40
1748853,2018-06-20 02:28:28 UTC,"guodi, could you paste your wifi dev id and subsystem id here?
You can find it by ""lspci -nnk"", just the id like this [8086:A370][8086:42A4]"
1748853,2018-06-15 14:05:43 UTC,This bug was fixed in the package linux-oem - 4.15.0-1008.11
1748853,2018-06-14 14:24:17 UTC,"I updated to kernel 4.15.0.23 and upgraded to firmware 1.157.19,but wireless network and bluetooth does still not work,so does  the ethernet.So,I.don't know how to report the bug log."
1748853,2018-06-14 12:16:29 UTC,This bug was fixed in the package linux - 4.15.0-23.25
1748853,2018-06-13 09:30:49 UTC,This bug was fixed in the package linux-oem - 4.15.0-1008.11
1748853,2018-06-10 08:36:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748853,2018-06-11 15:08:06 UTC,This bug was fixed in the package linux - 4.15.0-23.25
1748853,2018-06-10 10:01:34 UTC,"Installed kernel 4.15.0-23.25 from bionic-proposed, Intel 9462NGW started working (Network controller [0280]: Intel Corporation Device [8086:a370] (rev 10))"
1748853,2018-05-24 18:05:28 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1748853,2018-02-21 19:08:44 UTC,This bug was fixed in the package linux-oem - 4.13.0-1021.23
1748853,2018-02-15 15:12:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1748853,2018-06-12 02:40:17 UTC,Bug #1776376
1748853,2018-05-15 16:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1748861,2019-12-05 13:58:29 UTC,Why is the version kept at v2.0.3 ? v3.0 is out!
1748861,2020-02-02 08:59:28 UTC,"> Why is the version kept at v2.0.3 ?
"
1748861,2020-10-22 19:57:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu."
1748881,2018-03-07 12:37:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748887,2018-02-12 17:13:00 UTC,"Chris, a couple questions about the template..."
1748887,2018-02-12 23:52:52 UTC,"Mike,"
1748891,2018-02-21 00:44:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748894,2018-02-13 03:07:40 UTC,Can you see if this happens on master?  Mitaka is no longer supported upstream.
1748894,2018-02-18 10:06:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748894,2018-02-18 10:19:15 UTC,"This happens to our cluster as well which is on pike, but somewhat in different way. Since the cluster is HA, instance do able to get the ip from one of the dhcp namespaces but dnsmasq does not work later if the problematic namespace ends up first in resolv.conf. When we delete the specific port from the network which automatically gets created after a few seconds, things start working again."
1748894,2019-02-12 15:12:39 UTC,"Same problem here, running Queens. DHCP packets are going out, but not reaching the server"
1748894,2019-11-07 06:51:42 UTC,"Confirmed. OpenStack Rocky.
DHCP packets not reaching the server."
1748895,2018-10-08 11:15:16 UTC,"The uploaded revision of SENDDOC works ok on my system (LO 6.1.2.1, Ubuntu 18.04.1) when Tools, Options, Internet, Email E-mail program is left blank, or filled as /usr/bin/xdg-email."
1748895,2018-10-08 11:13:15 UTC,"Created attachment 145467
A proposed revision for /usr/lib/libreoffice/program/senddoc"
1748895,2018-09-24 09:15:54 UTC,Re-opening per user comment and upstream report.
1748895,2018-09-18 11:23:56 UTC,"See also Ubuntu Bug #1748895
LO unable to find a working email configuration"
1748895,2018-09-20 10:01:12 UTC,"I should have added that when Tools ... Email is set to xdg-email (timed at 10:12) or set to be blank (timed at 10:16), then claws-mail is called, but without focus, and without any COMPOSE window.  Focus has to be manually restored to CLAWS by clicking on it, before anything else can be done ..."
1748895,2018-09-20 09:56:35 UTC,"With respect, I think the problem is related to apparmor.
When Tools/Options/Internet/Email is set to /usr/bin/claws-mail, the error window appears (working email client not found), an error message is sent to screen (Writer called from the command line),
""/usr/lib/libreoffice/program/senddoc: 366: /usr/lib/libreoffice/program/senddoc: /usr/bin/claws-mail: Permission denied"", and the kernel log contains 3 DENIED lines,
Sep 20 10:09:04 USER_ID-Inspiron-5767 kernel: [ 1965.191418] audit: type=1400 audit(1537434544.991:41): apparmor=""DENIED"" operation=""file_inherit"" profile=""libreoffice-senddoc"" name=""/home/USR/errors_090715.odt"" pid=4934 comm=""senddoc"" requested_mask=""wr"" denied_mask=""wr"" fsuid=1001 ouid=1001
Sep 20 10:09:04 USER_ID-Inspiron-5767 kernel: [ 1965.191423] audit: type=1400 audit(1537434544.991:42): apparmor=""DENIED"" operation=""file_inherit"" profile=""libreoffice-senddoc"" name=""/home/USR/.config/libreoffice/4/user/uno_packages/cache/uno_packages.pmap"" pid=4934 comm=""senddoc"" requested_mask=""wr"" denied_mask=""wr"" fsuid=1001 ouid=1001
Sep 20 10:09:05 USER_ID-Inspiron-5767 kernel: [ 1965.196286] audit: type=1400 audit(1537434544.995:43): apparmor=""DENIED"" operation=""exec"" profile=""libreoffice-senddoc"" name=""/usr/bin/claws-mail"" pid=4940 comm=""senddoc"" requested_mask=""x"" denied_mask=""x"" fsuid=1001 ouid=0"
1748895,2018-10-08 11:18:51 UTC,"Hi Bernard,
Thanks for the patch!
Would you mind submitting it to gerrit instead? you can have more informacion here https://wiki.documentfoundation.org/Development/gerrit/SubmitPatch"
1748895,2018-09-22 10:39:55 UTC,"Sorry to post so much, but I think I've found the problem, and a solution."
1748895,2018-10-08 18:09:18 UTC,"Hi Xisco,"
1748895,2019-08-14 11:04:15 UTC,"6.3.0.4 includes most of the changes I suggested, but still fails to operate properly - it switches the focus to the email client, but fails to create a new email."
1748895,2018-11-11 14:13:58 UTC,"GEARY works simply because it is not named in program senddoc, which then uses xdg-email as a default, to call the system email client, whatever it is.  But hey, as an entry in Tools/.../Internet, it works!"
1748895,2018-11-12 17:37:35 UTC,"(In reply to Bernard Moreton from comment #15)

> GEARY works simply because it is not named in program senddoc, which then
> uses xdg-email as a default, to call the system email client, whatever it
> is.  But hey, as an entry in Tools/.../Internet, it works!
>
> So, possibly, would ""/usr/bin/wxyz"" ...
"
1748895,2018-11-19 09:49:47 UTC,The original issue reported here was fixed.
1748895,2018-09-18 11:20:39 UTC,"The problem still affects me:
Ubuntu 18.04.1
LO 6.1.1.2
claws-mail
senddoc will not call claws-mail, or 'ls', or 'sleep'"
1748895,2020-11-26 11:30:59 UTC,"There is a new twist to this saga.
With LO 7.0.1.2 today I get an error message
/home/mbm/.claws-mail/mimetmp/.comments: unlink: Is a directory"
1748895,2020-11-27 06:06:03 UTC,"Hopefully not confusing things by adding this information... I use LibreOffice ""E-mail as PDF"" a lot. After about a fortnight of not having used it, when it worked fine, today I tried again."
1748895,2020-11-27 12:41:33 UTC,"And further to my last comment, the point is proved.
Claws[-mail] is set in senddoc to use
ATTACH=""${ATTACH:-}${ATTACH:+ }$2""
without any reference to encoding."
1748895,2021-01-19 01:39:50 UTC,I noticed a couple of days ago (17th or 18th Jan 2021) that Send e-mail as PDF started to work again. Presumably some update fixed things. So that's great!
1748895,2018-11-11 09:11:41 UTC,Since upgraded to LO 6.1.0 onwards started facing the problem of documents send by email stopped working
1748895,2018-09-18 09:50:33 UTC,"I modified 'senddoc' temporarily, to 'echo' the claws-mail command, and opened my testfile again from the commandline.  That showed
/usr/bin/claws-mail --attach /tmp/lu35337hoq3k.tmp/lu35337hoq3n.tmp/errors_090715.odt
(all on one line)."
1748895,2020-11-27 09:00:31 UTC,"Just to clarify my remarks yesterday,
the error window in Claws-mail showed a filename that looked very much as though it had been encoded."
1748895,2018-09-17 11:16:48 UTC,"Send by email still fails in 6.1.1.2.
This is disappointing, since 'sending' a document is a basic operation, which users would naturally expect.  As noted, this all worked prior to 6.0, so it's a regression."
1748895,2018-02-12 15:24:21 UTC,"Indeed, if I unload the apparmor profile for soffice.bin, sending the current document as e-mail attachment works again."
1748895,2018-02-12 15:50:47 UTC,Corresponding apparmor entry in journalctl:
1748895,2018-02-12 15:17:46 UTC,"Confirmed. This appears to be a regression. I can observe the issue in xenial and bionic, where the functionality used to work as expected in previous versions (5.1.6 and 5.4.3, respectively)."
1748895,2018-02-12 16:40:20 UTC,"The senddoc profile is wrong like the other one was too -
profile libreoffice-senddoc /usr/lib/libreoffice//usr/lib{,32,64}/libreoffice/program/senddoc {
  #include <abstractions/base>"
1748895,2018-02-12 16:51:11 UTC,The path to the senddoc executable is incorrect in the apparmor profile:
1748895,2018-02-12 18:16:34 UTC,"Bug filed upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=115659
And fixed proposed here: https://gerrit.libreoffice.org/#/c/49614/"
1748895,2018-02-12 18:34:16 UTC,And as a distro patch: https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=cb98b45509c8fe810daba893e56df2003466e02a
1748895,2018-02-21 19:08:31 UTC,This bug was fixed in the package libreoffice - 1:5.4.5-0ubuntu0.17.10.1
1748895,2018-02-21 19:49:15 UTC,Still in LO 6.0.x
1748895,2018-02-12 15:18:50 UTC,And the following error is most likely related:
1748895,2018-03-01 05:14:51 UTC,Still present with LO6 and Thunderbird on Ubuntu 16.04.03
1748895,2018-03-01 06:13:29 UTC,"apt policy libreoffice-common
libreoffice-common:
  Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
  Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
  Version table:
 *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500
        500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages
        500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status
     1:5.1.6~rc2-0ubuntu1~xenial3 500
        500 http://au.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        500 http://au.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages
     1:5.1.2-0ubuntu1 500
        500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        500 http://au.archive.ubuntu.com/ubuntu xenial/main i386 Packages"
1748895,2018-03-01 11:17:23 UTC,"This is fixed in libreoffice 6.0.1 in ubuntu 18.04, and will be fixed in the next update in the PPA for 16.04 (6.0.2)."
1748895,2018-03-01 14:18:47 UTC,Nope.  Still broken.
1748895,2018-03-01 15:25:09 UTC,"Please try to unset your email-client inside of libreoffice settings, and rely on the system-wide setting which can be made in e.g. gnome-control-center"
1748895,2018-03-01 16:02:05 UTC,"Okay, works now if </usr/bin/evolution> is deleted and client is left <blank>"
1748895,2018-03-05 17:13:13 UTC,"Description:
When tools/options/internet/email is set to /usr/bin/claws-mail, send by email fails.  If it's unsert, to allow a default of xdg-email, it still fails, and if it's explicitly set to /usr/bin/xdg-email it still does not work.  Trying to Send now leaves me in limbo, somewhere between LO and my email client (Claws), with neither having focus, so alt-tab gets me nowhere until I manually reassert focus on one or the other.
Build ID: 1:6.0.2~rc1-0ubuntu0.16.04.1~lo1
on Ubunto 16.04.4 LTS"
1748895,2018-03-05 23:13:32 UTC,"Confirm fixed under latest libreOffice update, and Ubuntu MATE 16.04
Thanks"
1748895,2018-03-06 07:32:06 UTC,"Tested and I can reproduce the issue when claws-mail is the default e-mail client on the system, even with apparmor profiles disabled (so unlikely to be an apparmor-related issue)."
1748895,2018-03-06 08:14:20 UTC,"(In reply to Olivier Tilloy from comment #1)

> Tested and I can reproduce the issue
"
1748895,2018-03-01 05:39:35 UTC,Which version exactly? Can you please share the output of:
1748895,2018-09-17 13:14:22 UTC,"I see a similar report on Apache OpenOffice, also on the Ubuntu bug reports.
Following a hint from the latter, I deleted the entry ""/usr/bin/claws-mail"" in Tools/Options/Internet/Email and tried again to send a document.  This time no error was reported to the GUI, but I'd called soffice from the commandline, and there an error had appeared ""/usr/lib/libreoffice/program/senddoc: 361: /usr/lib/libreoffice/program/senddoc: /usr/bin/claws-mail: Permission denied"""
1748912,2020-03-19 07:23:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748914,2018-05-23 07:45:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748925,2018-02-12 16:39:03 UTC,apport information
1748925,2018-02-12 16:39:02 UTC,apport information
1748925,2020-10-23 06:47:58 UTC,But it is still available in bionic and it was not working ever since although it would be just adding the simple fix!
1748925,2020-10-22 19:58:00 UTC,Closing since the package is removed from Ubuntu
1748925,2019-01-16 10:11:24 UTC,I can confirm that building the Debian package from the upstream repo with the fix Tobias mentioned work perfectly fine on Bionic.
1748925,2019-01-15 14:12:09 UTC,With the actual version from the upstream repository I get still the following error:
1748925,2018-02-12 16:39:00 UTC,apport information
1748925,2018-02-13 17:54:49 UTC,Both 1.10.0 and 1.9.0 + revision cb30615c7174 work here.
1748925,2018-02-13 14:08:42 UTC,I would.  I assume this is the fix: https://hg.logilab.org/review/hgview/rev/cb30615c7174
1748925,2018-02-13 09:32:08 UTC,"Hi Ethan, thanks for reporting this bug and using hgview. I believe a fix has been pushed upstream https://hg.logilab.org/review/hgview but has not yet been published or arrived in debian / ubuntu. Would you be willing to try out an install from source to confirm this ? I've notified the maintainers of hgview to encourage them to push this update where it need to be pushed."
1748925,2018-02-12 17:48:50 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1748925,2018-02-12 16:39:04 UTC,apport information
1748925,2018-02-13 18:13:19 UTC,"Needs an upstream/ubuntu upgrade for Bionic
 https://www.logilab.org/ticket/10126859"
1748928,2018-02-13 10:12:47 UTC,from term.log
1748928,2018-02-13 10:16:15 UTC,The only thing the postinst script does is run update-xmlcatalog. Reassigning to xml-core
1748942,2018-04-20 13:14:37 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1748942,2018-02-16 05:57:12 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc2 release candidate.
1748942,2018-02-16 00:27:54 UTC,"Reviewed:  https://review.openstack.org/545037
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d0c10db716c6d5a90ed329ba4806535ec91b34c0
Submitter: Zuul
Branch:    stable/queens"
1748942,2018-02-15 17:06:57 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/545037"
1748942,2018-02-12 19:35:17 UTC,"(1:29:28 PM) mgoddard: mriedem: the scheduling works, but any flavor-requested traits won't be pushed to the ironic node's instance_info. These are not yet used by ironic, but will be used in future for some capabilities-like things
(1:29:49 PM) mriedem: mgoddard: if they aren't used in ironic in queens, then it's not something worth holding up rc2 IMO"
1748942,2018-02-12 19:29:04 UTC,How is instance_info.traits used in nova? What impact does this have? What doesn't work if we don't fix this?
1748942,2018-02-15 17:04:41 UTC,"Reviewed:  https://review.openstack.org/543574
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=54713a834f2a0e5b55b8f77c601ff35eb74b9b09
Submitter: Zuul
Branch:    master"
1748942,2018-02-12 18:42:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543574"
1748945,2018-02-12 19:29:38 UTC,"I tried to push this up to my PPA, but ran into dependency issues... It wants the following: binutils-mingw-w64-i686 (>= 2.28~), binutils-mingw-w64-x86-64 (>= 2.28~), g++-7, gcc-7-source (>= 7.2.0-20), gnat-7"
1748945,2018-02-12 20:42:32 UTC,"Update: I tried pushing a backport from artful, and that only blocked on gcc-6. I found ppa:ubuntu-toolchain-r/test which has a gcc-6 for Xenial, and am now trying a build. Maybe this will work better?"
1748951,2018-02-13 16:17:48 UTC,"We are using the sysctl ansible module, so it should be idempotent, and therefore not have issues with its edition."
1748951,2018-02-13 20:15:46 UTC,"In our case we have a post-provisioning script that writes a specific /etc/sysctl.conf. This could be handled better and I do not have a strong opinion on the default value of ""sysctl_file"" but I do think we should be able to override it."
1748951,2018-02-20 16:44:58 UTC,"Using the module would work without the need to implement sysctl_file.
We've considered the sysctl_file for inclusion and are not against including it, should someone patch it."
1748956,2019-05-13 14:00:40 UTC,This bug was fixed in the package ubuntu-meta - 1.434
1748956,2018-08-12 17:41:49 UTC,This bug was fixed in the package byobu - 5.127-0ubuntu1
1748956,2019-05-10 06:20:14 UTC,"TBH that is just showing that [1], fell through the cracks :-/"
1748956,2018-03-28 13:34:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1748970,2018-04-19 19:31:15 UTC,This issue was fixed in the openstack/keystone 14.0.0.0b1 development milestone.
1748970,2018-02-15 21:57:27 UTC,"Reviewed:  https://review.openstack.org/544096
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a1ea04de86ebc57e7c2ba142c346f54aa93745c1
Submitter: Zuul
Branch:    stable/queens"
1748970,2018-02-14 18:32:07 UTC,"Reviewed:  https://review.openstack.org/544095
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=752d299d58f63810136966d9dc9a6e97252c9d32
Submitter: Zuul
Branch:    stable/queens"
1748970,2018-02-14 06:56:06 UTC,"Reviewed:  https://review.openstack.org/544012
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8748e729b2f139c245316fcece181625978c70a1
Submitter: Zuul
Branch:    master"
1748970,2018-02-14 06:55:53 UTC,"Reviewed:  https://review.openstack.org/544011
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a226a3d8be5ba720f149606a84df0432ec4858c7
Submitter: Zuul
Branch:    master"
1748970,2018-02-22 15:11:06 UTC,This issue was fixed in the openstack/keystone 13.0.0.0rc2 release candidate.
1748970,2018-02-13 21:41:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544095"
1748970,2018-02-13 17:18:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544012"
1748970,2018-02-13 17:18:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544011"
1748970,2018-02-13 17:16:38 UTC,"This is actually a bug in the role assignment API. When asking keystone for a list of role assignments for a specific role (GET /v3/role_assignments?role.id={role_id}), it won't prune system role assignments that don't match the role in question. This was causing a problem because we have a notification call back system that attempts to remove assignments before a role is deleted [0]. When the role assignment API goes to ask for all role assignments for a specific role, it doesn't filter out the system role assignments [1]. This was problematic because it was returning a system role assignment for the admin user, which resulted in a false revocation event getting persisted. As soon as tempest cleaned up the roles for a test class, a revocation event would be stored for the admin user and prevent them from cleaning up user, etc..."
1748970,2018-02-13 14:46:45 UTC,"Is the revocation even coming from the Role assignment?  It should not be, but we used to be really aggressive about revocations upon changes.  That was more important with PKI tokens than today with Fernet."
1748970,2018-02-13 05:19:25 UTC,"I was able to recreate this locally with tempest and keystone. It appears that the token used to delete users or list domain is considered invalid during the token validation process, resulting in a 401 [0]. Keystone compares the token being sent with the request against all matched revocation events it knows about, and it does determine a match. The 401 always pops up during tearDown or when clearing credentials in tempest."
1748970,2018-02-13 21:41:23 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544096"
1748970,2018-02-12 21:25:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/543622"
1748971,2018-02-13 19:38:40 UTC,"Here's two examples of how to generate an ARA report (or not) based on the status of the job:
- https://github.com/openstack/openstack-ansible/blob/7f192b104f3c27fddfc2f86b9b7d61e9222b124c/scripts/scripts-library.sh#L149
- https://github.com/openstack-infra/zuul-jobs/blob/46fb37f8bbb30b03e95a19e73fd84341dac110cf/roles/emit-ara-html/tasks/main.yaml#L24"
1748971,2021-02-17 17:10:05 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1748998,2018-02-12 21:11:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749003,2018-02-26 05:04:57 UTC,Where did this get to? I think we landed the fix for it.
1749005,2018-02-14 14:16:18 UTC,https://github.com/juju/juju/pull/8377
1749008,2018-02-12 21:24:36 UTC,I have found that (the version I have installed was eyeD3-0.8.4) If I just install eyed3 0.8 using:
1749008,2018-05-28 15:11:39 UTC,Why don't you install with sudo apt-get install python-eyed3 or sudo apt-get install python3-eyed3 ? And does that still result in the same error?
1749016,2018-03-06 11:03:26 UTC,"On Mon, Feb 12, 2018 at 09:44:09PM -0000, Michael Fruchtman wrote:

> Public bug reported:
>
> When converting a VMDK to VHDX the resulting VHDX's Region table has a
> small error. According to the VHDX specification the BAT and Metadata
> entries for the region header required bit should be set to 1.  In a
> VHDX created by qemu-img, this bit is not set.
"
1749019,2018-02-13 15:07:44 UTC,command line in maas rescue/ephemeral environment for v3 will look like:
1749019,2018-02-13 15:16:26 UTC,Next image for bionic should have this fix in place.
1749019,2018-02-13 20:13:16 UTC,"This is fix-committed in maas-images.
I would expect that the next bionic image to come out will have the fix.
So anything > 20180212 should be good."
1749028,2019-10-01 22:29:37 UTC,For a while now snapd adds a special attribute to the mount units for each snap so that GUI apps know not to show it. I just double checked on my Ubuntu 19.10 system and none of the many snaps I have installed show up in gnome disks.
1749030,2018-08-31 07:43:20 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1749030,2018-08-31 07:43:29 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/545487
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1749030,2018-02-16 23:20:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545487"
1749044,2018-02-13 06:14:17 UTC,There's a syntax error in /etc/default/grub
1749044,2018-02-13 16:02:38 UTC,"Thank you very much, Daniel"
1749044,2019-06-17 00:24:34 UTC,Hola.
1749057,2018-06-04 13:21:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572102"
1749057,2018-06-29 13:36:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/579159"
1749071,2018-02-13 08:38:36 UTC,"Thanks for your report. It seems to be correct upstream (in Debian), so it remains to fix it in Ubuntu too:"
1749075,2018-02-13 06:18:25 UTC,Can you please provide a screenshot or photo of the problem you're describing?
1749075,2018-02-23 05:42:06 UTC,The following extra styles should be added into both Ambiance and Radiance:
1749089,2018-02-14 17:44:16 UTC,"+1 to promote, results here: https://trello.com/c/Y9LW1c2P/199-pc-kernel-440-116140-104"
1749089,2018-02-20 15:08:59 UTC,Regression tests results were successful.
1749089,2018-02-21 04:37:14 UTC,Hardware Certification have begun testing this -proposed kernel.
1749089,2018-02-22 08:56:33 UTC,The package has been published and the bug is being set to Fix Released
1749090,2018-02-19 17:29:20 UTC,Regression test results look good.
1749090,2018-02-21 20:34:03 UTC,The package has been published and the bug is being set to Fix Released
1749091,2018-02-21 04:38:27 UTC,Hardware Certification have begun testing this -proposed kernel.
1749091,2018-02-21 18:58:58 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-116.140~14.04.1
1749091,2018-02-21 20:34:48 UTC,The package has been published and the bug is being set to Fix Released
1749091,2018-02-20 10:44:44 UTC,Regression tests results were successful.
1749092,2018-02-21 19:11:47 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1019.24
1749092,2018-02-21 20:35:19 UTC,The package has been published and the bug is being set to Fix Released
1749093,2018-02-19 17:04:26 UTC,Regression test results look good.
1749093,2018-02-21 20:36:09 UTC,The package has been published and the bug is being set to Fix Released
1749094,2018-02-14 17:43:35 UTC,"+1 to promote snap, results here: https://trello.com/c/3GbGyg3T/198-pi2-kernel-440-108593-50"
1749094,2018-02-21 19:07:44 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1085.93
1749094,2018-02-21 20:36:40 UTC,The package has been published and the bug is being set to Fix Released
1749095,2018-02-23 10:53:32 UTC,Hardware Certification have begun testing this -proposed kernel.
1749095,2018-02-23 12:49:24 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/euclid/4.4.0-9025.27/euclid-proposed-published.html"
1749095,2018-02-23 19:32:13 UTC,This bug was fixed in the package linux-euclid - 4.4.0-9025.27
1749095,2018-02-23 20:00:42 UTC,The package has been published and the bug is being set to Fix Released
1749096,2018-04-05 08:35:01 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1088.93
1749096,2018-02-21 19:07:19 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1087.92
1749096,2018-02-22 08:52:47 UTC,The package has been published and the bug is being set to Fix Released
1749096,2018-02-14 17:45:03 UTC,"+1 for promotion, results here: https://trello.com/c/ZljPY3vV/197-dragonboard-kernel-440-108792-43"
1749102,2019-04-12 00:08:06 UTC,Fixed in version 1.14-1.1 which will be shipped in Ubuntu Disco.
1749136,2018-02-15 08:43:08 UTC,"Do you mean built in commands, or a wiki page documenting how to get such information?"
1749136,2018-02-15 09:16:52 UTC,A built in command. bash plugins are tedious when you're using juju from dozens of different servers.
1749142,2019-09-25 07:55:49 UTC,"Any relevant logs in /var/log/kolla/nova/ ?
What version of kolla?"
1749150,2018-02-14 07:31:35 UTC,apport information
1749150,2018-02-14 07:31:34 UTC,apport information
1749150,2018-02-14 07:31:36 UTC,apport information
1749150,2018-02-14 07:31:37 UTC,apport information
1749150,2018-02-14 07:36:30 UTC,Just have sent info from the second host (Intel+NVidia; more prone to the issue). Will do it for the first host in a few hours.
1749150,2018-02-14 07:31:41 UTC,apport information
1749150,2018-02-14 10:54:15 UTC,"On the first host, apport-collect crashed with:"
1749150,2018-02-14 16:47:12 UTC,"Valentin Nechayev, please don't apport-collect from different machines. If you have an issue with different hardware, it is most helpful to file a new report instead via a terminal:
ubuntu-bug xorg"
1749150,2018-04-09 04:59:39 UTC,"Well, I was unable to spend much time in Gnome to reproduce the effect or refute it.
OTOH it wasn't reproduced since this ticket start on host 1 and became much less frequent on host 2, after I switched drivers on it nvidia->nouveau and back.
Also a new laptop showed it, but also rather rarely."
1749150,2018-06-09 04:17:21 UTC,[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]
1749150,2018-02-14 07:31:40 UTC,apport information
1749150,2018-02-14 07:31:33 UTC,apport information
1749150,2018-02-14 07:31:38 UTC,apport information
1749150,2018-02-14 07:31:31 UTC,apport information
1749150,2018-02-14 07:31:32 UTC,apport information
1749150,2018-02-13 23:00:18 UTC,"Valentin Nechayev, thank you for reporting this and helping make Ubuntu better."
1749150,2018-02-14 07:31:21 UTC,apport information
1749150,2018-02-14 07:31:22 UTC,apport information
1749150,2018-02-14 07:31:23 UTC,apport information
1749150,2018-02-14 07:31:24 UTC,apport information
1749150,2018-02-14 07:31:29 UTC,apport information
1749150,2018-02-14 07:31:26 UTC,apport information
1749150,2018-02-14 07:31:30 UTC,apport information
1749150,2018-02-14 07:31:28 UTC,apport information
1749150,2018-02-14 07:31:25 UTC,apport information
1749150,2018-02-14 07:31:27 UTC,apport information
1749150,2018-02-14 07:31:27 UTC,apport information
1749151,2019-10-04 04:26:42 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1749162,2018-03-19 15:47:51 UTC,This seems like a operational performance improvement and seems minor enough that I really don't think an RFE is needed. Perhaps we should just consider it rfe-approved?
1749163,2018-02-13 12:14:06 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=793420
1749166,2018-03-19 15:44:13 UTC,"I don't understand what the actual desire or problem is here, in terms of what we wish to change or improve. I think it would be good to create distinct bugs/tasks to detail what can be improved upon and move on from there, that way there is improved visibility and new contributors can help."
1749173,2018-02-21 00:17:32 UTC,"LUKS FAQ includes ""Note that automatic wiping is on the TODO list for cryptsetup, so at some time in the future this will become unnecessary."""
1749185,2018-03-18 07:58:30 UTC,"This behavior is not currently supported by Mahara. Copied of artefacts only works properly when the artefacts are placed into their own blocks. When they are in text blocks, they are only links, but Mahara does not recognize them as proper artefacts as if they were in the ""Files to download"" block for example."
1749193,2020-03-11 18:59:07 UTC,"Reviewed:  https://review.opendev.org/672780
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=e47e39827735268b507ae6a2b1cea77be65edabf
Submitter: Zuul
Branch:    master"
1749193,2018-02-13 13:51:29 UTC,proposed spec: https://review.openstack.org/#/c/543936
1749193,2018-09-13 17:10:49 UTC,"Reviewed:  https://review.openstack.org/543936
Committed: https://git.openstack.org/cgit/openstack/ironic-specs/commit/?id=f8816d0b3cad50ced8badd1dd5f8ac7d5f600bd7
Submitter: Zuul
Branch:    master"
1749213,2018-02-13 17:45:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749215,2019-04-19 15:19:35 UTC,I think this possibly introduced a regression bug 1825537 so I've marked Ocata as won't fix for this bug.
1749215,2018-04-20 13:14:06 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1749215,2018-04-02 13:18:44 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1749215,2018-03-31 00:53:27 UTC,"Reviewed:  https://review.openstack.org/548584
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8f6371c868625351e3b017d6b2aaaa458cd73172
Submitter: Zuul
Branch:    stable/pike"
1749215,2018-03-07 23:30:26 UTC,This issue was fixed in the openstack/nova 17.0.1 release.
1749215,2018-02-27 14:23:21 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/548300"
1749215,2018-02-28 12:32:36 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/548584"
1749215,2018-02-27 13:30:12 UTC,"Reviewed:  https://review.openstack.org/543971
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=caf167862dd82e98f0189c9598856de57dfa7d35
Submitter: Zuul
Branch:    master"
1749215,2018-02-13 16:35:23 UTC,During reproduction I saw that following trace:
1749215,2018-02-13 15:59:07 UTC,"> Observe even after the instance has been destroyed, there is still 1 set of allocations for the instance.
"
1749215,2018-02-13 15:33:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/543971"
1749215,2018-02-28 15:48:31 UTC,"Reviewed:  https://review.openstack.org/548300
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5039511840bd64151f3111d9c8d7d8a01344193b
Submitter: Zuul
Branch:    stable/queens"
1749215,2018-02-14 11:19:47 UTC,"So what I understood so far:
* resize fails but as it was a cast the ResizeError exception does not propagated back hence the above trace => allocation consumed by the migration remains after the migration fails
* the migration is set to error state [1] and therefore it does not considered as ongoing by the resource tracker [2] periodic _update_available_resource calculation [3]. => allocation consumed by the migration doesn't cleaned up by the periodic _update_available_resource task.
* there is another periodic task specifically to clean up failed resizes _cleanup_incomplete_migrations [4] , it sees the failed resize but it only cares about deleted instances [5] and does not delete the allocation at all.
* when the instance is deleted we delete the migrations but not the possible allocations due to that migrations."
1749221,2018-02-13 16:00:06 UTC,This change was made by a bot.
1749221,2018-02-13 16:43:09 UTC,"Can you reproduce the bug, or was it a one time event?"
1749221,2018-02-13 19:17:09 UTC,"It happens within 3 minutes of system boot into 4.13 kernel.
2 systems reproduced this.  You're lucky to be able to log in before it crashes."
1749221,2018-02-14 03:16:49 UTC,"Since you are using apparmor=0 parameter,
this will be a duplicate of bug 1734327."
1749221,2018-02-15 02:10:50 UTC,"Tetsuo,
Thanks for the info.  Removing 'apparmor=0' isn't an option right now both because MAAS doesn't let you control that and because it is there to work around other bugs (originally bug 1677336)."
1749221,2018-02-15 20:57:10 UTC,"I built a test kernel with the patch from Tetsuo.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1734327"
1749221,2018-07-24 09:32:07 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1749223,2019-10-20 09:07:07 UTC,It sounds like I have the same problem.
1749229,2018-03-09 14:29:19 UTC,"> @dsmythies - what was the different way?
"
1749229,2018-02-28 03:06:37 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1749229,2018-03-09 07:59:55 UTC,@dsmythies - what was the different way?
1749230,2018-03-12 13:30:20 UTC,"After trying to reproduce this bug on Xubuntu 18.04 (with a V 15.0 kernel), there is a very good new :
No more bug on my Asus T101HA-GR030T about the micro SD cards management :
All the types of 32 GB micro SD cards i tested (SANDISK, SAMSUNG, TOSHIBA) are recognized at OS-INIT and works fine even if dismount and remount."
1749230,2018-02-13 16:30:09 UTC,This change was made by a bot.
1749230,2018-02-14 13:39:05 UTC,Hi!
1749230,2018-02-13 16:44:06 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1749234,2018-02-14 04:51:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544165"
1749234,2018-02-23 03:27:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/547253"
1749234,2018-02-24 02:31:08 UTC,"Reviewed:  https://review.openstack.org/547253
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=e285e319d8f44feae6c6e700c7015efa5f42a78b
Submitter: Zuul
Branch:    stable/queens"
1749234,2018-08-20 18:31:37 UTC,This issue was fixed in the openstack/zun 1.0.1 release.
1749235,2018-02-13 16:54:26 UTC,"The link to https://docs.openstack.org/admin-guide/compute-node-down.html#evacuate-instances is also wrong, and there are a bunch of other problems in this doc so I'll fix those all together."
1749235,2018-02-13 17:16:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544010"
1749235,2018-02-13 17:22:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/544015"
1749235,2018-02-16 20:06:19 UTC,"Reviewed:  https://review.openstack.org/544010
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8be8d02aa77ebbe6687fa9ec4c74949cde0bf596
Submitter: Zuul
Branch:    master"
1749235,2018-02-28 20:45:26 UTC,"Reviewed:  https://review.openstack.org/544015
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4746a0d63862a4bb06a04636e6c0e4be9b38e82e
Submitter: Zuul
Branch:    master"
1749235,2018-03-01 08:34:55 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/548873"
1749235,2018-03-28 17:23:00 UTC,"Reviewed:  https://review.openstack.org/548873
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2ba48f3fa0c7665bb29c4f8de3e9efd130ae12a3
Submitter: Zuul
Branch:    stable/queens"
1749235,2018-04-02 13:09:25 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1749235,2018-04-20 13:14:34 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1749236,2018-02-13 19:27:58 UTC,Is not fixed in trunk. Basicaly the LPE try to apply a LPE to a empty path with only a move to. I do a fix soon and backport it
1749236,2018-02-13 17:15:59 UTC,"Have you tested the same in master? If I remember correctly this should already be fixed, see [1] for the relevant discussion and [2] for the MR that triggered it (you were actually commenting on that one)."
1749236,2018-02-13 18:03:56 UTC,"Ah, okay. I didn't follow that discussion closely, as I didn't really understand what you all were talking about at the time. As far as I was concerned, this was about boolops on clones, the LPE part didn't register."
1749237,2018-02-13 16:46:59 UTC,"FIX=  sudo su
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo -1 > $i; done"
1749237,2019-06-17 04:17:26 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1749237,2018-02-14 04:33:53 UTC,"Now i need to find a way to make this persistent on reboot
cause the seagate only gets detected with usb 3.0 connected before ubuntu boot on 1  same usb 3.0 port only, not the other one(s)
if i dont connect it, i have to manually enter the autosuspend command every time again"
1749237,2018-02-15 08:30:47 UTC,"On windows 10 only 1 usb 3.0 port detects the seagate, i suspect a faulty hardware"
1749237,2018-02-14 09:23:18 UTC,"Tested 18.04  daily on the problem machine liveusb, also does not get recognized"
1749237,2019-04-17 06:07:23 UTC,"Hello,
do you still have this issue with the latest kernel?
and can you confirm this is not a HW issue?"
1749244,2018-02-13 16:55:04 UTC,This is occurring on stable/queens on commit 49c50dfa2eeed490ca984c07cdc011e925233ec3.
1749244,2018-08-01 17:16:17 UTC,This test fails for py2 and py3.
1749244,2018-08-02 04:44:23 UTC,It's passing on my env.
1749244,2018-08-20 08:51:41 UTC,"meets this in our CI:
http://paste.openstack.org/show/728408/"
1749244,2018-10-19 07:27:39 UTC,"We ran into the same issue in our infrastructure. Valuable hint was the following entry in the debug output of tox: ""GET http://no.where/v2.0"" - which resulted in a 200 OK response. On a local system this was not the case as ""no.where"" should not resolve to anything and the unit test actually expects an error instead of a successful connection here."
1749244,2020-09-04 12:58:01 UTC,I cannot currently reproduce this error with the queens branches so I'm going to assume that it's currently fix-released / working as intended.
1749244,2018-08-02 12:43:23 UTC,Hmm that's interesting. I just hit it on master on Ubuntu Cosmic. Maybe it's a difference in the underlying distro.
1749248,2020-03-21 19:46:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749252,2018-02-21 08:07:53 UTC,Could you elaborate a bit more what you are requesting here?
1749252,2018-02-23 21:14:06 UTC,"I checked the midi controller wizard now but didn't find the requested controls.
The library contextmenu is usable but not very fast. (find title; right click; hover and move; left click)"
1749252,2020-08-24 21:08:41 UTC,MIDI control for fixing incorrect BPM detection would be incredibly welcome.
1749252,2020-08-25 13:52:40 UTC,"FYI
in Mixxx 2.3 there's no need to go back to the library anymore: you can open the track context menu by right-clicking on a track property in decks: title, artist, comment (Tango only). There you have a 'Adjust BPM' menu with all options."
1749254,2018-02-13 19:11:14 UTC,"Analyzing the logs, I observed that the execution sequence is as follows:"
1749254,2020-06-01 14:47:05 UTC,This was fixed when we fixed https://bugs.launchpad.net/os-brick/+bug/1756206 with review https://review.opendev.org/#/c/554704/
1749259,2018-02-13 18:31:47 UTC,Agreed.
1749259,2018-02-13 18:24:04 UTC,"If we add something like this, I think I would want an ""Are You Sure?"" prompt to be included. I'm concerned that people may inadvertently click it without realizing that they are removing all of their local settings."
1749262,2018-02-14 16:41:53 UTC,The newest OS X High Sierra operating system with the latest Java 9
1749262,2018-02-13 21:18:43 UTC,Thanks for reporting.
1749262,2018-08-23 20:00:52 UTC,"Im on 10.13.6, java 10. sikuli 1.4 and get this:"
1749262,2018-02-14 16:34:38 UTC,I just tried to reproduce the problem - no success.
1749262,2018-02-14 19:45:30 UTC,"WINDOW 10 with SikuliX IDE :
java 9.0.4
Java(TM) SE Runtime Environment (build 9.0.4+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)"
1749262,2018-02-15 11:19:07 UTC,Thanks. Confirmed: see the bug.
1749262,2018-02-14 17:42:26 UTC,"further details on  Environment:
java version ""9.0.4""
Java(TM) SE Runtime Environment (build 9.0.4+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)"
1749264,2018-02-13 20:25:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544067"
1749264,2018-02-13 21:43:34 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544098"
1749264,2018-02-13 21:43:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544099"
1749264,2018-02-14 00:50:15 UTC,"Reviewed:  https://review.openstack.org/544067
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=25596b874ce5b70a29ca53a95060f835fa1da955
Submitter: Zuul
Branch:    master"
1749264,2018-02-14 01:04:06 UTC,"Reviewed:  https://review.openstack.org/543622
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=3a3b3c5b5a35c93b9f3df79887805956208eaf5f
Submitter: Zuul
Branch:    master"
1749264,2018-02-14 18:16:30 UTC,"Reviewed:  https://review.openstack.org/544098
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=298f4458bafcb73be23a2812cc2cdda32ff38ce8
Submitter: Zuul
Branch:    stable/queens"
1749264,2018-02-14 18:16:39 UTC,"Reviewed:  https://review.openstack.org/544099
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=445837fd8bc89bbf0ade3abbfa21074a6c377581
Submitter: Zuul
Branch:    stable/queens"
1749264,2018-02-22 15:11:08 UTC,This issue was fixed in the openstack/keystone 13.0.0.0rc2 release candidate.
1749264,2018-04-19 19:31:18 UTC,This issue was fixed in the openstack/keystone 14.0.0.0b1 development milestone.
1749267,2018-04-19 19:31:17 UTC,This issue was fixed in the openstack/keystone 14.0.0.0b1 development milestone.
1749267,2018-02-22 15:11:04 UTC,This issue was fixed in the openstack/keystone 13.0.0.0rc2 release candidate.
1749267,2018-02-20 17:27:39 UTC,"Reviewed:  https://review.openstack.org/544101
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8646f40a4080eddb5f9cc58df2ce478ccfd38a77
Submitter: Zuul
Branch:    stable/queens"
1749267,2018-02-14 18:31:40 UTC,"Reviewed:  https://review.openstack.org/544100
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=89152d73ac167b71b11617bcf946c99c38956184
Submitter: Zuul
Branch:    stable/queens"
1749267,2018-02-13 20:51:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544074"
1749267,2018-02-14 09:08:21 UTC,"Reviewed:  https://review.openstack.org/544073
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=3fa997531f757a832aab209d585bb98503e72cc2
Submitter: Zuul
Branch:    master"
1749267,2018-02-13 21:45:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544101"
1749267,2018-02-13 21:45:29 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544100"
1749267,2018-02-13 20:51:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544073"
1749267,2018-02-14 09:08:32 UTC,"Reviewed:  https://review.openstack.org/544074
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5a24b96d951537fb12deb7050eb2e7dd7d40fc81
Submitter: Zuul
Branch:    master"
1749268,2018-02-22 15:11:05 UTC,This issue was fixed in the openstack/keystone 13.0.0.0rc2 release candidate.
1749268,2018-04-19 19:31:13 UTC,This issue was fixed in the openstack/keystone 14.0.0.0b1 development milestone.
1749268,2018-02-13 21:41:38 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/544097"
1749268,2018-02-14 06:56:16 UTC,"Reviewed:  https://review.openstack.org/530410
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=3c524e6491c1b35a2f8413ebe046c238bf530d71
Submitter: Zuul
Branch:    master"
1749268,2018-02-15 21:57:38 UTC,"Reviewed:  https://review.openstack.org/544097
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ddd7ff300e9159899f27a27fb3dda8ef9b91be1f
Submitter: Zuul
Branch:    stable/queens"
1749272,2018-02-15 19:01:38 UTC,"After some more experimentation, it turns out that even after destroying the default model and creating a new one it is impossible to add existing subnets using add-subnet. It is possible though to add subnets as part of the add-space command. So, there are two workarounds."
1749272,2018-08-17 03:52:32 UTC,"""juju-core"" is a project where we track Juju 1.x issues and suggestions. ""juju"" is the project for Juju 2.x. Re-targeting this report for visibility."
1749276,2018-02-13 21:40:30 UTC,there is a discussion about this at
1749276,2019-10-01 22:28:02 UTC,The dvb interface has been implemented and deployed a while ago. Marking this bug as fix released.
1749278,2018-12-03 22:36:51 UTC,We can set this with model config through FCE.
1749278,2019-07-03 17:33:27 UTC,It's fine as is.
1749279,2018-02-14 17:36:23 UTC,"I don't see how this is an apport issue, that's likely just a message from your browser."
1749282,2018-08-31 09:25:44 UTC,"This has now been fixed upstream (https://github.com/CanonicalLtd/netplan/pull/42/commits/3682933b73b552af8984bf0a3f109158219ead89). The yaml key is 'from'. It has been there for a while but was broken (it rendered From= instead of PreferredSource=), but is now the fix is now committed and should be in the next release."
1749282,2018-07-31 03:08:55 UTC,Any progress or timeline for when a fix might be released?
1749282,2018-04-19 22:06:24 UTC,Do you have an email address so I can properly credit this change?
1749282,2018-02-13 22:02:38 UTC,"This patch implements the proposed feature, however, the following caveats exist:"
1749282,2018-04-20 17:08:00 UTC,<email address hidden>
1749282,2018-04-09 15:14:01 UTC,"Patch looks good; I will apply this (with the minimal change of having the field in YAML called ""source"" rather than ""src"")."
1749283,2019-03-27 22:32:41 UTC,"Hi Christian,"
1749283,2019-03-28 07:05:29 UTC,"> > did your testing confirm that this would help your case?
>
> Sorry, have not had a chance to test this yet (delivering on-site).
>
"
1749283,2019-04-10 14:47:04 UTC,"@Dmitrii - I got Christian involved in this at your request, is it possible for you to confirm if the PPA contains a valid fix or get Christian a test case?"
1749283,2019-03-27 15:16:32 UTC,"The MPs are approved as well now, did your testing confirm that this would help your case?"
1749283,2019-06-03 06:08:34 UTC,"Following your request to ignore the resource-agent portion of this and just for postgresql-common I'm actually with Christoph on this.
In general we haven't had a delta on postgres packages for Debian maintenance on these packages is really good. If anything we have short one-off changes, as an example look at the current Delta in Eoan - it already is accepted in Debian and will be synced away soon. And we should keep it this way. Differences are ok for SRUs if ok under the SRU policy, but not going forward e.g. Eoan."
1749283,2019-06-03 08:27:06 UTC,"I agree - the postgresql-common should not be touched, nor there is a need to create an SRU for it.
However, resource-agents should be fixed, and only for Xenial and Bionic. But, I felt it was 'cleaner' to do it in a separate bug, LP: #1762492."
1749283,2019-06-03 09:01:21 UTC,"Thanks for the clarification Mario!
Now things fit together.
I'll mark the resource agent tasks invalid here per these comments to make sure no one is confused again."
1749283,2019-05-31 11:10:47 UTC,"@Christian, I've uploaded test pacakages to this ppa: https://launchpad.net/~mariosplivalo/+archive/ubuntu/lp1762492"
1749283,2019-03-25 11:46:51 UTC,"Note: I have seen your fixes to the Foundation Cloud for the same purpose, that was one more use case but that is fixed now as well right?"
1749283,2019-03-01 11:38:50 UTC,Subscribed ~field-high because this prevents a postgres process from starting when RA start action is executed.
1749283,2019-03-25 09:59:02 UTC,"This is easily reproducible when systemd is not used to manage postgres
lifetime. So, yes, quite easy to reproduce and verify if a fix is valid or
not."
1749283,2019-03-25 11:45:00 UTC,"With the default install it is obviously systemd managed.
There the config defaults to:
 $ grep stats_temp /etc/postgresql/10/main/postgresql.conf
    stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp'
and later the same with version bumped
 $ grep stats_temp /etc/postgresql/11/main/postgresql.conf
    stats_temp_directory = '/var/run/postgresql/11-main.pg_stat_tmp'"
1749283,2018-02-13 20:03:35 UTC,This does not affect trusty as in trusty stats_temp_directory is not configured:
1749283,2018-02-14 13:41:00 UTC,I have created a PPA where I built proposed fixes for this package:
1749283,2018-02-23 16:33:28 UTC,"The Stable Release Update process requires that the bug have a information regarding its impact, a test case and regression potential in the bug description. For this to be considered by the SRU team that information will need to be added."
1749283,2018-02-28 10:29:19 UTC,It looks like this is getting fixed in the resource agents in upstream:
1749283,2019-03-04 13:52:22 UTC,@Mario / @Eric - just to check in whoms curt the ball is right now - Is Mario or someone else in your Org still/again working on this? If not who do we need to bother to re-assign properly?
1749283,2019-03-04 13:55:24 UTC,"FYI - ressource agents took the fix [1].
As mentioned in comment #6 this is what you were waiting for - it might have been lost waiting on this thou - therefore take this opportunity to update responsibilities and please let Dmitrii know if/who is working on it then to resolve that."
1749283,2019-03-22 16:21:08 UTC,"Well that fix got merged a year ago - resource-agents on bionic is at 4.1.0~rc1 - I guess due to some unfortunate timing WRT the bionic freeze, but upstream has 4.1.1 and doesn't it make sense to either pull in the above PR or the 4.1.1 changes (after review?)."
1749283,2018-08-17 05:16:01 UTC,Unsubscribing sponsors for now; Brian is right.
1749283,2019-03-25 08:20:24 UTC,"Yeah Michael,
Making just the commit [1] an SRU where needed would have been my thought as well. But since it is assigned to Mario I wanted to know if he is still (or again) working on this to avoid doing the work twice - also they might as well have ended up with discussions somewhere completely else so getting feedback from him was the obvious next step."
1749290,2018-02-17 12:45:18 UTC,"This was changed in VTE version 0.40 to match xterm and pretty much all other terminal emulators, see also https://bugzilla.gnome.org/show_bug.cgi?id=743258 and https://git.gnome.org/browse/vte/commit/?id=c91ad5640."
1749290,2018-02-19 13:31:34 UTC,Thanks Egmont for the references.
1749290,2020-04-26 05:01:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749291,2018-02-13 21:55:35 UTC,Figured out what was going on. This was due to an issue in Ubuntu's 4.13 kernel where the function key was stuck being repeated once per second. Updating to Ubuntu's 4.15.3 kernel fixed the problem.
1749291,2020-04-09 20:32:00 UTC,"Thanks for the details, I think we can close this bug then."
1749293,2019-04-19 12:38:06 UTC,"Hello, do you still have this issue with the latest HWE kernel (4.15)?
Thanks."
1749293,2019-04-19 12:40:16 UTC,"BTW, if you need to remove the latest kernel, you can boot to the older kernel and remove the latest one with:
  sudo apt-get remove linux-image-$VERSION-generic"
1749293,2019-06-19 04:17:20 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1749296,2018-04-01 14:52:43 UTC,"I'm going to try to work on this.  It will involve a lot of learning for me, so I definitely won't be very quick.  If somebody else might be able to take care of this more quickly, I'm very happy to defer."
1749296,2018-04-01 14:36:38 UTC,"This appears to be happening on master right now too with the concerto data set.  Janet, it's only happening when I look at Subject authorities, not when I look at name authorities.  Is it the same for you?"
1749296,2018-09-06 21:08:19 UTC,"I am unassigning myself, because this turned out to be too advanced for me at this time."
1749302,2018-02-13 23:27:43 UTC,There should also be clarity on how SSH keys are used to make the connection.
1749302,2018-02-14 15:57:13 UTC,"For the juju add-model prompt, I know we don't have much space to work with. There's also a Juju Docs issue where we can expand on manual cloud bits. Pasting here for reference:"
1749302,2018-02-14 15:57:37 UTC,^^ s/add-model/add-cloud
1749302,2019-07-23 06:31:22 UTC,"PR against develop https://github.com/juju/juju/pull/10454 changes the prompt to ""Enter the ssh connection string for controller, username@<hostname or IP> or <hostname or IP>:""."
1749308,2019-03-14 01:09:04 UTC,"Once this is fixed, we might be able to remove device detection in bug #1539322"
1749308,2019-03-18 01:05:21 UTC,"Work-around for still selecting text:
- double-click for a word
- triple-click for a paragraph"
1749308,2020-02-13 01:27:36 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10757"
1749308,2020-07-20 04:53:28 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11075"
1749308,2020-09-21 19:35:20 UTC,"Reviewed:  https://reviews.mahara.org/11075
Committed: https://git.mahara.org/mahara/mahara/commit/4f4ab38ded7b59a2c92816ef8acc67c9a7464334
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1749309,2018-02-16 19:13:18 UTC,Could not perhaps Tor be fixed to follow the advice for developers at the end of
1749310,2018-03-19 10:32:28 UTC,Fix proposed to master: https://review.openstack.org/#/c/554174/
1749310,2018-03-19 10:35:04 UTC,https://review.openstack.org/#/c/554174/
1749316,2018-08-16 15:23:32 UTC,"Hey Sam,"
1749316,2018-08-17 00:03:27 UTC,This is with stable/queens branch of horizon and the manila-ui package.
1749316,2018-10-11 14:49:24 UTC,"Hey Sam,"
1749316,2018-10-11 22:10:58 UTC,"Hi Dustin,"
1749322,2018-02-19 04:52:25 UTC,http://ci.jujucharms.com/job/github-merge-juju/47/console
1749322,2018-02-18 15:38:50 UTC,The link is giving a 404.
1749322,2019-07-09 02:19:56 UTC,I can no longer make this test fail locally under stress. The cause of this intermittent failure must have been fixed as part of other work.
1749341,2018-02-17 01:44:47 UTC,"OK, yesterday i was testing without the NVIDIA drivers installed. Now i have them installed and i did a quick check using the intel drivers and using the NVIDIA propriety drivers (i think i have the nouveau disabled)."
1749341,2018-02-16 15:37:35 UTC,"It's a good thing, you mention that the issue only occurs sporadically, maybe I was just not trying to catch it hard enough."
1749341,2018-02-16 15:10:10 UTC,"Ok, that didn't make any difference.
But....
I have a dual boot system and yesterday windows deleted my linux partition whilst pretending to fix a problem with its own partition. So i had to reinstall Linux Mint 18.3 MATE (same as before), but now i find it a lot harder to reproduce the phenomenon. Now only 1 out of 15 shots is cut up, while before almost all were cut up (tested with the same aerobics class). I haven't reinstalled everything yet, these things take time. But there might have been an incompatibility on my previous installation.
It's kinda late now, i will check more in the following days. I will let you know the results."
1749341,2018-02-14 06:56:24 UTC,Please give more details: Which screenshot mode do you use? Is the video in fullscreen? Which video card is in use?
1749341,2018-02-15 01:35:24 UTC,Thanks for your reply.
1749341,2018-02-14 14:50:14 UTC,"The laptop is ASUS vivobook 5 i5-7200U, 12GB ram."
1749341,2018-02-15 10:52:01 UTC,"I see, thanks for testing! You can find out, if compositing is enabled in Marco by running"
1749341,2018-02-14 15:32:51 UTC,"Hmm, I tried it with the same settings on an Intel video chip (an older one though) and still cannot reproduce the issue. I have the impression that there is a tearing issue on your end and Shutter makes it more visible..."
1749342,2018-03-20 09:42:35 UTC,"Reviewed:  https://review.openstack.org/544155
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=d412de7100058f4a362cf58bd11f88b31b500f77
Submitter: Zuul
Branch:    master"
1749342,2018-08-20 18:31:26 UTC,This issue was fixed in the openstack/zun 1.0.1 release.
1749342,2018-08-18 20:01:15 UTC,"@Eduardo Gonzalez,"
1749342,2018-08-02 06:31:10 UTC,"Reviewed:  https://review.openstack.org/586842
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=7572495c997a6c5f230f0037b1f1ae36053f8f4e
Submitter: Zuul
Branch:    master"
1749342,2018-03-18 03:38:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/554021"
1749342,2018-07-30 15:54:39 UTC,This issue was fixed in the openstack/zun 2.0.0 release.
1749342,2018-07-31 08:04:02 UTC,Zun in kolla uses root user.
1749342,2018-03-28 01:34:32 UTC,"Reviewed:  https://review.openstack.org/554021
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=f7e2c2defce832c155b1f0e542e75e51e63a6699
Submitter: Zuul
Branch:    master"
1749342,2018-03-28 01:34:25 UTC,"Reviewed:  https://review.openstack.org/555978
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=dea6321543c1ad65890436167833cc880acf959e
Submitter: Zuul
Branch:    stable/queens"
1749342,2018-03-24 02:24:58 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/555978"
1749342,2018-03-22 02:59:27 UTC,"Reviewed:  https://review.openstack.org/554551
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=d9098aab26b82a0f78c8c5e72f76da600279e6b9
Submitter: Zuul
Branch:    stable/queens"
1749342,2018-03-20 14:00:03 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554551"
1749342,2018-07-28 20:21:41 UTC,Zun has switched to privsep to execute privileged command
1749342,2018-07-28 20:50:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/586842"
1749347,2018-02-14 03:35:41 UTC,It appears that maybe it's the video file itself that was generated by OBS... I used another video file that I got from youtube and the preview works fine.
1749347,2018-02-14 03:44:29 UTC,"Ok, last thing... I just used OBS's feature to ""remux"" the mkv output container to mp4, and it now works in openshot without issue.  Obviously the ""video"" inside the container is still the same, it's just that OpenShot does not like the mkv container?"
1749350,2018-02-28 11:53:18 UTC,"The original issue was determined to not be caused by this, and the code in question is layered in such a way to make it very difficult to change this behavior. Users who might be affected by this can set the oplog size to their desired size directly in agent.conf with MONGO_OPLOG_SIZE.
Unfortunately, we don't seem to expose this as ControllerConfig, so admins can't set it at bootstrap or controller it from the juju client."
1749361,2018-05-14 19:54:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749365,2019-09-05 00:37:01 UTC,"Code was fix and skip not in tempest at https://github.com/openstack/tempest/blob/be84d6a5e8b57de926d8aaeb96a4fc9a409a3649/tempest/api/volume/test_volumes_extend.py#L33
bug should be marked fixed released
https://github.com/openstack/tempest/search?q=1687044&unscoped_q=1687044"
1749365,2020-03-27 16:12:39 UTC,https://review.opendev.org/#/c/548918/
1749365,2018-02-15 09:05:07 UTC,yea bug https://bugs.launchpad.net/cinder/+bug/1687044 seems fixed on stables branch too. feel free to push  tempest patch to remove the skip decorator.
1749371,2018-02-14 06:35:29 UTC,"Version: Ubuntu MATE 17.10(amd64), with updates up to 2018.02.14"
1749372,2018-03-03 11:42:24 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0rc1 release candidate.
1749374,2019-10-01 22:44:36 UTC,The /bin/sync or /usr/bin/sync command is allowed now. As such I'm marking this as fix released.
1749376,2018-02-21 00:57:04 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1749376,2018-02-21 00:57:16 UTC,"Hello, can you give the output of ls -l /usr/bin/python  ?"
1749378,2018-07-17 14:30:01 UTC,Bug in pycompile according to the dpkg terminal log.
1749384,2018-06-26 12:34:46 UTC,This was made available in Ubuntu Bionic (ethtool 4.15 along kernel 4.15).
1749385,2018-02-14 08:06:15 UTC,From what I can see (though it is hard to see things in the vast log output) it might be a problem with not cleaning up completely.
1749385,2019-10-07 00:47:10 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1749385,2019-10-07 22:44:45 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1749390,2018-02-15 21:38:38 UTC,Triaged.
1749390,2018-02-15 21:41:44 UTC,"We will also need to deal in a gratious manner with migrating people to netplan who upgrade to 18.04, so this also involves a bit of work in postinst scripts. Migration that can be done safely probably should be done at upgrade time, but unsupported configurations (or those we can't make sense of) ought to keep users on ifupdown."
1749393,2020-08-01 05:05:56 UTC,This bug was fixed in the package qemu - 1:5.0-5ubuntu3
1749393,2020-05-01 06:47:12 UTC,Will be merged in 20.10 with qemu >=5.0 where this came upstream.
1749393,2020-03-10 09:07:09 UTC,"Fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=6fd5944980f4"
1749393,2020-01-17 23:52:57 UTC,"Another proposed patch:
https://<email address hidden>/"
1749393,2018-03-16 11:01:46 UTC,"On 16 March 2018 at 10:34, Richard Henderson
<email address hidden> wrote:

> Limit this to 16M; there does not appear to be any special
> support for this in the kernel itself, at least for i686.
>
> Fixes: https://bugs.launchpad.net/bugs/1749393
> Signed-off-by: Richard Henderson <email address hidden>
> ---
>
> Commentary in the launchpad bug suggests 128M gap for x86_64, but that's
> somewhat irrelevant to the given i686 test case.  There's certainly nothing
> in the referenced kernel patch that does any more than we had been doing
> without this patch.
"
1749393,2018-03-22 21:45:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749393,2018-04-04 16:16:10 UTC,qemu patch proposed at http://lists.nongnu.org/archive/html/qemu-devel/2018-03/msg04700.html
1749393,2018-02-14 15:46:36 UTC,"Affected by the same bug.
target architecture arm
host architecture amd64"
1749393,2018-03-01 19:15:15 UTC,This appears to be a problem in all PIE-compiled executables that use sbrk in qemu-user due to the way that position-independent code gets mmapped into adjacent ranges meaning there is no room for expansion. I've hacked my version of QEMU to force the program binary to mmap in a different range allowing for the region to be resized which fixes this issue. I don't know the most appropriate way to determine what range to use in generate though.
1749393,2018-03-15 16:17:57 UTC,"There seem to be two parts to this. Firstly, with a big reserved-region, which is the default for 32-bit-guest-on-64-bit-host, this code in main.c:"
1749393,2018-03-15 17:56:55 UTC,Could we over-allocate the data segment by QEMU_DATA_SIZE/getrlimit(RLIMIT_DATA)/128 MB depending on what's set - similar to how the stack size is managed?
1749394,2018-02-14 08:46:50 UTC,"In Tacker, I have created a VNFD with with autoscaling, template as in [1]."
1749394,2018-02-16 18:44:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545435"
1749394,2018-02-28 09:21:57 UTC,"Reviewed:  https://review.openstack.org/545435
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=c6b758477c3304deb8435b369406ea11e00f71db
Submitter: Zuul
Branch:    master"
1749394,2019-04-24 23:29:29 UTC,I've exactly same issue on kolla-ansible environment.
1749410,2018-02-14 11:26:00 UTC,"To be clear, the resource capacity is for the existing situation. Eg. say I want to have 2 vCPUs in my flavor, I'm asking Placement which Resource Provider is having 2 left vCPUs, ie. ( inventory * allocation_ratio - current allocations)"
1749410,2018-02-14 14:03:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544347"
1749410,2018-02-14 14:08:41 UTC,"Yep, my queries at the beginning were wrong. Thanks for the correction. Uploaded a change adding a few extra words to the ref."
1749410,2018-02-23 10:00:21 UTC,"Change abandoned by Bence Romsics (<email address hidden>) on branch: master
Review: https://review.openstack.org/544347
Reason: I guess this is pointless after Ia2a4f8f80ec68dd9c95e084c292a2fe2d6ec1b2d."
1749410,2020-11-06 08:50:15 UTC,Fixed by https://review.opendev.org/#/c/547065/
1749418,2018-04-25 09:24:03 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1749418,2018-04-20 13:12:41 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1749418,2018-04-13 13:34:11 UTC,"Reviewed:  https://review.openstack.org/559987
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=546236e34516ee061146cebd426a67ea17be2a72
Submitter: Zuul
Branch:    stable/queens"
1749418,2018-04-10 11:05:20 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/559987"
1749418,2018-04-09 18:24:36 UTC,"Reviewed:  https://review.openstack.org/544238
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7ceccee056cb8f50cb5efebd5156cfc56d8e4af7
Submitter: Zuul
Branch:    master"
1749418,2018-02-14 10:35:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/544238"
1749420,2018-02-17 09:10:10 UTC,"Could you please be a bit more specific? I haven't done this before, you see. By 'mainline kernel' do you mean the kernel that you provided in your previous post? And how do I boot with a kernel parameter (from grub maybe?) and where do I find the dmesg afterwards?"
1749420,2018-02-17 09:28:11 UTC,"Okay, I googled the procedures, but in case they're wrong I'm logging them here:"
1749420,2018-02-19 01:34:35 UTC,Thanks for those files. They seem to confirm that the kernel change in comment #16 is the cause of the regression.
1749420,2018-02-20 07:00:09 UTC,This change was made by a bot.
1749420,2018-02-20 15:15:50 UTC,Thank you for your efforts. I honestly hadn't expected this issue to be fixed or even looked at (especially since it seemingly only affects users with this specific laptop model) and I am positively surprised.
1749420,2018-03-01 06:15:20 UTC,It's already in the upstream. We only need to backport it to Artful's kernel.
1749420,2018-03-15 02:26:24 UTC,This bug was fixed in the package linux - 4.15.0-12.13
1749420,2018-03-19 10:57:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1749420,2018-05-22 00:00:38 UTC,This bug was fixed in the package linux - 4.4.0-127.153
1749420,2018-04-03 07:10:35 UTC,Accepting the Bionic verification for Artful.
1749420,2018-04-03 14:10:10 UTC,This bug was fixed in the package linux - 4.13.0-38.43
1749420,2018-04-24 16:02:53 UTC,Kernel fix arrived in Xenial/16.04 via upstream stable v4.4.119.
1749420,2018-04-27 19:11:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1749420,2018-04-27 23:03:22 UTC,"This regression does not affect Xenial, so the fix is redundant."
1749420,2018-04-30 02:14:59 UTC,"The original xenial may not be affected (kernel 4.4), but xenial users do have the option of a HWE kernel, which would be affected..."
1749420,2018-05-01 12:13:56 UTC,"Oh, of course, you are right, Mr. Van Vugt."
1749420,2018-07-02 08:31:58 UTC,This bug was fixed in the package linux-hwe - 4.15.0-24.26~16.04.1
1749420,2018-03-23 19:06:38 UTC,"In *Bionic*, the kernel in proposed (4.15.0-13.14) and in release (4.15.0-12.13) both fix this regression."
1749420,2018-02-17 06:54:50 UTC,Thanks for your testing.
1749420,2018-02-16 16:09:01 UTC,"Congratulations Mr. Feng, the kernel you provided fixes the issue completely! Colours now display as fine as on my Ubuntu 16.04 install. That is just great."
1749420,2018-02-16 12:22:01 UTC,"The colour artefacts seems to have been introduced in 4.8-RC2. 4.8-RC1 is **not** affected.
In case it's relevant: I downloaded and installed the kernels with UKUU as before (which uses kernels from Ubuntu mainline repo)."
1749420,2018-02-16 15:37:34 UTC,"Please try this kernel,
http://people.canonical.com/~khfeng/lp1749420/"
1749420,2018-02-14 19:44:10 UTC,"Can you see if this bug still happens with the latest bionic kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/14347009"
1749420,2018-02-14 20:04:04 UTC,I just installed the 4.15.0-10 kernel that you provided and rebooted. The colours didn't improve; the same artefacts and banding still appear like they did on kernel 4.13.
1749420,2018-02-15 02:32:00 UTC,Another possibility is that LCD panel dithering (controlled by the i915 kernel driver) has changed between kernel versions.
1749420,2018-02-15 04:06:34 UTC,"Oh, it's UX303LA to be exact :)"
1749420,2018-02-15 04:16:49 UTC,"Yes, based on what I can find, the Haswell UX303LA has about 61% sRGB coverage so it sounds likely to be a 6-bit (AKA 18-bit) panel, which makes it sound even more likely that comment #5 is the cause of the problem."
1749420,2018-02-15 05:23:10 UTC,"Judging by the dates, this change might be related:"
1749420,2018-02-15 07:00:07 UTC,This change was made by a bot.
1749420,2018-02-15 07:03:38 UTC,Wait a minute... it sounds like dithering is always going to be disabled (since commit 611032bfa71a7) for the case of (pipe_config->pipe_bpp == 6*3).
1749420,2018-02-14 11:00:07 UTC,This change was made by a bot.
1749420,2018-02-15 07:20:31 UTC,Or maybe pipe_bpp is some other weird value...
1749420,2018-02-15 11:03:22 UTC,"If it's any help, this problem seems to have been introduced in kernel 4.8. I tested different kernels with UKUU. Kernels prior to 4.8 do not have the colour banding issue."
1749420,2018-02-16 02:06:52 UTC,Excellent! That was my next question - for you to narrow it down further. Thanks.
1749420,2018-02-16 02:39:15 UTC,"Attached is the difference between kernel 4.7 and 4.8 in the Intel graphics driver. It's still a big diff, but at least eliminates my above theories about the cause of the regression. Now the main suspect, I think, would be:"
1749420,2018-02-16 02:44:16 UTC,I guess we can answer that question by seeing the EDID for the LCD panel.
1749420,2018-02-16 02:49:32 UTC,Scrap that. Try this instead:
1749420,2018-02-16 03:15:16 UTC,Please also try:
1749420,2018-02-16 06:38:39 UTC,I guess we can also bisect to the exact bad commit and report it to i915 developers.
1749420,2018-02-15 07:06:19 UTC,"if (intel_dp->compliance.test_data.bpc != 0)
  this seems like a simple bug per above;
else
  it's some other problem;"
1749420,2018-02-16 11:01:03 UTC,"It probably doesn't matter, but in case it does: the outputs were produced on 18.04 under Xorg and kernel 4.13."
1749425,2018-02-14 23:09:58 UTC,I've unsubscribed Canonical Field Critical as removing the 4095 tagged ports in OVS on all 3 Neutron Gateway nodes seems to have made the packet loss go away (for now?).
1749425,2018-02-14 23:32:00 UTC,You described a lot of issues in comment #14:
1749425,2018-02-23 22:45:55 UTC,"Hi folks, while trying to reproduce this behaviour myself I think i've stumbled upon some interesting behaviour. I setup a test as follows and checked for errors at specific points. I have a 4 node setup (24 core/64G ram) with 3 gateways and 1 compute. Neutron is configured with l3_ha enabled and max_agents_per_router set to 3;"
1749425,2018-02-16 07:45:21 UTC,Hi Brian
1749425,2018-02-16 17:23:38 UTC,"I've spent the last two days trying to reproduce these problems on an OpenStack Cloud with three gateway/network units, each with 8 cores and 16G of RAM;  I have 99 routers configured on the cloud, plumbed into a shared external provider network, and I've been switching them between ha and non-ha configuration continually for the last 24 hours using:"
1749425,2018-02-15 19:25:33 UTC,"And just as a follow-on to my previous comment - is it possible to test this with the latest code from the master branch?  I know you're running packages from Ubuntu I just didn't want to waste cycles tracking things down that might be fixed already, and maybe just need a backport to a stable branch.  That's not saying there isn't a new bug here as there most likely is."
1749425,2018-02-14 21:01:42 UTC,"@james-page, @axino -"
1749425,2018-02-14 21:03:10 UTC,Correction - The `remove_vip_by_ip_address` call failing just after the IPTablesManager is called and succeeds.
1749425,2018-02-14 17:49:17 UTC,You can see an update message prior to the remove-from-agent processing with:
1749425,2018-02-14 18:19:14 UTC,"OK so the original bug report was actually about packet loss in ovs; the network nodes have a large number of lost tap devices tagged with 4095 segmentation id, reporting no such device in OVS."
1749425,2018-02-14 12:11:47 UTC,I've subscribed Canonical Field Critical
1749425,2018-02-14 12:50:18 UTC,Would it be possible to get log files from /var/log/neutron and /var/log/openvswitch as well as the syslog and auth.log files from an impacted machine. I suspect that due to the large number of namespaces being managed something is just taking to long to parse/sync/refresh causing this issue.
1749425,2018-02-14 13:56:03 UTC,"We're going to provide the logs, but neutron-l3-agent is getting spammed with https://pastebin.canonical.com/p/PBPpJJkRgy/ for dozens of routers."
1749425,2018-02-14 17:33:23 UTC,Some sequencing:
1749425,2018-02-14 17:13:30 UTC,@axino
1749425,2018-02-14 17:39:11 UTC,OK and now:
1749425,2018-02-14 17:42:45 UTC,Supposition might be that ha_vr_id has been unset at this point in time?
1749425,2018-02-14 13:58:43 UTC,This is happening on all 3 neutron-l3-agents.
1749427,2018-02-14 11:30:14 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1749427,2018-03-22 10:28:43 UTC,"Issue can be found on ThunderX as well, there was a similar bug for it (bug 1751718), but it's for Bionic (Bionic works fine)"
1749427,2020-07-24 20:56:31 UTC,"Marking this as invalid, referenced bugs are all closed and pretty sure this is not a problem on arm64 any longer."
1749427,2019-03-05 11:04:48 UTC,"After changing the guest image to match the host (e.g. bionic on bionic), this seems to be working now."
1749429,2018-02-20 10:23:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/546106"
1749429,2018-03-18 16:55:35 UTC,"Reviewed:  https://review.openstack.org/546106
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=fc825d4586964d178f09802feb1c92fb09b4b586
Submitter: Zuul
Branch:    master"
1749429,2018-03-19 14:35:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/554241"
1749429,2018-03-20 10:05:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/554489"
1749429,2018-03-20 15:31:10 UTC,"Reviewed:  https://review.openstack.org/554489
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=6605dd26bc22458924f9bf58bc5ebf475c99ca80
Submitter: Zuul
Branch:    master"
1749429,2018-04-11 10:45:43 UTC,"Reviewed:  https://review.openstack.org/518670
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=439e528addd2ee481e8039cec4ba5892725b7ff6
Submitter: Zuul
Branch:    master"
1749429,2018-04-15 20:50:56 UTC,"Reviewed:  https://review.openstack.org/554241
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=7be2d258e2de97becccfc6804b323a28c274830f
Submitter: Zuul
Branch:    master"
1749431,2019-06-17 04:17:17 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1749431,2019-04-17 05:49:03 UTC,"Hello,"
1749440,2020-07-01 21:09:22 UTC,"thank you for your bug report, it does sound rather an issue with gnome gmail though"
1749440,2018-02-15 17:09:27 UTC,"Confirmed. The main gnome-gmail application is unable to launch (English). This does not happen with other launchers (file browser, LibreOffice, ...)."
1749443,2019-01-06 10:24:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749449,2018-02-15 23:37:16 UTC,Attempted to update from the command line and got this:
1749449,2018-03-26 15:32:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749449,2020-05-28 14:18:30 UTC,I believe this was a bug in apt/dpkg
1749450,2018-02-14 13:07:54 UTC,"Proposed patch:
https://review.openstack.org/#/c/539245/"
1749450,2019-06-18 01:33:13 UTC,"Reviewed:  https://review.opendev.org/664928
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=718a7b176f5b903619723432c92d140e9c2844ac
Submitter: Zuul
Branch:    stable/rocky"
1749450,2019-06-21 13:46:28 UTC,This issue was fixed in the openstack/tripleo-common 9.6.0 release.
1749450,2019-08-16 18:03:33 UTC,"Reviewed:  https://review.opendev.org/664929
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=587da83e57eecb14a36f54db9a8f488977a7a044
Submitter: Zuul
Branch:    stable/queens"
1749450,2019-09-13 15:06:41 UTC,This issue was fixed in the openstack/tripleo-common 8.7.1 release.
1749457,2019-09-23 17:05:09 UTC,"DnD will not be intuitive here (no one can guess it exists, or the way it will work)"
1749457,2019-09-17 00:31:13 UTC,"If you want to keep the implementation simpler (vs having to deal with drag & drop and such in a listview widget), a way to do it could be to have a ""Move transaction up"" and ""Move transaction down"" menu entries in the Transaction menu, and optionally a pair of toolbar buttons with up/down arrows for this purpose, maybe only showing those buttons when having selected a transaction that has other transactions on the same day. But already, even if it's just the menu entry, it would be a really good start."
1749457,2019-08-11 10:53:39 UTC,"(UX) Suggestion: If they are not the same-day and the user tries to drag- and drop across a day, then you can just adjust the date manually. This would allow a user to quickly ""correct"" incorrect dates."
1749457,2019-02-26 10:27:08 UTC,"Not only it looks ugly, but it's very important to have this function because it's a mess to check many transactions if they are not in the same order, as displayed by the bank's website for example, having the budget not go below zero is very important to actually check and compare before reconciliation. This might be implemented via drag & drop, and also via up/down arrows, so bug #1814452 can be fixed in the same way."
1749457,2018-03-29 04:03:58 UTC,I agree.  Most of the imports that are consumed by HB already have either timestamps that declare order or a financial transaction ID or 'FITID'.
1749457,2018-12-04 07:10:02 UTC,This would also help when you are working with imports and would like to find one missing transaction by opening two account history and comparing side by side.
1749457,2018-09-27 09:46:45 UTC,I agree with Jake's comment #2. It looks ugly when you see negative balances during the day (when you forgot to input credit transactions first). That is why i made same request to allow re-order the day's transactions by adding a time to  transactions or by numbering them or moving them up/down to adjust to the correct order.
1749457,2018-02-21 20:43:56 UTC,"Yeah exactly. As said, it just looks ugly when you have e.g. a negative (red!) number in your log there, while you actually never had that account balance in real life."
1749457,2018-02-19 22:50:56 UTC,"from a bank point of view, the bank balance will be the same no matter the order the txn are within a same day. The running balance will of course an reading it you might miss the changes order."
1749457,2018-12-23 15:14:40 UTC,You can add an option to let the user decide if have the balance shown in every transactions or only when the date of transaction is <> from the previous.
1749474,2018-02-15 03:58:12 UTC,"Adding this into the netlist opens a can of worms in that any change could break existing code.
Add it as a new file and nothing breaks because no one is currently reading that file."
1749474,2018-02-15 00:34:36 UTC,Another wishlist bug that might be related: https://bugs.launchpad.net/kicad/+bug/983230
1749474,2018-02-14 20:53:21 UTC,"I wonder how much could be done with python scripts in the board editor side. Doing things ""dynamically"" or ""on-the-fly"" (event based while editing) isn't possible ATM, but some checks and changes could be done."
1749474,2018-02-14 19:36:07 UTC,This is the original discussion (I think): https://forum.kicad.info/t/automating-engineering-requirement-notes/9457
1749474,2018-02-14 16:27:07 UTC,This might be a similar underlying request to https://bugs.launchpad.net/kicad/+bug/1571930 but with a different suggested solution.
1749474,2018-02-14 16:03:19 UTC,Netlist says the U34 pin 16 and C56 pin 1  both connect to VDD.
1749474,2018-02-14 14:55:56 UTC,"Would you give some examples? The simplest one I can think of are track impedance constraints or differential pair definitions. I have frequently seen simple text messages saying e.g. ""place C1 next to IC5"", but they are just notes for the layout designer, not the layout application. I am curious about your ideas."
1749474,2018-02-14 19:42:48 UTC,Technically there is nothing preventing kicad from passing this information from the schematic editor to the board editor using the netlist.  There has already been a discussion about passing predefined netclass information so this information you presented here is parametric in nature.  Of course passing this information is the trivial part.  Updating the board editor to handle this parametric information is far more involved.
1749475,2020-01-03 22:15:14 UTC,I've pushed a new rebase:
1749475,2020-01-29 21:36:10 UTC,I've been testing this enhancement on a sandbox kindly set up by Blake Henderson. I've run into problems when adding an additional entry to Trigger Event Definition Group Member Configuration. I'm unable to cleanly switch between different print formats. Here's what I did:
1749475,2020-01-29 21:37:27 UTC,"Here's a screenshot of the preview of the ""Brief"" format with the stock groups defined."
1749475,2020-01-29 21:38:48 UTC,"Here's a preview of the ""Super Brief"" format which was added to the group configuration."
1749475,2020-01-29 21:40:19 UTC,"This screenshot shows the ""Brief"" format chosen, but ""Super Brief"" is actually displayed, even after the Update button is clicked."
1749475,2020-01-29 21:41:10 UTC,"This screenshot shows the ""Full"" format chosen, but ""Super Brief"" is actually displayed, even after the Update button is clicked."
1749475,2020-02-07 21:00:13 UTC,Original Project:
1749475,2020-02-19 16:43:23 UTC,My preference would be to move forward with accepting the patron facing enhancements and addressing the issues with the new interfaces separately.
1749475,2020-04-09 19:30:30 UTC,"Galen, have you had a chance to revisit this? It would be great if we could get it resolved in time to get into 3.5. If not, and understanding that time is always valuable and pretty weird right now, would it be feasible for you to split your fixes to the original work from the new components that you built so we could get the original work signed off on?"
1749475,2020-08-21 21:28:10 UTC,I've done some additional testing on the latest branch of this development on the Feedback Fest test server.
1749475,2020-08-25 13:42:41 UTC,My signoff branch is at:
1749475,2020-08-25 14:38:23 UTC,"Thanks for testing Michele, and for pointing out about the upgrade issue. After discussing, Mike will work on a change that should preserve customizations and follow what was called for in the spec anyway:"
1749475,2020-08-25 19:47:59 UTC,"Hi folks,"
1749475,2020-09-13 03:35:14 UTC,"I tested Mike's upgrade script and it works as described, preserving any customizations that have been made to the action trigger definitions. This branch fixes a syntax error in the upgrade script and adds my signoff:"
1749475,2020-09-14 13:48:42 UTC,"Pushed to master for inclusion in 3.6. Thanks, Mike, Dan, and Michele!"
1749475,2019-12-04 16:17:48 UTC,"I'm adding a link to related bug 1854986, which may have been a factor in testing this code."
1749475,2020-02-11 18:52:41 UTC,"Question: Is it worth splitting up this work to the portion that was originally requested (which looks to be working well now, but would like to test again if it gets split apart) and the new interfaces  that we can get the first part accepted sooner?"
1749475,2019-12-04 16:04:15 UTC,"Lugene, the information that's printed is configurable in the template for the Action Trigger that generates the printout. The Action Trigger is called ""biblio.record_entry.print"". You may want to ask your system administrator about changing it. Library staff members may use this as well, however, and may find the Bib ID to be useful information."
1749475,2019-02-25 17:57:46 UTC,"Thanks for the quick feedback, Mike.  I get where you are coming from, and I see the utility, it just feels like something still isn't sitting quite right for me as it stands.  I'm sorry to be a pain!  Hopefully we can at least talk through it a little more and see if some improvements can be found."
1749475,2019-02-27 19:32:43 UTC,"If I get another free moment, I'll again try to test and post my DB-less option, not as something I am pushing for, but as more discussion fodder."
1749475,2019-09-19 14:10:19 UTC,"SPARK recently upgraded to 3.3 and started using baskets in the OPAC. One of the things we've noticed is, when printing a basket list, the Bib ID number prints with the item. This isn't helpful information for the patron. We'd like to see it left out or replaced with something the patron can relate to, perhaps the barcode."
1749475,2019-01-09 21:21:28 UTC,"Wonderful! Thanks, Mike!"
1749475,2019-01-11 17:57:13 UTC,"Hi Mike,"
1749475,2019-01-11 18:59:18 UTC,"Those basket menu entries are not related to this work, so I would recommend a new bug for them."
1749475,2019-01-23 18:49:20 UTC,"I've pushed two updates to the branch, one to propagate sorting from bucket and basket interfaces, and another to allow sort direction selection (and propagation).  The second commit also contains a fix for the log messages reported by Terran."
1749475,2019-02-06 23:08:12 UTC,"We're getting inconsistent testing results. The good news is, we're no longer seeing the errors in the server logs."
1749475,2019-02-20 13:50:48 UTC,"I did some testing on this recently and when I got an ISE I did get this in the logs:
Error processing Trigger template: undef error - Can't call method ""textContent"" on an undefined value at /usr/local/share/perl/5.18.2/OpenILS/Application/Trigger/Reactor.pm line 452.
That line is trying to pull a pubdate to sort by and 3 of them were indeed missing 008s. They undoubtedly poor records, but these things hide everywhere and throwing an ISE at users is pretty ugly."
1749475,2019-02-20 14:02:50 UTC,Re 008's: Having an 008 whose date1 is only fill characters also causes an ISE.
1749475,2019-02-20 14:07:28 UTC,"The branch needs a rebase on master, I get conflicts in the following files:"
1749475,2019-01-09 21:00:59 UTC,Here is a branch implementing this functionality.  From the commit message:
1749475,2019-02-20 19:41:47 UTC,"So, the rebase branch in comment #10 is broken. Don't use it."
1749475,2019-02-22 14:46:39 UTC,"Okay, I spent a large part of yesterday going over (and over) this code, and I would say it is 90% straightforward and good, with 10% curve ball which I am struggling to make sense of."
1749475,2019-02-22 23:08:32 UTC,"A first pass at removing the Event Def Groups code resulted in 13 insertions, 187 deletions.  I know that is proof of exactly nothing, but there were also no obvious hangups by moving in that direction.  Will do more testing on Monday and post the branch if things pan out."
1749475,2019-02-25 15:34:14 UTC,"Thanks for looking at the branch, Dan."
1749475,2019-02-25 19:44:18 UTC,"Thanks, Dan."
1749475,2019-02-27 15:47:40 UTC,"Thanks, Mike.  It helps to know which pieces are fundamental."
1749475,2019-02-27 16:42:19 UTC,"To be a bit more precise about ""Why Groups"", MassLNC in their initial requirements for this project specified the ability to choose among multiple output formats."
1749475,2019-02-20 14:47:09 UTC,"Also, on the Record Email preview page, once you click Email Now you're taken to a results page that explains that your email has been queued for delivery. Something happens to the CSS urls on this page so the page is largely un-stlyed. The ?v= part of the cache-buster is missing, so the browser is looking for style.css001, etc."
1749475,2019-02-27 19:31:32 UTC,I realized I should probably get at least most of my current code out there to also help the conversation:
1749477,2018-02-14 14:58:28 UTC,"[shardy@tripleodev2 openshift_openstack]$ ssh -F /home/shardy/.quickstart-shiftstack/ssh.config.ansible undercloud
Warning: Permanently added 'tripleodev2.localdomain,192.168.1.91' (ECDSA) to the list of known hosts.
Warning: Permanently added 'undercloud' (ECDSA) to the list of known hosts.
Last login: Wed Feb 14 14:57:38 2018 from gateway
[stack@undercloud ~]$ sudo su -
Last login: Wed Feb 14 14:42:32 UTC 2018 on pts/0
Last failed login: Wed Feb 14 14:57:51 UTC 2018 from gateway on ssh:notty
There were 352 failed login attempts since the last successful login.
[root@undercloud ~]#"
1749481,2018-02-27 15:42:48 UTC,"I tested again this AM beginning with a fresh install of 20180227, applying updates, and then installing gnome-panel. During installation I chose to auto-login so after initially logging out and selecting flashback w/metacity I still booted the default DE."
1749481,2018-02-27 16:23:08 UTC,This may or may not be worth mentioning but the reason I totally purged lightdm was just using dpkg to change to gdm3 returns an error:
1749481,2018-03-01 14:58:41 UTC,*** Bug 793948 has been marked as a duplicate of this bug. ***
1749481,2019-07-15 01:47:22 UTC,"Yes the upstream bug link (I just fixed up) is showing it was fixed in gdm3 version 3.27.91, so before 18.04 was released."
1749481,2018-04-11 21:02:34 UTC,Seems to be fixed in Ubuntu 18.04.
1749481,2019-07-14 22:22:18 UTC,Is this issue still happening? I think it was fixed in 18.04.
1749481,2018-03-04 15:38:34 UTC,It looks like it is now even more broken. Selecting GNOME session sometimes log me into the Ubuntu session instead. Weird.
1749481,2018-02-27 11:22:18 UTC,That's weird. Still the same issue on my Ubuntu 18.04 system when using gdm 3.27.90.
1749481,2018-02-27 00:20:59 UTC,Upstream thinks is fixed in gdm3 3.27.90 which we have in Ubuntu 18.04 now. Can you confirm?
1749481,2018-02-26 15:46:56 UTC,*** Bug 793456 has been marked as a duplicate of this bug. ***
1749481,2018-02-21 17:13:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749481,2018-02-21 13:00:57 UTC,Adding a gnome-session task just in case that could be part of the problem.
1749481,2018-02-19 18:18:36 UTC,"Attachment 368580 pushed as f4f7b69 - Revert ""session: don't call gdm_session_defaults_changed from setup"""
1749481,2018-02-19 18:17:24 UTC,This reverts commit 572a19324b75cc1f1b2db4908e2d7c9f06e4e335.
1749481,2018-02-14 19:03:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749481,2018-02-14 15:42:46 UTC,Bug reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=793456
1749481,2018-02-27 01:12:45 UTC,Works properly to boot both the flashback w/metacity and GNOME Classic sessions now.
1749481,2018-02-19 18:17:31 UTC,"Created attachment 368580
Revert ""session: don't call gdm_session_defaults_changed from setup"""
1749484,2018-02-14 15:31:42 UTC,This is not specific to libreoffice. The gnome-calculator snap exhibits the same issue:
1749484,2018-02-14 16:10:23 UTC,"After logging into to wayland and then back into X11, a wayland socket is lingering:"
1749484,2018-02-14 19:06:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749484,2018-02-14 21:30:46 UTC,"I have reproduced this issue on 17.10.  After logging out of a wayland session, the socket is left behind."
1749484,2019-08-01 13:59:51 UTC,Same for 18.04
1749535,2018-02-14 16:08:02 UTC,"I installed Elementary about 30 minutes ago, and I've run update and upgrade."
1749538,2019-10-09 10:22:53 UTC,Thanks for reporting this Kyle.
1749538,2019-10-14 13:21:12 UTC,I just fixed this as I was pushing a few other changes to the core docs.
1749558,2018-02-14 17:26:14 UTC,"StacktraceTop:
 fritzbox_get_ip (profile=0x0) at firmware-common.c:882
 app_copy_ip () at application.c:83
 g_closure_invoke (closure=0x55e9b5964e60, return_value=0x0, n_param_values=2, param_values=0x7fffec693c20, invocation_hint=0x7fffec693ba0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55e9b59b20a0, detail=detail@entry=0, instance=instance@entry=0x55e9b5bdeca0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffec693c20) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x55e9b5bdeca0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffec693df0) at ../../../../gobject/gsignal.c:3391"
1749560,2018-02-14 17:52:39 UTC,The Nova clean-up fixes are here.
1749560,2018-02-26 07:25:36 UTC,"> I think this has to be mitigated in Nova but also Heat should probably report the first failure if there are subsequent failures in the retry mechanism, even if ""BadRequest"" was the failure.
"
1749562,2018-02-14 19:10:11 UTC,"seems upstream already fixed
https://git.gnome.org/browse/network-manager-openvpn/commit/?id=d90cf9105e33fd4f646adf4f1ef8b9f95afc737b"
1749562,2018-06-19 06:05:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749562,2019-04-19 10:21:42 UTC,"http://www.pivpn.io/ is using tls-crypt by default, so ubuntu is not even capable connecting to this popular and easy to setup vpn solution."
1749562,2019-04-23 15:08:06 UTC,The commit referenced in the previous comment is included in https://launchpad.net/ubuntu/+source/network-manager-openvpn/1.2.10-0ubuntu1 which was updated before 18.04 so that's not likely the fix/problem here
1749562,2020-01-09 16:15:45 UTC,I'm not a programmer but I'll be happy to do whatever I can to facilitate getting this resolved.
1749573,2018-02-19 12:22:36 UTC,thanks.
1749573,2018-02-19 11:59:22 UTC,"Hi Andreas,"
1749573,2018-02-17 15:44:18 UTC,Hi Roger…
1749573,2018-02-17 15:34:33 UTC,Already logged as bug 1749690
1749573,2018-02-15 09:24:21 UTC,"file, download ""hplip-3.17.11-plugin.run"" and it works…"
1749573,2018-02-14 22:39:00 UTC,I had the same issue once I got the update notification and decided to update Hplip.
1749573,2018-02-14 19:14:18 UTC,hand-debug
1749573,2018-02-14 19:10:23 UTC,"> hp-plugin -ui -ldebug
"
1749574,2018-08-06 16:49:20 UTC,This issue was fixed in the openstack/solum 5.7.0 release.
1749574,2018-07-26 13:36:10 UTC,This issue was fixed in the openstack/trove 10.0.0.0b3 development milestone.
1749574,2018-07-02 17:17:38 UTC,"pycrypto was removed from most / the main openstack projects, there are still a few outliers, but nothing core."
1749574,2018-06-15 01:01:57 UTC,Trove has removed pycrypto completely. :)
1749574,2018-06-14 14:27:19 UTC,"Reviewed:  https://review.openstack.org/573070
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=4279fd253baf77fef8a5a8e6374f79e988d01d4b
Submitter: Zuul
Branch:    master"
1749574,2018-06-13 06:05:27 UTC,"Reviewed:  https://review.openstack.org/560292
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=46a031e76544572562eaf3e757a0ff488c3389f2
Submitter: Zuul
Branch:    master"
1749574,2018-05-17 09:48:31 UTC,https://review.openstack.org/569073
1749574,2018-06-11 12:59:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/574244"
1749574,2018-06-03 22:39:29 UTC,"Change abandoned by Ade Lee (<email address hidden>) on branch: master
Review: https://review.openstack.org/544873
Reason: The changes in this patch have been subsumed in https://review.openstack.org/568879 and https://review.openstack.org/#/c/564839/"
1749574,2018-04-11 07:17:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/560292"
1749574,2018-02-21 10:53:40 UTC,"Change abandoned by Ameed Ashour (<email address hidden>) on branch: master
Review: https://review.openstack.org/544891"
1749574,2018-02-15 12:21:06 UTC,"Fix proposed on master
https://review.openstack.org/#/c/544891/"
1749574,2018-02-15 12:08:01 UTC,"Fix proposed for Barbican
https://review.openstack.org/#/c/544873/"
1749574,2018-02-14 19:13:27 UTC,http://codesearch.openstack.org/?q=pycrypto&i=nope&files=.*requirements.*&repos= for a current list of projects consuming pycrypto
1749574,2018-06-13 05:46:57 UTC,"Reviewed:  https://review.openstack.org/574244
Committed: https://git.openstack.org/cgit/openstack/solum/commit/?id=4bb3f91e8afc1e60f674d3e191a5945dfe909bd2
Submitter: Zuul
Branch:    master"
1749590,2020-04-27 10:59:27 UTC,"I confirm this also in Ubuntu 20.04, with LO 6.4.3.2, installed by Ubuntu Software 3.36.1"
1749590,2019-01-23 12:42:42 UTC,I can confirm this for LO 6.1 on Ubuntu 18.04 Bionic Beaver.
1749590,2018-02-26 11:53:28 UTC,"i dont know if it helps, but if i recall correctly in unity was a similar bug and it was resolved.
Now in unity you see the secuence for any app of libreoffice
1.- Click in application
2.- In the dock, opens the white icon
3.- When app start, the dock show the correct icon."
1749590,2018-02-15 10:59:51 UTC,I can reliably observe the issue on bionic too.
1749590,2019-03-27 00:31:32 UTC,"I just want to add, in kubuntu plasma the problem does not exist. Each libreoffice application (writer, impress, calc, draw) is associated with its icon in the panel."
1749597,2018-02-22 16:51:26 UTC,"For my own understanding, I'm curious:"
1749625,2018-02-21 06:50:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749625,2019-01-19 03:26:53 UTC,I confirm this happens to me too on Ubuntu 18.04.1 LTS.
1749625,2019-04-03 09:54:00 UTC,"This is still happening on Ubuntu 18.04.2 LTS
if anyone working on this needs more info please ask."
1749625,2019-04-03 15:19:05 UTC,"still happening i tried passing options in the command line but none seem to do anything. changed  cameras did not help either , looks like a software bug  i am running ubuntu nothing i do seems to have any effect on the errors i am getting, best that we wait for the developers to update and uplaod a new code."
1749630,2018-09-11 13:28:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749635,2019-05-28 20:24:19 UTC,There is already a feature file for Resume that includes a scenario for Cover letter functionality.
1749645,2018-02-19 14:49:24 UTC,AFAICT there aren't plans to change mistral client based on brief conversation I had in IRC with one of the mistral client cores.
1749645,2018-02-19 12:43:08 UTC,"ok, let's keep this one closed and continue in the new bug 1750311"
1749645,2018-02-19 10:22:04 UTC,"apevec, looks like it's a new bug(in queens, master is not facing it) https://bugs.launchpad.net/tripleo/+bug/1750311"
1749645,2018-02-19 09:48:31 UTC,"openstack-heat-api-10.0.0-0.20180218090758.3b894d2 was used in latest promotion attempt[1] and it still failed OC deploy[2]
2018-02-19 02:49:26 | 2018-02-19 02:49:18Z [overcloud.AllNodesDeploySteps.WorkflowTasks_Step2_Execution]: CREATE_FAILED resources.WorkflowTasks_Step2_Execution: ERROR"
1749645,2018-02-18 09:04:00 UTC,"Reviewed:  https://review.openstack.org/545371
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=7ec0a70b2001962d616ba3cdddb7dc8f6466696b
Submitter: Zuul
Branch:    stable/queens"
1749645,2018-04-19 19:24:32 UTC,This issue was fixed in the openstack/heat 11.0.0.0b1 development milestone.
1749645,2018-02-16 16:11:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/545371"
1749645,2018-02-16 18:00:22 UTC,"Reviewed:  https://review.openstack.org/545247
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=fd3b5a5d8601d48cf963f4d4b5eb7630a8ec878f
Submitter: Zuul
Branch:    master"
1749645,2018-02-15 18:37:36 UTC,Note: error in ... resource_type: OS::Mistral::ExternalResource
1749645,2018-02-15 20:24:13 UTC,"- During a deployment Heat tried to start a mistral workflow to install ceph [2018-02-15 02:59:16.223 30322] [1]
- /usr/lib/python2.7/site-packages/mistral/api/controllers/v2/workflow.py:88 fetched the workflow [2018-02-15 02:59:17.078 30322]
- /usr/lib/python2.7/site-packages/wsme/api.py:222, as called by Mistral, could not decode the JSON that it received from Heat [2018-02-15 02:59:17.097 30322]"
1749645,2018-02-23 14:01:58 UTC,This issue was fixed in the openstack/heat 10.0.0.0rc2 release candidate.
1749645,2018-02-16 09:36:44 UTC,https://review.openstack.org/545247 should work around the issue in Heat. This was introduced by https://review.openstack.org/#/c/488531/
1749645,2018-02-16 15:35:28 UTC,"Also added python-mistralclient as affected, since https://review.openstack.org/#/c/488531/ will likely break many consumers of its API."
1749645,2018-02-16 09:36:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545247"
1749650,2018-02-19 02:08:32 UTC,"Still happens with 0.92.x, master and LPERefactor branch (0.92+devel (e0c26b8, 2018-02-14))"
1749650,2019-12-11 05:10:11 UTC,Still happens in 1.0beta2.  Migrated to:  https://gitlab.com/inkscape/inbox/issues/1357
1749653,2019-09-16 08:45:49 UTC,Migrated to https://github.com/widelands/widelands/issues/3258
1749653,2018-03-14 07:02:50 UTC,I have attached some test results.
1749653,2018-02-20 12:38:02 UTC,I have linked a new branch https://code.launchpad.net/~widelands-dev/widelands/ware_routing_fps that we can use to measure which threshold we should have.
1749653,2018-02-20 12:33:27 UTC,"We have discussed om the forum, that we will skip some ware routing calculations when an economy has more than X flags."
1749653,2018-02-17 17:22:37 UTC,"I messed up above: forgot that there are think() routines in many places, not just in AI. Should not write to LP when there is not time to think() self first."
1749653,2018-02-17 16:16:43 UTC,https://code.launchpad.net/~widelands-dev/widelands/ware_routing_speedup makes a big difference with a release build on my system
1749653,2018-02-17 16:09:22 UTC,"I made some attempt to run this over callgrind. The result was that about 60% of the time was in think(), about 30% in replaywriter and the rest was not clear story. The replaywriter was a bit of a surprise, since the game barely progressed."
1749653,2018-02-17 13:55:53 UTC,Thanks for your reply and sorry if I sounded too demanding. And also thanks for that hint with the road layout. I will try to modify that ...
1749653,2018-02-17 12:51:39 UTC,"Unless we want to call somebody's attention to a bug, we usually don't assign anybody, because everybody is a volunteer. It's up to the volunteers to snap up the bugs that they want to fix. We use milestones to make sure that nothing important gets forgotten."
1749653,2018-02-17 11:01:06 UTC,"Do you guys think the ""being slow"" problem with my game is a bug or just a problem of the performance of my machine?"
1749653,2018-02-16 19:31:21 UTC,Eiskriege is a really big map. Some time ago Tibor has made a branch which speeds up ware routing. This is this branch https://code.launchpad.net/~widelands-dev/widelands/ware_routing_speedup
1749653,2018-02-16 19:07:24 UTC,Thanks for testing! I'll unassign you then.
1749653,2018-02-16 18:23:25 UTC,@GunChleoc:
1749653,2018-02-15 11:11:18 UTC,"I'm now having a problem with the attached savegame, which I used to be able to load without problems."
1749653,2018-02-15 07:44:41 UTC,Here's the slow savegame
1749653,2018-02-17 15:54:43 UTC,"Don't worry, you weren't too demanding. Your tone is polite enough and you had a legitimate question :)"
1749653,2018-02-17 08:48:53 UTC,"Seems like my system was exceptionally slow, I can now load Ice Wars again and also the attached savegames. The second one is indeed slower than the first one. I'll try the ware routing speedup branch to see if it makes a difference - it will be immediately apparent on my old machine :)"
1749656,2019-06-07 20:20:32 UTC,I don't think we even have this job anymore. Feel free to reopen if still a problem.
1749657,2019-11-28 08:45:59 UTC,Thank you for your bug report. Reassigning to the kernel since it's probably a video driver issue. You might have better chance on improved support for modern hardware on 18.04 rather than 16.04 though
1749657,2019-11-28 07:13:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749664,2018-03-20 03:39:09 UTC,Patches[1][2] merged sometime back should fix this issue.
1749666,2018-02-15 09:53:14 UTC,Our fix for queens is just use keystone queens source code.
1749666,2018-02-15 10:15:38 UTC,"I think it would be best to forge a migration path from queens to rocky in the form
of a blueprint. It would be a continuously updated commit until the release
of rocky. I will jump on that later today, so that the core team can review it as changes
occur. Removing uuid token provider would be the first stage of it, and it will also close this bug."
1749666,2018-02-17 00:50:46 UTC,"Hi Alex,
how to fix this Bug, am still have the same Problem with Pike.
Do have a Workaround ?"
1749666,2018-03-05 22:27:58 UTC,"Since this bug is only affecting development branch (master), removed critical tag."
1749666,2018-10-24 10:02:52 UTC,"Hi, I'm trying to deploy kolla-ansible with queens release and I'm getting the same mistake:"
1749666,2019-10-03 10:38:47 UTC,docker exec keystone keystone-manage db_sync
1749672,2019-07-09 16:26:27 UTC,"Override component to main
xdg-desktop-portal 1.0.3-0ubuntu0.0 in xenial: universe/admin -> main
xdg-desktop-portal 1.0.3-0ubuntu0.0 in xenial amd64: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.0 in xenial arm64: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.0 in xenial armhf: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.0 in xenial i386: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.0 in xenial powerpc: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.0 in xenial ppc64el: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.0 in xenial s390x: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.0 in xenial amd64: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.0 in xenial arm64: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.0 in xenial armhf: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.0 in xenial i386: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.0 in xenial powerpc: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.0 in xenial ppc64el: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.0 in xenial s390x: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.0 in xenial amd64: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.0 in xenial arm64: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.0 in xenial armhf: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.0 in xenial i386: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.0 in xenial powerpc: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.0 in xenial ppc64el: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.0 in xenial s390x: universe/admin/optional/100% -> main
22 publications overridden."
1749672,2019-01-22 23:04:08 UTC,Security team ACK for promoting xdg-desktop-portal-gtk and xdg-desktop-portal to main for bionic and xenial.
1749672,2018-10-04 16:40:11 UTC,"Override component to main
xdg-desktop-portal 1.0.2-1 in cosmic: universe/misc -> main
xdg-desktop-portal 1.0.2-1 in cosmic amd64: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.2-1 in cosmic arm64: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.2-1 in cosmic armhf: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.2-1 in cosmic i386: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.2-1 in cosmic ppc64el: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.2-1 in cosmic s390x: universe/admin/optional/100% -> main
Override [y|N]? y
7 publications overridden."
1749672,2019-07-09 16:13:08 UTC,"Override component to main
xdg-desktop-portal 1.0.3-0ubuntu0.2 in bionic: universe/misc -> main
xdg-desktop-portal 1.0.3-0ubuntu0.2 in bionic amd64: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.2 in bionic arm64: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.2 in bionic armhf: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.2 in bionic i386: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.2 in bionic ppc64el: universe/admin/optional/100% -> main
xdg-desktop-portal 1.0.3-0ubuntu0.2 in bionic s390x: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.2 in bionic amd64: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.2 in bionic arm64: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.2 in bionic armhf: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.2 in bionic i386: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.2 in bionic ppc64el: universe/admin/optional/100% -> main
xdg-desktop-portal-dev 1.0.3-0ubuntu0.2 in bionic s390x: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.2 in bionic amd64: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.2 in bionic arm64: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.2 in bionic armhf: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.2 in bionic i386: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.2 in bionic ppc64el: universe/admin/optional/100% -> main
xdg-desktop-portal-tests 1.0.3-0ubuntu0.2 in bionic s390x: universe/admin/optional/100% -> main
19 publications overridden."
1749672,2018-07-27 03:21:27 UTC,"I reviewed xdg-desktop-portal (0.11-2) as checked into cosmic. This is not
a full security audit but rather a quick gauge of maintainability."
1749672,2018-02-23 21:16:43 UTC,"This seems fine from a MIR perspective, but needs a security review."
1749672,2018-02-21 19:37:10 UTC,Security review needed.
1749672,2018-02-15 16:59:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749672,2018-09-13 12:27:37 UTC,this needs seeding or a package referencing it
1749674,2018-02-15 10:16:13 UTC,Also this will probably trigger if the overcloud stack is named differently?
1749674,2019-07-29 21:26:54 UTC,"Yes, this does indeed happen when one uses a different stack name"
1749680,2018-02-15 11:03:30 UTC,Good catch!
1749680,2018-02-15 12:08:46 UTC,Proposed ansible lint rule to tackle this: https://github.com/willthames/ansible-lint/pull/324
1749680,2018-02-15 12:28:42 UTC,"Note to self: OSA ships rules in https://github.com/openstack/openstack-ansible-tests/tree/master/ansible-lint, if the upstream PR is rejected, the rule could be proposed to OSA."
1749680,2018-02-23 14:05:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547432"
1749690,2018-03-02 07:08:22 UTC,"I also had this problem, and the newtwork was NOT down, and my distribution is supported (Ubuntu 17.10). I have an HP LaserJet P1102.
I had to download the plugin manually and select it from hp-setup."
1749690,2019-10-08 07:42:32 UTC,Install apparmor utils
1749690,2019-01-29 17:50:48 UTC,This was still an issue as of today with Linux Mint 19. I installed the plugin manually as Afshan suggested and it worked for me.
1749690,2018-03-09 09:05:38 UTC,"Just to confirm that after some manual attempts failed, I also heard
from some other users that the issue was being looked at."
1749690,2018-02-19 12:14:07 UTC,"Hi Afshan,"
1749690,2018-02-16 22:49:26 UTC,I am having the same issue that the hp-plugin tells me:
1749690,2018-02-19 11:58:27 UTC,"Hi Vasya,"
1749690,2018-02-18 06:35:56 UTC,"Ok, here is how I was able to get my printer to work."
1749690,2018-02-17 15:30:38 UTC,Affects Debian hplip version 3.16.11+repack0-3
1749690,2018-02-17 07:34:28 UTC,"Yup, same here and I just bought a brand new HP Color Laser printer that I can't use. I'm taking it back if this issue doesn't get fixed shortly."
1749690,2018-02-16 04:23:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749690,2018-02-19 12:04:29 UTC,"It appears that the problem is fixed now. Today hp-setup successfully downloaded and installed plugin. Since there were no updates to the packages, I assume the issue was on HP servers."
1749699,2018-02-15 13:14:20 UTC,"it is also not an error at all, it is an artificially picked threshold, we should not treat it as an error but use more proper wording altogether ..."
1749706,2018-04-28 09:51:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749707,2018-06-29 10:26:44 UTC,"I'm not sure, if I see a reincarnation of this bug here:"
1749707,2018-06-29 12:24:16 UTC,"Regarding the pysnmp_mibs warnings (Comment 2), they are harmless and are fixed with this patch that recently landed - https://review.openstack.org/#/c/570400/."
1749707,2018-06-29 16:14:29 UTC,There doesn't seem to an introspection issue identified here except that the node is taking an excessive amount of time to power off.
1749707,2018-09-16 01:09:16 UTC,"Reviewed:  https://review.openstack.org/580119
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=d64a2585daea72c248e1c07f5c76b4c8c51e2799
Submitter: Zuul
Branch:    master"
1749707,2018-08-21 09:45:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/594111"
1749707,2018-08-30 09:15:19 UTC,"Reviewed:  https://review.openstack.org/594111
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=7cc62968410f5b55d7a95707c71a641c72036a08
Submitter: Zuul
Branch:    master"
1749707,2018-06-29 06:49:00 UTC,"Wes, for my deployments, I'm using this tiny script:"
1749707,2018-06-30 09:13:45 UTC,"Reviewed:  https://review.openstack.org/579051
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=fb019907124240a2dbbd297567b54412ec6463c8
Submitter: Zuul
Branch:    master"
1749707,2018-06-29 04:26:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/579051"
1749707,2018-06-28 08:27:53 UTC,https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset002-master-upload/db23aa3/undercloud/var/log/extra/errors.txt.gz#_2018-06-28_00_08_10_998
1749707,2018-06-28 12:08:53 UTC,I opened a related bug (and submitted a patch) for the unhandled error loop. https://bugs.launchpad.net/tripleo/+bug/1779097
1749707,2018-06-28 16:59:07 UTC,"I need more information about the deployment than what I am seeing in this bug.
fs002 is working now that the correct config is passed"
1749707,2018-03-07 11:24:35 UTC,"[root@localhost ironic]# rpm -qa | grep snmp
net-snmp-agent-libs-5.7.2-28.el7_4.1.x86_64
net-snmp-libs-5.7.2-28.el7_4.1.x86_64
python2-pysnmp-4.3.2-3.el7.noarch
erlang-snmp-19.3.6.4-1.el7.x86_64
puppet-snmp-3.9.1-0.20180107181719.5d73485.el7.centos.noarch"
1749707,2018-03-22 08:35:35 UTC,"adding more content here: 2018-03-22 08:32:10.166 26096 WARNING mistral.actions.openstack.base [req-a429f94d-ef74-4cd5-9cdb-98bd1dd9eae9 1e8a5eab880b4bcc93168da6f7799248 7360d58d28c5407785ca8942de0c2303 - default default] Traceback (most
 recent call last):
  File ""/usr/lib/python2.7/site-packages/mistral/actions/openstack/base.py"", line 117, in run
    result = method(**self._kwargs_for_run)
  File ""/usr/lib/python2.7/site-packages/ironic_inspector_client/v1.py"", line 225, in wait_for_finish
    ""of nodes %s"") % new_active_uuids)
WaitTimeoutError: Timeout while waiting for introspection of nodes [u'0eac254f-7fa4-45e8-a82e-5d8edbf37f47']
: WaitTimeoutError: Timeout while waiting for introspection of nodes [u'0eac254f-7fa4-45e8-a82e-5d8edbf37f47']
2018-03-22 08:32:10.167 26096 ERROR mistral.executors.default_executor [req-a429f94d-ef74-4cd5-9cdb-98bd1dd9eae9 1e8a5eab880b4bcc93168da6f7799248 7360d58d28c5407785ca8942de0c2303 - default default] Failed to run
 action [action_ex_id=69f21c2c-c950-4663-a599-34840c39cd17, action_cls='<class 'mistral.actions.action_factory.BaremetalIntrospectionAction'>', attributes='{u'client_method_name': u'wait_for_finish'}', params='{
u'max_retries': 120, u'retry_interval': 10, u'uuids': [u'0eac254f-7fa4-45e8-a82e-5d8edbf37f47']}']
 BaremetalIntrospectionAction.wait_for_finish failed: Timeout while waiting for introspection of nodes [u'0eac254f-7fa4-45e8-a82e-5d8edbf37f47']: ActionException: BaremetalIntrospectionAction.wait_for_finish fai
led: Timeout while waiting for introspection of nodes [u'0eac254f-7fa4-45e8-a82e-5d8edbf37f47']
2018-03-22 08:32:10.167 26096 ERROR mistral.executors.default_executor Traceback (most recent call last):
2018-03-22 08:32:10.167 26096 ERROR mistral.executors.default_executor   File ""/usr/lib/python2.7/site-packages/mistral/executors/default_executor.py"", line 114, in run_action
2018-03-22 08:32:10.167 26096 ERROR mistral.executors.default_executor     result = action.run(action_ctx)
2018-03-22 08:32:10.167 26096 ERROR mistral.executors.default_executor   File ""/usr/lib/python2.7/site-packages/mistral/actions/openstack/base.py"", line 130, in run
2018-03-22 08:32:10.167 26096 ERROR mistral.executors.default_executor     (self.__class__.__name__, self.client_method_name, str(e))
2018-03-22 08:32:10.167 26096 ERROR mistral.executors.default_executor ActionException: BaremetalIntrospectionAction.wait_for_finish failed: Timeout while waiting for introspection of nodes [u'0eac254f-7fa4-45e8
-a82e-5d8edbf37f47']"
1749707,2018-03-23 08:55:49 UTC,"Even when this was reported on a local deployment, it can be easily reproduced by using devmode on RDO cloud"
1749707,2018-03-07 11:19:31 UTC,I can not find any file/directory with the name pysnmp_mibs
1749707,2018-03-07 11:14:34 UTC,"in ironic-conductor log, I found:
2018-03-07 10:12:42.116 2922 DEBUG ironic.common.utils [-] Command stdout is: ""Chassis Power is on
"" execute /usr/lib/python2.7/site-packages/ironic/common/utils.py:76
2018-03-07 10:12:42.116 2922 DEBUG ironic.common.utils [-] Command stderr is: """" execute /usr/lib/python2.7/site-packages/ironic/common/utils.py:77
2018-03-07 10:12:42.117 2922 ERROR oslo.service.loopingcall [-] Dynamic backoff interval looping call 'ironic.conductor.utils._wait' failed: LoopingCallTimeOut: Looping call timed out after 19.72 seconds
2018-03-07 10:12:42.117 2922 ERROR oslo.service.loopingcall Traceback (most recent call last):
2018-03-07 10:12:42.117 2922 ERROR oslo.service.loopingcall   File ""/usr/lib/python2.7/site-packages/oslo_service/loopingcall.py"", line 141, in _run_loop
2018-03-07 10:12:42.117 2922 ERROR oslo.service.loopingcall     idle = idle_for_func(result, watch.elapsed())
2018-03-07 10:12:42.117 2922 ERROR oslo.service.loopingcall   File ""/usr/lib/python2.7/site-packages/oslo_service/loopingcall.py"", line 338, in _idle_for
2018-03-07 10:12:42.117 2922 ERROR oslo.service.loopingcall     % self._error_time)
2018-03-07 10:12:42.117 2922 ERROR oslo.service.loopingcall LoopingCallTimeOut: Looping call timed out after 19.72 seconds
2018-03-07 10:12:42.117 2922 ERROR oslo.service.loopingcall
2018-03-07 10:12:42.117 2922 ERROR ironic.conductor.utils [req-6184f919-5874-4f2c-87a8-0d9b5fde2a1f 652b46cbc4544957bf2909991a20b29b f5025b207a33405a96d9f570742c8a11 - default default] Timed out after 30 secs waiting for power power off on node 128d8c6c-928a-4100-8c44-e59ec6cc306e.: LoopingCallTimeOut: Looping call timed out after 19.72 seconds
2018-03-07 10:12:42.149 2922 DEBUG ironic.conductor.task_manager [req-6184f919-5874-4f2c-87a8-0d9b5fde2a1f 652b46cbc4544957bf2909991a20b29b f5025b207a33405a96d9f570742c8a11 - default default] Successfully released exclusive lock for changing node power state on node 128d8c6c-928a-4100-8c44-e59ec6cc306e (lock was held 39.03 sec) release_resources /usr/lib/python2.7/site-packages/ironic/conductor/task_manager.py:352
2018-03-07 10:12:42.273 2922 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): ipmitool -I lanplus -H 10.0.1.12 -L ADMINISTRATOR -U admin -R 12 -N 5 -f /tmp/tmpzfNatr power status execute /usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py:372
2018-03-07 10:12:42.393 2922 DEBUG oslo_concurrency.processutils [-] CMD ""ipmitool -I lanplus -H 10.0.1.12 -L ADMINISTRATOR -U admin -R 12 -N 5 -f /tmp/tmpzfNatr power status"" returned: 0 in 0.120s execute /usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py:409
2018-03-07 10:12:42.394 2922 DEBUG ironic.common.utils [-] Execution completed, command line is ""ipmitool -I lanplus -H 10.0.1.12 -L ADMINISTRATOR -U admin -R 12 -N 5 -f /tmp/tmpzfNatr power status"" execute /usr/lib/python2.7/site-packages/ironic/common/utils.py:75
2018-03-07 10:12:42.394 2922 DEBUG ironic.common.utils [-] Command stdout is: ""Chassis Power is on
"" execute /usr/lib/python2.7/site-packages/ironic/common/utils.py:76
2018-03-07 10:12:42.395 2922 DEBUG ironic.common.utils [-] Command stderr is: """" execute /usr/lib/python2.7/site-pa..."
1749707,2018-06-28 08:31:42 UTC,There is also a circular dependency detected there
1749707,2018-06-28 08:48:58 UTC,"that Errno 13 should be a red herring, see the elastic recheck stats for 'hardware type or interface pxe_ipmitool could not be loaded'"
1749707,2018-06-28 08:22:04 UTC,"It's a promotion blocker
https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset002-master-upload/db23aa3/undercloud/home/jenkins/overcloud_prep_images.log.txt.gz"
1749707,2018-06-28 09:01:36 UTC,"Also nova v2 client removed 'certs' attribute
https://github.com/openstack/python-novaclient/commit/4bc4078fcb4f2a47269882cc83e1d637db1f37c2#diff-44e279ea2e50d3bb91894688e57c02f8"
1749709,2018-03-13 14:57:43 UTC,"Failing test with extra logging enabled, needs some work to sort through
all the logs:
http://10.125.0.203:8080/job/RunUnittests-ppc64el/282/testReport/junit/github/com_juju_juju_worker_provisioner/TestPackage/"
1749709,2019-09-09 05:30:12 UTC,we have done a bit of work on provisioner tests and this one is no longer in our codebase.
1749709,2018-02-28 00:33:10 UTC,"Adding extra logging. It isn't obvious what the problem is, but the test is stupid."
1749709,2018-02-15 13:54:19 UTC,(was seen on the 2.3 branch.)
1749709,2018-03-12 13:14:31 UTC,"several intermittent failures in this test:
 bug #1753407
 bug #1754021
 bug #1749709"
1749709,2018-02-28 00:36:20 UTC,https://github.com/juju/juju/pull/8434
1749710,2018-02-15 13:52:07 UTC,"Juju is connecting to an HTTPS endpoint, albeit on a non-standard port. But
it should use a Proxy if you need a proxy to connect to remote machines."
1749710,2018-02-15 14:20:42 UTC,"As a user, I don't consider this a Juju bug."
1749710,2018-02-15 15:10:05 UTC,"> I think it's a fairly widely used and expected behavior.
"
1749710,2018-02-16 02:18:39 UTC,I think it would be sufficient to add some logging saying the proxy it is using if one is set. Sound ok Junien?
1749710,2018-02-16 06:57:28 UTC,Sure
1749711,2018-02-15 15:07:56 UTC,"I should add this is on a fresh devstack with only ""enable_plugin mistral https://github.com/openstack/mistral"" added to localrc."
1749712,2018-02-19 02:03:30 UTC,(probably)
1749712,2018-02-19 02:01:50 UTC,Duplicate of
1749719,2018-02-15 15:48:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545013"
1749721,2018-02-16 23:50:24 UTC,">> but then, why does it affect the doc when I close and open it?
"
1749721,2018-02-17 13:11:56 UTC,"The setting in the Preferences dialog is labeled ""Default grid settings"" to indicate that new documents will have the values it contains."
1749721,2018-02-19 02:00:04 UTC,Doesn't sound like a wishlist item to me - it should either:
1749721,2020-08-15 18:53:33 UTC,"Might qualify as an UX issue (which you could try posting to gitlab.com/inkscape/inbox issues), but working as intended imo : changing the ""default grid settings"" does change the value for grids created after that ?"
1749721,2018-02-16 02:54:45 UTC,"Are you changing the default grid setting in the Preferences panel, or the current grid settings in the Document Properties dialog (Grids tab)?"
1749721,2018-02-16 20:39:45 UTC,"On 16/02/2018 02:54, TylerDurden wrote:

> Are you changing the default grid setting in the Preferences panel, or
> the current grid settings in the Document Properties dialog (Grids tab)?
>
> Also which OS?
>
> TD
>


Thank you for replying,"
1749722,2018-04-12 19:37:05 UTC,An upstream commit landed for this bug.
1749722,2018-06-20 18:06:59 UTC,"This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New"
1749722,2018-02-19 15:47:56 UTC,"On Mon, Feb 19, 2018 at 9:33 AM, Dimitri John Ledkov <<email address hidden>

> wrote:
"
1749722,2018-02-15 20:27:21 UTC,"Note, while timesyncd does have a compiled in value, it can be modified, and cloud-init already knows how to render a systemd-timesyncd configuration file to set the ntp configuration."
1749722,2018-02-19 15:33:10 UTC,"I think cloud-init is the oracle of information of which ntp daemon to use, and which ntp servers to use. Thus on bionic+ cloud-init, when configuring ntp, should also ""disable systemd-timesyncd"" if some alternative NTP server is to be used."
1749722,2018-02-15 20:02:41 UTC,"Thanks for the bug report.  This is in progress already, but may not be solved in exactly the way you are suggesting.  I'll let Ryan comment on specific implementation as he sees fit."
1749722,2018-02-19 15:33:46 UTC,"""if some alternative NTP server is to be used."" should read ""if some alternative NTP client daemon is to be used."" obviously =)"
1749722,2018-02-16 23:20:44 UTC,"Some further looking at the systemd side, Bionic no longer carries the override conf (disable-with-time-daemon.conf) in favor of updating each client's systemd unit to use:"
1749723,2018-02-18 09:05:02 UTC,"Hi Gustavo,"
1749723,2018-02-18 09:06:09 UTC,To be precise:
1749723,2018-02-18 02:41:19 UTC,This seems more close to you having held broken packages. Can you run dpkg --configure -a and apt-get install -f to see if that fixes it?
1749725,2018-02-22 18:41:20 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1749727,2018-06-01 22:39:04 UTC,"Do you happen to have a link to the Gnocchi policy that breaks this? Just curious because this is the first time I've seen a policy rule built like that, as opposed to the following syntax:"
1749727,2018-06-29 13:18:24 UTC,"Hi Lance,"
1749727,2018-10-24 18:57:07 UTC,"This is very much an odditiy in how oslo_policy does the creds dict lookup. Basically the first value is always a direct lookup of the creds dict, so you do creds_dict[<key, first value>] compared with the literal string of the second value."
1749728,2018-03-20 22:37:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749728,2018-05-11 23:41:51 UTC,"I am experiencing the same behavior in Xubuntu 18.04 (has been a problem for a while) when using ""open with"" on the .deb package from Thunar (right mouse menu). If I start gdebi-gtk from the command line and use the ""file open"" menu option then everything works ok."
1749728,2018-07-08 16:45:51 UTC,I finally got around to tracking down this problem it seems to be a mimeinfo.cache issue.
1749728,2018-07-09 15:46:31 UTC,after some sleep I have a couple of additional comments:
1749728,2018-07-09 16:05:32 UTC,from my auth.log file:
1749728,2018-10-05 21:58:26 UTC,any news on this bug ? very annoying ....
1749730,2018-04-15 19:58:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749734,2018-08-06 09:57:55 UTC,"Since implementing this on delete_host command would make this a copy of nova service-list, we now focus only on delete_cell; tbh I am not sure what's the goal of having delete_host.. maybe to just delete the host_mapping and re-create the host mapping in the same cell? -> wondering what's the use case for that."
1749734,2018-02-21 15:13:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546660"
1749734,2018-02-15 15:56:02 UTC,Bug has been filed following the discussion on IRC : http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-02-14.log.html#t2018-02-14T15:08:39
1749734,2018-07-06 14:14:49 UTC,This is arguably a duplicate of bug 1756179 which is already resolved now - DELETE /os-services/{id} will now delete resource provider and host mapping for a compute service record when deleting the service via the REST API.
1749739,2018-02-17 16:53:52 UTC,Ive seen that happen to me too
1749739,2020-09-10 14:18:22 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1749742,2018-02-15 17:41:11 UTC,A mockup of how that would work:
1749742,2018-02-16 18:52:58 UTC,"Are you aware that in case of recording (to a file), you can create a cue file which is a representation of that? (Aside of the benefits of having a .cue file with software that recognizes it, to begin with)"
1749742,2018-02-17 09:13:07 UTC,"I think that having a list of songs in the comment section also can be an advantage to the user as if he wants to have a more readable list of songs, he will not be required to have a software to support .cue files or have to convert the .cue file in some other format."
1749744,2018-02-15 17:21:09 UTC,apport information
1749744,2018-02-15 17:21:11 UTC,apport information
1749744,2018-02-20 16:43:55 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1749744,2018-02-20 17:17:15 UTC,"Chère Madame, cher Monsieur,"
1749744,2018-03-05 18:20:50 UTC,"hello
i have installed"
1749744,2018-02-23 18:36:45 UTC,kernel-bug-exists-upstream
1749744,2018-03-05 07:54:45 UTC,"Please try drm-intel-nightly [1]. If the issue still happen,"
1749744,2018-03-06 09:35:01 UTC,bug filed at https://bugs.freedesktop.org/
1749744,2018-02-15 17:21:06 UTC,apport information
1749744,2018-02-23 18:34:09 UTC,"hi
I still the same kernel warning  ."
1749744,2018-02-15 17:21:05 UTC,apport information
1749744,2018-02-15 17:20:57 UTC,apport information
1749744,2018-02-15 17:21:02 UTC,apport information
1749744,2018-02-15 17:20:52 UTC,apport information
1749744,2018-02-15 17:20:52 UTC,apport information
1749744,2018-02-15 17:20:54 UTC,apport information
1749744,2018-02-15 17:20:55 UTC,apport information
1749744,2018-02-15 17:20:56 UTC,apport information
1749744,2018-02-15 17:21:03 UTC,apport information
1749744,2018-02-15 17:20:58 UTC,apport information
1749744,2018-02-15 17:20:59 UTC,apport information
1749744,2018-02-15 17:21:00 UTC,apport information
1749744,2018-02-15 17:21:01 UTC,apport information
1749744,2018-02-15 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1749769,2018-02-15 18:06:23 UTC,And here my gpu-manager.log
1749769,2018-02-15 18:06:50 UTC,And lspci
1749769,2018-02-15 18:07:14 UTC,Xorg.0.log too
1749769,2018-02-15 18:14:08 UTC,and in kern.log there always:
1749769,2018-10-08 22:18:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749770,2018-02-21 13:36:40 UTC,"Hi Brian,"
1749770,2018-02-21 17:35:21 UTC,"I agree that affix number 3 makes it clear that ""Scan to PC"" means that the scan is initiated from the PC. So surely the field should say ""Scan from PC""?"
1749774,2018-02-15 20:26:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749774,2019-05-10 06:07:40 UTC,Thanks Steve for the ping for awareness!
1749774,2019-05-10 06:20:10 UTC,MP prepared in [1]
1749774,2019-05-13 14:00:40 UTC,This bug was fixed in the package ubuntu-meta - 1.434
1749777,2018-02-27 23:09:31 UTC,"Yeah, we spent a lot of time trying to make the output both compact and showing command lines. The problem is that once you have more than a few options, it gets wild and unfriendly as a dump of information after a typo."
1749777,2019-09-19 09:08:02 UTC,The output in Eoan today currently looks like the following:
1749777,2018-02-28 15:07:29 UTC,This bug was fixed in the package command-not-found - 18.04.0~pre1
1749777,2018-02-28 07:25:23 UTC,The current output (in lp:command-not-found) looks like this:
1749777,2018-02-27 23:07:18 UTC,Just copying over my description from Bug #1752185 here for reference:
1749777,2018-02-27 20:49:20 UTC,I think it is an UX regression to go from:
1749777,2018-02-27 20:50:14 UTC,I liked that the 'existing' version of command-not-found was explicit about the action to take:
1749777,2018-02-21 13:58:23 UTC,"On 02/21/2018 01:36 PM, Michael Vogt wrote:

> We are working on improving this currently. Right now c-n-f has no
> version concept for the apt backend (easy for snaps). But we have a plan
> how to fix that (some work though).
"
1749777,2018-02-21 13:36:30 UTC,We are working on improving this currently. Right now c-n-f has no version concept for the apt backend (easy for snaps). But we have a plan how to fix that (some work though).
1749777,2018-02-21 11:35:25 UTC,Perhaps this would be a better format:
1749777,2018-02-27 23:05:10 UTC,I'm also much more fond of the original output (that I mostly wrote) because it was actionable. When doing the format transition we lost the intent of the tool. To help novice users install packages that they may not be familiar with.
1749779,2018-02-22 01:51:37 UTC,"I've had a look at your crash files and unfortunately they do not contain stack traces we can read yet. Sometimes they do in plain text... Uploading the crash files with the 'ubuntu-bug' command should fix that, allowing robots to do proper retracing on them."
1749779,2018-02-22 07:06:22 UTC,"When executing ubuntu-bug with the crash file, I do not get any bug ID."
1749779,2018-02-22 07:39:11 UTC,"Since you have applied the workaround from bug 994921 already, one of those approaches should work now."
1749779,2018-02-22 17:25:58 UTC,"https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1751101
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1751102"
1749779,2018-02-24 09:49:00 UTC,I applied the procedure described there: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1751101/comments/7
1749779,2018-02-26 02:17:24 UTC,"Reported upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/71"
1749779,2020-04-06 17:17:40 UTC,No problem with Ubuntu 20.04 and Firefox 74
1749779,2020-05-03 09:18:41 UTC,"For me  in 20.04, bug is definitely still present. I have earlyoom active, and 32 gb a few seconds of ""freeze"" (which is not really a freeze) earlyoom activates and nukes a few things, including Firefox, which brings back interactive response. It also killed Chrome and Remmina, which was irritating, but that's what earlyoom is there to do; better than minutes of no keyboard response.
Alt F2 seem to work after a few seconds too, which allows restart of the gnome shell.
I will comment on the upstream bug."
1749779,2020-05-05 05:58:39 UTC,it also aftects me on ubuntu 20.04
1749779,2020-12-10 17:23:19 UTC,"Same problem with Ubuntu 20.10 if I hold a little bit too much F11 with Firefox.
Ubuntu 20.10 AMD CPU Wayland
GPU RADEON 6850"
1749779,2018-02-21 21:30:38 UTC,"Because I did not want to leak any personal data in the crash files, I reinstalled an Ubuntu 17.10 on another hard drive to have a fresh generic installation and did the tests there before rebooting on my regular installation."
1749779,2018-02-26 02:10:39 UTC,"Yes, sorry. I can confirm the bug exists in 18.04. It is trivial to reproduce, which is unusual :("
1749779,2018-02-21 02:11:32 UTC,"OK, thanks. I don't know why that happens. It never fails like that for me but other people have reported the problem you describe."
1749779,2018-02-19 20:39:30 UTC,I cannot reproduce the problem with gedit. Maybe the problem arises only with XWayland.
1749779,2018-02-20 01:28:45 UTC,"Sorry, I forgot to mention that you may need to apply the workaround for bug 994921 _first_."
1749779,2018-02-20 21:25:56 UTC,I applied the workaround and ran again the command. It seems that nothing happens when I try to send the report:
1749779,2002-12-13 13:55:21 UTC,"User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021211
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021211"
1749779,2002-12-13 14:55:21 UTC,"Confirming (build 2002121108, win95), Changing OS->All. I also think this is a
real bug, not an enhanchment, setting severity to minor."
1749779,2008-06-10 16:59:12 UTC,"Filter ""spam"" on ""guifeatures-nobody-20080610""."
1749779,2018-02-16 02:14:55 UTC,"Please install 'openssh-server' and log into the system from another computer. Now reproduce the freeze and during the freeze, run this from your ssh login:"
1749779,2018-02-17 10:48:16 UTC,"Hello Daniel. Thank you for your suggestion. However, I get this error:"
1749779,2018-02-19 02:07:41 UTC,Please try this instead then:
1749779,2018-02-17 11:17:22 UTC,"I found the bug with my main computer which has an AMD gpu. I can reproduce the bug with the PC I'm using to connect with SSH. I just need to hold F11 down on Firefox. That PC has a nVidia gpu, so I guess the problem is gpu vendor independent."
1749779,2018-02-17 11:05:39 UTC,These are the processes that take the most of CPU time when the freeze occurs:
1749779,2018-02-19 20:27:56 UTC,I ran the command and asked to save the report (creating a new bug requires a Web browser).
1749779,2018-02-19 20:29:40 UTC,"Interestingly, doing the same with Sublime Text leads to the same result."
1749779,2018-02-20 01:27:12 UTC,Yes you can copy the link out of ssh into your local machine's web browser to complete the bug creation. Please do that. Once you have that link it does not matter which machine you use the web browser on the to complete the process.
1749791,2018-06-12 09:22:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749794,2019-09-19 14:53:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1749803,2020-01-06 11:08:18 UTC,"Hello,
4.13.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1749809,2019-04-17 06:06:28 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?"
1749809,2019-06-17 04:17:25 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1749814,2018-11-12 20:49:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749814,2020-02-27 02:41:20 UTC,"For ubuntu 18.04, php7.2 is the default.  If a different version is installed you'll likely need to rebuild php-imagick (and other modules) to get them to work with that version."
1749815,2018-02-15 22:00:07 UTC,This change was made by a bot.
1749815,2018-02-20 16:42:40 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1749815,2018-02-22 23:12:39 UTC,Thanks Joseph for your help. I have always had this problem with this machine.
1749822,2018-04-10 20:54:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749826,2018-02-15 23:00:07 UTC,This change was made by a bot.
1749826,2018-02-20 16:42:12 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1749826,2018-02-22 23:16:20 UTC,Thanks Joseph for your help. I have always had this problem with this machine.
1749848,2018-12-03 22:39:24 UTC,I don't think we're grabbing load logs at all anymore.
1749858,2018-02-16 00:58:17 UTC,This is the JNLP file that is crashing.
1749864,2019-01-17 18:05:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749864,2019-01-17 18:06:37 UTC,"For me, the application works but most of the button icons do not display properly."
1749864,2020-04-20 07:36:16 UTC,Same here. Using printer Brother DCP-L2552DN
1749865,2018-02-16 08:28:44 UTC,"Hi Simon,"
1749865,2020-04-09 04:17:22 UTC,[Expired for usd-importer because there has been no activity for 60 days.]
1749869,2018-05-05 18:18:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749870,2019-09-19 14:46:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1749873,2021-01-21 00:16:32 UTC,i.e. Ubuntu >= 20.04.
1749873,2021-01-21 00:14:44 UTC,This was fixed in Virtualenv 20.
1749879,2018-02-22 01:40:32 UTC,"Reviewed:  https://review.openstack.org/545995
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=403b4cd3b5e09fd4055d620eba73890f8223f9e1
Submitter: Zuul
Branch:    master"
1749879,2018-02-19 22:04:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/545995"
1749882,2018-03-13 10:43:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/552473"
1749884,2019-03-08 17:16:01 UTC,There are two branches implementing a fix for this.
1749888,2018-06-29 03:43:37 UTC,"Change abandoned by Rajat Dhasmana (<email address hidden>) on branch: master
Review: https://review.openstack.org/574178
Reason: https://review.openstack.org/#/c/576479/"
1749888,2018-06-29 03:42:17 UTC,"Change abandoned by Rajat Dhasmana (<email address hidden>) on branch: master
Review: https://review.openstack.org/576479
Reason: http://eavesdrop.openstack.org/meetings/cinder/2018/cinder.2018-06-27-16.03.log.html#l-56"
1749888,2018-06-14 00:55:47 UTC,"What's the difference if I create a volume with specified AZ, and then restore that volume?"
1749888,2018-06-19 10:44:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/576479"
1749888,2018-05-21 20:24:24 UTC,"It's not the create call I'm talking about, it's the backup-restore call"
1749888,2018-05-21 11:39:30 UTC,"hi,"
1749888,2018-02-18 21:25:28 UTC,Maybe it should be handled like a snapshot is and instead of having a separate method (backup-restore) you can pass a backup ID into the create volume call?
1749888,2018-02-16 11:44:59 UTC,There are currently 2 ways to do this:
1749888,2018-06-11 09:03:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/574178"
1749888,2018-06-19 06:07:02 UTC,I think maybe the best way to handle this is to support a backup-id argument to the volume-create method? Then it acts in the same way as creating a volume from a snapshot. The backup-restore method could be deprecated.
1749897,2018-02-16 05:21:41 UTC,It's not a fresh install.
1749903,2018-02-16 07:32:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749936,2018-02-18 02:25:43 UTC,"I don't think Gnome web browser comes default with Artful. You can check it here:
http://releases.ubuntu.com/17.10/ubuntu-17.10.1-desktop-amd64.manifest
http://releases.ubuntu.com/17.10.1/ubuntu-17.10.1-desktop-amd64.manifest"
1749939,2019-08-07 18:56:18 UTC,UI has been removed
1749942,2019-10-14 21:23:46 UTC,Bionic currently has fping 4.0-6 and smokeping 2.6.11-4. So unfortunately the buggy smokeping version combined with the more recent fping version break smokeping's detection:
1749942,2019-10-14 21:20:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749942,2019-03-24 15:36:28 UTC,"ook, 2nd trial. I've reapplied the same changes on the right version this time. so smokeping 2.6.11-4"
1749942,2019-04-20 20:51:22 UTC,"Hello Gabriel, thanks for your work on this bug!"
1749942,2019-03-23 21:31:54 UTC,"oops. seems like I based my changes on the wrong package version. bionic has 2.6.11-4, not -2"
1749942,2019-03-23 20:28:46 UTC,Here's (attached) my first attempt at the debdiff thing. I'm hoping that I did this correctly but I'm not used to this process so please tell me if I need to correct some aspect of it.
1749942,2019-03-23 18:58:26 UTC,Oh.. actually to completely fix smokeping's compatibility with smokeping we need also a second patch (which is actually addressing the original bug report *harrumpf*).
1749942,2019-03-23 18:46:24 UTC,Hi there!
1749942,2019-03-24 00:22:16 UTC,"The attachment ""Import two compatibility patches for fping 4.0"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1749944,2019-05-28 04:17:50 UTC,[Expired for kolla because there has been no activity for 60 days.]
1749944,2019-05-28 04:17:48 UTC,[Expired for nova (Ubuntu) because there has been no activity for 60 days.]
1749944,2018-03-01 18:42:21 UTC,It'd be useful if we could get a full list of installed packages. ubuntu-source-nova-compute isn't an Ubuntu package and I can't tell what nova-compute-* packages are installed. I think you can capture this info automatically by running 'apport-collect 1749944'.
1749944,2018-03-01 16:27:22 UTC,We install the following package:
1749944,2018-03-01 15:57:14 UTC,The Pike version of Dockerfile.j2 adds these files to the libvirt container.
1749944,2018-02-16 17:08:28 UTC,"nova-compute-libvirt Depends on python-libvirt
nova-compute-kvm Depends on nova-compute-libvirt
nova-compute Depends on nova-compute-kvm | nova-compute-hypervisor"
1749944,2018-02-16 16:59:58 UTC,"I can confirm that the (binary) Docker.io repo nova-compute image from 3 days ago fails on account of the missing libvirt package. Rebuilding nova-compute from master kolla-ansible with python-libvirt in Dockerfile.j2, then redeploying will fix the issue."
1749944,2018-02-16 16:32:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749944,2018-02-16 13:23:25 UTC,"Hi Eduardo, agree that having nova-compute-kvm one may expect to have python-libvirt installed too. However looks this is not the case :(
Images were fetched from Docker.io repo, not built by myself."
1749944,2018-02-16 12:47:06 UTC,"Hi, in libvirt should be a dependency of nova packages, in source installs we define such package, but in binary it was always a dependency of nova packages."
1749944,2018-02-16 12:27:09 UTC,"Looks like this error is similar to this one:
https://bugs.launchpad.net/kolla/+bug/1642640
https://review.openstack.org/#/c/399145/"
1749944,2018-03-01 13:31:44 UTC,The following binary packages provide the nova-compute-hypervisor virtual package. Please can you let us know which ones are installed?
1749950,2018-03-05 20:14:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749950,2019-11-14 02:10:25 UTC,"Closing this, as Deja Dup no longer links with WebKit"
1749959,2018-03-21 14:47:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1749961,2020-05-06 15:44:21 UTC,"Hi Ubuntu Community,"
1749961,2020-05-05 10:54:24 UTC,"Awesome Bryan, thanks for your kind words!!
I'll nominate this bug for Focal then.
Cheers,"
1749961,2020-05-04 22:34:33 UTC,"Hi Guilherme,"
1749961,2020-05-04 14:53:58 UTC,"Hi John and all, thanks for updating logs and enhancing the report! Due to a lot of other work, and the nature of this problem (being a FW issue that we'd try to alleviate using a hack in linux), I wasn't able to work the tentative hack approach yet."
1749961,2020-05-01 16:33:07 UTC,"Hi Ubuntu and Linux Team, I have been observing the attached dmesg output with several different ASMedia 3142 Cards whilst doing usb bulk transfers using the linux read and write api's to a usb device. This tends to break the software invoking said API's.  I am using Ubuntu server 18.04.3 with kernel 4.15.0-55-generic. I see this issue with both Intel and AMD based computers."
1749961,2019-12-21 23:22:11 UTC,"I also wanted to mention that in my case after the issue is triggered I can unplug the cable from the ethernet jack on the eGPU I have, then plug it back in and it'll work again for a little bit until I trigger it again."
1749961,2020-04-03 21:35:39 UTC,I'm also getting the above errors when trying to read from a 1080p60 USB3 webcam. It seems I have some information not mentioned above.
1749961,2020-02-28 15:34:06 UTC,I am seeing this same issue on my system. Any help would be greatly appreciated. I am using Ubuntu 16.04 with the 4.15.0-88-generic kernel. I have seen it on both host controllers on the motherboard.
1749961,2020-05-06 15:56:04 UTC,"Hi John,"
1749961,2019-12-21 22:34:30 UTC,"Guilherme, I've attached a dmesg that ends as soon as my ethernet in the egpu disconnects.  It's just a matter of running something like ""fast.com"" a couple times to trigger it."
1749961,2019-12-15 14:50:15 UTC,"Sounds good.  I'm not sure if matters or not but, I'm now on Ubuntu 19.10.  I'm seeing the exact same behavior as before."
1749961,2019-12-14 02:00:03 UTC,"Thank you Bryan! We can try the ""hackish"" approach proposed by Mathias in that thread..let me study the code and get back to you in next few weeks!"
1749961,2020-04-03 21:50:20 UTC,"Beyond all of that, does anyone happen to know of a USB3 card that does work (on Linux)?"
1749961,2020-05-06 16:51:24 UTC,"Hi John,"
1749961,2020-06-23 13:57:25 UTC,"I tried with iommu=off when I last looked at this and the problem
persisted."
1749961,2020-05-06 20:08:31 UTC,"John,"
1749961,2020-05-14 13:17:08 UTC,"Hi Aki and Linux Community, I was able to get the camera and Yes it does produce the issue reported above with an ASMedia 3142. I have captured a lecroy trace that I can share, I hope this helps someone.  You can observe the enumeration and timing between packets, as well as see where the flow control error occurs."
1749961,2020-06-23 07:17:32 UTC,"Could somebody that is seeing this problem try to boot with kernel flag ""iommu=off"". Some hardware that used to work with older kernels may be broken and fails to work with modern kernels which default to using IOMMU."
1749961,2020-06-29 23:25:28 UTC,"Tried running with iommu=off with my EGPU, exact same behavior as before."
1749961,2020-07-09 06:48:18 UTC,I was told by ASMedia only firmware update can fix this issue. Please ask the device/board vendor to roll out new firmware update.
1749961,2020-07-12 20:11:07 UTC,I'll try to reach out to Razer again to see if they will push out a firmware update.  Is there any documentation on the underlying firmware bug that I can point them towards?
1749961,2019-12-13 19:49:48 UTC,I would be willing to try a debug kernel.
1749961,2020-08-12 21:17:59 UTC,I am having the same exact error with `USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller` and a `Logitech StreamCam`.
1749961,2020-09-07 22:31:24 UTC,Has anyone gotten their hardware vendor to cough up a new firmware yet?  Razer has shown no movement.
1749961,2020-09-09 22:34:23 UTC,I've heard nothing back from razer.  I first submitted the issue to them over two years ago now.  Not holding my breath.
1749961,2020-10-27 22:30:12 UTC,Confirmed this continues on Ubuntu 20.10.
1749961,2021-01-03 15:15:03 UTC,"Hello, I have a Razer Core Chroma with this USB contoller, and I can confirm that this issue still present at 5.9.16."
1749961,2021-02-04 16:20:18 UTC,I did a little bit of research on the Razer Core Chroma usb card.
1749961,2021-02-23 13:57:00 UTC,"I can confirm @lamalas ""Lenovo Thunderbolt Dock Gen 2"" shows these same problems with a high speed USB (Samsung SSD T7) disk on Ubuntu 20.10. No need to involve the gige port to see the problem."
1749961,2020-05-06 18:46:25 UTC,"Thanks Lior, and Aki. I fear the Razer core X chroma may require extensive setup and a graphics card that I do not have handy or am prepared to take on right now.  And I cannot get the IMX291 CMOS Camera overnight. Aki, do you mind looking at the Camera and trying decipher which device side usb controller or mcu is on the board, maybe I can find something similar that I can get over night."
1749961,2019-12-13 14:06:55 UTC,"Thanks a lot @kaihengfeng! Quite great discussion with Mathias - it seems there's a potential quirk for IN packets, but the right approach indeed is getting the HW fixed by ASMedia."
1749961,2020-07-13 03:33:53 UTC,"No, I don't think there's any public information on this issue."
1749961,2019-12-13 13:11:17 UTC,"Hi Erik, thanks for your report! Can you attach a dmesg right after the issue reproduces?
Also, are you willing to run debug kernels in your machine?"
1749961,2019-12-13 13:23:49 UTC,"For reference, here's the analysis from xHCI maintainer:
https://<email address hidden>/"
1749961,2018-02-16 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1749961,2018-02-20 12:36:36 UTC,"Patch was modified (by adding the PCI_ID of device 1142A, which confusingly is 1242!) and still the problem reproduces."
1749961,2018-03-28 10:30:02 UTC,"Hello,
Looks like I am having the same problem."
1749961,2018-03-28 12:35:19 UTC,"Nice imperia, thanks for the report here. First we need to be sure it's exactly the same adapter.
Can you provide the the output of ""lspci -nn"" ?"
1749961,2018-03-29 15:14:49 UTC,"Hello,"
1749961,2018-03-29 19:00:20 UTC,"Mar 29 20:20:03 vdr kernel: [119370.230528] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c590 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230533] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230537] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.230542] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.230547] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5a0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.230553] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 0000000041e92668 (0x2ae36c5a0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.230558] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230631] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 0000000060641c50, dev 2, ep 0x82, starting at offset 0x2ae36c5a0
Mar 29 20:20:03 vdr kernel: [119370.230638] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230650] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5a0
Mar 29 20:20:03 vdr kernel: [119370.230700] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5a0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230705] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230710] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:20:03 vdr kernel: [119370.230715] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue segment = 00000000573583cc (virtual)
Mar 29 20:20:03 vdr kernel: [119370.230719] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: New dequeue pointer = 0x2ae36c5b0 (DMA)
Mar 29 20:20:03 vdr kernel: [119370.230725] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Set TR Deq Ptr cmd, new deq seg = 00000000573583cc (0x2ae36c000 dma), new deq ptr = 0000000050070757 (0x2ae36c5b0 dma), new cycle = 0
Mar 29 20:20:03 vdr kernel: [119370.230730] <intr> xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230798] [27868] xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cancel URB 00000000588cca08, dev 2, ep 0x82, starting at offset 0x2ae36c5b0
Mar 29 20:20:03 vdr kernel: [119370.230805] [27868] xhci_ring_cmd_db:282: xhci_hcd 0000:00:00.0: // Ding dong!
Mar 29 20:20:03 vdr kernel: [119370.230816] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Successful Set TR Deq Ptr cmd, deq = @2ae36c5b0
Mar 29 20:20:03 vdr kernel: [119370.230865] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Removing canceled TD starting at 0x2ae36c5b0 (dma).
Mar 29 20:20:03 vdr kernel: [119370.230870] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Finding endpoint context
Mar 29 20:20:03 vdr kernel: [119370.230874] <intr> xhci_dbg_trace:31: xhci_hcd 0000:00:00.0: Cycle state = 0x0
Mar 29 20:..."
1749961,2018-03-29 19:19:10 UTC,"Thanks a lot Imperia! It's indeed the same PCI adapter, and it's even better you're running an upstream kernel like this."
1749961,2018-03-29 22:41:44 UTC,"Wow Imperia, you're being really helpful here, thank you very much!"
1749961,2018-04-02 06:50:19 UTC,"Hello,"
1749961,2018-04-02 12:28:48 UTC,"Thanks again Imperia, the traces are fine. They're only 25MB, shouldn't have caused any kind of disk issues, like out of space condition. Also, I'd like to see the correlated kernel log to match the problematic TRBs from the kernel log with trace information. Can you provide me the relevant kern.log file?"
1749961,2018-04-10 23:14:50 UTC,"Hi Imperia, I built a mainline kernel (version 4.16) with a different quirk that I think might help here. Can you test it? Thanks in advance!"
1749961,2018-04-11 12:34:41 UTC,"Hello,"
1749961,2018-07-24 09:34:01 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1749961,2018-08-27 18:39:18 UTC,"this is dmidecode output of my machine, in case the fix is FW related, it may be useful in order to contact the motherboard vendor"
1749961,2018-03-29 20:12:44 UTC,"echo xhci-hcd >> /sys/kernel/debug/tracing/set_event
(tail -F -n0 /var/log/kern.log &) | grep -q ""TRB DMA""
cp /var/log/kern.log /home/imperia/log1.log"
1749961,2018-10-05 12:38:21 UTC,"Hi Roy, thanks for the report. What is your motherboard? What kernel are you running? And what tests are triggering this issue for you?
If you have logs, it'll be pretty useful."
1749961,2019-09-30 12:37:23 UTC,"So Felix, can you provide more details like the machine or device you're using, a dmesg showing the problem, and a bit more information about the device itself? I guess you're the first reporter with a ""SATA"" device showing that."
1749961,2019-09-28 23:11:41 UTC,having same problem with Bus 002 Device 004: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb
1749961,2019-05-26 06:49:35 UTC,"I am experiencing the exact same issue first reported in this LP (ASMedia ASM1142 USB 3.1 Controller with a Logitech Brio 4k, ERROR Transfer event TRB DMA ptr not part of current TD ...). In my case the controller is provided by a StarTech.com 4 Port USB 3.1 PCIe Card 3x USB-A and 1x USB-C [PEXUS313AC2V]."
1749961,2019-05-06 20:22:14 UTC,"Thanks Gabe! I agree with you, would be really nice to have a quirk for that. It would be more easy to analyze that possibility with a datasheet for this adapter, which unfortunately I don't have.
I'm on vacation until next week, I'll try to discuss that in linux-usb when I'm back, and pursue a kernel quirk instead of firmware-only fix."
1749961,2019-05-04 13:58:38 UTC,"In attempt to update the firmware I installed the razer software on my newly created windows partition, to see if it could be updated through there.  No luck."
1749961,2019-05-04 03:45:29 UTC,I'm also experiencing the same issue with the ASM1142 controller on the Core X Chroma and can reproduce consistently. I'm running kernel 5.0.9.
1749961,2019-04-29 13:32:31 UTC,"Great Bryan, the model of your USB controller is the same reported in this LP; also, given the outputs you provided, the network interface ""enx90203a19dcb6"" in under one of those USB controllers - you mentioned you see the TRB DMA errors and the interface stops responding. Is the problematic interface that one, ""enx90203a19dcb6"" ?"
1749961,2019-04-26 21:31:12 UTC,Please see attached log for the outputs that you requested.
1749961,2019-04-26 21:31:07 UTC,Please see attached log for the outputs that you requested.
1749961,2019-04-25 12:20:12 UTC,"Hi Bryan, thanks for the report. It could be the same issue, can you provide the full dmesg, and also the outputs of the following commands: ""lspci -nnvvv"", ""lspci -t"" and ""ls -l /sys/class/net""?"
1749961,2019-04-25 00:01:04 UTC,"Hello,"
1749961,2018-10-05 22:11:09 UTC,"Hi Roy, thanks for your quick response. First thing, I'd like to ask you to attach the output of ""lspci -vvv"" and ""dmidecode"" in this LP so we can validate the adapters and be sure they are exactly the same, and also the motherboard type. Run both commands as root user."
1749961,2018-10-05 14:16:18 UTC,"Hi Guilherme,"
1749961,2019-12-08 19:28:20 UTC,I'm also seeing this issue on a fresh install of Ubuntu 19.10 with a Razer Core X Chroma and a Lenovo X1 Extreme Gen2. I was seeing it on a fully updated Arch Linux install and installed Ubuntu in hopes it would fix the issue. Here's some info from my current install. Let me know if you need anything else!
1749961,2018-10-04 20:37:14 UTC,I am running into this same issue with an ASMedia 2142 USB board.  Was a fix ever identified?
1749964,2018-02-16 14:10:49 UTC,"StacktraceTop:
 Py_FatalError (msg=msg@entry=0x68db00 ""Cannot recover from stack overflow."") at ../Python/pylifecycle.c:1462
 _Py_CheckRecursiveCall (where=where@entry=0x660f48 "" while calling a Python object"") at ../Python/ceval.c:686
 _PyObject_FastCallDict (func=func@entry=0x7fbf8e9922d0, kwargs=0x0, nargs=0, args=0x0) at ../Objects/abstract.c:2305
 callmethod (is_size_t=0, va=0x7ffee41279d0, format=0x0, func=0x7fbf8e9922d0) at ../Objects/abstract.c:2583
 _PyObject_CallMethodId (o=o@entry=0x7fbfa55b3630, name=name@entry=0x9c2580 <PyId_flush>, format=format@entry=0x0) at ../Objects/abstract.c:2640"
1749969,2018-03-11 18:27:43 UTC,"I have tested this with ""Store_crypto"" plugin and as per my understanding the reason behind this is that it is not converting der to pem like it do in ""KMIP"" plugin."
1749969,2018-03-12 13:06:39 UTC,"Yes, I later tracked down in the code where this was happening: https://github.com/openstack/barbican/blob/master/barbican/plugin/crypto/simple_crypto.py#L142-L165"
1749970,2018-05-25 01:04:12 UTC,"The table only displays 100, but it also ignores the row limits along with pagination.  If you have 30 pending patrons and limit the rows to 10, it still displays 30 rows."
1749970,2019-04-02 16:45:24 UTC,This seems to be fixed by passing a count and offset to the backend API call.
1749970,2019-04-02 17:12:47 UTC,Working branch for review: user/jeff/lp1749970_fix_pending_patron_paging
1749970,2019-10-21 14:51:12 UTC,"Thanks, Jeff! I've confirmed that this fixes the paging bug. (The sort is still broken, but I'll go ahead and sign off on this one since the sort has a different bug.)"
1749970,2019-10-21 17:34:12 UTC,"Pushed to rel_3_4, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jeff and Terran!"
1749973,2018-02-18 17:49:11 UTC,"This is due to the fact that, when in autopilot mode, OR uses the default values used also for AI trains for the brake parameters, and not the values specific for the trainsets.
If you have problems with brakes remaining partly on when exiting autopilot mode, try using the brake reset command."
1749976,2018-02-21 00:08:05 UTC,Thanks!! Its works fine!
1749976,2018-02-20 16:41:08 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1749976,2018-02-16 17:09:01 UTC,apport information
1749976,2018-02-16 17:08:59 UTC,apport information
1749976,2018-02-16 17:08:53 UTC,apport information
1749976,2018-02-16 17:08:48 UTC,apport information
1749976,2018-02-16 17:08:50 UTC,apport information
1749976,2018-02-16 17:08:47 UTC,apport information
1749976,2018-02-16 17:08:51 UTC,apport information
1749976,2018-02-16 17:08:44 UTC,apport information
1749976,2018-02-16 17:08:46 UTC,apport information
1749976,2018-02-16 17:08:30 UTC,apport information
1749976,2018-02-16 17:08:33 UTC,apport information
1749976,2018-02-16 17:08:35 UTC,apport information
1749976,2018-02-16 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1749976,2018-02-16 17:08:39 UTC,apport information
1749976,2018-02-16 17:08:41 UTC,apport information
1749976,2018-02-16 17:08:43 UTC,apport information
1749976,2018-02-16 17:08:37 UTC,apport information
1749978,2018-02-16 15:53:21 UTC,Not sure why the entry is not created automatically: https://review.openstack.org/#/c/540473/
1749978,2018-02-16 17:36:50 UTC,@sofer we are working on https://review.openstack.org/#/c/543031/ to address the issue in holistic way
1749978,2018-02-16 17:42:51 UTC,hrm.. maybe better to look at https://review.openstack.org/#/c/545072/
1749978,2018-02-21 15:29:00 UTC,Adding that https://review.openstack.org/#/c/526000/ as requested.
1749978,2018-03-26 10:48:21 UTC,"Reviewed:  https://review.openstack.org/540473
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=33cf682ebb2a56c62cc7df0b6ba9170e1460f74e
Submitter: Zuul
Branch:    master"
1749983,2018-04-19 14:00:14 UTC,This issue was fixed in the openstack/cinder 13.0.0.0b1 development milestone.
1749983,2018-03-21 01:42:18 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/545382"
1749983,2018-02-16 16:42:12 UTC,Added nova since it has the exact same code.
1749983,2018-02-16 16:48:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545382"
1749983,2018-02-16 16:33:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545378"
1749983,2018-02-16 19:40:33 UTC,"Reviewed:  https://review.openstack.org/545378
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=c100c8f1888f8963ed5cf81661e52889d765d2b2
Submitter: Zuul
Branch:    master"
1749985,2018-02-16 16:25:26 UTC,installed packages via dpkg -l
1749985,2018-02-16 16:44:34 UTC,using aptitude:
1749993,2018-02-16 17:10:00 UTC,"Now I have turned off low graphic mode in terminal:
gsettings set com.canonical.Unity lowgfx false"
1749993,2018-02-16 17:22:39 UTC,"In both cases ""low graphic mode"" true or false the ""tab switcher"" background is too transparent too.
This happened to me first time and I am using Ubuntu more then 10 years (different versions of course but the same! laptop)."
1749993,2018-02-18 19:07:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750009,2018-02-16 18:39:16 UTC,"Per https://www.loc.gov/marc/bibliographic/bd490.html and http://www.loc.gov/standards/mods/v3/mods-mapping.html#relateditem the indexing seems to be doing what the rules say, and indexing the 8xx instead of the 490 when the latter is traced."
1750009,2018-02-16 19:02:07 UTC,"Ideally, when searching for 490 1 terms, records with the 8xx field linked to it would be retrieved."
1750009,2019-05-28 18:29:19 UTC,"I agree with Robert and Elaine. The indexing may be following the strictest sense of the rules, but it isn't user-friendly."
1750022,2018-06-29 21:47:27 UTC,"This feature will be included in a new ops repo, being upstreamed in:
https://review.openstack.org/#/c/574882/
https://review.openstack.org/#/c/578963/"
1750025,2019-10-23 15:29:59 UTC,"More discussion at bug 1791662, and a suggested way to disable displayfields for series display.
Josh"
1750025,2019-10-23 15:20:07 UTC,Does anyone have ideas on how this should be fixed?
1750025,2018-02-16 18:35:40 UTC,also attaching screen shot showing marc - 490 and 800 in yellow
1750025,2019-05-28 18:19:55 UTC,Can confirm that this remains an issue in 3.1.
1750025,2019-10-22 20:40:05 UTC,"Hello, we just ran into this issue, I'm assuming this is because of the use of display fields for the search results."
1750031,2018-02-23 14:21:37 UTC,"This bug was reproduced on a xenial Azure cloud image
$ cat /etc/cloud/build.info
build_name: server
serial: 20180222"
1750031,2018-02-23 14:45:48 UTC,"I've also tried a bionic azure image
$ cat /etc/cloud/build.info
build_name: server
serial: 20180222"
1750036,2018-02-25 22:31:49 UTC,"I am thinking about trying:
$ initctl restart unity-panel-service"
1750036,2018-02-20 21:32:25 UTC,"I ran the three sudo commands and then restarted but received an error message after some reloading  occurred: Could not install 'linux-header-4.4.0-78'.  The command 'sudo apt-get install -f' returns dpkg: error: unable to access dpkg status area: Read-only file system as first of three E responses.  There are 6 more W responses and two more E responses.  Wipe and reload?
Hans"
1750036,2018-02-20 16:40:07 UTC,You may need to run the following from a terminal:
1750036,2018-02-16 20:00:03 UTC,This change was made by a bot.
1750046,2018-02-21 12:31:54 UTC,"4.13.0-36.40 - generic
Regression test CMPL."
1750046,2018-02-21 20:32:30 UTC,The package has been published and the bug is being set to Fix Released
1750051,2018-04-01 15:52:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750051,2018-05-05 15:53:12 UTC,submit a patch to add the feature.
1750051,2018-05-05 16:40:48 UTC,"The attachment ""patch.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1750051,2018-05-07 14:35:46 UTC,I looked at the patch (didn't test it) and I think the fprintf call is missing an argument to format as a string. It should read like this IMHO:
1750051,2018-05-08 06:46:10 UTC,"you're right
only adding 6 lines and one bug inside :-("
1750051,2019-01-05 02:42:28 UTC,"Another issue with this is that setting the ""From:"" header to ""root (Cron daemon)"" makes it difficult to forward this mail outside of the system.  Many servers (like gmail) will bounce emails with an improper ""From:"" header."
1750051,2019-01-15 10:05:22 UTC,"It looks I accidentally changed status of this bug from ""Triaged"" to ""Fix Released"" (I clicked ""fix released"" in hope it will take me to the version in which it was fixed, but that wasn't a link, but an update action)."
1750051,2019-01-18 21:04:15 UTC,"to answer #7
if you set an improper value to MAILFROM ok
but if you give to From field a correct value there is no reason to not be forwarded"
1750051,2019-06-14 16:23:59 UTC,CentOS 8 is not out yet so Ubuntu 18.04 is the best LTS for servers at the moment ... except for bugs like this.
1750051,2020-07-02 08:35:28 UTC,a bug report with a patch submitted and no news since one year ... what can we do to make it accepted more quickly ?
1750051,2021-01-06 20:31:50 UTC,I also just ran into a case where this would make my life much easier. Any idea on when we can expect this?
1750052,2018-02-21 18:59:14 UTC,This bug was fixed in the package linux-hwe - 4.13.0-36.40~16.04.1
1750052,2018-02-21 20:31:43 UTC,The package has been published and the bug is being set to Fix Released
1750052,2018-02-21 17:01:38 UTC,Regression tests were successful.
1750052,2018-02-21 04:37:31 UTC,Hardware Certification have begun testing this -proposed kernel.
1750053,2018-02-21 04:37:34 UTC,Hardware Certification have begun testing this -proposed kernel.
1750053,2018-02-22 09:04:36 UTC,Regression tests for linux-hwe 4.13.0-36.40~16.04.1 completed successfully.
1750053,2018-02-22 09:05:57 UTC,Setting automated-testing manually to 'Fix Released' based on the results for linux-hwe 4.13.0-36.40~16.04.1 (bug 1750052).
1750053,2018-02-22 09:18:10 UTC,"4.13.0-36.40~16.04.1 - generic
Regression test CMPL."
1750053,2018-02-22 10:00:28 UTC,The package has been published and the bug is being set to Fix Released
1750057,2018-02-22 14:39:19 UTC,The package has been published and the bug is being set to Fix Released
1750057,2018-02-19 16:39:14 UTC,"I was a bit worried with the config changes there (seemed like more than just the revert of the arm fixes), but smb confirmed for me that these are all wanted. So approving."
1750057,2018-02-22 14:17:30 UTC,This bug was fixed in the package linux-raspi2 - 4.13.0-1014.15
1750059,2018-02-23 13:33:14 UTC,"Yep, I will test that. /var can be tricky because of /var/run, so I'll use a VM for it."
1750059,2018-02-28 08:34:25 UTC,"Small update: I can't get the workaround to reproduce consistently in a VM. While the directories are all mounted as they should and snapd is started and running, snaps still appear ""broken"". I'm investigating further."
1750059,2018-03-07 11:34:00 UTC,The workaround keeps on breaking in a VM. I'm on the point I can't assist further without guidance.
1750059,2018-02-23 12:23:06 UTC,"I expect that if /var or /var/lib are zfs datasets, and you created the homologous .mount units, it would still work."
1750059,2021-02-17 09:07:41 UTC,"I use Ubuntu 20.04 w/ ZFS for the whole system, and for me this still broke despite using zfsutils 0.8. I only have a ZFS dataset for /var, not for /var/lib/snapd—not sure if this contributes to the problem."
1750059,2021-02-17 12:15:48 UTC,"This should no longer be the case? Everything in /etc/zfs/zfs-list.cache/* should be dynamically handled by systemd, does it contain entries for your pool?"
1750059,2019-08-22 22:04:01 UTC,Closing remark: the new systemd generators from upstream zfsonlinux fix this. Version 0.8.x has it (Ubuntu kernel 5.2.0 needed or compile zfs separately).
1750059,2018-02-23 12:12:23 UTC,"Hi, I tried this over noon and I have some good news. The workaround seems successful (I did a few reboots, and snaps did not break again)."
1750059,2018-02-20 08:42:33 UTC,"I'll see if I have that available. ZFS scripts might do things a bit differently, I know there are a few outstanding actions wrt. systemd mount compatibility (""native generators"")."
1750059,2018-02-23 07:51:10 UTC,The problem is this becomes quite breakable when snaps get updated and all. The mount units are specific to a snap version.
1750059,2018-02-22 22:52:26 UTC,"How about: create a OneShot service that just polls to see if the zfs mount is done, and have it be RequiredBy and Before the snap mount units."
1750059,2018-02-22 22:32:43 UTC,I just pinned it down.
1750059,2018-02-22 21:35:19 UTC,Could you run «systemd-analyze plot > /tmp/startup.svg» and attach the resulting /tmp/startup.svg?
1750059,2018-02-22 21:17:13 UTC,"So far no luck. I added a After=local-fs.target to the snapd unit file, but it still appears broken:"
1750059,2018-02-19 12:50:04 UTC,how is the mounting of /var/lib/snapd ordered in relation to starting of snapd?
1750059,2018-02-20 00:02:23 UTC,Having snapd have an After= on the .mount unit that mounts /var/lib/snapd should be enough? I think. I haven't tested this (obviously).
1750059,2018-02-19 21:13:43 UTC,I assume it has to do something with the mount times as well.
1750059,2018-02-23 09:43:45 UTC,"ah! if that'd work, perfect."
1750064,2018-04-20 13:14:28 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1750064,2018-02-22 18:28:02 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc3 release candidate.
1750064,2018-02-22 08:20:30 UTC,"Reviewed:  https://review.openstack.org/546729
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6fcd03d3dbd738024dd8f4c4a34eb7495363e47a
Submitter: Zuul
Branch:    stable/queens"
1750064,2018-02-21 18:32:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/546729"
1750064,2018-02-16 22:43:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545478"
1750064,2018-02-21 22:05:42 UTC,"Reviewed:  https://review.openstack.org/545478
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5754ac0ab3670b47243b2d880aa153a7f42a3ac5
Submitter: Zuul
Branch:    master"
1750069,2018-12-11 14:42:34 UTC,Marked the xenial and bionic tasks as incomplete. Seth gave some guidance but the desktop team needs to respond on how to handle it before anything is done with the seeding.
1750069,2019-07-09 16:26:37 UTC,"Override component to main
xdg-desktop-portal-gtk 1.0.2-0ubuntu0.0 in xenial: universe/gnome -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu0.0 in xenial amd64: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu0.0 in xenial arm64: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu0.0 in xenial armhf: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu0.0 in xenial i386: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu0.0 in xenial powerpc: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu0.0 in xenial ppc64el: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu0.0 in xenial s390x: universe/gnome/optional/100% -> main
8 publications overridden."
1750069,2019-07-09 16:15:50 UTC,"Override component to main
xdg-desktop-portal-gtk 1.0.2-0ubuntu1.1 in bionic: universe/misc -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu1.1 in bionic amd64: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu1.1 in bionic arm64: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu1.1 in bionic armhf: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu1.1 in bionic i386: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu1.1 in bionic ppc64el: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-0ubuntu1.1 in bionic s390x: universe/gnome/optional/100% -> main
7 publications overridden."
1750069,2019-01-29 13:08:30 UTC,(Setting the bug back to Triaged per comment 10)
1750069,2019-01-22 23:03:24 UTC,Security team ACK for promoting xdg-desktop-portal-gtk and xdg-desktop-portal to main for bionic and xenial.
1750069,2018-12-11 03:37:32 UTC,"https://github.com/flatpak/xdg-desktop-portal-gtk/issues/165
https://github.com/flatpak/xdg-desktop-portal-gtk/issues/166
https://github.com/flatpak/xdg-desktop-portal-gtk/issues/167"
1750069,2018-09-04 02:48:04 UTC,"I will probably finish this MIR in ~two weeks, I thought I'd share the notes I've collected so far in case they are useful to anyone:"
1750069,2018-12-07 12:36:09 UTC,@seth-arnold You approved this for cosmic only.  What's the status of getting this approved for bionic and xenial?  Getting this in bionic and xenial would greatly improve the snap desktop support.
1750069,2018-02-23 21:16:36 UTC,"This seems fine from a MIR perspective, but needs a security review."
1750069,2018-02-20 17:52:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750069,2018-12-11 03:13:16 UTC,"Thanks for the reminder Ken, I completely forgot to file issues on the gui backend."
1750069,2018-10-04 16:40:36 UTC,"Override component to main
xdg-desktop-portal-gtk 1.0.2-2 in cosmic: universe/misc -> main
xdg-desktop-portal-gtk 1.0.2-2 in cosmic amd64: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-2 in cosmic arm64: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-2 in cosmic armhf: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-2 in cosmic i386: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-2 in cosmic ppc64el: universe/gnome/optional/100% -> main
xdg-desktop-portal-gtk 1.0.2-2 in cosmic s390x: universe/gnome/optional/100% -> main
Override [y|N]? y
7 publications overridden."
1750069,2018-10-03 04:52:22 UTC,"I reviewed xdg-desktop-portal-gtk version 0.11-1 as checked into cosmic.
This isn't a full security audit but rather a quick gauge of
maintainability."
1750076,2018-02-16 23:00:29 UTC,I see this with multiple versions of Juju including 2.3.2-xenial-amd64
1750079,2018-09-19 08:58:02 UTC,"I think it would also be helpful if subordinates had a way to know whether they are the only charm instances on a machine or not, as behavior might have to be different in the two cases and having to infer that through fs probing is probably not entirely reliable."
1750079,2018-04-09 02:25:04 UTC,"One specific example of this case:  https://bugs.launchpad.net/nrpe-charm/+bug/1750490. We have nova-compute and ceph-osd deployed on the metal of a host (the same one).  We relate nrpe to nova-compute to get the specific monitors from that charm (via the relation).  We then relate nrpe to the ceph-osd to get the ceph monitors.  What that does however is cause the nrpe charm to fall over on the second subordinate, because the first already opened the port.  For NRPE at least, the port conflict is the only reason we have an issue because the charm itself handles the config files gracefully.  Other charms may not be so lucky."
1750079,2018-04-12 05:35:38 UTC,"OK, have had chats with John and Xav around this issue. I think we have come up with a proposed solution that should keep everyone happy."
1750079,2018-02-19 12:44:40 UTC,Tim Penhey <email address hidden> writes:
1750079,2018-02-19 04:49:28 UTC,"I guess the question is what do you expect to happen? We would
a) Omit one of the subordinates (how would we decide which one)?
b) Somehow share the subordinate so it ends up related to both of the
primaries, but only has one actual subordinate running?
c) Prevent the hulk smash because it would cause subordinate conflict
d) make it clearer to charms that they shouldn't expect to be unique on a
machine
e) end-run around it by having machine-level subordinates, rather than
having them associated with a primary charm at all."
1750079,2018-02-18 20:39:39 UTC,There is nothing inherently wrong with two (hulk-smashed) primary units on the same machine having instances of the same subordinate. There is nothing in Juju that should be confused by this.
1750079,2018-02-19 12:48:11 UTC,John A Meinel <email address hidden> writes:
1750082,2019-06-05 07:37:55 UTC,"The last report was in 16.10, that seems to have been fixed in newer versions"
1750084,2018-02-17 00:19:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545494"
1750084,2018-02-21 18:57:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/546740"
1750084,2018-02-21 22:03:35 UTC,"Reviewed:  https://review.openstack.org/545494
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2152f309439a9d9b054a481826242ca15f5c93e
Submitter: Zuul
Branch:    master"
1750084,2018-02-22 13:52:42 UTC,"Reviewed:  https://review.openstack.org/546740
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f0a722d1efd9bb92e2ec5120a3b2091425222393
Submitter: Zuul
Branch:    stable/queens"
1750084,2018-02-22 18:28:01 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc3 release candidate.
1750084,2018-04-20 13:14:26 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1750095,2018-02-17 06:35:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545512"
1750095,2018-08-22 19:17:50 UTC,This issue was fixed in the openstack/cloudkitty 8.0.0 release.
1750098,2020-07-20 10:25:58 UTC,"thank you, closing"
1750098,2020-07-18 17:46:21 UTC,this can be considered fixed
1750098,2018-02-20 20:40:18 UTC,What version of GNOME Software is this?
1750098,2018-02-21 12:54:33 UTC,I'm using gnome-software 3.26.1 on ubuntu 17.10 with latest updates
1750119,2018-02-20 00:03:43 UTC,"It does display a message for a wired interface that is not connected, but does not say anything when an interface is connected. It also does it in a way that is ""jumpy"" per bug 1750114. It probably makes sense to fix the two bugs at the same time."
1750119,2018-03-23 00:21:26 UTC,"> It does display a message for a wired interface that is
> not connected, but does not say anything when an interface
> is connected.
"
1750120,2018-02-17 11:35:58 UTC,For reference I started a mockup at https://docs.google.com/document/d/1Y8WBREexkZij-2e6xg2NEJxELg56McOh3GMf6eQZxRQ/edit#
1750121,2018-05-17 18:54:30 UTC,"@Jens,"
1750121,2018-05-18 08:33:33 UTC,"I still fail to reproduce this locally. Can you describe the steps that are needed to setup your CI environment? Do you see the error only in your CI or also when you follow the steps in [1] manually?
Is this an aio setup or are neutron-api and neutron-bgp-dragent running in different environments? Can you also please check what happens in your setup when using the original 12.0.0 pkgs?"
1750121,2018-05-25 20:09:49 UTC,"@Jens,"
1750121,2018-05-29 23:47:40 UTC,"It looks like this might be mis-tagged verification-failed-bionic, but it's not entirely clear to me. Can someone please confirm that this *does* work on bionic, and then we can release the artful and bionic packages?"
1750121,2018-05-30 06:54:22 UTC,"@Chris: The test were done successfully, I just missed that tag when updating yesterday, sorry. Should be ready to release both artful and bionic, as well as the corresponding UCA updates."
1750121,2018-05-30 16:59:06 UTC,"For Ubuntu, could somebody please confirm the package version strings that were tested for Artful and Bionic? Before I release the tested packages in Artful and Bionic, I want to make sure that what I'm releasing is definitely what was tested, and specifying the package version strings avoids any confusions between UCA, Ubuntu, upstream, etc. You can get the string using the command ""dpkg-query -W neutron-bgp-dragent"" on the test system for example."
1750121,2018-06-07 12:11:04 UTC,I did test 2:11.0.0-0ubuntu2~cloud0 and 2:12.0.0-0ubuntu1.1~cloud0 on Xenial. The packages seem to be identical to those in Artful and Bionic.
1750121,2018-06-11 07:49:38 UTC,"For the SRU verification to be valid, we need testers to test the exact same binaries that are supposed to be released into -updates. The reason for that is that the build environment can be different for different binaries, even though the sources might be the same. The build environment can then influence the actual behavior and cause regressions, which already happened a few times before."
1750121,2018-06-11 09:34:58 UTC,"I successfully use neutron-dynamic-routing-common, python-neutron-dynamic-routing and neutron-bgp-dragent in version 2:12.0.0-0ubuntu1.1 (from bionic-proposed) on bionic to provide BGP peerings with Neutron network routes."
1750121,2018-06-13 09:38:25 UTC,"The verification of the Stable Release Update for neutron-dynamic-routing has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1750121,2018-06-13 09:48:29 UTC,This bug was fixed in the package neutron-dynamic-routing - 2:12.0.0-0ubuntu1.1
1750121,2018-06-13 10:28:17 UTC,"If it needs testing in artful in order to get fixes into Pike UCA, then IMO your process is broken. I think I spent more than enough time on this, if you insist to prefer keeping to distribute faulty packages, so be it."
1750121,2018-06-14 12:50:17 UTC,The verification of the Stable Release Update for neutron-dynamic-routing has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1750121,2018-06-14 12:50:20 UTC,"This bug was fixed in the package neutron-dynamic-routing - 2:12.0.0-0ubuntu1.1~cloud0
---------------"
1750121,2018-06-25 13:49:39 UTC,Marking Artful as Won't Fix since it's nearly EOL.
1750121,2018-06-25 13:50:42 UTC,The verification of the Stable Release Update for neutron-dynamic-routing has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1750121,2018-06-25 13:50:44 UTC,"This bug was fixed in the package neutron-dynamic-routing - 2:11.0.0-0ubuntu2~cloud0
---------------"
1750121,2018-05-09 13:45:14 UTC,"@Dr. Jens, Thanks for testing. I'd prefer the user manually restart neutron-server. It doesn't feel right to have neutron-dynamic-routing postinst do a restart of neutron-server."
1750121,2018-06-13 09:36:55 UTC,Thank you for the testing. I will release 2:12.0.0-0ubuntu1.1 from bionic-proposed to bionic-updates based on this result.
1750121,2018-05-09 13:28:34 UTC,@David: Did you also restart neutron-server after upgrading the neutron-dynamic-routing packages? Omitting that step was the only way I could reproduce your error during my testing on bionic.
1750121,2018-02-19 09:56:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545783"
1750121,2018-05-07 19:59:33 UTC,I've tagged the verification of this bug as failed since restart of neutron-bgp-dragent results in a missing auth_type when attempting to recreate the peer. add_bgp_peer_to_bgp_speaker() gets a KeyError exception for 'auth_type' as can be seen in David's results in the previous comment.
1750121,2018-05-08 21:04:42 UTC,"@David: I have not been able to reproduce the error on xenial with queens UCA. Your logs look like you are running without the patch applied. Can you doublecheck that you did install the patched packages? Can you set ""debug=true"" in /etc/neutron/bgp_dragent.ini and post logs from that?"
1750121,2018-03-21 22:12:04 UTC,This makes BGP essentially useless after the Neutron agent (container in my case) reboots in stable/pike installed by Openstack Ansible. Please merge the patch into Neutron so it can be cherry-picked to Neutron's stable/pike branch so the sha's can be bumped to snag it.
1750121,2018-03-22 06:12:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/555162"
1750121,2018-03-22 06:39:19 UTC,"Reviewed:  https://review.openstack.org/545783
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=fd497a491afec89d4a15cf061b5d5610fb7ad6d2
Submitter: Zuul
Branch:    master"
1750121,2018-03-29 16:26:18 UTC,"Reviewed:  https://review.openstack.org/555162
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=c1914078fc2d75ca18e875cdc55a3ee49a9bcd9c
Submitter: Zuul
Branch:    stable/pike"
1750121,2018-04-08 10:20:17 UTC,"Reviewed:  https://review.openstack.org/555161
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=a29018ba87b18828c52326030413bc5e55f3668b
Submitter: Zuul
Branch:    stable/queens"
1750121,2018-04-19 14:11:34 UTC,This issue was fixed in the openstack/neutron-dynamic-routing 13.0.0.0b1 development milestone.
1750121,2018-04-24 18:08:03 UTC,This issue was fixed in the openstack/neutron-dynamic-routing 11.0.1 release.
1750121,2018-04-24 18:17:43 UTC,This issue was fixed in the openstack/neutron-dynamic-routing 12.0.1 release.
1750121,2018-03-22 06:12:09 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/555161"
1750121,2018-05-03 19:28:34 UTC,This bug was fixed in the package neutron-dynamic-routing - 2:12.0.0-0ubuntu2
1750121,2018-05-03 20:19:09 UTC,"Hello Dr., or anyone else affected,"
1750121,2018-05-03 20:55:33 UTC,"Hello Dr., or anyone else affected,"
1750121,2018-05-04 09:39:00 UTC,"@Corey: There are releases 11.0.1 and 12.0.1 containing the patch, so I don't understand why you cherry-picked it instead of using the new releases."
1750121,2018-05-04 12:39:01 UTC,"Hello Dr., or anyone else affected,"
1750121,2018-05-04 16:12:12 UTC,"Hello Dr., or anyone else affected,"
1750121,2018-05-04 16:30:06 UTC,"@Jens, we just don't have full test coverage for neutron-dynamic-routing quite yet on our end so I was trying to keep the stable delta to a minimum. If by any chance you could test corresponding releases for us then I can prepare some stable point releases."
1750121,2018-05-07 17:55:44 UTC,I still see this failure when the neutron-bgp-dragent is restarted.
1750121,2018-05-07 07:40:56 UTC,"Ah, o.k., well for stable/pike this is actually the only patch from 11.0.0 to 11.0.1, so maybe we can keep your version there, except that it may be confusing to users."
1750121,2018-05-03 12:45:26 UTC,"I've uploaded new versions of neutron-dynamic-routing with the cherry-picked patch to cosmic, bionic, and artful where the package is awaiting acceptance from the unapproved queues:"
1750122,2018-03-06 08:37:29 UTC,"Reassigning, there's no way gnome-terminal could ask gtk to do this. Must be a gtk bug."
1750124,2018-02-20 00:20:37 UTC,"Interesting idea. In the long run we want to support iscsi mounts which will require having the network up before partitioning. I'm also not quite sure how to implement this, it might require us to be much more involved in how curtin executes rather than just generating a config and handing if off, which is not necessarily a bad thing just a bit trickier to do."
1750125,2019-11-13 21:17:05 UTC,"subiquity does geoip lookup and uses CC.[archive|ports].ubuntu.com as the default value as xnox suggests. Is there anything else we want to do here, even as a wishlist item? I'm inclined to say no."
1750125,2018-07-22 23:07:27 UTC,"You can specify a mirror now but all the other cleverness has not been implemented, and seems a bit less essential, so I'll retitle and reprioritize the bug."
1750125,2019-04-02 21:50:19 UTC,"launchpad already has a list of mirrors per country, including tests for completeness and currency. I wouldn't want to duplicate that client side. Granted, the mirrors completeness and currency in launchpad is only for archive.ubuntu.com; and not ports. There is currently no facility in launchpad to register, and probe/check ports archives."
1750129,2018-03-15 19:01:50 UTC,"I traced this back to an issue in ryu, see https://sourceforge.net/p/ryu/mailman/message/36260483/ .
This issue only happens when the agent is not able to establish a BGP session to the peer. When the BGP session is connected while the speaker is being removed, https://bugs.launchpad.net/bugs/1750383 is triggered instead."
1750137,2018-02-20 00:15:22 UTC,"On the implementation side, subiquity generates netplan which supports interface renaming, so subiquity doesn't need to sweat the details. Most of the work will be making the UI nice."
1750139,2018-02-17 13:12:20 UTC,"StacktraceTop:
 IceProcessMessages (iceConn=0x563feb03a9e0, replyWait=replyWait@entry=0x0, replyReadyRet=replyReadyRet@entry=0x0) at ../../src/process.c:175
 client_iochannel_watch (channel=<optimized out>, condition=<optimized out>, client=0x563feb0299c0) at gsm-xsmp-client.c:84
 g_main_dispatch (context=0x563feb013350) at ../../../../glib/gmain.c:3177
 g_main_context_dispatch (context=context@entry=0x563feb013350) at ../../../../glib/gmain.c:3830
 g_main_context_iterate (context=0x563feb013350, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3903"
1750141,2018-02-17 14:11:59 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x7eff7c691367 ""Gtk"", file=file@entry=0x7eff7c70bdd0 ""../../../../gtk/gtktreestore.c"", line=line@entry=1220, func=func@entry=0x7eff7c70c4f0 <__func__.37258> ""gtk_tree_store_remove"", message=message@entry=0x55cf172908e0 ""assertion failed: (parent != NULL)"") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x7eff7c691367 ""Gtk"", file=file@entry=0x7eff7c70bdd0 ""../../../../gtk/gtktreestore.c"", line=line@entry=1220, func=func@entry=0x7eff7c70c4f0 <__func__.37258> ""gtk_tree_store_remove"", expr=expr@entry=0x7eff7c6ec2b7 ""parent != NULL"") at ../../../../glib/gtestutils.c:2459
 gtk_tree_store_remove (tree_store=0x55cf172c7ef0, iter=0x55cf16075000) at ../../../../gtk/gtktreestore.c:1220
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x55cf17ce90c8, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffcf2062418, avalue=<optimized out>) at ../src/x86/ffi64.c:525"
1750141,2019-01-16 22:22:59 UTC,https://errors.ubuntu.com/problem/edc91a5e55a32a4483bcf051a36a7c7b8123cbf3
1750146,2020-05-09 08:11:54 UTC,"I have the latest Ubuntu 20.04 and it also seems to have this bug. There are workarounds, but I think it should work out of the box like it does on Windows. It is weird to have this kind of bug as Xbox One controller might just be the most popular controller and these kinds of issues prevent people from gaming on Linux."
1750146,2020-09-23 09:41:16 UTC,"Yeah, it seems to get worse with every 5.4 LTS update. Worked almost flawless about some months ago (despite taking something from 30-60s to successfully connect). But I don't see a correlation to any commits. But now, it's almost impossible to connect successfully, it usually disconnects after a 1-2 minutes (coincidentally just when entering a game)."
1750146,2020-08-17 14:00:26 UTC,"Correcting my previous post: doesn't work with lts 5.4 anymore. Seems to be rare occasion that i got it to pair succesfully with 5.4, after that it connected normally with even 5.7 and 5.8. Then suddenly again doesn't connect or pair properly with any of those."
1750146,2020-08-17 13:12:21 UTC,Same issue in Arch linux kernel 5.8.1. Worked fine before with xpadneo or xpad driver if disabled bluetooth ertm. Works properly with lts kernel (5.4.58) so regression happened somewhere between 5.4 and 5.8. Systemctl status bluetooth spams this:
1750146,2020-08-12 14:09:26 UTC,"Can confirm this still happens with kernel 5.8.1. While the device is listed correctly with its full name in bluetoothctl and can be trusted, the final pairing will not work. syslog will constantly have a ""Refusing...."" message for the device and the connection:"
1750146,2020-06-05 20:42:57 UTC,Same issues with Ubuntu 20.04 LTS with the 5.7.0 Kernel.
1750146,2019-09-01 18:48:46 UTC,Same problems experienced on 19.04 Ubuntu.
1750146,2020-09-23 09:46:58 UTC,Dear sender!
1750146,2018-05-09 17:39:08 UTC,I'm using this workaround as a permanent solution. (while waiting for kernel patches for this problem)
1750146,2018-05-03 01:07:37 UTC,I've tried on Ubuntu 18.04 LTS and I'm still getting the same issues.
1750146,2018-05-03 01:06:48 UTC,I've tried on Ubuntu 18.04 LTS and I'm still getting the same issues.
1750146,2018-04-28 05:14:47 UTC,"And PS: Sorry, I just now saw the fix is only temporary."
1750146,2018-04-28 05:14:09 UTC,"Thank you for the update, Andre.
Has anyone had a chance to try this fix?"
1750146,2018-04-19 18:24:05 UTC,Hello Guys!
1750146,2018-02-24 15:44:25 UTC,"** SEE THE ORIGINAL BUG REPORT IN LAUNCHPAD HERE:
https://bugs.launchpad.net/gnome-control-center/+bug/1750146 **"
1750146,2018-02-17 14:32:25 UTC,Screenshot
1750146,2019-02-08 04:39:31 UTC,No fix yet?
1750155,2018-07-14 14:27:00 UTC,closing dup
1750155,2018-06-11 22:13:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750155,2018-05-26 09:51:19 UTC,"Hello folks,"
1750155,2018-05-25 23:31:58 UTC,"So, can we close this as dupe?"
1750155,2018-02-20 03:02:53 UTC,Why not add this feature by default into Wine?
1750155,2018-02-17 15:44:13 UTC,"(In reply to Nikolay Sivov from comment #2)

> This sounds like a duplicate of bug 40613.
"
1750155,2018-02-17 15:22:47 UTC,This sounds like a duplicate of bug 40613.
1750155,2018-02-17 15:21:31 UTC,"Created attachment 60490
Screenshot"
1750155,2018-02-17 15:20:01 UTC,Debugging output text from PlayOnLinux and Wine
1750155,2018-02-17 15:17:36 UTC,"Created attachment 60489
Open Debugging Info in a Text Editor"
1750155,2018-02-17 16:05:38 UTC,"(In reply to jebeld17 from comment #3)

> (In reply to Nikolay Sivov from comment #2)
> > This sounds like a duplicate of bug 40613.
>
> I tried the fixes mentioned within and nothing worked.
"
1750165,2021-01-12 17:24:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750165,2021-01-12 17:25:51 UTC,This affects me with kernel 5.8.0-36-generic and Ubuntu 20.10.
1750180,2019-07-09 00:49:32 UTC,"Things to note, feature should"
1750180,2019-07-09 23:18:23 UTC,"Wayne please put back the status to New, there are no opinions in the Description of this RFE, everything there is verifiable fact"
1750180,2019-07-10 12:28:26 UTC,"@efa ""Let KiCAD be professional"" is an opinion.  Relational databases do not make an EDA professional.  The ""Opinion"" status in launchpad is defined as ""Doesn't fit with the project, but can be discussed.""  Using a database to store symbols has been dismissed in the past by the development team as unnecessary overhead.  Once Python support is implemented for the schematic editors, it will be fairly easy to implement your own database support but it's not something that KiCad is likely to provide.  So given that I set the status to ""Opinion"", I'm willing to discuss the idea.  Otherwise I would have set the status to ""Wont Fix""."
1750180,2019-07-10 23:23:17 UTC,"OK thank you. Take care that already now the 'database' of components supplied by KiCAD is similar/bigger than other professional EDA libraries, and big enough to be fitted in a real DB.
Continue to keep the library of parts locally on designer HDD, and editable, can be really undesired when parts number become so high. Normally company prefer to keep validated parts (scheme symbol is right, not out of production, in preferred parts list, other policy) under control on external server. DB is a good choice, sure not the only one."
1750180,2019-07-10 23:37:46 UTC,"if needed, I can describe how exactly work the placing of parts, synch of parts and validation of parts with OrCAD Capture+CIS with a DB"
1750181,2020-08-30 18:30:41 UTC,"I can't reproduce in pcb v4.2.2-12-ge18755b, see attached screenshots."
1750191,2018-02-19 17:20:45 UTC,"Thanks for letting us know, Chris!"
1750191,2018-02-19 07:56:29 UTC,"hhis bug has been temporarily fixed by reverting Tav's changes (reverted by Tavmjong).
I'm leaving the bug open in case it helps him troubleshoot the issue. Update to fix the issue."
1750191,2018-02-18 12:09:26 UTC,"I believe this is the way that the operation is intended to behave, see:"
1750191,2018-02-19 01:42:00 UTC,"Confirmed, I, too get only a fill instead of the shape of the stroke."
1750191,2018-02-19 04:32:34 UTC,"attached is a demo of what I get from Stroke-to-Path using Windows 10 and Inkscape 0.92+devel (9d6b0e8, 2018-02-18)"
1750192,2018-02-18 09:22:22 UTC,"I don't see how openstack-manuals is relevant here - marking as invalid. If you have a specific place that should be updated, please tell us."
1750193,2018-02-18 12:35:11 UTC,"- problem not reproduced on Windows 10, Inkscape 0.92+devel (9d6b0e8, 2018-02-18)
- attached is the drawing I had after step 6"
1750193,2018-02-18 12:36:50 UTC,attached is what I get after step 7
1750193,2018-02-18 16:15:29 UTC,Tav reverted a previous commit that has fixed it temporarily. I'm going to leave the bug open for now in case it helps him track down the problem. Thanks for the work everyone!
1750199,2018-02-19 23:05:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750216,2018-02-19 01:21:31 UTC,Inkscape uses RGB colorspace.
1750216,2018-02-19 03:40:01 UTC,"Hi TylerDurden,"
1750216,2018-02-19 17:23:27 UTC,Does it work correctly when you change the color in Illustrator?
1750216,2018-02-19 20:30:44 UTC,"If I change the color mode in Illustrator, no warning pops out when I copy the equations to Illustrator. It looks fine in Illustrator interface as well. The problem only occurs when I export to PDF."
1750216,2020-03-25 08:41:50 UTC,Sounds like a bug in Illustrator (otherwise: Why would it look correctly in Illustrator interface?).
1750220,2018-02-19 11:40:40 UTC,"radial gradient problem confirmed on Windows 10, Inkscape 0.92+devel (9d6b0e8, 2018-02-18)"
1750220,2018-02-19 09:12:05 UTC,Here is svg file
1750220,2018-02-19 09:12:50 UTC,Here is xaml file
1750224,2020-05-09 07:04:57 UTC,"Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   QtCore                        	0x000000010ade8e6b QMutex::lock() + 11
1   org.mixxx.mixxx               	0x000000010a6b7ab7 0x10a106000 + 5970615"
1750224,2020-05-09 07:07:01 UTC,Does this still happen with Mixxx 2.2?
1750224,2020-05-10 18:16:59 UTC,Tried to reproduce but was unable to. Closing as fix released
1750228,2018-02-18 13:39:54 UTC,"This is my
lspci -v | grep -A7 -i ""audio""
output:"
1750231,2019-10-04 04:26:47 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1750243,2019-06-20 03:55:23 UTC,any update on this issue current version snap still does not include StartupWMClass have to manually add StartupWMClass=chromium in /var/lib/snapd/desktop/applications/chromium_chromium.desktop
1750243,2019-08-07 12:55:26 UTC,Fixed with https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=02e1a3b458a1edef2307278880337e8e494d5569.
1750243,2019-08-07 12:44:24 UTC,"I tested again, and while I can confirm that the chromium snap cannot be pinned to the favorite apps in a Fedora 29 VM without the ""StartupWMClass=chromium"" line in its desktop file, Ubuntu doesn't seem to be affected. I tested bionic and eoan, in the alternative gnome-session, which has defaults similar to Fedora."
1750243,2018-11-16 19:03:41 UTC,"Note that the fact that ""Create shortcut"" doesn't work in the snap is a known issue: bug #1732482."
1750243,2018-02-23 17:04:35 UTC,"I cannot observe the issue on Ubuntu 18.04. I can pin the chromium snap icon to the launcher, both in the Ubuntu and GNOME sessions, and clicking that icon matches the newly-created window to the icon."
1750243,2018-10-17 18:41:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750243,2018-02-24 13:04:02 UTC,And Fedora (in VM)
1750243,2018-02-23 19:12:02 UTC,Solus
1750243,2018-10-17 19:01:06 UTC,I've got the same issue in the Ubuntu 18.10 beta.
1750253,2018-02-18 16:12:31 UTC,"StacktraceTop:
 g_mutex_clear (mutex=mutex@entry=0x55bb6889e090) at ../../../../glib/gthread-posix.c:1307
 bus_dbus_impl_destroy (dbus=0x55bb6889e030) at dbusimpl.c:635
 g_closure_invoke (closure=0x55bb68893050, return_value=0x0, n_param_values=1, param_values=0x7ffc53ece290, invocation_hint=0x7ffc53ece210) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55bb688930a0, detail=detail@entry=0, instance=instance@entry=0x55bb6889e030, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc53ece290) at ../../../../gobject/gsignal.c:3673
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc53ece450) at ../../../../gobject/gsignal.c:3391"
1750253,2018-04-16 19:41:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750262,2018-02-18 22:51:26 UTC,"Even after purge/reinstall of PCManFM and related desktop packages, resetting the values in config files to default, the issue still persists. Same error:"
1750262,2020-04-17 05:10:01 UTC,"Desktop Manager Not Active !
Same story: Lubuntu 18.04 (same problem)! Desktop Manager Not Active , Everything on the desktop disappears! Only LogOFF fixes things."
1750262,2020-04-17 05:30:19 UTC,Thank you for reporting this bug to Ubuntu.
1750264,2020-08-17 11:54:06 UTC,It's fixed now in https://launchpad.net/ubuntu/+source/libcdio-paranoia/10.2+2.0.0-1
1750264,2018-05-16 20:14:51 UTC,For anyone who wants a fix independent from Ubuntu maintainers action:
1750264,2018-04-14 12:46:47 UTC,The solution would be to just set the binary to be installed in the install file. Independent from the decision of deb multimedia. Workable solution with the least amount of effort.
1750264,2018-03-09 15:43:22 UTC,looking at deb multimedia there they decided to create a new file
1750264,2018-03-09 15:36:17 UTC,"Actually quite simple, no one set the binary to be installed in libcdio-paranoia2.install file
i.e.
usr/lib/*/libcdio_paranoia.so.*
usr/bin/*"
1750264,2018-03-09 14:09:27 UTC,"Well it appears it's been moved out of libcdio & the binary is no longer built
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888053"
1750264,2018-03-09 13:59:07 UTC,"so libcdio17 is broken on audio cd's (- https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644
 And now the cd-paranoia binary is missing.
What's going on??"
1750264,2018-03-09 16:23:34 UTC,"What i should of said is a new package for cd-paranoia, can't see ubuntu doing that for 18.04.."
1750266,2018-05-06 17:37:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750269,2018-02-18 22:58:45 UTC,"Can you go over some details of what you were doing that led to this error? At first glance, it seems very closely related to bug 1741447. Before marking this one as a duplicate, I want to ensure it is about the same thing."
1750269,2020-08-18 04:17:17 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1750278,2018-02-18 20:24:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1750278,2018-05-09 18:39:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750278,2018-05-09 19:10:27 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1750280,2019-11-20 04:17:23 UTC,[Expired for snapd because there has been no activity for 60 days.]
1750280,2019-09-20 08:16:37 UTC,On second thought I'm switching the status to incomplete because it's not one of the packages we maintain directly and it does feel like something that is related to packaging more to snapd bugs.
1750280,2019-09-20 08:13:56 UTC,Hello.
1750282,2018-02-20 01:22:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750282,2018-03-02 09:35:16 UTC,This error occurred during system upgrade.
1750287,2018-02-19 01:16:29 UTC,The output of `ubuntu-bug sound-juicer` is attached.
1750287,2018-02-19 20:28:18 UTC,The only relevant output of ```derrell@derrell:~/INSTALLS$ sound-juicer --gst-debug=all
1750292,2018-02-21 10:45:40 UTC,"After testing, in F5 HUD window there is dynamic braking, but no sound."
1750293,2018-05-13 00:19:19 UTC,"I just experienced the bug described. I then followed the steps listed above in the update, but continued to experience the bug described. See below:"
1750325,2018-04-13 13:46:33 UTC,I'm on `4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux` and this bug has only started since more recent versions of 4.13.
1750325,2018-02-19 08:24:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1750325,2018-04-13 13:37:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750330,2018-02-19 15:43:54 UTC,"Setting enable_neutron_dvr: ""no"" did the job.
It appears that enable_neutron_dvr: ""no"" is not working in all-in-one deployments."
1750330,2018-02-19 15:44:45 UTC,"It appears that enable_neutron_dvr: ""yes"" is not working in all-in-one deployments."
1750330,2018-02-19 15:48:32 UTC,"Having set:
enable_neutron_provider_networks: ""yes""
enable_neutron_dvr: ""no"""
1750330,2018-11-19 21:15:53 UTC,"all-in-one deployment ,
This in globals.yml does not fix the problem:
enable_neutron_provider_networks: ""yes""
enable_neutron_dvr: ""no"""
1750333,2018-04-21 14:24:41 UTC,"Reviewed:  https://review.openstack.org/561652
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=7bfd0ba69ca37a87978d653eb65d710aa5f4776c
Submitter: Zuul
Branch:    stable/queens"
1750333,2018-04-16 15:37:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561652"
1750333,2018-03-27 21:45:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557067"
1750333,2018-03-27 21:43:02 UTC,"Basically, it looks like the db repo is not initialized for the listener.  I have a fix - working on functional tests to make sure we test it in the gate."
1750333,2018-04-12 18:53:54 UTC,"Reviewed:  https://review.openstack.org/557067
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=7061d65ca934875da9a9e4956bd105c97a47137c
Submitter: Zuul
Branch:    master"
1750336,2018-02-19 09:02:41 UTC,Please try changing your password to purely US English characters and tell us if that works around the bug. I am reminded of similar bug reports such as bug 1566357 and bug 1716159.
1750336,2018-02-19 09:57:12 UTC,My passwords are all english and 0-9 combinations.
1750336,2018-02-20 05:28:26 UTC,"I did further investigation。 The reason is that, when using Nvdia-340.104 driver, I am not able to type any UPPERCASE letters using the CapsLk key. I discovered this when I click the ""Not listed?"" link and then type letters in the username input field. All appercase letters are accepted as lowercase only."
1750336,2018-02-20 05:42:09 UTC,"Sounds like this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=772866"
1750336,2018-08-15 03:56:01 UTC,This may turn out to be one of the login bugs we fixed in 18.04 recently so...
1750345,2018-02-28 12:12:04 UTC,"Thanks for your bug report.  The installation documentation has been reworked in Pike, and the error is fixed there.  I just proposed a patch for stable/ocata."
1750345,2018-03-02 16:07:21 UTC,"Reviewed:  https://review.openstack.org/548574
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=301f52681d8dc0802ff093526e2647cf2b034f6c
Submitter: Zuul
Branch:    stable/ocata"
1750348,2018-02-19 14:56:53 UTC,I found the problem... I had to install and configure support for Audio.
1750353,2018-06-26 15:53:32 UTC,We can't backport it to stable branches as it cause issues with some stadium projects
1750353,2018-06-19 01:01:42 UTC,"Reviewed:  https://review.openstack.org/573617
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=75d08e2b0c44859c55152fbadeb5e23204aeee4b
Submitter: Zuul
Branch:    stable/queens"
1750353,2018-06-18 23:45:28 UTC,"Reviewed:  https://review.openstack.org/573620
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ce13674afdc1888616b488562cca9f6fba2dc0d2
Submitter: Zuul
Branch:    stable/ocata"
1750353,2018-06-08 08:34:41 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/573620"
1750353,2018-02-19 11:09:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545799"
1750353,2018-06-08 08:32:38 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/573617"
1750353,2018-06-27 10:05:35 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/573618
Reason: as we had to revert it from Queens we will not backport it also here"
1750353,2018-03-12 07:59:50 UTC,"Reviewed:  https://review.openstack.org/545799
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d5f27524819bc95530d0d5856782546fd02d65f8
Submitter: Zuul
Branch:    master"
1750353,2018-06-08 08:33:08 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/573618"
1750353,2018-09-18 14:09:01 UTC,This issue was fixed in the openstack/neutron 12.0.4 release.
1750353,2018-04-19 14:13:29 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b1 development milestone.
1750365,2018-04-13 06:06:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750365,2018-04-13 06:07:57 UTC,Agreed.
1750368,2018-02-19 13:25:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/545826"
1750368,2018-02-20 15:51:27 UTC,"HTML rendering of the specs, PS4:"
1750368,2018-05-16 20:42:11 UTC,"Reviewed:  https://review.openstack.org/545826
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=2a34abbd25444a1d643324dafe762131e6c0a18c
Submitter: Zuul
Branch:    master"
1750368,2018-08-31 14:44:30 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/598986"
1750368,2019-02-28 15:10:12 UTC,"Reviewed:  https://review.openstack.org/598986
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=c97f096695dbceb68fcdb6b07b33f0651bc34bfd
Submitter: Zuul
Branch:    master"
1750368,2020-03-19 15:26:18 UTC,"Due to lack of activity neutron-interconnection project was some time ago moved from Neutron stadium to the x/ namespace.
So I think that we can close this RFE as ""abandoned"" now."
1750371,2019-10-15 11:52:33 UTC,"This looks like a bug in maas, not snapd."
1750371,2019-10-15 13:04:05 UTC,Are you re-initializing or on fresh install you hit this issue?
1750372,2019-12-20 15:14:28 UTC,This was introduced with the fix for https://bugs.launchpad.net/python-jenkins/+bug/1659787.
1750372,2020-03-04 02:58:40 UTC,"Reviewed:  https://review.opendev.org/700196
Committed: https://git.openstack.org/cgit/jjb/python-jenkins/commit/?id=19e7f7395aaa0d876a39baf82a80b775d17ff2b3
Submitter: Zuul
Branch:    master"
1750376,2018-03-22 09:25:13 UTC,This bug was fixed in the package ceph - 12.2.4-0ubuntu1
1750376,2018-03-29 18:20:44 UTC,"Hello Dr., or anyone else affected,"
1750376,2018-03-19 12:35:53 UTC,Pushed to ubuntu/bionic; will be included in 12.2.4 upload.
1750377,2018-03-05 09:14:23 UTC,seems thus bug is not related to glance. Are you using vagrant (https://github.com/chef/bento/issues/665)?
1750383,2018-03-15 18:22:58 UTC,"It sounds this bug doesn't affect operations, just an annoying log message. Setting importance to Low."
1750383,2018-03-15 18:59:08 UTC,"Actually I traced this back to an issue in ryu, see https://sourceforge.net/p/ryu/mailman/message/36260483/ . A workaround might be to explicitly remove all peers (in the ryu driver) before shutting down the speaker, but I'd be fine with waiting for this to be fixed in ryu, too."
1750385,2018-03-03 13:27:47 UTC,I did not find the option to not even power the bluetooth adapter as I can in KDE but turning bluetooth off did not seem to change the wifi behavior.
1750385,2018-03-14 04:40:47 UTC,Can you attach kernel config on Manjaro?
1750385,2018-03-27 12:55:05 UTC,Unfortunately I am not able to find the configuration file in Manjaro. I looked into /usr/src/ but this folder is completely empty. I also tried locating it via find -type f -name '.config' but this only found my Linux Mint Kernel configurations.
1750385,2018-03-29 09:25:08 UTC,"Ahm... I can try. Never built one before and I'm not sure how well my broken Manjaro installation will cope with that. But I can definitely try it...
Do you happen to have instructions somewhere on how to build a kernel yourself?"
1750385,2018-03-28 15:22:24 UTC,Here it is
1750385,2018-03-02 04:13:59 UTC,"Please do check that, thanks!"
1750385,2018-04-10 16:16:24 UTC,"This Problem persist at kernel 4.13.0.32 i report the same problem in all kernels
4.13.0.36 - Bug Report #1751622
4.13.0.37 - Bug Report #1757548"
1750385,2018-03-27 13:49:21 UTC,Proably `zcat /proc/config.gz` will do.
1750385,2018-03-01 17:30:34 UTC,I have the bluetooth adapter powered off in Manjaro but I also have it powered off in Mint (I did not check the bluetooth state in the live ubuntu-image on the USB though).
1750385,2018-03-29 08:52:37 UTC,"Interesting.
Maybe CONFIG_RTLWIFI_DEBUG=y workaround the issue? The value is not set on Ubuntu."
1750385,2018-02-28 11:09:24 UTC,So I installed the linked image on a USB and booted that up.
1750385,2018-03-01 03:07:11 UTC,Do you enable Bluetooth in Manjaro? This might be yet another WiFi/BT coexist bug...
1750385,2018-02-19 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1750385,2018-02-19 19:14:14 UTC,Added requested (log)-files
1750385,2018-02-21 09:46:18 UTC,I installed the linked kernel and the wifi still wasn't working (though with antenna 1 it didn't even find the wifi in the first place and with antenna 0 it wouldn't connect (the signal was really really bad though) so it almost seems as if the problem is even worse than with the 4.13. Though that could just be coincidence).
1750385,2018-02-20 18:53:54 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1750385,2018-02-24 14:19:10 UTC,"@Kai-Heng Feng
So I went through the -rc* kernels and I found the 4.11-rc8 working just fine whereas the wifi broke down with 4.12-rc1."
1750385,2018-02-25 15:08:23 UTC,Do you see the same issue on Bionic daily image in http://cdimage.ubuntu.com/daily-live/current/ ?
1750385,2018-02-25 19:46:20 UTC,"Do you want me to put that on a USB/CD, boot from that and check how the wifi is doing?"
1750385,2018-02-22 09:56:48 UTC,"Please find the first bad -rc* kernel between v4.10 to v4.13 from [1] that has this issue, thanks."
1750385,2018-02-28 08:15:06 UTC,Yes. Of course a reusable media is preferable...
1750386,2018-02-19 14:46:36 UTC,When done on the openstack provider:
1750386,2018-02-19 14:58:27 UTC,If I then try to `juju bootstrap...` again on the ubuntu unit:
1750386,2018-02-19 14:58:46 UTC,"FTR, I don't necessarily expect this to work or be advisable, it is a bug to represent one way that we have discovered that we can create a problem for ourselves.  As such, someone else will likely try the same eventually, and maybe juju can guard against it more thoroughly."
1750386,2018-02-19 20:00:27 UTC,The check should be earlier prior to damaging an existing system.
1750390,2018-02-22 20:19:37 UTC,The error in the log is:
1750391,2018-02-19 18:53:35 UTC,"And, just to clarify, multiple bibs will use a single (unique) browse entry.  That table is a list of unique strings, and the mapping table(s) identify which records use each and how each is used."
1750391,2018-02-19 18:22:28 UTC,"So a little hiccup to this, is it looks like authority entries will not have a corresponding def_map entry, so just doing a blanket test for any browse_entrys that do not have def_maps is not going to work if you are using authorities."
1750393,2018-02-19 18:43:21 UTC,"The warning string in the Xorg.0.log, ""flip queue failed"", is found in the following driver:
/usr/lib/xorg/modules/drivers/radeon_drv.so
found in package: xserver-xorg-video-radeon-hwe-16.04"
1750393,2018-02-19 18:59:25 UTC,"Specifically, the source file:"
1750393,2018-02-19 19:01:24 UTC,"I'll ""gdb attach"" the Xorg process next and see if I can't get some runtime data."
1750393,2018-02-19 19:24:51 UTC,"Okay, a little code inspection leads to one of these two function calls failing at line 3062:"
1750393,2018-02-19 19:27:25 UTC,Line 3039 in the source can also cause the message:
1750393,2018-02-23 16:35:55 UTC,This issue has a workaround:
1750393,2018-03-16 15:05:34 UTC,I filed similar bug https://bugs.launchpad.net/ubuntu/+source/compton/+bug/1756354
1750393,2018-02-19 15:45:00 UTC,"I think something is hosed with the radeon driver in mesa 17.2.8, but I can't find the 17.2.4 pkgs to roll back and test the theory.  The 17.2.4 was pulled from updates and proposed lines.  I'm hesitant to rollback to 11.2."
1750393,2018-02-19 18:50:19 UTC,"Source of warning message from radeon_drv.so:
./src/drmmode_display.c:	xf86DrvMsg(scrn->scrnIndex, X_WARNING, ""flip queue failed: %s\n"",
./src/radeon_kms.c:	xf86DrvMsg(scrn->scrnIndex, X_WARNING, ""flip queue failed in %s: %s\n"",
./src/radeon_kms.c:	xf86DrvMsg(scrn->scrnIndex, X_WARNING, ""flip queue failed in %s: %s, """
1750395,2018-02-19 18:25:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/545946"
1750395,2018-11-19 20:44:20 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.2 release.
1750395,2018-11-19 20:51:39 UTC,This issue was fixed in the openstack/python-openstackclient 3.14.3 release.
1750395,2019-03-08 04:20:31 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1750395,2019-05-08 13:58:14 UTC,"Dear colleagues,"
1750395,2019-05-08 13:59:23 UTC,Continue and My template was that.
1750403,2018-02-20 21:32:49 UTC,During boot there are these lines
1750403,2018-02-21 09:26:02 UTC,"On Tue, Feb 20, 2018 at 09:32:49PM -0000, Jean-Baptiste Lallement wrote:

> The journal is already attached in comment #2
"
1750403,2018-03-27 15:19:43 UTC,"Originally it was 1GB. I think the increased memory usage is caused by snapd that unsquashes the snaps.
The other issue is that gnome-shell times out which may or may not be related to the extra delay imposed by snapd. This point must be verified."
1750403,2018-02-19 16:09:45 UTC,journal from the machine affected
1750403,2018-02-20 14:31:10 UTC,"I noticed that core 3887 is on the image while 4017 is published to stable, a theory is that the refresh to stable happens during boot and consumes lot of resources leading to memory starvation or timeouts."
1750403,2018-02-20 13:10:38 UTC,Increasing the memory of the guest to 2GB fixes the problem.
1750403,2018-02-20 08:03:33 UTC,The diff of squashfs shows that it coincides with the seeding of snap packages
1750403,2018-02-20 16:19:28 UTC,"On Tue, Feb 20, 2018 at 02:31:10PM -0000, Jean-Baptiste Lallement wrote:

> I noticed that core 3887 is on the image while 4017 is published to
> stable, a theory is that the refresh to stable happens during boot and
> consumes lot of resources leading to memory starvation or timeouts.
"
1750403,2018-03-27 15:01:57 UTC,"> Increasing the memory of the guest to 2GB fixes the problem.
"
1750411,2018-03-01 18:34:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750413,2018-03-09 13:42:01 UTC,Seems to be an upstream issue: http://tracker.ceph.com/issues/23088
1750413,2018-03-24 21:10:46 UTC,"Change abandoned by Chuck Short (<email address hidden>) on branch: master
Review: https://review.openstack.org/545980"
1750413,2019-09-12 13:09:35 UTC,We use now CentOS Storage SIG Ceph packages with signed key.
1750430,2018-04-24 21:16:16 UTC,"I am having this bug, but do you think this is also the cause of the sessions being wiped after disconnecting / reconnecting ? (using f6)"
1750430,2018-07-26 00:11:41 UTC,"I am experiencing an issue which I think may be related ever since I updated to Bionic (byobu version: 5.125-0ubuntu1, tmux version: 2.6-3) -- it seems to be correlated with the introduction of the grouped window view (or possibly having it turned on by default)."
1750430,2018-07-26 00:38:10 UTC,"I have also reproduced the issue in Byobu 5.126, installed from the PPA."
1750430,2018-08-23 13:04:31 UTC,"Today I reproduced the same issue by closing the GUI terminal window in which Byobu was running, and reattaching the session from a new terminal window. I can confirm that `byobu kill-session -t 1` executed from the other session successfully gets rid of one of the duplicate sessions."
1750430,2018-10-29 09:31:33 UTC,I was wondering if there is any progress on this. I prefer using tmux and due to this issue I can't.
1750430,2020-06-13 20:40:43 UTC,This was addressed in byobu 5.124
1750433,2020-08-08 04:17:23 UTC,[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]
1750433,2020-06-08 08:17:33 UTC,Sorry for the long delay... Do you still experience this problem?
1750443,2018-02-23 01:35:16 UTC,"The problem only occurs using Wayland, using Xorg it works normally. That is why it works by default (Xorg) in 18.04."
1750443,2018-02-19 21:51:48 UTC,"I have tried with Vbox 3D enabled and the 'sudo nautilus' works OK. Disabling 3D again reintroduces the error. The error occurs with both Vbox Guest Additions 5.2.7 and 5.2.4. Enabling 3D is not a good workaround, because of bug Bug 1748729 related to 3D enabled."
1750444,2018-04-06 04:10:45 UTC,apport-cli collected info from affected platform
1750444,2018-04-06 04:02:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750444,2018-04-06 03:58:38 UTC,"I'm also affected.  I saw this bug last time I fired up my chromebook with FF 58.0.2, and now again after doing a dist-upgrade and bringing down 59.0.2."
1750444,2018-02-21 11:33:51 UTC,apport information
1750444,2018-02-21 11:33:49 UTC,apport information
1750444,2018-02-21 11:33:50 UTC,apport information
1750444,2018-02-21 11:33:48 UTC,apport information
1750444,2018-02-21 11:33:45 UTC,apport information
1750444,2018-02-21 11:33:46 UTC,apport information
1750444,2018-02-21 11:33:46 UTC,apport information
1750444,2018-02-21 11:33:44 UTC,apport information
1750444,2018-02-21 11:33:41 UTC,apport information
1750444,2018-02-21 11:33:41 UTC,apport information
1750444,2018-02-21 11:33:40 UTC,apport information
1750444,2018-02-19 21:27:15 UTC,Note while I submitted this from a Linux chroot env on an Android device it also fails in the same way on a RPi3 running Ubuntu-Mate.
1750444,2018-02-21 11:33:47 UTC,apport information
1750444,2018-02-21 11:33:43 UTC,apport information
1750445,2019-04-24 11:13:15 UTC,I got another unexpected behavior. I am facing this issue after an update and a reboot.
1750445,2019-04-25 05:46:56 UTC,"I got my unexpected behavior from a script. This script runs in a chroot and modifies the ""Console-loadkeys"""
1750445,2019-04-25 05:49:10 UTC,(sudo dumpkeys | grep -v -E 'keycode *84 ' | grep Console >/dev/null) && (sudo dumpkeys | grep -v Console | sudo loadkeys)
1750447,2018-02-20 21:51:30 UTC,English bibles also result in an exception
1750448,2018-02-20 01:33:41 UTC,"I'm not sure I understand. Searching via custom columns and the like has
only ever worked in the calibre library not on devices. The device view
does not display custom columns and similar metadata, only
title/authors/date/size/collections."
1750448,2018-02-20 01:33:50 UTC,Changing the component for this bug.
1750448,2018-02-21 12:39:08 UTC,"I'm with Kovid on this. The only searches that have ever worked on the device list are for the displayed columns. Any time I've had a search in the library list using other columns and changed to the device list, the result would be empty."
1750449,2018-03-07 20:55:44 UTC,"Hi,"
1750449,2018-03-04 18:06:24 UTC,"The old version of moodbar was based on GStreamer 0.10, which is deprecated and has been removed from some distros for security reasons."
1750449,2018-02-19 22:14:20 UTC,kubuntu 17.10
1750456,2020-12-14 00:05:12 UTC,Internally this exists. Anything for external usage should probably be proposed and discussed on the mailing list. Nobody's looking at it otherwise.
1750464,2018-10-24 17:48:19 UTC,"Yes, although I can't provide evidence for what happened exactly, your settings must have had Fahrenheit in between. Deleting all old config files while the plugin is not loaded or the entire panel not running at all, will probably fix your troubles."
1750464,2018-10-24 11:51:05 UTC,"I had similar issue with all readings first not updating and then disappearing after a while — and readings updated only by opening xfce4-sensors-plugin settings. Solved by two things:
1) Removed xfce4-sensors-plugin from panel settings list of items in panel (I don't know exact names in English, because I use Finnish).
2) From directory ~/.config/xfce4/panel removed files .xfce4-sensors-plugin-*.rc and xfce4-sensors-plugin-*.rc (notice the dot in front of the first one, I had one of those configs).
Then just readded the sensors plugin to the panel and did all settings again."
1750464,2018-02-27 19:55:50 UTC,"OK, so for now as a hint:"
1750464,2018-02-19 23:39:21 UTC,"Created attachment 7611
Panel_Displaying_Right_Core_Temps"
1750464,2018-02-23 00:56:17 UTC,It is all very strange.  I think the system is fine.  Just now the panel reported temps ~34 degrees C while the standalone viewer was reporting ~90 degrees C.  Then I merely toggled between Celsius and Fahrenheit a few times and both the panel and standalone viewer then agreed on values ~56 degrees C.  So neither the panel nor the standalone viewer were displaying the proper values before I toggled temperature scale.
1750464,2018-02-27 02:17:30 UTC,"Hi Fabian,"
1750464,2018-02-19 23:38:23 UTC,"Created attachment 7610
Panel_Displaying_Wrong_Core_Temps"
1750464,2018-02-20 18:53:38 UTC,"Although I see your problems, I must tell you that
1. The xfce4-sensors standalone viewer does not interfere with the plugin
2. the ACPI values from file system and the values reported by libsensors3/4 are used; not detected on my own
3. I have similar problems with the coretemp values being 20-30K off the real value in comparison to ACPI, thinkpad and all the others."
1750465,2018-04-12 07:54:03 UTC,This bug was fixed in the package budgie-artwork - 0.8.3ubuntu1
1750465,2018-04-05 20:03:26 UTC,Testing the packaging for budgie-artwork:
1750465,2018-04-04 01:29:32 UTC,"Hello Stephen, or anyone else affected,"
1750465,2018-04-03 18:30:45 UTC,This bug was fixed in the package plymouth - 0.9.2-3ubuntu13.3
1750465,2018-04-03 17:21:15 UTC,"Here is the list of all blocking trigers that remain in the archive:
http://paste.ubuntu.com/p/7hP7pVqGMp/"
1750465,2018-03-29 17:00:19 UTC,"The verification of the Stable Release Update for plymouth has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1750465,2018-04-03 16:29:45 UTC,Can anyone perform testing of plymouth for xenial? It's blocking another SRU that's in the queue right now.
1750465,2018-04-03 16:22:10 UTC,This bug was fixed in the package ubuntu-gnome-default-settings - 17.10.4
1750465,2018-04-03 16:22:04 UTC,This bug was fixed in the package kubuntu-settings - 1:18.04ubuntu10
1750465,2018-04-03 16:22:01 UTC,This bug was fixed in the package ubuntu-mate-artwork - 18.04.9
1750465,2018-03-29 17:10:20 UTC,This bug was fixed in the package plymouth - 0.9.2-3ubuntu18
1750465,2018-06-20 15:28:22 UTC,"Dear Kubuntu, Mate, and Gnome flavour folks: Please also fix the bug in stable releases."
1750465,2018-04-03 17:15:18 UTC,"I tested the plymouth update for xenial by enabling proposed, then installing plymouth-theme-ubuntu-text, then modifying /etc/apt/sources.list from xenial to bionic and finally running sudo apt-get dist-upgrade.  The upgrade completed with no issues."
1750465,2018-04-03 12:01:25 UTC,"I've done a do-release-upgrade -d update with the plymouth from xenial-proposed and it completed successfully. Not marking v-done, since the test case in the description requires some additional testing."
1750465,2018-03-28 21:06:49 UTC,This bug was fixed in the package budgie-artwork - 0.9.6
1750465,2018-02-20 00:04:59 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1750465,2018-02-20 00:42:54 UTC,The auto-generated log attachments only show:
1750465,2018-03-28 22:30:18 UTC,i have tested the proposed package and it works (on ubuntu-MATE 17.10 clean install)
1750465,2018-03-05 03:54:35 UTC,I hit this too (on arm64).
1750465,2018-03-05 08:02:45 UTC,"Thanks, this shows that new lsb-release has been unpacked but not configured, then the package manager attempts to process the triggers for plymouth-theme-ubuntu-text.  This appears to be a package manager bug (either apt or dpkg) for trying to do these operations out of order."
1750465,2018-03-21 06:14:00 UTC,"Some thoughts here:
 - bash is shown as being unpacked immediately before this.  bash is an essential package.
 - the package which triggers the plymouth theme packages is base-files, which ships /etc/lsb-release.  base-files is also an essential package.
 - apt tries to handle Essential packages specially, by configuring them as quickly as possible.
 - the plymouth packages use 'interest' triggers, not 'interest-noawait' triggers, so the base-files package can't be configured until after the plymouth triggers have been run.
 - dpkg doesn't let the triggers be run before the dependencies are configured."
1750465,2018-02-20 04:48:44 UTC,"After trying to resuscitate the machine, it appears I have no term log. This upgrade wasn't even meant to be an actual test. After fixing the EOL 17.04 problem on my father's laptop and how horribly that went due to our ISP's service, I was attempting to see if it was the ISP or us causing grief."
1750465,2018-03-21 08:35:50 UTC,"Um, Steve, something is wrong in your analysis: base-files is fully configured before bash is unpacked, and when _unpacking_ bash it tries to process the trigger (i mean, there's no ""Setting up bash"" in front of it; but maybe dpkg processes triggers before printing that)."
1750465,2018-03-21 14:48:06 UTC,This bug was fixed in the package plymouth - 0.9.3-1ubuntu2
1750465,2018-03-21 15:01:11 UTC,"14:04 <rbasak> juliank: based on https://bugs.launchpad.net/ubuntu/+source/apt/+
bug/1750465/comments/10, are you suggesting I should hold on processing slangase
k's SRU upload?
14:04 <ubottu> Launchpad bug 1750465 in plymouth (Ubuntu Artful) ""upgrade attemp
ting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-
3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unpr
ocessed)"" [Undecided,In progress]
14:05 <juliank> rbasak: I'm not sure what he did precisely, I only saw the bug m
essages.
14:06 <rbasak> juliank: http://launchpadlibrarian.net/361447927/plymouth_0.9.2-3
ubuntu17_0.9.2-3ubuntu18.diff.gz is his artful SRU upload.
14:06 <juliank> That should be correct anyway.
14:06 <juliank> And it probably fixes the bug even if we don't know the exact reason yet...
14:07 <rbasak> OK. If you and slangasek both agree on what we should land, I'm happy :)
14:07 <rbasak> I'll accept assuming all the other SRU bits look OK."
1750465,2018-03-21 15:02:05 UTC,"Hello Stephen, or anyone else affected,"
1750465,2018-03-22 02:33:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750465,2018-03-28 11:56:49 UTC,"Hello Stephen, or anyone else affected,"
1750465,2018-03-21 06:19:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750465,2018-03-28 22:12:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750467,2018-02-21 01:57:12 UTC,Is this a security hardening move or were holes in the structure leaked via another interface?
1750479,2018-02-20 02:00:07 UTC,This change was made by a bot.
1750479,2018-02-20 19:34:28 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1750479,2018-02-20 19:34:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750479,2018-04-09 14:41:04 UTC,Same problem on 17.10. The packaging seems to be broken; no perf-archive script is installed anywhere. All I can find is /usr/src/linux-headers-4.13.0-38/tools/perf/perf-archive.sh but that is not used
1750479,2018-06-09 04:17:27 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1750479,2019-01-10 17:01:16 UTC,@jsalisbury? Why was this originally marked as incomplete?
1750486,2020-10-13 07:24:21 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/757720"
1750488,2018-03-05 21:45:09 UTC,Thanks for the report.
1750491,2018-02-20 18:43:02 UTC,"As requested, apport information was uploaded"
1750491,2018-02-20 18:41:15 UTC,apport information
1750491,2018-02-20 18:41:14 UTC,apport information
1750491,2018-02-20 18:41:13 UTC,apport information
1750491,2018-02-20 18:41:12 UTC,apport information
1750491,2018-02-20 18:41:10 UTC,apport information
1750491,2018-02-20 18:41:09 UTC,apport information
1750491,2018-02-20 18:41:09 UTC,apport information
1750491,2018-02-20 18:41:06 UTC,apport information
1750491,2018-02-20 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1750491,2018-02-20 18:41:00 UTC,apport information
1750491,2018-02-20 18:41:01 UTC,apport information
1750491,2018-02-20 18:41:07 UTC,apport information
1750491,2018-02-20 18:41:03 UTC,apport information
1750491,2018-02-20 18:41:05 UTC,apport information
1750491,2018-02-20 18:41:02 UTC,apport information
1750498,2018-02-20 14:22:02 UTC,"thanks for finding.
I am working on it."
1750498,2018-02-21 08:10:09 UTC,please try out
1750498,2018-02-21 09:35:34 UTC,"Now it works well, thank you!"
1750498,2018-02-21 10:13:24 UTC,"Thanks for testing and feedback.
All the best."
1750513,2018-05-16 07:51:20 UTC,"I've added the apport logs, they are from Ubuntu 18.04 as since then I've tried installing 17.04 and then upgraded it to 18.04. The problem still persists."
1750513,2018-05-16 07:49:32 UTC,apport information
1750513,2018-05-16 07:49:29 UTC,apport information
1750513,2018-05-16 07:49:28 UTC,apport information
1750513,2018-05-16 07:49:27 UTC,apport information
1750513,2018-05-16 07:49:25 UTC,apport information
1750513,2018-05-16 07:49:22 UTC,apport information
1750513,2018-05-16 07:49:30 UTC,apport information
1750513,2018-05-16 07:49:20 UTC,apport information
1750513,2018-05-16 07:49:19 UTC,apport information
1750513,2018-05-16 07:49:18 UTC,apport information
1750513,2018-05-16 07:49:17 UTC,apport information
1750513,2018-05-16 07:49:21 UTC,apport information
1750513,2018-05-16 07:49:15 UTC,apport information
1750513,2018-05-16 07:49:13 UTC,apport information
1750513,2018-05-15 14:50:41 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1750524,2020-07-25 20:15:16 UTC,"Like I understand this is feature request, remembering last image size when Pinta is closing and then use that exact image size when reopening Pinta. Is it?"
1750524,2020-07-27 01:44:08 UTC,"I can't reproduce this - for me it does immediately use the last image size when creating a new document, without needing to restart first. The exception would be if an image is on the clipboard (bug 1426052), so I think this can be closed as a duplicate?"
1750527,2018-02-20 10:05:46 UTC,I think I'd add U+FFFD REPLACEMENT CHARACTER to the list of 'nopes'.
1750527,2020-09-21 18:23:02 UTC,"The specific issue here around snapd safely displaying arbitrary description has been fixed, so I'm closing this task, but I think that we should possibly also have another new bug/task for snapd in validating the description field, etc. from `snap pack` so that for snap authors that have mistakes or errors in their snap yaml, they see the error immediately from snapcraft instead of pushing it to the store and seeing it fail from the review-tools check, but I will file another bug for that."
1750527,2019-10-29 19:19:36 UTC,"John, is the snapd task of this bug still in progress? Could you please update the bug with the current state?"
1750527,2018-07-11 22:48:21 UTC,This is now implemented in trunk.
1750527,2018-02-20 13:51:00 UTC,"John and I discussed this a bit on IRC. We should not allow control characters in any of our fields that end up being displayed to the user in snapcraft.yaml and snap.yaml or from forms from the dashboard. Historically, control characters can be used in various attack scenarios on the user's terminal. I'm told that snapd is going to allow snap.yaml overrides for description and summary that are in the store."
1750527,2018-02-20 13:50:55 UTC,The bug is private because at least VTE has in the past had issues with how it handles escapes.
1750527,2018-02-20 10:09:31 UTC,"The store is saving newlines as \r\n, so maybe accept \r only if followed by \n only in description."
1750527,2018-02-24 00:30:01 UTC,Relevant: http://people.canonical.com/~john/vt340.png
1750530,2019-09-20 08:18:24 UTC,This bug is split between the raspberry pi 3 gadget snap and the snapd snap which implements some of the raspberry pi specific config options. I'll ask my colleagues to look at this.
1750532,2018-08-17 12:07:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750553,2020-02-28 09:47:05 UTC,Same problem after upgrade salt-minion (py3) 2019.2.3 to 3000 (py3)
1750553,2020-08-30 14:18:51 UTC,Fixed in 10.0.0b1 (2018-03-31)
1750553,2019-04-23 09:53:40 UTC,"Since this is a bug in python-pip (not salt), I mark the bug for salt as invalid."
1750556,2018-03-03 16:42:29 UTC,"If in a near future the user can choose a custom color for each cue point, shouldn't we let him choose the color of THE CUE in preferences?"
1750560,2018-02-20 17:19:16 UTC,If the volume is the source of a flash copy then the delete should wait for the flash copy to complete and then delete the volume.
1750563,2018-02-20 12:56:09 UTC,More debug. I've slightly modified a couple of functions in neutron/agent/linux/keepalived.py. Just for debug purpose.
1750563,2018-03-19 20:55:38 UTC,I'm a little confused by this bug.
1750563,2018-03-21 13:23:20 UTC,"Hello Brian,"
1750565,2019-06-10 04:17:30 UTC,[Expired for kolla because there has been no activity for 60 days.]
1750565,2019-04-10 10:14:27 UTC,Seems like more of a kolla-ansible issue?
1750567,2018-04-10 15:08:16 UTC,"Per the documentation on the charm, crush-initial-weight is designed for bringing new OSDs in with a reduced weight, with the assumption that the administrator will slowly increase the weight of the new OSDs to the ceph default of 1/TB of capacity."
1750574,2018-02-20 13:48:34 UTC,"The problem seems to be that whereas MoonshotServer.install_id_card (used by moonshot-webp) sets the idcard.store_password = true, the import_identities_cb does not."
1750576,2018-06-07 19:21:51 UTC,"This is a complex javascript package, and there seems to be a heavy history of XSS issues with openstack dashboards. I'd be more confident if this was reviewed by the Security Team. They can optionally decide that I'm just being too paranoid ;)"
1750576,2018-11-30 02:13:41 UTC,"I reviewed heat-dashboard version 1.4.0-0ubuntu1 as checked into cosmic.
This shouldn't be considered a full audit but rather a quick gauge of
maintainability."
1750576,2018-12-11 14:28:03 UTC,"I really don't like the fact that the tests are not being run for the package. In comparison, I'm not as worried about the use of chown -R in the maintainer scripts."
1750576,2019-04-09 13:58:40 UTC,Thanks for the reviews all. I've uploaded a new version of heat-dashboard to disco with tests running successfully.
1750576,2019-04-09 14:50:16 UTC,Thanks. MIR approved.
1750576,2020-02-20 13:40:18 UTC,This is seeded now.
1750576,2020-06-17 02:46:23 UTC,And now in main.
1750576,2020-06-17 07:16:18 UTC,We are indeed subscribed to heat-dashboard bugs!
1750578,2020-11-04 14:34:22 UTC,The bug as written is incorrect and it's not clear that we really need to document this specifically.
1750581,2018-02-20 14:51:57 UTC,"I copied this from the original front page, we will seek for alternative text."
1750584,2018-02-23 17:54:05 UTC,Maybe this can help:
1750584,2018-02-25 22:52:02 UTC,"@brian_p, I'll have to give up. I've just tried the whole day to make the printer work on my Windows. It was firstly recognized, but as soon as I began to install the drivers, it wasn't seen anymore by the system, exactly as it happened on Ubuntu. This must be a problem with the printer itself, maybe because of the transport when I brought it from my brother's house to mine (8 hours driving). Thanks for your help."
1750584,2018-02-25 20:46:23 UTC,My last post on this issue. I do not want to respond solely to myself.
1750584,2018-02-25 13:32:56 UTC,The show stopper is in your hp-check:
1750584,2018-02-23 18:54:37 UTC,This was a double-check on what we knew from 'lsusb | grep 03f0'. No printer is detected. But lots of other USB devices are; so the lsusb utility is operating as it should.
1750584,2018-02-23 17:46:37 UTC,Please run the command 'lsusb' and post the output here.
1750584,2018-02-26 19:41:43 UTC,"Hello Tales,"
1750584,2018-02-22 14:39:47 UTC," > @brian_p: About cables and connection, I have tried already
 > several cables that work fine with other equipment or OS."
1750584,2018-02-22 12:47:42 UTC,"@brian_p: About cables and connection, I have tried already several cables that work fine with other equipment or OS."
1750584,2018-02-21 13:39:37 UTC,"Hi,"
1750584,2018-02-21 13:28:01 UTC,Check the cable and the connections.
1750584,2018-02-21 13:20:19 UTC,COMMAND #1 is intended to detect the device file which the aio set up when is plugged in. I'd expect lp0 but you have entries only for (probably) mouse and keyboard. This isn't good.
1750584,2018-02-21 12:51:48 UTC,"[COMMAND #1]
ttomaz@tales-inspiron:~$ ls -l /dev/usb
total 0
crw------- 1 root root 180, 0 Fev 21 09:27 hiddev0
crw------- 1 root root 180, 1 Fev 21 09:27 hiddev1"
1750584,2018-02-21 11:33:18 UTC,Give the outputs of:
1750584,2018-02-23 17:09:00 UTC,@brian_p: Tried again 'lsusb' and the result was the same:
1750586,2018-02-20 17:48:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750586,2018-02-22 15:18:30 UTC,The post installation file /var/lib/dpkg/info/python-minimal.postinst runs the following command:
1750586,2018-02-23 08:17:34 UTC,"Thank you Stephen, your solution worked for me too. A different package as you expected, but removing the folder seems to have resolved my issues."
1750586,2018-02-23 16:49:37 UTC,"Thanks, Stephen."
1750586,2018-02-26 07:24:10 UTC,"I have three packages under /usr/share/python, I think they are all company specific packages."
1750586,2018-04-20 18:50:42 UTC,"I faced issues when upgrading Ubuntu 16.04 (I don't remember exactly, maybe from 16.04.3 to 16.04.4). At end of the upgrade it showed following error:"
1750586,2018-06-05 14:14:05 UTC,"Thanks Stephen.
As per your note I removed the /usr/share/python/rekall-forensic  folder then it is worked for me 2 days I spend for finding out a solution thanks for your help..."
1750593,2018-02-22 20:21:12 UTC,Thanks for confirming the problem.
1750593,2018-02-22 19:46:18 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1750594,2018-02-22 13:10:48 UTC,"From IRC:
07:06 <@jdstrand> mvo: hey, so jjohansen looked at the memory issue quite a bit yesterday. the summary is that the profiles themselves are is a small leak (*much* smaller than 30M; on the order of 2M after processing all the profiles in /var (if I'm reading  jj's numbers right))
07:07 <@jdstrand> mvo: so it seems that the system was already under memory pressure, and that straw caused it to oom, but it was simply the straw that broke the camel's back. there were many more straws before it
07:08 <@jdstrand> mvo: jjohansen said he'll contine searching for that small leak. he's also investigating reducing that 30M by quite a bit"
1750594,2018-04-12 18:55:38 UTC,I confirmed this bug and I will provide a simple reproducer. I'm bisecting kernels to find what is causing the (most) of the leak. I will post additional details as they become available.
1750594,2018-04-13 11:57:48 UTC,Some quick facts from the forum:
1750594,2018-04-16 10:25:40 UTC,I can confirm that jj's patch fixes this issue.
1750599,2018-10-04 11:00:27 UTC,This issue was fixed in the openstack/networking-ovn 4.0.3 release.
1750599,2018-07-09 01:41:39 UTC,This issue was fixed in the openstack/networking-ovn 4.0.2 release.
1750599,2018-04-27 12:02:38 UTC,"Reviewed:  https://review.openstack.org/547039
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=b57c59ea482b2605ab6b6c9ba36e3032d94cf897
Submitter: Zuul
Branch:    stable/queens"
1750599,2018-04-19 14:11:11 UTC,This issue was fixed in the openstack/networking-ovn 5.0.0.0b1 development milestone.
1750599,2018-03-15 15:15:53 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/547334"
1750599,2018-02-23 13:32:41 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/547006
Reason: in favor of: https://review.openstack.org/#/c/543374/"
1750599,2018-02-23 12:34:54 UTC,"Reviewed:  https://review.openstack.org/546986
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=5d19dad877a5589e026ab4af7b09e6c8ee97fc22
Submitter: Zuul
Branch:    master"
1750599,2018-02-23 10:31:41 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/546199"
1750599,2018-02-23 09:28:33 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: master
Review: https://review.openstack.org/546198"
1750599,2018-02-23 09:12:15 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: master
Review: https://review.openstack.org/547077
Reason: this was meant for stable/queens"
1750599,2018-02-22 15:53:45 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: master
Review: https://review.openstack.org/547017
Reason: For some reason I sent this patch to stable/queens but it didn't work. This patch is for stable/queens only :)"
1750599,2018-02-22 15:53:36 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/547039"
1750599,2018-02-22 15:22:25 UTC,"Change abandoned by Numan Siddique (<email address hidden>) on branch: master
Review: https://review.openstack.org/546986"
1750599,2018-02-22 14:50:02 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: master
Review: https://review.openstack.org/547014"
1750599,2018-02-22 14:37:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/547006"
1750599,2018-02-21 11:36:48 UTC,"Again, I made a mistake running it manually with ostestr. Forcing tox to downgrade to ovsdbapp==0.9.0 didn't help either. It must be something else, investigating."
1750599,2018-02-21 11:29:03 UTC,But running from ostestr does? :?
1750599,2018-02-21 11:25:53 UTC,"Disregard, running it serially doesn't help either. Sorry for confusing"
1750599,2018-02-20 16:09:23 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/546199"
1750599,2018-02-20 16:08:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/546198"
1750599,2018-02-23 09:11:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/547334"
1750602,2018-02-27 12:21:00 UTC,Why you are posting a bug for Telegram for Android in the Ubuntu Touch tracker?
1750604,2018-02-21 14:13:09 UTC,Updating an internet on a deployed node is supported on one circumstance:
1750604,2019-09-19 11:57:26 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1750604,2018-02-20 16:20:58 UTC,"Hi Peter,"
1750604,2018-02-20 21:31:47 UTC,FAOD from bug #1703661 I was kinda assuming that updating an interface of a Deployed (ie. non-Ready / Broken / Alloc) was not supported. Therefore expecting an error to be thrown.
1750611,2018-02-20 17:31:06 UTC,"Some poking around suggests that changing the iframe URL in opac/parts/record/summaryplus.tt2 so that it uses ""Options=N"" rather than ""Options=Y"" will remove the close button from the embedded content."
1750613,2018-02-25 17:33:38 UTC,"hello
It seems to me that this is the same problem with the file /boot/grub/grub.cfg"
1750613,2018-02-26 15:57:28 UTC,"Hello
I post the contents of a  boot-info in an installed ubuntu."
1750615,2019-07-25 17:27:45 UTC,"Reviewed:  https://review.opendev.org/670926
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=52da4d0e129048d1b808bdde07364cde698cf475
Submitter: Zuul
Branch:    master"
1750615,2019-09-27 09:10:33 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1750618,2018-03-30 17:12:58 UTC,"Reviewed:  https://review.openstack.org/550555
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9890f3f69622489a0fd57cb1df354d7aa60161e0
Submitter: Zuul
Branch:    stable/pike"
1750618,2018-05-02 12:01:34 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1750618,2018-04-20 13:14:14 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1750618,2018-04-19 14:32:59 UTC,"Reviewed:  https://review.openstack.org/550560
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=286dd2c23c7c361c6538be65941e3c19e83e6d52
Submitter: Zuul
Branch:    stable/ocata"
1750618,2018-04-02 13:18:31 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1750618,2018-04-02 13:09:18 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1750618,2018-03-21 14:48:44 UTC,"Reviewed:  https://review.openstack.org/550545
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c5e519a8875a9766a0d3a06cb76cceba26634e6
Submitter: Zuul
Branch:    stable/queens"
1750618,2018-03-07 17:38:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550545"
1750618,2018-03-07 18:33:09 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/550560"
1750618,2018-03-07 18:12:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/550555"
1750618,2018-02-21 15:39:28 UTC,"Actually, it's showing as consuming 512MB under ""memory_mb_used"" even when the instance is gone, so I think this might be intentional."
1750618,2018-02-21 15:28:23 UTC,"It looks like it's mostly only affecting the rebuild action.  In the compute_nodes table in the nova DB I'm seeing ""memory_mb_used"" be 1024 when it should be 512, but the CPU/disk usage is where it should be so I'm not sure what's going on."
1750618,2018-02-21 05:45:16 UTC,"Is this extra Claim only affect the rebuild action, or can it leaks and affect the project quota or the compute capacity after the rebuild is completed?"
1750618,2018-02-20 18:50:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546268"
1750618,2018-02-20 17:29:04 UTC,This is a regression introduced with change I11746d1ea996a0f18b7c54b4c9c21df58cc4714b which was backported all the way to stable/newton upstream:
1750618,2018-03-07 20:40:26 UTC,"Reviewed:  https://review.openstack.org/546268
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a39029076c7997236a7f999682fb1e998c474204
Submitter: Zuul
Branch:    master"
1750620,2018-02-21 16:31:17 UTC,"The thing is with stuff like this is spurious information in the file could cause issues down the road. For example the netlist parser might be changed in the future and the file, and all files based on it, would break."
1750620,2018-02-21 16:04:59 UTC,"On 2/21/2018 9:55 AM, Brian Piccioni wrote:

> I didn't modify the files at github. Those are the original files of the
> board designer. I didn't use KiCad to modify the files at all.
>
> I expect they screwed something up. My point is that the ERC or
> something should catch the bad file format.
"
1750620,2018-02-21 15:58:02 UTC,"I'm not sure what we could do about the deleted sheet but we could clear
the annotation for copied sheets which should clean up any phantom sheet
path information.  Otherwise we would have to create some code that
would check for invalid sheet paths and remove the phantom sheet paths
left over from the copied sheet."
1750620,2018-02-21 14:29:47 UTC,"Yes.
It happens when in a complex hierarchy, one sheet is deleted, or when copying sheets coming from a complex hierarchy from an project."
1750620,2018-02-21 13:43:34 UTC,"@Brian, did you at one point have the ""eDP LCD"" sheet in the ""Power Supply, Extensions and MiPi-DSI"" sheet and then move it to the root sheet?  Judging by the time stamps, that appears to be the cause of the phantom hierarchical component definitions.  I don't think this will cause any issues but I am curious as to how this happened.  I've never seen this behavior before but then again I don't look at every schematic file after I create a schematic.  @JP, have you ever seen this before and if so should we be concerned about it?  I would think that any left over hierarchy definitions would get removed when the file either moved or saved."
1750620,2018-02-21 14:55:46 UTC,I didn't modify the files at github. Those are the original files of the board designer. I didn't use KiCad to modify the files at all.
1750623,2018-09-24 14:47:17 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1750623,2018-06-04 14:27:57 UTC,This issue was fixed in the openstack/nova 16.1.4 release.
1750623,2018-05-20 22:06:26 UTC,"Reviewed:  https://review.openstack.org/561015
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ffbf5918c650e8499de206b73f050d5e8580b04e
Submitter: Zuul
Branch:    stable/pike"
1750623,2018-04-25 09:23:59 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1750623,2018-04-20 13:12:33 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1750623,2018-04-17 10:58:23 UTC,"Reviewed:  https://review.openstack.org/561014
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=04ea910ad13b412f410ccf520074cacee6bbe13e
Submitter: Zuul
Branch:    stable/queens"
1750623,2018-04-13 22:47:58 UTC,"Reviewed:  https://review.openstack.org/546357
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c3a894b6af32ff8ddba728328bc7d4e1339b2964
Submitter: Zuul
Branch:    master"
1750623,2018-04-13 16:01:18 UTC,The numa stuff changing during rebuild is IMO a separate bug which we should fix with a new filter mechanism somehow (fail fast in API or conductor pre-scheduler?) and then we can also backport that fix.
1750623,2018-04-13 16:00:37 UTC,We should fail the rebuild if the new image changes any hardware resource accounting stuff since we don't do a resource claim on the compute during a rebuild.
1750623,2018-02-20 22:17:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546357"
1750623,2018-04-12 19:17:04 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561014"
1750623,2018-04-13 17:37:45 UTC,Opened https://bugs.launchpad.net/nova/+bug/1763766 to track preventing the resource consumption from changing during rebuild.
1750623,2018-04-13 15:39:04 UTC,"What if the image properties contain vCPU topology or NUMA resource information? If the new image properties specify a different vCPU topology or NUMA topology/memory pages amounts, then that effectively amounts to a resize doesn't it?"
1750623,2018-04-13 15:54:09 UTC,"Yes, if the image properties result in different resources being consumed (different amount of CPU/RAM on each numa node for example, or different page size) then I think placement would need to know."
1750623,2018-04-12 19:22:47 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/561015"
1750625,2020-04-20 12:51:23 UTC,"Yes, it worked that way. Thank you!"
1750625,2020-04-20 09:18:22 UTC,"That release file is sort of invalid, as we also need the uncompressed Packages file hashed, because we check hashes after decompression too."
1750625,2020-04-20 06:52:50 UTC,"I think the answer is simple: We should stop sending If-Modified-Since. There's no advantage to sending that compared to getting back the same release file, and it's a bad design."
1750625,2020-04-20 08:09:59 UTC,"I actually tried to add a Release file without signing it, because it would be simple, only a single command:"
1750625,2020-04-19 20:58:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750625,2018-08-22 10:18:13 UTC,I think a problem is that your Release file is missing a Date field. APT should not be trying to redownload unmodified files.
1750625,2018-02-20 19:01:56 UTC,Still occurring in xenial with apt 1.2.25
1750625,2018-02-20 18:55:44 UTC,"In trusty, this works as expected."
1750625,2020-04-19 21:08:54 UTC,"This is a bug in 20.04 as well. I have no Release file, this is a private, unsigned repository, only Packages.xz. On first run, apt update first works. On the second run apt update issues a HTTP GET with an If-Modified-Since header:"
1750625,2020-04-20 06:45:48 UTC,"I guess that's good to know that it does not really work without a release file now anyway, it is a good argument for removing support for such repos completely. I made a plan a year or two ago, but have not acted on it yet :/"
1750633,2018-06-14 10:19:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750633,2018-06-14 10:38:41 UTC,"I'd really appreciate a backport of the fix. Some other distributions shipping with paramiko 2.0 ship it already, for example mageia (https://advisories.mageia.org/MGAA-2018-0077.html)"
1750633,2018-07-14 13:39:15 UTC,Here's the link to the upstream fix: https://github.com/paramiko/paramiko/pull/979/commits/fdc09c9f93fd189a6398d5b350a3c91011d9b4cb
1750633,2018-07-14 14:03:20 UTC,"This bug does not involve any paramiko entry points used by duplicity, so I removed the dependency."
1750633,2018-07-26 14:07:25 UTC,"Hej Kenneth, thanks for the answer. I agree that this is a sufficient workaround, but for an LTS version of Ubuntu, I think it would be worthwhile considering backporting this fix."
1750638,2018-02-20 19:16:40 UTC,Marked as confirmed based on several other reports on the internet:
1750641,2018-02-20 19:58:16 UTC,"I would hazard a guess that this is a problem between Qt5 and TWM, not VLC per se... And even if it is blatantly obvious which one of those two has changed, I would not hazard a guess as to which one is at ""fault""."
1750641,2018-02-21 13:35:25 UTC,Reassigned accordingly.
1750642,2018-02-21 12:57:28 UTC,"as i said in the forum (or was it IRC ?), bug 1628289 might be related ..."
1750642,2018-07-17 14:57:57 UTC,I believe I'm experiencing the same on Arch Linux.
1750645,2020-04-18 16:52:13 UTC,"I just find it incredible that even despite this bug being open, there was this official announcement late last year that the d-i installer will be completely phased out in favor of 'subiquity' starting with the focal release."
1750645,2020-01-20 18:09:45 UTC,Since no later than 18.04.3 the installer offers to encrypt an LVM which is configured during manual partitioning. I assume this solves this bug?
1750645,2019-07-02 18:41:52 UTC,"ccooke: As another Ubuntu user, I think I can answer this:"
1750645,2019-07-02 13:46:47 UTC,Why is this marked as 'Fix Released'?
1750645,2019-02-21 14:22:43 UTC,"I'm going to repurpose this bug to be about encryption, the other things are covered by other bugs I believe."
1750645,2018-11-05 17:15:23 UTC,"I agree with everything danielbuus said, except I would change the faces to >-( and :'("
1750645,2018-05-03 20:56:01 UTC,"@Tomasz: The d-i based install image is ""the traditional installer found on the alternative downloads page"" as you can read from the Download Ubuntu Server 18.04 page[1][2][3]:"
1750645,2018-06-11 20:50:40 UTC,I'm totally agree with Sander. A new installer is useless and non needed.
1750645,2018-05-21 12:28:05 UTC,"I understand that Subiquity will provide these features in the future, but I find it very irresponsible to make it the default installer for a server release without being production ready (and these features are a MUST for servers). Let alone pushing this in an LTS release. Very irresponsible..."
1750645,2018-05-03 20:09:36 UTC,"Forgive my ignorance, but what is a ""d-i based install image""?"
1750645,2018-04-09 19:03:49 UTC,"Just decided to try 18.04 beta when I found the new installer is terrible and even denies me to install the system to a previously created partitions. No FAT32 FS for the UEFI partition, no option to mount any existing one. This is really ridiculous an stupid."
1750645,2018-03-21 02:43:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750645,2018-02-20 20:27:30 UTC,"> There is no way to select encryption and lvm to start with.
"
1750645,2018-06-28 12:45:21 UTC,"I know I probably shouldn't join the negativity train here, but... OMG, why? The usual installer is the best I've ever used in my 18 years of Linuxing."
1750647,2018-02-23 14:38:35 UTC,"Ah, I wonder when DEFCENUM started taking non-keywords. The idea was that
having a single namespace for enum members would match the C semantics,
IIRC."
1750647,2018-02-20 20:18:00 UTC,"actually, looking closer, DEFCENUM and FOREIGN-ENUM-VALUE accept non-keyword keys, so KEYWORDP is wrong there anyway"
1750647,2018-02-20 20:56:36 UTC,https://github.com/cffi/cffi/pull/129
1750651,2018-02-21 12:45:37 UTC,"Thank you for your bug report, indeed that package is coming from the Debian packaging and missing some options. Would be worth sending to the Debian BTS"
1750654,2018-02-21 13:08:54 UTC,"On Tue, Feb 20, 2018 at 08:43:41PM -0000, Martin Pitt wrote:

> Public bug reported:
>
> As per documentation, the `-B best` option should automatically select
> the best backingstore, falling back all the way to dir.
>
> But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:
"
1750657,2018-02-20 20:51:39 UTC,https://btrfs.wiki.kernel.org/index.php/FAQ#Does_btrfs_support_swap_files.3F
1750657,2018-03-13 07:20:51 UTC,I created https://github.com/CanonicalLtd/subiquity/pull/295 for the simplest possible fix. Too simple? Opinions welcome.
1750657,2018-07-15 08:00:58 UTC,"This is not just affecting btrfs, I'm using XFS and my files have holes too. And according to the swapon man page, ext4 could have the same issue."
1750659,2018-02-20 21:07:02 UTC,"Before filing this I asked a question in StackExchange:
https://graphicdesign.stackexchange.com/questions/105721/how-can-i-draw-a-loopback-connector-using-inkscape-connectors
If there is a solution I'd like to post it there too, so it's public."
1750662,2018-02-21 06:42:56 UTC,"A couple of drive-by thoughts on this one.
It seems that the issue is more around slowness in general as pacemaker times out on the monitoring of all its services:
Feb 20 18:50:14 [15128] centos-7-inap-mtl01-0002637151       lrmd:  warning: child_timeout_callback:    haproxy-bundle-docker-0_monitor_60000 process (PID 86216) timed out
Feb 20 18:50:38 [15128] centos-7-inap-mtl01-0002637151       lrmd:  warning: operation_finished:        haproxy-bundle-docker-0_monitor_60000:86216 - timed out after 20000ms
Feb 20 18:50:38 [15128] centos-7-inap-mtl01-0002637151       lrmd:  warning: child_timeout_callback:    rabbitmq-bundle-docker-0_monitor_60000 process (PID 86274) timed out
Feb 20 18:50:38 [15128] centos-7-inap-mtl01-0002637151       lrmd:  warning: child_timeout_callback:    galera-bundle-docker-0_monitor_60000 process (PID 86434) timed out
Feb 20 18:50:38 [15128] centos-7-inap-mtl01-0002637151       lrmd:  warning: child_timeout_callback:    redis-bundle-docker-0_monitor_60000 process (PID 86625) timed out
Feb 20 18:50:38 [15128] centos-7-inap-mtl01-0002637151       lrmd:  warning: operation_finished:        galera-bundle-docker-0_monitor_60000:86434 - timed out after 20000ms
Feb 20 18:50:38 [15131] centos-7-inap-mtl01-0002637151       crmd:    error: process_lrm_event: Result of monitor operation for galera on galera-bundle-0: Timed Out | call=139 key=galera_monitor_10000 timeout=30000ms
Feb 20 18:50:38 [15128] centos-7-inap-mtl01-0002637151       lrmd:  warning: operation_finished:        redis-bundle-docker-0_monitor_60000:86625 - timed out after 20000ms
Feb 20 18:50:38 [15128] centos-7-inap-mtl01-0002637151       lrmd:  warning: operation_finished:        rabbitmq-bundle-docker-0_monitor_60000:86274 - timed out after 20000ms
Feb 20 18:50:38 [15131] centos-7-inap-mtl01-0002637151       crmd:    error: process_lrm_event: Result of monitor operation for haproxy-bundle-docker-0 on centos-7-inap-mtl01-0002637151: Timed Out | call=52 key=haproxy-bundle-docker-0_monitor_60000 timeout=20000ms
Feb 20 18:50:38 [15131] centos-7-inap-mtl01-0002637151       crmd:    error: process_lrm_event: Result of monitor operation for galera-bundle-docker-0 on centos-7-inap-mtl01-0002637151: Timed Out | call=22 key=galera-bundle-docker-0_monitor_60000 timeout=20000ms
Feb 20 18:50:38 [15131] centos-7-inap-mtl01-0002637151       crmd:    error: process_lrm_event: Result of monitor operation for redis-bundle-docker-0 on centos-7-inap-mtl01-0002637151: Timed Out | call=33 key=redis-bundle-docker-0_monitor_60000 timeout=20000ms
Feb 20 18:50:38 [15131] centos-7-inap-mtl01-0002637151       crmd:    error: process_lrm_event: Result of monitor operation for rabbitmq-bundle-docker-0 on centos-7-inap-mtl01-0002637151: Timed Out | call=11 key=rabbitmq-bundle-docker-0_monitor_60000 timeout=20000ms
Feb 20 18:50:38 [15131] centos-7-inap-mtl01-0002637151       crmd:     info: throttle_check_thresholds: Moderate CPU load detected: 12.020000
Feb 20 18:50:38 [15131] centos-7-inap-mtl01-0002637151       crmd:     info: throttle_send_command:     New throttle mode: 0010 (was 0000)"
1750662,2018-02-21 19:17:02 UTC,+1 to being able to tune timeouts
1750662,2021-02-17 17:10:09 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1750663,2018-09-26 03:13:13 UTC,"Sorry, that was a valid program's complaint ^.
It looks like it's working now."
1750663,2018-05-20 13:11:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750663,2018-09-26 02:57:23 UTC,After the procedure above I am having another error:
1750666,2018-02-22 17:03:00 UTC,"Reviewed:  https://review.openstack.org/546804
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=58af9ba39bda8753bb9d86d3587e2529911843f9
Submitter: Zuul
Branch:    stable/queens"
1750666,2018-04-20 13:14:09 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1750666,2018-03-01 15:39:38 UTC,"Reviewed:  https://review.openstack.org/546275
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e5a055d2c6f04330cb83b33f8ddd4c9875fdb1b7
Submitter: Zuul
Branch:    stable/pike"
1750666,2018-03-01 14:45:37 UTC,"Reviewed:  https://review.openstack.org/546812
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b61bf73b0fe5e96ab2953df93444acd2db6de62f
Submitter: Zuul
Branch:    stable/pike"
1750666,2018-02-22 18:27:58 UTC,This issue was fixed in the openstack/nova 17.0.0.0rc3 release candidate.
1750666,2018-02-22 17:02:43 UTC,"Reviewed:  https://review.openstack.org/546803
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9b59abc04475e51458112541ca2bb50e51599cfd
Submitter: Zuul
Branch:    stable/queens"
1750666,2018-04-02 13:18:48 UTC,This issue was fixed in the openstack/nova 16.1.1 release.
1750666,2018-02-22 00:31:38 UTC,"Reviewed:  https://review.openstack.org/546315
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3120627d9802ceda46c2db387fec8fbc80700338
Submitter: Zuul
Branch:    master"
1750666,2018-02-21 23:37:47 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/546812"
1750666,2018-02-21 23:08:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/546804"
1750666,2018-02-21 23:08:12 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/546803"
1750666,2018-02-20 22:26:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546398"
1750666,2018-02-20 21:22:24 UTC,It should be noted that this was found during backporting of https://review.openstack.org/#/c/545132/ to stable/pike where we don't have this code to set the bdm.attachment_id:
1750666,2018-02-22 00:31:50 UTC,"Reviewed:  https://review.openstack.org/546398
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=16c2c8b3ee9d70e928a61ceb1ef5931d40e509a4
Submitter: Zuul
Branch:    master"
1750668,2018-02-20 21:54:16 UTC,"If I install python-minimal, which provides /usr/bin/python (python2.7), it also fails with the same import error."
1750669,2019-03-26 16:29:28 UTC,"Reviewed:  https://review.openstack.org/647677
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=de083009eb51d1af086387bbac0dca8d3c4474c0
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-03-26 16:29:15 UTC,"Reviewed:  https://review.openstack.org/647676
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4ccb4c258f54642a272e0d865aa1768b7f1ffee5
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-03-26 16:29:00 UTC,"Reviewed:  https://review.openstack.org/647675
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ad108dafe2bdd1b6523d6f45315bb136b9b01408
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-03-26 10:38:27 UTC,"Reviewed:  https://review.openstack.org/645889
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d1cfa3ab3f87f15f61c5387670d3b75ee2ba93ba
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 16:28:31 UTC,"Reviewed:  https://review.openstack.org/647673
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=fd08266abb3a4fb18ac05921ca11c4768daa2f6d
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-03-26 15:12:34 UTC,"Reviewed:  https://review.openstack.org/645890
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ef838a3a3f575562b1fc84623c3a8491d4f2e2f4
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 16:29:54 UTC,"Reviewed:  https://review.openstack.org/647678
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=1d8ac830a1ed6a571db6987d4ef657cf3e04d640
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-03-26 08:08:57 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647680"
1750669,2019-03-26 16:28:45 UTC,"Reviewed:  https://review.openstack.org/647674
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0786fde3932e218ef355a6cc958f83c3c7033686
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-03-26 16:30:09 UTC,"Reviewed:  https://review.openstack.org/647679
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=02eebfe5732fb9935331551e223337b22db7aebd
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-04-01 17:03:41 UTC,"Reviewed:  https://review.openstack.org/647814
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=db3b293cdea31b5a2b4fab1108d905832ee15550
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-03-26 17:00:39 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647814"
1750669,2019-03-26 17:00:57 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647815"
1750669,2019-04-02 12:02:35 UTC,"Reviewed:  https://review.openstack.org/647815
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=933b7509a4177680158baeeb582f82470f73ae38
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-06-26 20:59:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/667730"
1750669,2019-09-13 09:15:18 UTC,"Change abandoned by Vishakha Agarwal (<email address hidden>) on branch: master
Review: https://review.opendev.org/612615"
1750669,2019-09-13 20:43:26 UTC,"Reviewed:  https://review.opendev.org/645968
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f0ef5741c1ffb4173ce5d845a4ec30e075984b3e
Submitter: Zuul
Branch:    master"
1750669,2019-09-13 20:55:07 UTC,"Reviewed:  https://review.opendev.org/667730
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bbd77d0bf9dde57e5ca5d53f7214df85713b9f1e
Submitter: Zuul
Branch:    master"
1750669,2019-09-27 09:10:11 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1750669,2019-03-26 08:08:41 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647679"
1750669,2019-03-26 16:30:27 UTC,"Reviewed:  https://review.openstack.org/647680
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=56e48127938be2d67b984d00b155833532233713
Submitter: Zuul
Branch:    stable/stein"
1750669,2019-03-26 08:08:24 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647678"
1750669,2019-03-26 08:07:29 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647675"
1750669,2019-03-26 08:07:47 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647676"
1750669,2018-12-04 22:32:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622615"
1750669,2019-03-20 22:00:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645021"
1750669,2019-03-20 22:00:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645022"
1750669,2019-03-20 22:00:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645023"
1750669,2019-03-20 22:01:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645024"
1750669,2019-03-21 19:29:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645309"
1750669,2019-03-21 19:29:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645310"
1750669,2019-03-21 19:30:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645311"
1750669,2019-03-22 04:58:12 UTC,"Reviewed:  https://review.openstack.org/622615
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=465a8bb59be13739253a52d7e457067cf63d3ba8
Submitter: Zuul
Branch:    master"
1750669,2019-03-22 21:27:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645889"
1750669,2019-03-22 21:27:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645890"
1750669,2019-03-25 17:53:52 UTC,"Reviewed:  https://review.openstack.org/645021
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bb4192e88d88b781b2a821f3a499b7168b7bbc31
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 01:28:29 UTC,"Reviewed:  https://review.openstack.org/645022
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8f4e179c69eae7ced731776717c09a979bd67cc5
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 01:28:40 UTC,"Reviewed:  https://review.openstack.org/645023
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8450d4a9cc76ce9e476d3cadf863f40f072f4cfe
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 01:28:50 UTC,"Reviewed:  https://review.openstack.org/645024
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=fac844c4ae058c148889b636ab6cbb637df7e554
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 01:31:48 UTC,"Reviewed:  https://review.openstack.org/645309
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=593e67e6ca429c6e6b54c5453a05c40a73abee85
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 01:32:20 UTC,"Reviewed:  https://review.openstack.org/645310
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ba09e89ba1b8a883b09ca81f43bf54bd870411c1
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 01:32:31 UTC,"Reviewed:  https://review.openstack.org/645311
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6e118bad3d49bc1da7137a406fb8cb2e3da931ca
Submitter: Zuul
Branch:    master"
1750669,2019-03-26 08:06:52 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647673"
1750669,2019-03-26 08:07:09 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647674"
1750669,2018-10-23 07:33:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612615"
1750669,2019-03-26 08:08:06 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647677"
1750676,2019-09-27 09:10:46 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1750676,2019-06-19 14:13:22 UTC,"Reviewed:  https://review.opendev.org/665231
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=092570fc5ef43497c29cf174bfff43323a49fb58
Submitter: Zuul
Branch:    master"
1750676,2019-06-13 20:19:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665231"
1750678,2018-10-04 07:15:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/607820"
1750678,2019-09-10 06:29:59 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/681162"
1750678,2019-09-15 09:20:15 UTC,"Reviewed:  https://review.opendev.org/607820
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d009384c9b683008d572f9996e1fe4e5e5d82096
Submitter: Zuul
Branch:    master"
1750678,2019-09-15 22:15:33 UTC,"Reviewed:  https://review.opendev.org/681162
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6435017c242d759ec18dac30d667f0e196e49f38
Submitter: Zuul
Branch:    master"
1750678,2019-09-27 09:09:59 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1750688,2020-08-26 02:19:20 UTC,"Just FYI, the MP was submitted, still pending."
1750688,2019-09-19 11:57:29 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1750688,2020-08-18 14:08:17 UTC,I'm developing a tool that will rely on lldp data collected by maas to draw a network map to catch errors and miscabling during HAP phase of cloud install in customers. It is very important that this gets fixed.
1750688,2018-08-13 20:04:16 UTC,"Hi Nobuto,"
1750688,2018-02-20 23:42:39 UTC,"           *-network:0
                description: Ethernet interface
                product: Ethernet Controller X710 for 10GbE SFP+
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:01:00.0
                logical name: eno1
                version: 01
                serial: 24:6e:96:XX:XX:XX
                size: 10Gbit/s
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi msix pciexpress vpd bus_master cap_list rom ethernet physical fibre
                configuration: autonegotiation=off broadcast=yes driver=i40e driverversion=1.4.25-k duplex=full firmware=6.00 0x800034e6 18.3.6 latency=0 link=yes multicast=yes slave=yes speed=10Gbit/s"
1750688,2018-08-14 09:49:29 UTC,"> What's the best way to discover this interface automatically? Is there a file we can check somewhere under sys/kernel to allow us to identify this interface?
"
1750690,2018-03-15 18:09:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750690,2018-03-20 18:56:20 UTC,"First selected compiz in MATE Tweak -> Windows -> Window manger
Then selected 'Dock Preferences' of the Munity Dock.
then Windows -> Windows selection -> 'From window thumbnail prefiews (requires Compiz)'
crash"
1750690,2018-04-12 03:00:24 UTC,I had the same problem when moving Terminator from the desktop to the dock.
1750698,2018-02-21 00:57:20 UTC,"StacktraceTop:
 copy_into_unchecked (adapter=adapter@entry=0x7fcffc0227e0, dest=dest@entry=0x7fcffc0550f0 ""x\006"", skip=0, size=size@entry=2101) at gstadapter.c:333
 gst_adapter_get_internal (adapter=adapter@entry=0x7fcffc0227e0, nbytes=nbytes@entry=2101) at gstadapter.c:749
 gst_adapter_get_buffer (adapter=adapter@entry=0x7fcffc0227e0, nbytes=nbytes@entry=2101) at gstadapter.c:1012
 gst_adapter_take_buffer (adapter=0x7fcffc0227e0, nbytes=nbytes@entry=2101) at gstadapter.c:1074
 gst_video_decoder_add_to_frame (decoder=decoder@entry=0x7fcffc049370, n_bytes=n_bytes@entry=2101) at gstvideodecoder.c:3229"
1750698,2019-07-23 04:16:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750714,2018-02-21 14:12:31 UTC,"What if someone picks the machine up and moves it or the cables are changed? Shouldn't MAAS handle those changes automatically, especially as we push more towards the networking be completely automated."
1750714,2018-02-21 14:44:49 UTC,"I think that updating the inteface VLAN should be prevented only when MAAS is *not* managing DHCP and the user is using an external DHCP server (and obviously, the interface is set to DHCP)."
1750714,2019-09-19 14:46:47 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1750715,2018-02-21 04:37:05 UTC,"LXD autopkgtest for Xenial is currently clean, the rest are unrelated to LXD, closing."
1750715,2019-10-10 10:27:09 UTC,I believe we've fixed them all (for now!)
1750722,2019-07-09 02:28:45 UTC,The cause of this failure has been fixed since the report was filed as I can no longer make the test fail locally under stress.
1750732,2020-10-27 02:24:08 UTC,"Hardware long gone, invalidate this bug."
1750732,2019-04-11 10:59:33 UTC,"Hello,
sorry that I missed this one,"
1750732,2018-10-30 17:18:18 UTC,Is there any update on this bug report?
1750732,2018-11-08 22:56:44 UTC,"The system was set to boot from PXE by default, at least before MAAS deployed it:
Feb 22 03:28:41 lodygin cloud-init[3447]: + echo before grub-install efiboot settings
Feb 22 03:28:41 lodygin cloud-init[3447]: before grub-install efiboot settings
Feb 22 03:28:41 lodygin cloud-init[3447]: + efibootmgr
Feb 22 03:28:41 lodygin cloud-init[3447]: BootCurrent: 0002
Feb 22 03:28:41 lodygin cloud-init[3447]: Timeout: 1 seconds
Feb 22 03:28:41 lodygin cloud-init[3447]: BootOrder: 0002,0003,0004
Feb 22 03:28:41 lodygin cloud-init[3447]: Boot0002* UEFI: IP4 Intel(R) Gigabit CT Desktop Adapter
Feb 22 03:28:41 lodygin cloud-init[3447]: Boot0003* UEFI: Built-in EFI Shell
Feb 22 03:28:41 lodygin cloud-init[3447]: Boot0004* Hard Drive"
1750732,2018-03-15 15:25:59 UTC,"Hi, do we have an update on this?
the new SRU cycle has begun and it is blocking us from testing this node."
1750732,2018-02-22 06:51:43 UTC,"Hello,
I'm using MaaS 2.3 (2.3.0-6434-gd354690-0ubuntu1~16.04.1)"
1750732,2018-02-21 17:56:55 UTC,"MAAS sends a debconf selection to curtin, so that curtin tells grub to not update the nvram. The information that's required is:"
1750732,2018-02-21 17:50:05 UTC,The change in GRUB for bug 1642298 only adds a hook to disable updating NVRAM - it doesn't change any defaults. The code to do that is in curtin and/or MAAS. What versions of curtin/MAAS are in use here?
1750732,2018-10-03 12:59:21 UTC,"This is possibly a firmware issue, seeing as the default state for grub as provided by maas/curtin config should be to skip modifying nvram."
1750737,2018-09-06 07:41:11 UTC,"import, export, please"
1750737,2018-09-06 12:24:41 UTC,We just need a volunteer who is able to implement it.
1750763,2018-03-20 15:07:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750763,2018-05-11 10:45:07 UTC,"Boot on Lubuntu 18.04 64-bit hangs at /script/local-premount/resume for approx. twenty seconds with no disk activity, then boot resumes correctly."
1750764,2018-02-21 19:31:17 UTC,Thank you for taking the time to report this! I fixed it by move the initializing call to on_tabWidget_currentChanged to MainWindow::show as well. There is not really a reason to already call it inside the constructor as far as I can see.
1750766,2019-07-09 08:39:15 UTC,"I think this has to do with the python docker module. You have both docker and docker-py in pip list. I would suggest trying with only one of these installed, probably docker-py (which is the older one) given that you are using an older version of kolla-ansible."
1750768,2018-02-21 16:24:14 UTC,you can see that patron id IDA00015 is getting error while log in
1750770,2018-02-21 10:24:00 UTC,"I now have a second system, did not mess with the job dependencies (yet) on this one and created a secondary admin user to get to the logs."
1750770,2018-02-21 10:26:59 UTC,"cloud-init.log http://paste.ubuntu.com/p/WwRp8ggDdr/
cloud-init-output.log http://paste.ubuntu.com/p/RVystXn6VQ/"
1750770,2018-03-08 08:08:42 UTC,"I suspect this is 16.04 only.
in 18.04, ds-identify should disable cloud-init correctly.
in 16.04 its still set to reporting only mode. and in the log it shows that the list got set to Ec2 (maybe)."
1750770,2018-03-08 08:24:23 UTC,"I expected it not to break, let me (try to) recreate and talk later (hopefully my vmware still works ...)."
1750770,2018-03-08 08:33:51 UTC,"""not to break"" is rather useless statement - I beg your pardon.
Better:
I'd expect it to:
- cloud-init wont work as there is no datasource (fine
- cloud-init not to change my user in a way that I can't log in anymore."
1750770,2018-03-08 11:34:02 UTC,In a joint debug session it was found that the user gets locked by the none Datasource.
1750770,2018-03-08 11:34:54 UTC,"Maybe the none DS should not add/lock user.
Without data adding that it is worth nothing."
1750770,2018-03-08 22:29:50 UTC,"So in cloud-init on bionic, in the scenario that Christian was running in, cloud-init would disable itself so that no disabling of the ubuntu user would occur."
1750777,2018-04-27 13:44:07 UTC,https://review.openstack.org/#/c/564748/ has been proposed to tag neutron 12.0.2
1750777,2018-05-02 19:27:43 UTC,"Corey - I was going to reply to your upstream announcement to pick this up, we're just waiting on the 12.0.2 tag to merge."
1750777,2018-05-02 20:55:29 UTC,Thanks Brian. I'll cherry-pick it for now and pick up the stable release when that's available.
1750777,2018-05-03 13:23:19 UTC,New versions of neutron for queens has been uploaded to the cosmic and bionic unapproved queues where they are awaiting acceptance:
1750777,2018-05-03 20:05:56 UTC,"Hello Thomas, or anyone else affected,"
1750777,2018-05-04 12:38:29 UTC,"Hello Thomas, or anyone else affected,"
1750777,2018-05-04 16:50:01 UTC,This bug was fixed in the package neutron - 2:12.0.1-0ubuntu2
1750777,2018-05-08 04:36:23 UTC,This issue was fixed in the openstack/neutron 12.0.2 release.
1750777,2018-05-07 15:56:14 UTC,Regression tests have passed successfully for queens-proposed and bionic-proposed:
1750777,2018-04-25 18:34:29 UTC,"Ok, now it makes sense to me.  I have asked to create a new tag for stable/queens, will discuss at next Monday's neutron meeting since we should probably be doing it on a regular cadence, https://wiki.openstack.org/wiki/Network/Meetings#On_Demand_Agenda"
1750777,2018-05-07 15:57:26 UTC,Thanks for testing Trent!
1750777,2018-05-14 07:56:21 UTC,"The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1750777,2018-05-14 08:06:21 UTC,This bug was fixed in the package neutron - 2:12.0.1-0ubuntu1.1
1750777,2018-05-14 12:25:04 UTC,The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1750777,2018-05-14 12:25:06 UTC,"This bug was fixed in the package neutron - 2:12.0.1-0ubuntu1.1~cloud0
---------------"
1750777,2018-05-07 05:36:11 UTC,"Verified on xenial-queens; fresh nova-lxd install from conjure-up was exhibiting the behavior, restarting the service did not help.  Upgraded package from queens-proposed and the issue no longer occurs."
1750777,2018-04-25 07:03:01 UTC,"I'm using kolla-ansible centos/binary which installs neutron 12.0.1 from RDO (latest release, not the stable git repo - released 27 days ago) - which doesn't have the patch for 100% cpu usage (not counting other patches between 12.0.1 release and stable/queens branch)"
1750777,2018-03-05 20:53:30 UTC,"So one thing I think I noticed is that queue.get() can throw an exception, even though it's blocking.  The reason is that the Queue (actually LightQueue) class is actually based on collections.queue, and from it's doc page (get is implemented by popleft):"
1750777,2018-04-24 13:23:02 UTC,"Would there be a possibility to do a new neutron release in Queens?
This bug is only in stable branch, not the 12.0.1 release - and most deployment project install latest release... which makes most of new deployments useless... (using 100% cpu)"
1750777,2018-04-24 19:37:53 UTC,"Michal - I don't understand, this is fixed in the stable/queens branch now.  Where are you getting your packages from?"
1750777,2018-03-01 15:46:17 UTC,"I couldn't reproduce this with a quick stack, will try again later.  I did create a test patch to test a theory, don't know if it will fix the issue however."
1750777,2018-03-01 15:47:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548976"
1750777,2018-03-02 23:44:57 UTC,"I've looked at the code, and unless I read the code too quickly (which is honestly quite a possibility given the amount of snow and travelling plans clogging in my head), I think we are  having a race condition:"
1750777,2018-03-03 00:08:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/549331"
1750777,2018-03-03 00:09:57 UTC,"one detail in the above is wrong: queue.get() is blocking by default
but I think the rest of the comment still holds"
1750777,2018-03-05 20:55:35 UTC,s/collections.queue/collections.deque
1750777,2018-02-21 10:38:50 UTC,The bug is in the code introduced by https://review.openstack.org/#/c/537654 .
1750777,2018-03-07 20:47:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550598"
1750777,2018-03-09 20:27:16 UTC,"Miguel was able to reproduce this by spawning a VM and then destroying it, top would then show the agent in a tight loop.  I was able to do the same and found that even with my fix that got merged, the agent could still go into a tight loop.  Thomas' change is better, https://review.openstack.org/#/c/549331/ - I just updated it based on additional testing and have proposed a revert of my change that merged."
1750777,2018-03-09 22:04:12 UTC,"Change abandoned by Brian Haley (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/550598"
1750777,2018-03-17 12:21:53 UTC,"Reviewed:  https://review.openstack.org/549331
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=35c225aaa37ee685000bfa07a02e83481485138d
Submitter: Zuul
Branch:    master"
1750777,2018-03-19 15:20:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554258"
1750777,2018-04-05 12:22:30 UTC,"Reviewed:  https://review.openstack.org/554258
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cca870abbc4f8a784c9cbed817ff307ab3094daa
Submitter: Zuul
Branch:    stable/queens"
1750777,2018-04-19 14:13:03 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b1 development milestone.
1750777,2018-03-07 20:40:07 UTC,"Reviewed:  https://review.openstack.org/548976
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4c8b97eca32c9c2beadf95fef14ed5b7d8981c5a
Submitter: Zuul
Branch:    master"
1750778,2018-02-21 10:38:32 UTC,ubuntu_qrt_* tests are unable to git clone the qa-regression-testing repo:
1750779,2018-02-21 13:18:46 UTC,"crash reproduced, although not quite using the same steps:"
1750779,2018-02-21 13:24:03 UTC,"same result with Inkscape 0.92+devel (9d6b0e8, 2018-02-18)"
1750780,2018-03-06 12:43:19 UTC,"For open-vm-tools this issue will only exist with the planned backport of the newer version.
Since we will not ship the broken backport as we found it in pre-checks the correct state for open-vm-tools in xenial is invalid."
1750780,2018-03-21 06:30:54 UTC,"Note: When we do the Xenial backport of the new version of open-vm-tools (which we plan to do) this becomes an issue. In the same upload I intend to fix it right away, so it should never effectively exist in the field (keep invalid, but there might be a fix-released update to open-vm-tools here at some point)."
1750780,2018-04-20 06:26:54 UTC,"This will only ""become"" an issue for Xenial/Artful with the backport.
But lets do it right for tracking - so I added/modified tasks for these releases which allows me to refer changes and changelog to here."
1750780,2018-05-08 23:46:50 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1750780,2018-05-09 00:02:53 UTC,"Hello ChristianEhrhardt, or anyone else affected,"
1750780,2018-10-08 13:43:25 UTC,"So, is there anything requested to be done with Xenial's systemd in this bug?"
1750780,2018-05-16 02:12:20 UTC,This bug was fixed in the package open-vm-tools - 2:10.2.0-3~ubuntu0.16.04.1
1750780,2018-05-16 02:12:39 UTC,"The verification of the Stable Release Update for open-vm-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1750780,2018-05-16 02:13:02 UTC,This bug was fixed in the package open-vm-tools - 2:10.2.0-3~ubuntu0.17.10.1
1750780,2018-10-09 05:37:31 UTC,"No, unless you were afraid that what ticked open-vm-tools into having issues here being a wider more general issue. But then given that 16.04 is used widely for quite some time I think we can assume it is a corner case only."
1750780,2018-02-27 07:24:05 UTC,"With the former update in mind I retried Xenial/Bionic again.
All of it is racy (as we knew), but it never triggered for Bionic."
1750780,2018-02-27 06:48:02 UTC,"Thanks Scott for your cross check.
I wonder why my former test failed on each of my tests without writing, but never the less your extended example is great for the systemd issue that remains."
1750780,2018-05-09 14:02:23 UTC,"1. Upgrade from proposed - this is the same for all associated bugs, so I only documented details in bug 1741390"
1750780,2018-02-26 17:16:03 UTC,"I'Ll likely revert the Binonic change tmrw morning as we have discussed.
local-fs.target is actually >> the implicit dependency."
1750780,2018-02-21 10:46:18 UTC,Note: IMHO a consequence of the bad fix (in Debian) to bug 1667831
1750780,2018-02-21 16:33:49 UTC,"So, definitely using the"
1750780,2018-02-22 07:22:08 UTC,I'll fix the current known race for now.
1750780,2018-02-22 07:23:57 UTC,"I tested the fix a bit more, always worked for me, that said I'll:"
1750780,2018-02-22 08:00:44 UTC,"1. I updated the ppa we test for a potential xenial-backport.
   It now has 10.2.0-3ubuntu0.16.04.1~ppa2 with the fix applied"
1750780,2018-02-22 07:36:33 UTC,"cloud-init task was just for discussion, marking it invalid to make clear there is no cloud-init action needed."
1750780,2018-02-22 15:16:03 UTC,I dont think I really agree with this fix.
1750780,2018-02-22 16:10:09 UTC,"While I can follow your argument of ""it should work"" I tested and if I drop 'After=local-fs.target' I'm in bad state again. If from this state I disable PrivateTmp it works as well.
So it is PrivateTmp even though the documentation you linked says it should not."
1750780,2018-02-22 16:25:18 UTC,"On Thu, Feb 22, 2018 at 9:16 AM, Scott Moser <email address hidden>
wrote:"
1750780,2018-02-23 19:41:39 UTC,There is a difference between cloud-init sometimes running after local-fs.target and being guaranteed to run after local-fs.target.  The change here guarantees it.
1750780,2018-02-26 16:43:08 UTC,"Installed another Xenial and Bionic in vmware to take a deper look.
- Xenial (with backported open-vm-tools): affected
- Bionic (with the interim fix reverted): no hit in several retries, explanation below"
1750780,2018-02-22 08:37:48 UTC,This bug was fixed in the package open-vm-tools - 2:10.2.0-3ubuntu1
1750780,2018-02-26 17:58:32 UTC,"I agree with reverting change in bionic, and that xenial still needs some fix."
1750783,2018-03-08 04:01:55 UTC,https://github.com/mixxxdj/mixxx/pull/1541
1750783,2018-02-21 23:26:50 UTC,I am not certain that the effect should only play when the deck is playing. Consider someone playing a live instrument along with a track. They may want to hear the metronome at the tempo of the next track for a few bars before starting the new track.
1750783,2018-02-22 11:35:18 UTC,"I also believe that if the metronome can also be played even when the deck is not playing gives more control to the user. As otherwise if he wants to stop the metronome, he can turn it off."
1750788,2021-02-17 17:10:12 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1750788,2018-02-26 22:32:52 UTC,"Update process did change in Pike, some background in: https://bugs.launchpad.net/tripleo/+bug/1715557"
1750788,2019-09-04 17:32:36 UTC,Does this command still exist?  I'm on CentOS 7 in a standalone deployment and I'm not seeing it in the command list...
1750789,2018-03-27 15:52:41 UTC,vpnaas dashboard has never been implemented.
1750789,2019-02-04 10:47:22 UTC,"As of today (20190204), I can see that there's variable in os_horizon role to enable the dashboard :
horizon_enable_neutron_vpnaas.
But I cannot see the installation repo definition in playbooks/defaults/repo_packages/openstack_services.yml."
1750794,2018-02-23 10:18:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750794,2018-03-31 13:27:54 UTC,Is there any chance this bug can be at least considered?
1750796,2018-02-22 19:07:33 UTC,"Hi Joseph,
I have installed kernel 4.16.0-041600rc2_4.16.0-041600rc2.201802190311 and - it works!!!
I booted about 30 times, the xserver always runs and everything was fine."
1750796,2018-02-21 13:45:14 UTC,"Since xserver does not work, the browser can not opened to authorize the report. Tryed apport-collect 1750796 via ssh. The lync browser came up, but I'm not sure if the report has send the log file."
1750796,2018-02-21 13:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1750796,2018-02-21 20:01:35 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1750808,2018-02-21 12:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1750809,2018-02-21 12:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1750814,2018-03-13 13:40:53 UTC,"Could it just be a CLI flag ""--all"" ? That seems like you wouldn't have to worry about collisions."
1750814,2018-03-14 06:32:38 UTC,"Sure - something like ""juju scp --all /path/to/local /remote/path"" ? It's looking a bit weird but I don't think that's avoidable"
1750817,2018-02-21 15:11:05 UTC,thank you for taking the time to issue a report!
1750817,2018-02-21 20:32:01 UTC,Here's the file.
1750817,2018-02-21 22:34:13 UTC,"thank you for the file.
crash not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06) (32 bit build)"
1750817,2018-02-21 23:51:04 UTC,"I tried running inkscape from the windows command prompt and I did not get any extra messages.
I navigated to the folder where the file was saved on windows explorer, and typed ""cmd \k"" into the address bar. This opened a cmd in the folder's directory, where I then executed ""start buggy_file.svg""."
1750817,2018-02-22 00:51:31 UTC,"thanks for trying, it was just a thought. If the programmer has used an ASSERT command in his code then it is typical to get a DOS output message, however there are lots of cases where there will be no message either (which I think can happen if there were a memory access violation of some sort.)"
1750817,2018-02-22 12:45:27 UTC,64 bit inkscape.
1750817,2018-02-22 14:52:55 UTC,"I did some testing, with and without different things to try to narrow down what's happening.
the factors that seem to determine whether it crashes is"
1750817,2020-03-08 12:12:01 UTC,"Replicated with the test file in 0.92.3, there is output in CLI (I'm not sure if this is not true in older versions of inkscape, but newer versions don't have output without the inkscape.com wrapper). This was also replicated in the 1.0alpha appimage (from Jan 2019)."
1750818,2020-05-15 17:28:51 UTC,"Ken, I see that one of the MR commits was already added to snap-store git, however to make this fix actually work, the another one (https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/457/diffs?commit_id=74980a2f94cefa1e75778bf8fcba55ddaa880405) needs to be added as well."
1750818,2020-05-14 19:12:38 UTC,"The upstream fix was just merged into master. I am not sure if/when the fix will be backported to gnome-3-36 branch, however fixing this in Ubuntu should be pretty easy. The fix consists of these two commits that can be applied downstream (in deb gnome-software / Snap Store): https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/457/commits"
1750818,2020-10-12 16:23:57 UTC,I'm not seeing this issue in an up-to-date 20.04 installation.
1750818,2020-05-15 20:31:17 UTC,"@asciiwolf, with just the other commit it definitely fixed the issue described in the bug report.  I spent some time looking at the other and might cherry-pick that as well."
1750818,2020-05-05 14:08:24 UTC,"There is an upstream fix for this issue being prepared, see the remote bug watch ticket."
1750818,2018-02-22 16:16:55 UTC,"Thank you for your bug report, what Ubuntu serie and gnome-software version are you using? On what deb did you try?"
1750818,2020-04-15 17:38:24 UTC,Same issue with the latest stable Snap Store.
1750818,2018-02-22 16:36:47 UTC,The latest Ubuntu 18.04 build. (But I had the same issue on Ubuntu 17.04.) For example the Steam deb from: http://store.steampowered.com/about/
1750818,2020-04-26 17:38:29 UTC,Upstream issue: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/965
1750818,2018-02-22 16:42:37 UTC,"Oops, s/17.04/17.10. :-)"
1750818,2018-02-22 16:38:54 UTC,(But it was happening on other deb packages as well.)
1750826,2018-06-15 14:18:09 UTC,xenial-queens-proposed:
1750826,2018-06-15 14:12:53 UTC,Tempest regression test results:
1750826,2018-06-15 13:50:07 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1750826,2018-04-10 09:53:54 UTC,"Hello James, or anyone else affected,"
1750826,2018-06-15 13:50:09 UTC,"This bug was fixed in the package ceph - 12.2.4-0ubuntu0.17.10.1~cloud0
---------------"
1750826,2018-03-26 13:08:14 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1750826,2018-03-22 09:25:13 UTC,This bug was fixed in the package ceph - 12.2.4-0ubuntu1
1750826,2018-03-22 09:03:16 UTC,"Hello James, or anyone else affected,"
1750826,2018-03-03 14:45:06 UTC,See also version 12.2.4
1750826,2018-03-29 18:20:56 UTC,"Hello James, or anyone else affected,"
1750829,2018-05-18 15:46:35 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/569449"
1750829,2018-05-03 15:11:51 UTC,"Reviewed:  https://review.openstack.org/565670
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=efa26e8dc24b5e828447fb78d0f54004054ae8b9
Submitter: Zuul
Branch:    stable/pike"
1750829,2018-05-08 10:40:57 UTC,"Reviewed:  https://review.openstack.org/565672
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=691ffcfe93c56efba44230c65884118dbd9f89af
Submitter: Zuul
Branch:    stable/ocata"
1750829,2018-05-18 15:13:37 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/569442"
1750829,2018-05-25 01:47:11 UTC,"Reviewed:  https://review.openstack.org/570271
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a27ea0f9100d0061c1cf3b20407095d3cd04df26
Submitter: Zuul
Branch:    stable/queens"
1750829,2018-06-22 12:20:28 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/569449"
1750829,2018-05-25 05:57:20 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/570514"
1750829,2018-05-29 10:32:50 UTC,"Change abandoned by Kashyap Chamarthy (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/569442"
1750829,2018-05-29 12:39:03 UTC,"Reviewed:  https://review.openstack.org/570513
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=27bacacdd8a3741cfbd7e14a4ea50713c5e1d9e5
Submitter: Zuul
Branch:    stable/pike"
1750829,2018-05-31 15:57:02 UTC,"Reviewed:  https://review.openstack.org/570514
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c18cd38d4d72524c55b4ad3bfa8d9ed5e6b44caf
Submitter: Zuul
Branch:    stable/ocata"
1750829,2018-05-03 09:51:54 UTC,"Reviewed:  https://review.openstack.org/565668
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9ab466c6d9bb657409356f29139a9edfbb98747
Submitter: Zuul
Branch:    stable/queens"
1750829,2018-07-16 17:08:52 UTC,"Reviewed:  https://review.openstack.org/581730
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=1700603b0dd257cd934e5a39aea6b571f9d29c94
Submitter: Zuul
Branch:    master"
1750829,2018-05-25 05:57:06 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/570513"
1750829,2018-05-02 11:59:11 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1750829,2018-04-25 09:21:12 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1750829,2018-05-02 08:21:46 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/565670"
1750829,2018-02-21 14:23:44 UTC,The (WIP) proposed change: https://review.openstack.org/#/c/534384/ -- libvirt: Allow to specify granular CPU feature flags
1750829,2018-02-21 14:25:52 UTC,"Quoting one quick and simple user benchmark with and without ""pcid"" feature
flag from 'qemu-devel' mailing list post[1]:"
1750829,2018-04-06 15:00:11 UTC,"Reviewed:  https://review.openstack.org/534384
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6b601b7cf6e7f23077f428353a3a4e81084eb3a1
Submitter: Zuul
Branch:    master"
1750829,2018-04-09 10:53:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/559700"
1750829,2018-04-09 10:53:46 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/559702"
1750829,2018-05-02 08:27:34 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/565672"
1750829,2018-04-10 20:18:18 UTC,"Reviewed:  https://review.openstack.org/559700
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=98eb85f29c5f0775de480d5ea2946dcbba85fe8a
Submitter: Zuul
Branch:    stable/queens"
1750829,2018-04-13 09:05:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/561168"
1750829,2018-04-20 13:12:48 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1750829,2018-04-25 09:24:01 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1750829,2018-05-01 22:11:57 UTC,"Reviewed:  https://review.openstack.org/565043
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e438eda9bb16cdd3b627b93da2435572275b921
Submitter: Zuul
Branch:    master"
1750829,2018-05-02 08:20:46 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/565668"
1750829,2018-04-11 19:29:06 UTC,"Reviewed:  https://review.openstack.org/559702
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=56350b977e412d59da96a79290d80c6422fa44b1
Submitter: Zuul
Branch:    stable/pike"
1750829,2018-04-21 00:52:36 UTC,"Reviewed:  https://review.openstack.org/561168
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c6b2fce289b68af92afeddf8d30efcda1903f06
Submitter: Zuul
Branch:    stable/ocata"
1750831,2018-02-27 12:20:43 UTC,Why you are posting a bug for Telegram for iOS in the Ubuntu Touch tracker?
1750835,2018-02-27 08:42:12 UTC,Recent failure is a bit different from others. In /var/log/messages in previous cases all errors were related to qemu process:
1750835,2018-02-27 08:34:17 UTC,"I have put logs related to recent failure in bug description, please consider."
1750835,2018-02-22 00:15:58 UTC,"Issue has happened multiple times already and causes (partial) workload failure/outage, so I've bumped up the importance."
1750835,2018-02-23 22:36:45 UTC,please provide steps to reproduce
1750838,2018-02-27 12:20:30 UTC,Why you are posting a bug for Telegram for iOS in the Ubuntu Touch tracker?
1750840,2019-10-08 11:01:09 UTC,"Partially addressed already by `snap info <snap>`, however there are more aspects of size to be reported - makring as duplicate of 1661533."
1750847,2018-02-27 02:02:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750852,2018-05-02 08:43:37 UTC,"XPS, OpenXPS or Open XML Paper Specification is an open specification from Microsoft based on Extended Application Markup Language (XAML) and Open Packaging Convention (OPC). There are two versions of the standard with extensions `.xps` and `.oxps`."
1750856,2018-02-22 10:59:09 UTC,https://github.com/snapcore/snapd/pull/4718
1750856,2019-10-15 11:21:12 UTC,"This is fixed now, we don't run these tests on s390x anymore as part of autopkgtest."
1750857,2018-02-26 06:48:01 UTC,"Is the issue that you don't have permissions to do anything on the controller without having a model?
Presumably you do have a login into the controller, its just that the ""juju gui"" command is expecting to have a model to connect to first?"
1750857,2018-02-26 14:15:07 UTC,"Yes, it's that model assumption that's the issue."
1750860,2018-02-27 13:49:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750860,2018-02-28 14:30:57 UTC,Tank you very much for your exelent work!!!!
1750860,2018-02-21 17:25:37 UTC,Package: snapd 2.31.1~14.04
1750860,2018-02-21 18:47:16 UTC,"First i want to thank you and many others who work for us to make Ubuntu
fantastic👏"
1750873,2018-03-07 08:33:43 UTC,Step 1: investigate and time things so we can quantify the problem and any improvements we make.
1750873,2018-03-11 23:53:21 UTC,"I think about half of the delay is spent unpacking the initramfs, suggesting that switching to lz4 or gzip compression instead of the current lzma might help significantly (this sounds familiar from other contexts...)"
1750873,2018-04-12 04:25:59 UTC,This bug was fixed in the package livecd-rootfs - 2.521
1750873,2020-09-02 19:45:47 UTC,"Is this bug closed? When installing via 20.04.1 live server ISO, I see a message that says:"
1750873,2020-09-07 10:53:10 UTC,"I don't have any real ideas for how to make boot faster, so perhaps we should close this bug. Errors relating to TPM communications are definitely something different and should be tackled in a different report!"
1750891,2018-05-16 01:55:14 UTC,"Hi Lee,"
1750891,2019-11-30 04:17:39 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1750891,2019-09-30 12:03:04 UTC,Are you still seeing this failure in your CI?
1750891,2018-05-16 22:49:51 UTC,In Node._start MAAS double checks that the commissioning OS is available on all rack controllers before starting. While list-boot-images told you the image is available the check in Node._start didn't. As part of LP:1762461 I had to rewrite this check. Now both list-boot-images and the check in ._start use the same RPC call(ListBootImagesV2) to determine if images are synced.
1750891,2018-05-16 01:17:34 UTC,@andreserl - I looked into your reproduction and the behavior you see is actually expected. list-boot-images on both the UI and API call list_boot_images() in src/provisioningserver/rpc/boot_images.py. This is cached to reduce IO. The cache is updated after image sync. Deleting the images doesn't invalidate the cache so it returns the same set of images before you deleted them.
1750891,2018-04-25 15:01:45 UTC,i think this issue is related or the same issue as https://bugs.launchpad.net/maas/+bug/1766370
1750891,2018-05-04 10:24:37 UTC,"Hi Guys,"
1750891,2018-02-22 19:42:11 UTC,"Ok, so I think i may know how to reproduce this issue on a single region/rack."
1750891,2018-02-21 20:03:08 UTC,rack-controller list-boot-images is what we're using - that's what Blake told us to use to make sure that rack controllers are all synced and maas is ready to deploy machines.
1750891,2018-02-21 19:29:58 UTC,"Hi Jason,"
1750891,2018-05-04 10:25:17 UTC,(marking it as incomplete until we can reproduce with beta3 as could have been related to https://bugs.launchpad.net/maas/+bug/1766370)
1750892,2019-01-30 21:15:09 UTC,This issue was fixed in the openstack/glance 18.0.0.0b1 development milestone.
1750892,2018-10-05 02:08:22 UTC,"Change abandoned by iain MacDonnell (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/598253
Reason: Project can't decide if this is the right thing to do or not, so dropping backports."
1750892,2018-10-05 02:08:08 UTC,"Change abandoned by iain MacDonnell (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/598204
Reason: Project can't decide if this is the right thing to do or not, so dropping backports."
1750892,2018-08-30 17:52:24 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/598253"
1750892,2018-08-30 15:22:44 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/598204"
1750892,2018-08-15 12:52:41 UTC,"By the looks of it the replace call indeed does not touch the image state. Add call 'thjough will change the state from 'queued' to 'active'. You might want to try out ""op"":""add"",""path"":""/locations/0"""
1750892,2018-04-12 23:42:46 UTC,Also note that the checksum is None and there's no way to set it in the v2 API.
1750892,2018-02-21 19:52:39 UTC,"Yes, please! I was considering opening a separate bug to request something like that..."
1750892,2018-02-21 19:35:53 UTC,"Slightly off topic, but it's kind of overkill to have to expose locations in order to use the http store in this way.  Maybe what we need is a 'web-reference' (instead of web-download) import method to do this."
1750892,2018-08-25 11:14:56 UTC,"Reviewed:  https://review.openstack.org/592775
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=e2c54d58b33c7350c78629cc7726b5fa4509637b
Submitter: Zuul
Branch:    master"
1750899,2020-11-21 14:20:54 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1750899,2021-01-21 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1750905,2018-02-22 18:32:40 UTC,Mixxx is installed via your Ubuntu beat ppa here:
1750905,2018-02-22 18:33:16 UTC,*Ubuntu beta ppa*
1750905,2018-02-22 16:37:22 UTC,"Thanks for testing.
Iirc, this should work if installed via *.deb package, if not this is a regression. Im not on linux, so cant test."
1750905,2018-04-15 23:31:47 UTC,for auto-completion we can install a file here:
1750905,2018-02-22 15:55:21 UTC,"``mixxx --h`` works with all supported platforms.
On linux, ``man mixxx` should work with the (outdated) man page available @https://github.com/mixxxdj/mixxx/blob/master/build/debian/mixxx.sgml"
1750905,2018-02-22 11:22:16 UTC,mixxx --help
1750905,2018-02-22 16:16:52 UTC,man mixxx doesn't work here.
1750905,2018-02-22 10:51:10 UTC,"Yeah, auto-complete would be nice! Or some minimal man page that lists available options.
I rarely use controller debug or different ressource path, but if I do I have to look it up in the wiki to checck the correct spelling."
1750906,2018-02-21 21:11:05 UTC,"This would be nice, but I think it would be a lot of work to implement."
1750906,2018-02-22 09:46:21 UTC,"Yeah this is definitely a ""hopefully sometime in the future"" kind of request, although I would find it very useful I wasn't expecting to see it in the next version...."
1750914,2018-03-09 21:45:26 UTC,Of particular frustration with this bug is the fact that the rack controller name is editable but MaaS refuses to save the edits because it can't look up the _existing_ name you're trying to correct.  That is not a great UX experience.
1750914,2018-08-13 20:23:21 UTC,"Hi Jay,"
1750914,2019-09-19 14:53:54 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1750916,2018-05-08 15:39:17 UTC,"Hi Tina,"
1750919,2018-11-14 13:48:48 UTC,This (generally desirable) option should *not* be offered in case this is an offline installation (feature requested at #1750819).
1750919,2019-02-21 14:19:06 UTC,We should do this. We should *always* update security updates (well. if there is a network connection) and offer to install all updates.
1750919,2019-04-18 01:18:23 UTC,Now that security updates are installed by default this is a bit lower priority.
1750920,2019-03-06 01:23:36 UTC,"This was briefly discussed at the last engineering sprint and ISTR that it may not be the best thing to do here.  I'll leave this triaged/wishlist and if we get a concrete yes|no from foundations/grub/uefi folks, then we can either add to next cycle or mark won't fix with details as to why or why not."
1750920,2019-03-21 23:04:29 UTC,"We are doing this in ubiquity on the desktop today for 18.04 and later.  It may not be necessary for the maas case, but I believe it's what we should be doing for the subiquity case, so that any Ubuntu-installed amd64 boot disk is portable across machines regardless of firmware configuration."
1750927,2018-11-13 20:34:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750933,2019-07-15 17:47:54 UTC,How to proceed with ceilometer if gnocchi-api doesn't get installed?
1750933,2019-05-09 09:29:55 UTC,"Since the latest release does not have gnocchi-api, I would suggest please remove it from the official documentation too on the following link. It suggests restart service gnocchi-api."
1750933,2019-02-20 23:34:33 UTC,You can use httpd to solve this problem.
1750933,2018-04-19 05:47:22 UTC,"Any workaround for this issue?
https://docs.openstack.org/ceilometer/pike/install/install-base-ubuntu.html
Above document is invalid"
1750933,2018-03-14 14:19:21 UTC,Latest release of gnoochi 4.2.1 doesn't have gnoochi-api. So we can't start or stop gnoochi-api service
1750933,2018-03-14 14:19:19 UTC,Latest release of gnoochi 4.2.1 doesn't have gnoochi-api. So we can't start or stop gnoochi-api service
1750933,2019-02-28 17:11:19 UTC,How to use httpd to solve the aforementioned issue.
1750942,2018-03-24 09:49:54 UTC,Patch available at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892715
1750942,2019-03-06 13:36:22 UTC,"Dear Arijit,
Many thanks for reporting this issue and providing a fix. I have applied your patch to the GIT repository on Sourceforge but I don't know how long it will take (if ever) to get included in the version distributed with 14.04
Regards, Paul"
1750947,2018-03-22 01:29:22 UTC,"@Robie,"
1750947,2018-11-19 09:40:27 UTC,I don't like that the sponsorship queue says my name is on this. Removing sponsors.
1750947,2018-08-31 01:27:02 UTC,The fix was removed from Xenial in May. Please see bug 1767784 where it was reverted.
1750947,2018-08-30 02:00:26 UTC,Actually the fix was reverted back in May 2018:
1750947,2018-04-23 10:12:31 UTC,"The verification of the Stable Release Update for pulseaudio has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1750947,2018-04-13 05:31:21 UTC,I have checked pulseaudio/1:8.0-0ubuntu3.9 on xenial and it does fix the problem.
1750947,2018-04-12 09:46:46 UTC,"Hello Hui, or anyone else affected,"
1750947,2018-04-12 09:46:26 UTC,"I will be accepting this upload, but for future reference: in the regression potential field please also include an assessment where possible regressions can appear. This should be mostly hypothetical, but think of this section as a hint for testers who'd like to know what to test to see if anything isn't broken. Also, this section should give us, the SRU team, a good understanding of how badly broken other things can get in the worst-case scenario if this upload gets approved. Usually this involves looking at the patch and checking which other use-cases it can effect and, in some bizarre circumstance, break those by accident."
1750947,2018-03-23 15:21:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750947,2018-03-21 13:47:04 UTC,"> [Regression Potential]
"
1750947,2018-03-08 03:48:18 UTC,added a pointer to this bug and uploaded
1750947,2018-03-08 03:48:52 UTC,update the description to add the usual impact/test case/regression potential etc
1750947,2018-02-22 04:57:39 UTC,"[ 800.271277] Freezing user space processes ...
[ 820.267656] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
[ 820.267704] alsa-sink-HDMI D 0 1554 1117 0x00000004
[ 820.267710] Call Trace:
[ 820.267723] __schedule+0x3c2/0x8b0
[ 820.267727] schedule+0x36/0x80
[ 820.267730] schedule_timeout+0x17a/0x360
[ 820.267735] ? call_timer_fn+0x140/0x140
[ 820.267745] snd_power_wait+0xba/0x110 [snd]
[ 820.267751] ? snd_power_wait+0xba/0x110 [snd]
[ 820.267756] ? wake_up_q+0x70/0x70
[ 820.267766] snd_pcm_common_ioctl1+0x41/0x930 [snd_pcm]
[ 820.267772] snd_pcm_playback_ioctl1+0x13e/0x250 [snd_pcm]
[ 820.267777] ? eventfd_ctx_read+0x67/0x210
[ 820.267784] snd_pcm_playback_ioctl+0x28/0x40 [snd_pcm]
[ 820.267789] do_vfs_ioctl+0xa1/0x5f0
[ 820.267792] SyS_ioctl+0x79/0x90
[ 820.267796] entry_SYSCALL_64_fastpath+0x1e/0xa9
[ 820.267798] RIP: 0033:0x7fb4d9bbdf07
[ 820.267800] RSP: 002b:00007fb4d5d3cc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 820.267803] RAX: ffffffffffffffda RBX: 00007fb4d5d3cca0 RCX: 00007fb4d9bbdf07
[ 820.267805] RDX: 0000000001888d20 RSI: 0000000000004122 RDI: 0000000000000016
[ 820.267807] RBP: 0000000001888d20 R08: 0000000000000043 R09: 0000000000000001
[ 820.267808] R10: 000000000185f870 R11: 0000000000000246 R12: 0000000001888d20
[ 820.267810] R13: 0000000000000000 R14: 00007fb4d5d3a650 R15: 0000000000615080
[ 820.267837] OOM killer enabled.
[ 820.267838] Restarting tasks ... done."
1750947,2018-03-21 06:39:00 UTC,"This fixed the ""missing LP bug number problem"". Please help trigger the SRU build."
1750947,2018-02-22 05:13:40 UTC,"Commit a222a07920731f3c4967faccab7469af50b428a4 is obviously a little old. So ""Fix Released"" for current series. Only needs some work to get it into xenial."
1750947,2018-02-22 05:42:37 UTC,"reply #5, yes, only xenial needs this commit because artful and bionic already had this commit."
1750947,2018-02-22 05:12:07 UTC,"Sorry, I missed the part about the crashes being in the kernel."
1750947,2018-03-06 02:41:21 UTC,Yes I think that's what we need.
1750947,2018-03-06 03:05:11 UTC,"OK, got it. thanks."
1750947,2018-03-08 03:19:48 UTC,"Already pushed the fix to ubuntu-xenial branch, and this is the debdiff against 3.8. If everything is ok, please trigger the SRU build."
1750947,2018-02-22 03:15:27 UTC,If this is a crash then it's very likely we already have a bug report for it.
1750947,2018-03-05 02:08:10 UTC,"@Daniel,"
1750947,2018-02-22 04:54:23 UTC,"E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 26649288 bytes (151073 ms).
E: [alsa-sink-HDMI 0] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_dump():
E: [alsa-sink-HDMI 0] alsa-util.c: Hooks PCM
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: Slave: Hardware PCM card 0 'HD-Audio Generic' device 3 subdevice 0
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: -25928392 bytes (-146986 ms).
E: [alsa-sink-HDMI 0] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_dump():
E: [alsa-sink-HDMI 0] alsa-util.c: Hooks PCM
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: Slave: Hardware PCM card 0 'HD-Audio Generic' device 3 subdevice 0
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
..."
1750953,2018-02-22 16:13:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1750955,2018-05-22 17:25:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1750955,2020-08-10 00:42:16 UTC,libopencv-dev (3.3.1)
1750958,2018-02-22 08:33:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546919"
1750958,2018-04-23 06:54:41 UTC,"Change abandoned by Hironori Shiina (<email address hidden>) on branch: master
Review: https://review.openstack.org/546919
Reason: The alternative fix[1] was merged."
1750980,2018-02-22 08:02:08 UTC,"StacktraceTop:
 __glXSendError (dpy=dpy@entry=0x55bb0f9b4e50, errorCode=errorCode@entry=0 '\000', resourceID=resourceID@entry=0, minorCode=minorCode@entry=26, coreX11error=coreX11error@entry=false) at ../../../src/glx/glx_error.c:62
 MakeContextCurrent (dpy=0x55bb0f9b4e50, draw=60817467, read=60817467, gc_user=0x55bb0fa72060) at ../../../src/glx/glxcurrent.c:216
 InternalMakeCurrentVendor (dpy=dpy@entry=0x55bb0f9b4e50, draw=draw@entry=60817467, read=read@entry=60817467, ctxInfo=ctxInfo@entry=0x55bb102d8a70, callerOpcode=<optimized out>, threadState=threadState@entry=0x55bb0fd74780, vendor=0x55bb0fb45400) at ../../../src/GLX/libglx.c:823
 CommonMakeCurrent (dpy=0x55bb0f9b4e50, draw=60817467, read=60817467, context=<optimized out>, callerOpcode=<optimized out>) at ../../../src/GLX/libglx.c:1005
 gst_vaapi_texture_glx_put_surface_unlocked (flags=0, crop_rect=0x7ffccbbeadc0, surface=0x7faea408ed90, base_texture=0x55bb1041aca0) at ../../../../gst-libs/gst/vaapi/gstvaapitexture_glx.c:355"
1750983,2018-02-24 09:15:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547733"
1750983,2018-07-26 08:57:41 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.0 release.
1750985,2018-02-23 08:04:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547316"
1750985,2018-07-26 08:57:42 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.0 release.
1750987,2018-02-25 11:37:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547810"
1750991,2018-02-26 22:05:51 UTC,neutron-lbaas is now maintained by the octavita team. I forward this to octavia launchpad but it is now frozen. More recommended way is to file a bug on octavia storyboard (neutron-lbaas project).
1750994,2018-02-26 22:06:36 UTC,neutron-lbaas is now maintained by the octavita team. I forward this to octavia launchpad but it is now frozen. More recommended way is to file a bug on octavia storyboard (neutron-lbaas project).
1750996,2018-02-26 22:07:15 UTC,neutron-lbaas is now maintained by the octavia team. I forward this to octavia launchpad but it is now frozen. More recommended way is to file a bug on octavia storyboard (neutron-lbaas project).
1750998,2018-02-22 22:25:05 UTC,This bug was fixed in the package django-piston3 - 0.3~rc2-3ubuntu3
1750999,2018-02-26 22:07:42 UTC,neutron-lbaas is now maintained by the octavia team. I forward this to octavia launchpad but it is now frozen. More recommended way is to file a bug on octavia storyboard (neutron-lbaas project).
1751000,2018-02-22 09:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1751000,2019-12-02 07:38:41 UTC,In this cycle with B-4.15 Oracle (4.15.0-1030.33) test skipped with instances DenseIO1.8 and failed on VM.Standard1.4
1751000,2019-11-06 07:26:42 UTC,The pmu failure could be found on Oracle B-4.15 as well:
1751000,2018-02-22 08:42:15 UTC,apport information
1751000,2018-02-22 08:42:14 UTC,apport information
1751000,2018-02-22 08:42:13 UTC,apport information
1751000,2018-02-22 08:42:07 UTC,apport information
1751000,2018-02-22 08:42:08 UTC,apport information
1751000,2018-02-22 08:42:06 UTC,apport information
1751000,2018-02-22 08:42:10 UTC,apport information
1751000,2018-02-22 08:42:11 UTC,apport information
1751000,2018-02-22 08:42:09 UTC,apport information
1751006,2018-03-14 19:46:43 UTC,"pcre2 library is not in Ubuntu Main, and therefore cannot be used, at runtime, by such a core package as systemd."
1751006,2018-06-19 11:32:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751006,2018-08-07 02:27:27 UTC,"Maybe we can have `journalctl-grep` package for administrators that use this grep functionality for checking what happened? Nowadays debugging is recognized as foremost computing activity, even chips have special JTAG pins to allow online debugging."
1751006,2019-01-23 17:40:11 UTC,pcre2 was promoted to main today for Ubuntu 19.04.
1751006,2019-10-21 12:29:40 UTC,journactl --grep works in Ubuntu 19.10 (but not 19.04 or older versions).
1751007,2019-07-29 11:47:31 UTC,"Will be good to add some field to support both ""publish"" and ""advanced publish"" for all scopes so customers can switch to the new field and completely ignore the old one (""advanced_published"" as a temporary name)."
1751007,2019-07-30 06:59:40 UTC,"A possible name can be ""aggregated_publish"" / ""combined_published"" / ""final_publish"" / ..."
1751007,2019-07-30 08:00:13 UTC,"Also we need to aggregate in case we have publish on both (""on-success"" or ""on-error"") and in ""on-complete"""
1751007,2019-09-03 14:04:40 UTC,"Reviewed:  https://review.opendev.org/678555
Committed: https://git.openstack.org/cgit/openstack/python-mistralclient/commit/?id=4ecb7dc99af49ff28d6f66288a588205c5e6e0cf
Submitter: Zuul
Branch:    master"
1751007,2019-09-05 18:31:33 UTC,"Reviewed:  https://review.opendev.org/678530
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=9804e74d52ed14d73e18017ba757786ab3def897
Submitter: Zuul
Branch:    master"
1751007,2019-09-13 16:05:30 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1751007,2019-09-13 19:11:26 UTC,This issue was fixed in the openstack/python-mistralclient 3.10.0 release.
1751010,2018-02-22 11:09:29 UTC,"There's a node-engine property that can be used to request a specific nodejs version.For clarity it might be best to introduce a new yarn-version property, which could presumably set node-package-mangager to yarn as well."
1751011,2018-03-01 19:32:30 UTC,Upstream's fix is not something we are keen to change.
1751011,2018-03-09 14:22:25 UTC,The ROS (http://www.ros.org/) team uses qemu and docker to build native arm packages on our buildfarm. So this is a pretty significant roadblock for us as we prepare our next release based on bionic.
1751011,2018-03-13 14:13:48 UTC,https://lists.gnu.org/archive/html/bug-bash/2018-02/msg00093.html
1751011,2018-03-14 07:34:49 UTC,I'd like to know any progress from the qemu community. I feel like it would be long journey to address this problem.
1751011,2018-03-15 15:28:48 UTC,This is upstream LP: #1749393
1751011,2018-03-22 21:45:41 UTC,"<jbicha> slangasek: can you explain the bash 4.4.18-1.1ubuntu1 removal?
<jbicha> because I used sbuild-launchpad-chroot to create an armhf chroot but it is stuck trying to update bash with an error that looks like Debian bug 889869
<slangasek> jbicha: PIE is a security feature, and shouldn't be disabled to work around a bug in qemu-user-static"
1751011,2018-03-22 22:05:41 UTC,"Matthias, please investigate compiling bash using --without-bash-malloc (and then re-enabling PIE in Debian)."
1751011,2018-03-23 16:54:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751011,2018-03-27 15:42:04 UTC,I'm readding the rls-bb-incoming tag. Hope y'all don't mind. I just think this needs to be fixed for the 18.04 LTS release. It doesn't matter to me whether it's fixed/worked around in bash or in qemu as long as it works. :)
1751011,2018-03-27 16:05:44 UTC,"Another use case is in LTSP, where we debootstrap an armhf chroot to netboot raspberrypi clients.
This currently fails in 18.04."
1751011,2018-04-04 16:16:26 UTC,qemu patch proposed at http://lists.nongnu.org/archive/html/qemu-devel/2018-03/msg04700.html
1751011,2018-04-06 09:07:45 UTC,This bug was fixed in the package bash - 4.4.18-2ubuntu1
1751011,2018-02-23 19:58:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751011,2018-02-23 20:00:30 UTC,This has been fixed in Debian's bash (4.4.18-1.1)
1751017,2018-03-07 10:44:25 UTC,"Change abandoned by Steven Hardy (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/546935
Reason: https://review.openstack.org/#/c/547249  landed instead"
1751017,2018-02-22 10:20:51 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/546935"
1751033,2019-12-17 12:41:12 UTC,Upstream report was closed 2018-02-16 as being fixed in version 3.26.2 so fixed in Ubuntu from the 18.04 release.
1751037,2018-02-22 16:07:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751037,2018-02-22 16:20:37 UTC,"The attachment ""0001-Pidgin-Indicate-mute-unmute-status-when-changed-remo.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1751038,2018-02-22 16:07:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751038,2018-02-22 16:20:45 UTC,"The attachment ""0001-Ensure-labelled-buttons-are-shown-for-search-results.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1751039,2018-02-22 16:07:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751039,2018-02-22 16:20:53 UTC,"The attachment ""0001-Fix-Finch-search-results-display-17238.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1751040,2018-03-15 18:49:20 UTC,"Agreed that we may want to filter out extensions that won't participate in returned payload formation. One thing worth noticing is that I don't think we actually send all the data to the client that then filters out unneeded fields, as you seem to imply. Instead, we call db_utils.resource_fields(res, fields) before passing the payload dict to the root api layer, the function that filters out fields not explicitly requested. If that's the case, I am not sure which new API tests you suggest to implement. (The current API behaviour is already as expected; of course additional coverage for the 'fields' feature is welcome if it's not good enough, but this matter is independent of the proposal)."
1751040,2018-03-16 08:58:35 UTC,Hi
1751040,2020-03-24 21:42:11 UTC,Are You still want to work on this? If so we can discuss that during one of our next drivers meeting.
1751040,2020-06-02 19:54:43 UTC,"As we discussed during the PTG this idea makes sense for us.
I will add it to the next drivers meeting agenda to discuss it once again in more details (and hopefully approve officially there).
@Tom, also if You are not going to work on implementation of this, please unassign your self from it so someone else interested in working on it may take it :)"
1751040,2020-06-02 20:28:06 UTC,"Hi,
I will attend the driver meeting this friday. Unfortunately we do not have the bandwidth to do this right now. I do however have a patchset of february 2018 (!! so outdated) if anyone wants to have a look at that feel free to email me."
1751040,2020-06-19 15:00:42 UTC,"During last drivers meeting we approved this RFE. But as there is no volunteer for now to work on implementation, lets keep it approved but not target it for any specific release.
If there is anyone who wants to work on this, please reach out to us here, on OpenStack ML or on #openstack-neutron channel @freenode."
1751042,2018-02-22 14:06:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/546991"
1751042,2018-08-16 07:29:00 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/546991
Reason: With no activity since February, this looks abandoned. Please restore if you plan on continuing to work on this, but it probably also requires a minimal specless blueprint for the stein release since this is a feature add."
1751046,2018-02-22 16:21:02 UTC,"The attachment ""0001-Do-not-rewrite-custom-buddy-icons-already-in-the-cac.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1751046,2018-02-22 16:07:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751068,2018-02-22 14:38:02 UTC,I repeated this bug by installing the system from scratch and updating all the proposed packages
1751068,2018-03-07 07:03:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751077,2018-02-22 15:27:53 UTC,Maybe we should introduce a clean step to unlocks the disks?
1751080,2018-02-25 23:08:38 UTC,"Yeah, we should accept MB etc too. And write error messages that explain how to fix the problem when we can."
1751096,2019-07-03 17:16:39 UTC,We do this in cases we want to now.
1751098,2018-02-25 11:48:59 UTC,"No, I did not make bug report yet, but I've tried a bunch of different kernels to try and find out where the issue started."
1751098,2018-02-25 13:54:29 UTC,"Okay, I filed one:"
1751098,2018-02-26 15:42:06 UTC,"I built the next test kernel, up to the following commit:
1039796b23f7e844ed797ee3adc951a5e3c22b4b"
1751098,2018-02-28 00:43:31 UTC,I am sorry Joseph.
1751098,2018-02-24 15:19:16 UTC,"Kristoffer, did you file your bug report yet? I think I'm experiencing the exact same issue. After Grub, my system hangs with the 4.13.0-36 kernel. I just see a flashing cursor. 4.13.0-32 boots fine."
1751098,2018-04-30 23:55:33 UTC,"After a fresh install of Ubuntu 18.04 (about an hour ago) on my Gigabyte P55W v5, and same problem: right after logging in, everything freezes... and that's about it. I waited for 15 minutes, and nothing happened."
1751098,2018-05-01 19:21:31 UTC,"The original bug reporter is unable to reproduce this bug, so would it be possible for others affected to test the latest mainline kernel?  It is available for download from:"
1751098,2018-07-24 09:32:11 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1751098,2018-04-27 09:19:15 UTC,Hi
1751098,2018-02-24 04:56:50 UTC,I ended up updating to Ubuntu 18.04 dev. An update to the BIOS of my laptop made it completely unstable to the point of not booting most of the time. Ubuntu 18.04 seems to work fine so far.
1751098,2018-04-29 22:49:41 UTC,"Dell XPS 15 - Same issue. I first upgraded Ubuntu 17.10->18.0. That worked but shutdown was very slow. Then I reinstalled 18.04 today to get a fresh start. But after boot, when entering password, laptop freezes completely. I also try ""try Ubuntu"" and that also fails."
1751098,2018-02-22 21:14:48 UTC,"I built the next test kernel, up to the following commit:
b73948811b253d868aba711e1b8cfcc045c9cc50"
1751098,2018-02-22 23:30:15 UTC,"The kernel also has the bug.
Please keep doing the bisect and I will gladly keep trying them."
1751098,2018-02-22 17:58:56 UTC,I started a kernel bisect between 4.13.0-32 and 4.13.0-36. The kernel bisect will require testing of about 7-10 test kernels.
1751098,2018-02-22 18:12:13 UTC,"Joseph, the bisected kernel (4.13.0-33) seems to have the bug. It hangs my laptop just as 4.13.0-36"
1751098,2018-02-22 18:12:15 UTC,That one ( http://kernel.ubuntu.com/~jsalisbury/lp1751098/ ) booted successfully for me.
1751098,2018-02-22 18:41:43 UTC,"Kristoffer, can you run uname -a to confirm you booted the test kernel?  Nicolas reports the test kernel does not boot."
1751098,2018-02-22 17:41:21 UTC,"This kernel (4.13.0-36.40) hangs for me as well, but it's much earlier in the boot process so it doesn't even get to the point where it would ask me for my dm-crypt password. The fallback image (4.13.0-32.35) boots fine though."
1751098,2018-02-22 18:51:36 UTC,"Maybe we are facing different bugs. In my case, it does boot, but it hangs shortly after. If I hurry, I am even able to log in to the desktop."
1751098,2018-02-22 18:46:18 UTC,"$ uname -a
Linux kristoffer-ubuntu-desktop 4.13.0-33-generic #36~lp1751098Commit721530cf07670 SMP Thu Feb 22 17:22:43 UTC 201 x86_64 x86_64 x86_64 GNU/Linux"
1751098,2018-02-22 20:12:47 UTC,"I built the next test kernel, up to the following commit:
9c58aebfd9d8c8d5b156898656c5c180a36e7a63"
1751098,2018-02-22 20:32:37 UTC,Tested the new kernel. It still has the bug.
1751098,2018-02-22 19:02:29 UTC,"Sounds like different bug indeed. For me it hangs pretty much immediately after GRUB and I don't even see the plymouth screen with the Ubuntu logo or the password promt for dm-crypt. Tried many times, same result every time."
1751098,2018-02-22 19:16:14 UTC,"@Kristoffer, yes sounds like a different bug.  I'll continue the bisect with Nicolas.  Probably best to open a separate bug report indeed."
1751108,2018-02-23 12:02:15 UTC,"I think the error message could be improved here, but what it's telling you is that it can't find the target ""deployment"" and that you should use a target of ""dpa"" (this corresponds to the top level target name you want to use from your deployment config file). Also, the ""local"" config should likely just be local.yaml rather than the full path (although that may work too)."
1751108,2018-02-23 21:59:52 UTC,"A nicer error would be good, but in the meanwhile we found out what needed to be done, and yes, we were fumbling the project name. Sorry for the spam!"
1751113,2018-02-23 00:22:35 UTC,"What to do now, please?"
1751113,2018-02-23 10:13:06 UTC,The problem fixed by installing synaptic support.
1751113,2019-08-21 14:13:12 UTC,"Further to comment #4, issue was fixed by installing a package that some Ubuntu flavours/configurations still require."
1751113,2018-02-22 21:11:33 UTC,This is not a bug with the release upgrader rather with some other package that was upgraded during the upgrade process.
1751133,2018-03-14 13:29:00 UTC,"I think we run a dsvm job already, do we need something else?"
1751133,2018-03-14 16:37:04 UTC,"Well, I'd prefer something more functional running locally from tox and failing fast rather than this joke [1]. ;)"
1751134,2018-03-19 19:20:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554326"
1751134,2018-03-24 06:54:40 UTC,"Hi Aleksanda, are you still working on this issue? I would like to work on it. Please let me know."
1751134,2018-03-26 11:04:49 UTC,Hi! Yes I'm still working.
1751135,2018-03-14 12:35:29 UTC,"I have a WIP patch for that, feel free to take it over: https://review.openstack.org/#/c/538338/"
1751139,2018-02-23 17:45:00 UTC,Boot of both ubuntu-mate and lubuntu/lxqt (both 18.04) with kernel 4.15.0-10 in virtualbox:
1751139,2018-02-23 17:26:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751139,2018-12-26 22:56:40 UTC,"When I execute privileged `apt-get upgrade -y` on my Ubuntu 18.04 Bionic Beaver instance in VirtualBox, the overall command fails during update-initramfs with an apparent omission of the recursive flag to the copy file utility."
1751140,2018-02-22 21:16:01 UTC,"further discussion in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732201
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726073
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726116
https://bugzilla.mozilla.org/show_bug.cgi?id=1429692"
1751140,2018-10-04 09:12:06 UTC,nss-pem embeds nss instead
1751141,2021-01-11 13:46:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751143,2018-02-23 05:53:31 UTC,It will be good to have this. Thanks!
1751144,2019-06-17 04:57:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1751144,2019-08-17 04:17:18 UTC,[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]
1751146,2020-10-26 18:28:31 UTC,I added this content as part of https://github.com/evergreen-library-system/Evergreen/pull/101
1751151,2018-06-01 21:17:04 UTC,"ok, I also could add the quotes and now netplan accept the file:"
1751151,2018-07-19 09:57:11 UTC,Hi!
1751151,2018-03-19 02:21:01 UTC,This bug was fixed in the package netcfg - 1.142ubuntu6
1751151,2018-02-26 14:58:43 UTC,"Good catch, this is a bug in netcfg."
1751151,2018-02-23 00:22:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1751151,2018-06-01 21:04:17 UTC,"Hi, I am at Ubuntu 18.04 LTS (complete updated) and also can't apply my 01-netcfg.yaml:"
1751151,2018-06-01 21:06:49 UTC,"ups, I pasted my modified nameserver line with the duplicate ""addresses:"" - please ignore this"
1751153,2018-02-22 22:26:42 UTC,BTW: using lxd provider for juju won't reproduce this issue as it goes down a slightly different path. lxd provider uses cloud-init's NoCloud datasource so it pools user-data/meta-data earlier in cloud-init which will not exhibit this race condition.
1751153,2018-03-13 14:13:13 UTC,we are unlikely to make a change in juju-1.X to address this.
1751153,2018-03-13 14:21:58 UTC,"We seem to be doing:
    defer func() {
        cause := errors.Cause(err)
        switch {
        case cause == apiagent.ErrDenied:
        case cause == errAgentEntityDead:
        case params.IsCodeUnauthorized(cause):
        case params.IsCodeNotProvisioned(cause):
        default:
            return
        }
        err = ErrConnectImpossible
    }()"
1751153,2018-03-13 14:25:10 UTC,"Is there a reason you want to delete /var/lib/cloud instead of just provisioning a new instance? It seems like you're already in a virtual machine, and it might be cleaner to just stand up another one."
1751155,2018-02-23 01:25:30 UTC,Please post your Inkscape version (copy paste from About menu) and you system info.
1751155,2018-02-26 00:55:26 UTC,"Specifically, if you're using a Mac + multiple monitors, find help in the FAQ:
https://inkscape.org/en/learn/faq/#windows-appear-screen-multiple-monitor-setup"
1751155,2019-05-14 13:14:06 UTC,"Closing as there has been no response for 30 days. If this is still an issue with the latest version of Inkscape, please go to https://inkscape.org/report. Thank you!"
1751157,2020-05-01 06:51:47 UTC,The option is available in git now
1751159,2019-12-11 05:20:11 UTC,"Oh gosh, somehow I never saw this.  I guess I wasn't subscribed.  I didn't find the Last Updated viewing option until after this was posted."
1751159,2018-02-22 22:55:14 UTC,@brynn: Would you like to suggest a list of colors and sections?
1751159,2019-12-11 12:12:52 UTC,"That's actually a bug that started when the keys were updated for 1.0. The 1.0 version will look alright, as far as I understand (haven't seen it yet)."
1751160,2018-02-22 22:54:45 UTC,"@Jabier: Do you remember what you meant by ""and a fixed position sort section menu for a 12"" ? I do not understand that part."
1751160,2018-02-22 23:12:43 UTC,"Hi Maren.
Forget ""and a fixed position sort section menu for a 12"" because if fixed the menu, make part of the menu inaccessible. So we dont like it ;)
Cheers."
1751160,2018-02-23 00:40:47 UTC,"Great, thank you!"
1751161,2018-02-23 10:08:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751163,2018-02-22 23:31:01 UTC,Patch proposed: https://review.openstack.org/#/c/546621/
1751164,2018-03-27 17:26:35 UTC,https://review.openstack.org/556987
1751165,2018-02-23 00:09:02 UTC,"I did not find a straightforward way, which is why I chose something that I felt did not require translation (""man page"" is a proper name for me - I'd not even translate it if possible, at least in languages with latin alphabet)."
1751165,2018-02-23 00:56:59 UTC,"Want to close as wontfix, or keep open for someone to take up in case they want to invest some time into a minor issue?"
1751165,2018-02-27 21:55:57 UTC,"You decide - for me it's ""wontfix"", but if you think it adds non-negligible value feel free to keep open."
1751165,2019-06-16 16:44:39 UTC,Closing as it's unlikely to be ever fixed.
1751166,2018-02-23 14:21:04 UTC,"confirmed on Windows 10, Inkscape 0.92+devel (9d6b0e8, 2018-02-18)"
1751168,2019-06-11 04:17:18 UTC,[Expired for kolla because there has been no activity for 60 days.]
1751168,2019-04-11 06:56:54 UTC,I can't see any changes in the swift image code that would fix this so I'll leave it open.
1751168,2019-04-10 10:15:27 UTC,"I have seen swift syncing working in Rocky, could you retest?"
1751168,2018-05-08 03:58:28 UTC,It's been a long time and no response. Could someone have a look?
1751168,2019-04-11 01:47:42 UTC,"Hi Mark,thanks for replying. The bug was created one year ago, it was in Pike release. If it has already fix in the latest release , then feel free to close this bug."
1751171,2018-02-23 03:18:32 UTC,"Just to add to this, pcbnew layer visibility and other rendering options change the kicad_pcb file. Those options have nothing to do with the design itself, just how it's presented to the user, so they should not be part of the pcb file. Consider: you open the project to look at the layout, and in doing so you turn layers off and on. That touches the design file, so the user will be asked to save the file before closing the program. But that's not a design change, it's a viewing thing. So please don't add visibility controls to the project or pcb file!"
1751171,2018-02-23 13:42:50 UTC,this affects me too.
1751182,2018-05-09 11:20:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751182,2019-08-05 03:52:07 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1751186,2019-03-22 03:47:56 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1751186,2018-09-24 14:47:04 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1751186,2018-08-31 13:45:20 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/598953"
1751186,2018-08-10 10:17:28 UTC,"Change abandoned by Chen (<email address hidden>) on branch: master
Review: https://review.openstack.org/581403
Reason: In favor of approach https://review.openstack.org/#/c/588943"
1751186,2018-09-21 12:02:16 UTC,"Reviewed:  https://review.openstack.org/598953
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4c27443e6fe91095318204e7ec86ef97ad5b9efa
Submitter: Zuul
Branch:    stable/rocky"
1751186,2018-07-12 09:54:56 UTC,"I did this in current master(Rocky), the db records did exists, but yes, InstanceGroup.Members won't have the deleted member so it might not affect the scheduling process, but still, growing db records could be a problem."
1751186,2018-08-08 22:52:23 UTC,See related (duplicate) bug 1778804.
1751186,2018-02-23 14:35:22 UTC,"That looks fine to me, given we lazy-load the members field when calling it. So, I'm pretty sure the InstanceGroup.members shouldn't be saying that 3b9aa471-612f-4967-a405-574241e84aa0 is in there."
1751186,2018-08-31 10:14:06 UTC,"Reviewed:  https://review.openstack.org/588943
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5162a9a1de3cf4d652707d8a1ff73b7b136b8053
Submitter: Zuul
Branch:    master"
1751186,2018-03-22 07:40:44 UTC,"Hi, there. Does anyone work on it?"
1751186,2018-03-22 07:58:43 UTC,Let me try work on it
1751186,2018-03-20 01:56:35 UTC,"I‘m sure.Under the same conditions，many times, the results are the same.
nova version: Pike"
1751191,2018-02-23 04:23:31 UTC,Another video with an audio player and a progress bar and counter sometimes going backwards
1751191,2018-03-20 18:00:03 UTC,"Hello, can you please try the suggestions provided here?
https://www.virtualbox.org/ticket/13653"
1751191,2018-03-20 18:00:33 UTC,specially the CR_RENDER_FORCE_PRESENT_MAIN_THREAD=0 export in /etc/environment or similar place
1751191,2018-04-26 02:05:02 UTC,I had exactly the same problem with Ubuntu Mate 18.04. That problem disappeared when I switched from the Compiz compositor to the Marco Compton GPU compositor
1751191,2018-04-26 09:06:40 UTC,Ubuntu 16.04 and Virtualbox 5.2 is a combo not provided by Ubuntu
1751191,2018-04-26 09:06:51 UTC,please try something in the archive
1751191,2018-04-27 18:29:22 UTC,"Why should I try an older version with more unsolved problems. I prefer the one bug I know! For my use of Ubuntu 16.04 VM to support Banking and PayPal, I can live with the problem."
1751191,2018-04-27 19:43:38 UTC,">Besides your last remark is somewhat stupid, I run a host OS and use 4 VMs for different >purposes. I do not change my whole set up, because one guest Ubuntu 16.04 has a problem. It >would be easier to swap that one distro. The host OS Xubuntu 18.04, the other 3 VMs (Windows XP >from 2002, Xubuntu 18.04 and Ubuntu Mate 18.04) have no problem with 3D acceleration of now >version 5.2.10 of Virtualbox.
"
1751192,2019-09-27 09:03:33 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1751192,2019-05-24 16:50:38 UTC,"Reviewed:  https://review.opendev.org/556751
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e822360b6696c492bb583240483ee9593d7d24e1
Submitter: Zuul
Branch:    master"
1751192,2018-03-27 04:29:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/556751"
1751192,2018-02-26 01:05:28 UTC,"@tssurya we have a fix for this already in Newton. I need to rebase it to master. Suggest that you don't waste time on this, I'll send it up soon."
1751192,2019-05-23 01:35:28 UTC,"I'm not sure why this was changed from Wishlist => Low, but AFAICT there isn't a defect in the existing functions archive_deleted_rows provides and this is talking about adding an enhancement. Changing this back to Wishlist thusly."
1751192,2018-02-23 04:45:25 UTC,"It it true that we do not have a way of archiving records according to the time of deletion, the ""delete_at"" field could be used along with adding a new tag to nova-manage archive_deleted_rows. The points mentioned by the reporter for wanting this are noted and it would certainly be helpful to delete time range based records."
1751193,2018-06-25 06:12:50 UTC,"@kevin-zhao, are you working on this, if not can I assign it to myself?"
1751193,2018-06-25 07:39:43 UTC,Yes I already submitted a patch. Sorry about that. I forgot to link thepatch with this bug.
1751193,2019-02-22 04:58:34 UTC,"Reviewed:  https://review.openstack.org/633371
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=d0a7940981bb123bfc12d4ed2d24a4bf50e513e4
Submitter: Zuul
Branch:    master"
1751204,2018-02-23 09:00:55 UTC,Confirmed with 2.1.0-beta1 (build 2.1 r6513)
1751204,2020-03-24 15:37:48 UTC,"fixed in https://github.com/mixxxdj/mixxx/pull/2307
""keep the library focused when any deck controls or the overview are clicked"""
1751205,2018-03-12 23:32:38 UTC,"Hi sonu, thanks for the bug report!
The obvious fix here would be for Congress to reject requests with non 'latin-1' characters."
1751209,2018-03-12 23:50:38 UTC,"Hi Sonu,"
1751217,2018-02-23 09:06:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547330"
1751230,2018-02-23 12:27:08 UTC,"The attachment ""dep package rebuilt without postinst"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1751245,2018-02-23 17:01:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751248,2018-02-27 14:32:22 UTC,Possibly installing via source the package gnutls-3.6.x fixes the problem.
1751248,2020-04-17 08:22:56 UTC,"Thank you for your bug report. Is that still an issue? If so could you attach the output of
$ dpkg -l | grep gnutls"
1751248,2020-06-17 04:17:19 UTC,[Expired for glib-networking (Ubuntu) because there has been no activity for 60 days.]
1751249,2018-03-27 10:16:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751249,2018-03-16 12:06:44 UTC,"> For a possibly-reusable example of this from the joule images, see:
>
>   git+ssh://git.launchpad.net/~vorlon/tuchuck/+git/uc16-build-script
"
1751249,2018-03-15 21:37:39 UTC,"On Thu, Mar 15, 2018 at 05:15:37PM -0000, Oliver Grawert wrote:

> nontheless, we need the ""content:"" directive on a ""role: system-data""
> partition working for a customer project soon where some udev rules (and
> other files) need to be pre-installed in the system-data partition.
"
1751249,2018-03-15 16:50:40 UTC,"@ogra: I just performed some experiments while trying to reproduce this bug, but my observations are a bit different than yours. Actually it's still more or less a bug, but not as severe. The story:"
1751249,2018-03-14 09:29:20 UTC,"Hey, what is the forecast time-wise on this being fixed & released?"
1751249,2018-02-23 12:49:45 UTC,"$ find build/unpack/gadget/writable/
build/unpack/gadget/writable/
build/unpack/gadget/writable/meep.txt
build/unpack/gadget/writable/system-data
build/unpack/gadget/writable/system-data/etc
build/unpack/gadget/writable/system-data/etc/foo.txt"
1751249,2018-02-23 11:45:51 UTC,"building with -b ./build creates the following (the proper files from the gadget copied via ""content:""):"
1751249,2018-03-15 17:15:37 UTC,"@sil2100 weird, I wonder why I always ended up with the opposite but will re-check it again  ..."
1751252,2018-05-10 13:31:34 UTC,"Hello Jean-Baptiste, or anyone else affected,"
1751252,2018-05-17 06:52:44 UTC,"The verification of the Stable Release Update for ubiquity has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1751252,2018-05-17 06:52:40 UTC,This bug was fixed in the package ubiquity - 18.04.14.1
1751252,2018-05-14 07:21:20 UTC,"Hi,"
1751252,2018-05-13 12:51:09 UTC,I can confirm that the package version from bionic-proposed solves the problem.
1751252,2018-05-08 16:38:11 UTC,This bug was fixed in the package ubiquity - 18.10.1
1751252,2018-05-03 10:29:41 UTC,"A patch to fix the crash is here:
https://bugs.freedesktop.org/show_bug.cgi?id=98883#c6"
1751252,2018-05-08 12:29:01 UTC,"Ah, I'm sorry, I didn't see that there had been a bionic upload for this since the vcs was untouched and there was nothing in the unapproved queue... I just uploaded ubiquity for this to *cosmic* - not bionic yet. If it gets approved it should be in the next day's dailies and hopefully someone can test those to verify it's good."
1751252,2018-05-07 13:53:03 UTC,"An upload of ubiquity to bionic-proposed has been rejected from the upload queue for the following reason: ""All looks good with the package itself, but sadly there seems to be some leftover .gladep file included with the changes. Could you reupload without it? Or, if it's needed, just mention that in the bug? Thank you!""."
1751252,2018-05-04 06:41:12 UTC,"The patch https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056 did work for me on my mid-2017 MacBookPro (HW, not VM)."
1751252,2018-05-03 22:55:50 UTC,I tried the patch for /usr/lib/ubiquity/ubiquity/misc.py in a virtual machine.
1751252,2018-05-03 19:19:28 UTC,Fix for ubiquity proposed here: https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056
1751252,2018-06-01 22:04:05 UTC,"For anyone looking for how to use this fix with the current Ubuntu 18.04 installation ISO, this page ( https://askubuntu.com/a/1040322/14601 ) has a good description how to use the patch produced above in Comment 37."
1751252,2018-05-08 14:25:05 UTC,Removed the .gladep file; it seems to have crept in by error during the git migration (also in my cosmic upload) and uploaded bionic. Thanks and sorry cyphermox if this treads on your toes.
1751252,2018-07-25 19:11:33 UTC,Could a maintainer review the patch there?
1751252,2018-07-26 02:12:00 UTC,The patch says:
1751252,2018-07-25 22:22:44 UTC,The XLockDisplay is needed so that an error in another thread does not get reported as a failure of XShmAttach.
1751252,2018-12-12 05:11:58 UTC,I think the fix is in Ubuntu 18.04.1 (not 18.04) so please use 18.04.1:
1751252,2018-12-12 04:26:49 UTC,an  able to upgrade from 17.04 to 18.04
1751252,2018-12-06 23:05:41 UTC,"In the Live Version on MacBook Pro 2015 (13 inches, Retina) I changed the 'Screen Scale' from 200% to 100%, settings > Device > Display, and solved!"
1751252,2018-11-05 15:49:07 UTC,"Untargetting from cairo/bionic, the ubiquity fix is enough there"
1751252,2018-08-25 13:31:43 UTC,-- GitLab Migration Automatic Message --
1751252,2018-07-26 02:40:07 UTC,"> XShmAttach returns True to indicate it successfully queued the request.
> It does not fail to queue the request.
>
> If the server fails to process the request successfully, then it sends an
> error response.
>
> It would be helpful to understand why you are expecting an error response.
"
1751252,2018-07-25 20:23:34 UTC,"@Sebastian: I don't know who you count as a maintainer, but I'll take a look..."
1751252,2018-07-26 02:29:41 UTC,"(In reply to Daniel van Vugt from comment #14)

> The patch says:
>
> ""XShmAttach returns True, even on error.""
>
> and
>
> ""XShmAttach is hard-coded in libXext to return True, even on failure.""
"
1751252,2018-07-26 02:16:39 UTC,"(In reply to Daniel van Vugt from comment #11)

> attachment 139297 [details] [review] mentions multiple times ""why"" it is
> necessary to make it synchronous. Because it's impossible to detect errors
> in XShmAttach otherwise.
"
1751252,2018-05-03 10:27:18 UTC,"Created attachment 139297
Handle-XShmAttach-failures-v1.patch"
1751252,2018-07-26 02:10:08 UTC,"(In reply to Daniel van Vugt from comment #11)

> The reasons are detailed in attachment 139297.
"
1751252,2018-07-26 01:58:51 UTC,So I think reliability should be the first priority.
1751252,2018-07-26 01:53:30 UTC,It's been a few months so my memory is not completely clear. I do however think Uli's statement is incorrect in the final two sentences:
1751252,2018-07-26 01:07:43 UTC,XSetErrorHandler() is not appropriate for use with multi-thread code.
1751252,2018-07-26 02:20:55 UTC,Great. I would be happy to see alternative solutions but also don't need to be involved at all...
1751252,2018-05-03 07:31:18 UTC,Please report crash files by running this command:
1751252,2018-05-04 01:39:50 UTC,"You will get the same behaviour using the cairo fix too:
https://bugs.freedesktop.org/show_bug.cgi?id=98883#c6"
1751252,2018-05-02 14:02:25 UTC,Ubiquity also crashes inside a virtual machine (VirtualBox) running on a non-HiDPI host machine.
1751252,2018-05-01 08:00:30 UTC,Here's the crash with GDK_SYNCHRONIZE=1. It appears to be graphical. And I have a theory this maybe only happens on machines that default to hi-DPI (scale 200%) in the live session...
1751252,2018-05-01 07:30:43 UTC,The X error (from comment #3) is:
1751252,2018-04-30 07:19:00 UTC,And my own crash from 18.04 final:
1751252,2018-04-30 06:58:11 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15"
1751252,2018-04-28 20:36:47 UTC,"I am getting the same issue, same error. Crashes once I reach the progress screen of 18.04 installation."
1751252,2018-04-26 22:14:52 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1751252,2018-04-03 14:30:06 UTC,Marking Incomplete for glib per the previous comment.
1751252,2018-03-02 13:43:32 UTC,"Steve, what makes you think it might be a glib issue?"
1751252,2018-02-23 12:16:30 UTC,"StacktraceTop:
 XPending (dpy=0x1384000) at ../../src/Pending.c:55
 client_message_to_wire (event=0x7ffde5091650, ev=0x0) at ../../../../../gdk/x11/gdkasync.c:199
 _gdk_x11_send_client_message_async (display=<optimized out>, window=140728446031488, propagate=1935767139, event_mask=140728446031480, event_send=0x0, callback=0x1291c00, data=0x2939b9c) at ../../../../../gdk/x11/gdkasync.c:263
 ?? ()
 ?? ()"
1751252,2016-12-07 23:52:04 UTC,"XLockDisplay() would work, and there is no bug if there is only one thread (i.e. when XInitThreads() is not called), but XLockDisplay() is not necessary."
1751252,2018-05-03 07:22:06 UTC,I can reproduce this issue on xps13 9350. crash report is attached.
1751252,2016-12-02 17:01:40 UTC,"Correct me if I'm wrong, but XLockDisplay() says that there is no other thread that could ""steal the next request"", right?
Also, feel free to correct me, but cairo should be calling XLockDisplay() before doing ""SHM stuff""."
1751252,2016-11-28 20:31:20 UTC,"pool->attached = XNextRequest(dpy) - 1;
after the XShmAttach would work, yes.
It would then have a sequence number either equal to that of the XShmAttach request or to that of a subsequent request, if there was one."
1751252,2016-11-28 19:40:47 UTC,"I wonder whether the fix of setting the pool->attached = XNextRequest(dpy)
after the XShmAttach would work.  That's effectively delaying the shmdt until after whatever the next X request is after the attach has completed; who knows what that is, but as long as there is one (ahem, that might be a bit of an assumption; could we just add a dummy?) then it should complete.  Not got a clue what the perf would be."
1751252,2016-11-28 02:03:49 UTC,"_cairo_xlib_display_fini_shm sets pool->attached to XNextRequest() assuming
the approaching XShmAttach() will be the next request.
https://cgit.freedesktop.org/cairo/tree/src/cairo-xlib-surface-shm.c?id=3f1a6f7225e31057a8af9313f051a1d311df0c69#n602"
1751252,2018-05-01 08:06:15 UTC,WORKAROUND:
1751252,2018-05-01 09:16:29 UTC,Stack trace with debug symbols (mostly).
1751252,2016-12-07 17:09:35 UTC,"XLockDisplay only works if XInitThreads was done, and that his highly not recommended as it slows Xlib down enormously (because it was very badly implemented with fine-grained locking)."
1751252,2018-05-01 09:27:37 UTC,Ignore comment #16. Negative offsets appear to be valid: https://developer.gnome.org/gdk3/stable/gdk3-Cairo-Interaction.html#gdk-cairo-set-source-pixbuf
1751252,2018-05-01 09:20:40 UTC,This looks odd. We start with a 16x16 icon upscaled to 32x32 (scale=200%) but the pixbuf_x/y offset seems to be negative (memory underrun?). Is that a faulty attempt at rendering 32x32 from 16x16 input?
1751252,2018-05-02 10:06:02 UTC,So it sounds like a race between Xorg and the ubiquity perms dropping which then breaks Xorg's ability to authenticate XShmAttach used in cairo.
1751252,2018-05-02 09:55:40 UTC,"Given that XShmAttach can fail (you can google the reasons), I think maybe we need to handle that in ubiquity/cairo and fall back to an alternative rendering method."
1751252,2018-05-02 09:52:12 UTC,"Unfortunately I can't tell what in shm_access is failing exactly because gdb skips straight from shm.c:314 back to the caller. So that suggests this code path, but I can't verify it:"
1751252,2018-05-02 08:47:39 UTC,Getting closer. It's this failing in the Xorg process:
1751252,2018-05-02 08:19:40 UTC,"Possibly relevant to permissions: The uid of this process changed from 'root' in 17.10 (where it works), to 'ubuntu' in 18.04 (where it doesn't work)."
1751252,2018-05-02 05:22:41 UTC,The BadAccess from ShmAttach is coming from the Xorg process somewhere in here:
1751252,2018-05-02 10:02:58 UTC,"OK, I can now reproduce the problem at scale=100%. The trick is to slow down the installer with GDK_SYNCHRONIZE=1. So this is just a race condition, usually triggered by slower rendering of scale 200%, but can be triggered other ways."
1751252,2018-05-02 03:42:31 UTC,"This one also started in version 18.04.11:
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15"
1751252,2018-05-02 03:41:05 UTC,"According to this page, the problem possibly started in ubiquity version 18.04.11:
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524"
1751252,2018-05-01 23:59:36 UTC,Here is the backtrace (bt f) with debug symbols.
1751252,2018-05-01 14:02:46 UTC,On an Dell XPS 9360 with a 3200x1800 display it also defaults to 200% and I reliably reproduce this bug with the 18.04 final image.
1751252,2018-05-01 13:36:45 UTC,"It has been brought to my attention by a community user, that the workaround (change scale from 200% to 100%) found in comment#14 works."
1751252,2018-05-01 11:00:43 UTC,"Correction:
Possibly worth noting is that size==4096 at scale 200%, and size==1024 at scale 100%."
1751252,2018-05-02 04:01:45 UTC,Thanks @pjsingh5000. Your attachment shows the python stack ends at:
1751252,2018-05-01 10:32:23 UTC,Here's the offending source code up to the failing X call. I'm not so sure that the math is right (or how getting it wrong might trigger this bug)...
1751264,2018-02-26 16:08:16 UTC,"Hi,"
1751268,2018-08-21 04:51:38 UTC,"I don't know if this will help, but I have an old Centrino i5 mobile running 4.18.1 as a media pc and if I connect an external monitor and boot I get a hard crash of the PC. I managed to get a complete dmesg just before the hang."
1751268,2018-05-14 20:12:19 UTC,"Yes, that self-test thing was the delay early in boot with the simply-configured drm-tip kernel.  Thanks!"
1751268,2018-05-11 08:36:40 UTC,Per logs you have selftests enabled:
1751268,2018-05-10 15:56:45 UTC,"Created attachment 139469
dmesg from a successful boot with drm-tip 4.17.0-rc4, and a simpler .config."
1751268,2018-05-04 12:26:58 UTC,"Alec, any updates from you on this?"
1751268,2018-05-04 13:50:00 UTC,"Jani, like to comment or add something to https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-intel.html?"
1751268,2018-05-04 13:08:05 UTC,No update since the Fedora suggestion above.
1751268,2018-04-27 14:53:09 UTC,"I just asked the Fedora bugzilla about what patches they're putting on to their rpms, and they suggested:"
1751268,2018-09-12 08:34:45 UTC,"Alec, do you still have the boot failure?"
1751268,2018-05-10 15:55:33 UTC,"Interesting development here.  I decided to try the latest drm-tip (4.17.0-rc4) and see what happens.  It died: but looking at it harder, it seems my working drm-tip (4.16.0-rc7) had a much simpler .config file.  I think the difference is I compiled the new one as root, which picked up all the config settings from my currently running fedora 4.14 kernel, while doing it as a normal user for 4.16 did not."
1751268,2018-09-12 13:50:22 UTC,"I do: even with the current Fedora Kernel (4.17.19) and the latest Lenovo BIOS (which got updated recently, presumably for spectre mitigation).  Just verified this when booting this morning (accidentally chose the wrong kernel in grub)."
1751268,2019-06-17 07:06:22 UTC,"Alec, any updates here? Did you get any chance to bisect the results?
Priority is updated as the issue isn't in drmtip."
1751268,2018-09-21 18:41:21 UTC,"ok, all's not wine and roses.  When exiting X, it goes into the same style lockup as used to happen on boot.  Which includes crashing so hard that often times (but not all the time) the BIOS can't find the boot disk after the next power cycle."
1751268,2018-10-21 18:43:07 UTC,"(In reply to Alec Habig from comment #36)

> ok, all's not wine and roses.  When exiting X, it goes into the same style
> lockup as used to happen on boot.  Which includes crashing so hard that
> often times (but not all the time) the BIOS can't find the boot disk after
> the next power cycle.
>
> At least the bug moving further back in the chain means I can do some work,
> and investigate a running system.  Thank goodness I didn't uninstall the
> (still happily working) kernel-4.14.18-300.fc27.x86_64
"
1751268,2019-01-17 02:55:09 UTC,"Sorry for the long silence.  Going has been slow: it takes a while to do a tweak/test/reboot/hang cycle.  Especially since the disk controller gets munged upon the bug happening, even persisting across a power cycle (!) about 50% of the time (I have no idea how such a thing is even possible).  And, this device is my ""get work done"" laptop, using the 4.14 kernel which is perfectly happy."
1751268,2019-02-04 19:45:33 UTC,"Not sure if helpful, but I had similar issue - machine would not boot if (only) using external monitors. My computer is a Dell Latitude 5590; it had previously booted, upon power up, with the machine closed, thus using only external monitors."
1751268,2019-03-10 14:51:55 UTC,Just accidentally booted into fedora's 4.20.13-200.fc29.x86_64  (have been happily running the drm-tip)... and it worked!
1751268,2019-04-04 18:03:36 UTC,nuts.  Going to 4.20.15-200.fc29.x86_64 failed again... and backing up to 4.20.13-200 also failed.  Tricked by a race condition into thinking that that version actually worked?  Bad interaction with some other update applied since?  Dunno.
1751268,2019-04-18 08:52:20 UTC,"drm-tip works, nothing in dmesg to indicate failure. Pretty much the only way to get progress is to get a bisect result."
1751268,2019-06-17 14:22:29 UTC,"Bisecting is a manual process, since it's some option (or combination thereof) enabled in Fedora's .config that's the problem rather than a bad commit which git can help with."
1751268,2019-07-09 13:51:03 UTC,Closing this issue as NOTOUTBUG.
1751268,2018-04-27 14:08:40 UTC,"Created attachment 139175
full journalctl -b -1 -l dump obtained after being able to issue a clean reboot via sssh."
1751268,2018-09-21 15:33:23 UTC,"So since last week, kernel-4.18.7-100.fc27.x86_64 came out on the Fedora updates repo.  Tried it just now in the process of looking at the next batch of options differences... and it didn't crash!  And all the other drivers I need on this laptop are enabled (which wasn't the case with your drm-tip kernel)."
1751268,2018-04-27 14:07:57 UTC,"sshing in let me continue to work on shell in the ssh session, after the console hung upon exiting.  dmesg reports continued ""flip timeout"" errors as kms flails."
1751268,2018-03-30 13:26:47 UTC,"Will try.  Am not optimistic we'll get much, however, as the crash occurs before syslogd can write anything."
1751268,2018-04-27 09:32:28 UTC,"I also don't see an actual crash or hang here anyway. Sure, the display may be toast, but per the logs systemd gracefully shuts down on power button press. Can you ssh into the machine?"
1751268,2018-02-27 19:04:17 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1751268,2018-04-27 09:39:12 UTC,"Finally, the Optimus stuff have always been a pain. Life suddenly feels too short when debugging issues with them. I know it sucks for you as a user, but please understand that they're really hard for us too. We only have control over one piece of the puzzle, without much clues of the whole."
1751268,2018-02-28 11:46:04 UTC,"4.13.0-32.35: Boot
4.15.0-10.11: Does not boot
4.16.0-041600rc3.201802261351: Does not boot"
1751268,2018-02-28 19:06:18 UTC,We can perform a kernel bisect to identify the commit that introduced this regression.  We first need to identify the last kernel that did not have this bug and the first that did.
1751268,2018-03-29 17:26:07 UTC,"Created attachment 138431
A photo of some of the kernel spew."
1751268,2018-03-29 19:15:32 UTC,Similar Fedora F27 bug:
1751268,2018-03-30 12:27:18 UTC,"HI, can you try with latest drm-tip (https://cgit.freedesktop.org/drm-tip and please add drm.debug=14 module parameter, and attach dmesg from boot to reproducing the problem. Thanks."
1751268,2018-02-23 13:30:07 UTC,This change was made by a bot.
1751268,2018-03-30 14:24:13 UTC,"Created attachment 138444
dmesg from initial boot into single user mode"
1751268,2018-03-30 14:24:57 UTC,"Created attachment 138445
dmesg from boot into runlevel 3 after ntfs filesystems removed"
1751268,2018-03-30 14:30:31 UTC,"ok, boot success!  First try fell into single user mode due to ntfs filesystems the drm-tip kernel didn't like.  (the first dmesg attachement)."
1751268,2018-03-30 15:52:01 UTC,"Narrowed down the possibilities: just fished the 4.16.0-rc7 rpms for f28 out of koji: same crash, same lack of any entries into /var/log/messages whilst doing so.  So, the problem isn't fixed in the newer kernel: it them must be something that's in the Fedora kernel and not in the drm-tip kernel."
1751268,2018-03-30 14:25:57 UTC,"Created attachment 138446
dmesg including logging after X started"
1751268,2018-04-25 11:54:52 UTC,"[    3.562059] bbswitch: loading out-of-tree module taints kernel.
[    3.562266] bbswitch: version 0.8
[    3.562272] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.VID_
[    3.562278] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG_.VID_
[    3.562286] ACPI Warning: \_SB.PCI0.PEG.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20180105/nsarguments-100)
[    3.562634] bbswitch: detected an Optimus _DSM function
[    3.562644] pci 0000:01:00.0: enabling device (0000 -> 0003)
[    3.562676] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on"
1751268,2018-04-27 09:30:13 UTC,"(In reply to Jani Saarinen from comment #18)

> There are similar issues seen on many bugs eg. on IVB:
> https://bugs.freedesktop.org/show_bug.cgi?id=104573.
> Ville, any idea for those?
"
1751268,2018-04-27 06:22:51 UTC,"There are similar issues seen on many bugs eg. on IVB: https://bugs.freedesktop.org/show_bug.cgi?id=104573.
Ville, any idea for those?"
1751268,2018-04-26 20:17:21 UTC,"Created attachment 139147
/var/log/messages from that corresponding session, including an unfortunately sparse record of the actual hang.  Last line in the dmesg corresponds to 14:44:44 in this full log."
1751268,2018-04-25 11:46:09 UTC,"Jani, any advice here?"
1751268,2018-04-26 20:15:44 UTC,"ok.  First, a note that yesterday and today's test were with kernel-4.15.17-300.fc27.x86_64"
1751268,2018-04-26 20:16:23 UTC,"Created attachment 139146
dmesg from drm.debug=14 clean boot (which then hung after this log was copied...)"
1751268,2018-04-25 18:11:24 UTC,"... and, to close the loop: 4.14.18 continues to work great (well, without bumblebee now, because it's uninstalled), as does windows 7 (dual-booted)."
1751268,2018-04-25 18:07:44 UTC,"Slight correction - my first attempt to boot with discrete graphics enabled was foiled by there being a second bios setting that tries to autoset the graphics cards, despite me having just manually set it.  REALLY forcing discrete graphics off got me back to the exact same ""hang, doesn't write to syslog, but I could take a photo of it"" problem as started this thread.  Same kernel dump about ironlake and drm."
1751268,2018-04-25 17:49:21 UTC,"Created attachment 139108
dmesg from boot with nouveau instead of proprietary driver."
1751268,2018-04-25 17:48:28 UTC,Good idea Jani!
1751268,2018-04-26 07:07:40 UTC,"(In reply to Alec Habig from comment #11)

> Created attachment 139108 [details]
> dmesg from boot with nouveau instead of proprietary driver.
"
1751269,2018-02-23 13:15:08 UTC,"This is more visible. When selecting the window, the problem disappears. Some refresh issue?"
1751274,2019-06-16 15:27:26 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape-docs/documentation/issues/4
1751275,2018-02-23 13:26:38 UTC,"Plz help me, i couldn't find out what error occur it"
1751279,2018-03-22 06:29:07 UTC,"I have discovered that it works fine to make the offer in the client model, and consume it into the server model using a name of your choosing (ie offer the client rather than the more obvious offer the service). So charms using the remote application name can continue to do so using CMR, provided they are in the consuming model, and no functionality has been lost. It is still not ideal, but we are in the same situation as without CMR."
1751279,2018-03-14 03:15:14 UTC,"(although PostgreSQL could certainly trust the data it finds in the PostgreSQL side of the relation settings, the UX is quite poor and the data propagated as new units are brought up)"
1751279,2018-02-23 15:20:52 UTC,"@jameinel The operator of the client charm would need to backup the token somewhere, so it could be reused when redeploying. Every client charm would need to provide some mechanism to retrieve the token. I think the user experience here is worse than adding an action on the server to map relations to credentials (which certainly isn't ideal, but possible)."
1751279,2018-03-14 03:07:26 UTC,"per-relation configuration may be a solution, which has been discussed in the past. If the operator could 'juju relation-set postgresql db:0 dbuser=foo', we would have a standard mechanism for charms to use to allow operators to assign an identity to a remote charm. TBH I'm not sure if this is a major UX improvement over adding an action to do the same thing (juju run-action --wait --leader postgresql set-dbuser relation=db:0 user=foo)"
1751279,2018-03-13 14:37:10 UTC,"I think this is certainly something worth thinking about. The difficulties of ""not allowing clients to say who they want to access as"", but needing the ability to re-use a pre-existing identity is difficult.
Even if we didn't have anonymization, cross-model relations would mean that each new deploy should show up as a different identity. I suppose you could try to set up a chain-of-trust that ""I am application foo in model UUID X-Y-Z"", and find a way to trust that nobody else could pretend to be a model UUID X-Y-Z with name foo."
1751279,2018-02-23 14:55:06 UTC,"The postgres charm could generate a unique identifier that cannot really be
guessed (UUID, 256 bytes of random data). And then trust that only a client
that knew that data would be able to present it back to postgres.
(it's essentially just password auth, instead of username auth)"
1751279,2018-03-14 03:10:35 UTC,"(By per-relation configuration, I mean configuration attached to the relation that may be set by the operator. Unlike relation-set, which can be modified by the charm and other code running in the container and for ACL purposes should be considered untrusted)"
1751280,2018-02-23 14:36:10 UTC,"The fix will be in the 1.0.6 release soon, then we'll update that in bionic."
1751280,2018-03-12 22:32:44 UTC,fwupd (1.0.6-2) unstable; urgency=medium
1751280,2018-03-13 09:24:10 UTC,https://bugs.launchpad.net/ubuntu/+source/fwupd/1.0.6-2
1751281,2018-10-19 14:52:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751282,2018-02-24 12:38:18 UTC,Apologies. Not a bug. Pressing Space bar or t key causes selection of appropriate group of packages by marking with *. Pressing Tab key then causes Ok to be highlighted. Pressing Enter key then causes installation of marked (with *) group(s) of packages.
1751294,2018-03-06 23:47:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751294,2018-03-06 23:51:39 UTC,"I see the same behaviour, but I'm not sure if the cause is the same, on 4.4.0-112-generic and 4.4.0-116-generic. In my case, the VM remains responsive for a variable amount of time. Sometimes it works long enough to login via SSH, at other times it does not get to the login screen. In almost all circumstances I cannot see what is wrong with the system (nothing gets printed to screen), and I see the VM use up all available CPUs. Likewise, the only way to get out of that is to do a hard reset."
1751294,2018-03-17 15:00:11 UTC,"I'm not sure if this is the cause or a red herring, but I found this on one of the machines which got stuck on boot. Other instances usually don't print anything."
1751294,2018-04-14 02:37:09 UTC,This seems to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349
1751305,2019-09-26 11:51:02 UTC,eh... i'm uncomfortable about closing this.
1751305,2019-09-25 23:13:05 UTC,"The `snap interfaces` command has now been deprecated and the `snap connections` is now the command to use to inspect interface connections. I cannot reproduce the issue in this bug with the `snap connections` command, so I'm closing this."
1751307,2019-09-25 23:02:49 UTC,"The `snap interfaces` command is deprecated, and instead the `snap connections` command should be used. The `snap connections` command does auto-complete in this case. See:"
1751311,2018-09-15 00:59:02 UTC,If DXF has attributes for text then we should use them.  Otherwise we should update the tooltip to indicate that ASCII text will only be used for plain text.
1751311,2018-09-17 22:10:56 UTC,"@Eldar, is your text multi-line?  We always plot multi-line text as graphics, but we should correctly plot a single line of italic text as ASCII."
1751311,2019-06-07 04:17:21 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1751330,2018-02-24 07:32:42 UTC,I totally agree that current approach is far from ideal.
1751330,2018-02-26 14:41:29 UTC,"Thank you for your feedback Boris. This is great news to hear. I would definitely love to talk more in detail about the future of Rally and how I could help contribute more. Is there a blueprint in Launchpad for the new ""rally template"" feature? I will be unavailable for the next week. After this week I will see if I can find you on the Rally IRC channel."
1751330,2018-02-26 19:32:30 UTC,"So we don't use actually blueprints;) and core team is quite small at the moment so we are trying to avoid bureaucracy, if you would like we can have short call and I can explain what we are working on and where help will be very appreciate, so you can pick whatever you are interested in ;)"
1751341,2018-05-07 18:07:13 UTC, cfg80211: failed to load regulatory.db
1751353,2020-08-18 17:49:43 UTC,This breaks Stat Cats on the patron edit form when I try to apply it. Screenshot attached showing the header but no stat cats appearing (in this test there should be two appearing).
1751353,2020-09-24 19:53:49 UTC,This problem persists as Terran describes above.
1751353,2020-08-10 16:06:02 UTC,I've updated Zavier's commit here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/khuckins/lp1751353-type-to-select-in-patron-stat-cats
1751353,2020-05-27 09:01:52 UTC,"Here is the updated branch:
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/zbanks/lp1751353-type-to-select-needed-in-patron-stat-cat-dropdowns"
1751353,2018-02-23 19:54:54 UTC,Bug 1751356 for the item editor version of this
1751353,2019-11-12 22:02:40 UTC,"With long lists of municipalities in our commonwealth and many complaints about staff time spent scrolling a list, do you think there will be any updates on this."
1751353,2020-07-16 18:29:08 UTC,"Removed pullrequest as this looks like it'll be needing a bit more work. Zavier's moving on to new projects, so I intend to pick this up in the near future"
1751353,2018-02-23 19:56:03 UTC,Confirmed on 3.0.3 webclient
1751356,2018-02-27 15:49:48 UTC,"I tested on 3.0.3. When testing, I cannot recreate this behavior for patron stat cats, even with the caveat of unset value and/or reset back to no value. What I'm observing is the inability to type-to-select without any additional selection being made. I tested both registering a patron and an existing patron account. Within the item editor, however, I am seeing the behavior you mention on item stat cats. What I see is that, instead of the filtering options populating, the select option jumps down to the beginning of the letter typed. For example, if I type ""k"" in the item stat cat dropdown, it will jump down to the start of k's in my list, such as kit. I see similar behavior in other interfaces not related to stat cats, such as typing ""k"" to select through all of the different libraries starting with k when selecting a pickup library location. My best description of the behavior is like that of a ""Find on this Page"" feature and less like a filter."
1751356,2019-11-13 21:41:16 UTC,"For anyone who wants to work on this, it sounds like the Stat Cat dropdown needs to be replaced with an eg-basic-combo-box. See bug #1793196 for one example of how this can be done."
1751356,2020-05-19 16:42:18 UTC,The item stat cat dropdown is now using an eg-basic-combo-box. Here is the branch:
1751356,2020-06-12 19:49:00 UTC,sign off pushed to user/rogan/lp1751356_signoff
1751356,2020-08-05 21:36:27 UTC,"This needs a bit more work, as it breaks the statcat dropdown when using the volcopy editor to edit an item template rather than an item."
1751356,2020-12-15 18:04:50 UTC,"Thanks for the feedback Galen. The dropdowns are now working properly on the item template.  Also, during testing I came across a scenario where the end user switches from a saved value for a stat cat to no saved value.  To indicate no selection I added the entry ""<NONE>"".  This is consistent with with the text on other fields that are unset."
1751356,2021-02-09 17:01:29 UTC,Any chance this fix can be applied to the Patron Stat Cats as well?
1751356,2021-02-09 19:51:54 UTC,"I have tested this code and consent to signing off on it with my name, Christine Burns and my email address, <email address hidden>."""
1751358,2018-02-24 01:40:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751358,2018-02-24 20:33:07 UTC,"I struggled with this issue as well. I think I have solved it by running ""/etc/kernel/postinst.d/dkms 4.13.0-36-generic --force /boot/vmlinuz-4.13.0-36-generic"" (so adding a ""--force"" flag)."
1751358,2018-02-28 19:16:43 UTC,Adding --force flag didn't help... It still hangs
1751359,2018-02-23 21:52:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547671"
1751359,2018-02-27 12:26:01 UTC,Root cause is that starting in Pike this command:
1751375,2020-11-12 18:47:27 UTC,Still a problem in 3-6-0
1751375,2018-11-16 20:46:13 UTC,"Confirmed that adding a new item tag on the fly while editing multiple items results in the creation of multiple, duplicate item tags.  I am unable to confirm that this also happens when creating items.  Currently, I cannot create multiple items on our test system."
1751376,2018-03-28 19:36:15 UTC,"With the newer version of Inkscape 0.92.3, I can also reproduce the same bug following steps 1) to 8)."
1751376,2018-03-28 19:37:30 UTC,Please see attached video (inkscape-3.ogv) in the previous comment. In that video I monitor all steps
1751376,2018-03-28 19:42:06 UTC,"When clicking ""OK"" several times, in the end the whole system crashes and you are looged out loosing all the information."
1751379,2019-04-09 20:50:24 UTC,"I've ended up with a combination of a leftupdown script which is modified to not unconfigure the interface, plus a cron job which checks the output of birdc show protocols all and runs ipsec auto --down [tunnelname] then waits ten seconds and runs ipsec auto --up [tunnelname] if bird reports a failure, which finally seems to be an adequate workaround for achieving a reasonable approximation the desired stability."
1751379,2018-04-27 22:29:29 UTC,Upgrading from Ubuntu 17.10 to 18.04 appears to have fixed the problem with the vti interfaces disappearing from the output of ip addr during a network glitch.
1751379,2019-11-15 23:09:21 UTC,"Because Debian 10 seems to have a more robust security update policy for the libreswan package than Ubuntu does, I've moved this functionality from Ubuntu to Debian 10, and I believe I got a newer version of libreswan in the process."
1751384,2019-05-13 18:04:35 UTC,"Still not sure what the cause is however, the mojo run of trusty-mitaka has been failing for a while."
1751384,2019-05-13 20:41:24 UTC,Note: this error does not happen in the queens or rocky specs. It's possible that it is a bug that has been fixed since mitaka.
1751384,2021-01-08 12:01:29 UTC,"Yep, existing bug in mitaka https://bugs.launchpad.net/charm-ceilometer/+bug/1773171"
1751396,2018-10-08 21:20:01 UTC,"Reviewed:  https://review.openstack.org/607345
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d1a0d630d22180cbe602d56cfb308732add453de
Submitter: Zuul
Branch:    stable/rocky"
1751396,2018-10-02 19:05:28 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/607345"
1751396,2018-10-03 12:11:26 UTC,This does not affect Ubuntu Pike because neutron 11.0.5 does not include the original patches that are being reverted.
1751396,2018-10-04 11:43:21 UTC,This bug was fixed in the package neutron - 2:13.0.1-0ubuntu1
1751396,2018-10-05 13:14:32 UTC,"Hello Swaminathan, or anyone else affected,"
1751396,2018-10-05 18:01:36 UTC,"Hello Swaminathan, or anyone else affected,"
1751396,2018-10-08 14:07:00 UTC,"This bug was fixed in the package neutron - 2:13.0.1-0ubuntu1~cloud0
---------------"
1751396,2018-10-10 14:02:04 UTC,Regression testing successful for bionic-proposed (tempest results):
1751396,2018-10-02 18:01:10 UTC,Marking Artful as invalid since it is EOL.
1751396,2018-10-17 17:14:20 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/611396"
1751396,2018-10-17 19:37:37 UTC,"I don't think the regression testing is sufficient for this SRU verification, please follow the test case in the description to verify that this is fixed."
1751396,2018-10-19 05:31:15 UTC,"Reviewed:  https://review.openstack.org/611396
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=eb7bb07184bfcc2f64cbf53f9d69891cd7261eea
Submitter: Zuul
Branch:    stable/pike"
1751396,2018-11-06 06:11:26 UTC,This issue was fixed in the openstack/neutron 11.0.6 release.
1751396,2018-11-06 16:51:07 UTC,This SRU is no longer needed as we're uploading neutron 12.0.5 to bionic (queens) which includes this fix.
1751396,2018-11-13 18:48:29 UTC,Thank you for taking the time to verify this stable release fix.  We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE).  Please remove the verification-done tag and add one for the release you have tested the package in.  Thank you!
1751396,2018-11-19 15:48:20 UTC,"This bug has been fixed in the neutron 12.0.5 stable point release via https://bugs.launchpad.net/cloud-archive/+bug/1795424. neutron 12.0.5 was tested with a tempest smoke test run against a juju-deployed openstack as described in https://wiki.ubuntu.com/OpenStackUpdates.
Please see test results at: https://bugs.launchpad.net/cloud-archive/+bug/1795424/comments/17"
1751396,2018-10-10 15:41:06 UTC,Regression testing successful for queens-proposed (tempest results):
1751396,2018-09-21 13:20:15 UTC,s/New/Triaged
1751396,2018-02-24 02:08:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547696"
1751396,2018-09-19 20:40:29 UTC,"Reviewed:  https://review.openstack.org/596402
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2d47cb7d9a8ab021ccbc08713b32ccddf6e1baa7
Submitter: Zuul
Branch:    stable/queens"
1751396,2018-03-20 17:48:39 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554644"
1751396,2018-04-02 18:17:47 UTC,"Reviewed:  https://review.openstack.org/554644
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=02d31ffb8abb157dff02fc977241ebdbf8ead89c
Submitter: Zuul
Branch:    stable/queens"
1751396,2018-04-03 17:58:23 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/558585"
1751396,2018-04-19 11:40:02 UTC,This bug was fixed in the package neutron - 2:12.0.1-0ubuntu1
1751396,2018-04-19 14:13:17 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b1 development milestone.
1751396,2018-04-20 15:57:21 UTC,"Hello Swaminathan, or anyone else affected,"
1751396,2018-05-08 04:36:33 UTC,This issue was fixed in the openstack/neutron 12.0.2 release.
1751396,2018-09-21 13:19:43 UTC,Moving status back to New for Ubuntu due to reverted patch.
1751396,2018-06-22 17:58:46 UTC,12.0.2 is available in the Queens cloud archive.
1751396,2018-06-29 02:20:45 UTC,"Reviewed:  https://review.openstack.org/558585
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6956821764e81c61f4c3620a2a6753394b5bc69a
Submitter: Zuul
Branch:    stable/pike"
1751396,2018-07-18 12:04:02 UTC,"Reviewed:  https://review.openstack.org/578112
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f65e7ba05d0502bdc7163a6221ed8138ac183055
Submitter: Zuul
Branch:    stable/ocata"
1751396,2018-07-25 23:07:44 UTC,"Hi, this appears to have broken DVR functionality for a simple shared tenant network. The DVR flows translating the DVR macs are missing on the physical bridges now for a VLAN based network. This tenant network is shared, and only attached to 1 router."
1751396,2018-07-25 23:29:18 UTC,Logged https://bugs.launchpad.net/neutron/+bug/1783654 to address the missing DVR flows on a shared VLAN tenant network
1751396,2018-08-23 06:10:51 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/595496"
1751396,2018-08-23 21:37:32 UTC,"Reviewed:  https://review.openstack.org/595496
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=267eea50fd9e9c74faa96d529a7ec2fd8aa8d51f
Submitter: Zuul
Branch:    master"
1751396,2018-08-24 16:58:38 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/596402"
1751396,2018-06-26 14:07:20 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/578112"
1751396,2018-03-20 00:05:18 UTC,"Reviewed:  https://review.openstack.org/547696
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d019790fe436b72cb05b8d0ff1f3a62ebd9e9bee
Submitter: Zuul
Branch:    master"
1751407,2019-09-30 20:37:56 UTC," Setting up libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1) ...
 update-alternatives: error: cannot stat file '/usr/bin/java/jdk-9.0.4/bin/jar': Not a directory
 dpkg: error processing package libegl1-mesa:amd64 (--configure):
  subprocess installed post-installation script returned error exit status 2"
1751409,2018-02-24 03:19:53 UTC,# magnum cluster-template-create  --name k8s-1 --image fedora-atomic-latest --keypair mykey --external-network provider --dns-nameserver 10.40.0.5 --master-flavor m1.large --flavor m1.large --coe kubernetes --network-driver flannel
1751409,2018-03-25 17:43:11 UTC,"With which magnum release you have this issue?
Which fedora atomic image are you using?"
1751409,2018-03-26 18:08:31 UTC,I was using pike when I have this issue.
1751418,2018-02-24 09:02:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/547728"
1751418,2020-02-03 14:05:20 UTC,The KeyError problem seems to be fixed by this patch: https://review.opendev.org/#/c/639319/
1751418,2020-02-10 10:57:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/706793"
1751418,2020-02-10 11:03:25 UTC,"I've uploaded the fixed IP fix as a separate patch, please let me know if I need to change anything in the commit message (as I've only taken your changes and slightly modified them to take the [1] patch into account). Is co-authored-by enough, or should I change/add anything else?"
1751418,2020-02-19 04:15:25 UTC,"Reviewed:  https://review.opendev.org/706793
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=9e3cc27e8c9458abf77cea4f0017f7de258d020f
Submitter: Zuul
Branch:    master"
1751421,2018-10-04 16:01:40 UTC,"Marking Triaged/Low per request at #ubuntu-bugs. I can also state I have had it, at least twice, on 18.04."
1751421,2018-10-04 21:23:24 UTC,"Thanks for making the changes, C!
:)
G"
1751421,2018-10-04 23:51:45 UTC,A major problem for Ubuntu (and I guess for Linux system in general) is that they have a steep learning curve for user coming from a Windows environment.
1751421,2018-10-05 01:20:27 UTC,"Hi Humphrey,
I appreciate your concerns. Regarding the implementation of menus, there are some versions of linux specifically laid out to mimic windows so it is easier for users from the windows world to adapt to linux."
1751421,2018-10-11 14:55:47 UTC,"It'd be helpful to know how the mice which people experience this with are connected to the system. Are they bluetooth, wireless, something else?"
1751421,2018-10-10 07:17:35 UTC,Happened to me again.
1751421,2018-10-11 20:44:30 UTC,USB connected
1751421,2018-10-11 20:45:56 UTC,Mine is on USB.
1751421,2018-10-06 01:12:18 UTC,I believe that the criteria as set out in https://wiki.ubuntu.com/Bugs/Importance allow me to argue as follows.
1751421,2018-10-04 14:40:54 UTC,"Hi Martha and Humphrey,
For the ease of the programmers, I will add some extra information here to complete the bug. Please feel free to add any corrections.
-----------------------"
1751421,2018-09-26 23:46:11 UTC,"I noticed the update icon in the launchbar.
I clicked the icon.
I wanted to click ""install now"", but the mouse button didn't work.
So I rebooted and then it did work."
1751421,2018-09-26 11:53:30 UTC,"Hello Martha,
Thank you for taking the time to report that you also have this problem. Could you shed any light on the exact steps to reproduce this bug?
Can you give an indication as to the program/application causing the problem?
Thanks
G"
1751421,2018-10-04 14:32:14 UTC,"Thanks for the update, Martha. That helps clarify. I will set up the summary now.
Take care
:)
G"
1751421,2018-05-16 09:00:17 UTC,My mother is not computer literate and is completely helpless when the mouse buttons don't work.
1751421,2018-08-31 01:32:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751421,2018-09-01 01:49:41 UTC,happens on 18.04 as well
1751421,2018-05-02 09:25:57 UTC,just happened again
1751421,2018-09-20 03:59:04 UTC,"I just restarted after Software Updater told me and now the buttons do NOT work.
But then I had a brainwave and started Terminal and exited straight away.
And, lo and behold, the buttons are working again!"
1751421,2018-09-21 15:58:19 UTC,"Hi Humphrey,
Here I am again, bugging you about a bug report, at your request. :)"
1751421,2018-09-24 01:24:36 UTC,"Sorry, but what you ask me goes beyond my expertise."
1751421,2018-09-19 23:42:36 UTC,"I started the computer after having been away for a week and started BOINC to resume processing, but I could not use the mouse to select the process.
I then noticed that software updater was loaded so I reckon that software updater was the culprit.
But ...
I decided to first log a bug against BOINC (using ~$ ubuntu-bug -w), because BOINC does not allow selection of a process via the keyboard.
And ...
During the process of entering bug information on Launchpad (using Firefox) I noticed that I could use the mouse again.
So there."
1751421,2018-09-26 11:48:37 UTC,"OK, Humphrey. I will look at next steps.
Have a great day.
:)
G"
1751436,2018-02-26 18:38:34 UTC,"Not reproduced in Inkscape 0.92.2 (c477208a6d, 2018-01-28) on Windows 10."
1751436,2020-03-12 17:36:57 UTC,"I am also unable to reproduce the issue with your steps; however, there are cases where the ""grid display"" and the ""grid checkbox"" become out of sync. These are tracked in https://gitlab.com/inkscape/inkscape/-/issues/664. Feel free to comment there, if you find another way to reproduce."
1751437,2018-02-27 20:42:41 UTC,"Thanks for the privacy advice, I did not know that the svg contained such info. I removed the attachement. In case you need a sample again let me know and I 'll upload another one.
I run the debugger and reproduced the bug. Please find attached the debug log."
1751437,2018-02-27 21:46:32 UTC,"(It's a long-standing issue, with the file paths. At some point, someone wrote a warning here:
https://inkscape.org/en/about/privacy/. There's a bug report for it somewhere, too.)"
1751437,2018-02-26 18:35:23 UTC,"I did more testing and I can consistently reproduce the error in the attached svg file.
Please not that:
-With a file containing just a few elements it does not occur.
-If before sculpting I choose the rectangle and click on ""Object to path"" it does not occur.
Please find attached an archive containing the svg and the log.
To recreate:
-Open the provided svg
-click on the ""create rectangle""
-drag mouse to create rectangle
-click on sculpting tool(with ""push parts of path"" selected, width=5, force=19).
-click and drag sculpting cursor a little bit outside rectangle's bounds and drag to rectangle to sculpt it.
-inkscape will crash with segmentation fault as soon as the sculpting cursor and rectangle bounds collide."
1751437,2018-02-26 00:35:09 UTC,"Cannot confirm this on Linux Mint 18.3. Can you be a bit more specific in your description, and share an example file that has the issue?"
1751437,2018-02-27 19:31:01 UTC,Thank you for providing this very good info.
1751450,2018-03-07 18:14:24 UTC,Did you try using GRUB to get to a previous version of the kernel?
1751472,2018-03-15 11:58:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553367"
1751472,2018-04-04 04:04:58 UTC,"Reviewed:  https://review.openstack.org/553367
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ac20fc22adb133d9de5f2ec15faad11b2de1987a
Submitter: Zuul
Branch:    master"
1751472,2018-04-17 12:23:54 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/561925"
1751472,2018-04-17 16:16:10 UTC,"Reviewed:  https://review.openstack.org/561923
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=525ea3cfac0d91752bdac1bbca4191976d3c592a
Submitter: Zuul
Branch:    stable/queens"
1751472,2018-04-19 18:11:42 UTC,"Reviewed:  https://review.openstack.org/561925
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=15aed7e0e0b4564d78db466e565e612eda6c502a
Submitter: Zuul
Branch:    stable/pike"
1751472,2018-04-20 13:13:42 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1751472,2018-04-25 09:21:08 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1751472,2018-04-25 09:23:52 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1751472,2018-05-16 13:21:47 UTC,This issue started to appear again -- http://logs.openstack.org/39/554439/20/check/ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa/e3c2ae3/logs/screen-n-cpu.txt.gz#_May_15_14_51_20_013490
1751472,2018-04-17 12:21:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561923"
1751474,2018-02-28 16:54:33 UTC,"On 2/25/18 7:18 PM, Christian Boltz wrote:

>> there are no DENIED in audit log.
>
> DBUS events are somewhat special - you'll find them in the syslog, but not in audit.log.
> (Background: AFAIK the DBUS checks happen in userspace, which also means denials can't be logged to the audit subsystem.)
>
"
1751474,2018-02-25 15:51:39 UTC,kde-open5 DBus error fixed with this (copied form Ubuntu Firefox profile):
1751474,2018-02-25 17:18:44 UTC,"> there are no DENIED in audit log.
"
1751474,2018-02-25 15:44:28 UTC,"Similar issue on KDE, while working with `kde-open5`:"
1751477,2018-05-15 14:50:53 UTC,This change was made by a bot.
1751486,2018-06-12 09:47:36 UTC,"Can you confirm that the problem only happens when parallelizing Pythia8 shower?
In other terms, if you run"
1751489,2019-01-09 14:15:40 UTC,"That bug report also has a comment saying that with --block-size=65536 it worked, but that was for an error code of -5, not -3."
1751489,2018-06-27 13:27:26 UTC,Can be avoided not using -z
1751489,2019-07-10 13:56:10 UTC,"The other hint in the debian bug is that with rsync 3.1.1 (upgraded from 3.1.0) it works. In this bug, 3.1.1 was at the receiving side, and 3.1.0 is the sender."
1751494,2018-02-28 17:19:13 UTC,The exact commit that causes this problem is this:
1751494,2020-07-22 04:44:23 UTC,"This has been fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=1019242af11400252"
1751508,2018-09-13 11:17:39 UTC,Very similar error occurs in Xubuntu 18.04:
1751508,2018-02-24 21:40:14 UTC,"StacktraceTop:
 OsAbort () at ../../../../os/utils.c:1361
 AbortServer () at ../../../../os/log.c:877
 FatalError (f=f@entry=0x55a1df546857 ""Couldn't add screen\n"") at ../../../../os/log.c:1015
 InitOutput (screen_info=screen_info@entry=0x55a1df7d50a0 <screenInfo>, argc=argc@entry=11, argv=argv@entry=0x7ffdecc2ee08) at ../../../../../hw/xwayland/xwayland.c:926
 dix_main (argc=11, argv=0x7ffdecc2ee08, envp=<optimized out>) at ../../../../dix/main.c:197"
1751508,2018-04-12 00:26:28 UTC,I am also seeing this on a similar system - Lenovo Thinkpad X260 - and for me this occurs when I boot with the laptop docked with two external monitors connected. If I boot without it docked then it boots fine - but when docked Xwayland seems to always crash on startup.
1751508,2018-02-27 13:25:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751508,2018-05-07 07:56:57 UTC,"See also:
https://errors.ubuntu.com/problem/d239c29b34bc845bb8b3ede5c7e671a0ae269955"
1751517,2018-11-19 10:03:36 UTC,"Seems that btrfs ignores compression attribute if compression was set using mount option.
So, the solution is to set compression attributes per-directory:"
1751517,2018-11-19 10:08:28 UTC,Results (using btrfs-compsize tool):
1751517,2018-11-15 14:17:24 UTC,The simplest workaround for the moment:
1751517,2018-02-27 13:31:28 UTC,There may be non root partitions that users want to compress with zstd so you shouldn't
1751517,2018-03-25 12:11:29 UTC,"> Another option:
> Archlinux uses this patched grub version:
>
> https://github.com/Antynea/grub-btrfs
"
1751517,2018-03-25 12:05:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751517,2018-03-04 08:36:26 UTC,"possible workaround:
Patch all btrfs-tools so that they don't compress files accessed by grub with zstd."
1751517,2018-02-26 16:32:06 UTC,"I wonder if I should be disabling zstd support in btrfs-progs, if we cannot boot them."
1751517,2018-10-03 13:00:47 UTC,This would be an enhancement request.
1751524,2018-03-02 12:54:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751545,2018-02-27 02:52:54 UTC,"It seems you can login with empty password in the login screen. Not sure why this didn't work for me when I was testing it last time. But the rest of the issue still stands. It is confusing that you have to type a password if the account should not have a password. Ideally, user should just be able to click on their username in the list of usernames on the login screen."
1751546,2019-04-20 16:41:27 UTC,"Hello, apologies for the delay on any update here."
1751546,2018-03-14 08:23:30 UTC,"Here is a patch to fix vanilla-gnome task. Had to jump through a few hoops to generate it, since lubuntu does not have a bionic seed apparently, so the debian/rules update target is broken."
1751546,2018-03-13 08:15:14 UTC,"To be clear, there are *many* ""generic-desktop-environment"" packages in the archive, and tasksel doesn't have support for any of the others.  I don't see why vanilla-gnome should be a special snowflake here."
1751546,2018-03-13 08:14:17 UTC,"We could make tasksel use the package instead of tasks for this one specific task (which would be more reasonable, IMO, than cluttering the archive with a task that doesn't relate to any official flavours), but that also leads to the question of should tasksel be offering a task that isn't related to any flavours?  Maybe we should have removed it from tasksel, not renamed it."
1751546,2018-03-08 08:28:28 UTC,"Brian, I may be way off track here since its been a long time since I looked at tasksel, however doesnt it essentially run:"
1751546,2018-03-06 21:23:51 UTC,It looks like some changes were made to tasksel previously which need to modified again.
1751546,2018-03-02 09:37:24 UTC,There is no vanilla-gnome-desktop task in the archives.
1751546,2018-02-28 19:23:01 UTC,I was able to recreate this in Bionic today.
1751546,2018-02-25 08:19:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1751546,2018-03-07 04:16:10 UTC,"Strangely there is a vanilla-gnome-desktop package found into synaptic, but its changelog shows:"
1751552,2019-09-16 17:57:02 UTC,Migrated to https://github.com/widelands/widelands/issues/1702
1751562,2018-02-25 11:54:55 UTC,https://stackoverflow.com/questions/28948415/get-thread-id-in-sbcl/48972801#48972801 has some insight on how to make it work for Windows as well - it will retrieve the thread handle then.
1751562,2018-04-29 09:53:29 UTC,"you could find the thread by name
see https://bugs.launchpad.net/sbcl/+bug/1399727/comments/5"
1751562,2018-05-01 21:48:22 UTC,this works:
1751568,2018-03-05 22:13:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751568,2020-10-22 19:58:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu."
1751570,2018-02-25 12:11:19 UTC,https://review.openstack.org/#/c/488874/
1751571,2018-03-12 12:19:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551984"
1751571,2018-03-14 13:29:40 UTC,"I don't think we should do it in sushy-tools, but rather in the ironic devstack plugin itself."
1751571,2018-06-01 07:11:38 UTC,"Change abandoned by Aija Jaunteva (<email address hidden>) on branch: master
Review: https://review.openstack.org/551984
Reason: Abandoning this,
new proposed solution is in new code review - https://review.openstack.org/#/c/571645/
As the new proposed solution is in different project (sushy, not sushy-tools), new code review was created."
1751577,2018-02-25 15:20:48 UTC,"Are you getting the above error on installing Nutty from a Snap.Although I develop Nutty for Elementary OS, it should install and work fine on Ubuntu as well."
1751584,2018-12-13 09:15:37 UTC,"I am having the same problem. Mine is the latest version of UBUNTU with Kernal 4.15.0-42-generic
."
1751584,2019-10-03 08:57:56 UTC,"As 4.13 is not supported anymore, I will mark this as duplicated to bug 1808418, to keep it tracked there. Thanks."
1751584,2018-12-13 20:57:27 UTC,I went ahead and filed this new bug that's more specific to my hardware: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418
1751584,2018-12-13 20:30:14 UTC,"...on second thought, I'm not sure updating it would be the best idea since the end problem appears to be specific to my hardware. I think it's probably better to mark this bug as invalid and create a new one."
1751584,2018-12-13 20:28:07 UTC,"After upgrading my BIOS the problem came back again with the 4.15 kernels. I was able to solve the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:"
1751584,2018-07-12 17:20:06 UTC,"I hesitatingly upgraded to 18.04, and the 4.15 kernel that it comes with booted just fine, so it seems like this issue is limited to the 4.13 kernels that come with 17.10/16.04 HWE."
1751584,2018-04-20 11:08:40 UTC,It looks like I was also suffering from this bug:
1751584,2018-04-15 05:00:16 UTC,I have three systems of which two show this problem.
1751584,2018-04-04 15:47:30 UTC,"For me the 4.13.0-36 kernel works just fine.
However, 4.13.0-37 and 4.13.0-38 won't boot."
1751584,2018-03-31 20:02:19 UTC,"After having intermittent problems booting 4.13.0-32, 4.13.0-36, and 4.13.0-37 I uninstalled those kernels (which also uninstalled linux-generic-hwe-16.04 and linux-image-generic-hwe-16.04) as well as intel-microcode. I'm running the 4.4 kernel that comes with 16.04 now with zero problems. It's not ideal but since 17.10 won't be supported much longer anyway, I'll just wait for the 18.04 kernel."
1751584,2018-03-24 12:08:24 UTC,"The weirdest thing just happened yesterday. 4.13.0-37 wouldn't boot, so I tried 4.13.0-32. The boot process got stuck at this line:"
1751584,2018-03-05 13:01:03 UTC,I'm using Ubuntu 16.04 with Intel graphics.
1751584,2018-03-05 11:35:12 UTC,This seems to be a caused by NVIDIA driver on Ubuntu 17.10 (see attachment). Can anyone confirm this?
1751584,2018-02-25 21:19:13 UTC,"I have the same problem on 17.10. My computer hangs at a slightly different point, see attached screenshot."
1751584,2018-02-25 21:09:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751584,2018-04-15 05:07:32 UTC,Forgot to mention that these systems are all Intel IGP.   No add-on graphics chips.
1751593,2018-02-08 10:34:18 UTC,"Created attachment 368140
Test Qt application which demonstrates the problem"
1751593,2018-02-08 10:47:56 UTC,"That really doesn't look like the same issue at all, the entire window is opaque and black, as if it wasn't using transparency at all."
1751593,2018-02-08 10:56:55 UTC,Does it look like something I should open a new bug for?
1751593,2018-02-08 11:27:07 UTC,"Created attachment 368144
ARGB window using cairo"
1751593,2018-02-08 11:35:21 UTC,"(FWIW, trying to get xprop of the transparent Qt mapped window (the one shat shows up black), all I get is “WM_NAME(STRING) = ""mutter guard window""”)"
1751593,2018-02-14 15:08:20 UTC,The “black border” effects comes from the frame window resize.
1751593,2018-02-15 08:03:46 UTC,"So yes, bug 757104 is a good idea, setting a different bg color on the gdk window frame changes the color seen during resize, so the black seen comes from the gdk_window background color, before it's eventually repainted by the compositor."
1751593,2018-02-22 13:04:36 UTC,"Comment on attachment 368571
[PATCH 2/2] window: Fix sync issue causing back borders"
1751593,2018-02-15 12:10:07 UTC,"So I reckon the problem is because in Wayland, we update the surface when a new buffer is received."
1751593,2018-02-19 16:38:48 UTC,"Created attachment 368569
[PATCH 1/2] window: Add set_frozen method"
1751593,2018-02-19 16:39:41 UTC,"Created attachment 368571
[PATCH 2/2] window: Fix sync issue causing back borders"
1751593,2018-03-20 19:55:19 UTC,let's track this on gitlab only.
1751593,2018-07-17 02:22:45 UTC,"Tracking upstream in:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/53
formerly https://bugzilla.gnome.org/show_bug.cgi?id=767212"
1751593,2020-03-02 11:21:17 UTC,This bug was fixed in the package mutter - 3.35.91-1ubuntu1
1751593,2018-02-15 10:01:29 UTC,"Created attachment 368368
Debug patch to exhibit the issue"
1751593,2018-02-08 08:30:29 UTC,"(In reply to Michael Thayer from comment #17)

> It probably wasn't helpful of me to mention XShape here at all.  It is only
"
1751593,2018-02-15 12:10:48 UTC,"I mean, I think this is purely a mutter compositor issue."
1751593,2018-02-08 08:19:32 UTC,"(In reply to Michael Thayer from comment #15)

> Pointed to this bug by Jonas Ådahl on the GNOME Shell mailing list.
>
> We seem to see something similar when starting VirtualBox.  In VirtualBox we
> need for various reasons to know what the usable area of each screen is -
> that translates as the largest rectangle which fits on that screen without
> obscuring any panels or similar.  We find that out by mapping a maximised
> window on each screen at start-up and checking its position and dimensions.
> To prevent disturbance to the user we create the window fully translucent,
> or if the X server does not support that we use XShape and leave only a
> single pixel visible.  On GNOME Shell Wayland edition (what is the right way
> to say that?) this unfortunately flashes a black rectangle up on the screen
> in the area which should be translucent.
"
1751593,2016-06-21 08:09:20 UTC,"(In reply to Olivier Fourdan from comment #1)

>  - It seems to affect some apps more than others (FF, TB whereas I cannot
"
1751593,2016-06-21 14:32:32 UTC,"(In reply to Olivier Fourdan from comment #2)

> Actually it seems to affect gtk2 and Qt based apps and I think this could be
> related to the use of the _NET_WM_SYNC protocol v1 by these toolkits.
"
1751593,2016-09-01 08:50:21 UTC,*** Bug 770367 has been marked as a duplicate of this bug. ***
1751593,2016-09-02 07:40:52 UTC,"So on Xorg, forcing sync eliminates the black box flickering but causes it on Xwayland?
Could this be a Xayland bug as suggested in bug 77036?"
1751593,2016-09-02 08:16:52 UTC,"It's two different things imho. _NET_WM_SYNC is not to avoid black box flickering of the drop shadows on X11 (as these are outside the client toplevel window), it's to synchronize frames redraw and avoid resizing faster than the client can cope."
1751593,2016-12-14 08:17:18 UTC,Quick update - I have been looking into this lately to see if we could use Pekka's proposal of adding an _XWAYLAND_ALLOW_COMMITS property to tell Xwayland when to commit the surface:
1751593,2018-02-08 08:24:18 UTC,"It probably wasn't helpful of me to mention XShape here at all.  It is only used if ARGB is not available, so is probably not relevant here.  I will see if our GUI developer has time to write up a simpler reproduction scenario.  He is a (cross-platform) Qt developer rather than an X11/Wayland specialist, so is it alright if it uses Qt?"
1751593,2016-06-03 17:01:10 UTC,"Created attachment 329082
bug demonstration"
1751593,2016-12-14 09:51:56 UTC,"Created attachment 341943
[PATCH] MetaWindowActor: Remove uneeded test"
1751593,2016-12-14 10:41:00 UTC,Review of attachment 341942:
1751593,2017-04-15 19:32:41 UTC,"Also experience this on Fedora 25 (Gnome 3.22 on Wayland).
i5-2410M with Sandybridge integrated graphics.
Is there any way to help?"
1751593,2017-05-30 01:50:13 UTC,"I'm also experiencing this issue with applications such as Firefox and Qt Creator, but not with i.e Blender and Chromium and most pre-insalled applications. I'm using Fedora 25 with Gnome 3.22.3 on Wayland, running on an Intel i5-2500 with its own integrated graphics."
1751593,2017-08-15 18:15:32 UTC,testing 3.26 beta... this bug is still happening.
1751593,2018-01-21 16:00:43 UTC,"@Olivier Testing your patch with mutter 3.26.2, it does not resolve the problem. It makes the black artifacts outside the windows disappear, however the right and the bottom edge of the window flicker badly inside, black and otherwise, I would say that aspect is worse than before."
1751593,2018-02-08 07:06:13 UTC,Pointed to this bug by Jonas Ådahl on the GNOME Shell mailing list.
1751593,2016-12-14 09:51:02 UTC,"Created attachment 341942
[PATCH] MetaWindowActor: Update shape in pre-paint"
1751593,2016-06-21 07:45:40 UTC,"Yes, I can reproduce as well *sometimes* - The back area is actually the shadows mutter adds to server-side decorations with the X11 backend."
1751595,2018-02-26 11:24:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751597,2018-05-12 10:52:29 UTC,Still present in 8.1-1 on Ubuntu Cosmic https://launchpad.net/ubuntu/+source/openclonk/8.1-1
1751597,2019-06-21 16:54:31 UTC,Resolved with https://bugs.launchpad.net/ubuntu/+source/openclonk/8.1-1build1
1751621,2019-01-30 10:09:32 UTC,"Hey,"
1751621,2018-02-28 03:09:14 UTC,apport information
1751621,2018-02-28 03:09:11 UTC,apport information
1751621,2018-02-28 03:09:08 UTC,apport information
1751621,2018-02-28 03:09:06 UTC,apport information
1751621,2018-02-28 03:09:05 UTC,apport information
1751621,2018-02-28 03:09:03 UTC,apport information
1751621,2018-02-28 03:09:02 UTC,apport information
1751621,2018-02-28 03:09:01 UTC,apport information
1751621,2018-02-28 03:08:59 UTC,apport information
1751621,2018-02-28 03:08:58 UTC,apport information
1751621,2018-02-28 03:08:56 UTC,apport information
1751621,2018-02-28 03:08:55 UTC,apport information
1751621,2018-02-28 03:08:53 UTC,apport information
1751621,2018-02-28 03:08:51 UTC,apport information
1751621,2018-02-25 18:52:05 UTC,apport information
1751621,2018-02-27 20:09:09 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1751621,2018-02-28 03:08:50 UTC,apport information
1751621,2018-02-25 18:51:44 UTC,apport information
1751621,2018-02-25 18:51:45 UTC,apport information
1751621,2018-02-25 18:51:48 UTC,apport information
1751621,2018-02-25 18:51:49 UTC,apport information
1751621,2018-02-25 18:51:50 UTC,apport information
1751621,2018-02-25 18:51:52 UTC,apport information
1751621,2018-02-25 18:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1751621,2018-02-25 18:51:54 UTC,apport information
1751621,2018-02-25 18:51:55 UTC,apport information
1751621,2018-02-25 18:51:55 UTC,apport information
1751621,2018-02-25 18:51:56 UTC,apport information
1751621,2018-02-25 18:51:58 UTC,apport information
1751621,2018-02-25 18:51:59 UTC,apport information
1751621,2018-02-25 18:52:01 UTC,apport information
1751621,2018-02-25 18:51:53 UTC,apport information
1751622,2018-02-28 03:08:16 UTC,apport information
1751622,2018-02-28 03:08:18 UTC,apport information
1751622,2018-02-28 03:08:19 UTC,apport information
1751622,2018-02-28 03:08:20 UTC,apport information
1751622,2018-02-28 03:08:21 UTC,apport information
1751622,2018-02-28 03:08:23 UTC,apport information
1751622,2018-02-28 03:08:28 UTC,apport information
1751622,2018-02-28 03:08:25 UTC,apport information
1751622,2018-02-28 03:08:27 UTC,apport information
1751622,2018-02-28 03:08:29 UTC,apport information
1751622,2018-02-28 03:08:33 UTC,apport information
1751622,2018-02-28 03:08:14 UTC,apport information
1751622,2018-02-28 03:08:36 UTC,apport information
1751622,2018-02-28 03:08:24 UTC,apport information
1751622,2018-02-28 03:08:13 UTC,apport information
1751622,2018-02-25 19:20:31 UTC,apport information
1751622,2018-02-25 19:20:54 UTC,apport information
1751622,2018-02-25 19:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1751622,2018-02-25 19:20:30 UTC,apport information
1751622,2018-02-25 19:20:33 UTC,apport information
1751622,2018-02-25 19:20:35 UTC,apport information
1751622,2018-02-25 19:20:37 UTC,apport information
1751622,2018-02-25 19:20:38 UTC,apport information
1751622,2018-02-25 19:20:40 UTC,apport information
1751622,2018-02-27 20:08:52 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1751622,2018-02-25 19:20:42 UTC,apport information
1751622,2018-02-25 19:20:43 UTC,apport information
1751622,2018-02-25 19:20:44 UTC,apport information
1751622,2018-02-25 19:20:45 UTC,apport information
1751622,2018-02-25 19:20:47 UTC,apport information
1751622,2018-02-25 19:20:50 UTC,apport information
1751622,2018-02-25 19:20:41 UTC,apport information
1751626,2018-03-09 21:35:05 UTC,This works fine and does provide so real functionality.
1751626,2018-03-10 10:05:30 UTC,I know that it works as intended. Where are the tests for automated upgrades and how do they use this functionality?
1751626,2018-03-19 04:07:20 UTC,"I'm leaning toward agreeing with Simon. The upgrade tests should just mock out the version number (that's why we use mock in the first place), and I'm pretty sure they do already. At minimum I'd suggest using the flags in the registry instead of depending on sys.argv, and collecting the bzr version code to a single place that is used in both setup.py and OpenLP as a whole."
1751626,2018-03-19 14:47:12 UTC,"If you are ok with it, I would create a merge request that removes it."
1751628,2018-03-09 21:29:24 UTC,The running from a USB device may not be implemented the rest of the portable code should work as it available on Openlp.org
1751649,2018-03-06 06:46:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751657,2019-10-21 12:31:10 UTC,"This is fixed on Ubuntu 19.10, where journalctl -g works fine."
1751657,2018-08-29 08:01:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751667,2018-02-26 20:25:25 UTC,"Hi Jamie, If I read this right, that implies a newer version of snapd? Is this something that is making its way into the daily? Am I understanding this correctly?"
1751667,2018-02-26 18:37:38 UTC,The snap-confine profile is not loaded at the time ubuntu-budgie-welcome is launched. You should see a different error if you do:
1751667,2018-03-02 19:38:30 UTC,This is now merged in 2.32. Please see https://forum.snapcraft.io/t/confined-snaps-dont-work-on-live-images-due-to-apparmor-path-mapping/3767/9 if you want to check it out for yourself.
1751667,2018-03-02 02:34:24 UTC,"On 2 March 2018 at 11:37, Jamie Strandboge <email address hidden> wrote:"
1751667,2018-03-01 22:37:52 UTC,"*sigh* my test case in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1751667/comments/8 was flawed. With the PR, on a livecd the apparmor unit correctly doesn't load the policy. snapd starts at some point, notices it is on an overlay, adds the overlay snippet to /var/lib/snapd/apparmor/snap-confine and then loads all the /etc/apparmor.d/*snap-confine* profiles. So long as snapd starts before preinstalled snaps then all is fine."
1751667,2019-10-29 22:00:45 UTC,Based on the discussion in this bug report I'm marking this as fix released.
1751667,2018-03-01 21:37:33 UTC,I tested to see if the changes in https://github.com/snapcore/snapd/pull/4714 would address this bug. I did this by:
1751667,2018-02-27 21:18:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751667,2018-02-26 23:33:10 UTC,"Is this something that will make it in prior to 18.04 (I assume not)? I only ask as we may have to do a workaround where the DEB runs off of the ISO, but the seed for install is the snap package."
1751667,2018-02-26 21:20:02 UTC,"PR 4714 is not committed yet (it is approved). Once committed to trunk, I'll propose it for 2.32."
1751667,2018-03-01 22:11:45 UTC,The problem is that the apparmor systemd unit (and the script it calls) exit if /rofs/etc/apparmor.d exists. This is correct in the general case. What needs to happen is either snapd loads them itself or the apparmor init scripts instead load just the snap-confine profiles.
1751667,2018-02-27 14:40:46 UTC,"It is planned for 18.04. If other bugs remain for running classic or strict snaps on livecd, they'll need to get fixed."
1751668,2018-02-26 15:01:46 UTC,"For python2.7 only the tar and bash problem exists.
and eentlet must still be updated, in order to avoid 'eventlet.green._socket_nodns' has no attribute 'EAI_NODATA'"
1751670,2018-02-26 00:40:14 UTC,"Tried on Linux Mint 18.3 with latest master (0.92+devel (193c56f, 2018-02-22)), and used the rectangle corner radius field. The crash doesn't happen for me, it just goes back to 0."
1751670,2018-02-26 02:22:44 UTC,More tests:
1751670,2018-02-27 19:33:31 UTC,"Hah, great that you already come up with a possible solution!"
1751674,2018-02-26 00:32:17 UTC,"Yeah, the page fails uploading the code dump file. Actually it seems to upload the whole file but then it shows a ""Timeout error"" error. Anyway, let me know if you need that file and if so how can I send it to you."
1751674,2018-03-15 14:46:58 UTC,"What's happening here is that the memory range you're asking to dump (physaddrs 0 to 0x3fffffff) includes a lot of devices, including the interrupt controller, which is at 0x1e000000. There's a longstanding bug in the GIC code where it will crash if you try to access its per-CPU register bank from some context that isn't a guest CPU (including the monitor or the QEMU gdb stub), because it doesn't know which CPU's version of the registers you wanted. That's what you've run into here."
1751674,2018-03-15 14:59:20 UTC,LP:1602247 is the bug for the similar issue when using the gdb stub.
1751677,2020-07-11 16:42:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751677,2020-07-11 09:23:45 UTC,It's solved! :D
1751677,2020-07-11 08:45:00 UTC,I see this thread is getting its age but I come across the same
1751677,2018-02-26 11:13:59 UTC,Unfortunately the interesting parts are cut off. Can you please provide the full lines?
1751677,2020-07-11 16:42:01 UTC,"Please note that the apparmor unit will not stop loading profiles if some fail to load (ie, it should load all the profiles it is able to; if that isn't the case, that would be a bug in the unit), but if there are any errors loading any of the profiles, the unit will be marked in the failed state."
1751701,2018-05-03 05:47:19 UTC,Can you post your terminal output from running docky in the terminal with the -d (or --debug) flag when the error is triggered.
1751715,2019-09-16 08:46:17 UTC,Migrated to https://github.com/widelands/widelands/issues/3260
1751716,2018-02-27 07:27:46 UTC,New finding: the distortion seems to appear after reboot (without power off).  IMO some variables in sound card (probably gain) are not reset to initial values during reboot and/or switch between audio sources (maybe even during switch between browser tabs) and this over-steers final amplifiers.
1751716,2018-02-27 08:10:54 UTC,Thanks. I have seen other audio bugs with the same problem -- the state of the hardware changes on warm boot. But hopefully there is a software solution...
1751716,2018-02-27 12:26:09 UTC,"Hi,"
1751737,2018-02-26 10:00:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1751739,2018-05-09 09:04:03 UTC,https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1756040
1751739,2019-12-03 09:29:09 UTC,"I tested this scenario today with 2.7.0, and was able to deploy a container to a machine using FAN networking:"
1751740,2018-03-13 15:56:42 UTC,"is it possible to also include /etc/network/interfaces
Are you intending to add external addresses to containers that are running (and not giving addresses to the host machine)? Or is nothing going to be publicly exposed?"
1751743,2018-04-13 12:25:11 UTC,*note that the dhcp server is also a juju-provisioned VM with the same network setup as the host.
1751743,2020-06-26 13:49:30 UTC,"This is on our list of priorities for Juju 2.9, pending the setup of our VMWare cluster so that we can do internal testing of the fix."
1751743,2020-10-21 20:50:14 UTC,De-escalating as feature work to support container networking in vsphere did not make the roadmap. Added vsphere-provider tag.
1751743,2018-03-14 10:24:52 UTC,I presume that you did have DHCP running on the network that ens192 was connected to (presumably that was how ens192 got the 10.10.137.58 that we ended up assigning to br-ens192).
1751743,2018-04-13 12:18:00 UTC,"Yes, DHCP is running on the network ens192 was connected to."
1751745,2018-02-26 10:09:58 UTC,"StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 run_pipeline (ncommands=<optimized out>, commands=0x7ffc45de2bc0, no_pipe=<optimized out>) at ./debian/build/../../src/roff/groff/pipeline.c:529
 run_commands (no_pipe=0) at ./debian/build/../../src/roff/groff/groff.cpp:579
 main (argc=<optimized out>, argv=<optimized out>) at ./debian/build/../../src/roff/groff/groff.cpp:494"
1751745,2018-03-13 22:26:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751745,2018-04-04 00:42:56 UTC,"When it happened to me I was trying to load a manpage on a root shell.
sudo -s"
1751747,2019-06-13 19:15:02 UTC,https://github.com/KiCad/kicad-source-mirror/commit/df08f9921f2def9a4867e8c3e510f495acd3c1d1
1751750,2018-02-26 16:46:10 UTC,https://gitlab.gnome.org/GNOME/gnome-software/issues/313 - filed upstream.
1751750,2018-02-26 16:20:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1751750,2018-02-26 16:49:19 UTC,thanks!
1751754,2018-02-26 10:36:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751759,2018-02-27 01:36:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751763,2018-02-26 11:46:59 UTC,apport information
1751763,2018-02-26 11:47:00 UTC,apport information
1751763,2018-02-26 11:47:01 UTC,apport information
1751763,2018-02-26 11:47:02 UTC,apport information
1751770,2018-02-27 19:14:50 UTC,"Looks good to me so far. The commented out sphinx dependency is a bit annoying, but I guess it is a reminder for the moment when it will be re-added once the license issue is fixed. From my side it's a +1, but I'd need some more experienced to check it as well (as I'm still in training)."
1751770,2018-03-06 17:13:11 UTC,Accepted.
1751782,2018-02-27 01:21:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548109"
1751782,2018-02-26 14:38:02 UTC,I found the reason why. The devtack plugin.sh which was merged about 10 days ago added this:
1751784,2018-07-18 15:14:28 UTC,"As a concrete example, I had a case yesterday where all logging I had was (trimmed output):"
1751784,2019-09-20 15:37:34 UTC,Is this still an issue? We should probably mark it as low-hanging-fruit if someone thinks a new contributor could pick this up.
1751784,2019-09-22 21:14:42 UTC,"Yes, this is still a problem for OpenStack operators, that require more descriptive information on why a host is filtered out by the NUMATopologyFilter. Andrea gave an example on comment #2."
1751784,2020-12-07 15:33:22 UTC,This is no longer a problem
1751784,2018-04-05 02:16:16 UTC,"This is a request for enhancement. I think this has come up before too, so I'll see if I can find related requests and discussions about it."
1751790,2018-02-26 14:30:29 UTC,"AFAICT the following specs are affected by this issue:
baremetal7-next.yaml
baremetal7.yaml
designate-next-ha.yaml
full-next.yaml
full-ssl-next.yaml
full-ssl.yaml
full.yaml
ha-next.yaml
ha.yaml
ksv3-full-next.yaml
ksv3-full.yaml"
1751795,2018-02-26 18:42:30 UTC,we developed those in different steps - and nobody had time to merge it.
1751799,2018-03-22 15:30:48 UTC,The package has been published and the bug is being set to Fix Released
1751799,2018-03-14 18:51:21 UTC,"Microsoft testing is complete, so I am toggling Stakeholder-signoff to ""fix released""."
1751799,2018-03-22 11:22:51 UTC,"4.13.0-1012.15 - azure
Regression test CMPL."
1751799,2018-03-22 14:55:59 UTC,This bug was fixed in the package linux-azure - 4.13.0-1012.15
1751799,2018-03-09 09:59:41 UTC,USN not needed for linux-azure kernel
1751800,2019-08-14 13:18:26 UTC,"Glad to have this brought to my attention, since even one word code changes deserve three sign-offs, sometimes :)  Pushed to master through rel_3_1.  Thanks, James and Remington!"
1751800,2019-05-02 19:23:30 UTC,"James's commit on github appears to lack a Signed-off-by: in the commit message.  We need that as an assurance that he is actually able to share the code with Evergreen proper.  It's a formality, but it helps us track things is there ever is a dispute about the code."
1751800,2019-05-02 19:14:58 UTC,"James, if I was wrong, that's great!  Because I couldn't think of anything else that could be causing the problem.  A quick test shows me that it works.  Are you able to create a branch in the Evergreen working repository? (https://git.evergreen-ils.org/?p=working/Evergreen.git)  If not, I'll grab your commit from GitHub."
1751800,2019-05-02 16:57:06 UTC,"Hi!  I think Remington you were wrong.  I did a test and found that the fields are getting reversed in service.removeField() -- likely due to the pop() which pops the last element, these elements are push()ed onto a fresh array with the reversed order.  I've pushed a patch here on Github."
1751800,2019-01-24 14:38:05 UTC,I thought the reverse-sorting bug occurred in this file:
1751800,2019-01-08 16:29:00 UTC,Thanks John! That's what I get for not searching well enough! :)
1751800,2019-05-31 13:43:26 UTC,"Alright, James added his signoff on GitHub, and I've added mine here:"
1751800,2019-01-08 15:44:04 UTC,"Hi Stuart,"
1751800,2019-01-08 15:05:30 UTC,The other thing I have found out which is perhaps not related.
1751800,2019-01-03 16:47:41 UTC,"This happens for me both in the Display Fields and the Filters tabs. Sorting the filed order is one thing I definitely miss from the XUL client, much easier."
1751800,2018-11-06 17:39:00 UTC,Also +1 to Anna's comment.  It's very time consuming to re-sort.
1751800,2018-09-17 13:52:30 UTC,+1 to Anna's comment. It's very frustrating.
1751800,2018-06-25 12:59:29 UTC,"This is highly annoying, especially since it takes so many more clicks already to set up the order in which columns appear now than it did in the XUL client."
1751800,2018-02-26 15:35:59 UTC,"Yes, this is happening to me as well. It appears to be resorting into the order they were originally in."
1751800,2019-01-08 16:12:33 UTC,"Tiffany, and Stareagle, I believe this behavior was reported here: https://bugs.launchpad.net/evergreen/+bug/1778521"
1751803,2018-03-14 12:04:02 UTC,The package has been published and the bug is being set to Fix Released
1751803,2018-03-14 11:15:29 UTC,This bug was fixed in the package linux-hwe - 4.13.0-37.42~16.04.1
1751803,2018-03-14 01:30:53 UTC,Hardware Certification have begun testing this -proposed kernel.
1751803,2018-03-13 14:16:23 UTC,"bug 1755073 is not considered to be a blocker for the promotion of this package, so I'll set 'Regression Testing' as 'Fix Released'."
1751803,2018-03-13 06:06:39 UTC,The ThunderX ARM64 node is affected by bug 1755073 as well.
1751803,2018-03-12 12:26:00 UTC,"There is a deployment issue for node gonzo with i386 lowlatency kernel, it seems that it will stuck on rebooting with the lowlatency kernel (deployment task works with other nodes, just not this one, but the weird thing is that i386 generic works fine on this one)"
1751803,2018-03-14 06:51:17 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.13.0-37.42~16.04.1/xenial-4.13-proposed-published.html"
1751804,2018-02-26 15:55:33 UTC,"Hi Trinh,"
1751804,2018-02-26 16:05:36 UTC,"Hi Yossi,"
1751804,2018-02-27 01:21:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548109"
1751807,2018-03-14 12:04:37 UTC,The package has been published and the bug is being set to Fix Released
1751807,2018-03-14 01:33:58 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.13.0-1015.16/raspi2-4.13-proposed-published.html"
1751807,2018-03-14 11:15:54 UTC,This bug was fixed in the package linux-raspi2 - 4.13.0-1015.16
1751807,2018-03-14 01:30:37 UTC,Hardware Certification have begun testing this -proposed kernel.
1751812,2019-09-12 20:16:08 UTC,The combination Shift+/ (or any symbol for that matter) is not valid anymore (and can't be entered into the hotkye setter). The hotkey will default to the uppercase symbol (whatever is on the upper key portion).
1751812,2019-09-12 19:55:37 UTC,"I remember some work being done on this, and it doesn't reproduce for me; did it get fixed?"
1751812,2018-02-26 16:05:01 UTC,I can not find that commit in master.
1751812,2018-02-26 17:52:14 UTC,It happens in both the legacy and modern canvases.
1751812,2018-04-03 12:56:48 UTC,I fixed this in the legacy canvas but not the gal canvas.  There is something strange going on with the way the new tool framework handles key events so I'm going to defer this to v6 as part of the fix for all key events that have this issue.
1751812,2018-02-26 16:28:11 UTC,It looks like Tom is using the OCC patch on top of master.
1751819,2018-05-11 15:35:45 UTC,This change was made by a bot.
1751829,2018-02-26 16:28:01 UTC,"StacktraceTop:
 InitializeUserDataDir () at ../../chrome/app/chrome_main_delegate.cc:450
 PreSandboxStartup () at ../../chrome/app/chrome_main_delegate.cc:804
 Initialize () at ../../content/app/content_main_runner.cc:655
 Main () at ../../services/service_manager/embedder/main.cc:413
 content::ContentMain(content::ContentMainParams const&) () at ../../content/app/content_main.cc:19"
1751829,2018-04-03 02:28:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751839,2018-03-13 06:19:18 UTC,"3.13.0-143.192~precise1 - generic
Regression test CMPL."
1751839,2018-03-13 09:31:50 UTC,The package has been published and the bug is being set to Fix Released
1751842,2018-03-02 17:32:01 UTC,It's a bit big for juju status output:
1751842,2018-03-02 17:45:10 UTC,"I'm not saying make it part of the juju status output, except maybe to
summarize - i.e. just show health status there."
1751842,2018-03-05 13:47:56 UTC,@jhobbs  I think incorporating ceph health summary into workload status is a good idea.  Please raise a separate wishlist bug to represent that feature request.  Thank you.
1751842,2018-03-09 19:21:39 UTC,Looks like this might be an haproxy timeout after all: http://paste.ubuntu.com/p/bKynKjcJGt/
1751842,2018-03-15 11:59:22 UTC,"Snip from glancelient (source for ""Error finding address for"")"
1751842,2018-03-19 15:11:23 UTC,"James,"
1751842,2018-03-15 12:03:57 UTC,"unfortunately the actual underlying error is hidden here; re the original bug report - yes there are successful requests to the glance API, but they don't appear to correspond timestamp wise to the 180 second timeout detailed (the good requests are some seconds later)."
1751842,2018-03-15 12:31:56 UTC,"Marking Incomplete for now as I still don't think we understand the root cause of the error, and we don't have a reproducer as a result."
1751842,2018-03-02 17:27:17 UTC,I've filed https://bugs.launchpad.net/charm-ceph-mon/+bug/1752942 to track the separate identified bug in failure domain configuration that should not be affecting this situation
1751842,2018-03-22 09:09:41 UTC,Logs won't help - I need a reproducer or access to a system which is exhibiting this issue.
1751842,2019-01-31 16:14:56 UTC,"Looks like it is not just glance:
shade.exc.OpenStackCloudException: Error fetching keypair list (Inner Exception: Unable to establish connection to http://10.244.40.91:8774/v2.1/os-keypairs: HTTPConnectionPool(host='10.244.40.91', port=8774): Max retries exceeded with url: /v2.1/os-keypairs (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f599ff4d110>: Failed to establish a new connection: [Errno 113] No route to host',)))
Exception in thread Thread-3 (most likely raised during interpreter shutdown):
Traceback (most recent call last):"
1751842,2018-03-15 12:02:17 UTC,I think this is raised from a requests.exceptions.ConnectionError exception in keystoneclient which handles the actual URL call.
1751842,2018-03-02 17:24:30 UTC,"Chris, why not build ceph status into the charm's update status hook?"
1751842,2018-03-15 11:53:07 UTC,shade.exc.OpenStackCloudException: Image creation failed: Error finding address for http://10.244.40.85:9292/v2/images/2c1e2ceb-3142-46f8-93ac-ea0eac00509b/file: Unable to establish connection to http://10.244.40.85:9292/v2/images/2c1e2ceb-3142-46f8-93ac-ea0eac00509b/file
1751842,2018-03-02 17:09:34 UTC,"@jason-hobbs, looking a bit into the charms, and the juju status of one of the deployments, it is clear to me there there is a bug in the ceph* charms, in that we never update crush to actually use a configuration based failure domain (ceph-osd: https://github.com/openstack/charm-ceph-osd/blob/master/hooks/ceph_hooks.py#L193 ; ceph-mon: https://github.com/openstack/charm-ceph-mon/blob/master/hooks/ceph_hooks.py#L370); however, you should be using the availability zone support, so should not be affected by that bug."
1751842,2018-02-26 21:01:01 UTC,"If that works, should we change the standard charm timeouts?"
1751842,2018-02-27 19:07:12 UTC,We are still hitting this with:
1751842,2018-02-27 19:35:41 UTC,Bump to field high due to repeat blocking failures in CI
1751842,2018-02-27 22:01:40 UTC,Some ceph errors from a run today that hit this:
1751842,2018-03-02 17:11:14 UTC,"This bug is invalid for glance, it is a ceph bug."
1751842,2018-02-27 23:11:50 UTC,"We need to add logging of when we start the request, and when the request finishes. This may be in the rally logs; we are missing some due to a bug in our log collection. We'll get that fixed, and add logging to the other place this is happening."
1751842,2018-02-27 22:11:06 UTC,http://paste.ubuntu.com/p/j8dfT4qk9n/ Here is the bundle from comment #7
1751842,2018-02-26 17:41:31 UTC,"Speaking the David Ames on IRC, it sounds like we may be able to solve/workaround this by increasing the server/client haproxy timeouts for glance."
1751842,2018-02-28 23:47:53 UTC,Also the ceph-mon relation exists. Which may be competing storage backends.
1751842,2018-03-01 21:55:21 UTC,We've updated our bundle to remove the cinder-volume-service relation and will re-test.
1751842,2018-03-02 00:45:07 UTC,This turns out to be a ceph-mon/ceph-osd problem. When customize-failure-domain=True ceph comes up degraded. This may be a bug in ceph-mon/ceph-osd or it may be a misconfiguration of Juju availability zones. I'll discuss with my team.
1751842,2018-03-02 16:18:23 UTC,"If customize-failure-domain is enabled, then the Juju deployment *must* have multiple availability zones available, either through the Juju Availability Zone configuration, or through juju configuration on the ceph-osd charms (where you would need three+ application deployments)."
1751842,2018-03-02 16:34:14 UTC,"We do have multiple availability zones in our deployment; we have 3 of them. I'm not sure which charm this should be against at this point, but it shouldn't be invalid across the board."
1751842,2018-02-28 23:45:26 UTC,Found this warning in the glance logs:
1751842,2018-02-26 17:42:02 UTC,I've changed our timeout values from 90 seconds to 180 seconds; we will report if we continue to hit this.
1751846,2018-02-26 17:43:20 UTC,"Here's a OGV File displaying the problem. As shown in the video, new applications windows minimize, max, close buttons are not appearing in the upper-left-hand corner as well as a portion of the window."
1751846,2018-02-26 20:32:45 UTC,This also occurs even if I make other workspaces and try to create new windows in it.
1751846,2018-05-21 16:19:40 UTC,works fine if 32 bits
1751847,2018-02-26 23:55:02 UTC,*** This is an automated message ***
1751847,2018-03-05 15:25:18 UTC,"I have performed a NEW review on this package and everything looks good: copyrights, building, lintian-clean, unit testing. I will need a double-check from a more experience archive admin, but as far as I am concerned this is good to be accepted into bionic universe."
1751847,2018-03-06 17:13:24 UTC,Accepted.
1751850,2018-02-27 09:10:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1751850,2018-05-07 22:50:27 UTC,This is due to the installation script doesn't consider that PC variant of grub *may* co-exist.  Here's a patch that forces it to install Signed EFI variant of GRUB bootloader instead.
1751850,2018-05-08 00:41:48 UTC,"The attachment ""ubuntu-bug-1751850.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1751859,2019-07-28 04:17:42 UTC,[Expired for OpenStack nova-compute charm because there has been no activity for 60 days.]
1751859,2018-05-29 19:24:34 UTC,"FYI, going ""incomplete,"" given that we cannot reproduce it, and it's not currently observed anywhere that we know of."
1751859,2018-03-23 13:57:59 UTC,"I've got jupyter notebook with a lot of stats that I'll publish to an instance in serverstack (internal IP) ... some very interesting things to look at around memory usage, disk IO, and rabbitmq message timeouts.  I'll get something up in the next few days. (also attach a pdf to this bug report)."
1751859,2018-05-21 13:00:58 UTC,"No update on this one in a while and it is in danger for failing High SLA requirements of ""Significant attention will be given to the issue"" Please update."
1751859,2018-05-08 20:41:25 UTC,Field High SLA now requires that a estimated date for a fix is listed in the comments. Please provide this estimate for the open tasks.
1751859,2018-04-24 11:15:54 UTC,Just to build on Ryan's comment:
1751859,2018-04-23 15:32:08 UTC,"There isn't one thing that will resolve this, in our view.  The next steps are for more people to analyze this data, and testing theories on the various fronts of potential contention.  We've solicited input from additional engineers."
1751859,2018-04-19 21:54:03 UTC,"Thanks for the analysis, that is an amazing document!"
1751859,2018-04-09 11:59:24 UTC,"Please see the attached of the analysis I did on the Juju crash dump files.  There were no Tracebacks or other crashes in the logs, so I started staring at the log files.  I then thought it might be useful to actually try to graph what's going on in the system."
1751859,2018-03-29 20:32:42 UTC,"At the moment, our only line on this bug is one of system load."
1751859,2018-03-21 13:33:43 UTC,"Even so, given that these systems are running writeback bcache with nvme cache devices, 90 MB/s disk write should not be a bottleneck."
1751859,2018-03-21 12:14:15 UTC,"Actually, scratch juju status, as that's in the crashdump.  Thanks."
1751859,2018-03-21 13:07:26 UTC,"@tinwood coincidentally, that /var/log/load/iotop.log file exposes running processes, so you may be able to derive the info you were seeking in comment #6."
1751859,2018-03-21 13:28:05 UTC,"whoops, storage i/o goes much higher than 2 MB/s sometimes; I wrongfully assumed it was all in K/s in the first look:"
1751859,2018-03-14 19:53:04 UTC,escalated to field high
1751859,2018-03-21 11:25:46 UTC,Which nova-compute units were failing please?
1751859,2018-03-21 12:33:11 UTC,"Do we have a way to know the system load of the metal hosting rabbitmq?  I ask because these look like amqp messaging timeouts, which we know can happen with too much resource contention."
1751859,2018-03-21 12:49:40 UTC,"Okay, I've had a good trawl through the logs in the crash dump and the only errors I can find are amqp (rabbitmq) related timeout errors.  However, the logs appear to show that rabbit is happy."
1751859,2018-03-20 21:25:28 UTC,Added the bundle and juju-crashdump from the latest recreate.
1751859,2018-03-21 12:55:37 UTC,"The crashdump includes load information in /var/log/load - top and
iotop output is collected every 30 seconds."
1751859,2018-03-21 13:01:25 UTC,Here's CPU utilization numbers from the crashdump.  None of the systems ever exhaust their CPU resources:
1751859,2018-03-21 13:04:35 UTC,"Answering my own question:  /var/log/load in the baremetal units within the crashdump tarball, contains load info.  Please cross-reference amqp timeouts with load spikes."
1751859,2018-03-21 12:54:48 UTC,"Alex, these failures come from a CI setup. If additional logging is
needed, I would suggest that it be added to the charm."
1751859,2018-03-21 13:06:05 UTC,storage i/o is also low; peak is 2 MB/s write. http://paste.ubuntu.com/p/bPYCsKpWRF/
1751866,2018-05-11 15:36:00 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1751866,2018-07-11 04:17:49 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1751883,2018-12-28 18:27:37 UTC,"I realized this is why I turn off the option to rescan the library on startup. If that did not block the GUI, I would gladly leave that option enabled."
1751883,2018-09-15 20:05:37 UTC,Is this still an issue with Mixxx 2.1.4?
1751883,2018-02-27 08:20:34 UTC,"Small correction from my side: mixxx 2.1 is linked against Qt 4.8.7.
I didn't investigate correctly yesterday."
1751883,2018-12-27 20:02:28 UTC,This still happens in master.
1751883,2018-02-26 22:54:36 UTC,"If I  start the library scanner from the menu later, everything works lieke expected"
1751883,2018-02-26 22:49:37 UTC,"OK, than there is no need to rebuild it with Qt4."
1751883,2018-02-26 22:19:30 UTC,"hey Be, this is not a duplicate of #1738227.
#1738227 is about the *analyzer*, this bug report is about the *library scanner*.
The fixes for #1738227 are part of the 2.1 branch already."
1751883,2018-02-26 20:22:26 UTC,"Is it your own build made with qt5?
Is a qt4 version also effected?"
1751883,2018-02-27 06:59:49 UTC,"We are now correctly using a dedicated, thread-local database connection for each thread. Could this issue with the library scanner be caused by internal synchronizations within SQLite that prevent to create concurrent transactions for different connections? Just a thought, we need to validate this."
1751886,2018-08-29 21:21:39 UTC,Isn't tracking calls across systems the purpose of request_id and global_request_id (both of which are in the context)?
1751889,2018-03-08 19:18:34 UTC,Hello I am having the same issue on 3 different accounts at the same time.
1751889,2018-02-27 12:11:01 UTC,"Hello,"
1751889,2018-02-27 13:36:14 UTC,"Hi thanks for your answer, the thing is that message appears even in the channel that I just join after the join the message apper an I cant send even a one message, also I asked to me admin of some channel using another way (email) about if I was block and they said that not at all, I looking in internet another users has the same problem, I was not banned in any of the channels until now so please can you help me checking what happend"
1751889,2018-02-27 13:42:05 UTC,But th way this is my phone number 593995884050 maybe this could help checking in the main system what is happening
1751897,2018-02-26 21:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1751909,2018-02-26 21:34:48 UTC,I seem to be able to import larger filesystems just fine
1751909,2018-02-26 21:56:08 UTC,juju controller machine-0.log | http://paste.ubuntu.com/p/6hd5JbxJ5W/
1751909,2018-02-27 07:55:30 UTC,I don't see an actual error in: https://paste.ubuntu.com/p/FX9qbmbQGQ/ is it just that machine 4 (for elasticsearch/4) stays in allocating?
1751909,2018-02-27 13:25:36 UTC,"@jameinel yeah ...... the other part is such that if you import the volume and attach it, it will hang and never attach."
1751909,2018-03-05 21:58:42 UTC,"What seems to be happening is that ""--storage foo=ebs,2000G"" defaults to the standard volume-type:"
1751909,2018-03-05 22:09:36 UTC,"Also worth noting.. gp2 is probably the same as the default juju ""ebs-ssd"" storage pool, meaning you might be able to do the following without creating a new pool:"
1751909,2018-03-05 22:19:50 UTC,"Oh mylanta, we *do* expose an error... It's not obvious at first:"
1751909,2018-03-05 22:31:33 UTC,"@kwmonroe ""How about we set the storage status to something besides 'pending' if the underlying volume is in 'error'?:"" - 100%"
1751909,2018-03-13 02:04:51 UTC,"Filed this https://bugs.launchpad.net/juju/+bug/1753593 in support of st1, sc1, and io1."
1751909,2018-02-26 21:40:04 UTC,"but alas, I still get a failure with the larger volume https://paste.ubuntu.com/p/zzYHGH2mNT/"
1751910,2018-02-27 07:09:37 UTC,"Indeed, most profiles on my system for GTK/GNOME apps either include abstractions/dconf or have its content inlined (from the days when we could not rely on the dconf abstraction, which did not exist back then). I would not mind including abstractions/dconf in abstractions/gnome but it will require careful coordination with profiles that already include abstractions/gnome and dconf-related rules. I think a good first step would be to first de-duplicate dconf-related rules for all profiles in apparmor.git and apparmor-profiles.git: include the dconf abstraction instead and drop the corresponding lines. This would require a dedicated bug/branch."
1751913,2018-04-06 06:23:06 UTC,"Change abandoned by wangqi (wang.qi@99cloud.net) on branch: master
Review: https://review.openstack.org/548298"
1751913,2018-02-27 14:20:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548298"
1751913,2018-03-13 15:15:07 UTC,"wangqi, Are you still working on this bug?"
1751920,2018-02-27 14:41:41 UTC,The 5.5 series update for 14.04 is now available.
1751920,2018-02-27 14:46:38 UTC,The 10.0 series update for 16.04 is now available.
1751920,2018-03-06 15:25:28 UTC,This bug was fixed in the package mariadb-5.5 - 5.5.59-1ubuntu0.14.04.1
1751920,2018-03-06 15:25:30 UTC,This bug was fixed in the package mariadb-10.0 - 10.0.34-0ubuntu0.16.04.1
1751920,2018-04-15 04:50:55 UTC,Unsubscribing the Security Sponsors Team for now because there's nothing to sponsor for 10.1 yet. Please resubscribe us once you have the Artful debdiff.
1751920,2019-06-11 14:25:58 UTC,Setting mariadb-10.1 to 'Fix Released' as Bionic (1:10.1.34-0ubuntu0.18.04.1) and newer releases already contain the fixes for those CVEs.
1751927,2018-02-26 22:51:07 UTC,"StacktraceTop:
 g_settings_set_property (object=0x7f131800fe10, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at ../../../../gio/gsettings.c:590
 object_set_property (nqueue=0x1a82730, value=<optimized out>, pspec=0x1a758d0, object=0x7f131800fe10) at ../../../../gobject/gobject.c:1439
 g_object_new_internal (class=class@entry=0x1a9a270, params=params@entry=0x7ffe9c031c00, n_params=n_params@entry=1) at ../../../../gobject/gobject.c:1831
 g_object_newv (object_type=26033328, n_parameters=n_parameters@entry=1, parameters=parameters@entry=0x1aa42a0) at ../../../../gobject/gobject.c:2030
 pygobject_constructv (self=self@entry=0x7f1329309288, n_parameters=1, parameters=0x1aa42a0) at ../../gi/gobjectmodule.c:990"
1751929,2018-02-26 22:40:40 UTC,ara.json from failed deploy
1751929,2018-02-26 22:41:42 UTC,command-ZIP_DEFLATED from failed deploy
1751929,2018-02-26 22:42:24 UTC,setup-ZIP_DEFLATED from failed deploy
1751932,2019-10-07 14:23:15 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc2 release candidate.
1751932,2020-11-06 15:21:13 UTC,"Reviewed:  https://review.opendev.org/729657
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=5fec81daa6b0cd694bb8987abdd88e0e6106bdfc
Submitter: Zuul
Branch:    stable/stein"
1751932,2020-05-20 16:34:10 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/729657"
1751932,2020-02-18 11:07:19 UTC,This issue was fixed in the openstack/cinder 16.0.0.0b1 development milestone.
1751932,2019-10-04 15:40:13 UTC,"Reviewed:  https://review.opendev.org/686519
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=7b227c647d5d81c1ae9e54b0e5fd76cc07c73257
Submitter: Zuul
Branch:    stable/train"
1751932,2018-10-17 19:36:26 UTC,From launchpad definition[1]: Triaged -> the bug supervisor considers that the bug report contains all information a developer needs to start work on a fix.
1751932,2019-10-01 13:09:27 UTC,"Change abandoned by Erlon R. Cruz (<email address hidden>) on branch: master
Review: https://review.opendev.org/671510
Reason: This was fixed in another patch for SolidFire."
1751932,2019-09-30 11:54:38 UTC,"Change abandoned by Thiago Correa (<email address hidden>) on branch: master
Review: https://review.opendev.org/668557
Reason: fix merged on patch: https://review.opendev.org/#/c/675630/"
1751932,2019-09-27 04:11:32 UTC,"Reviewed:  https://review.opendev.org/675630
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=215d6b2b272847d695c5c5d17c9d387e123b1396
Submitter: Zuul
Branch:    master"
1751932,2019-07-18 15:27:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671510"
1751932,2019-04-09 15:43:57 UTC,"Do we have more information on this? Could you, please, provide some extra information about the environment (OS version, whether python 3 was enabled or not) on which this bug happens?"
1751932,2018-10-16 16:53:59 UTC,"Status indicates ""triaged"" but I'm not clear how.  Has this behavior been mitigated or is there some mechanism for workaround available?  Or is ""triaged"" an indication of something else entirely?"
1751932,2019-10-04 03:20:48 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/686519"
1751951,2019-10-27 10:18:54 UTC,Debian has now packaged an experimental version of 2.82 (https://tracker.debian.org/pkg/e3)
1751954,2020-12-04 01:40:36 UTC,Also reported here: https://askubuntu.com/questions/1296506/ubuntu-20-04-why-does-turning-off-wi-fi-can-be-turned-off-to-save-power-turn
1751954,2019-10-24 22:13:06 UTC,"This appears to have been partially fixed upstream at
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/53"
1751954,2018-02-27 16:35:17 UTC,"Ok, I reopened this and adjusted the bug title a bit."
1751954,2019-10-24 22:09:01 UTC,Point to currently open bug on GNOME Gitlab (which has further references to related bug reports)
1751954,2018-02-27 01:00:26 UTC,See also https://bugzilla.gnome.org/765279
1751954,2018-02-27 00:55:24 UTC,I'm going to go ahead and close this bug. You're welcome to try to talk to the GNOME Design Team about this if you think it is confusing. The best way to reach them is via IRC. They can be found in the #gnome-design channel on irc.gnome.org during European business hours.
1751954,2018-02-27 00:53:40 UTC,"That is literally the off switch for Wi-Fi. It is not a ""turn off wifi when my screensaver turns on"" switch."
1751954,2018-02-27 00:43:28 UTC,Same bug reported for redhat: https://bugzilla.redhat.com/show_bug.cgi?id=1495433
1751954,2018-02-27 14:40:26 UTC,"Oh, yes, very bad design :) Thanks for the info and the link Jeremy!"
1751963,2019-04-04 03:37:27 UTC,Please provide more details about what kind of files don't play and in what app(s) you are trying to play them.
1751963,2019-06-03 04:17:32 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1751990,2018-04-04 03:47:32 UTC,apport information
1751990,2018-04-04 03:47:35 UTC,apport information
1751990,2018-04-04 05:15:08 UTC,"log are produced by using kernel 4.8 since 4.13 will not boot, will not be able to do anything,(do you want a log from 4.13 with cuda?)"
1751990,2018-04-04 05:17:45 UTC,just additional attached file
1751990,2018-04-04 05:30:56 UTC,Not sure how to     add the tag: 'kernel-bug-exists-upstream'
1751990,2018-05-11 18:02:18 UTC,"After
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
sudo apt upgrade"
1751990,2018-04-27 19:00:47 UTC,"add kernel parameter ""blacklist=nouveau modprobe.blacklist=nouveau"" will help to boot up for kernel 4.13 and 4.16, but does not solve nvidia problem"
1751990,2018-05-02 03:27:51 UTC,Try reinstalling the driver?
1751990,2018-05-11 19:04:43 UTC,for both 4.13 and 4.16
1751990,2018-04-10 03:47:24 UTC,"Does blacklist nouveau work for you? e.g. add kernel parameter ""blacklist=nouveau modprobe.blacklist=nouveau""."
1751990,2018-04-04 03:47:29 UTC,apport information
1751990,2019-10-03 10:39:17 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1751990,2018-04-04 03:47:25 UTC,apport information
1751990,2018-04-02 20:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1751990,2018-04-04 03:47:07 UTC,apport information
1751990,2018-04-04 03:47:09 UTC,apport information
1751990,2018-04-04 03:47:11 UTC,apport information
1751990,2018-04-04 03:47:13 UTC,apport information
1751990,2018-04-03 16:57:51 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1751990,2018-04-04 03:47:17 UTC,apport information
1751990,2018-04-04 03:47:19 UTC,apport information
1751990,2018-04-04 03:47:21 UTC,apport information
1751990,2018-04-04 03:47:23 UTC,apport information
1751990,2018-04-04 03:47:15 UTC,apport information
1751990,2018-04-04 03:47:27 UTC,apport information
1751996,2018-08-29 15:14:59 UTC,"I can confirm this behavior, although I will note that if you want dependency management then running setup.py install directly is not recommended (so this may have been intentional behavior, but I'm not sure). It's better to use pip install ."
1752006,2018-02-27 08:06:34 UTC,"So do You want to add some validation and ""nice"" error message that fwaas is not compatible with Linuxbridge agent or You want to add support for fwaas in LB agent?"
1752006,2018-02-27 09:00:52 UTC,"@Slawek:
IMO, it's better to support fwaas in LB agent. But I'm not sure if fwaas team has a plan for supporting iptables driver for fwaas. However, at least we can make firewall l2 agent to be more generic by moving 'request_int_br' to driver side. Do you think so?"
1752006,2018-02-27 09:14:17 UTC,"request_int_br is method from ovs agent extension API class AFAIR. It shouldn't be added to LB agent extension class as there is no int_br in LB agent at all.
IMO it would be good to propose some simple (I hope) patch which will tell user that ""this L2 agent is not supported with fwaas"" or something like that and later propose patch which provides such support for LB agent and iptables driver (if there are such plans).
What do You think about it?"
1752006,2018-02-27 09:24:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/548195"
1752006,2018-02-27 09:40:23 UTC,"@Slawek: IMO, it's better to note that in document because if operator doesn't specify firewall_l2_driver for firewall l2 agent extension, then firewall_l2_driver will be set to 'noop' as [1]. So I think we don't need to log something in code. What do you think about that option?"
1752006,2018-02-27 09:58:36 UTC,Updating docs sounds reasonable for me :)
1752006,2018-03-01 12:11:26 UTC,"Reviewed:  https://review.openstack.org/548195
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=acc08e0da71eb23c869f4053c876bf7f25028f89
Submitter: Zuul
Branch:    master"
1752014,2018-06-18 14:17:11 UTC,"The following object list exist the same problems:
cluster\profile\node\policy\receiver\action\event"
1752014,2018-06-20 07:23:50 UTC,review url: https://review.openstack.org/#/c/576374/
1752014,2018-06-18 14:29:31 UTC,"Yes, This problem is openstacksdk not support api limit return."
1752020,2018-03-06 22:46:24 UTC,What git hash does this occur on?
1752022,2018-02-27 10:38:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548212"
1752024,2018-02-27 09:08:28 UTC,"Thanks Tim for reviewing those, some comments"
1752024,2018-02-28 09:53:10 UTC,Yes it probably makes sense to wait until after the LTS to drop those. Will revisit early next cycle.
1752042,2018-02-27 15:38:59 UTC,"But Shutter uses GTK2, not GTK3. Does the problem appear with a particular icon theme or with all themes?"
1752042,2018-02-27 16:16:51 UTC,"This icon doesnt exist in any newer icon themes because of the ""deprecated"" stuff, so if you have a more recent install (ubuntu bionic atm), none of the tested icon themes has this icon anymore.
From the second link:
'... Use named icon ""dialog-information"".'"
1752042,2018-02-27 18:41:56 UTC,"Well, I am using the Faenza theme which doesn't ship the gtk-index icon as well. But Shutter falls back to some icon which seems to be neither shipped with Shutter itself nor part of the Faenza theme."
1752047,2020-06-04 02:42:31 UTC,What was the original problem you experienced? Is it still happening?
1752047,2020-08-03 04:17:32 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1752054,2020-11-20 04:17:24 UTC,[Expired for mate-themes (Ubuntu) because there has been no activity for 60 days.]
1752060,2018-10-01 12:53:45 UTC,"Hi,
This bug is caused by typo in property call wifiobj. It is supposed to be wifiObj. Im including patch which fixes it."
1752060,2018-08-20 19:12:58 UTC,"ubuntu 18.04, HPLaserJet P1102w
same problem"
1752060,2018-04-18 18:13:00 UTC,I have the same printer (HPLaserJet P1102w) and get the same error on Ubuntu 16.10 LTS.
1752060,2018-04-07 19:40:24 UTC,Same problem with HPLaserJet P1102w on Ubuntu 18.04 (beta)
1752060,2018-03-07 07:29:47 UTC,"Same problem. I use mobile hotspot and have no chance to configure the wifi hotspot in term of ""protection""."
1752060,2018-02-28 05:31:25 UTC,"Hi Boyd,"
1752060,2018-02-27 21:35:13 UTC,"Yeah it has always worked in the past. Some update of something has broken
it."
1752060,2018-02-27 21:16:48 UTC,I can also confirm the very same bug on Fedora 26 running 3.17.11-3.fc26
1752060,2018-02-28 15:49:59 UTC,Sorry its an HPLaserJet P1102w
1752060,2018-02-27 20:27:23 UTC,Is your wireless-capable device one which is supported by this utility?
1752064,2018-02-27 11:31:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752064,2018-03-05 21:17:46 UTC,"For those who cannot access errors.ubuntu.com, here is the stacktrace."
1752064,2018-03-05 21:22:29 UTC,"According to the crash tracker, this happened since 0.91 all the way to current PPA builds (with a huge spike for 0.91-7ubuntu2 in ubuntu 16.04, but that's probably only because of the LTS, etc)."
1752067,2018-02-27 12:12:03 UTC,"StacktraceTop:
 ?? ()
 ms_dirty_update (timeout=0x7ffdf2b3a514, screen=0x558435ee2110) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:636
 msBlockHandler (pScreen=0x558435ee2110, timeout=0x7ffdf2b3a514) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:680
 BlockHandler (pTimeout=pTimeout@entry=0x7ffdf2b3a514) at ../../../../dix/dixutils.c:394
 WaitForSomething (are_ready=<optimized out>) at ../../../../os/WaitFor.c:219"
1752081,2018-05-18 20:05:22 UTC,"Just rebooted with 4.13.0-41-generic kernel, everything working fine again. Clearly 4.15.0-20-generic is at fault here."
1752081,2018-05-18 19:59:07 UTC,"Same here on 18.04, causing a Qualcomm QCA9880 3x3ac card to not even show up in lspci. ath10k driver is gone as well."
1752081,2018-05-16 09:02:23 UTC,Same issue on Cosmic.
1752082,2018-03-04 20:14:18 UTC,This also effects Lmod on my system.
1752082,2019-04-23 12:27:40 UTC,"The attachment ""lua-posix-debbug-891541.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1752082,2019-04-23 10:18:14 UTC,"Here's the packaging patch from debian, please fix this issue in bionic."
1752082,2019-04-18 06:32:03 UTC,"Please fix this, we are getting the same error with lmod."
1752082,2019-02-14 10:56:47 UTC,This is still not fixed.
1752082,2019-01-11 06:33:03 UTC,"Hmm, this is still not fixed! :(
Without the fix you get a window, after logging in, with a stack trace saying ""posix.ctype not found""."
1752082,2018-07-28 09:17:28 UTC,"Can confirm and agree with the previous comments. This should have been fixed in the LTS .1 release, but it's not. It breaks my Lmod installation and fixing it manually on a couple of workstations is annoying to say the least. Please roll out 33.4.03!"
1752082,2019-03-19 22:37:40 UTC,"Yes, it looks like we need to go from lua-posix package version 33.4.0-2 to something slightly newer.  This is on Ubuntu 18.04.x"
1752082,2018-07-09 12:05:25 UTC,We need lua-posix 33.4.0-3 on Bionic
1752082,2018-04-20 10:46:32 UTC,"@Thomas (Tvk7) it looks like you are using lua 5.2, where as Alex G's symlink solution is for lua 5.1."
1752082,2018-04-11 17:35:30 UTC,"Debian has just released a fixed package version, lua-posix 33.4.0-3:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891541#34"
1752082,2018-04-11 09:47:09 UTC,"The link, at least for me, brings up the next error:"
1752082,2018-03-12 15:24:18 UTC,The reason for this happening is that lua-posix changed its main module name from posix_c to posix. The maintainers of the debian package missed that and still install a symlink from /usr/lib/x86_64-linux-gnu/lua/5.1/posix_c.so.
1752082,2018-03-10 21:50:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752082,2018-07-25 09:29:56 UTC,Could you pleeeease roll out the simple fix for the simple problem? This breaks all 3rd party software with dependency to lua 5.2 (and probably also 5.3?). It's a PITA to tell all users how to manually fix this problem.
1752082,2018-07-11 20:33:33 UTC,Works for me: Grab lua-posix 33.4.0-3 binary deb from https://packages.ubuntu.com/cosmic/lua-posix and install on bionic.
1752083,2018-03-06 06:43:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752083,2018-03-25 03:59:47 UTC,Are you still experiencing this bug?
1752083,2018-03-25 06:08:39 UTC,This is still logged on a fully updated bionic (with 'proposed' archive enabled)
1752083,2018-03-25 12:52:06 UTC,I can't duplicate this bug with the test case you provided in comment #5.
1752083,2018-07-02 09:23:32 UTC,I'm having this issue with cairo session. With normal gnome session it works fine.
1752083,2018-11-18 00:08:47 UTC,Issue exists on 18.10 Cosmic Cuttlefish.
1752083,2019-05-17 12:59:46 UTC,I have the same issue after installing amdpgu proprietary driver. Is there any resolution?
1752085,2018-07-19 17:25:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752091,2018-04-06 02:12:47 UTC,The error is now gone.
1752091,2018-03-02 15:00:24 UTC,Trying to install daily build 3/1/18 and seeing the install window close (no error indicated) right after collecting user data from the Who are You screen.  Checking the syslog on the install system found this error as the last entry.
1752091,2020-02-22 10:49:23 UTC,"In my case, the bug apparead when I mounted an encfs volume andf began to navigate on it"
1752091,2019-12-12 05:36:20 UTC,hey TJ have you got a version for 19.10 ?
1752091,2019-11-30 20:37:22 UTC,"Hello TJ, your gvfs-package build on https://launchpad.net/~tj/+archive/ubuntu/bugfixes seems to have resolved the problem for me! Therefore, a 1000 thanks! :-)"
1752091,2019-10-14 10:18:33 UTC,I've built a test package for 18.04 in my PPA if you want to test it:
1752091,2019-07-27 10:43:20 UTC,g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed happens on my device as of recently downloaded image
1752091,2019-07-07 21:37:17 UTC,Still observed here.
1752091,2019-06-06 22:48:38 UTC,"Yes Antonio (tonecas), this looks promising indeed."
1752091,2019-05-10 23:28:36 UTC,same problem here. don't know where this is coming from but it maybe related to this:
1752091,2019-05-09 14:04:27 UTC,I have the same problem when trying to start the current mysql service after changing the datadir in the mysql.d cnf file. Using 18.04 LTS.
1752091,2019-04-25 23:33:31 UTC,One of IHV parnter get this issues too during stressapp + iperf testing. LP#1823615
1752091,2019-04-23 02:06:55 UTC,I encounter this problem trying to install 18.04.2 in QEMU
1752091,2020-09-05 05:29:59 UTC,"In my case, the bug apparead when I mounted an Cryptomator volume and began to navigate on it. Ubuntu 18.04"
1752091,2019-02-14 07:30:58 UTC,"I found this fix:
https://gitlab.gnome.org/GNOME/gvfs/commit/d7e1397854f32e793b4f65d894908d67072dcb3f"
1752091,2018-03-02 17:21:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752091,2018-03-02 17:27:05 UTC,"The prior attempt to install was with a USB.  Create a bootable DVD with the same daily build level and the install process failed at the same location, right after the Who are You? screen.  Couldn't get to the syslog because the install process was no longer responding so could not verify the G_UDEV_IS_DEVICE failure message."
1752091,2018-03-15 07:31:55 UTC,"Same issue here: Ubuntu 18.04 daily build, dated 14-03-18
message repeated 7 times: [ g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed]"
1752091,2019-03-27 12:09:04 UTC,"This bug affects me, wait for updating"
1752091,2018-03-14 18:14:49 UTC,"Same problem here: Xubuntu 18.04, daily."
1752091,2018-06-01 00:38:56 UTC,I have this issue also.
1752091,2018-06-20 02:03:39 UTC,"Has this bug been fixed?
I encountered this when I trying to install the latest version of 18.04."
1752091,2018-08-03 14:51:31 UTC,I just got the issue on an image I downloaded two days ago. :( Not sure what to do from here.
1752091,2019-01-03 01:46:33 UTC,I can confirm the problem on my system:
1752091,2018-04-19 15:34:50 UTC,still have it here on 18.04
1752096,2019-07-27 18:57:46 UTC,PR welcome.
1752098,2018-12-12 20:04:17 UTC,Possibly related bug 1807996
1752098,2018-04-03 22:08:59 UTC,I saw the same behaviour on Item Status and Holdings View when choosing to delete Copies.
1752098,2018-04-04 13:14:36 UTC,"The setting should be observed, and if it's not after allowing the action then that's a bug.  But the confirmation screen is about what the user actually requested, which is the deletion of a copy.  The deletion of the volume when the last copy is removed is something that happens after the copy has been deleted, and that was neither explicitly requested, nor has it occurred when the dialog is shown to the user.  The dialog is reporting what was explicitly requested by the user so that the user can be sure they didn't mistakenly attempt to delete more (or less) than they intended.  I don't think this dialog, by itself, is a bug."
1752098,2020-04-09 19:35:32 UTC,"When the setting to delete the call number when the last copy is deleted on, it is being observed.   But that means when the dialog says ""Will delete 1 item and 0 call numbers,""  that in fact, is not true. If there is only one item attached to the call number, 1 item and 1 call number will be deleted. The fact that they are being deleted in two separate actions is irrelevant and invisible to the user. They are both occurring as a result of the delete items request, so this dialog is highly misleading and confusing."
1752100,2021-01-04 10:01:11 UTC,This has been fixed for a while now.
1752102,2018-11-13 13:16:03 UTC,What is wanted here is really not clear.  We already have support for multiple storage backends in Cinder.  That is one of the key features.
1752103,2018-02-27 15:49:56 UTC,Trove Blueprint: https://blueprints.launchpad.net/trove/+spec/zaqar-integration
1752103,2018-05-16 14:05:48 UTC,"""(mjozefcz): Catalyst Cloud is working on solution with Zaqar (flwang) - HTTP calls. Similiar use-case is in Octavia (using HTTP calls to Amphora Instance). Dedicated RabbitMQ and securying it with some Rabbit ACL's is pain in the ass - its really slow. We need to exchange our needs and knowledge with Octavia Team."
1752108,2018-04-11 20:30:51 UTC,Testing Xubuntu 18.04 Daily
1752108,2018-02-27 14:43:52 UTC,"StacktraceTop:
 WTFCrash () at ./Source/WTF/wtf/Assertions.cpp:272
 WebKit::WebProcess::ensureNetworkProcessConnection (this=this@entry=0x559b13ad80e0) at ./Source/WebKit/WebProcess/WebProcess.cpp:1127
 WebKit::WebProcess::initializeWebProcess (this=0x559b13ad80e0, parameters=...) at ./Source/WebKit/WebProcess/WebProcess.cpp:383
 IPC::callMemberFunctionImpl<WebKit::WebProcess, void (WebKit::WebProcess::*)(WebKit::WebProcessCreationParameters&&), std::tuple<WebKit::WebProcessCreationParameters>, 0ul> (args=..., function=<optimized out>, object=0x559b13ad80e0) at ./Source/WebKit/Platform/IPC/HandleMessage.h:40
 IPC::callMemberFunction<WebKit::WebProcess, void (WebKit::WebProcess::*)(WebKit::WebProcessCreationParameters&&), std::tuple<WebKit::WebProcessCreationParameters>, std::integer_sequence<unsigned long, 0ul> > (function=<optimized out>, object=0x559b13ad80e0, args=...) at ./Source/WebKit/Platform/IPC/HandleMessage.h:46"
1752108,2018-03-09 23:29:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752108,2018-04-01 14:27:09 UTC,"happened to me, too"
1752108,2018-04-01 17:08:47 UTC,"Testing Xubuntu 18.04 daily, Linux Xubuntu-18-04 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1752108,2018-04-01 23:51:46 UTC,"System:    Host: bionic Kernel: 4.15.0-13-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Xfce 4.12.3 (Gtk 2.24.31)
           Distro: Ubuntu Bionic Beaver (development branch)"
1752108,2018-04-07 01:48:06 UTC,Latest crash from the latest xubuntu 18.04 beta version
1752108,2018-04-13 20:41:28 UTC,I find that only google-chrome causes the webkit crash. I used Firefox on both lxde and xfce without out ever experiencing the crash.
1752108,2020-10-02 08:52:51 UTC,Happened when I selected Run for the Groovy live USB boot
1752115,2018-03-06 22:14:52 UTC,"Reviewed:  https://review.openstack.org/549411
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2941bfd165055348dd584b630d4e631ef05e328
Submitter: Zuul
Branch:    master"
1752115,2018-03-06 22:15:03 UTC,"Reviewed:  https://review.openstack.org/548427
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=139426d51416313e8b14a335695adc7165bc4848
Submitter: Zuul
Branch:    master"
1752115,2018-03-07 16:30:10 UTC,"Reviewed:  https://review.openstack.org/550220
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b006a5ba91d3d8c7c7bfec7d3df6bb1da0aa3cf4
Submitter: Zuul
Branch:    stable/queens"
1752115,2018-04-20 13:13:59 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1752115,2018-03-07 23:30:23 UTC,This issue was fixed in the openstack/nova 17.0.1 release.
1752115,2018-03-06 19:26:57 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550221"
1752115,2018-03-07 20:59:31 UTC,"Reviewed:  https://review.openstack.org/550221
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=370c10453f95cfc42465e6f4b19d96d468b440e0
Submitter: Zuul
Branch:    stable/queens"
1752115,2018-03-06 19:26:38 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/550220"
1752115,2018-03-03 11:13:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/549411"
1752115,2018-03-01 17:44:08 UTC,"You're correct about the shared-targets flag, however that was specifically to solve for locking create/delete of targets on backends using shared-targets.  That's actually a different problem, it means that a single backend has multiple volumes that are all doing data transfer across a single 'shared' target."
1752115,2018-02-28 11:00:12 UTC,"So I'm a little confused here as this seems to be a case of the shared target issue we solved at least on global level, but not per host where it's applicable. It was known that LVM is exporting one target per host. So is this a case we forgot to cover when we introduced the shared_targets flag and mechanisms or is it a completely separate issue?"
1752115,2018-02-28 00:59:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548427"
1752115,2018-02-27 23:58:53 UTC,"So looking into this the problem appears to be that Nova calls the brick initiator disconnect_volume method indiscriminately.  Brick has no way currently to interrogate usage of a connection, and I'm not sure that something like that could be added in this case."
1752115,2018-02-27 18:06:13 UTC,The disconnect is happening in a nova-cpu call to os-brick. The path is:
1752115,2018-02-27 17:23:05 UTC,This is the tempest test wip - https://review.openstack.org/#/c/548356
1752123,2018-03-07 01:29:05 UTC,"That's fine. I knew I was aiming for Wayland sessions on 10-bit support, not Xorg. It might also take some additional mutter work."
1752123,2018-03-06 10:33:52 UTC,"You still can, by setting ""allow_rgb10_configs"" true in drirc for gnome-shell. Only the driver defaults were flipped."
1752123,2018-03-06 06:35:21 UTC,Any chance we could fix the aforementioned tests?
1752123,2018-03-06 13:05:49 UTC,This bug was fixed in the package mutter - 3.27.92-1
1752123,2018-02-28 11:40:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752123,2018-03-02 19:49:20 UTC,This bug was fixed in the package mesa - 18.0.0~rc4-1ubuntu3
1752126,2018-03-07 07:47:34 UTC,I have the same problem. It seems like libvirt* 3.6 is not happy with the qemu 2.10. Manually installing libvirt* 4.0 resolves the dependency issues
1752126,2018-03-08 09:49:48 UTC,"Hi,"
1752126,2019-04-10 10:17:14 UTC,Is this still a problem? The image builds fine in CI.
1752126,2019-06-10 04:17:32 UTC,[Expired for kolla because there has been no activity for 60 days.]
1752130,2018-02-27 18:55:20 UTC,Thanks for reporting this. I'll check this out and add this to new version of specs.
1752130,2018-03-01 06:28:54 UTC,"Hi, this has been added to specs at http://acbf.wikia.com/wiki/References_Section_Definition"
1752130,2018-03-01 13:43:43 UTC,Yay!
1752131,2018-02-28 14:33:16 UTC,"chose another DSM IP and credential,  it work."
1752131,2018-02-27 17:11:40 UTC,"It appears either 10.10.10.23 is not accessible, it that is not the right IP for dsm."
1752131,2018-02-27 19:10:29 UTC,"Dell Storage have two Controller
1. with SN 47884 and IP 10.10.10.21
2. with SN 47883 and IP 10.10.10.22
and Cluster IP is 10.10.10.23 all this IP are accessible from compute node cinder."
1752132,2019-03-26 07:42:18 UTC,Is this still an issue? For me it's fixed.
1752132,2018-03-02 14:37:38 UTC,"Reviewed:  https://review.openstack.org/548358
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=c2538f78f139b8db3ee152a53d916a5b961370f9
Submitter: Zuul
Branch:    master"
1752132,2018-02-28 10:23:56 UTC,Possible dup of bug 1751299? This one has a stack trace and a temporary fix though so we might want to keep it :)
1752132,2018-02-27 17:14:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/548358"
1752133,2019-09-17 15:49:57 UTC,PR here: https://github.com/mixxxdj/mixxx/pull/2286
1752133,2019-08-02 11:42:23 UTC,"I think breaking the sync part of this bug https://bugs.launchpad.net/bugs/1325157
Still happens the rest is legacy. I assume it will be fully fixed after this change."
1752133,2019-08-01 18:38:30 UTC,"OK, thank you for the input. So please Philip go ahead and thank you for taking care."
1752133,2019-08-01 18:24:47 UTC,"I believe I coded the logic for loops which always picks the previous beat.  At the time it seemed to make sense but I can think of plenty of circumstances where the loop has been a beat off that this has annoyed me.  I would be fine changing that to make pick the nearest beat instead.  I don't think we need to sweat the mid-beat problem.  We have loop slide buttons, and if the DJ hits the button at 51% and the loop is a beat off, they really only have themselves to blame."
1752133,2019-08-01 17:05:27 UTC,"As you've already seen in my PR my first thought was to use the closest beat (fraction) to start the loop. If the next beat marker is ahead of the current position use a ""catching loop"". If the previous beat is closer, it behaves like before."
1752133,2019-08-02 12:35:31 UTC,What about this one with setting a Loop Out point? Or you only mean everything seems fixed/better with regards the beatloop function (and sorry for not being 100% clear that's what I meant originally.)
1752133,2019-07-31 21:44:46 UTC,"Ah, OK beatloops are the topic.
Currently they are enabled in a way that the play position is in the loop."
1752133,2019-07-29 13:47:40 UTC,"Some of that may be due to hotcues having been set in an old version where the analyse bug was present (when waveforms often used to be offset) as a couple of them where it looked like the marker was exactly on the beat and it exhibited that behaviour, after deleting and resetting the hotcue it triggers the loop in the right place. Still overall I think the points stand."
1752133,2019-07-29 13:41:24 UTC,How can beatloop_enable ever result in a loop of zero length when it takes the length of the loop from beatloop_size property?
1752133,2019-07-28 13:26:37 UTC,"This was done on demand, in case the resulting loop would have zero length."
1752133,2019-08-01 06:07:44 UTC,"After the discussion here:
https://github.com/mixxxdj/mixxx/pull/2213#issuecomment-517131089
I have realized the real issue.
It behaves odd if the beatloop code results not exactly into the position if the cue point."
1752137,2020-04-09 20:14:37 UTC,Can you provide more details or example files?
1752152,2018-03-29 15:19:14 UTC,I know this is at least needed in Queens but I'm not sure if we need this in Pike. Need to see if anything is using this code in Pike.
1752152,2018-03-29 15:20:09 UTC,"Eric, FYI we live tested this in one of our environments this morning. Success!"
1752152,2018-03-29 15:36:40 UTC,Thanks all.  We're working to push it through.
1752152,2018-03-29 21:55:56 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/557837"
1752152,2018-03-30 02:35:15 UTC,"Reviewed:  https://review.openstack.org/557837
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=307382f58d38778b480d2d030e427759a44c204b
Submitter: Zuul
Branch:    stable/queens"
1752152,2018-03-30 00:19:57 UTC,"Reviewed:  https://review.openstack.org/557508
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=20eaaee2334957eb8739ecca524a1c4aa9f246e9
Submitter: Zuul
Branch:    master"
1752152,2018-04-02 13:08:58 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1752152,2018-04-20 13:13:03 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1752152,2018-03-29 08:32:14 UTC,"@efried, patch seems to be working fine with vm deploy/delete, volume attach/delete flows"
1752152,2018-03-29 22:14:45 UTC,"I audited the stable/pike code. While https://review.openstack.org/#/c/469579/ went into pike, and is used if we actually create/update/delete volume attachments, we don't actually call any of those flows. We didn't start creating new style attachments until Queens. Some of the plumbing was added in Pike, but not actually 'turned on' in the API at that point, so we shouldn't need to backport any fixes to stable/pike."
1752152,2018-03-28 21:20:10 UTC,"@Divya, would you please try https://review.openstack.org/#/c/557508/ in your environment and let us know if it fixes the issue?"
1752152,2018-03-21 23:26:23 UTC,"Ouch, good find. https://review.openstack.org/#/c/508345/ could replace the microversion checks via cinderclient if we use the keystoneauth1 Adapter object, but that's not something we can backport to queens and pike."
1752152,2018-03-28 05:20:21 UTC,"In this specific case of getting the server version url, the url is https://<cinder ip>:9000/. As Matt mentioned above, this returns different version information and doesn't require authentication. This doesn't really have to be a secure call in my opinion (verify can be set to False)."
1752152,2018-03-28 05:05:57 UTC,"mriedem, I am using Queens and the url used is https. The request library by default does secure communication unless specified otherwise."
1752152,2018-03-21 23:49:41 UTC,"I'm also beginning to wonder how it is that if this was regressed since Pike, how is it we haven't heard more about this issue? I assume most productions clouds are using SSL."
1752152,2018-03-21 23:48:06 UTC,This is hitting the version document too:
1752152,2018-03-21 23:42:00 UTC,Getting the version document over http isn't the answer.  Let's just duplicate the cinderclient.client.get_highest_client_server_version method in nova - at least for the stable version of the fix - but using the _SESSION instead of a raw requests.get to get the version document.
1752152,2018-03-21 23:40:11 UTC,"I'm not sure why this isn't a problem in devstack in our CI environment because tls-proxy is enabled which makes the endpoints get set using https, so I don't see how this is a problem for you but not in devstack?"
1752152,2018-03-21 23:33:42 UTC,"I think we can mark this as invalid for cinderclient as there isn't anything we can backport and require with a new minimum version on stable branches for cinderclient, so nova likely has to solve this alone."
1752152,2018-03-21 23:31:15 UTC,"The alternative is on the nova side, we just construct a cinderclient Client object and use it's internal client (session) to make a request, or use a keystoneauth1 adapter to make the request. I'm not sure if all of the version negotiation checking that's happening in cinderclient is something we need to worry about, i.e. what happens in here:"
1752152,2018-03-28 20:55:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557508"
1752154,2018-02-27 19:19:06 UTC,"Sorry I'dont know how to attack multiple files, here is a tar.gz with:
lightdm.txt  lscpu.txt  lshw.txt  lspci.txt  lsusb.txt  Xorg.0.txt"
1752164,2018-02-28 01:59:04 UTC,When run in terminal error says... /bin/bash: evolution: command not found. Thunderbird is definitely set as the preferred app.
1752164,2018-03-01 18:42:15 UTC,"Solved...
GConf /desktop/gnome/url-handlers/mailto/command
Change evolution to thunderbird.
Weird that System Settings didn't set this."
1752167,2018-05-03 05:34:52 UTC,"If my memory serves me right, many of the more lighter desktop environments in Linux, such as LXDE and others, aren’t making use of your graphics card full potential by avoiding using a compositing window manager."
1752167,2018-05-03 05:37:39 UTC,To make Compton autostart upon LXDE login – create a .desktop file in your ~/.config/autostart directory (create one if not available) and copy paste the following inside it:
1752173,2018-02-28 23:55:03 UTC,*** This is an automated message ***
1752174,2018-04-05 23:00:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752183,2018-02-27 22:12:34 UTC,"There will also need to be some thought about how to deal with existing groups
- that are rudderless, that is have no admins
- that have been abandoned, that is have no members"
1752183,2018-02-27 22:16:11 UTC,Having a group with no admin/members is not necessarily a bug as a site admin can always add a user to a group as a group admin via Administration -> Groups -> Administer groups -> Manage (cog) button.
1752183,2018-02-27 22:34:07 UTC,"Robert and I discussed it in person. Since account deletion only affects personal data and not collaborative data, I'd not tie the group deletion to the account deletion as that might get messy from an institution standpoint. An institution may want to keep the data there even if there aren't any group members."
1752188,2018-03-12 00:46:44 UTC,a plan is to fix it by converting our l3 plugin to an l3 flavor.  cf. bug 1643830
1752194,2018-04-05 02:54:04 UTC,They need to be run under sudo. also the intel-gpu-tools in 14.04 shouldn't have support for an i7-7700.
1752194,2019-06-14 14:58:11 UTC,"I have exactly the same ""Couldn't map MMIO region: Operation not permitted"" problem with Ubuntu 19.04.
======================
(intel_gpu_top:23801) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23801) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23801) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:23801) intel-mmio-CRITICAL: Couldn't map MMIO region
Stack trace:
  #0 [_init+0x7b87]
  #1 [_init+0x5420]
  #2 [_init+0xe85]
  #3 [__libc_start_main+0xeb]
  #4 [_init+0x1c92]
Test (null) failed.
**** DEBUG ****
(intel_gpu_top:23801) intel-chipset-DEBUG: Test requirement passed: pci_dev
(intel_gpu_top:23801) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23801) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23801) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:23801) intel-mmio-CRITICAL: Couldn't map MMIO region
(intel_gpu_top:23801) igt-core-INFO: Stack trace:
(intel_gpu_top:23801) igt-core-INFO:   #0 [_init+0x7b87]
(intel_gpu_top:23801) igt-core-INFO:   #1 [_init+0x5420]
(intel_gpu_top:23801) igt-core-INFO:   #2 [_init+0xe85]
(intel_gpu_top:23801) igt-core-INFO:   #3 [__libc_start_main+0xeb]
(intel_gpu_top:23801) igt-core-INFO:   #4 [_init+0x1c92]
****  END  ****
FAIL (-1.000s)"
1752194,2018-11-13 18:37:38 UTC,Hitting this on 18.04 with Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz and i915 driver.
1752194,2018-05-12 01:32:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752194,2018-04-05 02:41:12 UTC,"I have exactly the same ""Couldn't map MMIO region: Operation not permitted"" problem with Ubuntu 14.04.5 with 1.3-0ubuntu2.1 build. My CPU is Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz on my ASUS VivoMini PC."
1752194,2018-04-05 04:13:45 UTC,"Yes I did run with sudo. The error message is different without sudo. I think the new 14.04.5 fixed a lot of problems with the new intel cpu. At least it fixed all my graphics card driver issue in one shot. However, how do I find out what is supported with intel-gpu-tools?"
1752194,2019-07-13 02:35:26 UTC,"I've hit this too on 18.04.
It may be related to kernel lockdown in UEFI secure boot.
https://bugs.freedesktop.org/show_bug.cgi?id=93199"
1752194,2018-04-05 04:20:25 UTC,but of course the intel-gpu-tool for trusty hasn't been updated since 2014 so likely it doesn't support i7-7700 (released in 2017) as you described. However it's the same MIMO error message I am getting. I'm hoping the same fix will be updated to the version for trusty.
1752194,2020-06-24 07:58:53 UTC,"Ubuntu 18, Intel(R) UHD Graphics 620"
1752197,2018-04-06 19:21:13 UTC,This bug was fixed in the package webkit2gtk - 2.20.0-2ubuntu1
1752197,2018-03-24 21:12:51 UTC,This issue can be fixed by switching webkit2gtk to use gstreamergl but that is blocked on LP: #1753581 .
1752197,2018-04-06 19:56:33 UTC,"I play a movie on youtube from the start without trouble, but it still in slowness and not normal"
1752197,2018-03-06 12:58:29 UTC,I'm closing the epiphany task since this is easy to reproduce in the GNOME help app (yelp) too.
1752203,2018-03-01 09:17:56 UTC,"This seems to be another case of it:
  http://10.125.0.203:8080/job/RunUnittests-race-amd64/147/console"
1752205,2018-02-28 01:09:09 UTC,"It would be great if this token could be passed in via the URL, example: consul://<email address hidden>"
1752205,2019-03-28 23:54:56 UTC,I've tried adding this into the Consul driver. It seems to be a bit deeper/harder than i expected.
1752205,2020-04-08 04:35:33 UTC,How can I help get this done? Can anyone comment on Nick's question from a year ago?
1752205,2020-04-27 02:44:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/723300"
1752205,2020-04-28 20:28:44 UTC,"Change abandoned by punkrokk (<email address hidden>) on branch: master
Review: https://review.opendev.org/723300
Reason: Abandoning in favor of: https://review.opendev.org/718488"
1752205,2020-05-15 10:01:52 UTC,"Reviewed:  https://review.opendev.org/718488
Committed: https://git.openstack.org/cgit/openstack/tooz/commit/?id=08b2d93226071c74ce8bf85265429511e417af73
Submitter: Zuul
Branch:    master"
1752207,2019-09-09 13:53:40 UTC,"Any chance the fix for this can be cherry-picked in bionic?
https://github.com/antirez/redis/commit/afc4b36c1026a4fab0e6c50af09c6bd18adc17d5"
1752207,2018-04-13 12:59:48 UTC,Related to ipv6 (disabled on the server)
1752207,2018-04-03 09:46:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752207,2018-08-08 17:34:52 UTC,This bug also affects redis-server 5:4.0.9-1 under Ubuntu 18.04.1.
1752207,2018-02-28 01:22:37 UTC,Moar:
1752207,2018-02-28 01:19:48 UTC,More info:
1752207,2018-03-01 00:35:01 UTC,I had ipv6 disabled on my network interface.  Reenabling it allowed redis to start up fine.
1752208,2018-03-01 08:52:46 UTC,I don't get the problem. Try keeping the print screen key pressed for a longer time (about 1 second).
1752222,2018-05-31 23:14:50 UTC,This is probably similar to LP: #1721200
1752222,2018-06-01 07:46:08 UTC,Is metadata.yaml in the built charm valid UTF-8? The yaml library is failing to parse it.
1752222,2018-06-01 07:49:18 UTC,"(charmhelpers.core.hookenv.principal_unit() is falling back to compatibility code, attempting to to discover the principal unit name by looking at the metadata.yaml of the other cohosted units. So the metadata.yaml triggering this could be the primary charm's or another subordinate)."
1752222,2020-03-04 02:00:57 UTC,"This needs some further testing to get a reliable reproducer, I suspect it's only an issue when there's non-ascii chars in the data passed over the relation between the subordinate and principal."
1752224,2021-01-12 08:12:19 UTC,"Got hit by this bug today, except the data in the DB was an FQDN, and the charm wanted to insert an IP address. Worked around by updating the rows manually with the IP address."
1752224,2021-02-25 16:17:41 UTC,"Adding notes on how to access the grafana DB:
cd /var/lib/grafana/
sudo apt install sqlite3 -y
sqlite3 grafana.db
SQLite version 3.22.0 2018-01-22 18:45:57
Enter "".help"" for usage hints.
sqlite> .tables
alert                     dashboard_tag             server_lock
alert_notification        dashboard_version         session
alert_notification_state  data_source               short_url
alert_rule_tag            login_attempt             star
annotation                migration_log             tag
annotation_tag            org                       team
api_key                   org_user                  team_member
cache_data                playlist                  temp_user
dashboard                 playlist_item             test_data
dashboard_acl             plugin_setting            user
dashboard_provisioning    preferences               user_auth
dashboard_snapshot        quota                     user_auth_token
sqlite> select * from data_source;
.... table output"
1752224,2018-09-18 06:16:23 UTC,"There is indeed a duplicate row - what I found is that the address for prometheus had changed from IP address to name, and because the entire row doesn't match the charm tries to add a fresh row with the same id."
1752225,2018-02-28 03:18:33 UTC,The renew endpoint documentation: https://www.consul.io/api/session.html#renew-session
1752225,2019-03-28 23:29:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648557"
1752225,2020-02-13 14:50:09 UTC,Any reason this hasn't been merged? I need this fix myself.
1752225,2020-02-13 16:08:02 UTC,"Change abandoned by Nick Maludy (<email address hidden>) on branch: master
Review: https://review.opendev.org/648557
Reason: Messed up rebase"
1752225,2020-02-13 16:12:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/707681"
1752225,2020-02-13 19:05:52 UTC,"FYI, the build is passing now!"
1752225,2020-03-04 03:02:21 UTC,"Reviewed:  https://review.opendev.org/707681
Committed: https://git.openstack.org/cgit/openstack/tooz/commit/?id=6e750b6921c42f3c2ffed2e135be4d9c65e96f36
Submitter: Zuul
Branch:    master"
1752225,2020-03-19 10:10:39 UTC,This issue was fixed in the openstack/tooz 2.2.0 release.
1752234,2018-03-02 16:51:16 UTC,"As a workaround for the other issue mentioned, you can save it in a template file, then you can have different templates for different projects."
1752234,2020-03-12 17:38:29 UTC,Closing this in favor of https://gitlab.com/inkscape/inkscape/-/issues/188 as part of Inkscape's bug migration.
1752239,2020-01-20 03:09:51 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1752239,2020-03-20 04:17:25 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1752240,2019-06-10 04:17:24 UTC,[Expired for kolla because there has been no activity for 60 days.]
1752240,2019-04-10 10:17:41 UTC,Is this still an issue?
1752247,2018-03-29 15:42:21 UTC,What about if you pass:
1752251,2018-07-18 10:21:03 UTC,I have a real mce hardware problem and can't view it without such tools! Is there an alternate to mcelog ?
1752251,2020-02-05 17:13:59 UTC,The removal of the package is quite unfortunate since rasdaemon is still missing the email notification feature.
1752251,2019-05-15 08:39:38 UTC,The mcelog package functionality has been replaced by rasdaemon. Best to focus on rasdaemon.
1752251,2019-02-26 10:12:42 UTC,"Debian removed the package because they disabled kernel support.
Ubuntu removed the package because Debian did, but kept kernel support. Strange."
1752251,2019-02-03 19:25:12 UTC,"As long as there is no working alternative I would like to have mcelog back.
Some tool to get hardware error messages is rather important, I think."
1752251,2018-07-25 05:14:26 UTC,"@#9, Supposedly rasdaemon could handle MCEs on bionic+. Have not yet witnessed it working though, even on hardware that had dozen reports/year shown with mcelog."
1752251,2018-05-30 16:07:02 UTC,"Also if there's use in having this package around it might be worth considering whether it could be packaged as a snap, which doesn't require going through the sru process."
1752251,2018-05-30 16:05:59 UTC,"Yes, since the Ubuntu kernel still has the mcelog interface endless, the mcelog package could be used in Ubuntu.  However, the interface is marked deprecated and the package was subsequently removed from Debian and then Ubuntu.  I don't see a reason to reintroduce this package in sru, instead of users migrating to non-deprecated interfaces."
1752251,2018-05-30 12:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1752251,2018-05-30 11:36:31 UTC,Or maybe MCELOG should be disabled in the Ubuntu kernel config.
1752251,2018-05-30 09:44:11 UTC,"As Vinson said, Ubuntu kernels support MCE and mcelog source builds/works on 18.04."
1752251,2018-05-09 01:37:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752251,2018-02-28 21:56:38 UTC,Ubuntu 18.04 bionic kernel 4.15.0-10 enables support for mcelog.
1752251,2018-02-28 17:03:46 UTC,Thanks for reporting.
1752269,2018-10-15 13:17:53 UTC,"primary error is no ""com.ubuntu.apport.apport-gtk-root"", the second error came in sepperate pop-up for ""linux-image-extra-4.13.0.40~16.04.1"". This indicates bad support for an AMD 7tr gen processor on my DELL computer."
1752269,2018-06-22 12:59:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752277,2018-03-02 11:01:34 UTC,"I checked the python-swiftclient code; it must be an obscure circumstance where that happens. By default exceptions are either raised or a tuple is returned, and I wasn't able to spot a situation where this won't happen."
1752281,2018-03-01 10:08:44 UTC,"confirmed on Windows 10, Inkscape 0.92+devel (9d6b0e8, 2018-02-18)"
1752281,2018-03-02 12:39:22 UTC,a somewhat better result can be obtained by editing the svg file to remove the illegal transform. In the attached svg file I have edited the transform for the object id = linearGradient9457 to try to make it invertible. This produces a better output when saved as pdf.
1752281,2020-01-08 19:44:08 UTC,This issue has been reportet to Inkscape's new Bugtracker on Gitlab. https://gitlab.com/inkscape/inbox/issues/748
1752283,2018-02-28 10:00:14 UTC,https://pastebin.ubuntu.com/p/BMC3jSsc4d/
1752283,2018-02-28 12:32:51 UTC,Fixed by @james-page in https://bazaar.launchpad.net/~ost-maintainers/openstack-mojo-specs/openstack-mojo-specs-1802/revision/350
1752289,2018-03-07 23:30:21 UTC,This issue was fixed in the openstack/nova 17.0.1 release.
1752289,2018-03-07 19:23:33 UTC,"Reviewed:  https://review.openstack.org/548572
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3a3b0f09db318faf1a1ea711a73bb365cab8b233
Submitter: Zuul
Branch:    master"
1752289,2018-03-07 22:11:52 UTC,"Reviewed:  https://review.openstack.org/550259
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c50ffc9dc185d8aadb1f3addba4085cb8bfbf4d3
Submitter: Zuul
Branch:    stable/queens"
1752289,2018-03-06 21:18:03 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550259"
1752289,2018-04-20 13:14:03 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1752289,2018-02-28 13:29:32 UTC,This is likely related to https://github.com/openstack/nova/commit/6cde77ebbab85bc8ccd2ab7ad977b1d4af4a13fa if it's a regression in Queens.
1752289,2018-02-28 11:58:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548572"
1752289,2018-02-28 13:53:33 UTC,"The issue is the 'url' option is missing, so nova uses the ksa adapter code to lookup the entry in the service catalog, but there is no 'network' entry in the context."
1752290,2018-09-25 05:13:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604969"
1752290,2018-11-15 02:39:59 UTC,"Change abandoned by Kim Bao Long (<email address hidden>) on branch: master
Review: https://review.openstack.org/604969
Reason: Thanks yushiro!
This patch is not necessary any more due to our design has changed."
1752290,2018-10-23 07:39:35 UTC,"Reviewed:  https://review.openstack.org/564668
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=50c75e9e51a053c89a585c55a586ed3d931d82f1
Submitter: Zuul
Branch:    master"
1752290,2018-10-23 07:07:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612612"
1752290,2018-10-22 23:16:19 UTC,"Reviewed:  https://review.openstack.org/577086
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6352b944a4dfa209e11f1981d9204aa89b9f157d
Submitter: Zuul
Branch:    master"
1752290,2018-09-25 09:54:32 UTC,"Change abandoned by Kim Bao Long (<email address hidden>) on branch: master
Review: https://review.openstack.org/605025"
1752290,2018-09-25 09:47:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605025"
1752290,2018-09-20 09:17:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604023"
1752290,2018-03-19 08:21:05 UTC,"Thanks a lot, Miguel!!!"
1752290,2018-08-31 07:39:47 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/577086
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1752290,2018-06-21 07:52:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577086"
1752290,2018-04-27 04:20:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564668"
1752290,2018-08-31 07:42:00 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/564668
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1752290,2018-03-15 23:21:43 UTC,"We discussed this RFE during the Dublin PTG  and we agreed to implement it. Please see the ""API topics"" section in the PTG summary: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128183.html. As a consequence, moving this RFE to approved status. Please go ahead with the implementation"
1752290,2018-03-01 09:27:45 UTC,Set status to Confirmed for corresponding to the tag set by amotoki :)
1752298,2018-02-28 11:04:31 UTC,"Also, ""RefDesStringCompare"" in common/strings.cpp"
1752298,2018-02-28 13:33:04 UTC,eeschema/fields_editor_table_model.cpp is now gone.
1752298,2018-02-28 15:00:50 UTC,"You will be delighted to hear that eeschema/pin_number.cpp does that for volts, to support pin names specifying voltages."
1752298,2019-07-01 15:07:13 UTC,"FYI, you may find http://www.davekoelle.com/alphanum.html useful if it's not known already."
1752299,2018-03-30 19:54:28 UTC,Same issue with applications listed in the categories. Snap packages are not listed there.
1752299,2018-03-08 22:18:34 UTC,Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-software/issues/314
1752299,2018-03-09 10:47:44 UTC,"We don't currently have this data from the snap store, but we should add it."
1752299,2018-03-09 11:03:43 UTC,Forum post: https://forum.snapcraft.io/t/no-method-to-show-recently-updated-snaps/4409
1752299,2018-03-09 11:05:38 UTC,Updated link:  https://forum.snapcraft.io/t/no-method-to-show-recently-updated-snaps/4409
1752300,2018-10-14 19:48:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752304,2018-02-28 13:15:52 UTC,"Hi Manuel,"
1752304,2018-02-28 14:35:14 UTC,"Yes, exactly what I am mentioning in my initial description (have a look at both vnffgd). I think that  suddenly changing an API without granting some ""deprecation period"" is against the openstack policies, so that's why I consider this as a bug. Unfortunately, I currently don't have the time to do this but I'd say it is good that it is kept in the backlog of bugs"
1752304,2018-03-01 18:00:52 UTC,Hi Manuel. I will help you with this and raise this question with the Tacker team. Will keep you inform.
1752305,2018-02-28 12:40:35 UTC,"Going over the deeper LOG messages, I'm concerned that this is actually something significant like we're running >1 API Server under certain circumstances."
1752305,2018-02-28 13:17:01 UTC,"It seems very strange that cmd/jujud/agent/agenttest.go is ""priming"" the api host ports with:
api host ports primed []network.HostPort{localhost:42249}"
1752305,2019-09-09 05:48:57 UTC,"I can no longer reproduce this failure locally under stress after hundreds of runs.
It seems that we have fixed the cause of this failure since we have last looked at this report. We have both in api ports area as well as in leases, including legacy ones."
1752308,2018-03-29 18:21:05 UTC,"Hello Dr., or anyone else affected,"
1752308,2018-03-22 09:25:13 UTC,This bug was fixed in the package ceph - 12.2.4-0ubuntu1
1752313,2018-02-28 14:27:04 UTC,Thanks for your report!
1752313,2018-02-28 15:32:24 UTC,Reported upstream.
1752313,2018-03-02 23:14:18 UTC,"It looks like it happens with apps that have ""X-Ubuntu-Gettext-Domain"" instead of having the translated strings directly in the desktop file, so it may be some bug in gettext or another component that Ubuntu uses."
1752313,2018-03-03 18:28:27 UTC,I saw the upstream response. So this bug will probably keep being open for now.
1752322,2020-02-16 09:57:56 UTC,"Can someone reproduce this in buster, please?"
1752322,2020-12-13 05:34:49 UTC,"Have you tried changing your keyboard layout? Since the Raspberry Pi was made in Britain, the default keyboard is also British. This throws off many American keyboard layouts. When trying to configure my Wifi I ran into the issue as well, but with @ signs. I had to reconfigure the keyboard settings, but since then have had no issues with special characters. I was using Buster Lite, and it has been functional since. I do not know if this is the same as your issue, but it might be worth taking a look at."
1752324,2018-03-05 23:43:12 UTC,RFC 7230 deprecates folded headers; see section 3.2.4.
1752330,2018-07-23 17:39:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584981"
1752330,2018-05-17 12:53:52 UTC,related bug https://bugzilla.redhat.com/show_bug.cgi?id=1578793
1752330,2018-05-17 12:51:52 UTC,There is enough stuff happening with permissions on upgrades that this needs revisiting. I've started looking at baremetal->container converstion tool for supporting processes. that can be run as part of the upgrade process.
1752330,2018-03-01 16:49:59 UTC,"Sidenote: be careful with permissions. A misstep can ""wreck"" some of the network namespaces and requires a reboot to recover."
1752330,2018-03-01 16:48:56 UTC,FWIW I think the ideal would be to leave the spawned processes alone since that avoids breaking the dataplane. Respawning the dnsmasq process would not be as bad as long as the previous one is shutdown.
1752330,2019-05-02 16:23:39 UTC,"Change abandoned by Brent Eagles (<email address hidden>) on branch: master
Review: https://review.opendev.org/584981"
1752330,2020-11-04 14:31:52 UTC,In practice this has never presented an issue so I'm closing it.
1752334,2019-02-28 17:04:50 UTC,Working branch at user/stompro/lp1752334_badcontact_use_additional_note
1752334,2020-01-23 00:27:11 UTC,"I just eyeballed this, and it looks good from my initial observation.  It also looks like it would be a really good candidate for a live test, perhaps using this live test as an example: https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/src/perlmods/live_t/zz-lp1779467-mark-item-discard.t"
1752347,2018-03-28 13:35:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557337"
1752350,2018-03-12 14:56:13 UTC,thanks Joseph
1752350,2018-03-19 07:09:34 UTC,add grub file
1752350,2018-03-19 07:07:56 UTC,"just comment, we are also meet this issue during testing Xen on Ubuntu18.04 Beta1 on all of platform:
1. install Ubuntu 18.04
2. reboot
3. When I try to boot my virtual machine host using a xenial based Xen system (Xen 4.6, linux generic 4.4.0) it crashes immediately.
Expect Result:
on step3 we expect enter into system with Xen successfully.
Actual Result:
On step3, we failed enter into system with Xen.
Note: No matter boot by UEFI or Legacy mode, above issue reproduced."
1752350,2018-03-12 13:52:55 UTC,"The 4.15.5 updates are in the Ubuntu 4.15.0-12 kernel, which is scheduled for release on April 2nd, 2018."
1752350,2018-03-10 12:33:26 UTC,"@jsalisbury, when do you think it will be safe to `apt-mark unhold` the kernel?"
1752350,2018-03-07 09:54:12 UTC,The commit that fixes this bug is in upstream stable 4.15.5.  These updates have  been applied to Bionic master-next.
1752350,2018-03-06 17:47:34 UTC,"@jsalibury, your kernel fixed my domUs =)"
1752350,2018-03-06 16:16:22 UTC,I wanted to mention that installing v4.16-rc4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/ solved the problem for me.
1752350,2018-03-06 16:27:41 UTC,"@jsalibury, the Kernel you provided does successfully boot on Xen."
1752350,2018-03-06 07:29:54 UTC,"@Johanns, does my test kernel fail for you as well?"
1752350,2018-03-05 23:39:52 UTC,"Hi Joseph, I removed 4.15.0.11.12 and installed yours."
1752350,2018-03-05 23:05:31 UTC,"@jsalisbury, I already have 4.15.0.11.12 installed... can you update your test kernel please?"
1752350,2018-03-05 09:30:36 UTC,"I built a test kernel with commit 4f277295e54c5b7340e48efea3fc5cc21a2872b7.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752350"
1752350,2018-02-28 15:03:32 UTC,"I can not run apport-collect on the affected system, since the kernel crashes immediately."
1752350,2018-02-28 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1752350,2018-03-06 12:12:22 UTC,I think I will find some time later today to try it out.
1752356,2020-08-20 20:16:43 UTC,Some issues came up testing this.  Another branch with the work is here:
1752356,2020-08-27 19:23:52 UTC,"Thank you for the improvement, Terran.  I tested each of the 4 error messages you can get when trying to check out a patron on the block list.  They all look good to me.  I consent to signing off to this with my name Mike Risher (<email address hidden>)"
1752356,2020-08-20 22:45:10 UTC,"Thanks, Mike and Bill. I found in testing that the new message had been applied to accounts marked Barred rather than accounts marked Expired, so my sign off is here with that correction. I've also taken the liberty of adding similar wording (as per Bill's commit) to the other reasons ""WHY"" accounts can appear on the block list."
1752356,2020-08-10 18:58:44 UTC,"I took my work and Bill's, rebased it, tested it, and put it on this branch:"
1752356,2018-02-28 15:40:04 UTC,Confirmed on 3.0.3 I also agree that displaying the last download date is a very helpful troubleshooting tool (and training tool).
1752356,2019-07-03 18:41:35 UTC,"Thanks, All.  I have pushed a branch with a sign off for Mike's patch, plus an additional commit."
1752356,2019-07-01 21:25:43 UTC,"I've pushed a branch here
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mrisher/lp1752356-offline-blocklist-date-addition"
1752356,2020-08-07 20:13:25 UTC,Mike / Bill - I am hitting some errors when I apply this to a test server running current master. Could you please rebase?
1752367,2018-04-23 15:14:40 UTC,Adding a note from the duplicate bug that stat cat entries also cannot be deleted.
1752367,2021-02-12 01:15:42 UTC,"Stat cats can be edited and deleted in the proposed angular port of the stat cat interface; however, I'm not sure the end result is the desired behaviour."
1752376,2018-03-01 08:25:00 UTC,apport information
1752376,2018-03-01 08:25:03 UTC,apport information
1752376,2018-03-01 08:25:01 UTC,apport information
1752376,2018-03-01 08:25:04 UTC,apport information
1752376,2018-03-01 08:24:57 UTC,apport information
1752376,2018-03-06 11:53:16 UTC,@Sorfrost: The acpi tables attached are for some reason not complete and cannot be  disassembled.
1752376,2018-03-06 16:37:04 UTC,Only seems to occur when the PC has been connected to AC charger for a very long time. Unfortunately I cannot reproduce that situation at the moment.
1752376,2018-03-01 08:24:58 UTC,apport information
1752376,2018-03-05 09:49:26 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1752376,2018-03-01 08:24:56 UTC,apport information
1752376,2018-03-01 08:24:52 UTC,apport information
1752376,2018-03-01 08:24:54 UTC,apport information
1752376,2018-03-01 08:24:55 UTC,apport information
1752376,2018-03-01 08:24:52 UTC,apport information
1752376,2018-03-01 08:24:51 UTC,apport information
1752376,2018-03-01 08:24:50 UTC,apport information
1752376,2018-03-01 08:24:49 UTC,apport information
1752376,2018-03-01 08:24:47 UTC,"ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu     1654 F.... pulseaudio
CasperVersion: 1.387
DistroRelease: Ubuntu 17.10
LiveMediaBuild: Ubuntu 17.10 ""Artful Aardvark"" - Release amd64 (20180105.1)
MachineType: Dell Inc. Vostro 5568
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-21-generic N/A
 linux-backports-modules-4.13.0-21-generic  N/A
 linux-firmware                             1.169.1
Tags:  artful
Uname: Linux 4.13.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:"
1752376,2018-02-28 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1752377,2018-02-28 20:28:35 UTC,"Given this issue occurs after a compiz update, moving to compiz."
1752379,2019-08-20 15:59:59 UTC,"I'm utterly confused about what the support policy actually is .. is ""Supported:"" in universe still updated/meaningful? Apparently I have 123 unsupported packages on bionic, including things like apcupsd, iftop, fatrace, distcc, systemd-container ..?"
1752379,2019-08-26 15:13:42 UTC,"Steve: That's more of a support question (https://ubuntu.com/support - see also the references to community support to the bottom). However, other Ubuntu users wondering about this same question may end up on this bug report, so here's a quick reply:"
1752380,2018-02-28 18:17:33 UTC,"For third-party installs, we probably don't have the support status information, so we probably should say something like ""Support unknown (Third party package)"" or something similar."
1752403,2019-03-18 02:43:05 UTC,"Hi, is this still an issue for you with the latest Inkscape version?"
1752403,2019-06-10 07:53:53 UTC,"Closing as there has been no response for 60 days. If you still have a similar issue, please file a report on our new bug tracker: https://inkscape.org/report. Thank you!"
1752411,2018-08-24 05:33:36 UTC,"Thanks Trent for the extra verification.
Tests also look good so far, but currently since a lot got uploaded due to feature freeze some tests take a while.
We should have that in cosmic soon and then can pick the same for Bionic."
1752411,2018-08-24 13:31:20 UTC,"> RE -W/w in `host`
, correct -- even with timeout set, it blocks forever (I tested this several days ago in the dup'd ticket iirc)
"
1752411,2018-08-24 05:13:25 UTC,"I agree with the sentiment that 5 seconds feels too long, however as a workaround I decided I would just copy the existing timeout. I certainly would not want to make it longer since this is in the critical boot path."
1752411,2018-08-24 06:30:38 UTC,"> When host call fails (even with timeout), it returns ""1"" claiming ""dns_has_local()=true"".
"
1752411,2018-08-23 15:38:14 UTC,"Hi fermulator,
I was wondering vice versa if 5 seconds would be too short actually.
Yes the good cases will return in sub-second, but it is the bad cases we want to fix here.
Having a bit more time to recover if it can doesn't seem too bad to me."
1752411,2018-08-21 06:43:36 UTC,"I agree strongswan/openconnect (and maybe more) are affected by the symptom, while the bug lies in bind9-host/avahi packages at least according to current debugging."
1752411,2018-08-23 14:53:11 UTC,"PS: I've been running with a hacked /usr/lib/avahi/avahi-daemon-check-dns.sh for a few days with this code:
```
  OUT=`LC_ALL=C /usr/bin/timeout 2 host -t soa local. 2>&1`
```
, works like a charm"
1752411,2018-08-23 14:51:51 UTC,"Are we sure timeout of 5 seconds is appropriate? (it FEELS too long)
My intuition says that if a DNS query takes longer than 1 second it took too long ..."
1752411,2018-08-22 09:53:00 UTC,"I've had some minor cleanups on the changelog, but other than that I think the most recent submission is good."
1752411,2018-08-21 14:49:11 UTC,"Request sponsorship of this upload for cosmic and then SRU to bionic
 - New debdiff uploaded for both bionic and cosmic
 - Fixed the SRU version for bionic
 - Added a comment about the workaround to the script
 - Updated bug description with SRU template"
1752411,2018-08-24 15:19:23 UTC,"I've been trying to figure out how to test this with dig instead, and I think I found something.  If you have a normal /etc/resolv.conf then you see this:
===
$ dig -t soa local.; echo $?"
1752411,2018-08-23 15:07:01 UTC,We should also consider:
1752411,2018-08-29 09:25:03 UTC,The suggested mitigation is in bionic-unapproved for the consideration of the SRU team.
1752411,2018-10-16 19:05:58 UTC,"In https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1797926 looks like the host command, that doesn't timeout and is the subject of this bug here, crashed."
1752411,2018-08-30 10:04:54 UTC,"also attching a gdb full bt, which shows that epoll_wait is called it a timeout value of ""-1"" (infinite) in thread #4."
1752411,2018-08-30 10:11:14 UTC,I found a source reference here: https://github.com/fanf2/bind-9/blob/master/lib/isc/unix/socket.c#L4127
1752411,2018-08-30 19:09:59 UTC,"Hello Liam, or anyone else affected,"
1752411,2018-08-31 06:28:20 UTC,@Trent - since you had the most reproducible setup could you take a look at verifying also the Bionic upload?
1752411,2018-08-31 07:17:19 UTC,Reported upstream as https://gitlab.isc.org/isc-projects/bind9/issues/520
1752411,2018-08-31 09:11:39 UTC,"I tried the numerous suggested fixes and the all worked for me including uninstalling ""avahi-daemon"". That last one resolved my problem so I can't test the latest fix."
1752411,2018-08-31 09:41:11 UTC,Hi Liam!
1752411,2018-09-03 09:22:17 UTC,"Confirmed the fix works on my affected system, after upgrade to 0.7-3.1ubuntu1.1 from bionic-proposed and a system reboot the boot works (relatively) quickly as expected and doesn't get stuck."
1752411,2018-09-06 02:34:30 UTC,"Package: avahi-daemon
Version: 0.7-3.1ubuntu1.1"
1752411,2018-09-06 07:48:36 UTC,This bug was fixed in the package avahi - 0.7-3.1ubuntu1.1
1752411,2018-09-06 07:48:47 UTC,"The verification of the Stable Release Update for avahi has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1752411,2018-08-20 16:11:23 UTC,"(this is currently in the ""openconnect"" path despite marked as ""invalid"" against that package, bug was submitted originally to that project -- can we move to avahi?)"
1752411,2018-08-29 09:29:43 UTC,"@Erich - infinite hangs are usually due to the kernel somewhere, while suggesting dig was a good idea just to try I wonder if we would have to find what ""host"" actually hangs on to be sure that ""dig"" in turn will not some day block on just the same."
1752411,2018-08-20 16:04:21 UTC,(btw; while we're fixing that script ... fix/change backtics to POSIX compliant sub-shell'ing $() ?
1752411,2018-08-30 09:47:01 UTC,"in fact, there are two host commands running, both show wchan=sigsuspend, perf shows nothing and strace shows commands is suspended. new strace is attached."
1752411,2018-08-20 15:46:11 UTC,"Definitely a duplicate. @paelzer was suggesting in bug 1786261 that dig be used instead, do you guys know if that's a reasonable possibility?"
1752411,2018-03-21 08:33:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752411,2018-04-03 19:18:30 UTC,I'm also affected. Looking at the process list (ps ax) I found:
1752411,2018-04-03 19:31:28 UTC,"in fact, the ""host"" command is hanging, sorry."
1752411,2018-04-03 19:55:06 UTC,Nice work Marc.
1752411,2018-04-04 10:59:46 UTC,"If you define ""infinite"" as longer than 10 seconds - yes. Something is quite bogus here."
1752411,2018-04-09 06:37:39 UTC,I ran into this myself today after upgrading a machine to bionic..
1752411,2018-04-09 06:39:03 UTC,No VPN in use.. this is probably a bug equally in bind9-host and avahi-daemon
1752411,2018-04-09 08:34:23 UTC,"I did some testing using strace and looking at backtraces of why ""host"" is stuck, and it's not immediately clear to me why it's getting stuck.  Will need to look more in depth into it tracing it's actual execution - it's multi threaded and using poll so not super straight forward from the trace for someone unfamiliar with the code-base."
1752411,2018-04-09 12:55:13 UTC,"Can you try running ""host"" with -d in the scenario where it is hanging?"
1752411,2018-04-09 13:42:35 UTC,"My system was upgraded, so maybe a leftover. So I uninstalled ifupdown and upstart. Problem still persists :-(
I will attach a ltrace -Sf host output - maybe it helps..."
1752411,2018-08-20 16:02:57 UTC,Notes;
1752411,2018-04-16 03:43:49 UTC,With host -d I simply get
1752411,2018-04-04 07:04:48 UTC,The default timeout for the 'host' command is 10 seconds.  Is it taking longer than that?
1752411,2018-04-19 14:44:55 UTC,Some troubleshooting I did with Trent today showed:
1752411,2018-04-18 02:56:01 UTC,There is a new bind9 upload to bionic-proposed (9.11.3+dfsg-1ubuntu1)
1752411,2018-08-20 14:54:24 UTC,"FYI bug 1786261 could be another symptoms of this, reporters there will take a look and might add another affected package to this."
1752411,2018-08-17 05:29:48 UTC,"Unsubscribing sponsors for now, awaiting the fixes Robie commented about."
1752411,2018-08-03 13:06:57 UTC,Thank you for working on this. I agree with your approach. The debdiff looks good.
1752411,2018-07-19 19:36:16 UTC,"I've run into this problem as well after upgrading my Ubuntu 17.10 installation (upgraded from 17.04) to Ubuntu 18.04 last week. My VPN script calling ""openconnect"" hang and no packets got forwarded. My first workaround was however to connect using nm-applet instead which worked fine (available via package network-manager-openconnect-gnome)."
1752411,2018-08-01 03:28:47 UTC,"Hoping to get attention to this again. Since 18.04.1 is out now, more and more users are likely to hit this issue as more users will be upgrading. This issue applies equally to desktop and server scenarios."
1752411,2018-05-22 23:53:07 UTC,Sponsors: Can we get this debdiff uploaded now? We've had a few more reports and I'd like to get this workaround in place.
1752411,2018-05-07 17:06:58 UTC,"It should probably also check for 127.0.0.53, not just 127.0.0.1"
1752411,2018-05-06 09:09:27 UTC,Please also see https://bugs.debian.org/898038
1752411,2018-04-20 11:59:57 UTC,"I think that time is past, we were in beta freeze in the past week, and are in final freeze now. Unless there is a clear test case showing under which conditions this happens and how widespread it is, it's probably best to start thinking in SRU terms."
1752411,2018-04-20 08:04:14 UTC,"I'd still like to get the upload debdiff for 'timeout' that I prepared uploaded.  Even if we manage to debug the bind9-host issue, it will still be useful to have the timeout command there as a backup.  Not long before we run out of time for bionic release."
1752411,2018-07-10 12:43:12 UTC,"I was hit by this exact problem (update to Ubuntu 18.04), the host command would hang and adding timeout works around the issue.  Please put the temporary fix in so others are not affected."
1752417,2020-10-02 16:21:08 UTC,"This was filed as an FFe back in 2018, and I don't see that the Desktop Team has acked the other additions to the defaut seed.  Unsubscribing ubuntu-release."
1752417,2018-04-06 15:45:30 UTC,"Ubuntu Desktop and Ubuntu Security teams are in agreement that it would be worth adding to the default installation, that's a new feature though so needs ubuntu-release to ack the addition, turning the bug to a ffe and subscribing them for review"
1752417,2019-05-09 23:04:17 UTC,network-manager-openvpn-gnome is now included by default.  Assigning to Desktop Team for evaluation of the other packages.
1752417,2018-04-30 15:30:51 UTC,"Apicultor, comment #10 was not intended as a solution. It is just pointing out an existing GUI way to install and uninstall VPN plugins."
1752417,2018-04-30 14:50:12 UTC,"In reply to #10, if you think that should be what's required on a new install to get something other than PPTP, then I have lost all hope for Ubuntu on the desktop."
1752417,2018-04-30 13:36:59 UTC,"By the way, there is a GUI way to install VPN plugins. It's surprisingly hidden though."
1752417,2018-04-06 14:33:10 UTC,Thank you for filing this bug. I agree that it's worth asking the desktop team to consider the default set of VPN plugins available by default from time to time.
1752417,2018-03-26 08:14:00 UTC,"As it stands, Ubuntu supports deprecated-and-insecure PPTP connections out of the box even though most other major OS vendors have actually removed support for such connections entirely."
1752417,2018-04-05 08:31:46 UTC,"Private Internet Access is a bit of a Trojan horse, but I'm glad you agree the suite of VPN types supported out of the box desperately needs to be brought up to date."
1752417,2018-04-05 08:13:48 UTC,I'd concur and suggest that as so many people use openvpn for 'Private Internet Access' that would be a far more appropriate out-of-the-box VPN add-on to ship.
1752417,2018-04-05 08:07:28 UTC,It looks like this seed is affected by virtue of including only network-manager-pptp-gnome:
1752417,2018-03-26 10:31:25 UTC,"@seth-arnold: This bug was filed against 18.04 prerelease. The only option provided to me by Bionic is PPTP, which is insecure and its use is dangerous."
1752417,2018-03-15 00:22:05 UTC,"Hello Apicultor,"
1752417,2018-04-05 23:21:31 UTC,"Desktop team, what do you think, can we add network-manager-openvpn-gnome to the seeds to give users a tolerable VPN choice?"
1752424,2018-03-25 18:46:52 UTC,Not critical for 5.0.
1752424,2018-03-21 13:10:43 UTC,"@Jon, my work computer has w7 so I can help test patches.  I'm not
terribly familiar with the tool framework event handling so it could
take me a while to figure this out.  Although this wont be the case for
for much longer.  My new computer is in the process of being configured
and I will have to give this one up in the next couple of weeks so I
wont have access to a w7 machine after that."
1752424,2018-03-24 23:47:56 UTC,"This event is handled by WX_VIEW_CONTROLS::onWheel()
It would be interesting to know if the GAL canvas thinks it has focus and if you get wxEVT_LEAVE_WINDOW events"
1752424,2018-03-09 18:42:40 UTC,"I tried also different computer with Windows 7 and saw the same behavior (wheel active outside canvas).
On another computer with Windows 10 it behaved correctly. maybe it is Windows 7 specific thing."
1752424,2018-03-21 01:18:09 UTC,@Wayne are you able to debug at all?  I don't have access to Windows 7 for testing.
1752424,2018-03-09 02:16:08 UTC,"Hmm.  Can't reproduce on Linux or Windows 10, using debug builds or the latest official nightly (0bdae22af).  Can anyone else reproduce / figure out why it doesn't happen for me?"
1752424,2018-03-05 15:39:31 UTC,"This happens in the modern canvas for both the board and footprint editors, the legacy canvas it behaves as expected."
1752424,2018-03-09 03:07:13 UTC,Cannot reproduce on Mac either.
1752429,2018-02-28 21:34:02 UTC,"Video link:
https://www.youtube.com/watch?v=UW_jeTHbU90&feature=youtu.be"
1752429,2020-04-23 17:33:20 UTC,Closing because INVALID.
1752437,2018-11-19 17:09:30 UTC,"(In reply to Marc from comment #79)

> Created attachment 279541 [details]
> Output of dmesg after booting kernel 4.19.2 with new patch v2 (touchscreen
> works)
>
> Congratulations, this work!
"
1752437,2018-11-28 22:33:22 UTC,"I was able to test the latest patch from Hans on Arch Linux with 4.19.4-arch1 on my HP M6-AR004DX AMD FX-9800p laptop, and can confirm that the ELAN0732 touchscreen finally works!  No need for the ACPI/DSDT edits.  No more GPIO errors in journalctl, and the device was detected and installed with hid_multitouch."
1752437,2018-11-27 19:27:11 UTC,"(In reply to Addie Morrison from comment #96)

> Is anyone else seeing the issue where the touchscreen/pen don't work when
> the computer is first powered on (needs to be rebooted at least once)? If
> so, was this supposed to be fixed by this or should that be a separate bug
> report?
"
1752437,2018-11-27 19:14:26 UTC,"Is anyone else seeing the issue where the touchscreen/pen don't work when the computer is first powered on (needs to be rebooted at least once)? If so, was this supposed to be fixed by this or should that be a separate bug report?"
1752437,2018-11-27 04:43:15 UTC,"HP envy x360 13-ag0018au with Ryzen 7 here, the touchscreen issue is resolved with BIOS F.21.Rev.A and standard fedora kernel-4.19.3-300.fc29.x86_64"
1752437,2018-11-26 08:29:10 UTC,*** Bug 199529 has been marked as a duplicate of this bug. ***
1752437,2018-11-24 14:40:13 UTC,"(In reply to Maxime from comment #92)

> What do you mean with a HID component in this case? A stylus?
"
1752437,2018-11-24 14:34:06 UTC,"(In reply to Hans de Goede from comment #88)

> (In reply to Maxime from comment #87)
> > I applied the latest patch, it works but it makes my touchscreen show up as
> > having a battery that's at 0%. The previous patch had the same behaviour on
> > my system.
>
> Good to hear that this patch works for you to.
>
> The battery at 0% is an unrelated issue, please file a new bug against
> product Drivers component HID (or input if there is no HID component) for
> this.
"
1752437,2018-11-21 10:38:38 UTC,"(In reply to Maxime from comment #87)

> I applied the latest patch, it works but it makes my touchscreen show up as
> having a battery that's at 0%. The previous patch had the same behaviour on
> my system.
"
1752437,2018-11-21 23:09:11 UTC,"(In reply to Stephen Owusu from comment #85)

> I tried to apply a patch but the kernel fails to compile. It only generated
> the headers file. There was a recipe for target error for
> retpoline-check-generic. Anyone know how I can fix this? Also, I am very new
> to all this but how long does a patch submission to appear in the next
> release?
"
1752437,2018-11-21 22:42:42 UTC,"(In reply to Hans de Goede from comment #81)

> p.s.
>
> I plan to add the following to the commit msg, please let me know if you've
> objections against this:
>
> Reported-by: Lukas Kahnert <email address hidden>
> Tested-by: Marc <email address hidden>
"
1752437,2018-11-29 18:45:42 UTC,"(In reply to Hans de Goede from comment #97)

> (In reply to Addie Morrison from comment #96)
> > Is anyone else seeing the issue where the touchscreen/pen don't work when
> > the computer is first powered on (needs to be rebooted at least once)? If
> > so, was this supposed to be fixed by this or should that be a separate bug
> > report?
>
> When this happens do you see any relevant messages in dmesg ?
>
> In: https://bugzilla.redhat.com/show_bug.cgi?id=1644013
>
> There is a report of the machine sometimes reporting:
>
> [    5.739281] irq 7: nobody cared (try booting with the ""irqpoll"" option)
> [    5.739284] CPU: 5 PID: 0 Comm: swapper/5 Tainted: G         C
> 4.19.2-301.hdg1.fc29.x86_64 #1
> [    5.739285] Hardware name: HP HP ENVY x360 Convertible 15-cp0xxx/8497,
> BIOS F.21 10/19/2018
> [    5.739285] Call Trace:
> [    5.739288]  <IRQ>
> [    5.739294]  dump_stack+0x5c/0x80
> [    5.739297]  __report_bad_irq+0x37/0xae
> [    5.739298]  note_interrupt.cold.9+0xa/0x69
> [    5.739300]  handle_irq_event_percpu+0x6a/0x80
> [    5.739301]  handle_irq_event+0x27/0x44
> [    5.739302]  handle_fasteoi_irq+0x7f/0x120
> [    5.739305]  handle_irq+0xbf/0x100
> [    5.739307]  do_IRQ+0x49/0xd0
> [    5.739308]  common_interrupt+0xf/0xf
> [    5.739309]  </IRQ>
>
> After which the kernel disables IRQ 7 causing the touchscreen to not work
> again.
>
> If you're seeing this too, please open a new bug for the ""irq 7: nobody
> cared"" problem.
>
> The patch fixing the IRQ not being assigned to the GPIO controller has been
> merged upstream now, so I'm closing this bug.
"
1752437,2018-11-21 10:21:43 UTC,"I applied the latest patch, it works but it makes my touchscreen show up as having a battery that's at 0%. The previous patch had the same behaviour on my system."
1752437,2018-11-20 15:33:28 UTC,"(In reply to Hans de Goede from comment #81)

> p.s.
>
> I plan to add the following to the commit msg, please let me know if you've
> objections against this:
>
> Reported-by: Lukas Kahnert <email address hidden>
> Tested-by: Marc <email address hidden>
"
1752437,2018-11-20 08:51:06 UTC,"I tried to apply a patch but the kernel fails to compile. It only generated the headers file. There was a recipe for target error for retpoline-check-generic. Anyone know how I can fix this? Also, I am very new to all this but how long does a patch submission to appear in the next release?"
1752437,2018-11-19 18:20:26 UTC,"(In reply to Hans de Goede from comment #78)

> (In reply to Lukas Kahnert from comment #76)
> > This error happens because your patch only fixes the mis-detection of the
> > IRQ. There ist still https://bugzilla.kernel.org/show_bug.cgi?id=199529
> > which needs also bei fixed to get the touchscreen work.
>
> Right, I figured that out now, actually I believe that with your hack to
> drivers/acpi/resource.c the changes you made to drivers/base/platform.c
> should no longer be necessary.
>
> We've been looking at the wrong part of the DSDT the culprit is not:
>
> Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
>                     {
>                         0x00000007,
>                     }
>
> This uses an extended interrupt syntax, so acpi_dev_get_irqresource() gets
> called with legacy == false and the troublesome acpi_get_override_irq()
> never happens.
>
> I believe the real culprit is:
>
>     Scope (_SB.PCI0)
>     {
>         Device (SMBD)
>         {
>             Name (_HID, ""SMB0001"")  // _HID: Hardware ID
>             Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource
> Settings
>             {
>                 IO (Decode16,
>                     0x0B20,             // Range Minimum
>                     0x0B20,             // Range Maximum
>                     0x20,               // Alignment
>                     0x20,               // Length
>                     )
>                 IRQ (Level, ActiveLow, Shared, )
>                     {7}
>             })
>         }
>     }
>
> Which does use a legacy style IRQ resource, this causes
> acpi_dev_get_irqresource() to be called with legacy == true and then the
> troublesome acpi_get_override_irq() happens.
>
> I believe that this troublesome node gets parsed before the AMDI0030 node
> and then by the time the AMDI0030 node happens, inside
> acpi_dev_get_irqresource() we hit the else of:
>
>         irq = acpi_register_gsi(NULL, gsi, triggering, polarity);
>         if (irq >= 0) {
>                 res->start = irq;
>                 res->end = irq;
>         } else {
>                 acpi_dev_irqresource_disabled(res, gsi);
>         }
>
> Which sets the DISABLED flag, which is causing the issue in
> drivers/base/platform.c . The reason we hit the else path is because of the
> earlier enumeration of the same interrupt with conflicting trigger /
> polarity settings so the second one fails with -EBUSY (it would work if the
> flags would match).
>
> My new attempt deals with this by adding the ""SMB0001"" HID to the blacklist
> for creating platform devices, so that acpi_dev_get_resources() does not get
> called on it at all, avoiding the call of acpi_dev_get_irqresource() with
> legacy == false.
>
> The not creating of a platform_device for the ""SMB0001"" HID is not an issue
> since the driver for it is an acpi bus driver not a platform bus driver.
"
1752437,2018-11-19 17:53:02 UTC,p.s.
1752437,2018-11-23 03:09:20 UTC,"(In reply to Maxime from comment #87)

> I applied the latest patch, it works but it makes my touchscreen show up as
> having a battery that's at 0%. The previous patch had the same behaviour on
> my system.
"
1752437,2018-11-30 09:40:43 UTC,"(In reply to Bram Coenen from comment #99)

> First of all thank you helping out Hans. I got the same problem with ""irq 7:
> nobody cared"" and made a bug report over here:
> https://bugzilla.kernel.org/show_bug.cgi?id=201817 . I'm new to bug
> reporting, so I hope I did it right!
"
1752437,2018-12-16 16:41:37 UTC,"(In reply to Robert Munn from comment #103)

> I can confirm the patch is included in 4.19.7 as well.
"
1752437,2018-12-16 11:26:32 UTC,"(In reply to Eran Benjamin from comment #101)

> Hi all,
>
> I have been following this bug and patch for a while for my bq-100, it's
> exhilarating to know that you guys solved the touch/flip issue and I can go
> back as running my laptop vm host on linux again.
>
> I've been refreshing this daily to see when the RESOLVED changes into
> VERIFIED so I can DL a stable kernel, but I think it doesn't work this way.
>
> Therefore, can someone please point to how do I get Hans de Goede's patch
> into an ubuntu 18.10 install?
> Is it the patch command, or ukuu, or a clean compile of the kernel (and if
> so, any howto for ubuntu for required extras?).
>
> I usually don't poke into my daily driver computer if it's not required, but
> this Windows as host OS was supposed to only be till October, it unbalances
> my zen :-)
>
> So, wait till official patched Kernel (any time estimate)?
> Or patch the kernel?
>
> Cheers all.
"
1752437,2019-03-07 06:32:04 UTC,Does this still happen on an up-to-date system?
1752437,2018-12-25 04:52:11 UTC,"(In reply to Thomas from comment #111)

> (In reply to Thomas from comment #110)
> > I have installed archlinux and kernel 4.19.11-arch1-1-ARCH on my HP ENVY
> > x360 – 15-bq101ng. I also installed Gnome and Gnome-extra, but still my
> > Stylus and touchscreen do not work. Can some one help me please ?
> > Thanks
>
> I now even installed Ubuntu 18.10 with kernel 4.19.11 through ukuu but it
> still not work.
"
1752437,2018-12-24 22:00:17 UTC,"> acpi=noirq disables any hardware that makes use of irqs like the touchscreen.
> If you have a dual boot you could be affected by this https://bugzilla.kernel.org/show_bug.cgi?id=201817 which triggers a kernel panic when you reboot from windows(without a complete poweroff in between).
"
1752437,2018-12-24 20:00:50 UTC,"(In reply to Lukas Kahnert from comment #114)

> (In reply to Adynathos from comment #113)
> > I am observing similar problems with HP Spectre x360 15-df0850nz.
> >
> > It does not boot without **acpi=noirq**. With *acpi=noirq*:
> >
> > * Touchpad does not work
> > * Touchscreen or pen does not work
> > * Does not wake up after suspending
> > * Keyboard sometimes does not work, but will be fine again after reboot
> >
> > Here is the dmesg log from kernel 4.18.0:
> > https://alexandria.adynathos.net/d/2528a04f758c409c85c4/
> > I also tried kernel 4.20 from
> > https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable but
> > the problem persists.
> >
> > There are bugs filed on some of these topics, but they do not seem to cover
> > the IRQ booting problem:
> >
> > * https://bugzilla.kernel.org/show_bug.cgi?id=201775
> > * https://bugzilla.kernel.org/show_bug.cgi?id=201885
> >
> > I am new to ACPI errors, could you tell me how to proceed to best report or
> > try to fix this?
> > Thank you.
>
> acpi=noirq disables any hardware that makes use of irqs like the touchscreen.
> If you have a dual boot you could be affected by this
> https://bugzilla.kernel.org/show_bug.cgi?id=201817 which triggers a kernel
> panic when you reboot from windows(without a complete poweroff in between).
"
1752437,2018-12-24 19:44:41 UTC,"(In reply to Adynathos from comment #113)

> I am observing similar problems with HP Spectre x360 15-df0850nz.
>
> It does not boot without **acpi=noirq**. With *acpi=noirq*:
>
> * Touchpad does not work
> * Touchscreen or pen does not work
> * Does not wake up after suspending
> * Keyboard sometimes does not work, but will be fine again after reboot
>
> Here is the dmesg log from kernel 4.18.0:
> https://alexandria.adynathos.net/d/2528a04f758c409c85c4/
> I also tried kernel 4.20 from
> https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable but
> the problem persists.
>
> There are bugs filed on some of these topics, but they do not seem to cover
> the IRQ booting problem:
>
> * https://bugzilla.kernel.org/show_bug.cgi?id=201775
> * https://bugzilla.kernel.org/show_bug.cgi?id=201885
>
> I am new to ACPI errors, could you tell me how to proceed to best report or
> try to fix this?
> Thank you.
"
1752437,2018-12-23 22:31:04 UTC,"Marc Rene Schädler, as per upstream https://bugzilla.kernel.org/show_bug.cgi?id=198715#c97 a patch was merged upstream. Hence, to confirm your issue is resolved upstream, could you please revert any custom patched kernels, and test https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.8/ (no custom patches) and advise to the results?"
1752437,2018-12-23 19:25:43 UTC,I am observing similar problems with HP Spectre x360 15-df0850nz.
1752437,2018-12-16 09:13:04 UTC,"Hi all,"
1752437,2018-12-22 07:06:46 UTC,"Ok it work the problem was, that I start Windows 10 and restart the PC to Archlinux or Ubuntu. In Archlinux there is a log 'Disabling IRQ #7' when the bug appears, in the startup time."
1752437,2018-12-21 19:46:48 UTC,"I have installed archlinux and kernel 4.19.11-arch1-1-ARCH on my HP ENVY x360 – 15-bq101ng. I also installed Gnome and Gnome-extra, but still my Stylus and touchscreen do not work. Can some one help me please ?
Thanks"
1752437,2018-12-21 11:16:28 UTC,it is now working with vanilla kernel 4.9.10 and BIOS F.19 :smile:
1752437,2018-12-18 10:37:10 UTC,"I can confirm 4.19 from Ubuntu works well with Ubuntu 8.10, I've been using it for a couple of days now, it's fast and stable as long as you don't try to suspend (which freezes the machine)."
1752437,2018-12-16 19:02:19 UTC,"(In reply to Seth Shelnutt from comment #106)

> I've just updated to 4.19.9, verified the patch was included, and I'm now
> getting:
>
> cmi: probe of SMB0001:00 failed with error -5
"
1752437,2018-12-16 18:36:07 UTC,"I've just updated to 4.19.9, verified the patch was included, and I'm now getting:"
1752437,2018-12-16 18:30:02 UTC,"(In reply to m.kolesinski from comment #104)

> (In reply to Robert Munn from comment #103)
> > I can confirm the patch is included in 4.19.7 as well.
>
> AFAIK, patches aren't normally part of a kernel release...those are up to
> your distro.
>
"
1752437,2018-12-16 14:57:04 UTC,I can confirm the patch is included in 4.19.7 as well.
1752437,2018-12-21 22:51:53 UTC,"(In reply to Thomas from comment #110)

> I have installed archlinux and kernel 4.19.11-arch1-1-ARCH on my HP ENVY
> x360 – 15-bq101ng. I also installed Gnome and Gnome-extra, but still my
> Stylus and touchscreen do not work. Can some one help me please ?
> Thanks
"
1752437,2018-11-03 06:12:22 UTC,The issue affects all distributions running on HP touchscreen laptop powered with AMD processors.  The culprit is a misconfiguration of ACPI table impacting the touchscreen function. Some users attempted to workaround the problem but needed input from upstream.
1752437,2018-11-19 22:45:01 UTC,"(In reply to Hans de Goede from comment #77)

> Created attachment 279539 [details]
> [PATCH] ACPI / platform: Add SMB0001 HID to forbidden_id_list
>
> Ok second attempt, a completely different patch which I think actually is
> better (if it works).
>
> Please give this one a try (without any other patches for this same issue).
>
> Again please attach dmesg output.
>
> If this patch does not fix things, then also please attach the output of:
>
> ls /sys/bus/platform/devices
>
> I would like the output of that command for both a kernel without the patch
> as well as for one with the patch.
"
1752437,2018-05-13 06:58:58 UTC,"(In reply to Nicola Sorace from comment #27)

> Hello!
>
> I think I managed to apply Daniel's ACPI table patch, but the touchscreen
> still doesn't work. I now get this error in dmesg:
>
> [    2.284918] i2c_hid i2c-ELAN0732:00: HID over i2c has not been provided
> an Int IRQ
> [    2.286070] i2c_hid: probe of i2c-ELAN0732:00 failed with error -22
>
> I don't really know what I'm doing (took me like two days to apply the
> patch) so I'm sorry if I've done something dumb. I reaaally want to get this
> touchscreen working.
"
1752437,2018-03-26 06:55:58 UTC,"This is the reason why your touchpad doesn't work:
[    0.948213] amd_gpio AMDI0030:00: Failed to get gpio IRQ: -22
[    0.948487] amd_gpio: probe of AMDI0030:00 failed with error -22"
1752437,2018-03-22 15:46:09 UTC,"The device seems to be a ""ELAN0732""."
1752437,2018-03-16 07:16:09 UTC,"Created attachment 274773
DMESG output after boot on 4.16 (drm-next)"
1752437,2018-06-10 05:54:25 UTC,"Which BIOS is the most recent?
I thought ist was: F.17 Rev.A from 11. Apr. 2018 (17.7 MB)"
1752437,2018-03-15 17:00:07 UTC,This change was made by a bot.
1752437,2018-03-15 16:32:33 UTC,"Marc Rene Schädler, thank you for reporting this and helping make Ubuntu better."
1752437,2018-03-01 04:17:38 UTC,"Not sure what more information I should provide,
If there is more information needed to troubleshoot this issue please let me know."
1752437,2018-03-28 06:09:42 UTC,Thank you for pointing out the reason.
1752437,2018-02-13 20:45:06 UTC,"(In reply to g.fitch from comment #7)

> (In reply to Aidan Hahn from comment #3)
>
> > Which kernel are you using? I dont even get this output.
>
> 4.15-drm-next (fixes a nasty problem with 3 out of 5 boots locking up -
> still get irritating lock-ups when using X, and especially anything opengl).
>
> I turned on i2c debugging to see the status messages that the i2c-hid,
> elants_i2c etc. modules should be printing if they find the device but have
> some other communications problem.
>
> I'm new to this, so not sure what I'm looking at, but I think the
> touchscreen only identifies itself through ACPI, as an i2c slave at its own
> address, and drivers/i2c/i2c-core-slave.c can't enumerate that yet. So the
> device node doesn't get created, and the hid drivers have nothing to connect
> to.
>
> I could be completely wrong, though - I'm good at being wrong :)
"
1752437,2018-02-13 03:11:14 UTC,"Created attachment 274147
Disassembled ACPI table for HP Envy x360 15z (ryzen 5 2500u)"
1752437,2018-02-13 03:10:16 UTC,"I believe this problem to be related to the thread located here:
https://www.spinics.net/lists/linux-input/msg50784.html"
1752437,2018-02-13 01:27:15 UTC,"Created attachment 274145
DMESG on 4.16rc1"
1752437,2018-02-13 01:25:31 UTC,"I just tried kernel 4.16rc1
Touchscreen is still not operating. output very similar to 4.15 will attach another dmesg"
1752437,2018-02-12 10:41:16 UTC,This appears to be related - same machine (HP Envy x360 with Ryzen):
1752437,2018-02-07 21:26:05 UTC,"Link to the wacom-hid-descriptors bug report, for reference: https://github.com/linuxwacom/wacom-hid-descriptors/issues/12"
1752437,2018-02-07 20:50:42 UTC,"Created attachment 274057
dmesg output after boot"
1752437,2018-02-13 07:18:43 UTC,(In reply to Aidan Hahn from comment #3)
1752437,2018-03-29 10:24:56 UTC,Please try this kernel:
1752437,2018-03-16 07:15:27 UTC,Updated kernel to 4.16 (drm-next) and upon compile turned on some i2c debugging features. Now when I boot I recieve the following:
1752437,2018-04-11 22:19:01 UTC,This problem also affects me.  I have a similar model HP ENVY x360 15-bq0xx
1752437,2018-05-13 02:02:15 UTC,Hello!
1752437,2018-05-11 01:34:46 UTC,Lukas' patch also worked for me. Ubuntu 18.04 patched to Linux kernel 4.17-rc4 on my HP Envy x360 15-bq100 Convertible. Thanks to all that contributed to this issue!
1752437,2018-03-29 12:30:50 UTC,"Thanks, I tried it."
1752437,2018-05-02 23:25:17 UTC,"(In reply to m.kolesinski from comment #23)

> (In reply to Daniel Andersen from comment #22)
> > Created attachment 275675 [details]
> > ""Fixing"" the ACPI Error the other way around: patching the acpi table
> >
> > Instead of adding a temporary hack into the kernel, it is also possible to
> > patch the acpi table which is created by the HP Firmware. This should work
> > with all kernels and this would show that the main work to do is on HPs
> side
> > - not on the kernel developers side.
>
> I can confirm that hand-patching the ACPI to change the GPIO interrupt
> type/level eliminates the same GPIO error on my HP M6AR004DX laptop, which
> has an FX-9800P.  The ELAN0732 touchscreen still isn't working (on to the
> next error)...with the patched ACPI:
>
> [    8.464309] i2c_hid i2c-ELAN0732:00: i2c-ELAN0732:00 supply vdd not
> found, using dummy regulator
> [   13.490200] i2c_hid i2c-ELAN0732:00: failed to reset device.
> [   19.676718] i2c_hid i2c-ELAN0732:00: failed to reset device.
> [   25.863360] i2c_hid i2c-ELAN0732:00: failed to reset device.
> [   32.050080] i2c_hid i2c-ELAN0732:00: failed to reset device.
> [   33.063523] i2c_hid i2c-ELAN0732:00: can't add hid device: -61
> [   33.063732] i2c_hid: probe of i2c-ELAN0732:00 failed with error -61
>
> I've been trying to find information on how to fix this darned touchscreen
> controller for about a year.  The comments in this thread are the first that
> have actually made any real progress forward, so thank you to those that
> were able to dig into this.
"
1752437,2018-05-02 14:06:31 UTC,"(In reply to Daniel Andersen from comment #22)

> Created attachment 275675 [details]
> ""Fixing"" the ACPI Error the other way around: patching the acpi table
>
> Instead of adding a temporary hack into the kernel, it is also possible to
> patch the acpi table which is created by the HP Firmware. This should work
> with all kernels and this would show that the main work to do is on HPs side
> - not on the kernel developers side.
"
1752437,2018-04-30 10:40:04 UTC,"Created attachment 275675
""Fixing"" the ACPI Error the other way around: patching the acpi table"
1752437,2018-04-30 10:30:40 UTC,"Well, there is another temporary solution and that is fixing the ACPI table."
1752437,2018-04-26 15:30:47 UTC,"@Bráulio I'm sorry but I'm not a kernel developer and this patch is just a dirty hack, which only works on this notebook. On other hardware it could make the system unbootable.
For upstream it needs a cleaner solution."
1752437,2018-05-07 07:20:35 UTC,Lukas' patch works for me.
1752437,2018-04-25 22:24:08 UTC,"(In reply to Lukas Kahnert from comment #14)

> Created attachment 275381 [details]
> possible fix for touchscreen
>
> I think I found the problem.
> There are 2 ACPI-related bugs which prevents the detection of the
> touchscreen.
>
> 1. As already mentioned, the AMD GPIO driver tries to get an IRQ for GPIO
> but the ACPI code is missing for x86.
> 2. The IRQ of the GPIO device is misconfigured. For some reason it sets the
> IRQ ""edge, high"" but in the ACPI table it's defined as ""level, low"".
>
> I made a fix but it's only a temporary workround until someone who have more
> knowledge of the subsystems can implement it cleaner.
> Could someone try this patch on a desktop enviroment? I just tested the
> output of hidraw which worked.
"
1752437,2018-04-15 19:03:18 UTC,"(In reply to g.fitch from comment #15)

> Hi Lukas,
>
> I tested it with KDE 5 (17.12.3) with one of the drm-next kernels:
> Linux tau-ceti 4.16.0-rc7-gc5902206599d-dirty #4 SMP PREEMPT Sun Apr 15
> 17:37:13 BST 2018 x86_64 AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
> AuthenticAMD GNU/Linux
>
>
> Your patch works fine for the touchscreen on this laptop - touchscreen is
> detectable and usable with both finger and the supplied pen.
>
> The relevant bit of dmesg is:
>
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: ACPI slave is
> not supported yet
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: Standard-mode
> HCNT:LCNT = 642:749
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: Fast-mode
> HCNT:LCNT = 132:239
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: GPIO lookup for
> consumer scl
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: using ACPI for
> GPIO lookup
> Apr 15 17:47:11 tau-ceti kernel: acpi AMDI0010:00: GPIO: looking up scl-gpios
> Apr 15 17:47:11 tau-ceti kernel: acpi AMDI0010:00: GPIO: looking up scl-gpio
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: using lookup
> tables for GPIO lookup
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: lookup for GPIO
> scl failed
> Apr 15 17:47:11 tau-ceti kernel: i2c-dev: adapter [Synopsys DesignWare I2C
> adapter] registered as minor 5
> Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: adapter [Synopsys DesignWare I2C
> adapter] registered
> Apr 15 17:47:11 tau-ceti kernel: acpi ELAN0732:00: GPIO: looking up 0 in _CRS
> Apr 15 17:47:11 tau-ceti kernel: gpio gpiochip0: Persistence not supported
> for GPIO 89
> Apr 15 17:47:11 tau-ceti kernel: i2c_hid i2c-ELAN0732:00: probe
> Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: master_xfer[0] W, addr=0x10,
> len=2
> Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: master_xfer[1] R, addr=0x10,
> len=30
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: i2c_dw_xfer:
> msgs: 2
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: enabled=0x1
> stat=0x10
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: enabled=0x1
> stat=0x504
> Apr 15 17:47:11 tau-ceti last message repeated 9 times
>
>
>
> The patch creates one issue, which is that the following warning now pops up
> at boot:
>
> The battery in your keyboard (""ELAN0732:00 04F3:2537"") is low, and the
> device may turn itself off at any time. Please replace or charge the battery
> as soon as possible.
>
> However all other peripherals and buttons work fine, so it's a minor
> nuisance.
>
> Thank you for getting us this far!
"
1752437,2018-04-15 18:37:53 UTC,"Created attachment 275385
config for working system"
1752437,2018-04-15 17:12:09 UTC,"Hi Lukas,"
1752437,2018-04-15 14:52:21 UTC,"Created attachment 275381
possible fix for touchscreen"
1752437,2018-04-15 00:37:33 UTC,"Created attachment 275377
dmesg output from kernel 4.16(with hacks)"
1752437,2018-04-15 00:33:33 UTC,"I recently bought the same laptop and tried to look deeper into the problem.
I'm not a kernel developer or have any knowledge in kernel subsystems but what I found so far is that the AMD GPIO driver doesn't support ACPI for x86 platforms.(Kernel 4.16)
On HP Envy x360(Ryzen) the GPIO device is detected as ACPI device with an interrupt resource."
1752437,2018-04-25 22:25:44 UTC,"Also Lukas, can you upstream this patch?"
1752440,2018-03-05 16:37:55 UTC,"@andreserl I'm not sure if I'm using a mirror or not, I'm just using the built in maas.io images. Where would I see that/what log are you looking for? Once I get Bionic installed or the latest lshw compiled, I'll get you all the logs. Thanks!"
1752440,2018-03-02 21:11:52 UTC,"Are you using a mirror ? That could be due to a mirror not up to date with
the Ubuntu images but I wouldn’t be sure without a full log."
1752440,2018-03-02 20:51:34 UTC,"I tried deploying Bionic out through MaaS but it doesn't seem to be working. Looking at the console of the system, I'm getting a ""failed posting event: start: init-local/check-cache: attempting to read from cache [trust]"". Screenshot is attached as well (let me know if you want me to open up a separate ticket for this). Since I can't deploy out Bionic, I'll try compiling lshw from scratch."
1752440,2018-03-02 09:37:52 UTC,It look like these patches have already been accepted into the Bionic version of lshw.
1752440,2018-02-28 22:46:45 UTC,So this is definitely and issue in LSHW. MAAS directly grabs the information from there.
1752440,2018-02-28 22:56:27 UTC,Could you please post the lshw output in XML form to allow us to create a unit test?
1752440,2018-02-28 22:49:18 UTC,"Actually, I think I may have spoken too soon. Lshw shows two banks of memory:"
1752440,2018-03-05 16:47:11 UTC,Attached is the latest lshw.log from lshw version B.02.18.76. Looks like its getting the right DIMM size (64GB each).
1752440,2018-03-02 09:29:38 UTC,"lshw shows two banks of memory but MAAS is still correctly calculating the output from lshw. There are twelve occurrences of the line <size units=""bytes"">34358689792</size> which is 384GB. I looked up the part number reported by lshw, 72ASS8G72LZ-2G3B2. According to [1] each DIM should be 64G, not 32G. There is a commit upstream [2] which adds support for DDR4 RAM and another [3] which adds support for larger amounts of RAM found in DDR4 RAM. As [1] says this module is DDR4 I suspect the version of lshw in Ubuntu needs both these patches."
1752448,2018-03-05 14:00:03 UTC,Feel free to word the new message in whatever way you feel is more correct. The current message is definitely incorrect.
1752448,2018-03-05 08:39:04 UTC,"I'm not sure if we can improve that. The current message is somewhat correct, changing it to ""already installed"" would be sort of wrong - whether it's installed or not does not matter. What's mattering is that these versions are supposed to remain installed, sort of."
1752452,2019-05-22 14:42:01 UTC,"in disco, with automated testing on."
1752452,2019-04-01 16:03:05 UTC,"ATM bionic is busted, but I did fix up disco. Disco should be working correctly."
1752452,2018-03-02 02:16:29 UTC,Some changes need to be made to this file I presume: https://bazaar.launchpad.net/~ubuntu-cdimage/debian-cd/ubuntu/view/head:/tools/boot/bionic/boot-ppc64el
1752452,2018-02-28 23:44:06 UTC,"console right before the grub prompt, note the unrecognized number message:"
1752452,2018-03-01 07:51:50 UTC,Recreated per IRC discussions I was highlighted - in this case you should assume the ISO is bad and not your commandline.
1752452,2018-03-01 07:53:39 UTC,On the ISO content:
1752453,2018-03-01 00:00:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1752453,2018-03-01 00:33:37 UTC,ok. cat /var/log/installer/syslog > was empty. So was partman.
1752453,2018-03-01 00:52:42 UTC,"I wonder if it's specifically related to Kubuntu only? After checking other archs could you also, by any chance, try installing any other .4 flavours on that system?"
1752453,2018-03-01 04:09:15 UTC,"Since I'm done testing Kubuntu, I will test Lubuntu .4 i386."
1752453,2018-03-01 05:10:43 UTC,"Lubuntu's i386 testcases were all covered, so I tried MATE's instead. It passes with flying colors. In some ways, looks better than ours too!"
1752453,2018-03-01 11:36:57 UTC,"It'll be really hard to assess this issue without any logs. A few other testers that I asked to check out the i386 Kubuntu images weren't able to reproduce the aforementioned issues. Similarly, even after multiple attempts it was still always successful for me in an i386 kvm. It's very worrying but without it being reproducible for others or easily identifiable, I don't want to consider it a blocker for the release."
1752453,2018-03-01 18:44:41 UTC,"@valorie-zimmerman: cyphermox tested on his i386 machine Kubuntu installation and it went fine, so if you don't mind I'd like to include i386 Kubuntu in the release right now."
1752453,2018-03-06 22:43:09 UTC,Yes of course. We can't pull support with no announcement beforehand.
1752459,2020-03-20 15:34:34 UTC,Note: It seems you can workaround this by closing the channel and reopening it for only the architectures you want to keep.
1752459,2018-05-10 22:22:50 UTC,"We will need to write a user story for this, I suspect this is more of an ""unrelease"" scenario than what we designed `close` for."
1752459,2018-05-10 21:46:32 UTC,Ah! I definitely didn't read the bug report that way :) .
1752459,2018-05-10 21:32:03 UTC,That's exactly my point.
1752459,2018-05-10 12:17:24 UTC,closing should be arch independent.
1752459,2018-05-10 17:29:38 UTC,"Whoa, it's not? No kidding, on it."
1752459,2018-05-10 20:21:05 UTC,"Alan, I'm not seeing this behavior. The only information snapcraft sends to the store seems to be the channel, no arch-specific stuff. Also, I just tested closing on my amd64 machine, and it's closed on my arm64 machine as well. Can you verify this, and perhaps walk me through how to reproduce it?"
1752463,2018-03-15 22:17:44 UTC,Thanks. Probably need Sylvain Bauza to take a look at this.
1752463,2018-03-15 22:21:33 UTC,"Although, isn't there a workaround for this?"
1752463,2018-03-21 14:02:56 UTC,"While I understand your point, I tried to not provide a documentation for only one specific GPU driver, here NVidia."
1752463,2018-03-21 18:11:02 UTC,"Matt, https://review.openstack.org/#/c/459753/ is for hiding the hypervisor signature in the guest because the nVidia driver checks it. That's for GPU passthrough, not for virtual GPU given you need to have a specific nVidia driver for your compute node itself (not the guest)."
1752470,2018-03-01 02:23:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548733"
1752472,2018-03-05 08:40:39 UTC,I forgot to add python3-macaroonbakery as a dependency. python3-macaroonbakery is used in the livepatch python helper and is not automatically picked as a dependency.
1752472,2018-03-26 10:44:44 UTC,This bug was fixed in the package gnome-online-accounts - 3.27.92-1ubuntu2
1752472,2018-03-02 16:46:24 UTC,"On Fri, Mar 02, 2018 at 07:51:58AM -0000, Sebastien Bacher wrote:

> The provider has been discussed with upstream and they are fine on the
> idea, Marco did a first code review and upstream said they would review
> it as well this week.
"
1752472,2018-03-01 03:19:47 UTC,Please find attached the required debdiff.
1752472,2018-03-01 04:19:40 UTC,"The attachment ""goa.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1752472,2018-03-02 07:51:58 UTC,"The provider has been discussed with upstream and they are fine on the idea, Marco did a first code review and upstream said they would review it as well this week."
1752479,2018-03-15 20:59:30 UTC,https://review.openstack.org/#/c/551922/
1752479,2018-03-16 09:44:59 UTC,Ironic spec for dynamic portgroups: https://specs.openstack.org/openstack/ironic-specs/specs/approved/dynamic-portgroups.html
1752480,2018-03-05 09:41:07 UTC,https://review.openstack.org/#/c/548877/1
1752480,2018-03-10 11:03:44 UTC,https://review.openstack.org/#/c/549920/
1752480,2018-06-25 12:33:39 UTC,This issue was fixed in the openstack/networking-generic-switch 1.1.0 release.
1752485,2018-03-01 08:08:55 UTC,"What I reported, is not a bug, it is let say a feature."
1752485,2018-03-01 04:48:51 UTC,Silviu-
1752499,2018-03-19 19:31:14 UTC,"Unfortunately, https://github.com/openstack/horizon/blob/41da50adabb7121ea3c2d2d85ad039192b9940cf/doc/source/user/browser_support.rst is out of date. AFAIR, it was discussed some time ago in IRC and we agreed to not make IE support as a priority for us"
1752507,2018-05-05 04:21:48 UTC,looks like the -needed tags were missing..
1752507,2018-03-01 07:22:59 UTC,looks like artful is missing it too
1752507,2018-04-24 15:25:54 UTC,"For xenial the firmware has been added as part of bug 1763823, ""Update firmware for 18.04 hwe kernel."" Still needed for artful, and since there's no way to dup only the xenial task I'm marking it fix committed."
1752507,2018-04-24 23:21:03 UTC,Note that actually loading the firmware by the kernel is affected by https://bugs.launchpad.net/intel/+bug/1760545 or requires (currently) manually updating the kernel's initramfs with the added firmware.
1752507,2018-04-30 17:30:03 UTC,"Hello Timo, or anyone else affected,"
1752507,2018-05-05 00:30:21 UTC,Tested and verified using cod/tip/drm-tip/2018-05-04 mainline build with upgraded linux-firmware from xenial-proposed:
1752507,2018-05-05 01:46:15 UTC,"ubuntu@ubuntu:~$ ls -l /lib/firmware/i915/glk_dmc_ver1_04.bin
-rw-r--r-- 1 root root 8800 Apr 24 15:28 /lib/firmware/i915/glk_dmc_ver1_04.bin
ubuntu@ubuntu:~$ dpkg -s linux-firmware
Package: linux-firmware
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 223599
Maintainer: Ubuntu Kernel Team <email address hidden>
Architecture: all
Multi-Arch: foreign
Version: 1.157.18
Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-restricted-common
Provides: atmel-firmware
Breaks: linux-firmware-snapdragon (<= 1.2-0ubuntu1)
Conflicts: atmel-firmware
Description: Firmware for Linux kernel drivers
 This package provides firmware used by Linux kernel drivers.
ubuntu@ubuntu:~$"
1752507,2018-05-05 01:47:55 UTC,ALso tested and verified using cod/tip/drm-tip/2018-05-04 mainline build with upgraded linux-firmware from artful-proposed:
1752507,2018-05-05 01:50:34 UTC,"ubuntu@ubuntu:~$ ls -l /lib/firmware/i915/glk_dmc_ver1_04.bin
-rw-r--r-- 1 root root 8800 Apr 24 15:28 /lib/firmware/i915/glk_dmc_ver1_04.bin
ubuntu@ubuntu:~$ dpkg -s linux-firmware
Package: linux-firmware
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 210549
Maintainer: Ubuntu Kernel Team <email address hidden>
Architecture: all
Multi-Arch: foreign
Version: 1.169.4
Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-restricted-common
Provides: atmel-firmware
Breaks: linux-firmware-snapdragon (<= 1.2-0ubuntu1)
Conflicts: atmel-firmware
Description: Firmware for Linux kernel drivers
 This package provides firmware used by Linux kernel drivers.
ubuntu@ubuntu:~$"
1752507,2018-05-05 01:56:35 UTC,@Łukasz Zemczak (sil2100)
1752510,2018-03-04 09:18:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752512,2018-03-02 09:20:24 UTC,"Hi Thaodan,"
1752512,2018-03-02 12:12:41 UTC,"The network was not interrupted and even then the error should show this.
There's no progress dialog or something visible."
1752514,2018-03-01 08:19:25 UTC,"The attachment ""patch-xrdp-0.9.5-pfs.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1752519,2018-03-01 09:50:12 UTC,"loci install pip packages with few flags, so installing these packages isn't going to fix the issue."
1752520,2018-03-01 10:16:38 UTC,LGTM.
1752520,2018-03-30 20:05:00 UTC,"My patch was accepted by hostap upstream, meaning that as soon as we merge into our repository, we no longer require libradsec for the initiator part."
1752526,2018-05-29 18:22:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752528,2018-03-01 09:22:55 UTC,Sorry. Mistyped. Read initramfs SETS UP wrong ......
1752535,2018-03-01 09:45:45 UTC,From errors.u.c it started on Feb 27th on Bionic.
1752535,2018-03-01 09:47:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752535,2018-03-05 15:27:05 UTC,The issue there is
1752535,2018-03-22 19:31:34 UTC,How is this not listed under bionic? It is currently impossible to install daily image because of this bug - the installer crashes.
1752537,2018-03-01 10:02:31 UTC,I think this is a themeing problem (because of the unusual code in GNOME Tweaks).
1752540,2018-03-15 05:35:19 UTC,"Reviewed:  https://review.openstack.org/552898
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=d451edc2b83128e182e8885adf01f925ea2f98b6
Submitter: Zuul
Branch:    stable/queens"
1752540,2018-03-28 23:16:04 UTC,"Reviewed:  https://review.openstack.org/554675
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=5ca262641f5a8182d0f87c413f919c47b43b27ac
Submitter: Zuul
Branch:    stable/pike"
1752540,2018-04-10 10:56:57 UTC,"Hi,"
1752540,2018-05-03 15:16:33 UTC,"So since this task is delegated, compute node (os-rone-kvm-01 in Kevin's case) should have SSH key to access containers. I tried to add the ssh key to compute node to user root manually and after that I tried to connect to container correctly. But anyway after running playbooks I receive this error:"
1752540,2018-05-04 11:10:11 UTC,As hotfix can be copying hosts file from any target host to deployment host.
1752540,2018-03-14 20:42:03 UTC,"Reviewed:  https://review.openstack.org/552900
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=707398789403293aaedc1d78ddc4a164611366c7
Submitter: Zuul
Branch:    stable/ocata"
1752540,2018-05-04 11:07:27 UTC,"So deployment host is delegating task to nova_conductor container, but it uses its container name as hostname for SSH eg. controller1_nova_conductor_container-c4707efe and deployment host doesn't have hosts file prepared as target nodes."
1752540,2018-03-14 18:03:29 UTC,"Reviewed:  https://review.openstack.org/552899
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=c581c2af7b2bfdf60fb4467d7d5b17bed32fc85f
Submitter: Zuul
Branch:    stable/pike"
1752540,2018-03-14 12:57:47 UTC,"Reviewed:  https://review.openstack.org/547072
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=6321cf90304023c20dc6abb87e2fa20107b7051d
Submitter: Zuul
Branch:    master"
1752540,2018-03-14 13:04:19 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/552899"
1752540,2018-03-14 13:01:57 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/552898"
1752540,2018-03-14 13:04:48 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/552900"
1752540,2018-03-05 11:30:27 UTC,"Change abandoned by git-harry (<email address hidden>) on branch: master
Review: https://review.openstack.org/548921
Reason: Currently blocked by https://bugs.launchpad.net/openstack-ansible/+bug/1753443"
1752540,2018-03-05 11:23:45 UTC,"@Jesse, it appears that review addresses this issue as a side effect of the changes being made but is not intentionally trying to address this bug. I'm happy to abandon 548921 in favour of that change as long as its larger scope isn't likely to significantly slow its progress. This bug is a common source of failure when deploying multiple compute nodes."
1752540,2018-03-05 08:04:05 UTC,I think this issue is already being worked on in https://review.openstack.org/547072 ?
1752540,2018-03-01 11:27:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/548921"
1752550,2018-03-01 11:30:06 UTC,This change was made by a bot.
1752550,2018-03-02 04:10:03 UTC,"It looks like this might be related to bug 1452016, there is no ppc64le specific template available on Trusty."
1752576,2018-03-05 13:42:13 UTC,"On Thu, Mar 01, 2018 at 01:18:46PM -0000, Christian Dywan wrote:

> testtools.matchers._impl.MismatchError: 'mkdir -p /tmp/tmpsol__uqg/core\n/snap/snapcraft/current/usr/bin/unsquashfs -d /tmp/tmpsol__uqg/core/current /tmp/tmpsol__uqg/.cache/snapcraft/projects/snapcraft-core/snap_hashes/armhf/88c510ff6076cdabd32dd70edcc1cbb29e949e0c681488d35b4477070baa41a483f90da246f029477ab0a4e831e7e234\n' does not match /.*mkdir -p /tmp/tmpsol__uqg/core\nunsquashfs -d /tmp/tmpsol__uqg/core/current .*88c510ff6076cdabd32dd70edcc1cbb29e949e0c681488d35b4477070baa41a483f90da246f029477ab0a4e831e7e234\n/
"
1752610,2018-03-02 04:55:41 UTC,"Hi Raffamaiden,"
1752610,2018-03-02 07:03:20 UTC,By running
1752610,2018-03-07 04:31:44 UTC,"Hi Raffamaiden,"
1752610,2018-03-07 09:24:39 UTC,"Maybe there is a difference between a fresh Ubuntu 17.10 install and update from previous version of Ubuntu (the latter is my case).
Any way I was missing that library and the .run file did not install it.
Thanks."
1752613,2019-06-17 04:17:19 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1752613,2019-06-17 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1752613,2019-04-17 06:00:00 UTC,"Hello,
do you still seeing this issue with the latest 4.15 HWE kernel?
Thanks"
1752613,2018-04-25 09:18:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752613,2018-04-25 09:19:26 UTC,Updated to 4.13.0-38 but the issue still persists.
1752632,2019-12-07 10:39:30 UTC,I'm adding the wsl tag because soon the MOTD will be shown in WSL terminal and this script's speed affects the time needed to show it.
1752632,2020-05-01 20:04:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752632,2019-12-07 10:37:25 UTC,"I confirm that the observation in the bug is valid, but since the MOTD component includes dynamic data such as system load IMO it should not be cached."
1752635,2020-05-02 00:31:07 UTC,has this landed?
1752639,2018-04-07 16:56:39 UTC,I also had the battery indicator similarly disappear after I played with the options to show percentage and time with the icon.
1752639,2018-04-11 13:10:36 UTC,"Indicator-sound fails to compile at the moment, due to some error with pulseaudio."
1752646,2020-11-24 16:10:44 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1752646,2021-01-24 04:17:25 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1752654,2018-03-02 17:04:01 UTC,"For album gain, the we hole album needs to be analyzed together, somehow as a single track.
For this to work, we need to fetch all tracks from an album in one analysis.
It will get a bad result of a single track is missing or the album tracks are ripped from different recordings."
1752654,2018-05-09 22:31:35 UTC,"Ups, #7 went to the wrong bug."
1752654,2018-05-09 22:28:59 UTC,"Mixxx has already global accessible control objects for it: [Recording], ""status"" with RECORD_OFF (0.0) RECORD_READY (1.0) RECORD_ON (2.0) and RECORD_SPLIT_CONTINUE (3.0) and [Recording], ""toggle_recording"".
These controls might be used from a PlugIn, to enforce the streaming user conditions. If [Recording], ""status"" is different from 0.0 the Plug-In may stop either the stream or the recording via [Recording], ""toggle_recording"""
1752654,2018-03-02 12:08:53 UTC,I would like if Mixxx could calculate this along with the track gain. The analyzer could be toggled by a preference option so users who would not use album gain would not need to spend the CPU time analyzing it. I am not sure how to implement this because Mixxx analyzes one track at a time.
1752654,2018-03-02 17:16:33 UTC,"Perhaps we could cache a running average per album in the database? I'm not sure how album gain normalization is typically calculated, so that might not be feasible."
1752654,2018-03-02 02:16:32 UTC,The use case is playing whole albums with AutoDJ and preserving the relative levels of tracks within each album.
1752654,2018-03-01 18:18:20 UTC,Please explain your use case.
1752654,2018-03-02 06:24:41 UTC,"Thinking of it again, the album replay gain is probably the one that is the ""intended"" loudness of a track.
For example, it does not make sense to play a noise floor intro at track replay gain. That would be much to loud."
1752656,2019-07-08 10:55:55 UTC,"Note that SRUing debian-archive-keyring to xenial and earlier is hard, because its keyring generation code relies on gpg features that were added after bionic, and avoiding those features would break reproducibility of the generated keyring files and invalidate the signatures by Debian release team members.  If we need to do this it's possible the only sensible option would be to smash in the generated files."
1752659,2019-10-23 19:41:55 UTC,Adding context to some of the references in the first paragraph of this bug:
1752670,2018-03-01 18:36:09 UTC,Ubuntu folks need to import ppp 2.4.7-2+2 from Debian where this is fixed. Apologies for the trouble.
1752680,2020-06-15 02:12:07 UTC,"Sounds like a different bug, maybe? This bug looks more like night light going off when it should be on."
1752680,2019-12-16 02:07:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752680,2020-06-14 11:43:17 UTC,I've related issue. I'm on Focal 20.04 LTS.
1752680,2018-08-08 08:53:39 UTC,The problem still exists in the latest (18.04.1) LTS release.
1752680,2018-03-01 18:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1752680,2018-03-02 05:22:34 UTC,See also bug 1728342
1752680,2018-08-08 08:33:34 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018."
1752680,2018-03-01 18:53:45 UTC,"These log files collect private information like the contents of my drives, which is not acceptable. I cannot run the apport-collect command."
1752681,2018-03-01 20:19:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1752681,2018-03-05 18:06:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752681,2018-03-05 18:16:39 UTC,"I encounter the same problem with the daily Xubuntu 18.04 and Ubuntu MATE 18.04 of March 5, 2018. The connection via ethernet cable does not work unless I disable the ipv6.
In practice I have to set the Method to Ignore in IPV6 Settings to navigate."
1752681,2018-03-06 06:04:59 UTC,"@Marco,
I also have disabled IPV6 but still the same thing happens. Many users reported that problem and I see many post for older ubuntu versions. That is a very annoying bug."
1752681,2018-03-06 19:07:20 UTC,"In my case it works also by setting the IPV6 to ""Automatic, address only"".
Try like this. Turn off the connection, set it to Automatich, address only or ""Ignore"" and then re-enable the connection. In my case this procedure works (see attachment)"
1752685,2018-08-05 04:31:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752692,2018-07-24 09:34:06 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1752697,2018-03-02 08:53:01 UTC,I cannot reproduce this bug. Tags are not exported unless the the config option is enabled. I'm always able to restore the metadata that is present in the file with Metadata > Import from File Tags. Please note that missing fields in file tags are ignored during import and do not overwrite the metadata managed by Mixxx. The file tag must contain an empty/blank field to clear the corresponding field in Mixxx.
1752697,2018-03-05 19:41:09 UTC,It seems that I do not understood how this works.
1752697,2018-03-06 18:25:05 UTC,Related: https://bugs.launchpad.net/mixxx/+bug/1748758
1752697,2018-03-06 18:26:29 UTC,...according to the preference settings.
1752697,2018-03-06 19:41:40 UTC,"Yes, this seems good."
1752699,2019-05-28 21:34:24 UTC,There is already a feature file for this functionality
1752709,2018-03-02 16:58:43 UTC,"I can reproduce the issue by unplugging and usb stick! When I plug it in nothing special happens, but when I unplug it the bug appears immediately. The same workaroud (switching VTs) resolves it temporarily."
1752709,2018-12-13 09:32:14 UTC,"Reproduced it with the current 18.04.
 - resume after stand-by
 - switch to a different VT solves the problem"
1752709,2018-12-13 09:32:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752709,2018-03-02 01:51:08 UTC,I would like to find out if this is a problem in libinput.
1752709,2018-03-01 20:57:30 UTC,"Sorry, I made a mistake: the original report and the subsequent comment apply to xorg session, not wayland. But the bug also occurs with the wayland session, the only difference being that under wayland, switching VTs does not make the issue disappear, only logging out and back in does."
1752709,2018-03-01 20:49:44 UTC,After some more testing I can add the following:
1752709,2018-03-02 16:26:08 UTC,"It seems Unity is not affected. I took some time to respond because I could not reproduce the bug yesterday after rebooting the machine. It seems something triggers the bug, and once it has been triggered I can consistently reproduce it with pm-suspend, even after logging out and back in (this in itself makes the issue disappear, but suspending makes it appear again)."
1752712,2018-03-26 17:25:21 UTC,"i had the same issue, on ubuntu 18.04 LTS installed this package :"
1752712,2018-06-07 07:38:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752712,2018-06-30 02:00:51 UTC,Installing libgnomeui-0:amd64 resolved the issue for me. Ubuntu 18.04.
1752712,2019-01-03 14:38:44 UTC,"Installing libgnomeui-0:amd64 resolved the issue for me too. Ubuntu 18.04
sudo apt install libgnomeui-0:amd64"
1752712,2019-07-21 06:27:42 UTC,"I also got this crash on Ubuntu 18.04, then installing libgnomeui-0:amd64 also works well for me :)
sudo apt-get install libgnomeui-0:amd64"
1752721,2020-01-08 06:46:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752721,2020-01-08 06:47:35 UTC,me too. - 14.04
1752721,2020-01-08 06:49:16 UTC,"resolved
sudo apt install sensible-utils"
1752725,2018-03-02 10:39:48 UTC,Please do not spam the #tripleo channel w/ alerts on non-voting jobs
1752736,2018-03-02 15:47:45 UTC,"2017-10-27 20:28:57.855 29039 CRITICAL nova [req-deca1acd-7a73-4bac-a1b6-95ae5466e8a0 - -] Unhandled error: NotAllowed: Connection.open: (530) NOT_ALLOWED - access to vhost 'nova_cell1' refused for user 'stackrabbit'
2017-10-27 20:28:57.855 29039 ERROR nova Traceback (most recent call last):
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/usr/bin/nova-compute"", line 10, in <module>
2017-10-27 20:28:57.855 29039 ERROR nova     sys.exit(main())
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/opt/stack/nova/nova/cmd/compute.py"", line 57, in main
2017-10-27 20:28:57.855 29039 ERROR nova     topic=compute_rpcapi.RPC_TOPIC)
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/opt/stack/nova/nova/service.py"", line 240, in create
2017-10-27 20:28:57.855 29039 ERROR nova     periodic_interval_max=periodic_interval_max)
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/opt/stack/nova/nova/service.py"", line 126, in __init__
2017-10-27 20:28:57.855 29039 ERROR nova     conductor_api.wait_until_ready(context.get_admin_context())
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/opt/stack/nova/nova/conductor/api.py"", line 67, in wait_until_ready
2017-10-27 20:28:57.855 29039 ERROR nova     timeout=timeout)
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/opt/stack/nova/nova/baserpc.py"", line 58, in ping
2017-10-27 20:28:57.855 29039 ERROR nova     return cctxt.call(context, 'ping', arg=arg_p)
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py"", line 169, in call
2017-10-27 20:28:57.855 29039 ERROR nova     retry=self.retry)
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/usr/lib/python2.7/site-packages/oslo_messaging/transport.py"", line 123, in _send
2017-10-27 20:28:57.855 29039 ERROR nova     timeout=timeout, retry=retry)
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 578, in send
2017-10-27 20:28:57.855 29039 ERROR nova     retry=retry)
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 522, in _send
2017-10-27 20:28:57.855 29039 ERROR nova     msg.update({'_reply_q': self._get_reply_q()})
2017-10-27 20:28:57.855 29039 ERROR nova   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 503, in _get_reply_q
2017-10-2"
1752736,2018-03-19 23:55:49 UTC,This would have to be handled a bit differently than the existing timeout code that was linked in the bug report.
1752737,2018-03-01 23:02:38 UTC,"Thanks; this is a bug in avahi itself [1], so the best we can do is work around this in MAAS."
1752737,2018-03-19 13:17:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752737,2018-09-05 21:25:56 UTC,In MAAS we have provided a work around in LP: #1773698
1752737,2019-05-07 01:25:22 UTC,"Potential upstream fix for backport, may be relevant to MAAS:
https://github.com/lathiat/avahi/pull/206"
1752738,2018-03-27 09:39:48 UTC,"Bug is not reproduced for queens release, maybe already fixed?"
1752738,2018-08-06 08:36:37 UTC,"I have reproduced this error on solidfire not lvm.
It looks like not implemented yet get_manageable_volumes method in solidfire.py"
1752741,2019-08-21 21:46:17 UTC,This is still an issue in Disco with plasma-nm 5.16.4.
1752758,2018-04-02 15:13:03 UTC,I am closing this bug because this has been resolved in:
1752769,2018-03-03 16:35:22 UTC,Will be fixed in vte2.91 version 0.51.92.
1752769,2018-03-02 13:06:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752769,2018-03-02 13:07:26 UTC,"Indeed, thanks for the report."
1752769,2018-03-02 03:31:56 UTC,mate-terminal and terminator have the same problem. The checkboxes for 'allow bold text' can be clicked but they do nothing.
1752772,2018-10-21 07:54:16 UTC,"This page at a hardware troubleshooter gives a brief description of why resume-after-suspend is prone to loss of connectivity. I think it suggests that this recurring bug may involve any number of factors, such as BIOS/UEFI (updated in 18.10,) networking hardware drivers, grub2, system configuration."
1752772,2019-04-09 05:11:42 UTC,"Gordon,
Please file a separate bug report, thanks."
1752772,2019-04-08 21:37:08 UTC,Is this issue fixed in 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019?
1752772,2019-01-18 04:30:13 UTC,"Please test the kernel in -proposed, thanks!"
1752772,2019-01-18 03:22:39 UTC,"And, after running the Ubuntu software update, the problem still exists with 4.15.0-43
uname -a
Linux platinum-ubuntu 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1752772,2019-01-18 03:05:48 UTC,"I am also affected by this bug.
uname -a
Linux platinum-ubuntu 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1752772,2019-01-16 15:30:59 UTC,"i solved my problem of ""ethernet card don't work after returning from suspension"" by updating kernel from 4.15 to 4.20 (Ubuntu 18.04 Bionic) using UKUU
to install the latest kernel install Ubuntu Kernel Update Utility
$ sudo add-apt-repository ppa:teejee2008/ppa
$ sudo apt-get install ukuu
disable access control with the following command:
$ sudo xhost +
then install with ukuu
$ sudo ukuu
$ sudo ukuu --install-latest
and reboot
$ sudo reboot"
1752772,2019-01-09 09:55:08 UTC,"I thought my above script was working, but lately it hasn't worked.
So I changed it to this now, disabled then enabled the service and it worked when I tested it now."
1752772,2019-01-05 11:16:47 UTC,"Regarding my previous comment
""4.15.0-24-generic resolved the problem for me.""
That is true for my Asus N53SV laptop."
1752772,2018-12-13 13:23:12 UTC,Also happens with driver=r8152 driverversion=v1.09.9. I'm on an Ubuntu dell xps-13 and I'm using a dock station where the ehternet cable is wired.
1752772,2018-12-08 20:02:59 UTC,also occurs with sky2 driver
1752772,2018-11-20 13:53:55 UTC,"I have solved this for my laptop, in 2 stages."
1752772,2018-11-19 17:23:57 UTC,"I have the same problem on my bionic, and now cosmic, laptop."
1752772,2018-10-23 05:05:12 UTC,"rtimai,"
1752772,2018-10-21 07:56:04 UTC,https://askleo.com/why-does-my-network-not-work-after-resuming-from-standby/
1752772,2019-05-01 18:08:31 UTC,"My HP ProBook 6540b has the following hardware:
  *-network
       description: Ethernet interface
       product: 88E8072 PCI-E Gigabit Ethernet Controller
       vendor: Marvell Technology Group Ltd.
       physical id: 0
       bus info: pci@0000:45:00.0
       logical name: ens1
       version: 10
       serial: 70:5a:b6:b2:9f:50
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full ip=192.168.1.23 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:29 memory:d0500000-d0503fff ioport:2000(size=256) memory:d0520000-d053ffff"
1752772,2018-12-13 14:43:33 UTC,"Olivers, please file a new bug as r8151 is a completely different device."
1752772,2019-06-02 20:09:45 UTC,"Im having the same bug in Kubuntu 19.04  Kernel 5.0.0-15-generic
Using the following commands fixes the problem till next suspend"
1752772,2018-10-21 07:36:57 UTC,@kaihenfeng: I don't understand. Why should my case be a new bug?
1752772,2019-07-30 21:42:36 UTC,"Since changes were introduced with 4.15.0-24, the r8169 driver becomes unusable on x86 machines (16.04 and 18.04 distributions). The device is always in link down state."
1752772,2020-11-13 12:44:17 UTC,Is anything going on with this? It's been quite a while. I recently retested and the r8169 still will not wake for 80+ seconds upon wake.
1752772,2020-08-23 23:51:46 UTC,"I tried adding the module to MODULES_WHITELIST and the prefix to SKIP_INTERFACES to my acpi-support...no dice, still takes approx 80 seconds before the interface is brought back up."
1752772,2020-08-08 12:40:21 UTC,Perhaps should have added more info as I didn't notice someone with a different adapter posting before me which may lead people to think I am chiming in about the r8152 rather than the r8169.
1752772,2020-08-04 08:11:35 UTC,"I'm affected too. Noticed a few months back after updates resuming from suspend became obnoxiously slow, almost 2 minutes to resume the network interface. Meanwhile the system is trying to remount network drives and failing because there is no network so clearly the system isn't in sync with itself. Super obnoxious!"
1752772,2020-05-26 05:23:19 UTC,"Mark,"
1752772,2020-05-26 03:41:12 UTC,"same problem here with r8152 on 19.10 (Eoan Ermine) kernel 5.0.0-1030-oem-osp1
the modprobe -r / -i trick fixes it when resuming from suspended state.
laptop is a Dell XPS 13 7390 but the wired ethernet device is on a TB16 dock so lshw shows its on a usb bus rather than pci -
  *-network:2
       description: Ethernet interface
       physical id: 3
       bus info: usb@6:1.2
       logical name: enx98e743d454f3
       serial: 98:e7:43:d4:54:f3
       size: 1Gbit/s
       capacity: 1Gbit/s
       capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.09.9 duplex=full ip=192.168.10.90 link=no multicast=yes port=MII speed=1Gbit/s"
1752772,2020-05-11 21:21:16 UTC,"Seeing this with r8152 on 20.04 (Regolith 1.4) with kernel 5.4.0-29
Will try reloading the driver after my next resume."
1752772,2020-03-15 07:30:20 UTC,"@edwin, this takes one full minute to complete, which kind of defeats the purpose of suspending. I could almost do a full cold boot in that time."
1752772,2020-02-04 10:07:39 UTC,Simply run: sudo /etc/init.d/network-manager restart. Then the network comes back.
1752772,2019-12-02 18:17:06 UTC,I am also affected by this bug.
1752772,2019-10-01 04:14:56 UTC,"Can you please test versions >= 5.0.0-30.32? Particularly,
commit 67d0bc70365cc6936255914e900a1362c608a381
Author: Heiner Kallweit <email address hidden>
Date:   Sat Jul 27 12:45:10 2019 +0200"
1752772,2019-09-03 09:14:46 UTC,"UPD: The same issue, as described in previous post, reappeared when booting the older 5.0.0-25-generic kernel.
It seems like data race that can be triggered randomly on certain boots."
1752772,2019-09-03 09:00:27 UTC,"After update to kernel 5.0.0-27-generic, it became even worse.
Now Ethernet doesn't work right from the boot, and ""modprobe"" solution has no effect."
1752772,2019-08-27 16:38:56 UTC,"Same here with kernel 5.0.0-25-generic, however the script from post #120 seems to work around this."
1752772,2019-08-25 15:18:24 UTC,"I can confirm the bug affects kernel version 5.0.0-25-generic (at least, on my machine).
The issue started happening after update to this version.
It didn't exist on any 4.18.0 version that I previously had."
1752772,2019-08-23 19:02:08 UTC,"Ricci,"
1752772,2019-08-23 16:06:11 UTC,I'm having the same bug in Kubuntu 19.04.03 Kernel 5.0.0-25-generic
1752772,2019-07-12 23:46:10 UTC,The same problem in Xubuntu 18.04.2 with kernel 4.15.0-54. The fix is:
1752772,2018-05-21 09:02:09 UTC,"Sorry for the late reply.
I should be able to find some time and cherry-pick necessary commits this week."
1752772,2020-08-17 12:23:07 UTC,Am using a Lenovo T440s with 19.10 a docking station and an e1000e driver.
1752772,2018-05-15 19:56:27 UTC,The kernel version 4.17-rc5 is also working for me.
1752772,2018-03-14 23:14:29 UTC,"Yes, with 4.16-rc4 and 4.16-rc5 the problem persists. Every kernel version after 4.15-rc5 is making the computer lose connectivity after returning from suspension."
1752772,2018-03-14 06:46:02 UTC,Do you still have this issue on v4.16-rc4?
1752772,2018-03-06 23:26:18 UTC,"The last version working properly is 4.15-rc4. 4.15-rc5 don't suspend (it fails to) and, starting from 4.15-rc6, this problem with the Ethernet card appears."
1752772,2018-03-06 05:12:16 UTC,Please find the first bad -rc* kernel that has this issue.
1752772,2018-03-05 17:50:02 UTC,"Using the 4.16-rc4 kernel have not made the network card work after suspension and, when I try to wake up the system it is remounting the file system as read only and I can't open Firefox, so I'm reporting from another computer now."
1752772,2018-03-05 10:16:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1752772,2018-03-02 13:09:05 UTC,apport information
1752772,2018-03-19 01:08:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752772,2018-03-02 13:09:04 UTC,apport information
1752772,2018-03-02 13:09:01 UTC,apport information
1752772,2018-03-02 13:08:59 UTC,apport information
1752772,2018-03-02 13:08:58 UTC,apport information
1752772,2018-03-02 13:08:56 UTC,apport information
1752772,2018-03-02 13:08:55 UTC,apport information
1752772,2018-03-02 04:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1752772,2018-05-20 12:01:42 UTC,"So if this is the solution, how long before it gets into the standard update to folks?"
1752772,2018-03-02 13:09:02 UTC,apport information
1752772,2018-03-19 03:07:51 UTC,Can you do a kernel bisection?
1752772,2018-03-04 05:18:25 UTC,you might need to install both: r8168-dkms & libelf.dev (a r8168 report already exist on launchpad)
1752772,2018-03-21 11:20:54 UTC,"Right, I have two desktops that have this card. Let me see if I can reproduce the issue on them."
1752772,2018-05-14 14:09:16 UTC,"This kernel did not work, when waking from suspension it shows the same dmesg messages and only reloading the r8169 module the Ethernet works again."
1752772,2018-03-20 16:42:34 UTC,"The kernels built using this procedure are not working properly. The screen is limited at 640x480 and, after suspending and trying to restore, the screen never turns on again, even trying to change to a tty don't work, so I can't test because I can't see anything."
1752772,2018-05-14 00:29:11 UTC,"Just upgrade from Xubuntu artful to bionic, and just discovered I face the same issue."
1752772,2018-05-11 17:30:53 UTC,The kernel version 4.17-rc4 is working for me.
1752772,2018-05-11 09:01:52 UTC,"From http://kernel.ubuntu.com/~kernel-ppa/mainline/:
works: v4.17-rc1, v4.17-rc3, v4.17-rc4   (-rc2 not tested, but I assume it works)
fails: v4.16.7"
1752772,2018-05-11 05:17:53 UTC,"On 11/05/18 04:47, Kai-Heng Feng wrote:

> Can you try v4.17-rc4? There are several genirq fixes.
>


@ kai.heng.feng - that appears to work for me here"
1752772,2018-05-11 03:47:11 UTC,Can you try v4.17-rc4? There are several genirq fixes.
1752772,2018-04-29 08:15:36 UTC,"I forgot this yesterday: I accidentally compiled git master HEAD of that repo first. It worked fine, so something fixed this bug between v4.16.5 and 46dc111dfe47. If required I can try to bisect, but it will take a while, my CPU is almost 10 years old (takes 1+ hour to compile the kernel). I guess I could speed this up by using the pre-compiled debs to find a smaller range of commits first."
1752772,2018-05-14 08:08:12 UTC,"Please try this kernel, I pulled the genirq fixes."
1752772,2018-04-27 21:57:29 UTC,"With a different install of Bionic in my notebook, the problem is happening too. This appears on dmesg:"
1752772,2018-04-12 06:16:19 UTC,"Okay, can you use the patch [1] and attach dmesg after resume?"
1752772,2018-04-12 06:01:14 UTC,i just installed the latest mainline kernel available in the mainline ppa which was 4.16.1-041601-generic_4.16.1-041601.201804081334 and the problem is just the same.
1752772,2018-04-12 05:31:33 UTC,Can you try latest mainline kernel again? At least the issue is gone for me with latest mainline kernel.
1752772,2018-04-07 06:49:57 UTC,"just testing ubuntu 18.04 beta 2 and have this exact same problem. removing and reloading the r8169 module fixes the problem, but i think it's a serious bug if networking is completely lost on every system suspend..."
1752772,2018-04-28 22:26:41 UTC,"I cloned git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack and checked out tag v4.16.5, applied the 6 patches listed at the top of http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.5/ and the one debug patch at https://lkml.org/lkml/2018/4/3/136."
1752772,2018-03-30 19:06:41 UTC,https://lkml.org/lkml/2018/3/30/508
1752772,2018-03-30 18:51:35 UTC,This is the bad commit:
1752787,2018-03-02 11:32:18 UTC,"- confirmed on Windows 10, Inkscape 0.92.2 (6c06d47, 2018-02-06)
- confirmed on Windows 10, Inkscape 0.92+devel (9d6b0e8, 2018-02-18)"
1752787,2018-03-02 11:36:35 UTC,"attached is the backtrace from Inkscape 0.92.2 (6c06d47, 2018-02-06)"
1752787,2019-12-28 23:24:00 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1752791,2018-03-02 11:46:16 UTC,"have you tried the following?
- with the text tool selected there is a box at the top with a tip that says ""Spacing between baselines"". It currently reads 150% in the attached screenshot."
1752791,2018-03-02 12:17:28 UTC,I hadn’t noticed that – thanks a lot! I was looking in the dialogs and completely overlooking the toolbars.
1752791,2018-03-02 12:21:44 UTC,I’ve now changed the bug title according to my last comment. The spacing settings plus text path offset might be suited for a fourth tab in that Text and Fonts dialog.
1752791,2020-09-10 14:01:16 UTC,Closing because INVALID: undefined request.
1752791,2020-09-10 14:27:26 UTC,What is undefined about this request? I changed the title of this big to say quite precisely what the request is. It still applies to a current version of Inkscape.
1752791,2020-09-10 14:34:22 UTC,"Ah, okay, maybe I should move this to Gitlab ..."
1752800,2018-03-02 13:00:32 UTC,Unless there has been a change of heart in the past six years
1752800,2018-03-05 13:14:27 UTC,"Hi Ra,"
1752807,2018-03-05 02:51:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752820,2018-03-02 15:23:20 UTC,"Ah, I figured it out. You're looking at the py3 version, which wasn't written by me."
1752820,2018-03-02 14:56:59 UTC,"I don't seem to be able to paste from another app at all in Pygame (on Linux), so I guess that's not been properly tested."
1752820,2018-03-02 23:51:45 UTC,"print(pygame.scrap.get(SCRAP_TEXT)) works fine on windows.
thanks"
1752823,2018-07-21 19:01:11 UTC,I have the same problem. Using Ubuntu Mate 18.04. The Pantheon theme.
1752823,2020-12-08 21:42:57 UTC,"It's 2020 and I have the same problem, icons unlock on every restart. I would change docks, but I like this one."
1752823,2018-06-08 10:26:11 UTC,"Same problem on Debian 9 - 64 bits with XFCE desktop.
Plank installed from apt-get version 0.11.3-2.
Any solution?"
1752824,2018-03-02 11:16:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549182"
1752824,2018-03-20 02:00:19 UTC,"Reviewed:  https://review.openstack.org/549182
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=87a6bb4184efb0e7da2d8a7ad7f189a3bc4cf03e
Submitter: Zuul
Branch:    master"
1752824,2018-04-20 13:14:01 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1752824,2018-08-13 11:55:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/591365"
1752824,2018-09-19 16:21:02 UTC,"Reviewed:  https://review.openstack.org/591365
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=997b38503b1ced8acab031bbaa24f3d82f1c6336
Submitter: Zuul
Branch:    stable/queens"
1752824,2018-09-24 14:46:58 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1752826,2019-06-07 20:27:44 UTC,"Ocata is EOL, though this was likely due to this THT change -> https://review.opendev.org/#/c/442024/1/puppet/services/neutron-base.yaml"
1752829,2018-11-10 14:16:12 UTC,"Created attachment 142424
dmesg output"
1752829,2018-03-04 10:53:37 UTC,apport information
1752829,2018-03-04 10:53:42 UTC,apport information
1752829,2018-03-05 10:52:48 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1752829,2018-03-21 13:25:14 UTC,"I can see that your chip matches this condition:
""rdev->pdev->revision == 0x83"""
1752829,2019-10-27 16:24:23 UTC,"Why is the core clock for this GPU (HAINAN) and what seems to have codename OLAND hard-coded anyway? The other GPUs do not have their clocks hard-coded, which allows them to be modified without modifying and rebuilding the module."
1752829,2018-11-09 15:46:26 UTC,A number of boards had stability issues at the default clocks. Please attach your dmesg output.
1752829,2018-11-10 14:17:34 UTC,"Comment on attachment 142424
dmesg output"
1752829,2018-03-04 10:53:29 UTC,apport information
1752829,2019-11-19 09:32:47 UTC,-- GitLab Migration Automatic Message --
1752829,2018-11-09 14:28:45 UTC,"Created attachment 142420
root/drivers/gpu/drm/radeon/si_dpm.c with 1 line modified"
1752829,2018-03-04 10:53:27 UTC,apport information
1752829,2018-03-21 14:53:34 UTC,Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:
1752829,2018-03-04 10:53:21 UTC,apport information
1752829,2018-03-04 10:53:19 UTC,apport information
1752829,2018-03-04 10:53:16 UTC,apport information
1752829,2018-03-04 10:53:15 UTC,apport information
1752829,2018-03-04 10:53:14 UTC,apport information
1752829,2018-03-04 10:53:13 UTC,apport information
1752829,2018-03-04 10:53:25 UTC,apport information
1752829,2018-03-04 10:53:10 UTC,apport information
1752829,2018-03-04 10:53:06 UTC,apport information
1752829,2018-03-04 10:53:02 UTC,apport information
1752829,2018-03-04 10:53:01 UTC,apport information
1752829,2018-03-03 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1752851,2018-08-25 23:38:41 UTC,thx for the report!
1752851,2020-03-17 22:44:27 UTC,Fixed in boot-repair - 4ppa69
1752857,2018-04-12 12:30:28 UTC,I am having the exact same issue with kernel 4.15.16 from the mainline kernel ppa sing make-kpkg.
1752857,2018-04-12 12:31:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752858,2018-03-14 08:58:25 UTC,"IP address and route are added by kuryr-cni, instead of dnsmasq by dhcp-agent.
But if subnets are shared with vm, dhcp should be enabled."
1752858,2018-03-21 18:04:28 UTC,You can enable dhcp. You only need to make sure that the Kubernetes service IP will be taken by a fake service and for the neutron subnet allocation pools to take it into account (that last part should be automatic).
1752860,2019-12-03 20:19:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752860,2019-12-03 20:21:15 UTC,I have the same problem. Here are my CUPS logs.
1752860,2020-01-15 01:42:39 UTC,"I was able to get my LaserJet 1020 working by following the instructions at the website below. Use the command ""sudo system-config-printer"" instead of ""sudo gnome-cups-manager""."
1752860,2020-11-28 23:26:31 UTC,1) First install hplip:
1752876,2018-07-07 18:52:12 UTC,"sfdisk has to be run as root but it's fine because KPM KAuth helper can run commands as root. On the other hand, libparted was a library."
1752876,2018-07-07 18:37:53 UTC,"Say, how does moving to sfdisk help?  It still has to be run as root.  You might consider using partman, which is the libparted wrapper program that allows debian-installer to make libparted calls from bash scripts.  It takes commands and gives replies via a pair of named pipes."
1752876,2018-07-07 18:55:00 UTC,"Anyway, we can probably close this bug. It's not too late for 18.04 and 18.10 has util-linux 2.32 anyway."
1752876,2018-07-07 18:55:54 UTC,s/It's not too late for/It's now too late for/
1752903,2019-04-16 08:50:52 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/599494
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1752903,2019-04-16 08:50:39 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1752903,2018-09-04 05:23:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599494"
1752903,2018-03-02 15:56:10 UTC,please be careful when fixing this. there is networking-midonet fip64 extension. https://developer.openstack.org/api-ref/network/v2/index.html#fip64
1752908,2018-03-02 15:42:42 UTC,apport information
1752908,2018-03-02 15:42:43 UTC,apport information
1752908,2018-03-02 15:42:44 UTC,apport information
1752908,2018-03-02 15:42:45 UTC,apport information
1752908,2018-03-02 18:08:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752911,2018-03-02 15:48:49 UTC,https://review.openstack.org/548594
1752911,2018-03-14 18:43:23 UTC,I'm good with this.
1752911,2018-03-14 18:45:35 UTC,"+1, let's do it."
1752911,2018-08-09 15:27:59 UTC,This issue was fixed in the openstack/virtualbmc 1.4.0 release.
1752916,2018-03-02 15:57:43 UTC,"Desktop launcher should then read ~/.config/user-dirs.dirs and, if it has access to the real user home, redefine the various XDG_* dirs with those paths."
1752916,2019-10-15 11:09:57 UTC,I agree that it would be good if part of the execution chain could read the XDG directories and at least set the variables.
1752925,2018-03-05 15:33:31 UTC,I think issues like this one worth adding a day2 tag. I'm not sure the failures like described may be detected for the deployment time. So it seems like a subject of either the consequent future runs of 'openstack overcloud deploy' (or undercloud install) OR something like cluster operators coming from Kubernetes with the adoption of the latter as well...
1752925,2018-03-05 15:35:31 UTC,"...basically, for k8s, the problems like that is already solved by simple health checks and kubelet restarting the failing ones. So cluster operators are mostly the case for HA statefull services to extend that logic with a proper orchestrating/roll-outs of restarts et al."
1752925,2018-09-28 16:36:16 UTC,We had this and then had to revert https://review.openstack.org/#/c/584288/
1752925,2018-10-02 13:26:18 UTC,What was the reason for the revert?
1752925,2018-10-02 16:21:04 UTC,because https://bugs.launchpad.net/tripleo/+bug/1782598
1752925,2021-02-17 17:06:54 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1752929,2018-03-02 20:16:57 UTC,"Boy, you don't make it easy for me to assist you getting closer to this issue."
1752929,2018-03-02 17:01:59 UTC,"I cannot reproduce this error, neither with your compiler version (GCC v6.3) nor with newer (more picky) GCC v7 and clang compilers. However, I have a hunch. Does the attached patch help?"
1752929,2018-03-03 17:33:18 UTC,Replaced the posted (and probably useless) master-based patch with a v2.0.0-based patch (after reproducing the fixed-in-master problem using v2.0.0 sources on a 32bit platform).
1752929,2018-03-03 17:43:12 UTC,"> Boy, you don't make it easy for me to assist you getting closer to this issue.
"
1752929,2018-03-03 20:06:34 UTC,Thanks Alex! You're awesome. Thanks for your patience. This patch solved the issue!
1752942,2019-01-07 13:29:02 UTC,"Ignore me, this is still the case - OSDs are configured with Rack + Row but the monitors only modify the crushmap to utilize rack"
1752942,2019-01-07 13:27:50 UTC,This has already been resolved by configuring it as rack+row
1752946,2018-03-05 18:07:30 UTC,"I really tried, but it does not do: I do not get a proposed kernel."
1752946,2018-03-03 05:03:13 UTC,apport information
1752946,2018-03-05 10:36:29 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1752946,2018-03-03 05:03:11 UTC,apport information
1752946,2018-03-09 14:00:41 UTC,"Sorry, I do not find a way to get proposed to work. So I cannot complete your request."
1752946,2018-03-03 05:03:08 UTC,apport information
1752946,2018-04-04 16:59:11 UTC,-38 kernel does not do any better.
1752946,2018-04-04 17:38:28 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1752946,2018-04-04 19:29:06 UTC,"As you can read in comments #18 an #19 I cannot activate proposed.
If you can tell me a way to get to activate proposed, I'm willing to do so."
1752946,2018-06-17 16:53:44 UTC,For me the bug is gone. I updated to bionic and tested a while. No mor problems until now.
1752946,2018-03-14 19:57:15 UTC,"Just updated to 4.13.0-37 kernel, problem remains"
1752946,2018-03-03 05:03:07 UTC,apport information
1752946,2020-01-09 06:42:02 UTC,Closing as per comment in #24
1752946,2018-03-03 05:03:04 UTC,apport information
1752946,2018-03-03 05:03:05 UTC,apport information
1752946,2018-03-02 20:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1752946,2018-03-03 05:02:56 UTC,apport information
1752946,2018-03-03 05:02:57 UTC,apport information
1752946,2018-03-02 20:19:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1752946,2018-03-03 05:02:59 UTC,apport information
1752946,2018-03-03 05:03:00 UTC,apport information
1752946,2018-03-03 05:03:02 UTC,apport information
1752946,2018-03-03 05:03:04 UTC,apport information
1752946,2018-03-03 05:02:58 UTC,apport information
1752956,2018-03-02 19:00:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1752956,2018-04-17 20:10:40 UTC,There's a WIP branch here: https://github.com/CanonicalLtd/netplan/pull/18
1752956,2018-09-07 04:13:34 UTC,"I have similar issue, and it got ok after setting the same column alignment for the keyword of ethernets"
1752957,2018-03-27 19:09:15 UTC,"Turns out this is _not_ desired behavior, so using this bug to track the fix."
1752957,2018-03-22 16:50:06 UTC,"Kyle, this is solved with the latest 2.40 (to be released) version, right?"
1752957,2018-03-26 17:31:38 UTC,"Indeed, the traceback no longer occurs. However, there's still a behavior change when compared to 2.35, which errors out with ""classic confinement requires the core snap to be installed. Install it by running `snap install core`."" 2.40 just happily uses '/snap/core/current/lib64/ld-linux-x86-64.so.2'. Is that desired? I'll set back to New just in case, but if this is working as desired, feel free to set to Fix Committed."
1752960,2018-04-22 16:16:59 UTC,"Not sure what is going on here, but the workaround no longer seems to work."
1752960,2018-05-01 22:31:07 UTC,And what is /usr/sbin/grafana-server?
1752960,2021-02-22 19:12:36 UTC,Since we provide the option to use ports other than 3000 (specifically 80) we should support it and the charm does whatever is required if grafana can't support it directly.
1752960,2020-04-01 22:32:05 UTC,"I believe this is still a valid bug. While the default is to use port 3000, sometimes it's necessary to use port 80 such as environments where there are restrictive firewall rules."
1752960,2018-03-27 16:12:01 UTC,"If the /usr/sbin/grafana-server binary is replaced, the setcap would need to be executed again."
1752960,2020-03-03 06:32:13 UTC,"Grafana now listens on port 3000, and works fine - will mark invalid."
1752960,2018-03-27 14:58:29 UTC,"Nobuto, I agree - good question on why port 80. Our foundation bundle
used that; I changed it back to 3000 after hitting this bug."
1752960,2018-03-27 15:20:16 UTC,"We casually set and tried port 80 at the beginning and it didn't work because the ""port"" option was no-op[1]. The no-op looks fixed, but now we realized that running it with port 80 requires more privilege since grafana wasn't running as root. So I don't think there is a real necessity to use privileged ports from field point of view, other than clarifying the option is only for >1024."
1752960,2018-03-26 09:55:33 UTC,"After fixing a typo in my patch and testing it locally, I can confirm this works. This feels kind of kludgey but it does indeed solve the problem. If someone can point me to a workflow for submitting a pull request for a charm, I'd be happy to commit it."
1752960,2018-03-21 14:33:53 UTC,I wrote a quick patch to make a setcap system call immediately after the apt install but haven't had time to test it.
1752960,2018-03-05 21:03:03 UTC,"vern's work shows this is a problem with file capabilities, perhaps in the upstream grafana packaging?"
1752960,2018-03-05 20:46:09 UTC,This can be reproduced using lxd provider:
1752960,2018-03-02 23:33:03 UTC,I was able to get grafana green by doing `juju ssh grafana/0` and executing:
1752960,2018-03-27 14:11:09 UTC,Does that capability survive even after grafana .deb package gets updated? Or is it reset after the update?
1752961,2018-10-11 03:02:39 UTC,fdea70d has the bug.
1752961,2018-10-01 17:54:07 UTC,"I built the next test kernel, up to the following commit:
fdea70d26a471e002f2afc3a48821323b699f1e6"
1752961,2018-09-25 03:33:22 UTC,d60dafd does NOT have the bug.
1752961,2018-09-11 17:51:12 UTC,"I built the next test kernel, up to the following commit:
d60dafdca4b463405e5586df923f05b10e9ac2f9"
1752961,2018-09-11 04:07:53 UTC,1c8c5a9 has the bug.
1752961,2018-09-05 13:35:15 UTC,"I reviewed the btrfs commits in v4.18-rc1, but the are quite a few of them.  We should perform a ""Reverse"" bisect to identify the correct on that fixes this bug."
1752961,2018-09-04 06:30:02 UTC,Both 4.18-rc1 and 4.18-rc4 do NOT have the bug.
1752961,2018-08-28 15:37:59 UTC,Thanks for testing.  We need to narrow down the specific version of 4.18 that has the fix.  Can you test the following kernels:
1752961,2018-08-28 05:27:53 UTC,Both 4.15.18 and 4.17.17 have the bug.
1752961,2018-08-16 05:23:31 UTC,6836796 does NOT have the bug.
1752961,2018-08-17 19:09:13 UTC,It looks like 4.18 does not have the issue.
1752961,2018-08-16 15:33:58 UTC,"Commit 362f6729cbb1d6bbab59e069f19441b0622ff7ec was reported as the first bad commit.  However, this commit is a merge tag, so we'll need to bisect into that merge."
1752961,2018-07-24 09:34:09 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1752961,2018-08-15 15:31:23 UTC,"I built the next test kernel, up to the following commit:
6836796de4019944f4ba4c99a360e8250fd2e735"
1752961,2018-08-15 05:55:09 UTC,362f672 has the bug.
1752961,2018-08-13 19:56:11 UTC,The latest test kernel is for commit 362f6729cbb1d6bbab59e069f19441b0622ff7ec
1752961,2018-08-13 18:13:31 UTC,Sorry for the delay.  I missed the email regarding you're test results of the last kernel.
1752961,2018-08-10 16:09:30 UTC,Any new build to test?
1752961,2018-08-21 16:02:03 UTC,That's good news.  We now have to identify the fix in 4.18 and ensure it is applied to Ubuntu.  Can you test the following two upstream stable kernels to see if the fix was already sent to stable:
1752961,2018-10-11 19:54:30 UTC,"I built the next test kernel, up to the following commit:
6a8b25abf1b79db6877645335c73ad6a5061d9b0"
1752961,2018-12-20 21:34:09 UTC,"I did my upgrade from Debian stable to stretch-backports and therefore from 4.9 to 4.18 today.
Wrong distribution, I know ;-)"
1752961,2018-10-15 16:36:43 UTC,"I rebuilt the kernel, so they should be there now:
http://kernel.ubuntu.com/~jsalisbury/lp1752961"
1752961,2020-11-09 08:10:17 UTC,"I upgraded from 16.04 to 18.04 (from kernel 4.4.0-193-generic to 4.15.0-122-generic) and I had this exact issue. Same HP Microserver Gen 8 as the others, probably there's something in their motherboard that makes SATA disks discovery particularly slow, and the kernel (or initrd scripts harness?) doesn't _really_ wait for /dev to populate properly."
1752961,2018-07-20 13:51:07 UTC,878c33a does NOT have the bug.
1752961,2019-01-15 06:43:05 UTC,"I just updated to Debian ""4.19.0-0.bpo.1-amd64 #1 SMP Debian 4.19.12-1~bpo9+1 (2018-12-30) x86_64 GNU/Linux"""
1752961,2019-01-01 19:23:10 UTC,"Dear Christian,
Thank you for your reply.
I took another route which worked.
First i booted with kernel 4.4 normally.
I edited /usr/share/initramfs-tools/scripts/local-premount/btrfs by adding sleep=5 before ""/bin/btrfs device scan"" line, then i ran the following commands:
update-initramfs -u
update-grub
grub-install /dev/sda
and then rebooted and it works :)"
1752961,2019-01-01 15:52:36 UTC,"Hi Bogdan!
Sorry to hear, that it doesn´t work for you.
I fear that you did add the parameter in the same way then I did. So there might be some other difference."
1752961,2019-01-01 09:25:03 UTC,"Dear Christian,
Can you please detail a little how/where you added the rootdelay parameter.
I am facing the same problem with a 4 drive raid1 on a HP MicroServer Gen8, on update from Ubuntu server 16.04 to 18.04 (kernel 4.4 to kernel 4.15).
I tried to add the parameter to /etc/default/grub in both GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX= with no success, and then update-grub, grub-install /dev/sda.
sda is 3tb hdd gpt
I tried to increase rootdelay up to 90 still no boot.
On boot i can confirm that the rootdelay is added to commandline if i try to edit the entry.
For now i am booting with old 4.4 kernel, but i dont't think this is ok in the long run.
Thanks in advance."
1752961,2018-12-07 19:00:58 UTC,v4.17 final has the bug.
1752961,2018-12-03 15:04:26 UTC,Thanks for retesting.  Can you test v4.17 final?  It is available from:
1752961,2018-10-12 22:16:22 UTC,The packages appear to still be the build from 10/01.
1752961,2018-11-28 08:23:48 UTC,"I retested the last 2 builds from the original bisection, and I'm pretty confident that the results were correct:
362f672 has the bug.
6836796 does NOT have the bug."
1752961,2018-11-16 15:11:57 UTC,We may have to go back and retest for the bisect then.
1752961,2018-11-15 04:55:26 UTC,"It looks like I made a mistake on a previous build.  I retested d60dafd, built on 20180911, and it actually does have the bug.  Sorry!"
1752961,2018-11-15 04:30:06 UTC,18f1837 has the bug.
1752961,2018-11-14 19:16:47 UTC,"I built the next test kernel, up to the following commit:
18f1837632783fec017fd932a812d383e3406af0"
1752961,2018-11-13 06:05:45 UTC,Agreed.  68cc38f has the bug.
1752961,2018-11-11 19:48:25 UTC,68cc38ff33f38424d0456f9a1ecfec4683226a7e has the bug.
1752961,2018-10-23 18:09:11 UTC,"I built the next test kernel, up to the following commit:
68cc38ff33f38424d0456f9a1ecfec4683226a7e"
1752961,2018-10-23 05:25:22 UTC,6a8b25a has the bug.
1752961,2018-11-28 07:14:37 UTC,Mainline 4.20-rc2 has the bug.
1752961,2018-07-17 15:39:13 UTC,"I built the next test kernel, up to the following commit:
878c33a78811f90795f17333bc3a7c819a1589a7"
1752961,2018-05-06 00:54:24 UTC,apport information
1752961,2018-07-05 15:15:35 UTC,"I built the next test kernel, up to the following commit:
409acdd0412e9343095d965a9228f6e6a83a416f"
1752961,2018-05-28 23:48:01 UTC,"FWIW, v4.12.14 also works."
1752961,2018-05-28 23:13:58 UTC,v4.12 Final works.  v4.13-rc1 does not.
1752961,2018-05-22 16:28:24 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the last kernel that did not have this issue.
1752961,2018-05-14 00:01:53 UTC,This issue started with the version 4.13 series.  The last version that did not have the issue is 4.11.0-14.
1752961,2018-05-07 16:07:58 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1752961,2018-05-06 00:54:42 UTC,apport information
1752961,2018-05-06 00:54:39 UTC,apport information
1752961,2018-05-06 00:54:37 UTC,apport information
1752961,2018-05-06 00:54:35 UTC,apport information
1752961,2018-05-06 00:54:33 UTC,apport information
1752961,2018-05-06 00:54:30 UTC,apport information
1752961,2018-05-06 00:54:29 UTC,apport information
1752961,2018-05-06 00:54:26 UTC,apport information
1752961,2018-07-06 22:26:02 UTC,409acdd does NOT have the bug.
1752961,2018-05-06 00:54:22 UTC,apport information
1752961,2018-05-06 00:54:19 UTC,apport information
1752961,2018-05-06 00:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1752961,2018-05-30 15:09:06 UTC,I started a kernel bisect between v4.12 final and v4.13-rc1. The kernel bisect will require testing of about 7-10 test kernels.
1752961,2018-05-31 04:50:54 UTC,e5f76a2e0e84ca2a215ecbf6feae88780d055c56 (4.12.0-041200.201805301435) does not work.
1752961,2018-05-05 23:39:27 UTC,This problem is still present as of 4.15.0-20.
1752961,2018-05-31 12:01:25 UTC,"I built the next test kernel, up to the following commit:
1849f800fba32cd5a0b647f824f11426b85310d8"
1752961,2018-07-04 23:35:11 UTC,0cf9f50 does NOT have the bug.
1752961,2018-07-03 14:41:04 UTC,"I built the next test kernel, up to the following commit:
0cf9f5096da2200b52cee0e38139c99c4fc0151c"
1752961,2018-07-03 13:47:11 UTC,c94dc34 does NOT have the bug.
1752961,2018-07-02 21:35:17 UTC,"I built the next test kernel, up to the following commit:
c94dc34f771a25b8c3e0955147fdc4f5e3d79908"
1752961,2018-06-29 15:37:52 UTC,"I built the next test kernel, up to the following commit:
44c891af576997763d1d4c790d50d10db9eff00f"
1752961,2018-06-29 06:33:04 UTC,24040a5 does NOT have the bug.
1752961,2018-06-27 15:48:52 UTC,"I built the next test kernel, up to the following commit:
24040a58379e2f2fa6aa9466911b758073b6bdfa"
1752961,2018-06-22 23:53:37 UTC,4422d80 does NOT have the bug.
1752961,2018-07-02 14:57:03 UTC,44c891a does NOT have the bug.
1752961,2018-06-20 04:54:13 UTC,cbf4b38 does NOT have the bug.
1752961,2018-06-20 18:04:17 UTC,"I built the next test kernel, up to the following commit:
4422d80ed7d4bdb2d6e9fb890c66c3d9250ba694"
1752961,2018-05-31 15:04:47 UTC,1849f80 has the bug.
1752961,2018-06-12 20:11:25 UTC,Sorry for the delay.
1752961,2018-06-14 22:02:14 UTC,cbcd4f0 has the bug.
1752961,2018-05-31 04:54:45 UTC,I guess it's less ambiguous to say that e5f76a2 has the bug.
1752961,2018-06-16 14:01:30 UTC,1b044f1 does NOT have the bug.
1752961,2018-06-18 17:59:30 UTC,"I built the next test kernel, up to the following commit:
cbf4b3867875206aa548a8c6d7c886f3299d619e"
1752961,2018-06-15 16:46:11 UTC,"I built the next test kernel, up to the following commit:
1b044f1cfc65a7d90b209dfabd57e16d98b58c5b"
1752968,2018-12-17 22:10:30 UTC,"My apologies. I was going to create a bug about cursor focus and acquisitions and this bug already existed so I added comment #2.  Now I'll simply amend my comment #7 to agree with the original bug report, same cursor focus as xul."
1752968,2019-04-29 15:36:54 UTC,"I want to add that we are using this branch in production at CW MARS since we upgraded to Evergreen 3.2.4 on April 15, 2019.  I will very likely push the fix to master, rel_3_3, rel_3_2, and rel_3_1 very soon barring any negative feedback in the meantime."
1752968,2018-12-18 16:46:40 UTC,"Thanks, Janet!"
1752968,2018-12-18 16:34:11 UTC,Thank you Janet!
1752968,2018-12-18 16:30:35 UTC,Thank you Jason!!
1752968,2018-12-18 16:25:34 UTC,"Tested Jason's new commit on 3.2. The cursor focus is now in the barcode box with an existing barcode highlighted so that scanning in a new barcode replaces the existing one.
I can sign off on this branch, Janet Schrader, <email address hidden>."
1752968,2018-12-18 15:47:10 UTC,"OK, Janet, thanks for the feedback!"
1752968,2018-12-18 15:20:41 UTC,"This behavior is not the same as the xul client for editing (replacing) the barcode. In xul the focus means the barcode itself is highlighted so scanning in a barcode deletes what's in the box, replacing it with the new barcode. In the web client the cursor focus is in the box at the end of the barcode so scanning a new barcode adds it to the existing one."
1752968,2019-05-01 13:46:12 UTC,Pushed to master and rel_3_1 through rel_3_3.
1752968,2018-12-17 18:46:15 UTC,"Thanks, Christine."
1752968,2018-12-17 17:55:03 UTC,"Janet, the bug description says nothing whatsoever about acquisitions. You mention it in comment #2, but I don't think this bug was originally about acquisitions."
1752968,2018-12-17 17:44:53 UTC,"This bug was to keep the focus in the barcode box when editing items created during acquisitions, not adding new items. The current xul behavior has the cursor focus in the barcode box both when adding or editing items so I see that as the preferred behavior to keep the web client consistent with xul."
1752968,2018-12-17 16:52:50 UTC,"Actually, focusing when the barcode is empty is pretty easy, too, so here's a branch (1 commit) that does that:"
1752968,2018-12-17 16:15:41 UTC,"I have been looking at this. Getting the cursor to always focus in the barcode fields is pretty simple. However, it jumps to the barcode field when editing existing copies, not just when adding new ones. Is that what everyone wants, or should it only autofocus the barcode field when adding a new copy?"
1752968,2018-11-09 00:26:45 UTC,"Bumping this up to Medium, because of the impact you were talking about, Janet."
1752968,2018-10-31 21:40:48 UTC,Added tag regression as this was a function available in the xul client.
1752968,2018-10-05 20:15:45 UTC,"This bug is a major workflow problem for a library doing centralized cataloging for multiple branches. Updating the system generated barcode created in acquisitions to the real item barcode is no longer a simple scan the barcode when opening the item record. It now requires moving to the barcode box and highlighting the  existing barcode, then scanning. Two steps when there used to be none."
1752968,2018-04-30 19:51:41 UTC,"Confirmed 3.1 -- seeing this when I use ""add volumes & copies"""
1752968,2018-12-17 18:24:15 UTC,Hi Jason
1752969,2018-03-02 20:18:21 UTC,"gdal and other geospatial packages are not maintained within Ubuntu. The commit can be cherry-picked into the Debian package, but that doesn't get the fix into Ubuntu."
1752975,2018-08-10 21:39:49 UTC,This issue was fixed in the openstack/bifrost 5.1.0 release.
1752975,2018-04-09 21:17:41 UTC,This issue was fixed in the openstack/bifrost 5.0.1 release.
1752975,2018-03-04 20:29:19 UTC,"This patch resolves my node enrolment problems. I now have entries in ""ironic driver-list"" and ""ironic node-enroll"" runs without error."
1752975,2018-03-04 20:00:19 UTC,"I have a related issue, as posted on openstack-dev at http://lists.openstack.org/pipermail/openstack-dev/2018-March/127886.html . I'll patch in this change and redeploy and see if that helps."
1752975,2018-03-02 20:32:17 UTC,"Looking are the hardware type code, I think cisco types load ok because they support IPMI management interface. Ilo requires the Ilo specific management interface, which is not enabled by default."
1752975,2018-03-02 20:26:43 UTC,"With cisco-ucs-managed and cisco-ucs-standalone added, I now hit this:"
1752975,2018-03-03 21:50:00 UTC,https://review.openstack.org/549318
1752978,2020-06-12 16:52:42 UTC,"I have the same issue, it prints:"
1752985,2020-01-28 08:26:52 UTC,Please ask upstream about such issues!
1752992,2018-03-08 11:41:01 UTC,Let me know if you need any assistance with this.
1752992,2018-03-30 20:03:35 UTC,"Sorry I missed this. I already built Moonshot for Debian, and it seems to work. CHeck this page:
https://wiki.moonshot.ja.net/display/Moonshot/Install+Moonshot+Libraries+on+a+Debian+9+Client"
1753012,2018-03-07 20:12:25 UTC,"StacktraceTop:
 xf86platformProbe () at ../../../../../../hw/xfree86/common/xf86platformBus.c:311
 xf86BusProbe () at ../../../../../../hw/xfree86/common/xf86Bus.c:226
 InitOutput (pScreenInfo=pScreenInfo@entry=0x557c2932e6c0 <screenInfo>, argc=argc@entry=3, argv=argv@entry=0x7ffe64d48138) at ../../../../../../hw/xfree86/common/xf86Init.c:462
 dix_main (argc=3, argv=0x7ffe64d48138, envp=<optimized out>) at ../../../../dix/main.c:197
 __libc_start_main (main=0x557c28f02b80 <main>, argc=3, argv=0x7ffe64d48138, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe64d48128) at ../csu/libc-start.c:310"
1753012,2018-05-22 02:27:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753012,2018-05-22 02:28:26 UTC,"Tracking in:
https://errors.ubuntu.com/problem/e62d193f8a871d8a404be58362b9c1a32852877d"
1753012,2018-08-20 21:16:35 UTC,"A hypothesis was discussed in bug #1753012 that the root cause of this bug was in the kernel, specifically in blk-core.c. The patch was finally merged in kernel version 4.15.0-31-generic. I'm running on 4.15.0-32-generic but the bug is still happening:"
1753022,2018-10-24 09:13:54 UTC,I think this just involves adding the correctly formatted comments.
1753034,2018-03-08 23:48:05 UTC,"StacktraceTop:
 ?? ()
 gs_page_authenticate_cb (dialog=0x563c665ec300, response_type=GTK_RESPONSE_CANCEL, user_data=0x563c643cb2d0) at ../src/gs-page.c:87
 g_cclosure_marshal_VOID__BOOLEANv (closure=<optimized out>, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x563c63b936a0) at ../../../../gobject/gmarshal.c:978
 _g_closure_invoke_va (closure=0x563c63f0d1a0, return_value=0x0, instance=0x563c665ec300, args=0x7ffc07f0cad0, n_params=1, param_types=0x563c63b936a0) at ../../../../gobject/gclosure.c:867
 g_signal_emit_valist (instance=0x563c665ec300, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc07f0cad0) at ../../../../gobject/gsignal.c:3300"
1753050,2018-03-21 13:34:43 UTC,"Make sure your system is up to date.
$ sudo apt update && sudo apt -y dist-upgrade"
1753050,2018-03-22 20:32:48 UTC,"$ dkms list
outputs nothing"
1753050,2018-03-05 16:56:32 UTC,"As told in the description, with kernel 4.4.0-112-generic the outputs are recognized and work fine.
The next kernel I installed was 4.4.0-116-generic with which the bug appears. The bug is not fixed in v4.16-rc4."
1753050,2018-03-22 22:01:37 UTC,"I used ""dkms status"" to get the required information about the module name (nvidia-340) and version (340.104)"
1753050,2018-03-03 08:00:07 UTC,This change was made by a bot.
1753050,2018-03-05 10:53:09 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1753062,2018-04-13 14:53:15 UTC,My wireless mouse has clicking problem after upgraded to 18.04. One click sometimes becomes double click.
1753067,2019-09-16 17:36:55 UTC,Migrated to https://github.com/widelands/widelands/issues/2102
1753068,2019-06-22 04:27:01 UTC,"the rebuild of virt-viewer has successfully built with SPICE_GTK, it should be in the next update run."
1753068,2019-06-21 23:14:55 UTC,"spice-gtk is now up to date in raspbian stretch, I have just scheduled a rebuild of virt-viewer, lets see if it picks spice up without further changes or not (it did on Debian armhf, so i'm hopeful)."
1753068,2019-06-21 22:45:57 UTC,"anonscm is gone, replaced by salsa, but in any case what is on there is of limited relevance to fixing stuff in an existing stable (and soon to become oldstable) release."
1753068,2019-06-21 21:45:37 UTC,BTW raspbian buster contains a virt-viewer that appears to be built against SPICE-GTK.
1753068,2019-06-21 19:25:11 UTC,@peter: I was building everything from debian sources from anonscm. I assume it was something with the particular versions that may be fixed in the newer ones.
1753068,2019-06-21 13:05:19 UTC,I was able to hackishly get it working using Debian Sid packages to fill in the gaps. There's no audio and no ability to map USB devices but it works.
1753068,2019-06-21 21:05:49 UTC,@jjakob
1753068,2019-06-21 08:31:43 UTC,"Is it still not fixed? I gave up on fixing it that time after building everything and installing it, there was a lot of graphics glitches, missing graphics etc. that would require debugging the graphics subsystem and fixing bugs, which I have zero experience in. I was testing with the raspbian hardware accelerated graphics (itself experimental at the time) as the sw accelerated was unusably slow. I suspect it has something to do with the combination of the two. Since some time has passed and things may be different now, it would be good to recompile it and check if anything's improved. Unfortunately I don't have the time to do that right now."
1753068,2019-06-20 23:24:57 UTC,can someone please fix this in the base raspbian? I doubt people who are new to linux will have any knowledge or even know where to begin on rebuilding packages.
1753068,2018-03-22 01:09:09 UTC,"Patch for building the dependency, spice-gtk from https://anonscm.debian.org/git/collab-maint/spice-gtk.git. This disables werror to fix the cast errors and disables building html docs to fix a file not found error during dh_install. Tested on spice-gtk 0.34-1.
Apply the patch, commit, (optionally run ""debchange -l +gitxyz"") and build with ""dpkg-buildpackage -rfakeroot -us -uc"".
You need to build and install libspice-protocol-dev from https://anonscm.debian.org/git/collab-maint/spice-protocol.git before building spice-gtk."
1753068,2018-03-22 00:56:48 UTC,"Attached is a patch for building virt-viewer on armhf with spice-gtk enabled.
Applies to both source obtained via apt-get source or from https://salsa.debian.org/libvirt-team/virt-viewer.git.  Tested on virt-viewer 5.0-1 and 6.0-2.
Apply the patch, commit and build using ""dpkg-buildpackage -rfakeroot -us -uc --build=binary"".
Before building virt-viewer you need to build spice-gtk and spice-protocol from git as virt-viewer requires libspice-client-glib-2.0-8 (>= 0.33) but the distribution version is 0.32."
1753068,2018-03-06 21:02:58 UTC,"So I tried to build virt-viewer from source. However, the source package in raspbian archives required newer spice-client-glib/gtk than that available in the archives:"
1753068,2019-06-21 11:58:07 UTC,"I'm not sure where your builds are picking up the -Werror from, that doesn't seem to be a problem in any of our builds. The problem in spice-gtk is a missing build-dependency, i'll get that dealt with so raspbian stretch's spice-gtk package is back in sync with Debian stretch's one."
1753069,2018-03-08 14:09:01 UTC,What release is this happening on? Do you have the latest fixes?
1753069,2018-03-21 02:47:28 UTC,I running on devstack master. I will look into the db and get back to you.
1753070,2019-10-01 13:36:14 UTC,We discussed that in the desktop team meeting and don't feel it's important enough to use direct release tracking without having an owner so deleting the stable lines for now
1753070,2020-04-05 21:48:26 UTC,"@padmahas, thank you for your detailled comment. That is a different issue than the one described there (which has been fixed now), could you open a new report for it?"
1753070,2020-04-05 03:22:26 UTC,"Hello @Sebastein,"
1753070,2020-03-19 07:34:40 UTC,This bug was fixed in the package gnome-control-center - 1:3.36.0-0ubuntu3
1753070,2020-04-07 08:10:06 UTC,"Sure @Sebastien,"
1753070,2020-01-24 10:35:03 UTC,Bug still present in the current devel version of Focal Fossa.
1753070,2019-10-26 10:07:53 UTC,"I was facing the same problem
And after scavenging through the internet
I found a fix"
1753070,2019-05-23 08:47:43 UTC,"This is still an issue in Disco, with a difference: there is no ""default"" button anymore in the Sound settings, only Bark|Drip|Glass|Sonar, none of which is the original Ubuntu bell from the Yaru theme."
1753070,2018-10-04 21:10:15 UTC,Having the same issue here.
1753070,2018-12-16 13:14:48 UTC,"As a temporary workaround, set /org/gnome/desktop/sound/theme-name to the default ""Yaru"". You can use the following command for this:"
1753070,2018-12-07 07:55:41 UTC,"I've also experienced the issue. With Ubuntu 18.04 LTS, when I first started tinkering with the sound settings, the default turned to a drip, and I've used the bark-replacement method that mcbruno712 suggested, above, as a temporary workaround."
1753070,2018-11-04 20:36:13 UTC,"Actually, I forgot to mention one thing that I've noticed:"
1753070,2018-11-04 20:24:18 UTC,Same issue here on Ubuntu 18.10
1753070,2018-09-09 06:29:44 UTC,"Found a solution,open terminal and write sudo mv /usr/share/sounds/ubuntu/stereo/bell.ogg /usr/share/sounds/gnome/default/alerts this will move the file bell.ogg to the other directory, the write cd /usr/share/sounds/gnome/default/alerts , now, sudo mv bark.ogg bark1.ogg (this will change the name of the file bark.ogg), then write sudo mv bell.ogg bark.ogg (this will change the name of the file bell.ogg to bark.ogg) finally go to the sound setting into the setting menu and select Bark as the sound effect, but considering that we replaced bark with bell, bell sound will be played."
1753070,2018-06-24 19:52:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753070,2019-01-29 00:49:10 UTC,"This bug is there for years, in fact for as long as I remember seeing this software around (so, maybe 10 years on Ubuntu?). It bothered me a lot (like a scratch on a brand new car or high tech device), and I always thought ""well it's an obvious bug, it will be fixed soon, as everyone else will notice it and will be bothered by it (so that they will report it)""."
1753071,2018-03-04 19:18:02 UTC,"Cool, I'll leave it on the wishlist for now."
1753071,2018-03-04 17:10:33 UTC,"Actually there is a somewhat architecture reason.  Inter and intra process communication between the schematic and board editors is undefined when you open a schematic (or board) that is not part of the current project so to prevent any issues do to undefined communications, we just don't allow opening non-project boards and schematics in a way that could cause problems.  It's a fairly trick problem to solve since kicad is designed as a single document interface (SDI).  We've talked in the past about converting to and MDI but there are far more important issues to fix at the moment."
1753071,2018-03-03 12:05:08 UTC,"I have some sympathy for that, but I'd have to research it a bit to make sure there isn't an architectural reason we do it that way."
1753071,2018-03-03 11:10:52 UTC,"@Andrey, did you click the big eeschema button in the Kicad main window, or double-click on a file in the project tree?"
1753071,2018-03-03 11:28:22 UTC,"OK, yes motherboard-stable.sch did not exist, I was opening motherboard.sch in a motherboard-stable project from the project tree."
1753078,2018-10-12 01:37:50 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/a6be60a75215d699978e07692593d9cb3c403598"
1753078,2018-10-12 01:34:46 UTC,Invalid for gnome-shell. This is an extension bug.
1753078,2018-03-28 04:46:59 UTC,Agreed and after verification I didn't find any occurrence of this crash in errors.u.c
1753078,2018-03-28 01:39:47 UTC,"I don't think rls-bb-incoming is appropriate here, because this bug is caused by a non-default extension being installed."
1753078,2018-03-27 12:27:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753078,2018-03-08 10:35:34 UTC,"I think the extension that's monitoring the CPU, which I'm using, is this: https://extensions.gnome.org/extension/120/system-monitor/"
1753078,2018-03-08 02:00:58 UTC,This looks like a new crash nobody has reported before. It also looks like it might be crashing in some kind of CPU-monitoring shell extension.
1753078,2018-03-07 21:44:11 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 __GI_abort () at abort.c:90
 glibtop_error_io_vr (server=server@entry=0x7fbd765f93e0 <_glibtop_global_server>, format=format@entry=0x7fbd763f6305 ""open (%s)"", error=<optimized out>, args=args@entry=0x7ffd110b1e40) at error.c:103
 glibtop_error_io_r (server=server@entry=0x7fbd765f93e0 <_glibtop_global_server>, format=format@entry=0x7fbd763f6305 ""open (%s)"") at error.c:157
 file_to_buffer (server=server@entry=0x7fbd765f93e0 <_glibtop_global_server>, buffer=buffer@entry=0x7ffd110b1f60 """", bufsiz=bufsiz@entry=81920, filename=filename@entry=0x7fbd763f56fe ""/proc/stat"") at glibtop_private.c:130"
1753078,2018-03-09 02:18:06 UTC,Thanks. I think I've found the related packages now. See above.
1753091,2018-03-03 16:20:07 UTC,"The attachment ""apt_clone.py.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1753098,2018-10-15 13:42:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753109,2018-03-06 23:19:43 UTC,"sorry, can you clarify if you're using devstack or using distro packages? the doc you linked is using distro packages."
1753109,2018-03-07 01:20:00 UTC,I was using devstack. Yes I found the option to setup ceilometer with gnocchi in local.conf and that is worked! Thanks
1753109,2018-04-18 12:38:14 UTC,"Facing same issue:
tack@ubuntu:/etc/init.d$ sudo apt-get install gnocchi-api
Reading package lists... Done
Building dependency tree
Reading state information... Done
gnocchi-api is already the newest version (3.1.9-0ubuntu1~cloud0).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up gnocchi-api (3.1.9-0ubuntu1~cloud0) ...
Registering service and endpoints for gnocchi with type metric at http://17.203.148.136:8041
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils. This warning is caused by an out-of-date import in /usr/local/lib/python2.7/dist-packages/zaqarclient/queues/cli.py
Failed to discover available identity versions when contacting http://127.0.0.1:35357/v3/. Attempting to parse version from URL.
Unable to establish connection to http://127.0.0.1:35357/v3/auth/tokens: HTTPConnectionPool(host='127.0.0.1', port=35357): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0d23e3a8d0>: Failed to establish a new connection: [Errno 111] Connection refused',))
Warning - data is empty
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils. This warning is caused by an out-of-date import in /usr/local/lib/python2.7/dist-packages/zaqarclient/queues/cli.py
Failed to discover available identity versions when contacting http://127.0.0.1:35357/v3/. Attempting to parse version from URL.
Unable to establish connection to http://127.0.0.1:35357/v3/auth/tokens: HTTPConnectionPool(host='127.0.0.1', port=35357): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ff5315f3250>: Failed to establish a new connection: [Errno 111] Connection refused',))
dpkg: error processing package gnocchi-api (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 gnocchi-api
E: Sub-process /usr/bin/dpkg returned an error code (1)
stack@ubuntu:/etc/init.d$"
1753112,2019-11-13 08:39:11 UTC,probably solved by https://github.com/mixxxdj/mixxx/pull/2247
1753112,2018-03-03 15:17:15 UTC,workaround/fix for Tango in https://github.com/mixxxdj/mixxx/pull/1531
1753112,2018-03-03 15:13:11 UTC,"Probably there's already an unperceived blur at normal size, but it's not obvious since size in skin (111*111px) doesn't differ much from svg size (96*96px)"
1753113,2018-03-20 17:58:56 UTC,That's a great idea!
1753115,2018-03-03 15:24:13 UTC,related to 1559482 add-apt-repository manpage does not mention new -u option
1753115,2018-06-07 08:59:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753115,2020-07-07 10:59:57 UTC,"add-apt-repository -h mentions the option, though."
1753120,2020-07-01 00:28:20 UTC,Fixed in version gtkmm2.4/1:2.24.5-4
1753120,2019-05-31 20:43:13 UTC,"The following packages have unmet dependencies:
 libgtkmm-2.4-dev : Depends: libgtkmm-2.4-1v5 (= 1:2.24.4-2) but 1:2.24.5-2 is installed"
1753120,2019-05-31 20:45:09 UTC,strange
1753120,2019-04-10 03:17:47 UTC,"package libgtkmm-2.4-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package libgtkmm-2.4-dev:i386 1:2.24.5-2"
1753120,2019-05-31 20:29:39 UTC,"I am having the same problem, how to solve this?"
1753120,2018-05-30 17:17:05 UTC,Yeah. Ubuntu 18.04 UEFI is causing a lot of stress.
1753120,2018-05-01 22:56:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753120,2019-01-06 16:04:31 UTC,"I used my computer with ""legacy boot"" + gpt partitioning."
1753127,2018-11-28 12:39:54 UTC,@Battan: the problem you reported does not seem to be the same as the one in this bug report. Please file a separate bug report for that.
1753127,2018-06-12 22:50:03 UTC,"Hello,"
1753127,2018-06-12 13:58:31 UTC," Hello ,"
1753127,2018-06-09 16:56:09 UTC,"Hello,
The GUI (graphicc user interface)!dose not start If i have no internet connection (offline )
An other personé (novice on ubuntu ) has upgrade Ubuntu 16.04 to Ubuntu 18.04 Have the same probkeme
The internet must connect at start (Ethernet or WiFi)
Same problem whith the live dvd ?
Why this internet connection deprndence
Why the GUI coud’nt Start ofline
Could you confirme this and help me to fix this issue
Thanks for your supporters
Best regards"
1753127,2018-06-12 16:46:36 UTC,This bug also affect kernel 4.16 and kernel 4.17
1753127,2018-03-14 07:16:14 UTC,"@Doug: if you're using a hybrid system, then I think Wayland will use your Intel card, but you should still be able to use the discrete GPU for some applications (at least in the next GNOME release)."
1753127,2018-03-07 12:16:27 UTC,"On 03/06/2018 11:37 PM, Daniel van Vugt wrote:

> I think this is correct. Nvidia disables KMS support by default, which
> means no wayland support.
>
> It is documented (with a workaround) here:
> http://us.download.nvidia.com/XFree86/Linux-x86_64/390.25/README/kms.html
>
> ** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
>     Importance: Undecided => Medium
>
> ** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
>         Status: New => Triaged
>


Correct but now in 18.04 KMS can no longer be set in the combo of
Ubuntu's 4.15 kernel & nvidia drivers.
See here
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752739"
1753127,2018-03-07 04:37:39 UTC,"I think this is correct. Nvidia disables KMS support by default, which means no wayland support."
1753127,2018-03-14 21:56:15 UTC,"What was quite 'odd' is the day I filed this was a fresh install, updated, then installed nvidia-drivers (390.x), rebooted
For about 2 days it was as described, log into xserver got nvidia, log into wayland got intel.
Then, for no apparent reason on boot up the option to log into wayland disappeared. The only way to get it back was to remove the bulk of the nvidia driver packages."
1753128,2018-03-03 18:32:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/549493"
1753132,2018-03-03 23:26:07 UTC,"Just pulled the most recent sources after this patch, and can confirm it’s working beautifully again.  I really appreciate your efforts and your project."
1753141,2018-03-05 18:29:15 UTC,@pointhi-
1753141,2019-05-11 11:38:12 UTC,"The modern toolset doesn't support drag-selection from other tools.  We'll see how annoying folks find it, but for now this bug no longer exists."
1753141,2018-03-06 14:16:09 UTC,Nick: https://cloud.oe5tpo.com/s/spCBCmfyYwCrr36
1753141,2018-03-06 13:12:08 UTC,I have never seen the current behavior as a problem. Are you using some strange input device since it is troublesome to keep the cursor static while clicking?
1753141,2018-03-06 05:53:03 UTC,"@JP-  You are right, the current filter (hard coded) takes a number of mouse events before deciding that there is a drag.  Playing with this, it seems that I can trigger a drag more easily at high resolution due to more mouse events."
1753141,2018-03-05 18:42:44 UTC,no wire at all
1753141,2018-03-05 18:06:41 UTC,"It's hard to say if the mouse moved sufficiently to a drag-selection, but it's possible. My thought was that the ""mouse up"" event happens in my case outside of the circle drawn around the pin."
1753141,2018-03-06 19:15:10 UTC,"Honestly, after seeing this video, I do share the Wayne's opinion:
""the user is just going to have to be more careful"""
1753141,2018-03-05 17:55:25 UTC,"@Seth
Option 1): AFAIK, the filtering is already in place.
Starting a block command is made only if the mouse drag distance is enough (a few pixels).
(See if it is good for HDPI)"
1753141,2018-03-05 17:30:49 UTC,"this reproduction steps are pretty artificial. When thinking about the issue itself, selection normally means holding the mouse button quite some time. I assume the position for the start of the wire is taken from the ""mouse up"" event. My proposal would be something like: when the ""mouse down"" event followed by the ""mouse up"" event happens inside a time-delta of 100ms or so, the position from ""mouse down"" is used for the tool action."
1753141,2018-03-05 16:34:21 UTC,OK.  Will put this on the wishlist then after bugs
1753141,2018-03-05 16:15:39 UTC,"I don't like #2 at all.  One thing that I have always thought KiCad did
better than any other EDA tool is not limiting each tool to doing only
one thing at a time.  I hate having to constantly change tools to get
work done.  I would rather fix our drag heuristics so you don't get drag
event when single clicking too quickly.  At some point, no amount of
heuristics is going to solve this issue and the user is just going to
have to be more careful."
1753141,2018-03-05 10:36:51 UTC,"It’s pretty easy to get behind (2).  The Selection tool is called the selection tool because it does selections.  The Wire tool, on the other hand, is not called the wire tool because it does selections. :)"
1753141,2018-03-05 05:25:01 UTC,I see two options for this.
1753141,2018-03-05 17:55:38 UTC,@pointhi-
1753148,2020-03-12 17:25:26 UTC,marked Won't Fix as it seems to be a minor issue with the Qt SVG module.
1753159,2020-05-30 20:21:31 UTC,Thanks
1753159,2020-05-30 20:20:50 UTC,This should give you a good explanation of what fsck is and does and how to use it. https://www.computerhope.com/unix/fsck.htm
1753159,2020-05-30 19:21:23 UTC,"Thanks, i fixed it. :)
Please, can you explain me how to run a fsck
Or give me a good page so i can read it?"
1753159,2020-05-29 03:49:46 UTC,"Being that is was 2 years ago, I don't remember exactly what I did. I can only assume at this point, since I am not in a position right now to replicate this issue and try to work around it again. However I will try to give instructions to help, so be aware that I might not be giving sufficient instructions. I am assuming you can access the terminal in some form, and hopefully know at least the basics of working with the terminal."
1753159,2020-05-29 03:11:02 UTC,"Hi Christian i have the same problem,but i'm new in using linux, can you explain me how to fix it,step by step,please?"
1753159,2018-03-03 21:23:36 UTC,"After experimenting and researching, it appears that the user profile named ""User"" was corrupted. I fixed the issue by creating a new user and copying their files from the .config folder in their user folder. I then deleted the secondary account."
1753159,2020-05-29 03:25:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753169,2018-04-04 20:13:22 UTC,"n Wed, Apr 04, 2018 at 06:01:38AM +0000, Gianfranco Costamagna wrote:"
1753169,2018-03-03 21:00:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753169,2018-03-05 00:58:26 UTC,"I noticed someone else filed an ""Intent to file removal bug"" in debian:"
1753169,2018-03-12 10:08:55 UTC,"FTR, I've added a request for a decision on this to https://wiki.ubuntu.com/TechnicalBoardAgenda, as I don't see that it can be resolved any other way. I'm not sure at which meeting this will be discussed as tomorrow's meeting may be too short notice."
1753169,2018-03-22 20:49:58 UTC,See also https://launchpad.net/bugs/1758163 for xchat-gnome.
1753169,2018-03-27 06:34:03 UTC,"Hi Robie, Gianfranco,"
1753169,2018-04-04 06:01:38 UTC,"Hello Steve and all,"
1753169,2018-04-04 16:38:58 UTC,"On Wed, Apr 4, 2018 at 2:01 AM, Gianfranco Costamagna
<email address hidden> wrote:

> we still don't have a clean upgrade path from xchat to hexchat, at least for configuration files.
"
1753172,2018-03-03 21:15:31 UTC,"The calendar is also affected, its currently displayed in Urdu and it should much rather be displayed in English."
1753172,2018-03-03 21:10:57 UTC,bug 1160441 might be related or actually the one we solved and introduced the issue I reported.
1753174,2020-08-10 02:14:58 UTC,libzulucrypt1:amd64 5.2.0.1507812525.517c7030-0
1753175,2020-08-10 02:15:44 UTC,zulucrypt-gui 5.2.0.1507812525.517c7030-0
1753176,2018-03-11 10:35:06 UTC,You are getting the problem because you already have zuluCrypt installed from packages provided by zuluCrypt upstream and you are trying to update them using ubuntu provided packages.
1753176,2020-08-10 02:16:20 UTC,libzulucrypt1:amd64 5.2.0.1507812525.517c7030-0
1753177,2018-03-05 17:02:43 UTC,"Thank you for your bug report, that looks like an upstream bug which has been fixed in that commit
https://gitlab.gnome.org/GNOME/gnome-software/commit/4a61725c"
1753183,2020-04-30 08:18:06 UTC,The default format is deb
1753183,2019-01-10 14:11:26 UTC,"Indeed, that's because the snap doesn't include the search provider, installing the gnome-calculator deb can be used as a workaround until that problem is resolved (it's currently being worked on)"
1753183,2019-12-22 23:50:08 UTC,"This is still an issue in 19.10. Has there been any progress? Also, is there any explanation anywhere about why gnome-calculator is a snap and not a deb? I have to imagine fixing both this issue and the launch time issue (https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734) are hard to fix and thus won't be fixed soon, and both would be solved if gnome-calculator wasn't a snap."
1753183,2020-04-29 14:08:58 UTC,"Please note that gnome-calculator is (also?) available as a deb package on Ubuntu 20.04.
Can't recall whether the **default** is deb or snap though."
1753186,2018-03-05 12:51:16 UTC,"Hi,"
1753186,2020-11-24 16:20:33 UTC,"Closing this as WontFix since it works as expected, and keeping it open as wishlist item does not make too much sense."
1753191,2018-03-04 01:29:34 UTC,apport information
1753191,2018-03-04 01:29:33 UTC,apport information
1753191,2018-03-04 01:29:31 UTC,apport information
1753191,2018-03-04 01:29:26 UTC,apport information
1753191,2018-03-04 01:29:29 UTC,apport information
1753191,2018-03-04 01:29:36 UTC,apport information
1753191,2018-03-04 01:29:30 UTC,apport information
1753191,2018-03-04 01:29:37 UTC,apport information
1753191,2018-03-04 01:29:46 UTC,apport information
1753191,2018-03-04 01:29:39 UTC,apport information
1753191,2018-03-04 01:29:40 UTC,apport information
1753191,2018-03-04 01:29:42 UTC,apport information
1753191,2018-03-04 01:29:43 UTC,apport information
1753191,2018-03-06 04:35:52 UTC,"This started happening once I installed Ubuntu on this PC. In fact, this issue persists throughout all versions of linux I've installed (Fedora/Manjaro/Mint). It wasn't happening on my windows install."
1753191,2018-03-04 01:29:48 UTC,apport information
1753191,2018-03-05 10:50:19 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1753191,2018-03-04 01:29:38 UTC,apport information
1753191,2018-03-04 01:29:25 UTC,apport information
1753191,2018-03-04 01:28:53 UTC,apport information
1753191,2018-03-04 01:29:02 UTC,apport information
1753191,2018-03-04 01:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1753191,2018-03-04 01:28:43 UTC,apport information
1753191,2018-03-04 01:28:44 UTC,apport information
1753191,2018-03-04 01:28:46 UTC,apport information
1753191,2018-03-04 01:28:47 UTC,apport information
1753191,2018-03-04 01:28:49 UTC,apport information
1753191,2018-03-04 01:28:50 UTC,apport information
1753191,2018-03-04 01:28:51 UTC,apport information
1753191,2018-03-04 01:28:54 UTC,apport information
1753191,2018-03-04 01:28:55 UTC,apport information
1753191,2018-03-04 01:28:56 UTC,apport information
1753191,2018-03-04 01:28:57 UTC,apport information
1753191,2018-03-04 01:28:59 UTC,apport information
1753191,2018-03-04 01:29:00 UTC,apport information
1753191,2018-03-04 00:54:15 UTC,devices
1753191,2018-03-04 01:29:05 UTC,apport information
1753192,2018-03-11 20:12:31 UTC,"The menuentry for arch linux is named '""Arch Linux'. Grub Customizer isn't handling the '""' correctly (I should fix this...)."
1753192,2018-03-05 23:17:11 UTC,http://ix.io/T4Q
1753192,2018-03-05 22:49:29 UTC,What's the content of /etc/grub.d/10_linux_proxy?
1753209,2021-01-05 00:05:43 UTC,"Seems like this got fixed on neutron and neutron-tempest-plugin side ... the LP is marked Fix Committed for tempest party, however there hasn't been any commit merged/committed in tempest regarding this (or at least i haven't found any), therefore I'm changing the state to Invalid .. If my assumptions are not correct and the bug is still causing troubles, please feel free to raise it and change the status of the LP accordingly."
1753209,2018-06-05 02:02:47 UTC,"Reviewed:  https://review.openstack.org/571682
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=19c367d5795e4f6c1f9a9d421e22a4cf1e5b15a2
Submitter: Zuul
Branch:    stable/ocata"
1753209,2018-06-06 23:41:55 UTC,"Reviewed:  https://review.openstack.org/571681
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=221df78612820fcbd3455b4b1092bdc8160c56cb
Submitter: Zuul
Branch:    stable/pike"
1753209,2018-06-18 15:16:07 UTC,This issue was fixed in the openstack/neutron 11.0.5 release.
1753209,2018-06-18 15:39:33 UTC,This issue was fixed in the openstack/neutron 10.0.7 release.
1753209,2018-11-06 10:37:04 UTC,"Change abandoned by Federico Ressi (<email address hidden>) on branch: master
Review: https://review.openstack.org/604718"
1753209,2018-11-14 08:04:33 UTC,"I personally think the solution of this problem is a lack in base test case classes. When a test case doesn't specify a network to use, it should create one using some parameters specified in tempest.conf. Using a shared network by default (implicitly, without any notice, and without choosing it) makes testing shared networks near to impossible in the contest of running test cases in parallel and therefore should be forbidden and limited to very specific test cases where shared network is explicitly pick up by test case."
1753209,2019-05-28 07:56:57 UTC,"Based on master skip list update: https://tree.taiga.io/project/tripleo-ci-board/task/1088?kanban-status=1447275
Below is the tests are passing:
 ""tempest.api.volume.test_volumes_snapshots.VolumesSnapshotTestJSON"": [
        ""tempest.api.volume.test_volumes_snapshots.VolumesSnapshotTestJSON.test_snapshot_create_delete_with_volume_in_use"",
        ""tempest.api.volume.test_volumes_snapshots.VolumesSnapshotTestJSON.test_snapshot_create_get_list_update_delete"",
        ""tempest.api.volume.test_volumes_snapshots.VolumesSnapshotTestJSON.test_snapshot_create_offline_delete_online""
    ],"
1753209,2019-05-28 07:57:19 UTC,Logs are here https://logs.rdoproject.org/openstack-periodic-master/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset021-master/7ab6f45/logs/undercloud/home/zuul/tempest.log.txt.gz#_2019-05-28_04_21_53
1753209,2019-05-28 08:00:41 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/661694"
1753209,2019-12-12 14:10:44 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/698724"
1753209,2019-12-12 14:20:40 UTC,"Change abandoned by Soniya Murlidhar Vyas (<email address hidden>) on branch: master
Review: https://review.opendev.org/698724
Reason: This patch is already existing:- https://review.opendev.org/#/c/696387"
1753209,2020-01-13 12:08:53 UTC,"Reviewed:  https://review.opendev.org/696387
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=361cc61be41fbce818abfd61f49c910fa7a77e0f
Submitter: Zuul
Branch:    master"
1753209,2020-01-13 17:10:45 UTC,"Reviewed:  https://review.opendev.org/699394
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=f1b00f047569913eb33fe67c6cf714ca0e8b4373
Submitter: Zuul
Branch:    master"
1753209,2020-01-15 19:13:29 UTC,"Reviewed:  https://review.opendev.org/699275
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=5d393c80b8d525683f525c9d6d8a8a5a5798dbb5
Submitter: Zuul
Branch:    master"
1753209,2020-10-07 01:36:36 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.opendev.org/698887"
1753209,2018-06-05 01:55:28 UTC,"Reviewed:  https://review.openstack.org/571677
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9f72d8387ecb2b81b9e7969004ea247a948de6f9
Submitter: Zuul
Branch:    stable/ocata"
1753209,2019-05-29 15:15:12 UTC,"Reviewed:  https://review.opendev.org/661694
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=85bba9f24a79da8069d5d0b4a7515dd62893e202
Submitter: Zuul
Branch:    master"
1753209,2018-06-05 00:42:58 UTC,"Reviewed:  https://review.openstack.org/571676
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=48c5c84ee0327e2d6f5239a2e61d3787395635e1
Submitter: Zuul
Branch:    stable/pike"
1753209,2019-12-13 12:09:22 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/698887"
1753209,2018-06-01 09:57:47 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/571682"
1753209,2018-03-04 08:11:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/549516"
1753209,2018-03-04 13:20:00 UTC,"Reviewed:  https://review.openstack.org/549516
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=4a3e4bc6e942f7cd37c413db98f9ef7aa65cc300
Submitter: Zuul
Branch:    master"
1753209,2018-03-05 18:01:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/549837"
1753209,2018-03-07 17:16:20 UTC,"Reviewed:  https://review.openstack.org/549837
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=e1d432115cd424ab6a4be474a7a1e1922c4553ed
Submitter: Zuul
Branch:    master"
1753209,2018-03-08 17:48:22 UTC,"So the reason of failure here is that one test case uses a network that was temporarily shared with all tenants while running a RBAC test case. When the network is for a short span of time shared with everyone, the other test case - VolumesSnapshotTestJSON:test_snapshot_create_delete_with_volume_in_use - creates an instance with the following request body:"
1753209,2018-03-08 17:49:44 UTC,Added neutron to affected projects since we may need to modify the api test case that is the root cause of the failure; also added tempest to clarify what's the recommendation for this type of test cases affecting other users.
1753209,2018-03-08 19:41:43 UTC,"My belief is that all test classes should use resources explicitly created for them; so in case of volume tests that are triggering a race in RBAC test class, they would boot instances with port/net specified instead of allowing nova to pick one."
1753209,2018-03-15 17:19:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/553499"
1753209,2018-06-05 00:21:33 UTC,"Reviewed:  https://review.openstack.org/571675
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d9de2233d5edb7f978ed72e2ea8c4dc42a399e3d
Submitter: Zuul
Branch:    stable/queens"
1753209,2018-03-18 13:01:51 UTC,"Reviewed:  https://review.openstack.org/553499
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6c772de103e469ad17cdbc6a86ed15655aa6b9cc
Submitter: Zuul
Branch:    master"
1753209,2018-04-05 23:22:57 UTC,"@Akihiro, probably yes. Probably will require a separate bug report."
1753209,2018-05-22 22:19:41 UTC,"Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: master
Review: https://review.openstack.org/553501"
1753209,2018-03-18 09:47:41 UTC,"https://review.openstack.org/#/c/553499/ and https://review.openstack.org/#/c/550987/ move a test which shares a network via neutron RBAC mechanism. Do we also need to clean up all shared network case like a network with shared=True attribute? Do we also need to clean up 'shared' cases for other resources (like subnet pool, qos policy and so on)?"
1753209,2018-06-01 09:47:49 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/571675"
1753209,2018-06-01 09:48:39 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/571676"
1753209,2018-06-01 09:49:09 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/571677"
1753209,2018-06-01 09:56:41 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/571681"
1753220,2018-05-27 10:07:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753226,2019-01-02 12:36:24 UTC,"I think this is duplicated with these two bugs:
https://bugs.launchpad.net/nova/+bug/1289064
https://bugs.launchpad.net/nova/+bug/1712008"
1753226,2018-03-04 16:25:29 UTC,Output of host info after live migration
1753226,2018-10-11 20:55:02 UTC,What version of nova are you using? And did you specify a host when you requested the live migration or no? Did you use the 'force' flag?
1753242,2018-03-17 07:42:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753251,2018-03-04 13:27:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549607"
1753251,2018-03-04 14:04:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549612"
1753251,2018-03-05 19:26:51 UTC,"Reviewed:  https://review.openstack.org/549607
Committed: https://git.openstack.org/cgit/openstack/openstack-helm/commit/?id=1c85fdc390e05eb578874e77fad9d4ec942da791
Submitter: Zuul
Branch:    master"
1753251,2018-03-05 22:10:23 UTC,"Reviewed:  https://review.openstack.org/549612
Committed: https://git.openstack.org/cgit/openstack/openstack-helm/commit/?id=d60d2741c5fc34069aa69c0a153ec2dd28df154e
Submitter: Zuul
Branch:    master"
1753251,2018-06-11 01:39:25 UTC,"Change abandoned by Pete Birley (<email address hidden>) on branch: master
Review: https://review.openstack.org/549625"
1753252,2018-05-11 15:36:03 UTC,This change was made by a bot.
1753260,2018-04-01 19:27:16 UTC,I wonder if this could somehow be related to bug #1760457?
1753263,2018-07-25 09:34:13 UTC,"On a Dell XPS 15 9560 laptop I'm seeing the same error as above on the ""Processor"" section :"
1753263,2018-10-02 03:18:09 UTC,/proc/timer_stats was enabled when the kernel was compiled with CONFIG_TIMER_STATS=y
1753263,2019-12-12 13:45:00 UTC,From https://lwn.net/Articles/714710/
1753263,2020-05-31 21:42:41 UTC,This is a confirmed regression with complete information.
1753263,2020-05-31 22:13:57 UTC,Related fixed bug @ https://bugs.freedesktop.org/show_bug.cgi?id=100626
1753263,2020-05-31 22:21:03 UTC,Closed in (what I think to be) upstream https://gitlab.gnome.org/GNOME/gnome-power-manager/-/issues/3
1753263,2018-09-12 05:39:33 UTC,lenovo Ideapad 510
1753263,2018-04-27 19:25:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753263,2018-04-28 03:08:53 UTC,"On a Dell XPS 13 laptop, Power Statistics does show the AC adapter and Laptop battery status, but the Processor statistics has the same error as above:"
1753263,2018-03-12 16:08:44 UTC,"Thank you for your bug report. What sort of computer do you use? On a laptop it should least batteries info, on a desktop indeed you get only the CPU information and that seems buggy.
There is a Debian bug report describing similar problems on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689298
It might have to do with upower/kernel options, needs investigation"
1753263,2018-03-12 17:04:36 UTC,It's a virtual machine under KVM on my desktop PC.
1753274,2018-03-04 18:26:17 UTC,"Hi,"
1753276,2018-07-13 13:49:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753281,2018-03-23 22:25:32 UTC,Same for me on Ubuntu 17.10. I also noticed that setting Super only as Expo key doesn't work either.
1753281,2018-07-05 13:38:40 UTC,"This behavior is - for some reason - caused by the new system tray in mate-panel. It's called 'Indicator Applet Complete'. You can use 'Indicator Applet' instead. I don't actually know the difference between the two, but they're very similar."
1753281,2018-07-05 18:46:57 UTC,@Johannes Wolf - thank you for the info. I filed this upstream bug report: https://github.com/mate-desktop/mate-indicator-applet/issues/28
1753284,2019-06-17 01:35:12 UTC,I suspect that this is because this credential is a region specific one and we are not validating it against a correct region. There is work underway to optionally allow users to specify what region the credential is for at add-credential Juju CLI.
1753284,2019-06-25 01:29:46 UTC,This seems to be a duplicate of bug # 1680523.
1753290,2018-03-14 10:27:27 UTC,"Just to clarify, is the goal to
a) Provide better error messaging when we are unable to provision an instance
b) Pick a different VM size
c) Pick a different region"
1753291,2018-03-05 23:55:05 UTC,*** This is an automated message ***
1753291,2018-03-05 19:29:28 UTC,Thanks for reporting.
1753294,2018-10-10 14:02:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753295,2018-03-05 12:37:39 UTC,@dj-kaza The first bug you mention is a duplicate of https://bugs.launchpad.net/mixxx/+bug/1656590 which I reported a year ago. You could comment there and edit this bug here so it's only about the play direction.
1753295,2018-03-05 12:54:01 UTC,"Thanks ronsi0, when I searched for similar bugs I could only find the one I linked in the original post, which I suspect the fix is what has caused this behaviour on the first place. Anyway doing as suggested so apologies if these comments seem random to casual readers...."
1753295,2018-03-05 13:00:20 UTC,Sorry for the type on your name ron. Can't see how to edit posts apart from the initial report....
1753296,2018-03-06 21:56:59 UTC,"StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f723ab87c40 <main_arena>) at malloc.c:4464
 _int_malloc (av=av@entry=0x7f723ab87c40 <main_arena>, bytes=bytes@entry=5428) at malloc.c:3703
 __GI___libc_malloc (bytes=5428) at malloc.c:3065
 read_packet (c=0x55dd80b71f60) at ../../src/xcb_in.c:259
 _xcb_in_read (c=c@entry=0x55dd80b71f60) at ../../src/xcb_in.c:1012"
1753297,2018-03-04 23:14:27 UTC,"Not realy, circles can have LPE but if has LPE or Edit to segment, for example, are converted to paths on save. Maybe is the good approach to rectangles..."
1753297,2018-03-04 22:19:17 UTC,"Oh, I see - even a circle has 'path' in its id attribute. So circles are handled as paths?"
1753297,2018-03-04 21:22:57 UTC,Rectangle is handled in inkscape as a svg:rect. svg:rect couldnt have LPE (it convert to path on apply a new LPE)
1753329,2018-03-12 13:11:07 UTC,"Hi Jes,
this is a topic that actually is discussed between Ubuntu / Docker itself and other parties.
There is no clear outcome yet, but things are going on (slowly and quite a while already)."
1753329,2018-09-10 19:23:55 UTC,I added it to the sprint topics again
1753329,2020-05-30 15:53:33 UTC,"As another datapoint, the docker.io package serves as a build dependency to many container-related packages in the archive. Dropping the package would in the short-term mean breaking all packages that use this code  (nomad, buildah, podman, to name a few). In the long term, it might cause increased vendoring inside the archive, making security support harder."
1753342,2018-03-16 06:02:04 UTC,"Reviewed:  https://review.openstack.org/549661
Committed: https://git.openstack.org/cgit/openstack/puppet-murano/commit/?id=f2b71b1adbba9433f8aee48d340fd34aa105ae4c
Submitter: Zuul
Branch:    master"
1753342,2018-03-17 19:22:45 UTC,"Reviewed:  https://review.openstack.org/553868
Committed: https://git.openstack.org/cgit/openstack/puppet-ceilometer/commit/?id=de20f77d031c3817ec035d8535e1421309bb258f
Submitter: Zuul
Branch:    stable/queens"
1753342,2018-03-16 17:54:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/553869"
1753342,2018-03-16 17:54:37 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/553868"
1753342,2018-03-19 03:59:51 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554113"
1753342,2018-03-13 06:35:56 UTC,"Reviewed:  https://review.openstack.org/549660
Committed: https://git.openstack.org/cgit/openstack/puppet-ceilometer/commit/?id=76bce0ada4dbb0b59f4936ef4f9a6d76f82066f0
Submitter: Zuul
Branch:    master"
1753342,2018-03-17 19:30:03 UTC,"Reviewed:  https://review.openstack.org/553869
Committed: https://git.openstack.org/cgit/openstack/puppet-ceilometer/commit/?id=2f235228ab089bcb78206bc38c1e513177957ca9
Submitter: Zuul
Branch:    stable/pike"
1753342,2018-03-09 17:32:51 UTC,"Reviewed:  https://review.openstack.org/549663
Committed: https://git.openstack.org/cgit/openstack/puppet-vitrage/commit/?id=c9b4316df44154d9baf74dbe8dd0839ba8bed7d2
Submitter: Zuul
Branch:    master"
1753342,2018-03-05 01:36:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549663"
1753342,2018-03-05 01:36:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549662"
1753342,2018-03-05 01:35:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549661"
1753342,2018-03-05 01:35:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549660"
1753342,2018-03-19 04:00:08 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554114"
1753342,2018-03-13 05:55:26 UTC,"Reviewed:  https://review.openstack.org/549662
Committed: https://git.openstack.org/cgit/openstack/puppet-magnum/commit/?id=785ab85b29eb990c3904678a3287d37445241277
Submitter: Zuul
Branch:    master"
1753342,2018-03-19 04:02:00 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554115"
1753342,2018-04-19 21:05:55 UTC,This issue was fixed in the openstack/puppet-vitrage 3.0.0 release.
1753342,2018-03-19 04:02:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554117"
1753342,2019-05-16 23:05:57 UTC,This issue was fixed in the openstack/puppet-murano 11.6.0 release.
1753342,2019-05-16 23:04:59 UTC,This issue was fixed in the openstack/puppet-magnum 11.6.0 release.
1753342,2019-05-16 23:02:45 UTC,This issue was fixed in the openstack/puppet-ceilometer 11.6.0 release.
1753342,2018-04-19 21:03:16 UTC,This issue was fixed in the openstack/puppet-murano 13.0.0 release.
1753342,2018-04-19 21:02:26 UTC,This issue was fixed in the openstack/puppet-magnum 13.0.0 release.
1753342,2018-04-19 20:59:13 UTC,This issue was fixed in the openstack/puppet-ceilometer 13.0.0 release.
1753342,2018-03-29 00:15:38 UTC,This issue was fixed in the openstack/puppet-vitrage 2.4.0 release.
1753342,2019-05-16 23:07:38 UTC,This issue was fixed in the openstack/puppet-vitrage 1.2.0 release.
1753342,2018-03-29 00:12:59 UTC,This issue was fixed in the openstack/puppet-murano 12.4.0 release.
1753342,2018-03-19 06:47:32 UTC,"Reviewed:  https://review.openstack.org/554117
Committed: https://git.openstack.org/cgit/openstack/puppet-vitrage/commit/?id=5f82c2435471702654afdd6881fedb4b1edd3343
Submitter: Zuul
Branch:    stable/queens"
1753342,2018-03-19 06:47:23 UTC,"Reviewed:  https://review.openstack.org/554118
Committed: https://git.openstack.org/cgit/openstack/puppet-vitrage/commit/?id=87fcbe93db238831a1dcc795ec67914f98ba5466
Submitter: Zuul
Branch:    stable/pike"
1753342,2018-03-19 04:50:09 UTC,"Reviewed:  https://review.openstack.org/554113
Committed: https://git.openstack.org/cgit/openstack/puppet-magnum/commit/?id=54b4f8d847450dbd5c8b7f8d75d6beaaf5dd9621
Submitter: Zuul
Branch:    stable/queens"
1753342,2018-03-19 04:50:00 UTC,"Reviewed:  https://review.openstack.org/554114
Committed: https://git.openstack.org/cgit/openstack/puppet-magnum/commit/?id=82bc629df8977236036a69d1a274df73bd6f89dc
Submitter: Zuul
Branch:    stable/pike"
1753342,2018-03-19 04:48:31 UTC,"Reviewed:  https://review.openstack.org/554116
Committed: https://git.openstack.org/cgit/openstack/puppet-murano/commit/?id=b36cf04f3408f4312d767eec2f77c56228d23e94
Submitter: Zuul
Branch:    stable/pike"
1753342,2018-03-19 04:48:23 UTC,"Reviewed:  https://review.openstack.org/554115
Committed: https://git.openstack.org/cgit/openstack/puppet-murano/commit/?id=d7ccce0c501189d57ea3c209fad4a28453eb8116
Submitter: Zuul
Branch:    stable/queens"
1753342,2018-03-19 04:02:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554116"
1753342,2018-03-19 04:02:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554118"
1753342,2018-03-29 00:10:21 UTC,This issue was fixed in the openstack/puppet-ceilometer 12.5.0 release.
1753349,2019-02-17 03:29:22 UTC,"any comments on this issue as am facing same issue using NSH as correlation when creating port chain, it will fail to steer the traffic towards the SFs"
1753350,2018-03-09 21:40:01 UTC,"StacktraceTop:
 gdk_window_has_impl (window=<optimized out>) at ../../../../gdk/gdkwindow.c:677
 _gdk_window_has_impl (window=window@entry=0x0) at ../../../../gdk/gdkwindow.c:678
 gdk_x11_window_get_xid (window=0x0) at ../../../../../gdk/x11/gdkwindow-x11.c:5566
 gtk_im_context_xim_filter_keypress (context=0x1c21300, event=0x7f9e0000aee0) at ../../../../../modules/input/gtkimcontextxim.c:673
 gtk_im_multicontext_filter_keypress (context=0x1ef7cc0, event=0x7f9e0000aee0) at ../../../../gtk/gtkimmulticontext.c:359"
1753350,2018-03-15 08:05:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753351,2018-03-05 03:07:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549667"
1753352,2018-03-06 00:28:30 UTC,Further to the above:
1753357,2018-03-07 01:00:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/#/c/549670/"
1753357,2018-08-17 20:06:17 UTC,This issue was fixed in the openstack/kuryr-libnetwork 2.0.0 release.
1753358,2020-08-10 02:25:59 UTC,"ufraw (0.22+cvs20170121+r2272~rdeb7~0~crass~ubuntu16.04.1)
ufraw-batch (0.22+cvs20170121+r2272~rdeb7~0~crass~ubuntu16.04.1)"
1753376,2018-04-10 00:37:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753376,2020-08-12 10:18:18 UTC,"Reminder: SRU processing is currently blocked pending the answer to Brian's question in comment 9. If it remains blocked, the upload will get rejected from the queue."
1753376,2018-05-08 04:01:31 UTC,"Same here, at first you are met with a very sparse window, but FreeCad is thankfully usable if you use the view drop down and select a workbench"
1753376,2018-04-29 15:55:10 UTC,The same issue is noted on Ubuntu 18.04 Wayland.
1753376,2019-07-17 20:21:11 UTC,I have prepared a change to the Debian package that will eliminate this issue.
1753376,2019-08-14 03:02:05 UTC,Fixed in 0.17+dfsg1-1
1753376,2020-01-12 14:46:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753376,2020-07-17 12:31:07 UTC,Hi Zachary! Apologies for the delay in reviewing your patch.
1753376,2020-07-28 20:44:23 UTC,The upload to the SRU queue for Bionic does not match the debdiff attached to this bug nor this bug's description. Why was the debian/rules file change dropped?
1753376,2020-09-01 20:29:17 UTC,"An upload of freecad to bionic-proposed has been rejected from the upload queue for the following reason: ""This was rejected from the queue to questions from the Ubuntu SRU team which were unanswered.""."
1753378,2018-10-08 12:05:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753378,2018-10-08 13:33:49 UTC,Corresponding Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874727
1753385,2018-03-07 10:22:08 UTC,"I've adapted another person's shell script to do what I want Sound Converter to do, namely convert all the .wav files in a directory to .mp3 files placed in another directory. Script is attached."
1753394,2018-04-16 13:11:32 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/561613"
1753394,2018-04-17 12:49:12 UTC,"Reviewed:  https://review.openstack.org/561196
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9c66434eea245ae05a449059391515376f5a456
Submitter: Zuul
Branch:    stable/queens"
1753394,2018-04-20 05:24:11 UTC,"Reviewed:  https://review.openstack.org/561611
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b255e16bd93d9891caff8ffc84b8d7bc2991f90a
Submitter: Zuul
Branch:    stable/pike"
1753394,2018-04-20 13:13:26 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1753394,2018-03-14 21:43:45 UTC,You can checkout whatever tag of code you're on (16.0.1):
1753394,2018-04-25 09:21:02 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1753394,2018-04-25 09:23:57 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1753394,2018-05-02 11:59:35 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1753394,2018-04-16 13:09:33 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/561611"
1753394,2018-04-24 18:06:08 UTC,"Reviewed:  https://review.openstack.org/561613
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1150d4a2af5b06c2df5dea053f5f7aea090c9145
Submitter: Zuul
Branch:    stable/ocata"
1753394,2018-04-13 11:08:59 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561196"
1753394,2018-03-07 03:33:19 UTC,"I tried to add image property hw_scsi_model=virtio-scsi, ID seems correct, but ipxe cannot boot from SAN device:
Boot from SAN device 0x81 failed: Exec format error(http://ipxe.org/2e852001)
Boot from SAN device 0x82 failed: Exec format error(http://ipxe.org/2e852001)"
1753394,2018-03-07 13:00:09 UTC,"I found driver.py, driver.pyc and driver.pyo under the directory /usr/lib/python2.7/site-packages/nova/virt/libvirt from the package python-nova-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch.
How can I apply the patch?"
1753394,2018-03-07 12:48:58 UTC,"OpenStack RPM packages are installed in my environment.
python-nova-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch
openstack-nova-conductor-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch
openstack-ansible-os_nova-16.0.0-1.el7.centos.ncir.1.noarch
openstack-nova-api-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch
openstack-nova-novncproxy-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch
openstack-nova-console-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch
openstack-nova-scheduler-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch
ansible-nova-nokia-c7.ge25659f-1.el7.centos.ncir.noarch
python2-novaclient-9.1.0-1.el7.noarch
openstack-nova-placement-api-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch
openstack-nova-common-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch
openstack-nova-compute-16.0.1-0.20170926081607.edd59ae.el7.centos.noarch"
1753394,2018-03-07 07:47:07 UTC,Jay is working on a patch which should fix your issue as-well.
1753394,2018-03-07 01:38:27 UTC,But why it can work on Newton?
1753394,2018-03-07 01:28:25 UTC,"The image is a ipxe image, used to set some extra parameters and load boot program from volume.
If I remove ""image: { get_param: ipxe_image_id }"", and let the VM boot from volume, then ID is correct.
It means virtio-blk and virtio-scsi cannot exist together?
 OMU-0:
    type: OS::Nova::Server
    properties:
      name: OMU-0
      flavor: { get_param: flavor_omu }
      key_name: { get_param: key_name }
      networks: { get_attr: [OMU_0_ports, port-map] }
      block_device_mapping_v2:
        - { ""boot_index"": 0, ""disk_bus"": ""scsi"", ""volume_id"": { get_attr: [vol_omu, resource.0] } }
        - { ""boot_index"": -1, ""disk_bus"": ""scsi"", ""volume_id"": { get_attr: [vol_omu, resource.1] } }"
1753394,2018-03-06 17:06:39 UTC,"I would say it's a configuration issue... but it's difficult to say, we perhaps have to fix something."
1753394,2018-03-06 14:58:20 UTC,Looks like https://github.com/openstack/nova/commit/c25629f85feb53b5be0347f68c43b3b55fb9f137 in pike might have caused a regression.
1753394,2018-04-13 10:42:34 UTC,"Reviewed:  https://review.openstack.org/538310
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2616b384e642b6eb58eef7da87b6e893f25a949e
Submitter: Zuul
Branch:    master"
1753401,2018-03-12 03:18:36 UTC,"Maybe you have seen this (?):
http://tavmjong.free.fr/blog/?p=822"
1753401,2018-03-12 06:19:19 UTC,Thanks for the explanation. What are some options to make it work?
1753407,2018-03-12 13:14:42 UTC,"several intermittent failures in this test:
 bug #1753407
 bug #1754021
 bug #1749709"
1753423,2019-09-20 15:01:54 UTC,This issue was fixed in the openstack/kolla-ansible ocata-eol release.
1753432,2018-06-08 19:56:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/573824"
1753432,2018-06-11 19:01:26 UTC,Patch for hacluster to provide support to update pacemaker's configuration. https://review.openstack.org/573039/
1753432,2018-06-11 19:02:55 UTC,Patch for charm-helpers to expose rabbitmq_port in AMQPContext class https://github.com/juju/charm-helpers/pull/187
1753432,2018-07-17 15:00:30 UTC,"Reviewed:  https://review.openstack.org/573039
Committed: https://git.openstack.org/cgit/openstack/charm-hacluster/commit/?id=02d83b2e4ead28c0f144f2e7495e0352843bf39e
Submitter: Zuul
Branch:    master"
1753432,2018-09-27 19:21:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605844"
1753432,2019-02-15 08:22:31 UTC,"Reviewed:  https://review.openstack.org/605844
Committed: https://git.openstack.org/cgit/openstack/charm-hacluster/commit/?id=639dadb141176eed3eaff6ba99b352c4ae5e1278
Submitter: Zuul
Branch:    master"
1753432,2019-04-01 11:00:12 UTC,Support for managing nova-consoleauth with corosync/pacemaker is being dropped in the next release of the charms (19.04) - https://github.com/openstack/charm-nova-cloud-controller/commit/b6e314077fa352ba58c346919a1e1cd4f6593226
1753432,2019-04-02 15:47:55 UTC,"Change abandoned by Felipe Reyes (<email address hidden>) on branch: master
Review: https://review.openstack.org/573824
Reason: single-nova-consoleauth config option is being removed in 19.04"
1753434,2018-10-31 07:51:45 UTC,"Reviewed:  https://review.openstack.org/613705
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f916a3ebd1e654221bdb65af37e70ec55d673883
Submitter: Zuul
Branch:    stable/queens"
1753434,2018-11-01 04:34:09 UTC,"Reviewed:  https://review.openstack.org/613706
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bdbcf5653afbea500394dd8b0a3a423f9e1eeed3
Submitter: Zuul
Branch:    stable/pike"
1753434,2018-10-26 23:21:25 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/613705"
1753434,2018-04-09 21:30:13 UTC,"Reviewed:  https://review.openstack.org/558012
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7c4da6fb756189e6afc1c699e06ce74488c61d45
Submitter: Zuul
Branch:    master"
1753434,2018-04-06 17:45:04 UTC,"Just an update, I tried to test this scenario on both  the CVR and DVR and I am seeing the same behavior.
It would be great if you can provide more info on reproducing the steps in here."
1753434,2018-10-26 23:22:58 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/613706"
1753434,2018-03-29 15:25:13 UTC,"Sorry let me take it back. Since it is for unbound floatingIP that traffic should be flowing through the SNAT Namespace.
Yes as you mentioned if the 'sg-' traffic is blocked, then you may not get any traffic from the subnet associated ports to the SNAT Namespace.
This need to be evaluated."
1753434,2018-03-29 15:08:19 UTC,"With Address scopes you don't need floatingIP. You can directly pass in the traffic. The traffic should be flowing through the FIP Namespace.
If you could give me more information on your test setup and how to reproduce this. It would be useful."
1753434,2018-03-29 15:02:53 UTC,"Let me check.
Do you have more info on how to reproduce this issue."
1753434,2018-03-31 00:24:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/558012"
1753438,2018-03-05 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1753438,2018-03-05 11:02:09 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1753438,2018-03-19 10:55:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1753438,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1753439,2018-05-11 01:14:47 UTC,"The verification was done by Redpine, ODM and one of the Beta customers."
1753439,2018-05-10 16:55:40 UTC,Could you please provide some information about how you verified the fix for xenial?
1753439,2018-04-30 17:39:18 UTC,"Hello Amitkumar, or anyone else affected,"
1753439,2018-04-13 19:19:48 UTC,@Shrirang - we have neither the firmware in linux-firmware nor the driver in the kernel for bionic. We cannot apply fixes for things which do not exist.
1753439,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1753439,2018-03-05 11:02:23 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1753439,2018-03-18 15:48:36 UTC,This firmware is required for in Bionic as well to support Dell Edge 300X devices in 18.04.
1753439,2018-03-05 12:05:07 UTC,"SRU Justification
================="
1753439,2018-03-05 11:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1753439,2018-05-16 01:53:39 UTC,This bug was fixed in the package linux-firmware - 1.157.18
1753439,2018-03-19 10:56:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1753439,2018-05-16 01:53:54 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1753442,2019-09-09 06:22:19 UTC,"I can no longer reproduce this failure locally under stress after hundreds of runs.
It seems that we have fixed the cause of this failure since we have last looked at this report."
1753443,2018-04-20 13:13:58 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1753443,2018-03-07 18:25:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550557"
1753443,2018-03-07 21:53:14 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/550557
Reason: not needed for queens since that still supports 4.x"
1753443,2018-03-05 10:59:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549737"
1753443,2018-03-07 17:26:59 UTC,"Reviewed:  https://review.openstack.org/549737
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b81a66b3b0b1ce9f56280dda40ac871132cb29f2
Submitter: Zuul
Branch:    master"
1753445,2019-09-09 06:51:09 UTC,"I can no longer reproduce this failure locally under stress.
It seems that we have fixed the cause of this failure since we have last looked at this report."
1753453,2019-09-09 06:53:18 UTC,We have done a bit of work in the area and this one is no longer in our codebase.
1753455,2019-09-09 07:11:56 UTC,We must have fixed the cause of this failure since it was reported. I cannot reproduce it locally under stress.
1753466,2018-06-07 01:47:48 UTC,"Hi Kris,"
1753466,2020-06-26 10:17:58 UTC,"As discussed in Victoria PTG, I created separate LP bugs to add OVS firewall and OVN support:
https://bugs.launchpad.net/neutron/+bug/1885261
https://bugs.launchpad.net/neutron/+bug/1885262"
1753466,2020-04-08 11:40:58 UTC,"Hi everyone, with the merge in of the fullstack tests and the CLI commands, I regard this RFE as implemented now. Please let me know if there are any concerns."
1753466,2019-12-03 12:00:27 UTC,"Reviewed:  https://review.opendev.org/696070
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=f470973446e8ef9b25f5a038c4c6f1fbd854f7a2
Submitter: Zuul
Branch:    master"
1753466,2019-11-26 11:55:57 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/696070"
1753466,2018-06-06 14:14:50 UTC,Hi
1753466,2018-05-29 08:49:32 UTC,"Hi @minsel,"
1753466,2020-12-23 01:16:53 UTC,Is there anyone going to implement ml2 OVS backend stateless security group without iptables?
1753466,2018-05-11 14:33:17 UTC,"This RFE was discussed during today's drivers meeting. We agreed in continuing it as part of FWaaS. With that, the RFE is approved"
1753466,2018-04-27 13:26:44 UTC,"@Giel,"
1753466,2018-03-19 08:11:26 UTC,I was wondering the same thing. Should this extension be implemented as a part of SG or FWaaS?
1753466,2018-03-16 03:40:48 UTC,We had a brief discussion about this RfE in the weekly FWaaS meetings as well (http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-03-15-14.00.log.txt) and we would like to combine efforts as minsel suggested. Let's make sure we don't duplicate work.
1753466,2018-03-15 23:34:52 UTC,"Yes, we discussed stateless firewalling with the FWaaS team in Dublin Friday morning. The FWaaS is on-board with it. I think this should be one effort"
1753466,2018-03-09 18:22:46 UTC,I was not aware of this actually. This RFE has been in the pipeline since before the PTG last week.
1753466,2018-03-09 17:59:01 UTC,The introduction of stateless firewalling (much like ACLs) was discussed at the Rocky PTG. Are you aware of this? There is interest in this as an addition to the FWaaS sub-component of Neutron however the extension of security groups was not discussed.
1753466,2018-05-10 22:56:14 UTC,"Stateless firewall is already being implemented by the Firewall team. Since we haven't heard from the submitter of this RFE, we will assume that approaching this from the FWaaS side is acceptable"
1753467,2018-04-24 23:27:01 UTC,"I don't think this text is ""from"" plymouth; I think it's from systemd.  TTBOMK we actually currently have no integration between systemd and plymouth, such that systemd is writing its own messages to the console; which happens to most of the time be hidden because the console is in graphical mode so you only see the plymouth splash."
1753467,2018-04-24 16:01:53 UTC,I was able to confirm this using today's image in a virtual machine. This bug was first reported with plymouth version 0.9.3-1ubuntu1 which a merge from Debian unstable.
1753467,2018-04-25 01:17:32 UTC,Here's a video of the problem I'm seeing with the vga driver with kvm.
1753467,2018-03-05 14:04:57 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1753467,2018-04-22 15:28:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753486,2019-09-20 11:56:19 UTC,With the transition to making MAAS a snap we have went down this path:
1753489,2018-03-05 14:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1753489,2018-04-05 19:51:15 UTC,reference:  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754053
1753489,2018-03-30 18:52:59 UTC,"I believe this occurred while running disk/disk_stress_ng_dm-1 from the certification test suite on the system in our lab called ""seuss"", which had been installed manually w/ d-i, using LVM w/ crypted home. (I dug that info out of LP: #1749040, from whence this bug was spawned)."
1753490,2020-01-26 13:51:05 UTC,https://github.com/mixxxdj/mixxx/pull/2379
1753495,2018-03-08 03:07:11 UTC,"Hi Emmanuel,"
1753495,2018-09-19 06:26:14 UTC,"Hi Afshan,"
1753498,2018-03-05 14:25:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549773"
1753498,2018-03-07 09:08:36 UTC,"Reviewed:  https://review.openstack.org/549773
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=49fea478ee6d2fe67f6c248b8da9b0ce910184f8
Submitter: Zuul
Branch:    master"
1753504,2018-03-11 00:34:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551721"
1753504,2018-03-11 00:34:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551722"
1753504,2018-03-11 00:34:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551724"
1753504,2018-03-11 00:34:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551720"
1753504,2018-03-11 00:34:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551723"
1753504,2018-03-09 00:19:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551037"
1753504,2018-05-14 16:48:24 UTC,This issue was fixed in the openstack/neutron-vpnaas-dashboard 1.3.0 release.
1753504,2018-03-08 19:41:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550986"
1753504,2018-03-07 23:46:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550647"
1753504,2018-03-07 23:04:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550641"
1753504,2018-03-05 14:27:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549774"
1753504,2018-03-05 14:26:45 UTC,"neutron-vpnaas-dashboard patches:
https://review.openstack.org/#/c/549651/
https://review.openstack.org/#/c/549652/"
1753504,2018-03-13 09:43:53 UTC,"Reviewed:  https://review.openstack.org/550641
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=03c5c1f537bdb31f1014721d0c07660b8c74f75b
Submitter: Zuul
Branch:    master"
1753504,2018-03-08 20:49:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551000"
1753504,2018-03-13 09:49:43 UTC,"Reviewed:  https://review.openstack.org/550647
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=06961da731611fa813e8e4c6cd63a660d17d68d2
Submitter: Zuul
Branch:    master"
1753504,2018-03-15 18:01:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553540"
1753504,2018-03-15 18:17:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553573"
1753504,2018-03-25 18:12:40 UTC,"Reviewed:  https://review.openstack.org/549774
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/commit/?id=4ae1508604a00df70b57d331c4f56d4069711cac
Submitter: Zuul
Branch:    master"
1753504,2018-03-26 13:36:12 UTC,"Reviewed:  https://review.openstack.org/555469
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=f6b1e85899acd20f8a08a8302542497f2b4977ae
Submitter: Zuul
Branch:    master"
1753504,2018-03-26 17:44:12 UTC,"Reviewed:  https://review.openstack.org/555477
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=ac24ab19c3a5ab71036c6f5447a904d022dec73c
Submitter: Zuul
Branch:    master"
1753504,2018-03-27 23:59:00 UTC,"Reviewed:  https://review.openstack.org/551720
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/commit/?id=8825c3cd5c753e85524654b5be5645a8f45f314d
Submitter: Zuul
Branch:    master"
1753504,2018-04-03 14:20:29 UTC,"Reviewed:  https://review.openstack.org/551721
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/commit/?id=b17392b5fa37a4bed1159d86f06f07e451aab41d
Submitter: Zuul
Branch:    master"
1753504,2018-04-19 14:10:39 UTC,This issue was fixed in the openstack/networking-midonet 7.0.0.0b1 development milestone.
1753504,2018-04-03 14:20:47 UTC,"Reviewed:  https://review.openstack.org/551723
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/commit/?id=6cd9d487ed9dba893a8946a24c221312dde01b03
Submitter: Zuul
Branch:    master"
1753504,2018-03-25 18:06:52 UTC,"Reviewed:  https://review.openstack.org/549652
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/commit/?id=6cbdee8340734962912657057875a91a0f3214ae
Submitter: Zuul
Branch:    master"
1753504,2018-04-03 16:05:12 UTC,"Reviewed:  https://review.openstack.org/551724
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/commit/?id=6faaf2cad7a77ff830c632848009c6aa035ada2a
Submitter: Zuul
Branch:    master"
1753504,2018-04-03 22:14:06 UTC,This issue was fixed in the openstack/python-neutronclient 6.8.0 release.
1753504,2018-04-10 16:52:27 UTC,The 'networking-vSphere' project is also affected by this 'mox/mox3' change.
1753504,2018-04-11 15:10:34 UTC,"Reviewed:  https://review.openstack.org/558621
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=e93a57d5323464f3f2e5660e606ab92f5ea2b77a
Submitter: Zuul
Branch:    master"
1753504,2018-04-11 16:58:33 UTC,"Patch submitted for networking-vsphere repo.
https://review.openstack.org/#/c/560165/"
1753504,2018-04-11 17:12:55 UTC,"Reviewed:  https://review.openstack.org/560165
Committed: https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=424629c8330d737cb5f479308c6e7f34d711c1e5
Submitter: Zuul
Branch:    master"
1753504,2018-04-11 19:59:56 UTC,"This bug is used to track official projects under the neutron governance. We have completed the mox-removal community goal as ""neutron"" project."
1753504,2018-05-14 16:48:50 UTC,This issue was fixed in the openstack/neutron-fwaas-dashboard 1.4.0 release.
1753504,2018-04-03 19:40:59 UTC,The remaining project with mox3 is now networking-midonet. We need a new release for python-neutronclient so that networking-midonet test consumes a new testing interface from python-neutronclient.
1753504,2018-03-25 18:06:44 UTC,"Reviewed:  https://review.openstack.org/549651
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/commit/?id=0087e89e444bcb8bd3961c889d046fe1295841f0
Submitter: Zuul
Branch:    master"
1753504,2018-04-03 14:20:38 UTC,"Reviewed:  https://review.openstack.org/551722
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/commit/?id=58804c1e994155b570b61ddaf81237a8ce37c483
Submitter: Zuul
Branch:    master"
1753504,2018-03-24 10:25:12 UTC,"Reviewed:  https://review.openstack.org/553878
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=260f74308e3c78d3e1561280578f03cb5612ff4f
Submitter: Zuul
Branch:    master"
1753504,2018-03-24 13:33:49 UTC,"Reviewed:  https://review.openstack.org/553883
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=ce623030ee19619eb28276e6f9f0a395261560ba
Submitter: Zuul
Branch:    master"
1753504,2018-03-15 20:50:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553609"
1753504,2018-03-15 23:22:50 UTC,"Reviewed:  https://review.openstack.org/551000
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=d8a605c591e3fcd049925d1911d7314965739d0c
Submitter: Zuul
Branch:    master"
1753504,2018-03-16 18:03:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553871"
1753504,2018-03-16 18:13:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553872"
1753504,2018-03-16 18:43:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553878"
1753504,2018-03-16 19:30:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553883"
1753504,2018-03-22 09:35:11 UTC,"Reviewed:  https://review.openstack.org/551037
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=c50b1267710fdc0585a8618c6f9513bd0f3a6161
Submitter: Zuul
Branch:    master"
1753504,2018-03-16 18:43:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553877"
1753504,2018-03-22 09:35:26 UTC,"Reviewed:  https://review.openstack.org/553573
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=02b6e6f841dcc262fb42e88d5ead06025edb0190
Submitter: Zuul
Branch:    master"
1753504,2018-03-22 21:54:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555469"
1753504,2018-03-22 22:05:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555477"
1753504,2018-03-23 18:29:31 UTC,"Reviewed:  https://review.openstack.org/553609
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=5a0d8c8b907f4ebbe5a1d7f8b0704ecdd7170a54
Submitter: Zuul
Branch:    master"
1753504,2018-03-23 20:34:56 UTC,"Reviewed:  https://review.openstack.org/553871
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=bcce41e8478e92c0b9b60c2dd91b826d687264ef
Submitter: Zuul
Branch:    master"
1753504,2018-03-24 01:02:11 UTC,"Reviewed:  https://review.openstack.org/553872
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=633a20cde9a282f17b59d120f5c97e3989e6cec1
Submitter: Zuul
Branch:    master"
1753504,2018-03-24 07:39:13 UTC,"Reviewed:  https://review.openstack.org/553877
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=8dac1afd43481d9c9ffcde3674eed3f7c64896ab
Submitter: Zuul
Branch:    master"
1753504,2018-03-22 09:35:19 UTC,"Reviewed:  https://review.openstack.org/553540
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=93e4ef2e7de95aa16e13331df14b2d157c9a24a5
Submitter: Zuul
Branch:    master"
1753504,2018-03-15 23:11:25 UTC,"Reviewed:  https://review.openstack.org/550986
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=f2abd8ce1645984ab5a2f5f267527fb3b386814b
Submitter: Zuul
Branch:    master"
1753506,2018-03-05 14:28:17 UTC,"Also saw this in a real environment using ironic-inspector @ master, with the lldp_basic and local_link_connection plugins enabled. It prevented inspector from starting up. Disabling these plugins allowed inspector to start."
1753506,2018-03-05 20:05:47 UTC,"Note the Warning in the docs for construct here for 2.9:
https://construct.readthedocs.io/en/latest/transition29.html"
1753506,2018-03-07 17:58:00 UTC,Bob's fix in requirements: https://review.openstack.org/#/c/549866/
1753509,2019-04-29 10:46:58 UTC,"I have the same problem. Setting ""CreateIPPPrinterQueues"" to ""No"" doesn't change anything."
1753509,2018-03-07 09:05:02 UTC,"This is not a bug of Avahi, Avahi is only handling the DNS-SD broadcasts. The queues are created by cups-browsed and which queues are exactly created can be configured in /etc/cups/cups-browsed.conf."
1753509,2018-03-07 09:33:35 UTC,"Note that the default setting for ""CreateIPPPrinterQueues"" in Ubuntu is ""Driverless""."
1753509,2020-11-01 17:00:16 UTC,"This bug surely does not belong to ""cups-filters"" package. And probably it does not belong to Avahi. And to CUPS either. This bug does belong to GTK library and GTK apps which do not provide an option like ""list only local CUPS printers, not everything Avahi has sniffed on the network""."
1753509,2019-05-13 13:12:07 UTC,"Hallo, same problem here. I set cups.conf to
Browsing Off
BrowseLocalProtocols none"
1753509,2019-07-13 04:18:05 UTC,[Expired for cups-filters (Ubuntu) because there has been no activity for 60 days.]
1753509,2019-07-26 20:11:16 UTC,"Did everyone just give up? I'm still trying to solve this and I have a thread going on over at MX Linux.
https://forum.mxlinux.org/viewtopic.php?f=108&t=51567"
1753509,2019-10-16 20:22:50 UTC,"Same happening for me in 18.04. I just removed cups-browsed service. In localhost:631 those ""unwanted"" printers are gone, but in the rest of applications (like firefox, chrome, etc), still there."
1753509,2019-11-19 22:22:40 UTC,I could get rid of the auto browsing/adding with the following:
1753509,2020-03-05 19:19:50 UTC,Thank you for the step by step procedure jrgsampaio.  I just followed it with the trivial modification to edit cupsd.conf instead of cups.conf.
1753509,2020-04-06 20:02:00 UTC,"This is one of the most stupid default behaviors I have encountered.  Out of the several colleagues and family members who use linux (it is used quite a bit in a university environment), they are ALL (down to the last one) very annoyed at this behavior.  The problem is that you have your laptop open, and ""Becca"" from your calculus class comes in to your office and opens her Macbook, and my laptop adds a printer.  Then ""Chad"" (he's not even in your class) just opens their Macbook in the hallway, and you gain a new printer again.  After a couple of months, it is a couple of hundred added printers, though they are all grayed out in the list when trying to print.  Even though Chad will never visit the department again, his macbook is in my printer list forever. Just picking one of the actual working printers becomes difficult since it involves scrolling through a long list of gray printers to find the one nongray one in the middle.  Deleting them is actually quite annoying to do through the GUI and it is not at all obvious."
1753509,2020-11-01 17:06:42 UTC,please also refer to lp:1379359 and to the GTK2/3 patch at https://launchpad.net/~roman-shipovskij/+archive/ubuntu/gtk+3.0-withoutavahiprinters
1753509,2019-04-29 13:29:17 UTC,Could you please try the following:
1753509,2019-04-29 10:47:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753510,2018-08-11 08:52:22 UTC,"Ok, please try this kernel:
https://people.canonical.com/~khfeng/linux-image-4.18.0-rc1+_4.18.0-rc1+-1_amd64.deb"
1753510,2018-03-08 16:14:17 UTC,"I tried rcu_nocbs=0-7  as and argument booting the march 3rd daily iso.
(reported as helping by one user on phoronix) but no change."
1753510,2018-06-17 17:35:29 UTC,"tried 4.18.rc1 rcu_nocbs=0-3:   crashes into initramfs as before.
with rcu_nocbs=0-7: it goes into some sort of infinite loop spewing registers on the console."
1753510,2018-06-17 17:46:01 UTC,"Have you tried kernel parameter ""nomodeset""?"
1753510,2018-06-20 01:43:41 UTC,"tried nomodeset.  now there is no mode set while booting, and goes into a boot loop.
then updated motherboard bios (april one.) repeat, and now it crashes to (initramfs)"
1753510,2018-07-21 04:07:05 UTC,"tried again 4.17.4 upstream and mesa 18.2 from oibaf.  no change.
when I am lucky, I get into (initramfs) prompt."
1753510,2018-07-25 09:30:43 UTC,"Can you see what's wrong in dmesg, when in the initramfs prompt?"
1753510,2018-07-25 12:40:03 UTC,"I cannot get into initramfs anymore... it just loops during boot. image attached.
similar image available for 4.17.4 if desired."
1753510,2018-07-25 13:40:56 UTC,"For Ryzen APU, is it possible to try latest mainline, 4.18-rc6?
For Radeon 7850, try kernel parameter ""radeon.si_support=0 amdgpu.si_support=1"""
1753510,2018-07-29 04:44:30 UTC,"the crash that prompted with initramfs, but accepted no keyboard input,
then kept printing some messages a few minutes later."
1753510,2018-06-11 11:16:59 UTC,"yes:  4 Cores/8 Processing Threads,  I tried 0-7 and 0-3.  0-7 crashes worse than 0-3.  I could imagine the number being related to cores, rather than threads."
1753510,2018-07-29 04:48:37 UTC,"did a series of boots with 4.18.rc6, rcu=0-3, rcu=0-7, from power off, from reset (behaviour is always different from power on versus when starting from a reset.) applied the radion and amdgpu options above, no success.  The behaviour varies (sometimes hang, sometimes crash, sometimes loop infinitely, once in a while get to initramfs prompt.)"
1753510,2018-07-30 13:45:31 UTC,"upgraded everything: firmware, mesa, kernel (rc7.)  Now it crashes.
First crash was different from subsequent ones."
1753510,2018-07-30 13:46:06 UTC,subsequent crashes look more like this
1753510,2018-08-04 07:31:07 UTC,Have you tried latest amdgpu [1]?
1753510,2018-08-05 13:53:52 UTC,"It''s on my disk checked out, but this is a whole kernel... not sure how to
get correct configs and such."
1753510,2018-08-05 14:02:54 UTC,trying this for now: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
1753510,2018-08-05 23:55:18 UTC,"dpkg-source: info: use the '3.0 (quilt)' format to have separate and
documented changes to upstream files, see dpkg-source(1)
dpkg-source: error: unrepresentable changes to source
dpkg-buildpackage: error: dpkg-source -i.git -b linux subprocess returned
exit status 1
scripts/package/Makefile:71: recipe for target 'deb-pkg' failed"
1753510,2018-08-11 12:59:42 UTC,"if it is of interest, I could buy a USB debugging cable and give you
access...
saw this:
https://www.kernel.org/doc/html/v4.17/driver-api/usb/usb3-debug-port.html
but I would have to order the cable.   Recommendations welcome."
1753510,2018-09-03 15:34:15 UTC,"tried again with 4.19rc2. Stripped off all other usb peripherals (including existing mouse & kb), only had the internal (windows) SSD and the usb one I am plugging in.  Now using a logitech K400 or so, which seems compatible with everything.  When I boot, it dumps me into (initramfs) prompt, and I can use it.  If I do ls /dev, I see sda, sda1, sda2, sda3 and no other disk partitions. When I try to mount them, I find they are the windows SSD that is SATA connected.  It doesn't see the externally USB connected drive."
1753510,2018-07-29 04:50:37 UTC,"I also tried booting with none of the workarounds (no_spectrev2,  rcu_cbs, radio, amdgpu) it looped on boot. just like back in 4.15."
1753510,2018-06-11 04:09:45 UTC,Isn't Ryzen 2400G a 8 threads processor?
1753510,2018-08-11 12:24:47 UTC,during dpkg -i :
1753510,2018-06-10 03:11:04 UTC,"Entry should be  'rcu_nocbs=0-3'. Typo, cheers
bob"
1753510,2018-03-11 16:39:42 UTC,tried again with 03/11 daily after beta announcement. No change.
1753510,2018-03-11 16:41:20 UTC,"based on this: http://iso.qa.ubuntu.com/qatracker/milestones/387/builds
syslinux looks more promising/appropriate."
1753510,2018-06-10 21:43:04 UTC,"OK, now it dumps into the (initramfs) prompt but at least it doesn´t crash just sitting at that prompt. any suggestions what to do once at the initramfs prompt?"
1753510,2018-05-09 16:09:58 UTC,Are you still having this issue with the final release?
1753510,2018-05-09 16:27:07 UTC,yes.
1753510,2018-05-09 18:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1753510,2018-05-10 16:02:15 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1753510,2018-06-01 23:35:40 UTC,"OK, took the boot disk out, and installed the 4.17-rc7 from the above location, and it still does not work. same loop as before."
1753510,2018-06-01 23:51:30 UTC,"I mean I put it in a usb enclosure, so now I can move it to a PC that I can boot linux on, and make changes, and then easily move it back to try booting.  so easy to test now."
1753510,2018-05-10 18:49:04 UTC,"I can only boot in windows... cannot boot in ubuntu to choose the custom kernel.
any idea how to adjust an installation image to use a custom kernel?"
1753510,2018-06-03 13:49:31 UTC,"now I can switch the disk between working and broken computers, I can provide logs... here is the last 100 lines of kern.log with 2.17-rc7:"
1753510,2018-06-07 03:00:30 UTC,tried with nospectre_v2 rcu_nocbs=0-7
1753510,2018-06-07 04:11:07 UTC,The amdgpu driver in Bionic is not new enough.
1753510,2018-06-08 01:34:12 UTC,"OK updated firmware, including amdgpu."
1753510,2018-06-08 02:27:32 UTC,"with 4.17  (is that what is meant by ""mainline"" )"
1753510,2018-06-08 18:54:13 UTC,"Did you upgrade the initramfs after firmware update?
Run `sudo update-initramfs -u -k all`."
1753510,2018-06-08 23:32:06 UTC,OK did that.  the crash is a little different.
1753510,2018-06-10 03:08:36 UTC,"HI, I have Gigabyte ab350n wifi m/b and 2400g cpu. Dual booting has been an issue but I found that the booting process identified 8 compute units but it appeared the kernel wasn't accepting the count so 'rcu_nocbs=03"" placed on kernel load line in grub improved later part of initiation. ( The 0-7 parameter dids not work for me)"
1753510,2018-06-02 00:00:27 UTC,"I tried to mark the report confirmed, but couldn´t because I am the original reporter.. I guess."
1753511,2018-12-24 06:44:48 UTC,"In case this helps anyone - restarting the neutron_server container on all controllers, and then restarting the neutron_openvswitch_agent container on all compute nodes, solved the issue."
1753511,2018-05-21 00:58:09 UTC,"I had the same issue with kolla/centos-binary-neutron-openvswitch-agent:pike. I am also using multinode deployment with default parameters in global.yml (except for the network ips) and openstack_release: ""pike""."
1753511,2018-08-14 10:16:36 UTC,same here im using ocata though any fix ?
1753511,2018-10-26 14:16:50 UTC,"I'm seeing the same issue on rocky, does anyone have a fix for this?"
1753511,2018-12-24 05:36:13 UTC,Configuration:  Kolla-Ansible 7.0.0 release on CentOS 7.5
1753512,2018-03-14 10:48:25 UTC,worst case the 'juju run APP crashdump' action could report a path-on-disk and then you would juju scp UNIT /path .
1753512,2018-03-19 15:12:05 UTC,"Yeah - this seems reasonable.  juju crashdump can check for the
existence of the crashdump action and go from there."
1753512,2018-03-06 07:15:54 UTC,"Having a standard, common action that charms implement seems like a good
way forward on this. Then juju-crashdump can see if the, eg,
""debugging-logs"" hook is available for the charm and call it to get
additional information to include.
I believe there is still some rough edges around actions being able to
produce file content that can be downloaded separately, but something along
those lines seems like a reasonable standard."
1753512,2018-03-14 10:47:32 UTC,"overall, this seems more like convention than something Juju needs to implement. Though its possible we would need to polish how we handle large-content-blobs in actions."
1753513,2018-03-05 14:58:58 UTC,mcatanzaro said
1753525,2018-09-06 19:55:50 UTC,This is definitely not a ubuntu specific bug.
1753525,2018-08-24 17:43:58 UTC,Ubuntu 18.04.1
1753525,2018-09-06 16:27:52 UTC,"The same problem: 056a:00d1 Wacom Co., Ltd Bamboo Pen & Touch (CTH-460-DE)"
1753525,2018-09-06 16:33:34 UTC,"And the same with ID 056a:00d4 Wacom Co., Ltd Bamboo Pen (CTL-460)"
1753525,2018-06-12 13:26:53 UTC,"Same with me, on two different CPUs (old 2009 macbook and an amd desktop) both running 18.04."
1753525,2018-09-06 16:34:24 UTC,"In both cases the tablets are recognized, but not styluses"
1753525,2018-09-06 17:55:48 UTC,I have check this with latest installation image of 18.10. The situation is even worse there. Attempt to detect a stylus crashes the ubuntu session in 18.10.
1753525,2018-09-06 19:56:31 UTC,I mean with
1753525,2018-10-29 16:00:43 UTC,if that's still an issue for some configs on Ubuntu (GNOME) 18.04/18.10 the best would be to report it upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues
1753525,2018-09-11 01:31:23 UTC,I just attempted the upgrade from 16.04 to 18.04 and have this issue as well.
1753525,2018-09-16 13:17:45 UTC,"I am the same problem that
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/comments/34"
1753525,2018-10-22 06:57:53 UTC,"same here Ubuntu 18.04, Wacom ISDv4 104, builtin i2c tablet work but no stylus setting"
1753525,2018-10-27 20:06:00 UTC,My CTL-4100 just works on propperties setting on Unity
1753525,2020-07-16 05:49:16 UTC,"on Jul 16 2020 I still have the same problem. The pad is perfectly recognized when using terminal commands but not detected in the device dialog under settings>devices>Wacom Tablet. When I hit Test your settings I can input but have to use high pressure. I did install the most recent drivers from source following this link https://linuxwacom.github.io/ , installing input wacom from source and building the Xdriver. Installing input wacom went without error messages and installing the Xdriver gave the message that the installed driver is already the newest one. When I try to use the tablet with Xournal it sometimes works and sometime doesn't rebooting usually fixes the ""not working"". ""Not working"" symptoms are: when drawing a line it gets interrupted, the pressure has to be extremely high, the cursor jumps around wildly, switching between eraser and pen is not controllable, the cursor can not be mapped to a specific monitor. I am on Ubuntu 18.04.3 The tablet is a Wacom Intuos BT S The output from xsetwacom --get ""Wacom Co.,Ltd. Intuos BT S stylus"" all is:
Option ""Area"" ""0 0 15200 9500""
Button: Actions are not supported by xorg.conf. Try shell format (-s) instead.
Button: Actions are not supported by xorg.conf. Try shell format (-s) instead.
Button: Actions are not supported by xorg.conf. Try shell format (-s) instead.
Button: Actions are not supported by xorg.conf. Try shell format (-s) instead.
Option ""DebugLevel"" ""0""
Option ""CommonDBG"" ""0""
Option ""Suppress"" ""2""
Option ""RawSample"" ""4""
Option ""PressCurve"" ""0 0 100 100""
Option ""Mode"" ""Absolute""
Option ""TPCButton"" ""off""
Option ""Touch"" ""off""
Property 'Wacom Hardware Touch Switch' does not exist on device.
Option ""Gesture"" ""off""
Option ""ZoomDistance"" ""0""
Option ""ScrollDistance"" ""0""
Option ""TapTime"" ""250""
Property 'Wacom Proximity Threshold' does not exist on device.
Option ""Rotate"" ""none""
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Option ""Threshold"" ""26""
Option ""Serial"" ""0""
Option ""PressureRecalibration"" ""on""
Option ""PanScrollThreshold"" ""1300"""
1753525,2020-07-26 20:38:13 UTC,"Reporting the bug from ubuntu  18.04.4 LTS. The tablet works and the pointer moves as expected but the settings->devices->wacom configuration does not recognize the tablet. Also, I report this same tablet and same computer was working properly before, but not sure if it was on 18.04 or 19.something. The thing is it was working well before doing a clean reinstall of 18.04.4"
1753525,2020-07-26 21:21:35 UTC,"Solved after deleting custom installation of lib-wacom and then installing xserver-xorg-input-wacom, libwacom2, and libwacom-common. Showing on the settings page after rebooting."
1753525,2018-05-28 16:31:18 UTC,"Hi, I am in Ubuntu 18.04 release, my wacom model is Wacom Cintiq 15x PL-550, I can use the tablet, but I can not calibrate, set buttons stylus, etc."
1753525,2018-09-08 10:14:45 UTC,since upgrade from 16.04 to 18.04  I have this issue.
1753525,2018-04-12 14:25:13 UTC,"and by
libwacom-list-local-devices
[Device]
Name=Wacom Serial Tablet WACf004
DeviceMatch=serial:0000:0000;
Class=ISDV4
Width=0
Height=0
IntegratedIn=Display;System;
Styli=0xfffff;0xffffe;"
1753525,2018-08-22 15:01:22 UTC,"every new version of ubuntu you make me cry with this damn graphic tablet.
please update the list of graphics tablets"
1753525,2018-04-12 14:03:18 UTC,"The Wacom Intuos S Tablet (Model: ctl 4100) is not recognised in the wacom section in the gnome control center on ubuntu bionic, though basic mouse functionality works."
1753525,2018-03-05 19:53:10 UTC,"The ""stylus not recognized"" part of this issue is almost certainly https://bugzilla.gnome.org/show_bug.cgi?id=793499."
1753525,2018-03-05 20:18:21 UTC,@Jason Gerecke
1753525,2018-03-05 20:44:06 UTC,@Jason Gerecke
1753525,2018-03-05 20:46:23 UTC,Programming the tablet
1753525,2018-03-05 20:47:47 UTC,Map tablet buttons
1753525,2018-03-05 20:50:37 UTC,Tablet buttons menu that opens when button is klicked.
1753525,2018-03-06 09:37:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1753525,2018-03-06 17:36:29 UTC,@Sebastien Bacher:
1753525,2018-03-05 19:40:31 UTC,"My solution, sort of:"
1753525,2018-03-06 18:10:18 UTC,Edit: to be more precise on my tablet:
1753525,2018-03-07 17:57:47 UTC,Here is the link: https://bugzilla.gnome.org/show_bug.cgi?id=794159
1753525,2018-03-07 21:05:29 UTC,"It is not a Gnome issue, it is an Ubuntu issue: https://bugzilla.gnome.org/show_bug.cgi?id=794159#c1"
1753525,2018-03-11 19:30:41 UTC,"Usually I use my Wacom Intuos CTH-450/K with Gimp. Now I tested it with Krita. Seems that all functions of the board are supported, including varying line width with varying stylus pressure. But only after I installed gnome, see above https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/comments/2
This will still give the developers something to work till April."
1753525,2018-03-15 21:18:54 UTC,Correction: my graphics tablet is a > CTH-490/K <
1753525,2018-03-19 17:39:04 UTC,"linuxcub, my apologies for not replying sooner -- I don't think I got a notification of your messages for some reason..."
1753525,2018-04-12 13:46:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753525,2018-04-12 14:01:31 UTC,"The Wacom Intuos S Tablet (Model: ctl 4100) is not recognised in the wacom section in the control center, though basic mouse functionality works."
1753525,2018-03-07 08:14:16 UTC,You can use that url directly https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-control-center
1753525,2018-04-12 14:04:45 UTC,"By the linux kernel (again on ubuntu bionic) it's recognised as:
lsusb
Bus 001 Device 002: ID 056a:0374 Wacom Co., Ltd"
1753528,2018-03-31 20:52:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753528,2018-03-07 20:23:57 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7efbfdc7eb9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7efbfdc7ccba ""corrupted double-linked list"") at malloc.c:5350
 _int_malloc (av=av@entry=0x7efbe4000020, bytes=bytes@entry=6) at malloc.c:3926
 __GI___libc_malloc (bytes=bytes@entry=6) at malloc.c:3065
 g_malloc (n_bytes=6) at ../../../../glib/gmem.c:99"
1753534,2018-03-05 22:51:10 UTC,"I can reproduce this in Inkscape 0.92.2, on Windows 7 Pro, 64-bit"
1753534,2018-03-06 13:08:05 UTC,Maybe you have seen this:
1753534,2018-03-06 13:52:48 UTC,"You are missing the main point here, let me rephrase:"
1753534,2018-03-07 03:11:21 UTC,This is the same for text on any path.
1753534,2020-09-09 22:56:25 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1753535,2018-03-05 17:15:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/549824"
1753535,2020-07-15 19:43:14 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.opendev.org/549824
Reason: Abandoning since there hasn't been any recent activity, if anyone wants to continue this work, please feel free to restore this."
1753536,2018-11-16 03:27:40 UTC,I want to add that Dan Pearl is working on adding the org. unit setting to control whether or not this field displays in the OPAC. That seems to be the last outstanding request for this feature.
1753536,2018-11-16 14:54:02 UTC,Is there a decision for the field to use the owning library or the checkout library?
1753536,2018-11-16 15:17:56 UTC,"After a long discussion, it seems that Owning Library (as implemented) is most useful, as long as there is an org setting to turn it off.  I understand there is some justification to add a choice of which data to use if this doesn't do the job (in a future? LP)."
1753536,2018-11-16 17:16:59 UTC,Owning library will work well for us.  Thanks.
1753536,2018-11-30 17:01:15 UTC,Here is the branch that controls this feature via an org unit setting.
1753536,2019-04-29 22:52:22 UTC,For Sitka we'd definitely prefer to display circ_lib over owning lib.  We have a significant number of libraries doing interlibrary loan through Evergreen and showing owning library to patrons for items from other libraries that they borrowed through their home library and need to return to their home library would confuse patrons.
1753536,2018-12-03 15:30:56 UTC,"It works for me, so I pushed a signoff branch to working/user/dyrcona/lp1753536_optional_owning_lib-signoff"
1753536,2019-04-29 22:12:37 UTC,"The release notes as written are a little misleading, as it is not universally the case that the owning library's policies control renewals."
1753536,2019-09-06 16:34:19 UTC,"Pushed to master for inclusion in 3.4. Thanks, Dan and Jason!"
1753536,2019-04-30 13:11:36 UTC,"Jennifer, my understanding is that in this case, circ_lib is the circ_lib from the asset.copy. Unfortunately, both the asset.copy and action.circulation tables have columns with that name and they mean different things.  If you want the action.circulation.circ_lib to display, that is not the intention of this enhancement and would complicate this setting further."
1753536,2019-05-13 18:19:43 UTC,"I have rebased my signoff branch from comment #22 on master, updated the release note, and force-pushed to the same branch."
1753536,2018-11-30 17:28:27 UTC,http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dpearl/LP1753536_optional_owning_lib
1753536,2018-11-13 13:23:05 UTC,I agree with the suggestions in comment #5.
1753536,2018-11-16 03:09:10 UTC,Removing pullrequest tag while there is still ongoing discussion for this feature's future.
1753536,2018-08-28 18:47:26 UTC,Our circ policies are mostly decided by the checkout library and the checkout library is responsible for overdue and lost issues. Patrons are supposed to contact the checkout library for renewal.
1753536,2018-10-24 23:33:24 UTC,Changed the target to 3.next because this is a new feature.
1753536,2018-03-22 19:46:49 UTC,"I'm not in love with the column header, but I think it connects with patrons."
1753536,2018-03-30 15:48:28 UTC,"I just pushed a rebased, signed off branch to working/user/dyrcona/LP1753536_lib_column-signoff:"
1753536,2018-03-30 16:40:23 UTC,"Looking at the release notes, it says:"
1753536,2018-03-30 17:35:11 UTC,"I can see changing the label to Owning Library and using the call number owning library as being viable. This feature could be more complicated, as the answer to whom should I call for more renewals is ""it depends."" This is something that we were asked to do as a local customization, but that I thought could have broader application in the community."
1753536,2018-03-30 16:18:45 UTC,"I wonder if this shouldn't use the call number owning lib, instead of the copy circ lib. Especially in the face of floating groups, the latter isn't really the owner but the ""current home""."
1753536,2018-04-05 18:23:59 UTC,OK I have made the changes and pushed to user/dpearl/LP1753536_lib_column_respin
1753536,2018-04-05 20:20:47 UTC,Here's a fixed git branch.  It just needed a 'git rebase origin/master'.  I also added Dan's sign-off to the top commit.
1753536,2018-04-05 20:35:58 UTC,"Thanks, Remington.  It looks like it is all there."
1753536,2018-08-08 18:57:57 UTC,This wishlist item is lonely and could use a reviewer.  It's relatively easy to test.
1753536,2018-08-23 20:32:52 UTC,"I have confirmed the code works as expected and pushed a new rebase/sign-off branch, including some commit message tweaks on the 2nd commit:"
1753536,2018-03-30 18:44:42 UTC,"I'm a +1 to the above proposal, with or without the org unit setting."
1753538,2019-12-17 22:33:40 UTC,"FYI, the upstream Charms Deployment Guide now includes instructions for achieving the desired goal via the policyd overrides feature of the OpenStack Charms."
1753541,2018-03-07 18:07:26 UTC,The serial number of the printer is surely given by iSerial 3 000000000Q87Q2ZCPR1a. Is this shown in the URI for the HP-LaserJet-Professional-P1102 queue when it is the only print queue shown by system-config printer and 'lpstat -t'?
1753541,2018-03-08 06:53:26 UTC,Many thanks to brian_p! The solution with the removal of system-config-printer-udev solved my problem in Debian!
1753541,2018-03-08 00:11:58 UTC,I can now reproduce your observations.
1753541,2018-03-07 21:58:40 UTC,"LC_ALL=en_US.UTF-8 inxi -Fxz
System:    Host: debian Kernel: 4.9.0-6-amd64 x86_64 (64 bit gcc: 6.3.0)
           Desktop: Xfce 4.12.3 (Gtk 2.24.30)
           Distro: Debian GNU/Linux 9 (stretch)
Machine:   Device: laptop System: ICL product: RAYbook Bi1010
           Mobo: Notebook model: W51PU
           UEFI: American Megatrends v: 5.12 date: 04/05/2017
Battery    BAT0: charge: 26.8 Wh 100.0% condition: 26.8/28.0 Wh (96%)
           model: Notebook BAT status: Full
CPU:       Quad core Intel Celeron N3450 (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 8755
           clock speeds: max: 2200 MHz 1: 1508 MHz 2: 1295 MHz 3: 1399 MHz
           4: 1206 MHz
Graphics:  Card: Intel Device 5a85 bus-ID: 00:02.0
           Display Server: X.Org 1.19.2 drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.00hz
           GLX Renderer: Mesa DRI Intel HD Graphics 500 (Broxton 2x6)
           GLX Version: 3.0 Mesa 13.0.6 Direct Rendering: Yes
Audio:     Card Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Audio Cluster
           driver: snd_hda_intel bus-ID: 00:0e.0
           Sound: Advanced Linux Sound Architecture v: k4.9.0-6-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 01:00.1
           IF: enp1s0f1 state: down mac: <filter>
           Card-2: Intel Device 24fb driver: iwlwifi bus-ID: 02:00.0
           IF: wlp2s0 state: up speed: N/A duplex: N/A mac: <filter>
Drives:    HDD Total Size: 500.1GB (19.7% used)
           ID-1: /dev/sda model: HGST_HTS545050B7 size: 500.1GB
Partition: ID-1: / size: 28G used: 8.3G (32%) fs: ext4 dev: /dev/sda5
           ID-2: /home size: 189G used: 1.7G (1%) fs: ext4 dev: /dev/sda7
           ID-3: swap-1 size: 4.12GB used: 0.19GB (5%) fs: swap dev: /dev/sda6
Sensors:   System Temperatures: cpu: 55.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 173 Uptime: 4:51 Memory: 1054.2/3788.7MB
           Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (zsh 5.3.1) inxi: 2.3.5"
1753541,2018-03-07 17:24:08 UTC,"After my attempts to update hplip and return to the original state:
LC_ALL=en_US.UTF-8 lpstat -t
scheduler is running
system default destination: HP-LaserJet-Professional-P1102
device for HP-LaserJet-Professional-P1102: hp:/usb/HP_LaserJet_Professional_P1102?serial=000000000Q87Q2ZCSI1c
device for HP-LaserJet-Professional-P1102-2: hp:/usb/HP_LaserJet_Professional_P1102?serial=000000000Q87Q2ZCPR1a
device for PDF: cups-pdf:/
HP-LaserJet-Professional-P1102 accepting requests since Wed Mar  7 20:07:49 2018
HP-LaserJet-Professional-P1102-2 accepting requests since Wed Mar  7 20:08:05 2018
PDF accepting requests since Sun Feb 25 04:51:28 2018
printer HP-LaserJet-Professional-P1102 disabled since Wed Mar  7 20:07:49 2018 -
 Unplugged or turned off
printer HP-LaserJet-Professional-P1102-2 is idle.  enabled since Wed Mar  7 20:08:05 2018
printer PDF is idle.  enabled since Sun Feb 25 04:51:28 2018"
1753541,2018-03-07 22:08:45 UTC,"I also have a second laptop with the installed OS Arсhlinux. There such is not observed, there does not work at all autoaddition of the printer. I would be glad of such a decision and in Debian."
1753541,2018-03-07 10:10:57 UTC,There is a single device but the URIs of the two queues have two serial numbers. 000000000Q87Q2ZCSI1c and 000000000Q87Q2ZCPR1a. I wonder how that comes about and which one is the real one for the printer?
1753541,2018-03-07 05:03:17 UTC,"Hi Bill,"
1753541,2018-03-06 18:57:18 UTC,"lpstat -t
планировщик запущен
назначение системы по умолчанию: HP-LaserJet-Professional-P1102
устройство для HP-LaserJet-Professional-P1102: hp:/usb/HP_LaserJet_Professional_P1102?serial=000000000Q87Q2ZCSI1c
устройство для HP-LaserJet-Professional-P1102-2: hp:/usb/HP_LaserJet_Professional_P1102?serial=000000000Q87Q2ZCPR1a
устройство для PDF: cups-pdf:/
HP-LaserJet-Professional-P1102 принимает запросы с момента Вт 06 мар 2018 21:51:16
HP-LaserJet-Professional-P1102-2 принимает запросы с момента Вс 04 мар 2018 20:45:36
PDF принимает запросы с момента Вс 25 фев 2018 04:51:28
принтер HP-LaserJet-Professional-P1102 свободен. Включен с момента Вт 06 мар 2018 21:51:16
принтер HP-LaserJet-Professional-P1102-2 отключен с момента Вс 04 мар 2018 20:45:36 -
 Unplugged or turned off
принтер PDF свободен. Включен с момента Вс 25 фев 2018 04:51:28"
1753541,2018-03-06 14:37:13 UTC,Please provide the output of 'lpstat -t' when the two print queues show.
1753541,2018-03-07 17:03:15 UTC,"Hi, Afshan F.
""error: debian-9.3 version is not supported, so all dependencies may not be installed. However trying to install using debian-9.1 version packages.""
I would not want to risk not the future is confident that this will solve my problem."
1753543,2019-04-16 15:53:52 UTC,"Should this bug report be marked ""fix released""?"
1753543,2018-04-06 15:19:57 UTC,This issue was fixed in the openstack/openstack-ansible-lxc_container_create 16.0.10 release.
1753543,2018-04-03 16:43:21 UTC,This issue was fixed in the openstack/openstack-ansible-lxc_container_create 15.1.18 release.
1753543,2018-03-06 20:55:34 UTC,"Reviewed:  https://review.openstack.org/550148
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_container_create/commit/?id=018cc83b1a5a23e70e1abe82df20a8032d2e1afb
Submitter: Zuul
Branch:    stable/pike"
1753543,2018-03-06 20:51:50 UTC,"Reviewed:  https://review.openstack.org/550147
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_container_create/commit/?id=0be23b0532eb69bfbd7ea245dc65f0aee906af97
Submitter: Zuul
Branch:    stable/newton"
1753543,2018-03-12 12:47:50 UTC,This issue was fixed in the openstack/openstack-ansible-lxc_container_create 17.0.0.0rc2 release candidate.
1753543,2018-03-06 20:51:33 UTC,"Reviewed:  https://review.openstack.org/550145
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_container_create/commit/?id=3d1e70d1be8d10a54da35ad97c3e750384f8a73b
Submitter: Zuul
Branch:    stable/queens"
1753543,2018-03-06 16:28:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/550148"
1753543,2018-03-06 16:27:50 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/550147"
1753543,2018-03-06 16:27:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/550146"
1753543,2018-03-06 20:51:42 UTC,"Reviewed:  https://review.openstack.org/550146
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_container_create/commit/?id=708b83668e9b95b60dfbcb30837eba655c097beb
Submitter: Zuul
Branch:    stable/ocata"
1753550,2018-03-20 19:52:49 UTC,"Midair collision. I was thinking between High and Medium, so Medium it is."
1753550,2018-04-20 13:13:17 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1753550,2018-04-02 13:09:08 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1753550,2018-03-29 09:57:54 UTC,"Reviewed:  https://review.openstack.org/554963
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e55a5f412bf6bc343eb8bb11348afe57c2012066
Submitter: Zuul
Branch:    stable/queens"
1753550,2018-03-21 15:52:41 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554963"
1753550,2018-03-21 14:48:23 UTC,"Reviewed:  https://review.openstack.org/554703
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6482165bb1f44f5c98d9361153d737c22c92112d
Submitter: Zuul
Branch:    master"
1753550,2018-03-20 21:23:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554703"
1753550,2018-03-20 19:59:18 UTC,"The problem is that the periodic doesn't have a token, and [glance]/api_servers isn't configured, so when the notification code is trying to build a payload, it's trying to get the image API endpoint URL to build a link to the image for the notification. Getting the endpoint URL without a token fails."
1753550,2018-03-20 19:46:22 UTC,"Okay, I was able to reproduce the problem locally with devstack by:"
1753550,2018-03-20 19:50:22 UTC,"Setting this to High because any periodic task that will result in notifications being sent, will hit this problem if CONF.glance.api_servers is not set."
1753550,2018-03-20 17:52:38 UTC,"I've not a glance config section so it's all default options.
I've got that commit, and don't have service_user configured."
1753550,2018-03-20 18:02:25 UTC,"And yep, it's devstack all in one server set up."
1753550,2018-03-20 17:45:34 UTC,"Matt, in comment 0 they mentioned they're using devstack on commit id: 5d2add74534719c5670b29152964a60e8f23b42b so they should have the fix you mentioned."
1753550,2018-03-20 17:19:27 UTC,"Also, see https://github.com/openstack/nova/commit/62ef6cfcf01d84813f71d1e8252b86c170ee39f0 - do you have [service_user] configured in nova.conf? Do you have that fix? ^"
1753550,2018-03-20 17:18:10 UTC,What's your [glance] config in nova.conf?
1753550,2018-03-20 17:08:50 UTC,Thank you for adding that trace -- it shows why the intended behavior to set the instance to STOPPED fails:
1753550,2018-03-20 13:46:01 UTC,"Also no it doesn't get updated eventually, I've left a server for a while and it remains like that. Having a look through the log files it gets the same error and traceback every time it's called."
1753550,2018-03-20 13:42:13 UTC,I do get both those messages followed by an exception error message:
1753550,2018-03-20 01:19:52 UTC,"Here's where the code should be updating the instance power state to ""shutdown"" during the periodic task:"
1753550,2018-03-20 01:15:21 UTC,There is a periodic task in nova-compute controlled by the config option [DEFAULT]sync_power_state_interval which defaults to 600 seconds (10 minutes). The periodic task will update the power_state in the database to reflect the power state returned by the virt driver. That's the power state update that you see.
1753558,2020-05-20 15:13:26 UTC,"I'm not sure why github mentions v5.0.0 there, as that commit is from 2016.  That commit is just documenting how to avoid clashing with QEMU's usage of fw_cfg, and shouldn't be considered a recommendation / encouragement to actually use fw_cfg for application data. The QEMU maintainers still actively discourage any application usage of fw_cfg."
1753558,2020-05-20 10:59:56 UTC,"The QEMU maintainers consider the ""fw_cfg"" feature to be only intended for QEMU to communicate with the firmware.  While some projects have indeed used fw_cfg for general purpose data passthrough, this is discouraged by QEMU maintainers. There are a fairly small, limited number of data slots in fw_cfg, and QEMU needs to be able to use these precious free slots for its own tasks in future."
1753558,2020-05-20 14:47:01 UTC,"I was going to just straight up disagree, but then I noticed that this only changed in v5.0.0 (i.e. very recently): https://github.com/qemu/qemu/commit/63d3145aadbecaa7e8be1e74b5d6b5cbbeb4e153"
1753558,2018-03-05 18:38:44 UTC,"Note this patch is completely *untested* so don't commit it as is ! It just meant to illustrate the a general approach to solving the bug and needs someone to validate it & provide unit tests, etc."
1753558,2020-05-20 10:34:34 UTC,"Daniel, do you have any thoughts on this approach vs using fw_cfg for it? That seems more purpose built for passing configuration into guests."
1753559,2020-08-04 17:04:35 UTC,I have tested this using Pinta 1.7+r1134-202008032046~ubuntu18.04.1 but can't reproduce a problem.
1753559,2020-08-04 19:45:43 UTC,"I do not do image editing at the moment, so we can close it."
1753565,2018-03-05 19:28:20 UTC,"I can confirm sites exist with multiple memcache servers.  Even for sites that only have 1 server, being able to perform maintenance on a cache server without having to bring the ILS down would be nice to have."
1753572,2019-01-24 23:03:15 UTC,Bryan - is there any chance we could get that image?
1753572,2019-03-06 11:43:04 UTC,"The verification of the Stable Release Update for busybox has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1753572,2019-03-06 11:42:58 UTC,This bug was fixed in the package busybox - 1:1.27.2-2ubuntu3.1
1753572,2019-02-19 07:32:58 UTC,Thanks!
1753572,2019-02-19 01:18:51 UTC,"Yes, 1.27.2-2ubuntu3.1 looks to fix the issue with 1.27.2-2ubuntu3!"
1753572,2019-02-18 14:23:16 UTC,"Hi Bryan,"
1753572,2019-02-01 19:19:55 UTC,"I have the image, how can I get it to you privately to test? (Or alternatively, I can test it with the new version if you have a link?)"
1753572,2019-01-30 21:58:26 UTC,Creating image now.
1753572,2019-01-25 01:01:07 UTC,"Yeah apologies, I have to allocate another U18 host and build one.  Will aim for tomorrow."
1753572,2019-01-17 19:16:54 UTC,I was using it to build a U18 debirf image when I saw this issue.  I can generate one in a bit for you.
1753572,2019-02-08 23:03:12 UTC,"Hello Bryan, or anyone else affected,"
1753572,2018-11-28 15:27:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753572,2018-03-05 19:44:49 UTC,Proposed solution: back port the env var patch or upgrade to 1.28.
1753572,2018-03-05 19:57:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753572,2018-06-13 15:00:19 UTC,The EXTRACT_UNSAFE_SYMLINKS variable was backed out in busybox 1.28.2 by the following commit:
1753572,2018-06-22 12:24:14 UTC,Hi! I've prepared a busybox update and uploaded it to my PPA here:
1753572,2018-03-05 19:40:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753572,2018-07-03 14:42:15 UTC,Hello?
1753572,2018-07-06 22:05:45 UTC,"This does look good now, thanks!"
1753572,2018-07-13 15:20:16 UTC,This bug was fixed in the package busybox - 1:1.27.2-2ubuntu4
1753572,2019-01-17 18:31:00 UTC,I just uploaded this for bionic to be processed by the SRU team.
1753574,2019-09-19 16:41:30 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.opendev.org/549861
Reason: Already done"
1753578,2018-03-06 11:13:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753601,2018-03-05 23:45:33 UTC,for example:
1753601,2018-04-01 14:58:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753606,2018-03-06 01:00:22 UTC,So I just got a restore to work .... I'm pretty sure I had it borked due to a timestamp skew of some sort on my end. I think the issue was I needed to specify a timestamp ?close? to that of the latest backup. You can close this if you like.
1753606,2018-03-19 03:04:49 UTC,"2018-03-06 00:09:29 UTC [20296]: [6-1] db=,user= FATAL:  requested recovery stop point is before consistent recovery point"
1753610,2018-03-29 00:15:40 UTC,This issue was fixed in the openstack/puppet-vitrage 2.4.0 release.
1753610,2018-04-19 21:05:53 UTC,This issue was fixed in the openstack/puppet-vitrage 3.0.0 release.
1753610,2018-03-06 06:32:00 UTC,"Reviewed:  https://review.openstack.org/549943
Committed: https://git.openstack.org/cgit/openstack/puppet-vitrage/commit/?id=7b25ef7447186a7571609baae29a1c776cb8f638
Submitter: Zuul
Branch:    stable/queens"
1753610,2018-03-06 03:55:32 UTC,"Reviewed:  https://review.openstack.org/549899
Committed: https://git.openstack.org/cgit/openstack/puppet-vitrage/commit/?id=f21dfbd1c759f516bcb0c55f2ad17d2ff61c4652
Submitter: Zuul
Branch:    master"
1753610,2018-03-06 05:46:41 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/549943"
1753613,2018-07-02 10:44:12 UTC,This should be fixable with some opportunistic reading of request-id.
1753616,2018-07-02 10:56:27 UTC,"Commit bda5d1508190286d92951f1b9643d1b08a57ecae in charmhelpers switch the mysql helper to directly use leader_get/leader_set, rather than using the original peer storage helper which deals with the migration transparently."
1753616,2018-07-02 11:10:27 UTC,I think we need to introduce a charm specific migration step to resolve this specific issue.
1753616,2019-11-29 15:41:33 UTC,"Adding it to the charm-guide for a note for upgraders.  It looks like the issue is that the migration code in charm-helpers was to get things from disk to the peer relation, and now it tries to get things from disk to the leader-settings.  What it doesn't do is migrate the passwords from the peer-relation to the leader-settings."
1753640,2018-04-30 14:59:14 UTC,"Reviewed:  https://review.openstack.org/564463
Committed: https://git.openstack.org/cgit/openstack/charms.ceph/commit/?id=978e561782105db0cf47c1076434f0739dd3855d
Submitter: Zuul
Branch:    master"
1753640,2020-07-08 19:13:10 UTC,I forgot to say I'm running that command in the other juju model where the ceph cluster is deployed.
1753640,2020-07-08 16:05:44 UTC,@chris: It's a second cinder backend that's connected to a ceph cluster in a different juju model on the same juju controller.
1753640,2020-07-08 05:43:55 UTC,"If you've got ceph in the model (as suggested by `juju ssh ceph-mon...`), why is ceph-proxy deployed?"
1753640,2020-07-07 15:18:06 UTC,I just this issue in a deployment with ceph-proxy as a cinder-ceph backend. My workaround was:
1753640,2018-12-03 09:25:31 UTC,The updates to ceph-mon will remove the warning messages - however there is a pending piece of work to actually provide the application name from each consuming charm that still needs to be done.
1753640,2018-05-09 12:05:03 UTC,"Reviewed:  https://review.openstack.org/564466
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=22aa0c614601570e1d6de67936287e3ccf185432
Submitter: Zuul
Branch:    master"
1753640,2018-05-08 20:43:05 UTC,Field High SLA now requires that a estimated date for a fix is listed in the comments. Please provide this estimate for the open tasks.
1753640,2018-04-26 06:23:12 UTC,Subscribing ~field-high.
1753640,2018-03-15 11:39:34 UTC,Ceph will make a guess on the application once it starts to get filled; however the charms should set this on deployment to avoid early lifecycle health warnings in ceph.
1753640,2018-04-06 16:11:13 UTC,"hi @nobuto - FYI, the openstack-on-lxd example bundles have been updated to use ceph-mon + ceph-osd instead of the deprecated legacy ceph charm."
1753640,2018-04-04 23:34:08 UTC,"sudo ceph status
  cluster:
    id:     4ce1de56-383e-11e8-aedd-00163e99e06d
    health: HEALTH_WARN
            application not enabled on 2 pool(s)"
1753640,2018-04-04 22:04:01 UTC,Also seeing the issue
1753640,2018-04-24 05:28:27 UTC,"As a side-note for other intrepid travellers hitting this -
On a recent deployment, I also had to run 'ceph osd pool application enable default.rgw.buckets.index rgw' to get to HEALTH_OK."
1753640,2018-03-09 10:19:29 UTC,"Can confirm, I get the same in version 12.2.1"
1753640,2018-03-09 03:26:12 UTC,"After trying ceph-mon/next charm, the number of affected pools are decreased. It looks like rgw related so adding ceph-radosgw charm task for now."
1753640,2018-03-06 08:22:23 UTC,"According to https://ceph.com/community/new-luminous-pool-tags/ , there is a new step following pool creation that we'll need to add support for: `rbd pool init <pool-name>`"
1753640,2018-03-06 04:58:52 UTC,"Ah, openstack-on-lxd uses ceph charm instead of ceph-mon charm actually. it may not be the case with ceph-mon. I will double check with it."
1753662,2018-03-22 00:19:10 UTC,"BTW, have we set the baseline of ""good"" in this bisection with xenial configs?"
1753662,2018-03-21 23:03:59 UTC,55cbdaf6399de16b61d40d49b6c8bb739a877dea looks bad.
1753662,2018-03-22 00:19:59 UTC,Correction: Does HWE kernel mean it's with xenial configs? Or was it built with the source release config i.e. artful?
1753662,2018-03-21 11:39:33 UTC,"I was pretty occupied today, so I'm going to test 55cbdaf6399de16b61d40d49b6c8bb739a877dea now and report back my tomorrow morning."
1753662,2018-03-20 15:36:47 UTC,"I built the next test kernel, up to the following commit:
55cbdaf6399de16b61d40d49b6c8bb739a877dea"
1753662,2018-03-20 12:11:09 UTC,ea094f3c830a67f252677aacba5d04ebcf55c4d9 looks bad.
1753662,2018-03-20 00:15:29 UTC,"I built the next test kernel, up to the following commit:
ea094f3c830a67f252677aacba5d04ebcf55c4d9"
1753662,2018-03-19 22:37:51 UTC,ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 looks bad.
1753662,2018-03-19 22:37:19 UTC,ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 looks bad.
1753662,2018-03-16 09:54:53 UTC,"The new build of v4.12-rc3  is a good build (2 of 151).
4.12.0-041200rc3-generic #201803151851"
1753662,2018-03-17 12:38:17 UTC,It's good that the v4.12-rc3 with xenial configs was bad.  It means we should use Xenial configs when performing the bisect and not Artful configs.  I'll kick off another bisect and post the first test kernel.
1753662,2018-03-17 05:51:05 UTC,"Ok, we see some differences with the three kernels. How do we want to proceed from here?"
1753662,2018-03-16 14:55:51 UTC,"Sorry the correct link for the new 4.12-rc3 kernel with Xenial configs is:
http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3-xenial-configs/"
1753662,2018-03-16 14:53:25 UTC,I built another v4.12-rc3 test kernel.  This time with Xenial configs instead of Artful configs.  This test kernel can be downloaded from:
1753662,2018-03-22 15:05:12 UTC,"The HWE kernel was built with the Artful configs.  I restarted the bisect using the Xenial configs and marking 4.12-rc4 as good and 4.12-rc3 as bad.  We should re-test that to confirm we are going down the right patch.  I built a 4.12-rc4 kernel with Xenial configs, which can be downloaded from:"
1753662,2018-03-16 00:55:50 UTC,"v4.12-rc4 is good, 1 of 146. Going to test v4.12-rc3."
1753662,2018-03-15 19:19:48 UTC,"A re-build of v4.12-rc3 is now available here:
http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3"
1753662,2018-03-15 18:52:51 UTC,"Yes, sorry this is a ""Reverse"" bisect, so v4.12-rc4 should be good and not bad."
1753662,2018-03-15 17:11:11 UTC,"> We may have went wrong somewhere in the bisect. However, just to be sure, I built a v4.12-rc4 test kernel. This kernel should be bad and contain the bug. If it does not, it may be due to the configs I'm using to build the test kernels.
"
1753662,2018-03-19 13:41:49 UTC,I restarted the bisect.  This time using Xenial configs and not Artful configs.
1753662,2018-03-24 14:37:52 UTC,4.12-rc4 kernel with Xenial configs looks bad.
1753662,2018-04-11 15:54:46 UTC,"FWIW, kernel trace happens with the kernel in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/comments/77"
1753662,2018-03-26 16:03:34 UTC,2018年3月27日(火) 0:11 Joseph Salisbury <email address hidden>:
1753662,2018-03-15 15:11:29 UTC,"The reverse bisect reported the following commit as the fix, but I'm doubtful since its and i915 commit:"
1753662,2018-06-11 10:57:26 UTC,I would have thought this would be the relevant patch:
1753662,2018-06-08 05:44:12 UTC,"Hi Joseph,"
1753662,2018-04-30 17:36:08 UTC,"We've seen a similar-sounding issue in the past, but couldn't get it tracked down to the root cause."
1753662,2018-04-30 04:22:23 UTC,#146~lp1753662ThreeCommits is better at some level (around 40% failure rate to 20%).
1753662,2018-06-11 20:50:41 UTC,We are also seeing this running trusty with the HWE kernel (i.e. 4.4) in which we have upgraded to the upstream i40e drivers.
1753662,2018-04-27 17:47:17 UTC,I built a test kernel with the two commits pointed out by Jay.  The test kernel also required commit f307668bfc as a prereq.
1753662,2018-04-27 16:17:22 UTC,"Thanks for the pointer, Jay!  I'll build a Xenial test kernel with these two commits and post a link to it."
1753662,2018-04-27 05:15:51 UTC,I would suggest testing
1753662,2018-03-26 15:02:53 UTC,"I built a 4.4 kernel using the Artful configs, it can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1753662"
1753662,2018-04-16 12:25:17 UTC,"Just for the record, up-to-date numbers after the weekend."
1753662,2018-04-15 13:45:28 UTC,"Ok, we have some numbers with the new host."
1753662,2018-04-14 03:13:54 UTC,"I ran HWE 4.13 just to make sure the result is the same as the previous host. And as we confirmed before, the issue is not reproducible with HWE 4.13."
1753662,2018-04-13 21:39:20 UTC,Thanks for testing.  I would have thought 4.4 with the Artful configs would not have had the bug if a config change is the fix.
1753662,2018-04-13 05:39:07 UTC,"FWIW, I tried PCI hot-plugging to try another way for faster iterations without reboot.
https://paste.ubuntu.com/p/qDVkMcTYPQ/"
1753662,2018-04-13 05:29:34 UTC,4.4 kernel using the Artful configs didn't make much difference.
1753662,2018-04-11 01:49:11 UTC,Finally got a machine up and running. Will resume testing shortly.
1753662,2018-04-03 11:45:39 UTC,The new environment is not fully up yet to test. ETA would be by the end of this week.
1753662,2018-04-02 19:41:12 UTC,Just curious if you had a chance to test the kernel posted in #77?
1753662,2018-03-26 16:14:23 UTC,Thanks for the update.  I'll start comparing the configs between Xenial and Artful to see if the change that caused this sticks out.
1753662,2018-04-15 13:48:24 UTC,"Just for the record, I'm using the attached rc.local for testing."
1753662,2018-03-15 08:17:52 UTC,4681ee21d62cfed4364e09ec50ee8e88185dd628 looks good.
1753662,2018-03-06 11:51:18 UTC,The kernel with c15e07b02bf0 didn't make a difference on the race condition. The issue is still reproducible. Let me know when you need my testing again with different kernels.
1753662,2018-03-14 18:55:41 UTC,"I built the next test kernel, up to the following commit:
4681ee21d62cfed4364e09ec50ee8e88185dd628"
1753662,2018-03-07 09:58:50 UTC,"For the record,"
1753662,2018-03-07 04:17:16 UTC,"I run an overnight test with v4.12 just to make sure it really fixed the issue. It happened sometimes, but way less frequencies. We may need to test it longer for ""good"" cases since the patch may not be only one. Anyway, the current status is:"
1753662,2018-03-06 16:40:09 UTC,"Correction. I thought v4.12-rc1 had i40e 2.1.7 because of:
https://github.com/torvalds/linux/commit/15990832cd3e7e8904f8dacdabfa33adb9a836d6
But it actually has 2.1.14 from the log output."
1753662,2018-03-06 16:34:17 UTC,"v4.12-rc1 with i40e 2.1.7 - bad
v4.12 with i40e 2.1.14 - good"
1753662,2018-03-06 16:14:30 UTC,"If v4.12-rc1 is still bad, we would need to test some of the other release candidates, such as rc2, rc3, rc4, etc."
1753662,2018-03-06 16:03:44 UTC,"v4.11 with i40e 1.6.27 - bad
v4.12 with i40e 2.1.14 - good"
1753662,2018-03-06 15:29:03 UTC,Not reproducible with 4.13-rc1 with 5 reboots.
1753662,2018-03-06 14:37:48 UTC,"Reproducible with:
v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/"
1753662,2018-03-06 14:24:36 UTC,"Reproducible with:
4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/"
1753662,2018-03-06 14:18:27 UTC,"To narrow it down further, can you also test the following kernels:"
1753662,2018-03-06 13:50:17 UTC,"Thanks, I was running some tests with existing HWE kernels in xenial repo like linux-image-4.8.0-58-generic, linux-image-4.10.0-42-generic and linux-image-4.13.0-36-generic. It looks like 4.10 is the last bad one and 4.13 is the first good one."
1753662,2018-03-06 13:05:40 UTC,"To perform a ""Reverse"" bisect, we need to identify the last kernel version that had the bug and the first kernel version that does not."
1753662,2018-03-06 12:55:44 UTC,The record of xenial default kernel.
1753662,2018-03-06 12:19:15 UTC,For the record of testing.
1753662,2018-03-06 09:39:05 UTC,"If that commit doesn't fix the issue, we can perform a ""Reverse"" bisect between 4.4 and 4.13 to find the fix."
1753662,2018-03-06 08:30:54 UTC,"There is one LACP commit that sticks out between v4.4 and v4.13:
c15e07b02bf0 (""team: loadbalance: push lacpdus to exact delivery"")"
1753662,2018-03-06 07:30:05 UTC,This change was made by a bot.
1753662,2018-03-06 07:16:26 UTC,"This might be related (not exactly the same):
https://sourceforge.net/p/e1000/bugs/524/
One says 1.6.42 fixed his issue."
1753662,2018-06-12 02:39:36 UTC,"Jeff,"
1753662,2018-03-07 16:33:28 UTC,"Do you happen to have results from any of the other release candidates, such as 4.12-rc4?"
1753662,2018-03-07 17:01:03 UTC,I have let rc4 run for hours.
1753662,2018-03-08 02:00:09 UTC,"With rc3, will test rc2 next."
1753662,2018-03-08 07:24:45 UTC,With rc2 result. It looks like there is a noticeable difference between v4.12-rc3 and v4.12-rc4.
1753662,2018-03-14 15:59:23 UTC,"The test is still in progress, but so far 171d8b9363725e122b164e6b9ef2acf2f751e387 looks good (0 of 21). Since I already downloaded the kernel locally, please go ahead to build the next one. Thanks,"
1753662,2018-03-14 14:11:37 UTC,"I built the next test kernel, up to the following commit:
171d8b9363725e122b164e6b9ef2acf2f751e387"
1753662,2018-03-14 08:48:38 UTC,d38162e4b5c643733792f32be4ea107c831827b4 looks good.
1753662,2018-03-14 05:49:02 UTC,"The test is still in progress, but so far d38162e4b5c643733792f32be4ea107c831827b4 looks good (1 of 37). Since I already downloaded the kernel locally, please go ahead to build the next one. Thanks,"
1753662,2018-03-13 18:44:24 UTC,Yes that is the correct kernel.  The mainline-build-one script uses the 'git describe' command to come up with the name.  That command returns the closest git tag and not the one that contains it.  So in the case of commit d38162e4b5c643733792f32be4ea107c831827b4:
1753662,2018-03-13 17:29:35 UTC,"Oh wait,"
1753662,2018-03-13 17:22:25 UTC,"@Joseph,"
1753662,2018-03-13 16:57:08 UTC,"I built the next test kernel, up to the following commit:
d38162e4b5c643733792f32be4ea107c831827b4"
1753662,2018-03-13 04:33:00 UTC,25f480e89a022d382ddc5badc23b49426e89eabc looks good.
1753662,2018-03-15 02:14:42 UTC,171d8b9363725e122b164e6b9ef2acf2f751e387 looks good. The next test is with 4681ee21d62cfed4364e09ec50ee8e88185dd628.
1753662,2018-03-12 14:42:27 UTC,"I built the next test kernel, up to the following commit:
25f480e89a022d382ddc5badc23b49426e89eabc"
1753662,2018-03-09 07:34:10 UTC,"I built the next test kernel, up to the following commit:
400129f0a3ae989c30b37104bbc23b35c9d7a9a4"
1753662,2018-03-09 06:26:46 UTC,0bb230399fd337cc9a838d47a0c9ec3433aa612e seems good. I'm ready for the next test.
1753662,2018-03-09 02:42:31 UTC,"I run xenial HWE over a night while sleeping, the result was 0/119. The next test is with:
v4.12.0-041200rc3 #201803081620 - ?  0bb230399fd337cc9a838d47a0c9ec3433aa612e"
1753662,2018-03-08 16:36:24 UTC,"I built the next test kernel, up to the following commit:
0bb230399fd337cc9a838d47a0c9ec3433aa612e"
1753662,2018-03-08 12:52:52 UTC,4.12.0-041200rc3-generic #201803080803 looks good. Please proceed to the next one. I will test it my tomorrow which would be 12 hours later from now.
1753662,2018-03-08 11:14:25 UTC,So far 0 of 6 with 4.12.0-041200rc3-generic #201803080803. But I will keep it running for a while to see if it becomes close to 30% or 0%.
1753662,2018-03-08 10:52:25 UTC,"I just noticed I forgot to paste the SHA1 for the test kernel posted in comment #29:
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6"
1753662,2018-03-08 10:34:47 UTC,"Ok, 25% - 30% seems a baseline. I'd like to make sure v4.13 is really 0% for longer running test, but will do the bisection of v4.12-rc3 and v4.12-rc4 first."
1753662,2018-03-08 08:38:22 UTC,I started a kernel bisect between v4.12-rc3 and v4.12-rc4. The kernel bisect will require testing of about 7-10 test kernels.
1753662,2018-03-09 15:04:50 UTC,400129f0a3ae989c30b37104bbc23b35c9d7a9a4 looks good.
1753667,2019-09-19 14:53:57 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1753667,2018-03-06 08:01:52 UTC,"Hi Nobuto,"
1753667,2018-03-06 08:44:18 UTC,"@Andres, it's true that this is a feature request. The LACP bonding status check may not require an agent since I'm fine with one-time check like reporting cloud-init failures you implemented before:
https://bugs.launchpad.net/maas/+bug/1707850
(or we could use cloud-init to enable bonding status check at the end of network configuration.)"
1753670,2018-07-13 05:28:49 UTC,"@Richard Harding, John A Meinel,"
1753675,2018-03-07 00:22:52 UTC,"There is no way to add arguments to individual conversion functions, they must all present the exact same calling signature, which is a major problem for the cvt_d_st() and cvt_f_st() routines with a ""too-small"" output buffer."
1753675,2018-03-07 10:11:52 UTC,"Indeed, the design decisions made when the conversion API was created cause problems that are hard to fix. The fact that we have two sets of conversion functions lets me assume that there had been previous attempts to fix shortcomings (missing array support I guess). What I do not quite understand is why the scalar version had not been abandoned for a array[1] interpretation. Is it that much slower?"
1753675,2018-03-08 00:16:19 UTC,"I suspect your understanding may be a little off. My knowledge of the history is that the scalar versions were added later, which is why they are called ""fast"" convert — this was an attempt to improve the performance of links that only transport a scalar, and comparing the speeds of the convert routines by themselves the ""fast"" ones do seem to be about 20-30% faster. However I suspect that the extra overhead of working out which one to call probably removes most of the speed advantage that the fast routines have. I'm still measuring the effect of doing that, but it does seem to slow down dbGet() a little."
1753675,2018-03-08 12:27:30 UTC,I had not looked up the older history of the conversions. I simply guessed from the complexity.
1753676,2020-04-16 09:41:23 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/720414"
1753676,2019-11-22 17:51:38 UTC,"Reviewed:  https://review.opendev.org/678016
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ebcf6e4ce576285949c5a202f2d7d21dc03156ef
Submitter: Zuul
Branch:    master"
1753676,2020-04-19 02:52:59 UTC,"Reviewed:  https://review.opendev.org/720414
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6fa8540f2ce40aacca4fcf588a050ed26f66d24c
Submitter: Zuul
Branch:    stable/train"
1753676,2019-08-20 15:24:10 UTC,"Because of this issue it is possible to loss instance disk(saw it in production).
This scenario is reproductible on a multi node master devstack deployment:"
1753676,2019-08-22 13:48:15 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678016"
1753677,2018-03-06 08:46:03 UTC,"Oddly, it works perfectly in Weston:"
1753677,2018-03-06 08:48:46 UTC,"Upstream:
https://gitlab.gnome.org/GNOME/mutter/issues/55"
1753677,2018-03-07 07:20:06 UTC,"es2gears_wayland is requesting two frame callbacks per frame, and then reporting a framerate double of what it is actually drawing, see this log:"
1753677,2018-03-07 07:25:49 UTC,Also seen in gnome-shell on Ubuntu 18.04:
1753677,2018-03-07 07:50:47 UTC,"New upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=105376"
1753677,2018-03-07 08:43:03 UTC,"One 'frame' will be requested by the EGL implementation and another by es2gears. That's fine, as neither will receive the other's events."
1753677,2018-09-08 19:49:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753677,2018-12-20 06:14:48 UTC,"Also, on a real 120Hz display, es2gears_wayland reports 240 FPS. Verified in both gnome-shell and weston."
1753677,2019-05-14 15:37:21 UTC,-- GitLab Migration Automatic Message --
1753697,2021-02-17 17:10:15 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1753697,2018-03-06 10:23:39 UTC,Lowered prio as it looks not so bad as I thought it is :)
1753697,2018-03-06 10:19:01 UTC,"TBH I didn't found so much to start worrying, but there some, like OVB repo and quickstart.sh / reproducer-quickstart.sh wrappers clonning the quickstart/extras repos."
1753697,2018-03-06 10:23:15 UTC,There is also one for tempest http://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/validate-tempest/templates/configure-tempest.sh.j2#n80
1753715,2019-01-23 16:48:57 UTC,If kuryr-daemon is running as superuser then why is oslo.privsep needed? The idea of privsep is to provide limited access to privileged calls for unprivileged processes. If a process is already privileged then it can just make calls directly.
1753718,2019-04-30 13:43:16 UTC,"how did you run it as root? I'm having the same problem. I'm installing Rocky. In Pike there was a tgtd container... now I don't see it. From your post, I assume now is part of Cinder-volume container."
1753718,2019-05-02 15:56:01 UTC,"I discussed this with qqmber on IRC, it does appear to be a bug."
1753718,2019-12-15 14:23:17 UTC,Possibly the effect of this: https://bugs.launchpad.net/kolla-ansible/+bug/1856458
1753718,2020-02-14 04:17:23 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1753741,2018-04-10 09:20:48 UTC,that's fixed in 3.28.1
1753755,2018-03-06 13:43:53 UTC,Maybe it's just about terminating the session when the service is stopped?
1753755,2018-03-06 14:24:38 UTC,Maybe this can be used for networking-dpm: https://docs.python.org/2/library/atexit.html
1753757,2018-03-06 21:07:37 UTC,"So is this something that requires access to the hypervisor?  i.e. you need to be root on the underlying compute node?  If so, tcpdump can already be used by root to capture tenant traffic.  It doesn't look like it's something that can be done from inside a tenant VM, so I don't see why it is a security issue?"
1753757,2018-03-07 15:34:29 UTC,"I'm moving this back to Incomplete since I still don't understand the security risk here, thanks.  It will automatically transition to In Progress if/when a patch is proposed to fix it."
1753757,2018-03-16 06:40:43 UTC,"As I tested, yes this is responsible to disclose the privacy of VM by redirecting its network traffic at some destination point, irrespective who is looking at the traffic either host or some other."
1753757,2018-03-16 14:39:25 UTC,"But who is redirecting the VM traffic?  Is it being done by a port mirror?  That isn't something a tenant can do, only someone with access to the hypervisor.  If I am mis-understanding then please list the commands a tenant can run to cause this."
1753780,2018-05-24 11:18:30 UTC,This might be of limited usefulness as one needs to be a core dev to change the default repository and the importer deliberately doesn't run with those credentials.
1753780,2018-03-06 15:45:50 UTC,"Marking as Wishlist, as we do have the script to do this for us for the same values as the other scripts (whitelist, blacklist, phasing)."
1753782,2018-04-16 18:34:04 UTC,"Actually it is still observable. Just mouseover the field and you will see it in the tooltip.
You are able to copy-paste the location or link target as well (just select it, no ... will be in the clipboard but full path instead).
Also full path to the file is available via right-click menu."
1753782,2018-03-16 05:14:17 UTC,I also get this on xenial and have made it a bit clearer to read.
1753782,2018-03-16 05:16:17 UTC,I also get this on bionic.
1753785,2018-03-06 15:59:37 UTC,Affects - Ocata and Newton
1753785,2018-03-06 16:03:10 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/550139"
1753785,2018-03-07 17:16:30 UTC,"Reviewed:  https://review.openstack.org/541721
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=c23eb809d290e85d9eeef0b9f51a5d6c80a31ff6
Submitter: Zuul
Branch:    stable/ocata"
1753785,2018-03-12 20:30:16 UTC,"Reviewed:  https://review.openstack.org/550139
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=f2be057d1c969e35a936502c04aecca1b5597daf
Submitter: Zuul
Branch:    stable/newton"
1753785,2018-03-26 18:03:17 UTC,This issue was fixed in the openstack/tripleo-heat-templates 6.2.12 release.
1753785,2018-03-26 18:15:31 UTC,This issue was fixed in the openstack/tripleo-heat-templates 5.3.11 release.
1753786,2018-03-16 15:53:01 UTC,This bug was fixed in the package mdadm - 4.0-2ubuntu1
1753787,2018-03-10 02:01:38 UTC,"StacktraceTop:
 g_main_loop_is_running (loop=0x1) at ../../../../glib/gmain.c:4147
 li_manager_bus_vanished (connection=<optimized out>, name=<optimized out>, mgr=<optimized out>) at ./src/li-manager.c:153
 do_call (client=client@entry=0x7fad80012000, call_type=call_type@entry=CALL_TYPE_NAME_VANISHED) at ../../../../gio/gdbusnamewatching.c:219
 call_vanished_handler (client=client@entry=0x7fad80012000, ignore_cancelled=0) at ../../../../gio/gdbusnamewatching.c:245
 call_vanished_handler (ignore_cancelled=0, client=0x7fad80012000) at ../../../../gio/gdbusnamewatching.c:243"
1753789,2018-03-06 18:23:27 UTC,I tend to agree with this.  @Wayne et. al. -- anyone disagree?
1753789,2018-03-06 18:41:40 UTC,"There may be use cases where a user would want to define different
colors in the board editor and in the footprint editor.  Typically you
are dealing with more layer in the board editor than the footprint
editor so using the same colors may be less than optimal.  I would
prefer that we make it optional to link the footprint editor layer
colors to the board editor layer colors but don't force that as the only
option.  If you force it, you will most likely get another bug report
from a user who uses different color sets.  I would prefer that we defer
this to v6 since it's a behavioral change."
1753789,2018-03-06 19:03:44 UTC,"Moreover, because there are less copper layers in the fp editor than the board editor, transparency settings can differ between editors."
1753789,2018-03-06 21:25:47 UTC,"If there are valid reasons/use cases for the color sets to be different, at least make it easy/intuitive to copy colors from pcbnew to fpeditor (and vici versa) for identical layers. I guess I could make a little script and stick it in the plugin folder but I'd say such solution is not intuitive."
1753789,2018-03-07 18:29:43 UTC,I will add an easy way to copy them back and forth as part of color theme support for V6
1753791,2018-03-06 17:00:06 UTC,This change was made by a bot.
1753799,2021-01-16 04:37:05 UTC,"This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information."
1753799,2021-01-01 04:38:14 UTC,"Dear Bug Submitter,"
1753799,2020-12-17 05:35:37 UTC,Thank you for the crash report.
1753799,2018-03-09 13:47:57 UTC,"Hello,"
1753799,2018-03-09 02:05:49 UTC,"StacktraceTop:
 QString::size (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:233
 QString::toLocal8Bit() const & (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:520
 QFile::encodeName (fileName=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qfile.h:89
 K3b::ExternalBinPermissionModel::Private::getProgramInfo (this=0x563289b16880, program=0x56328a16da20, owner=..., group=..., wantedGroup=..., perm=@0x7fffaf5953b8: 116, wantedPerm=@0x7fffaf5953bc: 14) at ./src/option/k3bexternalbinpermissionmodel.cpp:109
 K3b::ExternalBinPermissionModel::Private::needChangePermissions (this=<optimized out>, program=<optimized out>) at ./src/option/k3bexternalbinpermissionmodel.cpp:148"
1753799,2018-03-30 13:43:26 UTC,"Git commit 1e771f7f3ddf83fd7c3bf78b35247a82ebbb8c2c by Leslie Zhai.
Committed on 30/03/2018 at 13:38.
Pushed by lesliezhai into branch 'master'."
1753800,2018-05-24 13:39:23 UTC,"In this edge case, Debian libffi 3.1~rc1+r3.0.13-12 differs from Ubuntu libffi 3.1~rc1+r3.0.13-12 as follows:"
1753800,2018-05-24 13:45:25 UTC,"The result of this is that on two separate subsequent occasions (due to multiple publication events) the importer attempts to create an orphan tag because the previous import tag already exists but has a different tree. On the second attempt to create an orphan tag, it fails as the orphan tag already exists."
1753800,2020-09-28 12:01:31 UTC,Fix released in git-ubuntu version 1.0
1753801,2018-03-20 18:28:57 UTC,Connections leveled off just over 800 on this cloud:
1753801,2018-03-27 15:39:07 UTC,"There are many ways to solve these issues, and some of them were discussed in the bug triage of today."
1753804,2018-03-06 18:30:06 UTC,This change was made by a bot.
1753804,2018-03-06 18:14:28 UTC,Additional info: This is the line I added to /etc/default/grub to search for a working kernel and  revert to 105 until this is fixed:
1753804,2018-03-07 08:06:47 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1753804,2018-03-07 16:49:29 UTC,I installed 4.4.120-0404120-generic. Is this the version you intended?
1753812,2018-03-26 18:54:52 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.0.0.0b1 development milestone.
1753812,2018-04-19 13:33:03 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.0.0.0b2 development milestone.
1753817,2021-02-17 17:06:57 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1753828,2018-03-18 23:00:23 UTC,"Bonjour
Quel est votre problème ? Vous postez notre message dans le forum de _Mahara  ais votre copie d’écran montre l’installation de paquets de langue dans Ubuntu. Ou je ne trompe ? Veuillez en dire plus ici afin que nous puissions vous aider.
D Jan"
1753830,2018-03-08 15:59:22 UTC,"Regarding the max gap, I am not sure if it is really necessary or if the ""Guest add disks"" function would handle it. Example:"
1753830,2018-03-08 01:28:37 UTC,"64 , 69 and 5 means 64G , we need enhance this in our document
this might need Bill's help"
1753830,2018-03-09 03:00:23 UTC,"no, DIRMAINT don't support this kind of 6+2 mode, so in turn openstack can't support either
so mode27 might be needed in your case otherwise you will get a 'no disk available' issue"
1753833,2018-04-02 13:09:12 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1753833,2018-04-20 13:13:46 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1753833,2018-03-23 01:08:09 UTC,"Reviewed:  https://review.openstack.org/553742
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aaae38d1aa227a732b9aa8c93d77a909d0324696
Submitter: Zuul
Branch:    stable/queens"
1753833,2018-03-16 10:10:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/553742"
1753833,2018-03-18 02:16:40 UTC,"Reviewed:  https://review.openstack.org/550967
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8da6831e6375d013f0235a542b6b91580a43f61f
Submitter: Zuul
Branch:    master"
1753833,2018-03-08 18:07:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550967"
1753833,2018-03-08 10:20:17 UTC,"Adapted Solution : Using the CantStartEngineError for handling this gracefully, continuing the archival and informing the user that 0 instance_mappings and 0 request_specs rows were archived because the CONF.api_database.connection was not set."
1753842,2018-03-12 16:02:09 UTC,"I like the idea, but I have a feeling it will need a spec."
1753842,2018-03-20 13:32:01 UTC,Boot-to-ramdisk is a critical need for the HPC use case.  I'm happy to write up the spec.  What level of detail is required for a spec?  Is there an example you can point me to for guidance?
1753844,2018-03-07 07:50:12 UTC,In the unit logs for nova-cloud-controller:
1753848,2018-03-06 23:14:37 UTC,(Note that successfully testing reports that use joins on virtual fields requires the fix for bug 1721807.)
1753848,2020-09-24 15:58:03 UTC,EG 3.5.1
1753853,2018-04-01 19:27:21 UTC,"Again, sorry for the delay, I didn't get subscribed. I'm not sure why... I didn't used to have to do that explicitly."
1753853,2018-03-26 02:20:53 UTC,"Thank you for pointing me to ""--screen-layer-order"". Now my print script works with pcb 4.1 as intended.
Colour settings on the command line do indeed always override the default colours. However, the options --mirror and --layer-stack only apply properly if --screen-layer-order is in place. If I skip this option, the command seems to always print all available layers. Since I gave explicit b/w colour only for some layers, the print contained coloured lines. This confused me into thinking --layer-color-* does not override."
1753853,2018-03-25 12:56:59 UTC,"I think that the color settings on the command line should always override the default color settings. If that's not happening, then it's definitely a bug. You shouldn't have to specify --as-shown for that to happen... I don't think that is the purpose of that option."
1753854,2018-03-25 12:38:28 UTC,You're talking about the png exporter?
1753854,2018-03-26 01:18:24 UTC,"Yes, this is about the png exporter in photo realistic mode.
This is the command I use:
pcb -x png --photo-mode --dpi 600 --use-alpha --only-visible --outfile out.png  ../ioboard.pcb"
1753854,2018-04-01 19:27:29 UTC,Hi-
1753854,2018-05-20 13:17:27 UTC,"Hi Kai-Martin,"
1753860,2018-07-27 05:36:01 UTC,PR Proposed: https://github.com/CanonicalLtd/netplan/pull/40
1753861,2018-03-07 08:04:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1753863,2018-03-08 17:55:58 UTC,Hi - this is not managed by the OpenStack Foundation. It's managed by the community and led by Marton Kiss (mrmartin).
1753864,2018-05-11 15:36:08 UTC,This change was made by a bot.
1753866,2020-02-28 14:59:07 UTC,We no longer use this Groups software.
1753866,2018-03-08 17:55:06 UTC,Hi - this is not managed by the OpenStack Foundation. It's managed by the community and led by Marton Kiss.
1753867,2018-03-07 01:45:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550302"
1753867,2018-03-30 06:41:39 UTC,"Change abandoned by weikeyou (<email address hidden>) on branch: master
Review: https://review.openstack.org/550302"
1753875,2019-06-17 01:38:19 UTC,"We have addressed excessive logging due to invalid credentials and consequently, db performance in the instances described has been addressed."
1753875,2018-11-30 08:52:20 UTC,"Reoccurred today on a JAAS controller; workaround: shut down jujuds, resynced database, dropped logs collection for the controller model, started up again, changed logging config to ""<root>=ERROR;unit=ERROR""."
1753875,2018-06-26 14:19:53 UTC,"For what it's worth, we upgraded this controller from 2.3.3 to 2.3.7 on May 17th, and txns pruning stopped at that time. Today there were 56M txns documents, the oldest ones being https://pastebin.canonical.com/p/Wk4v9RyfhG/, which contain for example :"
1753875,2018-05-25 02:07:36 UTC,"We have no control over these credentials, so we have no way of updating them.  Since the only option is to delete the models entirely, I'll ask the JAAS team to review the list of affected models and approve deletion."
1753875,2018-05-25 01:33:50 UTC,"@Paul Collins (pjdc),"
1753875,2018-05-24 22:47:21 UTC,"In the interests of stopping these controllers from OOMing and paging us multiple times a day: If the invalid stored credentials are the cause of the immediate problem, and if *missing* credentials don't seem to cause Juju any serious problems (even if they give Juju developers heartburn)... can we not just manually delete the invalid credentials from the database?"
1753875,2018-05-23 23:27:01 UTC,I've gone through the logs and broken down problematic models as follows:
1753875,2018-05-22 20:31:39 UTC,"Based on the current behaviour, I think the only action that makes sense
in the short term is finding the models with invalid credentials and
removing them."
1753875,2018-05-22 15:26:32 UTC,"We have had to add sysctl panic-reboots on OOM, as the maintenance overhead of this public-facing JAAS installation was making it difficult to keep service constant."
1753875,2018-05-22 04:46:00 UTC,Here's the information I gathered per my previous comment for a recent OOM-kill of jujud-machine-2 in the affected environment: https://private-fileshare.canonical.com/~pjdc/lp1753875.machine-2.tar.gz
1753875,2018-05-22 03:27:31 UTC,Thanks for the update on the Juju changes! It sounds like a lot of work.
1753875,2018-05-22 02:42:13 UTC,"@Paul Collins (pjdc),"
1753875,2018-05-22 02:12:06 UTC,"I've started looking into this again.  We're now on 2.3.7 and the problem, whatever it is, persists."
1753875,2018-03-14 10:59:43 UTC,bug #1747368 is one of the ones about high-load on Mongo.
1753875,2018-03-14 10:58:35 UTC,"I realize that there is a fair amount of log messages around this, but do we know that this is the actual high load? There have been other issues with load and Mongo (some of which should be fixed in Juju 2.3.4).
Have you tried grabbing CPU profiles on the controller machines to see where the time is being spent?"
1753879,2018-03-07 02:46:54 UTC,If the official swift ci running on the windows's system?
1753880,2019-06-13 23:07:48 UTC,i have seen this several times in horizon but given this has been the case for as long as i have worked on openstack im triaging this as low as its easy to work around and while annoying does not really cause any harm or prevent people form working with guest that have been migrated.
1753886,2018-06-14 02:27:21 UTC,Fixed by: https://review.openstack.org/#/c/553314/
1753887,2018-07-18 14:09:22 UTC,"@chenyb4, are your working on this, if not can i assign it to myself?"
1753887,2018-07-26 17:17:59 UTC,This issue was fixed in the openstack/python-zunclient 2.1.0 release.
1753890,2020-12-10 21:59:46 UTC,Already fixed in the Quick Start guide.
1753893,2018-03-12 23:49:19 UTC,I'm marking this Fix Released because I already finalized the debian/changelog entry for mutter 3.28.0-1. The update will be synced from Debian tomorrow.
1753893,2018-03-13 00:07:51 UTC,"Fantastic, thankyou!"
1753919,2018-03-09 14:09:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551288"
1753928,2018-03-08 10:50:22 UTC,"It's probably a bit too late now, as we're past feature freeze. See https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule and https://wiki.ubuntu.com/FeatureFreeze."
1753928,2019-12-07 10:37:12 UTC,"Looks like a couple of releases went by without much happening, but Ubuntu 20.04 is now looking to release with opencv 4.1.2 (https://bugs.launchpad.net/ubuntu/+source/opencv/4.1.2+dfsg-5)"
1753936,2018-03-07 07:47:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1753936,2018-03-07 11:30:43 UTC,Upstream fixed in https://github.com/CanonicalLtd/landscape-client/commit/57802e873721a64797d1eccab977e8be26cc1d12
1753936,2018-03-09 14:14:21 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu2
1753940,2018-03-07 08:28:20 UTC,"golang should probably be checked / fixed / upstream issue filed, etc."
1753940,2018-03-07 08:28:29 UTC,and meanwhile we should probably badtest snapd in bionic.
1753940,2018-03-07 08:27:50 UTC,"I am confused about the value of running go vet, in autopkgtests, as any issues discovered by go vet, during testing of affects of reverse dependencies on a released version of snapd. This is not as installed testing, and would require manual changes to the code."
1753955,2018-03-07 12:33:41 UTC,"I have the feeling we might be displaying an error that is confusing the
issue. If I was to guess, I would say we're actually trying to create amd64
instances on a ppc machine. So it isn't that 'we can't find tools' (a red
herring) but that we can't launch the instance."
1753955,2018-03-08 10:49:22 UTC,Here is a juju crashdump if that helps any
1753955,2018-03-14 11:11:04 UTC,"Just to clarify, if you specify the Arch for the containers, then things are launched and provisioned as expected. But you'd like to have Juju assume the arch for containers from the arch for the host machines."
1753963,2018-03-07 17:58:10 UTC,"StacktraceTop:
 recreate_growing_buffer (brw=brw@entry=0x7f436e56b040, grow=grow@entry=0x7f436e5903f8, name=name@entry=0x7f43673b5d38 ""batchbuffer"", size=size@entry=20480) at ../../../../../../src/mesa/drivers/dri/i965/intel_batchbuffer.c:173
 intel_batchbuffer_reset (brw=brw@entry=0x7f436e56b040) at ../../../../../../src/mesa/drivers/dri/i965/intel_batchbuffer.c:193
 intel_batchbuffer_reset_and_clear_render_cache (brw=0x7f436e56b040) at ../../../../../../src/mesa/drivers/dri/i965/intel_batchbuffer.c:221
 brw_new_batch (brw=<optimized out>) at ../../../../../../src/mesa/drivers/dri/i965/intel_batchbuffer.c:694
 _intel_batchbuffer_flush_fence (brw=brw@entry=0x7f436e56b040, in_fence_fd=in_fence_fd@entry=-1, out_fence_fd=out_fence_fd@entry=0x0, file=file@entry=0x7f43673ba440 ""../../../../../../src/mesa/drivers/dri/i965/brw_context.c"", line=line@entry=244) at ../../../../../../src/mesa/drivers/dri/i965/intel_batchbuffer.c:1032"
1753965,2018-03-14 22:28:29 UTC,https://github.com/snapcore/snapcraft/pull/2004
1753965,2018-04-09 14:49:51 UTC,This isn't fixed unfortunately because the internal _pip module uses snapcraft.internal.common.run directly rather than the run/run/output methods of the plugin.
1753966,2020-07-01 21:04:37 UTC,Thank you for your bug report. Is that still an issue? Do you use a special location for your user directory(or remote one)?
1753966,2020-08-31 04:17:30 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1753968,2018-03-07 17:18:44 UTC,"while adding the list is trivial it is actually blocked on
https://bugs.launchpad.net/bugs/1754030"
1753968,2018-03-07 10:18:11 UTC,"Sites like this: https://kb.vmware.com/s/article/2012352 seem to indicate the VirtualSystemType field can hold multiple values, rather than just a single value."
1753968,2018-03-07 17:19:59 UTC,"When that bug is fixed, we can land"
1753969,2018-07-25 20:39:10 UTC,openstack_requirements/tests/files/upper-constraints.txt tempest-lib===1.0.0
1753969,2018-03-09 08:55:31 UTC,I think after this https://review.openstack.org/#/c/536191/ commit this bug doesn't effect Kingbird project.
1753995,2018-03-22 16:40:56 UTC,"Hi there, you are no worse situation than you were before. If you are building off of xenial you should be generally ok as long as you do not use CGO as the interpreter is pretty much stable in the world we live today."
1753995,2018-03-30 13:44:27 UTC,"Hi,"
1753995,2019-11-11 00:51:40 UTC,"Same here, also tried to build Telegraf. Obviously snapcraft tries to patch binaries to re-link them to its libc, and this patching fails for Telegraf."
1753999,2018-03-08 09:30:44 UTC,"Yes, it's a self-signed cert at that point I used to move forward manually."
1753999,2018-03-08 09:12:08 UTC,"How does the IP address work when we don't have a valid cert for the
controller because we're still waiting for the let's-encrypt certificate.
Juju doesn't serve anything out without https. Is it just a self-signed
cert until LE gives us their signature on it?"
1753999,2018-03-08 09:58:21 UTC,"Are we having an issue that 'juju gui' is trying to connect to 443 instead
of 17070? That shouldn't be the case because if you have dns-name set we
only serve the controller on 443.
There is no reason that a DNS name wouldn't connect, but an IP address
would *as long as* your DNS record actually points to the machine."
1753999,2018-03-08 07:09:00 UTC,"Are we able to figure out the IP address if we are trying to get a DNS
name? Did you try the IP address yourself and see that it worked?"
1753999,2018-03-08 07:24:01 UTC,So the IP address works fine. It's just the autocert-dns-name does some handshaking with let's encrypt and that took some 4minutes to complete. I attempted to get the GUI details during that time and instead of the timeout the info that would be there w/o let's encrypt would be helpful I believe.
1754015,2018-03-23 06:19:51 UTC,"I don't have an artful around to test, FWIW."
1754015,2018-04-23 18:40:59 UTC,"This bug was fixed in the package nova - 2:16.1.0-0ubuntu1~cloud0
---------------"
1754015,2018-04-23 18:40:55 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1754015,2018-04-18 00:18:29 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1754015,2018-04-18 00:18:13 UTC,This bug was fixed in the package nova - 2:16.1.0-0ubuntu1
1754015,2018-04-16 11:53:12 UTC,"Testing completed successfully for artful-proposed:
1. create new artful LXD container
2. sudo add-apt-repository cloud-archive:pike-proposed ; sudo apt update
3. echo 'APT::Install-Recommends ""false"";' | sudo tee /etc/apt/apt.conf.d/99no-recommends
4. sudo apt-get install nova-compute-kvm
5. version is 2:16.1.0-0ubuntu1
6. verify ipxe-qemu is installed"
1754015,2018-04-13 07:14:07 UTC,"Testing done :
1. create new xenial LXD
2. sudo add-apt-repository cloud-archive:pike-proposed ; sudo apt-get update
3. echo 'APT::Install-Recommends ""false"";' | sudo tee /etc/apt/apt.conf.d/99no-recommends
4. sudo apt-get install nova-compute-kvm
5. verify ipxe-qemu is installed"
1754015,2018-04-04 09:01:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754015,2018-03-22 21:21:21 UTC,"Hello Junien, or anyone else affected,"
1754015,2018-03-23 11:44:36 UTC,"Hello Junien, or anyone else affected,"
1754015,2018-03-12 20:50:41 UTC,This bug was fixed in the package nova - 2:17.0.1-0ubuntu1
1754015,2018-03-22 19:21:34 UTC,I've uploaded a new version of nova to the Artful review queue where it is awaiting SRU team review [1]. Once it is accepted into artful-proposed we can backport this to pike-proposed for testing.
1754015,2018-03-12 09:33:50 UTC,"Hi,
first I agree to Coreys first checks."
1754015,2018-03-12 09:00:05 UTC,"I don't think that we can't close this bug because it's not resolved. I shouldn't have to manually install packages to get a working cloud, even if I have APT::Install-Recommends set to False."
1754015,2018-03-09 22:26:02 UTC,"Hi Junien,"
1754015,2018-03-09 14:38:57 UTC,Note that ipxe-qemu is also needed on ppc64el
1754015,2018-03-09 06:40:20 UTC,"Hi,"
1754015,2018-03-08 16:28:00 UTC,... mark this incomplete until we have further details.
1754015,2018-03-08 16:27:43 UTC,"Hi Junien,"
1754016,2018-03-07 13:30:08 UTC,This change was made by a bot.
1754016,2018-03-08 09:12:54 UTC,"Hello,
fresh install of daily build of 18.04 and done updates once.. nothing more"
1754016,2018-03-07 13:19:13 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1754026,2018-03-07 17:51:47 UTC,"The DuplicateOptError is probably caused by reusing a ConfigOpts instance with a slightly different definition of the zfssa_rest_timeout option, and I do see at least 2 places that option is defined, in zfssaiscsi.py and zfssanfs.py:"
1754026,2018-03-07 17:54:00 UTC,"The problem in Ironic appears to be that the mock is being created too early, so changes in the library behavior are invoking os.path.exists() more often than expected. I suggest moving the decorator that mocks out os.path.exists() to be a context manager inside the test function around the call where the mock is actually needed."
1754026,2018-03-12 11:34:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551973"
1754026,2018-03-12 11:41:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551975"
1754026,2018-03-12 14:06:25 UTC,"Reviewed:  https://review.openstack.org/551973
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=ac65ec6a6eaf4a537e36ad1598e8ce5b818639b1
Submitter: Zuul
Branch:    master"
1754026,2018-03-27 02:14:05 UTC,"Reviewed:  https://review.openstack.org/551975
Committed: https://git.openstack.org/cgit/openstack/ironic-inspector/commit/?id=5c63f1490c9429841a31af21de5d3461a718c8f5
Submitter: Zuul
Branch:    master"
1754026,2018-05-16 13:34:59 UTC,This issue was fixed in the openstack/ironic-inspector 7.3.0 release.
1754026,2018-07-05 10:15:25 UTC,This issue was fixed in the openstack/ironic 11.0.0 release.
1754030,2018-03-23 16:47:01 UTC,"I said that I'd attach OVFs for the v11 VMs with and without the serial console.  Having looked at them there are no differences between them except the serial stanza, previously I thought we might have other deltas that might be interesting.  I've abandoned that path of investigation.  The kernel cmdline setting appears to be the culprit."
1754030,2020-04-25 22:37:47 UTC,"And yes, this is still an issue on the 1804 and 2004 .ova images."
1754030,2020-04-25 22:37:26 UTC,"If you're looking for reasons why customers require a later VM hardware version, you need version 11 for the faster spectre/meltdown mitigations (11 enables PCID/INVPCID) and you need version 13 or 15 (the documentation varies on which it is) to support the VMWare Cloud Provider and do things like using vmdks as dynamic storage in your kubernetes cluster."
1754030,2018-03-23 16:45:28 UTC,In /etc/default/grub.d/50-cloudimg-settings.cfg we set the console on the kernel command-line to use both tty1 and ttyS0.  For v11 VMs with no changes to the hardware configuration (no addition of a serial console) we need to remove ttyS0 from the kernel command-line to prevent boot from stalling.
1754030,2018-03-08 13:09:27 UTC,"Just to confirm, I tried it with both Xenial and Bionic images (ubuntu-bionic-18.04-cloudimg-20180307)"
1754030,2018-03-22 15:20:21 UTC,"John,"
1754030,2018-03-08 11:26:17 UTC,"I tried going via the vsphere web UI (flash) and directly booting xenial-server-cloudimg-amd64-disk1.vmdk but its possible I had set up the configuration incorrectly.
I've since tried to just directly import the ova from the 'govc' commandline:
govc import.ova ./xenial-server-cloudimg-amd64.ova"
1754030,2018-03-23 02:02:06 UTC,"While not a critical priority, we really want vSphere to be a well supported cloud, and that means supporting the newer hardware versions. There was a customer request to support v13, but since our vSphere was only version 6, we only had hardware v11."
1754030,2018-03-22 15:14:16 UTC,"I've pulled the latest xenial OVA, imported via vSphere 6 client, upgraded to v11 hardware; this recreated the failure.  I then added a serial console for this VM by editing the VM settings (console to file) and booted to get more debug info; now the VM boots."
1754033,2018-03-07 13:52:14 UTC,Added the file with the applied patch.
1754033,2018-03-07 16:18:38 UTC,"The attachment ""Adding error messages"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1754035,2018-03-07 22:24:16 UTC,"Please attach these files as a zip/tar package:
/boot/grub/grub.cfg
/etc/grub.d (all files)
/etc/default/grub"
1754035,2018-03-07 22:42:25 UTC,Bonjour Daniel
1754035,2018-03-12 04:08:03 UTC,"Ok thanks. I did remove all those files. Uninstall grub-customizer.
Reinstall grub in Manjaro with ""grub-install"" and ""update-grub"".
Re-install grub-customizer.
Now there is no error running the customizer but it only sees Manjaro,
nothing else. Not Mint nor Peppermint. Strange."
1754035,2018-03-12 12:17:35 UTC,"Ok Daniel, more info on this if that can help you. I tried
Grub-Customizer on another Manjaro machine. No error on running by the
program but it says that there was scripts to be updated and perform a
saving. I tried but the following error pop up. (Translate from French)."
1754035,2018-03-18 23:31:54 UTC,"Hello Daniel, just want to keep you up to date. I received a huge update
from Manjaro which include a new grub (2.03). Now GC can detect all my
OS (3) ! It run without issues and can write a new configuration. The
only thing which doesn't work so good is that moving around the entries
does not work or behave strangely. Hopefully you will get it all sorted out."
1754035,2018-03-11 21:07:48 UTC,Unfortunately I can't reproduce the problem using your files. So this will take some time to debug.
1754041,2019-09-19 14:46:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1754045,2018-04-23 14:12:35 UTC,"I have not seen this issue since the latest improvements, hence marking it as incomplete."
1754045,2019-09-19 14:46:53 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1754048,2019-06-12 04:26:43 UTC,"Reviewed:  https://review.opendev.org/653068
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c2be944fb89f94a10d7105b2e072eeab5582c5a7
Submitter: Zuul
Branch:    master"
1754048,2019-07-30 06:30:39 UTC,"Reviewed:  https://review.opendev.org/651614
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d78ac78395e05bbcce6674d7150e8ec25c3a558e
Submitter: Zuul
Branch:    master"
1754048,2019-09-27 09:10:49 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1754048,2019-04-16 18:16:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653068"
1754048,2018-08-02 21:48:50 UTC,This was technically found in the Queens release and probably true for older releases that use federation. I don't think this is something we need to fix for Rocky.
1754048,2018-03-19 16:20:14 UTC,"I noticed this when doing some refactoring of the token provider API recently. I agree that we should get the token provide up-to-speed by populating the identity provider's domain in the token response, instead of the cookie-cutter Federated domain."
1754048,2019-04-10 17:23:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651614"
1754051,2018-03-07 14:36:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754051,2018-05-02 08:55:00 UTC,"Meanwhile, please upgrade to version 1.2018.4"
1754051,2018-05-02 09:10:36 UTC,See also bug report at Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897414
1754051,2018-09-26 07:37:56 UTC,"Meanwhile version 2018.11 is the latest stable. Please, include that in Cosmic release."
1754051,2020-01-08 15:30:57 UTC,Upgrade to version 1.2019.13 please.
1754051,2020-08-06 12:10:10 UTC,"1:1.2018.13+ds-2 published in focal-release on 2019-10-18
1:1.2020.2+ds-1 published in groovy-release on 2020-04-30"
1754055,2020-12-09 04:17:24 UTC,[Expired for cloud-init (Ubuntu) because there has been no activity for 60 days.]
1754055,2020-10-09 19:58:00 UTC,"Hi,"
1754056,2018-03-07 16:19:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1754056,2018-03-07 16:47:41 UTC,"- added package gnome-settings-daemon
- I should mention that I tried to figure out the key-code by using XEV, but it does not work"
1754056,2018-10-16 06:59:37 UTC,"Ok, I ""solved"" this issue, by moving to Kubuntu. KDE allows the user to choose what which button should do. So I simply linked the ""switch off"" command to the button on my keyboard and now it works as before. No idea why Ubuntu is making such a mess of a simple feature like this. Additionally I am now able to have buttons on both sides of the window title bars. What a nice feature on a quite large TV screen."
1754062,2019-08-01 14:14:19 UTC,Marking as fix released in openstacksdk with https://review.opendev.org/#/c/550558/
1754062,2019-03-07 14:21:17 UTC,@Michal
1754062,2019-03-07 13:06:48 UTC,"@James , could you please show me that patch ? Thanks"
1754062,2019-01-14 18:07:18 UTC,"@Francois - This isn't completely fixed, yet, but a new patch set went up today."
1754062,2018-12-17 16:15:41 UTC,"I'm not sure this issue is actually fixed, I gave it a try today without any luck using the lastest python-openstackclient."
1754062,2018-04-26 19:39:43 UTC,This issue was fixed in the openstack/neutron-lib 1.14.0 release.
1754062,2018-03-13 12:16:18 UTC,"Reviewed:  https://review.openstack.org/550588
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=ce10b9df28ece6daee1f199740b672aae707630b
Submitter: Zuul
Branch:    master"
1754062,2018-03-12 15:03:55 UTC,"Just a comment since Amotoki commented in my neutron-lib api-ref change - when the subnetpool was created, the default_prefixlen value should have been specified (in this case at 28), that way callers don't need to specify it.  I think it defaults to min_prefixlen if not specified.  We still need to fix the bug..."
1754062,2018-03-07 20:11:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550588"
1754062,2018-03-07 18:32:18 UTC,"Hi Brian,"
1754062,2018-03-07 16:24:37 UTC,"So it looks like there are multiple issues here - the api-ref in neutron-lib is missing this field, and as you stated, the sdk is missing it probably because it's not listed.  I'll ping someone to take a look at the api-ref.  I'm not that familiar with the sdk but if you had a simple patch that helps feel free to post it and I'll take a look.  Thanks."
1754066,2018-03-07 15:24:48 UTC,As part of https://review.opencontrail.org/#/c/40011/ I've added a patch for python (tarfile_verbose.py) that will print file paths on exception.
1754069,2021-02-08 00:28:00 UTC,"The attachment ""completely untested debdiff for hirsute"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1754069,2021-02-08 00:22:51 UTC,"unfortunately, this fails to build in bionic ATM"
1754069,2021-02-07 23:13:36 UTC,found a previous patch that applies cleanly to bionic
1754069,2021-02-07 22:52:40 UTC,"Unfortunately, the sources do not apply cleanly to bionic.  We probably need an older patch."
1754069,2021-02-07 22:39:12 UTC,"$ QUILT_PATCHES=debian/patches/ quilt push
Applying patch debian/patches//nautilus-restore-typeahead.patch
patching file data/org.gnome.nautilus.gschema.xml
Hunk #1 succeeded at 195 (offset 3 lines).
patching file src/nautilus-global-preferences.h
patching file src/nautilus-list-view.c
Hunk #1 succeeded at 3121 (offset 41 lines).
Hunk #2 succeeded at 3153 (offset 41 lines).
Hunk #3 succeeded at 4187 (offset 97 lines).
patching file src/nautilus-list-view.h
patching file src/nautilus-window-slot.c
Hunk #2 succeeded at 131 with fuzz 2 (offset 2 lines).
Hunk #3 succeeded at 263 (offset 22 lines).
Hunk #4 succeeded at 794 (offset 30 lines).
Hunk #5 succeeded at 1411 (offset 44 lines).
Hunk #6 succeeded at 3272 (offset 61 lines).
Hunk #7 succeeded at 3333 (offset 61 lines).
Hunk #8 succeeded at 3862 (offset 122 lines).
Hunk #9 succeeded at 3948 with fuzz 2 (offset 157 lines)."
1754069,2021-02-07 22:39:00 UTC,"FWIW, the patch from arch at least still applies cleanly to the hirsute sources"
1754069,2018-09-15 15:46:54 UTC,Either reopen #1164016 or keep this one open (since in 1164016 you asked me to open a new one instead).
1754069,2018-03-07 17:02:45 UTC,"(and as usual I can't even edit my own comments, so here comes an additional comment to correct a typo):"
1754069,2018-03-07 17:01:33 UTC,"But actually I wonder why Ubuntu still keeps Nautilus as the file explorer, given the level of stupidity that the upstream developer have demonstrated. In the last year, I have seen nothing but completely retarded design decision and regressions that degrade usability beyond the unthinkable, and not a simple improvement."
1754069,2018-03-07 16:59:39 UTC,"> 'Released' is a dev decision, not a user one.
"
1754069,2018-03-07 16:39:00 UTC,"'Released' is a dev decision, not a user one.
What you request is an upstream design choice, which we possibly get with 3.28. So nothing can be made on old releases as they only get 'security' fix and backport sometimes."
1754069,2021-02-07 22:24:33 UTC,"@teo1978: I (and hundreds others as seen in bug 1164016 share your pain), but your tone and choice of language isn't helping your case."
1754070,2018-04-09 21:17:40 UTC,This issue was fixed in the openstack/bifrost 5.0.1 release.
1754070,2018-08-10 21:39:48 UTC,This issue was fixed in the openstack/bifrost 5.1.0 release.
1754070,2018-03-16 09:26:26 UTC,"Proposed solution: https://review.openstack.org/#/c/550573. That appears to fix the issue, in combination with https://review.openstack.org/#/c/512699."
1754070,2018-03-07 16:09:09 UTC,"ironic==10.2.0.dev81
keystoneauth1==3.4.0
keystonemiddleware==4.21.0
openstacksdk==0.11.3
os-client-config==1.29.0
python-ironicclient==2.2.0
python-keystoneclient==3.15.0
python-openstackclient==3.14.0"
1754070,2018-03-14 09:54:47 UTC,might be related to https://bugs.launchpad.net/python-openstackclient/+bug/1724283
1754070,2018-03-07 15:45:53 UTC,Here's the change that switched to the none auth_type: https://github.com/openstack/bifrost/commit/21ca45937a9cb36c6f04073182bf2edea8acbd5d.
1754070,2018-03-14 11:44:14 UTC,"Thanks for the link to that issue. I checked keystoneauth in my environment, and I do have Vlad's change (https://review.openstack.org/515730), which was included in keystoneauth1 3.4.0."
1754072,2019-09-19 18:07:36 UTC,No longer an issue but nobody updated this bug report.
1754072,2018-03-09 18:09:27 UTC,The attachment is what I see when video detection succeeds.
1754072,2018-03-09 17:30:05 UTC,I think that the slowness and the alternate screen sequence is related.
1754072,2018-03-09 18:10:30 UTC,The attachment is the 1st screen when video detection fails.
1754072,2018-03-09 10:29:39 UTC,Is this bug the result of trying to test suspend in a virtual machine?
1754072,2018-03-07 16:05:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754072,2018-03-09 17:28:59 UTC,This was a Live Session without VM.
1754073,2018-04-26 09:10:19 UTC,Thank you for the very thoughtful Regression Potential section. Please could you confirm that the opposite scenarios have been verified as written up there? Please also confirm the package versions tested.
1754073,2018-05-02 02:20:50 UTC,This bug was fixed in the package landscape-client - 16.03-0ubuntu3.17.10.3
1754073,2018-05-02 02:13:47 UTC,This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.4
1754073,2018-05-02 02:13:25 UTC,"The verification of the Stable Release Update for landscape-client has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1754073,2018-05-02 02:13:14 UTC,This bug was fixed in the package landscape-client - 14.12-0ubuntu6.14.04.3
1754073,2018-04-30 13:27:11 UTC,"I've tested:
16.03-0ubuntu3.17.10.3
16.03-0ubuntu2.16.04.4
14.12-0ubuntu6.14.04.3
to ensure they're working properly.
I don't have access to a Apache Cloudstack instance to test that particular detection part but that was tested by Karify DevOps (karifydevops) on Trusty."
1754073,2018-04-30 10:46:40 UTC,"As per Robie's comment, could you also give us some more information regarding how the package has been tested, what test cases have been actually performed as part of the verification?"
1754073,2018-04-24 15:41:25 UTC,"I have the package from -proposed running on a few xenial containers, VMs and hardware to make sure it still works."
1754073,2018-04-19 08:17:02 UTC,I have tested this new package on trusty and now works as intended.
1754073,2018-04-05 09:04:58 UTC,"Hello Alex, or anyone else affected,"
1754073,2018-04-05 09:02:43 UTC,"Hello Alex, or anyone else affected,"
1754073,2018-04-05 08:53:42 UTC,"Hello Alex, or anyone else affected,"
1754073,2018-03-29 19:14:34 UTC,Sponsored for A/X/T
1754073,2018-03-29 15:41:57 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu3
1754073,2018-03-29 14:13:40 UTC,Sponsored for bionic.
1754073,2018-03-27 16:20:52 UTC,"The attachment ""bionic.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1754073,2018-03-26 14:09:35 UTC,committed upstream https://github.com/CanonicalLtd/landscape-client/commit/e08cd1ac06b0c2e1761749e05e10593a4b123317
1754073,2018-04-06 14:42:01 UTC,"I don't have access to a Apache Cloudstack instance to test the detection part. I""ve installed it on Trusty and Xenial yesterday. All works as expected."
1754075,2018-04-09 11:14:37 UTC,"On Monday, 9 April 2018 12:56:12 CEST Lars Kollstedt wrote:
[...]

> This patch should IMHO work, but I have no opportunity to test it without
> your help, since we're in udeb and testing preseed issues. ;-)
"
1754075,2018-04-23 16:22:42 UTC,Of course only if they're inheriting special repositories this way. But the bugs referenced here IMHO are showing lot's of examples representing different reasons and ways to do this. ;-)
1754075,2018-07-17 16:05:10 UTC,Any progress on this?  This is a serious regression for us which makes preseed substantially less functional in bionic...
1754075,2018-10-19 11:30:10 UTC,Easy workaround which does not require another apt-setup.udeb:
1754075,2019-01-21 22:17:02 UTC,"I've just been bitten by this bug while upgrading our business PXE/preseed installations from Xenial to Bionic. We use an internal private repository for company specific packages. I'm unable to get the apt key installed with the preseed, so nothing works."
1754075,2019-01-24 12:26:50 UTC,"I too used the workaround:
d-i preseed/late_command string \
   in-target wget -q -O /etc/apt/trusted.gpg.d/repo_key.asc http://our.repo/repo_key.asc ; \"
1754075,2019-05-08 14:54:03 UTC,This bug was fixed in the package apt-setup - 1:0.141ubuntu3
1754075,2019-01-31 10:40:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754075,2019-03-24 21:08:36 UTC,Same problem here. We are using a preseed with two local repos for or own packages and we cant use local0 and local1 due to the problem with keys.
1754075,2019-03-28 14:34:23 UTC,We are working to deploy Ubuntu18 using PXE to a bunch of computers and would love to see this problem solved.
1754075,2018-04-23 16:17:22 UTC,"Hello again,"
1754075,2019-05-20 11:13:38 UTC,"Hello Manoj, or anyone else affected,"
1754075,2019-06-11 09:46:11 UTC,"I installed Ubuntu once with release apt-setup (ubuntu5) and once with proposed (ubuntu5.1). With release, the generator failed; with the proposed update the repository configured in preseed was correctly added."
1754075,2019-01-30 14:19:14 UTC,From the apt side: The patch in #12 looks correct - we want people to put the keys in trusted.gpg.d like this.
1754075,2018-04-23 15:50:56 UTC,"Hello,"
1754075,2018-04-09 10:56:12 UTC,"Hi,"
1754075,2018-04-12 05:50:46 UTC,"Hello,"
1754075,2018-04-09 12:26:32 UTC,"The attachment ""replace_apt_key_add.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1754075,2019-06-12 21:23:02 UTC,This bug was fixed in the package apt-setup - 1:0.104ubuntu5.1
1754075,2018-04-05 20:29:09 UTC,In apt-setup-0.104ubuntu5/generators/60local there is an call
1754075,2018-04-05 20:14:29 UTC,"Hi again,"
1754075,2018-03-28 06:26:19 UTC,"Hi again,"
1754075,2018-03-26 16:01:54 UTC,"Hi,"
1754075,2018-03-26 13:20:49 UTC,Didn't want to throw out apt-setup.
1754075,2018-03-26 13:19:38 UTC,apt-key complains about missing necessary gnupg or gnupg2 package.
1754075,2018-03-26 13:11:15 UTC,Repeating Comment to make the Bugs clickable (can't edit):
1754075,2018-03-26 13:08:15 UTC,"Hi again,"
1754075,2018-03-26 10:59:46 UTC,"Hi,"
1754075,2018-03-26 10:30:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754075,2018-04-23 14:58:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754075,2019-06-12 21:23:08 UTC,"The verification of the Stable Release Update for apt-setup has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1754078,2018-03-08 12:28:50 UTC,apport information
1754078,2018-03-08 12:28:51 UTC,apport information
1754078,2018-03-08 12:28:49 UTC,apport information
1754078,2018-03-08 12:28:53 UTC,apport information
1754078,2018-03-08 12:28:54 UTC,apport information
1754078,2018-03-08 12:28:52 UTC,apport information
1754078,2018-03-08 12:28:48 UTC,apport information
1754078,2018-03-08 12:28:44 UTC,apport information
1754078,2018-03-08 12:28:46 UTC,apport information
1754078,2018-03-08 12:28:45 UTC,apport information
1754078,2018-03-08 12:28:47 UTC,apport information
1754078,2018-03-08 12:28:43 UTC,apport information
1754078,2018-03-08 12:28:42 UTC,apport information
1754078,2018-03-07 16:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754079,2020-08-06 16:44:03 UTC,The same is true with the HP Laserjet M12122nf printer. The duplex function is disabled in applications and the two-sided option does not appear in the settings.
1754079,2018-03-16 17:31:45 UTC,"Hello Afshan,"
1754079,2018-03-16 04:35:28 UTC,"Hi Michael,"
1754079,2018-03-15 13:29:06 UTC,lpinfo -v should be lpinfo -m.
1754079,2018-03-15 13:19:00 UTC,"Hello Michael,"
1754079,2018-03-14 12:14:03 UTC,"Hi Michael,"
1754079,2018-03-14 21:46:37 UTC,"Hi Afshan,"
1754079,2018-03-09 15:08:35 UTC,"Hi Brian,"
1754079,2018-03-08 23:19:05 UTC,"Hello Michael,"
1754079,2018-03-08 21:24:43 UTC,"Hi Brian,"
1754079,2018-03-08 19:56:44 UTC,You have installed the printer with the wrong PPD file. (Or you do not have an M452dw).
1754079,2018-03-08 18:58:01 UTC,The driver does not show duplex as an option.  The only option that is display is for the 3rd tray.  I've also looked at the ppd and didn't see any mention of a duplex settings in it.
1754079,2018-03-08 11:17:57 UTC,"From the CUPS web interface at localhost:631 go to Printers, select the queue and move on to Administration and Set Default Options. Then Options Installed and set Duplex unit to On."
1754079,2018-03-09 18:07:26 UTC,"Thanks for pursing this, Michael; because I always use Debian's packages I tend to forget about developers.hp.com as a source for HPLIP. BTW, I have no connection with the project; I am just a user, like you."
1754084,2018-09-11 23:25:41 UTC,Works for me too
1754084,2018-10-21 17:11:56 UTC,Same problem using kubuntu-desktop on 18.04
1754084,2018-12-13 14:53:44 UTC,Same problem on Kubuntu 18.10
1754084,2019-01-09 03:28:34 UTC,Same problem on Ubuntu 18.10 with both the repo 0.16.6712+dfsg1-3build1 version and the current Appimage 0.17 version.
1754084,2019-07-17 20:12:44 UTC,I have prepared a change to the Debian package that will eliminate this issue.
1754084,2019-02-09 00:10:35 UTC,I am using the freecad 0.18-pre appimage on elementary juno (ubuntu 18.04) and this worked for me:
1754084,2020-05-21 10:06:50 UTC,"As noted in the Debian bug this may be a driver issue.
Freecad starts fine for me on Ubuntu 20.04 with nvidia drivers on a  Geforce GTX 1060"
1754084,2018-09-06 23:45:11 UTC,Same here. 'LIBGL_DRI3_DISABLE=true freecad' worked OK
1754084,2019-01-09 03:30:27 UTC,"$ freecad
FreeCAD 0.16, Libs: 0.16R
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2015
  #####                 ####  ###   ####
  #                    #      # #   #   #
  #     ##  #### ####  #     #   #  #   #
  ####  # # #  # #  #  #     #####  #   #
  #     #   #### ####  #    #     # #   #
  #     #   #    #     #    #     # #   #  ##  ##  ##
  #     #   #### ####   ### #     # ####   ##  ##  ##"
1754084,2018-08-30 16:47:31 UTC,I have the same error.
1754084,2018-05-21 00:46:27 UTC,"hi Jens, hi all,
thanks a lot for answering. In my case I had a fresh install of Xubuntu
18.04, so there was no old .config there."
1754084,2018-06-13 15:07:39 UTC,"So, I think I've figured it out."
1754084,2018-06-24 10:10:13 UTC,"Don: thanks for finding the corresponding Debian bug report (comment #3). I've added a bug watch, so that this bug will be automatically notified once the status changes in Debian."
1754084,2018-03-11 10:54:40 UTC,"This happens with ""Gnome with X11"" and not with ""Gnome with Wayland"""
1754084,2018-03-18 20:37:54 UTC,See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890882
1754084,2018-03-31 17:16:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754084,2018-03-08 02:36:09 UTC,I can't reproduce this in a VM running the latest bionic daily build. Can you give more information on your setup?
1754084,2018-05-06 16:25:17 UTC,"Same deal here, 18.04 on a Ryzen 7 2700U (laptop variant) Could be AMD/ryzen specific?"
1754084,2018-05-12 06:22:45 UTC,"I have the same problem. In the end I went down to kubuntu 16.04 I only have the problem in Ubuntu 18.04.
 In Ubuntu 16.04 and 17.10 I had no problem."
1754084,2018-05-20 18:51:54 UTC,"I have the same problem with the stock version of Freecad. I have just upgraded and Freecad stopped working.
The output is the same as described above... but I have installed Freecad 0.17 beta from the Ubuntu Software package and it seems to work when I launch it from a terminal with the freecad.FreeCAD command."
1754084,2018-05-01 18:11:45 UTC,Same think happened on Lubuntu 18.04.
1754086,2018-07-02 14:33:37 UTC,"This is most likely a bit of a race between ceph-osd units being up and running, and the pool creation in ceph-mon occuring."
1754092,2018-12-07 18:07:40 UTC,"affects 18.04.1 LTS
Firefox 63.03"
1754092,2019-01-08 15:29:37 UTC,firefox 60.4.0 affected
1754104,2018-10-09 19:54:06 UTC,This issue was fixed in the openstack/cinder 12.0.4 release.
1754104,2018-06-08 20:42:22 UTC,This issue was fixed in the openstack/cinder 13.0.0.0b2 development milestone.
1754104,2018-06-15 13:31:20 UTC,This issue was fixed in the openstack/watcher 1.10.0 release.
1754104,2018-07-27 07:44:37 UTC,This issue was fixed in the openstack/manila 6.0.2 release.
1754104,2018-08-21 17:39:41 UTC,"Reviewed:  https://review.openstack.org/566790
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=2295f537c53638895809a41bc140afa417b94f55
Submitter: Zuul
Branch:    stable/queens"
1754104,2019-07-10 07:53:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670005"
1754104,2019-08-13 02:49:18 UTC,"Change abandoned by zengjia (<email address hidden>) on branch: master
Review: https://review.opendev.org/670937"
1754104,2019-07-16 03:20:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670937"
1754104,2019-07-17 03:53:40 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/671181"
1754104,2019-07-17 08:36:00 UTC,"Reviewed:  https://review.opendev.org/671181
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=ea5cbf633cfa56a418a79cde4ccfea0c1f6f3f92
Submitter: Zuul
Branch:    feature/losf"
1754104,2019-07-22 20:15:08 UTC,This issue was fixed in the openstack/swift 2.22.0 release.
1754104,2018-06-07 22:08:31 UTC,This issue was fixed in the openstack/manila 7.0.0.0b2 development milestone.
1754104,2019-07-11 19:00:22 UTC,"Reviewed:  https://review.opendev.org/670005
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=0ae1ad63c10ea8643fc0998dca159b844286c414
Submitter: Zuul
Branch:    master"
1754104,2018-05-11 14:05:16 UTC,"Reviewed:  https://review.openstack.org/567581
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=bd6c800f8f01dd285b67a8e1a8d2d440090217b2
Submitter: Zuul
Branch:    stable/queens"
1754104,2018-04-04 19:48:23 UTC,"Will want to backport this one, the duplicates are beginning to pile up."
1754104,2018-05-08 06:22:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/566790"
1754104,2018-05-07 11:57:06 UTC,I've marked this as affecting the upstream cinder/manila projects rather than the Ubuntu cinder/manila packages. Please feel free to switch it back if it does in fact affect Ubuntu packages. Thanks.
1754104,2018-05-04 19:19:32 UTC,"Upstream projects, rather."
1754104,2018-05-04 19:17:21 UTC,"Hi junboli,"
1754104,2018-04-24 18:11:16 UTC,This issue was fixed in the openstack/glance 16.0.1 release.
1754104,2018-04-19 14:01:59 UTC,This issue was fixed in the openstack/glance 17.0.0.0b1 development milestone.
1754104,2018-04-05 19:09:26 UTC,"Reviewed:  https://review.openstack.org/559136
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=704483fa9d8df5ba2e362e6d206f4a6c8745ea0e
Submitter: Zuul
Branch:    stable/queens"
1754104,2018-04-05 17:20:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/559136"
1754104,2018-04-05 16:31:09 UTC,"Reviewed:  https://review.openstack.org/558932
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=7dfce420279423708138596c6646551308058b50
Submitter: Zuul
Branch:    master"
1754104,2018-04-05 12:28:16 UTC,"Marked this as critical for stable/queens, because triaging these duplicates takes up a lot of time, plus this will not cause any code regressions."
1754104,2018-04-04 21:12:25 UTC,"Forgot the closes-bug tag on the review, so here it is: https://review.openstack.org/558932"
1754104,2018-04-04 19:53:03 UTC,from https://docs.openstack.org/keystone/latest/install/keystone-install-ubuntu.html
1754104,2018-05-10 12:36:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/567581"
1754110,2020-07-30 14:27:50 UTC,"Pushed to master for inclusion in 3.6, along with a tweak to the release notes. Thanks, Kyle and Jane!"
1754110,2020-07-20 15:18:18 UTC,"Thanks, Kyle.  It works well for me.  I was able to add all sorts of amusing labels to the fields in the patron registration form! :-D"
1754110,2018-09-11 17:41:24 UTC,"I've updated the branch by rebasing to the latest master, and added release notes in an additional commit - I wasn't entirely certain where to place them, but the API subfolder seemed closest to what would make sense."
1754110,2018-08-30 20:32:02 UTC,"Kyle,"
1754110,2018-03-07 17:49:57 UTC,Branch can be found here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1754110-patron-reg-field-label-override
1754110,2018-08-31 15:38:39 UTC,"Hey Kathy,"
1754111,2018-03-09 18:59:10 UTC,Mmmm...  Happened again on the last update.  I didn't look to see if the System76 driver was part of the updated packages.
1754111,2018-03-09 19:03:12 UTC,See also: https://bugs.launchpad.net/-driver/+bug/1754113
1754111,2018-03-09 19:04:04 UTC,https://bugs.launchpad.net/system76-driver/+bug/1754113
1754113,2018-03-09 19:02:54 UTC,See also https://bugs.launchpad.net/system76-driver/+bug/1754111
1754124,2018-05-10 03:03:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754125,2020-02-11 08:54:03 UTC,@Paul White
1754125,2021-01-05 16:24:53 UTC,"""Stop & Quit"" might not always work in slow / single core machines."
1754125,2020-04-06 15:01:17 UTC,"For some of the depressing history of this, see bug #875002 (which has been incorrectly marked as fixed by someone without a clue) from way back in 2011."
1754125,2020-02-11 11:13:19 UTC,"Paul, the ""Stop & Quit"" action is certainly a plus, but it doesn't solve this precise bug report, as there still is a case where ""Rhythmbox stays running in the background after quit"" (if you just close the window). I'm not the one to decide whether or not this is the desired behaviour, but I just think that the ""Stop & Quit"" action is only a workaround for this bug."
1754125,2020-02-11 10:13:11 UTC,"Julien, you are right in that the icon disappears if the program is simply closed with 'Quit'."
1754125,2020-02-11 08:24:04 UTC,In rhythmbox 3.4.4 there is an additional quickmenu option of 'Stop & Quit'. This version will be in Ubuntu 20.04. Does that addition fix this bug? It works for me but others may disagree.
1754125,2018-03-27 15:04:36 UTC,"tagging rls-bb-notfixing, it's not important enough to be milestoned"
1754125,2019-10-19 11:12:55 UTC,This all comes down to a truly awful and bad patch Ubuntu adds that in effect breaks the program.
1754125,2018-03-07 22:30:46 UTC,How are you closing RhythmBox? The program is not actually closed if music is playing and you press the X on the top right corner. Usually I had to do CTRL+Q if I wanted to actually shut it down. Can you try this?
1754125,2018-03-08 15:53:15 UTC,"I have tried CTRL+Q. Still does not shut down. The only way is to kill the
process."
1754125,2020-02-11 08:10:29 UTC,"This behaviour might me perfect in the default Ubuntu desktop (gnome-shell + Unity plugins), but it's broken if you use upstream gnome-shell because there is no tray to control Rhythmbox from once closed."
1754125,2018-03-27 17:10:45 UTC,We decided today that we're going to leave the current behavior for 18.04 LTS.
1754125,2018-03-28 10:20:16 UTC,"It does only stay active if it's playing, if you stop the song first and close it then it exits, you can also exit while playing using the file->exit menu entry"
1754129,2018-03-07 21:41:18 UTC,"- confirmed on Windows 10, Inkscape 0.92+devel (9d6b0e8, 2018-02-18)"
1754129,2018-03-09 05:45:23 UTC,"@apenner corrected, the icons for 'Tile' and 'Component Transfer' are missing from the 'share/icons' directory."
1754130,2019-01-18 15:25:10 UTC,"@Seth, I set the milestone to 6.0.0-rc1 unless you can figure out a way to partially map the Eagle netclass constraints to KiCad.  Feel free to change it back to 5.1 if you think you can knock this out quickly."
1754130,2018-12-20 00:38:32 UTC,Let's hold off on postponing this item.  I suspect it is a relatively easy fix although I haven't dug into it yet.
1754130,2019-01-10 14:55:47 UTC,"According to this email https://lists.launchpad.net/kicad-developers/msg38945.html this cannot be fixed until we implement netclass to netclass clearances.  Since this would be part of the new constraint system, this should be changed to milestone 6.0.0-rc1 unless this information is not correct."
1754130,2018-03-15 22:49:53 UTC,Here are Eagle net class test files. Pictures above has been generated using this test files.
1754130,2018-03-14 17:50:24 UTC,"As KiCad do not have clearance matrix so I think maximum clearance on each row/net should be used or global clearance, whichever is higher."
1754130,2018-12-20 00:23:06 UTC,"@Wayne, @Seth,"
1754143,2018-03-13 14:22:45 UTC,sla2 for 9.0-updates
1754143,2018-03-19 08:56:11 UTC,"Cannot reproduce, looks like this is a problem with ruby rexml library or ruby itself. Marking as incomplete until this issue is reproduced again. If so, then please provide output of
lstopo --no-caches --of xml"
1754143,2018-03-21 20:11:12 UTC,"This may be related to the following bug.
https://bugs.launchpad.net/fuel/+bug/1742886"
1754145,2020-04-27 04:17:26 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1754145,2020-04-27 04:17:25 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1754145,2018-03-18 11:58:43 UTC,it is also the same under XWayland
1754145,2018-03-07 20:19:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1754145,2020-02-26 07:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754150,2018-04-26 17:30:56 UTC,Just for the curious: http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/171062/testcases/1305/results has now an update.
1754150,2018-04-26 17:29:09 UTC,"Yes, after the 2nd or 3rd time that was displayed (screenshot). However, during the first boot from the ISO image on VirtualBox it showed just one(!) field, with the option/letters ""None"". That of course was not a -great- option to choose from at all."
1754150,2018-04-26 16:58:17 UTC,You don't see this?
1754150,2018-04-26 16:20:28 UTC,After some reboots/shut offs of the VirtualBox machine the OEM option is finally displayed. The reason for that is yet unknown.
1754150,2018-04-26 16:02:04 UTC,"The problem was confirmed and documented on iso.qa.ubuntu.com on 2018-04-26.
see: http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/171062/testcases/1305/results/"
1754150,2018-04-26 16:00:31 UTC,"Don't know what happened here, but this bug/issue (OEM installation test case doesn't follow screen sequence) is by no means INVALID."
1754150,2018-03-09 18:05:16 UTC,I'll leave it as invalid since the title is misleading.
1754150,2018-03-09 17:34:21 UTC,I believe that this report and report #1754072 are related.  The test hardware is circa 2009.
1754150,2018-03-09 17:23:55 UTC,There is nothing wrong with the OEM script when the system startup correctly detects the video hardware.
1754150,2018-03-09 16:58:55 UTC,Thanks for checking me.
1754150,2018-03-09 16:58:39 UTC,Your mp4 is not what I was seeing after I downloaded & installed from the above URL on 2018-03-07 i.e.
1754150,2018-03-09 08:10:27 UTC,Not sure that you followed the testcase correctly here - just re-checked it. Works fine for me. Vid included
1754150,2018-03-07 21:05:02 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754150,2018-03-07 19:58:19 UTC,Machine used:
1754150,2018-03-07 19:57:08 UTC,"The image I used was linked to from the OEM test case:
http://iso.qa.ubuntu.com/qatracker/milestones/387/builds/167649/downloads"
1754150,2018-03-09 17:13:51 UTC,"@texadactyl - the image I used is the one you used. One of those things, thanks for changing bug status."
1754156,2018-03-23 15:01:28 UTC,"I've found the answer to this and created a new question.
https://askubuntu.com/questions/1018580/"
1754156,2018-03-10 15:16:35 UTC,"Having the same problem, but I'm using xorg."
1754156,2018-03-07 20:39:06 UTC,"I meant lock icon in the top right, not left.  (Is there no editing button here)"
1754156,2018-03-07 20:43:34 UTC,Can someone delete comment #2 and this one - I found the edit button for the original - but I can't edit/delete the comment.
1754156,2018-03-10 15:15:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754164,2018-03-07 21:03:39 UTC,See attachment for osrfsys and gateway logs for a failed request.
1754164,2018-03-15 17:52:26 UTC,Streaming the API response seems to fix the issue:
1754164,2018-03-21 18:04:48 UTC,"Beware, changing an API from non-streaming to streaming changes how the client interacts with the call.  Any clients (e.g. Open-ILS/web/js/dojo/openils/CopyLocation.js) that call the API will need to be taught to expect a stream instead of a single array of things."
1754164,2018-03-27 16:34:16 UTC,"Thanks for reviewing, Bill. I should have known it wouldn't be so easy. :)"
1754170,2018-06-13 16:30:55 UTC,"Went through these over the past couple of days and here's how they stand now.  I will be attaching PR's for a few of the smaller items.  Corrections to filepaths, symlink instructions, etc. are outside my current skillset."
1754170,2018-06-13 18:52:56 UTC,"cataloging/marc_tag_table.adoc -- PR here, also includes location info & screenshots: https://github.com/evergreen-library-system/Evergreen/pull/57"
1754170,2018-06-13 19:02:51 UTC,"Thanks for looking into these, Andrea. Two quick comments:"
1754170,2018-06-13 19:37:34 UTC,Thanks for the feedback -- I removed the PR for root.adoc
1754191,2018-07-15 17:25:30 UTC,This looks like issue in mutter or respective window manager. No problem in Unity.
1754191,2018-07-14 17:43:24 UTC,I've got a similar problem with thunderbird and firefox. There is a black border when opening and resizing the frames.
1754191,2018-05-09 08:21:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754191,2018-08-08 15:37:22 UTC,@fossfreedom: is this still happening with the latest stable chromium update?
1754191,2018-03-08 09:04:20 UTC,"Just tested in a VM with the latest 18.04 budgie ISO, and I can't observe the problem. I can't get chromium to open with its window partially underneath the panel."
1754191,2018-03-08 00:04:54 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754191,2018-03-08 10:17:42 UTC,Olivier - very reliable - has happened over the last few days - possibly due to the updated graphics stack that has dropped in 18.04?
1754194,2020-09-28 12:01:43 UTC,Fix released in git-ubuntu version 1.0
1754198,2018-03-08 02:51:29 UTC,"- confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)
- the png export appears to work well at a reduced dpi of 96, for example."
1754198,2020-04-04 04:34:57 UTC,"No new progress, but as part of bug migration to Gitlab, closing this issue."
1754202,2018-03-08 00:58:22 UTC,"StacktraceTop:
 gtk_image_reset (image=0x0) at ../../../../gtk/gtkimage.c:1864
 gtk_image_clear (image=0x0) at ../../../../gtk/gtkimage.c:1909
 update_weather (self=0x556c508283c0) at ../src/views/gcal-year-view.c:2113
 g_closure_invoke (closure=0x556c50937b50, return_value=0x0, n_param_values=1, param_values=0x7fffdcadaf40, invocation_hint=0x7fffdcadaec0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x556c5045f960, detail=detail@entry=0, instance=instance@entry=0x556c50518040, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffdcadaf40) at ../../../../gobject/gsignal.c:3635"
1754202,2018-03-09 21:43:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754203,2018-04-19 21:03:15 UTC,This issue was fixed in the openstack/puppet-murano 13.0.0 release.
1754203,2018-03-29 00:13:00 UTC,This issue was fixed in the openstack/puppet-murano 12.4.0 release.
1754203,2018-03-26 20:39:49 UTC,"Reviewed:  https://reviews.mahara.org/8723
Committed: https://git.mahara.org/mahara/mahara/commit/90ead3447503a74103d1d0f3db94c50e757df96d
Submitter: Robert Lyon (<email address hidden>)
Branch:    18.04_STABLE"
1754203,2018-03-26 20:39:42 UTC,"Patch for ""18.04_STABLE"" branch: https://reviews.mahara.org/8723"
1754203,2018-03-26 20:39:34 UTC,"Reviewed:  https://reviews.mahara.org/8719
Committed: https://git.mahara.org/mahara/mahara/commit/7e3d2c0c6a9c5a153022406dd433856bbc629e7f
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1754203,2018-03-19 03:56:53 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554112"
1754203,2018-03-19 04:48:41 UTC,"Reviewed:  https://review.openstack.org/554112
Committed: https://git.openstack.org/cgit/openstack/puppet-murano/commit/?id=c16b6d88683b3b750a236361a5ffc32cc02632ca
Submitter: Zuul
Branch:    stable/queens"
1754203,2018-03-10 00:30:24 UTC,"Reviewed:  https://review.openstack.org/550654
Committed: https://git.openstack.org/cgit/openstack/puppet-murano/commit/?id=9ff14c13a9da11e61e6afd3183851c899811cb9a
Submitter: Zuul
Branch:    master"
1754203,2018-03-08 01:04:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550654"
1754203,2018-03-26 02:48:46 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/8719"
1754212,2018-12-25 07:04:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627229"
1754219,2019-11-28 12:29:08 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/696532"
1754219,2019-12-03 22:41:21 UTC,"Reviewed:  https://review.opendev.org/696532
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=7948fee7e25707904f81ccc8854a1f98265c8f0b
Submitter: Zuul
Branch:    master"
1754219,2019-11-26 23:55:04 UTC,"Reviewed:  https://review.opendev.org/692110
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=f94508d537432817619932074a5f98ea08d93055
Submitter: Zuul
Branch:    master"
1754219,2019-10-29 15:13:41 UTC,"@zhengyong - did you ever get around to write any patches for this? (If not, I'll pick this upp and fix this.)"
1754219,2019-10-30 01:45:41 UTC,"hello harald-jensas, I have not write any patches, you pick this up"
1754219,2019-10-30 11:40:41 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/692110"
1754226,2018-03-12 12:18:59 UTC,I think networking-sfc should provide the way to delete port even it belongs to port-pair-group.
1754226,2018-03-13 00:41:38 UTC,"That would break the consistency of the port pair. At the very least, if we need to prevent port deletion, it should return a proper BadRequest error to the user instead of an Internal Error"
1754226,2018-03-20 05:32:31 UTC,"Hi Ivar,"
1754232,2018-04-03 09:45:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754241,2018-03-08 06:04:50 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754247,2018-03-08 06:01:52 UTC,/dev errors:
1754247,2018-03-10 00:20:35 UTC,Just realised these may be separate issues. Maybe activating the logging reveals that wpa_supplicant is being called with option `--all` as the interface and that fails.
1754256,2018-03-26 18:53:33 UTC,This issue was fixed in the openstack/os-net-config 8.4.0 release.
1754256,2018-03-08 07:29:09 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550731"
1754256,2018-03-13 19:11:34 UTC,"Reviewed:  https://review.openstack.org/550731
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=193928916e1d831b4790026efd85c56c611297e8
Submitter: Zuul
Branch:    stable/queens"
1754260,2018-03-13 21:44:43 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.0 release.
1754260,2021-02-19 15:51:57 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1754260,2018-03-08 07:40:59 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/550735"
1754260,2018-03-13 19:11:25 UTC,"Reviewed:  https://review.openstack.org/550735
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b11e641f4a9e181be358cc44b5f516f955d72b57
Submitter: Zuul
Branch:    stable/queens"
1754270,2018-03-08 08:47:53 UTC,"Found a Debian bug about the same issue but with AFS instead of fscrypt:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846377"
1754270,2018-04-27 20:05:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754270,2018-10-23 19:56:25 UTC,"I tested the setup on Ubuntu 18.10 and it seems to work correctly with a couple of fixes, I have created a small guide here:"
1754274,2018-03-08 08:50:48 UTC,apt history
1754275,2018-03-08 08:53:48 UTC,Tests are constantly failing with network issues for ppc64el.
1754275,2018-03-08 09:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754284,2020-05-04 20:43:47 UTC,Relevant: https://extensions.gnome.org/extension/1873/disable-unredirect-fullscreen-windows/
1754284,2020-05-04 20:38:30 UTC,Workaround:
1754284,2020-03-18 02:13:18 UTC,"That's actually two bugs; this one and bug 1846398. If the tearing is an issue for you then try logging into ""Ubuntu on Wayland"" instead."
1754284,2020-03-17 17:28:05 UTC,"Same issue, visible in VLC, mpv Media Player and Google Chrome when in fullscreen mode. I'm using 150% fractional scaling, Ubuntu 19.10."
1754284,2020-02-05 06:29:12 UTC,Apparently it's also a bug in the Nvidia driver still.
1754284,2018-04-10 16:06:47 UTC,"In addition to Totem, Firefox also exhibits this with fullscreen HTML5 video. Here's a good test: https://www.youtube.com/watch?v=5xkNy9gfKOg"
1754284,2020-01-31 08:29:56 UTC,"I've moved some old tearing bugs in here since I now understand it's just a bug in the Xorg modesetting driver, which is the one that most machines use:"
1754284,2018-04-11 01:37:51 UTC,"Yes, this going to be a general problem with fullscreen windows in Xorg sessions."
1754284,2018-04-01 17:45:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754284,2020-02-05 06:25:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754286,2019-07-30 05:09:34 UTC,"mistral is slated for removal from tripleo deployment process, this enhancement does add value, close it."
1754289,2018-08-03 00:50:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754290,2018-03-24 17:43:11 UTC,":~$ synapse
[INFO 23:12:01.886280] [synapse-main:266] Starting up...
[INFO 23:12:01.953674] [synapse-main:208] Binding activation to
<Control>space
[INFO 23:12:01.990170] [view-base:251] Screen is composited.
[INFO 23:12:01.991055] [controller:57] Using xim input method.
[WARN 23:12:02.037771] [desktop-file-service:196] Unable to create AppInfo
for /usr/share/applications/kde4/ktelnetservice.desktop
[WARN 23:12:02.038047] [desktop-file-service:196] Unable to create AppInfo
for /usr/share/applications/kde4/kmailservice.desktop
[WARN 23:12:02.046495] [desktop-file-service:196] Unable to create AppInfo
for /usr/share/applications/itweb-settings.desktop
[WARN 23:12:02.055098] [desktop-file-service:72] GNOME-Flashback is not
understood
[WARN 23:12:02.055517] [desktop-file-service:72] GNOME-Flashback is not
understood
[WARN 23:12:02.060053] [desktop-file-service:196] Unable to get exec for
Evolution Data Server
[WARN 23:12:02.060300] [desktop-file-service:72] GNOME-Flashback is not
understood
[WARN 23:12:02.062188] [desktop-file-service:72] GNOME-Flashback is not
understood
[WARN 23:12:02.076001] [desktop-file-service:196] Unable to get exec for
Photos lens for Unity
[WARN 23:12:02.076726] [desktop-file-service:196] Key file contains key
'Terminal' which has a value that cannot be interpreted.
[WARN 23:12:02.078690] [desktop-file-service:72] GNOME-Flashback is not
understood
[WARN 23:12:02.079994] [desktop-file-service:196] Unable to create AppInfo
for /usr/share/applications/vim.desktop
[WARN 23:12:02.091559] [desktop-file-service:72] GNOME-Flashback is not
understood
[WARN 23:12:02.099236] [desktop-file-service:72] GNOME-Flashback is not
understood
[WARN 23:12:02.099460] [desktop-file-service:196] Unable to create AppInfo
for /usr/share/applications/pt6.desktop
[WARN 23:12:02.112643] [desktop-file-service:196] Unable to create AppInfo
for /home/tushar/.local/share/applications/__packettracer6.desktop
[WARN 23:12:02.113277] [desktop-file-service:196] Unable to create AppInfo
for /home/tushar/.local/share/applications/packettracer6.desktop
[INFO 23:12:02.128745] [gnome-session-plugin:158] org.gnome.SessionManager
is available
[WARN 23:12:02.144811] [ssh-plugin:114] /home/tushar/.ssh/config: Error
opening file: No such file or directory
[WARN 23:12:02.145459] [hybrid-search-plugin:184] Unable to parse
/home/tushar/.local/share/recently-used.xbel
Segmentation fault (core dumped)"
1754290,2018-03-19 09:43:12 UTC,"Can you start it from the commandline, and post the output?"
1754294,2020-10-29 18:50:54 UTC,"this is related to libssl1.0 (""libcurl3"") -> libssl1.1 (""libcurl4"") transition."
1754294,2018-10-04 03:09:38 UTC,"Here's what I did to ""solve"" it on 18.04"
1754294,2018-10-02 15:19:00 UTC,"use a ppa https://launchpad.net/~jonathonf/+archive/ubuntu/curl
pin curl to such ppa"
1754294,2018-10-01 11:41:55 UTC,Any solution to the problem will be highly appreciated at this point ~(;
1754294,2018-09-26 16:26:40 UTC,"And here's another one... I'm in Ubuntu 18.04, and Apache 2.4 and cURL can not be installed at the same time."
1754294,2018-09-16 22:51:45 UTC,"So it's September 2018. 18.04 was released in April 2018. And we still can't have ""curl"" and ""VirtualBox"" installed simultaneously? You have got to be freaking kidding me."
1754294,2018-09-05 12:44:34 UTC,As said in comment #3 I opened an issue #2944 on github. Here is the link https://github.com/curl/curl/issues/2944.
1754294,2018-09-05 12:35:07 UTC,"Can anyone from maintainers work on this bug, Please ? As said in comment #3, is there anyone who can at least point me on where to solve this issue. I know things get frustrating when maintainers get comments like #4. Now would you guys please let go and solve this bug. It will help folks like me. Thanks"
1754294,2018-10-09 10:01:35 UTC,Seriously is there anyone working on this bug?? Please help us by solving this bug. This is driving crazy to lots of people
1754294,2018-09-04 23:47:06 UTC,"mssql-server is another fallen one... depends on libcurl3, and force me to uninstall KiCAD, libcurl4, libcurl4-openssl-dev, cmake and curl...
How can a mess like this one make it to a LTS release...
And also #3 answer is just awful, how can you just wash your hands like that."
1754294,2018-08-04 12:19:33 UTC,Upgraded from 16.04 to 18.04.1 expecting stability. Now I can't have cmake and google earth installed simultaneously without tedious manual package patching at every update?!
1754294,2018-07-30 06:21:15 UTC,same with mongodborg - depends on libcurl3
1754294,2018-07-13 06:52:19 UTC,"Hi Mark,
The problem is a little more complex."
1754294,2018-07-13 06:30:01 UTC,Or can this be done.
1754294,2018-07-13 05:56:25 UTC,Can this not be done?
1754294,2018-07-09 19:07:05 UTC,Mysql Workbench is also affected and removed after updating to curl4 from curl3
1754294,2020-12-21 09:25:49 UTC,"@xnox,"
1754294,2018-08-10 11:05:30 UTC,Sharing some other details and help in case it can benefit anyone.
1754294,2018-07-08 23:45:02 UTC,+1 to #66
1754294,2018-10-16 10:56:44 UTC,"I´m having a problem with this issue too. I´m using a DEV-System on Ubuntu 18.04 with multiple installed PHP-versions (by ondrej) connected to Apache2 with FPM-modules. I cannot install ""php-curl (7.1)"" (by ondrej) because it depends on ""libcurl4"" ... and installing libcurl4 would result in deinstalling apache2 (and several other packages) which is dependent on libcurl3."
1754294,2018-10-19 10:14:39 UTC," Thanks for the solution :)
Tim"
1754294,2020-07-29 09:42:46 UTC,"I've removed all apt sources.list and added back from current version of Ubuntu which helped me to package by package upgrade it to current Ubuntu version of the package
I had same issues and they were in a system because some packages were from the previous version ( 16 ) which must be upgraded after OS upgrade to 18"
1754294,2019-12-19 21:03:05 UTC,"The specific package on which Shibboleth depends, and that in turn demands libcurl3,
is libxmltooling7, in case that helps."
1754294,2019-08-22 10:03:01 UTC,Thanks Petr. I'll snoop around and see if I can find the future roadmap for Shibboleth wrt libcurl3/4. I have this gut-feeling not everything is a-okay over there. We can't be the only ones getting hit ny this...
1754294,2019-08-22 08:33:35 UTC,"@adrianvg Despite the very poor planning and execution of the libcurl3/libcurl4 transition, the best solution is to get all the relevant packages updated to use libcurl4. I very much doubt the next LTS release will resolve this."
1754294,2019-08-22 08:10:42 UTC,"Dev issued me a ticket as he needed php7.0-curl on a server (using Shibd for user authentication) running Ubuntu 18.04 LTS, so I obliged.
Dependency libcurl4 was needed too, but had to stop there as the package shibboleth-sp2-common was to be removed. The shibboleth-sp2-common contains the shib daemon.
Some googling got me to https://depts.washington.edu/bitblog/2018/06/libcurl3-libcurl4-shibboleth-php-curl-ubuntu-18-04/ and of course here."
1754294,2019-05-05 12:44:09 UTC,"I tried installing 3 different libcurl3_7.52.1-5 flavours like gnut_ls, nss..etc and it still says libcurl3 not installed.what should i do?"
1754294,2019-04-02 14:23:42 UTC,"> None of the packages which you are having an issue with are ones from the official Ubuntu archive
"
1754294,2018-10-19 00:51:37 UTC,"for an Explanation of the problem, and a work around see:"
1754294,2019-02-04 18:52:57 UTC,"Just solved this issue on Debian 9.
After upgrade from previous version I had old sources.list. That was my issue.
Just set correct version of sources.list and ran sudo apt-get update && sudo apt-get upgrade
And after that I found that curl library now require libcurl3 instead of libcurl4. Maybe this can help someone..."
1754294,2019-01-28 20:54:19 UTC,Btw I made an alias to update my laptop taking care of some of the annoying stuff regarding this issue. Modify to fit your needs (:
1754294,2018-12-16 06:23:11 UTC,"I am also affected by this problem.
Made a workaround by downloading curl3 and passing it manually to anything that needs it. (Replace the original with a shell script that calls this.)
`LD_LIBRARY_PATH=$HOME/mylib/curl3:$LD_LIBRARY_PATH application_name`"
1754294,2018-12-15 14:10:11 UTC,"I have installed Ubuntu 18.04 because I thought it must already be stable. Then I had to find out that it is impossible to run node js 11 and mongodb 4 on the same system, just because node js 11 depends on libcurl4 and mongodb-org 4 depends on libcurl3, and they cannot coexist. Come on, this bug has been here for more than 6 months now! I don't have a choice but to select a different distribution. :-("
1754294,2018-11-26 19:04:28 UTC,AH HA!
1754294,2018-11-25 00:25:48 UTC,"@davek I'm not saying this bug isn't bad but virtualbox-5.2 and slack-desktop have been fixed a long time ago. virtualbox-5.2 depends on libcurl4 and slack-desktop even better on ""libcurl3 | libcurl4""."
1754294,2018-11-24 18:36:09 UTC,"So basically the state of this bug is we still need 2 systems:
* 1 with libcurl3 and everything that depends on it, like virtualbox and slack
* another with libcurl4 and everything that depends on it, like kicad"
1754294,2018-11-18 22:50:36 UTC,"I recently encountered this problem in 18.04 trying to play a game I recently purchased, Prime Mover.  Upon startup it immediately aborts with the error"
1754294,2019-02-04 11:33:03 UTC,Hellooooo Anyone from maintainers is this bug ever going to be fixed ? If not then atleast close this bug. It freaks me out to come here every week and only confirmed tag. Please do something about this.
1754294,2018-05-08 17:30:10 UTC,What a shame! In this situations I always remember Linus Torvalds words: never break user experience.
1754294,2018-07-08 23:52:59 UTC,"Geachte heer/mevrouw,"
1754294,2018-05-07 11:17:27 UTC,">None of the packages which you are having an issue with are ones from the official Ubuntu archive, subsequently there is nothing we (the developers of Ubuntu) can do about this. You'll need to take up the issue with the people who develop these packages.
"
1754294,2018-03-12 12:40:25 UTC,"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 specifying a dependency on libcurl3, in fact they did depend on libcurl.so.4 which should no problem to be provided by the new libcurl4."
1754294,2018-03-12 12:05:40 UTC,"My all problematic applications use libcurl.so.4 from libcurl3 and none of which does not use libcurl.so.3, I do not understand how symlink to unused library will solve this problem?"
1754294,2018-03-12 11:44:53 UTC,"Yes, but, it are symlinks that could trivially be changed:"
1754294,2018-03-12 11:41:19 UTC,"igor@mcmcc-GL553VE:~$ ldd /usr/lib/x86_64-linux-gnu/opera/opera | grep libcurl
        libcurl.so.4 => /usr/lib/x86_64-linux-gnu/libcurl.so.4 (0x00007f5e8cb3c000)"
1754294,2018-03-12 11:33:25 UTC,"The problem is that, in libcurl3 used libcurl.so.4, and not libcurl.so.3..."
1754294,2018-03-12 11:07:57 UTC,"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."
1754294,2018-03-11 07:08:39 UTC,"I don't understand the conflict between libcurl3 and libcurl4 too, why can't they coexist?
Still wondering how to handle that while keeping opera."
1754294,2018-03-12 17:59:42 UTC,"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 :-/"
1754294,2018-03-11 03:47:41 UTC,I have the same problem with Kopano packeges and php 7.0.
1754294,2018-03-10 10:29:23 UTC,"The libcurl4 package was not showing up for me in Ubuntu Package Search and a few minutes ago it appeared!
What I can suggest is a workaround that applies to users of Ubuntu Bionic Beaver that is still in beta.
Download the files libcurl3_7.58.0-2ubuntu2_amd64.deb and libcurl4_7.58.0-2ubuntu2_amd64.deb.
Unpack the contents of each one at a time into a folder and modify the control file in the DEBIAN folder by removing the constraint in the conflict and replace fields.
Repackage the files and install them with dpkg with the --force-all option as they modify some common files.
Take a hold on these packages with apt-mark and dpkg selections.
I gave the following commands to hold:
sudo apt-mark hold libcurl3 libcurl4
echo ""libcurl3 hold"" | sudo dpkg --set-selections
echo ""libcurl4 hold"" | sudo dpkg --set-selections"
1754294,2018-03-10 08:35:14 UTC,When trying to solve the dependence with libcurl3 there is a problem with the removal of official Ubuntu packages...
1754294,2018-03-10 06:55:40 UTC,"1007/5000
Truth?
I mean that a library like libcurl4 that is not available separately as it does with libcurl3 and that is threaded down the user forcing the removal of lbcurl3 and all related applications being that you are the developers and not your problem?
Are you Microsoft employees by any chance?
Because it's looking alike.
The same arrogant attitude of fucking the customer that I do what I want and he'll have to swallow me.
The problem is in curl that forces this break and jeopardizes the whole system.
I even understand using a new library with new functions, leaner and so on, but do you need to screw with the whole system or with other applications?
I'm going to have a chat with the Debian people to do the same thing and make Ubuntu impractical and give the same excuse.
Then we will see if you are developers or are like Bill Gates, thief of ideas of others, putting their own name and blaming the mistakes on others."
1754294,2018-03-09 20:58:49 UTC,"None of the packages which you are having an issue with are ones from the official Ubuntu archive, subsequently there is nothing we (the developers of Ubuntu) can do about this. You'll need to take up the issue with the people who develop these packages."
1754294,2018-03-08 16:30:12 UTC,"uname -m && uname -r && cat /etc/*release
x86_64
4.15.0-10-generic
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic"
1754294,2018-03-08 16:25:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754294,2018-05-08 08:04:41 UTC,"Can't canonical turn libcurl3 into a transitional package for libcurl4? When I did so manually I got stuff to work fine. Most 3rd party binaries use dot target libcurl3 as there was no libcurl4 package when in fact they'd work fine against libcurl4 since the ABI did nto change between curl 3 and 4, only the headers got changed. Please have this fixed. An LTS should be reliable in every aspect including the fact that it should not break installs."
1754294,2018-03-10 11:20:28 UTC,"I manually edited file /var/lib/dpkg/status, it replaced libсurl3 (>= 7.16.2) to libcurl4 (>= 7.16.2) and libcurl3 to libcurl4, in those places where there is no version checking. Almost all the packages that require libcurl3 work without problems, except for the virtualbox, for it we had to take libcurl.so.4 from the libcurl3 package and put it in the /usr/lib/virtualbox directory..."
1754294,2018-03-13 04:27:50 UTC,"FWIW, I got opera-stable and viber to install with libcurl4 by extracting their debs, manually editing their control file to say libcurl3|libcurl4, recreating the deb using the ""ar -r"" command, and then using dpkg -i to reinstall. They run fine but of course I haven't been able to test all their functionality."
1754294,2018-03-13 02:40:28 UTC,@Brian Murray: I think that it is incorrect to mark this bug as invalid - at the very least it should be kept as confirmed against the 18.04 release notes so they can include a warning against upgrading to Ubuntu 18.04 because it may not be compatible with a number of popular third-party applications.
1754294,2018-03-13 14:19:40 UTC,"For spotify this trick doesn't work, it complains about the changed CURLOPT_SSL_CTX_FUNCTION symbol when starting the application."
1754294,2018-05-06 17:53:26 UTC,I'm re-posting this comment I made on the ngemu forums as it is related.
1754294,2018-05-05 09:10:00 UTC,slimjet is another victim
1754294,2018-05-03 15:26:11 UTC,My workaround for slack-desktop was to install using snap:
1754294,2018-04-29 23:29:54 UTC,"Another solution for this problem is downloading sources for libcurl4 package (apt-get source libcurl4), modifying ""control"" file by adding ""Provides: libcurl3 (= ${binary:Version})"" to libcurl4 section and rebuilding the package. It may also be necessary to add the new version to ""changelog"", in my case apt couldn't install the new deb right.
After that, everything mostly works well, except some apps (like virtualbox-5.2), which complain like ""version `CURL_OPENSSL_3' not found"", but for virtualbox-5.2 it is solved by installing the package virtualbox."
1754294,2018-04-28 19:57:00 UTC,I do not understand how this did not hold up the release of Ubuntu 18.04.  Many apps now conflict because of this issue.
1754294,2018-04-28 19:30:43 UTC,"I have the same problem with Slack 3.1.1, R (r-core-base) and curl. Either I have installed curl and r-core-base or Slack (also there were problems with Spotify). If I install Slack which depends on libcurl3 then I have to remove curl and r-core-base. Very annoying."
1754294,2018-04-28 05:24:18 UTC,"This also creates a conflict with r-core-base. I can have curl installed or R installed, but not both at the same time. Ubuntu 18.04."
1754294,2018-03-13 14:11:00 UTC,@Rocko method worked for slack-desktop 3.1 too. Installed without issues after dependency edited on control and remade .deb
1754294,2018-04-25 16:25:09 UTC,@djaler1 I was able to use the method detailed by @timdepauw to get both Slack and Insomnia working - for Insomnia I just grabbed the raw deb from here
1754294,2018-04-26 06:02:14 UTC,"Insomnia now can work without libcurl as dependency. It now statically
linked"
1754294,2018-04-19 19:40:53 UTC,This is causing havoc! People installing .NET Core which depends on libcurl3 cannot install cmake that is depending on libcurl4. The nomenclature of these packages implies that they should be installable side by side.
1754294,2018-03-28 16:02:40 UTC,"This method doesn't work with Insomnia, for example"
1754294,2018-03-28 13:14:41 UTC,Confirming that this seems to fix slack-desktop for now:
1754294,2018-03-25 22:04:10 UTC,This is a very big problem.
1754294,2018-03-17 12:12:43 UTC,"I installed Slack ignoring the dependency and works:
dpkg --ignore-depends libcurl3 -i slack-desktop-3.1.0-amd64.deb"
1754294,2018-03-15 11:18:57 UTC,"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"
1754294,2018-03-15 05:22:19 UTC,@Maarten: Maybe spotify will install and work from its flatpak? It's the second flatpak app listed here: https://www.omgubuntu.co.uk/2017/07/7-flatpak-apps-can-install-right-now-flathub
1754294,2018-04-21 12:32:28 UTC,I agree with @borgdylan. I'm thinking of leaving Ubuntu just for this reason. Too much time without this problem being fixed.
1754296,2018-07-13 14:47:56 UTC,"The commit (patch) that fixes it, is here:
https://cgit.freedesktop.org/xorg/xserver/commit/?id=1326ee0bc5eb858c3c00847b3ba65134e4ca2e2d"
1754296,2018-07-08 19:44:49 UTC,Quick way to reproduce using Xvfb on Bionic:
1754296,2018-07-08 19:39:55 UTC,Fixed upstream according to https://bugs.freedesktop.org/show_bug.cgi?id=104993 (different upstream bug id than mentioned in the comment above)
1754296,2018-06-25 11:35:00 UTC,"Similar report in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891287
and the upstream issue report at Freedesktop Xorg upstream: https://bugs.freedesktop.org/show_bug.cgi?id=105570 (where the breaking commits are identified!)."
1754296,2018-06-06 14:10:11 UTC,"We do have an Intel graphics card, but we just use the ""modesetting"" driver."
1754296,2018-03-10 06:46:43 UTC,I suspect libglx0 (transition from libgl1-mesa-glx to libglx0)
1754296,2018-03-11 05:43:52 UTC,"Maybe this is i915/i965 intel driver related. If someone with an in intel IGP could reproduce this. I have xserver-xorg-video-intel installed by the way. With not mentioning ""intel"" explicitly as the driver in xorg.conf doesn't it automatically uses modesetting or glamorgl?"
1754296,2018-03-08 10:56:20 UTC,"tried with ""strace startx"""
1754296,2018-06-06 13:23:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754296,2018-03-11 05:38:15 UTC,"Just had the idea to unload ""glx"" and see if I can Disable Composite without crashing Xorg / startx / xinit."
1754296,2018-03-08 11:08:28 UTC,"Now I remove +s bit from /usr/bin/X, /usr/bin/xinit, /usr/bin/startx, /usr/bin/Xorg and tried to run Valgrind with it. Honestly I have no idea about debugging. I just know that valgrind and strace can be somehow use for it. Hope this helps!"
1754299,2018-03-08 11:03:56 UTC,"Incomplete will auto-expire which I don't want in this case, so I'll use Confirmed. But please note that the bug unfortunately make progress without further information such as steps to reproduce - so it is still effectively Incomplete."
1754299,2018-03-08 11:19:14 UTC,But please note that the bug unfortunately *won't* make progress
1754304,2019-09-19 11:57:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1754306,2018-05-19 16:40:06 UTC,"workaround found!
Problem is only on old PIs like Model A. work perfekt on zero W and pi3."
1754306,2018-03-19 15:59:03 UTC,"Work around for me, use 2017-07-05-raspbian-jessie-lite.zip install asterisk and then upgrade to stretch"
1754306,2018-03-19 20:36:20 UTC,Sorry. There is no Workaround!!!
1754306,2018-03-14 09:38:51 UTC,"Hallo, today i tryed the new current raspian image 2018-03-13 lite. Same problem:"
1754306,2018-03-14 12:37:32 UTC,"Same problem with the full image 2018-03-13:
Setting up asterisk (1:13.14.1~dfsg-2+deb9u3) ...
Adding system user for Asterisk
Adding user `asterisk' to group `dialout' ...
Adding user asterisk to group dialout
Done.
Adding user `asterisk' to group `audio' ...
Adding user asterisk to group audio
Done.
Created symlink /etc/systemd/system/multi-user.target.wants/asterisk.service → /lib/systemd/system/asterisk.service.
Job for asterisk.service failed because a timeout was exceeded.
See ""systemctl status asterisk.service"" and ""journalctl -xe"" for details.
invoke-rc.d: initscript asterisk, action ""start"" failed.
● asterisk.service - Asterisk PBX
   Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: timeout) since Wed 2018-03-14 12:37:04 UTC; 204ms ago
     Docs: man:asterisk(8)
  Process: 2268 ExecStart=/usr/sbin/asterisk -g -f -U asterisk (code=killed, signal=KILL)
 Main PID: 2268 (code=killed, signal=KILL)"
1754309,2019-04-04 03:36:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1754309,2019-06-03 04:17:31 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1754317,2018-03-09 06:47:22 UTC,"Change abandoned by weikeyou (<email address hidden>) on branch: master
Review: https://review.openstack.org/551046"
1754321,2018-03-08 14:43:17 UTC,"I wonder if chromium-browser should explicitly depend on libsecret, to enable support for it. It's currently not built-in."
1754321,2019-12-28 11:26:37 UTC,"+1, it would be nice because I don't want to use a snap version of Chromium on Ubuntu 19.10 and 20.04 and try to rebuild Chromium from Bionic in eoan and focal in ppa:mikhailnov/utils, I will try to build libgnome-keyring to avoid changing chromium-browser packaging manually for now."
1754321,2019-12-28 12:19:12 UTC,From source code of Chromium:
1754325,2018-04-03 13:10:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754325,2018-03-08 15:15:43 UTC,"StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x1) at ../../../../gobject/gtype.c:4129
 g_signal_handlers_disconnect_matched (instance=0x1, mask=mask@entry=(G_SIGNAL_MATCH_FUNC | G_SIGNAL_MATCH_DATA), signal_id=signal_id@entry=0, detail=detail@entry=0, closure=closure@entry=0x0, func=func@entry=0x560d18f922b0 <gs_details_page_notify_state_changed_cb>, data=0x560d1ab3ea10) at ../../../../gobject/gsignal.c:2931
 set_app (self=self@entry=0x560d1ab3ea10, app=0x7f47241e4980) at ../src/gs-details-page.c:1632
 gs_details_page_url_to_app_cb (source=<optimized out>, res=<optimized out>, user_data=0x560d1abac6e0) at ../src/gs-details-page.c:1756
 g_task_return_now (task=0x7f4748146e20) at ../../../../gio/gtask.c:1148"
1754326,2018-03-08 16:21:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1754328,2018-03-08 16:21:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1754328,2018-03-08 17:25:14 UTC,"The bug is against the Ubuntu installer. I don't know what is the package of this component and I cannot get a console (I'e tried all tty's but no luck). Given that installation issues are quite common, I would expect you to link bugs against 'components' instead of 'source packages'."
1754328,2018-03-08 17:51:55 UTC,"Thanks @paulw2u for linking the source package. I've never heard of Ubiquity before, so I also learned something new today :D https://wiki.ubuntu.com/Ubiquity"
1754330,2018-03-22 23:21:52 UTC,"Anything on the serial console? Take the SD card out and put it into your computer, edit config.txt and put ""enable_uart=1"" at the end if you haven't yet done so.
If you get a normal login prompt at the serial console, take the SD out again and edit cmdline.txt, put ""s"" at the end of the existing line of kernel options (add a space and the single character s).
Then the Pi should boot into single-user mode, where you can change the password on the serial console via raspi-config or passwd pi, whichever one you prefer. When you're done changing the password, delete the ""s"" from /boot/cmdline.txt (this can be done on the console while still in single-user mode) and then reboot."
1754330,2020-02-16 09:55:52 UTC,"Is this still an issue? Otherwise, please close this bug."
1754331,2018-03-08 13:57:50 UTC,Circular dependencies are possible. And it's definitely not a bug in dh-autoreconf. Leaving it up to folks with KDE knowledge to see if they want to change that or not.
1754332,2018-03-16 22:20:29 UTC,This bug was fixed in the package livecd-rootfs - 2.511
1754332,2018-03-16 18:36:36 UTC,Bah:
1754332,2018-03-16 18:31:25 UTC,"I've tried to reproduce this, and failed..."
1754335,2018-04-11 00:50:24 UTC,Closing as this doesn't seem to be an issue any more.
1754335,2019-09-19 11:57:34 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1754339,2018-03-08 14:09:19 UTC,This is a huge problem for netplan with default networkd backend.
1754340,2018-03-08 17:52:06 UTC,"I can't reproduce this. Can you please fully update your system and try again? If that doesn't help, please post the full output of `apt show speedcrunch libqt5core5a`."
1754345,2020-06-16 14:17:41 UTC,I found the solution accidentally:
1754345,2020-08-29 20:09:52 UTC,"Thanks for this Farab, your solution worked for me."
1754345,2019-08-20 19:44:35 UTC,"I have machine in this state now
It does not refresh any snaps or install any new ones
interestingly, when I deleted .snap/auth.json if fixed things half way
now I can install new snap (ubuntu-image), refresh snapcraft snap
but refreshing core and core18 returns again (invalid credentials)
snap version 2.39.3
Ubuntu 18.04.2
What I noticed when I try to refresh, I get pop up window with password request"
1754345,2019-01-11 12:21:22 UTC,Reinstalling broken snap also helps. In my case:
1754345,2020-05-19 06:18:48 UTC,"To replicate this issue, make sure you had at least one update available for one of your snap package, then go to the Ubuntu.com and change your Ubuntu user password! Head back to the terminal and type ""snap refresh"". You get ""invalid credentials"" error for any packages that you had installed before the password change. Also all feature updates for packages you had before changing your password give you the same error.
Unfortunately, the only way to fix it for me was to remove all snap package and reinstall it again.
Also, snap logout and snap login after password change does not change anything. You still get ""invalid credentials"" for all the feature packages updates you had installed before changing your Ubuntu password.
Also, your removing /var/lib/snapd/state.json give you false ""All snaps up to date."""
1754345,2018-11-28 13:17:59 UTC,"Stopping snapd, removing /var/lib/snapd/state.json and restarting snapd did fix the issue - of course at the cost of losing snapd state. https://forum.snapcraft.io/t/handling-invalid-credentials-password-change-blocking-macaroon-refresh/2526/4 seems relevant"
1754345,2018-11-28 13:00:28 UTC,"While I have no idea how I got to this state, I'm having the same problem. The ~/snap/.auth.json file is not broken, and snap logout/login does nothing to help (even though login proceeds successfully). Additionally, I keep having problems logging into Ubuntu One which only seems to be (temporarily) solved by resetting password, so maybe it's possible there's some problem with the server-side state of the account?"
1754345,2018-11-23 11:44:06 UTC,"I cannot provoke any such error (by deliberately breaking my macaroon, or even removing it). Unclear how to reporduce, given that this bug is old it's quite possible the problem was fixed or was a temporary issue with the store. Closing on that basis."
1754345,2018-11-28 15:03:08 UTC,"Konrad, did you keep a copy of the old state.json?"
1754350,2018-05-30 15:24:22 UTC,I suggest nano - it's easier for users and smaller than vim
1754350,2018-11-06 19:40:41 UTC,snap install nano-editor?
1754350,2020-06-04 17:07:51 UTC,Added livecd-rootfs to comment on the requested change and marking cloud-images task invalid.
1754350,2020-06-04 17:13:05 UTC,I've opened a track for livecd-rootfs where the minimal image is defined and I'm going to close the cloud-images portion.
1754360,2018-10-08 21:49:06 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1754360,2018-10-02 20:43:51 UTC,"Reviewed:  https://review.openstack.org/605884
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1535d42ea14503db63d34ac47dc8ae231e0edf59
Submitter: Zuul
Branch:    stable/ocata"
1754360,2018-10-02 00:14:27 UTC,"Reviewed:  https://review.openstack.org/581454
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1487ea7abb974650d5658b29e52e0b0603751556
Submitter: Zuul
Branch:    stable/pike"
1754360,2018-09-27 23:25:58 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/605884"
1754360,2018-09-24 14:47:19 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1754360,2018-10-08 21:45:44 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1754360,2018-07-30 16:08:20 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1754360,2018-07-11 01:34:26 UTC,"Reviewed:  https://review.openstack.org/550865
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1e77faaa412ab9909dd9491cab4a819b5c84d3e8
Submitter: Zuul
Branch:    master"
1754360,2018-07-10 19:09:59 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/581454"
1754360,2018-07-10 18:56:23 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/581451"
1754360,2018-03-08 15:16:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/550865"
1754360,2018-07-31 18:53:12 UTC,"Reviewed:  https://review.openstack.org/581451
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bcae081c4672a13eb1a75d1d3d81a439b5fdb796
Submitter: Zuul
Branch:    stable/queens"
1754364,2018-03-08 15:37:19 UTC,"Note: we have the list of available timezones in JS via moment.tz.names(), which returns an array of known, valid timezone names."
1754364,2019-02-20 22:36:07 UTC,"I'm adding documentation tags, since we should at least give people a clue of the input format in the setting name or description, and the docs. (I found myself guessing at ""EST"", or ""-5:00""...)."
1754364,2019-02-27 22:42:51 UTC,I've opened a new bug for the documentation aspects of this:
1754366,2018-03-12 16:08:11 UTC,Hi! The neutron error can be ignored (deploy with networking-baremetal to avoid it). Your actual problem is: Error starting iSCSI target: Failed to publish a target: Could not create NetworkPortal in configFS. Could you please fetch deploy ramdisk logs? IIRC they are stored in /var/log/ironic/deploy by default.
1754366,2018-03-20 09:49:34 UTC,"Hi, Dmitry"
1754386,2019-05-16 13:38:31 UTC,"Reviewed:  https://review.opendev.org/659358
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=6cbddde02ed413015c9fb70da6e421ff4fa999da
Submitter: Zuul
Branch:    master"
1754386,2019-05-15 18:36:21 UTC,"Change abandoned by Marcelo Subtil Marcal (<email address hidden>) on branch: master
Review: https://review.opendev.org/657867
Reason: https://review.opendev.org/#/c/659358/"
1754386,2018-03-15 14:45:11 UTC,This is a bit tricky - this configuration option has context in older openstack releases where the port security extension did not exist; I think we should leave the configuration option in but drop the log message - its complete foobar.
1754386,2019-05-13 14:24:12 UTC,https://review.opendev.org/#/c/657867/
1754386,2019-05-15 18:27:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659358"
1754387,2020-01-28 19:31:11 UTC,"My mistake - it lets you upload more than a hundred to pending and page through them, but it will still only transfer the ones you have marked to the bucket, and the rest disappear off the pending screen."
1754387,2020-07-22 17:50:20 UTC,"Pushed to master, rel_3_5, and rel_3_4. Thanks, Josh and Gina!"
1754387,2020-02-20 16:14:25 UTC,"I, Gina Monti, have tested this code during the Feedback Fest and consenting to sign off.  Email: <email address hidden>."
1754387,2020-02-03 19:55:59 UTC,Here is a branch that makes the following changes.
1754387,2020-02-03 19:00:30 UTC,"I retract what I said in comment 15, the file load feature is quite efficient, it sends all the barcodes in one query.  That is why the order of the barcodes in the loaded file gets lost, or at least part of the reason.  Postgres returns the results in no particular order.  Then the grid sorts them by user id."
1754387,2020-01-28 22:09:58 UTC,"Another issue is that loading 5K users by barcode places a high load on the server.  The item status file loader is setup to load serially because of this same issue I believe, I think that would be a good change for loading users also."
1754387,2020-01-28 20:41:44 UTC,"We just ran into this, a co-worker was trying to batch edit the 5000 users that had accounts that expired in 2016, and was going to load them into a user bucket and batch edit them.  But since only 100 can be moved to a bucket at a time, it doesn't seem possible to use the user buckets like that."
1754387,2019-11-18 18:39:42 UTC,This bug is resolved after applying the fix for https://bugs.launchpad.net/evergreen/+bug/1749970
1754387,2019-11-18 18:13:35 UTC,"Yes, Terran. Thanks, I posted it to the wrong bug. Please ignore my post;)"
1754387,2018-03-08 16:48:21 UTC,I suspect this has the same underlying cause as this other pending user bucket bug: https://bugs.launchpad.net/evergreen/+bug/1749970
1754387,2019-11-18 17:54:17 UTC,"Jennifer, if you apply the patch for https://bugs.launchpad.net/evergreen/+bug/1749970 does it resolve this issue?"
1754387,2019-03-28 17:30:10 UTC,SPARK/PaILS is running 3.1.10 and we are still experiencing this issue.
1754387,2018-10-30 21:04:36 UTC,I've confirmed that this is still an issue in 3.1.6
1754387,2018-05-30 16:30:17 UTC,"Also related - I tried importing a CSV file of 734 patrons into a pending user bucket and it only imported 122 of them. (And confirmed when I tried transferring those 122 to a bucket, it only transferred 100 of them and the other 22 disappeared.)"
1754387,2018-04-12 00:07:10 UTC,I can confirm the behavior Anna sees in version 3.0.5.
1754387,2018-03-08 18:22:10 UTC,"Sorry, I saw ""Pending Users"" and thought ""Pending Patrons"" - never mind!"
1754387,2018-03-08 17:57:49 UTC,I thought that bug was for Pending Patrons not the User Bucket interface. Does Pending Patrons use User Buckets as a frame?
1754387,2019-11-18 18:12:07 UTC,"Oops, sorry about that! I must have posted on the wrong bug. I meant to
find the one about the different wording used for Patron Buckets, which are
called User Buckets on the Circ Drop Down Menu. That might be an issue with
our documentation, though, so back to the drawing board."
1754390,2018-04-26 00:54:54 UTC,I would strongly recommend updating to CFITSIO 3.44 which patched a several more issues. Though 3.45 which should be released in the next two weeks will also contain an annoying bug fix.
1754390,2018-03-19 20:23:42 UTC,"Thanks Achim, the sync has been requested; it's after feature freeze date, so the release team may decide to hold it up, but the upstream changelog looked encouragingly like bugfixes-only to me: https://heasarc.gsfc.nasa.gov/FTP/software/fitsio/c/docs/changes2.txt"
1754390,2018-03-19 15:39:25 UTC,"Debian sid contains the fixed cfitsio version, can someone trigger a sync to bionic?"
1754390,2018-03-15 01:43:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1754393,2018-03-09 11:47:51 UTC,"Just found out this is a problem with Wayland.
When running on Xorg display manager, this works fine."
1754394,2018-03-08 17:23:13 UTC,"Well, I'll be absolutely damned."
1754394,2018-03-08 16:13:44 UTC,Also I'm observing the same thing when opening photos (eg the screenshots above) with Gnome Image Viewer 3.26.
1754394,2018-03-09 10:04:56 UTC,"Per OP comment, this isn't chromium-specific (gnome image viewer also affected).
Re-targetting the bug at unity."
1754397,2018-03-15 14:48:12 UTC,"Maybe the right thing todo is to disable unattended upgrades once a new origin is configured, and then re-enable them after the packages have actually been upgraded?  This would avoid an out-of-charm control upgrade by the daily cronjob."
1754397,2018-03-08 16:22:24 UTC,I've added the charms that are typically smooshed in the same machine.
1754400,2018-05-29 15:25:56 UTC,(maybe) relevant bug: https://bugs.documentfoundation.org/show_bug.cgi?id=101630
1754400,2018-05-29 15:22:15 UTC,"After allowing less secure apps in my google account security settings (https://myaccount.google.com/security#connectedapps), I was able to save a writer document on my google drive by only providing e-mail address and password."
1754400,2018-05-24 15:08:02 UTC,"Just tested again with libreoffice 6.0.3 in bionic, after we explicitly enabled the google drive API for the project that holds the API key used in libreoffice (it was not enabled previously)."
1754400,2018-03-09 09:30:40 UTC,"Just tested the 6.0.2 snap (from the candidate channel), and I'm seeing a different behaviour: no error, but I get prompted a 6-digit PIN code, as if 2FA was enabled for my test google account (which it isn't)."
1754400,2018-03-09 09:42:41 UTC,"gdrive-client-id and gdrive-client-secret differ between the deb packages and the snap. I wonder if the tokens were updated/renewed, but we forgot to update the deb packages."
1754400,2018-03-14 06:33:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754401,2018-03-13 17:28:29 UTC,"Finally found what changed. I updated /etc/fstab to have /proc mounted with hidepid=2,gid=sudo for added security. This works perfectly on 16.04 but totally breaks on 17.10."
1754401,2018-03-14 02:09:25 UTC,Thanks for the clarification.
1754401,2018-03-14 15:04:03 UTC,"Created attachment 138109
/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
1754401,2018-03-14 15:06:01 UTC,"I added a link to the upstream bug, thanks for the guidance Daniel."
1754401,2018-06-13 19:48:13 UTC,"Booting with hidepid=2 on a Fedora 28 machine, X starts with no problem. Presumably some other part of Ubuntu's setup is getting confused by this. It would be helpful if you could strace X startup to see why it doesn't think it can find the console."
1754401,2018-12-13 18:34:25 UTC,-- GitLab Migration Automatic Message --
1754416,2018-03-08 17:12:31 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/550954"
1754416,2018-03-09 04:20:39 UTC,"Reviewed:  https://review.openstack.org/550954
Committed: https://git.openstack.org/cgit/openstack/senlin-dashboard/commit/?id=e3692c3a1488798fd23ea3770b2425c33dbf9978
Submitter: Zuul
Branch:    stable/pike"
1754416,2018-03-09 04:21:59 UTC,"Reviewed:  https://review.openstack.org/550951
Committed: https://git.openstack.org/cgit/openstack/senlin-dashboard/commit/?id=03cde5d8b7805790e4476b8ef073d26e6cc2119c
Submitter: Zuul
Branch:    stable/queens"
1754416,2019-04-17 07:14:12 UTC,This issue was fixed in the openstack/senlin-dashboard 0.7.1 release.
1754421,2018-03-08 17:53:20 UTC,Hi - this isn't managed by the OpenStack Foundation. This should be elevated to the managers of groups.openstack.org/groups/san-francisco-bay-area.  mrmartin (Marton Kiss)
1754421,2020-02-28 14:58:41 UTC,We moved to a different Groups system.
1754428,2019-10-30 19:26:18 UTC,"Jason: No, we need a volunteer to fix this one."
1754428,2020-06-18 16:01:25 UTC,Additional comments http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-06-18-15.01.log.html
1754428,2019-10-24 14:55:24 UTC,"Do we have any updates on this defect, and milestone?"
1754428,2018-03-08 18:20:56 UTC,Manila Data service log
1754428,2018-03-08 18:20:32 UTC,Manila scheduler service log
1754428,2018-03-08 18:20:07 UTC,Manila share service log
1754428,2018-03-08 18:19:42 UTC,Manila API Log
1754438,2018-03-08 19:02:40 UTC,As of today - 782 tests fail when I set oslo_policy.enforce_scope = True in keystone's unit tests [0].
1754438,2018-09-25 02:23:04 UTC,Hi Sonu
1754440,2020-08-04 17:01:26 UTC,I can confirm this in Pinta latest Ubuntu PPA 1.7+r1134-202008032046~ubuntu18.04.1 following bug report steps. I get the following error:
1754440,2020-08-04 20:17:49 UTC,I suspect the issue is caused by the selection having zero area after the selection is inverted.
1754455,2018-03-29 16:35:23 UTC,"OK. I expected to find them under Administration or Cataloging. I'll update them with my additions and put them in one of those two places. Guess I'll check the docs to see where marc_export goes in the regular documentation, if it appears there at all."
1754455,2018-03-29 16:25:12 UTC,"There are release notes:
docs/RELEASE_NOTES_NEXT/marc_export_strip.adoc"
1754455,2018-03-29 14:47:11 UTC,"I'm testing this with some export that I will need to do in May, and it occurred to me that an additional feature that would be nice to have, that this branch does not provide, would be to delete tags from the output based on subfield values. My main use case would be to delete 856 tags where the subfield 9 is not for one of the libraries whose records I am exporting."
1754455,2018-03-16 17:25:28 UTC,"Here is a branch that supports regular expressions.  Thanks for the suggestion, Mike!"
1754455,2018-03-09 17:37:26 UTC,"For safekeeping, I have created a branch that supports this basic functionality.  No Pullrequest."
1754455,2018-07-06 15:15:09 UTC,"I'm not working on this at the moment. Most of the reason for our need has passed. I do intend to revisit this later, which might very well be never."
1754455,2018-03-09 16:28:19 UTC,"We have been asked specifically if it is possible to remove the subfield 0 from all tags when doing exports. So, we started a branch that adds a command line option to marc_export that can be use to remove the subfield zero from all tags. We want to share that with the community, since others might have a similar need."
1754455,2018-03-09 15:23:06 UTC,"I think one should tread lightly removing all instances of this subfield from a bib record on import or export since it may be essential to future linked data. I think it would be better to address problems with specific $0s rather than strip all $0s, whether correct or not. However, having the option to strip them out or not would allow for local control. A perfect world would be a way to identify the problem subfield for resolution, while leaving the remaining ones in place."
1754455,2018-03-09 14:43:29 UTC,"""That said, we could make the parenthetical check more robust, and
require the value in the record to match the configured value for the
Evergreen instance.*""*"
1754455,2018-03-08 20:41:12 UTC,I would argue that we are following the standard.  The format of our $0 is:
1754455,2018-03-09 16:35:35 UTC,"Number 1 in my previous comment got a little botched from my palm resting on my touchpad. I fixed most of the mess, but guess I missed that bit."
1754458,2018-09-26 22:49:51 UTC,"https://launchpad.net/~james-rogers-n fix, to insert dbus-launch worked for me."
1754458,2018-09-15 04:09:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754458,2018-09-13 00:11:40 UTC,idk
1754458,2018-08-20 09:51:51 UTC,Possible duplicate/related bug: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1728449
1754458,2018-08-20 09:39:33 UTC,I ran into this after an update from 16.04. I had a custom panel as well but I found a way to show the notification panel again without resetting the dconf configuration. I had three indicator-application.desktop files (and I IIRC likewise as many probably competing running instances of it):
1754458,2018-06-14 15:42:48 UTC,"Created a new account and works fine.
So after a little bit of digging, the only relevant difference was dconf."
1754458,2018-06-02 15:43:53 UTC,"The offered solution of changing the panel style did not persist after restart. The following has solved the problem for me, with the solution persisting across sessions/restarts."
1754458,2018-05-30 22:04:12 UTC,"Yes I found this bug too.  The bug arose after I did a clean full install of Mate 18.04LTS, but I re-used my old Mate 16.04 home partition. So it's probably confused by my old style configuration files which were imported from Mate16.04 to Mate 18.04."
1754458,2018-05-08 04:24:52 UTC,"I'm getting the same problem with Telegram and Steam, both packages were installed in the same way on both systems.
Indicator was visibile prior to upgrade, is not after upgrade, works in a clean install of bionic."
1754458,2018-05-08 13:22:33 UTC,"After installing a 18.04 that couldn't be fresher,
I added the applet  Indicator Applet Complete
and now I've got in a bunch:
that Network Manager applet that was missing (that of 16.04.4 was badly working after suspend)
a Battery applet that was missing too
a duplicate Sound applet
a Mixed applet (Monitor, Help, Settings, Lock/Switch, users, Log out…, Suspend…, Shutdown)"
1754458,2018-04-27 13:54:33 UTC,"Same problem here. I had nm-applet icon showing up just fine on 17.04. After upgrading to 17.10 it disappeared, but I was able to get it back by using MATE Tweak to revert to a saved panel layout. Now, after upgrading to 18.04, it disappeared again. I am still able to recover it by reverting to a saved panel layout, but now I have to do it every single time I restart my computer."
1754458,2018-04-17 12:49:38 UTC,"For me this was due to my panel no longer having an indicator applet. Adding it back did not work. I managed to ""fix"" it by resetting the panel config (right click on the panel, select 'Reset Panel')."
1754458,2018-04-14 13:41:50 UTC,"FYI: please don't run graphical programs with plain `sudo`, see https://askubuntu.com/a/270019/549800"
1754458,2018-03-25 00:15:45 UTC,"Hi,
This problem also affect other applications like shutter (it also appears if launched by root).
Thanks"
1754458,2018-03-19 00:31:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754458,2018-03-18 13:07:45 UTC,I experience the same problem.
1754458,2018-05-14 09:24:38 UTC,"Pär Lindfors (paran) wrote on 2018-04-17:
 I managed to ""fix"" it by resetting the panel config (right click on the panel, select 'Reset Panel')."
1754459,2019-09-03 02:04:36 UTC,"At least for the 2.x release sapi.pc isn't included, so dropping this bug against disco and eoan."
1754460,2018-03-09 07:49:47 UTC,You may need to run the following from a terminal:
1754460,2018-03-29 18:58:17 UTC,"THANKS for having helping me.
I did the process: sudo apt-get install-f and sudo apt-get clean and sudo apt -get update.
I had to do sudo apt autoremove to change the wrong packages and I started the updates again.
Eveything was ok but the linux-firmware 1.157.16 which failed to install properly.
I am sorry but the bug is still here. THANKS FOR YOUR HELP!"
1754460,2018-03-08 21:00:04 UTC,This change was made by a bot.
1754462,2020-12-27 05:56:50 UTC,This bug was fixed in the package flask-socketio - 5.0.1-1
1754464,2018-03-09 05:58:47 UTC,"Removing packages from bionic:
 ruby-autoparse 0.3.3-2 in bionic
  ruby-autoparse 0.3.3-2 in bionic amd64
  ruby-autoparse 0.3.3-2 in bionic arm64
  ruby-autoparse 0.3.3-2 in bionic armhf
  ruby-autoparse 0.3.3-2 in bionic i386
  ruby-autoparse 0.3.3-2 in bionic ppc64el
  ruby-autoparse 0.3.3-2 in bionic s390x
Comment: FTBFS with ruby2.5, removed from Debian testing; Debian bug #888146
2 packages successfully removed."
1754464,2018-03-15 16:01:07 UTC,ruby-filepath's dep8 tests hang (reproducible locally) and upstream mentions only ruby2.3 compatibility https://github.com/gioele/filepath
1754464,2018-03-16 20:19:02 UTC,"Removing packages from bionic:
 ruby-filepath 0.6-3 in bionic
  ruby-filepath 0.6-3 in bionic amd64
  ruby-filepath 0.6-3 in bionic arm64
  ruby-filepath 0.6-3 in bionic armhf
  ruby-filepath 0.6-3 in bionic i386
  ruby-filepath 0.6-3 in bionic ppc64el
  ruby-filepath 0.6-3 in bionic s390x
Comment: Broken with ruby2.5, removed from Debian testing; LP: #1754464, Debian bug #889278
1 package successfully removed."
1754477,2018-03-08 21:51:12 UTC,"StacktraceTop:
 memcpy (__len=<optimized out>, __src=<optimized out>, __dest=0x0) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
 gen8_render_init (ctx=<optimized out>) at gen8_render.c:1809
 i965_Init (ctx=0x7fe0b400b5e0) at i965_drv_video.c:6998
 __vaDriverInit_1_0 (ctx=0x7fe0b400b5e0) at i965_drv_video.c:7164
 va_openDriver (dpy=dpy@entry=0x7fe0b400b470, driver_name=driver_name@entry=0x7fe0b4022f70 ""i965"") at va.c:447"
1754484,2019-09-19 14:53:59 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1754484,2018-03-29 21:38:04 UTC,here is another example:
1754484,2018-03-29 22:12:05 UTC,"Jason,"
1754484,2018-03-29 22:15:49 UTC,"@Mike,"
1754484,2018-03-29 22:37:26 UTC,"Here is /e/n/i. BTW, This comment and #2 come from a maas 2.3.1 install - this is not a 2.4 specific issue."
1754484,2019-09-20 12:10:37 UTC,"MAAS uses network probing to determine which interfaces are on which fabrics. Being that the other 3 interfaces are not configured MAAS has no way to determine that they are similar. Saying ""It seems exceedingly unlikely that a single rack controller would have interfaces in multiple fabrics and this doesn't make sense as a default assumption."" is really based on your experience and others can have different experiences where this is true."
1754484,2020-10-21 16:38:15 UTC,"I still disagree here. MAAS can just assume that interfaces on the same rack controller are on the same fabric, and that will be true 99% of the time. That's good enough to make it default behavior, and if people really do have interfaces on different fabrics, they can correct that afterwards."
1754486,2018-05-24 23:18:19 UTC,apport information
1754486,2018-05-24 23:18:21 UTC,apport information
1754486,2018-05-24 23:18:22 UTC,apport information
1754486,2018-05-24 23:18:15 UTC,apport information
1754486,2018-05-24 23:18:24 UTC,apport information
1754486,2018-05-24 23:18:26 UTC,apport information
1754486,2018-05-24 23:18:23 UTC,apport information
1754486,2018-05-24 23:18:18 UTC,apport information
1754486,2018-05-24 23:18:12 UTC,apport information
1754486,2018-05-24 23:18:16 UTC,apport information
1754486,2018-05-24 23:18:14 UTC,apport information
1754486,2018-05-24 23:18:13 UTC,apport information
1754486,2018-05-24 23:18:11 UTC,apport information
1754486,2018-05-24 23:18:10 UTC,apport information
1754486,2018-05-11 15:36:17 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754486,2018-05-24 23:18:17 UTC,apport information
1754492,2018-03-09 17:10:32 UTC,apport information
1754492,2018-03-09 17:10:29 UTC,apport information
1754492,2018-03-09 17:10:30 UTC,apport information
1754492,2018-03-09 17:10:34 UTC,apport information
1754492,2018-03-09 17:10:28 UTC,apport information
1754492,2018-03-20 18:29:25 UTC,Please try kernel in https://people.canonical.com/~khfeng/lp1754492/
1754492,2018-04-24 19:20:47 UTC,"@Kai-Heng, I've recently reinstalled Ubuntu Gnome and now have kernel 4.13.0-39-generic. Does that suffice? or does it need to be installed from the link you specified?"
1754492,2018-04-25 06:58:00 UTC,"Hi, I've built a new one base on latest Artful kernel, please try it:
https://people.canonical.com/~khfeng/lp1754492-2/"
1754492,2018-04-27 04:40:03 UTC,Which laptop light do you refer to?
1754492,2018-03-09 17:11:50 UTC,"@Joseph, It existed since I first installed Ubuntu Gnome on this (new) machine back in August."
1754492,2018-03-09 17:10:27 UTC,apport information
1754492,2018-04-26 21:14:17 UTC,"Thanks. I'll try it this weekend.
Moreover, I'd like to add that when suspended the laptop light remains solid. Wouldn't it be more appropriate to have it ""beat""?"
1754492,2018-03-09 17:10:24 UTC,apport information
1754492,2018-03-08 22:40:37 UTC,"Distributor ID: Ubuntu
Description:    Ubuntu 16.04.4 LTS
Release:        16.04
Codename:       xenial"
1754492,2018-03-08 23:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754492,2018-03-09 07:49:19 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1754492,2018-03-09 17:10:11 UTC,apport information
1754492,2018-03-09 17:10:13 UTC,apport information
1754492,2018-03-09 17:10:25 UTC,apport information
1754492,2018-03-09 17:10:18 UTC,apport information
1754492,2018-03-09 17:10:22 UTC,apport information
1754492,2018-03-09 17:10:16 UTC,apport information
1754492,2018-03-09 17:10:19 UTC,apport information
1754492,2018-03-09 17:10:21 UTC,apport information
1754506,2018-06-12 14:37:08 UTC,This bug was fixed in the package autofs - 5.1.2-3ubuntu1
1754506,2018-06-06 20:30:37 UTC,Fix confirmed with the patch from comment #8
1754506,2018-04-03 05:24:29 UTC,"Thanks for debugging this issue down to your configuration bit that triggered it.
As well as to point out the existing upstream fix."
1754506,2018-03-18 18:35:51 UTC,"Just a little update: I think I've figured out what causes autofs to stall.
Since I've tested sshfs and cifs, and reproduced it using both, I can rule out a specific target fs.
I think it has something to do with the indirekt map feature:"
1754506,2018-03-30 11:16:43 UTC,"I finally solved the problem with the help of Ian Kent.
He pointed me in the right direction: https://git.kernel.org/pub/scm/linux/storage/autofs/autofs.git/commit/?id=37dd05dd1bccdedc4157902420e1da506b2bf35f"
1754506,2018-03-13 19:38:41 UTC,"Some additional information:
I enabled the debug output for autofs4 module: echo -n 'module autofs4 +p' > /sys/kernel/debug/dynamic_debug/control
According to the kernel log, the mount is reported busy: autofs4:pid:7051:autofs4_mount_busy: returning = 1"
1754506,2018-03-13 19:07:40 UTC,"As far as I know, just a few steps are necessary to reproduce this issue:
1. Setup a simple smb server on machine a, like the one I've attached to this report.
2. Create a smb user on machine a: smbpasswd -a $username
3. Enable smb in auto.master on machine b (and set the timeout to something small, e.g., 30 secs):
/media/smb/      program:/etc/auto.smb
4. Save the credentials on machine b: echo ""username=$username\npassword=$password"" > /etc/creds/machineb
5. Try to access the home directory from machine b:
user@machineb:~$ ls -lh /media/smb/machineb/$username
6. The smb mount is still there after more than 30 seconds"
1754506,2018-03-12 13:23:32 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1754506,2018-03-12 13:22:56 UTC,"Hi Alexander,
this seems to be a reoccuring issue but so far always turned out to be a config issue.
E.g. for some hints and similar cases:
https://ubuntuforums.org/showthread.php?t=1355715
https://askubuntu.com/questions/194727/mounting-samba-share-whenever-its-available-unmounting-when-its-not"
1754506,2018-03-14 08:28:03 UTC,"Some additional information:
By further digging into it, I've learned that for some reasons the smb is reported busy.
In autofs4_mount_busy(https://elixir.bootlin.com/linux/v4.15.6/source/fs/autofs4/expire.c#L34) the call of may_umount_tree() returns 0. This indicates that the mount is considered busy. I'll keep you posted."
1754507,2020-09-28 12:01:38 UTC,Fix released in git-ubuntu version 1.0
1754511,2018-12-17 10:10:11 UTC,These are just warnings but the logging config does need to be improved.
1754513,2018-03-09 00:05:11 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754517,2018-03-09 02:05:06 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754521,2019-05-23 20:40:14 UTC,Installing gnunpg2 should fix the problem.
1754521,2019-05-23 20:40:49 UTC,As duplicate of https://bugs.launchpad.net/ubuntu/+source/qtpass/+bug/1829693
1754521,2019-01-13 12:33:36 UTC,Can't reproduce. Please provide a screenshot of the dialog box.
1754529,2018-03-09 01:09:03 UTC,and partman. It would be cool if one could do both attachments at the same time.
1754529,2018-03-09 02:05:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754536,2018-03-09 02:04:58 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754536,2018-04-10 23:59:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754537,2018-03-09 18:37:07 UTC,"mesa hasn't been updated in trusty, so there's no reason to update libjogl either"
1754540,2018-12-14 05:59:24 UTC,"Same issue in senlin bug report:
https://bugs.launchpad.net/senlin/+bug/1801755"
1754540,2018-03-12 11:49:29 UTC,I think you are missing --resource-id and --resource-type in the command.
1754542,2019-11-27 03:06:13 UTC,"Hi Lee,"
1754542,2019-11-27 02:41:05 UTC,"Hi Zhang Chen ,"
1754542,2018-08-07 11:53:42 UTC,"Currently, we support virtio-net, and not support all vhost-xxx."
1754542,2018-07-27 10:35:33 UTC,"Yes, ide works."
1754542,2018-07-27 06:55:35 UTC,"Hi Chao,"
1754542,2018-07-27 04:53:07 UTC,"Hi, Zhang Chen"
1754542,2018-06-03 16:28:02 UTC,"Hi Suiheng,"
1754542,2019-11-27 06:35:12 UTC,"Hi Zhang Chen
I use sysbench compare Host、Qemu Native VM(virtio-blk)、Qemu Native VM、Qemu
colo disk performance.
The result in below attachment.
Qemu Native VM(virtio-blk) use -device virtio-blk-pci
Qemu colo follow https://wiki.qemu.org/Features/COLO
Thanks
Lee"
1754542,2018-03-23 09:03:17 UTC,Thanks zhijian.
1754542,2018-03-22 07:31:20 UTC,"I took a photo when SVM print reset.
It seems like kernel panic.
I hope this will help."
1754542,2018-03-22 07:39:39 UTC,SVM error photo
1754542,2018-03-17 20:14:53 UTC,"Hi Suiheng,"
1754542,2018-03-17 20:16:04 UTC," Hi Suiheng,"
1754542,2018-03-21 06:04:58 UTC,"Hi Suiheng,"
1754542,2018-03-20 09:18:00 UTC,"It is my trace event file.
I read it many times, but still can't find the cause of the error.
I just found after colo_vm_state_change ide_reset and ps2_kbd_reset ..."
1754542,2018-03-19 02:08:55 UTC,"Hi Zhang Chen，
I follow the https://wiki.qemu.org/Features/COLO, And Vm no crash.
But SVM rebooting constantly after print RESET, PVM normal startup."
1754542,2018-03-20 09:19:16 UTC,It is svn trace even
1754548,2018-03-12 08:53:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754563,2018-05-08 04:36:04 UTC,This issue was fixed in the openstack/neutron 10.0.6 release.
1754563,2018-03-16 14:36:05 UTC,"Reviewed:  https://review.openstack.org/552111
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=61aa1fe9512f2a71feffbcce55b82a9fe17651c3
Submitter: Zuul
Branch:    stable/queens"
1754563,2018-05-08 04:32:17 UTC,This issue was fixed in the openstack/neutron 11.0.4 release.
1754563,2018-03-29 17:31:09 UTC,This issue was fixed in the openstack/neutron 12.0.1 release.
1754563,2018-03-17 01:38:43 UTC,"Reviewed:  https://review.openstack.org/552539
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=40ac93b806528f49521f6244859d0118c4113aff
Submitter: Zuul
Branch:    stable/pike"
1754563,2018-03-13 15:03:02 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/552540"
1754563,2018-03-13 15:01:05 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/552539"
1754563,2018-03-16 00:33:22 UTC,"Reviewed:  https://review.openstack.org/552540
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0f46559557c0942b69503b4dd357d68132da0762
Submitter: Zuul
Branch:    stable/ocata"
1754563,2018-03-12 18:18:32 UTC,Might just be a missing setup_privsep() call in L2 agent init code.
1754563,2018-03-12 18:35:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/552111"
1754563,2018-03-12 18:27:00 UTC,"Yes, that was the problem.  It was actually just fixed in master, but in a larger change.  We will have to create a stable backport with just the relevant change."
1754571,2018-03-15 08:05:16 UTC,"It is now clear that this fault applies to Ubuntu 16.04, not to any specific Linux kernel version. I have found that Ubuntu 17.10 with the same current Linux (4.13 35/40) does not have the fault, but 16.04.3 running on the same hardware and with the same Linux does show the fault:  boot-up only progresses to a frozen log-in screen, and the build will only run in recovery mode.  The previously reported screen handling problems are almost certainly due to the known reduced display support in this recovery mode, and are not the real fault, which is that these 16.04 builds won't boot-up."
1754571,2018-03-12 19:24:25 UTC,Joseph:
1754571,2018-03-12 14:18:02 UTC,Does this bug go away if you boot into the prior kernel?
1754571,2018-03-09 12:32:18 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1754571,2018-03-09 12:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754571,2018-03-12 08:31:47 UTC,"I have retested this with the upstream kernel 4.16.0-041600rc4-generic, and the symptoms are the same:  boot-up only gets as far as a frozen log-in screen."
1754575,2018-03-09 08:37:34 UTC,Note that this affects open MPs as well.
1754575,2018-03-09 15:21:47 UTC,"I don't think this is with solving or spending time on. It's because of
where/how LP stores MP data."
1754575,2018-03-13 20:24:45 UTC,"We decided today to live with the consequences of this for now, but have two high-level approaches before we next have to 're-import the world'."
1754575,2020-09-24 13:06:38 UTC,"I addressed this with new behaviour for --reimport - it fetches rich history, reimports, and then force pushes everything with --prune, which removes all refs not pushed. This means that the repository is never actually deleted, so this issue is resolved. Most of this was in commit 7a60e7f."
1754581,2018-03-12 19:10:42 UTC,"Do you happen to know if this is a regression in Trusty, or if this bug always existed in Trusty and was fixed in Xenial and newer kernels?"
1754581,2018-03-09 13:20:51 UTC,"On Fri, Mar 9, 2018 at 9:49 AM, Joseph Salisbury
<email address hidden> wrote:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
"
1754581,2018-03-19 16:24:39 UTC,I think it may have always been present; I can recreate this on Trusty GA kernels; we've changed how we clean/remove bcache devices which I believe is triggering a new path on Trusty kernels.
1754581,2018-03-09 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754581,2018-03-09 08:49:48 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1754584,2018-03-29 21:39:24 UTC,"One requires both the user space and the kernel packages to be installed, so please re-test when the kernel also appears in -proposed.  Apologies for the confusion."
1754584,2018-03-23 11:30:11 UTC,"I suspect this happens because the page is being locked in mappedread and again in filemap_page_mkwrite. Since the page is already locked, the locking of the page in filemap_page_mkwrite causes the task to block indefinitely."
1754584,2018-03-23 12:18:42 UTC,Touching page before the pread causes the page to be dirty and a page fault occurs and then the code does not hang.
1754584,2018-03-24 11:07:05 UTC,"Upstream have developed a fix for this, I'll get it packaged and tested on Monday: https://github.com/zfsonlinux/zfs/pull/7339"
1754584,2018-03-23 10:57:09 UTC,And still occurs with the latest ZFS from today's SPL+ZFS git repos.
1754584,2018-03-29 18:35:56 UTC,"Hello Joshua, or anyone else affected,"
1754584,2018-03-29 18:36:43 UTC,"Hello Joshua, or anyone else affected,"
1754584,2018-03-29 20:12:35 UTC,"I am marking this verification-failed as my steps to reproduce this and the ones in step #24 still fail in Bionic, Artful, and Xenial."
1754584,2018-03-29 20:30:42 UTC,@colin - is there a requirement to have a newer kernel and not just a newer zfs-linux for this to be fixed?
1754584,2018-04-10 21:53:21 UTC,Is there a kernel ready for testing this on bionic or xenial?
1754584,2018-04-18 00:14:28 UTC,"The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1754584,2018-04-13 23:43:34 UTC,This bug was fixed in the package linux - 4.15.0-15.16
1754584,2018-04-16 16:18:44 UTC,"Hi @powersj,"
1754584,2018-04-16 18:22:56 UTC,"Using two NUCs, one with Xenial and one with Artful I was able to verify both the kernel and zfs fixes. Marking verification-done-artful and erification-done-xenial"
1754584,2018-04-17 10:50:24 UTC,Thanks for verifying Joshua. Much appreciated!
1754584,2018-04-18 00:14:18 UTC,This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu20
1754584,2018-03-22 20:27:33 UTC,Boiled it down to a minimal async I/O reproducer as follows:
1754584,2018-04-18 00:14:42 UTC,This bug was fixed in the package zfs-linux - 0.6.5.11-1ubuntu3.3
1754584,2018-04-23 08:22:44 UTC,This bug was fixed in the package linux - 4.4.0-121.145
1754584,2018-04-23 09:21:59 UTC,This bug was fixed in the package linux - 4.13.0-39.44
1754584,2019-02-14 13:34:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1754584,2019-02-14 16:44:45 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1754584,2018-04-10 22:09:49 UTC,Not yet
1754584,2018-03-22 16:55:20 UTC,"And also on 4.4.0-116-generic, zfs 0.6.5.6-0ubuntu19"
1754584,2018-03-26 16:54:24 UTC,This bug was fixed in the package zfs-linux - 0.7.5-1ubuntu11
1754584,2018-03-09 15:07:55 UTC,I marked this private.  Unpriviledged user on a zfs filesystem can essentially create processes that cannot be killed.
1754584,2018-03-22 16:16:28 UTC,"This can be reproduced with 4.13.0-37-generic, 0.6.5.11-1ubuntu3.2 so it's not a regression."
1754584,2018-03-09 08:30:12 UTC,This change was made by a bot.
1754584,2018-03-09 08:48:19 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1754584,2018-03-09 09:36:20 UTC,"> Did this issue start happening after an update/upgrade?
> Was there a prior kernel version where you were not having this particular problem?
"
1754584,2018-03-09 09:38:39 UTC,Since I need zfs I did mark as kernel-fixed-upstream.
1754584,2018-03-09 10:20:14 UTC,apport information
1754584,2018-03-09 10:20:16 UTC,apport information
1754584,2018-03-09 10:20:16 UTC,apport information
1754584,2018-03-09 10:20:18 UTC,apport information
1754584,2018-03-09 10:20:18 UTC,apport information
1754584,2018-03-09 10:20:21 UTC,apport information
1754584,2018-03-09 10:20:20 UTC,apport information
1754584,2018-03-09 10:20:23 UTC,apport information
1754584,2018-03-09 10:20:24 UTC,apport information
1754584,2018-03-09 10:20:25 UTC,apport information
1754584,2018-03-09 10:20:26 UTC,apport information
1754584,2018-03-09 10:20:28 UTC,apport information
1754584,2018-03-09 10:24:35 UTC,This also occurs with the current proposed kernel in bionic when I used lxd + zfs:
1754584,2018-03-09 10:39:58 UTC,Reproduced again on 4.13 with zfs:
1754584,2018-03-09 10:51:15 UTC,Would it be possible for you to see if changing lxd to use btrfs instead of zfs on Bionic causes the bug?
1754584,2018-03-09 11:16:41 UTC,"> Would it be possible for you to see if changing lxd
> to use btrfs instead of zfs on Bionic causes the bug?
"
1754584,2018-03-09 13:54:06 UTC,"This does recreate on a zfs filesystem also.  No lxc is required.
Recreated as root and non-root on 4.15.0-10-generic ."
1754584,2018-03-09 14:04:11 UTC,recreate in a vm that had a free block device /dev/vdb.
1754584,2018-03-09 10:20:22 UTC,apport information
1754585,2018-03-23 01:11:09 UTC,"uninstallation of ceph worked.
however, upgrading was difficult it required:"
1754585,2018-03-29 18:21:16 UTC,"Hello getaceres, or anyone else affected,"
1754585,2018-03-23 01:13:11 UTC,sorry about the typos.
1754585,2018-03-22 09:25:13 UTC,This bug was fixed in the package ceph - 12.2.4-0ubuntu1
1754585,2018-03-16 09:58:38 UTC,See also https://answers.launchpad.net/ubuntu/+source/ceph/+question/665657
1754585,2018-03-19 12:32:22 UTC,"The ceph*.prerm scripts have snippets for stopping ceph daemons managed via the init.d scripts, which are no longer shipped by the Ubuntu packages."
1754585,2018-03-18 05:42:19 UTC,also affects Ubuntu 18.04 still
1754585,2018-03-16 09:54:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754585,2018-03-19 12:33:45 UTC,Committed to ubuntu/bionic branch; will be included with my 12.2.4 upload.
1754590,2018-04-19 16:57:21 UTC,"I do not know what the majority opinion is. But I personally like the traditional menus+icons interface, and I'm not a big fan of the ribbon model."
1754590,2018-04-19 17:02:53 UTC,"Additional note: Ribbons can be useful with the basic tools, but Inkscape has plenty of functionality in the menus. Is it possible to include it all in the ribbon interface? With Microsoft Office, I find the ribbon interface annoying when you need tools/functions that are not immediately available in the ribbon."
1754590,2019-06-11 02:16:55 UTC,"Hi, this has now been moved to our new GitLab request tracker. Please follow there for all future updates. Thank you!"
1754595,2018-03-09 19:32:29 UTC,I don't think we support installing the client from source like that.
1754595,2018-03-12 08:14:39 UTC,Totally agree with U wrt to support but upgrade workflow has changed a lot and to get early feedback have to install it from source.
1754601,2018-03-23 11:38:45 UTC,apport information
1754601,2018-03-23 11:38:46 UTC,apport information
1754601,2018-03-23 11:38:47 UTC,apport information
1754601,2018-03-23 11:38:50 UTC,apport information
1754601,2018-03-23 11:38:53 UTC,apport information
1754601,2021-01-25 06:20:34 UTC,I'm one of the OpenConnect developers.
1754601,2018-03-31 21:19:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754601,2020-11-17 08:06:54 UTC,"I have a similar issue with a Pulse Secure VPN
After some time and usually after one or more hex dumps were displayed, I get the following"
1754601,2021-01-20 15:05:05 UTC,"I've encountered the same problem as Sven N. (https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1754601/comments/24), with the same Ubuntu 20.04 and OpenConnect version v8.05-1. After a few minutes, the ""SSL read error"" and ""HTTP/1.1 101 Switching Protocols"" appear reproducibly, connected clients hang or abort, and I had to cancel and reconnect."
1754601,2018-03-23 11:38:44 UTC,apport information
1754601,2018-03-23 13:57:17 UTC,The information I added today is rather relativised by the fact that today I am unable to reproduce the problem with the Ubuntu 4.15 kernels either.  I will update this when (if?) it happens again.
1754601,2018-03-23 11:38:43 UTC,apport information
1754601,2018-03-23 11:38:32 UTC,apport information
1754601,2018-03-23 11:38:40 UTC,apport information
1754601,2018-03-16 08:30:31 UTC,I tried it for a bit with the old Artful kernel without issues.  As soon as I booted back into the Bionic 4.15 I was unable to connect to the VPN again.  It might be worth mentioning that the Cisco VPN tool also failed to connect.  I did not try that one with 4.13.
1754601,2018-03-23 08:24:56 UTC,"The Cisco tool has trouble with both kernels.  openconnect has so far not had problems with 4.16rc6 from the mainline PPA.  So it is only Bionic's 4.15 so far.  Not tested with mainline PPA 4.15, but I can if that makes sense.  I am guessing it is a heisenbug, but I might be wrong."
1754601,2018-03-23 09:24:21 UTC,"No problems seen so far with 4.15.7-041507-generic either, after 25 minutes connected to the VPN.  Sounds like it might be a problem in the Ubuntu changes to 4.15 after all."
1754601,2018-03-23 10:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754601,2018-03-23 11:38:33 UTC,apport information
1754601,2018-03-23 11:38:42 UTC,apport information
1754601,2018-03-23 11:38:36 UTC,apport information
1754601,2018-03-23 11:38:37 UTC,apport information
1754601,2018-03-23 11:38:38 UTC,apport information
1754601,2018-03-23 11:38:39 UTC,apport information
1754601,2018-03-23 11:38:35 UTC,apport information
1754602,2020-05-31 07:52:04 UTC,Hello!
1754602,2018-11-07 14:43:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754624,2019-12-17 06:09:04 UTC,"Microchip has made the source available for there AVR GCC 3.6.2 toolchain, which should provide the needed architectures for the new devices. The Debian maintain may need to be shown this link."
1754624,2019-02-21 04:53:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754634,2018-03-09 13:09:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/551274"
1754634,2018-03-19 10:21:15 UTC,"Reviewed:  https://review.openstack.org/551274
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=e1738033dfab389727e61c76eb0312f392f0ff41
Submitter: Zuul
Branch:    master"
1754634,2018-03-19 16:49:02 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554291"
1754634,2018-03-21 16:54:47 UTC,"Reviewed:  https://review.openstack.org/554291
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=2221868690e004a74de313fb2cba41045fe99bc8
Submitter: Zuul
Branch:    stable/queens"
1754634,2018-04-19 14:02:05 UTC,This issue was fixed in the openstack/glance 17.0.0.0b1 development milestone.
1754634,2018-04-24 18:11:21 UTC,This issue was fixed in the openstack/glance 16.0.1 release.
1754640,2019-08-07 19:02:43 UTC,UI has been deprecated
1754641,2018-03-22 16:43:02 UTC,Should we make use of `assumes` for this or passthrough?
1754641,2018-03-09 15:30:52 UTC,Thanks ondra! Can you please include the snapd version for when this was introduced? Or is it still master?
1754641,2018-03-09 16:55:32 UTC,"Timers are quire fresh but already available in edge and beta channel
They do work with version: 2.31.1+git607.a15e601~ubuntu16.04.1 and 2.31.2"
1754654,2018-03-09 13:02:01 UTC,Adding second screen shot of legacy staff client with correct due date displayed.
1754654,2018-03-09 14:24:04 UTC,There was a fix for this in 3.0.4:
1754654,2018-04-11 19:24:41 UTC,"I've also discovered this bug. The fix listed by Terran did correct a previous display issue with due dates, but this one appears to remain and both Robert (3.0.5) and I (3.0.4) are testing this on releases that contain that bug fix."
1754654,2018-05-30 19:14:00 UTC,"Apparantly it's not just the due date field, also seeing the exact problem with circulation library. I imagine just all the fields on this screen are coming from the very first record retrieved when doing a,"
1754655,2019-05-30 10:03:31 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.12
1754655,2019-05-14 23:32:50 UTC,Tested gnome-software 3.20.5-0ubuntu0.16.04.12 and was able to install moon-buggy from the command line and gnome-software showed the correct state before and afterwards.
1754655,2019-05-14 08:00:19 UTC,"Hello Robert, or anyone else affected,"
1754655,2019-04-25 13:57:14 UTC,"An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: ""Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.""."
1754655,2019-04-17 02:37:00 UTC,"This fix wasn't correctly applied in xenial, so will be re-uploaded"
1754655,2018-05-03 15:59:30 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1754655,2018-05-03 15:59:10 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.10
1754655,2018-05-02 03:50:53 UTC,On a fully updated Xenial VM with -proposed enabled moon-buggy shows as installed in GNOME Software if installed from the command line.
1754655,2018-03-29 22:13:10 UTC,"Hello Robert, or anyone else affected,"
1754655,2018-03-09 14:14:19 UTC,This bug was fixed in the package gnome-software - 3.27.92-0ubuntu2
1754657,2018-06-06 12:53:27 UTC,"@sil2100, please can you reject the python-pylxd uploads in the Artful queue?"
1754657,2018-06-06 15:29:42 UTC,"Hello Corey, or anyone else affected,"
1754657,2018-09-20 12:35:53 UTC,"The verification of the Stable Release Update for python-pylxd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1754657,2018-09-20 12:36:14 UTC,This bug was fixed in the package python-pylxd - 2.0.7-0ubuntu1
1754657,2018-10-03 19:45:01 UTC,The verification of the Stable Release Update for python-pylxd has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1754657,2018-06-06 12:52:37 UTC,"Sorry, confusing releases on my end. Ok so we'd have to move python(3)-requests-toolbelt to Depends, which would require it to be in main, if we were to upload to Artful. Artful is almost EOL so let's see if we can handle this in the cloud-archive only."
1754657,2018-10-03 19:46:24 UTC,"@tinwood, did you get a chance to test pike-proposed?"
1754657,2018-10-25 13:57:42 UTC,"@coreycb pike-proposed on xenial is giving python 2.2.6, which is fine as it will work. 2.0.7 is in xenial standard:"
1754657,2018-10-25 14:09:24 UTC,Thanks @tinwood. If pike-prposed has been successfully tested can you change the tag from verification-pike-needed to verification-pike-done? Then we can get this promoted to pike-updates.
1754657,2018-10-29 12:17:17 UTC,The verification of the Stable Release Update for python-pylxd has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1754657,2018-10-29 12:17:19 UTC,"This bug was fixed in the package python-pylxd - 2.2.6-0ubuntu0.17.10.1~cloud0
---------------"
1754657,2018-10-03 19:45:04 UTC,"This bug was fixed in the package python-pylxd - 2.0.7-0ubuntu1~cloud0
---------------"
1754657,2018-06-06 12:30:38 UTC,"@Corey, yes, you're correct; xenial doesn't use it; It first appeared in 2.2.5, and xenial is on the 2.0.x series.  So artful got 2.2.x series, which means artful has the issue, whereas xenial as 2.0.7 which means it doesn't have this feature (as we didn't backport it)."
1754657,2018-06-06 11:21:30 UTC,"@sil2100, that is a good catch, and sadly, Corey, there isn't an easy solution.  What requests.toolbelt is used for is to allow Multipart uploads to lxd (from pylxd) so that data can be streamed from disk, rather than pulled into memory."
1754657,2018-03-22 12:31:05 UTC,"Hello Corey, or anyone else affected,"
1754657,2018-06-05 19:42:03 UTC,"I've uploaded a new version of python-pylxd to Artful with python(3)-requests-toolbelt added to Suggests, and have also uploaded Bionic and Cosmic versions of python-pylxd with python(3)-requests-toolbelt fixed via the above linked bug."
1754657,2018-06-05 18:22:27 UTC,I've opened the following bug to track the missing python(3)-requests-toolbelt issue: https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/1775238
1754657,2018-06-05 18:16:30 UTC,"That is a great catch, and an issue in bionic and cosmic as well, so we'll need fixes in those releases first. I think we can add it via Suggests in Artful and Depends in Bionic/Cosmic (since it's in main for the latter). The reason python-pylxd is in main is due to use by nova-lxd, which doesn't use the Image.create() method. Rather, pre-built images are retrieved from glance in the case of nova-lxd. Since that's the case I think we can consider this dependency as being optional and add it as a Suggests for Artful in this SRU."
1754657,2018-06-04 19:16:32 UTC,Just want to confirm: do the python*-requests-toolbelt build-dependencies result in any binary dependencies in the end binary packages? I'm asking as python-pylxd is in main while python-requests-toolbelt is still in universe in artful for instance. Wouldn't want a component mismatch with this SRU.
1754657,2018-06-02 11:09:54 UTC,@corey.bryant -- I probably didn't have 2.2.6 ready at the time; sorry.  I'll test it as soon as it becomes available in proposed.  Thanks.
1754657,2018-06-01 19:48:30 UTC,I've uploaded 2.2.6 to the artful review queue [1] where it is awaiting review by the SRU team.
1754657,2018-06-01 18:23:48 UTC,"I don't completely remember why but I think 2.2.6 wasn't available at the time that 2.0.7 was uploaded. Either way, I don't think it ever got uploaded so I'll do that now."
1754657,2018-06-01 16:48:54 UTC,I can't check artful as pylxd 2.2.6 doesn't appear in artful-proposed yet.
1754657,2018-06-01 15:22:33 UTC,So tested this manually on xenial (pylxd/lxd) and it's all working perfectly.
1754657,2018-03-15 18:02:23 UTC,"Hello Corey, or anyone else affected,"
1754657,2018-03-09 14:35:08 UTC,I've uploaded python-pylxd 2.0.7 to the xenial Unapproved queue where it is awaiting SRU team review: https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=
1754657,2018-06-06 11:42:22 UTC,OK thanks for checking. I see that the version of nova-lxd in bionic uses images create() but I'm not seeing a similar call in the xenial version. Is it possible the xenial version of nova-lxd doesn't use it?
1754671,2019-05-15 17:34:10 UTC,"dwmw2, did you apply the systemd fix from comment #27? For this bug to be fixed you need BOTRH the fixed packages of network-manager and systemd."
1754671,2019-05-15 18:33:47 UTC,These systems are using dnsmasq not systemd-resolver. This was done for historical reasons; I'm not sure of the specific bug which caused that choice.
1754671,2019-03-08 07:54:06 UTC,Is there a 16.04 package? This was a regression there caused by an earlier update.
1754671,2019-05-22 17:11:47 UTC,"We aren't using systemd-resolver for various historical reasons; we are using dnsmasq which should be expected to work. It isn't, but we have manually added the dns-priority=-1;dns-search=~. settings which make it work, as an emergency deployment when the latest NM update broke things for everyone."
1754671,2019-05-22 17:28:39 UTC,"dwmw2, the systemd fix was mainly meant for people with standard configuration where this fix is actually needed and solve the problem."
1754671,2019-05-15 17:20:43 UTC,"I am receiving reports that it isn't fixed in 18.04 either. Users are still seeing DNS lookups on the local network, until they manually edit the VPN config to include:"
1754671,2019-05-22 16:26:49 UTC,"Unfortunately, the SRU for systemd did not yet get processed. Therefore I have now uploaded this version of systemd to my PPA so that you can already test/get your problem solved. Please tell here whether it actually fixes the bug."
1754671,2019-05-13 16:25:58 UTC,"The original bug report was about a regression in 16.04 with the dnsmasq integration.  While I'm glad this got the ball rolling on the bionic networkd integration, let's not forget that we broke xenial?  Added a xenial task for network-manager accordingly."
1754671,2019-04-01 03:38:05 UTC,"Looking at the upstream bug, it looks like the fix relies on reworking large parts of the code and wouldn't be easy to SRU to Xenial."
1754671,2019-05-13 14:10:58 UTC,Will be releasing network-manager without the systemd part for now as it poses no threat to the user.
1754671,2019-05-10 12:57:56 UTC,"Hello dwmw2, or anyone else affected,"
1754671,2019-05-09 17:09:57 UTC,"Good news, the network-manager SRU is not broken or wrong, but an additional SRU, on systemd, is needed to actually fix this bug."
1754671,2019-05-08 16:14:03 UTC,I have now done the test under [Test Case] in the initial description of this bug report.
1754671,2019-04-13 21:24:46 UTC,"Based on comment #12 I am not sure that this is considered ""verification-done"" by the relevant developers and there was no comment given when the tags were changed.  Resetting."
1754671,2019-05-22 17:46:13 UTC,This is Bionic.
1754671,2019-03-11 16:50:17 UTC,"@seb128 please see ""In 16.04 the NetworkManager package used to carry this patch..."" in the bug description above."
1754671,2019-03-11 08:46:12 UTC,"@dwmw2, 'This was a regression there caused by an earlier update.' would give some details ont that? you should probably open another report specifically about that if there was a regression in a xenial update"
1754671,2019-05-13 14:14:00 UTC,This bug was fixed in the package network-manager - 1.10.14-0ubuntu2
1754671,2019-05-22 17:53:49 UTC,"> These systems are using dnsmasq not systemd-resolver.
> This was done for historical reasons; I'm not sure of
> the specific bug which caused that choice.
"
1754671,2019-10-10 18:20:01 UTC,"Great work, thank you very much!"
1754671,2019-08-21 09:03:43 UTC,"Without the ipv4.dns-priority and ipv4.dns-search settings being manually set, I see the wired device still being used for its own search domain. This is what causes the problem."
1754671,2020-11-12 14:31:19 UTC,"bugzilla.gnome.org is being shut down in favor of a GitLab instance.
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time."
1754671,2019-11-05 16:40:21 UTC,1.10.6-2ubuntu1.2 has cause a regression in functionality.
1754671,2019-11-04 14:08:01 UTC,"The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1754671,2019-11-04 14:07:48 UTC,This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.2
1754671,2019-10-31 15:44:42 UTC,"I have just run the test case from this bug description on the bionic-proposed version 1.10.6-2ubuntu1.2.
tcpdump does not show any leak of the VPN-specific queries. I have not observed other issues in my tests."
1754671,2019-10-28 22:40:44 UTC,"No worries about my previous comment, it is solved."
1754671,2019-10-28 21:48:33 UTC,Now network-manager is hanging on (all autopkg tests passed):
1754671,2019-05-22 17:59:00 UTC,"Due to the SRU regressions reported in LP: #1829838 and LP: #1829566, I have reverted this SRU for the moment, restoring network-manager 1.10.6-2ubuntu1.1 to bionic-updates.  I am marking this bug verification-failed pending resolution of the reported regressions."
1754671,2019-10-26 21:35:41 UTC,"The netplan.io (arm64) autopkgtest failure (due to timeout) has been retried today, it passed:
http://autopkgtest.ubuntu.com/packages/n/netplan.io/bionic/arm64"
1754671,2019-10-25 10:33:56 UTC,"Hello dwmw2, or anyone else affected,"
1754671,2019-10-22 12:19:41 UTC,"Sorry for the late reply, I was on a conference last week."
1754671,2019-10-12 01:15:55 UTC,"This fix was first included in upstream 1.12.0, so this was actually fixed in Cosmic with network-manager 1.12.2-0ubuntu3"
1754671,2019-10-10 14:37:50 UTC,"I have backported what was listed as nm-1-10 fix for the bug in the upstream bugzilla [1].
I have also applied fixes for bug #1825946 and bug #1790098 to it."
1754671,2019-08-22 10:25:44 UTC,"In my case, 'older' is 1.10.6. At this point I'm just trying to get things working for my users on Ubuntu 18.04. So I'm comparing 1.10.6 (the current Ubuntu package) with 1.10.14 (the update, that was briefly shipped in 18.04 updates and then withdrawn)."
1754671,2019-08-22 07:51:33 UTC,"> My biggest practical problem here was that we had set
> ipv4.dns-priority and ipv4.dns-search options in an emergency
> deployment to our users after Ubuntu shipped the 1.10.14 update to
> 18.04 to fix this... and then when they *pulled* the update, new
> installations got the new config but older NM, and that didn't work
> correctly either.
"
1754671,2019-08-21 11:33:44 UTC,"No, ipv4.dns-priority=-1 breaks older NM because there, there's no default routing domain ~. and not even any way to set it. So lookups outside the VPN domains are just refused instead of being leaked to the local nameservers as they were before."
1754671,2019-10-25 12:24:41 UTC,"All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1754671,2019-02-09 04:20:18 UTC,I can also confirm that the network-manager package version 1.10.14-0ubuntu1 from bionic-proposed fixes the issue.
1754671,2018-11-19 21:51:26 UTC,"Excellent, thank you Thomas!"
1754671,2019-02-05 11:37:09 UTC,"Ack, then I will remove those settings and test again. With dnsmasq, OK? This can never work with plain resolv.conf anyway."
1754671,2018-11-07 15:46:13 UTC,See the discussion in the upstream bug report. The fix is in the master branch and needs to be backported to the 1.10 series so that we can pick it up in bionic.
1754671,2018-11-02 13:48:48 UTC,"Same question, will it be backported to Ubuntu 18.04 ?"
1754671,2018-10-29 15:46:44 UTC,Is it possible to upload a fixed package to bionic backports?
1754671,2018-10-17 16:27:36 UTC,"(In reply to Beniamino Galvani from comment #55)

>
> Any opinions? This latter approach seems doable, but it is a big
> change for a minor release.
"
1754671,2018-10-17 15:46:55 UTC,"The backport is quite complicated due to several changes that made the
DNS code in nm-1-12 diverge from nm-1-10. The th/policy-and-mdns
branch [1] alone changed:"
1754671,2018-10-16 08:39:10 UTC,"@David, I don't think that comment is either constructive or true. We have somewhat limited resources and struggle a bit sometime to keep up with network-manager bugfixes/update but we would backport a fix for this bug to our stable serie if there is one landing in the 1.10 vcs."
1754671,2018-10-15 21:03:59 UTC,"I'd like to see them in a Fedora release, which is preferably via a 1.10.z release rather than just cherry-picking the patches."
1754671,2018-10-15 18:35:16 UTC,"(In reply to Olivier Tilloy from comment #51)

> (In reply to Beniamino Galvani from comment #45)
> > (In reply to Michael Biebl from comment #42)
> > > Will those changes be pulled into the nm-1-10 branch as well?
> >
> > Let's wait until the branch is merged to master and see if there are
> > any issues. If there are no complaints, we can think about backporting
> > it to a stable branch.
>
> Now that this has been in master and 1.12 for a few months, is this
> something you would consider backporting to 1.10 ?
"
1754671,2018-10-15 15:02:19 UTC,"(In reply to Beniamino Galvani from comment #45)

> (In reply to Michael Biebl from comment #42)
> > Will those changes be pulled into the nm-1-10 branch as well?
>
> Let's wait until the branch is merged to master and see if there are
> any issues. If there are no complaints, we can think about backporting
> it to a stable branch.
"
1754671,2018-05-14 17:39:19 UTC,A fix was merged to the upstream master branch: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d9782589248e61c0cb5aec90e3eb62612891116b
1754671,2018-05-14 14:44:19 UTC,FWIW the original situation appears to be fairly broken regardless of the security situation. I've lost count of the number of times in my recent travels that the DNS servers of the airport/hotel/etc. in which I find myself are *not* directly on the local subnet. And thus aren't accessible as soon as I join the VPN.
1754671,2019-02-05 11:50:56 UTC,"(In reply to David Woodhouse from comment #67)

> Ack, then I will remove those settings and test again. With dnsmasq, OK?
"
1754671,2018-05-14 07:59:27 UTC,"That is, bg/dns-bgo746422 LGTM"
1754671,2018-05-14 07:36:41 UTC,bg/dns-domains-bgo746422 LGTM
1754671,2018-04-10 13:03:19 UTC,There's active work going on upstream (see https://bugzilla.gnome.org/show_bug.cgi?id=746422 and https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=bg/dns-bgo746422) to fix the issue.
1754671,2018-03-20 14:51:52 UTC,This is CVE-2018-1000135. For some reason the 'Link to CVE' option above doesn't seem to work.
1754671,2018-03-09 14:13:13 UTC,"Confirming this is broken. Dropping the patch 0001-dns-use-DBus-to-make-dnsmasq-nameserver-changes.patch in network-manager (1.2.4-0ubuntu0.16.04.1) was done, but it looks like not all the code in that patch was actually upstream."
1754671,2018-11-07 15:58:54 UTC,"This is fixed in the 1.12 series of network-manager (1.12.0 release), so cosmic and dingo are not affected."
1754671,2018-11-16 18:48:22 UTC,I confirm that the Ubuntu desktop team would be interested in picking up the update if this fix and related branches were to be backported to the 1.10 branch.
1754671,2018-05-14 13:32:11 UTC,Merged to master:
1754671,2019-02-04 21:50:33 UTC,"Not sure what happened there. It was looking up *some* names in the $COMPANY.com domain on the VPN, but others not, consistently. I couldn't see a pattern."
1754671,2019-02-05 09:44:20 UTC,"Before I do that, do we agree that I shouldn't have needed to manually set dns-priority and dns-search as described in comment 62, for a VPN connection which is full-tunnel?"
1754671,2019-02-05 08:18:22 UTC,"Hi,"
1754671,2019-02-05 07:48:09 UTC,"@dwmw2, as far as i understand, you should configuring DNS through systemd-resolve only. Try remove your edits from `/etc/NetworkManager/system-connections`, or even delete your connections from NetworkManager interface, and create new. After that, establish vpn connection and see at `systemd-resolve --status`, you should get something like this:"
1754671,2019-02-04 22:38:28 UTC,"Gr, and apologies too for spelling your name wrong, Sebastien."
1754671,2019-02-04 22:37:35 UTC,I've finally managed to test the Ubuntu 18.04 backport; apologies for the delay.
1754671,2018-11-16 20:23:00 UTC,it's backported to nm-1-10 branch: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1e486a721de1fec76c81bfc461671a7fbdae531b
1754671,2019-02-04 21:23:16 UTC,"Hm, that didn't last long. Now it isn't looking up *anything* in the VPN domains. It's all going to the local VPN server. I don't know what changed."
1754671,2019-02-04 14:55:16 UTC,network-manager-1.10.14-0ubuntu1 does seem to fix the DNS problem here; thanks.
1754671,2019-01-08 14:05:08 UTC,"@Steve (sorry for the late reply): not sure how that relates to bug #1726124, but in my limited understanding of the changes, they shouldn't regress the split-DNS use case."
1754671,2018-12-24 07:09:51 UTC,"I installed package of network-manager 1.10.14-0ubuntu1 from bionic-proposed, and can confirm that version fixed dns leak: now when vpn connection established it gets `DNS Domain: ~.` in systemd-resolve automatically, so no more needed to manually apply command `systemd-resolve -i tun0 --set-domain=~.`. This positively fix dns leakage, verified by dnsleaktest.com"
1754671,2018-12-21 18:09:03 UTC,How does this proposed change relate to LP: #1726124?  Are users who are currently relying on correct split DNS handling by network-manager+systemd-resolved in bionic going to see this regress and have all DNS requests now sent over the VPN when they aren't supposed to?
1754671,2018-12-21 17:22:09 UTC,"Please test and share your feedback on this new version here, but refrain from changing the verification-needed-bionic tag for now. This new version includes many changes and we want to give it an extended testing period to ensure no regressions sneak in, before it is published to bionic-updates. Thanks!"
1754671,2018-12-21 16:53:19 UTC,"Hello dwmw2, or anyone else affected,"
1754671,2018-12-19 15:33:07 UTC,I've updated the description for the SRU but if someone had a better description of a testcase that would be welcome
1754671,2018-11-20 21:25:17 UTC,That's handy. The backport to Ubuntu 18.04 is being tracked by https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1754671.
1754671,2018-11-20 10:58:33 UTC,The fix is included also in the 1.10.14 release.
1754671,2018-11-19 21:51:40 UTC,The fix was backported to the upstream 1.10 series.
1754671,2019-02-05 10:00:35 UTC,"(In reply to David Woodhouse from comment #65)

> Before I do that, do we agree that I shouldn't have needed to manually set
> dns-priority and dns-search as described in comment 62, for a VPN connection
> which is full-tunnel?
"
1754673,2018-03-09 16:55:55 UTC,"It seems like the focus on GerbView's supported Gerber formats are extremely myopic towards KiCad. If the parser exists for the Gerber format, which it does, and KiCad can be a tool to view Gerbers from any other ECAD tool, it's hard for me to understand why that wouldn't be a useful feature."
1754673,2018-03-09 15:10:48 UTC,"Yes, but shouldn't we try to parse files created by other software if we can?"
1754673,2018-03-09 14:52:01 UTC,Be careful
1754673,2018-03-09 15:43:51 UTC,Perhaps.
1754677,2020-08-25 22:54:45 UTC,"Reviewed:  https://review.opendev.org/737225
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=28faa24e68467f7c10e00e433fec61914e172ca1
Submitter: Zuul
Branch:    master"
1754677,2020-06-22 07:34:54 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/737225"
1754677,2019-01-28 20:28:34 UTC,Removing the targetted milestone since stein-1 has passed.
1754677,2018-03-09 20:36:44 UTC,"yep, looking back in the git history, the type definition comes from before domains became projects."
1754677,2018-07-26 10:12:00 UTC,"Reviewed:  https://review.openstack.org/570438
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9cefb4dfc9f3497fd4c123ad9b1aadc65b2974d0
Submitter: Zuul
Branch:    master"
1754677,2018-03-09 20:29:33 UTC,I have a feeling the reason for this in keystone is that the query in question isn't looking at the type when doing a query: https://github.com/openstack/keystone/blob/master/keystone/assignment/backends/sql.py#L358
1754677,2018-09-26 13:29:03 UTC,"I don't see a fix committed for this, the @wip marker on the test that Raildo added is still there so I don't think this is fixed yet."
1754685,2018-03-13 01:16:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754685,2018-03-13 01:27:15 UTC,"Upgraded unity and a bunch of other packages on 2018-03-09.  After rebooting the next time, a crash dialog appeared.  The unity interface didn't load.  Clicked the report bug button."
1754687,2018-03-09 15:23:58 UTC,Log excerpt:
1754687,2018-05-26 11:36:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754693,2019-03-05 12:14:41 UTC,bionic got the hwe update already
1754693,2018-11-28 20:30:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754693,2018-12-04 17:12:57 UTC,"excellent, I'll prepare the sru for cosmic"
1754693,2019-01-28 10:05:57 UTC,"Hello Nathaniel, or anyone else affected,"
1754693,2019-02-01 07:06:31 UTC,this will be fixed via the hwe backport
1754693,2019-03-05 12:15:01 UTC,please verify this on cosmic
1754693,2018-11-22 14:14:27 UTC,please test new xserver from https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
1754693,2019-06-04 19:29:22 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1754693,2019-06-18 23:32:25 UTC,"Is this fix being backported to bionic?
I am still getting crashes with the snap version of skype (8.34.0.78) on xwayland-hwe-18.04."
1754693,2019-07-02 07:08:38 UTC,"bionic upload is on the queue, this bug is not mentioned on the changelog though so you get no notification about it"
1754693,2019-07-02 07:08:54 UTC,I mean it's on bionic-proposed
1754693,2019-07-21 02:09:14 UTC,"Fixed in Bionic
---"
1754693,2019-03-05 12:15:50 UTC,"oops, bionic did not get this yet"
1754693,2018-11-06 07:45:42 UTC,"Also, this is a SIGSEGV..."
1754693,2018-12-04 15:44:09 UTC,I can confirm with the PPA enabled I no longer see classic snaps crash when running wayland on cosmic.  I tested vscode and slack.
1754693,2018-11-06 06:04:13 UTC,"I have the same issue on 18.04, Wayland:
```
$ snap list skype
Name   Version    Rev  Tracking  Publisher  Notes
skype  8.33.0.41  63   stable    skype✓     classic
```"
1754693,2018-03-20 16:26:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754693,2018-04-11 09:48:00 UTC,"Tracking in:
https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca"
1754693,2018-04-24 09:59:24 UTC,On an up-to-date 18.04 machine today I can no longer reproduce this crash.  Could someone else confirm the same?
1754693,2018-04-24 13:49:34 UTC,I just ran updates on my 18.04 machine today also and can confirm Slack is working under Wayland
1754693,2018-04-24 16:51:00 UTC,I can still reproduce this now on my T470 with fully up-to-date bionic (also tried the https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging PPA)
1754693,2018-04-26 01:53:25 UTC,"Also tracking xorg-server, so people can find this bug more easily, and in case a fix is required in Xwayland directly."
1754693,2018-05-07 08:03:19 UTC,I've just done a little tidy up of some of the hottest xorg-server crashes. This one is presently #64 of the xorg-server crashes affecting bionic. There have been 7 reports of it on errors.ubuntu.com in the past year.
1754693,2018-11-06 07:22:34 UTC,"Now tracking in both:
https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae"
1754693,2018-10-04 02:13:20 UTC,"Now affecting cosmic too, only just:"
1754693,2018-10-22 14:12:00 UTC,"I'm on cosmic, upgraded from bionic, and I have the same issue. I had to revert to an X11 session in order to launch slack."
1754693,2018-10-22 14:16:13 UTC,"Oct 22 09:01:41 NOV13FG5Q2 dbus-daemon[2934]: [session uid=1000 pid=2934] Activating service name='org.gnome.GConf' requested by ':1.84' (uid=1000 pid=5586 comm=""/snap/slack/9/usr/lib/slack/slack --executed-from
="" label=""snap.slack.slack (complain)"")
Oct 22 09:01:41 NOV13FG5Q2 dbus-daemon[2934]: [session uid=1000 pid=2934] Successfully activated service 'org.gnome.GConf'
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE)
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Backtrace:
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x55bab3776c39]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f18b4fcae1f]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 2: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f18b1449760]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f18b130e4b1]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f18b122b52a]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f18b122b5ee]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f18b122b6c9]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f18b10f7432]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f18b146335d]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f18b1827e89]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f18b1825c93]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 11: /usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55bab36a3c69]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 12: /usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55bab36a168b]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 13: /usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55bab376561d]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 14: /usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55bab36abbd9]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 15: /usr/bin/Xwayland (glvndGetExports+0xde5) [0x55bab3785f35]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 16: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55bab3740bae]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 17: /usr/bin/Xwayland (InitFon..."
1754693,2018-03-09 16:00:22 UTC,"StacktraceTop:
 st_renderbuffer_delete (ctx=0x7fa39154b040, rb=0x5599442b15f0) at ../../../src/mesa/state_tracker/st_cb_fbo.c:238
 _mesa_reference_renderbuffer_ (ptr=ptr@entry=0x5599442b12a8, rb=rb@entry=0x0) at ../../../src/mesa/main/renderbuffer.c:212
 _mesa_reference_renderbuffer (rb=0x0, ptr=0x5599442b12a8) at ../../../src/mesa/main/renderbuffer.h:72
 _mesa_free_framebuffer_data (fb=fb@entry=0x5599442b1160) at ../../../src/mesa/main/framebuffer.c:223
 _mesa_destroy_framebuffer (fb=0x5599442b1160) at ../../../src/mesa/main/framebuffer.c:199"
1754693,2018-10-24 14:42:30 UTC,"I'm seeing what I believe to be the same issue with Visual Studio Code. If I try to start it after logging in using Gnome on Wayland, I find myself looking at a login screen. (If I login to Gnome on Xorg this does not happen.)"
1754693,2018-10-29 21:19:04 UTC,"I recently switched back to Ubuntu, only to find that Slack in a snap is still crashing on Wayland! I previously reported what seems like a related bug on snapcraft-- here's the link to the related bug with logs and some details from experiences on Fedora28 and Arch. https://forum.snapcraft.io/t/slack-for-linux-crash-on-wayland/5909"
1754693,2018-10-04 01:50:37 UTC,I have the same problem. How to provide additional information?
1754701,2018-03-14 11:03:54 UTC,"I believe something like this is already in progress. Specifically, having a way to give users a new simple registration flag."
1754701,2018-03-14 22:43:44 UTC,"@jameinel Yeah, just anything other then a user facing erroneous error/dead end."
1754701,2019-12-11 17:49:24 UTC,juju login now supports this process so marking this one fix-committed with the work that went into Juju 2.6.
1754702,2019-05-13 10:17:54 UTC,Please let me add up to those who consider this bug as greatly underestimated.
1754702,2019-05-13 10:54:56 UTC,Hi!
1754702,2019-05-13 14:53:29 UTC,Can someone please give instructions for how to reproduce this bug from a clean install of Ubuntu? I've tried changing the key binding in Tweaks but it doesn't happen here.
1754702,2019-08-25 17:59:13 UTC,Have you tried removing default 400 ms switcher delay?
1754702,2020-04-24 21:14:05 UTC,I just have installed Ubuntu 20.04 and this bug is still there (after switching layout everything on system freezes on a second). I had created question on askubuntu for 19.10 version https://askubuntu.com/questions/1211801/ubuntu-19-10-change-keyboard-language-freeze with video that displays freeze https://youtu.be/zIb2p1n80pA
1754702,2019-11-12 21:51:14 UTC,Better to use:
1754702,2019-11-12 21:51:50 UTC,Problem still exist in Ubuntu 19.10
1754702,2020-02-21 17:27:38 UTC,Also have this issue on Ubuntu 18.04.
1754702,2019-04-21 13:08:27 UTC,"> I originally filed this bug, so I am not sure if it can be marked as not in disco dingo
"
1754702,2020-05-07 12:09:03 UTC,"This is probably something which needs to be fixed upstream. If you have any useful information to add to the upstream issue, please do so."
1754702,2019-08-30 18:04:20 UTC,"#20 — well, it worked for me."
1754702,2019-04-21 06:35:21 UTC,"I have one more update. I could not use ubuntu 18.04 with this bug, so since then, I have been working on ubuntu 16.04 with unity. Yesterday I tried ubuntu 19.04 on a live usb and after configure to my usual setting, the bug was not present. I proceeded to install in on my computer, and I found the bug again. I tried the same procedure and I got the same results. Therefore, I am guessing it could be some configuration file somewhere.  After backing up my files, I did a clean install and now the bug is nowhere to be found. I could not determine what it was, but I am thinking it was something in the transition to gnome was not compatible. I am using 19.04 with no problem now, working perfectly and very surprised at how much the desktop has evolved in over a year. Beautiful and fast! kudos to everyone involved. I originally filed this bug, so I am not sure if it can be marked as not in disco dingo. Thanks"
1754702,2018-10-29 11:03:28 UTC,I have Ubuntu Gnome with English and Russian.
1754702,2019-04-01 11:04:57 UTC,I faced this issue too. Also I found that default layout switcher is very restrictive. For example I сouldn't set right Alt or Caps Lock keys to switch layout.
1754702,2019-01-30 13:19:00 UTC,"I'm using CapsLock to switch keyboard layouts, and I'm also affected by this bug.
I believe that now the priority of this bug is underestimated, because most of the people use one and sometimes two layouts, so they may not face with this problem often and assume that it's not so important. But when you live in a bilingual country and use 3 layouts all the time (I'm using UA/RU/EN), this problem becomes super annoying.
For me personally, it's the biggest reason why I'm not going to upgrade Ubuntu from 16.04 to 18.04 on my work PC."
1754702,2018-11-21 08:11:27 UTC,Same problem. In syslog after layout switching I can see:
1754702,2018-10-29 08:53:26 UTC,"i am use key ""WIN + SPACE"", and have problem about this bug."
1754702,2018-06-27 09:58:18 UTC,Same issue. Very annoying bug.
1754702,2018-05-10 16:47:58 UTC,"The other day installed ubuntu 18.04, and there is this bug. Please correct. It is impossible to work."
1754702,2018-05-10 16:46:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754702,2018-03-13 12:19:39 UTC,I changed the bug title a bit to reflect the known observations.
1754702,2018-03-13 11:46:40 UTC,"I also do not know about the code, but I tested ubuntu mate 18.04 and ibus.  Here a similar menu appears, but there is no delay when typing and changing input method.  Maybe it could be a hint to fix the bug."
1754702,2018-03-10 21:08:57 UTC,"That other bug is several years old, and both the code and exact behavior have changed since then, so I suggest that we keep them separate and let an experienced developer evaluate their possible relationship."
1754702,2018-03-10 15:58:19 UTC,"Hello, Thanks for the information.  I reviewed the information that you sent me.  It is the same issue as described in the ask ubuntu question.   Therefore it should be the same problem as the bug you mentioned.   I have been using unity, and for 18.04 thought about moving to gnome, so this is the first time I experience it.  Should I mark as duplicate of 1244090?  The only new information is that it affects 18.04 too. Thanks in advance."
1754702,2018-03-09 17:36:54 UTC,Thanks for your report. Changing affected package to gnome-control-center.
1754702,2019-04-05 07:33:19 UTC,"The issue persist after changing it with tweak. I'm using Shift + Alt for years. But after language switch it always takes 1-2 seconds. No screen freezing or anything. Just the language takes time to change. As mentioned above, very annoying if you have to change languages frequently."
1754703,2020-06-05 00:40:35 UTC,This bug was fixed in the package gnome-shell-extension-disconnect-wifi - 24-1
1754704,2018-05-22 09:16:45 UTC,Note that there is no setting to have this behavior. The exclustion requires first a set of cores:
1754704,2018-03-15 11:26:33 UTC,Is it possible todo:
1754704,2018-03-15 11:25:23 UTC,This sounds quite a sensible approach - the current approach does depend on all compute hosts being the same spec which is not awesome.
1754704,2018-05-22 08:59:43 UTC,"I have tried using the vcpu-pin-set: ""^0-6"":"
1754706,2020-09-28 12:01:31 UTC,Fix released in git-ubuntu version 1.0
1754713,2018-03-09 17:21:07 UTC,Addition: The issue occured in Ubuntu 17.10 beta and was never removed (I tried a dozen of kernels).
1754717,2018-03-09 17:47:48 UTC,Okay I probably reported it in a completely wrong location. Please close this.
1754729,2020-08-05 08:17:48 UTC,"For the record I see this kind of spurious failures regularly on OSCI, on random keystone endpoints but quite often on the /v2.0/tokens endpoint, like here:"
1754729,2018-03-23 19:15:15 UTC,Yep we hit it two times. 3/9 and 3/11.
1754729,2018-03-23 18:57:15 UTC,"@Ryan
I was asked to escalate this issue from management to get some additional attention. I could drop the field group, but only until we repro it again. I'll leave it in incomplete state until we see it again."
1754729,2018-03-23 18:14:09 UTC,"By measure of our SLA process, it is indeed an ""Infrastructure or control plane component crashing,"" but given the rarity and inability to provide a clear reproducer, I would not consider that ""Major"" under the same SLA process."
1754729,2018-03-23 18:10:26 UTC,"Given that this race is so far not reproducible in our lab, and the reporting lab as seen it two times, I suggest this is not necessarily a high SLA bug."
1754729,2018-03-23 18:14:55 UTC,"We will continue to attempt to reproduce, and if it recurs with increasing impact, please do let us know."
1754729,2018-03-22 21:59:01 UTC,"The deployment eventually succeeds, with what looks like failed hook retries.  We generally do not want to lean on that for resolution, so I consider this bug/race valid.  A hook should never go into error.  We'll triage further and attempt to reproduce.  Thank you."
1754729,2018-03-22 21:11:59 UTC,https://bugs.launchpad.net/charm-keystone/+bug/1754729/+attachment/5074539/+files/juju-crashdump-9ba9ac17-4eaf-4f4f-a844-18c789659936.tar.gz
1754729,2018-03-21 16:14:54 UTC,The bundle is attached.  This deployment does not have any overlay yaml file.
1754729,2018-03-21 16:07:59 UTC,Please attach the bundles and any other bundle inheritance files.
1754729,2018-03-14 19:49:40 UTC,Escalated to field high for additional attention
1754729,2018-03-23 17:56:41 UTC,"@Ashley,"
1754737,2019-05-17 07:11:24 UTC,"Change abandoned by Maysa de Macedo Souza (<email address hidden>) on branch: master
Review: https://review.opendev.org/548453"
1754748,2018-03-14 11:25:31 UTC,"Is the issue that there is an offer in bdx/daniel-redis, but they shouldn't even have visibility on it (much less getting a NotFound error).
Or is the client currently switched to a model that they don't have access to?"
1754748,2018-03-14 11:27:25 UTC,"I believe the intent is that offers that you cannot consume should just be treated as not there. The alternative would be to show them, but specifically flag them as ""you don't have rights to consume this""."
1754763,2018-04-30 20:23:12 UTC,I don't see it on the action list on 3.1. This is a very important function on Item Status screen.
1754763,2018-05-30 00:50:01 UTC,"The information previously displayed through the ""Show Last Few Circulations"" action is now available in 3.1 on the new ""Circ History List"" tab in Detail View in Item Status.  However, this tab is not convenient to use in comparison to the old action."
1754767,2018-03-19 14:55:23 UTC,"I'm not sure that we can change the error message, it's probably the case that there are a few different conditions that cause that error and Glance doesn't have a way to know what exactly the problem is."
1754771,2018-05-11 15:36:20 UTC,This change was made by a bot.
1754774,2018-11-30 15:37:41 UTC,"On a well-managed system, DNSSEC resolution should depend on the system-installed and system-maintained DNSSEC root, not on using icann-ca.pem for individual packages to separately update their root stores via sidechannel mechanisms."
1754776,2018-11-30 15:39:25 UTC,I think this is the same as https://bugs.debian.org/894580 which should have been fixed in 2.3.0-3
1754779,2018-03-10 00:20:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1754785,2019-03-24 22:51:13 UTC,"I built SBCL 1.3.0 and ran this exactly as shown,  many times over, and was unable to reproduce the problem."
1754792,2018-04-08 13:06:50 UTC,This will be solved in linux 4.17. There was a patch in January to enable this device: https://patchwork.kernel.org/patch/10162493
1754792,2018-03-30 16:08:03 UTC,"From what I understand, the touchpad has a secondary i2c interface used for advanced multitouch recognition. Using the aforementioned program, I collected some i2c packets and analyzed them."
1754792,2018-03-29 13:01:17 UTC,"Same here (HP x2 10-p030nl). For what it's worth, I attach the result of lsusb -v of this device."
1754792,2018-03-29 10:15:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754792,2018-03-30 14:13:29 UTC,"I gathered other information that may be relevant, a report generated with the Elan official tool from Windows. It contains some useful information on the commands to send and other things."
1754800,2019-12-04 08:56:47 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1754800,2019-12-04 08:56:56 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/551425
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1754800,2020-09-25 15:34:48 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1754800,2020-09-25 15:34:56 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/551425
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1754804,2020-11-19 21:05:18 UTC,Submitted an equivalent proposal to Debian:
1754804,2020-11-19 18:08:54 UTC,This bug was fixed in the package fonts-ubuntu - 0.83-4ubuntu2
1754804,2020-11-19 13:44:52 UTC,fonts-ubuntu is shipped by default on Ubuntu systems. It has significant reverse dependencies and cannot be uninstalled easily. Debian considers fonts-ubuntu to be “non-free” while Canonical disagrees.
1754804,2018-03-19 00:36:24 UTC,Debian doesn’t consider the Ubuntu Font Licence to be free; that’s why this package was uploaded (after all these years) to non-free.
1754804,2018-06-21 00:05:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754805,2018-03-12 14:47:41 UTC,"I don't have msts installed in my pc
On Mar 11, 2018 4:10 AM, ""cjakeman"" <email address hidden> wrote:"
1754805,2018-03-12 17:07:33 UTC,Thanks for responding about MSTS.
1754805,2018-03-12 17:27:24 UTC,"I don't know what I have done in 3-4 days
And
Acts are running in other routes
On Mar 12, 2018 10:50 PM, ""cjakeman"" <email address hidden> wrote:"
1754805,2018-03-17 09:47:16 UTC,Use the latest experimental version of OR instead of the 1.2 stable version. This could solve your problem.
1754805,2018-03-26 14:42:33 UTC,please send me link for open rails experimental
1754805,2018-03-10 22:32:53 UTC,Your file OpenRailsLog.txt shows lots of missing files reported. The problem that stopped Open Rails in this case was a problem with the sound.
1754820,2019-02-11 18:24:11 UTC,The problem appears to be due to missing packages
1754820,2019-02-11 18:00:04 UTC,"I've suffered with this problem as well and the suggested fix of resetting the panel only made it switch from the raven trigger applet getting moved around, to the user indicator applet being the roaming applet on my panel. To say this is annoying would be putting it likely, will probably end up switching to MATE over it tbh."
1754820,2018-03-10 22:14:48 UTC,"I tried to reproduce this fault on my 32bit UB daily build (downloaded yesterday), but was unable to do so even after restarting the computer 8-10 times."
1754820,2018-03-10 11:22:19 UTC,This I think has been reported previously upstream.
1754820,2018-03-11 06:58:48 UTC,"I had This problem on a 32 bit computer (réal install) and in an other one but in a VM.
But if i'm thé only one with This bug, it could be a mishandling."
1754820,2018-03-11 11:52:35 UTC,Yeah - its a known glitch - as I mentioned - it is cleared by doing a panel reset.
1754822,2018-03-10 10:25:27 UTC,"IIRC, the reason we don’t depend on it is because the tool couldn’t get
into main as it pulled dependencies that the security team would be unable
to maintain."
1754822,2018-03-10 11:46:34 UTC,Right. How do we handle this in the snap?
1754822,2018-03-10 12:44:54 UTC,"Seems we don't need a full WS-MAN implementation, here's
just-enough-python to get started:"
1754833,2018-03-15 12:29:49 UTC,"Well, there's another path - changing the default browser back to Firefox, which would be my personal preference... ;)"
1754833,2019-12-01 03:39:09 UTC,Has this issue been fixed yet?
1754833,2018-03-17 12:40:53 UTC,It looks highly likely (to my less-than-expert-eye anyway) that the bug you've linked to is the same issue...
1754833,2018-03-15 22:24:18 UTC,I'm wondering if something in xdg-utils has regressed as per this bug report https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1509139
1754833,2018-03-14 10:36:57 UTC,I've no idea what needs to be overridden to change the xdg-settings for the default-web-browser.  If anyone knows please shout.
1754833,2018-03-14 08:26:27 UTC,"Firefox is not installed, so I think your final point is likely to be correct."
1754833,2018-03-14 07:32:59 UTC,That's interesting.
1754833,2018-03-14 03:39:39 UTC,"Hi Olivier,
No, I hadn't tried to install chromium at all - I merely used the one version of chromium which came bundled with Budgie."
1754833,2018-03-12 12:28:00 UTC,"Could it be that you have installed chromium both from ubuntu packages and from the snap, by any chance?"
1754833,2018-03-14 10:28:14 UTC,"I can confirm it's a bug in budgie. I installed the latest ISO in a VM, and am seeing that after first login, not having launched any application except for terminal:"
1754836,2018-04-04 01:41:25 UTC,seems related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058
1754836,2018-04-04 02:22:34 UTC,Another piece of the puzzle: if you run:
1754836,2018-04-04 03:19:50 UTC,Some more: touching the system cache files doesn't make it work.
1754836,2018-04-04 05:54:59 UTC,"One final thing: this does not affect Ubuntu desktop after install. But it does affect the Ubuntu live image, which takes an extra minute or so to boot. It seems that the Ubuntu desktop installer rebuilds the system font cache during install."
1754836,2018-04-04 10:14:51 UTC,the issue sounds like https://bugs.freedesktop.org/show_bug.cgi?id=103652 / https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880574
1754836,2018-04-04 12:51:48 UTC,"For reference, the lp report tracking the fontconfig issue is bug 1749546"
1754836,2018-04-05 05:06:40 UTC,"OK, let's track this in bug 1749546 unless/until the fix for that proves to not help with this one."
1754836,2018-04-09 16:33:37 UTC,Yep - checked with image I built for us Saturday morning. Was fixed then.
1754836,2018-04-09 18:09:35 UTC,"The Bluez timeout errors still show up in ~/.xsession-errors at least on hardware without Bluetooth. However, it seems to be harmless."
1754836,2018-04-09 19:50:37 UTC,"On 09/04/18 19:09, Alistair Buxton wrote:

> *** This bug is a duplicate of bug 1749546 ***
>      https://bugs.launchpad.net/bugs/1749546
>
> The Bluez timeout errors still show up in ~/.xsession-errors at least on
> hardware without Bluetooth. However, it seems to be harmless.
>


I don't see it - checked on vm and hardware."
1754836,2018-04-10 01:42:05 UTC,I set up Xubuntu last night just to check this but couldn't find it. I guess I forgot you need a machine _without_ Bluetooth.
1754836,2018-04-10 03:44:19 UTC,It's also worth pointing out that a timeout is probably expected and correct on machines without Bluetooth. So it's just slightly suboptimal design to go logging messages that look like errors when in fact they are expected outcomes.
1754836,2018-11-06 15:59:32 UTC,Similar happens in Linux Mint 19 system with no Bluetooth devices.
1754836,2020-10-23 16:15:56 UTC,"I have no use for Bluetooth, and disable it in 20.04.1 by removing these packages via Synaptic:
bluez
bluez-cups
bluez-obexd
gnome-bluetooth
pulseaudio-module-bluetooth"
1754836,2018-04-09 09:34:41 UTC,"The font cache issue is apparently fixed. Can anyone confirm (with the latest daily image) if this issue still occurs? If so, which image?"
1754836,2018-04-03 21:21:33 UTC,This is a command-line that is useful for manually exercising the org.bluez DBus activiation. It might reproduce the timeout or otherwise give useful clues. Command should be all on one line (ignore Launchpad line wrapping):
1754836,2018-04-04 01:36:09 UTC,As far as the original bug with delayed login goes... it seems that the Bluetooth stuff is a red herring.
1754836,2018-04-03 09:54:22 UTC,"If this bug does not affect Ubuntu directly, this is a list of shared differences that Ubuntu MATE and Xubuntu have with Ubuntu. Hopefully this can help identify where the issue exists."
1754836,2018-03-10 11:42:22 UTC,live session xsession-errors
1754836,2018-03-11 15:20:22 UTC,The same messages are logged on the live image boot.
1754836,2018-03-12 03:06:10 UTC,The 25 second delay is a standard dbus timeout. I assume you're talking about:
1754836,2018-03-13 10:05:13 UTC,"No, we are talking about the errors in xsession-errors.txt:"
1754836,2018-03-13 10:07:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754836,2018-03-13 10:56:09 UTC,This might be related to the undocumented addition of pulseaudio-module-bluetooth to blueman 2.0.5-1
1754836,2018-03-14 17:59:38 UTC,Don't appear to be able to find the appropriate log in Ubuntu - however grepping journalctl there for blue* gives me:
1754836,2018-03-13 10:35:04 UTC,There is more stuff in syslog too. It looks like pulseaudio is trying and failing to start blueman.
1754836,2018-03-24 06:42:31 UTC,Ubuntu Mate - 75 second timeout noted in .xsession-errors
1754836,2018-03-31 11:16:03 UTC,"Turned up the importance for this bug. For a user, a 75-second wait time when they are used to 0-10 would be an indication there is a serious bug and the software (Xubuntu, Ubuntu MATE, and anything else yet unidentified) does not run on their system."
1754836,2018-03-31 13:49:16 UTC,"On the current daily ISO this now hangs for 50 seconds instead of 75, and the blueman/bluetooth messages are completely gone from xsession-errors."
1754836,2018-03-31 14:36:27 UTC,"Since this only happens on first login, I ran a diff on the full home directory before/after login:"
1754836,2018-03-31 14:54:40 UTC,I tried to log in over ssh and run top so I could watch which processes were running but this caused the delay to disappear.
1754836,2018-04-01 06:24:20 UTC,Daily 1st April:
1754836,2018-04-03 09:18:41 UTC,"Since it seemed like this issue was coming from bluez or blueman, I did some package removal tests and was surprised by the results. These were done in order, which all packages removed in the previous step still removed in the following step."
1754836,2018-03-18 07:05:38 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1754836,2018-04-03 20:47:22 UTC,"The Dbus bluze system config doesn't run, it has ""Exec=/bin/false"" -- /usr/share/dbus-1/system-services/org.bluez.service It's left to systemd to activate it via /lib/systemd/system/bluetooth.service"
1754837,2018-03-10 14:22:10 UTC,"> Mar 10 11:56:00 konki-ThinkPad-T520 udev-configure-printer:
> Device vendor/product is 03F0:2B17
"
1754837,2018-03-10 18:07:22 UTC,After installing previous version of hplip everything went fine and it has dicovered the HP priter without any problems.
1754837,2018-03-10 18:43:00 UTC,"> After installing previous version of hplip everything went
> fine and it has dicovered the HP priter without any problems.
"
1754855,2018-05-27 22:50:19 UTC,"After a lot of investigation, it seems this is caused by Compiz' default Edge Flipping binding to the top of the screen under Desktop Wall -> Bindings -> Edge Flipping. Changing Top to None resolves this."
1754855,2018-06-01 06:23:05 UTC,"Hi Alex,"
1754855,2018-05-28 08:48:54 UTC,Thank you Matt for the investigation. Do you consider the issue as resolved ?
1754855,2018-03-19 08:44:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754855,2018-03-10 15:02:49 UTC,Tried a couple things in CompizConfig Settings Manager -
1754855,2018-03-10 14:47:11 UTC,"Sorry, no coffee yet this morning. This is on latest daily build of Ubuntu MATE 18.04, all packages updated 2018-03-10."
1754855,2018-03-10 14:43:36 UTC,Errata - title: Top pixel *row* of menu items
1754855,2018-05-26 07:55:58 UTC,"This also affects XFCE - if Compiz is installed and used as WM, the top line of pixels don't roll over on top panel items (menus specifically)."
1754859,2018-03-10 16:10:35 UTC,"StacktraceTop:
 JS_GetClass (obj=0x0) at ./js/src/jsapi.cpp:1663
 gjs_error_from_gerror (context=context@entry=0x55a04a544c90, gerror=gerror@entry=0x55a04a7d3630, add_stack=add_stack@entry=true) at gi/gerror.cpp:498
 gjs_throw_g_error (context=context@entry=0x55a04a544c90, error=0x55a04a7d3630) at gjs/jsapi-util-error.cpp:200
 import_module_init (module_obj=..., file=0x55a04a7ba420, context=0x55a04a544c90) at gjs/importer.cpp:310
 load_module_init (context=context@entry=0x55a04a544c90, in_object=in_object@entry=..., full_path=full_path@entry=0x55a04a802320 ""/home/sven/.local/share/flatpak/exports/share/gjs-1.0/__init__.js"") at gjs/importer.cpp:353"
1754861,2018-11-16 01:43:43 UTC,"Had the same experience.  Though it wasn't difficult to find instructions to change the console font, it would have been nice if an appropriate font had been chosen automatically during install."
1754872,2018-08-21 10:00:03 UTC,There is no correct behavior here.
1754872,2018-08-22 14:44:36 UTC,"Julian, thanks for the detailed comment."
1754872,2018-10-14 12:42:45 UTC,"Can the order be changed so that xubuntu-desktop depends on lightdm-gtk-greeter, lightdm? The dependencies are listed in alphabetical order, but that may be not a requirement."
1754872,2018-10-14 14:31:34 UTC,Bug exists in Cosmic. Please fix dependencies.
1754872,2018-10-14 16:33:29 UTC,"Norbert, please be respectful of other Ubuntu projects even if you don't want to use them yourself."
1754872,2018-10-20 21:23:29 UTC,"Debian's xfce4-session package only recommends light-locker, so my suggestion in comment #26 would be an acceptable solution."
1754872,2019-02-26 02:41:16 UTC,This bug was fixed in the package xfce4-session - 4.12.1-6ubuntu1
1754872,2019-08-31 18:52:45 UTC,My experience is that installing 'apt-get install xubuntu-desktop' doesn't produce the desired results as it pulls in recommends that will pull in the extra items listed above in #32 for the reasons explained in #25.
1754872,2019-02-26 22:49:31 UTC,"No changes were made to xubuntu-core and xubuntu-desktop yet, so the bug is obviously not fixed yet. However, the part regarding xfce4-session was fixed (should not pull in xscreensaver anymore)."
1754872,2019-08-31 20:25:30 UTC,"Use tasksel to install the task, it's what it's there for."
1754872,2019-08-31 20:58:32 UTC,Are these tasks up-to-date and maintained by Ubuntu?  Who knows. I never even heard about tasks and tasksel until well after the abysmal experience of trying to install the xubuntu-desktop package.
1754872,2019-09-01 08:16:21 UTC,"There are subtle differences between how the meta package is installed and how tasks are installed, even if the meta package installs all task packages."
1754872,2019-10-26 13:45:41 UTC,"I've added this to the 20.04 development blueprint, so let's revisit and discuss. If we can't solve the problem with packaging, let's document the mini.iso installation process so others have an easier time."
1754872,2019-11-03 18:44:33 UTC,"Assigned this issue to xubuntu-docs. Let's document the correct way to handle the installation of the xubuntu-desktop package, and make it easy for users to find (and forums to point to) when these questions arise in the future."
1754872,2018-08-18 17:05:46 UTC,"Raphael, your comment does not appear to be related to this bug report."
1754872,2019-02-26 21:18:00 UTC,Bug still exists. Simple installation of Xubuntu Desktop on top of 19.04 (disco) mini.iso with `sudo apt install xubuntu-desktop` results in long list of unwanted GNOME packages.
1754872,2018-08-18 11:44:51 UTC,"On Sat, 2018-08-18 at 08:34 +0000, Theo Linkspfeifer wrote:

> Explicitly installing light-locker will remove xscreensaver from the
> list.
>
> It looks like there are quite some oddities.
>


Yes, as I discovered later there is a problem in a bad interaction
between lightdm and xscreensaver."
1754872,2018-05-21 00:19:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754872,2018-08-18 08:34:36 UTC,Explicitly installing light-locker will remove xscreensaver from the list.
1754872,2018-03-11 09:09:57 UTC,"@Timur
I can't confirm this behavior on Ubuntu 18.04 LTS with MATE DE (installed from [mini.iso](http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso) as `ubuntu-mate-desktop` package).
I do not have `gnome-control-center` executable in such system. I'll test official [beta-1](http://cdimage.ubuntu.com/ubuntu-mate/releases/18.04/beta-1/ubuntu-mate-18.04-beta1-desktop-amd64.iso) and report again."
1754872,2018-03-11 09:15:56 UTC,But if I manually install `gnome-control-center` with `sudo apt-get install gnome-control-center` to set Online Accounts I can't did so. `gnome-control-center online-accounts` opens empty window.
1754872,2018-03-11 09:34:46 UTC,I moved MATE part to new bug report - [bug 1754942](https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1754942) - please subscribe and comment here about MATE problems. Finally I confirm the problem which you discovered.
1754872,2018-03-14 02:49:20 UTC,"This does not affect a base install of Xubuntu, but one that is shared with other installed sessions that pull in the GNOME Control Center and the Date Time Indicator."
1754872,2018-03-14 11:27:42 UTC,Dear Sean!
1754872,2018-03-14 13:07:20 UTC,Just tested clean installation of Xubuntu. It does not affected by this bug.
1754872,2018-04-01 18:09:09 UTC,Dear Sean!
1754872,2018-04-01 18:50:05 UTC,Hello Norbert
1754872,2018-04-01 19:16:49 UTC,@dino99
1754872,2018-04-06 21:16:06 UTC,Still happens after installation of `xubuntu-desktop` from beta2 netboot.iso.
1754872,2018-04-19 11:06:12 UTC,"I just tried using the netboot iso and installed the Xubuntu Desktop task. Once installation finished and rebooted, I have a pristine Xubuntu desktop with no additional indicators."
1754872,2018-04-19 21:14:41 UTC,Dear Sean!
1754872,2018-03-11 08:28:19 UTC,"I can confirm this behavior. I'm using Ubuntu Mate 18.04 and some Gnome utilities like gnome-calendar or gnome-weather. In gnome-calendar I wanted to add a Google account, but there's no way do do it, because it opens the gnome-control-center and shows a blank window."
1754872,2018-05-21 00:20:14 UTC,Same problem here - I installed from early beta and used the same method of installing visa tasksel!
1754872,2018-08-17 22:57:42 UTC,"xubuntu-desktop depends on lightdm-gtk-greeter, and yet while performing the test case apt wants to pull in unity-greeter instead (see `apt depends lightdm`). This will install various indicator- packages plus gnome-control-center."
1754872,2018-03-11 08:31:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754872,2018-08-18 08:48:05 UTC,Add a caret to the package name to replicate what tasksel does:
1754884,2018-03-13 10:52:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754884,2018-03-10 19:54:11 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f455de72b9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f455de74800 ""free(): invalid next size (fast)"") at malloc.c:5350
 _int_free (have_lock=0, p=0x55c659dd81a0, av=0x7f455e0a7c40 <main_arena>) at malloc.c:4213
 __GI___libc_free (mem=0x55c659dd81b0) at malloc.c:3124
 CRYPTO_free (str=0x55c659dd81b0) at mem.c:434"
1754886,2020-05-24 21:54:53 UTC,"Hello, I'm having the same issue on my Jetson Xavier, with the following code:"
1754886,2019-06-06 03:14:49 UTC,"Hi,
Has the problem been solved?"
1754886,2019-06-09 04:14:38 UTC,eclipse (Debian) is not fixed. The status is misleading.
1754886,2019-06-09 04:26:56 UTC,This is the workaround:
1754886,2019-06-09 04:37:20 UTC,"Sorry, update on the workaround steps:"
1754886,2019-06-18 23:11:10 UTC,@ pintubigfoot:
1754886,2019-06-22 13:37:02 UTC,@jasepow
1754886,2019-05-28 18:43:41 UTC,"Hello guys
Bukenya Lukman here
I recently upgraded to ubuntu 18.04 and wanted to continue with my java game projects using eclipse as the IDE but it cant start. Below is the error it gives me. I have spent three days googling and it has failed."
1754886,2019-07-21 13:50:27 UTC,@pinubigfoot #30
1754886,2019-08-05 10:01:29 UTC,"to  pintubigfoot (pintubigfoot)
help me out
my log file .....
!SESSION 2019-08-06 15:31:39.930 -----------------------------------------------
eclipse.buildId=debbuild
java.version=11.0.4
java.vendor=Ubuntu
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_IN
Command-line arguments:  -os linux -ws gtk -arch x86_64"
1754886,2019-08-25 09:39:47 UTC,@jouharc
1754886,2019-11-08 16:05:13 UTC,"Helo¡¡¡
The answer #30 worked for me.
Ubuntu Linux XXX 4.15.0-66-generic # 75-Ubuntu SMP Tue Oct 1 05:22:52 UTC 2019 i686 i686 i686 GNU / Linux"
1754886,2019-11-08 16:05:24 UTC,aa Thanks¡¡¡¡
1754886,2019-11-10 14:40:59 UTC,"@pinubigfoot #30
@pinubigfoot #34"
1754886,2020-04-21 14:31:57 UTC,"I just tried to apt-install eclipse on my Linux Mint 19.1 machine, and ran into this problem.  The workaround in comment #30 did the trick, but I have to say I agree with @lucasarnaud79: this situation is unacceptable.  Managing dependencies is the package maintainer's job, not the user's.  The latest update on this thread says ""Fix Released"", but the problem still seems to be occurring."
1754886,2020-05-06 22:35:40 UTC,"I'm sorry, I made a mistake.
This status is incorrect."
1754886,2019-07-30 12:24:59 UTC,to #26 pintubigfoot (pintubigfoot)
1754886,2019-05-05 08:00:33 UTC,Is the issue now fixed? I have the same problem after new installation of ubuntu 18.04
1754886,2019-06-09 15:16:35 UTC,To #23 zhuzhizhan (zhuzhizhan)
1754886,2019-03-31 08:39:11 UTC,I also encounter this problem: here is the log created when i failed to start eclipse:
1754886,2018-03-11 09:35:32 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1754886,2018-05-18 08:01:51 UTC,"Have the same problem.
Seems root cause is a broken dependcy:"
1754886,2018-05-23 10:20:20 UTC,Is there a workaround for this ?
1754886,2018-06-17 08:49:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754886,2018-06-25 19:48:08 UTC,Based on duplicate bug 1777421 it seems the underlying cause might be that the package org.eclipse.core.runtime.adaptor is not installed into /usr/share/eclipse/plugins/.
1754886,2018-07-02 14:37:59 UTC,"Let's summarize the situation!
Yesterday I was happy to pass from Kubuntu 14.04 -where everything were fine- to Kubuntu 18.04. Today I tried to simply access to another windows desktop. Impossible! Because of 'too much security'! I set up MySQL workbench with MySQL server, with the Workbench client I tried to access to mysql server -port 3306-  impossible yet!
I tried to set up Amule, just for the fun, KAD is blocked!
I tried to set up and launch Netbeans, bad idea! It did not work! Netbeans failed to launch. After I set up Eclipse, and I tried to launch Eclipse I retrieved this kind of  beautiful message 'An Error has occured....! etc...' the same message shown above. I foresaw to install Weblogic and Websphere, but ...it seems to be a bad idea, regarding my ""Hot"" experience since yesterday! What the hell did U do ? Is Kubuntu 18.04 be an O/S ?
Why didn't you warn us that Kubuntu 18.04 is only made for connecting funny smartphones, and tablets with Desktops ? But mostly not for other things!"
1754886,2018-08-02 19:16:04 UTC,Also affecting me. Are there any updates on when a fix for this might be released?
1754886,2018-08-02 20:26:48 UTC,I don't understand how things as critical as this are not being fixed immediately?  Netbeans also fails to start.  This is a java problem in both cases.
1754886,2018-07-04 22:21:36 UTC,"ME TOO:
bash $ uname -a
Linux BiskitHome.ri.cox.net 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
superbiskit@BiskitHome:~
bash $ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION=""Ubuntu 18.04 LTS""
NAME=""Ubuntu""
VERSION=""18.04 LTS (Bionic Beaver)""
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=""Ubuntu 18.04 LTS""
VERSION_ID=""18.04""
HOME_URL=""https://www.ubuntu.com/""
SUPPORT_URL=""https://help.ubuntu.com/""
BUG_REPORT_URL=""https://bugs.launchpad.net/ubuntu/""
PRIVACY_POLICY_URL=""https://www.ubuntu.com/legal/terms-and-policies/privacy-policy""
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
superbiskit@BiskitHome:~"
1754886,2018-08-15 21:22:41 UTC,"Silly me! There is a simple work around:
​apt-get purge eclipse ; ​apt autoremove
Download Eclipse Installer on https://eclipse.org/downloads and install it as non root.
My apologizes."
1754886,2018-08-19 12:04:31 UTC,See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891956#47 for the reasons behind why this is not being fixed
1754886,2018-08-23 13:28:59 UTC,On Raspberry-Pi and Ubuntu 18.04 LTS no simple work around for me here. Only work around on Pi is to use the Rasbian interface. So this should be a critical bug for 18.04 LTS.
1754886,2018-08-27 14:31:13 UTC,"I guess you guys need explicitly Eclipse 3.8 . Just go to Ubuntu-Software, deinstall 3.8 and install Eclipse 4.8 (Photon) which is the default package on the Ubuntu-Software."
1754886,2018-08-27 16:55:41 UTC,"Hi Michael,"
1754886,2018-11-14 17:34:41 UTC,eclipse still doesn't start on Ubuntu 18.04 all patches applied.
1754886,2018-12-13 12:52:32 UTC,Another month and still no fix... when will this be fixed?
1754886,2018-12-17 07:40:42 UTC,The workarround purposed by Jef (e70838) at answer #11 works for me.
1754886,2018-08-15 20:21:57 UTC,"Sorry to be another metoo, but the purpose of 18.04.1 LTS is to ensure this does not happen. The problem has been found in march, we are in august.
I use my computer for java development using eclipse. This issue is not even mentioned on https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes."
1754886,2019-04-05 01:59:54 UTC,Same problem here ubuntu 18.04:
1754898,2020-09-22 11:35:08 UTC,All non-blacklisted packages in main now import successfully.
1754898,2018-03-16 21:42:59 UTC,"Additionally, ecj also failed at 10% phasing of main."
1754898,2018-03-17 03:49:16 UTC,lxml also affected
1754898,2018-03-22 01:09:31 UTC,"ecj
libffi
lxml
oxide-qt
reiser4progs"
1754898,2018-03-27 23:35:20 UTC,"I don't believe 20% had anything further, after blacklisting the two
large packages"
1754898,2018-05-24 11:00:50 UTC,"I'm going to convert this bug into tracking package import failures that have yet to be triaged. Once individual root causes are identified, we should have separate bugs for each root cause import failure instead. Then this bug can be resolved when there are no import failures whose root cause is not covered by another bug."
1754901,2021-02-08 14:22:25 UTC,I should have closed this a while back - its definitely resolved in focal.
1754909,2018-03-11 01:30:38 UTC,apport information
1754909,2018-03-11 01:30:39 UTC,apport information
1754909,2018-03-11 01:30:40 UTC,apport information
1754909,2018-07-01 01:23:12 UTC,"Experiencing same issue in 17.10 and 18.04 upgrade.  Reinstalled 18.04 fresh, still occurring."
1754909,2018-07-02 13:01:52 UTC,"The easiest workaround seems to be to use the slic3r-prusa package rather than the slic3r package. This changes the Slic3r version to be Prusa's fork, which might or might not be your preference; but at least the slic3r-prusa version's display works as expected. Note that the binary name changes from slic3r to slic3r-prusa3d with the package change, too."
1754909,2018-03-11 01:30:36 UTC,apport information
1754913,2018-03-20 05:58:45 UTC,4. Kernel v4.16-rc6 works well.
1754913,2018-03-20 05:43:35 UTC,"1. ""Recovery Mode"" from the GRUB menu is working good.
2. ""GRUB_GFXPAYLOAD_LINUX=text"" is working good.
3. ""GRUB_TERMINAL=console"" is working good."
1754913,2018-03-13 05:44:13 UTC,Dupe of lp: #1724639?
1754913,2018-06-27 22:15:21 UTC,"Same issue with Gateway LT20 Netbook (Intel 945GM chipset and 1024x600 display) running Xubuntu 16.04
Problem began with latest update to Linux 4.13.0-45-generic kernel.
Using recovery mode barely usable but stretches 800x600 across the display.
Booting with 4.10.0-42-generic eliminates the problem."
1754913,2018-03-12 13:15:18 UTC,"Can you boot if you select ""Recovery Mode"" from the GRUB menu?  You can get to the GRUB menu by holding the SHIFT key after poweron and seeing the BIOS screen."
1754913,2018-03-11 03:31:49 UTC,"Due to broken screen, I cannot do that 'apport' thing."
1754913,2018-03-11 03:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1754913,2018-03-12 13:15:33 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1754931,2018-03-12 11:04:58 UTC,"btw, just to clarify some more.
I don't need to restart the plank for any reason.
by trying to restart the plank, I am just demonstrating the issue that I face every time I restart my computer.
the original issue is, the lock setting doesn't stay put every time I restart my computer."
1754935,2018-03-11 12:22:01 UTC,"Hello, please try and find the exact syntax to cause the crash so that there is a reliable way for the developers to reproduce this bug."
1754935,2018-03-11 14:52:19 UTC,"I can reliably reproduce this by
- starting mate-calc
- typing in 8*8
- press enter
- display shows 64
- on the calculator keyboard click: x2, square root sign
- press enter
- crash"
1754935,2018-03-11 15:01:26 UTC,"Please see: https://bugs.launchpad.net/ubuntu/+source/mate-calc/+bug/1754972, which contains the crash report that was produced when I reproduced above sequence."
1754935,2018-03-11 15:17:43 UTC,"I can't access this link but Monsta might be able to.
I can't immediately reproduce the bug using the sequence you've described on a Ubuntu MATE 18.04 Beta install in a VM.
How did you install mate-calc? (Did you install the whole mate-desktop?)"
1754935,2018-03-11 15:20:08 UTC,"Wait, nevermind my previous. I missed the ""square root sign"" part or your steps.
Now that I have corrected this, I can indeed reproduce your crash.
This also affects Artful."
1754935,2018-03-11 16:04:20 UTC,"Just to be clear: I did not install mate-calc. It's part of the distro I am testing at the moment: Xubuntu 18.04. Should I warn the people over there as well? Or is that not necessary? (Sorry for asking, but I'm quite new to all this.)"
1754935,2018-03-14 21:34:20 UTC,Perhaps it's helpful to mention: a shorter sequence of actions does also lead to a crash:
1754938,2019-10-20 13:07:52 UTC,"It's a pity this bug was not filed with the 'requestsync' tool, for future reference:
https://wiki.ubuntu.com/SyncRequestProcess"
1754938,2019-12-20 04:17:23 UTC,[Expired for python-meshio (Ubuntu) because there has been no activity for 60 days.]
1754941,2018-03-19 18:52:38 UTC,"HPLIP 3.18.3
Ubuntu 16.04.1
Kernel: 4.13.0-37-generic"
1754941,2018-03-14 10:47:30 UTC,looks like it's already there:
1754941,2018-03-14 10:12:17 UTC,"Hi Praesepe,"
1754948,2020-10-19 21:09:07 UTC,"Hi,"
1754949,2018-08-23 13:31:17 UTC,This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
1754949,2018-08-13 15:43:01 UTC,"Hello Ferdinand, or anyone else affected,"
1754949,2018-08-08 08:04:36 UTC,"The drm_mode_get_hv_timing() function (used in the required kernel commit) depends on a non trivial amount of other changes, and I don't think a backport would be easy, or safe. That commit will be available in Linux 4.17, though, so we are going to get the fix in Ubuntu 18.10."
1754949,2018-08-01 01:37:37 UTC,This bug was fixed in the package mutter - 3.28.3-2
1754949,2018-07-27 13:20:34 UTC,"Fix is in salsa now, will be in ubuntu at next sync."
1754949,2018-07-27 01:51:12 UTC,"And so is ""meta_gpu_kms""."
1754949,2018-07-26 15:20:46 UTC,"I haven't seen this crash, since I disabled Wayland in /etc/gdm3/custom.conf:"
1754949,2018-07-27 01:50:47 UTC,"That's correct. Because the ""meta_renderer_native"" part is Wayland-only :)"
1754949,2018-07-18 07:08:31 UTC,Bump. This is the 3rd most common gnome-shell crash right now.
1754949,2018-04-25 09:14:55 UTC,The driver involved should be also be fixed including this:
1754949,2018-03-27 08:21:53 UTC,"Looks similar to:
https://errors.ubuntu.com/problem/b0adc3c02c0ba6f5e7fafd72721ff0050a8a88f4"
1754949,2018-03-27 08:06:08 UTC,Also tracking in https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665
1754949,2018-03-15 02:05:34 UTC,"Upstream bug report:
https://gitlab.gnome.org/GNOME/mutter/issues/70"
1754949,2018-03-15 02:01:52 UTC,The crash occurs on this line of code:
1754949,2018-03-14 15:48:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1754949,2018-03-11 10:47:46 UTC,"StacktraceTop:
 meta_gpu_kms_apply_crtc_mode (gpu_kms=gpu_kms@entry=0x55bbde3ca4b0, crtc=0x7f3fcc053480, x=x@entry=0, y=y@entry=0, fb_id=fb_id@entry=0) at backends/native/meta-gpu-kms.c:143
 meta_renderer_native_finish_frame (renderer_native=0x55bbde3e01f0) at backends/native/meta-renderer-native.c:2848
 clutter_stage_cogl_redraw (stage_window=0x55bbde6b1560) at cogl/clutter-stage-cogl.c:871
 clutter_stage_do_redraw (stage=0x55bbde6b0d20) at clutter-stage.c:1121
 _clutter_stage_do_update (stage=0x55bbde6b0d20) at clutter-stage.c:1236"
1754949,2018-07-25 01:46:42 UTC,"Temporarily reopening the gnome-shell task, just so people can find the bug. And are less likely to create more duplicates."
1754966,2018-03-11 16:24:25 UTC,"Hi James,"
1754966,2018-03-17 09:49:27 UTC,You should attach here the OpenRailsLog.txt file you get on the desktop (the one you get after a crash). It might contain useful infos about your problem.
1754968,2018-03-14 12:22:44 UTC,No that did not show when running it from the console.
1754968,2018-03-14 06:28:09 UTC,"Hi Jorge,"
1754968,2018-03-13 12:47:04 UTC,"I believe I already did that on my firsr comment, but here ir is again:"
1754968,2018-03-12 13:10:45 UTC,"Thanks for the update, here is the info from hp-xhexk -t command, but again, the driver works fine, it's the tray icon the one with the problem:"
1754968,2018-03-12 12:47:57 UTC,"Hi Jorge,"
1754968,2018-03-11 14:10:53 UTC,This is what it shows from the command line:
1754968,2018-03-13 11:14:29 UTC,"Hi Jorge,"
1754986,2018-03-11 17:18:11 UTC,On advice by Manfred Hample I did
1754986,2018-03-11 18:08:44 UTC,"Just did another run of update-manager.
Started with sudo update-manager.
It ran without any messages in cli, then when the dialogue came up telling me there were updates, I got this in cli:"
1754986,2018-03-11 18:14:47 UTC,The sudoku-message may have been triggered by the fact that sudoku was part of the upgrade
1754986,2018-03-12 18:08:42 UTC,"Did another sudo-update manager run.
Got:"
1754986,2018-03-14 17:40:16 UTC,Did an sudo update-manager from cli again; Whilst in the update-manager I clicked on one of the links which referred me to the bug that was being repaired by the update; firefox did not start immediately; then it did. In cli I then had a load of messages. See attachtment.
1754997,2018-03-11 18:52:27 UTC,See also https://github.com/mixxxdj/mixxx/pull/1529
1754999,2018-03-13 15:08:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755001,2018-12-29 03:40:18 UTC,Its great how motivated and fast the linux-community solves bugs and problems.
1755006,2018-03-16 06:21:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755006,2018-03-16 06:22:19 UTC,1725164 bug page doesn't exist anymore
1755006,2018-04-20 20:36:38 UTC,"Just got this after rebooting.  No idea what's going on here, I have no modems attached to this machine.  I don't believe it is the same as the other bug, as the routine listed as crashing was neither g_closure_invoke() nor the one in the other bug.  I have no idea what it actually _was_; I would have expected that to be attached with my own bug report but it wasn't.  :/"
1755006,2018-03-11 18:13:01 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1725164, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1755035,2018-03-12 14:55:55 UTC,It should be related to the following changes
1755037,2019-04-12 14:39:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755044,2018-03-12 17:54:25 UTC,"From that docs page, https://docs.openstack.org/swift/latest/deployment_guide.html describes config options. Also, the sample config files provided in the source repo (https://github.com/openstack/swift/tree/master/etc) are very well commented and suitable starting points for deployment."
1755049,2019-05-28 21:37:36 UTC,Must be uploaded directly onto the web server by a system administrator.
1755056,2018-10-19 14:12:16 UTC,This issue was fixed in the openstack/openstacksdk 0.18.0 release.
1755056,2018-03-19 03:38:53 UTC,"How? We'd add the new ones, and keep the old ones. Additive changes should be fine."
1755056,2018-03-19 03:25:59 UTC,It will be an API impact change. need micro version support first.
1755056,2018-03-20 08:35:08 UTC,yeah. that's a way to keep backward compatibility.
1755067,2018-06-28 09:21:52 UTC,"I have the same issue, anyone else could give me some suggestions to solve this issue :(?"
1755067,2018-06-29 07:51:19 UTC,"In my case, it can be solved when I try to upgrade my gnocchi server version from tag 4.2.0 to 4.2.5"
1755067,2018-07-18 12:43:39 UTC,"I can also run this command ""sudo docker exec -it gnocchi_metricd gnocchi-upgrade"" to do database migration to solve this issue. Here is my execution log."
1755067,2018-06-28 09:21:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755070,2018-03-12 03:14:11 UTC,This block our testing.
1755070,2018-03-12 05:20:50 UTC,"seems repo works now :).
But still need to update system date to be several hours late. :)"
1755070,2018-03-12 05:27:53 UTC,"This sort of inconsistency shouldn't happen on mirrors which use the recommended 2-stage sync: https://wiki.ubuntu.com/Mirrors/Scripts  Currently cn.archive.ubuntu.com is redirected to us.archive.ubuntu.com, so if the latter works for you, the former should also.  I've just confirmed that I can deploy bionic cloud images and run apt updates on them, so my guess is that you're dealing with a local DNS override or troublesome transparent proxy."
1755072,2020-01-02 17:56:34 UTC,"Hello everyone,"
1755072,2020-01-02 14:12:56 UTC,"The settings dialog is too big with a 1366*768 screen.
I use qpdfview 4.17.99, LXQT 0.14.1, Debian 10 (stable/buster)."
1755094,2018-03-12 08:18:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1755096,2018-03-28 10:34:33 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1755096,2020-09-19 12:38:58 UTC,Still present http://manpages.ubuntu.com/manpages/focal/en/man1/gpg.1.html
1755104,2018-03-12 13:53:14 UTC,"Hi, this is currently supported in the latest release of the charm:
https://jujucharms.com/grafana/9"
1755104,2018-03-12 13:55:24 UTC,"Sorry, I now see that you want to use Juju resources to install apt/snap files, not connect to an apt repo or the snapstore."
1755104,2019-09-13 14:19:34 UTC,Any update on this request as we might need this feature sooner than later for offline deployments.
1755104,2020-03-03 06:35:46 UTC,"Although we have the install_method available for snap, there's no option to include a resource.  We will also need to include the core snap resource in order to allow offline deployments."
1755118,2018-03-12 09:00:08 UTC,This change was made by a bot.
1755118,2018-07-24 09:34:17 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1755119,2019-08-07 15:11:36 UTC,"The chromium snap has been exclusively built from source for a good while.
I just tested again in a bionic VM (X11 and Wayland sessions), and the problem appears to be gone, so I'm closing the bug. Please re-open if you're still seeing this in any configuration."
1755119,2018-08-14 12:19:31 UTC,This appears to be fixed in the latest stable release.
1755119,2018-09-06 16:13:13 UTC,The problem appears to be back (see https://github.com/ubuntu/snapcraft-desktop-helpers/issues/150#issuecomment-418458767). Re-opening.
1755138,2020-07-10 19:14:36 UTC,Thanks for reporting.
1755164,2018-04-09 21:26:10 UTC,This issue was fixed in the openstack/ironic 9.1.4 release.
1755164,2018-03-28 22:33:58 UTC,"Reviewed:  https://review.openstack.org/553330
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=ca4fb9b1cfe2693771e6b0d346d5923db66696e8
Submitter: Zuul
Branch:    stable/pike"
1755164,2018-03-15 11:12:55 UTC,"Change abandoned by Jacek Tomasiak (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/552515
Reason: Closing in favor of: https://review.openstack.org/#/c/553330/"
1755164,2018-03-13 13:40:48 UTC,"Pre-requisite for above change is: https://review.openstack.org/#/c/469627/
Backport requested for Pike: https://review.openstack.org/#/c/552515/"
1755164,2018-03-12 13:37:54 UTC,Possible solution: https://review.openstack.org/#/c/476173/
1755164,2018-03-15 11:11:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/553330"
1755164,2018-03-13 13:38:48 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/552515"
1755173,2018-10-25 18:50:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755174,2018-03-12 14:28:02 UTC,Thank you for your bug report. Could give some extra details on what rhythmbox feature you are using? It should be going through a configured proxy without problem but there might be issues with specific services...
1755174,2018-03-12 15:09:31 UTC,I tried to subscribe an audio podcast under a regular URL.
1755175,2018-03-12 15:17:30 UTC,"We have cards for that, and some work was done, but stopped:
https://trello.com/c/djXJD5TH/488-bootstrapping-nodes-for-multinode-ci-job-investigation
https://trello.com/c/j0uTClOE/475-bootstrapping-multinode-nodes-is-done-with-tripleosh-https-githubcom-openstack-infra-tripleo-ci-blob-2dc251f965b1a6262177e75f2b5"
1755182,2018-05-06 13:34:56 UTC,Also see https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1768199/
1755182,2018-04-18 21:52:10 UTC,Chromium/Chrome has patched this from current 66 betas
1755182,2018-03-29 01:42:06 UTC,"The same happens to me. In addition, when I lock the session and then I log back, the chrome crashes."
1755182,2018-04-08 13:31:08 UTC,"Same issue here, although the stutter only lasts for a few seconds and then everything seems to go back to normal."
1755182,2018-04-08 14:37:08 UTC,Did some more testing and I cannot reproduce the issue using google-chrome-unstable (67.0.3386.1-1)
1755182,2018-04-08 13:06:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755185,2018-03-12 16:20:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1755185,2018-09-20 12:04:44 UTC,I am the same user that registered the bug (No idea which email I used)
1755185,2018-09-20 15:00:47 UTC,"I assigned to `base-files` because I imagine it could be something with /etc/profile /etc/profile.d /etc/environment or so, but it is honestly a shot in the dark. I could not localize it."
1755188,2018-03-14 05:35:29 UTC," https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750937?comments=all
freeze or crush after the later update, but with  Nvidia-related issue"
1755189,2018-03-13 14:45:54 UTC,"Confirmed, and it's still a problem in git upstream even. Looks like not many people use this script, or maybe a more recent perl is enforcing something that it wasn't before."
1755189,2018-09-10 19:29:02 UTC,Still valid.
1755189,2018-09-10 19:41:06 UTC,PR: https://github.com/squid-cache/squid/pull/284
1755189,2019-03-12 13:33:09 UTC,"This is fixed in disco, which ships squid 4."
1755189,2019-03-12 13:37:06 UTC,"Hm, this is complicated to manage in lp. Cosmic has the package ""squid"" (not squid3), and is affected. Disco has ""squid"" but is NOT affected."
1755195,2018-03-19 08:21:03 UTC,"Louie: This patch [1] was merged on 14th March which bumps the openstacksdk version from 0.9.19 to 0.11.2. When we installed latest masakari code using devstack, we are hitting this bug [2] and not the one you are getting."
1755195,2018-03-19 13:42:05 UTC,I see that and the following should address the issue.
1755203,2018-03-12 15:40:34 UTC,"Cyborg, LOCI, Maskari don't yet have TC project tags, thus the reason they're not showing."
1755203,2018-03-12 23:29:19 UTC,Aodh is definitely not visible on https://www.openstack.org/project-mascots/ for me.
1755203,2018-03-15 17:00:52 UTC,"Hey there. Sorry about the confusion. My brain was squarely in the project navigator, which has the aodh logo. I'm working on getting that one up there. Masakari and teh other new projects haven't yet chosen a mascot (or are in the process of doing so). Might be a bit before we get those up as we have to go through the design and approval process."
1755203,2018-03-15 17:58:37 UTC,"Haha, no worries ;-)  Thanks a lot for looking at this, and no rush from my side of course!"
1755205,2018-03-15 10:29:55 UTC,"root cause found but needs to be fixed. Found that somehow a user managed to insert an incorrect security rule, which caused the stack trace. After deleting the faulty row, no more errors in the log files."
1755205,2018-03-19 03:03:23 UTC,"Neutron doesn't set the protocol as a Interger value, it be stored as varchar in db."
1755213,2018-04-04 09:32:32 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1086.94
1755213,2018-03-26 14:28:19 UTC,No derivative specific changes.
1755213,2018-04-04 12:03:02 UTC,The package has been published and the bug is being set to Fix Released
1755213,2018-03-21 10:56:42 UTC,Hardware Certification have begun testing this -proposed kernel.
1755213,2018-03-20 13:54:43 UTC,"No regression found, results here: https://trello.com/c/lTdgut1m/210-pi2-kernel-440-108694-51"
1755213,2018-03-21 11:31:58 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1086.94/raspi2-4.4-proposed-published.html"
1755215,2018-03-20 13:55:33 UTC,"No regressions found, results here: https://trello.com/c/gefu1OOd/209-dragonboard-kernel-440-108893-44"
1755215,2018-03-21 10:57:43 UTC,Hardware Certification have begun testing this -proposed kernel.
1755215,2018-03-21 14:44:05 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1088.93/snapdragon-4.4-proposed-published.html"
1755215,2018-03-26 14:22:19 UTC,No derivative specific changes.
1755215,2018-04-04 09:34:08 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1088.93
1755215,2018-04-04 12:03:24 UTC,The package has been published and the bug is being set to Fix Released
1755215,2018-04-05 08:35:01 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1088.93
1755219,2018-04-04 10:32:34 UTC,The package has been published and the bug is being set to Fix Released
1755219,2018-04-02 17:08:14 UTC,"Issue can be reproduced in the older -1019 kernel, no body check the result before so I will set this as a new baseline for future reference."
1755219,2018-04-04 09:33:39 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1020.25
1755223,2018-03-14 10:53:32 UTC,"I think you meant to say Newton is EOL and not Queens.
Note that we haven't EOLed Newton in TripleO."
1755223,2021-02-17 17:07:00 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1755228,2018-03-23 03:08:00 UTC,"3.13.0-143.192~precise1 - generic
Regression test CMPL."
1755228,2018-03-23 10:29:19 UTC,There is no automated testing for ESM PPA uploads.
1755228,2018-04-03 15:38:43 UTC,Origin kernel passed and no regression known for the backport (and no specific changes for the backport either).
1755228,2018-04-04 10:02:34 UTC,The package has been published and the bug is being set to Fix Released
1755230,2018-03-12 17:57:59 UTC,"StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x5641852ab280) at ../../../../gobject/gtype.c:4131
 g_signal_emit_valist (instance=0x5641852ab280, signal_id=307, detail=0, var_args=var_args@entry=0x7ffc22e843d0) at ../../../../gobject/gsignal.c:3176
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
 g_menu_model_items_changed (model=<optimized out>, position=<optimized out>, removed=<optimized out>, added=<optimized out>) at ../../../../gio/gmenumodel.c:690
 queue_emit_all (queue=queue@entry=0x564184f87920) at ./lib/dbusmenu-importer/model.c:150"
1755230,2018-03-16 09:02:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755230,2019-03-25 14:24:06 UTC,"fresh disco install xubuntu-daily-03-22-2019 iso .. occurs shortly after first login to xfce/xubuntu
while doing updates .. just before they completed .."
1755232,2019-10-17 12:54:51 UTC,this is in eoan
1755232,2018-11-12 22:09:59 UTC,This is fixed in https://gitlab.freedesktop.org/xorg/xserver/commit/35e5a76cc1d02801fadd49d12e60664b02e4bebc
1755232,2018-03-16 14:36:31 UTC,Maybe something similar to what I experience. See https://bugs.freedesktop.org/show_bug.cgi?id=105557
1755232,2018-03-13 08:24:00 UTC,"I tried adding critical section to DeactivatePointerGrab. Xorg was working, including multitouch.
 After some time, when I touched the screen (single finger) it deadlocked. So it really looks like a multithreading issue."
1755232,2018-03-20 16:06:09 UTC,"@jnavila: It looks like it could be related, but I couldn't reproduce your crash (or at least I think so). With context menu opened in chrome I tried tapping on the window border, Unity bar and system tray - both when Chrome was maximized and when it wasn't. No crash. Should I do something else?"
1755236,2018-03-12 16:44:23 UTC,Quoting the large number fixes it
1755236,2018-03-12 18:24:35 UTC,"Ok so this is a jq bug:
# echo '{""id"" : 1241000000}' | jq '.'
{
  ""id"": 1.241e+09
}"
1755236,2019-07-08 14:30:15 UTC,The JSON Query (jq) bug is still present and outside of TripleO's control.
1755236,2021-02-17 17:10:18 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1755247,2018-03-15 22:29:26 UTC,"I'm working on this as part of the base importer tests, which are currently gated on some test infra. I have the code written, just need to add the corresponding tests."
1755247,2020-03-24 12:58:51 UTC,I think we'll be able to call this completely done when my current in-progress branch lands (based on Nish's branch).
1755247,2020-09-28 12:01:37 UTC,Fix released in git-ubuntu version 1.0
1755249,2018-03-12 17:43:35 UTC,Web Client screen shot attached...
1755256,2019-06-21 08:00:48 UTC,"Hi, can you check which version of XQuartz are you using? Thank you!"
1755256,2019-09-19 12:11:49 UTC,"Closing as there has been no activity for 60 days. If you still have this problem, check the already reported issues at https://inkscape.org/report. Thank you!"
1755258,2018-09-05 21:57:43 UTC,"Works for me, and pushed to master for inclusion in 3.2-beta.  I've added targets for 3.0 and 3.1 but am not backporting for the moment pending dealing with the OpenSRF patch."
1755258,2018-06-12 16:19:42 UTC,Opened OpenSRF bug #1776510
1755258,2018-06-12 16:05:24 UTC,Fix pushed:
1755258,2018-05-29 15:23:10 UTC,Noting that at present the web staff client is simply not checking whether the auth_proxy is active or attempting to use open-ils.auth_proxy.login.  Following the example in Open-ILS/xul/staff_client/chrome/content/auth/session.js or Open-ILS/src/perlmods/lib/OpenILS/WWW/EGCatLoader.pm would serve to add it.
1755258,2018-06-12 16:06:55 UTC,"Because of the caveat noted in my last comment, I'm going to target this bug to 3.2 beta only for now, since back-porting it could cause breakage for sites not running the auth_proxy service."
1755259,2020-01-07 18:21:09 UTC,"- The project page, when you click on ""code"", has a link to the activereviews page of the project (on https://code.launchpad.net/launchpad, search for ""Launchpad itself has XX active reviews."""
1755259,2020-01-08 11:49:00 UTC,Ah - it looks like we missed that this bug is a duplicate of bug 1789847.
1755259,2020-01-09 13:18:45 UTC,Thanks for the help! I'll check that bug and see what can be improved in terms of performance there.
1755266,2019-06-07 16:05:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/663986"
1755266,2020-05-11 13:42:28 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/663986"
1755266,2020-05-11 13:42:21 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/618621"
1755266,2019-06-14 16:54:50 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/663986"
1755266,2018-11-17 16:33:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/618621"
1755266,2018-03-22 12:21:34 UTC,"Hi Matt,"
1755266,2018-06-29 17:51:36 UTC,"Matt, do you need a pull request and gerrit to consider a fix for this?"
1755266,2018-03-28 15:18:17 UTC,"Here another suggestion for a fix:
As the last element for a fully working solution for my config, I extended the libvirt driver code in driver.py to make the lvm based swap volume deleted when the instance has been moved to the new host successfully:"
1755266,2018-03-25 11:16:40 UTC,"Correction for code analysis of driver.py, 8024ff:"
1755266,2018-03-21 22:07:24 UTC,"I'm a bit confused about the 'swap volume' terminology here. As far as I know, swap disks are never stored as cinder volumes, they are ephemeral storage on the local compute host, as noted here:"
1755266,2018-07-24 10:11:57 UTC,Could someone of the Nova team please comment how to proceed with that topic.
1755268,2018-03-12 23:57:56 UTC,I'm tried to use simple modules loading instead /etc/init.d/openibd script:
1755268,2018-03-16 11:50:37 UTC,"I was teted right now, the problem occurs also on stock kernel."
1755268,2018-03-16 12:00:06 UTC,This change was made by a bot.
1755268,2018-03-19 14:19:13 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1755268,2018-03-19 16:51:28 UTC,"Hi Joseph, thanks for your answer."
1755268,2018-03-20 12:40:10 UTC,"Hi, I can't build new mellanox drivers for new kernel, so I used default one:"
1755268,2018-03-20 13:07:21 UTC,"Additional I've also tested latest hwe kernel (4.13.0-37-generic) and build-in driver, the same problem here:"
1755268,2018-03-20 15:44:15 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1755268,2018-03-20 21:32:09 UTC,"OK, this is my meesage that I wrote to kernel's netdev list:
https://<email address hidden>/msg223827.html"
1755268,2018-07-24 09:32:15 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1755276,2018-03-13 17:11:16 UTC,"Tested on debian jessie on x64 - same thing, so this isn't raspbian specific. Now, starting it with the following options actually work."
1755276,2018-03-13 18:00:18 UTC,"It doesn't seem much has changed on x11vnc since jessie (where it works), though. Jessie runs 0.9.13-1.2, whereas Stretch runs 0.9.13-2, so if someone knows what's happened between the two, perhaps it could help. The project is still somewhat active, but not a lot, and the versions in both jessie stretch are both flagged with ""lastmode: 2011-08-10"", which is a while ago…"
1755279,2018-05-23 09:10:29 UTC,"Hi, I have tried this bug and git the error like"
1755280,2018-03-25 19:54:29 UTC,Is it reported before?
1755280,2018-03-24 21:33:49 UTC,this is very old bug
1755285,2018-03-16 08:21:13 UTC,GPG2 support added in keychain 2.8.4 so package must be updated.
1755289,2018-03-12 21:42:18 UTC,"Here's a first draft of the change, hopefully I haven't made too much a mess of the ASCIDoc.
http://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/jboyer/lp1755289-serialize-instructions"
1755289,2018-03-13 14:12:17 UTC,"Jason, these changes look good to me.  When you're done, I'll happily sign off, merge, and deploy to evergreen-ils.org."
1755289,2018-03-13 15:53:38 UTC,"I really just needed another set of eyes on it, so if you think it looks good I'm happy to call it done!"
1755289,2018-03-13 16:06:56 UTC,"Signed off, merged to Hatch master, and deployed:"
1755305,2020-07-29 15:53:31 UTC,seems the same issue than bug #1853331 and should be fixed now in groovy
1755305,2020-07-10 07:49:21 UTC,My apologies for the fudged linebreak in the previous comment.
1755305,2020-07-10 05:19:34 UTC,"According to upstream, this is self-inflicted pain in Ubuntu:"
1755305,2020-04-27 13:04:49 UTC,"Hi, is there any updates for this? I see this issue in xubuntu 20.04 (and previously 19.10). It clogs up the .xsessions-errors file periodically until I run out of disk space. A temporary fix is to write a cron job to empty this file if it exceeds some threshold"
1755305,2019-04-11 05:43:45 UTC,Any movement on this? I'm getting the same issue with gnome flashback with ubuntu 18.04 with latest updates.
1755305,2018-11-30 16:13:50 UTC,"18.04.1 LTS (Bionic Beaver) 64-bit
Confirm"
1755305,2018-11-08 11:18:13 UTC,Upstream issue: https://gitlab.gnome.org/GNOME/network-manager-applet/issues/34
1755305,2020-06-03 06:53:02 UTC,Example of errors:
1755305,2018-10-24 12:56:18 UTC,"However, it this particular issue still present in 18.04 or 18.10?"
1755305,2018-10-24 21:45:16 UTC,"I can confirm the issue is still there on 18.04 as I am currently running 18.04.1 LTS (Bionic Beaver) 64-bit. I do not use 18.10, so I comment on that."
1755305,2018-04-15 13:31:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755305,2018-06-15 06:10:23 UTC,"I can understand how this may seem like nothing of concern to the devs / maintainers, but when you end up with log files of 15-20MB, and nearly all of it is due to this, it is problemsome. There is no need to see this a handful of times each minute as it just interferes with the actual intention of the xsession-errors file."
1755305,2018-10-13 16:37:07 UTC,Please report it to upstream.
1755305,2020-06-03 06:52:28 UTC,"I am encountering the same issue in 20.04. The message is repeating approximately every three seconds, resulting in log files of hundreds of gigabytes. It also makes the system log nearly useless for any other use; it is near-impossible to even open the file, and causes logrotate to hang up for hours every time it attempts to run since it attempts compression."
1755305,2018-10-22 15:36:47 UTC,This kind of message floods the .xsession-errors file:
1755305,2018-10-22 17:05:42 UTC,"@ Claudiux (claudiux) - If your comment was for me, I know the issue. I should be more clear, I do not know what this means, or how to do it:"
1755305,2018-10-24 12:53:44 UTC,https://en.wikipedia.org/wiki/Upstream_(software_development)
1755305,2018-10-14 15:05:53 UTC,I do not know what that means.
1755307,2018-03-14 14:11:52 UTC,"Hi,
the mainline kernel v4.4.121 works fine.
Please note, that with the installation of the hwe-16.04 kernel, also xserver was updated to 1.19, so I can not say anything about the combination of kernel v4.4.121 with the original xserver."
1755307,2018-03-13 15:42:51 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1755307,2018-03-12 23:51:06 UTC,apport information
1755307,2018-03-12 23:51:04 UTC,apport information
1755307,2018-03-12 23:51:01 UTC,apport information
1755307,2018-03-12 23:51:00 UTC,apport information
1755307,2018-03-12 23:50:59 UTC,apport information
1755307,2018-03-12 23:50:58 UTC,apport information
1755307,2018-03-12 23:50:56 UTC,apport information
1755307,2018-03-12 23:50:55 UTC,apport information
1755307,2018-03-12 23:50:54 UTC,apport information
1755307,2018-03-12 23:50:52 UTC,apport information
1755307,2018-03-12 23:50:50 UTC,apport information
1755307,2018-03-12 23:50:49 UTC,apport information
1755307,2018-03-12 23:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1755307,2018-03-12 23:50:57 UTC,apport information
1755307,2018-03-12 23:50:53 UTC,apport information
1755309,2018-08-18 04:00:49 UTC,"The comment on the pin_eld_notify got fixed (sometime before 4.4.0-130), removing the pipe reference, and enumerating the two valid arguments, but the actual ""pipe"" argument was left."
1755309,2019-02-06 05:02:59 UTC,"Someone grabbed a release candidate for this file, and didn't notice it had changed before the final.
Look at the kernel source in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/include/drm/i915_component.h?h=v4.4.172 for what the original file should be.  The pipe argument did not appear again until 5 or 6 kernel releases later.  Please fix this before the end-of-support date in April 2019.  This error killed the HDMI audio for the Intel Compute Stick STCK1A8LFC when the Intel supplied 4.4 kernel update script is run."
1755312,2018-03-12 23:06:00 UTC,Prior Bug Reported as #517440
1755312,2018-03-15 14:10:13 UTC,"This issue is becoming more than a nuisance.  On 03/14/18 no less than 6 reboots were required to eliminate separate episodes of the behavior.  Most occur at the initial opening of any application, however the issue is now manifested after using an application successfully and upon opening a different application.  It is not indicated by any one particular application.  Rarely happens more than 5 minutes after a system start."
1755314,2019-08-02 20:57:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755314,2019-08-02 20:59:29 UTC,I want 80x24.
1755315,2020-03-20 02:22:08 UTC,"Hi Tejeev,
thanks for your reply, in this case I will change the status back to Incomplte for now until we have further issue."
1755315,2020-05-19 04:17:41 UTC,[Expired for Grafana Charm because there has been no activity for 60 days.]
1755315,2020-03-17 05:11:22 UTC,"I checked the code, while `upgrade-charm` hook is triggered, the charm just remove `grafana.installed` flag, which will trigger `install_packages`. In there, the code doesn't consider the situation of re-install and upgrade, which may need a restart. Of course the apt or snap package manager may do that, but not guaranteed. It will be better if the code can check the current service status and do a restart if necessary."
1755315,2020-03-05 01:11:31 UTC,"How was the upgrade performed, and how can this be reproduced. Need some more information about the process used to validate this issue."
1755315,2020-03-17 21:13:43 UTC,"Not sure.. this was filed 2 years ago and I don't even remember what customer's stack I was working on.  Maybe there's a record in the bootstack salesforce tickets, but I don't have access any more."
1755333,2018-03-13 02:25:49 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
 QMessageLogger::fatal (this=this@entry=0x7ffc418f3b10, msg=msg@entry=0x7fda4b24c8b7 ""%s"") at global/qlogging.cpp:796
 init_platform (argv=<optimized out>, argc=<optimized out>, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at kernel/qguiapplication.cpp:1148
 QGuiApplicationPrivate::createPlatformIntegration (this=<optimized out>) at kernel/qguiapplication.cpp:1294
 QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at kernel/qguiapplication.cpp:1311"
1755333,2018-03-14 11:30:59 UTC,"Hi Marcos,"
1755340,2018-03-14 11:31:47 UTC,"Hi Macros,"
1755340,2018-03-13 02:55:56 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
 QMessageLogger::fatal (this=this@entry=0x7fff366fb300, msg=msg@entry=0x7fb4b11e18b7 ""%s"") at global/qlogging.cpp:796
 init_platform (argv=<optimized out>, argc=<optimized out>, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at kernel/qguiapplication.cpp:1148
 QGuiApplicationPrivate::createPlatformIntegration (this=<optimized out>) at kernel/qguiapplication.cpp:1294
 QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at kernel/qguiapplication.cpp:1311"
1755367,2018-05-07 03:17:46 UTC,could you please paste the code change and close this bug
1755368,2018-03-13 11:16:25 UTC,"This is because of tacker is not fully implemented in tripleo, see: https://review.openstack.org/#/c/526099"
1755368,2021-02-18 16:46:06 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1755378,2018-03-13 07:30:06 UTC,This change was made by a bot.
1755378,2018-03-13 15:45:47 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1755378,2018-03-14 00:08:32 UTC,"Running 4.16.0-041600rc4-generic right now, works fine."
1755378,2018-03-26 15:31:40 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1755378,2018-03-29 00:33:09 UTC,Is that kernel in main now? After adding proposed just now it doesn't seem to have any kernel packages.
1755381,2018-03-23 09:02:18 UTC,"We already have skip-checks-extra, but this is different we want to exclude all checks (if any) for a given application/service.
Implementation should be similar to skip-checks-extra though."
1755384,2018-08-07 18:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1755384,2018-08-07 19:27:50 UTC,"This bug was initially opened for Artful, but it is now EOL as is the 4.13 kernel. Can you confirm this bug still exists in Bionic(18.04)?"
1755384,2018-08-22 07:02:04 UTC,"This issue doesn't exist when check ubuntu18.04.1-desktop64.
Ubuntu-18.04.1-desktop has kernel 4.15.0-32-generic."
1755385,2018-03-14 07:41:01 UTC,"This bug reporting is inappropriate within ""Rip"" package, but it's so hard to find the true path to report such a bug (I read many pages and tried many ways, but none provides me the solution). Could somebody help me ?"
1755390,2018-03-13 08:35:58 UTC,Nota : test OK of digiKam 5.9 through appimage in Kubuntu Bionic Beta 1
1755390,2018-03-14 07:40:31 UTC,"This bug reporting is inappropriate within ""Rip"" package, but it's so hard to find the true path to report such a bug (I read many pages and tried many ways, but none provides me the solution). Could somebody help me ?"
1755391,2020-04-09 20:22:10 UTC,I can't reproduce this with the latest build from git. Do you have any more specific steps to reproduce the issue?
1755397,2018-03-19 01:54:44 UTC,默认应用是系统设置好的，不能在控制面板里面去初始化哪个默认应用，要是初始化了，每次打开控制面板都会去设置该应用。
1755397,2018-04-26 06:39:26 UTC,The bug existed in bionic 20180426 amd64.
1755397,2018-04-26 09:21:32 UTC,The bug existed in bionic 20180425.1 i686.
1755399,2018-04-26 07:13:40 UTC,The bug was fixed in bionic 20180426 amd64.
1755411,2018-03-19 23:56:35 UTC,"Assigning ""wishlist"" because it's probably a low-frequence occurrence ... although if you' re seeing it in production, it happens more often than we'd like."
1755414,2018-03-19 03:44:21 UTC,Thanks for raise this. It sounds like a new enhance for neutron. I will tag it as rfe and discuss during the driver meetings.
1755414,2018-06-15 13:43:41 UTC,"I don't think I understand the use case behind this proposal. From a user point of view, what is it that you are trying to accomplish? Would you provide more details?"
1755414,2018-06-18 09:15:49 UTC,"Hi Miguel,"
1755414,2020-03-24 21:49:24 UTC,"Due to lack of any activity in this RFE since more than 1 year, I'm going to close it for now. If You would be still interested in implementing this and would like to continue discussion on that, feel free to reopen it and ping me (slaweq) on irc."
1755433,2018-06-20 16:21:34 UTC,This issue was fixed in the openstack/heat-translator 1.1.0 release.
1755434,2018-03-29 00:13:15 UTC,This issue was fixed in the openstack/puppet-neutron 12.4.0 release.
1755434,2019-05-16 23:06:08 UTC,This issue was fixed in the openstack/puppet-neutron 11.6.0 release.
1755434,2018-04-19 21:03:32 UTC,This issue was fixed in the openstack/puppet-neutron 13.0.0 release.
1755434,2018-03-23 03:02:29 UTC,"Reviewed:  https://review.openstack.org/554098
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=74152561f93e5ae33c7199ea9d9f095638ce6299
Submitter: Zuul
Branch:    stable/pike"
1755434,2018-03-19 03:36:22 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554098"
1755434,2018-03-13 09:54:29 UTC,"Since there is no CVE, we'll open the bug and fix it."
1755434,2018-03-19 03:36:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554097"
1755434,2018-03-16 22:35:14 UTC,"Reviewed:  https://review.openstack.org/552457
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=8f6c82638fe2781e4a2a2ffafadc83ba83f299ba
Submitter: Zuul
Branch:    master"
1755434,2018-03-19 18:34:21 UTC,"Reviewed:  https://review.openstack.org/554097
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=fa94be98588be22ddfd83509e4e6268ee0edd28c
Submitter: Zuul
Branch:    stable/queens"
1755438,2018-03-13 09:48:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755442,2018-03-13 10:27:15 UTC,"""Budgie network applet"" is GNOME's network-manager."
1755445,2018-03-13 10:20:11 UTC,Tests are failing with the following error:
1755445,2019-10-07 00:50:59 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1755445,2019-10-07 22:46:49 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1755447,2018-10-22 06:44:38 UTC,Was also fixed on python3.7 branch in February.  3.7.0~b3 (bionic version) was tagged March 29.
1755447,2018-10-22 06:42:37 UTC,Fixed on upstream 3.6 branch in February; so that's resolved for 3.6.5 and later (3.6.5 tagged Mar 28).
1755452,2018-04-16 19:06:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755452,2018-04-16 19:08:10 UTC,Was testing the daily ISO in a virtual machine. Ubiquity didn't adapt to the actual screen size; I couldn't click next. So I closed ubiquity and then this crash happened.
1755452,2018-04-16 20:06:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1755452,2020-03-21 13:42:57 UTC,Happened to me on xubuntu 20.04 daily iso from march 20th 2020.
1755452,2020-03-31 12:49:39 UTC,"I was able to recreate this on a 20.04 daily iso dated 20200330 by clicking quit after selecting a language. This happens both when choosing ""Install Ubuntu"" or launching ""Install Ubuntu"" from the desktop."
1755452,2020-05-16 15:42:22 UTC,Able to recreate on Ubuntu Desktop amd64 20.10 daily 20200516
1755455,2019-06-18 23:51:07 UTC,There appears to currently be only a single way to get the docker-distribution to listen when dealing with ipv6 traffic. You can configure it to only listen on the port which will result in it answering on any ipv4 or ipv6 interface on the system. You can specify the following hieradata in a file to accomplish this configuration:
1755455,2019-07-31 20:33:47 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/554608
Reason: this doesn't work for docker-distribution"
1755455,2019-04-19 07:13:18 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/653688
Reason: local testing shows ipv6 addresses do not get accepted by docker-registry config"
1755455,2019-04-19 07:12:40 UTC,local testing shows ipv6 addresses do not get accepted by docker-registry config
1755455,2019-04-18 08:32:48 UTC,NOTE: I tried to use notation :
1755455,2019-04-18 08:31:16 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/653688"
1755455,2018-03-20 16:04:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554608"
1755460,2018-03-15 08:02:51 UTC,This bug was fixed in the package memcached - 1.5.6-0ubuntu1
1755464,2018-03-13 12:11:54 UTC,"backtrace (forgot to say, 32 bit build):"
1755464,2018-03-13 12:33:52 UTC,Confirmed on Windows 7 with the same build (64-bit version)
1755464,2018-03-13 17:48:14 UTC,I believe the _focus_widget is suppose to be set to the canvas widget. Maybe it isn't being set properly.
1755464,2018-03-13 18:59:27 UTC,As a matter of fact InkSpinScale::set_focus_widget() is never called and _focus_widget therefore remains uninitialized...
1755464,2019-02-12 12:11:17 UTC,"I can no longer reproduce this on Windows 10, Inkscape 1.0alpha (9cedb1b, 2019-02-08)"
1755466,2018-03-13 12:15:34 UTC,Testcase 'nm' fails with the following error:
1755467,2018-09-21 12:28:38 UTC,"Change abandoned by Tom Barron (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/572090
Reason: We reverted the change from which this is a cherry-pick."
1755467,2018-09-04 08:25:59 UTC,"Goutham Pacha Ravi:
There is another bug related to this bug.It's all about solving residual problems after Manila tempest
https://bugs.launchpad.net/manila/+bug/1754588
https://review.openstack.org/#/c/551206/，
Will the patch also cause the above problems？
Does the patch still need to be continued?"
1755467,2018-06-15 22:01:35 UTC,"Reviewed:  https://review.openstack.org/575549
Committed: https://git.openstack.org/cgit/openstack/manila-tempest-plugin/commit/?id=d1f6a062b696b3c21817386da2c432fc844319e3
Submitter: Zuul
Branch:    master"
1755467,2018-03-26 13:57:03 UTC,"Reviewed:  https://review.openstack.org/552506
Committed: https://git.openstack.org/cgit/openstack/manila-tempest-plugin/commit/?id=264a6029db225716e11fbb5fd7b3014459b869b1
Submitter: Zuul
Branch:    master"
1755467,2018-06-04 12:19:20 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/572090"
1755467,2018-03-13 12:45:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/552506"
1755467,2018-06-15 18:50:49 UTC,"This bug fix broke DHSS=True tests that use tempest's pre-provisioned credentials mechanism [1]. It is currently essential for DHSS=True drivers that test with the NeutronNetworkPlugin (or derivatives) to use pre-provisioned tempest credentials to run tests. You can see the test failures on the container driver jobs (manila-tempest-dsvm-postgres-container) since this change was introduced. When we merged this change, our gate tests were affected by another bug [2] that hid the failures and made us miss it in code review."
1755482,2020-08-22 22:01:29 UTC,Likely fixed in newer versions of the ddclient package.
1755498,2020-03-10 05:44:59 UTC,"Maybe set (or allow as an option) ""bold is bright"" in vte"
1755498,2020-03-10 05:53:10 UTC,Temporary fix: add
1755498,2018-03-25 07:15:10 UTC,That is great news! Thanks!
1755498,2018-03-21 21:52:16 UTC,"Forthcoming vte-0.52.1 adds support for changing the bold color via escape sequence, e.g.:"
1755498,2018-03-14 07:25:04 UTC,"> [...] though I understand that it will probably not happen.
"
1755498,2018-03-14 06:38:32 UTC,"Yes, you are completely right."
1755498,2018-03-13 21:22:13 UTC,"> even plain terminator terminal (without terminal multiplexer)
> displayed nice bright white color for bold attribute.
"
1755505,2018-04-28 14:14:50 UTC,Thanks. Was able to fix all the warning in my ceph cluster by running following commands from ceph-mon container.
1755524,2018-03-22 16:44:04 UTC,Thanks for the report
1755524,2018-04-12 13:24:52 UTC,"Hi there, I am not seeing this behavior[1]"
1755538,2018-03-14 16:38:29 UTC,Upstream bug report: https://gitlab.gnome.org/GNOME/mutter/issues/68
1755538,2019-08-20 05:44:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755538,2018-03-14 02:31:31 UTC,"As this seems to be the first reported case of an invisible cursor, please report it upstream here:"
1755538,2018-03-14 02:29:14 UTC,I am going to remove your mention of the screen corruption because that's a separate issue -> bug 1753776.
1755538,2018-03-14 16:35:27 UTC,"Ok Daniel, I will report the bug upstream.
Thanks!"
1755544,2018-03-13 17:15:06 UTC,Administration section doesn't work
1755556,2018-03-13 19:10:13 UTC,Looks to me like this is a Thunar problem. From man engrampa it looks like this is expected behavior while using the --extract-here option.
1755556,2018-08-23 10:28:16 UTC,https://git.xfce.org/thunar-plugins/thunar-archive-plugin/tree/scripts/engrampa.tap
1755577,2020-02-23 10:19:24 UTC,Doomsday has been updated to 2.2 in Ubuntu Focal (https://bugs.launchpad.net/ubuntu/+source/doomsday/2.2.2+ds1-1~exp2). Bug 1757628 on the QT4 issue has a bit more details.
1755580,2018-03-13 20:07:00 UTC,The GUI issue is for vsphere but the issue also happens on GCE (possibly others as well)
1755580,2018-03-13 21:13:25 UTC,"Can you provide a log confirming this? It seems like this is an API issue with your call, but not an issue on the cli."
1755580,2018-03-13 22:48:08 UTC,@nskaggs the calls are outlined in the original description.
1755587,2018-03-30 00:43:49 UTC,I cna confirm this is an issue on the UI only. Updating over the API works just fine.
1755587,2018-04-03 00:21:44 UTC,"I've got a fix proposed for this, but the full fix may also require a fix for bug #1759946, otherwise moving a subnet will leave each interface with an IP address on the subnet confused about which VLAN it belongs to."
1755587,2018-03-22 23:04:35 UTC,"This is a somewhat strange bug at first glance, because in the MAAS data model, subnets are not directly associated with fabrics. They are associated with VLANs, and VLANs are on a specific fabric. In other words, you cannot actually change the fabric of a subnet. You can only change the VLAN of a subnet, and the new fabric is implied."
1755587,2018-03-13 21:31:26 UTC,"Great! Thanks Chris, one more quick question, no tracebacks in the logs?"
1755587,2018-03-13 20:39:36 UTC,"Hi Chris,"
1755587,2018-03-13 21:35:20 UTC,"Actually, nevermind, I just confirmed this bug and there was no error log at all."
1755587,2018-03-13 20:57:02 UTC,"Andres,"
1755593,2018-03-20 16:38:53 UTC,"I like the idea of using OSA to pre-install pip dependencies into rally virtualenv, as we already have that in place. But I wonder what do you mean by ""at the versions that Tempest will require"" ?"
1755593,2018-03-21 01:36:07 UTC,"Rally installs an encapsulated Tempest of its own to use for verifying OS functionality; in the OSA deployment of Rally, some of the dependencies for its encapsulated Tempest are more recent than the packages that Rally itself requires. In order for Rally to perform all of its functions including verification, its environment has to include packages (specifically Oslo.concurrency) at the versions its encapsulated Tempest requires."
1755603,2018-07-24 03:04:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755607,2018-03-14 11:07:22 UTC,"I worked around this problem by manually installing the junit package (3.8.2-9). Note that the gradle package transitively declares a dependency to junit4, but seems to strictly require JUnit 3."
1755609,2018-03-20 16:36:59 UTC,"You are defining your br-mgmt network as the ssh network, and define 10.120.241.0/24 as the management network, yet your're using 10.120.240.11, 10.120.240.12 and 10.120.240.5, 10.120.240.6, which are outside the range."
1755609,2018-03-20 17:40:26 UTC,Please see today's bug triage meeting conversation on ideas for fixing this.
1755624,2018-03-16 14:47:15 UTC,More tests:
1755624,2018-04-04 08:11:04 UTC,"Now fixed here too, on 4.15.0-14 kernel"
1755624,2018-03-17 08:42:38 UTC,Also discussed here: https://lkml.org/lkml/2018/2/12/123
1755624,2018-03-17 08:36:35 UTC,Thanks Steve for the head up
1755624,2018-03-16 17:06:32 UTC,"Hi dino99,"
1755624,2018-03-16 13:59:43 UTC,"So i have reinstalled both intel-microcode & iucode-tool and then rebooted.
Still get the latest microcode version with the error; even if the reinstall has not displayed warning/error and the kernel rebuilt as expected."
1755624,2018-03-16 13:43:28 UTC,From the 4.15.0.12-13 still get the error
1755624,2018-03-14 17:25:52 UTC,4.15.0-12.13-generic from bionic-proposed is also working for me. Relevant CPU model info (same as in description):
1755624,2018-03-14 16:33:00 UTC,"4.15.0-12.13-generic, from bionic-proposed, fixes this bug for me due to it containing this upstream commit:"
1755624,2018-03-14 15:52:14 UTC,Would it be possible for those that can reproduced this bug to test the proposed kernel and post back if it resolves this bug?
1755624,2018-03-14 00:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1755624,2018-03-13 23:47:28 UTC,"I see the same issue on my Skylake desktop (sig=0x506e3).  The microcode updates at startup (microcode: microcode updated early to revision 0xc2, date = 2017-11-16) but I still get ""Intel Spectre v2 broken microcode detected; disabling Speculation Control"".  I also tested it on Ivy Bridge, Broadwell, and another Skylake system (0x406e3) and it works properly on all those."
1755624,2018-03-16 13:48:56 UTC,Something abnormal:
1755627,2018-04-25 12:54:52 UTC,"Is the fixed kernel available right now? Or when could it be available?
This ""ubrs"" messages are flooding our syslog log files on many machines."
1755627,2018-04-25 14:33:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1755627,2018-04-25 16:46:03 UTC,Hello.
1755627,2018-04-27 19:02:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1755627,2018-04-27 19:12:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1755627,2018-04-27 19:30:37 UTC,"Verified fixed in all affected -proposed kernels:
 trusty 3.13.0-146.195
 xenial 4.4.0-123.147
 artful 4.13.0-40.45"
1755627,2018-05-11 00:40:03 UTC,It looks like it got deferred to 4.4.0-125 according to the changelog [1].
1755627,2018-05-11 00:17:39 UTC,I am still experiencing this issue after upgrading to xenial 16.04.4 LTS 4.4.0-124-generic.
1755627,2018-05-11 16:10:46 UTC,"Indeed, the -proposed kernel versions which included this fix were all bumped out due to an unrelated security fix release.  The next kernel versions (now available in -proposed) include the fix again:"
1755627,2018-05-21 23:59:29 UTC,This bug was fixed in the package linux - 3.13.0-149.199
1755627,2018-05-22 00:00:38 UTC,This bug was fixed in the package linux - 4.4.0-127.153
1755627,2018-05-22 00:04:32 UTC,This bug was fixed in the package linux - 4.13.0-43.48
1755627,2018-04-30 17:49:09 UTC,Hello.
1755627,2018-04-24 19:30:50 UTC,Just FYI folks: This fix does not yet appear in the kernels which just landed in -proposed (which are respins for an unrelated issue).  The fix is still queued up for the next cycle (currently 4.4.0-123.147).
1755627,2018-04-18 18:16:30 UTC,"Hello,"
1755627,2018-04-13 16:00:20 UTC,@lscotte - Thanks for reporting the issue.  Launchpad will post a note to this bug as soon as the kernel versions containing the fix reach the -proposed archive.
1755627,2018-04-12 17:48:47 UTC,Thank you @kamalmostafa - we'll keep an eye out for the updated packages in the repositories and follow up if anything is not as expected. Thanks again for fixing this!
1755627,2018-04-12 17:17:51 UTC,"@bmoyles-  FYI, we're just removing the kernel.ibrs_dump interface altogether -- its only purpose is to provide that debug info, and nothing like it made it to mainline."
1755627,2018-03-14 22:23:57 UTC,"https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/kernel/sysctl.c#n2433
and
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/kernel/sysctl.c#n2446"
1755627,2018-03-14 21:46:43 UTC,Thank you Leann!
1755627,2018-03-14 18:30:44 UTC,"Also, to call it out again, this appears to affect Trusty's LTS kernel, too (it's not clear how one marks a bug as such from the Launchpad UI)"
1755627,2018-03-14 18:18:28 UTC,"For the sake of completeness on this one, I installed the following mainline packages on an AWS m5.large instance running 16.04.3 w/ 4.4.0-112-generic"
1755627,2018-03-14 17:07:24 UTC,"It's worth noting, too, that this does not happen on Bionic @  4.15 (using Ubuntu 4.15.0-1001.1-aws 4.15.3) but it does happen on Trusty (using Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39)"
1755627,2018-03-14 16:32:19 UTC,Returning to confirmed status - easily reproducible with LTS kernels.
1755627,2018-03-14 16:31:34 UTC,"We use LTS kernels, so no - unfortunately we cannot."
1755627,2018-03-14 15:49:20 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1755627,2018-03-14 00:35:02 UTC,"We do not use apport and this is easily reproducible. If there is any pointed information I can provide beyond what I've already submitted, please let me know."
1755627,2018-03-14 00:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1755627,2018-04-21 13:31:49 UTC,Hello.
1755629,2018-06-26 11:56:49 UTC,"I'd suggest to at least add something like
  if [ -d ""$(dirname $warn_file)"" ]
around the cat
and then before the chmod/chattr
  if [ -f ""$warn_file"" ]"
1755629,2019-05-23 21:41:20 UTC,"This bug is hitting our clusters hard especially when dynamically adding nodes. In this case, container workloads that use /mnt are scheduled on the new nodes before walinuxagent is updated causing corruption of attrs and perms of /mnt, and potentially file/folder underneath."
1755629,2018-06-26 11:45:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755629,2018-06-26 11:45:53 UTC,I agree that LP#1626318 is essentially the same and dup'ed it onto this one.
1755640,2018-03-14 01:42:28 UTC,"The attached JAR-file has online help (click the Help button) to explain how to use it.  Unfortunately, Java cannot 'see' ALSA MIDI devices, so you have to use a hardware MIDI interface (such as a USB MIDI keyboard)."
1755640,2018-03-14 01:59:09 UTC,"In the traced MIDI messages in the bug-report, the top line is the most recent, and the bottom line is the oldest.  It came from the Java console (of IcedTea)."
1755656,2018-04-19 23:18:38 UTC,This bug was fixed in the package youker-assistant - 3.0.0-0ubuntu1
1755656,2019-04-09 05:54:04 UTC,"youker-assistant & ukui-control-center conformity , remove function of beautify"
1755667,2018-07-18 12:04:12 UTC,Triaging as 'Low' as this does not effect function - its more of a UX issue.
1755667,2018-07-18 11:48:49 UTC,I can confirm that I see the same behaviour - however I'd like to understand why we end up with crufty worker entries.
1755667,2018-07-18 12:02:30 UTC,"""heat-manage service clean"""
1755667,2018-07-18 12:03:12 UTC,"Other than its in the initial commit for the charm, I also don't understand why we set the host configuration option to heat, rather than allowing the default of the local hostname."
1755675,2018-03-17 01:12:33 UTC,Sorry I left out a package name.
1755675,2018-03-17 04:28:40 UTC,CRAP I finally got it!
1755675,2018-03-14 08:19:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1755681,2018-04-01 20:24:44 UTC,"After two weeks of no response, is this the wrong venue?"
1755681,2018-04-03 05:59:11 UTC,"I think you are right here, not sure what happened to the triager of march 14th."
1755681,2018-04-03 06:09:42 UTC,"The offending line you identified was not fixed as a bug fix that one could directly backport, but instead as part of [1]"
1755681,2018-04-03 06:10:54 UTC,Note: I'm asking as a SRU [1] usually needs sort of a reproduction steps guide to verify - and since I fail to recreate ...
1755681,2018-04-03 19:05:14 UTC,"My reliable repro was actually a much less intensive `watch 'pstree -aup' | grep ""...""`"
1755681,2019-08-13 15:01:50 UTC,"Lucas identified this beign the same as one that he works on.
Marking as duplicate."
1755689,2018-03-19 00:11:29 UTC,"Can you provide more information about where you are seeing this error?  What is your setup like, etc.?"
1755689,2018-04-05 12:25:56 UTC,"If Glance is returning 500 for pretty much every call (except maybe 'versions'), you may be hitting this bug: https://bugs.launchpad.net/glance/+bug/1754104"
1755689,2018-04-06 08:31:38 UTC,glance image uploading time getting error
1755694,2018-03-14 06:41:01 UTC,"StacktraceTop:
 IA__FcConfigSubstituteWithPat (config=<optimized out>, config@entry=0x0, p=p@entry=0x5607a4db2040, p_pat=p_pat@entry=0x0, kind=kind@entry=FcMatchPattern) at fccfg.c:1723
 IA__FcConfigSubstitute (config=config@entry=0x0, p=p@entry=0x5607a4db2040, kind=kind@entry=FcMatchPattern) at fccfg.c:1838
 pango_cairo_fc_font_map_fontset_key_substitute (fcfontmap=<optimized out>, fontkey=0x7ffc770e3bc0, pattern=0x5607a4db2040) at pangocairo-fcfontmap.c:116
 pango_fc_default_substitute (pattern=<optimized out>, fontsetkey=0x7ffc770e3bc0, fontmap=0x5607a4cf1e40) at pangofc-fontmap.c:1616
 pango_fc_font_map_get_patterns (key=0x7ffc770e3bc0, fontmap=0x5607a4cf1e40) at pangofc-fontmap.c:1670"
1755694,2018-06-06 12:37:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755694,2020-07-01 21:03:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Is that specific to a document, if so could you add it to the bug report?"
1755694,2020-08-31 04:17:28 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1755696,2020-12-07 02:17:44 UTC,"fix proposed, review:"
1755696,2020-12-01 11:33:39 UTC,"actions shouldn't manipulate config files, that's a hook + config.yaml job."
1755696,2020-12-07 01:28:24 UTC,"My intention is to add config option `inject-password` to the config.yaml that would allow user to inject admin/root password at nova instance boot time.
According to config reference [1]:"
1755704,2018-03-14 08:15:14 UTC,"StacktraceTop:
 g_type_check_instance_is_a (type_instance=type_instance@entry=0x558fc35d2240, iface_type=<optimized out>) at ../../../../gobject/gtype.c:4013
 GCAL_IS_MONTH_CELL (ptr=0x558fc35d2240) at ../src/views/gcal-month-cell.h:31
 gcal_month_cell_set_date (self=self@entry=0x558fc35d2240, date=date@entry=0x558fc3a7ea40) at ../src/views/gcal-month-cell.c:480
 update_month_cells (self=0x558fc37b83b0) at ../src/views/gcal-month-view.c:983
 g_closure_invoke (closure=0x558fc4277f60, return_value=0x0, n_param_values=1, param_values=0x7fffe7a33680, invocation_hint=0x7fffe7a33600) at ../../../../gobject/gclosure.c:804"
1755716,2018-03-14 10:21:17 UTC,"Crash just happened again, right after unlocking screen saver, then the gnome launcher on the left and status bar at the top disappeared, followed a few seconds later by Xorg exiting"
1755718,2018-04-26 09:21:15 UTC,The bug existed in bionic 20180425.1 i686.
1755723,2018-04-26 09:15:21 UTC,The bug existed in bionic 20180425.1 i686.
1755727,2018-04-09 11:12:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559707"
1755727,2018-04-13 08:23:01 UTC,"Change abandoned by feng.shengqin (<email address hidden>) on branch: master
Review: https://review.openstack.org/559707"
1755728,2018-03-15 08:37:40 UTC,"yeah, it's a good reminder. The projects who use keystonemiddleware should pay attention."
1755728,2018-11-05 06:43:37 UTC,https://github.com/openstack/cinder/commit/19dd18b17f2fbcca37b0c6633f47c0b7cdace9a7#diff-568ee7fd302847948453bea53c42c72f
1755728,2019-01-28 18:05:57 UTC,Looks like there are other projects still relying on auth_uri [0]. Keeping this open since it's a relatively good low-hanging-fruit bug and something we should try and correct in other services.
1755728,2018-03-19 15:55:30 UTC,It might help to associate projects that need assistance moving to www_authenticate_uri to this bug report.
1755734,2018-04-26 09:17:08 UTC,This function was not existed.
1755756,2019-01-18 20:26:48 UTC,What version of qemu-utils are people using when they hit this? It looks like --force-shared should only be used with qemu>=2.10.
1755756,2019-11-07 16:42:53 UTC,Are there any updates on the status of this ? I'm experiencing the same behavior in my Queens deployment.
1755756,2019-10-17 06:38:37 UTC,ImageUnacceptable: Image f083653d-e3bd-46d9-8e89-7ec031d0b8f3 is unacceptable: Image virtual size is 8GB and doesn't fit in a volume of size 1GB.
1755756,2019-01-18 20:37:05 UTC,"I guess one thing we could do is if we run with --force-share and we don't get an error, we could check the stdout/err output for ""unrecognized option '--force-share'"" and if we find that, we need to run it again without --force-share (the version check was meant to handle that for us, but qemu-img and qemu-utils could be different package versions...)."
1755756,2019-01-18 20:31:22 UTC,"(2:30:15 PM) dansmith: mriedem: pretty sure that the issue was that we installed something, got qemu-utils=something, then upgraded to cloud archive, got a new qemu, but it was fine with the older qeu-utils, and didn't upgrade it
(2:31:00 PM) mriedem: dansmith: ah ok, so qemu could be 2.10 but qemu-utils could be 2.5 or something
(2:31:01 PM) dansmith: meaning qemu==N doesn't require qemu-utils==N, just qemu-utils==anything
(2:31:04 PM) dansmith: right
(2:31:04 PM) mriedem: yeah"
1755756,2018-09-19 08:27:04 UTC,do you have any solution ? ı am getting same errors on pike.
1755756,2018-08-30 15:31:09 UTC,"I hit this because I had a backlevel qemu-utils compared to what devstack installs in our gate jobs. Devstack installs cloud-archive:pike when deploying queens and installs qemu-utils from there. If you're on xenial and getting qemu-utils from the base distro, this may be your problem."
1755756,2018-04-11 15:13:23 UTC,"Just some added information. stable/queens devstack build. Error only when creating a new instance from the openstack CLI:
Build of instance c6b46fc3-8f80-449d-a1a7-93be661a6166 aborted: Image 64325b6e-e625-4838-8f9d-7b54fff2506c is unacceptable: 'qemu-img info' parsing failed.
Code
500
Details
File ""/opt/stack/nova/nova/compute/manager.py"", line 1840, in _do_build_and_run_instance filter_properties, request_spec) File ""/opt/stack/nova/nova/compute/manager.py"", line 2108, in _build_and_run_instance reason=e.format_message())
Created
April 11, 2018, 2:24 p.m."
1755756,2018-04-05 01:36:57 UTC,Thanks for including the traceback paste.
1755756,2018-03-15 11:52:38 UTC,I am also getting the  error after launching Instance .
1755756,2018-03-15 08:06:55 UTC,Getting same error when tried to launch instance from Dashboard of devstack master.
1755756,2018-08-30 22:11:23 UTC,"I tried a test with an older version of qemu-img in devstack and found that if the version of qemu-img does not recognize the --force-share flag, it will anyway return 0, so that explains how the bug reporter saw ""returned 0"" and still got the failure:"
1755757,2018-03-14 10:39:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/552873"
1755757,2018-03-19 07:07:27 UTC,"Hello, QingchuanHao."
1755757,2018-03-19 08:19:59 UTC,"Thank your comment, Eunsoo Park."
1755757,2018-03-21 09:43:25 UTC,"I think that handling of the port Add/Remove events should be handled according to the Pod network owner. As long as we support single network owner, kuryr should be handling the events. Once there are multiple network providers as it is currently discussed by k8s-net-sig team, it should be only kuryr destined Pods"
1755757,2018-12-07 15:36:20 UTC,"Change abandoned by Antoni Segura Puimedon (<email address hidden>) on branch: master
Review: https://review.openstack.org/552873
Reason: Lack of activity"
1755761,2018-03-14 11:09:38 UTC,I am not seeing the issue with the latest daily ISO for Ubuntu proper. So this seems specific to the budgie images.
1755761,2018-03-14 11:22:32 UTC,Olivier - maybe - but ubiquity is not customised in anyway for budgie other than the cosmetics such as the wallpaper and panel.
1755764,2018-03-14 23:55:03 UTC,*** This is an automated message ***
1755765,2018-03-21 14:43:44 UTC,Hardware Certification have begun testing this -proposed kernel.
1755765,2018-03-22 08:24:45 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.13.0-1016.17/raspi2-4.13-proposed-published.html"
1755765,2018-03-27 08:36:19 UTC,No derivative specific changes.
1755765,2018-04-04 12:16:34 UTC,This bug was fixed in the package linux-raspi2 - 4.13.0-1016.17
1755765,2018-04-04 13:01:47 UTC,The package has been published and the bug is being set to Fix Released
1755767,2018-04-03 14:00:39 UTC,This bug was fixed in the package linux-hwe - 4.13.0-38.43~16.04.1
1755767,2018-04-04 06:34:23 UTC,The package has been published and the bug is being set to Fix Released
1755767,2018-04-03 13:19:55 UTC,"Manual overriding as I did not see any backport specific changes, the Artful kernel looked good and I did not hear about issues."
1755767,2018-03-23 07:29:51 UTC,Hardware Certification have begun testing this -proposed kernel.
1755767,2018-03-28 08:20:49 UTC,Mark this as Incomplete due to the ThunderX issue (bug 1758036)
1755767,2018-03-26 08:30:42 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.13.0-38.43~16.04.1/xenial-4.13-proposed-published.html"
1755767,2018-03-29 08:51:34 UTC,"Regarding the ThunderX zram smoke test, according to bug 1755073 that bug is also on upstream and a SAUCE patch with a interim fix has been sent to the mailing which is going to be committed to the next SRU cycle. Based on that, I'm marking regression-testing as 'Fix Released'."
1755771,2018-03-22 11:13:42 UTC,Mark this task as Incomplete for the zram smoke test bug. Although this is a new test.
1755771,2018-03-27 08:33:49 UTC,No derivative specific changes.
1755771,2018-03-29 08:48:40 UTC,"The ubuntu_zram_smoke_test is not a regression and is being handled on bug 1757937, hence marking regression-testing as 'Fix Released'."
1755771,2018-04-03 14:37:37 UTC,This bug was fixed in the package linux-gcp - 4.13.0-1012.16
1755771,2018-04-04 09:34:13 UTC,The package has been published and the bug is being set to Fix Released
1755779,2018-08-24 01:59:06 UTC,If you have a crash file then please always use 'ubuntu-bug' to send it:
1755779,2018-08-23 14:07:56 UTC,"Hello Daniel van Vugt,"
1755779,2018-08-20 13:55:27 UTC,"Hello,"
1755779,2018-08-02 02:00:31 UTC,"Now
https://gitlab.gnome.org/GNOME/mutter/issues/253"
1755779,2018-08-24 11:09:41 UTC,"Hello,"
1755779,2018-06-08 01:58:45 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/37a88e96048de35d02939c3dd8fe220f716448ee"
1755779,2018-08-01 18:58:38 UTC,https://gitlab.gnome.org/GNOME/gnome-shell/issues/456
1755779,2018-03-14 11:12:32 UTC,"StacktraceTop:
 _g_log_abort (breakpoint=breakpoint@entry=1) at ../../../../glib/gmessages.c:583
 g_log_writer_default (log_level=6, log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7fff1a1f0800, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../../glib/gmessages.c:2735
 g_log_structured_array (log_level=G_LOG_LEVEL_ERROR, fields=0x7fff1a1f0800, n_fields=6) at ../../../../glib/gmessages.c:1970
 g_log_structured_standard (log_domain=log_domain@entry=0x7f90daeaf28e ""Gdk"", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f90daecda78 ""../../../../../gdk/x11/gdkdisplay-x11.c"", line=line@entry=0x7f90daecd4cf ""2766"", func=func@entry=0x7f90daece190 <__func__.74387> ""_gdk_x11_display_error_event"", message_format=message_format@entry=0x7f90daece50b ""%s"") at ../../../../glib/gmessages.c:2027
 _gdk_x11_display_error_event (display=display@entry=0x55fd45c2f110, error=error@entry=0x7fff1a1f0e50) at ../../../../../gdk/x11/gdkdisplay-x11.c:2766"
1755779,2018-08-21 01:38:04 UTC,You add a line to /etc/environment:
1755779,2018-03-26 20:12:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755779,2018-03-15 02:10:39 UTC,Looks like bug 1691701. Only the stack trace changed a little in 18.04 so we have this new bug.
1755787,2019-10-01 05:38:14 UTC,Fixed in https://launchpad.net/fatrace/trunk/0.14
1755795,2018-04-26 15:48:10 UTC,We should work on minimising the usage of the default share type in tests to only tests that specifically test that functionality. We should create share types automatically for all other cases. Group setup and teardown is a good place for this stuff. There is also the possibility of individual test setup and teardown for tests that require any sort of special requirement.
1755795,2018-03-30 09:16:08 UTC,"Tom Barron:
    I'm terribly sorry, I accidentally deleted the driver_handles_share_servers attribute of default.
    the'manila type-list'command is executed as follows:"
1755795,2018-07-20 20:25:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584505"
1755795,2018-03-29 04:47:04 UTC,"Tom Barron:
    If default_share_type_name = default is not configured in tempest.conf, the test case will create a new type during the execution, and the test can be executed correctly.
    if  default_share_type_name = default is configured in tempest.conf,the above error will occur."
1755795,2018-03-29 01:30:59 UTC,"Tom Barron:
    share type named 'default', which is created by default after the environment is installed.
In my environment, the'manila type-list'command is executed as follows:"
1755795,2018-03-28 15:49:55 UTC,Did you create a share type named 'default'?
1755795,2018-03-29 20:10:26 UTC,"I am puzzled by the fact that the share type named 'default', and which 'manila type-list' reports *is* the default, is missing its required_extra_specs (the driver_handles_share_servers attribute)."
1755811,2018-07-23 09:42:43 UTC,Note this has happened again with another systemd update (232-25+deb9u4)
1755811,2019-11-24 03:45:37 UTC,I just updated a fresh install of retropie and ran into this issue as well.
1755811,2019-09-17 03:31:52 UTC,I confirm that. This issue prevents retropie from loading to EmulationStation GUI after a system update
1755813,2018-05-11 15:36:31 UTC,This change was made by a bot.
1755817,2018-03-14 14:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1755817,2018-04-09 16:49:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1755817,2018-04-16 15:20:39 UTC,"Note: the issue is only reproducible on a system with more than 1 CPU. It fails on the ""Cross-CPU LDT invalidation"" testcase."
1755817,2018-04-16 15:49:40 UTC,Verified the issue to be fixed with Trusty kernel 3.13.0-145.194.
1755817,2018-04-23 08:22:12 UTC,This bug was fixed in the package linux - 3.13.0-145.194
1755818,2021-02-17 17:10:22 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1755821,2019-02-27 15:25:14 UTC,"Reviewed:  https://review.openstack.org/637495
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-plugins/commit/?id=43d2ef6a000c44da3358e2dd0d7c04db68c9b1a9
Submitter: Zuul
Branch:    stable/rocky"
1755821,2019-02-21 09:35:36 UTC,"Reviewed:  https://review.openstack.org/636935
Committed: https://git.openstack.org/cgit/openstack/ansible-config_template/commit/?id=66a97f2b403252d2b6f8aaa38f17deccbd753b4c
Submitter: Zuul
Branch:    master"
1755821,2019-02-14 11:55:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/636935"
1755821,2019-02-18 09:07:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/637495"
1755821,2019-02-13 18:25:14 UTC,"In trying to address this bug we found that Pythons ConfigParser
module will not parse an input file with an indented comment line
with leading whitespace before the first section header."
1755822,2018-03-14 14:29:55 UTC,also #1629 (transifex)
1755822,2018-03-14 17:28:29 UTC,Which language are you using so this can be corrected for the next release.
1755822,2018-03-14 20:05:35 UTC,"I do translation from source English language to Slovak, but I think that there are missing some brackets in the source string - some variable representation."
1755822,2018-03-16 06:04:21 UTC,The code is wrong and needs to be fixed as the error is incorrect.
1755833,2018-03-28 13:27:37 UTC,Any help or comments?
1755833,2020-05-06 17:09:54 UTC,"I replicate the weird behavior in Inkscape 0.92.5 (fe8e1c6569, 2020-04-22) but not in Inkscape 1.1-dev (4e2169377c, 2020-05-06) or 1.0 (4035a4f, 2020-05-01) appimage or 1.0alpha (9dee831, 2019-01-15) appimage, testing on Linux Mint 19.1 with an ellipse."
1755836,2018-03-14 15:44:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/552931"
1755839,2018-04-03 01:38:36 UTC,I meet the exactly the same problem.
1755839,2018-03-27 12:55:30 UTC,Negative for me... still hanging...
1755839,2018-03-26 07:29:25 UTC,The hanging issue has been fixed somehow. And I can run update and upgrade. Even reboot is fine.
1755839,2018-03-26 07:15:30 UTC,I cannot confirm that for my installation:
1755839,2018-03-25 13:06:23 UTC,"I was able to run ""sudo apt-get upgrade -f"" to fix the issue. Not sure what changed but this bug is fixed for me."
1755839,2018-03-21 07:40:59 UTC,"Any workaround to get apt-get going again? My computer renders a kind of useless. I just started to set it up, so most of the software i need is missing..."
1755839,2018-03-16 14:32:31 UTC,@jsalisbury
1755839,2018-03-20 10:27:45 UTC,Not nice as i am now not able to install anything via apt-get... Maybe the importance should be adjusted.
1755839,2018-03-19 08:30:22 UTC,`sudo apt-get install -f ` hangs so marking this as Confirmed
1755839,2018-04-10 06:40:13 UTC,"Seems to be fixed now, ie after i run"
1755839,2018-03-15 23:12:22 UTC,Package install was hung for a long time.
1755839,2018-03-15 19:23:55 UTC,You may need to run the following from a terminal:
1755839,2018-03-14 15:30:04 UTC,This change was made by a bot.
1755839,2018-03-20 15:46:27 UTC,I'm confirming that I am experiencing the same issue and the suggested fix is not fixing it. Still hangs and now I can't install any software.
1755839,2018-03-16 13:37:23 UTC,Killing the main plymouth server process allowed the installation to proceed.
1755849,2021-02-19 15:52:00 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1755853,2018-12-28 14:56:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755853,2019-03-06 10:22:44 UTC,"I found this : https://dkim-milter-discuss.narkive.com/rO3LtMGS/solved-can-t-read-smfic-eoh-reply-packet-header-success
(remove search"" line from the /etc/resolv.conf file)
but it didn't help."
1755853,2019-12-26 11:20:41 UTC,"This still seems to be a problem. We need more information about the conditions leading to the crash though, config, logs, backtrace etc."
1755853,2018-12-28 14:48:57 UTC,"hey,
I have the same bug"
1755855,2018-03-14 16:36:14 UTC,"StacktraceTop:
 get_tags_no_iface (file=0x5634513c7e50 ""/home/haze/Music/Dil Da Haal.mp3"", tags_sel=<optimized out>) at interface.c:3919
 interface_cmdline_formatted_info (server_sock=<optimized out>, format_str=0x5634513922d0 ""%song"") at interface.c:4281
 server_command (params=0x5634509d0a40 <params>, args=0x563451392070) at main.c:260
 main (argc=<optimized out>, argv=<optimized out>) at main.c:1261"
1755855,2018-03-14 18:56:43 UTC,"Does this affect ""/home/haze/Music/Dil Da Haal.mp3"" only? Did you tried other files in mp3 format? Could you please test ""/home/haze/Music/Dil Da Haal.mp3"" with an other media player? What is the output of 'file /home/haze/Music/Dil\ Da\ Haal.mp3' ?"
1755855,2018-03-16 14:49:02 UTC,"this bug show again, with 4 file mp3 on my musics folder."
1755855,2018-03-18 07:46:40 UTC,* Huzaeni Rifai <email address hidden> [2018-03-16 14:49 -0000]:
1755858,2018-06-01 08:10:28 UTC,Done for Cosmic.
1755858,2018-09-05 14:11:10 UTC,Nominated this for xenial based on bug 1651497.
1755858,2018-09-06 16:34:46 UTC,"To be explicit, I don't think that the risk of regression here is such that we should not SRU this to bionic.  I think anyone checking for the running status of an open-iscsi service, on a system that does not have any iscsi targets configured, is writing buggy code and that should not be catered to in the face of the significant impact this bug has on all other users of Ubuntu Server."
1755858,2018-09-07 18:19:48 UTC,"I prepared merge proposals for both xenial and bionic.
Also:
 - tested autopkgtest on both xenial and bionic
 - uploaded to [my ppa](https://launchpad.net/~smoser/+archive/ubuntu/ppa) for xenial and bionic
 - uploaded bionic to SRU queue"
1755858,2018-09-10 06:06:18 UTC,"FYI - Smoser and I started to prep SRU work for this.
But once we agree on the content I'd be really happy if someone who was affected by the upgrade issue (and therefore has a valid and ""real"" iscsi setup) would test from the PPA before shoving that into the SRU queue."
1755858,2018-06-01 06:58:21 UTC,This bug was fixed in the package open-iscsi - 2.0.874-5ubuntu4
1755858,2018-09-21 17:06:34 UTC,"@smoser, @paelzer, your bionic upload has been sitting for ~10 days in the upload queue, and it's blocking upload for bug 1791108.  Can you shake the sru trees to get that upload approved, or can you ask for it to be rejected so i can upload for the other bug?"
1755858,2018-10-01 15:53:54 UTC,We do not usually do this type of validation as there is no Proposed pocket MAAS image or cloud image. An image would need to be build for just this package. The only alternative is to manually upgrade the images after they are applied to the nodes/pods/and instances.
1755858,2018-10-01 14:38:59 UTC,@cgregan are you able to verify the bionic-proposed pkg?
1755858,2018-10-01 15:48:05 UTC,"We do not typically pull from proposed. I would need to look into the
process. The usual trouble is that once you turn on proposed, you"
1755858,2018-10-01 17:00:01 UTC,"@Chris,
For what its worth, there is a process to build maas images with -proposed
enabled at
 https://gist.github.com/smoser/8a34b1713badb643dee3a25e5cf134b8"
1755858,2018-10-02 00:26:04 UTC,"Here is my verification of bionic proposed.
It should be considered in cooperation with open-iscsi dep8 tests
which do a iscsi root boot:
  http://autopkgtest.ubuntu.com/packages/o/open-iscsi/bionic/amd64"
1755858,2018-10-02 17:54:12 UTC,This bug was fixed in the package open-iscsi - 2.0.874-5ubuntu2.2
1755858,2018-10-02 17:54:19 UTC,"The verification of the Stable Release Update for open-iscsi has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1755858,2018-09-25 21:59:49 UTC,"Hello Steve, or anyone else affected,"
1755858,2018-05-31 07:22:44 UTC,"Ok, the forth was a charm - so on LP Infra it seems to be flaky which is a separate issue.
This is the working log from the ppa: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-ci-train-ppa-service-3279/cosmic/amd64/o/open-iscsi/20180531_060452_bd5ba@/log.gz"
1755858,2018-05-24 13:28:20 UTC,Lets get it right in Cosmic also to see what we come up with and if you then say this should be safe for an SRU I'll follow your guidance :-)
1755858,2018-05-30 13:49:22 UTC,"The hit in ""testsuite"" is more complex, as it does not reproduce for me.
From the log:
======================================================================
ERROR: test_tgt_boot (__main__.CloudImageTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File ""/tmp/autopkgtest.BEvlMr/build.15A/src/debian/tests/test-open-iscsi.py"", line 274, in test_tgt_boot
    subprocess.check_call(cmd)
  File ""/usr/lib/python2.7/subprocess.py"", line 190, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['/tmp/autopkgtest.BEvlMr/build.15A/src/debian/tests/tgt-boot-test', '-v', '--netdev=user,net=10.1.1.0/24,host=10.1.1.2,dns=10.1.1.4,dnssearch=example.com', '--disk=/tmp/tmpin5Hu3/output-disk.img,serial=output-disk', '--user-data-add=/tmp/tmpin5Hu3/user-data', '/tmp/autopkgtest.BEvlMr/build.15A/src/debian/tests/cosmic.d/disk.img', '/tmp/autopkgtest.BEvlMr/build.15A/src/debian/tests/cosmic.d/kernel', '/tmp/autopkgtest.BEvlMr/build.15A/src/debian/tests/cosmic.d/initrd']' returned non-zero exit status 124"
1755858,2018-05-23 12:03:34 UTC,"Status of a clean install in a VM and/or Container, so testable rather trivial:"
1755858,2018-05-23 12:55:56 UTC,"Most basic tests cross check on Fedora:
First I tried a safe no-op
  $ iscsiadm -m discovery -t sendtargets -p 127.0.0.1
  This is working fine on fedora to activate the service"
1755858,2018-05-23 12:57:18 UTC,Trying a hacky POC:
1755858,2018-05-23 13:11:15 UTC,"Test 1:
iscsiadm -m discovery -t sendtargets -p 127.0.0.1
worked to activate it as needed"
1755858,2018-05-23 13:38:25 UTC,"Interesting, this worked just fine without the iscsid.conf entry as in Fedora:
  iscsid.startup = /bin/systemctl start iscsid.socket"
1755858,2018-05-23 13:43:15 UTC,"Ok, this is the code path that tries to connect.
It has a fallback to run this command.
I think we would want anyway that this is not started in a random context, but from the socket/service.
The following connect will then pick and start via the socket."
1755858,2018-05-23 13:56:47 UTC,"I have a test branch and build
+  * make iscsid socket activated to only activate it as-needed (LP: #1755858)
+    - debian/open-iscsi.socket: systemd socket file for iscsid
+    - debian/open-iscsi.service: do not start or check iscsid.service
+    - debian/rules: install and enable iscsid.socket
+    - debian/patches/iscid-conf-use-systemd.socket-patch: default to the socket"
1755858,2018-05-31 07:20:55 UTC,This now worked a few times locally (4/4) but never on Infra (3/3).
1755858,2018-05-23 16:08:39 UTC,"On Wed, May 23, 2018 at 01:58:05PM -0000,  Christian Ehrhardt  wrote:

> Fortunately we are so early in the cycle that I'd say if reviews and
> tests seem good we can change it. And if on any image/maas/cloud tests
> we break things we didn't expect there is time enough to revert it
> before cosmic is entering any Freeze.
"
1755858,2018-05-24 13:43:01 UTC,FYI: on the MP I'm iterating on different degrees of not-fun I have with dh_* in regard to control them to do exactly what I need for open-iscsi.
1755858,2018-05-30 07:25:31 UTC,"MP is reviewed and accepted, new version pushed to Cosmic as https://launchpad.net/ubuntu/+source/open-iscsi/2.0.874-5ubuntu3"
1755858,2018-05-30 08:08:58 UTC,"Also reported to Debian and linked up their bug.
It should help them just as much."
1755858,2018-05-30 13:28:35 UTC,"This worked in https://bileto.ubuntu.com/#/ticket/3268 when tested before (ppa now abandoned due to upload taking the version).
I also had amd64 tests running locally (due to that the fix to the tests that I had added)"
1755858,2018-05-30 13:44:09 UTC,"To be a bit faster (in case it is a race) than last time running with 4CPU and 2G memory this time.
$ autopkgtest --apt-upgrade --shell-fail  --no-built-binaries --apt-pocket=proposed=src:open-iscsi open-iscsi_2.0.874-5ubuntu3.dsc -- qemu --qemu-options='-cpu host' --cpus 4 --ram-size=2048 ~/autopkgtest-cosmic-amd64.img"
1755858,2018-05-23 13:58:05 UTC,Fortunately we are so early in the cycle that I'd say if reviews and tests seem good we can change it. And if on any image/maas/cloud tests we break things we didn't expect there is time enough to revert it before cosmic is entering any Freeze.
1755880,2020-12-16 22:29:19 UTC,This bug was fixed in the package doc-base - 0.11
1755887,2018-04-07 17:55:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755887,2018-04-07 18:02:03 UTC,"I'm experiencing the same issue. I tried deleting all ""Login"" keyrings, and a new one gets created every time I log in."
1755887,2018-08-01 10:09:30 UTC,I have the same on 16.04
1755898,2018-04-29 19:04:05 UTC,"This should be fixed in Ubuntu 18.04 LTS, can you please check?"
1755898,2018-04-26 17:28:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755901,2018-08-01 11:07:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755903,2018-03-14 20:31:40 UTC,RIP Stephen Hawking
1755903,2019-09-19 15:12:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1755909,2018-03-22 13:45:44 UTC,This is the exact same traceback as bug 1719436; marking as duplicate.
1755909,2018-03-29 15:58:17 UTC,"ok not a dupe, oops."
1755918,2018-03-14 22:11:24 UTC,"Actually, the root cause is something which Mozilla seems to have forgotten implementing in Firefox 59:"
1755918,2018-03-15 00:22:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1755918,2018-03-17 06:43:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755918,2018-07-30 13:48:14 UTC,"Problem is, that some systems with ubuntu-defaults-it , ubuntu-defaults-zh-cn and ubuntu-defaults-baltix packages installed doesn't have line
intl.locale.requested=""""
in /usr/lib/firefox/distribution/distribution.ini"
1755936,2019-07-07 12:35:55 UTC,See bug #1770632 for follow up.
1755936,2018-03-14 22:58:35 UTC,"u3833@vttre56002:~$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ PS/2 Elantech Touchpad                  	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ Integrated IR Camera: Integrate         	id=9	[slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C         	id=10	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=11	[slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                  	id=13	[slave  keyboard (3)]"
1755936,2018-03-25 11:29:19 UTC,"I tested the new version. Now it it starts, unfortunately it disables not only the TrackPad, but also the TrackPoint same time. As I researched a bit, it seems that that Elantech Trackpoint and TrackPad is only one device not like Synaptics before :-("
1755936,2018-04-02 08:37:08 UTC,I did some testing in meanwhile.
1755936,2018-04-02 09:02:57 UTC,Please run touchpad-indicator from terminal.
1755936,2018-04-02 09:20:43 UTC,"Hi Lorenzo,
thanks for looking at it. Here is the output of the terminal, when disabling and enabling the ""touchpad"" from the menu."
1755945,2019-05-28 21:45:50 UTC,ran both scripts - did not find any issues
1755945,2018-03-14 23:36:09 UTC,"I think the first time it failed was in this patch:
https://reviews.mahara.org/#/c/8122/"
1755952,2018-03-15 00:35:04 UTC,"In the mean time use, https://github.com/thesourcerer8/altium2kicad"
1755952,2018-12-18 12:37:30 UTC,"Hi All,"
1755952,2018-12-16 18:56:26 UTC,"@JP, it was one of our developers who was working on it.  I will let that developer come forward to discuss it if they are willing.  I didn't realize Peter (Clifton) was working on Altium tool.  I haven't talked to Peter for a long time so this must be something fairly recent."
1755952,2018-12-16 18:42:39 UTC,"@Wayne,
Perhaps you are thinking about this one:
https://github.com/pcjc2/openaltium"
1755952,2018-12-16 17:43:09 UTC,"Hey Wayne,"
1755952,2018-12-16 17:04:01 UTC,Using github is fine but the actual project is hosted on launchpad so we would not be able to do a merge in the same way we can when you use git on launchpad.  You can send patches to the developers mailing list[1] for review.
1755952,2018-12-16 15:44:27 UTC,Hi Cé-
1755952,2018-12-16 18:12:26 UTC,"@Cedric, this is not the Altium2kicad conversions tool.  It is an actual plugin similar to the Eagle plugin that we currently have.  AFAIK, the primary difference is that the Eagle file format (greater than version 6) is xml and the Altium file format is a binary format that uses MS OCX controls which may have restrictions on reverse engineering.  This is what I know from the developer but it's been a few years since this discussion occurred so I may not be remembering this correctly.  The developer's mailing list is definitely the proper place to discuss this."
1755952,2018-12-16 14:12:27 UTC,"I would like to start coding this feature. This is the first time I'm trying to code anything for KiCAD. Where do I begin? Should I make a fork from here: https://github.com/KiCad/kicad-source-mirror ,then make a new branch, and send pull requests when I have made progress?"
1755952,2018-03-28 11:34:47 UTC,"About the Altium files formats, I can list the main and correlate with KiCad:
.SchDot : sheet template -> .kicad_wks
.SchDoc : schematic -> .sch
.PrjPcb : project -> .pro
.PrjPcbStructure : rules about rooms (blocks of schematic that repeat) -> ?
.PcbDoc -> .kicad_pcb
.SCHLIB / .LibPkg / .IntLib : symbols and footprints -> .lib / .kicad_mod
.rep / .dat -> .dcm?
.DsnWrk : group projects .PrjPcb -> It have not a correspondent on KiCad
.OutJob : configuration to output GERBERS / PDF / ... -> It have not a correspondent on KiCad
.xml : BOM -> .xml (Use a total diferent format of KiCad, see https://github.com/xesscorp/KiCost/blob/master/kicost/eda_tools/altium/altium.py and do not need to be converted)
.pas : Pascal code for some kind of project initialization -> ?"
1755952,2018-03-28 06:34:32 UTC,"@Russel,"
1755952,2018-03-28 01:43:01 UTC,"There is also this, schematic only but at least it's in Python
https://github.com/vadmium/python-altium"
1755952,2018-03-27 21:47:53 UTC,"Not necessarily [1], but I have no idea how well developed the library is."
1755952,2018-03-27 12:09:25 UTC,Well looks like i'm learning Perl...
1755952,2018-12-16 14:19:36 UTC,"Hi All,"
1755955,2018-03-17 14:29:12 UTC,"I'm guessing that the runs completed as they should?  Were there any
inclusions that should not have been made?"
1755955,2018-03-19 18:30:23 UTC,"Yes, runs completed as they should. As far as I know -- I did not do any detailed testing, just did not see anything grossly wrong."
1755955,2018-03-21 15:34:47 UTC,"It looks like the best ordering is that they appear in the first two arguments.  Neither one needs to be first.  I'll try to verify that, but that's my impression from reading the code again."
1755955,2018-03-21 16:30:37 UTC,"That probably makes is harder to have a meaningful ""Warning"" then when exclude-device-files is not first in list [or, possible second, if exclude-if-present is first]."
1755955,2020-03-06 16:16:35 UTC,"  - Removed warning and will now allow these two to
    be in any order.  If encountered outside of the
    first two slots, duplicity will silently move
    them to be in the first two slots.  Within those
    two slots the order does not matter."
1755962,2018-03-19 00:31:41 UTC,"Hey zhengyong,"
1755962,2018-03-19 14:25:50 UTC,"@api('/v1/introspection/<node_id>/data', rule=""introspection:data"",
     methods=['GET'])
def api_introspection_data(node_id):
    if CONF.processing.store_data == 'swift':
        if not uuidutils.is_uuid_like(node_id):
            node = ir_utils.get_node(node_id, fields=['uuid'])
            node_id = node.uuid
        res = swift.get_introspection_data(node_id)
        return res, 200, {'Content-Type': 'application/json'}
    else:
        return error_response(_('Inspector is not configured to store data. '
                                'Set the [processing] store_data '
                                'configuration option to change this.'),
                              code=404)"
1755966,2019-08-19 14:50:06 UTC,This is effectively solved by the 19.07 release of the nova-cloud-controller which has optimisations to reduce the time taken for upgrades (it doesn't re-evaluate all of the knownhosts during an upgrade).
1755966,2018-03-26 14:36:45 UTC,This issue can also be reproduced during a deployment.
1755966,2018-07-02 11:14:18 UTC,We might be better to review TLS configuration of libvirt and change the way we do live migration rather than tackle this specific issue.
1755968,2018-03-15 03:25:49 UTC,same issue with kubuntu-18.04-beta1-desktop-amd64.iso.
1755968,2018-03-26 09:01:53 UTC,same with latest daily build(ubuntu-18.04-desktop-64bit 25-Mar-2018)
1755968,2018-04-12 09:34:24 UTC,This issue disappear in ubuntu-18.04 desktop beta2.
1755968,2018-06-23 09:14:52 UTC,"I still have the same (probably) issue (ubuntu-18.04 26 Apr)
(sorry for the screenshot)"
1755968,2018-08-31 11:54:45 UTC,I have a possibly related problem.
1755968,2019-10-08 06:21:10 UTC,"I have not  hit this issue anymore with ubuntu image (such as 18.04.2, 18.04.3, 19.04, 19.10)in ESXi."
1755968,2020-03-19 20:39:34 UTC,Changed the bug status to Fix Released due to reporter's previous message.
1755970,2018-03-15 04:05:58 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1755974,2018-03-15 04:25:50 UTC,"StacktraceTop:
 gvdb_table_new (filename=filename@entry=0x7f00d0026790 ""/home/karma/.cache/tracker/ontologies.gvdb"", trusted=trusted@entry=1, error=error@entry=0x7f00d8477ab0) at gvdb-reader.c:166
 tracker_ontologies_load_gvdb (filename=filename@entry=0x7f00d0026790 ""/home/karma/.cache/tracker/ontologies.gvdb"", error=error@entry=0x7f00d8477ab0) at tracker-ontologies.c:626
 load_ontologies_gvdb (error=0x7f00d8477ab0, manager=0x563ec9542620) at tracker-data-manager.c:3868
 tracker_data_manager_initable_init (initable=<optimized out>, cancellable=<optimized out>, error=0x7f00d8477b30) at tracker-data-manager.c:4261
 tracker_direct_connection_thread_func (self=0x563ec955d090) at /home/carlos/Source/gnome/tracker/src/libtracker-direct/tracker-direct.vala:134"
1755981,2021-01-21 08:53:45 UTC,We hit the simillar issue with follow error in nova-compute log:
1755981,2018-04-17 01:37:38 UTC,"I am thinking about that we can change the structure of ALLOCATED_PORTS, use the instance_uuid as key to record these ports are being used by specific server. Only release ports that are not used by other servers when we call serial_console.release_port() during destroy a server."
1755987,2020-01-26 23:17:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1755987,2020-01-26 23:19:12 UTC,From https://askubuntu.com/questions/1153506/how-do-i-enable-all-keys-on-the-touchscreen-keyboard :
1755991,2018-03-15 08:21:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1755999,2019-10-01 10:22:35 UTC,"This issue does not exist in D AMD64
    generic/430	 2s"
1755999,2020-05-13 08:10:09 UTC,"Passed with Focal 5.4 (5.4.0-31.35), with just 1 second to run:
generic/430	 1s"
1755999,2019-10-01 11:25:52 UTC,"BTW this hang can be found on Bionic 5.0 kernel, on ext4 / btrfs / xfs.
So it might has something to do with the userspace tools as well."
1755999,2018-09-13 09:53:15 UTC,"Old bug but still reproducible.
http://10.246.72.4/test-results/4.15.0-34.37-generic/michael__4.15.0-34.37__2018-08-28_21-18-00/xfstests/results/xfstests.ext4/debug/xfstests.ext4.DEBUG.html"
1755999,2018-03-15 07:30:07 UTC,This change was made by a bot.
1755999,2018-03-15 11:13:53 UTC,Mainline kernel bisect shows that this stuck occurs between 4.9.87 and 4.10rc1
1755999,2018-03-15 09:11:25 UTC,"There is a similar bug report [1] for NFS, and the fix has already landed in Bionic kernel [2]"
1755999,2018-03-15 08:44:48 UTC,A quick and dirty gdb debug indicates it's looping with copy_file_range syscall(326)
1755999,2018-03-21 09:00:40 UTC,This issue has gone with xfsprogs 4.15.1
1756004,2018-08-27 20:35:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756006,2018-04-13 09:10:20 UTC,"On Thu, Apr 12, 2018 at 12:41:30PM -0000, Jeremy Bicha wrote:

> Resetting to New since the g-s-d commits have been accepted upstream.
> They are the first 4 commits for 12 Apr, 2018.
>
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commits/master
"
1756006,2018-05-01 15:01:46 UTC,"The changes got commited to upstream master, we might want to backport/SRU in bionic?"
1756006,2018-05-02 17:09:39 UTC,"Well at least with what's upstream it's not working with what was committed
for me."
1756006,2018-10-01 20:40:18 UTC,"sufficiently large swapfile should be enough, as systemd has support to hibernate to a file offset.
However, none-the-less, I did not manage to resume off that myself yet."
1756006,2018-10-01 21:21:01 UTC,When I did those PR upstream I did it with a swapfile actually on Ubuntu.  The key comes down to how initramfs-tools hands off the offsets.  It's kinda a jumbled mess though.
1756006,2018-10-01 21:47:24 UTC,Try d-feet as root.  I think I recalled seeing this too.
1756006,2018-04-12 12:41:30 UTC,"Resetting to New since the g-s-d commits have been accepted upstream. They are the first 4 commits for 12 Apr, 2018."
1756006,2018-10-02 14:51:06 UTC,GNOME is discussing reverting this change for 3.30. Posted moments ago in #control-center on irc.gnome.org:
1756006,2018-10-04 14:31:18 UTC,"Mario, I believe GNOME is planning to do a gnome-settings-daemon 3.30.1.2 release soon disabling the feature by default (at compile time). See https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/78 and its attached merge proposal especially the NEWS entry."
1756006,2020-09-17 18:38:31 UTC,"This appears to no longer be a current FFe, so retitling and unsubscribing ubuntu-release."
1756006,2018-10-01 21:27:47 UTC,I used d-feet to Execute org.freedesktop.login1 org.freedesktop.login1.Manager CanSuspendThenHibernate
1756006,2018-04-06 10:09:26 UTC,This bug was fixed in the package systemd - 237-3ubuntu7
1756006,2018-10-01 19:24:20 UTC,Ubuntu 18.10 has this feature as part of GNOME 3.30.
1756006,2018-04-04 15:26:31 UTC,@superm1
1756006,2018-04-02 20:51:56 UTC,"The rename is done upstream, it's now suspend-then-hibernate.  I'm uploading systemd with these patches."
1756006,2018-03-28 14:52:57 UTC,"Gsd is pushing for the name change in systemd, so I'm going to get that
upstreamed before bringing this into Ubuntu. (Suspend to hibernate to
suspend then hibernate)."
1756006,2018-03-28 14:10:18 UTC,The systemd part is OK since it's cherry-picks - +1 for uploading that.
1756006,2018-03-15 08:01:49 UTC,Out of curiosity - do we have firmware-based hibernate [1] enabled out of the box?
1756006,2018-03-28 14:04:01 UTC,"This is an important improvement, so I have no objections from a docs and/or translators POV."
1756006,2018-03-28 10:21:39 UTC,upstream g-s-d asked for a name change but otherwise it seems fine in principle
1756006,2018-03-27 15:06:20 UTC,"(rls-bb-notfixing from a desktop perspective, it doesn't need to be milestoned but we want to review/comment on the change anyway)"
1756006,2018-03-26 16:14:26 UTC,"Actually, I guess an UIFe will anyway be required as for the gnome-settings-manager? I can't reach the Gnome gitlab today so I don't know for sure. If it does affect some user visible strings, please proceed as per my earlier comment and if the respective teams go +1 on it, we'll formally switch this bug to 'Triaged'."
1756006,2018-03-26 16:11:54 UTC,"I am generally fine with this feature, especially after Dimitri's input. So formally I approve of this FFe. But since this will also be changing user-visible strings in systemd, I *think* you will also need to have an UIFe, e.g. you will have to inform the doc and translation teams [1]. I'm not sure about this as I have no idea how systemd translations are driven as they do not seem to be handled through launchpad. It might be that both the documentation and translation teams do not provide any translation support for these packages per-se and no formal UIFe will be required."
1756006,2018-03-25 22:55:16 UTC,"From systemd point of view, the patches are relatively straight forward, and simply add ""one more way to sleep/suspend/hybernate/etc"" without affecting any other code paths or any other functionality. Thus i see little risk for landing the systemd patches."
1756006,2018-03-15 08:42:57 UTC,"No, not on modern system.  We haven't used that technology for a while."
1756006,2018-04-06 09:38:55 UTC,(cleaning up ~ubuntu-release bugs)
1756009,2018-03-15 16:56:20 UTC,"There are a couple of reasons why Mailman doesn't send a post to all regular members with delivery enabled. The post can be from a member whose ""Receive your own posts to the list?"" option is No (not metoo checked in the admin membership list), or a member whose ""Avoid duplicate copies of messages?"" option is Yes (nodupes checked in the admin membership list) is directly addressed in To:, Cc:, Resent-To: or Resent-Cc: of the incoming post."
1756010,2018-05-11 15:36:36 UTC,This change was made by a bot.
1756013,2018-03-15 13:26:51 UTC,"The main problem is that Onboard was not designed to work with GNOME3, that has restrictions, that Onboard can hardly bypass. (Onboard is also incompatible to Wayland, which is an additional issue.) There is a gnome extension for Onboard that slightly improves the situation, but a proper compatibility with GNOME 3 requires Onboard to be rewritten, having the restrictions of GNOME 3 in mind. A rewrite of Onboard started some time ago under the name of OnboardOSK; but I don't know what state OnboardOSK is in."
1756016,2018-03-15 14:24:29 UTC,@andreserl in one case the machine was manually added.
1756016,2019-09-19 11:57:36 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1756016,2018-03-15 22:01:27 UTC,"The issue here was that the MAC address used for BMC was correct, but the MAC address used for PXE booting was not correct. When I set the MAC address for PXE booting to the correct interface, enlistment worked perfectly fine."
1756016,2018-03-15 09:14:58 UTC,"James,"
1756016,2018-03-15 08:40:03 UTC,The description of the bug here actually doesn’t match the error st all.  If you are seeing
1756016,2018-03-15 08:58:55 UTC,I'll have him chime in if possible
1756016,2018-03-15 08:49:10 UTC,"Looking at rackd.log here, I see this:"
1756016,2018-03-15 09:05:52 UTC,"ohhhh, he didn't specify *all* of the mac addresses. That must be the key!"
1756016,2018-03-15 08:58:38 UTC,"@andreserl the user had entered incorrect BMC details previously to cause those errors, but isn't related to the main issue"
1756026,2018-03-15 10:58:03 UTC,"- could you attach the .eps file here?
- also, which OS, and which version of Inkscape (see Help->About)"
1756026,2018-03-15 12:23:42 UTC,No issues here importing a version of the eps file found via google image search.
1756026,2020-09-11 19:38:06 UTC,Closing because INVALID: Incomplete.
1756035,2018-04-18 21:49:26 UTC,"We, too, have a strong use case to decouple charms and bundles from channels.  A bundle should be able to refer to stable charms, and dev charms.  But today, it appears to be global to the bundle."
1756035,2019-06-25 00:58:45 UTC,Seems to be a duplicate of bug # 1677404
1756035,2019-06-25 05:47:51 UTC,"@Anastasia, only if #1677404 will actually finally cover the case of setting specific channels for individual charms in the bundle."
1756040,2018-05-09 09:03:56 UTC,We should also check into https://bugs.launchpad.net/juju/+bug/1751739 and see if there is a consistent issue here.
1756040,2019-10-31 04:07:12 UTC,Removing from a milestone as this work will not be done in 2.3 series.
1756040,2019-04-04 14:22:49 UTC,Comment #3 correctly diagnoses the issue (bad network-config) which caused cloud-init to error out.  And Comment #11 suggests that this configuration has been resolved.  I'm closing the cloud-init task here.  Please re-open if you believe there is a cloud-init issue that needs fixing.
1756040,2019-02-26 10:12:33 UTC,This appears to have been addressed and not updated in 2.5 release as well as a 2.4 release.
1756040,2018-08-01 16:31:01 UTC,"See also: https://bugs.launchpad.net/juju/+bug/1784730, could be a duplicate"
1756040,2018-04-17 16:49:26 UTC,"Closing LXD task for now as it looks like a cloud-init/nplan problem instead, the LXD plumbing seems fine."
1756040,2018-03-15 18:09:49 UTC,"Hi,
can you run:
 cloud-init collect-logs
and also get
 /var/lib/cloud/seed/"
1756040,2018-03-15 15:50:16 UTC,This is bionic top to bottom.
1756040,2018-03-15 15:35:40 UTC,"restarting my machine and disconnecting from the VPN made them work, so I
don't think it was snap Lxd or bionic at fault."
1756040,2018-03-15 15:28:30 UTC,Does manually running dhclient against eth0 in the container work?
1756040,2018-03-15 11:45:46 UTC,"I'll note that I tried just launching a bionic container using snap
3.0.0.beta5 and after ""lxc launch ubuntu:x"" and ""lxc launch ubuntu-daily:b""
neither of them came up with an IP address."
1756040,2018-03-18 10:39:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756055,2018-03-22 17:53:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756059,2020-03-07 14:32:53 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1756070,2018-03-15 13:30:06 UTC,This change was made by a bot.
1756070,2018-03-15 19:00:08 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1756070,2018-03-26 07:39:48 UTC,"Issue started after one of the updates. Prior kernel version difficult to pinpoint, since the bug seems to happen only after cold boots, not after a warm boot."
1756076,2018-03-15 14:00:03 UTC,This change was made by a bot.
1756081,2018-03-15 14:01:17 UTC,"On the bright side messages are in journal, but not if you use -u to filter.
And if a service looks like this:
  service[123]: good
  service[123]: good
  service[123]: <dead>"
1756084,2018-04-09 18:27:43 UTC,"Here is what the Query's return ran as the user.
This is a 32 bit machine."
1756084,2018-04-09 16:29:42 UTC,"Thanks for the details, Lynn."
1756084,2018-04-09 15:24:41 UTC,Here is a windows 7 32 bit machine running Web Client 3.0.1 Hatch 0.1.5 and no printers show.
1756084,2018-03-22 14:56:52 UTC,"Yesterday, one of our libraries reported this issue with the same ""Hatch is disconnected when communicating with the native messaging host"" message."
1756084,2018-03-21 14:22:09 UTC,"Bill,"
1756084,2018-03-21 14:14:51 UTC,"Bill,"
1756084,2018-04-09 21:13:31 UTC,"Thanks, Lynn.  And you confirmed this file exists and is readable by the user?"
1756084,2018-03-21 13:52:39 UTC,"Bill,"
1756084,2018-03-16 14:21:52 UTC,"Can you confirm a ""lib"" directory exists in the Hatch install directory and that it includes a hatch.jar file?"
1756084,2018-03-15 19:21:59 UTC,"Bill, we have tried maybe 3 times re-installing hatch and when a test is performed it gives the attached error message."
1756084,2018-03-15 16:15:00 UTC,"Thanks, Robert.  This appears to be an installation issue.  The browser is unable to talk to the Java service.  My next suggestion would be to try the step listed in ""Optional: Test Hatch"" to see if the Hatch script (which runs the Java executable) runs OK."
1756084,2018-03-15 15:16:45 UTC,Attached is the console that is seen on one of the effected work stations.
1756084,2018-03-15 14:31:23 UTC,"Hi Robert, could you check the contents of the extension browser console that are logged when then page is loaded and/or when navigating to the printer admin page?"
1756084,2018-03-21 14:03:28 UTC,"Robert, for the PC with no lib directory, the installer simply failed somewhere along the way.  So that's problem 1.  Curious what happens if you re-run the installer."
1756087,2018-04-24 10:44:58 UTC,Note that this is still happening on xenial/queens with 18.02 charms.
1756098,2018-04-02 19:33:22 UTC,"If you have time, could you try starting from Ubuntu 17.10, then upgrade to 18.04 and see if you can reproduce the issue? You're welcome to use a virtual machine to make testing easier."
1756098,2018-04-02 23:57:14 UTC,"Sure, when I get a moment I'll firstly try to reproduce the issue with bionic by installing 3.27.92 and upgrading to 3.28 again. Then if I can confirm that the issue really does happen, I'll try an upgrade from artful (3.26.1). (I hope this was only an issue within the development branch and therefore not affect ""real"" users, but we'll see)."
1756098,2018-04-04 21:45:38 UTC,"I've not yet been able to reproduce this yet, but while investigating I've found that the cache folder for gnome-software (and therefore the gnome software flatpak plugin) has changed from 17.10 to 18.04 - so it might not be an issue for ""real"" users upgrading from 17.10?"
1756105,2018-09-08 11:47:02 UTC,"Not a fix for S0i3, but the latest X1 6th Gen BIOS (1.30) now has a power option to enable S3 without having to patch."
1756105,2018-03-29 23:21:17 UTC,"fyi almost all of the time after suspending it will wake up at some point. but there is an small upside to that; closing/opening lid ""works"". battery drain is definitely lower during suspend compared to ec_no_wakeup=0"
1756105,2018-03-21 08:29:29 UTC,"thanks! that helps indeed. it's not completely preventing wake-up events it seems, as usually after longer period it wakes up, but it definitely helps reduce power consumption. I'll experiment some more to see if/how I can influence the wake-up."
1756105,2018-03-17 10:58:58 UTC,note that in previously mentioned thread on lenovo forum the workaround used is to enable S3 by patching DSDT tables. for those interested: see https://bbs.archlinux.org/viewtopic.php?id=234913
1756105,2018-03-17 10:45:19 UTC,have the same issue. tried latest mainline http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc5/ but this does not fix the issue.
1756105,2018-03-15 18:54:18 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1756105,2018-03-15 15:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1756105,2018-03-19 13:03:15 UTC,please pass `acpi.ec_no_wakeup=1` on the Linux command line to reduce the power consumption.
1756107,2019-08-07 19:02:33 UTC,UI has been deprecated
1756118,2019-12-15 11:12:32 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/699115"
1756118,2020-03-09 20:21:05 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/train
Review: https://review.opendev.org/699115"
1756118,2020-01-21 13:39:03 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/699116"
1756118,2020-01-21 13:38:57 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/699117"
1756118,2019-12-15 11:13:40 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/699117"
1756118,2019-12-15 11:13:04 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/699116"
1756118,2019-12-06 23:05:52 UTC,"Reviewed:  https://review.opendev.org/589769
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4bb54ae86981d186e41dcc325d171ab951beb7b6
Submitter: Zuul
Branch:    master"
1756118,2018-03-15 15:41:11 UTC,OK removed the 'wishlist' tag if this used to work. FWIW nothing obvious jumps out at me for recent changes in the libvirt driver for the 'compare_cpu' code.
1756118,2019-10-09 08:38:11 UTC,"It is true that libvirt does not know how to detect host CPU model on AArch64, but even if it _wants_ to know, it cannot, because even the `/proc/cpuinfo` on AArch64 doesn't show anything interesting.  There are lots of vendors making different AArch64 CPUs, and they are not easily comparable.  They all differ in various ways.  (This is also confirmed by Jiri Denemark of libvirt.)"
1756118,2018-08-08 21:15:38 UTC,Lowering this to Medium as it's been regressed since Queens.
1756118,2018-08-08 09:15:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589769"
1756118,2018-04-05 02:18:25 UTC,Marking it as High because it's a regression in Queens.
1756118,2018-04-05 02:16:32 UTC,"Okay, according to the BZ comment [0], it's expected that libvirt doesn't know how to detect the CPU model on AArch64. And in the past, it was wrongly being reported by libvirt, which was a bug in libvirt."
1756118,2018-03-15 15:25:08 UTC,This isn't a 'bug' since it was never supported before anyway.
1756118,2018-03-15 15:27:04 UTC,For us it is a regression as on Newton with libvirt 2.2.10 live migration from nova level on aarch64 worked fine.
1756118,2019-10-09 09:01:42 UTC,In theory those fields from /proc/cpuinfo could be used to at least know are we trying to migrate to same CPU:
1756126,2018-03-15 17:16:00 UTC,"not reproduced on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06), using the command-line:
inkscape --without-gui -f \Windows\Temp\test.svg -e ""\Windows\Temp\test.png"""
1756126,2018-03-15 17:32:20 UTC,"No, this is in a batch but they're all .svg."
1756126,2018-03-15 18:21:17 UTC,"Not reproduced here either, but I could not check the piping part as I'm on Windows 10, too."
1756126,2018-03-15 22:06:00 UTC,"1. It does not.
2. 0.92.2 says that's not a valid option."
1756126,2018-03-15 22:34:13 UTC,"I believe the syntax for this option is:
inkscape --without-gui --convert-dpi-method=none"
1756126,2018-03-16 00:04:01 UTC,"> 1. It does not.
"
1756126,2018-03-16 12:50:34 UTC,None of that works.  Attaching the file and output.
1756126,2020-09-21 12:33:48 UTC,Closing because INVALID: Can't replicate.
1756129,2018-03-15 16:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1756129,2018-10-04 22:13:32 UTC,This behavior is still seen even in 4.18.0.1002 proposed azure kernel for Cosmic 18.10 release (daily builds).
1756132,2018-03-16 22:03:54 UTC,As You can check in https://github.com/openstack/networking-odl/blob/master/networking_odl/qos/qos_driver_v2.py#L33 networking-odl qos driver supports currently only bandwidth limit rule so You will be able to attach to such ports only QoS policy with such rule types.
1756132,2018-03-19 15:34:31 UTC,Rajiv is currently working at high priority on the issue with below review being the first step towards resolution:
1756137,2018-03-15 16:54:38 UTC,Adding keystone to get OpenStack charms on the radar. Keystone may or may not require documentation updates.
1756138,2018-03-19 07:47:45 UTC,One initial error (although not at step2) is expected. Did you follow https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/director_installation_and_usage/#sect-Replacing_Controller_Nodes
1756138,2018-03-19 10:22:40 UTC,"yes ...
the issues is trigger after the new controller is added manually into pacemaker ..."
1756138,2021-02-17 17:07:04 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1756142,2020-08-03 21:28:56 UTC,Removing pullrequest tag as the comments indicate it may need additional changes.
1756142,2018-04-04 00:12:33 UTC,"So, these max_chunk_size and max_bundle_count values would go in the API definition for the affected open-ils services? If that's the case, I'd be willing to try it in conjunction with Dan's patches to see if that resolves the issues for me."
1756142,2018-03-27 17:06:16 UTC,"In addition to max_chunk_size (for supporting older OpenSRFs), I think it would be a good idea to also add:"
1756142,2018-03-27 16:21:18 UTC,"Bill, that's interesting.  I was beginning to wonder if there might be some regression lurking in here somewhere.  Also, since there is no official way to link that I know of, putting a reference to bug #1754164 on here as well (copy location specific)."
1756142,2018-03-20 13:28:12 UTC,"I am wondering if we might have two different bugs in this interface.  I've done much of my testing using srfsh, as the original problem seems to manifest there as well using the following command:"
1756142,2018-03-27 16:04:12 UTC,"Another data point, I just updated from OpenSRF 2.4 to OpenSRF 2.5.  One large API call (open-ils.circ.copy_location.retrieve.all) that worked fine in 2.4 is now failing in the same way as the reporter templates, with an apparent timeout after 6 seconds."
1756142,2018-03-20 19:02:10 UTC,"Mike,"
1756142,2018-03-19 19:58:39 UTC,NOTE: The error message also appears with line 560.
1756142,2018-03-27 16:20:51 UTC,"Maybe not the best solution, but a quick solution in my case was to add max_chunk_size => 0 to the API definition."
1756142,2018-03-19 18:35:36 UTC,"I suspect that this may be an old-xul-client-has-old-opensrf-JS issue.  Blake, does your staff client match the server's version of opensrf?"
1756142,2018-03-15 17:43:32 UTC,Here is a fix for master (top two commits):
1756142,2018-03-15 17:48:45 UTC,2.12 version:
1756142,2018-03-15 18:13:41 UTC,We've seen this since our upgrade to 2.12 last fall with one folder in particular. We split it up into four separate folders.
1756142,2018-03-19 19:55:34 UTC,I see no output at all and get this in the console over and over again:
1756142,2018-03-16 01:40:06 UTC,But now it's working.... not sure what's up with that.
1756142,2018-03-16 01:46:06 UTC,"Yeah, it's back to broken again. I am feeling like it's responding to the javascript call before it has the complete set of data."
1756142,2018-03-19 18:32:49 UTC,Dan's branch seems to definitively resolve the issue with template folders for me.
1756142,2018-03-16 01:36:48 UTC,"After loading the patch, I can sometimes get an error in the XUL client when opening an output folder with only one result:"
1756147,2018-03-15 23:32:30 UTC,apport information
1756147,2018-03-15 23:32:33 UTC,apport information
1756147,2018-03-15 23:32:34 UTC,apport information
1756147,2018-03-15 23:32:35 UTC,apport information
1756147,2018-04-30 03:05:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756147,2018-03-15 17:45:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1756147"
1756160,2018-03-20 14:55:49 UTC,"Ralph Gauges, can you please attach all files which you have in /etc/cups/ppd/? Please attach the files one by one, do not compress them and do not package them together."
1756160,2018-03-15 22:24:54 UTC,"StacktraceTop:
 mime_compare_srcs (f0=<optimized out>, f1=<optimized out>) at filter.c:285
 cups_array_add (a=0x7fb760450810, e=0x7fb760364ed0, insert=insert@entry=0) at array.c:1134
 cupsArrayAdd (a=<optimized out>, e=<optimized out>) at array.c:103
 mimeFilter2 (mime=0x55adb9656550, src=src@entry=0x55adb9670800, srcsize=srcsize@entry=0, dst=0x55adb97e8610, cost=cost@entry=0x0) at filter.c:199
 mimeFilter (mime=<optimized out>, src=src@entry=0x55adb9670800, dst=<optimized out>, cost=cost@entry=0x0) at filter.c:150"
1756160,2018-03-16 16:59:10 UTC,Reported upstream as
1756164,2018-03-22 09:12:31 UTC,"For future travellers - I think nova-lxd will also need to be aware that the storage is ceph backend, and that for migrations the block storage does not need to be migrated - but that may be handled directly in LXD anyway."
1756164,2018-03-22 09:11:19 UTC,"Adding ceph support is a little more involved as we'll need to add a relation to a ceph-mon cluster, and configure LXD as required to support this backend."
1756169,2018-03-17 15:08:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756169,2018-10-26 16:49:20 UTC,It is multi repetitive popups after start-up.
1756172,2019-09-13 15:45:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756172,2019-09-13 15:47:35 UTC,"I am starting to configure Ubuntu to use smartcard auth, and am running into similar issues.  I'll note though that I have to modify /etc/pam.d/common-auth to work with a smartcard and pam_sss.  I'm curious to know what your PAM configuration is."
1756179,2018-06-28 13:16:21 UTC,"Is it possible to backport these fixes to stable/pike, too?"
1756179,2018-07-05 20:35:18 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/580498"
1756179,2018-07-05 20:38:54 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580499"
1756179,2018-07-09 19:31:50 UTC,"Reviewed:  https://review.openstack.org/580498
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd50dcaf3e51722c9510d417c1724d8cdafe450b
Submitter: Zuul
Branch:    stable/pike"
1756179,2018-07-09 19:51:54 UTC,"Reviewed:  https://review.openstack.org/580499
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9fe847bdca39627b4d1741d2c5807ebca7101d2e
Submitter: Zuul
Branch:    stable/pike"
1756179,2018-09-24 14:46:52 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1756179,2018-06-08 12:25:45 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1756179,2018-09-24 19:59:21 UTC,"Reviewed:  https://review.openstack.org/603749
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94848ca40f9bce9c53b820bbfe66eb3d2d181afc
Submitter: Zuul
Branch:    stable/ocata"
1756179,2018-10-08 21:49:15 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1756179,2019-05-03 19:42:39 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657021"
1756179,2019-06-21 08:32:47 UTC,"Reviewed:  https://review.opendev.org/657021
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8921a470ee797cd75def387ce184ee0ffaae6517
Submitter: Zuul
Branch:    master"
1756179,2018-09-19 13:02:55 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/603749"
1756179,2018-06-04 13:52:30 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1756179,2018-07-09 12:29:14 UTC,"Reviewed:  https://review.openstack.org/580491
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8dd4c6195434a1e271ad8cd7fbd66d4801a4cba
Submitter: Zuul
Branch:    stable/pike"
1756179,2018-05-22 08:20:07 UTC,"Reviewed:  https://review.openstack.org/563236
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cba1a3e2c1b161204a3662a0d9fbf33da38aa7d3
Submitter: Zuul
Branch:    stable/queens"
1756179,2018-05-22 08:31:31 UTC,"Reviewed:  https://review.openstack.org/563698
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dede2de2bd482d0378a7acd81b65d93b1635e825
Submitter: Zuul
Branch:    stable/queens"
1756179,2018-03-21 13:21:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554920"
1756179,2018-04-11 20:04:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/560626"
1756179,2018-04-20 05:47:02 UTC,"Reviewed:  https://review.openstack.org/560626
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a80ac96362c8fafba1bfe71244b52ba2f082c86e
Submitter: Zuul
Branch:    master"
1756179,2018-04-20 17:05:55 UTC,"Reviewed:  https://review.openstack.org/560706
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ea9d0af31395fbe1686fa681cd91226ee580796e
Submitter: Zuul
Branch:    master"
1756179,2018-04-20 18:51:33 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/563229"
1756179,2018-03-15 20:58:58 UTC,"The change will also require a release note since nova-api today does not require having the [placement] section of nova.conf configured, but this would require that in order for nova-api to talk to placement-api to delete things."
1756179,2018-04-23 16:27:40 UTC,"Reviewed:  https://review.openstack.org/554920
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=589c495c1ae62129e20ab5e2641e330541eee01f
Submitter: Zuul
Branch:    master"
1756179,2018-04-23 16:57:18 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/563698"
1756179,2018-05-16 18:31:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/568925"
1756179,2018-05-19 01:55:45 UTC,"Reviewed:  https://review.openstack.org/568925
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3abd5f5797737b54c10ea85d4b833aff054d1bee
Submitter: Zuul
Branch:    master"
1756179,2018-05-20 18:35:07 UTC,"Reviewed:  https://review.openstack.org/563229
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bcd462e49b4d51e78e9f31c60cd9e4d9fd8f99f9
Submitter: Zuul
Branch:    stable/queens"
1756179,2018-04-20 19:00:38 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/563236"
1756190,2020-02-06 18:23:49 UTC,"I tested this and I believe ksc/osc is not affected by this, the server-side changes were enough to return the correct result."
1756190,2019-03-05 17:49:28 UTC,"Change abandoned by Nicolas Helgeson (<email address hidden>) on branch: master
Review: https://review.openstack.org/554327"
1756190,2018-04-19 19:30:54 UTC,This issue was fixed in the openstack/keystone 14.0.0.0b1 development milestone.
1756190,2018-03-27 21:36:14 UTC,"Reviewed:  https://review.openstack.org/553108
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4b572e564dcd5d9f8f608caba922f844f24cbc00
Submitter: Zuul
Branch:    master"
1756190,2018-03-19 19:25:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554327"
1756190,2018-03-20 20:46:59 UTC,"This may affect KSC as well, see [0]."
1756190,2018-03-19 17:11:13 UTC,"Hi Rajat, this bug should be fixed once patch https://review.openstack.org/#/c/523499/ has been merged."
1756190,2018-03-16 09:16:45 UTC,"I have reproduced this bug, on my env, for ""not-tags-any=blue"" it is still return both p1 and p2."
1756190,2018-03-15 21:59:32 UTC,"This follows with the API-WG spec[0]'s example on combining tags, the example given is currently not possible with ""exact"" matching vs subset."
1756190,2018-03-21 16:52:26 UTC,"jessegler noticed that Lance's example when testing the keystone fix was passing in a list of tags as opposed to a comma-delimited string of tags into KSC, which currently is not supported."
1756201,2019-07-04 16:05:33 UTC,Issue about to be fixed in 18.04.
1756201,2018-09-02 18:48:20 UTC,Seems to be a problem with 18.04 too.
1756201,2018-03-17 10:26:32 UTC,see 2nd entry
1756201,2018-03-17 10:31:21 UTC,I got xsane running by copying the content of /usr/lib/x86_64-linux-gnu/sane from the old Ubuntu 14.04 (64 bit) installation to the same location in my Ubuntu 17.10 (64 bit) install.
1756201,2018-05-29 08:08:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756209,2018-03-26 03:03:01 UTC,"Just to keep this up to date, they have now committed a patch to fix this."
1756209,2020-09-10 23:03:45 UTC,"Hello Thomas, or anyone else affected,"
1756209,2020-09-13 01:42:44 UTC,"All autopkgtests for the newly accepted glibc (2.27-3ubuntu1.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1756209,2020-10-21 16:21:20 UTC,"Bionic has already been fixed.
I could not reproduce the issue even with 2.27-3ubuntu1.2."
1756209,2020-11-02 18:30:28 UTC,"The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1756215,2018-03-19 09:10:20 UTC,"Reviewed:  https://review.openstack.org/554099
Committed: https://git.openstack.org/cgit/openstack/puppet-heat/commit/?id=8921d8b0c01568bd71671558e8275cf486d38226
Submitter: Zuul
Branch:    stable/queens"
1756215,2018-03-23 02:55:45 UTC,"Reviewed:  https://review.openstack.org/554104
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=aae889c32f77831181fc8dc7db9b6dd593da41f2
Submitter: Zuul
Branch:    stable/pike"
1756215,2018-03-29 00:10:19 UTC,This issue was fixed in the openstack/puppet-ceilometer 12.5.0 release.
1756215,2018-03-29 00:11:44 UTC,This issue was fixed in the openstack/puppet-heat 12.4.0 release.
1756215,2018-03-29 00:13:32 UTC,This issue was fixed in the openstack/puppet-nova 12.4.0 release.
1756215,2018-04-19 21:03:48 UTC,This issue was fixed in the openstack/puppet-nova 13.0.0 release.
1756215,2018-04-19 21:01:34 UTC,This issue was fixed in the openstack/puppet-heat 13.0.0 release.
1756215,2018-03-19 07:21:12 UTC,"Reviewed:  https://review.openstack.org/554100
Committed: https://git.openstack.org/cgit/openstack/puppet-heat/commit/?id=dab3e556ce50b4e4ff972fe845131c214acff3bd
Submitter: Zuul
Branch:    stable/pike"
1756215,2019-05-16 23:02:43 UTC,This issue was fixed in the openstack/puppet-ceilometer 11.6.0 release.
1756215,2019-05-16 23:04:01 UTC,This issue was fixed in the openstack/puppet-heat 11.6.0 release.
1756215,2019-05-16 23:06:27 UTC,This issue was fixed in the openstack/puppet-nova 11.6.0 release.
1756215,2018-04-19 20:59:09 UTC,This issue was fixed in the openstack/puppet-ceilometer 13.0.0 release.
1756215,2018-03-19 06:25:12 UTC,"Reviewed:  https://review.openstack.org/554103
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=9db79a61176288dceb384f8fef731f74b8ac3434
Submitter: Zuul
Branch:    stable/queens"
1756215,2018-03-16 22:37:02 UTC,"Reviewed:  https://review.openstack.org/553647
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=3ad015b57d8d02d3d6360c312c05ba971e0212bd
Submitter: Zuul
Branch:    master"
1756215,2018-03-19 06:06:25 UTC,"Reviewed:  https://review.openstack.org/554102
Committed: https://git.openstack.org/cgit/openstack/puppet-ceilometer/commit/?id=f2f2d2b97bdd562ee347e78237ad537b9a604eca
Submitter: Zuul
Branch:    stable/pike"
1756215,2018-03-16 01:10:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553645"
1756215,2018-03-16 01:17:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553646"
1756215,2018-03-16 01:25:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553647"
1756215,2018-03-16 22:16:38 UTC,"Reviewed:  https://review.openstack.org/553645
Committed: https://git.openstack.org/cgit/openstack/puppet-ceilometer/commit/?id=c7b7671f973b7df8b7bc5fc10ba633010a726545
Submitter: Zuul
Branch:    master"
1756215,2018-03-16 22:47:29 UTC,"Reviewed:  https://review.openstack.org/553646
Committed: https://git.openstack.org/cgit/openstack/puppet-heat/commit/?id=6fd473247164bf54a14a78e8930ce57b843ee843
Submitter: Zuul
Branch:    master"
1756215,2018-03-19 06:06:35 UTC,"Reviewed:  https://review.openstack.org/554101
Committed: https://git.openstack.org/cgit/openstack/puppet-ceilometer/commit/?id=069b04271b123e63f2c0aed19cbb05bed6209bad
Submitter: Zuul
Branch:    stable/queens"
1756215,2018-03-19 03:38:18 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554100"
1756215,2018-03-19 03:38:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554101"
1756215,2018-03-19 03:38:58 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554102"
1756215,2018-03-19 03:39:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554103"
1756215,2018-03-19 03:39:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554104"
1756215,2018-03-19 03:38:02 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554099"
1756219,2018-04-15 04:45:06 UTC,Unsubscribing the Ubuntu Sponsors team as there's nothing to sponsor yet. Please resubscribe us when you have something ready.
1756222,2018-03-16 02:07:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553651"
1756222,2018-06-24 03:21:53 UTC,"Change abandoned by Yafei Yu (<email address hidden>) on branch: master
Review: https://review.openstack.org/553651"
1756228,2018-06-15 06:56:50 UTC,Increased allowed precision in commit 5244c0.
1756234,2018-04-02 18:04:55 UTC,I also got this error. Could you try destroy ceph containers and deploy again?
1756234,2018-04-02 18:17:03 UTC,"Yeah, I was able to solve this issues by destroying all the images and containers and re-install everything all over."
1756236,2018-03-22 09:10:49 UTC,"Reviewed:  https://review.openstack.org/554011
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=4605f230846c7bedfe499840afc1ca5a622a239f
Submitter: Zuul
Branch:    master"
1756236,2018-03-16 03:56:00 UTC,"@Ji.Wei,"
1756236,2018-03-17 20:25:34 UTC,"Hi Ji.Wei,"
1756238,2018-03-31 21:50:22 UTC,This bug was fixed in the package vte2.91 - 0.52.0-1ubuntu2
1756238,2020-09-22 21:25:05 UTC,In groovy the code for vte-keep-FD patch has been refactored to support new upstream code.
1756238,2018-08-14 19:28:44 UTC,"I have the exact same problem in Ubuntu 18.04.1 tottaly updated, including backports. Mark Smith #26 commentary works with me also. I think the gdebi-gtk when not opened from terminal, crashes when I have to type me password"
1756238,2018-08-14 18:20:31 UTC,I *might* have a possible clue for the gdebi gui crash in Bionic.
1756238,2018-08-03 17:37:18 UTC,"I just did a clean install of Xubuntu 18.04.1 and then installed gdebi and its frontend.
The interface crashes for me so it hasn't been fixed. The back-end might work from the command line but the gui is broken."
1756238,2018-06-21 18:55:35 UTC,"The verification of the Stable Release Update for vte2.91 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1756238,2018-06-21 10:14:42 UTC,Let's just mark it as done so the team's tools see that it is fixed
1756238,2018-06-06 19:35:37 UTC,As far as I was concerned this bug was already fixed in:-
1756238,2018-06-06 17:33:55 UTC,"Hello Mark-pcnetspec, or anyone else affected,"
1756238,2018-05-31 22:07:52 UTC,This bug is Fix Released in bionic. The reference is only included in LP-Bugs-Fixed because I copied the previous merge entry and then built the source package with -v. Sorry that that's confusing.
1756238,2018-05-31 19:44:25 UTC,"Thanks for uploading the fix for this bug report to -proposed.  However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process.  You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential.  Thanks in advance!"
1756238,2018-03-31 23:04:58 UTC,"vte2.91 (0.52.0-1ubuntu2) fixes it, thanks everyone."
1756238,2018-03-31 21:42:42 UTC,Ideally gdebi should be fixed not to rely on this patch. Obviously that's somewhat more work.
1756238,2018-11-17 11:51:04 UTC,There is a error into the /usr/share/polkit-1/actions/com.ubuntu.pkexec.gdebi-gtk.policy file:
1756238,2018-03-31 20:47:18 UTC,"Egmont, see https://bugzilla.gnome.org/show_bug.cgi?id=320128 (mentioned in the patch header)."
1756238,2018-03-23 15:04:54 UTC,"In my Ubuntu 18.04 Beta 1 the gdebi program does not install any deb packages, but when I click install package it crashes and closes. I am installing through dpkg on the terminal."
1756238,2018-03-30 00:25:19 UTC,Any update on this ?
1756238,2018-03-30 16:36:51 UTC,Maybe this is related to the fix for LP: #1719746 and the reason why the %f option was dropped in Ubuntu 17.10.
1756238,2018-03-30 17:53:33 UTC,"No it's not that clicking the .deb doesn't fire up gdebi-gtk (it does), it's that gdebi-gtk crashes whilst installing the .deb throwing the error:-"
1756238,2018-03-30 18:18:38 UTC,"One other person suggested that updating vte from 0.50 to 0.52 triggered this bug
LP: #1758918"
1756238,2018-03-30 18:55:13 UTC,"Yep, definitely something in vte 0.52 because downgrading to 0.48 by installing these packages from artful:-"
1756238,2018-03-20 18:27:52 UTC,Same problem here using Ubuntu 18.04 beta 1.  Did an update and now gdebit doesn't even ask for a password.  But does work in terminal.
1756238,2018-03-31 19:41:11 UTC,"I can reproduce the bug, and I also get the same (faulty) result with vanilla vte-0.48 compiled by me (that is, not the Ubuntu package, contrary to comment 7)."
1756238,2018-03-30 19:02:51 UTC,I may have gone overboard with libvte-2.91-0-udeb which isn't a default package so is unnecessary.
1756238,2018-03-31 20:44:27 UTC,"Ok, I'm going to go ahead and restore the patch for now to fix gdebi."
1756238,2018-03-31 21:22:24 UTC,"for what it's worth, 91_keep_fds.patch fixes libvte-2.91-0 for me."
1756238,2018-03-31 19:54:17 UTC,"Which, of course, raises the question:"
1756238,2018-03-31 19:46:07 UTC,"Yup, with manually compiled vte-0.53, this patch fixes the problem."
1756238,2018-03-31 20:42:58 UTC,Looks like 91_keep_fds.patch was something that never made it upstream when originally added.
1756243,2019-08-07 19:02:20 UTC,UI has been deprecated
1756246,2018-03-16 11:11:30 UTC,"I think these strings may be coming directly from the Ironic API data, and so not easily translatable from the UI."
1756246,2019-08-07 19:00:55 UTC,UI has been deprecated
1756250,2019-08-07 19:00:42 UTC,UI has been deprecated
1756251,2018-03-16 11:19:47 UTC,"It looks like it is marked as translatable, albeit in an unusual format: https://github.com/openstack/tripleo-ui/blob/master/src/js/components/nodes/NodesListView/NodeListItem.js#L41-L44"
1756251,2019-08-07 18:59:36 UTC,UI has been deprecated
1756253,2018-03-16 11:22:11 UTC,It looks like the Status line is not translatable on that page:
1756253,2019-08-07 19:02:10 UTC,UI has been deprecated
1756258,2018-03-19 10:30:14 UTC,"Hi,"
1756258,2020-03-22 04:17:24 UTC,[Expired for GNU Arm Embedded Toolchain because there has been no activity for 60 days.]
1756262,2018-07-10 10:52:13 UTC,"Hi Puneet,"
1756262,2020-01-25 18:56:57 UTC,"Due to a long inactivity here and no reproduce steps provided as asked in the previous comment, I'm gonna assume the reporter's issue got resolved and mark this as Invalid. If you still encounter the issue, please, provide more information and feel free to reopen this bug."
1756266,2018-03-19 07:33:36 UTC,"I found the problem. In my stack template, i define resourcegroup depends_on a waitcondition. And when i remove depends_on , everything will be ok. I think you need to check the logic of updating action."
1756266,2018-03-16 08:24:00 UTC,The log is below:
1756266,2018-03-16 08:07:44 UTC,Can you describe how it failed? Can you attach the logs? Thanks.
1756266,2018-03-16 12:01:53 UTC,"I just tested it and it seems to work as expected on master, I don't think anything has changed since pike for it to not work too."
1756285,2018-03-16 11:46:57 UTC,you check syslog for any denials you get when the snap is used in strict mode and a controller is attached ?
1756285,2018-03-16 13:15:38 UTC,"I did now, I get these two:"
1756285,2018-03-16 13:37:07 UTC,"hmm, clearly unrelated (thats a known issue with teh screensaver inhibition)"
1756285,2018-03-16 13:50:28 UTC,There's this whole block that didn't appear in strict mode.
1756285,2018-03-16 14:23:08 UTC,"there you go, the joystick interface needs to allow access to the input device at:"
1756285,2018-03-16 14:24:47 UTC,aaand it looks like https://github.com/snapcore/snapd/commit/82616efcbb4fac3c4a9d2e4846f8ebec7821055b#diff-4a1da2e3f7e118a874d308ec61d7d055 already has the fix in snapd's master tree ...
1756285,2018-03-16 14:27:58 UTC,"hmm, in fact https://forum.snapcraft.io/t/joysick-access-for-sdl2-apps/3027/7 says it has been merged into snapd 2.30, that should actually be in use everwhere."
1756285,2018-03-16 14:34:52 UTC,"First of all thanks for all the help so far, really appreciate it :)
On Fedora the output is
snap    2.31.1-2.fc27
snapd   2.31.1-2.fc27
series  16
fedora  27
kernel  4.15.8-300.fc27.x86_64"
1756285,2019-10-01 22:45:51 UTC,I happen to have both gamepads available and I can give that a try. For now I'm marking this as confirmed.
1756287,2020-06-12 13:42:22 UTC,It seems to have been fixed.
1756287,2018-12-19 04:18:34 UTC,"Hi, I just tried out new queens kolla, still has this error. Tried few ways to fix it but has no clue at all. Tried install plugin manually inside docker, no luck. Please if anyone has any idea, please help."
1756287,2018-04-12 12:30:05 UTC,"Marking as invalid as I think this is a kolla bug, not a Mistral one. Let me know if there is something that needs fixed in Mistral."
1756287,2018-04-09 11:08:47 UTC,"Hello zhubingbing,
I deployed Openstack Pike and Queens by kolla-ansible versions 5.0.0 and now 6.0.0.
I deployed completely new Openstack and I also tried to upgrade from Ocata to Queens, but the same error appears in Dashboard.
Latest working version of Mistral has been in Openstack Ocata and kolla-ansible 4.0.2
If you want more information, logs and so on, let me know."
1756287,2018-03-19 14:55:31 UTC,please give me more inforamaiton
1756287,2018-05-10 11:57:24 UTC,"Hi Sir Dougal,"
1756291,2018-03-16 10:17:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/553743"
1756291,2018-08-31 07:42:35 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1756291,2018-08-31 07:42:45 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/553743
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1756291,2018-09-22 04:10:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604501"
1756291,2018-09-24 23:49:11 UTC,"This is not a bug. The DNS extension was implemented to use the Public URL in Designate. So my next question is, why do we need this? In what use case this is necessary?"
1756291,2018-09-25 08:17:46 UTC,"IIUC talking about publicURL/internalURL only makes sense when using an auto-discovered endpoint from the service catalog. But neutron is using the fixed URL configured in the designate.url config variable anyway, so where would this endpoint type come into play at all?"
1756291,2019-01-08 08:38:51 UTC,"Looking at the designate driver, designateclient instance is configured by keystoneauth1 load_session_from_conf_options [1]. The suggested way is to use keystoneauth. The other way with password.Password is a legacy one. Do you see an improvement in keystoneauth load_session_from_conf_options?"
1756291,2020-03-24 21:52:03 UTC,"Due to lack of any activity in this RFE since more than 1 year, I'm going to close it for now. If You would be still interested in implementing this and would like to continue discussion on that, feel free to reopen it and ping me (slaweq) on irc."
1756296,2019-12-13 10:46:28 UTC,Thx for info Thomas. So I will now move this rfe to postponed state.
1756296,2018-10-26 14:03:34 UTC,"what do you plan to use instead of NORMAL action?
something similar to ofagent?
https://github.com/openstack/networking-ofagent/blob/stable/mitaka/networking_ofagent/plugins/ofagent/agent/flows.py#L100-L102"
1756296,2019-11-29 08:59:52 UTC,"Hi Thomas,"
1756296,2019-11-29 09:19:19 UTC,Slawek: no I don't intend to work on this in the near future
1756311,2018-11-29 14:42:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756311,2018-12-24 00:00:18 UTC,"Happens to me randomly, I think scheduled by the systemd timer. When fstrim is called on the root mount it instant hangs the entire system forever. Mouse and keyboard do respond but anything requiring disk access wont be accessible anmore."
1756315,2020-09-15 05:45:59 UTC,"Hello Alexandre,"
1756315,2019-08-23 09:27:18 UTC,Update to my previous comment ... running fstrim on 4.15.0-58-generic result in much more reported trimmed data (206.6 GiB) vs 4.15.0-55-generic (144.4 GiB) (e.g. this was not caused by snapshot release). On 4.15.0-58-generic I see errors like this in kernel log:
1756315,2019-08-23 08:57:36 UTC,I can confirm this bug on Ubuntu 16.04.6 LTS. Apparently it is related to latest kernel update (in my case HWE).
1756315,2018-03-16 14:39:17 UTC,Can you try the following?
1756315,2018-12-05 00:18:15 UTC,I ran into this issue on 14.04 and 16.04 as well. Ubuntu 18.04 does not seem to be affected.
1756315,2018-12-05 00:16:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756315,2018-03-21 13:21:24 UTC,Hello David!
1756315,2018-12-05 09:20:03 UTC,"I did some quick testing with some different kernel versions on Ubuntu 14.04, the issue seems to exist in versions up to 4.10 but with 4.11 it is fixed."
1756319,2018-03-16 12:24:19 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/553770"
1756319,2018-03-23 10:10:02 UTC,"Change abandoned by yolanda.robla (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/553770
Reason: this was not a cherry-pick but i agree, better to do it with that"
1756319,2018-03-27 04:44:48 UTC,"Reviewed:  https://review.openstack.org/553768
Committed: https://git.openstack.org/cgit/openstack/tripleo-image-elements/commit/?id=122d921d8a0139acb34735b9785a4c4429cb90cc
Submitter: Zuul
Branch:    stable/pike"
1756319,2021-02-19 15:52:03 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1756319,2018-03-16 12:21:59 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/553768"
1756329,2018-03-28 14:08:51 UTC,We should add a section in the docs (in https://docs.openstack.org/designate/latest/admin/production-guidelines.html) to point out you need to turn off the recursion
1756329,2020-03-09 14:50:19 UTC,Bind won't stop you from creating and deleting domains that already exist upstream.
1756331,2019-06-07 20:21:47 UTC,Closing as Pike is EOL. This was likely due to an out of date tripleo-common
1756337,2018-04-06 06:57:38 UTC,Due to https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997020 I switched this to 'Confirmed'.
1756337,2018-03-16 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1756337,2018-03-16 13:25:58 UTC,"Hi There,"
1756349,2018-03-16 20:44:53 UTC,Richard Hipp just committed a fix in sqlite master. Apparently this must be https://www.sqlite.org/cgi/src/timeline?r=corrupt-schema
1756349,2018-03-17 00:16:09 UTC,Use CVE-2018-8740.
1756353,2018-04-06 08:29:33 UTC,"The action ""nova.floating_ips_findall"" was recently removed as it was deprecated in novaclient - that may be the cause of this failure. Either way the Mistral engine shouldn't get stuck."
1756354,2018-03-16 15:20:05 UTC,Similar symptoms https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati-hwe-16.04/+bug/1750393
1756357,2019-09-19 12:05:12 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1756362,2018-03-16 16:23:19 UTC,"It is also worth noting that the task-list and action-execution-list are paginated (but exection-list isn't, because reasons). They will only show the first 100 by default"
1756362,2018-03-16 16:22:16 UTC,Are you looking for this? I think it might give you the output you want?
1756362,2018-04-06 08:22:17 UTC,"I believe this didn't show up due to the pagination, and thus isn't a bug in Mistral. It is best to filter with the Mistral API or CLI args rather than grep."
1756362,2021-02-17 17:10:25 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1756366,2018-12-11 16:40:20 UTC,"The links is broken, file not found."
1756366,2021-02-17 17:10:29 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1756369,2018-08-18 10:09:38 UTC,Confirmed here too. Calendar application is not synced with my Google account which is in my Online Accounts in settings which do work for my e-mail from gmail etc...
1756369,2018-05-15 10:48:18 UTC,"Confirmed here too. When I go to the Calendar application nothing is synced while my Google account is added to my Online Accounts in settings. When I go to Calendar -> Calendars -> Google (click to setup) and log into my Google Account, after I click Allow to allow Gnome Calendar to use my Google account, the window disappears and nothing happens."
1756369,2018-10-23 11:57:44 UTC,Also in Ubuntu 18.10 - can t log in Google Calendar
1756369,2018-05-14 00:34:49 UTC,Another confirmation . i m including an image of my error code.
1756369,2018-09-03 16:38:49 UTC,I have the same issue on 16.04. Using Online Accounts to add my Google account does give me my Drive files. But the calendar is not listed (options only for files & photos). The Gnome Calendar is empty.
1756369,2018-05-09 12:42:34 UTC,"Another confirmation. But if I try to sync calendars manually, I have a form for auth in Google. But if I enter right login/password I have error ""HTTP error code 401 (Unauthorized)""."
1756369,2018-03-29 23:16:15 UTC,Another confirmation.  Installed the EDS and it changed or fixed absolutely nothing.
1756369,2018-05-14 00:33:36 UTC,another confirmation.
1756369,2018-03-23 11:32:59 UTC,"I can confirm. Fresh install on daily Ubuntu 18.04 (2018-03-23).
I installed evolution and gnome-calendar and it won't sync in neither of them.
Also doesnt sync in gnome global menu in the time/date menu."
1756369,2018-03-16 16:44:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756389,2018-03-20 15:20:07 UTC,We just discussed this on IRC - I'm not happy with the proposed solution of inserting a delay into the startup file like this. It'll make timeouts and it's not really acceptable to have calendar events broken for 60 seconds in my opinion.
1756389,2018-03-16 16:58:01 UTC,bootchart with ev-cal-factory delayed by 1 minute.
1756389,2018-03-20 14:44:32 UTC,Could you please propose this upstream (with a patch if you can) ?
1756401,2018-03-19 23:16:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756401,2020-08-07 13:29:27 UTC,Artful is EOL and other supported releases have received a newer openjdk version so marking as fix released.
1756405,2018-07-24 13:59:53 UTC,FactoryOwners.Permanent=yes (previously: FactoryOwners.HaveAllPlans=) should now work on building upgrades. Change is available in the latest unstable testing build.
1756407,2018-03-17 15:05:28 UTC,"The entering of amount is not that much complex you describe:
- if you use tab from the date, the amount is selected and typing 80 + enter seize what you want with 3 key typing.
- ctrl+a into the amount select all and enable doing the same
- the amount enable to enter . and , as well
- the amount is plugged to a spin, I should probably remove (but some people use it to adjust some cents)"
1756407,2018-03-17 21:25:01 UTC,"Merci Maxime,"
1756407,2019-08-03 16:34:25 UTC,"Yeah, I think adding a calculator would be redundant considering the amount of programs that already exists with that purpose (a big part of them even included by default in most moderns systems), would be great to keep homebank KISS when possible. However, i agree with Kreyer with the + and - buttons being quite useless!"
1756407,2020-05-04 14:45:31 UTC,"from #1865155
when you click on the amount widget (or widget get focus) AND the amount is 0.00
empty the text"
1756414,2018-04-11 12:21:39 UTC,This bug was fixed in the package linux-azure - 4.15.0-1004.4
1756414,2018-03-30 03:39:41 UTC,I'd rather move to the 4.15 kernel than spend time applying these patches to 4.13.
1756414,2018-03-29 23:44:36 UTC,Should we include those changes to the 4.13 azure kernel in xenial?
1756414,2018-04-02 19:36:34 UTC,This bug was fixed in the package linux-azure-edge - 4.15.0-1005.5
1756418,2018-03-29 14:34:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756418,2018-04-07 04:56:52 UTC,"same problem for me on ubuntu bionic beaver beta 18.04
Any solution yet ?"
1756418,2018-04-07 04:58:34 UTC,seem to be same as bug#1754999 reported march 11.
1756420,2020-10-09 21:41:47 UTC,"And by HVM support, I actually mean PV support, doh."
1756420,2020-10-09 21:40:42 UTC,I am going to mark this as won't fix for cloud-images.
1756420,2018-03-27 13:23:22 UTC,"grub-legacy-ec2 is now successfully split out of cloud-init, so I've closed the cloud-init task."
1756420,2018-03-23 20:22:08 UTC,I opened up bug 1758420 to handle the split out of grub-legacy-ec2.
1756420,2018-03-16 19:28:24 UTC,"I looked a bit further, started to file a MIR bug for pv-grub-menu.  It seems like pv-grub-menu is not likely a simple drop in fix."
1756426,2018-12-13 18:00:11 UTC,"Not sure I've set all the tracks and such correctly above.
The fix for this issue went into the ubuntu seeds during the cosmic release [1]."
1756426,2018-03-28 13:28:48 UTC,"Can we milestone this bug for fixing in 18.04 ?
I've milestoned, if you disagree, please feel free to respond and un-do."
1756426,2018-03-19 14:38:42 UTC,"This is removed by line 32 in https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/ubuntu-cpc/hooks/032-root-squashfs.binary#L32, which strips out all grub packages from the image (as the image isn't expected to require a bootloader)."
1756426,2018-03-19 14:59:33 UTC,This is really a general policy issue. Ubuntu default policy is that packages should have their recommends installed by default.
1756426,2018-03-22 21:42:53 UTC,I agree that it is a bug for official Ubuntu images to subset the standard seeds in a way that deviates from the definition for those images.
1756428,2018-06-20 15:27:10 UTC,"I can't change that, because that would change behavior for everyone."
1756431,2018-04-04 16:08:15 UTC,"@sunweaver Could you perform a test build in an Ubuntu PPA with armhf and arm64 enabled and report back if the package builds correctly in Ubuntu on all arches (with logs)? I think once we have certainty that the new version does no longer FTBFS, I'd be glad to approve the FFe."
1756431,2018-03-20 20:29:37 UTC,"1) yes, functionality-wise by Martin Wimpress (local build, I presume), I myself test-built in a bionic sbuild chroot"
1756431,2018-04-06 10:20:06 UTC,"Hi,"
1756431,2018-03-20 15:42:54 UTC,"Sorry, the correct / new version is 2.0.93-2."
1756431,2018-03-20 15:42:25 UTC,I (Debian maintainer) just uploaded 2.0.93-1 fixing co-installability of ayatana-indicator-power and indicator-power.
1756431,2018-03-16 19:42:35 UTC,I have subscribed the authors of these commits should anybody have any questions.
1756431,2018-03-20 16:40:44 UTC,A few things I would like to know before proceeding:
1756437,2018-12-09 16:13:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756441,2018-09-26 17:13:24 UTC,Confirmed in 3.0.12ish.
1756441,2018-09-26 17:43:47 UTC,I want to add that I am working on changes to the behavior of the Mark Item functionality that will likely address this bug. It looks like these changes will be ready for Evergreen 3.3. See https://bugs.launchpad.net/evergreen/+bug/1779467
1756441,2019-07-31 13:59:37 UTC,"Confirmed in the 3.3.2 web client.  I'm seeing the same errors in osrfsys.log after checking in an item that triggers a transit, and then trying to mark it damaged. No error is given to the user."
1756441,2019-09-11 17:15:40 UTC,Removed reference to xul client in description.
1756446,2018-04-03 16:18:08 UTC,Both staging and production have been updated now.
1756446,2018-03-30 16:59:06 UTC,This bug was fixed in the package whoopsie - 0.2.60
1756446,2018-03-30 15:49:51 UTC,I've fixed this in daisy revision number 793 and submitted an RT regrading updating staging.
1756446,2018-03-17 16:29:55 UTC,Indeed without the error logs it's often difficult to guess what the issue is. Even some limited sample or filtered values would be better than having nothing included as today.
1756446,2018-03-30 15:37:20 UTC,Rather than having to futz about changing the number of lines of JournalErrors collected in SRUs I've modified whoopsie to upload the whole JournalErrors file however daisy will only write the last 50 lines to the database.  By having this in daisy we can adjust the number of lines as needed without having to SRU whoopsie multiple times.
1756454,2019-08-07 18:59:51 UTC,UI has been deprecated
1756457,2018-05-29 07:21:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756459,2018-03-20 14:18:58 UTC,Fixed with the 2.1 upload as well.
1756459,2018-04-26 14:36:05 UTC,Any chance this gets fixed for Xenial?
1756461,2018-03-16 23:47:42 UTC,"Hello again,"
1756472,2018-03-17 04:24:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1756474,2020-07-02 03:07:23 UTC,"Setting up samhain (4.1.4-2build1) ...
Job for samhain.service failed because a timeout was exceeded."
1756474,2020-07-02 04:02:29 UTC,related to:
1756474,2019-02-23 14:14:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756474,2018-03-17 01:43:46 UTC,Hmm?
1756474,2019-02-23 14:19:48 UTC,Bastou entrar no modo de descanso com tela de proteção e aí que quando voltei deu essa mensagem:
1756476,2018-03-17 02:21:36 UTC,Deleted on 2013-09-25: requires xulrunner which is no longer in Ubuntu; LP: #1222330
1756476,2018-03-17 02:39:42 UTC,"Thank you for the information. It does sound like once version > 5.0 is packaged in Debian, the problem will be resolved. Hopefully at that time it can be synced to Ubuntu."
1756476,2019-10-23 13:47:53 UTC,"I liked to raise this issure again. Zotero is the only comprehensive open source citation manager and it should be available directly. Furthermore it is a standalone software, but I am note sure how much of the code is based on Firefox."
1756476,2020-01-26 01:39:53 UTC,"Work to package Zotero in Debian appears stalled. However, there is a flatpak available on flathub.org which is kept up to date and works well."
1756484,2018-03-17 03:52:34 UTC,I believe I have corrected this by changing my refresh rate from 59.99 Hz to 59.86 Hz.
1756496,2018-03-17 11:14:17 UTC,"confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1756496,2018-03-17 11:21:19 UTC,"unfortunately, it looks like there are two separate problems here. I was just able to duplicate the crash message on exit by loading a different svg file, so it is not related to the CPU hangup."
1756496,2018-03-17 17:58:27 UTC,"I really don't know what that means but if you need anything else let me
know. It seems to be related to the jpg itself but I can't tell what is
different about it from all the others that work just fine."
1756496,2018-03-19 20:10:55 UTC,"I downloaded the problem svg and the jpg.  The SVG does indeed hang Inkscape, making it unresponsive."
1756496,2018-03-20 16:17:07 UTC,"Could it be my cpu/ram are not robust enough for something?  The weird
thing is though it is only a few images not all of them! I have had similar
problem with patterns I've created with the pattern maker extension. So
much so that I stopped using it."
1756502,2020-07-03 21:49:40 UTC,"libjpeg8:i386 (8d-1+deb7u1)
libjpeg8:amd64 (8d-1+deb7u1)"
1756506,2018-04-20 08:46:12 UTC,Similar issue observed with the drivers supplied with virtualbox guest additions in Ubuntu 14.04 after a regular upgrade (running the same kernel as mentioned in previous post).
1756506,2018-04-20 09:41:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756506,2018-05-02 08:40:48 UTC,"Please consider my remark above a workaround. It will load your kernel module, but it also exposes a kernel vulnerability to your system by allowing a non repoline compiled module to load."
1756514,2018-03-22 14:13:24 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/555315"
1756514,2018-03-22 09:10:58 UTC,"Reviewed:  https://review.openstack.org/554012
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=086c04b9202df8587370cab89331b903212079eb
Submitter: Zuul
Branch:    master"
1756514,2018-03-26 06:55:41 UTC,"Reviewed:  https://review.openstack.org/555315
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=0ef54adbccda8fcceba055e8cec1b40b8f467659
Submitter: Zuul
Branch:    stable/queens"
1756514,2018-03-17 22:09:17 UTC,"Hi @Yang,"
1756514,2018-03-17 21:58:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/554012"
1756514,2018-03-18 12:44:08 UTC,"Hi @hongbin,"
1756517,2018-10-03 13:19:07 UTC,"AFAIK, grub-installer (the udeb package) already has logic to install correctly on RAID systems, by using the underlying devices. This should be writing grub-*/install-devices as well, which should be taking care of package upgrades."
1756520,2018-08-29 21:39:22 UTC,It looks like this may have been related to eventlet vendoring six. That was removed in https://github.com/eventlet/eventlet/commit/53b63c66f0d9a7d6ba9182a207529ebd949e95f3 so it may not be a problem in newer versions of eventlet. Would you be able to verify that this is fixed by eventlet 0.24.1?
1756521,2018-03-17 10:41:28 UTC,"StacktraceTop:
 mount_cb (item=<optimized out>, row=0x55f460b9c570) at ../src/gtk/nautilusgtkplacesview.c:1584
 g_closure_invoke (closure=0x55f460a33660, return_value=0x0, n_param_values=1, param_values=0x7ffc643260f0, invocation_hint=0x7ffc64326070) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55f460117050, detail=detail@entry=0, instance=instance@entry=0x55f46064b4f0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc643260f0) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc643262b0) at ../../../../gobject/gsignal.c:3391
 g_signal_emit (instance=instance@entry=0x55f46064b4f0, signal_id=<optimized out>, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447"
1756523,2018-04-09 18:57:24 UTC,This is probably the same as https://bugs.launchpad.net/libtickit/+bug/1744933.
1756523,2018-04-09 19:30:39 UTC,"I'm not pretty sure they are the same error, in the bug you pointed it seems to fail with a buffer overflow and here is fails with:
""Parse errors: No plan found in TAP output"""
1756523,2018-04-09 22:52:39 UTC,"Unlikely to be related to 1744933, because these are all window-level tests, and that bug relates to the (real) term driver, which wouldn't even be used as the mockterm for these window tests."
1756535,2018-03-17 12:25:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1756535,2018-05-19 07:06:10 UTC,"This bug seems to disappear after the final release of Kubuntu 18.04.
The issue might be closed but I can't find how to do that."
1756538,2021-01-21 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1756538,2018-03-17 14:20:24 UTC,"One more: Qemu on Debian 9-10 minimal requires -show cursor command to use the mouse inside a windows guest, but with Qemu on Ubuntu minimal the cursor is controllable by default. Again, this is all within the context of an Android/Arm8/Linux minimal/Chroot-based host."
1756538,2018-03-17 19:23:31 UTC,Qemu Virtual CPU is capping at 1 GHz for version 2.5+ and 2 GHz for version 2.4
1756538,2020-11-21 14:16:40 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1756547,2020-08-27 19:54:27 UTC,"@Marco: The issue was caused by the fact that LP used an older (xenial) version of gettext. So as soon as they upgrade, it should be possible to drop the workaround. Can't tell if they have done that yet; easiest to ask Colin or William."
1756547,2020-08-27 17:52:29 UTC,Could we also add gettext to this bug so that we can monitor when it will be fixed on that side and thus remove the ubuntu workaround?
1756547,2018-04-08 10:30:10 UTC,This bug was fixed in the package gnome-shell - 3.28.0-0ubuntu5
1756547,2018-04-07 15:29:57 UTC,To the sponsor: Another upload needed; a no-change build is sufficient.
1756547,2018-04-07 12:38:19 UTC,"@gunnarhj: Sorry, no idea. The only package where I have seen this issue is gnome-shell."
1756547,2018-04-06 23:31:43 UTC,@AsciiWolf: Do you have an idea which other packages besides gnome-shell suffer from this kind of translation import problem?
1756547,2018-04-07 04:10:21 UTC,This bug was fixed in the package gnome-shell - 3.28.0-0ubuntu4
1756547,2018-03-29 07:32:34 UTC,"William, I guess you set as incomplete for launchpad before the IRC discussion? Seems the consensus was to try to backport the newest gettext and make launchpad use it, Colin started poking at that it seemed?"
1756547,2018-03-29 04:20:41 UTC,There was a long IRC discussion about this issue yesterday:
1756547,2018-03-18 15:57:52 UTC,I opened a bug task for Launchpad itself.
1756547,2018-03-18 15:34:04 UTC,"I approved, and it was imported with the very same errors."
1756547,2018-03-18 15:02:32 UTC,"I think this is rather a Launchpad issue. The msgstr[2] is commonly used in GNOME pofiles in our (Czech) language and for example in this case the msgstr[1] and msgstr[2] for ""%d years ago"" are different. I manually edited and uploaded the pofile, feel free to review it."
1756547,2018-03-17 20:43:19 UTC,"The template provides two alternatives in those cases, a singular and a plural, while some upstream Czech translator has provided three alternatives, for instance:"
1756547,2018-04-06 23:26:13 UTC,"The build of gnome-shell 3.28.0-0ubuntu4 was not sufficient to fix this. The POT file without javascript comments was imported, but LP still complained about the PO files for the affected languages."
1756548,2020-04-01 13:02:05 UTC,Closing because INVALID: Works as expected -- Lines are correctly anti-aliased for the output size/dpi.
1756553,2018-05-27 15:49:34 UTC,Update: I did a dist-upgrade and got kernel version 4.14.34-v7+ which so far seems OK.
1756553,2018-03-24 01:04:57 UTC,"Can confirm, happens as long as there is activity in X (even moving a window around is enough).
Running openbox on xserver-xorg with GL driver enabled."
1756553,2018-05-27 15:42:44 UTC,"Seeing exactly the same stacktrace here, repeated in syslog, messages and kern.log which all grew to over 800 mb and caused the root partition to run out of space. This is pretty bad since the Pi becomes completely unusable for kids -- they asked me to help because logging in at the X login prompt just causes a black screen and brings them back to the login prompt."
1756553,2018-03-19 13:39:01 UTC,"Confirmed, I am getting the same flood of trace dumps when using Xwayland on Raspberry Pi 3b with dtoverlay=vc4-kms-v3d enabled, after updating kernel to 4.9.80-v7."
1756553,2018-03-18 00:23:25 UTC,"Also confirmed that this issue occurs under the ""G2 GL (Fake KMS)"" mode."
1756553,2018-03-18 00:18:27 UTC,"I've established that this is being caused by OpenGL being enabled - I had enabled this in ""G1 GL (Full KMS)"" mode. When running in ""G3 Legacy"" I do not get these events in the syslog."
1756553,2018-03-23 15:07:50 UTC,"I'm seeing a more-general issue here.  Things (tightvncserver, conky) autostarted by almost any method (rc.local, .profile, systemD) get started in a loop forever till memory and CPU are 100% and it locks up and gets very hot.
Something basic wrong?"
1756555,2018-03-18 14:39:08 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1756564,2018-03-31 15:14:13 UTC,I've created a branch called user/sandbergja/lp1756564_add_booking_data_to_sample_data_set
1756564,2018-06-10 23:41:06 UTC,"Hi Jane,"
1756564,2018-10-20 17:46:23 UTC,"Hi Garry,"
1756564,2019-08-02 14:50:40 UTC,"Thanks, Jane.  I was able to load the data without issue and create reservations on a newly built system in the web client.  I was also not able to reproduce Garry's issues."
1756564,2019-08-03 16:27:51 UTC,"Pushed to master. Thanks, Bill and Jane!"
1756578,2018-03-19 08:45:30 UTC,Use the latest experimental version of Open Rails instead of the 1.2 stable version and your error should disappear.
1756578,2018-03-18 08:37:14 UTC,This error occurs when you don't have installed the version of XTracks or YTracks required for that route. Check the route documentation.
1756578,2018-03-18 10:20:40 UTC,"thankyou but now i installed xtracks and now when i am opening this
railindia route its showing me error i have attached that picture. please
help me in resolving this problem please help me and guide me sir."
1756579,2018-03-17 18:49:26 UTC,back-trace
1756579,2018-03-18 12:22:59 UTC,Not reproduced on Xubuntu 16.04.4 with Inkscape stable 0.92.2+68~ubuntu16.04.1
1756579,2020-09-13 05:27:15 UTC,Closing because INVALID: Can't replicate.
1756583,2018-11-11 11:19:03 UTC,"As I am going to introduce as well Account Group (maybe), please see
 #1095160 wish: possibility to add more account types"
1756583,2018-11-16 18:37:15 UTC,"The latest update on #1095160 indicates that we'll have both account types and groups, and I think it would make sense to be able to report trends for both. So yes, we can say this wish is to be able to have trend time reports for account types and groups."
1756583,2021-01-01 16:09:03 UTC,no one else seem to need this so I close.
1756585,2018-03-21 07:36:33 UTC,"Small correction for comment ""#18"": the command to selectively restore a configuration option is ""dconf write"" (not ""dconf set"")."
1756585,2018-03-21 07:25:22 UTC,The problem was caused by an old (created under Ubuntu 12.04) DCONF configuration (attached).
1756585,2018-03-20 11:31:32 UTC,"""unity"" starts again successfully. Unfortunately, I do not why."
1756585,2018-03-20 09:54:10 UTC,"I have compared the ""syslog"" messages for a failing (""unity"" startup fails) and a successful (""unity"" startup correct) login. There are some differences. But for me, they do not seem critical: in the failing case, apparently, someone tries to start a ""bamfdaemon"" which is already running; in the succeeding case, there is not such message. The cases are slightly different with respect to the services started (""udisk2.service"" versus ""fwupd.service""/""unity-fallback-mount-helper""). The failing case seems to have problems with ""nautilus""; the succeeding one with the ""gnome-screensaver""."
1756585,2018-03-19 10:06:03 UTC,"I'm not sure if it's related, but when I log in with another account (regular or administrator type), the problem doesn't appear.
Same thing if I create another account.
In my case, this bug concerns only the primary account."
1756585,2018-03-19 10:30:54 UTC,"If I create a new user, ""unity"" starts fine (for this user)."
1756585,2018-03-18 09:46:27 UTC,"Downgrading of the above packages from ""xenial-updates"" to ""xenial"" has not solved the problem. Further analysis is for the ""xenial-updates"" versions."
1756585,2018-03-19 12:06:17 UTC,I can get back my compiz config with 'setsid compiz --replace' BUT everything is lost again after reboot...
1756585,2018-03-19 08:57:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756585,2018-03-18 19:02:14 UTC,Bug may be related to https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444
1756590,2018-05-30 21:50:44 UTC,"The list looks to me like a support case waiting to happen. It might have people think they can add more ipv4 addresses as ""gateway"", and then they might not get the behavior they expect (should it be multiple gateways at the same metric? only the last applies? etc.)"
1756590,2018-08-01 13:06:48 UTC,"I don't think the risk is very high, since 'netplan generate' would surely provide helpful feedback ;)"
1756593,2018-03-17 20:30:24 UTC,"Start of the log (above is only the tail end where it gets stuck during the cpio:
root@charion:/boot# update-initramfs -u -k 4.15.0-12-generic -b /boot -t -v
Keeping /boot/initrd.img-4.15.0-12-generic.dpkg-bak
update-initramfs: Generating /boot/initrd.img-4.15.0-12-generic
Copying module directory kernel/drivers/usb/host
(excluding hwa-hc.ko sl811_cs.ko sl811-hcd.ko u132-hcd.ko whci-hcd.ko)
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/isp116x-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/ssb/ssb.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/ssb-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/r8a66597-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/oxu210hp-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/max3421-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/bcma/bcma.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/bcma-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/isp1362-hcd.ko
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/fotg210-hcd.ko
Copying module directory kernel/drivers/usb/c67x00
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/c67x00/c67x00.ko
Copying module directory kernel/drivers/usb/chipidea
Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/gadget/udc/udc-core.ko
[...]"
1756593,2020-10-23 15:38:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756593,2020-10-23 16:14:23 UTC,"Not having very serious problems with my Linux per se (Kernel: 4.15.0-122-generic i686 Bits: 32 Desktop: MATE 1.20.1 Distro: Linux Mint 19.1 Tessa) I also wonder about these irritating initramfs-tools messages saying ""ORDER ignored: not executable"", although they don't seem to be error messages: maybe it is meant that these scripts are ""not executable"".
But anyway i've got a question, maybe a silly one: Would it make sense to alter the access privileges of these scripts by giving them execute permission?"
1756595,2019-09-12 12:14:19 UTC,This bug was fixed in the package apt - 1.6.12
1756595,2019-09-12 12:14:03 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1756595,2019-09-12 12:13:46 UTC,This bug was fixed in the package apt - 1.8.3
1756595,2019-09-11 09:20:34 UTC,"Oh, as I wrote on the other bug, autopkgtest regressions all went away, except for apport, which had the usual random failure also present in earlier failures."
1756595,2019-09-11 09:17:26 UTC,"I started some multipass VMs, installed the core snap in there, checked that the snap was mounted in df."
1756595,2020-07-10 16:22:15 UTC,This bug was fixed in the package coreutils - 8.30-3ubuntu3
1756595,2019-09-05 11:58:39 UTC,"Hello Andreas, or anyone else affected,"
1756595,2019-09-02 19:34:24 UTC,"All autopkgtests for the newly accepted apt (1.8.3) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1756595,2019-09-02 15:57:28 UTC,"Hello Andreas, or anyone else affected,"
1756595,2019-06-26 11:41:24 UTC,This bug was fixed in the package apt - 1.9.1
1756595,2019-06-05 22:07:53 UTC,Just adding '-x squashfs' to the df command would fix this.
1756595,2019-09-05 15:32:00 UTC,"All autopkgtests for the newly accepted apt (1.6.12) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1756595,2018-03-29 16:14:49 UTC,This actually comes from apt (apt-pkg/deb/dpkgpm.cc) and no filtering of the df output is done.
1756597,2020-09-24 15:04:05 UTC,This bug was fixed in the package rhythmbox - 3.4.4-1ubuntu3.1
1756597,2020-09-22 20:17:30 UTC,Tracked in: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1829
1756597,2018-10-28 11:28:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756597,2018-10-29 16:08:35 UTC,rather https://gitlab.gnome.org/GNOME/rhythmbox/issues
1756597,2018-10-29 16:08:18 UTC,The issues are upstream ones and should be reported on https://gitlab.gnome.org/GNOME/gnome-control-center/issues
1756597,2020-09-22 18:02:22 UTC,"If somebody can guide me how, I am willing to help update the plugin.  This is a really frustrating problem on Rhythmbox."
1756598,2019-05-11 11:18:13 UTC,The eeschema hittest accuracy is now 5 pixels (was 0 before).
1756598,2018-03-19 23:37:39 UTC,"I'm going to set this request to allow tool options that are ""close"" to the wire on non-45° increments.  That will give you the ability to break the wire even when you aren't exactly on the grid"
1756598,2018-03-17 23:12:34 UTC,"Hi,
yes indeed (and I hadn't seen it at first) but it's not convenient : it only works if you can bring the cursor precisely on the wire, which is nearly impossible in many cases i.e. whenever the wire follows an odd slope that doesn't intersect grid points."
1756598,2018-03-18 14:24:22 UTC,Just do it at the end of a wire.
1756598,2018-03-17 21:56:27 UTC,"If you right-click on the wire, do you not get a break wire option?"
1756598,2018-03-18 14:33:57 UTC,"Here, on 4.0.7, right-clicking on the end of a wire does not offer the ""Break wire"" option."
1756614,2018-03-17 22:50:40 UTC,On closer inspection it turns out that the icon is being drawn at the right size. It looks funny because the wrong variant has been selected: light icon on a light panel. status notifier does not seem to be able to select the correct variant.
1756621,2018-04-24 17:07:05 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1756625,2018-07-20 18:22:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756625,2018-07-20 18:25:00 UTC,Similar problem with bionic. gnome-calculator suddenly stopped working. here is the terminal log.
1756625,2018-07-27 11:11:17 UTC,Similar problem after update Ubuntu Bionic Beaver gnome-calculator stopped working.
1756627,2018-03-18 02:42:24 UTC,"This happens if you have the package ""ayatana-indicator-application"" installed. Note that although it appears to be stealing the indicators, they don't show up in indicator-plugin instead."
1756627,2019-01-19 23:04:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756633,2019-05-22 22:54:47 UTC,"All releases of Ubuntu (except for Ubuntu 12.04 ESM, where the kernel does not support early microcode loading, and the changes to add support are significant and would likely introduce regressions) received backported intel-microcode updates for Spectre/Meltdown."
1756633,2018-03-28 01:27:01 UTC,"@sdeziel -- I have tested on an Ivy Bridge era (i5-3427U) and Apollo Lake era (N3350) system thus far. The former is covered by the Intel 20180312 release, the latter is not. If time permits I'll also test on a Skylake system."
1756633,2018-03-18 12:02:18 UTC,"So far, the intel-microcode package has been kept in sync between all the supported releases. They all get the ""stable"" version at the same time. If you'd like to help testing, there is version 3.20180312.0 that is currently in QA and available from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa."
1756633,2018-03-22 08:53:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756638,2018-09-26 05:11:37 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/404
1756638,2018-03-18 09:41:32 UTC,"Distance (and with it, abs. magnitude) is computed from the parallax value given in the source catalog. Is there a specified lower end for reliable parallax?"
1756643,2018-03-18 09:56:45 UTC,It looks like you are using Windows from the screenshot. Is that correct?
1756643,2018-03-18 10:14:31 UTC,"Yes I am Using windows 10 Home 64-bit Version.
I just tested this on the Mixxxdj 2.1 Beta and yes it does crash after the current recording is double clicked. It may not crash at first but after 2-5 times it does crash by giving repeated error messages like in the previous Screenshot."
1756643,2018-09-15 22:55:23 UTC,"I do not think it is appropriate to fix this trivial bug in a point release. While it is not great that Mixxx crashes, there is no use case for the attempted behavior so this does not interfere with normal operation of the application."
1756643,2018-09-18 03:10:23 UTC,"A crash bug is always critical importance. See:
https://www.mixxx.org/wiki/doku.php/launchpad_bugs#bug_importance_guidelines"
1756643,2018-09-20 16:15:46 UTC,"When I try to load a recording in progress to a deck, Mixxx doesn't crash but it goes into an infinite loop of popping an error message that the file cannot be loaded that I can't get out of."
1756643,2018-09-20 16:18:26 UTC,(using master)
1756646,2018-04-06 18:24:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756647,2019-04-05 18:51:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756650,2018-03-18 09:56:04 UTC,This is the most recent screenshot of the installer I can find where it gives any helpful information on this screen. Notice that even back then it didn't say the name of the software or the version!
1756650,2018-03-18 10:05:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1756650,2018-05-01 10:02:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756650,2018-05-01 10:03:08 UTC,Sounds like an intentional design decision (in order to keep the release notes fresh and online only).
1756650,2018-05-01 11:30:22 UTC,It only sounds intentional after you changed the title of the bug to be something other than what I reported.
1756650,2018-03-18 09:31:41 UTC,As an absolute bare minimum this screen should say the name and version of the software you are about to install.
1756651,2018-03-18 10:05:38 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1756656,2018-03-18 12:27:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1756659,2018-03-18 12:27:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1756660,2018-04-23 05:21:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756664,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1756674,2018-03-18 13:01:41 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
 __GI_abort () at abort.c:79
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8c300b0b9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f8c300b23f0 ""malloc_consolidate(): invalid chunk size"") at malloc.c:5350
 malloc_consolidate (av=av@entry=0x7f8c302e5c40 <main_arena>) at malloc.c:4441"
1756681,2018-03-25 17:06:08 UTC,"Hey,"
1756681,2020-02-22 15:30:43 UTC,"Hi Maxime,
For some reason, I cannot log into Launchpad.  It shows me logged in and
when I go to the Homebank site and click report bug, it gives me an Oops
messages."
1756681,2019-08-03 16:48:26 UTC,"I think the current design just do the work and adding tabs will only bloat the window, and require extra clicks to load any transference. I love the design as is today, the only comment i would make is that i almost never used the + & - buttons in the ammount field to add cents. HomeBank is really great! Thanks for such software @mdoyen !"
1756681,2019-06-06 06:54:17 UTC,That could work well. Thanks.
1756681,2019-06-06 06:41:55 UTC,"I have choosen to do like some other tools do with a txn type at the top.
see screenshot of future txn dialog."
1756681,2020-01-15 21:43:04 UTC,"Hi Maxime,
I need to report a serious bug but the system won't allow me to log in so I
can't create a new bug report.  I installed 5.3 and I have noticed that
when you click the (-) sign next to the amount, to create an expense, the
end number changes.  It adds the negative sign and changes the last number.
I have noticed this several times when my balance was off.  For example, I
need to add an expense of $100.00 but when I click the (-) sign to make it
negative, it changes the value to -$100.01.  When I test it and try it
again, it does the same thing.  Any number that I add and then hit the (-)
sign, it adds the negative sign and then changes the last number.  Is this
supposed to add a negative sign or change the value?"
1756681,2018-05-16 11:51:29 UTC,"Hello,
Having multiple entry points for a transaction may confuse folks.  I do
like only having one, personally, but I do forget to click the positive or
negative button at times and then have to go back and fix it.  I have never
used the plus or minus on the right-hand side of the amount.  Funny part is
that I hadn't even thought about it until you mentioned it.  I just
highlight the amount input area and enter the value (I guess you could have
a popup dialogue that opens when you click the amount area,  with a number
""pad"" to select the click the numbers, to enter the amount value...that
might be handy).  it is the following step that I forget occasionally,
which is to add the negative....by default it is positive which is okay.  I
still think the best workflow would be to reverse the Payment and Amount so
that the type of payment selected would automatically add the positive or
negative to the Amount.  I used Money for years until it went away and that
is when I went to HomeBank.  Money didn't require a positive or negative
input since it was dependent on the transaction type."
1756681,2018-05-16 11:18:46 UTC,"After a little review of some other apps:
mmex, mint, kmymoney, quicken, money pus, ynab, moneywiz and ibank"
1756681,2018-04-15 17:51:08 UTC,"Hi Maxime and Carl,
One thing is certain : Homebank is the best successor to MS Money.
I like to use it every day, but some small details remain.
When you size a transaction 9 times on 10 it's a debit, but the default transaction in HB is still a credit : why ?
In the same vein, the default payment means on the top of the list) is a credit card. To my knowledge, at least in France, the most common one is the debit card.
Why not create a selectable default choice for the payment means (or, at least, an option to sort the list)?"
1756681,2018-03-25 18:00:30 UTC,"It is nice having them all in one dialog but if it is before the amount line, the positive and negative could auto fill based on the choice. That would be nice."
1756681,2018-06-02 09:12:06 UTC,"Money plus, like quicken has a dual input entry, directly into the register"
1756700,2019-04-04 00:35:57 UTC,"@kaihengfeng, I cc'ed you: https://bugzilla.kernel.org/show_bug.cgi?id=203147 (upstreamed because I produced it outside of Ubuntu)"
1756700,2019-03-21 18:35:44 UTC,"When I wrote the workaround, I didn't observe this:
[   60.486464] xhci_hcd 0000:05:00.3: Refused to change power state, currently in D3
[   60.486471] xhci_hcd 0000:05:00.4: Refused to change power state, currently in D3"
1756700,2019-03-21 17:16:50 UTC,I fail to see how it is not the same issue; I am receiving the same error that the commit (621faf4f) claims to fix.
1756700,2018-08-27 07:00:56 UTC,This bug was fixed in the package linux-oem - 4.15.0-1017.20
1756700,2019-03-16 09:44:33 UTC,"So it's not a same issue, please file a separate bug report."
1756700,2019-03-16 02:55:09 UTC,"I am using a ThinkPad E585, which has a Raven Ridge APU, and the problem still exists for me in kernel 4.20.15."
1756700,2019-02-14 16:14:33 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1756700,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1756700,2018-04-09 12:49:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1756700,2018-06-22 19:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1756700,2018-06-21 07:30:05 UTC,The commit isn't in upstream v4.15 stable. I'll backport it to Bionic.
1756700,2018-04-23 12:52:04 UTC,This bug was fixed in the package linux-oem - 4.13.0-1024.27
1756700,2018-04-10 05:46:44 UTC,All external USB ports work correctly in -1023.
1756700,2018-04-05 14:27:12 UTC,"I don't see the SAUCE patch in bionic nor upstream, so it'll take quite some time to get there.."
1756700,2018-03-26 09:35:36 UTC,"The patch I sent has Cc: linux-stable, so Bionic will get this via upstream stable update."
1756700,2018-03-26 09:16:51 UTC,shouldn't this apply to bionic too?
1756700,2018-08-07 14:01:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1756704,2019-10-09 16:20:53 UTC,I am also able to confirm this issue. I've worked it around in the following way:
1756704,2019-03-12 15:28:13 UTC,I can confirm this issue.
1756704,2018-05-15 05:57:35 UTC,I also confirm this issue.
1756704,2018-04-02 20:58:43 UTC,I confirm this issue.
1756704,2018-07-27 23:53:03 UTC,"I confirm this issue. It's very troublesome since I do development primarily on a Windows box and all my text files are CR/LF (Although when I check out my files on macOS or Linux they are LF only), but this is quite annoying, especially in Visual Studio Code."
1756705,2018-04-27 14:37:23 UTC,"This RFE has been approved in today's Drivers meeting. The suggestion during the meeting was that the response should be an array of dictionaries, with each dictionary corresponding to one binding level"
1756705,2019-05-14 20:19:37 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.opendev.org/554508
Reason: This patch has been stale for awhile now. Moving it to abandoned to clean-up the queue. If this patch is still active, please push an update to it."
1756705,2018-08-31 07:42:29 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/554848
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1756705,2018-08-31 07:42:20 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1756705,2018-04-20 15:54:17 UTC,"I had an IRC conversation with Bob Kukura, who originally implemented HPB. He mentioned that the original intent was to expose in the API the details of the binding but the team never got to do it: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2018-04-20.log.html#t2018-04-20T15:31:24"
1756705,2018-03-20 11:32:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554508"
1756705,2018-04-13 15:54:32 UTC,"@Evgeny,"
1756705,2018-03-26 07:54:00 UTC,"Hi Miguel,
As LBaaS provider, we want be able to retrieve HPB levels info by using Openstack REST API, for configuring back-end systems out of Openstack cloud."
1756705,2018-03-22 20:22:19 UTC,"@Evgeny,"
1756705,2018-03-21 09:46:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554848"
1756705,2018-03-19 07:56:46 UTC,I think that You should talk with Neutron Drivers team members to triage it and then discuss on Drivers team meeting on IRC first
1756705,2018-04-15 06:20:19 UTC,"@Miguel,"
1756714,2018-03-18 22:12:09 UTC,"If I select a specific tspan element in the XML Editor its bounding box is marked in the drawing, but if I select a flowSpan or flowPara element there is no bounding box shown. The flowRoot element has a bounding box, but not flowRegion (although the rect inside of the flowRegion has one). Guess there can be some connection? Maybe there is some good technical reason for this, but from a user perspective it looks wrong both that the bounding boxes are not seen in the GUI and that they do not (always) show up in --query-all output."
1756714,2018-03-18 22:03:17 UTC,"This might be a curious thing to even bother to report, but I am abusing --query-all and tspans to insert inlined images in text, as a workaround for the lack of support for flowImage. It would be very nice if I could also make it work for flowing text. Was hoping that it was a simple fix like just some boolean to flip in a class, but I guess if it is not even 100 % straightforward to reproduce (at least not for flowRoot) it might be more difficult to fix."
1756714,2018-03-18 20:31:00 UTC,"- not reproduced on Windows 10, Inkscape 0.92.3pre0 (f5a6572, 2018-03-03)"
1756714,2018-03-18 21:52:52 UTC,"I created a small test SVG with a normal text and a flowing text and only the normal text (attached). Only tspan shows up in --query-all output, not any of the flow elements."
1756714,2018-03-18 22:00:04 UTC,"Sorry, I did not at first notice there was a testflow.svg attached Alvin."
1756723,2018-03-21 09:51:10 UTC,"Hi Jens,"
1756723,2018-03-21 10:55:40 UTC,"Can you verify that you are getting an SSL error when you run without the ""--insecure"" option?"
1756723,2018-03-22 05:06:05 UTC,Here is the error -
1756723,2018-03-22 13:02:09 UTC,This is strange. I'll try once more to reproduce on a fresh instance.
1756723,2018-03-23 07:34:20 UTC,"O.k., I missed one step, which strangely only seems to affect the Neutron commands:"
1756723,2018-03-23 09:42:30 UTC,"Thanx for the response.Performed unset OS_CACERT, still working fine."
1756727,2018-06-14 02:23:28 UTC,Implemented by: https://review.openstack.org/#/c/557205/
1756728,2020-11-21 14:14:36 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1756728,2021-01-21 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1756735,2019-07-24 13:37:49 UTC,Just to be clear: I don't use symbols from my old (KiCad 4) libraries in new (KiCad 5) projects.
1756735,2018-03-19 12:10:31 UTC,"The way I see it is the global lib-tables represent the libraries that are ""installed"" into KiCad."
1756735,2019-07-24 09:29:47 UTC,I also really wish this functionality was there.
1756735,2019-07-24 12:20:50 UTC,"@Seppe, this could be done but the motivation to do this is low because the new schematic file format will have the symbols embedded in the file which means that you will not have to maintain your symbol libraries tables to prevent broken symbol links."
1756738,2018-03-18 21:13:54 UTC,"StacktraceTop:
 g_wakeup_new () at ../../../../glib/gwakeup.c:161
 g_main_context_new () at ../../../../glib/gmain.c:656
 pk_client_get_details (client=0x560409456c80, package_ids=0x7fb9c8159060, cancellable=cancellable@entry=0x7fb9bc1c9c20, progress_callback=0x7fb9fa9dcc30 <gs_plugin_packagekit_progress_cb>, progress_user_data=progress_user_data@entry=0x7fb9d0ff87b0, error=error@entry=0x7fb9d0ff8878) at pk-client-sync.c:363
 gs_plugin_packagekit_refine_details2 (error=0x7fb9d0ff8878, cancellable=0x7fb9bc1c9c20, list=0x56040d472140, plugin=0x56040939b3a0) at ../plugins/packagekit/gs-plugin-packagekit-refine.c:366
 gs_plugin_packagekit_refine_details (error=0x7fb9d0ff8878, cancellable=0x7fb9bc1c9c20, flags=383923654, list=0x56040a6f2980, plugin=0x56040939b3a0) at ../plugins/packagekit/gs-plugin-packagekit-refine.c:515"
1756741,2018-03-24 11:47:26 UTC,"Hello Manolo,"
1756741,2018-04-11 12:00:58 UTC,"Hello,"
1756741,2018-03-25 18:01:49 UTC,"/usr/share/ppd/HP isn't used by my Debian (and, I suspect, your Ubuntu) hplip. Move it out of the way if you are bothered."
1756741,2018-03-25 16:04:27 UTC,"ok, done."
1756741,2018-03-24 09:36:46 UTC,"Hi Brian,"
1756741,2018-03-22 18:33:47 UTC,"Hello Manolo,"
1756741,2018-03-22 18:19:44 UTC,"Hi Brian,"
1756741,2018-03-21 13:48:33 UTC,"Dear Afshan,
Thanks for your reply."
1756741,2018-03-21 19:04:26 UTC,"> I experience the problem when connecting my Kubuntu 17.10 machine
> with the device via wifi. The wifi settings on the device and on
> the wifi-modem are ok since another Linux machine (Ubuntu 16.04)
> perfectly prints and scans via wifi.
"
1756741,2018-03-19 10:57:54 UTC,"Hi Manolo,"
1756741,2018-03-22 17:45:07 UTC,"Hello Manolo,"
1756741,2018-03-22 12:07:44 UTC,"Dear Brian,"
1756742,2018-06-06 01:10:13 UTC,"The verification of the Stable Release Update for nplan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1756742,2018-06-06 01:09:38 UTC,This bug was fixed in the package nplan - 0.32~17.10.4
1756742,2018-05-08 20:50:35 UTC,"Hello Mark, or anyone else affected,"
1756742,2018-04-18 14:17:24 UTC,"Upload of netplan.io 0.35 that resolves this is in bionic unapproved queue now. Once that lands, I'll reupload finish-install."
1756742,2018-05-14 20:44:12 UTC,Verification-done on artful: nplan 0.32~17.10.4
1756742,2018-03-21 20:07:04 UTC,"While I added the right ""breadcrumbs"" in finish-install; I've also updated the text in netplan.io postinst. I'm preparing a release for that and some other smalls bugs right now."
1756742,2018-03-20 17:10:52 UTC,This bug was fixed in the package finish-install - 2.59ubuntu2
1756742,2018-03-19 02:56:38 UTC,Confirmed; finish-install includes code that only checks for the presence of /e/n/i.
1756742,2018-03-19 01:36:53 UTC,"This needs further investigation: d-i is doing something wrong if it's still writing /e/n/i, as netplan would otherwise have written the correct file on install."
1756742,2018-03-27 21:53:10 UTC,"The netplan.io in question was released, but there is a bug in the postinst that compares versions with lt-nl instead of lt, which means the breadcrumbs are not created on first install."
1756742,2018-04-18 18:38:56 UTC,This bug was fixed in the package netplan.io - 0.35
1756745,2018-03-19 14:03:18 UTC,"@Mark,"
1756745,2018-03-24 22:37:10 UTC,Will one be able to edit *and delete* a domain?
1756745,2018-03-27 19:54:34 UTC,"Yes, in MAAS 2.4 you will be able to edit any domain, and delete a domain (except the default domain). So doing what you describe should be possible if you simply rename the `maas` domain to `foo`."
1756745,2018-03-27 23:44:41 UTC,Why not enable people to switch the default domain from one to another?
1756745,2018-04-09 20:37:27 UTC,The team has always agreed that the default domain should be able to be changed; it's just a matter of priority and scope.
1756750,2018-03-21 22:42:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756761,2018-04-06 21:07:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756781,2018-03-24 21:13:41 UTC,"Yes, I think that would be very helpful. Addresses that are on the network but not recorded in MAAS are 'rogue' even if they don't conflict with anything else, because we want MAAS to be a full and accurate record of every device on the LAN."
1756781,2018-03-23 23:20:39 UTC,Good ideas. We'll see what we can do for MAAS 2.4.
1756783,2018-03-19 04:07:23 UTC,"You boot just with DisplayPort, it connected?"
1756783,2018-03-19 04:09:11 UTC,"Yes, to get both screen working... I need to boot with only the Display Port connected!
If I boot with both ports connected only the DVI one gets detected."
1756787,2018-04-04 01:58:30 UTC,https://review.gerrithub.io/#/c/406260/
1756790,2019-06-15 01:53:34 UTC,"How did you get the software in the first place? There is no download files registered with this launchpad nor in the ""Ubuntu Software"" app store, nor on the home page of the project."
1756793,2018-03-20 23:31:01 UTC,"Hi Colin,"
1756793,2018-03-20 14:22:41 UTC,"There are two recent issues in 18.04 that we're aware about. For one of them, the most trivial fix is to reboot the system. It's a problem in systemd ignoring a Condition on the snap.mount being inside a container and stopping the snap.mount unit, which chains into unmounting all snaps during the prerm which exists inside the previous deb."
1756793,2018-03-20 15:57:59 UTC,Do we have a QA process that can prevent this happening again?
1756793,2018-03-20 17:39:40 UTC,We have the fix for this issue and we will be working on making new package in proposed available ASAP
1756793,2018-03-20 17:45:41 UTC,NOTE: as a workaround you can do this:
1756793,2018-03-30 23:24:45 UTC,sudo snap refresh core --beta
1756793,2020-10-01 11:26:31 UTC,"Marking as Incomplete to let the issue expire if there is no activity. If the problem persist, feel free to post a comment."
1756793,2018-05-11 11:28:28 UTC,@flux:
1756793,2020-04-13 14:02:26 UTC,"I have the same issue on Snap Notepad-plus-plus.
Only on restart (not on the installation instance)."
1756793,2020-04-13 14:23:45 UTC,"Hey, everyone affected. Could you please post the output of ""snap version"" as a comment."
1756793,2018-03-20 14:05:13 UTC,"Having the same issue with several apps like: spotify, skype, flare-rpg
Intellij and telegram-desktop work"
1756793,2020-10-01 11:27:26 UTC,"Actually, the original problem was fixed and fix was released, so updating the status to reflect that."
1756793,2018-05-10 15:03:04 UTC,"Sorry, but this bug affects me yet. With spotify, atom and vlc I have ""snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks"". How can I resolve? Thanks
"""
1756793,2018-03-20 13:39:27 UTC,"sudo snap install spotify && snap run spotify --> ""execl failed: No such file or directory""
sudo snap install brave && snap run brave --> ""execl failed: No such file or directory""
sudo snap install mumble && snap run mumble --> Works as expected."
1756793,2018-03-19 19:49:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756793,2018-03-20 12:34:28 UTC,"Well, the ""cannot find"" is. :D"
1756793,2018-03-19 16:55:22 UTC,"If slack works and spotify fails, it might be a confinement issue"
1756793,2018-03-19 17:08:46 UTC,"sounds like ""classic confinement"" vs. ""properly confined"" to me"
1756793,2018-03-19 17:14:52 UTC,"$ snap info
snap    2.32+18.04~pre5
snapd   2.32+18.04~pre5
series  16
ubuntu  18.04
kernel  4.15.0-12-generic"
1756793,2018-03-20 13:09:14 UTC,Thunderbird --beta doesn't work either and errors out like in the Firefox snap
1756793,2018-03-19 18:53:55 UTC,I'm seeing this with firefox on 18.04
1756793,2018-03-19 18:57:52 UTC,"Same problem for me, after an update of appearance and snap 2.32, I can not start many snap."
1756793,2018-03-19 17:26:46 UTC,I cannot reproduce this on fully up-to-date bionic along with a stable core snap.
1756793,2018-03-19 16:41:13 UTC,I'm seeing this with the Spotify snap using snapd 2.32+18.04~pre5 on bionic; the Slack snap launches fine.
1756793,2018-03-19 22:46:15 UTC,I'm getting this error with other snaps as well:
1756793,2018-03-19 23:59:56 UTC,I don't know if it's the same issue as I get a different error message.
1756793,2018-03-20 12:10:30 UTC,"19681 execve(""/usr/lib/snapd/snap-device-helper"", [""/usr/lib/snapd/snap-device-helpe""..., ""add"", ""snap_spotify_spotify"", ""/sys/class/mem/null"", ""1:3""], 0x7ffdeb9a73b8 /* 0 vars */) = -1 ENOENT (No such file or directory)
19681 write(2, ""execl failed"", 12)      = 12
19681 write(2, "": No such file or directory\n"", 28) = 28"
1756793,2018-03-20 12:33:21 UTC,probably a different bug:
1756793,2018-03-20 12:34:14 UTC,Alan: Yours is really a different bug. A reboot fixes it or running the versioned postinst code in https://github.com/snapcore/snapd/blob/master/packaging/ubuntu-16.04/snapd.postinst#L15
1756793,2018-03-19 19:31:48 UTC,"I do not know if they can be useful, but I place other logs that I found"
1756801,2018-03-29 00:28:28 UTC,"Oh, I see this was encountered using 18.04.14."
1756801,2018-04-01 13:58:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756801,2018-03-19 06:10:43 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x28c12b0, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x28c12b0) at ../../../../gobject/gobject.c:3204
 g_weak_ref_get (weak_ref=<optimized out>) at ../../../../gobject/gobject.c:4379
 g_settings_backend_invoke_closure (user_data=0x7fe74001ae00) at ../../../../gio/gsettingsbackend.c:263
 g_main_dispatch (context=0x2512c60) at ../../../../glib/gmain.c:3177"
1756801,2018-03-29 00:27:36 UTC,This was fixed in mate-tweak (18.04.6-1)
1756806,2018-03-19 07:58:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554156"
1756806,2018-03-21 14:18:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554932"
1756806,2018-03-21 15:08:43 UTC,"Change abandoned by Zhao Chao (<email address hidden>) on branch: master
Review: https://review.openstack.org/554932
Reason: This should be submitted by accident, please keep updating the original one:"
1756806,2019-01-10 03:14:51 UTC,"Reviewed:  https://review.openstack.org/554156
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=88464d89612ae8150c73db52a4e3555961853fc1
Submitter: Zuul
Branch:    master"
1756813,2019-05-16 23:04:42 UTC,This issue was fixed in the openstack/puppet-keystone 11.6.0 release.
1756813,2018-04-19 21:02:10 UTC,This issue was fixed in the openstack/puppet-keystone 13.0.0 release.
1756813,2018-03-20 04:05:24 UTC,"Reviewed:  https://review.openstack.org/554162
Committed: https://git.openstack.org/cgit/openstack/puppet-keystone/commit/?id=5eb9a3f393822569df73e60efc5c1136e81826f4
Submitter: Zuul
Branch:    stable/queens"
1756813,2018-03-29 00:12:22 UTC,This issue was fixed in the openstack/puppet-keystone 12.4.0 release.
1756813,2018-03-19 08:18:39 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554163"
1756813,2018-03-19 08:18:23 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554162"
1756813,2018-03-19 08:17:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554161"
1756813,2018-03-20 01:51:00 UTC,"Reviewed:  https://review.openstack.org/554161
Committed: https://git.openstack.org/cgit/openstack/puppet-keystone/commit/?id=364150a55389da79fae11b8f38997204e6c8f7ea
Submitter: Zuul
Branch:    master"
1756813,2018-03-23 05:30:00 UTC,"Reviewed:  https://review.openstack.org/554163
Committed: https://git.openstack.org/cgit/openstack/puppet-keystone/commit/?id=4de23ac5cefb38b63524d170f9eb7adf0bbeba3a
Submitter: Zuul
Branch:    stable/pike"
1756815,2018-03-19 08:35:26 UTC,solution: modify /sys/devices/platform/dell-laptop/leds/dell\:\:kbd_backlight/stop_timeout
1756815,2018-03-19 12:28:59 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1756815,2018-05-25 17:35:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756815,2018-09-07 21:59:01 UTC,modifying the stop_timeout file fixes it but after the next software update its set back to 60secs
1756821,2019-09-19 11:57:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1756824,2019-01-23 22:20:14 UTC,"I understand the nature of LTS, but its frustrating to me as the owner of a DELL xps 13 to be hamstrung by how slowly drivers/firmwares get into LTS. This bug has been around for almost a year now and nothing. Why use LTS if I have to use 2+ year old hardware because its so slow accepting patches..."
1756824,2018-05-26 19:18:12 UTC,It's probably not. This issue described here is specific for intel hardware (8260 and 8265) and its fixed already in upstream firmware specific for these intel cards.
1756824,2019-02-08 17:29:21 UTC,I built a package with the bluetooth firmware files from the bug updated from the tip of linux-firmware. Can you please give this a try and confirm it fixes your issue? Thanks!
1756824,2018-05-26 11:46:52 UTC,I think it is the same as https://askubuntu.com/questions/1032417/ubuntu-18-04-lts-bluetooth-discovery-not-working
1756824,2018-03-19 13:40:13 UTC,"linux-firmware version 1.173
Ubuntu 18.04"
1756824,2018-03-19 13:55:01 UTC,apport information
1756824,2018-03-19 13:55:00 UTC,apport information
1756824,2018-03-19 13:54:59 UTC,apport information
1756824,2018-03-19 12:09:31 UTC,"Can you please indicate which Ubuntu release you're running, and what version of the linux-firmware package you currently have installed? Thanks!"
1756824,2018-04-30 08:27:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756826,2020-01-13 07:56:15 UTC,This bug was fixed in the package gnome-calculator - 1:3.28.2-1~ubuntu18.04.3
1756826,2020-01-13 07:56:10 UTC,This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.3
1756826,2020-01-13 07:56:10 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1756826,2020-01-13 07:55:58 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.14
1756826,2020-01-13 07:55:51 UTC,This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.5
1756826,2019-12-19 12:58:48 UTC,Confirmed working also with new calculator
1756826,2019-12-19 12:13:51 UTC,"I want to mention to the release team, that the regression in gnome-calculator DOES NOT affect the other packages, so them can be considered verified and be sent to updates safely (not to block waiting for them), while only gnome-calculator needs an update."
1756826,2019-12-19 12:11:02 UTC,"So, I've verified this for:"
1756826,2018-10-11 09:51:53 UTC,This bug was fixed in the package gnome-software - 3.30.2-0ubuntu3
1756826,2018-10-09 11:46:39 UTC,@robert-ancell the required work to fix this in gnome-software has been merged here (https://gitlab.gnome.org/Community/Ubuntu/gnome-software/merge_requests/6) but they have not been updated in cosmic. Do you mind taking a look? Thanks :)
1756826,2018-09-05 15:24:46 UTC,Fixed in gnome-calculator 1:3.29.91-1ubuntu2
1756826,2018-09-05 14:16:01 UTC,This bug was fixed in the package gnome-shell - 3.29.92-1ubuntu1
1756826,2018-09-03 16:42:39 UTC,This bug was fixed in the package nautilus - 1:3.26.4-0ubuntu3
1756826,2019-12-19 12:35:29 UTC,"Hello Iain, or anyone else affected,"
1756830,2018-03-19 09:40:04 UTC,I've tried the solution to Archlinux forum post and it works right now. The solution (more like a hack) is proposed here in the bottom message:  https://superuser.com/questions/1278234/have-to-restart-networkmanager-to-get-wifi-autoconnect
1756832,2018-03-23 01:30:11 UTC,"Reviewed:  https://review.openstack.org/554388
Committed: https://git.openstack.org/cgit/openstack/puppet-openstack-integration/commit/?id=de1f894ed810d326b7578fc0c64fe9a84880db92
Submitter: Zuul
Branch:    stable/pike"
1756832,2018-03-21 10:30:15 UTC,"Reviewed:  https://review.openstack.org/554387
Committed: https://git.openstack.org/cgit/openstack/puppet-openstack-integration/commit/?id=47da92f4e8c0131f7ec2c606b05651c3ed630c2f
Submitter: Zuul
Branch:    stable/queens"
1756832,2018-03-19 09:49:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554184"
1756832,2018-03-20 00:18:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554387"
1756832,2018-03-19 18:44:17 UTC,"Reviewed:  https://review.openstack.org/554184
Committed: https://git.openstack.org/cgit/openstack/puppet-openstack-integration/commit/?id=f8d4883f520c1dcbfd000b37c14607f87ae65932
Submitter: Zuul
Branch:    master"
1756832,2018-03-20 00:18:46 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554388"
1756837,2018-04-10 09:23:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756837,2020-03-24 15:57:34 UTC,This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 67ubuntu20.04.3
1756837,2020-04-21 15:25:56 UTC,"It' is really fixed? Just tested on Ubuntu 20.04 RC, package gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 and doesn't see any difference. Badges still disappear after screen lock."
1756851,2018-04-18 15:46:26 UTC,Already fixed in latest: https://docs.openstack.org/neutron/latest/admin/fwaas-v2-scenario.html
1756851,2019-05-16 16:05:30 UTC,"Fixed according to Petr, so let's close this."
1756852,2020-11-10 15:48:43 UTC,"This error message can be misleading during troubleshooting, had it on our environment as the last message on log and took us a while to figure the issue was elsewhere. I'll submit a patch to remove the provides as James suggested."
1756852,2018-09-18 23:16:12 UTC,"Not sure about ""errors out"", but we saw this kill this run: https://solutions.qa.canonical.com/#/qa/testRun/04bd84a2-da33-4244-9afc-a3513e26d442"
1756852,2018-05-21 19:14:00 UTC,On 18.02:
1756852,2018-07-18 12:05:47 UTC,Errors out is not quite true - reactive logs an ERROR message because it can't find the implmenetation.
1756852,2018-07-18 12:06:09 UTC,Lets just drop the provides entry from the designate charm.
1756862,2018-03-19 12:44:57 UTC,and earlier in syslog
1756862,2018-03-19 12:43:46 UTC,"Mar 19 11:59:14 ubuntu ubiquity: Traceback (most recent call last):
Mar 19 11:59:14 ubuntu ubiquity:   File ""/usr/bin/apt-clone"", line 148, in <module>
Mar 19 11:59:14 ubuntu ubiquity:     args.source, args.destination, new_distro=args.new_distro_codename, protect_installed=protect_installed)
Mar 19 11:59:14 ubuntu ubiquity:   File ""/usr/lib/python3/dist-packages/apt_clone.py"", line 501, in restore_state
Mar 19 11:59:14 ubuntu ubiquity:     self._restore_package_selection(statefile, targetdir, protect_installed, exclude_pkgs)
Mar 19 11:59:14 ubuntu ubiquity:   File ""/usr/lib/python3/dist-packages/apt_clone.py"", line 658, in _restore_package_selection
Mar 19 11:59:14 ubuntu ubiquity:     cache.commit(self.fetch_progress, self.install_progress)
Mar 19 11:59:14 ubuntu ubiquity:   File ""/usr/lib/python3/dist-packages/apt/cache.py"", line 529, in commit
Mar 19 11:59:14 ubuntu ubiquity:     raise SystemError(""installArchives() failed"")
Mar 19 11:59:14 ubuntu ubiquity: SystemError: installArchives() failed
Mar 19 11:59:14 ubuntu /plugininstall.py: log-output -t ubiquity chroot /target umount /sys
Mar 19 11:59:14 ubuntu /plugininstall.py: log-output -t ubiquity chroot /target umount /proc
Mar 19 11:59:14 ubuntu /plugininstall.py: log-output -t ubiquity umount /target/run
Mar 19 11:59:14 ubuntu /plugininstall.py: log-output -t ubiquity umount /target/dev
Mar 19 11:59:14 ubuntu /plugininstall.py: log-output -t ubiquity umount -f /target/proc
Mar 19 11:59:14 ubuntu /plugininstall.py: log-output -t ubiquity umount -f /target/sys
Mar 19 11:59:14 ubuntu /plugininstall.py: log-output -t ubiquity umount -f /target/dev
Mar 19 11:59:14 ubuntu /plugininstall.py: log-output -t ubiquity umount -f /target/run
Mar 19 11:59:14 ubuntu /plugininstall.py: Could not restore packages from the previous install:
Mar 19 11:59:14 ubuntu /plugininstall.py: Traceback (most recent call last):
Mar 19 11:59:14 ubuntu /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 246, in run
Mar 19 11:59:14 ubuntu /plugininstall.py:     self.apt_clone_restore()
Mar 19 11:59:14 ubuntu /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 1486, in apt_clone_restore
Mar 19 11:59:14 ubuntu /plugininstall.py:     restore_cmd, preexec_fn=install_misc.debconf_disconnect)
Mar 19 11:59:14 ubuntu /plugininstall.py:   File ""/usr/lib/python3.6/subprocess.py"", line 291, in check_call
Mar 19 11:59:14 ubuntu /plugininstall.py:     raise CalledProcessError(retcode, cmd)
Mar 19 11:59:14 ubuntu /plugininstall.py: subprocess.CalledProcessError: Command '['apt-clone', 'restore-new-distro', '/target/ubiquity-apt-clone/apt-clone-state-ubuntu.tar.gz', 'bionic', '--destination', '/target']' returned non-zero exit status 1."
1756862,2018-04-16 22:54:31 UTC,"I've emailed the ubuntu-doc team about this change, https://lists.ubuntu.com/archives/ubuntu-doc/2018-April/020601.html."
1756862,2018-04-15 11:15:35 UTC,This bug was fixed in the package ubiquity - 18.04.6
1756862,2018-04-12 19:37:57 UTC,"Looking around at other ubiquity bugs we can see that apt-clone with the restore-new-distro option has not worked for lots of people for quite some time. As an example bug see bug 1152399 which is a collection of duplicate bugs where the ""install"" of Ubuntu failed when calculating the upgrade from a previous release to a later release of Ubuntu. This leaves people in a hard to resolve situation and subsequently due to that issue and this crash with apt-clone we have decided to remove the option to upgrade a release of Ubuntu from ubiquity."
1756862,2018-04-12 15:23:46 UTC,Another screenshot with different debugging set.
1756862,2018-04-11 17:16:57 UTC,"After modifying apt_clone.py to set ""Debug::pkgDPkgPM"" I saw the error messages in the attached screenshot."
1756862,2018-04-17 16:37:09 UTC,"Post-hoc approval of the UI Freeze exception, per the understanding that this does not impact the existing docs."
1756862,2018-04-10 21:47:56 UTC,Running it with --simulate we can see something weird is going on:
1756862,2018-04-10 17:47:46 UTC,The traceback from apt-clone can be seen here:
1756862,2018-04-05 19:06:38 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1756862,2018-04-05 18:23:11 UTC,From the duplicate report:
1756862,2018-04-05 18:22:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756862,2018-04-11 17:09:15 UTC,I think I was encountering a different problem yesterday as I was trying to ubiquity upgrade an old (not up to date) version of artful. After updating my artful system and then trying the upgrade I'm encountering the error message:
1756863,2018-03-22 12:05:39 UTC,"@Nicholas - we are unsure who handles that, could you please reassign in the Juju team as you think will be correct?"
1756863,2018-05-22 02:31:03 UTC,I can't re-assign it seems. Poke @thumper.
1756865,2018-04-10 17:27:05 UTC,"I think this was my mistake, I think the student was having Java 9. I am now on Java 9 as well so I can test it if this works. I don't have Java 8 to test it though, but I guess that there is no problem then if it is still in API."
1756865,2018-04-10 13:32:22 UTC,"Can someone please confirm this issue is present on Java 8, according to documentation the API should only be removed in Java 9. (run java -version to see java version)"
1756865,2018-04-01 13:53:48 UTC,Here is what comes on the command line output:
1756867,2020-09-23 16:06:45 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/554229"
1756876,2018-03-21 09:56:19 UTC,"o/ Tengu - some pointers from irc just now - but its hard to see what exactly the problem is, I mean it will be some error in the controller(s) journal"
1756876,2018-03-22 05:57:48 UTC,"Hello Michele,"
1756876,2018-03-21 16:37:24 UTC,So yeah a messed up network will just kill quorum on the cluster and things will just go down the rabbithole.
1756876,2018-03-21 12:43:42 UTC,"Hello Marios,"
1756876,2018-03-21 09:16:55 UTC,"Hello,"
1756876,2018-03-21 05:45:26 UTC,"Hello Michele,"
1756876,2018-03-20 17:15:55 UTC,"Hi Cedric,"
1756876,2018-03-20 16:25:58 UTC,"Hello Michele,"
1756876,2018-03-20 16:19:40 UTC,"Hi guys, I am in a similar situation, is there a way the can be accommodated so I can have the BM moved to Containers?"
1756876,2018-03-20 12:44:40 UTC,I guess it really depends what steps you took. When you say 'upgrade' from pike bm to pike container it is not entirely obvious what took place?
1756876,2018-03-19 16:29:41 UTC,"Would be great to at least have some inputs ;). I'm more than ready to dig into that, but with no real clue it's a bit hard."
1756876,2018-03-19 16:21:46 UTC,"Setting ""low"" priority as we don't support this use case and don't test it at all."
1756877,2018-03-29 20:37:54 UTC,apport information
1756877,2018-03-29 20:37:55 UTC,apport information
1756877,2018-03-29 20:37:56 UTC,apport information
1756877,2018-03-29 20:37:57 UTC,apport information
1756877,2018-03-29 20:37:58 UTC,apport information
1756877,2018-03-29 20:37:59 UTC,apport information
1756877,2018-03-29 20:38:00 UTC,apport information
1756877,2018-03-29 20:38:02 UTC,apport information
1756877,2018-03-29 20:41:21 UTC,I am not so sure but as I understand it running the nvidia driver does not allow to use the integrated intel graphics to run and always the higher power consumption nvidia gpu. And that is why the laptop runs the fans all the time and is warmer because it cannot switch between the two to minimize the consumption. But I must admit that I havent actually measured anything so it could just be my idea.
1756877,2018-03-29 20:37:53 UTC,apport information
1756877,2018-03-29 20:43:51 UTC,If this is just an output latency issue why would trying to write or use a shortcut result in a key being registered as being pressed multiple times? Example is pressing 'Ctrl' + 'T' for a new tab and opening 20 more tabs or writing 'and' and resulting in 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaand'
1756877,2018-03-29 20:44:09 UTC,Run the apport-collect command btw.
1756877,2018-03-30 15:28:29 UTC,"I must admit that the lag is less noticeable but it is still there and it affects sound (with sound playback stopping for a split seconds while playing), keyboard input (with the keys registering multiple times), mouse (scrolling might take a second to register) and the display."
1756877,2018-03-31 19:10:15 UTC,"Looks like this affects me, also using a Dell XPS 15 9530."
1756877,2018-03-31 19:18:15 UTC,Reported via ubuntu-bug -- hope this helps:
1756877,2018-04-03 03:01:41 UTC,Thanks Luke. Your confirmation is very helpful.
1756877,2018-04-11 21:11:21 UTC,FYI I'm currently mitigating this using Bumblebee:
1756877,2018-03-29 20:38:47 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1756877,2018-03-29 20:37:52 UTC,apport information
1756877,2018-03-28 16:20:41 UTC,Well is does appear to solve the problem with the lag but then there is high battery drain and the fans won't stop spinning which is also undesireable
1756877,2018-03-29 20:37:50 UTC,apport information
1756877,2018-03-29 20:37:51 UTC,apport information
1756877,2018-03-20 02:32:46 UTC,"(1) Are you using USB wired, USB-wireless, or Bluetooth mouse and keyboard?"
1756877,2018-03-20 05:36:01 UTC,"(4) Please also run this command on the machine and send us the output:
    dmesg > dmesg.txt"
1756877,2018-03-20 10:08:11 UTC,"I am running Ubuntu from my laptop so sometime I use USB keyboard and wireless mouse and some times just my laptop's keyboard and touch pad and I have had this issue with both, with or without any extensions active"
1756877,2018-03-20 10:08:42 UTC,"Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 8087:07dc Intel Corp.
Bus 003 Device 003: ID 06cb:0ac3 Synaptics, Inc.
Bus 003 Device 005: ID 0bda:573c Realtek Semiconductor Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub"
1756877,2018-03-20 10:10:15 UTC,dmesg
1756877,2018-03-20 10:24:59 UTC,"I should note however that the problem is less noticeable today, maybe due to some update."
1756877,2018-03-20 11:33:21 UTC,Other configuration i have tried is with or without an external screen. I am running the mesa graphics driver and not the proprietary Nvidia one.
1756877,2018-03-19 13:17:47 UTC,I have also tried using it without extensions but the issue still remains but I haven't tried using it with xorg because it causes other issues for me especially with hidpi scaling
1756877,2018-03-21 02:12:12 UTC,"Also your kernel log (dmesg.txt) is showing a lot of errors from the nouveau graphics driver. Nouveau is known to have lots of bugs, so please try installing this one instead:"
1756877,2018-03-21 02:08:46 UTC,Please also try updating again. Just 1 hour ago we got a newer version of libinput: 1.10.3
1756877,2018-03-29 20:37:49 UTC,apport information
1756877,2018-03-29 20:37:48 UTC,apport information
1756877,2018-03-29 20:37:47 UTC,apport information
1756877,2018-03-22 01:55:07 UTC,"I'm not sure but this seems to suggest ""yes"" (?):"
1756877,2018-03-29 01:46:27 UTC,"That's surprising, and is the opposite of what I would expect. Are you saying the high power usage occurs _with) nvidia-driver-390 installed?"
1756877,2018-03-29 02:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1756877,2018-03-21 09:36:43 UTC,Do I have to disable secure boot for the proprietary driver to work?
1756880,2018-03-27 19:40:19 UTC,Same as stable/queens branch
1756880,2018-12-06 08:54:32 UTC,"In my opinion this is not a bug but a obvious choice for ceilometer.
Since ceilometer API has been deprecated , command ceilometer meter-list cannot find any end point (URL) to connect with keystone.
Hence this message occurs."
1756884,2019-10-10 10:27:46 UTC,I believe we've fixed these. If not please shout.
1756885,2018-04-23 02:30:06 UTC,"Strange, the license reports as Free in GNOME Software  3.28.1 (in 18.04) but Terminal still reports the license as `unknown`."
1756894,2018-06-06 12:16:03 UTC,"Hello Toan,"
1756894,2018-06-06 18:29:25 UTC,"Hello again,"
1756894,2018-06-06 19:17:13 UTC,"I use Ubuntu 18.04. As you said, I can select multiple files and choose open with qpdfview without problem. But the strange thing is that if I set qpdfview as default pdf reader, then select multiple files and press enter or choose open, it only opens the first file selected."
1756894,2018-06-07 06:59:27 UTC,"Hello again,"
1756894,2018-06-07 11:10:11 UTC,This is the desktop file:
1756894,2018-06-07 17:05:49 UTC,"Hello again,"
1756894,2018-06-07 17:27:53 UTC,"Okular works fine with me, it uses this line:
Exec=okular %U"
1756894,2018-06-07 17:40:36 UTC,"Hhhmmm, according to the specification %U means list of URL whereas %F means list of files. I guess Okular can download URL using KIO and then open the files locally, but qpdfview does not support anything but local files. So maybe Nautilus works correctly for %U but has a bug for %F?"
1756894,2018-06-06 12:32:01 UTC,"I used file browser. I already knew how to open multiple files in qpdfview, but the way it's done is inconvenient. I would like to be able to open multiple files from file browser."
1756896,2018-08-04 01:56:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756897,2018-03-22 07:07:56 UTC,"The issue is not observed frequently, I would like to add some more information."
1756897,2018-03-19 14:47:16 UTC,sla1 for 9.0-updates
1756897,2018-03-21 12:55:53 UTC,Please provide steps to reproduce.
1756900,2018-05-14 12:42:07 UTC,"I think that this might be a current limitation of nova-lxd.  Obviously, a ZFS pool name can't have a '/' in it.  This is a limitation of ZFS itself.  e.g. try to create a pool name with:"
1756900,2018-05-31 07:12:29 UTC,"Reviewed:  https://review.openstack.org/571226
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=97cb7ea742d4dbcc83079da33ebb4d7e66d0ee9c
Submitter: Zuul
Branch:    master"
1756901,2019-11-18 20:42:27 UTC,The issue is fixed in 19.10
1756901,2018-06-09 20:01:25 UTC,"Sorry for the confusion, I was using the snap version."
1756901,2018-06-09 19:58:36 UTC,"Hi, I have gnome-calendar 3.26.3 and I still experience this bug. Also, whenever I try to open it again it crashes after few seconds."
1756901,2018-03-27 14:32:52 UTC,"I tried to reproduce this bug in Bionic Daily, Calendar did not crash but after connecting to my google account and everything looking ok, no calendar events were shown."
1756901,2018-04-08 17:24:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756901,2018-03-20 06:29:12 UTC,"Nope, doesn't look familiar. I have an AMD RX560, so there still could be some graphical errors that intervene, even if it's kernel version 4.15."
1756901,2018-03-19 20:00:02 UTC,This line certainly looks suspicious:
1756901,2018-03-19 15:42:20 UTC,Updated: This affects vanilla GNOME as well.
1756901,2018-03-19 15:28:28 UTC,"StacktraceTop:
 g_type_check_instance_cast (type_instance=0x56170bb6f930, iface_type=94656966589920) at ../../../../gobject/gtype.c:4057
 remove_source (manager=<optimized out>, source=0x7f34dc066940, user_data=<optimized out>) at ../src/gcal-source-dialog.c:1639
 g_closure_invoke (closure=0x56170bc13700, return_value=0x0, n_param_values=2, param_values=0x7ffe93ac6120, invocation_hint=0x7ffe93ac60a0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x56170adee2f0, detail=detail@entry=0, instance=instance@entry=0x56170ade61c0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffe93ac6120) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffe93ac62f0) at ../../../../gobject/gsignal.c:3391"
1756901,2018-03-20 08:50:45 UTC,Moved here: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264
1756904,2018-04-10 20:42:48 UTC,One of the things we should cater for is the problem of invalid chars in filepath names
1756904,2018-05-08 02:20:26 UTC,Hi Cecilia
1756904,2018-05-07 21:48:30 UTC,"As we discussed, there are 2 ways we to resolve this
1. Translate the filenames to be included in the export, removing all symbols that could be consider invalid chars in the os.
This is not easy as replacing the symbols, since we could have similar names that translate to the same name, so we would have to keep track of all the names taken and find a way to choose a new one in case is not available."
1756904,2018-05-04 01:23:13 UTC,for testing
1756904,2018-03-27 21:16:57 UTC,"Hello Danny,"
1756904,2018-04-12 01:55:46 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/8798"
1756904,2018-03-26 21:39:50 UTC,Some more testing with Danny's export:
1756904,2018-03-26 03:18:55 UTC,"Danny, can you please also upload the Leap2A export for this portfolio so we can import it into our instance of Mahara?"
1756904,2018-03-26 03:18:07 UTC,Links to content in blocks still worked for us on Windows. Will need to take a closer look at your links.
1756904,2018-03-21 12:16:48 UTC,"Links are workining on Mac, but I tested on Windows 10 et Windows 7 and it is not working. HTML is well displayed but the link doesn't work because of folders name."
1756904,2018-03-20 22:21:28 UTC,"I don't think that this is an issue because the special characters are still displayed properly when looking at the HTML page in the browser, and the links go to the correct places."
1756904,2018-03-27 13:33:42 UTC,Exported a fresh Leap and HTML from demo.mahara.org
1756920,2018-03-23 07:11:32 UTC,"Probably worth investigating what xmllint does differently here. Or just put a print statement in xmlerror.pxi to see what exact error information libxml2 reports here, and if there is anything else that can be extracted from it."
1756931,2018-03-19 16:42:57 UTC,Can confirm - there is nothing we can do unfortunately - this is a known upstream issue.
1756933,2018-11-05 14:29:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756933,2018-11-05 14:30:36 UTC,Behavior is still present in 18.04.1 LTS
1756945,2018-05-11 15:36:46 UTC,This change was made by a bot.
1756945,2021-01-07 04:04:56 UTC,4.13 EOL
1756952,2018-03-19 20:06:03 UTC,"Also reproducible in xterm and various other terminal emulators, at least sometimes (not always). So not a gnome-terminal issue."
1756952,2018-03-19 22:15:12 UTC,"I guess we should close this, then?"
1756953,2018-03-21 05:46:23 UTC,"Hi Daniel,"
1756953,2018-03-21 18:45:37 UTC,Thank you for the response.
1756964,2018-03-19 18:28:46 UTC,attached crashdump from run
1756964,2018-05-16 16:04:42 UTC,"I've had what might be a similar issue, but for removing prometheus. It was hanging endlessly on removal, and on the unit I could see it looping on relation-get calls towards telegraf"
1756970,2020-09-03 05:52:59 UTC,"FWIW, I saw this after an upgrade to Bionic, the units were logging the same errors, but still able to issue tokens."
1756970,2020-01-07 08:08:13 UTC,"We are seeing additional users hit this (likely, not confirmed) but in production and so critical."
1756970,2019-09-27 14:50:34 UTC,"Seeing this issue on site , bundle stable queens + bionic + bluestore"
1756970,2019-09-27 15:11:22 UTC,https://pastebin.canonical.com/p/YByW25Mm8Q/
1756970,2018-08-21 03:56:33 UTC,Have you seen this in recent deploys from master / cs:~openstack-charmers-next?  I believe this should be fixed as a consequence of removal of PKI token support from charm.
1756970,2018-03-22 09:14:38 UTC,"Please can you provide details for the OpenStack release being deployed, and the bundle that you are deploying so we can see all configuration options that might be causing this issue."
1756970,2019-09-04 11:12:25 UTC,"Hi! I see a similar error using bundle-bionic-queens.yaml bundle from openstack-on-lxd:
""""""
(keystoneclient.common.cms): 2019-09-04 10:48:02,672 ERROR Signing error: Can't open /etc/keystone/ssl/certs/signing_cert.pem for reading, No such file or directory
140704560206272:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:72:fopen('/etc/keystone/ssl/certs/signing_cert.pem','r')
140704560206272:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:79:
unable to load certificate"
1756970,2018-04-19 15:20:21 UTC,"This was a Queens run.
cdoqa-system-tests	cdoqa-system-tests_547
cloud-init	cloud-init_18.2-4-g05926e48-0ubuntu1~16.04.1
cpe-foundation	cpe-foundation_1.0.0-323-gf62b43f
infra-ubuntu	infra-ubuntu_xenial
juju	juju_2.4-beta1+develop-e688e18
lxd	lxd_2.0.11-0ubuntu1~16.04.4
maas	maas_2.3.0-6434-gd354690-0ubuntu1~16.04.1
python3-curtin	python3-curtin_18.1-609-gfc19cec-0ubuntu1~ubuntu16.04.1"
1756970,2018-04-17 20:02:11 UTC,Attaching the latest reproduction of this issue.
1756976,2020-02-14 02:05:20 UTC,"Hmm, the error message says no more free space, but the df output shows there's space left."
1756976,2020-04-14 04:17:47 UTC,[Expired for flashplugin-nonfree (Ubuntu) because there has been no activity for 60 days.]
1756984,2018-03-19 19:54:52 UTC,"StacktraceTop:
 dl_new_hash (s=0x7f1d94fa7f3c ""pixman_rasterize_trapezoid"") at dl-lookup.c:555
 _dl_lookup_symbol_x (undef_name=0x7f1d94fa7f3c ""pixman_rasterize_trapezoid"", undef_map=0x55a6c8f6d5b0, ref=ref@entry=0x7ffeda6e5728, symbol_scope=0x55a6c8f6d908, version=0x0, type_class=type_class@entry=1, flags=5, skip_map=0x0) at dl-lookup.c:791
 _dl_fixup (l=<optimized out>, reloc_arg=<optimized out>) at ../elf/dl-runtime.c:112
 _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125
 wfbRasterizeTrapezoid (pPicture=0x55a6c977fa80, trap=0x55a6c9c11ce4, x_off=0, y_off=0) at ../../../../fb/fbtrap.c:60"
1756984,2018-03-27 08:34:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756984,2018-04-04 11:39:25 UTC,"I strongly suspect this is the same bug in upstream kernel v4.15, which causes this issue:"
1756992,2018-05-03 00:24:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756994,2018-10-08 21:45:34 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1756994,2018-09-24 17:06:59 UTC,"Reviewed:  https://review.openstack.org/589503
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=05b945e61ab2739b39869f571379e1c95a017906
Submitter: Zuul
Branch:    stable/pike"
1756994,2018-09-24 14:47:03 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1756994,2018-08-09 20:39:48 UTC,"Reviewed:  https://review.openstack.org/589505
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91d47b11e939bccff469b1070e072cc58b61b5df
Submitter: Zuul
Branch:    stable/queens"
1756994,2018-08-07 14:33:54 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/589503"
1756994,2018-04-20 13:13:28 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1756994,2018-03-19 23:26:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554380"
1756994,2018-08-07 14:34:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/589505"
1756994,2018-03-20 12:37:59 UTC,"Reviewed:  https://review.openstack.org/554380
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bbb668bbec2e2fa6b7f64b9af9504b973016058c
Submitter: Zuul
Branch:    master"
1756997,2018-03-19 20:18:01 UTC,"Console output from apport-valgrind attached,
NB: I invoked it with:
/usr/bin/apport-valgrind -l valgrind.$$.log -C ./cache -v /usr/bin/plasmashell < /dev/null &> apport-valgrind.$$.log &"
1756997,2018-08-08 20:55:10 UTC,"FYI, this is fixed in Bionic running the latest NVidia drivers and KDE version."
1756998,2018-03-19 20:35:50 UTC,Setting the kernel parameter intel_iommu = off was the first attempt to solve the problem.
1756999,2020-08-11 09:32:54 UTC,Looks like it's only ever happened once in focal.
1756999,2018-03-20 02:24:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1756999,2018-03-19 20:27:10 UTC,"StacktraceTop:
 do_lookup (path=path@entry=0x0, size=size@entry=0x7f590bffea58, flags=flags@entry=0x0, data=data@entry=0x0, data_size=data_size@entry=0x0, error=0x7f590bffea00, lookup_flags=G_RESOURCE_LOOKUP_FLAGS_NONE, resource=<optimized out>) at ../../../../gio/gresource.c:609
 g_resource_get_info (resource=<optimized out>, path=path@entry=0x0, lookup_flags=lookup_flags@entry=G_RESOURCE_LOOKUP_FLAGS_NONE, size=size@entry=0x7f590bffea58, flags=flags@entry=0x0, error=error@entry=0x7f590bffea00) at ../../../../gio/gresource.c:836
 g_resources_get_info (path=path@entry=0x0, lookup_flags=lookup_flags@entry=G_RESOURCE_LOOKUP_FLAGS_NONE, size=size@entry=0x7f590bffea58, flags=flags@entry=0x0, error=error@entry=0x0) at ../../../../gio/gresource.c:1241
 _gdk_pixbuf_new_from_resource_try_pixdata (resource_path=resource_path@entry=0x0) at gdk-pixbuf-io.c:1658
 gdk_pixbuf_new_from_resource (resource_path=0x0, error=error@entry=0x556af106c780) at gdk-pixbuf-io.c:1709"
1756999,2018-03-20 02:25:02 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/8d3c75a48e07bfa1d8379f00f17ca259f0471ab8"
1757002,2018-03-19 21:13:15 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x56496058b9c0, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x56496058b9c0) at ../../../../gobject/gobject.c:3204
 g_weak_ref_get (weak_ref=<optimized out>) at ../../../../gobject/gobject.c:4379
 g_settings_backend_invoke_closure (user_data=0x7faa48005400) at ../../../../gio/gsettingsbackend.c:263
 g_main_dispatch (context=0x56495febb6c0) at ../../../../glib/gmain.c:3177"
1757002,2018-08-23 09:12:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757007,2018-03-19 22:17:11 UTC,"Specifically, what you probably want is the `post-refresh` hook (as of 2.29). Basic informational docs are here:"
1757008,2018-07-21 00:02:37 UTC,"Hi Andrew,"
1757008,2018-07-21 20:57:20 UTC,Here is what worked for me to restore WiFi functionality...
1757008,2018-07-22 10:41:35 UTC,"after latest update i lost wifi connection this mens im without INTERNET, how can this be possible and when can we have an update to fix it."
1757008,2018-07-22 11:10:36 UTC,ok i did Run Software & Udpates from the launcher. In the Developer Options tab.
1757008,2018-07-22 11:12:11 UTC,at this time ubuntu software store is limited so maybe they are doing something but now cant see my programs on the store
1757008,2018-07-22 13:39:02 UTC,"Hello,"
1757008,2018-07-22 15:51:28 UTC,"Same problem over here in an old DELL inspiron.
Thanks to Melissa's post (#25) it was solved."
1757008,2018-07-24 09:06:03 UTC,WORKAROUND: https://askubuntu.com/a/1052418/308869
1757008,2018-07-22 19:22:59 UTC,"@Marc Peña (pachulo)
Thank you very much! The fix is really in: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1777444?comments=all"
1757008,2018-07-29 23:11:33 UTC,"on Ubuntu 16.04 LTS.  Installed tightVNCViewer, now get this problem.  Using usb wireless as old Dell broadband driver does not work.  Dell M6300 laptop."
1757008,2018-08-08 09:15:53 UTC,"sudo apt-get purge bcmwl-kernel-source
sudo apt-get install broadcom-sta-dkms"
1757008,2018-08-25 16:05:32 UTC,In which versions of the packages the fix is released? Which release of Ubuntu?
1757008,2018-08-25 17:57:14 UTC,"It works starting with 4.15.0-33-generic, at
least it did for me.
frank"
1757008,2018-10-07 00:09:29 UTC,I am still not able to see any networks on 4.15.0-36-generic.
1757008,2018-07-20 22:30:42 UTC,"After browsing through some of the previous links, the proposed fix for the bcmwl version successfully solved the problem.
Fix found here: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1777646"
1757008,2018-07-22 17:03:15 UTC,"How much will take to mark package bcmwl-kernel-source/now 6.30.223.271+bdcom-0ubuntu1~1.3 as tested if it is fixing bug from March, please?"
1757008,2018-07-20 19:11:23 UTC,I installed Ubuntu 16.04 on a MacBook Pro
1757008,2018-07-20 22:00:40 UTC,"I ran into this bug with today's update to kernel 4.15.0-29. I had no problem previously using the 4.15.0-24 kernel. The bug reporter automatically directed me to this bug report. I see similar issues, where my wifi adapter seems to have disappeared. I have not yet tried the workaround."
1757008,2018-07-11 21:21:56 UTC,"  // , Looks like there's an official fix that doesn't require drivers from Bionic here:"
1757008,2018-07-18 16:06:30 UTC,WORKAROUND: https://askubuntu.com/a/1052418/308869
1757008,2018-06-24 01:08:47 UTC,please help me!! wifi cannot unable to active because not in interfaces
1757008,2018-07-02 12:33:50 UTC,"Happened today after the upgrade, lost wifi :-/"
1757008,2018-07-02 12:51:41 UTC,"Happened today after the upgrade, lost wifi :-/"
1757008,2018-07-02 14:40:35 UTC,do i have to downgrade my kernel?
1757008,2018-07-02 14:46:13 UTC,do i have to downgrade my kernel?
1757008,2018-07-03 09:28:41 UTC,Hi.
1757008,2018-07-03 12:13:23 UTC,The solution seems to be in the -proposed repo: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1777444
1757008,2018-07-03 12:21:42 UTC,"So, I've tried to install the package in proposed and WiFi is working OK with kernel 4.15."
1757008,2018-04-05 07:01:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757008,2018-07-03 20:32:39 UTC,"Hi, how to fix this practically without compiling any code? Today i lost wlan and error message let me into this bug. Currently my laptop is a brick without wlan..."
1757008,2018-07-03 23:47:29 UTC,"@Sami: the compilation is done automatically by the installer. You can either plug in Ethernet or reboot and chose Advanced Ubuntu boot option, scroll down to the previous ver. of the Kernel (4.13) and boot with it normally to get the WiFi connection back. Then ""See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed"" - just a couple of steps that don't affect your overall system if you ""Create the file /etc/apt/preferences.d/proposed-updates with this content:..."". Then sudo apt-get update and  sudo apt-get install broadcom-sta-dkms/xenial-proposed. This should successfully compile for both 4.13 and 4.15 kernels. Then reboot normally and forget about this incident till the kernel testing flow breaks again next year or whenever."
1757008,2018-07-04 07:15:57 UTC,Thank you @Stan! got it fixed!
1757008,2018-07-05 12:01:27 UTC,"Thank you a lot: easily fixed with ""apt-get update/upgrade"" today. Good work !"
1757008,2018-07-05 12:35:22 UTC,Is there a fix for the bcmwl package? I see that the broadcom-sta seems to have had a fix but I can't see mention of bcmwl? Or am I missing something?
1757008,2018-07-05 17:26:14 UTC,Same here (broadcom-sta vs bcmwl).
1757008,2018-07-11 21:20:32 UTC,"  // , I have the same problem."
1757008,2018-07-03 16:09:05 UTC,The package in proposed fixed the issue for me too.
1757013,2018-03-19 22:39:49 UTC,"StacktraceTop:
 script_lib_plymouth_on_keyboard_input (state=0x1e, data=0x21, keyboard_input=<optimized out>) at ./script-lib-plymouth.c:261
 on_keyboard_input (plugin=0x5594463c79a0, keyboard_input=<optimized out>, character_size=1) at ./plugin.c:370
 process_keyboard_input (character_size=1, keyboard_input=0x5594464da950 ""K"", keyboard=0x5594463c43c0) at ply-keyboard.c:254
 on_key_event (keyboard=0x5594463c43c0, buffer=0x5594463d2650) at ply-keyboard.c:288
 ply_event_loop_handle_met_status_for_source (status=<optimized out>, source=0x5594463d2020, loop=0x5594463b53a0) at ply-event-loop.c:1034"
1757013,2018-04-01 21:54:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757021,2018-04-01 02:15:03 UTC,updating the bios seems to have fixed the problem. thank you.
1757021,2018-04-01 02:08:54 UTC,i wasn't able to update the bios due to my computer also being affected by the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147
1757021,2018-04-01 01:08:27 UTC,"ive tried with updates a09 and a10 as well with the same results. i also noticed that changes to the bios will frequently not save (i added a hdd password, it saved successfully, but while trying to remove it until my bios is fixed, it saves, then on reboot, the change is reverted..)"
1757021,2018-03-31 22:12:42 UTC,can't seem to update bios from a08 to a11. following the instructions here: http://www.dell.com/support/article/us/en/04/sln171755/updating-the-dell-bios-in-linux-and-ubuntu-environments?lang=en
1757021,2018-03-24 04:11:43 UTC,"final update. after closing the lid for over a minute, it's back to rebooting. when i closed the lid a few seconds then re-opened, it simply shut down."
1757021,2018-03-26 05:03:07 UTC,Please update BIOS to latest version (A11).
1757021,2018-03-24 03:48:17 UTC,i keep seeing acpi bios error (bug) in dmesg. attaching dmesg.log if it helps any.
1757021,2018-03-20 15:58:08 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1757021,2018-03-20 01:30:10 UTC,This change was made by a bot.
1757021,2018-03-26 09:54:42 UTC,Will do (soon)
1757030,2018-03-23 08:41:36 UTC,"... and there is a copy+paste error with
{{{
  GET CONFIGURATION
  46 01 00 00 00 00 00 00 08 00
  From drive: 8b
  00 00 00 9c 00 00 00 00
  From drive: 8b
  00 00 00 9c 00 00 00 00
       8 ms
}}}
Of course, the drive replied only once."
1757030,2018-03-23 17:07:57 UTC,"Attaching logs for
./growisofs -Z /dev/dvdrw=dvd.iso (nodao.log)
./growisofs -use-the-force-luke=dao -Z /dev/dvdrw=dvd.iso (dao.log)"
1757030,2018-03-23 17:07:08 UTC,dao option
1757030,2018-03-23 17:06:31 UTC,no DAO option
1757030,2018-03-23 12:25:58 UTC,"The attachment ""This patch enables SCSI logging to stderr in dvd+rw-tools"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1757030,2018-03-23 08:34:43 UTC,"Urm. The last stement should have been:
""... i will probably _not_ get to doing it soon."""
1757030,2018-03-23 18:32:34 UTC,"Hi,"
1757030,2018-03-22 23:00:33 UTC,"On Thu, Mar 22, 2018 at 07:09:56PM -0000, Thomas Schmitt wrote:

>
> growisofs has no such logging facility. But back in 2009 i augmented a
> local copy of it by logging functionality from libburn.
>
> If you are interested, it's about 150 lines of code. Mostly one piece
> which defines two methods. Plus two method calls in method transport().
> You'd have to put that code into a local copy of dvd+rw-tools source and
> build the programs from that.
>
> Then i will possibly be able to make a new thory from such a (very verbose)
> log.
"
1757030,2018-03-22 19:09:56 UTC,"Hi,"
1757030,2018-03-22 16:29:36 UTC,"On Wed, Mar 21, 2018 at 04:42:25PM -0000, Thomas Schmitt wrote:

>
> Looking at the source code of growisofs it seems that no command RESERVE
> TRACK is sent for DVD+R DL. libburn sends it if it decided for DAO/SAO-like
> writing for which it announces the amount of data in advance.
>
> You could risk a medium and run xorrecord with explicit option -tao
> in order to see whether it fails too:
>
>   xorrecord dev=/dev/sr0 -v -tao -pad 2017.iso
>
> (If no -tao or -dao is given, i expect libburn to decide for -dao.)
"
1757030,2018-03-21 16:42:25 UTC,"Hi,"
1757030,2018-03-21 15:05:21 UTC,"This is terrible.  How can growisofs mess this up so badly?  I didn't even
eject the disc and immediately can burn the image with xorrecord with no
problems."
1757030,2018-03-20 08:01:40 UTC,"Hi,"
1757030,2018-03-20 02:27:06 UTC,"I also tried Pioneer BDR-205 Blu-ray recorder, firmware 1.12.  growisofs can record any blank DL DVD with no problem.  xorriso can record DL DVD on either drive."
1757030,2018-03-23 08:29:46 UTC,"Hi,"
1757034,2019-05-16 23:05:55 UTC,This issue was fixed in the openstack/puppet-murano 11.6.0 release.
1757034,2018-04-19 21:03:11 UTC,This issue was fixed in the openstack/puppet-murano 13.0.0 release.
1757034,2018-03-29 00:12:58 UTC,This issue was fixed in the openstack/puppet-murano 12.4.0 release.
1757034,2018-03-21 01:16:15 UTC,"Reviewed:  https://review.openstack.org/554736
Committed: https://git.openstack.org/cgit/openstack/puppet-murano/commit/?id=990cef403fe5a6a3952db8a567fcd6ad8524a4da
Submitter: Zuul
Branch:    stable/queens"
1757034,2018-03-21 01:13:01 UTC,"Reviewed:  https://review.openstack.org/554737
Committed: https://git.openstack.org/cgit/openstack/puppet-murano/commit/?id=ea486842bcd4ca6c6265ec765f450fac56c1479f
Submitter: Zuul
Branch:    stable/pike"
1757034,2018-03-21 00:35:44 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/554737"
1757034,2018-03-21 00:35:28 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554736"
1757034,2018-03-20 14:43:30 UTC,"Reviewed:  https://review.openstack.org/554404
Committed: https://git.openstack.org/cgit/openstack/puppet-murano/commit/?id=ca7f7657acac8a9efe1943929a1e38a8a8921af8
Submitter: Zuul
Branch:    master"
1757034,2018-03-20 02:50:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554404"
1757038,2018-03-20 03:01:38 UTC,ReqHandle.py:
1757038,2018-03-20 03:03:52 UTC,This also influences the zvmsdk debug log. (debug info won't be printed when log_level is set to DEBUG)
1757038,2018-03-20 03:05:11 UTC,"Correct to comment #2: zvmsdk log not affected, sdkserver would."
1757038,2018-03-20 05:16:56 UTC,https://review.gerrithub.io/#/c/404441/
1757040,2019-10-02 21:28:03 UTC,I'm seeing this on train now with:
1757040,2018-06-15 13:54:14 UTC,Some more debug:
1757040,2018-04-06 08:18:24 UTC,Can you provide the command you used to run the test with testtools and also show us the error received?
1757040,2018-06-15 12:56:32 UTC,Pasting the error that I see here:
1757040,2018-06-15 13:24:17 UTC,"We're just running tests with 'stestr run'. Typically issues like this occur due to dependency differences where the tox virtualenv has a dependency that differs from the failing environment. I'm hitting this in Ubuntu package builds so I imagine we have a dependency that falls within the allowed requirements constraints, but actually doesn't work."
1757049,2018-03-20 06:24:21 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f634ab64b9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f634ab62c9d ""corrupted size vs. prev_size"") at malloc.c:5350
 _int_realloc (av=av@entry=0x7f634ad99c40 <main_arena>, oldp=oldp@entry=0x5602daf19f30, oldsize=oldsize@entry=160, nb=nb@entry=176) at malloc.c:4564
 __GI___libc_realloc (oldmem=oldmem@entry=0x5602daf19f40, bytes=bytes@entry=154) at malloc.c:3221
 xrealloc (mem=mem@entry=0x5602daf19f40 ' ' <repeats 152 times>, ""\241"", len=len@entry=154) at ../resize.c:624"
1757049,2018-07-03 22:42:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757053,2018-03-20 07:15:28 UTC,I forgot to mention that the original file is an .ai file from Adobe Illustrator.
1757053,2018-03-20 10:50:28 UTC,thank you for taking the time to issue a report.
1757053,2018-03-20 11:08:08 UTC,"the problem can also be reproduced by a normal path, not a star. attached is an svg file which shows the same problem. In this case the path has been closed using a 'z' command rather than explicitly drawing the last line."
1757053,2018-03-20 12:09:37 UTC,Thanks.
1757053,2021-01-27 19:25:18 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1757061,2018-10-08 07:16:40 UTC,"Reviewed:  https://review.openstack.org/608165
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ae39c0332d773226e3bd7dd0f81da9660b7ba7cb
Submitter: Zuul
Branch:    stable/rocky"
1757061,2018-11-06 06:01:18 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1757061,2018-12-14 05:17:29 UTC,"Reviewed:  https://review.openstack.org/608179
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4ac57b5aca18a91c6f29fe9c1a8fb0456c8c7785
Submitter: Zuul
Branch:    stable/queens"
1757061,2019-04-26 17:16:32 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1757061,2019-02-22 23:07:38 UTC,"Reviewed:  https://review.openstack.org/608180
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=58ed9bc606692c140d1cb315e83795b2e73ade9d
Submitter: Zuul
Branch:    stable/pike"
1757061,2019-03-22 03:47:01 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1757061,2018-12-19 20:48:22 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1757061,2018-10-05 08:09:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/608179"
1757061,2018-10-05 08:10:01 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/608180"
1757061,2018-10-05 00:46:00 UTC,"Reviewed:  https://review.openstack.org/555160
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=513f2d3d254e2ffcc5c9eb786bc1c7d52036d392
Submitter: Zuul
Branch:    master"
1757061,2018-10-05 06:34:45 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/608165"
1757061,2018-03-20 10:38:05 UTC,I am checking the bug on my Pike environment  where i have got the error.
1757061,2018-03-20 11:02:21 UTC,"if raise except as follow:   InstanceAgentNotEnabled,SetAdminPasswdNotSupported,NotImplementedError,NotImplementedError,UnexpectedTaskStateError,the vm's state is ACTIVE,
but vm's vm_state become ERROR if raise other except."
1757061,2018-03-21 07:10:45 UTC,https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L3522
1757061,2018-03-21 08:26:29 UTC,"did another check ...seems set_admin_password is a 'call' instead of 'cast', so looks like we can keep it as ACTIVE, let me try work on it"
1757061,2018-03-21 08:25:59 UTC,"fully understand the request, however, better to provide what's wrong there in order to decide based on more solid information.."
1757061,2018-03-22 06:10:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555160"
1757061,2018-03-21 07:57:25 UTC,"I think it's OK to give users a hint of information,rather than the virtual machine state is set to error.This led to the user cannot continue to operate the virtual machine, virtual machine also can work, just modify the password failed."
1757063,2018-03-21 10:27:07 UTC,"When using the --debug option, one can see the response from the neutron API like"
1757063,2018-06-01 09:27:35 UTC,"The patch fixed the bug.
https://review.openstack.org/#/c/571101/"
1757063,2018-06-01 09:52:20 UTC,"The SDK and OSC have migrated to using storyboard, the old bug reports like this one are no longer expected to be updated, see https://storyboard.openstack.org/#!/story/1757063 instead."
1757063,2018-06-18 00:49:09 UTC,This issue was fixed in the openstack/openstacksdk 0.14.0 release.
1757063,2019-10-22 20:05:18 UTC,This issue was fixed in the openstack/openstacksdk 0.11.4 release.
1757073,2018-03-20 23:03:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757073,2018-03-22 06:28:47 UTC,"problem disappeared with last updates and new snap version:
corrado@corrado-p13-bb-0319:~$ snap version
snap    2.32+18.04~pre6
snapd   2.32+18.04~pre6
series  16
ubuntu  18.04
kernel  4.15.0-12-generic
corrado@corrado-p13-bb-0319:~$"
1757073,2018-08-02 15:11:38 UTC,Same problem! Snaps mysteriously stop working.
1757075,2018-04-24 05:20:51 UTC,"Found several hits recently, increase priority by now"
1757075,2019-03-19 07:17:26 UTC,"Hi,"
1757075,2019-03-19 07:49:35 UTC,please paste your logs here
1757091,2020-01-14 14:31:10 UTC,"It's 2020 now and I can confirm this bug for Ubuntu 18.04.3 LTS, too."
1757091,2019-03-08 08:38:46 UTC,Is there a workaround tip in order to re-enable lightdm in ubuntu 18.04 ? I am using systemd.
1757091,2018-03-21 18:43:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757091,2018-03-21 18:45:50 UTC,"I do confirm the bug, fresh ubuntu 17.10 install"
1757091,2019-03-07 19:10:24 UTC,I confirm this bug for 18.04.
1757102,2019-08-08 09:31:26 UTC,"Reviewed:  https://review.opendev.org/674781
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=059248f86eb5800fef42fffe9ed737b6f2729626
Submitter: Zuul
Branch:    master"
1757102,2019-09-13 16:05:36 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1757107,2018-08-04 18:40:22 UTC,I have now adopted a workflow where I use dgit to verify that what is in the packaging git matches what is uploaded.
1757107,2018-06-20 13:35:16 UTC,"There are many packaging changes that were introduced in the security update, that regress security."
1757107,2018-06-28 21:56:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757107,2018-06-20 14:54:50 UTC,"> They have been introduced when the person doing the Ubuntu upload has recreated the debdiffs using a different base version.
"
1757107,2019-05-16 05:13:27 UTC,Fixed with 1:10.1.38-0ubuntu0.18.04.2 on bionic
1757107,2018-04-15 05:26:09 UTC,Unsubscribing the Sponsors Team for now as there's nothing to sponsor quite yet.
1757107,2018-07-01 21:35:19 UTC,Using git is good. The root of the problem here was that another DD had tagged commit https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/d6c1b1f9cac58d988882c3a0494c501e40d905b5 as https://salsa.debian.org/mariadb-team/mariadb-10.1/commits/debian/10.1.25-1 falsely.
1757107,2018-03-26 17:25:42 UTC,"Just to be clear, in https://salsa.debian.org/mariadb-team/mariadb-10.1/branches there is a branch for each Ubuntu release, and they have been branches of the release tag of the last Debian release they synced from and shipped with."
1757107,2018-03-31 17:37:45 UTC,@xnox Waiting for your comments. I would like to know where you get the sources you are comparing and what unfit-for-security-upload changes did you see in them exactly?
1757107,2018-03-26 13:13:25 UTC,"It is easiest if we list the commits that caused the regressions, and then selectively revert them."
1757107,2018-03-26 15:42:07 UTC,@otto
1757107,2018-06-20 14:04:21 UTC,Hello!
1757107,2018-03-26 16:51:34 UTC,"All of the changes in https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/diff/debian/?id=ubuntu/10.1.30-0ubuntu0.17.10.1&id2=debian/10.1.25-1 are packaging wise necessary minimum changes for the security update to work (e.g. refreshing patches, applying a FTBFS patch, adopt to upstream build artifact changes due to use of --fail-missing)."
1757107,2018-03-26 15:43:21 UTC,"The reason behind this debdiff, is that autopkgtests started to fail, and the database is not running after the install, which is grave."
1757107,2018-03-26 17:21:59 UTC,I am unable to figure out what has happened here.
1757122,2020-02-12 05:55:15 UTC,Hi
1757122,2020-04-13 04:17:25 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1757127,2020-11-15 20:28:39 UTC,Duplicate of #1848890
1757131,2018-03-20 16:17:41 UTC,"as far as I can tell, the link you have provided does not lead to an eps file that can be downloaded. Could you attach the eps file that you want to work with to this bug report for further testing?"
1757131,2020-09-09 16:37:43 UTC,Closing because INVALID.
1757140,2018-03-21 12:40:33 UTC,"Update:
I proceeded with further investigation and found the root of the problem. You can find more information to the issue I opened to pip https://github.com/pypa/pip/issues/5099"
1757143,2018-03-20 17:59:40 UTC,I'm going to go ahead and mark the kernel task as invalid as the workaround is to read /proc/modules as root.
1757143,2018-03-20 17:31:29 UTC,"After chatting with xnox on IRC, he discovered that the output of catting /proc/modules in 4.15 now depends on who is doing the catting."
1757143,2018-03-20 17:04:50 UTC,"So now I've got a dump of /proc/modules from 16.04.4 (4.13) and the issue is much more apparent:
ubuntu@xwing:~$ cat /proc/modules
nls_iso8859_1 16384 1 - Live 0x0000000000000000
ppdev 20480 0 - Live 0x0000000000000000
intel_rapl 20480 0 - Live 0x0000000000000000
x86_pkg_temp_thermal 16384 0 - Live 0x0000000000000000
intel_powerclamp 16384 0 - Live 0x0000000000000000
coretemp 16384 0 - Live 0x0000000000000000
kvm_intel 204800 0 - Live 0x0000000000000000
joydev 20480 0 - Live 0x0000000000000000
input_leds 16384 0 - Live 0x0000000000000000
kvm 589824 1 kvm_intel, Live 0x0000000000000000
irqbypass 16384 1 kvm, Live 0x0000000000000000
intel_cstate 20480 0 - Live 0x0000000000000000
intel_rapl_perf 16384 0 - Live 0x0000000000000000
mei_me 40960 0 - Live 0x0000000000000000
lpc_ich 24576 0 - Live 0x0000000000000000
wmi_bmof 16384 0 - Live 0x0000000000000000
mei 102400 1 mei_me, Live 0x0000000000000000
ie31200_edac 16384 0 - Live 0x0000000000000000
shpchp 36864 0 - Live 0x0000000000000000
parport_pc 32768 0 - Live 0x0000000000000000
parport 49152 2 ppdev,parport_pc, Live 0x0000000000000000
mac_hid 16384 0 - Live 0x0000000000000000
ib_iser 49152 0 - Live 0x0000000000000000
rdma_cm 57344 1 ib_iser, Live 0x0000000000000000
iw_cm 45056 1 rdma_cm, Live 0x0000000000000000
ib_cm 49152 1 rdma_cm, Live 0x0000000000000000
ib_core 217088 4 ib_iser,rdma_cm,iw_cm,ib_cm, Live 0x0000000000000000
iscsi_tcp 20480 0 - Live 0x0000000000000000
libiscsi_tcp 20480 1 iscsi_tcp, Live 0x0000000000000000
libiscsi 53248 3 ib_iser,iscsi_tcp,libiscsi_tcp, Live 0x0000000000000000
scsi_transport_iscsi 98304 4 ib_iser,iscsi_tcp,libiscsi, Live 0x0000000000000000
autofs4 40960 2 - Live 0x0000000000000000
btrfs 1101824 0 - Live 0x0000000000000000
raid10 49152 0 - Live 0x0000000000000000
raid456 143360 0 - Live 0x0000000000000000
async_raid6_recov 20480 1 raid456, Live 0x0000000000000000
async_memcpy 16384 2 raid456,async_raid6_recov, Live 0x0000000000000000
async_pq 16384 2 raid456,async_raid6_recov, Live 0x0000000000000000
async_xor 16384 3 raid456,async_raid6_recov,async_pq, Live 0x0000000000000000
async_tx 16384 5 raid456,async_raid6_recov,async_memcpy,async_pq,async_xor, Live 0x0000000000000000
xor 24576 2 btrfs,async_xor, Live 0x0000000000000000
hid_generic 16384 0 - Live 0x0000000000000000
hid_logitech_hidpp 32768 0 - Live 0x0000000000000000
hid_logitech_dj 20480 0 - Live 0x0000000000000000
usbhid 49152 0 - Live 0x0000000000000000
hid 118784 4 hid_generic,hid_logitech_hidpp,hid_logitech_dj,usbhid, Live 0x0000000000000000
raid6_pq 118784 4 btrfs,raid456,async_raid6_recov,async_pq, Live 0x0000000000000000
libcrc32c 16384 1 raid456, Live 0x0000000000000000
raid1 40960 0 - Live 0x0000000000000000
raid0 20480 0 - Live 0x0000000000000000
multipath 16384 0 - Live 0x0000000000000000
linear 16384 0 - Live 0x0000000000000000
i915 1830912 1 - Live 0x0000000000000000
crct10dif_pclmul 16384 0 - Live 0x0000000000000000
crc32_pclmul 16384 0 - Live 0x0000000000000000
ghash_clmulni_intel 16384 0 - Live 0x0000000000000000
pcbc 16384 0 - Live 0x0000000000000000
aesni_intel 188416 0 - Live 0x0000000000000000
drm_kms_helper 167936 1 i915, Live 0x0000000000000000
aes_x86_64 20480 1 aesni_intel, Live ..."
1757143,2018-03-20 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1757143,2018-03-20 15:29:20 UTC,"One CR got lost in the bug description.
So with the CR at the right position, you can see that I directly executed ""/usr/lib/plainbox-provider-resource-generic/bin/module_resource"" and the output of that starts with traceback in the next line(s) ..."
1757143,2018-03-20 16:46:29 UTC,"Ahhh, thanks Frank.  I was a bit confused initially :)"
1757143,2018-03-20 14:02:11 UTC,"Outcome: job passed
-------------[ Running job 23 / 113. Estimated time left: unknown ]-------------
------------------[ Collect information about kernel modules ]------------------
ID: com.canonical.certification::module
Category: com.canonical.plainbox::uncategorised
... 8< -------------------------------------------------------------------------
Traceback (most recent call last):
  File ""/tmp/nest-6gxdhm_0.80e53c0441ed77c4cf9047854d346bc637d09c9c37947a2f263c82c421d37b6a/module_resource"", line 73, in <module>
    sys.exit(main())
  File ""/tmp/nest-6gxdhm_0.80e53c0441ed77c4cf9047854d346bc637d09c9c37947a2f263c82c421d37b6a/module_resource"", line 62, in main
    for module in modules:
  File ""/tmp/nest-6gxdhm_0.80e53c0441ed77c4cf9047854d346bc637d09c9c37947a2f263c82c421d37b6a/module_resource"", line 57, in get_modules
    yield get_module(line)
  File ""/tmp/nest-6gxdhm_0.80e53c0441ed77c4cf9047854d346bc637d09c9c37947a2f263c82c421d37b6a/module_resource"", line 49, in get_module
    ""offset"": int(offset, 16)}
ValueError: invalid literal for int() with base 16: '0x'
------------------------------------------------------------------------- >8 ---
Outcome: job failed
-------------[ Running job 24 / 113. Estimated time left: unknown ]-------------
-------------------[ Collect information about dpkg version ]-------------------
ID: com.canonical.certification::dpkg
Category: com.canonical.plainbox::uncategorised
... 8< -------------------------------------------------------------------------
version: 1.19.0.5
architecture: s390x
------------------------------------------------------------------------- >8 ---
Outcome: job passed
-------------[ Running job 25 / 113. Estimated time left: unknown ]-------------
-------------[ Check that data for a complete result are present ]--------------
ID: com.canonical.certification::miscellanea/submission-resources
Category: com.canonical.plainbox::miscellanea
Job cannot be started because:
 - required dependency 'com.canonical.certification::dkms_info_json' has failed
 - required dependency 'com.canonical.certification::dmi' has failed
 - required dependency 'com.canonical.certification::dmi_attachment' has failed
 - required dependency 'com.canonical.certification::module' has failed
 - required dependency 'com.canonical.certification::raw_devices_dmi_json' has failed
Outcome: job cannot be started"
1757143,2018-03-20 16:56:57 UTC,"$ cat /proc/modules
iptable_filter 16384 0 - Live 0x          (null)
macsec 49152 0 - Live 0x          (null)
vsock_diag 16384 0 - Live 0x          (null)
vsock 45056 1 vsock_diag,[permanent], Live 0x          (null)
sctp_diag 16384 0 - Live 0x          (null)
sctp 385024 3 sctp_diag, Live 0x          (null)
dccp_diag 16384 0 - Live 0x          (null)
dccp 126976 1 dccp_diag, Live 0x          (null)
tcp_diag 16384 0 - Live 0x          (null)
udp_diag 16384 0 - Live 0x          (null)
raw_diag 16384 0 - Live 0x          (null)
inet_diag 24576 5 sctp_diag,dccp_diag,tcp_diag,udp_diag,raw_diag, Live 0x          (null)
unix_diag 16384 0 - Live 0x          (null)
af_packet_diag 16384 0 - Live 0x          (null)
netlink_diag 16384 0 - Live 0x          (null)
binfmt_misc 20480 1 - Live 0x          (null)
algif_rng 16384 0 - Live 0x          (null)
salsa20_generic 16384 0 - Live 0x          (null)
camellia_generic 32768 0 - Live 0x          (null)
cast6_generic 24576 0 - Live 0x          (null)
cast_common 16384 1 cast6_generic, Live 0x          (null)
serpent_generic 28672 0 - Live 0x          (null)
twofish_generic 16384 0 - Live 0x          (null)
twofish_common 28672 1 twofish_generic, Live 0x          (null)
lrw 20480 0 - Live 0x          (null)
algif_skcipher 16384 0 - Live 0x          (null)
tgr192 24576 0 - Live 0x          (null)
wp512 36864 0 - Live 0x          (null)
rmd320 20480 0 - Live 0x          (null)
rmd256 20480 0 - Live 0x          (null)
rmd160 20480 0 - Live 0x          (null)
rmd128 20480 0 - Live 0x          (null)
md4 16384 0 - Live 0x          (null)
algif_hash 20480 0 - Live 0x          (null)
af_alg 28672 3 algif_rng,algif_skcipher,algif_hash, Live 0x          (null)
8021q 40960 0 - Live 0x          (null)
garp 20480 1 8021q, Live 0x          (null)
mrp 20480 1 8021q, Live 0x          (null)
stp 16384 1 garp, Live 0x          (null)
llc 16384 2 garp,stp, Live 0x          (null)
dm_service_time 16384 1 - Live 0x          (null)
dm_multipath 40960 2 dm_service_time, Live 0x          (null)
scsi_dh_rdac 20480 0 - Live 0x          (null)
scsi_dh_emc 16384 0 - Live 0x          (null)
scsi_dh_alua 24576 2 - Live 0x          (null)
qeth_l2 57344 2 - Live 0x          (null)
genwqe_card 86016 0 - Live 0x          (null)
crc_itu_t 16384 1 genwqe_card, Live 0x          (null)
chsc_sch 20480 0 - Live 0x          (null)
eadm_sch 16384 0 - Live 0x          (null)
qeth 143360 1 qeth_l2, Live 0x          (null)
ctcm 102400 0 - Live 0x          (null)
ccwgroup 20480 2 qeth,ctcm, Live 0x          (null)
fsm 16384 1 ctcm, Live 0x          (null)
vfio_ccw 24576 0 - Live 0x          (null)
vfio_mdev 16384 0 - Live 0x          (null)
mdev 20480 2 vfio_ccw,vfio_mdev, Live 0x          (null)
zcrypt_cex4 16384 0 - Live 0x          (null)
vfio_iommu_type1 28672 0 - Live 0x          (null)
vfio 36864 3 vfio_ccw,vfio_mdev,vfio_iommu_type1, Live 0x          (null)
zcrypt 69632 1 zcrypt_cex4, Live 0x          (null)
sch_fq_codel 20480 3 - Live 0x          (null)
iscsi_tcp 20480 0 - Live 0x          (null)
libiscsi_tcp 32768 1 iscsi_tcp, Live 0x          (null)
rdma_ucm 28672 0 - Live 0x          (null)
ib_umad 24576 0 - Live 0x          (null)
ib_ipoib ..."
1757143,2018-03-20 15:25:47 UTC,"Is this some kind of a ""dependency packing solution of modules into a binary""? And is it big-endian aware?"
1757143,2018-03-20 15:06:52 UTC,"Frank,"
1757145,2018-03-20 14:28:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554567"
1757145,2018-05-09 15:48:22 UTC,"Change abandoned by Sagi Shnaidman (<email address hidden>) on branch: master
Review: https://review.openstack.org/554567
Reason: was done in https://review.openstack.org/#/c/563321/"
1757147,2018-05-02 01:18:07 UTC,"Hi,"
1757152,2018-06-01 09:55:08 UTC,fixed in https://review.openstack.org/#/c/559594/
1757152,2018-06-05 18:22:58 UTC,This issue was fixed in the openstack/python-zunclient 1.4.0 release.
1757173,2018-03-29 07:15:00 UTC,Mark the regression testing task as incomplete due to the failures in ubuntu_qrt_kernel_security test -  test_095_kernel_symbols_missing (bug 1751202)
1757173,2018-03-29 09:04:40 UTC,"Comment #4 on bug 1751202 states that a fix is already queued for 4.15 stable and that from the security team perspective the issue has no security impact and should not block promoting kernels. Given that, I'm marking regression-testing as 'Fix Released'."
1757173,2018-03-29 11:03:24 UTC,Certification tests not required for linux-hwe-edge.
1757173,2018-04-04 08:40:09 UTC,"Based on a devel kernel, no verifications."
1757173,2018-04-04 10:35:51 UTC,The package has been published and the bug is being set to Fix Released
1757190,2018-03-21 19:44:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/555029"
1757190,2018-04-20 13:13:18 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1757190,2018-03-22 04:28:16 UTC,"Reviewed:  https://review.openstack.org/554667
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5f3cca205581d45d92714ce1a909d4394b7812ff
Submitter: Zuul
Branch:    master"
1757190,2018-03-28 16:29:53 UTC,"Reviewed:  https://review.openstack.org/555029
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8706dc3f4fe44622d459b020b1c5adef392faa0c
Submitter: Zuul
Branch:    stable/queens"
1757190,2018-03-20 17:25:55 UTC,"I can tell that during migrate_disk_and_power_off from the virt driver on the source host, that the bdm.connection_info has the multiattach flag set because we get this message when disconnecting the volume from the first instance on the first host:"
1757190,2018-03-20 15:59:36 UTC,This is a bit confusing because I'm seeing the disk 'shareable' flag set in the guests in other multiattach tests:
1757190,2018-03-20 19:14:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554667"
1757190,2018-04-02 13:09:06 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1757190,2018-03-20 16:24:13 UTC,"The test_resize_server_with_multiattached_volume test creates two servers and a single multiattach volume, then attaches the volume to the two servers, resizes both servers and then detaches the volume from each."
1757191,2018-03-20 16:22:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1757191,2018-03-20 16:42:25 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1757191,2018-03-23 19:58:58 UTC,"Hi Joeseph, I got the tester to try 4.16 and the tests still fail for the same reason.  This is the test output indicating that /sys/class/net/DEVICENAME/speed still reports a -1 for the second port."
1757191,2018-04-03 18:40:51 UTC,Thanks for testing.  We now know this bug also exists upstream.  Do you happen to know if this is a regression?  Was there a prior kernel version that did not exhibit this bug?
1757191,2018-04-03 21:13:12 UTC,It looks like this happened perhaps sometime between 4.10 and 4.13:
1757191,2018-04-04 15:28:16 UTC,"We can perform a bisect to identify the commit that introduced this bug.  Would it be possible for the tester to test some kernels?  To perform a bisect, we need to identify the last kernel version that did not have the bug and the first version that did.  The first kernels to test would be:"
1757191,2018-07-24 09:32:18 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1757202,2019-12-28 05:39:36 UTC,"Drat, I meant to add this too:
Search keywords: linux mint switch user wrong resolution"
1757202,2019-09-11 13:16:01 UTC,"Same issue with Xubuntu 18.04.3
Used workaround with ""Files"" section, but I had to use /usr/lib/x86_64-linux-gnu/nvidia-430 path.
/usr/lib/x86_64-linux-gnu/nvidia/xorg and /usr/lib/x86_64-linux-gnu/xorg do not exist in my system."
1757202,2019-03-09 17:18:45 UTC,"What should be done if everything in post #2 is set as directed, but on the following step...:
glxgears -info |grep NVIDIA"
1757202,2019-12-28 05:38:49 UTC,"I just had this problem on a Mint-19.3 XFCE upgraded from 18.3.  For me, the fix was:"
1757202,2019-03-03 14:19:16 UTC,Same issue with Xubuntu 18.10 Cosmic and nvidia-driver-415.
1757202,2018-11-15 08:56:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757202,2018-05-24 08:20:11 UTC,The bug is not related to lightdm because it also occurs with gdm3.
1757202,2018-05-11 16:47:00 UTC,"I can confirm the bug on Xubuntu 18.04.
My graphics card is an nVidia GeForce GTX 570 (GF110)."
1757202,2019-03-03 14:55:57 UTC,Fixed with:
1757204,2018-03-21 10:54:42 UTC,"libindicator3-dev depends on libgtk-3-dev, and it appears it is not installable in parallel for two architectures:"
1757204,2018-03-21 11:02:32 UTC,The issue with libgtk-3-dev is bug #1317116.
1757204,2018-03-22 14:35:52 UTC,"Getting the -dev packages to be co-installable would require fixing libgtk-3*, but there is already value in having the library packages co-installable."
1757207,2019-03-22 03:47:30 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1757207,2018-10-08 21:50:45 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1757207,2018-10-08 21:45:31 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1757207,2018-10-08 20:53:35 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1757207,2018-10-03 14:26:29 UTC,"Reviewed:  https://review.openstack.org/604788
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ef5c02209a28510eee66edc8495acc6cd4e0993a
Submitter: Zuul
Branch:    stable/pike"
1757207,2018-09-26 15:46:44 UTC,"Reviewed:  https://review.openstack.org/604786
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=72d2e82e1275035c70cb6862ff15dc41b3d9b621
Submitter: Zuul
Branch:    stable/queens"
1757207,2018-09-25 12:16:19 UTC,"Reviewed:  https://review.openstack.org/604785
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c559c5b357f47ae2bed9397bbfb8b2e08dc5b8a5
Submitter: Zuul
Branch:    stable/rocky"
1757207,2018-09-24 13:54:31 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/604788"
1757207,2018-09-21 22:34:33 UTC,"""disabled"" is one thing - you can come back from that - but ""deleted"" is a one-way ticket ... no?"
1757207,2018-09-24 13:48:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604785"
1757207,2018-09-24 13:48:51 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/604786"
1757207,2018-03-21 21:18:19 UTC,"> su -s /bin/sh -c ""nova-manage cell_v2 discover_hosts --verbose"" nova
The deleted compute node will be added again as a new node.
"
1757207,2018-03-21 21:21:33 UTC,This is also related:
1757207,2018-03-28 13:57:55 UTC,"Hi Matt,"
1757207,2018-07-27 11:59:42 UTC,It appears that not accounting for deleted is discussed here: https://github.com/openstack/nova/blob/6be7f7248fb1c2bbb890a0a48a424e205e173c9c/nova/cmd/status.py#L114-L128
1757207,2018-07-06 22:57:39 UTC,Shouldn't the upgrade check simply discount deleted compute_nodes ?
1757207,2018-09-22 00:59:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604495"
1757207,2018-09-24 13:29:22 UTC,"Reviewed:  https://review.openstack.org/604495
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3e902313e9c3117e76d6adf88a2f104bc229374c
Submitter: Zuul
Branch:    master"
1757207,2018-05-28 04:17:37 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1757208,2018-03-20 16:54:56 UTC,"StacktraceTop:
 udisks_linux_drive_object_get_block (object=object@entry=0x7fbfb400c9f0, get_hw=get_hw@entry=0) at udiskslinuxdriveobject.c:476
 handle_eject (_drive=<optimized out>, invocation=0x7fbf9c007960, options=0x55a0d0b45f00) at udiskslinuxdrive.c:977
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fbfb1226880, fn=fn@entry=0x55a0cf0fdce0 <handle_eject>, rvalue=<optimized out>, avalue=avalue@entry=0x7fbfb1226790) at ../src/x86/ffi64.c:525
 g_cclosure_marshal_generic (closure=0x55a0d09b7e70, return_gvalue=0x7fbfb1226a50, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=<optimized out>) at ../../../../gobject/gclosure.c:1490"
1757208,2018-04-14 08:49:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757209,2018-03-21 08:47:35 UTC,"I guess you might be getting hit by
https://bugs.freedesktop.org/show_bug.cgi?id=92681
https://bugzilla.gnome.org/show_bug.cgi?id=756463"
1757211,2021-02-17 17:07:07 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1757212,2018-03-21 04:11:27 UTC,"The provided dxf file ""inkscape dxf train.dxf"" behaves as expected in six conventional CAD/CAM programs:
Fusion 360
SheetCamTNG
Alibre Design
LibreCad
MOI3D
V-Carve Pro"
1757212,2018-03-21 09:50:50 UTC,"Thanks, TD.  I'll relay your comments to the user."
1757212,2019-12-11 05:22:48 UTC,Will not migrate.  Closing.
1757215,2018-03-20 18:24:01 UTC,Or maybe this is the intended result?
1757215,2018-03-20 18:42:36 UTC,Also happens for other shapes.
1757215,2020-09-13 18:19:21 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1757217,2018-03-22 15:50:24 UTC,"Hi Joeseph,"
1757217,2018-03-22 20:07:27 UTC,That is good news.  That means Bionic should get the fix through the normal stable update process.
1757217,2018-03-21 16:25:00 UTC,Can you test the latest upstream stable 4.15 kernel? That will tell us if the fix in mainline was already cc'd to stable.  It can be downloaded from:
1757217,2018-03-20 20:12:18 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1757217,2018-03-21 13:56:43 UTC,I tried 4.16 and the behaviour there seems to follow the old experiences:
1757217,2018-03-20 18:30:07 UTC,This change was made by a bot.
1757218,2019-08-22 16:18:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1757218,2018-05-10 08:42:32 UTC,"Please try the kernel here:
https://people.canonical.com/~khfeng/lp1757218/"
1757218,2018-05-10 14:27:42 UTC,"Unfortunately, this kernel still has the same issue."
1757218,2018-06-09 14:05:09 UTC,"Sorry for the late reply for this issue. Does this issue also happen to cold boot? AFAICT, it only happens to reboot, right?"
1757218,2018-06-09 14:42:24 UTC,The issues happens only on cold boot. In a pattern of:
1757218,2018-06-11 17:45:14 UTC,"Added a delay init quirk, let's see if this kernel works:
https://people.canonical.com/~khfeng/lp1757218/"
1757218,2018-06-12 03:05:27 UTC,"This kernel version works, but I don't understand why testing a 4.17 version would be relevant on this case, as the first kernel fixed is 4.16-rc5 and, according to the checkout we've done before, the first good commit should be:"
1757218,2018-06-12 03:22:14 UTC,Forgot to mention you should test it with btusb.autosuspend=0
1757218,2018-06-12 03:45:26 UTC,"Ok, using btusb.autosuspend=0 with this kernel version worked. I tested to turn the notebook off and on 5 times and all times both Bluetooth and Wireless worked."
1757218,2018-06-12 19:16:23 UTC,Bionic kernel with the delay quirk:
1757218,2018-06-12 19:53:06 UTC,"This kernel did not work. On boot, the same messages that appeared with the other problematic kernels appear and the boot freezes."
1757218,2018-11-03 11:20:56 UTC,Please try if this kernel works. May need to reboot twice because the fix is in shutdown path.
1757218,2019-06-17 19:54:57 UTC,This bug was fixed in the package linux-oem - 4.15.0-1043.48
1757218,2019-07-03 11:03:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1757218,2019-07-03 13:02:41 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1757218,2019-07-03 13:07:18 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1757218,2019-07-03 18:54:35 UTC,"I tested 4.15.0-55-generic and after multiple times turning the computer on and off, both Bluetooth and Wireless network were working correctly all the times."
1757218,2019-07-08 09:39:46 UTC,This bug was fixed in the package linux-oem - 4.15.0-1045.50
1757218,2019-07-15 22:40:05 UTC,This bug was fixed in the package linux - 5.2.0-8.9
1757218,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1757218,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1757218,2018-04-17 19:52:34 UTC,"This file is one with the failed boot, unfortunately the kernel panic message don't appear. Unlike the other file with the failure I uploaded before, on this one the boot failed. I was helped on #ubuntu+1 on how to add netconsole to initramfs, so I was able to obtain the first 7 seconds of the log."
1757218,2018-11-03 16:01:46 UTC,I shutdown and turned on the computer using this kernel four times and in none the problem happened. With the default Bionic kernel the failure on boot would have happened twice.
1757218,2018-04-17 18:52:42 UTC,"Many tries were required until I could obtain a useful log. As it can be seen in the kernel command line, I had to add many debug options to obtain this."
1757218,2018-03-30 17:00:26 UTC,"This is funny, but the option btusb.enable_autosuspend=0 make the bug happen on v4.16-rc7. I'm seeing a pattern that, when I change the kernel version or a grub option, I can't just turn on and off the notebook twice (as it triggers normally), but thrice."
1757218,2018-03-20 18:30:14 UTC,This change was made by a bot.
1757218,2018-03-20 20:15:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1757218,2018-03-21 05:12:59 UTC,"The behavior appears to be much better with the kernel version 4.16-rc6. However, I think this is not 100% solved, as the following error is still (but now rarely) happening when disconnecting from a network:"
1757218,2018-03-21 12:11:22 UTC,usb 1-7 is the Bluetooth of the wireless module.
1757218,2018-03-21 13:13:09 UTC,This is the dmesg from when it failed yesterday.
1757218,2018-03-21 13:37:30 UTC,Looks like the ath10k_pci device drops off the PCI bus completely. I guess you can't find the device in `lspci` when this happens.
1757218,2018-03-21 16:03:22 UTC,"This is not happening with the kernel 4.16-rc6, so I added the tag kernel-fixed-upstream."
1757218,2018-03-22 05:01:28 UTC,Does it also get fixed by latest upstream stable kernel?
1757218,2018-03-22 14:09:44 UTC,With kernel version 4.15.12 the the problem is not fixed. It has the same behavior as 4.15.0-12.
1757218,2018-04-17 06:18:33 UTC,"Can you attach dmesg with ""btusb.enable_autosuspend=0"", and another dmesg without the parameter?"
1757218,2018-03-26 13:28:35 UTC,The first kernel fixed is 4.16-rc5.
1757218,2018-03-26 08:40:59 UTC,Can you find the first v4.16-rc* that fixes this issue? We need to backport the fix to Bionic's kernel.
1757218,2018-03-27 01:05:19 UTC,"Finally, after 10 kernels built, I've obtained the result. Here is the output:"
1757218,2018-03-27 14:20:56 UTC,"The kernel was updated today to version 4.15.0-13 and the commit ""Bluetooth: btusb: Use DMI matching for QCA reset_resume quirking"" was added. I have tested the notebook and now it is no longer failing to boot or booting without wireless and bluetooth."
1757218,2018-03-27 14:44:03 UTC,No problem. Does this somehow (magically) also fix the ethernet r8169 for you?
1757218,2018-03-27 16:00:48 UTC,"Don't mark this as fixed yet, it has just happened in a different way: it progressed further on boot until it froze at the a message like waiting for /dev/disk."
1757218,2018-03-27 20:33:52 UTC,"This is insane. I have reset that bisect and tried again using ""fixed"" and ""broken"" instead of ""new"" and ""old"" and, again, the bisect had the following:"
1757218,2018-03-27 20:39:55 UTC,The only thing I can think that is wrong is the configuration file of the kernels. They have some significant differences regarding Bluetooth.
1757218,2018-03-27 20:40:36 UTC,This is comparing the 4.15.0-13 kernel with the mainline kernel.
1757218,2018-03-29 07:10:29 UTC,"Do you have this issue when using v4.16-rc7 with kernel parameter ""btusb.enable_autosuspend=0""?"
1757218,2018-03-29 14:57:59 UTC,"No, using this parameter when using the kernel v4.16-rc7 do not cause the issue."
1757218,2018-03-30 07:56:11 UTC,"Because the commit you bisected has been included since 4.15.12, which you said the issue is not fixed (comment #10)."
1757218,2018-03-30 15:54:14 UTC,The bug is still the same. What happened was that the system froze at a different message in that particular try. Journalctl from a successful initialization showing the most common point of failure:
1757218,2018-03-26 14:44:49 UTC,"It's hard to say which commit(s) fixes the issue, so the fastest way is to bisect locally."
1757229,2018-03-20 19:08:46 UTC,"The generated container configuration had an incorrect lxc.rootfs.path parameter. Instead of ""lxc.rootfs.path = dir:/var/lib/lxc/OracleLinux7/rootfs"", it should have been ""lxc.rootfs.path = dir:/mnt/disks/hgst/part_3/var/storage/<ommitted>/lxc-images/OracleLinux7"". When --rootfs= argument is passed to the Oracle template."
1757229,2020-03-26 02:59:14 UTC,Our pre-generated oracle images are tested daily and seem to be working fine.
1757234,2020-03-08 20:13:14 UTC,Current version of the charm released the dashboards for all orgs.
1757234,2020-03-08 20:16:54 UTC,"Apologies, re-looked.  The current charm creates dashboards in the main org as described.  The assumption is made that additional users have at least read permission to the main org, and any additional orgs are made to allow admin access to users that do not need admin to the main org.  This behavior is by design, to view the Juju generated dashboards switch to the main org."
1757250,2018-10-11 01:52:58 UTC,"Reviewed:  https://review.openstack.org/603261
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=c8e3b996aed7707c222db35640adc9860b2c8839
Submitter: Zuul
Branch:    master"
1757250,2018-09-18 17:21:55 UTC,"> make sure all direct_client methods accept the headers kwarg
"
1757251,2018-03-21 12:43:17 UTC,"I'm the 'upstream' for this package, and packager in Debian, and I would also like to see this updated in the artful backports!"
1757251,2018-03-23 07:50:42 UTC,I confirm that expired keys should be updated.
1757262,2019-09-19 11:57:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1757266,2018-03-21 09:29:32 UTC,"Related Suspend bug (and fix) ""Desktop unable to Suspend when Inactive Edit"" bug #1757375"
1757271,2021-02-18 16:46:10 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1757271,2018-09-28 16:41:36 UTC,"Hey Steve,"
1757273,2018-03-21 01:48:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/554759"
1757273,2018-03-23 14:11:02 UTC,"Reviewed:  https://review.openstack.org/554759
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=be9854b0fdff22a72a9699a0900e53e0595bd533
Submitter: Zuul
Branch:    master"
1757273,2018-03-29 01:37:37 UTC,"Reviewed:  https://review.openstack.org/555901
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=505ba2a74a5496ce0975a3d512bd8cdeb4e7d55c
Submitter: Zuul
Branch:    stable/queens"
1757273,2018-04-02 13:09:04 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1757273,2018-04-20 13:13:13 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1757277,2018-03-20 22:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1757277,2018-03-21 15:50:52 UTC,"Commit 9baf30972b55 is in the Xenial kernel as of 4.4.0-98.  It sounds like you are running the 4.4.0-111 kernel, correct?"
1757277,2018-03-30 20:44:17 UTC,"@Drew
Do you have an update to the request above?"
1757277,2018-04-19 22:22:23 UTC,"Joseph,"
1757281,2019-12-21 23:23:50 UTC,"Hello, I am facing the same problem. Is there a any workaround? I would just like to set all the quotas to unlimited."
1757287,2021-01-09 22:17:20 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1757292,2018-03-22 22:32:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555481"
1757292,2018-04-04 14:14:04 UTC,"Reviewed:  https://review.openstack.org/555481
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bb8ba2cf568fda4c5c59352296b758705869fb2f
Submitter: Zuul
Branch:    master"
1757292,2018-04-20 13:12:59 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1757292,2019-05-09 16:14:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/658149"
1757292,2019-05-24 10:32:44 UTC,"Reviewed:  https://review.opendev.org/658149
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=89063ecb61edb31522b6f1ab3f10a682a6c17f5d
Submitter: Zuul
Branch:    stable/queens"
1757292,2019-07-10 21:39:49 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1757292,2018-03-21 00:25:22 UTC,"FWIW, calling setup_networks_on_host() from post_live_migration_at_destination() was added way back in Essex:"
1757303,2019-12-10 04:17:17 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1757303,2019-10-10 10:28:36 UTC,"Please set back to New if the answer to Ian's question is ""yes""."
1757303,2019-10-09 20:34:58 UTC,Is this still a problem with snaps in a more recent Ubuntu version and a more recent snapd version?
1757303,2018-03-26 19:07:04 UTC,"@Toan, I suggest creating a topic at https://forum.snapcraft.io/, referencing this bug and mentioning you are using Ubuntu Budgie 18.04 and there are no (relevant) security policy denials. This will get more people looking at the issue."
1757303,2018-03-25 11:40:28 UTC,I've just tried $ sudo journalctl --follow | grep audit with firefox today and it returned this:
1757303,2018-03-26 14:54:51 UTC,"@Toan, this is unrelated to input methods. You need only connect the network-observe interface to make the denial go away: 'sudo snap connect firefox:network-observe'."
1757303,2018-03-21 14:23:10 UTC,"It 'hanging there' is expected-- it is tailing the log and will only output security violations if it finds them. To be clear, you exercised the snap and tried to use these input methods while the command was running in the terminal?"
1757303,2018-03-21 13:29:04 UTC,"I can't see any output, it was hanging there."
1757303,2018-03-21 13:09:41 UTC,Do you have any security denials? Please run in a terminal:
1757303,2018-03-26 15:31:38 UTC,"Well, after trying with several other apps, I came to the conclusion that this problem is not the apps's fault, nor the snap. Maybe there's something wrong with ubuntu budgie 18.04 since I could use ibus with libreoffice last time in ubuntu 17.10, but in this version it doesn't work at all."
1757309,2018-03-22 03:16:04 UTC,Patch: https://review.openstack.org/#/c/554133/
1757309,2018-03-29 01:53:37 UTC,Fixed in https://review.openstack.org/#/c/554133/
1757320,2018-06-13 19:13:04 UTC,"Please don't hijack this bug. We only plan on fixing critical, obvious, user-facing bugs in Qt 4 going forward."
1757320,2020-03-08 02:40:19 UTC,Removed from debian testing and unstable:
1757320,2018-06-13 17:15:29 UTC,Providing a static archive would allow upward compatibility for future versions of Ubuntu on projects like mine (by providing a distribution independent statically compiled executables)
1757320,2020-03-09 05:57:29 UTC,"Removing packages:
 qt4-x11 4:4.8.7+dfsg-20ubuntu2 in focal
  libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal arm64
  libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal armhf
  libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal i386
  libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el
  libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal s390x
  libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal arm64
  libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal armhf
  libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal i386
  libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el
  libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal s390x
  libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal arm64
  libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal armhf
  libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal i386
  libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el
  libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal s390x
  libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal arm64
  libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal armhf
  libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal i386
  libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el
  libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal s390x
  libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal arm64
  libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal armhf
  libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal i386
  libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el
  libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal s390x
  libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal arm64
  libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal armhf
  libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal i386
  libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el
  libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal s390x
  libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal arm64
  libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal armhf
  libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal i386
  libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el
  libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal s390x
  libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal arm64
  libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal armhf
  libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal i386
  libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el
  libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal s390x
  libqt4-designer-dbg 4:4.8.7+dfsg-20ubuntu2 in focal amd64
  libqt4-designer-dbg 4:4.8.7+dfsg-20ub..."
1757320,2018-03-22 20:46:45 UTC,"This one need to replace current fwbuilder package:
https://github.com/fwbuilder/fwbuilder"
1757320,2018-03-22 02:17:51 UTC,"Instead of filing one megabug, I filed separate bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal"
1757320,2018-03-21 07:56:42 UTC,"ubuntu/fmit has been ported to Qt5 a while ago. Just need to use the last
version from github."
1757320,2018-03-21 04:06:44 UTC,"kdesudo can be removed from the archive as soon as my merged
ubuntu-release-upgrader change has been uploaded and has migrated."
1757320,2018-06-13 17:10:31 UTC,"Sorry, but what about solving Qt4 issues first https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1776717 ?"
1757323,2018-03-21 03:37:56 UTC,i should add: i do NOT get these crashes if I boot the same image on the host bare-metal.
1757323,2020-11-21 14:13:54 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1757323,2021-01-21 04:17:16 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1757326,2019-12-10 04:17:21 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1757326,2019-10-10 10:29:30 UTC,Please set back to New after answering Ian's questions.
1757326,2019-10-09 20:51:23 UTC,Is this still an issue for you?
1757326,2018-03-21 07:24:43 UTC,Are you sure it's just snaps? The journal errors attached suggest to me that your NIC may be missing firmware files or something similar:
1757326,2018-03-21 13:43:24 UTC,"flatpak versions of apps and apt-installed versions of apps work fine.  i was, for example, able to file this bug."
1757328,2018-04-19 06:34:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757342,2018-03-21 10:28:14 UTC,Hi gongysh. Can you please add the steps to reproduce this error? Thanks.
1757342,2018-03-28 09:48:29 UTC,Hi gongysh
1757344,2018-03-21 16:25:01 UTC,Hello and thank you for filing this bug!
1757344,2018-03-21 18:08:15 UTC,"yes, update-manager, actually I find no real problem, it just fire up this crash report and I supposed there was some problem so I filled the bug.
package php7.1-sqlite3 is correctly installed.
`dpkg --configure --pending` is silent, no package unconfigured."
1757344,2018-06-26 10:58:13 UTC,"Hi,
coming by checking older bugs - unfortunately there wasn't a good idea/log that helps us to continue on understanding this issue.
Due to that for now it is not really actionable and I'll mark it incomplete to reflect that."
1757347,2018-03-21 07:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1757353,2019-01-23 03:25:20 UTC,"HI, thanks for your report, could you share your scenario ? neutron.list_security_groups() should list security groups
to which the project has access."
1757354,2018-04-28 03:52:38 UTC,This bug exists in bionic-final 20180427 enhanced.
1757354,2018-04-26 09:20:47 UTC,The bug existed in bionic 20180425.1 i686.
1757354,2018-03-22 07:40:47 UTC,这边暂时没有复现。
1757354,2018-04-26 06:38:45 UTC,The bug existed in bionic 20180426 amd64.
1757363,2018-06-04 20:04:48 UTC,What model/cpu is your router?
1757363,2020-11-17 11:08:38 UTC,My guess is your router CPU doesn't match the ISA (likely your CPU has extensions to the 24Kf ISA).
1757363,2021-01-17 04:17:19 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1757371,2018-05-14 13:02:13 UTC,Thinking some more on this (and related to https://bugs.launchpad.net/nova-lxd/+bug/1756900) we can probably use the '-p' option in the zpool list to get a parseable output without having to use strutils.
1757371,2018-05-14 11:18:05 UTC,"We use oslo strutils to parse the number, which also isn't locale sensitive.  As zfs uses snprintf() for the number printing, and that IS locale sensitive, then yes, it would probably fail.  Work around is to not install on locale other than English."
1757371,2018-05-31 07:12:26 UTC,"Reviewed:  https://review.openstack.org/571226
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=97cb7ea742d4dbcc83079da33ebb4d7e66d0ee9c
Submitter: Zuul
Branch:    master"
1757375,2019-04-11 00:43:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757375,2019-04-11 10:48:44 UTC,Your workaround worked for me too. I'm running Xubuntu 18.04. Now I can suspend the machine.
1757375,2019-07-16 15:49:17 UTC,"The solution is right here, so simple to apply. Why is this ignored? No one else suspends their machines? Merge the necessary polkit rule, please."
1757375,2019-07-18 07:56:09 UTC,"It's not ignored but the bug is about a 3 years old version of Ubuntu and it got only one report in that time with 2 affect users, that makes it a pretty low priority issue."
1757375,2019-07-18 08:03:57 UTC,it's also weird because /usr/share/polkit-1/actions/org.freedesktop.login1.policy has
1757375,2019-09-05 18:38:42 UTC,"Thanks for the response. Sorry for the delay, I didn't get a notification about this."
1757375,2019-09-15 03:39:38 UTC,"I can also reproduce this on both of my computers running Xubuntu 19.04, a desktop and a laptop."
1757375,2020-03-23 02:46:30 UTC,Still a major laptop usability problem in eoan.
1757375,2020-04-26 03:15:33 UTC,"I think I can't reproduce this anymore on Xubuntu 20.04. I left the laptop idle and after 30 minutes it was suspended as expected, without making any fixes (clean install)."
1757375,2019-04-20 12:24:18 UTC,"No change in Disco. Still missing the entry at ""com.ubuntu.desktop.pkla""."
1757381,2019-02-03 15:00:35 UTC,"> tags is commonly separated by a space (like in launchpad, quicken and many other)
"
1757381,2018-03-22 15:36:27 UTC,BTW this is not a dupe of https://bugs.launchpad.net/homebank/+bug/1336928.
1757381,2019-03-30 14:58:56 UTC,"will be possible with GTK 4
https://blog.gtk.org/2019/03/15/entries-in-gtk-4/
https://gitlab.gnome.org/GNOME/gtk/blob/master/demos/gtk-demo/demotaggedentry.c"
1757381,2018-03-21 19:57:16 UTC,yes things to improve out there
1757381,2018-03-29 11:55:55 UTC,"to me it is a duplicate: the overall of those 2 wish is to improve the tags management process, no matter the way one user, another or you want it, this is the goal of duplicate: the what, not the how."
1757406,2018-09-21 13:05:40 UTC,"I made some comments about this issue on https://github.com/mixxxdj/mixxx/pull/1242
(wiezo)
The importance is that fixing this enables a constant beat pattern if desired."
1757406,2018-09-22 00:25:14 UTC,I have fixed this issue in https://github.com/mixxxdj/mixxx/pull/1242. The only remaining thing is to write a test for it (which is in my plan).
1757408,2018-03-23 14:42:11 UTC,Please retest with developer mode disabled. I wouldn't rate this as critical if it only happens when developer mode is enabled.
1757408,2018-03-23 23:20:49 UTC,"I'm sorry, I broadcast at A=432Hz, witch is only (nearclose) possible in developer mode. (pitch_adjust -0,32)"
1757408,2018-03-23 23:30:42 UTC,"I really appreciate the work you're doing, it is a great tool! Thanks!"
1757408,2018-03-24 13:26:32 UTC,I cannot reproduce this on win10 with the latest beta 64 bit
1757410,2018-03-21 22:10:33 UTC,"This could be a prove of concept, for a new AutoDJ transition feature."
1757412,2018-03-21 22:17:22 UTC,"The Browse feature bypasses the library by design. It shows the truth from the HD.
So the played column cannot be shown."
1757414,2018-04-15 08:34:01 UTC,"Please read Charpter 10.14.1 and 10.14.2. of the manual
Coppy the file sigcf.dat and sigscr.dat in a folder OpenRails in the mainfolder of the Route.
if needed increase in the File sigcfg.dat the parameters SignalNumClearAhead (  3 ore more  ) in the Blocks of signaltypes with ""SignalFnType ( NORMAL )"""
1757416,2019-09-17 15:33:19 UTC,The issue has been fixed long ago:
1757416,2019-09-17 10:08:05 UTC,Hi Otto. What's the status of this issue? Thanks!
1757422,2018-03-21 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1757422,2018-04-09 12:49:35 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1757422,2018-04-10 05:43:22 UTC,I can confirm r8169 enters D3 when no cable is plugged.
1757422,2018-04-23 12:52:04 UTC,This bug was fixed in the package linux-oem - 4.13.0-1024.27
1757422,2018-06-15 09:36:36 UTC,"this needs to be sent for bionic too, or linux-oem (4.13) -> -hwe (4.15) upgrade will regress"
1757422,2018-06-21 07:30:46 UTC,There are some subsequent fixes for r8169. I'll make a new backport for this in Bionic.
1757422,2018-07-24 09:34:24 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1757422,2019-06-17 19:54:57 UTC,This bug was fixed in the package linux-oem - 4.15.0-1043.48
1757428,2020-10-02 09:05:04 UTC,There is no release note content for Pike and Ocata: the development team didn't provide any at the time.
1757430,2021-02-17 17:10:32 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1757430,2018-03-23 14:47:24 UTC,This is high due to the security concerns.
1757435,2018-03-21 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1757435,2018-04-24 15:02:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1757435,2018-04-26 16:29:51 UTC,This bug was fixed in the package linux - 4.4.0-122.146
1757437,2019-01-09 14:28:08 UTC,Bug can be closed
1757437,2018-12-18 16:51:21 UTC,"Hey,
This is still happening, there is no dashboard, but there is a bigger problem -
Vitrage API address is not added to haproxy config."
1757437,2018-03-22 05:15:46 UTC,which install_type and distro are you using?
1757437,2018-03-22 06:40:06 UTC,"Hi Sir Jeffrey,"
1757442,2018-05-11 15:56:36 UTC,apport information
1757442,2018-05-11 15:56:35 UTC,apport information
1757442,2018-05-11 15:56:33 UTC,apport information
1757442,2018-05-11 15:56:32 UTC,apport information
1757442,2018-05-11 15:56:30 UTC,apport information
1757442,2018-05-11 15:56:29 UTC,apport information
1757442,2018-05-11 15:56:27 UTC,apport information
1757442,2018-05-11 15:56:22 UTC,apport information
1757442,2018-05-11 15:56:24 UTC,apport information
1757442,2018-05-11 15:56:26 UTC,apport information
1757442,2018-05-11 15:36:57 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1757442,2018-05-11 15:56:17 UTC,apport information
1757442,2018-05-11 15:56:21 UTC,apport information
1757442,2018-05-11 15:56:20 UTC,apport information
1757442,2018-05-11 15:56:19 UTC,apport information
1757442,2018-05-11 15:56:23 UTC,apport information
1757445,2019-04-02 14:54:19 UTC,"By the way, I connected back up the sound on my machine before that most recent crash.  So, it is not the cause (for anyone who may have considered that possibility)."
1757445,2019-04-02 14:43:08 UTC,"I have had 3 hangs between 24 March and 1 April.  All were when I was out and about, so I couldn't SSH into the machine."
1757445,2019-03-24 11:24:45 UTC,It hung again yesterday (S 23 Mar 2019).  It used to hang multiple times daily.
1757445,2019-03-22 15:30:33 UTC,"Err, the issue sounds a lot like Bug #1743094.  Maybe one should be marked as a duplicate of the other."
1757445,2019-03-22 15:27:41 UTC,This issue sounds a lot like Bug #1757445.  Maybe one should be marked as a duplicate of the other.
1757445,2019-03-22 15:17:49 UTC,"I forgot to mention that before demonstrating that ""Night Light"" and ""Dim screen when inactive"", I upgraded to the latest BIOS from Lenovo on 20 March (a day prior to posting #16 and before turning off the dimming features).  It is the Lenovo 85UJ25US (1.46) BIOS, which is an upgrade from 8BET55WW (1.35).  It was upgraded in hopes that it would resolve the problem."
1757445,2019-03-22 15:03:45 UTC,"By the way, this issue appeared on my machine, which is a Lenovo W520."
1757445,2019-03-21 19:37:32 UTC,I've found that I can make the system stable with the following settings:
1757445,2018-09-30 23:49:38 UTC,Just wanted to share my observations.
1757445,2018-08-24 00:07:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757445,2018-09-24 20:58:45 UTC,"Hi there, I'm running the kernel 4.15.0-34-generic #37 on an ASUS N752VX with the same problem too :
Blanked screen and pulsating power led.
When I try to wake up the system, the power LED would switch on, fans starts however the screen stays black. I've plugged an external screen, without result. I have to hard reboot each time."
1757445,2018-05-13 01:55:32 UTC,"I noticed the existence of this error during the boot: ""nouveau 0000: 01: 00.0: bus: MMIO read of 00000000 FAULT at 612004 [IBUS]"".
So I decided to search and found a suggestion to include the following parameter in the kernel command line ""nouveau.modeset = 0"". So I decided to test it and immediately the boot errors disappeared, there were no more crashes when suspending and resuming, just as there were no more crashes when shutting down. Either with the 4.16-0 kernel nor with the official 4.15.0-20 kernel.
I suggest to those affected by this bug that they try this suggestion."
1757445,2018-05-12 00:16:00 UTC,"I have been testing the Kernel 4.16.0 for two days, so far suspend and resume has been working without hanging
However, whenever I suspend and resume, at least once, when I try to shut down the system hangs and only accepts REISUB or forced shutdown.
Besides that, I lost the functionality of ureadahead, which does not work with ""upstream kernels""."
1757445,2018-05-10 17:04:09 UTC,"Please disregard comment # 7, I celebrated too early. After some time the problem returned.
I am currently testing the 4.16 kernel (0). In a few days I will post some results."
1757445,2018-05-09 12:44:18 UTC,"After some tests I discovered that, in my case, the locking is related to wireless. By disabling the wireless network the problem disappears, it suspends and returns normally.
So, as a test, I deactivated the power saving, as suggested in the link ""https://gist.github.com/jcberthon/ea8cfe278998968ba7c5a95344bc8b55"" and everything went smoothly."
1757445,2018-05-08 21:00:39 UTC,"Same fault with Dell Inspiron 5557. On resume it takes about 4 seconds and then the lock screen appears, when trying to unlock it accepts four to five digits and then hangs completely (nor REISUB works). The only option is manually power off."
1757445,2018-04-09 17:24:01 UTC,"Similar problem over here, resume reproducibly fails on my Dell Mini 1018:
STR seems to work properly when closing the lid:
Blanked screen, pulsating power led etc. When I try to wake up the system, the power LED would switch on, however the screen stays black."
1757445,2018-03-21 15:26:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1757445,2018-03-21 14:56:29 UTC,I'm seeing messages in syslog that show USB device(s) not reconnecting.  I spoke to Jamie and his monitor is connected over a USB-C dock.  That might be involved here.
1757445,2018-03-21 14:30:11 UTC,This change was made by a bot.
1757445,2018-07-18 20:36:52 UTC,"The bug also affects Xenial with Linux HWE (4.15.0.24.46).
No issues with Linux HWE (4.13.0.45.64)."
1757445,2018-05-13 01:57:19 UTC,"EDIT: ""nouveau.modeset=0"" no spaces."
1757447,2019-09-25 20:31:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757457,2018-03-21 23:14:35 UTC,"I built debuggable toolchain, obtained a core dump and ran gdb on it:"
1757464,2018-03-21 17:55:37 UTC,Thanks deray
1757464,2018-03-21 16:56:46 UTC,">> HTTP response for GET https://x.x.x.x/redfish/v1/SessionService: status code: 401, error: Base.1.0.0.GeneralError: unknown error
"
1757467,2018-04-03 05:35:18 UTC,This bug is still present in kubuntu 18.04 beta wayland session.
1757467,2018-03-22 02:02:18 UTC,"It's a KDE/Kubuntu bug only. Not a bug in the Wayland protocol, and not a bug in Gnome Shell."
1757467,2018-03-21 15:46:18 UTC,gnumeric's version is 1.12.35
1757472,2018-09-29 20:15:06 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/556670"
1757472,2018-03-27 16:33:41 UTC,This is where nova-conductor fails to start:
1757472,2018-03-27 16:30:17 UTC,This is a failure I get in nova-conductor without having [database]/connection set:
1757472,2018-03-26 22:21:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/556670"
1757472,2018-03-27 16:48:34 UTC,"However doing this means if in reality if an operator has forgotten to set CONF.database.connection in nova_cell1.conf for the cell, he/she will run in loops since it will now be pointing to cell0 without emitting a warning and hence will not figure out what is wrong? But I guess considering cell0 is the default cell it is okay to do so ? I am not sure."
1757472,2018-03-26 14:32:53 UTC,This seems to be where we blow up when [database]/connection isn't set for nova-api:
1757472,2018-03-22 16:10:57 UTC,Here is my test patch: https://review.openstack.org/555346
1757472,2018-03-22 14:08:35 UTC,OK I'll push a devstack patch to not set [database]/connection in nova.conf and see what blows up.
1757472,2018-03-22 10:21:21 UTC,"For example with nova-api.
If /database/connection is not specified it will try to connect to localhost:
2018-03-22 11:14:36.419 19615 WARNING oslo_db.sqlalchemy.engines [req-79c428ff-1c14-4225-9530-18e948f0798f - - - - -] SQL connection failed. -1 attempts left.: DBConnectionError: (_mysql_exceptions.Operat
ionalError) (2002, 'Can\'t connect to local MySQL server through socket \'/var/lib/mysql/mysql.sock\' (2 ""No such file or directory"")') (Background on this error at: http://sqlalche.me/e/e3q8)"
1757472,2018-03-21 21:14:34 UTC,Do you have some more information about the actual failure or a traceback? I think I've been surprised by this as well before and can't remember if there is a good reason for having [database]/connection set to cell0 when running nova-api.
1757472,2018-03-26 15:28:08 UTC,The problem is this code is not cell-aware:
1757473,2018-04-20 22:03:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757473,2018-05-06 22:16:39 UTC,Doing what Tallicia said gave me the following error:
1757473,2018-05-10 19:15:32 UTC,try this:
1757473,2018-07-01 16:06:07 UTC,+1 luitzen's solution worked for me to.
1757473,2018-05-02 03:22:00 UTC,"Following the following three steps, Steam launches now from Show Applications list in gnome."
1757482,2018-07-30 16:27:24 UTC,"Reviewed:  https://review.openstack.org/584326
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c1d2f13495b2eb925be6495840795ead5929fd0e
Submitter: Zuul
Branch:    stable/ocata"
1757482,2018-07-20 11:11:24 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/584326"
1757482,2018-07-21 06:36:03 UTC,"Reviewed:  https://review.openstack.org/584324
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8287d7f546e4ffe7a2ac32df50d6b465484f81cc
Submitter: Zuul
Branch:    stable/queens"
1757482,2018-07-26 17:18:50 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b3 development milestone.
1757482,2018-09-18 14:08:26 UTC,This issue was fixed in the openstack/neutron 12.0.4 release.
1757482,2018-11-06 06:09:55 UTC,This issue was fixed in the openstack/neutron 11.0.6 release.
1757482,2020-10-26 22:19:03 UTC,"None of the branches which ever carried this bug are in a maintained state (the release in which the fix first appeared in under extended maintenance already), so there is little point in entertaining an advisory now. Switching the OSSA task to invalid."
1757482,2018-07-20 11:10:32 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/584325"
1757482,2018-07-30 17:29:59 UTC,"Reviewed:  https://review.openstack.org/584325
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=988eceac27a9ad91775376b3b3fedf84963663a5
Submitter: Zuul
Branch:    stable/pike"
1757482,2018-07-20 11:09:58 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/584324"
1757482,2018-03-27 03:31:43 UTC,"Also, want to add that the 'public' network in the above example was created in this manner, with the external and shared flags set:"
1757482,2018-06-14 14:21:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575444"
1757482,2018-06-08 22:11:06 UTC,"I tested this seems like need to address another issue as comment 3 mentioned,
i created another subnet on public net with  allocation_pools  | {""start"": ""10.50.20.0"", ""end"": ""10.50.255.100""}"
1757482,2018-06-01 10:45:56 UTC,I completely agree with the comments from the reporter.
1757482,2018-05-31 22:35:30 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1757482,2018-05-30 20:04:47 UTC,Re-opened since bug 1774019 seems to be a duplicate.  In that case a user was able to add a router to a shared external network and it got the .1 address.  Looks like there is an edge case here we need to cover.
1757482,2018-05-26 04:17:48 UTC,[Expired for neutron because there has been no activity for 60 days.]
1757482,2018-03-27 02:57:29 UTC,"All,"
1757482,2018-03-22 13:30:51 UTC,Armondo I will work on providing more detail for the issue.  Received the below from Kevin Benton through the mailing list so wanted to add to the bug for additional feedback.
1757482,2018-03-22 06:35:49 UTC,"Thanks for reporting the issue. I suspect the issue should not be limited to linuxbridge. One part that's not clear is the sequence of commands you chose to plug the logical router on the network. If that was done through the CLI and using the add-interface command, that takes either a specific port or a subnet. In the latter case the IP ends up being auto-allocated from within the IP allocation pool. In the former case, that can be overridden but then it feels like the harm is somewhat self-inflicted?"
1757482,2018-07-13 02:20:39 UTC,"Reviewed:  https://review.openstack.org/575444
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=54aa6e81cb17b33ce4d5d469cc11dec2869c762d
Submitter: Zuul
Branch:    master"
1757485,2018-03-21 16:55:29 UTC,"StacktraceTop:
 malloc () from /tmp/apport_sandbox_7_4f320a/lib/x86_64-linux-gnu/libc.so.6
 g_markup_collect_attributes () from /tmp/apport_sandbox_7_4f320a/lib/x86_64-linux-gnu/libglib-2.0.so.0
 gs_appstream_create_app (plugin=plugin@entry=0x55918a9919e0, item=item@entry=0x55918c6e9c20, error=error@entry=0x7f5fff7fd878) at ../plugins/core/gs-appstream.c:57
 gs_plugin_refine_wildcard (plugin=plugin@entry=0x55918a9919e0, app=app@entry=0x7f5fec129300, list=list@entry=0x55918ea63c00, flags=flags@entry=2097184, cancellable=cancellable@entry=0x55918aac2c80, error=error@entry=0x7f5fff7fd878) at ../plugins/core/gs-plugin-appstream.c:548
 gs_plugin_loader_call_vfunc (helper=helper@entry=0x7f5fec12b460, plugin=plugin@entry=0x55918a9919e0, app=app@entry=0x7f5fec129300, list=0x55918ea63c00, list@entry=0x0, refine_flags=2097184, refine_flags@entry=0, cancellable=cancellable@entry=0x55918aac2c80, error=0x7f5fff7fdac8) at ../lib/gs-plugin-loader.c:597"
1757486,2018-05-07 09:10:49 UTC,I think health checks need more work in general and should be tailored to behave better for desktop applications. I don't know if we should solve it with user-level hooks though (exact semantics is unclear to me).
1757486,2018-03-22 11:25:05 UTC,"If it's just about needing an X server, I wonder if we could come up with an interim example that users root-level hooks with xvfb-run."
1757486,2018-03-28 14:21:21 UTC,"The Snapcraft team and I spoke about this more and pulling in xvfb-run would also pull in the X stack, which is too much."
1757500,2018-03-21 18:09:31 UTC,"Sorry, I spoke too soon. (I'm not familiar with Python - yet)"
1757507,2018-03-21 19:07:01 UTC,"Here it is:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1757507-restrict-opt-in-for-real"
1757507,2018-03-29 11:31:28 UTC,"While this patch addresses half of the issue, it doesn't actually address user search, so away goes the pullrequest tag. Will try to figure out how to make that all work out."
1757513,2018-03-21 20:28:59 UTC,I wonder why some extensions might want to use own description field. What can be different there comparing to standardattributes?
1757513,2018-03-22 06:24:32 UTC,The use of standardattrdescription should supersede the use of a pre-existing 'description' field on a resource. When Kevin introduced the code he figured out a way to make existing resources having the description field simply inherit the standard one and thus remove the old resource/code. Is the case you're facing a scenario where there's just left-overs?
1757513,2018-03-23 11:12:10 UTC,"Reviewed:  https://review.openstack.org/555016
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=21e0942c0c15949b96a42df2a46e0201b7704643
Submitter: Zuul
Branch:    master"
1757513,2018-04-03 18:15:51 UTC,"As shown in [1], the segment and security group extensions already define the 'description' attribute and are also both implemented with subclasses of HasStandardAttributes thus applicable to stdattrs."
1757513,2018-04-20 20:48:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/563298"
1757513,2018-05-14 09:39:53 UTC,"Reviewed:  https://review.openstack.org/563298
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0c112a9f8997472bc9bc27b11501fc18c2e35dd5
Submitter: Zuul
Branch:    master"
1757513,2018-05-30 19:51:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571292"
1757513,2018-06-02 13:43:46 UTC,"Reviewed:  https://review.openstack.org/571292
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cb0782ce611af6d9d1a063f10a96f8daf4115850
Submitter: Zuul
Branch:    master"
1757517,2013-04-27 02:02:42 UTC,"For what it's worth, the strategy we're using in musl seems to work well:"
1757517,2013-04-26 18:06:47 UTC,"Carlos, any update on this?"
1757517,2013-05-22 18:40:25 UTC,"(In reply to comment #36)

> Carlos, any update on this?
>
> We've just run into this problem again: java loading JNI code instrumented for
> profiling created thread stack blocks that were too small.
>
> It would be *really* nice for glibc to just do the right thing and account for
> __static_tls without users having to explicitly work around it (by adding
> __static_tls to their requested stack size).
"
1757517,2012-05-23 17:08:07 UTC,*** Bug 6976 has been marked as a duplicate of this bug. ***
1757517,2012-04-25 02:54:54 UTC,"maybe i'm reading it wrong, but if your goal is to round up to the next page, wouldn't you want to add __static_tls_size to size and then do the round up ?"
1757517,2012-05-23 16:41:15 UTC,"(In reply to comment #32)

> Paul pointed me to this bz when I submitted a patch to fix bug 6973 and bug
> 6976 today:
>
> http://sourceware.org/ml/libc-alpha/2012-05/msg01544.html
>
> If we're looking to fix all stack size and guard related issues in this bz,
> does it make sense to mark the other two bzs as duplicates of this one? I
> understand Carlos is coming up with a much more comprehensive fix for this.
"
1757517,2012-05-22 07:05:05 UTC,Paul pointed me to this bz when I submitted a patch to fix bug 6973 and bug 6976 today:
1757517,2012-04-25 20:09:56 UTC,"(In reply to comment #30)

> Perhaps I should round it up to the next page size after doing the increment.
> In #25 Paul suggested I do the roundup for the increment before adding.
>
> Or perhaps the safest is to do the roundup of the TLS size and after the add.
"
1757517,2012-04-25 18:24:01 UTC,Perhaps I should round it up to the next page size after doing the increment. In #25 Paul suggested I do the roundup for the increment before adding.
1757517,2012-05-23 17:07:56 UTC,*** Bug 6973 has been marked as a duplicate of this bug. ***
1757517,2013-11-23 09:20:11 UTC,"The same test case fails on glibc 2.5 (RHEL 5.10), but that is expected. I have an application, which dlopens plugins. It happens to be that dlopen fails with new plugins, ""cannot allocate memory in static TLS block""."
1757517,2012-04-24 22:35:39 UTC,"(In reply to comment #27)

> Created attachment 6363 [details]
> Proposed fix that only adds to the stack size if it's less than 16 times
> __static_tls_size
>
> This patch checks if the stack size is less than 16 times the
> __static_tls_size, and adds to it in that case.
>
> Carlos, I know you're working on this for trunk, but we'd like a fix for
> ChromeOS.
>
> What are your thoughts about this patch, Paul/Carlos/Mike?
"
1757517,2014-02-16 19:42:06 UTC,"*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugzilla."
1757517,2015-03-23 02:50:38 UTC,"FYI, the Rust compiler is linking every threaded Rust application against the glibc private symbol __pthread_get_minstack in order to work around this bug:"
1757517,2015-12-16 19:40:36 UTC,"The JVM is having trouble too, see the following core-libs-dev discussion:"
1757517,2015-12-16 20:22:41 UTC,"(In reply to Steven Schlansker from comment #43)

> The JVM is having trouble too, see the following core-libs-dev discussion:
>
> http://mail.openjdk.java.net/pipermail/core-libs-dev/2015-December/037557.
> html
>
> If you link the JVM as a library and use thread local storage, it is very
> hard for JVM internal threads to ensure that their stack is usable.
>
> From the Rust discussion, they link that the Go runtime had the exact same
> problem.
>
> How many languages are going to have to work around this broken behavior
> before there is a glibc fix? :(
"
1757517,2017-09-01 16:02:15 UTC,Two more data points: This also causes trouble for the Ruby runtime when configured to link against jemalloc. The full details are in https://github.com/jemalloc/jemalloc/issues/1006 . We've also hit this in some vendor-supplied code at Facebook.
1757517,2018-01-29 23:27:02 UTC,"Following on comment 42, we should note that Anders then switched Rust to use a dlsym lookup instead of weak linkage:
https://github.com/rust-lang/rust/pull/23631"
1757517,2018-03-21 19:03:14 UTC,"To see the problem in Jack, this example from the Jack project can do it:"
1757517,2018-03-21 19:09:53 UTC,Upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=11787
1757517,2018-04-05 06:57:56 UTC,*** Bug 23018 has been marked as a duplicate of this bug. ***
1757517,2020-02-24 02:39:24 UTC,"Hi guys,"
1757517,2020-02-26 02:09:50 UTC,"(In reply to Wang Liushuai from comment #48)

> Hi guys,
>
> In ByteDance, we hit this Glibc bug twice in real-world production and
> adopted the fix based on the OpenJDK solution. However, these temporary
> fixes are not extensible. In the end, it needs to be fixed on the Glibc side.
"
1757517,2013-11-24 15:58:42 UTC,"(In reply to David Abdurachmanov from comment #39)

> I do assume ""cannot allocate memory in static TLS block"" is related to huge
> TLS segments size. It most likely doesn't fit into TLS space. Is there a
> quick way to confirm this, or I need to debug dynamic loader?
>
> The fix is not in 2.18 as I understood, any progress for 2.19?
"
1757517,2012-04-24 22:02:55 UTC,"Created attachment 6363
Proposed fix that only adds to the stack size if it's less than 16 times __static_tls_size"
1757517,2012-03-24 18:29:24 UTC,"(In reply to comment #15)

> But I will go ahead and contact distribution maintainers,
> as Carlos suggested in comment#10.
"
1757517,2012-03-30 16:44:43 UTC,"(In reply to comment #24)

> I think the real question here isn't the change in the size of the stack but
> the increase in the # of pages and potential wastage.
>
> If the TLS is small won't we end up burning an entire page for this small
> amount of data?  For apps that use small stacks and lots of threads, that extra
> page could turn out to be significant.
"
1757517,2012-04-01 19:46:32 UTC,"(In reply to comment #25)

> There's no perfect solution here.  I wonder if we could come up with a good
> heuristic based on the relative sizes of the TLS and thread requested stack.
> If the TLS is sufficiently small relative to the size of the requested stack,
> then just fold the TLS into the requested stack like we've always done.
> Otherwise, add the size of the TLS to the size of the requested stack (rounding
> to a page of course).  Harder to document and implement, but seems like it'd
> strike a better balance.
>
> I don't know where the cutoff should be, 1%, 10%, 50%? Some experimentation may
> guide us.
"
1757517,2010-07-02 23:02:12 UTC,This is a continuation of issue 10643.
1757517,2010-07-02 23:03:01 UTC,"Created attachment 4869
test case from pr10643"
1757517,2012-02-24 04:34:48 UTC,Ping?
1757517,2012-03-23 20:34:37 UTC,"I've reviewed the patch sent to the mailing list and provided comments:
http://sourceware.org/ml/libc-alpha/2012-03/msg01002.html"
1757517,2012-03-23 20:37:19 UTC,If the minimal values computes by the code are not enough then the only real solution is to fix the programs with large per-thread memory requirements e.g. set RLIMIT_STACK to a reasonable value.
1757517,2012-03-23 21:32:30 UTC,(In reply to comment #5)
1757517,2012-03-23 22:06:50 UTC,I can provide some information about Chrome built with -fprofile-generate:
1757517,2012-03-23 22:46:37 UTC,"(In reply to comment #6)

> (In reply to comment #5)
>
> Carlos,
>
> I don't believe you've understood the problem.
>
> Default stack sizes are fine.
>
> But aio_write creates a small (16K) stack, and chrome creates 128K stacks.
>
> Normally this is also just fine; and all works.
>
> But then application creates a larger-than-usual TLS (either by allocating
> 4096 thread-local ints as in the test case here, or by instrumenting for
> profiling), and suddenly things start crashing in hard-to-diagnose fashion.
"
1757517,2012-03-23 22:50:12 UTC,"(In reply to comment #7)

> I can provide some information about Chrome built with -fprofile-generate:
>
> p __static_tls_size
> $1 = 114880
>
> Now let's look at how Chrome allocates thread stacks:
>
> http://code.google.com/p/chromium/source/search?q=kShutdownDetectorThreadStackSize&origq=kShutdownDetectorThreadStackSize&btnG=Search+Trunk
>
> http://code.google.com/p/chromium/source/search?q=kWorkerThreadStackSize&origq=kWorkerThreadStackSize&btnG=Search+Trunk
>
> are two examples. There are other stack sizes too. From what I have seen, if
> the stack size is less than __static_tls_size, it just fails to allocate the
> stack. If it is something like 128k, it gets allocated, but soon runs out of
> stack into the guard page where it causes a segfault on a random function (as
> it allocating locals for the function).
"
1757517,2012-03-23 23:01:14 UTC,"Paul et al.,"
1757517,2012-03-23 23:02:38 UTC,"Joseph,"
1757517,2012-03-22 19:39:25 UTC,"Created attachment 6297
Proposed fix."
1757517,2012-03-24 16:05:19 UTC,"(In reply to comment #12)

> (In reply to comment #8)
>
> > Please note that the aio helper thread *should* be using a default 2MB stack on
> > x86, not 16K, I don't see anywhere that sets the helper threads stack to 16K.
>
> The helper thread stack size *is* set by __pthread_get_minstack.
"
1757517,2012-03-24 17:08:10 UTC,"the increased size should only matter if the new size pushes past a page boundary right ?  and even then, it'd only be 4KiB per thread ?"
1757517,2012-03-24 17:39:41 UTC,"(In reply to comment #14)

> the increased size should only matter if the new size pushes past a page
> boundary right ?  and even then, it'd only be 4KiB per thread ?
"
1757517,2012-03-24 20:12:51 UTC,"(In reply to comment #14)

> the increased size should only matter if the new size pushes past a page
> boundary right ?  and even then, it'd only be 4KiB per thread ?
>
> i don't see that being a problem.
"
1757517,2012-03-24 20:45:11 UTC,"On my desktop (based on Ubuntu Lucid), in /usr/bin, there are 430 executables that link to libpthread.so, but only 4 of them have TLS:"
1757517,2012-03-24 20:56:57 UTC,"(In reply to comment #18)

> On my desktop (based on Ubuntu Lucid), in /usr/bin, there are 430 executables
> that link to libpthread.so, but only 4 of them have TLS:


[At worst 160 bytes]

> I rest my case ;-)
"
1757517,2012-03-25 05:28:43 UTC,"on my Gentoo/x86_64 system with about 2000 packages installed that covers quite a range of categories of software, here's my stats (using scanelf to count non-symlinked ELFs in various dirs):"
1757517,2012-03-30 16:19:32 UTC,I think the real question here isn't the change in the size of the stack but the increase in the # of pages and potential wastage.
1757517,2012-03-26 11:02:14 UTC,"I think it will least surprise users if ""stack"" means the stack actually
available to the thread, not including implementation details such as TLS,
so they can work with tools that determine the amount of stack space used
by individual functions to work out how large a stack may be needed."
1757517,2012-03-26 14:28:05 UTC,"(In reply to comment #21)

> I think it will least surprise users if ""stack"" means the stack actually
> available to the thread, not including implementation details such as TLS,
> so they can work with tools that determine the amount of stack space used
> by individual functions to work out how large a stack may be needed.
"
1757517,2012-03-27 19:08:13 UTC,I'm assigning this issue to myself since it seems that nptl/allocatestack.c and nptl/nptl-ini.c need cleanup regarding the definition of stack.
1757517,2012-03-24 02:21:06 UTC,(In reply to comment #8)
1757519,2018-03-23 13:43:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757529,2018-03-21 20:44:10 UTC,"Historical context (thanks, Julian): http://paste.ubuntu.com/p/qFfThVFChK/"
1757529,2018-03-21 20:29:26 UTC,"Attached apt term.log shows the history:
- 36 is running
- 31 is purged
- 37 is installed
- 32 is purged
- 38 is installed
- 37 is *not* purged
- rebooted to 38
- 36 and 37 are still not purged"
1757529,2018-03-21 20:36:48 UTC,"As an alternative to running /etc/kernel/postinst.d/apt-auto-removal on boot, the code could be changed so that 37 is not retained once 38 is installed.  I can't remember now if there was a rationale for marking second-newest kernel for retention, in the case where that kernel had never been booted."
1757530,2018-12-27 17:10:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757530,2018-12-27 17:18:35 UTC,"In my case, I encountered this error while trying to install to a disk that had a pre-existing lvm lvgroup on it. I was able to resolve the error by using gparted from the livecd to manually wipe the existing partition table. After wiping the disk, I restarted the installation process successfully."
1757534,2018-03-21 20:49:23 UTC,A model config to be used with juju as a workaround:
1757534,2020-07-03 19:29:48 UTC,"Hi, we have the same issue at a customer at the moment, and preferably would not use the workaround suggested by Dmitrii. The customer will be deploying the system in this manner for all future builds. It would be good to get some guidelines on when we could get a resolution to this"
1757548,2018-03-21 21:34:09 UTC,apport information
1757548,2018-03-21 22:00:07 UTC,This change was made by a bot.
1757548,2018-03-21 21:34:20 UTC,apport information
1757548,2018-03-21 21:34:17 UTC,apport information
1757548,2018-03-21 21:34:13 UTC,apport information
1757548,2018-03-21 21:34:12 UTC,apport information
1757548,2018-03-21 21:34:10 UTC,apport information
1757548,2018-03-21 21:34:08 UTC,apport information
1757548,2018-03-21 21:30:55 UTC,Printscreen of my problem.
1757548,2018-03-21 21:34:06 UTC,apport information
1757548,2018-03-21 21:34:04 UTC,apport information
1757548,2018-03-21 21:34:03 UTC,apport information
1757548,2018-03-21 21:34:02 UTC,apport information
1757548,2018-03-21 21:34:00 UTC,apport information
1757548,2018-03-21 21:33:59 UTC,apport information
1757548,2018-03-21 21:33:58 UTC,apport information
1757548,2018-03-21 21:34:07 UTC,apport information
1757550,2020-06-18 15:21:03 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/736743"
1757550,2020-06-18 15:22:09 UTC,"Change abandoned by Samuel BARTEL (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/736743"
1757550,2020-06-18 15:31:56 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/736746"
1757555,2018-03-21 22:22:37 UTC,Correction - the second system is not failing.  All snap installed application are running OK.  Could be the mix of application installed on this system.  List of snaps installed;
1757555,2018-03-22 15:22:52 UTC,Thought both my laptop and desktop were failing to start snap installed applications but recheck the desktop yesterday and found snap installed application were OK.  After starting the laptop and running update/upgrade (do that every morning) the snap applications are starting again.  Please close this bug out.
1757555,2019-10-10 10:30:52 UTC,"Setting to Invalid to ""close this bug out"" as requested, although it would've been nice to figure out what was going on."
1757563,2021-01-05 17:59:12 UTC,launchpad-dependencies (0.137) xenial; urgency=medium
1757565,2018-04-10 14:11:43 UTC,Verified artful-proposed.
1757565,2018-04-10 09:32:50 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1757565,2018-03-26 14:06:17 UTC,"Joseph,
Thanks for providing the link to the mailing list post.  That is very
helpful."
1757565,2018-03-23 20:15:42 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090976.html"
1757565,2018-03-23 19:17:47 UTC,That's great news.  I'll SRU those two commits to the Artful kernel.
1757565,2018-03-23 18:01:19 UTC,Test kernel: GOOD
1757565,2018-03-23 17:27:45 UTC,I built an Artful test kernel with commit e3b8a48.  It also needed commit f48bf66b6 as a prereq.
1757565,2018-03-23 16:57:52 UTC,"Yeah, rc2 was fine."
1757565,2018-03-23 15:51:25 UTC,It looks like that commit landed in -rc3:
1757565,2018-03-23 15:55:42 UTC,"Hmm, even though git describe returns that tag, it seem s-rc2 has that commit."
1757565,2018-04-23 09:21:59 UTC,This bug was fixed in the package linux - 4.13.0-39.44
1757565,2018-03-23 15:38:35 UTC,Thanks for doing all the leg work.  I'll build a test kernel with that commit and post it shortly.
1757565,2018-03-22 21:58:31 UTC,v4.15 Final: GOOD
1757565,2018-03-23 14:33:59 UTC,v4.15-rc6: GOOD
1757565,2018-03-21 23:30:05 UTC,This change was made by a bot.
1757565,2018-03-22 15:17:38 UTC,"I'd like to perform a ""Reverse"" bisect to figure out what commit fixes this bug.  We need to identify the last kernel version that had the bug, and the first kernel version that fixed the bug."
1757565,2018-03-22 19:27:57 UTC,The Bionic 4.15.0-12 kernel is based off of upstream 4.15.7.  Can you test that kernel as well?  That will tell us if the fix in Bionic is an Ubuntu SAUCE patch or a 4.15 stable update.
1757565,2018-03-22 19:34:45 UTC,An upstream commit landed for this bug.
1757565,2018-03-22 16:40:36 UTC,v4.14-rc1: BAD
1757565,2018-03-22 19:56:22 UTC,"@Scott, will that upstream commit make it so the kernel fix we are looking for is not required?"
1757565,2018-03-22 20:18:42 UTC,"On Thu, Mar 22, 2018 at 2:56 PM, Joseph Salisbury
<email address hidden> wrote:

> @Scott, will that upstream commit make it so the kernel fix we are
> looking for is not required?
"
1757565,2018-03-22 20:32:59 UTC,"Thanks for the info, Ryan."
1757565,2018-03-22 23:09:22 UTC,"That would indicate the fix is in from v4.15-rc2 -> 4.15 Final.  I'll review the commits in that range, but there are probably thousands of them.  It will help to narrow it down further.  Could you test the 4.15 release candidates on the following page to find the last good kernel and first bad kernel:"
1757565,2018-03-22 19:46:07 UTC,v4.15.7: GOOD
1757565,2018-03-23 14:55:05 UTC,This looks promising and landed in -rc2:
1757567,2018-03-22 07:19:55 UTC,fixed in bionic
1757570,2018-04-25 20:56:02 UTC,Hey folks - anything I can do to bump / help this backport request along?  Thanks!
1757576,2018-04-20 00:05:42 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1757576,2018-03-22 00:41:35 UTC,"StacktraceTop:
 settings_backend_path_changed (target=0x1aff610, backend=<optimized out>, path=0x7f65d0015090 ""/"", origin_tag=0x0) at ../../../../gio/gsettings.c:460
 g_settings_backend_invoke_closure (user_data=0x1ad9100) at ../../../../gio/gsettingsbackend.c:267
 g_main_dispatch (context=0x179fec0) at ../../../../glib/gmain.c:3177
 g_main_context_dispatch (context=context@entry=0x179fec0) at ../../../../glib/gmain.c:3830
 g_main_context_iterate (context=0x179fec0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3903"
1757576,2018-03-30 06:11:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757583,2018-03-22 03:34:18 UTC,I further investigated this problem. My initial report was based on annotations to a document sent by a bank. Some forums report that document DRM properties affect the ability to create/edit annotation. See:
1757590,2019-03-04 22:18:28 UTC,"Removing packages from disco:
 amarok 2:2.9.0-0ubuntu6 in disco
  amarok 2:2.9.0-0ubuntu6 in disco amd64
  amarok 2:2.9.0-0ubuntu6 in disco arm64
  amarok 2:2.9.0-0ubuntu6 in disco armhf
  amarok 2:2.9.0-0ubuntu6 in disco i386
  amarok 2:2.9.0-0ubuntu6 in disco ppc64el
  amarok 2:2.9.0-0ubuntu6 in disco s390x
  amarok-common 2:2.9.0-0ubuntu6 in disco amd64
  amarok-common 2:2.9.0-0ubuntu6 in disco arm64
  amarok-common 2:2.9.0-0ubuntu6 in disco armhf
  amarok-common 2:2.9.0-0ubuntu6 in disco i386
  amarok-common 2:2.9.0-0ubuntu6 in disco ppc64el
  amarok-common 2:2.9.0-0ubuntu6 in disco s390x
  amarok-dbg 2:2.9.0-0ubuntu6 in disco amd64
  amarok-dbg 2:2.9.0-0ubuntu6 in disco arm64
  amarok-dbg 2:2.9.0-0ubuntu6 in disco armhf
  amarok-dbg 2:2.9.0-0ubuntu6 in disco i386
  amarok-dbg 2:2.9.0-0ubuntu6 in disco ppc64el
  amarok-dbg 2:2.9.0-0ubuntu6 in disco s390x
  amarok-doc 2:2.9.0-0ubuntu6 in disco amd64
  amarok-doc 2:2.9.0-0ubuntu6 in disco arm64
  amarok-doc 2:2.9.0-0ubuntu6 in disco armhf
  amarok-doc 2:2.9.0-0ubuntu6 in disco i386
  amarok-doc 2:2.9.0-0ubuntu6 in disco ppc64el
  amarok-doc 2:2.9.0-0ubuntu6 in disco s390x
  amarok-utils 2:2.9.0-0ubuntu6 in disco amd64
  amarok-utils 2:2.9.0-0ubuntu6 in disco arm64
  amarok-utils 2:2.9.0-0ubuntu6 in disco armhf
  amarok-utils 2:2.9.0-0ubuntu6 in disco i386
  amarok-utils 2:2.9.0-0ubuntu6 in disco ppc64el
  amarok-utils 2:2.9.0-0ubuntu6 in disco s390x
Comment: Removed from Debian testing; Debian bug #784448
1 package successfully removed."
1757591,2020-03-05 08:43:00 UTC,Already removed:
1757594,2019-08-28 21:48:25 UTC,appmenu-qt has been removed from the Eoan archive.
1757600,2020-02-06 11:01:17 UTC,"autopilot-touch is now green in NBS, after that autopilot-qt can be removed from Ubuntu Archive."
1757600,2020-02-13 10:58:47 UTC,Please remove autopilot-qt from focal: src and binaries
1757600,2020-02-13 22:39:39 UTC,"Removing packages from focal:
 autopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal
  autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal amd64
  autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal arm64
  autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal armhf
  autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal ppc64el
  autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal s390x
  autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal amd64
  autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal arm64
  autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal armhf
  autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal ppc64el
  autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal s390x
  libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal amd64
  libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal arm64
  libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal armhf
  libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal ppc64el
  libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal s390x
  libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal amd64
  libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal arm64
  libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal armhf
  libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal ppc64el
  libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal s390x
  qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal amd64
  qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal arm64
  qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal armhf
  qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal ppc64el
  qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal s390x
Comment: Unmaintained, depends on obsolete Qt4, last upload 5 years ago; LP: #1757600
1 package successfully removed."
1757612,2020-02-13 20:14:58 UTC,Please remove from focal. src and binaries.
1757612,2020-02-14 01:12:09 UTC,Maybe it's duplicate with Bug #1862105?
1757627,2019-11-26 16:14:21 UTC,This bug was fixed in the package dhcpcd-ui - 0.7.5-0ubuntu3
1757628,2020-02-07 18:43:44 UTC,Does not look like anyone in Debian is stepping up to package the 2.x Qt5 version of this.
1757629,2019-11-27 07:54:21 UTC,Fixed in 1.1.1~dfsg0-2
1757647,2020-03-03 10:04:40 UTC,This has now been removed from unstable in addition to testing.
1757647,2020-03-03 22:39:22 UTC,"Removing packages:
 gle-graphics 4.2.5-7build1 in focal
  gle-graphics 4.2.5-7build1 in focal amd64
  gle-graphics 4.2.5-7build1 in focal arm64
  gle-graphics 4.2.5-7build1 in focal ppc64el
  gle-graphics 4.2.5-7build1 in focal s390x
  gle-graphics-dbgsym 4.2.5-7build1 in focal amd64
  gle-graphics-dbgsym 4.2.5-7build1 in focal arm64
  gle-graphics-dbgsym 4.2.5-7build1 in focal ppc64el
  gle-graphics-dbgsym 4.2.5-7build1 in focal s390x
Comment: (From Debian) RoQA; Depends on Qt4; Debian bug #952996
Remove [y|N]? y"
1757652,2019-11-02 10:01:54 UTC,This bug was fixed in the package gr-fosphor - 3.8~1.278b66e-2
1757655,2019-10-16 18:13:24 UTC,"Removing packages:
        hamfax 0.8.1-1build2 in eoan
                hamfax 0.8.1-1build2 in eoan amd64
                hamfax 0.8.1-1build2 in eoan arm64
                hamfax 0.8.1-1build2 in eoan armhf
                hamfax 0.8.1-1build2 in eoan i386
                hamfax 0.8.1-1build2 in eoan ppc64el
                hamfax 0.8.1-1build2 in eoan s390x
                hamfax-dbgsym 0.8.1-1build2 in eoan amd64
                hamfax-dbgsym 0.8.1-1build2 in eoan arm64
                hamfax-dbgsym 0.8.1-1build2 in eoan armhf
                hamfax-dbgsym 0.8.1-1build2 in eoan i386
                hamfax-dbgsym 0.8.1-1build2 in eoan ppc64el
                hamfax-dbgsym 0.8.1-1build2 in eoan s390x
Comment: (From Debian) RoQA; Depends on Qt4, dead upstream, unmaintained; Debian bug #940133
Remove [y|N]? y"
1757657,2020-03-09 05:40:45 UTC,"Removing packages from focal:
 heimdall-flash 1.4.1-2 in focal
  heimdall-flash 1.4.1-2 in focal amd64
  heimdall-flash 1.4.1-2 in focal arm64
  heimdall-flash 1.4.1-2 in focal armhf
  heimdall-flash 1.4.1-2 in focal ppc64el
  heimdall-flash 1.4.1-2 in focal s390x
  heimdall-flash-frontend 1.4.1-2 in focal amd64
  heimdall-flash-frontend 1.4.1-2 in focal arm64
  heimdall-flash-frontend 1.4.1-2 in focal armhf
  heimdall-flash-frontend 1.4.1-2 in focal ppc64el
  heimdall-flash-frontend 1.4.1-2 in focal s390x
Comment: Depends on obsolete and to-be-removed qt4-x11; removed from Debian testing; LP: #1757657
1 package successfully removed."
1757657,2018-03-22 08:01:49 UTC,"Assigning to Steve, there's a new upstream release in Debian that can be packaged which switches to Qt 5. He's the only maintainer listed."
1757657,2020-03-08 02:43:11 UTC,qt4-x11 is now removed from debian testing and unstable.
1757659,2020-03-05 08:43:37 UTC,"Current hydrogen in Ubuntu uses qt5, so we should not remove this despite it being removed from Debian."
1757664,2019-10-16 18:29:24 UTC,"Removing packages:
        imagevis3d 3.1.0-7build1 in eoan
                imagevis3d 3.1.0-7build1 in eoan amd64
                imagevis3d 3.1.0-7build1 in eoan arm64
                imagevis3d 3.1.0-7build1 in eoan i386
                imagevis3d 3.1.0-7build1 in eoan ppc64el
                imagevis3d 3.1.0-7build1 in eoan s390x
                imagevis3d-dbgsym 3.1.0-7build1 in eoan amd64
                imagevis3d-dbgsym 3.1.0-7build1 in eoan arm64
                imagevis3d-dbgsym 3.1.0-7build1 in eoan i386
                imagevis3d-dbgsym 3.1.0-7build1 in eoan ppc64el
                imagevis3d-dbgsym 3.1.0-7build1 in eoan s390x
Comment: (From Debian) RoQA; depends on qt4, dead upstream; Debian bug #941106
Remove [y|N]? y"
1757671,2019-10-16 18:13:49 UTC,"Removing packages:
        karlyriceditor 1.11-2.1build1 in eoan
                karlyriceditor 1.11-2.1build1 in eoan amd64
                karlyriceditor 1.11-2.1build1 in eoan arm64
                karlyriceditor 1.11-2.1build1 in eoan armhf
                karlyriceditor 1.11-2.1build1 in eoan i386
                karlyriceditor 1.11-2.1build1 in eoan ppc64el
                karlyriceditor 1.11-2.1build1 in eoan s390x
                karlyriceditor-dbgsym 1.11-2.1build1 in eoan amd64
                karlyriceditor-dbgsym 1.11-2.1build1 in eoan arm64
                karlyriceditor-dbgsym 1.11-2.1build1 in eoan armhf
                karlyriceditor-dbgsym 1.11-2.1build1 in eoan i386
                karlyriceditor-dbgsym 1.11-2.1build1 in eoan ppc64el
                karlyriceditor-dbgsym 1.11-2.1build1 in eoan s390x
Comment: (From Debian) RoQA; Depends on Qt4, unmaintained; Debian bug #940134
Remove [y|N]? y"
1757676,2019-11-23 10:22:58 UTC,Removed in Ubuntu
1757676,2020-05-07 07:22:04 UTC,I upgraded to 19.10 and found that kdbg is no longer there.
1757680,2019-03-04 22:16:06 UTC,"Removing packages from disco:
 kdepim4 4:4.14.10-7 in disco
  knode 4:4.14.10-7 in disco amd64
  knode 4:4.14.10-7 in disco arm64
  knode 4:4.14.10-7 in disco armhf
  knode 4:4.14.10-7 in disco i386
  knode 4:4.14.10-7 in disco ppc64el
  knode 4:4.14.10-7 in disco s390x
  ktimetracker 4:4.14.10-7 in disco amd64
  ktimetracker 4:4.14.10-7 in disco arm64
  ktimetracker 4:4.14.10-7 in disco armhf
  ktimetracker 4:4.14.10-7 in disco i386
  ktimetracker 4:4.14.10-7 in disco ppc64el
  ktimetracker 4:4.14.10-7 in disco s390x
  libcalendarsupport4 4:4.14.10-7 in disco amd64
  libcalendarsupport4 4:4.14.10-7 in disco arm64
  libcalendarsupport4 4:4.14.10-7 in disco armhf
  libcalendarsupport4 4:4.14.10-7 in disco i386
  libcalendarsupport4 4:4.14.10-7 in disco ppc64el
  libcalendarsupport4 4:4.14.10-7 in disco s390x
  libincidenceeditorsng4 4:4.14.10-7 in disco amd64
  libincidenceeditorsng4 4:4.14.10-7 in disco arm64
  libincidenceeditorsng4 4:4.14.10-7 in disco armhf
  libincidenceeditorsng4 4:4.14.10-7 in disco i386
  libincidenceeditorsng4 4:4.14.10-7 in disco ppc64el
  libincidenceeditorsng4 4:4.14.10-7 in disco s390x
  libkdepim4 4:4.14.10-7 in disco amd64
  libkdepim4 4:4.14.10-7 in disco arm64
  libkdepim4 4:4.14.10-7 in disco armhf
  libkdepim4 4:4.14.10-7 in disco i386
  libkdepim4 4:4.14.10-7 in disco ppc64el
  libkdepim4 4:4.14.10-7 in disco s390x
  libkdepimdbusinterfaces4 4:4.14.10-7 in disco amd64
  libkdepimdbusinterfaces4 4:4.14.10-7 in disco arm64
  libkdepimdbusinterfaces4 4:4.14.10-7 in disco armhf
  libkdepimdbusinterfaces4 4:4.14.10-7 in disco i386
  libkdepimdbusinterfaces4 4:4.14.10-7 in disco ppc64el
  libkdepimdbusinterfaces4 4:4.14.10-7 in disco s390x
  libkdgantt2-0 4:4.14.10-7 in disco amd64
  libkdgantt2-0 4:4.14.10-7 in disco arm64
  libkdgantt2-0 4:4.14.10-7 in disco armhf
  libkdgantt2-0 4:4.14.10-7 in disco i386
  libkdgantt2-0 4:4.14.10-7 in disco ppc64el
  libkdgantt2-0 4:4.14.10-7 in disco s390x
  libkleo4 4:4.14.10-7 in disco amd64
  libkleo4 4:4.14.10-7 in disco arm64
  libkleo4 4:4.14.10-7 in disco armhf
  libkleo4 4:4.14.10-7 in disco i386
  libkleo4 4:4.14.10-7 in disco ppc64el
  libkleo4 4:4.14.10-7 in disco s390x
  libkpgp4 4:4.14.10-7 in disco amd64
  libkpgp4 4:4.14.10-7 in disco arm64
  libkpgp4 4:4.14.10-7 in disco armhf
  libkpgp4 4:4.14.10-7 in disco i386
  libkpgp4 4:4.14.10-7 in disco ppc64el
  libkpgp4 4:4.14.10-7 in disco s390x
  libmessagecomposer4 4:4.14.10-7 in disco amd64
  libmessagecomposer4 4:4.14.10-7 in disco arm64
  libmessagecomposer4 4:4.14.10-7 in disco armhf
  libmessagecomposer4 4:4.14.10-7 in disco i386
  libmessagecomposer4 4:4.14.10-7 in disco ppc64el
  libmessagecomposer4 4:4.14.10-7 in disco s390x
  libmessagecore4 4:4.14.10-7 in disco amd64
  libmessagecore4 4:4.14.10-7 in disco arm64
  libmessagecore4 4:4.14.10-7 in disco armhf
  libmessagecore4 4:4.14.10-7 in disco i386
  libmessagecore4 4:4.14.10-7 in disco ppc64el
  libmessagecore4 4:4.14.10-7 in disco s390x
  libmessageviewer4 4:4.14.10-7 in disco amd64
  libmessageviewer4 4:4.14.10-7 in disco arm64
  libmessageviewer4 4:4.14.10-7 in disco armhf
  libme..."
1757684,2018-04-11 14:04:01 UTC,"The kdiff3 readme states ""Supported Qt-versions: 4.8, 5.2 or higher"", so perhaps only the packaging needs updated?"
1757684,2018-05-11 02:13:21 UTC,"I'll let Debian do this one, and I'll follow up once that's all sorted."
1757684,2019-07-19 06:45:37 UTC,1.8 in Eoan is now KF5/Qt5
1757686,2019-04-26 14:43:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757688,2018-06-04 22:54:58 UTC,"Hi Simon,"
1757688,2018-06-04 22:58:24 UTC,"Le jeudi 22 mars 2018 09:38:56 CEST, vous avez écrit :

> ** Bug watch added: Debian Bug tracker #874952
>    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874952
>
> ** Also affects: keurocalc (Debian) via
>    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874952
>    Importance: Unknown
>        Status: Unknown
"
1757688,2018-06-05 07:36:48 UTC,I have now committed to the KDE repositories:
1757695,2019-11-23 10:23:22 UTC,Removed in Ubuntu
1757695,2018-03-22 08:57:59 UTC,This might just need a new upstream release. I'll look into it.
1757700,2019-08-22 18:14:20 UTC,Fixed in 1.0.0-3
1757708,2019-11-09 15:42:14 UTC,Dead upstream since 2010: http://sourceforge.net/projects/kontrolpack/
1757708,2019-12-05 16:44:15 UTC,"Removing packages from focal:
 kontrolpack 3.0.0-0ubuntu4 in focal
  kontrolpack 3.0.0-0ubuntu4 in focal amd64
  kontrolpack 3.0.0-0ubuntu4 in focal arm64
  kontrolpack 3.0.0-0ubuntu4 in focal armhf
  kontrolpack 3.0.0-0ubuntu4 in focal i386
  kontrolpack 3.0.0-0ubuntu4 in focal ppc64el
  kontrolpack 3.0.0-0ubuntu4 in focal s390x
Comment: Qt4, unmaintained; LP: #1757708
1 package successfully removed."
1757709,2018-04-03 20:40:56 UTC,"Rik can follow through during the next Apps transition, unless I happen to be the one doing it..."
1757716,2019-09-04 17:57:00 UTC,"Removing packages from eoan:
 kqoauth 0.98-0ubuntu1 in eoan
  libkqoauth-dbg 0.98-0ubuntu1 in eoan amd64
  libkqoauth-dbg 0.98-0ubuntu1 in eoan arm64
  libkqoauth-dbg 0.98-0ubuntu1 in eoan armhf
  libkqoauth-dbg 0.98-0ubuntu1 in eoan i386
  libkqoauth-dbg 0.98-0ubuntu1 in eoan ppc64el
  libkqoauth-dbg 0.98-0ubuntu1 in eoan s390x
  libkqoauth-dev 0.98-0ubuntu1 in eoan amd64
  libkqoauth-dev 0.98-0ubuntu1 in eoan arm64
  libkqoauth-dev 0.98-0ubuntu1 in eoan armhf
  libkqoauth-dev 0.98-0ubuntu1 in eoan i386
  libkqoauth-dev 0.98-0ubuntu1 in eoan ppc64el
  libkqoauth-dev 0.98-0ubuntu1 in eoan s390x
  libkqoauth0 0.98-0ubuntu1 in eoan amd64
  libkqoauth0 0.98-0ubuntu1 in eoan arm64
  libkqoauth0 0.98-0ubuntu1 in eoan armhf
  libkqoauth0 0.98-0ubuntu1 in eoan i386
  libkqoauth0 0.98-0ubuntu1 in eoan ppc64el
  libkqoauth0 0.98-0ubuntu1 in eoan s390x
Comment: Ubuntu-specific, FTBFS, depends on Qt4 and blocks glibc; LP: #1757716, LP: #1842378
1 package successfully removed."
1757717,2019-10-20 03:23:55 UTC,This was removed from Eoan
1757722,2019-09-27 14:51:16 UTC,Removed from Eoan
1757735,2018-12-24 03:55:59 UTC,"Please remove this package from Ubuntu. It has just been removed from Debian (see the attached bug), it is in sync from Debian, and is based on the obsolete Qt 4."
1757741,2019-11-25 11:36:54 UTC,No reverse depends in Focal. Has never been in debian.
1757741,2019-12-05 16:46:36 UTC,"Removing packages from focal:
 libqtbamf 0.2.4-0ubuntu2 in focal
  libqtbamf-dev 0.2.4-0ubuntu2 in focal amd64
  libqtbamf-dev 0.2.4-0ubuntu2 in focal arm64
  libqtbamf-dev 0.2.4-0ubuntu2 in focal armhf
  libqtbamf-dev 0.2.4-0ubuntu2 in focal i386
  libqtbamf-dev 0.2.4-0ubuntu2 in focal ppc64el
  libqtbamf-dev 0.2.4-0ubuntu2 in focal s390x
  libqtbamf1 0.2.4-0ubuntu2 in focal amd64
  libqtbamf1 0.2.4-0ubuntu2 in focal arm64
  libqtbamf1 0.2.4-0ubuntu2 in focal armhf
  libqtbamf1 0.2.4-0ubuntu2 in focal i386
  libqtbamf1 0.2.4-0ubuntu2 in focal ppc64el
  libqtbamf1 0.2.4-0ubuntu2 in focal s390x
Comment: Qt4, unmaintained; LP: #1757741
1 package successfully removed."
1757744,2019-10-13 15:00:12 UTC,This seems to be fixed in libquazip 0.7.6-4.
1757751,2019-11-21 21:11:53 UTC,This bug was fixed in the package lmms - 1.2.1+dfsg1-2
1757755,2019-11-29 13:45:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757764,2019-07-28 00:21:20 UTC,New release in Debian unstable will eventually fix this.
1757764,2019-07-28 00:22:42 UTC,New version without qt4 released.
1757768,2020-01-20 10:56:04 UTC,The fixed version 1.9.0+dfsg-2 is in eoan & focal i.e. current stable release and development series.
1757769,2019-10-16 18:14:25 UTC,"Removing packages:
        ofono-phonesim 1.21-1 in eoan
                ofono-phonesim 1.21-1 in eoan amd64
                ofono-phonesim 1.21-1 in eoan arm64
                ofono-phonesim 1.21-1 in eoan armhf
                ofono-phonesim 1.21-1 in eoan i386
                ofono-phonesim 1.21-1 in eoan ppc64el
                ofono-phonesim 1.21-1 in eoan s390x
                ofono-phonesim-dbgsym 1.21-1 in eoan amd64
                ofono-phonesim-dbgsym 1.21-1 in eoan arm64
                ofono-phonesim-dbgsym 1.21-1 in eoan armhf
                ofono-phonesim-dbgsym 1.21-1 in eoan i386
                ofono-phonesim-dbgsym 1.21-1 in eoan ppc64el
                ofono-phonesim-dbgsym 1.21-1 in eoan s390x
Comment: (From Debian) RoQA; Depends on qt4, dead upstream; Debian bug #940141
Remove [y|N]? y"
1757777,2018-08-20 12:46:39 UTC,"Currently the package appears to be using Qt 5. However, paraview-dev still depends on qt4-dev-tools, which is probably just left over during the change from Qt 4."
1757782,2020-02-03 23:43:45 UTC,"According to debian bug version info, the current version in 20.04 should be fixed."
1757809,2019-11-09 15:19:05 UTC,Remove from debian: https://tracker.debian.org/news/896012/removed-111-1-from-unstable/
1757809,2019-12-05 16:54:41 UTC,"Removing packages:
 prison 1.1.1-1build2 in focal
  libprison-dbg 1.1.1-1build2 in focal amd64
  libprison-dbg 1.1.1-1build2 in focal arm64
  libprison-dbg 1.1.1-1build2 in focal armhf
  libprison-dbg 1.1.1-1build2 in focal i386
  libprison-dbg 1.1.1-1build2 in focal ppc64el
  libprison-dbg 1.1.1-1build2 in focal s390x
  libprison-dev 1.1.1-1build2 in focal amd64
  libprison-dev 1.1.1-1build2 in focal arm64
  libprison-dev 1.1.1-1build2 in focal armhf
  libprison-dev 1.1.1-1build2 in focal i386
  libprison-dev 1.1.1-1build2 in focal ppc64el
  libprison-dev 1.1.1-1build2 in focal s390x
  libprison0 1.1.1-1build2 in focal amd64
  libprison0 1.1.1-1build2 in focal arm64
  libprison0 1.1.1-1build2 in focal armhf
  libprison0 1.1.1-1build2 in focal i386
  libprison0 1.1.1-1build2 in focal ppc64el
  libprison0 1.1.1-1build2 in focal s390x
Comment: (From Debian) ROM; old source, no more used; Debian bug #885000
Remove [y|N]? y"
1757809,2018-11-10 23:50:21 UTC,The only thing that uses prison is kde4pimlibs (named kdepimlibs in Debian).
1757810,2020-07-30 01:32:20 UTC,projectm (2.1.0+dfsg-4ubuntu1) focal; urgency=medium
1757814,2019-10-27 11:42:40 UTC,"Please now remove from focal, as removed from debian testing and unstable."
1757815,2020-02-13 22:18:13 UTC,Please remove python-qt4 from focal archive. src and binaries.
1757815,2020-02-13 22:20:13 UTC,Please remove qt-assistant-compat from focal archive. src and binaries.
1757815,2020-02-13 22:34:39 UTC,"Removing packages:
 python-qt4 4.12.1+dfsg-3ubuntu3 in focal
  pyqt4-dev-tools 4.12.1+dfsg-3ubuntu3 in focal amd64
  pyqt4-dev-tools 4.12.1+dfsg-3ubuntu3 in focal arm64
  pyqt4-dev-tools 4.12.1+dfsg-3ubuntu3 in focal armhf
  pyqt4-dev-tools 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  pyqt4-dev-tools 4.12.1+dfsg-3ubuntu3 in focal s390x
  pyqt4-dev-tools-dbgsym 4.12.1+dfsg-3ubuntu3 in focal amd64
  pyqt4-dev-tools-dbgsym 4.12.1+dfsg-3ubuntu3 in focal arm64
  pyqt4-dev-tools-dbgsym 4.12.1+dfsg-3ubuntu3 in focal armhf
  pyqt4-dev-tools-dbgsym 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  pyqt4-dev-tools-dbgsym 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4-dbg 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4-dbg 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4-dbg 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4-dbg 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4-dbg 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4-dbus 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4-dbus 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4-dbus 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4-dbus 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4-dbus 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4-dbus-dbg 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4-dbus-dbg 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4-dbus-dbg 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4-dbus-dbg 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4-dbus-dbg 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4-dev 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4-dev 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4-dev 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4-dev 4.12.1+dfsg-3ubuntu3 in focal i386
  python-qt4-dev 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4-dev 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4-gl 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4-gl 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4-gl 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4-gl 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4-gl 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4-gl-dbg 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4-gl-dbg 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4-gl-dbg 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4-gl-dbg 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4-gl-dbg 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4-sql 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4-sql 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4-sql 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4-sql 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4-sql 4.12.1+dfsg-3ubuntu3 in focal s390x
  python-qt4-sql-dbg 4.12.1+dfsg-3ubuntu3 in focal amd64
  python-qt4-sql-dbg 4.12.1+dfsg-3ubuntu3 in focal arm64
  python-qt4-sql-dbg 4.12.1+dfsg-3ubuntu3 in focal armhf
  python-qt4-sql-dbg 4.12.1+dfsg-3ubuntu3 in focal ppc64el
  python-qt4-sql-dbg 4.12.1+dfsg-3ubuntu3 in focal s390x
  pytho..."
1757815,2020-02-13 22:34:59 UTC,"Removing packages:
 qt-assistant-compat 4.6.3-7build1 in focal
  libqtassistantclient-dev 4.6.3-7build1 in focal amd64
  libqtassistantclient-dev 4.6.3-7build1 in focal arm64
  libqtassistantclient-dev 4.6.3-7build1 in focal armhf
  libqtassistantclient-dev 4.6.3-7build1 in focal ppc64el
  libqtassistantclient-dev 4.6.3-7build1 in focal s390x
  libqtassistantclient4 4.6.3-7build1 in focal amd64
  libqtassistantclient4 4.6.3-7build1 in focal arm64
  libqtassistantclient4 4.6.3-7build1 in focal armhf
  libqtassistantclient4 4.6.3-7build1 in focal ppc64el
  libqtassistantclient4 4.6.3-7build1 in focal s390x
  libqtassistantclient4-dbgsym 4.6.3-7build1 in focal amd64
  libqtassistantclient4-dbgsym 4.6.3-7build1 in focal arm64
  libqtassistantclient4-dbgsym 4.6.3-7build1 in focal armhf
  libqtassistantclient4-dbgsym 4.6.3-7build1 in focal ppc64el
  libqtassistantclient4-dbgsym 4.6.3-7build1 in focal s390x
  qt-assistant-compat 4.6.3-7build1 in focal amd64
  qt-assistant-compat 4.6.3-7build1 in focal arm64
  qt-assistant-compat 4.6.3-7build1 in focal armhf
  qt-assistant-compat 4.6.3-7build1 in focal ppc64el
  qt-assistant-compat 4.6.3-7build1 in focal s390x
  qt-assistant-compat-dbgsym 4.6.3-7build1 in focal amd64
  qt-assistant-compat-dbgsym 4.6.3-7build1 in focal arm64
  qt-assistant-compat-dbgsym 4.6.3-7build1 in focal armhf
  qt-assistant-compat-dbgsym 4.6.3-7build1 in focal ppc64el
  qt-assistant-compat-dbgsym 4.6.3-7build1 in focal s390x
Comment: (From Debian) ROM; Dead upstream, Qt 4 removal; Debian bug #945194
Remove [y|N]? y"
1757816,2020-02-13 20:25:26 UTC,Please remove from focal. src and binaries
1757816,2020-02-13 22:37:30 UTC,"Removing packages from focal:
 qarecord 0.5.0-0ubuntu8 in focal
  qarecord 0.5.0-0ubuntu8 in focal amd64
  qarecord 0.5.0-0ubuntu8 in focal arm64
  qarecord 0.5.0-0ubuntu8 in focal armhf
  qarecord 0.5.0-0ubuntu8 in focal ppc64el
  qarecord 0.5.0-0ubuntu8 in focal s390x
Comment: Depends on obsolete Qt4, unmaintained, no new upstream for 10 years; LP: #1757816
1 package successfully removed."
1757818,2019-11-25 11:43:32 UTC,Last activity upstream was 11+ years ago: https://www.linux-apps.com/content/show.php?content=65066
1757818,2019-12-05 16:55:43 UTC,"Removing packages from focal:
 qchat 0.3-0ubuntu2 in focal
  qchat 0.3-0ubuntu2 in focal amd64
  qchat 0.3-0ubuntu2 in focal arm64
  qchat 0.3-0ubuntu2 in focal armhf
  qchat 0.3-0ubuntu2 in focal i386
  qchat 0.3-0ubuntu2 in focal ppc64el
  qchat 0.3-0ubuntu2 in focal s390x
Comment: Qt4, unmaintained; LP: #1757818
1 package successfully removed."
1757819,2019-12-05 16:57:43 UTC,"Removing packages from focal:
 qdevelop 0.28-0ubuntu1 in focal
  qdevelop 0.28-0ubuntu1 in focal amd64
  qdevelop 0.28-0ubuntu1 in focal arm64
  qdevelop 0.28-0ubuntu1 in focal armhf
  qdevelop 0.28-0ubuntu1 in focal i386
  qdevelop 0.28-0ubuntu1 in focal ppc64el
  qdevelop 0.28-0ubuntu1 in focal s390x
Comment: Qt4, unmaintained; LP: #1757819
1 package successfully removed."
1757819,2019-11-26 05:45:38 UTC,"Seems dead upstream. The site in debian control and watch file no longer seems to deal with the project, and left over code on other sites (Google code/Sourceforge/qdevelop.org) is no more recent than the 0.28 release from 2009."
1757823,2020-01-01 01:38:26 UTC,A version with QT5 is now in Focal.
1757825,2019-10-16 18:16:44 UTC,"Removing packages:
        qliss3d 1.4-5 in eoan
                qliss3d 1.4-5 in eoan amd64
                qliss3d 1.4-5 in eoan arm64
                qliss3d 1.4-5 in eoan armhf
                qliss3d 1.4-5 in eoan i386
                qliss3d 1.4-5 in eoan ppc64el
                qliss3d 1.4-5 in eoan s390x
                qliss3d-dbgsym 1.4-5 in eoan amd64
                qliss3d-dbgsym 1.4-5 in eoan arm64
                qliss3d-dbgsym 1.4-5 in eoan armhf
                qliss3d-dbgsym 1.4-5 in eoan i386
                qliss3d-dbgsym 1.4-5 in eoan ppc64el
                qliss3d-dbgsym 1.4-5 in eoan s390x
Comment: (From Debian) RoQA; Dead upstream, depends on Qt4; Debian bug #940202
Remove [y|N]? y"
1757828,2019-08-28 05:47:39 UTC,Fixed in 0.7.2-5.
1757835,2018-03-22 07:55:45 UTC,Copied from the Debian bug:
1757835,2018-03-23 02:06:32 UTC,Thank you!
1757836,2019-08-26 23:34:57 UTC,Fixed in 1.9-4
1757838,2018-03-23 02:16:15 UTC,"Apparently this has been ported to Qt 5 upstream. I'll take care of this one, and I'll probably get it in Debian."
1757838,2020-02-14 17:12:58 UTC,This bug was fixed in the package qtgain - 1.0.0-0ubuntu1
1757840,2019-10-26 06:32:43 UTC,This bug was fixed in the package qthid-fcd-controller - 4.1-5
1757841,2019-10-16 18:32:22 UTC,"Removing packages:
        qtiplot 0.9.8.9-18 in eoan
                qtiplot 0.9.8.9-18 in eoan amd64
                qtiplot 0.9.8.9-18 in eoan arm64
                qtiplot 0.9.8.9-18 in eoan i386
                qtiplot 0.9.8.9-18 in eoan ppc64el
                qtiplot 0.9.8.9-18 in eoan s390x
                qtiplot-dbgsym 0.9.8.9-18 in eoan amd64
                qtiplot-dbgsym 0.9.8.9-18 in eoan arm64
                qtiplot-dbgsym 0.9.8.9-18 in eoan i386
                qtiplot-dbgsym 0.9.8.9-18 in eoan ppc64el
                qtiplot-dbgsym 0.9.8.9-18 in eoan s390x
                qtiplot-doc 0.9.8.9-18 in eoan amd64
                qtiplot-doc 0.9.8.9-18 in eoan arm64
                qtiplot-doc 0.9.8.9-18 in eoan armhf
                qtiplot-doc 0.9.8.9-18 in eoan i386
                qtiplot-doc 0.9.8.9-18 in eoan ppc64el
                qtiplot-doc 0.9.8.9-18 in eoan s390x
Comment: (From Debian) RoQA; Depends on Qt4, upstream went closed-source; Debian bug #941285
Remove [y|N]? y"
1757848,2018-03-23 02:38:15 UTC,"Hum, this might be a false positive. I'll investigate further."
1757848,2019-08-23 12:56:42 UTC,I have just filed an RM bug for it: bug 1841178.
1757851,2020-02-04 01:47:15 UTC,"Removing packages from focal:
 qwt5 5.2.3-1 in focal
  libqwt5-doc 5.2.3-1 in focal amd64
  libqwt5-doc 5.2.3-1 in focal arm64
  libqwt5-doc 5.2.3-1 in focal armhf
  libqwt5-doc 5.2.3-1 in focal i386
  libqwt5-doc 5.2.3-1 in focal ppc64el
  libqwt5-doc 5.2.3-1 in focal s390x
  libqwt5-qt4 5.2.3-1 in focal amd64
  libqwt5-qt4 5.2.3-1 in focal arm64
  libqwt5-qt4 5.2.3-1 in focal armhf
  libqwt5-qt4 5.2.3-1 in focal ppc64el
  libqwt5-qt4 5.2.3-1 in focal s390x
  libqwt5-qt4-dev 5.2.3-1 in focal amd64
  libqwt5-qt4-dev 5.2.3-1 in focal arm64
  libqwt5-qt4-dev 5.2.3-1 in focal armhf
  libqwt5-qt4-dev 5.2.3-1 in focal ppc64el
  libqwt5-qt4-dev 5.2.3-1 in focal s390x
Comment: Depends on obsolete Qt4, removed from Debian testing; Debian bug #875166, LP: #1757851
1 package successfully removed."
1757851,2020-01-21 20:10:19 UTC,"This has now been removed from debian testing, and will be removed from unstable in February."
1757859,2018-03-22 08:17:09 UTC,"The GUI parts of rsplib have been ported to Qt 5.x a long time ago, since version 3.1. Updated rsplib packages can be found in my PPA: https://launchpad.net/~dreibh/+archive/ubuntu/ppa/+packages?field.name_filter=rsplib&field.status_filter=published&field.series_filter= . They just need an uploader."
1757859,2018-03-23 02:51:38 UTC,"Awesome, many thanks!"
1757859,2019-12-05 06:05:43 UTC,This bug was fixed in the package rsplib - 3.2.4-0ubuntu1
1757860,2019-10-16 18:30:03 UTC,"Removing packages:
        scantailor 0.9.12.2-3 in eoan
                scantailor 0.9.12.2-3 in eoan amd64
                scantailor 0.9.12.2-3 in eoan arm64
                scantailor 0.9.12.2-3 in eoan armhf
                scantailor 0.9.12.2-3 in eoan i386
                scantailor 0.9.12.2-3 in eoan ppc64el
                scantailor 0.9.12.2-3 in eoan s390x
                scantailor-dbgsym 0.9.12.2-3 in eoan amd64
                scantailor-dbgsym 0.9.12.2-3 in eoan arm64
                scantailor-dbgsym 0.9.12.2-3 in eoan armhf
                scantailor-dbgsym 0.9.12.2-3 in eoan i386
                scantailor-dbgsym 0.9.12.2-3 in eoan ppc64el
                scantailor-dbgsym 0.9.12.2-3 in eoan s390x
Comment: (From Debian) RoQA; Depends on Qt4, dead upstream; Debian bug #941151
Remove [y|N]? y"
1757861,2020-01-21 20:04:30 UTC,"This has now been removed fron debian testing, and will be removed from  unstable in February."
1757861,2020-02-04 01:49:16 UTC,"Removing packages from focal:
 scap-workbench 1.1.5-1 in focal
  scap-workbench 1.1.5-1 in focal amd64
  scap-workbench 1.1.5-1 in focal arm64
  scap-workbench 1.1.5-1 in focal armhf
  scap-workbench 1.1.5-1 in focal ppc64el
  scap-workbench 1.1.5-1 in focal s390x
Comment: Depends on obsolete Qt4, removed from Debian testing; Debian bug #875177, LP: #1757861
1 package successfully removed."
1757865,2020-01-21 20:07:41 UTC,"This has now been removed from debian testing, and will be removed from unstable in February."
1757865,2020-01-21 20:25:29 UTC,please not.
1757865,2020-01-21 20:26:00 UTC,"and also, I'll have scribus-ng removed (again)."
1757865,2020-01-21 20:39:03 UTC,"This conversation directly affects the default installation of Ubuntu Studio, so, as the flavor lead, I'm wondering a couple of things:"
1757865,2020-01-21 20:52:33 UTC,Yes to both
1757865,2020-01-25 19:02:03 UTC,This bug was fixed in the package scribus - 1.5.5+dfsg-4
1757866,2018-03-23 02:56:41 UTC,"Hum, might be a false positive. It should be uploaded to Debian anyway though."
1757874,2020-02-04 01:46:34 UTC,"Removing packages from focal:
 sofa-framework 1.0~beta4-12build1 in focal
  libsofa1 1.0~beta4-12build1 in focal amd64
  libsofa1 1.0~beta4-12build1 in focal arm64
  libsofa1 1.0~beta4-12build1 in focal ppc64el
  libsofa1 1.0~beta4-12build1 in focal s390x
  libsofa1-dev 1.0~beta4-12build1 in focal amd64
  libsofa1-dev 1.0~beta4-12build1 in focal arm64
  libsofa1-dev 1.0~beta4-12build1 in focal ppc64el
  libsofa1-dev 1.0~beta4-12build1 in focal s390x
  sofa-apps 1.0~beta4-12build1 in focal amd64
  sofa-apps 1.0~beta4-12build1 in focal arm64
  sofa-apps 1.0~beta4-12build1 in focal ppc64el
  sofa-apps 1.0~beta4-12build1 in focal s390x
  sofa-data 1.0~beta4-12build1 in focal amd64
  sofa-data 1.0~beta4-12build1 in focal arm64
  sofa-data 1.0~beta4-12build1 in focal armhf
  sofa-data 1.0~beta4-12build1 in focal i386
  sofa-data 1.0~beta4-12build1 in focal ppc64el
  sofa-data 1.0~beta4-12build1 in focal s390x
  sofa-tutorials 1.0~beta4-12build1 in focal amd64
  sofa-tutorials 1.0~beta4-12build1 in focal arm64
  sofa-tutorials 1.0~beta4-12build1 in focal armhf
  sofa-tutorials 1.0~beta4-12build1 in focal i386
  sofa-tutorials 1.0~beta4-12build1 in focal ppc64el
  sofa-tutorials 1.0~beta4-12build1 in focal s390x
Comment: Depends on obsolete Qt4, removed from Debian testing; Debian bug #875184, LP: #1757874
1 package successfully removed."
1757874,2020-01-21 20:06:09 UTC,"This has now been removed from debian testing, and will be removed from unstable in February."
1757885,2018-03-22 02:44:58 UTC,Synergy already builds on qt5. Relevant patches for Debian upstream are at https://github.com/epakai/synergy-debian/commit/e2b31c6e91b4b52f19884ffbf060cfe5b8904d92
1757885,2018-03-23 03:14:41 UTC,"Awesome! Please update the Debian bug when it's done, and I'll update this bug when it hits Ubuntu."
1757885,2019-01-14 16:46:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757885,2019-01-14 16:55:19 UTC,"@joshua-honeycutt :
Please update synergy packages to latest upstream version - v1.10.1 and update debian packaging to v1.10.1 (I see QT5 port is already done: https://github.com/epakai/synergy-debian/blob/debian/sid/debian/changelog )"
1757885,2020-10-22 19:59:55 UTC,the package is removed now
1757888,2019-08-19 11:16:45 UTC,This bug was fixed in the package telepathy-qt - 0.9.7-5fakesync1
1757892,2018-03-23 03:34:33 UTC,Upstream seems semi-active; I'll check it out.
1757903,2020-07-23 06:29:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757906,2019-01-28 14:19:59 UTC,"VMPK's author has clarified that it's been ported to QT5 a long time ago:
https://sourceforge.net/p/vmpk/bugs/54/"
1757906,2019-11-18 18:07:34 UTC,"vmpk v0.7.2-1 is now in focal, so this is fixed for the next release (20.04)."
1757907,2019-10-16 18:36:30 UTC,"Removing packages:
        voxbo 1.8.5~svn1246-3build1 in eoan
                voxbo 1.8.5~svn1246-3build1 in eoan amd64
                voxbo 1.8.5~svn1246-3build1 in eoan arm64
                voxbo 1.8.5~svn1246-3build1 in eoan armhf
                voxbo 1.8.5~svn1246-3build1 in eoan i386
                voxbo 1.8.5~svn1246-3build1 in eoan ppc64el
                voxbo 1.8.5~svn1246-3build1 in eoan s390x
                voxbo-dbgsym 1.8.5~svn1246-3build1 in eoan amd64
                voxbo-dbgsym 1.8.5~svn1246-3build1 in eoan arm64
                voxbo-dbgsym 1.8.5~svn1246-3build1 in eoan armhf
                voxbo-dbgsym 1.8.5~svn1246-3build1 in eoan i386
                voxbo-dbgsym 1.8.5~svn1246-3build1 in eoan ppc64el
                voxbo-dbgsym 1.8.5~svn1246-3build1 in eoan s390x
Comment: (From Debian) RoQA; Depends on qt4, dead upstream; Debian bug #941529
Remove [y|N]? y"
1757913,2020-03-11 20:32:04 UTC,This bug is fixed in Debian by porting program to Qt5.
1757913,2020-02-04 05:58:19 UTC,"Removing packages from focal:
 yagf 0.9.3.2-1ubuntu2 in focal
  yagf 0.9.3.2-1ubuntu2 in focal amd64
  yagf 0.9.3.2-1ubuntu2 in focal arm64
  yagf 0.9.3.2-1ubuntu2 in focal armhf
  yagf 0.9.3.2-1ubuntu2 in focal ppc64el
  yagf 0.9.3.2-1ubuntu2 in focal s390x
Comment: Depends on obsolete Qt4, removed from Debian testing; Debian bug #875243, LP: #1757913
1 package successfully removed."
1757913,2019-03-21 15:03:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757913,2019-02-14 02:41:59 UTC,It was ported on qt5 by Mageia: http://svnweb.mageia.org/packages/cauldron/yagf/current/
1757913,2020-01-21 20:00:35 UTC,This has now been removed from debian testing. Please now remove from focal.
1757920,2018-03-22 03:00:45 UTC,"1) we need add info in pre-requirement section of doc
2) we need update API to indicate that info
3) add a section in appendix about it as troubleshooting"
1757920,2018-11-23 06:00:29 UTC,this already done?
1757920,2018-03-22 02:42:14 UTC,"Should update API doc, add this as prerequirements before calling host_get_info"
1757925,2018-03-22 05:11:21 UTC,"this image is already there now, please check https://hub.docker.com/r/kolla/centos-source-kuryr-libnetwork/tags/"
1757925,2018-03-22 06:22:26 UTC,Thanks.
1757925,2018-03-22 06:37:58 UTC,"I am very sorry because I don't describe the problem clear. The ""centos-binary-kuryr-libnetwork"" image does not exit."
1757931,2018-03-22 06:19:59 UTC,"I'd suggest to check out how Octavia+Neutron work and the respective policy.json configurations are, because if I understand your use case correctly, it should be quite similar to it. That's what rule:context_is_advsvc was built for. I can do some digging as there might be something missing in your policy.json."
1757931,2018-03-22 14:28:40 UTC,I'll have to play around with context_is_advsvc ... it seems pretty close to what i want. The only thing that would have to be different is that I don't want to give out those port-management permissions.
1757931,2018-03-23 05:28:25 UTC,"OK great, thanks!"
1757950,2018-03-23 04:39:40 UTC,"Hi,
Can you please try to reproduce the issue and capture the logs when it works and when it does not work?
Thanks."
1757950,2018-03-22 07:02:37 UTC,"You're right. I meet this issue several times. I checked that, Heat was called but sometime nothing happens."
1757957,2018-07-24 03:00:57 UTC,This issue was fixed in the openstack/kolla-ansible 6.1.0 release.
1757957,2018-03-22 08:22:49 UTC,https://bugs.launchpad.net/kolla-ansible/+bug/1755505
1757957,2018-06-07 20:55:14 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b2 development milestone.
1757962,2018-03-27 07:48:06 UTC,you need to look at if ping is still working
1757962,2018-03-27 09:07:34 UTC,"Ping was not working, status of instance was shutoff."
1757983,2018-03-22 10:33:40 UTC,"We've migrated to github, the issue you're reporting is here https://github.com/elementary/pantheon-agent-polkit/issues/20"
1757990,2018-03-28 20:34:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1757994,2018-04-24 07:17:28 UTC,"In aodh alarm update command, the following cases are missing in aodhclient code :"
1757994,2018-07-05 05:00:40 UTC,Patch link : https://review.openstack.org/#/c/564098/
1757994,2019-08-19 14:59:33 UTC,This issue was fixed in the openstack/python-aodhclient 1.3.0 release.
1758003,2018-04-19 07:59:38 UTC,I'm not sure to be honest...
1758003,2018-04-19 07:39:17 UTC,thanks Adam. I didn't noticed you had 2 branchs! Sorry!
1758003,2018-03-23 01:00:02 UTC,"Thanks Andre,"
1758006,2018-03-22 16:59:45 UTC,The error in your log is:
1758006,2018-04-26 21:29:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758009,2018-03-27 08:22:43 UTC,"Hi all,
I have this problem too but in
.config/compiz-1/compizconfig/config
i have"
1758009,2018-03-26 09:42:22 UTC,"At first solution 5 did not work for me. A prerequisite I guess is that you have to remove lowgfx.conf file before, not just comment it out. Otherwise any change in .config/compiz-1/compizconfig/config will be overwritten back to profile = unity-lowgfx."
1758009,2018-03-26 07:17:28 UTC,Post #5 worked for me too.
1758009,2018-03-26 04:34:39 UTC,I can also confirm the workaround in post #5 worked for me. Same symptoms with segfault in libcompizconfig.
1758009,2018-03-25 14:54:10 UTC,"@robprije: your suggested workaround in your post #5 above has fixed the problem for me. Thank you! I had the same symptoms on my workstation, and here is the relevant error message from syslog:"
1758009,2018-03-25 12:21:32 UTC,"@mak, strange, I asked because I do wonder whether it's the same bug."
1758009,2018-03-23 14:17:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758009,2018-03-24 16:18:56 UTC,@mak. You mean low -graphics mode is not working for you?
1758009,2018-03-24 15:42:42 UTC,"hi all,
I've the same problem, guest-user is okay, but my profile has the problem.
I
* moved my .config to backup
* upgraded everything (Upgrade: unity-control-center-faces:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), unity-control-center:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), libunity-control-center1:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1))
* tested with unity --reset-icons
* test with lowgfx /.config/upstart/lowgfx.conf
* .config/compiz-1/compizconfig/config: profile = unity
* unity-tweak-tool
* ppa: paulo-miguel-dias / pkppa"
1758009,2018-03-24 15:31:31 UTC,"Guest session is also working here in default graphics mode, so it's probably a regression that just occurs with a certain Compiz settings or plugin."
1758009,2018-03-24 08:32:16 UTC,I resolved the problem for myself.
1758009,2018-03-24 04:48:58 UTC,I think I'm getting the same error
1758009,2018-03-22 10:11:53 UTC,"FYI
Apparently more people are affected, a high amount of visitors since March 2018 on this Askubuntu page, describing the same symptoms due to a bug January 2018. #1735594"
1758009,2018-03-24 17:32:24 UTC,"@janghou: yes, i mean low-graphics. and yes: after every step i rebooted the system ;)"
1758009,2018-03-27 10:59:16 UTC,The (mutually exclusive) solutions lowgfx.conf startup and profile = unity in compizconfig/config did not work for me.
1758009,2018-03-27 11:38:16 UTC,"@Marco, #5 did not work for me at first, but it did the later (?!?)."
1758009,2018-03-29 16:02:55 UTC,"@Janghou: thank you, cleaning the cache helps!"
1758009,2018-03-30 12:01:33 UTC,Only doing `mv ~/.config ~/.config-BACK` fixed the issue for me.
1758009,2018-03-30 20:26:43 UTC,"h,
steps/workarounds listed on: https://askubuntu.com/questions/992571/gui-unity-crashing-in-16-04-lts-after-updates-2018-01-04-compiz-segfaults"
1758009,2018-04-10 01:19:19 UTC,Post #20 worked for me.  Thanks Ruslan.  Had to move important config files back into .config later.  Nothing else I tried worked after searching forums for hours and trying their suggestions.
1758009,2018-07-23 17:55:29 UTC,"I also tried several of the solutions proposed here and in askubuntu, but only # 20 worked for me.
Indeed, it is not necessary to delete the entire .config directory. Just move the compiz subdirectory: '$ mv ~/.config/compiz-1 backup/'"
1758009,2018-07-27 14:07:44 UTC,"Had the same issue (after an apt-get dist-upgrade after at least a month since the last time I upgraded). Comment #5 solved the issue for me. Surprisingly, I didn't even need to restart."
1758009,2018-09-27 04:51:13 UTC,"Had this issue, fixed by updating .config/compiz-1/compizconfig as in comment #5."
1758009,2018-11-13 14:58:28 UTC,"I think I found the root cause for the compiz-config-profile-setter segfault. The call ""ccsFreeContext(context);"" in line 218 in compiz_config_profile_setter.c frees the context object while background event processing still uses the object, which then leads to the segfault."
1758009,2018-11-13 16:21:18 UTC,"The attachment ""compiz-config-profile-setter_segfault.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1758009,2018-03-29 14:48:50 UTC,"Yep,"
1758013,2018-03-22 14:53:20 UTC,TRY 5:
1758016,2021-02-22 16:00:39 UTC,Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1758016,2018-03-22 11:36:03 UTC,"(overcloud) [stack@undercloud ~]$ cat overcloud_create_ssl_cert.log
2018-03-21 14:25:05 | + openssl genrsa 2048
2018-03-21 14:25:05 | + openssl req -new -x509 -key /home/stack/overcloud-ca-privkey.pem -out /home/stack/overcloud-cacert.pem -days 365 -subj '/C=US/ST=NC/L=Raleigh/O=Red Hat/OU=OOOQ/CN=overcloud'
2018-03-21 14:25:05 | + sudo cp /home/stack/overcloud-cacert.pem /etc/pki/ca-trust/source/anchors/
2018-03-21 14:25:05 | + sudo update-ca-trust extract
2018-03-21 14:25:06 | + openssl req -newkey rsa:2048 -days 365 -nodes -keyout /home/stack/server-key.pem -out /home/stack/server-req.pem -subj '/C=US/ST=NC/L=Raleigh/O=Red Hat/OU=OOOQ/CN=10.0.0.5' -reqexts subjectAltName -config /dev/fd/63
2018-03-21 14:25:06 | ++ printf '[subjectAltName]\nsubjectAltName=IP:10.0.0.5\n[req]req_extensions = v3_req\ndistinguished_name=req_distinguished_name\n[req_distinguished_name]'
2018-03-21 14:25:06 | Generating a 2048 bit RSA private key
2018-03-21 14:25:06 | ...........+++
2018-03-21 14:25:06 | ..............+++
2018-03-21 14:25:06 | writing new private key to '/home/stack/server-key.pem'
2018-03-21 14:25:06 | -----
2018-03-21 14:25:06 | + openssl rsa -in /home/stack/server-key.pem -out /home/stack/server-key.pem
2018-03-21 14:25:06 | writing RSA key
2018-03-21 14:25:06 | + openssl x509 -req -in server-req.pem -days 365 -CA /home/stack/overcloud-cacert.pem -CAkey /home/stack/overcloud-ca-privkey.pem -set_serial 01 -out /home/stack/server-cert.pem -extensions subjectAltName -extfile /dev/fd/63
2018-03-21 14:25:06 | ++ printf '[subjectAltName]\nsubjectAltName=IP:10.0.0.5\n[req]req_extensions = v3_req\ndistinguished_name=req_distinguished_name\n[req_distinguished_name]'
2018-03-21 14:25:06 | Signature ok
2018-03-21 14:25:06 | subject=/C=US/ST=NC/L=Raleigh/O=Red Hat/OU=OOOQ/CN=10.0.0.5
2018-03-21 14:25:06 | Getting CA Private Key"
1758016,2018-06-14 08:09:21 UTC,A workaround so far that Ajo pointed out:
1758017,2018-03-26 09:18:14 UTC,apport information
1758017,2018-03-26 09:18:38 UTC,apport information
1758017,2018-03-26 09:18:37 UTC,apport information
1758017,2018-03-26 09:18:34 UTC,apport information
1758017,2018-03-26 09:18:29 UTC,apport information
1758017,2018-03-26 09:18:22 UTC,apport information
1758017,2018-03-26 09:18:20 UTC,apport information
1758017,2018-03-26 09:18:19 UTC,apport information
1758017,2018-03-26 09:18:17 UTC,apport information
1758017,2018-03-26 09:18:16 UTC,apport information
1758017,2018-03-26 09:18:15 UTC,apport information
1758017,2018-03-26 09:18:13 UTC,apport information
1758017,2018-03-26 09:18:24 UTC,apport information
1758017,2018-03-26 09:18:11 UTC,apport information
1758017,2018-03-26 09:17:58 UTC,apport information
1758017,2018-03-26 09:17:59 UTC,apport information
1758017,2018-03-26 09:18:12 UTC,apport information
1758017,2018-03-26 09:18:03 UTC,apport information
1758017,2018-03-26 08:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1758017,2018-03-26 09:18:02 UTC,apport information
1758017,2018-03-26 09:18:05 UTC,apport information
1758017,2018-03-26 09:18:07 UTC,apport information
1758017,2018-03-26 09:18:08 UTC,apport information
1758017,2018-03-26 09:18:09 UTC,apport information
1758017,2018-03-26 09:18:10 UTC,apport information
1758017,2018-03-26 09:18:04 UTC,apport information
1758019,2020-04-23 19:54:42 UTC,The new installer is now out.
1758019,2020-03-23 08:11:08 UTC,"------- Comment From <email address hidden> 2020-03-23 04:03 EDT-------
IBM Bugzilla status-> closed, Will not be fixed by Canonical"
1758019,2020-03-21 17:01:42 UTC,"The focus regarding installer moved to subiquity with 20.04.
And since clock and TZ are discovered and/or set automatically this ticket is at least Invalid for the subiquity version that is currently in development for 20.04.
Hence setting this ticket to Invalid."
1758019,2020-03-04 15:40:06 UTC,"Well, not exactly - it first of all means that manual clock and TZ configuration is in the current version of subiquity not addressed by any UI screen. And this will probably not change with the subiquity version that is shipped with 20.04 GA.
In case there are good reasons to have this, a ticket can be opened, this feature requested and the development team will triage and decide...
Please notice that this is the same on all architectures."
1758019,2020-03-04 15:20:15 UTC,"------- Comment From <email address hidden> 2020-03-04 10:16 EDT-------
@Canonical: Does that mean this request will ""WILL NOT BE IMPLEMENTED""
Please provide your input for finalization of the LP......"
1758019,2020-02-11 10:10:49 UTC,"------- Comment From <email address hidden> 2020-02-11 05:00 EDT-------
@CAN. Will that be fixed with the new subiquity installer?"
1758019,2020-02-17 01:16:15 UTC,subiquity does not currently let you set the timezone at all.
1758019,2019-05-23 08:56:44 UTC,"Yes, probably.
I am going to leave this ticket open until there is a version of the new installer that can be used to verify this."
1758019,2019-05-23 07:29:34 UTC,"------- Comment From <email address hidden> 2019-05-23 03:27 EDT-------
@Canonical. will that be fixed with the new Installer with 19.10 ? Than I will change the target release to 19.10 ???"
1758019,2018-08-31 12:49:37 UTC,"------- Comment From <email address hidden> 2018-08-31 08:48 EDT-------
Set to Prio=low..    circumventiona awailable..."
1758019,2018-03-29 11:33:10 UTC,"It's probably similar like you want to try.
In this case geoip response with UK/London (because that's were the intranet/internet passage is), but the system itself is in Germany, hence Europe/Berlin is selected."
1758019,2018-03-26 10:09:43 UTC,This appears to come from integration of tzsetup & clock-setup.
1758019,2018-03-22 10:40:25 UTC,Default Comment by Bridge
1758019,2019-06-03 16:45:17 UTC,Setting to 'In Progress' with the work on subiquity.
1758023,2018-08-17 11:58:42 UTC,"Support for libinput was added long ago [1]. However, the xfce4-settings package build does not depend on xserver-xorg-input-libinput-dev, and therefore support for libinput is missing. This was changed in version 4.13.x (Xubuntu 18.10)."
1758023,2018-08-17 13:15:34 UTC,"> Support for libinput was added long ago [1]. However, the xfce4-settings
> package build does not depend on xserver-xorg-input-libinput-dev, and
> therefore support for libinput is missing. This was changed in
> version 4.13.x (Xubuntu 18.10).
"
1758023,2018-08-17 13:16:42 UTC,"> How could anybody use a Xubuntu installation with a working mouse (driver) ?
"
1758023,2018-08-22 17:35:35 UTC,"I have just upgraded my first machine to 18.04 on a ThinkPad W500. The TrackPoint needs speed adjusting, but much to my dismay, I am faced with this problem. I strongly agree with Ulrich, I do not expect the existence of such a bug, nor can I accept it."
1758023,2018-08-22 17:37:38 UTC,"Should read: ""do not expect such a bug in a supposedly stable LTS release"""
1758023,2018-08-22 19:32:59 UTC,I can also confirm that at least the workaround by Lagoda in #10 seems to work for me so far.
1758023,2019-04-16 06:14:55 UTC,It's still an issue on Ubuntu 18.04.2 LTS with xserver-xorg-input-libinput version 0.27.1-1.
1758023,2018-12-24 21:43:18 UTC,"In the end I upgraded to Xubuntu 18.10, and I've now got things how I want. However, the GUI still doesn't work properly: it has acceleration, which works, but no sensitivity. In that sense the upgrade was a waste of time."
1758023,2018-08-14 20:58:09 UTC,"FWIW, I'm experiencing the same problem on a Thinkpad X260 with Xubuntu 18.04.  The trackpoint is pretty much unusable without proper speed and acceleration settings."
1758023,2019-04-19 09:48:25 UTC,"I'm also having this issue on""Ubuntu 18.04.2 LTS"" with Xubuntu, going with #10's workaround"
1758023,2019-05-06 12:45:22 UTC,"FWIW the workaround in #10 also worked for me for disabling scroll-wheel-emulation under 18.04, which didn't seem to respond to changes in the appropriate xinput setting."
1758023,2019-11-16 11:03:03 UTC,New Logitech keyboard and mouse onto existing system: Ubuntu 18.04.3 LTS.
1758023,2019-12-11 00:53:20 UTC,I tried it with Debian 10.2 stable Xfce and it worked.
1758023,2018-11-28 19:50:51 UTC,"I'm in the same position as others after upgrading from 16.04 to 18.04.1. The GUI settings do nothing. I can change the acceleration using xinput, but I can't change the sensitivity, making my trackball (Logitech Marble Mouse) pretty useless. I suffer from RSI and this is a serious regression for me. I hope the fix is backported soon, otherwise I'll have to find another distro."
1758023,2018-08-12 05:39:45 UTC,I tried the newer Xubuntu 18.10 Cosmic Cuttlefish [[development branch!]] and the settings work there as aspected.
1758023,2018-04-12 10:46:31 UTC,"I'm not able to reproduce the mouse acceleration issue. If I set it low, sweeping my mouse barely moves across the screen. Setting it high, sweeping goes edge to edge."
1758023,2018-07-13 13:58:55 UTC,"I have now tried using xset to change my pointer acceleration and sensitivity, via 'xset m ACCELLERATION THRESHOLD', both with libinput installed and uninstalled, to no avail. I have also verified that my settings are being recorded via 'xset q | grep -A 1 Pointer', and also verified that changing the respective settings in the settings applet do not affect these settings, both also with libinput installed and uninstalled."
1758023,2018-07-13 13:42:25 UTC,"Additionally, I was able to confirm that changing the double-click time in the settings applet did have an affect."
1758023,2018-07-13 13:16:57 UTC,"I have had this same problem since upgrading to 18.04, and it has been infuriating, as the defaults greatly impact my ability to perform my work. I'm going to have to switch distros (planning for Solus) if this does not get fixed. Additionally, Lagoda's solution (in #10) did not work at all for me."
1758023,2018-07-10 03:02:12 UTC,"Also, Lagoda's solution (in #10) worked for me."
1758023,2018-07-10 00:38:01 UTC,"Same problem here.
I'm using different mouses, none of them is affected by the acceleration and sensibility slides.
I can't disable acceleration."
1758023,2018-04-12 18:05:53 UTC,sudo apt remove xserver-xorg-input-libinput && sudo apt install xserver-xorg-input-evdev
1758023,2018-04-12 16:33:11 UTC,And the xinput details of my mouse
1758023,2018-04-12 16:17:31 UTC,"Same problem.
Change acceleration in mouse settings have no effects.
My keyboard and mouse appears in double (see image)."
1758023,2018-04-12 12:53:04 UTC,Thank you Sean for your explanation and for looking after Xubuntu 18.04 bugs here on Launchpad.
1758023,2018-04-12 10:24:41 UTC,How do we make this bug aware to the Xubuntu team? Did I use the wrong tags in the bug report?
1758023,2018-04-10 01:03:43 UTC,"An update.  To set the mouse speed, I used..."
1758023,2018-04-09 18:29:48 UTC,"I'm using openbox, Ubuntu 18.04"
1758023,2018-03-22 16:14:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758023,2018-03-22 11:12:21 UTC,Maybe related to the following bug report for Xubuntu 17.10 from November 2017 ?
1758023,2018-08-11 23:22:30 UTC,FWIW this seems to be the same as issue:-
1758030,2018-03-22 11:22:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555257"
1758032,2018-03-22 12:09:37 UTC," Following the suggestion of
 https://stackoverflow.com/questions/45821085/awshttpsconnection-object-has-no-attribute-ssl-context"
1758037,2018-05-09 17:36:37 UTC,This bug was fixed in the package libvirt - 4.0.0-1ubuntu10
1758037,2018-05-09 08:43:55 UTC,Started tests for a Cosmic upload and added SRU Template.
1758037,2018-04-30 04:36:18 UTC,"Ok, together we found a fix for this which now is integrated upstream."
1758037,2018-04-27 22:00:11 UTC,(forgot to switch the component to libvirt)
1758037,2018-04-27 21:58:13 UTC,"After discussion on-list, we decided that although we may need to increase the buffer size again sometime in the future, due to memory usage concerns it is still best to just set the buffer size to 256k, and include a lot of verbiage explaining the choice (and pointing out the probable source of failure if it happens again) in the code and in the git log. (See the follow-up comments to the V12 patch listed above)."
1758037,2018-04-26 07:08:09 UTC,FYI Discussion of propsoed fix in https://www.redhat.com/archives/libvir-list/2018-April/msg02459.html
1758037,2018-04-25 08:06:30 UTC,"Hi,
I wanted to let you know that this problem is not only affecting Fedora.
I happened to debug [1] leading the same conclusions on the fd being -1 breaking the latter setsockopt."
1758037,2018-04-25 21:30:10 UTC,"I just tried setting the buffer size to 256k instead of 128k, and everything works. I posted a patch:"
1758037,2018-04-25 15:29:17 UTC,Looking at source the default size if you don't call pcap_set_buffer_size is *massively* larger than the PCAP_BUFFERSIZE constant libvirt has defined:
1758037,2018-04-25 10:04:55 UTC,"Added this summary to the BZ:
I realized that the path without:
  <parameter name='CTRL_IP_LEARNING' value='dhcp'/>
works but is totally different.
It uses pcap_open_live"
1758037,2018-04-25 10:04:35 UTC,"I realized that the path without:
  <parameter name='CTRL_IP_LEARNING' value='dhcp'/>
works but is totally different.
It uses pcap_open_live"
1758037,2018-04-25 09:21:41 UTC,"Debugging pcap_activate and pcap_create with and without
  <parameter name='CTRL_IP_LEARNING' value='dhcp'/>"
1758037,2018-05-11 05:24:50 UTC,"Regression- and Case-Tested once more from a ppa and being good.
Also pushed to ubuntu libvirt-maintainers git as a new cosmic-4.0 branch
Uploaded to Cosmic and completed, now considering SRUs."
1758037,2018-04-25 08:02:25 UTC,"After discussion with upstream on this we found that this also affects other Distributions.
TL;DR: when libpcap has TPACKET_V3 enabled there is a weird incompatibiity between libpcap the kernel & libvirt"
1758037,2018-03-22 13:13:38 UTC,"TL;DR:
- test needs no change to filter
- did this work ever before (happend on 3.6 as well for me)?
- if you retest use >= 4.0.0-1ubuntu6
- did you see bad file descriptor messages, does it help you to see what we need?"
1758037,2018-04-20 09:28:10 UTC,"I tested this on Xenial, Artful and Bionic."
1758037,2018-04-18 13:58:04 UTC,"Ok, so it fails for both of us.
I currently have not debugged the reasons yet."
1758037,2018-04-18 13:31:26 UTC,"------- Comment From <email address hidden> 2018-04-18 06:49 EDT-------
Hi Seeteena,"
1758037,2018-03-27 12:04:41 UTC,"(In reply to Laine Stump from comment #8)

> Was your test platform F28, or something else?
>
"
1758037,2018-03-27 11:09:09 UTC,"(In reply to Martin Sehnoutka from comment #7)

> Created attachment 1413663 [details]
> Libpcap patch that logs debug information and bypasses the problem
>
> Thanks for the reproducer. Just for the record, it is necessary to install
> libvirt-daemon-config-nwfilter package before this starts to work.
"
1758037,2018-03-27 10:27:09 UTC,"Created attachment 1413663
Libpcap patch that logs debug information and bypasses the problem"
1758037,2018-03-26 14:09:49 UTC,"If you have a system with libvirt and virt-manager installed, you can just create a virtual machine, then edit its configuration with ""virsh edit"" to att the following ""<filterref>"" section to its <interface>, then attempt to start the virtual machine:"
1758037,2018-03-22 11:51:14 UTC,------- Comment (attachment only) From <email address hidden> 2018-03-22 07:42 EDT-------
1758037,2018-03-22 11:51:12 UTC,Default Comment by Bridge
1758037,2018-03-22 08:36:38 UTC,"Could you please provide us with some steps to reproduce? Something about how to compile/run the code in order to trigger this bug, so that we can properly examine it."
1758037,2018-02-26 11:33:43 UTC,Switching the needinfo to the assignee(myself).
1758037,2018-02-22 14:24:58 UTC,Can you recommend how we should modify the libvirt code that uses pcap to avoid this regression in pcap's behavior? (while maintaining compatibility with other/older distros that haven't enabled TPACKET_V3)
1758037,2018-02-22 13:27:19 UTC,"TPACKET_V3 was enable because it is a vital feature for network packet analyzers. I don't want to disable it again, because it will trigger other bugs (usually it is about packet drops)."
1758037,2018-02-20 20:03:52 UTC,"Starting with F27, the Fedora-only patch that disabled TPACKET_V3 support was removed with the comment:"
1758037,2018-04-23 14:12:53 UTC,"Based on ""virNWFilterSnoopDHCPOpen:1130 : internal error: pcap_setfilter: can't remove kernel filter: Bad file descriptor"""
1758037,2018-04-25 10:00:02 UTC,"Ok, repro with local build works."
1758037,2018-05-11 06:56:42 UTC,"SRU test builds and tests from PPA worked, pushed for SRU review to X/A/B-unapproved."
1758037,2018-05-21 06:58:19 UTC,This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.23
1758037,2018-05-11 07:03:30 UTC,"Hello bugproxy, or anyone else affected,"
1758037,2018-05-11 09:49:37 UTC,"Upgraded
- 1.3.1-1ubuntu10.23
- 3.6.0-1ubuntu6.7
- 4.0.0-1ubuntu8.1
without issues."
1758037,2018-05-11 10:31:32 UTC,"------- Comment From <email address hidden> 2018-05-11 06:22 EDT-------
(In reply to comment #33)

> Ok, together we found a fix for this which now is integrated upstream.
>
> commit ce5aebeacd10a1c15cb3ee46a59c8b5ff235589e
> Author: Laine Stump <email address hidden>
> Date:   Wed Apr 25 17:12:03 2018 -0400
>
> nwfilter: increase pcap buffer size to be compatible with TPACKET_V3
>
> Bionic+1 is not yet open, so atm it is a bit complex for a few days to push
> fixes.
> Furthermore since this never worked I'm not quite sure we want/need to SRU
> it back to all releases - at least it can't be urgent IMHO.
>
> I'd ask for the reporters opinion for it, my plan would be to:
> 1. wait until 18.10 release opened the Archive
> 2. fix in 18.10
> 3. SRU to 18.04, 17.10, 16.04
>
> Would that be ok for you?
"
1758037,2018-05-21 06:53:40 UTC,"The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1758037,2018-05-21 06:57:44 UTC,This bug was fixed in the package libvirt - 3.6.0-1ubuntu6.7
1758037,2018-05-21 07:03:42 UTC,This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.1
1758037,2018-06-04 09:20:40 UTC,"------- Comment From <email address hidden> 2018-06-04 05:13 EDT-------
(In reply to comment #42)

> (In reply to comment #33)
> > Ok, together we found a fix for this which now is integrated upstream.
> >
> > commit ce5aebeacd10a1c15cb3ee46a59c8b5ff235589e
> > Author: Laine Stump <email address hidden>
> > Date:   Wed Apr 25 17:12:03 2018 -0400
> >
> > nwfilter: increase pcap buffer size to be compatible with TPACKET_V3
> >
> > Bionic+1 is not yet open, so atm it is a bit complex for a few days to push
> > fixes.
> > Furthermore since this never worked I'm not quite sure we want/need to SRU
> > it back to all releases - at least it can't be urgent IMHO.
> >
> > I'd ask for the reporters opinion for it, my plan would be to:
> > 1. wait until 18.10 release opened the Archive
> > 2. fix in 18.10
> > 3. SRU to 18.04, 17.10, 16.04
> >
> > Would that be ok for you?
>
> Yes. Thanks for the quick test results as well.
"
1758037,2018-06-21 14:36:16 UTC,"Because it isn't clear from Comment 14, I wanted to point out that the patch referenced there is not present upstream until libvirt-4.3.0. I had pushed it to the v4.1-maint branch at the end of April so that it will be included in an F28 build, but the Fedora builds have lately been based on the upstream mainline releases rather than the maintenance branches, so this bug is still present in F28 (and also F27)"
1758037,2018-07-03 17:18:12 UTC,libvirt-3.7.0-6.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2b053454a4
1758037,2018-07-04 16:22:24 UTC,"libvirt-3.7.0-6.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2b053454a4"
1758037,2018-05-11 07:01:59 UTC,"Hello bugproxy, or anyone else affected,"
1758037,2018-05-11 07:00:52 UTC,"Hello bugproxy, or anyone else affected,"
1758048,2019-02-25 02:00:28 UTC,Same problem: brand new installation of xubuntu 18.04. Xfce version 4.12
1758048,2014-05-23 11:29:52 UTC,"Created attachment 5494
Panel Items List"
1758048,2014-05-23 11:34:15 UTC,The bug was noticed while using Xubuntu 14.04
1758048,2014-12-07 02:28:50 UTC,I'm experiencing this issue in both Xubuntu 14.04 and 14.10. Here is a video I took during a guest session of 14.10 demonstrating the issue.
1758048,2016-02-09 22:12:39 UTC,"I'm using XFCE 4.12 and have the same issue with the panel item names being duplicated in the list, and they change when hovering the mouse over them. I am using Arch Linux."
1758048,2016-02-09 22:18:29 UTC,"Created attachment 6607
Duplicated Item Names in XFCE 4.12"
1758048,2018-01-09 06:14:56 UTC,"I see the same thing on Fedora 26 with Xfce 4.12, xfce4-panel 4.12.1"
1758048,2018-10-05 08:32:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758050,2018-03-22 13:03:57 UTC,Upstream (based on a merged duplicate): https://dev.gnupg.org/T2011
1758058,2019-12-22 15:45:23 UTC,"root@sc:~# docker logs cinder_volume
+ sudo -E kolla_set_configs
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Copying service configuration files
INFO:__main__:Copying /var/lib/kolla/config_files/cinder.conf to /etc/cinder/cinder.conf
INFO:__main__:Setting permission for /etc/cinder/cinder.conf
INFO:__main__:Writing out command to execute
INFO:__main__:Setting permission for /var/lib/cinder
INFO:__main__:Setting permission for /var/lib/cinder/backup
INFO:__main__:Setting permission for /var/lib/cinder/tmp
INFO:__main__:Setting permission for /var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b
ERROR:__main__:Failed to change ownership of /var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b to 42407:42407
Traceback (most recent call last):
  File ""/usr/local/bin/kolla_set_configs"", line 351, in set_perms
    os.chown(path, uid, gid)
PermissionError: [Errno 1] Operation not permitted: '/var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b'
INFO:__main__:Setting permission for /var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b/.ftpquota
ERROR:__main__:Failed to change ownership of /var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b/.ftpquota to 42407:42407
Traceback (most recent call last):
  File ""/usr/local/bin/kolla_set_configs"", line 351, in set_perms
    os.chown(path, uid, gid)
PermissionError: [Errno 1] Operation not permitted: '/var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b/.ftpquota'
INFO:__main__:Setting permission for /var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b/.banner
ERROR:__main__:Failed to change ownership of /var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b/.banner to 42407:42407
Traceback (most recent call last):
  File ""/usr/local/bin/kolla_set_configs"", line 351, in set_perms
    os.chown(path, uid, gid)
PermissionError: [Errno 1] Operation not permitted: '/var/lib/cinder/backup/a611d2397f2e445ec8fc8de2df80db5b/.banner'
INFO:__main__:Setting permission for /var/lib/cinder/tmp/cinder-cleanup_incomplete_backups_1
INFO:__main__:Setting permission for /var/log/kolla/cinder
INFO:__main__:Setting permission for /var/log/kolla/cinder/cinder-scheduler.log
INFO:__main__:Setting permission for /var/log/kolla/cinder/cinder-api-access.log
INFO:__main__:Setting permission for /var/log/kolla/cinder/cinder-api.log
INFO:__main__:Setting permission for /var/log/kolla/cinder/cinder-backup.log
INFO:__main__:Setting permission for /var/log/kolla/cinder/cinder-wsgi.log
INFO:__main__:Setting permission for /var/log/kolla/cinder/cinder-manage.log
++ cat /run_command
+ CMD='cinder-volume --config-file /etc/cinder/cinder.conf'
+ ARGS=
+ sudo kolla_copy_cacerts
+ [[ ! -n '' ]]
+ . kolla_extend_start
++ [[ ! -d /var/log/kolla/cinder ]]
+++ stat -c %a /var/log/kolla/cinder
++ [[ 2755 != \7\5\5 ]]
++ chmod 755 /var/log/kolla/cinder
++ . /usr/local/bin/kolla_cinder_extend_start
++++ stat -c %U:%G /var/lib/cinder
+++ [[ cinder:cinder != \c\i\n\d\e\r\:\k\o\l\l\a ]]
+++ sudo chown -R cinder:kolla /var/lib/cinder
chown: changing ownership of '/var/lib/cinder/backup/a611d2397f2e445..."
1758067,2018-04-17 05:50:47 UTC,Variable OpenType fonts are not listed at all.
1758067,2018-04-14 22:05:06 UTC,Support is not implemented yet.
1758067,2018-04-17 05:05:07 UTC,"Adolfo, can you please elaborate on what you mean by not implemented yet?
I don't see any indication that opentype support is not implemented in libreoffice (it seems that there's no UI to select specific opentype features, but fonts should definitely be listed at the very least)."
1758067,2018-03-22 16:24:27 UTC,Adobe Source Family seems to be installed.
1758067,2018-03-22 16:09:48 UTC,apport information
1758067,2018-03-22 16:09:46 UTC,apport information
1758067,2018-03-22 16:09:45 UTC,apport information
1758067,2018-03-22 14:24:23 UTC,"Can you please run ""apport-collect 1758067"" to attach useful information to the bug report?"
1758070,2018-04-16 15:23:41 UTC,Over 3 weeks and nobody has posted a reply/comment/solution.
1758070,2018-04-17 15:33:20 UTC,It's been almost a month since I posted this bug. It would be nice if someone looked at it.
1758071,2018-09-12 21:54:29 UTC,In the hope that this might help someone else...
1758071,2018-03-22 14:28:17 UTC,Possible upstream issues: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842015 -> https://dev.gnupg.org/T2818 (-> https://dev.gnupg.org/T2843#)
1758071,2018-07-02 22:28:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758071,2018-07-02 22:31:40 UTC,I have found that using pinentry-gtk-2 is the only one that currently performs a graceful fallback to tty. This has been my solution in the interim. This still has an annoying behavior of not pulling the terminal or application back into focus after entering your pin.
1758073,2018-08-09 15:33:08 UTC,This issue was fixed in the openstack/sushy-tools 0.4.0 release.
1758074,2018-03-24 13:17:50 UTC,"diff --git a/packaging/commands/apt.go b/packaging/commands/apt.go
index 06149dc..6379fef 100644
--- a/packaging/commands/apt.go
+++ b/packaging/commands/apt.go
@@ -50,7 +50,7 @@ var aptCmder = packageCommander{
        isInstalled:           buildCommand(dpkgquery, ""-s %s""),
        listAvailable:         buildCommand(aptcache, ""pkgnames""),
        listInstalled:         buildCommand(dpkg, ""--get-selections""),
-       addRepository:         buildCommand(addaptrepo, ""%q""),
+       addRepository:         buildCommand(addaptrepo, ""%s""),
        listRepositories:      buildCommand(`sed -r -n ""s|^deb(-src)?
(.*)|\2|p""`, ""/etc/apt/sources.list""),
        removeRepository:      buildCommand(addaptrepo, ""--remove ppa:%s""),
        cleanup:               buildCommand(aptget, ""autoremove""),"
1758075,2018-03-22 18:11:48 UTC,Your bug report says that:
1758081,2018-03-23 13:47:45 UTC,I added this code in the egg and buildout is working again.
1758086,2018-04-16 07:23:00 UTC,"Isn't that a thing could be solved with the max_unit property for Placement inventory?
https://developer.openstack.org/api-ref/placement/#update-resource-provider-inventories"
1758086,2018-04-17 10:36:00 UTC,"@Andrey, no it needs to be depending on the vendor ID, since that problem is only related to the nvidia driver."
1758086,2018-04-18 14:56:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/562304"
1758086,2018-09-20 21:58:47 UTC,"Reviewed:  https://review.openstack.org/562304
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7529627488886f981a4c3d3d7994f92ef7956cee
Submitter: Zuul
Branch:    master"
1758086,2020-10-20 15:07:33 UTC,"FWIW, tested with nvidia GRID10.2 release (R440.87) and the issue remains."
1758091,2020-11-13 16:09:54 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1758092,2018-07-18 12:08:23 UTC,"I think we still deploy with both API versions enabled, so we'll also need to disable the v1 api for the switch point where we stop deploying the registry service."
1758104,2018-04-04 01:21:39 UTC,"Reviewed:  https://review.openstack.org/555373
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=d6c6011fc83ab9a3bbd65e8dd4557ebf25b363ae
Submitter: Zuul
Branch:    master"
1758104,2018-03-22 16:58:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555373"
1758110,2018-03-22 17:02:25 UTC,E: Sub-process /usr/bin/dpkg returned an error code (1)
1758117,2019-03-14 20:59:36 UTC,`rmadison calligraplan` shows that package is missed only for Ubuntu 18.04 LTS (bionic)
1758117,2019-03-14 20:58:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758117,2019-01-31 10:34:20 UTC,"There is a separate package calligraplan for cosmic and disco
https://launchpad.net/ubuntu/+source/calligraplan"
1758134,2018-05-08 18:15:10 UTC,This change was made by a bot.
1758144,2018-03-22 20:36:38 UTC,It looks like `repo-use.yml` isn't compatible with JIT configuration of Unbound clients introduced in https://github.com/openstack/openstack-ansible/commit/b3c670faeba53eb00212deb1e197499959c40561
1758144,2018-05-30 11:52:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571178"
1758144,2019-08-07 15:40:16 UTC,"Change abandoned by Jesse Pretorius (odyssey4me) (<email address hidden>) on branch: master
Review: https://review.opendev.org/571178
Reason: No longer working on this. Please restore this patch if it is still required."
1758155,2019-03-11 21:45:19 UTC,The above error still occurs in 0.7.17.
1758155,2020-06-12 19:58:52 UTC,Just tested on duplicity 0.8.13
1758155,2020-06-12 21:04:11 UTC,I'm going to close this and open a low priority bug on Gitlab about making the output nicer.
1758185,2018-04-02 20:00:48 UTC,This requires changes in the breezy UI/API.
1758212,2018-03-31 14:36:54 UTC,"This bug is present also in Inkscape 0.92.3 (2405546, 2018-03-11)"
1758212,2020-04-05 11:19:46 UTC,Closing because INVALID: Migrated.
1758214,2018-03-23 01:47:29 UTC,Example of unresponsive window
1758214,2018-03-23 05:35:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758214,2018-03-23 10:08:08 UTC,"That is a known issue. I had code to add a progress bar, but it was unfinished, so I preferred to simply restore the old behaviour for now. The prime-select tool takes a while to complete."
1758214,2020-05-04 21:57:58 UTC,"That was most likely caused by initramfs update in the background that is no more performed after https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011 fixed, released in version 0.8.8.1"
1758221,2019-09-16 14:07:35 UTC,"Hi Lajos,"
1758221,2019-09-16 13:52:32 UTC,"Thanks Kees,
I verified that having the service_provider line twice can cause this issue, I close this."
1758221,2019-08-10 12:02:52 UTC,"This is more a configuration issue so this bug could be closed, I guess."
1758221,2018-03-25 17:50:08 UTC,I would need neutron.conf and l2gw_plugin.ini to check your configuration.
1758221,2019-08-10 12:02:09 UTC,This problem arises when mentioning configuration twice:
1758232,2018-03-29 00:10:06 UTC,This issue was fixed in the openstack/puppet-barbican 12.4.0 release.
1758232,2018-03-23 07:09:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555663"
1758232,2018-03-26 22:53:45 UTC,"Reviewed:  https://review.openstack.org/555663
Committed: https://git.openstack.org/cgit/openstack/puppet-barbican/commit/?id=add33824e46ff1b61e512ba83158876f8fbf1e5c
Submitter: Zuul
Branch:    master"
1758232,2018-03-27 00:18:53 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/556685"
1758232,2018-03-27 00:19:21 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/556686"
1758232,2018-03-28 02:15:22 UTC,"Reviewed:  https://review.openstack.org/556685
Committed: https://git.openstack.org/cgit/openstack/puppet-barbican/commit/?id=7c7dc16a49e01c7ccd5f191652f37e4e29b0c26e
Submitter: Zuul
Branch:    stable/queens"
1758232,2018-03-28 02:26:20 UTC,"Reviewed:  https://review.openstack.org/556686
Committed: https://git.openstack.org/cgit/openstack/puppet-barbican/commit/?id=8dc9fcf88d6cde81783c046534f755f7c9ccd446
Submitter: Zuul
Branch:    stable/pike"
1758232,2018-04-19 20:58:55 UTC,This issue was fixed in the openstack/puppet-barbican 13.0.0 release.
1758232,2019-05-16 23:02:32 UTC,This issue was fixed in the openstack/puppet-barbican 11.6.0 release.
1758233,2018-03-23 04:03:39 UTC,Is there a potential for corrupting the database with multiple instances open?
1758233,2018-03-23 11:46:02 UTC,"The database cannot be ""corrupted"" by it.
But you can have all kinds of race conditions when playing or editing the same track or playlists.
For example if you play the same track in both instances, the play counter may be incremented by on or by two."
1758233,2018-03-23 11:48:41 UTC,"Bug or feature?
For me this is a feature, because you can use two different soundcard and databases.
We can consider to place a warning:
""One instance of Mixxx is already running. Do you wish to start a second one?"""
1758233,2020-09-24 23:40:44 UTC,"I thought about an option for ""Only allow one instance of Mixxx"", where trying to launch again would just refocus the running instance. Probably better to comment here rather than create a new issue."
1758236,2018-08-21 21:33:36 UTC,I'm the same problem with manjaro.
1758240,2018-03-23 12:07:56 UTC,"There is no ConsistencyGroupException in tempest that the tests are expecting, so that one is obvious. But the one about the group state looks like a correct failure. Can you attach the cinder logs so we can trace what was done against that CG?"
1758240,2018-08-29 17:36:36 UTC,What is the backend being used here?
1758243,2018-05-01 05:46:20 UTC,"@Roman: I don't know what might be wrong. You might be able to get more information with the command ""systemctl status bumblebeed.service"". Also, you could try ""tail -f /var/log/syslog"" in one terminal before running ""optirun glxinfo"" in another and check back on the tail output afterwards. ""journalctl -e"" might also have some relevant info."
1758243,2018-04-30 14:04:33 UTC,"@Rocko: unfortunately it didn't work. I've also tried the 5 commands by Juan Montero (purge and then reinstall), but it didn't help. Any idea what can be wrong?"
1758243,2018-05-01 09:52:51 UTC,"Sorry for the length of this post, I don't know how to attach multiple files.
I am pasting the output of the following commands:"
1758243,2018-04-28 20:16:40 UTC,"This solution worked for me, but I had to manually install nvidia-dkms-390.
I think bumblebee-nvidia should pull in this package automatically."
1758243,2018-04-28 21:12:12 UTC,Update: both optirun and primusrun crash when trying to load openGL.
1758243,2018-04-03 13:40:47 UTC,"For me it doesn't work even with setting all the stuff mentioned here. Neither with intalling nvidia-prime, which sets different blacklisting. The error is that Nvidia GPU could not be found."
1758243,2018-03-28 18:46:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758243,2018-05-02 00:23:10 UTC,@Juan: I should have suggested running just optirun glxinfo|grep 'server glx vendor'!
1758243,2018-04-25 01:06:25 UTC,"@Roman: it might be the systemd nvidia-fallback, which loads nouveau if the nvidia driver isn't loaded. I'm seeing this problem now even with my 'alias nouveau off' setting:"
1758243,2018-05-02 02:53:53 UTC,I've opened https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1768390 for the X_GLXSwapBuffers issue.
1758243,2018-05-02 09:07:06 UTC,"Hi Rocko,"
1758243,2018-05-03 03:25:30 UTC,"@Roman: it sounds like bumblebee is trying to load a module that has been aliased to 'off' somewhere in your /etc/modprobe.d folder. Is the configuration in /etc/bumblebee/bumblebee.conf set to load nouveau, perhaps? Or has the nvidia module been aliased to off by accident?"
1758243,2019-10-20 17:24:40 UTC,@Rocko Do you now if the new NVIDIA PRIME offloading support works with AMD (CPU) + Nvidia combo? I know someone who has one of those laptops and I was amazed to discover there was not a single working solution for that combo (which is understandable since those laptops are very recent).
1758243,2019-10-20 14:21:19 UTC,"@Matthieu: Yes, nvidia on-demand works great in Ubuntu 19.10 with those two variables. I also include this one (it's to make Vulkan only use the nvidia card - Vulkan works really well for running DX 11 wine apps using dxvk):"
1758243,2019-10-17 21:51:56 UTC,"Hello,"
1758243,2019-10-17 10:05:19 UTC,Hi!
1758243,2019-10-17 09:32:38 UTC,@Rocko
1758243,2019-09-17 15:42:29 UTC,@Pete:
1758243,2019-09-17 09:18:52 UTC,"I had all this working wonderfully on a Thinkpad T480 on Ubuntu Disco, until a recent reboot after an update (possibly due to kernel 5.0.0-27, possibly due to a udev update)"
1758243,2019-06-10 18:57:53 UTC,"Very important: I had to select ""intel"" in nvidia-settings to prevent loading the blacklisted nvidia driver by nvidia-persistenced."
1758243,2019-06-09 12:06:23 UTC,These proposed way seems to work for me. What are the next steps to bring it upstream?
1758243,2019-05-27 20:39:23 UTC,"Note: Also export PRIMUS_libGL=/usr/lib/x86_64-linux-gnu/libGL.so.1 to make primusrun work.
And #31 and #32 works for nvidia-dkms-430 with the above environment variable"
1758243,2019-04-01 15:44:08 UTC,"Sorry, the path is cropped in my previous post.
The correct path is:"
1758243,2019-04-01 15:42:41 UTC,"I just did a fresh install of the Disco beta, with nvidia-driver-418, bumblebee-3.2.1-20 and the manual configuration is still required, as follows:"
1758243,2019-01-15 09:10:22 UTC,"And just to correct some typos in my comment above: the extra X shouldn't appear after that XorgModulePath= line, and of course it's systemctl not systemctrl for restarting the daemon."
1758243,2019-01-15 09:08:55 UTC,@zubozrout: I got the same error (Module 'nvidia' is not found) when I tried it just now. I had to alter the /etc/bumblebee/bumblebee.conf XorgModulePath in 18.10 to get optirun to work with the nvidia 415 driver:
1758243,2019-01-08 14:25:31 UTC,"Btw, I've tried to follow this guide (among others) which seems quite complex but is is a complete no-go for me: https://float-middle.com/ubuntu-18-04-steam-and-nvidia-390/"
1758243,2019-09-17 09:43:50 UTC,A followup to the above (#36):
1758243,2018-09-12 03:21:39 UTC,"FWIW, I've found that optirun doesn't work in Ubuntu 18.10 - the nvidia module loads but as soon as the application tries to create a 3D window, the appliction exits - but primusrun does work, so long as you ensure the path to its libGL is correct, as per https://github.com/Bumblebee-Project/Bumblebee/issues/951#issuecomment-379512353:"
1758243,2018-05-03 07:54:28 UTC,"OK, after installing a fresh copy of Ubuntu 18.04 and executing exactly the steps mentioned here I managed to get to a state where you are. Non-GL apps work with optirun, GL apps throw BadMatch (invalid parameter attributes) error. So I'll wait until the bug you opened is solved. Then we will see."
1758243,2018-05-04 19:10:33 UTC,"I am at the same point as well with 18.04.  OpenGL fails with the same error, while everything else seems to work as expected.  I guess no Steam for me until this is fixed."
1758243,2018-05-07 08:37:46 UTC,"For me switching to Nvidia card using the Nvidia settings tool or prime-select works like a charm. Also when I set the kernel parameter nvidia-drm.modeset=1 I get a tear-free experience, which is excellent. So while this is not fixed, I can fully use the Nvidia card by switching to it entirely."
1758243,2018-05-23 18:28:56 UTC,"I can confirm as of today this bug is still present.
I made the changes suggested by Rocko. Still primusrun does not work properly."
1758243,2018-05-31 07:33:55 UTC,I have the exact same issue with the exact same error messages as the original post.
1758243,2018-05-31 07:36:01 UTC,"Whoops, I meant to say that I have the exact same error messages as Juan in post #6 (https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/comments/6)"
1758243,2019-01-08 14:22:54 UTC,"@rockorequin - I seem to be able to launch apps with primusrun setting the correct libGL path, but although apps launch that way they are actually not using Nvidia but only the integrated Intel GPU (at least I don't see any performance improvements). In the bumblebee lok I can then see the following issue:"
1758243,2018-06-04 10:12:00 UTC,"Thanks, that solved it. I had a million tabs open, and I guess I missed that line late in his OP."
1758243,2018-06-05 14:55:39 UTC,"The fix from post #20 solved the issue.
Now both glxgears and glxheads work."
1758243,2018-06-19 05:07:56 UTC,"I can confirm that the full procedure covered in #1 and #5 has worked for me once I added one addition change. I found a file in /etc/modprobe.d with the line ""alias nvidia off"" which prevented bumblebee from loading the nvidia module. It was in /etc/modprobe.d//blacklist-nvidia.conf which I believe is created by prime-select and remained although nvidia-prime had been purged. I commented out the line and restarted bumblebee with ""sudo systemctl restart bumblebeed"" and everything then worked."
1758243,2018-07-20 01:36:56 UTC,these two lines is no longer necessary.
1758243,2018-08-02 00:29:14 UTC,"I would recommend keeping the ""nvidia_drm"" and ”nvidia_modeset"" aliases since removing them caused me problems (system freezes after running primusrun/optirun or loading the nvidia kernel module)."
1758243,2018-06-04 07:23:42 UTC,"From the attached bumblebee issue, carlicious recently posted that a fix for running Ubuntu apps other than wine is to set __GLVND_DISALLOW_PATCHING=1 (and this works for me - I tried running 0ad, glxheads)."
1758244,2019-08-02 15:09:19 UTC,"fixxed in https://github.com/mixxxdj/mixxx/pull/1880
""Deere :: add Key/BPM expansion indicators, put Key controls next to play position """
1758250,2018-03-23 08:41:38 UTC,'wayland' is just the protocol so please don't assign bugs to that.
1758250,2018-03-23 08:55:35 UTC,"Sorry, that's not easy for me. Thank you for your help."
1758250,2018-03-23 08:19:49 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1758252,2018-03-23 06:43:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555656"
1758252,2018-03-23 07:02:06 UTC,"Change abandoned by tanmingxiao (<email address hidden>) on branch: master
Review: https://review.openstack.org/555656"
1758253,2018-03-23 06:51:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555658"
1758253,2018-03-23 15:01:42 UTC,"Hi @weikeyou,"
1758253,2018-03-23 15:05:02 UTC,I am going to set this bug as incomplete because we need further information to triage this bug. Please feel free to reset the status once further information is provided.
1758253,2020-06-22 02:27:01 UTC,"Change abandoned by weikeyou (<email address hidden>) on branch: master
Review: https://review.opendev.org/555658"
1758258,2018-03-23 07:16:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/555667"
1758258,2018-05-09 00:57:55 UTC,"Change abandoned by jihoon (<email address hidden>) on branch: master
Review: https://review.openstack.org/555667"
1758258,2018-05-09 01:03:37 UTC,closed
1758274,2018-03-23 09:45:59 UTC,"Suggest change your update mirror - run ""Software & Updates"" and choose a different mirror there."
1758274,2018-04-21 18:28:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758275,2018-08-26 20:33:41 UTC,"It's not evaluating the defun, it's taking the named-lambda used by the defun and making a local call to it. This is a known issue."
1758275,2018-08-26 11:03:26 UTC,"Hello Adam,"
1758275,2018-08-26 19:46:25 UTC,"Hello Richard,"
1758282,2020-12-07 08:08:12 UTC,"Hello,
fix for second problem has been accepted upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=a64f1263a56bd8653267c1a9800daa0bc993a743"
1758282,2020-03-24 08:18:48 UTC,"Hi,
We have two issues here:
1. mdraid stuff is always included in initrd even system isn't on raid( ubuntu specific).
2. grow continue service is not restarted after switch root( to be fixed in upstream)"
1758282,2020-03-23 14:42:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758282,2018-03-26 09:28:07 UTC,"This seems to me to be an upstream bug. The grow command starts the systemd unit, but doesn't enable it to be persistent. The md device names can change after reboot (if an additional array is connected whilst the system is off), therefore I think upstream udev rules should be improved to detect arrays that need mdadm-grow-continue@.service, and trigger that unit via SYSTEMD_WANTS stanza in the udev rules."
1758282,2018-07-16 14:44:17 UTC,"Mdadm is running it's additional instance for reshape purposes.
It might do it in two ways:
running systemd service file (mdadm-grow-continue service), or by forking.
The second one is used as fallback method, executed if first one fails."
1758287,2019-04-17 12:12:36 UTC,https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
1758287,2018-03-23 09:58:26 UTC,"StacktraceTop:
 __glXSendError (dpy=dpy@entry=0x56326c2d49e0, errorCode=errorCode@entry=0 '\000', resourceID=resourceID@entry=0, minorCode=minorCode@entry=26, coreX11error=coreX11error@entry=false) at ../../../src/glx/glx_error.c:62
 MakeContextCurrent (dpy=0x56326c2d49e0, draw=39845959, read=39845959, gc_user=0x56326d414050) at ../../../src/glx/glxcurrent.c:216
 InternalMakeCurrentVendor (dpy=dpy@entry=0x56326c2d49e0, draw=draw@entry=39845959, read=read@entry=39845959, ctxInfo=ctxInfo@entry=0x56326d3f6910, callerOpcode=<optimized out>, threadState=threadState@entry=0x56326c6aee90, vendor=0x56326c479200) at ../../../src/GLX/libglx.c:823
 CommonMakeCurrent (dpy=0x56326c2d49e0, draw=39845959, read=39845959, context=<optimized out>, callerOpcode=<optimized out>) at ../../../src/GLX/libglx.c:1005
 destroy_objects (texture=0x56326c71fed0) at ../../../../gst-libs/gst/vaapi/gstvaapitexture_glx.c:87"
1758287,2018-04-23 19:57:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758287,2018-04-24 01:26:54 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91"
1758287,2019-04-16 17:06:03 UTC,"Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1758287"
1758287,2019-04-16 17:13:20 UTC,Which exact Mesa/GLX version has this been tested with?
1758287,2019-04-17 17:49:37 UTC,https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
1758289,2018-08-15 04:50:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758291,2021-02-19 15:51:45 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1758291,2018-03-29 15:32:52 UTC,"Reviewed:  https://review.openstack.org/554647
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=19e25fe2fdba56300d69f66067a90d4910eb9410
Submitter: Zuul
Branch:    stable/newton"
1758291,2018-03-29 14:23:37 UTC,For newton https://review.openstack.org/#/c/554647/
1758324,2018-03-23 12:58:25 UTC,"The default dhclient timeout is 60, centos have changed it in the cloud image to 300 here
https://bugs.centos.org/view.php?id=6866"
1758324,2021-02-17 17:07:10 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1758328,2018-03-23 13:16:49 UTC,Shortcut to the function - http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/sql/Pg/030.schema.metabib.sql;hb=HEAD#l830
1758330,2018-03-23 13:28:23 UTC,"StacktraceTop:
 handle_mount (filesystem=0x561009e74e00, invocation=0x7f800400b500, options=0x561009f49010) at udiskslinuxfilesystem.c:1447
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7f7ffd7c5870, fn=fn@entry=0x561008f68270 <handle_mount>, rvalue=<optimized out>, avalue=avalue@entry=0x7f7ffd7c5780) at ../src/x86/ffi64.c:525
 g_cclosure_marshal_generic (closure=0x561009ebfc40, return_gvalue=0x7f7ffd7c5a40, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=<optimized out>) at ../../../../gobject/gclosure.c:1490
 g_closure_invoke (closure=0x561009ebfc40, return_value=0x7f7ffd7c5a40, n_param_values=3, param_values=0x7f7fe8002370, invocation_hint=0x7f7ffd7c5a20) at ../../../../gobject/gclosure.c:804"
1758336,2019-04-16 15:44:02 UTC,"I also have a Radeon WX 3100 card, and you would have to get the AMDGPU PRO drivers from AMD. However, I saw in the release notes of the latest available drivers (19.Q1 as I write this) that the WX 3100 and the WX 2100 are not supported by their Linux drivers for OpenCL. Perhaps the next iteration of the drivers will."
1758339,2018-05-23 12:30:33 UTC,Also seeing this - not sure what effect it has on us.
1758339,2019-07-19 19:44:19 UTC,"Hi,"
1758339,2019-07-19 19:44:55 UTC,Please reopen (mark as new) if you feel there's something that cloud-init is not doing correctly.
1758349,2018-03-23 15:21:16 UTC,I noticed this a while ago: it only appears in developer mode.
1758349,2018-03-23 19:00:54 UTC,"Indeed, thanks for pointing that out.
Adding a note to the comment will do it."
1758353,2019-07-10 07:56:41 UTC,It's possible that your port is Binding_failed.
1758353,2019-07-25 11:54:41 UTC,"Nothing you see in openstack, you can only see the errors in the logs and you'd notice that the machines was unreachable. Notice, this happens to running machines, machines that might have been running for months."
1758354,2018-03-23 14:58:00 UTC,"Another thing we should cleanup is the documentation around the ""disable_libvirt_livesnapshot"" config option because it talks about libvirt 1.2.2 but the minimum required libvirt version at this point is 1.2.9, so that's confusing. Per bug 1741667, we should probably mention that live snapshot of a non-running instance isn't known to work until at least libvirt 3.6.0 per our test infrastructure. Anything between 1.2.9 and 1.3.6 would have to be tested for snapshotting a non-running instance."
1758356,2018-03-26 10:35:14 UTC,"Sorry, but I cannot help you: problem situation too complex and too far away from my experiences."
1758356,2018-03-26 07:37:13 UTC,"It is CentOS 6.3.
I thinks my problem is coming from my installation because i did the offline install but it does not work (same problem : https://bugs.launchpad.net/sikuli/+bug/1756820)"
1758356,2018-03-23 16:08:01 UTC,"Thanks,"
1758356,2018-03-23 16:29:17 UTC,"see docs:
http://sikulix-2014.readthedocs.io/en/latest/interaction.html#listening-to-global-hotkeys"
1758356,2018-03-23 15:43:41 UTC,guess you are talking about 1.1.2 ;-)
1758356,2018-03-23 16:30:08 UTC,I just checked on my Ubuntu 16.04 64-Bit and cannot reproduce the problem.
1758356,2018-03-23 15:25:53 UTC,"In terminal a message : Exception : org.python.core.PyException thrown from the UncaughtExceptionHandler in thread ""Thread-9"""
1758358,2018-04-06 07:22:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559287"
1758363,2018-05-11 21:35:29 UTC,"I'm sorry to report that this is not merely ""cosmetic"". I just noticed there is also a behavioral impact; when such a warning is triggered while running - for example - quilt pop 5, if the first de-application causes the warning, only 1 patch will be popped."
1758364,2018-04-10 09:32:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1758364,2018-04-23 12:52:04 UTC,This bug was fixed in the package linux-oem - 4.13.0-1024.27
1758364,2018-04-23 09:21:59 UTC,This bug was fixed in the package linux - 4.13.0-39.44
1758364,2018-04-19 08:51:04 UTC,"Hi @alexander-deucher,"
1758364,2018-04-16 10:24:20 UTC,please check the proposed kernel(s) and adjust the tags
1758364,2018-04-09 12:49:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1758366,2018-03-23 15:26:51 UTC,"test_wpa2_ip4 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv4 ... ok
test_wpa2_ip6 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv6 with only RA ... ok
test_auto_detect_ap (__main__.Hotplug)
new AP is being detected automatically within 30s ... expected failure
test_auto_detect_eth (__main__.Hotplug)
new eth router is being detected automatically within 30s ... Cannot find device ""eth0""
/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm:23: PyGIWarning: NetworkManager was imported without specifying a version first. Use gi.require_version('NetworkManager', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import NetworkManager, NMClient, GLib
/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm:23: PyGIWarning: NMClient was imported without specifying a version first. Use gi.require_version('NMClient', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import NetworkManager, NMClient, GLib
expected failure"
1758373,2018-03-23 15:46:49 UTC,"HELP!  I adjusted at the beginning of the bug report, that this is NOT a gnome-settings-daemon bug, BUT a bison bug, ... there was a possibility TO CHANGE THE PACKAGE WHAT IS AFFECTED, I do not know why it changed back to gnome-settings-daemon?"
1758373,2018-03-23 17:17:32 UTC,"In the future, please use `ubuntu-bug package-name` to report bugs. Thanks.
https://help.ubuntu.com/dev/ubuntu-help/report-ubuntu-bug.html.en"
1758373,2018-03-24 12:59:53 UTC,"> In the future, please use `ubuntu-bug package-name` to report bugs. Thanks.
> https://help.ubuntu.com/dev/ubuntu-help/report-ubuntu-bug.html.en
"
1758381,2020-08-10 16:49:51 UTC,"Thank you to Jennifer Weston, Jennifer Pringle, and Elaine Hardy for assisting in testing. I have added my sign off to:"
1758381,2020-08-13 14:55:40 UTC,"This needs more work, as it breaks the grid if the user does one of the following:"
1758381,2020-08-08 17:56:50 UTC,"Tested patch Terran loaded to test server. It does indeed appear to now order the items in the order scanned.  Success!  One note - XUL used to do this in reverse order by time entered. It was helpful to have the last one scanned at the top of the list rather than at the bottom but I'm not sure that's a show-stopper.  Order scanned whether direct or reverse is certainly an improvement.
+1 to signing off on this as it is"
1758381,2020-05-20 21:19:24 UTC,Here's a branch that forces scan order on the pending tab:  https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1758381-copy-bucket-pending-order
1758381,2020-04-09 00:17:09 UTC,Confirmed still an issue in 3.5beta
1758381,2019-09-19 19:16:55 UTC,Confirming that scanning items into the Pending tab of Item Buckets still appears to sort them based on Copy ID (rather than displaying in the order scanned) in 3.3.3.
1758381,2019-02-04 15:38:49 UTC,Our libraries also would like them to appear in the order they were scanned.
1758381,2019-01-08 15:15:36 UTC,Additional testing in 3.1 suggests sort order is based on Copy ID.  Our libraries would also prefer that they appear in the order they were entered.
1758381,2018-05-29 20:10:38 UTC,Based on preliminary testing the order may not be random but may in fact be sorting based on call number in 3.1.
1758381,2020-08-18 01:01:29 UTC,Holding on repatch to fix grid breakage.  No strong preference from CWG conversations relating to direct order versus reverse order.  Direct order will be fine.  We would like to see the order retained when transferring from pending into copy bucket.
1758381,2018-04-25 23:45:20 UTC,Confirmed that the random order and the inability to sort on the Pending Copies tab are both still present in 3.1
1758381,2018-06-26 22:41:13 UTC,Our libraries would prefer that they appear in the order they were entered so staff can double check that no items were missed.
1758381,2020-08-26 19:59:31 UTC,"I know I'm a little late on this discussion, but I do like the most recently scanned at the top. It makes it much easier to check, especially if you're scanning more items than what the field is set to show at the time."
1758385,2018-06-16 19:29:28 UTC,Upstream bug: https://github.com/ubuntu-mate/mate-tweak/issues/38
1758389,2018-03-24 17:27:57 UTC,"I attached a patch, illustrating changes I propose.
I amended ""recurse"" option so that it take a regexp of filesystem names to work on, besides old values ""0"" and ""1"". That is, old values keep their meaning, but if recurese is set to something like ""boot|backup"" it will work only on those filesystems."
1758389,2018-03-24 20:19:06 UTC,"The attachment ""0001-Allow-to-list-affected-filesystems-in-recurse.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1758389,2018-03-26 16:48:42 UTC,Simplified conditional logic and allowed to negate expression.
1758389,2018-03-26 17:08:08 UTC,"Please disregard last paragraph in my comment #1. I've found that I was not able to boot with recurse=1 not due of read-only /var, but due of script's attempt to remount absent cdrom for which I have an entry in my /etc/fstab (added by system installer)."
1758393,2018-03-24 04:00:46 UTC,Changing the component for this bug.
1758396,2018-03-23 17:14:36 UTC,"After load the 3D, all software responds."
1758398,2018-03-27 17:33:43 UTC,"It's about mounts on /media, mounted by command line or pam_mount."
1758398,2018-03-26 12:46:36 UTC,The change has been done in https://gitlab.gnome.org/GNOME/glib/commit/0d69462
1758398,2018-03-26 12:09:35 UTC,"The description is misleading, smb: or ssh: mounts done from the desktop are listed, it's only about traditional mounts using cifs/smbfs right?"
1758398,2018-03-26 12:08:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1758398,2018-03-27 17:55:09 UTC,"Someone reported it.
https://gitlab.gnome.org/GNOME/nautilus/issues/312"
1758398,2018-04-13 10:53:09 UTC,"x-gvfs-show doesn't work either
https://gitlab.gnome.org/GNOME/nautilus/issues/362"
1758402,2019-04-07 14:29:01 UTC,"Thanks for looking into this.  I've rebuilt the NFS server host, upgrading from NFS 4.1 to 4.2, and upgraded the client to Kubuntu 19.04 (beta) and now I can no longer reproduce this problem.  .xsession-errors no longer contains the reported messages about KActivities"
1758402,2018-07-23 08:47:03 UTC,I guess you found the same things regarding NFS and sqlite as I did.
1758402,2018-05-14 16:46:45 UTC,"I chatted with some of the Linux NFS kernel developers and they know of no problems with sqlite on NFS when used against a Linux server.  I did find some documentation of problems with Solaris servers, but the Firefox developers did get the ""unix-excl"" VFS pushed into upstream sqlite a few years ago which does internal locking.  I'm not sure what kactivitymanagerd is using.  (I searched the source but don't see anywhere that might be set; I guess it's only using frameworks or qt functions to interact with sqlite.)"
1758402,2018-05-14 16:04:16 UTC,"Oh, great.  This is going to be absolutely terrible."
1758402,2018-05-12 08:44:21 UTC,After receiving a recent update to Firefox it can't access it's bookmarks.
1758402,2018-04-24 00:05:02 UTC,"Also, the NFS version involved here is 4.2; NFS3 is not involved at all.  It shouldn't matter at all, but we use kerberized NFS (sec=krb5p) and the servers are all running RHEL7.4."
1758402,2018-04-23 23:55:23 UTC,All user home directories are automounted and the mount options are identical between users.
1758402,2018-04-23 18:20:38 UTC,"The NFS might be the problem - namely, from what I've read in sqlite3 docs, the 'shared memory' might not work on some NFSs. I'll probably have to make Kamd disable the database (and everything that uses the database - favourites, recent documents...) on nfs instead of it failing to start."
1758402,2018-04-23 17:57:33 UTC,"@Jason Tibbits:  Is there any difference between users in the line in fstab that mounts the NFS share, e.g. mount options?"
1758402,2018-03-21 19:12:56 UTC,Plasma 5.12.3 was working fine on Kubuntu 17.10 plus backports ppa
1758402,2018-04-07 18:06:37 UTC,Strictly the fix is the same.  A crashing kactivitiesmanagerd will no longer crash plasmashell.
1758402,2018-04-07 17:39:59 UTC,I do not think this is a duplicate of 387979:
1758402,2018-03-28 21:35:31 UTC,*** This bug has been marked as a duplicate of bug 387979 ***
1758402,2018-03-28 21:33:13 UTC,As a work-around on 18.04: if I make the kactivitymanagerd/resources directory a symlink to directory on the local (non-NFS) disk then plasma does not crash.
1758402,2018-03-28 19:27:04 UTC,Comment 1 was on 18.04 beta.
1758402,2018-03-27 17:38:33 UTC,"paul@desktop:~/.local/share/kactivitymanagerd/resources$ sqlite3 database
SQLite version 3.22.0 2018-01-22 18:45:57
Enter "".help"" for usage hints.
sqlite> pragma journal_mode;
Error: disk I/O error
sqlite> pragma journal_mode=wal;
Error: disk I/O error
sqlite>"
1758402,2018-03-23 17:32:47 UTC,"Sorry, trying again to attach .xsession-errors"
1758402,2018-03-23 17:30:24 UTC,The full .xsession-errors file is attached
1758402,2018-04-23 17:31:02 UTC,"I just wanted to add that it may be related to NFS, but there is also something else involved which I don't yet understand."
1758409,2018-03-23 21:23:34 UTC,"Example run on a slower machine shows how nocloud-kvm does require more time:
https://paste.ubuntu.com/p/nW3TySXSCc/"
1758409,2018-03-23 21:00:36 UTC,"#1 is handled already by the retry logic in instances.py:_wait_for_system, so I am only going to update _ssh_connect to not wait as long."
1758422,2018-08-29 16:54:49 UTC,"I can verify that this is still happening, but unfortunately I'm not sure what we can do about it. The only ""solutions"" I've found involve downloading and patching unittest2 as part of the package build, which isn't really something we can control."
1758444,2018-03-23 21:47:20 UTC,Run gnome software and install gnome terminal
1758444,2018-03-23 23:32:23 UTC,running tilix from gnome terminal it works fine. Launching from the dock or menu doesn't work.
1758444,2019-05-27 17:17:54 UTC,"I have the same situation on 18.04. Same happened for Files.
What is helping me is to kill  gnome-session-binary.
After restart all working well."
1758447,2018-10-03 13:22:54 UTC,Triaged:
1758459,2018-11-13 14:39:40 UTC,"The report got no duplicate or user activity so it doesn't seem important for our users, also there is no testcase so it's difficult to verify a SRU until we get one, tagging as rls-not-fixing but we can still do the update later if someone describe how to trigger the issue"
1758459,2020-05-01 20:13:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu."
1758459,2018-07-31 08:51:13 UTC,Do you have an example that could be used to write a testcase for a SRU?
1758459,2018-04-18 07:51:45 UTC,"The changes from 2.93 seem mostly bugfixes,
https://github.com/transmission/transmission/releases/tag/2.93"
1758459,2018-03-23 23:27:53 UTC,A private tracker I belong to now requires 2.93 or above.
1758459,2018-03-23 23:22:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758462,2018-03-24 01:42:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/555970"
1758462,2018-03-24 01:43:54 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/555972"
1758462,2018-03-24 02:00:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/555974"
1758462,2018-03-24 14:28:18 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/556025"
1758462,2018-03-26 10:13:49 UTC,"Reviewed:  https://review.openstack.org/555970
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=b8725e5d2bad6ce069d8cfb67afa88137632286e
Submitter: Zuul
Branch:    master"
1758462,2018-03-26 12:03:33 UTC,"Reviewed:  https://review.openstack.org/555972
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=ef089271479ea65fc3200cd9e2bbe69a3d004e07
Submitter: Zuul
Branch:    stable/queens"
1758462,2018-04-06 19:53:00 UTC,"Reviewed:  https://review.openstack.org/555974
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=83c4ec9393db8caec118fec97b1d522b77d07138
Submitter: Zuul
Branch:    master"
1758462,2018-04-07 04:05:25 UTC,"Reviewed:  https://review.openstack.org/556025
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=22efd5de5478676fc643a534ab52360f20eb968a
Submitter: Zuul
Branch:    stable/queens"
1758463,2018-03-24 00:00:06 UTC,This change was made by a bot.
1758463,2018-03-27 21:20:45 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1758463,2018-03-31 19:02:41 UTC,Also exists in 16.04LTS and upstream in  v4.16-rc7.  tag::kernel-bug-exists-upstream
1758465,2019-10-15 11:08:04 UTC,There's some related work for better resiliency against unknown unknowns but it's not close to landing: https://github.com/snapcore/snapd/pull/7205
1758465,2018-03-24 00:08:28 UTC,of course removing the broken symlinks fixed the issue.
1758466,2018-03-24 00:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1758466,2018-03-24 01:03:34 UTC,apport information
1758466,2018-03-24 01:03:36 UTC,apport information
1758466,2018-03-24 01:03:37 UTC,apport information
1758466,2018-03-24 01:03:39 UTC,apport information
1758466,2018-03-24 01:03:40 UTC,apport information
1758466,2018-03-24 01:03:41 UTC,apport information
1758466,2018-03-24 01:03:43 UTC,apport information
1758466,2018-03-24 01:03:45 UTC,apport information
1758466,2018-03-24 01:07:18 UTC,Can see the difference in the dmesg output
1758466,2018-04-22 05:19:55 UTC,This appears to have been fixed in:
1758471,2018-04-23 08:22:44 UTC,This bug was fixed in the package linux - 4.4.0-121.145
1758471,2018-03-24 01:15:24 UTC,No logs needed as its a build warning
1758471,2018-04-10 09:30:52 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1758471,2018-03-24 00:57:35 UTC,This only affect Xenial.
1758471,2018-03-24 01:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1758484,2018-03-28 07:59:52 UTC,Thanks for reporting.
1758484,2018-03-28 15:58:15 UTC,I ain't dead yet!
1758487,2018-04-23 02:09:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758487,2019-05-10 00:40:53 UTC,"This is upstream bug https://github.com/keepassxreboot/keepassxc/issues/1574, fixed on https://github.com/keepassxreboot/keepassxc/pull/1906"
1758487,2019-09-07 06:24:09 UTC,Fixed in 2.3.3
1758489,2018-03-24 06:17:08 UTC,kubuntu 18.04 beta 1
1758489,2018-03-30 19:09:53 UTC,I delete all my .local/share directory and the problem disapear.
1758489,2018-04-15 05:25:13 UTC,I have done an other test with the latest upgrade on 04 the 14th.
1758491,2018-05-08 18:15:17 UTC,This change was made by a bot.
1758492,2018-03-25 06:49:09 UTC,"I have done some other tests with filelight.
Filelight gives me the same result that df."
1758492,2018-03-24 06:18:12 UTC,kubuntu 18.04 beta 1
1758492,2018-04-15 05:28:42 UTC,Nobody else ?
1758496,2018-03-24 07:00:07 UTC,This change was made by a bot.
1758496,2018-03-24 06:57:31 UTC,The output of: ls /sys/class/backlight > backlight is nothing
1758496,2018-03-24 07:02:00 UTC,"acpixtract acpidump.txt
iasl -d DSDT.dat"
1758496,2018-03-27 21:17:40 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1758496,2018-04-16 05:41:11 UTC,"When you use ""acpi_backlight=vendor"", is /sys/class/backlight still empty?"
1758496,2018-04-16 08:45:02 UTC,"Yes jsalisbury, this issue started happening after an upgrade. Sorry, I'm not sure ... from 16.10 to 17.4 could be ...
Ok, many thanks. I have not enought time, but I'll try to test the latest upstream kernel."
1758496,2018-04-16 08:52:46 UTC,"Yes kaihengfeng. Now, my GRUB_CMDLINE_LINUX_DEFAULT=""acpi_osi=Linux acpi_backlight=vendor"" and /sys/class/backlight still empty. Today I've updated the laptop and the kernel is 4.13.0-38-generic and the problem still happening."
1758496,2018-04-16 09:07:42 UTC,acpi_osi=Linux is not necessary.
1758496,2018-04-16 11:42:05 UTC,I've test the latest v4.16 with this errors during installation:
1758496,2018-04-16 16:34:53 UTC,"I don't quite understand. If you can't boot under v4.16, how did you test it?"
1758496,2018-04-17 11:42:41 UTC,"Because, the system boot up but it stops and freezes due to problem with (nouveau) graphics. When the system is frozen it still allows me to test the brightness keys. Unfortunately with the frozen system I can not access a terminal or use it in any way.
(Sorry for my painful use of the language ...)"
1758496,2018-04-18 03:56:05 UTC,"I guess you can avoid the issue by using kernel parameter ""nomodeset"""
1758496,2018-04-18 17:43:52 UTC,"Today I reinstalled my laptop with a Ubuntu 17.10 and the system show the same problem. When the first boot finised I looked for the files on the /sys/class/backlight folder but this folder was empty. I changed /etc/default/grub with GRUB_CMDLINE_LINUX_DEFAULT=""nomodeset acpi_backlight=vendor"" as Kaihengfeng said. I ran update-grub and reboot, with the same result; /sys/class/backlight folder is empty. The brightness keys don't work. What can I do?"
1758496,2018-04-19 12:04:07 UTC,"Again, I test the 4.16 kernel with the parameter ""nomodese"". As Kaihengfeng guessed the system boot but the problem still there; /sys/class/backlight folder was empty. My second test was boot again with 4.16 without ""nomodeset"" parameter in the grub file and the results were others. As I expected the system was frozen and in this last test the brightness keys didn't work.
It smells like a problem betwen my firmware and the kernel.
I can do more test to find the problem."
1758496,2018-04-27 07:26:07 UTC,This commit [1] might solve it. Can you git it a try?
1758496,2018-05-04 14:38:48 UTC,"Thanks Kaihenfeng! I try it from [2], but /sys/class/backlight still empty. Ops! ..."
1758496,2018-05-08 05:54:09 UTC,"Please file an upstream bug at https://bugzilla.kernel.org/
Product: ACPI
Component: Power-Video"
1758496,2018-05-12 11:13:39 UTC,Ok! Thanks kaihengfeng! I'll do it.
1758496,2018-06-09 11:47:26 UTC,I file this bug on:
1758497,2018-09-05 20:12:35 UTC,"Just found out that it was caused by files from an old version of font-manager in my home directory (namely .fonts.conf as well as folders under .local, .config and .cache)
Removing .fonts.conf resolved the problem for me."
1758497,2020-07-01 21:02:05 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Closing since one since it sounds like it was a font configuration issue and not one with the pdf viewer
1758497,2018-09-02 06:11:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758499,2018-03-24 07:11:52 UTC,"StacktraceTop:
 g_mutex_lock (mutex=0x0) at ../../../../glib/gthread-posix.c:1343
 g_main_loop_quit (loop=0x7f953c0cf190) at ../../../../glib/gmain.c:4124
 do_call (client=client@entry=0x7f953400d550, call_type=call_type@entry=CALL_TYPE_NAME_VANISHED) at ../../../../gio/gdbusnamewatching.c:219
 call_vanished_handler (client=client@entry=0x7f953400d550, ignore_cancelled=0) at ../../../../gio/gdbusnamewatching.c:245
 call_vanished_handler (ignore_cancelled=0, client=0x7f953400d550) at ../../../../gio/gdbusnamewatching.c:243"
1758499,2018-04-05 14:18:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758512,2018-10-23 07:30:19 UTC,"Fresh Ubuntu 18.04 on Dell XPS13 9360, Intel video - can also reproduce this bug"
1758512,2018-11-06 01:29:23 UTC,Confirmed reproduced on latest Ubuntu 18.04.1.  Switching between terminals with ctrl+alt+f1-7 does not work after initial switch and logout.  Only a blank screen and unresponsive keyboard/mouse which had to be resolved through reboot.
1758512,2019-01-29 06:49:41 UTC,Its' reproducible on AMD Ryzen APU's as well. Can the priority of this be bumped up and someone fix it. This is a basic feature which every Linux distro has.
1758512,2019-02-22 11:45:29 UTC,Also reproduceable on a Lenovo Thinkpad W540. fresh install of Ubuntu 18.04 (Dualboot Windows 10).
1758512,2019-02-23 14:29:25 UTC,I have same bug on ubuntu 18.04. Lenovo G560
1758512,2019-02-25 01:43:40 UTC,"Also affects 'mutter', since I imagine that's the component which must handle the key combo for gnome-shell."
1758512,2019-04-19 21:03:33 UTC,I have same bug on ubuntu. Lenovo B5400.
1758512,2019-07-03 02:41:03 UTC,"Alexander, please see bug 1550779 for that."
1758512,2020-01-28 09:10:04 UTC,"Reproducible on 18.04.3 LTS on a t460s Thinkpad. (Yes, enable function-lock, or remember to press Fn + ctrl + alt + f3)"
1758512,2020-01-28 09:12:26 UTC,"Typo above, the second CTRL-ALT-F1 in the text above should be CTRL-ALT-F3...."
1758512,2020-05-16 14:57:56 UTC,I have the same exact issue on 20.04 LTS. I'm using a Radeon RX 570 GPU. Kernel 5.4.0-29-generic
1758512,2020-07-16 08:29:51 UTC,"I have the same issue on:
* Ubuntu 18.04.4
* Kernel 4.15.0-111-generic
* Thinkpad T480s"
1758512,2020-09-17 00:23:15 UTC,"Here is sit, in 2020, Nvidia, Ubuntu 20.04, SAME issue... as a desktop, full keyboard I have no Fn'b button (lol pun intended). Kernel, 5.4.0-47-generic, Nvidia Driver 450.66 (Game Driver)"
1758512,2020-11-26 04:17:00 UTC,"I can reproduce it but only in:
* GNOME Shell 3.36.4
* KDE Plasma Shell 5.18.5"
1758512,2019-07-02 20:13:19 UTC,"The same problem
Dell Vostro 5648, i5-7200U"
1758512,2018-10-19 20:20:12 UTC,"I too have this problem on multiple computers. Laptops behave the worst.
I tried a temporary work around:
in .bashrc I added:
alias text='systemctl isolate multi-user.target'
alias graphical='systemctl isolate graphical.target'"
1758512,2018-05-07 07:15:34 UTC,Is your Intel machine also running Ubuntu 18.04?
1758512,2018-08-14 20:31:40 UTC,"I also have these problems (and also many other problems since 18.04) on multiple computers.
1 desktop with nvidia drivers and 1080ti
1 laptop with 1070
1 laptop with intel 620 : sometimes after repeatedly typing ctrl+alt+f3 it shows up."
1758512,2018-03-26 02:31:38 UTC,gdm might have Fn lock turned off.
1758512,2018-03-26 08:08:27 UTC,"The ""Fn"" trick did not succeed. The keystrokes with ""Fn"" did not get recognised, these without Fn  (i.e., the standard ones) did as shown below."
1758512,2018-05-05 09:45:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758512,2018-05-05 16:54:09 UTC,What graphics drivers are you using?
1758512,2018-05-07 02:32:07 UTC,Note that Ctrl+Alt+Fn is not a system-wide keyboard shortcut. There's no such thing.
1758512,2018-08-24 02:49:31 UTC,"@raphael-fáistonpc: I have been having this and other GDM3 related issues hitting the laptops I administer and its a showstopper here, too. My current ""solution"" has been to give up on GDM3 and just 'sudo apt install lightdm'. Perhaps that will let your robotics team get back to work without having to chuck all of the latest Ubuntu."
1758512,2018-05-07 06:48:08 UTC,"Further info: I updated my main computer to 18.04. That one has Nvidia graphics (updated to the latest nvidia-390 from PPA). Behaviour is different, but buggy, too, as follows:"
1758512,2018-05-07 06:32:26 UTC,I am on Intel graphics (xps13 i7-4500U HD4400).
1758512,2018-05-07 07:39:06 UTC,"Yes, both are on 18.04."
1758512,2018-05-13 08:18:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758512,2018-05-15 17:18:36 UTC,"I get this bug if I uncoment WaylandEnable=false in /etc/gdm3/custom.conf .
If I use gdm3 with Wayland I get #1764643 instead."
1758512,2018-06-13 17:35:57 UTC,I can confirm that I have the exact same problem in fresh install of ubuntu 18.04 today. Intel graphics here. Very annoying as this pops up just as I decided to upgrade after a period of testing ( where I never noticed this problem.)
1758512,2018-06-14 02:16:17 UTC,"I'm using 18.10 now and have noticed there's sometimes a confusingly long delay for the VT login prompt to appear. It's just a cursor on a black screen for a while, and then suddenly the VT login prompt appears (sometimes)."
1758512,2018-05-07 07:14:40 UTC,gdm3 uses Wayland by default.
1758516,2020-08-10 02:08:52 UTC,python-volatility 2.6-1-xenial1
1758517,2018-03-26 14:19:07 UTC,"I have the exact same core dumps from bamf.
Running Arch linux."
1758517,2018-03-24 10:14:30 UTC,This is bamf 0.5.3-2
1758517,2018-03-26 14:18:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758537,2018-03-25 10:14:02 UTC,https://github.com/quodlibet/mutagen/issues/344
1758537,2018-03-26 17:24:32 UTC,Fixed in master: https://github.com/quodlibet/mutagen/commit/62e4dbb6c3e9268a659030090ff67a1082d2b771
1758537,2018-03-24 15:17:54 UTC,"I thought it might be because 'WXXX' is for freeform url data, so I used a more official frame 'WOAS'.  The frame name wasn't munged, but the value was:"
1758537,2018-03-24 16:00:33 UTC,"Thanks, that looks like a bug."
1758542,2018-03-24 15:27:36 UTC,"StacktraceTop:
 ped_assert (cond_text=cond_text@entry=0x7fe909814d1a ""num > 0"", file=file@entry=0x7fe909814e18 ""../../../libparted/labels/mac.c"", line=line@entry=975, function=function@entry=0x7fe909815250 <__PRETTY_FUNCTION__.5253> ""_generate_raw_freespace_part"") at ../../libparted/debug.c:111
 _generate_raw_freespace_part (geom=0x7fe8fc06b6d8, geom=0x7fe8fc06b6d8, part_map=0x7fe8fc043000, num=0, disk=0x7fe8f006bba0) at ../../../libparted/labels/mac.c:975
 mac_write (disk=0x7fe8f006bba0) at ../../../libparted/labels/mac.c:1102
 ped_disk_commit_to_dev (disk=disk@entry=0x7fe8f006bba0) at ../../libparted/disk.c:501
 disk_commit (disk=disk@entry=0x7fe8f006bba0, path=path@entry=0x7fe8fc096f70 ""/dev/sdc"", error=error@entry=0x7fe90b3d7580) at part.c:253"
1758542,2018-03-28 14:27:22 UTC,the segfault is in libparted
1758542,2018-09-14 15:09:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758542,2018-09-14 15:17:03 UTC,udisksd crashed when I tried to enlarge the EFI partition.
1758543,2020-07-21 15:11:16 UTC,"Fix released, probably with some 2.2.x version."
1758545,2018-09-06 14:40:39 UTC,"Is there any chance you can find a page in your bios like the one I've attached and post it? For me I hit f12 (boot device  select), device configuration, amd pbs, and firmware version. I'm having an identical issue with my dell Inspiron 7375 and an Intel 7260 and am curious if I can expect a fix from dell sometime soon."
1758545,2018-08-16 01:25:15 UTC,"After updating the BIOS to version 6KCN30WW, finally this bug is gone away."
1758545,2018-05-10 21:26:13 UTC,"It's not caused by WiFi card. As I understand, this error is produced by AMD Ryzen2200 processor. I have the same problem too."
1758545,2018-05-02 18:30:23 UTC,"I would like to say, that I also have this problem. But i don't run Ubuntu. I have the exact same hardware, but I have updated the BIOS to the newer version provided by Lenovo."
1758545,2018-03-26 04:56:05 UTC,"The error is from your wifi cards. That said, it's more like to be a compatibility issue between your Ryzen PCH and Intel 8265. Generally this should get fixed by system firmware (i.e. BIOS).
Please contact Lenovo for their support."
1758545,2018-03-26 05:32:05 UTC,"Thanks Kai-Heng, I think the error comes from  Wifi card and NVME ssd drive, both of them installed on PCIE slot. Anyway, do you mean there is no hope except Lenovo will issue a firmware? That's sad. My laptop is not supported by official,really sad."
1758545,2020-01-11 10:41:55 UTC,"I can also report the same behavior, on a Clevo laptop running Ubuntu 20.04 (development version), kernel 5.3.0-24. Clevo does not currently provide BIOS updates for this model, and it is unlikely that they ever will."
1758545,2018-03-24 16:00:06 UTC,This change was made by a bot.
1758545,2018-03-26 05:44:32 UTC,There's new BIOS update for the laptop. Give it a try first.
1758547,2020-04-01 13:32:56 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1758547,2018-03-25 03:23:18 UTC,Oh! It's true that it works with the color palette. But I normally disable the color palette to save screen space. My Bad.
1758547,2018-03-24 18:48:11 UTC,I usually select a tool and then click a color in the palette... verifying in the upper right corner above the snaps that the color is selected.  Will this work for you?
1758548,2018-09-01 11:46:12 UTC,Kovid:
1758548,2018-09-02 03:02:28 UTC,The only way this can possibly happen is if the calibre library is on a broken filesystem such as a network share or a folder shared using a file sync service such as dropbox/gdrive/etc.
1758548,2018-10-07 14:37:12 UTC,"Yeah, I risk my data with broken ass applications like Calibre all the time. That is why I have Gdrive as a backup. Get real."
1758548,2018-09-02 23:37:49 UTC,"Thanks for the fast reply, Kovid. :)"
1758548,2018-09-03 11:38:00 UTC,"Hello everyone,"
1758548,2018-09-03 15:01:54 UTC,"Hi Freikland,
Yes, I think that is a great approach. :)
He did mention a ext4 file system but try your ext3 file system and see if that works."
1758548,2018-09-01 11:40:43 UTC,"Hi Freikland,
Thanks for the epub book to test on. I have tried it on my computer and am not able to replicate the problem. That is OK.
I believe there is enough information now and I have sent it to the programmers. For their ease, I will re-post the summary.
Thanks again for your patience
:)
G"
1758548,2018-09-03 15:19:29 UTC,ext3 is fine.
1758548,2018-10-06 08:55:38 UTC,"I've had this same issue in a 2.x version and now 3.30 version of Calibre. I'm running this on Debian 9 (LMDE3) and it appears that the Insync Google Drive synchronization tool causes/contributes to this issue. In other words, when Insync is paused, and I edit the Author field of any file (which changes the folder name of where the files reside) then there is no problem, but when Insyc is active, both the cover and the file disappear (are not in the Trash nor elsewhere in the folder structure)."
1758548,2018-10-06 11:05:01 UTC,"Hi Jeff. Thanks for the update. As Kovid indicates, if you make sure your libray is stored on your hard drive, the issue is resolved.
Take care
:)
G"
1758548,2018-10-06 11:25:11 UTC,"Hi G,"
1758548,2018-10-07 07:47:52 UTC,"filesystems have no concept of atomic operations. You cannot have
multiple software accessing the same set of files at the same time and
expect things to magically work. If you put your calibrelibrary on a NAS
or a folder that is modified by other software, things *will* break."
1758548,2018-10-07 13:13:11 UTC,"Actually, every other piece of software I use has no problem with being synched to gdrive. Calibre is the only thing that breaks. Clearly this has to do with a difference in the way Calibre functions, rather than NAS or file synchronization operations. Everything else is quite robust, including about a dozen file and media editors, from Libre Office, to video, audio, and image editors, to a variety of file editors, to KeePassXC. No one else complains about these file sync utilities or NAS drives, or has worked around any issues. Things do magically work, though not unfortunately for Calibre."
1758548,2018-10-07 13:29:06 UTC,"Because all of those utilities are editors, that work on one file at a
time. Anyway, I dont really care whether you believe me or not. File
systems are not atomic, that is a fact. Waving your hands and saying X,
Y or Z magically work, just means that you have been lucky enough to
avoid running into a situation where they will not work so far."
1758548,2018-09-03 17:11:25 UTC,"Thanks for yhe clarification, Kovid! That's good to know.
:)
G"
1758548,2018-09-01 11:34:12 UTC,Searched for duplicates of this bug - found none
1758548,2018-08-31 20:47:50 UTC,"Thanks for your reply, Freikland.
Just to clarify, when you change the case on the title or author name, are you typing the edits manually on the keyboard?"
1758548,2018-09-01 01:20:59 UTC,"Hi Freikland,
Thank you for your patience on this issue."
1758548,2018-07-29 20:20:48 UTC,"Hello Freikland,
Thank you for submitting this bug and reporting a problem with Calibre.  You made this bug report some time ago and Ubuntu and Calibre have been updated since then."
1758548,2018-09-01 06:42:29 UTC,"Hi gf,"
1758548,2018-08-24 11:40:18 UTC,"Hello Freikland,
Thanks for the reply."
1758548,2018-08-24 16:43:08 UTC,"Hello,"
1758548,2018-08-25 01:02:11 UTC,"Hello Freikland,
Thanks for the reply.
Are you using special characters in the new name of the book?
For example, are you using any of these:  è, é, ê, ë
Thanks"
1758548,2018-08-25 01:13:49 UTC,"Hello again, Freikland,
I found this other bug report regarding French characters and the AZERTY keyboard. Will you go to that bug report and see if it answers your question and solves the problem?"
1758548,2018-08-24 05:40:47 UTC,"Hello,"
1758548,2018-08-25 13:06:40 UTC,"Thanks Freikland, for the extra steps and details. That helps clarify the problem to upper case or lower case on the title or author name."
1758548,2018-08-25 14:56:33 UTC,"I edit only the information in the ""Title"" and ""Author"" boxes. I'm using others (sorting) only to check colors, green or red."
1758548,2018-08-31 14:14:17 UTC,"Hi Freikland,
You have had Calibre 3.30 for a week. Can you tell me if the problem occurs in that new version?"
1758548,2018-08-31 19:22:53 UTC,"Good evening,"
1758548,2018-08-31 20:50:59 UTC,"Hi again Freikland,
I also found on this website, several people having difficulty with the capitalization of the words in the title, in Calibre, due to different languages.
It does not solve your problem but I just thought I would send you the link, for your information:"
1758548,2018-08-31 22:18:54 UTC,"Hi gf,"
1758548,2018-08-25 05:49:54 UTC,"Hi,"
1758551,2019-06-28 04:51:49 UTC,"Updating this 'bug' in snap versions of gnome-calculator, gnome-characters and gnome-system-monitor: I recently noticed..."
1758551,2018-03-24 16:43:57 UTC,This issue is being tracked by the Ubuntu Desktop Team at
1758551,2018-03-24 16:18:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1758553,2019-07-27 17:56:24 UTC,"The serialisation is done by libxml2. defs.py is mostly used by the cleaner and for informational purposes, not for serialisation."
1758553,2019-03-08 07:23:31 UTC,"Implemented here:
https://github.com/lxml/lxml/commit/1e6007745376593cd10ca2389aa6bc406f72f630"
1758553,2019-07-27 17:15:11 UTC,Hey!
1758553,2019-07-27 18:21:38 UTC,"Thanks, I will push a similar fix to libxml2 then!"
1758555,2018-03-27 01:24:39 UTC,"Hello, I've opened a new bug at https://gitlab.gnome.org/GNOME/librsvg/issues/236"
1758560,2018-03-26 12:49:59 UTC,"Hello,"
1758560,2018-03-24 20:30:29 UTC,"Hi Jillian,"
1758563,2018-03-27 17:07:10 UTC,"Hi, I made some more testings."
1758563,2018-03-27 02:29:36 UTC,Please elaborate about how step 3 failed. Please also try it again with a very simple password.
1758563,2018-03-26 05:23:40 UTC,"Hi, I'm not sure this is an exact duplicte of bug 1716159 (I saw it before reporting here). It's right, today I checked, if I enter û in the gdm login field, it writes u, but :"
1758563,2018-03-26 06:57:03 UTC,I have just documented a possible workaround in bug 1716159. Please try that.
1758563,2018-03-26 12:50:12 UTC,"Thanks, I already did that the first time I was blocked on login screen, it failed at step 3 : unable to connect after changing passwd in recovery..."
1758563,2018-03-28 10:45:41 UTC,"Current 18.04, on gdm login field, if I type : € # $ @ ù é they are well and correctly written."
1758563,2018-03-28 11:55:21 UTC,"That looks like that gnome-shell regression, https://gitlab.gnome.org/GNOME/gnome-shell/issues/115 which has been fixed upstream and should be fixed when we update to 3.28.1"
1758563,2018-04-11 16:33:48 UTC,This affects me as well. I am using:
1758563,2018-04-17 10:24:22 UTC,Yep. GNOME Shell 3.28.1 fixed this issue for me.
1758563,2018-04-24 15:59:05 UTC,"I am running the latest beta of 18.04 with upgrades. Since installation I try to log in the gdm screen and receive the message, ""Sorry, that didn't work. Please try again."" I get the same message when I try to log in to Update Manager. The app and gdm screen launch if I enter my password again."
1758563,2018-04-26 01:55:05 UTC,"Bob, I think you want bug 1765261, not this one."
1758563,2018-03-26 02:10:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1716159, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1758564,2020-04-05 13:33:44 UTC,"This will be fixed in the new upstream project under:
https://github.com/gnome-terminator/terminator/pull/6"
1758564,2019-05-09 02:35:09 UTC,I'm on Terminator 1.91-1 and Ubuntu Linux 18.10 (cosmic) and had the same issue.
1758564,2019-04-10 06:45:31 UTC,"Unfortunately, the same solution does not apply to the current version of Terminator: 1.91-4"
1758564,2019-02-06 19:20:05 UTC,"Changed to reflect VTE version 0.52
1. Delete terminator/terminatorlib/plugins/custom_commands.pyc to force re-compilation at next run time."
1758564,2018-05-03 13:52:43 UTC,This bug is also happening on Fedora 28: https://bugzilla.redhat.com/show_bug.cgi?id=1573927
1758564,2018-04-10 21:37:29 UTC,I confirm this bug is happening on Arch Linux package as well:
1758564,2018-03-24 19:05:15 UTC,"For Kali distros the terminator files that need to be changed are located at:
/usr/share/terminator/terminatorlib/plugins"
1758564,2018-03-24 19:02:37 UTC,1. Delete terminator/terminatorlib/plugins/customer_commands.pyc to force re-compilation at next run time.
1758564,2018-08-03 10:11:19 UTC,"VTE version 0.52 fixed its Python binding of feed_child(), no longer taking that third parameter."
1758572,2020-07-18 21:01:10 UTC,Can this be reproduce with the latest Mono installer? https://www.mono-project.com/download/stable/
1758581,2018-03-27 10:40:55 UTC,"Hi again,"
1758581,2018-03-28 18:08:04 UTC,"> I think I will do with thisconfiguration waitin for a HPLIP update...
"
1758581,2018-03-27 14:10:58 UTC,"Hi Yann,"
1758581,2018-03-27 11:23:35 UTC,Thanks do you have any idea about when it is solved?
1758581,2018-03-27 11:00:06 UTC,"Hi LE BARS,"
1758581,2018-03-27 10:06:05 UTC,"Hi LE BARS,"
1758581,2018-03-28 07:03:43 UTC,"Hi Brian,"
1758581,2018-03-27 09:45:03 UTC,"Hi Brian,"
1758581,2018-03-27 09:29:14 UTC,"Hi LE BARS,"
1758581,2018-03-26 18:52:06 UTC,"Hello LE BARS,"
1758581,2018-03-26 08:29:23 UTC,"Hello Brian,"
1758581,2018-03-25 19:07:25 UTC,"Would you please explain in detail what you mean by ""recto verso""? How does it differ from ""duplex""?"
1758581,2018-03-27 09:46:12 UTC,"Hi Afshan,"
1758586,2018-03-24 22:37:21 UTC,I would guess there was a mistake setting the sound name in this upstream change quite some time back:
1758586,2018-03-26 06:41:15 UTC,In: https://cgit.kde.org/kteatime.git/commit/src/kteatime.notifyrc?id=305b9e74bba43724f368a5446a9787ffb3b293c3
1758586,2018-03-26 09:13:48 UTC,Yep the file doesn't exist.  Pick another sound file to replace it with.
1758586,2020-05-30 20:14:04 UTC,https://invent.kde.org/utilities/kteatime/-/merge_requests/1/diffs?commit_id=74da1c26169ad56d895775f124e65415eb30cd6d
1758586,2020-07-04 11:58:36 UTC,"Git commit f89cde574f0c7c8b80fe729e1168d7ccb74d04ba by Martin Tobias Holmedahl Sandsmark, on behalf of Martin T. H. Sandsmark.
Committed on 04/07/2020 at 11:58.
Pushed by sandsmark into branch 'master'."
1758589,2018-03-27 00:54:39 UTC,apport information
1758589,2018-03-27 00:54:40 UTC,apport information
1758589,2018-03-27 00:54:41 UTC,apport information
1758589,2018-03-27 00:54:42 UTC,apport information
1758589,2018-04-26 06:41:34 UTC,"iwl3945 has choppy powersaving support. Please see if disabling it can help.
This gist [1] shows how to do it."
1758589,2018-03-27 00:54:45 UTC,apport information
1758589,2018-03-27 00:54:47 UTC,apport information
1758589,2018-03-27 00:54:48 UTC,apport information
1758589,2018-03-27 00:54:38 UTC,apport information
1758589,2018-04-26 14:20:30 UTC,"OK, @Kai-Heng Feng, thank you for suggestions! I will have a try, and report the result after about one week, do you think it is OK?"
1758589,2018-03-27 00:54:43 UTC,apport information
1758589,2018-03-27 00:54:36 UTC,apport information
1758589,2018-03-27 00:54:30 UTC,apport information
1758589,2018-03-27 00:54:33 UTC,apport information
1758589,2018-03-27 00:54:32 UTC,apport information
1758589,2018-03-27 00:54:31 UTC,apport information
1758589,2018-03-27 00:54:29 UTC,apport information
1758589,2018-03-27 00:54:25 UTC,apport information
1758589,2018-03-27 00:54:23 UTC,apport information
1758589,2018-03-27 00:54:22 UTC,apport information
1758589,2018-03-27 00:54:21 UTC,apport information
1758589,2018-03-27 00:54:20 UTC,apport information
1758589,2018-03-26 05:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1758589,2018-04-26 14:42:52 UTC,Should be good.
1758589,2018-03-27 00:54:34 UTC,apport information
1758589,2018-06-19 02:11:20 UTC,"@Kai-Heng Feng, seems that your solution should be OK. Thank you for your help!"
1758589,2018-03-27 00:54:35 UTC,apport information
1758596,2018-03-27 10:40:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758602,2018-12-11 15:30:50 UTC,https://specs.openstack.org/openstack/api-wg/guidelines/http/caching.html is the OpenStack project's guidance on what should be done regarding http caching (and should be done in each project)
1758607,2018-12-06 08:02:56 UTC,I agree with changing this and I think we should set the default to 10 or 15 minutes.
1758607,2019-02-12 19:45:02 UTC,"Likewise, supporting an arbitrarily large interval/retry combination (within reason) would be helpful. A customer ran into this timeout after 186s in a cloud with an 80GB Windows image."
1758607,2019-06-28 08:44:54 UTC,Does the charm have to expose block_device_allocate_retries directly or can we make it friendlier such that the charm user can indicate timeout in seconds rather than have to compute it in their head via block_device_allocate_retries and block_device_allocate_retries_interval?
1758607,2019-06-28 09:17:19 UTC,"As long as the config description has mentions to block_device_allocate_retries and block_device_allocate_retries_interval to give an idea of upstream config values, friendlier config name would be nice to have."
1758607,2019-07-03 15:09:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668933"
1758607,2019-07-04 05:20:18 UTC,The preceding proposed fix now exposes block_device_allocate_retries_interval and block_device_allocate_retries as configuration options for the charm.
1758607,2019-07-04 06:19:09 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669060"
1758607,2019-07-04 06:21:57 UTC,For clarity:
1758607,2019-08-21 05:50:49 UTC,"I would love to see a fix for this merged, including an increased default as it's a common problem to need to increase this. Not only for large images, but also when deploying multiple VMs at once as multiple images copying at once are often converted through the root disk of the cinder node, and can bottleneck on slower root disks."
1758607,2020-06-05 20:03:07 UTC,I just hit this problem in a lab environment with every openstack component virtualised in VMs on one baremetal machine. It's a low performance environment. I put block_device_allocate_retries = 300 and block_device_allocate_retries_interval = 3 and it worked for me.
1758607,2018-12-11 05:39:25 UTC,Recently hit in 2 production environments when deploying Windows images.. Even 240 is not enough.
1758620,2018-03-25 07:00:06 UTC,This change was made by a bot.
1758620,2018-03-28 20:29:08 UTC,"Installed, tested upstream kernel v4.16-rc7 generic."
1758620,2018-04-20 16:59:56 UTC,"Don't know if this is relevant to this bug but the following sequence of events almost always happens when I wake from ""Suspend"":"
1758620,2018-03-27 21:15:46 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1758621,2018-05-08 18:45:07 UTC,apport information
1758621,2018-05-08 18:45:21 UTC,apport information
1758621,2018-05-08 18:45:18 UTC,apport information
1758621,2018-05-08 18:45:13 UTC,apport information
1758621,2018-05-08 18:45:10 UTC,apport information
1758621,2018-05-08 18:45:05 UTC,apport information
1758621,2018-05-08 18:45:03 UTC,apport information
1758621,2018-05-08 18:45:00 UTC,apport information
1758621,2018-05-08 18:41:26 UTC,apport information
1758621,2018-05-08 18:45:25 UTC,apport information
1758621,2018-05-08 18:41:24 UTC,apport information
1758621,2018-05-08 18:41:17 UTC,apport information
1758621,2018-05-08 18:41:14 UTC,apport information
1758621,2018-05-08 18:41:11 UTC,apport information
1758621,2018-05-08 18:41:08 UTC,apport information
1758621,2018-05-08 18:41:05 UTC,apport information
1758621,2018-05-08 18:41:02 UTC,apport information
1758621,2018-05-08 18:15:32 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1758621,2018-04-27 15:06:53 UTC,Just tested again on new Ubuntu 18.04 with kernel 4.15. The direct synchronous small 4K write performance is still slower than kernel 4.4 on Ubuntu 16.04.
1758621,2018-05-08 18:41:20 UTC,apport information
1758623,2018-04-26 17:05:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758625,2021-01-07 04:05:04 UTC,4.8 EOL
1758625,2018-05-08 18:15:43 UTC,This change was made by a bot.
1758632,2020-02-05 17:33:37 UTC,"Having a look into what the package installs, .otf versions of the fonts are present, so this bug should be fixed already."
1758639,2018-08-11 16:26:43 UTC,Is this https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1696790?
1758642,2019-08-27 05:44:35 UTC,"This bug is still present in 16.04, but seems to be fixed in 19.04. I don't see an explicit commit for it though, which makes me wonder if it's a memory corruption issue in the GTK layer."
1758651,2018-03-25 12:32:08 UTC,"StacktraceTop:
 mieqProcessDeviceEvent (dev=0x5570388b4a10, event=0x7fef5f3e8010, screen=0x557037facf60) at ../../../../mi/mieq.c:438
 ProcXTestFakeInput (client=0x557038aba680) at ../../../../Xext/xtest.c:429
 Dispatch () at ../../../../dix/dispatch.c:479
 dix_main (argc=12, argv=0x7fff0eccf928, envp=<optimized out>) at ../../../../dix/main.c:287
 __libc_start_main (main=0x557037a1baa0 <main>, argc=12, argv=0x7fff0eccf928, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff0eccf918) at ../csu/libc-start.c:310"
1758651,2018-03-30 14:25:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758651,2018-06-01 07:36:48 UTC,"Tracking in:
https://errors.ubuntu.com/problem/9ce363e7fa4057cf260e93ab2c1dc7193cde9970"
1758651,2018-07-27 03:46:03 UTC,"Video showing the problem: https://youtu.be/TYMBOmLgPHI
The exact same thing happens 30% of the times I close/open the lid of my laptop."
1758653,2018-04-26 01:30:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758653,2018-04-06 01:59:21 UTC,"Manually creating that subdir can be done, and then that error is gone"
1758653,2018-04-27 19:47:21 UTC,"I had that bug with a fresh install of released Ubuntu 18.04. I installed ""samba-common-bin"" and that error went away."
1758653,2018-11-22 23:34:17 UTC,"Oddly enough, this problem started for me after I mounted a NFS volume using autofs."
1758671,2018-04-08 08:13:10 UTC,"Sure, no rush. Just put it on the list of minor things to add when 2.1 stabilizes."
1758671,2018-04-07 10:58:56 UTC,Elaborating on filing request (partly repeating what was already said):
1758671,2018-03-29 22:47:32 UTC,"I see your point, that option would follow the Tango design idea to hide unused and distracting controls. Does the vc toggle really distract you? It is so tiny and unobtrusive compared to other controls like the mixer or the waveforms where hiding makes much more sense.
I never used vinyl control, I just need Passthrough every now and then (which is also the reason vc is expandable per-deck) and I don't notice that button."
1758671,2018-04-07 12:27:29 UTC,"Yes, with default On this works like before.
Don't get me wrong, I'd implement it, just not now. I'm pretty sure other issues will pop up after the release. I'd appreciate to collect those and fix them at once."
1758671,2018-03-25 18:34:52 UTC,Did you try the button next to overview? It expnads vinyl controls per deck.
1758671,2018-03-26 08:31:51 UTC,"Yes, I understand vinyl control can be collapsed / uncollapsed. But since almost all other UI elements in the deck can be hidden, why not allow hiding vinyl control? If users are not using vinyl control, even collapsed state adds no value to the UI in their use-case."
1758681,2019-03-13 18:51:54 UTC,I have the same problem since about two days ago although it worked fine before... Did you find a solution to this ?
1758681,2019-03-13 18:52:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758683,2018-03-28 08:12:07 UTC,"Dear Sasha,
thanks for reporting this.
Admittedly, that part of the package was never meant to be rock solid, and hasn't been
tested with different root versions, or with large files. Thus, in this case it is not
suprising that it doesn't work well.
In spite of being the original author of that piece of code, I can't remember why hadd
was not deemed a viable option. Maybe it was simply due to my poor understanding of root.
I'll investigate as soon as I'll have some time. In the meanwhile, I have nothing against
you using hadd, but I strongly suggest to test its results against those of the standard
package in a few cases where the latter is supposed to do well, and which are quick to run.
Best, Stefano."
1758683,2019-05-17 09:46:00 UTC,"Hi,"
1758683,2019-06-29 19:42:43 UTC,"Hi Olivier,
I did some modification of Template/NLO/SubProcesses/combine_root.sh, please find attached the diff file.
Let me know if you will have further questions.
Cheers,
Sasha."
1758683,2019-06-29 19:44:50 UTC,Forgot to mention: this diff is created using MG5_aMC_v2_6_0
1758683,2019-07-03 07:51:07 UTC,Thanks so much for this.
1758685,2018-03-27 22:05:44 UTC,"According to this, apparently it is not advisable to use both lines at the same time:
https://devtalk.nvidia.com/default/topic/828962/screen-tearing/"
1758685,2018-04-30 12:19:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758685,2018-05-03 22:22:05 UTC,"Are there any other side effects as a result of using __GL_YIELD=""USLEEP"" or KWIN_TRIPLE_BUFFER=1? Will tearing be prevented on all connected monitors? Is there a performance hit?"
1758686,2018-04-17 04:36:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758686,2018-03-25 15:25:56 UTC,"StacktraceTop:
 g_assertion_message () from /tmp/apport_sandbox_weslljal/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message () from /tmp/apport_sandbox_weslljal/lib/x86_64-linux-gnu/libglib-2.0.so.0
 caja_file_operation_complete (op=0x55c325a07170, result_file=0x55c325a07000, error=0x0) at caja-file.c:1680
 rename_callback (source_object=0x7efe70022360, res=0x55c3241eae00, callback_data=0x55c328ebfe50) at caja-file.c:1781
 ?? () from /tmp/apport_sandbox_weslljal/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0"
1758697,2018-08-10 06:13:08 UTC,"See attachments for current thinking - I'd want the tuning of the devices to be independent of the charm code, so having a systemd unit that runs after block device udev processing seems to make sense to me."
1758697,2018-08-10 05:02:04 UTC,I've just spent the last hour scratching my head as to the best way to tune bcache devices via the charms; I wanted to take and approach where only devices presented to the charm where tuned; my first thought was to use tmpfiles.d to persist the cache settings however that's not going to be reliable with bcache due to the fact the bcache device naming is not consistent between reboots in systems with multiple bcache devices - which in this case is very likely.
1758697,2018-04-03 12:49:59 UTC,+1 to having the charms do this; we turn off sequential cutoff wherever we use bcache.
1758697,2018-03-25 16:35:11 UTC,https://www.kernel.org/doc/Documentation/bcache.txt
1758697,2018-03-26 15:45:08 UTC,2018年3月26日(月) 23:20 Ryan Harper <email address hidden>:
1758697,2018-03-26 14:12:20 UTC,"I think the priority would be for any config that is required during the initial creation; other settings can be configured via scripts or other tuning mechanism.  The cutoff, for example isn't something curtin should do by default ,rather it's a knob for benchmarking.  I'd think the benchmark test would set and clear that as needed."
1758697,2018-04-03 12:45:43 UTC,"I've subscribed two charms that are hit the most by this. Both Nobuto and Ryan are right. It's a in-flight option and charms should handle this. Charm should be intelligent enough to realize that OSD/ephemeral block device is bcache and, especially in Ceph OSD case, that sequential cutoff should be disabled."
1758698,2018-03-25 16:40:04 UTC,"StacktraceTop:
 sk_addr_free (addr=0x2400000002fd) at unix/uxnet.c:477
 net_select_result (fd=<optimized out>, event=<optimized out>) at unix/uxnet.c:1443
 select_result (fd=<optimized out>, fd@entry=13, event=event@entry=2) at unix/uxsel.c:123
 fd_input_func (source=<optimized out>, condition=<optimized out>, data=<optimized out>) at unix/gtkcomm.c:89
 g_main_dispatch (context=0x562be2460130) at ../../../../glib/gmain.c:3177"
1758698,2021-02-09 19:32:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758710,2018-03-26 19:41:06 UTC,"The container controller should always set the query param format=json [1], which will (should?) override any Accept headers -- and we see that in that first line from your proxy-server log:"
1758710,2018-03-27 07:25:59 UTC,"In my opinion, the problem in code, we make requests and expects that response will be in json format, but we do not inform server that we expect response as json.
I have prepared patch, to fix this: https://review.openstack.org/#/c/556277/1"
1758710,2018-04-01 14:42:26 UTC,swift-get-nodes /etc/swift/container.ring.gz AUTH_42859d61583d48b7aead939fb39cb898/test
1758710,2018-09-22 11:55:42 UTC,any updates on this?
1758710,2018-10-15 09:02:20 UTC,"Can anybody review the patch, the problem is actual for our installation.
if there is issue in configuration, how to fix it without modification of code?"
1758710,2018-10-15 09:11:41 UTC,"python-swiftclient                 3.6.0
swift                              2.19.0"
1758712,2018-03-29 00:30:08 UTC,I think I had this already in my list... I'll fix it soon.
1758712,2018-04-10 19:28:58 UTC,"This fix has to be done inside gnome-builder itself, as it provides a way to define custom theming for various styles [1], and it can't be overridden at theme level. Being gnome-builder in universe I think we can lower this issue and not really something critical for release."
1758715,2018-04-10 02:30:16 UTC,not sure how to react :)
1758715,2018-04-09 23:30:06 UTC,"See
  https://specifications.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html
for the full list of named icons"
1758715,2018-04-09 23:29:40 UTC,"Actually it might be easier to just used named icons from the icon theme:
- 'format-text-direction-ltr'
  The icon for the left-to-right text formatting action.
- 'format-text-direction-rtl'
  The icon for the right-to-left formatting action."
1758715,2018-04-10 13:35:55 UTC,As Af:
1758715,2018-04-09 22:45:46 UTC,I like these.
1758715,2018-04-09 22:46:29 UTC,"(it should be possible by just using a web browser, no command line skills required.)"
1758715,2018-03-26 02:29:49 UTC,Would you like to suggest two new icons that fit with the icon sets that Inkscape provides?
1758715,2018-04-09 23:50:29 UTC,"Oh :-o - I'm so sorry, As Af !!!"
1758715,2018-04-08 09:49:32 UTC,"sure,
here are the icons I drew now"
1758717,2018-08-30 14:57:20 UTC,"Have a slightly different problem in 18.04, window width isn't the problem, it's the height. When attempting to create a new basket, the dialog window is too big vertically. The top where the text needs to be entered to name the new basket is hidden behind the top bar. Using Alt-F8, Alt & mouse drag or Alt-Space allows resizing of the horizontal width from its default (fairly wide) size to the full width of the screen and vice versa, but the height cannot be changed. Needed to ""killall basket"" to get the screen back."
1758719,2018-03-25 18:49:01 UTC,got a lot of xruns from lmms to but that maybe a matter of soundcard performance
1758719,2018-03-25 18:58:44 UTC,Opening and closing zynaddsubfx makes lmms freeze and glitch for 1 sec
1758726,2018-04-08 12:15:01 UTC,"This problem I was having after waking up from suspend to RAM. Every time I wake up the machine from sleeping to RAM I get the following message:
""Gestor de ventanas KWin
Desktop effects were restarted due to a graphics reset"""
1758726,2018-04-11 12:35:05 UTC,"Ok, blinks/flickers problem continue some times after wake up the PC, albeit less frequently."
1758726,2018-04-13 23:03:41 UTC,"This is the report related to KDE. Workaround in comment 15:
https://bugs.kde.org/show_bug.cgi?id=385324"
1758753,2018-04-03 15:42:41 UTC,"That is, since https://git.launchpad.net/autopkgtest-cloud/commit/?id=fc15307f5d24158d614ee009430a207cc015f567 we get stderr output mailed out via cron instead of logged"
1758753,2018-04-03 15:40:13 UTC,"I turned off debugging for this script the other day, so the log file isn't really growing any more."
1758754,2018-06-08 03:31:44 UTC,"Reviewed:  https://review.openstack.org/573478
Committed: https://git.openstack.org/cgit/openstack/zun-tempest-plugin/commit/?id=fb75b5e3f9c984577567679115758b1103b6d919
Submitter: Zuul
Branch:    master"
1758754,2018-06-08 01:59:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/573478"
1758754,2018-03-25 21:44:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/556306"
1758756,2018-03-27 21:07:50 UTC,"I think that the problem is in the file /usr/share/themes/Breeze/gtk-3.20/gtk3.css and gtk-dark.css, lines 3634-3640:"
1758756,2018-06-18 14:59:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758756,2020-03-02 19:48:58 UTC,"I had the same issue on Kubuntu 18.04.4, but I was able to overcome it by disabling the window style under appearance (Disable CSD). See attached screenshot."
1758764,2018-07-26 03:06:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758765,2019-03-22 14:58:17 UTC,Hey Tom is this still occurring with Tempest plugin?
1758765,2019-09-27 20:29:44 UTC,"This job was removed in favor of manila-ui-dsvm, which is now in-tree, which does not face this problem. Please feel free to re-open in case you see this again."
1758772,2018-03-26 04:19:49 UTC,"The attachment ""Updated .jar file"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1758772,2018-03-26 06:56:22 UTC,"Note that packaging JabRef for Ubuntu needs more work than just adding the JAR file. In short: This is because Debian's strong policy regarding code provenance. For instance, in ArchLinux, this is different (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jabref). However, they cannot say which source code went into that jar. For more information see https://wiki.debian.org/ReproducibleBuilds."
1758772,2020-05-04 06:42:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758774,2018-12-04 18:28:11 UTC,pytrainer still doesn't work in Ubuntu 18.10.
1758774,2018-05-05 13:27:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758775,2018-03-26 01:37:50 UTC,I intend to integrate a fix for this with the work to enable chrony support for bionic.
1758775,2018-03-27 15:31:23 UTC,"I saw the same problem on GCE instances after reboot:
/usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /var/lib/ntp/ntp.conf.dhcp -u 112:116"
1758775,2018-03-27 23:38:56 UTC,Just restarting ntp may not fix this; it's recommended to touch /etc/ntp.conf before doing so.
1758775,2018-10-05 07:34:25 UTC,Indeed got hit by this bug today on GCE.
1758775,2019-08-01 23:25:49 UTC,"This is actually LP: #1823098. I don't think this is a charm problem, I mean, it could touch ntp.conf on update-status hook but that's ugly."
1758775,2019-08-02 08:41:14 UTC,"I don't think this is really the same problem.  The init script for NTP is designed to honour the settings provided by the DHCP client.  In most cases, this is expected, but when the charm is configured, users expect the charm to manage the local settings for them without needing to override the DHCP client.  I think the preferred solution would be for the charm to disable the DHCP client from modifying the NTP configuration by removing ""ntp-servers"" from the ""request"" entry in /etc/dhcp/dhclient.conf."
1758775,2019-10-28 04:45:46 UTC,"Even with removing 'ntp-servers' from /etc/dhcp/dhclient.conf, /var/lib/ntp/ntp.conf.dhcp is written out. Steps to reproduce:"
1758775,2019-10-28 04:46:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758800,2018-03-28 10:20:13 UTC,Please also set status for main linux task (Bionic) will the change be needed there or is (or will) it included already.
1758800,2018-03-28 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1758800,2018-04-09 12:49:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1758800,2018-04-10 09:32:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1758800,2018-04-23 09:21:59 UTC,This bug was fixed in the package linux - 4.13.0-39.44
1758800,2018-04-23 12:52:04 UTC,This bug was fixed in the package linux-oem - 4.13.0-1024.27
1758802,2018-06-17 02:58:49 UTC,"neutron vpn run as l3 extenstions now
https://bugs.launchpad.net/kolla/+bug/1753617"
1758819,2018-11-07 17:15:40 UTC,"I am also able to reproduce this bug. The problem is that when hvf is enabled, qemu will attempt to execute the xgetbv instruction, which isn't supported on my processor (Intel Xeon X5670)."
1758819,2019-04-21 18:35:36 UTC,According to the response here: https://<email address hidden>/msg572220.html
1758819,2020-11-24 16:23:49 UTC,Looking through old bug tickets ... Did you ever send your patch to the qemu-devel mailing list? See https://wiki.qemu.org/Contribute/SubmitAPatch for more information
1758819,2018-03-31 20:54:46 UTC,Disregard the above log; that was from a September 2017 build.
1758819,2018-03-31 20:51:34 UTC,"Process:               qemu-system-x86_64 [6330]
Path:                  /Users/USER/*/qemu-system-x86_64
Identifier:            qemu-system-x86_64
Version:               0
Code Type:             X86-64 (Native)
Parent Process:        bash [1558]
Responsible:           qemu-system-x86_64 [6330]
User ID:               501"
1758828,2018-03-26 06:40:38 UTC,"this is different from bug #1749004 because that was an actual Data Race, this is more an unsynchronized series of events being asserted as though we assume they will happen in a specific order."
1758828,2018-03-26 06:48:13 UTC,"Also failed:
http://10.125.0.203:8080/job/RunUnittests-arm64/319/testReport/junit/github/com_juju_juju_worker_caasoperator/TestPackage/"
1758828,2019-09-09 07:11:35 UTC,"We have done a considerable amount of work both in CAAS area as well as fixing couple of irregularities in our watchers. As part of this work, we must have fixed the cause of this failure since I can no longer reproduce it locally after plenty of runs under stress."
1758830,2018-03-26 08:18:24 UTC,"The attachment ""Patch from ofical development branch of cantor"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1758833,2018-04-28 07:01:06 UTC,The bug exists in bionic-final 20180427 enhanced.
1758833,2018-04-26 09:22:08 UTC,This bug was fixed in bionic-final 20180425.1 version
1758844,2018-04-05 17:11:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758844,2018-03-26 08:37:13 UTC,"StacktraceTop:
 tcache_get (tc_idx=2) at malloc.c:2943
 __GI___libc_malloc (bytes=bytes@entry=48) at malloc.c:3050
 _FcStrSetGrow (growElements=1, set=0x55905cd07730) at fcstr.c:1154
 _FcStrSetAppend (set=set@entry=0x55905cd07730, s=s@entry=0x5590595f47c0 ""/etc/fonts/conf.d/10-scale-bitmap-fonts.conf"") at fcstr.c:1180
 IA__FcStrSetAdd (set=0x55905cd07730, s=s@entry=0x5590595f47c0 ""/etc/fonts/conf.d/10-scale-bitmap-fonts.conf"") at fcstr.c:1217"
1758844,2018-04-04 06:58:53 UTC,I tried to reproduce with the conf file attached but could not.
1758849,2018-03-26 16:07:10 UTC,"This is already fixed, and being released as part of 2.32. Here is the commit:"
1758849,2018-04-03 18:33:12 UTC,"The fix is also in candidate now. It includes code to unbreak you if you are in the broken state already. The promotion of the fix to stable should happen any day. The following workaround should also work (if you can't refresh to candidate):
- snap set core service.ssh.disable=false
- ignore the error
- reboot
after the reboot you should have ssh. But the best course of action is of course to use the real fix :)"
1758858,2018-12-11 22:46:10 UTC,"I think milestone for this bug was moved by mistake, fix is already commited to dev branch, it will go into 5.1."
1758858,2019-05-11 08:47:44 UTC,This was released in 5.1.0.
1758858,2018-09-08 14:29:38 UTC,"Fixed in revision c68ad411ff9c89aafb90920bcbedd3cd2509924e
https://git.launchpad.net/kicad/patch/?id=c68ad411ff9c89aafb90920bcbedd3cd2509924e"
1758858,2018-03-26 10:28:15 UTC,Sorry about that.
1758858,2018-03-26 10:12:20 UTC,Please add version info.
1758858,2018-12-11 19:21:42 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1758859,2018-03-26 17:36:28 UTC,"Hey Romain, thanks for the bug report!"
1758859,2018-03-26 19:47:56 UTC,Yes that was indeed the culprit. I messed this up when I refreshed my credentials. Thanks Kyle and sorry for taking your time.
1758859,2018-03-26 21:14:18 UTC,"Oh no problem at all! We need to handle that error better, so we definitely appreciate the bug :) ."
1758860,2019-09-19 12:05:15 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1758869,2018-03-27 23:01:14 UTC,This is caused by this commit from mainline:
1758869,2018-03-27 23:03:40 UTC,Issue and patches described here:
1758869,2018-03-28 16:21:42 UTC,Also affects Xenial generic kernel (4.4.0-117.141).
1758869,2018-03-28 16:26:35 UTC,Attached backport of mainline a15a7535 fixes the problem (tested on c3.large instances) for Xenial generic and linux-aws 4.4-based kernels.
1758869,2018-03-29 15:39:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1758869,2018-03-30 16:39:39 UTC,"Verified fixed in proposed kernels:
  linux (4.4.0-118.142)
  linux-aws (4.4.0-1054.63)"
1758869,2018-04-04 09:27:25 UTC,This bug was fixed in the package linux - 4.4.0-119.143
1758869,2018-03-26 11:11:28 UTC,"Also affection Trusty + AWS 4.4.0-1015 in proposed, log here:
https://pastebin.ubuntu.com/p/6CZdpPnMKw/"
1758869,2018-03-26 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1758875,2020-10-26 10:37:23 UTC,removing the assignee due to a long inactivity
1758875,2018-06-15 05:42:08 UTC,"After checking more details on existing migration tests, i have few queries before adding the new tests."
1758875,2018-03-27 02:58:19 UTC,"Yea, we can add test for migration with same type. please propose the patch on gerrit."
1758875,2018-03-27 02:59:15 UTC,"Though it is not bug, it is new test addition. but anyways let's add new test."
1758881,2018-03-26 11:26:00 UTC,The duplicate bug is private.
1758881,2018-03-26 11:10:10 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1651686, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1758895,2018-03-26 20:36:48 UTC,related https://github.com/lxc/lxd-pkg-snap/issues/10
1758898,2018-03-26 14:11:11 UTC,Are you sure this is a duplicate of https://bugs.launchpad.net/bugs/1153309? That one seems to have a problem with typep after a single class definition. The bug described here is in PCL:
1758905,2018-04-19 22:12:31 UTC,This issue was fixed in the openstack/designate-dashboard 7.0.0.0b1 development milestone.
1758911,2018-03-26 13:14:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758911,2019-12-03 08:14:01 UTC,can't reproduce with 18.04
1758911,2019-12-04 15:05:00 UTC,Confirmed...
1758914,2018-03-26 14:28:54 UTC,I am using the following work around: simply create the bookmark with its default name and afterwards edit the created bookmark to your liking.
1758919,2018-03-26 13:53:02 UTC,attached is the original and juju modified interfaces file
1758919,2018-03-26 13:55:11 UTC,"the routes are in the wrong bond (bond2), however the gateways are on br-bond0. Also in MAAS they are set to those proper subnets."
1758919,2018-03-27 04:49:51 UTC,"IMHO, this should also be fixed in cloud-init. If the input netplan contains ""global"" routes, the renderer (or whatever can pre-process the Netplan before renderering) should intelligently determine which interfaces have an on-link gateway that matches the global route, and automatically render the route at interface scope instead of ""global""."
1758919,2018-03-26 14:39:51 UTC,"IMHO that's an obvious MAAS fault in writing the routes always to the last device and not to the device the routes are 'attached' to. In this scenario doing ifdown bond2 (an interface that has absolutely nothing to do with the static routes) would bring the routes down. Moreover, the assumption that order of the devices in e/n/i will be the order in which the devices are brought might be incorrect. IMHO This should be fixed in MAAS."
1758919,2018-03-26 14:30:39 UTC,"You are right, and as soon as I wrote the comment I realized I was wrong (mixed it with using iptables in post-up)."
1758919,2018-03-26 13:59:09 UTC,"on nodes without containers, the configuration is put to /etc/network/interfaces.d/50-cloud-init.cfg, which is also available on all nodes, but getting overridden."
1758919,2018-03-26 14:26:04 UTC,"Note that:
https://launchpadlibrarian.net/362140579/50-cloud-init.cfg
Is a lie, because it pretends that it is just setting up the ""post-up""
routes ""after all interfaces"", but really all of those are explicitly
attached to bond2 (it though it wasn't indenting them, but ifup, et al,
don't actually pay attention in that fashion.)"
1758919,2018-03-26 14:24:25 UTC,"Why is adding it to the ""last interface"" correct. Wouldn't it be more
correct to attach routes to the interface that contains that route?"
1758919,2018-03-26 14:29:09 UTC,"Is this actually Field Critical? Isn't just moving the post-up to a
different section enough to fix the field issue as a workaround?"
1758919,2018-03-26 13:59:10 UTC,"ifup brings interfaces in serial. In juju's ENI, this means that it would bring bond0 before br-bond0 and br-bond1. And since layer3, provided by br-bond1 and br-bond2 would not exist when post-up is run, post-up would fail. Because of '|| true' that would not cause ifup to fail, but it would leave the machine without routes."
1758921,2018-03-26 13:52:21 UTC,The attached patch extends the scope of locking to solve the issue (and https://bugs.launchpad.net/sbcl/+bug/1758898 as well). Users afraid of deadlock might want to use (setf *dfun-miss-lock-all-p* nil) to have the original behavior.
1758924,2019-05-15 04:17:30 UTC,[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]
1758924,2019-03-15 07:04:40 UTC,Thanks Sebastien for re-assigning.
1758924,2018-04-16 15:10:59 UTC,I have confirmed that overwriting gnome-keyring-daemon with an older version from ub16 does return the behavior to expected.
1758924,2018-04-16 15:09:22 UTC,"Update - that ssh-add -d did not actually work. It appears that it does get the 'ssh-add -l' output back to correct, but any attempt to actually USE the agent immediately re-adds the entry with only the filename/path as the comment."
1758924,2018-04-10 17:53:00 UTC,Workaround appears to be 'ssh-add -d' to remove the dynamically added identities - it then seems to reload from identity file and includes the key comment.
1758924,2019-03-14 10:31:50 UTC,"Thank you for your bug report, in that version gnome-keyring removed its own ssh-agent implementation to use the openssh one,
https://gitlab.gnome.org/GNOME/gnome-keyring/commit/8db2b978"
1758926,2018-03-27 11:14:26 UTC,I tried to produce this bug in Bionic and I couldn't - 27/3/2018
1758928,2018-08-30 15:41:55 UTC,Might also be useful to have actions for audit- and clear-quarantine
1758930,2018-03-26 20:29:22 UTC,Looks like a crash in gnome-online-accounts. Can you check if a crash file was generated in /var/crash/ ?
1758930,2018-03-26 21:00:56 UTC,Yes attaching.....
1758930,2018-03-29 12:07:03 UTC,"How can I help this issue, I attached logs and would welcome running any diag you might require."
1758930,2018-03-30 10:26:17 UTC,Hey lewis this looks like a crash in gnome-online-accounts rather than in software-properties. Do you get this all the times?
1758930,2018-04-28 14:58:55 UTC,I had to manually install libicu57 <https://packages.debian.org/stretch/amd64/libicu57/download> to get software-properties-gtk to run (due to crash in gnome-online-accounts).
1758930,2018-04-28 15:37:19 UTC,This is powerpc
1758930,2018-04-28 15:38:53 UTC,Sorry yes it's amd64 too many desktops lol I'll try your suggestion.
1758930,2018-04-28 15:41:48 UTC,"This was on my desktops at work, it's w10 with ubuntu on it using ask setup
presentation at www.tinyurl.com/donofrio1804 (ignore unneeded onedrive
login)"
1758931,2020-01-25 22:17:50 UTC,"As with almost every tool, setting the style (including the line spacing) *before* actually creating an object sets the new value permanently. So first: select the text tool, change the line spacing. Any new text that is created has the new line height."
1758931,2018-03-26 22:54:57 UTC,You might try this:
1758931,2018-03-26 17:54:40 UTC,"Oh, wow. Thanks! That did fix it. But only for that single box. Every time I create a new one it's back to 1000. Clicking Set default does not help, even after changing the font (I seem to always have to change the font in the Text and Font dock to be able to click Apply, so I thought it might help here too)."
1758931,2018-03-27 20:57:57 UTC,"Thanks, TD! That worked. But I would never have been able to figure this out on my own. That is: I think this is so unintuitive that it should be changed in some way. Maybe for example the linespacing should also be saved when clicking on ""Set default""? Though that might be confusing since that setting is not in the Text and Fonts dock, where the default button is…"
1758931,2018-03-26 17:18:43 UTC,You might check the line spacing on that font. The screencapture shows it set to 1000.00 or such. I get similar results by setting the spacing that way.
1758937,2018-03-26 14:46:27 UTC,This is an example image when using a single screen.
1758937,2018-03-26 14:53:15 UTC,Another related bug.
1758937,2018-06-16 19:33:01 UTC,Upstream bug: https://github.com/mate-desktop/mate-panel/issues/303
1758942,2018-11-28 07:00:11 UTC,This change was made by a bot.
1758943,2018-07-05 16:32:22 UTC,"Reviewed:  https://review.openstack.org/557712
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=0376185fb34a8cba3d8d705e579e08cddfb9316d
Submitter: Zuul
Branch:    master"
1758943,2018-07-06 11:53:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/580614"
1758943,2018-07-06 18:04:06 UTC,"Reviewed:  https://review.openstack.org/580614
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=f67696177643b448f9e7e918cd72841f43dacfcd
Submitter: Zuul
Branch:    stable/queens"
1758943,2018-07-27 13:15:44 UTC,This issue was fixed in the openstack/glance 17.0.0.0b3 development milestone.
1758949,2018-03-31 17:15:56 UTC,"Hi,"
1758949,2018-03-30 17:18:08 UTC,"Hi,"
1758949,2018-03-30 22:09:32 UTC,"well - there is no ""CVS pharmacy - Online Pharmacy - Transfer Prescription
or Refil2"" but there is a folder called ""CVS pharmacy - Online Pharmacy -
Transfer Prescription or  Refil<more characters>"" - the ""2"" isn't present."
1758949,2018-03-27 17:02:27 UTC,"Hi,"
1758949,2018-03-27 15:42:57 UTC,"Not fixing paths works fine. Hadn't tried that until just now.
Not having a clue is the real problem isnt it. This is a case of ""the
computer knows but ain't tellin' """
1758949,2018-03-27 07:58:21 UTC,"Hi,"
1758949,2018-03-30 15:28:54 UTC,"well - I guess I'm misunderstanding something. I can only write a DVD if I
select NOT to be windows compatible. If I select windows compatibility
brasero ejects the disk and posts the error. If you didn't mean for me to
write a windows compatible DVD then your suggested procedure doesn't show
any mangling."
1758972,2018-03-26 16:59:55 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
 QMessageLogger::fatal (this=this@entry=0x7ffd768337c0, msg=msg@entry=0x7f0d15c01758 ""QThread: Destroyed while thread is still running"") at global/qlogging.cpp:796
 QThread::~QThread (this=0x18cd350, __in_chrg=<optimized out>) at thread/qthread.cpp:429
 sipQThread::~sipQThread (this=0x18cd350, __in_chrg=<optimized out>) at ./build-3.6/QtCore/sipQtCorepart2.cpp:10069
 forgetObject (sw=sw@entry=0x7f0d0f81ad38) at siplib.c:12032"
1758975,2018-03-26 17:28:49 UTC,Adding a query to identify likely victims of this bug.
1758975,2018-04-05 19:27:43 UTC,I have seen this occur. Our descriptions are very similar.
1758981,2018-04-13 00:30:18 UTC,"Afshan F , do you need any other info here?"
1758981,2018-08-29 16:58:24 UTC,Does anyone have a solution to this problem?
1758981,2018-04-03 21:31:14 UTC,Bump
1758981,2018-03-29 06:24:38 UTC,"Hi,"
1758981,2018-03-29 16:59:29 UTC,"error_log:
E [29/Mar/2018:10:55:51 -0400] Unknown directive JobPrivateAccess on line 83 of /etc/cups/cupsd.conf.
E [29/Mar/2018:10:55:51 -0400] Unknown directive JobPrivateValues on line 84 of /etc/cups/cupsd.conf.
E [29/Mar/2018:10:55:51 -0400] Unknown directive SubscriptionPrivateAccess on line 85 of /etc/cups/cupsd.conf.
E [29/Mar/2018:10:55:51 -0400] Unknown directive SubscriptionPrivateValues on line 86 of /etc/cups/cupsd.conf.
E [29/Mar/2018:11:27:06 -0400] Unknown directive JobPrivateAccess on line 83 of /etc/cups/cupsd.conf.
E [29/Mar/2018:11:27:06 -0400] Unknown directive JobPrivateValues on line 84 of /etc/cups/cupsd.conf.
E [29/Mar/2018:11:27:06 -0400] Unknown directive SubscriptionPrivateAccess on line 85 of /etc/cups/cupsd.conf.
E [29/Mar/2018:11:27:06 -0400] Unknown directive SubscriptionPrivateValues on line 86 of /etc/cups/cupsd.conf."
1758981,2018-03-27 09:22:45 UTC,"Hi KitchM,"
1758981,2018-03-28 21:21:37 UTC,"I removed the second printer in CUPS, but nothing happens any different."
1758981,2018-03-29 17:00:14 UTC,syslog
1758981,2018-03-27 17:55:59 UTC,Now it doesn't clean at all; nothing prints out.
1758982,2018-03-26 17:27:39 UTC,"Although this bug is not in the keystone charm, adding it here and marking it invalid, as the keystone charm is the most likely place others will look for this bug."
1758992,2020-02-26 13:15:52 UTC,I'm fine with closing this here as long as the upstream gcc bug remains open.  I worked around this at the time I reported it so it's not blocking me.
1758992,2020-02-26 10:38:04 UTC,"Peter, It turns out nobody in community is sure of how to resolve it. Is this problem still blocking you? We may consider close it with won't fix."
1758992,2018-04-11 14:22:35 UTC,Thanks for reporting the bug then. It's being worked on.
1758992,2018-04-11 14:14:24 UTC,"Yes, I was referring to the platform of the pre-built toolchain, not the kernel."
1758992,2018-04-11 13:59:01 UTC,"Oh my bad, I misunderstood the last sentence in your original comment. You meant that you get this bug with our Linux toolchain. Understood. Any chance you could change your app to use an int rather than unsigned char in the meantime?"
1758992,2018-04-11 13:15:16 UTC,I don't know if the Linux kernel could be affected; my discovery was in a Nordic Cortex-M-based Bluetooth soft device (binary blob with SWI-based API defined in a header).  I've patched their headers to work around it.
1758992,2018-04-11 12:30:32 UTC,"Hi Peter,"
1758992,2018-04-11 12:20:44 UTC,I've reported the bug in [1]. I have a patch that works for this testcase which I'm currently testing.
1758994,2019-02-19 15:32:31 UTC,We should SRU .2 to bionic indeed
1758994,2019-02-19 15:06:56 UTC,"Hi, when will the fix included in LTS? Bionic is on 18.04.2 now but the fix hasn't been included at all."
1758994,2018-11-22 20:51:27 UTC,"Hi, I was wondering as to when the fix will be included in Ubuntu 18.04.1 LTS?"
1758994,2018-03-27 11:24:27 UTC,I was able to recreate this bug in bionic - 27/03/2018
1758994,2018-06-03 07:57:29 UTC,Hi I can confirm that when I install camorama from the Ubuntu Software application in 18.04 LTS the webcam works properly while cheese displays the error.
1758994,2018-05-31 23:25:49 UTC,"Hi,"
1758994,2018-05-31 23:23:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1758994,2018-03-26 20:13:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1758994,2018-07-14 06:25:39 UTC,"This looks exactly like an issue that has just been worked around in GStreamer (see upstream bug at https://bugzilla.gnome.org/show_bug.cgi?id=796789, the fix will be in release 1.14.2)."
1758997,2018-04-10 12:57:58 UTC,"### get_ip_addr() ###
{'broam': {'bridged_interfaces': ['eno1'],
           'flags': ['BROADCAST', 'MULTICAST', 'UP', 'LOWER_UP'],
           'index': 10,
           'inet': ['10.244.40.31/21'],
           'mac': 'd2:66:98:72:48:73',
           'name': 'broam',
           'settings': {'group': 'default',
                        'mtu': '1500',
                        'qdisc': 'noqueue',
                        'qlen': '1000',
                        'state': 'UP'},
           'type': 'ethernet.bridge'},
 'eno1': {'flags': ['BROADCAST', 'MULTICAST', 'UP', 'LOWER_UP'],
          'index': 2,
          'mac': '14:02:ec:42:28:bc',
          'name': 'eno1',
          'settings': {'group': 'default',
                       'master': 'broam',
                       'mtu': '1500',
                       'qdisc': 'mq',
                       'qlen': '1000',
                       'state': 'UP'},
          'type': 'ethernet.physical'},
 'eno2': {'flags': ['BROADCAST', 'MULTICAST'],
          'index': 3,
          'mac': '14:02:ec:42:28:bd',
          'name': 'eno2',
          'settings': {'group': 'default',
                       'mtu': '1500',
                       'qdisc': 'noop',
                       'qlen': '1000',
                       'state': 'DOWN'},
          'type': 'ethernet.physical'},
 'eno3': {'flags': ['BROADCAST', 'MULTICAST'],
          'index': 5,
          'mac': '14:02:ec:42:28:be',
          'name': 'eno3',
          'settings': {'group': 'default',
                       'mtu': '1500',
                       'qdisc': 'noop',
                       'qlen': '1000',
                       'state': 'DOWN'},
          'type': 'ethernet.physical'},
 'eno4': {'flags': ['BROADCAST', 'MULTICAST'],
          'index': 6,
          'mac': '14:02:ec:42:28:bf',
          'name': 'eno4',
          'settings': {'group': 'default',
                       'mtu': '1500',
                       'qdisc': 'noop',
                       'qlen': '1000',
                       'state': 'DOWN'},
          'type': 'ethernet.physical'},
 'eno49': {'flags': ['BROADCAST', 'MULTICAST', 'UP', 'LOWER_UP'],
           'index': 4,
           'inet': ['10.245.219.23/20'],
           'mac': '5c:b9:01:9d:09:fc',
           'name': 'eno49',
           'settings': {'group': 'default',
                        'mtu': '1500',
                        'qdisc': 'mq',
                        'qlen': '1000',
                        'state': 'UP'},
           'type': 'ethernet.physical'},
 'eno50': {'flags': ['BROADCAST', 'MULTICAST'],
           'index': 7,
           'mac': '5c:b9:01:9d:09:fd',
           'name': 'eno50',
           'settings': {'group': 'default',
                        'mtu': '1500',
                        'qdisc': 'noop',
                        'qlen': '1000',
                        'state': 'DOWN'},
           'type': 'ethernet.physical'},
 'ens1f0': {'flags': ['BROADCAST', 'MULTICAST'],
            'index': 8,
            'mac': '00:11:0a:66:2d:6c',
            'name': 'ens1f0',
            'settings': {'group': 'default',
                         'mtu': '1500',
                         'qdisc': 'noop',
                         'qlen': '1000',
    ..."
1758997,2018-04-10 21:57:54 UTC,We believe this issue has been fixed with as a side effect. Could you please test the latest MAAS for dailybuils?
1758997,2018-04-10 19:58:26 UTC,in another environment
1758997,2018-04-10 12:57:31 UTC," hostname | ifid |  name  |   type   |    mac_address    | ip | alloc_type | cidr | vid | fabric
----------+------+--------+----------+-------------------+----+------------+------+-----+--------
 leafeon  |    1 | eno1   | physical | 1c:98:ec:21:98:54 |    |            |      |     |
 leafeon  |    2 | eno2   | physical | 1c:98:ec:21:98:55 |    |            |      |     |
 leafeon  |    3 | eno3   | physical | 1c:98:ec:21:98:56 |    |            |      |     |
 leafeon  |    4 | eno4   | physical | 1c:98:ec:21:98:57 |    |            |      |     |
 leafeon  |    5 | eno49  | physical | 8c:dc:d4:b3:08:0c |    |            |      |     |
 leafeon  |    6 | eno50  | physical | 8c:dc:d4:b3:08:0d |    |            |      |     |
 leafeon  |    7 | ens1f0 | physical | 00:11:0a:68:67:c8 |    |            |      |     |
 leafeon  |    8 | ens1f1 | physical | 00:11:0a:68:67:c9 |    |            |      |     |
 meinfoo  |    9 | eno1   | physical | 14:02:ec:42:28:bc |    |            |      |     |
 meinfoo  |   10 | eno2   | physical | 14:02:ec:42:28:bd |    |            |      |     |
 meinfoo  |   11 | eno3   | physical | 14:02:ec:42:28:be |    |            |      |     |
 meinfoo  |   12 | eno4   | physical | 14:02:ec:42:28:bf |    |            |      |     |
 meinfoo  |   13 | eno49  | physical | 5c:b9:01:9d:09:fc |    |            |      |     |
 meinfoo  |   14 | eno50  | physical | 5c:b9:01:9d:09:fd |    |            |      |     |
 meinfoo  |   15 | ens1f0 | physical | 00:11:0a:66:2d:6c |    |            |      |     |
 meinfoo  |   16 | ens1f1 | physical | 00:11:0a:66:2d:6d |    |            |      |     |
 swoobat  |   17 | eno1   | physical | 14:02:ec:40:fd:9c |    |            |      |     |
 swoobat  |   18 | eno2   | physical | 14:02:ec:40:fd:9d |    |            |      |     |
 swoobat  |   19 | eno3   | physical | 14:02:ec:40:fd:9e |    |            |      |     |
 swoobat  |   20 | eno4   | physical | 14:02:ec:40:fd:9f |    |            |      |     |
 swoobat  |   21 | eno49  | physical | 5c:b9:01:9b:56:64 |    |            |      |     |
 swoobat  |   22 | eno50  | physical | 5c:b9:01:9b:56:65 |    |            |      |     |
 swoobat  |   23 | ens1f0 | physical | 00:11:0a:68:6e:b4 |    |            |      |     |
 swoobat  |   24 | ens1f1 | physical | 00:11:0a:68:6e:b5 |    |            |      |     |
(24 rows)"
1758997,2019-09-19 14:46:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1758997,2018-04-04 17:58:44 UTC,Here's a script that automates the SQL queries I mentioned in my previous comment.
1758997,2018-04-04 15:12:47 UTC,re #3 This happens before we move subnets.
1758997,2018-04-03 18:24:57 UTC,A few things:
1758997,2018-04-10 11:59:23 UTC,setting this bug report to incomplete because the requested information has not been provided
1758997,2018-04-03 18:22:09 UTC,"Hi Jason/Eric,"
1758997,2018-04-02 22:44:06 UTC,reproduced again on 2.4.0~beta2-6783-g2739ac4-0ubuntu1~18.04.1~20180402~ubuntu18.04.1
1759000,2018-03-27 18:28:36 UTC,I added few information about the Ironic and Neutron ports.
1759000,2018-03-27 18:37:29 UTC,In the logs I can see the provisioning network VLAN tagged on both switches but for the tenant network VLAN it only happened on SW11.
1759000,2018-03-27 19:04:49 UTC,I guess this is the same issue: https://bugs.launchpad.net/networking-generic-switch/+bug/1576597
1759000,2018-03-27 21:10:37 UTC,https://review.openstack.org/#/c/557051/
1759000,2018-03-27 21:16:48 UTC,After applying the change above I can see the VLAN tagged on bot switches.
1759003,2018-05-14 14:59:36 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1759003,2018-05-14 14:59:32 UTC,This bug was fixed in the package livecd-rootfs - 2.408.30
1759003,2018-05-11 17:31:34 UTC,The -updates version produces the same content as the -proposed version for non-minimized builds.
1759003,2018-05-11 16:18:39 UTC,"I have just performed two livefs builds using the proposed version (i.e. 2.408.30), one with the minimized subproject and one without."
1759003,2018-05-11 15:36:48 UTC,I'm going to perform verification of this now.
1759003,2018-03-28 21:27:00 UTC,"I wasn't planning on doing the xenial back port myself, but I can if you want..."
1759003,2018-05-09 12:19:48 UTC,"> There is no regression as this change is scoped to ubuntu-cpc minimal images only, which have not been announced.
"
1759003,2018-03-29 00:55:06 UTC,A back-port that affects ubuntu-cpc:minimized (but not non-minimized) would be great because cloud-init does explode in the minimal images without the fix.  We just don't want to see a change in the standard images.
1759003,2018-03-27 14:30:44 UTC,"mwhudson, if you're bringing this back to xenial could you ensure this affects ubuntu-cpc/minimized only but not the rest of ubuntu-cpc?  We'd like that as a first pass."
1759003,2018-03-27 03:47:03 UTC,This bug was fixed in the package livecd-rootfs - 2.515
1759003,2018-03-26 18:44:26 UTC,Failure is:
1759003,2018-03-26 18:43:28 UTC,I launched a xenial minimal cloud-image (20180321) via LXD:
1759003,2018-05-09 12:21:16 UTC,"Hello Robert, or anyone else affected,"
1759004,2018-03-27 23:15:39 UTC,"Reviewed:  https://review.openstack.org/556120
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0f4d7ff5277a3effcf23d17fd85abeb7dc78aca8
Submitter: Zuul
Branch:    master"
1759013,2018-09-24 15:35:19 UTC,"The problem still persists. I am using 2.4.3-bionic-amd64, but tried without success with other channels (edge, beta) or via apt."
1759013,2019-06-25 02:44:36 UTC,I am pretty sure that veebers is not working on this bug.
1759013,2018-09-10 11:54:50 UTC,@niedbalski can you specify what version of Juju and which track/channel of the snap you're using? I tested it with the edge and stable channels with success.
1759013,2018-03-26 20:52:34 UTC,There seems to be some oddity around a user's path env var and whether juju metadata is a found command when running from snap.
1759013,2018-03-27 07:44:48 UTC,"Ok, this has been fixed for the point-release-tracking (candidate) and stable snaps (i.e. 2.3.5+2.3-bbd1ada works)."
1759013,2018-03-26 22:13:27 UTC,juju-metadata is not in any PATH (it can be found in the likes of /snap/juju/3591/bin but that's not normally in any path).
1759013,2018-03-26 19:42:23 UTC,Confirmed for 2.3.4 and version listed above.  Not an issue for the tip of develop
1759013,2018-09-09 16:00:32 UTC,This doesn't works with juju 2.4.x snap
1759014,2019-04-25 07:47:40 UTC,The systemd issue on Bionic has been resolved with systemd 237-3ubuntu10.21: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804478
1759014,2019-04-18 23:39:30 UTC,A possible SRU regression has been reported against netplan.io 0.96-0ubuntu0.18.10.2 in LP: #1825206.  This version has been rolled back to -proposed while the investigation is ongoing.
1759014,2019-04-15 22:33:21 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1759014,2019-04-15 22:32:43 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.2
1759014,2019-04-11 07:40:29 UTC,netplan.io 0.96-0ubuntu0.18.04.3 with systemd 237-3ubuntu10.19:
1759014,2019-04-10 21:19:42 UTC,"Hello Alan, or anyone else affected,"
1759014,2019-04-08 14:08:19 UTC,Submitted https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730.
1759014,2019-03-29 13:33:51 UTC,Verified using netplan.io 0.96-0ubuntu0.18.04.2 and systemd 237-3ubuntu10.15 with
1759014,2019-03-29 13:27:21 UTC,Verified using netplan.io 0.96-0ubuntu0.18.10.2 and systemd 239-7ubuntu10.10 with
1759014,2019-03-29 13:01:44 UTC,Short installation instructions for the netplan.io 0.96 package on Ubuntu 18.04:
1759014,2019-03-29 01:21:08 UTC,"Hello Alan, or anyone else affected,"
1759014,2019-03-29 01:14:26 UTC,"Hello Alan, or anyone else affected,"
1759014,2019-03-27 08:52:23 UTC,"Hi Mathieu, I don't think Cosmic or Disco systemd are affected. They are both >= v239, and Cosmic behaved fine when verifying https://bugs.launchpad.net/netplan/+bug/1776228."
1759014,2019-04-30 21:02:51 UTC,"Hello Alan, or anyone else affected,"
1759014,2019-04-01 12:15:44 UTC,Applied
1759014,2019-04-30 21:56:53 UTC,"Hello Alan, or anyone else affected,"
1759014,2020-12-02 19:00:06 UTC,The fix for dns override for dhcp4 does not work with network manager.
1759014,2019-05-02 11:14:25 UTC,"Verified netplan.io 0.96-0ubuntu0.18.04.4 with the configuration from https://bugs.launchpad.net/netplan/+bug/1759014/comments/52. Routes are configured as expected, as is DNS."
1759014,2019-03-27 08:20:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759014,2020-08-03 01:23:09 UTC,"@ddstreet I've been looking into a different issue, which is due to the Netplan renderer.
The renderer defaults to networkd on server/cloud and NetworkManager on Desktop.  Some apps expect NetworkManager, and break on systems configured with networkd (e.g. UI network config, apt-daily, etc)."
1759014,2020-06-24 21:02:11 UTC,"@francogpellegrini, @fernando-sismonda, I just tested with netplan yaml similar to yours, and i can't reproduce any problem; the dhcp dns server is correctly ignored on my test system.  What versions of netplan, and systemd, do you have installed?  Also, what's the content of your /run/systemd/network/* and/or /etc/systemd/networkd/* files?"
1759014,2020-06-21 04:00:26 UTC,"Hi all, I'm using ubuntu 20.04 on a raspberry pi (64bit version).  And the problem is still present.  My netplan:"
1759014,2020-04-22 13:54:13 UTC,"I'm using the version  0.98-0ubuntu1~18.04.1, and the bug is NOT fixed using this:"
1759014,2019-09-27 17:50:39 UTC,"From reading the comments, I believe the only systemd issue was fixed in bug 1804478, so I marked this as fix released for systemd.  If that's incorrect and there is still a systemd problem, please feel free to reopen and comment, or open new bug."
1759014,2019-05-02 08:28:49 UTC,Is it possible to get this into 18.04.3 release? Not that fond of waiting until January 2020 for the .4 release.
1759014,2019-09-10 01:39:18 UTC,I just want to note here is that it seems not working still for me in ubuntu 18.04 running on aws ec2 ami.
1759014,2019-05-08 00:00:42 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
1759014,2019-05-06 16:40:58 UTC,I needed :
1759014,2019-05-06 15:27:26 UTC,"@Tom Matthews: Are you sure that https://bugs.launchpad.net/netplan/+bug/1759014/comments/62 is netplan's fault? On my test box the systemd renderer DHCP settings end up in the same stanza for IPv4 and IPv6, like"
1759014,2019-05-06 14:13:36 UTC,Is it possible to get this into 18.04.3 release? Not that fond of waiting until January 2020 for the .4 release.
1759014,2019-05-04 12:46:34 UTC,"netplan.io 0.96
systemd 240"
1759014,2019-05-02 12:18:28 UTC,Verified netplan.io 0.96-0ubuntu0.18.10.3 using
1759014,2019-05-08 00:01:20 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
1759014,2019-03-26 19:16:18 UTC,This means we'll need to identify what patches need to be applied on top of v237 to make this work.
1759014,2019-03-22 09:33:22 UTC,"Hi Timo, this is good news. Just out of curiosity, how did you overcome systemd v239 dependency, which is needed by recent netplan versions, apparently to fix another bug?"
1759014,2019-03-26 01:24:59 UTC,"Mathieu, quick search reveals that this bug https://bugs.launchpad.net/netplan/+bug/1802004 might be related to systemd v237, and that v239 supposedly fixes it. I stumbled upon it after I tried to re-build the latest netplan on bionic, that's why I've just rebuilt current bionic version with PR#48 applied."
1759014,2018-10-10 03:11:27 UTC,"Any chance you can also add the ability to send the other DHCP options, like option 77 user class (user-class dhclient, UserClass= in networkd)"
1759014,2018-10-08 20:49:08 UTC,"Can we add support in the patch for setting 'UseDomains=false' or 'UseDomains=route'? This would allow ignoring the search domain provided by the dhcp server, which is useful when running in clouds that don't allow overriding this field.  This use to be possible by setting the 'supersede domain-search' option in /etc/dhcp/dhclient.conf"
1759014,2018-10-05 04:32:53 UTC,[x-post from the merge request]
1759014,2018-10-04 22:19:43 UTC,"I have a merge proposal based on the patch in #10.
https://code.launchpad.net/~awj/netplan/+git/netplan/+merge/354158"
1759014,2018-10-04 18:19:51 UTC,"If I understand patch #10 correctly, that looks acceptable.  Any patch for netplan should be consistent with the purpose of netplan, that being, it correctly instructs the underlying configured network management engine.  Netplan should NOT be creating new behaviors apart from what the underlying manager would and can do."
1759014,2018-09-06 13:38:47 UTC,"Hello,
The feature - to disable DHCP DNS, very useful for Google Cloud, as Google Cloud doesn't have any option to change DHCP DNS servers to a custom one, yet"
1759014,2018-10-30 16:21:58 UTC,"The attachment ""replace_dhcp_dns.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1759014,2018-08-31 05:29:18 UTC,"I also cannot think of a good use case for such a configuration, but that could just mean that I am not sufficiently creative or experienced.  I also prefer configuration that is straightforward and doesn't have magic dependencies between settings (or at least as few as possible."
1759014,2018-08-31 02:47:58 UTC,"The patch in #7 would fix some use cases while breaking others.  For example, the current behavior is ALSO a legitimate way to configure a network, and would be broken by that patch."
1759014,2018-05-07 14:29:35 UTC,"Netplan is only appending DNS Search domains and IP's with dhcp4: set to yes.  additionally, its ignoring the command ""nmcli con modify ${deviceid} ipv4.ignore-auto-dns yes"""
1759014,2018-08-10 14:11:41 UTC,"Is there any timeframe for fixing this issue?  There is no way to migrate to Ubuntu 18.04 when netplan can't be configured to use a static list of DNS servers with DHCP enabled.  This is a very common configuration in large complex network environments.  I fail to see how this bug made it past basic quality controls.
NetworkManager settings:
nmcli connection modify ${ID} ipv4.ignore-auto-dns yes
nmcli connection modify ${ID} ipv4.dns 'xx.xx.xx.10 xx.xx.xx.20'
nmcli connection modify ${ID} ipv4.dns-search 'abc01.domain.com. abc02.domain.com.'"
1759014,2018-08-07 18:44:12 UTC,This is affecting my organization and affects our ability to evaluate migrating from Ubuntu 14.04 to 18.04. Superseding AWS's advertised nameservers is a requirement for our applications.
1759014,2018-05-08 08:00:52 UTC,I don't think the two bugs are related.
1759014,2018-05-07 16:47:23 UTC,This bug appears to be related to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703882
1759014,2018-08-31 03:39:42 UTC,"In what legitimate use case one would want to add DHCP provided DNS server AFTER the list of manually configured ones? That’s just doesn’t make sense. Having anything configurable might seem useful, but it adds unneeded complexity in this case IMHO."
1759014,2018-11-06 14:58:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759014,2018-08-31 01:32:03 UTC,"The fix is trivial, any objections to putting it upstream?"
1759014,2018-11-22 04:01:32 UTC,This bug was fixed in the package netplan.io - 0.90
1759014,2018-11-15 14:44:31 UTC,"^^^ I accidentally did that, won't let me set it back to Fix Committed. Sorry!"
1759014,2019-03-25 20:13:55 UTC,There is no dependency on v239 for netplan backports. Bionic ships with v237 (and some patches); the dependency on systemd is for >= 235-3ubuntu3 in netplan.io. I do not believe a newer version than that is required.
1759014,2018-04-17 20:12:57 UTC,Package in Ubuntu was renamed from nplan to netplan.io; but regardless this bug is relevant to the netplan project in general; just moving bugs around here.
1759014,2019-03-22 09:18:14 UTC,"Hello Alan, or anyone else affected,"
1759014,2019-03-22 09:10:51 UTC,"Hello Alan, or anyone else affected,"
1759014,2019-03-21 14:37:18 UTC,"Thank You Alexey for your feature backport.  I tested with your script, and the updated version correctly handled the new options when using networkd as the renderer on ""Ubuntu 18.04.2 LTS (GNU/Linux 4.18.0-16-generic x86_64)"". (NetworkManager not currently supported)"
1759014,2019-03-21 04:54:28 UTC,"For those who needs the bionic package with just this feature backported, I've made one. Install it with `curl -s https://packagecloud.io/install/repositories/l21/netplan/script.deb.sh | sudo bash`."
1759014,2019-03-26 09:34:15 UTC,"Verification of https://bugs.launchpad.net/netplan/+bug/1776228 confirmed that systemd v237 has issues triggered by customizing DHCP config, which systemd v239 corrected."
1759014,2019-02-11 06:57:13 UTC,"If the maintainers are willing to accept it, I have backported this to 18.04 here:"
1759014,2019-02-10 18:48:32 UTC,This is a very important feature to have backported to 18.04 as being able to override default gateways for multi-homed hosts (configured to use dhcp for multiple interfaces) and being able to avoid using DNS servers provided by a DHCP server(s) are quite common requirements.
1759014,2019-02-04 23:48:25 UTC,We also just ran into problems due to not being able to specify DHCP options in netplan. Please backport the fix to standard 18.04.
1759014,2019-01-19 16:58:25 UTC,"Just wanted to add another vote for backporting this fix to 18.04, would be really great and as other commenters have pointed out - it should not change behaviour for exiting configurations."
1759014,2019-01-03 01:16:26 UTC,Please backport fix to 18.04
1759014,2018-12-13 16:13:47 UTC,"In relation to the above comment, Canonical recently announced that Long Term Support for 18.04 is now extended to a 10 year period. It would be beneficial to have this fix backported to the long term Ubuntu release."
1759014,2019-02-23 22:06:43 UTC,"Another vote here, fighting this sadness with some VERY sad wrapper scripts. Netplan should never have been in any LTS if it can not support some of these basic options, honestly."
1759014,2018-12-07 14:07:03 UTC,Are there any plans to bring this fix to what I consider to be a regression (lack of feature parity with what was possibly previously in dhclient) into the current LTS release (Bionic 18.04)?
1759026,2018-03-26 21:02:25 UTC,The original request is to document intentions for TLS 1.3 support as part of the release notes.
1759031,2019-09-19 12:11:14 UTC,"Closing as there has been no activity for 60 days. If you still have this problem, check the already reported issues at https://inkscape.org/report. Thank you!"
1759031,2018-04-01 20:03:45 UTC,"Hi,"
1759031,2018-03-26 21:13:08 UTC,Can you add information on the OS used?
1759031,2019-06-04 03:50:55 UTC,"Hi, is this still an issue with the latest Inkscape version (0.92.4)?"
1759043,2018-03-30 20:27:16 UTC,"Thanks for the heads up, Jeremy. I think so too when looking at the code; no reason to bother upstream."
1759043,2018-03-30 20:09:36 UTC,"Yeah, I may have made a mistake. I've made many tryes before. And It only worked when I've undone all the procedures.
I guess editing greeter.dconf-defaults is much better too. It's safier and easier to make automated config across many installations."
1759043,2018-03-30 19:55:09 UTC,"Gunnar, I think /etc/gdm3/greeter.dconf-defaults might be unique to Debian and Ubuntu."
1759043,2018-03-30 19:28:41 UTC,"Thank you, Fábio!"
1759043,2018-03-30 03:29:24 UTC,"Hmmm.... Now I've just made a new clean OS reinstall. Installed all apt updates available right now (including dconf-cli_0.26.0-2ubuntu3, dconf-gsettings-backend_0.26.0-2ubuntu3 and dconf-service_0.26.0-2ubuntu3).
Followed straightly gnome's webpage instructions. It worked as expected! Then edited /etc/gdm3/greeter.dconf-defaults as Jeremy suggested - and It worked. And lastly undone first steps and left only /etc/gdm3/greeter.dconf-defaults edited. And It also worked.
For me It seems that, in current start, both procedures works as expected."
1759043,2018-03-30 03:02:06 UTC,"If any of you think it valuable, I can make new tests."
1759043,2018-03-30 03:00:14 UTC,I followed straightly all the steps (https://help.gnome.org/admin/system-admin-guide/stable/login-userlist-disable.html.en). A database similar to yours was created at /etc/dconf/db/gdm.
1759043,2018-03-29 19:08:56 UTC,"That's It!
I've tested a iso image generated early today and edited /etc/gdm3/greeter.dconf-defaults.
Thanks!"
1759043,2018-03-29 16:39:34 UTC,"On 2018-03-29 17:51, Jeremy Bicha wrote:

> (I haven't tried this stuff.)
"
1759043,2018-03-29 15:51:27 UTC,And I think you need to uncomment the [org/gnome/login-screen] line too.
1759043,2018-03-29 15:50:09 UTC,Oops. Try /etc/gdm3/greeter.dconf-defaults instead
1759043,2018-03-29 15:33:53 UTC,"Thanks, worth testing. But OTOH I'm disinclined to advise users in the official docs to edit a package owned file in /usr/share. There ought to be a better way."
1759043,2018-03-29 14:54:54 UTC,@Jeremy: Do you know offhand what the behavior in Ubuntu is supposed to be? Is it changed via patches in gdm3 and/or accountsservice?
1759043,2018-03-28 18:21:04 UTC,"The documentation is equal to the online one.
Does it mean It needs a correction with new procedures?"
1759043,2018-03-26 23:47:54 UTC,I am reassigning this to gnome-user-docs. The documentation may need to be customized a bit for Ubuntu here.
1759043,2018-03-29 21:53:47 UTC,"Editing /etc/gdm3/greeter.dconf-defaults, as Jeremy suggested, works for me too. However, also the instruction in system-admin-guide works fine for me, so making an Ubuntu specific variant of that page seems not to be motivated. Possibly there is room for improvements of the upstream page."
1759043,2018-03-29 15:01:22 UTC,"Maybe all you need to do is uncomment the disable-user-list line in
/usr/share/gdm/greeter.dconf-defaults"
1759061,2019-05-07 00:49:50 UTC,ref: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817358
1759061,2019-05-07 01:18:18 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657509"
1759061,2019-05-20 12:24:24 UTC,"Reviewed:  https://review.opendev.org/657509
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=4629aebe12473de8918bec3bb4ae5a23509dda24
Submitter: Zuul
Branch:    master"
1759061,2019-05-06 22:49:30 UTC,this page is completly outdated and needs a refresh: https://docs.openstack.org/image-guide/ubuntu-image.html
1759061,2019-05-07 00:48:06 UTC,"I think something is wrong with the iso.
Have you tried a newer version like http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/netboot/mini.iso
or Ubuntu 18.04? Will adapt the documentation to the latest version"
1759081,2019-09-19 12:00:03 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1759082,2018-03-27 00:44:35 UTC,"Hi Gabriel,"
1759082,2019-09-19 12:05:18 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1759084,2018-08-24 01:28:00 UTC,"Not strictly related to the original issue, but I just went through the included abstractions, and someone more familiar with akonadi will easily spot opportunities for additional restrictions. For example I would be surprised if mysqld needs netlink or the net_bind_service capability, which leak in (indirectly) through the netservice abstraction. I would actually doubt that this profile should permit any capability at all, citing the Ubuntu wiki: ""... it is generally not a bug in the profile if a non-default configuration is being used by the application."" And adjusting user and group permissions such that mysqld as a different user can access (just the) emails is certainly a non-default configuration, supporting which IMHO reduces the security for the broad majority which just runs something default."
1759084,2018-03-28 12:16:43 UTC,"Thank you for using Ubuntu and reporting a bug. This is not a bug in AppArmor, but in the akonadi Ubuntu package. I'm closing the AppArmor task, but leaving the akonadi task open and adding an 'apparmor' tag."
1759085,2019-09-19 11:57:42 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1759085,2018-03-30 06:53:17 UTC,Interface data is needed for filtering and on the listing page as well as displaying the primary MAC address. Removing interface data may save some data on details page load but would complicate handler code as get() would have to send less data then list()
1759086,2018-03-30 06:36:16 UTC,"After looking closely at how our websockets work I think this will require a large amount of effort for little gain. Machines need storage information for filters, listing, summary, and results. The only time this would save data is on the interfaces page."
1759086,2019-09-19 11:57:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1759089,2018-05-07 08:55:20 UTC,Can we use the svg file directly or do we need a PNG icon?
1759089,2018-05-08 03:37:00 UTC,From snapd daemon/api.go is suggests anything named icon.* will work. From GNOME Softwares point of view - we're happy to render .svgs. Not sure what the snap spec requires.
1759092,2019-09-19 12:00:06 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1759096,2018-04-28 10:41:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759098,2018-04-19 21:00:05 UTC,This issue was fixed in the openstack/puppet-designate 13.0.0 release.
1759098,2018-04-19 21:04:35 UTC,This issue was fixed in the openstack/puppet-panko 13.0.0 release.
1759098,2018-04-19 21:03:57 UTC,This issue was fixed in the openstack/puppet-octavia 13.0.0 release.
1759098,2018-04-19 21:03:28 UTC,This issue was fixed in the openstack/puppet-neutron 13.0.0 release.
1759098,2018-04-19 21:02:48 UTC,This issue was fixed in the openstack/puppet-mistral 13.0.0 release.
1759098,2018-04-19 21:02:34 UTC,This issue was fixed in the openstack/puppet-manila 13.0.0 release.
1759098,2018-04-19 21:02:20 UTC,This issue was fixed in the openstack/puppet-magnum 13.0.0 release.
1759098,2018-04-19 21:02:04 UTC,This issue was fixed in the openstack/puppet-keystone 13.0.0 release.
1759098,2018-04-19 21:01:51 UTC,This issue was fixed in the openstack/puppet-ironic 13.0.0 release.
1759098,2018-04-19 20:59:39 UTC,This issue was fixed in the openstack/puppet-cloudkitty 2.0.0 release.
1759098,2018-04-19 21:01:29 UTC,This issue was fixed in the openstack/puppet-heat 13.0.0 release.
1759098,2018-04-19 21:01:16 UTC,This issue was fixed in the openstack/puppet-gnocchi 13.0.0 release.
1759098,2018-04-19 21:01:03 UTC,This issue was fixed in the openstack/puppet-glare 2.0.0 release.
1759098,2018-04-19 21:00:47 UTC,This issue was fixed in the openstack/puppet-glance 13.0.0 release.
1759098,2018-04-19 21:00:32 UTC,This issue was fixed in the openstack/puppet-freezer 2.0.0 release.
1759098,2018-04-19 21:00:19 UTC,This issue was fixed in the openstack/puppet-ec2api 13.0.0 release.
1759098,2018-04-19 20:59:53 UTC,This issue was fixed in the openstack/puppet-congress 13.0.0 release.
1759098,2018-04-19 21:05:04 UTC,This issue was fixed in the openstack/puppet-sahara 13.0.0 release.
1759098,2018-05-16 08:18:27 UTC,"Change abandoned by Vu Cong Tuan (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/568465
Reason: Hi Tobias Urdin,
Thanks for your comment.
This patch will be abandoned then."
1759098,2018-04-19 21:06:25 UTC,This issue was fixed in the openstack/puppet-zaqar 13.0.0 release.
1759098,2018-06-06 12:41:11 UTC,This issue was fixed in the openstack/puppet-watcher 13.1.0 release.
1759098,2018-06-06 12:40:50 UTC,This issue was fixed in the openstack/puppet-vitrage 3.1.0 release.
1759098,2018-06-06 12:40:39 UTC,This issue was fixed in the openstack/puppet-trove 13.1.0 release.
1759098,2018-06-06 12:38:32 UTC,This issue was fixed in the openstack/puppet-nova 13.1.0 release.
1759098,2018-06-06 12:38:05 UTC,This issue was fixed in the openstack/puppet-neutron 13.1.0 release.
1759098,2018-05-23 07:49:49 UTC,"Change abandoned by Vu Cong Tuan (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/569920
Reason: Hi Tobias Urdin,
Thanks for your comment.
This change will be abandoned then."
1759098,2018-05-22 04:24:04 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/569920"
1759098,2018-04-19 21:05:21 UTC,This issue was fixed in the openstack/puppet-tacker 13.0.0 release.
1759098,2018-05-16 08:30:58 UTC,"Change abandoned by Vu Cong Tuan (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/568460"
1759098,2018-05-15 06:44:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/568465"
1759098,2018-05-15 06:36:06 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/568460"
1759098,2018-05-05 02:11:51 UTC,"Reviewed:  https://review.openstack.org/558434
Committed: https://git.openstack.org/cgit/openstack/puppet-vitrage/commit/?id=e6fc31d0ad67b488c25a28188446e0a3aefd6ad8
Submitter: Zuul
Branch:    master"
1759098,2018-05-04 14:25:11 UTC,"Reviewed:  https://review.openstack.org/558983
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=fe4fc654f4e45cba0293c94f1b16bfda7d2a7a83
Submitter: Zuul
Branch:    master"
1759098,2018-05-03 18:25:05 UTC,"Reviewed:  https://review.openstack.org/558454
Committed: https://git.openstack.org/cgit/openstack/puppet-ceilometer/commit/?id=54aa99c544e0c1fb2ad813a92fbb5a61d2717391
Submitter: Zuul
Branch:    master"
1759098,2018-05-02 19:31:43 UTC,"Reviewed:  https://review.openstack.org/558451
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=20d93c4148c3d5082315263e7754267f50cb46bd
Submitter: Zuul
Branch:    master"
1759098,2018-04-23 17:23:50 UTC,"Reviewed:  https://review.openstack.org/558437
Committed: https://git.openstack.org/cgit/openstack/puppet-watcher/commit/?id=1c23b8e61e27eb0ae88f5dbc73da9dd95c94873e
Submitter: Zuul
Branch:    master"
1759098,2018-05-15 19:17:17 UTC,"Reviewed:  https://review.openstack.org/558431
Committed: https://git.openstack.org/cgit/openstack/puppet-trove/commit/?id=4e3341f58988bf938b409cc35a97b8ba57d87a07
Submitter: Zuul
Branch:    master"
1759098,2018-04-19 20:59:22 UTC,This issue was fixed in the openstack/puppet-cinder 13.0.0 release.
1759098,2018-04-03 09:00:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558446"
1759098,2018-04-05 02:59:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558983"
1759098,2018-04-03 08:58:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558442"
1759098,2018-04-03 08:58:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558441"
1759098,2018-04-03 08:58:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558440"
1759098,2018-04-03 08:58:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558439"
1759098,2018-04-03 08:57:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558438"
1759098,2018-04-03 08:57:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558437"
1759098,2018-04-03 08:57:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558436"
1759098,2018-04-03 08:57:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558435"
1759098,2018-04-03 08:56:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558434"
1759098,2018-04-03 08:56:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558433"
1759098,2018-04-03 08:56:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558432"
1759098,2018-04-03 08:55:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558431"
1759098,2018-04-03 08:47:04 UTC,"Change abandoned by zhongshengping (chdzsp@163.com) on branch: master
Review: https://review.openstack.org/558419"
1759098,2018-04-03 04:58:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558361"
1759098,2018-04-03 03:17:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558344"
1759098,2018-04-19 20:58:53 UTC,This issue was fixed in the openstack/puppet-barbican 13.0.0 release.
1759098,2018-04-03 03:03:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558340"
1759098,2018-04-03 08:59:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558443"
1759098,2018-04-03 08:59:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558444"
1759098,2018-04-03 07:59:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558419"
1759098,2018-04-03 08:59:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558447"
1759098,2018-04-03 08:59:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558445"
1759098,2018-04-04 19:34:42 UTC,"Reviewed:  https://review.openstack.org/558827
Committed: https://git.openstack.org/cgit/openstack/puppet-keystone/commit/?id=b5a94c653fbceab117db082538f80dbfc5fb2b2c
Submitter: Zuul
Branch:    master"
1759098,2018-04-04 15:41:26 UTC,This change affects downstream as a lot of the providers depend on auth_uri.  We need to keep this in place and make sure that we update all providers to use the new URL.
1759098,2018-04-04 13:55:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/558827"
1759098,2018-04-04 10:47:51 UTC,"Reviewed:  https://review.openstack.org/558450
Committed: https://git.openstack.org/cgit/openstack/puppet-ironic/commit/?id=0f3ff5e94818f0689ff5b5fe11f0fa01916c127b
Submitter: Zuul
Branch:    master"
1759098,2018-04-04 07:58:05 UTC,"Reviewed:  https://review.openstack.org/558361
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=dfd67c27a3b77b42d03fd2c7323c2447e1fada52
Submitter: Zuul
Branch:    master"
1759098,2018-04-04 06:43:03 UTC,"Reviewed:  https://review.openstack.org/558344
Committed: https://git.openstack.org/cgit/openstack/puppet-keystone/commit/?id=73d07c00f4e05cb14408f16560cbe20283955a1e
Submitter: Zuul
Branch:    master"
1759098,2018-04-04 02:40:31 UTC,"Change abandoned by zhongshengping (chdzsp@163.com) on branch: master
Review: https://review.openstack.org/558419
Reason: see another patch[1]."
1759098,2018-04-05 02:54:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558982"
1759098,2018-04-03 09:02:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558455"
1759098,2018-04-03 09:02:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558454"
1759098,2018-04-03 09:01:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558453"
1759098,2018-04-03 09:01:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558452"
1759098,2018-04-03 09:00:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558448"
1759098,2018-04-03 09:01:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558451"
1759098,2018-04-03 09:01:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558450"
1759098,2018-04-04 00:59:31 UTC,"Change abandoned by zhongshengping (chdzsp@163.com) on branch: master
Review: https://review.openstack.org/558419"
1759098,2018-04-03 09:00:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558449"
1759102,2018-03-27 06:44:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/556764"
1759117,2019-11-01 10:24:53 UTC,Downstream report: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel-profiles/+bug/1759117
1759140,2018-04-08 14:18:48 UTC,Upstream bug : https://bugs.kde.org/show_bug.cgi?id=392434
1759140,2018-04-12 20:13:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759140,2018-04-12 20:27:04 UTC,This inability to easily set umask is not specific to Kubuntu or Dolphin.
1759143,2018-03-27 07:28:02 UTC,"StacktraceTop:
 g_assertion_message () from /tmp/apport_sandbox_s2x4y_qg/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message () from /tmp/apport_sandbox_s2x4y_qg/lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_widget_get_parent_window (widget=0x56126587e9b0) at ../../../../gtk/gtkwidget.c:10691
 ?? ()
 ?? ()"
1759143,2018-04-11 07:28:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759145,2018-03-27 19:24:04 UTC,"it doesn't seem unreasonable to expect that if a charm uses a tool it
ensures it is installed beforehand."
1759145,2018-05-16 11:02:18 UTC,The mlocate usage is in hardening in charmhelpers (this is on the ceph-osd charm).
1759145,2018-03-27 18:40:49 UTC,"A deeper question would be:  how and what should charm authors expect to have to declare as dependencies, when the image in use is not a standard cloud image?"
1759145,2018-03-27 08:36:28 UTC,Which Juju provider are you on?
1759145,2018-03-27 09:45:59 UTC,We're using the manual provider with 16.04 images supplied by the cloud hosting company (OVH).
1759145,2018-03-27 08:40:57 UTC,"In QCOW2 cloud image as well:
http://cloud-images.ubuntu.com/releases/xenial/release-20180306/ubuntu-16.04-server-cloudimg-amd64.manifest"
1759145,2018-03-27 07:43:31 UTC,"Currently on customer-site, quick turn around appreciated."
1759145,2018-03-27 10:14:15 UTC,"Then it sounds like it's your responsibility to make sure expected package set is installed before adding nodes for manual provider. Something like
apt-get install minimal^ standard^
and so on."
1759150,2019-04-25 11:47:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759150,2019-04-25 12:49:11 UTC,same problem in container environment. when i do a live migration (suspend/resume) the systemd-resolve doesn't work. i should restart the daemon.
1759158,2018-09-24 11:57:42 UTC,"Thanks for the update, MF. I will mark it as confirmed.
Have a great day.
:)
G"
1759158,2018-09-24 11:55:00 UTC,"Thanks for the update, MF. I will mark it as confirmed.
Have a great day.
:)
G"
1759158,2018-09-24 11:17:48 UTC,"MF, this issue about integration with Gnome Shell notification subsystem."
1759158,2018-09-24 08:31:07 UTC,"I also experience issue 2. (on bionic) of this bug: even though messages are read and correctly marked as read in Thunderbird window, the red notification on Thunderbird dock icon is not updated."
1759158,2018-08-20 00:18:58 UTC,"Hi Eugene,
I haven't forgotten you. I will try to replicate this on my own computer so we can get this bug confirmed.
Thanks
G"
1759158,2018-07-15 19:50:57 UTC,"Ok, thanks for the update, Eugene. I will change the status back to ""new"" and look at next steps.
Take care
:)
G"
1759158,2018-07-15 19:19:45 UTC,"Nothing was changed in Thunderbird notifications since bugreport time.
Still needs improvements."
1759158,2018-07-15 18:55:25 UTC,"Hello Eugene,
Thank you for submitting this bug and reporting a problem with Thunderbird.  You made this bug report some time ago and there have been several versions of Ubuntu and Thunderbird since then."
1759158,2018-03-27 14:47:42 UTC,I was able to reproduce both of these bugs on Bionic Daily.
1759158,2018-08-20 05:32:15 UTC,Thank you!
1759171,2018-03-27 11:08:20 UTC,"That's tracked upstream here:
https://github.com/nodejs/node/issues/18770"
1759171,2018-03-27 11:36:13 UTC,"Is the work complete upstream, and is there a backport available for either 6.12.0 or 8.10.0?"
1759183,2018-04-03 12:12:59 UTC,"As I said in the OP, the status of the machine in MAAS when I tried the first remove was, iirc, ""allocated"" - it was not ""ready"" or ""deployed""."
1759183,2018-04-03 14:22:54 UTC,https://bugs.launchpad.net/bugs/1760808 is for the verbose log messages.
1759183,2018-04-03 09:03:40 UTC,"Given machine 33 seemed to have id ""7kq434"", was this the case that both 33 and 77 had that ID, or is it just that 33 was being torn down (which you would eventually turn into 77)?"
1759183,2018-03-27 12:21:06 UTC,I guess my OP wasn't clear : juju stopped getting stuck in the loop to remove 33/lxd/?? once I forced the removal of the whole machine 33 - it did remove the whole machine without problem.
1759183,2018-03-27 12:15:04 UTC,"The logs are from before machine 33 deletion. They were, IIRC, from /var/log/juju/machine-33.log on machine 33."
1759183,2018-03-27 11:08:44 UTC,So someone thinks it is responsible for machine 33:
1759183,2018-03-27 10:40:55 UTC,"Yes, ""7kq434"" is the MAAS node id. I think what I did after the error above was to force-remove the machine (not the LXD) from juju, recommission it in MAAS and redeploy the application on it. It's currently machine 77. Machines 30 31 32 and 33 don't exist in the model anymore."
1759183,2018-03-27 09:28:17 UTC,"The error messages seem a bit odd.
Specifically, Machiner and Provisioner are actually both complaining about
not being able to find ""7kq434"", which would be a MAAS instance id.
However, Machiner is run for the local machine. So either you should have a
machine ""7kq434"" where those workers are running, or there shouldn't be a
place for them to be running that they would be confused."
1759191,2018-03-27 09:34:33 UTC,"This request is for Landscape Dedicated Server, however I don't see any reason the implementation would end up being specific.  Mentioning just in case."
1759191,2018-03-27 12:48:25 UTC,"Note sometimes there is no real need to reboot (e.g. kernel updated but issues is already livepatched) or sometimes the need is triggered by manual actions. Seems to me like this is a reasonable request, but it's something I'd see as a separate profile (reboot profile?) instead of adding to the existing package profiles. Just a though though."
1759191,2018-03-30 22:36:13 UTC,@simpoir -- agreed to a 'reboot profile'
1759194,2018-03-28 06:05:30 UTC,"can you paste the compute log ? I think you are reboot your compute node and during reboot compute node, some instance is scheduled to be reboot and during the reboot process the instance is not there?"
1759194,2018-04-14 02:55:02 UTC,"having same issue with centos7 all-in-one source build. after reboot server, all instances get into error state, and directory /etc/libvirt/qemu in nova_libvirt is empty. Should nova auto re generate xml when hard reboot an instance?"
1759194,2020-05-19 11:28:46 UTC,Marking it Incomplete. Please provide logs a requested in comment #1. When you do please set the bug status back to New.
1759194,2020-07-19 04:17:30 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1759210,2020-08-13 13:31:13 UTC,Django 2.0 has been supported since this commit.
1759219,2018-11-16 12:57:35 UTC,"Alan, do you mind re-checking it in latest Fedora? Any errors in the journal / system logs?"
1759219,2018-11-16 18:57:34 UTC,"Checked on fedora 29, and again it fails silently, and there's nothing in syslog or journal."
1759219,2020-01-07 11:09:02 UTC,Zyga just tested this on fedora 31 with snapd 2.42.2 and reports it works.
1759234,2018-05-08 04:36:20 UTC,This issue was fixed in the openstack/neutron 12.0.2 release.
1759234,2018-03-28 20:59:01 UTC,"Reviewed:  https://review.openstack.org/554038
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e1446284f0589989029b347b07691775a2667120
Submitter: Zuul
Branch:    stable/queens"
1759236,2018-03-27 20:13:28 UTC,I agree with John.
1759236,2018-03-27 20:59:20 UTC,An error is fine by me - just something I noticed while poking around.
1759236,2018-03-27 11:14:03 UTC,"I would have thought that ""juju deploy --to lxd:X"" where X doesn't exist in
the model should be an error.
I wonder if something changed here with the ""lxd:new"" being added to bundle
deployments."
1759247,2018-03-27 11:37:17 UTC,"Unfortunately I had to delete all logs from this bug report because they contained possibly-confidential information. If you need, I can try to reproduce this on a non-company machine with nothing confidential, and reattach the logs."
1759247,2020-04-15 21:03:30 UTC,Tested this in eoan - hostname had the new name.
1759248,2019-07-28 17:12:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759250,2018-04-24 13:38:53 UTC,"Change abandoned by Max Pavlukhin (<email address hidden>) on branch: master
Review: https://review.openstack.org/563958"
1759250,2018-04-25 20:25:00 UTC,"Reviewed:  https://review.openstack.org/563971
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f6b0f7635c222029fc1b554dffceb579b3e4a846
Submitter: Zuul
Branch:    master"
1759250,2018-04-24 13:57:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/563971"
1759250,2018-04-24 13:57:02 UTC,"Change abandoned by Max Pavlukhin (<email address hidden>) on branch: master
Review: https://review.openstack.org/563970
Reason: wrong author"
1759250,2018-04-24 13:56:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/563970"
1759250,2018-04-24 13:39:39 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/563960"
1759250,2018-04-24 13:34:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/563958"
1759250,2018-04-24 13:55:30 UTC,"Change abandoned by Max Pavlukhin (<email address hidden>) on branch: master
Review: https://review.openstack.org/563960"
1759250,2018-04-24 13:32:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/563956"
1759250,2018-03-28 15:08:48 UTC,"Change abandoned by Max Pavlukhin (<email address hidden>) on branch: master
Review: https://review.openstack.org/556838"
1759250,2018-03-28 15:12:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/557366"
1759250,2018-03-28 15:17:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/557367"
1759250,2018-04-11 20:10:45 UTC,"Reviewed:  https://review.openstack.org/557366
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6e6166bda47bd1fc8687340e479a913e7fc0ed58
Submitter: Zuul
Branch:    master"
1759250,2018-04-24 13:33:03 UTC,"Change abandoned by Pavlukhin Max (<email address hidden>) on branch: master
Review: https://review.openstack.org/563956"
1759250,2018-03-27 12:28:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/556838"
1759250,2018-04-18 13:06:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/562271"
1759250,2018-04-24 12:54:31 UTC,"Change abandoned by Pavlukhin Max (<email address hidden>) on branch: master
Review: https://review.openstack.org/562271"
1759250,2018-04-13 12:07:55 UTC,"Change abandoned by Max Pavlukhin (<email address hidden>) on branch: master
Review: https://review.openstack.org/557367"
1759253,2018-07-25 14:22:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759257,2019-06-03 19:37:18 UTC,"This is handled upstream already, and fix released in disco and later."
1759257,2019-06-03 19:37:58 UTC,"An update to trusty, xenial, bionic and cosmic regarding this will be done soon."
1759257,2019-06-01 00:46:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759258,2019-07-05 15:13:50 UTC,This is fixed in eoan.
1759274,2018-03-27 13:55:34 UTC,"StacktraceTop:
 ?? ()
 call_in_idle_cb (user_data=0x7f6dd4091040) at ../../../../gio/gdbusconnection.c:4851
 g_main_dispatch (context=0x222b0e0) at ../../../../glib/gmain.c:3177
 g_main_context_dispatch (context=context@entry=0x222b0e0) at ../../../../glib/gmain.c:3830
 g_main_context_iterate (context=context@entry=0x222b0e0, block=block@entry=0, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3903"
1759275,2019-09-19 14:46:57 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1759278,2019-03-26 14:40:36 UTC,"My OS is:
$lsb_release -a                                                                                                                                           14:39:55
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic"
1759278,2019-06-18 21:54:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759278,2019-06-18 21:53:57 UTC,Same problem here:
1759278,2019-03-26 14:39:33 UTC,I have the same problem as Stdedos (stdedos)
1759278,2018-08-14 14:49:40 UTC,Same on bionic 18.04:
1759278,2018-07-09 11:02:05 UTC,Workaround is to run command like this:
1759278,2018-07-08 15:09:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759278,2018-08-14 14:50:39 UTC,"My OS is:
$ lsb_release -a
Distributor ID:	LinuxMint
Description:	Linux Mint 19 Tara
Release:	19
Codename:	tara"
1759282,2018-03-27 14:11:25 UTC,The following workaround works:
1759282,2018-04-30 15:25:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1759282,2018-05-07 16:11:57 UTC,Importance low????? You must really be retarded.
1759282,2018-10-13 16:50:52 UTC,Still observing the issue.
1759285,2018-11-09 05:02:21 UTC,"When implementing this feature, the optional support for AUTHENTICATION using x509 client certificates should also be implemented."
1759301,2018-05-09 05:46:21 UTC,"Reviewed:  https://review.openstack.org/566758
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=7589f3c2602f1fc8230e357105940e452920d975
Submitter: Zuul
Branch:    master"
1759301,2018-05-07 20:48:05 UTC,"The charm is executing the ApacheSSLContext when the queens version of the charm does not install apache2. It fails on a2ensite, which does not exist."
1759301,2018-04-18 15:23:27 UTC,reproduced again in CI
1759301,2018-05-07 23:40:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566758"
1759305,2018-07-06 01:20:19 UTC,i dont understand the bug report...
1759313,2018-03-28 16:32:14 UTC,Hello!
1759313,2018-03-29 11:21:01 UTC,Hello
1759316,2018-06-04 13:52:32 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1759316,2018-05-29 12:52:31 UTC,"Reviewed:  https://review.openstack.org/563251
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aaa259d9d34bab4fd168111b7393c000f7b82077
Submitter: Zuul
Branch:    stable/queens"
1759316,2018-03-27 16:18:29 UTC,"The code in [1] was added in Newton, and I think we'd be OK to add a warning if you're not using cells v1 and the osapi_compute minimum version is < 15 in that code as a breadcrumb at least, and we could backport that through to queens, pike and ocata."
1759316,2018-04-20 13:12:40 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1759316,2018-04-20 19:31:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/563251"
1759316,2018-03-28 20:49:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557506"
1759316,2018-04-20 05:21:23 UTC,"Reviewed:  https://review.openstack.org/557506
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eaf6340847c35ace3b4b681a95b8a79a7a3f2491
Submitter: Zuul
Branch:    master"
1759321,2019-01-08 09:32:11 UTC,"I can confirm. That happens to me as well.
I wrote a cleanup script to delete all these resources after test run as a workaround but it would be better to let tempest clean up."
1759321,2018-07-10 04:16:28 UTC,"In a new devstack environment(with default config), running API tests:
there are routers and security groups left."
1759323,2018-04-03 16:34:48 UTC,See also our bug triage conversation for ideas on how to solve this issue.
1759323,2018-04-03 16:40:01 UTC,"Rather than a warning, a simple report indicating which components are not covered by a given YAML input may be more useful.  For an audience looking for a complete install, it can be considered a linter, and solve the request in this issue.  For an audience with a mature deployment, it provides a checklist for operators to ensure they have addressed any absent components in another way."
1759323,2018-04-03 18:19:44 UTC,Thanks Emmet for a succinct summary of the discussion we had on IRC.
1759333,2020-11-13 16:10:28 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1759333,2020-11-16 10:58:19 UTC,"Thomas, I think the issue is there. SSE/MMX weren't yet added for HVF."
1759337,2020-11-13 16:10:55 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1759337,2021-01-13 04:17:21 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1759338,2020-11-13 16:43:16 UTC,"Yes this can be closed, no problems now using open bios to boot Solaris and it does support multiple processors though this is actually slower than one."
1759338,2019-04-23 20:12:31 UTC,"As of QEMU 4 OpenBIOS can boot Solaris again, and it does properly allocate multiple CPUs. Of course, it's a whole lot slower on multiple CPUs which I wasn't really anticipating, but it does work.  (And single CPU is so fast anyway compared to the actual hardware it's emulating!)  So this bug while still applicable can be closed."
1759338,2020-11-13 16:11:18 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1759338,2020-11-13 16:34:19 UTC,"Reporter said in comment #1 that the bug can be closed, so let's close it :-)"
1759343,2019-06-21 19:44:37 UTC,"Okay, pushed Dan's latest fixes to 3.1 (just the first commit, as requested), 3.2, 3.3, and master.  Thanks to all!"
1759343,2019-06-21 16:02:25 UTC,"Okay, I have pushed Dyrcona's (aka Jason's) rel_3_1 reverts to rel_3_1.  Thanks, Jason!"
1759343,2019-06-21 15:56:07 UTC,"Okay, branch is here:"
1759343,2019-06-20 14:32:58 UTC,It turns out that the supplied branch does not work with Evergreen 3.1 and needs to be backed out.  The rel_3_1 branch will require a different fix.
1759343,2019-06-13 21:58:54 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks so much, Jason and Terran."
1759343,2019-01-18 18:08:15 UTC,Here's a branch that makes the Annotate option on the Bills page a persistent workstation setting.
1759343,2019-06-21 15:14:18 UTC,"We've been attempting to release the last couple days, and in trying to sort out the 3.1 breakage noted by Jason above, I noticed what I believe is another bug in this code as committed.  The setting as added to the DB does not match the setting as used in the code, as one is prefixed with 'eg.' and the other is not.  I think in this case we are better off changing the code to match the DB, rather than deal with more DB trouble.  It is a fairly small thing, but releases should probably be re-rolled for 3.2 and 3.3 as well."
1759343,2019-02-05 16:31:47 UTC,"We tested this on 3.2.3 and it works well, thanks Jason!"
1759344,2020-08-15 19:17:01 UTC,Closing because migrated to https://gitlab.com/inkscape/inbox/-/issues/1229.
1759344,2020-08-15 19:40:23 UTC,"oops, sorry, it was this one: https://bugs.launchpad.net/inkscape/+bug/1720822"
1759346,2018-03-27 21:27:54 UTC,"Attached is an updated reproducer that adds 'aa-exec -p env -- ...' (ie, not unconfined). It operates the same (ie, ix still scrubs)."
1759346,2018-03-28 16:06:34 UTC,"FYI, this was discovered because of https://forum.snapcraft.io/t/2-0-lxd-snap-fails-on-sytems-with-partial-apparmor-support/4707"
1759346,2018-03-29 18:44:57 UTC,"Just wondering - if this bug survived so long without being noticed, isn't it a sign that in most cases scrubbing doesn't hurt or is even a good idea?"
1759346,2018-03-29 19:21:49 UTC,These seem like counter arguments. On the one hand you seem to say that scrubbing is ok for ix and then change to suggest modifying ix to not scrub and introduce Ix.
1759346,2018-03-29 19:35:21 UTC,"FYI, I clarified the description that the issue is for 'aa-exec', not everything."
1759349,2018-04-16 09:10:57 UTC,"Maybe we could alter the message to indicate that this applies to systemd where snaps are actually confined. OTOH, i see that this is only visible if you issue `snap debug confinement` command. Including this information in say, `snap version` would make it more accessible."
1759349,2018-04-16 11:23:41 UTC,Proposed a small patch to include confinement mode in `snap version` output. If this is merged we will be able to update hello-world.evil to suggest looking at current confinement mode before filing a bug to snapd.
1759357,2018-03-27 19:27:34 UTC,"This is indeed great documentation, but we don't have similar patron color codes in the web client. The only color I remember seeing is red, which, I believe, appears for several different reasons."
1759357,2019-05-11 04:38:53 UTC,"Set to Won't Fix, because the web client doesn't use a border around the patron name to designate their status, and Sitka no longer offers documentation for this."
1759372,2020-05-15 03:50:07 UTC,https://github.com/juju/juju/pull/11585
1759372,2018-05-08 12:44:16 UTC,"There are several ways to trigger a pubsub: unexpected EOF.
It appears Upgrade is one of them.
I've done it with:
juju enable-ha
juju remove-machine 2"
1759388,2018-10-03 06:26:46 UTC,Still happening in Cosmic 20181002
1759388,2018-10-03 06:42:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759388,2019-05-08 02:35:35 UTC,"FWIW, I did basically the same process on 19.04 and it didn't crash."
1759391,2018-11-10 20:38:58 UTC,"Please allow me to continue to use Ubuntu/Firefox in purchase situations
and collect better data.  None of the extensions I have would be likely to
cause this by design, but there may be some accidental problem than arises
and I will attempt to isolate it for you."
1759391,2018-11-10 19:54:59 UTC,"Hi Stan, the latest example is not something that is reproducible (or not) without registering and attempting to make a purchase. In one of your other bug reports you recognised that Firefox extensions had perhaps caused some of your issues so I assume that you've disabled any or adjusted the setting of any that you might be using when making these purchases. Not sure how to proceed."
1759391,2018-11-10 16:16:33 UTC,"Thank you for digging into this problem.  I think it still exists, in
Firefox 63.  Yesterday I was trying to buy some auto parts from a classic
car dealer (Larry's Thunderbirds and Mustangs) and the same phenomenon
happened.  I could log it, choose the parts, fill out the information on
shipping and credit card, but then when I went to hit the final CONTINUE
button, nothing happened.  No notice, no failure dialog box, no nothing.  I
immediately went over to my MacAir, and did the identical purchase, not one
iota of difference, and the final CONTINUE button worked instantly and
completed my sale.  I have no idea why.  On this man's website, there are
many CONTINUE buttons, and they all work under Ubuntu/firefox except the
last one.  On the MacAir, I used Safari."
1759391,2018-11-10 10:14:00 UTC,"Hi Stan, you should now be using Firefox 63. Is this still an issue?"
1759391,2018-09-09 13:22:13 UTC,"Stan, whether an upgrade to 18.04 solves the problem depends on where the bug is, i.e. in Firefox or in Ubuntu. But I don't see any further examples of the bug to test."
1759391,2018-09-08 13:41:33 UTC,"I understand.  However, I found the bug in other locations and added that
to the bug notice in successive comments.  Maybe one of them is
sufficiently easily accessible so that the difficulties with RZD goe away.
But do you think the update to 18.04 will have solved it incidentally?"
1759391,2018-09-07 20:38:33 UTC,"Stan, I'm not going to attempt to fix the problem. I'm just trying to clear out old untouched and now irrelevant bugs from Launchpad. I don't doubt that there's an issue here but I can't see this progressing very far if the error is on a web page that is not accessible to one or more developers (Ubuntu or Mozilla) without them registering, making a booking and then attempting to make a purchase just to see what the problem is. I'm very sorry but I don't think I can help you with this."
1759391,2018-09-07 20:00:03 UTC,"Hi, Paul, thank you for looking at the bug.  It only appears after you have
gone all the way through the process of picking a train, wagon, seats,
registering and so on, when it is time to give your credit card number.  I
was always logged into the site when I got this far, as much as I can
remember.  I thought it was bizarre that they would have a website problem
right when they were about to get your money, and it wasn't bizarre because
the website has no problem, which I found out when I used Windows.
Something bizarre was in the Ubuntu Firefox thing that prevented the
payment section from responding to my clicks."
1759391,2018-09-06 22:39:06 UTC,"Stan, I've tested the link that you quoted and see exactly the same in Firefox 62, Chrome 69 and Chromium 68. The menu seems to be fully functional. I'll attach a screenshot. Is that what you see? Or do you need to be logged in to the site in order to see the problem?"
1759391,2018-09-09 18:24:32 UTC,"I'm sorry, but I didn't keep records of the other ones, except what I
thought I wrote onto my original bug report, or other ones under my name.
I""ll keep looking for new instances."
1759412,2018-03-27 22:26:37 UTC,"StacktraceTop:
 tcache_get (tc_idx=8) at malloc.c:2943
 __GI___libc_malloc (bytes=145) at malloc.c:3050
 safe_malloc (siz=<optimized out>) at ../../lib.c:151
 mutt_convert_string (ps=ps@entry=0x7ffd73bbccd0, from=from@entry=0x55eb4bdb9177 ""utf-8"", to=0x55eb4c717f20 ""utf-8"", flags=flags@entry=0) at ../../charset.c:503
 imap_utf_decode (idata=idata@entry=0x55eb4c72a410, s=s@entry=0x7ffd73bbcd00) at ../../../imap/utf7.c:283"
1759415,2020-05-26 23:08:20 UTC,"As the Tripleo-UI has been deprecated, this bug is no longer valid."
1759415,2018-04-04 16:54:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558880"
1759415,2018-07-16 13:55:01 UTC,removing the workflows tag.  There is already a workflow for this and it's used in the CLI.  At this point it's only a Web UI specific bug.
1759415,2019-06-13 16:00:21 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/558880
Reason: tripleo-ui has been retired, if this is still needed please target the appropriate branch"
1759417,2018-04-04 16:54:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558880"
1759417,2018-04-05 13:37:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/559087"
1759417,2018-04-06 17:18:05 UTC,"Reviewed:  https://review.openstack.org/559087
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=b65e9a1fe8c8b0deedc342df3cb31df684276aa9
Submitter: Zuul
Branch:    master"
1759417,2019-06-13 16:00:20 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/558880
Reason: tripleo-ui has been retired, if this is still needed please target the appropriate branch"
1759417,2019-08-07 19:01:57 UTC,UI has been deprecated
1759421,2018-04-23 09:07:04 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1021.26
1759445,2018-04-06 16:42:07 UTC,Possibly a reproduction but in this case Xenial is deployed and rsyslog shows the kernel upgraded to 4.4.0-119-generic. These are automated runs and we don't have the console output to confirm a kernel panic.
1759445,2018-04-04 16:42:44 UTC,Mark is pressing to potentially change dist upgrade to detect older firmware versions prior to upgrade to ensure the latest is in place before Ubuntu upgrade
1759445,2018-04-04 16:09:50 UTC,We need to continue to investigate this issue as anyone upgrading a certified hardware with older firware will be stuck. This will be a bad user experience.
1759445,2018-04-03 18:13:25 UTC,"After updating firmware on the servers, we can't reproduce it at all anymore."
1759445,2018-04-02 23:09:12 UTC,"It's possible that the message is related, but it would be difficult to track down without shortening the number of commits to search through between 4.4 and 4.15."
1759445,2018-04-02 20:11:25 UTC,So far we've only been able to produce this by doing bionic deploys.
1759445,2018-03-30 15:51:58 UTC,We reproduced it again... looking to try the testing now.
1759445,2018-03-28 16:50:11 UTC,We can no longer reproduce this.
1759445,2018-03-28 13:37:01 UTC,This bug is a kernel panic when rebooting at the end of a MAAS deployment of bionic; there is no way to run apport-collect.
1759445,2018-03-28 03:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1759445,2018-03-28 03:13:09 UTC,"Hi Eric,"
1759446,2018-04-05 12:25:02 UTC,"Snap beta testing complete, no regressions found. Readyfor promotion. Results here: https://trello.com/c/TFfcOOxs/3-pc-kernel-440-117141-107"
1759446,2018-04-05 12:16:16 UTC,Reset the bug to inprogress...
1759446,2018-03-29 19:18:41 UTC,"Snap beta testing complete, no regressions found. Readyfor promotion. Results here: https://trello.com/c/TFfcOOxs/3-pc-kernel-440-117141-107"
1759446,2018-03-29 19:18:15 UTC,test
1759446,2018-03-29 18:54:30 UTC,"Snap beta testing complete, no regressions found. Readyfor promotion. Results here: https://trello.com/c/TFfcOOxs/3-pc-kernel-440-117141-107"
1759446,2018-03-29 19:10:57 UTC,"Snap beta testing complete, no regressions found. Readyfor promotion. Results here: https://trello.com/c/TFfcOOxs/3-pc-kernel-440-117141-107"
1759446,2018-03-29 18:51:54 UTC,test
1759446,2018-03-29 18:34:02 UTC,"Snap beta testing complete, no regressions found. Readyfor promotion. Results here: https://trello.com/c/TFfcOOxs/3-pc-kernel-440-117141-107"
1759446,2018-03-29 17:36:33 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/TFfcOOxs/3-pc-kernel-440-117141-107"
1759446,2018-03-29 19:17:33 UTC,"Snap beta testing complete, no regressions found. Readyfor promotion. Results here: https://trello.com/c/TFfcOOxs/3-pc-kernel-440-117141-107"
1759453,2018-03-28 03:06:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557124"
1759453,2018-03-28 18:23:04 UTC,"Reviewed:  https://review.openstack.org/557124
Committed: https://git.openstack.org/cgit/openstack/puppet-cinder/commit/?id=624020c60fd7a9201d3359b5a161f18bd8dc30f8
Submitter: Zuul
Branch:    master"
1759453,2018-03-29 01:03:58 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/557561"
1759453,2018-03-29 01:04:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/557562"
1759453,2018-03-29 06:54:59 UTC,"Reviewed:  https://review.openstack.org/557562
Committed: https://git.openstack.org/cgit/openstack/puppet-cinder/commit/?id=01d3e0e9e6c5d33a236a16c25bef1e56b0d7d285
Submitter: Zuul
Branch:    stable/pike"
1759453,2018-03-29 06:55:10 UTC,"Reviewed:  https://review.openstack.org/557561
Committed: https://git.openstack.org/cgit/openstack/puppet-cinder/commit/?id=4011a82f547740bd49844105d9f264965eac0645
Submitter: Zuul
Branch:    stable/queens"
1759453,2018-04-19 20:59:24 UTC,This issue was fixed in the openstack/puppet-cinder 13.0.0 release.
1759453,2018-11-23 05:33:43 UTC,This issue was fixed in the openstack/puppet-cinder 12.4.1 release.
1759453,2019-05-16 23:02:58 UTC,This issue was fixed in the openstack/puppet-cinder 11.6.0 release.
1759455,2020-04-07 20:42:31 UTC,This issue was fixed in the openstack/python-zunclient 4.0.0 release.
1759455,2020-03-30 01:35:27 UTC,https://review.opendev.org/#/c/715595/
1759455,2018-06-25 06:17:46 UTC,I have assigned this to myself. I am working on this
1759455,2018-08-04 17:51:43 UTC,"@Namrata, yes you can assign it to yourself"
1759455,2018-07-18 12:41:46 UTC,"@bharaththiruveedula, are you working on this, if not can I assign it to myself?"
1759455,2018-06-14 02:20:36 UTC,Unassigned due to no activity since 2018-03-28 .
1759455,2018-09-26 01:24:59 UTC,"This bug's title ""Support adding/removing floating IPs"" made me think that it is impossible for a container to have a floating IP address.  Maybe the title should be ""Support adding/removing floating IPs by specifying container instead of port""."
1759462,2019-01-12 12:28:12 UTC,"I can consistently replicate the issue when resuming from suspend. After resuming the shortcuts don't work anymore, running Alt-F2 restart solves the problem."
1759462,2019-01-11 08:56:20 UTC,"""Alt-F2 restart"" temporarily fixes the problem, yes it's ugly, but at least, it's fast."
1759462,2018-12-21 07:02:12 UTC,What did you do with the keyboard?!
1759462,2018-12-20 17:11:42 UTC,The same problem with Yakuake:
1759462,2018-12-14 23:39:20 UTC,"This (keyboard shortcuts not working) happened to me, specifically CTRL+ALT+T not giving me the terminal. I experimented and found that the ALT key was at fault - it wasn't registering. I then found a reference on line (sorry don't have the URL) to this being a keyboard Language issue. I then tried: Settings, Language and Region, then set Language to English (United States) - I had it on English (Australia). My ALT key is now working."
1759462,2018-10-13 17:34:21 UTC,"I don't believe it's important, but like a few others in this thread, I have a Logitech Combo keyboard (MK550)."
1759462,2018-10-13 17:10:32 UTC,"I have the same problem. I have installed Ubuntu 18.04 with Unity using the mini ISO. So I don't have GNOME installed with Unity. Keyboard shortcuts (e.g., launching Terminal or switching between keyboard layouts) don't work. Adding sleep 5 before launching compiz in /usr/lib/systemd/user/unity7.service works but only if I don't lock the screen. After unlocking the screen, shortcuts don't work again. The other solution that I've tried is to toggle ""Commands"" in ""CompizConfig Settings Manager."" This works but only if I don't log out. So I have to redo it every time I log out and log in. Is there any permanent solution to this? This is really irritating."
1759462,2018-10-12 19:48:52 UTC,"have the problem mentioned above, some shortcuts work some don't in particular ctrl-alt-t for opening a terminal, ctrl-alt-c in libreoffice.
What I observe is: ctrl-alt switches input source (I have two keyboards layouts defined en and de) although in the shortcut settings in settings the shortcut for switching between input sources is defined differently.
If I try to change the shortcut to open a terminal from ctrl-alt-t in the settings menu to again ctrl-alt-t, the shortcut ctrl-t is shown in the menue although I pressed ctrl-alt-t. If I accept the selection, the new shortcut ctrl-t works.
When in libreoffice ctrl-alt switches input source and ctrl-alt-c does not work to add comments.
Thus it looks like the problem might be with the alt key. Just guessing"
1759462,2018-10-11 20:42:55 UTC,"For unity, see my comment here: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1188569/comments/15"
1759462,2018-10-09 09:57:27 UTC,Fix from #11 worked only until I locked the screen. After unlock my custom keyboard shortcuts did not work again.
1759462,2018-09-01 19:54:06 UTC,Fix from #11 works for me:
1759462,2018-12-07 16:20:41 UTC,This affects me.
1759462,2019-02-01 15:03:31 UTC,"For folks using Unity, I think I got a solution that doesn't require #11 's awful sleep hack."
1759462,2019-02-28 12:50:41 UTC,"Kubuntu 18.04, KDE Plasma Version 5.12.7, Qt Version 5.9.5, Microsoft Natural keyboard:
Same thing: Although configured in Global Shortcuts, Ctrl-Alt-t does not trigger Konsole"
1759462,2019-04-14 04:51:47 UTC,I am currently using Ubuntu Budgie and I can confirm this issue still occurs with the latest 18.04.2 version. Fresh install and I can only get shortcuts to work using the Alt button. I am using an X240 Lenovo Thinkpad Laptop. If anyone has any possible fixes let us know.
1759462,2019-06-24 17:34:59 UTC,I have the same issue. It has started recently after several months of usage. Super+D works. Most other shortcuts including Ctrl+Alt+T for opening terminal do not work. The physical volume buttons have stopped working too. Tried assigning custom shortcuts but that did not work too. Restarting does not solve the issue. Version: Ubuntu 18.04.2 LTS (Budgie) with all updates installed.
1759462,2018-09-01 19:40:34 UTC,"Upgraded from Ubuntu 16.04 to 18.04 and media keys, Ctrl-`, Ctrl-Alt-T, and many more are not working.
Now I can't assign Ctrl-` any more, very annoying, now I use shift-` but this is a bad fix (it blocks ~)."
1759462,2019-06-24 17:37:32 UTC,It saddens me to see the importance marked as low since this disrupts my workflow.
1759462,2019-07-26 11:58:00 UTC,"Just switched to budgie (from lubuntu) and encountered this issue, specifically while trying to fix the launcher shortcut for 'launch terminal'. After trying a number of the suggested workarounds, including the language/region ones, I dug into gnome settings and found that:"
1759462,2019-07-26 12:08:40 UTC,Forgot to add: this is on disco with budgie* 10.5-0ubuntu1.1 and gsd 3.32.1-0ubuntu1
1759462,2019-10-28 15:22:46 UTC,"Great, #11 - this worked for me, having exactly the same problems.
Dell 17 G7 7790"
1759462,2019-11-16 01:55:44 UTC,"#26 worked for me, although possibly in an unexpected way."
1759462,2020-03-10 07:00:59 UTC," Kubuntu 18.04.04 doesnt have Dolphin shortcut Ctrl+E
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1866763
 Kubuntu 18.04.04 terminal doenst have shortcut ctrl+t
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1866764"
1759462,2020-05-13 09:40:45 UTC,"Had issues with keyboard shortcuts for changing language, up/down volume, open terminal and so on..."
1759462,2020-05-13 09:43:46 UTC,"Just to be clear about the comment I wrote above, the solution is not really related to Skype, its probably just the fact that something new is loading up on log in and removing it will (hopefully) solve the issue."
1759462,2020-06-14 14:30:04 UTC,"My particular problem stemmed from reconfiguring python3 to point to python3.7 instead of python3.6 via update-alternatives. Logging into terminal-only mode (Ctrl + F3), setting update-alternatives to use the system version of python3.6 again, and rebooting solved the issue."
1759462,2019-02-01 16:53:53 UTC,"Nvm, ignore my previous comment."
1759462,2018-08-24 07:10:57 UTC,I had the same problem with sound and brightness hot keys after upgrading to Ubuntu 18.04 on a Lenovo P50 using Unity.
1759462,2018-05-06 19:47:19 UTC,"For myself, it is happening much less frequently. I have only had it once since the final release. I'm curious if there is pattern here with upgrades vs fresh install. (I was a fresh install)."
1759462,2018-08-23 14:19:28 UTC,"I just install 18.04.1.
With Gnome 3, no problem of keyboard shortcuts.
With Unity, some shortcuts don't work (Ctrl+Alt+T, Print screen , Media keys)."
1759462,2018-03-28 12:05:39 UTC,"Thank you for your bug report, does it work under an Ubuntu session?"
1759462,2018-03-28 13:07:09 UTC,"I also experience the same thing from time to time... Sames key stop functioning on my Logitech  K800 keyboard but it is "" intermittent""... IF the problems comes back, I will let you know and troubleshoot "" Report any info you want"
1759462,2018-03-28 20:23:47 UTC,15 hrs later - keyboard still functioning as expected with caffeine on. Probably going to stop soon and see if I can get it to break.
1759462,2018-04-14 16:20:01 UTC,Additional Info:
1759462,2018-04-14 16:21:38 UTC,I had forgotten to update my comment (wrote on 2018-03-28: ) - About a day later the behaviour returned and the caffeine test was not effective.
1759462,2018-04-29 05:07:20 UTC,Like #3 I also have the Logitech K800 wireless keyboard.
1759462,2018-04-29 17:07:00 UTC,"Reply to #8, problem seems to have gone away on it's own today. Had tried multiple DE's that didn't work and went into Unity. A message that ""Updates are available"" appeared. Clicking on it installed nothing but probably ran `sudo apt update`, `sudo apt upgrade` in the background. Rebooted into 16.04. Later rebooted into 18.04 test environment and `Ctrl`+`Alt`+`T` and media keys are working."
1759462,2018-05-06 15:47:24 UTC,I'm also experiencing the exact same issues.
1759462,2018-05-06 17:45:52 UTC,I've been able to get a workaround for this issue.
1759462,2018-05-14 03:24:38 UTC,I just had it come back. Just cannot nail it down (pattern).
1759462,2018-05-14 03:26:15 UTC,"@arter97 - in my scenario, I have never had Compiz running (Does not come on Ubuntu Budgie)"
1759462,2018-05-21 09:06:27 UTC,"I have the same keyboard shortcut problem ctrl-alt-t  doesn't work. It starts once i login with Unity, and after switching between GNOME and Unity couple of times and restart, it starts to work again."
1759462,2018-05-23 06:35:22 UTC,"I have the same problem as well: After fresh install ubuntu 18.04 on the x360 spectre 13 inch 2017 version, the shortcut Ctrl+Alt+T to open the terminal doesn't work."
1759462,2018-03-28 14:22:09 UTC,Another test I just completed. In a situation where my shortcuts were working… I put caffeine on to prevent sleep or hibernation… and my shortcuts are still working. Granted I was not doing a lot on the machine over this time… Used it for a bit and then went to bed. But 8 hrs later. still good. I’m going to work shortly and I might try to leave my laptop running for my commute and then use the machine through the day with caffeine on. See how it goes.
1759462,2018-05-23 15:11:02 UTC,"Problem solved itself after logging out (from Unity), logging back into Ubuntu, logging back out and back into Unity. Since then the shortcuts work perfectly."
1759462,2018-06-28 16:19:38 UTC,Changing the keyboard input method system to none fixed my problem.  The left control key is working great.  [ctrl] [alt] T brings up the terminal window from the left side as well as the right.  Now I just need to learn some terminal commands!  Thanks very much for the assist.
1759462,2018-08-18 08:21:43 UTC,Fresh install of 18.04.1 + Unity
1759462,2018-06-28 10:02:48 UTC,seb - various comments here indicate that this affect ubuntu session - so it seems generic ... or at least to GNOME based desktops like Ubuntu and Ubuntu Budgie.  Changing from incomplete to confirmed.
1759462,2018-06-28 02:26:13 UTC,"One thing I’ve noticed is that on budgie, when you restart the window
manager, keyboard shortcuts begin working again. I’m curious if that would
work for you…
On Wed, Jun 27, 2018 at 5:50 PM Mike Edwards <email address hidden>
wrote:"
1759462,2018-06-28 00:43:25 UTC,Thanks for the question.  My desktop is just Ubuntu.  I'm not familiar with Budgie.
1759462,2018-06-28 10:00:04 UTC,Mike - just wondering if this is an ibus issue - UB has had various people confirm that the following seems to fix/help - https://discourse.ubuntubudgie.org/t/volume-up-down-calculator-ctr-altl-t-windows-key-a-and-more-not-working-anymore/140/75
1759462,2018-06-27 21:21:26 UTC,"I have a fresh install of 18.04 on an LG Gram.  The [control] [alt] T keys do not open the terminal.  Within the terminal, the control keys don't work either.  This is frustrating."
1759462,2018-06-27 09:27:21 UTC,"I have a fresh Ubuntu 18.04 install and experience the same problems: some keyboard shortcut do not work all of a sudden (they worked before, on the same installation)"
1759462,2018-06-06 15:39:39 UTC,"On a fresh install with just the updates of today 2018-06-06, I have problems with Ctrl-Alt-Fn to switch terminals. It fails being logged in (at virtual console from Ctrl-Alt-F7) and from the login screen (Ctrl-Alt-F1). I thought console terminals had been disabled but ended up reading this bug."
1759462,2018-05-23 19:48:04 UTC,Have confirmed this to be an issue on other distros besides Ubuntu budgie. Usually restarting the window manager solves it. Wondering if it is something to do with gnome 3.28.
1759462,2018-08-23 16:11:51 UTC,I am having the same issue
1759462,2018-06-27 23:13:01 UTC,"I have seen some people who have made these types of comments with desktops
other than Budgie, Can you confirm which one you are on?
On Wed, Jun 27, 2018 at 2:31 PM Mike Edwards <email address hidden>
wrote:"
1759462,2018-05-23 06:38:39 UTC,Just want to mention that the hotkey doesn't work on Wayland as well as Xorg. The DE is GNOME.
1759473,2019-11-22 21:48:52 UTC,"Reviewed:  https://review.opendev.org/541152
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad78f24812df8e83c188b100d05b1c5a577c8f84
Submitter: Zuul
Branch:    master"
1759474,2018-03-28 05:19:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759475,2018-03-28 05:22:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759478,2018-03-28 06:04:19 UTC,"I'm not sure how patches are done. I cloned the git repo and it had a .gitreview file but this pointed to the upstream code, not the debian packaging code?"
1759478,2018-03-28 05:51:37 UTC,I should mention they are included in the package and installed at /usr/lib/python2.7/dist-packages/manila_ui/local/enabled/
1759483,2018-03-29 16:47:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759483,2018-04-18 15:15:42 UTC,I'm on Debian testing and installed the update from unstable:
1759483,2018-04-18 15:19:54 UTC,Note the command mentioned in the debian thread:
1759483,2018-04-30 08:31:28 UTC,"As a temporary workaround, downgrading libgs9-common, libgs9 and ghostscript packages to version 9.21 from the Artful repositories helps."
1759483,2019-05-13 15:31:52 UTC,Upcoming Ubuntu 19.10 is also affected:
1759483,2019-05-13 15:35:46 UTC,It works on bionic.
1759488,2018-03-28 06:57:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557163"
1759488,2018-06-07 09:28:07 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/557163"
1759490,2018-03-28 17:17:13 UTC,@Bob-  You can drag a track that doesn't require changing a second track that also violates the clearance rule.
1759492,2020-11-10 16:24:54 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1759492,2021-01-10 04:17:39 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1759494,2018-04-13 23:39:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759494,2018-08-06 10:35:51 UTC,"I just like to add that in the absence of other alternative(s), it is unwise to remove system-config-lvm from the repository. Much more so when there is no apparent reason (Xorg being still the display server used in Ubuntu...)."
1759494,2018-10-06 14:55:30 UTC,"Really, no one?"
1759494,2018-11-20 04:52:55 UTC,"please put this back in , Wayland caused too many other problem and has been given the boot
had to install using ubuntu server for LVM raid function but now no LVM"
1759497,2018-07-30 09:41:07 UTC,-- GitLab Migration Automatic Message --
1759497,2018-03-29 00:55:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759497,2018-03-28 16:07:45 UTC,"Each ""mempool"" in pulseaudio is 64 MB by default, and there's one mempool per client. Maybe gnome-shell has multiple connections to pulseaudio? 8 connections sounds excessive, though... Maybe the server's own mempool is visible in the client memory mapping too, so perhaps two mempools per connection are visible in the client memory map. 4 connections sounds still a bit much, though."
1759497,2018-03-28 07:24:17 UTC,"Created attachment 138392
gnome-shell-all-mmaps-at-startup.pdf"
1759497,2018-03-28 07:36:07 UTC,Looks like maybe gnome-shell's use of libcanberra might be one of the triggers.
1759497,2018-03-28 07:21:21 UTC,Although this may not be a bug. It might just be reserved address space with very little physical memory impact.
1759497,2018-03-28 07:40:36 UTC,"Also upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/159"
1759502,2018-03-28 07:48:57 UTC,"StacktraceTop:
 PyCData_clear (self=0xb1bd177c) at ./Modules/_ctypes/_ctypes.c:2575
 PyCData_dealloc (self=0xb1bd177c) at ./Modules/_ctypes/_ctypes.c:2587
 subtype_dealloc (self=0xb1bd177c) at ../Objects/typeobject.c:1222
 frame_dealloc (f=0xb1a5bbfc) at ../Objects/frameobject.c:462
 _PyEval_EvalCodeWithName (_co=_co@entry=0xb3cae1d8, globals=globals@entry=0xb3cad414, locals=locals@entry=0x0, args=0xb1a5bbb4, argcount=2, kwnames=0xb4539598, kwargs=0xb1a5bbbc, kwcount=<optimized out>, kwstep=1, defs=0xb3cadba0, defcount=3, kwdefs=0x0, closure=0x0, name=0xb77ed688, qualname=0xb77ed688) at ../Python/ceval.c:4164"
1759502,2018-03-30 06:47:36 UTC,"Unfortunatelly, this bug is reproduced with installed 32 bit Debian weekly build testing system with equals described testcase.
This system containing too with Liblouis 3.5.0 version, but Orca screen reader version is different, 3.26.0 stable version."
1759507,2018-03-28 08:18:00 UTC,There is also messages pointing out that docker-containerd had bee restarted a few times:
1759507,2018-06-01 00:52:00 UTC,Here it is happening during crond docker-puppet.py
1759507,2021-02-22 16:00:47 UTC,Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1759508,2019-07-03 13:00:09 UTC,"Looks like not, since at least some of the machines I have to hand don't have it installed..."
1759508,2019-07-03 12:41:06 UTC,Does FAI install ubuntu-standard?
1759508,2018-07-26 11:11:02 UTC,"ubuntu-standard depends on psmisc, so this should always been installed; however probably does not hurt to add it to ceph as well."
1759508,2019-07-03 10:58:09 UTC,Actually marking this won't fix - psmisc is guaranteed by the base OS so no need to provide it explicitly.
1759508,2019-07-03 11:36:03 UTC,"We encountered this problem because our 16.04 boxes (installed via FAI) did not have psmisc installed on them, so are you sure about that?"
1759509,2019-01-07 15:04:23 UTC,Marking as Incomplete while waiting for changes to be upstreamed.
1759509,2019-06-12 09:24:57 UTC,This bug was fixed in the package libvirt - 5.4.0-0ubuntu1
1759509,2019-05-13 14:04:28 UTC,Status update: qemu patches now released. Libvirt patches are targeted for release in 19.10.
1759509,2019-04-25 13:19:48 UTC,"------- Comment From <email address hidden> 2019-04-25 09:16 EDT-------
Hi,"
1759509,2019-04-01 21:39:29 UTC,"------- Comment From <email address hidden> 2019-04-01 17:38 EDT-------
Hi,"
1759509,2019-01-31 08:45:08 UTC,"We have the qemu bits in Ubuntu 19.04 now, but I have not heard of any libvirt bits yet.
Furthermore an SRU makes no sense yet as the qemu changes alone won't fix the overall case.
Therefore I'm unassigning myself until there are clear next steps to take."
1759509,2019-01-30 22:24:10 UTC,This bug was fixed in the package qemu - 1:3.1+dfsg-2ubuntu1
1759509,2019-01-07 07:16:39 UTC,I've read through the changes and think they are fine to be added to hour qemu 3.1 currently being prepared for Ubuntu 19.04
1759509,2019-01-31 21:29:36 UTC,"------- Comment From <email address hidden> 2019-01-31 16:19 EDT-------
Yeah, we're still missing the Libvirt part of this feature/fix that will use the new QEMU APIs to enhance dompmsuspend behavior."
1759509,2018-12-04 23:09:23 UTC,"------- Comment From <email address hidden> 2018-12-04 18:02 EDT-------
The current posting is here:
https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg01774.html"
1759509,2018-03-28 11:24:41 UTC,"Please let us know as soon as the needed patches got upstream accepted.
Changing this ticket incomplete for now."
1759509,2018-04-06 08:42:34 UTC,Since 18.10 will likely be 2.12 based it would be nice to get the post 2.12 upstream commit IDs as soon as they are existing as we won't pick it up automagically :-)
1759509,2018-06-22 07:27:29 UTC,Ping for my question of post 2.12 commit IDs - see comment #3
1759509,2018-12-20 23:39:23 UTC,"------- Comment From <email address hidden> 2018-12-20 18:32 EDT-------
The patch series was pushed to QEMU upstream. The commits id are:"
1759509,2018-03-28 10:30:03 UTC,"------- Comment From <email address hidden> 2018-03-28 06:24 EDT-------
Note from Daniel, who is looking into this bug."
1759509,2018-08-20 13:46:47 UTC,"IBM, 18.10 feature freeze is on the 23rd of Aug, any news on the upstream status of this patch?"
1759509,2018-11-19 14:45:00 UTC,Have these patches made its way upstream? if so could you please post links here?
1759509,2018-06-22 10:10:25 UTC,"------- Comment From <email address hidden> 2018-06-22 05:54 EDT-------
Hi,"
1759510,2018-04-03 01:48:16 UTC,"Reviewed:  https://review.openstack.org/557673
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=ab4139e30ca56425fb4f62ebf2d5cb48a0455952
Submitter: Zuul
Branch:    master"
1759510,2018-04-03 04:40:53 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/558359"
1759510,2018-04-04 04:24:21 UTC,"Reviewed:  https://review.openstack.org/558359
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=0da269128ed14096315c9b9e54679fd7e85e9b9b
Submitter: Zuul
Branch:    stable/queens"
1759510,2018-04-19 14:02:04 UTC,This issue was fixed in the openstack/glance 17.0.0.0b1 development milestone.
1759510,2018-04-24 18:11:19 UTC,This issue was fixed in the openstack/glance 16.0.1 release.
1759510,2018-03-29 10:20:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557673"
1759512,2019-07-03 10:58:13 UTC,This appears to be fixed in Wireshark 2.4.6 and newer.
1759512,2018-03-28 09:51:22 UTC,"update, after some experimentation it turns out that this config setting it to blame:"
1759512,2018-03-28 12:49:54 UTC,"On Wed, Mar 28, 2018 at 10:51 AM, Andreas Schultz <email address hidden> wrote:

> update, after some experimentation it turns out that this config setting
> it to blame:
>
>  gui.column.format:
>         ""No."", ""%m"",
>         ""Time"", ""%t"",
>         ""Source"", ""%s"",
>         ""Destination"", ""%d"",
>         ""Protocol"", ""%p"",
>         ""Length"", ""%L"",
>         ""RAT-Type"", ""%Cus:diameter.RAT-Type:0:R"",
>         ""Info"", ""%i""
>
> More specifically, the ""RAT-Type"" column breaks it. After removing that
> line, everything works again.
>
> I'm going to report this upstream.
"
1759517,2018-03-28 09:01:48 UTC,Thank you
1759517,2018-03-30 05:05:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759521,2018-03-28 20:52:07 UTC,"Hello, there's a strong chance this is hardware failure:"
1759521,2018-03-28 21:00:07 UTC,This change was made by a bot.
1759522,2018-03-28 09:16:54 UTC,"Also, `force_size` suboption of `vpc` doesn't work on win version of qemu-img."
1759522,2019-10-27 06:17:41 UTC,Can confirm this is still an issue with 4.1.0.
1759522,2020-02-10 06:25:25 UTC,I confirm this is still exists using qemu-4.2.0.
1759522,2020-02-19 06:08:28 UTC,"I remembered asking a QEMU developer about this. He suggested me to send an email to the developer mailing list, or send messages to IRC channel."
1759522,2020-02-29 00:14:40 UTC,I also discovered just a few days ago the problem that sparse VHD/VHDX image files are not being accepted by Windows.
1759526,2019-02-19 12:56:17 UTC,"There is a confusion between those two packages, gnome-shell-extension-dashtodock and gnome-shell-extension-ubuntu-dock. We follow the ubuntu one."
1759546,2018-03-29 00:55:56 UTC,This seems about heat panel.
1759548,2018-03-29 02:00:22 UTC,"Harald,"
1759548,2018-03-29 11:23:44 UTC,"Hi Daniel, the bug is now reported upstream here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/166"
1759548,2018-04-03 03:19:41 UTC,Thanks.
1759552,2019-01-31 07:33:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/634110"
1759552,2020-10-13 20:26:57 UTC,"Change abandoned by Jonathan Rosser (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/633993
Reason: this is included in stein/train/ussuri and rocky is now extended-maintainance"
1759552,2019-01-30 16:17:20 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/633993"
1759552,2019-02-03 16:59:21 UTC,"Reviewed:  https://review.openstack.org/634110
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_glance/commit/?id=414df67f868867d1b95a4e8c0b4d2f4a30923595
Submitter: Zuul
Branch:    master"
1759552,2018-03-28 18:08:05 UTC,"Reviewed:  https://review.openstack.org/557373
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_glance/commit/?id=97d19586aa7437ffee35d1cf46eb13bc00949c40
Submitter: Zuul
Branch:    stable/pike"
1759552,2018-03-28 15:37:22 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/557373"
1759552,2018-03-28 12:04:54 UTC,I should probably add: deploying with 16.0.8 should be fine too; the problematic change was cherry-picked into stable/pike 4 commits after the 16.0.8 release was cut:
1759552,2018-03-28 12:44:30 UTC,Related: bug 1742951
1759552,2018-04-16 22:58:11 UTC,This issue was fixed in the openstack/openstack-ansible-os_glance 16.0.11 release.
1759557,2019-09-19 12:00:09 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1759570,2018-04-24 19:37:38 UTC,possibly a dupe of bug 1721035.
1759574,2019-06-25 11:27:12 UTC,"Fixed in revision ba7cf09ad55b42d342c3c1d4b1ab9ad2a77d59d1
https://git.launchpad.net/kicad/patch/?id=ba7cf09ad55b42d342c3c1d4b1ab9ad2a77d59d1"
1759574,2019-06-22 06:53:44 UTC,"Thanks to your work I can now assign hotkeys for ""Fill zones"" (Alt+B) and ""Wireframe zones"" (Alt+V) and the hotkeys also are shown properly in the menu on the latest Windows nightly."
1759574,2019-06-21 10:26:49 UTC,The three toolbar zone display modes are available in the hotkeys list as a result of the new hotkeys architecture.
1759577,2020-09-13 07:53:58 UTC,Closing because INVALID: Duplicate issue.
1759577,2018-03-28 16:00:16 UTC,"By the way, the problem can be partially solved by pressing Ctrl++ (Path → Union) with selected problem path, but again it's not always completely remove all overlapped nodes. Also the execution of this operation for each particular path is very time-consuming when there is big amount of paths in the image."
1759577,2018-03-28 15:31:59 UTC,"> Can you have a look?
"
1759577,2018-03-28 14:48:11 UTC,"Just a side note:
I think this is a known issue, but don't have time for research right now. Can you have a look?
And we're on 0.92.3 now in the stable ppa (which doesn't change the problem, though - but you might like to update)."
1759578,2018-05-04 17:34:59 UTC,"i tried two variants:
1) lxc launch images:ubuntu/18.04 u1
2) lxc launch ubuntu:18.04 u2"
1759579,2018-03-28 14:18:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/557347"
1759579,2018-03-28 14:32:18 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/557353"
1759579,2018-03-28 14:32:26 UTC,The same applies to Ocata release as well.
1759579,2018-04-05 21:46:38 UTC,"Change abandoned by Rafal Szmigiel (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/557353
Reason: this time cherry-picking with -x"
1759579,2018-07-13 04:42:38 UTC,"Reviewed:  https://review.openstack.org/557353
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=497fd35c50f80e7d4c033ee3bf58031f15463bb6
Submitter: Zuul
Branch:    stable/ocata"
1759579,2018-07-13 05:30:55 UTC,"Reviewed:  https://review.openstack.org/557347
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=0eacb6c622a4c6b92f0d4fb6c860037999c4cdb7
Submitter: Zuul
Branch:    stable/pike"
1759579,2018-08-08 04:21:35 UTC,This issue was fixed in the openstack/tripleo-heat-templates 6.2.16 release.
1759579,2018-08-08 04:22:39 UTC,This issue was fixed in the openstack/tripleo-heat-templates 7.0.15 release.
1759588,2019-05-17 08:04:18 UTC,"Hi there, it seems we now have a similar request on our new GitLab bug tracker. Please follow there for all future updates. Thank you!"
1759588,2018-03-30 02:25:48 UTC,"Cool - thanks for investigating, Eduard :-D"
1759588,2019-06-16 01:09:31 UTC,"Reopening, as the author of the report explained today that these bugs are not the same."
1759588,2018-03-29 00:06:00 UTC,"I think having both - most important info for copying (maybe in the About dialog?) and some info in the crash dialog - would be useful. Many bugs are not crashes, fortunately."
1759588,2018-03-28 23:17:17 UTC,Great idea!
1759588,2018-03-30 00:19:07 UTC,"Just found the following article via GIMP 2.10.0 RC1 news item:
https://girinstud.io/news/2018/02/automatic-bug-report-stack-traces-gimp/"
1759597,2018-04-25 12:04:32 UTC,The best fit would be etcd3 if it had support for leadership methods because Designate uses them in the coordination code.
1759597,2018-04-25 10:50:54 UTC,In my opinion the decision should be driven by the following question:
1759597,2018-06-14 17:42:11 UTC,"Even better, we could simply use Designate worker and Producer, which do not require the leadership methods mentioned in #5, instead of zone manager and pool manager which are deprecated for removal in Rocky ."
1759597,2018-04-16 13:26:01 UTC,"Would etcd be an option? The etcd charm is well maintained and will form part of the upcoming secrets management work with vault, so I'd rather move to etcd rather than introduce redis or zookeeper - neither charm is fantastically well supported right now."
1759597,2018-04-16 14:06:26 UTC,I don't think redis is much better for coordination purposes than memcached being a mostly in-memory store.
1759597,2018-04-16 09:14:37 UTC,"I discussed that offline with Kiko and Ante and the suggestion is to use redis instead of zookeeper. Anyway, I would still appreciate a feedback before I start working on that."
1759603,2018-08-19 20:00:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759603,2018-11-01 15:32:38 UTC,0.4-0ubuntu5 still a problem in Ubuntu 18.04.1
1759609,2018-03-28 15:43:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557377"
1759609,2018-03-29 14:44:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/557727"
1759609,2018-03-29 18:14:14 UTC,"Reviewed:  https://review.openstack.org/557377
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad4a26e1843bc4cefa2c5b4bb093d692cddfaa49
Submitter: Zuul
Branch:    master"
1759609,2018-03-29 20:24:53 UTC,"Reviewed:  https://review.openstack.org/557727
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=890b74a0c535870d39881c96aa570258ffc4aa21
Submitter: Zuul
Branch:    stable/queens"
1759609,2018-04-02 13:08:59 UTC,This issue was fixed in the openstack/nova 17.0.2 release.
1759609,2018-04-20 13:13:04 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1759610,2018-04-01 14:40:19 UTC,"4.4.0-1016.16 - aws
Regression test CMPL."
1759610,2018-04-03 14:41:52 UTC,No derivative specific changes.
1759610,2018-04-04 09:33:14 UTC,This bug was fixed in the package linux-aws - 4.4.0-1016.16
1759610,2018-04-04 10:35:03 UTC,The package has been published and the bug is being set to Fix Released
1759613,2018-04-04 10:36:13 UTC,The package has been published and the bug is being set to Fix Released
1759613,2018-04-03 15:40:05 UTC,No derivative specific changes.
1759613,2018-04-01 14:27:55 UTC,"4.4.0-1054.63 - aws
Regression test CMPL."
1759613,2018-04-04 09:32:57 UTC,This bug was fixed in the package linux-aws - 4.4.0-1054.63
1759625,2018-04-29 10:50:22 UTC,"The bug didn't say it needed to happen in bionic, but ok…"
1759625,2018-04-29 02:22:34 UTC,If you don't plan to include GIMP 2.10 into bionic then please set status of this bug to Wontfix
1759625,2018-04-29 10:51:25 UTC,"Because of how Launchpad works, I need to wait until 18.10 development opens to mark this wontfix for bionic."
1759625,2018-04-28 00:12:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759625,2018-04-14 03:14:13 UTC,"Unfortunately updating gimp to 2.10 breaks mypaint. Until mypaint is updated to a version that uses the newer version of libmypaint, we will be unable to include gimp at this time as it will cause workflow difficulties with some of our userbase. Releasing gimp 2.10 as an SRU (so long as mypaint can be updated to 1.3 after its release) would be the best route. Another option is to encourage the snap version of gimp 2.10 once released for those who want/need it."
1759625,2018-04-28 02:06:09 UTC,I'm closing this bug. We're not going to include gimp 2.10 in Ubuntu 18.04 LTS so it's probably better to close this bug so that we don't confuse people.
1759633,2018-03-28 17:20:53 UTC,"Hello,"
1759633,2018-04-17 13:12:26 UTC,"Hi,"
1759633,2019-02-05 20:23:11 UTC,moved form https://bugs.launchpad.net/yade/+bug/1759633 to https://gitlab.com/yade-dev/trunk/issues/40
1759633,2018-04-09 01:33:33 UTC,"Hello, Sorry to reply later.
I use a simple example given by Jan.
This is OK:
O.periodic = True
O.cell.setBox(6,10,14)
b1 = sphere((0,0,0),1,color=(1,0,0))
b2 = sphere((2,4,4),1,color=(0,1,0))
b3 = sphere((4,8,8),1,color=(0,1,1))
O.bodies.append((b1,b2,b3))
O.step()
b3.state.vel = 5e-5*Vector3(-1.1,-2,-2.2)
#
from yade import qt
qt.View()
O.run()"
1759636,2020-11-12 17:57:18 UTC,Confirmed that users without the ADMIN_COPY_TAG permission can create tags on the fly.
1759637,2018-03-28 17:20:51 UTC,https://bugs.launchpad.net/mixxx/+bug/1758189
1759647,2018-04-06 15:37:33 UTC,"Issue reproduced
2018-04-06 04:50:06 DEBUG install W: GPG error: http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike Release: The following signatures were invalid: BADSIG 5EDB1B62EC4926EA Canonical Cloud Archive Signing Key <email address hidden>
2018-04-06 04:50:06 DEBUG install W: The repository 'http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike Release' is not signed."
1759647,2018-05-22 19:13:58 UTC,"2018-05-22 02:58:17 DEBUG install W: GPG error: http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike Release: The following signatures were invalid: BADSIG 5EDB1B62EC4926EA Canonical Cloud Archive Signing Key <email address hidden>
2018-05-22 02:58:17 DEBUG install W: The repository 'http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike Release' is not signed.
2018-05-22 02:58:17 DEBUG worker.uniter.jujuc server.go:181 running hook tool ""juju-log""
2018-05-22 02:58:17 INFO juju-log Installing ['apache2', 'glance', 'haproxy', 'memcached"
1759665,2018-03-28 19:56:42 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f34f0b36b9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f34f0b38870 ""double free or corruption (out)"") at malloc.c:5350
 _int_free (have_lock=0, p=0x7ffd6c78cb90, av=0x7f34f0d6bc40 <main_arena>) at malloc.c:4278
 __GI___libc_free (mem=0x7ffd6c78cba0) at malloc.c:3124
 CountCSD (csdnames=csdnames@entry=0x55fe6d1e6fa0) at ../frontends/csladspa/csladspa.cpp:451"
1759665,2018-12-20 01:41:52 UTC,I'm told this is fixed in Ubuntu 18.10 (via the split-out upstream package csladspa 6.11.1).  I'm reasonably sure that cherry-picking https://github.com/csound/csladspa/commit/ecc7f131c5530ad517254dd5b24ba9b2742f69ab will do the job here.
1759665,2018-12-20 03:17:19 UTC,Added SRU information for review.
1759667,2019-01-29 13:26:08 UTC,"Maybe merge this bug with #1777415, since it targets the circumvention of login, too."
1759685,2019-04-05 09:21:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759685,2018-03-28 21:10:01 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fb2d1d70b9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7fb2d1d72870 ""double free or corruption (out)"") at malloc.c:5350
 _int_free (have_lock=0, p=0x564f26bf0790, av=0x7fb2d1fa5c40 <main_arena>) at malloc.c:4278
 __GI___libc_free (mem=mem@entry=0x564f26bf07a0) at malloc.c:3124
 g_free (mem=mem@entry=0x564f26bf07a0) at ../../../../glib/gmem.c:194"
1759688,2018-03-29 21:18:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759699,2018-03-28 22:13:24 UTC,"Stacktrace:
 #0  0x00007fe0719fc517 in ?? ()
 No symbol table info available.
 #1  0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0  0x00007fe0719fc517 in ?? ()
 #1  0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()"
1759699,2018-03-29 06:13:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759699,2018-04-13 08:30:02 UTC,"Calendar crashed on me without doing anything, straight after login."
1759699,2018-06-15 12:55:04 UTC,"gnome-calendar:
  Installed: 3.28.2-1
  Candidate: 3.28.2-1
  Version table:
 *** 3.28.2-1 500
        500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status"
1759701,2018-03-28 22:16:51 UTC,"StacktraceTop:
 ?? () from /tmp/apport_sandbox_fe4dsbuv/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqgif.so
 QFactoryLoader::instance (this=<optimized out>, key=...) at plugin/qfactoryloader.cpp:276
 QIcon::addFile (this=0x7ffe9a719aa0, fileName=..., size=..., mode=mode@entry=QIcon::Normal, state=state@entry=QIcon::Off) at image/qicon.cpp:843
 QIcon::QIcon (this=<optimized out>, fileName=...) at image/qicon.cpp:565
 ScalableEntry::pixmap (this=0x55aad9455240, size=..., mode=QIcon::Normal, state=QIcon::Off) at image/qiconloader.cpp:515"
1759713,2018-03-29 00:21:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1759715,2021-01-06 20:42:55 UTC,So 1.0.0.67-2 has landed in hiruste (which is much closer to debian sid). I also plan to sync hirsute again before freezes and then intend to continue updating ubuntu devel to be as close as possible to debian sid - I will also investigate any SRU opportunities to fix features that are broken in older releases.
1759715,2020-10-27 11:40:20 UTC,"For anyone following, I've reported bug 1901689 to attempt to bring Ubuntu hirsute back into sync with the current Debian sid version, I'll update that bug as progress is made. Then we can hopefully close this one if I am successful."
1759715,2020-10-22 19:23:33 UTC,I was planning on seeing if the situation could be improved in any way over the coming weeks. Lets see if we can improve the package to either by updating or in sync with debian (and then look at potential SRU/backports) over this cycle before removing from the archive.  As there are currently still advantages to using the deb version from the archive over the flatpak version and not everyone wants to install debs from URLs that are not in the archive ...
1759715,2020-10-10 12:02:48 UTC,"Steam is outdated again since Groovy, is not automatically synced from Debian (because of Ubuntu patches/changes that were not backported to Debian) and seems to have no active maintainer in Ubuntu. I think that removing it from the Ubuntu repository and adding it to sync blacklist would be a good solution after all. It is recommended to use the official package from Valve anyway."
1759715,2020-05-14 17:20:28 UTC,Steam was updated in Focal and most of the mentioned issues were resolved. I think this ticket can be closed.
1759715,2020-02-04 14:46:38 UTC,"Anyway, the best solution in my opinion would be to blacklist the Debian Steam packages and work with Valve about providing their official Steam package in Ubuntu repository."
1759715,2020-02-04 12:08:24 UTC,Some updates regarding points from the original Bug Description:
1759715,2020-01-08 19:10:07 UTC,"Any news here? The steam* packages are still available in the Ubuntu 20.04 repositories in an outdated form (1.0.0.54+repack-5ubuntu1 released in February 2018). Please, either update them (1.0.0.61-2 is the latest version in Debian Bullseye) or remove them completely."
1759715,2020-01-20 11:44:38 UTC,Here is a changelog from Debian that contains all the new versions that happened after 1.0.0.54+repack-5ubuntu1:
1759715,2020-01-08 19:12:08 UTC,*(but I really hope that it will get updated to more recent 3.34.2 before Ubuntu 20.04 is released).
1759715,2019-04-17 19:46:26 UTC,"> Snap Status
> -----------
> Currently requires --edge and --devmode so it won't show up
> in the Ubuntu/GNOME Software app yet. Probably won't be
> there in time for the release of Ubuntu 18.04 LTS.
"
1759715,2018-10-15 13:40:07 UTC,"I believe the steam-installer does ""work"". It's just not ideal (it's not an uninstaller)."
1759715,2018-04-14 13:24:48 UTC,Or at least remove the steam-installer package that is not working anymore.
1759715,2018-04-03 19:26:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759715,2020-01-29 11:32:18 UTC,"Here is a ticket about updating the steam/steam-devices packages:
https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1796464"
1759715,2019-06-20 19:56:28 UTC,"In the end, the steam package goes away because it only builds an i386 binary and we are dropping i386 as an architecture."
1759717,2018-08-02 08:17:32 UTC,"This is probably caused by the same issue as
https://bugs.launchpad.net/designate-dashboard/rocky/+bug/1750384"
1759748,2018-03-29 03:22:03 UTC,"Just checked on x86_64, and I don't see the issue there:"
1759748,2018-03-29 05:58:37 UTC,arm64 build for ceph failed to build with a dep-wait; we'll need to sort that out which means a rebuild for all archs.
1759748,2018-04-02 21:31:55 UTC,FYI queens-proposed looks good for arm64 deploy
1759758,2019-09-15 15:33:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759758,2018-05-30 04:17:29 UTC,[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]
1759758,2018-03-29 07:24:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1759758,2018-03-29 05:25:13 UTC,"StacktraceTop:
 XPending (dpy=0x562c4b6257b0) at ../../src/Pending.c:55
 gdk_check_xpending (display=<optimized out>) at ../../../../../gdk/x11/gdkeventsource.c:269
 gdk_event_source_check (source=0x562c4b615e60) at ../../../../../gdk/x11/gdkeventsource.c:306
 g_main_context_check (context=context@entry=0x562c4b65cc10, max_priority=2147483647, fds=fds@entry=0x562c4b698f10, n_fds=n_fds@entry=3) at ../../../../glib/gmain.c:3736
 g_main_context_iterate (context=0x562c4b65cc10, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3900"
1759758,2018-03-30 13:26:27 UTC,This has been a recurring problem since 2010? Can we just have someone look at it a tiny little bit please?
1759760,2018-03-29 07:27:18 UTC,Are you sure you're using a Wayland session? Xorg is still the default in 18.04.
1759760,2018-03-29 07:27:36 UTC,I mean Xorg is now the default in 18.04. It wasn't in 17.10.
1759760,2018-03-29 20:15:30 UTC,"gunter@Marius:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 300mm x 170mm
   1920x1080     59.96*+"
1759760,2018-04-03 03:22:37 UTC,Thanks.
1759760,2018-04-07 14:36:57 UTC,Bug is upstreamed as https://gitlab.gnome.org/GNOME/gnome-shell/issues/185. But since gnome has switched to gitlab launchpad doesn't recognize gnome bug tracker URLs any more so I cannot add the bug URL here.
1759771,2020-11-16 08:14:51 UTC,Zero crashes after 18.10 so consider it fixed.
1759771,2018-03-29 07:12:18 UTC,"The crash occurred in Mesa gallium code (so radeon or nouveau). However the caller was mutter (gnome-shell) from its hybrid GPU logic, which is only used in Wayland sessions."
1759771,2018-04-30 07:56:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759771,2018-04-30 07:56:59 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/6b864c2e9dee175ac64103ea0b6a0bd8652f3e1f"
1759773,2018-03-29 06:47:18 UTC,"I filed the bug on behalf of Ignazio and have confirmed the issue, to be due to the validation checks in the plugin for the device_owner. I am evaluating potential other issues on a HA scenario."
1759773,2018-05-18 07:02:46 UTC,"Can confirm the issue, for someone that knows the code better, is all that needs to be done the actual check from this line in fwaas_plugin_v2.py be updated:"
1759773,2018-08-02 02:49:56 UTC,any update on this bug?
1759774,2018-03-31 14:45:53 UTC,"Reviewed:  https://review.openstack.org/557626
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=7aeb6825ff90da14f32251969b254e2115a3438d
Submitter: Zuul
Branch:    master"
1759774,2018-06-07 20:55:05 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b2 development milestone.
1759775,2018-03-29 07:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1759775,2018-03-29 07:05:22 UTC,Affecting X-HWE-edge ppc64le as well.
1759784,2018-04-03 16:22:54 UTC,Please see our bug triage conversation for the reason of this classification.
1759784,2018-12-01 02:59:13 UTC,"Reviewed:  https://review.openstack.org/551791
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=ada265c8449334538a011300785634774787d54d
Submitter: Zuul
Branch:    master"
1759784,2018-12-04 18:21:01 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/622513"
1759784,2018-12-11 13:57:11 UTC,"Reviewed:  https://review.openstack.org/622513
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=55bfbdbd93882fbb98df706f2a70ceabc08e2e9e
Submitter: Zuul
Branch:    stable/rocky"
1759787,2018-07-27 10:41:00 UTC,Just as another data point:
1759787,2018-07-25 07:48:15 UTC,Using an HP ProLiant DL380 Gen10 (Intel Xeon Gold 5118 CPU @ 2.30GHz) I tested the following kernels (on xenial):
1759787,2018-07-24 09:32:21 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1759787,2018-06-14 06:26:40 UTC,"I've also seen this issue with a Dell R740 server, Xeon Gold 6132 CPU @ 2.60GHz, kernel 4.13.0-37-generic.  Switching to hpet clocksource mitigated it successfully."
1759787,2018-03-29 20:36:44 UTC,"Can you see if this bug also exists in the latest Bionic kernel:
https://launchpad.net/ubuntu/+source/linux/4.15.0-13.14/+build/14466170"
1759787,2018-03-29 08:30:07 UTC,This change was made by a bot.
1759790,2020-09-25 15:46:45 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/639585
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1759790,2020-09-25 15:46:35 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1759790,2020-06-25 13:21:45 UTC,"Due to no activity in this RFE for long time, I'm marking it as ""postponed"" for now. Feel free to reopen it if You will want to discuss that again on drivers meeting and if You will want to work on that."
1759790,2020-03-26 21:40:30 UTC,"Hi Xu Xiaodan,"
1759790,2020-01-10 15:10:14 UTC,"Hi Xu Xiaodan,"
1759790,2019-12-13 09:57:46 UTC,"Hi Bin Lu,"
1759790,2019-10-18 07:39:15 UTC,We discussed this RFE in the neutron drivers meeting last week [1].
1759790,2019-10-11 15:01:32 UTC,"personally i hope it's named ""weight"", ""preference"", or something along the line rather than ""metric""."
1759790,2019-12-19 05:39:06 UTC,"Hi Akihiro Motoki and Slawek Kaplonski,"
1759790,2019-05-29 15:34:31 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.opendev.org/638605
Reason: This patch has been stale for awhile so I'm abandoning it. If it's still valid please push an update to revive it."
1759790,2019-02-27 07:11:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639585"
1759790,2019-02-22 08:47:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638605"
1759790,2018-04-03 01:43:51 UTC,"Yeah, you are quite right @bo, it's about supporting metric setting for the NFV scenario, thanks for the opnion."
1759790,2018-04-03 01:20:16 UTC,"Thanks, @yanxian. Yeah, the first sight is NFV scenario for me. :). Good to know what you want. So I think this may be related a flavor proposal which support metric setting or some higher network/routing function driver, right? Since, namespaced one also support setting that, but may lack the routing function you want. So just a opnion from me. :)"
1759790,2018-04-03 01:07:40 UTC,"Hi, @zhaobo
thanks for the comments.
Yes we can use other L3 backend such as hardware routers or virtual routers
to implement it, not in the namespaced."
1759790,2018-04-02 06:12:28 UTC,"in software vtep and hardware vtep case, its useful to realize multi-path routes for destination."
1759790,2018-03-31 01:40:16 UTC,"That means we may owns multiple routes with different Routers, one link down, the backup one can hold on. I think it is valid in real case, but for namespaced baesd reference implementation, it's hard to find some good usecases. Could u provider some more usecases? Do you use other L3 backend? :)"
1759790,2019-10-03 13:56:05 UTC,"Hi,"
1759794,2018-05-02 03:56:43 UTC,We probably want to add a delay here to give the upgrade time to kick off.
1759796,2020-02-14 02:34:51 UTC,3.20180325ubuntu2~cloud1 in the cloud archive and everywhere else.
1759796,2018-04-03 17:20:19 UTC,"Reviewed:  https://review.openstack.org/557906
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=3a26647c789ebd17064bcf63a88e673bcb0ecca0
Submitter: Zuul
Branch:    stable/queens"
1759796,2018-03-30 08:11:03 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/557906"
1759796,2018-03-29 11:58:28 UTC,"Reviewed:  https://review.openstack.org/557655
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=739c51392f4244d68c023b061ce0300932db285b
Submitter: Zuul
Branch:    master"
1759796,2018-03-29 10:49:55 UTC,"@dino99: Thanks, good to know the package has been fixed upstream."
1759796,2018-03-29 09:18:37 UTC,i mean 'should not be affected' indeed
1759796,2018-03-29 09:17:59 UTC,"if your system is updated, then you should be affected by that typo which was fixed :"
1759796,2018-03-29 09:03:30 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/557655"
1759796,2018-03-29 10:56:01 UTC,"Download it from https://launchpad.net/ubuntu/+source/dh-python,
then do 'sudo dpkg -i dh-python' from the download dir."
1759814,2018-03-29 15:48:05 UTC,"Vanilla kernels (4.15.14 and 4.13.16, build with make-kpkg) suspend&resume without problems."
1759814,2018-04-15 06:39:59 UTC,same problem with 4.13.0-38.
1759814,2018-05-01 11:07:48 UTC,"I switched to a vanilla 4.16 kernel (currently 4.16.6), so no issue for me any more.
Nevertheless is there info that I should contribute?"
1759817,2018-04-16 02:51:21 UTC,some extra info
1759817,2018-04-06 01:52:27 UTC,happens with LibreOffice as well
1759817,2018-03-30 02:51:30 UTC,happens with leafpad as well
1759817,2018-04-02 06:01:52 UTC,happens with terminal as well
1759817,2018-04-02 05:59:37 UTC,happens with boinc as well
1759828,2018-03-30 00:24:32 UTC,dmidecode output from BIOS F22
1759828,2018-03-30 00:15:15 UTC,I'm on the new BIOS.  It requires iommu=pt
1759828,2018-03-29 11:30:06 UTC,This change was made by a bot.
1759833,2018-03-29 12:24:45 UTC,"The attachment ""Translation update for Greek (file: firefox/debian/firefox.desktop.in)"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1759833,2018-03-29 13:05:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759836,2019-08-25 20:19:12 UTC,"Same problem here with Debian 10, Dell Inspiron 13 1370.
Workaround by Florian works for me too."
1759836,2019-08-02 21:32:57 UTC,Ignore my previous two posts.
1759836,2019-08-02 06:05:55 UTC,"'However, the message ""Running in software rendering mode"" and cpu use may have gone down slightly but is still extremely high.' should have been written as 'However, the message ""Running in software rendering mode"" remains and cpu use may have gone down slightly but is still extremely high.'."
1759836,2019-08-02 06:02:23 UTC,"OK, so this is annoying."
1759836,2019-06-30 16:49:00 UTC,"Mortimer, it's still available at the Google cache:
https://webcache.googleusercontent.com/search?https://webcache.googleusercontent.com/search?q=cache:Ulh1YXwMuK8J:https://dev.getsol.us/T5224"
1759836,2019-06-10 07:50:20 UTC,This is a problem for non-dell computers also.
1759836,2019-04-14 14:22:24 UTC,"This problem has been around for a long time and a lot of people have struggled with it. You can find examples such as the following on quite a few help sites, for example"
1759836,2019-01-21 11:07:37 UTC,I too can confirm that the solution Florian posted (modifying /lib/udev/rules.d/97-hid2hci.rules) works.
1759836,2019-04-13 18:30:30 UTC,These nerd-level suggestions all work but the root cause (the real problem) is not solved and will pop up again. How is the non-nerd supposed to do this? ...would you want your neighbor editing your system files????  Someone needs to fix this permanently!
1759836,2019-04-13 17:34:37 UTC,I fix the problem with this approach:
1759836,2019-04-13 17:23:25 UTC,An update: The problem I reported in January went away on its own after a few weeks of having the problem every single day when I booted each morning. I was installing Ubuntu software updates when they became available during that time. There is something going on during boot that causes this problem.
1759836,2019-04-13 14:02:46 UTC,"I have the same problem, that John related."
1759836,2019-03-31 18:07:25 UTC,"I'am not even able to install ubuntu 18.04 because of this, it keeps printing the error message and it's stuck."
1759836,2019-02-05 18:42:24 UTC,still no fix :(
1759836,2019-08-26 22:17:51 UTC,"Lenovo T510 with  4.18.0-25 is also effected, this strangely almost freezes the GUI, despite that systemd-udevd only occupies one core"
1759836,2019-04-13 23:27:55 UTC,"I agree with you, its not the best solution. This bug impact many users! At next release of this softwares this bug has to be fixed."
1759836,2019-08-28 10:08:08 UTC,"As many have commented, this is almost certainly a bug in the bluez udev rule 'hid2hci', that is caused by the introduction of 'bind' and 'unbind' uevents."
1759836,2019-01-08 19:38:50 UTC,"BTW, add to my previous comment an additional symptom:  sometimes my system will ""appear to hang"" entirely during boot (but it will power down normally by briefly touching the power off button when it ""looks like"" it is stuck)."
1759836,2019-08-28 17:42:15 UTC,"> that is a fix for me
"
1759836,2019-10-21 14:47:03 UTC,This bug was fixed in the package bluez - 5.48-0ubuntu3.2
1759836,2019-10-17 15:35:09 UTC,thank you!  marking as verified for bionic :)
1759836,2019-10-17 15:25:08 UTC,"Dan,"
1759836,2019-10-17 10:33:06 UTC,nobody who has been affected by this bug is able to test on Bionic?
1759836,2019-10-08 11:51:58 UTC,"there's a lot of people subscribed to this bug, and presumably interested in seeing it fixed on Bionic; can any of you please test with the package from bionic-proposed and report the results?  Until you do, it's unlikely this fix will be released into bionic-updates."
1759836,2019-10-03 08:27:23 UTC,"The verification of the Stable Release Update for bluez has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1759836,2019-10-03 08:27:15 UTC,This bug was fixed in the package bluez - 5.50-0ubuntu2.1
1759836,2019-09-29 22:17:07 UTC,@stan thanks for testing on Disco.
1759836,2019-09-27 06:59:05 UTC,Works for me with 5.50-0ubuntu2.1 on an old dell.
1759836,2019-09-26 17:03:45 UTC,"@yura9, @mauromol, or anyone experiencing this, if you are running Bionic or Disco, can you please test with the 'bluez' package currently in -proposed?  See the previous 2 comments for instructions how."
1759836,2019-09-24 20:06:13 UTC,"Hello Vinícius, or anyone else affected,"
1759836,2019-01-08 18:42:34 UTC,"When I boot up every day without exception, my machine starts up with one of the CPU cores running at 100%. I see lots of posts on other forums (Unbuntu  etc) going back over a year or more blaming touchpads or nvidia or WiFi. Some even say they can't use their thumb drive if it isn't plugged in when they boot. The problem also mimics a defective thumb drive where you plug it in and Ubuntu doesn't see it (because systemd-udevd doesn't have the cycles to process the newly plugged in USB device). Losing one core makes my machine slower but not too noticeably so. I do see much longer boot times and sometime it will hang entirely during boot. I assume a single core or dual core machine will be drastically slowed down or even unusable. When I search I find other non-ubuntu os's complaining about similar problems."
1759836,2019-09-10 23:25:00 UTC,This bug was fixed in the package bluez - 5.50-0ubuntu4
1759836,2019-09-10 20:18:10 UTC,"> Sorry for the late reply. Here comes the output:
> KERNEL[90619.640204] remove /module/nvidia (module)
> KERNEL[90619.696504] add /module/nvidia (module)
"
1759836,2019-09-10 19:42:47 UTC,"Sorry for the late reply. Here comes the output:
KERNEL[90619.640204] remove   /module/nvidia (module)
UDEV  [90619.659490] add      /kernel/slab/:0012288 (slab)
KERNEL[90619.696504] add      /module/nvidia (module)
KERNEL[90619.697757] add      /kernel/slab/:0012288 (slab)
KERNEL[90619.697792] add      /bus/pci/drivers/nvidia-nvswitch (drivers)
KERNEL[90619.698144] remove   /bus/pci/drivers/nvidia-nvswitch (drivers)
UDEV  [90619.734780] add      /bus/pci/drivers/nvidia-nvswitch (drivers)
KERNEL[90619.760125] remove   /kernel/slab/:0012288 (slab)
KERNEL[90619.780134] remove   /module/nvidia (module)
UDEV  [90619.799634] add      /module/nvidia (module)
UDEV  [90619.863581] remove   /module/nvidia (module)
UDEV  [90619.914399] remove   /bus/pci/drivers/nvidia-nvswitch (drivers)
UDEV  [90619.980993] remove   /kernel/slab/:0012288 (slab)
KERNEL[90619.987727] add      /kernel/slab/:A-0000256/cgroup/filp(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987765] add      /kernel/slab/dentry/cgroup/dentry(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987787] add      /kernel/slab/inode_cache/cgroup/inode_cache(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987807] add      /kernel/slab/:A-0000128/cgroup/pid(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987827] add      /kernel/slab/sock_inode_cache/cgroup/sock_inode_cache(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987846] add      /kernel/slab/:A-0001024/cgroup/UNIX(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987873] add      /kernel/slab/skbuff_head_cache/cgroup/skbuff_head_cache(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987893] add      /kernel/slab/kmalloc-512/cgroup/kmalloc-512(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987918] add      /kernel/slab/:A-0000192/cgroup/cred_jar(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987938] add      /kernel/slab/mm_struct/cgroup/mm_struct(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987956] add      /kernel/slab/:A-0000208/cgroup/vm_area_struct(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988007] add      /kernel/slab/:A-0000064/cgroup/anon_vma_chain(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988029] add      /kernel/slab/anon_vma/cgroup/anon_vma(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988058] add      /kernel/slab/kmalloc-192/cgroup/kmalloc-192(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988076] add      /kernel/slab/kmalloc-1k/cgroup/kmalloc-1k(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988094] add      /kernel/slab/task_struct/cgroup/task_struct(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988113] add      /kernel/slab/:A-0000080/cgroup/task_delay_info(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988128] add      /kernel/slab/:A-0000704/cgroup/files_cache(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988144] add      /kernel/slab/sighand_cache/cgroup/sighand_cache(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.988159] add      /kernel/slab/:A-0001088/cgroup/signal_cache(351529:nvidia-persistenced.service) (..."
1759836,2019-09-03 13:24:11 UTC,"> I tried your fix Dan and it seems not to work.
"
1759836,2019-09-01 18:21:47 UTC,Hi
1759836,2019-08-28 16:59:29 UTC,"Great! Thank you, Dan, that is a fix for me."
1759836,2019-09-24 18:19:46 UTC,"Hello Vinícius, or anyone else affected,"
1759836,2018-12-30 04:41:07 UTC,I can confirm that the solution Florian posted (modifying /lib/udev/rules.d/97-hid2hci.rules) works for me as well.
1759836,2018-06-13 16:57:02 UTC,"As per https://patchwork.kernel.org/patch/10384111/ message from Bluez mailing list, editing 97-hid2hci.rules as follows works around the new uevents added to the kernel in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65"
1759836,2018-05-12 03:43:37 UTC,"Also have Dell Inspiron N5010 systemd-udevd taking up 100% of processor System is overheating
ran strace -fvvp pid and get this info repeating endlessly
epoll_wait(10, [{EPOLLIN, {u32=445921552, u64=94798964078864}}, {EPOLLIN, {u32=445707360, u64=94798963864672}}, {EPOLLIN, {u32=445832272, u64=94798963989584}}], 11, 0) = 3
clock_gettime(CLOCK_BOOTTIME, {tv_sec=2541, tv_nsec=278071571}) = 0
epoll_wait(10, [{EPOLLIN, {u32=445921552, u64=94798964078864}}, {EPOLLIN, {u32=445707360, u64=94798963864672}}, {EPOLLIN, {u32=445832272, u64=94798963989584}}], 11, 0) = 3
clock_gettime(CLOCK_BOOTTIME, {tv_sec=2541, tv_nsec=278167641}) = 0
recvmsg(7, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="""", iov_len=0}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=1790, uid=0, gid=0}}], msg_controllen=32, msg_flags=0}, MSG_DONTWAIT) = 0
recvmsg(7, {msg_namelen=0}, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily unavailable)
sendmsg(3, {msg_name={sa_family=AF_NETLINK, nl_pid=1789, nl_groups=00000000}, msg_namelen=12, msg_iov=[{iov_base=""libudev\0\376\355\312\376(\0\0\0(\0\0\0\37\1\0\0\5w\305\345\261\2Ge""..., iov_len=40}, {iov_base=""ACTION=bind\0DEVPATH=/devices/pci""..., iov_len=287}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, 0) = 327
epoll_wait(10, [{EPOLLIN, {u32=445921552, u64=94798964078864}}, {EPOLLIN, {u32=445707360, u64=94798963864672}}, {EPOLLIN, {u32=445832272, u64=94798963989584}}], 11, 0) = 3
clock_gettime(CLOCK_BOOTTIME, {tv_sec=2541, tv_nsec=284128363}) = 0
recvmsg(3, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=0x000001}, msg_namelen=128->12, msg_iov=[{iov_base=""unbind@/devices/pci0000:00/0000:""..., iov_len=8192}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=0, uid=0, gid=0}}], msg_controllen=32, msg_flags=0}, 0) = 264
getrandom(""\x5c\x05\xb7\x00\xc9\x0e\x92\x24\x64\x4b\x1d\xbe\x21\xad\x25\xab"", 16, GRND_NONBLOCK) = 16
getrandom(""\xa2\x4a\x63\x92\x35\xf3\x63\x78\x5d\xec\x7b\x25\xfe\xe4\xfe\xd5"", 16, GRND_NONBLOCK) = 16
getrandom(""\xed\xfb\x0a\x18\x24\xe4\x07\xdb\xc1\x9e\x4e\xfe\xf5\xcc\xb6\xb3"", 16, GRND_NONBLOCK) = 16
getrandom(""\x98\x96\xbe\xbe\x06\x4b\xe3\x26\xe0\xeb\xb2\xc6\xcc\x17\x3c\x7f"", 16, GRND_NONBLOCK) = 16
getrandom(""\x3a\x5a\x82\x79\xfb\xb7\x32\x02\x58\x05\xdb\x2a\x81\x7a\x16\x50"", 16, GRND_NONBLOCK) = 16
getrandom(""\xb0\xde\x65\xbb\x40\x2e\x1c\x35\x11\xad\x32\x9c\x19\x18\xc7\x33"", 16, GRND_NONBLOCK) = 16"
1759836,2018-05-11 09:15:10 UTC,Happening here on a Dell Latitude E5500
1759836,2018-05-11 09:09:17 UTC,"Same here, problem started after I upgraded from Ubuntu 17.10 -> 18.04 on my Dell Latitude E6500 laptop.
In Ubuntu 18.04 I used 4.15.0-20-generic, now I use 4.13.0-39-generic and now temperatures are normal again."
1759836,2018-05-09 23:02:06 UTC,"Bus 001 Device 009: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c:0000 Broadcom Corp."
1759836,2018-05-09 17:24:20 UTC,Hit this problem after updated Ubuntu 17.10 -> 18.04 on my old Dell Latitude E6400 laptop.
1759836,2018-05-04 05:57:10 UTC,"I have the very same problem using the same distro (Ubuntu 18.04, 64-bit) on Dell Latitude E5400 laptop. Disabling BT from BIOS or removing the aforementioned rule solves the problem but leaves BT unusable."
1759836,2018-12-22 17:54:47 UTC,"Command from Y S Gupta fixed to high cpu load for me.
As this is just a workaround. I suppose this bug should remain open.
Thanks for this, i can now reuse my bluetooth card."
1759836,2018-05-03 05:09:24 UTC,"Also reported on Solus [https://dev.solus-project.com/T5224], Manjaro [https://forum.manjaro.org/t/high-cpu-usage-on-kernel-4-14-and-4-15-from-systemd-udevd-which-seems-to-be-the-synaptic-touchpad-driver/35972] and Gentoo (on the Manjaro page)."
1759836,2018-05-02 12:26:43 UTC,"i have:
 -  stopped systemd-udevd
 -  uninstalled nvidia-compute-utils-396
 - started systemd-udevd"
1759836,2018-05-02 12:21:42 UTC,and cannot disable nvidia-persistenced.service:
1759836,2018-05-02 11:42:45 UTC,"on official bionic , upgraded from artful:"
1759836,2018-05-01 15:00:10 UTC,"I use Dell Inspiron 1545 with Intel® Core™2 Duo CPU P8700 @ 2.53GHz × 2
If I use kernel shipped with 18.04, I get 100% cpu  problem.
If I user kernel 4.14 I get Kernel Panic on system boot up."
1759836,2018-05-01 06:12:37 UTC,"I do see those messages - it's an older Dell Latitude.
I also tried booting with the kernel shipped with 17.10 and the problem doesn't exist there."
1759836,2018-04-30 18:48:15 UTC,Hee ubuntu user
1759836,2018-04-30 15:56:54 UTC,Do you see lines like the next one in your journal?
1759836,2018-04-09 18:58:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759836,2018-03-06 21:09:45 UTC,"Created attachment 274593
dmesg"
1759836,2018-05-12 03:45:29 UTC,Please help this makes my laptop completely usless
1759836,2018-05-14 00:58:24 UTC,Adding some information in case it's useful.
1759836,2018-05-03 06:12:39 UTC,Is there reason to believe that bluez (the bluetoothd process) is involved here? If the problem is low-level bluetooth then the correct package to log that against is 'linux'.
1759836,2018-05-14 20:49:23 UTC,"I have a Dell Inspiron N5010 laptop and this bug affected my system.
hope to fix the bug soon."
1759836,2018-05-14 15:47:44 UTC,"I noticed this problem because my wireles KB/Mouse combo became nearly unusable after upgrading from 17.10 to 18.04. I'm seeing the high CPU consumption as reported above and the dell HID messages as reported above. Also, if I unplug the transceiver for my KB/Mouse it stops working until I reboot."
1759836,2018-06-13 08:37:39 UTC,I had this problem with NVidia after I disabled nvidia card in BIOS.
1759836,2018-06-11 22:36:16 UTC,"Same problem with an old  Dell Inspiron 1545 recently upgraded to Ubuntu 18.04 (4.15.0-22-generic). After disabling Bluetooth in the Bios and removing package Bluez, system is usable again."
1759836,2018-06-04 07:46:01 UTC,"on bionic, stopping udevd and starting it again correct the problem:"
1759836,2018-05-29 16:54:36 UTC,"Removing the bluez package solves the problem for me. After that bluetooth does not work, of course."
1759836,2018-05-28 16:07:41 UTC,I tried it with mainline 4.16.12 and 4.17-rc7 on the Dell Latitude and the problem still exists.
1759836,2018-05-28 04:42:02 UTC,FYI: running with the 4.17-rc6 release candidate of the new kernel from https://wiki.ubuntu.com/Kernel/MainlineBuilds seems to have fixed the issue for me.
1759836,2018-05-28 04:24:46 UTC,"You need to actually downgrade your running kernel to 4.13. Just
downgrading the headers isn't enough."
1759836,2018-05-28 05:05:50 UTC,"And it seems to be fixed also in the current stable kernel, 4.16.11 ."
1759836,2018-05-23 01:59:47 UTC,Interesting read. If they are adding Dell 'features' then maybe also my built in webcam will one day work again as that also doesn't work.
1759836,2018-05-22 23:36:55 UTC,"It's a known kernel bug that Dell bluetooth is broken in kernels >=4.14, so sticking with the old kernel that works for now."
1759836,2018-05-22 07:40:13 UTC,Just upgraded from kernel 4.15.0-20-generic => 4.15.0-22-generic - still the same problem....
1759836,2018-05-20 07:57:41 UTC,"I observed the high cpu usage after upgrading from udev-233 to udev-236/udev-238 on Gentoo Linux. Downgrading back to udev-233 lets me use newer kernels (currently running 4.15.18) without any problems.
Using DELL Latitude E6400 from 2009, with same Broadcom Bluetooth module as mentioned above."
1759836,2018-05-19 17:16:47 UTC,"I also faced the same issue and thanks to the Lumar's comment, workaround mentioned in the link worked for me too:
https://dev.solus-project.com/T5224"
1759836,2018-05-19 02:30:00 UTC,"The bug is present on my system.
It was temporarily solved with workaround from https://dev.solus-project.com/T5224, but I don't use Bluetooth and so don't know if it is now working."
1759836,2018-05-15 12:54:29 UTC,Forget last time to add some details about the problem with the new kernel 4.15.0-20-generic versus 4.13.0-39-generic.
1759836,2018-05-15 02:23:58 UTC,I am using Dell Inspiron 15R (N5010) and this bug affects my system as described above. Waiting for the fix.
1759836,2018-05-26 19:22:03 UTC,"Similar problem for me. Dell E6530, Ubuntu 18.04"
1759839,2020-05-20 08:10:58 UTC,"hi,
I have gone through Docs of pike,queens,rocky versions and found the placement API port error(as mentioned above) in Controller node install and configure in openSUSE and SUSE Linux Enterprise doc. But in later versions from stein the steps with respect to placement API were removed and i think moved to other project , so can anyone help in finding the project or exact location where this bug fix required."
1759839,2020-06-26 13:49:57 UTC,"After discussing this on the nova meeting it seems this bug is invalid. And the other bug [2] was the valid bug, which is already fixed."
1759839,2020-06-04 14:22:34 UTC,"hi ,
i think below bug[1]specifies same as this bug , even through specifically mentioned with stable-pike release.
A fix was released with continuing the Placement API endpoint port as ""8780"" in openSUSE and SUSE Linux Enterprise doc. So do we need to make this bug as duplicate . Even i got -1 from my reviewer , referring to this link[2]. If not can i get a response for what to proceed next."
1759839,2020-05-27 10:17:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/731141"
1759839,2020-05-26 10:25:30 UTC,"Change abandoned by vinay harsha mitta (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/728766"
1759839,2018-10-15 11:39:12 UTC,"> Things would break if anyone is running devstack with WSGI_MODE != ""uwsgi""
"
1759839,2018-03-30 04:55:33 UTC,are you using latest master or some version?
1759839,2018-10-12 20:00:32 UTC,I checked our docs and it looks like we have port 8780 in the OpenSUSE documentation:
1759839,2018-04-03 13:29:18 UTC,"@Thomas note the comment there: "" This virtualhost is only here because some directives can
# only be set by a virtualhost or server context, so that's why the port is not bound."""
1759839,2018-04-03 08:36:19 UTC,"@Chris, in the SUSE package, the default placement port is aligned with the devstack setup (see https://git.openstack.org/cgit/openstack-dev/devstack/tree/files/apache-placement-api.template#n5) where port 8780 is used.
So what do you mean with ""...what people are commonly using for exposing as a placement port..."" ?"
1759839,2018-03-30 11:59:28 UTC,The root problem here is that suse is using a different port from (at least some) deb-based systems.
1759839,2018-03-30 11:57:00 UTC,I agree that 8780 is not aligned with what people are commonly using for exposing as a placement port (8778).
1759839,2018-10-12 20:08:53 UTC,"Regarding the devstack use of port 8780, it looks like devstack deploys services based on the WSGI_MODE variable and can run them either under uwsgi or apache mod_wsgi (example: keystone, placement, glance). So, I'm not sure if we should remove it from devstack if placement supports mod_wsgi. Things would break if anyone is running devstack with WSGI_MODE != ""uwsgi"" since the same setting is used to control keystone, placement, and glance."
1759846,2018-04-03 12:52:40 UTC,"Actually
    systemctl -q is-enabled anacron 2>/dev/null
works to, and is shorter (and more intuitive)."
1759846,2019-03-17 01:07:36 UTC,This is *still* an issue nearly a year on.
1759852,2018-03-30 13:40:54 UTC,"Offtopic, but I've already wondered about this before:
Is the 'portableapps.com' download file the same as the one that is provided from the inkscape.org website?"
1759852,2018-03-30 09:01:59 UTC,"Reading again my last comment I want to clarify: IMHO 14 is a good choice in the gtk-menu option for the menu icons but it's not for the toolbar icons when the inskcape-decoration option is missing. Obviously increasing the gtk-menu (with inkscape-decoration missing) to fix the toolbar icons makes the icons in menus too big.
So to have the best of the two, both the gtk-menu and the inkscape-decoration have to be present and 14 seems a good value for both."
1759852,2018-03-30 14:33:37 UTC,"I can confirm that the file ""share\themes\MS-Windows\gtk-2.0\gtkrc"" is the same for both from portableapps.com and from inkscape.org for version 0.92.3."
1759852,2018-03-30 08:53:13 UTC,"I'm a bit puzzled...
I just rechecked the two situations in Windows XP and Windows 7 putting the same numbers in the inkscape-decoration option and I get the same results.
So I wrote something wrong in my last comment."
1759852,2018-03-29 13:02:10 UTC,"ok,
I discovered one more icon that has also changed in size. It is in the Tool Controls Bar. It's caption reads: ""When locked, change both width and height by the same proportion"""
1759852,2018-03-29 21:32:32 UTC,"Hello LucaDC and Eduard Braun,"
1759852,2018-03-29 16:53:50 UTC,"@koos - are you sure the issue is specific to 0.92.3 (i.e. did not exist in 0.92.2 already)? Maybe it's a change preference? For example ""Pre-render named icons"" is known to cause differences in behavior."
1759852,2018-03-29 15:02:07 UTC,"Another way for achieving the same result is leaving the numbers in the first line in ""share\themes\MS-Windows\gtk-2.0\gtkrc"" as they are and appending at the end of the same line (before the closing double quotes):"
1759852,2018-03-29 14:28:18 UTC,"Hi koos,
please try this manual patch: backup and edit the text file ""share\themes\MS-Windows\gtk-2.0\gtkrc"" (starting from the installation directory), in the first line:"
1759852,2018-03-29 12:57:09 UTC,"second screenshot
to demonstrate the small icons in 0.92.3"
1759852,2018-03-30 08:24:04 UTC,"@Eduard,
for me it's been trial-and-error, I don't know how gtk interprets the numbers, what I've seen is that the same numbers yeld different sizes in Windows XP Classic theme and Windows 7 so I need two different gtkrc files for them (14,14 for XP, 18,18 for 7, and with these the icons look a bit bigger than how they should). I don't have any Windows 8.1 nor Windows 10 installations to try and see if they behave like in Windows 7; if, as I expect, this is the case then I wouldn't spend time in understanding why Windows XP has a different behavior."
1759859,2018-03-29 13:42:28 UTC,"StacktraceTop:
 H2Core::InstrumentComponent::get_layer (idx=<optimized out>, this=<optimized out>) at ./src/core/include/hydrogen/basics/instrument_component.h:109
 H2Core::Sampler::__render_note (this=this@entry=0x56511e90d2c0, pNote=0x56511fa2efd0, nBufferSize=nBufferSize@entry=1536, pSong=pSong@entry=0x56511e968b30) at ./src/core/src/sampler/sampler.cpp:383
 H2Core::Sampler::process (this=0x56511e90d2c0, nFrames=nFrames@entry=1536, pSong=pSong@entry=0x56511e968b30) at ./src/core/src/sampler/sampler.cpp:126
 H2Core::audioEngine_process (nframes=1536) at ./src/core/src/hydrogen.cpp:788
 H2Core::alsaAudioDriver_processCaller (param=0x56511e920cc0) at ./src/core/src/IO/alsa_audio_driver.cpp:84"
1759859,2018-03-29 21:34:07 UTC,"By the way, check your CPU fan, your CPU is overheating."
1759860,2018-05-19 09:47:58 UTC,"Thank you Geoff for pointing to the real solution.  I am a bit scared of making this kind of changes to a system file, but I will give it a try.  Anyway, looking forward to see the fix implemented by Canonical.  Hibernate / Resume from hibernation is for me the solution for my PCs (not notebooks) since Windows XP :-)  You can simply continue where you left off on PCs that are off about 16 hours a day."
1759860,2018-05-19 01:59:25 UTC,"Radu, take a look at this bug - https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297 As you suggested, adding the resume entry to grub worked around my inability to resume from hibernate, but the fix noted in bug #1769297 looks to be the real fix.  I tested it successfully."
1759860,2018-05-17 17:32:56 UTC,"Finally found a solution for this issue => you have to add the kernel parameter ""resume=UUID=<UUID_OF_SWAP_PARTITION>"" to the /etc/default/grub file: edit the file and afterwards sudo update-grub) or use Grub Customizer."
1759860,2018-04-27 15:00:33 UTC,"As reported before, Ubuntu MATE 17.01 with ANY kernel 4.15.x or ANY kernel 4.16.x on the same PC -> Hibernate / Resume from Hibernate work perfectly!"
1759860,2018-04-27 14:57:54 UTC,Installed fresh Ubuntu Bionic 18.04 (release).
1759860,2018-05-15 09:09:00 UTC,After upgrade from 17.10 to 18.04 (via do-release-upgrade) my PC now fails to resume from hibernate.
1759860,2018-04-02 08:49:15 UTC,"Same PC - test installations - same hardware:
Debian 9 (debian-testing-amd64-DVD-1.iso 2018-04-02 06:56  3.6G) with MATE DE, kernel 4.15.0-2-amd64"
1759860,2018-03-29 14:00:07 UTC,This change was made by a bot.
1759860,2018-03-30 01:43:40 UTC,Hibernate / Resume from Hibernate:
1759860,2018-03-30 01:28:52 UTC,Hibernate / Resume from Hibernate:
1759860,2018-03-29 19:40:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1759860,2018-03-29 14:15:04 UTC,"Same PC, Ubuntu MATE 17.10 with Linux Kernel 4.15.02, 4.15.12, 4.15.13, 4.15.14 -> Hibernate & Resume from Hibernate WORK AS EXPECTED."
1759860,2018-04-06 15:58:58 UTC,Ubuntu MATE 18.04 Beta 2 (downloaded today) installed on the same PC.
1759861,2019-05-27 02:18:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759864,2019-08-01 15:05:41 UTC,"Thanks, all.  Issue and fix confirmed.  Merged to 3.2 and above."
1759864,2019-07-31 14:25:02 UTC,Signed off here:
1759864,2019-07-31 14:21:56 UTC,"I think Christine's check-in comment (#3) may be partly caused by bug #1756441 (marking damaged fails silently on in-transit items).  In any case, I agree with abellenir that it seems like a different bug from this one."
1759864,2019-03-12 15:33:41 UTC,"i got the same error as the original report when marking an item as damaged on both the record's holdings view and from a patron's holds tab:
Error: [$injector:unpr] Unknown provider: egItemProvider <- egItem"
1759864,2019-03-12 16:13:50 UTC,I'm curious what happens if you try after applying the branch from bug 1779467 without your branch applied.
1759864,2018-06-07 16:11:42 UTC,Confirmed in 3.1
1759864,2018-03-29 14:26:51 UTC,Confirmed in 3.0.2
1759864,2019-03-12 17:08:20 UTC,"Jason: if i do that, javascript console says:
Error: [$injector:unpr] Unknown provider: egItemProvider <- egItem"
1759889,2020-04-21 01:40:04 UTC,"Thanks, raised here https://gitlab.com/sane-project/backends/-/issues/278"
1759889,2020-04-19 19:35:54 UTC,"It seems that the issue is connected with Sane backend (pixma).
Please check on bug list, if the issue was already reported:
https://gitlab.com/sane-project/backends/-/issues"
1759889,2020-04-18 15:54:40 UTC,"Attached as a file the full output for ""simple-scan 3.34.1"" when scanning 2 pages from the feeder, which still has this bug."
1759889,2020-04-18 23:50:27 UTC,"I checked on Sane supported drivers, and your device is well supported (pixma backend):"
1759889,2020-04-15 21:40:50 UTC,Please provide full debug logs from simple-scanner
1759889,2020-04-19 16:18:47 UTC,"Very similar failure observed - the 1st page scans, but the 2nd fails."
1759896,2018-04-03 16:10:50 UTC,There is documentation here: https://docs.openstack.org/openstack-ansible/latest/user/security/index.html
1759896,2018-04-03 16:12:40 UTC,"COuld you also explain what you're trying to achieve? Do you want https between haproxy and keystone, or is https termination in haproxy + http in the (considered internal) management network enough?"
1759896,2018-04-03 16:59:04 UTC,I am trying to place the ssl certificate on the container. HAPROXY should perform pass-through. That way there is no way to sniff the network and glean passwords from it.
1759896,2018-04-03 17:01:55 UTC,The documentation provided does not work. If you follow it exactly. You will get a broken environment. Weather it is for rabbit or for Keystone.
1759901,2018-05-20 01:53:49 UTC,"Thanks for the report, and I apologize for the long delay in acknowledging it. I so seldom get any kind of communication about the project that I forgot to check the e-mail box this mail goes to."
1759901,2018-05-20 21:33:29 UTC,"I installed a bionic chroot today and installed the application from the xenial repo. It appears to mostly work as expected. There is an error message when attempting to load the config, but it doesn't appear to be a major issue. I can configure tunnels and ports and successfully start the tunnel. I can use the ports associated with the tunnel once it's started."
1759906,2019-03-08 06:06:21 UTC,I took the time to update gSTM for gtk3 and removed the gnome dependencies. Source is available at https://github.com/dallenwilson/gstm along with links to packages for Ubuntu and Gentoo.
1759906,2018-05-21 14:03:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759906,2018-03-30 08:33:00 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1759906,2018-10-03 06:39:18 UTC,"This tool was essential for my work, so when it stopped working, and I couldn't find anything similar, I created my own version."
1759911,2019-09-19 11:57:47 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1759923,2018-04-02 19:36:34 UTC,This bug was fixed in the package linux-azure-edge - 4.15.0-1005.5
1759923,2018-04-02 20:02:33 UTC,The package has been published and the bug is being set to Fix Released
1759924,2019-02-09 13:42:54 UTC,"Reviewed:  https://review.openstack.org/626408
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=245364ece1689853bf33ac25d7319618d064d909
Submitter: Zuul
Branch:    stable/queens"
1759924,2019-04-26 17:16:19 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1759924,2019-04-15 16:11:41 UTC,"Reviewed:  https://review.openstack.org/626413
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b3e45387ce1979b394b38d6e124e001e2898c1a
Submitter: Zuul
Branch:    stable/ocata"
1759924,2019-03-26 04:18:11 UTC,"Reviewed:  https://review.openstack.org/626409
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c7bb9b1652b6df3e0a353a5c9f4cf70299c4e5e7
Submitter: Zuul
Branch:    stable/pike"
1759924,2019-03-24 23:40:06 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1759924,2019-03-24 23:04:41 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1759924,2019-03-22 03:49:07 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1759924,2018-12-20 04:19:54 UTC,"Reviewed:  https://review.openstack.org/626407
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3e38d1cf16ca29948be499aa37e2494ffd001f12
Submitter: Zuul
Branch:    stable/rocky"
1759924,2018-03-29 18:52:32 UTC,I think this was the scenario described in IRC for this bug:
1759924,2018-12-19 23:49:36 UTC,"Reviewed:  https://review.openstack.org/559828
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=93802619adde69bf84d26d7231480abb4da07c91
Submitter: Zuul
Branch:    master"
1759924,2018-12-19 23:29:20 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/626409"
1759924,2018-12-19 23:23:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/626408"
1759924,2018-12-19 23:20:40 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626407"
1759924,2018-04-09 20:19:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559828"
1759924,2018-04-09 19:37:41 UTC,"Per comment 2 on cleaning up the port when we shelve offload, it sounds like that should be OK to do:"
1759924,2018-04-09 19:28:46 UTC,"Based on the steps in comment 3, I have a recreate with steps and output here:"
1759924,2018-04-09 17:41:36 UTC,I think I should be able to reproduce this with a single-host devstack by doing something like:
1759924,2018-12-20 00:10:32 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/626413"
1759924,2018-03-29 18:55:56 UTC,"Also note that when we shelve offload, we aren't doing any of this cleanup:"
1759927,2018-04-07 01:55:03 UTC,Additional entries now appearing:
1759927,2018-03-29 21:07:12 UTC,These are just warnings which can be ignored.
1759927,2018-03-29 22:23:02 UTC,"I understand they are warnings, but when applications produce continuous log entries, you end up with multiple MB sized log files. This is different than an application providing warnings at startup or something. This is continuous, I have it open in my tray."
1759933,2018-04-05 03:15:27 UTC,"Hi Hari,"
1759933,2018-04-05 20:58:59 UTC,"FYI, the cosmetic issue with the Sandesh request turns out to be a malformed request UrlQuery from the HTTP server where the routing instance name was cut short when it had special characters."
1759940,2018-04-30 15:24:18 UTC,"indeed, that was an Ubuntu patch which has been commented out"
1759941,2018-05-20 02:02:56 UTC,"The program does not hard code the path to the .ui file. It only hard codes the default, but allows the location to be over-ridden with a command line option: -g or --glade-path"
1759942,2018-06-23 20:36:10 UTC,"I believe I'm hitting the same issue, albeit with a Lenovo Miix 310, which previously to upgrading to Bionic had working audio."
1759942,2018-10-04 15:26:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759945,2021-02-22 16:00:55 UTC,Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1759945,2018-04-02 15:49:28 UTC,In the past we've been told that threads should be 1 and the process count should be tuned. It depends on the service i guess.  For processes we use the os_worker fact that uses a sliding scale with a cap so folks don't end up with 48+ processes for every service running
1759945,2018-04-03 22:19:51 UTC,"Ok, <sigh> so we may need to review each individual service..."
1759945,2018-04-04 20:07:14 UTC,"I can't really comment on the defaults for anything other than placement, I wish I could but, time, energy, etc."
1759946,2018-04-03 00:29:12 UTC,"We should further discuss how to properly handle this issue. In particular, if there are multiple subnets on a VLAN, and only one of them is moved, should we move *all* the subnets to the new VLAN? There might be a mix of multiple IPv4 and IPv6 subnets on the same VLAN. So we have to handle the following cases:"
1759946,2018-04-03 00:30:20 UTC,"For now, I'll move forward assuming we're just going to force a refresh, to prevent users from having to restart the rack controller to re-detect the network after moving a subnet to another fabric/VLANs."
1759949,2018-05-20 02:05:40 UTC,This probably has to do with some sort of backward compatibility issue and the version I originally coded against being deprecated or something. I'll look into it when I have a chance.
1759949,2018-05-20 02:13:31 UTC,"Hmm. I only see python-glade2 in bionic. I'm uncertain whether there is a python module with glade3 support in bionic. Until I have a bionic dev environment, I won't know whether I'll be able to continue with the existing ui method or not."
1759950,2019-06-18 12:48:21 UTC,This seems to be the crux of the issue. In a VT console I did:
1759950,2019-06-18 13:55:54 UTC,"I've captured a log where it doesn't fail. The difference is a single error message. In failing sessions there is an additional ""Failed to configure CRTC..."" which is not seen here:"
1759950,2019-06-18 14:07:26 UTC,The reason the CRTC isn't configured:
1759950,2019-06-18 17:13:11 UTC,Added:
1759950,2019-07-03 10:00:15 UTC,I assume that /xfce4-power-manager/logind-handle-lid-switch needs to be set to 'false'.
1759950,2019-06-23 13:00:02 UTC,Tested with the 19.10 daily (2019-06-22) amd64 build and the problem affects the live environment too.
1759950,2019-10-22 01:30:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759950,2020-08-22 23:56:03 UTC,This issue does not seem to occur when compiling XFCE Settings Mnaager without UPower as per my findings here: https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/222
1759950,2019-06-18 12:21:49 UTC,Finally found some evidence and it is surprising.
1759950,2019-06-19 11:51:53 UTC,I modified libxrandr to return the actual error code returned from XRRSetCrtcConfig():
1759950,2019-06-17 09:27:20 UTC,maxpus=1 still suffers the same issue.
1759950,2019-06-18 02:57:14 UTC,Yet more results changing the target once again!
1759950,2019-06-15 22:24:01 UTC,Just having upgraded several laptops to 19.04 and been hit by this again. Did some more research and revisited my upstream report and suspect this is caused by some interaction with the power manager and possibly systemd-logind (maybe they both try to set DPMS state for lid-close/open events? )
1759950,2019-06-16 23:26:22 UTC,On brainwash's suggestion (IRC #xubuntu-devel) I disabled UPower's Lid handling with /etc/UPower/UPower.conf:
1759950,2019-06-16 20:58:02 UTC,And it gets weirder... with supend-lock disabled AND leaving x-p-m dialog box on screen whilst suspending the LCD always gets enabled on resume!
1759950,2019-06-16 20:54:08 UTC,Update: Disabling x-p-m Security > Lock screen when system is going to sleep causes the LCD to be blank resume for the 1st cycle.
1759950,2019-06-16 20:47:49 UTC,"I've done some more tests with another clean install of 19.04; The only user setting I changed was on x-p-m for Laptop Lid Closed, On Battery = suspend."
1759950,2019-06-15 23:01:08 UTC,More search seems to point to a 2015 commit that integrated light-locker into xfce4-power-manager. This patch in particular appears to attempt to work with logind Lid handling too:
1759950,2019-06-15 22:52:44 UTC,To check on current systemd-logind properties including these:
1759950,2019-06-15 22:36:50 UTC,Turns out this *is* systemd-logind and xfce4-power-manager fighting over the lid close event.
1759950,2019-02-20 18:06:48 UTC,"Btw, I tested this with mate-power-manager and it works straight out of the box, without even changing the default logind settings."
1759950,2019-02-20 17:25:46 UTC,"No matter how I configure xfce4 power manager lid close on battery/ac events, the ones configured in logind.conf win."
1759950,2019-06-17 08:19:17 UTC,"I purged both xfce4-screensaver and light-locker packages, restarted lightdm and tested with x-p-m set to suspend on lid-close for battery (and AC as I've had the battery exhaust several times due to the length of these tests!)"
1759950,2018-11-11 18:17:44 UTC,Same problem here in a fresh install of Xubuntu 18.04 on a Lenovo T61.
1759950,2018-10-27 15:07:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759956,2018-05-08 04:36:03 UTC,This issue was fixed in the openstack/neutron 12.0.2 release.
1759956,2018-04-19 14:12:47 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b1 development milestone.
1759956,2018-05-08 04:32:01 UTC,This issue was fixed in the openstack/neutron 11.0.4 release.
1759956,2020-06-09 09:27:56 UTC,This seems to be fix-released in both stable/pike and stable/queens so I'm marking it so
1759956,2018-04-18 16:21:50 UTC,This bug was fixed in the package neutron - 2:12.0.0-0ubuntu3
1759956,2018-04-07 04:47:35 UTC,"Reviewed:  https://review.openstack.org/559256
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fb9ec1afb6545def3130952008ee7f20dbaafd2c
Submitter: Zuul
Branch:    stable/queens"
1759956,2018-04-06 02:39:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/559257"
1759956,2018-04-06 02:39:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/559256"
1759956,2018-04-05 19:50:26 UTC,Affects pike and queens UCA packages.
1759956,2018-04-05 19:09:15 UTC,"Reviewed:  https://review.openstack.org/557836
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=81db328b2df08f2b4adcc80104cf05ad8966c019
Submitter: Zuul
Branch:    master"
1759956,2018-03-29 21:48:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557836"
1759956,2018-04-07 21:57:05 UTC,"Reviewed:  https://review.openstack.org/559257
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0224dcfea4ffeaac6cbcec7464887e7538e49091
Submitter: Zuul
Branch:    stable/pike"
1759962,2018-03-30 10:37:24 UTC,To the group that produced this extremely short-sighted install procedure - here is one thing that you can do to save your honor.
1759971,2018-04-07 17:21:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/559494"
1759971,2018-04-18 16:21:50 UTC,This bug was fixed in the package neutron - 2:12.0.0-0ubuntu3
1759971,2018-04-07 17:27:51 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/559496"
1759971,2018-04-09 20:10:33 UTC,"Reviewed:  https://review.openstack.org/559494
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e53aa131ab65d50457efb01dee20332f935f15d0
Submitter: Zuul
Branch:    stable/queens"
1759971,2018-04-19 14:12:38 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b1 development milestone.
1759971,2018-10-03 16:46:05 UTC,Artful is EOL
1759971,2018-08-13 11:47:56 UTC,"Reviewed:  https://review.openstack.org/559496
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=29e0c7629fd6377539e5c15e4df34672e0bf1691
Submitter: Zuul
Branch:    stable/pike"
1759971,2018-11-06 06:11:20 UTC,This issue was fixed in the openstack/neutron 11.0.6 release.
1759971,2020-09-08 14:35:27 UTC,I've confirmed that the packages in Pike have this fix applied.
1759971,2018-04-06 22:47:31 UTC,Affects Pike and Queens UCA.
1759971,2018-06-22 18:00:15 UTC,12.0.2 is available in the Queens cloud archive.
1759971,2018-04-06 22:35:07 UTC,"Reviewed:  https://review.openstack.org/558137
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ff5e8d7d6cdc6ce3cd93aededec512e1855f6c28
Submitter: Zuul
Branch:    master"
1759971,2018-05-08 04:35:58 UTC,This issue was fixed in the openstack/neutron 12.0.2 release.
1759971,2018-04-06 11:10:51 UTC,"Yes, neither address scope information, nor fixed IP address assignment because the port is still unbound during the first call to list_active_sync_routers_on_active_l3_agent (_build_routers_list is called after some nested calls)."
1759971,2018-04-06 19:17:31 UTC,Ok Got it.
1759971,2018-04-02 01:21:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558137"
1759971,2018-04-03 23:05:06 UTC,There seems to be a concurrency issue with how router updates are handled in l3 agents.
1759971,2018-04-04 14:19:01 UTC,* Localized it further to get_routers in l3 agent which does an RPC call to sync routers - setting a trace before that RPC call clearly makes the problem go away.
1759971,2018-04-04 14:48:19 UTC,"So, to sum up:"
1759971,2018-04-04 18:26:27 UTC,After a gateway port gets created it is marked as unbound:
1759971,2018-04-02 01:14:29 UTC,"Tracing this again I can see that if external network is added after a tenant network ex_gw_port (""network:router_gateway"") has a very limited amount of information as opposed to fip_agent_port (""network:floatingip_agent_gateway"") which is retrieved from neutron service via an RPC call from neutron-l3-agent:"
1759971,2018-04-04 18:52:33 UTC,There are 4 router ports in unbound/DOWN state where device_owner is network:router_gateway
1759971,2018-04-05 01:02:45 UTC,With one dvr_snat node and a single physnet configured on it (otherwise HostConnectedToMultipleSegments is raised) all ports are ACTIVE in the end and there are no extra router_gateway ports but the issue is still present - IoW it's not due to a wrong router_gateway port being fetched.
1759971,2018-04-05 02:17:19 UTC,I think it's this portion of code that results in an issue:
1759971,2018-04-06 05:41:51 UTC,"The gateway_port host binding for DVR routers are handled in 'l3_dvr_db', where we specifically pass in the host information for the gateway.
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvr_db.py#L612"
1759971,2018-04-06 05:43:29 UTC,"So to summarize what you are saying is when external gateway is attached after the tenant network, the address_scopes are not populated in the get_sync_data sent by the server to the agent."
1759971,2018-04-01 20:54:18 UTC,Tracing neutron-l3-agent via rbdb clears the issue out a bit.
1759978,2019-08-17 22:26:43 UTC,https://github.com/mixxxdj/mixxx/commit/4af33c6a82af8be0da51b00b9d48f1d7d9cb9c3c
1759979,2018-06-04 13:52:27 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1759979,2018-06-08 12:25:40 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1759979,2018-04-26 11:18:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/564468"
1759979,2018-05-29 12:52:02 UTC,"Reviewed:  https://review.openstack.org/564468
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ffe092b112884fda2420ee847128ed975686e8cb
Submitter: Zuul
Branch:    stable/queens"
1759979,2018-04-26 01:00:36 UTC,"Reviewed:  https://review.openstack.org/562838
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5a42701f89a5139acdc38f8572b1083ba528264c
Submitter: Zuul
Branch:    master"
1759984,2018-04-09 19:00:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759984,2018-05-02 18:36:43 UTC,Hit a similar dependency error while installing another package.
1759984,2018-05-05 01:26:30 UTC,"I have the same problem as Desnesn (in #2). Found a workaround that can be applied while Ubuntu team and the packages developers don't solve the deadlock.
Just install the python-gpgme package for Artful that can be downloaded at ""https://www.ubuntuupdates.org/package/core/artful/main/base/python-gpgme""
install it before install the problematic package.
This workaround was suggested by the support team of Warsaw developers. Can be seen at
""https://www.reclameaqui.com.br/gas-tecnologia-a-diebold-company/ubuntu-18-04-lts-erro-de-instalacao_Ksid1yMqTuP2jy66/"" (text in portuguese)"
1759984,2018-07-14 17:15:49 UTC,I reported this issue upstream: https://github.com/dropbox/nautilus-dropbox/issues/51
1759984,2018-08-01 01:56:28 UTC,This was fixed upstream in https://github.com/dropbox/nautilus-dropbox/commit/e9367206f9b723103362e8dd154363517e9a9841
1759984,2018-11-27 09:55:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1759984,2020-01-05 11:51:53 UTC,What do I need to do to obtain the released fix? Just running `sudo apt-get update && sudo apt-get dist-upgrade` isn't enough...
1759984,2020-12-18 18:38:00 UTC,Where is this fix supposed to be released?
1759986,2018-03-30 09:51:44 UTC,Thanks for reporting and providing a patch for this issue.
1759986,2020-06-07 11:17:19 UTC,"I've just verified smart-notifier 0.28-6 on Ubuntu Groovy, and the space and a couple of other typoes are indeed fixed. Unfortunately it was a bit too late for 20.04, but it will be part of the next Ubuntu release."
1759987,2018-03-30 07:41:21 UTC,"I'm aware of that. Thankfully, this will give us time to tweak it, should we decide to change the colors or font."
1759987,2018-04-05 07:24:19 UTC,@fossfreedom I tweaked the theme some so it's a little less jarring to new users.
1759987,2018-04-05 07:34:01 UTC,"Cheers. I will come back to look at this next month once the frantic part
of 18.04 is out of the way."
1759987,2018-04-05 08:09:53 UTC,"We also have to decide on a name. We could leave it as bug-grub-theme, but we could probably figure out something better. And we also can't use grub-theme-breeze."
1759987,2018-12-11 17:00:19 UTC,Just bumping in time for 19.04.
1759987,2018-12-12 14:16:49 UTC,Thanks for the reminder Larry
1759987,2018-12-13 18:35:54 UTC,The KDE Neon devs should be able to point you in the right direction.
1759987,2018-12-16 03:57:00 UTC,"On a side note, I think I've figured out what to call the grub theme."
1759987,2018-12-28 21:37:48 UTC,It would be best to check with the Solus devs first.
1759987,2018-03-30 07:04:06 UTC,It is too late for inclusion for 18.04 since we are well past user interface and feature freeze.
1760043,2018-03-30 08:36:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/557909"
1760043,2018-07-06 12:38:19 UTC,"Change abandoned by Nguyen Hai (<email address hidden>) on branch: master
Review: https://review.openstack.org/557909"
1760047,2019-03-18 05:44:51 UTC,May be DHCP agent port cache is out of sync with neutron server.
1760047,2019-01-29 10:57:27 UTC,"Reviewed:  https://review.openstack.org/626830
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=99f4495c940011293e3cabbb590770dc1e7b6900
Submitter: Zuul
Branch:    master"
1760047,2019-03-18 05:33:13 UTC,"Hi all, I am also experiencing same kind of issue. I am using latest neutron code"
1760047,2019-03-29 14:39:53 UTC,Any chance to have this cherry pricked in Rocky ?
1760047,2018-12-21 06:44:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/626830"
1760047,2019-04-07 17:11:57 UTC,"Reviewed:  https://review.openstack.org/649573
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=056e049e2b9c7db0802092691d63dcc1b9705a29
Submitter: Zuul
Branch:    stable/rocky"
1760047,2019-04-11 12:13:40 UTC,"Reviewed:  https://review.openstack.org/649580
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dd5e89e717ef0993d1de4c97d1f0d3132f2845e5
Submitter: Zuul
Branch:    stable/queens"
1760047,2019-04-19 10:21:22 UTC,"After this patch we've started to get ""Duplicate IP addresses found, DHCP cache is out of sync"" messages (but actually it ain't true, see log below) really often, which sometimes causes vm unable to get an ip address from DHCP server. Therefore resync with neutron server is triggered causing unwanted events."
1760047,2019-05-09 14:10:27 UTC,Thx Michael for this info. I opened new bug for that https://bugs.launchpad.net/neutron/+bug/1828423
1760047,2019-04-03 10:31:03 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649573"
1760047,2018-12-20 05:49:25 UTC,"As LIU Yulong described in bug/1778616, The neutron must get the `Provisioning complete` notification for port before it sends 'network-vif-plugge' event to nova."
1760047,2019-04-03 11:07:40 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/649580"
1760047,2018-08-10 06:59:51 UTC,"We meet such issue too in stable/queens, the root cause was same as Piotr Misiak (piotr-misiak) said in comment #7.
I submitted a new bug here, but now it is marked duplicate to this.
https://bugs.launchpad.net/neutron/+bug/1778616"
1760047,2018-12-19 01:39:05 UTC,"Hi, any updates or recommendations from neutron team?"
1760047,2018-03-30 17:31:47 UTC,Needs triaging.
1760047,2018-04-03 19:20:54 UTC,"When I spawn one or a few or a dozen VMs at once I can't reproduce the issue.
Seems the issue is only during large provisioning."
1760047,2018-04-04 10:05:12 UTC,So in my case the port is stale in DHCP agent because it is in NetworkCache.deleted_ports set.
1760047,2018-04-04 14:16:23 UTC,Finally I found it.. DHCP agent waits a couple of minutes to acquire lock on network in function DhcpAgent.port_update_end():
1760047,2018-03-30 17:31:02 UTC,"Is it reproducible in small scale or only seen in large scale.
Yes we need to figure out why the dhcp is thinking certain ports are stale ports."
1760047,2018-04-05 07:31:59 UTC,Here is code with my debug message:
1760047,2018-04-05 08:43:53 UTC,"I am not sure if it could possibly due to large number of VMs spawn at the same time ran out of threads in your env. It is also difficult for me to reproduce it now, but I am marking this as confirmed. Would you please share more details of your environment? I see you are using Kolla. Do you deploy AIO or multi-nodes? Are you running Kolla in VM or physical machine? etc.."
1760047,2018-04-05 08:56:12 UTC,The env has 3 controller nodes and 40 compute nodes. But for debugging purposes I spawn VMs on 6 compute nodes with debugging enabled. The env is not busy. I use kolla.
1760047,2018-04-05 09:16:12 UTC,"All servers all physical. We use DVR, L3_HA and L2 population."
1760047,2018-04-05 09:32:56 UTC,"Maybe I have a hint. I spawn 100 VMs using horizon. So VMs have a name with a numeric suffix from 1 to 100. I think (I'm not sure) each time ERROR state have VMs with suffixes between 10 and 20 one by one, for example: 11,12,13,14,15 and VMs from 1 to 10 and from 16 to 100 are OK.
Maybe it is correlated with rpc_workers? But why does this happens only once during provisioning and not every 12 VMs?"
1760047,2018-03-30 08:40:44 UTC,I forgot to mention that we have Neutron 11.0.3
1760055,2018-03-30 09:30:26 UTC,Here is the fix
1760065,2019-10-09 12:18:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/687544"
1760065,2019-11-11 15:39:16 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1760065,2019-10-10 10:43:35 UTC,"Reviewed:  https://review.opendev.org/687544
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=bdc8df0c9066aadd442b6f63db5daec6dcda96f1
Submitter: Zuul
Branch:    master"
1760065,2019-08-23 19:54:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678296"
1760065,2019-08-20 10:22:19 UTC,"(cut from article above, correct except for `entity=`client.cinder`"
1760065,2019-08-20 10:21:16 UTC,"If this problem occurrs, there are `Mar 22 15:55:24 dev-ceph-01 docker: 2018-03-22 15:55:24.018624 7f7b084aa700  0 log_channel(audit) log [INF] : from='client.? 10.0.0.1:0/2275353734' entity='client.openstack' cmd=[{""prefix"": ""osd blacklist"", ""blacklistop"": ""add"", ""addr"": ""10.0.0.2:0/3833716830""}]:  access denied` entries in the `/var/lib/docker/volumes/kolla_logs/_data/ceph/ceph.log` file."
1760065,2019-08-20 10:13:00 UTC,"So we need to add `allow command ""osd blacklist"" to the `client.cinder`. Otherwise after a hypervisor crash, instances will  not boot with ""INACCESSIBLE BOOT VOLUME"""
1760065,2018-08-30 14:24:55 UTC,Is there any quick workaround to release the lock?
1760065,2018-06-19 21:21:17 UTC,"Having the same issue, change client.nova auth caps only fix the vms that don't have attached volumes.
Need change client.cinder as well if there are attached volumes to vm"
1760065,2019-08-20 10:22:42 UTC,Seeing this in Rocky btw
1760066,2018-04-04 08:26:51 UTC,"Change abandoned by wangwei (<email address hidden>) on branch: master
Review: https://review.openstack.org/557922
Reason: This method is not suitable, I will make changes in kolla-ansible."
1760068,2019-03-03 14:17:16 UTC,"Same issue with Xubuntu 18.10 Cosmic and nvidia-driver-415.  As mentioned above it is not only the lock screen, but the boot splash screens as well."
1760068,2019-03-03 14:50:42 UTC,In my instance (Xubuntu 18.10 with nvidia 415 from the graphics drivers PPA) I was able to fix the lock screen resolution by using the following:
1760068,2019-03-03 15:46:46 UTC,"~$ inxi -G
Graphics:  Device-1: NVIDIA GP104 [GeForce GTX 1070] driver: nvidia v: 415.27
           Display: x11 server: X.Org 1.20.3 driver: nvidia resolution: 2560x1440~60Hz
           OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 415.27"
1760068,2019-04-14 18:18:45 UTC,With Xubuntu 19.04 Disco Dingo and the 418.56 nvidia drivers it appears now my system has:
1760068,2019-07-07 12:38:25 UTC,Problem solved with solution
1760068,2019-09-28 23:49:06 UTC,"ls /usr/lib/x86_64-linux-gnu/nvidia*
tells ""No such file or directory"""
1760068,2019-07-21 12:33:59 UTC,"I solved it in Desktop Settings, by changing the Window Manager from ""Xfwm4 + Compositing"" to ""Compiz""."
1760068,2019-09-28 13:11:06 UTC,Okay.For nvidia-435.21 I fixed it with:
1760068,2019-09-29 11:37:44 UTC,"I used
sudo nvidia-xconfig
to create initial /etc/X11/xorg.conf file like told in #18"
1760068,2019-09-29 14:16:08 UTC,"Oh, I found alternative way that works for GRUB menu resolution and console resolution, too, and no need to create /etc/X11/xorg.conf."
1760068,2018-11-15 21:28:35 UTC,It's almost the same workaround for all nvidia versions: you must inform where is the nvidia_drv and libglx.
1760068,2019-07-07 15:21:36 UTC,"Thank you very much, ubunt 18.04 LTS and it fixed my issue as well. However I also tested nvidia driver 430 not tested and it doesn't seem to work in that driver."
1760068,2018-11-15 07:50:36 UTC,"Nevermind, the full solution from the link did in fact work for me. Using nvidia-driver-390."
1760068,2019-11-21 09:29:28 UTC,"well, the same situation.
System:    Host: diacon Kernel: 4.15.0-70-generic x86_64 bits: 64 Desktop: Xfce 4.12.3 Distro: Linux Mint 19.2 Tina
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME X370-A v: Rev X.0x serial: <root required>
           UEFI [Legacy]: American Megatrends v: 5220 date: 09/12/2019
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP L2 cache: 4096 KiB
           Speed: 1885 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 1885 2: 1888 3: 2192 4: 2076 5: 1912 6: 2062 7: 2074
           8: 2065 9: 1884 10: 1887 11: 2054 12: 1889 13: 1886 14: 1889 15: 2193 16: 2190
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] driver: nvidia v: 430.50
           Display: x11 server: X.Org 1.19.6 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 430.50
Audio:     Device-1: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel
           Sound Server: ALSA v: k4.15.0-70-generic
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: 40:b0:76:5e:8e:51
Drives:    Local Storage: total: 1.58 TiB used: 297.63 GiB (18.4%)
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
           ID-2: /dev/sdb vendor: SanDisk model: SDSSDA240G size: 223.57 GiB
           ID-3: /dev/sdc vendor: Western Digital model: WD5000AAKX-75U6AA0 size: 465.76 GiB
           ID-4: /dev/sdd vendor: Western Digital model: WD5003ABYX-01WERA1 size: 465.76 GiB
Partition: ID-1: / size: 245.98 GiB used: 47.76 GiB (19.4%) fs: ext4 dev: /dev/sda5
Sensors:   System Temperatures: cpu: 38.5 C mobo: N/A gpu: nvidia temp: 35 C
           Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 0%
Info:      Processes: 293 Uptime: 1h 23m Memory: 31.41 GiB used: 2.46 GiB (7.8%) Shell: bash inxi: 3.0.32"
1760068,2018-11-09 13:29:03 UTC,"Thank you, Theo!"
1760068,2018-03-31 11:04:40 UTC,Doesn't seem to affect Intel graphics.
1760068,2018-11-15 07:37:51 UTC,That work around did not work for me.
1760068,2018-04-02 08:12:21 UTC,doesn't affect nouveau either
1760068,2018-04-02 10:19:02 UTC,"Unable to confirm for nvidia-340, but also not sure it's fully installed. Installed via Software & Updates, and it says it's installed, but nvidia-settings has two tabs and this is inxi's output. If this is correct output, it seems to be working on nvidia-340 here."
1760068,2018-04-30 05:53:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760068,2018-05-18 20:51:22 UTC,"Me too. Xubuntu 18.04, fresh install."
1760068,2018-08-23 09:35:11 UTC,This is a duplicate of bug 1757202.
1760068,2018-04-02 11:03:36 UTC,Also no luck getting nvidia-driver-390 installed to test.
1760068,2018-09-01 14:12:51 UTC,"Thiago, this bug may be caused by having two Xorg instances (the user session and the unlock screen which runs in another VT) accessing the graphics driver. And up until now, only the nvidia driver was reported to be part of the problem."
1760068,2018-09-17 20:02:11 UTC,Most likely not a bug in light-locker.
1760068,2018-10-09 10:10:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760068,2018-11-08 15:22:34 UTC,A new version of nvidia-graphics-drivers-340 is available in -updates.
1760068,2018-11-08 20:03:47 UTC,I'm using the 340.107 and the problem persists.
1760068,2018-11-08 21:23:05 UTC,"Well, as mentioned in comment #10, this bug is not limited to the unlock screen (which happens to be a second Xorg instance if you use light-locker)."
1760068,2018-09-01 11:14:31 UTC,"It affects me too... I have an ATI Mobility Radeon HD 5470. And it has nothing to do with 2 users at the same time, because it happens to me with a single user logged in."
1760069,2018-04-09 11:00:29 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760074,2019-12-24 09:44:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760087,2018-03-30 12:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760090,2018-04-03 04:23:04 UTC,"Hi,"
1760090,2018-11-07 15:06:17 UTC,"it also affects me in debian, but debian or its version is not the problem:"
1760090,2018-11-07 18:58:57 UTC,I confirm what ~charisz said
1760092,2019-09-26 16:40:54 UTC,Got this after pairing of my Logitech M555b mouse on Ubuntu MATE 19.10 beta.
1760092,2018-12-21 17:21:30 UTC,"Hello,"
1760092,2018-12-20 23:15:34 UTC,a complete trace
1760092,2018-12-20 22:21:48 UTC,"Hello,"
1760092,2018-12-20 21:40:13 UTC,"Hello,"
1760092,2018-09-09 08:14:44 UTC,This happens every time I search for Bluetooth devices.
1760092,2018-09-16 11:48:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760092,2018-12-20 22:47:45 UTC,/usr/lib/python3/dist-packages/dbus$ connection.py
1760104,2018-06-01 01:25:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760104,2018-06-01 01:32:25 UTC,"Annoyingly, around 50 reports of the crash on bionic is still not enough for it to make it into the top 100 xorg-server crashes on bionic. So not easy to find."
1760104,2018-06-01 01:28:51 UTC,Now tracking in:
1760104,2018-05-31 12:04:59 UTC,"So, the pauses I am experiencing is likely due to simply the fact that the keyboards and mice are being removed then added back, which is a different issue than the crashes (which appear nvidia related). I will likely create a PR to only trigger the input subsystem on an as-needed base to reduce the annoying pauses we see during refreshes."
1760104,2018-05-30 23:02:20 UTC,I had some luck with this not pausing/blinking gnome-shell:
1760104,2018-05-30 22:28:42 UTC,"I noticed I could prevent gnome-shell from blinking/pausing if instead of 'sudo udevadm control --reload-rules && sudo udevadm trigger' I instead did 'sudo udevadm control --reload-rules && sudo udevadm trigger --subsystem-nomatch=input'. I'm not sure there is much that snapd can do with that information, but it might be a clue to make gnome-shell/X11/nvidia to behave better."
1760104,2018-05-30 22:10:00 UTC,I suspect this is because snapd will do 'sudo udevadm control --reload-rules && sudo udevadm trigger' on interface connections. These operations are supposed to be safe but I've seen with my Intel graphics that gnome-shell/X11 will blink when this happens (due to the 'udevadm trigger') but it doesn't crash. I suspect that your particular combination of gnome-shell/X11/nvidia isn't responding particularly well when this happens.
1760104,2018-05-30 19:11:48 UTC,Just had this again.
1760104,2018-05-24 12:03:43 UTC,"I've just installed a snap and experienced this issue. The snap is a game using the opengl interface and immediately after the install the entire desktop UI locked up, Xorg crashed and I was returned to the display manager. Here is the associated error report:"
1760104,2018-05-24 12:01:22 UTC,I've had this again. Here's the crash report links.
1760104,2018-05-24 12:00:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760104,2018-05-16 13:06:41 UTC,"I've added a task for snapd, because this only happens when I'm doing ""snap install"" something. Usually at the point when it connects the opengl interface."
1760104,2018-03-30 13:40:08 UTC,"StacktraceTop:
 ?? ()
 InputReady (fd=38, xevents=1, data=0x5652a82b81d0) at ../../../../os/inputthread.c:180
 ospoll_wait (ospoll=0x5652a7788640, timeout=timeout@entry=-1) at ../../../../os/ospoll.c:412
 InputThreadDoWork (arg=<optimized out>) at ../../../../os/inputthread.c:367
 start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463"
1760105,2018-04-01 19:59:10 UTC,"Hi Shreyas,
you should attach the full OpenRailsLog.txt file. To help you one should first know what OR version you are using, and this is written in the first part of the logfile."
1760106,2018-07-19 12:13:45 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.2
1760106,2018-07-19 12:14:06 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1760106,2018-08-28 00:32:43 UTC,This bug was fixed in the package systemd - 239-7ubuntu4
1760106,2018-07-18 13:16:23 UTC,"This patch set is still present, and is operating as expected in 237-3ubuntu10.2"
1760106,2019-01-18 12:01:27 UTC,klibc ftbfs on i386 in disco.
1760106,2019-01-21 13:22:46 UTC,"removing, breaks amd64 autopkg tests."
1760106,2018-09-05 06:19:27 UTC,"Has this fix built into daily live? Currently for server and client, we all come across this issues in 18.10."
1760106,2018-07-03 06:57:33 UTC,"Hello Mario, or anyone else affected,"
1760106,2019-01-22 12:45:51 UTC,@Mario
1760106,2018-05-25 13:55:33 UTC,Hm.... I think I am confused on how this feature is supposed to work.
1760106,2018-06-08 22:25:29 UTC,I think this is actually fine. Ship it.
1760106,2018-04-06 10:26:20 UTC,As this is 4.17 only I assume we will have to backport this for the kernel.  Asking one of the  kernel-team folk to review that.  Also how close is pottering to accepting the systemd changes.  As it seems we need all three bits ready.
1760106,2018-04-06 15:42:36 UTC,"@Andy,"
1760106,2018-04-06 15:44:04 UTC,"regarding klibc upstream is MIA for a long time.  There are patches that have been posted before mine, but no activity since:"
1760106,2018-03-30 13:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760106,2018-04-11 14:07:36 UTC,"@xnox in order to coordinate the systemd upload in case you have anything in flight, here's a debdiff:"
1760106,2018-04-13 23:43:34 UTC,This bug was fixed in the package linux - 4.15.0-15.16
1760106,2018-05-24 10:07:38 UTC,"Hello Mario, or anyone else affected,"
1760106,2018-04-07 19:18:54 UTC,"Please note, I'm not part of the release team."
1760107,2018-04-04 11:31:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760113,2018-05-23 23:17:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760113,2018-05-24 00:16:20 UTC,"My notebook computer is an HP Envy x360 15z-bq100 Convertible running Ubuntu Bionic (18.04), kernel 4.17.0-rc4-custom (custom for a patch to enable the ELAN touchscreen). lshw:
sadhu-notebook
    description: Notebook
    product: HP ENVY x360 Convertible 15-bq1xx (1ZA02AV)
    vendor: HP
    version: Chassis Version
    serial: 8CG8047TGY
    width: 64 bits
    capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
    configuration: boot=normal chassis=notebook family=103C_5335KV HP Envy sku=1ZA02AV uuid=79D7BD68-F104-E811-9A04-9C305B260786
  *-core
       description: Motherboard
       product: 83C6
       vendor: HP
       physical id: 0
       version: 63.18
       serial: PGSRH1A0GAD39M
       slot: Base Board Chassis Location
     *-firmware
          description: BIOS
          vendor: AMI
          physical id: 0
          version: F.14
          date: 12/14/2017
          size: 64KiB
          capacity: 15MiB
          capabilities: pci upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi
     *-memory
          description: System Memory
          physical id: 11
          slot: System board or motherboard
          size: 32GiB
        *-bank:0
             description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
             product: CT16G4SFD824A.C16FBR
             vendor: Unknown
             physical id: 0
             serial: A9160FF6
             slot: Bottom - Slot 1 (left)
             size: 16GiB
             width: 64 bits
             clock: 2400MHz (0.4ns)
        *-bank:1
             description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
             product: CT16G4SFD824A.C16FBR
             vendor: Unknown
             physical id: 1
             serial: A9161116
             slot: Bottom - Slot 2 (right)
             size: 16GiB
             width: 64 bits
             clock: 2400MHz (0.4ns)
     *-cache:0
          description: L1 cache
          physical id: 13
          slot: L1 - Cache
          size: 384KiB
          capacity: 384KiB
          clock: 1GHz (1.0ns)
          capabilities: pipeline-burst internal write-back unified
          configuration: level=1
     *-cache:1
          description: L2 cache
          physical id: 14
          slot: L2 - Cache
          size: 2MiB
          capacity: 2MiB
          clock: 1GHz (1.0ns)
          capabilities: pipeline-burst internal write-back unified
          configuration: level=2
     *-cache:2
          description: L3 cache
          physical id: 15
          slot: L3 - Cache
          size: 4MiB
          capacity: 4MiB
          clock: 1GHz (1.0ns)
          capabilities: pipeline-burst internal write-back unified
          configuration: level=3
     *-cpu
          description: CPU
          product: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
          vendor: Advanced Micro Devices [AMD]
          physical id: 16
          bus info: cpu@0
          version: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
          serial: Unknown
          slot: FP5
          size..."
1760113,2018-05-24 00:30:35 UTC,My issue is identical to the current description of this bug. In addition to the previously posted comment I'm including this output re:VGA card from the lspci command:
1760113,2018-05-28 21:44:50 UTC,"I also have the same issue using 18.04 (clean install) 4.15.0-22-generic, with the following graphics using Nvidia 390
:"
1760115,2018-03-30 14:11:26 UTC,"StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
 __cxxabiv1::__terminate(void (*)()) () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
 std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
 __cxxabiv1::__cxa_throw (obj=obj@entry=0x55de6d05fa30, tinfo=0x55de6c398dd0 <typeinfo for Glib::RegexError>, tinfo@entry=0x7fb91a6ed760 <typeinfo for Glib::RegexError>, dest=dest@entry=0x7fb91a4bd060 <Glib::RegexError::~RegexError()>) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:95
 Glib::RegexError::throw_func (gobject=0x55de6d05d010) at regex.cc:318"
1760115,2019-05-15 08:53:07 UTC,"Not sure if this is exactly the same bug, but I get an easily reproduce-able crash when using the search bar(magnifying glass icon) under the ""Processes"" tab, by typing a '[' character into the textbox."
1760115,2019-05-15 11:44:53 UTC,"The issue is fixed in newer versions (GNOME 3.30/cosmic/distro) and in the snap (which is how the software is shipped in bionic by default)
https://gitlab.gnome.org/GNOME/gnome-system-monitor/commit/18bd98e2"
1760115,2019-05-15 11:48:47 UTC,"The error is https://errors.ubuntu.com/problem/19e723ae and has 292, probably not worth a SRU since it's a low number, the deb is not used by default and it's easy to workaround"
1760120,2018-04-02 11:27:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760120,2018-04-02 11:30:32 UTC,"With nodejs version 6.x entering maintenance cycle [1], it would be reasonable to move it to ""legacy"" package, and update nodejs package to version 8.x. That would make quite a few developers happy."
1760127,2018-04-02 20:16:33 UTC,"The 3.13 kernel in Trusty was not affected by this. I have tested all the kernels since 4.4 and they are affected.
I can confirm that the bug is fixed in the 4.15 and 4.16 kernels."
1760127,2018-03-30 15:00:13 UTC,This change was made by a bot.
1760127,2018-04-02 18:51:41 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1760138,2018-04-03 12:36:05 UTC,This looks like  a bug or race in juju itself.
1760138,2018-04-03 14:21:13 UTC,"This seems to be some sort of load issue, as this is what I'm seeing:
$ grep -rnI ""is-leader\|leader-set"" .
./unit-ceph-mon-1.log:1196:2018-03-30 01:54:36 DEBUG worker.uniter.jujuc server.go:181 running hook tool ""is-leader""
./unit-ceph-mon-1.log:1206:2018-03-30 01:56:50 DEBUG worker.uniter.jujuc server.go:181 running hook tool ""leader-set""
./unit-ceph-mon-1.log:1230:2018-03-30 01:58:27 DEBUG config-changed subprocess.CalledProcessError: Command '['leader-set', 'fsid=9a557a74-33bd-11e8-aedb-00163ef9463f', 'monitor-secret=AQBemb1ajb3qLRAAlPxv893HqNK1oos2V1jUzg==']' returned non-zero exit status 1"
1760138,2018-05-02 11:18:42 UTC,Thanks John for doing the additional analysis; I was also heading in the direction of a gap between is_leader() and leader_set().
1760138,2018-05-02 11:23:27 UTC,"Sorry, I meant to comment on https://bugs.launchpad.net/charm-ceph-mon/+bug/1768241 -- but it also seems relevant here!"
1760138,2019-06-12 08:20:01 UTC,"So we've noted several performance issues around leadership that have been fixed in or around 2.5.1. (moving to raft for leadership, and fixing performance issues around some of the lease update operations as the number of leases gets large.)
Given those fixes, it is likely that *this* bug was around ""is-leader => leader-set"" was taking longer than 30s to refresh its leadership, causing it to lose its leadership in that time, and thus we believe those issues to be fixed.
Not directly in 2.5.8, but as a close approximation."
1760152,2018-03-30 16:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760152,2018-04-02 20:15:29 UTC,"I built a test kernel with commits 7a7415659144 and 87a23801e502.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1760152"
1760152,2018-04-09 16:07:11 UTC,"Apologies for the slow response, I was on holidays last week."
1760152,2018-04-10 11:42:01 UTC,"Hi,"
1760152,2018-04-23 20:30:04 UTC,I cherry picked the two commits mentioned in the bug description on top of: Ubuntu-4.15.0-12.13.  Here is the top three commits in my tree used to build the test kernel:
1760153,2018-03-30 16:29:41 UTC,"StacktraceTop:
 do_ssl3_write (s=s@entry=0x7f223c100700, type=type@entry=21, buf=0x7f223c0eb998 ""\002\026"", pipelens=pipelens@entry=0x7f2241c533f4, numpipes=numpipes@entry=1, create_empty_fragment=create_empty_fragment@entry=0) at ../ssl/record/rec_layer_s3.c:763
 ssl3_dispatch_alert (s=0x7f223c100700) at ../ssl/s3_msg.c:98
 ssl3_get_record (s=s@entry=0x7f223c100700) at ../ssl/record/ssl3_record.c:521
 ssl3_read_bytes (s=0x7f223c100700, type=23, recvd_type=0x0, buf=0x7f223c1137e0 ""`\a"", len=8192, peek=0) at ../ssl/record/rec_layer_s3.c:1055
 ssl3_read_internal (s=0x7f223c100700, buf=0x7f223c1137e0, len=8192, peek=0) at ../ssl/s3_lib.c:3840"
1760153,2019-01-23 09:56:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760157,2018-03-30 17:55:57 UTC,We need to add this to the setup.cfg:
1760157,2018-07-03 13:48:58 UTC,This issue was fixed in the openstack/cliff 2.13.0 release.
1760190,2018-04-03 07:28:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760190,2020-02-25 11:17:39 UTC,Is this issue going anywhere?
1760190,2018-03-30 20:35:09 UTC,I think duplicate status is wrong. this bug not about gdm. its about unused but installed icons themes
1760193,2020-02-18 19:41:44 UTC,"Thanks, Kyle! My signoff is at:"
1760193,2020-02-18 19:16:59 UTC,"Good catch, those shouldn't have made it in there. I've rebased the branch and removed those patches"
1760193,2020-02-18 19:04:34 UTC,"The rewording looks good, Kyle - could you please rebase against master so that the 1857910 and 1654529 patches aren't in this branch?"
1760193,2020-02-18 18:45:19 UTC,"I've pushed a commit to reword this, thanks all for the feedback!"
1760193,2020-02-17 17:48:01 UTC,+1 to:
1760193,2020-02-21 18:30:41 UTC,Pushed to master.  Thanks Kyle and Terran!
1760193,2020-02-17 17:09:55 UTC,I agree with Lynn that the wording is confusing.
1760193,2020-02-17 16:42:03 UTC,"I would sign off on this, except for some ambiguity.  The link says ""Add Item Records to bucket"", to me that would be the same as ""Add Items to Bucket"".  If it would say ""Add Title Records to Bucket"" or ""Add Titles to Bucket"" that would make a little more since."
1760193,2020-01-28 18:34:02 UTC,I've pushed a branch here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1760193-add-record-bucket-item-status
1760193,2019-09-13 20:09:49 UTC,Confirmed in 3.3.2
1760193,2018-07-16 15:54:04 UTC,"Kathy,
   Thank you. I must say this turns this bug from an minor annoyance into kind of a big deal. I am hoping we can get its Important bumped up."
1760193,2018-07-16 14:03:26 UTC,"Until this bug is addressed, you can't add multiple titles to a record bucket."
1760193,2018-07-16 13:34:50 UTC,"This workaround is serviceable, but how does one, from Item Status, add multiple titles to a Record Bucket."
1760193,2020-02-17 17:11:39 UTC,(Adding needsrepatch tag to improve wording.)
1760199,2018-08-26 10:52:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760199,2018-08-26 17:44:05 UTC,I've been testing out the Kubuntu 18.04.1 Desktop Environment on another machine.
1760201,2018-04-16 10:24:59 UTC,Sorry for delay...
1760201,2018-04-17 01:24:09 UTC,"Thanks. The common factor then in both reports of this bug is that nouveau is in use. And historically, this isn't surprising. Nouveau has occasionally had such missing textures bugs like this over the years."
1760201,2018-04-17 07:05:13 UTC,"WaylandEnable=false solved my problem. Thank you.
Ubuntu 18.04 using default xorg, why gdm using wayland?
Will you set gdm default xorg?"
1760201,2018-04-16 08:51:24 UTC,lspci -k (nouveau)
1760201,2018-04-17 07:29:51 UTC,Well using nvidia proprietary driver is solving for me (nothing changed in gdm3 custum.conf).
1760201,2018-06-19 08:49:22 UTC,"I'd like to report that this issue is also being reproduced with nouveau on NVIDIA GF108. However, my dmesg does not seem to contain nouveau errors."
1760201,2018-04-17 07:44:17 UTC,"Also, if anyone can reproduce the problem again, do you find nouveau errors in your kernel log around the time of the missing rendering?"
1760201,2018-04-17 07:55:34 UTC,"[16738.253190] nouveau 0000:01:00.0: Direct firmware load for nouveau/nvc1_fuc084 failed with error -2
[16738.253198] nouveau 0000:01:00.0: Direct firmware load for nouveau/nvc1_fuc084d failed with error -2
[16738.253200] nouveau 0000:01:00.0: msvld: unable to load firmware data
[16738.253204] nouveau 0000:01:00.0: msvld: init failed, -19"
1760201,2018-06-07 02:33:19 UTC,This bug has been reported with both GF106 (bug 1775279) and GM107GLM (this bug) hardware.
1760201,2018-07-20 23:26:12 UTC,I just wanted to state that this issue seems to have resolved itself. I've grabbed the updated packages from apt and these are what I believe the relevant updates were. Is there any more information that might be more useful?
1760201,2018-04-17 07:43:08 UTC,"Thank you for information. nvidia-driver-390 driver have problems too, i hope you can fix before the 18.04 final release. (https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1762200)
Last question; mutter 3.28.1 not released when it will release and will you put in 18.04? (maybe bug 1762200 about mutter)"
1760201,2018-04-16 08:48:08 UTC,"@ultrabit, please run: lspci -k"
1760201,2018-04-17 07:12:50 UTC,The problem may not be Wayland as much as forcing X allows the Nvidia driver to work and avoids Nouveau and its bugs.
1760201,2018-04-16 08:25:00 UTC,All: Please run this command and send us the output:
1760201,2018-04-03 07:25:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1760201,2018-04-03 18:35:51 UTC,apport information
1760201,2018-04-03 18:35:52 UTC,apport information
1760201,2018-04-03 18:35:52 UTC,apport information
1760201,2018-04-04 07:24:21 UTC,the issue could be a missing font?
1760201,2018-04-06 01:19:43 UTC,Lock screen normal only login screen have this bug
1760201,2018-04-16 08:35:03 UTC,lspci -k
1760201,2018-04-06 11:46:04 UTC,"i find user-1000.journal file its 50,3 mb. is it correct file?"
1760201,2018-04-06 07:52:43 UTC,Could you add your journalctl log to the bug?
1760201,2018-04-16 03:15:49 UTC,"Ahmet, are you using multiple monitors?"
1760201,2018-04-16 08:10:49 UTC,"@vanvugt No, but system detect 2 screens https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1762200"
1760201,2018-04-16 03:14:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760201,2018-04-06 12:50:11 UTC,https://gist.github.com/Parduk/54ab53a12ec063ae6c3bc945f326130b
1760201,2018-04-16 03:15:36 UTC,Confirmed also with LANGUAGE=it_IT.UTF-8 (bug 1764071)
1760227,2018-03-30 21:57:50 UTC,"StacktraceTop:
 js::Shape::matches (other=..., this=0x0) at /build/mozjs24-aUzIx7/mozjs24-24.2.0/js/src/vm/Shape-inl.h:263
 js::ShapeHasher::match (l=..., k=0x0) at /build/mozjs24-aUzIx7/mozjs24-24.2.0/js/src/jspropertytree.cpp:31
 js::detail::HashTable<js::Shape* const, js::HashSet<js::Shape*, js::ShapeHasher, js::SystemAllocPolicy>::SetOps, js::SystemAllocPolicy>::match (l=..., e=...) at ./dist/include/js/HashTable.h:1035
 js::detail::HashTable<js::Shape* const, js::HashSet<js::Shape*, js::ShapeHasher, js::SystemAllocPolicy>::SetOps, js::SystemAllocPolicy>::lookup (collisionBit=0, keyHash=<optimized out>, l=..., this=0x6d66b50) at ./dist/include/js/HashTable.h:1057
 js::detail::HashTable<js::Shape* const, js::HashSet<js::Shape*, js::ShapeHasher, js::SystemAllocPolicy>::SetOps, js::SystemAllocPolicy>::lookup (l=..., this=0x6d66b50) at ./dist/include/js/HashTable.h:1357"
1760227,2020-11-16 08:37:22 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life on April, 2019"
1760227,2020-11-16 15:04:31 UTC,I haven't seen this bug in 18.04 nor now in 20.04.
1760231,2018-03-30 22:17:32 UTC,"StacktraceTop:
 g_wakeup_new () at ../../../../glib/gwakeup.c:161
 g_main_context_new () at ../../../../glib/gmain.c:656
 start_sync (data=<optimized out>, data=<optimized out>) at snapd-client-sync.c:24
 snapd_client_get_interfaces_sync (client=client@entry=0x55c32bfd3580, plugs=plugs@entry=0x7fe8231667b0, slots=slots@entry=0x7fe8231667b8, cancellable=cancellable@entry=0x55c32a8f7e80, error=error@entry=0x7fe823166878) at snapd-client-sync.c:454
 gs_plugin_refine_app (plugin=plugin@entry=0x55c32a6cf910, app=app@entry=0x7fe81c112750, flags=flags@entry=2097184, cancellable=cancellable@entry=0x55c32a8f7e80, error=error@entry=0x7fe823166878) at ../plugins/snap/gs-plugin-snap.c:994"
1760231,2018-04-02 03:47:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760240,2018-11-26 14:38:58 UTC,"Thank you for your bug report, that looks like an upstream issue and should be reported on https://gitlab.gnome.org/GNOME/gtk/issues"
1760246,2018-05-01 07:20:50 UTC,Looks like they are already discussing the issue on https://gitlab.gnome.org/GNOME/nautilus/issues/385
1760246,2018-05-01 00:49:55 UTC,"Okay, I just got the confirmation email and copied the bug, see https://gitlab.gnome.org/GNOME/nautilus/issues/394"
1760246,2018-05-01 00:42:44 UTC,https://wiki.ubuntu.com/Bugs/Upstream/GNOME reports here: https://bugzilla.gnome.org/enter_bug.cgi?classification=Core that nautilus has moved to https://gitlab.gnome.org/GNOME/Nautilus
1760246,2018-04-30 15:16:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1760246,2018-05-01 07:19:55 UTC,Sorry for the confusing and thanks for reporting upstream!
1760247,2018-04-02 14:12:12 UTC,"Hi Paulo Vitor,"
1760247,2018-04-22 08:53:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760271,2018-03-31 16:24:59 UTC,New info
1760273,2019-12-17 07:53:34 UTC,"Yep, agreeing tho You-Sheng.
People are seeing this when e.g. using lm-sensores as it will trigger the hwmon interfaces which have plenty of these old calls."
1760273,2019-12-02 05:28:57 UTC,Harmless. There are still 40+ drivers using this API in current mainline kernel v5.4.
1760273,2019-12-01 09:58:17 UTC,Is this bug harmless?
1760273,2018-04-03 14:35:24 UTC,#5 comment addon
1760273,2018-04-05 05:12:00 UTC,kernel 4.15.0-15
1760273,2018-04-03 14:25:46 UTC,Test with 4.15.0-14-generic kernel
1760273,2018-04-03 09:16:00 UTC,Have tested the 4.16 vanilla kernel; and the hwmon warning is gone now.
1760273,2018-04-03 05:24:24 UTC,Still exist in Bionic
1760273,2018-04-02 20:04:07 UTC,Do you happen to know if this bug also exists in Bionic?
1760273,2018-03-31 09:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760273,2018-04-03 14:28:40 UTC,"oem@ubuntu:/boot$ sudo grep hwmon_device_register abi-4.15.0-14-generic
EXPORT_SYMBOL_GPL vmlinux 0x00000000	devm_hwmon_device_register_with_groups
EXPORT_SYMBOL_GPL vmlinux 0x00000000	devm_hwmon_device_register_with_info
EXPORT_SYMBOL_GPL vmlinux 0x00000000	hwmon_device_register   #  <<<<<<<<<<<<<<<<<<<<<
EXPORT_SYMBOL_GPL vmlinux 0x00000000	hwmon_device_register_with_groups
EXPORT_SYMBOL_GPL vmlinux 0x00000000	hwmon_device_register_with_info"
1760278,2020-01-25 16:47:40 UTC,"Muhammed, is still an issue?"
1760278,2020-01-26 09:29:58 UTC,"I don't think so seems bugs solved, after about 2 years. :D"
1760282,2018-04-01 03:32:59 UTC,"this appears to be unrelated to cryptsetup itself.  udisks2 has a Suggests: against libblockdev-crypto2; perhaps it should be a Recommends, or perhaps the gui tools need to be better about automatically pulling in needed components."
1760282,2018-04-01 07:08:07 UTC,"""this appears to be unrelated to cryptsetup itself"""
1760282,2018-04-04 15:42:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760282,2018-04-04 19:42:28 UTC,the suggests needs to be changed to a recommend which is pending on MIRs review (e.g bug #1754422)
1760284,2018-04-24 04:36:23 UTC,"If this issue doesn't happen to Bionic (which uses v4.15 based kernel), I think it's reasonable to upgrade. The bcmwl should work be able to build against v4.15."
1760284,2018-07-24 09:32:24 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1760284,2018-04-02 20:02:02 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1760284,2018-03-31 10:30:08 UTC,This change was made by a bot.
1760284,2018-04-08 19:10:20 UTC,"I installed linux-kernel-4.16.0-041600-generic, I'm able to boot it but Broadcomm WiFI driver which I supsected as a reason fails:
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.16.0-041600-generic /boot/vmlinuz-4.16.0-041600-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.16.0-041600-generic /boot/vmlinuz-4.16.0-041600-generic
ERROR (dkms apport): kernel package linux-headers-4.16.0-041600-generic is not supported
Error! Bad return status for module build on kernel: 4.16.0-041600-generic (x86_64)
Consult s/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information.
ERROR (dkms apport): kernel package linux-headers-4.16.0-041600-generic is not supported
Error! Bad return status for module build on kernel: 4.16.0-041600-generic (x86_64)
Consult /var/lib/dkms/vboxhost/5.0.32/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.16.0-041600-generic /boot/vmlinuz-4.16.0-041600-generic
update-initramfs: Generating /boot/initrd.img-4.16.0-041600-generic
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915"
1760287,2018-03-31 10:45:27 UTC,"The question expired so I'm opening this as a feature request, thanks"
1760287,2019-06-05 13:10:17 UTC,As a workaround you can use this tool https://github.com/sapcc/nova-password
1760295,2019-05-10 12:38:23 UTC,https://github.com/mixxxdj/mixxx/pull/1856
1760302,2018-03-31 14:05:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1760303,2018-03-31 14:30:48 UTC,The cancel_all_events function has been around since kilo so it's somewhat surprising no one has ever reported this before.
1760303,2018-03-31 14:02:47 UTC,Seeing this in a functional test:
1760303,2018-09-24 14:46:54 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1760303,2018-09-10 20:18:49 UTC,"Reviewed:  https://review.openstack.org/592086
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=77a831de8b5ef573527b844c852bf22f775d7787
Submitter: Zuul
Branch:    stable/queens"
1760303,2018-03-31 14:30:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558059"
1760303,2018-04-20 13:12:57 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1760303,2018-04-09 20:09:55 UTC,"Reviewed:  https://review.openstack.org/558059
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d9369d034cb0694def2510885ddfb9b039cbad49
Submitter: Zuul
Branch:    master"
1760303,2018-08-15 15:26:45 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/592086"
1760310,2018-04-11 04:53:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760316,2019-10-09 17:08:18 UTC,https://github.com/mixxxdj/mixxx/pull/2322
1760316,2019-04-30 07:54:18 UTC,just noticed the 'allowFocusWhenParametersHidden' switch is not documented on the wiki..
1760316,2019-04-30 07:51:18 UTC,"> Let's try to go on the same page ..
"
1760316,2019-04-30 06:23:19 UTC,Let's try to go on the same page ..
1760316,2019-04-29 11:23:32 UTC,"I'm afraid somehow we're not on the same page here.
Of course, this is targeted at the controller use case only.
In #3 I explained the constraints of the currently available COs, in #9 I outlined the benefits of a new control in the GUI."
1760316,2019-04-29 06:46:52 UTC,"Is this a use case for focus indicator without a controller?
What do you want to achieve?"
1760316,2019-04-28 15:49:54 UTC,"To be clear:
the existing COs are fine for their purpose (focused effect and show focus) and I'd neither extend nor alter them.
'show_focus' for collapsed FX units is disabled by default in the MAPPINGS, and then it's only allowed when parameters are visible which is fine because it reduces mistakes during FX handling in most use cases."
1760316,2019-04-20 21:01:02 UTC,"We should not touch [EffectUnitN],focused_effect. It's valid to store the focused effect as users might have an effect permanently focused, for example to tweak paramters of the Moog filter or the echo effect."
1760316,2019-04-19 11:24:34 UTC,"[EffectUnitN],focused_effect of unfoccused units is supressd in skins but it's not reset, it's even restored after restart.
So we need something else as unit focus indicator."
1760316,2019-04-18 22:04:53 UTC,"> [EffectRack1_EffectUnitN],focused_effect can be stored for unfocused units as well, so it tells nothing about which unit has controller focus.
"
1760316,2019-04-18 21:37:44 UTC,Unfortunately none of the available controls suits the need.
1760316,2019-04-18 18:54:58 UTC,"I think we can already use <Transform><Not/></Transform> to build widget that indicate that the whole unit has the focus.
Does this work?"
1760316,2019-04-18 06:09:34 UTC,Let's try to outline what we already have and why this does not work.
1760316,2019-04-20 21:50:58 UTC,I am afraid that this could be redundant and by chance ambiguous.
1760316,2019-04-19 22:38:13 UTC,"This sounds like a mapping issue. If the mapping changes the focus away from the unit, we can require to set [EffectUnitN],focused_effect zero."
1760319,2018-04-07 14:01:58 UTC,Bug no longer seems to affect me as of (roughly) April 6.
1760323,2020-09-18 11:39:35 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1760325,2018-09-29 03:48:15 UTC,Still an issue in Kubuntu 18.10.
1760325,2018-09-29 03:48:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760331,2018-04-26 07:50:46 UTC,"I can confirm, that plank is unable to detect existing windows in KDE Plasma 5.12.*
Plank is always shown if i use intellihide or any window dodge-mode."
1760331,2018-05-29 11:24:04 UTC,"Confirmation: with Plasma 5.12.5, KDE-Frameworks 5.46.0 intellihide is working again.
I have Arch Linux (I report it for the sake of completeness, I know this is  a distro-independent issue)."
1760331,2018-05-11 17:05:11 UTC,Same here! (Plasma 5.12.4)
1760331,2018-05-27 07:54:53 UTC,Intellihide works since latest KDE update (@Kubuntu 18.04) again.
1760331,2018-05-29 07:18:33 UTC,"Confirmation: window dodge-modes and intellihide working
fine again after KDE updates."
1760331,2018-05-14 13:12:07 UTC,Same here for ArchLinux with KDE Plasma 5.12.5 and KDE Frameworks 5.45.0
1760337,2018-12-04 08:37:52 UTC,"Thanks for the great explanation.  That seems to indeed being an issue with ""overlay"" releases.  I'm currently uncertain how to approach this and fix it, but your analysis is correct and helpful."
1760338,2019-02-01 03:43:02 UTC,Can confirm that removing xserver-xorg-input-synaptics fixes the issue.
1760338,2018-10-15 10:43:04 UTC,"""The Trackpad Hotkey continues to be recognized however the same 'Trackpad deactivated' graphic pops-up every time Fn+F5 hotkey is depressed. This is somehow not linked to the Enable/Disable Trackpad functionality in Gnome Control Center/Settings (i.e. does nothing)."""
1760338,2018-10-15 10:22:32 UTC,"So sorry to bug you on this Peter, but could we please have your 2 cents on this issue? Many thanks"
1760338,2018-10-15 10:06:51 UTC,"updated kernels have also failed (can't find how to add requested tags, sorry)"
1760338,2018-12-18 07:44:41 UTC,"Deleting the synaptics driver resolves the issue.
It appears the driver needs to be deleted with the introduction of the libinput driver (now that the synaptics driver has been deprecated)."
1760338,2018-10-12 14:53:40 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1760338,2018-10-12 08:38:21 UTC,The Trackpad Hotkey continues to be recognized however the same 'Trackpad deactivated' graphic pops-up every time Fn+F5 hotkey is depressed. This is somehow not linked to the Enable/Disable Trackpad functionality in Gnome Control Center/Settings (i.e. does nothing).
1760338,2018-09-25 05:18:28 UTC,affects bionic
1760338,2018-09-13 09:57:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760338,2018-09-13 09:55:44 UTC,"Upgraded from 16.04 to 18.04.1 LTS.
Similar issue encountered where Fn keys are working (audio, mute, bright, volume and even wifi) except for enable/disable touchpad.
However, Touchpad disabled graphic is displayed (indicating recognition) but unfortunately has no effect i.e. not able to enable/disable using Fn key (Fn+F5)."
1760338,2018-10-13 01:05:22 UTC,"No, they started in a fresh new installation (18.04).
Sorry, I can't test it anymore cause I changed to Deepin and, last month, I changed back to Ubuntu but I completely removed gnome and installed DDE as my window manager. So sorry."
1760338,2018-10-15 10:30:08 UTC,"Hi Joseph,"
1760344,2018-03-31 19:58:33 UTC,"StacktraceTop:
 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:62
 std::char_traits<char>::length (__s=0x0) at /usr/include/c++/6/bits/char_traits.h:267
 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::append (__s=0x0, this=0x5625e8f5cf70) at /usr/include/c++/6/bits/basic_string.h:1128
 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator+= (__s=0x0, this=0x5625e8f5cf70) at /usr/include/c++/6/bits/basic_string.h:1052
 CRenderSystemGL::InitRenderSystem (this=0x5625e8f5cec8) at RenderSystemGL.cpp:113"
1760344,2018-04-15 02:02:55 UTC,"Is this something you can still reproduce?  If so, please attach the output of ""grep kodi /var/log/dpkg.log*"""
1760344,2018-04-16 17:37:51 UTC,"/var/log/dpkg.log:2018-04-13 13:55:06 upgrade kodi-data:all 2:17.6+dfsg1-1 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:55:06 status half-configured kodi-data:all 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:06 status unpacked kodi-data:all 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:06 status half-installed kodi-data:all 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:08 status half-installed kodi-data:all 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:09 status unpacked kodi-data:all 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:55:09 status unpacked kodi-data:all 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:55:09 upgrade kodi-bin:amd64 2:17.6+dfsg1-1 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:55:09 status half-configured kodi-bin:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:09 status unpacked kodi-bin:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:09 status half-installed kodi-bin:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:10 status half-installed kodi-bin:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:10 status unpacked kodi-bin:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:55:10 status unpacked kodi-bin:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:55:10 upgrade kodi:amd64 2:17.6+dfsg1-1 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:55:10 status half-configured kodi:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:10 status unpacked kodi:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:10 status half-installed kodi:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:10 status half-installed kodi:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:10 status half-installed kodi:amd64 2:17.6+dfsg1-1
/var/log/dpkg.log:2018-04-13 13:55:13 status unpacked kodi:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:55:13 status unpacked kodi:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:05 configure kodi-data:all 2:17.6+dfsg1-1build1 <none>
/var/log/dpkg.log:2018-04-13 13:56:05 status unpacked kodi-data:all 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:05 status half-configured kodi-data:all 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:05 status installed kodi-data:all 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:05 configure kodi-bin:amd64 2:17.6+dfsg1-1build1 <none>
/var/log/dpkg.log:2018-04-13 13:56:05 status unpacked kodi-bin:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:06 status half-configured kodi-bin:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:06 status installed kodi-bin:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:07 configure kodi:amd64 2:17.6+dfsg1-1build1 <none>
/var/log/dpkg.log:2018-04-13 13:56:07 status unpacked kodi:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:07 status half-configured kodi:amd64 2:17.6+dfsg1-1build1
/var/log/dpkg.log:2018-04-13 13:56:08 status installed kodi:amd64 2:17.6+dfsg1-1build1"
1760344,2018-04-17 16:41:47 UTC,Thank you for that.  Can you please attach the files under /var/log/apt/ as well?
1760344,2018-04-17 16:44:07 UTC,"and the output of ""sudo dpkg --configure -a"", please"
1760344,2018-04-17 17:13:23 UTC,"at this time, i have not this problem.
i think this is resolving, but i dont know how..."
1760344,2019-03-11 20:46:59 UTC,"Sorry for the late response.  So, you no longer experience this issue?"
1760344,2019-03-14 00:06:42 UTC,no problem. no i don't experience anymore.
1760344,2020-02-18 10:37:33 UTC,I am happy to hear you are no longer experiencing this issue.
1760351,2018-04-01 00:20:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1760351,2018-05-08 17:44:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760355,2018-04-02 22:32:06 UTC,The version of rsvg i am using is 2.40.13
1760355,2018-04-13 12:07:22 UTC,Thanks for taking the time to report this bug and helping to make Ubuntu better.
1760355,2018-04-18 07:00:33 UTC,"It looks like this was reported in https://gitlab.gnome.org/GNOME/librsvg/issues/247, which upstream claims was fixed in 2.40.19. Possibly this is commit https://gitlab.gnome.org/GNOME/librsvg/commit/05fd03117bffbae36b28b5ea7934520b46751476 ."
1760355,2018-04-02 14:08:05 UTC,"Hi Shyamkumar,"
1760358,2018-08-16 23:45:45 UTC,Hello
1760358,2018-08-16 23:51:05 UTC,"Ah!!! Actually, this does work,"
1760366,2018-04-04 01:57:09 UTC,Thanks.
1760366,2018-04-03 19:38:56 UTC,"I should have mentioned that I'm using the ""GNOME Flashback (Compiz)"" desktop, sorry about that."
1760366,2018-04-03 06:49:27 UTC,Sorry about that. I can't seem to reproduce the issue with Terminal...
1760366,2018-04-03 05:57:21 UTC,"I don't think that is correct, the screenshot I attached is from the Terminal application, which doesn't have any additional UI in the titlebar. It wasn't this tall a week ago."
1760366,2018-04-03 01:58:59 UTC,Tall titlebars are only used in cases where they may contain buttons etc. This is the design from upstream and we intend to keep it in Ubuntu.
1760366,2018-04-03 06:51:33 UTC,Correction:
1760371,2018-04-01 09:22:38 UTC,"This was a system that generally stayed on 24/7, so I am not sure what updates might have caused this to happen.  The last update before the system rebooted occurred at ""Start-Date: 2018-03-31  09:57:33"", see attached update history file."
1760371,2018-04-01 09:24:26 UTC,"With libpam-kwallet4 and libpam-kwallet5 removed, I've attached the output of ""journalctl -p err -b -r"" for you to inspect as well, see journalerrs.log."
1760371,2018-04-01 09:57:05 UTC,"Based on the discussion from https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535, libpam-kwallet errors appear to be a non-issue in this case. I am still unsure as to why lightdm and gdm are failing but lxdm succeeds albeit with a now-crippled desktop environment. The gdm failure messages appeared to be much less helpful, something to the effect of: ""CRITICAL: We failed, but the fail whale is dead""."
1760371,2018-04-02 03:12:37 UTC,"See additional logs files attached. This is a hybrid Intel/AMD system, but the Intel graphics is the only one used as far as I know:"
1760371,2018-04-02 06:51:32 UTC,"Here is also the boot history, to match against the software install/update history log that I attached earlier. The issue occurred on the first reboot on March 31st, the prior successful reboot was March 13th. The history.log file shows updates to systemd and openbox on March 25th that may be relevant to this issue, but I do not know what else to do to investigate the underlying cause."
1760371,2018-04-03 08:18:58 UTC,"Apparently, I've had VirtualBox guest utilities installed on my host system which you are generally just supposed to run on the guest. This issue only occurred when the package was updated. After trial and error, I've found that the offending package is virtualbox-guest-x11:amd64 (5.1.34-dfsg-0ubuntu1.16.04.2), none of the other virtualbox-guest packages cause this problem."
1760371,2018-10-07 04:23:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760375,2018-04-01 02:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760375,2018-04-01 14:19:00 UTC,"it's easy to reproduce, no log needed."
1760375,2018-04-02 20:00:30 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1760375,2018-04-03 01:35:44 UTC,"same phenomenon after update latest v4.16 kernel.
this should have concern with systemd-logind.service, tasks have been added into session cgroup."
1760391,2020-10-30 11:05:43 UTC,"Hello,"
1760391,2018-08-03 12:54:33 UTC,I see this as well. Ran into this problem on both physical and virtual machines.
1760391,2018-05-10 04:26:58 UTC,1) Bionic x86_64 (also with Virtualbox)
1760391,2019-08-01 07:22:12 UTC,Same problem on disco with acpid 2.0.31-1ubuntu2.
1760391,2018-05-10 03:35:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760397,2018-04-01 09:56:35 UTC,"StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x1) at ../../../../gobject/gtype.c:4129
 g_signal_emit_valist (instance=0x1, signal_id=475, detail=0, var_args=var_args@entry=0x7ffe56934ca0) at ../../../../gobject/gsignal.c:3176
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../../../../gobject/gsignal.c:3447
 g_closure_invoke (closure=0x55de62d68a20, return_value=0x0, n_param_values=1, param_values=0x7ffe56934f40, invocation_hint=0x7ffe56934ec0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55de63897770, detail=detail@entry=0, instance=instance@entry=0x55de650c0920, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffe56934f40) at ../../../../gobject/gsignal.c:3635"
1760397,2018-04-20 00:26:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760398,2020-08-02 22:35:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760405,2019-10-22 20:05:15 UTC,This issue was fixed in the openstack/openstacksdk 0.11.4 release.
1760405,2018-06-18 00:49:08 UTC,This issue was fixed in the openstack/openstacksdk 0.14.0 release.
1760405,2018-06-01 03:11:03 UTC,"These patches fixed the bug.
https://review.openstack.org/#/c/555142/
https://review.openstack.org/#/c/571101/"
1760405,2018-05-04 00:28:13 UTC,"@Brian Haley, sorry for the late, I'll look at this bug in recent days."
1760405,2018-05-03 18:03:47 UTC,@Dongcan - have you had a chance to look at this yet?  It actually affects more than just floating ip commands.  Thanks.
1760405,2018-04-05 20:03:51 UTC,"The ""old"" neutronclient shows the correct failure message:"
1760405,2018-04-05 20:01:17 UTC,So it seems neutron-server returns the error we want:
1760405,2018-04-02 08:35:47 UTC,Reproduced in master too.
1760405,2018-05-30 14:15:08 UTC,Now being tracked in storyboard.
1760433,2021-01-30 19:07:30 UTC,This is still an issue with updated snaps occurring on Ubuntu MATE 20.04 and 20.10 running plank 11.89-1.
1760433,2020-07-22 16:18:16 UTC,"I see this commit mentioned above ""Increase delay for auto-removal of broken/unavailable applications to 1 min"" is included in the latest release (0.11.89)."
1760433,2018-09-28 11:33:52 UTC,"I've only experienced this with apps updated via snapd. Every time a new version of IntelliJ IDEA is released, the icon disappears from my Dock. Apps installed via apt or flatpak have been unaffected so far."
1760433,2019-03-08 18:48:21 UTC,Expected workaround https://git.launchpad.net/plank/commit/?id=0a842b45dae54c3457f55c7db39f12155050e75a
1760433,2019-03-08 18:27:54 UTC,There's a thread of Manjaro linux users who have the same problem:
1760433,2020-06-10 00:26:27 UTC,Is the above commit in the version? I still experience this bug and it's a pain in the ass. Ubuntu 18.04.
1760449,2018-04-01 16:12:15 UTC,Patch to set APBS_PSIZE_LOCATION and APBS_PDB2PQR_LOCATION to the locations used in the ubuntu pdb2pqr package for psize.py and pdb2pqr.py scripts required by the APBS Tools 2.1 plugin.
1760449,2018-04-01 16:15:09 UTC,"To clarify, the steps to reproduce the functionality of the patched pymol, the correct steps are described for Example 1 at https://pymolwiki.org/index.php/Apbsplugin"
1760449,2018-04-01 16:19:16 UTC,"The attachment ""apbs_path_fix.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1760450,2018-08-07 16:17:52 UTC,"The problem hasn't occurred so far after adding ""csi_mod.scan=sync""."
1760450,2018-08-06 18:12:24 UTC,"Hi. I faced a similar issue and when I tried to add ""scsi_mod.scan=sync"" to /etc/default/grub and then run update-grub I got the following error:
/usr/sbin/grub-mkconfig: 36: /etc/default/grub: scsi_mod.scan=sync: not found"
1760450,2018-08-07 21:48:35 UTC,Hi Vedant.  Change the line in /etc/default/grub e.g.
1760450,2018-06-15 10:08:16 UTC,"Thanks for your confirmation, Julien.  I have asked Ubuntu to import the proper fix from upstream and they responded very promptly.  See:"
1760450,2018-06-14 09:30:25 UTC,"I confirm that adding ""scsi_mod.scan=sync"" does indeed fix this bug."
1760450,2018-05-31 05:35:28 UTC,@Daniel
1760450,2018-04-01 16:24:52 UTC,"StacktraceTop:
 _dl_fixup (l=0x559c10faa5a0, reloc_arg=<optimized out>) at ../elf/dl-runtime.c:84
 _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125
 create_bits_picture (yoff=0x7fff0a6c9594, xoff=0x7fff0a6c9590, has_clip=1, pict=0x559c129a29d0) at ../../../../fb/fbpict.c:325
 image_from_pict_internal (pict=pict@entry=0x559c129a29d0, has_clip=has_clip@entry=1, xoff=xoff@entry=0x7fff0a6c9590, yoff=yoff@entry=0x7fff0a6c9594, is_alpha_map=is_alpha_map@entry=0) at ../../../../fb/fbpict.c:457
 wfb_image_from_pict (pict=pict@entry=0x559c129a29d0, has_clip=has_clip@entry=1, xoff=xoff@entry=0x7fff0a6c9590, yoff=yoff@entry=0x7fff0a6c9594) at ../../../../fb/fbpict.c:487"
1760450,2018-05-29 04:46:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760450,2018-04-04 11:20:16 UTC,Hi Ubuntu users!  Signal 7 is SIGBUS.  SIGBUS should be relatively unusual on x86 [1].
1760450,2018-05-29 08:09:16 UTC,"I found it hard to follow your log files because of so many errors from extension ""<email address hidden>"". Maybe try removing your extensions if they're that buggy/noisy."
1760450,2018-05-29 08:22:23 UTC,"Uh, if anyone else is affected by this, there's a trivial fix upstream already (and a workaround).  Hop to it, Ubuntu.  gregkh is looking disappointed at you :-).  I checked, and it looks like you didn't apply it to you 4.15 tree.  See end for links to the fix etc."
1760457,2018-05-20 13:10:58 UTC,"Hi Charles,"
1760460,2019-07-19 19:15:34 UTC,Thank you for filing a bug.  Cloud-init does not provide the INSTANCE_ID env variable for runcmd as you say.  You may be interested in using the instance-data.json in a jinja template.  Please take a look:
1760463,2018-04-17 21:15:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760463,2020-03-17 08:01:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760463,2020-05-17 04:17:25 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1760471,2018-04-06 09:10:25 UTC,Related THT review (Related-Bug magic comment didn't link it here for some reason): https://review.openstack.org/559268 Set ulimit for neutron agent containers
1760471,2018-04-06 08:50:53 UTC,"> For glance and cinder package changes to increase the ulimit file and process to 131072
> with reasoning why they need it
"
1760471,2018-04-05 15:12:01 UTC,"<<< nofile=24096 is still too high for any neutron agent needs, In the past (baremetal) we were running with 1024, and that is fine. Leaves the rootwrap-daemon execution back to 3ms , This is a critical factor to many customers. We spent a lot of time coming up with the rootwrap-daemon solution which helped with scale a lot. Otherwise we'd be on regresion.
Yes 24096 is too high, i just used this number to show the difference in performance using the reproducer.
1024 should be enough for agents atleast as they used to run with this and and can be done as jistr mentioned."
1760471,2018-04-05 14:57:35 UTC,"I'd be careful with lowering the file limit globally, i think e.g. MariaDB needs at least 16K for common operation."
1760471,2018-04-05 14:38:20 UTC,This should be fixed for production too.
1760471,2018-04-05 14:40:00 UTC,"nofile=24096 is still too high for any neutron agent needs, In the past (baremetal) we were running with 1024, and that is fine. Leaves the rootwrap-daemon execution back to 3ms , This is a critical factor to many customers. We spent a lot of time coming up with the rootwrap-daemon solution which helped with scale a lot. Otherwise we'd be on regresion."
1760471,2018-04-05 12:56:57 UTC,"<< Another option would be to lower the global docker NOFILE ulimit in the docker systemd unit, but only when ran on CI.
I think we can start by setting limit nofile for neutron agents containers(and other services which are relying on oslo-rootwrap-daemon)"
1760471,2018-04-05 12:20:09 UTC,Latest Docker changes on NOFILE ulimit:
1760471,2018-04-05 12:14:55 UTC,"Another option would be to lower the global docker NOFILE ulimit in the docker systemd unit, but only when ran on CI."
1760471,2018-04-05 12:04:25 UTC,"By default, docker containers inherits ulimits from limits of the docker deamon. On Fedora 27, the daemon gets NOFILE=1048576 limit from LimitNOFILE=1048576 in /usr/lib/systemd/system/docker.service."
1760471,2018-04-05 11:47:16 UTC,"The performance difference likely comes from close_fds=True of subprocess.Popen. On Python 2, Popen calls close(fd) on all file descriptors from 3 to SC_OPEN_MAX. On my Fedora 27 ""host"", SC_OPEN_MAX is 1,024. But in docker, SC_OPEN_MAX is... 1,048,576: 1,000x larger."
1760471,2018-04-05 12:59:40 UTC,"For Example, something similar to below:-"
1760471,2018-04-05 14:19:56 UTC,"> but only when ran on CI.
"
1760479,2018-04-01 22:02:39 UTC,"sorry, I wasn't triggering the correct rules in ds-identity to cause cloud-init to bring up the network."
1760479,2020-10-09 19:53:37 UTC,Marking invalid based on the comment above. Thanks for following up!
1760493,2018-04-02 05:44:31 UTC,"Edit: It suffices to create an (empty) selection set (in an empty document), then applying any extension (which 'does something', meaning which doesn't leave the document unchanged). Then most actions afterwards (e. g. inserting an object) let Inkscape crash.
Tested with 0.92.3 (2405546, 2018-03-11), Win 8.1."
1760493,2018-04-02 06:07:15 UTC,"Another addition:
After applying any extension assigning new selection sets in the GUI is not possible anymore as mentioned. But: When looking into the XML-Editor, there appear (empty) extension sets, when clicking the plus symbol in the extension sets dockable dialog (on Save and Reload they will be also visible in the GUI). So maybe that's of interest to track the bug down that there is this discrepancy between the GUI and the file."
1760493,2018-04-02 07:54:59 UTC,So another addition (and workaround):
1760493,2018-04-02 10:08:07 UTC,"running Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1760493,2018-04-02 10:14:02 UTC,backtrace for crash in Case 2:
1760512,2019-09-26 23:19:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760514,2018-04-05 04:14:35 UTC,And my exact error is:
1760514,2018-04-24 09:59:12 UTC,"Christian, please triage."
1760514,2018-04-05 03:46:12 UTC,Just had this same problem.
1760514,2018-04-02 00:03:40 UTC,perhaps related to bug 1687079 but maybe not?
1760516,2020-03-12 17:18:06 UTC,fixed by disabling custom scaling and letting Qt do the app scaling
1760517,2018-04-02 01:42:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558139"
1760517,2018-04-04 02:11:04 UTC,"Reviewed:  https://review.openstack.org/558139
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=f8d8b0316c27ab9a1bc6ed7694ca08b793890855
Submitter: Zuul
Branch:    master"
1760517,2019-02-12 10:03:37 UTC,os-client-config / shade should be replaced by openstacksdk
1760517,2019-09-12 13:22:02 UTC,"per and os-client-config have been unpinned, shade is still there because some kolla_* Ansible modules rely on them."
1760536,2021-02-17 17:10:01 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1760536,2018-04-02 16:02:04 UTC,You'll need to look at the ironic/nova logs on the undercloud to determine failure.
1760539,2018-04-03 08:53:52 UTC,apport information
1760539,2018-04-03 08:53:55 UTC,apport information
1760539,2018-04-03 08:53:56 UTC,apport information
1760539,2018-04-03 08:53:58 UTC,apport information
1760539,2018-04-03 08:53:59 UTC,apport information
1760539,2018-04-03 08:54:01 UTC,apport information
1760539,2018-04-03 08:54:02 UTC,apport information
1760539,2018-04-03 08:53:51 UTC,apport information
1760539,2018-04-03 08:54:05 UTC,apport information
1760539,2018-04-03 08:54:07 UTC,apport information
1760539,2018-04-03 08:54:11 UTC,apport information
1760539,2018-04-03 08:54:13 UTC,apport information
1760539,2018-04-03 09:39:06 UTC,"IIRC, this is a limitation of the FW of ath10k, it can't correctly report the connection speed."
1760539,2018-04-03 12:04:23 UTC,"ok.
that's great."
1760539,2018-04-03 08:54:04 UTC,apport information
1760539,2018-04-03 08:53:48 UTC,apport information
1760539,2018-04-03 07:53:43 UTC,apport information
1760539,2018-04-03 07:54:11 UTC,apport information
1760539,2018-04-02 06:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760539,2018-04-02 19:52:43 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1760539,2018-04-03 07:49:57 UTC,"1. I installed Kubuntu 18.04 beta-1, after it was released, and from first day, I always have been getting:
Bit Rate=1 Mb/s on 2.4G, and
Bit Rate=6 Mb/s on 5G."
1760539,2018-04-03 07:53:41 UTC,apport information
1760539,2018-04-03 07:53:46 UTC,apport information
1760539,2018-04-03 07:53:48 UTC,apport information
1760539,2018-04-03 07:53:49 UTC,apport information
1760539,2018-04-03 07:53:51 UTC,apport information
1760539,2018-04-03 08:53:47 UTC,apport information
1760539,2018-04-03 07:53:56 UTC,apport information
1760539,2018-04-03 07:53:57 UTC,apport information
1760539,2018-04-03 07:53:59 UTC,apport information
1760539,2018-04-03 07:54:01 UTC,apport information
1760539,2018-04-03 07:54:03 UTC,apport information
1760539,2018-04-03 07:54:05 UTC,apport information
1760539,2018-04-03 07:54:09 UTC,apport information
1760539,2018-04-03 07:53:54 UTC,apport information
1760545,2018-11-13 18:51:26 UTC,This bug was fixed in the package linux - 4.15.0-39.42
1760545,2018-11-12 08:48:19 UTC,This bug was fixed in the package linux-oem - 4.15.0-1024.29
1760545,2018-11-02 07:18:34 UTC,"The kernel is in bionic-proposed, -39.42. For some reason this bug wasn't spammed about it."
1760545,2018-11-02 05:48:57 UTC,Thanks! Is there a timeline for wen this new linux-generic kernel may be released for 18.04 / 4.15.x?
1760545,2018-10-29 06:44:50 UTC,The fix will be in next -generic kernel release.
1760545,2018-10-24 10:47:52 UTC,This bug was fixed in the package linux-oem - 4.15.0-1024.29
1760545,2018-10-24 06:51:22 UTC,Verified by Alex Tu.
1760545,2018-10-28 04:58:50 UTC,"Hi Guys,"
1760545,2018-05-07 21:32:16 UTC,Attached is the patch (or commit b607990c76ceda0a7a7ceacabab174cdc8b9beee).
1760545,2018-04-02 10:19:27 UTC,This should be a regression issue. We don't find this in 17.10.
1760545,2018-10-07 21:51:00 UTC,What is the timeline for having this fix backported to the 4.15 kernel?
1760545,2018-04-04 23:19:01 UTC,"from the log file, we found glk_dmc firmware load failed."
1760545,2018-04-13 19:02:16 UTC,"We have the exact same glk_dmc file in our linux-firmware package, which we received from upstream linux-firmware. The additional files should not be needed. The -2 error code does indicate it couldn't find the file, but perhaps the linux-firmware package was not up to date?"
1760545,2018-05-07 21:23:25 UTC,A mainline patch is available now in v4.17-rc4.
1760545,2018-04-13 20:21:43 UTC,"$ modinfo -F firmware /lib/modules/$(uname -r)/kernel/drivers/gpu/drm/i915/i915.ko
i915/bxt_dmc_ver1_07.bin
i915/skl_dmc_ver1_26.bin
i915/kbl_dmc_ver1_01.bin
i915/skl_guc_ver6_1.bin
i915/kbl_huc_ver02_00_1810.bin
i915/bxt_huc_ver01_07_1398.bin
i915/skl_huc_ver01_07_1398.bin"
1760545,2018-04-24 13:06:53 UTC,I've already submitted a patch to mainline Cc: stable (https://patchwork.kernel.org/patch/10335195) which will address this issue if accepted (note: the current discussion is about the 'acceptability and health' of using the firmware with recent kernels.
1760545,2018-04-13 19:55:34 UTC,"Oh, or likely the issue is that the firmware doesn't get included in the initrd because there's no MODULE_FIRMWARE statement for it in the driver."
1760561,2018-04-03 03:21:07 UTC,"# NOTE(gordc): set single thread to process data sequentially
# if batching enabled.
batch = (1 if self.conf.notification.batch_size > 1
         else self.conf.max_parallel_requests)"
1760579,2019-01-12 12:54:28 UTC,修正しました。emojiでも検索に引っかかると思います。19.04から適用されるはずです。
1760584,2020-02-24 09:21:32 UTC,"The issue, based on the comments, got resolved in the neutron-tempest-plugin, so from tempest perspective, this can be closed then. I'll mark it as Invalid. If you feel like there is a change needed in tempest, provide info and feel free to reopen it."
1760584,2018-04-06 17:13:03 UTC,I agree with Brian that it should be changed to /30 in test. But maybe we should also add some additional validation on Neutron's side and raise some error when user tries to do such small subnet with no any IP address available.
1760584,2018-04-02 13:21:27 UTC,"Actually, we found that running this on OVN also fails, since it is allocating a DHCP port all the time for metadata, so using --disable-dhcp won't work in that case.  So maybe changing to a /30 is the best solution."
1760584,2018-12-10 21:17:25 UTC,The bug that was causing the OVN failure was fixed in https://review.openstack.org/#/c/559771/ - it changed the subnet cidr to a /29 so it should always succeed.
1760584,2018-04-02 13:13:54 UTC,"The other option is to pass ""disable-dhcp"" when creating the subnet.  I guess I would prefer this since technically a /31 is valid for a subnet (point to point links)."
1760592,2018-04-15 08:29:17 UTC,"Hi vpc, please check this doc:"
1760593,2018-04-02 21:41:04 UTC,"Hello Hans,"
1760593,2018-04-04 18:10:47 UTC,"> Why can't hp-setup simply connect to it and configure it as a scanner?
"
1760593,2018-04-05 00:44:41 UTC,Desktop computer (the one with which the MFC was configured with):
1760593,2018-04-05 10:50:51 UTC,"The only thing needed for the scanning function to work from the desktop is to get its device URI. This is done by libsane-hpaio and its dependencies. The URI is formed from what is obtained from the dns-sd broadcasts of the OfficeJet Pro 6970 and an entry for it in /usr/share/hplip/data/models/models.dat. /etc/sane.d/dll.d/hplip contains ""hpaio"" and running something like xsane should just work."
1760593,2018-04-05 11:28:46 UTC,This is what I got:
1760593,2018-04-05 13:48:45 UTC,"> There was a lot of output which I believe was not relevant,
> thus I filtered the output. If I am wrong, tell me what I
> should be looking for.
"
1760593,2018-04-12 00:24:39 UTC,"Ok, copying models.dat from the desktop (which worked) to the laptop (which didn't work) made scanning possible.  It resolved my problem (but not this issue)."
1760599,2018-12-06 23:56:08 UTC,"I created a branch to fix this, called user/sandbergja/lp1760599_disable_merge_records_unless_multiple_records_selected"
1760599,2019-03-05 21:01:36 UTC,Works as advertised.  Sign off pushed to user/rogan/lp1760599
1760599,2019-05-23 21:32:32 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jane and Rogan!"
1760601,2018-12-07 23:12:29 UTC,"Update: you can close this modal using the Esc key.  That appears to be the only way, though."
1760601,2020-12-17 00:25:13 UTC,Note that this is fixed in the angular staff catalog.
1760608,2018-04-02 15:34:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760608,2018-04-02 15:43:15 UTC,For 16.04 LTS xenial the copy command should be:
1760608,2018-04-06 21:47:12 UTC,"The correct solution is to modify the import in axi-info to ""from ConfigParser"" to ""from configparser"". If someone created a debdiff I'd be happy to sponsor it."
1760612,2018-07-08 23:27:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760621,2019-11-16 07:21:46 UTC,"Hi, Linux Uprising has a PPA for Guake and it serves 3.6.3 which have this issue fixed. https://www.linuxuprising.com/2019/05/new-guake-drop-down-terminal-ppa-ubuntu.html"
1760621,2019-05-04 09:11:25 UTC,"> I doubt this package is still maintained.
"
1760621,2018-12-07 20:53:44 UTC,The solution found by Raül worked for me. Thanks Raül.
1760621,2019-05-03 19:54:18 UTC,"Hi. I am the maintainer of Guake. I try to fix bugs on HEAD as much as possible and I have very good contributors that fixes bugs or even adds new features. But I do not maintain backport, since the paste version is itself backward compatible up to Ubuntu 16.04.
So in short, latest version of Guake can be installed on any Ubuntu since 16.04. That’s the way Guake is developped.
And yes since 3.x libtempter0 is a mandatory dependency."
1760621,2019-05-03 18:12:53 UTC,"@Daniel Echeverry or @epsilon77 , would you please update the bionic package to 3.0.6 since this issue is fixed in 3.0.6. See the following links for references."
1760621,2019-05-02 19:11:43 UTC,Great fix Raul! How do I implement it?
1760621,2019-03-06 06:23:13 UTC,"Sorry, I comment #17 before try #3. Fixed by comment #3 too."
1760621,2019-03-06 05:52:38 UTC,I fixed this bug in this way.
1760621,2019-02-16 07:05:37 UTC,Raül Cambeiro's fix worked for me as well on Ubuntu 18.04.1 with Guake Terminal 3.0.5.
1760621,2018-11-01 17:04:56 UTC,Fixed by comment #3
1760621,2018-05-08 17:37:44 UTC,I can confirm the fix in #3 works. Thanks Raül!
1760621,2018-10-03 16:17:38 UTC,If you look at this ticket on github about this bug (https://github.com/Guake/guake/issues/1198) most people fix this by installing libutempter0 on Ubuntu 18.04. This library is not set as a dependency of guake. I wonder if it sholud be.
1760621,2018-09-27 10:28:25 UTC,+1 fix works by Raül Cambeiro
1760621,2018-08-07 10:30:09 UTC,"I doubt this package is still maintained. This bug was opened in april, it's VERY critical (in fact, it makes Guake unusable) but nobody cares."
1760621,2018-08-02 23:48:33 UTC,"I second flan_suse's comment; having a backport of this bug to the Ubuntu repositories seems like the right thing to do. I'd be happy to get involved to help, but I've never contributed a Ubuntu patch before, so I'd need quite a bit of handholding to move forward. Is there someone on the Guake maintainer team who could give me some pointers?"
1760621,2018-07-27 17:00:55 UTC,I confirm that the solution pointed out by Raül Cambeiro (comment #3) worked for me too.
1760621,2018-07-17 14:19:32 UTC,The 18.10 repositories already provide Guake 3.3.0:
1760621,2018-07-17 14:15:59 UTC,"So this fix will never make it to the Ubuntu 18.04 repositories? It was applied a long time ago upstream, yet the latest version in the 3.0.x series is 3.0.5, which contains the bug. According to Ubuntu's package update policies, 18.04 users will forever be stuck with 3.0.x. There is no version 3.0.6 which contains the upstream fix that is available on the 18.04 repositories."
1760621,2018-05-08 17:37:13 UTC,I confirm that the solution pointed out by Raül Cambeiro worked for me.
1760621,2018-05-08 10:31:17 UTC,"This has already been fixed upstream. It's a Python indenting issue.
https://github.com/Guake/guake/commit/f8699b4be6c058fd58a33a1d783cd404e9076b0e"
1760621,2018-04-05 07:20:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760621,2018-10-06 11:50:51 UTC,Fixed by comment #3
1760631,2018-04-03 15:29:06 UTC,Spent some time today suspecting my network... and replacing switches to see if it's that. It doesn't seem to be.
1760641,2018-04-05 08:30:58 UTC,The package has been published and the bug is being set to Fix Released
1760641,2018-04-03 13:31:32 UTC,Hardware Certification have begun testing this -proposed kernel.
1760641,2018-04-04 22:39:34 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/4.4.0-119.143~14.04.1/trusty-4.4-proposed-published.html"
1760641,2018-04-03 16:20:25 UTC,Wass successful with the initial kernel spin and only regression fixes since then.
1760641,2018-04-05 07:40:19 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-119.143~14.04.1
1760644,2019-03-21 13:25:46 UTC,"Sure Sneha, go ahead!"
1760644,2019-03-21 13:09:38 UTC,"If no work has been done, can I take this issue?"
1760644,2018-05-03 15:45:23 UTC,Thanks for this report.
1760644,2019-09-27 19:44:21 UTC,"A lot of fixes have been made to the api-ref - I'm closing this catch-all bug as Fixed at the moment. If there are specific mistakes that we find after these fixes, new bugs can be opened and actioned upon."
1760644,2019-07-26 22:02:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/673112"
1760644,2019-04-04 20:09:40 UTC,"Reviewed:  https://review.openstack.org/617175
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=2736d4adcc7d5f8d8d41ae040d31557a77a2a717
Submitter: Zuul
Branch:    master"
1760644,2019-04-04 17:02:32 UTC,"Reviewed:  https://review.openstack.org/648796
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=4ffca949c20d46434f82e549bb406bd5706b686a
Submitter: Zuul
Branch:    master"
1760644,2019-04-04 16:55:47 UTC,"Reviewed:  https://review.openstack.org/648568
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=5bf0337396b108623eb240efb4794ec2ded323fd
Submitter: Zuul
Branch:    master"
1760644,2019-04-04 16:46:00 UTC,"Reviewed:  https://review.openstack.org/648547
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=f185ff0f446102c28bf333bb8c531ccb85a07744
Submitter: Zuul
Branch:    master"
1760644,2019-04-04 16:45:36 UTC,"Reviewed:  https://review.openstack.org/623559
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=d7140ffe0915655652ae5b8308fbd519a26b9851
Submitter: Zuul
Branch:    master"
1760644,2019-07-27 10:30:32 UTC,"Reviewed:  https://review.opendev.org/673112
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=b39bc70093f0d263e7df6d144a785a5b3b58ea25
Submitter: Zuul
Branch:    master"
1760644,2019-03-29 00:49:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648568"
1760644,2019-03-28 22:01:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648547"
1760644,2019-03-28 01:19:27 UTC,"Reviewed:  https://review.openstack.org/648005
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=41d243c3948b041d46e516380212e41b128baa49
Submitter: Zuul
Branch:    master"
1760644,2019-03-27 20:22:05 UTC,"Reviewed:  https://review.openstack.org/647973
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=5cd643785d81784d61e4d9b49ff0707ff5dd4ed9
Submitter: Zuul
Branch:    master"
1760644,2019-03-27 07:03:25 UTC,https://review.openstack.org/#/c/647973/ is another partial fix.
1760644,2019-03-27 05:38:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648005"
1760644,2019-03-27 05:40:00 UTC,https://review.openstack.org/648005 is just a partial fix fixing some missing parameters.
1760644,2019-03-27 05:39:15 UTC,"Sneha: This is an ""epic"" bug, there are lots of fixes that can be made incrementally until we're satisfied we have weeded out the mistakes the OP encountered. Please feel free to submit patches."
1760644,2019-03-29 23:38:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/648796"
1760648,2018-04-02 17:30:20 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760648,2018-04-22 19:15:06 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1006.6
1760648,2018-06-11 15:26:06 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1027.32
1760649,2018-04-22 19:15:06 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1006.6
1760649,2018-04-02 17:30:26 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760649,2018-06-11 15:26:06 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1027.32
1760651,2018-04-02 17:34:47 UTC,"Hold off on this for now.  It's not necessary currently to get the NVDIMM support in, and there's a good chance this build dependency will disappear soon anyway."
1760651,2018-04-02 20:20:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1760661,2018-04-19 19:44:02 UTC,Since this an upstream issue it is waiting for a fix by that team. As always chromium and chrome are regularly updated as soon as new versions are made available.
1760661,2018-04-10 06:24:44 UTC,Please add the links here to those upstream reports. Thanks
1760661,2018-04-19 18:24:47 UTC,I this issue going to be fixed for release?
1760661,2018-04-19 04:10:05 UTC,I have also been having this problem lately. I mostly notice it when I'm scrolling.
1760661,2018-04-10 20:37:50 UTC,Here it is:
1760661,2018-04-10 06:14:47 UTC,Now a Chrome update on UB 7.10 has created the same problem there.  This seems to be a Chrome issue.  I've submitted bug reports to the Chrome and Chromium sites.  Will continue to watch...
1760661,2018-04-03 21:31:43 UTC,"Ok, interesting, it only stopped because I opened the Chrome task window as you suggested.  When the window is open, the pausing stops completely, even if it's minimized.  But if I close the Chrome task window, the pausing comes back!"
1760661,2018-04-05 23:50:10 UTC,"I reinstalled Chromium/Chrome on the new Beta 2 of Ubuntu Budgie 18.04 and the problem persists.  It seems to be a visual pausing only, as audio is fine.  As I mentioned, though, it impacts scrolling as well, though, which is janky.  I've even seen the opening Chromium/Chrome animation pause briefly upon first boot-up, so this is still a thing :(."
1760661,2018-04-06 08:45:34 UTC,Bret - please run apport-collect 1760661 to gather debug info and it will attach to this bug report
1760661,2018-04-03 10:41:29 UTC,So the deb package is also seemingly affected?
1760661,2018-04-03 21:43:46 UTC,That behavior (pausing resolved by having the Chrome Task window open via shift-esc only to have pausing stop when that task window is closed) I verified in Chrome deb and Chromium snap both.
1760661,2018-04-03 19:56:16 UTC,"It happened from the moment after launching the first time in Chromium and Chrome.  Deb and snap both.  After happening for three days, today it stopped and is working fine...  I will reinstall from the Deb and see if that is working now...  Thanks."
1760661,2018-04-05 03:48:49 UTC,"Not the entire browser UI, but the contents freeze for a period of time - videos, scrolling, animations, etc.  If I open the Chrome/Chromium task window, everything is fine."
1760661,2018-04-04 10:33:25 UTC,"Can you elaborate on the symptoms? Is the entire browser UI frozen, or just the chrome/contents? How about other apps when that happen, are they paused too, or still responsive?"
1760661,2018-04-05 17:48:56 UTC,Also had reports on this via our support tracker discourse site. Seems chromium or chrome has this issue. Firefox apparently has no issues in playing videos.
1760667,2018-04-02 22:57:34 UTC,"Ah, thanks for dropping by - I think we met on the forums. Can you post a link to this issue there, if you're the same person?"
1760667,2018-04-03 11:33:56 UTC,"Sure it's done, Hachmann !"
1760667,2018-04-03 11:36:40 UTC,"OOPs, i forgot, this is a diff between ldd on the ""/usr/bin/inkscape"" of each package..."
1760667,2019-06-11 03:19:13 UTC,Assuming fixed on 1.0 as only GTK3 is supported.
1760672,2018-04-24 19:47:19 UTC,"Hi Po-Hsu,
Many (possibly all) of these failures should be fixed as of linux-kvm (4.4.0-1021.26).  I'll mark this as Fix-Released; If there are still any failures left for this test case, please file a new bug."
1760672,2018-04-09 10:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760673,2019-08-29 14:49:03 UTC,"I have the same problem, i.e. very frequent crashes. I can't see a pattern."
1760673,2020-01-03 17:57:52 UTC,"I think this bug is due to a bug in libgtk+2.0, see:
 https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710"
1760675,2021-01-07 08:52:58 UTC,Deprecated tracker.
1760676,2021-01-07 08:52:01 UTC,Deprecated tracker.
1760688,2018-05-05 19:52:56 UTC,I have the same problem in Ubuntu 18.04 LTS with Thunderbird ver. 52.7.0 (64-bit).
1760704,2018-05-05 17:07:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760713,2018-12-10 20:41:57 UTC,Would it be possible to get a backport of this to xenial as well?
1760713,2019-09-04 14:29:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760714,2019-09-04 14:07:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760716,2018-04-12 12:25:08 UTC,The Latitude 5490 of my colleague had Ubuntu 17.10 installed and updated the firmware automatically to 1.1.9 (I assume via fwupd). Now the machine boots to a black screen and all attempts to reinstall the system have failed so far. BIOS downgrade is blocked. Booting to recovery mode still works.
1760719,2020-04-02 16:57:17 UTC,"Fixed to designate this config file.  I also modified the associated directions for using netstat, to instead use ss."
1760719,2018-10-26 16:39:20 UTC,I had the same issue noted above with the instructions. I support this recommended change.
1760722,2018-04-17 11:35:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561911"
1760722,2019-02-26 13:11:54 UTC,Is this still being worked on? and is it still an issue?
1760722,2019-12-03 15:32:15 UTC,"Change abandoned by Lukas Bezdicka (<email address hidden>) on branch: master
Review: https://review.opendev.org/561911
Reason: https://review.opendev.org/#/c/544696/"
1760724,2018-11-17 02:02:39 UTC,"I had the same issue, and posted to the ubuntu forum.
The solution for me was to go to Settings->Configure Konqueror->Performance and uncheck the box ""Always try to have one preloaded instance""."
1760724,2019-02-27 20:25:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760724,2019-02-27 20:32:58 UTC,"Yes, I can confirm that once Konqueror is started - with ""Always try to have one preloaded instance"" enabled - a process (possibly the same one? (didn't check)) does stay around, even after an clicking quit.  This is very annoying, since when shutting down the system (or possibly even when logging out?), it does not seem to respond (quickly enough?) to the (presumed) SIGTERM, and as a result, you get a Crash Report at the next login."
1760731,2018-04-02 23:57:16 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x556378e64e40, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4025
 g_object_ref (_object=_object@entry=0x556378e64e40) at ../../../../gobject/gobject.c:3206
 object_property_maybe_complete (self=0x556378e64e40) at libnm/nm-object.c:452
 init_finish (initable=<optimized out>, result=0x556379ab2710, error=0x0) at libnm/nm-object.c:1159
 obj_nm_inited (object=<optimized out>, result=<optimized out>, user_data=<optimized out>) at libnm/nm-client.c:2236"
1760735,2021-02-17 17:07:13 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1760737,2018-04-04 07:22:41 UTC,From the online chat when we talked about this:
1760737,2018-04-04 22:36:55 UTC,We could add this to the message that lists all the extensions that need to be installed when you install SAML for the first time.
1760755,2018-07-26 16:03:11 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1760755,2018-08-09 01:18:06 UTC,"yes, please."
1760755,2018-08-09 01:19:06 UTC,7/25/18 Currently in Linux-next
1760755,2019-05-07 03:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1760758,2018-04-03 04:21:26 UTC,"In 16.04 och 17.10 ibus-sunpinyin is the default IM for Simplified Chinese through IBus, and ibus-libpinyin just an option available in universe. Setting priority ""Low""."
1760770,2019-09-19 11:57:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1760772,2018-04-05 08:07:54 UTC,Considering the fact that there are multiple and potentially conflicting sources for importing ratings this task can easily get complicated.
1760782,2020-12-15 19:53:00 UTC,"Very old, please reply if it affects you."
1760782,2021-02-14 04:17:28 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1760793,2018-04-03 07:43:29 UTC,"StacktraceTop:
 as_ref_string_unref (rstr=0x33 <error: Cannot access memory at address 0x33>) at ../libappstream-glib/as-ref-string.c:227
 as_node_yaml_destroy_node_cb (node=<optimized out>, data=<optimized out>) at ../libappstream-glib/as-yaml.c:120
 g_node_traverse_pre_order (node=0x5566726a6e90, flags=flags@entry=G_TRAVERSE_ALL, func=func@entry=0x7fc65d1e75a0 <as_node_yaml_destroy_node_cb>, data=data@entry=0x0) at ../../../../glib/gnode.c:547
 g_node_traverse_pre_order (node=<optimized out>, flags=flags@entry=G_TRAVERSE_ALL, func=func@entry=0x7fc65d1e75a0 <as_node_yaml_destroy_node_cb>, data=data@entry=0x0) at ../../../../glib/gnode.c:542
 g_node_traverse_pre_order (node=<optimized out>, flags=flags@entry=G_TRAVERSE_ALL, func=func@entry=0x7fc65d1e75a0 <as_node_yaml_destroy_node_cb>, data=data@entry=0x0) at ../../../../glib/gnode.c:542"
1760797,2020-06-07 09:15:46 UTC,isn't this just https://bugs.launchpad.net/ubuntu/+source/ring/+bug/1723878 ?
1760797,2018-04-03 08:27:19 UTC,"Stacktrace: No stack.
StacktraceSource:"
1760801,2019-03-03 19:37:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760805,2020-03-19 09:02:42 UTC,"Trove is using storyboard for feature/bug tracking, please go to https://storyboard.openstack.org/#!/project_group/trove if issue still exists."
1760805,2018-09-27 10:59:52 UTC,I have this bug too:
1760805,2020-03-08 15:51:34 UTC,"This issue is too long ago! And i have forgot hao i fix it .I just remember that  i have modified some source code ,and it has been running steadily for two years."
1760805,2020-02-17 14:19:50 UTC,I have this issue a swell.
1760810,2018-04-03 09:26:55 UTC,"APT, by design, only picks candidate versions when installing dependencies, and the non-pinned proposed version is not the candidate. apt install foo/target has some logic to switch dependencies to target too, which works sometimes, but it's nothing that happens when using pinning."
1760810,2018-05-19 09:42:32 UTC,"> I'll check, but I think autopkgtest will happily take it.
"
1760810,2018-05-19 09:03:42 UTC,"On 18-05-18 22:23, Julian Andres Klode wrote:

> Oh, you got a working result? I tried aspcud in various variants, but I
> don't get any solutions. https://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=897330
"
1760810,2018-05-18 20:23:33 UTC,"Oh, you got a working result? I tried aspcud in various variants, but I don't get any solutions. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897330"
1760810,2018-06-03 19:43:37 UTC,Please give feedback on my proposed implementation in autopkgtest. It also adds support for submission of versioned packages that need to come from -proposed.
1760810,2018-04-21 20:14:18 UTC,After discussion on IRC (#debian-devel) I filed Debian bug 896506¹ about this failing command.
1760810,2018-04-20 20:00:31 UTC,"@juliank: I tried your command (with --simulate) on my own laptop and with this option it says that gnome can't be installed, while plain apt will happily install it."
1760810,2018-04-03 10:43:59 UTC,sbuild passes:
1760810,2018-04-03 10:11:20 UTC,"On Tue, Apr 03, 2018 at 09:26:55AM -0000, Julian Andres Klode wrote:

> APT, by design, only picks candidate versions when installing
> dependencies, and the non-pinned proposed version is not the candidate.
> apt install foo/target has some logic to switch dependencies to target
> too, which works sometimes, but it's nothing that happens when using
> pinning.
"
1760810,2018-05-18 20:04:29 UTC,"Hmm, maybe it was just the syntax being wrong. The following line at least succeeded:"
1760818,2019-09-27 06:53:15 UTC,"I installed Lubuntu 18.04 LTS on VirtualBox, and I met similar issue. The text messages on gajim chat window were messy. GTK didn't seem to refresh the window and kept previous text overlapped on the window."
1760818,2019-02-09 16:24:06 UTC,Same issue since I switched from ibus to xim on Ubuntu 18.04.
1760818,2019-03-15 05:39:40 UTC,I confirm what Jarrod Farrell (jarrodmaddy)wrote. I have to chose between having the non-working gedit/calculatir or being unable to type passwords in Firefox.
1760818,2019-03-15 09:53:27 UTC,"The Adwaita theme was helped to me, switching the input method was not."
1760818,2019-03-22 01:07:57 UTC,"I have upgraded through several versions of Ubuntu up to 18.04.2, and I've tried all suggestions, but still getting screen overwriting in Meld to the point of making it unusable."
1760818,2019-06-21 04:54:55 UTC,I am running Ubunti 18.04.2 in an Enhanced Hyper-V session - https://www.zdnet.com/article/windows-10-tip-run-ubuntu-linux-in-an-enhanced-hyper-v-session/.
1760818,2019-09-28 15:40:03 UTC,"I'm wondering why this has not been fixed after such a long time. It can at least be improved easily.
If the Adwaita theme works (which it does in may case, too), then it is (at least partly) a theme issue.
In fact, some defaults seem to be missing in the Ambiance and Radiance themes:"
1760818,2020-05-16 23:02:20 UTC,The im-config impact on this issue should be fixed via this upload:
1760818,2019-12-22 20:31:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760818,2020-01-11 18:04:50 UTC,"I have just been hit with this on a new install of 18.04 from a CD I had to do because of a hard drive change and full restore.  Initially text editor worked well, but one of the applications I added, or a software update, seems to have caused the transparency.  The workaround suggested by Heiko L is impossible for me to implement as my text editor/gedit has a transparent background and I cannot see what I am doing."
1760818,2020-01-11 18:07:35 UTC,Further to my last comment I suspect Gramps or one of its add-ons as the cause based on timing of when the error began.
1760818,2020-04-21 08:56:00 UTC,"Happened to gnome-calculator on my laptop. Didn't notice any problem with gedit. Renamed ~/.xinputrc, logout/login, problem solved. This laptop started with 10.04LTS and has upgraded through all LTS versions to 18.04LTS. I use gnome-flashback metacity by default..."
1760818,2020-10-15 08:00:19 UTC,I solved the problem changing the gnome theme to Adwaita using gnome tweaks.
1760818,2018-11-20 13:20:04 UTC,"Since I upgraded from to 18.04 I've had this problem (actually gnome apps) : Main windows unusable with weird main window.
Changing from the theme (Ambiance) to any other theme (Adwaita, Numix, etc) solved the problem.
(I'm using gnome shell)"
1760818,2019-10-11 16:27:47 UTC,"I'm able to reproduce the faulty on bionic (not upgraded from xenial), with GTK_IM_MODULE=xim and an empty .xinputrc."
1760818,2018-11-10 21:29:44 UTC,"Are you all on gnome-shell? I have the same transparency issue in gnome-session-flashback / lightdm, but only when using theme Ambiance. I moved to theme Adwaita and the transparency issues are gone."
1760818,2018-04-30 12:45:19 UTC,"Seems reinstalling ubuntu-desktop fixed it for real, ibus is now in GTK_IM_MODULE for new users."
1760818,2018-09-18 13:14:09 UTC,Having the issue over here on 18.04.1 and as mentioned it seems to be focused on what input method system you choose. For me I can't switch over to ibus (without downgrading) without summoning the wrath of bug #1765304.
1760818,2018-04-20 06:55:09 UTC,"I can, on my old account upgraded from xenial, but not on my laptop which was installed with bionic"
1760818,2018-04-20 07:08:08 UTC,"the issue sounds similar to bug #1620806, do you have a ~/.xinputrc? does deleting it fixes the issue?"
1760818,2018-04-20 08:06:15 UTC,"I did, but logout/login didn't seem to fix the issue. Maybe gdm should've been restarted as well?"
1760818,2018-04-20 10:40:56 UTC,"It didn't help here either, I've deleted it back when I filed this bug originally."
1760818,2018-04-23 01:39:34 UTC,Sounds like some config setting inherited from upgrades is triggering this.
1760818,2018-04-30 12:11:43 UTC,"Some data points:
- I did not have .xinputrc
- still, GTK_IM_MODULE=xim in my sessions was set
- it seems im-config is responsible, selecting a different value via the Languages panel or im-config doesn't change anything
- removing im-config fixes this, but also removes ubuntu-desktop (it's a direct dependency)
- bringing im-config back makes it go bad again
- seems to be a per-user thing as one of my users now does not have the issue, new users do
- the following scripts seem to be involved:
  /etc/X11/Xsession.d/70im-config_launch
  /etc/profile.d/input-method-config.sh"
1760818,2018-11-10 21:21:40 UTC,"Are you all on gnome-shell? I have the same transparency issue in gnome-session-flashback / lightdm, but only when using theme Ambiance. I moved to theme Adwaita and the transparency issues are gone."
1760818,2018-04-30 12:46:16 UTC,"So a workaround that worked for me:
$ apt-get purge im-config # removes ubuntu-desktop as well
$ apt-get install ubuntu-desktop # installs im-config along with anything that fixes it..."
1760818,2018-04-03 10:04:15 UTC,I can't reproduce this on 18.04... can anyone else?
1760818,2018-05-01 07:55:43 UTC,It's another instance of bug #1620806 - just triggered differently.
1760818,2018-05-01 15:02:38 UTC,"To the extent this issue is caused by im-config setting GTK_IM_MODULE=xim, it ought to be a leftover from ~/.xinputrc files created in 16.04. Since the fix of bug #1605408, nothing should set GTK_IM_MODULE=xim automatically."
1760818,2018-05-01 15:32:55 UTC,"Second thoughts.. im-config does fall back to GTK_IM_MODULE=xim under certain conditions. The code is in the file
/usr/share/im-config/data/21_ibus.rc"
1760818,2018-05-02 07:16:51 UTC,"Right, looks like I was missing ibus-gtk then - reinstalling ubuntu-desktop brought it back."
1760818,2018-05-02 21:28:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760818,2018-08-16 22:00:10 UTC,I experienced this bug today. Restart didn't help initially. Then I changed the Input Method from xim to ibus and the problem was gone. Changing back to xim did not bring the problem back. I'm confused that it worked. Would be nice if somebody else could try the same.
1760818,2018-08-19 18:09:29 UTC,"Following-up on my previous comment, the problem did come back, even though it was gone at first after I switched to ibus and then back to xim. Now I switched to ibus and restarted, the problem is gone. So I'm not switching back to xim, as I suspect the problem would reappear again then."
1760818,2018-05-01 07:24:43 UTC,Added an im-config task but I don't know how that could trigger graphical problems.
1760820,2018-04-19 12:11:53 UTC,"@Tim, is this going into 2.4.beta1?"
1760826,2019-11-10 04:17:30 UTC,[Expired for python-novaclient because there has been no activity for 60 days.]
1760826,2018-06-17 04:17:28 UTC,[Expired for python-novaclient because there has been no activity for 60 days.]
1760826,2019-09-10 08:00:49 UTC,"This bug has been open for about a year without any activity.
I'm going to move it to ""Incomplete"".
This bug can be reopened (set back to ""New"") if someone decides to work on this."
1760826,2018-04-17 11:28:33 UTC,"@Augustin, Thank you.
But I could not find the cause."
1760826,2018-04-05 07:10:37 UTC,"Sure, i have replaced some values with <...> (username, ip addresses, domain, auth token, ...):"
1760826,2018-04-05 00:43:07 UTC,Could you attach the output of the command with '--debug' option?
1760826,2018-04-17 14:07:30 UTC,Thanks for your reply.
1760827,2018-04-03 11:04:26 UTC,"The patch #1 is naive because it is doing some work already done in %CONDITION-WAIT and because it may not be solving some on all levels. For example, the FIXME in %WAIT-FOR-MUTEX could probably lead to a similar issue."
1760840,2018-04-03 11:45:41 UTC,bug affects on ubuntu 14.04.x that contains old npm version
1760840,2018-04-03 11:47:17 UTC,"contains patch for rhel version, it might work with ubuntu :)"
1760840,2018-04-03 11:48:34 UTC,npm ca update patch for rhel. it might work on ubuntu too
1760840,2018-04-03 11:50:29 UTC,/usr/share/npm/node_modules/npmconf/config-defs.js contains code that need to be updated.
1760840,2018-04-03 12:24:23 UTC,"The attachment ""attachment.cgi?id=1416573"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1760840,2018-07-22 22:06:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760848,2020-03-26 03:18:06 UTC,We're now using distrobuilder to build pre-made images avoiding the mess that was those scripts.
1760848,2018-06-11 11:21:24 UTC,"Oliver, this bug is exactly about creating a bionic container on an ubuntu 16.04 host."
1760848,2018-04-26 08:56:53 UTC,"In my case the underlying host is an ubuntu 16.04. I don't know, if that can cause trouble?"
1760848,2018-04-26 08:16:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760848,2018-06-11 11:55:11 UTC,This is fixed in lxc 2.1.1 which is available via ppa for 14.04 but has to be pushed to xenial updates.
1760849,2019-03-16 21:55:22 UTC,WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + numlockx(optionally)
1760849,2020-09-17 08:36:03 UTC,Hello!
1760849,2020-07-20 16:18:15 UTC,"same issue here, on Ubuntu 20.04(Focal)"
1760849,2020-07-17 17:12:01 UTC,"This still happens on Ubuntu 20.04 (Focal), too. In my case, I have one external monitor which is mirrored. But the login screen appears only on the laptop's screen but not on the external monitor's display."
1760849,2019-07-18 13:11:01 UTC,"In addition, for me, install lightdm solve the problem. Now, I can see login screen on both monitors :)"
1760849,2019-07-18 13:05:04 UTC,Are there some solution for it?
1760849,2019-03-06 08:27:47 UTC,I agree mirroring login screen to all displays is the ideal default behavior.
1760849,2018-04-04 02:09:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1723025, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1760849,2019-01-05 19:43:00 UTC,"I switched to lightdm but the problem still exists: if I attach an external monitor to my laptop, no login screen appears, nevertheless, I can enter my credentials blind, and than everything's fine.
If I boot with nomodeset than at least the login is ok. I've got a dell laptop with integrated intel video."
1760849,2019-03-06 08:26:03 UTC,I have exactly the same issue. This is really annoying bug.
1760849,2018-04-04 03:57:04 UTC,"It's a different project that implemented ""login controls followed the mouse""."
1760849,2018-04-04 11:42:12 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=794971
1760849,2018-04-04 03:41:24 UTC,"I don't think this is a dupe of Bug #1723025, which is discussing behavior when a screen is disabled such as a laptop being closed while an external monitor is connected. In my case, the laptop screen is not disabled (the laptop is not designed to operate with the lid closed). The laptop screen simply cannot be seen when using the external monitor and keyboard due to its physical positioning."
1760849,2018-12-21 01:40:24 UTC,Reworded the bug title because I keep finding duplicates of this issue and it's hard to direct people here while the bug title only describes one possible solution instead of describing the problem. Other people have requested other solutions like honoring their account's own primary monitor preference as a global setting.
1760849,2018-12-21 01:42:29 UTC,"That said, I personally agree that mirroring the login screen on all monitors would be best."
1760849,2018-05-25 12:13:09 UTC,Upstream issue shuffled to to https://gitlab.gnome.org/GNOME/gdm/issues/372
1760853,2020-04-19 19:45:38 UTC,"Change abandoned by Bharat Kunwar (<email address hidden>) on branch: master
Review: https://review.opendev.org/558497"
1760861,2018-07-12 19:40:16 UTC,2018-07-12 VictorWestmann - +1 for this. Really useful enhancement.
1760861,2020-04-23 14:36:54 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1760866,2018-04-03 14:11:12 UTC,"StacktraceTop:
 save_thumbnail_in_cache_thread (task=0x5650d9322bb0, ev_recent_view=0x0, data=0x5650d9608f80, cancellable=<optimized out>) at ev-recent-view.c:350
 g_task_thread_pool_thread (thread_data=0x5650d9322bb0, pool_data=<optimized out>) at ../../../../gio/gtask.c:1331
 g_thread_pool_thread_proxy (data=<optimized out>) at ../../../../glib/gthreadpool.c:307
 g_thread_proxy (data=0x5650d9732230) at ../../../../glib/gthread.c:784
 start_thread (arg=0x7f24b5b97700) at pthread_create.c:463"
1760866,2020-08-31 04:17:25 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1760866,2020-07-01 21:00:09 UTC,Thank you for your bug report. Is that still an issue? Does it happen on a specific document? If so could you attach it there?
1760874,2018-04-03 14:29:06 UTC,"StacktraceTop:
 g_realloc (mem=<optimized out>, n_bytes=2147483648) at ../../../../glib/gmem.c:169
 g_array_maybe_expand (array=0x7f5ba0c0c200, len=<optimized out>) at ../../../../glib/garray.c:794
 g_array_set_size (farray=farray@entry=0x7f5ba0c0c200, length=1844592832) at ../../../../glib/garray.c:570
 g_byte_array_set_size (array=0x7f5ba0c0c200, length=<optimized out>) at ../../../../glib/garray.c:1847
 read_cb (socket=0x7f5b9ce37bb0, condition=<optimized out>, client=0x7f5ba05cd060) at snapd-client.c:566"
1760879,2018-04-03 18:18:07 UTC,"After adding serial numbers, I can confirm that the deployment works."
1760879,2019-09-19 12:05:20 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1760879,2018-06-28 13:35:19 UTC,"i push e, and change /efi/ubuntu/grubx64.efi ->  /efi/centos/grubx64.efi, press F10, it can boot,"
1760879,2018-06-28 13:29:37 UTC,"2.4.0beta2,  i got same error, when i deploy centos7 in uefi model."
1760879,2018-06-01 14:02:26 UTC,"This bug is believed to be fixed in curtin in version18.1-17-gae48e86f-0ubuntu1. If this is still a problem for you, please make a comment and set the state back to New"
1760879,2018-04-19 15:26:11 UTC,An upstream commit landed for this bug.
1760879,2018-04-03 18:07:49 UTC,"As per the collect logs, on an ephemeral node, you can find curtin here:"
1760879,2018-04-03 17:26:20 UTC,"This is what I have in /dev/disk:
ubuntu@46-f4:~$ sudo su -
root@46-f4:~# ls -la /dev/disk
total 0
drwxr-xr-x  4 root root   80 Apr  3 17:25 .
drwxr-xr-x 17 root root 3600 Apr  3 17:25 ..
drwxr-xr-x  2 root root   60 Apr  3 17:25 by-partuuid
drwxr-xr-x  2 root root  160 Apr  3 17:25 by-path
root@46-f4:~# ls -la /dev/disk/by-partuuid/
total 0
drwxr-xr-x 2 root root 60 Apr  3 17:25 .
drwxr-xr-x 4 root root 80 Apr  3 17:25 ..
lrwxrwxrwx 1 root root 10 Apr  3 17:25 9ef12100-01 -> ../../vda1
root@46-f4:~# ls -la /dev/disk/by-path/
total 0
drwxr-xr-x 2 root root 160 Apr  3 17:25 .
drwxr-xr-x 4 root root  80 Apr  3 17:25 ..
lrwxrwxrwx 1 root root   9 Apr  3 17:25 pci-0000:00:06.0 -> ../../vda
lrwxrwxrwx 1 root root  10 Apr  3 17:25 pci-0000:00:06.0-part1 -> ../../vda1
lrwxrwxrwx 1 root root   9 Apr  3 17:25 pci-0000:00:08.0 -> ../../vdb
lrwxrwxrwx 1 root root   9 Apr  3 17:25 virtio-pci-0000:00:06.0 -> ../../vda
lrwxrwxrwx 1 root root  10 Apr  3 17:25 virtio-pci-0000:00:06.0-part1 -> ../../vda1
lrwxrwxrwx 1 root root   9 Apr  3 17:25 virtio-pci-0000:00:08.0 -> ../../vdb"
1760879,2018-04-03 17:23:14 UTC,This is what I managed to grab by ssh'ing in and tailing /var/log/cloud-init*
1760879,2018-04-03 17:17:54 UTC,"having a hard time doing that
ubuntu@46-f4:~$ sudo su -
root@46-f4:~# curtin collect-logs"
1760879,2018-04-03 16:24:58 UTC,"I think curtin can help here, but zfsroot requires GPT partitions, this is msdos."
1760879,2018-04-03 15:06:36 UTC,"So as per agreed with the server team, passing zfsroot as a filesystem should allow it to work exactly the same was as any normal filesystem would."
1760879,2018-04-03 15:01:56 UTC,This is how storage was like when I hit deploy.
1760879,2018-04-03 14:43:01 UTC,"Hey Andreas,"
1760879,2018-04-03 18:06:20 UTC,"OK,"
1760880,2019-09-19 11:57:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1760880,2018-06-01 14:02:28 UTC,"This bug is believed to be fixed in curtin in version18.1-17-gae48e86f-0ubuntu1. If this is still a problem for you, please make a comment and set the state back to New"
1760880,2018-04-19 15:26:08 UTC,An upstream commit landed for this bug.
1760880,2018-04-03 16:31:35 UTC,"I think we can update the format command documentation around zfsroot to indicate that there can be only one zfsroot, like there can be only one '/' mount."
1760880,2018-04-03 16:29:17 UTC,"zfsroot only accepts a single partition/device, that is we look at where '/' is mounted and use the underlying device (partition or disk) to construct the zpool/zfs commands as needed."
1760880,2018-04-03 15:09:01 UTC,"I think this could also be related to [1]. That said, it could be ok to have a partitioning be formatted but not mounted, but yet, this fails on zfsroot, which leads me to believe this may be an issue with curtin."
1760880,2018-04-03 14:53:20 UTC,"This is the state the storage screen was when I clicked ""deploy""."
1760880,2018-04-03 14:52:55 UTC,Attached
1760880,2018-04-03 14:24:55 UTC,"Hey Andreas,"
1760881,2018-04-03 15:02:28 UTC,"Jason, it seems like this bug would also resolve much of bug https://bugs.launchpad.net/evergreen/+bug/1573666."
1760887,2018-04-03 18:47:34 UTC,"Sounds like dup of #1722121, fixed in Bionic."
1760887,2018-04-04 00:28:35 UTC,"Could be a dup indeed, wouldn't be surprised. What's Bionic? How can I get it?"
1760893,2019-05-24 21:30:58 UTC,"Based on mutual assent of those weighing in, I have pushed this in as offered by Dan P.  Thanks, Dan!"
1760893,2018-07-25 13:22:25 UTC,"I didn't register a vote before, but I prefer the reverse sort as well.  It is initially unexpected, but pays dividends in the long run, which (IMO) ultimately matters more.  People are very likely to add things in order, and it's very convenient for the one most recently added to be at the top of the selector."
1760893,2018-07-25 03:06:48 UTC,"Dan's fix work, but Dan W. raises a good question. I expected the sort to be in ascending order, which is how it was done in the xul client. But the fix sorts the parts in descending order. What do others think? It should be easy enough to tweak to sort descending if we want to replicate the previous behavior from the xul client."
1760893,2018-04-10 21:13:51 UTC,"I think we do need *some* sort here, and Dan's fix seems like a good option.  Perhaps the biggest question is whether it sorts forward or in reverse, with notable benefits either way."
1760893,2018-07-25 12:00:44 UTC,"When adding parts to a volume, I think descending would be better. We use parts for both multi-disc dvd/cd sets and periodicals.  Although we have a lot more discs than periodicals, the periodicals have  far longer parts lists."
1760893,2018-04-10 20:54:36 UTC,"Jason, I still think there is a bug here since the part selector isn't following the default alpha order."
1760893,2018-04-10 20:39:42 UTC,Setting this bug to Invalid because it concerns a local customization at CW MARS.
1760893,2018-04-10 18:52:52 UTC,Works for me in Concerto.
1760893,2018-04-10 15:06:40 UTC,"The XUL client at C/W MARS has been customized to list parts in reverse label_sortkey order. For dates, this means the most recent will be at the top of the list."
1760893,2018-04-03 15:59:03 UTC,Sorry! CW MARS has custom code to do the chronological sort.  Default Evergreen sort is alphabetical.
1760893,2018-04-10 21:03:14 UTC,"Kathy, you can always change the status if you think I got it wrong. I just want people to know that Dan's code is how we want it sorted at CW MARS and is not written for the community."
1760897,2018-04-24 09:45:25 UTC,you can add `build-attributes: [no-patchelf]` to avoid the patching to adapt the binary to work correctly across multiple distributions.
1760907,2019-01-12 15:18:44 UTC,"Ubuntu and derivatives from version 18.04 is only compatible with version 8.2 of Netbeans, so I solved this problem."
1760907,2018-07-21 02:10:12 UTC,Those packages only have 3/(48 and 21) files in common.
1760907,2018-06-22 20:18:55 UTC,This is going to sound like a strange fix but I've had it work on 2 systems:
1760907,2018-06-14 03:37:59 UTC,Upstream bug report: https://issues.apache.org/jira/browse/NETBEANS-756?jql=project%20%3D%20NETBEANS%20AND%20text%20~%20crash
1760907,2018-06-14 03:46:11 UTC,"Re comment 2, I believe there are two bugs here, but this is the important one. People are seeing a crash accompanied by a warning about a Java 9 deprecation, and assuming they're connected, and thus are reporting the Java 9 deprecation (#1763091). However, the crash occurs even without the use of Java 9 (this bug), and in an identical way regardless of which version of Java is used."
1760907,2018-06-14 03:22:09 UTC,"I've been looking into this bug myself (Launchpad's duplicate finder isn't suggesting this bug as a duplicate target so it's been reported several times by many people, including me). My findings are summarised in #1776724."
1760907,2018-05-07 14:03:48 UTC,"same issue fetching after upgrade new ubuntu version. netbeans crash in Turning on modules, in the splash screen."
1760907,2018-05-05 17:38:41 UTC,It crashes even after fresh installation of Ubuntu 18.04 and afterwards netbeans installation with
1760907,2018-04-12 16:55:49 UTC,"My netbeans crash in Turning on modules, in the splash screen."
1760907,2018-04-11 23:28:36 UTC,"No, I'm already using java 8 and I uninstalled open-jdk9 and 8, but netbeans is just the splash screen"
1760907,2018-04-11 16:51:22 UTC,"Is this the same as LP: #1763091 ? If so, I will dupe it (as I'm hoping to resolve that today)."
1760907,2018-06-14 03:23:26 UTC,"Although the original bug report was incomplete, there's more complete information at the duplicates."
1760909,2018-04-03 16:16:02 UTC,When installing packages with a wildcard like this you are going to run into conflicts with different tools packages that were made for different kernels. You should pick the tools package that matches your kernel stream.
1760909,2018-04-03 16:17:04 UTC,"Also, linux-azure-edge will change to 4.15 soon and this conflict is likely to go away then. It is not guaranteed that azure and azure-edge won't have the same kernel at the same time."
1760910,2020-01-22 02:26:18 UTC,"I'm on Parrot OS which is a rolling release of debian, this bug also affects me, I'm using XFCE."
1760910,2019-10-16 20:50:14 UTC,I've seen this problem in every recent Xubuntu release (17.10--19.04).
1760910,2019-09-17 19:51:06 UTC,"I Found a App called ""Eddy"" in app Store and it works fine to me.It can install .deb file Easily"
1760910,2019-05-12 22:39:58 UTC,"A bit of a work around that worked for me is in the gdebi.desktop file where it says ""Terminal=false"" change it to ""Terminal=true"" minus the quotes of course. A ""terminal window""(sort of) pops up behind the gdebi window and allows you to install, reinstall ect. Don't know but it installs packages for me in this way. A bit easier this way than pointing to the package you want to install through the terminal. Kind of works normal this way."
1760910,2019-01-25 10:18:57 UTC,"SUP, there is any information, how soon this bug will be fixed?
it's strange when u want install deb package from GUI but u NEED to open a terminal and start gdebi-gtk from CONSOLE to make it work properly with GUI. =/"
1760910,2018-07-25 00:30:40 UTC,"This new ""admin: //"" method did not work being changed in desktop entry.
The bug still remains in gdebi-gtk."
1760910,2018-05-28 05:48:30 UTC,"I found a solution.  Installed package "" lxqt-sudo "" using synaptic and changed the exec line in gdebi.desktop to "" Exec=lxqt-sudo gdebi-gtk %f "" and now gdebi works ok.  Is it safe in general to use lxqt-sudo for graphical applications in Xubuntu 18.04?"
1760910,2018-07-22 02:55:26 UTC,"In researches in forums, the change that affects the gdebi was the discontinuation of the gksu package. They are currently using the admin: // command from the gvfs package. How can I use it to solve this problem?"
1760910,2018-05-18 12:25:15 UTC,"Let me know if this is a different bug and I will file another report, but I think that it's the same."
1760910,2018-05-27 23:59:37 UTC,"Same problem here, using Xubuntu 18.04. (Clean install, not upgrade)  If I click on a .deb file and choose ""open with gdebi"", the gui opens and checks for depencies, but when ""install"" is clicked the gui disappears (crashes).  But if I open gdebi via terminal, it works fine."
1760910,2018-04-08 14:06:14 UTC,"What is happening is that I can run or run gdebi normally through the terminal or right-click and install the deb package with gdebi and it runs gdebi normally, but when I click install package gdebi closes.It is a bug other than bug 1756238.  ."
1760910,2018-04-08 14:16:55 UTC,"Yes, I was able to install the deb package by running the gdebi-gtk package in terminal mode using sudo. But it would not be a good procedure for a beginner, since gdebi was made for this, install deb packages and dependencies in graphical mode."
1760910,2018-04-08 20:34:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760910,2018-04-08 09:08:04 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1760910,2018-04-09 02:00:26 UTC,"I tried putting this command on the launcher inside the /usr/share/applications/gdebi.desktop folder, but it did not work."
1760910,2018-04-09 12:03:00 UTC,Run:
1760910,2018-04-09 14:14:59 UTC,"It worked, thank you very much."
1760910,2018-04-08 20:39:53 UTC,"If you edit the:-
/usr/share/applications/gdebi.desktop
launchers 'Exec' line to:-"
1760918,2018-05-07 15:08:37 UTC,"Hello Seyeong, or anyone else affected,"
1760918,2018-05-07 16:26:05 UTC,"Hello Seyeong, or anyone else affected,"
1760918,2018-05-08 13:17:16 UTC,This issue was fixed in the openstack/oslo.versionedobjects 1.31.3 release.
1760918,2018-05-08 13:17:24 UTC,This issue was fixed in the openstack/oslo.versionedobjects 1.26.2 release.
1760918,2018-05-09 11:30:47 UTC,for artful
1760918,2018-05-10 09:40:00 UTC,for pike
1760918,2018-05-14 08:26:56 UTC,"The verification of the Stable Release Update for python-oslo.versionedobjects has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1760918,2018-05-14 12:15:34 UTC,The verification of the Stable Release Update for python-oslo.versionedobjects has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1760918,2018-05-14 12:15:36 UTC,"This bug was fixed in the package python-oslo.versionedobjects - 1.26.0-0ubuntu2~cloud0
---------------"
1760918,2018-04-17 13:20:43 UTC,"I've re-uploaded this for bionic (queens), artful (pike), and ocata along with the fix for LP: #1763179. Bionic and Artful are awaiting SRU team review."
1760918,2018-05-21 04:54:09 UTC,"@corey
we can do this sru for xenial and mitaka as well?"
1760918,2018-05-30 14:27:48 UTC,"To be clear, this patch wasn't completely reverted. Rather, LP:1763179 was fixed on top of this patch. Nonetheless, since nothing's been uploaded yet for xenial/mitaka, let's plan on just fixing this via a single bug in LP:1763179."
1760918,2018-05-31 13:19:53 UTC,"got it,"
1760918,2018-05-14 08:26:50 UTC,This bug was fixed in the package python-oslo.versionedobjects - 1.26.0-0ubuntu2
1760918,2018-04-17 13:06:20 UTC,I'm not sure why pike was marked as fix committed. Moved back to Triaged as nothing was uploaded to the UCA for pike.
1760918,2018-05-30 14:20:41 UTC,"Hi Seoyeong, since this patch was reverted in favor of https://bugs.launchpad.net/oslo.versionedobjects/+bug/1763179, and never uploaded for Xenial/Mitaka, can we just fix this via LP#1763179? Marking as Won't Fix for xenial/mitaka for now."
1760918,2018-04-16 00:08:57 UTC,"corey, sil2100"
1760918,2018-04-17 12:40:59 UTC,This is being reverted via https://bugs.launchpad.net/cloud-archive/+bug/1763179.
1760918,2018-04-08 03:24:27 UTC,"Reviewed:  https://review.openstack.org/557778
Committed: https://git.openstack.org/cgit/openstack/oslo.versionedobjects/commit/?id=b1d0b5d886afef8c08330bf3c2291e180aa1f534
Submitter: Zuul
Branch:    master"
1760918,2018-04-09 08:21:47 UTC,"The attachment ""lp1760918_xenial.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1760918,2018-04-09 18:53:48 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/559815"
1760918,2018-04-09 19:22:11 UTC,"Hi Seyeong,"
1760918,2018-04-09 21:52:34 UTC,This bug was fixed in the package python-oslo.versionedobjects - 1.31.2-0ubuntu2
1760918,2018-04-10 11:34:09 UTC,"Hello Seyeong, or anyone else affected,"
1760918,2018-04-10 11:37:34 UTC,"Hello Seyeong, or anyone else affected,"
1760918,2018-04-09 20:31:09 UTC,"I've uploaded this for all affected releases. Most are awaiting review by the SRU team.
Note that I updated the ocata patch to add ""# -*- coding: utf-8 -*-"" to test_fields.py"
1760918,2018-04-11 09:47:53 UTC,This issue was fixed in the openstack/oslo.versionedobjects 1.33.0 release.
1760918,2018-04-11 10:47:33 UTC,"Reviewed:  https://review.openstack.org/559820
Committed: https://git.openstack.org/cgit/openstack/oslo.versionedobjects/commit/?id=5931129fc998f0ef48f39b0c6e84faa564670f1d
Submitter: Zuul
Branch:    stable/pike"
1760918,2018-04-11 10:47:43 UTC,"Reviewed:  https://review.openstack.org/559815
Committed: https://git.openstack.org/cgit/openstack/oslo.versionedobjects/commit/?id=e918eb976fb5a6f9fa7b7644d5a10d383fcfcf21
Submitter: Zuul
Branch:    stable/queens"
1760918,2018-04-11 14:58:25 UTC,"Seyeong, If I understand correctly, you're saying this patch isn't required on any release other than mitaka, however it doesn't break the other releases. Is that correct? The patch has already landed upstream in master (rocky), stable/queens, and stable/pike. If it doesn't regress those releases then I don't think it's worth reverting upstream. As for the SRU for those releases, we don't need to make the extra effort to SRU it. Please confirm before we move ahead. Thanks."
1760918,2018-04-11 21:01:53 UTC,This fix was not correct and will need to be backported again.
1760918,2018-04-12 09:14:15 UTC,Does comment #21 mean that the fix is introducing regressions? Should I reject the current python-oslo.versionedobjects from the artful and xenial queues?
1760918,2018-04-12 12:03:48 UTC,"Lukasz, yes please reject and we'll get the new fix backported. Thanks Sean."
1760918,2018-04-11 04:28:24 UTC,Hello Corey
1760920,2018-04-17 16:44:29 UTC,"This list of 1001 source packages has 284 other source packages as reverse-dependencies in the archive.  Of these, the ones that are seeded are:
 - asciidoc
 - erlang
 - evolution-data-server
 - hsqldb1.8.0
 - libbluray
 - libreoffice
 - openjdk itself
 - openjpeg2
 - publican
 - ust
 - sheepdog"
1760920,2018-04-06 21:06:01 UTC,"On Fri, Apr 06, 2018 at 11:29:44AM -0000, Tiago Stürmer Daitx wrote:

> Other packages that have (or could have been) affected during the
> migration due to their deps or b-deps and thus might be of interest are:
"
1760920,2018-04-06 03:24:22 UTC,"Of those 1123 packages 996 are in Ubuntu, all of them also in Bionic. The attached file is contains the output of rmadison for all of them - it amounts to 1001 packages because a few are also in bionic-proposed."
1760920,2018-04-05 19:27:23 UTC,"Please provide the list of source packages here in the bug, without reference to the third-party (debian.org) website."
1760920,2018-04-06 11:29:44 UTC,Other packages that have (or could have been) affected during the migration due to their deps or b-deps and thus might be of interest are:
1760929,2018-06-16 19:48:10 UTC,"What monitor resolution are you using? Also, what's your DPI density set to, Auto-Detect or Regular?"
1760929,2018-07-25 05:34:28 UTC,"Thanks Victor. The resolution is 2560x1600 and it shows as 192dpi.  I tinkered with it some and found that if I change from Auto detect to hidpi, the issue goes away entirely.  I think you are right in that it is not auto detecting correctly."
1760929,2018-07-27 19:31:30 UTC,"Additional information.  The problem was less severe when set to hidpi instead of auto detect, but was still there.  I was using compiz for a window manager.  After switching to Marco with compton compositor, it has gone away entirely.  It is still set to hidpi instead of auto.  Fixed a tearing issue with Marco configuration that kept me using compiz and not planning to go back now."
1760940,2019-04-17 15:28:24 UTC,Sign-off for Jane's branch pushed:
1760940,2018-04-06 14:37:05 UTC,"I don’t use the text editor very often since I do most of my editing in OCLC and overlay into EG. The few times I do use text (and flat) is when it’s punctuation or typo, and it takes longer to overlay into my ILS, so I’ll just fix it in OCLC and then fix it in the text editor. The only time it would be helpful is if I was scanning for typos, but then again, it is a lot of red if it’s catching all the delimiters & etc. I like the toggle option."
1760940,2018-04-04 21:53:37 UTC,If the MARC workform had spell-check I'd find it useful. I also prefer the workform to the flat-text editor as it's easier to read. If it has to be available in both then I'd like a toggle for off/on and the granularity of turning it off for the fixed fields and linked fields.
1760940,2018-04-04 16:18:56 UTC,"I have no issue with it being turned off, that being said it is easy for me to ignore when modifying records. My coworker made the comment that it is useful for catching spelling errors when typing descriptions in records. I am seeking opinions from other catalogers in my consortium and will pass along their comments."
1760940,2018-04-04 19:27:55 UTC,"From our Technical Services Coordinator: Having it turn off for specific MARC fields would be nice, there are some that would always look misspelled.  The fields I'm mostly interested in spellchecking are 245, 500, 520, and 650's.  Names are so hard, I don't know if spellchecking that would be helpful.  The regular MARC editor would easier to spot misspellings in."
1760940,2018-04-04 15:44:51 UTC,"If it would only be turned off for the flat text editor, I see no reason not to turn it off, since it's so annoying and almost worthless for that function."
1760940,2018-04-04 16:00:01 UTC,I would like the granularity of default off for the FF and for linked fields. The ability to toggle it on and off would also be helpful.
1760940,2018-04-03 18:02:53 UTC,"Personally, I only use the flat text editor if I am copying and pasting into a record and not when I am checking a record for errors. I see problems better in the default editor. So it doesn't matter either way to me."
1760940,2018-04-04 11:35:13 UTC,It might be a good idea to send a message to the cataloging list to see if we can get more feedback from catalogers.
1760940,2018-04-04 15:41:12 UTC,"This may be ultimately better spun off into a separate bug, but the browser spellchecker is active in the non-flat-text editor. Do folks have a preference about that as well?  I could also envision more granularity, as it would be possible in the default editor to do things like that:"
1760940,2018-04-03 23:32:43 UTC,I spoke with a colleague who uses the flat text editor extensively while cataloging.  Her strong preference is to turn off spellchecking for that box.
1760949,2018-05-10 11:29:42 UTC,"It needs to run in the charm venv, use a hashbang:"
1760949,2019-11-29 15:34:08 UTC,"Reviewed:  https://review.opendev.org/693567
Committed: https://git.openstack.org/cgit/openstack/charm-tempest/commit/?id=1e546550f2298dabda091f753ecb710b84f5a341
Submitter: Zuul
Branch:    master"
1760955,2018-05-08 20:34:41 UTC,"Created attachment 7720
Xfce Indicator Plugin settings 1. Rightmost envelope is from indicator plugin"
1760955,2018-05-08 20:35:31 UTC,"Created attachment 7721
Xfce Indicator Plugin settings 2"
1760955,2018-05-08 20:38:02 UTC,"Created attachment 7722
Xfce Indicator Plugin settings 3"
1760955,2018-12-08 15:14:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1760956,2020-08-21 15:58:39 UTC,Marking as invalid as the charms now use venvs and are not dependent on system packages.  charms.openstack works in this environment; thus there is nothing to do.
1760956,2020-08-21 15:57:06 UTC,The charm is no longer being maintained.
1760956,2020-08-21 15:46:16 UTC,The charm now includes in the layer.yaml:
1760956,2018-04-03 19:46:02 UTC,"In an interesting and relevant twist, coincidentally the same day we're dealing with pip >= 10.0 and python-apt on a separate bug which affected test execution environments (bug #1760720):"
1760956,2020-08-21 15:40:01 UTC,The charm uses:
1760956,2018-04-03 18:47:41 UTC,"Reference, some recent default behavior changes:"
1760956,2020-08-21 15:43:07 UTC,The src/layer.yaml now contains:
1760956,2018-04-03 18:45:22 UTC,"The following confirms and details the current state of the two options, which are essentially at odds with one-another in terms of declaring dependencies in a sane way."
1760961,2019-09-19 11:57:57 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1760978,2019-10-10 10:31:31 UTC,"I don't think this bug is about snapd, or even about Ubuntu."
1760981,2018-04-10 15:25:35 UTC,currently having the user(s) boot to 4.10 kernel. Has there been any updates for this particular issue?
1760981,2018-04-05 09:31:06 UTC,"Same thing is happening to multiple Ubuntu installations all over our organisation.
We need this fixed ASAP..."
1760981,2018-04-06 15:10:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761001,2018-07-16 20:18:21 UTC,"I can confirm this happening in 3.0.9, as well."
1761001,2018-10-15 16:50:43 UTC,"Still happening in 3.1.6. Would prefer a ""Copies deleted"" or ""Items deleted"" message."
1761002,2019-01-14 08:54:34 UTC,This is less about the charms and more about the deployment.
1761002,2019-11-18 16:22:53 UTC,I have verified the issue with the latest charms (OpenStack Charms release 19.10).
1761002,2019-11-18 22:32:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/694852"
1761002,2019-11-19 16:50:58 UTC,"Reviewed:  https://review.opendev.org/694852
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=1bbcc43f40d739dd88c808b5cf2c586a013150b5
Submitter: Zuul
Branch:    master"
1761002,2019-01-07 17:09:43 UTC,"We believe this is resolved in the latest ceph-mon and ceph-osd charm revisions. If you find that that is not the case, please re-open this bug with additional and updated information. Thank you."
1761003,2018-12-17 14:34:49 UTC,"Yes, may be related to Bug #1748839 reported by Petr Michalec on 2018-02-12!  Almost a year ago!"
1761003,2018-10-01 19:19:49 UTC,Bug is also happening 18.10
1761003,2018-04-04 20:08:03 UTC,"Hello,"
1761003,2018-04-04 14:35:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1761003,2018-05-01 10:05:38 UTC,Looks like same as: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839
1761005,2018-04-04 13:38:30 UTC,"Already fixed in 1.0.6 release, marking bionic fix released."
1761012,2018-04-03 23:16:25 UTC,"hmm, it seems to be there to me."
1761012,2018-04-03 23:35:31 UTC,"I thought I did, since I also did a general 'apt-get upgrade' to get the system current before adding extra software."
1761013,2018-04-03 22:46:03 UTC,"StacktraceTop:
 ImageStrings::find(Endian*, char const*, int*, unsigned int) () from /tmp/apport_sandbox_p6i2e2i_/usr/lib/jvm/java-9-openjdk-amd64/lib/libjimage.so
 ImageFileReader::find_location_index(char const*, unsigned long long*) const () from /tmp/apport_sandbox_p6i2e2i_/usr/lib/jvm/java-9-openjdk-amd64/lib/libjimage.so
 JIMAGE_FindResource () from /tmp/apport_sandbox_p6i2e2i_/usr/lib/jvm/java-9-openjdk-amd64/lib/libjimage.so
 ClassPathImageEntry::open_stream(char const*, Thread*) () from /tmp/apport_sandbox_p6i2e2i_/usr/lib/jvm/java-9-openjdk-amd64/lib/server/libjvm.so
 ClassLoader::load_class(Symbol*, bool, Thread*) () from /tmp/apport_sandbox_p6i2e2i_/usr/lib/jvm/java-9-openjdk-amd64/lib/server/libjvm.so"
1761013,2021-01-13 20:53:34 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1761018,2020-03-17 14:32:42 UTC,"Ah, thanks for that. I think I can document around the specific issues we have by recommending specifying instance types in an overlay, but yes, in general it sucks."
1761018,2020-03-16 15:46:33 UTC,"This still seems to be a problem on a lot of regions, and not limited to bootstrapping"
1761018,2020-03-16 22:07:46 UTC,"Looks like the valid SKUs are subscription specific sadly.
So unlike other clouds where there's a known list of instances types for regions, this will need to be dynamically determined each time for the given credential in use."
1761042,2019-11-01 09:09:45 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1761042,2020-01-01 04:17:23 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1761048,2020-10-04 22:17:27 UTC,good detailed writeup of some requirements in https://bugs.launchpad.net/charm-ceph-mon/+bug/1813360
1761048,2020-10-12 05:55:25 UTC,https://review.opendev.org/#/c/757370/
1761048,2020-11-18 02:27:49 UTC,"Reviewed:  https://review.opendev.org/757370
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=a5ef8d687d1b315138ab5c7076f268e78aab6d35
Submitter: Zuul
Branch:    master"
1761050,2018-08-01 15:02:23 UTC,"Change abandoned by Dougal Matthews (<email address hidden>) on branch: master
Review: https://review.openstack.org/462056
Reason: Abandoning in favor of...
https://review.openstack.org/#/c/572448/
https://review.openstack.org/#/c/585904/"
1761050,2021-02-19 15:51:50 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1761050,2019-12-23 06:41:54 UTC,"Hi, we're looking for volunteers to take this bug. Ideally, from the TripleO team. Anybody is interested? The Mistral core team won't likely be able to take it in Ussuri 2."
1761050,2019-07-27 20:54:43 UTC,"hi @d0ugal , @alex-schultz
i wonder why this change is abandoned ? (unless i misunderstood)
i m having thee same error's and the same scenario with containerized undercloud
with Rocky version
The scenario mainly reproduces on large deployment (more then 30 Blades)
can you suggest a solution ?"
1761050,2019-06-07 19:01:52 UTC,"Change abandoned by Brad P. Crochet (<email address hidden>) on branch: master
Review: https://review.opendev.org/572448"
1761050,2018-08-30 05:35:40 UTC,"Reviewed:  https://review.openstack.org/585904
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=0f17aecbe9a45744341fa4ca1a498de4f57ed531
Submitter: Zuul
Branch:    master"
1761050,2018-07-18 12:29:29 UTC,"Change abandoned by Brad P. Crochet (<email address hidden>) on branch: master
Review: https://review.openstack.org/572448
Reason: Will see if Change-Id: Ia2a19a3fcd8808475a16d4d439e085e62a00dfdc works better"
1761050,2018-04-04 20:46:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/558922"
1761050,2018-04-19 15:38:16 UTC,Added the security-hardening tag as we now require a 4 hour Keystone token that has security disadvantages.
1761050,2018-04-16 15:20:46 UTC,We have a related Mistral bug: https://bugs.launchpad.net/mistral/+bug/1595084
1761050,2018-04-16 15:19:26 UTC,"therve told me about some testing related to this bug, it seems you can replicate the same issue with the heat actions. So this is likely a bug specific to Mistral."
1761050,2018-04-05 22:56:20 UTC,"Reviewed:  https://review.openstack.org/558922
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=02cacfd53a9cf168d7e1967faef3211333800eb6
Submitter: Zuul
Branch:    master"
1761050,2018-04-04 05:48:18 UTC,"I don't think it's a token provider configuration issue, since we only have 2 keys by default. And the deployment seems to start and go forward for quite a while: https://logs.rdoproject.org/56/542556/100/openstack-check/gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-master/Z64d11a27268e46db803351bb52f7cc25/undercloud/home/jenkins/overcloud_deploy.log.txt.gz"
1761050,2018-04-04 07:31:36 UTC,"Going through the zaqarclient codebase, it seems to me that they don't use keystone sessions to do http requests, instead, they use the session to get the token explicitly and further in their ""transport drivers"" they build another object to do the requests. in the case of the http driver, they create another requests session and put the headers explicitly there. This is where they do authentication:"
1761050,2018-06-05 15:26:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572448"
1761053,2018-06-03 03:19:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761060,2019-05-16 23:03:32 UTC,This issue was fixed in the openstack/puppet-ec2api 11.6.0 release.
1761060,2018-05-24 05:20:16 UTC,"Reviewed:  https://review.openstack.org/570127
Committed: https://git.openstack.org/cgit/openstack/puppet-ec2api/commit/?id=89d721612be1d380d453cdbf4118623281de3cdc
Submitter: Zuul
Branch:    stable/pike"
1761060,2018-05-24 05:20:08 UTC,"Reviewed:  https://review.openstack.org/570126
Committed: https://git.openstack.org/cgit/openstack/puppet-ec2api/commit/?id=8efff78512acbdf878b070d46453d29404744814
Submitter: Zuul
Branch:    stable/queens"
1761060,2018-04-19 21:00:18 UTC,This issue was fixed in the openstack/puppet-ec2api 13.0.0 release.
1761060,2018-05-23 07:09:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/570126"
1761060,2018-04-13 19:14:57 UTC,"Reviewed:  https://review.openstack.org/558697
Committed: https://git.openstack.org/cgit/openstack/puppet-ec2api/commit/?id=814ae8df60ee842a126c2ecced47c42b0528ad4d
Submitter: Zuul
Branch:    master"
1761060,2018-04-04 05:56:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/558697"
1761060,2018-05-23 07:09:32 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/570127"
1761070,2018-04-05 08:47:38 UTC,"Hi, could you please provide more details about the issue? what kind of error messages are you seeing when neutron/agent/linux/iptables_firewall.py takes default bridge name from network ID? how we can reproduce it?"
1761070,2018-04-05 09:21:23 UTC,If if have the following set:
1761080,2018-04-04 20:36:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761093,2018-04-05 09:06:39 UTC,"well, apparently, it was a glitch… The migration just finished. Like… yes…"
1761093,2021-02-18 16:46:14 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1761096,2020-09-22 15:09:02 UTC,"The verification of the Stable Release Update for squid3 has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1761096,2020-09-22 15:08:57 UTC,This bug was fixed in the package squid3 - 3.5.12-1ubuntu7.14
1761096,2020-09-16 15:52:47 UTC,Verifying that the bug is fixed.
1761096,2020-09-09 16:57:42 UTC,"Hello Olivier, or anyone else affected,"
1761096,2020-09-09 16:50:52 UTC,"On Xenial the source package is squid3, not squid, so I'll add/adjust tasks for that so the tracking works correctly."
1761096,2020-09-04 20:53:59 UTC,I'm marking the dnsmasq bug as Invalid since this is a problem with squid/systemd.
1761096,2020-09-04 11:03:53 UTC,"On Friday, September 04 2020, Christian Ehrhardt  wrote:"
1761096,2020-09-04 06:34:12 UTC,Thanks for --no-ask-password Sergio.
1761096,2020-09-03 01:11:29 UTC,"Thanks for the further investigation, Christian."
1761096,2020-09-02 06:27:44 UTC,"Since Sergio mentioned groovy, this really only is a xenial issue:"
1761096,2020-09-02 06:15:03 UTC,"Sergio:

> ""squid takes 30 seconds to restart regardless of dnsmasq/resolvconf (this is still true nowadays, with groovy)""
"
1761096,2020-09-02 06:14:47 UTC,"Sergio:

> ... reload"" actually exits successfully ... systemctl ... keeps waiting
"
1761096,2020-09-01 20:39:20 UTC,"OK, I've spent some time investigating this one, so I decided to post my progress here.  Unfortunately I don't have a full fix yet, but I managed to find some interesting pointers related to systemd."
1761096,2018-10-25 21:42:47 UTC,"Regardless of resolvconf or dnsmasq, squid itself takes about 30s to restart. I wonder if it depends on dnsmasq via nss-lookup, then when dnsmasq is restarted, that tries to restart squid, which takes 30s each time? I couldn't reproduce the ""squid reload"" blocking when I run it manually, but I do see it happening in the ps fauxw tree, just like Christian did."
1761096,2018-10-25 21:24:08 UTC,"This is complicated indeed. I also spotted this in the logs during the long wait:
Oct 25 21:16:07 xenial-squid-dnsmasq systemd[1]: nss-lookup.target: Job nss-lookup.target/start failed with result 'dependency'."
1761096,2018-06-20 14:24:41 UTC,"I confirm that every second
 $ systemctl restart dnsmasq
hangs"
1761096,2018-04-04 10:58:09 UTC,I works also very well with trusty
1761096,2018-04-04 10:46:28 UTC,Note that this does not apply to bionic release nor artful for which everything seems to be working very smoothly
1761096,2020-09-02 07:33:17 UTC,"As already reported dnsmasq hangs on the hooks:
             ├─2089 /bin/sh /etc/init.d/dnsmasq systemd-start-resolvconf
             ├─2097 run-parts --arg=-a --arg=lo.dnsmasq /etc/resolvconf/update.d
             ├─2116 run-parts /etc/resolvconf/update-libc.d
             ├─2129 /bin/sh /etc/resolvconf/update-libc.d/squid
             ├─2130 /bin/sh /usr/sbin/invoke-rc.d squid reload
             └─2148 systemctl reload squid.service"
1761103,2018-04-04 12:31:17 UTC,I have no time to work on a snap sorry. Someone else will have to step up and do the work.
1761103,2018-04-04 16:42:16 UTC,"No reason to be sorry, I didn't expect that. :)
I just didn't want it to be entirely forgotten."
1761105,2018-07-24 09:34:32 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1761105,2018-05-08 05:33:14 UTC,This should be fixed by 4.13.0-40.45.
1761105,2018-04-04 23:41:22 UTC,Tested latest v4.16 kernel kernel-fixed-upstream tag was added
1761105,2018-04-04 15:23:08 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1761105,2018-04-04 09:00:06 UTC,This change was made by a bot.
1761105,2018-04-23 23:15:16 UTC,confirming the problem still exists in ubunu kernel version linux-image-4.13.0-39-generic
1761114,2018-04-04 09:11:19 UTC,"besides, exec-personality-aarch64.service get format issue in commit 12591863."
1761114,2018-04-04 09:31:35 UTC,"Why are you building obsolete systemd from xenial?
The systemd package you downloaded is more than 2 years old, for xenial.
The latest xenial release of systemd is 229-4ubuntu21.2, which you can download from xenial-updates using e.g."
1761114,2018-04-04 10:21:45 UTC,"I am taking some features off on systemd, so i have to rebuild systemd package.
Yes, I am building as root, and after pull the latest release and checked the source code,
I think this issue still exists."
1761114,2018-04-04 10:41:42 UTC,"verified, build failed with version 229-4ubuntu21.2.
I was built with the command:"
1761119,2018-04-04 09:49:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/558771"
1761119,2018-04-12 08:11:24 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/558771"
1761119,2018-12-10 21:09:52 UTC,This looks like it was fixed with https://review.openstack.org/#/c/559771/ ?
1761128,2018-04-10 06:34:01 UTC,It worked with xubuntu 16.04.
1761128,2018-04-24 04:41:54 UTC,Can you try 4.15.0-11-generic? There are other report says that it's a regression between -11 and -13.
1761128,2018-04-04 15:21:03 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1761128,2018-04-04 10:30:08 UTC,This change was made by a bot.
1761128,2018-04-10 04:19:12 UTC,Did it work on any previous kernel?
1761142,2020-02-20 16:25:04 UTC,"I have tested this code and consent to signing off on it with my name, rfrasur, and my email address, <email address hidden>."
1761142,2020-08-03 21:41:01 UTC,"Pushed to master, rel_3_5, and rel_3_4, along with a follow-up that tweaks the field-changed style to ensure visibility and color contrast. Thanks, a. bellenir and Ruth!"
1761142,2019-03-28 16:35:45 UTC,"here's a branch that adds a green border around fields whose values have changed for the selected copies.
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/abellenir/lp1761142-volcopy-editor-changed-fields-hard-to-discern"
1761142,2018-04-04 14:23:30 UTC,The image Bob supplied is of the volume/copy editor after a template has been applied.
1761142,2018-04-04 12:14:18 UTC,"See related bug 1538666. Robert, your screenshot showing the volume/copy editor or the template editor? In my experience, I don't even get any visual cue when most fields are edited because any with pre-populated values start off as green. We definitely could use some improvement here."
1761142,2018-04-04 16:18:50 UTC,Adding a screen shot to show the green highlighting of edited item attributes in the XUL client for comparison. The highlighting occurs if a template is applied or if the attribute is manually edited.
1761144,2018-04-04 16:04:58 UTC,I can confirm there's no debug option in the charm config in cs:grafana-10.
1761144,2019-06-07 11:47:36 UTC,Fixed in https://code.launchpad.net/~tcuthbert/grafana-charm/+git/grafana-charm/+merge/368535
1761153,2020-11-10 15:42:33 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1761153,2021-01-10 04:17:33 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1761170,2018-12-05 15:06:03 UTC,"This kinda goes back to a bit of a management conflict on the haproxy service; the principle service manages its configuration file and will do restarts when the conf file changes, however the pacemaker cluster is also 'managing' the daemon including monitoring checks to ensure it keeps running."
1761173,2018-04-12 03:09:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761173,2018-04-04 14:33:53 UTC,"Hi,"
1761173,2018-04-04 13:26:10 UTC,"StacktraceTop:
 __assert_fail_base (fmt=0x7f9ee9f04b03 <error: Cannot access memory at address 0x7f9ee9f04b03>, assertion=assertion@entry=0x7f9ee8f93660 ""!xcb_xlib_threads_sequence_lost"", file=file@entry=0x7f9ee8f934cb ""../../src/xcb_io.c"", line=line@entry=259, function=function@entry=0x7f9ee8f93908 <__PRETTY_FUNCTION__.14350> ""poll_for_event"") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f9ee8f93660 ""!xcb_xlib_threads_sequence_lost"", file=file@entry=0x7f9ee8f934cb ""../../src/xcb_io.c"", line=line@entry=259, function=function@entry=0x7f9ee8f93908 <__PRETTY_FUNCTION__.14350> ""poll_for_event"") at assert.c:101
 poll_for_event (dpy=dpy@entry=0x561bc9a54580) at ../../src/xcb_io.c:256
 poll_for_response (dpy=dpy@entry=0x561bc9a54580) at ../../src/xcb_io.c:274
 _XEventsQueued (dpy=dpy@entry=0x561bc9a54580, mode=mode@entry=2) at ../../src/xcb_io.c:349"
1761184,2018-04-19 11:50:19 UTC,"No verification test for hwe-edge, as it's the same as the bionic kernel, so verification should have been done on the master kernel."
1761184,2018-04-19 12:04:13 UTC,"< taihsiang> cascardo: no, we don't cert test hwe-edge"
1761184,2018-04-19 15:20:10 UTC,"Regression testing seems to have same results as from the last version. xfstests was okay on arm64, failed for unrelated reasons on other arches. Assuming OK there."
1761184,2018-04-23 08:23:37 UTC,This bug was fixed in the package linux-hwe-edge - 4.15.0-15.16~16.04.1
1761184,2018-04-23 09:03:38 UTC,The package has been published and the bug is being set to Fix Released
1761193,2018-04-04 16:14:10 UTC,https://github.com/snapcore/snapd/pull/4983 should fix this.
1761193,2018-04-04 15:39:24 UTC,People shouldn't need it; every use of it means there's a bug (or lack of a feature).
1761193,2018-04-04 14:40:18 UTC,"This workaround seems ok, thanks :)
Maybe this SNAPD_AUTH_DATA_FILENAME should get documented somewhere ?"
1761193,2020-03-04 13:33:45 UTC,"Hi All,
This bug affects our corporate environment which uses root-squashed, kerberized homes on RHEL 8.  It would be very very nice to have software never assume as root that it should be able to arbitrarily write into a user's homedir.  That should be reserved for software that has already dropped privs back to user.
Thanks!
 - Kodiak"
1761193,2018-04-04 14:14:13 UTC,"My problem might be elsewhere… After creating a ~/.snap/auth.json:
`snap install something` → ""error: cannot add authorization: EOF"""
1761193,2018-04-04 13:54:38 UTC,"As a workaround to get you unblocked, you can set SNAPD_AUTH_DATA_FILENAME to something nonexistent and things should work."
1761193,2018-04-04 13:46:28 UTC,"one question I have is why isn't policykit prompting you for your password: as long as your snapd is reasonably up to date, running ""snap install something"" should use policykit to prompt you for your password."
1761193,2018-04-04 14:16:27 UTC,"sorry, to be clear:"
1761197,2019-05-13 08:01:35 UTC,@sorrison: nice!
1761197,2019-05-11 02:44:22 UTC,"Cool thanks, ended up doing it with 2 things."
1761197,2019-05-09 11:16:37 UTC,"@sorrison: We basically did what's in the patch, a temp migration tool to get us past that :). Since it was a migration, wasn't sure if it would get merged upstream, so didn't propose it. However you could use it downstream and if you have any questions feel free to ask."
1761197,2019-05-23 13:24:31 UTC,"Change abandoned by Surya Seetharaman (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/657995
Reason: purpose served."
1761197,2019-05-09 00:03:36 UTC,"Was there any work around for this?
We are just planning cellsv1->v2 migration and we are hitting this. Thinking of writing some code but wondering if you already have something CERN?"
1761197,2018-04-05 17:49:48 UTC,I think some of this is expected with the syncing up-down of instance data from parent cell to child cells and vice versa. There's some incompleteness there as Surya explained that some instance_extra fields are populated in the child cell DBs and some aren't.
1761197,2018-04-04 15:40:33 UTC,"Also, new instances don't have the keypair (NULL) defined in instance_extra in child cells DBs when running cellsV1. This is happening in Ocata."
1761197,2019-05-09 11:10:13 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/657995"
1761198,2018-04-04 21:10:08 UTC,"Per the cells meeting today, we should look at rolling this into the online_data_migrations routine so we can eventually remove it later, since once you get to Queens and archive does the cleanup for you, we won't need a separate command for this older record cleanup."
1761198,2018-04-10 14:39:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/560042"
1761216,2020-08-02 23:13:54 UTC,"OK, then yah, I suspect the change I recently made should fix this: deja-dup now checks fstab and mounts the target location before a backup starts."
1761216,2020-08-19 16:46:50 UTC,This bug was fixed in the package deja-dup - 42.2-1ubuntu1
1761216,2020-08-03 15:40:20 UTC,"Yes, since 20.04, I have not had the problem, but I thought it was due
to using a linux server and smb  which solved the problem."
1761216,2020-08-03 09:57:33 UTC,"The upstream commit seems to be https://gitlab.gnome.org/World/deja-dup/-/commit/e349a1c7 , if it fixes the issue we should probably backport that one to the LTS"
1761216,2020-08-02 16:44:05 UTC,"Yes, it is listed in fstab and yes, I entered the path as a local
storage device."
1761216,2018-04-06 02:26:43 UTC,"I tried using ""Disks"" to allow for the partition on which the backups live on a local drive to ""mount on startup""."
1761216,2018-09-17 16:37:11 UTC,I have not found the bug you describe to be true.
1761216,2018-09-16 21:00:46 UTC,Hello everyone.
1761216,2018-08-15 10:02:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761216,2018-04-05 19:47:40 UTC,This was on 18.04 Beta.
1761216,2020-08-01 17:57:38 UTC,How is this other drive configured? Is it an entry in fstab? And you were entering its path as a Local Folder storage location?
1761222,2020-02-21 19:55:45 UTC,"Hi Chris,
I created the new bug, it's LP# 1864236
<https://bugs.launchpad.net/evergreen/+bug/1864236>, Usability improvements
to Holdings View grid."
1761222,2020-02-21 18:38:30 UTC,"Committed to master.  Since this is adding new features, not backporting to 3.3/3.4."
1761222,2019-02-05 20:44:27 UTC,"Thanks, Remington."
1761222,2020-02-18 20:06:08 UTC,"Tiffany,
I tested this too and can confirm, like you did, the column choices are there.
Suggestions for improvements are:
1.) add grid lines to separate columns for easier reading
2.) designate item attributes that are ""Yes"" or ""No"" by just the letters Y and N
3.) the ability to resize columns as Elaine and Sarah mentioned above
4.) make column headers more readable when columns are shrunk by having text wrap or abbreviated."
1761222,2020-02-18 19:33:03 UTC,"I can confirm that I can see values in the columns that Remington specified, and that the Due Dates are only showing for items in a non-checked in circulation."
1761222,2019-07-30 20:05:59 UTC,"I have signed off on Bill's new commit, and I added one more commit to fix my misunderstanding of the ""quality"" column.  Here's my branch:"
1761222,2018-11-09 20:04:29 UTC,"FYI, here's the existing bug for not being able to resize columns:"
1761222,2018-11-06 15:33:52 UTC,"Janet, I confirmed with Galen that the old ""Alert Message"" column is deprecated as of 3.1, since the new Item Alert matrix was added. That means the 3.1 upgrade process converts old style alerts into the new alert structure, so they are accessible via the new ""Alerts"" column (which includes a count and a ""Manage"" button to open the new alert screen)."
1761222,2018-11-07 16:51:42 UTC,"That list of options looks good to me, and I agree with Elaine on her comments about the columns. The pop-up is an improvement, but we're more often than not trying to compare multiple items at once. The ability to drag columns wider and narrower is greatly missed. Also the limits on how narrow you can make a column are particularly maddening when you want more real estate and you have to waste a bunch of dead space on columns that have data a single character wide. Overall there are a ton of great features in the web client, but the thing I miss the most is the old column functionality."
1761222,2018-11-07 16:11:44 UTC,Here's a branch that adds the six missing columns I mentioned above:
1761222,2018-11-07 15:17:08 UTC,"The bubble pop-up, while nice, doesn't allow viewing all of an attribute at once. Nor does the better column config provide a workable solution. For example, I need to see most attributes in Holdings view on a regular basis, which means long call numbers may be cut off. Re-doing the column configuration by removing fields and making the call number column larger is cumbersome and time consuming. The popup only allows me to see one call number at a time when I need to see multiple call numbers. Being able to adjust the column width as needed allows me to see long call numbers at once, making choosing the vols that need editing more efficient."
1761222,2018-11-07 14:48:03 UTC,">>This may need to be a separate ticket but we also need to be able to make the columns as wide as we need to be able to read the attribute. In the XUL client, we can adjust a columns width as needed by dragging it wider. We no longer have that ability in the web client.<<
"
1761222,2018-11-06 21:00:17 UTC,Elaine Hardy (in person) also asked for any columns that are in the XUL client. Here is what seems to be missing:
1761222,2018-10-05 19:38:39 UTC,"I created a duplicate of this bug, mine is #1761222:
In holdings view the choices for columns in the web client are not the same as those in the xul client. Missing choices are ""alert message"", ""fine level"", and ""loan duration"". The alert message is particularly missed as it helps catalogers see that it's been added correctly to item records.
I see between 3.0.9 and 3.0.12 the missing deposit and deposit amount have been added to the web client. We'd like to see the web client have the same choices as the xul one."
1761222,2018-04-04 15:55:28 UTC,"This may need to be a separate ticket but we also need to be able to make the columns as wide as we need to be able to read the attribute. In the XUL client, we can adjust a columns width as needed by dragging it wider. We no longer have that ability in the web client."
1761222,2018-11-08 19:34:43 UTC,"+1 for what Sarah and Elaine said. I also would like to have the ability to drag columns to customized widths. I also noticed that the minimum size is not the same in all interfaces. In View Holds I can size the price column so small I can only see the $ and first digit. In Item Status and Holdings View I have enough room for a $9,000.00 item when it's at the smallest."
1761223,2020-04-01 15:08:40 UTC,fixed in 1.2.8-2
1761223,2018-04-30 15:38:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761223,2018-05-11 20:45:58 UTC,https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1770392 has more information.
1761226,2018-04-04 16:07:33 UTC,should first be a question
1761229,2018-04-07 13:10:45 UTC,Can you explain a bit what the use cases for querying the geometric width would be?
1761229,2018-04-07 14:13:25 UTC,"Thanks for considering this. My use case is in a Python script, where use the Inkscape CLI get basic dimensionality information (and sometimes run some verbs). Extracting the geometric dimensions from an SVG object is not easy and requires e.g. understanding nested transformations, and finding max and min points in bezier curves. I could perhaps be using PythonWebkit instead, but the Inkscape CLI is very easy to use, and performance is not critical for my script. I guess this kind of use case is basically why the Inkscape CLI exists?"
1761229,2018-04-07 14:45:44 UTC,"There are some helper functions available for usage by Python extensions, see [1]."
1761229,2018-04-09 08:21:05 UTC,"Thanks for the pointer to simpletransform.py! It certainly seems to handle most of the complexity I was talking about (transforms and bounding boxes of bezier curves), though it seems to still need a bit of tweaking to be pluggable in my use case (descending into groups, at least)."
1761234,2019-01-11 18:02:18 UTC,"I was wondering whether there was any update on this issue, or if there was a chance it might move forward? I don't think it's too big of a change, and it would save a lot of time, especially on large designs."
1761234,2019-02-08 07:13:15 UTC,"This ""bug"" torture me almost daily"
1761234,2019-02-07 23:09:30 UTC,No update as yet.
1761234,2018-08-27 14:13:34 UTC,"If you don't mind asking, is there a specific concern associated with allowing a user to do this? The Symbol Library References tool - which is a really useful tool - is almost exactly what we need, except it doesn't actually update symbol parameters or fields across the entire design."
1761234,2019-11-13 16:49:54 UTC,"Hi,"
1761234,2018-06-21 20:11:40 UTC,"I was also a bit surprised to find out that the update did not affect the full schematic but only the current page. Was actually in the process or preparing a feature request for this, but found out this was already requested here."
1761234,2018-05-24 20:40:59 UTC,Kicad does lend itself to git for revision control (which is what we use).
1761234,2018-05-23 15:54:41 UTC,"The problem here is the undo buffer, which is not shared between sheets. The field update process may run on the whole project, but then one would not be able to undo it. There are discussions about solving the separate undo buffers problem in v6."
1761234,2018-05-18 17:07:21 UTC,"Hi,"
1761234,2018-04-12 10:09:50 UTC,For the moment it is impossible to create undo entries for changes affecting multiple sheets. Modifying the update field tool to work on multiple sheets means we need to sacrifice the undo possibility.
1761234,2018-06-22 14:41:38 UTC,After 5.0 gets out the door JP and I are going to do 3 rounds in the boxing ring over this.
1761237,2018-04-04 18:08:44 UTC,"As best as I can work out, MachineAgent.initController uses agentConfig.MongoInfo() which then gets passed to mongo.DialWithInfo()."
1761237,2018-04-19 12:23:15 UTC,"The running system has been restarted a few times, and played with a bit more. So I'm not sure how bad I'm making it, but it has been complaining about raft a lot in the log.
It is currently HA 3 on machines 1,3,7:
1        started  10.16.17.211  juju-ebff95-1  xenial      Running
3        started  10.16.17.189  juju-ebff95-3  xenial      Running
6        stopped  10.16.17.22   juju-ebff95-6  xenial      Running
7        started  10.16.17.120  juju-ebff95-7  xenial      Running"
1761237,2018-04-04 17:29:39 UTC,"Also note, even after creating new extra machines, and killing some of them, and then bringing more up, it still has something that is trying to connect to the machines that are now gone:"
1761237,2018-04-04 17:58:55 UTC,"Oddly, the only addresses it claims actually work is localhost, even though it should be able to try to reach mongo on the other replica's ports:
3078:machine-6: 21:57:17 DEBUG juju.mongo dialled mongodb server at ""127.0.0.1:37017""
3079:machine-3: 21:57:18 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.189:37017: connect: no route to host
3080:machine-3: 21:57:18 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.4:37017: connect: no route to host
3081:machine-5: 21:57:42 DEBUG juju.mongo dialled mongodb server at ""127.0.0.1:37017""
3082:machine-5: 21:57:45 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.189:37017: connect: no route to host
3083:machine-5: 21:57:48 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.189:37017: connect: no route to host
3084:machine-6: 21:57:48 DEBUG juju.mongo dialled mongodb server at ""127.0.0.1:37017""
3085:machine-5: 21:57:51 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.189:37017: connect: no route to host
3086:machine-3: 21:57:51 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.189:37017: connect: no route to host
3087:machine-3: 21:57:51 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.4:37017: connect: no route to host
3088:machine-3: 21:57:54 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.189:37017: connect: no route to host
3089:machine-3: 21:57:54 WARNING juju.mongo mongodb connection failed, will retry: dial tcp 10.16.17.4:37017: connect: no route to host"
1761238,2019-01-24 13:37:18 UTC,"Tested in 3.1.2 - Still occurring.  Similar silent failure happens if the bib record has no items at all, not just non-holdable items."
1761241,2018-04-04 16:58:16 UTC,"I'd like to also note that, I'm wondering if this override does not currently exist, as a way to prevent staff from accidentally placing holds on empty bibs. Seems some nuance might be needed here."
1761241,2018-04-04 17:13:00 UTC,"I could be remembering incorrectly, but I think even if the hold is overridden, the hold will never capture since the system will not see an eligible copy to fill the hold. Can anybody confirm this?"
1761241,2018-04-04 17:27:23 UTC,"Kathy,"
1761241,2018-04-04 19:15:05 UTC,The override would come in handy during database cleanup when a title I need to see has only missing copies attached. Then I could place a hold in case the item is found and be able to clean up the record.
1761250,2018-04-04 17:45:36 UTC,"StacktraceTop:
 ?? ()
 drag_gesture_update_cb (gesture=0x55b319066610, offset_x=4, offset_y=<optimized out>, window=0x55b318c10d10) at ../../../../gtk/gtkwindow.c:1625
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffe37261980, fn=fn@entry=0x7f2262dd51f0 <drag_gesture_update_cb>, rvalue=<optimized out>, avalue=avalue@entry=0x7ffe37261870) at ../src/x86/ffi64.c:525
 g_cclosure_marshal_generic_va (closure=0x55b317e0cc20, return_value=0x0, instance=<optimized out>, args_list=<optimized out>, marshal_data=<optimized out>, n_params=2, param_types=0x55b317cd2f30) at ../../../../gobject/gclosure.c:1604"
1761251,2018-04-24 14:53:06 UTC,I am checking to see if anyone has looked into this or if this is something that is going to be placed on the back - burner?
1761251,2018-04-07 13:19:09 UTC,I'm afraid I do not understand the problem with the the description given.
1761251,2018-04-09 15:02:07 UTC,"I am working on getting additional information from the actual person who is having the problem.
From what the person is actually stating -
1. They are in the svg drawing and they upload the svg. drawing into the device (aka web server).
when they make those svg. file active - they should be able to enter localhost/SVG/name of saved page.svg but when they make changes and save them to a SVG format it should accept those changes upon upload (which is on my side and was checked.) However the xlink:href naming convention does not change and the person who is having issues saves the file and then to verify that the file name is saved as they need to be they go into the SVG. file properties and they do not see a change in the Xlink:href to reflect what the saved name is. They then make changes to the xlink:href to the name of the saved page and it is not saving when they select save or save as."
1761251,2018-04-12 16:23:47 UTC,Attached SVG files to the bug report
1761255,2018-04-04 17:56:36 UTC,It keeps on crashing when I use add centre child in Gtk-box
1761255,2018-04-04 18:23:42 UTC,"StacktraceTop:
 gtk_box_size_allocate_with_center (widget=0x5601196d1840, allocation=0x7ffdda049d10) at ../../../../gtk/gtkbox.c:932
 gtk_box_allocate_contents (gadget=<optimized out>, allocation=0x7ffdda049d10, baseline=<optimized out>, out_clip=0x7ffdda049d30, unused=<optimized out>) at ../../../../gtk/gtkbox.c:1204
 gtk_css_gadget_allocate (gadget=0x56011a52c970, allocation=allocation@entry=0x7ffdda049e30, baseline=-1, out_clip=out_clip@entry=0x7ffdda049d90) at ../../../../gtk/gtkcssgadget.c:782
 gtk_box_size_allocate (widget=0x5601196d1840, allocation=0x7ffdda049e30) at ../../../../gtk/gtkbox.c:1220
 gtk_widget_size_allocate_with_baseline (widget=widget@entry=0x5601196d1840, allocation=allocation@entry=0x7ffdda049ec0, baseline=<optimized out>, baseline@entry=-1) at ../../../../gtk/gtkwidget.c:6123"
1761256,2018-04-04 18:15:20 UTC,"StacktraceTop:
 read_buffer (source=0x5574d8861690) at glade-previewer-main.c:197
 on_data_incoming (source=0x5574d8861690, condition=G_IO_HUP, data=0x5574d8661360) at glade-previewer-main.c:218
 g_main_dispatch (context=0x5574d8698090) at ../../../../glib/gmain.c:3177
 g_main_context_dispatch (context=context@entry=0x5574d8698090) at ../../../../glib/gmain.c:3830
 g_main_context_iterate (context=0x5574d8698090, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3903"
1761257,2019-09-19 11:57:59 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1761261,2018-04-06 19:23:01 UTC,"Same problem on my ASUS GL703VD.
I tried the 18.04 beta today starting a live session with the suggested boot option (modprobe.blacklist=nouveau).
I can work using an external monitor connected to the HDMI interface. The laptop display become black during the boot just after few seconds but I can see the boot progress on the external monitor."
1761261,2018-04-06 19:23:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761261,2018-04-11 18:28:02 UTC,"Maybe the back-light problem is related to the patch for the  Elan1200 touchpad:
https://bugzilla.redhat.com/show_bug.cgi?id=1543769#c69"
1761261,2018-04-12 09:08:40 UTC,"can you attach your /var/log/gpu-manager.log, please?"
1761261,2018-04-12 10:12:32 UTC,"Here's my log file, as requested, running on the ""standard"" 17.10 kernel with the latest nvidia driver.
investigating my issue I tried to install the 4.15 and 4.16 series kernel using this version of the nvidia driver.
the monitor works fine in the 4.15.3 version, but in the 4.15.4 and higher the monitor remains off."
1761261,2018-04-12 21:11:44 UTC,"I have noticed the same thing. I am running on 16.04 with the HWE 17.10 kernel and monitor works.
I installed the bionic 4.14.0-17 kernel and I was able to still use the laptop display. I tried the latest Bionic kernel (4.15.0-13) and it does not work.
During testing on another bug (LP:1738263) I tested Artful with the Bionic kernel 4.15.0-10 and everything appeared to be working normally with the exception that DKMS failed to build the NVIDIA modules due to not being compatible with the the header files. However, when you install anything newer, the display fails to stay on past the GRUB menu."
1761261,2018-04-16 19:48:59 UTC,"It could be a backlight issue. I tried with the latest daily-build (April 16, 2018) and I boot up with the nouveau.modeset=0 kernel param and it shows the splash screen, and then I hear the login sound, and if I turn off the lights in my office and look closely, I can see the display, but it looks like the backlight for the screen is not lit. I tried adjusting the brightness using the FN+F7/F8 (Which adjust brightness) and they don't work (They don't work on any other distribution/Release as well. Only things that work are volume control and Projector options)."
1761261,2018-04-17 08:22:49 UTC,"The attachment ""spth-pinctrl-fix.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1761261,2018-04-23 17:08:08 UTC,"So I patched the 4.15.0-15-generic kernel from kernel.ubuntu.com with the supplied patch and then intstalled the kernel on my 16.04 xenail laptop and everything works as it should. The display came up, the touch pad is responsive and working normally. I have enclosed my dumps of lswh, lspci, lsmod and my cmdline output."
1761261,2018-07-02 21:34:09 UTC,"So I built a kernel from the Upstream LTS (4.17.3) and tried to apply the patch, which failed. So I removed it and tried a clean build and was able to get Xenial to boot up with this kernel. I then decided to install Bionic and install this kernel on my laptop however, I noticed that when I downloaded the latest version (as of July 2, 2018) the laptop display worked. I checked and I am running Bionic with the 4.15.0-24 kernel. I then installed the NVIDIA proprietary drivers and low and behold the laptop is working. (I had to modify my grub to include nouveau.modeset=0 since after logging in the display would hang, but after passing the kernel parameter everything worked out of the box.)"
1761261,2018-04-30 20:55:42 UTC,"Trackpad and Graphics work with the spth-pincntrl-fix.diff patch on the 4.17 kernel, however, the wifi card does not work, and if you close the lid or it goes to hibernate, the system becomes unresponsive."
1761261,2018-04-17 08:09:05 UTC,"Hi all,
I found this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1543769#c69
and this patch seems to solve the backlight problem (and the ELAN jercky touchpad as well)
I don't know how to compile the kernel with this patch.
maybe someone can build the kernel for me to test on my laptop or let me know how to build myself."
1761261,2018-04-30 19:50:26 UTC,"I tried testing with the latest RC build of the 4.17 kernel from kernel.org (Torvald's GIT) and built the kernel following the instructions here [1].
After installing the kernel and headers, it looks like it regressed and the display did not work (backlight) and I could not switch terminals. I was able to reboot my laptop and switch the the previous kernel. My next test will be with the patches and see what happens."
1761261,2018-04-30 20:11:21 UTC,[1] https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
1761262,2019-09-20 12:18:27 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1761262,2019-09-19 12:05:23 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1761264,2018-04-04 18:47:37 UTC,"Does running ""apt-get -f install"" help. For some reason you don't have libavcodec57 installed even though it is a dependency of ffmpeg."
1761264,2018-04-08 07:11:29 UTC,"> Does running ""apt-get -f install"" help.
"
1761264,2018-04-08 08:50:50 UTC,Thanks that makes more sense.
1761264,2019-04-10 13:15:52 UTC,This bug still exists in Ubuntu 19.04/disco:
1761276,2018-06-19 19:55:44 UTC,"We are also experiencing this issue. When we click on the title, it retrieves the record but then goes to a blank search page. If we refresh the page, it loads the correct record. We are on the web client."
1761276,2018-05-24 18:47:52 UTC,There is discussion of similar-sounding issues in bug 1731272. I tested the fix from that bug's comment #13 but it didn't fix the issue in this bug (I still inconsistently get the splash page during record retrieval).
1761276,2018-05-17 21:24:41 UTC,Ben Holt pointed out that similar-sounding issues have been encountered before by the Angular community.  Examples:
1761276,2018-04-25 20:27:02 UTC,"I can usually reproduce the issue on a 3.1 test server by retrieving record 78 and clicking the title link in record summary.  The link URL is /eg/staff/cat/catalog/record/78.  When I click it, console debug logs include the following sequence:"
1761276,2018-05-04 14:11:34 UTC,(on Evergreen 3.0.2-ish)
1761276,2018-05-04 14:11:15 UTC,I can confirm the problem on Chrome.  I can also confirm that the problem does not happen on Firefox.
1761276,2018-05-04 20:16:45 UTC,Evergreen 3.1
1761276,2018-04-04 19:23:52 UTC,"And sometimes you get caught on that splash page, from a variety of places, and can't get beyond it without clearing the cached images and files for the browser. In those cases, the url is for the record you are trying to display and not for the home (splash) page -- https://gapines.org/eg/staff/cat/catalog/record/1472631 as opposed to https://gapines.org/eg/staff/ -- but redisplaying won't retrieve the record. Going back and clicking the link again won't either."
1761277,2018-04-04 20:05:40 UTC,"The problem is enblend. The bug has already fixed in changeset 882d3ccba621, but is not yet included in a released version."
1761285,2019-06-02 12:38:23 UTC,Playback of youtube videos was fixed in 3.0.6-1.
1761285,2018-04-04 19:36:21 UTC,"Obviously similar to bug 1600645, but behavior and output are different so I think it's a different issue."
1761288,2018-05-04 06:21:41 UTC,"I agree this would be nice to have. However, we do have ""juju-force-upgrade"" which can help depending on the cause of the upgrade failure.
However, most specific upgrade failures ultimately are causing a change to the database that is preventing us from moving forward, which means that there is *some* sort of manual intervention/fixup/cleanup step required. And if we knew what that was going to be, then we would have fixed the original bug and not needed to rollback the upgrade.
If this was deemed particularly critical, we could potentially do something like stop Mongo, copy the db to a backup location, copy the tools to an alternate location, and then have a rollback that would wipe out the active directory and move everything back to what it was."
1761292,2018-04-05 18:31:51 UTC,I agree a snap package would be a good idea. Not sure how easy it is though as Diodon uses quite some Xorg features which might not be allowed within a snap scope.
1761292,2018-04-05 21:57:01 UTC,I've submitted a proposal for that https://github.com/diodon-dev/diodon/pull/8
1761292,2018-04-05 21:57:37 UTC,"Per se, Xorg features are alla allowed within a snap, so it works fine on that terms."
1761292,2018-04-06 07:12:20 UTC,Yeah I know Zeitgeist is kind of end of life. I think this is a shame though as they are no real alternatives covering the same use case. We will need to look into this at some point in the context of #1235880
1761298,2018-04-04 20:30:01 UTC,?
1761298,2018-04-05 16:13:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761299,2019-12-03 20:10:47 UTC,-- GitLab Migration Automatic Message --
1761299,2018-04-04 21:54:57 UTC,I really wish there were some symbols for frame 1 and 2.
1761299,2018-04-04 21:11:28 UTC,"Hello,"
1761299,2018-04-04 20:40:37 UTC,"StacktraceTop:
 tp_handle_inspect (self=0x0, handle=9) at handle-repo.c:277
 ?? ()
 ?? ()
 ?? ()
 ?? ()"
1761299,2018-04-04 20:40:42 UTC,Thank you for your report!
1761306,2018-04-05 20:14:59 UTC,Another example:
1761306,2018-12-23 14:10:01 UTC,"The dynamic-extent is applied to the &rest list, not the function, and then it's used out of extent."
1761306,2018-12-26 15:34:42 UTC,"I am sorry to reopen this.
I believe that propagating DX property outside of a non-DX closure is an error."
1761317,2018-04-06 17:00:42 UTC,"Reviewed:  https://review.openstack.org/558864
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=31bf66133503e339aa3c160b11bfb4e0e418ff8d
Submitter: Zuul
Branch:    stable/newton"
1761317,2018-04-23 21:56:41 UTC,This issue was fixed in the openstack/tripleo-heat-templates 5.3.12 release.
1761318,2018-04-14 02:49:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761322,2019-09-19 14:47:00 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1761322,2018-04-12 00:22:50 UTC,"Can you please re-test this with Blake's fix to properly install the reactor? I think this was a symptom of ""stalled reactor"". When the service is properly running, we check the output of `ip addr` every 30 seconds and update the interfaces if there has been any change."
1761322,2018-04-04 22:43:11 UTC,FWIW I did this:
1761331,2020-09-28 12:01:42 UTC,Fix released in git-ubuntu version 1.0
1761332,2020-09-28 12:01:33 UTC,Fix released in git-ubuntu version 1.0
1761359,2019-09-19 14:47:03 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1761362,2018-04-07 18:21:09 UTC,04/07/2018: Arch Linux has fixed it. https://bugs.archlinux.org/task/58115
1761363,2019-10-01 22:51:00 UTC,There's no interface for zeitgeits as of snapd 2.42. I'm marking this as confirmed.
1761374,2018-04-05 05:19:36 UTC,"Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/174"
1761374,2018-11-20 09:37:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761375,2020-02-23 18:43:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761379,2019-06-20 15:36:33 UTC,On bionic LGTM:
1761379,2019-06-18 16:02:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1761379,2019-06-18 12:02:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1761379,2019-06-18 12:01:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1761379,2019-05-21 13:56:42 UTC,Posted v2. Clarified reported build failure.
1761379,2019-04-04 12:32:14 UTC,"Hi, Gustavo."
1761379,2019-04-29 13:50:34 UTC,"Adding a pointer to the thread of the kernel team SRU mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-April/thread.html#99997
Looks like it missed the current SRU cycle.
Is there a chance to get it into the next cycle?"
1761379,2019-04-11 14:46:52 UTC,"Hi, Gustavo."
1761379,2019-04-04 13:00:08 UTC,"------- Comment From <email address hidden> 2019-04-04 08:50 EDT-------
Hi Cascardo!"
1761379,2019-06-20 15:36:58 UTC,On disco LGTM:
1761379,2019-03-29 03:09:41 UTC,"------- Comment From <email address hidden> 2019-03-28 23:03 EDT-------
(In reply to comment #38)

> Can you try the kernel at ppa:cascardo/linux, and see if that works for you?
"
1761379,2019-05-14 18:53:57 UTC,Probably will be ready for the cycle the ends on the last week of June.
1761379,2019-07-15 22:40:05 UTC,This bug was fixed in the package linux - 5.2.0-8.9
1761379,2019-08-19 18:45:47 UTC,"Brian,"
1761379,2019-07-22 14:09:19 UTC,"Marking Cosmic as ""invalid"" as it is now EOL."
1761379,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1761379,2019-08-16 00:53:58 UTC,"Can anyone comment as to whether or not this will be considered for kernels beyond -generic and -hwe? Specifically for aws, aws-hwe, and aws-edge kernels?"
1761379,2019-03-26 11:19:40 UTC,"------- Comment From <email address hidden> 2019-03-26 07:18 EDT-------
(In reply to comment #39)

> Gustavo, Could you test please
"
1761379,2019-08-19 19:47:05 UTC,"Thanks Brad, I just saw that this has been in -proposed for a bit on bionic, missed that originally when looking for the file https://packages.ubuntu.com/search?searchon=contents&keywords=libperf-jvmti.so&mode=exactfilename&suite=bionic-updates&arch=any
We'll keep our eyes peeled for the release."
1761379,2019-08-22 16:18:18 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1761379,2019-08-27 22:45:09 UTC,"Sorry, agent looks missing on proposed for Xenial. Canonical, could you please check it?"
1761379,2019-09-02 11:19:27 UTC,This bug was fixed in the package linux-aws - 5.0.0-1014.16
1761379,2019-09-02 12:55:36 UTC,This bug was fixed in the package linux-aws-edge - 5.0.0-1014.16~18.04.1
1761379,2019-09-02 13:03:24 UTC,This bug was fixed in the package linux-aws - 4.15.0-1047.49
1761379,2019-09-02 15:18:07 UTC,This bug was fixed in the package linux-aws-hwe - 4.15.0-1047.49~16.04.1
1761379,2019-10-14 01:02:15 UTC,This bug was fixed in the package linux-aws - 5.3.0-1003.3
1761379,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1761379,2019-03-22 10:05:09 UTC,"Hi, Gustavo."
1761379,2018-06-25 15:19:51 UTC,"------- Comment From <email address hidden> 2018-06-25 11:18 EDT-------
(In reply to comment #9)

> Support for artful will end soon (July 2018) therefore marking this as a
> won't fix.
"
1761379,2019-03-21 13:54:30 UTC,"Hi, Gustavo."
1761379,2018-04-05 06:16:54 UTC,"This probably affects one of the packages linux-tools-* that I can't mark, hence using linux (kernel) for now.
It looks to me that we don't ship ""libperf-jvmti.so"" with any package (and never have been).
But letting the kernel-team leave a comment on this ..."
1761379,2018-05-07 11:20:18 UTC,"------- Comment From <email address hidden> 2018-05-07 07:16 EDT-------
Hello,"
1761379,2018-06-25 14:24:49 UTC,Support for artful will end soon (July 2018) therefore marking this as a won't fix.
1761379,2018-06-26 20:23:11 UTC,I'm investigating this for Bionic.  I'll post an update shortly.
1761379,2018-08-27 13:09:38 UTC,"------- Comment From <email address hidden> 2018-08-27 09:00 EDT-------
Hi Salibury,"
1761379,2018-09-13 22:24:11 UTC,I built a test kernel with NO_JVMTI disabled in tools/perf/Makefile.config.
1761379,2018-10-10 21:09:25 UTC,"------- Comment From <email address hidden> 2018-10-10 17:08 EDT-------
Hi Joseph,"
1761379,2018-10-10 22:32:13 UTC,I'll check into why those are missing and should have more packages ready shortly.
1761379,2018-10-11 12:14:23 UTC,I built a v2 test kernel.  All the .debs can be downloaded from:
1761379,2018-10-11 16:49:51 UTC,"------- Comment From <email address hidden> 2018-10-11 12:40 EDT-------
(In reply to comment #18)

> I built a v2 test kernel.  All the .debs can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1761379/v2
>
> Can you test this kernel and see if it resolves this bug?
"
1761379,2018-10-11 19:13:30 UTC,"It's possible this is happening because I'm cross compiling.  I'll build the packages in a PPA, so it is a native compile."
1761379,2019-03-21 20:39:55 UTC,"------- Comment From <email address hidden> 2019-03-21 16:33 EDT-------
Hi Cascardo,"
1761379,2018-10-15 14:02:18 UTC,"Marking as ""incomplete"" while awaiting IBM's test results from the PPA."
1761379,2018-10-17 16:51:11 UTC,"I create one more PPA at the same locate, but with v3 in the name:
 https://launchpad.net/~jsalisbury/+archive/ubuntu/1761379"
1761379,2018-10-18 13:19:49 UTC,"------- Comment From <email address hidden> 2018-10-18 09:14 EDT-------
(In reply to comment #23)

> I create one more PPA at the same locate, but with v3 in the name:
> https://launchpad.net/~jsalisbury/+archive/ubuntu/1761379
"
1761379,2018-10-18 20:19:33 UTC,"------- Comment From <email address hidden> 2018-10-18 16:11 EDT-------
Hi Joseph,"
1761379,2018-11-26 15:07:33 UTC,This bug is awaiting a decision from the kernel team because it adds a dependency on Java for kernel builds.
1761379,2018-12-21 16:17:25 UTC,"quick update:
Looks like a way was found (by apw) to modify the dependencies to become able to finally ship libperf-jvmti.so, but this needs to be discussed with the Ubuntu archive team first - which is the next step here..."
1761379,2018-12-21 17:19:52 UTC,"------- Comment From <email address hidden> 2018-12-21 12:13 EDT-------
Hi Frank,"
1761379,2019-03-15 04:39:53 UTC,"------- Comment From <email address hidden> 2019-03-15 00:38 EDT-------
Any update on this bug ?"
1761379,2019-03-18 18:29:48 UTC,"------- Comment From <email address hidden> 2019-03-18 14:24 EDT-------
Frankly, it's quite upsetting not hearing from Canonical after so much time. I do understand that kernel team might frown upon adding a Java stuff as a dep for building the kernel packages and that any other similar conundrum might exist. But it seems Canonical is not paying much attention at all to that issue which, besides PPC64, also applies to other architectures."
1761379,2019-03-18 19:59:17 UTC,I sincerely apologise for the delay. I'll do my utmost to get you a response as soon as possible.
1761379,2019-03-19 09:21:39 UTC,"The canonical engineering team has been tracking this issue, but apologies again for the delay in responding to the request for technical discussion on this bug."
1761379,2019-03-20 15:16:32 UTC,"I am doing a test build in order to try to provide this package, and look at how many dependencies changes that introduces."
1761379,2019-03-20 16:29:46 UTC,"------- Comment From <email address hidden> 2019-03-20 12:22 EDT-------
Thanks a lot Andrew, Terry, and Cascardo."
1761379,2018-10-15 21:39:31 UTC,"------- Comment From <email address hidden> 2018-10-15 17:33 EDT-------
Hi Joseph,"
1761379,2018-05-11 15:10:17 UTC,"------- Comment From <email address hidden> 2018-05-11 11:07 EDT-------
Hi Canonical,"
1761382,2020-11-03 14:19:59 UTC,"Upon boot, checking journalctl -eb:"
1761382,2020-11-05 12:11:58 UTC,"Same comment as David Oswald (daoswald) here, from an Arch linux 5.9.3-arch1 running gdm on xorg."
1761382,2018-04-05 06:18:13 UTC,@Daniel
1761382,2018-04-05 06:08:56 UTC,Confirmed. But is it breaking anything?
1761382,2018-04-05 06:08:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761382,2018-09-13 07:41:55 UTC,Breaks importing firefox data into brave browser.
1761390,2020-04-22 21:42:53 UTC,I fixed this in https://discourse.ubuntu.com/t/service-kerberos-with-openldap-backend/15356
1761390,2020-04-22 22:50:57 UTC,The published location for that source code reference is:
1761405,2018-04-19 12:44:48 UTC,"Reviewed:  https://review.openstack.org/561954
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c0db837835438f89a10e2dfb130db2f39cb18477
Submitter: Zuul
Branch:    stable/queens"
1761405,2018-09-24 14:47:21 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1761405,2018-06-04 14:28:00 UTC,This issue was fixed in the openstack/nova 16.1.4 release.
1761405,2018-05-30 10:51:39 UTC,"Reviewed:  https://review.openstack.org/563254
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a731a05ab6a67a51f774e24e46d57ca5a5920f8
Submitter: Zuul
Branch:    stable/pike"
1761405,2018-04-25 09:23:51 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1761405,2018-04-20 19:35:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/563254"
1761405,2018-04-20 13:12:28 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1761405,2018-04-17 14:09:36 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561954"
1761405,2018-04-16 11:39:23 UTC,I feel that our current knob oslo_messaging_notifications.driver = noop is enough to turn off the notifications. But I agree that this needs to be documented a bit better in the notification dev ref and in the description of the notification_format config option.
1761405,2018-04-16 18:13:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561684"
1761405,2018-04-16 17:54:54 UTC,"> @Matt (comments#3): Actually nova skips the expensive part of the versioned payload generation if the driver is set to 'noop' [1][2]. So I think we are OK to just document the possible config a bit better.
"
1761405,2018-04-05 14:08:51 UTC,"I think this might be a duplicate, I'm pretty sure I've talked with gibi about this before."
1761405,2018-04-10 07:33:38 UTC,Indeed setting :
1761405,2018-04-06 06:01:32 UTC,"Hi,"
1761405,2018-04-05 14:26:24 UTC,"Can you test out the noop workaround suggested in comment 3? If that works for you, then I think this just becomes a docs fix in the nova notifications docs."
1761405,2018-04-05 14:25:50 UTC,One thing I think you can do as a workaround is to set the notification driver to 'noop':
1761405,2018-04-05 14:09:29 UTC,"There are other services that rely on nova notifications beyond ceilometer, like searchlight, designate and mistral, there might be others. But you might not be using any of those, so it is a valid request to be able to disable notifications altogether."
1761405,2018-04-17 08:46:54 UTC,"Reviewed:  https://review.openstack.org/561684
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=11528966ba000addde5416f085332e0d39c46588
Submitter: Zuul
Branch:    master"
1761406,2018-08-08 13:07:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761406,2018-04-05 08:27:14 UTC,"StacktraceTop:
 spice_logv (log_domain=0x7fdf72e4b195 ""Spice"", args=0x7fdf655fe5c0, format=0x7fdf72e4b09e ""assertion `%s' failed"", function=0x7fdf72e556a0 <__FUNCTION__.15482> ""red_get_clip_rects"", strloc=0x7fdf72e5512d ""red-parse-qxl.c:352"", log_level=G_LOG_LEVEL_ERROR) at log.c:178
 spice_log (log_level=log_level@entry=G_LOG_LEVEL_ERROR, strloc=strloc@entry=0x7fdf72e5512d ""red-parse-qxl.c:352"", function=function@entry=0x7fdf72e556a0 <__FUNCTION__.15482> ""red_get_clip_rects"", format=format@entry=0x7fdf72e4b09e ""assertion `%s' failed"") at log.c:196
 red_get_clip_rects (slots=slots@entry=0x55f8ffe1cf60, group_id=group_id@entry=1, addr=<optimized out>) at red-parse-qxl.c:352
 red_get_clip_ptr (qxl=0x7fded4814a2f, red=0x7fdf5c0d77d0, group_id=1, slots=0x55f8ffe1cf60) at red-parse-qxl.c:1020
 red_get_native_drawable (flags=0, addr=<optimized out>, red=0x7fdf5c0d7780, group_id=1, slots=0x55f8ffe1cf60) at red-parse-qxl.c:1049"
1761406,2018-04-06 08:51:43 UTC,Sig 5 is a Trap.
1761411,2018-04-05 10:24:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761425,2018-04-10 04:28:12 UTC,Look like it's the same in create_vnffg()
1761425,2020-05-21 05:28:14 UTC,"When I checked the latest source code, it seems that ns_info is being used as follows.
Therefore, I will change the status of this bug."
1761433,2018-04-12 08:53:23 UTC,"3.13.0-145.194~precise2 - generic
Regression test CMPL."
1761433,2018-04-17 10:56:30 UTC,Cert. does not cover the ESM kernel.
1761433,2018-04-19 15:09:06 UTC,ESM kernels are not covered by ADT tests. Setting automated-testing to 'Invalid'.
1761433,2018-04-23 10:01:37 UTC,The package has been published and the bug is being set to Fix Released
1761439,2018-04-23 11:31:43 UTC,The package has been published and the bug is being set to Fix Released
1761439,2018-04-10 09:11:36 UTC,"4.4.0-1017.17 - aws
Regression test CMPL."
1761439,2018-04-23 09:05:57 UTC,This bug was fixed in the package linux-aws - 4.4.0-1017.17
1761443,2018-04-23 09:06:26 UTC,This bug was fixed in the package linux-aws - 4.4.0-1055.64
1761443,2018-04-23 15:00:42 UTC,The package has been published and the bug is being set to Fix Released
1761443,2018-04-10 05:55:58 UTC,"4.4.0-1055.64 - aws
Regression test CMPL."
1761444,2018-04-17 19:56:40 UTC,Hardware Certification have begun testing this -proposed kernel.
1761444,2018-04-19 18:39:37 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/euclid/4.4.0-9026.28/euclid-proposed-published.html"
1761444,2018-04-23 09:06:48 UTC,This bug was fixed in the package linux-euclid - 4.4.0-9026.28
1761444,2018-04-23 11:32:38 UTC,The package has been published and the bug is being set to Fix Released
1761445,2018-04-17 07:20:03 UTC,"4.4.0-1021.26 - kvm
Regression test CMPL."
1761445,2018-04-23 09:07:04 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1021.26
1761445,2018-04-23 12:01:48 UTC,The package has been published and the bug is being set to Fix Released
1761446,2018-04-23 09:07:29 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1087.95
1761446,2018-04-23 12:32:00 UTC,The package has been published and the bug is being set to Fix Released
1761446,2018-04-19 17:04:14 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1087.95/raspi2-4.4-proposed-published.html"
1761446,2018-04-10 18:06:41 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/TasSnOLD/233-pi2-kernel-440-108795-52"
1761446,2018-04-19 17:04:01 UTC,Hardware Certification have begun testing this -proposed kernel.
1761458,2018-04-09 09:10:21 UTC,Hardware Certification have begun testing this -proposed kernel.
1761458,2018-04-17 19:56:17 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.13.0-1017.18/raspi2-4.13-proposed-published.html"
1761458,2018-04-23 12:41:15 UTC,This bug was fixed in the package linux-raspi2 - 4.13.0-1017.18
1761458,2018-04-23 14:02:10 UTC,The package has been published and the bug is being set to Fix Released
1761461,2018-04-10 06:16:00 UTC,"4.13.0-1013.17 - gcp
Regression test CMPL."
1761461,2018-04-23 12:40:18 UTC,This bug was fixed in the package linux-gcp - 4.13.0-1013.17
1761461,2018-04-23 15:02:31 UTC,The package has been published and the bug is being set to Fix Released
1761462,2018-04-09 20:29:14 UTC,Hardware Certification have begun testing this -proposed kernel.
1761462,2018-04-18 23:29:56 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.13.0-39.44~16.04.1/xenial-4.13-proposed-published.html"
1761462,2018-04-20 11:31:37 UTC,"4.13.0-39.44~16.04.1 - lowlatency
Regression test CMPL."
1761462,2018-04-23 12:39:47 UTC,This bug was fixed in the package linux-hwe - 4.13.0-39.44~16.04.1
1761462,2018-04-23 14:03:52 UTC,The package has been published and the bug is being set to Fix Released
1761463,2018-05-08 18:16:13 UTC,This change was made by a bot.
1761467,2018-04-05 12:27:42 UTC,You can check some guide in here http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd03/tosca-nfv-v1.0-csd03.html#_Toc447714731
1761467,2018-04-06 01:44:24 UTC,Hi Phuoc. Thanks for the link. I meant a guide in the Tacker docs like these for VNFD and VNFFGD:
1761474,2018-04-05 11:34:19 UTC,"On Thu, 05 Apr 2018 11:04:10 -0000, latimerio wrote:"
1761483,2018-04-10 19:05:39 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1761483,2019-07-22 14:22:50 UTC,This is now fixed on eoan and disco (which have firmware versions 20190215) and can boot on 3B+ and CM3+. Hopefully Adam won't mind if I hijack his bug to SRU the changes back to bionic so it can boot on these too :)
1761483,2019-07-22 15:39:50 UTC,"Sponsored for bionic, waiting for SRU team approval. Note to SRU reviewers: this upload, along with the main firmware bump, also includes the addition of bluetooth firmware. This change, being part of the backport, has no effect on the images at all (so no risk of introducing a regression) but might be useful for the future when we decide to backport the bluetooth enablement pieces."
1761483,2019-07-22 18:41:15 UTC,"Hello Adam, or anyone else affected,"
1761483,2019-07-30 11:22:35 UTC,"Verification done with Pi 3B, 3B+, CM3, and CM3+. All went smoothly."
1761483,2019-07-30 16:18:45 UTC,This bug was fixed in the package linux-firmware-raspi2 - 1.20190215-0ubuntu0.18.04.1
1761483,2019-08-10 20:47:32 UTC,This latest update contained RaspberryPi2/3 GPU firmware and bootloaders failed to install on my Raspberry Pi 3B+ running Ubuntu 18.04. All other packages installed properly using the Software Updater program. I have tried to reinstall RaspberryPi2/3 GPU firmware and bootloaders several times and the results are always the same. The attached screenshot shows the details.
1761483,2019-08-11 07:24:20 UTC,@David that is a problem caused by a package installed from the Ubuntu Flavour Maker PPA. That ppa is maintained by Martin Wimpress and is used by his version of Ubuntu Mate for the pi.  He needs to solve it for Ubuntu mate users.  I suggest you raise a bug with him.
1761483,2019-08-11 07:28:53 UTC,Somebody has already done it bug 1839054.
1761483,2020-02-03 22:45:25 UTC,I got the same issues is there a fix? on raspberry pi 3 with ubuntu mate beta 1 18
1761483,2020-02-03 22:47:25 UTC,this is the error I get
1761483,2019-07-30 16:18:51 UTC,"The verification of the Stable Release Update for linux-firmware-raspi2 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1761487,2018-04-11 11:10:31 UTC,"Reviewed:  https://review.openstack.org/559111
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=587eb4303be65810133e88114106ee9019940118
Submitter: Zuul
Branch:    master"
1761487,2018-04-05 14:28:34 UTC,You don't have the [neutron] user credentials section of nova.conf configured:
1761487,2018-04-05 14:30:46 UTC,This could be an opportunity to put something more instructive in the logs when [neutron]auth_type is not set:
1761487,2018-04-05 14:32:50 UTC,I also noticed that the install guide isn't very clear on configuring nova.conf to set credentials for talking to neutron:
1761487,2018-04-05 15:12:43 UTC,I've re-opened and changed this to be a docs bug.
1761487,2018-04-05 15:27:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559111"
1761487,2018-04-05 15:53:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559115"
1761487,2018-04-05 18:11:27 UTC,"During installation I have followed documentation from this point:
https://docs.openstack.org/install-guide/environment-packages-ubuntu.html
I have found some errors in documentation or better to say wrong steps.
How and where can I report them?"
1761487,2018-04-06 18:55:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/559399"
1761487,2018-04-20 13:12:44 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1761487,2018-04-11 11:10:52 UTC,"Reviewed:  https://review.openstack.org/559115
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a6d9655d7806bade90cffcd107cd1e9ca1861f0f
Submitter: Zuul
Branch:    master"
1761487,2018-04-11 11:11:21 UTC,"Reviewed:  https://review.openstack.org/559399
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b752717f253f0c3eb45cc7ae5530bc8f295b4c22
Submitter: Zuul
Branch:    master"
1761489,2018-12-19 15:11:40 UTC,"Feature request, will add when convenient and will require web UI and snapcraft additions."
1761497,2018-04-05 13:25:27 UTC,"We discussed on IRC, but I have to admit I'm unsure what to do on this.
Especially since different hosts with same SW levels are exposing different behavior."
1761497,2018-06-05 04:17:54 UTC,[Expired for virt-manager (Ubuntu) because there has been no activity for 60 days.]
1761497,2019-03-29 08:42:26 UTC,Switching from spice to VNC works around the issue.
1761497,2019-03-29 14:24:16 UTC,I tried spicy from the package spice-client-gtk and doesn't have this problem. So this issue is only with the spice client in libvirt.
1761497,2019-04-01 07:22:43 UTC,"Common misunderstanding :-)
s/with the spice client in libvirt/with the spice client in virt-manager/
Which are different sources/projects."
1761503,2019-09-30 07:06:09 UTC,"Most likely this was intended to be based on the timestamp, e.g. if more than 5 minutes since last heartbeat, mark it as DOWN. This could probably be done on either the cli side (e.g. as part of python-designateclient) or within designate central."
1761503,2019-09-25 07:58:29 UTC,The resolution of this bug is blocking the implementation of a smart check for the Designate services in the openstack-service-checks charm
1761504,2018-04-05 13:37:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559087"
1761504,2018-04-06 17:18:04 UTC,"Reviewed:  https://review.openstack.org/559087
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=b65e9a1fe8c8b0deedc342df3cb31df684276aa9
Submitter: Zuul
Branch:    master"
1761504,2021-02-17 17:07:18 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1761532,2019-01-25 14:50:22 UTC,"I think I've fixed this upstream (https://gitlab.gnome.org/GNOME/nautilus/merge_requests/335) but it has not been released in 3.30.x branches, while will be fixed in first 3.31.x we release."
1761532,2018-04-05 15:56:17 UTC,"StacktraceTop:
 nautilus_query_matches_string (query=0x0, string=0x7f62f0059180 ""2015-02-27 12.46.21.jpg"") at ../src/nautilus-query.c:370
 recent_thread_func (user_data=<optimized out>) at ../src/nautilus-search-engine-recent.c:148
 g_thread_proxy (data=0x7f62f002ae80) at ../../../../glib/gthread.c:784
 start_thread (arg=0x7f62f70c5700) at pthread_create.c:463
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95"
1761532,2019-01-25 14:10:29 UTC,"Still happening with 3.30 in Fedora, https://retrace.fedoraproject.org/faf/reports/2418334/"
1761532,2019-01-25 14:11:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1761538,2018-04-05 19:45:14 UTC,"This likely is more related to RabbitMQ (and as fungi pointed out, should probably be noted in OSSN) if it has a security impact on OpenStack as a whole, rather than specifically keystone."
1761538,2018-04-05 17:45:33 UTC,"If this behavior is configurable or other mitigation can be devised, or if it gets patched upstream in rabbitmq, then a security note (not advisory) may be appropriate to let operators know about the risk and what they can do."
1761538,2018-04-05 16:22:43 UTC,"Archana, I believe the right place to open this bug is at https://github.com/rabbitmq/rabbitmq-server/issues/new as the logs mentioned here has nothing to do with Keystone."
1761538,2018-04-05 16:25:41 UTC,But logging this Erlang Cache could have a security impact on OpenStack
1761544,2018-04-06 22:24:21 UTC,"Reviewed:  https://review.openstack.org/559273
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=66e03a3af213d496c89fef7ea8566e8ff7718315
Submitter: Zuul
Branch:    stable/queens"
1761544,2018-04-24 18:11:15 UTC,This issue was fixed in the openstack/glance 16.0.1 release.
1761544,2018-04-05 17:24:32 UTC,Change proposed to master: https://review.openstack.org/558187
1761544,2018-04-06 05:49:34 UTC,"Reviewed:  https://review.openstack.org/558187
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=c611c92dc164123fefd49ba5e9004e73d336ac63
Submitter: Zuul
Branch:    master"
1761544,2018-04-06 06:13:36 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/559273"
1761544,2018-04-19 14:01:57 UTC,This issue was fixed in the openstack/glance 17.0.0.0b1 development milestone.
1761555,2018-04-19 14:29:15 UTC,"What I noticed is that when there are two tenant network ports attached to a router (no VMs) and one tenant network gets removed, notifications are sent out correctly to L3 agents."
1761555,2018-04-10 09:05:22 UTC,"There were no instance ports there - only a distributed router port, centralized SNAT port and DHCP ports."
1761555,2018-04-10 00:21:31 UTC,"When you say that no 'notifications' are sent to the l3-agent when the subnet is removed, where there any active 'Service ports' ( VM ports) in the compute Node, when you tried to remove the Subnet."
1761555,2018-04-06 06:02:04 UTC,I think we should take a single case here to see what is going wrong.
1761555,2018-04-06 22:09:40 UTC,"Yes, you are right, let's solve the problem with notifications to l3 agents first."
1761557,2021-02-05 11:42:30 UTC,The bug fix is almost 3 years old. Can anybody apply it?
1761557,2018-04-10 12:27:58 UTC,apport information
1761557,2021-02-05 11:41:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761557,2018-04-10 12:28:03 UTC,apport information
1761557,2018-04-10 12:28:01 UTC,apport information
1761557,2018-04-10 12:28:00 UTC,apport information
1761557,2018-04-10 12:27:59 UTC,apport information
1761557,2018-04-10 12:27:57 UTC,apport information
1761557,2018-04-10 12:27:56 UTC,apport information
1761557,2018-04-10 12:27:54 UTC,apport information
1761557,2018-04-10 12:27:53 UTC,apport information
1761557,2018-04-10 12:27:52 UTC,apport information
1761557,2018-04-10 12:27:51 UTC,apport information
1761557,2018-04-10 12:27:50 UTC,apport information
1761557,2018-04-10 12:27:49 UTC,apport information
1761557,2018-04-10 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1761557,2018-04-10 12:27:55 UTC,apport information
1761565,2018-05-14 10:50:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761565,2018-04-05 19:00:30 UTC,"Так же При обработке следующих пакетов произошли ошибки:
 libmetacity1:amd64
 libgail-3-0:amd64
 libcompizconfig0:amd64
 locales"
1761568,2018-04-05 19:13:31 UTC,"~ $ lsb_release -a; uname -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 17.10
Release:	17.10
Codename:	artful
Linux gigbib 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1761571,2020-10-09 18:44:52 UTC,There's a new allocate-public-ip constraint. Set to false to avoid creating a public ip.
1761573,2018-04-12 22:00:49 UTC,"On Thu, Apr 12, 2018 at 4:36 PM, Andres Rodriguez
<email address hidden> wrote:

> Ryan,
>
> Maybe I’m missing something but I’m wondering How Will installing Xenial
> and upgrading cloud-initramfs help here when the system boots of the kernel
> and not an ephemeral image/network?
"
1761573,2018-04-16 15:36:42 UTC,"I can no longer deploy Xenial on the same hardware. I see the same issues as with Bionic (Note that the system PXE boots just fine, loads the ephemeral env, but gets stuck in the same place)."
1761573,2018-08-11 12:28:18 UTC,I'm also running into this issue..
1761573,2018-04-12 21:36:29 UTC,"Ryan,"
1761573,2018-08-12 10:42:34 UTC,"After another edit, namely a symlink of cloud-init.target into the multi-user.target.wants directory it finally boots up with cloud-init and everything work as expected."
1761573,2018-08-13 14:19:37 UTC,"Hi Daniel,"
1761573,2018-10-31 12:27:07 UTC,We are hitting the same problem while booting VM with cloud-init configuration disk (iso image). Network interface will not configure itself with dhcp.
1761573,2018-08-12 10:28:37 UTC,"Creating /etc/systemd/network/default.network with contents:
```
[Match]
Type=en*"
1761573,2018-04-12 19:47:10 UTC,"Hrm, You could install Xenial and then upgrade to bionic's cloud-init ramfs; but keep the 4.4 kernel.  This would allow us to test the initramfs code vs. the hardware.  If 4.4 + cloud-initramfs-tools 0.40 works, then you likely have an issue with the kernel + the e1000e driver to sort."
1761573,2018-04-12 19:41:49 UTC,full log
1761573,2018-04-12 18:58:47 UTC,Can you paste the whole log?
1761573,2018-04-12 18:43:36 UTC,"So it seems that the latest 4.15 kernel in -updates has indeed made a difference, however, it hasn't really solve the problem. [1] shows the new issue. It doesn't seem to be  driver problem and DHCP is working fine, provided that otherwise, the machine wouldn't have even gotten to this point."
1761573,2018-04-05 20:49:59 UTC,Possibly related:
1761573,2018-04-05 20:46:04 UTC,"So, what's happening here is the BOOTIF parameter specifies a MAC of a device, but that device is *not* found; then we see the errors here."
1761573,2018-04-05 20:19:52 UTC,"Also can you provide a list of interfaces and their mac address values?  Maybe the commissioning, lshw output?"
1761573,2018-04-05 20:17:11 UTC,Can you attach the xenial log that boots just fine on the same hardware?
1761573,2018-04-12 19:42:19 UTC,"The hardware is remote, the only thing I could do is deploy Xenial and dist-upgrade to Bionic if that helps ?"
1761575,2018-11-14 03:00:07 UTC,This change was made by a bot.
1761577,2018-05-04 13:46:07 UTC,"I have the same issue on Google cloud.
my constrains --constraints ""cores=2 mem=2G"" are ignored"
1761591,2018-04-06 06:12:24 UTC,Yes your understanding is right. Today there is a tight dependency on the SNAT namespace when a gateway is attached.
1761591,2018-04-06 06:13:41 UTC,Can you check if the SNAT flow iptable rules in the SNAT namespace exists when configured for 'disable_snat'?
1761591,2018-04-06 11:50:41 UTC,"Yes, they do http://paste.openstack.org/show/718590/"
1761591,2018-06-14 14:54:05 UTC,"If the SNAT rule is seen in iptables, then that should be fixed first."
1761593,2018-05-24 13:46:03 UTC,"Alberto, can you have a look to see if there's anything to be done for -340 in bionic please?"
1761593,2018-05-24 14:49:45 UTC,@Iain: a backport is in the plans.
1761593,2018-05-17 15:30:59 UTC,This bug was fixed in the package nvidia-graphics-drivers-340 - 340.106-0ubuntu5
1761593,2018-09-12 11:34:24 UTC,"Hello Kev, or anyone else affected,"
1761593,2018-10-01 07:58:54 UTC,"The verification of the Stable Release Update for nvidia-graphics-drivers-340 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1761593,2018-09-20 06:45:36 UTC,What packages and versions have been tested during verification?
1761593,2018-10-01 07:58:28 UTC,"Seeing the urgency of the package being blocked in -proposed, I'll be releasing it conditionally without test version number."
1761593,2018-05-15 12:48:13 UTC,This bug was fixed in the package nvidia-graphics-drivers-390 - 390.48-0ubuntu4
1761593,2018-09-12 13:58:33 UTC,@tjaalton - thanks - all done and tagged
1761593,2018-05-14 15:09:39 UTC,"@Doug: I'm working on the meta-package part for LP: #1753333 , this is a separate bug report, only about the blacklist file."
1761593,2018-10-01 07:58:48 UTC,This bug was fixed in the package nvidia-graphics-drivers-340 - 340.107-0ubuntu0.18.04.1
1761593,2018-04-09 20:44:10 UTC,The real answer here is we should rm_conffile those files in /etc and ship them in /lib/modprobe.d instead.
1761593,2018-04-09 20:37:26 UTC,"This is very much a bug in nvidia-graphics-drivers-340.  One can debate if software-properties should or shouldn't purge (though traditionally, the argument was that silent frontends shouldn't purge because the user hasn't explicitly asked for that), but if a removed package's unpurged conffiles cause the system to misbehave, that package needs to be rethought to avoid that situation."
1761593,2018-04-09 20:35:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761593,2018-04-06 18:57:07 UTC,Just booted xubuntu 17.10.1 iso - installed nvidia with software-properties - additional drivers.
1761593,2018-04-06 17:15:20 UTC,Rechecked this (multiple times)
1761593,2018-04-06 16:29:57 UTC,apport-collect failed to collect new information for this bug as nvidia is no longer installed.
1761593,2018-04-06 15:46:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761593,2018-04-06 15:45:26 UTC,"I've had exactly the same problem described above. Installed Nvidia drivers via via Additional Drivers and all was working fine.
After that I decided to remove the Nvidia drivers and rebooted the laptop. My screen resolution was set as 640x480, without any possibility of changing it.
Asking for help, on #ubuntu+1 @ Freenode, someone told me to check /etc/modprobe.d for a nvidia conf file. I've done that and it was there.
Deleting the file and rebooting the laptop solved the issue."
1761593,2018-04-06 15:35:39 UTC,someone turned up in #ubuntu+1 - they had nvidia-340.conf left after uninstallation
1761593,2018-05-10 00:02:29 UTC,"As stated in duped bug removing nvidia drivers (nvidia-390 here) via software-properties only removes the driver meta package so actually nothing is removed.
(- and of course /etc/modprobe.d/nvidia-graphics-drivers.conf will still  be there .."
1761602,2018-04-09 02:10:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761602,2020-10-22 20:00:32 UTC,the package is removed from Ubuntu
1761606,2020-05-03 06:35:56 UTC,"This happens too in Linux Mint MATE 19.3 (in my case 64bit) Stopping and starting the applet does not help but logging off and back on again soves this iommediately. It occurs since the change from the old separated applets to the ""unified XApp Status Applet"" combines the status of updates and network. Simulating it is hardly possible, it's more a gamble."
1761606,2019-11-21 06:30:42 UTC,"In Ubuntu MATE 18.04, this happens in e.g. one out of 10 logins (not just in the Live CD)."
1761606,2019-11-12 00:06:39 UTC,it's not a bug in nmapplet if lubuntu includes 2 indicators
1761606,2019-11-04 16:38:41 UTC,"Exec=/bin/bash -c ""sleep 2 && nm-applet"""
1761606,2019-11-04 14:30:12 UTC,Lubuntu 18.04.3 LTS 64 bit fresh install & dist-upgrade on:
1761606,2019-11-02 15:48:52 UTC,"Thanks to Alkis Georgopoulos @alkisg for the hint, `Exec=nm-applet --indicator` indeed does work for me in LUbuntu 18.0.4."
1761606,2019-04-04 05:07:57 UTC,"Xubuntu 18.04.2
Two network icons appear at start up but not every time.
The 1st icon appears because Status Notifier plugin is enabled.
The 2nd icon appears because nm applet and network are included in Notification area and if I choose to be hidden only the arrow appears in panel instead of the 2nd icon.
Under 16.04 there was no problem ever.
xfce-panel -r solves the problem but not permanently.
Any idea on this issue?"
1761606,2019-03-13 22:28:48 UTC,Xubuntu 18.04. In the settings panel remove the Status Notifier Plugin. Only one network icon will remain.
1761606,2019-02-16 17:41:36 UTC,"Two network & volume indicators also on XFCE panel.
No change even after resetting the panel (xfce4-panel -r).
I guess two is better than none. ;-)"
1761606,2018-12-12 08:49:31 UTC,I tried `Exec=nm-applet --indicator` on a Lubuntu 18.04 w/ current updates. After reboot still 2 icons were shown on the panel.
1761606,2018-12-02 08:14:49 UTC,"And another test would be:
In /etc/xdg/autostart/nm-applet.desktop
to replace:
Exec=nm-applet
with:
Exec=nm-applet --indicator"
1761606,2018-12-02 08:11:20 UTC,"It appears to be a race condition, like maybe nm-applet first registers itself in the tray, then indicator-applet-complete is loaded, and it shows nm-applet a second time. While if nm-applet starts after indicator-applet-complete has finished loading, it doesn't register itself in the tray, only in the indicator-applet-complete itself."
1761606,2018-11-06 13:48:39 UTC,In Xubuntu this may be fixable by removing the indicator-application package:
1761606,2019-12-18 07:20:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761606,2018-09-10 05:53:37 UTC,"This happens on Xubuntu and UbuntuMATE variants of 18.04.01 LTS too, its high time that this needs a resolution."
1761606,2018-09-25 20:08:02 UTC,Title of this bug is:
1761606,2018-04-05 21:54:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761606,2018-04-05 22:05:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1761606,2018-04-13 10:34:52 UTC,"Since the older bug (1685502) was marked duplicate in favor of this one, I'll just copy a few related links (aside from the listed duplicates) that might be of interest:"
1761606,2018-04-29 20:05:34 UTC,"the same problem is present in xubuntu 18.04LTS, two wifi icons is displayed in the panel"
1761606,2018-04-11 22:04:06 UTC,"Confirmed on Lubuntu 18.04 32bit @ 12/4/18 on daily iso, after a succesfull install
2 wifi icons showing at right down corner"
1761606,2018-07-12 19:39:19 UTC,"Same here, on an installed Xubuntu 18.04"
1761606,2018-07-29 22:19:43 UTC,"I've got the same problem in Xubuntu 18.04. Two network icons appear in the panel.
When I restart the Xfce Panel (xfce4-panel --restart), one of the two duplicate icons goes away but it comes back especially when I resume the system after suspend."
1761606,2018-08-13 09:37:48 UTC,"Also present on Lubuntu 18.04 (from a 16.04 upgrade, at least)."
1761606,2018-08-13 09:39:57 UTC,"Maybe an hint:
  - The first network icon has no sections horizontal bar UI-delimiters (e.g. between the 'Wifi' and 'Mobile broadband' sections)
  - The second network icon has those UI-delimiters"
1761606,2018-05-01 20:42:57 UTC,"Occurs for me on live session and installed versions of release Xubuntu 18.04 Bionic Beaver. Two network icons are displayed, both functional."
1761615,2018-11-19 21:31:49 UTC,Confirmed on EG 3-2-0
1761615,2020-10-22 12:45:43 UTC,I have a branch that works for me in removing item tag mappings upon item deletion:
1761615,2020-10-30 16:12:36 UTC,"I have tested this code and consent to signing off on it with my name, Beth Willis and my email address, <email address hidden>."
1761626,2018-04-09 00:47:13 UTC,"I'm not even remotely sure about things here, so some raw notes:"
1761626,2018-07-24 09:32:27 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1761626,2018-04-07 03:48:55 UTC,"I can test earlier mainlines, but keep in mind that ppc64el is very slow on my home qemu setup (note ""only"" ""very slow""; ppc64 is ""amazingly slow"", presumably due to endian swapping).  Does Kernel have a POWER8 playground machine, if it comes to bisect compiling?"
1761626,2018-04-07 05:08:53 UTC,"4.8.0 works, 4.9.0 panics.  I'll see about bisecting."
1761626,2018-04-06 00:16:49 UTC,Same result with 4.16.0-041600-generic and 4.13.0-38-generic
1761626,2018-04-05 23:30:06 UTC,This change was made by a bot.
1761626,2018-04-06 18:16:01 UTC,"We should probably also report this upstream, since it still affects current mainline.  https://wiki.ubuntu.com/Bugs/Upstream/kernel"
1761629,2018-06-20 03:47:42 UTC,"Hello,"
1761629,2018-06-20 07:53:57 UTC,Hello
1761629,2018-06-20 08:38:24 UTC,Hello
1761629,2018-06-25 09:24:18 UTC,"The verification of the Stable Release Update for heat has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1761629,2018-06-25 09:34:17 UTC,This bug was fixed in the package heat - 1:10.0.1-0ubuntu2
1761629,2018-06-25 09:48:06 UTC,This bug was fixed in the package heat - 1:9.0.4-0ubuntu2
1761629,2018-06-25 09:49:01 UTC,This bug was fixed in the package heat - 1:6.1.2-0ubuntu1.1
1761629,2018-06-25 12:51:03 UTC,The verification of the Stable Release Update for heat has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1761629,2018-06-25 12:51:04 UTC,"This bug was fixed in the package heat - 1:10.0.1-0ubuntu2~cloud0
---------------"
1761629,2018-06-25 12:53:14 UTC,The verification of the Stable Release Update for heat has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1761629,2018-06-25 12:55:38 UTC,The verification of the Stable Release Update for heat has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1761629,2018-06-25 12:55:39 UTC,"This bug was fixed in the package heat - 1:8.0.6-0ubuntu1~cloud1
---------------"
1761629,2018-06-25 12:56:52 UTC,The verification of the Stable Release Update for heat has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1761629,2018-06-25 12:56:53 UTC,"This bug was fixed in the package heat - 1:6.1.2-0ubuntu1.1~cloud0
---------------"
1761629,2018-08-08 22:51:57 UTC,"Reviewed:  https://review.openstack.org/562887
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=c4968824dbeaad849d16482cc7a6234e862714c6
Submitter: Zuul
Branch:    stable/pike"
1761629,2018-09-04 19:55:18 UTC,This issue was fixed in the openstack/heat 9.0.5 release.
1761629,2018-09-04 19:56:03 UTC,This issue was fixed in the openstack/heat 10.0.2 release.
1761629,2018-06-18 14:02:46 UTC,"Hello Seyeong, or anyone else affected,"
1761629,2018-10-03 20:02:35 UTC,This landed upstream in heat but I think heat is now using storyboard for bug tracking. I think the upstream task can be moved to fix released.
1761629,2018-06-18 14:01:46 UTC,"Hello Seyeong, or anyone else affected,"
1761629,2018-06-25 12:53:16 UTC,"This bug was fixed in the package heat - 1:9.0.4-0ubuntu2~cloud0
---------------"
1761629,2018-06-18 05:17:30 UTC,Hello
1761629,2018-06-18 13:56:47 UTC,"Hello Seyeong, or anyone else affected,"
1761629,2018-04-05 23:57:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559195"
1761629,2018-04-19 19:24:09 UTC,This issue was fixed in the openstack/heat 11.0.0.0b1 development milestone.
1761629,2018-04-20 01:20:05 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/562887"
1761629,2018-04-24 08:29:54 UTC,"The attachment ""lp1761629_xenial.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1761629,2018-05-15 16:17:10 UTC,"Reviewed:  https://review.openstack.org/562888
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=b76d18730d1e4f110d720cfaba980b4cda9e561c
Submitter: Zuul
Branch:    stable/queens"
1761629,2018-05-30 19:19:44 UTC,"Seyeong, Thanks for the patches. I've uploaded everything for SRU Team review except for xenial(mitaka) and ocata. Those are failing to build due to unit test issues. Can you take a look?"
1761629,2018-05-31 13:07:02 UTC,"Thanks for checking it corey,"
1761629,2018-04-20 01:20:34 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/562888"
1761629,2018-05-31 18:08:54 UTC,Thanks Seyeong. I've uploaded this for ocata and xenial as well.
1761629,2018-05-31 17:06:12 UTC,"Hello Seyeong, or anyone else affected,"
1761629,2018-06-16 14:19:40 UTC,Hello
1761629,2018-06-14 22:10:00 UTC,This was also accepted into Xenial although there is no comment about that acceptance.
1761629,2018-06-14 22:02:57 UTC,"Hello Seyeong, or anyone else affected,"
1761629,2018-06-18 03:40:14 UTC,Hello
1761629,2018-06-14 22:01:56 UTC,"Hello Seyeong, or anyone else affected,"
1761629,2018-06-09 06:17:36 UTC,Hello
1761629,2018-06-04 19:03:52 UTC,We'll have to wait for the previous heat upload to get tested and released into bionic-updates.
1761639,2018-04-06 03:16:03 UTC,The hpilo module has to be added to the images generated by maas-images. Closing as invalid for MAAS.
1761640,2018-04-06 05:36:05 UTC,"maas-run-remote-scripts is executed by cloud-init, which is executed by systemd. Your shell normally sets $HOME as well as other environment variables. Since no process is started by a shell $HOME is never defined. We could either set $HOME manually in maas-run-remote-scripts or execute all scripts through bash."
1761640,2019-09-19 11:58:04 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1761672,2018-04-06 06:42:28 UTC,"StacktraceTop:
 Exiv2::ValueType<std::pair<unsigned int, unsigned int> >::toFloat (this=0x564bc823a480, n=0) at ../include/exiv2/value.hpp:1695
 (anonymous namespace)::toVariantDouble (value=...) at ./src/extractors/exiv2extractor.cpp:98
 (anonymous namespace)::toVariant (type=QVariant::Double, value=...) at ./src/extractors/exiv2extractor.cpp:128
 KFileMetaData::Exiv2Extractor::add (this=this@entry=0x564bc806bd50, result=result@entry=0x7fff3dfab580, data=..., prop=prop@entry=KFileMetaData::Property::PhotoFocalLength, name=name@entry=0x7f4b5361c2e0 ""Exif.Photo.FocalLength"", type=type@entry=QVariant::Double) at ./src/extractors/exiv2extractor.cpp:225
 KFileMetaData::Exiv2Extractor::extract (this=0x564bc806bd50, result=0x7fff3dfab580) at ./src/extractors/exiv2extractor.cpp:182"
1761672,2018-04-19 09:11:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761672,2020-04-15 11:31:23 UTC,Still happens after each startup.
1761677,2018-04-06 20:31:21 UTC,Another caveat is about format for neutron messages. Here are a few fields [1]. So the default format will cause an error for 'handler:neutron_floatingip'.
1761681,2018-05-06 22:36:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761682,2018-04-08 11:05:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761682,2018-04-08 11:09:25 UTC,The issue occurred for me when the latest set of updates were applied. Just trying to remove avahi-dnsconfd give an error about the pre-removal script failing. Here is the output from 'apt remove avahi-dnsconfd'
1761684,2018-10-08 11:19:07 UTC,This bug was fixed in the package ubuntu-themes - 16.10+18.10.20181005-0ubuntu1
1761684,2018-10-08 13:43:26 UTC,"Hello Didier, or anyone else affected,"
1761684,2018-10-18 10:14:06 UTC,"$ apt-cache policy light-themes
light-themes:
  Installato: 16.10+18.04.20181004-0ubuntu1
  Candidato:  16.10+18.04.20181004-0ubuntu1"
1761684,2018-10-22 10:34:50 UTC,Fine also with
1761684,2018-10-23 23:56:08 UTC,This bug was fixed in the package ubuntu-themes - 16.10+18.04.20181005-0ubuntu1
1761684,2018-10-23 23:56:35 UTC,"The verification of the Stable Release Update for ubuntu-themes has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1761684,2018-04-09 03:07:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761686,2018-05-08 18:16:30 UTC,This change was made by a bot.
1761691,2018-05-23 15:22:35 UTC,"Reviewed:  https://review.openstack.org/570084
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=3b503219acc2a25177c35886bbea7899efe68a7c
Submitter: Zuul
Branch:    master"
1761691,2018-05-23 00:37:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/570084"
1761691,2018-04-25 00:07:57 UTC,"Reviewed:  https://review.openstack.org/561210
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=2f061ca51f4af69efbb200e318cf269faffe93af
Submitter: Zuul
Branch:    master"
1761691,2018-04-24 14:17:47 UTC,"Reviewed:  https://review.openstack.org/561209
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=da2a8835dd4a15b64791b034ad1d96dca69055fb
Submitter: Zuul
Branch:    master"
1761691,2018-04-13 13:28:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561225"
1761691,2018-04-24 18:18:35 UTC,"Reviewed:  https://review.openstack.org/561225
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=89683e8fc4ff0000c0408cab99b377841358747b
Submitter: Zuul
Branch:    master"
1761693,2018-04-07 10:42:16 UTC,apport information
1761693,2018-04-07 10:43:42 UTC,"I am making a little Logbook and picture data about the problem and i will put it here later. Anyway, i run apport-collect 1761693 as requested and the data is being collected and I will send it to you."
1761693,2018-04-07 11:46:19 UTC,The debug works like :
1761693,2018-04-07 14:24:29 UTC,I think i solve the problem using this process:
1761693,2018-04-08 08:35:43 UTC,"After 24h i can confirm that my solution is not stable. If i turn off the machine the problem is back and this time is not speed in question but the network manager that will ""collapse""."
1761693,2018-04-08 08:59:16 UTC,"[  140.014404] ---[ end trace 06d9b1a38644b1a5 ]---
[  146.093218] r8822be: [ERR]Pwr cmd polling timeout!!
[  146.093228] r8822be: [ERR]Pwr cmd offset : 5!!
[  146.093231] r8822be: [ERR]Pwr cmd value : 0!!
[  146.093235] r8822be: [ERR]Pwr cmd msk : 2!!
[  146.093238] r8822be: [ERR]Read offset = 5 value = 2!!
[  146.093242] r8822be: [Err]pwr sub seq parser fail, status = 0x28!
[  146.093245] r8822be: Handle power off cmd error
[  159.806294] r8822be: halmac_init_hal failed
[  159.806317] r8822be: halmac_init_hal failed
[  159.806333] r8822be: halmac_init_hal failed
[  159.806350] r8822be: halmac_init_hal failed
[  159.806366] r8822be: halmac_init_hal failed
[  159.806381] r8822be: halmac_init_hal failed
[  159.806396] r8822be: halmac_init_hal failed
[  159.806411] r8822be: halmac_init_hal failed
[  159.806427] r8822be: halmac_init_hal failed
[  159.806442] r8822be: halmac_init_hal failed
[  165.923616] r8822be: [ERR]Pwr cmd polling timeout!!
[  165.923626] r8822be: [ERR]Pwr cmd offset : 5!!
[  165.923630] r8822be: [ERR]Pwr cmd value : 0!!
[  165.923633] r8822be: [ERR]Pwr cmd msk : 2!!
[  165.923637] r8822be: [ERR]Read offset = 5 value = 2!!
[  165.923640] r8822be: [Err]pwr sub seq parser fail, status = 0x28!
[  165.923644] r8822be: Handle power off cmd error
[  198.838942] r8822be: halmac_init_hal failed
[  198.838966] r8822be: halmac_init_hal failed
[  198.838982] r8822be: halmac_init_hal failed
[  198.838997] r8822be: halmac_init_hal failed
[  198.839013] r8822be: halmac_init_hal failed
[  198.839029] r8822be: halmac_init_hal failed
[  198.839044] r8822be: halmac_init_hal failed
[  198.839060] r8822be: halmac_init_hal failed
[  198.839076] r8822be: halmac_init_hal failed
[  198.839091] r8822be: halmac_init_hal failed
[  204.947841] r8822be: [ERR]Pwr cmd polling timeout!!
[  204.947851] r8822be: [ERR]Pwr cmd offset : 5!!
[  204.947854] r8822be: [ERR]Pwr cmd value : 0!!
[  204.947858] r8822be: [ERR]Pwr cmd msk : 2!!
[  204.947861] r8822be: [ERR]Read offset = 5 value = 2!!
[  204.947864] r8822be: [Err]pwr sub seq parser fail, status = 0x28!
[  204.947868] r8822be: Handle power off cmd error
[  262.061429] r8822be: halmac_init_hal failed
[  262.061481] r8822be: halmac_init_hal failed
[  262.061524] r8822be: halmac_init_hal failed
[  262.061568] r8822be: halmac_init_hal failed
[  262.061607] r8822be: halmac_init_hal failed
[  262.061646] r8822be: halmac_init_hal failed
[  262.061685] r8822be: halmac_init_hal failed
[  262.061728] r8822be: halmac_init_hal failed
[  262.061767] r8822be: halmac_init_hal failed
[  262.061807] r8822be: halmac_init_hal failed
[  268.168199] r8822be: [ERR]Pwr cmd polling timeout!!
[  268.168209] r8822be: [ERR]Pwr cmd offset : 5!!
[  268.168212] r8822be: [ERR]Pwr cmd value : 0!!
[  268.168216] r8822be: [ERR]Pwr cmd msk : 2!!
[  268.168219] r8822be: [ERR]Read offset = 5 value = 2!!
[  268.168222] r8822be: [Err]pwr sub seq parser fail, status = 0x28!
[  268.168226] r8822be: Handle power off cmd error
[  295.841849] r8822be: halmac_init_hal failed
[  295.841871] r8822be: halmac_init_hal failed
[  295.841888] r8822be: halmac_init_hal failed
[  295.841903] r8822be: halmac_init_hal failed
[  295.841918] r8822be: halmac_init_ha..."
1761693,2018-04-08 09:00:07 UTC,This change was made by a bot.
1761693,2018-04-24 08:02:34 UTC,Thx for the info. I will wait that the final bionic beaver version comes out and i will try the new kernel on that version.
1761693,2018-04-25 17:45:07 UTC,"Meanwhile, i upgraded my kernel for the version 4.17-rc1 but the problem remains. When i boot the machine the system detects the wifi but he only works for a few sec (5/10 sec max). Then the wifi loses connection from the network that he was connected and in the end (20/30 sec) the Available networks disappear and the network manager stops working.Also, during this 20/30 sec process the operating system seems to be limited and slower"
1761693,2018-04-26 09:40:12 UTC,"Hello some new data about this issue,"
1761693,2018-05-08 05:37:09 UTC,"Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: network-wireless"
1761693,2018-05-08 08:23:22 UTC,done.
1761693,2018-04-07 10:42:15 UTC,apport information
1761693,2018-04-24 04:33:34 UTC,Please try v4.17-rc1.
1761693,2018-04-07 10:42:13 UTC,apport information
1761693,2018-04-07 11:48:01 UTC,"Lastly, in the version v4.16 kernel[0] wifi won't work in any moment"
1761693,2018-04-07 10:42:10 UTC,apport information
1761693,2018-04-07 10:42:09 UTC,apport information
1761693,2018-04-07 10:42:08 UTC,apport information
1761693,2018-04-07 10:42:07 UTC,apport information
1761693,2018-04-07 10:42:05 UTC,apport information
1761693,2018-04-07 10:42:11 UTC,apport information
1761693,2018-04-07 10:42:03 UTC,apport information
1761693,2018-04-07 10:42:02 UTC,apport information
1761693,2018-04-07 10:42:01 UTC,apport information
1761693,2018-04-07 10:41:59 UTC,apport information
1761693,2018-04-07 10:41:58 UTC,apport information
1761693,2018-04-07 10:41:57 UTC,apport information
1761693,2018-04-06 17:49:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1761693,2018-04-06 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1761693,2018-04-06 08:21:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1761700,2019-04-18 06:54:35 UTC,@François Tissandier
1761716,2021-02-17 17:07:22 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1761718,2018-04-11 13:18:39 UTC,"root@network2:~# lxc-ls
network2_neutron_server_container-2a5838f7 ubuntu-xenial-amd64"
1761721,2018-09-28 11:24:05 UTC,"Wow, thats old, but i just found out myself. See this for solutions:
https://askubuntu.com/questions/544754/lubuntu-14-04-unmute-sound-from-keyboard-not-work"
1761722,2018-11-09 07:09:34 UTC,What is the correct solution? I try to roll out an Openstack-Ansible rocky Production Ceph envoirement(10hosts - one is a seperated deployment-host). So far just problems :(
1761722,2019-05-03 20:46:01 UTC,I think the part of your config that is causing the problems is:
1761724,2018-04-06 10:23:59 UTC,"In ./ironic_staging_drivers/ovirt/ovirt.py:_getvm
Wrapping url in str(url) fixes the problem assuming the VM name doesn't contain multibyte characters"
1761724,2018-04-10 13:23:54 UTC,"Fix submitted here
https://review.openstack.org/#/c/559353/"
1761731,2020-09-19 07:25:03 UTC,Closing because INVALID: Can't replicate (Fixed?).
1761731,2018-04-06 14:46:29 UTC,Seems like this is (related to) key issue 3 in http://wiki.inkscape.org/wiki/index.php/Line_Height_Bugs
1761735,2018-04-07 18:31:00 UTC,I want to have a language extension that allows me to do exactly this - signal an error when I instantiate a mixin. Otherwise I am unable to enforce this constraint in my library.
1761735,2018-04-07 18:38:29 UTC,s/some-slot/%hidden-slot/
1761735,2018-04-07 18:38:58 UTC,...
1761735,2018-04-16 23:38:41 UTC,"I agree with Stas. The spec is explicitly clear that condition instances are not (necessarily) STANDARD-OBJECT, that SLOT-VALUE might not work, etc.
In addition to affording ourselves various efficiencies in the implementation of conditions, there would be yet another potential issue to solve involving infinite regress.
It's tricky enough to deal with things like unprintable objects in backtraces; I can only imagine how much more tricky if INITIALIZE-INSTANCE protocol has to be fully obeyed to make a condition instance and trying to signal a condition about something going wrong in INITIALIZE-INSTANCE."
1761735,2018-04-07 18:12:05 UTC,That doesn't make it any more standard. And you want to change the language just to signal an error when instantiating a mixin?
1761735,2018-04-17 21:23:50 UTC,My use case actually does not involve calling MAKE-INSTANCE itself or causing MAKE-CONDITION to obey its protocol; I fell prey to the XY problem.
1761735,2021-01-28 06:52:27 UTC,I guess this one's here would be solved too:
1761735,2018-07-23 16:27:50 UTC,I would also like to request such a feature.
1761735,2018-04-17 17:56:43 UTC,"We have a notion of class freezing.  I'd be willing to say that all builtins (WARNING, ERROR, etc) are frozen condition classes (but subclassable) and that calling MAKE-CONDITION on them can bypass MAKE-INSTANCE, etc. Does that help your use-case?"
1761735,2018-04-07 17:30:40 UTC,Okay. I have not worded myself clearly enough.
1761735,2018-04-06 12:10:45 UTC,MAKE-CONDITION is not called in MAKE-INSTANCE as ALLOCATE-INSTANCE calls ALLOCATE-CONDITION directly.
1761735,2018-04-07 17:14:16 UTC,"I am working on a library for defining and managing protocols, which are parts of interfaces. These protocols contain protocol classes, which are not meant to be instantiated directly - only their subclasses may be instantiated."
1761735,2018-04-07 16:58:19 UTC,"I'd prefer not to have a thing that should never be implemented to be permanently listed in the wishlist.
This is not standard and will help no one if it's implemented. The code using that will not only be non standard, but also not work on older SBCL versions
The standard is the only thing we can rely on to properly implement and optimize code. The reasoning ""other implementations do it that way"" is a slipper slope, where do we stop? I'd even prefer an error or a warning to be signalled, which is in line with how SBCL treats other non standard code. A language that is implicitly encoded by its implementation is a sad thing."
1761735,2018-04-07 11:24:40 UTC,I don't think this is any more invalid than other wishlist issues.
1761735,2018-04-06 12:35:51 UTC,"Nonetheless it provides me with the ability to create constructors for condition objects which are created in a standard way, through MAKE-CONDITION. SBCL currently has no such functionality."
1761735,2018-04-06 12:30:00 UTC,That doesn't appear to be an extension but a side effect of conditions being implemented directly on top of clos objects.
1761735,2018-04-06 12:27:50 UTC,This behavior is not defined by the standard. This is an extension request. Its purpose is to make SBCL's MAKE-CONDITION behave the same way as it does in other CL implementations which already have this extension.
1761735,2018-04-06 12:25:05 UTC,What standard section is this about?
1761735,2018-04-07 17:24:38 UTC,"The standard clearly says ""make-condition, not make-instance, must be used to create condition objects explicitly."" I usually refrain from changing the language when trying to write my programs."
1761739,2018-05-02 13:57:48 UTC,"The wording has been changing to ""No, don't send system info"" which is less misleading since it's indeed not sending any system info, unsure if that's good enough to consider the issue as resolved?"
1761739,2018-05-02 14:37:15 UTC,"My personal opinion is that saying ""don't send"" when we do send something is the misleading part. OK, maybe no system info is being sent - but something else is and we haven't said that."
1761739,2018-09-02 17:08:30 UTC,"> I've confirmed with Jamie B that the ping still needs to be sent
"
1761739,2018-10-19 07:16:56 UTC,"Note, with the current privacy regulations, if Canonical uses consent as the base for submitting this information for collection, I am quite sure it would be against the law to send IP address to a Canonical server when consent is missing.   Sending IP address provides time, location and the fact that a given version of Ubuntu is being installed to Ubuntu, and every network sniffing entity on the way like NSA and GCHQ.  This set of information is by definition personal information, and by combining the IP address with other sources it is often possible to identify the individual uniquely (for example if the user uses Facebook, log into her email etc). As consent is obviously missing if the user declined to submit the information about his machine, Canonical would have to come up with another basis for the collection.  It would be hard to argue it is vital for the operation of the service provided, one of the other options for data collection.  It is probably a good idea to check out the GDPR provisions available, to reduce the chance of a large fine."
1761739,2018-10-24 06:48:49 UTC,"The fact that you claim to not log or store the IP address is beside my point, which is that the IP address is _transferred_ out of the machine even when the user said no to submitting any information.  If consent is your legal basis for submitting information to Ubuntu, it is not valid for transferring the 'I do not want information to be submitted' message over HTTP, independent of what story you provide on what you do with the personal information once it arrive."
1761739,2018-10-19 10:30:53 UTC,"Of course IP information is sent.  Any HTTP connection will pass on the IP address of the other end during establishment of its TCP/IP connection.  The fact that HTTP is used over TCP is enough to send the IP address. It could be avoided by enforcing the use of Tor or similar, but that is purely academic given that most people are not using a service to hide their IP address."
1761739,2018-10-19 11:10:15 UTC,IP addresses are not logged or stored.
1761739,2018-04-10 21:28:33 UTC,"I was looking at updating the ""Show First Report"" button to show the empty report content if you select ""No"" but I think that might be misleading. If you select ""No"", then ""Show First Report"" then ""Yes"" you might not notice the text has changed."
1761739,2018-10-19 08:02:07 UTC,There is no IP info being sent
1761739,2018-04-10 16:08:56 UTC,"(This is probably being tracked elsewhere, but the linked privacy policy might need updating for this. Currently, it mentions *storing* IP addresses in relation to dash searches, and there's not really any other mention apart from"
1761739,2018-05-02 14:37:21 UTC,cents
1761739,2018-04-10 15:21:22 UTC,"mpt's going to come up with something better, but it probably shouldn't be a yes/no question - rather a radio something like"
1761739,2018-04-10 04:58:19 UTC,We should definitely make a design call ASAP on this.
1761739,2018-04-10 14:35:07 UTC,"I've confirmed with Jamie B that the ping still needs to be sent, so we need to work with design on improving the wording and making it clear than something will still be sent, perhaps showing the contents."
1761739,2018-04-10 14:49:08 UTC,Current screenshot for reference
1761739,2018-04-06 12:42:51 UTC,"Right, note that it was described on the list topic
https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html"
1761739,2018-04-10 15:37:07 UTC,"To be clear - IP address are not being saved to the database.  The data will of course have to come from an IP address, but we're not recording the data submitted against and IP address."
1761739,2018-04-10 14:52:50 UTC,or slightly better:
1761739,2018-04-10 14:55:47 UTC,Can we use this bug as a release bug to track that request then maybe?
1761739,2018-04-10 14:51:52 UTC,Wording for this feels like it's going to be awkward. Here's one suggestion
1761742,2018-04-10 20:51:18 UTC,@didrocks - is libsysmetrics thread-safe? I guess I should just wrap the call in a thread?
1761742,2018-04-11 06:35:16 UTC,"libsysmetrics is using multiple goroutines (and potentially threads), but all the external API is thread-safe, I took care to not do any operations which can change the global state for that purpose."
1761742,2018-09-02 15:31:35 UTC,"I think “Continue” should advance immediately to the next step, regardless of how long any submission takes or whether it fails. The user is doing us a favour by submitting data, and there’s no need for us to bother them at all if it happens not to work. It’s not as if we’re desperately short of submissions."
1761747,2018-04-06 16:08:46 UTC,This is not a duplicate bug. Please re-read report. This is about the minimal install not listing Firefox *as* installed when it clearly is.
1761748,2018-10-04 09:22:24 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/607864"
1761748,2018-10-24 16:47:05 UTC,This issue was fixed in the openstack/os-win 4.1.0 release.
1761748,2018-10-16 07:32:21 UTC,"Reviewed:  https://review.openstack.org/607864
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=65b06c243b169597d8bcb201c5a8ad5824fcddda
Submitter: Zuul
Branch:    stable/queens"
1761748,2018-10-04 07:56:00 UTC,"Reviewed:  https://review.openstack.org/607549
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=5ba1e81cd1f82859058178ebb9183c3e9ccf17d8
Submitter: Zuul
Branch:    stable/rocky"
1761748,2018-10-03 10:32:15 UTC,"Reviewed:  https://review.openstack.org/606066
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=42cfab1081dcb46b7dca898316fb095206b78666
Submitter: Zuul
Branch:    master"
1761748,2018-09-28 12:53:50 UTC,"It looks like a new unnamed port was added, which is odd as port names are mandatory. I'll add a check. Thanks for reporting this bug."
1761748,2018-10-03 12:38:49 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/607549"
1761751,2018-05-02 14:11:50 UTC,Is it HDMI from the board to HDMI on the monitor? I'd like to rule out any use of an adapter or HDMI-to-DVI cable.
1761751,2018-04-23 20:13:27 UTC,"I've also been building all of the bisect testing kernel with Bionic configs, which may explain why they are all bad."
1761751,2018-04-23 20:58:13 UTC,I built a Bionic test kernel with the following two config options not set:
1761751,2018-04-24 18:50:52 UTC,The test kernel (4.15.0-15-generic #16~lp1761751) boots normally.
1761751,2018-04-24 21:01:26 UTC,I built a Bionic test kernel with the following one config option not set:
1761751,2018-04-27 08:14:38 UTC,Kernel 4.15.0-15-generic #16~lp1761751v2: Boots normally
1761751,2018-04-30 15:14:50 UTC,"Hi Harry,"
1761751,2018-04-30 15:39:51 UTC,What display connectors are being used?
1761751,2018-04-30 15:40:44 UTC,Replied on the ticket.
1761751,2018-05-02 06:24:32 UTC,"I don't think it is the same bug. I have a card with HDMI and DVI
connectors (XFX RX 460). The HDMI connector is connected to the monitor,
the DVI connector is unplugged."
1761751,2018-05-02 16:22:49 UTC,"I'm not sure if you asked for the contents of these files from a working
or non-working kernel, but I'll take the working kernel since that's
obviously a lot easier."
1761751,2018-12-13 05:43:19 UTC,Seems to be another AMDGPU DC issue...
1761751,2018-05-02 19:47:43 UTC,I booted the 4.17rc1 kernel.
1761751,2018-05-15 11:44:09 UTC,"Some information from me, using 4.16.8 kernel
System is Lenovo Z50-75 laptop with AMD-A10 cpu (Kaveri) and both HDMI and VGA ports. I use the VGA port to which is connected an Acer X223HQ display, capable of displaying up to 1920x1080. The laptop screen is also 1920x1080"
1761751,2018-05-16 12:39:04 UTC,"Problem still exists in 4.16.9 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.9/
(#uname -r output is 4.16.9-041609-generic )"
1761751,2018-05-22 07:14:19 UTC,"Problem still exists in 4.16.10 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.10/
(#uname -r output is 4.16.10-041610-generic )"
1761751,2018-05-23 06:31:59 UTC,Problem persists in kernel 4.16.11
1761751,2018-05-24 06:40:46 UTC,Problem persists in kernel 4.17-rc6 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6/
1761751,2018-09-16 18:45:25 UTC,"HI guys,"
1761751,2018-12-11 16:30:22 UTC,I'm getting exactly this issue. An ATI RX 480 on Kubuntu 18.04 with a ASUS MG28U on HDMI-1. It is on a 5m cable so using the displayport wasn't an option. The long HDMI cable is to allow the large system box to be away from my desk. I mostly use the system as a web and data server and it is stuffed with hard drives.
1761751,2018-04-22 03:26:34 UTC,"Yeah, so I doubt it's a whitespace fix in the rxrpc driver. However, a diff between the configs on v415-rc2 and v415-rc3 has lots of differences, the most interesting being this one:"
1761751,2019-01-23 00:31:19 UTC,I have previously created an upstream bug report for this:
1761751,2019-03-02 16:39:30 UTC,"Just as an update, in the Freedesktop issue, I found using a LOWER specced/older cable to fix the problem."
1761751,2018-05-02 17:50:10 UTC,"Thanks, mind posting the same for the non-working kernel? I'm curious if the problem is
1) we don't detect the display
2) we don't enable the display
3) we enable the display but wrong"
1761751,2018-04-21 18:01:21 UTC,Kernel 3d7682af228fd78dc46bc: Black screen.
1761751,2018-04-23 20:58:46 UTC,"Also, with this test kernel both the linux-image and linux-image-extra .debs need to be installed."
1761751,2018-04-20 19:46:45 UTC,Kernel 5fc62f6a139a7b06b027bf442cd4205619506f59: Black screen.
1761751,2018-04-06 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1761751,2018-04-06 14:06:30 UTC,"Ok, so I found this message when trying to boot a faulty kernel without workaround, if it helps:"
1761751,2018-04-06 17:54:56 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
1761751,2018-04-07 04:47:20 UTC,"v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ - Boots normally
v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ - Boots normally
v4.15-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc5/ - Black screen
v4.15-rc9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/ - Black screen
v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ - Black screen
v4.16-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ - Not tested"
1761751,2018-04-07 04:57:50 UTC,"4.15.0-041500rc2-generic - Boots normally
4.15.0-041500rc3-generic - Black screen
4.15.0-041500rc4-generic - Not tested"
1761751,2018-04-10 17:44:47 UTC,I started a kernel bisect between v4.15-rc2 and v4.15-rc3. The kernel bisect will require testing of about 7-10 test kernels.
1761751,2018-04-12 01:04:48 UTC,Kernel 4.15rc2+78d9b048446c3c0a83313444fb706f8f3bccdae7: Black screen.
1761751,2018-04-12 01:22:26 UTC,Possibly upstream bug found: https://bugs.freedesktop.org/show_bug.cgi?id=105880
1761751,2018-04-12 17:11:45 UTC,"I built the first test kernel, up to the following commit:
6a5e05a47b6cb8e59bfad351444322b1e4012326"
1761751,2018-04-13 18:32:14 UTC," > I built the first test kernel, up to the following commit:"
1761751,2018-04-16 15:54:10 UTC,Kernel 2391f0b4808e3d5af348324d69f5f45c56a26836: Black screen.
1761751,2018-04-13 21:37:48 UTC,"Whoops, yes, the last kernel was the second."
1761751,2018-04-17 04:13:16 UTC,Kernel af57b7fffaf74ff337e479abb19026d72065673b: Black screen.
1761751,2018-04-17 12:29:43 UTC,"I built the next test kernel, up to the following commit:
a0da456bbf95d2a9294799bb05c61bfb24736bb7"
1761751,2018-04-18 11:20:52 UTC,Kernel a0da456bbf95d2a9294799bb05c61bfb24736bb7: Black screen.
1761751,2018-04-18 11:31:19 UTC,There's nothing graphics related here:
1761751,2018-04-18 14:05:10 UTC,"There are only 3 kernels left to test, so I hope we hit a good results soon."
1761751,2018-04-19 05:16:53 UTC,Linux version 4.15.0-041500rc1-generic (jsalisbury@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #201804181224: Black screen
1761751,2018-04-19 14:55:18 UTC,"I built the next test kernel, up to the following commit:
282ef4729195c8503f7101d574acfb5e7c8a8209"
1761751,2018-04-19 23:45:04 UTC,Kernel 282ef4729195c8503f7101d574acfb5e7c8a8209: Black screen.
1761751,2018-04-20 16:24:50 UTC,"I built the next test kernel, up to the following commit:
5fc62f6a139a7b06b027bf442cd4205619506f59"
1761751,2018-04-16 17:50:09 UTC,"I built the next test kernel, up to the following commit:
af57b7fffaf74ff337e479abb19026d72065673b"
1761751,2018-04-20 20:26:01 UTC,"I built the next test kernel, up to the following commit:
3d7682af228fd78dc46bc6bf40e0268ad04521ec"
1761763,2018-04-11 12:39:04 UTC,"Looking at your logs, generally it seems like dbus is broken for some reason."
1761763,2018-04-11 14:05:48 UTC,I replied on launchpad but in answer to your 2 questions.
1761763,2018-04-11 14:02:44 UTC,This happened when I did fix broken packages after going into advanced option from grub
1761763,2018-04-11 12:37:47 UTC,Thanks for the report.
1761763,2018-04-11 11:01:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761771,2018-07-18 09:11:44 UTC,Unattended-upgrades' postinst only triggered the problem which is in monit/redis:
1761785,2018-11-28 08:35:24 UTC,"It also makes deployments in Ubuntu 18.04 containers fail, because systemd-resolved is already listening on 127.0.0.53:53:"
1761785,2019-07-22 13:22:48 UTC,"I encountered the same issue and fixed it by setting ```unbound_listen_interface: ""{{ ansible_eth1.ipv4.address }}""``` in user_variables.yml as well to be able to install in Ubuntu 18.04 containers, because systemd-resolved was already listening on 127.0.0.53:53."
1761788,2018-07-20 15:43:50 UTC,"Change abandoned by Paul Bourke (pbourke) (<email address hidden>) on branch: master
Review: https://review.openstack.org/559379
Reason: If someone else wants to pick this up feel free to reopen"
1761796,2018-08-15 18:00:31 UTC,"Tested the 4.17 kernel, and this is the issue I now see:"
1761796,2018-04-06 18:22:09 UTC,"Test both -proposed & 4.16 kernels, and the issue persists."
1761796,2018-04-06 18:39:19 UTC,collecting logs with mainline kernel.
1761796,2018-08-16 15:22:49 UTC,"I think our best bet is to perform the bisect.  When you have a chance, can you test the kernel posted in comment #34?  I'll build the next test kernel based on that test result."
1761796,2018-04-06 18:41:22 UTC,apport information
1761796,2018-04-25 21:48:27 UTC,"Can you see if this bug happens with the Artful kernel?  It is available from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/14537150"
1761796,2018-04-30 07:22:21 UTC,This issue is not present in Artful. This issue is only present in Bionic.
1761796,2018-04-30 13:52:25 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
1761796,2018-05-15 20:27:08 UTC,Finally got around to test this. ANd this are my findings:
1761796,2018-05-17 20:19:39 UTC,I started a kernel bisect between v4.15-rc6 and v4.15-rc7. The kernel bisect will require testing of about 6 test kernels.
1761796,2018-05-16 19:55:24 UTC,"So I've tested all the way from rc2 -> rc7, and confirm that rc7 is the issue. In two different machines:"
1761796,2018-05-18 19:14:46 UTC,"@Joseph:
Issue still exists:"
1761796,2018-05-21 17:25:43 UTC,"I built the next test kernel, up to the following commit:
abb62c46d4949d44979fa647740feff3f7538799"
1761796,2018-08-14 16:04:19 UTC,"Hi Joseph,"
1761796,2018-08-14 20:01:14 UTC,"The problem with having the kernels pre-built is the bisect needs to know whether a test kernel has the bug or not.  Based on that input, the bisect decides the next SHA1 to test."
1761796,2018-08-14 23:19:12 UTC,"Maybe I did something wrong, but this kernel (4.18) causes a kernel panic. The process I followed was same as always, to wget the *.deb, dpkg -i *.deb && update-grub at the end to ensure this kernel is used:"
1761796,2018-08-15 14:49:48 UTC,"Thanks for testing.  The panic was not caused from anything you did.  That is a new bug in the 4.18 kernel. We will have to monitor this new bug, since Cosmic will eventually be 4.18 based.  We should also test the latest Cosmic kernel, which is 4.17 based.  It is available from:"
1761796,2018-04-06 17:55:23 UTC,apport information
1761796,2018-05-16 15:54:12 UTC,"Just to confirm, 4.15-rc1 does not have the issue, but 4.15 final does?  If that is the case, we can try to narrow it down further.  Could you test v4.15-rc9:"
1761796,2018-04-06 17:55:22 UTC,apport information
1761796,2018-04-06 18:39:42 UTC,apport information
1761796,2018-04-06 17:55:18 UTC,apport information
1761796,2018-04-06 16:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1761796,2018-04-06 17:45:33 UTC,apport information
1761796,2018-04-06 17:45:34 UTC,apport information
1761796,2018-04-06 17:45:37 UTC,apport information
1761796,2018-04-06 17:45:38 UTC,apport information
1761796,2018-04-06 17:45:39 UTC,apport information
1761796,2018-04-06 17:45:40 UTC,apport information
1761796,2018-04-06 17:45:42 UTC,apport information
1761796,2018-04-06 17:55:20 UTC,apport information
1761796,2018-04-06 17:45:44 UTC,apport information
1761796,2018-04-06 17:47:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1761796,2018-04-06 17:55:11 UTC,apport information
1761796,2018-04-06 17:55:12 UTC,apport information
1761796,2018-04-06 17:55:13 UTC,apport information
1761796,2018-04-06 17:55:14 UTC,apport information
1761796,2018-04-06 17:55:16 UTC,apport information
1761796,2018-04-06 17:55:17 UTC,apport information
1761796,2018-04-06 17:45:43 UTC,apport information
1761798,2020-11-25 14:03:13 UTC,"OK, but that still says in both cases here we've got a virtio error telling us that the queues are broken before migration even starts;  so we should try and figure out why that's happening first."
1761798,2020-11-24 12:17:25 UTC,"hang on, I've just noticed the :"
1761798,2020-11-23 16:56:22 UTC,[Copy/pasting my comment from here: https://bugs.launchpad.net/nova/+bug/1737625/comments/4]
1761798,2020-11-23 15:30:29 UTC,in the new case we have the same qemu/libvirt version in both nodes
1761798,2020-11-23 15:17:15 UTC,"Source node
https://zuul.opendev.org/t/openstack/build/d50877ae15db4022b82f4bb1d1d52cea/log/logs/subnode-2/libvirt/qemu/instance-0000001a.txt"
1761798,2018-05-29 22:23:27 UTC,"I also think this is a qemu bug, will do some tests, try to reproduce."
1761798,2020-11-25 13:44:10 UTC,I see two recent hits we have still logs for.
1761798,2020-11-23 14:53:14 UTC,We hit a very similar issue https://zuul.opendev.org/t/openstack/build/d50877ae15db4022b82f4bb1d1d52cea/log/logs/subnode-2/screen-n-cpu.txt?severity=0#13482
1761798,2018-05-15 02:00:53 UTC,"Hm, looks like the e-r query [1] for this bug doesn't find it if the screen-n-cpu.txt is on the subnode-2:"
1761798,2018-04-09 08:25:53 UTC,"I'm not sure that's the same as the bz 1450524 - in this case it's virtio-blk, where I *think* that bz was tracked down to a virtio-balloon and a virtio-net issue."
1761798,2018-04-06 16:47:06 UTC,The offending instance QEMU from the log that crashed:
1761798,2018-04-06 16:37:52 UTC,Maybe when we move to use the Queens UCA we'll have better luck with this:
1761798,2018-05-29 22:21:19 UTC,"Ran into a similar issue, when snapshotting an instance, it won't start afterwards.
Root cause is inconsistency between state of device virtio-scsi and the saved VM RAM state in /var/lib/libvirt/qemu/save/
Removing instance-0000****.save file from thsi folder allows starting the VM back but may cause data corruption.
Specifics of my case - using virtio-scsi driver and discard enabled, backend is Ceph. Impacted 2 Windows VMs so far."
1761801,2018-04-06 17:29:29 UTC,Why do you need dbus-python?
1761801,2018-04-06 17:31:19 UTC,Ok ignore the distro version and desktop version questions!
1761801,2018-04-06 19:52:14 UTC,"My cloud app need the dbus-python to work... im a beginner in linux, so i dont know if this is a bug or not...
This is the app
https://meocloud.pt/downloads (https://link.getmailspring<email address hidden>/0?redirect=https%3A%2F%2Fmeocloud.pt%2Fdownloads&recipient=MTc2MTgwMUBidWdzLmxhdW5jaHBhZC5uZXQ%3D)
Sorry my english"
1761801,2018-04-13 20:41:22 UTC,"Update,
I dont know if it helps, but I tested on ubuntu 18.04 and works fine..."
1761802,2019-09-19 11:58:07 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1761804,2018-08-26 19:43:15 UTC,"Part of the issue here is that they really are several individual A (or AAAA) records, with the imposed constraint that the TTL for all RRs of a given type MUST be identical.  When you add in that several of the RRs are added dynamically as the node is deployed, it gets even more interesting."
1761804,2019-09-19 12:00:12 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1761806,2018-04-06 20:24:59 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1761806,2018-04-11 02:28:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761806,2018-04-11 02:41:50 UTC,"same here
HP Envy 13
lspci
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 61)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)"
1761813,2018-04-18 20:14:45 UTC,It's not an issue with the environment that maas never says anything like:
1761813,2018-04-18 19:53:45 UTC,"Sure we can treat that as maas adding some more error surface. That said, MAAS already logs as much as it cans and surfaces errors from MAAS itself into the UI."
1761813,2018-04-18 19:47:52 UTC,"While simplestreams could do a better job telling MAAS what's wrong, MAAS could also do a better job telling the user what might be wrong. There are various possibilities from simplestreams - can't connect, missing signature, etc."
1761813,2018-04-18 18:01:05 UTC,Marking this as invalid for MAAS because:
1761813,2018-04-17 21:23:56 UTC,"Thanks Jason -- please set back to new when you can.  we don't see anything systemic in the simplestreams library right now, so we will need a way to reproduce."
1761813,2018-04-17 21:15:19 UTC,"I'm sorry, this bug is not reproduced right now so I can't do those things."
1761813,2018-04-17 20:39:34 UTC,"@Jason,"
1761813,2018-04-17 20:13:09 UTC,"On Tue, Apr 17, 2018 at 2:50 PM, Andres Rodriguez
<email address hidden> wrote:

> @Jason,
>
> Instead of restarting regiond have you forced the import of images either
> via the API or via the UI?
"
1761813,2018-04-17 19:50:39 UTC,"@Jason,"
1761813,2018-04-17 19:40:07 UTC,"FWIW, I found a really old IRC log (1.4 times) talking about this similar
issue. Not saying it’s related or the same, but just bringing it up in case
this could lead somewhere."
1761813,2018-04-18 21:13:46 UTC,"Service checking as you describe is a known wishlist enhacement, but I'll
be happy to receive contributions if you have the cycles."
1761813,2018-04-17 19:24:47 UTC,A couple of things that make me think it's not a proxy issue:
1761813,2018-04-17 19:18:39 UTC,The traceback indicates that the json document that was loaded did not include a PGP header.
1761813,2018-04-06 20:09:27 UTC,I'm marking this incomplete as I'm unable to reproduce the issue.
1761813,2018-04-06 19:30:05 UTC,"Actually, this seems like a maas bug. I restarted regiond and it's working now."
1761813,2018-04-06 17:51:18 UTC,"That said, it's hard to tell, because the error from MAAS/simplestreams is not very useful. It would be great if it said what it's looking for that's missing..."
1761813,2018-04-06 17:49:53 UTC,We're running this through a proxy internal to Canonical.  I believe the lack of Cache-Control settings for the simplestreams on maas.io are causing issues with that cache:
1761813,2018-04-06 17:39:46 UTC,Steps I'm taking:
1761813,2018-04-06 17:38:37 UTC,The streams were updated 3+ hours ago. It's 17:37 UTC now and 13:58 is the latest update time from there:
1761813,2018-04-06 17:36:15 UTC,seems that the streams have just been updated: https://images.maas.io/ephemeral-v3/daily/streams/v1/
1761813,2018-04-06 17:33:38 UTC,"I /think/ this issue would indicate that the streams are not signed, which could mean that the streams were published before they were fully signed."
1761813,2018-04-06 17:32:28 UTC,"Hi Jason,"
1761813,2018-04-17 19:03:42 UTC,"The bionic occurrence of this is [1]. Based on the logs attached in [1], this happened on ""2018-04-10 01:29:39"""
1761814,2021-01-29 17:21:06 UTC,BC Libraries Co-op Support has recently received a request for this type of functionality; note that the member library requested that the function be set by circ modifier.
1761814,2018-05-30 17:20:02 UTC,I think hold rules are a reasonable way to go about it for a good flexibility/complexity trade off. Especially because different locations may want different times and you wouldn't want a new circ mod just for that.
1761814,2018-05-30 15:16:13 UTC,We have received several requests for this type of functionality from our member libraries.
1761814,2018-05-30 15:38:52 UTC,"As a discussion point, ISTM this would best be implemented as a value attached to hold rules for flexibility, and would default to the org setting if the value is not set on a rule.  Thoughts?"
1761821,2018-04-16 18:35:07 UTC,"On Fri, Apr 6, 2018 at 11:00 AM, Steve Langasek
<email address hidden> wrote:

> Public bug reported:
>
> error message at the end of a 'git ubuntu clone cryptsetup':
>
> fatal: could not read Username for 'https://git.launchpad.net': terminal
> prompts disabled
"
1761821,2018-04-16 19:07:25 UTC,cf LP: #1735098
1761823,2018-04-09 05:50:22 UTC,@Hongbin
1761823,2018-04-13 13:48:58 UTC,"As it was proposed / discussed already during the drivers meeting, moving to confirmed. Let's elaborate on it further and then we can discuss it again in the meeting"
1761835,2018-04-06 18:48:37 UTC,"This was previously addressed in https://bugs.launchpad.net/charms/+source/neutron-openvswitch/+bug/1635067 however the implementation was never carried over to the NG charm. Additionally the fix has since broken, as reported in https://bugs.launchpad.net/charm-helpers/+bug/1761840"
1761838,2020-09-13 14:25:02 UTC,"Why not just add a new hook tool ""unit-get fan-network"" ?"
1761838,2021-02-04 23:31:23 UTC,Also affects juju 2.8.7-focal-amd64. Couple notes and a simplified use case; it seems the fan gets in the way of deployments that don't even leverage network-get:
1761838,2020-09-13 14:18:48 UTC,I get the problem too: Here is a discussion I opened on discourse.
1761838,2019-02-14 11:10:03 UTC,This issue happens for me as well.
1761838,2019-02-14 15:28:51 UTC,"juju model-config fan-config="""" container-networking-method="""""
1761838,2018-04-09 04:29:18 UTC,"You can set it with ""juju model-defaults"" instead of ""juju model-config"".
That should set the new configuration for the next model being created."
1761838,2018-04-07 07:14:11 UTC,"Hi John,"
1761838,2018-04-07 04:40:07 UTC,"I don't believe in GCE we automatically configure a Fan config. However,
due to the way the fan works, if you would run containers then you need to
be advertising the fan addresses even for processes that are not in
containers. (it is how the fan determines whether it can use direct
addressing or needs to NAT packets.)"
1761838,2018-05-04 06:10:23 UTC,"If model-defaults aren't being respected on new models, that is certainly an issue."
1761871,2018-04-09 02:53:57 UTC,"Colin,"
1761871,2020-09-14 07:48:08 UTC,This sounds like something that's probably already fixed.
1761873,2018-04-07 09:10:12 UTC,"The window title is handled by Metacity, so reassigning."
1761873,2018-04-07 14:43:12 UTC,"We add ""(as superuser)"" if the process which owns the window claims to be owned by user 0, i.e. root."
1761878,2018-04-09 14:12:42 UTC,"""No Connect"" in the pin table means that the pin type is set to ""No Connect"" not that there is no connection to the pin itself.  Your change to the pin table will allow you to connect two ""No Connect"" pins together without an error.   My guess that you want an optional ""Ignore unconnected pins"" option which we currently do no support."
1761887,2018-04-06 23:05:13 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1761887,2018-04-06 23:30:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761891,2018-04-06 23:05:15 UTC,Working branch user/jeffdavis/lp1761891-remove-old-report-email-templates has a commit that removes the unused versions of report-fail and report-success.
1761896,2018-04-06 23:38:19 UTC,Working branch user/jeffdavis/lp1761896-email-template-date-header has a fix for the A/T templates.
1761901,2018-04-07 11:12:37 UTC,After the release upgrade has finished I have still 1103 packages to be upgraded.
1761907,2018-04-07 01:22:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559453"
1761907,2018-08-08 10:24:08 UTC,"Reviewed:  https://review.openstack.org/559453
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ae246945a6f9a803bdd6ccfe3d3b758deef813c5
Submitter: Zuul
Branch:    master"
1761907,2018-09-04 16:23:51 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0rc1 release candidate.
1761911,2018-04-07 05:38:01 UTC,"Before I submitted this, I had run the following command, per the web page mentioned above."
1761919,2018-04-07 03:49:17 UTC,Tried a restart and installing again.
1761922,2019-10-10 10:32:29 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1761930,2018-04-07 06:00:07 UTC,This change was made by a bot.
1761930,2018-04-10 15:40:11 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1761930,2018-04-10 20:28:24 UTC,Also tested 4.13.0-38-generic without any of the extras modules packages etc.
1761931,2018-04-18 14:43:07 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.17
1761931,2018-04-19 13:43:23 UTC,"Bon... j'ai remis ""Certaines entrées de votre fichier sources.list, concernant des tierces parties, ont été désactivées. Vous pouvez les réactiver après la mise à niveau avec l'outil «[nbsp]Logiciels &amp; mises à jour[nbsp]» ou avec votre gestionnaire de paquets."""
1761931,2018-04-19 09:51:40 UTC,Je confirme que ça pose problème avec le GUI: fenêtre vide et message d'erreur...
1761931,2018-04-19 15:05:33 UTC,"> status: 	In Progress → Fix Committed
"
1761931,2018-04-11 20:15:22 UTC,"Jean-Baptiste,"
1761931,2018-04-10 07:18:58 UTC,"@Jean-Marc, merci pour ton aide."
1761931,2018-04-09 17:52:18 UTC,Bravo pour l'efficacité :)
1761931,2018-04-09 07:29:10 UTC,"Bonjour,"
1761931,2018-04-09 07:25:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761934,2018-04-09 05:58:53 UTC,why oh why file it against mesa?
1761934,2018-04-11 04:38:57 UTC,"My apologies for filing against mesa.  Not sure how that happened.  But the problem itself remains.  Since it's been over a week now, I think it's important to have it on the radar."
1761934,2018-04-11 04:40:18 UTC,"jp.archive.ubuntu.com seems to have recovered, though."
1761936,2018-04-26 16:03:50 UTC,"The incidence on the official client was already resolved as explained in my last post and it was closed and fixed in version 2.4.1. I must say that the way is to use the official version and not the one that is distributed from the Ubuntu repositories, unfortunate but it is the reality. Yesterday I wrote to some of the maintainers of the distribution client and I did not get any response, as it happens here where the bug has not been assigned to any developer. This is how bug tracking works in such an important distribution and how many users use it?"
1761936,2018-04-18 00:02:45 UTC,"Bug reported also on the official Owncloud client, which is the same version apparently as the Ubuntu distribution package:"
1761936,2018-04-11 00:50:33 UTC,"I have tried installing chromium, which generates a key in the ring of keys and it works. It is a problem in the Package package: owncloud-client 2.4.1+dfsg-1, not in seahorse."
1761936,2018-04-25 17:53:19 UTC,In the official thread of the package is the temporary solution this moment: https://github.com/owncloud/client/issues/6455?_pjax=%23js-repo-pjax-container
1761936,2018-04-08 21:26:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761936,2018-04-08 21:27:43 UTC,Same issue here.
1761943,2018-04-20 16:49:08 UTC,Am I the only one affected?
1761947,2018-04-16 23:25:38 UTC,"The macroexpander of DEFMETHOD is to blame, but this could be considered just an unfortunate side-effect of *EVALUATOR-MODE* being set to :COMPILE, which makes the entire form a single lambda. As such, the defmethod expander warns before the DEFCLASS is executed. Some potential fixes:"
1761947,2018-04-16 23:26:22 UTC,This adds a compilation-unit around LOAD which I think we should do anyway.
1761947,2018-12-15 16:18:42 UTC,This is still present as of 1.4.14.
1761947,2020-02-29 11:24:35 UTC,Still present on 2.0.1.
1761964,2018-04-07 13:40:52 UTC,"TLDR:
- if you press the ""Back"" key after partitioning, Ubiquity fails to repartition (Ubuntu 18.04-beta2), possibly bricking your PC."
1761971,2018-08-18 12:32:02 UTC,"Dear Philippe, no clue here. I gave up and installed 18.04 from scratch
and it works like a charm."
1761971,2018-08-17 19:10:43 UTC,Any clues since 1st report ? I am also affected and will investigate as I am able to reproduce using xinit.
1761971,2018-08-17 19:15:16 UTC,Workaound :
1761971,2018-08-17 21:05:17 UTC,It was observed on:
1761979,2018-04-09 16:01:04 UTC,"Hello Colin,"
1761979,2018-04-07 18:23:40 UTC,I said i wanna give you some more information about the error here so I'll do :)
1761979,2018-09-17 18:33:51 UTC,Here's another one
1761979,2018-04-07 13:47:21 UTC,"It is necessary to quote the actual OOPS ID, rather than truncating it to ""oops.....""."
1761979,2018-04-07 13:53:08 UTC,sry. I'll give further info to this bug the next time this message occurs. :) Have a nice weekend
1761990,2018-04-11 20:12:28 UTC,"To allow us to understand what your problem is, please could you attach the OpenRailsLog.txt file that can be found on your desktop. Do this right after you've had the problem and it will contain useful information which we can use to diagnose the issue."
1761991,2018-04-07 22:03:51 UTC,Thanks for your report!
1761991,2018-04-10 15:03:48 UTC,You're welcome!
1761991,2018-04-14 11:34:54 UTC,"Additionally, I tested other languages after a full installation in a QEMU virtual machine."
1761991,2018-05-31 12:05:08 UTC,Should I split this bug report?
1761991,2018-07-28 09:51:30 UTC,New tests done on Cosmic Daily 2018 07 28. Full installation.
1761991,2018-07-28 09:56:26 UTC,"Summary Table of (non) translated strings in French, Spanish, German, Portuguese"
1761991,2018-09-27 04:17:51 UTC,[Expired for Ubuntu Translations because there has been no activity for 60 days.]
1761995,2020-07-01 21:03:56 UTC,I can confirm that this fix works on Ubuntu 20.04. To reiterate:
1761995,2018-04-18 07:53:27 UTC,It's being made a recommend but that was blocked on some MIRs to be reviewed/accepted
1761995,2018-04-17 20:03:55 UTC,"udisks2 2.7.6-2ubuntu6 ""suggests"" libblockdev-crypto2;"
1761995,2018-04-17 19:25:14 UTC,"I can confirm what Sebastien proposed. Installing libblockdev-crypto2 and restarting the udisks2.service did the trick.
Also it maybe worth mention that in my case the installation of Ubuntu 18.04(beta2) performed with the new ""minimal installation"" option."
1761995,2018-04-17 18:38:26 UTC,"Hi Sebastien, yeah actually I did it right after reporting this bug. Installing libblockdev-crypto2 and restarting udisks2 service made it work!"
1761995,2018-04-17 12:36:47 UTC,"Hi Sebastien, just gave that a try and it didn't help for me. Thank you"
1761995,2018-04-16 16:44:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761995,2018-04-16 16:46:48 UTC,"I have an installation of Xenial (16.04 LTS) which doesn't have this bug (gnome-disk-utility version 3.18). After upgrading to 18.04 (gnome disk version 3.28) I start seeing this bug. It's not a showstopper as I know my way through the command line, but still, I spend 60% of my time on macOS and having a common task such as LUKS + ext4 done through a graphical interface is much appreciated"
1761995,2018-04-14 00:28:39 UTC,Same problem here! Any workarounds?
1761995,2018-04-08 09:38:28 UTC,"This also affects the case when you want to Open an encrypted disk/usb that was LUKS encrypted on another Linux system (Debian/Ubuntu).
It cannot Open it - Mount it, returning a similar error."
1761995,2018-04-08 09:33:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1761995,2018-04-17 11:59:47 UTC,does it work if you install libblockdev-crypto2 ?
1761996,2018-04-08 05:30:10 UTC,"Hi,"
1761996,2018-04-08 11:35:08 UTC,"Sure, here it is:
------------------------------
00:00.0 ""Host bridge"" ""Intel Corporation"" ""Mobile 945GSE Express Memory Controller Hub"" -r03 ""Hewlett-Packard Company"" ""Mobile 945GSE Express Memory Controller Hub""
00:02.0 ""VGA compatible controller"" ""Intel Corporation"" ""Mobile 945GSE Express Integrated Graphics Controller"" -r03 ""Hewlett-Packard Company"" ""Mobile 945GSE Express Integrated Graphics Controller""
00:02.1 ""Display controller"" ""Intel Corporation"" ""Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller"" -r03 ""Hewlett-Packard Company"" ""Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller""
00:1b.0 ""Audio device"" ""Intel Corporation"" ""NM10/ICH7 Family High Definition Audio Controller"" -r02 ""Hewlett-Packard Company"" ""NM10/ICH7 Family High Definition Audio Controller""
00:1c.0 ""PCI bridge"" ""Intel Corporation"" ""NM10/ICH7 Family PCI Express Port 1"" -r02 """" """"
00:1c.1 ""PCI bridge"" ""Intel Corporation"" ""NM10/ICH7 Family PCI Express Port 2"" -r02 """" """"
00:1d.0 ""USB controller"" ""Intel Corporation"" ""NM10/ICH7 Family USB UHCI Controller #1"" -r02 ""Hewlett-Packard Company"" ""NM10/ICH7 Family USB UHCI Controller""
00:1d.1 ""USB controller"" ""Intel Corporation"" ""NM10/ICH7 Family USB UHCI Controller #2"" -r02 ""Hewlett-Packard Company"" ""NM10/ICH7 Family USB UHCI Controller""
00:1d.2 ""USB controller"" ""Intel Corporation"" ""NM10/ICH7 Family USB UHCI Controller #3"" -r02 ""Hewlett-Packard Company"" ""NM10/ICH7 Family USB UHCI Controller""
00:1d.3 ""USB controller"" ""Intel Corporation"" ""NM10/ICH7 Family USB UHCI Controller #4"" -r02 ""Hewlett-Packard Company"" ""NM10/ICH7 Family USB UHCI Controller""
00:1d.7 ""USB controller"" ""Intel Corporation"" ""NM10/ICH7 Family USB2 EHCI Controller"" -r02 -p20 ""Hewlett-Packard Company"" ""NM10/ICH7 Family USB2 EHCI Controller""
00:1e.0 ""PCI bridge"" ""Intel Corporation"" ""82801 Mobile PCI Bridge"" -re2 -p01 """" """"
00:1f.0 ""ISA bridge"" ""Intel Corporation"" ""82801GBM (ICH7-M) LPC Interface Bridge"" -r02 ""Hewlett-Packard Company"" ""82801GBM (ICH7-M) LPC Interface Bridge""
00:1f.2 ""SATA controller"" ""Intel Corporation"" ""82801GBM/GHM (ICH7-M Family) SATA Controller [AHCI mode]"" -r02 -p01 ""Hewlett-Packard Company"" ""82801GBM/GHM (ICH7-M Family) SATA Controller [AHCI mode]""
01:00.0 ""Network controller"" ""Broadcom Limited"" ""BCM4312 802.11b/g LP-PHY"" -r01 ""Hewlett-Packard Company"" ""U98Z049.00 Wireless Mini PCIe Card""
02:00.0 ""Ethernet controller"" ""Qualcomm Atheros"" ""AR8132 Fast Ethernet"" -rc0 ""Hewlett-Packard Company"" ""AR8132 Fast Ethernet"""
1761996,2018-04-08 23:53:44 UTC,This has been fixed upstream.
1761998,2018-04-07 15:15:45 UTC,"I solved my connection problem as follows:
I edited the existing connection and changed the IPV4 settings to Automatic Address Only (DHCP), and then changed the DNS servers to 8.8.8.8,8.8.4.4 and solved the problem."
1761999,2018-09-08 15:13:38 UTC,"I had an ugly instance of this problem on an EPYC processor. Not sure what it was related to.
It all started with errors during package upgrades.
sudo apt-get update >> success
sudo apt-get upgrade >> segmentation fault
The upgrade left several packages in a half-installed state (attach Part 1), and basic os command started to crash (attach Part 2).
In the syslog I had ""general protection fault: 0000 [#1] SMP NOPTI"" with multiple processes, see a detail failure log in attach Part 3 and Part 4. Attach Part 5 lists numerous processes that had the same failure as Part 4.
The system load started to climb, from idle, progressively by about 1 point per 3-5 min, until levels like 20-30, at this point it was very difficult to enter and reboot the system. I tried and managed to have it respond with reboot -f but it had the problem still and system did not come up correctly, until we performed a physical shutdown and restart. From then the system seems clean. I corrected the packages by reinstallation, and so far no problem.
Very frightening!
Can it be related to some problem between Ubuntu and the Ryzen/EPYC technology?"
1761999,2019-03-06 10:48:00 UTC,Does this issue still happen on an up-to-date system?
1761999,2018-09-08 15:15:02 UTC,The logs have been anonymised. Problem started around the time 00:50
1761999,2018-04-12 21:34:14 UTC,So i removed virtualbox and guest dkms and installed Mainline 4.16.1-041601 and i conclude
1761999,2018-04-07 14:30:07 UTC,This change was made by a bot.
1761999,2018-04-10 15:39:39 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1761999,2018-04-10 16:34:27 UTC,"Will try to do so, but Friday at the earliest since I am not at home during
the week.
Hope I get it right with uninstalling VirtualBox and stuff and getting all
necessary packages for the mainline build."
1762005,2018-04-07 14:41:20 UTC,fix it
1762005,2018-04-07 14:54:48 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #927636, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1762010,2018-05-12 10:15:23 UTC,"As far as I know, support for BitLocker is already available on util-linux."
1762012,2018-04-07 16:21:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1762015,2018-04-07 16:15:09 UTC,"StacktraceTop:
 tcache_get (tc_idx=3) at malloc.c:2943
 __GI___libc_malloc (bytes=bytes@entry=65) at malloc.c:3050
 g_malloc (n_bytes=n_bytes@entry=65) at ../../../../glib/gmem.c:99
 g_strdup (str=0x7fe4f474a2e0 ""0fd9032e9ce4638848da711b59d9d5a13fb14efd83b4d5a811e9653ab20e7c8d"") at ../../../../glib/gstrfuncs.c:363
 g_value_dup_string (value=value@entry=0x7fe5037fd0c0) at ../../../../gobject/gvaluetypes.c:1136"
1762029,2018-05-08 18:16:45 UTC,This change was made by a bot.
1762031,2018-04-24 18:11:09 UTC,This issue was fixed in the openstack/glance 16.0.1 release.
1762031,2018-04-19 14:01:55 UTC,This issue was fixed in the openstack/glance 17.0.0.0b1 development milestone.
1762031,2018-04-10 18:41:16 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/560126"
1762031,2018-04-12 00:04:25 UTC,"Reviewed:  https://review.openstack.org/560126
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=b87a97832fe83313076ac338372390b05a9658c4
Submitter: Zuul
Branch:    stable/queens"
1762031,2018-04-07 18:26:35 UTC,https://review.openstack.org/559501
1762031,2018-04-10 18:37:26 UTC,"Reviewed:  https://review.openstack.org/559501
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=c48acba8404629c11bc16c7da99bc7a084e13b99
Submitter: Zuul
Branch:    master"
1762033,2020-05-15 13:12:19 UTC,"A similar bug is still present in 2.0.10, but fixed in 2.0.12: https://hg.libsdl.org/SDL/rev/6e17e1a6cf2e"
1762042,2018-04-07 18:28:44 UTC,format is incorrect while system language is English
1762042,2018-04-09 03:12:28 UTC,Does the problem go away after you reboot?
1762042,2018-04-21 11:51:07 UTC,"No, still exist"
1762042,2018-04-23 08:05:37 UTC,"Could you include the output of the command ""locale"" on the system which is displaying the wrong format?"
1762042,2018-04-23 08:22:38 UTC,"pisi@Pisi-U1804PC:~$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE=""en_US.UTF-8""
LC_NUMERIC=tr_TR.UTF-8
LC_TIME=tr_TR.UTF-8
LC_COLLATE=""en_US.UTF-8""
LC_MONETARY=tr_TR.UTF-8
LC_MESSAGES=""en_US.UTF-8""
LC_PAPER=tr_TR.UTF-8
LC_NAME=tr_TR.UTF-8
LC_ADDRESS=tr_TR.UTF-8
LC_TELEPHONE=tr_TR.UTF-8
LC_MEASUREMENT=tr_TR.UTF-8
LC_IDENTIFICATION=tr_TR.UTF-8
LC_ALL=
pisi@Pisi-U1804PC:~$"
1762042,2018-06-23 04:17:22 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1762042,2020-12-18 18:25:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762044,2018-04-17 12:48:58 UTC,"Reviewed:  https://review.openstack.org/560429
Committed: https://git.openstack.org/cgit/openstack/python-glanceclient/commit/?id=ae8d7d52c8b32f4c12fe75e8b788ee88da60fda9
Submitter: Zuul
Branch:    stable/queens"
1762044,2018-12-12 03:51:46 UTC,This issue was fixed in the openstack/python-glanceclient 2.10.1 release.
1762044,2018-04-11 13:55:47 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/560429"
1762044,2018-04-11 12:49:14 UTC,Change was cherry-picked to stable/queens: https://review.openstack.org/#/c/560126/
1762044,2018-04-08 18:53:40 UTC,Don't know if we want to backport to stable/queens or not; adding queens target here so we remember to look at it.  Depends on whether https://review.openstack.org/#/c/559501/ in glance is backported to stable/queens.
1762044,2018-04-08 18:51:14 UTC,Change proposed to master: https://review.openstack.org/#/c/559587/
1762044,2018-04-11 04:34:44 UTC,"Reviewed:  https://review.openstack.org/559587
Committed: https://git.openstack.org/cgit/openstack/python-glanceclient/commit/?id=e89fcae346eee1e3e5b5beb65e641fbc666fd59c
Submitter: Zuul
Branch:    master"
1762047,2018-04-07 19:18:37 UTC,"Also Flatpak app not run via gnome-software until reboot computer.
gnome-software shows ""Unable to launch Steam: ""localhost"" is not installed """
1762047,2018-04-07 19:24:25 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1762059,2018-04-07 20:25:16 UTC,Following discussions on IRC this might be related to the package
1762059,2018-04-18 04:32:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762069,2018-04-09 21:10:28 UTC,"It seems like this is something to add to the metadata.yaml aspect for
charms."
1762069,2018-04-09 11:08:40 UTC,John A Meinel <email address hidden> writes:
1762069,2018-04-09 22:27:19 UTC,Tim Penhey <email address hidden> writes:
1762069,2018-04-09 04:37:26 UTC,"They currently do have a way to expose payload versions (I'm running
""postgres 9.1.2"" for xenial/postgreqsl-25)"
1762069,2018-04-09 05:08:31 UTC,"For example, we could produce the hash of the charm contents, as a way to
define ""identity"". However, that wouldn't give you nice
human-understandable identifiers. And any other identifier that would be
human-readable would probably require some sort of process to make sure it
gets updated when it needs to (I changed the charm content, did you bump
the version number?) so that you can trust it accurately represents what
you want."
1762072,2018-08-23 14:48:55 UTC,Having exactly the same problem with Nextcloud-client snap under Ubuntu Budgie 18.04 (and also under 18.10)
1762073,2018-04-13 17:47:03 UTC,Fix proposed to master:  https://review.openstack.org/#/c/559503/
1762084,2018-09-17 08:10:24 UTC,"tweaks does not fully fixes the problem. In 16.04 I've had (and I've used) both functionalities: two-fingers tap and right bottom touchpad area click. Now if I enable area click in tweaks, the two-fingers tap stops working or vise-versa.
This is regression bug introduced in 18.04. Please, fix this, that right-click works for both cases."
1762084,2018-04-30 17:17:01 UTC,Are you runnng synaptics or libinput?
1762084,2018-08-29 11:25:14 UTC,Rectification: tapping does work but in a very small area. It needs a strong tap to work
1762084,2018-05-20 17:02:49 UTC,https://askubuntu.com/questions/1028757/touchpad-right-click-doesnt-work-on-touchpad-only-the-buttons-above-it-thinkp
1762084,2018-05-08 19:08:27 UTC,"I can confirm eyalliors report, adding that it only works in the most bottem-right place of the corner – I'd expect a larger click area (about 2x2cm)."
1762084,2018-05-05 20:02:58 UTC,"asus ux560u, upgraded from 17.10 to 18.10 today - have no right click. tweaks can emulate right click when TAPPING the right corner of the touchpad - but the touchpad has a physical right button that doesn't do anything."
1762084,2018-05-03 17:16:56 UTC,"Hello,
We try Synaptics and Libinput and the problem is same."
1762084,2018-05-02 04:20:49 UTC,I am only suggesting this because of my setup.
1762084,2018-05-01 07:35:05 UTC,I'm running Synaptics.
1762084,2018-04-30 17:04:16 UTC,Confirmed with Slimbook KatanaII and fresh install.
1762084,2018-08-29 11:19:56 UTC,Same problem as @eyallior and @fxedel: physical right button of touchpad doesn't work. In my case tapping right corner doesn't work neither.
1762084,2018-04-25 17:18:04 UTC,Great for pointing to a convenient solution. Not really a bug then (fortunately) but a (perhaps little?) configuration issue.
1762084,2018-04-29 19:36:28 UTC,"The ""select area"" solution does not work on the asus vivobook n580v laptop. Any suggestions?"
1762084,2018-04-09 08:47:50 UTC,Tweaks solved the problem for me.
1762084,2018-04-12 20:51:03 UTC,I have upgraded two notebooks (Asus UX360U and Jumper EZBook 3 Pro) and both now suffer from this issue (but in both cases two-finger tap still works).
1762084,2018-04-12 20:55:15 UTC,"Danny, what tweaks solved the problem for you?"
1762084,2018-04-08 12:29:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762084,2018-04-13 09:11:45 UTC,"Install/Open GNOME Tweaks
Go to Mouse and Keyboard
Under Mouse Click Emulation select Area."
1762084,2018-04-17 16:43:31 UTC,"Thanks Danny, as advised, GNOME Tweaks fixes the issue."
1762084,2018-04-18 08:14:50 UTC,You're welcome.
1762084,2018-04-13 09:11:03 UTC,"Install/Open GNOME Tweaks
Go to Mouse and Keyboard
Under Mouse Click Emulation select Area."
1762089,2018-04-12 09:28:19 UTC,And following panels too.
1762089,2021-02-04 10:42:14 UTC,This issue was fixed in the openstack/horizon 16.2.1 release.
1762089,2020-09-08 10:52:45 UTC,"Reviewed:  https://review.opendev.org/749291
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=63214ab177c0e4120558be5516709905b91cb6a8
Submitter: Zuul
Branch:    stable/train"
1762089,2020-09-01 14:12:10 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/749291"
1762089,2020-01-06 12:34:22 UTC,"Reviewed:  https://review.opendev.org/696321
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=ef4055e2888bb0fe67d64e9c422a31f925469200
Submitter: Zuul
Branch:    master"
1762089,2019-11-27 15:10:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/696321"
1762089,2019-11-27 14:39:23 UTC,"The problem is quite tricky and is only visible sometimes, but I think I have figured it out. The culprit is in this code: https://github.com/openstack/horizon/blob/3aa3cc934bf77fd656c53f160125ffa69b1e9b81/horizon/static/framework/conf/resource-type-registry.service.js#L397-L433"
1762089,2018-04-12 09:29:02 UTC,These panels show only second character....
1762089,2018-04-12 08:43:26 UTC,"Also, Admin - Container - Images panel shows ""m"" instead ""Images""."
1762089,2020-01-09 18:46:56 UTC,This issue was fixed in the openstack/horizon 18.0.0 release.
1762089,2018-04-12 08:27:31 UTC,"Australian English also shows ""o""."
1762089,2018-04-12 06:01:00 UTC,"But I could not find which project have such a translation on djangojs.po file. At least, Zun UI does not have such a translation on djangojs.po for en-gb."
1762089,2018-04-12 05:51:16 UTC,"@Hongbin,"
1762089,2018-04-12 04:06:40 UTC,"@Shu,"
1762089,2018-04-11 06:25:11 UTC,"@Hongbin,"
1762089,2018-04-12 08:41:20 UTC,".po files on horizon and zun seem to have no problem, and `gettext(""Containers"")` returns ""Containers"" as expected on chrome console."
1762089,2018-04-11 03:49:42 UTC,"@Shu,"
1762089,2018-04-09 04:42:08 UTC,"This title is set by https://github.com/openstack/zun-ui/blob/master/zun_ui/static/dashboard/container/containers/containers.module.js#L85 , and this will be translated by *.po files in https://github.com/openstack/zun-ui/tree/master/zun_ui/locale if language is set except English on horizon."
1762090,2018-04-08 02:11:19 UTC,"StacktraceTop:
 isBayer (pix_fmt=<optimized out>) at src/libswscale/swscale_internal.h:743
 sws_scale (c=0x0, srcSlice=0x55bc31c83670, srcStride=0x55bc31c836b0, srcSliceY=0, srcSliceH=180, dst=0x55bc31c83860, dstStride=0x55bc31c838a0) at src/libswscale/swscale.c:763
 SetTime(FFViewer&, double) ()
 GetRawFrame(double, FFViewer&) ()
 boost::detail::function::function_obj_invoker0<boost::_bi::bind_t<Glib::RefPtr<Gdk::Pixbuf>, Glib::RefPtr<Gdk::Pixbuf> (*)(double, FFViewer&), boost::_bi::list2<boost::_bi::value<double>, boost::reference_wrapper<FFViewer> > >, Glib::RefPtr<Gdk::Pixbuf> >::invoke(boost::detail::function::function_buffer&) ()"
1762092,2018-10-24 17:35:04 UTC,"Qt documentation says:
Note: Non-integer scale factors may cause significant scaling/painting artifacts.
http://doc.qt.io/qt-5/highdpi.html"
1762092,2018-10-24 17:43:48 UTC,"I've been using a scale factor of 3.0 since enabling Qt's automatic scaling in https://github.com/mixxxdj/mixxx/pull/1521 , so this doesn't personally affect me anymore."
1762096,2018-04-08 12:01:57 UTC,The biggest question is how to make it feel natural. Maybe we need a kind of touch handle.
1762096,2018-06-12 02:31:37 UTC,Pushing this to 2.3.0 so I can focus on the library redesign branch.
1762110,2018-04-19 21:04:12 UTC,This issue was fixed in the openstack/puppet-openstack_extras 13.0.0 release.
1762113,2018-04-11 04:47:50 UTC,"I'm adding a comment here as I have new information. I discovered a tpm_crb-driven tpm implementation on a laptop running Bionic (ASUS ZenBook UX360CAK). Now that I happened to test tpm2-tools on it, I discovered that:"
1762115,2019-12-22 23:00:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762115,2020-07-01 20:59:24 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1762119,2018-04-26 03:13:17 UTC,This bug was not fixed in bionic-final 0425 version
1762119,2018-09-23 08:23:49 UTC,This bug was fixed in the package ukui-control-center - 1.1.5-0ubuntu1
1762130,2018-04-18 07:56:17 UTC,"Reviewed:  https://review.openstack.org/559559
Committed: https://git.openstack.org/cgit/openstack/os-xenapi/commit/?id=6953134a1348e6cfce3166262ed5f4768ef37cf9
Submitter: Zuul
Branch:    master"
1762130,2018-04-08 07:20:27 UTC,six module is installed via rpm python-six-1.9.0-2.el7.noarch; this RPM is installed in XS7.1. But unfortunately it's not included in XS7.0.
1762130,2018-04-08 07:20:51 UTC,"Even in XS7.1, there is also a dependence issue:
[root@xrtuk-11-13 plugins]# python -m agent.py
/usr/bin/python: No module named future"
1762130,2018-04-08 09:27:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559559"
1762152,2018-04-17 13:51:45 UTC,"There is only one report and it doesn't seem like a release concern at this point even if it would be interesting to investigate. The mac-address option doesn't sound like it should have an effect, could you try if just restarting network-manager without changing the config has the same impact?"
1762152,2018-11-07 17:49:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762154,2018-04-08 10:42:16 UTC,"StacktraceTop:
 load_module (menubar=0x562cdd507870, name=0x562cdd518043 ""libapplication.so"") at applet-main.c:594
 load_modules (indicators_loaded=<synthetic pointer>, menubar=0x562cdd507870) at applet-main.c:639
 applet_fill_cb (applet=applet@entry=0x562cdd19a400, iid=<optimized out>, data=<optimized out>) at applet-main.c:1013
 mate_panel_applet_marshal_BOOLEAN__STRING (closure=0x562cdd1be6a0, return_value=0x7ffc8a9f8280, n_param_values=<optimized out>, param_values=0x7f243400f360, invocation_hint=<optimized out>, marshal_data=<optimized out>) at mate-panel-applet-marshal.c:122
 g_closure_invoke (closure=0x562cdd1be6a0, return_value=0x7ffc8a9f8280, n_param_values=2, param_values=0x7f243400f360, invocation_hint=0x0) at ../../../../gobject/gclosure.c:804"
1762154,2018-04-21 01:45:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762163,2020-03-15 20:33:48 UTC,Thank you Claudio Lanconelli for your post #6 which indicated where a patch could be found.
1762163,2019-09-06 23:44:18 UTC,"The bug is fixed in solid 5.46, back port it to 5.44 for bionic 18.04 LTS, please"
1762163,2020-03-26 16:08:50 UTC,Thanks Claudio for confirming that my PPA with the upstream Solid patch fixes the issue.
1762163,2020-03-26 09:16:30 UTC,"I tried your PPA and it fixes the issue, thank you Curtis."
1762163,2018-08-21 08:26:54 UTC,"FYI, I have this problem with ext4 formatted USB drives, not with fat32 drives."
1762163,2020-02-17 19:57:13 UTC,"This issue with mounting and displaying ""Malformed URL"" is still a problem with Kubuntu 18.04.4 LTS Bionic Beaver with all updates applied as of today (Feb 17, 2020)."
1762163,2018-05-19 18:49:10 UTC,I updated KDE to 5.12.5 from Backports PPA and problem is still persists.
1762163,2018-07-23 09:19:13 UTC,I have just completed a fresh installed of Kubuntu 18.04 which contains Plasma version 5.12.6. The problem is still present.
1762163,2018-05-19 18:11:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762163,2018-05-03 21:50:08 UTC,"The is an update:
https://bugs.kde.org/show_bug.cgi?id=370975"
1762164,2019-05-14 21:07:39 UTC,I think the branch wlwebsite_py36 is mature now.
1762164,2019-04-13 08:30:39 UTC,"Ubuntu 18.04 ships python 3.6 and i ask janus how long will it will take to set up a server. He told me he needs approximately 1 hour. So once a server decision was made, i assume switching to the new server can be made in one or two weeks."
1762164,2019-04-11 07:45:01 UTC,I don't think so - your plan sounds OK.
1762164,2019-04-10 20:41:38 UTC,Working on the port to python3 is independent from the server. But the difficulties i have is to get the changes into a branch. Form what i know i can't run the 2to3 script to read and write the same file file in one go. So my plan is to:
1762164,2019-04-10 16:53:19 UTC,Maybe this can be coordinated with SirVer for the server move? We wouldn't have this problem then.
1762164,2019-04-09 06:48:06 UTC,"Since python3.6 can not be installed on Ubuntu 14.04, we may have to use a ppa for that:"
1762164,2019-03-03 11:32:07 UTC,pip warning:
1762164,2019-03-02 11:13:52 UTC,Markdown text in topic preview
1762164,2019-02-27 17:18:20 UTC,"@janus: Das ist teil vom pybb_cleanup, und ich wusste sonst nicht wohin damit ;)"
1762164,2019-02-27 16:43:08 UTC,"I like your attachment version. Jut make sure that the text will automatically break into multiple lines when the screen gets small, just like with the topic title."
1762164,2019-04-06 09:40:31 UTC,Because using python 3.4 in combination with mysqlclient through an error:
1762164,2019-02-27 16:27:28 UTC,I want to exchange the last column in the topics lists. Currently we have:
1762164,2018-11-08 11:12:37 UTC,Downtime it is then. Your time is too valuable.
1762164,2018-11-07 22:19:15 UTC,"I have try'd a lot to get a VM to work with Ubuntu server working. Sometimes it works, sometimes not. It took me a lot of time to find the reason: For some reason the VM only works if i reboot the host... It seems a 'cold' boot (after disconnecting power) does not apply all capabilities. No idea why ... Booting twice my main machine (host) to get the VM to work, let me discourage the initial idea. Sorry, there is a lot of other stuff to do... So the idea to set up a VM to speed up the downtime was only made for other people as a proposal ;-)"
1762164,2018-11-06 13:28:36 UTC,Sounds like a good idea if your computer is fast enough :)
1762164,2018-11-06 07:13:31 UTC,"Sounds like a 12 hour job... Installing linux isn't really time consuming, in comparison with windows. I guess most of the time will be needed to install the needed additional packages, recreating the virtualenvironments and adjusting the start scripts."
1762164,2018-11-05 21:17:41 UTC,"Support for Ubuntu 14.4 runs out in the first quarter of 2019. We must update the server to bionic beaver (18.04 LTS). The last time I did update the server, it went absolutely fine with in-place update, however this time it is better to restore from backup after reinstall. This is a lot of work, unfortunately :("
1762164,2018-11-05 17:51:03 UTC,The server runs with Ubuntu 14.04.5 LTS
1762164,2018-11-02 15:17:48 UTC,"Ubuntu Bionic (18.04) has Python 3.6, so that's definitely an option."
1762164,2018-11-02 11:11:07 UTC,Turns that this task is a bit difficult for me :-D :
1762164,2019-02-27 16:42:19 UTC,die idee find ich gut aber ist dieser bug der richtige ort dafür?
1762167,2019-07-29 16:32:41 UTC,*** Bug 410334 has been marked as a duplicate of this bug. ***
1762167,2019-06-16 02:25:18 UTC,*** Bug 408759 has been marked as a duplicate of this bug. ***
1762167,2019-06-07 07:36:05 UTC,*** Bug 408406 has been marked as a duplicate of this bug. ***
1762167,2019-05-19 08:32:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762167,2019-04-19 12:13:41 UTC,*** Bug 406026 has been marked as a duplicate of this bug. ***
1762167,2019-04-10 13:04:47 UTC,This bug still exists in Ubuntu 19.04/disco in this package version:
1762167,2019-03-04 05:52:43 UTC,"Created attachment 118522
New crash information added by DrKonqi"
1762167,2019-03-12 21:44:35 UTC,*** Bug 405407 has been marked as a duplicate of this bug. ***
1762167,2019-03-12 11:52:57 UTC,*** Bug 404670 has been marked as a duplicate of this bug. ***
1762167,2019-01-27 12:49:08 UTC,*** Bug 403016 has been marked as a duplicate of this bug. ***
1762167,2019-03-03 18:53:58 UTC,"Created attachment 118516
New crash information added by DrKonqi"
1762167,2019-07-30 17:13:22 UTC,"Created attachment 121845
New crash information added by DrKonqi"
1762167,2019-03-27 11:08:04 UTC,"Created attachment 119080
New crash information added by DrKonqi"
1762167,2019-09-01 02:24:08 UTC,*** Bug 411222 has been marked as a duplicate of this bug. ***
1762167,2020-07-14 22:07:00 UTC,*** Bug 422071 has been marked as a duplicate of this bug. ***
1762167,2019-09-29 20:33:07 UTC,"Git commit b819ef6a35495e12a204cbb241cdb2502c4cd11e by Valerii Malov.
Committed on 29/09/2019 at 20:31.
Pushed by valeriymalov into branch '5.1'."
1762167,2019-10-06 19:21:56 UTC,Would anybody be able to compile this and check if crash on exit is fixed?
1762167,2019-12-27 18:40:55 UTC,I can confirm that this bug has been fixed.
1762167,2019-12-27 18:41:31 UTC,*** Bug 392256 has been marked as a duplicate of this bug. ***
1762167,2019-12-27 18:42:59 UTC,*** Bug 405610 has been marked as a duplicate of this bug. ***
1762167,2019-12-27 18:46:09 UTC,*** Bug 415247 has been marked as a duplicate of this bug. ***
1762167,2020-01-13 11:36:24 UTC,*** Bug 415645 has been marked as a duplicate of this bug. ***
1762167,2020-02-13 19:23:43 UTC,*** Bug 416518 has been marked as a duplicate of this bug. ***
1762167,2020-04-21 09:22:57 UTC,"For me the bug is fixed, no crash when closing ktorrent (version 5.1.2)."
1762167,2020-05-20 09:36:21 UTC,Thanks for the update; changing status.
1762167,2020-05-20 10:26:57 UTC,"(In reply to Christoph Feck from comment #53)

> Thanks for the update; changing status.
>
> The fix is not in v5.1.2, but might have been backported by the
> distribution. See comment 44 for the commit.
"
1762167,2020-07-14 22:07:25 UTC,*** Bug 423523 has been marked as a duplicate of this bug. ***
1762167,2021-02-20 04:16:48 UTC,"Created attachment 135931
New crash information added by DrKonqi"
1762167,2018-11-07 11:03:55 UTC,*** Bug 400392 has been marked as a duplicate of this bug. ***
1762167,2019-09-09 14:49:48 UTC,*** Bug 411002 has been marked as a duplicate of this bug. ***
1762167,2018-10-05 23:29:23 UTC,*** Bug 399411 has been marked as a duplicate of this bug. ***
1762167,2018-05-17 03:36:25 UTC,*** Bug 393785 has been marked as a duplicate of this bug. ***
1762167,2018-09-12 14:01:13 UTC,*** Bug 398145 has been marked as a duplicate of this bug. ***
1762167,2017-08-04 15:14:00 UTC,Application: ktorrent (5.0.1)
1762167,2017-11-30 12:38:41 UTC,"Created attachment 109128
New crash information added by DrKonqi"
1762167,2017-12-10 13:56:17 UTC,*** Bug 387669 has been marked as a duplicate of this bug. ***
1762167,2017-12-10 13:57:04 UTC,*** Bug 384476 has been marked as a duplicate of this bug. ***
1762167,2017-12-10 13:57:55 UTC,*** Bug 387754 has been marked as a duplicate of this bug. ***
1762167,2017-12-10 14:00:14 UTC,*** Bug 385766 has been marked as a duplicate of this bug. ***
1762167,2017-12-10 14:02:30 UTC,*** Bug 385543 has been marked as a duplicate of this bug. ***
1762167,2018-01-02 18:42:02 UTC,*** Bug 387945 has been marked as a duplicate of this bug. ***
1762167,2018-01-02 18:42:21 UTC,*** Bug 387927 has been marked as a duplicate of this bug. ***
1762167,2018-01-02 18:42:54 UTC,*** Bug 385761 has been marked as a duplicate of this bug. ***
1762167,2018-01-10 09:55:29 UTC,"Created attachment 109780
New crash information added by DrKonqi"
1762167,2018-02-22 01:32:07 UTC,*** Bug 390157 has been marked as a duplicate of this bug. ***
1762167,2018-02-22 01:32:26 UTC,*** Bug 389915 has been marked as a duplicate of this bug. ***
1762167,2017-12-26 12:21:15 UTC,"Created attachment 109528
New crash information added by DrKonqi"
1762167,2018-02-27 16:34:40 UTC,"Created attachment 111054
New crash information added by DrKonqi"
1762167,2018-02-26 18:18:25 UTC,"Created attachment 111024
New crash information added by DrKonqi"
1762167,2018-09-05 03:19:52 UTC,*** Bug 397327 has been marked as a duplicate of this bug. ***
1762167,2018-09-04 12:05:48 UTC,"To anyone still having this issue, do you use ""scan folders"" plugin and does disabling it fix the crash on exit (or it crashes ktorrent too when you disable the plugin)?"
1762167,2018-07-28 11:53:11 UTC,"Created attachment 114174
New crash information added by DrKonqi"
1762167,2018-07-20 02:20:57 UTC,*** Bug 395907 has been marked as a duplicate of this bug. ***
1762167,2018-05-17 03:37:23 UTC,*** Bug 394111 has been marked as a duplicate of this bug. ***
1762167,2018-09-09 02:17:54 UTC,"(In reply to Valeriy Malov from comment #24)

> To anyone still having this issue, do you use ""scan folders"" plugin and does
> disabling it fix the crash on exit (or it crashes ktorrent too when you
> disable the plugin)?
"
1762167,2018-10-03 11:11:08 UTC,*** Bug 399330 has been marked as a duplicate of this bug. ***
1762167,2018-05-17 03:36:00 UTC,*** Bug 393572 has been marked as a duplicate of this bug. ***
1762167,2018-04-08 12:43:29 UTC,"StacktraceTop:
 bt::TorrentInterface::getDisplayName (this=0x563791af8990) at /usr/include/KF5/libktorrent/interfaces/torrentinterface.h:426
 kt::ViewModel::Item::data (this=0x563791eadaa0, col=<optimized out>) at ./ktorrent/view/viewmodel.cpp:212
 kt::ViewModel::data (this=<optimized out>, index=..., role=<optimized out>) at ./ktorrent/view/viewmodel.cpp:648
 QModelIndex::data (arole=0, this=0x7ffecb875080) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:432
 QStyledItemDelegate::initStyleOption (this=0x563791eb49d0, option=0x7ffecb874ef0, index=...) at itemviews/qstyleditemdelegate.cpp:345"
1762167,2018-03-17 11:22:41 UTC,*** This bug has been confirmed by popular vote. ***
1762167,2018-03-16 19:00:32 UTC,"Created attachment 111449
New crash information added by DrKonqi"
1762167,2018-05-17 03:36:54 UTC,*** Bug 392831 has been marked as a duplicate of this bug. ***
1762170,2018-04-09 17:41:53 UTC,"Hi,"
1762170,2018-04-09 03:07:57 UTC,"Generate .map files for both, and compare them to locate the difference."
1762170,2018-04-09 17:21:14 UTC,I did .lst file compare and part of that diff is in attachment
1762170,2018-04-12 11:20:14 UTC,Okay. Will prepare in a couple of days.
1762170,2018-04-13 20:12:12 UTC,"It's strange, but looks like it's only affected in a big project. I've found that function ErrQtnProper differs in ""big"" binaries, but when i compliles it separatelly binaries are the same."
1762170,2020-02-26 11:52:58 UTC,"Hi qmor,"
1762170,2020-02-26 18:20:02 UTC,"Can't do work example on small project (< 1000 lines). Will prepare better and maybe then reopen bug with good example.
This bug may be closed now. Sorry and thanks."
1762172,2018-07-20 13:44:39 UTC,"ok, it sounds the same like Reloop did.
The center Led means, no ultra pitch offset.
I think we can provide controls for both interfaces.
How would this be presented in skins?"
1762172,2018-07-20 12:03:57 UTC,"I think that's the turntable my friend referred to and the feature is called Ultra Pitchfader: Vestax PDX2000
https://www.emusician.com/gear/vestax-pdx-2000"
1762172,2018-07-20 14:35:21 UTC,"I think we need two things:
1) an optional 2nd ultra pitch fader that shifts the pitch range
2) labels for the regular pitch fader that display the lower & upper limit.
any pitch range offset is visible then even if the ultra pitch fader is hidden."
1762172,2018-07-20 05:33:21 UTC,"We already have the rateRange control. However this is not scaled well to fit on a knob control.
It sounds as if this does not suite, right?
It sounds as if the knob is a coarse rate slider that keeps the normal rate slider on 8 %."
1762172,2018-08-01 07:06:08 UTC,the second step is here: https://github.com/mixxxdj/mixxx/pull/1767
1762172,2018-07-20 05:40:59 UTC,"These buttons are already possible.
https://www.amazona.de/test-reloop-rp-7000mk2-dj-plattenspieler/3/
But are we able to fully emulate this turntable? What does the center led?"
1762172,2018-07-25 21:23:50 UTC,"first step is done:
https://github.com/mixxxdj/mixxx/pull/1765"
1762174,2018-04-08 15:31:39 UTC,"While doing a quick test I noticed it's not possible to use [Controls],RateRangePercent or [ChannelN],rateRange for visibility connections in skins or use them directly for <Number>"
1762179,2018-04-29 23:55:54 UTC,"I am getting the same errors while doing a ""replay"". Are there any updates on the resolution/fix ?"
1762179,2018-04-30 12:14:44 UTC,"@arna35: I have tested this yet unmerged patch: https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg04286.html and it solves this problem, I will close this issue once it gets merged."
1762179,2018-05-01 01:19:46 UTC,"@Ciro,"
1762179,2020-11-10 15:45:38 UTC,Looks like the patches have been merged now (see commit cda382594b7ea50aff5f672f32767f9f9fef4c12 and earlier)
1762179,2020-12-10 09:16:59 UTC,Released with QEMU v5.2.0.
1762180,2018-04-09 08:03:35 UTC,"In your previous Bug Report #1761990 you wrote ""i have downloaded ir simulator but not working properly please help me so that i can play game"""
1762184,2018-04-08 17:26:43 UTC,"Running testing - that's buster, right?"
1762184,2018-04-08 14:41:32 UTC,"From the version numbers you report I presume you are running buster, can you confirm that?"
1762190,2018-12-18 11:27:31 UTC,"The message is scary, but it's not really a problem; snapd will retry later."
1762190,2018-12-18 11:17:30 UTC,"restarting the snapd service helped in my case:
sudo systemctl restart snapd
(credit https://askubuntu.com/questions/851810/unable-to-install-snap-package)"
1762190,2018-05-12 11:41:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762194,2018-09-19 14:11:50 UTC,The bug report was moved to https://github.com/Stellarium/stellarium/issues/374
1762194,2018-04-08 16:04:55 UTC,"Different catalog, different result..."
1762194,2018-04-08 17:46:33 UTC,Thank you for your quick a answer.
1762194,2018-04-08 18:28:42 UTC,"One task ""somebody"" should do in the next 5 years or so is switching to Gaia data. In this process, we should think about best non-positional data as well. Volunteers welcome."
1762195,2018-04-10 20:53:23 UTC,"Agreed, we probably shouldn't show if we're not admin."
1762215,2018-04-30 18:04:02 UTC,"It appears that the crash does not happen any more even though the wvdial package version remains the same as before. Possibly some condition has changed, not sure what (library versions is one possibility)."
1762215,2018-08-13 18:04:34 UTC,"After disappearing for a while, the problem re-appeared."
1762215,2020-05-22 13:50:40 UTC,"This is still reproducible in Bionic 18.04, but not on the latest Focal 20.04"
1762217,2018-04-12 17:22:18 UTC,"Same problem detected in the ""2018-04-12"" iso"
1762217,2018-04-11 13:13:32 UTC,"Same problem detected in the ""2018-04-11 08:03"" iso"
1762217,2018-04-10 14:29:49 UTC,"Same problem detected in the ""2018-04-10 08:03"" iso"
1762217,2018-04-08 17:40:20 UTC,"I also note that during these 3 months (or more) of testing I had several problems related to the nouveal and nvidia drivers available in the ""devel"" repositories for bionic."
1762217,2018-04-09 14:04:33 UTC,"Same problem detected in the ""2018-04-09 07:58"" iso"
1762222,2018-04-08 18:54:36 UTC,"You are using a version that is years old. Update to the newest version. You can do that by either installing it from http://damonlynch.net/rapid/download.html , or waiting until 18.04 is released and installing the version found in that in release."
1762222,2018-10-20 00:40:28 UTC,"for the record, i see the same behavior in debian with 0.9.9 and 0.9.12. By default, RPD does not mount the sdcard automatically, i need to start Thunar or some file manager and click on the device to have it mounted. then RPD can see it and operate normally. i always thought that feature was just not implemented."
1762235,2018-04-08 19:13:50 UTC,"StacktraceTop:
 g_hash_table_iter_init (iter=iter@entry=0x7ffc4658f660, hash_table=0x3838342032313132) at ../../../../glib/ghash.c:769
 nm_ip_address_dup (address=<optimized out>) at libnm-core/nm-setting-ip-config.c:388
 g_boxed_copy (boxed_type=94466899797584, src_boxed=src_boxed@entry=0x55eaca1a7c60) at ../../../../gobject/gboxed.c:343
 gjs_boxed_from_c_struct (context=context@entry=0x55eac8284a00, info=info@entry=0x55eaca90da80, gboxed=0x55eaca1a7c60, flags=<optimized out>) at gi/boxed.cpp:1235
 gjs_value_from_g_argument (context=context@entry=0x55eac8284a00, value_p=..., type_info=type_info@entry=0x55eacb36c540, arg=arg@entry=0x7ffc4658fb08, copy_structs=copy_structs@entry=true) at gi/arg.cpp:2909"
1762235,2018-04-09 03:01:00 UTC,I can't find any other reports of this crash right now.
1762235,2018-04-17 16:05:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762235,2019-06-19 01:47:10 UTC,Tracking in: https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10
1762235,2020-11-16 08:15:26 UTC,Zero crashes after 19.04 so consider it fixed.
1762236,2018-04-08 20:22:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1762238,2019-05-11 11:50:32 UTC,Fixed in Bionic.
1762238,2019-05-11 11:53:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762259,2018-05-27 10:17:47 UTC,"Yes Ubuntu is not booting without settings nomodeset in grub, generally in Old desktop.
Working fine in my Laptop"
1762259,2018-04-30 16:27:25 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=105911
1762259,2018-05-13 16:29:50 UTC,This bug is fixed on Fedora 28. I've also tested the Opensuse Tumbleweed but their distro kernel also has this bug
1762259,2018-04-26 06:52:22 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu"
1762259,2018-06-06 14:32:38 UTC,But Fedora also uses grub...
1762259,2018-04-26 01:01:38 UTC,I can confirm the issue persists with the latest linux kernel
1762259,2018-04-10 15:37:27 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1762259,2018-04-08 23:00:07 UTC,This change was made by a bot.
1762259,2018-04-26 01:04:25 UTC,"Technically the system boots, but nothing is displayed"
1762259,2018-06-06 14:34:52 UTC,"It's easy to get the patches from Fedora and apply them on Ubuntu, isn't it?"
1762287,2018-04-10 22:46:30 UTC,I was just assuming that XDG_CURRENT_DESKTOP wasn't being set there at all (it's not really a desktop) but I didn't test it.
1762287,2018-08-15 20:14:19 UTC,You can use this in initial-setup.json:
1762287,2018-04-10 21:40:57 UTC,I applied the part of the patch that shows the account/password screens in new user mode. For the XDG_CURRENT_DESKTOP check - should we make GDM set this to ubuntu:GNOME? I think that makes more sense. Not sure where this is set though.
1762289,2018-04-09 00:41:25 UTC,"StacktraceTop:
 _dbus_abort () at ../../../dbus/dbus-sysdeps.c:93
 _dbus_warn_check_failed (format=format@entry=0x7f7981ed57c8 ""arguments to %s() were incorrect, assertion \""%s\"" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n"") at ../../../dbus/dbus-internals.c:281
 _dbus_warn_return_if_fail (function=function@entry=0x7f7981ed1070 <__func__.6104> ""dbus_connection_get_data"", assertion=assertion@entry=0x7f7981ed0346 ""connection != NULL"", file=file@entry=0x7f7981ed07b0 ""../../../dbus/dbus-connection.c"", line=line@entry=6079) at ../../../dbus/dbus-internals.c:936
 dbus_connection_get_data (connection=connection@entry=0x0, slot=<optimized out>) at ../../../dbus/dbus-connection.c:6079
 atspi_dbus_connection_setup_with_g_main (connection=0x0, context=0x558734bea3d0, context@entry=0x0) at ../atspi/atspi-gmain.c:549"
1762289,2018-04-10 14:27:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762294,2018-06-24 14:18:03 UTC,"I think the M-Bus is generally a good option for anybody with a spare channel they can use, even if not obvious and may confuse some people at first (better documentation may help but definitely not for everybody.) But still this is not going to fix it for anybody using a two channel mixer, like the VMS2 owners who opened the threads/Bugs linked above."
1762294,2018-06-24 12:23:10 UTC,I may forget about this if it is not assigned to a milestone.
1762294,2018-06-24 11:34:04 UTC,This is still not confirmed.
1762294,2018-04-15 19:46:19 UTC,"I have removed it from the 2.2 milestone, because we should not implement it.
We have already a sufficient solution."
1762294,2018-04-15 14:41:46 UTC,"Why did you remove this from the 2.2 milestone? I would prefer a new contributor to take care of this, but I can if no one does before the 2.2 feature freeze."
1762294,2018-04-09 16:14:21 UTC,In neither of those forum threads are users asking for crossfader bus outputs. They are asking to send samplers to an external mixer. Many mixers that do not have a dedicated sampler input have an auxiliary input that could be used for this purpose. Bug #970965 is also asking for this but proposing a bad way of implementing it.
1762294,2018-04-09 21:41:35 UTC,"Why do you think that a bad way? It just works.
The m-bus is you sampler bus but nice configurable."
1762294,2018-04-09 13:23:57 UTC,"I can find only two old forum threads on the topic:
https://mixxx.org/forums/viewtopic.php?f=3&t=4148
https://mixxx.org/forums/viewtopic.php?f=3&t=7937"
1762294,2018-04-09 11:58:00 UTC,That does not make sense and I am sceptical anyone is actually doing that. What is the use of sending two decks to the same mixer channel when the EQs and volume fader are coupled for both decks?
1762294,2018-04-09 11:44:08 UTC,"They are necessary, if you want to use four decks with a two stereo channels sound card and a hardware Mixer. This is quite handy, because you just replace the internal crossfaded with an external.If you choose the deck outputs, you have just two decks."
1762294,2018-04-09 10:47:06 UTC,"I don't understand why we have crossfader bus outputs. I couldn't imagine a user figuring out they could send samplers to a mixer with the center crossfader bus output. Also, what if the hardware mixer lets the user assign samplers to the mixer's crossfader? That would get really confusing."
1762294,2018-04-09 06:07:41 UTC,"I am not sure if we really need a sampler output bus. This would be an artificial beast just for a single use case.
We have already the mid bus. I think that should be sufficient, or do I miss something?"
1762294,2018-04-09 15:30:54 UTC,This is the original bug Introducing the xfader busses https://bugs.launchpad.net/bugs/970965
1762295,2018-04-11 02:08:10 UTC,Code submitted here.
1762308,2018-04-09 06:05:39 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1762311,2018-07-13 06:20:59 UTC,"Reviewed:  https://review.openstack.org/559668
Committed: https://git.openstack.org/cgit/openstack/proliantutils/commit/?id=f3db9b7c8adc08c7ef32eb55e114a9fee4fe77a5
Submitter: Zuul
Branch:    master"
1762311,2018-07-16 04:10:34 UTC,"Reviewed:  https://review.openstack.org/561124
Committed: https://git.openstack.org/cgit/openstack/proliantutils/commit/?id=ffe1e61cf2bcae5dcfb523a7b81089d359148156
Submitter: Zuul
Branch:    master"
1762314,2018-09-11 13:25:19 UTC,"The same issue here. Different videos, different volume. In general very low."
1762314,2018-09-11 22:30:17 UTC,"For the T570, I seem to have resolved the issue by installing the HDA DKMS driver from the ALSA Daily Build Snapshots here:"
1762314,2018-09-10 11:00:23 UTC,"Same issue here on T570 running Manjaro, this is the only bug report talking about the problem which seems not related to Ubuntu but to alsa. All sliders are up in alsamixer, sound is around half-volume compared to the Windows install. ALSA Driver Version: k4.14.67-1-MANJARO.
these did not help: https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture/Troubleshooting#Volume_is_too_low"
1762314,2018-09-04 12:18:26 UTC,"Originally had this issue on my ThinkPad T570 running Ubuntu 16.04 and added a bug report to this issue. Yesterday, I upgraded to Ubuntu 18.04 and the problem still exists. Please advise if additional detail would be useful."
1762314,2018-06-11 01:40:09 UTC,"Identical symptoms, package version, distro version, also ALC298, also tried windows, only difference is computer model (Lenovo T570). Confirmed on two identical computers with identical setups. Sorry, don't know how to generate a new report or add debug info."
1762314,2018-06-11 01:03:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762314,2018-07-12 20:06:16 UTC,"This looks like an Alsa-driver bug, I have the same hardware but I'm using Arch Linux and I have the exact same problem. Don't know also to generate all these reports if anyone wants more details just tell me."
1762316,2018-06-04 14:35:59 UTC,This issue was fixed in the openstack/python-magnumclient 2.9.1 release.
1762316,2018-08-06 21:07:43 UTC,This issue was fixed in the openstack/python-magnumclient 2.10.0 release.
1762316,2018-05-07 13:10:22 UTC,"patches to python-magnumclient (master and Queens) and python-zunclient (master) have been merged.
(https://review.openstack.org/#/q/topic:bug/1762316)"
1762316,2018-05-04 09:24:11 UTC,"magnumclient had wrong entrypoints to its classes for OSC plugin, is being fixed in https://review.openstack.org/#/c/566245/"
1762316,2018-04-16 12:53:45 UTC,"thanks a lot Amir, this workaround works well!"
1762316,2018-04-09 13:32:31 UTC,"Although the ""complete"" command is provided by the framework, it is up to the plugins and users of cliff to set things up properly. If cliff eats the exception developers won't see it."
1762316,2018-04-11 14:10:26 UTC,"python2-designateclient-2.9.0-0.20180211221136.65cc292.el7.centos.noarch
python2-magnumclient-2.9.0-0.20180305153838.1385866.el7.centos.noarch
python2-muranoclient-1.0.1-0.20180216002752.2944800.el7.centos.noarch
python2-keystoneclient-3.15.0-0.20180211175653.1e8c930.el7.centos.noarch
python-ironic-inspector-client-3.1.1-0.20180314115502.c65ff94.el7.centos.noarch
python2-ncclient-0.4.7-5.el7.noarch
python2-manilaclient-1.21.0-0.20180211215650.27c189f.el7.centos.noarch
puppet-ipaclient-2.5.2-0.20180216000114.b086731.el7.centos.noarch
dhclient-4.2.5-58.el7.centos.3.x86_64
python2-glareclient-0.5.2-0.20180219215809.6da299f.el7.centos.noarch
python2-tackerclient-0.11.0-0.20180211231620.8509a59.el7.centos.noarch
python-websocket-client-0.34.0-3.el7.noarch
python2-novaclient-9.1.1-0.20180213141814.a1c0074.el7.centos.noarch
python2-openstackclient-3.14.1-0.20180402185834.a3caf7b.el7.centos.noarch
python2-os-client-config-1.29.0-0.20180211214132.ed71a59.el7.centos.noarch
python2-octaviaclient-1.4.0-0.20180219220313.830e49f.el7.centos.noarch
python2-zaqarclient-1.9.0-0.20180211232746.c1689bf.el7.centos.noarch
cups-client-1.6.3-29.el7.x86_64
python-openstackclient-lang-3.14.1-0.20180402185834.a3caf7b.el7.centos.noarch
openssh-clients-7.4p1-13.el7_4.x86_64
glusterfs-client-xlators-3.8.4-18.4.el7.centos.x86_64
python2-ceilometerclient-2.9.0-0.20180210123537.3b4e35a.el7.centos.noarch
python2-troveclient-2.14.0-0.20180216003748.e30e8db.el7.centos.noarch
python-dracclient-1.3.2-0.20180326174322.a8ef5bf.el7.centos.noarch
python2-gnocchiclient-7.0.1-0.20180213170923.e35af68.el7.centos.noarch
python2-heatclient-1.14.0-0.20180213175737.2ce6aa1.el7.centos.noarch
python2-mistralclient-3.3.0-0.20180215125917.1008e4e.el7.centos.noarch
python-tripleoclient-9.2.1-0.20180410161616.1c1af2a.el7.centos.noarch
libvirt-client-3.2.0-14.el7_4.9.x86_64
python2-monascaclient-1.10.0-0.20180213171455.5ea9035.el7.centos.noarch
python2-saharaclient-1.5.0-0.20180213173808.ee5f173.el7.centos.noarch
python2-ironicclient-2.2.0-0.20180211230646.683b7c6.el7.centos.noarch
python2-cinderclient-3.5.0-0.20180211213738.1de605c.el7.centos.noarch
python2-barbicanclient-4.6.0-0.20180211180442.262025b.el7.centos.noarch
python2-senlinclient-1.7.0-0.20180213202846.e6cdf2d.el7.centos.noarch
python2-glanceclient-2.9.1-0.20180211173704.b982516.el7.centos.noarch
dibbler-client-1.0.1-0.RC1.2.el7.x86_64
python2-aodhclient-1.0.0-0.20180211222211.86ac8fd.el7.centos.noarch
python2-scciclient-0.6.1-0.20180213201842.6c3c54f.el7.centos.noarch
python2-swiftclient-3.5.0-0.20180211175153.b91651e.el7.centos.noarch
python2-neutronclient-6.7.0-0.20180211221651.95d64ce.el7.centos.noarch
docker-client-1.13.1-53.git774336d.el7.centos.x86_6"
1762316,2018-04-10 05:47:07 UTC,I have reinstalled the undercloud again and that is the version i get with the error.
1762316,2018-04-16 12:08:40 UTC,"Hi Noam,
Yes, magclient is magnumclient, so as a workaround I've created the following link:
sudo ln -s /usr/lib/python2.7/site-packages/magnumclient /usr/lib/python2.7/site-packages/magclient"
1762316,2018-04-09 12:46:00 UTC,"$ openstack help complete
[...]
This command is provided by the cliff plugin."
1762322,2018-04-09 15:25:31 UTC,"rounded-red.svg is not rendered correctly but processed correctly, so opening and saving as svg works without any problems (saving as png does not work properly)
Tested on Inkscape 0.92.3 (2405546, 2018-03-11) with Windows 10 (Build 16299.334)"
1762322,2019-02-03 08:15:11 UTC,"confirmed on Windows 10, Inkscape 0.92.4 (5da689c313, 2019-01-14)"
1762322,2020-01-09 19:24:42 UTC,"This issue has been reported to https://gitlab.com/inkscape/inkscape/issues/635, so closing this here."
1762345,2018-04-10 01:41:11 UTC,"Hello, it looks like you're trying to install an older version of the snap DNA analysis tool with the snapd package manager. I do not know how you got the older version of the snap tool rather than the new version, 2013-11-29-1ubuntu2.16.04.1, which should make it possible to have both installed at the same time."
1762346,2018-04-09 08:55:42 UTC,"StacktraceTop:
 g_type_check_instance_cast (type_instance=0x6f725074736f5022, iface_type=94808139230528) at ../../../../gobject/gtype.c:4052
 handle_icon_slow_two_click (event=0x7f68241e88e0, icon=0x563a403d6c90, container=0x563a3dbda8a0) at nemo-icon-container.c:4967
 nemo_icon_container_did_not_drag (event=0x7f68241e88e0, container=0x563a3dbda8a0) at nemo-icon-container.c:3141
 button_release_event (widget=0x563a3dbda8a0, event=0x7f68241e88e0) at nemo-icon-container.c:3471
 _gtk_marshal_BOOLEAN__BOXEDv (closure=0x563a3d71c570, return_value=0x7fffaa4bea70, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x563a3d71c5a0) at ../../../../gtk/gtkmarshalers.c:128"
1762347,2019-06-28 13:38:49 UTC,Hi guys!
1762347,2019-06-27 17:12:35 UTC,It's happening the same in Rocky
1762347,2019-01-08 15:25:17 UTC,Im hitting this bug with Queens and Ceph Luminous.
1762347,2018-05-13 19:01:58 UTC,"Crazik, thanks for the bug report. If Swift returns 401 error, it's OK for Horizon to force user re-login"
1762347,2018-05-15 09:08:12 UTC,After migrating to Queens with Ceph Luminous issue is solved.
1762351,2018-04-25 08:55:57 UTC,Bugzilla for the root cause https://bugzilla.redhat.com/show_bug.cgi?id=1565179
1762351,2018-09-10 11:59:29 UTC,Testing if it's still an issue with https://review.openstack.org/601254
1762351,2018-06-14 17:18:04 UTC,No updates on the BZ
1762351,2018-05-07 11:01:50 UTC,"07 May, no updates in BZ"
1762351,2018-04-30 15:24:42 UTC,(triage) holding pattern waiting on BZ
1762351,2018-04-13 21:31:24 UTC,"It’s not invalid, we have a promotion because a workaround https://review.rdoproject.org/r/#/c/13327/"
1762351,2018-04-09 17:51:25 UTC,cpu flags seem to be identical on failing / successful runs... perhaps we could enforce tcg mode until we find the root cause.
1762351,2018-04-13 15:14:00 UTC,triage note: this job has passed for the past 5 runs
1762351,2018-04-09 14:01:02 UTC,So this is not happening always and something is to do with nested virtualization:-
1762351,2018-04-13 15:14:43 UTC,(and we've had a promotion)
1762351,2018-04-10 12:45:23 UTC,tagging tech-debt for RCA
1762351,2018-04-10 07:24:41 UTC,<< cpu flags seem to be identical on failing / successful runs... perhaps we could enforce tcg mode until we find the root cause.
1762357,2020-09-10 13:55:37 UTC,Closing because INVALID: Can't replicate.
1762357,2018-04-09 09:55:06 UTC,C:\\Users\\pvalero\\Desktop\\Logo PR \007 WS_2 Azul+Gris 2017.eps
1762357,2018-04-19 16:51:16 UTC,Could #1728637 be related?
1762357,2018-04-19 22:35:35 UTC,"- does this happen with all .eps files, or just this one?
- could you attach the .eps file that fails?"
1762357,2018-04-20 18:44:40 UTC,"Hi Johannes and Alvin, this happen with all .eps, I can't open any, always it gives error."
1762360,2020-01-14 16:11:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762363,2021-02-11 10:27:13 UTC,"Still the isssue in Bootstrap OPAC, see the attachment"
1762363,2018-12-19 18:17:18 UTC,Catalog search for Les Misérables
1762363,2018-12-19 18:16:44 UTC,Catalog search for exposé
1762363,2018-12-19 18:16:01 UTC,Catalog search for Paul Cézanne
1762363,2018-05-24 14:54:45 UTC,"I have tested this in EG 3.1.1 and in EG master. In both cases the problem still exist.
Words containing non-ASCII characters are not highlighted in search results"
1762363,2018-12-19 18:14:01 UTC,This is a problem for catalogs of all languages. Words and names with diacritics are not uncommon in all catalogs. Here are a few examples of words/names containing diacritics from our English language catalog:
1762363,2018-05-24 15:52:08 UTC,"This is a sided effect of long-standing (and, until highlighting) user-invisible search code.
 Specifically, it's because we force the use of search_normalize() against both indexed and search input terms, which strips diacritics.  This is addressable, but unfortunately fairly non-trivial."
1762363,2018-12-19 18:15:18 UTC,Catalog search for Charlotte Brontë
1762369,2018-06-15 17:43:27 UTC,neutron_tempest_plugin patch: https://review.openstack.org/#/c/575726/
1762369,2018-06-25 22:30:26 UTC,"Reviewed:  https://review.openstack.org/575805
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=74a8a70c6864f8445918eff73587045d9c09f9ce
Submitter: Zuul
Branch:    stable/pike"
1762369,2018-11-06 06:10:39 UTC,This issue was fixed in the openstack/neutron 11.0.6 release.
1762369,2018-06-15 17:42:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/575805"
1762369,2018-06-14 10:49:49 UTC,"It is exactly the same in master branch in neutron_tempest_plugin repo: https://github.com/openstack/neutron-tempest-plugin/blob/7681a5cf5769211dc355e2bf8cd7499795f6de22/neutron_tempest_plugin/api/test_ports.py#L111
and I think that it's not failing only because it's skipped in gate job probably"
1762373,2018-04-10 04:03:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762375,2018-04-09 10:52:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559699"
1762375,2018-09-11 22:19:32 UTC,"Change abandoned by Honza Pokorny (<email address hidden>) on branch: master
Review: https://review.openstack.org/559699
Reason: closing in favor of https://review.openstack.org/#/c/601626/"
1762378,2019-09-17 20:54:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762378,2019-09-17 20:57:11 UTC,"I confirm the issue is still here (Ubuntu Server 18.04.3), as the package has not been updated (6.4.0+dfsg-1)."
1762378,2019-10-02 10:24:53 UTC,I can this issue as well on Ubuntu 18.04.3 LTS.
1762382,2018-04-09 14:57:14 UTC,Could you open an issue upstream against systemd/systemd on github requesting such a change?
1762382,2018-04-09 11:07:33 UTC,"Looks like, this key is supported by systemd, but for another model: https://github.com/systemd/systemd/blob/master/hwdb/60-keyboard.hwdb#L321"
1762382,2018-04-15 08:55:07 UTC,Pull request merged upstream: https://github.com/systemd/systemd/pull/8715
1762382,2018-04-15 08:56:20 UTC,"Until systemd gets updated, following file can be used. Put it to /etc/udev/hwdb.d"
1762382,2018-04-19 05:16:26 UTC,Confirmation by other person https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/comments/8
1762382,2018-04-19 05:44:52 UTC,"Please use this instead once it's get merged:
https://github.com/systemd/systemd/pull/8762"
1762385,2018-10-01 17:15:35 UTC,This bug was fixed in the package linux - 4.15.0-36.39
1762385,2018-08-28 00:32:43 UTC,This bug was fixed in the package systemd - 239-7ubuntu4
1762385,2018-07-03 06:57:46 UTC,"Hello Dmitriy, or anyone else affected,"
1762385,2018-07-19 12:13:45 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.2
1762385,2018-07-18 13:31:07 UTC,"This patch set is still present, and is operating as expected in 237-3ubuntu10.2"
1762385,2018-07-19 12:14:08 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1762385,2018-10-10 15:49:41 UTC,"Hello Dmitriy, or anyone else affected,"
1762385,2018-04-16 07:00:46 UTC,"Ok it actually happens to all Dell machines I tested.
Also I can see your systemd's hwdb commit to fix the issue. I'll update your change to make it apply to all dell machines."
1762385,2018-10-24 16:50:01 UTC,Thank you for checking that this doesn't introduce a regression on unaffected hardware.
1762385,2018-10-24 17:11:46 UTC,"Either this change will make the rfkill button work (good), or not (current behaviour). Given the code paths, validating similar SKUs for non-regression is a good enough confidence level that this change doesn't regress other/unrelated machines. It's a low risk to accept this change as is, because the worst case scenario is a no-change in behaviour. The upside is that it may have fixed rfkill button."
1762385,2018-10-24 17:39:46 UTC,Thanks. I think that's sufficient justification.
1762385,2018-10-24 19:44:13 UTC,This bug was fixed in the package systemd - 229-4ubuntu21.5
1762385,2018-05-25 06:15:43 UTC,I verified the udev -proposed on Dell Inspiron 5767 machine and it works fine. Change tag to verification-done-bionic. Thanks.
1762385,2018-12-18 16:28:55 UTC,I still get this error in Cosmic on a Dell M6500.
1762385,2018-10-23 13:15:36 UTC,Tested xenial live session with stock systemd/udev and upgraded one from proposed. My dell laptop is not affected by this issue. But at least rfkill keys still work for me with both old and new systemd/udevd and there are no error messages in dmesg.
1762385,2018-05-24 10:07:53 UTC,"Hello Dmitriy, or anyone else affected,"
1762385,2018-04-16 06:43:17 UTC,Did you see this after you pressed the wireless hotkey? Or did it just happen out of nowhere?
1762385,2018-04-26 08:20:56 UTC,"The attachment ""This is a patch to dell-wmi.c kernel module adding 2 new key definitions"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1762385,2018-04-09 11:30:06 UTC,This change was made by a bot.
1762385,2018-04-10 16:04:21 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1762385,2018-04-13 05:58:32 UTC,"According to https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-wmi.c this key isn't supported by kernel.
To add support record { KE_IGNORE, 0xe008, { KEY_RFKILL } } must be added to array dell_wmi_keymap_type_0010. Right now it exists only in dell_wmi_keymap_type_0000."
1762385,2018-04-16 07:12:48 UTC,"I found one more missing key definition: FN-Lock key - Lock icon with 'Fn' on it, it toggles Fn row behavior between F1-F12 and media keys. I'm not sure with keycode it should have assigned, so I set it to IGNORE in patch."
1762385,2018-04-17 08:38:08 UTC,I can observe the same issue on several Dell systems with Linux kernel v4.4. I didn't test older kernel though.
1762385,2018-05-14 09:26:27 UTC,Attached deb patch for bionic
1762385,2018-04-18 06:40:33 UTC,There are actually two different bugs:
1762385,2018-04-18 07:35:03 UTC,"It should be this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=788683"
1762385,2018-04-19 04:59:39 UTC,"I can confirm the ""!"" release is required."
1762385,2018-04-19 05:15:22 UTC,Enough guessing. Gnome bug is a different one. And it has no connection to this bug.
1762385,2018-04-19 05:43:20 UTC,This is the same one as the Gnome bug.
1762385,2018-04-17 08:57:13 UTC,"Rfkill key produces 2 events: keyboard and one, that should be handled by dell-wmi."
1762391,2020-02-04 05:31:58 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.34) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1762391,2020-02-04 05:48:10 UTC,"All autopkgtests for the newly accepted systemd (242-7ubuntu3.3) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1762391,2020-02-05 15:39:09 UTC,"I have just verified bionic. With version 237-3ubuntu10.34 after replaying test case from the description I see the groups from /etc/security/group.conf (dialout, users) added:"
1762391,2020-02-05 15:46:59 UTC,With identical setup and testcase for eoan I have managed to successfully verify the patch with version 242-7ubuntu3.3:
1762391,2020-02-06 15:20:46 UTC,"This SRU needs to be reuploaded, due to security update that trumped this in progress SRU."
1762391,2020-02-06 21:42:31 UTC,"Hello mtemp, or anyone else affected,"
1762391,2020-02-06 21:46:34 UTC,"Hello mtemp, or anyone else affected,"
1762391,2020-02-10 10:19:53 UTC,I have repeated verification for eoan (242-7ubuntu3.7) with identical results.
1762391,2020-02-07 07:06:28 UTC,"All autopkgtests for the newly accepted systemd (242-7ubuntu3.7) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1762391,2020-02-10 10:21:15 UTC,Similarly for bionic using version 237-3ubuntu10.39 verification was also successsful:
1762391,2020-02-17 09:25:35 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1762391,2020-02-03 21:53:11 UTC,"Hello mtemp, or anyone else affected,"
1762391,2020-02-17 10:07:54 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.39
1762391,2020-02-18 15:14:03 UTC,"upstream systemd issue is https://github.com/systemd/systemd/issues/11198
As launchpad was failing to sync the status of the upstream issue, I just marked it manually as fix released."
1762391,2020-02-07 04:59:41 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.39) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1762391,2020-02-03 21:41:14 UTC,"Hello mtemp, or anyone else affected,"
1762391,2020-02-17 09:35:40 UTC,This bug was fixed in the package systemd - 242-7ubuntu3.7
1762391,2020-01-23 16:26:02 UTC,This bug was fixed in the package systemd - 244.1-0ubuntu2
1762391,2020-01-28 15:07:17 UTC,systemd in Xenial differs to much to cleanly apply the upstream fix. It would require reimplementing it and may be more risky than useful.
1762391,2018-08-09 16:01:20 UTC,"I am also using this feature and all previous versions of Ubuntu worked fine with this configuration. However with Bionic the GDM logins no longer add these local groups. Only no graphical logins like su, sudo, ssh, etc... add the appropriate local groups as per the /etc/security/group.conf."
1762391,2018-08-20 12:54:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762391,2018-12-18 08:36:56 UTC,According to my tests GDM works as expected - checking groups the user belongs to on different terminal emulators (e.g. xterm) proves that the /etc/security/group.conf groups are correctly applied.
1762391,2019-02-11 18:08:07 UTC,"pam_group is a historical curiosity. While we should continue to ship it in pam for compatibility with existing configurations, there is no good reason to use it in a new deployment, and we should not consider incompatibility with pam_group to itself be a reason to change the behavior of a pam application."
1762391,2020-01-14 08:10:19 UTC,"This issue has been fixed upstream, I believe it makes sense to also have it in Ubuntu."
1762391,2018-08-09 16:58:37 UTC,There is also a Gnome bug for this at https://gitlab.gnome.org/GNOME/gdm/issues/393#
1762391,2020-01-14 11:55:45 UTC,Please hold on with uploading until https://github.com/systemd/systemd/issues/14567 is resolved.
1762391,2020-01-16 09:54:53 UTC,SRU proposal for focal.
1762391,2020-01-17 14:36:46 UTC,SRU proposal for bionic.
1762391,2020-01-17 14:37:11 UTC,SRU proposal for eoan.
1762391,2020-01-14 09:32:18 UTC,SRU proposal for Focal (upstream backport).
1762391,2020-01-20 14:58:56 UTC,SRU proposal for eoan (patches split)
1762391,2020-01-20 15:44:19 UTC,SRU proposal for bionic (patches split)
1762392,2018-05-08 13:05:47 UTC,"I think a better solution would be to use monotonic timer.
python3 has this, but python2 it is not built-in, so we'd still need to have the current path available."
1762393,2018-04-13 12:03:35 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1762393,2020-08-10 02:06:54 UTC,python-volatility 2.5-1-trusty1
1762393,2020-08-10 02:08:04 UTC,"Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!"
1762397,2018-04-09 12:12:13 UTC,"StacktraceTop:
 gtk_container_real_check_resize (container=0x564575170df0) at ../../../../gtk/gtkcontainer.c:2182
 _g_closure_invoke_va (closure=0x564574c501f0, return_value=0x0, instance=0x564575170df0, args=0x7ffc1a53c260, n_params=0, param_types=0x0) at ../../../../gobject/gclosure.c:867
 g_signal_emit_valist (instance=0x564575170df0, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc1a53c260) at ../../../../gobject/gsignal.c:3300
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../../../../gobject/gsignal.c:3447
 g_closure_invoke (closure=0x5645751b9ee0, return_value=0x0, n_param_values=2, param_values=0x7ffc1a53c500, invocation_hint=0x7ffc1a53c480) at ../../../../gobject/gclosure.c:804"
1762397,2020-11-16 08:40:47 UTC,I can't find any other crashes that look like this. Is it still happening?
1762397,2021-01-16 04:17:20 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1762408,2019-12-27 02:51:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762409,2018-04-09 12:53:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762410,2018-04-10 08:58:35 UTC,This bug was fixed in the package myspell-hr - 20060617-2.4ubuntu1
1762410,2018-04-10 12:58:04 UTC,"Nothing particularly new, the relevant Debian bugs are several years old..."
1762410,2018-04-10 18:55:25 UTC,This bug was fixed in the package openoffice.org-hyphenation-pl - 1:3.0a-4ubuntu1
1762410,2018-04-10 18:06:52 UTC,"Thanks for sponsoring, Mattia!"
1762410,2018-04-10 13:02:03 UTC,"And I just sponsored openoffice.org-hyphenation-pl_3.0a-4ubuntu1_source.changes for Gunnar, so unsubscribing ~ubuntu-sponsors."
1762410,2018-04-10 08:58:34 UTC,This bug was fixed in the package hyphen-ru - 20030310-1ubuntu3
1762410,2018-04-09 22:04:29 UTC,"Gunnar, for Ubuntu's main flavor, I fixed this issue earlier today. I did not look at any of the other Ubuntu flavors though."
1762410,2018-04-09 21:56:41 UTC,"Well, I just uploaded hyphen-ru, which is not synced currently, to the queue."
1762410,2018-04-09 20:50:29 UTC,These packages are synced from Debian. It would be great if someone affected by this bug would report this issue to Debian.
1762410,2018-04-09 12:53:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762410,2018-04-09 22:12:42 UTC,"Ah, apparently I didn't know that. Hopefully we help some flavors by fixing this bug then."
1762411,2018-04-10 02:32:19 UTC,"--all-projects allows you to see the stacks of all projects as an admin user. However, that would not allow you do update/delete of those stacks."
1762413,2018-04-09 13:00:07 UTC,This change was made by a bot.
1762413,2018-04-10 16:03:41 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1762413,2018-04-19 12:53:35 UTC,"Tested the 4.16.3 vanilla kernel, with quite the same errors"
1762413,2018-05-03 11:45:34 UTC,"I have the same problem when trying to use the ubuntu-18.04-server (not live) image using the installer on VMware ESXi 6.5 - using BIOS or EFI, different vga= commandline settings don't make a difference.
after around 1 minute of uptime i get a kernel dump with check_for_bios_corruption ...
is this the same problem on a completely different platform?"
1762413,2018-05-03 12:01:50 UTC,"using the following settings on the kernel commandline makes the debian installer appear: ""vga=normal fb=false"""
1762418,2018-04-13 19:20:42 UTC,Another bug found in tiff2pdf: http://bugzilla.maptools.org/show_bug.cgi?id=2785
1762418,2018-04-13 19:19:13 UTC,Another bug found in tiff2pdf: http://bugzilla.maptools.org/post_bug.cgi
1762418,2018-04-13 18:41:52 UTC,Reported: http://bugzilla.maptools.org/show_bug.cgi?id=2784
1762418,2018-04-13 12:03:08 UTC,Thanks for taking the time to report this bug and helping to make Ubuntu better.
1762423,2018-04-10 02:09:29 UTC,"INFO nova.compute.manager [None req-0516127d-e96f-4a85-a050-70c058f77a44 service nova] [instance: 2ebb3db1-e99f-4b5c-85f4-ae3c9f93ca79] Successfully reverted task state from resize_finish on failure for instance.
ERROR oslo_messaging.rpc.server [None req-0516127d-e96f-4a85-a050-70c058f77a44 service nova] Exception during message handling: libvirtError: Cannot access storage file '/opt/stack/data/nova/instances/2ebb3db1-e99f-4b5c-85f4-ae3c9f93ca79/disk.swap' (as uid:64055, gid:124): No such file or directory
ERROR oslo_messaging.rpc.server Traceback (most recent call last):
ERROR oslo_messaging.rpc.server   File ""/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py"", line 163, in _process_incoming
ERROR oslo_messaging.rpc.server     res = self.dispatcher.dispatch(message)
ERROR oslo_messaging.rpc.server   File ""/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py"", line 220, in dispatch
ERROR oslo_messaging.rpc.server     return self._do_dispatch(endpoint, method, ctxt, args)
ERROR oslo_messaging.rpc.server   File ""/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py"", line 190, in _do_dispatch
ERROR oslo_messaging.rpc.server     result = func(ctxt, **new_args)
ERROR oslo_messaging.rpc.server   File ""/opt/stack/nova/nova/exception_wrapper.py"", line 76, in wrapped
ERROR oslo_messaging.rpc.server     function_name, call_dict, binary)
ERROR oslo_messaging.rpc.server   File ""/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py"", line 220, in __exit__
ERROR oslo_messaging.rpc.server     self.force_reraise()
ERROR oslo_messaging.rpc.server   File ""/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py"", line 196, in force_reraise
ERROR oslo_messaging.rpc.server     six.reraise(self.type_, self.value, self.tb)
ERROR oslo_messaging.rpc.server   File ""/opt/stack/nova/nova/exception_wrapper.py"", line 67, in wrapped
ERROR oslo_messaging.rpc.server     return f(self, context, *args, **kw)
ERROR oslo_messaging.rpc.server   File ""/opt/stack/nova/nova/compute/manager.py"", line 186, in decorated_function
ERROR oslo_messaging.rpc.server     ""Error: %s"", e, instance=instance)
ERROR oslo_messaging.rpc.server   File ""/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py"", line 220, in __exit__
ERROR oslo_messaging.rpc.server     self.force_reraise()
ERROR oslo_messaging.rpc.server   File ""/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py"", line 196, in force_reraise
ERROR oslo_messaging.rpc.server     six.reraise(self.type_, self.value, self.tb)
ERROR oslo_messaging.rpc.server   File ""/opt/stack/nova/nova/compute/manager.py"", line 156, in decorated_function
ERROR oslo_messaging.rpc.server     return function(self, context, *args, **kwargs)
ERROR oslo_messaging.rpc.server   File ""/opt/stack/nova/nova/compute/utils.py"", line 976, in decorated_function
ERROR oslo_messaging.rpc.server     return function(self, context, *args, **kwargs)
ERROR oslo_messaging.rpc.server   File ""/opt/stack/nova/nova/compute/manager.py"", line 214, in decorated_function
ERROR oslo_messaging.rpc.server     kwargs['instance'], e, sys.exc_info())
ERROR oslo_messaging.rpc.server   File ""/usr/local/lib/pyth..."
1762423,2018-04-11 08:58:25 UTC,"some debug shows even swap disk is 0, we will still create guest configuration which leads to problem ......"
1762423,2018-04-13 04:51:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561122"
1762423,2019-04-08 17:53:56 UTC,"Load: 20190404T013000Z
Node Config: 2+3
Failing resize - original flavor has swap. Instance Power Status Running but Status changes to ERROR"
1762423,2019-06-25 19:13:35 UTC,"Behaviour in Load: 20190622T013000Z
 Lab: WP_3_7"
1762423,2019-07-25 13:52:01 UTC,"Change abandoned by Eric Fried (<email address hidden>) on branch: master
Review: https://review.opendev.org/561122
Reason: This has had no activity for >1y. Please reopen if still needed."
1762425,2020-07-01 20:58:43 UTC,"Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1762425,2020-07-01 20:59:04 UTC,the bug was reported agains the pdf viewer evince but it doesn't seem a problem with this software?
1762425,2020-08-31 04:17:24 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1762436,2018-09-23 23:15:33 UTC,Switch user is the only work around on a device without a keyboard (tablet).
1762440,2018-04-10 02:22:58 UTC,This should also be an option for keepouts
1762445,2018-12-31 14:29:42 UTC,"Hello Ari,"
1762445,2018-12-27 18:46:12 UTC,"Thanks a lot for the update, Adam. I've just now had the time to give this another go. Unfortunately it seems like compilation is getting stuck at a different point now. Not sure if this is on my end or related to this bug, but if you have the time I'd really appreciate it if you could take a look:"
1762445,2019-01-16 17:02:24 UTC,"Thanks once again for the quick response, Adam. That definitely seems to be the cause. I'll try to look into building libmupdf with the right flags soon."
1762445,2018-04-10 19:42:10 UTC,"Hello Ari,"
1762445,2018-04-12 23:05:38 UTC,"Hey Adam,"
1762446,2018-04-09 15:35:09 UTC,"This matches my use case as well.
But it need to be more I telligent, since the cue can be to easily moved, but the first beat is a track value.
There are also other uscase possible like Denon mode where this assumption is not true."
1762449,2019-06-05 07:39:21 UTC,"That was still an issue in 18.10, no report from 19.04 so far"
1762449,2020-07-01 20:57:17 UTC,"Closing, there has been no report after 18.10"
1762451,2018-04-09 21:01:10 UTC,"hmm ... this afternoon, i had 100% reproducibility. i did not restart the pc, there was no automatic update, i had the same document open, and now after 6 hours just being there, it does not occur anymore. restarted inkscape, not there. no idea, what happend. still line-spacing=0%, dropdown still grey. don't understand this."
1762461,2019-01-09 08:48:15 UTC,I'm getting a similar experience on 2.5.0 final here.  3 rack controllers offline and I've been waiting 45 mins to bounce the region service.  This is my second attempt - the first time the box eventually ground to a complete halt.
1762461,2019-01-09 21:18:27 UTC,I will do that next time I'm running a deployment.  FYI I resolved this by:
1762461,2019-01-09 19:00:40 UTC,"Hi Phil,"
1762461,2018-05-06 11:51:02 UTC,I see this:
1762461,2018-05-06 11:50:45 UTC,"Not sure where we are tracking this, but I see it in the GMAAS too. I think I have one sick rack controller. Might it have to do with the IP addresses on which RPC services listen?"
1762461,2018-04-11 23:57:17 UTC,PLease see 1762461 for more details too.
1762461,2018-04-11 23:56:47 UTC,https://bugs.launchpad.net/maas/+bug/1761601 is a duplicate of this.
1762461,2018-04-09 15:40:53 UTC,This seems very similar to:
1762465,2018-04-27 01:41:49 UTC,I also agree that https://imgur.com/qS0ODeq would be best.
1762465,2018-04-26 22:48:07 UTC,"Oh, except for a less dramatic deviation from the current design the sidebar should have orange text and an undivided dark background, I think, rather than an orange line, as in the most recent imgur. Probably the lighter shade of gray should be used."
1762465,2018-04-26 22:44:11 UTC,"I think the latter solution - keep the dark background but remove the line - makes the most sense. Can this be SRU'd to 18.04 when done? I think this is a significant enough design bug that an SRU should be done? Regression potential would be, perhaps, that updates (the change from the buggy UI to the new UI) don't produce the intended result (though updates can easily be tested for)."
1762465,2018-04-26 19:34:51 UTC,Two more solutions:
1762465,2018-04-26 18:33:58 UTC,"That is true, it should be the same color for icon and label as they are one item."
1762465,2018-04-24 01:31:43 UTC,"I think that would be OK as a solution, but not ideal."
1762465,2018-04-23 15:39:33 UTC,"I think that's a too big change, and Ambiance-RW that was ack'ed by design had this two color situation."
1762465,2018-04-23 15:59:11 UTC,"Something like this, to be more clear: https://usercontent.irccloud-cdn.com/file/DwPJt7na/image.png"
1762465,2018-04-23 01:41:09 UTC,I think there are just too many columns. The icons and labels should have the same background colour. So one column instead of two.
1762465,2018-04-21 01:30:42 UTC,Not sure how this can be solved... Something like https://i.imgur.com/RA9esFK.png would be better?
1762465,2018-04-21 01:27:58 UTC,Not sure how this can be solved... Something like https://i.imgur.com/ZVXQ1ku.png ?
1762465,2018-04-16 08:51:53 UTC,"As far as I can tell, you need to look for ""placessidebar"" in:
/usr/share/themes/Ambiance/gtk-3.20/gtk-widgets.css"
1762465,2018-04-13 12:23:25 UTC,"I agree to this bug. I think the sidebar should have the same background, labels and icons."
1762465,2018-04-10 01:34:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762465,2018-04-23 03:10:45 UTC,Same as the design of the side bar in http://news.google.com - one background for icons and labels.
1762468,2018-04-11 21:51:48 UTC,"The first kernel on that list that exhibits the bug is the first one:
4.14 Final.  Recall: the bug results in a full up hang.  The disk stops
swapping (it's audible).   I can reboot with sysctl SUB however."
1762468,2018-05-02 15:46:54 UTC,-update-
1762468,2018-05-02 15:46:21 UTC,"At the risk of saying something completely unrelated; any change this is a regression of #1310058 where the UUID got overwritten? It came back a few times around 2015, leading me to believe that the devs don't actually use this method, and might not test for this scenario, making a regression possible."
1762468,2018-04-12 17:17:24 UTC,"Thanks for finding the mainline 4.10 does not have the bug and 4.11 final does.  Can you also test v4.11-rc1, so we can find which release candidate introduced the bug?"
1762468,2018-04-12 13:01:39 UTC,"In response to #7, I don't think this is the same issue.  The cryptswap initiates with no difficulties, timeouts, etc. on boot.  When I first installed Bionic, ubiquity did not correctly install the swap, and I filed #1759253 on that issue."
1762468,2018-04-11 22:03:27 UTC,"BTW, I _do_ realize that you want a starting point for bisection; I'm
sorry this is turning out so messy."
1762468,2018-04-11 15:18:37 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
1762468,2018-04-12 20:41:36 UTC,"Some good and bad news: I have been testing this in a running Gnome 3 environment.  I decided to start testing on console.  On console, all kernels seem to fail using crypt swap.  This suggests to me that failure must depend on current memory usage, dirty ratio, or some such runtime condition."
1762468,2018-04-10 18:01:32 UTC,"Yes, the problem does occur in mainline 4.16 and I have added the requested tag."
1762468,2018-04-09 16:10:51 UTC,"The code that I used to force failure, memtest.c, is attached to the bug report."
1762468,2018-04-09 16:30:08 UTC,This change was made by a bot.
1762468,2018-04-10 20:07:57 UTC,Looks like the same issue as reported on lp:#1736072
1762468,2018-04-10 16:01:26 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1762468,2018-04-09 23:18:22 UTC,"It seems that cryptswap is working correctly on 17.10 with the kernel 4.13.0-36-generic on a different machine using the same test as described above.  I tried the same kernel (4.13.0-36) on 18.04 (machine used in original post) and it still fails.  Of course, I checked that the swap appears in /proc/meminfo.  Hope this provides a clue."
1762469,2020-01-05 16:54:04 UTC,"This problem was fixed as part of commit 5ab8b4daac1f2d314ada0fde29959264bccdeeeb on 2018-05-08. I am closing this bug, accordingly."
1762478,2018-04-09 16:38:58 UTC,For now I cowboyed a change to blacklist squid3. It should fail with an informative message for the SRU team.
1762483,2018-04-09 17:31:42 UTC,Workaround:
1762483,2018-04-10 16:12:14 UTC,Please see our bug triage conversation to know how to fix this. The workaround is essentially correct in the meantime.
1762483,2018-04-11 12:11:55 UTC,Disregard comment #3. I commented on a wrong bug. Sorry.
1762483,2018-11-11 12:54:13 UTC,The playbooks directory contains the setup-infrastructure.yml playbook. The run-upgrade.sh script calls the setup-insfrastructure.yml playbook with specific arguments to upgrade RabbitMQ.
1762492,2019-05-31 11:13:51 UTC,This also does apply only to Xenial an Bionic as Cosmic and later series have versions where upstream fixed this.
1762492,2018-04-09 17:39:57 UTC,This does not apply to Trusty as stats directory for postgres is not configured there.
1762492,2019-06-03 09:01:09 UTC,Setting dev version to fix released per last comment.
1762493,2018-04-09 18:21:30 UTC,Fix proposed: https://review.openstack.org/#/c/559803/
1762501,2020-09-11 04:10:41 UTC,Closing because INVALID: incomprehensible.
1762511,2018-12-10 08:23:08 UTC,"Reviewed:  https://review.openstack.org/620442
Committed: https://git.openstack.org/cgit/openstack/python-zunclient/commit/?id=617f1126ac21119708050a64a18b7fba339a82f4
Submitter: Zuul
Branch:    stable/rocky"
1762511,2018-12-05 01:34:29 UTC,"Reviewed:  https://review.openstack.org/620637
Committed: https://git.openstack.org/cgit/openstack/python-zunclient/commit/?id=5a0a13283020d59005a8fcd43f84c1a02fd48abd
Submitter: Zuul
Branch:    stable/queens"
1762511,2018-12-03 08:26:38 UTC,"Reviewed:  https://review.openstack.org/620622
Committed: https://git.openstack.org/cgit/openstack/python-zunclient/commit/?id=216ba98b4e285c3d23ab68a876afb38b3cc2482e
Submitter: Zuul
Branch:    stable/queens"
1762511,2018-11-29 07:27:07 UTC,"Reviewed:  https://review.openstack.org/620441
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=e5c588acfd7070b309b5285ac55dd3f0f6bfbfbe
Submitter: Zuul
Branch:    stable/rocky"
1762511,2018-11-29 03:46:52 UTC,"Reviewed:  https://review.openstack.org/620620
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=b8d8595fa376d56c87600510b8aba8fdcc013390
Submitter: Zuul
Branch:    stable/queens"
1762511,2018-11-29 03:02:21 UTC,"Reviewed:  https://review.openstack.org/620443
Committed: https://git.openstack.org/cgit/openstack/python-zunclient/commit/?id=3adcd73ac7024ae084532d0d8fb264dad245b694
Submitter: Zuul
Branch:    stable/rocky"
1762511,2018-11-28 15:46:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/620637"
1762511,2018-11-28 15:15:31 UTC,"No problem, Glad I could help"
1762511,2018-11-28 15:03:15 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/620622"
1762511,2018-11-28 15:01:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/620620"
1762511,2018-11-28 14:57:33 UTC,"Got it. Thanks for the information, David."
1762511,2018-11-28 14:13:24 UTC,"I really just used your patch, but queens did not have the conditional statement in the function do_exec(387) like master so I added it, but left the variables from queens in zunclient/common/websocketclient/websocketclient.py."
1762511,2019-03-20 04:51:49 UTC,This issue was fixed in the openstack/zun 3.0.0.0rc1 release candidate.
1762511,2018-11-28 03:06:21 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620443"
1762511,2018-11-28 03:05:05 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620441"
1762511,2018-11-28 03:03:07 UTC,"@David,"
1762511,2018-11-27 19:38:52 UTC,"That was my fault, I made a mistake. I have wss working throughout my environment now. Thanks for the patch. I had to modify it slightly to work in queens specifically in the websocketclient.py for the do_exec function."
1762511,2018-11-27 15:33:22 UTC,"@hongbin I patched my deployment with your fix and I can now use wss with openstack cli via ""openstack appcontainer exec --interactive mycontainer --net network=netuuid cirros /bin/sh"". I am still having issues with zun-ui console connections. zun-ui for me sits on a separate node than my controller and compute. So I am wondering if I might have missed something there. I patched websocketclient.py with the two patches you have for zunclient on the nodes with zun-ui, but I still can not get a connection. Does zun-ui request the websocket console connections in the same way as openstack cli? Or does it have another dependency I might have missed."
1762511,2018-11-27 06:16:23 UTC,"Reviewed:  https://review.openstack.org/619942
Committed: https://git.openstack.org/cgit/openstack/python-zunclient/commit/?id=67660449617b2a884735f000f922faafe69659b0
Submitter: Zuul
Branch:    master"
1762511,2018-11-27 06:16:16 UTC,"Reviewed:  https://review.openstack.org/619907
Committed: https://git.openstack.org/cgit/openstack/python-zunclient/commit/?id=ff3b380680c109d0819c19b5530b483082c6935b
Submitter: Zuul
Branch:    master"
1762511,2018-11-27 04:22:11 UTC,"Reviewed:  https://review.openstack.org/619934
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=1bb994962be5822fdf992adf2ead07a72f6064f4
Submitter: Zuul
Branch:    master"
1762511,2018-11-25 22:33:02 UTC,"After a couple of fixes [1][2][3], I managed to get the ""wss"" connection work in master branch. I will backport the fixes to stable branches after they are merged in master."
1762511,2018-11-25 21:52:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619942"
1762511,2018-11-25 16:26:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619934"
1762511,2018-11-20 19:54:30 UTC,"@hongbin, I was getting ready to open another bug for wss based on our discussion last week, but it looks like this is the same issue."
1762511,2018-11-28 03:05:53 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620442"
1762542,2018-04-10 01:36:33 UTC,"It appears gnome-weather is using custom rendering, not the theme."
1762542,2018-04-10 08:22:07 UTC,"gnome-weather has always looked broken in Ambiance. In Adwaita and third party themes, it looks normal."
1762542,2018-04-13 12:03:28 UTC,"Even if it uses custom rendering, I wish Ambiance could support that since gnome-weather looks very good by default in Adwaita and Materia themes."
1762545,2018-04-10 01:23:55 UTC,Please explain in more detail what the problem is and where you are seeing it.
1762545,2018-04-13 12:12:07 UTC,Steps:
1762545,2018-04-16 11:43:53 UTC,You could maybe add a screenshot to the bug showing the feature you request?
1762545,2018-04-16 12:43:48 UTC,"In this screecast Nautilus using Adwaita, notice the dashed lines at the top and bottom. They appear when there is more content to scroll to, and disappear when there isn't."
1762552,2018-12-19 21:22:18 UTC,Currently the 401 from the store looks like this (no nice error payload):
1762558,2018-04-11 10:46:21 UTC,"IMHO it's best to keep this open until we find out what's going on;  it's not impossible it's something that's changed in qemu, and even if it isn't qemu's fault then you won't be the only person who ends up reporting it here, so it'll be good to get the answer."
1762558,2018-04-10 17:43:06 UTC,"...on the other hand, I was clearly not thinking straight in associating this with the qemu version bump in Rawhide, because we don't *run* that qemu. We use the qemu from the worker host, not from the image under test, and the worker hosts are not running Rawhide, and their qemu hasn't changed during the time this problem appeared."
1762558,2018-04-11 15:30:59 UTC,"Up to you, of course. Just realized I didn't mention here that I also reported this downstream, and since it turns out to be not triggered by a qemu change I've been doing most of the investigation there:"
1762558,2018-04-10 05:55:08 UTC,"These error messages (""memslot_get_virt"") do not come from QEMU, but from spice, so please report this problem to the Spice project first (see https://www.spice-space.org/support.html for how to file a bug there)."
1762558,2018-04-10 16:05:55 UTC,"Nothing about SPICE changed in the affected time frame. This started happening between 2018-04-02 and 2018-04-07. The last time SPICE was changed in Rawhide was on 2018-02-09. However, qemu was bumped from rc1 to rc2 on 2018-04-05."
1762563,2018-04-10 00:23:03 UTC,"The attachment ""01_fix-d-module-versions-crash.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1762563,2018-04-10 17:29:22 UTC,Relevant upstream bug reports: https://github.com/mesonbuild/meson/pull/3336 (crash) and https://github.com/mesonbuild/meson/issues/3337 (flags not applied).
1762567,2018-08-01 03:14:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762570,2018-04-18 03:46:11 UTC,It seems the simplest thing here is to extend the Machine doc used to add two fields.
1762570,2018-04-18 03:47:03 UTC,We could prod cloudbase to see if they could also find ways to get the information for the windows agents.
1762582,2018-04-10 01:49:06 UTC,Reported upstream: https://github.com/mate-desktop/mate-panel/issues/763
1762582,2019-07-22 15:01:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762587,2018-04-10 13:04:29 UTC,The current version of keystone that I have installed is: 13.0.0 Queens and the keystone-ldap charm version is # 8  I have successfully listed my user id from my corporate directory without the ldap-user and ldap-password setting in my /etc/keystone/keystone.domain_ldap.conf file so I am confident that the current version of keystone does support this function.
1762587,2018-04-10 07:03:39 UTC,"Anonymous bind is indeed a common pattern in LDAP architectures and it allows for increased security by not storing any credentials on the server, utilizing end user provided credentials for all operations."
1762587,2018-04-10 01:35:03 UTC,Just an update.  If I remove the values ldap-user/ldap-password from /etc/keystone/domains/keystone.domain.conf and restart the keystone service I am able to authenticate against the directory.
1762588,2019-12-24 16:55:44 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1762588,2018-10-20 19:15:16 UTC,"Hi Nataraj,
For the ease of the programmers, I will add a summery here to complete the bug report. Please feel free to add any corrections.
Also, do you mind if I update the title of the bug report to:
“thunderbird 52.9.1/18.04 compact folder broken for IMAP Dovecot”
Thanks
G
-----------------------"
1762588,2018-10-20 18:29:24 UTC,"My apologies, Nataraj. That was my mistake, leaving it at incomplete status when you had replied.
Thanks, Paul, for changing the status back to new.
G"
1762588,2018-10-19 21:57:47 UTC,Bug re-opened.
1762588,2018-10-19 21:47:02 UTC,"I was sent a message asking if this bug still existed.  I responded that it did, yet the bug report was changed to expired.  How can this bug be reopened?  Why was it previously in an incomplete state.  I believe that I provided all of the requested information..  Am I suppose to change the status to something else?"
1762588,2018-08-20 00:13:05 UTC,"Hi Nataraj.
Sorry for the delay in my reply."
1762588,2018-07-15 20:06:18 UTC,"Yes, this is still a problem for me and I can confirm that the same version under ubuntu 14.04 works correctly, so this is likely related to the build options used under 18.04, unless there is a library issue."
1762588,2018-07-15 19:46:31 UTC,apport information
1762588,2018-07-15 19:46:30 UTC,apport information
1762588,2018-07-15 19:46:28 UTC,apport information
1762588,2018-10-19 04:18:17 UTC,[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.]
1762588,2018-07-15 19:46:26 UTC,apport information
1762588,2018-07-15 19:46:24 UTC,apport information
1762588,2018-07-15 19:46:23 UTC,apport information
1762588,2018-07-15 19:46:21 UTC,apport information
1762588,2018-07-15 19:46:27 UTC,apport information
1762588,2018-07-15 19:46:20 UTC,apport information
1762588,2018-07-15 19:46:19 UTC,apport information
1762588,2018-07-15 19:00:22 UTC,"Hello Nataraj,
Thank you for submitting this bug and reporting a problem with compacting folders in Thunderbird.  You made this bug report some time ago and Ubuntu and Thunderbird have been updated since then."
1762588,2018-04-25 18:07:03 UTC,"I noticed that Thunderbird was upgraded to 52.7 in the 18.04 release, but for some reason the problem still exists (compact folder missing from the folder menu) and still works consistantly for me under Ubuntu 14.04.  I'm not sure why.  I'm planning to upgrade my IMAP server and hoping that will resolve the issue."
1762592,2018-04-10 02:09:36 UTC,And here is a snapshot of what happens in the shell...
1762592,2018-04-11 14:56:34 UTC,"Hi,"
1762592,2018-04-11 19:32:08 UTC,Thanks a lot for your answer!
1762593,2018-11-01 08:58:35 UTC,"yes, this should be replaced by shutil.which"
1762593,2018-11-01 10:29:41 UTC,"An upload of anki to bionic-proposed has been rejected from the upload queue for the following reason: ""Please use different fix as discussed.""."
1762593,2018-11-01 22:25:09 UTC,"Matthias, could you or someone report your suggested fix to Debian since Ubuntu's anki is in sync with Debian?"
1762593,2018-10-18 21:26:08 UTC,"Based on my recollection at the time python3-distutils was split out, I understood that packages were generally expected to not use python3-distutils at runtime.  Matthias, can you review this and comment on whether this is sensible (as a solution to this problem in Debian unstable and in cosmic) before we accept this SRU?"
1762593,2019-03-30 20:22:27 UTC,The error persists in Linux Mint 19.1. I solved it installing python3-disutils.
1762593,2018-11-01 20:51:53 UTC,"In the meantime I installed Ubuntu 18.04 on another PC (lenovo Thinkpad i5 64bit)
and thereafter Anki in Version 2.1.0beta36 from
the link given by the ""https://wiki.ubuntuusers.de/Anki/"" website"
1762593,2018-10-06 13:31:55 UTC,"Rolf, I uploaded your fix to the bionic queue. It will need to be manually approved by a member of the Ubuntu Stable Release team before it will be available there for testing."
1762593,2018-05-22 09:44:48 UTC,I did install the package mentioned above and now I get the following error when I start anki from the Terminal and doing 2 (Chinese)-Flashcards:
1762593,2018-08-17 18:00:09 UTC,"@pcb, please file a separate bug for that issue."
1762593,2018-07-28 09:13:40 UTC,"Thanks, Fiona. Installing the python3-distutils package worked for me as well on Linux Mint 19. I was able to open Anki normally."
1762593,2018-05-01 06:19:51 UTC,"I have the same problem on fresh install Xubuntu 18.04 LTS, on Virtualbox. Screen shot in attachment."
1762593,2018-04-28 08:01:46 UTC,I solved the problem by installing the python3-distutils package. Please update the dependencies accordingly.
1762593,2018-04-27 13:54:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762593,2018-08-17 18:05:49 UTC,This has been fixed in the latest Debian upload which has been sync'd to Ubuntu+1
1762607,2018-08-29 01:55:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762630,2018-04-10 13:49:11 UTC,"in the past days i've seen a few packages been rebuild with dh-python. I suppose the job is not yet complete, as your request. So the report makes sense."
1762630,2018-04-10 08:41:00 UTC,Here is the complete output while trying to install python3 in a bionic environment (debootstrap).
1762630,2018-04-10 09:02:34 UTC,"You might use the genuine sources.
Here are mine; what are yours ?"
1762630,2018-04-10 12:04:06 UTC,I'm sorry the environment I'm using does not have all the base packages. But I'm still curious why the dh-python dependency was removed from the python3 package.
1762652,2018-04-10 15:56:06 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1762652,2018-04-10 12:25:57 UTC,"apport-collect crashes here, sorry. I'm using a German locale and KDE. Error:"
1762652,2018-04-10 17:59:33 UTC,"Well this is more about the user space tool perf, not really the kernel itself. And I can't really imagine why DWARF unwinding would have anything to do with the kernel used. I'm on stock ubuntu 4.13.0-38-generic btw."
1762652,2018-04-10 08:21:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1762652,2018-04-10 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1762665,2018-04-20 09:35:34 UTC,"Hi George,"
1762667,2018-04-10 08:37:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/559956"
1762667,2018-04-13 03:57:15 UTC,"Change abandoned by zhongshengping (chdzsp@163.com) on branch: master
Review: https://review.openstack.org/559956"
1762667,2018-04-13 15:56:20 UTC,"Reviewed:  https://review.openstack.org/559929
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=dd7fd5586c41a8a873ba18426e277b7f36551e9b
Submitter: Zuul
Branch:    master"
1762667,2018-04-19 21:03:27 UTC,This issue was fixed in the openstack/puppet-neutron 13.0.0 release.
1762667,2018-05-23 07:11:59 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/570128"
1762667,2018-05-23 07:12:13 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/570129"
1762667,2018-05-24 06:38:49 UTC,"Reviewed:  https://review.openstack.org/570129
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=73635f17cde44bc488aa65efe88a15614065904b
Submitter: Zuul
Branch:    stable/pike"
1762667,2018-05-28 06:05:53 UTC,"Reviewed:  https://review.openstack.org/570128
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=b06ce52f57648bda7cbc01c77bedba31e6948ece
Submitter: Zuul
Branch:    stable/queens"
1762667,2019-02-15 14:29:33 UTC,This issue was fixed in the openstack/puppet-neutron 12.4.1 release.
1762667,2019-05-16 23:06:07 UTC,This issue was fixed in the openstack/puppet-neutron 11.6.0 release.
1762673,2019-09-23 09:01:44 UTC,One can use iptables to block access to port 8080 on the host running the proxy to prevent access
1762673,2018-09-03 05:58:22 UTC,"We at least want disk usage control over the squid proxy, and thought we could disable the service and delete all of the cache files. I don't mind if the service is running (see what happens with your investigation into the run/stop inconsistency you mentioned), but can I get some clarity on controlling that?"
1762673,2019-09-11 17:44:27 UTC,"The same behaviour persists on 2.6, proxy is not shutting down completely, and it's still working as a proxy even when disabled explicitly in the settings:"
1762673,2018-04-10 13:32:53 UTC,"Hi Jason,"
1762673,2018-04-10 13:46:29 UTC,"Actually, it seems there's some inconsistency on when the proxy gets stopped."
1762676,2019-03-22 08:04:56 UTC,Same problem here. For instance:
1762682,2018-04-10 09:17:32 UTC,I linked a upstream bug - it looks like the same problem.
1762682,2018-10-09 20:16:59 UTC,"The activity in the upstream bug seems to have stalled. Last report seems to indicate that http://bugs.squid-cache.org/attachment.cgi?id=3549 ""works around the problem"", but it's not clear what the consequences are of the workaround versus a proper committed fix."
1762688,2018-09-24 14:47:32 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1762688,2018-07-30 16:07:51 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1762688,2018-07-02 09:33:00 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/579503"
1762688,2018-07-04 14:01:37 UTC,"Reviewed:  https://review.openstack.org/579503
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3163c9391ec2569f77e583bccf6163c309e45482
Submitter: Zuul
Branch:    stable/queens"
1762688,2018-06-22 13:51:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577424"
1762688,2018-06-29 08:52:08 UTC,"Reviewed:  https://review.openstack.org/577424
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c59397e09de5506bccba513ef31ffb8585fcdc3
Submitter: Zuul
Branch:    master"
1762691,2020-02-18 14:09:03 UTC,This issue was fixed in the openstack/networking-ovn 6.0.1 release.
1762691,2019-11-14 17:13:50 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/694362"
1762691,2020-01-09 13:02:42 UTC,"Reviewed:  https://review.opendev.org/698254
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=70fdad3175b9cde09a9f926a6373fea7df89c8f3
Submitter: Zuul
Branch:    stable/queens"
1762691,2019-12-17 14:49:28 UTC,"Reviewed:  https://review.opendev.org/698252
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=274cde7043fbb92fed7f595e4a6b8a0dc77c5fb3
Submitter: Zuul
Branch:    stable/rocky"
1762691,2019-12-10 14:14:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/698254"
1762691,2020-02-28 15:26:32 UTC,This issue was fixed in the openstack/networking-ovn 5.1.0 release.
1762691,2019-12-10 14:11:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/698252"
1762691,2019-11-18 17:51:17 UTC,"Reviewed:  https://review.opendev.org/694362
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=156d271ae721ef219c0b64c659dd60e19c95858c
Submitter: Zuul
Branch:    stable/stein"
1762691,2019-10-24 14:37:54 UTC,"Reviewed:  https://review.opendev.org/653718
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=2aac5afcf9d850b3a2b40da4b2f0668fd464a2a7
Submitter: Zuul
Branch:    master"
1762691,2019-04-18 11:11:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653718"
1762691,2019-08-13 14:29:09 UTC,"Reviewed:  https://review.opendev.org/591461
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=12070403db4851ef73011c52124cd335b6807521
Submitter: Zuul
Branch:    master"
1762691,2019-05-13 11:25:13 UTC,"Change abandoned by Reedip (<email address hidden>) on branch: master
Review: https://review.opendev.org/657794"
1762691,2019-05-08 13:02:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657794"
1762691,2018-08-10 05:23:35 UTC,"When a new chassis is added, schedule_unhosted_gateways[1] will be called to host unhosted gateways. In this function, we can add this chassis to all gateways which are hosted on less than MAX_GW_CHASSIS[2]."
1762691,2018-07-27 07:52:49 UTC,"Hey Miguel, I handled the scheduling but not the rescheduling.
Anil had something in mind for this. @Anil can you share it here so that someone else can take over?
Thanks!"
1762691,2018-07-27 07:19:39 UTC,"@dalvarez did you already handle this, or was it something else?"
1762691,2019-09-19 10:09:38 UTC,This issue was fixed in the openstack/networking-ovn 7.0.0.0b1 development milestone.
1762696,2018-07-10 04:17:35 UTC,[Expired for neutron (Ubuntu) because there has been no activity for 60 days.]
1762696,2018-05-10 12:14:21 UTC,Pretty standard Ocata Xenial test runs:
1762696,2018-10-25 15:46:07 UTC,Looks like we hit this again today.
1762696,2018-05-10 11:10:51 UTC,"2018-04-07 16:49:39.534 270916 ERROR neutron.api.v2.resource FlushError: New instance <IPAllocation at 0x7fc11a65e450> with identity key (<class 'neutron.db.models_v2.IPAllocation'>, ('1.1.3.62', u'38007c7e-aec9-4743-8fee-ecc9f78c07f9', u'e1e77010-3a1e-4a4e-84fc-263c59c304e0')) conflicts with persistent instance <IPAllocation at 0x7fc11ab22050>"
1762696,2018-05-10 11:12:02 UTC,"Also the bundle might be helpful - this is an error from openstack, not the charm so version is rather important."
1762698,2019-09-03 08:09:20 UTC,"As I see networking-l2gw doesn't use mox, it is only mentioned in lower-constraints.txt"
1762700,2018-04-11 19:58:45 UTC,Using this log tarball: juju-crashdump-ad91fa98-f4a7-4ab3-90a3-e9c2f3b75f9b.tar.gz
1762700,2018-05-15 21:19:18 UTC,Did juju come to some solution here? Could someone summarize what changed?
1762700,2018-04-19 15:41:02 UTC,"If this happens in a container, can you provide:"
1762700,2018-04-18 08:15:40 UTC,"I just ran into this on AWS running Xenial instances and Xenial containers.
I don't know if AttributeError: 'NoneType' object has no attribute
'iter_interfaces' is a red-herring or not, as it does continue onward with
the rest of the actions. (It successfully runs the bootcmd/runcmd stages of
the scripts.)"
1762700,2018-04-12 14:26:01 UTC,My comment/issue appears to be a slightly different bug as it applies to artful+netplan as opposed to xenial
1762700,2018-04-12 14:19:25 UTC,I have replicated this with artful on arm64 and juju 2.3.2:
1762700,2018-04-12 13:25:08 UTC,Removing field critical as this was confirmed to not affect stable juju.
1762700,2018-04-11 22:22:35 UTC,PR for issue as seen in 2.4-beta1: https://github.com/juju/juju/pull/8582
1762700,2018-04-11 22:19:59 UTC,"also an attachment of the entire /var/log/cloud-init.log helps too.
I'm expecting we can see specifically the network config passed to cloud-init local stage with a message like"
1762700,2018-04-11 22:17:24 UTC,anytime I see cloud-init generating tracebacks on network config I generally end up looking at what was metadata provided to the datasource. If possible please also attach /run/cloud-init/instance-data.json if available. (cloud-init v. 17.2 ++)
1762700,2018-04-11 21:26:23 UTC,good news is that lxc exec to the unhappy containers is possible.
1762700,2018-04-11 20:20:19 UTC,"Hmm, after hitting this with 2.4 I switched to 2.3.5 from the snap
store and hit it. I do not have logs from that reproduction. We will
continue to test and see if we can reproduce on 2.3.5."
1762700,2018-04-11 19:56:14 UTC,This is a juju 2.4-beta1 bug per the new log files.
1762700,2018-04-10 14:07:46 UTC,Can you describe the steps used to create the environment? Are these Trusty machines or Xenial?
1762700,2018-04-11 17:43:28 UTC,"From the logs provided, juju is determining ip addresses to give to the containers and the cloud-init-output.log says they were assigned:"
1762700,2018-04-11 18:28:38 UTC,"Ok, the crashdumps with ""da37941a-0cdd-4004-a761-481247ff8bff.tar.gz"" are from the wrong test run. It did not exhibit this bug.  I'm uploading crashdumps from a run that did."
1762700,2018-04-10 11:42:40 UTC,"Is that Juju 2.0.11? I'm pretty sure we don't support that version. 2.0
didn't support network spaces very well, 2.1 would certainly be a minimum
recommendation."
1762700,2018-04-10 11:44:24 UTC,"I believe:
 AttributeError: 'NoneType' object has no attribute 'iter_interfaces'"
1762700,2018-04-10 12:04:08 UTC,"No, it was lxd 2.0.11, sorry, fixed."
1762700,2018-04-10 12:46:33 UTC,Juju crash dump attached
1762700,2018-04-10 11:09:28 UTC,Escalated to Field Critical due to blocking nature of this issue
1762700,2018-04-10 15:44:25 UTC,"The attached crashdump should show how they're being deployed, but
they're all xenial."
1762700,2018-04-11 07:15:07 UTC,"07:13 < jam> jhobbs: my initial thought is that it is a cloud-init bug, where we might be passing something like ""networking=false"" because we are going to set up networking ourself
07:14 < jam> and that causes a particular place that always assumed it had a value to iterate, but the object it has is now None."
1762700,2018-04-11 12:59:32 UTC,Is it possible to get the crashdump from the controller model as well?
1762700,2018-04-11 14:07:33 UTC,"The error at the top of the cloud-init-output.log appears to be a red herring.  It's part of the init-local piece done by cloud-init asap after boot.  I bootstrapped an controller on OpenStack, deployed the ubuntu charm --to lxd.  The container did get an IP addr in this case, but also had the same error at the top of the cloud-init-output.log"
1762704,2018-04-19 16:09:11 UTC,"No has entendido lo que he querido decir. Te lo enseño en este vídeo:
https://youtu.be/_Ym90BbkNCM"
1762704,2019-07-13 09:29:17 UTC,"Hello Alberto,"
1762704,2019-07-11 00:52:48 UTC,"For my record, current code is at:
https://bazaar.launchpad.net/~qr-tools-developers/qr-tools/trunk/files"
1762704,2019-07-11 00:51:07 UTC,"Since:
- Now the app also crashes while scanning QR with the webcam, and has been like that for a while.
- The app seems unmaintained."
1762704,2018-04-23 21:56:26 UTC,"No tientes al volcán, porque soy como Pompella! 🌋"
1762704,2018-04-23 21:07:29 UTC,"Alberto,"
1762704,2018-04-23 17:25:11 UTC,@ Ramiro
1762704,2018-04-22 21:33:21 UTC,"Hola Alberto,"
1762704,2019-07-13 14:03:37 UTC,I will consider that.
1762704,2018-04-19 13:31:15 UTC,"Alberto,"
1762704,2018-04-19 11:27:44 UTC,"¿Cómo se ve el contacto en la aplicación ""Contacts""?
http://www.androidguys.com/wp-content/uploads/2017/08/Google-Contacts.jpg"
1762704,2018-04-18 12:47:55 UTC,"Generated raw text is:
MECARD:N:Alberto Salvia Novella;TEL:;EMAIL:<email address hidden>;NOTE:;BDAY:;ADR:;URL:;"
1762704,2018-04-18 23:43:47 UTC,Alberto
1762704,2018-04-18 21:04:14 UTC,"Si quieres te lo digo en Español, a ver si me comprendes :P"
1762704,2018-04-18 20:59:05 UTC,"Damm, but that's the screen before adding! Not the contact itself, after adding."
1762704,2018-04-18 19:44:10 UTC,Seems ok to me
1762704,2018-04-18 18:47:41 UTC,@ Ramiro
1762704,2018-04-18 15:35:08 UTC,This is the info I get decoding in Android with Moto Camera app:
1762704,2018-04-18 12:52:22 UTC,"I was able to reproduce the error on an iPhone. I'm unable to test on Android, as nobody home has one. I don't own any phone myself."
1762704,2018-04-18 02:08:46 UTC,I can't reproduce the error using my mobile phone. May be you can attach the generated QR code and I will check.
1762704,2018-04-18 23:44:20 UTC,"Olvidé el adjunto, por supuesto xD"
1762724,2018-06-07 11:43:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762724,2018-04-24 14:39:27 UTC,"this came from
 https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2018-April/017967.html"
1762724,2018-10-18 12:12:38 UTC,"Hi,"
1762734,2018-04-11 13:05:54 UTC,This also applies to gnocchi.
1762734,2020-07-20 15:36:03 UTC,This is fixed in Ussuri:
1762734,2019-09-12 13:46:11 UTC,And the cinder keyring too for Nova.
1762738,2018-06-19 05:33:29 UTC,"Your bug report seems to show you're using Unity 7 and not Gnome Shell, so reassigning this to unity."
1762738,2018-06-19 20:53:54 UTC,Can you reproduce on fresh install/live iso? Please try with latest live iso.
1762743,2018-04-10 14:44:41 UTC,https://github.com/kubernetes/cloud-provider-openstack/issues/48
1762752,2020-03-24 21:53:22 UTC,"Due to lack of any activity in this RFE since more than 1 year, I'm going to close it for now. If You would be still interested in implementing this and would like to continue discussion on that, feel free to reopen it and ping me (slaweq) on irc."
1762752,2018-06-04 10:47:35 UTC,"hi, I Have tried this on the nova api as well and found similar results like"
1762766,2018-06-28 14:19:25 UTC,"Verified now, despite me not changing my verification script. Odd."
1762766,2018-07-05 07:55:22 UTC,This bug was fixed in the package apt - 1.2.27
1762766,2018-07-05 07:55:18 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1762766,2018-06-28 14:16:10 UTC,"huh, why did it say backports? Me looks again, and sees the package."
1762766,2018-06-27 15:38:48 UTC,"Hello Graham, or anyone else affected,"
1762766,2018-04-11 11:04:32 UTC,"In our case it burned a number of days of dev time, so this is definitely causing pain."
1762766,2018-06-28 14:14:52 UTC,No package in proposed yet.
1762766,2018-04-11 10:38:36 UTC,"I think so, but I don't think it's worth pushing out an update just for that change. It's been broken since forever, so it's not like it's fixing a regression or something; so I'd probably wait for something else to attach it to."
1762766,2018-04-11 10:14:51 UTC,"Is it possible to backport this to trusty too? This bit us hard, and there are a lot of people out there posting this problem but with no solution."
1762766,2018-04-10 16:58:58 UTC,Queued the fix for xenial in my repo for CI.
1762766,2018-04-10 16:51:51 UTC,"I'm not sure when we fixed that, but we did. So bionic works fine. Not sure about artful."
1762766,2018-04-11 10:41:19 UTC,"Or rather, I'm not sure it's worth it. I plan to look at other fixes in 1.6 soon, and see which of these we need for stable series."
1762768,2018-05-06 15:19:13 UTC,I've spotted this also after a clean install of 18.04.
1762772,2018-04-12 09:44:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762772,2018-04-12 18:36:44 UTC,Symptoms are the same as #1508146 (but I'm not sure it's the same cause).
1762774,2018-04-13 15:22:47 UTC,"Reviewed:  https://review.openstack.org/560031
Committed: https://git.openstack.org/cgit/openstack/puppet-octavia/commit/?id=d6c8f91f6394b7bd1c82fd6212b81d4a10590a3b
Submitter: Zuul
Branch:    master"
1762774,2018-04-16 19:44:50 UTC,"Reviewed:  https://review.openstack.org/561347
Committed: https://git.openstack.org/cgit/openstack/puppet-octavia/commit/?id=613596c267567dd10574d36e89fad2f2e16f9ac3
Submitter: Zuul
Branch:    stable/queens"
1762774,2018-04-13 20:28:36 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/561347"
1762780,2018-10-17 07:12:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762780,2018-04-10 16:50:30 UTC,"StacktraceTop:
 memset () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:186
 _dl_map_segments (loader=0x7ffd5f9af650, has_holes=<optimized out>, maplength=<optimized out>, nloadcmds=2, loadcmds=<optimized out>, type=<optimized out>, header=<optimized out>, fd=<optimized out>, l=0x557b3af33280) at ./dl-map-segments.h:131
 _dl_map_object_from_fd (name=name@entry=0x7f81e7d98acf ""libgomp.so.1"", origname=origname@entry=0x0, fd=<optimized out>, fbp=fbp@entry=0x7ffd5f9af990, realname=<optimized out>, loader=loader@entry=0x557b3af2feb0, l_type=<optimized out>, mode=<optimized out>, stack_endp=<optimized out>, nsid=<optimized out>) at dl-load.c:1126
 _dl_map_object (loader=0x557b3af2feb0, name=0x7f81e7d98acf ""libgomp.so.1"", type=2, trace_mode=0, mode=<optimized out>, nsid=<optimized out>) at dl-load.c:2389
 openaux (a=a@entry=0x7ffd5f9b1020) at dl-deps.c:63"
1762780,2018-04-11 01:05:33 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1762785,2020-06-25 08:48:18 UTC,"Hello,"
1762788,2018-04-11 07:08:46 UTC,in such cases always first start a question.
1762795,2018-10-05 14:07:13 UTC,"Reviewed:  https://review.openstack.org/590421
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=abd9ea280042b1dd1bc76bdff9aa05b7a284dfdb
Submitter: Zuul
Branch:    stable/ocata"
1762795,2018-04-10 17:39:06 UTC,i guess they are new with pycodestyle 2.4.0
1762795,2018-04-11 15:10:31 UTC,"Reviewed:  https://review.openstack.org/558621
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=e93a57d5323464f3f2e5660e606ab92f5ea2b77a
Submitter: Zuul
Branch:    master"
1762795,2018-04-11 15:11:15 UTC,no longer critical
1762795,2018-06-04 10:09:30 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/572071"
1762795,2018-06-05 04:11:28 UTC,"Change abandoned by YAMAMOTO Takashi (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/572071
Reason: merged into https://review.openstack.org/572242"
1762795,2018-07-12 15:23:15 UTC,"Reviewed:  https://review.openstack.org/572242
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=ae2ed9a6dff37d9b04525643c8fe8dc76766a225
Submitter: Zuul
Branch:    stable/queens"
1762795,2018-07-13 14:38:55 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/582607"
1762795,2018-08-09 16:34:16 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/590421"
1762799,2018-04-11 09:06:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762803,2018-07-26 08:57:42 UTC,This issue was fixed in the openstack/python-openstackclient 3.16.0 release.
1762803,2018-06-04 03:27:17 UTC,This issue was fixed in the openstack/python-openstackclient 3.14.2 release.
1762803,2018-04-10 19:36:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/560132"
1762803,2018-04-20 14:05:49 UTC,"https://review.openstack.org/560132 is merged, I'm not sure why this bug isn't marked closed for rocky."
1762815,2018-04-10 19:12:46 UTC,Fix pushed:
1762815,2018-05-01 00:58:48 UTC,"The fix works for me. Pushed to master, rel_3_0, and rel_2_5. Thanks, Bill!"
1762817,2018-04-12 06:17:28 UTC,"It seems like this might be an unsupported hack: ""For example on Macs, it returns java.lang.UnixProcess which has a private field called pid. Using Reflection you can easily get the value of this field. This is admittedly a hack, but it might help. What do you need the PID for anyway?"" https://stackoverflow.com/questions/4750470/how-to-get-pid-of-process-ive-just-started-within-java-program/5578924"
1762817,2020-05-14 09:03:26 UTC,"Since Java 9 class Process has new method long pid(). However, this requires that we update the language version to 11, which should be ok, as 1.8 is soon EOL."
1762817,2020-07-22 11:13:52 UTC,"Java version is updated to 11, so we replaced the existing implementation with net pid() method"
1762818,2018-04-22 19:58:38 UTC,A victim of some other fix.  This regression can be prevented by adding amdgpu.dc=0 to the kernel command line.
1762818,2018-11-12 07:30:07 UTC,This change was made by a bot.
1762827,2018-07-28 17:02:46 UTC,"Same as Phil trying to install Wine on 18.04.
I also got a different error trying to do a git make but when it tried to send report it said my Ubuntu was not valid and remove 3rd party software (?)"
1762827,2018-06-23 18:58:28 UTC,"I got this error message while attempting to install Wine from the Ubuntu 18.04 repository. The Wine install failed.
Thanks,
Phil"
1762827,2018-04-11 17:05:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762835,2020-01-14 16:12:15 UTC,This bug was fixed in the package linux-raspi2 - 5.3.0-1015.17
1762835,2020-01-06 13:36:26 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1053.57
1762835,2020-01-06 13:15:05 UTC,This bug was fixed in the package linux-raspi2 - 5.0.0-1024.25
1762835,2020-01-06 12:54:28 UTC,This bug was fixed in the package linux-raspi2 - 5.3.0-1015.17
1762835,2019-10-25 08:07:57 UTC,"The error is benign, meaning that the kernel simply tries to load a driver for a device that is already managed by a different driver and thus logs an error. I don't believe that this is the cause of the issue you're seeing."
1762835,2019-10-09 06:33:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762835,2018-05-14 17:16:48 UTC,I sent the patch to the kernel mailing list back in April: https://lists.ubuntu.com/archives/kernel-team/2018-April/091646.html
1762835,2018-05-14 17:14:26 UTC,"This really needs fixing as it clearly is confusing users.  It is a very visible error message, especially if you boot with 'quite splash' as it remains on the boot screen for quite a few seconds."
1762835,2019-10-25 07:39:18 UTC,Hello @juergh
1762835,2018-04-17 20:27:00 UTC,Just for fun I did the reverse - i.e. downstream mmc modules removed and upstream modules kept in. Note how confusing the mmc module messages are in dmesg.  It is impossible for the casual reader of the dmesg logs to tell which mmc module are in use.
1762835,2018-04-17 20:23:18 UTC,This is the dmesg with the patched kernel (upstream mmc modules removed).
1762835,2018-04-17 21:16:38 UTC,Raspbian dmesg
1762835,2018-04-11 22:58:31 UTC,Attached is a config patch.
1762835,2018-04-11 22:44:50 UTC,This is the Xenial config: It uses bcm2835 and bcm2835_sdhost which is a mix of the upstream and downstream drivers.
1762835,2018-04-10 22:05:46 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1762835,2018-04-10 21:58:18 UTC,Same problem if I upgrade to 4.15.  Note the
1762845,2018-04-21 23:24:23 UTC,The Details link should still be there as it should take you to the details page where you can see comments if any had been left as well as additional metadata.
1762845,2019-12-10 23:23:36 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10665"
1762845,2020-03-31 19:17:06 UTC,"Reviewed:  https://reviews.mahara.org/10665
Committed: https://git.mahara.org/mahara/mahara/commit/4c567b3cf29e9044760bb30041569c2e885f7308
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1762846,2018-05-23 20:32:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762850,2018-04-10 23:05:18 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1762852,2018-04-11 10:10:05 UTC,I think general best practice would be to use the 'pause-health' and 'resume-health' actions on one on the ceph-mon units before commencing the ceph-osd upgrade; however there is another bug here in the fact that the charm moves on after 10 minutes of waiting - which is insufficient.
1762852,2018-04-11 10:13:13 UTC,"OSD's are upgraded in turn so I think a general heartbeat timestamp from the current unit performing the upgrade is probably a good idea - for units with lots of osd and lots of data, 10 minutes is just to short..."
1762852,2020-07-06 16:15:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/739535"
1762852,2020-07-17 15:11:21 UTC,"Reviewed:  https://review.opendev.org/739535
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=6b0a11b4048027d7de11d28bbf388bd0c337400f
Submitter: Zuul
Branch:    master"
1762873,2018-04-11 13:01:54 UTC,"Hi,"
1762873,2018-04-13 13:19:12 UTC,"An idea that has been floated is having a prebuilt image (either a VM image or an lxd image; I think the latter would be preferrable) with all the components configured and compiled to point to staging, with appropriate keys."
1762873,2018-12-19 14:56:13 UTC,"Purchasing will be redesigned/reimplemented, and the current implementation is configured to be unusable. Won't fix this bug as is."
1762873,2018-04-12 23:26:23 UTC,"One of the issues using the staging store is you need to recompile snapd to use it. So that make it harder to run on a standard image for example. Aside from that, I think it should be acceptable to use the staging store, as it will be close enough to a real-world test."
1762886,2018-04-11 21:12:51 UTC,Can you please share the following information:
1762886,2018-05-03 18:10:27 UTC,@shiliang - can you give the 'openstack router create...' command arguments you are using to create the router?  And the version of neutron you are using?  Thanks.
1762888,2020-10-21 06:11:23 UTC,Could you check with 0.92.5 or later?
1762888,2020-10-23 00:33:50 UTC,Thanks for looking into this. I tried 1.0.1 and the export works as expected.
1762888,2020-10-23 05:07:12 UTC,"Awesome, setting to fix released. Thanks for retesting, if you find any more bugs, please feel free to report (we've moved to GitLab, see http://inkscape.org/report)."
1762888,2018-04-11 13:14:10 UTC,"Hi,"
1762888,2018-04-11 01:47:19 UTC,The exported pdf is attached here.
1762888,2018-04-11 06:38:48 UTC,"Hi,"
1762898,2020-09-09 13:20:22 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1762902,2018-04-11 05:00:00 UTC,"Hi Hongbin,"
1762902,2018-04-12 03:57:14 UTC,"@Deepak,"
1762902,2019-02-22 04:58:27 UTC,"Reviewed:  https://review.openstack.org/633371
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=d0a7940981bb123bfc12d4ed2d24a4bf50e513e4
Submitter: Zuul
Branch:    master"
1762910,2018-04-11 10:42:59 UTC,The position is probably shifted because of the bar displayed under the icon but not when muted
1762910,2018-04-12 02:06:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762910,2018-05-09 05:19:08 UTC,"To avoid any odd-looking padding I think the solution would be to enforce the OSD to stay as a square always, and just optionally paint the bar over the top (possibly with a border to avoid conflicting with some/future icons)."
1762910,2018-05-09 05:19:47 UTC,Maybe also shrink the icon so as to ensure it never touches the bar when the bar is visible.
1762912,2018-11-08 20:57:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762920,2018-04-11 08:20:46 UTC,"The attachment ""PATCH: casper-helpers try_mount() diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1762930,2018-08-05 13:20:10 UTC,This was fixed in https://github.com/openstack/cloudbase-init/commit/24365043e31a7cb0899d2222bbba654ef718da5b
1762930,2019-06-20 12:13:25 UTC,"closing the bug, as the fix has been released: https://github.com/cloudbase/cloudbase-init/commit/24365043e31a7cb0899d2222bbba654ef718da5b"
1762930,2018-07-26 15:11:52 UTC,"Hello,"
1762935,2018-04-16 09:24:30 UTC,"After reinstalling Apache2, PHP 7.2, and Redis (and generating a new SSL-Cert) the system will run again without errors."
1762940,2018-08-31 19:57:21 UTC,This issue also occurs on arm64. Attached is a screenshot from a HiSilicon D05 running 18.04.
1762940,2018-09-19 06:53:35 UTC,"Hi:
Please refer to this wiki:
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel"
1762940,2018-09-19 02:01:06 UTC,"@AaronMa
Do you have docs for how to compile a new kernel. I can found below doc link
https://help.ubuntu.com/community/Kernel/Compile
But it seems a bit old."
1762940,2018-09-07 20:57:25 UTC,"@Mao: correct, I do not observe screen blur in d-i on D05."
1762940,2018-09-06 01:33:20 UTC,@Zhanglei
1762940,2018-09-04 08:11:17 UTC,"For #37 screen shot and #39. We found this wayland issues for 18.04 and Huawei x86 server, but it seems no for 18.04.1. In my test, apt-get install ubuntu-desktop and reboot works fine."
1762940,2018-09-05 17:06:32 UTC,"This is definitely reproducible on a D05 (arm64) with 18.04 running wayland, and the symptoms look identical. I re-tested with the 18.04.1 ISO and confirmed."
1762940,2018-09-04 09:01:39 UTC,For #37-#39
1762940,2018-08-31 20:23:26 UTC,"As observed on x86, disabling wayland also avoids the problem on ARM."
1762940,2019-04-04 14:11:54 UTC,summary for workaround via kernel parameter to blocker loading:
1762940,2018-09-06 00:48:14 UTC,"Dann,"
1762940,2019-05-14 07:56:36 UTC,"@Aaron Ma
I want to test your patch. But seems it would patch with error. I guess, the new 18.04 source code have been change to:
        list_add_tail(&vgadev->list, &vga_list);
instead of:
-	list_add(&vgadev->list, &vga_list);
+	list_add_tail(&vgadev->list, &vga_list);
Does it mean this patch have been already merged in our new source. In last month, I testing with 18.04.2 iso (d-i) and this screen blur is still existing. Does it mean this patch did not solve our cases."
1762940,2018-08-31 08:54:04 UTC,"Hisilicon team said this driver (hibmc_drm) are only for arm64. For X86 architecture, it need to use default driver for this SM750."
1762940,2019-05-17 00:57:42 UTC,"For #44, in the following testing, if disable hibmc_drm loading, then it works fine and would not be hang."
1762940,2019-07-25 16:04:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1762940,2019-07-25 18:32:41 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1762940,2019-07-28 23:34:02 UTC,"I installed 4.15.0-56-generic to a bionic VM, with the -modules and
-modules-extra packages. I went into /var/lib/modules/4.15.0-56/ and did a search for
hibmc_drm. There was no mention apart from a header Makefile. The module was not
built and not present on amd64."
1762940,2019-08-07 08:34:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1762940,2019-08-07 22:55:13 UTC,"I installed linux-hwe 4.15.0-57 #63~16.04.1-Ubuntu on xenial, and ensured the -modules and -modules-extra package was installed."
1762940,2019-08-09 11:38:28 UTC,This bug was fixed in the package linux - 5.2.0-10.11
1762940,2019-08-13 08:59:53 UTC,This bug was fixed in the package linux - 5.0.0-25.26
1762940,2019-08-13 11:27:47 UTC,This bug was fixed in the package linux - 4.15.0-58.64
1762940,2019-08-15 22:31:24 UTC,I have submitted the patch upstream to dri-devel and CC'd the hibmc maintainers.
1762940,2019-09-30 03:30:27 UTC,The patch has been mainlined as of Linux 5.4-rc1 with:
1762940,2019-05-16 06:49:02 UTC,"For #44 Aaron's suggested patch, it seems patch have been included after 4.15.0-46. The testing 18.04.2 iso with 4.15.0-48 kernel seems the system would be hang on language selection after select install server of grub screen. So it seems this hibmc_drm would caused another this hang issues too."
1762940,2018-08-31 02:27:51 UTC,"Huawei hisilicon team thought it might be caused by hibmc_drm which are upstream and included in v4.10 kernel for their ARM64 server. It is right. After disable this module by:
 modprobe.blacklist=hibmc_drm
In the grub whiling booting iso. The install screen blur was disappeared."
1762940,2018-09-26 22:20:03 UTC,"With 18.04 UEFI on x86, does passing the kernel parameter ""video=efifb:off"" make a difference?"
1762940,2018-08-29 02:13:45 UTC,"Tested with 18.04.1 Desktop, it wouldn't screen blur. The kernel log are enclosed."
1762940,2018-04-11 14:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1762940,2018-04-11 14:59:33 UTC,"Hey Mao, Is this visible after install?"
1762940,2018-04-17 03:22:02 UTC,"The screen also get blur after ubuntu 18.04 beta2 was installed by legacy bios on Huawei server (VGA card is SM750 which was embedded in Hi1710 iMBC chips).  The ubuntu-destktop was installed by ""apt-get install ubuntu-desktop and init 5 to switch to x."
1762940,2018-04-17 10:18:54 UTC,"For Xenial ubuntu-deskto on Huawei server testing (UEFI), all kernel 4.4 (default) and 4.13 (hwe) and 4.15 (hwe-edge) works well (no screen blur)."
1762940,2018-04-20 14:46:19 UTC,"Today, Huawei side did x-window testing 16.04.04 in legacy BIOS model, all 4.4,4.13(hwe),4.15(hwe-edge which as as 18.04), 4.17rc1 works fine (no screen blur)."
1762940,2018-05-07 02:45:23 UTC,"Below image uses the Subiquity and it can be installed successfully. But after install ubuntu-desktop, the login screen would become screen blur after reboot or init 5, but it can be start by startx after init 3 in the terminal.
http://releases.ubuntu.com/18.04/ubuntu-18.04-live-server-amd64.iso."
1762940,2018-05-10 09:11:49 UTC,"Blur screen for GDM login was caused by wayland, it can be fix by force to use Xorg in /etc/gdm3/customer.conf to uncoment WaylandEnable=false"
1762940,2018-05-17 23:06:47 UTC,"For ISO of classic Debian installer (d-i), it would become screen blur after kernel load and in the first screen of ""select a langue"""
1762940,2018-05-22 13:10:41 UTC,"This bug seems related with 4.15.0-20, the test result on UEFI model for different combination of 16.04, 18.04 and their kernel are below:
18.04(d-i not subiquity) with 4.13 kerel:               no screen blur
18.04(d-i not subiquity) with 4.15.22 kerenl:           no screen blur
16.04 with 4.15.20 kernel                               screen blur
18.04(d-i) with 4.15.20 kernel                          screen blur
Notes: 4.13 kernel come from 16.04.4 ISO
       4.15.0-22 kernel come from upgrading installed 18.04
       screen blur means blur screen picture for language select page
       Test with customized ISO which was replaced by vmlinux and initrd (new kernel)"
1762940,2018-05-23 09:36:05 UTC,"In #18, 4.13 should replaced with 4.4.0-116 which used by 16.04.4 ISO."
1762940,2018-06-25 09:10:45 UTC,The daily build is still use 4.15.0-20 kernel. It was expecting of update and fix this blur problem. http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/20180625/bionic-server-amd64.iso
1762940,2018-07-13 18:13:46 UTC,"This looks to me as if Ubuntu (the kernel, Wayland, and/or the X server, depending on when the problem occurs) is delivering a video mode that the display device can't handle. (With VGA, the display should deliver its capabilities to the computer via EDID, but this doesn't always work correctly.) Thus, the first question is what that ""display device"" is. The screen shots look like a remote KVM of some sort. Is that the BMC's built-in screen-sharing tool, a network-accessible KVM hardware device (like a Raritan or Avocent), or something else? If possible, I recommend testing in person with a plain monitor plugged directly into the computer, at least as a diagnostic procedure. If that works, then it's likely that the issue is either a matter of a restrictive set of video modes in the remote-access tool, miscommunication between the remote-access tool and the kernel/Wayland/X, or both. Also, if a physical monitor is plugged into the server while it's being accessed remotely, it's conceivable that the kernel/Wayland/X is taking its cues about video mode from the physical monitor rather than from the remote-access tool, thus creating a mismatch. If the problem is caused by the remote access tool, or by an interaction between that and the kernel/Wayland/X, then updating the remote access tool's firmware may fix the problem."
1762940,2018-08-29 08:11:38 UTC,"In case 18.04.1 server and destop iso use same kernel of v4.15.0-29 and the GUI works fine on destop, so the kernel should not be blamed."
1762940,2018-08-29 02:09:23 UTC,"Tested on 17.10 server d-i install, it would be screen blur too during installation, the kernel is 4.13.0."
1762940,2018-08-23 11:16:53 UTC,ACPI Exception have been reported here and it seems not related to screen blur
1762940,2018-08-23 10:59:21 UTC,"In the screen blur kernel syslog, it show below error which 16.04.5 GA kernel don't have this error:
...
Aug 21 10:25:50 kernel: [    0.589408] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381)
(repeated 942 lines)
..."
1762940,2018-08-22 09:50:36 UTC,"replace 18.04.1 with 4.15.0-29 kernel from my laptop (16.04) and it would be screen blur too. The syslog are enclosed here. If I replacing it with 4.15.0-32-generic from my laptop, it would not be screen bure on language select screen, but the system seems hanged (died) in case I can't switch to tty2 or press ""enter"" key to continue."
1762940,2018-08-22 09:46:07 UTC,The 18.04.1 ga-kernel (4.15.0-29) would be screen blur. The syslog are enclosed too.
1762940,2018-07-17 11:18:49 UTC,This bug seems related with the kernel or 4.15.0-20 of d-i ISO. Please refer to #18 for test results on different kernel.
1762940,2018-08-22 09:42:07 UTC,I test 16.04.5 ga-kernel would not be screen blur but the hwe-kernel(4.15.0-29) which is same as 18.04.1 would become screen blur.
1762940,2018-08-21 09:33:19 UTC,"I just tested with /boot/vmlinuz-4.15.0-29-generic which from my laptop ( to replace install/vmlinuz with this file), it would be screen blur.  If I use 4.15.0-32-generic, blur would disappear."
1762940,2018-08-13 08:40:12 UTC,I have tested with 18.04.1 on Huawei FusionServer 2288 again. The screen blure is same. The kernel of this iso have been update to 4.15.0-29-generic.
1762940,2018-07-17 12:23:00 UTC,"The daily build is still use 4.15.0-20 kernel.
http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/current/bionic-server-amd64.iso"
1762940,2018-08-22 09:43:58 UTC,The 16.04.5 ga-kernel wouldn't be screen blur and their syslog are enclosed.
1762955,2020-03-30 17:07:23 UTC,Closing because INVALID: can't replicate on the following versions/OSes (FIXED) --
1762958,2018-04-11 09:17:39 UTC,"Have pushed a patch.
https://review.openstack.org/#/c/560324/"
1762978,2020-06-25 13:30:27 UTC,"I have just experienced this on Kubuntu 20.04. I have an nvidia card and apt just upgraded the nvidia drivers. I wonder if that is related. After the upgrade, blender refuses to start, stating that there is no supported graphics card so *something* has changed there."
1762978,2020-10-14 01:26:39 UTC,reboot command.
1762978,2020-10-14 01:25:35 UTC,I just updated my NVIDIA driver on Kubuntu 20.04. I had to use a konsel and issue the rebbot command to bypass this problem. Could this be a problem with NVIDIA drivers.
1762978,2019-03-08 09:21:08 UTC,"Also happens from time to time (no update happening), but not reproducibly, on Kubuntu 18.04 LTS"
1762978,2019-03-08 09:20:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762984,2018-04-25 06:20:34 UTC,More on this:
1762984,2018-04-27 09:53:39 UTC,Works now.
1762984,2018-04-27 10:15:13 UTC,Nope. Still an issue.
1762984,2018-05-29 18:25:48 UTC,"Fixed - The symlink of resolv.conf was wrong. The following shows how - resolv.conf-BAK was the old, broken one, resolv.conf the one I fixed. I don't know how that happened, but I have installed the 18.04 beta version, may that was the reason."
1762988,2018-12-28 16:54:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762988,2018-12-28 17:25:48 UTC,"This also affects the 18.04.1 ""alterantive installer (debian-installer), where I reproduced it today."
1762988,2018-12-28 17:37:32 UTC,The root cause of this is discussed at bug #1565950.
1762999,2019-02-12 05:07:58 UTC,Bug still exists.. Really regretting I updated to 18.04.. Even almost one year after release there are still so many things not working...
1762999,2018-10-06 13:12:25 UTC,Still broken on 18.04 LTS (!!!!!!).
1762999,2018-10-06 13:22:30 UTC,"Norbert, don't hesitate to help with a fix! Thanks!"
1762999,2018-10-06 14:26:37 UTC,Dear Sylvestre!
1762999,2019-03-14 18:40:36 UTC,I can see a fix added recently into universe(proposed) at https://launchpad.net/ubuntu/+source/scilab/+index by Łukasz Zemczak. When will this make it into release?
1762999,2018-10-06 12:42:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762999,2020-09-25 08:50:45 UTC,KO with
1762999,2020-09-25 08:58:55 UTC,After purge desinstallation and reinstallation :
1762999,2020-09-25 09:01:48 UTC,It is for Scilab 6.1.0 apt installation
1762999,2020-09-25 16:01:37 UTC,"That was a regression introduced by OpenJDK 11.0.6, it is being tracked in bug 1870813."
1762999,2020-09-25 08:43:08 UTC,Still error in Ubuntu 20.04 !
1762999,2018-08-07 20:49:15 UTC,"Just installed 18.04, Scilab is broken."
1762999,2018-04-25 20:52:02 UTC,Bug exists in Ubuntu 18.04 LTS with all updates.
1762999,2018-07-07 18:09:44 UTC,Bug still exists on Ubuntu 18.04 LTS with all updates.
1762999,2018-07-24 15:27:50 UTC,18.10 cosmic is affected too.
1762999,2018-04-11 11:52:45 UTC,apport information
1762999,2018-04-11 11:55:46 UTC,Same on clean netboot.iso.
1762999,2018-04-14 13:39:58 UTC,Problem is not fixed. Even with proposed updates. Scilab is unusable.
1762999,2018-04-17 21:27:08 UTC,Problem is not fixed. Even with proposed updates. Scilab is unusable.
1762999,2018-04-11 11:52:44 UTC,apport information
1762999,2018-04-26 09:16:39 UTC,Scilab on Bionic starts normally if I have OpenJDK 9 (reproducible only on one system):
1762999,2018-04-30 02:11:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1762999,2018-05-02 20:34:53 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1762999,2018-04-22 18:55:47 UTC,Problem is not fixed. Even with proposed updates. Scilab is unusable. Ubuntu 18.04 LTS with all updates.
1763006,2018-04-28 06:28:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763006,2018-05-09 15:34:04 UTC,The package name is (was) actually gdb-arm-none-eabi.
1763006,2018-05-09 15:50:15 UTC,Using gdb-multiarch seems to be an alternative.
1763006,2018-08-20 10:18:22 UTC,I tried the gdb-multiarch and it gives me
1763006,2019-04-13 23:24:47 UTC,"gdb-multiarch seemed like it should work.
I use openocd 0.10.0 but when I attempt a connection to it reports of my SAMD09D14A (on an Adafruit Seesaw)
""warning: Architecture rejected target-supplied description
...
Truncated register 16 in remote 'g' packetInfo : dropped 'gdb' connection"""
1763006,2019-04-21 20:37:50 UTC,"I came across this while following the Apache mynewt blinky tutorial, with a nRF development board https://mynewt.apache.org/latest/tutorials/blinky/nRF52.html
The mynewt load target script has hard-coded the arm-none-eabi-gdb command -> not found error."
1763006,2020-08-16 16:35:43 UTC,"I just tried installing gdb-multiarch as a replacement for gdb-arm-none-eabi for an Atmel SAMD target and an STM32 target, and that worked out of the box. Maybe this issue can be closed?"
1763008,2020-09-25 04:17:21 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1763008,2020-07-26 13:53:13 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1763020,2018-05-15 05:26:11 UTC,The same bug has been fixed in Nove recently (https://bugs.launchpad.net/nova/+bug/1765144). But it is still there in Cinder.
1763025,2020-10-16 18:22:14 UTC,This bug was fixed in the package ubiquity - 20.10.12
1763025,2020-04-19 02:19:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763025,2018-04-11 15:08:32 UTC,"Thanks for your report. It's worth looking into, but it won't be fixed for Ubuntu 18.04."
1763033,2019-10-14 13:41:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763036,2019-06-08 10:29:29 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1763036,2019-08-08 04:17:21 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1763037,2019-06-05 08:45:41 UTC,"The flag is enable in Ubuntu 18.10 and newer, unsure if that would be a candidate for a LTS backport though"
1763040,2019-02-14 16:54:59 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1763040,2018-04-11 14:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1763040,2018-04-23 23:51:27 UTC,This bug was fixed in the package linux - 4.15.0-19.20
1763040,2018-04-23 23:52:13 UTC,This bug was fixed in the package linux-meta - 4.15.0.19.20
1763040,2019-02-14 12:12:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1763043,2019-09-16 15:20:21 UTC,This is no longer valid on master (Train) due to this change:
1763043,2019-09-16 15:19:08 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/560467
Reason: Since https://review.opendev.org/#/c/634606/86/nova/compute/resource_tracker.py the merge conflict on this makes this no longer fixable on master, i.e. live migration is supported with move claims on master now. Given how low priority this is with not much interest it's likely not worth backporting at this point either."
1763043,2018-04-11 15:21:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/560467"
1763046,2018-04-12 08:09:10 UTC,"Usage error - need to run make rpm before running make containers.
Two AIs:
1) Improve documentation to clarify this
2) Update makefiles to handle this dependency automatically."
1763047,2018-04-11 16:21:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1763048,2019-10-29 21:20:09 UTC,Since the minimum length check has been merged into snapd I'm marking the task as fix released (it was released since the commit was merged).
1763048,2018-04-11 16:16:29 UTC,"Just to be clear, at the time of writing all projects do the same check: they check that regexp, and that it neither starts nor ends with a dash, nor contains a double dash, nor is longer than 40 characters.  The rationale for doing it like this instead of with a single regexp is well documented in the projects themselves; for example, from snapd:"
1763048,2018-04-24 09:50:52 UTC,Isn't this a dup of LP: #1751447 ?
1763048,2018-04-25 10:17:46 UTC,"Sergio, I left it open because this one explicitly mentions min length, which I think we're not checking."
1763048,2018-07-11 21:31:51 UTC,The minimum length check is now implemented in trunk.
1763048,2018-11-14 16:31:40 UTC,"The snapd ""ValidateName"" code checks for length since 362784dc523520b8257450664a76f507dc28a4e0"
1763051,2018-10-24 19:23:44 UTC,"Reviewed:  https://review.openstack.org/612714
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ae2da62955e5c856fec71eebb4f3458fb4c7fb79
Submitter: Zuul
Branch:    stable/rocky"
1763051,2018-10-23 18:33:59 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/612773"
1763051,2018-10-24 21:41:35 UTC,"Reviewed:  https://review.openstack.org/612773
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6b065dad8015ea4fdacb0aedc763b38c5c8a9130
Submitter: Zuul
Branch:    stable/queens"
1763051,2018-10-23 14:25:51 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/612714"
1763051,2018-10-15 22:20:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/610739"
1763051,2018-04-17 17:11:07 UTC,I agree to fix this. I will also open a blueprint to do the audit on the rest of the start/end notification as it feels we have more such places.
1763051,2018-10-22 19:33:15 UTC,"Reviewed:  https://review.openstack.org/610739
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7a2228142b8f8f015a554e2b25198ab37811a058
Submitter: Zuul
Branch:    master"
1763070,2019-01-08 22:10:10 UTC,I get this too on my lab with slow virtual controllers when testing test_dualnet_multi_prefix_dhcpv6_stateless ...
1763070,2019-01-08 22:10:37 UTC,{0} tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_slaac_from_os [153.546098s] ... FAILED
1763070,2019-01-08 22:11:49 UTC,Question:   Is the following the proper value to tweak here ?
1763070,2019-10-31 21:57:12 UTC,Slawek noticed that n-api is hitting a MessagingTimeout during a resize call and I traced that down to a POST /allocations call from nova to placement:
1763071,2018-04-11 16:21:20 UTC,See also https://forum.snapcraft.io/t/4930/3
1763074,2018-04-11 16:00:14 UTC,A test or example that uses this interface would be great.  I'm trying to use this interface myself and if successful I might circle back and submit an update to the 'benchmark' example to make it introspectable.
1763089,2021-02-18 16:46:18 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1763089,2018-08-01 10:14:20 UTC,"I believe this is caused by problems with nested virtualization when running certain kernels on Skylake. When I manually changed the CPU model in libvirt, the VM does boot."
1763089,2018-06-18 09:49:46 UTC,"Still seeing this with latest master - undercloud VM is stuck after
""
Probing EDD (edd=off to disable)... ok
"""
1763089,2018-06-07 16:19:03 UTC,Finally managed to grab the state of the console via virt-manager:
1763089,2018-04-13 12:17:44 UTC,Just tried again with the image that was built yesterday (from /queens/rdo_trunk/b18490299814d62f21b6594a3e95da68465b2e0d_85b157a9) with the same result.
1763089,2018-04-13 11:10:05 UTC,Not sure what you mean?
1763089,2018-04-13 01:41:06 UTC,"you're probably having issues with RDO cloud, don't you?"
1763089,2018-06-07 16:09:44 UTC,Still happening with today's checkout. Would be grateful for any troubleshooting suggestions...
1763091,2019-06-27 19:38:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, according to this report, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. Thanks in advance."
1763091,2018-04-27 17:22:16 UTC,I'm having the same problem with a fresh Xubuntu 18.04 install
1763091,2018-05-01 12:58:19 UTC,"I'm having the same problem with a fresh Ubuntu 18.04 install.
I installed netbeans through the command:"
1763091,2018-06-05 19:44:35 UTC,"I have the same problem, with the IDE. If urgent for my case, download jdk-8u171-nb-8_2-linux-x64.sh from netbeans.org."
1763091,2018-06-14 03:26:20 UTC,I believe that there are two separate bugs here.
1763091,2018-06-14 03:39:21 UTC,"(By the way, should this bug be marked as a duplicate of #1760907? I assume most people who are subscribed to this care more about the crash than the use of a deprecated feature that still works. The crash has nothing to do with Java 9, though; it can be reproduced even running NetBeans under Java 8.)"
1763091,2019-01-09 09:34:34 UTC,NetBeans needs to be updated to version 10. This problem is entirely caused by Ubuntu having an old version of NetBeans.
1763099,2018-04-30 23:34:24 UTC,"Reported to libiberty developers:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85452"
1763099,2018-04-13 13:29:01 UTC,"Reported to binutils developers:
https://sourceware.org/bugzilla/show_bug.cgi?id=23058"
1763099,2018-04-13 12:00:10 UTC,Thanks for taking the time to report this bug and helping to make Ubuntu better.
1763100,2018-09-04 10:49:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763100,2018-09-04 10:50:20 UTC,This solution seems to work. Thanks! ;)
1763100,2019-03-07 19:09:05 UTC,Here is an actual patch that fixes the problem.
1763100,2019-03-07 20:21:35 UTC,"The attachment ""console-setup-1.178ubuntu9-JNZ-1.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1763100,2019-05-02 21:27:36 UTC,"I confirm the bug also on Ubuntu 19.04.
Patch on post #3 resolve the problem."
1763100,2021-01-16 10:21:27 UTC,"I confirm the bug also on Ubuntu 20.04.1
Patch on post #3 resolve the problem."
1763101,2019-10-11 08:50:30 UTC,Here is the changelog which fix this.
1763101,2018-04-30 23:31:24 UTC,"Reported to libiberty developers:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85453"
1763101,2019-10-11 08:49:23 UTC,"It is fixed in binutils 2.32.
should we backport it in 2.30?"
1763101,2018-04-13 12:00:01 UTC,Thanks for taking the time to report this bug and helping to make Ubuntu better.
1763101,2018-04-13 13:31:24 UTC,"Reported to binutils developers:
https://sourceware.org/bugzilla/show_bug.cgi?id=23059"
1763102,2018-04-13 11:59:42 UTC,Thanks for taking the time to report this bug and helping to make Ubuntu better.
1763102,2018-04-13 13:27:01 UTC,"Reported to binutils developers:
https://sourceware.org/bugzilla/show_bug.cgi?id=23057"
1763102,2018-04-30 23:37:43 UTC,"Reported to libiberty developers:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85454"
1763111,2020-02-17 14:33:53 UTC,"This is caused by the KDE session restoration mechanism, which starts a second instance.
The second instance sees the first and pings it to open the main window."
1763111,2018-04-14 13:52:17 UTC,This is a Bionic Beaver bug: I don't know how to tell you...
1763111,2018-04-27 06:22:35 UTC,"Solved! Today I removed in Settings - autostart the autokey-gtk -c starting program, and then added autokey program. So the problem is solved."
1763111,2018-04-27 07:39:46 UTC,No! Solved once yes and once not. This is the .desktop:
1763111,2018-04-27 07:42:34 UTC,And this is the warning message in terminal:
1763111,2018-04-27 08:53:03 UTC,"Seems that the problem is ""autokey-gtk -c"" command: instead works correctly ""autokey"" command."
1763116,2018-04-13 10:02:20 UTC,"I agree this would be helpful.  At the moment we use cgit for the repository browser interface on git.launchpad.net, and while it's very fast and we could more or less drop it in with minimal work, it may be difficult to customise it in this kind of way.  I'm not entirely ruling it out, but I think I've tried before and failed to find exactly the switch we'd need."
1763118,2020-08-15 18:47:33 UTC,"Hi,"
1763145,2018-04-30 15:06:43 UTC,the issue is in the video driver
1763145,2018-04-11 18:42:53 UTC,"StacktraceTop:
 ?? ()
 pipe_resource_reference (tex=0x0, ptr=0x7f98341b1840) at ../../../../src/gallium/auxiliary/util/u_inlines.h:144
 vl_compositor_cleanup_state (s=s@entry=0x7f98341b1828) at ../../../../src/gallium/auxiliary/vl/vl_compositor.c:1466
 vlVaTerminate (ctx=<optimized out>) at ../../../../../src/gallium/state_trackers/va/context.c:353
 vaTerminate (dpy=0x7f9834065060) at va.c:751"
1763151,2018-04-20 09:38:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763152,2018-04-11 19:31:33 UTC,Confirmed. To see this behavior:
1763155,2018-04-11 19:39:38 UTC,"Oh, weird. The value for this column does not display when first retrieving the interface, but if I add a message, it does display. I see the same behavior with the Staff Alert field."
1763155,2018-04-11 19:46:04 UTC,"I've updated the description based on the behavior I now see. Also, my initial recommendation was to remove the Name field because I thought it showed the same info as the Label field, but I know realized that I was incorrect on that assumption."
1763157,2018-04-11 19:38:41 UTC,VPN config is as follows:
1763157,2018-04-11 20:18:11 UTC,Maybe it is the same situation as in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1551823 ...
1763157,2018-04-24 09:17:24 UTC,"To further proof the issue I now tested the same scenario with another wifi usb module in the same network/router setup, this time the driver module was rt2800usb.
Same result."
1763175,2018-04-11 21:01:04 UTC,"Status log for test/0, for comparison. No upgrade-charm occurs."
1763175,2018-04-11 20:58:06 UTC,Attached output of juju status - this is a minimal test charm with an install hook that sets the status message to the output of `resource-get test0`. Note that the leader is the one who was missing a resource.
1763175,2018-04-11 21:00:07 UTC,Status log for test/1. Note that the upgrade-charm hook occurs; I never called `juju attach` or `juju upgrade-charm`.
1763175,2018-04-11 21:01:56 UTC,"Attached juju debug-log output. I didn't see anything useful in here, but just in case."
1763175,2018-04-11 21:02:52 UTC,Scratch that about juju debug-log being useless. The output of `resource-get` is in there:
1763175,2018-04-11 21:05:12 UTC,"Attached controller logs. The 'failed to track progress: setting the resource failed' and 'failed to track progress: resource ""test0"" not found' around 19:12:41 look interesting."
1763175,2018-04-11 21:07:18 UTC,"$ juju version
2.3.5-xenial-amd64"
1763175,2018-04-11 21:14:34 UTC,"Attached tarball with the charm, bundle, and script I used to repro. The script deploys from the charm store however. I have only been able to reproduce this by deploying a bundle pointing to the charm store, but given how rare this behavior is, I can't rule anything out."
1763181,2018-10-06 17:18:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/608417"
1763181,2019-04-04 10:21:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649963"
1763181,2019-10-23 13:03:11 UTC,"Reviewed:  https://review.opendev.org/686402
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c072993e0953e9bd45ce4265414b8cbefe1ca7a1
Submitter: Zuul
Branch:    stable/rocky"
1763181,2018-10-04 16:13:28 UTC,"Reviewed:  https://review.openstack.org/607620
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=14a3b1318cf84983e1c029ffa1d3a7b2d0223779
Submitter: Zuul
Branch:    master"
1763181,2019-10-03 13:33:21 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/686402"
1763181,2018-10-03 15:43:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/607620"
1763181,2018-04-12 21:44:49 UTC,"My suspicion is that when we call _validate_instance_group_policy() which calls group.get_hosts(), that we will only return the original hosts where they're evacuating *from*, not the host they're both evacuating *to*, because we don't set instance.host to the new host until the evacuation is basically done."
1763181,2018-09-26 14:24:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605436"
1763181,2018-09-26 12:13:18 UTC,"There's definitely an obvious race here which I think Chris is describing in comment 1? I'm going to describe it again in my own words, just to be sure:"
1763181,2018-04-12 23:17:07 UTC,I think for the evacuate case (as well as migration/resize and live-migration) we'd want to do something like:
1763181,2018-09-26 17:22:00 UTC,"The rationale for the check against ""older"" instances is to try to avoid the case where two anti-affinity instances land on the same node, they *both* detect problems, and they *both* reschedule, potentially landing on the same node again.  Ideally we want only one of them to reschedule and the other to continue."
1763183,2018-05-21 20:23:52 UTC,"Reviewed:  https://review.openstack.org/563234
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a817b78dc44cf2cb4157531b2d92b03a4d0ca7d1
Submitter: Zuul
Branch:    stable/queens"
1763183,2018-09-24 14:46:54 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1763183,2018-07-09 16:11:17 UTC,"Reviewed:  https://review.openstack.org/580496
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8cd1204873287d9f0196cbc48d8c408448c67c43
Submitter: Zuul
Branch:    stable/pike"
1763183,2018-07-09 12:29:27 UTC,"Reviewed:  https://review.openstack.org/580491
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8dd4c6195434a1e271ad8cd7fbd66d4801a4cba
Submitter: Zuul
Branch:    stable/pike"
1763183,2018-07-05 20:26:10 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580496"
1763183,2018-06-04 13:52:35 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1763183,2018-05-20 18:35:10 UTC,"Reviewed:  https://review.openstack.org/563229
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bcd462e49b4d51e78e9f31c60cd9e4d9fd8f99f9
Submitter: Zuul
Branch:    stable/queens"
1763183,2018-04-11 22:27:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/560674"
1763183,2018-04-20 18:51:34 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/563229"
1763183,2018-04-20 13:12:22 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1763183,2018-04-20 05:55:47 UTC,"Reviewed:  https://review.openstack.org/560674
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=42f62f1ed2ad76829eb9d40a8b9646a523f6381f
Submitter: Zuul
Branch:    master"
1763183,2018-04-20 05:47:04 UTC,"Reviewed:  https://review.openstack.org/560626
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a80ac96362c8fafba1bfe71244b52ba2f082c86e
Submitter: Zuul
Branch:    master"
1763183,2018-04-20 18:57:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/563234"
1763186,2018-04-13 21:42:44 UTC,"And that's the correct behavior. You have chosen not to install recommends for this package, so reinstalling the package should not pull them in now, aka forget your choice. Eventually there might be a new command to do stuff like this, but we have not come up with a name yet."
1763191,2020-05-10 09:42:38 UTC,"I think this was fixed in Mixxx 2.2.
Please reopen the bug if this is not the case."
1763191,2018-05-01 14:08:28 UTC,"The problem is that I do not know which device is using ASIO. If I
uninstall one by one I'll know. But I do not want to uninstall anything!
Why do not they strengthen Mixx to get in the way when it's installed?"
1763191,2018-04-30 15:02:51 UTC,"Do you have an idea which other program is using you ASIO device?
Is it possible to use the ""Windows WDM-KS"" or ""Direct Sound"""
1763191,2018-04-22 01:20:34 UTC,Greetings! I am using Mixxx 2.1.0 for 64-bit Windows but I just uninstalled and installed again. The same problem appeared! Notice that the audio output is not configured and that FL ASIO is being used by another program. As well? What does it means? thankful
1763191,2018-04-15 23:16:53 UTC,did you forget to answer my questions or is the bug solved on you side?
1763191,2018-04-12 15:27:16 UTC,"Very well! Appreciate! Congratulations on the speedy response! I like Mixxx
more and more!"
1763191,2018-04-11 22:18:13 UTC,Which version of Mixxx and on which OS are you? Which audio API and sound card did you choose?
1763191,2018-04-16 00:23:35 UTC,"I did not forget your questions and I did not solve the mistake. I could
not find the time to look at this yet. But I'll look as fast as I can!
Thankful!"
1763198,2018-04-23 17:08:46 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1763198,2018-04-11 23:05:56 UTC,Reported upstream: https://github.com/robint99/mate-dock-applet/issues/130
1763198,2018-04-23 13:43:19 UTC,"I noticed that this will occur with minimized apps open too, so step (3) is more like ""close or minimize all other windows""."
1763198,2018-05-21 01:26:57 UTC,Fixed upstream (I haven't tested it).
1763199,2018-09-07 16:13:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763200,2018-04-12 10:59:24 UTC,See also: https://bugs.launchpad.net/kicad/+bug/1750374.
1763201,2018-04-12 12:01:55 UTC,"Update:
when we run make install-dependencies before the installation, snap installation of golang 1.10 version gets updated.
Refer: github.com/juju/ju/Makefile"
1763201,2018-04-11 23:25:02 UTC,Thank you for report! It is paramount for us to have an up-to-date documentation \o/
1763206,2018-06-14 03:56:24 UTC,"As you are using gnome shell, are you on Ubuntu 18.04? Because indicator-keylock has been removed from 18.04 and unsupported."
1763209,2018-11-28 15:49:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763209,2018-11-28 15:53:49 UTC,I am having the same issue on a Dell XPS 13 L322X.
1763209,2019-02-18 22:54:24 UTC,"I had the same issue after migrating from Kubuntu 14.04 to Kubuntu 18.04 on a XPS L321X.
Installing xserver-xorg-input-synaptics fixed it for me."
1763209,2019-09-10 15:58:26 UTC,"I'm also having this issue, on a Lenovo Thinkpad T450S."
1763221,2018-04-12 00:22:51 UTC,"The attachment ""/usr/lib/python3/dist-packages/blueman/plugins/applet/PowerManager.py.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1763221,2018-04-14 12:14:47 UTC,"I just finished a better patch and sent it upstream
https://github.com/blueman-project/blueman/issues/859"
1763221,2019-08-24 20:05:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763228,2018-04-12 01:19:11 UTC,Linux Doko 4.14.0-kali3-amd64 #1 SMP Debian 4.14.17-1kali1 (2018-02-16) x86_64 GNU/Linux
1763231,2018-04-12 09:00:00 UTC,Don't mind. I will change my mapping and use the button press to change the focus like in the DJ-202 mapping. Instead the BACK/FWD buttons can be mapped to MoveLeft/MoveRight.
1763231,2018-04-12 08:55:07 UTC,"[Library] MoveRight expands the sidebar item, but the next press simply scrolls right inside the sidebar pane instead of collapsing the item. Unusable, too."
1763231,2018-04-12 08:52:15 UTC,"The proposed control simply switches the focus from the sidebar to the table. I have separate buttons for switching focus, this is not what I need here."
1763231,2018-04-12 08:48:28 UTC,No. I don't want to load the selected track into the first available deck. The controller has dedicated buttons for loading tracks.
1763231,2018-04-12 08:22:22 UTC,"Ah, I got the issue:
We have now ""[Library] GoToItem"" as the replacement."
1763231,2018-04-12 07:43:43 UTC,enable -> expand
1763231,2018-04-12 07:43:21 UTC,"The use case is exactly as documented in the Wiki, i.e. toggeling the expansion state (expanded/collapsed) of the selected sidebar item."
1763231,2018-04-12 06:41:57 UTC,"ToggleSelectedSidebarItem is not deprecated yet. The issue is that it is in the old namespace, and it can be candidate for deprecation though."
1763231,2018-04-12 09:16:27 UTC,But this is still a valid issue if we declare [Playlist] ToggleSelectedSidebarItem as deprecated with no appropriate replacement.
1763231,2018-04-12 12:57:19 UTC,The idea behind an alternative to [Playlist] ToggleSelectedSidebarItem was that it is not usefull in all library panes.
1763232,2018-04-12 02:04:30 UTC,"Small edit: millisecond setting in the above step-by-step should be 1,000, not 10,000."
1763273,2018-05-23 04:01:37 UTC,"After several weekends of testing, I believe I can report with high confidence that the kernel update to 4.17-rc2 fixes the second of the two problems; specifically, we no longer see kernel crashes after using Alt-SysRq-k to recover from frozen/hanging blank screens."
1763273,2018-04-26 08:09:24 UTC,"Yes, I can test those this weekend ... if you have any specific advice on updating the kernel, let me know, otherwise I'll use the notes here:"
1763273,2018-04-24 05:04:18 UTC,Can you try latest mainline kernel in [0]?
1763273,2018-04-24 04:36:01 UTC,"Hit another kernel panic this weekend, again after having the screen go blank and be unblankable via any normal method, then trying Alt-SysRq-k and getting this panic (with a different stacktrace than the other, but also going through the radeon driver and radeon_crtc_handle_flip)."
1763273,2018-04-23 18:33:55 UTC,"I think I've filled in all the necessary info -- and I have another screenshot to upload too, once I get it off my phone, from another kernel panic in the same context."
1763273,2018-04-16 20:58:36 UTC,One further historical detail: when these machines were running 14.04.3 and we made the mistake of accepting the HardWare Enablement (HWE) upgrade:
1763273,2018-04-16 07:10:08 UTC,"OK ... I think that's all I can do for today.  I've uploaded as attachments to this original report all the files generated by apport-bug today, and marked the other ticket as a duplicate."
1763273,2018-04-12 07:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1763273,2018-04-16 06:41:27 UTC,"Here are the details from apport-bug, as promised (copied from #1764211 because I had to use a different Launchpad account):"
1763273,2018-04-16 03:31:23 UTC,"While logged in via ssh to the machine with the ""hung"" Xorg (screen blank, no way to recover except Alt-SysRq-k), I dumped the output of Alt-SysRq-t into the syslog -- see attached file.  Not sure this is much use, however.  Just trying to be complete while I'm on-site with a hung machine."
1763273,2018-04-16 03:16:06 UTC,"Further debugging today while I'm on-site with the kiosks.  The system froze, as usual, after normal idle screen blanking.  I was able to login via ssh and retrieve some details."
1763273,2018-04-16 01:43:51 UTC,"Further details from apport-bug are in #1764211; I'll copy them into this account using my ""cdarroch"" personal Launchpad account in a few hours, when I get home."
1763273,2018-04-13 20:24:23 UTC,"I'm only on-site with these kiosks once a week, but the next time I'm there I will run apport-collect on one of the affected systems, and see if we can't capture the problem.  I'll also investigate whether there are any messages in kernel log files, as best I can."
1763273,2018-04-16 06:59:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763289,2018-04-12 07:55:22 UTC,"I discussed this with John Lenton at the Budapest sprint, but I forgot to open a bug it seems."
1763289,2018-09-21 09:17:23 UTC,What specific operation would you be interested in differentiating?
1763289,2018-09-24 04:31:38 UTC,"Operations that are useful to differentiate:
- (install/remove) Abort (i.e. calling /v2/changes/[id] with ""action"": ""abort"")
- (install) Download failure (e.g. no network connection)
- (install) Insufficient disk space
- (install/remove) I/O failures (e.g. hard disk failures)"
1763296,2018-04-23 14:00:39 UTC,The package has been published and the bug is being set to Fix Released
1763296,2018-04-20 05:47:06 UTC,linux-oem: 4.13.0-1024.27
1763296,2018-04-12 08:16:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763296,2018-04-17 10:53:07 UTC,We use test results from Cert.
1763296,2018-04-23 12:52:04 UTC,This bug was fixed in the package linux-oem - 4.13.0-1024.27
1763319,2018-04-12 10:40:30 UTC,"While fixing this would be pretty low-risk, nothing is zero-risk and Print has worked this way for a long time.  Therefore pushing to 6.0."
1763319,2018-07-22 22:35:03 UTC,"Fixed in revision 2a9856ba340af47b9ad5a43bd512297aea4f3d87
https://git.launchpad.net/kicad/patch/?id=2a9856ba340af47b9ad5a43bd512297aea4f3d87"
1763321,2018-05-09 16:22:22 UTC,"Reviewed:  https://review.openstack.org/566234
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=668a28986270dfd30546c7c1d52947e15b66049a
Submitter: Zuul
Branch:    master"
1763321,2018-10-10 11:22:12 UTC,"Moving to triaged as the fix was done only for events (event_pipeline.yaml), not metrics (pipeline.yaml)."
1763323,2019-06-10 04:33:22 UTC,"This test has passed with Azure kernels (example output for 4.18.0-1019.19~18.04.1 Azure):
ubuntu_fan:0051|
ubuntu_fan:0051| Testing Fan Networking (pre-0.13.0 API)
ubuntu_fan:0051| docker pull ubuntu: PASSED
ubuntu_fan:0051| enable disable fan test: PASSED
ubuntu_fan:0051| fanctl show test: PASSED
ubuntu_fan:0051| fanctl check bridge config test: PASSED
ubuntu_fan:0051| fanatic docker test(--dns=168.63.129.16): PASSED"
1763323,2019-06-10 04:28:05 UTC,"For comment #6, CONFIG_NET_IPIP has been enabled for all KVM kernels:
$ grep -e IPIP ubuntu-kvm-*/debian.kvm/config/config.common.ubuntu
ubuntu-kvm-bionic/debian.kvm/config/config.common.ubuntu:CONFIG_NET_IPIP=y
ubuntu-kvm-cosmic/debian.kvm/config/config.common.ubuntu:CONFIG_NET_IPIP=y
ubuntu-kvm-disco/debian.kvm/config/config.common.ubuntu:CONFIG_NET_IPIP=y
ubuntu-kvm-xenial/debian.kvm/config/config.common.ubuntu:CONFIG_NET_IPIP=y"
1763323,2019-05-30 09:18:16 UTC,Test disabled in ACT for KVM kernels https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=be027ae34aa565fb640697b56d862fb087a0ad0b
1763323,2018-09-21 13:21:57 UTC,"Discussed with smb and jvosburgh, this issue is similar to bug 1570565, some configs are missing for the KVM kernel."
1763323,2018-11-07 11:19:46 UTC,Spotted on Cosmic KVM as well.
1763323,2018-09-12 19:04:31 UTC,"Hi Sam, is this still an issue?
+60 day bug with no action on it, marking bug as incomplete and will
close in 5 days if no update."
1763323,2018-05-10 06:11:53 UTC,Can be found on 4.15 kvm as well.
1763323,2018-04-12 10:32:46 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1763323,2018-09-13 04:15:54 UTC,Still failing for the latest KVM kernel - 4.15.0-1021.21-kvm
1763328,2018-04-12 10:46:40 UTC,"It may be a buffering issue, as far as where the WARNING happens (if it happens on stderr, which isn't buffered, while stdout is buffered)."
1763328,2019-09-09 09:04:54 UTC,"Whatever was the cause of this failure, it looks like it has been addressed - I cannot reproduce this locally under stress after a lot of runs."
1763331,2019-07-22 07:03:49 UTC,Since the report was filed we have done great improvements in watchers area and have not seen re-occurrence of this failure. I am marking this as Fix Released.
1763335,2018-04-13 09:44:57 UTC,Actually there's a bit more work to support Python 3 than just fixing the imports.
1763346,2018-04-12 14:02:14 UTC,There is alno no image when i Click COmpute then Image. Also there is no prompt when I click launch instance. Help please. This is after pulling horizon image of queens
1763354,2020-02-10 11:41:00 UTC,Artful is EOL for long time.
1763354,2018-04-13 15:03:41 UTC,Regression test results on Bionic/18.04:
1763354,2018-04-16 12:50:59 UTC,This bug was fixed in the package xen - 4.9.2-0ubuntu1
1763359,2020-04-12 15:00:45 UTC,"Hi, the original issue can be replicated in Inkscape 0.92.4, but not in 1.1-dev anymore (1.1-dev (c990a67, 2020-04-09), Windows 10). The second issue has been reported to Gitlab: https://gitlab.com/inkscape/inbox/-/issues/2298"
1763359,2018-11-27 01:53:19 UTC,"Both for master and 0.92.x, also on Linux."
1763359,2018-11-27 01:52:39 UTC,"If you do this with a screenshot on the clipboard, it will add a miniature screenshot to the canvas. This is for the pencil tool, or when you finish a Bézier line by pressing Enter."
1763371,2018-04-12 13:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1763371,2018-04-12 19:59:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1763371,2018-04-13 12:37:59 UTC,doesn't work on v4.16
1763377,2018-06-16 20:42:58 UTC,"This also applies to the official release, 8.1.2."
1763381,2018-04-12 13:59:23 UTC,It seems to be a different case. Possibly related to the i3 window manager.
1763384,2018-04-18 17:42:26 UTC,According to Matthew Wilcox this is probably a won't fix bug with a recommendation to the Ubuntu developers to disable or remove support for this orphaned kernel module:
1763384,2018-04-13 11:55:39 UTC,Thanks for taking the time to report this bug and helping to make Ubuntu better.
1763384,2018-04-13 15:32:40 UTC,Reported to <email address hidden>
1763384,2018-06-29 18:22:45 UTC,This issue has received the following identifier: CVE-2018-12928
1763394,2018-11-20 20:15:21 UTC,"I got the same error message and was quite confused. Fortunately Kyle helped me out - my issue was that the travis setup script did not copy all the bits from the source into the snapcraft chroot and I got this error. Having a hint lile ""unable to find or determine source type of ""/path/to/my/code""  would be cool."
1763397,2020-02-26 22:35:24 UTC,Marking as Won't Fix for 2.3 series since we are not planning to make any further releases in this series at this stage.
1763399,2020-02-04 16:08:08 UTC,"This was ultimately fixed in
https://review.opendev.org/#/c/627941/"
1763399,2018-06-25 05:29:09 UTC,Will there be any fix for this ?
1763399,2018-06-25 13:54:30 UTC,"Yes, I have a fix I will submit shortly for this issue."
1763399,2018-07-05 13:17:56 UTC,This is probably a dupe of https://bugs.launchpad.net/cinder/+bug/1578036 where I have submitted a patch.
1763399,2020-02-04 15:44:39 UTC,Can we close this then?
1763403,2018-05-01 00:06:07 UTC,"Hello Sergej, do you know if discussion of this issue has been made public?"
1763403,2018-04-13 15:32:18 UTC,Reported to <email address hidden>.
1763403,2018-05-01 20:06:27 UTC,"Yes, the discussion can be found here: https://marc.info/?l=linux-ntfs-dev&m=152413769810234&w=2"
1763403,2018-06-29 18:21:43 UTC,"These issues have received the following identifiers:
CVE-2018-12929 for the issue in ntfs_read_locked_inode
CVE-2018-12930 for the issue in ntfs_end_buffer_async_read
CVE-2018-12931 for the issue in ntfs_attr_find"
1763403,2018-04-13 11:55:20 UTC,Thanks for taking the time to report this bug and helping to make Ubuntu better.
1763403,2018-05-01 20:26:10 UTC,"Excellent, thanks Sergej."
1763405,2018-05-02 13:53:34 UTC,Isn't docker running inside fedora atomic containers currently configured to use systemd driver by default?
1763405,2018-05-02 13:40:57 UTC,"using cgroupfs instead of systemd driver solved this issue, would like to add a label to be able to select the cgroup driver?"
1763405,2018-04-17 11:07:48 UTC,"Change abandoned by Bharat Kunwar (<email address hidden>) on branch: master
Review: https://review.openstack.org/561605"
1763405,2018-04-17 11:08:56 UTC,"Change abandoned by Bharat Kunwar (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/560952"
1763405,2018-04-16 12:42:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561605"
1763405,2018-04-17 11:02:20 UTC,FYI https://bugzilla.redhat.com/show_bug.cgi?id=1558425
1763405,2018-04-12 15:51:29 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/560952"
1763408,2018-09-14 16:35:56 UTC,"Latest version is working again, showing the main window."
1763410,2020-03-25 11:50:56 UTC,"Zero hits, I can't recall how this was resolved but we are not seeing it anymore."
1763410,2020-05-25 04:17:19 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1763417,2018-04-18 02:17:17 UTC,I'm seeing the same bug with red headerbar buttons in other apps. I think colorhug-client was where I saw it last.
1763417,2018-04-18 02:17:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763429,2018-10-02 16:15:26 UTC,I had this same problem as described by #11. I found that changing the display driver to proprietary nvidia driver helped. The nouveau driver was the issue.
1763429,2018-09-01 19:03:59 UTC,Confirmed on Yoga 730-15 with current mainline kernel 4.18.5-041805-generic_4.18.5-041805.201808241320_amd64 on Ubuntu 18.04 (but also happend with stock 18.04 kernel).
1763429,2018-05-08 05:49:28 UTC,Can you try latest firmware in [1]?
1763429,2018-05-02 13:51:24 UTC, tag kernel-bug-exists-upstream
1763429,2018-05-02 13:04:44 UTC,"Unfortunately the new Ubuntu kernel did not fix the issue, it only worked fine during some reboots. I now tried mainline v4.16.6 and v4.17-rc3, both did not fix the issue neither."
1763429,2018-07-08 04:17:20 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1763429,2018-04-12 19:56:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1763429,2018-04-12 16:00:06 UTC,This change was made by a bot.
1763429,2018-04-12 15:39:23 UTC,"Adding reboot=bios, reboot=pci, reboot=cold, reboot=warm, reboot=efi, acpi=force to the kernel parameters list did not help."
1763429,2018-04-23 08:58:48 UTC,"The system was only recently installed, so there was no other version of the kernel before on this system. However, last week I could get my hands on this system again and update/upgrade installed a new kernel which fixed the problem, I did not have the possibility yet to check whether it now also reboots without ""reboot=cold""."
1763433,2018-04-12 16:00:19 UTC,"As a result,"
1763433,2021-02-17 17:07:25 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1763434,2019-11-14 01:36:20 UTC,"I suspect this is fixed now. Please reopen if not, thanks!"
1763442,2018-09-06 04:19:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763456,2018-06-11 17:16:02 UTC,This bug was fixed in the package linux-azure - 4.15.0-1013.13~16.04.2
1763456,2018-04-12 16:58:30 UTC,Subscribed Canonical Kernel Distro Team to this bug.
1763456,2018-04-20 22:06:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1763456,2018-04-24 12:46:52 UTC,This bug was fixed in the package linux-azure - 4.15.0-1008.8
1763459,2018-05-04 06:26:25 UTC,"We don't intend to save metrics history inside a Juju controller, but we could provide mechanisms for you to scrape and/or register a place for us to publish them."
1763459,2018-04-18 16:35:16 UTC,"Hi John,"
1763459,2018-04-16 03:44:32 UTC,"I don't think we guarantee to store a long history of metrics. I believe we
store the current value and any values that haven't been forwarded yet. It
might be better to implement some sort of ""push"" support. So when we get
metrics we forward them. Internally I'm not sure we could trivially support
multiple forwarding targets."
1763471,2018-04-13 14:41:42 UTC,"I added the Swedish translation of ""Software &amp; Updates"" to software-properties.mo manually."
1763471,2018-04-13 16:14:27 UTC,This gets a bit complicated.
1763471,2018-04-13 16:30:51 UTC,"Hmm, the summary field for /usr/share/metainfo/software-properties-gtk.appdata.xml is translated into Swedish (and shows up in GNOME Software that way; you might need to restart GNOME Software for changes to be recognized). It's already translated because I reused the string from the .desktop for it and there are .po files in the package (but they are ancient!)."
1763471,2018-04-15 01:06:19 UTC,"So the info in the appdata file is passed to DEP-11, Ubuntu Software fetches already localized strings from the latter, and there is a time factor. Did I get that (approximately) right?"
1763474,2018-04-12 18:27:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561003"
1763474,2018-04-12 18:38:55 UTC,"We hit this in tripleo, more info in the OPNFV jira:
https://jira.opnfv.org/browse/APEX-588"
1763485,2018-12-03 22:41:10 UTC,"If this is still an issue, it should be against cpe-foundation"
1763510,2018-04-12 22:02:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561061"
1763510,2018-04-12 21:15:37 UTC,"Note that a fix for this is going to be backwards incompatible, even though the patch the introduced the issue technically was backwards incompatible."
1763510,2018-04-16 20:28:34 UTC,"Reviewed:  https://review.openstack.org/407587
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=96a883a5ad37a922218b6d33eec7baa206622620
Submitter: Zuul
Branch:    master"
1763520,2019-04-12 10:20:11 UTC,This bug was fixed in the package gtk+3.0 - 3.24.8-1ubuntu1
1763520,2019-04-11 12:28:19 UTC,Uploaded as https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.8-1ubuntu1
1763520,2019-04-11 10:18:36 UTC,"Thanks, but there's no need. We'll get it via 3.24.8 which I'm uploading now."
1763520,2019-04-09 14:36:31 UTC,Here is an updated debdiff for gtk+3.0 in Ubuntu Disco. It is based on the current gtk_3.0 package of Disco with the patch of
1763520,2019-07-22 08:56:07 UTC,This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu4
1763520,2019-04-04 16:46:19 UTC,The patch got merged upstream.
1763520,2019-03-28 18:08:19 UTC,As soon as the patch is incorporated upstream I will post the resulting patch here.
1763520,2019-04-23 08:27:56 UTC,"Till, can you provide updated debdiffs and re-subscribe ubuntu-sponsors / ping someone on the desktop team when there's something to upload please?"
1763520,2019-04-05 18:01:04 UTC,The patch got also merged into the 3.24 branch of GTK:
1763520,2019-06-05 13:33:02 UTC,"Closing Cosmic task as Cosmic goes EOL in a month from now and Disco is available. In addition, the problem only occurs when updating from an older Ubuntu release. So it is recommended to generally update to Disco instead of to Cosmic and in case one updated to Cosmic getting this problem to update again to Disco."
1763520,2019-07-22 08:56:15 UTC,"The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1763520,2019-07-11 08:30:03 UTC,I've sponsored the uploaded to Bionic now
1763520,2019-07-11 10:45:38 UTC,"Hello Steve, or anyone else affected,"
1763520,2019-07-11 12:29:32 UTC,"All autopkgtests for the newly accepted gtk+3.0 (3.22.30-1ubuntu4) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1763520,2019-07-16 21:02:49 UTC,"Lukasz, I do not see any problems with this package, neither on the"
1763520,2019-03-28 18:06:13 UTC,Updated the proposed patch for upstream according to their requirements.
1763520,2019-07-17 16:05:50 UTC,"seb128 retried apport/i386 and libreoffice/ppc64el, blaming ""infrastructure issue[s]"" (I don't see evidence of that; it seems like slightly flaky tests to me). They passed on the retry, and so I think you are OK for testing now."
1763520,2019-07-18 16:54:02 UTC,"I am experiencing this same problem in Linux Mint 19.1. After creating a print job, there is no response from the printer (it doesn't wake up or anything), there is no printing, but the only message in the error log is ""CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'MaisonLaser-Gray..\' already exists"""
1763520,2019-07-18 17:49:15 UTC,"Jason, the message you mention has nothing to do with the bug reported here, it is from the color management daemon and in no case prevents a job from printing. The bug reported here is about a problem of the GTK/GNOME print dialog not handling printer driver updates correctly. It only happens when a printer driver gets updated (can happen during a general system update or an upgrade to a new Ubuntu version). We need your error_log (in debug mode, see ""CUPS error_log"" on https://wiki.ubuntu.com/DebuggingPrintingProblems) to judge whether you are suffering this bug or something else."
1763520,2019-07-18 18:39:19 UTC,I have checked the gtk+3.0 SRU in bionic-proposed now and could reproduce the bug before updating and encountered correct behavior after the update. So I am marking this SRU as verified.
1763520,2019-06-05 13:51:01 UTC,"Debdiff for Bionic SRU, using the patch from upstream."
1763520,2018-12-07 21:23:43 UTC,I have now added debdiffs for disco and for the SRUs. Please can someone with appropriate rights upload them? Thanks.
1763520,2018-07-03 19:30:13 UTC,debug error log attached.  I believe the failed print job starts at 03/Jul/2018:12:22:01.
1763520,2018-12-07 21:21:01 UTC,debdiff for cosmic.
1763520,2018-04-12 22:14:10 UTC,"The particular printer instance showing this failure is one that I've set up specifically in the course of trying to debug this (hence, '-new' in the queue name), but the problem exists also with my previously-existing queue."
1763520,2018-05-04 19:41:51 UTC,Have you checked
1763520,2018-05-04 19:47:32 UTC,Please run the command
1763520,2018-12-07 21:22:17 UTC,debdiff for bionic.
1763520,2018-07-10 14:28:00 UTC,It seems that evince has supplied a wrong name for the paper size. See these two lines in the error_log:
1763520,2018-07-10 14:30:38 UTC,Turned cups task into cups-filters as one could improve the filters by putting an error message into error_log if the page size name is not correct.
1763520,2018-07-10 14:34:53 UTC,"Steve, which page size did you select when printing from evince?"
1763520,2018-07-23 04:43:16 UTC,"> Steve, which page size did you select when printing from evince?
"
1763520,2018-08-20 20:37:06 UTC,I see as the only problem here that jobs are submitted with PageSize=Custom.Letter.SM (and not PageSize=Letter.SM). This is most probably a problem of the GTK print dialog.
1763520,2018-05-04 19:52:32 UTC,Please also attach your file /etc/cups/cupsd.conf.
1763520,2018-08-22 01:00:25 UTC,"BTW when I say it was named 'something like [...]', after I changed the paper size to US Letter and confirmed that printing now worked, I went back into the dialog and the original paper size name had disappeared."
1763520,2018-08-22 07:36:15 UTC,"Then the bug is that the GTK print dialog in the case that the page size saved from the last session is an invalid one, prefixes it with ""Custom."", which is completely wrong. What it should do is removing the saved wrong size and return to the printer's system default size."
1763520,2018-09-03 18:36:22 UTC,The attached patch fixes the bug.
1763520,2018-11-28 14:50:40 UTC,"@Till, did you try to upstream that patch?"
1763520,2018-11-28 22:50:03 UTC,"No, not yet."
1763520,2018-11-29 09:39:55 UTC,"@Till, k, can you add that to your todolist then?"
1763520,2018-11-29 11:59:18 UTC,Done. Pull request posted: https://gitlab.gnome.org/GNOME/gtk/merge_requests/434
1763520,2018-11-29 13:32:00 UTC,Thanks!
1763520,2018-12-07 21:19:56 UTC,debdiff for disco.
1763520,2018-08-22 00:52:41 UTC,"I went into evince's printer settings, and found that under 'Page Setup', the 'Paper size' had been set to something named 'Letter small borders' or similar.  So it looks like the severity of the bug could reasonably reduced since at some point in the past there WAS a user non-default configuration that triggered this error, and it's not reproducible by default on bionic if you're just using US Letter as your paper size.  Nevertheless it still means that after upgrade, a gtk printer config that was valid ceases to be valid with no obvious explanation why."
1763525,2018-04-17 13:58:38 UTC,stap 3.2 includes this fix:
1763525,2020-03-23 17:15:08 UTC,The stap script works fine on focal (systemtap 5.2 and Linux 5.4.0).
1763533,2018-06-01 12:28:18 UTC,What is the error code the call is failing with?
1763533,2018-04-20 22:57:52 UTC,"On further triage the issue seems to be related to the following line in the continerd log:
time=""2018-04-18T11:27:35.765002258-06:00"" level=fatal msg=""containerd: epoll wait"" error=""Failed to wait epoll"""
1763533,2018-04-18 17:42:21 UTC,"root@linaro-erp-os-control:~# docker-containerd -v
containerd version 0.2.3 commit: 6e23458c129b551d5c9871e5174f6b1b7f6d1170"
1763533,2018-04-18 17:41:38 UTC,Attached dockerd logs.
1763533,2018-09-26 14:01:27 UTC,Some version of this is also affecting me on aarch64 on 4.14.0-49.10.1 Centos
1763533,2018-04-18 06:31:02 UTC,"the grpc error should be raised by docker daemon.
This is wired, sound like docker daemon cannot handle the request. I haven't seen the similar issue."
1763533,2018-04-18 05:47:00 UTC,Linaro ERP 17.12 == Debian 'stretch' + 4.14 kernel
1763533,2018-04-18 15:33:16 UTC,I do not see the error if I put in the 1s sleep. The sleep only makes sure that there is a 1s delay after every successful execution of a command in kolla_toolbox. As I said in the bug report this does seem to be an error with something in the docker framework not being ready.
1763533,2018-10-09 14:54:40 UTC,This did it for me: https://github.com/projectatomic/containerd/pull/7
1763534,2018-04-14 00:51:49 UTC,"Note: if you are using a Xenial based MAAS that has not been patched to use `ip` instead, and you use it to commission on Bionic, it will fail due to this issue."
1763534,2018-04-13 00:13:43 UTC,"net-tools is deprecated in favor of iproute2, and is only included in the server seed in 18.04 because there wasn't time in the 18.04 cycle to verify the effects of its removal.  What depends on the behavior of 'ifconfig -s' (which I've never once in 20 years of Linux seen before) that makes this 'critical'?"
1763534,2018-04-13 01:37:58 UTC,"Maas is being fixed to use “ip” instead of ifconfig. The reason why it
wasn’t noticed before is because MAAS does only use LTS releases for
commissioning. Since we only run ifconfig -a during commissioning, then the
regression wasn’t found till recently."
1763534,2018-04-16 21:16:27 UTC,"On Sat, Apr 14, 2018 at 12:51:49AM -0000, Mike Pontillo wrote:

> Note: if you are using a Xenial based MAAS that has not been patched to
> use `ip` instead, and you use it to commission on Bionic, it will fail
> due to this issue.
"
1763534,2018-04-13 01:03:14 UTC,"OTOH, it's also been this way since zesty and no one else seems to have cared until now that it regressed.  I think the effort is better spent fixing maas to not depend on deprecated tools."
1763534,2018-04-12 23:40:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763534,2018-04-13 00:51:24 UTC,Ok; that seems like something that should be fixed in maas by making it not parse the output of deprecated tools with buggy interfaces?
1763534,2018-04-13 00:28:50 UTC,Because this bug causes the following to happen: https://bugs.launchpad.net/maas/+bug/1759284
1763534,2018-04-13 00:53:31 UTC,"That said, this does appear to be a change in behavior between net-tools 1.60 in xenial and net-tools 1.60+git20161116.90da8a0 in bionic."
1763536,2021-01-10 04:17:36 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1763536,2020-11-10 16:04:39 UTC,Have you ever tried with a newer version of QEMU?
1763536,2019-08-02 17:35:03 UTC,"We recently fixed bug #1696773 which was a cause of various crashes or other problems when trying to run go binaries under linux-user, including ""go build hello.go"". So I strongly suspect this is a duplicate of that bug. Could you test with the QEMU v4.1.0 rc3 or later, please?"
1763536,2018-04-25 15:55:42 UTC,"Thanks for the update,  I will test that version and report back ( it may be a few days)"
1763536,2018-04-24 19:59:56 UTC,"With QEMU from tag v2.12.0-rc4 on Fedora 27 x86_64, it works too."
1763536,2018-04-23 22:04:28 UTC,"Using QEMU from tag v2.12.0-rc4 on Ubuntu Xenial ppc64el, it works."
1763536,2018-04-17 21:02:50 UTC,I will attempt to find an way to re-create without docker.  The key is we need a way to create a ppc64le (or arm64) fakeroot with go that we can chroot into.  That is easy to do with docker.  BTW: the use case using docker and qemu-user-static is becoming fairly common way to cross build container images.
1763536,2018-04-17 17:54:14 UTC,Do you have a simpler repro case (ie one that doesn't require docker) ?
1763536,2018-04-13 19:22:00 UTC,FYI: To workaround this issue you can limit the docker container to a single cpu like this:
1763536,2018-04-13 19:13:11 UTC,"I missed a step for reproduction.  Step 1 should be:
docker run --rm --privileged multiarch/qemu-user-static:register
This modprobes binfmt and registers qemu-ppc64le-static as the interpreter for ppc64le executables."
1763536,2018-04-17 21:16:36 UTC,"I care more about the arm64 case, so if you're going to do one then that would be my preference."
1763537,2018-04-13 01:28:27 UTC,Yes it's probably possible. Although unusual to want a statically linked PulseAudio.
1763555,2018-09-11 22:35:02 UTC,"Reviewed:  https://review.openstack.org/594356
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=aeca374328ae96d4641b6c11bd65ce9e1a16abcc
Submitter: Zuul
Branch:    stable/queens"
1763555,2020-09-26 10:10:10 UTC,"From the comments it seems the problem here from tempest side was not deleted cache before volume type deletion process. The following bug addressed this issue, the fix is included in tempest 21 tag and higher:
https://bugs.launchpad.net/tempest/+bug/1823880"
1763555,2020-06-17 09:04:23 UTC,Has been the issue seen since the cinder fixes got merged? As it's been more than a year since last update we need to evaluate if the bug is still relevant - the tempest codebase got changed much over the year plus the fixes landed in cinder ...
1763555,2018-10-09 19:53:38 UTC,This issue was fixed in the openstack/cinder 12.0.4 release.
1763555,2018-08-21 16:14:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/594356"
1763555,2018-04-24 08:36:41 UTC,Adding tempest as affected project:
1763555,2018-05-02 13:02:45 UTC,"Reviewed:  https://review.openstack.org/561622
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=6e9cbd1e4b5aa7208ab929e14047ab94ba801056
Submitter: Zuul
Branch:    master"
1763555,2018-04-16 13:50:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561622"
1763555,2018-06-08 20:42:32 UTC,This issue was fixed in the openstack/cinder 13.0.0.0b2 development milestone.
1763558,2018-04-17 07:08:31 UTC,"Please note that vmbuilder is community only support.
On Ubuntu's side uvtool and if an install experience is required virt-inst is more recommended."
1763558,2018-05-02 09:25:18 UTC,The issue has been resolved.
1763564,2020-07-01 20:46:39 UTC,"Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1763564,2020-07-01 20:47:02 UTC,"you reported the issue against the pdf viewer, does the problem has to do with this software?"
1763564,2020-08-31 04:17:23 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1763567,2018-06-06 15:06:12 UTC,"hi, Andy, good catch. It will be great if you have time do some work around this."
1763570,2018-04-13 18:31:22 UTC,Tagging as a regression - the expected results in the description were obtained on xenial.
1763578,2018-05-10 17:33:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763582,2018-05-06 03:47:36 UTC,"Adding some additional information.
Agree with you the that the original issue ie that --output works only with --format was targeted to be fixed by just removing the --output option for the juju 'run' command. But then later it was identified there is some usage of the having this option and writing to a file.
So, the PR which was targeting to remove the --output option is closed for now.
Will address the original issue of fixing the --output option behaviour even with out providing the --format option.
Agree ?"
1763582,2018-05-12 00:54:14 UTC,Will detail the precise use of having --output option for this particular command run and we can move further. Thanks John.
1763582,2018-05-08 02:58:39 UTC,"We should certainly have some sort of effect when passing --output. If
there is some reason we can't use it, then we should fail with an error and
not silently ignore the users request."
1763582,2018-05-04 06:30:21 UTC,"It sounds like the decision to 'fix' this is to just remove the flag completely, but it does at least fix the issue of --output only being respected if --format is supplied, which is certainly a bug.
Please link a PR if this does get landed."
1763582,2018-05-04 08:29:52 UTC,It was decided not to fix this at this point of time. I have closed the PR for now.
1763582,2018-04-16 03:32:33 UTC,"As per the decision made in team meeting, the --output and --format options can be removed for the run command."
1763582,2018-04-15 21:45:57 UTC,Reopened this issue after observing few scenarios.
1763582,2018-04-13 06:50:35 UTC,"The option --output works well with --format option. if format is omitted it choose default terminal.
So this is not an issue."
1763584,2018-05-28 07:31:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763584,2018-05-28 07:46:40 UTC,"My system is being affected as well, I'm running Ubuntu 16.04.4 having the same service failing to start."
1763584,2018-12-12 10:57:07 UTC,My system (Ubuntu 18.04) on a Thinkpad X1 Extreme is affected as well. I operate the laptop with closed  lid using a Thinkpad TB3 docking station. Here is the relevant output:
1763584,2020-11-12 12:01:31 UTC,"This is affecting me running Ubuntu 20.10. Is ureadahead still used, 2 years on, or should I remove it?"
1763588,2020-07-21 17:11:23 UTC,This should work:
1763588,2020-03-18 13:06:52 UTC,I have in the /etc/init.d/trousers this:
1763588,2018-04-13 14:14:03 UTC,Donal don't write such silly things. This patch is intended to fix that behavior.
1763588,2018-04-18 15:16:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763588,2018-04-13 06:39:16 UTC,"This fixes script error:
Apr 13 13:27:13 dmig-Inspiron-5379 trousers[18286]: /etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator"
1763588,2018-04-13 12:51:02 UTC,The patch does not work if you have more than one TPM device in your machine (I don't know if that is a common thing or not).
1763588,2018-04-13 08:20:47 UTC,"The attachment ""fix-check.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1763591,2018-11-26 15:57:35 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software on https://gitlab.gnome.org/GNOME/glib/issues/
1763594,2018-06-27 20:28:27 UTC,I reproduced the same(?) issue by passing by passing an usb controller to kvm.(https://www.redhat.com/archives/vfio-users/2018-February/msg00030.html) When I shut down the virtual machine and try to start again it always fails. Tested your kernel and still the same issue. Hope this helps.
1763594,2018-06-29 11:16:27 UTC,"Re #29:  I've been running the patched kernel for a day now, and so far I haven't seen any xhci issues.  I'll give an update later this week."
1763594,2018-07-02 13:23:53 UTC,"Bas,"
1763594,2018-06-28 03:51:29 UTC,"I don't see ""xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead"" in the logs you attached, so it's quite possibly another issue."
1763594,2018-05-09 21:02:34 UTC,Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413440.
1763594,2018-06-22 08:28:41 UTC,I just noticed that this 4.17 kernel is from Debian Experimental.  No idea what this was installed on my system though...
1763594,2018-06-22 08:19:21 UTC,I just encountered this bug again in cosmic with kernel 4.17.0-041700rc1-generic.  Definitely not fixed in 4.17.
1763594,2018-07-02 14:04:48 UTC,"I haven't encountered the bug since I've installed your new kernel.  However, I haven't used my computer very much over the weekend, but so far, so good!"
1763594,2018-05-26 08:40:13 UTC,"Looking at the changelogs for the kernel, it seems someone has already created a fix for this and submitted it for 4.17.0-rc6 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6/CHANGES)"
1763594,2018-06-27 15:42:51 UTC,"Please try this kernel, which has some back ported commits to solve the issue:
https://people.canonical.com/~khfeng/lp1763594/"
1763594,2018-07-16 21:05:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763594,2019-01-24 08:31:12 UTC,"@Steve,"
1763594,2018-07-22 12:14:40 UTC,"Verified this on a Thinkpad X230 with lastest Ubuntu 18.04/Linux Mint 19 kernel and Archlinux (4.17.8-1-ARCH).
For me, however, the symtoms are a bit different:"
1763594,2018-07-25 21:30:03 UTC,This bug was fixed in the package linux-oem - 4.15.0-1012.15
1763594,2018-08-05 17:08:19 UTC,"Kai-Heng,"
1763594,2018-08-06 04:41:03 UTC,"The kernel team doesn't like the big pull I've made, so I made a backported version of the patch which is now in upstream linux stable."
1763594,2018-11-14 17:56:43 UTC,"I've been getting similar disconnects on a Dell Latitude 5580 that is connected to a Dell D6000 docking station via USB-C.  I'm also using DisplayLink driver version 4.4.24 (https://www.displaylink.com/downloads/ubuntu) in order to connect to two external displays.  With Ubuntu 17.10 I was not seeing any disconnects.  With 18.04 I see at least one per day where the external monitors go dark, and these messages in syslog:"
1763594,2019-01-11 10:31:07 UTC,"Kai-Heng,"
1763594,2019-02-17 20:03:08 UTC,"Kai-Heng,"
1763594,2019-10-16 08:44:48 UTC,"Got the same issue on 5.2 5.3 and 5.4 rc kernels.
The BT part of my Intel 8265 wifi/BT card of my matebook D14 laptop is kicked out after a few minutes of use with a logitech anywhere mx 2s mouse."
1763594,2019-08-21 19:48:16 UTC,"@kunwoo: That patch made it into kernel 4.17.10:
https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.17.10"
1763594,2018-07-20 15:44:47 UTC,This bug was fixed in the package linux-oem - 4.15.0-1012.15
1763594,2018-04-27 20:52:23 UTC,Also maybe related as I am running TLP: https://www.spinics.net/lists/linux-usb/msg167941.html
1763594,2019-08-21 19:21:39 UTC,I am on Kernel 5.2.9 and still experiencing this issue. How has this been fixed?
1763594,2018-04-24 06:32:39 UTC,Maybe related: https://bugzilla.redhat.com/show_bug.cgi?id=1565131
1763594,2018-04-13 07:22:07 UTC,apport information
1763594,2018-04-13 07:22:08 UTC,apport information
1763594,2018-04-13 07:22:09 UTC,apport information
1763594,2018-04-13 07:22:10 UTC,apport information
1763594,2018-04-13 07:22:11 UTC,apport information
1763594,2018-04-13 07:22:12 UTC,apport information
1763594,2018-04-13 07:22:13 UTC,apport information
1763594,2018-04-13 07:22:14 UTC,apport information
1763594,2018-04-13 07:22:15 UTC,apport information
1763594,2018-04-13 07:22:16 UTC,apport information
1763594,2018-04-13 07:22:17 UTC,apport information
1763594,2018-04-13 07:22:18 UTC,apport information
1763594,2018-04-13 07:22:19 UTC,apport information
1763594,2018-04-13 07:22:20 UTC,apport information
1763594,2018-04-13 07:22:21 UTC,apport information
1763594,2018-04-16 18:27:45 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1763594,2018-04-22 18:54:38 UTC,"This is above my competence level in Linux, but I can confirm this problem in:"
1763594,2018-04-22 19:27:24 UTC,"So I installed the latest upstream kernel (4.17-rc1) and the bug described above still occurs. It's frustrating because it means my bluetooth mouse stops working after about 5 minutes, and I can't get it to work again without rebooting. Code copied and pasted below"
1763594,2018-04-23 03:56:23 UTC,Does this happen in previous kernel versions?
1763594,2018-04-13 07:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1763594,2018-04-24 14:34:11 UTC,"This seems similar indeed, although I don't have any thunderbolt hardware.  I'll try running a kernel with CONFIG_USB_XHCI_DBGCAP=n to see if that solves the issue."
1763602,2019-11-08 17:03:10 UTC,Setting to wont-fix as trusty-icehouse is no longer a target/nor supported by the charm.
1763608,2019-04-10 15:49:15 UTC,Is this not fixed in 18.04.2 yet?
1763608,2019-04-20 23:43:17 UTC,"I also have the same problem, running openstack on Ubuntu 18.04.2.
The physical interface of br-ex does not come up because there is not IP address set in netplan yaml file."
1763608,2019-05-08 10:58:02 UTC,"This major bug is one year old and the only answer ""there is no usefulness ..."""
1763608,2019-05-08 14:07:13 UTC,We're actively working on this. Fixing this bug had to wait for another round of stable updates to complete while we correctly addressed the problem and made sure it was fixed correctly.
1763608,2019-05-09 02:09:53 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1
1763608,2019-05-09 21:57:09 UTC,"Hello Johannes, or anyone else affected,"
1763608,2019-05-09 21:59:37 UTC,"Hello Johannes, or anyone else affected,"
1763608,2019-05-09 22:02:31 UTC,"Hello Johannes, or anyone else affected,"
1763608,2019-05-24 16:30:21 UTC,"Thanks to cyphermox, we pinpointed the issue in IRC to:
* when the kernel cmdline contains ip=client-ip:server-ip:gateway:netmask (e.g. due to syslinux IPAPPEND 3),
* ipconfig in the initramfs generates a /run/net-enp0s3.conf file with PROTO='none',
* while the netplan integration in the initramfs-tools was expecting that to be PROTO='static'."
1763608,2019-05-10 17:50:41 UTC,"So; this has landed in Eoan now, and also in -proposed repositories for 18.04, 18.10, 19.04. I'll start doing testing on these releases, but since I don't have an openvswitch setup, any and all further independent confirmation that the issue is fixed (or indeed, if it's not), is welcome."
1763608,2019-05-13 08:00:55 UTC,Verified that the fix works with netplan.io=0.97-0ubuntu1~18.04.1 in bionic.
1763608,2019-05-13 13:10:13 UTC,"@Lars, thanks!"
1763608,2019-05-13 20:33:29 UTC,Verification-done on cosmic:
1763608,2019-05-13 21:02:42 UTC,Verification-done for disco:
1763608,2019-05-20 08:19:24 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1763608,2019-05-20 08:29:26 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~19.04.1
1763608,2019-05-20 08:42:25 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.10.1
1763608,2019-05-20 08:47:57 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.04.1
1763608,2019-05-23 05:46:01 UTC,LTSP booting in 18.04 has broken with the recent netplan update; I think due to this patch.
1763608,2019-05-24 13:50:15 UTC,"In the initramfs; if an ip= command exists in the kernel command-line, a netplan configuration will be written. I would expect this is a requirement anyway if you want to use nfsroot=."
1763608,2019-05-24 14:01:08 UTC,"Sorry for the regression, and thanks for the detailed bug report. I'm
sure a fix will be relatively quick and straightforward, but as an aside
I would suggest that you run some machines on -proposed because that's
where we cook changes to the deep plumbing, and this one was there for a
reasonable period before moving to -updates. I think this would be
especially valuable for LTSP given your audience and some of the tricky
ways in which you exercise the low level bits."
1763608,2019-05-24 14:47:34 UTC,After further discussion about this bug on IRC; I understand the situation better. These are thin clients that run everything off the network.
1763608,2019-02-04 18:16:42 UTC,@Dmitrii I agree.
1763608,2019-05-09 22:34:48 UTC,Thanks for the update. I appreciate these things take time.
1763608,2019-02-04 16:27:49 UTC,Subscribed field-high (netplan) as this impacts the ability of network nodes in OpenStack deployments to come up with a working data-plane.
1763608,2018-04-17 20:16:18 UTC,"Indeed; but this is meant to be that way -- there is no usefulness in having a network device listed in the file without any configuration, as you can always just do ""ip link set $device up"" to bring it up."
1763608,2018-04-23 10:52:32 UTC,"""there is no usefulness in having a network device listed in the file without any configuration, as you can always just do ""ip link set $device up"" to bring it up"""
1763608,2018-04-23 12:25:48 UTC,"I tried the following config, but it had no effect. Using false instead
of off had also no effect. Using true, resulted in netplan generating a
systemd config."
1763608,2018-04-26 07:07:49 UTC,There are in fact many cases where you want an interface brought up without having to apply an IP address.
1763608,2018-05-17 19:29:43 UTC,"Not sure if just anyone is allowed to mark a bug as duplicate, but this looks to be the same as bug #1728134: https://bugs.launchpad.net/netplan/+bug/1728134"
1763608,2018-07-24 08:55:17 UTC,"@cyphermox: ""there is no usefulness in having a network device listed in the file without any configuration, as you can always just do ""ip link set $device up"" to bring it up"""
1763608,2018-07-25 12:47:55 UTC,I am very disappointed about quality of this software.
1763608,2018-09-26 16:07:09 UTC,The case specific to bridging is at #1736975
1763608,2018-10-05 11:49:49 UTC,"For example kolla/openstack requires running interface without an configuration. It attaches it's open-switch bridges in a later startup process.
Example:
https://docs.openstack.org/neutron/rocky/install/environment-networking-controller-ubuntu.html"
1763608,2018-10-08 09:09:16 UTC,I don't think this is a kolla bug. Marking invalid for kolla.
1763608,2018-07-20 07:50:45 UTC,A workaround is to set a local ipv6 address on the interface.
1763608,2018-10-12 20:46:49 UTC,"In a general OpenStack installation, especially rolled out via kolla-ansible or openstack-ansible we require network interfaces which are up and without any further configuration. The deployment tools then connect either open-vswitch or linux-bridge to these interfaces. open-vswitch is not making sure that the physical interface is in later process. An example can be shown, if required.
So this is affecting kolla-ansible."
1763608,2018-10-11 07:46:15 UTC,"Can You explain how it's related to Neutron? I don't know about anything like ""Netplan"" to be used in Neutron."
1763608,2018-12-29 06:54:54 UTC,"Lessen learned, don't use any Ubuntu products before LTS .3 release"
1763608,2018-12-17 22:25:57 UTC,"I'm in a similar boat as Mateusz Pawlowski (teluka).
We've got a few different VLANs that we bridge off of to give various LXDs access to different things.  Specifically: LXD inter-container communication/general colo network access, LXD DB hosts, and or DMZ access."
1763608,2018-11-29 00:00:56 UTC,Just ran into this when installing devstack on Ubuntu 18. I configured netplan with:
1763608,2018-11-12 20:12:58 UTC,ii  netplan.io                            0.40.1~18.04.2                    amd64        YAML network configuration abstraction for various backends
1763608,2019-02-04 16:55:36 UTC,I do not think Neutron is related in any way here by the way because it is not responsible for bringing OVS bridge interface links up => moving to invalid for Neutron.
1763608,2018-11-10 13:23:54 UTC,The version of netplan.io in bionic-proposed appears to resolve this problem for me.
1763608,2018-11-07 10:03:19 UTC,"Regardless of the application stack, it is simply not acceptable a NIC manager that does not allow to have an interface up with not ip configured. This is basically makes the interface usable just at layer 3, how about having something working on the date lync?!?"
1763608,2018-10-12 21:22:22 UTC,"@Andreas, sorry but I still don't understand how it affects neutron. Maybe You can give some more detailed example to explain that."
1763608,2018-11-12 19:27:59 UTC,"Hi Tim,"
1763615,2018-04-15 04:30:28 UTC,Unsubscribing the Ubuntu Sponsors team as there's nothing to sponsor at the moment. Please resubscribe the sponsors team when the Release Team has made a decision.
1763615,2018-04-15 06:03:44 UTC,"Ah, I have been advised otherwise. I'll sponsor now."
1763615,2020-03-19 14:39:03 UTC,Actually this was fixed since bionic.
1763619,2018-04-25 09:51:33 UTC,"hi cong, just to update that i tested queens, it is working fine
but tested pike, it throw different error. It is due to heat translator
any pointer if i can fix this? how about update the heat translator?"
1763619,2018-04-13 08:49:12 UTC,logfile attached
1763619,2018-04-13 13:52:14 UTC,Its hard to debug because the error is from heat translator. Can you update it to master or queens version?
1763619,2018-04-13 14:49:29 UTC,"i need to test it on ocata and mitaka version actually
if i update to queens, can it be fixed in ocata version? I can give it a try"
1763619,2018-04-13 15:32:35 UTC,"Its hard to say, because ocata may become EOL soon."
1763619,2018-04-13 15:52:51 UTC,"i see, do you have any sample for auto scaling that is tested?"
1763620,2019-08-07 17:41:24 UTC,"Reviewed:  https://review.opendev.org/561166
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=11f5fbedc36ae0a470deec3ba2820c9c66409ce3
Submitter: Zuul
Branch:    master"
1763620,2019-10-07 14:24:00 UTC,This issue was fixed in the openstack/tempest 22.0.0 release.
1763620,2018-04-13 09:01:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561166"
1763635,2018-04-13 11:04:20 UTC,"Follow that post, then report. It might be due to the hardware model on your laptop."
1763635,2018-04-13 11:06:58 UTC,"Also see:
https://help.ubuntu.com/community/SynapticsTouchpad
https://wiki.ubuntu.com/DebuggingTouchpadDetection"
1763644,2018-04-13 09:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1763644,2018-04-16 13:50:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1763644,2018-04-17 14:04:26 UTC,* linux-snapdragon kernel 4.4.0-1090.95 successfully booted and passed all ADT tests [1] and also snap-certification tests.
1763644,2018-04-23 08:22:44 UTC,This bug was fixed in the package linux - 4.4.0-121.145
1763644,2018-04-23 09:07:48 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1090.95
1763647,2018-07-22 23:02:54 UTC,"The latest dailies and 18.04.1 (to be released this week) support RAID. They don't allow the creation of a degraded setup though, so I guess I can retitle and repurpose the bug for that."
1763649,2018-08-31 15:04:44 UTC,Would it be possible to get a fixed QEMU version into the Xenial-Ocata cloud archive?
1763649,2018-05-15 09:47:20 UTC,"I was confused by your ""versions on Bionic/Queens are good"" statement."
1763649,2018-05-15 09:27:09 UTC,"So it is not fixed by your upgrade to queens as you first thought?
=> Ubuntu 16.04 + UCA-Queens fails other than stated in comment #2?"
1763649,2018-05-15 09:07:17 UTC,"Well,  still Xenial with cloud archive repos for queens."
1763649,2018-08-31 15:03:31 UTC,I can confirm that upgrading from Xenial-Ocata to Xenial-Pike (both Cloud Archive) solves the issue.
1763649,2018-05-15 08:47:30 UTC,"Problem was solved by upgrade to Queens.
Looks like it was caused by ceph/rados libs w/ qemu issues."
1763649,2018-04-17 07:40:01 UTC,"@Corey / James - I have no ceph around at all, also this is reported against a cloud-archive qemu (Ocata if I read it correctly)."
1763649,2018-05-15 09:00:46 UTC,"Thanks Crazik for reporting that, at least that means newer versions on Bionic/Queens are good."
1763650,2020-03-28 01:59:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763663,2018-04-13 14:48:07 UTC,No details? What do you call the tremendously helpful URLs that are 404s (waiting for the deprecation notices to be merged)? :P
1763672,2018-04-13 10:49:08 UTC,The version in use is os-net-config-8.4.1-0.20180328025607.08a0f08.el7.centos.noarch
1763688,2018-04-23 09:06:24 UTC,The package has been published and the bug is being set to Fix Released
1763688,2018-04-23 08:23:44 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-121.145~14.04.1
1763688,2018-04-20 15:36:33 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/4.4.0-121.145~14.04.1/trusty-4.4-proposed-published.html"
1763688,2018-04-20 03:10:59 UTC,"4.4.0-121.145~14.04.1 - generic
Regression test CMPL."
1763688,2018-04-18 23:06:32 UTC,Hardware Certification have begun testing this -proposed kernel.
1763689,2018-04-16 12:54:22 UTC,Hardware Certification have begun testing this -proposed kernel.
1763689,2018-04-16 14:46:29 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/QTDGymAQ/237-dragonboard-kernel-440-109095-46"
1763689,2018-04-19 18:31:56 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1090.95/snapdragon-4.4-proposed-published.html"
1763689,2018-04-23 09:07:48 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1090.95
1763689,2018-04-23 12:33:42 UTC,The package has been published and the bug is being set to Fix Released
1763689,2018-05-03 02:04:18 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1090.95
1763690,2018-05-04 13:30:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763705,2018-04-13 13:05:40 UTC,This is the body passed to neutron server to create the router:
1763707,2018-04-13 13:48:01 UTC,"in Tacker configuration file, we also have:"
1763707,2018-04-13 14:07:48 UTC,"Hi Phuoc,
That just tells you what kind of vim drivers the Tacker instance currently supports not what is enabled."
1763712,2018-04-13 14:08:33 UTC,"Hmm, not seeing corresponding logs on the c-vol side. I wonder if we are hitting rabbitmq issues?"
1763712,2018-12-12 20:31:32 UTC,Similar to:
1763712,2018-12-12 20:49:42 UTC,Looking at a recent failure:
1763712,2018-12-12 21:05:07 UTC,Related change: https://review.openstack.org/624809
1763712,2018-12-13 18:05:59 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/624809
Reason: Quick recheck"
1763712,2018-12-13 18:07:00 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/624809
Reason: Must have done it too quickly."
1763712,2018-12-14 05:17:09 UTC,"Reviewed:  https://review.openstack.org/624809
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=206f980cc2f09610ffb86cfc7728222fd39eee4f
Submitter: Zuul
Branch:    master"
1763714,2019-01-07 16:33:34 UTC,"They are required to develop native kresd plugins(We need such plugin in our infrastructure, but I'm pretty sure very few people need that).
The distributed headers are completely unusable as they use double quotes instead of angle brackets and IIRC, they even reference headers that are not distributed in include (and require to use them from source directly)."
1763714,2019-01-07 16:09:20 UTC,"We (upstream) are not aware of any existing or planned SW anywhere using the headers or libkres :-)  (except kresd linking against libkres, of course)"
1763715,2019-04-27 21:21:52 UTC,Hi José-
1763715,2019-06-05 19:01:46 UTC,"@Jose, I took a look at your patch and you have a lot of coding policy violations[1].  The easiest way to fix you issue is use the clang-format hooks[2] build into our git repo.  Also, we typically prefix class members with ""m_"" not ""_"".   I'm not sure showing a warning dialog every calculation is a good idea.  I would rather see a checkbox that allows the user to keep their current settings and a warning in the ""Results"" box if there is calculation error.  Most users find constantly showing a warning dialog annoying."
1763715,2019-05-30 02:40:43 UTC,@José- Is this something you could look at for 5.1.3?
1763715,2018-09-23 13:58:43 UTC,Hi José-  Thank you for continuing to improve your patch!  It will take a bit of time to review your patch and consider this approach.  I should be able to look at it after the 5.0.1 release unless someone else is able to get to it first!
1763715,2018-09-22 06:14:23 UTC,"I'm attaching a patch that takes a different approach, it adds a copy of every input parameter and compares the copy after the calculation, if different, shows a message to the user and let's him/her keep the new values or return to the original ones.
This patch could cover the following:
* showing a message to the user so he/she knows explicitly what happened.
* allows the user to see the new values,
* allows the user to keep the original values."
1763715,2018-09-08 03:31:47 UTC,"I haven looked in detail, but it seems that several calculations use approximations and try to reduce the error by adjusting several values for input parameters, that's why at first I thought of letting the values change (current behavior), show a message box to the user stating that the change is indeed detected and let him/her keep the new values or go back to his/her original input."
1763715,2019-04-26 16:55:04 UTC,Sorry that this slipped through the cracks.  Setting milestone so we don't forget it
1763715,2018-09-05 02:33:00 UTC,I'm attaching a WIP patch that does not update the input parameters described in the bug description.
1763715,2018-08-24 16:29:19 UTC,"I am guessing the fact ""Synthesize"" overwrite input parameters is only a (bad) side effect of the way internal calculations are made."
1763715,2018-08-24 16:01:56 UTC,@José-  Good question.  I think the correct solution is Janis' suggestion: warn of no solution when the result is NaN and keep the user's previous input values.
1763715,2018-08-24 08:14:53 UTC,I don't see any situation where I would want my input parameters changed. What would be the use for that? I think warning that there is no solution for given parameters would be enough.
1763715,2018-08-24 07:26:47 UTC,Would it be ok to show a dialog asking the user if he/she wants to keep or revert the changes to the input parameters?
1763715,2018-09-05 02:54:21 UTC,Hi José-
1763717,2018-06-29 20:17:17 UTC,"same problem over here, driver 396.
Applications affected on my system:
  shotcut
  hiri
  noson"
1763717,2019-11-20 04:17:24 UTC,[Expired for snapd because there has been no activity for 60 days.]
1763717,2018-04-13 13:37:02 UTC,"$ sudo  /usr/lib/snapd/snap-discard-ns  shotcut
[sudo] password for alan:
alan@hal:~$ SNAPD_DEBUG=1 SNAP_CONFINE_DEBUG=1 shotcut
2018/04/13 14:36:49.197207 cmd.go:203: DEBUG: restarting into ""/snap/core/current/usr/bin/snap""
DEBUG: security tag: snap.shotcut.shotcut
DEBUG: executable:   /snap/core/current/usr/lib/snapd/snap-exec
DEBUG: confinement:  classic
DEBUG: base snap:    core
DEBUG: ruid: 1000, euid: 0, suid: 0
DEBUG: rgid: 1000, egid: 0, sgid: 0
DEBUG: apparmor label on snap-confine is: /snap/core/4443/usr/lib/snapd/snap-confine
DEBUG: apparmor mode is: enforce
DEBUG: skipping sandbox setup, classic confinement in use
DEBUG: creating user data directory: /home/alan/snap/shotcut/21
DEBUG: requesting changing of apparmor profile on next exec to snap.shotcut.shotcut
DEBUG: loading bpf program for security tag snap.shotcut.shotcut
DEBUG: read 14 bytes from /var/lib/snapd/seccomp/bpf//snap.shotcut.shotcut.bin
DEBUG: execv(/snap/core/current/usr/lib/snapd/snap-exec, /snap/core/current/usr/lib/snapd/snap-exec...)
DEBUG:  argv[1] = shotcut"
1763717,2018-04-16 09:02:14 UTC,Works fine outside of snap when I installed all the dependencies on the host.
1763717,2018-04-16 09:02:57 UTC,"FWIW, this looks like a problem with the binary itself."
1763717,2018-04-16 14:26:39 UTC,This is the problem https://bazaar.launchpad.net/~popey/+junk/mameedge/view/head:/snap/snapcraft.yaml#L182
1763717,2018-06-02 11:58:19 UTC,"i am experiencing the same problem running shotcut on 18.04
n: failed to create symbolic link '/home/matthew/snap/shotcut/21/.config/gtk-2.0/gtkfilechooser.ini': File exists"
1763717,2018-06-02 11:59:22 UTC,BTW i am using an nvidia gtx 1050 mobile
1763717,2019-09-20 09:15:04 UTC,"Dear reported, can you please provide a single application to look at. I'd like to look at a specific case instead of at a broad spectrum. Snaps using classic confinement do not benefit from some of the system compatibility features provided by snapd. It requires careful creation of a correct snap. I suspect it is much more likely that a specific snap is made incorrectly."
1763718,2018-04-13 15:01:43 UTC,https://bugs.launchpad.net/evergreen/+bug/1705133/comments/9
1763718,2018-04-13 14:56:32 UTC,"Hi Pam,"
1763718,2018-04-13 14:56:50 UTC,"This is not in Webby, also not in 3.0.4."
1763718,2018-04-13 14:22:43 UTC,"This is a critical field for our libraries.  We have it display by default in the staff client and often refer to it whenever a problem with a hold occurs.  For example, from time to time, a hold slip will print without patron contact information.  We check staff hold? field, so we can determine if the patron unchecked their contact information when they placed the hold or staff did in error."
1763727,2018-10-13 09:55:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763727,2018-10-13 11:52:56 UTC,"postinstall script /var/lib/dpkg/info/firebird3.0-server.postinst exits with error after command:
`adduser --system --quiet --home /var/lib/firebird --group --gecos ""Firebird Database Administator"" firebird`
when user 'firebird' exists or/and it is not system user."
1763727,2018-10-13 12:16:20 UTC,Another way: ignore errors.
1763727,2018-10-13 12:20:34 UTC,"...oops, wrong button :)"
1763730,2019-05-07 12:20:42 UTC,Closing because no longer replicated in 1.0alpha . This is still an issue in 0.92.x.
1763730,2018-04-13 16:26:55 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1763730,2018-05-02 13:01:59 UTC,"I have the following information from user Moini on inkscapeforum.com: ""the colors are applied via CSS classes. Inkscape doesn't fully support that yet in Inkscape 0.92.3...  it's even worse with the development version, although that is supposed to be more advanced in that respect. There, upon opening, the objects are all black (or rather: fill is unset) already""."
1763733,2020-09-15 13:56:45 UTC,"For sites that make use of fan networking, you need to return the fan address for containers to be able to interoperate with the other machines. My memory is a little bit hazy on the exact details, but for 2 application to interoperate where one is in a container and one is on the host machine, they both should use fan addresses in order to communicate."
1763733,2020-09-15 13:26:40 UTC,Subscribing field-critical as this blocks the customer deployment.
1763733,2020-09-16 10:45:15 UTC,"Thank you, @jameinel. Let me remove fan networking altogether.
Unsubscribing field-critical as we have a workaround."
1763733,2020-02-26 22:35:50 UTC,Marking as Won't Fix for 2.3 series since we are not planning to make any further releases in this series at this stage.
1763733,2020-09-15 13:23:57 UTC,I'm experiencing `network-get` returning fan network IP address as well on vSphere substrate. I'd expect network-get always to return non-fan address.
1763738,2018-04-13 16:21:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1763741,2018-04-24 19:50:21 UTC,"Reviewed:  https://review.openstack.org/561404
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d435f2f03ffe6cb473c516b4d21027c706467d59
Submitter: Zuul
Branch:    master"
1763741,2018-06-08 12:25:50 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1763741,2018-05-15 05:45:40 UTC,"Reviewed:  https://review.openstack.org/563253
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=18d670b0b53f07e18710e84ae490a91c44653f20
Submitter: Zuul
Branch:    stable/queens"
1763741,2018-04-20 19:34:41 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/563253"
1763741,2018-04-14 12:44:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561404"
1763741,2018-04-14 12:34:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561403"
1763741,2018-04-13 14:44:42 UTC,"Also note that we'd likely want to split this into two changes, one for 2.47 which could be backported to stable branches, and one for 2.61 which is just for Rocky."
1763741,2018-04-20 05:21:06 UTC,"Reviewed:  https://review.openstack.org/561403
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8a6722ea9cdcbbee417b092a7261339b73dfe0c4
Submitter: Zuul
Branch:    master"
1763748,2018-05-24 18:05:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1763748,2018-05-12 06:11:33 UTC,"I finally could get back to my laptop, and I have tried Kau-Heng's patched kernel 4.15.0-22 . I confirm that the webcam now works as expected. Thanks a lot Kay-Heng and Mario."
1763748,2018-05-15 11:46:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763748,2018-05-14 17:42:20 UTC,@Mario Tested-by submitted to upstream. Thanks for this hint!
1763748,2018-05-25 01:02:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1763748,2018-05-11 21:52:51 UTC,"@Mario
Well, 1.0 already works without any patch. It'just downgraded in features too, right?"
1763748,2018-05-10 17:04:40 UTC,"@Kai Heng,"
1763748,2018-05-11 10:55:26 UTC,Hello! I have compiled kernel module with patch from https://lkml.org/lkml/2018/5/8/1117 and I can confirm it works. I'm attaching related lines from dmesg. Module was loaded via insmod. I'm using 4.16.1 Kernel.
1763748,2018-05-11 05:48:13 UTC,Some steps to install the kernel on https://people.canonical.com/~khfeng/lp1763748-rtl/.
1763748,2018-05-11 04:41:03 UTC,"I built a kernel with the patch. Please try it here.
https://people.canonical.com/~khfeng/lp1763748-rtl/"
1763748,2018-05-26 01:39:16 UTC,"I'm not seeing a -proposed kernel for linux-generic-hwe-16.04 or linux-generic-hwe-16.04-edge, but would be happy to test one."
1763748,2018-05-10 18:15:33 UTC,"Hello,
  I am with the few who tried the downgraded firmware 1.0
  Would it be possible to release the firmware 1.5 for us to re-upgrade?"
1763748,2018-05-11 14:54:32 UTC,"@Josef,"
1763748,2018-05-26 13:00:47 UTC,Just confirming the kernel in proposed fixed the webcam for me in 18.04.
1763748,2018-06-11 15:27:54 UTC,This bug was fixed in the package linux-oem - 4.13.0-1030.33
1763748,2018-05-29 06:01:48 UTC,"Ok for Xenial (v4.4) kernel, there's one missing commit that adds UVC1.5 to device ID."
1763748,2018-05-31 14:24:14 UTC,"well. I have just tested the proposed kernel (*) for 16.04. strangely my camera is not seen at all, there is not trace of any ""UVC"" activity in syslog/dmesh, and when I load the module ""by hand"" it does not detect any camera. only lsusb does. Am I still missing something?"
1763748,2018-05-31 14:37:38 UTC,"Well, you are not wrong. There's one missing commit for Xenial. I've already filed LP: #1773905 for that."
1763748,2018-05-31 15:04:59 UTC,"Ok thanks, sorry. Now I understand the meaning of your message #47. I'll wait."
1763748,2018-06-08 13:42:15 UTC,"PS : I tried the ""hwe"" 16.04 kernel (which is the kernel from 17.10) and it does not work either..."
1763748,2018-06-11 03:20:14 UTC,"""Proposed"" needs to be enabled in APT to use the new kernel."
1763748,2018-06-11 15:08:06 UTC,This bug was fixed in the package linux - 4.15.0-23.25
1763748,2018-06-11 15:09:13 UTC,This bug was fixed in the package linux - 4.4.0-128.154
1763748,2018-06-11 15:10:16 UTC,This bug was fixed in the package linux - 4.13.0-45.50
1763748,2018-06-13 09:30:49 UTC,This bug was fixed in the package linux-oem - 4.15.0-1008.11
1763748,2018-06-14 12:16:29 UTC,This bug was fixed in the package linux - 4.15.0-23.25
1763748,2018-06-15 14:05:43 UTC,This bug was fixed in the package linux-oem - 4.15.0-1008.11
1763748,2018-05-28 14:03:52 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1763748,2018-05-10 14:47:37 UTC,"All,"
1763748,2018-05-11 22:03:08 UTC,"Only if you have userspace that uses other 1.5 features, which doesn't
exist today in Linux. The patch and fw 1.0 should be functionally
equivalent for Linux."
1763748,2018-05-03 16:10:00 UTC,"Many thanks too !!!
Works perfectly.
Also no need to reboot."
1763748,2018-05-03 16:37:18 UTC,More comments coming from DELL:
1763748,2018-04-13 15:08:14 UTC,It seems that there is a patch being worked out:
1763748,2018-04-16 06:33:23 UTC,"Another piece of information. This webcam is working with the 1.0 firmware, but not with the 1.5 firmware that the Dell XPS 13 9370 ships right now. Some affected user have reported the issue and they have changed the screen for them with a webcam with the 1.0 firmware, and the webcam started working."
1763748,2018-04-16 07:57:53 UTC,I tried the following upstream kernel:
1763748,2018-04-16 14:47:35 UTC,"Dear Walter,
  that's interesting, thanks for digging this out. Is there any way we can use the firmware 1.00 instead of 1.50? For example swapping a file in /lib/firmware?"
1763748,2018-04-16 15:05:57 UTC,"Dear Stefano, I think the problem is there is no appropriate driver in the Linux kernel for the 1.50 firmware, and the installed webcam has that firmware."
1763748,2018-04-16 15:47:30 UTC,"I've tried with a 4.17rc1 kernel recompiled with the patch mentioned in #2 but no change, the webcam does not work."
1763748,2018-04-16 16:13:06 UTC,Is the webcam firmware upgradable under Linux? I can't reproduce the issue on the XPS 9370 at my hand because it's with older firmware.
1763748,2018-04-16 16:27:45 UTC,"Kai-Heng Feng (kaihengfeng):

>Is the webcam firmware upgradable under Linux? I can't reproduce the issue on the XPS 9370 at my hand >because it's with older firmware.
"
1763748,2018-04-17 07:04:39 UTC,"Please try this kernel,
https://people.canonical.com/~khfeng/lp1763748/"
1763748,2018-04-17 07:35:10 UTC,"Thanks Key-Heng, I tried your kernel but in my system there is no change. The webcam is still using the 1.50 firmware and is not detected by the system."
1763748,2018-04-17 07:36:00 UTC,"Dear Kai-Heng
  thank you vefry much for your contribution. I do have a webcam version
15.0
  I (think I) installed your .deb and rebooted and this is what I see in
the journal:
apr 16 15:18:39 ox kernel: Linux video capture interface: v2.00
apr 16 15:18:39 ox kernel: usbcore: registered new interface driver btusb
apr 16 15:18:39 ox kernel: uvcvideo: Found UVC 1.50 device
Integrated_Webcam_HD (0bda:58f4)
apr 16 15:18:39 ox kernel: uvcvideo: UVC non compliance - GET_DEF(PROBE)
not supported. Enabling workaround.
apr 16 15:18:39 ox kernel: uvcvideo: Failed to query (129) UVC probe
control : -75 (exp. 34).
apr 16 15:18:39 ox kernel: uvcvideo: Failed to initialize the device (-5).
apr 16 15:18:39 ox kernel: uvcvideo: Unknown video format
00000032-0002-0010-8000-00aa00389b71
apr 16 15:18:39 ox kernel: uvcvideo: Found UVC 1.50 device
Integrated_Webcam_HD (0bda:58f4)
apr 16 15:18:39 ox kernel: uvcvideo: UVC non compliance - GET_DEF(PROBE)
not supported. Enabling workaround.
apr 16 15:18:39 ox kernel: uvcvideo: Failed to query (129) UVC probe
control : -75 (exp. 34).
apr 16 15:18:39 ox kernel: uvcvideo: Failed to initialize the device (-5).
apr 16 15:18:39 ox kernel: usbcore: registered new interface driver uvcvideo
apr 16 15:18:39 ox kernel: USB Video Class driver (1.1.1)
   It looks (to me) that the version 1.50 is still detected by the kernel.
Two questions:
   a) how can I make sure I am running your version (the uname -r is the
same...)
   b) is there any other output you would like to see?"
1763748,2018-04-17 12:35:05 UTC,"Ok, I use a more direct way to force the version to be 1.0:
diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c
index 28b91b7d756f..33ee104f1800 100644
--- a/drivers/media/usb/uvc/uvc_driver.c
+++ b/drivers/media/usb/uvc/uvc_driver.c
@@ -2067,6 +2067,8 @@ static int uvc_probe(struct usb_interface *intf,
                goto error;
        }"
1763748,2018-04-13 15:30:07 UTC,This change was made by a bot.
1763748,2018-04-18 04:01:23 UTC,"Right, I wasn't give it too much hoping.
I'll escalate the issue to UVC upstream to let them know the issue.
I'll also ask Realtek if there's a way (maybe via USB control message) to switch between UVC1.0/UVC1.5."
1763748,2018-04-19 14:58:22 UTC,"@Kai Heng,"
1763748,2018-04-19 15:28:15 UTC,"As I say in message #5, I tried 4.17rc1 and the webcam was still not working."
1763748,2018-04-19 15:39:45 UTC,"I actually found the discussion [1] several days ago. The patch is to support a new format.
The webcam in [1] is the UVC1.0 variant."
1763748,2018-04-19 15:41:39 UTC,"If the firmware is downgrade-able, I guess the best option here is to ask users to downgrade the firmware via fwupdmgr?"
1763748,2018-04-19 16:14:40 UTC,See this forum:
1763748,2018-05-03 14:27:47 UTC,"HUGE Thanks!
I can confirm that this solution works perfectly for my laptop (for the record: you do not even need to reboot)."
1763748,2018-04-19 16:34:33 UTC,"@Walter Garcia-Fontes,"
1763748,2018-04-20 06:21:52 UTC,Let's wait for maintainers' reply for [1].
1763748,2018-04-26 02:30:26 UTC,"I am no kernel expert so, will leave that to those of you who are qualified. I did find this interesting. I am experiencing all of the same symptoms but, when I spin up a Windows instance in Virtualbox on 17.10 host, the camera is available and it works. Not sure how to explain that but, it does tell me that the camera is actually functionable."
1763748,2018-04-26 05:14:50 UTC,@jay-z The reason is quite simply that there are drivers for this webcam available for Windows but not for Linux.
1763748,2018-04-17 12:56:32 UTC,"I tried this last one, and webcam still not detected. But now syslog seems to show the 1.00 firmware. This is the output of ""dmesg | grep uvcvideo"":"
1763748,2018-05-03 11:49:58 UTC,A solution has been proposed by Dell France:
1763761,2019-09-23 06:29:48 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/683849"
1763761,2019-09-23 02:58:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/683838"
1763761,2019-09-20 17:34:23 UTC,UNSUUBSCRIBE!!!
1763761,2021-01-04 01:10:18 UTC,"Hey,"
1763761,2018-05-02 14:51:18 UTC,I've got a patch up moving the list of properties from the glanceclient docs (which is a weird place for them) to the Glance Admin Guide: https://review.openstack.org/#/c/565780/
1763761,2018-05-03 13:55:23 UTC,Doc is now in the Glance repo: doc/source/admin/useful-image-properties.rst
1763762,2018-04-13 16:14:18 UTC,"StacktraceTop:
 QChar::unicode (this=0xabc91ec45d20) at ../../include/QtCore/../../src/corelib/tools/qchar.h:426
 <lambda(int)>::operator() (i=0, __closure=<synthetic pointer>) at tools/qstring.cpp:489
 (anonymous namespace)::UnrollTailLoop<7>::exec<int, ucstrncmp(const QChar*, const QChar*, int)::<lambda(int)>, ucstrncmp(const QChar*, const QChar*, int)::<lambda(int)> > (returnIfExited=0, i=0, returnIfFailed=..., loopCheck=..., count=6) at tools/qstring.cpp:182
 ucstrncmp (a=0xabc91ec45d20, b=<optimized out>, l=l@entry=6) at tools/qstring.cpp:492
 ucstrcmp (blen=6, b=<optimized out>, alen=21988, a=<optimized out>) at tools/qstring.cpp:665"
1763763,2018-10-01 09:44:05 UTC,"Thanks Marco but it should be fine, that gtk change is low priority and I can have a look, it should be easy enough (basically adding a static list of .desktop names to ignore)"
1763763,2018-10-01 09:01:15 UTC,"Ah, ok sorry... I was pointed here by the trello card, thus I attached nautilus to it."
1763763,2018-10-01 08:42:37 UTC,"Marco, dropping the legacy .desktop is not what this bug was about. Those are in bionic and can't be removed there so the bug is about patching gtk to filter those specific files out, which is a workaround but should do the job for the stable serie"
1763763,2019-05-14 09:41:41 UTC,The issue is fixed in >= Cosmic. We could workaround it in bionic but it's low priority at this point
1763763,2018-09-28 00:24:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763763,2018-04-17 13:53:33 UTC,"Thanks, that's worth fixing but not really a release blocked issue, tagging rls-bb-notfixing"
1763763,2018-09-28 23:57:32 UTC,This bug was fixed in the package nautilus - 1:3.26.4-0ubuntu4
1763766,2020-01-16 20:00:09 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/702972"
1763766,2020-08-18 02:28:23 UTC,"Reviewed:  https://review.opendev.org/703116
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=643405b3a751f7547417e48e00db05d9fe8e99c4
Submitter: Zuul
Branch:    stable/rocky"
1763766,2020-02-06 12:45:02 UTC,This issue was fixed in the openstack/nova 19.1.0 release.
1763766,2020-02-06 12:40:37 UTC,This issue was fixed in the openstack/nova 20.1.0 release.
1763766,2020-01-31 15:43:40 UTC,"Reviewed:  https://review.opendev.org/702974
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8346c527b379395851a9de063b4978b489076bf6
Submitter: Zuul
Branch:    stable/stein"
1763766,2020-01-31 02:34:48 UTC,"Reviewed:  https://review.opendev.org/702972
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9f57d16f38f0290718e3ba78393d064746f7e527
Submitter: Zuul
Branch:    stable/stein"
1763766,2020-01-17 17:49:45 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/703142"
1763766,2020-01-17 17:49:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/703140"
1763766,2020-01-17 16:33:03 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/703118"
1763766,2020-08-18 02:30:34 UTC,"Reviewed:  https://review.opendev.org/703118
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=84c63816602dcdf91885d20bb5d26cec336fb71e
Submitter: Zuul
Branch:    stable/rocky"
1763766,2020-01-16 20:00:43 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/702974"
1763766,2019-12-23 19:28:34 UTC,"Reviewed:  https://review.opendev.org/700127
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=48bb9a9663374936221144bb6a24688128a51146
Submitter: Zuul
Branch:    stable/train"
1763766,2020-01-17 16:32:29 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/703116"
1763766,2019-12-20 11:42:01 UTC,"Reviewed:  https://review.opendev.org/698260
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f6060ab6b54261ff50b8068732f6e509619d713e
Submitter: Zuul
Branch:    master"
1763766,2019-12-20 18:49:22 UTC,"Reviewed:  https://review.opendev.org/698530
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=745de99063bf77704a7f0610fe9e3647257eaa50
Submitter: Zuul
Branch:    stable/train"
1763766,2018-04-13 16:22:20 UTC,"For background, this was discussed in bug 1750623 and deemed to be a separate bug which requires its  own fix. As far as I can tell, this has been a problem since NUMA support was added, which I think was Juno."
1763766,2018-08-20 10:10:58 UTC,I am looking for a way to tell NUMAtopology filter's hardware.numa_fit_instance_to_host to skip tune above host topology in rebuild case.
1763766,2018-08-20 15:08:52 UTC,"Currently we allow rebuilding to a new image with different image properties, so we need to ensure that the new image properties take effect on a rebuild.  For example, the new image could interact with the AggregateImagePropertiesIsolation or ImagePropertiesFilter scheduler filters so we need to ensure that these filters get run."
1763766,2018-08-22 07:00:05 UTC,"I hit a situation when free vcpus on host <= instance flavor used vcpus (CPU pinning requested). The rebuild such instance on the same host (e.g. Guest OS Upgrade with new image) will fail.
Even with 3 other bugs fixes:
    https://bugs.launchpad.net/nova/+bug/1750623
    https://bugs.launchpad.net/nova/+bug/1750618
    https://bugs.launchpad.net/nova/+bug/1772523
NUMAtopology filter's hardware.numa_fit_instance_to_host will will call _numa_fit_instance_cell_with_pinning() which compares host_cell.avail_cpus < required_cpus, then skip the host selection with debug message ""Not enough available CPUs to schedule instance. Oversubscription is not possible ..."".
With educated guess, memory fit may also fail."
1763766,2018-04-23 19:49:26 UTC,Some related discussion in the mailing list here:
1763766,2019-12-09 23:49:18 UTC,"Reviewed:  https://review.opendev.org/687957
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6f5358ac1992b17b7f3f99d9a32290e0d4740dae
Submitter: Zuul
Branch:    master"
1763766,2019-12-10 14:28:36 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/698260"
1763766,2019-12-11 16:39:07 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/698530"
1763766,2019-12-20 09:43:01 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/700127"
1763766,2019-10-10 17:06:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/687957"
1763773,2018-04-19 20:37:02 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1763774,2018-08-28 10:01:57 UTC,Have you tried running GDM with X instead of Wayland ?
1763774,2019-03-12 19:08:03 UTC,"I also have the same problem on Ubuntu 18.04.2.
The login screen starts normally, but right after typing my password and pressing enter the screen is black."
1763774,2018-10-03 09:13:33 UTC,I can login if I choose the recover mode at the boot menu and then the option resume.
1763774,2018-10-03 09:04:31 UTC,I have the same experience since last week as sebastian. I'm using the nvidia 340.
1763774,2018-08-31 12:13:06 UTC,"I am also affected by this since the latest upgrade which included among others libX11, libmutter, mutter and libvulkan (full list attached). I am using the Nvidia binary 396 drivers and everything was runnning fine before. I could however circumvent the problem by ssh'ing into the machine and simply stoping the gdm3.service and then restarting it. However I could not switch to another TTY as suggested in the first post. Hope this helps a bit to solve the issue."
1763774,2018-06-17 22:48:23 UTC,I've tried multiple approaches for 2 months and I'm still not able to install boot with the Nvidia drivers enabled.
1763774,2018-04-30 11:47:45 UTC,"Just wanted to confirm that I'm affected by this as well.
I'm getting a black screen at startup whenever I enable the Nvidia driver (tried both 390 and 396).
I have a GTX 1050 Ti (with an Asus Prime X299-Deluxe Mobo).
Tried deleting xorg.conf with no results. On 18.04 final."
1763774,2018-04-28 13:09:59 UTC,I am still affected by this after the 18.04 release.
1763774,2018-04-15 10:58:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763774,2018-04-14 17:03:28 UTC,"BTW, I was able to resolve the hang using the fix from this report https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1705369"
1763774,2018-04-13 16:52:28 UTC,"Wasn't sure whether to file this as an xorg bug instead.  I noticed that the native driver functions up to the point when I click ""sign in"", and xorg functions on its own.  It seems to be an interaction between the xorg native nvidia package and the nvidia driver."
1763776,2019-05-23 13:13:27 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/660997"
1763776,2019-05-23 22:31:53 UTC,"Reviewed:  https://review.opendev.org/660991
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ed5f481aa6b9f19f54a88eb0ff72f9e8ad6bb301
Submitter: Zuul
Branch:    stable/stein"
1763776,2019-05-24 03:00:42 UTC,"Reviewed:  https://review.opendev.org/657959
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=9cc7489cca85eee6ce9950c1ee1d5f01c8251efc
Submitter: Zuul
Branch:    master"
1763776,2019-05-25 00:07:16 UTC,"Reviewed:  https://review.opendev.org/656398
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=2816c3da7ba491c8e119c37be00994c10f6ab8a5
Submitter: Zuul
Branch:    master"
1763776,2020-08-21 08:18:57 UTC,"Reviewed:  https://review.opendev.org/746786
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=1399785a59a8e08b2228c957e8aeabad104a7101
Submitter: Zuul
Branch:    stable/train"
1763776,2020-08-18 08:14:01 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/746656"
1763776,2019-05-23 13:01:36 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660991"
1763776,2020-08-18 18:19:01 UTC,"Reviewed:  https://review.opendev.org/746656
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=1fd42a85da98e356e85146a9afbec528584c600b
Submitter: Zuul
Branch:    master"
1763776,2020-08-18 18:40:54 UTC,"Related fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/746785"
1763776,2020-08-18 18:41:06 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/746786"
1763776,2020-08-19 14:09:28 UTC,"Reviewed:  https://review.opendev.org/746785
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=7fcc694d002e3c163d14698067b6540dd913a324
Submitter: Zuul
Branch:    stable/ussuri"
1763776,2019-05-27 13:27:47 UTC,"Reviewed:  https://review.opendev.org/660997
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=74fd3fe5b96b3d7c532b83b327c86d91e5ef6f9a
Submitter: Zuul
Branch:    stable/rocky"
1763776,2019-05-23 00:30:56 UTC,"Reviewed:  https://review.opendev.org/655822
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=016279b71e74700c18f2270649cb7567ae94505f
Submitter: Zuul
Branch:    master"
1763776,2019-04-29 20:25:40 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/656398"
1763776,2019-05-16 10:43:09 UTC,"Reviewed:  https://review.opendev.org/658278
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=098fdb2cd912dabeeb40161edc6dd5df98940c31
Submitter: Zuul
Branch:    stable/stein"
1763776,2019-05-22 23:40:36 UTC,"Reviewed:  https://review.opendev.org/658280
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=6b0bf9098e5c6d3bc6677e39406a397bb4e50527
Submitter: Zuul
Branch:    stable/rocky"
1763776,2018-04-13 16:59:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561273"
1763776,2018-04-19 13:30:50 UTC,This issue was fixed in the openstack/puppet-tripleo 9.0.0 release.
1763776,2019-04-25 17:16:21 UTC,I'm recycling this bug as we still can't use a hostname for undercloud_*_host parameters.
1763776,2019-04-26 01:25:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655822"
1763776,2018-04-16 22:40:33 UTC,"Reviewed:  https://review.openstack.org/561273
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=6d510547965350338d0d11c4114f67bc6c3d9702
Submitter: Zuul
Branch:    master"
1763776,2019-05-09 18:29:47 UTC,"Reviewed:  https://review.opendev.org/655777
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=c925c3b93bf02538c9308baf91aa0c7cc6dd20e9
Submitter: Zuul
Branch:    master"
1763776,2019-05-10 06:55:10 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/658278"
1763776,2019-05-10 07:01:45 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/658280"
1763776,2019-05-16 07:58:41 UTC,"For local UC docker registries resolvable into an IPv6 address, we should consider backporting that into instack for Queens."
1763776,2019-05-09 09:02:45 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657959"
1763794,2019-12-18 09:23:45 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1763805,2018-04-13 18:47:53 UTC,"StacktraceTop:
 Akonadi::CollectionFetchJob::collections (this=this@entry=0x0) at ./src/core/jobs/collectionfetchjob.cpp:197
 Akonadi::CollectionRequester::Private::_k_collectionReceived (this=0x5572a947dde0, job=0x5572a93a5740) at ./src/widgets/collectionrequester.cpp:80
 QtPrivate::QSlotObjectBase::call (a=0x7ffe38c20eb0, r=0x5572a939bf50, this=0x5572a93a1cc0) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
 QMetaObject::activate (sender=sender@entry=0x5572a93a5740, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe38c20eb0) at kernel/qobject.cpp:3749
 QMetaObject::activate (sender=sender@entry=0x5572a93a5740, m=m@entry=0x7f47f6f61500 <KJob::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe38c20eb0) at kernel/qobject.cpp:3628"
1763817,2018-10-09 21:13:08 UTC,"From playing around it appears about 300 seconds after boot.
I was able to recreate this with kernel 4.15.0-29-generic but no longer after running apt upgrade and rebooting to the 4.15.0-36-generic kernel."
1763817,2018-04-13 19:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1763817,2018-10-09 20:30:09 UTC,I did a clean install of BIONIC via ubuntu-18.04.1-server-arm64.iso on an ARM system and encountered this on first boot.  I am happy to send logs but apport-collect states that I am not the owner
1763824,2018-04-19 00:56:39 UTC,"However, due to near EOL on ocata, there is no plan for the re-work backport of this fix. Ocata is explicitly being marked as ""wont fix"""
1763824,2018-04-19 19:30:46 UTC,This issue was fixed in the openstack/keystone 14.0.0.0b1 development milestone.
1763824,2018-04-19 00:54:59 UTC,This also impacts ocata.
1763824,2018-07-27 07:29:57 UTC,This issue was fixed in the openstack/keystone 13.0.1 release.
1763824,2018-07-27 07:54:04 UTC,This issue was fixed in the openstack/keystone 12.0.1 release.
1763824,2018-04-21 03:53:15 UTC,"Reviewed:  https://review.openstack.org/561354
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=22af1d9f35c86e9c5bca288c2996be5c19e3cd61
Submitter: Zuul
Branch:    stable/pike"
1763824,2018-04-18 20:55:23 UTC,"Reviewed:  https://review.openstack.org/561348
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=78adf4b40fb88e371101ed065ac1d15063d8d86e
Submitter: Zuul
Branch:    master"
1763824,2018-04-20 19:40:38 UTC,"Reviewed:  https://review.openstack.org/561353
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=7bd6454e4721d1ff4935ad36e30e5420ad10e70e
Submitter: Zuul
Branch:    stable/queens"
1763824,2018-04-16 22:29:54 UTC,"Change abandoned by Morgan Fainberg (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/561353"
1763824,2018-04-13 20:49:23 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/561354"
1763824,2018-04-13 20:49:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/561353"
1763824,2018-04-13 20:38:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561348"
1763824,2018-04-13 19:52:19 UTC,"This impacts, primarily the resource-options code, but could impact any schema that NULL is expected as well as another type such as boolean."
1763824,2018-04-16 22:30:05 UTC,"Change abandoned by Morgan Fainberg (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/561354"
1763848,2018-04-13 22:25:05 UTC,Cuando intento solucionar las dependencia ocurre un error relacionado con la ruptura de tuberías.
1763849,2018-04-23 15:16:02 UTC,I wonder if this is related to bug 1763849
1763849,2018-04-23 15:51:00 UTC,"That is, bug 1738893. Many thanks to Andrea for pointing out my mistake."
1763849,2018-04-23 23:27:14 UTC,Hi Kathy
1763858,2019-10-02 04:17:21 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1763858,2018-04-17 06:23:54 UTC,I cannot confirm this on ubuntu trusty
1763858,2019-08-02 11:29:47 UTC,"The crash seems to be vamp related.
We have removed the vamp glue layer in current master. Please check if this bug still ocours."
1763858,2018-09-27 17:33:16 UTC,I have the same issue: --safeMode and setting the waveform to 0 or 2 doesn't change anything. The logs are similar as well. I have attached a backtrace with symbols.
1763858,2018-09-15 20:23:14 UTC,Thanks!
1763858,2018-09-15 20:12:10 UTC,"Just noting, Qt 5.9.2 is enabled for this package."
1763858,2018-04-18 09:09:52 UTC,"You are using
Mixxx ""2.0.0"" ""(git 1.12 r5772)"
1763858,2018-04-17 06:22:06 UTC,"> changing WaveformType to 0 or 2
"
1763858,2018-04-16 19:03:30 UTC,"OK, save mode does not work for you.
But it should.
Please produce a gdb backtrack from the crash."
1763858,2018-04-16 23:33:26 UTC,"Even without the debug symbols, that looks like a video driver problem. Try disabling waveforms by editing ~/.mixxx/mixxx.cfg and changing WaveformType to 0 or 2, save, then try to start Mixxx."
1763858,2018-04-16 23:01:04 UTC,"Thank you. Unfortunately you do not have the debug symbols installed.
you can do it via"
1763858,2018-04-16 22:38:08 UTC,"$ gdb mixxx
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html

>


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""x86_64-linux-gnu"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word""...
Reading symbols from mixxx...(no debugging symbols found)...done.
(gdb) run --safeMode
Starting program: /usr/bin/mixxx --safeMode
[Thread debugging using libthread_db enabled]
Using host libthread_db library ""/lib/x86_64-linux-gnu/libthread_db.so.1"".
[New Thread 0x7fffdc8f4700 (LWP 21885)]
[New Thread 0x7fffd1c02700 (LWP 21886)]
[New Thread 0x7fffd1401700 (LWP 21887)]"
1763858,2018-04-16 15:22:04 UTC,mixxx --safeMode
1763858,2018-04-14 05:48:52 UTC,Try to start Mixxx with
1763858,2018-04-16 23:48:30 UTC,"Ok, I will try."
1763870,2019-07-07 16:14:51 UTC,Is there anything I can do to accelerate the resolution of this bug for Xenial and Bionic?
1763870,2018-04-14 04:22:46 UTC,"The attachment ""Patch for the symbol versioning patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1763870,2019-06-13 16:48:25 UTC,"I can confirm that while this is ""fixed"" by updating to a newer release of Ubuntu (or Debian, as can be read in the Debian bug tracker), this problem is still present in Xenial."
1763870,2019-06-13 17:07:12 UTC,"I can also further confirm that even on the latest LTS, bionic, the same problem still exists today when using the latest version of the official packages `openssl1.0`, `libssl1.0.0`, and `libssl1.0-dev` to have access OpenSSL 1.0.2."
1763870,2019-06-13 20:21:39 UTC,Here is a minimal working example to test the issue: https://gist.github.com/romen/b95e99b3563a8ba4c27d88512c7932ff
1763871,2018-06-30 20:25:55 UTC,I found how to disable Alt-L.
1763871,2018-06-30 19:28:35 UTC,I confirm the issue on Ubuntu Beaver.
1763871,2018-04-16 19:20:06 UTC,Confirmed. A couple of ideas:
1763871,2018-04-27 15:03:45 UTC,"Making the default right-click accessible via a modifier seems like a practical, low-cost solution -- that's what I intuitively tried before discovering the OP's approach."
1763873,2018-05-18 17:39:08 UTC,"Hi,"
1763873,2018-05-18 23:33:05 UTC,"Multiple selection for eeschema should be in 6.0.  I suspect we'll get the cross-probing of multiply-selected nets for free, but I'll leave this open to double-check."
1763873,2019-04-03 10:22:34 UTC,"Fixed in revision 52246121b9791f4571e450fda1f0289c195e3e6e
https://git.launchpad.net/kicad/patch/?id=52246121b9791f4571e450fda1f0289c195e3e6e"
1763879,2018-04-14 03:36:15 UTC,"StacktraceTop:
 QList<KMainWindow*>::QList (this=0x7f4ba75b87d0, l=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:807
 KMainWindow::memberList () at ./src/kmainwindow.cpp:923
 KMKernel::dumpDeadLetters (this=<optimized out>) at ./src/kmkernel.cpp:1127
 kmCrashHandler (sigId=<optimized out>) at ./src/kmkernel.cpp:997
 KCrash::defaultCrashHandler (sig=6) at ./src/kcrash.cpp:392"
1763879,2018-04-19 20:36:23 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1763879,2018-05-10 08:26:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763892,2019-03-05 03:34:04 UTC,Verified on cosmic that mutter version 3.30.2-1~ubuntu18.10.4 has fixed this bug.
1763892,2019-03-13 08:10:20 UTC,"Bionic fix on the way:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362"
1763892,2019-03-12 08:28:10 UTC,You are a living legend Daniel. Thank you for your work :)
1763892,2019-03-12 01:25:39 UTC,Yes I will be backporting the same fix to bionic. At least I will try to. I don't know what conflicts and incompatibilities might be in mutter 3.28.
1763892,2019-03-11 18:47:17 UTC,@Łukasz
1763892,2019-03-07 09:25:09 UTC,there is also this:
1763892,2019-03-11 15:00:12 UTC,This bug was fixed in the package mutter - 3.30.2-1~ubuntu18.10.4
1763892,2019-03-11 15:00:01 UTC,"I think we can assume that at least the mutter cosmic SRU does not introduce regressions and does fix the bug for certain testers. In case there's a follow-up fix needed, please file a separate bug."
1763892,2019-03-13 08:17:21 UTC,Excited! Cant wait.
1763892,2019-03-07 05:19:47 UTC,"Rachel,"
1763892,2019-03-07 05:09:23 UTC,mutter 3.30.2-1~ubuntu18.10.4 doesn't appear to solve this issue in ubuntu budgie.
1763892,2019-03-11 15:00:14 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1763892,2019-03-13 08:41:40 UTC,A few caveats to remember though:
1763892,2019-03-17 13:46:07 UTC,"> I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my 144hz display. However, if I disable my second display (it only supports 60hz), I my main gets 144hz as expected.
"
1763892,2019-03-15 16:17:08 UTC,Hi. On 18.10 with proposed enabled the screen now renders at > 60 Hz and feels smooth (:  This fixes the issue for me. Thank you for you hard work guys.
1763892,2019-03-17 12:26:22 UTC,"I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my 144hz display.  However, if I disable my second display (it only supports 60hz), I my main gets 144hz as expected."
1763892,2019-03-18 02:34:04 UTC,I forgot to mention that multi-monitors still won't work properly in Wayland sessions. You'll only get the speed of the slowest monitor. But a fix for that is coming eventually:
1763892,2019-03-18 10:47:45 UTC,"I'm using Xorg with an AMD Vega 64.  Both displays are connected to the GPU.  My main 144hz display is connected via Display Port, and my second 60hz display is connected via HDMI."
1763892,2019-03-18 12:52:33 UTC,Hello again. Well this is promising news. Because I am also using xorg with multiple monitors. And observing the same exact issue. Taking that discussion over to the other bug then.
1763892,2019-03-19 02:06:00 UTC,"Sorry, this is an issue I should have foreseen and warned people about. This bug is not about multiple monitors, it is about the single monitor case only."
1763892,2019-03-19 02:19:16 UTC,"Argh, sorry again. Bug 1730460 and one of the above links are about Wayland sessions only. Please open a new bug for Xorg."
1763892,2019-03-19 10:26:55 UTC,Thank you Daniel. The new bug is https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832
1763892,2019-05-28 20:46:33 UTC,"Hello Knut, or anyone else affected,"
1763892,2019-05-29 03:46:35 UTC,Fix verified on bionic (both Xorg and Wayland sessions) using mutter version 3.28.4-0ubuntu18.04.1
1763892,2019-05-29 03:49:52 UTC,"The test case passes, and gnome-shell reaches 120Hz for me. But it's not as smooth and reliable as I would like in Xorg sessions. I think https://gitlab.gnome.org/GNOME/mutter/merge_requests/520 will fix that in the coming months."
1763892,2019-06-06 09:33:55 UTC,This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.1
1763892,2019-03-13 08:54:21 UTC,"Still a massive upgrade for me. Ive been working in Windows for the last 10
years with FPS/Hz ranging from 100-240. Loving ubuntu, but it feels so
choppy right now."
1763892,2019-03-02 19:11:34 UTC,Confirmed fixed in Pop_OS 18.10 using the test case provided.
1763892,2018-11-22 13:57:53 UTC,I should say:
1763892,2019-03-01 14:45:37 UTC,"Hello Knut, or anyone else affected,"
1763892,2018-04-14 07:24:27 UTC,Seems I make a mistake here - I confused my laptop installation with this one on my desktop machine.  This one is not running the NVidia drivers.
1763892,2018-04-16 01:41:57 UTC,Thanks for the bug report. It's been a known issue for a while: https://bugzilla.gnome.org/show_bug.cgi?id=781296
1763892,2018-04-16 01:42:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763892,2018-08-02 03:18:34 UTC,Workaround:
1763892,2018-11-09 01:25:45 UTC,"When this bug was first reported in 17.10 it was a Wayland-only bug and the fix for that is awaiting review:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/171"
1763892,2018-11-09 09:26:34 UTC,Verified on a 120Hz display that Xorg sessions only need clutter-Smooth-out-master-clock-to-smooth-visuals.patch removed to fix this.
1763892,2018-11-09 09:47:54 UTC,"Proposed fix for Xorg sessions:
https://salsa.debian.org/gnome-team/mutter/merge_requests/19"
1763892,2019-03-01 21:28:24 UTC,Installed new mutter from proposed today and... Well it didn't crash my system. Due to other complications (which were mentioned previously in may last comment)/ I cannot confirm if it actually fixes the 120/144hz issue in my specific environment. However the changes seems safe enough to me. Hopefully others can also install / confirm / deny.
1763892,2018-11-13 01:20:15 UTC,"Hmm, that's not quite right. The Xorg fix has landed, but the Wayland fix has not. Both require changes to mutter."
1763892,2018-11-22 13:47:48 UTC,Can we please use a different bug for Wayland?
1763892,2018-11-23 01:45:13 UTC,Yeah this bug started out as just being about Wayland so I don't feel comfortable making this bug just about the Xorg case now.
1763892,2018-11-23 06:59:39 UTC,"Here's the final missing piece:
https://salsa.debian.org/gnome-team/mutter/merge_requests/20"
1763892,2018-11-12 19:46:49 UTC,This bug was fixed in the package mutter - 3.30.1-4
1763892,2018-11-23 09:19:46 UTC,"Yes, removing the change from the SRU would resolve the problem, weirdly. Though without fixing the bug."
1763892,2018-11-23 09:10:18 UTC,That fix doesn't appear to be merged upstream.
1763892,2019-02-22 16:40:19 UTC,When do you expect to get into Bionic?
1763892,2019-02-22 10:52:15 UTC,"Cosmic branch prepared:
https://code.launchpad.net/~vanvugt/mutter/+git/mutter/+ref/fix-lp1763892-cosmic"
1763892,2019-02-22 09:52:19 UTC,"Thanks Daniel for your recent comments. They are very helpful. As someone who upgraded to Cosmic specifically to fix this bug. I found it still wasn't working and simple was not sure the reason (as have other factors at play on my system, including Budgie Desktop, multiple monitors, and nvidia card with the closed 415.xx drivers). And even after switching to intel igp (and physically removing my nvidia graphics card), loading up Gnome 3 / unity desktop instead of budgie, and physically disconnecting my 2nd 60hz TV. The original 'remove patch' + CLUTTER_FPS env var still was not changing anything. My xrandr output is claiming 120hz (for acer x34p monitor). However it's still mouse trails and not feeling 120hz."
1763892,2019-02-22 08:09:47 UTC,I am aiming to get the fix(es) into cosmic before bionic.
1763892,2019-02-18 10:57:08 UTC,"Hi Daniel van Vugt, would you be kind enough to let us know how to apply this patch and compile mutter from source. Thank you,
Marius."
1763892,2019-02-25 09:18:38 UTC,"Correction:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599"
1763892,2019-02-01 09:41:46 UTC,I've generated a fresh patch for 3.30 based on the final upstream commits in 3.32:
1763892,2018-11-30 02:02:00 UTC,mutter (3.30.2-2) unstable; urgency=medium
1763892,2018-11-28 01:20:12 UTC,Yes I certainly aim to get the fix into 18.04 eventually. This counts as a hardware enablement bug so it shouldn't be a problem. The only delay is that we need to ensure the fix(es) are in 19.04 and 18.10 first.
1763892,2019-02-16 01:53:55 UTC,"Nothing about Bionic yet? Still need the ""CLUTTER_DEFAULT_FPS"" workaround."
1763892,2018-11-27 12:17:07 UTC,Hi there. Sorry but I'm a bit confused as to which branches will be getting this fix and which ones will not be. Specifically I as wondering if a fix might be back-ported to 18.04. Because I need to stay on LTS release for the canonical kernel live patching service. Otherwise I really would not mind upgrading. Not using wayland over here just xorg. Here is my mutter version. And my Ubuntu software updater says 'no new updates'...
1763905,2018-04-17 21:04:35 UTC,This was assigned CVE-2018-10191.
1763905,2018-04-17 19:46:15 UTC,"Hi, thanks for the report. Unfortunately, as the issue is public, we can not issue a CVE for it. I have submitted a CVE request to https://cveform.mitre.org/ and will report back when MITRE has assigned a CVE for this issue."
1763923,2018-04-18 07:11:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763923,2018-07-25 13:01:04 UTC,https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/1778256 fixed this bug
1763923,2019-01-31 20:29:02 UTC,I have installed apt-btrfs-snapshot 3.5.1 today but the dependencies was not installed automatically.
1763923,2019-11-02 13:26:40 UTC,"This also affects 19.10 so I'm guessing this is waiting on a fix from Debian? The noted debbug is for a similar issue, missing this same depends, but it is for a different package."
1763923,2019-12-24 15:11:16 UTC,"This also happens on 20.04 (development branch).
Installing manually 'python3-distutils' did the trick."
1763923,2021-01-26 18:45:47 UTC,I'm confused why is this bug still present in 20.10.
1763928,2018-04-24 19:36:02 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1763940,2018-07-30 09:33:17 UTC,-- GitLab Migration Automatic Message --
1763940,2018-04-19 16:47:26 UTC,"Created attachment 138931
daemon.conf"
1763940,2018-04-26 11:26:39 UTC,I can't reproduce this... Can you provide the pulseaudio server log? Instructions:
1763940,2018-04-16 07:56:55 UTC,I can reproduce this bug in Totem and Clementine too.
1763942,2019-04-07 16:17:49 UTC,"Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected."
1763942,2019-04-08 09:52:27 UTC,It is theming issue:
1763942,2019-05-29 20:06:53 UTC,This bug was fixed in the package ubuntu-mate-artwork - 19.10.2
1763958,2018-07-30 10:30:27 UTC,Actually... not quite dead.
1763965,2018-04-19 16:49:32 UTC,I didn't want to reply in the Dark Metal thread and take it more off topic.
1763965,2018-04-19 16:51:10 UTC,Sorry re-read my original form post and it clearly did seem to coincide with the audio preferences thing. I had forgotten that.
1763967,2018-05-10 17:19:14 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1763967,2018-04-14 16:30:09 UTC,This change was made by a bot.
1763967,2018-04-16 21:14:57 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1763967,2018-04-16 21:15:15 UTC,"Also, does this issue go away if you boot back into the prior kernel?"
1763967,2018-04-16 23:24:55 UTC,"Bug does not exist in 4.16.2-041602-generic. I did rmmod b43 4 times and it always succeeded immediately. It never worked properly in 4.15.0-13-generic so I am confident this isn't just random success, and it means the bug is fixed in upstream."
1763967,2018-05-11 16:44:26 UTC,rmmod b43 works in 4.15.0-21-generic
1763973,2018-04-14 16:52:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763974,2018-05-10 08:23:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763974,2018-04-14 17:14:03 UTC,"StacktraceTop:
 ?? ()
 QObjectData::dynamicMetaObject (this=<optimized out>) at kernel/qobject.cpp:203
 QMetaObject::cast (this=0x7fabfab29540 <QWidgetWindow::staticMetaObject>, obj=obj@entry=0x55d7db6d1aa0) at kernel/qmetaobject.cpp:366
 QMetaObject::cast (this=<optimized out>, obj=obj@entry=0x55d7db6d1aa0) at kernel/qmetaobject.cpp:355
 qobject_cast<QWidgetWindow*> (object=0x55d7db6d1aa0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:514"
1763975,2018-04-14 17:29:52 UTC,The flickering does not happen if I bypass the Avocent SV340D KVM and plug directly into the monitor. Any thoughts as to why this would happen?
1763975,2018-04-16 03:03:42 UTC,@update. Started occurring even when bypassing the Avocent.
1763975,2018-11-12 07:00:06 UTC,This change was made by a bot.
1763975,2019-02-17 00:00:15 UTC,Just wondering if there is any update on this?
1763975,2019-03-13 09:58:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763977,2018-04-21 21:46:47 UTC,syslog adds :
1763977,2018-04-21 18:20:02 UTC,"On 21/04/18 11:21, ben van 't ende wrote:

> 0.17.0-1ubuntu7 just arrived and fixed it! kudos to the fixer. great
> job!
"
1763977,2018-04-21 21:43:18 UTC,Got worse for me with 0.17.0-1ubuntu7
1763977,2018-04-21 21:49:01 UTC,(I do not have an xorg.conf)
1763977,2018-04-17 08:42:26 UTC,Hi Tom
1763977,2018-04-21 22:28:19 UTC,"Rebooted several times, stays fixed with rc.local empty."
1763977,2018-04-24 19:19:48 UTC,"You've marked this as fix released, yet it only address' Calaudio's issue, which was not the one originally reported."
1763977,2018-04-21 10:21:44 UTC,0.17.0-1ubuntu7 just arrived and fixed it! kudos to the fixer. great job!
1763977,2018-10-16 04:37:17 UTC,"Hi, can I know what's the status of this bug? I'm having exactly the same problem trying 18.10 RC, which installs sddm 0.18.0ubuntu2, and none of the workarounds described above solves the issue for me. Cheers."
1763977,2018-04-21 22:07:53 UTC,Fixed : sudo usermod -a -G video sddm
1763977,2018-04-19 19:37:09 UTC,"0.17.0-1ubuntu6 arrived. Same issue. core-dump at boot, fine on manual start or from rc.local"
1763977,2018-04-16 21:07:12 UTC,Not fixed.
1763977,2018-04-17 19:29:54 UTC,"(or alternatively, where is the core dump file ? GDB is occasionally useful...)"
1763977,2018-04-17 19:18:10 UTC,"no effect, and frankly I don't think incorrect start up sequencing will cause a core dump."
1763977,2018-04-17 18:01:58 UTC,Should be a version 0.17.0-1ubuntu5 arriving soon.
1763977,2018-04-16 15:30:34 UTC,This bug was fixed in the package sddm - 0.17.0-1ubuntu4
1763977,2018-04-15 19:42:28 UTC,The fix has been uploaded to Bionic.
1763977,2018-04-15 15:21:51 UTC,Hi
1763977,2018-04-14 17:14:21 UTC,"Workaround : echo ""service sddm start"" >> /etc/rc.local"
1763977,2018-04-18 17:15:51 UTC,Confirmed that version 0.17.0-1ubuntu5 does not solve the problem.
1763978,2018-10-09 03:33:33 UTC,The bug is fixed after Nvidia pushed an update on 08/10/2018.
1763978,2018-09-09 14:32:55 UTC,"/etc/systemd/system/display-manager.service.wants/nvidia-prime-boot.service was just a symlink to /lib/systemd/system/nvidia-prime-boot.service and it's gone in the latest nvidia-prime package version, 0.8.8.1 that is in bionic-proposed."
1763978,2018-08-26 10:21:33 UTC,"I get the same thing with kernel 4.18.x. The current implementation of the service fails on muxless optimus. Also if one turns off the GPU using /sys/bus/pci, GDM will still not boot up even if the prime boot service would succeed."
1763978,2018-08-08 09:04:28 UTC,"Hi, any solution? Same problem with kernel 4.15.0-30-generic"
1763978,2018-05-20 14:50:34 UTC,"Hi,
I also seem to have this problem:
Ubuntu 18.04
nvidia-prime 0.8.8"
1763978,2018-04-16 18:59:01 UTC,"Hi,
I too had the same problem and after some digging I found out that the file from which the service runs is:
/etc/systemd/system/display-manager.service.wants/nvidia-prime-boot.service"
1763978,2018-04-16 20:22:07 UTC,"The attachment ""Modified service file"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1763978,2018-04-16 19:10:11 UTC,"@op3ntrap
Thanks for responding, since this problem also affects you would you mind clicking ""this bug also affects me (top left). This will give the bug a higher priority."
1763978,2020-05-04 21:54:45 UTC,"The service causing the issue was removed as part of the https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011 fix, released in 0.8.8.1 version."
1763978,2018-05-20 14:45:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763980,2020-05-22 04:17:42 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1763986,2020-07-04 20:08:45 UTC,Also please fidn the initial dialogue box that appears when I try to open grub customizer after installation.
1763986,2020-07-04 20:05:59 UTC,Hi
1763986,2020-07-10 19:27:11 UTC,"Sorry forgot to give you the information regarding my booting partitions. I have a triple boot including windows 10, Manjaro and ubuntu 20.04. Manjaro was the last one to install."
1763986,2018-10-03 11:54:17 UTC,"A workaround is to:
- remove all *_proxy scripts found in /etc/grub.d (or at least their 'x' bit)
- update-grub"
1763986,2018-10-02 23:05:27 UTC,"I have also experienced the same issue on Ubuntu cosmic 18.10 with Grub Customizer 5.0.8.
I have attached a screenshot."
1763986,2018-06-17 08:20:35 UTC,Bug is still present in 5.0.8.
1763986,2018-10-02 23:12:36 UTC,"I have to add that this issue came up only after upgrading to linux 4.18.0-8.
GC was doing relatively fine before that upgrade."
1763992,2018-04-14 19:02:35 UTC,The 02_test-suite.patch has to be regenerated to cope with context changes in the pymol 2.1.0 sources.
1763992,2018-04-14 19:03:58 UTC,The 22_fix_pymol_import.patch has to be regenerated to cope with context changes in the pymol 2.1.0 sources.
1763992,2018-04-14 19:05:23 UTC,The 33_fix_relative_paths_in_example_scripts.patch has to be regenerated to cope with context changes in the pymol 2.1.0 sources.
1763992,2018-04-14 19:07:36 UTC,Add additional 40_fix_apbstools_search_path.patch should be added to solve the long standing issue of the apbstools plugin not being able to find the required psize.py and pdb2pqr.py files from the pdb2pqr package in ubuntu. Trivial to fix.
1763992,2018-04-14 19:10:54 UTC,The PyQt GUI for pymol appears as shown in the attached screen shot under 18.04.
1763992,2018-04-14 20:21:36 UTC,"The attachment ""02_test-suite.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1763992,2018-04-21 13:38:25 UTC,"Just to be clear, the changes required to the existing packaging are..."
1763992,2018-04-21 13:58:39 UTC,"Ubuntu's pymol has no changes compared to Debian. Therefore, it would be useful if you could report this bug to the Debian maintainers of pymol."
1763994,2018-04-14 20:22:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1763994,2019-02-12 22:59:29 UTC,"Hi guys!
My laptop is same model and there's the same issue. I use Ubuntu 18.04 and 4.15.0.45-generic Kernel. I tried to install diff kernel like 4.17.18 and 4.18.4 but when I reset Ubuntu, I have a wrong and I have to change to last kernel that it's working..."
1763994,2018-09-27 09:18:25 UTC,You can always install different kernel with UKUU - Ubuntu Kernel Update Utility
1763994,2018-09-23 18:32:00 UTC,"Unfortunately Bionic is still on 4.15.0, so I haven't been able to confirm the fix."
1763994,2018-08-23 02:41:50 UTC,Awesome!  Thanks so much!  I'll give it a try once 18.04 is on one of these kernels.
1763994,2018-08-22 06:28:02 UTC,"4.4.151, 4.9.123, 4.14.66, 4.17.18, 4.18.4 now has the necessary commits to fix the issue."
1763994,2018-04-14 19:27:41 UTC,Output of lspci:
1763994,2018-07-13 07:18:05 UTC,"I can confirm the problem with loud beeping sound at bios booting time. In my case it can be interrupted by long-pressing power button until the laptop switches off, the next boot works well."
1763994,2018-07-13 07:16:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763994,2019-04-19 13:19:13 UTC,Had same problem today. I had new LG Gram 15Z980.
1763994,2019-02-17 17:57:09 UTC,"LG gram 15z980 with ubuntu 18.04 and 4.15.0-45, same issue! Really load and annoying..."
1763994,2018-08-19 16:57:00 UTC,I came up with a fix and now it's in the queue for future stable kernels.
1763994,2019-02-18 10:42:08 UTC,@Salvador You maybe have a problem with secure boot that is not allowing unsigned kernels to boot. So 4.17.18 and 4.18.4 are not signed with certificate for secure boot.
1763996,2018-04-16 11:49:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1763997,2018-04-14 19:49:06 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x55831b6d43e2 ""caja-file.c"", line=line@entry=7193, func=func@entry=0x55831b6d5990 <__func__.66218> ""caja_file_is_in_trash"", message=message@entry=0x55831de0dd20 ""assertion failed: (CAJA_IS_FILE (file))"") at ../../../../glib/gtestutils.c:2532
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x55831b6d43e2 ""caja-file.c"", line=line@entry=7193, func=func@entry=0x55831b6d5990 <__func__.66218> ""caja_file_is_in_trash"", expr=expr@entry=0x55831b6bdb8c ""CAJA_IS_FILE (file)"") at ../../../../glib/gtestutils.c:2555
 caja_file_is_in_trash (file=0x0) at caja-file.c:7193
 get_column_order (list_view=list_view@entry=0x55831ca30b00) at fm-list-view.c:1933
 set_columns_settings_from_metadata_and_preferences (list_view=0x55831ca30b00) at fm-list-view.c:1944"
1763997,2018-04-15 10:39:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1763999,2018-06-02 07:33:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764004,2018-05-06 13:05:57 UTC,"Update.  Did some digging and I guess this is a backlight problem.  I'm runninge ASUS FX503 with NVIDIA GeForce GTX 1050.  I tried multiple options in isolinux grub (acpi_backlight=nivida, acpi_backlight=vendor, nvidia.modeset=0, nouveau.modeset=0) with no luck.  Installed plain ubuntu and was able to get 18.04 installed (amd64) but it locked up at log in screen.  Couldn't even bring up tty with ctrl-alt-F1,2,3, etc).  So, Now I'm back with 16.04.  Was still having problems so dropped to tty and did all the updates there including installing NVIDIA driver 396 and it's working perfectly.  So, my guess is that the backlight is disabled somehow when installing/upgrading to 18.04.  I wonder if it's a kernel issue as it caused isssues with ubuntu 18.04 as well.  Hope this helps someone."
1764008,2018-04-14 22:05:31 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1764008,2018-04-22 19:48:55 UTC,"Same trouble with Initial RC image 20180421.1
Installing on ThinkPad X41 with two drives. Seemed to install, on reboot got black screen with blinking cursor top left."
1764008,2018-04-25 04:33:52 UTC,Same trouble with version 20180424.
1764008,2018-04-25 18:31:55 UTC,Same trouble with version 20180425.
1764008,2018-04-26 05:50:51 UTC,Same trouble with version 20180425.1
1764008,2018-04-27 04:56:48 UTC,Same trouble with version 20180426.
1764020,2018-04-19 20:23:46 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1764020,2018-04-19 20:30:07 UTC,This change was made by a bot.
1764021,2020-04-23 14:21:55 UTC,Closing because INVALID: GTK Win32 theme is unmaintained.
1764021,2018-04-15 12:56:58 UTC,"(P.S. I though we already had a similar issue somewhere, but I was not able to find it)"
1764021,2018-04-15 12:55:38 UTC,"This is basically a GTK+ issue - ironically just closed today due to their GitLab migration:
  https://bugzilla.gnome.org/show_bug.cgi?id=710650
I'm not sure if they still accept GTK+2 bugs in GitLab (development is focused on GTK+3 and above these days) but you might try your luck."
1764024,2019-06-06 04:17:21 UTC,[Expired for ubuntu-mate-welcome (Ubuntu) because there has been no activity for 60 days.]
1764024,2018-04-15 00:12:09 UTC,does not recognize existing os windows 10 on uefi bios setting as am trying to install ubuntu mate version 17.10.15 on legacy setting not uefi
1764024,2018-04-15 00:35:21 UTC,This is more likely to be a bug in os-prober or grub
1764024,2018-05-24 13:43:23 UTC,"The crash is in ubuntu-mate-welcome, not os-prober."
1764024,2019-04-06 11:06:07 UTC,What is /usr/bin/username-welcome? That is not a file shipped by Ubuntu MATE Welcome or Ubuntu MATE.
1764025,2018-04-15 11:10:24 UTC,"Sorry, but it seems like caches settings, even after Network-manager has been restarted.
After system reboot it was fine with that option, so I copied my file configuration back to /etc/NetworkManager/dnsmasq.d, was also fine, but settings from that file did not take effect.
After reboot it stops to resolve any DNS address as per description.
here is my conf file:"
1764039,2018-07-07 11:46:54 UTC,"This is due the assumption that should be only one PCB design at time. There are differences in the render structure between OpenGL and raytracing render, so there is this result."
1764039,2018-07-08 03:34:25 UTC,It indeed seems like it comes from the assumption of having only one contiguous board outline.
1764039,2018-07-07 09:50:52 UTC,Please attach a board file for testing.
1764039,2018-07-11 17:48:32 UTC,I think this has always been this way and the assumption in KiCad is that there is only a single board outline.  I'm guessing the amount of effort to change this would not be trivial but it is something that we can certainly consider.  When anyone would have time to get around to this is unknown.
1764039,2018-07-07 01:43:59 UTC,Could you please test on http://downloads.kicad-pcb.org/osx/testing/kicad-unified-5.0.0-rc3-2.dmg?
1764039,2018-07-07 03:22:29 UTC,Same problem
1764044,2020-06-22 12:38:18 UTC,Thank you for following up with this.
1764044,2020-05-19 12:20:42 UTC,"Rolf,"
1764044,2020-06-21 20:01:28 UTC,"while you can certainly argue that the obsolete key was a configuration issue, I'd find it surprising to see the missing warning about this while silently pretending to be working just fine not to be considered a bug."
1764044,2020-05-17 14:16:12 UTC,"I finally was able to solve this. It turns out, my key was too old and thus kind of disabled as a security measure, I suppose. After creating a new key based off ED25519 and adding the corresponding public key to ~/.ssh/authorized_keys on the server, things are now working again."
1764062,2018-04-25 19:21:50 UTC,"Symbol library tables can be linked so changes to the file formats are unnecessary.  We would have to add some way to keep a list of library tables.  The project file seems like the logical place for this list.  We already have two ""groups"", global and project specific.  I'm not sure how useful more groups would be but it is doable."
1764062,2019-07-24 09:33:42 UTC,"@Wayne what do you mean with ""Symbol library tables can be linked"" and how does this work? Could it be used to solve https://bugs.launchpad.net/kicad/+bug/1756735?"
1764062,2019-07-24 12:23:23 UTC,"@Seppe, the design of the library table code allows any number of library tables to be linked together.  Currently, the UI only supports global and project library tables but any number of library tables could be added."
1764062,2019-07-24 13:17:28 UTC,"I see, but if I understand correctly, a change to the UI would still be required in order to use this."
1764067,2018-04-16 09:37:06 UTC,Ubuntu 18.04 Kernel 4.15 KVM is for guest virtual machine .
1764067,2019-07-30 02:55:12 UTC,"Hello,
do you still seeing this with the latest 4.15 KVM kernel (4.15.0.1039.39)?
Thanks."
1764067,2019-09-28 04:17:30 UTC,[Expired for linux-kvm (Ubuntu) because there has been no activity for 60 days.]
1764075,2018-06-14 09:03:27 UTC,"Former wondershaper user here, ""probably"" hit by #1739086 (I say probably because I get the same errors from the script but I did not bother to actually test if it did anything good or bad to my connection performance)."
1764075,2019-05-12 01:33:57 UTC,Any progress on updating the package?
1764075,2018-06-14 08:29:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764078,2018-04-17 20:31:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764078,2018-04-18 10:58:19 UTC,what can I do to help out with this problem?
1764086,2018-04-16 11:52:09 UTC,Probably it's the same problem explained at:
1764087,2019-07-25 04:31:01 UTC,I forgot all about this bug until the tag of cscc was added.
1764087,2018-05-06 07:22:30 UTC,"Dissapointed by the lack of progress on this bug, I decided to research and experiment more to a point where I am now happy with the way my boot up and shut down processes are working to my satisfaction, albeit not perfect.
You will notice I also raised the bug direct on xorg bug service https://bugs.freedesktop.org/show_bug.cgi?id=106407
and it was the response in there that made me appreciate it was not an xorg bug but that the problem lay elsewhere."
1764087,2018-10-22 08:21:19 UTC,apport information
1764087,2018-10-22 08:21:18 UTC,apport information
1764087,2018-10-22 08:21:16 UTC,apport information
1764087,2018-10-22 08:21:15 UTC,apport information
1764087,2018-10-22 08:15:39 UTC,"I need to update this bug.  Since raising the bug, the machine has been updated to Ubuntu 18.04 but still has some issues.
Please cross reference with bug https://bugs.launchpad.net/bugs/1766974
The grub file remains the same:-
GRUB_CMDLINE_LINUX_DEFAULT=""quiet nomodeset""
which results in lots of scrolling messages which I am happy to put up with.
The nain issue is the often errors of:-
 intel ips 0000:00:1f.6: failed to disable graphics turbo
during boot and shutdown.  This app arrantly is on +pci:0000:00:1f.6  and I gather is occurring 100s of time in the background."
1764087,2018-10-08 15:53:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764087,2018-05-05 09:19:34 UTC,"Cross reference now to a lightdm bug which has been raised as a consequence of
https://bugs.freedesktop.org/show_bug.cgi?id=106407
saying it is not a xorg bug"
1764087,2018-09-14 07:30:07 UTC,This change was made by a bot.
1764087,2018-04-25 06:35:05 UTC,"Hello Chris,
Writing to you direct rather than through the bug - hope you don't mind.
I too had my first failure today using the new kernel, manifesting itself
in the same way.
It's getting a bit tiresome now and I have little faith in it being
corrected. I have spent quite a bit of time researching the issue and
trying a few things out to no avail. There are other things needing my
attention just now.
So, it was always in my plans to install 18.04 LTS at some stage.  Rather
than do a fresh install of 16.04 LTS which I had thought was a way of
hopefully overcoming the problem, I may as well go for 18.04 LTS.
I just need to plan things out so that I manage to safely backup my
documents and all my settings (I have very low vision and my settings are
important to me). The planning and preparation in itself will take some
time.
When I get round to it I will let you know how things go.
Best Regards
Dave"
1764087,2018-04-25 18:29:16 UTC,Needs cross-referencing to this bug https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1766307
1764087,2018-04-22 20:40:46 UTC,This sounds like the error that I'm getting. I did a system update on 19th April. Ubuntu 16.04. Lenovo T61. Is display info (see below) relevant to the bug?
1764087,2018-04-22 22:52:11 UTC,Thanks for the workaround to make wifi work - that could come in useful.
1764087,2018-04-23 08:48:47 UTC,This might be the same bug as #1764445
1764087,2018-04-21 10:46:32 UTC,"I can see warnings and errors, but have no idea what to do to fix."
1764087,2018-04-24 08:35:24 UTC,"Now this is interesting!
As part Ubuntu updates the kernel was updated on 23rd April 2018 to 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1764087,2018-04-24 21:29:43 UTC,"Hi Dave, I'm using the new kernel (4.13.0-39-generic) and I still get the error (though my laptop did start up once without the error)."
1764087,2018-04-23 15:55:11 UTC,"You could well be right Chris that https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764445 raise one day later appears to be having the same effect, although the ubuntu version, and the architecture is different."
1764089,2018-04-15 10:27:04 UTC,"attachment is generated by the nvidia-bug-reporting tool, which collects many logs"
1764106,2018-05-01 14:48:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764106,2019-01-10 09:16:18 UTC,Same happened on Xenial (16.04) with hw enablement.
1764111,2020-06-27 18:30:45 UTC,This bug was fixed in the package gnome-shell-extension-autohidetopbar - 20200627-1
1764116,2018-04-17 15:41:35 UTC,"I can confirm that I have the same problem on my installation of Xubuntu 18.04, fully updated but installed originally in mid November 2017."
1764116,2018-04-17 00:26:12 UTC,Reported upstream: https://github.com/mate-desktop/engrampa/issues/200
1764116,2018-04-17 15:31:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764116,2018-04-16 22:32:25 UTC,"Also able to reproduce this using ubuntu mate 18.04
cdimage.ubuntu.com/ubuntu-mate/daily-live/current/bionic-desktop-amd64.isobionic-desktop-amd64.iso	2018-04-16 03:21"
1764116,2018-04-15 13:35:08 UTC,Also happens when making 7z files
1764116,2018-04-15 13:52:55 UTC,"Looks to be a permissions issue (works when running thunar as root), i guess it is using the read only origin to store temp file when it should use the destination for that"
1764116,2018-04-15 20:08:58 UTC,"my last post was correct
when compressing a large amount of data into a z7 file it created a .tz.tmp file in the file origin folder instead of the destination"
1764127,2019-04-17 06:33:20 UTC,"Hello Johannes,
do you still have this issue with the latest kernel in 18.04?
Thanks."
1764127,2019-04-18 06:21:00 UTC,Hello Po-Hsu Lin
1764127,2019-04-18 06:24:16 UTC,Hello Po-Hsu Lin
1764127,2019-06-18 04:17:21 UTC,[Expired for linux-signed-hwe-edge (Ubuntu) because there has been no activity for 60 days.]
1764137,2019-04-29 08:52:13 UTC,"I'm going to close this since the last response from the original reporter was a year ago, and it was that the problem could not be reproduced."
1764137,2018-05-15 17:11:21 UTC,"Also, the setup in comment #7 was tested with 4.17-rc4 and 4.17-rc5."
1764137,2019-04-10 08:47:56 UTC,It was long time ago but IIRC after upgrading from Ubuntu 17.10 to 18.04 GDM would try to start on Wayland. With proprietary Nvidia driver it would then fallback to software rendering haence the CPU usage.
1764137,2018-10-24 12:49:15 UTC,Can you confirm the problem is confined to older kernels?
1764137,2018-05-15 17:09:01 UTC,A bit odd that I cannot reproduce this on a fresh 18.04 installation on the same system.
1764137,2018-04-15 22:37:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764137,2018-04-15 16:29:46 UTC,apport information
1764137,2018-04-15 16:29:45 UTC,apport information
1764137,2018-04-15 16:29:44 UTC,apport information
1764137,2018-04-16 03:19:18 UTC,See also bug 1716434.
1764141,2018-04-15 15:22:23 UTC,what it is looks like.
1764141,2018-05-13 18:05:18 UTC,news?
1764142,2018-04-15 23:25:51 UTC,I think juju-gui project tracks their issues in github.
1764152,2018-04-15 16:55:56 UTC,Seemingly one cannot add more than one attachment - my second attachment overwrote the first. Here then is the first.
1764156,2020-07-17 19:29:26 UTC,Thanks for your report!
1764156,2019-06-19 09:52:01 UTC,Still not fixed in latest Ubuntu release.
1764157,2018-04-15 20:20:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1764169,2018-04-19 20:19:23 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1764172,2019-12-01 03:16:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764172,2019-12-02 00:05:26 UTC,"When installing Ubuntu Server using Subiquity (i.e. using the ubuntu-18.04-live-server-amd64.iso installer image), the user is prompted to enter a hostname for the new installation (along with username/password info, etc.)"
1764172,2019-12-02 00:15:35 UTC,Presumably the ideal solution would be for Subiquity to hand off to cloud-init in a manner that really only ran on that very first boot of the new system.
1764172,2019-12-02 00:28:55 UTC,"(In addition to the one mentioned by WirelessMoves, I found several other Ubuntu Forum threads as well as blog posts, etc. which recommend working around this problem by editing the /etc/cloud/cloud.cfg file to set the ""preserve_hostname:"" line's value to ""true"".  However, that approach means there would be a conffile conflict whenever the cloud-init package is upgraded, so a better solution in the long run is probably to create a new file in /etc/cloud/cloud.cfg.d/ with that setting instead.)"
1764172,2019-12-03 10:04:35 UTC,"Ah oops, this one fell through the cracks. Should try to do a quick fix."
1764172,2020-05-07 23:35:01 UTC,"This got fixed quite a while ago I think, apologies for the lack of updates."
1764180,2018-04-17 12:59:04 UTC,I changed the scheduler to from 'cfq' to 'deadline' and I increased to commit times. That seems to have solved the problem for me as today the system did not slow down to almost freeze anymore with the same load.
1764180,2018-04-16 14:58:44 UTC,"Your system sounds like its thrashing due your processes wanting to you more memory than is available in your system.  (BTW, this has nothing to do with e2fsprogs)."
1764180,2018-04-16 15:50:57 UTC,"Hi Theodore,"
1764202,2018-07-10 14:56:20 UTC,"Looks like this bug was incorrectly expired, sorry about that."
1764202,2018-06-18 04:17:31 UTC,[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]
1764202,2018-04-18 11:49:56 UTC,"This problem has been ongoing since I made Ubuntu 18.04 around March.
In Ubuntu 16.04 before that, this problem was not happened."
1764202,2018-04-17 04:53:19 UTC,It looks like this could be a problem with the NVIDIA proprietary driver.
1764219,2018-04-16 02:31:42 UTC,VMI config on the config node.
1764219,2018-04-16 02:32:10 UTC,VMI-Instance IP Config on the config node.
1764220,2018-04-16 10:00:22 UTC,"Since it's a non-invasive feature (+ we're already +1 on it for apt), FFe approved. Please proceed!"
1764220,2018-04-19 22:36:08 UTC,This bug was fixed in the package dpkg - 1.19.0.5ubuntu2
1764236,2018-04-21 16:02:40 UTC,"Hi @Ji.Wei,"
1764236,2018-08-09 07:14:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/590140"
1764246,2019-10-01 01:48:19 UTC,"I had two up-to-date Azure instances (16.04 and 18.04) where Linux-crashdump was installed. Both failed, with the following being shown at the end of the serial console:"
1764246,2019-01-30 16:19:23 UTC,"OK, so it seems it's really the minimum of reserved memory kernel needs in Bionic that is affecting
the success of kdump here.
Thanks for the report Gaëtan"
1764246,2019-01-30 16:13:33 UTC,By increasing the size reserved to 256MB it's working.
1764246,2019-01-30 16:01:55 UTC,I got the same behavior on Xenial with kernel 4.15.0-43-generic.
1764246,2018-10-25 18:34:53 UTC,"The OOM seems to be happening during initrd decompression. That has been observed before and also in Cosmic. I want to reduce the initrd footprint in case framebuffer drivers are included, which might happen when cryptsetup or plymouth are installed."
1764246,2018-09-27 02:07:53 UTC,A console screen when I triggered.
1764246,2018-09-27 02:01:02 UTC,kdump is not still working on 18.04.
1764246,2018-06-03 08:36:21 UTC,i also see the kdump cannot work on 18.04
1764246,2018-04-16 04:30:07 UTC,This change was made by a bot.
1764246,2018-09-27 21:30:48 UTC,"I tried here with a Bionic VM (kernel 4.15.0-34) and kdump worked fine, using the default
config (128M reserved for the crash kernel)."
1764247,2018-12-30 02:20:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764252,2018-04-26 03:33:45 UTC,"Hello,"
1764259,2018-04-16 07:25:49 UTC,You are right. The fix will probably need to be in the python-openstackclient code.
1764259,2018-04-16 07:02:40 UTC,"I didn't check it locally but from Your description it looks like it's bug in OpenStack Client, not in Neutron. If neutronclient displays proper error message, it means IMO that neutron returns proper info via REST API."
1764259,2018-09-28 17:34:23 UTC,Also encountered this problem while trying to set values on a router.  Running the command:
1764264,2018-05-25 20:18:01 UTC,"This bug is believed to be fixed in cloud-init (Ubuntu) in version 18.2-27-g6ef92c98-0ubuntu1~18.04.1. If this is still a problem for you, please make a comment and set the state back to New"
1764264,2018-04-19 03:32:36 UTC,"We can certainly change our assumption that all entries are a single
script, and instead break it up into each entry in the list is an
independent script.
However, that does make quoting, etc, a bit trickier. Coupled with things
like ""python inside bash inside a string inside yaml"" it gets...
interesting."
1764264,2019-10-31 04:03:31 UTC,Removing form milestone to let the report expire.
1764264,2018-06-20 18:06:49 UTC,"This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New"
1764264,2018-04-19 02:37:08 UTC,An upstream commit landed for this bug.
1764264,2018-04-18 19:32:52 UTC,"The issue with runcmd and bootcmd is confirmed. you're right there.
but in your log, you have an error (probably to /var/log/cloud-init-output.log) for your apt configure module that is fatal."
1764264,2018-04-16 11:37:28 UTC,"As near as I can tell, the cloud-init lines:
2018-04-16 07:14:36,809 - util.py[WARNING]: Running module apt-configure (<module 'cloudinit.config.cc_apt_configure' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_apt_configure.py'>) failed
2018-04-16 07:14:37,036 - schema.py[WARNING]: Invalid config:
..."
1764264,2018-04-16 08:46:24 UTC,"Note that after running, things seem to have actually worked, but ""systemctl list-units"" seems to say that cloud-init is flagged as failed."
1764264,2018-04-16 06:13:52 UTC,"I think for Juju this is a case where we do different setup on MAAS than on LXD. Specifically w/ the same 2.3.6 and LXD I see:
Cloud-init v. 18.2 running 'modules:config' at Mon, 16 Apr 2018 06:11:54 +0000. Up 16.00 seconds.
+ install -D -m 644 /dev/null /etc/systemd/system/juju-clean-shutdown.service
+ printf %s\n
[Unit]
Description=Stop all network interfaces on shutdown
DefaultDependencies=false
After=final.target"
1764264,2018-04-19 02:09:23 UTC,"on a mostly unrelated note, you're kind of relying on an implementation detail of cloud-init's runcmd behavior.
runcmd: ['set -xe', ""mkdir -p '/var/lib/juju'\ncat > '/var/lib/juju/MAASmachine.txt' << 'EOF'\n'hostname: nuc7\n'\nEOF\nchmod 0755 '/var/lib/juju/MAASmachine.txt'"", 'set -xe', ..]"
1764269,2019-09-30 21:33:08 UTC,"Another situation where the ""generated object list"" returns empty is when a large number of volume backup deletes are performed.  For example (this is an extreme, but possible, example that I tested), when 1,000 commands such as:"
1764269,2018-04-20 09:23:35 UTC,"Hi,
I have tried to reproduce this issue on latest release but not able to validate.
May be it's already fixed on latest but I am not sure about it. Also delete() function has changed to delete_backup() in latest release(Rocky).
Please suggest the conclusion pointer to verify the bug because ""cinder backup-list"" showing blank data and I am considering it has deleting/erasing completely."
1764269,2019-09-30 19:33:39 UTC,"We're using Kolla-Ansible deployed Rocky (7.0.2) with Swift as the backup driver.  We use Swift emulation on Ceph, not native Swift.  Backups work fine, so communication with the Swift emulation layer is working.  Backups are stored in the respective project's volumebackups container (chunks, metadata, and sha256file files)."
1764269,2019-09-30 20:18:54 UTC,"Just a quick update - I was able to deploy the ""swift_proxy_server"" container using Kolla Ansible, with some hacking, and once this was running, the volume backup delete function worked as expected."
1764269,2019-10-09 19:54:51 UTC,We have finished our upgrades to Stein and the problem still exists.
1764281,2020-02-26 22:34:41 UTC,Marking as Won't Fix for 2.3 series since we are not planning to make any further releases in this series at this stage.
1764311,2018-11-18 10:49:35 UTC,"Same problem: Dolphin sftp session open 12 hours (in a laptop, suspending between worktimes). I end with several sftp.so processes with high CPU use."
1764311,2018-06-08 19:28:27 UTC,"I'm using KDE on Arch Linux, but I'm also experiencing the exact same situation, and have been for months.  I tend to leave my systems running 24/7 and often notice one or more sftp.so processes in top taking up significant CPU resources.  I did notice the CPU usage is worse when my Dolphin sftp sessions are unable to connect to their target host (I use a VPN to connect to some of the hosts, which I don't leave running all the time, while the respective Dolphin window remains open).  Often CPU usage is reduced (although still not 0) once I reactivate the VPN."
1764311,2018-06-08 19:33:47 UTC,"I should also mention that I tend to kill the sftp.so processes with signal 15 when they act up, and they seem to eventually respawn on their own, but I'm not sure whether that is by system restart or something else (I haven't tracked it in that much detail)."
1764311,2018-06-08 19:22:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764314,2018-11-13 06:48:25 UTC,"As we demoted netcf and it doesn't work we can drop the further netcf tasks in Ubuntu in Won't Fix.
It is not that important to Ubuntu to have it working as discussed before it would a) pull in ifupdown and suggest it is well supported (which it is no more)."
1764314,2018-05-04 08:00:57 UTC,"Thanks Cyphermox for co-testign this with me.
Here an example of his better interface overview now:"
1764314,2018-05-11 05:25:19 UTC,"There already was an upload ongoing, but I need to group bug 1758037 on the same run and need to set new branches. ... Integrated that now.
Regression- and Case-Tested once more from a ppa and being good.
Uploaded to Cosmic - and it already completed.
Also pushed to ubuntu libvirt-maintainers git."
1764314,2018-05-09 17:36:37 UTC,This bug was fixed in the package libvirt - 4.0.0-1ubuntu10
1764314,2018-05-08 14:32:09 UTC,"Filed a bug in Debian for the netcf Dependency going forward, linked at the bug tasks."
1764314,2018-05-08 14:20:33 UTC,"We had a discussion on this:
I have to beg your pardon for all of the Ubuntu community, but we never intended to support write-managing through libvirt in Bionic. Libvirt iface-* never supported networkd or NetworkManager. To manage networks with different backends there is netplan.io."
1764314,2018-05-04 18:03:10 UTC,"Hi rbasak,
almost right - just missing a slight twist.
Yes to all you said until ""leaving the situation as-is for stable releases is appropriate since use case 1 above is far less serious than a potential regression in use case 3."""
1764314,2018-05-04 15:33:21 UTC,"> This implementation is based on ENI as network_interfaces_path is essentially
> static const char *const network_interfaces_path = ""/files/etc/network/interfaces""
"
1764314,2018-05-03 14:57:54 UTC,For me the main problem is the fact that the dialog in virt-manager is misleading.
1764314,2018-05-03 08:52:43 UTC,"Hi,
after sleeping once about this to sort my thoughts I have this morning revisited most of the code."
1764314,2018-05-03 14:00:07 UTC,I tried to select an interface in virt-manager and the desired interface didn't show in the pop-up menu. But it's true that the name can be entered in the free-form dialog. But I think that for virt-manager it makes sense to offer a complete view of the network _or_ a statement informing of the shortcoming.
1764314,2018-05-03 13:42:55 UTC,"Networks are configured through net-* commands (and respective APIs) and they all work.
This is what is commonly used by libvirt users and solutions depending on libvirt."
1764314,2018-05-03 13:11:39 UTC,"Note: easiest test without compiling is likely
$ apt install netcf
$ netcftool list
..."
1764314,2018-05-03 14:38:28 UTC,"Thanks for your reply Nicolas, so even for you if udev backend would work it would be preferred (full view of the network)."
1764314,2018-05-02 12:24:34 UTC,"This didn't fully work even pre netplan, in fact it is separate.
On my partially E/N/I partially NetworkManager system only the former are accessible to netcf.
So this functionality from libvirts POV was reduced for quite a while."
1764314,2018-05-02 10:00:57 UTC,It is sometimes surprising what extra features libvirt all has - I haven't touched this for all the time working with it - Feature of 2009 it seems :-)
1764314,2018-04-30 17:14:52 UTC,"For what is worth, I get nothing listed on my 18.04 laptop, where I use libvirt extensively:"
1764318,2019-09-15 15:25:27 UTC,Migrated to https://github.com/widelands/widelands/issues/3263
1764319,2018-04-19 20:12:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1764319,2018-04-19 20:14:09 UTC,It looks like your kernel has multiple oopses in the dmesg log. This is likely the cause of the dkg failure.
1764320,2018-04-18 08:37:08 UTC,apport information
1764320,2018-04-18 08:37:09 UTC,apport information
1764320,2018-04-18 08:37:11 UTC,apport information
1764320,2018-04-18 08:37:07 UTC,apport information
1764320,2018-04-18 08:37:13 UTC,apport information
1764320,2018-04-18 08:37:14 UTC,apport information
1764320,2018-04-18 10:48:07 UTC,This bug was fixed in the package thermald - 1.7.0-5
1764320,2018-04-18 14:14:29 UTC,"Tested on my machine using http://launchpadlibrarian.net/366148394/thermald_1.7.0-5_amd64.deb, working fine!"
1764320,2018-04-16 09:05:56 UTC,Are you able to boot into a previous non-4.15 kernel and repeat the steps in message #1?
1764320,2018-04-20 01:22:42 UTC,"Thanks Ben for spotting the bug and for the fix, I'm uploading that to Debian right now and will sync it into Ubuntu as soon as it is ready for syncing. Much appreciated."
1764320,2018-04-20 01:36:06 UTC,"Thanks, Colin. I will test it as soon as I can."
1764320,2018-04-20 02:32:11 UTC,"Confirmed fixed in Debian 1.7.0-6 (amd64 from incoming). Thanks, Colin."
1764320,2018-04-20 04:55:38 UTC,"I tried restarting thermald (1.7.0-5) at least 10 times, and the system always see the same broken sensor, the same as in 1.7.0-4 and the same as in 1.7.0-6."
1764320,2018-04-20 07:23:26 UTC,I'm tracking the fix in Ubuntu with bug report 1765572
1764320,2018-04-18 08:37:06 UTC,apport information
1764320,2019-08-15 17:48:33 UTC,The bionic SRU test message occurred because I accidentally uploaded the package with the entire old history.  This bug has already been fixed and the verification for bionic can be ignored.
1764320,2018-04-20 00:34:25 UTC,"@swid by ""working fine!"" do you just mean that the log entries are gone, or do you mean that thermald still works properly, including controlling temperature?"
1764320,2018-04-18 08:37:04 UTC,apport information
1764320,2018-04-16 08:44:42 UTC,Can you run the following and report back the output:
1764320,2018-04-18 08:37:01 UTC,apport information
1764320,2018-04-18 08:37:03 UTC,apport information
1764320,2018-04-16 09:52:37 UTC,And with the 4.15 kernel can you run the following and report back the output:
1764320,2018-04-16 11:37:00 UTC,"With 4.14 :
cat /sys/class/thermal/thermal_zone4/type
B0D4"
1764320,2018-04-17 11:20:03 UTC,"I believe the iwlwifi driver is providing a iwlwifi-virtual-0 thermal zone but the temperature information cannot be read, hence thermald can't read this and produces the warning.  However, it was my expectation that thermald should disable reading this and hence you shouldn't see many of these warnings appear."
1764320,2018-04-17 11:56:40 UTC,"Ah, I'm mistaken, that gets loaded later.  Do you mind supplying the list of modules loaded on your machine so I can see if I can find the driver that is failing on the thermal zone 4.  Can you run:"
1764320,2018-04-17 15:36:10 UTC,"On Tue, 2018-04-17 at 11:56 +0000, Colin Ian King wrote:

> Ah, I'm mistaken, that gets loaded later.  Do you mind supplying the
> list of modules loaded on your machine so I can see if I can find the
> driver that is failing on the thermal zone 4.  Can you run:
>
> lsmod
>


I am thinking wifi. If this is it, then I will do something for this."
1764320,2018-04-16 08:53:08 UTC,"Sure, here are the outputs:"
1764320,2018-04-18 08:16:05 UTC,I'm adding a small change to thermald so it does not continually spam the log.
1764320,2018-04-18 08:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1764320,2018-04-18 08:36:55 UTC,apport information
1764320,2018-04-18 08:36:57 UTC,apport information
1764320,2018-04-18 08:36:59 UTC,apport information
1764320,2018-04-18 04:50:28 UTC,"lsmod
Module                  Size  Used by
ax88179_178a           24576  0
usbnet                 45056  1 ax88179_178a
mii                    16384  2 usbnet,ax88179_178a
rfcomm                 77824  16
ccm                    20480  6
ebtable_filter         16384  0
ebtables               32768  1 ebtable_filter
devlink                45056  0
ip6table_filter        16384  0
ip6_tables             28672  1 ip6table_filter
iptable_filter         16384  0
cmac                   16384  1
bnep                   20480  2
hid_multitouch         20480  0
snd_hda_codec_hdmi     49152  1
snd_soc_skl            90112  0
snd_soc_skl_ipc        65536  1 snd_soc_skl
arc4                   16384  2
snd_hda_ext_core       24576  1 snd_soc_skl
snd_soc_sst_dsp        32768  1 snd_soc_skl_ipc
snd_hda_codec_realtek   102400  1
nls_iso8859_1          16384  1
snd_soc_sst_ipc        16384  1 snd_soc_skl_ipc
snd_soc_acpi           16384  1 snd_soc_skl
snd_hda_codec_generic    73728  1 snd_hda_codec_realtek
snd_soc_core          241664  1 snd_soc_skl
snd_compress           20480  1 snd_soc_core
ac97_bus               16384  1 snd_soc_core
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_hda_intel          40960  3
snd_hda_codec         126976  4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core           81920  7 snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hwdep              20480  1 snd_hda_codec
snd_pcm                98304  8 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core
intel_rapl             20480  0
iwlmvm                364544  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             204800  0
mac80211              778240  1 iwlmvm
kvm                   593920  1 kvm_intel
snd_seq_midi           16384  0
snd_seq_midi_event     16384  1 snd_seq_midi
snd_rawmidi            32768  1 snd_seq_midi
irqbypass              16384  1 kvm
uvcvideo               86016  0
intel_cstate           20480  0
iwlwifi               278528  1 iwlmvm
snd_seq                65536  2 snd_seq_midi_event,snd_seq_midi
intel_rapl_perf        16384  0
input_leds             16384  0
videobuf2_vmalloc      16384  1 uvcvideo
snd_seq_device         16384  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer              32768  2 snd_seq,snd_pcm
videobuf2_memops       16384  1 videobuf2_vmalloc
btusb                  45056  0
joydev                 24576  0
videobuf2_v4l2         24576  1 uvcvideo
btrtl                  16384  1 btusb
serio_raw              16384  0
snd                    81920  19 snd_compress,snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_soc_core,snd_pcm
hp_wmi                 16384  0
videobuf2_core         40960  2 uvcvideo,videobuf2_v4l2
btbcm                  16384  1 btusb
cfg80211              622592  3 iwlmvm,iwlwifi,mac80211
intel_wmi_thunderbolt    16384  0
idma64                 20480  0
wmi_bmof               1..."
1764320,2018-04-18 08:36:59 UTC,apport information
1764322,2019-09-20 07:35:25 UTC,AFAIK MAAS still doesn't offer that feature.
1764322,2019-09-19 15:12:47 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1764322,2018-04-18 23:35:50 UTC,You can do this with the CLI using the set-owner-data command
1764327,2018-04-16 08:34:27 UTC,The current autopkgtest of gdnsd probably needs to be badtested too.
1764327,2018-04-16 16:52:11 UTC,It is not reasonable for gdnsd to cause degradation of the system's local resolver when installed; we should therefore not ship a config snippet that overrides systemd-resolved behavior.
1764337,2018-07-26 15:57:00 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1764337,2018-08-09 01:16:24 UTC,"yes, please"
1764337,2018-10-26 05:42:55 UTC,"seems 19.04 will still use xen-4.9, therefore  move it into 19.10"
1764337,2019-09-11 16:06:08 UTC,duplicated with LP#1735480
1764338,2018-04-16 09:10:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764343,2018-08-09 00:53:38 UTC,"yes, you can. Thanks"
1764343,2018-05-01 09:46:56 UTC,ef8423022324
1764343,2018-07-26 15:56:37 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1764349,2018-09-27 22:15:39 UTC,Also affects s3api.
1764349,2018-04-16 09:34:04 UTC,"After _header_strip the header contains only non-printable, it returns None, and None can't split."
1764357,2018-04-16 14:56:37 UTC,"For the remaining issue #3 - on Chrony remove we know that:
1. no other time server is there anymore (due to conflicts)
2. we are going away"
1764357,2018-04-16 15:07:44 UTC,Test PPA (for #3) building in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3242
1764357,2018-04-16 14:14:30 UTC,"Added the related Debian bug I opened.
Also renamed as (for now) here we only address #3 of the issues described."
1764357,2018-04-20 01:40:45 UTC,This bug was fixed in the package chrony - 3.2-4ubuntu4
1764357,2018-04-19 10:48:29 UTC,Fix uploaded to bionic-unapproved in 3.2-4ubuntu4
1764357,2018-04-16 14:02:07 UTC,"#2 here some theory by smoser (thanks)
http://paste.ubuntu.com/p/6JDQ9ycJhw/"
1764357,2018-04-16 11:18:08 UTC,Lets break this into use cases in Bionic:
1764357,2018-04-16 13:05:36 UTC,Linked the upstream discussion on the determinism of conflicting services.
1764357,2018-04-16 13:04:41 UTC,Several insights on all of this:
1764357,2018-04-16 13:04:25 UTC,"Status right now:
ok   - 0. systemd-timesyncd"
1764357,2018-04-16 13:22:21 UTC,"#1 is solved by the package conflicts
#2 might be solved by very suble wording in systemd
#3 might be low prio as it was never different"
1764358,2018-07-26 15:56:02 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1764358,2018-08-07 10:33:07 UTC,"Yes, can be public. Thanks"
1764363,2018-11-23 09:41:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764363,2018-11-23 09:52:55 UTC,"I have the same behavior.
Sometimes when I click ""Update All"" nothing happens.
Sometimes it works."
1764365,2018-05-11 20:45:59 UTC,"OK, so the behaviour you want implemented:"
1764365,2018-04-23 10:55:42 UTC,"In 2014, I wrote error design guidelines for Ubuntu app developers. The relevant part of those guidelines was that when an error occurs, it should be described “as close as possible to the place where it occurred, and as soon as possible after it occurred, without being distracting”. <https://goo.gl/gEzmut> The password shortness message achieves the goal of being as close as possible to the place where the error occurred. Unfortunately, it misses the other two."
1764365,2018-05-15 13:03:43 UTC,"Yes, that sounds correct, thank you."
1764365,2018-04-17 18:18:45 UTC,"This would require some changes to our password-meter implementation (a YUI-based widget), which triggers a strength check on each key input/focus/blur event of the textbox."
1764365,2018-04-17 19:02:08 UTC,"The message appears as soon as I start typing and is accurate; the password so far is too short. It only goes away once I've typed enough characters, which is very immediate feedback."
1764366,2020-01-31 20:20:43 UTC,"ENGLISH
Thanks for your bug report. A few comments:"
1764366,2020-04-01 04:17:35 UTC,[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1764368,2018-04-16 21:26:35 UTC,"Hi,"
1764369,2018-04-16 10:05:40 UTC,"since pike, this is fixed by https://review.openstack.org/#/c/413861/, so this issue only happens on ocata branch."
1764369,2018-04-16 10:09:54 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/561573"
1764369,2018-05-22 16:23:46 UTC,"Reviewed:  https://review.openstack.org/561573
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=67b092ead7bd3395a8e0b71abdf20710de2c78dd
Submitter: Zuul
Branch:    stable/ocata"
1764369,2018-07-24 02:48:47 UTC,This issue was fixed in the openstack/kolla 4.0.5 release.
1764375,2019-02-05 07:25:36 UTC,It work fine with new Service_client class but yes conf option is not being passed from old manager class and from admin cred etc from dynamic cred class.
1764375,2019-07-12 19:42:38 UTC,"Change abandoned by Federico Ressi (<email address hidden>) on branch: master
Review: https://review.opendev.org/559069"
1764375,2021-01-08 16:20:27 UTC,"The old manager (which doesn't the mentioned option) is being removed by
https://review.opendev.org/c/openstack/tempest/+/767628
because it has been deprecated for several years and it has been superseded by tempest.lib.services.clients.ServiceClients class where the mentioned option can be passed through.
Therefore I'm gonna mark this as not valid. Feel free to reopen if you feel otherwise."
1764382,2018-04-16 11:40:25 UTC,"Review in progress for https://review.opencontrail.org/41950
Submitter: Ankit Jain (<email address hidden>)"
1764391,2019-10-04 11:25:59 UTC,This is fixed since Marco 1.22.3-0ubuntu1 in Ubuntu MATE 19.10.
1764392,2018-04-16 12:52:17 UTC,There is an ML post asking about the support of the whole bandwidth usage codepath in the xenapi driver. http://lists.openstack.org/pipermail/openstack-dev/2018-April/129397.html
1764393,2018-07-28 02:11:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764393,2018-04-16 12:40:21 UTC,"StacktraceTop:
 gtk_widget_get_mapped (widget=widget@entry=0xac85858577818181) at ../../../../gtk/gtkwidget.c:9241
 gtk_widget_should_animate (widget=0xac85858577818181) at ../../../../gtk/gtkscrolledwindow.c:4110
 indicator_start_fade (indicator=0x562105762298, target=<optimized out>) at ../../../../gtk/gtkscrolledwindow.c:4264
 maybe_hide_indicator (data=0x562105762298) at ../../../../gtk/gtkscrolledwindow.c:4304
 ?? ()"
1764394,2019-01-08 03:19:51 UTC,There's a bit of code in configure_graylog() that checks to see if CONF_FILE  (/var/snap/graylog/common/server.conf) exists. Maybe we can extend that to also check node_id_file and password_secret are set and exists in that config file.
1764394,2020-03-25 00:54:14 UTC,"Can reliably reproduce this by deploying multiple nodes on ""older"" hardware on a lxd controller. It is a race between the snap saying it is installed and the snap mount(s) actually becoming available. I deploy 3 nodes, and the first one always succeeds, but the other two get stuck."
1764394,2020-03-26 06:03:56 UTC,"Found the root cause in the snap itself. The configuration file does not initially exist in the filesystem, it is created in the service script during startup (via redirection of some potentially expensive operations). That creates a window where the snap has been installed, but the file either does not exists yet, or exists as an empty file while the contents are being generated - leading to the race."
1764406,2018-04-30 08:14:53 UTC,"I wonder if this is a duplicate of bug #1743139. If you run maven with -Djavax.net.ssl.trustStorePassword=changeit, does that successfully work around the problem?"
1764406,2018-05-01 08:51:31 UTC,I encountered the same problem. running maven with - Djavax.net.ssl.trustStorePassword=changeit successfully work around the problem. Thanks Sam Uong!
1764406,2018-05-03 06:00:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764408,2018-04-30 08:35:53 UTC,"To make the issue more clear I adding this info:
this bug effects on Metadata.
When deleting the DHCP port and it doesn't recreate, all instances that we boot would be booted without metadata.
localhost login: root
Password:
[root@localhost ~]# curl http://169.254.169.254/openstack
curl: (7) Failed connect to 169.254.169.254:80; No route to host"
1764408,2020-01-22 13:12:16 UTC,The OVN driver now lives in the neutron repository. Moving this bug to their tracker.
1764414,2018-04-17 01:26:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764414,2018-04-29 12:05:21 UTC,"This is actually a LibreOffice bug. Red Hat’s Caolán is hard at work at improving LO’s integration with Gtk+ in a gradual process he christened “welding”, which you’ll see when we release version 6.1 in August."
1764414,2019-06-27 21:33:54 UTC,"It's still affecting Ambiance in:
Version: 6.2.4.2
Build ID: 1:6.2.4-0ubuntu0.18.04.1~lo1"
1764417,2019-07-21 15:08:52 UTC,"As comment #19, my issue was apparently with Chrome Remote Desktop. After uninstalling it, everything seems to be back and working."
1764417,2019-07-18 14:05:12 UTC,"FWIW, I did not experience this issue until I changed the hardware platform."
1764417,2019-04-18 07:37:14 UTC,"It happen to me just now, grep by ""gnome-session-binary"":"
1764417,2020-10-23 16:55:10 UTC,This seems to have been fixed in Ubuntu 20.04.1 ...
1764417,2019-04-06 08:18:25 UTC,"I too am affected by this bug. I am attaching my syslog because I have unrecoverable failures in multiple components:
org.gnome.Shell.desktop
org.gnome.SettingsDaemon.Sharing.desktop
org.gnome.SettingsDaemon.Color.desktop"
1764417,2019-09-11 16:58:51 UTC,"After updating my Ubuntu, i had to uninstall chrome desktop, it wouldn't let me to open up terminal or files app. Then i re-installed chrome desktop, try it with default settings and it was working, i changed the Display to 0 (20 default) on the python file and comments. It would not let me initiate the remote access this time. It says timeout after 1200000 mili seconds something of that sort. I just think it was worth mentioning it."
1764417,2019-04-10 16:01:37 UTC,"Same, happens once a day"
1764417,2019-09-16 23:36:58 UTC,Getting this on 19.04
1764417,2020-07-08 03:45:20 UTC,"Fix:
If you search your journalctl output and find an event like this:
Jul 07 20:45:20 ubuntu dbus-daemon[1064]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.168' (uid=1000 pid=23634 comm=""/usr/lib/gnome-settings-daemon/gsd-color "" label=""unconfined"")"
1764417,2019-11-29 08:43:22 UTC,"Same bug ('org.gnome.SettingsDaemon.Color.desktop' failed to register) for me, but no NVIDIA card involved :"
1764417,2019-11-30 22:14:39 UTC,"I'm using Ubuntu 18.04 since it came out, but are effected by this bug only since two weeks.
What I noticed: I have a couple of programs setup to start automatically (via gnome-session-properties). When I log in and get kicked out because of this bug, those programs where never started at all. On a normal Login they start fine."
1764417,2020-01-06 09:39:14 UTC,"Very similar issue to the other reports. I see this every few days when I login. Typically I go to Nautilus, mount an encrypted FUSE drive, open Chrome, then randomly the session just dies. Interesting, my dual monitors are reversed so the order of them is wrong (left is on the right, and vice versa). Restarting seems fine."
1764417,2020-01-27 09:09:15 UTC,"Following up on my previous comment, after removing Chrome Remote Desktop three weeks ago I have not had any crashes on login. That old program (which Chrome didn't register as being installed, but was running in the background) seems to be the source of the issue for me."
1764417,2019-04-04 21:45:26 UTC,I had this issue until i uninstalled chrome remote desktop.
1764417,2020-07-08 03:53:16 UTC,"Commenting on my own comment #32 above:
Somehow launchpad decided to break the lines following ""display-manager."". The line breaks should not be there in the diff output."
1764417,2019-11-12 11:58:40 UTC,"Also getting an org.gnome.SettingsDaemon.Color.desktop error using Ubuntu 18.04 with Nvidia graphics card, no Chrome Desktop installed. The Desktop drops into a black screen, with this text:"
1764417,2019-03-07 17:31:38 UTC,"This just happened to me twice as well, after the first reboot after upgrading the kernel to 4.18.0-16-generic. System had been running for a few days (with several reboots) on 4.18.0-15-generic with no issues. After logging in for the second time without rebooting everything is good so far. Attaching the journal up from boot up to the crash moment."
1764417,2019-01-23 10:43:49 UTC,"Here you go. Had this occur twice in a row just now, so my original theory of the second login never failing was false."
1764417,2019-02-09 16:04:22 UTC,I'm struggling with 18.10:  Lots of bad things happen but this is worst: This happens every time more than 2 applications are open.
1764417,2018-04-17 12:53:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764417,2018-07-30 14:17:59 UTC,"I'm seeing this on 18.04 as well, gnome-settings-daemon 3.28.1-0ubuntu1."
1764417,2018-08-29 12:53:42 UTC,"I have similar problem,
Unrecoverable failure in required component org.gnome.Shell.desktop
and
CRITICAL: We failed, but the fail whale is dead. Sorry....
and some Unable to get on D-Bus"
1764417,2018-10-23 19:40:16 UTC,"Just had the same thing happen to me, on recently-updated Ubuntu 18.04."
1764417,2019-01-08 09:38:54 UTC,"Just got the same, shortly after I logged in, I opened VirtualBox (haven't started the VM yet), then Google Chrome -> went to my mails and ... just got logged out of my session!"
1764417,2019-01-16 13:28:30 UTC,"Happens to me as well with the same error. Thought it might be related to the Nvidia driver, but the initial reporter clearly mentions it only started to happen after upgrading to 18.04. Have any of you guys managed to track down the issue or find a workaround?"
1764417,2019-01-16 20:39:15 UTC,Could those having the issue add their journalctl log from the boot which showed the bug? Also comment #6 is about org.gnome.SettingsDaemon.Keyboard.desktop which is a different component (and it looks like xorg got issue and that impacted other components too)
1764417,2019-01-23 14:31:57 UTC,There is not much info in the log :/ Would it be possible to edit org.gnome.SettingsDaemon.Color.desktop to add a --debug to the Exec line and get a log with that next time you hit the issue?
1764417,2019-01-23 15:03:33 UTC,"Sure, I've now set it up thus and will post the results once I hit this again (it seems pretty unpredictable, so could be anything from days to weeks)."
1764417,2019-01-24 08:11:28 UTC,"...except that --debug isn't one of gsd-color's recognized parameters, and adding it caused GDM to fail to start. I changed it to --verbose which is available."
1764417,2019-01-24 09:35:40 UTC,"right, sorry about that, --verbose is the right option indeed"
1764417,2019-02-07 10:36:55 UTC,"A new log; still nothing useful from colord AFAICT, despite the --verbose."
1764417,2019-02-07 13:57:59 UTC,"Indeed, not much outside of
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout"
1764417,2019-02-10 17:21:02 UTC,"I'm seeing similar issue using nvidia card with latest NVIDIA driver update 410.
-----------------------------------------------------------------------
error log:"
1764418,2018-04-19 13:35:29 UTC,"I managed to make SSG (Software Simple Gateway) work. I've noticed from the iptables rules, that the following rule is applied when pinging from inside the VM to outside: DOCKER-ISOLATION."
1764418,2018-04-16 14:14:12 UTC,"Also, my VNC console fron OpenStack GUI blocks after I execute provision_vgw_interface.py script."
1764421,2018-04-18 09:35:10 UTC,"Reviewed:  https://review.openstack.org/561633
Committed: https://git.openstack.org/cgit/openstack/networking-bagpipe/commit/?id=ead407dd5ecaedd522e9db0ffc9c980cb38957ae
Submitter: Zuul
Branch:    master"
1764423,2018-04-19 20:01:55 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1764435,2018-04-16 15:16:44 UTC,"Note: same behavior even after dealing with the ""kept back packages"":"
1764435,2019-05-08 17:55:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764435,2020-05-20 08:43:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1709725, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1764440,2018-04-17 16:11:41 UTC,I believe this is releated to: https://bugs.launchpad.net/maas/+bug/1762461
1764440,2019-09-19 14:47:05 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1764446,2018-04-17 21:01:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/562053"
1764446,2019-08-27 21:32:33 UTC," link to work in progress needs review by people with votes that count
https://review.opendev.org/#/c/562053/"
1764450,2018-08-17 12:26:51 UTC,"I did request the pdftk namespace, so now you do not need pdftk-smoser, but just:"
1764450,2018-08-17 17:20:14 UTC,"There is pdftk-java ( https://launchpad.net/ubuntu/+source/pdftk-java ). It is an port of pdftk to pure java, therefore does no longer depend on gcj. The package provides a ""pdftk"" binary and is planned to be the replacement of the pdftk package. The package from cosmic should be backwards-compatible to 18.04."
1764450,2020-04-30 19:49:57 UTC,"Per comment #24 above, I don't believe libcprov-javapdf is currently installable, but it worked for me after replacing the first line with"
1764450,2019-03-19 23:55:05 UTC,*** This is an automated message ***
1764450,2019-03-24 13:14:39 UTC,Ubuntu Disco has now (again) pdftk 2.02-5 [1] as a pure transition package to pdftk-java [2].
1764450,2019-07-20 11:09:34 UTC,"Just FYI, the issue for backporting of pdftk-java to bionic has been reported here:"
1764450,2019-05-04 17:09:49 UTC,"Thanks for your suggestion to backport pdftk-java, Ibrahim Awwal. Please follow the procedure described on [1]."
1764450,2019-05-18 05:43:19 UTC,"On 15/5/19 6:34 pm, Dylan Aïssi wrote:

> ** Also affects: pdftk (Ubuntu Bionic)
>     Importance: Undecided
>         Status: New
>
> ** Changed in: pdftk (Ubuntu)
>         Status: Confirmed => Fix Released
"
1764450,2019-07-08 13:33:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764450,2020-03-06 18:26:18 UTC,The workaround that's working now (as Comment #4 doesn't work anymore) in 18.04 is
1764450,2019-04-29 22:23:00 UTC,"Is it possible to backport the fixed version (pdftk-java) to Bionic? If people are on the LTS release, having it available in Cosmic or Disco does not really help. It seems like it's possible to just install the Cosmic package on 18.04 but it'd be nice to not have to go that route. Thanks!"
1764450,2018-07-12 14:26:22 UTC,It seems nobody has contacted upstream so far and asked to fix this issue so I did this now and will see what happens. I guess the alternative would be just to wait until a fork makes it into the repositories or just to switch to another application that does a similar job.
1764450,2018-11-30 06:53:13 UTC,@scott moser thanks a lot for the snap! This tool is really missing in the normal repository :/
1764450,2018-07-08 16:07:01 UTC,You can find more solution on https://askubuntu.com/questions/1028522/how-can-i-install-pdftk-in-ubuntu-18-04-bionic
1764450,2018-07-10 21:33:29 UTC,To extend what @6-launchpad-net-cefn-com mentioned in Comment #7 I had to not only install gcc-6-base but also python. I ran
1764450,2018-04-17 17:58:56 UTC,Thanks for reporting.
1764450,2018-04-28 09:47:22 UTC,"An effective workaround is to build Marc Vinyal's fork as described by David Foerster here
https://askubuntu.com/questions/1028522/how-can-i-install-pdftk-in-ubuntu-18-04-bionic-shell-version-no-gtk and then wrap the jar file into an executable called ""pdftk"" using the lovely trick described here https://coderwall.com/p/ssuaxa/how-to-make-a-jar-file-linux-executable. This works perfectly for me and could point the way to a maintainable way forward for pdftk under Ubuntu. Maybe somebody who understands packaging could create a deb with the right dependencies, and put it on a repository somewhere?"
1764450,2018-05-02 18:33:48 UTC,Quick and easy workaround:
1764450,2018-05-04 15:56:42 UTC,I have posted about this issue and the current possible solutions here and elsewhere at https://linuxatty.wordpress.com/2018/05/04/xubuntu-18-04-bionic-beaver-released/.
1764450,2018-04-16 20:44:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764450,2018-06-06 18:07:25 UTC,I also needed to add
1764450,2018-06-21 17:40:57 UTC,"Felix's workaround worked.
Thank you."
1764450,2018-06-25 22:28:01 UTC,Confirmed: Bug & Felix' workaround (thank you!)
1764450,2018-07-08 15:00:12 UTC,See also the removal action from 18.04 here: https://bugs.launchpad.net/ubuntu/+source/pdftk/+bug/1757314
1764450,2018-05-07 14:14:40 UTC,"Felix's workaround works fine for me, even though it's a temporary solution, of course.
Thanks!
Michael"
1764458,2018-10-22 06:51:19 UTC,This bug is still present in Ubuntu 18.04.
1764459,2018-05-16 16:53:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764459,2018-04-16 16:57:06 UTC,Please treat me as a total newb if you need further information.
1764459,2018-04-23 14:45:26 UTC,hello?
1764459,2018-04-23 15:01:10 UTC,"Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker."
1764459,2018-04-23 16:16:35 UTC,This is absolutely a bug. System went from working to non-bootable without any user interference.
1764459,2018-04-28 23:24:52 UTC,"Definately a bug in there somewhere: on my system I can login, but when the screensaver kicks in the X session collapses, the screen is blank but when a key is touched it is full of these APCI messages.  Hitting return causes the X session to restart back to the initial login screen."
1764459,2019-05-11 13:39:55 UTC,I am also experiencing this issue.  Ubuntu locks up and then on a reboot I get the message:
1764460,2018-06-01 08:19:34 UTC,"For some reason, the git hook didn't close the LP bug but see, the upstream change is merged : https://review.openstack.org/#/c/564257/"
1764460,2018-06-08 12:25:32 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1764460,2018-05-15 04:04:10 UTC,This issue was fixed in the openstack/nova 17.0.4 release.
1764460,2018-04-26 13:59:16 UTC,"Reviewed:  https://review.openstack.org/564454
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a5aa8e2eb8d5a90780211ef67b8f2dcc76af64de
Submitter: Zuul
Branch:    stable/queens"
1764460,2018-04-25 15:37:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564257"
1764460,2018-04-18 02:36:31 UTC,"Confirmed, This is a pretty big bug that occurs quite often in large openstack setups"
1764460,2018-04-26 10:30:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/564454"
1764461,2018-04-16 17:10:18 UTC,"StacktraceTop:
 beroot (argc=0, argv=0x7ffcced65410) at zfuncs.cc:486
 main (argc=<optimized out>, argv=<optimized out>) at dkopp-6.5.cc:344"
1764461,2018-05-01 00:36:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1764461,2019-06-09 17:51:19 UTC,"Seeing the same errors. This app was updated by the developer and source posted on his/her website. See https://kornelix.net/downloads/downloads.html. Everything about this package is out of date, including the link to the developer's website. I download the source and built my own .deb and installed. Can confirm the updated version works fine on Ubuntu 19.04."
1764461,2019-06-09 17:51:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764461,2020-04-17 20:23:50 UTC,"So this bug has been open since 2018. There is a readily available fix, but the Debian maintainer has shown no interest in updating this package to anything that resembles a recent release. I love this software, but frankly this package should be just dropped altogether since Debian seems uninterested in maintaining it."
1764467,2018-04-16 17:35:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764467,2018-12-27 23:20:50 UTC,Is there any progress or something?
1764473,2018-04-17 07:23:21 UTC,"Development moved.
Please file bugs at"
1764476,2021-02-17 17:07:28 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1764489,2018-04-20 13:12:27 UTC,This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.
1764489,2018-04-20 17:13:17 UTC,"Reviewed:  https://review.openstack.org/562078
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=caca71376fbc2c1195cda71608c8d2a70ef9a678
Submitter: Zuul
Branch:    stable/ocata"
1764489,2018-04-19 22:04:41 UTC,"Reviewed:  https://review.openstack.org/562077
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d88b75e81eabfbd463007f6a4f27e6966a466530
Submitter: Zuul
Branch:    stable/pike"
1764489,2018-05-02 12:00:43 UTC,This issue was fixed in the openstack/nova 15.1.1 release.
1764489,2018-04-25 09:21:04 UTC,This issue was fixed in the openstack/nova 16.1.2 release.
1764489,2018-04-19 12:45:28 UTC,"Reviewed:  https://review.openstack.org/562074
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2d50f6e7854543849c4cb7641ae6b88fe04cb6f6
Submitter: Zuul
Branch:    stable/queens"
1764489,2018-04-25 09:23:49 UTC,This issue was fixed in the openstack/nova 17.0.3 release.
1764489,2018-04-17 22:52:32 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/562077"
1764489,2018-04-17 22:46:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/562074"
1764489,2018-04-17 21:16:51 UTC,"Reviewed:  https://review.openstack.org/561704
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=23bd8f62634707fc9896a38ff4dae606c89c6c4b
Submitter: Zuul
Branch:    master"
1764489,2018-04-16 19:35:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/561704"
1764489,2018-04-17 22:53:09 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/562078"
1764515,2018-04-17 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1764521,2018-04-16 20:44:07 UTC,"Although I wasn't installing anything at the time, the crash reporter also popped up saying that a problem occurred while installing libopencore-amrwb0 0.1.3-2.1"
1764521,2018-04-17 07:27:20 UTC,"Have you run memory checks? If everything crashes, it might be a faulty memory module."
1764521,2018-04-17 13:45:59 UTC,I have downloaded Memtest86-7.5.iso but haven't yet got the 40_custom entry correct to launch it via loopback.  I guess I could burn it to USB/CD.
1764522,2018-04-16 23:06:03 UTC,These messages look suspect:
1764522,2018-04-16 23:22:07 UTC,"I've been getting a ton of faults in ld; even after a 'Erase disk and reinstall Ubuntu' from a new live usb.  It's not the only one, of course - just a common one."
1764522,2018-04-17 19:58:45 UTC,"For example, this is from the most recent crash"
1764533,2018-04-25 23:09:43 UTC,Not a duplicate of 1764848 - the errors are regarding not being able to open files.
1764533,2018-10-01 14:07:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764537,2019-01-31 02:02:52 UTC,CONTRAIL_VERSION: 4.1.2
1764537,2018-06-06 07:14:48 UTC,3.10.0-862.el7 is already supported in mainline and R5.0
1764537,2018-06-05 08:16:58 UTC,"Review in progress for https://review.opencontrail.org/43520
Submitter: Kumar Harsh (<email address hidden>)"
1764537,2018-06-01 09:24:27 UTC,"Review in progress for https://review.opencontrail.org/43456
Submitter: Kumar Harsh (<email address hidden>)"
1764537,2018-05-31 08:56:23 UTC,"Review in progress for https://review.opencontrail.org/43424
Submitter: Kumar Harsh (<email address hidden>)"
1764537,2018-06-06 08:10:28 UTC,"Reviewed:  https://review.opencontrail.org/43520
Committed: http://github.com/Juniper/contrail-vrouter/commit/a7e853d0ead01cb7100392bef10f47067d2c959f
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1764537,2018-05-18 12:56:17 UTC,"Reviewed:  https://review.opencontrail.org/43155
Committed: http://github.com/Juniper/contrail-packaging/commit/df6f2ccbde785a824b0af6bffbc2aa878cd4572e
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1764537,2018-05-08 05:55:04 UTC,"Reviewed:  https://review.opencontrail.org/42574
Committed: http://github.com/Juniper/contrail-packaging/commit/16a6c7e0cade8083dabc43efbe8933c22749da56
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1764537,2018-05-09 09:56:41 UTC,"Reviewed:  https://review.opencontrail.org/42557
Committed: http://github.com/Juniper/contrail-packages/commit/4bb14c6333107a5f19d21aa3f6c554939feaeb73
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1764537,2018-05-01 13:43:53 UTC,"Review in progress for https://review.opencontrail.org/42574
Submitter: Kumar Harsh (<email address hidden>)"
1764537,2018-04-29 12:48:10 UTC,"Review in progress for https://review.opencontrail.org/42557
Submitter: Kumar Harsh (<email address hidden>)"
1764537,2018-04-27 06:38:30 UTC,"Review in progress for https://review.opencontrail.org/42574
Submitter: Kumar Harsh (<email address hidden>)"
1764537,2018-04-26 16:55:05 UTC,"Review in progress for https://review.opencontrail.org/42557
Submitter: Kumar Harsh (<email address hidden>)"
1764537,2018-05-18 06:34:37 UTC,"Review in progress for https://review.opencontrail.org/43155
Submitter: Kumar Harsh (<email address hidden>)"
1764545,2018-04-16 22:21:09 UTC,workaround for xenial system with python-openstackclient installed:
1764550,2018-04-16 22:22:15 UTC,"From the credential output:
      domain-name: devops_domain
      project-domain-name: devops_domain
      user-domain-name: devops_domain"
1764550,2018-04-17 11:11:03 UTC,thanks for the work around ...
1764556,2019-07-31 13:57:39 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/673821"
1764556,2019-07-31 14:00:52 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/673824"
1764556,2019-07-31 14:04:31 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/673827"
1764556,2019-07-31 14:20:09 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.opendev.org/673830"
1764556,2019-07-31 14:34:08 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/673833"
1764556,2019-08-07 20:39:37 UTC,"Reviewed:  https://review.opendev.org/673812
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=44709cfb5cfa6a8a384eb391ad520de55b2fa247
Submitter: Zuul
Branch:    stable/stein"
1764556,2019-08-08 01:54:02 UTC,"Reviewed:  https://review.opendev.org/673814
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=11fde850e6163b68e006e746406e6c5e6ac980e0
Submitter: Zuul
Branch:    stable/stein"
1764556,2019-08-12 20:41:00 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1764556,2019-08-09 02:31:36 UTC,"Reviewed:  https://review.opendev.org/673821
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=72f9aa720f9137a35d55b9f96e2220d2d0e5588d
Submitter: Zuul
Branch:    stable/rocky"
1764556,2019-08-09 17:32:37 UTC,"Reviewed:  https://review.opendev.org/673824
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=de035bbfccbfd5a3e7516434171e89e9df7d08fa
Submitter: Zuul
Branch:    stable/queens"
1764556,2019-08-09 17:49:16 UTC,"Reviewed:  https://review.opendev.org/673827
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97e78f8cc194c60d06a37b11c9c09405bf87b295
Submitter: Zuul
Branch:    stable/queens"
1764556,2019-08-12 21:06:46 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1764556,2019-08-19 15:41:06 UTC,This issue was fixed in the openstack/nova 17.0.12 release.
1764556,2019-07-31 13:48:51 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/673816"
1764556,2019-09-27 09:01:30 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1764556,2019-08-08 17:02:48 UTC,"Reviewed:  https://review.opendev.org/673816
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eadd78efe39e1958d14319cfcdbda15862485845
Submitter: Zuul
Branch:    stable/rocky"
1764556,2019-07-31 13:45:04 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/673814"
1764556,2018-06-04 12:08:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572089"
1764556,2019-07-31 08:26:00 UTC,"Reviewed:  https://review.opendev.org/582408
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=16e163053ca39886f11fdb8a3af10a28619fc105
Submitter: Zuul
Branch:    master"
1764556,2018-04-16 23:23:14 UTC,"An additional piece of information....running ""nova show <instance>"" as an admin user causes the service to be updated with a valid UUID, but running it as a regular user does not (presumably because it doesn't show the host information)."
1764556,2018-04-17 18:17:58 UTC,I'm working on a functional recreate test for this.
1764556,2018-04-17 20:51:54 UTC,Looking at https://review.openstack.org/#/q/topic:bug/1764556+(status:open+OR+status:merged) - it appears that https://review.openstack.org/#/c/543970/ does in fact fix the issue.
1764556,2018-04-17 23:21:13 UTC,"Yes, I think you're right.  With that commit applied it appears that the migration back to the original compute node is pulling in the service and updating the UUID on it.  So after the migration when we run ""nova list"" the service has a uuid on it already."
1764556,2018-04-18 16:47:04 UTC,I think we could get into the bad state described in the bug if we do a slightly different series of actions:
1764556,2018-04-18 19:12:53 UTC,So what's the best option here?  Internally it was suggested that we could just modify the online data migration to apply uuids to deleted service records.
1764556,2018-04-19 16:35:01 UTC,"I haven't thought about solutions yet, was spending a large chunk of my time just getting the functional regression recreate test working."
1764556,2018-04-17 20:22:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/562041"
1764556,2018-06-04 12:15:46 UTC,I also faced this problem.
1764556,2018-06-12 08:39:39 UTC,"Change abandoned by Damon Li (<email address hidden>) on branch: master
Review: https://review.openstack.org/572089
Reason: this patch can't fix this bug. Even we ignore the version check, when write service data to db, oslo_db will raise exception ""Service not found"". Seems can't get the deleted service."
1764556,2018-07-12 23:13:45 UTC,Just wanted to add a note that this bug smells like a similar bug:
1764556,2018-07-13 01:35:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/582435"
1764556,2019-07-30 20:09:22 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: master
Review: https://review.opendev.org/582435
Reason: https://review.opendev.org/562041 was preferred"
1764556,2019-07-31 02:00:17 UTC,"Reviewed:  https://review.opendev.org/562041
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=81f05f53d357a546c7f9a53cae6ef45b92e28bc1
Submitter: Zuul
Branch:    master"
1764556,2019-07-31 13:39:23 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/673812"
1764565,2018-04-17 08:32:39 UTC,"Thank you for your bug report, we moved to GitHub ( https://github.com/elementary/appcenter )
Can you reopen an issue there and open AppCenter in gdb as we need more information to understand what is wrong in your system.
The steps to give us more information:
`killall io.elementary.appcenter`
`gdb io.elementary.appcenter` to enter gdb
`run`
make it crash
`bt`
`q` to quit gdb
and copy-paste the output of the `bt` into a new bug report in GitHub.
We might also need to know the name of your locale to verify that it's not a bug on the translations."
1764565,2018-04-17 01:06:13 UTC," I'm sorry I just realized this report is at wrong place, should I repost it, or maybe Admin could help?"
1764566,2020-03-27 21:44:06 UTC,I can confirm that the issue is still present in the 27.03.2020 (EU time format) of the 20.04 iso
1764566,2018-04-16 23:55:47 UTC,"StacktraceTop:
 ?? ()
 brisk_menu_window_filter_section (item=<optimized out>, self=0x55c7301d2290) at ../src/frontend/menu-search.c:74
 brisk_menu_window_filter_apps (self=0x55c7301d2290, child=0x55c7303655a0) at ../src/frontend/menu-search.c:150
 gtk_list_box_apply_filter (box=0x55c730208340, row=0x55c7303b5690) at ../../../../gtk/gtklistbox.c:2261
 gtk_list_box_insert (box=0x55c730208340, child=<optimized out>, position=<optimized out>) at ../../../../gtk/gtklistbox.c:2952"
1764566,2018-09-27 22:46:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764566,2019-06-01 06:33:52 UTC,This still affects Eoan.
1764566,2019-07-09 18:00:28 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1764566,2020-03-10 06:09:40 UTC,Crash occurring on 20.04 Ubuntu MATE with 20200310 ISO.
1764566,2020-03-25 17:30:36 UTC,"daily-live/20200325
i5-4690k"
1764566,2020-03-27 21:52:05 UTC,Why not just delete Brisk menu and make a simpler one?
1764594,2019-07-22 07:05:44 UTC,Since the report was filed we have done great improvements in watchers area and have not seen re-occurrence of this failure. I am marking this as Fix Released.
1764594,2018-04-18 13:02:46 UTC,http://ci.jujucharms.com/job/github-check-merge-juju/951/testReport/junit/github/com_juju_juju_worker_provisioner/TestPackage/
1764595,2020-02-26 15:31:43 UTC,I can still reproduce with GCC 9.2.1 (9-2019-q4-major):
1764595,2020-12-03 14:30:15 UTC,Just checking in for the yearly test. Still present in 10.2.0 ;
1764596,2018-04-17 07:54:39 UTC,"Hi Michael,
  I would be happy for apps to be downgraded to Recommends, if you have a look at the seed[1] alot are already marked recommends (Recommends are the ones marked like ""* (gnome-weather)"". Overall the selection that are marked Recommends is a little inconsistent and this could certainly be cleaned up a bit."
1764596,2018-04-18 00:23:16 UTC,"Hey Tim,"
1764596,2018-04-18 08:24:08 UTC,The bzr branch is the source for generating the meta package (vanilla-gnome-desktop)
1764596,2018-11-27 12:42:46 UTC,Now that certain utilities are being shipped as snaps by default this might be more important. E.g. default install of 18.04 includes gnome-system-monitor as a snap but if you want the vanilla gnome desktop you end up with the deb version as well. If you're using snaps it makes more sense to use the snap version as it can see the snap processes (doesn't look like the deb one can) so would be nicer to be able to remove the deb version rather than the snap if the duplicated menu entries got annoying.
1764596,2019-07-13 00:55:02 UTC,"Hello Tim,"
1764596,2019-09-23 03:15:21 UTC,"The Ubuntu-gnome seeds can be found here:
https://code.launchpad.net/~ubuntu-gnome-dev/ubuntu-seeds/+git/ubuntu-gnome"
1764596,2020-04-11 02:27:36 UTC,This bug was fixed in the package ubuntu-gnome-meta - 0.87
1764597,2018-04-27 01:47:00 UTC,Issue still occurring in 4.17-rc2.
1764597,2018-04-27 04:34:14 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu"
1764597,2018-04-26 02:27:09 UTC,"Just an update, testing on 4.17-rc2 now. The issue doesn't come up that often, so I'll give it a few days to a week just in case."
1764597,2018-04-20 18:30:24 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1764597,2018-04-17 02:30:07 UTC,This change was made by a bot.
1764609,2018-04-17 03:48:02 UTC,There are now tooltips for it. Do we also need it in the manual? IMO the manual should be for topics that require too many words to fit into the UI.
1764609,2020-10-08 15:10:31 UTC,we get a lot of messages on facebook from radio users who are confused by the feature.  The tooltips don't seem to be sufficient.
1764609,2020-10-22 17:15:37 UTC,"@Owen I unassigned you as this was just picked up by an Outreachy applicant.
https://github.com/mixxxdj/manual/issues/57"
1764614,2018-04-17 08:11:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764614,2018-04-18 02:21:48 UTC,Some additional attempts to fix failed for me - I'm stuck and cannot update or remove anything.
1764614,2018-04-18 02:41:10 UTC,Found a FIX! Just need to move/backup the shared doc file that was causing the problem and all is right again.
1764618,2019-09-18 10:00:05 UTC,Some details for comment #4 and #5:
1764618,2019-09-18 12:28:03 UTC,"The attachment ""0001-api_test-fix-interfaces-comparison-failure.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1764618,2019-11-14 03:13:03 UTC,"@Connor, no, I don't really know how to work with that ubuntu importer to even land to focal. Currently focal has 3.0.4-1ubuntu5, but the source tree has 3.0.1 instead."
1764618,2019-09-18 09:43:47 UTC,Pull request to upstream: https://github.com/lxc/python3-lxc/pull/13
1764618,2019-11-12 19:45:31 UTC,"Hi Vicamo,"
1764618,2019-09-18 09:42:57 UTC,"In Bionic or above, tests are run by autopkgtest in the lxc package. However, its control file, https://github.com/lxc/lxc-pkg-ubuntu/blob/dpm-xenial/debian/tests/control, doesn't seem to depend on python3-lxc, which follows api_test in the python3-lxc package are not tested on Bionic or above[1]."
1764618,2019-09-17 10:21:10 UTC,Confirmed with 4.4.0-1056-kvm kernel. Failed program:
1764618,2019-09-17 17:25:36 UTC,CONFIG_ETHERNET itself is not turned on but says 'y' in annotation.
1764618,2018-04-17 05:58:48 UTC,ip addr output from the KVM host:
1764618,2019-09-18 08:24:22 UTC,https://github.com/lxc/python3-lxc/issues/2
1764618,2019-09-17 15:51:28 UTC,"CONFIG_E1000, driver for ethernet, is not enabled in kvm kernel."
1764621,2018-07-25 16:07:26 UTC,"Change abandoned by Marcin Juszkiewicz (<email address hidden>) on branch: master
Review: https://review.openstack.org/564552"
1764621,2018-07-24 12:53:24 UTC,"Reviewed:  https://review.openstack.org/564084
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=2aefc3d8fae53fac6d354d42c230eeff8815e96d
Submitter: Zuul
Branch:    master"
1764621,2018-06-07 03:15:56 UTC,associating exact  bug behind the failure
1764621,2018-07-27 13:34:50 UTC,This issue was fixed in the openstack/kolla 7.0.0.0b3 development milestone.
1764621,2018-04-18 06:39:28 UTC,i started a mail to talk about this issue http://lists.openstack.org/pipermail/openstack-dev/2018-April/129455.html
1764621,2018-04-17 05:25:54 UTC,"++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2018-04-15 13:53:58.089051 | primary | INFO:kolla.common.utils.neutron-server-opendaylight:Collecting ceilometer (from networking-odl==12.0.1.dev54)
2018-04-15 13:53:58.095393 | primary | INFO:kolla.common.utils.neutron-server-opendaylight:  Could not find a version that satisfies the requirement ceilometer (from networking-odl==12.0.1.dev54) (from versions: )
2018-04-15 13:53:58.095525 | primary | INFO:kolla.common.utils.neutron-server-opendaylight:
2018-04-15 13:53:58.480128 | primary | INFO:kolla.common.utils.neutron-server-opendaylight:No matching distribution found for ceilometer (from networking-odl==12.0.1.dev54)
2018-04-15 13:53:58.480264 | primary | INFO:kolla.common.utils.neutron-server-opendaylight:
2018-04-15 13:54:01.210214 | primary | INFO:kolla.common.utils.neutron-server-opendaylight:Removing intermediate container d5b97ba6cbb8
2018-04-15 13:54:01.287182 | primary | ERROR:kolla.common.utils.neutron-server-opendaylight:Error'd with the following message
2018-04-15 13:54:01.287519 | primary | ERROR:kolla.common.utils.neutron-server-opendaylight:The command '/bin/sh -c if [ ""$(ls /plugins)"" ]; then         pip --no-cache-dir install --upgrade -c /requirements/upper-constraints.txt /plugins/*;     fi' returned a non-zero code: 1
2018-04-15 13:54:02.668412 | primary | DEBUG:kolla.common.utils:Image neutron-server-opendaylight failed
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++"
1764621,2018-04-24 09:30:03 UTC,"Even im getting the same error when tried installing on Ubuntu:
I have Openstack-ansible(pike) AIO on Ubuntu 16.04."
1764628,2019-05-27 12:12:54 UTC,"The verification of the Stable Release Update for util-linux has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1764628,2019-03-15 04:50:15 UTC,"------- Comment From <email address hidden> 2019-03-15 00:39 EDT-------
Any update on this bug ?"
1764628,2019-05-27 12:11:56 UTC,This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.7
1764628,2019-06-20 11:19:56 UTC,"------- Comment From <email address hidden> 2019-06-20 07:09 EDT-------
Verified with  `util-linux                                           2.31.1-0.4ubuntu3.3`"
1764628,2019-05-15 20:39:29 UTC,"Hello bugproxy, or anyone else affected,"
1764628,2019-04-16 15:01:30 UTC,It's in the xenial-proposed queue.
1764628,2019-04-16 13:36:39 UTC,"xnox, would you please elaborate what ""in unapproved"" means ?"
1764628,2019-04-16 09:58:41 UTC,In unapproved
1764628,2019-04-03 00:21:43 UTC,"The attachment ""Fix to identify virtualization type correctly in Xenial on PowerPC"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1764628,2019-04-02 23:18:10 UTC,A test package is available in PPA:
1764628,2019-04-02 22:57:22 UTC,Please review and consider this debdiff to Xenial. It fixes the issue reported here.
1764628,2019-03-26 14:43:42 UTC,"IBM, please can you provide us with a list of patches (probably from the delta between 2.27 and 2.31) that needs to be applied on top of 2.27 to get the situation solved?
(For already released Ubuntu versions we cannot simply bump the version to 2.31 - the patches need to be cherry-picked ...)"
1764628,2019-05-20 13:08:42 UTC,"ubuntu@P8lpar2:~$ apt policy util-linux
util-linux:
  Installed: 2.27.1-6ubuntu3.7
  Candidate: 2.27.1-6ubuntu3.7
  Version table:
 *** 2.27.1-6ubuntu3.7 500
        500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el Packages"
1764628,2019-02-21 11:44:48 UTC,"Ok. so in xenial, on top of upstream release we cherrypick a few lscpu ""fixes"" for various arches, including powerpc from, what at the time was development. Clearly we didn't cherrypick enough of things, hence the lscpu regression. By 2.31 as used in bionic, things are all fine again."
1764628,2018-12-20 04:29:34 UTC,"------- Comment From <email address hidden> 2018-12-19 23:26 EDT-------
Upstream testing with util-linux [@ https://github.com/karelzak/util-linux]"
1764628,2018-12-20 06:33:38 UTC,"This is very clear now, thank you!"
1764628,2018-04-17 06:00:34 UTC,Default Comment by Bridge
1764628,2018-04-18 05:30:23 UTC,"------- Comment From <email address hidden> 2018-04-18 01:24 EDT-------
(In reply to comment #13)

> There seems to be no reason for
> https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 to fix
> this bug, since that is a targeted bugfix; and I understand your bug report
> to be asking if it's reproducible with this version, rather than telling
> that it is not.
>
> What are the values you expect in the output of lscpu for the ""Hypervisor
> vendor"" and ""Virtualization type"" fields that you highlight?  In what
> upstream version of util-linux is this known to be fixed?
"
1764628,2018-05-14 16:46:21 UTC,"it is not at all clear, based on the source changes included, why https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 would fix this issue."
1764628,2018-04-18 04:10:39 UTC,"There seems to be no reason for https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 to fix this bug, since that is a targeted bugfix; and I understand your bug report to be asking if it's reproducible with this version, rather than telling that it is not."
1764628,2018-08-20 14:00:38 UTC,"IBM, Xenial-updates is currently on version (https://packages.ubuntu.com/xenial-updates/util-linux) util-linux (2.27.1-6ubuntu3.6) could you please retest and confirm that this is now fixed ?"
1764628,2018-12-18 06:29:31 UTC,"------- Comment From <email address hidden> 2018-12-18 01:25 EDT-------
(In reply to comment #18)

> IBM, Xenial-updates is currently on version
> (https://packages.ubuntu.com/xenial-updates/util-linux) util-linux
> (2.27.1-6ubuntu3.6) could you please retest and confirm that this is now
> fixed ?
"
1764628,2018-12-20 02:01:36 UTC,"I'm confused reading this bug report. As the comments repeatedly mention identical version numbers, stating that both the issue is present and not present, requesting to pick up the version that is already in xenial, and later stating again that things are not fixed."
1764628,2018-12-20 02:06:39 UTC,Upstream for util-linux is at https://github.com/karelzak/util-linux
1764628,2018-07-03 16:19:37 UTC,"------- Comment From <email address hidden> 2018-06-27 01:45 EDT-------
(In reply to comment #16)

> Srikanth, Seeteena,
>
> Canonical has asked for an update to this bug.  Could you provide one?
> Specifically, their question is... ""please can you provide some more details
> why this is fixed with this util-linux version?""  Thanks.
"
1764631,2018-04-17 06:54:26 UTC,Could you please give some information about your video card and driver? Do you use Xorg or Wayland?
1764631,2018-04-17 09:16:03 UTC,I use Xorg
1764631,2018-04-17 09:19:07 UTC,"As a little update, just now, it's saving all screenshots as the same screenshot from a session I closed hours ago, 100% of the time."
1764631,2018-04-17 17:11:16 UTC,Are there any interesting lines in the log output (launch Shutter from terminal and see which lines are appended to the output when a screenshot is taken)?
1764639,2018-04-17 07:10:59 UTC,可能是主题里面没有对应尺寸的图标
1764639,2018-04-28 03:47:36 UTC,This bug is fixed in bionic-final 20180427 enhanced.
1764644,2018-04-17 11:48:45 UTC,"as already mentioned, the fixes inside the eps do solve the issue."
1764644,2018-04-17 12:02:19 UTC,"This is close to the result I am receiving when only changing the '/c' to '/l' inside the eps itself.
but still missing two points."
1764644,2018-04-17 11:32:00 UTC,"I think it would be best to raise this issue with the Maya developers, not with Inkscape."
1764644,2018-04-17 11:49:04 UTC,"alternatively, you could try an earlier version of Inkscape. attached is the result I get using Inkscape 0.91 r13725 (Jan 30 2015) and restricting the output to Postscript Level 2. This appears to contain only lines, no curves.
Does this work in Maya?"
1764644,2018-04-17 11:19:07 UTC,"let me emphasize the software again, I am importing it into Maya and so far only there is the incompatibility showing.
Opening your file inside maya, the same behaviour is shown."
1764644,2018-04-17 09:42:03 UTC,"sorry,"
1764644,2018-04-17 10:02:06 UTC,"thank you for the file. problem not reproduced if I use the file crosslike_shape.svg.
attached is the eps file I get from Inkscape, which appears to load correctly into GSView32.exe version 4.9."
1764644,2018-04-17 09:46:38 UTC,"opening the EPS in Illustrator or most other applications that can view them, shows a correct result.
However, the Curve creation in Maya fails due the mentioned formatting differences."
1764644,2018-04-17 10:05:26 UTC,"also, as far as I can tell, the eps file is not upside dowm. could you provide details of how you perform the eps export, which export options you use?"
1764644,2018-04-17 09:33:36 UTC,"thank you for taking the time to issue a report. I have not been able to reproduce the problem using Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11), and the attached svg file."
1764648,2018-04-17 14:22:41 UTC,This sounds like it could be an issue with recent versions of the NVIDIA proprietary driver (that would explain why 16.04 and 17.10 don't exhibit the issue).
1764648,2018-04-17 19:20:51 UTC,I filed an upstream bug: https://bugs.chromium.org/p/chromium/issues/detail?id=833984
1764648,2018-04-17 20:17:26 UTC,"According to the upstream bug report this is fixed in chromium 66, which is currently in beta and will be released to the stable channel this week."
1764661,2020-01-22 08:09:18 UTC,"Dear all,"
1764661,2020-01-22 12:42:49 UTC,"duplicity does not sync files like rsync.  We only restore what is in the backup, and do not restore over files without the --force option.  If there are files you do not want, clear the restore dir before running duplicity restore."
1764663,2019-07-12 03:17:53 UTC,"Hi cally725,"
1764663,2019-05-23 20:53:33 UTC,I see the same problem with a CentOS-Generic qcow2 image have you been able to fix your problem ?
1764663,2018-04-23 07:26:04 UTC,"I'm sorry, #1 I reply wrong. That's my bug for another one"
1764663,2018-04-23 06:56:52 UTC,Has been resolved：
1764665,2019-07-08 13:41:33 UTC,fixed by intoduction of noop plugin in 1.11.0
1764669,2018-04-26 03:31:28 UTC,This bug was not fixed in bionic-final 0425 version
1764669,2018-04-28 03:46:17 UTC,This bug exists in bionic-final 20180427 enhanced.
1764669,2018-12-24 20:31:40 UTC,This bug was fixed in the package ukui-power-manager - 1.1.2-0ubuntu1
1764685,2018-04-24 10:56:58 UTC,"Reviewed:  https://review.openstack.org/539469
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a3a94cf4ec3c0e41ab2a8a66dfc0e7adca2d2a8e
Submitter: Zuul
Branch:    master"
1764685,2018-04-24 14:01:47 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/563972"
1764685,2018-05-29 12:52:13 UTC,"Reviewed:  https://review.openstack.org/563972
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bc8c188fc1890d80a1b85866b3d31f51f0aceb38
Submitter: Zuul
Branch:    stable/queens"
1764685,2018-06-04 13:52:29 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1764685,2018-06-08 12:25:48 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1764685,2018-06-18 13:48:40 UTC,"I think this might have introduced a regression if you're filtering and have a marker, and that marker is in the build_requests table, we'll then try to find the marker in the cells and fail."
1764685,2018-06-18 14:08:25 UTC,I've reported bug 1777458 for the regression.
1764692,2018-04-26 03:40:36 UTC,This bug was fixed in bionic-final 0425 version
1764692,2018-04-28 03:45:12 UTC,This bug exists in bionic-final 20180427 enhanced.
1764692,2018-04-18 09:20:17 UTC,调整了ui控件。
1764695,2018-04-17 10:00:07 UTC,This change was made by a bot.
1764699,2018-04-17 09:41:10 UTC,"dpkg: ошибка при обработке пакета libperl5.22:amd64 (--configure):
 пакет libperl5.22:amd64 не готов к настройке
 настройка невозможна (текущее состояние: «half-installed»)
dpkg: зависимости пакетов не позволяют настроить пакет perl:
 perl зависит от libperl5.22 (= 5.22.1-9ubuntu0.3), однако:
  Пакет libperl5.22:amd64 не установлен."
1764699,2018-04-17 09:42:31 UTC,"sudo apt install libperl5.22
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Уже установлен пакет libperl5.22 самой новой версии (5.22.1-9ubuntu0.3).
обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено.
не установлено до конца или удалено 2 пакетов.
Необходимо скачать 0 B/3 402 kB архивов.
После данной операции, объём занятого дискового пространства возрастёт на 0 B.
Хотите продолжить? [Д/н] y
dpkg: ошибка при обработке пакета libperl5.22:amd64 (--configure):
 пакет libperl5.22:amd64 не готов к настройке
 настройка невозможна (текущее состояние: «half-installed»)
Отчёты apport не записаны, так как сообщение об ошибке указывает на повторную ошибку от предыдущего отказа.
                           dpkg: зависимости пакетов не позволяют настроить пакет perl:
 perl зависит от libperl5.22 (= 5.22.1-9ubuntu0.3), однако:
  Пакет libperl5.22:amd64 не установлен."
1764700,2020-03-31 11:54:48 UTC,"Change abandoned by Spyros Trigazis (<email address hidden>) on branch: master
Review: https://review.opendev.org/632721
Reason: The magnum team is cleaning up the backlog of changes older than 30 days. Feel to restore your patch."
1764700,2018-10-05 15:27:56 UTC,any updates on this ?
1764700,2018-11-15 03:45:57 UTC,I encountered the same problem while creating k8s cluster
1764700,2019-01-23 13:29:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632721"
1764701,2018-04-19 08:09:49 UTC,But in any case what's broken is the unversioned build - it does not even register as dynamically linked in ldd...
1764701,2018-10-17 06:52:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764701,2018-10-17 06:56:38 UTC,"i have the same(?) problem in ubuntu 18.10 starting sweethome3d
https://bugs.launchpad.net/ubuntu/+source/sweethome3d/+bug/1797920"
1764701,2019-08-12 08:28:37 UTC,I ran into a similar issue with Eclipse crashing (exit code 127) with this error in the console:
1764701,2020-03-23 14:42:28 UTC,The issue seems to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1838740
1764701,2019-04-23 07:03:24 UTC,"I also have this problem when trying to run Neuroph, I get the below error"
1764701,2018-04-19 08:09:13 UTC,the version script is:
1764701,2019-02-02 15:30:50 UTC,I am experiencing this issue when trying to start Terasology with OpenJDK 11.
1764701,2018-04-19 07:47:05 UTC,The lib.c is just:
1764701,2018-04-17 09:47:31 UTC,"Installing 16ubuntu2 in the Debian container makes it fail there too, so it seems highly likely that whatever is different between 16 and 16ubuntu2 is the cause"
1764701,2018-04-19 07:46:07 UTC,"Here's the output of gcc -v -shared -Wl,--soname=libadequate-test-versionless.so.0 lib.c with the PPA build, does not seem to help."
1764701,2018-04-17 09:45:33 UTC,Note that Debian's 7.3.0-16 works fine too.
1764701,2018-04-17 09:51:14 UTC,Summary of bisecting:
1764701,2018-04-17 09:52:46 UTC,Also:
1764701,2018-04-19 07:46:42 UTC,Here's the output with 15ubuntu2 which is working.
1764701,2018-04-19 02:27:11 UTC,"the output of the link command run with -v would probaböy help, as well as the contents of the linker scripts"
1764701,2018-04-19 04:32:10 UTC,there's agcc-7 test build building in ppa:doko/toolchain. please check this as well.
1764701,2018-04-19 02:12:25 UTC,"there are almost no changes between 16 and 16ubuntu2. Are you sure that 16 is good?  There might be a related problem reported as Debian #896012, but that is reported with 16."
1764715,2019-12-17 19:28:19 UTC,This is the result of a disconnected path with how the container is being setup. This isn't something that should be added to the apparmor abstractions. Ultimately this is a kernel issue and the limitations it puts on apparmor for tracking files with disconnected paths. There isn't anything that the apparmor package or abstractions can do to help with this so marking this as Won't Fix for lack of a better status.
1764716,2019-02-12 09:59:26 UTC,"+1, and need vxlan over unicast bridge support too."
1764716,2019-10-04 12:33:49 UTC,"+1, netplan brings me so much trouble, whatever i touched with it is either broken or not supported at all.."
1764716,2020-03-13 07:44:23 UTC,+1
1764716,2020-10-19 15:58:03 UTC,"Opened         2018-04-17
Deferred       2019-10-04
Any time line? 2020-10-19"
1764716,2020-12-18 23:42:45 UTC,I would use this as well
1764716,2021-01-08 10:39:40 UTC,Would be great if this get implemented
1764716,2021-01-15 19:15:12 UTC,"Not having this also means you rip out all the related bridge config from netplan as well, since you can't define a bridge using vxlan interfaces when they don't yet exist."
1764716,2018-05-23 19:58:16 UTC,+1 for this
1764719,2018-05-01 14:42:06 UTC,"Hello Seth,"
1764719,2018-05-01 00:38:40 UTC,"Hello Robert, Scott, do you know if CVE numbers have been assigned for these issues yet? Are patches available from upstream?"
1764719,2018-04-19 22:19:10 UTC,"Hi Robert, for reports that should be kept embargoed, I believe you can contact Alexandre Julliard <email address hidden> (wine lead developer) and CC: Marcus Meissner <email address hidden> (wine developer and SuSE security contact). Thanks!"
1764719,2018-04-20 02:53:57 UTC,"I already contacted julliard@ out of band, and he's fine with putting the reports public now."
1764719,2018-04-18 12:55:23 UTC,"I informed https://launchpad.net/~ubuntu-wine. I can also file a bug report to https://bugs.winehq.org, but I didn't find an option to mark reports as private there, hence everybody would see it. If that's ok, I can still do it."
1764719,2018-04-17 11:32:43 UTC,since there were newlines inserted into the bug description which made it less readable I attached it as advisory.txt
1764719,2018-04-18 06:47:15 UTC,"Hi Robert, thanks for the report. Has the upstream wine project been notified? As wine is in universe, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures ."
1764720,2018-04-28 10:42:48 UTC,This should be fixed in the engine. It is caused by the application of query simplification on the initial marking - if this check succeeds the engine should return an empty trace.
1764721,2018-04-17 12:07:19 UTC,This bug / RFE would belong on ovs-discuss / ovs-dev mail list.
1764724,2019-01-10 14:05:30 UTC,"Indeed, that's still an issue in the current version and seems an upstream one. Could you maybe report it to them as well on https://gitlab.gnome.org/GNOME/gnome-calculator/issues ?"
1764724,2019-01-14 00:42:24 UTC,Done.  https://gitlab.gnome.org/GNOME/gnome-calculator/issues/92
1764724,2019-01-14 09:48:52 UTC,Thanks!
1764727,2020-04-21 17:14:02 UTC,Adding the obvious: `caja --quit` will make it restart.
1764727,2020-04-21 17:11:30 UTC,Just want to note I have a system with caja 1.20.2 where it's using 7.3 GiB after 15 days uptime.
1764727,2019-04-23 05:59:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764727,2018-05-12 17:02:04 UTC,"I've also observed this. Over ~5 to 7 hours, caja version 1.20.2 memory usage reaches 2.5 or 3GB on Ubuntu 18.04 Bionic x86_64."
1764729,2018-04-19 20:12:07 UTC,Agree. Unfortunately I don't have the best words available to describe this in the docs.
1764738,2019-12-04 08:50:07 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1764738,2018-11-30 00:29:15 UTC,"Based on the feedback above, we have several operators / deployers interested in this RFE. Let's bring it up to the attention of the drivers team."
1764738,2019-05-04 22:34:34 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657170"
1764738,2019-12-04 08:50:16 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/623115
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1764738,2019-05-02 19:52:02 UTC,Have created a migration script here: http://paste.openstack.org/show/748074/
1764738,2018-12-13 17:21:31 UTC,"This RFE was approved to go ahead with a PoC. The drivers team understands that when the functionality is merged in Neutron, the code developers will include devref documentation"
1764738,2018-12-06 01:45:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623115"
1764738,2018-11-21 22:40:02 UTC,We actually have some code started to attempt to do the above.
1764738,2018-05-18 13:42:08 UTC,Let's wait a little longer to see if we get a response from the submitter
1764738,2018-06-08 13:35:11 UTC,"Hi Bjorn,"
1764738,2018-05-11 13:50:54 UTC,"@Bjolo,"
1764738,2018-05-22 08:44:48 UTC,"hi all,"
1764738,2018-11-21 21:04:40 UTC,We have a very similar use case.
1764738,2018-06-01 15:32:23 UTC,There is actually a comment in source code that we may want to consider relaxing this in the future to allow multiple segments on one host. (https://github.com/openstack/neutron/blob/master/neutron/db/ipam_backend_mixin.py#L736)
1764738,2018-06-01 16:24:46 UTC,"@Bjorn,"
1764738,2018-05-22 08:53:15 UTC,".... however, this should not enforce the operator to segment the compute resources. It should be independent of that."
1764742,2018-04-20 09:19:14 UTC,The work planned to move the OpenStack actions to mistral-extra [1] will solve this problem with OpenStack actions.
1764747,2019-03-28 12:53:41 UTC,Just use: Processing -> Toolbox -> Vector creation -> Points to path
1764747,2018-04-19 17:22:40 UTC,Thank you for reporting. Unfortunately I am using QGIS much less than I used to and I am quite busy with other stuff. I've been thinking that making an equivalent processing script could be easier than upgrading the plugin. Let's see if I can find some spare time to try.
1764747,2018-04-19 17:36:18 UTC,"Fair enough. I didn't realize it would require a lot of changes for updated versions of QGIS. I've never done any python before, but maybe I should look into what it would take also. I enjoy coding and like learning new things. I'll let you know if I find the time if I get started on it before you do. Thanks for your contributions."
1764747,2018-04-22 11:31:32 UTC,"Estimado amigo Goyo. Para mí y otras personas que usan tu plugin, es importante que lo siga mejorando para Qgis 3.0, es gran utilidad es muy bueno, aparta un poco de tu tiempo y modifícalo Dios te puede dar el tiempo necesario. Gracias"
1764757,2018-04-17 14:57:29 UTC,Should be fixed by https://review.openstack.org/#/c/556810/
1764765,2018-04-17 14:48:15 UTC,"StacktraceTop:
 _dl_fixup (l=0x562f95297fb0, reloc_arg=<optimized out>) at ../elf/dl-runtime.c:84
 _dl_runtime_resolve_xsave () at ../sysdeps/x86_64/dl-trampoline.h:125
 create_solid_fill_image (pict=0x562f95dd4d50) at ../../../../fb/fbpict.c:236
 image_from_pict_internal (pict=pict@entry=0x562f95dd4d50, has_clip=has_clip@entry=0, xoff=xoff@entry=0x7ffdb3cced60, yoff=yoff@entry=0x7ffdb3cced64, is_alpha_map=is_alpha_map@entry=0) at ../../../../fb/fbpict.c:463
 wfb_image_from_pict (pict=pict@entry=0x562f95dd4d50, has_clip=has_clip@entry=0, xoff=xoff@entry=0x7ffdb3cced60, yoff=yoff@entry=0x7ffdb3cced64) at ../../../../fb/fbpict.c:487"
1764782,2018-04-17 15:39:00 UTC,"Do we have any projects using that None value to indicate that the boolean value hasn't been set by the user? We have another way to do that now, so we could get them to update, but that's the only thing that comes to mind that would make me hesitate to change the behavior."
1764782,2019-08-12 20:06:12 UTC,"I have a case for adding a new BoolOpt which defaults to None (see https://review.opendev.org/#/c/675025/ ) because I want to add a new config option to nova (allow_cold_migrate_to_same_host) which defaults to whatever is set for another existing option (allow_resize_to_same_host, which defaults to False in config). So I want to default the new option to the value for the existing option (so I don't introduce a backward incompatible behavior change on upgrade) but still allow operators to opt into the behavior change with the new option."
1764782,2020-02-18 22:47:54 UTC,"I'm just going to close this. While I still think it's incorrect behavior, it's been around for a long time and it's unlikely to be worth the hassle of fixing all the places people may have relied on it."
1764783,2020-10-25 22:03:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/759600"
1764783,2020-10-28 03:13:50 UTC,"Reviewed:  https://review.opendev.org/759600
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=6a6e4907e5c57277bd998acfe2402ed5b8057326
Submitter: Zuul
Branch:    master"
1764795,2018-05-16 03:36:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568734"
1764795,2018-04-18 09:33:57 UTC,"It seems that when create encryption RBD volume, the backend size will bigger than the provided one. Then the DB just stores the provided size, not the real backend size (getting from the RBD driver). Then the snapshot created on the volume has the same problem."
1764799,2019-12-11 21:16:33 UTC,"I ran into this and it definitely wasn't due to missing build-deps.  The package built fine, simply could not issue ""debuild clean"" to remove the build artifacts.  The workaround in https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1764799/comments/3 does work however."
1764799,2018-06-27 22:31:46 UTC,I found a workaround:
1764799,2019-11-03 22:21:08 UTC,"If you see this issue, you might need to download dependencies:"
1764799,2018-05-17 00:54:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764806,2018-04-17 17:37:54 UTC,"On my notebook, urfkill dumped core while starting the GUI causing it to loop in the GUI initialization, so I simply removed urfkill and did not install it again.  I never missed that bugger ever since... (FWIW)"
1764807,2020-06-10 10:51:45 UTC,The zfsutils package was added to the seed for the release Ubuntu 19.10 Eoan and is also supported in Focal and Groovy. This won't be supported for older releases. Marking as fixed released.
1764814,2019-11-04 21:51:00 UTC,"> Oh, btw wondered if the fix for this might also result in a fix for #1728685?
"
1764814,2019-11-04 21:43:20 UTC,"Oh, btw wondered if the fix for this might also result in a fix for #1728685?"
1764814,2019-11-04 21:42:11 UTC,Ah ok I see where this comes from now.
1764814,2019-11-04 20:53:24 UTC,"Ah, no, actually it came from b0701e5 as a fix for bug 1638614. That's the edge case we need to ensure works."
1764814,2019-11-04 20:51:20 UTC,"Commit ab62e7d seems key to the history of ""fallback"" here. Based on the code before that commit, AFAICT the fallback was defensive programming rather than there being any specific edge case that we need to avoid. I think that means it's safe to specify something and replace how we determine the commit metadata with something deterministic."
1764814,2019-11-02 00:02:38 UTC,A deeper problem here is that it affects hash stability. My intention has been to look at this after the importer-add-tests branch. The commit metadata needs specifying and should not depend on Launchpad state that might change. We then need tests for that and then will be able to fix the implementation to match.
1764814,2019-11-01 22:45:21 UTC,"Fwiw, technically this isn't a Launchpad service error; teams can be suspended for various reasons I suppose.  So I don't think this needs filed against Launchpad"
1764814,2019-11-01 22:30:09 UTC,Currently seeing this for python-qt4.  Betting a number of python modules are similarly affected.
1764814,2019-08-05 09:38:09 UTC,FYI - There seems to be another affected package: python-tablib
1764814,2018-08-30 17:30:57 UTC,"From Nish:
<nacc> it needs a try/except for that return code in importer.py:1646"
1764814,2018-07-18 14:19:20 UTC,pkgbinarymangler 70~lucid1's changelog entry looks like this:
1764814,2018-07-18 14:18:33 UTC,Related: pkgbinarymangler has parsing difficulty on 70~lucid1
1764814,2018-04-17 18:46:10 UTC,"/*$ !bash
{}
  {*}"
1764814,2018-04-17 18:28:02 UTC,"For git-ubuntu, using Launchpad this way may not be reproducible, as I think user accounts can have their display names changed at any time. It might be better for us to fall back to something deterministic such as being based on the source package. The ultimate fallback might have to be ""Unknown <email address hidden>"" or something."
1764814,2018-04-17 18:24:25 UTC,"For every publishing record in Launchpad, we'd like to get the string of the name of the publication as viewed by Launchpad."
1764814,2019-10-24 06:47:47 UTC,Another affected package is (python-)twisted
1764814,2020-01-10 00:20:16 UTC,Now published in edge and the importer is active with the fix. All imports which were affected are now caught up.
1764823,2020-04-02 10:30:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764823,2020-04-02 10:44:23 UTC,"I have two Bionic x86_64 systems. One was showing the problem, the other was not.
The problem disappeared after issuing:"
1764823,2019-02-04 06:08:07 UTC,"That should have been created on install, by the namespace mechanism of dh_python2"
1764823,2018-04-18 00:53:53 UTC,"Found it: Package **python-backports.functools-lru-cache** does not contain the necessary file
/usr/lib/python2.7/dist-packages/backports/__init__.py"
1764848,2018-04-17 21:43:53 UTC,I was able to recreate this when upgrading a Ubuntu 16.04 chroot to Ubuntu 18.04 by editing /etc/apt/sources.list from xenial to bionic and running 'apt-get dist-upgrade'.
1764848,2018-04-26 11:00:37 UTC,"I know as an end-user it would be nice to be prompted about what to do with a duplicate certificate. That way when you are install more than one packages you will not have to run ""apt install -f"" to get things working."
1764848,2018-04-26 07:40:09 UTC,"""Wenn Sie in diesen weiteren Code von openssl eintauchen, gibt apps / rehash.c 1 zurück, wenn ein doppeltes Zertifikat gefunden wird."
1764848,2018-04-25 20:57:55 UTC,This bug was fixed in the package openssl - 1.1.0g-2ubuntu4
1764848,2018-04-25 17:07:19 UTC,Digging into this further openssl's code apps/rehash.c returns 1 when a duplicate certificate is found.
1764848,2018-04-25 15:38:45 UTC,Reverting the commit Laney identified did resolve the issue for me.
1764848,2018-04-17 20:09:29 UTC,perhaps a proper fix is for ubuntu-sso-client to release a new python-ubuntu-sso-client package in bionic that doesn't include this UbuntuOne-Go_Daddy_Class_2_CA.pem now that ca-certificates package has the CA.
1764848,2018-04-19 19:22:23 UTC,Here's the thread on debian-devel that describes the motivation for the change:
1764848,2018-04-19 09:58:08 UTC,I added some commentary to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895473
1764848,2018-04-26 17:43:38 UTC,The code of openssl does not need changing a new version of the package has been uploaded to the archive for Ubuntu 18.04.
1764848,2018-04-24 23:23:43 UTC,For people experiencing this bug if the duplicate certificate is Go_Daddy_Class_2_CA.pem provided by python-ubuntu-sso-client you can resolve this by purging the package e.g.
1764856,2018-04-19 07:03:49 UTC,"To add more information: as far as I can see, the delete tool is deselected once a disambiguation menu pop ups."
1764856,2018-04-19 15:57:15 UTC,"It definitely is deselected after a disambiguation popup is closed. This was what I originally wrote in the bug report. However, while testing before submitting the bug I saw it happen when there wasn't a disambiguation popup so I rewrote the bug. I'll try to reproduce the situation."
1764856,2018-06-03 20:56:23 UTC,"I haven't had any more unexpected component deletions, but I have noticed that if I rip up a track in close proximity with a component, often the component or track is highlighted as if it's been clicked on. That could explain how hitting Delete or Backspace a second time by accident could cause the component to be deleted."
1764856,2019-07-26 02:47:45 UTC,"It doesn't look like this is going to get addressed for 5.1, and it was completely re-written for 6.0 so I'm going to mark it fixed in 6.0."
1764860,2018-04-17 20:31:51 UTC,"StacktraceTop:
 _dbus_abort () at ../../../dbus/dbus-sysdeps.c:93
 _dbus_warn_check_failed (format=format@entry=0x7f1875ac87c8 ""arguments to %s() were incorrect, assertion \""%s\"" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n"") at ../../../dbus/dbus-internals.c:281
 _dbus_warn_return_if_fail (function=function@entry=0x7f1875ac71b0 <__func__.5319> ""dbus_message_iter_append_basic"", assertion=assertion@entry=0x7f1875ac64b8 ""_dbus_check_is_valid_utf8 (*string_p)"", file=file@entry=0x7f1875ac6a1d ""../../../dbus/dbus-message.c"", line=line@entry=2754) at ../../../dbus/dbus-internals.c:936
 dbus_message_iter_append_basic (iter=0x7ffcaf592190, type=115, value=0x7ffcaf592168) at ../../../dbus/dbus-message.c:2754
 main (argc=<optimized out>, argv=<optimized out>) at dbus.c:369"
1764860,2020-03-13 16:59:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764860,2020-03-13 17:02:15 UTC,"Just had this error in 20.04.
But may be related to this already reported:
[Bug 1866838] [NEW] ippusbxd crashed with SIGSEGV in usb_conn_acquire()"
1764863,2019-11-01 09:06:51 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1764863,2020-01-01 04:17:22 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1764867,2018-06-07 22:13:50 UTC,This issue was fixed in the openstack/neutron 13.0.0.0b2 development milestone.
1764867,2018-04-17 21:18:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/562054"
1764875,2018-04-17 21:54:45 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fde98e17b9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7fde98e19be8 ""malloc(): smallbin double linked list corrupted"") at malloc.c:5350
 _int_malloc (av=av@entry=0x7fde9904cc40 <main_arena>, bytes=bytes@entry=152) at malloc.c:3648
 __libc_calloc (n=n@entry=1, elem_size=elem_size@entry=152) at malloc.c:3436
 safe_calloc (nmemb=nmemb@entry=1, size=size@entry=152) at ../../lib.c:136"
1764882,2018-04-24 14:34:36 UTC,"This may actually be related to landscape-server returning ""maxiumum number of computers pending approval reached""."
1764882,2020-02-27 15:30:43 UTC,"Instead of accepting batches of 20, wouldn't it be simpler to just (temporarily) set a registration-key so clients don't need to be manually approved in the UI?"
1764883,2018-12-07 05:20:38 UTC,"Reviewed:  https://review.openstack.org/621199
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d9084d03e9d21fe249349c84549ede302ed1f652
Submitter: Zuul
Branch:    stable/queens"
1764883,2018-12-07 06:38:51 UTC,"Reviewed:  https://review.openstack.org/621200
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8bba879141d644b248d246cb2ed196068e20785c
Submitter: Zuul
Branch:    stable/queens"
1764883,2018-12-19 20:48:06 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1764883,2018-12-08 05:16:20 UTC,"Reviewed:  https://review.openstack.org/621205
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1abdb4ca22436c5eabadeab46b1237154c9cca92
Submitter: Zuul
Branch:    stable/pike"
1764883,2018-12-19 10:04:46 UTC,This issue was fixed in the openstack/nova 16.1.7 release.
1764883,2018-12-08 05:16:10 UTC,"Reviewed:  https://review.openstack.org/621204
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6380226863ecfcba2792c8ada3b2b92503b1d8ec
Submitter: Zuul
Branch:    stable/pike"
1764883,2018-11-30 16:14:27 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/621205"
1764883,2018-11-30 16:14:12 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/621204"
1764883,2018-11-30 16:08:17 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/621199"
1764883,2018-04-17 22:41:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/562072"
1764883,2018-04-18 13:51:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/562284"
1764883,2018-11-30 16:08:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/621200"
1764883,2018-07-25 04:38:19 UTC,"Reviewed:  https://review.openstack.org/562284
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c4988cdabf311d29cf64af732091068cfabeedaa
Submitter: Zuul
Branch:    master"
1764883,2018-07-30 16:06:55 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1764883,2018-07-24 17:35:04 UTC,"Reviewed:  https://review.openstack.org/562072
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9213398c785a0b54920754d50190e478293fbe8
Submitter: Zuul
Branch:    master"
1764896,2020-11-30 02:32:05 UTC,This is resolved now.
1764896,2020-11-30 09:09:45 UTC,"Thanks, closing then!"
1764904,2018-04-18 22:26:05 UTC,I did not propose this as a solution. I have described only the current state.
1764904,2018-04-18 21:04:39 UTC,Coupling this to the buffer size doesn't make much sense. The buffer size has no relationship to what may sound good.
1764904,2018-04-18 19:47:00 UTC,"We already have a bit of this feature in Mixxx. Currently we fade one buffer size, to avoid click sounds when looping."
1764904,2018-04-18 01:54:18 UTC,Great idea! I think it will take some experimentation to figure out exactly how this should work. Maybe a knob could be added to decks to control the fading amount.
1764904,2018-04-18 02:04:11 UTC,"Yep, a knob next to the loop buttons that goes from 0-100% of loop length would be good UI, I think."
1764908,2018-04-26 08:07:06 UTC,This bug was not fixed in bionic-final 0425 version
1764908,2018-04-28 03:43:10 UTC,This bug exists in bionic-final 20180427 enhanced.
1764912,2018-04-26 08:15:30 UTC,This bug was fixed in bionic-final 0425 version
1764912,2018-04-28 06:58:28 UTC,the bug exists in bionic-final 20180427 enhanced
1764914,2018-04-28 06:57:07 UTC,the bug exists  in bionic-final 20180427 enhanced
1764914,2018-08-09 03:30:55 UTC,"Hi, Harry Sheng,
  I think this is because your ""windows list"" applet has been hidden, and you can right click the panel and choose ""reset the panel""."
1764914,2018-04-26 08:17:24 UTC,This bug was fixed in bionic-final 0425 version
1764914,2018-08-04 16:01:09 UTC,"                          ./+o+-       harry@hp-dv3
                  yyyyy- -yyyyyy+      OS: Ubuntu 18.04 bionic
               ://+//////-yyyyyyo      Kernel: i686 Linux 4.15.0-29-generic
           .++ .:/++++++/-.+sss/`      Uptime: 2h 56m
         .:++o:  /++++++++/:--:/-      Packages: 1947
        o:+o+:++.`..```.-/oo+++++/     Shell: bash 4.4.19
       .:+o:+o/.          `+sssoo+/    Resolution: 1680x1050
  .++/+:+oo+o:`             /sssooo.   DE: GNOME
 /+++//+:`oo+o               /::--:.   WM: Ukwm
 \+/+o+++`o++o               ++////.   GTK Theme: Adwaita [GTK2/3]
  .++.o+++oo+:`             /dddhhh.   Icon Theme: Adwaita
       .+.o+oo:.          `oddhhhh+    Font: Cantarell 11
        \+.++o+o``-````.:ohdhhhhh+     CPU: Intel Core2 Duo T6500 @ 2x 2.1GHz [67.0°C]
         `:o+++ `ohhhhhhhhyo++os:      GPU: intel
           .o:`.syhhhhhhh/.oo++o`      RAM: 2807MiB / 3943MiB
               /osyyyyyyo++ooo+++/
                   ````` +oo+++o\:
                          `oo++."
1764918,2019-06-25 15:06:04 UTC,"Hi,"
1764942,2019-09-16 08:41:28 UTC,Migrated to https://github.com/widelands/widelands/issues/3265
1764946,2018-09-18 12:57:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764947,2018-04-18 09:42:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/562174"
1764947,2018-04-18 09:42:36 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/562175"
1764949,2018-04-26 01:47:28 UTC,bionic-final-0425版本未解决
1764949,2018-04-28 03:41:57 UTC,This bug exists in bionic-final 20180427 enhanced.(CD)
1764951,2018-04-26 08:18:12 UTC,This bug was not fixed in bionic-final 0425 version
1764951,2018-04-28 03:41:36 UTC,This bug exists in bionic-final 20180427 enhanced.
1764956,2019-03-15 15:34:40 UTC,This bug was fixed in the package linux - 4.4.0-143.169
1764956,2019-03-01 01:11:11 UTC,Final reminder: We are at the end of the SRU Cycle and request that you please provide verification the kernel in proposed resolves the problem for which this bug was submitted.  -Thank you!
1764956,2019-02-12 13:36:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1764956,2019-03-01 18:42:27 UTC,"I've managed to verify this on kernel 4.4.0-143-generic, the problem isn't reproducible anymore."
1764956,2019-01-14 08:27:49 UTC,The update to stable 4.4.169 will fix the majority of the issue.
1764956,2018-11-22 16:03:54 UTC,"Vincent, I'll update the description to match the SRU requirements, but your original description will still be available."
1764956,2018-10-23 21:38:03 UTC,"Hi Vincent, thanks for your report - really good research, even indicating a potential fix.
I manage to reproduce this issue using the following steps:"
1764956,2018-04-18 07:48:06 UTC,No log files to provide.
1764956,2018-04-18 07:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1764956,2018-11-22 16:02:27 UTC,"Gavin Guo had provided a patch to fix this issue, it's a SRU candidate: https://lists.ubuntu.com/archives/kernel-team/2018-November/096844.html"
1764959,2020-08-10 10:06:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764963,2019-09-26 15:00:44 UTC,PR https://github.com/juju/juju/pull/10652 fixes the BUG for the next milestone
1764963,2019-09-24 17:39:10 UTC,Joe and I were talking last week to make it provider specific because adding the change into the validator class could lead to unexpected side effect.
1764963,2019-09-20 11:20:19 UTC,"I think we'd need to sort by category (c3) and then withing all the c3.
instances."
1764963,2019-09-20 11:53:57 UTC,"Additionally, it should happen for other providers as well.
E.g. for openstack"
1764963,2018-04-18 10:28:19 UTC,"Maybe even better if we did something like group them by prefix, so you would end up with:"
1764963,2019-09-20 10:09:23 UTC,Would this output suffice?
1764965,2018-08-12 16:03:26 UTC,"Nope, tried again with arecord and it's recording slowly again. The same situation with audacity, sometimes it works and sometimes not."
1764965,2018-11-01 19:34:08 UTC,"Coming back from Pop!_OS 18.10 (Based on Ubuntu 18.10, 4.18.0-10-generic)"
1764965,2018-09-23 19:02:27 UTC,This bug is potentially the same one as 1716654 and also effects me as a single ALC1220 user (The gigabyte board has a second one which is not the case on the MSI X370 Pro Carbon).
1764965,2018-09-02 11:10:21 UTC,Hi!
1764965,2020-06-27 18:26:47 UTC,"Observing on Focal 20.04 on ROG STRIX X470-I, same ALC1220 audio device."
1764965,2018-08-18 06:32:50 UTC,"@Jacopo Yes, sometimes. Even restarting audacity or arecord does the trick. What really annoying is the noise level. And, yes I've tried everything under Windows 10 and sound records perfectly. The problem is that I hate too use Windows :)
Oh, I've updated linux kernel to 4.18 and the problem is still there."
1764965,2018-08-13 18:22:38 UTC,@Andrii I've experienced the same behavior topo... and rebooting seldom fixes the problem.
1764965,2018-08-12 15:53:35 UTC,"I've also tried command line tool for sound recording - arecord. And it works, somehow, but sound is very noisy and staticky."
1764965,2018-08-18 18:50:34 UTC,"@Jacopo, I think this problem may be an incompatibility issue between the PulseAudio driver (if driver is the correct term) and the ALC1220 chipset/codec.  I used this procedure to disable PulseAudio and found that I could record normally (link follows):"
1764965,2018-07-31 03:38:38 UTC,"I can get the record function to work properly by disabling Pulse and letting ALSA take over but as Pulse is required for so many basic functions, this is only a temporary solution.  I'm also running a MOBO with the Realtek ALC1220 codec."
1764965,2018-06-18 18:09:16 UTC,"@Markus could you please click on the ""Affects mee too"" link above the bug report, just under the title? Thanks :)"
1764965,2018-06-18 15:45:35 UTC,Here the same issue with Kubuntu 18.04. on a Asus Prime Z370-A. I hope for fixing this problem.
1764965,2018-06-16 13:12:28 UTC,I'm glad somebody else is affected by this bug...
1764965,2018-06-16 07:57:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1764965,2018-06-16 07:56:51 UTC,"Same setup and problem here, except it is a ASRock Mainboard, same Realtek ALC1220 Chipset."
1764965,2018-08-11 17:54:21 UTC,"I have the same problem and my board is MSI X370 Pro Carbon, (same ALC1220 Chipset). Tried Kubuntu 18.04 and Ubuntu 18.04. Recording with audacity also slow to the extreme. I changed sample rate in audacity to 510000 or 520000 Hz as a temporary workaround, but the sound is very noisy."
1764991,2018-04-20 01:40:47 UTC,This bug was fixed in the package livecd-rootfs - 2.524
1765002,2018-04-18 10:55:48 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
 QMessageLogger::fatal (this=<optimized out>, msg=<optimized out>) at global/qlogging.cpp:796
 queuedConnectionTypes (typeNames=...) at kernel/qobject.cpp:92
 ?? ()
 ?? ()"
1765002,2020-10-03 04:39:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765024,2021-02-22 07:00:55 UTC,It was fixed by https://review.opendev.org/c/openstack/horizon/+/769416
1765036,2018-04-18 11:59:27 UTC,All relevant info has been attached by using the utility script  https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info.
1765036,2019-08-19 16:23:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765036,2020-04-23 19:05:57 UTC,"Hi. I have Ubuntu 20.04 running on a Macboook PRO 2016 (with touchbar). I'm experiencing the same issue, but unloading brcmfmac module before suspend did not help. I also tried reloading the module and NetworkManager when the laptop wakes up, but not helpful as well."
1765043,2018-04-18 13:30:07 UTC,This change was made by a bot.
1765053,2019-06-04 15:36:02 UTC,@Martin: can you still reproduce this?
1765053,2018-04-24 16:43:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765053,2018-08-11 19:58:29 UTC,"I had the same problem
1) Installed nvidia-driver-390 (390.48 via software-properties-gtk)
2) Restarted to find out that it didn't built for kernel 4.17
3) Purged package, autoremoved, added repo ppa:graphics-drivers/ppa for driver 390.77
4) Restarted, resolution was low (probably because nouveau remained blocked)
5) Started to install nvidia-390, got the same error
6) sudo rm '/etc/OpenCL/vendors/nvidia.icd'
7) sudo apt --fix-broken install
After restart everything works."
1765053,2018-06-09 16:58:34 UTC,"Hello,
The GUI (graphicc user interface)!dose not start If i have no internet connection (offline )
An other personé (novice on ubuntu ) has upgrade Ubuntu 16.04 to Ubuntu 18.04 Have the same probkeme
The internet must connect at start (Ethernet or WiFi)
Same problem whith the live dvd ?
Why this internet connection deprndence
Why the GUI coud’nt Start ofline
Could you confirme this and help me to fix this issue
Thanks for your supporters
Best regards"
1765053,2018-04-20 10:39:10 UTC,Testing on a clean install of 18.04 daily today I can no longer reproduce this issue.
1765053,2018-04-19 02:26:21 UTC,"Martin,"
1765053,2018-04-19 13:06:17 UTC,I am unable to reproduce this using today's Bionic daily image.
1765053,2018-04-20 12:45:38 UTC,I've retested several installs and still encounter this issue. Installing via Additional Drivers UI or `apt install nvidia-driver-390` both work.
1765053,2018-04-19 12:44:27 UTC,"After removing all nvidia-related packages from a computer running 18.04, I tried
$ sudo ubuntu-drivers autoinstall
and everything installed with no errors."
1765055,2018-04-18 13:55:04 UTC,"StacktraceTop:
 _dbus_abort () at ../../../dbus/dbus-sysdeps.c:93
 _dbus_warn_check_failed (format=0x7f4bfcb90c10 ""Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application."") at ../../../dbus/dbus-internals.c:281
 _dbus_disconnect (messenger=0x562b973146a0) at listener.c:174
 messenger_listener_finalize (object=0x562b973146a0) at listener.c:150
 g_object_unref (_object=0x562b973146a0) at ../../../../gobject/gobject.c:3340"
1765059,2019-09-12 13:27:20 UTC,Does this bug still exist? Can you post new logs?
1765059,2019-11-12 04:17:41 UTC,[Expired for kolla because there has been no activity for 60 days.]
1765087,2019-07-30 12:17:15 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/673493"
1765087,2019-08-02 07:33:35 UTC,"Reviewed:  https://review.opendev.org/673493
Committed: https://git.openstack.org/cgit/openstack/python-mistralclient/commit/?id=051e9fa22b1b17d8c0405d940c7f7c593fcff28d
Submitter: Zuul
Branch:    master"
1765087,2019-09-13 19:11:28 UTC,This issue was fixed in the openstack/python-mistralclient 3.10.0 release.
1765090,2018-06-01 10:12:46 UTC,This bug was fixed in the package snapd - 2.32.9
1765090,2018-06-01 10:12:34 UTC,This bug was fixed in the package snapd - 2.32.9+17.10
1765090,2018-05-10 17:04:59 UTC,I don't see how the trusty validation is complete given the following test failure:
1765090,2018-04-24 17:16:16 UTC,Validation completed. Test results at: https://docs.google.com/document/d/13vIMXPKzMb3TytmszbSoRKOVu7x4DD9SPuL74rAycN0/edit?usp=sharing
1765090,2018-05-09 01:01:41 UTC,"Releasing this SRU to -updates is currently blocked on the following autopkgtest failures:
i386 on artful: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/s/snapd/20180507_070543_73bc3@/log.gz
amd64 on xenial: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/snapd/20180507_070059_48a5f@/log.gz"
1765090,2018-04-19 14:13:24 UTC,"Hello Michael, or anyone else affected,"
1765090,2018-04-19 14:12:58 UTC,"Hello Michael, or anyone else affected,"
1765090,2018-04-19 14:13:43 UTC,"Hello Michael, or anyone else affected,"
1765094,2018-04-18 19:40:11 UTC,thank you for taking the time to issue a report.
1765094,2020-01-21 07:11:09 UTC,Closing as part of migration to GitLab.
1765097,2018-04-18 15:25:45 UTC,"StacktraceTop:
 magazine_cache_pop_magazine (countp=0x5589fc0693f8, ix=1) at ../../../../glib/gslice.c:751
 thread_memory_magazine1_reload (tmem=<optimized out>, ix=1) at ../../../../glib/gslice.c:801
 g_slice_alloc (mem_size=mem_size@entry=32) at ../../../../glib/gslice.c:1014
 pango_glyph_string_new () at glyphstring.c:39
 shape_run (line=line@entry=0x7fe784001800, state=state@entry=0x7ffe49dd4eb0, item=item@entry=0x5589fcd9d040) at pango-layout.c:3231"
1765100,2018-06-16 18:33:56 UTC,affects both stable/pike and stable/queens.
1765100,2020-06-02 08:39:44 UTC,"pike and queens are in EM - won't fix in those releases - if you can reproduce it in currently supported releases (stein, train, ussuri) - please reopen the bug."
1765110,2018-04-20 20:48:23 UTC,apport information
1765110,2018-04-20 20:48:18 UTC,apport information
1765110,2018-04-20 20:48:20 UTC,apport information
1765110,2018-04-20 20:48:21 UTC,apport information
1765110,2018-04-20 20:48:25 UTC,apport information
1765110,2018-04-20 20:48:07 UTC,apport information
1765110,2018-04-20 20:48:29 UTC,apport information
1765110,2018-04-20 20:54:15 UTC,Somehow I was able to boot to the problem kernel just now without a freeze. But it took multiple booting tries. Then I ran apport.
1765110,2018-04-20 22:03:24 UTC,The proposed kernel  4.13.0-39-generic is working.
1765110,2018-04-20 20:48:16 UTC,apport information
1765110,2018-04-20 20:48:27 UTC,apport information
1765110,2018-04-20 20:48:15 UTC,apport information
1765110,2018-04-19 13:19:22 UTC,Updated description.
1765110,2018-04-20 20:48:12 UTC,apport information
1765110,2018-04-19 02:13:33 UTC,Please try to find the closest two kernel versions where one works and the other doesn't.
1765110,2018-04-20 20:48:14 UTC,apport information
1765110,2018-04-19 06:01:51 UTC,"Sounds like that contradicts the bug description: ""When using the 4.13.0-37-generic kernel, the login screen is completely frozen and unresponsive."""
1765110,2018-04-20 02:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765110,2018-04-19 04:29:42 UTC,"Oops, I made a mistake. Here is the case:"
1765110,2018-04-20 20:48:06 UTC,apport information
1765110,2018-04-20 20:48:10 UTC,apport information
1765110,2018-04-20 19:38:19 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1765129,2019-09-12 13:30:07 UTC,Is this still a bug? Can you post some logs? (Ansible deploy logs)
1765129,2019-11-12 04:17:43 UTC,[Expired for kolla because there has been no activity for 60 days.]
1765130,2018-04-18 16:54:00 UTC,Probably related to https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1652101
1765134,2018-08-11 16:54:55 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896012
1765134,2018-04-24 17:35:30 UTC,"Per discussion in the Debian bug, this is actually a lintian bug."
1765134,2018-08-11 16:27:27 UTC,"> Per discussion in the Debian bug, this is actually a lintian bug.
"
1765141,2020-11-27 17:32:24 UTC,I am on Ubuntu 20.04 and never observed that problem.
1765141,2018-05-09 09:21:24 UTC,"From what I've seen of the gnome-shell/mutter/clutter/cogl source code, they use white as a default colour. So if you see something that's all white it means there's meant to be a texture or image there, but for some reason it failed to render."
1765141,2018-05-09 15:50:57 UTC,Mesa version is the one that comes with Ubuntu 18.04: Mesa 18.0.0-rc5
1765141,2018-04-22 18:02:31 UTC,"I used X11 more often lately and faced the same bug, so it is not actually a Wayland only problem."
1765144,2018-06-08 12:25:42 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1765144,2018-05-11 08:28:43 UTC,As in the duplicates of this bug mentionend: The same error exists in the documentations of Cinder and Neutron!
1765144,2018-05-15 04:04:12 UTC,This issue was fixed in the openstack/nova 17.0.4 release.
1765144,2018-05-11 14:50:08 UTC,"Reviewed:  https://review.openstack.org/564336
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=056000230a2b44908193e61de2d17d89434e7ea8
Submitter: Zuul
Branch:    stable/queens"
1765144,2018-04-25 20:26:21 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/564336"
1765144,2018-04-25 20:25:28 UTC,"Reviewed:  https://review.openstack.org/562812
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=698630e1a432aa1f292fabe8d738a2f5867f73fe
Submitter: Zuul
Branch:    master"
1765144,2018-04-19 19:51:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/562812"
1765144,2018-04-19 19:31:59 UTC,"Some additional context. These bugs have been popping up because keystone removed the v2.0 API in Queens, which required two separate applications to be run side-by-side. The purpose of this was so administrators would talk to one application and end users would talk to the other. This ultimately pushed all the RBAC and policy problems onto operators, making ""secure deployments"" a system architecture problem."
1765144,2018-04-19 19:30:32 UTC,"(2:19:57 PM) mriedem: lbragstad: is this right? https://bugs.launchpad.net/nova/+bug/1765144
(2:19:59 PM) openstack: Launchpad bug 1765144 in OpenStack Compute (nova) ""[keystone_authtoken] auth_url = http://controller:35357 port error, it should be 5000"" [Undecided,New]
(2:20:40 PM) lbragstad: mriedem: yes and no
(2:20:55 PM) lbragstad: technically we removed the legacy v2.0 app in queens, so we no longer require two ports
(2:21:05 PM) lbragstad: but it certainly don't have to be port 5000, or 35357
(2:21:23 PM) mriedem: yeah looking in http://logs.openstack.org/20/554920/12/check/tempest-full/df42a0d/controller/logs/etc/nova/nova_conf.txt.gz
(2:21:27 PM) mriedem: we don't specify a port at all
(2:21:50 PM) lbragstad: oh - sure v
(2:21:52 PM) lbragstad: https://github.com/openstack/releases/blob/master/deliverables/queens/keystoneauth.yaml#L17
(2:22:00 PM) ***lbragstad fails copy/paste
(2:22:07 PM) lbragstad: auth_url = https://198.72.124.213/identity
(2:22:16 PM) mriedem: and auth_uri isn't specified at all
(2:22:44 PM) mriedem: was auth_uri keystone v1/v2 only?
(2:23:38 PM) lbragstad: you should use auth_url
(2:23:52 PM) lbragstad: auth_url and auth_uri was causing a lot of confusion
(2:23:57 PM) lbragstad: so we renamed it https://github.com/openstack/keystonemiddleware/commit/409b482253dec248ed828e92e52b09d4c02e51dd
(2:24:32 PM) lbragstad: it was ultimately a side-effect of integrating keystoneauth into keystonemiddleware
(2:27:01 PM) mriedem: ok so the note at step 5 here https://docs.openstack.org/keystone/latest/install/keystone-install-ubuntu.html#install-and-configure-components
(2:27:09 PM) mriedem: ""Before the Queens release, keystone needed to be run on two separate ports to accommodate the Identity v2 API which ran a separate admin-only service commonly on port 35357. With the removal of the v2 API, keystone can be run on the same port for all interfaces.""
(2:28:28 PM) openstackgerrit: Merged openstack/nova stable/ocata: Clean up volumes on boot failure  https://review.openstack.org/545086
(2:28:42 PM) mriedem: lbragstad: and i'm assuming that keystone-manage bootstrap creates the identity service endpoint in the catalog?
(2:28:51 PM) lbragstad: it does
(2:29:01 PM) mriedem: so if hte docs say ""--bootstrap-public-url http://controller:5000/v3/""
(2:29:11 PM) mriedem: then that's probably what the nova docs should use
(2:29:24 PM) mriedem: or internal url i guess, but they are the same in the docs
(2:30:16 PM) mriedem: ok i'll push a change to fix the nova install guide docs to remove auth_uri and change auth_url to use port 5000
(2:30:20 PM) mriedem: thanks"
1765153,2018-04-18 18:30:07 UTC,This change was made by a bot.
1765153,2018-04-18 21:14:38 UTC,"Thomas E. Horner, thank you for reporting this and helping make Ubuntu better."
1765153,2018-04-19 05:59:46 UTC,"1)
mfg: Heinrichs Weikamp
model: OSTC4"
1765153,2018-04-19 16:00:07 UTC,This change was made by a bot.
1765154,2020-04-14 11:30:10 UTC,"This is now resolved on the focal builds (the open-iscsi modules are not included, but nor does the systemd-modules-load service attempt to load them any more)."
1765154,2020-04-09 10:46:38 UTC,"I encountered the same problem, which puzzled me, we can add ib_iser.ko and ib_isert.ko and other required libraries to linux-modules-raspi2_18.04.1_arm64.deb, or add to linux-modules-extra -raspi2 ~ 18.04.1_arm64.deb, so that this problem can be solved well. Maybe some special circumstances need to use open-iscsi to call the printer and disk in the LAN.
If it has not been resolved, I think maybe I need to cross-compile a new deb containing the open-iscsi kernel part."
1765154,2018-12-16 12:37:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765154,2018-04-18 19:05:23 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1765160,2018-04-18 20:22:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1765160,2018-04-19 17:03:52 UTC,I include the /var/crash/_usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash
1765160,2018-04-19 17:56:04 UTC,"The next step i have done is, after installing xdiagnose, I run the following command in konsole:
ubuntu-bug xorg
and in the generated rapport, I click on submit, it take me to new page bugs.launchpad.net
and with more attached files:
and it create this new page:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765479
I have mentioned this page on that new link, but now, I have one more question, were I must continue to signal this bug ? Is it at the new:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765479
Or in this first page (https://bugs.launchpad.net/ubuntu/+bug/1765160),
or It will be merged automatically.
Thanks for helping"
1765160,2018-04-26 20:09:02 UTC,"Hello
Today when I have removed the screen cable from the main unit and plug it again after few moments, the session did not closes and all running programs stay running. I did it again another time, the same thing happened: all the programs stayed running. It seems that the updates of theses few last days solved the problem.
Thanks for all ubuntu developers for the great job they are doing."
1765165,2018-04-28 08:03:41 UTC,Hello.
1765170,2018-04-18 19:14:48 UTC,"Is there a crash file corresponding to this in /var/crash/ ? If so, can you please attach it here?"
1765170,2018-04-18 19:33:26 UTC,"As requested, the corresponding LibreOffice file is attached. Why was the file being closely related to the Roller and Light Locker files? Thankful."
1765179,2019-01-02 13:22:07 UTC,Works for me; pushed to master.  Thanks Cesar!
1765179,2018-12-10 22:28:05 UTC,"Here's a patch that addresses the error alert/message and  the pending patron grid refresh a user has been fully registered an is no longer pending. Issue was that after completing a staged user registration, the controller in regctl.js was refreshing to the same route, and trying to fetch the same staged user, but never finding it as it was no longer a staged/pending user."
1765179,2019-01-09 14:35:52 UTC,also pushed to rel_3_2
1765179,2018-04-18 19:36:49 UTC,Here is the error message that appears . . .  (screenshot attached)
1765179,2018-11-20 19:53:46 UTC,Confirmed in Evergreen 3.1.6.
1765189,2020-11-02 04:11:57 UTC,Can you please test Ubuntu 20.04 and tell us if it has the same problem?
1765189,2021-01-01 04:17:19 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1765192,2018-04-18 21:59:46 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/562392"
1765192,2018-04-18 22:22:04 UTC,This typo in the error message to the user is present only on stable/pike.
1765192,2018-04-19 22:20:22 UTC,"Reviewed:  https://review.openstack.org/562392
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=75ad1515fe5c1a83ca99e7e0ad9e61cf025e419f
Submitter: Zuul
Branch:    stable/pike"
1765192,2018-04-25 09:21:54 UTC,This issue was fixed in the openstack/python-novaclient 9.1.2 release.
1765194,2018-04-18 20:35:10 UTC,Removing line NoDisplay=true from /usr/share/applications/org.gnome.Terminal.desktop fix the problem. gnome-terminal also create an additional desktop file named gnome-terminal.desktop which is unnecessary.
1765197,2018-04-19 11:19:25 UTC,"Can you please provice a little bit more details about which influxdb charm you are using, as well as the telegraf one?"
1765197,2018-04-19 12:23:08 UTC,"Sure thing, I just used the promulgated current telegraf and influxdb charms. A dump looks like"
1765218,2018-04-18 22:04:52 UTC,I do not understand this at all.
1765219,2020-03-24 13:14:00 UTC,"This was fixed in commit edb18ab, released in 0.8.0."
1765219,2018-05-24 10:56:51 UTC,This is now resolved by using try/finally instead in ~racb/usd-importer:importer-cleanup-tmpdir-always.
1765220,2020-07-02 18:07:39 UTC,"Looks fixed to me as of now in focal.  @auerswal : Still present for you?  If not, please close or suggest closing the issue report."
1765220,2019-03-21 08:00:22 UTC,"Same for me, e.g. using the -C or -c options w/o filename:"
1765220,2019-03-21 07:48:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765233,2018-09-02 14:52:14 UTC,"If there is no file listing a human-sensible name for each time zone location, then let’s drop it and just say “the time zone you chose” instead."
1765233,2018-05-03 12:28:19 UTC,Could you open an issue against the design on github?
1765233,2018-05-03 23:10:08 UTC,Reported: https://github.com/CanonicalLtd/desktop-design/issues/110
1765233,2018-05-07 22:12:49 UTC,"The design showed something more reasonable, but I wasn't able to find any appropriate data to put in there in time - if anyone knows a way of getting a human readable location please describe it here!"
1765241,2018-04-19 19:15:10 UTC,SRU Justification:
1765241,2018-04-27 19:12:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1765241,2018-05-22 00:00:38 UTC,This bug was fixed in the package linux - 4.4.0-127.153
1765245,2018-12-12 14:09:05 UTC,"That's still an issue in the current version
https://errors.ubuntu.com/problem/3bd3a207afbabecf6f04ea083f904665bb4b4b0c"
1765245,2018-06-09 13:11:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765245,2018-12-18 12:43:13 UTC,Reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/320
1765266,2018-04-19 04:30:06 UTC,This change was made by a bot.
1765266,2018-09-05 08:19:24 UTC,"like, on <About this computer> it should tell me the kernel version"
1765267,2019-09-15 17:07:00 UTC,Migrated to https://github.com/widelands/widelands/issues/1071
1765271,2019-12-23 03:53:46 UTC,You solved the issue? I just got into it myself.
1765274,2018-04-19 11:57:02 UTC,"- reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- reproduced on Windows 10, Inkscape 0.92.3 (d2272d9, 2018-03-28)
- not reproduced on Windows 10, Inkscape 0.92+devel (e9e25c0, 2018-03-28)"
1765274,2020-09-10 19:24:38 UTC,Closing because INVALID: Can't replicate.
1765283,2018-04-24 19:21:25 UTC,"Hi Arunkumar,"
1765283,2018-04-24 19:29:06 UTC,"Ok upstream doesn't track bugs in launchpad anymore, as they've moved to storyboard."
1765283,2018-04-24 19:37:49 UTC,Ok it looks like there is already an upstream issue open for this at: https://storyboard.openstack.org/#!/story/2001878
1765298,2018-04-19 06:30:06 UTC,This change was made by a bot.
1765322,2020-03-18 21:15:36 UTC,"hi Jon,
it's strange you cannot ping google.
if you encounter this issue again, you can use the 'Disable internet check' option in the Advanced Options as a workaround."
1765335,2019-09-16 08:42:01 UTC,Migrated to https://github.com/widelands/widelands/issues/3266
1765341,2018-12-08 15:47:15 UTC,"The issue seems to be that your subnet does not contain the gateway address, and that pointtopoint configurations aren't supported by the default server installer (as well as some of its dependencies, i would think)."
1765341,2018-12-08 16:06:30 UTC,"> your subnet does not contain the gateway address
"
1765341,2019-04-04 23:05:06 UTC,"Hm so the bug about not being able to continue without a working network is fixed (in dailies, not in release media yet) but now I look at this bug I don't understand why the config you want to use does not work..."
1765348,2020-12-10 22:14:40 UTC,tox -e docs runs successfully now on master.
1765348,2018-06-04 11:17:54 UTC,"Reviewed:  https://review.openstack.org/559302
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=dbf754655fa2e5e17ec2fa6f85a03d88da0ccb6e
Submitter: Zuul
Branch:    master"
1765350,2019-10-23 08:41:00 UTC,"u@u:~$ cd /etc/NetworkManager/system-connections/
u@u:/etc/NetworkManager/system-connections$ ls
'TaipeiQA-5GHz(a*n*ac)'   TEST_CON
u@u:/etc/NetworkManager/system-connections$"
1765350,2019-11-07 07:07:42 UTC,"@Joc, you are right, output as below"
1765350,2019-11-06 11:14:25 UTC,"@Ray I think this is a different but related bug. Could you check the output of ""nmcli c"" after running this testing? I suspect there are TEST_CON connections not being cleaned up."
1765350,2019-11-06 08:32:37 UTC,"For more information, I can reconnected to Canonical-2.4GHz-g without supply password, I think it's does restore the connection info, but don't know why it's connected to ubuntu-cert-ac-open-tpelab rather than original AP (maybe the encrypted AP?)"
1765350,2019-11-06 08:27:35 UTC,I can reproduced this issue during RC50 testing.
1765350,2019-10-23 08:50:28 UTC,"Ok, so it appears the new save/restore jobs were being run when required but the SSID used in this situation used characters that NetworkManager replaces when creating the configuration file (because they are path separators)."
1765350,2019-11-13 07:51:26 UTC,"This issue was fix and verified pass on below version:
The AP was reconnected success after wireless test finish"
1765350,2019-10-23 08:31:15 UTC,@Erin Could you connect to the TaipeiQA-5GHz(a/n/ac) and then report what the contents of the directory /etc/NetworkManager/system-connections are please?
1765350,2019-02-07 16:01:37 UTC,"I think Maciej was correct in that the specific jobs listed in the bug description (dock/wireless...) only delete and then recreate network-manager connections for the APs used for testing. Hence, any other connections established should be fine."
1765350,2019-10-23 06:55:14 UTC,"This issue can be reproduced
SKU: MDA-DVT1-D6
BIOS: 0.1.25
Manifest: dell-bto-bionic-beaver-osp1-melisa-X25-20191017-21.iso
---
Test Step:
1. connect an AP
2. Do checkbox-cli run com.canonical.certification::wireless-cert-automated
---
u@u:~$ checkbox-cli --version
checkbox-ng: 1.5.0
checkbox-support: 0.42.0
com.canonical.ce:oem: 1.0
certification-client: 0.38.0
plainbox-provider-checkbox: 0.49.0
plainbox-provider-resource-generic: 0.41.0
plainbox-provider-sru: 1.14.0
plainbox-provider-tpm2: 1.11.0
---"
1765350,2019-05-27 08:42:35 UTC,Verified the bug was fixed with testing PPA on Italia - 201810-26511.
1765350,2018-10-26 08:27:26 UTC,@Maciej
1765350,2018-07-23 09:56:28 UTC,What I did is test this on two machines. On both it reconnected back after connecting to the test network. In other words: I cannot reproduce it :(
1765350,2018-07-06 08:34:35 UTC,The python rewrite of the nm wireless connection script does indeed delete all connections before exiting.
1765350,2019-10-23 07:29:34 UTC,"Run somerville/wireless Test plan
checkbox didn't connect to the original AP, it connect to 'ubuntu-cert-ac-open-tplab'.
The original configure was deleted. (need to type auth passwd again)"
1765355,2018-04-19 09:36:50 UTC,I can reproduce this on my Debian installation
1765355,2018-04-19 10:01:17 UTC,Any snapd older than 2.29 will have this issue.
1765355,2020-08-24 22:38:22 UTC,"This can't be reproduced on current debian-rpd (which uses snapd 2.37), so I'll set this bug to fixed."
1765361,2018-04-20 12:45:21 UTC,This is possibly related to #1751320
1765361,2018-04-20 13:57:15 UTC,Agree with Stefan. It very much looks like they are related.
1765361,2018-04-23 06:57:54 UTC,"Seems fixed in my tests. At least, where it used to fail, it does not now."
1765363,2018-09-01 19:51:39 UTC,Hey Tim! Not sure what was going on before (Mind must have been hazy after a full day of trying to fix this) but it actually is working now.
1765363,2019-09-28 15:35:07 UTC,"Same issue for me. Nvidia is not powered off in intel mode. Cause massive battery drain, powertop shows value between 30-40 W."
1765363,2019-08-19 14:26:31 UTC,Same issue for me.
1765363,2019-02-16 11:54:47 UTC,"This still happens after the 18.04.2 update.
My card is a MX150."
1765363,2018-12-10 20:23:01 UTC,This is affecting me with nvidia-prime 0.8.10 on Cosmic. Is that relevant here or should I report a new bug?
1765363,2018-06-04 10:07:40 UTC,"Thanks @tombuntus, works on my xps 9560 as well, even though I had to run `echo ""OFF"">/proc/acpi/bbswitch` after reboot. Also fixes problems with suspend."
1765363,2018-09-19 13:20:42 UTC,This issue should be fixed by the bug:
1765363,2018-09-01 03:31:26 UTC,"Hi Ryan, my solution uses bbswitch to turn off the card, which is what Ubuntu used before 18.04. If it works for your hardware in 16.04 (up to and including 17.10) it will work in  18.04. Also if it was working and then stopped working, it must be something you did."
1765363,2019-11-07 11:05:16 UTC,Same issue for me. Power consumption ~10W higher than normal on intel mode since some update around that happened around this past month. Previously had to use the command echo 'auto' > '/sys/bus/pci/devices/0000:01:00.0/power/control' (from powertop's tunables) to shut down the dGPU but otherwise worked fine.
1765363,2018-08-30 08:39:22 UTC,"this is the only solution that worked for me: https://goo.gl/vivchV
running ubuntu 18.04 after upgrade from ubuntu gnome 16.04.5
CPU intel i7-2670QM
GPU NVidia 525M
this solution is perfect for me! no bugs no lag nothing everything is super stable!"
1765363,2018-08-24 15:19:01 UTC,Still no fix in official repos?
1765363,2018-08-09 15:08:53 UTC,I applied the tweak of Tim (#46) on my Medion P6812 with a NVIDIA Corporation GF116M [GeForce GT 555M/635M].
1765363,2018-08-04 20:48:36 UTC,I am experiencing the same problem on a Dell XPS 9550 with a GTX 960M.
1765363,2018-07-27 12:16:03 UTC,"Same problem with Lenovo Legion Y520.
Intel HD 640 / Nvidia GTX 1050 Ti"
1765363,2018-06-07 18:50:44 UTC,"Setting ""nouveau.modeset=-1"" does not help here. My DELL XPS L502X is still running hot:"
1765363,2018-06-07 08:21:48 UTC,I've made a few tweaks which you can see here
1765363,2018-06-06 16:11:09 UTC,@tombuntus and @ mhr3
1765363,2018-08-31 20:51:37 UTC,Dell XPS 15 9570 with GTX 1050ti (mobile)
1765363,2020-01-13 06:41:34 UTC,Same issue for me. Power consumption ~10W higher than normal on intel mode.
1765363,2018-04-26 17:09:59 UTC,Definitely not TLP-related since I experience the same difference without TLP installed.
1765363,2020-04-07 00:59:02 UTC,Same issue for me as well.
1765363,2020-09-06 16:03:41 UTC,"I have this problem on kubuntu 18.04 and ubuntu,kubuntu 20.04
dell inspiron 5110n
nvidia gt525m
nvidia driver-390"
1765363,2018-06-03 19:27:47 UTC,"Ok, here's more complete detail, for 18.04. Do same as before with
kernel param nouveau.modeset=0 (I think this is probably dumb of me, but not sure)"
1765363,2020-05-27 03:55:15 UTC,"I am also affected by this bug. I am on Kubuntu 20.04 on a Dell XPS L502x. When I am on my Intel card, my computer reports my consumption as around 22 W. I checked my 'nvidia-prime' package, and it is 0.8.14. According to Vasyl, the bug should be fixed in this version, but unfortunately it is not, at least not for me. Please fix this bug, as the excessive power consumption essentially renders prime-select useless."
1765363,2020-05-20 21:35:53 UTC,Prime select is not turning off the dgpu in Ubuntu 20.04
1765363,2020-05-18 09:37:21 UTC,Probably the file name is /lib/udev/rules.d/50-pm-nvidia.rules
1765363,2020-05-18 09:29:32 UTC,"Vasyl, your solution works, but it has a big disadvantage.
HDMI doesn't work.
I'm deleting the 80-nvidia-poweroff.rules file - HDMI works after rebooting.
Restore this file - HDMI is not working."
1765363,2020-05-13 18:35:14 UTC,"I also have this bug. It seems that problem is on Ubuntu installer please check that comment:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/comments/7"
1765363,2020-05-04 21:05:53 UTC,"Hi Alberto, thank you for the reply! It motivated me to recheck the history of the changes for 'nvidia-prime' package."
1765363,2020-03-31 11:16:55 UTC,Same issue for me
1765363,2020-05-04 09:42:54 UTC,"I am pretty sure I fixed this in Ubuntu 19.10. If you use 20.04, you shouldn't need bbswitch or any other tweaks."
1765363,2020-05-04 06:17:02 UTC,@vasyl: I want to add to your comment.
1765363,2020-05-03 23:19:01 UTC,"@vasyl: thanks, good comment. It pays to RTFM, apparently."
1765363,2020-05-03 09:44:42 UTC,"I confirm the issue on Ubuntu 18.04 base with kernel 4.15.0-88, NVidia drivers 435.21 and 440.59 make no difference in the behavior. After 'prime-select intel' the nvidia driver is not loaded at all and intel graphcs are active, but according to PowerTop the NVIDIA chip still consumes the power. Acer laptop, NVidia 1050 Ti, Intel i5-7300HQ."
1765363,2020-05-03 04:07:59 UTC,"I will report that I also tried in 20.04 -- Kubuntu, Ubuntu (GNOME), and XFCE (as well as my main system MATE) and can report the same behavior (no poweroff of nvidia card by default even in intel mode)."
1765363,2020-05-03 04:06:20 UTC,This affects Ubuntu MATE 20.04 as well. The solution posted by Alexey_C (alexey-acv) works to appropriately poweroff the nvidia card (state ff) and lowers consumed power to about 6W).
1765363,2020-05-03 04:02:54 UTC,This problem affects ubuntu 20.04 as well. Ubuntu MATE 20.04 on an razer blade stealth (2019) laptop with nvidia MX150.
1765363,2020-04-28 06:40:27 UTC,"Yes. I win.
I install new systemd service with timer for power off NVidia after startup."
1765363,2020-04-27 12:26:07 UTC,"Hi.
I have this problem on Lenovo S540 and Ubuntu 18.04LTS
After reboot bbswitch is ON"
1765363,2020-05-04 09:22:11 UTC,"The bug is old and is getting a bit confusing, those still having issue on focal could you rather open a new report explaining clearly what you do, what you would expect and what happens instead? that should make easier to review the current status"
1765363,2018-06-02 19:46:16 UTC,"Here's my workaround, running on xps 15"" with 1050."
1765363,2018-04-26 16:33:22 UTC,"Running Quadro M1000M, no crash running Nouveau (just poor perf as everybody)"
1765363,2018-05-22 20:26:56 UTC,My solution also works around another bug which causes Ubuntu to default to a low framerate (40Hz for me) by using the intel driver instead of the modesetting driver and using custom modeline settings. If you don't want that remove the monitor config file and adapt the makefile.
1765363,2018-05-06 19:46:40 UTC,So pascal based gpu cant be turned of because powermanagment for nouveau is broken and disabled? And the loaded nouveau driver is causing freezes and slow down and instabilities?
1765363,2018-05-02 12:44:37 UTC,"This is a regression, with xubuntu 17.10 prime worked fine."
1765363,2018-04-30 15:14:35 UTC,"$ lspci | grep 3D
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 950M] (rev a2)"
1765363,2018-04-30 14:48:18 UTC,"@Alain What's you graphics card?
nouveau.runpm=-1 is the default setting for nouveau on Optimus systems. If the graphics card is not used, it will be powered down after 5 seconds iirc. As you did, this can be forced in the kernel boot parameters.
Unfortunately, with this setting, systems with recent graphics cards (GTX 10xx series) will not reach a usable desktop after login, and end up with a black screen.
I couldn't confirm but it may be this bug: https://bugs.freedesktop.org/show_bug.cgi?id=100228"
1765363,2018-04-30 08:19:15 UTC,"I tried something this morning, since I was convinced that this problem revolves around Nouveau power management."
1765363,2018-04-29 21:04:33 UTC,"Seems like you're right, François. I installed Powertop on both Ubuntu 18.04 (~12.5W at idle) and Fedora 27 (~5W) on the same laptop to measure the power comsumption. The method is not what I'd call scientific, but the difference is big enough to tell there's indeed something wrong.
On Fedora, I installed the proprietary driver via RPM Fusion, and disabled it with ""modprobe.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm"" kernel parameter."
1765363,2018-04-26 13:46:21 UTC,"Unfortunately, nouveau makes laptops with a Pascal dGPU (GeForce 10xx series) really unstable."
1765363,2018-05-08 03:51:56 UTC,"I can confirm the same issue on 18.04 using Gigabyte AERO 15x v8 with Nvidia GTX 1070 MaxQ. The `prime-select intel` method leaves the card powered on, even though the vgaswitcheroo/switch indicates it's off - the system power draw is ~ 20W."
1765363,2018-04-26 13:04:02 UTC,"Great, thanks for testing!"
1765363,2018-04-26 11:43:30 UTC,"When switching to Intel, nouveau is loaded manually (overriding the blacklist), and switches off the dGPU."
1765363,2018-04-26 11:12:33 UTC,"So, if I understand what's happening here. When switching to Intel, both Nouveau and the proprietary driver are blacklisted and the power management is disabled because of ""nouveau.run-pm=0"" kernel parameter. The discrete GPU is therefore always ON, but cannot be used at all."
1765363,2018-04-24 21:13:16 UTC,"I confirm a power usage issue.
Dell 7510 (too !)
Ubuntu (GNOME) 18.04
Nvidia M1000M"
1765363,2018-04-24 05:44:03 UTC,Running Xubuntu 18.04 by the way.
1765363,2018-04-24 05:42:18 UTC,Same here using a Precision 7510 after selecting Intel (sudo prime-select intel && sudo reboot) the following happens:
1765363,2018-04-24 05:38:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765363,2018-04-19 10:40:20 UTC,"However, I do not have this problem on my Thinkpad P50. The nvidia card is definitely turned off when in hybrid graphics after prime-select intel"
1765363,2018-04-26 12:23:18 UTC,"I didn't know about the SLI breakage, my bad."
1765363,2018-05-08 19:03:11 UTC,"Can confirm on a Dell XPS 9550 - power draw went from ~7W to ~20W after updating to 18.04, even with prime-select intel."
1765363,2018-06-01 22:30:49 UTC,"Matthieu's code is the best solution I've seen, as long as you are ok with lightdm.
The multi-dispatch aspects of the new module are a good simplification, Matthieu's approach looks like it's now easy to switch between intel and hybrid modes; he just blacklists modules."
1765363,2018-05-09 04:29:59 UTC,"Confirm on Lenovo ideapad 520S-14IKB (Intel i5-7gen, Nvidia 940MX , Intel 620HD).
On Ubuntu 17.10 (Nvidia driver 390.48 from ppa:graphics-drivers/ppa ppa:graphics-drivers/ppa) prime-select worked fine.
On Ubuntu 18.04 prime-select not turn off nvidia (driver from ppa and driver from repository).
Nouveau and bumblebee switches the graphics card well."
1765363,2018-05-22 20:17:18 UTC,"For anyone who is looking for a solution to their problem with newer Nvidia cards and the regression that you need to reboot to switch graphics:
https://github.com/matthieugras/Prime-Ubuntu-18.04"
1765363,2018-05-22 12:53:52 UTC,"I'm now using a mainline 4.17rc6 kernel, and it looks like ACPI errors are gone, however nouveau will still make my system unstable, causing a freeze on using `lspci` and on graphical login."
1765363,2018-05-20 17:17:46 UTC,"Let's try to let nouveau turn off the dGPU with a mainline 4.17rc6 kernel, probably available as DEB packages tomorrow (21/05/2018) from http://kernel.ubuntu.com/~kernel-ppa/mainline/.
See this PR: https://lkml.org/lkml/2018/5/18/159"
1765363,2018-05-14 19:20:06 UTC,"Please note that
RUNTIME_PM_DRIVER_BLACKLIST=""amdgpu nouveau nvidia radeon""
is TLP's default (happens too if the line is commented), so if you don't want to blacklist any driver you have to set
RUNTIME_PM_DRIVER_BLACKLIST=""""
as TLP config file's comments warn us about this trick."
1765363,2018-05-14 18:16:13 UTC,"I forgot a bootparameter: ""nouveau.modeset=0""."
1765363,2018-05-14 17:49:29 UTC,Following worked for me to get the dgpu switched off on an xps 15 9560.
1765363,2018-05-14 12:24:50 UTC,"Thanks Loris,"
1765363,2018-05-14 11:52:17 UTC,"Same here, NVIDIA Quadro M2000M (GM107GLM)."
1765363,2018-05-14 11:25:42 UTC,"@Stefan: When you're using nouveau.runpm=-1, nouveau is always used to dynamically power down the card. This works because a Dell XPS 9550 ships with a GeForce GTX 960M, which nouveau is actually able to power down, unlike the more recent XPS 560 with a GTX 1050."
1765363,2018-05-14 08:08:14 UTC,@Noam Mor:
1765363,2018-05-08 22:05:58 UTC,Confirming on Dell XPS 15 9560; Nvidia is not power-down when prime selecting Intel: I am now on 13W with TLP enabled... 17.10 would give me about half of that.
1765363,2018-05-13 17:50:54 UTC,"Changing nouveau.runpm=0 to nouveau.runpm=-1 in /etc/default/grub, and then running update-grub, fixed the issue. Back to 6W. Dell XPS 9550."
1765363,2018-05-11 08:21:42 UTC,"To manually disable you discrete graphics card:
sudo systemctl disable nvidia-fallback
sudo -s
root@system:
modprobe -r nvidia && modprobe bbswitch && echo ""OFF"">/proc/acpi/bbswitch && logger Nvidia OFF"
1765363,2018-05-10 08:54:20 UTC,I tried this on my Dell XPS 15 but without nouveau.runpm=0 the login freezes. With it on the GTX 1050 doesn't really turn off. Any clues?
1765363,2018-05-09 09:40:25 UTC,"On my machine even removing nouveau.runpm=0 didn't work, Nouveau was not able to turn off the card."
1765363,2018-05-09 09:16:04 UTC,"I confirm, when you delete the nouveau.runpm=0 option from grub (no need to force the -1 value if you just modify the grub file, it's default if @nepenthes is right), you get :"
1765363,2018-05-09 05:30:53 UTC,"Correction. I run command of Alain Rouet (alain-rouet):
# sed -i ""s/boot_params\['nouveau.runpm'\] = '0'/boot_params\['nouveau.runpm'\] = '-1'/"" /usr/bin/prime-select"
1765370,2019-10-27 09:23:44 UTC,kraft 0.82-1build1 is available in Ubuntu 19.04 and later releases.
1765370,2018-10-25 21:06:41 UTC,Newer version 0.82 has been released: https://github.com/dragotin/kraft/releases/tag/v0.82
1765370,2018-06-17 14:43:58 UTC,Kraft v. 0.81 was released: https://github.com/dragotin/kraft/releases/tag/v0.81
1765370,2018-04-19 11:06:19 UTC,"Yes, please update."
1765370,2018-04-19 14:12:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765373,2018-04-19 11:23:30 UTC,Patch 1/4 of reference backport made against Ubuntu-4.15.0-15.16 tag of git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
1765373,2018-04-19 11:23:56 UTC,Patch 2/4 of reference backport made against Ubuntu-4.15.0-15.16 tag of git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
1765373,2018-04-19 11:24:37 UTC,Patch 3/4 of reference backport made against Ubuntu-4.15.0-15.16 tag of git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
1765373,2018-04-19 11:25:13 UTC,Patch 4/4 of reference backport made against Ubuntu-4.15.0-15.16 tag of git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
1765373,2018-04-19 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765373,2018-07-09 15:39:39 UTC,"Hi,"
1765374,2020-06-14 21:33:06 UTC,Very sad indeed.
1765374,2020-06-15 09:37:51 UTC,"That's not what I meant, I meant the CLI Desktop installer (if there's still such a thing), I haven't tried it in several years but it did work with Hebrew due to some work done on the Debian Installer which fully supports Hebrew in CLI (I'm guessing with some sort of FriBiDi implementation and the correct fonts)."
1765374,2020-06-15 04:05:50 UTC,Well the desktop installer runs in a graphical environment and so can display all kinds of glyph.
1765374,2019-02-21 14:28:59 UTC,"I think to make this work we'd need to switch to running in fbterm, which would be possible but doesn't seem very likely to happen in the near term."
1765378,2018-09-21 15:01:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765379,2018-04-19 11:32:12 UTC,Patch 1/2 of reference backport made against Ubuntu-4.15.0-15.16 tag of git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
1765379,2018-04-19 11:32:43 UTC,Patch 2/2 of reference backport made against Ubuntu-4.15.0-15.16 tag of git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
1765379,2018-04-19 12:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765380,2018-04-19 12:55:47 UTC,If I'm using xenial and in pressed file bionic it's working
1765380,2018-04-19 13:18:31 UTC,If I'm using xenial and in pressed file bionic it's NOT working
1765383,2018-04-19 19:33:41 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1765385,2019-12-20 11:43:47 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/562547
Reason: Nice idea, but this is in merge conflict for quite some time and I'm not sure if anyone is prepared to respin this. Please let me know if you are and I can restore it."
1765390,2018-05-02 09:20:32 UTC,"Sorry for that. I only described the Problem with the Printer Concept/Workflow that is used in Ubuntu. In my opinion this is one Issue, I'm not able to get what is working in Background and what is working how in Background. I'm not familiar with the responsibility in the deep of your developing. In my opinion I don't have to. I barley able to manage to report in this strange and absolute not intuitive Web surface (see also [Bug 1765667] ). I like Ubuntu, but not that much that I would learn to develop some apps. So please do this for me. I'm wondering also that you allow accepting Bugs to this package but are not able to send it further to the correct address. Maybe there is a need of a Feature Request for a better Work-flow in this reporting tool 😉 ."
1765390,2019-04-29 10:58:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765390,2019-04-29 10:58:05 UTC,"Me to: ""I miss a switch in the printer settings to disable automatic detection and adding."""
1765390,2018-05-01 11:53:17 UTC,"One bug report should also describe one issues, it's not very practical dealing with different issues at the same place"
1765390,2018-04-19 16:21:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1765390,2018-04-20 10:31:26 UTC,thanks for the hint to https://wiki.ubuntu.com/Bugs/FindRightPackage It seems this Article is in the section Gnome not anymore actual. I had to use https://wiki.ubuntu.com/Bugs/FindRightPackage#Any to get it.
1765390,2018-05-01 11:52:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1765391,2018-07-18 17:24:20 UTC,"Reviewed:  https://review.openstack.org/558741
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=14198baf6ca8f4efe05feca0dd7633adc3128ce4
Submitter: Zuul
Branch:    master"
1765399,2019-09-14 17:25:23 UTC,The required C++ changes were merged: https://github.com/mixxxdj/mixxx/pull/2275
1765401,2018-04-20 17:19:22 UTC,Thanks for your suggestions.
1765401,2018-07-18 16:44:22 UTC,"Another thread relevant, at least for the gnucash aspect of this bug:
https://lists.gnucash.org/pipermail/gnucash-user/2018-March/075769.html"
1765401,2018-07-18 16:31:25 UTC,Linking Jonathan's mailing list thread for reference: https://lists.gnucash.org/pipermail/gnucash-user/2018-April/076587.html
1765401,2018-05-10 15:07:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765401,2018-04-20 16:05:22 UTC,"I don't have the solution for your issue unfortunately. But I can eliminate a few elements:
Gnucash has switched to gsettings/dconf starting with 2.6.0. That means gconftool and gconftool2 changes are ignored by gnucash. As you discovered making the change in dconf is seen by gnucash 2.6.x."
1765401,2018-04-19 17:39:03 UTC,"More info... I've confirmed that on 17.10, the toolbar style is controlled by /org/gnome/desktop/interface/toolbar-style. When I edit that setting in dconf-editor in 17.10, the change is reflected in the open GnuCash window, but when I edit that exact same setting in dconf-editor in 18.04, it has no effect on the open GnuCash window."
1765401,2018-04-19 16:26:01 UTC,Two additional notes:
1765401,2018-04-19 13:16:58 UTC,"Also tried putting `gtk-toolbar-style = GTK_TOOLBAR_BOTH` in ~/.gtkrc-2.0 and `[Settings]\ngtk-toolbar-style = GTK_TOOLBAR_BOTH` in ~/.config/gtk-3.0/settings.ini. The latter causes the output of gtk-query-settings to change, but neither of these settings causes GnuCash to behave differently."
1765401,2018-04-19 18:41:50 UTC,"Note: GnuCash 3.0, when built from source, does not display the toolbar correctly either."
1765402,2018-06-25 01:00:25 UTC,"While reports of suspected vulnerabilities for heat-dashboard are not normally coordinated by the OpenStack VMT, the reporter reached out to and subscribed us requesting some assistance as this has been sitting untriaged for over a month. I have in turn subscribed the Heat team's core security reviewers since I'm unsure who has initial visibility into private security bugs for heat-dashboard."
1765402,2018-06-25 14:38:58 UTC,"Both heat and heat-dashboard have moved their bugs to storyboard.openstack.org (possibly since this issue was opened, otherwise I don't see how you managed to create a new bug report on Launchpad)."
1765402,2018-06-25 15:05:05 UTC,"Thanks, Zane. Since this sounds like a known issue and you suggested switching it to public, I went ahead and did that."
1765411,2019-08-09 07:57:25 UTC,"Yongfenf Du, could you provide the versions of Ansible you were using, and your OS?"
1765411,2019-08-08 23:21:04 UTC,"Just ran into this problem in virtualenv.
""pip install ansible""
in the virtualenv fixed this.
Previous I'm using the ansible installed by ""yum install ansible"" outside of venv."
1765411,2018-09-17 19:47:10 UTC,"I got mine to work by removing system packages:
$ cd kolla-ansible
# pip uninstall -r requirements.txt"
1765411,2018-11-09 15:10:04 UTC,I ran into this problem. It seems there are issues with running kolla-ansible within a virtualenv.
1765411,2018-06-14 07:21:43 UTC,"same Problem:
OS: Ubuntu 16.04
OpenStack release: queens
Ansible version: 2.5.4.0
Python version: 2.7.13"
1765411,2018-04-20 13:30:02 UTC,"Found a fix for this that got me through the deployment successfully, but I'm not sure why pip doesn't take care of this as part of the dependency resolution for kolla-ansible."
1765411,2018-06-20 12:09:17 UTC,"Does anyone have a working config?
OS: ??
OpenStack release: ??
Ansible version: ??
Python version: ??"
1765425,2018-04-26 06:53:57 UTC,"Seen again:
http://ci.jujucharms.com/job/github-check-merge-juju/1078/testReport/junit/github/com_juju_juju_worker_caasoperator/TestPackage/"
1765430,2021-02-24 18:20:20 UTC,https://github.com/mixxxdj/mixxx/pull/3615
1765432,2018-04-19 14:58:13 UTC,We had the opensuse URL change today and had to do this emergency patch to stop all our tests failing: https://review.openstack.org/562599
1765434,2019-10-22 17:59:49 UTC,"Pushed to master, 3.3, and 3.4.  Thanks, Tiffany!"
1765434,2019-03-18 17:55:41 UTC,"I have a branch here that refreshes the iframe that the purchase order lives in. It adds a button next to the ""Open in New Window"" that when clicked will refresh the PO without sending you back to the search screen."
1765434,2019-01-22 18:00:23 UTC,"This continues in 3.2.  While in an existing PO, refresh returns to acq search screen."
1765434,2018-04-27 20:31:47 UTC,This issue exists in 3.1
1765436,2018-04-19 23:15:44 UTC,Wow... good catch. Very weird behaviour.
1765436,2018-04-23 01:50:02 UTC,"OK, good news, bad news..."
1765436,2018-04-23 02:05:09 UTC,There is a hard coded value in the apiserver that specified deploying to clean-empty machines.
1765438,2018-05-25 09:58:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/570552"
1765438,2018-06-09 17:59:34 UTC,"Reviewed:  https://review.openstack.org/570552
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-rabbitmq_server/commit/?id=91408d5a2eed5d0e9306372ea4c5ca7e2a1c8fe0
Submitter: Zuul
Branch:    master"
1765438,2018-05-15 15:46:00 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/568626"
1765438,2018-05-15 15:19:47 UTC,"Reviewed:  https://review.openstack.org/563641
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=f4e74ea7143b96554023c604620cac0b5f5a5753
Submitter: Zuul
Branch:    master"
1765438,2018-04-23 14:19:06 UTC,Related patch proposed: https://review.openstack.org/563641
1765438,2018-05-17 14:46:55 UTC,"Reviewed:  https://review.openstack.org/568626
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=c038e8dc6286573debd163102974faafba04664c
Submitter: Zuul
Branch:    stable/queens"
1765438,2018-04-23 13:24:06 UTC,"Doing this updated the fact cache, the re-running the rabbitmq playbook worked:"
1765438,2018-04-23 13:17:40 UTC,What is most odd is that the task executes as follows:
1765438,2018-04-23 12:19:17 UTC,"Interestingly, after the revert merged on a fresh build I got the same error:"
1765438,2018-04-23 13:38:38 UTC,It appears that this may be a regression in https://github.com/ansible/ansible/issues/17213
1765441,2018-04-26 14:53:46 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.openstack.org/562808
Reason: Will update in pycqa"
1765474,2018-04-20 06:36:27 UTC,"Hi Paj, thanks for reporting this bug."
1765474,2018-04-20 07:52:49 UTC,"Yes, looks like that bug to me too."
1765474,2019-09-16 19:06:26 UTC,Migrated to https://github.com/widelands/widelands/issues/3268
1765476,2018-04-19 20:45:58 UTC,"Source and binaries are reporting a wide variety of lintian error, warnings, fixable info and pedantic messages that should be looked at and addressed before inclusion in the archive."
1765477,2020-01-24 21:03:12 UTC,"I'm seeing this in eoan, too."
1765477,2019-02-27 18:07:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765477,2019-02-27 18:45:30 UTC,I'm having similar problems with DNS resolution in Bionic Ubuntu-Server.
1765477,2019-02-28 02:52:46 UTC,Any five second delay in name resolution is most likely caused by this open bug in systemd-resolved:
1765503,2019-04-16 20:35:52 UTC,apport information
1765503,2019-08-02 13:16:44 UTC,Just a small note: in the binary scilab distribution exists interesting file lib/thirdparty/libhdf5.settings and it states that it uses version 1.8:
1765503,2019-04-16 20:35:53 UTC,apport information
1765503,2019-04-16 20:35:54 UTC,apport information
1765503,2019-04-16 20:36:23 UTC,Still a problem on cosmic even with Scilab 6.0.1-7ubuntu1~18.10 .
1765503,2019-05-23 10:52:08 UTC,ATOMS is still broken on Eoan.
1765503,2019-05-23 11:02:41 UTC,ATOMS is still broken on Ubuntu 18.04 Bionic Beaver (LONG TERM SUPPORT release)..
1765503,2019-06-22 09:34:00 UTC,"Even with latest upgrades on eoan, disco, cosmic and bionic - ATOMS does not work."
1765503,2019-08-02 12:58:44 UTC,"Dear Ubuntu, Debian and Scilab developers/maintainers!"
1765503,2019-08-06 14:06:15 UTC,# Intro
1765503,2019-12-18 19:51:11 UTC,"Dear Stephane,"
1765503,2019-12-17 12:24:02 UTC,*** Bug 16287 has been marked as a duplicate of this bug. ***
1765503,2019-12-17 12:27:30 UTC,Nikolay why don't you commit you patches on CR ?
1765503,2019-12-17 16:59:05 UTC,"As per the analysis of Nikolay, the impact of this bug means that ATOMS and many other functions are not available to Ubuntu users."
1765503,2019-12-18 14:56:44 UTC,"(In reply to Paul van Haren from comment #15)

> As per the analysis of Nikolay, the impact of this bug means that ATOMS and many other functions are not available to Ubuntu users.
>
> I've tried installing the latest successful nightly build, but that doesn't work as the customization for Ubuntu/Debian is missing and too many
> environment issues arose. E.g. when starting scilab from the command line, nothing happens, no output, no CPU load. The only think you can do is
> stop the process (^Z) and then kill the stopped job. I couldn't run the stable 6.0.2. version either.
>
> Next, I've tried building from source, but here I couldn't get past the JOGL and javah issue, also reported by Nikolay (the javah issue I could
> work around, but I couldn't find a fix for the JOGL issue).
>
> Effectively, this means that I don't have means to run Scilab, and I guess with me also most of the other Ubuntu/Debian users.
>
> @Stepahne, is there something you can do to raise the awareness on this issue and take measures for a big fix release being pushed to the Ubuntu
> package maintainers?
>
> Thanks and regards, Paul
"
1765503,2019-12-18 23:42:08 UTC,"(In reply to Paul van Haren from comment #18)

> Dear Stephane,
>
> I think you're overlooking the observation by Nikolay (close to the bottom of comment 11):
>
> # Brief analysis
>
> I believe that root cause of the problem is change of `hid_t` datatype in HDF library.
>
> It is not an `int` anymore, it is `int64_t`.
> But the scilab source code have many places with hardcoded `int`.
> See for example `openHDF5File` - http://cgit.scilab.org/scilab/tree/scilab/modules/hdf5/src/c/h5_fileManagement.c which calls `H5Fopen`:
>
> ```
> int openHDF5File(const char *name, int _iAppendMode)
> {
>     hid_t           file;
> ...
>
>     file = H5Fopen(filename, H5F_ACC_RDONLY, H5P_DEFAULT);
> ...
>     return file;
> }
> ```
> Best regards, Paul
"
1765503,2019-12-20 16:03:32 UTC,Definitive fix under review @ https://codereview.scilab.org/#/c/21179/
1765503,2020-01-14 08:08:34 UTC,Merged @ http://gitweb.scilab.org/?p=scilab.git;a=commit;h=23ed74868f447cf4f2f0ed54409d8e2a8f86f48d
1765503,2020-02-17 21:42:50 UTC,Still a problem for 20.04 LTS.
1765503,2019-04-16 19:03:22 UTC,Still a problem on bionic even with Scilab 6.0.1-7ubuntu1~18.04 .
1765503,2019-08-07 22:54:25 UTC,"Created attachment 4992
Patches for Ubuntu (18.04 LTS and 19.04) and master branch"
1765503,2019-04-16 19:02:16 UTC,apport information
1765503,2019-12-18 15:00:47 UTC,"(In reply to Paul van Haren from comment #15)

> As per the analysis of Nikolay, the impact of this bug means that ATOMS and many other functions are not available to Ubuntu users.
>
> I've tried installing the latest successful nightly build, but that doesn't work as the customization for Ubuntu/Debian is missing and too many
> environment issues arose. E.g. when starting scilab from the command line, nothing happens, no output, no CPU load. The only think you can do is
> stop the process (^Z) and then kill the stopped job. I couldn't run the stable 6.0.2. version either.
>
> Next, I've tried building from source, but here I couldn't get past the JOGL and javah issue, also reported by Nikolay (the javah issue I could
> work around, but I couldn't find a fix for the JOGL issue).
>
> Effectively, this means that I don't have means to run Scilab, and I guess with me also most of the other Ubuntu/Debian users.
>
> @Stepahne, is there something you can do to raise the awareness on this issue and take measures for a big fix release being pushed to the Ubuntu
> package maintainers?
>
> Thanks and regards, Paul
"
1765503,2019-04-16 19:02:13 UTC,apport information
1765503,2019-04-16 19:02:15 UTC,apport information
1765503,2018-01-31 09:03:10 UTC,"BUG DESCRIPTION:
----------------
Not able to save or load a variable"
1765503,2018-04-25 20:51:33 UTC,Bug exists in Ubuntu 18.04 LTS with all updates.
1765503,2018-05-11 08:28:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765503,2018-05-17 10:17:00 UTC,"Hi,
I am also facing the same problem with exact symptoms as brought out above. Need urgent fix / alternative method to use atoms libraries."
1765503,2018-07-07 18:09:36 UTC,Bug still exists on Ubuntu 18.04 LTS with all updates.
1765503,2018-08-27 16:41:17 UTC,*** Bug 15738 has been marked as a duplicate of this bug. ***
1765503,2018-08-28 14:25:50 UTC,I confirm that this bug is also present under Ubuntu 18.04 64bits.
1765503,2018-08-28 15:36:04 UTC,"Antoine, could you please confirm here that this bug is now fixed on the 6.0-branch and on the master one, for this OS, as you did on users@?
Thanks"
1765503,2018-07-24 15:32:51 UTC,18.10 cosmic is affected too.
1765503,2018-08-28 15:45:52 UTC,"This bug is resolved scilab-branch-6.0-1534494461 and scilab-master-1534776009, at least for Ubuntu 18.04 64bits."
1765503,2019-04-09 07:41:32 UTC,"(In reply to Stéphane MOTTELET from comment #9)

> Currently, no mainstream dist (Ubuntu, Fedora, ...) packaged Scilab 6.0.2 because the packaged 6.0.1 version does not work already. Just try the
> following pair of keywords on Google:
>
> Scilab Ubuntu
> Scilab Fedora
> ...
"
1765503,2019-04-08 19:02:42 UTC,"Currently, no mainstream dist (Ubuntu, Fedora, ...) packaged Scilab 6.0.2 because the packaged 6.0.1 version does not work already. Just try the following pair of keywords on Google:"
1765503,2018-08-28 15:39:30 UTC,"PhiRG,
Could you please try on Debian with the nightly build: http://www.scilab.org/en/development/nightly_builds/branch60
Thanks"
1765503,2019-04-08 16:55:42 UTC,"There are plenty of users who install distribution packages believing they are ""official"" packages that still fail with the same problem. We cannot always say them to install the .tar.gz"
1765503,2019-03-23 11:29:07 UTC,Still broken on Bionic and Disco.
1765503,2019-04-08 18:37:59 UTC,"@Stéphane: I don't understand your rationale for reopening this report.
Do you mean that there are some distributions packaging the official Scilab 6.0.2, with which the reported problem still occur?"
1765503,2019-03-21 14:42:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765503,2018-10-06 12:41:56 UTC,Still broken on Cosmic.
1765503,2018-08-30 09:18:38 UTC,"Hello Samuel,"
1765518,2019-02-05 23:23:06 UTC,"I tested landscape-client and landscape-common for both bionic-proposed and cosmic-proposed.
Then I reset the locale config, enabled script execution, set some fancy unicode tags and ran a script successfully."
1765518,2019-02-07 19:36:27 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu4.1
1765518,2019-02-07 19:38:16 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu3.2
1765518,2018-12-14 11:52:25 UTC,"Hello Gabriel, or anyone else affected,"
1765518,2019-02-07 19:37:06 UTC,"The verification of the Stable Release Update for landscape-client has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1765518,2018-12-14 11:49:36 UTC,"Hello Gabriel, or anyone else affected,"
1765518,2018-06-13 20:49:17 UTC,Easily reproduced by setting accented tags (e.g. éàµ) on a fresh computer. This also appears to affect xenial.
1765518,2018-12-07 09:19:39 UTC,"An upload of landscape-client to cosmic-proposed has been rejected from the upload queue for the following reason: ""Includes a change without an SRU bug attached to it""."
1765518,2018-11-29 19:46:32 UTC,Fix released in disco.
1765518,2018-07-25 14:22:47 UTC,Fix pushed as PR #51 https://github.com/CanonicalLtd/landscape-client/pull/51
1765518,2018-12-07 09:21:25 UTC,"An upload of landscape-client to bionic-proposed has been rejected from the upload queue for the following reason: ""Includes a change without an SRU bug attached to it""."
1765531,2018-05-08 12:04:10 UTC,apport information
1765531,2018-04-20 19:35:44 UTC,"Hello,"
1765531,2018-05-08 12:04:06 UTC,apport information
1765531,2018-05-08 12:04:08 UTC,apport information
1765531,2020-07-23 22:01:50 UTC,./eclim_2.7.2.bin
1765545,2020-09-16 09:18:35 UTC,This is an old bug with an unanswered question from Miguel. I'm marking this as Incomplete. If the problem still visible please put this back to New and provide the requested data.
1765545,2018-04-20 07:59:13 UTC,"@dalvarez, can you try running:"
1765556,2018-05-20 13:42:28 UTC,"Update regarding 17.10 - After switching from GDM to lightDM, logout and login are enough, no reboot required. With GDM, logout and sudo systemctl restart display-manager was also enough and didn't require a full reboot."
1765556,2018-04-24 23:52:14 UTC,"Yes, same thing wit the latest version of Ubuntu 18.04 installed (Fresh install)"
1765556,2018-04-28 20:06:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765556,2018-04-28 20:08:49 UTC,"ubuntu 18.04 and nvidia 340.106 ,nvidia-prime 0.8.8 ."
1765556,2018-04-30 19:25:34 UTC,"The same on Ubuntu 18.04 and nvidia 340.106, nvidia-prime 0.8.8, kernel Linux 4.15.0-20, GeForce GT 540M"
1765556,2018-05-04 10:00:30 UTC,You should read the changelog.
1765556,2018-05-12 00:45:01 UTC,También tengo el mismo problema que detalla el señor.
1765556,2018-05-14 21:09:45 UTC,This also affects me on 17.10.
1765556,2018-06-05 18:41:03 UTC,The prime-select replacement in https://github.com/matthieugras/Prime-Ubuntu-18.04 works without requiring a restart (simply kills and starts again the display manager).
1765556,2018-07-17 10:49:33 UTC,I confirm fargoth #10 about TimRichardson MatthieuGras prime-select with bbswitch
1765563,2018-04-20 11:36:34 UTC,https://launchpad.net/ubuntu/+source/gegl/0.3.30-1ubuntu1
1765564,2018-06-07 01:07:35 UTC,Any progress on the verification for this?
1765564,2018-06-11 15:08:06 UTC,This bug was fixed in the package linux - 4.15.0-23.25
1765564,2018-05-22 00:01:48 UTC,This bug was fixed in the package linux-azure - 4.13.0-1018.21
1765564,2018-05-25 01:02:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1765564,2018-06-11 15:10:16 UTC,This bug was fixed in the package linux - 4.13.0-45.50
1765564,2018-05-24 20:30:42 UTC,This bug was fixed in the package linux-azure - 4.15.0-1012.12
1765564,2018-05-10 19:06:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1765564,2018-05-23 16:37:10 UTC,"Hi,"
1765564,2018-05-22 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765564,2018-05-21 23:58:06 UTC,This bug was fixed in the package linux-azure - 4.15.0-1012.12
1765564,2018-06-14 12:16:29 UTC,This bug was fixed in the package linux - 4.15.0-23.25
1765564,2018-05-23 17:10:20 UTC,We have let affected customers know that this kernel is available and are awaiting their feedback on whether fixing this particular race condition also addressed the issues they are experiencing.
1765564,2019-02-14 16:44:37 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1765578,2019-09-12 13:31:15 UTC,Is this still a problem? Can you post fresh build logs?
1765578,2019-11-12 04:17:45 UTC,[Expired for kolla because there has been no activity for 60 days.]
1765583,2020-04-24 13:34:04 UTC,"very old, n/a"
1765601,2018-04-21 15:39:42 UTC,"There is a preference called ""Edit action changes track width"" that you can disable to prevent this behavior."
1765601,2018-04-21 17:04:55 UTC,"The legacy canvas uses 'E' for changing track width. Initially GAL mapped 'E' to open properties dialog for all kinds of items, but due to frequent user requests, an option to select the behavior has been added."
1765601,2018-04-21 18:33:54 UTC,"It is a handy option, I use it a lot. but it should only be active for tracks when in track laying mode."
1765601,2018-04-27 14:45:19 UTC,"What do you mean by ""track laying mode""?  Do you mean with the Route Tracks tool selected?  ('cause that's the one place it /doesn't/ work today.)"
1765601,2018-04-27 17:45:54 UTC,"Yes, I could not find the right name for it. its thr rout tracks tool. I get the feeling this is the only right mode to change tracks, being it placement or width"
1765601,2018-12-11 19:23:31 UTC,Is this actually a wishlist bug?
1765601,2018-12-11 20:14:28 UTC,This is wishlist.  The behavior is legacy and we can look at better ways to handle it in 6.0  But there's no bug.
1765611,2018-05-17 01:37:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765621,2018-04-20 08:47:57 UTC,apport information
1765621,2018-04-20 08:48:10 UTC,apport information
1765621,2018-04-20 08:48:08 UTC,apport information
1765621,2018-04-20 08:48:07 UTC,apport information
1765621,2018-04-20 08:48:05 UTC,apport information
1765621,2018-04-20 08:48:03 UTC,apport information
1765621,2018-04-24 03:17:59 UTC,"1. I don't update anything on ubuntu VM.
2. I just seen this happen on ubuntu 16.04 LTS and don't test on other version."
1765621,2018-04-20 08:48:01 UTC,apport information
1765621,2018-04-20 08:48:00 UTC,apport information
1765621,2018-04-20 08:47:59 UTC,apport information
1765621,2018-04-20 08:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765621,2018-04-20 20:30:56 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1765621,2018-04-20 08:48:02 UTC,apport information
1765628,2018-10-23 21:42:41 UTC,"Note it is currently not possible to boot the pi in Ubuntu armhf using uefi.  As previously mentioned, the generic kernel is missing pi modules, and Linux-raspi2 is missing efi-stub https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1710517"
1765628,2018-10-23 19:01:42 UTC,"The current thinking seems to be that efi passes grub2 the flattened device tree.  The problem with this is that the dtb is not at all stable.  It is supposed to be independent of operating system, but there are differences between the upstream and rpi foundation kernels.  Grub2 or U-boot can give the user the choice of kernel or even operating system, but it could be fed an incompatible dtb by efi.  Grub2 can load a device tree which solves this, but you currently loose the overlays."
1765628,2020-04-09 11:00:57 UTC,"Going back through old bugs - I think we can mark this ""Fix Released"" at this point; the classic and core images are now unified (while the +raspi2, +raspi3, +cm3 images *appear* to exist in some cases these are now just links to the unified image)."
1765628,2018-12-06 20:51:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765628,2018-10-23 18:20:40 UTC,"I understand why flash-kernel was used, and in the past I myself have suggested its use (https://bugs.launchpad.net/raspbian/+bug/1723203 ).  I've created installers for the pi using ubiquity (https://ubuntu-mate.community/t/aarch64-on-raspberry-pi-2-rev-1-2-3b-3b/16853 ) and the debian-installer, which is why I'm convinced flash-kernel is not fit for purpose on the pi."
1765628,2018-10-23 08:23:54 UTC,"flash-kernel is the thing that puts the bootloader and bootloader configuration in place at the end of installations (the equivalent to grub-install on x86).
It is the interface/API you need if you want to use ubiquity or debian-intaller.
It is also hooked up directly with the kernel debs and automatically run after a kernel update (to adjust bootloader variables, write things to flash on systems where thats needed etc)."
1765628,2018-10-23 00:33:08 UTC,"Oliver, thanks for the comment.  Interesting that core has started to implement this.  I don't know much about snaps/gadgets."
1765628,2018-10-21 11:34:45 UTC,"note that we have the ability to build unified UbuntuCore images, but to my knowledge nobody works on support for this in classic ubuntu images (server/desktop) ..."
1765628,2018-10-21 10:42:13 UTC,"Trying the latest opensuse armhf image, they seem to have a U-boot.bin that works on the pi 2 and 3."
1765633,2018-04-20 11:37:02 UTC,I forgot to mention that restarting the TR server fix the issue.
1765633,2018-04-20 12:56:13 UTC,Thank you for the report. I think I came across this during development last week - the server hostname was not being updated after reloading the configuration. It should be fixed in the upcoming management/monitoring release (which I think will be 3.4.0).
1765633,2018-04-23 07:01:14 UTC,Seems fixed in 3.3.1 experimental release.
1765638,2018-04-20 12:06:49 UTC,"Hmm, seems that that hack was introduced when upgrading to UCA Pike: https://review.openstack.org/510660"
1765638,2018-04-20 09:37:11 UTC,"O.k., comparing with a similar but passing job (http://logs.openstack.org/86/547986/9/check/legacy-tempest-dsvm-neutron-scenario-multinode-lvm-multibackend/b299ddf/logs/dpkg-l.txt.gz) I found a difference:"
1765638,2018-04-20 11:27:42 UTC,This seems to be a packaging bug. The pip installation has a file
1765638,2018-04-20 11:29:37 UTC,This is for version 2.0.3+dfsg-4ubuntu1~cloud0 of python-paste from Queens UCA.
1765638,2018-04-20 12:01:58 UTC,"Ignore the previous statements, the issue did not reproduce itself on a fresh node. Seems devstack-plugin-ceph is the culprit by force-installing PasteDeploy:"
1765642,2018-04-20 12:28:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1765644,2018-04-20 11:42:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1765644,2018-04-20 11:44:14 UTC,"It's intentional that gnome-initial-setup run at first login after being installed. Yes, that means it will run for upgraders. I don't think we want to change that."
1765644,2018-05-03 12:34:29 UTC,I don't think Robert is working on that one
1765644,2018-06-05 14:01:01 UTC,Not sure we're going to SRU this one :(
1765649,2020-03-27 17:18:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765649,2020-07-04 11:43:32 UTC,libpng12-0 1.2.50-2+deb8u3
1765653,2020-07-24 21:40:57 UTC,As the ecryptfs support has been dropped in Bionic+(https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798359) marking bug invalid
1765653,2018-04-20 10:03:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765653,2018-07-24 09:34:44 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1765653,2018-09-05 10:05:18 UTC,"If you run the directory-concurrent.sh for ext4 at the very beginning, it will pass."
1765653,2018-09-14 14:09:57 UTC,"This is a test case issue, and the failure is a false positive. ecryptfs/tests/kernel/directory-concurrent/test.c hang_check() the parent uses select() to check to see if the child process has completed. The child process lets the parent know that its done by writing ""EXIT"" to a pipe. select() is non blocking while read() is blocking, so the select() would timeout after 30s if nothing was read from the pipe, this timeout state is used to detect a hang in rmdir/mkdir. But the test does not take into account of the fact that there is no guarantee that the the order of execution after a fork() will be  child first and then parent. If the parent executes before the child, we hit these false positives."
1765653,2018-09-14 14:15:08 UTC,"With this patch applied, the test case directory-current does not report these false positives."
1765654,2018-04-25 09:11:36 UTC,"Good spot, have fixed the en_GB translation!"
1765654,2018-04-25 08:51:32 UTC,"The issue is in the en_GB translations
https://translations.launchpad.net/ubuntu/bionic/+source/gnome-online-accounts/+pots/gnome-online-accounts/en_GB/91/+translate"
1765654,2018-04-24 18:42:27 UTC,"Seems like it's correctly spelled in the code:
add_entry (grid2, row++, _(""Passc_ode:""), &data->otp_entry);"
1765657,2018-04-20 10:14:21 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/563044"
1765657,2018-05-03 15:46:56 UTC,"Reviewed:  https://review.openstack.org/563044
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=78a03140da92f6618f8a1cbdcb4589ff629cc652
Submitter: Zuul
Branch:    stable/pike"
1765657,2018-07-24 12:24:24 UTC,This issue was fixed in the openstack/kolla 5.0.3 release.
1765664,2018-04-20 10:30:46 UTC,"As I side note... I will submit various Ubuntu patches for nm-applet upstream in the next couple of days. Also, I submitted an upstream patch, that enables building nm-applet against Ayatana AppIndicator."
1765676,2018-05-07 09:49:29 UTC,Is there a kind of rule or guideline in which case to use what? I didn't know about StoryBoard before and for future reference I'd like to know when to use launchpad or StoryBoard.
1765676,2018-07-13 04:54:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582448"
1765679,2019-01-10 20:40:10 UTC,"Change abandoned by Tim Burke (<email address hidden>) on branch: master
Review: https://review.openstack.org/564170
Reason: Thanks for this! I think I finally understand what's going on now -- took me long enough."
1765679,2019-07-22 20:15:35 UTC,This issue was fixed in the openstack/swift 2.22.0 release.
1765679,2019-04-29 05:38:03 UTC,"Reviewed:  https://review.opendev.org/655630
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=d391957fd70a02866615c9c5edc070dbde2b23ea
Submitter: Zuul
Branch:    feature/losf"
1765679,2019-04-25 08:23:01 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/655630"
1765679,2019-04-02 20:15:50 UTC,"Reviewed:  https://review.openstack.org/629926
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=a4298fb3ab071b1284fb7080f92c305c6b1cb445
Submitter: Zuul
Branch:    master"
1765679,2018-09-27 22:12:13 UTC,"Also affects s3api. More generally, I'm pretty sure get_container_info will give you (and presumably cache!!) radically different results depending upon where in the pipeline it was called..."
1765679,2018-04-25 11:38:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564170"
1765679,2018-04-25 11:29:17 UTC,"Change abandoned by Yuxin Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/563564
Reason: Need dependences."
1765679,2018-04-23 10:35:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/563564"
1765679,2019-01-10 20:23:39 UTC,"I finally ""get"" this bug! It took me until I tried to pick up https://review.openstack.org/#/c/436568/ and address your (very astute) review comment to understand..."
1765680,2018-04-23 08:00:29 UTC,Correct url: https://review.openstack.org/#/c/563502/
1765681,2018-04-21 07:59:50 UTC,So the bug is not that new :)
1765681,2018-04-20 14:08:20 UTC,Dropping from critical to high because Alejandro tells me this is not yet affecting production systems.
1765681,2018-04-20 13:46:17 UTC,I see the same behavior here. Investigating.
1765681,2018-04-20 14:00:54 UTC,"This is caused by confusion between the CoI and the APC after translating from the former to the latter. It figures out that o1.org/coi.org is equivalent to o1.org/apc.org, but then tries to look up the AAA server for o1.org/coi.org."
1765681,2018-04-21 00:29:20 UTC,"Oh dear, look at this: https://bugs.launchpad.net/moonshot-tr/+bug/1704184"
1765686,2020-11-16 07:55:51 UTC,Zero crashes after 18.10 so consider it fixed.
1765686,2018-10-25 02:30:06 UTC,"""Incomplete"" makes sense to me because it appears the problem stopped happening after 3.28, and not at all in 3.30. We will need more time to verify that's really true:"
1765686,2018-04-30 07:50:22 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/87e4666825764619cb47f3837f871d88d65dd606"
1765686,2018-12-24 04:17:52 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1765686,2018-04-20 11:57:21 UTC,"StacktraceTop:
 g_str_hash (v=0xca) at ../../../../glib/ghash.c:1894
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0xca, hash_table=0x7fd11804f800) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x7fd11804f800, key=0xca) at ../../../../glib/ghash.c:1153
 emit_signal_instance_in_idle_cb (data=0x7fd118012730) at ../../../../gio/gdbusconnection.c:3714
 g_main_dispatch (context=0x564d6d8f95f0) at ../../../../glib/gmain.c:3177"
1765686,2018-04-21 13:57:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765690,2018-04-20 12:03:59 UTC,"Red Hat issue: https://bugzilla.redhat.com/show_bug.cgi?id=1484411 ""Running wget with -O and -q in the background yields a file wget-log"""
1765690,2018-10-11 19:50:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765691,2018-04-20 15:31:11 UTC,"why this bug is filed for neutron, rather than networking-ovn?"
1765691,2019-05-14 07:49:44 UTC,I think its merged in core OVN. And I also think its been addressed in networking-ovn by setting - reside-on-redirect-chassis option to the logical router ports.
1765701,2018-09-05 23:34:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765713,2018-11-04 13:13:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765713,2018-06-04 19:12:16 UTC,"Make sure that Ubuntu packagers include the patch in https://gitlab.gnome.org/GNOME/evolution-data-server/commit/5c6b22b8eb72ccac07c7e5867aa6074347f7fd78 for https://bugzilla.gnome.org/show_bug.cgi?id=795997 (the patch was merged after the release of evolution-data-server 3.28 in GNOME).
And/or, if you did not set up your Google account via ""Online Accounts"" in the control center / settings but instead in Evolution directly, see https://bugzilla.gnome.org/show_bug.cgi?id=749974#c4"
1765714,2018-04-24 06:57:02 UTC,Could you share anything about the frequency of hitting this issue?
1765714,2018-04-25 08:01:24 UTC,"Hi Frode,"
1765714,2018-06-25 04:17:22 UTC,[Expired for OpenStack hacluster charm because there has been no activity for 60 days.]
1765714,2019-03-20 11:24:54 UTC,Reopening this.
1765714,2019-03-20 14:42:46 UTC,The config-changed hook doesn't attempt to update the credentials in the pacemaker; it looks like it is currently an install only option.  It's obviously useful for it to be configurable on an installed system.
1765726,2018-07-05 18:49:50 UTC,"In Ubuntu 18.04 LTS the repository https://launchpad.net/~shutter/+archive/ubuntu/ppa cannot be used as there are newest packages already in main Ubuntu repositories (universe/graphics). The editing requirement package libgoo-canvas-perl exist in Ubuntu 16.04 LTS but not in 18.04 LTS. There in Ubuntu 18.04 LTS is already the package libgoocanvas2-perl but this did not help as Shutter 0.94 does not recognize that package and ""Edit"" button is greyed out. What would be the solution? E.g. here https://itsfoss.com/shutter-edit-button-disabled/ is still offered old Ubuntu 16.04 LTS packages which do not exist anymore under Ubuntu 18.04 nor Linux Mint 19."
1765726,2018-05-14 17:10:10 UTC,"Sorry, forgot to paste the link..."
1765726,2018-05-14 17:09:43 UTC,"This is the thread on the snapcraft.io forums, in case anybody wants to follow it (or has some idea about snaps and can give me some support). :)"
1765726,2018-05-14 16:40:37 UTC,"That would be great Photon. I rely on Shutter as there are no good
alternatives that stand up in functionality."
1765726,2018-05-14 15:42:50 UTC,"Thanks for clarification! Still, this is important information."
1765726,2018-05-14 13:35:55 UTC,"Photon, I fixed the title for that other bug. I intended it to be for 18.10 but that wasn't what I originally wrote. Sorry!"
1765726,2018-05-07 02:13:06 UTC,having read through all of the comments in an attempt to try fix / restore Shutter functions after a clean install of 18.04 I too feel that this application has been a cornerstone of essential function in ubuntu / debian distros for years. There does not appear to be anything even close in capability.
1765726,2018-05-07 22:47:48 UTC,@Photon: Thank you for pointing out that workaround. I can confirm that following that procedure has resurrected the Shutter edit function.
1765726,2018-05-07 06:34:09 UTC,@MankyGitt: Did you try the workarounds described in the initial bug report?
1765726,2018-05-02 08:13:50 UTC,Here is a more or less complete list of optional dependencies (package names may vary since it is from the Arch Linux PKGBUILD):
1765726,2018-05-02 15:42:15 UTC,"In Ubuntu 16.04 (where all of Shutter's features work after: sudo apt-get install shutter), here are the listed dependencies (revealing Ubuntu package names):"
1765726,2018-07-05 19:29:23 UTC,"Workaround
----------
Download and install following Ubuntu 17.10 packages"
1765726,2018-05-14 08:40:24 UTC,Related: https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1771030
1765726,2018-07-05 21:17:41 UTC,Have to mention that under Ubuntu 18.04 LTS that workaround still is problematic as there will be only black screen and cannot do screenshots. Editing works but useless as whole program is rendering to useless state as there will be black screen. Tested also under Linux Mint 19 MATE (based on Ubuntu 18.04 LTS) and there worked as expected and also system tray icon is there. MATE is basically GNOME2 so you need to hack the applet in order to see system tray icon under GNOME3.
1765726,2019-10-04 13:32:45 UTC,Thank you so much for the PPA! I just finally upgraded from 14.04 and I really like to use Shutter for my work and I had even written a small plugin for it. It would be a real shame to see it go!
1765726,2018-07-11 21:09:10 UTC,"I'm using it happily on 18.04.
I followed the work around on this forum and I have full function."
1765726,2018-08-25 19:23:39 UTC,"Thanks to all for these clear explanations => it's time to quit Shutter for me.
I have replace it by deepin-screenshot: it takes screenshots, allows annotations and it's very easy to use (under Xubuntu it's available in official repo)."
1765726,2018-10-02 16:50:43 UTC,I hope we can figure this one out.  Shutter is simple and quite essential.
1765726,2018-10-13 18:31:05 UTC,I am closing the Ubuntu bugs here. Shutter was removed from Ubuntu 18.10 and we don't intend to bring back the removed libraries to Ubuntu 18.04 LTS.
1765726,2018-10-14 18:08:37 UTC,"Well, the bright side is that 16.04.5 will be supported until 2021. I'll be where shutter works."
1765726,2018-11-19 16:23:51 UTC,Absolutely baffling that it is allowed for stuff like this to be removed without anyone considering the ramifications for the users... what is software without usefulness to its users?
1765726,2018-11-19 16:39:46 UTC,">Absolutely baffling that it is allowed for stuff like this to be removed without anyone considering the ramifications for the users.
"
1765726,2018-11-19 16:41:12 UTC,"Oh, and... Both Ubuntu and Shutter are free software. You get what you pay for. Free software maintainers don't owe you anything, and aren't under any obligation to continue maintaining their software just because you don't want to have to stop using it. Speaking as the maintainer of many free software packages for many years: we do the best we can, but we don't appreciate the sense of entitlement some people demonstrate."
1765726,2018-11-19 17:16:24 UTC,I fully agree and feel with you Jonathan. I hope you know there are lots and lots of people out there that are very appreciative of the work that you and other maintainers do. You might not see or hear them because a happy user is usually a silent user while unhappy users audibly vent their opinion. However they are still there.
1765726,2018-11-19 17:39:04 UTC,I normally upgrade 1 to 2 month prior to each new release.
1765726,2018-11-19 18:50:15 UTC,"Very good to all, I understand that for the Ubuntu team, Shutter has no solution for incompatibility of the dependencies with the new Gnome canons. It is not a solution but for the moment I have been able to make it run without any problem with this PPA, which also comes with support for Ubuntu 18.10: sudo add-apt-repository ppa:ubuntuhandbook1/shutter."
1765726,2019-10-22 09:54:23 UTC,"If you're looking for a Shutter PPA for recent Ubuntu versions (including the latest Ubuntu 19.10), see here: https://www.linuxuprising.com/2018/10/shutter-removed-from-ubuntu-1810-and.html"
1765726,2018-05-01 23:27:18 UTC,"Please add libgtk2-appindicator-perl to the list of packages not being provided in Bionic that impact shutter. As described in Bug #1768032, the lack of that package means that the shutter appindicator doesn't work in Bionic."
1765726,2018-07-11 19:12:59 UTC,It's a shame ! Shutter helped me alot and everyone was really stunned by its features like blurr areas and to add self iterative stamps
1765726,2018-04-30 23:55:07 UTC,*** This is an automated message ***
1765726,2018-04-21 18:56:50 UTC,"Dominique, note that Shutter has many other dependency problems than just libgnome2-vfs-perl"
1765726,2018-04-30 11:51:32 UTC,hey all shutter fans !!!
1765726,2018-04-20 14:19:51 UTC,sudo apt-get install shutter
1765726,2018-04-20 14:47:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765726,2018-04-20 15:28:37 UTC,https://launchpad.net/ubuntu/+source/libgoo-canvas-perl/+publishinghistory
1765726,2018-04-20 15:30:49 UTC,Shutter is in rough shape and unmaintained. It has been removed from Debian Testing and will probably not be included in the next Debian release. It needs to be ported to gtk3 to re-enter Debian Testing.
1765726,2018-04-20 15:31:29 UTC,"Jeremy, well, obviously it has (optional) rdeps, Shutter. :)"
1765726,2018-04-20 15:40:10 UTC,"Jeremy, I see, looks, like a PPA for Shutter and its dependencies is a better solution. It has been dropped to AUR (the equivalent of a centralized PPA) in Arch over a year ago. If somebody feels like stepping up for this task, let me know! Can't do this myself since I have no experience with .deb packaging (didn't even manage to update Shutter's official PPA to 0.94...)."
1765726,2018-04-20 16:29:59 UTC,"After reading Jason Straight's bug-report, perhaps the missing package is not ""libgoocanvas2-perl"", but ""libgoocanvas"" instead. He says:"
1765726,2018-04-20 18:41:35 UTC,"Jeremy,"
1765726,2018-04-20 19:46:50 UTC,"Jeremy, unfortunately, Shutter's only developer abandoned it several years ago. It looks like I am the only one who tries to fix it up at least a little bit (mostly by just applying patches which other people submitted, because I don't even know perl). A port to GTK3 is completely out of scope for me, unfortunately..."
1765726,2018-04-20 19:55:04 UTC,"Lonnie, I completely agree, I also like Shutter a lot and that's why I am trying to fix it up at least a bit. I think, Shutter can survive till the big distros abandon Xorg and completely shift to Wayland. However, somebody would need to take care of packaging Shutter and its dependencies (which are quite some, unfortunately). I maintain Shutter's PKGBUILD for Arch Linux, so it will hopefully remain available for Arch as long as Xorg is alive. OpenSuse still has Shutter in its repos. Gentoo at least ships the old 0.93.1 version. Debian had Shutter in its repos so far, but now somebody would need to take care of the Debian packaging (maybe via a PPA)."
1765726,2018-04-20 22:16:33 UTC,"Photon,"
1765726,2018-04-20 23:55:03 UTC,*** This is an automated message ***
1765726,2018-04-21 00:36:16 UTC,"Unfortunately, I've downgraded from 18.04 back to 16.04.4 due to this issue."
1765726,2018-04-20 18:12:55 UTC,"Photon, Shutter has a good chance of being removed from Ubuntu soon (perhaps for 18.10). It needs to be ported away from libgnome (ideally to gtk3 and GObject Introspection). I apologize for the inconvenience but libgnome has been deprecated for many years."
1765726,2018-04-21 08:50:39 UTC,"Photon, I've done some work to port shutter from VFS to GIO (The dependency on VFS is the main trigger of shutter's removal from Debian. Using gtk2 is less a problem)."
1765726,2018-04-21 06:40:15 UTC,"One possibility to revive Shutter would be to crowdfund a professional to do the necessary development. This worked with Lazarus, a browser extension for saving web forms: https://github.com/lazarus-recovery/lazarus_addon/issues/2 In the case of Lazarus the total money required was about 500$ which was supplied by around 20 users in total. I think, properly organized, this could also be achieved for Shutter."
1765726,2018-04-30 11:26:28 UTC,@wentworth: All thanks goes to the author of the howto and dino99 for posting it in https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1767807/comments/2 :)
1765726,2018-04-30 10:44:54 UTC,"@Photon, I tried your link, it works for me. Great work."
1765726,2018-04-29 20:52:04 UTC,"Hi guys, I have good news and bad news. The bad news is that I still haven't found time to look into the snap thing. The good news is that there are .deb packages for libgoo-calvas-perl available: http://ubuntuhandbook.org/index.php/2018/04/fix-edit-option-disabled-shutter-ubuntu-18-04/ Check it out, does it work for you?"
1765726,2018-04-28 18:33:58 UTC,"I have been using shutter for years and this got me today as well after upgrading to 18.04. I found flameshot https://github.com/lupoDharkael/flameshot and it seems to have the fundamentals. Still I prefer shutter, but I thought I would suggest an alternative."
1765726,2018-04-24 21:16:14 UTC,"Photon, feel free to ask for help on the https://snapcraft.io/ forum if you need it."
1765726,2018-04-30 12:00:33 UTC,"As Jeremy have explained the Debian/Ubuntu removal of libgoo-canvas-perl, its a no sense to request a 'packaging' for it."
1765726,2018-04-24 18:52:06 UTC,"As long as the edit and ftp features work, I'm happy to run a snap of shutter."
1765726,2018-04-24 17:06:31 UTC,"Jason, good idea!"
1765726,2018-04-22 01:10:26 UTC,Sounds like shutter would be a prime candidate for someone to make a snap of? Isn't this the whole reason snaps were created?
1765726,2018-04-21 17:59:59 UTC,"Dominique, I would be glad to contribute but as I wrote above (and also in https://bugs.launchpad.net/shutter/+bug/1006290) I don't really know how to help..."
1765726,2018-04-24 20:37:44 UTC,"I never used (not to mention built) snaps before but I will have a look into it in the next few days. Of course, if anybody with some snap experience volunteers to take care of it, please go ahead! :)"
1765737,2018-08-09 16:48:42 UTC,"Reviewed:  https://review.openstack.org/590072
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=62d3b299367edb63fe618283dab65af11d24cc10
Submitter: Zuul
Branch:    stable/pike"
1765737,2018-08-09 04:13:34 UTC,"Reviewed:  https://review.openstack.org/590068
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4e8318809c38e7a227892c2c4c99500f16f87d6f
Submitter: Zuul
Branch:    stable/queens"
1765737,2018-08-09 02:16:48 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/590072"
1765737,2018-08-09 02:11:41 UTC,"Change abandoned by Chen (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/590068
Reason: Seems not the recommended way to cherry-pick"
1765737,2018-08-08 23:57:37 UTC,"Reviewed:  https://review.openstack.org/580259
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=058ee38c9654af415dcea24deb8ef40476fbf2f0
Submitter: Zuul
Branch:    master"
1765737,2018-07-05 03:24:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/580259"
1765737,2018-08-09 02:08:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/590068"
1765739,2018-05-10 08:07:00 UTC,haproxy just does simple tcp or http checks as configured in the charms - if a backend app service is non-functional this will not be detected.
1765739,2018-05-10 08:08:57 UTC,ftr we use tcp mode to support SSL termination at the service endpoint rather than at the load balancer.  Moving to http/https might be OK but we'd need to validate installation of the appropriate CA cert on the local install.
1765739,2021-01-15 14:41:19 UTC,"Hi, would it be possible to increase the priority higher than ""wishlist""?
We recently had an incident in a live customer cloud where losing a single compute, hosting one of the keystone units brought the service down completely."
1765739,2021-01-15 16:22:58 UTC,"I think bug 1880610 would resolve this one, especially for mysql since haproxy offers a backend-specific check for it."
1765742,2018-06-08 12:25:10 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1765742,2018-05-09 22:01:44 UTC,"Reviewed:  https://review.openstack.org/567232
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0f95b6a898c238b29987001e72447943351d5a77
Submitter: Zuul
Branch:    stable/queens"
1765742,2018-05-15 04:04:03 UTC,This issue was fixed in the openstack/nova 17.0.4 release.
1765742,2018-05-09 17:22:13 UTC,"Reviewed:  https://review.openstack.org/563213
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=717d09149ebea4d6451efb262f2b300cdbcf2208
Submitter: Zuul
Branch:    master"
1765742,2018-04-20 18:22:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/563213"
1765742,2018-05-09 14:12:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/567232"
1765746,2019-09-16 08:42:41 UTC,Migrated to https://github.com/widelands/widelands/issues/3269
1765746,2018-09-30 14:44:45 UTC,Agreed!
1765746,2018-09-30 09:41:39 UTC,"Although there will be no further commits for b20 I'd like to keep this bug open.
I have retargeted it to b21 though"
1765746,2018-07-25 19:40:54 UTC,new values about the calculations regarding needed supply of weapons for training sites due to changes in the other tribes weapon production
1765746,2018-07-24 14:55:46 UTC,added new mine Efficiency overview incorporating the Changes made by WorldSavior
1765746,2018-05-22 06:21:10 UTC,small chnage in production time of helmet
1765746,2018-05-12 21:24:12 UTC,Added some calcualtions about times to produce and to consume weapons and the resulting buildings that need to be build to the training sheet.
1765746,2018-05-06 12:50:45 UTC,I got the mechanism of scraping weapons and now wrong corrected that.
1765746,2018-09-20 20:49:14 UTC,excel sheet with vba to calculate soldier fighting values
1765746,2018-05-04 21:30:39 UTC,as the soldier gets equipped with a second sword and no weapon is scraped the first round of advanced training in the arena doesn't deliver any scrap.
1765746,2018-05-04 21:29:21 UTC,changed some wrong values due to forum inputs
1765746,2018-04-26 21:52:51 UTC,ok here is the mine efficiency excel. In contrary to the other excel sheets the yellow background does not contain suggestions from my side but spots were I noticed strange values. This is spread all over the tribes and barbarians are not really much worse than the others if we ignore the vallue wares per dug ressource.
1765746,2018-04-24 08:47:59 UTC,Here is the second Excel sheet dealing with the build costs of every tribe. I have accumulated the build costs of every single building. Afterwards I have splitted up refined material in the cheapest basic materials available in the economy. Afterwards I modified the build cost in the following way:
1765746,2018-04-20 15:18:20 UTC,"Excel now contains a second Frisian tribe to experiment with
First suggestions to improve the values are marked with yellow"
1765746,2018-04-20 15:10:18 UTC,"here are the current costs of training for all tribes
frisians definitely need too much coal and too much gold as well."
1765746,2018-05-06 12:49:48 UTC,some small changes to reflect forum discussion
1765748,2018-06-07 22:16:54 UTC,This issue was fixed in the openstack/glance 17.0.0.0b2 development milestone.
1765748,2018-06-07 14:12:19 UTC,This issue was fixed in the openstack/keystone 14.0.0.0b2 development milestone.
1765748,2018-05-15 16:51:29 UTC,python-zvm-sdk is now holding openstack back from moving forward on this and finally closing it.  They had a commit blocking >=1.8.0 but no reasoning given.
1765748,2018-05-15 00:03:58 UTC,"Reviewed:  https://review.openstack.org/568304
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f37895dc59f7bc2127b4e1ba8e38ab50e3f1f9cb
Submitter: Zuul
Branch:    master"
1765748,2018-05-14 14:36:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568304"
1765748,2018-05-10 13:22:18 UTC,"Reviewed:  https://review.openstack.org/564883
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=73cc41c9ceb4e38b60ea22402524bae49aa41c32
Submitter: Zuul
Branch:    master"
1765748,2018-04-27 20:52:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564883"
1765748,2018-04-25 15:35:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564255"
1765748,2018-04-25 20:25:38 UTC,"Reviewed:  https://review.openstack.org/564255
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5b00f19109b5f4d2ae229f7e8d79a4c5f0a66492
Submitter: Zuul
Branch:    master"
1765748,2018-04-25 15:25:05 UTC,In the nova `test_wsgi` tests there are two different issues to be dealt with:
1765748,2018-04-25 01:33:56 UTC,"Glance: failures for both py27 and py35, same tests in each:"
1765748,2018-04-24 20:00:19 UTC,As other people have probably noticed the accept handing in webob 1.8.x has completely changed [1] and even though there are some methods that are preserved but deprecated (best_match) they don't behave in the same way that they used to because the underlying implementation is much different.
1765748,2018-04-20 15:53:44 UTC,"Found in this review, see patchset 4's zuul failures in the cross tests for details."
1765748,2018-04-27 12:26:00 UTC,"Glance doesn't have any specific q-value tests broken at this point (we have broken tests, just not those).  Like Nova, we have a glance Request object that relies on the best_match() that is being eliminated by webob.  Using the webob replacement lookup() method doesn't make our tests pass out of the box.  The different behavior has to do with the circumstances under which None is returned by the glance Request object's best_match_language() method."
1765756,2018-12-03 22:41:48 UTC,Is this still an issue?
1765759,2018-09-15 20:12:37 UTC,Workaround is to use xvfb-run.
1765761,2018-04-20 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765761,2018-09-04 02:29:54 UTC,Also:
1765765,2019-02-20 07:26:20 UTC,"Hi Brian,"
1765765,2019-02-20 12:06:06 UTC,i never used ip=dhcp in the boot menu entries.
1765765,2019-02-19 15:03:57 UTC,Works for me on 18.04.1
1765765,2019-02-19 10:44:43 UTC,@beta-tester: Seems to work for me using 18.04.2
1765765,2019-02-20 22:29:41 UTC,"Just to confirm that for me also, 18.04.2 vs 18.04.1 fixes this issue and the systemd resolver is correctly picking up the dns from the non-managed interface that resulted from the network boot with ip=dhcp."
1765765,2018-04-29 04:59:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765765,2018-04-20 20:19:35 UTC,"there is a side note about that issue in report:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777"
1765765,2019-02-20 15:44:54 UTC,"@Guillermo
The OS shouldn't be trying to raise the interface as it's already configured during the boot process. You can't reconfigure the network interface while you're booting from the network :)
You need to modify /etc/network/interfaces on your boot server to set the interface to manual. See step 5 under 'creating your NFS installation' on this page
https://help.ubuntu.com/community/DisklessUbuntuHowto"
1765765,2018-07-31 13:32:19 UTC,still an issue of ubuntu 18.04.1
1765767,2020-03-30 12:02:25 UTC,I am unable to reproduce the issue with inkscape 0.92.4-5 in Debian.  Marking fixed.
1765767,2018-04-20 19:32:11 UTC,"- thank you for taking the time to issue a report.
- problem not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- when I open the second pdf file I find that the second Inkscape has a (docked) layers dialog associated with it as expected.
- when I close the layers dialogs I get no crash."
1765775,2019-11-15 05:41:03 UTC,Thank you for your bug report. Could you add an image triggering the problem to the bug? The report mentions that the desktop used is XFCE so it could also be specific to the environment
1765775,2019-11-15 14:05:32 UTC,The following image is triggering the bug: https://i.imgur.com/To30M5D.png
1765775,2019-11-15 23:36:57 UTC,The bug is in GTK3.
1765775,2019-11-15 23:40:17 UTC,"Upstream stated that it's fixed in gtk 3.24 which is newer Ubuntu series, closing. The bug can still make to target bionic if we believe a SRU for it should be workedon"
1765787,2019-01-29 13:52:21 UTC,Is this still an issue?
1765787,2019-01-29 22:14:06 UTC,not sure. i assume it is.
1765787,2019-11-13 10:20:15 UTC,Is this still an issue?
1765787,2021-02-17 17:07:31 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1765791,2018-04-20 20:28:01 UTC,You may need to run the following from a terminal:
1765791,2018-04-20 17:00:16 UTC,This change was made by a bot.
1765791,2018-04-21 04:14:55 UTC,"Launchpad has finally loaded the missing linux-image-4.15.0-18-generic (and lowlatency).
That makes linux-generic upgrade happy."
1765791,2018-04-20 20:40:24 UTC,"Thanks for the heads up, but does not resolve that issue."
1765796,2018-04-20 23:11:41 UTC,"To be clear, I wouldn't expect it to be able to parse this string, but I *would* expect it to fail validation, instead of causing a 500 response."
1765800,2018-09-20 06:41:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765800,2018-09-20 07:20:09 UTC,"Did you install the driver separately? I got the exact same message before I realized this.
sudo apt install mesa-vulkan-drivers mesa-vulkan-drivers:i386"
1765800,2018-09-20 08:22:33 UTC,"mesa-vulkan-drivers should probably be installed by default, but I'm not sure where the dependency should be added.. perhaps ubuntu-meta?"
1765801,2019-10-31 19:45:34 UTC,"This bug is fixed with commit e8138959 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=e8138959"
1765801,2019-12-19 22:58:15 UTC,"This bug is believed to be fixed in cloud-init in version 19.2-78. If this is still a problem for you, please make a comment and set the state back to New"
1765802,2018-05-02 00:20:11 UTC,"Reviewed:  https://review.openstack.org/565527
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=8951bdee92468b503c3f0430c2c10671fed69803
Submitter: Zuul
Branch:    stable/queens"
1765802,2018-05-01 18:11:43 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/565552"
1765802,2018-05-01 16:06:10 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/565527"
1765802,2018-05-17 05:24:37 UTC,"Reviewed:  https://review.openstack.org/565552
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=1db5b7421eb87d6d5c5d2490212ac1cab0bb28de
Submitter: Zuul
Branch:    stable/pike"
1765802,2018-04-20 22:08:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/563322"
1765802,2018-05-01 09:25:28 UTC,"Reviewed:  https://review.openstack.org/563322
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=039dbccb5d568953e281a21854916b60ad0a98e4
Submitter: Zuul
Branch:    master"
1765805,2018-05-31 18:39:27 UTC,"Change abandoned by Felipe Reyes (<email address hidden>) on branch: master
Review: https://review.openstack.org/565865"
1765805,2019-12-03 14:55:40 UTC,Setting as fix released as the associated c-h change has been merged into ceph-mon charm.
1765805,2018-05-03 20:10:49 UTC,"Reviewed:  https://review.openstack.org/565874
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=644dea83defe44210bffb2d22cba5aab994c5eda
Submitter: Zuul
Branch:    master"
1765805,2018-05-02 20:13:50 UTC,"ceph-osd -> https://review.openstack.org/#/c/565874
ceph-mon -> https://review.openstack.org/#/c/565865"
1765805,2018-04-20 21:32:54 UTC,https://github.com/juju/charm-helpers/pull/156
1765816,2019-09-19 14:47:09 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1765827,2019-10-13 01:05:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765834,2019-11-26 14:28:23 UTC,This issue was fixed in the openstack/swift 2.19.2 release.
1765834,2019-10-23 17:44:40 UTC,"Reviewed:  https://review.opendev.org/689883
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=423f96293b6eb43504b5370e893c280697ed23c9
Submitter: Zuul
Branch:    stable/rocky"
1765834,2019-10-21 21:59:24 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/689883"
1765834,2019-03-28 21:12:53 UTC,"Reviewed:  https://review.openstack.org/648245
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=6afc1130fd753306d64745c9bee7712182b273d3
Submitter: Zuul
Branch:    feature/losf"
1765834,2019-03-27 21:11:13 UTC,"Fix proposed to branch: feature/losf
Review: https://review.openstack.org/648245"
1765834,2019-03-25 17:07:23 UTC,This issue was fixed in the openstack/swift 2.21.0 release.
1765834,2019-03-20 23:53:01 UTC,"Reviewed:  https://review.openstack.org/629301
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=3a8f5dbf9c49fdf1cf2d0b7ba35b82f25f88e634
Submitter: Zuul
Branch:    master"
1765834,2019-01-08 19:50:06 UTC,"Jeremy, that sounds reasonable."
1765834,2018-12-12 13:59:09 UTC,"Is there a means of capturing the headers of a PUT request without an already compromised channel (hacked Swift infrastructure, compromised client system, man-in-the-middle HTTPS...)? Is this commonly deployed via plain, unsecured HTTP for example? If not, I'd be inclined to consider this a security hardening opportunity and continue working the bug in public rather than under embargo."
1765834,2018-12-12 13:46:38 UTC,"It looks like this was never triaged by the OpenStack VMT, so I'm doing that now. Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1765834,2018-12-11 23:32:33 UTC,"Looks like the old patch doesn't apply any more... rebased on top of current master, https://github.com/openstack/swift/commit/f7ca182"
1765834,2018-08-03 21:50:49 UTC,Realized this also affects s3api since it was imported.
1765834,2019-01-11 14:06:08 UTC,"Since it seems like exploiting this situation requires some additional access to begin with, I'm setting the OpenStack VMT's security advisory task to ""won't fix"" for now and tagging the report as a security hardening opportunity. If new information comes to light, we can of course revisit that choice (which also becomes much easier with the report now public)."
1765860,2018-09-21 08:49:33 UTC,"Whenever I try reporting additional circumstances, I get directed to the page"
1765860,2018-09-21 10:15:09 UTC,So I finally figured out how to avoid triggering this problem.  The clue was from dmesg:
1765860,2019-02-02 19:54:19 UTC,"Post scriptum: the USB_BLACKLIST_BTUSB thing only very temporarily appeared to do the trick.  I currently am back at the situation where no matter what I do, blueman-browse crashes with an ""operation still in progress"" exception within an ""operation still in progress"" exception and find no way to make this work."
1765869,2018-04-21 02:54:48 UTC,Able to get this log before this system crashes again:
1765879,2018-12-05 20:33:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765883,2018-04-21 02:05:52 UTC,Please consider the attached debdiff for fixing this bug.
1765883,2018-04-23 04:08:49 UTC,"As I understand it, this is fixed in groovy 2.4.15-1ubuntu1."
1765883,2018-04-21 15:51:41 UTC,This bug was fixed in the package gradle-debian-helper - 1.6ubuntu1
1765888,2018-04-26 14:08:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765888,2018-04-26 14:08:42 UTC,I think this is all a repercussion of using glvnd.
1765895,2019-09-30 19:39:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765897,2019-11-24 07:10:21 UTC,This is my main workstation; fully updated 20.04 system.
1765897,2019-10-12 23:43:04 UTC,"Update - the glitch appears to have gone, or more correctly moved."
1765897,2019-05-14 03:00:48 UTC,"Still the same; on my d960 box, bumped to 19.10 ~9 days after 19.04's release."
1765897,2019-03-07 01:16:09 UTC,this still occurs 2019-03-07
1765897,2018-04-25 02:14:12 UTC,"when I login with ""xubuntu""; i'm getting glitch (about same width of pixels; left of (my upper) monitor 2 in the same spot as under GNOME, but it's static.  The colors are varied, a mixture of black, grey-green-white, brown, white, as if some of a prior wallpaper was left on the monitor when my selected wallpaper was drawn."
1765897,2019-10-12 23:43:18 UTC,"Update - the glitch appears to have gone, or more correctly moved."
1765897,2018-04-21 06:04:46 UTC,"when i reboot, there are no glitches for a few minutes (maybe 2-4 minutes before it starts, long enough that I think its gone then its there)"
1765897,2018-04-21 05:24:20 UTC,maybe related are
1765897,2018-04-21 04:21:56 UTC,note:  I didn't know what package to put; so wrote `gnome` which became meta-gnome3 (via apport)
1765897,2018-04-21 06:06:57 UTC,i when first posting bug it wasn't reacting to keystrokes when typing into chromium. it is this time :(
1765902,2019-06-18 21:34:31 UTC,"The issue looks like bug #1778946 , could you check if the problem is only with name resolution and maybe try the ppp change?"
1765902,2019-06-19 16:31:49 UTC,I update my computer to ubuntu 19.04 and now there is no more problem with ptp
1765902,2019-06-21 15:31:21 UTC,Thanks!
1765908,2018-04-21 19:55:31 UTC,"I'm not sure I fully understand, so please bear with me:
Would rotated guides work for the first purpose?"
1765908,2018-04-21 22:25:23 UTC,"Guide helps, but it's a slow solution to generate perspective vector drawings."
1765914,2018-05-23 03:37:23 UTC,"Interesting! I would think that it should check if unity is actually running before it looks for the unity variables, and if gnome-shell is running it should just look for the gnome-shell variables."
1765914,2018-10-31 11:53:44 UTC,"Hi, same issue here, swing applications are unusable because of the big fonts."
1765914,2018-04-24 01:16:17 UTC,"I've attached a comparison of xrandr's output for Wayland and X11. In Wayland, it only shows the currently configured resolution, whereas in X11 it lists all available resolutions and flags the current one with an asterisk."
1765914,2018-05-17 06:25:54 UTC,"It looks like the code in src/java.desktop/unix/native/common/awt/systemscale/systemScale.c is reading the dconf /com/ubuntu/user-interface/scale-factor value to determine scaling and using the highest setting. When openjdk is drawing windows too large, this is the value:"
1765914,2018-05-22 20:36:06 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1765914,2018-10-31 11:45:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765915,2018-06-20 15:30:05 UTC,Pls help
1765915,2019-08-20 16:23:19 UTC,"Hi,
After testing this route, it seems that some paths might be broken.
The Activity ""Starting at"" option from nbq1 is not available with MSTS."
1765915,2018-04-25 16:57:37 UTC,Pls. add the OpenRailsLog.txt file you get on the desktop after the crash.
1765915,2018-05-09 11:30:39 UTC,Here it is
1765922,2018-12-25 14:53:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765923,2018-06-06 15:11:20 UTC,I had this issue and resolved it by modifying the 10-nvidia.conf file to add the line:
1765923,2018-08-22 17:06:38 UTC,"The driver works properly. However, the configuration is what's at issue (therefore an apt problem). The configuration that's forcible enforced in the xorg.conf.d directory doesn't take into account that some devices have dual video cards. My issue was that there is an onboard Intel video chipset and also a NVidia discrete video adapter in my laptop. The kernel detects Intel and NVidia video cards and loads the Intel drivers... When the X-Windows system loads it detects the NVidia video card and attempts to load the X-Server system for it, but the underling modules haven't been loaded into the system and therefore loads the the black screen."
1765923,2018-08-22 10:44:00 UTC,"I cannot possibly imagine how a blank screen on installing nvidia drivers is an apt problem, so I'm marking that as invalid."
1765923,2018-04-27 14:44:25 UTC,Same symptoms(*) here after a fresh upgrade to 18.04.
1765923,2018-04-27 14:37:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765923,2018-06-06 07:26:16 UTC,"I upgraded from 17.04 to this, and can't get to a desktop now.  Really regretting using ubuntu, yet again.  This is a dell xps 15 9550, I finally had to try an upgrade due to various weird issues with 17.04 still, but at least it worked vs. now.  Might try nouveau as recommended."
1765923,2018-04-23 10:46:04 UTC,Is this a machine with hybrid graphics?
1765923,2018-04-21 10:21:19 UTC,Installing GDM3 does lead to a system which will not boot to a black screen.  Note you will need to change the desktop session to plasma to get to kde.
1765923,2018-04-21 09:32:44 UTC,This is what I get when I log out of X and run sddm
1765923,2018-04-26 13:07:17 UTC,Yes it does have hybrid graphics.  I also use an external GPU.  This occurs with or without the EGPU plugged in.
1765926,2018-04-21 19:10:30 UTC,Thanks for tracking this.
1765926,2018-04-22 08:52:02 UTC,"> That's what I tried in the original Tango skin with a widget stack, but that didn't work on some version of Mac OS.
"
1765926,2018-06-30 10:38:25 UTC,as discussed in https://github.com/mixxxdj/mixxx/pull/1623
1765933,2020-10-02 16:25:43 UTC,"so apt in xenial doesn't have support for inrelease-path, which i guess is pre-requisite to build xenial images at point-in-time."
1765933,2020-10-07 00:51:01 UTC,"Ayub, please do not change the status of bug reports. Thanks."
1765933,2018-04-21 11:18:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765933,2020-10-02 16:20:25 UTC,Is the status of this bug accurate? across xenial..focal spectrum?
1765933,2020-10-02 16:53:47 UTC,"The status of this bug is accurate.  Please see the linked merge proposals for more information; the current blocker is me dealing with a complex set of review feedback on https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/373971.  After that, it will still remain for somebody to work out how to integrate this usefully into livecd-rootfs."
1765935,2018-05-14 19:53:31 UTC,The same error with Sony Vaio notebook. Kernel 4.15 is affected. I successfully boot with previous kernel.
1765935,2018-05-14 19:50:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765935,2018-07-26 07:00:54 UTC,"Same error here with a Dell Precision 3530. I kind of work around the issue with the acpi=off but some others issues appear after that, at least with the workaround you can boot"
1765935,2018-04-21 11:41:59 UTC,"I upgraded the bio manually to 1.7.0 and reinstalled Ubuntu. This Had No effect on the tpm Error described above which occurred again after hitting ""restart now"" at the end of the Installation, Just fyi"
1765935,2019-05-15 05:57:43 UTC,"Same error with a new 18.04 install on a Lenovo thinkpad.
Has this bug been fixed guys?"
1765938,2018-10-30 08:54:10 UTC,I upgraded to 18.10 and it seems the issue is now fixed. Cinnamon now works :) at least for me...
1765938,2018-06-17 14:31:52 UTC,I had the exact same problem. Removing gnome-user-share did the trick - I was able to log in to Cinnamon after a reboot.
1765938,2018-10-29 23:27:48 UTC,"On 18.10, I appear to have had the same issue, and I can confirm that installing cinnomon-desktop-environment +recommends did help in my case. I do not have gnome-user-share installed."
1765938,2018-05-03 08:22:44 UTC,Can you please change the importance since that issue makes cinnamon unusable which is the only desktop which can handle full screen WINE applications properly.
1765938,2018-05-03 08:21:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765938,2018-04-22 17:36:40 UTC,"Thanks for the suggestions... I have cinnamon-desktop-environment and all recommends, as well as gnome-user-share and it still can't login using cinnamon :("
1765938,2018-04-21 15:12:54 UTC,"I suppose that can be something as recommends missed or something that can cause unexpected issue.
FWIK install with cinnamon-desktop-environment including recommends solves many issue (major of cases about only one or more part)
Another thing that can cause issue spotted by some users seems gnome-user-share.
If you already install cinnamon-desktop-environment including recommends and gnome-user-share is something else that need more info and/or debug"
1765946,2018-08-25 17:00:17 UTC,Same here. Fresh install. Thank you.
1765946,2020-08-26 13:53:58 UTC,Same here:
1765946,2020-08-19 18:08:48 UTC,"Problem confirmed on Linux Mint 20 Ulyana (Cinnamon) after upgrading from Mint 19.3 (Cinnamon). Same thing, missing icon, can click on it and see the Solaar menu."
1765946,2020-08-15 03:28:18 UTC,Same here Ubuntu 20.04 / Budgie.
1765946,2020-07-25 14:16:48 UTC,"I confirm that there is no standard solaar icon on the panel.
I'm running LinuxMint 19.3 / cinnamon"
1765946,2020-07-11 08:07:10 UTC,Confirming no icon in sys tray on upgrade from Mint 19.3 to 20. Blank space where icon should be and the solaar menu when that space is left clicked.
1765946,2018-08-11 13:05:28 UTC,Same here. Might this perhaps be due to GTK3? Just asking...
1765946,2019-12-29 18:00:48 UTC,"Me too / XFCE. A dirty workaround I just discovered is to make Solaar a favorite in Whisker Menu, then ""add it to Panel""."
1765946,2018-05-03 19:14:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1765946,2020-07-03 10:45:36 UTC,same problem here on linuxmint 20 cinnamon. latest solaar with no icon in systray.
1765959,2018-12-21 16:49:48 UTC,@rharding @anastasia-macmood @wallyworld bump
1765959,2018-08-14 07:19:15 UTC,"See discussion in https://discourse.jujucharms.com/t/juju-storage-maas/142/3 for an explanation. It looks like Juju is mistakenly rejecting a unit deployment with non-dynamic storage because it rejects *all* placement directives, rather than *just* machine and container placement directives."
1765959,2019-01-09 05:58:06 UTC,https://github.com/juju/juju/pull/9607
1765960,2018-04-23 08:01:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1765962,2018-04-24 07:07:31 UTC,"Reviewed:  https://review.openstack.org/562913
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=fb3af49462954ed0f6604ea9a0606f5a5efeb1ae
Submitter: Zuul
Branch:    master"
1765962,2018-04-24 07:07:25 UTC,"Reviewed:  https://review.openstack.org/563425
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=099df4a174f8e1dbf29197bea1052a9d9a71d66c
Submitter: Zuul
Branch:    master"
1765962,2018-04-24 06:50:21 UTC,"Reviewed:  https://review.openstack.org/563426
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=142f49f46aaa536ed45a750276cd6db41248bb8d
Submitter: Zuul
Branch:    master"
1765962,2018-04-21 15:06:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/563425"
1765962,2018-04-21 15:22:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/563426"
1765963,2019-09-17 07:27:39 UTC,Migrated to https://github.com/widelands/widelands/issues/3270
1765964,2018-07-10 12:04:27 UTC,"@james beedy,"
1765964,2018-12-10 21:38:13 UTC,@anastasia-macmood I've tried everything I can think of. @uros-jovanovic has even taken a stab it it to no avail.
1765964,2019-01-25 13:35:06 UTC,"Interesting results when trying to deploy mariadb and gitlab charms [0], things don't seem to clean up properly and I hit this error [1] with a CAAS model."
1765964,2019-01-25 13:48:38 UTC,"got another CAAS model stuck in destroying, this one seems stuck for a different reason https://paste.ubuntu.com/p/GcnHbZcqPC/"
1765964,2019-01-25 21:17:43 UTC,The errors in the pastebins show i/o timeouts talking to 54.186.60.236 which is probably the k8s master node. It does appear to be issues with the underlying cluster and/or cloud on which k8s is running. You'll need to look at k8s logs and/or CDK logs to see what's happening. Juju is just reporting the errors.
1765964,2019-05-07 02:06:59 UTC,"We have done a lot of work in 2.6 around destroying models, applications and units."
1765965,2019-01-25 17:28:37 UTC,This still happens.
1765965,2019-08-13 17:01:14 UTC,"Fixed in revision c2d77a73007b61ae8a6aaf41aefadec988ae27c3
https://git.launchpad.net/kicad/patch/?id=c2d77a73007b61ae8a6aaf41aefadec988ae27c3"
1765965,2019-08-13 17:00:31 UTC,"While this doesn't reproduce on OSX, I've added some code that I hope will prevent it on MSW."
1765965,2018-04-23 09:28:23 UTC,"Fixed in revision cfa99168369b881e3a0a024decfc8896bae86745
https://git.launchpad.net/kicad/patch/?id=cfa99168369b881e3a0a024decfc8896bae86745"
1765965,2018-04-23 18:14:11 UTC,"Print button becomes active if the printing dialog is reopened, allowing to crash KiCad."
1765969,2018-04-21 16:29:22 UTC,"Since the store isn't secure, we should still have a warning there. Since it's not stored securely, I'm OK with it not being 100% accurate - it will make people err on the side of caution."
1765969,2018-04-22 16:55:35 UTC,Keeping the warning sounds reasonable.
1765969,2018-04-23 08:17:51 UTC,The password edit box can be solved for Build 21. We need:
1765969,2018-04-23 17:05:24 UTC,"Storing some dynamic password data on the server is an interesting idea, I haven't considered that approach yet. A disadvantage: Using Widelands on two computers no longer works without entering the password quite often. But this is a problem some other approaches share, too, so I guess we have to decide whether we want to support that."
1765969,2019-09-16 14:25:37 UTC,Migrated to https://github.com/widelands/widelands/issues/1703
1765970,2018-04-21 19:21:05 UTC,"Could you try with current head-of-git (the 2.12 rc4)? We adjusted our logic for setting up the initial reserved space since 2.11 -- it may well not fix this bug, but maybe we'll be lucky..."
1765970,2018-04-21 19:37:00 UTC,"Unfortunately, no dice"
1765973,2018-04-22 10:35:09 UTC,"Okay, fine by me."
1765973,2019-09-16 08:43:14 UTC,Migrated to https://github.com/widelands/widelands/issues/3271
1765973,2018-04-21 16:32:13 UTC,I'm in favor of removing it for Build 21. The mix will make it easier for users to make the transition and not get login errors when they have just updated.
1765979,2020-01-13 12:32:40 UTC,Does anyone have a temporary workaround?
1765979,2020-05-23 18:27:10 UTC,This has happened to me after I installed the 'flatpak' package. Uninstalling it solved the problem.
1765979,2018-04-21 20:53:26 UTC,"Everything works under X11, while still using zsh, how is that specific to zsh?"
1765979,2020-06-13 08:10:10 UTC,"Thanks Bruno, uninstalling Flatpak makes Snap icons appear in Wayland sessions."
1765979,2020-01-13 12:25:49 UTC,Switching the default shell to bash makes the icons appear again.
1765979,2020-06-01 06:52:51 UTC,"$ snap --version
snap    2.44.3+20.04
snapd   2.44.3+20.04
series  16
ubuntu  20.04
kernel  5.4.0-33-generic"
1765979,2020-01-13 11:56:21 UTC,I have the same issue. Launching snap apps works after sourcing /snap/bin though. Application icons are still missing...
1765979,2018-04-21 20:21:53 UTC,for zsh see bug 1640514
1765979,2019-08-19 19:31:34 UTC,+1
1765979,2019-03-18 12:11:23 UTC,Happens to me when using fish.
1765979,2019-02-27 19:13:13 UTC,"This is also the case in Ubuntu 18.10. I installed PyCharm Professional from a snap package, and I can't find it in the GNOME launch menu (by hitting the Super/Windows key). The only way to launch it is by running the `pycharm-professional` command in the terminal. Once it is running, it's not possible to pin it or drag it into a different position in the dock panel."
1765979,2019-10-15 11:05:47 UTC,This looks like an interaction between:
1765979,2018-04-21 16:59:44 UTC,This seems similar to the issue recently reported in Fedora...
1765980,2019-03-14 07:02:59 UTC,It's is mainline since v4.20-rc6. Have you tried it?
1765980,2019-02-21 18:08:43 UTC,"While digging into this - I found the following commit which might contain a fix:
https://github.com/torvalds/linux/commit/ebaf39e6032faf77218220707fc3fa22487784e0"
1765980,2018-11-02 15:52:54 UTC,"This has expired, but affects me too here.
I'm specifically using Proxmox, which uses Ubuntu for upstream kernel - currently at 4.15.18, and I see the same symptoms.
Specifically LXC, specifically at stop and specifically kworker using 100% of one core and preventing startup of other containers.
I've found that this isn't present in Proxmox's own kernel 4.15.10-1 specifically."
1765980,2018-06-24 04:17:52 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1765980,2018-06-24 04:17:51 UTC,[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.]
1765980,2018-04-24 20:31:17 UTC,"So far I have not been able to reproduce it on the mainline kernel linked above.
However, given the intermittent nature of the problem, I'm not convinced that this was actually fixed.
The source code related to the underlying root cause looks unchanged, and the symptoms may well be hidden away for my load pattern by unrelated changing resulting in different kmalloc behavior."
1765980,2018-04-23 19:57:38 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1765980,2018-04-21 18:01:50 UTC,"The cause of the issue is already understood, and the machine currently isn't running an unmodified kernel for debugging reasons. Apport logs won't help here.
Contact me if you need specific information."
1765980,2018-04-21 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765995,2018-05-08 18:17:13 UTC,This change was made by a bot.
1765998,2020-03-16 10:24:57 UTC,See also: https://github.com/lxc/lxd/issues/7029
1765998,2019-03-03 17:23:59 UTC,"I see, thanks for the info."
1765998,2020-03-19 10:25:33 UTC,Recently hit that on Focal due to the fact that quotas were enabled by LXD.
1765998,2019-02-26 13:11:00 UTC,I confirm I'm having this problem too since migrating to Bionic from Xenial.
1765998,2018-04-24 21:08:03 UTC,"This issue appears to be an upstream bug, since the bug still exists in mainline without a revert. Would it be possible for you to open an upstream bug report[0] and maybe ping the patch author?
 That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1765998,2019-03-02 06:08:15 UTC,"Hm, it's been a while...
I think back then I made some btrfs developers aware of it on IRC, but never got around to sending it to the mailing list.
I'm running my own kernel builds for now (I had to do that to fix some other issues anyway) with the patch from comment #4 applied, which seems to reliably fix this issue."
1765998,2018-04-23 19:03:57 UTC,This patch seems to fix it for me (running that for several days now).
1765998,2018-04-23 18:48:00 UTC,"I tried to build a Bionic test kernel with commit fb235dc reverted, but it does not revert cleanly and requires a back port.  Do you have the back port you performed and can post to the bug?"
1765998,2018-04-21 20:43:19 UTC,"I cannot run the affected (production) system using a broken kernel, and it will lockup after boot within seconds.
If necessary, I can provide additional information or testing upon request."
1765998,2018-04-21 18:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1765998,2018-04-23 20:20:08 UTC,I can confirm that the issue still exists in the mainline kernel build linked above.
1766003,2018-04-21 20:24:30 UTC,"The loop form doesn't even have any dynamic-extent declarations, so I'm not sure how you're comparing them."
1766003,2018-04-21 20:14:13 UTC,"Ok, I misspoke. note, not warning. I still don't see why the do form issues a note but the loop form doesn't."
1766003,2018-04-21 19:47:36 UTC,There's no warning in your first form either.
1766003,2018-04-21 19:11:41 UTC,Because it's the initial value of I.
1766003,2018-04-21 19:37:49 UTC,Why is the behavior of do so different from:
1766020,2018-11-19 21:58:59 UTC,sudo rm /usr/share/python3/runtime.d/hplip-data.rtupdate
1766020,2018-11-22 17:26:08 UTC,"Same problem, solution in #9 helped me.  (I am running Linux Mint 19)
saludos"
1766020,2018-11-21 07:32:44 UTC,Thank you very much #9 helped
1766020,2018-11-24 17:22:52 UTC,"Same problem, solution in #9 helped me. (I run Linux Mint 19 as Juan (13)).
Thanks all!"
1766020,2018-11-21 01:26:36 UTC,"Same problem, solution in #9 was good"
1766020,2018-11-21 00:29:27 UTC,"Same problem, solution in #9 helped me."
1766020,2018-07-26 12:59:31 UTC,"I have the same problem trying to back up my system using Deja Dup. When I try to run the app, I first get a message that I need to install package  gvfs-backends"
1766020,2018-04-24 16:50:40 UTC,"running python rtupdate hooks for python3.6...
E: py3compile:183: cannot create directory /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or directory')
...
error running python rtupdate hook hplip-data
dpkg: error processing package python3 (--configure):
 installed python3 package post-installation script subprocess returned error exit status 4"
1766020,2018-07-16 01:07:23 UTC,Output from hp-check -rt.
1766020,2018-07-16 01:06:33 UTC,"I have just struck this bug on 18.04LTS - not when installing hplip (it has been installed & working for weeks) but when doing an ""apt -y upgrade""."
1766020,2018-05-03 13:54:04 UTC,"Hi Brain,"
1766020,2018-04-24 09:05:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766020,2020-02-12 11:35:40 UTC,I have started to address remedy 3: bug 1862926.
1766020,2019-01-25 22:41:36 UTC,"dpkg: error processing package python3 (--configure):
 installed python3 package post-installation script subprocess returned error exit status 4
dpkg: dependency problems prevent configuration of gnome-online-accounts:
 gnome-online-accounts depends on python3; however:
  Package python3 is not configured yet."
1766020,2018-07-16 12:47:27 UTC,"Same problem, this helps me."
1766020,2020-02-10 17:54:13 UTC,What happens in the following (taken from the attachment of comment #5):
1766030,2018-10-29 06:39:30 UTC,"FYI the fix is in 3.0.0beta5, but so far not yet any released version.
So we will have to wait a bit to pick it up."
1766030,2018-04-28 23:19:38 UTC,I have reported it: https://github.com/hishamhm/htop/issues/785
1766030,2018-10-29 17:05:15 UTC,"Strange, to me 3.0.0beta5 is not fixed, it still has the color difference in virtualization load between the help and the meters."
1766030,2018-10-30 06:21:59 UTC,"Well I was not testing it, but only following the upstream issue and the fix referred there:"
1766030,2018-04-24 10:46:53 UTC,"Hi Leonardo,
Thank you for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue."
1766030,2020-10-01 11:10:29 UTC,Fix released in htop 3.0.0
1766043,2018-04-23 00:39:39 UTC,"Well, I am unsure exactly which information you want, so I will provide what I think you want with how I obtained it. If this is not what you want, let me know."
1766043,2018-04-23 00:12:44 UTC,What video drivers are in use?
1766047,2018-04-22 06:05:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766047,2018-04-23 07:20:27 UTC,Thanks for your suggestion.
1766047,2018-10-03 13:36:05 UTC,Not a bug in ubiquity or grub2. This will need changes in debian-cd (if I'm not mistaken) in how we generate the menu for live CDs.
1766048,2018-04-22 08:22:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1766048,2018-04-26 06:03:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766051,2018-04-22 06:05:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766056,2018-04-24 06:52:54 UTC,"I've been hit by this one again, testing the second spin of the kubuntu bionic final ISO. This time I got a photo of the error message, which I will transcribe below and attach if possible.
[   0.0000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x20 (or later)
[   0.040000] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae0000000040110a
[   0.040000] mce: [Hardware Error]: TSC 0 ADDR fef86f00 MISC 38a0000086
[   0.040000] mce: [Hardware Error]: PROCESSOR 0:40651 TIME 1524542899 SOCKET 0 APIC 0 microcode 1c
[   0.045483] ipmi:dmi:Invalid offset: 0"
1766056,2018-04-22 08:05:44 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766056,2018-04-23 23:57:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766056,2018-05-30 18:04:59 UTC,If you are unable to install the new microcode that may be a kernel problem.  Certainly doesn't have anything to do with ubiquity.
1766063,2019-04-22 17:29:00 UTC,This bug was fixed in the package xkeyboard-config - 2.26-2ubuntu1
1766063,2019-04-14 15:56:34 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=106169 is done
1766063,2018-04-23 05:23:29 UTC,"Not sure what you consider was done. That repository imports automatically from the upstream one. What I said, i.e. that it will be included in the xkb-data package only in 18.10, still stands."
1766063,2018-04-23 04:14:08 UTC,"Done
https://bazaar.launchpad.net/~alexeyten/xkeyboard-config/master/revision/1961"
1766063,2018-04-22 16:43:00 UTC,Thanks for your report and your patch!
1766068,2020-05-17 07:46:55 UTC,"Bump, @juliank !"
1766068,2020-01-22 17:37:49 UTC,@juliank is there any update on this bug? Did you ever get the chance to look at my patch?
1766068,2019-06-25 16:16:39 UTC,"Please submit this patch to Debian, where it will flow down to Ubuntu."
1766068,2020-05-29 15:35:07 UTC,Two years now since I submit this bug report. Any news?
1766068,2019-06-25 19:30:58 UTC,"Simon was a bit wrong, as the upstream situation is reversed, but either way, I guess it's me taking a look at it :)"
1766068,2020-06-02 22:25:07 UTC,This bug was fixed in the package command-not-found - 20.10.0
1766068,2020-06-02 22:35:57 UTC,"Thank you very much, juliank!"
1766068,2019-05-16 05:17:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766068,2020-05-31 22:46:35 UTC,"Unfortunately not. @juliank seems to have gone incommunicado on this issue.
Since I have a patch that fixes this issue, would it be helpful to people if I make a PPA containing the patched command-not-found? Then at least there will be a solution for people until someone from Ubuntu eventually picks this up (which realistically isn't looking likely any time soon)."
1766068,2019-05-14 20:24:22 UTC,"The attachment ""Remove --no-failure-message from zsh_command_not_found"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1766068,2018-04-22 15:06:42 UTC,It worked in Ubuntu Xenial because it ships Zsh 5.1 and the new behavior was introduced in Zsh 5.3.
1766068,2019-05-14 18:45:01 UTC,I raised the equivalent bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927876
1766068,2019-05-06 16:02:25 UTC,The bug is still reproducible with Ubuntu 19.04.
1766068,2018-11-08 12:10:17 UTC,Any news about this issue?
1766068,2018-07-01 17:38:41 UTC,"Actually, maybe I spoke too soon: there's an if guarding the definition of the function at the top of that file."
1766068,2018-07-01 17:38:00 UTC,The first line of the handler is also somewhat problematic. Namely:
1766068,2018-05-03 19:36:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766068,2020-08-18 17:04:05 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1766068,2018-04-22 15:05:40 UTC,I've found the origin of the problem.
1766068,2018-04-22 10:48:51 UTC,It works out-of-the-box in Ubuntu Xenial.
1766068,2019-05-14 18:49:45 UTC,"I have added the above patch to remove the --no-failure-message flag, which seems to fix the problem (I have also bumped compat and standards versions).
Please consider applying the patch and releasing a new version of the package."
1766075,2018-07-08 20:15:44 UTC,"I think I am experiencing the same issue. Upgrade to Ubuntu 18.04 failed.
Startup does not complete and screen sequences through: blank, startup console output and corrupt/uninitialised screen with lots of colours.
Log in almost impossible on other console as screen switches back.
Managed to log in via ssh from a laptop and captured first 1000 lines of output from dmesg - see attached.
From ssh login on 8th July managed to upgrade all packages but problem persists."
1766075,2018-04-24 07:58:05 UTC,I've also reported it to kernel.org
1766075,2018-04-24 07:57:35 UTC,Yes this happened after an update and affects all linux kernels.
1766075,2018-04-23 05:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1766075,2018-04-23 20:10:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1766076,2019-03-18 08:56:18 UTC,I'm seeing this on XPS 15 9570 with TB16 dock.
1766076,2019-12-12 09:21:41 UTC,"The delay to connect the USB devices seems to be a feature of the new firmware or something - on MS-Windows it takes even longer, about 30 seconds for all the devices to finish connecting. Could it be that the xhci_hcd failure is caused by the fact that the dock is now so slow to respond?"
1766076,2019-12-09 12:22:40 UTC,"I just went back to using my Precision 5520 with the TB16 dock, after that duo was benched for a few months while I waited for a replacement battery to be shipped, and now the situation is similar but worse:"
1766076,2019-11-14 21:57:42 UTC,The lastest journal log I saw right when I lost connectivity to HDMI and ethernet follows. There was no other logs associated. No clue if this is relevant.
1766076,2019-11-14 20:42:49 UTC,"Dell Precision 5530
Latest 5530 BIOS (1.13.0)
ikling usb-c hub
5.0.0-32-generic"
1766076,2019-10-27 08:02:42 UTC,"I have a similar problem with a USB mouse, except in my case:
* Unplugging the mouse from the dock and replugging it fixes the problem.
* If I do nothing, the kernel appears to disconnect and reconnect the mouse with a new device number, and it works again until the next hang."
1766076,2019-05-10 15:30:06 UTC,"In case this is useful: updating the Dell XPS 15 9560 BIOS to 0.1.14.2 and Dell TB16 dock and component firmware (packaged as version 1.0.2) seems to have resolved this for me. It's been a week and I haven't seen the issue since: previously, I was seeing it around once per day. I've been unable to trigger it by e.g. connecting various USB devices (USB-A storage &/or network adaptor, USB-C HDMI adaptor) to every port on the dock and laptop. I have two Dell U2715H monitors connected via one mini-DP to DP cable, daisy chained to the second monitor, and a few USB storage devices occasionally connected to the docking station's USB-A ports."
1766076,2019-05-01 17:03:31 UTC,My current complete workaround is documented here: https://gist.github.com/guss77/1356e5f3be4f2acbc73053cc6d3c0b1c
1766076,2019-04-28 09:57:02 UTC,"I haven't had that issue for a while, since kernel 4.20, I think, but I just had this issue again, on up to date 19.04 with kernel 5.0.0-13:"
1766076,2019-04-26 11:22:05 UTC,Dell 5530 fw1.8.1 w/TB16 fw 1.0.2. Tested on 5.0.9-200.fc29.x86_64.
1766076,2019-04-25 13:45:01 UTC,Still seeing this on 5.0.8 mainline. Connecting a USB device after a few hours results in this:
1766076,2019-04-08 09:05:04 UTC,Still seeing this on 5.0.6. PPA mainline. Booting windows prior to linux is WAR for me. Dell 5530 w/TB16. Don't think it is fixed in 5.
1766076,2019-04-08 08:45:29 UTC,"I've been running disco for a while with `generic` Ubuntu kernel 5.0.0 (currently 5.0.0-8), and I haven't experienced that problem for a while."
1766076,2019-04-05 17:48:05 UTC,I had seen this issue on a Precision 5510. I am running the 5.0.x kernel series for a while now and haven't had any issues so far. Currently on 5.0.6.
1766076,2019-04-05 11:29:24 UTC,"Started seeing something similar on Precision 5520 with TB16 dock after a recent kernel update. The original 4.18 worked fine, but 4.18.0-16 and 4.18.0-17 are definitely affected, possibly some earlier ones too."
1766076,2019-12-12 12:13:49 UTC,"For those who don't use Ubuntu, please see if reverting this helps:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a1092b13468839b1a864b126cacfb72ad016"
1766076,2019-05-01 16:06:41 UTC,"I'm running into a similar issue with an HP Zbook Studio G4 running Ubuntu 18.04, HP Thunderbolt 3 dock and an IOGEAR 3.0/4 Port Peripheral Sharing Switch (GUS434).  Often shortly after I switch back to the HP using the USB switch I get the xHCI host controller not responding, assume dead message.  Based on Oded's input above I created the following service to fix it for me:"
1766076,2019-12-25 09:30:45 UTC,"Just had the ""unknown event type 15"" error happen again, with the lp1766076 kernel and current firmware:"
1766076,2020-07-06 09:11:48 UTC,@ #97
1766076,2020-04-09 08:55:58 UTC,"Disabling Thunderbolt Security in the BIOS stops this from happening. This was the only workaround that worked for me.
Not saying this is a fix, but this may help you in finding the root cause."
1766076,2019-03-13 07:52:42 UTC,Dell M5530 1.8.1 w/TB16 1.0.2.  TB16 firmware flashed in Win10 fails on MST2 firmware.
1766076,2021-02-14 07:50:14 UTC,"#110 (Toumas) - I no longer experience this problem when running 20.10 with the latest kernel and the latest Dell firmware update (fwupdmgr works reasonably well, but you can also just download the firmware file from Dell, put it on a USB dok and the preboot screen lets you apply it directly - no MS-Windows needed)."
1766076,2021-02-10 20:36:46 UTC,Few months ago I gave up and stopped using my TB18. Easier to connect few cables once a day than fight with this. I'm much happier now. TB18 serves as an expensive laptop stand for me (elevates laptop 5 cm from table).
1766076,2021-02-10 20:15:37 UTC,My keyboard just dropped out after a few hours with `5.10.0-1008-oem` build. It's working again after the unbind/bind sequence from above.
1766076,2021-02-10 18:30:24 UTC,"I'm pretty confident I'm experiencing this same issue with a TB16 on ""Dell Inc. XPS 15 7590/0VYV0G, BIOS 1.9.1 12/14/2020"""
1766076,2021-02-07 17:14:25 UTC,"#106 - please open a separate issue to debug this.  The architecture for the WD19TB is very different than the TB16 and it shouldn't be conflated into this issue.  The most interesting things to include in your issue - please first try this kernel: https://launchpad.net/ubuntu/+source/linux-oem-5.10.  If it persists, can you please open an issue with 'ubuntu-bug linux-oem-5.10' which will attach all the logs to your issue?"
1766076,2021-02-07 16:58:46 UTC,"I have a very similar issue with a WD19TB under Ubuntu 20.04 (Dell Latitude 5410) and desperately browsing the net, looking for solutions."
1766076,2020-11-03 15:11:49 UTC,"Georgi, if you can afford it I would switch from the TB16 to the WD19TB. The latter works much better from my experience and what I read online."
1766076,2020-10-26 21:20:49 UTC,"I used to run into this regularly before and just recently ran into it again with the TB16. Previously I had the same issue with a different USB hub without a dock, occurring both on Windows and Linux Dell 5520 and Dell XPS 9560. Without the dock both systems were able to recover. With the dock, only Windows recovers successfully."
1766076,2020-10-03 21:53:34 UTC,"This is annoying I bought a Gigbyte 4 TB tb3(usb-c) drive to daisy chain, but it disconnects and I have to restart to get it back, and I also lose access to the things down the chain..."
1766076,2020-09-27 01:54:17 UTC,Found this in my syslog but no indication of why it happens.
1766076,2020-09-27 00:57:04 UTC,"Just to clarify. My peripherals are still powered on, show up in lsusb, and /proc/bus/input/devices, but no input is captured by my desktop. Happens on both Wayland and X11."
1766076,2020-09-27 00:48:04 UTC,"Setting thunderbolt to No Security on my device (XPS 9500 with Ubuntu 20.10) fixes the random disconnect, but input devices still randomly stop working.
The only way to fix this is to unplug them and plug them back in."
1766076,2020-08-19 14:11:03 UTC,"Responding to earlier statement in #93:
Replaced the TB16 (240W) with a WD19TB (180W) and issue disappeared. Also no issues with thunderbolt user authorization setting enabled."
1766076,2020-07-05 00:11:18 UTC,Having the same or at least similar issue on a DELL XPS13 (9360) D600 Dock. The thunderbolt connection suddenly drops for a few seconds and the automatically reconnects again. Screens go blank for that time and all peripherals also gets disconnected. This happens randomly but at least twice an hour. All firmware is up-to-date.
1766076,2020-04-20 12:04:52 UTC,"Disabling Thunderbolt Security in the BIOS did not help.
My BIOS has no Kernel DMA protection."
1766076,2020-04-09 09:44:09 UTC,"Please try enable ""kernel DMA protection"", this is the most security option."
1766076,2020-04-09 07:19:35 UTC,I have the same issue with a i-tec displaylink docking station. My OS is the ubuntu based linux mint 19.2 with kernel version 5.3.0-46-generic.
1766076,2018-10-25 06:10:27 UTC,apport information
1766076,2020-05-07 18:24:54 UTC,"Laptop: XPS 15 9570
BIOS Information
 Vendor: Dell Inc.
 Version: 1.15.0
 Release Date: 12/25/2019"
1766076,2018-10-25 06:10:24 UTC,apport information
1766076,2018-04-23 20:11:32 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1766076,2018-04-22 16:29:05 UTC,apport information
1766076,2018-10-25 06:10:26 UTC,apport information
1766076,2018-04-22 16:28:50 UTC,apport information
1766076,2018-04-22 16:28:47 UTC,apport information
1766076,2018-04-22 16:28:45 UTC,apport information
1766076,2018-04-22 16:28:44 UTC,apport information
1766076,2018-04-23 21:09:13 UTC,"I had this issue previously under Zesty and I think it was gone under Artful (though I'm not sure - the dock started having hardware issues at that point). I just upgraded to Bionic *and* got a new dock, and almost immediately started having these issues."
1766076,2018-04-22 16:28:42 UTC,apport information
1766076,2018-04-22 16:28:38 UTC,apport information
1766076,2018-04-22 16:28:37 UTC,apport information
1766076,2018-04-22 16:28:36 UTC,apport information
1766076,2018-04-22 16:28:35 UTC,apport information
1766076,2018-04-22 16:28:32 UTC,apport information
1766076,2018-04-22 16:28:30 UTC,apport information
1766076,2018-04-22 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1766076,2018-04-22 16:28:39 UTC,apport information
1766076,2018-05-04 21:35:44 UTC,I can confirm this is a regression between Artful and Bionic.
1766076,2018-04-22 16:28:41 UTC,apport information
1766076,2018-08-20 19:08:10 UTC,@Branan any luck?
1766076,2018-10-25 06:10:19 UTC,apport information
1766076,2018-10-25 06:10:17 UTC,apport information
1766076,2018-10-25 06:10:16 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  katamo    12313 F.... pulseaudio
 /dev/snd/controlC3:  katamo    12313 F.... pulseaudio
 /dev/snd/controlC0:  katamo    12313 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=639e9a98-76fc-4156-9d01-fe50f93ad7bd
InstallationDate: Installed on 2018-07-07 (109 days ago)
InstallationMedia: Ubuntu 18.04 LTS ""Bionic Beaver"" - Release amd64 (20180426)
MachineType: Dell Inc. Precision 7720
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=/dev/mapper/ubuntu--vg-root ro debug intel_iommu=on kvm.ignore_msrs=1 default_hugepagesz=2M hugepagesz=2M hugepages=4096 transparent_hugepage=never
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-38-generic N/A
 linux-backports-modules-4.15.0-38-generic  N/A
 linux-firmware                             1.173.1
Tags:  bionic
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 017JKT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd04/14/2017:svnDellInc.:pnPrecision7720:pvr:rvnDellInc.:rn017JKT:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7720
dmi.sys.vendor: Dell Inc."
1766076,2018-10-25 06:03:43 UTC,I have also experienced this issue on both a 5520 and 7720.
1766076,2018-10-25 05:42:25 UTC,"Sorry for the late reply, I'll start look into this issue."
1766076,2018-08-30 17:50:49 UTC,"The last TB firmware was released 2018-04, and it is up to date (also according to fwupdmgr)."
1766076,2018-07-04 04:17:32 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1766076,2018-08-30 17:33:32 UTC,Thank for the info! This is something Dell should know.
1766076,2018-08-30 17:20:54 UTC,"I had to downgrade the BIOS back to 1.10.1 (fwupdmgr installed 1.11) as under the new firmware suspend to RAM caused the system to completely power off (i.e. boot from scratch when powering on). I'll try to update again when the new update is released on Dell's website (the current version on the website is 1.10.1, so I can't even report an bug about the firmware update)."
1766076,2018-08-30 15:29:47 UTC,"Apparently there's a firmware update (I was running 1.10, which is about a month old - I've updated the firmware several times during the life time of this bug). I'll update and wait for it to happen again."
1766076,2018-08-30 14:52:30 UTC,"Ok, please make sure both BIOS and TBT are up-to-date.
You can update them by doing the following:
$ fwupdmgr refresh
$ fwupdmgr update
$ sudo reboot"
1766076,2018-08-30 14:07:42 UTC,Just got the issue again with latest Bionic kernel (Precision 5520 + TB16):
1766076,2018-08-22 08:30:14 UTC,Do all of you use Precision 5520 + TB16?
1766076,2018-08-22 08:20:22 UTC,"Sorry, I missed the important line from the dmesg log. It should be:"
1766076,2018-08-22 08:19:18 UTC,"I've been running a few days now with the main line kernel 4.18.3 (from Ubuntu's main line kernel downloads), and I just got this again:"
1766076,2018-08-21 05:49:58 UTC,This should be fixed in latest Bionic kernel.
1766076,2018-10-25 06:10:21 UTC,apport information
1766076,2018-10-25 06:10:23 UTC,apport information
1766079,2019-10-15 11:02:53 UTC,Hello
1766079,2018-04-24 02:06:02 UTC,It works in other directories.
1766079,2018-04-23 21:00:16 UTC,Does it work in other directories? Do you get any messages to audit logs or dmesg?
1766093,2018-04-23 02:20:48 UTC,"I see similar behavior in 92.2, when numeric precision is set to 7 in the Preferences>Input/output>SVG output>Numbers"
1766093,2020-09-10 13:51:29 UTC,Closing because INVALID: Can't replicate. Works as advertised.
1766095,2019-03-25 14:25:49 UTC,"Same on Ubuntu 18.04.2, ~ 5% CPU, plymouth package version 0.9.2-3ubuntu13.5"
1766095,2019-10-20 07:27:35 UTC,This is on Ubuntu 18.04.3 LTS
1766095,2019-10-20 07:26:25 UTC,See the same bug on my HP Spectre x360 15t.
1766095,2019-05-22 02:09:35 UTC,Same on Ubuntu Kylin 19.04
1766095,2019-05-12 18:26:55 UTC,"Sorry, that was a wrong link. Here's the correct one:
https://askubuntu.com/questions/766973/16-04-how-to-uninstall-plymouth"
1766095,2019-05-12 18:16:49 UTC,"Well, it's quite frustrating that the bug still persists even on 18.04. I'm using Xubuntu 18.04 with updates installed and the plymouthd had 25% CPU usage on ThinkPad T43p. I found a workaround on how to disable it. The process won't bother you again.
https://askubuntu.com/questions/407131/why-is-plymouthd-crashing-on-startup"
1766095,2019-03-25 14:56:07 UTC,"Sorry, made a mistake in previous comment (package version given is for 16.04.5)."
1766095,2018-07-20 05:08:43 UTC,"I just noticed this behavior.  ""sudo plymouth --quit"" is my current mitigation, as well."
1766095,2020-01-01 13:46:04 UTC,"Same on Ubuntu 19.10, ~ 5% CPU,
plymouth package version 0.9.4git20190712-0ubuntu4.1"
1766095,2018-06-17 06:41:16 UTC,same here @ 6-7% .
1766095,2018-05-09 22:56:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766095,2018-05-09 22:56:38 UTC,I have the exact same bug. plymouthd runs at a little under 5% all the time after a reboot. I kill the plymouthd process so it doesn't waste electricity. But it starts up again and does the same thing next boot.
1766095,2018-05-08 14:11:29 UTC,This is what the daemon is doing wasting the CPU:
1766095,2018-04-23 02:16:34 UTC,When plymouthd is burning up 5% of the CPU it also prevents Ctrl-Alt-F6 from giving you a console login. Instead you get a black screen that just echoes what you type.
1766095,2020-04-23 15:27:09 UTC,"Same problem on a fresh install of Ubuntu 19.10 x86_64 on a Toshiba Satellite U405. Another curiosity is that plymouth fails to display anything on the splash screen, it is just black until the system fully boots up."
1766095,2019-02-22 11:52:30 UTC,I did not have this problem until recently changed default theme. Now plymouthd utilizes ~15% cpu.
1766095,2020-04-18 07:51:57 UTC,Same problem on Xubuntu 20.04
1766097,2018-06-21 18:09:07 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766097,2018-08-13 22:40:28 UTC,Probably related to bug 11334.
1766100,2018-05-11 17:41:00 UTC,"I'm not able to reproduce this bug on Files 3.26.3-0ubuntu4 on Ubuntu 18.04 (at least, when downloading an image from Facebook to Desktop from Chromium 65.0.3325.181 (277) [snap]) so I'm assuming this is Fix Released, if you can reproduce this bug on Ubuntu 18.04 then please change this to New."
1766100,2018-05-12 01:22:32 UTC,"> I'm not able to reproduce this bug [...] so I'm assuming this is Fix Released
"
1766101,2018-04-22 16:37:53 UTC,The snapcraft.yaml is here https://github.com/sirredbeard/FeedReader/commit/71b0c6757e1d5b9b0b4bc91a4d0ab0675517eee4
1766101,2018-04-22 16:38:44 UTC,"The make file for that submodule, WebExtension, also builds fine."
1766101,2018-04-22 17:17:57 UTC,I have a snapcraft building well by calling cmake from override-build instead of using the cmake plugin.
1766101,2018-04-22 19:14:28 UTC,I have two versions of this snapcraft.
1766101,2018-04-23 13:09:15 UTC,"snapcraft, version 2.41+18.4.2"
1766101,2018-04-25 18:49:14 UTC,"The upstream project has now switched to Meson, so while issues #1 and #2 might still be issues with snap creation, and your fix may work, I am now focusing on issue #3, getting snap to build with the Meson plugin."
1766102,2018-04-22 16:45:00 UTC,"Dan Kegel:

> Public bug reported:
>
> If the package's debian/changelog has a first line with version 0,
> dh_installchangelogs fails with
>
> dh_installchangelogs: changelog parse failure
>
> This is fixed upstream, see https://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=894895
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: debhelper 11.1.6ubuntu1
> ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
> Uname: Linux 4.4.0-119-generic x86_64
> ApportVersion: 2.20.9-0ubuntu6
> Architecture: amd64
> Date: Sun Apr 22 16:31:02 2018
> PackageArchitecture: all
> SourcePackage: debhelper
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: debhelper (Ubuntu)
>      Importance: Undecided
>          Status: New
>
>
> ** Tags: amd64 apport-bug bionic
>
"
1766102,2018-04-22 17:19:51 UTC,"(Right... that's why I linked to that bug.
It would have been nice if I had noticed this problem a month ago, apologies...)"
1766102,2018-04-22 17:44:00 UTC,"Dan Kegel:

> (Right... that's why I linked to that bug.
"
1766103,2018-10-15 15:05:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1766103,2018-10-15 05:51:26 UTC,I upgraded from Xenial to Bionic and noticed the same. I also noticed that bug preventing from using VPN has been open for 6 months now! Could this be added to your priority list?
1766103,2018-05-27 11:26:16 UTC,Also I cannot do vpn connections after upgrade to bionic from 17.10.
1766103,2018-05-24 15:22:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766108,2018-04-22 22:08:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766108,2020-01-19 14:57:53 UTC,"Batt indicator bug still exists as tested in 20.04. See attached screencasts taken with,
1. indicator applet
2. indicator applet complete"
1766108,2020-01-19 14:58:36 UTC,With indicator applet complete.
1766108,2020-10-28 05:43:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766108,2021-02-17 09:26:32 UTC,This bug seems to be fixed in 21.04. I am not seeing it anymore on 21.04.
1766115,2018-05-30 13:46:05 UTC,"Strange.  It seems to think your system is in EFI mode, but also not in EFI mode at the same time:"
1766126,2020-04-06 14:09:39 UTC,This is no longer true as of 1:1.3.4-2.1ubuntu5.2 (bionic). Do you need this fix in xenial?
1766126,2020-04-06 14:38:47 UTC,"Personally, I am not waiting for fix in xenial anymore. The storage is now mounted to client directly."
1766130,2018-04-23 03:08:43 UTC,"Disks from the menu also know as gnome-disks is a more reliable way to
write usb sticks."
1766130,2018-04-24 11:45:11 UTC,"Hi fossfreedom,"
1766135,2018-05-03 14:32:23 UTC,"I have tested, and I am still unable to connect to openvpn , even with new certificate .
I have sent at least 10 emails to support, even was about install teamviewer for their technician to remote in , but did not go through with it.
I guess since connection works on 16.04 I will go back to 16.04 and wait it until eider PureVpn or Ubuntu fix this issue."
1766135,2018-08-21 10:36:48 UTC,"For anyone else coming across this
I hit up purevpn support and the guy sent a zip containing new .crt and .key, as well as .ovpn's for all their edge locations.
In which I see the server names have a ""2"" prepended to the first segment i.e.
usla-ovpn-udp.pointtoserver.com
->
usla2-ovpn-udp.pointtoserver.com"
1766135,2018-04-30 14:26:22 UTC,"Judging by the ""CA signature digest algorithm too weak"" you should contact PureVPN's support desk and ask for new certificate."
1766135,2018-08-21 10:38:16 UTC,here's the zip
1766135,2018-04-30 03:24:34 UTC,Step by step instructions that I have for many years used to connect to VPN and always worked until  Ubuntu 18.04
1766135,2018-04-30 15:13:42 UTC,"I have contacted them, and they give to me updated Ca.crt.. I will test it once I get home.
Thanks for help."
1766135,2018-04-30 03:01:25 UTC,Wdc.key
1766135,2018-04-30 03:00:37 UTC,ca.crt file
1766135,2018-04-30 02:54:55 UTC,"Here is syslog
I am still unable to connect
Works perfectly on 16.04"
1766135,2018-04-30 03:13:08 UTC,"So far I have found that I have to put ca.crt and Wdc.key or it fails instantly
I have found that it affect other users that use Ubuntu 18.04 proper :https://askubuntu.com/questions/1026991/ubuntu-18-04-cant-turn-on-vpn  and closing their question without at least attempting to help them is not helping anyone.
I am really disappointed that issue like this has come to LTS after everyone saying that 18.04 is not allowed to fail."
1766138,2018-04-23 00:56:45 UTC,"Same LAN Caja under Linux Mint shows two machines.
Point of interest New Ubuntu-mate machine does NOT show up.
This may be because of a incomplete/buggy/mis-configured Samba on the new machine."
1766140,2019-02-12 13:12:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766140,2019-02-12 13:14:43 UTC,Most probably Wayland-specific.
1766143,2020-09-04 19:40:26 UTC,webcamoid                   8.1.0+dfsg-7
1766143,2019-03-03 01:24:23 UTC,"I also confirm this.  Here are my messages, which are a little different:
~$ dmesg |tail -n 60
[  114.220089] usb 1-1.4: device descriptor read/64, error -32
[  114.420093] usb 1-1.4: device descriptor read/64, error -32
[  114.528302] usb 1-1-port4: attempt power cycle
[  115.156055] usb 1-1.4: new full-speed USB device number 16 using xhci_hcd
[  115.156177] usb 1-1.4: Device not responding to setup address.
[  115.364128] usb 1-1.4: Device not responding to setup address.
[  115.572019] usb 1-1.4: device not accepting address 16, error -71
[  115.664021] usb 1-1.4: new full-speed USB device number 17 using xhci_hcd
[  115.664129] usb 1-1.4: Device not responding to setup address.
[  115.876154] usb 1-1.4: Device not responding to setup address.
[  116.084017] usb 1-1.4: device not accepting address 17, error -71
[  116.084289] usb 1-1-port4: unable to enumerate USB device
[  116.107176] usbcore: registered new interface driver r8152
[  116.114216] usbcore: registered new interface driver cdc_ether
[  116.813530] usb 1-1.3: USB disconnect, device number 13
[  159.204122] r8152 1-1.3:1.0 (unnamed net_device) (uninitialized): Get ether addr fail
[  159.204998] r8152 1-1.3:1.0 eth0: v1.09.9
[  159.484438] usb 1-1.3: new high-speed USB device number 18 using xhci_hcd
[  159.601037] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[  159.601040] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  159.601042] usb 1-1.3: Product: USB 10/100/1000 LAN
[  159.601043] usb 1-1.3: Manufacturer: Realtek
[  159.601044] usb 1-1.3: SerialNumber: 00E04C360518
[  160.404159] usb 1-1.4: new full-speed USB device number 19 using xhci_hcd
[  160.496162] usb 1-1.4: device descriptor read/64, error -32
[  160.700444] usb 1-1.4: device descriptor read/64, error -32
[  160.904166] usb 1-1.4: new full-speed USB device number 20 using xhci_hcd
[  161.000162] usb 1-1.4: device descriptor read/64, error -32
[  161.200095] usb 1-1.4: device descriptor read/64, error -32
[  161.312417] usb 1-1-port4: attempt power cycle
[  161.948169] usb 1-1.4: new full-speed USB device number 21 using xhci_hcd
[  161.948422] usb 1-1.4: Device not responding to setup address.
[  162.156263] usb 1-1.4: Device not responding to setup address.
[  162.364267] usb 1-1.4: device not accepting address 21, error -71
[  162.466728] usb 1-1.4: new full-speed USB device number 22 using xhci_hcd
[  162.466887] usb 1-1.4: Device not responding to setup address.
[  162.672130] usb 1-1.4: Device not responding to setup address.
[  162.884049] usb 1-1.4: device not accepting address 22, error -71
[  162.884340] usb 1-1-port4: unable to enumerate USB device
[  162.887992] usb 1-1.3: USB disconnect, device number 18
[  202.868108] r8152 1-1.3:1.0 (unnamed net_device) (uninitialized): Get ether addr fail
[  202.869288] r8152 1-1.3:1.0 eth0: v1.09.9
[  203.144160] usb 1-1.3: new high-speed USB device number 23 using xhci_hcd
[  203.262058] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[  203.262068] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  203.262075] usb 1-1.3: Product: USB 10/100/1000 LAN
[  2..."
1766143,2018-11-02 19:40:45 UTC,I also had problems with Budgie 18.10.
1766143,2018-04-23 01:53:10 UTC,"May be just try rebuilding the package?
I installed webcamoid_8.1.0+dfsg-7_amd64.deb (the same version as in Ubuntu!) from Debian Sid https://packages.debian.org/sid/amd64/webcamoid/download , leaving webcamoid-data and webcamoid-plugins from Ubuntu, and it does NOT segfault."
1766143,2018-05-02 22:02:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766143,2018-10-23 11:26:24 UTC,I can confirm that this bug is still present in webcamoid on Xubuntu 18.10 (cosmic).
1766148,2018-04-27 20:04:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766151,2018-04-30 02:25:16 UTC,"Hi All,"
1766151,2018-04-30 02:26:42 UTC,Zun logs.
1766151,2018-04-28 21:25:38 UTC,"Hi,"
1766151,2018-04-28 20:07:41 UTC,"@Jeffery, could we have someone from Kolla to triage this bug?"
1766151,2018-04-26 23:41:31 UTC,"Hi Sir Hong,"
1766151,2018-04-28 19:46:24 UTC,"From Zun's perspective, I need further information to confirm this bug. I am mainly not sure if this bug is due to a defeat at Zun or a mis-configuration from Kolla."
1766151,2018-04-24 02:31:23 UTC,"Hi @vpc,"
1766151,2018-04-28 20:02:45 UTC,It seems this is the same problem as: https://bugs.launchpad.net/kuryr/+bug/1632291
1766153,2018-04-23 04:16:29 UTC,conky -v
1766153,2018-04-23 04:18:27 UTC,part of conkyrc with settings
1766153,2018-04-23 04:20:34 UTC,own_window_type normal or desktop
1766153,2018-04-23 04:21:16 UTC,own_window_type dock or panel
1766162,2018-04-24 07:54:10 UTC,"Fix committed
https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/408635/1"
1766163,2018-04-23 06:44:00 UTC,"This is related to the code that decides which track is currently. On one hand, we want to catch any track changes like requested here, on the other hand, a mashup of all four decks should not change the current track."
1766163,2018-04-23 08:24:39 UTC,"Currently the code in PlayerInfo::updateCurrentPlayingDeck examines all playing decks and picks the one with the highest gain as the ""current"" deck. When the ""current deck"" changes, it emits the currentPlayingTrackChanged signal, which is then filtered by SetlogFeature using the window of 6 to determine if a new history entry is written and the playcount is incremented."
1766163,2018-04-23 15:03:02 UTC,"Yes something like this sounds reasonable.
We will hit the same issue if we start to publish the playing track at Twitter or as a RDS tag while broadcasting. So we should decouple the logic from the history feature."
1766164,2020-04-09 09:05:53 UTC,"I wish to add a related request. If there is no next track available or Auto-DJ is disabled, it will be still possible to just trigger a fade-out."
1766164,2020-04-09 15:48:07 UTC,"Please file a new bug. This sounds for me like a real issue, not a feature request like this bug."
1766168,2018-04-23 08:05:58 UTC,"If a human operator would normally leave the crossfader in the centre, why not program the Auto DJ to also return the crossfader to the centre when he is not handling a track transition?"
1766168,2018-04-23 14:55:52 UTC,"This sounds a bit like to much magic for me.
How about start with a solution that just skips centring crissfader if it was on one side before Auto DJ was started?"
1766168,2018-04-23 06:20:41 UTC,"You have hit a valid issue.
On the other hand the current behaviour is intended, it puts the crossfaded back to a position where it was probably before, to allow instantly Mixxx successor tracks using the line faders.This is especially important if a user has disabked the crossfader in skins or no mapping for it."
1766190,2018-04-23 08:23:03 UTC,more information:
1766192,2019-04-18 00:06:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766192,2019-07-18 12:07:03 UTC,"I can confirm this with 19.04 (Disco Dingo) and libreoffice 6.2.5.2 latest updates. ""Document could not be locked"". Is this regression?"
1766192,2019-03-21 17:20:47 UTC,I can't read bookmark JSON file in ~/Documents from Firefox also.
1766192,2019-07-18 14:00:23 UTC,"Hi Ulrich-Lorenz, no regression - the root issue has not yet been resolved."
1766192,2019-09-12 08:13:53 UTC,"I cannot open attachments in Evolution using Libreoffice in Disco.
I receive the error:
Access to /home/user/.cache/evolution/tmp/<redacted>.xlsx was denied."
1766192,2019-09-19 09:31:31 UTC,"Nikolaj, that's a separate issue. Snaps are not allowed to read files in dot folders under $HOME."
1766192,2019-11-03 04:19:57 UTC,This issue also prevents importing CSV files stored in the user's home directory.
1766192,2019-03-21 17:19:10 UTC,"It seems no Snap package can access ~/.
I recently re-installed Ubuntu 18.10. On previous installation of Ubuntu 18.10, the problem didn't exist, so it may be due to a recent update."
1766192,2019-07-18 16:08:30 UTC,Just installed LibreOffice 6.3.0.1 with no change.
1766192,2019-03-21 17:16:49 UTC,This also applies to Firefox.
1766192,2019-03-21 20:43:30 UTC,"I fixed it. After installing Ubuntu, I copied data from another partition with `sudo cp -R...`.
Using `sudo chmod a+wrx -R /home/...` didn'r work.
Using `sudo chown ... -R /home/...` worked."
1766192,2019-03-21 10:51:00 UTC,"Sherif, where are those files located, exactly?"
1766192,2019-03-21 10:07:15 UTC,"Can't open files , at home, with Libreoffice Writer from Snap."
1766192,2018-10-17 10:45:22 UTC,Another occurrence caused by the same root problem: opening e.g. a PNG image file under $HOME/ with libreoffice draw causes the following dialog box to be shown:
1766192,2018-07-13 16:50:22 UTC,"As pointed out by Mike in a mailing list conversation (https://lists.freedesktop.org/archives/libreoffice/2018-July/080527.html), changing the lock filename pattern will invalidate the benefits of a cross-applications, cross-versions lock mechanism."
1766192,2018-07-06 14:17:00 UTC,Proposed fix: https://git.launchpad.net/~libreoffice/+git/libreoffice-snap/commit/?id=0fffe04e069c2e334a00b238cebf150fd2644bac
1766192,2018-05-30 16:22:10 UTC,Hello!
1766192,2019-03-21 17:16:33 UTC,Files are in ~/Documents.
1766192,2018-05-07 08:38:31 UTC,I'm marking this as triaged but I'm unsure how to solve it as we don't want to allow write access to dot files in the home directory. Perhaps libreoffice could be updated to create a different pattern for temporary file names when under snap confinement?
1766192,2018-04-23 12:04:35 UTC,Presumably this is a snapd policy and should be filed under snapd too? :)
1766198,2018-04-23 17:50:11 UTC,Thanks for reporting.
1766198,2018-04-24 20:04:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766198,2018-10-25 22:27:51 UTC,Roll-out new version to Debian as well plz.
1766199,2018-04-26 22:04:47 UTC,"It's fine on an undercloud, not sure what we need to do on the overcloud."
1766199,2021-02-17 17:07:34 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1766201,2019-04-20 06:30:17 UTC,"@manjo thanks for testing again! Now I see, we need to apply another small patch to security/integrity/digsig.c, that seems to have exactly the same error message that should be considered a warning instead. I'll post a fix soon."
1766201,2019-06-04 10:41:52 UTC,"------- Comment From <email address hidden> 2019-06-04 06:30 EDT-------
Thiru , please verify now?"
1766201,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1766201,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1766201,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1766201,2019-05-29 17:01:17 UTC,"ubuntu@lewis:~$ uname -a
Linux lewis 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@lewis:~$ apt policy linux-image-generic
linux-image-generic:
  Installed: 4.18.0.21.22
  Candidate: 4.18.0.21.22
  Version table:
 *** 4.18.0.21.22 500
        500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el Packages
        100 /var/lib/dpkg/status
     4.18.0.20.21 500
        500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el Packages
        500 http://ports.ubuntu.com/ubuntu-ports cosmic-security/main ppc64el Packages
     4.18.0.10.11 500
        500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages
ubuntu@lewis:~$
ubuntu@lewis:~$ dmesg -xT -l emerg,alert,crit,err | grep ""integrity:
Unable to open file""
ubuntu@lewis:~$"
1766201,2019-05-20 14:02:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1766201,2019-05-17 14:56:32 UTC,"ubuntu@tiselius:~$ uname -a
Linux tiselius 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:51:32 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@tiselius:~$ apt policy linux-image-generic
linux-image-generic:
  Installed: 5.0.0.16.17
  Candidate: 5.0.0.16.17
  Version table:
 *** 5.0.0.16.17 500
        500 http://ports.ubuntu.com/ubuntu-ports disco-proposed/main ppc64el Packages
        100 /var/lib/dpkg/status
     5.0.0.15.16 500
        500 http://ports.ubuntu.com/ubuntu-ports disco-updates/main ppc64el Packages
        500 http://ports.ubuntu.com/ubuntu-ports disco-security/main ppc64el Packages
     5.0.0.13.14 500
        500 http://ports.ubuntu.com/ubuntu-ports disco/main ppc64el Packages
ubuntu@tiselius:~$ dmesg -xT -l emerg,alert,crit,err | grep ""integrity: Unable to open file""
ubuntu@tiselius:~$"
1766201,2019-05-17 14:25:32 UTC,"ubuntu@tiselius:~$ uname -a
Linux tiselius 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:26:12 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@tiselius:~$"
1766201,2019-05-17 09:31:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1766201,2019-05-17 06:47:06 UTC,"@manjo can you confirm that the ""integrity: Unable to open file"" errors are not reported anymore with the fix applied? Thanks!"
1766201,2019-05-16 15:03:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1766201,2019-05-01 01:50:51 UTC,There appears to be more than one problem being described in this bug report. Since they are separate issues they should be tracked as separate bugs (this helps keeping tracking of the fixes).
1766201,2019-04-20 07:48:20 UTC,"And about the error ""vio vio: uevent:"" happening at boot, it could be triggered by something in the initramfs. I think the best thing we can do from a kernel perspective is to add extra information to the error message to figure out exactly which task is triggering this error, and maybe also print the exact data that is received by the kernel."
1766201,2019-06-12 13:28:44 UTC,"------- Comment From <email address hidden> 2019-06-12 03:03 EDT-------
==== State: MoreInfo by: tthananj on 12 June 2019 01:55:31 ===="
1766201,2019-04-19 21:37:42 UTC,"Fresh install of 18.04 on Power9 system, installed linux-image-generic-hwe-18.04"
1766201,2018-06-25 14:12:58 UTC,"To re-iterate the question in comment #4, the bug description appears to describe use of an LPAR. Does this report refer to running Ubuntu as a guest under PowerVM? Thanks."
1766201,2019-03-26 18:53:27 UTC,"About the first two errors (""Unable to open file ... x509_ima.der"") they should be downgraded to warnings and this was previously addressed here:
https://lists.ubuntu.com/archives/kernel-team/2017-February/082526.html"
1766201,2018-04-23 09:40:35 UTC,Default Comment by Bridge
1766201,2018-04-23 09:40:37 UTC,Default Comment by Bridge
1766201,2018-04-23 09:40:59 UTC,Default Comment by Bridge
1766201,2018-04-23 10:07:16 UTC,The bug description describes use of an LPAR. Does this report refer to running Ubuntu as a guest under PowerVM?
1766201,2018-04-23 10:09:31 UTC,"------- Comment From <email address hidden> 2018-04-23 06:08 EDT-------
== Comment: #7 - Application Cdeadmin <email address hidden> - 2018-04-23 02:24:36 ====== State: Open by: stccdenv on 20 April 2018 05:54:35 ===="
1766201,2019-04-19 21:18:49 UTC,"Update: the patch to downgrade the error ""Unable to open file..."" to a warning seems to be already applied to the bionic kernel (https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master-next&id=58441dc86d7b066a2c02079829a96035587a7066) and the cosmic kernel (https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic/commit/?h=master-next&id=ed79083b0d87cef2a64f906614f49faa40337e96)."
1766201,2018-04-23 18:00:53 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1766201,2018-04-23 10:50:52 UTC,"------- Comment From <email address hidden> 2018-04-23 06:41 EDT-------
== Comment: #1 - Application Cdeadmin <email address hidden> - 2018-04-20 05:56:05 ====== State: Open by: stccdenv on 20 April 2018 05:54:35 ===="
1766201,2018-04-26 09:40:59 UTC,"------- Comment From <email address hidden> 2018-04-26 05:36 EDT-------
==== State: Open by: wongklb on 26 April 2018 04:30:30 ===="
1766201,2018-05-02 09:51:37 UTC,"------- Comment From <email address hidden> 2018-05-02 05:36 EDT-------
==== State: Open by: stccdenv on 02 May 2018 04:33:30 ===="
1766201,2018-07-18 07:00:00 UTC,"------- Comment From <email address hidden> 2018-07-18 02:55 EDT-------
==== State: Open by: wongklb on 18 July 2018 01:46:11 ===="
1766201,2019-02-18 11:00:52 UTC,I can reproduce the same error on 18.04 runinng 4.18 HWE kernel. Seems like we need to take a closer look..
1766201,2019-02-18 11:14:25 UTC,reference: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771555
1766201,2018-04-23 18:21:00 UTC,"------- Comment From <email address hidden> 2018-04-23 14:14 EDT-------
===================================END=================================== State: Open by: cde00 on 23 April 2018 13:14:00 ===="
1766210,2018-04-23 10:45:02 UTC,even better would be a new variable that gives nfs share to be mounted
1766210,2018-04-23 16:15:46 UTC,https://review.openstack.org/#/c/563687/
1766210,2018-04-23 16:16:38 UTC,this is handled in blueprint https://blueprints.launchpad.net/kolla/+spec/glance-nfs-backend
1766213,2020-07-05 01:09:13 UTC,works fine in 16.04.6
1766213,2020-07-06 21:09:23 UTC,"Thank you, closing if it works fine now"
1766213,2020-07-01 20:42:23 UTC,"Thank you for your bug report. Is that still an issue? Could you try with an newer Ubuntu serie?
Is it specific to a document and if so could you share it?"
1766217,2020-10-16 15:49:28 UTC,"Have this same issue in 20.04 with xubuntu.
If launching via menu launcher - it runs with no parameters (update-manager) - and it reports that there are 400+MB of updates required, but I get no details of what they are.
If launching from shell with no-update parameter (update-manager --no-update) all is shown OK."
1766217,2020-10-17 08:43:25 UTC,Through a process of trial and error - removing the following from /var/lib/apt/extended_states
1766217,2019-08-24 20:41:24 UTC,I'm getting this as well. Here's my output for apt list --upgradable
1766217,2019-02-13 20:23:57 UTC,I just did `sudo apt-get --purge autoremove` and it worked.
1766217,2019-02-12 09:01:30 UTC,"@rbalint Thanks for looking into this.
I will try to provide the outputs requested when it re-occurs however I'm not sure how they would help - Unfortunately this issue occurs intermittently hence the difficulty in replicating the issue. Upgrades are actually available and upgradeable, just not visible (as per the screen-shots provided by @tommy-trussell)."
1766217,2019-02-05 14:42:02 UTC,"@hbchoong If you still see the issue could you please show the output of of ""apt list --upgradable"" and maybe attach the output of ""apt-mark showauto"" ?
I can't reproduce it on my VMs but maybe I can with the same package set to upgrade."
1766217,2019-02-05 11:23:23 UTC,"Agreed, and thanks for the note.
I have removed GNOME Software from the affected list."
1766217,2019-02-05 11:12:45 UTC,"This is a problem with update-manager, not GNOME Software."
1766217,2019-02-05 11:00:26 UTC,"...Please prove me (and Scott et al) wrong, NOT right!"
1766217,2019-02-05 08:57:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766217,2018-10-21 15:48:41 UTC,"I am having a similar issue where Software Center is showing an empty frame in 18.10.  Software Center issues like this originate back in 16.04 days.  Much of the same issues exist today.
Desktop support by Canonical seems abysmal now.  I guess their IoT and Server farm markets are 99% of their income so Desktop doesn't truly matter to them."
1766217,2019-02-05 08:55:26 UTC,"Still affecting Bionic & Cosmic also - Confirmed.
I can only hope Scott Palmer (skewty) can eventually be disproved, but to be frank it is getting harder to do so as each day goes by... Please prove me wrong."
1766217,2018-09-12 19:44:54 UTC,Update to my previous comment:
1766217,2018-09-07 18:15:34 UTC,"I've been seeing this for some time -- probably since July, but I'm not sure.  (Just back from a month or so offline, so my memory is fading.)"
1766217,2018-08-11 04:48:31 UTC,"I haven't seen it since, but I also have not seen a fix so IMO it is still a bug that needs to be fixed."
1766217,2018-08-02 19:11:02 UTC,"I have been seeing this.
TL;DR: workaround: delete /var/lib/apt/extended_states"
1766217,2018-07-24 19:14:16 UTC,Encountered this. Thank you for the rm directions. It fixed the issue. I did not have to do the reinstall after reboot.
1766217,2018-06-27 08:09:49 UTC,"It is nice to know that I can fix the symptoms, but it is still a bug that needs to be fixed."
1766217,2018-06-26 14:15:38 UTC,"I forgot. If after executing those commands now update-manager gets permanently stuck on ""waiting for other software managers to quit"" (which is kept stuck even after removing the locks in all apt places and closing all software managers), then run:"
1766217,2018-06-26 14:04:20 UTC,"I was having this same bug and I managed to ""fix"" it by deleting everything under /var/lib/apt"
1766217,2018-05-24 21:34:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766217,2018-04-23 11:17:18 UTC,"reboot and run software updater gives the same result
need to click <remind me later> to get out"
1766217,2018-09-13 17:30:05 UTC,TL;DR -- today using apt-get autoremove deleted the offensive lines in /var/lib/apt/extended_states and restored the list in software-updater -- though I doubt that will work every time.
1766228,2019-12-17 05:14:03 UTC,"Change abandoned by Ian Wienand (<email address hidden>) on branch: master
Review: https://review.opendev.org/563860"
1766228,2018-04-24 08:45:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/563860"
1766228,2018-04-24 06:01:28 UTC,I'm actually not sure it is the username.  Unfortunately my testing environment is broken (can't get to consoles in the vm's) so once that's fixed I'll try it again
1766228,2018-04-23 12:02:36 UTC,It looks to me that devuser has run correctly
1766228,2018-04-23 14:29:40 UTC,"using 'devuser' as the username worked and I can login via VNC console
but openssh-server even though installed , ssh does not work to and from the vm.
Even ipv4 address is not assigned."
1766228,2018-04-24 00:43:56 UTC,"I think this probably highlights that we should check if there is already a user with the same name, because that is confusing.  I'm not sure about the network setup"
1766230,2020-04-30 23:32:47 UTC,"[Ubuntu 19.10] PhpStorm, snap installed, seems working well (eg. when I run a debug session it opens chromium and the launcher icons are well associated). When I open a link on Slack, also snap installed, the new window appears in the ""all windows"" section of the contextual menu of the Slack launcher icon."
1766230,2021-02-04 10:48:18 UTC,"I am also seeing this behaviour on 20.04.1 - it is confusing. I also see it when I open Cypress from within a terminal inside JetBrains PhpStorm - the chrome windows opened by that are co-located with the PhpStorm 'pips'.
This makes ctrl-tabbing between open applications difficult."
1766230,2020-11-25 12:05:50 UTC,Same issue in Ubuntu 20.10 with Slack and Brave browser
1766230,2020-09-01 01:38:52 UTC,I am seeing the same issue on 18.04.5 LTS
1766230,2020-07-30 20:39:05 UTC,"I don't know if this helps but I think I fixed this by using Nicolas' answer in
https://askubuntu.com/questions/1103461/slack-shows-opened-links-to-browser-as-another-slack-instance-in-task-bar?rq=1"
1766230,2020-06-22 21:21:20 UTC,Yes it's in focal and its very annoying.
1766230,2020-06-10 08:23:48 UTC,"@seb128, yes. It is still in issue on 20.04 (focal)."
1766230,2020-05-01 15:28:22 UTC,Is that still an issue in focal?
1766230,2020-03-28 08:50:58 UTC,"This happen with me in PhpStorm, also snap installed."
1766230,2020-12-05 20:51:44 UTC,"Seeing the same on a fresh 20.04.1 install with snap Slack and deb Vivaldi (chromium-based). However, if I close Slack and Vivaldi both, and reopen Vivaldi (`ps aux | grep slack` is empty), it shows up under the Slack context anyway."
1766230,2020-01-06 08:29:01 UTC,"I can confirm this happens in ubuntu 18.04.3 between Chrome and Slack.
Workaround in #3 doesn't work for me, as WM_CLASS is already correctly set, i.e.:
* slack:  `WM_CLASS(STRING) = ""slack"", ""Slack""`
* chrome: `WM_CLASS(STRING) = ""google-chrome"", ""Google-chrome""`"
1766230,2019-12-10 07:26:46 UTC,"This is still appearing both on snap/deb version of slack, using chrome."
1766230,2019-09-10 08:49:51 UTC,I can confirm this using a snap version of Slack and deb version of Firefox.
1766230,2019-08-21 14:31:31 UTC,"For reference, I also see this same issue with Firefox set as my default browser, and I am using the snap version of Slack."
1766230,2019-08-21 14:30:09 UTC,"Seeing this behavior, as well. Others reference vscode (in the comment above), so I am curious to know if this is related to electron, or if this is a snap-specific issue."
1766230,2019-06-05 14:50:07 UTC,The same happens when opening URLs from within VSCode. The newly opened browser window seems to inherit the window class.
1766230,2019-04-03 11:08:46 UTC,"It has happened sometimes that Slack Notifications do not work. This error arises for various reasons and some of them are: Notifications Manager has determined that Slack notifications are not important; Do Not Disturb mode is preventing the notifications from going through, New notification behavior is not working properly, Quiet Hours (Focus Assist) is delaying Slack notifications and many other possible reasons.  No worries because here we have some methods to resolve this error."
1766230,2019-01-21 10:03:34 UTC,"I have this too, but with Slack and Nautilus. Steps to reproduce:"
1766230,2020-01-10 14:00:04 UTC,Removing the snap version and installing the deb version fixed the issue for me.
1766232,2020-07-15 19:29:33 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.opendev.org/563614
Reason: Abandoning since there hasn't been any recent activity, if anyone wants to continue this work, please feel free to restore this."
1766247,2018-04-23 13:05:19 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766248,2018-05-07 08:40:54 UTC,This error occurs because during the refresh we disable the old core snap for a brief moment. I agree that it should not surface to the user this way but I'm unsure how to fix it yet.
1766258,2019-11-14 02:01:23 UTC,Should be fixed in 19.10
1766262,2018-04-23 14:26:48 UTC,"I can confirm we're not using the ""Cap results in patron search at this number"" setting in the client.  Also, we have implicit search limits in place now that correspond to the grid row counts, e.g. limit 25 results per grid page.  I think we can safely remove this setting."
1766262,2018-05-16 19:47:28 UTC,"Adding a note that, as mentioned in bug 1771652, as part of this bug, we could also update descriptions for other bugs so that they make more sense in the web client world. One of those settings is Items Out Claims Returned, Lost and Long-Overdue Display settings, which refer to displaying specific checkouts in the top or bottom pane of the Items Out page. These options are now presented in separate tabs of the Items out page."
1766262,2018-05-17 14:42:06 UTC,I posted a branch on bug 1325704 that addresses the YAOUS descriptions that Kathy mentioned in comment #2.
1766262,2018-05-17 15:01:06 UTC,"Here is a list of settings that don't appear in any non-XUL code in master (to the best of my understanding).  This includes those mentioned in the original bug report.  Are any of these being used in a secret location, or possibly will be supported in the web client soon?"
1766262,2018-05-17 15:24:41 UTC,"Since acq is still using Dojo, I suspect those first two acq settings are still in use. If not, they should be in use as the fund balance limits are important to acq users."
1766266,2018-04-23 17:39:50 UTC,There is a system requirements page[1] on the KiCad website which specifies this so it should not be that much of a surprise to users.
1766266,2018-04-24 11:52:05 UTC,"Yes. My proposed is just fix it (as usually made in the most of the software): create a button ""<<"" that open the rest of the toolbar."
1766266,2018-04-24 12:27:28 UTC,"I understand what you are asking.  Unfortunately, it's not that simple.  wxWidgets supports this toolbar behavior in it's wxAuiToolbar object but the last time we enabled this feature it was very buggy so we disabled it.  That was with wxWidgets 3.0.0.  Maybe the issues have been resolved but I'm not willing to risk it for v5.  Hopefully it has been fixed in newer versions of wxWidgets."
1766266,2018-04-24 13:26:04 UTC,"I agree, make stable is a priority."
1766266,2019-05-18 20:28:05 UTC,We've updated the min requirement to 1280 x 1024.
1766269,2018-04-23 19:46:10 UTC,"Looking at the publishing history for the package (you can find this in the upper right corner on the overview page, or see https://launchpad.net/ubuntu/+source/soundkonverter/+publishinghistory) it was removed during the zesty development cycle. The removal message refers to it blocking a transition and bug 1659926 for more details. I assume this issue was ultimately resolved and the package was then reintroduced in time for bionic."
1766269,2018-04-23 21:57:58 UTC,thanks for the clarification hans!
1766287,2018-04-24 23:02:21 UTC,I'm able to recreate by launching the specified image in europe-west1 region;
1766287,2019-03-29 17:27:47 UTC,On guidance from raharper I have opened new bug for this @ https://bugs.launchpad.net/cloud-init/+bug/1822353
1766287,2019-03-29 17:20:08 UTC,I'd like to reopen this following Disco minimal images failing to set up networking due to similar reasons to this bug with the only difference being that no nic was found.
1766287,2018-06-20 18:06:33 UTC,"This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New"
1766287,2018-05-25 20:07:02 UTC,"This bug is believed to be fixed in cloud-init in version18.2-27-g6ef92c98-0ubuntu1~18.04.1. If this is still a problem for you, please make a comment and set the state back to New"
1766287,2018-05-03 23:47:14 UTC,I too have verified the GCE bionic images with cloud-init 18.2-27 (currently in bionic-proposed) in europe-west region. 20 of 20 launched successfully.
1766287,2018-04-26 20:39:24 UTC,An upstream commit landed for this bug.
1766287,2018-04-25 13:58:40 UTC,"After applying the systemd-udev-settle.service changes to cloud-init
on my instance, I've got 484 successful reboots with no interruption
of networking."
1766287,2018-04-24 07:45:04 UTC,"As requested in IRC, please find attached the collect-logs archive from a successful boot."
1766287,2018-04-24 23:17:27 UTC,To recreate:
1766287,2018-04-23 22:00:29 UTC,Here's what I think is happening.
1766287,2018-04-23 20:01:44 UTC,I have gathered as much as I can from attaching a snapshot of the boot disk from the instance that failed to boot.
1766287,2018-04-23 17:26:28 UTC,To help with debugging I will try and collect logs from the failed instance launch.
1766287,2018-04-23 15:52:25 UTC,Also see attached GCE console of successfully launched instance for comparison
1766287,2018-04-25 11:06:44 UTC,@raharper I hadn't realised you had been working on a reproducer.
1766292,2020-02-22 20:04:03 UTC,This was fixed in samba 4.10 which ubuntu already ships.
1766292,2018-05-03 07:05:30 UTC,This bug is effectively just tracking the upstream Python 3 work landing.
1766295,2018-04-25 14:36:21 UTC,"It is to be noted that this doesn't happen if I use cinder-api (ie: eventlet), it only happens if I am using uwsgi. So, likely, the client is behaving differently."
1766298,2018-08-29 17:50:22 UTC,"This may be tricky to fix.  Currently pbr doesn't keep track of which file a given requirement line comes from, so there's no way to figure out the base directory for relative paths like this."
1766300,2020-11-09 10:14:41 UTC,"@ebonato
in focal, the service fails because of that condition:
$ systemctl status hv-fcopy-daemon.service
● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
  Condition: start condition failed at Mon 2020-11-09 10:03:59 UTC; 58s ago
             └─ ConditionPathExists=/dev/vmbus/hv_fcopy was not met"
1766300,2019-06-19 21:05:37 UTC,"According to this MS Documentation:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/integration-services"
1766300,2019-03-14 21:39:52 UTC,"Hi Folks,
I can confirm that bug still on Latest kernel 4.18."
1766300,2018-04-23 17:00:08 UTC,This change was made by a bot.
1766300,2018-04-23 20:07:37 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1766306,2018-04-23 18:07:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/563728"
1766306,2018-04-23 18:09:37 UTC,I noticed this when working on a backport for stable/pike where my functional test wasn't specifying boot_index=0:
1766306,2018-04-23 18:35:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/563732"
1766306,2018-04-26 00:07:45 UTC,"Reviewed:  https://review.openstack.org/563728
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=048fa2310014e6282e183da0abee87c73b6d71b9
Submitter: Zuul
Branch:    master"
1766306,2018-04-26 01:53:10 UTC,"Reviewed:  https://review.openstack.org/563732
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9815c2331904a3749269289b861229796aa6c91
Submitter: Zuul
Branch:    master"
1766306,2018-04-26 11:11:11 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/564461"
1766306,2018-05-09 15:42:58 UTC,"Reviewed:  https://review.openstack.org/564461
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dcb51804127a40768f543fa30b6b505695bf64d1
Submitter: Zuul
Branch:    stable/queens"
1766306,2018-06-08 12:25:36 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1766307,2018-07-02 12:36:20 UTC,I've updated my Ubuntu every day and this bug continues.
1766307,2018-04-25 08:27:00 UTC,Appears to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087 which has not yet been confirmed.
1766307,2018-04-24 10:46:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766309,2019-09-16 17:55:05 UTC,Migrated to https://github.com/widelands/widelands/issues/1705
1766313,2018-04-29 14:18:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766313,2018-04-29 14:36:18 UTC,This package fails to install on a fresh Ubuntu 18.04.
1766313,2018-04-29 15:48:03 UTC,"If shim-signed and grub-efi-amd64-signed packages fail to install at Ubuntu 18.04 installation, the system became unreliable."
1766318,2018-04-23 19:45:21 UTC,"The git-to-bzr import problem there (https://code.launchpad.net/~soylent-tv/truckliststudio/trickliststudiogit) is hard to fix.  Is there a particular reason you need a git-to-bzr import?  Have you considered doing a git-to-git import instead (https://help.launchpad.net/Code/Git#Mirroring_repositories_from_other_sites), which supports most of the same Launchpad features and is much more reliable?"
1766318,2018-04-25 06:45:08 UTC,"Thanks Colin,
 I always use sf and Github import to brz in that way, I didn't know there was others way to import the code in LP.
I will try as you tell me and let you know.
Thanks.
karl."
1766318,2018-04-25 08:46:24 UTC,"Hi Colin,
 I added the git repository following the instructions and seems to work good.
Thanks again.
karl."
1766321,2018-04-24 20:21:00 UTC,From DpkgTerminalLog:
1766323,2019-07-15 19:05:54 UTC,"@Evan, the dev team uses the issue database to schedule work.  So if we have a plan for a fix that will address several bugs, we mark them as duplicates so that there's only one work item.  You can always get to the other duplicates (they're linked on the right-hand side of the screen)."
1766323,2019-08-21 08:27:37 UTC,"""This would allow a single LED footprint to have many 3D models for various colors, and then per-board the LED model's color can be selected and it will be remembered along with the board file"""
1766323,2019-07-15 16:34:10 UTC,"I'm not sure I would call this a duplicate. The other bug doesn't have all the substantive info this one does, and this is a subset of the other bug (if I understand it correctly)."
1766323,2018-09-01 07:35:42 UTC,"@jeyjey Jeff and @shack Frank,
referring to this topic
https://github.com/KiCad/kicad-packages3D/issues/388#issuecomment-417770911 ,
what I would like to have in the future, is the option to show/hide the 3D models dynamically and directly in the 3D viewer. (I don't consider the option to have i.e. more than a 3D model for a LED very useful).
What I would consider very useful is a full list of the 3D models (a tree list) within a correspondent check option to enable/disable the visualization on the 3D viewer (an evolution of what is now available to show/hide all SMD, TH and Virtual models).
This list with related checked options could be saved along with the pcb project, to reload the board in the same way next time it will be displayed.
And a nicer other addition would be the ability to change transparency to the selection too."
1766323,2018-04-24 08:49:15 UTC,I implemented a Preview checkbox in 6.0 for each model so that alternative modules could be previewed.  I think the ask is to have something like that persisted and also used for non-preview rendering.
1766323,2018-04-24 08:30:04 UTC,"It is not clear from your description what you are proposing. You can already define multiple 3D models for a footprint. I think what you are suggesting is to be able to have multiple predefined by the librarians and then have an option to enable or disable a model easily, other that just changing the full path to the model."
1766323,2018-08-02 15:36:19 UTC,"@Jeff
Some way to select 1 out of x 3D models would be great.
Perhaps some way of adding a filter in the modelname (or similar) so Kicad would pick up all the filtered models, and the user could then select the specific mode (s)he would like."
1766324,2020-08-06 12:29:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766325,2018-04-27 08:23:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766325,2018-04-27 08:24:51 UTC,This happens with the final release 18.04 as well.
1766325,2018-05-11 06:49:18 UTC,Hello. Is there somebody looking into this problem? No comment from ubuntu-devs so far and I wonder if this report is even noticed.
1766325,2018-09-07 16:15:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766325,2018-09-07 16:44:12 UTC,"I have the same issue.
Both after adding a new user or doing a password change to a current user I have the same problem."
1766325,2018-09-08 11:17:53 UTC,Currently without any changes to my setup...
1766327,2018-04-23 19:00:21 UTC,Image of stop process and cpu/gpu lockup on reboot. Forced shutdown (holding power button) was necessary.
1766334,2019-09-19 12:05:26 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1766334,2019-09-20 12:20:45 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1766346,2018-04-23 20:39:41 UTC,"StacktraceTop:
 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:93
 ptp_unpack_PTPTIME (str=0x5add1ab7 <error: Cannot access memory at address 0x5add1ab7>) at ptp-pack.c:646
 ptp_object_want (params=0x7f97a401d910, handle=1, want=want@entry=5, retob=retob@entry=0x7f97b8d2bb60) at ptp.c:6772
 ptp_add_object_to_cache (params=<optimized out>, handle=<optimized out>) at ptp.c:6895
 add_object_to_cache (device=0x7f97a4023ad0, object_id=<optimized out>) at libmtp.c:9134"
1766346,2018-05-01 01:07:21 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1766347,2020-03-04 14:05:39 UTC,"We can't assume that tear-down happens gracefully, this should be handled by the process that creates/checks the nagios user in the mongodb currently and possibly resets the password."
1766358,2018-05-09 17:10:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766359,2018-04-24 20:36:05 UTC,im getting the same problem
1766359,2018-05-08 18:46:19 UTC,Are you sure that it does not work using HTTP(S)_PROXY variables as documented on http://docs.python-requests.org/en/master/user/advanced/ ?
1766366,2018-05-22 17:24:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766366,2018-05-22 17:29:52 UTC,"This is a problem for us as well. We're using Docker as part of our toolchain for creating a file system for a disk image for our product, and need to be able to run ""prime-select intel"" during the Docker image build, at a time when grub has not been installed yet."
1766366,2020-05-04 21:49:53 UTC,"Related GRUB interaction code was removed as part of https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011 fix, released in 0.8.8.1"
1766370,2018-04-24 16:38:19 UTC,Using 'boot-resources stop-import' before starting our arm64 import let us progress past this.
1766370,2018-04-24 14:43:05 UTC,"While we investigate the issues, please try one of these options:"
1766372,2018-06-13 16:36:22 UTC,"no problem, we will get it on the next release after it gets committed.
Please do not hesitate to ask questions and do not spend too much time on this, it should be straightforward solution (few lines of diffs)"
1766372,2020-07-25 15:49:21 UTC,Released in 7.1.2
1766372,2018-06-13 16:12:06 UTC,"sine i am new , i may need some time here,  i will push this by 7.1.1
thanks ."
1766372,2018-06-14 20:13:25 UTC,https://review.openstack.org/#/c/575541/
1766372,2018-06-13 16:00:25 UTC,"Thanks for picking this up, could you please tell me the timeframe of your commit as I am planning the next release (7.1.0) and it needs to go out soon (hopefully by end of this week at the latest).
If not ready I can always pull another release later (7.1.1)."
1766372,2018-06-22 03:00:13 UTC,"Thank you for your contribution.
Will release in 7.1.2"
1766372,2018-04-24 04:56:58 UTC,"This is possible and would require extending the kloudbuster configuration file.
You are welcome to contribute to this patch, otherwise will need that someone has the time to add it."
1766372,2018-04-24 04:50:11 UTC,it would be helpful if we can make proxy vm  flavor also configurable like server/client vms .
1766372,2018-04-24 00:31:40 UTC,The flavor for the proxy VM is hardcoded and set to
1766372,2018-04-24 05:02:53 UTC,"most of the times when we try from kloudbuster, it  will launch the vm but few times it will fail with above issue ."
1766376,2018-04-24 07:14:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766376,2018-04-24 11:21:02 UTC,Thank you for deploying a broken mysql-server package.
1766376,2018-05-01 01:14:01 UTC,Has policy-rc.d been configured to prevent changes to the server state?
1766387,2018-04-28 06:49:19 UTC,"@sahid,seems this is automatic step of doc update, so assign to you and feel free to find someone else"
1766388,2018-04-26 16:02:09 UTC,Hi
1766388,2018-04-25 17:02:08 UTC,The solution to this is explained in paragraph 15.12 of the OR manual.
1766401,2018-06-20 18:06:26 UTC,"This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New"
1766401,2018-05-08 17:29:16 UTC,This bug was fixed in the package cloud-init - 18.2-4-g05926e48-0ubuntu1~16.04.2
1766401,2018-05-08 17:28:47 UTC,"The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1766401,2018-05-08 17:28:39 UTC,This bug was fixed in the package cloud-init - 18.2-4-g05926e48-0ubuntu1~17.10.2
1766401,2018-05-02 15:36:46 UTC,Marking verification-done for artful.
1766401,2018-05-02 12:22:14 UTC,marked verification-done-xenial based on comment 13 above.
1766401,2018-05-02 02:53:50 UTC,"Greetings,"
1766401,2018-05-02 01:21:03 UTC,"Hello James, or anyone else affected,"
1766401,2018-05-02 01:18:01 UTC,"Hello James, or anyone else affected,"
1766401,2018-04-30 19:21:59 UTC,An upstream commit landed for this bug.
1766401,2018-05-11 21:45:53 UTC,This bug was fixed in the package cloud-init - 18.2-41-g3b712fce-0ubuntu1
1766401,2018-04-27 04:44:01 UTC,Sorry for the delay. Work + Life = Crazy.
1766401,2018-04-26 20:24:31 UTC,"OK, so I think the next step here is to create a test xenial image without that datasource_list and confirm that it boots as expected."
1766401,2018-04-26 03:14:39 UTC,Partial Analysis from Chad...
1766401,2018-04-24 20:06:05 UTC,Hi James
1766401,2018-04-24 18:51:59 UTC,Thanks for getting back to me.
1766401,2018-04-24 17:47:54 UTC,A run of 'sudo cloud-init collect-logs' should create a cloud-init.tar.gz in your current working directory that could be attached to this bug. It'd give us the logs and config files that would aid triage in this case so we can see why cloud-init thought it should overwrite this file.
1766401,2018-04-24 17:28:51 UTC,Some questions...
1766401,2018-04-24 03:26:39 UTC,Version: Ubuntu 16.04.4
1766401,2018-04-28 04:37:03 UTC,"Validated Scott's attached fix on an upgraded Xenial exhibiting the same incorrect NoCloudDatasource identification. Once this related branch is 'Fix released' into bionic, an apt upgrade to the new cloud-init deb will correct the dhcp misconfiguration after running 'sudo cloud-init clean --reboot'"
1766402,2018-04-24 16:33:55 UTC,Gnome have put in their .desktop file:
1766402,2018-04-24 19:16:36 UTC,"Hello Rik,"
1766405,2018-04-26 08:41:03 UTC,This bug was not fixed in bionic-final 0425 version
1766405,2018-04-28 03:35:00 UTC,The bug exists in bionic-final 20180427 enhanced.
1766408,2018-04-28 03:34:46 UTC,The bug exists in bionic-final 20180427 enhanced.
1766408,2018-04-26 08:55:49 UTC,This bug was not fixed in bionic-final 0425 version
1766473,2018-05-07 15:33:09 UTC,The package has been published and the bug is being set to Fix Released
1766473,2018-05-07 14:58:06 UTC,This bug was fixed in the package linux-hwe-edge - 4.15.0-20.21~16.04.1
1766483,2018-04-28 03:34:30 UTC,The bug exists in bionic-final 20180427 enhanced.
1766483,2018-04-26 08:56:12 UTC,This bug was not fixed in bionic-final 0425 version
1766484,2018-04-24 16:41:43 UTC,We don't include sudo in are stage3/4.
1766484,2018-04-24 16:45:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564028"
1766484,2018-09-11 00:09:38 UTC,"Reviewed:  https://review.openstack.org/564028
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=f7818e4a57de7b9fd840fda412e1850941f2cfdb
Submitter: Zuul
Branch:    master"
1766485,2018-04-24 09:04:00 UTC,"Which does keystone API version support this feature?
I looked at the keystone API reference [1], but I cannot find any corresponding entry.
Horizon supports various releases, so all features must be discoverable via API."
1766485,2018-05-13 18:56:27 UTC,"Since Keystone doesn't provide an API to determine if this is supported, we have to put this issue on hold until at least T release"
1766485,2019-01-14 13:07:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630663"
1766485,2020-04-14 15:38:13 UTC,"Reviewed:  https://review.opendev.org/630663
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=7f849239eadfe3d97c088b77eae4d4852c0ab842
Submitter: Zuul
Branch:    master"
1766495,2018-09-24 11:13:15 UTC,"Same here, Ubuntu 18.04.1 LTS (Lubuntu), latest Remmina version.
Workaround the same as above, changing color depth to True Color (32bpp) fixed it."
1766495,2018-11-21 19:16:51 UTC,"The bug is really the grey plus sign on the dark grey background. That needs to be sorted. I'd never have found that without this thread, almost gave up in favour of another application."
1766495,2019-02-07 14:31:11 UTC,"All;
I can see the grey plus sign and clicked on that to create a new connection profile. My problem is I cannot find any settings visible to alter the color depth. I can change the connection resolution, but that seems to be the extent of my choices.
Where are you finding the setting for color depth, etc?
Thank you very much!!"
1766495,2019-02-07 14:38:06 UTC,"OMG!
I found it.
There is a scroll bar on the right hand side of the configuration screen.
THAT was completely invisible and I just happened to move my cursor over to the right, just close enough that it expanded and I could scroll down to many more settings below the Resolution, including the Color Depth.
Thanks and sorry for the newbie inquiry  :-)"
1766495,2019-02-20 19:30:37 UTC,How and where can I change the color depth? I don't see the option in the settings.
1766495,2019-08-26 06:43:39 UTC,remmina 1.3.5 from the remmina-next works perfect with the GFX AVC modes.
1766495,2019-08-07 21:56:11 UTC,"Can someone give a screen shot of how to specify ""True Color"" or another color depth in Remmina?"
1766495,2019-08-07 22:07:50 UTC,I found it.. if you already have the connection setup
1766495,2019-09-04 00:42:50 UTC,"la solucion esta aqui,"
1766495,2019-08-26 11:42:01 UTC,comment #7 worked for me. thanks
1766495,2019-08-07 20:23:14 UTC,"I believe AVC/H.264 is better compression than what is used by the other options.
I would very much like it if I did not have to select True Color or any of the other options.
Is there a workaround or plan to make AVC/H.264 usable in Ubuntu 18.04?"
1766495,2018-09-19 01:16:50 UTC,"It is not in that dialog, it appears before you try to connect."
1766495,2018-05-05 13:23:02 UTC,My procedure for the workaround:
1766495,2018-08-27 12:55:50 UTC,Experiencing the same problem on KDE Neon bionic testing.
1766495,2018-09-18 22:03:23 UTC,"if anyone could add a pic of this little +, I'd aprreciate it. I can't see it."
1766495,2018-04-29 20:59:24 UTC,"Not sure how Ian was able to work around this. On a fresh install of Kubuntu 18.04 and a fresh install of Remmina, the only option available is Quick Connect. I suspect I'd have more options /once I was able to connect/, such as remembering the connection, but it won't let you do that when it's failing out with this error about libfreerdp. And the main settings in Remmina don't have any H264 settings."
1766495,2018-05-01 14:18:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766495,2018-05-01 14:19:26 UTC,"Same bug after update to 18.04 from 17.10. I had installed remmina from github, but after upgrade I cant use GFX H264."
1766495,2018-05-01 16:04:49 UTC,"I answer myself to share partial solution. I deactivated main bionic (18.04) repository and after apt update, I installed remmina from remmina-next repository. It installed ok and H264 codec now run aswell. Then I activated main bionic repository again and hold remmina packages to avoid upgrade from there."
1766495,2018-04-24 07:03:53 UTC,"I found the color depth setting (not available for quick connect), and changing it to GFX RFX, I'm able to connect."
1766495,2018-05-18 03:01:07 UTC,"Can confirm changing the color depth works to establish a connection.  Color depth is not a quick create option (underneath the Resolution drop down) so I picked ""True Color"" and it connected successfully.  Would rather use GFX without fiddling with it though.  Not a show stopper.  Resolution is basically workable on the remote desktop."
1766495,2018-05-23 15:31:15 UTC,"Thanks very much Ian. I feel a bit silly now, but you're 100% correct. I couldn't figure out how to add a permanent entry initially because of the horrible theme. The ""+"" sign is virtually invisible on Kubuntu 18.04 and my monitor."
1766495,2018-07-08 01:13:44 UTC,Even while reading the location (upper-left) I still missed it for an absurd amount of time.  So I attached a visual aid for those who might need it.
1766495,2018-08-12 07:10:48 UTC,"Can confirm the button is absolutely invisible at least on Kubuntu :)
Thanks for a workaround, guys"
1766496,2018-04-24 07:05:25 UTC,"Flannel/Calico provides L3 connectivity so they won't know about VM's floating IPs and may SNAT the traffic in cali-POSTROUTING rule of NAT table in compute node.
if you try to add a rule to POSTROUTING of NAT table to skip cali-POSTROUTING, which will be ineffective, because the table is going to be periodically updated by calico policy."
1766503,2020-09-11 07:48:14 UTC,"Just after finished previous comment, gnome-calculator crashed ( most probably related to CTRL-z ) ."
1766503,2020-09-11 07:37:37 UTC,"Hi,"
1766503,2020-08-13 15:04:55 UTC,"I have a
Using Linux Mint mate (Linux Mint 19.1 Tessa)
Linux 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux"
1766503,2020-06-17 12:50:23 UTC,Same problem here on Linux Mate 19.3 with Xed and Ibus using large amounts (up to 200 %) of CPU usage. Opening system monitor or htop stops the problem temporarily.
1766503,2020-03-22 09:14:37 UTC,New note.  As commented here: https://github.com/linuxmint/xed/issues/237 you can make it happen by pressing control key is pressed in rapid succession.
1766503,2020-03-22 09:12:30 UTC,I have observed this is happening Mint Mate 19.3 but also only when using Xed.  I have been unable to track down this problem any further.
1766503,2020-02-13 06:09:46 UTC,Actually I have seen this a couple of times in the past week or so. I'll reconfirm if and when it happens again.
1766503,2020-09-11 07:58:36 UTC,"Wait, there's more"
1766503,2020-02-13 05:35:04 UTC,I can confirm. My system is:
1766503,2020-02-13 05:46:10 UTC,"One comment. This situation does NOT happen, when I use Atom to edit.
It is happening only with Xed Editor."
1766503,2019-12-26 23:00:06 UTC,"same issue in 19.10 / 5.3.0-24-generic , opening system monitor does fix it, wierd."
1766503,2018-12-17 01:37:46 UTC,That comment is slightly off topic here. This bug is about the ibus-* processes.
1766503,2018-12-14 15:25:35 UTC,OK. I got it. In my case processes starts in similar way /tmp/XXX-XXX... that's was suspicious after search info about similar cases I found this:
1766503,2018-11-28 20:36:15 UTC,Same here. If i open system monitor or htop app sysctrl or ibus disappear and cpu goes back to normal.
1766503,2018-07-17 08:49:15 UTC,"Ditto, also, I have similar experiences with ""sysctrl"", and a handful of ""dbus"" processes. It is odd how top (which I run, rather than htop), ""dispells"" these seconds after launch."
1766503,2018-05-21 14:10:41 UTC,I am experiencing the exact same issue as Stelios.  I can run htop and everything goes back to normal.
1766503,2018-05-10 11:18:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766503,2018-05-10 11:17:15 UTC,"i have  multiple instances of ibus-x11 running simultaneously in Bionic 18.04. Up to 40% of CPU is used by them. Once i run htop, the processes automatically  disappear a few seconds later and everything goes back to normal. In fact, i run htop now after every boot to deal with the problem. If i use System Activity (KDE) instead of htop, i see one entry, systemd, using up to 40% of CPU. If i kill it from there, it will reappear few minutes later."
1766503,2020-01-07 14:20:11 UTC,"Although not using Ubuntu directly, I am using Mint, which is based on it (Tina - 19.2, based on Bionic, MATE edition). Might be the same problem. If not applicable, then please ignore my comment.
I can reproduce this in all machines I have, in a few simple steps:"
1766509,2018-08-11 17:59:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766513,2018-05-18 15:23:42 UTC,"Looks like new debhelper in 18.04 LTS already does automatically what pkg-create-dbgsym was doing before, so pkg-create-dbgsym is not needed."
1766513,2018-04-30 07:21:49 UTC,"Hi,
Since this change, I cannot make a bionic chroot image on top of the ubuntu 16.04 version."
1766513,2018-07-03 08:27:02 UTC,"When will this be pushed into the xenial?
Just like the Chanho in comment 3 I'm also unable to build packages in Xeanial due to this."
1766513,2018-04-24 08:19:11 UTC,"Removing packages from bionic:
 pkg-create-dbgsym 0.73 in bionic
  pkg-create-dbgsym 0.73 in bionic amd64
  pkg-create-dbgsym 0.73 in bionic arm64
  pkg-create-dbgsym 0.73 in bionic armhf
  pkg-create-dbgsym 0.73 in bionic i386
  pkg-create-dbgsym 0.73 in bionic ppc64el
  pkg-create-dbgsym 0.73 in bionic s390x
Comment: obsolete, uninstallable in any real build environment; LP: #1766513
1 package successfully removed."
1766513,2018-04-24 16:50:59 UTC,Fixed in ubuntu-dev-tools 0.163
1766515,2018-04-26 09:06:45 UTC,The bug existed in bionic 20180425.1 i686.
1766517,2018-04-26 03:21:33 UTC,"The bug existed in bionic 20180425.1 amd64.
ukui-control-center 1.13-0ubuntu1"
1766517,2018-04-26 09:07:38 UTC,The bug existed in bionic 20180425.1 i686.
1766517,2018-04-28 03:27:10 UTC,The bug exists in bionic-final 20180427 enhanced.
1766518,2018-04-26 06:17:15 UTC,"The bug existed in bionic 20180425.1 amd64.
ukui-control-center 1.13-0ubuntu1"
1766518,2018-04-26 09:12:54 UTC,This bug was fixed in bionic-final 0425 version
1766518,2018-04-28 03:26:20 UTC,The bug exists in bionic-final 20180425 enhanced.
1766525,2018-04-26 09:15:03 UTC,The bug existed in bionic 20180425.1 i686.
1766525,2018-04-28 03:25:38 UTC,The bug exists in bionic-final 20180425 enchanced.
1766532,2018-04-28 03:24:55 UTC,The bug exists in bionic-final 20180427 enhanced.
1766532,2018-04-26 09:05:09 UTC,This bug was fixed in bionic-final 0425 version
1766540,2018-04-24 09:58:16 UTC,It is probably trying to build in a tmpfs?  See https://docs.openstack.org/diskimage-builder/latest/user_guide/building_an_image.html#speedups
1766540,2018-04-24 10:47:24 UTC,Used following in dib virtual env
1766540,2018-04-25 16:03:45 UTC,At this point in the build its just running in a chroot so either the tmpfs disabling must not be working and you are running out of space there or you are actually running out of disk space on a fs.
1766540,2018-04-28 10:48:05 UTC, sudo DIB_NO_TMPFS=1 ./disk-image-create -a ppc64el -o ubuntu-vm1 -t raw -x --no-tmpfs vm ubuntu --logfile diblogvm2.txt
1766540,2018-04-28 11:28:19 UTC,in reply to comment 4
1766540,2018-04-30 08:34:21 UTC,--no-tmpfs doesnt work
1766540,2018-04-30 14:33:34 UTC,"2018-04-30 04:53:58.884 | > + apt-get --option Dpkg::Options::=--force-confold --option Dpkg::Options::=--force-confdef --assume-yes install dkms linux-image-generic
2018-04-30 04:53:58.884 | > Reading package lists...
2018-04-30 04:53:58.884 | > Building dependency tree...
2018-04-30 04:53:58.884 | > Reading state information...
2018-04-30 04:53:58.884 | > The following package was automatically installed and is no longer required:
2018-04-30 04:53:58.884 | >   libfreetype6
2018-04-30 04:53:58.884 | > Use 'sudo apt autoremove' to remove it.
2018-04-30 04:53:58.884 | > The following additional packages will be installed:
2018-04-30 04:53:58.884 | >   binutils cpp cpp-5 crda gcc gcc-5 iw libasan2 libatomic1 libcc1-0
2018-04-30 04:53:58.884 | >   libgcc-5-dev libgomp1 libisl15 libitm1 libmpc3 libnl-3-200 libnl-genl-3-200
2018-04-30 04:53:58.884 | >   libubsan0 linux-firmware linux-image-4.4.0-122-generic
2018-04-30 04:53:58.884 | >   linux-image-extra-4.4.0-122-generic make wireless-regdb
2018-04-30 04:53:58.884 | > Suggested packages:
2018-04-30 04:53:58.884 | >   binutils-doc cpp-doc gcc-5-locales gcc-multilib manpages-dev autoconf
2018-04-30 04:53:58.884 | >   automake libtool flex bison gdb gcc-doc gcc-5-doc libgcc1-dbg libgomp1-dbg
2018-04-30 04:53:58.884 | >   libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
2018-04-30 04:53:58.884 | >   libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg fdutils
2018-04-30 04:53:58.884 | >   linux-doc-4.4.0 | linux-source-4.4.0 linux-tools
2018-04-30 04:53:58.884 | >   linux-headers-4.4.0-122-generic make-doc
2018-04-30 04:53:58.884 | > Recommended packages:
2018-04-30 04:53:58.884 | >   fakeroot libc6-dev | libc-dev libc6-dev grub-ieee1275
2018-04-30 04:53:58.884 | > The following NEW packages will be installed:
2018-04-30 04:53:58.885 | >   binutils cpp cpp-5 crda dkms gcc gcc-5 iw libasan2 libatomic1 libcc1-0
2018-04-30 04:53:58.885 | >   libgcc-5-dev libgomp1 libisl15 libitm1 libmpc3 libnl-3-200 libnl-genl-3-200
2018-04-30 04:53:58.885 | >   libubsan0 linux-firmware linux-image-4.4.0-122-generic
2018-04-30 04:53:58.885 | >   linux-image-extra-4.4.0-122-generic linux-image-generic make wireless-regdb
2018-04-30 04:53:58.885 | > 0 upgraded, 25 newly installed, 0 to remove and 0 not upgraded.
2018-04-30 04:53:58.885 | > Need to get 0 B/124 MB of archives.
2018-04-30 04:53:58.885 | > After this operation, 547 MB of additional disk space will be used.
2018-04-30 04:53:58.885 | > Selecting previously unselected package libmpc3:ppc64el.
2018-04-30 04:53:58.885 | > (Reading database ...
2018-04-30 04:53:58.885 | > (Reading database ... 5%
2018-04-30 04:53:58.885 | > (Reading database ... 10%
2018-04-30 04:53:58.885 | > (Reading database ... 15%
2018-04-30 04:53:58.885 | > (Reading database ... 20%
2018-04-30 04:53:58.885 | > (Reading database ... 25%
2018-04-30 04:53:58.885 | > (Reading database ... 30%
2018-04-30 04:53:58.885 | > (Reading database ... 35%
2018-04-30 04:53:58.885 | > (Reading database ... 40%
2018-04-30 04:53:58.885 | > (Reading database ... 45%
2018-04-30 04:53:58.885 | > (Reading database ... 50%
2018-04-30 04:53:58.885 | > (Reading database ... 55%
2018-04-30 04:53..."
1766543,2018-07-26 13:30:45 UTC,apport information
1766543,2018-07-26 13:30:26 UTC,apport information
1766543,2018-07-26 13:30:28 UTC,apport information
1766543,2018-07-26 13:30:29 UTC,apport information
1766543,2018-07-26 13:30:30 UTC,apport information
1766543,2018-07-26 13:30:32 UTC,apport information
1766543,2018-07-26 13:30:40 UTC,apport information
1766543,2018-07-26 13:30:35 UTC,apport information
1766543,2018-07-26 13:30:38 UTC,apport information
1766543,2018-07-26 13:30:25 UTC,apport information
1766543,2018-07-26 13:30:44 UTC,apport information
1766543,2018-07-26 13:30:34 UTC,apport information
1766543,2018-07-26 13:30:24 UTC,apport information
1766543,2018-04-24 10:03:41 UTC,"Also, nova-scheduler or nova-api-os-compute will log the following lines (a few times per minute) while this is happening :"
1766543,2018-07-26 13:30:21 UTC,apport information
1766543,2018-07-26 13:30:19 UTC,apport information
1766543,2018-07-26 13:30:17 UTC,apport information
1766543,2018-07-26 12:15:54 UTC,By the way the task blocks on the following :
1766543,2018-07-26 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1766543,2018-07-26 10:56:58 UTC,Raising a task for the kernel for an opinion on how to triage this problem further; Marking the nova task as Medium but leaving as New for now until we figure out what's going on - this is not a show stopped but is a pain.
1766543,2018-04-26 13:05:04 UTC,Thanks for continuing to dig into this.
1766543,2018-04-26 08:34:33 UTC,"OK, the bug happened again with strace attached to nova-compute. Once again, there's little to no IO/network while it happens. memory is stable. CPU is at least 50% idle (and the rest of it largely user mode). Nothing in dmesg."
1766543,2018-04-25 06:21:38 UTC,"Hi Corey,"
1766543,2018-04-24 14:14:10 UTC,"Hi Junien,"
1766543,2018-07-26 13:30:23 UTC,apport information
1766546,2018-04-25 10:25:40 UTC,"I think we are trying to fix too many problems here.
This bug refers to serviceaccount keys being different on each node which causes errors in multimaster deployments.
ca.key being exposed to master nodes is a security concern but has nothing to do with this bug.
My point here is that service account key pair does not have to be CA at all, it does not need to be signed by our cluster CA. And generally k8s deployments use different keypar for them.
I suppose we might dont want to use existing ca.key for it(and it's not always presented on master nodes)"
1766546,2018-04-25 09:41:46 UTC,To get things clear about certificates in Kubernetes:
1766546,2018-04-25 10:00:00 UTC,"Yes, we use a single ca for the cluster. The ca.key is passed with the heat-agent, not via user_data."
1766552,2019-09-15 16:55:28 UTC,Migrated to https://github.com/widelands/widelands/issues/568
1766552,2018-05-26 13:25:15 UTC,Possible starting point for a solution:
1766552,2018-09-24 11:16:12 UTC,"Accessing the Windows API without VisualStudio is non-trivial, so I'm retargeting this bug."
1766552,2018-04-30 07:15:35 UTC,"@SirVer: Do you have any idea how we might get at the actual screen resolution here, so that we can shift our pixels properly?"
1766552,2018-05-01 18:47:44 UTC,¯\_(ツ)_/¯ No idea.
1766555,2019-03-16 01:58:15 UTC,"I suggest to just use the AppImage provided on the scad download page.  The latest build at the moment, is OpenSCAD-2019.01-RC3.1-x86_64.AppImage"
1766555,2019-01-08 17:46:52 UTC,"using bionc-s build seems to work - just swap the ppa /etc/apt/sources.list.d file relase definition from cosmic to bionic. Any library related crashes you  MAY get are probably because of lib version incompatibility, so don't report any bugs to openscad from this hack. that said, it worked for the models I had."
1766555,2019-01-07 00:23:14 UTC,"I upgraded to Ubuntu 18.04, and found that I couldn't use openscad anymore.
I ended up here, this sucks."
1766555,2018-12-31 14:11:54 UTC,"Missing in 18.10, need it back asap please. ppa:openscad/releases also doesn't work for me."
1766555,2018-12-23 13:21:06 UTC,Openscad is great and worked very cleanly so far in previous ubuntu builds. I am hoping to get it from ubuntu repo ASAP.
1766555,2018-12-22 02:03:21 UTC,"Yes, missing in 18.10 and adding the ppa:openscad/releases repository doesn't work for me."
1766555,2018-12-08 14:33:51 UTC,Looks like it's missing from Ubuntu Cosmic (18.10) also.
1766555,2018-11-20 18:09:15 UTC,+1
1766555,2018-10-13 20:26:55 UTC,Yep got this problem and tired varios methods of installing it but every method runs into the same runtime error:
1766555,2018-10-09 16:01:12 UTC,"Can we still try to get openscad released in Ubuntu for bionic?  If it's going to take time to fix the arm failure, perhaps at least release it for the architectures that do build, especially amd64, which is what most openscad users will have."
1766555,2018-07-28 18:47:46 UTC,"When I installed Bionic in April there where several problems, among openscad whas one. This and other information about the future of Ubuntu made me to leave Ubuntu for my work, after 10 years, in favor of Debian.
Is Mark Shuttleworth doing a ""Red Hat""? In any case its nice to get rid of commercial considerations."
1766555,2018-07-28 13:31:28 UTC,"Well, it seems this won't be addressed anytime soon...  :/"
1766555,2018-08-04 06:18:49 UTC,"it  ""failed to build"", but in the link they say it ran out of virtual memory on their MIPS architecture build."
1766555,2018-07-18 07:37:51 UTC,+1 for getting it back in the distro. I was quite confused when it was suddenly gone.
1766555,2018-04-24 16:21:42 UTC,Thanks for reporting.
1766555,2018-04-25 06:13:36 UTC,Did you mean it was removed because it fails to build on mips/mipsel?
1766555,2018-07-23 07:57:57 UTC,"OpenSCAD missing in Ubuntu? This is bad. Creativity and media production is one of the areas where Open-Source software shines and has most potential to attract new users IMHO. OpenSCAD is just one crucial piece of software in this area, and missing it will hurt Ubuntu.
The Rep-rap community for instance is booming since the last 2 or 3 years, and I have seen many Windows users dip their toes in Ubuntu for the first time just because of the availability and ease of installation of OpenSCAD among other such tools. I am not an experienced package maintainer, but if there is something else I can do to help, let me know."
1766555,2018-04-28 10:14:49 UTC,As I proposed on askubuntu (https://askubuntu.com/a/1027764/454520) here is a temporary workaround : installing the debian/sid package.
1766555,2018-04-28 15:19:08 UTC,">Did you mean it was removed because it fails to build on mips/mipsel?
"
1766555,2018-04-25 15:54:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766555,2018-06-03 17:32:30 UTC,OpenSCAD is utterly important for my work. It was very irresponsible that the Ubuntu maintainers took if off the distribution's official repositories just because it wasn't compiling in a platform Ubuntu doesn't even have builds for.
1766555,2018-06-03 20:08:23 UTC,"OpenSCAD is also of key importance to my workflow, too."
1766555,2018-06-09 08:08:56 UTC,I would like to add my voice to those who have been negatively effected by this issue. We use openscad in a professional production setting.
1766555,2018-05-24 17:10:56 UTC,"To those who are like me desperately missing OpenSCAD, but who'd prefer another solution than installing the .deb package:"
1766556,2019-11-25 07:21:35 UTC,Currently it has 2.42.1-1
1766558,2018-05-14 07:29:43 UTC,This is now Ok without my having done anything except run Software Update.
1766558,2018-07-31 04:13:58 UTC,Now happening on clean install of Bionic.
1766565,2018-07-13 11:17:20 UTC,"This issue only happens on the KVM kernel, Bionic generic works fine with it."
1766565,2019-08-29 15:13:23 UTC,I do not see this occuring anymore on bionic / linux-kvm 4.15.0-1043.43
1766565,2019-08-29 15:16:46 UTC,"latest run of ubuntu_sysdig the module now installs properly as expected, the test itself still fails due to raw data can't be found for the initial test"
1766565,2019-08-29 15:16:53 UTC,"08/29 11:20:26 DEBUG|     utils:0153| [stdout] == sysdig smoke test to trace dd, cat, read and writes ==
08/29 11:20:26 DEBUG|     utils:0153| [stdout] Limiting raw capture file to 16384 blocks
08/29 11:20:26 DEBUG|     utils:0153| [stdout] Try 1 of 10
08/29 11:21:13 DEBUG|     utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:21:21 ERROR|     utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:21:21 DEBUG|     utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:21:21 DEBUG|     utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:21:21 DEBUG|     utils:0153| [stdout] Try 2 of 10
08/29 11:22:08 DEBUG|     utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:22:16 ERROR|     utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:22:16 DEBUG|     utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:22:16 DEBUG|     utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:22:16 DEBUG|     utils:0153| [stdout] Try 3 of 10
08/29 11:23:03 DEBUG|     utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:23:12 ERROR|     utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:23:12 DEBUG|     utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:23:12 DEBUG|     utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:23:12 DEBUG|     utils:0153| [stdout] Try 4 of 10
08/29 11:23:59 DEBUG|     utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:24:06 ERROR|     utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:24:06 DEBUG|     utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:24:06 DEBUG|     utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:24:06 DEBUG|     utils:0153| [stdout] Try 5 of 10
08/29 11:24:53 DEBUG|     utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:25:01 ERROR|     utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-1670.tmp.raw': No such file or directory
08/29 11:25:01 DEBUG|     utils:0153| [stdout] Raw capture file is 0 Mbytes
08/29 11:25:01 DEBUG|     utils:0153| [stdout] Converted events file is 0 Mbytes
08/29 11:25:01 DEBUG|     utils:0153| [stdout] Try 6 of 10
08/29 11:25:48 DEBUG|     utils:0153| [stdout] Could not find start of capture message, maybe sysdig didn't start?
08/29 11:25:57 ERROR|     utils:0153| [stderr] stat: cannot stat '/home/ubuntu/autotest/client/results/defa..."
1766568,2018-05-14 07:23:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766569,2018-04-24 12:27:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1766576,2018-04-27 05:54:13 UTC,related to bug #1602749
1766582,2020-01-22 16:35:25 UTC,This issue was fixed in the openstack/tempest 23.0.0 release.
1766582,2019-11-12 19:00:13 UTC,"Reviewed:  https://review.opendev.org/686738
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=7ca8602380d5959c273799fb0fae7d2b32cde9ea
Submitter: Zuul
Branch:    master"
1766582,2019-10-04 14:41:31 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686738"
1766582,2019-10-04 13:54:50 UTC,"I get the current flow, what I don't understand is, why we need to create another temporary manager [1] when we already have an admin one [2]. Why don't use just the admin one?
In that case we:
  1. don't need _add_admin method, _remove_admin_user_roles method and _remove_admin_role method
  2. we don't need to request new credentials with every project which is about to be deleted
  3. the whole cleanup process will be faster (less methods, less calls, no requesting credentials repeatedly)"
1766582,2019-10-03 17:45:05 UTC,"_clean_project() is using project['name'] for creating the creadential manager[1] is fine here as this method cleanup the project's resources do not delete the project itself. So flow is like below
- cleanup() function assigned the admin role to project to be cleaned up if not admin
- _clean_project() will go to each regoster service and delete their resources under that project
- cleanup() will call run on each self.global_services where project is added as one of the service. This will delete the project. And in this we use the admin_mgr[2]."
1766582,2019-09-30 21:05:02 UTC,"The unauthorized error is thrown not during deleting the project itself, but before when the tool is assigning [1][2] an admin role to the project for a user running the cleanup (in my case in the previous comment #1, the tool is assigning admin role to the test project for admin user). Apparently that's unauthorized."
1766582,2019-09-30 20:55:06 UTC,Steps to reproduce:
1766582,2019-10-03 07:40:38 UTC,"To be more precise than in the previous comment, the error is thrown when the credentials are obtained [1]. It's because the tool is trying to authenticate using the project name which is gonna be deleted. In this case the project is in a different domain than the user - the user's domain has no knowledge of the project - so it fails. It would make more sense if the tool used CONF.auth.admin_project_name instead of the project name which is about to be deleted. CLI client does that the same way, it authenticates using user's credentials (including admin_project_name)."
1766595,2018-05-09 17:02:59 UTC,"Why are we opening a new linux-azure-edge here? The 4.15 kernel should be going to -proposed as ""linux-azure"" this week."
1766595,2018-05-16 09:21:30 UTC,"Hardware Certification is not run on -edge kernels, setting certification-testing to 'Invalid'."
1766595,2018-05-22 13:35:40 UTC,All tasks have been completed and the bug is being set to Fix Released
1766597,2018-05-04 11:01:07 UTC,"Ad #16, I personally don't really think forcing arbitrarily curved rastnests are better. I don't agree with 	#15, although I think the icon commented look ok as proposed by Blubberbub, but no strong opinion here."
1766597,2019-04-09 21:14:16 UTC,I rebased the patch on `master` and fixed the conflicts. Only very minor changes were necessary to make it work (the way bitmaps are handled changed slightly).
1766597,2018-05-04 11:08:17 UTC,I believe our decision making looks something like (in priority order):
1766597,2018-05-04 11:38:01 UTC,We are in feature freeze so this isn't going to happen until after the v5 release.  I haven't had time to review or test the patch yet and I probably wont until after v5 is out.
1766597,2018-12-11 19:23:55 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1766597,2019-04-09 16:46:09 UTC,"@Blubberbub, master is now open for 6.0.  Can you rebase your patch so I can apply it?"
1766597,2019-04-09 22:41:23 UTC,"One small request:  Can you change the license of the artwork to CC-BY-SA-4.0?  In Inkscape, this is under Document Properties."
1766597,2018-05-04 10:37:32 UTC,I don't know how such things are decided in this project. Is there someone that just makes a decision? Will there be a poll?
1766597,2019-04-11 17:39:43 UTC,Added the licence to the .svg file and used `git format-patch` to format the patch this time. Tried to match the commit message format.
1766597,2019-04-11 21:31:23 UTC,Perfect.  I'll merge it to master.
1766597,2019-04-14 18:28:28 UTC,May I kindly ask that every option we add is available in the Preferences dialog and not only through an icon in the toolbars?
1766597,2019-04-15 20:30:02 UTC,"Hi Tom,"
1766597,2019-04-15 21:04:46 UTC,This patch really should have been cleaned up before it was pushed into master.  There are a lot of coding policy violations.  We really need to start doing a better job of enforcing this.  I'm seeing way too many coding policy issues as I traverse through the KiCad source.
1766597,2019-04-15 23:05:35 UTC,"@Blubberbub My comment wasn't directed exclusively at you, sorry if it sounded thay way. What I meant is that there are many functions of KiCad accessible only by toolbars or hotkeys that have no menu entries or checkboxes in the Preferences dialog. This is confusing and contributes to the perceived complexity/weirdness of Kicad GUI."
1766597,2019-04-10 13:56:13 UTC,"@Blubberbub, also the way your patch is formatted (just a diff?) will commit the changes under my name instead of yours.  Can you use git format-patch to make the patch?  That way you'll get credit for it."
1766597,2018-05-02 14:00:27 UTC,"I’d argue that it only changes graphics, not workflow."
1766597,2018-04-28 20:24:01 UTC,"For the ""making it optional"" i would like to add a toggle button to the left of the canvas similar to the buttons that control the pad and via style. But I haven't really found out how to do that, so i need a hint on how to achieve that. (Or it might be a trivial task for someone else more familiar with the code base?)"
1766597,2018-05-02 13:11:09 UTC,Not bad for programmer-art. ;)
1766597,2018-04-25 06:25:21 UTC,"As a first-time-supporter to this project: How likely is it that a ""reasonable good"" patch for this feature is going to be merged?"
1766597,2018-04-25 06:37:49 UTC,"I would be fine with such patch, given it remains selectable as an option."
1766597,2018-04-25 14:07:54 UTC,"And it doesn't conflict with this:
http://docs.kicad-pcb.org/doxygen/v6_road_map.html#v6_pcb_ratsnest_improvements."
1766597,2018-04-26 19:23:08 UTC,"This is the patch i'm trying to test, but i'm still fighting a little bit with the build environment."
1766597,2018-04-26 19:48:57 UTC,"General comments:
- You are implementing this in the legacy canvas.  This canvas will be removed in the not-too-distant future.  New features should be implemented in the GAL canvas.
- Be sure to keep track of limits or you will end up with arcs >360"
1766597,2018-04-26 19:49:34 UTC,Third general comment: Neat idea! :)
1766597,2018-04-25 08:58:01 UTC,+1
1766597,2018-04-27 15:32:45 UTC,"It wasn't the order of the points, but i was missing ""s.x + "" and ""s.y + "" in the cx/cy calculation. Ooops."
1766597,2018-05-02 13:40:52 UTC,"I'm glad you like it, Jeff."
1766597,2018-04-28 20:44:20 UTC,Your revised patch works better.
1766597,2018-05-02 12:07:24 UTC,"I switched back to using arcs for legacy rendering, because bezier turned out to be horrible slow.
Also i added a button that allows to toggle between curved and straight lines. (Programmer-Art included)"
1766597,2018-04-27 12:45:45 UTC,Thanks for your comments. These are very much appreciated.
1766597,2018-05-02 12:25:40 UTC,Maybe thy this. Just use the global deletions menu to delete all tracks.
1766597,2018-05-02 12:55:41 UTC,You can see a comparison and my programmer-art toggle-icon here: https://imgur.com/a/7AVqrQ7
1766606,2018-07-31 15:01:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766609,2018-04-24 17:53:50 UTC,"Hi,"
1766609,2018-04-24 17:54:28 UTC,Correction: pcb-4.2.0 ;-)
1766613,2018-05-20 16:17:55 UTC,"Hi Charles,"
1766627,2018-04-24 18:59:59 UTC,This bug was fixed in the package shim-signed - 1.34.9
1766627,2018-04-24 15:10:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766627,2018-04-24 17:07:16 UTC,This bug was fixed in the package shim-signed - 1.34.8
1766627,2018-04-24 17:31:23 UTC,"Reopening; the fix in 1.34.8 was overbroad, there is a new fix in 1.34.9 currently in bionic-proposed."
1766627,2018-04-24 17:33:24 UTC,We believe grub-efi-amd64 should also be fixed to not call update-secureboot-policy anymore.
1766628,2018-04-26 13:26:05 UTC,ubuntu 16.04 apparmor vlc rules
1766628,2018-04-26 13:24:01 UTC,The same happens on Ubuntu 16.04.
1766628,2018-04-24 20:12:53 UTC,The same happens with VLC snap on Ubuntu 18.04 beta.
1766628,2018-04-24 20:13:50 UTC,I should also add that this is only activating when XDG_CURRENT_DESKTOP=KDE is set and when Qt5 tries to launch kio/ksysoca to show proper KDE file open dialogs.
1766636,2018-05-04 08:54:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566243"
1766636,2018-05-08 10:11:54 UTC,"Change abandoned by Albert Mikaelyan (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/566119"
1766636,2018-05-08 10:11:15 UTC,"Change abandoned by Albert Mikaelyan (<email address hidden>) on branch: master
Review: https://review.openstack.org/566243"
1766636,2018-05-08 10:09:23 UTC,"Change abandoned by Albert Mikaelyan (<email address hidden>) on branch: master
Review: https://review.openstack.org/566269
Reason: Going to work on different approach here"
1766636,2018-05-08 10:09:01 UTC,"Change abandoned by Albert Mikaelyan (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/566121"
1766636,2018-05-04 10:03:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566269"
1766636,2018-05-04 08:28:05 UTC,"Problem found with the latest fix, as the version needs to be always checked, even when running rabbitmq_upgrade"
1766636,2018-05-03 17:08:29 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/566121"
1766636,2020-09-18 13:25:59 UTC,"Tbh I can't agree that there's no reason in doing anything when rabbitmq_upgrade is true, but the version is the same. As I really use that flag when I want to re-configure rabbit (ie re-create queues and etc), and this flag works like a magic when rabbit is stuck. So I'd rather either won't touch behaviour of upgrade flag or create another one which would dublicate that behaviour.
And there's no downtime of openstack services, because we use HA queues for rabbit, so we have only single server down, while 2 others continue operations. So no downtime when running with that flag is expected."
1766636,2018-05-03 17:07:09 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/566119"
1766636,2018-05-03 16:55:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/566116"
1766636,2018-05-03 15:44:37 UTC,"Reviewed:  https://review.openstack.org/566017
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-rabbitmq_server/commit/?id=c78e0b1d026ff34a53143fb897df0fdc8c5f8342
Submitter: Zuul
Branch:    master"
1766636,2018-05-03 10:08:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566017"
1766636,2018-05-03 02:49:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/565940"
1766636,2018-05-03 18:19:41 UTC,"Reviewed:  https://review.openstack.org/566116
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-rabbitmq_server/commit/?id=bfd11dbb89ce1428a4dc85b64f5df154157b06ab
Submitter: Zuul
Branch:    stable/queens"
1766640,2018-05-21 14:39:11 UTC,"For some of our public libraries, they might not want the name to appear on the printed pull list, but they may want it to show up on the pull list on the screen. Often libraries use a staff card to request multiple copies of a title for book clubs. The card often has ""Book Club"" in either the first or last name field. We have some libraries that don't want to sent their books for these requests, so they retarget those holds."
1766640,2018-05-21 15:16:55 UTC,"I understand the confidentiality concerns, but, if a library has such concerns, they can opt not to display the columns and they therefore would not appear in Print Full Gride. They can be displayed in XUL so, unless there is a good technical reason to suppress them in Print Full Grid in Webby (if the library desires it), it should be possible."
1766640,2018-05-21 14:10:22 UTC,I heard back from the library that brought this to my attention:
1766640,2020-05-20 14:46:02 UTC,"Here is another use case for having patron name on the pull list (especially now that lots of libraries are using curbside pickup): ""We are running the pull list and getting books upstairs and downstairs so if the name was printed on the list, we could coordinate patron pickups. Guess we'll have to make do. In the old system we used it a lot to consolidate items and limit holds so I am disappointed because now it is right there and I can see it but doesn't print."""
1766640,2020-05-20 15:28:12 UTC,"FYI - until this bug is fixed, I've found that if you have the patron name displaying on the grid and you use the browsers File > print function it will print the names. (But then you have to do it with each page if you have more than 100 items.)"
1766640,2019-01-23 18:51:10 UTC,This is being brought up again by our libraries now that they no longer have XUL available (where the names did print).
1766640,2018-05-18 13:51:47 UTC,">>the person's hold for whom the item is currently targeted is not necessarily (and in a busy system, even often) the hold that the item will fill at scan time<<
"
1766640,2018-05-17 18:57:07 UTC,I have concerns about including the patron name on printed pull lists. This is a confidentiality issue for our consortium. We would prefer names not be available on printed pull lists at all.
1766640,2018-05-17 19:18:40 UTC,"I agree they shouldn't be on the default printed list, and they're not something we would want to use in our public libraries, but I could see use cases where the patron names might be useful (for example, an academic library might want to prioritize holds for faculty)."
1766640,2018-05-17 15:14:37 UTC,We just discovered that the Patron First Name and Patron Last Name also do not appear in Print Full Grid in the Holds Pull List.
1766640,2018-04-25 21:10:57 UTC,"After some testing of the 'null' issue I think it is worthy of its own LP ticket, which I've created at bug 1766982"
1766640,2018-04-25 15:02:02 UTC,This is problematic for our libraries that generate pocket labels from Item Status .csv output (of which we have several).
1766640,2018-04-25 14:58:30 UTC,"It looks also like any field being displayed on the screen that doesn't have a value will show as ""null"" in the csv output. It should come over as just blank rather than the words ""null""."
1766640,2018-05-17 21:30:21 UTC,"Terran,  I can understand the thinking behind the faculty use case, unfortunately the person's hold for whom the item is currently targeted is not necessarily (and in a busy system, even often) the hold that the item will fill at scan time.  The specific hold that the copy is attached to on the pull list is for all intents and purposes an artifact of how the hold and copy data is stored."
1766642,2018-05-11 02:18:45 UTC,What about this?
1766648,2018-05-08 07:07:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766648,2018-08-21 04:43:12 UTC,My crash has been avoided for now by deleting the index:
1766652,2018-07-20 14:33:46 UTC,"Nope, seems fixed now. Thanks!"
1766652,2018-07-20 14:23:27 UTC,does this still happen with Kirigmai master from 20th july 2018 or more recent?
1766652,2018-06-21 01:50:06 UTC,*** Bug 395176 has been marked as a duplicate of this bug. ***
1766652,2018-04-06 18:26:18 UTC,*** Bug 392547 has been marked as a duplicate of this bug. ***
1766652,2018-04-05 19:53:41 UTC,"Created attachment 111858
Screen recording depicting the issue"
1766652,2018-04-06 00:14:07 UTC,"Same here, with Plasma 5.12.80 and KF 5.45, compiled from git yesterday."
1766652,2018-04-06 07:48:17 UTC,Also reported in Fedora
1766656,2020-08-26 15:49:06 UTC,"Hello,"
1766656,2020-10-26 04:17:19 UTC,[Expired for netplan because there has been no activity for 60 days.]
1766656,2018-07-17 05:18:28 UTC,Set status to new again - the specification about behavior is still missing.
1766656,2018-10-02 06:36:06 UTC,"Moreover, I don’t see a specified way to add an IP to an existing interface as a primary or secondary.  For me, is was added as the primary address.  But it needs to be documented."
1766656,2018-05-16 10:56:32 UTC,"Sure. Attached an example netplan and output of ""ip addr""."
1766656,2018-05-15 21:17:28 UTC,"Hello,"
1766656,2018-07-16 04:17:58 UTC,[Expired for netplan because there has been no activity for 60 days.]
1766657,2018-04-26 21:19:49 UTC,"Can you share an example file, please? This is not normal behaviour, probably something about your tool's default settings got messed up."
1766657,2018-05-09 18:36:16 UTC,I just made some changes to the template loaded on start. I turned off page edges and added a grid.
1766657,2020-09-09 16:32:03 UTC,Closing because INVALID: Can't replicate.
1766659,2018-04-24 16:38:12 UTC,@ Will Cooke
1766659,2018-04-24 18:04:35 UTC,I confirm that we should not have ifupdown in the default desktop install in 18.04 and that it would be reasonable IMHO to move pppoeconf to ship-live.  I am deferring to Adam to decide whether to accept this change due to the timing of release.
1766659,2019-05-09 22:32:23 UTC,This did not get acked in time for bionic but still needs doing on eoan; merging now.
1766659,2019-05-09 23:55:40 UTC,This bug was fixed in the package ubuntu-meta - 1.433
1766661,2018-06-27 22:07:14 UTC,"Reviewed:  https://review.openstack.org/571982
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=22ef3465215941097a96f078ae93aa65758d5a64
Submitter: Zuul
Branch:    master"
1766661,2018-06-03 18:39:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/571982"
1766661,2018-06-03 18:34:07 UTC,So the fact the interaction with ironic will likely need some extra work down the road since we still need to store a copy in Ironic..
1766661,2018-05-03 15:40:37 UTC,https://review.openstack.org/#/c/541420/ is also related for boot from volume to create new-style volume attachments.
1766661,2018-05-03 15:38:22 UTC,"Nova tracks bugs in launchpad, not storyboard, so this is OK for the nova bug. SB is fine for tracking ironic-specific work."
1766661,2018-04-26 16:28:06 UTC,"So a few different things, and my apologies if this comes across as a stream of consciousness."
1766661,2018-04-26 21:17:30 UTC,"One of the other items I noticed in the ironic code is that it assumes that the only way to return multipath = True, is if there are more than 1 connectors created in ironic.   This isn't a requirement for multipath to work.  In fact most multipath deployments rely entirely on the target side to export the volume via multiple ports."
1766661,2018-04-24 17:03:32 UTC,"Also,
  Here is a list of other cinder drivers and libraries that assume that the host entry
is always there for attach and detach."
1766661,2018-04-26 21:21:15 UTC,"I have created a storyboard bug for this. here:
https://storyboard.openstack.org/#!/story/2001926"
1766663,2018-04-26 05:06:21 UTC,Thank you for you quick response.
1766663,2018-04-24 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1766663,2018-04-24 17:09:56 UTC,apport information
1766663,2018-04-24 17:09:58 UTC,apport information
1766663,2018-04-25 21:15:04 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1766663,2018-04-26 11:55:09 UTC,"Hello,"
1766664,2018-04-25 22:35:41 UTC,"Matt, I am very sorry that you were hit by drupalgeddon 2.0. drupal7 is community supported in Ubuntu which means that it only gets updated when an Ubuntu community member supplies a debdiff."
1766664,2018-05-19 16:08:38 UTC,"Hello,"
1766666,2018-05-04 06:54:02 UTC,"I'm curious about syntax for this, and if it is always true that you want machines and not containers. We have talked about having machine subordinates. Or possibly model subordinates. Figuring out the syntax is still something we'd need to go through."
1766677,2018-06-06 20:11:19 UTC,"I think I figured out what's going on.  The functional testenv definitions in tox.ini have sitepackages=True.  It looks like tox only installs the requirements that aren't already present on the system in that case, so whether you see this message or not depends on whether you have stestr installed somewhere in your path.  I guess we could whitelist stestr for this case?  Probably not worth worrying about."
1766683,2018-04-24 20:21:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1766683,2018-04-25 09:42:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766683,2018-04-27 19:24:45 UTC,"Nicolas, could you please test the powerdevil build in our landing ppa with the patch applied?"
1766683,2018-05-03 12:58:48 UTC,"Rick,"
1766687,2018-04-24 18:52:17 UTC,Pls help me x
1766695,2020-09-21 14:48:26 UTC,"Noticed a similar issue today. With the difference that in my case, sesman would never come up. Found out that I was hitting [1]. Had to use workaround from [2]."
1766695,2018-06-30 09:31:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766700,2018-07-09 18:40:39 UTC,Just hit it again
1766700,2018-08-21 03:59:50 UTC,Have you seen this after the removal of PKI token support in [0]?
1766700,2019-05-13 18:17:29 UTC,There seem to be two separate bugs here.
1766700,2019-07-13 04:18:08 UTC,[Expired for OpenStack keystone charm because there has been no activity for 60 days.]
1766701,2018-10-18 00:42:49 UTC,"Reviewed:  https://review.openstack.org/611247
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f9cf83474971dfc0f47c1ee9b6d5d17583e1bf51
Submitter: Zuul
Branch:    stable/ocata"
1766701,2018-11-06 06:09:11 UTC,This issue was fixed in the openstack/neutron 11.0.6 release.
1766701,2018-10-20 02:16:18 UTC,"Reviewed:  https://review.openstack.org/611246
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c78b80becfd6ad5865fb1681a05395940591f431
Submitter: Zuul
Branch:    stable/pike"
1766701,2018-10-17 06:45:59 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/611247"
1766701,2019-03-25 20:37:42 UTC,This issue was fixed in the openstack/neutron-tempest-plugin 0.3.0 release.
1766701,2018-10-17 06:42:15 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/611246"
1766701,2018-10-17 06:48:17 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/590422
Reason: It's already done in https://review.openstack.org/#/c/602696/3"
1766701,2018-09-24 16:39:03 UTC,Fix was merged https://review.openstack.org/#/c/602696
1766701,2018-09-14 21:28:50 UTC,Patch proposed for neutron-tempest-plugin: https://review.openstack.org/#/c/602696
1766701,2018-08-08 12:20:40 UTC,"These tests are currently marked unstable, so will not appear with failed build_status?
https://github.com/openstack/neutron-tempest-plugin/commit/02a5e2b07680d8c4dd69d681ae9a01d92b4be0ac"
1766701,2018-08-02 14:58:05 UTC,Using:
1766701,2018-07-19 17:12:00 UTC,Using following query:
1766701,2018-10-16 20:34:19 UTC,Do we need to backport his patch?
1766707,2019-09-19 14:47:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1766709,2018-04-30 19:57:20 UTC,"It happened again, this time when I opened Steam.
This time I saved the dump file, after the crash logs, I hope it will be useful."
1766709,2018-08-10 14:39:01 UTC,The problem seems to have been resolved by updating the NVIDIA 390.77 drivers from the PPA: https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
1766709,2018-08-10 14:45:13 UTC,"On the Ubuntu repositories there is still the NVIDIA 390.48 driver, please upgrade to version 390.77"
1766710,2018-04-27 02:27:39 UTC,"Next, please report the problem to the dock developers here:"
1766710,2018-04-27 02:25:07 UTC,Thanks. Yes I somehow missed the part about auto-hide.
1766710,2018-04-26 07:42:30 UTC,"Okay, apport integration all set, report submitted. The background color of the shell is consistent if the Dock is not set to auto-hide, but with auto-hide on it will turn grey without the Top Bar inhereting."
1766710,2018-04-26 07:40:59 UTC,apport information
1766710,2018-04-26 07:40:56 UTC,apport information
1766710,2018-04-26 02:09:57 UTC,I can't seem to be able to reproduce the problem (in Ubuntu 18.04).
1766710,2018-04-26 07:40:57 UTC,apport information
1766717,2018-04-24 21:21:23 UTC,Is this the same system as in bug #1766018?  Do you now have it booted in BIOS mode instead of UEFI?
1766717,2018-04-24 23:24:43 UTC,Yes I have it booted in BIOS mode and the pendrive is set to boot in MBR. Probably same bug.
1766717,2018-04-25 06:04:44 UTC,"Ok.  It is known that shim-signed does not install on systems not booted in UEFI mode, because it expects to write to UEFI nvram variables."
1766717,2018-04-25 06:17:13 UTC,"Just uninstalled shim (or shim-signed can't remember).
It should have a way of detecting boot mode I guess."
1766718,2019-08-13 15:24:52 UTC,We received another request to modify this drop down menu.
1766728,2018-08-27 12:21:03 UTC,I have tested the the current linux-base in trusty-proposed (4.5ubuntu1~14.04.1) and I couldn't find any issues.
1766728,2018-08-27 13:07:53 UTC,This bug was fixed in the package linux-base - 4.5ubuntu1~14.04.1
1766728,2019-03-18 15:03:38 UTC,I am still having this issue while performing a fresh install of Xenial.
1766728,2018-05-01 15:49:14 UTC,I tested upgrades from xenial to bionic or linux-hwe-edge upgrades from xenial-updates to xenial-proposed after a linux-base upgrade to the one in xenial-proposed.
1766728,2019-03-19 15:49:12 UTC,Ditto. Netinstalls are broken and the installer ignored the suggested workaround in our kickstart:
1766728,2018-07-30 14:13:45 UTC,"Hello Thadeu, or anyone else affected,"
1766728,2019-03-19 09:59:53 UTC,We have still this issue with fresh install Xenial too.
1766728,2018-05-01 15:40:45 UTC,"The verification of the Stable Release Update for linux-base has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1766728,2018-05-01 15:40:40 UTC,This bug was fixed in the package linux-base - 4.5ubuntu1~16.04.1
1766728,2018-05-01 15:34:06 UTC,We will not need this in artful as we will not backport kernels there which need it.
1766728,2018-04-30 02:26:47 UTC,Fixed installing mainline PPA 4.17.0-041700rc2-generic on 16.04.4.
1766728,2018-04-25 21:04:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766728,2018-04-25 21:04:05 UTC,I can confirm this fixes 4.17-rc2 from mainline ppa for xenial. Thank you!
1766728,2018-04-25 16:46:18 UTC,"Hello Thadeu, or anyone else affected,"
1766728,2018-04-25 14:35:07 UTC,cascardo asked me to sponsor his upload to xenial-proposed. I've compare the build logs between the 4.0ubuntu1 version currently in xenial to the build logs from his 4.5ubuntu1~16.04.1 change. The build logs are clean with no surprises. I also compared the binary packages and was able to confirm his assertion that the perf bash completion file is not distributed.
1766729,2018-04-24 22:33:05 UTC,The error in your log is:
1766729,2018-04-25 14:15:29 UTC,"Hi,"
1766732,2018-04-24 22:57:19 UTC,"Hmm, no way to delete my now nonsensical comments?"
1766732,2018-04-28 15:14:30 UTC,"I agree, ""references"" misleads."
1766732,2018-04-25 12:01:25 UTC,"[No way to amend nor delete even fresh unseen comments - huge flaw in this ""launchpad"" tool?]"
1766732,2018-04-25 11:43:52 UTC,"I wonder if it's the verb ""reference"" that makes it unclear."
1766732,2018-04-25 10:49:05 UTC,"Why should the warning use the same language as the code itself?
Because the current warning is ambiguous and unclear."
1766732,2018-04-24 22:51:34 UTC,"Argh, isn't there some way to edit a bug report?  Use patch#3."
1766732,2018-04-24 22:49:45 UTC,"Oops, ignore the description and use the attachment."
1766732,2018-04-25 08:44:26 UTC,Why do you say the warning refers to values?
1766746,2018-04-25 02:24:04 UTC,"After discussing this on IRC it seems it could be a quirk of how the UI works: if you want to save the current config, you need to make sure that ""current config"" is selected in the list. Otherwise it will make a direct copy of whatever you do have selected."
1766746,2018-04-25 01:05:33 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766746,2018-04-25 02:01:03 UTC,"Hi. I wrote the patch that was applied in the most recent version, and I think I have seen your issue too. However, I don't understand how my patch could have fixed it."
1766746,2018-04-26 01:16:10 UTC,"Hi again - I didn't see your second message, about IRC conversation, until
just now.  But this suggestion seems not to be the case.  Here's my
experiment:
I modified a Gnome 2 panel and attempted to save it, but just copied the
Bionic ""current configuration.""  Failure.  Then I suspended the computer.
When I resumed, I saved the configuration, with Current Configuration
selected.  This time it worked.  Just as I was able to save a modified
Bionic config right after installation.  I think it's significant that both
times, I was able to save modifications to whatever config the session
started with.
After this success, I applied Redmond, modified it, and tried to save it.
But what was saved was the modified Gnome 2.  Which is the configuration
that was active when the session started.
I'm pretty sure that having Current Configuration selected saves the
configuration that's active when you log in, not the configuration you have
at the moment you save.  I could be wrong, but I hope this helps."
1766749,2018-10-01 20:15:09 UTC,I found this problem just a week ago put i can't reproduce it.
1766749,2018-04-30 00:36:29 UTC,"This bug also affects me, system details
Dell optiplex 990 USFF booting in legacy.
Memory - 4gb
Processor - Intel(R) Core(TM) i5-2500s CPU @ 2.5GHz"
1766749,2018-08-08 09:34:29 UTC,"I found out (to be seen on the screenshot)that the doubled Application Icons showed different network/HD load but the same CPUload. And if under some circumstanses if i open the NetworkIcon to the right (up/down arrows) there are to different kinds of the fonds (one seams to be bold, the other normal). but i can not reproduce the problem for shure, next time it could look other way."
1766749,2018-08-08 09:22:08 UTC,"this bug effects me;
installed a fresh ubuntu mate 18.04.1 on a HPZ210 Workstation.
I used mate-tweak to switch to the old mate layout, then configured the panel.
I saved the panel. After a PC restart are some panel entries doubled. (see picture)
Tested with another savename, panelreset via gui and with mate-panel --reset,
nothing helps. Between my trials the panel disappered. After restart of the PC
the panel is back but I had the same problems.
I have no idea how to get back to a clean panel with only some little modifications
(CPUload, net...)"
1766749,2018-04-29 12:45:26 UTC,"Under UEFI I got double applets changing from the default panel layout (Familiar) to Mutiny, however logging out and back in fixed it, after restart no issue."
1766749,2018-04-28 00:10:54 UTC,"My Toshiba Satellite Laptop P50T -A is the computer I use to try a lot of Linux Distros, the UEFI was never stable so I've always installed under Legacy, after trying Ubuntu Mate Live on my main system with UEFI the results are very stable as is the Toshiba Laptop with UEFI, there are some anomalies switching from and to different panel layouts, however this is sorted by a logout and login scenario."
1766751,2018-04-25 01:37:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766751,2018-04-25 01:40:57 UTC,"I am also seeing this when using Alt+~ with Caja. It does not show up with Alt+Tab. (Show Desktop Icons must be enabled in MATE Tweak, which is the default, but not my normal personal preference.)"
1766751,2018-04-25 01:45:25 UTC,"I can also confirm with Metacity 1:3.28.0-1, so maybe it's a Caja issue, not a Marco one? Or just a flaw both share?"
1766751,2018-04-25 02:08:35 UTC,This selects the desktop itself (which is an instance of caja). The idea seems to be that you can switch between the applications and the desktop. Selecting the desktop allows you to then use the keyboard to move between desktop icons.
1766751,2018-04-25 02:36:41 UTC,"It only appears when using the shortcut labeled ""Move between windows of an application, using a popup menu"", and selecting it doesn't focus the desktop, it doesn't change the focused window."
1766751,2018-04-25 13:05:16 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766753,2018-05-04 12:21:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566303"
1766753,2018-04-25 08:30:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564130"
1766753,2018-05-04 12:51:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566307"
1766753,2018-06-07 09:26:31 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/564130"
1766753,2018-06-07 09:26:43 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/566307"
1766753,2018-06-07 09:26:48 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/566303"
1766758,2018-04-25 02:05:18 UTC,apport information
1766758,2018-04-25 02:05:16 UTC,apport information
1766758,2018-04-25 02:05:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766758,2018-04-25 02:00:08 UTC,"...this was after having installed Xubuntu successfully, and rebooted."
1766758,2018-04-25 02:05:14 UTC,apport information
1766758,2018-05-03 01:24:09 UTC,"So, I've freshly installed the release version of Xubuntu 18.04 and applied updates, and now Gnome-Mines uninstalls as expected."
1766761,2018-04-25 02:19:33 UTC,"For the avoidance of doubt, I saw this on the QA tracker's main page: http://iso.qa.ubuntu.com/"
1766763,2018-04-26 05:56:14 UTC,"> In testing the patch I proposed, it seems to help but we still seem to orphan some ports
"
1766763,2018-04-25 15:31:00 UTC,"So thinking about it a little further, it might make sense to lookup and delete the internal ports if the server is in error state. Since replace doesn't imply rebuild, as far as I'm aware.  I think ironic is the only case where rebuild deploys to the same node."
1766763,2018-04-25 14:37:23 UTC,"In testing the patch I proposed, it seems to help but we still seem to orphan some ports... although this does appear to be a case of resource exhaustion where a failed deploy can't be replaced because the number of instances requested exactly matches the number of available baremetal nodes. On a plus side, it is failing at that very last node now which is a positive sign for the patch in my mind. (tl;dr I'm testing in an environment with BMC issues which can cause deployments to baremetal nodes to fail quite reliably) :|"
1766763,2018-04-26 19:56:12 UTC,"The problem is not a failure to schedule, but a failure for the deployment to be successful resulting in the instance in ERROR state shortly after the node spawn action occurs in nova. But we would never be able to re-use the port in the baremetal context because it has changed, the binding profile has been set/asserted and changed... so realistically we might not be able to re-use the port or IP allocation which I believe it does already."
1766763,2018-04-25 05:37:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564104"
1766763,2018-04-30 21:37:43 UTC,"Harald your correct in that regard that if someone defines a port far upfront, submits it in for use, then... there is not much we can do short of possibly consider resetting the prior MAC address back in ironic."
1766763,2018-04-25 06:17:30 UTC,"1. when replacing instances (we do that when updating a FAILED server resources), we call detach_interface[1] when preparing for replacement, which seems to delete the internal port unless preserve_on_delete is True[2]."
1766763,2018-04-29 13:32:35 UTC,Zane made point on the patch review. Deleting implicitly created ports is not the full solution to this problem. This issue is there also when using non-implicit ports.
1766764,2018-04-25 03:23:40 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894066
1766765,2019-05-06 18:25:42 UTC,"(In reply to Landry Breuil from comment #1)

> I think the original idea of setting PATH to a limited 'trusted' list of
> subdirs was to avoid potential attackers/malwares to drop malicious
> replacements for xlock/etc in user-writable directories potentially in the
> user's PATH...
"
1766765,2019-05-13 11:37:10 UTC,*** Bug 8830 has been marked as a duplicate of this bug. ***
1766765,2019-05-08 17:06:50 UTC,David Thompson referenced this bugreport in commit fd46109d056237410cad6901272c86f6d55a293c
1766765,2019-05-06 04:21:05 UTC,"(In reply to Skunnyk from comment #11)

> I wanted to use ""command -p getconf PATH"" in xflock4 to set the path instead
> of an hardcoded value.
> However on FreeBSD this command does not add /usr/local/bin, which is where
> xflock4 is located… (this is patched in port tree).
>
> Or maybe simply use an hardcoded ""
> /usr/bin:/bin:/usr/sbin:/sbin:/usr/X11R6/bin:/usr/local/bin"" to try to be
> compatible with all OS,and let packagers patch if needed.
"
1766765,2019-05-05 20:48:18 UTC,"I wanted to use ""command -p getconf PATH"" in xflock4 to set the path instead of an hardcoded value.
However on FreeBSD this command does not add /usr/local/bin, which is where xflock4 is located… (this is patched in port tree)."
1766765,2019-04-29 11:53:33 UTC,"So, what can we do ? Add a bigger list of ""trusted"" paths ? Use the command -p trick (which does not include /usr/local on linux, but works on OpenBSD) ?"
1766765,2019-04-29 06:22:55 UTC,"But then that means whatever you set in xfconf needs to have the full path to the binary, otherwise xflock might not find it in $PATH :)"
1766765,2018-08-22 03:04:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766765,2019-04-28 22:32:55 UTC,"Since 4.13, xflock4 query xfconf to know which binary to run, no need to have a list of path in xflock4 directly: https://git.xfce.org/xfce/xfce4-session/tree/scripts/xflock4#n27"
1766765,2016-01-30 15:45:01 UTC,"Oh, unfortunately `command -vp` does not work by dash even in Linux, but works by bash. (https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1539932)"
1766765,2016-01-29 21:46:21 UTC,"I think xflock4 could use ""command -vp command_name"" to get the secure path of a locker command command_name. Would that work in GNU GuixSD, too?"
1766765,2016-01-29 20:03:30 UTC,How could you know that the command is not in a removeable drive then?
1766765,2016-01-29 17:30:19 UTC,(In reply to Jarno Suni from comment #2)
1766765,2016-01-29 13:59:32 UTC,"So isn't the solution then that system administer changes PATH so that it does not contain user-writeable directories? Well, in terminal a regular user can change PATH though."
1766765,2016-01-29 09:16:06 UTC,I think the original idea of setting PATH to a limited 'trusted' list of subdirs was to avoid potential attackers/malwares to drop malicious replacements for xlock/etc in user-writable directories potentially in the user's PATH...
1766765,2015-10-30 12:35:00 UTC,"Created attachment 6514
patch file"
1766765,2016-01-31 14:09:35 UTC,"`command -pv` or even `command -v` is not required in POSIX 2004
http://stackoverflow.com/a/34572831/4414935
but I think we can use `command -p getconf PATH` to get a reasonable PATH for the script."
1766775,2020-11-18 14:39:57 UTC,"Hello, I think I just got this bug."
1766775,2021-02-14 15:06:02 UTC,"In Ubuntu 20.04 I had the problem that the automatic suspend notification didn't disappear moving the mouse. I had to literally close the pop up by clicking on the X. I noticed that in Power Settings, ""Dim Screen When Inactive"" was turned off. I tried to turn it on, and now the pop up disappear by moving the mouse."
1766775,2020-12-14 18:52:19 UTC,"Arff I was too fast. It was ok, but it restarded 5 min ago >.>"
1766775,2020-12-14 18:45:09 UTC,"Hello, me again."
1766775,2020-08-11 10:03:30 UTC,"Closed upstream, because nobody could reproduce it?"
1766775,2018-06-05 13:20:40 UTC,"Strange, I didn't have this in 17.10 nor 18.04 before it was released. But now I do have this problem."
1766775,2018-06-05 13:23:07 UTC,"The gnome bug is only about the ""automatic suspend"" notifications. However, for me power notifications also do not disappear when I plug in my power cable."
1766775,2018-05-11 09:17:10 UTC,This still occurs in Ubuntu 18.04.
1766775,2018-04-26 02:11:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1766775,2019-11-19 07:15:36 UTC,"I have this bugin Ubuntu 19.10 Eaon.
The suspend notification never goes away; also there is a "" x "" button but instead of closing the popup when you click on it the ""settings"" will open up."
1766779,2020-10-09 19:56:58 UTC,"Hi,"
1766786,2019-04-05 15:33:53 UTC,"@ellayararwhy you can workaround this by setting the service provider to systemd, like:"
1766786,2019-03-27 22:09:42 UTC,"Easier said than done, seeing as AWS ubuntu 18.04 currently only has support up to Chef 12.18.31. IOW, it's impossible to do an OpsWorks run command that tries to do a update-rc.d -n ... (so much for no-ops)"
1766786,2018-10-16 16:58:57 UTC,@jjudd
1766786,2018-10-16 04:44:39 UTC,This issue was fixed in this commit in Chef. It's a 6 character diff. https://github.com/chef/chef/commit/5320cbf9b41789a46a5c5c0a2d818966c9716405?diff=unified#diff-8561ad40ccb208ff3c3f12bf88746df2
1766786,2018-10-16 04:42:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766808,2020-10-02 09:18:00 UTC,Fixed in https://review.opendev.org/#/c/575618/
1766812,2018-05-02 18:24:18 UTC,"That change seems to imply Pike, and there are a lot of changes after that on the stable/pike branch so it's not the latest code."
1766812,2019-04-18 15:07:10 UTC,Do you have plans to finish this patch? Or can someone else pickup this problem?
1766812,2018-08-31 07:41:40 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/566817
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1766812,2018-08-31 07:41:20 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1766812,2018-05-08 08:52:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566817"
1766812,2018-05-03 02:36:09 UTC,"For example, I have two dhcp agents, dhcp-agent-1, dhcp-agent-2.
When stop the dhcp-agent-2,after agent_down_time * 2, the networks will be rescheduled by neutron-server to delete from dhcp-agent-2 slowly. After a while, you can see that the networks will not exist in the dhcp-agent-2 in the neutron db.In the process, neutron-server will send messages(some like network operation and port update) to the dhcp-agent-2 queue and the messages heap up because the dhcp-agent-2 not work."
1766812,2019-07-24 15:42:29 UTC,We got the same behavior which makes the DHCP sync a very long process (more than 10 hours)!
1766812,2018-05-02 03:50:45 UTC,"Hi, my branch is based the commit:"
1766812,2018-04-25 08:54:42 UTC,"- ml2, tenant_network_types = vxlan, mechanism_drivers = openvswitch,l2population
- see attachment
- see attachment
- two all-in-one node (neutron-server ,dhcp agent, l3 agent)
- no vms
- see above attachment
- see above attachment"
1766812,2018-04-30 06:10:02 UTC,Thank you for your update.
1766812,2018-04-28 07:27:33 UTC,"After further testing, all-in-one environment(dhcp agent and controller services together), if I create 200 networks, the centos 7.2 system almost have 1400 tasks, and can reproduce the issue."
1766812,2018-04-25 10:22:33 UTC,"I find some information. When I do the steps, the normal dhcp agent will update the port too, but they were finished in two reqs, but the dhcp agent I restart did not, it is one req with one update the port message, so it has many reqs to deal at one time.
The attachment log is another dhcp agent I do not any operation.
the two reqs: req-7357bbe2-fc84-4679-9ada-508a951bae7e
req-6b3bae67-4547-45e3-8dbc-e70d8aec6840"
1766812,2018-04-25 08:28:30 UTC,Thank you for providing information about that issue. I would like to ask you few more questions:
1766812,2018-04-25 07:18:15 UTC,which version of openstack and os?
1766812,2018-04-30 21:41:37 UTC,Can you give the specific version of neutron you are using?  I'm wondering if this is related to https://bugs.launchpad.net/bugs/1750777 - seems very similar.
1766825,2018-10-23 16:12:41 UTC,"Kai-Heng Feng,
I have XPS 9370. It uses Killer 1435"
1766825,2018-10-22 22:02:45 UTC,Qualcomm released new firmware recently that's worth checking out: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qca?id=534daf431c88b24236d23572039cdd79223b246a
1766825,2018-10-19 05:57:50 UTC,"kao,"
1766825,2018-10-19 04:13:41 UTC,"The issue affects also Cosmic (18.10)
Have
1) bluetooth missing
2) both wifi and bluetooth missing"
1766825,2018-08-25 06:18:25 UTC,It's a dirty workaround. Is it possible for you to check if this issue still happen on Bionic/Cosmic?
1766825,2018-05-17 01:09:40 UTC,"Sorry, I meant

> And I'm not sure if I got the right


nvm_usb_00000302.bin"
1766825,2018-05-23 11:57:17 UTC,"I hid my earlier posts because I reckoned they were noise, tbh. This one less so. :-)"
1766825,2018-05-17 01:01:45 UTC,Would be nice if someone from Qualcomm could have a look at it; just now an update of the linux-firmware Ubuntu package overwrote my fix again.
1766825,2018-10-23 16:49:55 UTC,"Found something that can help. But it needs to be proved on 9370.
9360 has been added to btusb reset table right in kernel module."
1766825,2018-05-16 10:17:12 UTC,"It seems there is no update since 2015 to qca subdir of linux-firmware, so those newer blobs will need to be submitted by Qualcomm, maybe ytkim specifically who did that 3 years ago if he's still at Qualcomm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/qca"
1766825,2018-08-24 16:39:30 UTC,Cyrus Lien (cyruslien)'s solution works.
1766825,2018-10-24 03:51:37 UTC,"kao,"
1766825,2018-12-27 12:31:08 UTC,Forgot to mention: I only experinece this issue for the last few days. Didn't have this issue before and I've been using deep sleep from the beginning when I installed Ubuntu 18.04 myself. The only thing beside Ubuntu package updates that occured some days ago is a BIOS update to 1.6.3 on the XPS 9370.
1766825,2018-10-25 14:28:40 UTC,"Kai-Heng Feng,
Please find the attached with dmesg. However, it's not pure bluetooth missing, I've lost both wifi and bluetooth. But think it has similar root.
Thank you"
1766825,2018-10-25 15:32:33 UTC,"Kao, do you use preinstalled Ubuntu?
Also what you saw is not the same as the original bug, can you file a new bug instead?"
1766825,2018-10-28 07:39:50 UTC,"I am also experiencing that both bluetooth and wifi are missing after setting mem_sleep to deep. My laptop also refuses to actually stay asleep in s2idle, I can see the screen come back on after I close the lid."
1766825,2018-10-28 07:46:42 UTC,"Attached more logs here. File contains dmesg for wifi crash, PCI device list and USB device list. Search for === to find section separators."
1766825,2018-10-28 07:48:36 UTC,"Also, I have to fully power off the laptop before booting again or else the devices won't come back (rebooting alone doesn't work)."
1766825,2018-10-30 13:54:48 UTC,Kai-Heng Feng
1766825,2018-12-27 12:18:36 UTC,"I am on Ubuntu 18.04 with kernel 4.18.0-13-generic and still have the disappearing bluetooth issue. Reboot doesn't help, need to powercycle the XPS 9370."
1766825,2019-02-21 08:40:40 UTC,"iirc, the firmware has been upstreamed and landed to bionic.
Could someone who encounter this issue can have a try on latest kernel and firmware?"
1766825,2019-08-22 05:10:14 UTC,"In light of comment #54, I am setting the linux task of this bug to Incomplete for now, so that anyone who was hit by this bug can comment whether the issue still exist or not after performing a full system update on Bionic."
1766825,2019-11-03 15:08:22 UTC,I'm running eoan and can confirm the issue with Bluetooth still exists on kernel 5.3.0-19-generic
1766825,2020-04-29 06:50:45 UTC,I can confirm that in ubuntu 18.04 the problem is still present
1766825,2018-05-03 10:12:13 UTC,Will escalate this issue to Qualcomm.
1766825,2018-10-24 16:47:34 UTC,Proposed solution in #42 didn't help too.
1766825,2018-05-03 10:06:17 UTC,"Confirmed, the issue was gone with firmware from https://askubuntu.com/a/1029749/95109."
1766825,2018-04-25 09:23:47 UTC,apport information
1766825,2018-05-03 05:08:09 UTC,"A quick workaround is rmmod btusb before suspend and insert btusb after resume.
To do this, you can put a executable script of any name in /lib/systemd/system-sleep/."
1766825,2018-04-25 09:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1766825,2018-04-25 09:23:46 UTC,apport information
1766825,2020-04-29 08:46:02 UTC,"BTW, just tried with this:"
1766825,2018-04-25 09:23:49 UTC,apport information
1766825,2018-04-25 09:23:50 UTC,apport information
1766825,2018-04-25 09:23:51 UTC,apport information
1766825,2018-04-25 09:23:52 UTC,apport information
1766825,2018-04-25 09:23:53 UTC,apport information
1766825,2018-04-25 09:23:54 UTC,apport information
1766825,2018-04-25 09:23:55 UTC,apport information
1766825,2018-04-25 09:23:57 UTC,apport information
1766825,2018-05-03 08:35:44 UTC,Please take a look at this answer at AskUbuntu: https://askubuntu.com/a/1029749/95109
1766825,2018-04-25 09:23:59 UTC,apport information
1766825,2018-04-25 09:24:01 UTC,apport information
1766825,2018-04-25 09:24:02 UTC,apport information
1766825,2018-04-25 09:24:04 UTC,apport information
1766825,2018-04-25 18:26:50 UTC,Also experiencing this issue. Same symptoms.
1766825,2018-04-25 19:00:14 UTC,Thanks for reporting. I've reached out to have this LP bug looked at.
1766825,2018-04-26 07:38:41 UTC,"The kernel is 4.4.0-121-generic(#4), I though it was solved on kernel version >= 4.4.0-93.116."
1766825,2018-04-26 07:40:47 UTC,"@Felix,"
1766825,2018-04-26 07:43:54 UTC,"@Felix,"
1766825,2018-04-26 08:02:56 UTC,@Cyrus
1766825,2018-04-26 09:07:54 UTC,Update: It's also happening with kernel 4.4.0-93.116
1766825,2018-05-03 04:08:19 UTC,I can reproduce it only on AC mode. Still can reproduce it after disable tlp.
1766825,2018-04-25 09:24:00 UTC,apport information
1766829,2020-03-22 16:01:05 UTC,Your email about [Bug 1766829] Email rejected to <email address hidden> was rejected. It appears to be spam.
1766829,2020-03-22 15:50:43 UTC,"Your email about [Bug 1766829] Re: Numlock on keyboard LED is not red if numlock is on
 at boot to <email address hidden> was rejected. It appears to be spam."
1766829,2019-07-29 22:19:30 UTC,It is an annoying issue. I have to type twice CapsLock  in order the Indicator work (more easy for me than NumLock).
1766831,2018-05-22 03:11:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569913"
1766831,2018-06-07 09:26:26 UTC,"Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/569913"
1766837,2018-04-25 10:15:47 UTC,"Please can you describe the issue, I'm not sure what the image is trying the show me."
1766837,2018-04-25 12:14:16 UTC,"The multiload indicator is added to the top panel.
The indicator is set up to show (from left to right):"
1766837,2019-10-11 19:29:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766837,2019-10-11 19:34:37 UTC,"I have the same issue, however, looking closely at the color preferences for the network monitor, there is one called ""gridlines"" which corresponds to the horizontal lines in the applet display.  Presumably the authors wanted a way to show changes in the scaling (vertical units) and decided on adding these gridlines.  So, one way to resolve most of the visual annoyance would be the option to make the lines have an alpha channel, i.e. the user can opt to make them transparent."
1766837,2019-10-11 19:43:35 UTC,"Also, for now I set the gridlines to be the same color as the background, which gets rid of some of the visual clutter."
1766840,2018-04-25 22:00:04 UTC,This change was made by a bot.
1766841,2020-11-16 18:45:28 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1766841,2018-05-11 09:47:39 UTC,"Rechecked in my site, the new installer (20180430) had solved the 1st problem, but it leads to another problem: When uninstall QEMU, the loaders.cache file cannot be deleted automatically."
1766841,2019-10-06 01:31:41 UTC,"I discovered that the following directory is not installed when the ""Desktop icons"" component is unchecked during installation:"
1766841,2018-04-30 13:10:11 UTC,"On Wed, Apr 25, 2018 at 10:23:07AM -0000, Justin wrote:

> Public bug reported:
>
> QEMU Version: 2.12 (Binary installer qemu-w64-setup-20180424.exe  from Stefan Weil's website so I am not sure I should report it to Weil by email or by this bug report system.)
> Host System: Windows 7 64bit
> Guest System: 9front 6350 (Codename“CONTENTS, MAINTAINED, STABLE”, Release 2018/02/02)
>
> QEMU Command:
> qemu-system-x86_64 -usb -device usb-mouse -hda plan9.qcow2.img -cdrom 9front-6350.iso -boot d
>
> QEMU warning:
> (qemu-system-x86_64.exe:8844): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file 'D:\qemu\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache': No such file or directory
>
> This likely means that your installation is broken.
> Try running the command
>   gdk-pixbuf-query-loaders > D:\qemu\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache
> to make things work again for the time being.
>
> (qemu-system-x86_64.exe:8844): Gtk-WARNING **: Could not find the icon 'window-minimize-symbolic-ltr'. The 'hicolor' theme was not found either, perhaps you need to install it.
> You can get a copy from:
>         http://icon-theme.freedesktop.org/releases
>
> ** Affects: qemu
>      Importance: Undecided
>          Status: New
>
>
> ** Tags: installation windows
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1766841
"
1766841,2018-04-30 15:18:10 UTC,Both messages are warnings – QEMU will work nevertheless.
1766847,2018-10-07 17:42:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766851,2019-03-27 14:17:27 UTC,"Related to #1820755 - although the new linux-base is now available in xenial-updates, the kernel packages do not version their depends to demand the new version, so apt-get will not necessarily install it (which causes base-installer  to fail, since debootstrap will not have upgraded from xenial-updates prior to installing base-installer/kernel/image, and will not upgrade when the linux-image-generic Depends are already satisfied)"
1766851,2019-03-26 08:24:22 UTC,"Same as Jason Pereira, I've this issue with fresh 16.04 intall, from network."
1766851,2019-03-26 20:31:00 UTC,"I'm also seeing this, when attempting to provision a vagrant box with 16.04. I have, in my Vagrantfile:"
1766851,2019-03-18 18:36:30 UTC,I am still having this issue with a fresh install of 16.04. Can anyone give an update to this bug
1766851,2018-04-25 21:04:50 UTC,This should fix it:
1766851,2018-04-25 11:44:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766851,2018-04-25 23:12:40 UTC,Same problem with Kernel 4.14.36: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.36/
1766856,2019-07-19 19:13:18 UTC,This bug is believed to be fixed.
1766857,2018-06-19 15:13:39 UTC,"At this point, we should probably have two separate bugs to address each problem.  Can we keep this bug for the second issue and create a new bug for the first issue?"
1766857,2018-07-06 18:46:59 UTC,Did you notice any other issues that occur when testing the test kernel posted in comment #12.  The second issue posted in the bug is resolved by changing the definition of KVP_CONFIG_LOC in hv_kvp_daemon.c:
1766857,2018-07-02 12:16:47 UTC,I have opened a different bug for the first issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640
1766857,2018-10-19 21:24:03 UTC,"Joe, for the 2nd issue initially reported here, about ""After the KVP daemon is being started the following messages appear"".
We've noticed a regression for this in 18.10 - daily's and even GA."
1766857,2020-04-03 02:07:09 UTC,Just created a new VM and wondered why enhanced mode logins in hyper-V weren't working and encountered this.
1766857,2018-11-02 15:32:13 UTC,Issue with 'Invalid kvp dependency scripts path /usr/libexec/hypervkvpd' remains in latest kernel-image bionic 4.15.0-38.41.
1766857,2018-11-16 15:36:18 UTC,"Hmm, I wonder if the linux-azure kernel has and extra patch(s) that the generic kernel does not.  I'll do some comparisons."
1766857,2020-04-03 02:33:29 UTC,Can confirm the Azure kernel also fixes enhanced sessions when combined with appropriate windows side metadata shenanigans.
1766857,2018-06-13 14:25:56 UTC,"Regarding comment #11:
I have tested both kernels provided with the following results:"
1766857,2018-10-23 13:58:29 UTC,"Hi Chris, I added a Cosmic 18.10 bug task.  Does this bug only happen in Cosmic, or is it still happening in Bionic?"
1766857,2018-06-08 17:06:35 UTC,"I built a test kernel which can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1766857/"
1766857,2018-04-25 22:59:31 UTC,"I tested back to the daily build from 2nd of March and I can confirm the second issue (regarding the binaries path), but not the first one (regarding the daemon crash). On the build from the 2nd of March the linux-tools and linux-cloud-tools version is 4.15.0-10.11"
1766857,2018-06-07 12:02:50 UTC,"I have tested Bionic with kernel 4.15.0-22-generic, linux-cloud-tools-4.15.0-22.24 and linux-tools-4.15.0-22.24 and both issues still occur."
1766857,2018-06-06 18:56:00 UTC,"Commit 7fa32e5ec28b was actually mentioned in bug 1664663, an I don't think it factors into this bug."
1766857,2018-06-06 18:54:11 UTC,"Commit 7fa32e5ec28b was mentioned in the descriptions.  However, that commit has been in mainlien since 4.15-rc3, so it's always been in 18.04."
1766857,2018-06-06 17:40:29 UTC,"In my own VMs, this does not affect linux-azure, it only affects the generic 4.15 kernel."
1766857,2018-06-05 08:04:09 UTC,"I confirm the second, the daemon hv_kvp_daemon not find the files:
/usr/libexec/hypervkvpd/hv_get_dns_info
/usr/libexec/hypervkvpd/hv_get_dhcp_info
With linux-cloud-tools version 4.15.0-22.24"
1766857,2018-06-05 07:54:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766857,2018-04-25 21:23:38 UTC,Did this bug just start happening with the 4.15.0-20 kernel?  Were there prior 18.04 kernels that did not exhibit this bug?
1766857,2018-06-08 14:17:26 UTC,"Since they might be related, lets focus on the second issue first, which is cause by the missing files."
1766857,2018-04-25 12:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1766859,2019-05-24 11:50:22 UTC,"This isn't specific to lubuntu.
It happens on ubuntu-mate 18.04 as well.
Changing VTs with Ctrl+Alt+F2 etc bypasses it."
1766859,2019-07-14 02:24:35 UTC,"This is, if anything, a bug with the configuration of the virtual machine."
1766859,2019-11-12 17:14:54 UTC,Changing the graphic controller in display to VMSVGA fixed it for me.
1766859,2020-08-14 07:25:45 UTC,It still happens with the latest virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 on Ubuntu 20.04.1 and kernel 5.4.
1766859,2020-04-20 07:44:24 UTC,"I remember some fixes before release, can you please try again with an updated vbox?"
1766859,2020-06-20 04:17:20 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1766859,2018-12-19 10:31:23 UTC,"It affects me as well, with the host being openSUSE Leap 15.0 with Intel graphics. (Guest is the aforementioned Lubuntu 18.04.) The workaround to switch TTYs (via right Ctrl+F1/F7) works."
1766859,2019-12-22 09:43:18 UTC,"This is probably an issue in VirtualBox; filing there instead of under ""lubuntu-meta""."
1766859,2018-12-13 22:09:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766859,2018-04-25 13:24:34 UTC,"In 25 april version, changing to tty and back (Ctrl+Alt F1 and the back with Ctr+Alt F7) display correctly."
1766859,2018-12-13 21:54:14 UTC,"Press Esc in the language selection menu and select nomodeset in the ""Other Options"" menu. This somehow works for me."
1766859,2018-08-11 19:51:21 UTC,"mberna's solution here is what worked for me on an Ubuntu 18.04 host with whatever is the current Lubuntu 18.04 desktop amd64 ISO:
https://superuser.com/questions/1295202/garbled-display-when-running-lubuntu-17-10-as-guest-os"
1766859,2018-04-26 20:18:06 UTC,"It's weird.  I can no longer duplicate the screen corruption on my Lubuntu 18.04 system now.  No matter what settings I use, it always works fine."
1766859,2018-04-26 19:13:19 UTC,My main Windows 10 computer on VirtualBox 5.1.34 works fine.
1766859,2018-04-26 12:22:24 UTC,"I had that same problem in the past and that solved it, and now 3d acceleration was disabled.
However, when te system is installed the problem doesn't occour (after installing Bionic and I'm using daily a 17.10).
It also doesn't happen when I use an already existed VM, and boot from it . But with a knew one it happens, ita happened with Bionica Daily 25.1 too."
1766859,2018-04-26 01:47:58 UTC,"I installed Lubuntu Bionic Desktop 20180425 under VirtualBox on a Windows 10 host.  I tried both with and without 3D acceleration enabled.  For me, I didn't get any screen corruption."
1766859,2018-04-25 13:05:14 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1766859,2018-12-13 21:58:39 UTC,"And yes, just like what Jb said, sometimes it just works without any issue. The issue is very hard to reproduce once you solved it, no matter what settings you use. Now the ISO boots fine with 64 MB of video memory, nested paging simulation and 3D acceleration."
1766863,2019-09-12 13:38:53 UTC,"You can't use append, but you can override this variable - even to an empty value and _append to it later in template-override."
1766865,2020-04-24 06:35:53 UTC,successfully tested with 20.04 / subiquity on LPAR with DASD and zFCP disks
1766865,2020-04-23 20:08:47 UTC,new installer is out.
1766865,2020-03-25 15:13:26 UTC,"I can confirm now that this works now on LPAR with DASD as well as with zFCP/SCSI disk storage using subiquity 20.03.
(I had to use edge just to overcome a probing block device issue and had to juggle around an issue with VLAN networking, but the zkey usage is independent on that.)"
1766865,2019-04-23 09:19:42 UTC,"------- Comment From <email address hidden> 2019-04-23 05:16 EDT-------
IBM bugzilla status -> closed, Fix Released with Disco"
1766865,2018-09-28 09:09:37 UTC,"------- Comment From <email address hidden> 2018-09-28 05:02 EDT-------
Moved this installer item from 18.10 -> 19.04..."
1766865,2018-09-05 07:59:45 UTC,"------- Comment From <email address hidden> 2018-09-05 03:53 EDT-------
Addl. information
You cannot encrypt the boot partition. -- After all, there must be code to open an encrypted partition
You can encrypt the root partition
in order to do so the code in boot partition must open the boot partition
i.e., the initrd or initramfs contains code to issue the cryptsetup open/luksOpen commands for the root partition before the chroot command
with LUKS/LUKS2 you must provide a pass phrase - on PCs that is asked for interactively  (possibly derived from the password) -- somehow Canonical does this with their Ubuntu distributions today
with protected keys crypto (PAES) - you need not protect a pass phrase. With dm-crypt plain mode you can use a secure key stored somewhere in the initrd/initramfs or with LUKS2 you can simply store the pass phrase in a file in the initrd/initramfs because the security of the disk key is protected by the HSM (CryptoExpress card)  and  does not depend on being wrapped by a secret pass phrase.
Note, before a system tries to use PAES it should verify that a CCA coprocessor (CEXnC adapter) is available."
1766865,2018-07-09 11:09:27 UTC,"------- Comment From <email address hidden> 2018-07-09 07:08 EDT-------
For installing the CCA lib, please see here:
https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linux.z.wskc.doc/wskc_c_install.html"
1766865,2018-07-09 10:59:29 UTC,"------- Comment From <email address hidden> 2018-07-09 06:50 EDT-------
You don't need a TKE.
You need to set up the (AES) masterkey on your card(s), thats all.
This can be done one the command line with an application which
is part of the CCA library. I'll add Ingo to cc and he may write down some more details or attach a paper which describes all this.
@Ingo, can you please copy-and-paste some instructions about how to install the CCA lib and set up master keys here? Thanks"
1766865,2018-06-13 08:06:10 UTC,"some additional thoughts:
- I think the latest s390-tool ships with zkey, but needs packaging (other ticket)
- CPACF and CryptoExpress5 (pairs) are availabel on our z13
- but we don't have a TKE, the utilities might be sufficient for testing, anyway end-2-end testing would req. TKE
- considerable work at d-i and partman needed (add. udebs)
- z12 is supported by Ubuntu, but not for pervasive encryption - that would need to be handled in installer, too"
1766865,2018-06-13 07:25:06 UTC,"The following changes will be needed:
1) modify s390-tools to ship zkey utilities in the udeb, for d-i
2) probably some modifications to partman-crypto to allow using zkey generated keys
3) detection when these keys are available
4) ensure consistent defaults are used, at same or greater cryptographic stength"
1766865,2018-09-04 18:52:55 UTC,This bug was fixed in the package s390-tools - 2.6.0-0ubuntu4
1766875,2018-05-18 07:39:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766875,2018-11-28 12:06:11 UTC,Got this recently in kubuntu 18.04.1 ff 63.0.3
1766886,2018-04-25 20:06:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766886,2018-04-25 19:57:00 UTC,poss duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
1766890,2018-06-12 08:52:22 UTC,Still failing with current -proposed enabled. Let's hope it solves itself once we fixed all other instances of triggers.
1766890,2018-06-12 09:26:49 UTC,"@juliank, I'll assign this to you for tracking purposes if you don't mind (the rls-bb-tracking page)"
1766890,2018-05-24 10:06:28 UTC,"My investigation has shown that upgrading libc6 first produces a vastly different installation ordering. Also, turning off immediate configuration of essential packages in apt makes it work; but triggers bug 1771791 in systemd much more easily than now."
1766890,2018-07-18 23:13:37 UTC,I tested this today by first restoring the clone file found in the tarball in comment #20 then  enabling and installing all the packages in -proposed for Ubuntu 16.04. I then modified DistUpgradeController.py in the dist-upgrader tarball so that -proposed would*n't* be disabled during the upgrade. With all of that I still encountered the following error:
1766890,2018-05-02 16:09:36 UTC,It's worth noting that when the apt-clone file is restored that the packages from PPAs are not installed (surely a bug in apt-clone) and so it is not related to the PPA packages rather some combination of the packages from the official archive.
1766890,2018-05-02 06:26:18 UTC,I'll keep identifying root cause for this issue.
1766890,2018-05-02 06:24:16 UTC,"I could reproduce this issue with oem image (somerville 20170614-0). With exactly the same error ""dpkg: cycle found while processing triggers:"""
1766890,2018-05-11 13:42:10 UTC,"I spent a bit of time looking into this one, and I really have no idea. I followed Brian's lead and restored the apt-clone file in comment #20, which makes the bug reproduce."
1766890,2018-07-18 23:14:09 UTC,Here's some more information from the failure:
1766890,2018-05-01 20:08:39 UTC,I performed another upgrade with the apt-clone file from this bug and editing sources.list from xenial to bionic but this time I first installed the version of libc6.
1766890,2018-08-07 22:00:10 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.7
1766890,2018-08-09 13:04:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766890,2018-08-09 16:00:29 UTC,"Hello Taihsiang, or anyone else affected,"
1766890,2018-08-09 17:50:19 UTC,I tested an upgrade today from Ubuntu 16.04 to Ubuntu 18.04 using the dist-upgrader from -proposed but not using the clone attached in this bug report and the upgrade did complete successfully with libc6 being upgraded first.
1766890,2018-08-09 21:56:52 UTC,"I also performed an upgrade from Ubuntu 16.04, with the apt-clone file restored, to Ubuntu 18.04 using the dist-upgrader from -proposed.. The upgrade proceeded without error and libc6 was installed first."
1766890,2018-08-09 22:31:23 UTC,"Hello Taihsiang, or anyone else affected,"
1766890,2018-08-13 15:15:49 UTC,"I also did some more verification with the graphical frontend and the apt-clone file restored, and it worked perfectly well, with libc6 upgraded first. Progress reporting was a bit weird as it went to 100% for the libc stuff, and then down again, but it could be worse."
1766890,2018-08-13 16:08:52 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.24
1766890,2018-08-13 16:08:57 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1766890,2018-07-24 16:32:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766890,2018-05-01 19:20:32 UTC,I was also able to recreate this by editing sources.list from xenial to bionic after restoring the apt-clone file.
1766890,2018-04-26 06:34:50 UTC,Thanks for the logs
1766890,2018-04-26 17:15:49 UTC,I also think we have enough information to work on this and no further logs are necessary.
1766890,2018-04-26 01:25:00 UTC,"Hi jibel, please refer to the attachment of comment #4. It is the tarball of /var/log/dist-upgrade"
1766890,2018-04-26 02:23:57 UTC,"@Taihsiang,"
1766890,2018-04-26 22:49:31 UTC,"Regarding Adam's comment and bamfdaemon that was fixed in Ubuntu 16.04, see bug 1589097."
1766890,2018-04-26 07:15:08 UTC,This system Dell XPS 13 9360 (CID 201606-22338) could install stock ubuntu 18.04 daily build 49f7bfba24b829f39f8c6d64ee72dfb2 *bionic-desktop-amd64.iso
1766890,2018-04-26 13:01:29 UTC,I reproduced the issue with the clone attached.
1766890,2018-04-26 13:44:59 UTC,"I've reproduced this with an XPS13 9370, same errors and now X is completely broken"
1766890,2018-04-26 13:59:00 UTC,"After the initial reboot, x seems to keep crashing, but if you can get to a vt and run apt-get install -f, it seems to at least allow the system to boot"
1766890,2018-04-26 14:45:19 UTC,"This trigger loop is almost certainly because bamfdaemon's trigger wasn't fixed to be interest-noawait until yakkety, and nothing forces it to deconfigure or upgrade early (ie: with a Breaks like we used in dpkg between trusty and xenial)."
1766890,2018-04-26 15:04:10 UTC,"FWIW, this error (my bug was marked a duplicate) completely broke my Xenial - Bionic upgrade, leaving me with a nearly unbeatable system.  I had to boot into Rescue Mode and do a lot of ctrl-C ing to get around this, and once I thought it had finally installed all the bionic packages, I rebooted into the OS proper, and STILL found it hadn't actually upgraded so I had to run 'apt-get -f install' again to finish the other 2400+ package updates."
1766890,2018-04-26 15:04:58 UTC,"Grr... autocorrect on OSX while I wait for Ubuntu to work again (finish upgrading).  That should have said ""leaving me with a nearly unbootable system."""
1766890,2018-04-26 15:16:36 UTC,"@Jeff, did you use apt instead of the dist-upgrader as well? Was your xenial uptodate before the upgrade?"
1766890,2018-04-26 16:27:19 UTC,"@seb, per discussion via IRC, here are my logs from /var/log/dist-upgrade (upgrade started last night and finally wrapped up this morning after a lot of coffee and swearing)."
1766890,2018-04-26 16:28:34 UTC,"FWIW, it's entirely possible I had other issues that just also included this one, or just exposed this one where I may not have seen it otherwise.  This just happened to be the only one that Apport was able to create and submit."
1766890,2018-04-26 16:30:04 UTC,Reproduced similar issue on different platform and SKU (will attach /var/log/dist-upgrade in this bug report):
1766890,2018-04-26 16:34:02 UTC,201606-22355.dist-upgrade.tar.gz  201610-25144.dist-upgrade.tar.gz are attachments for comment#18
1766890,2018-04-26 16:46:38 UTC,Dell-XPS-13-9350.tar is a tarball log containing 3 different SKU log of 9350. All of them could reproduce this issue.
1766890,2018-04-26 17:04:15 UTC,I believe the issue is with the libglib2.0-0 triggers which were changed to interest-noawait in bionic but probably also need fixing in xenial.
1766890,2018-04-25 14:52:32 UTC,Thanks for your report.
1766900,2018-05-24 18:08:52 UTC,"I would propose the use of the namespace in regards to there intended use, that is to create a structured convention with dictates the category in which the workflow belongs. A category could have a hierarchy of parent namespaces with children:"
1766900,2019-07-29 14:36:39 UTC,I don't think this is worth doing anymore with the reduced Mistral usage.
1766902,2019-07-29 14:36:06 UTC,I don't think this is worth doing anymore.
1766910,2018-04-25 15:50:29 UTC,"127.0.0.1:6600 was already taken, perhaps by mpd.socket (that is, systemd itself)? I have a feeling there's something broken in the way dh-systemd is setting up the postinst in such cases, but I haven't been able to nail it down, and while I've seen this before a number of times I don't think it occurs deterministically..."
1766916,2018-04-25 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1766919,2018-04-26 11:49:01 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/564333
Reason: Going with https://review.openstack.org/#/c/530777/ instead."
1766919,2019-06-19 20:45:19 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/564343
Reason: Drop this until mox usage is removed (looks like it's just the nova-network, neutronv2 and old block_device tests that are still using mox, but cleaning up the latter two are complicated - I know Takashi has patches for it, but it's tough to review those)."
1766919,2018-06-08 12:25:30 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1766919,2018-04-26 20:42:16 UTC,"Reviewed:  https://review.openstack.org/530777
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=35b304661d17e1b64460101ae30273a4c5672a14
Submitter: Zuul
Branch:    master"
1766919,2018-04-26 11:50:45 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/564334
Reason: Let's go with https://review.openstack.org/#/c/530777/ instead."
1766919,2018-04-26 11:41:49 UTC,"mox3 is also affected, as seen in the test results for this nova change:"
1766919,2018-04-25 21:02:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/564343"
1766919,2018-04-25 20:14:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564334"
1766919,2018-04-25 20:14:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564333"
1766919,2018-04-25 20:12:28 UTC,This method is also using inspect.getargspec but we don't see warnings for it in unit test runs because apparently we don't have any unit tests for that method:
1766919,2018-04-25 19:08:09 UTC,Looks like you can do something like this:
1766922,2018-04-26 17:09:43 UTC,Looks to me like some memory allocation issue in vrouter.
1766931,2018-05-11 14:08:31 UTC,"@Orson, do we want to mark this as a Wishlist to possibly support the shorthand syntax in the future, or is this a Won't Fix?"
1766931,2018-05-11 17:54:38 UTC,"I think a request for a dialog to define model parameters is fine, though it is not like it is completely broken now. I use parameters in the way described in my previous answer and they work as expected."
1766931,2018-04-26 08:23:37 UTC,"The value field is used directly only for passive components which do not have an explicit Spice model assigned. Once there are Spice_* fields defined they are used for simulation, so it means you can add the desired parameters to Spice_Model field."
1766935,2019-06-23 19:06:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766938,2018-05-29 12:00:02 UTC,"Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug."
1766938,2018-05-03 08:49:05 UTC,"This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'."
1766938,2018-04-27 01:55:41 UTC,"Yes it's possible one of your icons uses 16-bit colour, and explains why we don't see other/many reports of this crash."
1766938,2018-04-26 16:16:50 UTC,"optimized out, alas.  But:"
1766938,2018-04-26 05:00:49 UTC,"I would be curious to see the value of 'depth' in:
standard_pict_format_for_depth (int depth)"
1766938,2018-04-26 04:53:51 UTC,That's annoying. We should be able to retrace any crash from any package versions. Seems like we've made reporting crashes more difficult than it should be.
1766938,2018-04-26 04:30:20 UTC,"Too late!  The world has moved on, and I can no longer upload this bug:"
1766938,2018-04-26 02:48:22 UTC,If you're coming from a 17.10 or older system then you will need to apply the workaround from bug 994921 first.
1766938,2018-04-26 02:38:12 UTC,"Sure, sorry for uploading it wrong in the first place.
The new bug is ... uh... it didn't create one, it just went into the ether, in a cloud of dots."
1766938,2018-04-26 02:18:13 UTC,"Hi Dan,"
1766938,2018-04-25 22:13:38 UTC,"Doesn't sound like a release blocker offhand, but sheesh.  Boot loops are no fun."
1766938,2018-04-25 22:09:27 UTC,"Ah, that assert is in mutter."
1766938,2018-04-25 21:28:44 UTC,apport-retrace -g _usr_bin_gnome-shell.1000.crash
1766938,2017-08-03 17:28:59 UTC,Still crashes
1766938,2017-07-25 18:58:48 UTC,"This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'."
1766938,2016-07-19 16:16:09 UTC,Still crashes on Fedora 24 with the same error message and traceback.
1766938,2016-07-19 15:11:16 UTC,"Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1766938,2015-07-03 16:05:10 UTC,1. Install xterm
1766938,2020-11-16 08:50:19 UTC,I can't find any other reports of this crash. Is it still happening?
1766938,2020-11-16 16:35:30 UTC,"I no longer have access to the system in question, and haven't seen it anywhere else, may as well close as abandoned."
1766944,2018-04-25 21:17:47 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1766944,2018-04-25 18:00:06 UTC,This change was made by a bot.
1766946,2018-04-25 20:35:50 UTC,"So, I think Zane agreed to the idea of adding attributes, but not in this form. I don't think exposing a blob is a good thing. What we want (if we do?) is a structured element with namespace."
1766946,2018-04-25 22:14:24 UTC,Thanks for the feedback Thomas.
1766950,2019-05-07 12:04:09 UTC,"I hope this will help you to see the problem.  Especially the second video, where I just keep alternating highlighting two footprints and you can see that sometimes the cursor in EEschema goes right to the center of the symbol and sometimes off to the side."
1766950,2018-04-30 09:47:25 UTC,Confirmed the minor bug that the click causing focus change from eeschema to pcbnew only highlight the footprint but doesn't point to schematic symbol.
1766950,2018-05-01 07:31:46 UTC,Related is https://lists.launchpad.net/kicad-developers/msg32926.html
1766950,2018-11-29 04:13:12 UTC,"I'm having trouble reproducing any of these issues on master as of today, although I am on Linux and can't test on Windows at the moment.  Is anyone able to confirm that these problems still happen?  Maybe it's a Windows-only issue?"
1766950,2018-12-03 12:59:29 UTC,I cannot reproduce this on windows 10 pro with version (5.0.1-33-g76adf7dbe) so it may me the fact that the reporter is using 5.0.0-rc2 or there is a specific pattern that causes the issue.  I tested the cross probing in both directions using a schematic with a simple hierarchy.
1766950,2019-05-05 14:18:25 UTC,Still haven't seen this; please re-open issue with reproduction steps if anyone finds them.
1766950,2019-05-23 17:04:23 UTC,"After watching Art's video, it looks like it only happens on the US style resistors.  It also appears that the centering of the US style resistor is consistent.  How does the schematic editor determine how to center the symbol?  It seems to me that the problem lies there albeit a fairly minor problem."
1766950,2019-07-15 14:18:06 UTC,Seems to be resolved now
1766950,2019-07-15 17:54:01 UTC,"Thanks for circling back, @Art!"
1766956,2018-05-04 18:59:35 UTC,"There have been pulse audio updates since I reported this, and after today's updates (and deleting ~/.config/pulse), the two computers that had the problems now correctly output sound from the speakers."
1766962,2018-04-25 20:18:45 UTC,"Sorry, this is solved, I just had to set"
1766974,2018-10-22 06:58:35 UTC,apport information
1766974,2018-10-22 06:58:33 UTC,apport information
1766974,2018-10-22 06:58:37 UTC,apport information
1766974,2018-10-22 06:58:39 UTC,apport information
1766974,2020-09-04 11:14:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766974,2018-12-18 07:50:44 UTC,"I suspect your recent request of me to run  apport-collect 1766974 was an error and should have been directed at Michael Odumosu (michael5757) instead.
In any case, I have since the bug(s) freshly installed 18.04 LTS and have no bugs at all now.  I am unable to replicate."
1766974,2018-12-18 07:51:41 UTC,See my recent comment against the bug.
1766974,2018-10-22 06:58:32 UTC,apport information
1766974,2018-12-17 23:04:50 UTC,I got the same error too on linux 16.04.5 how do I send you the needed info
1766974,2018-10-22 06:58:31 UTC,apport information
1766974,2018-10-22 06:58:33 UTC,apport information
1766974,2018-10-22 06:58:30 UTC,apport information
1766974,2018-05-28 11:28:24 UTC,I confirm this bug.
1766974,2018-09-12 19:56:03 UTC,"This recently happened to me with linux-image-4.15.0-34-generic
see bug #1792213"
1766974,2018-10-22 06:15:40 UTC,"Dave,"
1766974,2018-10-22 06:58:24 UTC,apport information
1766974,2018-09-09 13:52:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766974,2018-10-22 06:58:28 UTC,apport information
1766974,2018-10-22 06:58:30 UTC,apport information
1766974,2018-10-22 06:58:29 UTC,apport information
1766974,2018-10-22 06:58:26 UTC,apport information
1766976,2020-09-22 10:27:08 UTC,"Just an addendum to my comment above. I would describe this as a serious problem with a default install of XUbuntu. I spent two days trying to work out why my Qt based app was not displaying certain unicode characters (eg cheese wedge). It was just showing the white rectangle. Other apps, eg Geany, gnome-console, were showing the cheese just fine; so I thought I had a bug. I didn't know that Qt apps could not display colour emojis. If they cannot display colour unicode characters, then they should display the grey equivalent instead of just displaying a white rectangle. As I say, I spent two days trying to understand why my app was not displaying certain characters when I knew that the font it was using did support that character."
1766976,2019-07-12 15:14:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766976,2019-11-01 10:09:09 UTC,"Has the status of color emoji in Qt changed? I've asked around and seen some rumblings about it, but when testing in 19.10 it looks like color emoji is still unsupported."
1766976,2019-11-01 11:04:11 UTC,I don't think Qt has full support for color emoji yet. Most Ubuntu users are using some GTK apps like a web browser (especially Xubuntu!) so installing a color emoji font is useful.
1766976,2019-11-14 21:34:52 UTC,"reverse-depends fonts-noto-color-emoji
Reverse-Recommends
==================
* dino-im
* fonts-noto
* gajim
* gnome-characters
* kubuntu-desktop [amd64 arm64 armhf i386 ppc64el]
* kubuntu-full [amd64 arm64 armhf i386 ppc64el]
* python3-sqt [amd64 arm64 ppc64el]
* ubuntu-budgie-desktop [amd64 arm64 armhf i386 ppc64el]
* ubuntu-desktop [amd64 arm64 armhf i386 ppc64el]
* ubuntu-desktop-minimal [amd64 arm64 armhf i386 ppc64el]
* ubuntu-mate-core
* ubuntu-mate-desktop
* ubuntu-unity-desktop [amd64 arm64 armhf i386 ppc64el]
* ubuntukylin-desktop
* ubuntustudio-desktop"
1766976,2020-09-21 11:27:05 UTC,"In a default fresh install of XUbuntu 20.04, Qt based applications, eg Featherpad and Qt-Creator, will not display certain unicode characers, eg, U+1F9C0 CHEESE WEDGE 🧀 (a white rectangle is shown instead). Non Qt apps, eg geany or gnome-terminal, show the cheese successfully. If Noto fonts are manually uninstalled, then the problem is fixed; Featherpad does display the cheese correctly. Conjecture: the Noto fonts were providing a colour version of the cheese wedge; the Qt apps could not display that but can display grey versions"
1766978,2020-04-20 21:35:31 UTC,I have this problem and the workaround (unmount and mount the Windows boot partition several times) didn't work. I've tried Ubuntu 18.04 LTS and Ubuntu 20.04 LTS Beta.
1766978,2018-05-01 20:24:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1766982,2019-07-31 19:06:46 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Garry and Josh!"
1766982,2019-03-11 01:13:07 UTC,"This worked as described for me.  Before fix I see 'null' in the pull list csv extract when there is no author, after fix I see just a blank string when there is no author."
1766982,2018-05-19 00:17:01 UTC,Patch submitted to Evergreen working repository - http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=695fb46f695aef3491d3f8fb6a29fea476b78466
1766982,2018-05-11 02:10:34 UTC,Thanks Mike for your comment. I have attached a proposed solution that checks for both null and undefined values.  It can also be found at https://github.com/gcollum/Evergreen/tree/LP1766982/
1766982,2018-05-06 20:31:26 UTC,"There's a function in grid.js that prepares text to be downloaded as CSV checking for quotes, commas, etc.  Would a line that searches case-insensitively for fields that only contain the word 'null' and replaces the string with '' be an acceptable solution?  Would there ever be case where either data is legitimately the word 'null', or that null values would be needed in any CSV file?"
1766982,2018-04-26 12:57:59 UTC,We are seeing this in PaILS. It is a problem because several of our libraries use the CSV output from Item Status to produce pocket labels.
1766982,2018-05-06 21:39:39 UTC,"Well, there's no way to represent null in CSV, so an empty string is the best we can do. The property should be tested for null-ness, though, as there's no reason we couldn't have a legitimate string containing the word ""null"".  The function you mention is the place for the check, and one for ""undefined"" might not hurt, too."
1766983,2018-05-12 16:18:13 UTC,This is a regression bug i.e. gpxviewer used to work with the same Ubuntu version (16.04). So it's presumably been caused by a Ubuntu software update. So it should be an easy bug to fix.
1767002,2019-07-19 19:12:37 UTC,I'm closing this bug as Fixed Released.
1767014,2018-04-30 08:07:05 UTC,Approximate translation of the error message:
1767014,2018-04-30 08:10:19 UTC,The error happened at package configuration time:
1767015,2018-04-26 23:41:26 UTC,"Additional test, using the standalone iperf3 tool, run network performance test between the node and IPERF server. To imitate the server certification test, run 4 iterations each at 900 seconds time interval of iperf3 testing at the node side. The following command as shown below:"
1767015,2018-05-02 13:49:04 UTC,"Jeff,
There's one big branch awaiting landing. There need to be some UX-related branch that I feel requires a week of work + documentation (1-2 days, tops).
The thing is I need to devote some time to other projects so cannot do any promises. But by saying it can solve some problems it surely bumps the priority."
1767015,2018-05-02 13:17:05 UTC,"I've been playing with remote... I think it may well solve the
problem, but it's not mature yet."
1767015,2018-05-02 12:47:29 UTC,"Maciej, yes, that sounds like it would fix the problem, so I've assigned this bug to you. Feel free to ping me if you want me to test this, since I've reproduced this specific bug myself."
1767015,2018-05-02 10:24:15 UTC,"This problem is one of many that checkbox-remote aims to solve.
In checkbox-remote when the controller is disconnected from SUT, it tries to reconnect and resume testing."
1767015,2018-05-01 14:08:25 UTC,"Per e-mail on 30 April, 2018, the problem seems to have been caused by an SSH session disconnecting during the test (which is common) combined with NOT using the ""screen"" utility. Under these circumstances, the test suite terminated the test run, causing the failure. The solution is to use ""screen"" or run the tests at the console. I'm going to leave this bug report open, since better robustness to this condition is desirable."
1767015,2018-04-26 01:59:42 UTC,syslog added
1767015,2018-04-27 13:20:09 UTC,"First, could you please clarify the following statements, which seem contradictory: ""All NIC cards either 1G or 10G Ethernet/SFP are failing Multi-NIC Iperf3 stress testing"" and ""this error always happened during Test No. 2 – when testing the 2nd port connection of any NIC cards."" The first clearly states a failure of all interfaces, but the second suggests that the first device tested passes while the second and subsequent tests fail."
1767015,2019-09-05 11:45:20 UTC,"Checkbox-Remote has been used in production for quite some time now and is stable and ready to be used as a remedy to this bug.
https://checkbox.readthedocs.io/en/latest/remote.html"
1767015,2018-04-26 01:57:21 UTC,syslog and dmesg added
1767015,2018-04-29 13:51:03 UTC,"This case is not the same as described on bug #1766330. All NIC devices installed on SUT have failed the Multi-NIC iperf3 stress testing on 18.04 beta release. The test stopped and exited with messages “packet_write_wait: Connection to <ip_address_primary-network>: Broken pipe” on the 2nd iteration of iperf3 testing. At IPERF server, a message popped-out on screen “the client has terminated”."
1767017,2018-04-26 11:46:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767017,2018-04-26 03:05:00 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1767020,2018-04-26 04:07:16 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1767020,2018-04-26 11:08:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767030,2018-05-11 17:56:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767030,2018-05-11 17:56:12 UTC,Filed upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/416
1767030,2018-04-30 13:45:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1767054,2018-04-26 07:41:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767054,2018-04-26 21:15:34 UTC,"""invalid"" is a bit strong, more like ""unlikely to be correct"". Part of the fun here is that subiquity currently doesn't ask for a country at all, I guess we should, although I suppose that doesn't matter much for Polish..."
1767054,2018-04-26 08:05:20 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1767057,2018-04-26 08:34:40 UTC,Did it work for beta2?
1767057,2018-04-26 08:55:51 UTC,I've reproduced this with the 64bit beta 2 ISO as well.
1767058,2018-04-30 10:20:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/565183"
1767058,2018-05-08 23:09:36 UTC,"Reviewed:  https://review.openstack.org/565183
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1a0179f7ab9b9c7f07ce9c4dd681486de5a4443a
Submitter: Zuul
Branch:    master"
1767058,2018-05-09 12:30:48 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/567211"
1767058,2018-05-21 03:23:18 UTC,"Reviewed:  https://review.openstack.org/567211
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3bf3986c14ed14b9f460161aa4cc2950da5f56f5
Submitter: Zuul
Branch:    stable/queens"
1767058,2018-06-04 13:52:26 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1767058,2018-06-08 12:25:23 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1767064,2018-05-08 18:17:34 UTC,This change was made by a bot.
1767077,2019-02-28 06:11:52 UTC,"I can't reproduce this bug at my end, both build environments creates snapcraft-foo container/vm, is this fixed?"
1767082,2018-07-24 15:31:09 UTC,18.10 cosmic is affected too.
1767082,2018-07-07 18:09:30 UTC,Bug still exists on Ubuntu 18.04 LTS with all updates.
1767082,2018-07-10 16:50:14 UTC,"solution works for me...
https://askubuntu.com/questions/1029163/how-to-get-scilab-6-0-1-working-on-ubuntu-18-04-lts
cd ~/Downloads
wget http://http.kali.org/pool/main/libj/libjlatexmath-java/libjlatexmath-fop-java_1.0.6-1_all.deb"
1767082,2020-09-14 19:51:51 UTC,"This was fixed in scilab 6.0.1-7ubuntu1~18.04, so closing this bug."
1767082,2018-09-15 14:58:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767084,2020-09-11 19:31:30 UTC,Closing because INVALID.
1767097,2018-04-28 18:16:27 UTC,"You misunderstood what the manpage intends to say.  Over time, two pathnames can refer to different files.  Essentially, the return value depends on the file, not on the pathname.  If you delete a file and recreate the file, it is no longer the same file."
1767097,2018-04-30 06:24:32 UTC,Thanks for your response.
1767097,2018-04-30 08:06:04 UTC,I believe the expectations actually is that the function result depends on file system contents.
1767097,2018-04-30 13:40:05 UTC,"So I see. I just don't see how this is meant to be useful, since you can't know how the function will behave. Any file you choose can always be changed by someone outside of the program's control, so you can never know if you will get the same result every time or a different one."
1767105,2018-05-07 13:08:27 UTC,"Thread #19 7092 (Suspended : Container)
 kill() at syscall-template.S:84 0x7ff7e9911767
 <signal handler called>() at 0x7ff7e9cb7390
 find_block_of_size() at apr_rmm.c:106 0x7ff7ea10e25a
 apr_rmm_calloc() at apr_rmm.c:342 0x7ff7ea10ea68
 util_ald_alloc() at util_ldap_cache_mgr.c:105 0x7ff7e3369b3d
 util_ldap_compare_node_copy() at util_ldap_cache.c:257 0x7ff7e3369784
 util_ald_cache_insert() at util_ldap_cache_mgr.c:501 0x7ff7e336a310
 uldap_cache_compare() at util_ldap.c:1,183 0x7ff7e33662d3
 ldapgroup_check_authorization() at mod_authnz_ldap.c:925 0x7ff7e8459937
 apply_authz_sections() at mod_authz_core.c:737 0x7ff7e4bb99fa
 apply_authz_sections() at mod_authz_core.c:751 0x7ff7e4bb9c01
 authorize_user_core() at mod_authz_core.c:840 0x7ff7e4bb9dca
 ap_run_auth_checker() at request.c:91 0x56127e692f00
 ap_process_request_internal() at request.c:335 0x56127e695d57
 ap_process_async_request() at http_request.c:408 0x56127e6b4690
 ap_process_request() at http_request.c:445 0x56127e6b4850
 ap_process_http_sync_connection() at http_core.c:210 0x56127e6b091e
 ap_process_http_connection() at http_core.c:251 0x56127e6b091e
 ap_run_process_connection() at connection.c:41 0x56127e6a6bf0
 ap_process_connection() at connection.c:213 0x56127e6a7000
 process_socket() at worker.c:631 0x7ff7e2f51f8b
 worker_thread() at worker.c:990 0x7ff7e2f51f8b
 start_thread() at pthread_create.c:333 0x7ff7e9cad6ba
 clone() at clone.S:109 0x7ff7e99e341d"
1767105,2018-05-07 13:09:22 UTC,The following upstream bug is being worked on:
1767105,2018-05-07 13:09:52 UTC,"Thread #19 7092 (Suspended : Container)
 kill() at syscall-template.S:84 0x7ff7e9911767
 <signal handler called>() at 0x7ff7e9cb7390
 find_block_of_size() at apr_rmm.c:106 0x7ff7ea10e25a
 apr_rmm_calloc() at apr_rmm.c:342 0x7ff7ea10ea68
 util_ald_alloc() at util_ldap_cache_mgr.c:105 0x7ff7e3369b3d
 util_ldap_compare_node_copy() at util_ldap_cache.c:257 0x7ff7e3369784
 util_ald_cache_insert() at util_ldap_cache_mgr.c:501 0x7ff7e336a310
 uldap_cache_compare() at util_ldap.c:1,183 0x7ff7e33662d3
 ldapgroup_check_authorization() at mod_authnz_ldap.c:925 0x7ff7e8459937
 apply_authz_sections() at mod_authz_core.c:737 0x7ff7e4bb99fa
 apply_authz_sections() at mod_authz_core.c:751 0x7ff7e4bb9c01
 authorize_user_core() at mod_authz_core.c:840 0x7ff7e4bb9dca
 ap_run_auth_checker() at request.c:91 0x56127e692f00
 ap_process_request_internal() at request.c:335 0x56127e695d57
 ap_process_async_request() at http_request.c:408 0x56127e6b4690
 ap_process_request() at http_request.c:445 0x56127e6b4850
 ap_process_http_sync_connection() at http_core.c:210 0x56127e6b091e
 ap_process_http_connection() at http_core.c:251 0x56127e6b091e
 ap_run_process_connection() at connection.c:41 0x56127e6a6bf0
 ap_process_connection() at connection.c:213 0x56127e6a7000
 process_socket() at worker.c:631 0x7ff7e2f51f8b
 worker_thread() at worker.c:990 0x7ff7e2f51f8b
 start_thread() at pthread_create.c:333 0x7ff7e9cad6ba
 clone() at clone.S:109 0x7ff7e99e341d"
1767105,2018-05-07 13:16:31 UTC,"> Another question that raises is, why to use fcntl as a backing mechanism for
> the
> LDAP locking ? If the lock was supposed to be guaranteed among different
> nodes,
> then backing the lock in a file, IF the name was based also on the instance
> id,
> which in this case is not, it could make sense. But in a shared-threaded only
> environment, why ?
"
1767105,2018-05-08 12:12:49 UTC,In a local test I set: `Mutex fcntl:/tmp/run default`
1767105,2018-03-01 16:36:14 UTC,*** Bug 58483 has been marked as a duplicate of this bug. ***
1767105,2018-06-12 13:00:31 UTC,Hi Rafael -- out of curiosity did you ever find how fcntl() came to be used here?
1767105,2018-06-12 20:24:47 UTC,"Hello Eric,"
1767105,2018-06-14 15:47:26 UTC,"To follow up with results of testing non-file locking: yep, the end user we were working with initially had this in their config, as Rafael said:"
1767105,2018-04-26 13:26:50 UTC,"Is fcntl being forced here somehow, or is it the default (apachectl -V|grep APR_USE) ?  I wonder if an affected user could try a different mechanism, via e.g. https://httpd.apache.org/docs/2.4/mod/core.html#mutex with ""ldap-cache"" as the parm (or if they already are somehow?)"
1767105,2018-05-08 12:27:52 UTC,[Tue May 08 08:26:42.418299 2018] [ldap:crit] [pid 68897:tid 700008b10000] (11)Resource deadlock avoided: [client 127.0.0.1:60404] LDAP cache lock failed
1767105,2018-04-26 12:30:18 UTC,"For this particular bug, the following upstream comment was done:"
1767105,2016-10-22 01:25:19 UTC,"(In reply to Max Burke from comment #2)

> I have not tried a later release in production, no, only because we have
> been soaking the change to see if it improved reliability.
>
> I am looking at the mod_ldap changes between our current version (2.4.16)
> and the latest (2.4.23) and see that the only changes are whitespace, either
> adding/remove spaces or adding newlines before braces, so I would expect
> that 2.4.23 is similarly affected.
>
> The LDAP_CACHE_LOCK construct is defined only to the util_ldap.c translation
> unit, it does not seem to be available, at present, to util_ldap_cache_mgr.c
> where the RMM blocks are allocated and freed.
"
1767105,2018-03-02 01:40:15 UTC,Just for a reference on someone that finds this bug.
1767105,2018-03-01 16:41:32 UTC,I recently re-fixed an issue that causes the lock in mod_ldap to not be used.  It will be in 2.4.31. It is a one-line change.
1767105,2018-03-01 16:38:26 UTC,"Max or Eric,"
1767105,2017-03-27 16:03:36 UTC,Fixed status - sorry wrong bug.
1767105,2016-10-26 21:52:37 UTC,"(In reply to Eric Covener from comment #3)

> What kind of Require ldap-* do you use? I noticed the debian OP didn't list
> that bit.
"
1767105,2016-10-21 19:47:49 UTC,"I have not tried a later release in production, no, only because we have been soaking the change to see if it improved reliability."
1767105,2016-10-21 19:29:23 UTC,"Hi Max, it appears to me that mod_ldap is trying to manage a global (cross process  + cross thread) lock outside of rmm, which is why it tells RMM to not use a lock."
1767105,2016-10-21 18:32:23 UTC,(I originally filed this with Debian's apache team because when I searched for related information on this issue I turned up something in their bug tracker. Here is the link for more context: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814980)
1767105,2018-04-26 12:29:05 UTC,"Eric,"
1767110,2018-04-26 13:19:47 UTC,"Review in progress for https://review.opencontrail.org/42398
Submitter: Pieter Malan (<email address hidden>)"
1767110,2018-05-23 15:14:35 UTC,"Review in progress for https://review.opencontrail.org/42398
Submitter: Jan Gutter (<email address hidden>)"
1767110,2018-05-28 09:34:39 UTC,"Review in progress for https://review.opencontrail.org/42398
Submitter: Pieter Malan (<email address hidden>)"
1767110,2018-05-29 16:07:36 UTC,"Reviewed:  https://review.opencontrail.org/42398
Committed: http://github.com/Juniper/contrail-ansible/commit/ca19ee4bc33d0a7599352710e23a31685f90b85c
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1767111,2018-04-26 13:29:57 UTC,"Review in progress for https://review.opencontrail.org/42395
Submitter: Pieter Malan (<email address hidden>)"
1767111,2018-05-16 23:05:54 UTC,"Reviewed:  https://review.opencontrail.org/42395
Committed: http://github.com/Juniper/contrail-server-manager/commit/8d5193db1c110ce0a63009aaca6c31577e6aec42
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1767115,2018-04-26 13:15:50 UTC,"When prompted I asked to keep my amended conf, it has workaround for network"
1767115,2018-04-30 19:39:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767118,2021-02-21 16:42:52 UTC,https://bugs.launchpad.net/snapstore-server/+bug/1916392 (Decentralize snap store operation structure as ubuntu mirrors)
1767118,2021-02-21 16:57:39 UTC,"Please note, this problem also has on other countries and refer above mentioned feature request.
just mirrors are perfect solution for address this issue, we everyone know it since very long time."
1767118,2019-09-29 11:17:01 UTC,"I did some google about how to create an snap mirror, but no further information is provided. At Beijing, Tsinghua Univ., I got 40-100kB/s download speed, which is too slow. If anyone knows how to establish an snap mirror site, please reply or just
create a new issue at https://github.com/tuna/issues/issues/new for a snap mirror (Tuna, as mentioned above). They normally reply in 24 hours."
1767118,2019-03-20 13:48:23 UTC,This seems necessary to allow local mirrors in companies that are not connected directly to the Internet.
1767118,2019-01-29 03:07:23 UTC,Any progress?
1767122,2018-04-26 14:41:23 UTC,"That's saying that duplicity logged 199 errors.  They should be present in the log before this summary.  It most likely is IO retries, but you should check and let us know what you find."
1767122,2018-05-23 22:11:00 UTC,"Helli,"
1767122,2018-06-02 15:41:22 UTC,The log should be in ~/.cache/deja-dup/.
1767122,2018-06-06 14:52:19 UTC,"Hello,"
1767122,2018-06-07 15:45:47 UTC,Try running it like this from a terminal:
1767122,2018-06-08 18:54:10 UTC,"Hello,"
1767122,2018-06-09 20:04:17 UTC,"Yes, read the man page and pay attention to the 'cleanup' and 'remove-*' commands.  With
$ duplicity cleanup --force <target url>""
you can clean out any partial backups taking up room. With
$ duplicity remove-all-but-n-full 2 <target url>
you can remove all but the last two backup sets."
1767125,2021-02-18 16:44:48 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1767125,2020-09-08 17:32:08 UTC,"This should just be cleaned up for victoria even if we don't backport it.
requirements for fix:
 - RoleParametersDefaults should be added to the roles definitions
 - Change ComputeNeutron* to Neutron* service listings"
1767126,2018-04-26 15:05:34 UTC,The -drive if=scsi still works on the machines that have a SCSI bus by default. And the change for x86 has been documented in the ChangeLog: https://wiki.qemu.org/ChangeLog/2.12
1767128,2018-05-14 12:22:23 UTC,The verification of the Stable Release Update for designate has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1767128,2018-05-14 08:13:23 UTC,This bug was fixed in the package glance - 2:16.0.1-0ubuntu1.1
1767128,2018-05-14 08:23:08 UTC,This bug was fixed in the package cinder - 2:12.0.1-0ubuntu1
1767128,2018-05-14 08:23:22 UTC,This bug was fixed in the package gnocchi - 4.2.4-0ubuntu1
1767128,2018-05-14 12:21:25 UTC,The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1767128,2018-05-14 12:21:26 UTC,"This bug was fixed in the package cinder - 2:12.0.1-0ubuntu1~cloud0
---------------"
1767128,2018-05-14 08:13:20 UTC,This bug was fixed in the package nova - 2:17.0.3-0ubuntu1
1767128,2018-05-14 12:22:24 UTC,"This bug was fixed in the package designate - 1:6.0.1-0ubuntu1~cloud0
---------------"
1767128,2018-05-04 12:37:53 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-14 12:22:44 UTC,"This bug was fixed in the package glance - 2:16.0.1-0ubuntu1.1~cloud0
---------------"
1767128,2018-05-14 12:23:05 UTC,The verification of the Stable Release Update for gnocchi has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1767128,2018-05-14 12:23:06 UTC,"This bug was fixed in the package gnocchi - 4.2.4-0ubuntu1~cloud0
---------------"
1767128,2018-05-14 12:25:47 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1767128,2018-05-14 12:25:48 UTC,"This bug was fixed in the package nova - 2:17.0.3-0ubuntu1~cloud0
---------------"
1767128,2018-08-08 14:49:54 UTC,"This bug was fixed in the package panko - 4.0.1-0ubuntu2~cloud0
---------------"
1767128,2018-05-14 08:13:14 UTC,This bug was fixed in the package designate - 1:6.0.1-0ubuntu1
1767128,2018-05-14 12:22:42 UTC,The verification of the Stable Release Update for glance has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1767128,2018-05-14 08:13:07 UTC,"The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1767128,2018-05-03 20:14:38 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-04 16:49:56 UTC,This bug was fixed in the package nova - 2:17.0.3-0ubuntu2
1767128,2018-05-03 19:56:18 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-03 20:01:33 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-03 20:08:31 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-03 20:11:35 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-07 15:55:53 UTC,Regression tests have passed successfully for queens-proposed and bionic-proposed:
1767128,2018-05-04 12:36:36 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-04 12:37:14 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-03 13:25:56 UTC,These package versions have been uploaded to the cosmic and bionic unapproved queues where they are awaiting acceptance:
1767128,2018-05-04 12:39:34 UTC,"Hello Corey, or anyone else affected,"
1767128,2018-05-04 16:18:28 UTC,This bug was fixed in the package gnocchi - 4.2.4-0ubuntu2
1767128,2018-05-04 16:18:34 UTC,This bug was fixed in the package glance - 2:16.0.1-0ubuntu2
1767128,2018-05-04 16:18:38 UTC,This bug was fixed in the package designate - 1:6.0.1-0ubuntu2
1767128,2018-05-04 16:33:10 UTC,This bug was fixed in the package cinder - 2:12.0.1-0ubuntu2
1767128,2018-05-04 12:37:35 UTC,"Hello Corey, or anyone else affected,"
1767131,2018-05-10 16:27:36 UTC,"As we have preseeded snaps in bionic, we'll want this SRU'd there (at least)."
1767131,2018-06-20 18:06:04 UTC,"This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New"
1767131,2018-05-24 02:00:32 UTC,This bug was fixed in the package cloud-init - 18.2-59-gcd1de5f4-0ubuntu1
1767131,2018-05-14 19:42:23 UTC,An upstream commit landed for this bug.
1767131,2018-05-01 17:53:32 UTC,"The snap module, which processes 'snap' configuration [1] currently runs
just about as early as it can run.  The snapd daemon is not available until
cloud_config_modules time frame [2], so use of 'snap' or any provided
commands is not possible before that."
1767131,2018-04-26 14:56:08 UTC,"Ideally, we would be able to configure the images to specify whether or not they should block on preseeded snaps.  We have some cases where command-line utilities are installed (and so we should block) but others where only a daemon is started (where there is limited utility in blocking)."
1767131,2018-05-03 07:33:40 UTC,"There isn't currently a systemd target that indicates that snapd has completed its preseeding, so cloud-init can't be ensuring that they are available like that.  Does cloud-init do something specific to confirm that pre-seeding has been completed before the user script point?"
1767132,2021-02-18 16:45:33 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1767139,2018-05-03 22:52:47 UTC,"Reviewed:  https://review.openstack.org/566096
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=80a001989351d3d427c204c8c06cfacc964f2a35
Submitter: Zuul
Branch:    master"
1767139,2018-05-03 21:18:42 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/566164"
1767139,2018-05-05 00:38:39 UTC,"Reviewed:  https://review.openstack.org/566161
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f95a10b26eb67796a4de32c32afe85c8f6a77048
Submitter: Zuul
Branch:    stable/queens"
1767139,2018-06-08 12:25:13 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1767139,2018-05-15 04:04:07 UTC,This issue was fixed in the openstack/nova 17.0.4 release.
1767139,2018-05-03 21:09:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/566161"
1767139,2018-05-07 22:23:48 UTC,"Reviewed:  https://review.openstack.org/566164
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d75b995d03df18164e6338d8b30a7729b52d2133
Submitter: Zuul
Branch:    stable/pike"
1767139,2018-05-03 15:35:32 UTC,"Great, glad you spotted it.  It's a bit awkward for me to collect a log now that I've worked around the problem, let me know if you still need that."
1767139,2018-05-15 04:04:47 UTC,This issue was fixed in the openstack/nova 16.1.3 release.
1767139,2018-05-03 15:00:11 UTC,I know what the problem is:
1767139,2018-04-29 23:26:05 UTC,"This problem, I also encountered."
1767139,2018-04-30 14:13:58 UTC,"bodhi05, did you mark it as such using the button above?  That would give the issue more points."
1767139,2018-05-01 18:24:37 UTC,"We also ran into this bug. The weird part was that after restarting the Nova compute process, this error went away. I wonder if there was a race condition."
1767139,2018-05-03 15:26:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566096"
1767139,2018-05-03 14:52:08 UTC,Bug 1765568 is related to this. We started seeing something similar in Ocata CI once this merged:
1767139,2018-05-03 14:54:10 UTC,"To be clear, when you say,"
1767139,2018-05-02 08:33:06 UTC,I think I've found a workaround for my set-up.  It seems that this error happens if the compute starts before the control node is ready.  If I delay installation of the compute until after the control node is fully up then it seems to be more reliable.
1767143,2018-06-05 21:14:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767144,2018-07-11 14:43:58 UTC,This issue was fixed in the openstack/python-muranoclient 1.1.0 release.
1767144,2018-06-11 16:04:24 UTC,Zuul has submitted this change and it was merged. ( https://review.openstack.org/566401 )
1767144,2018-05-07 13:05:02 UTC,https://review.openstack.org/#/c/566401/
1767146,2020-11-10 16:08:31 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1767146,2021-01-10 04:17:36 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1767149,2018-04-26 16:22:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564547"
1767149,2018-04-27 15:03:23 UTC,Do we know which resources and how/why they fail?
1767149,2018-04-27 16:15:22 UTC,I update the error message in desc now
1767162,2018-11-08 04:15:50 UTC,"$ sudo lshw -c video
  *-display
       description: VGA compatible controller
       product: Richland [Radeon HD 8570D]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 1
       bus info: pci@0000:00:01.0
       version: 00
       width: 32 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=radeon latency=0
       resources: irq:26 memory:c0000000-cfffffff ioport:f000(size=256) memory:fef00000-fef3ffff memory:c0000-dffff"
1767162,2018-04-27 00:46:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1767162,2018-04-27 01:00:20 UTC,"Bug reports requires the ""Package"" information. So, here it goes. But the bug is not limited to ""rhythmbox,"" it is a general bug to Ubuntu 18.04 LTS."
1767162,2018-11-07 10:21:37 UTC,Still no solution?
1767162,2018-11-07 15:10:18 UTC,"It's not specific to rhythmbox, reassigning to gtk but it might be freetype or something else in the stack. Could you add your journalctl log just after seeing the issue?
What videocard/driver do you use? Do you get the problem at random time or maybe sometime after suspend/resume for example?"
1767164,2018-04-26 20:31:59 UTC,"Looking at https://github.com/lxc/lxd/issues/4504#issuecomment-384759354, it seems that the system may not have had ubuntu-standard installed, so on do-release-upgrade the final package removal step may have listed apparmor."
1767164,2018-04-26 20:43:08 UTC,Yes the omission of ubuntu-standard seems to be the leading candidate for the cause of this issue. Thank you for investigating.
1767164,2018-04-26 20:30:11 UTC,"I tried to reproduce this and was unable to. The apparmor package did added a Breaks: media-hub, mediascanner2.0, messaging-app, webbrowser-app because of bug #1756800 and bug #1761176 so I tried upgrades with and without these installed. Test configurations:"
1767166,2018-05-25 20:04:53 UTC,"This bug is believed to be fixed in cloud-init in version18.2-27-g6ef92c98-0ubuntu1~18.04.1. If this is still a problem for you, please make a comment and set the state back to New"
1767166,2018-04-26 21:30:32 UTC,An upstream commit landed for this bug.
1767166,2018-05-02 01:18:38 UTC,"Hello Scott, or anyone else affected,"
1767166,2018-05-02 01:21:34 UTC,"Hello Scott, or anyone else affected,"
1767166,2018-05-04 02:11:52 UTC,"Validated against Xenial and Artful, while IBMCloud doesn't have any publicly available artful images, we've contrived an example upgrade from public xenial instance to artful to ensure it doesn't break."
1767166,2018-05-07 16:29:56 UTC,Additionally ran an integration test on proposed which covers lxd kvm and ec2 platforms with no errors:
1767166,2018-05-08 17:28:39 UTC,This bug was fixed in the package cloud-init - 18.2-4-g05926e48-0ubuntu1~17.10.2
1767166,2018-05-08 17:28:54 UTC,"The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1767166,2018-05-08 17:29:16 UTC,This bug was fixed in the package cloud-init - 18.2-4-g05926e48-0ubuntu1~16.04.2
1767166,2018-06-20 18:06:29 UTC,"This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New"
1767171,2018-04-27 17:05:26 UTC,For some reason Martin made a conscious decision to not include python3-launchpadlib as a dependency of apport. I believe this is in part because apport is installed on all systems yet not many of them will end up using apport-collect or apport-retrace (the two commands which need python3-launchpadlib).
1767172,2018-04-26 18:23:40 UTC,https://github.com/systemd/systemd/pull/8830
1767172,2018-05-01 18:19:23 UTC,"Looking at where the blacklists come from, it looks like kernel autogenerates ""blacklist_linux_4.15-0-15-generic.conf"" files which have a combination of OSS and watchdog blacklists."
1767172,2018-05-01 18:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1767172,2018-05-01 18:31:28 UTC,"Please note automatic blacklisting of watchdog modules was done to prevent ""accidental"" watchdog misuse, resulting in ""random"" shutdowns of production machines. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837 for more details."
1767172,2019-05-17 20:18:21 UTC,"Kees,"
1767172,2019-05-20 17:35:42 UTC,"I think it's fine. It sounds like there will just be no way to override package-installed blacklists any more. That's unfortunate, but it's a very rare situation."
1767179,2019-09-14 18:12:58 UTC,https://github.com/mixxxdj/mixxx/pull/1985
1767180,2018-04-30 19:45:29 UTC,So I tried the latest upstream kernel of 4.16 which at the moment was 4.16.6.Bluetooth still not working at the moment.
1767180,2018-05-20 00:00:20 UTC,"Bob, to confirm this is an upstream issue, could you please test the latest mainline kernel available (4.17-rc5) and advise to the results?"
1767180,2018-04-26 19:54:21 UTC,apport information
1767180,2018-04-30 15:46:25 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1767180,2018-05-27 12:13:21 UTC,"Ok, so I tried to use the most recent kernel (4.17-rc6) and it finally got my bluetooth adapter recognized."
1767180,2018-04-26 19:54:17 UTC,apport information
1767180,2018-07-12 17:54:50 UTC,"Sorry, was super busy and internet here isnt very good. So not really getting the reverse kernel bisection, is it just going from 4.17rc6 to 4.16.6 and seeing when bluetooth started working? Sorry I'm not that good with this sort of stuff."
1767180,2018-07-12 20:21:33 UTC,Bob:
1767180,2018-07-19 14:04:46 UTC,Ok so I tried looking back until I found the last working update. It was kernel version 4.16.12. When I installed 4.16.11 bluetooth appears as disabled and doesn't work.
1767180,2018-07-25 10:05:24 UTC,So this should be the commit that fixes your issue:
1767180,2019-02-14 16:54:57 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1767180,2018-05-27 13:08:34 UTC,"Bob, the next step is to fully reverse commit bisect from kernel 4.16.6 to 4.17-rc6, in order to identify the earliest good kernel commit, preceded immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?"
1767180,2018-04-26 19:54:14 UTC,apport information
1767180,2018-04-26 19:54:24 UTC,apport information
1767180,2018-04-26 19:54:08 UTC,apport information
1767180,2018-04-26 19:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1767180,2018-04-26 19:53:41 UTC,apport information
1767180,2018-04-26 19:53:43 UTC,apport information
1767180,2018-04-26 19:53:47 UTC,apport information
1767180,2018-04-26 19:53:51 UTC,apport information
1767180,2018-04-26 19:54:12 UTC,apport information
1767180,2018-04-26 19:53:56 UTC,apport information
1767180,2018-04-26 19:53:59 UTC,apport information
1767180,2018-04-26 19:54:01 UTC,apport information
1767180,2018-04-26 19:53:53 UTC,apport information
1767180,2018-04-26 19:54:06 UTC,apport information
1767181,2018-06-28 21:17:35 UTC,apport information
1767181,2018-06-28 21:17:36 UTC,apport information
1767181,2018-06-28 21:17:37 UTC,apport information
1767181,2018-06-28 21:17:39 UTC,apport information
1767181,2018-06-28 21:17:40 UTC,apport information
1767181,2018-06-28 21:17:54 UTC,apport information
1767181,2018-06-28 21:17:47 UTC,apport information
1767181,2018-06-28 21:17:32 UTC,apport information
1767181,2018-06-28 21:18:52 UTC,I have similar issue with a Logitech USB headset.  See attached apport info in the comments above.
1767181,2018-07-01 09:46:05 UTC,"Same as bladernr, the reboot helped me, but I don't think reboot should be necessary for USB plug-n-play devices."
1767181,2018-07-02 03:29:21 UTC,Can you do a kernel bisection?
1767181,2018-06-28 21:17:42 UTC,apport information
1767181,2018-06-28 21:17:31 UTC,apport information
1767181,2018-06-28 21:17:33 UTC,apport information
1767181,2018-06-28 21:17:28 UTC,apport information
1767181,2018-06-28 21:17:30 UTC,apport information
1767181,2018-04-26 19:44:40 UTC,"In these three screen shots, note that the settings ONLY apply to the line-in device, even when I select the webcam mic and the Jabra Speak, the only settings options are for line-in."
1767181,2018-04-26 19:45:14 UTC,"Finally, I plugged a headset into the line-in/out jack on the motherboard and that does work for both input and output."
1767181,2018-04-26 20:03:04 UTC,"Just to be sure, I logged out of Unity and logged into Gnome 3 and the results are identical. NO USB audio device works."
1767181,2018-04-26 20:07:51 UTC,"I also fired up alsamixer and again, the USB audio device is listed and accessible but not usable for sound in or out."
1767181,2018-04-26 19:43:07 UTC,"In the previous two screen shots, note that the Settings heading changes for each output device I choose, EXCEPT for the USB audio output device (as in this screenshot)."
1767181,2018-05-08 18:17:53 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1767181,2018-06-28 21:17:21 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   andrei    11513 F...m pulseaudio
 /dev/snd/pcmC0D0p:   andrei    11513 F...m pulseaudio
 /dev/snd/controlC0:  andrei    11513 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab
InstallationDate: Installed on 2017-12-26 (184 days ago)
InstallationMedia: Ubuntu 16.04 ""Xenial"" - Build amd64 LIVE Binary 20160624-10:47
MachineType: Dell Inc. Inspiron 5570
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic  N/A
 linux-firmware                             1.173.1
Tags:  bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-06-10 (18 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 09/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.4
dmi.board.name: 0DRPKR
dmi.board.vendor: Dell Inc.
dmi.board.version: X07
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.sys.vendor: Dell Inc."
1767181,2018-06-28 21:17:23 UTC,apport information
1767181,2018-06-28 21:17:25 UTC,apport information
1767181,2018-04-26 20:50:52 UTC,"OK, so I rebooted into 4.13.0-39 and as soon as I was logged in the USB audio started working.  So I thought maybe that indicated a regression between 4.13 and 4.15.  HOWEVER< I then rebooted again, into 4.15 once more, and now I have audio in and out on the USB devices."
1767195,2018-04-26 21:11:46 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1767196,2018-04-26 22:12:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1767196,2018-07-12 18:52:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767201,2018-05-01 02:04:04 UTC,"Hi Dan, can you please describe what you're doing, what you expected to happen, and what happened? Messages from logfiles might also be helpful."
1767201,2018-05-01 16:52:00 UTC,"Hi Seth,"
1767201,2018-05-02 06:39:38 UTC,"There have been no changes to the authentication stack from the side of pam and sudo.  If kvpm is calling sudo, and failing to call it in a context that has a tty available such that the user is never able to enter a password, this is not a bug in either pam or sudo but in kvpm."
1767203,2018-04-26 22:12:06 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1767210,2018-09-04 23:37:52 UTC,"I entered a question on the Ubuntu forums here https://ubuntuforums.org/showthread.php?t=2400309&p=13797999#post13797999.  Although I got the crash report, I must have cleared this while handling some other issue."
1767210,2018-04-27 18:53:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767218,2019-05-07 06:03:26 UTC,And the 3d viewer might also be another thing that would be good if it also allowed showing different variants (same of course with step export for your mechanical engineer)
1767218,2019-03-25 10:12:54 UTC,Hi all.
1767218,2018-10-18 11:29:53 UTC,"Yes, @nicke. And I alredy use KiCost."
1767218,2018-10-16 14:08:12 UTC,"Other EDA that recently had add variant system
http://labcenter.s3.amazonaws.com/movies/v8/designVariants.html"
1767218,2018-10-18 07:14:46 UTC,"By board variant, do you mean that the PCB artwork is the same, but only the BOM is different?"
1767223,2018-12-18 11:18:48 UTC,@ubuntu-sru and @ubuntu-sponsors: would you mind doing a new upload of this package to bionic using the same source as in the last build? This bug will be solved by rebuilding from the same source using the gcc-arm-none-eabi package currently in bionic.
1767223,2018-12-19 00:17:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767223,2019-04-20 18:40:44 UTC,"Hello Thomas, thank you for your work on this and I apologize for the delay on this."
1767223,2019-04-22 13:54:09 UTC,"Hi Simon, thank you very much for your attention to this bug as it has a major impact for many of us users!"
1767223,2019-04-22 14:02:56 UTC,Hi David!
1767223,2019-04-22 14:26:54 UTC,"This issue is present in Bionic only. (Looking back at the discussion on this bug, the package was confirmed working on Cosmic as of 2018-07-16.)"
1767223,2019-04-22 16:49:31 UTC,"Uploaded to Bionic, it is now awaiting review by the SRU team."
1767223,2019-04-23 15:29:14 UTC,"Dear Adam and/or Simon,"
1767223,2019-04-23 15:32:03 UTC,"I dug a little deeper and found that that the build failed with
the following error message:"
1767223,2019-06-06 21:50:21 UTC,fixed newlib package uploaded to bionic unapproved queue.
1767223,2019-06-20 22:37:10 UTC,"Hello Ed, or anyone else affected,"
1767223,2019-06-21 15:30:20 UTC,I tested with libnewlib-arm-none-eabi and libnewlib-dev from bionic-proposed:
1767223,2019-07-01 08:05:19 UTC,"The verification of the Stable Release Update for newlib has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1767223,2019-07-01 08:15:20 UTC,This bug was fixed in the package newlib - 2.4.0.20160527-3ubuntu0.1
1767223,2019-04-22 17:00:38 UTC,"Hello Ed, or anyone else affected,"
1767223,2018-12-18 03:50:11 UTC,"the universe section of the archive is mostly maintained by the Ubuntu community. Non-paid, non-commercially. So you either work with them to fix the issue, or live with it.  No, I'm not willing to spend my free time on this issue, and apparently you aren't either."
1767223,2018-12-18 11:03:57 UTC,This bug is due to newlib built against an older version of gcc-arm-none-eabi. It will be fixed by rebuilding newlib using the same source.
1767223,2018-12-18 01:07:10 UTC,"> but I don't understand why fixed packages are not available for bionic.
"
1767223,2018-04-27 09:31:48 UTC,"Note: I do not think it is an upstream problem, since I downloaded gcc-arm-none-eabi-6-2017-q2-update from ARM which contains a very similar version (both 6.3.1 20170620) and it does not exhibit the issue."
1767223,2018-05-02 14:38:16 UTC,I am having that issue also (using mbed-cli) after upgrading to 18.04. (Used to work on 17.10).
1767223,2018-05-02 14:39:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767223,2018-05-25 11:52:31 UTC,The same issue here. Needed to uninstall from apt and download from ARM website.
1767223,2018-06-13 07:39:26 UTC,Encountered the same issue. Is there a workaround/patch?
1767223,2018-12-18 02:32:06 UTC,"> And no, it doesn't help to state ""the bug is still there"" without addressing it.
"
1767223,2018-06-21 19:36:26 UTC,"There is more broken, thumb/libc.a contains strcmp for the wrong architecture.  So unless you don't need strcmp, there is no workaround."
1767223,2018-06-21 12:53:06 UTC,I'm also affected by this (Cortex M3).
1767223,2018-06-22 05:01:17 UTC,"(The work around mentioned in my opening post only partially helps, my code eventually crashes, presumably executing a libc or other stdlib function)"
1767223,2018-07-16 08:09:58 UTC,"Upstream Debian has fixed the issue and Cosmic already has the new packages. If you are on Bionic you can install the Cosmic packages to temporarily fix the issue, see https://github.com/bbcmicrobit/micropython/issues/514#issuecomment-404759614"
1767223,2018-07-16 18:18:11 UTC,"That's good, but I don't understand why fixed packages are not available for bionic. It's been almost 3 months! For now I will continue using the cross compiler builds provided by ARM."
1767223,2018-07-17 13:57:09 UTC,"I think they just don't care enough about the ""universe"" packages (or don't have the time/resources to care), they are just importing them from Debian's repos ""as is"" and very rarely update them, if ever."
1767223,2018-08-14 18:30:21 UTC,"I can confirm that this bug is still present in Bionic. The libnewlib-arm-none-eabi package is unusable. Pulling in the fixed version from upstream, or switching to the gcc-arm-embedded ppa, fixes the issue."
1767223,2018-12-17 16:17:13 UTC,"The bug is still present (2018-12-17).
Package version: 15:6.3.1+svn253039-1build1"
1767223,2018-06-22 04:57:07 UTC,"Yes, I think aside from building your own libc (and I'm not even certain that would fix it) the only alternative at present is to use a different toolchain or build your own. The binary toolchains from ARM (https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads) do however work fine."
1767227,2018-04-27 16:33:27 UTC,Ryan:
1767227,2018-07-24 07:42:09 UTC,This has been committed but hasn't been backported to Bionic.
1767227,2018-04-27 15:49:31 UTC,Thanks to Cyphermox for their very useful example and description of how to achieve this.
1767227,2018-04-27 16:20:17 UTC,Would you want to put up a PR that updates doc/netplan.md and doc/example-config?
1767227,2018-04-27 16:21:42 UTC,"Also, just for documentation within this bug, could you post what ultimately got things functioning for you?"
1767227,2018-05-02 15:00:58 UTC,Ryan:
1767235,2020-11-24 16:43:49 UTC,Until this is implemented I use &trigger=hello/... with the version in the target release.
1767237,2018-04-29 21:31:24 UTC,"The individual test results are in the artifacts ""summary"" file, so this can be done."
1767238,2018-04-29 07:54:39 UTC,"The policy.json file exists in stable/pike branch:
http://git.openstack.org/cgit/openstack/vitrage/tree/etc/vitrage/policy.json?h=stable%2Fpike"
1767238,2018-05-09 09:53:06 UTC,Thank you.
1767238,2018-06-10 15:00:58 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/574090"
1767238,2018-06-14 07:35:20 UTC,"Reviewed:  https://review.openstack.org/574090
Committed: https://git.openstack.org/cgit/openstack/vitrage/commit/?id=6e71478308bccd4f91afb07e15c0655700627a0e
Submitter: Zuul
Branch:    stable/pike"
1767238,2019-04-16 18:55:54 UTC,This issue was fixed in the openstack/vitrage 1.8.3 release.
1767255,2018-04-27 13:23:28 UTC,The canonical-certification-server command has been changed. You should now use the certify-18.04 command to run a full certification on Ubuntu 18.04. Various other commands exist to run a subset of the certification tests or to certify an Ubuntu 16.04 installation; see the recently-revised Self Test Guide (available from https://certification.canonical.com) for details.
1767255,2018-04-27 15:29:04 UTC,Recieved a good suggestion regarding this so implementing a helper in the suite.
1767255,2018-04-27 03:59:50 UTC,"Also, I've attached the current PPA."
1767272,2018-04-27 07:37:12 UTC,"The data log was too long.  because data deleted some versions.
And adding the 'cause'"
1767272,2018-04-27 08:35:54 UTC,updated the solution
1767272,2018-04-27 10:10:50 UTC,delete the sample patch. because I submitted repairing code to Gerrit.
1767272,2018-04-27 11:05:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564731"
1767272,2018-04-27 14:11:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/564774"
1767272,2018-05-08 12:25:03 UTC,"Change abandoned by Takahito Hirose (<email address hidden>) on branch: master
Review: https://review.openstack.org/564722
Reason: miss commit"
1767272,2018-05-08 12:25:26 UTC,"Change abandoned by Takahito Hirose (<email address hidden>) on branch: master
Review: https://review.openstack.org/564774
Reason: miss commit"
1767272,2018-05-08 12:27:20 UTC,"Change abandoned by Takahito Hirose (<email address hidden>) on branch: master
Review: https://review.openstack.org/564731
Reason: miss commit"
1767272,2018-07-27 08:24:13 UTC,"Change abandoned by Takahito Hirose (<email address hidden>) on branch: master
Review: https://review.openstack.org/564702"
1767272,2019-09-10 07:18:55 UTC,"This bug has been open for about a year without any activity.
It is not sure that this bug can be reproduced in python-novaclient latest version.
I'm going to move it to ""Incomplete"".
This bug can be reopened (set back to ""New"") if this bug can be reproduced in python-novaclient latest version or someone decides to work on this."
1767276,2018-11-26 06:21:50 UTC,"I have the same issue, Venkatesh's solution works for me but every time i do an upgrade it return."
1767276,2018-06-10 14:53:45 UTC,found a solution at https://askubuntu.com/a/1032156 and it works...
1767276,2018-11-20 11:34:00 UTC,"I am also affected by this, and the solution posted by Venkatesh R works for me."
1767276,2018-05-15 07:30:12 UTC,"I was in fact affected by this bug, which is definitely a duplicate of  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 as the fix worked great for me. I installed the first kernel, booted into it, had dpkg try again and everything worked. Booting back into the regular kernel was a snap and I purged the temporary kernel and fixed up the /vmlinuz and /initrd.img symlinks and rebooted cleanly."
1767276,2018-06-10 15:34:00 UTC,"I know of no reason that moving around the Ubuntu directory on your ESP would solve an efibootmgr failure.  If the cause of this wrote for you is that your firmware has been marked read-only by the previous kernel bug in Ubuntu 17.10, this will definitely not correct that problem."
1767276,2018-04-27 11:34:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767276,2018-05-11 04:52:33 UTC,Go to the hyperlink which Steve has mentioned and install the kernel. Then boot choosing the newly installed kernel option and go to recovery mode and upgrade your grub. Again reboot but choose the 4.15 kernel. And update. the shim package is installed.
1767276,2018-04-27 07:38:03 UTC,The error in your log is:
1767281,2018-05-03 13:54:20 UTC,Reported against design on https://github.com/CanonicalLtd/desktop-design/issues/109
1767281,2018-09-02 14:28:24 UTC,"Well spotted, Po-Hsu Lin, this was an error on my part. It should be “Ubuntu Software” (or whatever the app happens to be named at the time)."
1767294,2018-04-27 08:26:46 UTC,Thanks for your report. Confirmed on my system.
1767294,2018-04-27 08:59:59 UTC,"Even on system installed in 2012, this happens."
1767299,2019-09-19 03:35:27 UTC,For reasons stated further above I like to propose changing the status of this bug to critical.
1767299,2019-09-18 16:36:42 UTC,Works fine here with LVM.
1767299,2019-09-18 13:30:01 UTC,Setting up a Swap file is easy enough. Yet it's not the same as having a Swap partition with the correct size. It brings problems down the road with hibernation. I believe the average user wants a large enough Swap partition out of the box with hibernation enabled. More advanced users who don't like this kind of setup can feel free to change this to whatever they want. It's important to make Ubuntu Desktop usable for the average person out of the box without any advanced trickery or important features like hibernation disabled.
1767299,2019-09-18 12:06:49 UTC,"that approach works only when using a swapfile .. but as noted in the OP, when using an LVM partition it doesn't work so easily."
1767299,2019-09-17 08:55:58 UTC,Are there some easy to follow instructions how to increase the partition size without breaking the encryption setup?
1767299,2019-09-18 06:47:13 UTC,This is a major problem. I am now forced to do a full reinstall with proper swap allocation. This will set me back at least 1 full business day until I synced all my files again. There are not many common users out there who will go to that extend just to move over to Ubuntu.
1767299,2019-11-02 14:14:52 UTC,"I may have missed it, but I have encrypted SSD and want to hibernate.  I think I read that I have to use bigger encrypted swap partition (not file) and that it needs to have user-entered password.  Don't think I found anything that had how to do all that together.  I'm new to Linux, so any help is appreciated!"
1767299,2018-12-27 08:47:32 UTC,"The same problem here. Dell XPS 9370. LVM, whole disk encryption, 8GB RAM, 256GB SSD, 975MB swap. After an hour or two of ""heavy"" usage with various IDEs the laptop literally hangs because the CPU overheats, I believe due to RAM thrashing. I have to walk away from it for 15 mins to let it cool down. I'm lucky if I don't have to hard reboot it."
1767299,2018-12-27 07:32:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767299,2019-09-18 08:28:46 UTC,I manually add 4GB to the swapfile by
1767299,2020-10-08 12:48:42 UTC,"Upgraded to Kubuntu 20.04 from Linux Mint 18.3 (based on Ubuntu 16.04) just a couple of days ago, I already got one OOM and another time so close. I have 16 GB of RAM and I need to open many heavy programs. Never had any problem to handle this with my SSD and my previous 16.04 system, with highly acceptable results.
I can't see how this 1 GB swap file ""by default"" can be considered an improvement. If you don't want systems to swap, just remove the swap as a whole, why 1 GB?"
1767299,2020-02-24 18:02:53 UTC,"- high memory systems for desktop machines are rare: most people using desktop version of ubuntu have way more disk than RAM.
- it is quite hard for a non-expert user who just wants a secure system with encrypted disk and use hibernation to resize lvm partitions: there's no GUI tool for it, so he needs to learn to use several lvm command line tools
- although there are good reasons not to enable hibernation by default, it should be easy to enable it manually later as it is important for many laptop users.
- moreover, installer could be simply detecting if a given system is a high-memory one instead of applying strict defaults blindly: swap space could be capped for example with min(2*RAM, 0.2*disk)
- if taking into consideration disk size when deciding swap size is too difficult for any reason, there could be at least an option in the installer *GUI*: dealing with preseeding is also difficult for an average user for whom creating a bootable pendrive was already a challenge"
1767299,2019-12-16 14:45:08 UTC,@mjm3413 The steps I outlined further above work just fine with an encrypted SSD.
1767299,2019-12-16 17:39:08 UTC,"I'm sorry, I had no intention to change the visibility of the bug, I have reverted the change."
1767299,2020-03-06 19:53:43 UTC,"I tested Ubunto 20.04 daily today, and it seems the installer was still not fixed. A 4GB VirtualBox would only get 1GB as swap in encrypted LVM mode."
1767299,2020-05-04 22:43:35 UTC,"There seems to be a misconception on the part of the devs that allowing too much swap will result in machines under memory pressure suffering worse than if they simply ran out of memory and the kernel's OOM killer rescued the system.  Running out of memory is almost *never* better than hitting swap.  Depending on the application, it is possible to swap out vast swaths of system memory to make room for temporary spikes in memory allocation. It is also customary for the kernel to swap out about 1GB of memory that will most likely never be accessed again after boot.   This cannot be done when the max swap is 1GB.  Factor in fast SSD's and VNME's that come much closer to the performance of RAM, and a system can remain quite usable even if it should develop a swap storm.  The bottom line is that this should be a user-tunable in the installer and not something users have to resort to swapfiles to work around."
1767299,2020-05-19 13:17:27 UTC,Found same issue on Ubuntu 20.04.
1767299,2020-07-09 18:55:06 UTC,"Really. After I installed a new machine with an encrypted rootfs, I find out that it crashes under load, because with 64G memory it only has 1G swap? Why add swap at all and give a false sense of safety?"
1767299,2020-08-19 10:38:20 UTC,Why is this not fixed since 2018-04-27 !!! and I have to face the same problem after installing Ubuntu 20.04.1 ?
1767299,2020-08-25 05:43:46 UTC,"See above why it's not fixed. It's b/c xnox doesn't want to accept that his fix for #1351267 was less than ideal, so he labelled the problem ""opinion""."
1767299,2020-10-01 03:17:07 UTC,"Then, how can we get any other developer attention to fix this xnox's incompetent swap calculation algorithm?"
1767299,2020-10-08 09:03:13 UTC,"It looks like this is still a problem in Ubuntu 20.
Can we remove 18.04-20.04 from the title?"
1767299,2018-12-24 06:14:36 UTC,"I installed 16.04 on a hand-me-down laptop, because I need to support another system that is on 16.04 and it is easier for me to have an identical system
I installed 16.04, because later versions do not allow remote control using remmina (# 1790251, 1790249 & 1741027).
System is a 8Gb laptop with a 480Mb ssd.
Installer created a swap of 976Mb.
Install version was 16.04.5.  (Note that my DVD with 16.04.3 creates a swap of appropriate size.)"
1767299,2019-11-03 22:50:25 UTC,I have a number of users who want larger swap partitions. Is there an update on how to achieve this on first install? Only custom preseed steps?
1767299,2018-10-02 08:19:12 UTC,"We have 3 ASUS Laptops which have been re-imagined from Windows to Ubuntu 18.04, as part of an initial trial to move all 38 laptops to Ubuntu 18.04."
1767299,2018-06-25 14:31:10 UTC,"24h is quite short for a laptop not being used, it is less than a weekend. So I'd rather use hibernation for this reason, or I'll find my laptop battery empty on unsuitable moments."
1767299,2018-09-28 08:45:46 UTC,"I also agree that this 1 GB default is terrible. I have 16 GB RAM (maximum allowed on this laptop) and on Ubuntu 16.04 I had 8 GB swap and never noticed any performance issues. Now I reinstalled Ubuntu 18.04 from scratch and ended up with this 1 GB default, once I have a few Docker containers running, an IDE, and lots of tabs open in Chrome or Firefox, then I start getting slowdowns, sometimes to the point that the machine grinds to a halt and the only solution is to power off and restart."
1767299,2018-05-11 06:50:25 UTC,"Hello. Is there somebody looking into this problem? No comment from ubuntu-devs so far and I wonder if this report is even noticed. To me the importance of the problem seems to be high at least because it might affect all users choosing auto partition, lvm and encryption when installing ubuntu...."
1767299,2018-05-11 18:53:12 UTC,Just discovered I'm having the same issue. I used `d-i partman-auto/choose_recipe select atomic` for the install along with `d-i partman-auto-lvm/guided_size string max`. I can dump all the partman parameters here if that helps.
1767299,2018-05-11 18:53:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767299,2018-05-24 14:57:30 UTC,"Possibly related to changes for this ""bug""? https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1351267"
1767299,2018-05-30 15:20:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767299,2018-09-29 14:15:54 UTC,"The same problem here. LVM, whole disc encryption, 16GB RAM, 120GB SSD, 975MB swap. Any hints how to increase swap to 16GB without losing any data on ubuntu-vg?"
1767299,2018-06-18 17:07:05 UTC,Change appears to be intentional:
1767299,2018-06-21 15:31:20 UTC,It is intentional to have smaller swaps by default than it used to be the case.
1767299,2018-06-22 12:58:48 UTC,Nice to know that the value is configurable.
1767299,2018-06-23 05:36:53 UTC,"I wonder if it is an opinion that the number of companies using Ubuntu on laptops might be reduced starting with 18.04 considering the amount of extra effort to write a completely custom partman recipe with a larger swap (or assuming the answer above works in the preseed to actually get the old behavior of 100% or so) in order to use hibernation to conserve battery life, since suspend still tends to run a battery down fairly quickly, and those that don't have access to power now have to shut down their machines completely losing their working state rather than being able to quickly hibernate and resume."
1767299,2018-06-03 20:56:43 UTC,"This also happened to me.  GUI install, Erase all with encryption selected.  With a 250GB SSD and 12GB memory the installer gave me a 1GB swap partition and 249GB root partition."
1767299,2018-06-25 15:22:57 UTC,"It can also depend whether you have a discrete GPU or not, as sometimes those don't properly power off and eat a lot more battery when running and possibly when suspended. I frequently take my laptop home in case the on-call phone rings, and if I suspend on a Thursday/Friday and I don't pull it out of my bag and plug it in, if it is a holiday weekend I may pull it out and have the battery at 10% or less, which doesn't last long once you get on VPN and have the CPU crunching away at encryption, and having a fully encrypted disk also eats more battery (and makes it harder to do the LVM resize mentioned above)."
1767299,2018-06-25 16:02:10 UTC,"typically hibernation only collects the dirty pages in ram, compresses them and writes them to disk (swap) as an image (unless the code changed dramatically in the last years)."
1767299,2018-06-25 16:41:49 UTC,"IIRC, the default native kernel method does not compress the data, for that you need to install the swsusp2 package I think it was."
1767299,2018-06-25 18:58:38 UTC,"Per the above the flag appears to work, and it appears that setting the cap still does the automatic detection when the system memory is equal to or less than the cap."
1767299,2018-06-25 19:39:17 UTC,"We have for years before this change not supported hibernate out of the box on the desktop.  Regardless of whether the triggering bug report was cloud-oriented, this is not a change made just for the cloud.  Having too much swap on desktops is ALSO harmful because it will cause the kernel to enter swap death instead of OOM-killing processes to unblock the interactive environment.  This change in default behavior of the installer is fully intentional."
1767299,2018-06-28 14:32:28 UTC,"I think 950MB of swap default is too little for systems with low memory. Default install on a low-end laptop with 4GB of ram supplies me with a 950MB sized swap partition and it is easily filled when running browser with several tabs and some other programs running. Also on 8GB ram machines I get easily 1-2GB swap in use after an uptime of several days.
For machines with 16GB or more you could argue if swap is useful anyway except from hibernation maybe."
1767299,2018-07-07 16:32:19 UTC,"Made a fresh install recently and today bumped into heavy lags running a react native app on an Android emulator. Previous 16.04 install had 8 gigs swap and I had no issues with that. It never got full. I find the decision to lower it to 1Gb terrible, especially not giving an option or even a warning during the installation process."
1767299,2018-07-17 06:33:26 UTC,I totally agree that a 1 GB default is terrible.
1767299,2018-07-26 14:48:00 UTC,"Your issue is that you need more memory, not that you do not have enough swap.  The system grinds to a halt because swap is *really* slow.  You need enough memory so that you don't have to swap."
1767299,2018-07-27 07:06:36 UTC,"Also installed 18.04 with encryption and LVM on my laptop through the GUI installation. And got ~1GB swap. The process ""kswapd0"" started take all my CPU and made my new installed laptop freeze/hang. When the process swapped/worked no space left on the allocated swap memory area."
1767299,2018-06-25 14:06:55 UTC,"I'm kind of partial to hibernation myself, but really these days suspend only uses like 1% per hour ( or less ) so unless you are planning on being suspended for 24+ hours, you really don't need to worry about it."
1767302,2018-10-24 20:39:45 UTC,"I can confirm Gnome Boxes (gnome-boxes) works properly again in Ubuntu 18.10 x64.
Gnome Boxes version 3.30.2-0dc83a95 from dl.flathub.org."
1767302,2018-10-24 20:41:52 UTC,"Christian, get Flathub for Ubuntu and install the Flathub/Flatpak version of Boxes.
https://flathub.org/home"
1767302,2018-11-22 06:55:41 UTC,"Thanks Jeb.
With that in place, but no other confirmation on the PPA I think this is good for now.
I still pinged on my MP to Debian for consideration but the bug as reported here is incomplete for now (no clear action that we have to take for now)."
1767302,2019-01-07 13:52:33 UTC,"The user logged in in Cosmic and later should get uaccess set on /dev/kvm
getfacl /dev/kvm
after login should show that.
That is from udev/systemd and should therefore handle permissions correctly even without qemu installed in recent Ubuntu versions."
1767302,2018-09-24 07:32:56 UTC,"Suggested also to Debian via [1], but there the situation might be different (?polkit?)."
1767302,2019-01-07 14:40:33 UTC,"Christian, are you saying that you don't intend to SRU a fix to Ubuntu 18.04 LTS?"
1767302,2019-01-07 14:53:09 UTC,"Hi - Jeremy yes, not in qemu at least."
1767302,2019-04-27 12:11:16 UTC,Solved on 18.04 with: sudo adduser 'user' kvm and rebooted
1767302,2019-12-11 11:46:09 UTC,"FYI: adduser <username> kvm solves that problem
nope. added myself and still no joy."
1767302,2019-01-07 14:02:00 UTC,A little summary for my bad memory:
1767302,2018-09-24 07:15:50 UTC,"To be clear I'm waiting on a confirm that this (PPA above) is of benefit before pushing any further.
Setting this bug to incomplete to reflect this."
1767302,2019-01-07 14:56:24 UTC,"That were quite some updates, but it shows
- the fix in >=Cosmic came in via systemd
- (at least atm) I do not intend to fix it in Bionic Qemu
- gnome-boxes in Bionic is affected and could get a fix (the suggested auto-adding of users to
  group kvm if you want that)"
1767302,2018-09-17 12:56:15 UTC,Thanks Christian for looking into this. Maybe GNOME Boxes itself could suggest that users log out then log back in. There's this bug which asks Boxes to be more helpful in cases like this:
1767302,2018-09-17 12:26:59 UTC,"Thanks for the Ack Mdeslaur, Diff would be like:"
1767302,2018-09-17 12:09:40 UTC,"ACK from the security team, adding the sudo user to the kvm group is acceptable as we already to basically the same with the libvirtd group."
1767302,2018-09-17 12:01:48 UTC,"One more important thing to mention - even if we change the postinst to add you to group KVM.
Especially for desktop users (harder to re-login) you might still be affected by the current login context not directly getting the new group membership ""to be effective"" and therefore requiring a new login (see [1])."
1767302,2018-09-17 11:58:10 UTC,"I found the actual issue, thanks for all your feedback."
1767302,2018-09-17 07:31:07 UTC,"I've just installed gnome boxes into a virtual machine and checked by groups both before and after, and I'm not a member of the kvm group, despite being in the sudo group."
1767302,2018-09-17 06:13:22 UTC,"It would usually add users that are part of the sudo group to the KVM group.
Are you a member of the sudo group or are we facing an issue that this logic is nor more working?"
1767302,2018-05-20 18:59:28 UTC,"This actually affected me after the upgrade to Bionic. It was working before that.
Adding myself to the kvm group has Gnome Boxes working again.
For those who are still ""terminal leery"" you can add the ""Users and Groups"" app from the Software store for a GUI approach. Open it and find the kvm group, then select the box to add yourself to it. Log off or reboot and Gnome Boxes should fire up."
1767302,2018-05-19 04:56:05 UTC,"Might be the answer to this bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1759806"
1767302,2018-09-17 13:19:34 UTC,Could somebody give the PPA at [1] a try if that would achive what a gnome-boxes user would need?
1767302,2018-05-19 04:49:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767303,2019-06-03 12:26:05 UTC,"Change abandoned by Surya Seetharaman (<email address hidden>) on branch: master
Review: https://review.opendev.org/635532
Reason: cern specific"
1767303,2019-02-07 15:12:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/635532"
1767303,2018-12-06 14:59:50 UTC,"OK I understand the issue now. The problem is that when we get results from placement, all of the allocation candidates (compute nodes) might be in a single cell, because maybe the request is tied to an aggregate which represents that cell. But when the HostManager queries the cell databases for the compute nodes, it iterates overall enabled cells, which could be ~70 in CERNs case. So we're doing a lot of extra DB queries that won't yield results, and might be on older slower cell DBs which take longer to return a response."
1767303,2018-05-03 14:19:39 UTC,"If https://review.openstack.org/#/c/539617/ isn't enough, we could also think about adding a HostMapping.uuid field which mirrors the ComputeNode.uuid field and then we could get the list of host mappings by uuids and from that list get the list of cells from which to pull the compute nodes, but it would be good to know if https://review.openstack.org/#/c/539617/ made a big enough difference that it's good enough for now."
1767303,2018-11-06 19:05:35 UTC,"Or maybe at this point, this is a duplicate of bug 1737465?"
1767303,2018-05-03 14:10:57 UTC,"I'm confused, you reference https://review.openstack.org/#/c/539617/ but are pasting a code snippet of old code before that scatter/gather routine was added. Does https://review.openstack.org/#/c/539617/ resolve your issue or at least make it acceptable performance?"
1767309,2018-04-30 14:23:36 UTC,"Add this as a config option on master with a default being the same as the hard-coded value today (300), and include a 'fixes' release note with it since this isn't a feature."
1767309,2018-05-01 15:58:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/565526"
1767309,2018-05-03 16:22:52 UTC,"Reviewed:  https://review.openstack.org/565526
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=41d6b479fe8baf66578044b8773c3b892d64a2c4
Submitter: Zuul
Branch:    master"
1767309,2018-05-04 11:02:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/566288"
1767309,2018-05-09 22:48:25 UTC,"Reviewed:  https://review.openstack.org/566288
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3a39cfc471953f95b692c15ce2175bf92035a2da
Submitter: Zuul
Branch:    stable/queens"
1767309,2018-05-15 04:04:05 UTC,This issue was fixed in the openstack/nova 17.0.4 release.
1767309,2018-06-08 12:25:17 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1767312,2019-03-05 02:06:15 UTC,"I'm also affected by this bug. I've tried many different things that I described in another bug report:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1818382"
1767312,2019-03-05 02:18:52 UTC,Please use the workaround at the top of this bug.
1767312,2019-03-06 09:45:49 UTC,removing gstreamer1.0-vaapi did the trick but I don't think a user should be expected to do that on every new installation.
1767312,2019-03-06 09:48:59 UTC,Maybe it shouldn't be included in 19.04 until it's fixed?
1767312,2019-03-07 01:28:57 UTC,"As already stated above, the correct workaround, for now, is to configure a drirc (probably in a conf.d directory, so it doesn't clash with other settings files) so as to disable 10 bit per channel support for Totem. The same had to be done with Chromium-vaapi, as it also happens with that solution."
1767312,2019-03-07 08:34:51 UTC,"Which DRI driver are you using? 10bpc is disabled for every gallium driver (like radeonsi) and intel, so I don't understand how changing the drirc would affect at all."
1767312,2019-03-08 06:45:14 UTC,"This bug can only occur if 10bpc is enabled. There is no other possibility. It is clearly a colorspace mismatch between VAAPI and the decode target surface. If disabling 10bpc happens in Ubuntu Mesa packages, then it is clearly someone using unofficial package builds of Mesa which have 10bpc enabled on supporting hardware."
1767312,2019-03-11 06:56:31 UTC,"Verified on bionic (fresh install and fully updated) that the bug is still present, and that the workaround in comment #16 works. It just took me a while to remember you need to:
  1. Install ubuntu-restricted-addons; and
  2. Use Xorg (because if you're in a Wayland session you hit bug 1720820 instead)."
1767312,2019-03-08 07:09:01 UTC,I thought I had reproduced this bug in the past when doing radeon testing. And my radeon testing does not involve AMDGPU or PPAs. Just vanilla Ubuntu on radeon was enough to reproduce it.
1767312,2019-03-08 11:18:40 UTC,"I, too, had this bug manifested on clean Ubuntu without PPAs and without AMDGPU."
1767312,2019-03-08 13:18:42 UTC,"disabling 10bpc solved the problem, thanks"
1767312,2019-02-03 23:18:21 UTC,example of good video properties
1767312,2019-03-11 07:00:04 UTC,"Also verified mpv works, but mpv isn't using VAAPI at all. It's using software decoding because ""VO does not support requested hardware decoder""."
1767312,2019-03-18 03:14:05 UTC,I hit this bug on Fedora 28 when using a third-party mesa build. Here's the ~/.drirc I used to fix this:
1767312,2019-09-10 02:30:15 UTC,Sounds like we have a semi-permanent workaround now:
1767312,2019-03-08 06:51:55 UTC,"Or as one user posted, the official AMDGPU Pro package, which also enables 10bpc."
1767312,2019-02-03 23:17:51 UTC,example of broken video properties
1767312,2019-02-03 17:44:38 UTC,"I'm experiencing this issue as well.  I have an RX550 video card, using Ubuntu's drivers."
1767312,2019-02-03 21:06:57 UTC,"10bpc is already disabled by default for every gallium driver, so it's surprising to hear that you'd need to flip the default manually in drirc"
1767312,2018-04-27 09:26:25 UTC,i attach a screenshot that shows the problem
1767312,2018-04-28 17:38:38 UTC,I am also affected by this bug on Ubuntu 18.04
1767312,2018-04-28 17:38:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767312,2018-04-29 21:00:32 UTC,"Could you include the output of the command ""dpkg -l | grep gstreamer""?"
1767312,2018-04-30 02:38:41 UTC,Please also try this as a workaround:
1767312,2019-02-03 23:15:33 UTC,"After testing from a well modified system, the issue appears after I install the amdgpu driver from AMD."
1767312,2018-05-22 09:21:26 UTC,you should file it upstream at
1767312,2018-04-30 07:25:28 UTC,"I've opensource amdgpu driver ""xserver-xorg-video-amdgpu/bionic,now 18.0.1-1 amd64 [installato]""
The problem occurs both on xorg and wayland, but on wayland i've a total black screen, i can hear only audio.
every h264 video that i've tried has this problem.
if i remove ""mesa-va-drivers"" package, the problem disappear"
1767312,2018-05-23 19:30:20 UTC,"i understand.
so i must report upstream on https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa
or not??"
1767312,2018-05-24 01:18:45 UTC,"It's reasonably likely the bug is in mesa, so yes worth reporting still."
1767312,2018-08-29 03:52:20 UTC,"I have tested on my Radeon RX480, also AMDGPU drivers, git snapshot from 20180829 from Padoka PPA, and this bug occurs with Totem as well."
1767312,2018-08-29 04:53:51 UTC,"For future reference, please don't mention PPAs in bug reports, or report bugs against packages installed from PPAs. Because we are unable to support them."
1767312,2018-08-29 11:03:34 UTC,"I only thought to mention the PPA to indicate that the bug still occurs even in fairly bleeding edge Mesa code. I also still think it's either something wrong with gstreamer-vaapi, or something that gstreamer-vaapi is doing different from what mpv does for the same exact video. It should probably be reported to upstream Mesa, just in case it really is their bug."
1767312,2018-12-17 04:21:38 UTC,"Adding a comment to indicate that this is a problem with the 10bpc support which is enabled in Radeon graphics. I am unsure if it is enabled in Intel's drivers, so that would explain why it does not occur there. Either VA-API is outputting wrong, the client library is outputting wrong, or all the player applications are wrong. Something appears to be matching the buffers to each other without a conversion, simply because both RGBA32 and RGBA10-10-10-2 have the same number of bytes per pixel, but clearly completely different structure."
1767312,2018-05-23 01:48:06 UTC,"I would have done that already, but have not verified if the problem really is in mesa-va-drivers."
1767313,2018-08-10 09:34:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/590717"
1767313,2020-01-27 14:12:59 UTC,"Change abandoned by Adriano Petrich (<email address hidden>) on branch: master
Review: https://review.opendev.org/590717"
1767314,2018-12-18 22:24:22 UTC,"Just by way of more info I was editing a gitolite conf file of 4096 lines with the following stats to render the syntax with the cursor at the end of the file
The total time taken was 5 seconds. By default redrawtime is set to 2 seconds so the 5 srconds taken represents a considetable drop off in performance.  It is true that 18.04 feels sluggish. Maybe Spectre malware fix slowdowns?"
1767314,2020-11-01 23:27:24 UTC,Any news about this?!
1767314,2018-12-18 23:32:55 UTC,Setting regexpengine=1 drops this back down to 1.4 seconds. So either this is the root cause of this particular slowdown (i.e. when syntax highlighting gitolite format files) or at least compensates for whatever is the root cause.  According to https://stackoverflow.com/posts/38521226 the default regexp engine changed with Vim 7.4. This was the version shipped with Trusty onwards so in theory was already in use on 14.04 and 16.04 ubuntu so something doesnt quite tie up
1767314,2018-12-18 22:04:14 UTC,"Further investigation with a recompiled version more recent than that shipped with 18.04 yields that syntax highlighting failure is caused by redrawtime being exceeded  - often triggered after using G to move to the end of the file. It is not possible to set ""syntax on"" manually at that point as it immediatetly gets disabled again unless you move to the start of the file with g."
1767314,2018-12-18 18:36:31 UTC,"The ""set nocompatible"" fix doesn't work on 18.04.1 LTS server.  The trigger condition appears to be a random operation and not repeatable.  Symptoms include loss of tab completion and syntax highlighting.   It is persistent through a re-edit of the same file.  The fault can be cleared by removing .viminfo until the next random occurence."
1767314,2018-12-18 18:44:06 UTC,The mis-interpretation of PC cursor keys when accessed vi ssh (as described in the discussion link above) is very remeniscent of trying to use vim.tiny not vim.basic (which server install defaults to).  Maybe this along with my above post will help characterise the bug.
1767314,2018-06-01 03:45:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767314,2018-06-01 03:45:40 UTC,Thanks! vim on Ubuntu 18.04 is so annoying!  lol
1767319,2018-06-25 12:44:36 UTC,The same thing happens when debootstrap is used under Debian 9.
1767322,2018-09-01 12:34:37 UTC,apport information
1767322,2018-09-01 12:34:39 UTC,apport information
1767322,2018-09-01 12:34:41 UTC,apport information
1767322,2018-09-01 12:34:42 UTC,apport information
1767322,2018-09-01 12:34:44 UTC,apport information
1767322,2018-09-01 12:34:46 UTC,apport information
1767322,2018-09-01 12:34:48 UTC,apport information
1767322,2018-09-01 12:34:49 UTC,apport information
1767322,2018-09-01 12:34:51 UTC,apport information
1767322,2018-09-01 12:34:32 UTC,apport information
1767322,2018-09-01 12:34:35 UTC,apport information
1767322,2018-09-01 12:34:56 UTC,apport information
1767322,2018-09-01 12:34:58 UTC,apport information
1767322,2018-09-01 12:35:01 UTC,apport information
1767322,2018-09-11 19:11:30 UTC,"My wireless connections works fine in Windows, but in Ubuntu it does't even connect and the message of error is as above: ""activation of network connection failed"".  I am using the version 18.04.01."
1767322,2019-06-06 06:08:46 UTC,"My network works fine. I am on a wired network connection. However, whenever I try to connect using VPN I get the ""Activation of network connection failed"" error message."
1767322,2019-09-30 01:59:25 UTC,Oddly i have had the same issue and I today i was getting annoyed so i went to wifi and switched from my 5G to 2.4 and it has been solid since. I will update if anything changes. Can finally not have to run a constant ping to keep it alive. on 5G when running a constant ping that would prevent the issue from happening
1767322,2019-12-17 19:55:16 UTC,"I am facing same issue while re-connecting to my TunnelBear VPN. TunnelBear VPN uses open-vpn service. I have configured VPN as per instructions by TunnelBear. And it works fine when connect first time, but after that when choose ""Turn Off"" from Netowrok-Manager then choose ""Connect"" again, then I see this same error. See snapshot from syslog:
Dec 17 20:45:25 KUMAR-PC NetworkManager[902]: <info>  [1576611925.5171] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,""TunnelBear India"",0]: VPN plugin: state changed: starting (3)
Dec 17 20:45:25 KUMAR-PC NetworkManager[902]: <info>  [1576611925.5172] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,""TunnelBear India"",0]: VPN connection: (ConnectInteractive) reply received
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2019
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: library versions: OpenSSL 1.1.1  11 Sep 2018, LZO 2.08
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: TCP/UDP: Preserving recently used remote address: [AF_INET]103.228.153.233:443
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: UDP link local: (not bound)
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: UDP link remote: [AF_INET]103.228.153.233:443
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: chroot will be delayed because of --client, --pull, or --up-delay
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Dec 17 20:45:27 KUMAR-PC nm-openvpn[6237]: [9563/server] Peer Connection Initiated with [AF_INET]103.228.153.233:443
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Option 'explicit-exit-notify' in [PUSH-OPTIONS]:3 is ignored by previous <connection> blocks
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: ERROR: Cannot ioctl TUNSETIFF tun0: Device or resource busy (errno=16)
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Exiting due to fatal error
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]: <warn>  [1576611928.9900] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,""TunnelBear India"",0]: VPN plugin: failed: connect-failed (1)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]: <warn>  [1576611928.9901] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,""TunnelBear India"",0]: VPN plugin: failed: connect-failed (1)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]: <info>  [1576611928.9902] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,""TunnelBear India"",0]: VPN plugin: state changed: stopping (5)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]: <info>  [1576611928.9903] vpn-connection[..."
1767322,2018-09-01 12:34:52 UTC,apport information
1767322,2018-09-01 12:34:54 UTC,apport information
1767322,2018-09-01 12:37:05 UTC,"re: my apport information just uploaded: I am using wireless as my primary network connection. If I turn off the wired ethernet connection, the nagging message stops popping up."
1767322,2018-09-01 12:34:30 UTC,apport information
1767322,2018-05-02 15:57:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767322,2018-05-03 08:00:19 UTC,"The log shows that DHCP requests timeout, are you sure the wifi you are trying to connect to is working? It looks like an infrastructure issue rather than an Ubuntu bug"
1767322,2018-05-03 09:26:43 UTC,"The WiFi is off, and I used the Ethernet connection ""everything OK"". It's still  popup shows incessantly Activation of network connection failed."
1767322,2018-05-03 10:08:03 UTC,My WiFi is working perfectly but I'm still getting these messages
1767322,2018-07-30 06:26:49 UTC,"Just for your information, I have the same issue on my laptop (HP ZBook G3) since I upgrade my OS to 18.04."
1767322,2018-08-02 13:59:38 UTC,Same issue on my Lenovo G50-80 running Ubuntu 18.04. Please let me know if there's any other information I can post that would help rectify this.
1767322,2018-09-01 12:34:34 UTC,apport information
1767322,2018-08-08 23:25:50 UTC,"Same issue here, my ethernet does not work!! Please fix ASAP!"
1767322,2018-08-03 10:23:26 UTC,Same issue on my Dell XPS 12 9Q33 after upgrading to Ubuntu 18.04.
1767322,2018-08-21 03:51:19 UTC,I am seeing this issue as well.
1767322,2018-08-30 05:58:43 UTC,I am also experiencing random yet frequent network error notifications of HP Elitebook G3.
1767322,2018-08-30 06:30:17 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1767322,2018-08-31 06:18:13 UTC,"I had the same problem and just found out that it was caused by a USB network interface that probably has been added when I plugged in a USB network device some time ago. The device has not been connected for months, yet apparently it's active in network manager, trying to get DHCP leases, which of course will fail."
1767322,2018-08-31 18:54:02 UTC,I think you're on to something Manfred. I removed my bluetooth connection and that solved the problem.
1767322,2018-08-31 19:27:23 UTC,I have the same issue. Other wifi networks connect immediately but one. When I first installed Ubuntu 18.04 it worked completely fine for a couple of days but now it doesn't. Please help.
1767322,2018-09-01 12:34:27 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  sbicknel   1590 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-07-22 (40 days ago)
InstallationMedia: Ubuntu 18.04 LTS ""Bionic Beaver"" - Release amd64 (20180426)
IpRoute:
 default via 192.168.2.12 dev wlp3s0 proto dhcp metric 600
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
 192.168.2.0/24 dev wlp3s0 proto kernel scope link src 192.168.2.203 metric 600
MachineType: ASUSTeK Computer Inc. K53SV
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
Package: network-manager 1.10.6-2ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=9d6809b8-6df1-4e23-8eaa-abb32b394780 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic  N/A
 linux-firmware                             1.173.1
Tags:  bionic
Uname: Linux 4.15.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo syslog
WifiSyslog:"
1767322,2018-09-01 12:34:28 UTC,apport information
1767322,2018-08-13 12:11:03 UTC,shiba satellite here same issue.... infact all my v18 do this I believe I seen same issue a previous releases years and years ago though...
1767323,2018-05-09 15:02:47 UTC,We usually don't recommend using DEBUG logging in production systems for this reason.
1767324,2018-06-10 08:47:53 UTC,"As per jacob's comment have added the tag and changed to Confirmed, Joseph do you know how this bug should be progressed? Where it should be forwarded upstream or what further debug work could be done? A test against a yet newer kernel probably wouldn't go amiss but not sure not doing that should put the bug back to Incomplete since then we may always be behind."
1767324,2018-06-19 17:50:36 UTC,Please find the first -rc kernel in [1] that introduces the issue:
1767324,2018-05-24 23:28:21 UTC,I have been trying various kernels to see if it would help. The battery consumption got (almost) back to normal under 4.17.0~rc3 but now with rc6 is down to 1:30h again.
1767324,2018-04-30 15:40:25 UTC,Does this bug go away if you boot back into the prior kernel version?
1767324,2018-04-27 10:30:11 UTC,This change was made by a bot.
1767342,2020-03-27 21:15:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767342,2020-03-30 02:18:38 UTC,"I think this is probably correct, unfortunately."
1767349,2018-04-27 13:06:50 UTC,"This was already logged, but I've marked the other as a duplicate since you've included the videos."
1767349,2018-04-27 15:19:01 UTC,"Videos about others EDAs could give us ideas about the dynamic of the tool.
For the first effort of this feature implementation will be necessary some change in the .net file to content this information.
After Pcbnew could just import the informations to track classes (of course, to a simple feature, but this could contain also information about with track are differential pars, length match, obligatory minimum clearance, ...).
On Eeschema will need some new graphical tool to symbolize this, like in the video."
1767349,2019-05-07 16:24:10 UTC,This might be partly related to https://bugs.launchpad.net/kicad/+bug/1749474
1767349,2019-05-07 17:19:16 UTC,"In the document
https://docs.google.com/document/d/1qvCH9aHwCzp5qtKTna4jJXuloNU0b96gAxAHSKPuXpU/edit#heading=h.ykrpi4h5njn
have the directives and comments."
1767349,2019-05-08 23:52:05 UTC,Linked with lp:1654571
1767352,2018-05-02 22:23:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/565906"
1767352,2019-03-22 16:19:11 UTC,"Hello,"
1767360,2018-05-19 23:43:02 UTC,"Rod B., the next step is to fully reverse commit bisect from kernel 4.4 to 4.16 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?"
1767360,2018-05-01 04:03:50 UTC,"Used kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/
It boots/works.
Added tag and changed status as requested. 1st time Launchpad user so hope I did it correctly."
1767360,2018-05-04 17:23:54 UTC,I discovered that reducing the BIOS setting for DVMT Pre-Allocated Memory below 512M gets around the bug. IE: The three problem kernels listed in this report will boot if DVMT Pre-Allocated is set less then 512M. As mentioned in this report kernels 4.4.0-116 and before worked fine with DVMT Pre-Alloc set to 512M.
1767360,2018-04-27 13:30:14 UTC,This change was made by a bot.
1767360,2018-04-30 15:37:56 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1767361,2019-01-11 13:39:57 UTC,"FWIW, I patch phpMyAdmin using these two lines after installation:
perl -p -i -e ""s/\[\'select_expr\'\] == 1\)/\[\'select_expr\'\]\) == 1/g"" /usr/share/phpmyadmin/libraries/sql.lib.php
perl -p -i -e ""s/ count\(/ count\(\(array\)/g"" /usr/share/phpmyadmin/libraries/plugin_interface.lib.php"
1767361,2019-04-27 09:29:15 UTC,"Hi all,"
1767361,2019-02-19 20:31:10 UTC,Line #613 of sql.lib.php should be:
1767361,2019-01-09 09:27:54 UTC,Hi is it possible to solve it's verry difficult to use phpmyadmin on ubuntu 18.04 we have always a modal with the errors. We use highly phpmyadmin on many servers.
1767361,2019-04-27 16:22:39 UTC,"The attachment ""Improve PHP 7.2 compatibility"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1767361,2018-07-24 00:42:55 UTC,"I agree with Andy, quit talking and fix this stupid big"
1767361,2019-09-25 12:37:46 UTC,We are working on packaging the latest version of phpMyAdmin at Debian (https://salsa.debian.org/phpmyadmin-team/phpmyadmin/issues/1)
1767361,2019-10-20 17:06:13 UTC,I can confirm that the following sequence of commands worked on both of my 1804 LTS servers that were affected by this issue...
1767361,2020-08-19 21:23:50 UTC,"It says this is fixed/released in Ubuntu.
I'm running Ubuntu 18.04.5 LTS
I'm still seeing phpmyadmin Version information: 4.6.6deb5"
1767361,2020-08-20 14:49:56 UTC,"I re-read William Desportes's comment #22 and the fix is in Debian's buster-backports repository.
It does not appear to be in Ubuntu's bionic-backports."
1767361,2018-11-21 08:56:18 UTC,I have the same problem with export and click on a table. Please could you upgrade the package version ?
1767361,2020-08-20 16:51:17 UTC,"Hi Austin,"
1767361,2019-08-13 07:23:48 UTC,"We should not be offered just a patch, but a php 7.2 compatible phpmyadmin release, please!"
1767361,2018-11-14 07:41:32 UTC,"@Maxwell Dreytser:
If you think that this is a 20 minute job, please help solving it, e.g. by creating a package in a PPA."
1767361,2018-07-23 23:30:00 UTC,The latest version is https://files.phpmyadmin.net/phpMyAdmin/4.8.2/phpMyAdmin-4.8.2-all-languages.tar.gz - just grab it from phpMyAdmin's site and drop it in your /var/www/html tree.
1767361,2018-09-24 19:23:01 UTC,I agree with Andy's sentiment.  I run phpmyadmin 4.8.3 on several 18.04 systems.  Once the tmp directory is defined and the secret error defined its good to go.  For a LTS release this should have been fixed.
1767361,2018-09-24 19:02:45 UTC,"Are you guys still kidding me?!
Is it a motherfucker problem to make a deb package for phpmyadmin 4.8.x?
For 4 months old LTS release!"
1767361,2018-09-14 15:36:32 UTC,This is getting to be a pain every server install :-(
1767361,2018-09-14 15:17:58 UTC,I'm running a VPS with Ubuntu 18.04 and experience similar problems and get quite long error messages (see screenshot). It's pretty annoying to get those errors when switching panels and a maybe a beginner user would be get very scared to use the app afraid that could mess up the database operations...
1767361,2018-07-24 00:13:13 UTC,"Would you guys finally make fucking LAMP working on LTS?
That was a fuckup. Just fix it."
1767361,2020-09-15 14:19:56 UTC,"Hi William,
   I realize I never responded.
   I ended up using the PPA on Ubuntu 18.04 and it's working."
1767361,2018-06-21 07:42:56 UTC,Same as Michael Bolli : I still get many warnings.
1767361,2018-06-15 07:59:58 UTC,The fix only removes some of the warnings. In the table/database export tab for instance I still get many warnings.
1767361,2018-05-08 14:09:11 UTC,worked for me :-) thanks Sean
1767361,2018-05-08 13:41:17 UTC,The fix outlined in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890595#15 resolves the warnings.
1767361,2018-05-01 05:13:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767361,2021-02-09 19:44:24 UTC,"Hi,"
1767361,2018-10-30 18:13:50 UTC,Fast forward to End of October 2018 and this is STILL an issue.
1767361,2021-02-09 19:30:54 UTC,It is now 2021 and the bug is still there.
1767363,2020-09-15 12:23:19 UTC,This is actually super awkward as locking _disconnect_volume and/or _should_disconnect_target isn't enough here as we are reliant on the compute manager / block device actually deleting the attachments. Anyway here's the current list of places where we call _disconnect_volume in the libvirt virt driver:
1767363,2020-09-15 12:47:41 UTC,I think the better option here is to replace calls to _disconnect_volume with calls to block_device.detach():
1767363,2020-09-15 11:49:41 UTC,_disconnect_volume doesn't delete host volume attachments so the worst thing that can happen with this race is that the underlying volume connection isn't cleaned up on the host when multiple requests race each other. I'll throw a volume_id specific lock around the method to avoid this.
1767363,2018-05-28 05:19:58 UTC,But here I would like to mention 1 more thing that above case will occur only when we try to detach last instance from the volume. It will not occur if we have 4 instances attached to a single volume and we try to delete two instances from it.
1767363,2018-05-28 04:44:47 UTC,"Yes it is a bug, i have tested on my system. below are the reproducing steps :"
1767364,2018-05-01 02:06:35 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1767369,2018-04-27 14:44:46 UTC,"The update-manager has a lot more functionality to support smooth upgrades from one Ubuntu version to the next. Until gnome-software supports all of that, it would cause problems for Ubuntu to offer upgrades via gnome-software."
1767369,2018-04-28 05:02:35 UTC,"I use the update manager too, but implementing a manual upgrade into the Software Center as an optional way to upgrade instead would be a great option for users to upgrade at a later date if they choose to hold off on it, but not wait the full LTS cycle."
1767376,2018-05-02 16:27:46 UTC,Thanks. I will do this as fast as I can.☺
1767376,2018-05-01 19:17:29 UTC,"Hi Fy, probably it's quickest if you request the CVE directly from MITRE using:"
1767376,2018-05-01 02:10:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1767376,2018-05-05 07:38:32 UTC," This is a redundant  vulnerability that has been reported and fixed in
1.13.0 .
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17858"
1767376,2018-04-27 17:44:19 UTC,Thanks for reporting this vulnerability. Are you planning on requesting a CVE id for it?
1767376,2018-04-30 12:20:47 UTC,"Yes, it would be great if a CVE id could be signed. But I am not familiar
with the report prodcedure.  Should I request a CVE id by myself, or leave
this to you？"
1767378,2019-12-23 16:42:38 UTC,Here is the new documentation: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=c400c7e67921c1ecf8048be120d618166435907e
1767378,2019-12-23 18:02:56 UTC,https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=6e3fcbe9741c40414391c91bb5d19283403814bc
1767378,2019-12-30 22:54:03 UTC,"Thanks for this re-write, Lynn!  It looks good.  I went ahead and pushed it to master and rel_3_4, along with a quick follow up commit that fixed a link."
1767378,2019-12-31 13:26:02 UTC,Will do thanks.
1767386,2019-02-18 17:44:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767389,2019-11-09 17:41:48 UTC,Install a proprietary NVIDIA driver.
1767389,2020-05-17 15:13:13 UTC,Hello. I tried installing a proprietary Nvidia driver but the result was even worse: my second screen wasn't even detected.
1767389,2020-07-14 11:33:59 UTC,"I had the problem using both the nouveau driver (black screen with only a mouse pointer) and the nvidia driver (screen was not detected at all). I suspected the problem was being cause by secureboot (like so many problems are), so I disabled in via BIOS.....and now the second screen works perfectly."
1767390,2018-09-10 06:41:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767398,2018-05-24 20:30:26 UTC,This bug was fixed in the package linux-oem - 4.15.0-1006.9
1767398,2018-05-22 12:02:06 UTC,All tasks have been completed and the bug is being set to Fix Released
1767398,2018-05-21 23:58:49 UTC,This bug was fixed in the package linux-oem - 4.15.0-1006.9
1767398,2018-05-10 07:41:33 UTC,"The upload has a lot of leftover patchfiles laying around the source, please re-upload after cleanup."
1767398,2018-05-15 09:51:24 UTC,We don't run regression-testing on this.
1767400,2018-05-14 03:30:44 UTC,"4.15.0-1007.7 - gcp
Regression test CMPL, RTB."
1767400,2018-05-21 23:58:20 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1008.8
1767400,2018-05-22 13:01:21 UTC,All tasks have been completed and the bug is being set to Fix Released
1767400,2018-05-24 20:30:15 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1008.8
1767401,2018-04-30 15:04:02 UTC,boinc-client seems to have been uninstalled before boinc-app-eah-brp although the later package depends a tool provided by boinc-client to successfully purge.
1767401,2018-04-30 15:04:26 UTC,Its possible this is a bug in the package manager synaptic rather than in boinc-app-eah-brp.
1767403,2018-05-21 23:57:53 UTC,This bug was fixed in the package linux-aws - 4.15.0-1009.9
1767403,2018-05-24 20:30:36 UTC,This bug was fixed in the package linux-aws - 4.15.0-1009.9
1767403,2018-05-22 12:32:06 UTC,All tasks have been completed and the bug is being set to Fix Released
1767403,2018-05-18 12:32:51 UTC,"4.15.0-1008.8 - aws
Regression test CMPL."
1767403,2018-05-17 10:57:24 UTC,Hardware Certification is not run for cloud kernels. Setting certification-testing to 'Invalid'.
1767408,2018-05-22 13:00:06 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1011.12
1767408,2018-05-22 14:00:26 UTC,The package has been published and the bug is being set to Fix Released
1767408,2018-05-24 20:30:42 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1011.12
1767409,2018-05-10 08:22:39 UTC,"4.15.0-1009.9 - kvm
Regression test CMPL, RTB."
1767409,2018-05-21 23:58:34 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1010.10
1767409,2018-05-22 12:32:50 UTC,All tasks have been completed and the bug is being set to Fix Released
1767409,2018-05-24 20:30:31 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1010.10
1767410,2018-05-10 04:34:30 UTC,Mark this task as incomplete for the missing i386 tests.
1767410,2018-05-14 11:07:21 UTC,Hardware Certification is not run on -edge kernels.
1767410,2018-05-22 12:33:11 UTC,All tasks have been completed and the bug is being set to Fix Released
1767410,2018-05-15 09:51:26 UTC,Mark regression testing fix released as none of the bugs are regressions against the latest releases.
1767416,2019-01-11 01:03:57 UTC,"To note for people who work on this, the upgrade script sets that value to FALSE because the default value in stock Evergreen per 950.data.seed-values.sql also says they are FALSE."
1767416,2019-07-01 19:12:08 UTC,"Just confirming that we are seeing this in 3.1 here in SCLENDS. Example attached: as you can see, it can get pretty difficult to read when the subject headings are complex."
1767416,2019-07-01 19:34:27 UTC,Apologies-- my comment #5 was intended for a different bug.
1767416,2019-01-10 22:15:43 UTC,"After upgrading to 3.1.8 we are seeing a similar if not the same issue.  We are seeing only one 505 field display.  All the subfields of the single 505 display, but not the additional 505 fields."
1767416,2018-05-10 19:10:32 UTC,"Kathy, could you send the MARC contents (from the HTML display, or maybe screenshots of either the MARC editor or flat editor), or links to the records in a system?  It likely is just a simple index definition adjustment.  Of course, a partial reingest will be needed, but we can do just the one definition, IIRC."
1767416,2018-05-24 15:28:25 UTC,I've pasted the MARC record from the public view here - https://pastebin.com/CBJGzDc4
1767423,2018-04-30 14:20:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767428,2018-04-28 10:56:32 UTC,"I've managed to get to the correct state by variously switching between hidpi/lodpi and cycling through a few different panel configurations, with the last one before it became unbroken being cupertino. I can't now reproduce the problem again to find a causal scenario. Sorry :-("
1767428,2018-09-09 21:40:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767431,2019-09-16 11:22:53 UTC,"It just doesn't make sense to have a search as soon as you start typing, that's what the search button and Ctrl+F are for. It hinders workflow when wanting to get to files/folders quickly by typing initial letters of it."
1767431,2021-02-18 21:30:06 UTC,"This is really annoying, counter-intuitive behaviour. At the very least the old behaviour should be restorable by a setting."
1767431,2020-11-02 03:15:54 UTC,"Hi. I finally upgraded to 18.04 and Nautilus without type-ahead find is extremely limiting when it comes to file/folder navigation. I can't even fathom why it would be dropped. But if search is now the default action for when one starts typing, there should be a way to disable that, or enable type-ahead find, if not in an easily-found, user-friendly way, then at least as an option in Preferences. I know there is a patched version available, but I'd rather not have upgrade headaches which can arise from having patched versions of major system apps, so am just adding my voice to the countless others on the web begging for action on this."
1767431,2019-09-22 18:42:03 UTC,"Issue has a patch, so wondering: What are the decision criteria for bringing the patch into 18.04, perhaps backports? Does it have to happen upstream (through persuasion of Gnome devs)?"
1767431,2019-08-02 23:57:23 UTC,"This is super annoying, and very unexpected behaviour change particularly for users coming from Windows. There is a patch to change the behaviour back here: https://launchpad.net/~lubomir-brindza/+archive/ubuntu/nautilus-typeahead"
1767431,2019-03-07 21:33:59 UTC,"I don't think this should be marked as a duplicate of bug #1164016.  That bug was successfully fixed, but this one is a new regression that requires a different patch.  Since #1164016 is marked as Fix Released, a new bug should be opened for this new regression."
1767431,2018-05-01 08:41:34 UTC,"The attachment ""The second patch for 18.04 after applying the Arch patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1767431,2018-05-01 02:47:13 UTC,"@seb128, that URL is for git clone, the HTML page for the repo is at [1]. Also, to compile nautilus with the patch, there needs another small patch after applying the Arch patch, to remove a naming conflict introduced in an Ubuntu patch in 18.04. I attached my patch."
1767431,2018-04-30 22:06:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767431,2018-04-30 13:43:25 UTC,"Thank you fo your bug report, the patch url you gave doesn't seem valid though?"
1767431,2018-12-09 11:36:11 UTC,"This issue is much broader and was already earlier mentioned than the first provided link to askubuntu, see https://askubuntu.com/q/275883/854911  And given the amount of upvotes for that question and for the answers I think it is fair to reconsider this 'feature'."
1767440,2018-08-19 11:14:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767440,2019-03-30 10:36:12 UTC,I had a similar problem when installing android-sdk with --install-suggests.
1767446,2018-05-08 02:46:01 UTC,(P.S.)
1767446,2018-05-07 17:00:15 UTC,"(P.S.)
I rewrote the procedure in an easy-to-understand manner."
1767446,2018-05-07 17:28:00 UTC,(P.S.)
1767446,2018-12-04 18:12:13 UTC,"I have a similar problem with pluma, and vim in a terminal, on my ubuntu mate 18.04, switching from my default language to mozc with Japanese.
Also, with AbiWrite I have the impression the behaviour is a bit different (but I've only tried once): I can switch languages but when I type the text appears on a tiny window outside the editor and there seems to be no way to insert it in the editor window.
I can try more tests, but given the necessary ""hard reboot"", I fear for the integrity of my system.
Perhaps switching languages in an ""empty"" (ie with no active text editor) workspace?
I'd really like to see this fixed.
ありがとうございます。"
1767451,2018-04-27 18:09:18 UTC,"I figured out the problem. I logged the event in the run method of GlobalKeyBinding, and for most key events this is the kind of object I got:"
1767451,2018-04-27 18:16:13 UTC,https://github.com/robint99/mate-dock-applet/pull/133
1767452,2018-05-04 07:07:26 UTC,Cool! I'll try this weekend :D
1767452,2018-05-19 23:32:04 UTC,"Frew Schmidt, please address all of the following:"
1767452,2018-05-30 09:42:01 UTC,"Christopher, I believe the solution is in the redhat bug mentioned earlier."
1767452,2018-05-02 15:22:04 UTC,"Good news! the 4.17.0-rc3 kernel *fixed this issue*!   You can get it here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3/  I only tried undocking once so far but hey, I was able to undock and redock and there was no oops in dmesg.  I will likely try again later throughout the day for various meetings.  Will update here if I have any problems."
1767452,2018-05-30 14:18:20 UTC,"I intend to do this, but I expect it to eat up a few hours of time so
just haven't gotten around to it."
1767452,2018-05-30 14:33:58 UTC,I guess this is a dupe of LP: #1768852.
1767452,2018-05-30 13:50:18 UTC,"Anders Kvist:

>""Christopher, I believe the solution is in the redhat bug mentioned earlier.

https://bugzilla.redhat.com/show_bug.cgi?id=1565131"""
1767452,2018-05-02 13:29:16 UTC,Same.
1767452,2018-05-01 06:34:09 UTC,"I haven't had a single undock that worked, but I only tried with the 18.04 live installer, so guess that kernel already may be behind..."
1767452,2018-05-01 17:55:48 UTC,I just realized why I thought this was not predictable.  The system continues to function just fine after the Oops *until* I close my laptop. Once I close my laptop the whole thing freezes and does not recover.  Attaching one last kernel log and then will leave it alone till someone asks for more detail.
1767452,2018-05-02 08:53:55 UTC,"Yea, I cannot do a shutdown, it will hang during something with thunderbolt and I have to do a hard poweroff :/"
1767452,2018-05-01 04:33:43 UTC,I reproduced this this afternoon with the latest stable kernel (4.16.6.)  See attached subset of the kernel log.  I'll try with 4.17 tomorrow.
1767452,2018-04-30 16:59:22 UTC,"I do have a Thunderbolt dock, but it is not so trivially reproducable
for me.  Most of the time I can undock and redock just fine.  I
suspect I did something in an unusual order, like closed my laptop and
*then* undocked, instead of undocking first."
1767452,2018-04-30 16:52:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767452,2018-04-30 16:49:52 UTC,"I assume you have a Thunderbolt dock? I see the same, happens each time after undocking and then the dock won't work anymore until a reboot."
1767452,2018-04-27 17:36:54 UTC,Here's the above in an (unmunged) attachment
1767453,2019-04-25 12:29:15 UTC,"Even though comment #2 claims that this bug is not related to bug 1764848 it may actually be related to bug 1764848. It depends on the content of the autofirma package that apparently triggers this situation, it may be that the package contains duplicate certificates."
1767453,2019-04-25 12:23:14 UTC,@mquiros: Where can I download the autofirma package? I just ran into another source of certificates that have the same issue and I want to investigate.
1767453,2019-04-24 18:33:56 UTC,"I think I have found the culprit. It is a package called ""autofirma"", distributed by the Spanish Administration to perform digital signatures with the official certificates provided by the government.
Apparently, there is some kind of incompatibility between the files generated by this package and the postinstallation script of this version of ca-certificates.
I have just removed (purge) the autofirma package, then update ca-certificates to 20180409 without any problem and, after that, reinstalled autofirma (probably I may need to uninstall it again when another ca-certificates version comes out).
As autofirma is not an ubuntu-provided package, this should not be considered a bug after all. In any case, the information may be useful for any other Spanish user finding the same problem."
1767453,2018-11-29 15:47:12 UTC,"No success in my case (difference with Maurice report). Tried again today to upgrade (via dpkg -i) to 20180409 and got an error message saying that post-installation script produces an output status of ""1"" (this means error when executing the postinst script, doesn't it?). Package left unconfigured and 20170717~16.04.1 needs to be reinstalled to get a system without broken packages.
Is there some way to get more verbose information about what is going wrong with the post installation script?"
1767453,2018-11-28 16:07:40 UTC,Same here. I downloaded ca-certificates_20170717~16.04.1_all.deb from https://packages.ubuntu.com/xenial/all/ca-certificates/download
1767453,2019-04-25 14:18:38 UTC,The autofirma package can be downloaded from:
1767453,2018-09-10 17:01:53 UTC,"The bug appeared while upgrading from Ubuntu 16 to Ubuntu 18. It is a very serious bug, since many other packages depend on ca-certificates and were left unconfigured. Lots of error messages in the screen.
When the upgrade finished, the system was left in a very bad situation with so many non-configured packages. No workable reboot-shutdown button, not functioning menus ... If moving to a virtual terminal (Alt-F1) the virtual console did not work either, so the configuration error of ca-certificates is a really serious bug.
I did not dare to perform a hard poweroff and poweron because I was not confident that the system was going to be able to boot at all.
Fortunately enough, right clicking in the screen worked and I was able to open a terminal. From that terminal, I keyed firefox (not accesible through non-working menus) and downloaded from ubuntu archive the version 20170717 of ca-certificates and install it replacing the buggy 20180409 using dpkg -i.
After this, I performed
dpkg --configure -a
and all not-fully installed packages got correctly configured.
I had to poweroff via the button (no other choice) and when powering on again, Ubuntu 18 appeared with no other issue so far."
1767453,2018-04-27 20:40:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767453,2018-04-27 18:23:20 UTC,"The fixed version of libssl is installed, and the error message is not about a duplicate certificate so this is not a duplicate of bug 1764848."
1767453,2018-09-10 17:06:44 UTC,I also tried to install version 20180409 after Ubuntu 18 was already working and the error is still there. It is not a problem of the upgrade procedure but a problem of the package itself.
1767454,2018-05-05 18:01:15 UTC,"I can not confirm.
My two computers run Arch Linux
pc A: kde plasma 5.12.5, frameworks 5.45, dolphin 18.04, samba 4.8.1
pc B: Gnome 3.28.1, nautilus 3.28.1, samba 4.8.1"
1767454,2018-05-06 00:32:32 UTC,*** Bug 393880 has been marked as a duplicate of this bug. ***
1767454,2018-05-10 18:32:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767454,2018-06-23 10:08:22 UTC,"I can confirm this behavior with openSUSE Leap 15.0 (Plasma 5.12.5, Frameworks 5.45.0) on the client and Samba 4.6.14 on the server."
1767454,2018-07-20 21:06:01 UTC,*** Bug 392803 has been marked as a duplicate of this bug. ***
1767454,2018-07-20 21:06:02 UTC,*** Bug 388000 has been marked as a duplicate of this bug. ***
1767454,2018-07-20 21:14:38 UTC,Migrating information from a duped bug:
1767454,2018-09-17 14:28:30 UTC,*** Bug 398698 has been marked as a duplicate of this bug. ***
1767454,2018-11-14 09:15:57 UTC,"The issue is fixed with gvfs 1.38.1 in disco, that version is being SRUed now to cosmic and the patch backported to a bionic SRU"
1767454,2018-12-07 12:55:18 UTC,"Git commit 55eb68ff63646050311f8b689752ad500246c916 by Harald Sitter.
Committed on 07/12/2018 at 12:55.
Pushed by sitter into branch 'master'."
1767454,2019-03-10 17:37:23 UTC,"I have to say that this bug is a dissapointment. The whole samba support in Ubuntu since 18.04 is abysmal. Prior to this, I was able to access shares with no problems, now there is a problem. The bug has been posted one year ago. After changing the protoocol, I discovered I needed to change the interface too, because samba somehow insists on using virtbr0."
1767454,2019-03-10 19:46:42 UTC,What's described in comment #32 is being tracked in bug https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322
1767454,2019-03-26 02:52:58 UTC,I wanted to reconfigure an old PC to be a music server connected to our HIFI.  It took 3 days and 7 attempts to successfully install 18.04 due to an issue with installing on PC with multiple drives.  It refused to correctly write the GRUB boot loader to the same partition it itself installed Ubuntu to. I had to strip out all the drives to get round the problem to now discover I cannot connect to the Music media on my main Windows 10 PC due to this SMB issue.  I got round it by the connect to server option and bookmark option but Kodi cannot see the share or index the Music.  Now I'm off to Kodi support.
1767454,2019-03-26 12:23:18 UTC,This will be addressed shortly via bug #1778322
1767454,2019-05-21 04:07:15 UTC,"(In reply to Bernd Lachner from comment #5)

> I can confirm this behavior with openSUSE Leap 15.0 (Plasma 5.12.5,
> Frameworks 5.45.0) on the client and Samba 4.6.14 on the server.
>
> Dolphin shows nothing with smb:// if I go to the share directly in Dolphin
> it works. With smbtree the shares are showing correctly.
>
> The following file on the client helps, thank you:
> ~/.smb/smb.conf
> [global]
>     client max protocol = NT1
>
> But it would be better do solve this issue in the smb kio plugin directly.
"
1767454,2018-05-03 21:58:23 UTC,I mean to list shares NT1 is needed with smbtree.
1767454,2020-11-29 01:43:03 UTC,Ubuntu 20.04 LTS samba 2:4.11.6+dfsg-0ubuntu1.6
1767454,2018-09-21 16:01:37 UTC,The GNOME folks just forced the use of SMB1/NT1 for discovery purposes in Nautilus/GVFS: https://gitlab.gnome.org/GNOME/gvfs/merge_requests/12/diffs
1767454,2018-05-03 21:12:48 UTC,"On Thu, May 3, 2018 at 5:54 PM, tony <email address hidden> wrote:"
1767454,2018-10-17 10:02:48 UTC,*** Bug 399906 has been marked as a duplicate of this bug. ***
1767454,2018-05-03 19:42:00 UTC,"Defaults for xenial (samba 4.3.11):
  client min protocol = CORE
  client max protocol = default (which is NT1 in this version of samba)"
1767454,2018-03-28 11:37:42 UTC,"Dolphin doesn't show any samba share.
smb:// and smb://workgroup/ are empty."
1767454,2018-03-28 11:40:01 UTC,"Created attachment 111699
journalctl of samba 4.7.6"
1767454,2018-04-27 19:24:39 UTC,"Since syslog said:
Called ""net usershare info"" but it failed: Failed to execute child process “net” (No such file or directory)"
1767454,2018-04-29 05:35:39 UTC,"Thanks for the explanation, but that feels like a real regression to me! Just last week with 17.10 I was showing some people running Windows how easy it was to browse and connect to Windows servers with Nautilus. Now, with 18.04, they again have to jump through hoops and know cryptic smb URLs to connect to them..."
1767454,2018-04-29 20:35:50 UTC,"@tony, could you give some details about that SMB3_11 setting? Is that a known upstream issue/documented somewhere?"
1767454,2018-04-29 20:36:52 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=780958 looks like the same issue
1767454,2018-05-03 20:54:04 UTC,"Andreas, it looks like to me that smbtree still needs NT1 to list shares, as people harden there servers and disable less secure protocols it will break browsing for shares."
1767454,2018-04-29 20:40:09 UTC,"The upstream report claims it has been fixed in samba 4.8, we might have to look for a change to backport there
Another reference, https://bugzilla.samba.org/show_bug.cgi?id=12876"
1767454,2018-04-28 11:56:24 UTC,Nautilus is now using protocol SMB3_11 in Ubuntu 18.04 and that breaks browsing shares.
1767454,2018-04-30 15:58:54 UTC,"I added the extra file ~/.smb/smb.conf
    [global]
        client max protocol = NT1"
1767454,2018-04-30 19:09:36 UTC,Fresh 18.04 install and  install of smbclient.
1767454,2018-04-30 20:45:44 UTC,"Do your servers show up under ""Networks"" in ""other locations"", just alongside the ""Windows Network"" folder? My NAS does show up there, but it could be because of some sort of zeroconf broadcast, not smb. My ""windows network"" is also empty, I'm just checking if newer windows installs would show up outside of ""windows network"" like my NAS does."
1767454,2018-05-01 00:50:53 UTC,"No, in 18.04 my servers do not show up anywhere."
1767454,2018-04-30 12:41:36 UTC,"After you install smbclient, can you please just run the ""smbtree"" command:"
1767454,2018-05-03 17:09:03 UTC,"Sebastien Bacher, I am not sure if it is documented anywhere?"
1767454,2018-05-03 17:10:45 UTC,What are your servers? I can't get windows 10 or 2016 server to show up not even in artful (17.10).
1767454,2018-05-03 17:43:19 UTC,"Andreas Hasenack, my server is nas4free (https://www.nas4free.org/) running Samba version 4.7.6"
1767458,2018-04-27 20:54:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767464,2018-04-27 19:27:33 UTC,"/tmp is going to get pruned by systemd-tempfiles but there's no reason to leave those around.  There's some indirection going on where when the netplan cli loads, it's getting instances of all of the commands, but when apply or generate run, the try_config handler doesn't get to run, and subsequently the cleanup method is never called."
1767464,2018-04-27 20:54:44 UTC,I've put up a PR to address this.
1767464,2018-07-20 03:49:56 UTC,"That has been merged, marking as Fix Committed."
1767482,2018-04-27 19:13:29 UTC,"Tested with a fresh installation of the Kubuntu 18.04 Beta + ""sudo apt-get dist-upgrade"" after official release of (K)Ubuntu 18.04."
1767482,2018-05-14 01:41:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767493,2019-11-17 04:17:42 UTC,[Expired for gcc-5 (Ubuntu) because there has been no activity for 60 days.]
1767493,2019-09-17 10:39:46 UTC,I took a look at this and am unable to reproduce. The test program compiles and ran fine on an Ubuntu 16.04 system:
1767493,2018-05-24 18:57:51 UTC,Rumours suggest this is a valgrind issue.
1767493,2019-09-17 10:41:46 UTC,"I do not have access to and Orange Pi or NanoPi Duo. I suggest trying again with an updated toolchain and see if you still have the issue, and if so, specify the gcc invocation and board information. Thanks!"
1767497,2018-12-03 19:20:13 UTC,"This appears to perhaps be fixed in Ubuntu 18.10 with all updates applied. Don't know whether that means it's also fixed in 18.04, since I no longer run 18.04 anywhere and therefore can't test it."
1767505,2018-05-19 20:11:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767505,2019-01-30 19:50:14 UTC,"Same here, Ubuntu 18.04.1, Rhythmbox 3.4.2-4ubuntu1."
1767505,2019-02-25 06:06:16 UTC,Any solution?
1767505,2019-10-15 19:17:46 UTC,I also have this...
1767505,2019-10-15 19:46:33 UTC,"I pulled the source code and fixed it myself. I tried to push it back up, but I guess they were not interested."
1767505,2020-03-17 17:27:12 UTC,"I see it on Rhythmbox 3.4.2, Ubuntu 18.04.4 LTS"
1767505,2020-03-24 08:56:32 UTC,"Seeing the issue still with Version: 3.4.2-4ubuntu1. Radio streams just stop with the ""internal data stream error"". Other players such (TuneIn app) play the same stations/URLs just fine.
It takes at most a few minutes for the error to occur so it renders Rhythmbox completely useless as online radio player."
1767505,2020-03-25 09:35:12 UTC,"Seeing the issue still with Version: 3.4.2-4ubuntu1. Radio streams just stop with the ""internal data stream error"". Other players such (VLC, TuneIn app) play the same stations/URLs just fine.
It takes at most a few minutes for the error to occur so it renders Rhythmbox completely useless as online radio player."
1767505,2020-06-14 22:15:52 UTC,I cannot reproduce this issue on the latest Ubuntu 18.04.4 LTS ( rhythmbox - 3.4.2-4ubuntu1 ) with the default radio stations shipped with rhythmbox. I tried with and without crossfade.
1767505,2020-08-15 04:17:28 UTC,[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]
1767509,2018-05-04 02:54:33 UTC,Hello? Anybody?
1767514,2018-04-28 00:36:11 UTC,It occurs to me that we could potentially encounter the same issue at the next layer down with any provider resources contained in the scaled unit. I'm not sure what the answer to that is. Duplicating all of the files and rewriting the child templates/environments to map all of the right versions seems like it would get out of hand quite quickly.
1767516,2018-05-30 21:56:42 UTC,We have 2 related JTAC cases:
1767516,2018-04-27 22:09:58 UTC,"Contrail version is 3.2.9
aio50 not enabled RBAC yet.  But another aio71 with RBAC enabled also see this same issue."
1767516,2018-06-01 16:42:42 UTC,2018-0411-0626: floating ip pool being shared but invisible in 2nd tenant
1767516,2018-04-27 21:47:24 UTC,Problem could be seen on JTAC local testbed AIO50:
1767518,2018-07-13 08:50:11 UTC,"This might be a wild shot, but if it's a Fedora specific issue, maybe it's related to [1], though inkscape itself is not listed in those identified packages. I can be complete wrong, it only reminded me of this [1] message. I'm sorry if this would mislead anyone."
1767518,2018-08-06 12:46:39 UTC,Installing ttf-dejavu on alpine does fix it.
1767518,2018-08-01 03:49:14 UTC,*** Bug 1610607 has been marked as a duplicate of this bug. ***
1767518,2018-07-21 13:27:25 UTC,*** Bug 1607075 has been marked as a duplicate of this bug. ***
1767518,2018-07-21 10:15:49 UTC,"- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11), using the command:"
1767518,2018-07-19 21:59:21 UTC,Inkscape version: 0.92.2-r1 on alpine linux
1767518,2018-07-08 23:28:42 UTC,"With July's inkscape-0.92.3-2.fc28.x86_64 I no longer get an immediate crash working within a text object (yay!). But I just experienced a crash with
  stl_vector.h:950: std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _... : Assertion '__builtin_expect(__n < this->size(), true)' failed.
in the console and
  std::__replacement_assert(char const*, int, char const*, char const*) in the backtrace
possibly the same as comment #13 and comment #32, even though comment #40 reports this version fixed it."
1767518,2018-06-27 13:42:35 UTC,*** Bug 1595764 has been marked as a duplicate of this bug. ***
1767518,2018-07-08 09:34:15 UTC,Similar problem has been detected:
1767518,2018-07-05 11:37:48 UTC,"This version fixed my problem too:
$ rpm -q inkscape
inkscape-0.92.3-2.fc28.x86_64"
1767518,2018-07-04 08:06:48 UTC,"(In reply to Rafal from comment #38)

> A recent patch on Fedora 28 fixes this problem for me:
> $ inkscape --version
> Inkscape 0.92.3 (2405546, 2018-03-11)
"
1767518,2018-07-04 07:45:36 UTC,"A recent patch on Fedora 28 fixes this problem for me:
$ inkscape --version
Inkscape 0.92.3 (2405546, 2018-03-11)"
1767518,2018-07-02 01:00:17 UTC,*** Bug 1597066 has been marked as a duplicate of this bug. ***
1767518,2018-06-28 10:58:37 UTC,"A workaround is to install the Inkscape flatpak from Flathub, though that is currently an earlier version 0.92.2. If necessary you can manipulate text in the flatpak Inkscape, then copy and paste it into the Fedora version."
1767518,2018-09-22 21:14:35 UTC,*** Bug 1631986 has been marked as a duplicate of this bug. ***
1767518,2018-07-08 09:40:00 UTC,Similar problem has been detected:
1767518,2018-09-25 15:22:56 UTC,Similar problem has been detected:
1767518,2018-11-05 10:57:34 UTC,Similar problem has been detected:
1767518,2018-09-30 20:08:48 UTC,*** Bug 1634444 has been marked as a duplicate of this bug. ***
1767518,2019-05-28 23:46:38 UTC,"Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1767518,2019-05-02 19:47:41 UTC,"This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'."
1767518,2019-03-12 17:35:11 UTC,Similar problem has been detected:
1767518,2018-11-26 12:25:59 UTC,*** Bug 1653271 has been marked as a duplicate of this bug. ***
1767518,2018-11-17 14:12:25 UTC,Similar problem has been detected:
1767518,2018-11-13 12:08:34 UTC,Here's an easier way to crash inkscape-0.92.3-2.fc28.x86_64:
1767518,2018-09-25 18:18:51 UTC,*** Bug 1632878 has been marked as a duplicate of this bug. ***
1767518,2018-11-05 23:03:24 UTC,"(in reply to my comment #40) my workflow did not trigger the bug anymore, but it seems to be still around.
Yesterday I encountered this bug on Fedora 28 (and today on 29) x86_64.
$ rpm -q inkscape
inkscape-0.92.3-5.fc29.x86_64
and
inkscape-0.92.3-2.fc28.x86_64"
1767518,2019-05-31 12:22:15 UTC,"I see that the issue in Comment 0, my issue in Comment 59, and the issue in Comment 58 have been resolved in Fedora 29, Inkscape 0.92.4.  I didn't test every sequence from every comment, but it does seem more stable now when fiddling with text."
1767518,2018-11-05 01:51:43 UTC,"Same for me on fedora 29 :
/usr/include/c++/8/bits/stl_vector.h:950: std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = Inkscape::Text::Layout::Character; _Alloc = std::allocator<Inkscape::Text::Layout::Character>; std::vector<_Tp, _Alloc>::const_reference = const Inkscape::Text::Layout::Character&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed."
1767518,2018-11-03 03:37:52 UTC,*** Bug 1645728 has been marked as a duplicate of this bug. ***
1767518,2018-10-30 05:47:25 UTC,*** Bug 1644145 has been marked as a duplicate of this bug. ***
1767518,2020-09-21 12:08:12 UTC,Closing because INVALID.
1767518,2018-10-10 09:30:19 UTC,Similar problem has been detected:
1767518,2018-11-05 11:51:42 UTC,"This looks related to bug #1575842, but the previous comment contains inkscape-0.92.3-2.fc28, where the fix for the older bug is included, thus maybe this is not exactly the same issue or the issue is not completely fixed."
1767518,2018-06-21 22:33:43 UTC,Similar problem has been detected:
1767518,2018-10-21 01:20:57 UTC,*** Bug 1641306 has been marked as a duplicate of this bug. ***
1767518,2018-06-20 18:33:15 UTC,Similar problem has been detected:
1767518,2018-05-03 04:09:25 UTC,I've got a very similar problem:
1767518,2018-04-09 16:24:42 UTC,Similar problem has been detected:
1767518,2018-04-09 16:22:11 UTC,"Created attachment 1419412
File: proc_pid_status"
1767518,2018-04-09 16:22:09 UTC,"Created attachment 1419411
File: open_fds"
1767518,2018-04-09 16:22:08 UTC,"Created attachment 1419410
File: mountinfo"
1767518,2018-04-09 16:22:06 UTC,"Created attachment 1419409
File: maps"
1767518,2018-05-03 04:10:13 UTC,"Created attachment 1430418
problem that reproduces this crash"
1767518,2018-04-09 16:22:02 UTC,"Created attachment 1419407
File: environ"
1767518,2018-04-09 16:21:59 UTC,"Created attachment 1419405
File: cpuinfo"
1767518,2018-04-09 16:21:58 UTC,"Created attachment 1419404
File: core_backtrace"
1767518,2018-04-09 16:21:56 UTC,"Created attachment 1419403
File: cgroup"
1767518,2018-04-09 16:21:54 UTC,"Created attachment 1419402
File: backtrace"
1767518,2018-04-09 16:21:46 UTC,"Description of problem:
I double-clicked on a row of text and pressed Delete."
1767518,2018-06-20 19:18:43 UTC,*** Bug 1590279 has been marked as a duplicate of this bug. ***
1767518,2018-04-09 16:22:01 UTC,"Created attachment 1419406
File: dso_list"
1767518,2018-05-16 14:06:23 UTC,*** Bug 1578869 has been marked as a duplicate of this bug. ***
1767518,2018-04-09 16:22:04 UTC,"Created attachment 1419408
File: limits"
1767518,2018-05-27 14:24:46 UTC,Similar problem has been detected:
1767518,2018-05-22 01:32:33 UTC,Similar problem has been detected:
1767518,2018-06-19 09:55:30 UTC,"Description of problem:
The program execution is aborted every time you try to break the line of a text that the area was not defined by drag and drop of the cursor. Sometimes (often) this also happens with text boxes with defined area."
1767518,2018-06-19 09:53:20 UTC,*** Bug 1592776 has been marked as a duplicate of this bug. ***
1767518,2018-06-15 21:55:37 UTC,Similar problem has been detected:
1767518,2018-06-15 12:11:36 UTC,Similar problem has been detected:
1767518,2018-06-15 12:05:24 UTC,Similar problem has been detected:
1767518,2018-06-13 00:58:40 UTC,*** Bug 1590590 has been marked as a duplicate of this bug. ***
1767518,2018-06-12 09:23:00 UTC,*** Bug 1590231 has been marked as a duplicate of this bug. ***
1767518,2018-06-17 04:09:57 UTC,*** Bug 1592105 has been marked as a duplicate of this bug. ***
1767518,2018-06-12 03:06:48 UTC,*** Bug 1590078 has been marked as a duplicate of this bug. ***
1767518,2018-06-09 18:21:06 UTC,*** Bug 1589452 has been marked as a duplicate of this bug. ***
1767518,2018-06-09 15:18:46 UTC,My report was rejected as duplicate of this after uploading everything...
1767518,2018-06-08 19:31:27 UTC,*** Bug 1589365 has been marked as a duplicate of this bug. ***
1767518,2018-05-31 11:27:53 UTC,This has shown up on Fedora 28 (here) and on Alpine Linux. I found this bug from someone on Alpine Linux. https://bugs.launchpad.net/inkscape/+bug/1767518 Upstream hasn't (at time of writing) acknowledged it yet. I linked this bug to that ticket.
1767518,2018-05-31 09:34:08 UTC,Encountered what appears to be the same problem on Fedora 28.
1767518,2018-05-27 14:40:28 UTC,Similar problem has been detected:
1767525,2018-06-16 23:27:40 UTC,There is a fix for this submitted upstream: https://github.com/solus-project/brisk-menu/pull/101
1767525,2018-05-17 14:38:13 UTC,"I have been having the same problem with Super key. Clean install of 18.04. I am using a Azio MKG-1K en-us keyboard. I use the default drivers for it, and I know it worked in other distro's and I am pretty sure it worked in UM 17.10.
Currently using UM 18.04, pantheon theme, Marco Adaptive window manager, HUD and dock enabled."
1767525,2018-04-30 13:26:37 UTC,"Another thing I just noticed (that might be connected) is that if I activate ""Enable HUD"" in MATE Tweak, I can't move the windows with Alt+Click-Drag anymore as well. Same with Alt+Rightclick for resize. Since both Alt and Super are normally modifier keys, this could point to a common problem."
1767525,2018-04-30 12:40:18 UTC,"Many of the normal commands such as move window are bound to Mod4, which is the same key as Super_L but I believe has priority? Could this be why it overrides the normal shortcuts?"
1767525,2018-04-30 07:42:53 UTC,"Hello,"
1767525,2018-04-28 00:36:03 UTC,I think its the default (Marco (Adaptive Compositor) in mate tweak) using nvidia drivers.
1767525,2018-04-28 09:03:14 UTC,Hi
1767525,2018-04-28 01:11:06 UTC,"Should have asked earlier, but what keyboard layout are you using? And are your overall shortcuts on default or have you added/changed some of them?"
1767525,2018-04-27 23:58:59 UTC,"Hi, what window manager are you using? Marco, Compiz, other?"
1767525,2018-09-28 21:02:49 UTC,This bug was fixed in the package brisk-menu - 0.5.0-8ubuntu1
1767525,2018-04-29 00:50:37 UTC,"Hi, I'm having a similar problem, also have a en_GB keyboard layout.
I've seen that there were problems in the past with similar things, that were patched (e.g. https://github.com/solus-project/brisk-menu/issues/55)
All my key bindings are as default, I just installed the OS."
1767527,2018-11-19 15:53:15 UTC,"How was the system installed? Did this use d-i (the alternate installer image), or ubiquity?"
1767527,2019-01-10 16:47:11 UTC,Information was requested in October to help us reproduce this.  We would like to have this solved for 18.04.2 but need more information.
1767527,2019-02-25 17:26:21 UTC,"I can't make any sense of it. I have similar setups here; the systems get installed (with 18.04 as well as Disco) with nvme#n#p#_crypt devices, and those load properly."
1767527,2019-01-14 21:40:51 UTC,This system was installed with Ubiquiti.
1767527,2018-10-01 21:45:43 UTC,"It is unclear to me what the cause of this bug is.  It appears to be a mismatch between the device name as encoded in /etc/crypttab, and the actual device name used at runtime by the installer, preventing the cryptsetup initramfs hook from probing and detecting the correct device (and therefore the correct kernel modules) at initramfs generation time."
1767527,2019-01-14 17:14:40 UTC,"Comment 11 mentions bionic-desktop images, so I'm assuming ubiquity without more information to go on."
1767527,2018-04-28 15:33:34 UTC,"Once I was into the system, I ran ""sudo apt clean all; sudo apt update; sudo apt -y full-upgrade"", which completed successfully. Upon reboot, everything still worked. It seems to be part of the setup process itself that is broken."
1767527,2018-04-28 15:31:44 UTC,"TJ, some new information - this is a regression. Trying the EXACT same install path with the ""complex"" passphrase I usually use on an old bionic ""daily"" build worked perfectly. I was able to boot into the system and setup my applications. I'd rather not wipe it right now, but something broke between the official 18.04 build and this one:"
1767527,2018-04-28 09:23:36 UTC,Correct to the final instruction of my last comment:
1767527,2018-04-28 09:20:31 UTC,Dylan: I've updated the bug description to describe the situation as we left it.
1767527,2018-04-27 23:48:02 UTC,Original /etc/crypttab:
1767527,2018-04-27 23:43:28 UTC,"Full lshw output, in case this can't be reproduced in a VM easily: paste.ubuntu.com/p/jx2zR7JpTR/"
1767527,2018-04-27 23:36:36 UTC,"My usual passphrase is something complex similar to ""--[-Word#Word.A#More#Words*123*Word-]--"", with all of those symbols included, but with the passphrase abcdefg12, I still hit this issue."
1767528,2018-05-08 12:47:56 UTC,"The device in question indeed does not have a 'scope global' address:
https://en.wikipedia.org/wiki/Unique_local_address"
1767528,2018-05-08 12:56:24 UTC,Can you also give the output of:
1767528,2018-05-08 12:58:53 UTC,"It does seem like you are getting both a local address (fd00::1:0:4) and a possibly valid address (fe80::7cea:d7ff:fe95:31c).
Presumably the latter is via auto-discovery?
Or is it being defined in MAAS?"
1767528,2019-02-26 02:25:44 UTC,This bug still exists.
1767534,2020-04-27 17:26:51 UTC,This bug was fixed in the package libprelude - 5.1.1-6
1767534,2018-04-28 00:27:45 UTC,"Actually, after reading the summary a bit more closely, I think the following two lines fixed the problem:"
1767534,2018-04-30 21:32:01 UTC,I believe prelude-utils should conflict with or break libprelude2v5.
1767538,2018-05-06 18:55:52 UTC,"I am not sure which version of Me TV your are using on what platform. I am not sure anyone is going to be maintaining the 1.3.x, 1.4.x, or 2.0.x codebases. My suspicion is that the Linux DVB API has changed and the Me TV codebase has not."
1767539,2018-04-28 15:56:18 UTC,Thanks Scott!
1767539,2018-05-02 07:27:36 UTC,"Thanks Scott. I've gone ahead and built this package in the https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/ ; given the large amount of code around the introduced deserializer, I'd like to see a successful test report before publishing to trusty-security."
1767539,2018-05-03 04:21:35 UTC,"On Wednesday, May 02, 2018 07:27:36 AM you wrote:

> Thanks Scott. I've gone ahead and built this package in the
> https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/ ;
> given the large amount of code around the introduced deserializer, I'd
> like to see a successful test report before publishing to trusty-
> security.
"
1767539,2018-05-03 05:17:01 UTC,"On Thu, May 03, 2018 at 04:21:35AM -0000, Scott Kitterman wrote:

> On Wednesday, May 02, 2018 07:27:36 AM you wrote:
> > Thanks Scott. I've gone ahead and built this package in the
> > https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/ ;
> > given the large amount of code around the introduced deserializer, I'd
> > like to see a successful test report before publishing to trusty-
> > security.
>
> I'm running a patched version now.  The same patch has been released by
> Debian.
"
1767539,2018-05-03 05:17:33 UTC,This bug was fixed in the package quassel - 0.10.0-0ubuntu2.3
1767539,2018-05-09 01:07:04 UTC,Please re-subscribe ubuntu-security-sponsors when further updates are attached. Thanks.
1767539,2018-05-14 00:59:29 UTC,Uploaded a merge from Debian to Cosmic fixing this: https://launchpad.net/ubuntu/+source/quassel/1:0.12.5-2ubuntu1
1767539,2018-05-14 01:59:44 UTC,This bug was fixed in the package quassel - 1:0.12.5-2ubuntu1
1767542,2018-05-02 21:04:47 UTC,"I'm not sure what that meant. Could you rephrase? Note that the issue is that the user turns OFF Wi-Fi, but the system turns ON Airplane mode."
1767542,2020-04-13 10:18:48 UTC,"I'm having a desktop system where the wifi is disabled from the bios, and the airplane mode is constantly enabled."
1767542,2020-03-05 13:11:28 UTC,"Still an issue on Ubuntu 19.10 on my Dell XPS 9370.
Toggling it in system settings doesn't switch it to airplane mode, but it does in the top-right corner."
1767542,2020-03-03 15:55:20 UTC,"In Ubuntu 18.04 LTS this is still an issue, the described behaviour still occurs exactly as described.
Probably this is expected with your smartphone but absolutely not from your Laptop!"
1767542,2019-05-07 15:02:23 UTC,"Ubuntu devs are still dreaming that the OS will conquer ""Chromebook"" world, and will be running on tablets as well. Obviously, if a user turns of wifi, it's not because they most likely docked their notebook, no, it's because they're on an airplane with their tablet and need the airplane mode."
1767542,2020-06-24 12:30:05 UTC,"Issue persists on 20.04 on the same Dell XPS 9370.
Turning Wifi off still turns airplane mode on."
1767542,2018-05-02 09:49:20 UTC,How is that an important issue? It's a best confusing but whether no wifi/bluetooth is showed as equivalent to be in airplane mode or not is just a visual clue being displayed one way or another
1767542,2018-05-01 21:44:34 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=777759 then
1767542,2018-05-01 22:27:17 UTC,"Yes, this looks more like it. The bug is 13 months old though and still in ""new"" status. That's sad."
1767542,2018-05-01 22:37:15 UTC,"Also, isn't importance ""low"" a little understated for such a grave issue? This does not look like production ready quality."
1767542,2018-05-01 19:50:47 UTC,"I accidentally changed the status back to new and it won't allow me to set it back to ""triaged""."
1767542,2018-05-01 19:45:40 UTC,"@Sebastien, I do not think this issue is reflected anywhere in the issue you linked upstream."
1767542,2018-05-01 09:00:33 UTC,"Thanks, that's known upstream, see https://bugzilla.gnome.org/show_bug.cgi?id=748476"
1767544,2018-05-04 23:13:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767544,2018-05-01 23:21:59 UTC,Here is an audio demo of what happens.
1767544,2018-05-04 23:17:59 UTC,"On my computer, Orca tried to read part of the Wi-Fi settings screen before it locked up and exhibited the same behavior that was described in Jeremy's audio recording."
1767544,2018-05-01 08:56:24 UTC,"Thank you for your bug report. What do you mean exactly by the system hangs? You can't interact with the launcher, switch softwares, etc?
Upstream has a report about keyboard navigation not working in settings when orca is enabled, see https://gitlab.gnome.org/GNOME/gnome-control-center/issues/70 , but your issue is different?"
1767544,2018-05-01 19:36:17 UTC,"From an accessibility prospective, the system appears to hang. Orca doesn't read anything until I force close the gnome-control-center window. I'm blind, so cannot tell if anything happens if I move the mouse, or press Alt+Tab."
1767551,2018-04-28 09:53:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767551,2018-05-17 14:07:52 UTC,Are any more logs required to support the fixing of this?
1767558,2020-02-27 21:32:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767558,2020-02-27 21:39:42 UTC,"Can confirm.
Apparently the flightgear package is missing two dependencies.
I fixed this by manually installing this (as suggested in the FlightGear IRC channel):"
1767559,2018-07-31 12:25:42 UTC,I can confirm that updates from ppa:mamarley/updates libinput 1.11.3-0+ppa0~18.04.0 fix problem on Dell XPS L322X.
1767559,2018-05-24 03:23:39 UTC,"For the record, we now have 1.10.7 in cosmic."
1767559,2018-07-17 02:09:05 UTC,"Technically a stable release like bionic should stay on the original series it was released with (1.10) and get bug fixes only. So ideally only libinput 1.10.7, but also libinput isn't clear-cut about only releasing bug fixes in such releases and sometimes includes enhancements which would also make it more difficult to get authorised for bionic."
1767559,2018-09-13 19:21:12 UTC,"I want to add that the touchpad dropout issues affect the Lenovo Thinkpad T460s series as well. I got things working by downloading and installing the latest libinput packages for cosmic (unstable) from https://launchpad.net/ubuntu/+source/libinput. I installed libinput10, libinput-bin, and libinput-tools 1.12.0-1."
1767559,2018-06-25 09:32:24 UTC,"Whoever subscribed ubuntu-sponsors, please unsubscribe them."
1767559,2018-06-22 02:08:48 UTC,See also bug 1778072.
1767559,2018-06-20 14:10:01 UTC,Upgrading to 1.11 would fix those + touchpad movement in general
1767559,2018-05-21 02:25:07 UTC,Is that fixed in 1.10.7? :)
1767559,2018-07-16 10:07:20 UTC,Cosmic now has 1.11.1 - would it make more sense to change this to instead request 1.11.1 be SRU'ed into Bionic? Or still request for 1.10.6?
1767559,2018-05-08 02:12:59 UTC,We now have version 1.10.6 in cosmic :)
1767559,2018-05-07 10:10:31 UTC,I can see libinput 1.10.5 is now in Cosmic: https://packages.ubuntu.com/cosmic/libinput10
1767559,2018-04-29 08:34:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767559,2018-04-29 06:13:07 UTC,"Thanks, just tested the libinput 1.10.5 packages in that PPA - I can confirm it fixes the problem for my Dell XPS13 L322X on Bionic."
1767559,2018-04-28 12:43:18 UTC,libinput (1.10.5-0+ppa0~18.04.0) bionic; urgency=medium
1767559,2018-04-28 09:49:00 UTC,"I have ThinkPad T440s and I have a lot of issues with touchpad. Before installing Kubuntu 18.04, I used Arch and those issues did not appear after updating libinput to 1.10.5. So please provide us this update soon."
1767559,2018-04-28 03:16:32 UTC,This is the first time I've submitted an SRU request - let me know if there is more detail I need to add
1767559,2018-05-18 16:39:38 UTC,I was involved in a touchpad issue for Logitech wireless keyboard/touchpad combo devices where they used a debounce exception rule with an odd name and the code that made it into the 1.10.6 sources for cosmic needs work so be careful what you wish for.
1767560,2018-10-07 00:23:40 UTC,More related discussion: https://bbs.archlinux.org/viewtopic.php?pid=1651514#p1651514
1767560,2018-10-07 00:19:56 UTC,Found upstream discussion: https://forum.xfce.org/viewtopic.php?id=12138
1767560,2018-10-06 23:44:21 UTC,"I'm not fully certain. It appears like a theme specific bug, but it doesn't seem like the new xfce4-power-manager icon is using the theme's icons, but rather its own internal, or perhaps I'm looking at the wrong place."
1767560,2018-09-30 11:06:34 UTC,Is this a theme specific bug then?
1767560,2018-10-07 13:06:53 UTC,"Fwiw, I tried to follow/remain consistent with the Adwaita/Gnome icons."
1767560,2018-08-29 23:49:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767560,2018-08-22 12:41:13 UTC,It would be best to inform the upstream devs about this bug.
1767560,2018-10-07 13:03:29 UTC,This is correct: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/comments/7
1767560,2018-08-30 00:39:44 UTC,This bug affects Xubuntu 18.04 but not 17.xx or earlier
1767561,2018-04-28 14:25:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767561,2018-04-28 14:25:31 UTC,I tried to reproduce this error and got a crash. Not with the same message though. ubuntu-bug did not report my crash as a duplicate but I think it may well be: https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1767657
1767568,2019-11-24 10:13:13 UTC,"To Robie Basak, specifically with regards to #37."
1767568,2018-05-01 17:14:50 UTC,apport information
1767568,2018-05-01 17:14:52 UTC,apport information
1767568,2018-08-03 04:45:48 UTC,"After revisiting this issue I was able to find a solution, via the setterm command.  This is based on the guidance posted at https://superuser.com/questions/152347/change-linux-console-screen-blanking-behavior"
1767568,2018-09-25 21:51:08 UTC,"But DPMS is working for you?
Because it is not working for me...
The console gets blanked, but the monitor stays on unnecessarily.
Thanks for the info!"
1767568,2018-11-01 17:30:28 UTC,DPMS isn't working for me too on 18.04 x64 server (on 16.04 worked with no problem).
1767568,2018-11-02 07:35:43 UTC,What graphics do you use?
1767568,2018-11-30 05:08:25 UTC,"I'm experiencing this same issue on a Dell 7577 (laptop), it has got a GTX 1060 MaxQ, but I believe the internal display (which is where I am experiencing and trying to resolve this same issue) is running off the Intel HD Graphics 630."
1767568,2018-05-01 17:14:47 UTC,apport information
1767568,2018-11-30 05:17:18 UTC,"Actually, my apologies, I am not (and I can't figure out how to edit my last comment, if it is possible) ..."
1767568,2019-01-06 10:53:48 UTC,The problem concerns ubuntu 18.04 and 17.10. My configuration - Ubuntu 18.04 x64 server running on ASUS P9D-E/4L (Aspeed AST2300). On 16.04 DPMS worked with no problem.
1767568,2019-06-26 07:32:41 UTC,"The problem seems present in 19.04. My monitor stays ON, exactly as described in this bug."
1767568,2019-06-26 19:44:26 UTC,"my First test:
Ubuntu 16.04.6 LTS, with all the updates
no HWE, might try that later."
1767568,2019-06-26 21:32:42 UTC,"Ubuntu 16.04.6 LTS + HWE
doesn't seem to do the DPMS"
1767568,2019-06-27 21:25:56 UTC,"Summary of my tests
WORKS:
* Ubuntu 16.04.6 LTS (xenial), clean install and after updates as well
* Ubuntu 16.10 (Yakkety Yak), clean install and after updates as well"
1767568,2019-06-28 04:23:47 UTC,"The following ""fix"" seems to be the cause of this bug. Link below:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017"
1767568,2019-07-21 22:39:15 UTC,Thank you for taking the time to write this up and helping to make Ubuntu better.
1767568,2018-11-30 05:18:19 UTC,"As soon as I hit post on that last comment the display lit up again, so it's ""blank"" but not ""off"" - so I AM having the issue, and will stop spamming now, sorry."
1767568,2018-05-01 17:14:45 UTC,apport information
1767568,2019-11-25 09:48:56 UTC,"> I understand that the original reporter said that he got it working with setterm, but as by convention these bug reports often require verification from others in order to get any attention, it seems only reasonable that after many have said that the DPMS power saving is what is not working, while simple blanking and leaving the monitor on is what is currently happening, that this bug should not have been marked invalid.
"
1767568,2018-05-01 17:14:41 UTC,apport information
1767568,2018-05-01 17:14:43 UTC,apport information
1767568,2018-04-28 04:58:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1767568,2018-04-30 16:32:46 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1767568,2018-05-01 00:47:19 UTC,"Per the previous entry, I have retested for this issue with upstream kernel 4.16.6-041606-generic.  No change in DPMS behavior was observed, i.e., power save for the monitor does not seem to be enabled."
1767568,2018-05-01 10:58:40 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1767568,2018-05-01 15:36:53 UTC,After running the apport-collect command I was unable to log in to launchpad from the text based browser running on the server.  If someone can advise how I can manually collect the desired logs I would be happy to post them.
1767568,2018-05-01 17:14:15 UTC,apport information
1767568,2018-05-01 17:14:18 UTC,apport information
1767568,2018-05-01 17:14:13 UTC,apport information
1767568,2018-05-01 17:14:24 UTC,apport information
1767568,2018-05-01 17:14:26 UTC,apport information
1767568,2018-05-01 17:14:28 UTC,apport information
1767568,2018-05-01 17:14:30 UTC,apport information
1767568,2018-05-01 17:14:33 UTC,apport information
1767568,2018-05-01 17:14:35 UTC,apport information
1767568,2018-05-01 17:14:37 UTC,apport information
1767568,2018-05-01 17:14:39 UTC,apport information
1767568,2018-05-01 17:14:21 UTC,apport information
1767569,2018-04-28 04:48:28 UTC,"Problem occurred with: ubuntu-18.04-live-server-amd64.iso
Did not occur with: ubuntu-18.04-server-amd64.iso"
1767569,2018-04-28 18:24:43 UTC,Thanks for report.
1767569,2018-06-18 19:19:28 UTC,This has been fixed in upstream curtin here:
1767570,2019-05-06 15:55:23 UTC,Is anyone still seeing this bug on their system?
1767570,2019-07-06 04:17:27 UTC,[Expired for efibootmgr (Ubuntu) because there has been no activity for 60 days.]
1767570,2018-08-16 04:17:25 UTC,[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]
1767570,2018-04-28 10:55:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767570,2018-04-30 04:49:56 UTC,"The error in your log is:
Setting up shim-signed (1.34.9+13-0ubuntu2) ...
Installing for x86_64-efi platform.
File descriptor 3 (pipe:[224911]) leaked on vgs invocation. Parent PID 23233: grub-install
File descriptor 5 (/dev/sda1) leaked on vgs invocation. Parent PID 23233: grub-install
File descriptor 3 (pipe:[224911]) leaked on vgs invocation. Parent PID 23233: grub-install
File descriptor 5 (/dev/sda1) leaked on vgs invocation. Parent PID 23233: grub-install
Could not delete variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Block device required.
dpkg: error processing package shim-signed (--configure):
 installed shim-signed package post-installation script subprocess returned error exit status 1"
1767574,2018-05-02 14:18:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1767578,2018-06-30 13:53:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767580,2018-04-30 20:21:32 UTC,Upstream is preparing the 1.8 release. The final releases are here
1767586,2018-04-30 18:06:07 UTC,Forgot to mention that everything is running on top of NVIDIA-390 package for GTX 1060
1767586,2018-04-29 09:31:51 UTC,"If I log out and log in as a different user I get blank screen with mouse cursos visible and movable, but nothing else. If I log in as same user it works or if I boot I can log in with any user.
18.04 normal set up. I did install and purge gnome-session (to test ""vanilla gnome"")."
1767586,2018-04-29 10:27:36 UTC,@Heikki try this:
1767586,2018-04-29 10:36:18 UTC,"Also, if you are running Steam, just try this:"
1767586,2018-04-30 16:34:32 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1767586,2018-04-30 18:05:18 UTC,I have installed the following files:
1767594,2018-06-21 19:17:58 UTC,"For me, The freeze happens when the installer asks to connect to a wifi network , after that the next page doesn't come. Actualy only ubiquity freezes at that time, so I can open firefox and browse web."
1767594,2018-07-14 10:32:56 UTC,I'm also having this problem. I tried @gdeepankar solution but without success.
1767594,2018-07-26 21:44:50 UTC,"I had the same issue and @gdeepankar didn't work for me too.
The issue disappeared when my BIOS was updated.
Asus X555UB (Nvidia Geforce 940m)"
1767594,2018-08-03 21:42:46 UTC,I am having the same issue. I have Acer nitro 5 and Acer aspire 7 both with Nvidia GTX 1050. The installation freezes at network page. I am able to move the mouse cursors around but not select any of the option.
1767594,2018-09-26 14:48:53 UTC,"Hello All,
My laptop model is: MSI GE62VR6RF Apache Pro
Graphics Card: Nvidia Geforce GTX 1060"
1767594,2018-06-21 17:43:48 UTC,"Does the freeze still happen if you just let it sit there without using the installer?  Or if you use other things like do some web browsing?  When it does freeze, hold down the sysrq key and press R E I S U B and see if that reboots the computer."
1767594,2018-10-13 15:23:09 UTC,"Hello guys,
I have an MSI GF63-7RD Gaming Laptop with i7-8750H and NVIDIA GTX-1050Ti.
I am able to install ubuntu 18 on my laptop following the instructions here(https://gist.github.com/mari-linhares/cef4cb3440408e44963d1447a7db5ae0) . But after installation it was always using NVIDIA Graphics and draining the battery so fast. So I tried to change it to Intel HD Graphics in nvidia-prime. I changed it and when I rebooted, everythings broken. The system not loading nvidia drivers at all. Only Intel HD Graphics is working."
1767594,2019-07-03 19:14:35 UTC,"Also getting a freeze during installation of ubuntu desktop 18.04. As Leandro wrote: ""I'm able to click in continue in language selection, but it freezes on keyboard layout selection."" The environment is a packet.com bare metal server running VMware ESXi 6.5, size c1.small. Install Ubuntu as guest VM. This may be reproducible if you go to packet.com and try the same configuration. After multiple attempts, the keyboard seems to freeze at some point every time. Not consistent.
Then, switched to ubuntu server 18.04 instead of desktop. It had a different set of installer screens. The server setup successfully made it through to completion, so the problem was just on the desktop version."
1767594,2018-12-20 17:07:44 UTC,"I confirm that using:
nouveau.modeset=0
as written by Deepankar Gupta in #5 solves that the installation no longer freezes."
1767594,2018-12-25 18:28:17 UTC,"Same issue as Bhanu here (comment #21).
I have a msi gf63 8RD.
Only Intel HD graphics work."
1767594,2018-10-06 11:35:57 UTC,"Hello everybody,
I have an ASUS X556U(J).
It has an i7-6500U and NVidia GeForce GTX 920M.
Had the same problem myself. The installation would freeze on a random window, usually the language selection.
Simply, update your BIOS and this should resolve the issue.
I successfully installed Ubuntu 18.04.1 with no problems."
1767594,2018-06-21 03:36:25 UTC,No errors were found during memtest.
1767594,2018-05-23 10:13:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767594,2018-06-11 13:54:56 UTC,"Btw, just installing the nVidia drivers did not do the trick for me, I had to modify the grub configuration to set nouveau.modeset=0 in the Ubuntu entry. Was this supposed to happen automatically?"
1767594,2018-06-11 13:06:51 UTC,"Done, did not see the option."
1767594,2018-06-06 20:25:55 UTC,"You should confirm also affects me then, won't get as much attention if nobody confirms affected in the list."
1767594,2018-06-06 20:15:26 UTC,I can confirm this is an issue for the HP Pavilion Power 15cbXXX line too.
1767594,2018-05-28 12:05:53 UTC,"Yes, it was nvidia graphics card."
1767594,2018-05-28 11:50:53 UTC,"Thank you!It was the nvidia graphics that was causing the problems then.
Did it resolve your issue?
I will give it a try then."
1767594,2018-05-28 03:39:37 UTC,"Hi I found work around from the link below
https://ubuntuforums.org/showthread.php?t=2349782"
1767594,2018-05-25 03:28:49 UTC,"Ubuntu 18.04-desktop-amd64 version freezes when I trying ubuntu on my new laptop, ""Acer Predator Helios 300 Core i7 8th Gen - (8 GB/1 TB HDD/128 GB SSD/Windows 10 Home/4 GB Graphics) PH315-51 Gaming Laptop"".  The ubuntu freeze after like 1 min or so. I am not able to start Libra Office either, it freezes in-between."
1767594,2018-05-23 10:36:15 UTC,"I was trying to install Ubuntu 18.04 on my ASUS X556U, But the installer freezes everytime during the language selection or Ubuntu logo. My friend had the same issue who tried to install 18.04 on his machine. 16.04 installs without a problem. We both had NVIDIA GPU in similar. There wasn't any issue with the iso either, the checksums match. Tried with different rippers etcher,rufus and ubuntu's startup disk."
1767594,2018-04-28 08:46:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1767594,2018-06-20 14:08:19 UTC,"Please choose the memtest option at the boot menu and let it run for at least 15 minutes and let us know if it finds any errors.  Also when you say the install freezes, do you mean just the installer window, or the whole computer?  Does pressing the caps lock key still toggle the caps lock light?"
1767607,2018-05-30 14:03:06 UTC,"Thanks very much Mathieu,"
1767607,2018-05-01 18:01:40 UTC,"Hi Dimitri,"
1767607,2018-05-25 18:34:41 UTC,Won't this work?
1767607,2018-05-01 14:10:04 UTC,"https://systemd.network/systemd.network.html#Peer=:
.network supports [Address] Peer=
with same input as Address= in there."
1767608,2018-04-29 05:26:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767608,2019-02-24 17:33:44 UTC,"The bug is still present in 19.04 daily build.
Maybe removing the minimize button for that window could be a stopgap solution?"
1767612,2018-04-28 12:53:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1767614,2018-05-09 10:27:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767614,2018-10-27 12:26:00 UTC,"I am also experiencing random system freezes with nvidia-390. Sometimes after just a few minutes, other times after hours of operation."
1767621,2018-05-18 04:36:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767639,2018-06-17 23:17:52 UTC,The error is caused by the following line of code https://github.com/Guake/guake/blob/150a3a77f9355cb49e3c45a9be850b2f1ac684ec/guake/guake_app.py#L1473
1767639,2018-06-17 23:18:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767639,2019-11-15 22:12:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in upstream in Guake 3.0.6. The fixed version shipped with Ubuntu 19.04. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://wiki.ubuntu.com/UbuntuBackports for more information."
1767641,2018-06-24 18:26:27 UTC,Rico
1767641,2019-01-07 06:03:01 UTC,Plank is a dead loss.
1767641,2018-04-29 12:35:01 UTC,"This was fixed in git master
https://git.launchpad.net/plank/commit/?id=109f790cc1f1922411fd41ac104ab90a443a282a"
1767641,2018-04-30 04:21:18 UTC,Thanks for letting me know.
1767641,2019-01-06 10:54:42 UTC,"I am working on a Dell Laptop with a fresh install of Ubuntu Budgie 18.10. Here, the effect of degrading animation of the icons continues until today. After some time (or clicks) I haven't measured, the ""bouncing"" of the icons stops. From the issue record I understand that it has been fixed, but on my machine it continues until today. I really like Plank, but I find the (lack of) effect a little annoying."
1767645,2018-04-28 14:20:24 UTC,"I can explain the change at least: 18.04 now uses indicators instead of the older ""notification area"" applets."
1767650,2019-03-17 10:13:35 UTC,"Ubuntu 18.04.2 LTS, x86 (newest version available for this arch)"
1767650,2019-03-17 10:12:21 UTC,"This affects HP/Compaq 8510p too. This model too was sold with ""3D DriveGuard"", and the screen orientation is:"
1767650,2018-09-24 22:02:55 UTC,"Everything I have read points to the ""3D Driveguard"". I appreciate the feature and would not so much mind the screen auto-reorientation both
 a) the screen orientation would auto reset even when the screen is locked
 b) screen auto-reorientation could be controlled or disabled in the system display settings (not just for the user)"
1767650,2018-06-29 08:23:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767650,2018-05-01 21:42:19 UTC,"Right, it seems wrong, but is that an hardware issue/the rotation sensor providing bug informations?"
1767650,2018-05-01 18:08:32 UTC,"I find this behavior unexpected, confusing, and user-hostile.  But if there's no way to do anything about it at least it's documented here.  Thanks for the pointer to iio-sensor-proxy, I've removed that package:"
1767650,2018-05-02 02:02:56 UTC,"I believe the accelerometer in this model is intended for ""HP 3D Driveguard"" to park HDD drive heads to help protect the drive from fall damage. So the sensor was probably not intended to reflect the orientation of the screen."
1767650,2018-04-30 23:14:55 UTC,Output is attached.
1767650,2018-04-30 20:26:43 UTC,""" ** (process:2669): DEBUG: 18:42:21.879: iio-sensor-proxy is already running, or it cannot own its D-Bus name. Verify installation."""
1767650,2018-04-29 22:44:03 UTC,"$ G_MESSAGES_DEBUG=all /usr/sbin/iio-sensor-proxy
** (process:2669): DEBUG: 18:42:21.879: iio-sensor-proxy is already running, or it cannot own its D-Bus name. Verify installation.
$ udevadm info --export-db | grep iio
E: SYSTEMD_WANTS=iio-sensor-proxy.service
E: SYSTEMD_WANTS=iio-sensor-proxy.service
E: SYSTEMD_WANTS=iio-sensor-proxy.service
$"
1767650,2018-04-29 21:05:03 UTC,"Could you give the output of those commands?
 $ G_MESSAGES_DEBUG=all /usr/sbin/iio-sensor-proxy
 $ udevadm info --export-db | grep iio"
1767650,2018-05-01 07:33:18 UTC,"So yeah, it looks like your laptop has a rotation sensor which is sending the informations GNOME is using. Unsure there is technically a bug in that behaviour..."
1767652,2019-10-03 04:01:27 UTC,I have same problem with KiCad 4.0.7 on ubuntu 18.04.1 64 bit
1767652,2018-09-18 08:17:34 UTC,"With a freshly installed 18.04 LTS, I also experience this problem with KiCad."
1767652,2018-10-09 00:11:21 UTC,Try to update graphic card driver.
1767652,2019-04-08 22:50:00 UTC,Same problem with Lubuntu 18.04.2 LTS
1767652,2019-10-11 07:31:19 UTC,"Unbelievable that this still isn't fixed, as Kicad is the most popular hobby EE package out there."
1767652,2018-09-22 12:09:17 UTC,I can confirm this. After updating from Ubuntu 17.10 to 18.04. See screenshot
1767652,2019-12-10 19:25:21 UTC,Can confirm J. Reynaud's PPA for Kicad 4.0 works in Ubuntu 18.04. Had the same issue as OP using the package from Ubuntu repos.
1767652,2020-05-19 19:05:19 UTC,"Fault affects me, with KiCAD version 4.0.7 (installed from Ubuntu repository) on Ubuntu 18.04.4 LTS."
1767652,2020-06-01 16:31:14 UTC,Hello every one. I hqve the same issue with the following configuration :
1767652,2020-06-01 17:08:20 UTC,"Hello,"
1767652,2018-07-07 11:31:41 UTC,"Please note that a typical user would try only the formal version of KiCad without adding a PPA or building from source! As Ubuntu 17.10 end of life comes this month (July 2018), and the 18.04 version is not usable, KiCad runs only on Ubuntu 16.04 LTS !"
1767652,2019-10-23 07:17:12 UTC,This affects me too.  I'd rather not have to install ppas on my own.   I think Kicad is a pretty important package.
1767652,2018-06-14 10:25:27 UTC,"@Seth, ok I didnt't notice it was not for the PPA. Ubuntu maintainers need to address this."
1767652,2018-05-30 21:50:16 UTC,@Nick-  This bug is against the kicad build on Ubuntu.  Why did you mark it invalid?
1767652,2018-05-31 16:54:53 UTC,"Until this is fixed in the Ubuntu package, we shouldn't close it."
1767652,2018-05-02 11:00:59 UTC,I have same problems.
1767652,2018-05-04 14:16:49 UTC,"Me too, on two different machines. Standard Ubuntu 18.04 installs. Problem affects both Unity and gnome (Ubuntu) desktops."
1767652,2018-06-01 22:55:36 UTC,Exactly the same problem on Xubuntu (fine on 17.10 but cursor ghosting on 18.04). (Acer Aspire 5736Z.)
1767652,2018-05-08 15:33:09 UTC,Ubuntu Studio 18.04 confirmed
1767652,2018-05-08 17:31:50 UTC,"Yes, I have the same problem reported above, on Ubuntu 18.04."
1767652,2018-05-08 18:14:05 UTC,"Exactly the same behaviour here, on a Dell Precision 5520, Ubuntu 18.04."
1767652,2018-05-04 22:26:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767652,2018-05-14 16:12:28 UTC,"I can confirm that, the new PPA seems to work for me. Thx for pointing this out Darren!"
1767652,2018-05-15 01:44:05 UTC,"It worked, thank you."
1767652,2018-05-17 14:38:11 UTC,That worked indeed! Thanks!
1767652,2018-05-14 14:57:02 UTC,"The new ppa fixes it for me.
https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-4
http://kicad-pcb.org/download/ubuntu/"
1767654,2019-08-14 07:59:45 UTC,"Can someone experiencing this bug please try live booting Ubuntu 19.10 or 19.04, and tell us if the problem is fixed there?"
1767654,2020-03-04 02:24:45 UTC,"Please file an upstream bug at intel graphics upstream:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs"
1767654,2019-08-14 08:00:36 UTC,19.10: http://cdimage.ubuntu.com/daily-live/current/
1767654,2019-08-14 09:51:01 UTC,Or do a rough bisect using mainline builds of the kernel:
1767654,2019-12-23 18:26:12 UTC,"This has been tested with live ubuntu 19.10 as suggested by Daniel and the mouse problem persists for intel braswell. xdotool reveals that X reports a vertical position of zero, even when the mouse is painted with an offset to the right, which seems to indicate this is could be a compositor problem, a mouse driver problem (not providing proper movement info to the left), or a 915 driver problem"
1767654,2020-02-28 21:39:33 UTC,"The problem exists on my system:
     Ubuntu 18.04LTS with Gnome Classic Desktop
     ASUS N3050M-E M/B with the Intel N3050 (Braswell) CPU
     VGA video connector (not HDMI)"
1767654,2020-03-02 10:46:51 UTC,I can't reproduce this with Focal daily image. Can you guys please confirm?
1767654,2020-03-03 19:00:10 UTC,"I confirm the bug
The bug applies to all the distros I have tried:
Ubuntu; Linux Mint; Manjaro; Fedora; Opensuse etc.
I also tried various DEs: Kde, Gnome, Cinnamon, Xfce, Mate etc.
It's a general problem, not just of mutter and Gnome
The bug exists only with Mesa and Modesetting, if you install xf86-video-intel (Arch and Manjaro), the mouse does not lock but the mouse flashes and multiplies
Also, when there is a lock, I noticed that the left side of the screen ""unlocks"", but the mouse starts flashing (with Mesa and Modesetting)
It happens especially when I watch videos in full screen or at 60fps on Youtube"
1767654,2020-03-04 10:06:38 UTC,https://gitlab.freedesktop.org/drm/intel/issues/1377
1767654,2018-12-10 01:58:56 UTC,"Also, Xorg moves the cursor independently of gnome-shell/mutter. So any failure to move the cursor is likely to be in Xorg."
1767654,2020-03-10 10:05:39 UTC,"If possible, try to participate in the bug report that I have opened on gitlab and to share your experiences
If I am the only one discussing the problem, it will hardly be considered soon"
1767654,2020-06-05 07:08:01 UTC,"I found a fix for the issues on kde, as I am running kubuntu 20.04, all credit goes to the original poster."
1767654,2020-06-05 07:28:14 UTC,"Note the original bug report here is not using the 'intel' driver, and in fact you probably shouldn't be using it either. The 'intel' driver is old, unsupported and buggy. The default 'modesetting' driver is what we recommend so if you have a file named '20-intel.conf' it should probably be deleted."
1767654,2020-06-06 14:15:09 UTC,"I can confirm that the problem is present with both the intel and the modesetting driver on Braswell systems. The exact symptoms differ for each, but in both cases it is triggered when the mouse touches the left limit of the screen. With modesetting, it seems to ""stick"" until you move the mouse away from the left side. With intel, touching the left side starts a flickering that persists even after you move the mouse away. Mainly, just the mouse cursor flickers, but the whole screen will flicker when doing graphics intensive tasks like fullscreen video or gaming. Sometimes, the mouse flicker can be so bad it becomes nearly invisible."
1767654,2020-07-03 06:59:58 UTC,"@Bob Lawrence (pilotbob42) I don't have .xprofile but i created it my home folder like you suggested and added the text, mine was HDMI3. Unfortunately it doesn't seem to do anything."
1767654,2020-07-12 10:38:53 UTC,"@Bob Lawrence (pilotbob42)
So i'm back with a better workaround."
1767654,2021-01-01 22:44:52 UTC,@tonypanduru
1767654,2021-01-01 22:49:37 UTC,"I'll also add that this problem is still present in kernel 5.8 (no matter if you use ""modesetting"" or ""intel"" driver for the Braswell GPU."
1767654,2019-08-14 02:15:52 UTC,If this bug is Braswell-only then it needs to be assigned to the kernel and/or Mesa.
1767654,2020-03-05 01:06:54 UTC,"I see this as well. It seems to happen every 2 or 3 days as a result a some combination of random keystrokes. i reboot fixes the issue, but it is very annoying."
1767654,2019-08-13 13:52:47 UTC,Exact same issue with a Gigabyte BRIX GB-BACE-3150 with a Celeron N3150 (Braswell). I've had this issue with Lubuntu and Debian (lxqt with xfwm4) with and without Compton as compositor.
1767654,2018-12-04 03:57:48 UTC,I had the exact same problem with my Intel NUC5CPYH which uses the Braswell chipset. After reading a lot of other articles I found this worked for me and now I can move my mouse anywhere on the desktop and my whole experience is a lot snappier:
1767654,2019-07-24 10:02:02 UTC,"Hello, i have the same problem with my Gigabyte Brace N3150. After a lot of searching i found out that this also is related to HDMI (maybe other digital output as well, but i can't test that)."
1767654,2019-07-25 01:32:48 UTC,Interesting. That's a Braswell too...
1767654,2018-10-14 23:03:21 UTC,Disabling Gnome Shell extensions does not fix the problem.
1767654,2018-10-15 01:58:33 UTC,OK. Can you please provide a video or screencast of the problem?
1767654,2018-10-15 23:14:38 UTC,Here is my video. It is from my camera as a screen recording would not show the bug.
1767654,2018-10-16 02:00:45 UTC,Thanks. Next please try:
1767654,2018-10-17 22:40:40 UTC,"Logging into ""Ubuntu on Wayland"" or live booting Ubuntu 18.10 does not fix the problem."
1767654,2018-10-18 01:41:18 UTC,Thanks.
1767654,2018-10-18 01:42:42 UTC,I will need to get hold of a machine with a similar CPU/GPU to test that theory.
1767654,2018-10-18 21:44:38 UTC,There is also a few more issues that might relate to this issue.
1767654,2018-10-11 05:03:01 UTC,"If you have any Gnome Shell extensions installed, please try disabling them and tell us if that fixes the problem."
1767654,2018-12-07 20:42:13 UTC,"Thanks for the suggestion. It does stop the cursor from getting stuck on the left side of the screen but it causes the cursor to have more problems including disappearing in Chrome when there is no movement, multiple cursors appearing, and other weird artifacts on the screen. Switching to ""uxa""causes the mouse to get stuck on the left side of the screen again."
1767654,2018-12-10 01:58:09 UTC,"If 'Driver ""intel""' fixes the problem then that suggests this is a bug in the default driver ""modesetting"". So reassigning there."
1767654,2018-12-10 01:59:56 UTC,Oops. You already said Wayland is also affected.
1767654,2018-12-27 03:46:39 UTC,Remove/comment out the last two options should fix the problem.
1767654,2018-12-27 14:26:44 UTC,It does't fix the issue.
1767654,2019-01-03 01:18:34 UTC,It works for me using XFCE but I agree it doesn't work on KDE or Gnome.
1767654,2019-06-17 17:14:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767655,2018-05-28 15:35:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767655,2018-10-20 16:37:35 UTC,"At least asunder and dxx-rebirth work in 18.10, didn't try ripperx there, yet."
1767665,2018-12-12 20:13:58 UTC,"Hey, sorry for the long delay in fixing this bug. This issue should be fixed in the latest beta build, v64, without the dbus-launch hack (tested with Gnome Flashback on Ubuntu 18.04)."
1767665,2018-10-29 02:44:08 UTC,"I use a different workaround, which seems to fix additional indicators besides dropbox.
In file /usr/share/xsessions/gnome-flashback-metacity.desktop, I add ""Ubuntu;Unity"" to the variable ""DesktopNames""."
1767665,2018-10-26 12:39:03 UTC,not working on ubuntu 18.04.1 with gnome fallback
1767665,2018-07-20 21:20:13 UTC,"I had a similar issue here, but solved it with the following:
killall indicator-application-service
sudo apt remove indicator-application"
1767665,2018-04-30 14:44:47 UTC,"1. Stop dropbox.
2. Open /usr/share/applications/dropbox.desktop for editing.
3. Change ""Exec=dropbox start -i"" to ""Exec=env XDG_CURRENT_DESKTOP=Unity dropbox start -i"".
4. Copy /usr/share/applications/dropbox.desktop to ~/.config/autostart/dropbox.desktop or just make same change to autostart file."
1767665,2018-04-28 21:22:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767666,2018-04-29 15:35:13 UTC,Update: Looks like a made a simple mistake. I was using 64bit Mixxx with 32bit ReaRoute and Jack driver DLL's ! However this is an easy mistake to make seeing as ...
1767668,2018-04-28 15:38:11 UTC,Syslog trimmed and pasted here:
1767668,2018-04-28 15:47:50 UTC,Turns out I can trigger this by simply locking and trying to unlock now I'm undocked.
1767668,2018-04-28 17:31:22 UTC,"Related, sudo also takes a while to run:"
1767668,2018-04-29 08:49:31 UTC,"Having unmounted my NFS drives, things seem to be back to normal.  Will do some more testing."
1767668,2018-04-30 02:53:48 UTC,Yeah the delays look like they're triggered by changes in your network interfaces (e.g. the removal of the dock/ethernet interface):
1767670,2018-05-13 00:08:24 UTC,I have been able to solve this.
1767674,2018-06-11 14:38:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767678,2018-04-29 21:16:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767679,2018-07-25 06:57:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767681,2018-05-29 14:23:27 UTC,I can't reproduce this with the latest bionic image.  e.g. lxc list gives:
1767681,2018-04-29 03:39:05 UTC,"I originally posted this issue on GitHub of lxc. (https://github.com/lxc/lxc/issues/2296)
The guy told me that I have to post the issue here."
1767687,2018-04-29 19:41:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767696,2018-11-11 23:48:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767697,2018-04-30 22:15:51 UTC,From DpkgTerminalLog:
1767706,2018-10-18 12:36:02 UTC,"It's a known problem, see https://community.ubuntu.com/t/brain-dump-on-guest-session-progress/3717/9 for details"
1767706,2018-07-22 04:17:33 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1767706,2018-05-22 22:19:09 UTC,Confirmed. No Guest session on login screen. Ubuntu 18.04.
1767706,2018-05-01 11:02:51 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1767711,2019-06-30 11:06:22 UTC,18.04.02... Gnome Shell. Turning off FXAA works.
1767711,2018-12-17 22:22:06 UTC,"Same problem on Ubuntu 18.04 (with Gnome Shell).
""turn off FXAA"" workaround works here too."
1767711,2018-12-04 14:27:11 UTC,"""turn off FXAA"" workaround works here too.
Ubuntu 18.10, Nvidia driver 390.87-0ubuntu1"
1767711,2018-12-04 12:33:18 UTC,"I found out that disabling FXAA (NVIDIA X Server Settings -> X Screen 0 -> Antialiasing Settings) solves this issue.
Ubuntu 18.10, Gnome 3.30, NVIDIA Driver: 390.87, X-Server: 11.0, GTX 950."
1767711,2018-12-04 12:31:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767711,2018-08-13 23:15:01 UTC,"What does ""status: invalid"" mean?"
1767711,2018-08-13 21:45:25 UTC,"Looks like the next step would be to test with an older NVIDIA driver version from the Ubuntu repository, and maybe with the slightly newer version 390.77 from the NVIDIA website also."
1767711,2018-08-14 01:56:03 UTC,xfce4 (Ubuntu) → Invalid means that Theo believes this bug is not a bug in xfce4. But it is still a bug in another component(s).
1767711,2018-08-13 18:04:18 UTC,"I suggested to test with MATE's compositing window manager ""marco"" also. Any results?"
1767711,2018-08-12 19:22:53 UTC,"Forgot to mention: after turning off display compositing in xfwm4-tweaks-settings, and running parole, the output to stderr is exactly the same as when display compositing was turned on."
1767711,2018-08-12 19:21:43 UTC,"> what output do you get when launching totem from a terminal
"
1767711,2018-08-12 18:32:11 UTC,What output do you get when opening the Totem player from a terminal window?
1767711,2018-04-30 04:57:08 UTC,"gnome-calculator (3.28.0): does not have the same problem.
gedit (3.28.1): does not have the same problem."
1767711,2018-04-30 02:56:38 UTC,Do you find the same problem in gedit and gnome-calculator? (bug 1760818)
1767711,2018-08-13 20:41:45 UTC,I didn't try 'marco' because I didn't know what that is.  Installing it now.
1767714,2018-05-01 04:25:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767714,2018-06-01 12:10:28 UTC,nvidia-kernel-common-390 needs the following additional dependencies:
1767714,2020-05-02 00:08:49 UTC,nvidia 440 for ubuntu 20.04 works fine.
1767715,2018-05-02 22:28:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767715,2018-06-19 03:58:42 UTC,"All,"
1767715,2018-06-19 03:43:17 UTC,Anything I can help with? Any additional info you may need or logs?
1767715,2018-06-01 18:20:02 UTC,"Same issue, works only the first time you suspend after reboot any time after that it fails. (Laptop Lenovo T400)"
1767715,2018-05-02 19:02:46 UTC,I'm not using the Nvidia drivers and am experiencing the same issue.
1767715,2018-04-30 17:52:46 UTC,"I could narrow this issue down to the NVIDIA driver.
Setting the graphics card to Intel eliminates the issue."
1767715,2018-04-30 02:59:55 UTC,It looks like you might have 2 or 3 different bugs here.
1767715,2018-04-30 00:14:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767715,2018-05-01 07:18:08 UTC,"When you get the issue is ""systemctl suspend"" successful at suspending?
Can you give the output of the ""systemd-inhibit --list""?"
1767718,2018-04-30 17:49:33 UTC,"I've just discovered that This bug is already reported upstream, see https://github.com/ubuntu-mate/mate-tweak/issues/38"
1767718,2018-10-01 20:19:37 UTC,This bug was fixed in the package mate-tweak - 18.10.1-0ubuntu1
1767724,2018-04-29 09:28:52 UTC,"attached is a slightly edited version of the svg file, which will save as an XAML file. unfortunately the text is placed in the wrong location, not sure why."
1767724,2018-04-29 08:57:11 UTC,thank you for taking the time to issue a report.
1767724,2018-04-29 09:04:11 UTC,"- also reproduced on Inkscape 0.91 r13725 (Jan 30 2015)
- also reproduced on Inkscape 0.92+devel (7f24a76, 2018-04-17)"
1767724,2018-04-29 09:13:24 UTC,attached is the temporary file ink_ext_XXXXXXL2L7HZ
1767724,2018-04-29 10:51:47 UTC,"Cause of this issue:
Bug #1716724 (which is actually a duplicate of the much older bug #499257)"
1767737,2018-05-18 11:59:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767738,2018-04-28 23:34:00 UTC,apport information
1767738,2018-04-28 23:34:03 UTC,apport information
1767738,2018-04-28 23:34:06 UTC,apport information
1767738,2018-04-28 23:33:58 UTC,apport information
1767738,2018-04-29 16:21:10 UTC,running with 4.17 rc2 mainline gives me this callstack
1767738,2018-05-08 18:18:10 UTC,This change was made by a bot.
1767738,2018-07-10 09:44:59 UTC,"There's a lot of reviews from Windows users saying this drive hangs if connected to a USB 2.0 port, however I see you have it connected to a USB 3.0 port (xhci_hcd)."
1767738,2018-04-28 23:34:08 UTC,apport information
1767738,2018-04-28 23:33:56 UTC,apport information
1767738,2018-04-28 23:33:55 UTC,apport information
1767738,2018-04-28 23:33:53 UTC,apport information
1767738,2018-04-28 23:33:51 UTC,apport information
1767738,2018-04-28 23:33:49 UTC,apport information
1767738,2018-04-28 23:33:48 UTC,apport information
1767738,2018-04-28 23:33:46 UTC,apport information
1767738,2018-04-28 23:33:44 UTC,apport information
1767738,2018-04-28 23:33:42 UTC,apport information
1767738,2018-04-28 23:33:41 UTC,apport information
1767739,2018-05-08 12:16:55 UTC,I must precise this is using latest published Charm 261
1767739,2018-05-08 11:10:16 UTC,"Hello Chris, yes, absolutely I referenced the previous post but I am most definitely meaning ""source"".
My config goes as follow:"
1767739,2018-05-08 10:52:34 UTC,"Florian: For the ceph* charms, ""source"" is the configuration key to be concerned with rather than ""openstack-origin"""
1767739,2018-05-08 10:16:43 UTC,Hello everyone !
1767739,2018-04-29 02:14:00 UTC,Disregard:
1767740,2018-06-28 11:10:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767741,2018-04-29 06:25:22 UTC,What's going on:
1767741,2018-04-29 12:29:21 UTC,I'm letting you know that the version in the Ubuntu Software Center (2.1.0+dfsg-4build1) and on this Launchpad page (https://launchpad.net/ubuntu/+source/projectm) don't work with Ubuntu 18.04.
1767741,2018-05-10 11:04:27 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1767741,2018-07-26 19:55:36 UTC,Thanks.  lib-canberra-gtk and edit font paths worked for me.
1767747,2018-04-29 02:54:32 UTC,"StacktraceTop:
 _check_or_repair_pv_ext (cmd=0x415c415d5b08c483, vg=0x48ea75dd394801c3, repair=-2092377068, inconsistent_pvs=0x44f6894cfa894c00) at metadata/metadata.c:3762
 ?? ()
 ?? ()
 ?? ()
 ?? ()"
1767747,2018-09-05 21:15:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767751,2019-09-12 13:41:01 UTC,Fixed in https://review.opendev.org/#/c/565055/
1767757,2018-05-20 09:19:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767757,2018-04-29 08:49:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1767759,2018-06-18 06:38:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767760,2018-04-29 07:33:55 UTC,As already noted increasing the time-out up to 6.0 seconds works for me.
1767760,2018-04-29 08:47:37 UTC,"The attachment ""Increases time-out for plymouth ping"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1767760,2018-04-30 15:47:29 UTC,Thanks for bringing this up and including a patch. Could you provide a test case for us so that we can ensure that the Stable Release Update we provide addresses the issue that you are reporting?
1767760,2018-05-01 15:14:31 UTC,@ Brian Murray
1767768,2018-08-25 21:30:07 UTC,"Also Xubuntu 18.04, and exactly the same issue.
I have solved it with a workaround:
- Run xfce4-session-settings in terminal.
- Autostartup tab.
- Edit Docky, and change docky by bash -c ""sleep 1 && docky"""
1767777,2018-05-15 12:48:13 UTC,This bug was fixed in the package nvidia-graphics-drivers-390 - 390.48-0ubuntu4
1767777,2018-04-29 14:38:35 UTC,PR: https://github.com/tseliot/nvidia-graphics-drivers/pull/21
1767779,2018-09-04 19:09:01 UTC,`setxkbmap -query` gives the following output:
1767779,2018-09-02 17:20:44 UTC,"Can you post output of `setxkbmap -query` for normal and remote desktop? Also might be good idea to report bug upstream - https://gitlab.gnome.org/GNOME/gnome-flashback/issues, I don't think this is Ubuntu specific bug."
1767779,2018-04-30 15:19:50 UTC,"Hi, below here I added each keymap, the standard, with shift and altgr
for both the standard gnome that works fine, and for the gnome
flashback. I substituted dead keys with X for the flashback session,
then you can just compare it the the normal keymap. You will see that
the international letters, and the numbers are in the right place. But
the unique keys are randomly scattered, while some of the symbols have
the posistion of the US keyboard layout."
1767779,2018-04-30 12:38:39 UTC,"Could you try to improve bug? With better steps how to reproduce this bug. Especially input source / keymap part so I can try to reproduce this. Which input source should I add, what keys should I try, actual and expected results... How do I type Swedish unique letters?"
1767779,2018-04-29 10:46:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767785,2019-03-07 19:09:44 UTC,See bug #1763100 for the solution.
1767785,2019-03-07 20:21:44 UTC,"The attachment ""console-setup-1.178ubuntu9-JNZ-1.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1767787,2018-05-18 08:18:09 UTC,"Using prime indicator plus for switching, and lightDM instead of GDM behaves as it should."
1767789,2018-04-30 16:22:32 UTC,"This is not a bug with the software that provides the release upgrade process, rather with the system after upgrading."
1767795,2018-06-04 05:15:06 UTC,apport information
1767795,2018-06-04 05:15:04 UTC,apport information
1767795,2018-06-04 21:35:50 UTC,"Hrm, I thought the logged information would include status on which profile failed to start. Bummer."
1767795,2018-06-04 05:16:45 UTC,"Hi Seth,"
1767795,2018-06-04 05:15:03 UTC,apport information
1767795,2018-06-05 07:56:16 UTC,"[....] Reloading apparmor configuration (via systemctl):
apparmor.serviceapparmor.service is not active, cannot reload.
  failed!"
1767795,2018-06-04 05:15:00 UTC,apport information
1767795,2018-06-04 05:14:59 UTC,apport information
1767795,2018-06-04 05:14:58 UTC,apport information
1767795,2018-05-23 22:37:54 UTC,"Philipp, can you please run:"
1767795,2018-06-04 05:15:02 UTC,apport information
1767799,2018-05-13 05:31:46 UTC,I encountered the same problem:
1767799,2019-11-17 20:40:54 UTC,"I had this issue and I also managed to solve it with (I think) pure luck.
I had an old LTS installed, and wanted to upgrade to 18.04. I decided to do a clean install with a live-USB. I got this error but tried anyway. The installation never finished and my system was broken. I recently tried again, but this time I chose to NOT format / and I also didn't specify to use my old /home as /home. The installation then went flawlessly and I had a working 18.04.3 installation."
1767799,2019-02-18 20:25:08 UTC,Could anyone give steps that trigger the problem?
1767799,2019-02-18 14:18:54 UTC,"This issue still occurs, only on UEFI installations. Any fix or workaround?"
1767799,2018-08-16 14:33:07 UTC,"This bug still persists: Having installed Xubuntu 18.04.1 on 2 different computers successfully, it occurred when installing a 3rd one as described above:
installation type ""something else"" with partitions:
 sdaW efi fat32
 sdaX / ext4 (to be formatted)
 sdaY swap
 sdaZ /home ext4 (existing and encrypted from previous installation)
Having typed the indications in the window ""who are you"" yields an error message ""ubi-usersetup failed with exit code 141"", a syslog entry ""ecryptfs-setup-swap failed"" and infinite waiting.
The following workaround helped to get the system running:
 installation type ""something else"" with partitions:
  sdaW efi fat32
  sdaX / ext4 (to be formatted)
  sdaY /home ext4 (this will later become swap)
 run the rest of the installation with same username and password as in the old installation - this works
 after restart, open terminal (ctrl alt F1):
  log in there
  install sudo apt-get install ecryptfs-utils
  sudo reboot
 then change UUID of /home in /etc/fstab to the one of sdaZ, being the original encrypted /home partition
 install encrypted swap with
  sudo mkswap /dev/sdaY
  new entry in /etc/crypttab: ""cryptswap1 UUID=<from the previous mkswap command> /dev/urandom swap,offset=1024,cipher=aes-xts-plain64""
  comment out a possibly automatically created swap file in /etc/fstab
  instead new entry in /etc/fstab: ""/dev/mapper/cryptswap1 none swap sw 0 0""
 If everything has worked, after restart, logging in will open the encrypted /home and sudo blkid will display sdaY and /dev/mapper/cryptswap1 as swap type partitions.
Obviously besides fixing the bug it would be helpful if the installer would offer an option how to reasonably deal with an old encrypted /home partition which has been a probably frequently used option installing previous versions of Xubuntu."
1767799,2018-05-27 16:20:50 UTC,I confirm this bug.
1767799,2018-05-11 06:08:42 UTC,"I had Kubuntu 16.04 previously, and encountered a problem doing fresh install of Xubuntu 18.04.  Used USB boot drive created from ISO image; chose to install Xubuntu; chose to manually configure; set existing partitions as previously configured, choosing to format / and /boot.  All partitions are XFS except /boot and /boot/efi which are ext2 and vfat, respectively."
1767799,2018-05-03 14:15:53 UTC,Thanks for following up. I cannot reproduce this bug with your instructions but hit several other issues. I keep this report open. Let see if there are other users affected.
1767799,2018-05-02 20:00:07 UTC,"My old installation was a Xubuntu 16.04, with this partitioning :
lsblk --fs
NAME           FSTYPE LABEL    UUID                                   MOUNTPOINT
sda
├─sda1         ntfs   WINRE_DRV
│                              1864A97E64A95EEE
├─sda2         vfat   SYSTEM_DRV
│                              24A9-EDFC                              /boot/efi
├─sda3         vfat   LRS_ESP  465D-CC63
├─sda4
├─sda5         ntfs   Windows8_OS
│                              7C2EAC202EABD206
├─sda6         ntfs   LENOVO   820E87130E870001
├─sda7         ntfs   PBR_DRV  843064043063FC14
├─sda8         ext4            b94e6bfe-76fe-4012-b152-da47020b7d2f   /
├─sda9         swap            390eb494-8f34-404c-9cfd-85c95f74d69b   [SWAP]
└─sda10        ext4            498ef751-86c1-4707-a5eb-fe6ff3ea63d5   /home"
1767799,2018-05-02 14:04:22 UTC,Thanks but there is not enough information to understand the problem.
1767799,2018-04-30 10:07:23 UTC,"in the ""who are you?"" window, I enter the username, hostname and password. I click on next. The bug occurs at this time. Perhaps because I user ecryptfs ?"
1767799,2018-04-29 20:25:30 UTC,Thank you for your bug report. Could you describe when you hit the issue and after doing what steps/selecting what options?
1767799,2018-05-03 15:21:10 UTC,From the logs of bug #1761377
1767806,2018-05-16 08:16:03 UTC,"Please report the bug upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues
and let us know the URL of the new bug you create."
1767806,2018-05-18 12:40:35 UTC,"Thanks, I've now reported this at: https://gitlab.gnome.org/GNOME/gnome-shell/issues/287"
1767806,2018-05-21 01:55:47 UTC,"This bug is now an enhancement request, because https://gitlab.gnome.org/GNOME/gnome-shell/issues/287"
1767808,2019-05-28 04:11:00 UTC,okay I install
1767808,2019-05-20 05:15:26 UTC,"Please test Linux kernel v5.1, the fix lands there."
1767808,2019-05-03 15:01:30 UTC,"Hello,
I have a DELL PA-10 wtih GM965 intel graphic card. It couldn't boot with 4.15 kernel and I have to use 4.4.0. I'm using the default driver, I didn't find an other."
1767808,2019-01-25 16:25:50 UTC,"Same here, kernel 4.15.0-43
Same Intel graphics chipset
Using lubuntu 18.04 32bit
The fix in the description worked for me."
1767808,2019-01-25 16:11:58 UTC,"Same bug here:
lubuntu 18.04 32bit on Dell Latitude D530. Fully updated today 25/1/19.
Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller
Kernel: 4.15.0-43-generic"
1767808,2019-01-25 16:22:50 UTC,Sorry - I meant that the fix described in the Bug Description worked perfectly.
1767808,2018-12-13 22:07:37 UTC,"Same bug with Linux Mint MATE, kernel 4.15.0-42, GPU Intel Mobile GM965/960, module i915.
Adding ""video=SVIDEO-1:d"" works."
1767808,2018-05-09 00:41:16 UTC,@jsalisbury It is definitely not fixed upstream.  See https://bugs.freedesktop.org/show_bug.cgi?id=93782
1767808,2018-04-30 17:36:27 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].
1767808,2018-12-23 18:54:38 UTC,"Same bug here, with Ubuntu 16.04 and kernel 4.15.0-43 (LTS enablement stack) using Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) on DELL inspiron 1525."
1767810,2018-08-10 22:04:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767810,2018-09-07 23:16:42 UTC,"Happened just during an upgrade from 16.04 to 18.04 BECAUSE I FAILED AN ANSWER TO ACCEPT A CHANGE OF A 'CONFIG FILE' -likish request and pressed Enter, that is, to default keep the old config instead of changing to the new version."
1767810,2018-09-07 23:23:03 UTC,"It was something like: ""doc-base: This file has to be changed to a newer version ... ..., would you like to change to the new version or keep the old one?"" with a default on keep. I read too quickly and chose keep with a compulsive ENTER hit. My Bad. Any one remembers the file name ?"
1767811,2018-04-30 06:21:58 UTC,Thank you for your information.
1767811,2018-05-03 22:46:53 UTC,Awaiting response for Pawel's comments.
1767811,2018-05-04 03:18:46 UTC,"@pasuder, sorry for the delay. for your questions:"
1767817,2019-02-20 08:11:41 UTC,"Yes, it's fixed in the Disco serie, I've uploaded a test package to https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16410497"
1767817,2019-03-08 09:54:21 UTC,"Hello Mordi, or anyone else affected,"
1767817,2019-03-08 09:59:32 UTC,"Hello Mordi, or anyone else affected,"
1767817,2019-02-20 12:26:05 UTC,"It seems to work well. Sometimes it hang up, shows ""searching"" in the right bottom corner of nautilus window. If I delete back some characters in the input field, it starts to work again."
1767817,2019-02-19 17:02:47 UTC,"ok.
Thank you for hearing us.
I'll be glad to help making test if needed."
1767817,2019-02-16 17:06:09 UTC,"Thatoo, see my previous comment #8 why this bug occurs."
1767817,2019-02-17 22:26:15 UTC,"It is actually for me a reason to finally drop Ubuntu.
At least if they decide to abandon Ubuntu Touch and Unity to move back to Gnome, they should at least do it good and nor providing an OS that doesn't provide a proper modern search tool."
1767817,2019-02-17 19:28:47 UTC,"If the users think it is important, developers should raise the level of
priority."
1767817,2019-02-17 19:04:12 UTC,"Ubuntu 18.10 with tracker installed:
With Tracker Search Provider by hamiller Plugin for Gnome Shell, Full-text Search works, but is limited to 5 results as or2V has written. Full text search within Nautilus does not.
I still do not understand the classification of the bug on low priority. I can't believe this."
1767817,2019-03-08 16:16:02 UTC,1:3.26.4-0~ubuntu18.04.4 fixed this bug for me.
1767817,2019-02-17 17:55:53 UTC,"@or2v: Yes, Gnome Documents does not search plain txt-files. I read a while ago that it is so by the developers' decision."
1767817,2019-02-19 16:34:06 UTC,"It's a logic error in a patch, let's get that resolved (note that it's already fixed in the current Ubuntu serie which uses tracker)"
1767817,2019-03-08 22:11:19 UTC,1:3.26.4-0~ubuntu18.04.4 fixed this bug for me too!
1767817,2020-02-13 09:01:31 UTC,I have this issue in 19.10.. What do I do?
1767817,2019-03-22 19:35:10 UTC,"Ok guys, how long 'till this drop into updates? Still on proposed..."
1767817,2019-03-23 19:29:38 UTC,Thank you for taking the time to verify this stable release fix.  We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE).  Please remove the verification-done tag and add one for the release you have tested the package in.  Thank you!
1767817,2019-03-23 20:00:17 UTC,"@Brian, that was changed because it doesn't seem to get validated despite being verification-done-bionic, do you know why?"
1767817,2019-03-25 08:51:15 UTC,"The verification of the Stable Release Update for nautilus has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1767817,2019-03-25 08:52:15 UTC,"Thank you for testing the package, I have promoted it to bionic-updates. The cosmic counterpart still needs verification though. Could someone test the 18.10 package so we could get it released as well?"
1767817,2019-03-25 09:01:32 UTC,This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.4
1767817,2019-05-27 11:55:54 UTC,The 1:3.26.4-0ubuntu7.2 update in cosmic works as intended
1767817,2019-05-28 17:05:37 UTC,This bug was fixed in the package nautilus - 1:3.26.4-0ubuntu7.2
1767817,2019-12-14 12:44:15 UTC,"That's right but you can install the fix under 18.04.3, no need to wait 18.04.4...
You can install the fix here as explain earlier : https://launchpad.net/ubuntu/+source/nautilus/1:3.26.4-0ubuntu7.2"
1767817,2019-12-16 09:26:20 UTC,"I don't know how to help you more, everything is written some post before. Have you read
https://wiki.ubuntu.com/Testing/EnableProposed
and
https://launchpad.net/ubuntu/+source/nautilus/1:3.26.4-0ubuntu7.2
?"
1767817,2020-06-21 09:56:34 UTC,I have this issue in 20.04
1767817,2019-03-21 00:21:17 UTC,"1:3.26.4-0~ubuntu18.04.4 also fixed this bug for me in Bionic, thanks!"
1767817,2019-02-17 17:06:10 UTC,"Same problem with a fresh install of Ubuntu 18.10, with Gnome Files/Nautilus 3.26.4.
Tracker is not installed by default. I had to install it afterward. Works fine in command line into the terminal. But this is not enough."
1767817,2019-02-14 11:24:20 UTC,Did anyone manage to get a clue on where is that problem coming from? Ubuntu? Nautilus? Gnome? and how to solve it?
1767817,2019-02-14 19:17:20 UTC,"Nope, see previous posts."
1767817,2018-04-29 20:17:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1767817,2018-04-30 13:51:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767817,2018-05-02 12:03:16 UTC,"Sorry, but the process seems a bit too complex for me."
1767817,2019-02-17 10:35:49 UTC,"@Mordi, tracker can be installed, which some of the commenters here seemed to have done, also the current Ubuntu serie installs it by default now"
1767817,2018-05-04 13:59:11 UTC,"I think nautilus 3.26 should do full text search. If not, there are two possibilities
Remove the option from the search menu."
1767817,2018-05-08 17:05:59 UTC,I have the same problem. Does also not work with the nautilus version from flathub.
1767817,2018-05-17 19:54:29 UTC,"I have three computers, two desktops and one laptop. Two of them has a newly installed Ubuntu 18.04 and one has an upgraded 18.04 (from 17.10). In one desktop I installed ubuntu 18.04 in virtualbox. For every operating system I installed tracker. Full text search in nautilus doesn't work in any of them.
It must be a bug."
1767817,2018-05-20 15:45:19 UTC,Gnome developers think that this issue is a decision made by Ubuntu:
1767817,2018-06-27 14:35:23 UTC,Same here with a fresh installed Ubuntu 18.04...
1767817,2018-07-13 09:26:34 UTC,Same here with Ubuntu 18.04. Full text search ist a key function for an os. It's ridiculous that an os isn't able to process a full text search in 2018.
1767817,2018-08-02 23:37:56 UTC,Hi !
1767817,2018-05-03 15:35:24 UTC,"I kind of figured this out. In addition to Tracker, you need Gnome Documents and gnome-shell-extensions installed. Launch Gnome Documents, and it will index your files. Now you will be able to search by content from Gnome Documents and Gnome Shell, but still not from Nautilus. Perhaps this is because Ubuntu installs an older version of Nautilus (3.26)."
1767817,2018-08-03 18:58:36 UTC,"Gnome Documents doesn't find any documents either.
I resigned and use Recoll instead It's very fast and reliable."
1767817,2018-08-03 19:51:00 UTC,"Why don't want the developers fix this (and other) bug? Whether do they
want me to use the non-LTS releases? Or do they want me to use other
distros than Ubuntu?
So I would like to use Ubuntu 18.04 with full gnome functionality without
bugs. (e.g. without memory leak...)"
1767817,2018-08-12 19:57:35 UTC,"Full text search should work out of the box. Every modern OS has this. IMHO, the importance should be changed to ""high"" instead of ""low""!"
1767817,2018-09-28 16:38:52 UTC,Related:  Bug #1702878 - Cant add folders to Search in Gnome Control Center
1767817,2018-11-11 15:51:31 UTC,"Same with me.
Very annoying.
Ubuntu 18.10 installed.
Tracker full text search works in command line ($tracker search WordToSearch).
No full text search with the graphical file manager."
1767817,2018-11-22 11:43:19 UTC,"I registered just to post on this bug report.
I'm a dev trying to switch over to Linux and I chose Ubuntu assuming it would be the most functionable distro in 2018.
However I simply cannot make the transition until type-as-you-go search + indexing is not working just like on macos in 2013 and even now on windows 10."
1767817,2018-12-29 23:41:40 UTC,"Even after installing Nautilus 3.30 from the staging Gnome PPA (https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging?field.series_filter=cosmic), the full text search isn't working in Nautilus, but does in the terminal (tracker search xyz)."
1767817,2019-01-04 16:28:58 UTC,Any ideas of a solution?
1767817,2019-02-10 23:10:39 UTC,Does anybody know what to change in the source code to made FTS work? I can compile and install it...at my own risk.
1767817,2018-08-03 18:36:51 UTC,"You don't need Nautilus to search documents by content: for that, install gnome-documents. However, there is a bug: if you search documents from Gnome Shell, Gnome Documents will eventually crash and need to be restarted. To get around this bug, you have to disable the functionality from Settings/Search. Thereby, the only way to search documents by content is from Gnome Documents -app."
1767817,2019-02-14 18:23:37 UTC,Does anyone knows if it works again with ubuntu 18.10?
1767822,2018-05-11 15:16:10 UTC,Actually using the tightvncserver or vnc4server packages also give a black/grey screen in the viewer ...
1767822,2019-08-24 19:42:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767825,2018-12-11 23:48:17 UTC,"In my case crash only when I activate the gaussian effect.
crash dump attached"
1767831,2018-05-08 13:39:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767831,2018-05-08 13:42:20 UTC,I am unable to update my system.
1767832,2018-04-30 02:22:19 UTC,"Hello Aurélien,"
1767832,2018-04-30 07:21:21 UTC,"Adding the linux package, as this should be a kernel issue."
1767832,2018-05-07 12:25:22 UTC,"Hi,"
1767832,2018-05-07 12:46:21 UTC,The attachment...
1767832,2018-07-07 04:17:28 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1767832,2018-09-20 13:01:44 UTC,"I just found time in order to debug this problem. I found a ""bug"" in the hid-multitouch driver. I also enabled the confidence management provided by this touchpad in order to avoid pointer movements when we are using the keyboard."
1767832,2018-09-20 14:06:56 UTC,I think this commit fixes your issue?
1767832,2018-09-20 14:49:00 UTC,damned!!!! I did all this job for nothing... I didn't see the patch but seems it's exactly I encountered and the solution I found it seems that it fixes the issue right!
1767847,2018-08-11 11:11:53 UTC,Video is not available anymore.
1767847,2018-04-29 20:45:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1767847,2018-08-12 14:42:10 UTC,I set the video to be public; you should be able to view it
1767854,2019-04-29 17:52:07 UTC,Let me give you the digest from the (german) site mentioned in comment #1:
1767854,2020-06-25 16:05:08 UTC,Ubuntu now depends on duplicity and Python-gi again. Shouldn’t get in this state anymore.
1767854,2018-04-30 07:16:51 UTC,Hello
1767855,2020-06-22 14:46:29 UTC,"Looks like this is corrected in the upstream code, which we now have in focal."
1767855,2018-04-30 03:04:28 UTC,"@slavicd: It's not fix committed in Ubuntu (which is what the package state would be). It's fixed upstream, so the next MRE (Micorelease Exception) update of PHP will pick up the fix (Presuming it's in the release)."
1767855,2018-04-30 00:21:44 UTC,Apparently it's already fixed in master: https://github.com/php/php-src/commit/58c778ba6092798a6478d2bebc581f90a0a8cbac#diff-e59388f3109141d8fd15ee820f2b3820
1767855,2018-04-30 00:14:41 UTC,Yeah that would be ideal.
1767855,2018-04-29 23:33:51 UTC,If you could direct me towards the right repository that would help.
1767855,2018-04-29 23:24:58 UTC,"The default file contents are inherited directly from Debian and Ubuntu is
unlikely to add delta just for typos/grammatical errors. Please consider
filing with Debian?"
1767855,2018-04-30 00:04:35 UTC,"I just found out that the bug is all the way upstream - on php.net. This means I have to submit a bug with php, not Debian, then, I reckon."
1767857,2018-06-14 22:15:55 UTC,qemu-system-x86 broken when running kernel 4.4.0-128 as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-07-02 22:38:07 UTC,qemu-system-x86 broken when running kernel 4.4.0-130 as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-07-23 16:36:17 UTC,qemu-system-x86 broken when running kernel 4.4.0-131 as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-08-05 16:08:42 UTC,Upgraded to xubuntu 18.04.1 (sudo do-release-upgrade) and kernel 4.15.0-29-generic. Same problem when running qemu-system-x86 (1:2.11+dfsg-1ubuntu7.4) - black screen displays and qemu-system-x86 runs at 100% cpu indefinitely. Totally black screen immediately - no bios flashes.
1767857,2018-08-06 04:37:28 UTC,"That implies that for you it is some other config than the current kernel (or a combination thereof), so far multiple people including me have not been able to reproduce this - so to further fix things we have to spot what is different within your setup triggering the issue for you."
1767857,2018-08-06 08:04:12 UTC,Christian are you testing this on real hardware or on 32bit VMs?
1767857,2018-08-06 09:37:53 UTC,"Hi Ante, being a Kernel introduced issue Jürg was testing it (not me as I had no spare HW at the time anyway) - see comment #24."
1767857,2018-08-07 02:35:10 UTC,qemu-system-x86 broken when running kernel 4.15.0-30-generic as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-08-13 22:03:38 UTC,"I booted from the Xubuntu 18.04.1 Install ISO, installed qemu, copied and modified some files to adjust for user name and permissions, and ran my Windows 10 qemu-system-x86 script - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely). Totally black screen immediately - no bios flashes."
1767857,2018-08-14 22:44:38 UTC,qemu-system-x86 broken when running kernel 4.15.0-32-generic as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-08-15 11:20:01 UTC,"Chances are slim that this will fix itself automagically. And as long as we're not able to reproduce this, it's going to be difficult. I'll try to take another look in a couple of days once
the current kernel respin frenzy is over."
1767857,2018-08-17 11:33:50 UTC,"Since it appears that the problem is not my Xubuntu software setup (see post #33), I thought that maybe it is my hardware setup, which is rather old. So here is my hardware setup for you to consider:"
1767857,2018-08-23 21:46:53 UTC,qemu-system-x86 broken when running kernel 4.15.0-33-generic as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-09-12 12:10:10 UTC,qemu-system-x86 broken when running kernel 4.15.0-34-generic as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-10-02 20:03:02 UTC,qemu-system-x86 broken when running kernel 4.15.0-36-generic as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-10-24 11:20:22 UTC,qemu-system-x86 broken when running kernel 4.15.0-38-generic as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-11-15 19:54:48 UTC,"I could not upgrade from Xubuntu 18.04 to Xubuntu 18.10, due to possible demise of 32-bit support, so I have done a fresh install of Xubuntu 18.10 64-bit. Windows 10 guest will still not boot, but now I get the BIOS flash and the Windows 10 Logo, on which it stays indefinitely with 100% cpu. Here is my qemu command:"
1767857,2018-11-16 15:31:10 UTC,FIXED!!!
1767857,2018-11-19 13:20:30 UTC,"So, in Cosmic (18.10) it's fixed, but remains in Xenial (16.04) and Bionic (18.04)?"
1767857,2019-04-16 14:18:44 UTC,"/usr/bin/qemu-system-i386 -name ldap -S -machine pc-1.0,accel=kvm,usb=off -cpu host -m 1072 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 2a6c478a-9bd8-40f6-83cd-b2bf681ef5a0 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/ldap.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/opt/VIRT/LDAP/vda.raw,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:4a:93:0a,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/ldap.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -device usb-tablet,id=input0 -vnc 127.0.0.1:59 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7"
1767857,2018-05-29 15:13:42 UTC,"I'm not able to reproduce this on a physical host. Works just fine for all the 32-bit kernels that I tested. When you say 'black screen', do you not get anything at all? Not even some BIOS flickering in the beginning?"
1767857,2018-05-28 06:16:01 UTC,Host needs to be 32bit. Guest arch is irrelevant for the problem.
1767857,2018-11-19 15:14:12 UTC,"Andreas,"
1767857,2018-05-28 05:44:34 UTC,"You also said this only applies to the full 32bit stack for you (32bit host + guest) is that correct?
Had you the chance to try the same on 64bit host to know if this is a real constraint to see this issue? It would at least explain why I didn't see it as I had 32bit-Guest on 64-bit Host."
1767857,2018-04-30 13:29:04 UTC,qemu-system-x86 broken when running kernel 4.4.0-121 as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-05-02 20:39:03 UTC,"Could you please paste the full command line that the qemu process is using (ps fauxwww should be enough), and perhaps a xml dump of the vm, like this: ""virsh dumpxml <vm-name> > vm.xml"" and attach that to this bug as well."
1767857,2018-05-03 05:30:23 UTC,"Also a per qemu thread view is often useful, you might also add
$ pidstat -t -p <pidofqemu>"
1767857,2018-05-03 16:03:18 UTC,"QEMU command:
qemu-system-i386 -name windows-10-pro -pidfile /tmp/windows-10-pro.pid -m 2047M -cpu host -smp 1 -enable-kvm -rtc clock=host,base=localtime -machine type=ubuntu -k en-us -drive file=/media/V-BOX/KVM/Win10/Win10-VM.qcow2,if=virtio,media=disk,format=qcow2,index=0 -drive file=/media/Big_NTFS/G/Backup/KVM/Win10/Win10-VM_Backup_Disk.qcow2,if=virtio,media=disk,format=qcow2,index=1 -drive file=/media/Shared/E/Win10-VM_Page_File.qcow2,if=virtio,media=disk,format=qcow2,index=2 -usb -device usb-ehci,id=ehci -device usb-host,vendorid=0x13fe,productid=0x3100 -device usb-host,vendorid=0x090c,productid=0x1000 -device usb-host,vendorid=0x14cd,productid=0x1212 -device piix3-usb-uhci -device usb-tablet"
1767857,2018-05-04 06:37:22 UTC,"Hi Skipper,
thanks for sharing the qemu cmdline, there is nothing odd in this and I can run a system like that (not a win 10 guest) just fine."
1767857,2018-05-04 11:35:03 UTC,ChristianEhrhardt:
1767857,2018-05-04 13:45:21 UTC,"For the per thread view use:
 $ sudo pidstat -t -p <pidofqemu>"
1767857,2018-05-09 01:37:29 UTC,qemu-system-x86 broken when running kernel 4.4.0-124 as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-05-09 02:01:52 UTC,"sudo pidstat -t -p 4063
Linux 4.4.0-124-generic (desktop) 	05/08/2018 	_i686_	(2 CPU)"
1767857,2018-05-03 06:00:09 UTC,This change was made by a bot.
1767857,2018-05-09 11:31:09 UTC,Also fails (4.4.0-124 kernel) when trying to boot from WinPE ISO - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-05-09 05:14:05 UTC,"Hmm,
so it is not even burning CPU for anything neither in the Host (usr ~=qemu, sys ~=kernel) nor in the guest itself (~=guest).
The KVM exits confirm that, it doesn't do a a lot entry/exit is the pass in/out of guest context and the only meaningful exit means it emulates an instruction."
1767857,2018-05-27 18:53:24 UTC,"I can confirm that, while 4.4.0-119 works just fine, 4.4.0-121 doesn't work."
1767857,2018-05-25 08:17:41 UTC,"I've hit the same problem on 32bit 14.04 with both latest 3.13.0-149 and 4.4.0-127 kernels. I can confirm it works with 4.4.0-119. I could provide some kernel version bisection (both 3.13 and 4.4), but only over the weekend. These are production machines during the week :/"
1767857,2018-05-24 05:25:21 UTC,"Odd, I don't remember where I had the -224 kernel from exactly - even in proposed it isn't :-/.
The next one still is a bit out it seems  per bug 1772960
I agree that the last you can currently get is linux-image-generic 4.4.0.127.133
But with that as well it just works fine for me."
1767857,2018-05-28 05:45:30 UTC,And given we have two reporters that point to the upgrade lets tag it a regression due to that.
1767857,2018-05-23 21:13:48 UTC,qemu-system-x86 broken when running kernel 4.4.0-127 as well - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767857,2018-05-11 21:35:31 UTC,"""... try the even newer 4.4.0-224 kernel?"""
1767857,2018-05-11 07:43:54 UTC,"I re-deployed one of my systems to Xenial.
For the complexity of going back I took what kernel is currently active which was 4.4.0-224
With that I spun up the Xubuntu 32 bit iso you referred."
1767857,2018-05-09 22:04:27 UTC,Also fails (4.4.0-124 kernel) when trying to boot from xubuntu-18.04-desktop-i386 ISO - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely).
1767858,2018-04-29 20:23:18 UTC,Could everyone see this same bug?
1767858,2018-04-29 20:26:20 UTC,I cannot be vertified so I changed the status to Incomplete.
1767858,2018-04-29 20:31:22 UTC,I now can understand
1767859,2018-04-30 19:47:21 UTC,"This is not a bug with the software performing the release upgrade, rather with the system after the upgrade."
1767860,2018-04-29 20:45:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1767860,2020-01-25 18:00:11 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1767860,2020-03-26 04:17:42 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1767862,2018-04-29 21:03:57 UTC,"GTK+ only supports integer scaling, so anything other than 2x is hard to impossible. You can adjust font sizes and DPI, however. This is available in Appearance → Fonts (or open through MATE Tweak → Windows → Fonts)."
1767862,2020-10-05 23:58:13 UTC,Linux Mint 20 has added fractional scaling utilizing xrandr. This might be something to consider for mate too?
1767868,2018-05-16 19:11:49 UTC,"It will be very nice to have an update for that very important feature as of today Oval hole (in footprint) is a nice idea to support ""plated-through cutouts / slots"" but the generated Drill file with ""G85 Drill Drag callouts."" is not supported by any manufacturer as they all or > 90% support only Slots and cut-outs by doing:
SMD pads on both top and bottom layers and then drawing the Slots/Cutouts on Edge.Cuts(Board Outline) layer
See the link of multiple PCB Manufacturer:
- OSHPark http://docs.oshpark.com/troubleshooting/cutouts-and-slots/
- MacroFab https://macrofab.com/blog/plated-slots-stop-fitting-square-pegs-round-holes/
- SeeedStudio http://support.seeedstudio.com/knowledgebase/articles/1084123-how-do-plated-through-holes-slots-shows-on-the-ger
- Eurocircuits https://www.eurocircuits.com/blog/slots-and-cut-outs/"
1767868,2018-04-30 09:37:42 UTC,"@Jakub, Kicad defines this as a ""cutout"".  A ""slot"" (in Kicad) is an elongated hole (i.e. something that could be cut with a single translation of a milling cutter with a given diameter)."
1767868,2018-04-30 09:41:10 UTC,See also https://bugs.launchpad.net/kicad/+bug/1536319.
1767868,2018-04-30 03:58:33 UTC,It's defined as drawing on Edge Cuts layer where copper of filled zone on both sides of PCB is touching Edge Cuts drawing (from both sides - from the expected plated slot and PCB side). Via inside slot is only information for manufacturer as defined in OSH park docs.
1767868,2018-04-29 23:44:50 UTC,"@Jakub, I'm not sure what I'm looking at here.  What is it that is supposed to be a slot?  And how was it defined in Kicad?  (As a drawing on the Edge Cuts layer, or as an oval PTH?)"
1767868,2018-04-30 06:54:12 UTC,Please attach a board file such that it is easy to understand your exact layout. But I admit I am not sure exactly how plated slots are defined before I read #3.
1767878,2018-05-03 02:33:39 UTC,"The stack trace is hinting that something is going wrong in the read buffer in snapd-glib. Could be inside snapd-glib itself or external corruption. Nothing stands out, but the code is relatively complex..."
1767878,2019-06-05 13:54:19 UTC,There was not report post 3.28.1-0ubuntu4.18.04.1 so assuming it has been fixed
1767893,2018-10-16 02:57:04 UTC,"Same issue on my Dell Precision M3800, there's no such an issue on Ubuntu 16.04. I did a fresh install of Ubuntu 18.04.1 and upgrading the kernel to 4.15.0-36 right after the installation finish, but the system still freezes randomly. Sometimes the Gnome 3.28 will freeze at all and then fall back to the login screen (asking for a re-login), and then later on, kernel panic on CPU. I have no idea why this will happen."
1767893,2018-11-02 19:28:28 UTC,"Ubuntu 18.04 fresh install, with multiple gnome extensions."
1767893,2018-11-07 18:17:42 UTC,"Hi,"
1767893,2018-11-08 07:34:53 UTC,I just wanted to point out that I did not install indicator-multiload or any extensions.
1767893,2018-11-12 18:23:37 UTC,"I am having the same issue with 18.04LTS/Gnome several times a week: Everything freezes except mouse cursor. Time in the status bar freezes, tooltips don't show up. SSH works and the system seems to be healthy otherwise. Can switch CapsLock/NumLock on the keyboard, but otherwise Keyboard isn't responsive. Ctrl+Alt+F2 doesn't work. REISUB combo works"
1767893,2019-01-16 15:39:38 UTC,"@Dmitry: I have 32 GB of memory on my laptop and 16 GB on desktop. It does not happen with Kubuntu or Cinnammon over Ubuntu, or Fedora. Only pure Ubuntu (don't remember the name of their Gnome 3 fork)."
1767893,2019-04-19 00:23:23 UTC,Any luck resolving this issue?
1767893,2019-05-11 18:31:19 UTC,"Happened to me just now while resizing the width of the graphs, froze after a few seconds, then entered into a login loop. Could fix it with CTRL-ALT-F2, login, then 'apt-get purge multiload-indicator'. Had the login-loop happened some time later, I would not have associated the problem with the indicator app, and I would have never been able to fix it myself, so this this would have effectively bricked my laptop. Please fix or disable the app before it does more damage."
1767893,2019-05-26 19:09:26 UTC,"The regular momentary freezing I experience on my Ubuntu 18.04 is so annoying!! I cannot base it on anything substantial. I don't know how to even fix it once and for all, except being forced to reboot my laptop every time it happens."
1767893,2019-05-27 08:36:18 UTC,"This happens to me too.
I had top running:
Reason for this Ubuntu 18.04 freeze seems to be indicator process...
Top line:
COMMAND:indicator-+ PR:20 NI:0 VIRT:29,255g RES: 0,014t SHR:216 $CPU5% %MEM:94,2
This indicator process floods my memory... No way to stop it after login!"
1767893,2020-03-16 18:40:37 UTC,Dino says:
1767893,2018-11-16 14:16:02 UTC,"After inspecting more carefully, I believe it may be related to memory limit. I have 8GB of RAM on both machines and I usually have a lot of tabs open. I noticed that memory usage is above norm prior to freeze (around 95%)."
1767893,2018-10-11 15:24:01 UTC,"same issue here.  my computer started freezing randomly when i use google translate since 13:00h NL time today.
this did not happen before today.  i upgraded from 16.04 some three days ago."
1767893,2018-07-30 09:28:58 UTC,I have the same problem. UI seems unusable randomly.
1767893,2018-07-21 08:26:11 UTC,"Confirmed. My system freezes randomly. I used gnome, but the problem occured extremely frequently. Now I am using XFCE and the freeze have decresed but exists. The system stops and about half minute will be usable again.
I think it correlates to high cpu usage."
1767893,2018-07-20 15:38:30 UTC,"I have installed the Ubuntu 18.04 and it's impossible to use the system, it's freezing constantly. I was using Ubuntu 17.10 with no issues. My laptop is a MSI GS60 Ghost Pro."
1767893,2018-07-06 21:21:50 UTC,"Thank you dino99, 'gnome-shell-extension-system-monitor' (https://extensions.gnome.org/extension/120/system-monitor/) works fine and it seems to be a good replacement for indicator-multiload."
1767893,2018-06-09 15:00:45 UTC,Kubuntu 18.04 on amd64 freezes now and then for me too. Haven't found any correlation yet.
1767893,2018-05-20 08:28:16 UTC,"Same. Just installed 18.04, and indicator-multiload kept me in the login loop. Had to uninstall in maintenance mode"
1767893,2018-04-30 22:16:23 UTC,"Confirmed. I had the same behaviour. After installing ubuntu 18.04, then the system indicator multiload, an infinite loop login came up. I had to uninstall the indicator to get a successful login."
1767893,2018-04-30 19:49:32 UTC,"Thanks for the suggestion dino99.  I installed https://extensions.gnome.org/extension/120/system-monitor/ and while it doesn't display system load it does display cpu, gpu, network, disk, and even thermals.  All-in-all a nice little extension.  Thanks!"
1767893,2018-04-30 11:32:24 UTC,"oops,
not 'gnome-shell-shell-extension-system-monitor' but 'gnome-shell-extension-system-monitor'"
1767893,2018-04-30 11:31:09 UTC,"You should not use that old 'indicator-multiload' but the now well integrated 'gnome-shell-extensions' & 'gnome-shell-shell-extension-system-monitor' (all from archive), then activate them via 'gnome-tweaks'"
1767893,2018-04-30 09:48:59 UTC,"I experience similar issues as reported above. At the moment, I can't reproduce the GUI lockup (I had that earlier though). However, the GUI feels slow. gnome-shell and indicator-multiload need almost 20% of the CPU."
1767893,2020-06-10 12:38:59 UTC,"I aggree with Tomislav. It's still broken in 20.04. If there's no intent to upgrade or fix it, then it should be removed from available packages."
1767893,2018-08-06 00:28:30 UTC,"Same issue here as well. I had no problems under 17.10. After doing a fresh install of 18.04.1, I started having repeated system lock ups and freezes. Fiddling with anything in the Settings app seems to increase the chances of a lockup, but I haven't been able to correlate it to anything substantial. The lockups require a hard reboot to resolve.
I have a 2017 Razer Blade laptop."
1767896,2018-05-21 10:42:59 UTC,"Both seed proposals merged. I believe nothing else needs doing, and tomorrow's dailies should be fixed then."
1767896,2018-05-10 12:22:08 UTC,I've created channels for stable/ubuntu-18.04 and stable/ubuntu-18.10
1767896,2018-05-10 10:21:11 UTC,"I am not a publisher for that snap, so I can't do that. I'll ask on #snapd to see if anybody is."
1767896,2018-05-23 00:14:01 UTC,This issue fixed in daily build bionic-desktop-amd64.iso (20180522)
1767896,2018-05-10 10:52:33 UTC,Also proposed code changes to ubuntu seeds:
1767896,2018-05-24 03:42:55 UTC,Confirmed fixed in http://cdimages.ubuntu.com/daily-live/20180522/
1767896,2018-04-30 07:27:23 UTC,"First of all, kudos for using a nice machine :-)"
1767896,2018-10-25 02:33:18 UTC,"If the problem still happens in the final release of 18.10:
http://releases.ubuntu.com/18.10/ubuntu-18.10-desktop-amd64.iso"
1767896,2018-10-25 16:43:30 UTC,"Yes, this is with the 18.10 final release."
1767896,2018-10-25 17:05:39 UTC,"Hello, there is a difference between the live installer session where snaps are supported to a limited degree and the persistent image where they are not supported at all. I'm very sorry for the inconvenience. I don't know if it is feasible to disable snapd in that context (through the persistence layer)."
1767896,2018-10-25 17:35:21 UTC,So persistence is no longer possible?  That's very disappointing :(  Perhaps the option should be removed.
1767896,2019-10-10 09:48:13 UTC,"Moving it back to Won't fix, for snapd at least. I don't see an issue here that snapd itself _can_ fix."
1767896,2018-05-10 10:09:53 UTC,Code for fetching seeded snap while image building:
1767896,2018-10-24 23:45:40 UTC,"The above ""confirmed fixed"" link is broken."
1767896,2018-05-10 10:06:25 UTC,"gtk-common-themes is not published in channel ""stable/ubuntu-18.04"", thus the image building will fail."
1767896,2018-04-30 01:05:52 UTC,this could be a special case of bug 1729867
1767896,2018-05-10 08:03:42 UTC,it looks like the seed is missing gtk-common-themes
1767896,2018-04-30 14:48:56 UTC,"It is a nice machine :) This one was signed by David Hill, so it's a real treasure :)"
1767896,2018-04-30 14:53:13 UTC,"Hmm, is there an edit button here somewhere???"
1767896,2018-04-30 23:28:43 UTC,I've verified that this can be reproduced when booted from a flash drive. As above: extract the 18.04 ISO to a FAT32 drive. UEFI boot it. Create a persistence file and a persistence boot stanza.  Boot that.
1767896,2018-05-03 00:27:29 UTC,"I see that this but report is ""incomplete"".  In case it's waiting on the snap version it's 2.32.5."
1767896,2018-05-03 00:27:49 UTC,*bug* report ;)
1767896,2018-05-10 08:29:31 UTC,"If you seed a snap, then you also need to seed that snap's base, and snaps providing any plugs that snap requires, otherwise it'll fail to seed."
1767896,2018-05-09 11:11:43 UTC,"After finishing the installation and reboot, this issue could be observed before connecting to internet. snapd restarts again and again and consuming high percentage of cpu.
(Daily Build image: Ubuntu 18.04 LTS ""Bionic Beaver"" - Release amd64 (20180508)%)"
1767896,2018-05-09 11:13:53 UTC,"seeded snap in Ubuntu 18.04 LTS ""Bionic Beaver"" - Release amd64 (20180508)%"
1767896,2018-05-09 11:25:52 UTC,"That's very interesting!
Could you paste the output of ""snap tasks --last=seed"" ?"
1767896,2018-05-10 03:06:42 UTC,"output of ""snap tasks --last=seed"""
1767896,2018-05-10 03:19:38 UTC,Note that this issue doesn't happen with official released image ubuntu-18.04-desktop-amd64.iso.
1767896,2018-05-09 10:49:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767901,2019-07-26 20:51:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767901,2020-01-28 09:40:22 UTC,"Thank you for your bug report. Looks like the issue has been fixed in newer versions/Ubuntu series
https://bugs.launchpad.net/ubuntu/+source/espeakup/1:0.80-11
It might be a candidate for LTS SRU though but probably low priority since it seems we didn't get much reports about the issue and it's probably not the most installed package by our users"
1767902,2018-05-24 09:14:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767902,2018-05-15 10:19:19 UTC,"I was able to make this work by changing ""3.0 (quilt)"" in /usr/share/equivs/template/debian/source/format
to ""1.0"" (without quotes) as it was in earlier versions."
1767911,2019-09-08 22:34:52 UTC,"dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  man-db -> desktop-file-utils
 packages' pending triggers which are or may be unresolvable:
  man-db: /usr/share/man
  desktop-file-utils: /usr/share/applications
  gconf2: /usr/share/GConf/gsettings
  ufw: /etc/ufw/applications.d"
1767932,2018-05-05 21:16:39 UTC,Same shit on GTX 1050 Ti
1767932,2018-11-06 07:41:31 UTC,I get this every couple of days on our CI - from processes which access the GPU. nvidia-driver 396.24.02. Here are some dmesg warning from various failures
1767932,2018-10-19 19:32:37 UTC,"Getting this ""task kworker blocked for more than 120 seconds"" with nvidia-drivers-390 on Ubuntu 18.04 (Kernel 4.15.0.36-generic). I have a GTX 1070Ti and GTX 770 installed."
1767932,2018-09-06 01:42:16 UTC,"I had this exact problem today (same message in `dmesg`) which I found while investigating a hang of anything CUDA-related, appearing out of nowhere after my setup had been working for a while."
1767932,2018-05-05 23:55:03 UTC,"Kirill, looks to me like you are using the open source nouveau driver.
This is for the proprietary binary nvidia driver."
1767932,2018-11-06 07:44:30 UTC,BTW: Linux lb-santi 4.4.0-127-generic #153~14.04.1-Ubuntu SMP Sat May 19 14:00:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
1767932,2018-05-05 17:06:44 UTC,"Cannot confirm but when using nvidia through nvidia-prime, I get kernel hangs at seemingly random times. Does not occur with intel or without nvidia drivers"
1767932,2018-04-30 05:35:06 UTC,Apport report attached
1767932,2018-05-04 12:23:56 UTC,Same on 396.24-0ubuntu0~gpu18.04.1
1767932,2018-05-03 22:51:32 UTC,"Hang on  nvidia-driver-396                          396.18-0ubuntu0~gpu18.04.9
as well."
1767932,2018-04-30 07:06:41 UTC,Nvidia bug report
1767932,2018-04-30 05:36:45 UTC,"Card is a GTX770, doesn't seem to be reported anywhere."
1767932,2018-05-05 17:04:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767933,2020-01-15 05:31:34 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10718"
1767933,2020-05-08 00:28:40 UTC,"Reviewed:  https://reviews.mahara.org/10718
Committed: https://git.mahara.org/mahara/mahara/commit/b80a2a7b178733f1f119facc954adff1531b1d5a
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1767940,2018-07-30 03:08:21 UTC,This bug is very difficult to diagnose from the log file. Have you seen the bug again?
1767942,2018-08-24 19:34:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767955,2018-07-20 03:40:42 UTC,"I also discovered this, and cyphermox merged my patch a while ago. (https://github.com/CanonicalLtd/netplan/pull/27/commits/53a570308a9ac23d05dac70de43b64076caa0ffb) but the fix isn't in 0.36.3."
1767955,2020-04-14 13:56:42 UTC,Seems like the docs have been updated: https://netplan.io/reference#properties-for-device-type-ethernets:
1767959,2018-05-01 09:21:43 UTC,When i set Default editor Sublime and than again Atom this problem fixed
1767959,2018-04-30 15:43:17 UTC,default editor is atom
1767961,2019-01-07 20:51:11 UTC,I'm also seeing this on Ubuntu 18.04 - same stack trace.
1767961,2018-05-12 17:58:59 UTC,"Do you have steps to reliably reproduce this? I set up an 18.04 VM and haven't seen any crashes from selections, cropping, etc"
1767961,2019-01-09 06:05:23 UTC,"I also hit this, with a consistent repro:"
1767961,2018-05-09 12:44:49 UTC,"This is an 18.04 bug - starts up OK, but then the moment you try to do a couple of things like highlight and crop, then it simply exits."
1767961,2018-05-09 16:42:28 UTC,"thanks for reply,"
1767963,2018-05-09 09:07:50 UTC,"Perhaps right-clicks on an ""empty"" area of a widget should add the panel's ""add to panel"" entry to that menu? Since the menu includes ""lock to panel"" and the like, it's being provided _by_ the panel, not wholly by the widget itself."
1767963,2018-06-16 23:34:52 UTC,This upstream bug seems related: https://github.com/robint99/mate-dock-applet/issues/126
1767968,2019-04-14 14:22:24 UTC,"This problem has been around for a long time and a lot of people have struggled with it. You can find examples such as the following on quite a few help sites, for example"
1767968,2019-04-13 23:27:55 UTC,"I agree with you, its not the best solution. This bug impact many users! At next release of this softwares this bug has to be fixed."
1767968,2019-04-13 18:30:30 UTC,These nerd-level suggestions all work but the root cause (the real problem) is not solved and will pop up again. How is the non-nerd supposed to do this? ...would you want your neighbor editing your system files????  Someone needs to fix this permanently!
1767968,2019-04-13 17:34:37 UTC,I fix the problem with this approach:
1767968,2019-04-13 17:23:25 UTC,An update: The problem I reported in January went away on its own after a few weeks of having the problem every single day when I booted each morning. I was installing Ubuntu software updates when they became available during that time. There is something going on during boot that causes this problem.
1767968,2019-04-13 14:02:46 UTC,"I have the same problem, that John related."
1767968,2019-01-08 18:42:34 UTC,"When I boot up every day without exception, my machine starts up with one of the CPU cores running at 100%. I see lots of posts on other forums (Unbuntu  etc) going back over a year or more blaming touchpads or nvidia or WiFi. Some even say they can't use their thumb drive if it isn't plugged in when they boot. The problem also mimics a defective thumb drive where you plug it in and Ubuntu doesn't see it (because systemd-udevd doesn't have the cycles to process the newly plugged in USB device). Losing one core makes my machine slower but not too noticeably so. I do see much longer boot times and sometime it will hang entirely during boot. I assume a single core or dual core machine will be drastically slowed down or even unusable. When I search I find other non-ubuntu os's complaining about similar problems."
1767968,2018-12-22 17:54:47 UTC,"Command from Y S Gupta fixed to high cpu load for me.
As this is just a workaround. I suppose this bug should remain open.
Thanks for this, i can now reuse my bluetooth card."
1767968,2018-11-14 00:12:44 UTC,I am also affected for device 413c:8156 (Dell Wireless 370 Bluetooth Mini card) on Latitude E6400
1767968,2018-10-18 17:53:33 UTC,(In reply to Y S Gupta from comment #8)
1767968,2018-09-13 05:50:19 UTC,I also observed in my Dell laptop similar to Szymon that it relates to Touchpad.
1767968,2018-08-23 15:22:32 UTC,"I use ubuntu 18.04 with 4.15 kernel
I have hit the same problem, but with synaptics touchpad."
1767968,2019-01-08 19:38:50 UTC,"BTW, add to my previous comment an additional symptom:  sometimes my system will ""appear to hang"" entirely during boot (but it will power down normally by briefly touching the power off button when it ""looks like"" it is stuck)."
1767968,2018-06-14 00:32:13 UTC,"Scratch that last comment, on further testing found I was booted into incorrect kernel :/"
1767968,2018-06-13 16:50:40 UTC,As per https://patchwork.kernel.org/patch/10384111/ editing 97-hid2hci.rules as follows works around the new uevents added to the kernel in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
1767968,2018-06-03 13:14:41 UTC,I am also affected by this Bug please fix quick!
1767968,2018-05-20 07:57:41 UTC,"I observed the high cpu usage after upgrading from udev-233 to udev-236/udev-238 on Gentoo Linux. Downgrading back to udev-233 lets me use newer kernels (currently running 4.15.18) without any problems.
Using DELL Latitude E6400 from 2009, with same Broadcom Bluetooth module as mentioned above."
1767968,2018-05-09 23:02:06 UTC,"Bus 001 Device 009: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c:0000 Broadcom Corp."
1767968,2018-05-04 05:57:10 UTC,"I have the very same problem using the same distro (Ubuntu 18.04, 64-bit) on Dell Latitude E5400 laptop. Disabling BT from BIOS or removing the aforementioned rule solves the problem but leaves BT unusable."
1767968,2018-05-04 03:30:49 UTC,Have a look here: https://dev.solus-project.com/T5224
1767968,2018-05-01 15:00:06 UTC,My log file (if it helps):
1767968,2018-04-30 16:58:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767968,2018-04-30 16:42:16 UTC,"I have the exact same problem, also a Dell computer (Inspiron something). CPU load is almost always at 100% and temperature sensors measure over 100C! My computer has become unusable."
1767968,2018-03-06 21:09:45 UTC,"Created attachment 274593
dmesg"
1767968,2018-06-14 00:33:52 UTC,"Created attachment 276537
revert-bind_unbind-uevents.patch"
1767971,2021-01-07 19:55:31 UTC,Will this also be available in 20.10?
1767971,2021-01-08 11:25:09 UTC,It doesn't look like it. 20.10 is still on manpages 5.08.
1767971,2020-11-06 12:23:02 UTC,"This bug has been fixed with the upstream release (some days ago) of man-pages-5.09, which now provides a kernel_lockdown.7 page."
1767976,2019-09-16 08:38:38 UTC,Migrated to https://github.com/widelands/widelands/issues/3275
1767976,2018-05-27 21:05:18 UTC,"Genetic algorithm is too complex to give you an formula. This is like in medicine, you cannot calculate the effectiveness of a new drug, but must do (clinic) tests :("
1767976,2018-05-27 21:28:10 UTC,"That was a quick idea, about a simple change for a small improvement. As about code, I'll stick with economy for now. If sometime in the future flags start using reliable preciousness values to decide priority of serving wares, the AI may like to have a look..."
1767976,2018-07-02 12:43:45 UTC,"Hi,"
1767976,2018-07-02 13:28:42 UTC,"hessenfarmer,"
1767976,2018-07-02 13:52:20 UTC,"Unlike the currently intuitive/arbitrary value of preciousness, stocklevel is an objective number. Could you point me to the part of the code where stocklevel is considered in deciding what to build next?"
1767976,2018-07-02 15:12:15 UTC,"Hi, look into this funtion:
https://bazaar.launchpad.net/~widelands-dev/widelands/trunk/view/head:/src/ai/defaultai.cc#L4841
it returns one of these states: kForced, kNeeded, kNotNeeded, kNotBuildable, kAllowed, kNeededPending, kForbidden - should be selfexplanatory :)"
1767976,2018-07-02 15:58:43 UTC,"@ Tibor:
I don't have such numbers yet. But this is one of my ""things on the list"""
1767976,2018-07-04 05:55:13 UTC,"Well, the code is quite structured, so if you want to focus to some partial aspect of AI (placing of new buildings, attacking, road making, seafaring) you can look up relevant functions.
If you look at defaultai.cc in build 19 https://bazaar.launchpad.net/~widelands-dev/widelands/b19/view/head:/src/ai/defaultai.cc - there are a lot of arbitrary numbers that all had to be tested, that means recompilation and running multiple games - it was pain and took a lot of time and therefore I decided to save the time spent on endless circles of edit/compile/test work and introduce the genetic algorithm as procedure for automatic self-tuning of constants."
1767976,2018-07-04 08:13:58 UTC,"Hi
I have to admit that on a quick glance it looks not very comprehensible but after some thoughts I believe I understand what is going on in the code. While digging what preciousness is doing I probably found a bug giving preciousness a direct effect on the building necessity.
In
https://bazaar.launchpad.net/~widelands-dev/widelands/trunk/view/head:/src/ai/defaultai.cc#L5150"
1767976,2018-07-04 08:41:12 UTC,EXACTLY!!!! good catch!
1767976,2018-07-04 10:13:22 UTC,"I read the inputs[1] myself and I supposed that it is some kind of mathematical interpolation around the basis of the array (I forgot that arrays in C++ are 0-based), so I didn't bother looking at its value. My main issue is that such kind of bugs should be caught very early by printing some output and comparing it with the desired one. But current lack of structure makes that impossible, as it turns the code into a big ""black box"", meaning that such bugs can survive for many months, negating some improvement efforts during that time. Most tests should not need to run the game at all, they should instead be running specific functions against predefined inputs and comparing them with predefined outputs. That saves tones of time/pain and prevents most bugs from hiding for long times. It's a pity to spend so many hours coding and testing, just to have a few typing mistakes destroy the final result."
1767976,2018-07-04 11:23:22 UTC,"I dont defend coding style, could had been done better of course."
1767976,2018-05-27 19:36:36 UTC,I think you can suggest new preciousness without even be aware of how are they used under the hood...
1767976,2018-07-03 17:57:49 UTC,"I went through the code. Turns out that preciousness is just one instance in a code full of arbitrary values, most of which are not documented. Moreover, they are combined into countless lines of structureless code, which is almost unreadable in the large scale. And from what I can tell, if I was to make some change to it, it would be close to impossible to test its results. The overall effort would be a waste of time."
1767976,2018-05-27 15:31:28 UTC,"Maybe put a ""genetic algorithm"" tag to some bugs, so as I don't suggest alternatives for them. And maybe we could provide multiple versions of AI, one with pure genetics, one with no genetics at all, and one with a mix."
1767976,2018-05-27 20:45:09 UTC,"> I think you can suggest new preciousness without
> even be aware of how are they used under the hood...
"
1767976,2018-05-27 13:10:18 UTC,"I thought that we were in the realm of hacks here. Current hack isn't less wrong an approach than mine. The question is: Until we get enough CPU time for training, do we want a better AI or not?"
1767976,2018-04-30 23:06:59 UTC,As already stated I think 25 is far to less of a value. For the beginning I think 100 would be fine.
1767976,2018-05-01 06:48:48 UTC,"What happened in the mentioned bug is that a number was not copied over during an engine change, and therefore missing. This is now verified during tribe loading and will not happen again."
1767976,2018-05-01 20:09:34 UTC,Highest used preciousness is 14 now. And I think we should not go over 20 or 25. The minimum we can do is mention this range in documentation.
1767976,2018-05-26 14:04:52 UTC,"Such values should be the result of calculations. If given some data, I could try producing some formulas."
1767976,2018-05-26 19:10:22 UTC,"The problem is that genetic algorithm is involved here so it is difficult to come up with ""data"""
1767976,2018-05-26 19:51:43 UTC,"Data don't have to translate into specific things in the game. I can use the same numbers that you used to come with 14 or 25. Actually, anything you can provide me as input I can probably express it with numbers, in order to produce a non-arbitrary value."
1767976,2018-05-26 20:05:03 UTC,"It is only observation - when preciousness was 255 by mistake, it used to build many buildings of that type that were not utilized and never promoted (lack of experiences for the worker). So I dont have hard numbers.."
1767976,2018-05-27 14:57:34 UTC,"Well, here we discuss the values of preciousness in init files.
If you suggest scrapping them, this should belong under different topic."
1767976,2018-05-26 20:46:44 UTC,"No, I did not do any thorough testing."
1767976,2018-05-26 21:33:34 UTC,"Then let me try the inverse route: Could you give me some output data, from the things preciousness affects?"
1767976,2018-05-27 09:01:57 UTC,"Well, the output can be number of metalworks depending on preciousness. I saw a game with 8 metalworks and building new one. Of course most of them idle (<10%)."
1767976,2018-05-27 10:30:40 UTC,No need for statistics at this point. If I prepare a formula of this form:
1767976,2018-05-27 11:48:28 UTC,This is wrong approach. Genetic algorithm should consider count of buildings and their current utilization. And it tries to do it.
1767976,2018-05-26 20:31:37 UTC,"So you tried various numbers up to 255 until observing that 14 works best? Shouldn't such kind of observations and number-finding be done by training alone? Cause if the AI has to base its behavior on arbitrary numbers provided by human intuition, then it will never become competitive (unless maybe by mistake, which is highly doubtful)."
1767981,2018-04-30 16:10:21 UTC,"I'm sorry it is not clear to me but when did you see the error message? Was it during the release upgrade process, after you ran ""do-release-upgrade"" or was it when you did some apt operations after the upgrade completed successfully?"
1767981,2018-04-30 16:36:22 UTC,Hi Brian
1767981,2018-05-01 19:51:57 UTC,"I don't believe this has anything to do with the release upgrader, it just happened to be the process which caused you to notice that the permissions were incorrect."
1767982,2018-06-06 17:48:31 UTC,Does this actually have anything to do with util-linux?  What makes dpkg give this error message?
1767988,2018-04-30 14:35:26 UTC,"My launchpadlib version is 1.10.6, installed with pip."
1767992,2019-08-13 11:27:47 UTC,This bug was fixed in the package linux - 4.15.0-58.64
1767992,2019-08-09 17:21:21 UTC,"Hi Damir (or anyone else affected by this that may be reading the bug),"
1767992,2019-08-07 08:34:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1767992,2019-07-25 18:32:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1767992,2019-07-15 23:00:31 UTC,"Thank you for testing that and providing a test case, Damir!"
1767992,2019-07-15 16:27:10 UTC,Kernel from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767992/comments/8 solved my issues.
1767992,2019-06-27 05:58:59 UTC,"Please test the kernel:
https://people.canonical.com/~khfeng/lp1767992/"
1767992,2019-07-10 18:56:40 UTC,"Hi everyone,"
1767992,2019-02-08 19:41:11 UTC,"We had the same issue after updating from Ubuntu 14.04 to 16.04 and then 18.04 (the two consecutive updates were applied on the same day).
The filesystem is also XFS. and the setup is with raid10.
The bug does not completely froze the system. Many process still run and were able to write to disk. But new processes seems to have trouble with that.
Also, some processes that did not write to disk also halted. Example: htop and ps aux
Interesting thing is that ""ps aux"" actually started printing the output and around the middle of the execution, it halted, and Ctrl+C was unable to exit the program.
htop, which hangs a few seconds after its execution, showed that the frozen processed were in D (uninterruptible sleep) state."
1767992,2018-10-26 17:19:19 UTC,I can confirm this affected me as well. My RAID-10 is on a separate filesystem from the Operating System's SSD -- I have the RAID-10 mounted at '/raid10' on my server. My application is installed on the non-mdadm SSD at '/opt' but it reads/writes/executes files from the '/raid10' filesystem (made up of 6x8TB drives with 1 spare).
1767992,2018-07-20 13:17:39 UTC,"This issue is gone after we migrated from XFS to EXT4, so it is definitely XFS-related."
1767992,2018-07-20 12:21:47 UTC,Same problem here reproducible on Ubuntu 18.04 LTS. SATA RAID 10 with XFS filesystem. On each reboot the RAID does a resync. Any operation on the RAID before the resync is finished causes the process to hang. Might be also associated with another issue that causes the resync every time on boot.
1767992,2018-06-14 06:59:18 UTC,"Same here, md raid10 (not sure if its important but xfs, hung 3 times in last 2 days).
It seems that a combination of md raid10 check + I/O (maybe XFS-specific, I dunno, but both original poster and us seem to use XFS) frequently hangs on kernels that are newer than Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 (yes, I know it's a wide range, but everything started happening after we rebooted this machine, which upgraded us from Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 to Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16, the check was scheduled some time later, so we didn't catch it immediately)."
1767992,2019-04-02 16:59:15 UTC,Fixed in https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.21
1767992,2018-06-14 07:00:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767993,2018-05-04 01:56:16 UTC,Please be more polite. I committed more time to researching this bug report yesterday than any other. What the motherboard is capable of is at least relevant and you should be aware of it.
1767993,2019-02-28 08:48:12 UTC,"Still broken despite upgrading
 kernel to 4.15.0-46.49
 grub to 2.02-2ubuntu8.12
 mesa to 18.2.8-0ubuntu0~18.04.2"
1767993,2018-07-20 10:43:36 UTC,error file
1767993,2018-07-20 10:41:43 UTC,"Hello,"
1767993,2018-07-04 04:17:25 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1767993,2018-05-04 10:26:49 UTC,by breaking I mean which kernel makes it hang now without 'nomodeset'
1767993,2018-05-04 10:25:33 UTC,"or test older kernels to see where it broke, and file a bug upstream against drm/i915"
1767993,2018-05-03 02:04:19 UTC,Resolution limits are almost always imposed by the motherboard/system manufacturer. Not the software or CPU/GPU manufacturer. In the case of your system there are some interesting notes:
1767993,2018-05-02 10:20:35 UTC,I've found the problem (or at least got some closer):
1767993,2018-05-02 08:23:49 UTC,This is definitely not correct.
1767993,2018-05-01 02:01:42 UTC,"Oh, I see. X starting in low resolution mode is due to your kernel option 'nomodeset'. So don't use that. It's behaving correctly in falling back to 1024x768."
1767993,2018-05-01 01:57:18 UTC,This appears to be a kernel problem. X is reporting the KMS graphics device is missing:
1767993,2018-04-30 11:11:31 UTC,"00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21) (prog-if 00 [VGA controller])
        Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at 90000000 (64-bit, non-prefetchable) [size=16M]
        Region 2: Memory at 80000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at f000 [size=64]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
                Address: 00000000  Data: 0000
        Capabilities: [b0] Vendor Specific Information: Len=07 <?>
        Kernel modules: i915"
1767993,2018-05-03 10:19:01 UTC,Are you just here to keep me busy with useless conversation?
1767995,2020-04-27 15:22:09 UTC,It was fixed for me. I re-installed Ubuntu afresh though. Keeping my $HOME.
1767995,2020-04-27 15:03:05 UTC,Still affected in 20.04. Using Synaptics driver.
1767995,2019-10-20 23:33:41 UTC,Still in 19.10
1767995,2019-01-08 21:48:29 UTC,Thanks for reporting the issue upstream!
1767995,2019-01-08 17:48:06 UTC,I've reported this to the GNOME Gitlab - https://gitlab.gnome.org/GNOME/gnome-control-center/issues/340.
1767995,2018-12-12 13:18:27 UTC,The issue should be reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues
1767995,2018-11-09 19:28:08 UTC,"This horizontal scrolling behavior is very confusing.
It would be very nice to have this fixed."
1767995,2018-10-21 21:18:59 UTC,"Nevermind -- turns out the workaround utilizing xinput set-prop still works, the device ID had changed. Nevertheless, this is a frustrating issue and seemingly simple request that this should just work as it always did. Where are the unit tests to prevent these constant regressions? I understand and appreciate the nature of open source software but it does seem basic quality control has slipped. Every update it seems I have to run around and fix something new that worked fine before."
1767995,2018-10-21 21:02:42 UTC,This affects me too -- and the fix that I was using stopped working with a recent update. Now none of the solutions listed work. https://askubuntu.com/questions/1029128/inverted-horizontal-scrolling-ubuntu-18-04
1767995,2018-08-18 14:07:03 UTC,This affects me too. I noticed it as soon as I upgraded from 16.04 to 18.04.1.
1767995,2018-05-01 14:21:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1767995,2018-04-30 12:35:25 UTC,I just did some tests and figured that this does not affect the Wayland session.
1767997,2018-05-02 07:55:01 UTC,"Opened for a discussion upstream at: https://www.redhat.com/archives/libvir-list/2018-May/msg00043.html
I didn't have your email to CC you, but you can track via the WEB UI of the ML."
1767997,2018-04-30 16:50:38 UTC,"> So I wonder is this ""just"" a conflict between how libvirt expects pools to be set up (and as it does by itself) vs the manual set up one?
"
1767997,2018-04-30 16:28:07 UTC,"I was collecting a summary to report upstream, but then I wondered are there other scenarios where this should not be stripped to the base?
Or is there another common use case were the pool is created differently so it works?"
1767997,2018-04-30 14:10:50 UTC,"Ok, without apparmor fixes (unlikely soon for reasons outlined in other bug) or you weakening the isolation a bit on your system it won't work then."
1767997,2018-04-30 14:07:21 UTC,"> if that worked for you before or not
"
1767997,2018-05-14 08:57:45 UTC,Thanks for chiming in on the upstream discussion btw!
1767997,2018-04-30 14:05:38 UTC,I checked libvirt HEAD and the code's the same there: src/storage/storage_backend_zfs.c
1767997,2018-04-30 13:56:53 UTC,Flagging as libvirt issue as we ruled out virt-manager
1767997,2018-04-30 13:41:25 UTC,"Repro without disks or other HW dependency:
 $ apt install zfsutils-linux
 $ fallocate -l 100M /tmp/zfs
 $ sudo zpool create zfs /tmp/zfs
 $ sudo zfs create -V 10M zfs/vol1
You can use that as a disk just fine:
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw'/>
      <source dev='/dev/zvol/zfsmirrortest/vol1'/>
      <target dev='vdc' bus='virtio'/>
    </disk>"
1767997,2018-04-30 13:53:41 UTC,"Haven't read all your updates in between while I was writing :-)
Need to re-read all you posted - thanks for your work on this."
1767997,2018-04-30 13:24:14 UTC,"I looked in both 4.0.0 and HEAD source, and the call to zpool uses def->source.name.  I think it would work fine if it stripped out everything from the first slash."
1767997,2018-04-30 13:07:20 UTC,"And using strace on libvirtd, I see it's running this:"
1767997,2018-04-30 12:59:56 UTC,"Aha, good thinking about reproducing with virsh.  To find out what virt-manager is doing, I did:"
1767997,2018-04-30 12:32:20 UTC,"Hi (again) Brian,
this is rather unexpected let me try to follow what happened.
So far you only triggered this via virt-manager start/refresh so I'll follow that until we know a non virt-manager trigger - usually it only calls libvirt tasks so I'd assume we can identify a virsh <something> or so to trigger the same."
1767997,2018-04-30 13:56:21 UTC,"Read - I see we both got to the bad zpool call for now.
I'm in a hurry and need to drop for now (sorry), but will look at the source and maybe if there are later fixes post 4.0 - if not I'll go deeper and try to create a test version."
1768001,2018-05-01 02:12:54 UTC,The problem seems to be missing firmware for your bluetooth chip. The kernel is trying to load it and can't find it. Because package 'linux-firmware' is missing those files.
1768001,2018-05-01 12:07:58 UTC,"I'm afraid that the firmware files just look to be pulled out of Windows drivers downloaded from arbitrary download sites. I'd be hesitant to stick those into our linux-firmware package in any case, and without a license which allows us to redistribute the files we simply cannot distribute them in Ubuntu."
1768001,2018-05-01 02:05:20 UTC,Looks like the problem may be:
1768007,2018-04-30 14:11:05 UTC,"Hello - are you using the GPG support in eCryptfs? It looks like you have a bad version of the GPG module built and installed at /usr/lib/arm-linux-gnueabihf/ecryptfs/libecryptfs_key_mod_gpg.so. Do you know how that file got there? If you manually built and installed it, you may want to make a backup of the file (perhaps to your home directory), remove it from the location in /usr/lib/arm-linux-gnueabihf/ecryptfs/, and try again."
1768007,2018-05-02 08:05:51 UTC,I haven't intentionally installed gpg support.
1768010,2020-01-03 15:56:37 UTC,"Steve Bian (freespace) wrote on 2018-05-03:

>This issue is caused by MountFlags=slave in the systemd-udevd.service file. Historically 16.04 removed this flag to allow laptop-mode-tools to work:
>
>https://askubuntu.com/questions/1019865/why-does-ubuntu-16-04-remove-mountflags-slave-from-systemd-udevd-service
>
>In 18.04 this flag is preserved and as such when usbmount mounts filesystems they are mounted into systemd's private namespace and not visible to the user.
>
>A workaround is to override the MountFlag as described in:
>
>https://unix.stackexchange.com/a/441588/191141
"
1768010,2018-10-24 02:54:23 UTC,Dan: It looks like it's working as expected. The first error can be ignored because it always does that. It first tries to mount /dev/sdb which always fails because it is not a partition. Next it tries to mount /dev/sdb1 which succeeds because it is a partition.
1768010,2020-01-03 15:53:24 UTC,"Nikolaj Løbner Sheller (nikolaj-l) wrote on 2019-12-13:

>In
>  /lib/systemd/system/systemd-udevd.service
>setting
>  [Service]
>  PrivateMounts=no
>solves the problem for me.
"
1768010,2019-12-13 18:11:28 UTC,"In
  /lib/systemd/system/systemd-udevd.service
setting
  [Service]
  PrivateMounts=no
solves the problem for me."
1768010,2019-10-29 13:06:14 UTC,Thanks a zillion everyone! After the software update today my USB dongle is getting recognised as before. Many thanks. :)
1768010,2020-01-03 16:20:24 UTC,Bootch (di-man) wrote 22 minutes ago: 	#17
1768010,2018-10-24 11:02:40 UTC,Checking github - there are a number of repos there... Is it the leetking/usbmount that you are referring to in #8?
1768010,2018-10-24 10:56:09 UTC,"Thanks Colin - that's good to hear! usbmount has been part of the distro of my product for some time now and losing it was driving me nuts!
I will work with our programmer to get the latest from github."
1768010,2018-10-24 01:59:37 UTC,I've made the necessary changes described in #2 above but when I plug in a usb drive I get the following error
1768010,2018-10-24 11:58:22 UTC,"Dan: No, I was referring to this as per post #4. https://github.com/rbrito/usbmount"
1768010,2018-10-04 23:22:00 UTC,"Sorry for #6 above.. I shouldn't have been testing with a vfat volume, my bad."
1768010,2018-05-03 16:05:28 UTC,This issue is caused by MountFlags=slave in the systemd-udevd.service file. Historically 16.04 removed this flag to allow laptop-mode-tools to work:
1768010,2018-06-27 15:04:47 UTC,"@freespace - Thank-you, I can confirm that your workaround solves the problem for me on Bionic. (Really - that's ENORMOUSLY helpful and makes my work with cotswoldjam.org Raspberry Pi club a million times easier. Thanks again.)"
1768010,2018-07-06 09:18:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768010,2018-10-22 01:49:47 UTC,I can confirm that the current code on github fixes the udev issue for 18.04. The re-write also fixes an associated problem with mounting NTFS drives through usbmount.
1768010,2018-08-15 17:12:13 UTC,"Thanks again for this, it helped me too.
I have a further problem though: when my usb stick is auto-mounted by usbmount it has write permissions only for root, doing sudo chmod a+w /media/usb0 prints no errors but has no effect. How can I grant user write permissions to this mount-point.
Thanks a lot.
Steve."
1768010,2018-10-04 23:15:21 UTC,"I built the new package mentioned in #4 above.  While it does auto mount the USB devices, there does seem to be a permission issue as mentioned above."
1768010,2018-08-01 10:43:43 UTC,"This is already fixed upstream, but sadly no new package was commited: https://github.com/rbrito/usbmount/commit/2d2cdcc58b65bbadf1dbe532e9938967060cee09"
1768018,2018-04-30 13:16:53 UTC,Patch submitted to https://github.com/juju/charm-helpers/pull/166
1768018,2020-07-06 09:22:46 UTC,"This fix didn't appear to work (at least in some cases), new fix:
https://github.com/juju/charm-helpers/pull/484"
1768022,2018-06-05 16:44:47 UTC,"So, uh, interesting finding here. I pulled out each join one at a time and nothing would budge the planning time until I took out ausp and it dropped to > 100ms. Not wanting to remove it entirely I looked at the ON clause and on a whim swapped ahr.usr = ausp.usr for au.id = ausp.usr and that's all it takes. Is this whole thing built by the fielder or is this something else that could be gently nudged to make all of our web client users extremely happy?"
1768022,2018-06-05 17:12:07 UTC,"Jason, see the ""ahopl"" class in the IDL.  The SQL you want to tweak is in there."
1768022,2018-06-05 17:54:02 UTC,"Thanks for the pointer Bill, that's definitely a best case for this fix. I had that bug in the back of my mind for a little bit but since I didn't see anything with that kind of wildly inaccurate row estimates I didn't think to look at it that closely. (Ah, but Pg 9.3 didn't break out plan/exec time, at least not in Chris's paste...)"
1768022,2018-06-05 18:03:43 UTC,"Since I'm in a mood to get this fixed on my end I went ahead and threw together a branch others can test. Hopefully this will fix it for the installations where it's an issue (EI, PINES) without causing any speed issues anywhere else."
1768022,2018-06-05 19:00:15 UTC,"Jason,"
1768022,2018-06-05 19:52:06 UTC,"I did some test runs with the original and new query on a large test database.  Neither performed well, but the one with Jason's patch was about 10 seconds faster.  My best time was 57 seconds.  I can post the analyze if that would be helpful."
1768022,2018-06-06 11:54:03 UTC,"That still seems awfully long Bill, though I don't know how many holds it was looking at. I would be curious to see that analyze output if you wouldn't mind posting it somewhere. I don't suspect there's much more tweaking to be done for now though."
1768022,2018-06-06 15:25:54 UTC,https://pastebin.com/nMAwFqc1 is the explanation for the above edit. Note I've been using the same hold id (it hasn't made a difference to the planning time).
1768022,2018-06-06 15:00:29 UTC,"Jason, could you post the explain (or explain analyze) of the fast version?  Mine is here: https://pastebin.com/wHBNezUf ... the explain portion (and planning time) are what I'm interested in ATM."
1768022,2018-06-06 15:19:25 UTC,"Arg, sorry, I'm looking at query to build the initial holds pull list.  Same ""ahopl"" SQL, different WHERE clause."
1768022,2018-05-31 15:35:42 UTC,Branch for the max_bundle_count stop-gap:
1768022,2018-07-24 17:36:59 UTC,"To recap the pullrequest, we have two independent branches that should help with this issue:"
1768022,2019-02-25 21:59:47 UTC,"Hello, I just tried out the ""max_bundle_count=> 5"" change on a test 3.2.3 system, and now the pull list loads for me without any trouble."
1768022,2020-08-05 21:02:20 UTC,"We're no longer having this problem at PINES (running 3.4.2) and after a cursory look, it doesn't look like we applied either of the proposed patches here. Are other libraries still having this issue, or did the problem get fixed with another patch?"
1768022,2021-02-20 01:44:25 UTC,I am not seeing this issue any longer on 3.4 or later.  I was able to pull a hold list today with more than 200 items successfully.
1768022,2018-06-06 14:38:41 UTC,"To compare apples to apples, I reviewed the PG settings and made some changes.  The biggest impact came from changing join_collapse_limit from 8 to 14.  Now the query runs about 25 seconds.  Not great, but at least it doesn't time out any more."
1768022,2018-05-30 12:48:16 UTC,"That this is apparently limited to us is a good sign, I guess. The frustrating thing is that there doesn't appear to be anything I can do to knock that timing down. I've adjusted work_mem, join_collapse_limit, geqo_threshold, random_page_count, effective_cache_size, effective_io_concurrency, and temp_buffers to varying sizes from comically small to excessively large and it just won't budge. I haven't checked shared_buffers since the machine is in use and that one requires a restart, but I'll try that next."
1768022,2018-05-25 14:16:51 UTC,"Bill, I did apply the max_bundle_count to the wrong method initially (the .prepare method; not the plain search) but even applied to the correct method nothing appears for a while, then the 40 that I'm looking at come in rapidly in 3-4 chunks. (Possibly a web view redrawing artifact, hard to say.) It's still quite the delay from start to finish because of the 56+ seconds of query planning but it does appear that the lowered bundle count is keeping things alive long enough to eventually finish."
1768022,2018-05-25 16:11:06 UTC,"Thanks, Jason.  That's progress, anyway."
1768022,2018-04-30 13:12:42 UTC,This was originally noted early in the year but Jason Boyer indicated the community was aware of the slow query/time out issues and no bug was filed at that time. Sorry if this is a duplicate but initial queries of existing bugs did not find a match.
1768022,2018-05-23 15:23:10 UTC,There was another ticket: https://bugs.launchpad.net/evergreen/+bug/1738488 that should have helped with this issue but we are running currently with that patch and still timing out on holds pull list generation when the site has 50+ holds.
1768022,2018-05-23 15:36:19 UTC,Here's a potential fix:
1768022,2018-05-23 15:53:06 UTC,"I think we may want to spell that ""max_bundle_size"" rather than ""max_chunk_size"" in modern OpenSRF, but otherwise the theory seems sound.  Thanks, Bill!"
1768022,2018-05-24 13:10:40 UTC,It looks like max_chunk_size is what's en vogue at the moment. That said it hasn't had the desired effect on its own; still not displaying any entries. I'm trying to follow the path from call to db to see what could be the holdup but the more the merrier if there are any other ideas.
1768022,2018-05-24 13:36:52 UTC,"The name ""max_chunk_size"" is incorrect because this is not about chunking, it's about bundling.  The fact that ""max_chunk_size"" is used more times doesn't mean it's the right thing to use here."
1768022,2018-05-29 20:17:03 UTC,"Bill, I'm not against that.  A stop gap seems useful."
1768022,2018-05-24 13:47:29 UTC,"And, just because my morning wouldn't be complete without a small side of crow, the thing we /actually/ want is:"
1768022,2018-05-24 16:48:16 UTC,"Thanks, Mike.  max_bundle_count => 1 is really what I was going for."
1768022,2018-05-24 17:24:04 UTC,"So this is interesting. I've got those 2 entries for max_bundle_count and it's just not streaming anything. If I set the grid to show 10 or 25 they will eventually appear but all at once, and if I choose 50 or 100 nothing appears after the timeout. (All of opensrf and apache were restarted after making these changes so it shouldn't be old code or anything like that.)"
1768022,2018-05-24 17:59:05 UTC,"Huh, Jason, I'm seeing just the opposite.  When I add max_bundle_count=>1 to Fielder.pm, I start seeing the pull list render as a stream, where before it rendered only after filling up the page."
1768022,2018-05-24 18:05:40 UTC,"Jason, that planning time is ... crazy.  I'm seeing sub-milisecond planning times on data sets that are comparable to yours in size (within an order of magnitude).  There are lots of things that could be contributing, but to check the obvious ones, what do these give you:"
1768022,2018-05-25 11:49:40 UTC,I definitely agree that these plans are bananas. Here are the details:
1768022,2021-02-23 15:28:00 UTC,"Thanks Jennifer, we're no longer having issues either. I'll mark this one Won't Fix."
1768022,2018-05-24 15:51:23 UTC,"Ok. My confusion came from the fact that across every perl module there are only 5 references to max_bundle_size and they're all only in $client->can() calls so I made an assumption. Had I just searched for max_bundle_ I'd have noticed that sooner. :) In any case, it didn't have any visible effect either. Looking at the JS, it looks like fielder is involved so I'm not sure that method is involved or when it's called. I do see 20 calls to a fielder drone (there are more than 20 holds)."
1768023,2019-01-31 16:07:29 UTC,I had an issue with Kubuntu 18.04. It appears to be working again on a Kubuntu 18.04.1 VM I just installed
1768023,2018-09-03 09:55:00 UTC,It was installed from the Ubuntu when the error happened. Using it from getcomposer worked fine.
1768023,2018-09-02 18:04:54 UTC,"How did you install composer, was it via the Ubuntu package (`apt install composer`) or via getcomposer.org?"
1768023,2018-05-02 21:44:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768026,2020-03-14 20:40:33 UTC,1 for adding the fix to 18.04 LTS. When will it be fixed?
1768026,2018-04-30 17:09:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768026,2018-08-22 18:21:23 UTC,"It would be nice if someone could update the Vim package and fix this issue. Patch 1476 fixes this bug, and it was broken in patch 1449, which is just a little bit before the patch the Bionic package uses."
1768026,2018-09-27 12:41:08 UTC,It seems like this wants a re-sync from Debian.
1768026,2018-10-04 10:11:37 UTC,I've been getting bug reports for 5 months because a broken Vim patch was pulled into Debian. It would be nice if someone could update the package.
1768026,2018-10-19 19:15:19 UTC,"Please update the package! It breaks vim for ale users, which surely make up a significant percentage of serious users."
1768026,2018-10-29 11:34:11 UTC,Could you backport the fix to the 18.04 LTS? This is super annoying for vim users.
1768026,2019-01-10 21:03:26 UTC,+1 for adding the fix to 18.04 LTS
1768026,2019-01-12 09:22:00 UTC,Will there be a backport? This is really annoying...
1768026,2020-04-29 22:17:03 UTC,We need it.
1768031,2018-08-18 20:57:58 UTC,"Sound settings reset every time, no matter what I try. Even though everything works as a charm, it resets. Acer Swift 1, Ubuntu Mate 18.04"
1768033,2018-04-30 17:22:42 UTC,"Many broken packages (scroll down):
https://launchpadlibrarian.net/367996812/VarLogDistupgradeAptlog.txt"
1768033,2018-05-01 02:45:20 UTC," thank you. little comments:
why not do fresh installing:
Changing of system is more hobby than real necessity:  time is edged. This system was ""new"", was restored one day ago practically without  additions of packages. how its ll might be broken ?!  (Fresh install was very long  process  with not effective  ""war"" with efi and restoring many times grub). sorry  this comment is not professional and away of points."
1768038,2018-11-18 16:53:02 UTC,Here they are:
1768038,2018-11-19 09:55:50 UTC,Did you remove the following entry?
1768038,2018-11-19 15:54:06 UTC,No!  xubuntu/xfce4 deleted it all by itself when I logged off and then back on again (I did it twice to make sure).
1768038,2018-11-19 16:00:18 UTC,You have to edit this file while not being logged into the Xfce session.
1768038,2018-11-19 16:51:32 UTC,Thanks very much.  That worked.  Sorry I was so dim editing it in place.
1768038,2018-11-19 17:11:17 UTC,"So, it would be best to add this entry to the Xubuntu default settings (comment #10) until the actual issue is resolved (comment #7, second part)."
1768038,2018-11-15 17:48:17 UTC,"No, the old workaround doesn't work.  I've failed to find any solution."
1768038,2018-12-15 13:52:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768038,2019-01-29 03:37:22 UTC,Resolved with the below commit.
1768038,2019-01-29 05:18:06 UTC,This bug was fixed in the package xubuntu-default-settings - 19.04
1768038,2019-02-22 12:54:50 UTC,This worked like a charm for me:
1768038,2018-11-18 10:27:41 UTC,"My guess would be that xfce4-power-manager still tries to hibernate the system, but that operation is not permitted. What do the following two commands return?"
1768038,2018-11-19 17:17:08 UTC,Try running this command>>>
1768038,2018-11-16 21:15:12 UTC,And this is the full power-manager output
1768038,2018-11-15 12:40:50 UTC,"Tim, does the workaround from your comment still work?"
1768038,2018-11-16 18:05:00 UTC,"Some configuration related output is printed in the beginning, so please attach the whole terminal output."
1768038,2015-11-17 16:23:46 UTC,"Hi. With Xubuntu 15.10 (was same w/ 15.04) when suspend is initiated through inactivity, it fails with the quoted text: ""GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied""."
1768038,2016-08-16 02:06:43 UTC,This is still an issue in v.1.6.0
1768038,2016-11-21 03:01:13 UTC,I had this exact error in Xubuntu 16.04 and fixed it with this solution:
1768038,2018-11-16 21:14:26 UTC,This is the journalctl as requested
1768038,2017-08-26 22:33:30 UTC,"The error message ""GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied"" is unrelated to inactivity sleep not working. It is caused by a separate bug."
1768038,2018-05-04 19:40:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768038,2017-02-22 21:47:36 UTC,"The fix in the link (http://askubuntu.com/a/851760/83302) worked for me as well on Xubuntu 16.04. Incidentally, someone on the Ubuntu-devel-discuss mailing list reported what I think is the same bug and workaround and suggested a more permanent fix: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2016-July/016779.html."
1768038,2018-10-21 14:03:28 UTC,"For laptop users, the ability to suspend after an idle period is, I would have thought, quite important."
1768038,2018-11-16 09:45:16 UTC,Running the power manager in debug mode could give us a hint:
1768038,2018-11-16 14:13:26 UTC,"I did this.  I got the same error notification.  This is the last bit of the debug output (I then killed it).  It means nothing to me, but maybe it does to someone else."
1768038,2018-10-21 14:01:43 UTC,"This bug is still present in Cosmic xubuntu, installed on 20th October."
1768048,2018-05-04 23:28:16 UTC,"Yeah, A number of things to do with theming of panes are misbehaving in the new 18.04 release. I think (yet again) changes by the gnome devs are changing how things work, leaving everyone to figure out what, how, why, oh why, oh why?"
1768049,2018-05-07 14:41:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566603"
1768049,2018-05-18 09:06:14 UTC,"Reviewed:  https://review.openstack.org/566603
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=037abd3210907aa5242778dda4ac6b173981e640
Submitter: Zuul
Branch:    master"
1768050,2018-10-16 14:30:38 UTC,"Hi,
I also have this issue. But have not been able to solve it..
Is a newbie, so please forgive me if I do not provide all info first hand :)
Also I do not know where else to ask for help..."
1768050,2019-02-02 18:55:22 UTC,"Hi,
How do i find the right locale $x for DK ?"
1768050,2019-02-02 12:12:31 UTC,"Alexandre Lima's suggestion works, but it needs to be adjusted in case of not an English locale."
1768050,2019-04-02 10:51:59 UTC,"Hi,
I can not get this to work..
The Bug must still be there."
1768050,2018-06-14 11:06:51 UTC,I had the same problem and I solved with this solution:
1768050,2018-05-03 18:53:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768050,2018-05-04 14:37:51 UTC,"root@eerlon:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libnvidia-gl-390 libnvidia-gl-390:i386
The following NEW packages will be installed:
  libnvidia-gl-390 libnvidia-gl-390:i386
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 0 B/29.1 MB of archives.
After this operation, 147 MB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 153905 files and directories currently installed.)
Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_i386.deb ...
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340
dpkg-divert: error: mismatch on package
  when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390'
  found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340'
dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb (--unpack):
 new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2
Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_amd64.deb ...
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
dpkg-divert: error: mismatch on package
  when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by libnvidia-gl-390'
  found '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'
dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb (--unpack):
 new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb
 /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@eerlon:~#"
1768051,2020-02-17 11:53:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768054,2020-07-01 20:36:24 UTC,"Thank you for your bug report, it does sound similar to https://gitlab.gnome.org/GNOME/evince/-/issues/1031"
1768057,2019-07-07 04:17:29 UTC,[Expired for mate-desktop (Ubuntu) because there has been no activity for 60 days.]
1768061,2018-05-20 15:07:03 UTC,Confirmed in 3.1
1768061,2018-05-20 15:15:07 UTC,I get the following error message in the console during this error:
1768062,2018-04-30 16:41:36 UTC,"The attachment ""Minimal patch to update a2ping.pl 2.77p to 2.77p1"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1768064,2018-07-09 23:31:30 UTC,"I am moving this bug under ""juju"" project for triaging. ""juju-core"" is dedicated to Juju 1.x series exclusively."
1768064,2018-07-10 12:14:31 UTC,I had a closer look at your description and it is by design that Juju first terminates cloud instance and then will eventually mark the machine as terminated in Juju.
1768065,2019-10-15 13:45:04 UTC,I'm marking this as won't fix. Ideally the error message would not be printed at all but this would involve tricky changes to the dynamic linker that I don't think are warranted. I've explained why this behavior exists in the prior comment. I don't think we can do anything else about it.
1768065,2018-05-11 11:50:36 UTC,Hello
1768072,2018-05-14 18:48:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768074,2018-04-30 18:50:46 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1768074,2018-05-05 12:26:22 UTC,"I have now reported the bug i Bugzilla. This is my first report there, so feel free to correct any mistakes I may have made."
1768074,2018-08-08 03:10:03 UTC,"I found intresting behaviour. When mouse over on folder and stay moving on one folder - names will displayed. After mouse stops hover event leave folder and folder names are dissapeared.
Also when click right mouse button hover event freeze and folder name showing. But click only when folder highlighted."
1768074,2020-03-17 13:31:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768074,2020-07-16 14:18:18 UTC,The report is now also in gitlab on https://gitlab.gnome.org/GNOME/baobab/-/issues/14
1768074,2020-07-17 09:39:13 UTC,thanks
1768078,2018-04-30 18:45:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1768078,2018-06-12 19:04:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768078,2018-06-13 11:41:37 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=796577
1768078,2019-04-11 21:25:40 UTC,"Opened issue #471 on new Gnome GitLab ""gnome-control-center"" repo (old Bugzilla is deprecated now?)
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/471"
1768078,2019-04-23 12:13:13 UTC,Also see:
1768085,2018-05-11 09:47:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768085,2019-02-17 00:41:40 UTC,"The networking is ok, but the /etc/resolv.conf is deleted before every command execution. As a workaround, you can rewrite it and chain a series of commands:"
1768085,2018-04-30 18:18:23 UTC,"Setting 'export LIBGUESTFS_BACKEND=direct' does not help. I will try to find a way to build 1.38 for Ubuntu and re-try.
Thank you, Richard."
1768085,2018-04-30 18:54:37 UTC,"The difference with and without --network is in the qemu command line, basically whether
we set up a user network or not:"
1768085,2018-04-30 17:23:57 UTC,"I'm not sure, but can you try a few simple tests:"
1768085,2018-04-30 18:03:14 UTC,"Hangs on dhclient on Ubuntu 18.04, and works on 17.10:
$ virt-rescue --scratch --network -v -x"
1768087,2018-05-01 02:29:49 UTC,This sounds like it might be related to bug 1766137 or bug 1765261. You might need to wait till we have fixes for those.
1768088,2018-04-30 17:31:23 UTC,"It has been resolved with a restart of service systemd-network.
still a bug or not? I guess yes since netplan shoulkd apply directly the policy and create them."
1768088,2018-05-25 18:36:52 UTC,"Still a bug; if systemd-networkd requires a restart, then systemd-networkd has something that it gets confused about, that we'll need to figure out."
1768088,2018-11-20 18:43:39 UTC,I can duplicate this. Posted my issue to askubuntu before coming across this report. See https://askubuntu.com/questions/1094591/18-04-1-lts-systemd-network-not-applying-routingpolicyrule for details.
1768088,2018-11-20 19:13:15 UTC,"Further info: successive restarts of systemd-networkd or netplan apply (which I've since learned simply generates files and restarts networkd) applies the rule, following by the next immediate invocation removing the rule, and so on."
1768092,2021-02-18 16:45:36 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1768097,2019-01-06 18:35:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768098,2020-06-05 16:53:52 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1768098,2018-04-30 20:43:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1768098,2020-08-05 04:17:42 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1768112,2018-04-30 18:44:47 UTC,strace output of curl 7.47.0
1768112,2018-04-30 18:45:27 UTC,strace output of curl 7.22.0
1768113,2019-09-04 15:23:01 UTC,"For reference, here's some documentation about the data format that Serato uses for saving these ""Flips"": https://github.com/Holzhaus/serato-tags/blob/master/docs/serato_markers2.md#flip-entries"
1768114,2018-05-01 03:22:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768114,2018-05-12 19:54:33 UTC,Can't upgrade kodi now I've updated Lubuntu to 17.10
1768114,2020-08-10 00:36:33 UTC,kodi (2:17.6+git20180430.1623-final-0bionic)
1768115,2018-05-09 04:30:53 UTC,"------- Comment From <email address hidden> 2018-05-09 00:25 EDT-------
Is it essential to have two NUMA nodes for the guest memory to see this bug? Can we reproduce it without the NUMA node stuff in the xml?"
1768115,2018-05-09 06:01:01 UTC,------- Comment on attachment From <email address hidden> 2018-05-09 01:55 EDT-------
1768115,2018-05-09 11:31:05 UTC,------- Comment on attachment From <email address hidden> 2018-05-09 07:20 EDT-------
1768115,2018-05-09 12:51:03 UTC,"------- Comment From <email address hidden> 2018-05-09 08:47 EDT-------
(In reply to comment #26)

> Is it essential to have two NUMA nodes for the guest memory to see this bug?
> Can we reproduce it without the NUMA node stuff in the xml?
"
1768115,2018-05-10 04:40:49 UTC,------- Comment on attachment From <email address hidden> 2018-05-10 00:32 EDT-------
1768115,2018-05-09 01:41:13 UTC,------- Comment on attachment From <email address hidden> 2018-05-08 21:27 EDT-------
1768115,2018-06-18 15:36:21 UTC,"Hello,"
1768115,2019-06-03 13:55:14 UTC,Closing this bug since there is no activity or response for the last 3 months. Please re-open if you think this is still an issue that needs to be resolved.
1768115,2018-11-16 23:00:35 UTC,"This bug has not had any activity in a while, can any update be provided?"
1768115,2019-02-18 11:08:39 UTC,"IBM, could you please test with the hwe (4.18) kernel and report back if this bug is still valid?"
1768115,2018-05-14 00:50:47 UTC,"------- Comment From <email address hidden> 2018-05-13 20:45 EDT-------
(In reply to comment #30)

> Created attachment 127024 [details]
> Patch to add extra tlbsyncs and ptesyncs
>
> Try this one instead of the ""Patch to add extra tlbsyncs"". Ben H pointed out
> that it is ptesync which is important, not tlbsync (which is actually a
> no-op, though architecturally required), so this version adds a ptesync to
> the guest exit path as well as the tlbsync.
"
1768115,2018-05-08 20:40:45 UTC,"------- Comment From <email address hidden> 2018-05-08 16:37 EDT-------
Hit another instance of the RAM inconsistencies prior to resuming guest on target side (this one is migrating from boslcp6 to boslcp5 and crashing after it resumes execution on boslcp5). The signature is eerily similar to the ones above... the workload is blast from LTP but it's strange that 3 out of 3 so far have been the same data structure. Maybe there's a relationship between something the process is doing and dirty syncing?"
1768115,2018-04-30 19:20:27 UTC,Default Comment by Bridge
1768115,2018-05-07 19:00:55 UTC,------- Comment (attachment only) From <email address hidden> 2018-05-07 14:51 EDT-------
1768115,2018-05-07 18:51:02 UTC,------- Comment (attachment only) From <email address hidden> 2018-05-07 14:50 EDT-------
1768115,2018-05-07 18:50:59 UTC,"------- Comment From <email address hidden> 2018-05-07 14:48 EDT-------
The RCU connection is possibly a red herring. I tested the above theory about RCU timeouts/warning being a trigger by modifying QEMU to allow guest timebase to be advanced artificially to trigger RCU timeouts/warnings in rapid succession and ran this for 8 hours using the same workload without seeing a crash. It seems migration is a necessary component to reproduce this."
1768115,2018-05-04 13:31:01 UTC,------- Comment (attachment only) From <email address hidden> 2018-05-04 09:25 EDT-------
1768115,2018-05-04 13:30:58 UTC,------- Comment (attachment only) From <email address hidden> 2018-05-04 09:24 EDT-------
1768115,2018-05-04 13:11:06 UTC,"------- Comment From <email address hidden> 2018-05-04 09:09 EDT-------
(In reply to comment #15)

> This is not the same as the original bug, but I suspect they are part of a
> class of issues we're hitting while running under very particular
> circumstances which might not generally be seen during normal operation and
> triggering various corner cases. As such I think it makes sense to group
> them under this bug for the time being.
>
> The general workload is running IO-heavy disk workloads on large guests
> (20GB memory, 16 vcpus) with SAN-based storage, and then performing
> migration during the workload. During migration we begin to see a high
> occurrence of rcu_sched stall warnings, and after 1-3  hours of operations
> we hit filesystem-related crashes like the ones posted. We've seen this with
> 2 separate FC cards, emulex and qlogic, where we invoke QEMU through libvirt
> as:
"
1768115,2018-04-30 19:40:25 UTC,"------- Comment From <email address hidden> 2018-04-30 15:31 EDT-------
Both logs show that the dmesg buffer has been overrun, so by the time you get to xmon and run ""dl"" you've lost the messages that show what happened before things went wrong. You will need to be collecting console output from the beginning in order to show what happened."
1768115,2018-04-30 19:20:29 UTC,Default Comment by Bridge
1768115,2018-04-30 19:20:24 UTC,Default Comment by Bridge
1768115,2018-05-08 20:01:26 UTC,------- Comment (attachment only) From <email address hidden> 2018-05-08 15:57 EDT-------
1768121,2018-05-10 04:47:53 UTC,"Thanks for the heads up on the libssl issue.  Much appreciated.  It's just sad that this is where we are with the mainline kernel.
Take care."
1768121,2018-05-09 10:40:38 UTC,"This is fixed partly in the the bug https://bugs.launchpad.net/bugs/1766728 by updating Xenial package linux-base to include linux-update-symlinks binary. No fix for Trusty available so far, but the Xenial fix seems to working also with Trusty by updating linux-base to version 4.5."
1768121,2018-05-04 03:04:33 UTC,this same issue installing every kernel above v4.16.3 (which works) I was forced to reinstall ubuntu on restart during the v4.16.6 all was lost and unrecoverable.
1768121,2018-05-01 18:33:05 UTC,"Part of this bug report is a duplicate with bug 1766728, and I believe that was fixed as of a couple of hours ago. The other part of this bug report, about needing libssl1.1, isn't fixed, as far as I know."
1768121,2018-06-04 02:57:05 UTC,Hi guys.! I'm running linux mint 18.3 based on xenial and I managed to install the latest mainline kernel 4.17 using UKTool.. Just follow this steps (UKtool installation) and the programm will do the job for you automatically.. Good luck.!! https://www.2daygeek.com/uktools-easy-way-to-install-latest-stable-linux-kernel-on-ubuntu-mint-and-derivatives/#..
1768121,2018-05-01 02:36:22 UTC,same issue here
1768121,2018-05-01 01:10:32 UTC,"same problem here with 16.4,5,6 16.3 installed fine"
1768121,2018-05-01 02:36:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768122,2020-01-10 19:16:14 UTC,The TCN change issue is addressed in bug 1859191.
1768122,2020-01-10 13:35:21 UTC,PINES is seeing the change in TCN for all edited record in 3.4.2 so this probably is not related to undelete
1768122,2019-12-20 19:40:05 UTC,We have 3.4.2 on our test server and I am notable to undelete a record.
1768122,2019-08-28 16:04:34 UTC,"We are now on 3.2.7. I noticed about a month ago that I was no longer able to undelete records at all. The green popup window appears in the lower right saying the record was successfully updated, but the ""undelete"" button flashes to ""delete"" and then goes right back to ""undelete"". I asked our system administrator, and he was not able to undelete the record either. I have tried a few times since then, including today, and the same behavior happens no matter what record I attempt to undelete."
1768122,2020-02-04 22:40:10 UTC,"SCLENDS can also confirm. We're on 3.3 (3.3.5, as I write this), and I can confirm this behavior. I'm not able to undelete a record and see the same behavior Chrisy describes: when I select ""undelete,"" I get a ""record successfully updated message."" And then the ""delete"" very quickly reverts to ""undelete."""
1768122,2019-02-15 16:17:31 UTC,Possibly related to bug 1778314 ?
1768122,2019-02-15 15:49:19 UTC,"I ran into it last night. I undeleted a record in the web client, but could not clear the ""deleted"" labeling in the OPAC view. I tried searching for the Record ID in a new tab, but got the same ""deleted"" message."
1768122,2019-05-17 16:32:48 UTC,"We are currently on webclient 3.2.5. I ran into this issue this week. I undeleted a record on Tuesday afternoon. It still showed the red box around the title saying it was deleted, even though the MARC editor showed it as undeleted (and I could delete it again). I added a copy back to the record, refreshed many times, and it still showed in the OPAC view as deleted and I could not see the copy information there. Our System Admin and I tried a bunch of things, editing the LDR to change the code ""d"" back to ""n"" or ""c"", etc., with no success."
1768128,2018-04-30 20:39:50 UTC,"> Then I upgraded to 18.10.
"
1768134,2018-05-01 12:30:02 UTC,Maybe this is about gstreamer1.0-gtk3?
1768134,2018-05-02 13:08:01 UTC,"Indeed, I got the same Traceback as in issue # 83"
1768134,2018-05-03 21:09:38 UTC,I install gstreamer1.0-gtk3 and gaupol works well.
1768135,2018-05-09 07:33:46 UTC,"I'm using a different set of custom/heat/tripleo elements on a rhel7 image and I've run in the same ""Cannot uninstall 'virtualenv'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall."" error.
I've worked around it by setting DIB_INSTALLTYPE_pip_and_virtualenv to ""package""."
1768135,2018-07-09 22:01:37 UTC,Even setting DIB_INSTALLTYPE_pip_and_virtualenv to package did not help in my case with CentOS7.
1768135,2018-07-09 22:11:19 UTC,"Actually, strike my previous comment. It worked on second try."
1768141,2019-10-01 19:26:53 UTC,"Looks good to me, pushed to rel_3_1...master, thanks Chris and Galen!"
1768141,2019-05-20 20:27:46 UTC,Branch implementing this change is available here:
1768141,2019-08-02 14:43:39 UTC,"Thanks for the patch, Chris. Signoff branch is working/user/gmcharlt/1768141_signoff; that branch also contains a follow-up to change the DB update to an ""ALTER FUNCTION ... STABLE""."
1768144,2020-08-10 00:32:57 UTC,kodi 2:17.6+git20180430.1623-final-0bionic
1768144,2018-10-24 13:49:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768149,2018-05-01 00:42:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1768150,2018-07-01 12:37:07 UTC,Great ! Thanks to everybody !
1768150,2018-07-01 00:12:57 UTC,Any news ?
1768150,2018-07-01 02:39:44 UTC,"On Sun, 01 Jul 2018 00:12:57 -0000, Mathieu Dubois wrote:"
1768150,2018-05-02 07:32:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768154,2018-05-09 13:12:43 UTC,"they have not released a new version since 16.10, are they still going to continue?"
1768154,2018-07-17 02:21:04 UTC,Hello kajii narumi (kajiinarumi)
1768156,2018-04-30 23:55:34 UTC,I reported the bug after reading this question on ask.openstack.org: https://ask.openstack.org/en/question/111446/error-trove-failed-to-create-volume-for-instance-the-resource-could-not-be-found-http-404/
1768156,2018-05-18 10:10:43 UTC,"Thanks, the installation guide should be updated."
1768156,2019-04-16 10:49:59 UTC,This bug seems to be still in place... is there still work on this project?
1768165,2018-05-01 01:38:19 UTC,Reported upstream: https://github.com/mate-desktop/mate-control-center/issues/346
1768165,2018-05-01 02:46:47 UTC,"It was pointed out that dconf-editor offers a way to change the gsetting, so it's not quite true that there's *no way* to change it with the GUI. But I still think it's less discoverable or convenient for a lot of people ;-)"
1768165,2018-05-01 05:15:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768165,2020-02-09 14:40:10 UTC,Implemented in 1.22.
1768166,2019-06-02 00:28:43 UTC,"On 2019-06-02 01:08, Ping-Wu wrote:

> I might be able to personally force one or two Chinese Ubuntu forum
> participants to test your proposed changes. But that's about it for
> now.
"
1768166,2019-06-01 00:05:33 UTC,"Call for testing
================"
1768166,2019-06-01 03:05:06 UTC,"At the first run, things are looking good.  My biggest
concern--ibus-libpinyin, also is working OK!"
1768166,2019-06-01 03:28:43 UTC,"""My biggest concern--ibus-libpinyin, also is working OK!"""
1768166,2019-06-01 07:09:31 UTC,@Ping-Wu: ibus-pinyin will soon be removed from the archive.
1768166,2019-06-01 11:03:18 UTC,"I have been hearing this swan song for several years now that ibus-pinyin
is being or has been deprecated.  Actually it is a miracle that ibus-pinyin
still works in Ubuntu--*and only in Ubuntu*.  For unknown and very strange
reasons, I can never make ibus-pinyin work in Fedora, or even in Debian.
Indeed, this is the main reason that I am sticking with Ubuntu, even though
I was one of the very first supporters of the Fedora Linux when it was
being developed at the University of Hawaii."
1768166,2019-06-01 20:24:30 UTC,"@Ping-Wu: Which tools for inputting Chinese should be available on Ubuntu going forward is indeed a valid discussion, but this bug report is not a proper place for it. I notice your strong interest in the topic, and if you want to start such a discussion, I would suggest that you start a thread at <https://discourse.ubuntu.com/c/desktop>."
1768166,2019-06-01 23:08:39 UTC,Duly noted.
1768166,2019-06-09 16:41:01 UTC,The correct link should be:
1768166,2019-06-19 13:37:53 UTC,This bug was fixed in the package ibus-libpinyin - 1.11.0-1ubuntu0.18.04.1
1768166,2019-06-19 00:04:28 UTC,"I followed the steps as described in #24 and have tested the new ibus-libpinyin 1.11 in 18.04.2 for more than two weeks.  So far, I have not encountered any sudden crash problem as experienced in 1.10."
1768166,2019-06-19 10:33:17 UTC,Thanks Ping-Wu!
1768166,2019-06-19 13:25:02 UTC,"This feels like enough testing to consider this SRU verified. Thanks Ping-Wu, thanks Gunnar! Let me release this into -updates."
1768166,2019-06-19 13:37:24 UTC,This bug was fixed in the package libpinyin - 2.2.2-1~ubuntu18.10.1
1768166,2019-06-19 13:37:30 UTC,"The verification of the Stable Release Update for libpinyin has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1768166,2019-06-19 13:37:33 UTC,This bug was fixed in the package ibus-libpinyin - 1.11.0-1ubuntu0.18.10.1
1768166,2019-06-19 13:37:48 UTC,This bug was fixed in the package libpinyin - 2.2.2-1~ubuntu18.04.1
1768166,2019-05-31 23:55:24 UTC,I have done these tests:
1768166,2019-06-20 00:11:01 UTC,"I tried your ibus-pinyin ppa; the problem still persists.  I will explain
that in better detail later.  Basically, after 18.04 (no problem there),
ibus-pinyin fails to update the hierarchy of an ""entered"" word or phase in
the ""candidate list"".   This is one of the most important features of a
Chinese input tool.  Without it, thhis tool is unusable."
1768166,2019-06-09 16:47:43 UTC,"https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/bug/1768166/comments/24
<https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/comments/24>"
1768166,2019-05-30 18:00:45 UTC,"Currently ibus-libpinyin FTBFS on bionic-proposed, but this is unrelated to the changes in our package. There seems to be some SRUs ongoing there (particularly one for libio-socket-ssl-perl) that are causing some installability issues for gnome-common. It's a long dependency chain leading there, but yeah. Anyway, I have informed the people driving the other SRU to see what we can do to resolve the issue - maybe it's just transient?"
1768166,2019-06-09 10:17:34 UTC,"Hello,"
1768166,2019-05-30 16:31:18 UTC,"Hello Ping-Wu, or anyone else affected,"
1768166,2018-05-07 06:52:49 UTC,This may be a fixed bug in libpinyin.
1768166,2018-05-07 19:02:17 UTC,"Try to compile it (Ubuntu 18.04), got the following error message:"
1768166,2018-05-07 21:27:34 UTC,libpinyin 2.2.0 and ibus-libpinyin 1.10.0 are now in this PPA:
1768166,2018-05-11 01:12:02 UTC,"Thanks.  I have posted the new ppa to the Ubuntu China forum.  Believe it
will be greatly appreciated."
1768166,2018-07-10 04:17:51 UTC,[Expired for ibus-libpinyin (Ubuntu) because there has been no activity for 60 days.]
1768166,2019-05-30 16:33:33 UTC,"Hello Ping-Wu, or anyone else affected,"
1768166,2018-07-21 07:38:22 UTC,@russell-li: Are you reporting that you had frequent crashes and that upgrading via the PPA fixed the problem?
1768166,2018-07-21 08:44:23 UTC,"I don't know if upgrading via the ppa actually solved the random crash
problem, but I never had any crash after the upgrade.  There could be other
reasons including gnome upgrades.  But AT LEAST upgrading via the ppa did
not cause any negative effects.  Thus, I suggest applying the
ibus-libpinyin upgrade to the newer version for Ubuntu 18.04.1."
1768166,2018-07-28 07:13:25 UTC,"@Gunnar Hjalmarsson: yep, I had frequent crashes and that upgrading via the PPA fixed the problem. I have using it for a week and didn't find any problem, maybe the upgrading solved the problem."
1768166,2018-09-27 04:17:22 UTC,[Expired for ibus-libpinyin (Ubuntu) because there has been no activity for 60 days.]
1768166,2018-07-21 05:32:07 UTC,"I has this problem for many days, according to #3 ，I has solved this problem eventually
Thank you very much!"
1768166,2018-10-10 08:51:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768166,2019-05-30 15:57:50 UTC,"Hello Ping-Wu, or anyone else affected,"
1768166,2019-05-30 15:14:22 UTC,"Hello Ping-Wu, or anyone else affected,"
1768166,2019-05-28 10:41:12 UTC,"So generally, with my SRU hat on, after a longer discussion with Gunnar I think we should give the backport a spin - but under specific conditions. We would be keeping the SRU in -proposed for longer than 7 days and I'd appreciate some wider-testing during that time (maybe some call for testing?)."
1768166,2019-05-30 15:59:53 UTC,"Hello Ping-Wu, or anyone else affected,"
1768166,2019-05-20 14:11:34 UTC,"I have hesitated about upgrading, since the problem seems to have been present also with version 1.10 according to the crash reports."
1768166,2018-11-25 11:22:13 UTC,"I just encountered the problem again, after upgrading to libpinyin-1.10.0, but we can temporarily
solve the problem if we delete this two file:"
1768166,2018-10-10 08:58:09 UTC,"This problem in Bionic has also been reported via bug #1768192, which I have marked as a duplicate of this one. Ubuntu's error tracker reports quite a few occurrences of crashes with ibus-libpinyin 1.9.2-2:"
1768166,2019-05-20 15:11:39 UTC,"As I stated in the Chinese Ubuntu forum, I almost always stick to only the
LTS versions of Ubuntu.  I made an exception wrt 18.04 LTS and moved up to
19.04 and even 19.10 because ibus-libpinyin 1.11 is not available in
18.04.  However, 19.04 and 19.10 have their own problems and are not
recommended at least for now."
1768169,2019-07-17 23:20:44 UTC,"The problem should be fixed in git, and available in the 1.14.0."
1768169,2018-05-20 12:49:24 UTC,By disabling the Gesture parameter for my touchscreen multitouch is working. But no more pinch to zoom or to finger to scroll ... no more Gestures !
1768169,2018-05-20 12:50:41 UTC,oups sorry wrong place...
1768169,2018-11-23 01:11:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768169,2019-04-04 00:43:07 UTC,"I had a similar issue with my HP Spectre laptop, and submitted a bug to libinput: https://gitlab.freedesktop.org/libinput/libinput/issues/261"
1768169,2019-07-17 05:55:06 UTC,"I have HP Spectre X360 13"" 2019 Model, and have the same problem."
1768175,2018-08-02 03:13:13 UTC,Any help on this would be much appreciated as I have relied on ushare very much.
1768175,2018-06-02 04:16:24 UTC,"After purging the ushare package, I tried again today, but I still get the error above. This is displayed in the terminal:
The following NEW packages will be installed
  ushare
0 to upgrade, 1 to newly install, 0 to remove and 2 not to upgrade.
Need to get 0 B/53.4 kB of archives.
After this operation, 193 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package ushare.
(Reading database ... 234669 files and directories currently installed.)
Preparing to unpack .../ushare_1.1a-0ubuntu10_amd64.deb ...
Unpacking ushare (1.1a-0ubuntu10) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up ushare (1.1a-0ubuntu10) ...
Job for ushare.service failed because the control process exited with error code.
See ""systemctl status ushare.service"" and ""journalctl -xe"" for details.
invoke-rc.d: initscript ushare, action ""start"" failed.
● ushare.service - LSB: uShare
   Loaded: loaded (/etc/init.d/ushare; generated)
   Active: failed (Result: exit-code) since Sat 2018-06-02 12:14:03 +08; 8ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 23107 ExecStart=/etc/init.d/ushare start (code=exited, status=2)"
1768176,2018-06-06 01:55:21 UTC,Follow-up and clarification:
1768176,2018-06-15 22:19:28 UTC,I'd like to confirm the above observation. With GNOME the user has to hold down ALT to get the suspend option to appear on shutdown menu (IMHO this is really poor design). When the ALT key releases it wakes the computer before it has even really shut down. It is very timing sensitive. You have to release the ALT key the instant you click the button for the computer to actually suspend.
1768176,2018-05-01 21:26:17 UTC,"Hi Tom-lorinthe... I'm not so sure what is your suggestion. I should add ""acpi_rev_override=1"" after GRUB_CMDLINE_LINUX_DEFAULT=""splash acpi_rev_override=1 nouveau.runpm=0""??
In my case, when I run that command that line is commented as GRUB_CMDLINE_LINUX_DEFAULT=""quiet splash"". I am running Ubuntu 18.04, fresh install from April 26th on a Lenovo e11.
Everything works fine but the suspend feature; not with all windows closed, not at all, period.
Some guidance would be grateful.
Cheers."
1768176,2018-05-01 09:19:32 UTC,Same problem on Dell XPS 15 9560 with fresh install of Ubuntu 18.04 both X and Wayland. Did not have issue on 17.10 (X) and 17.04.
1768176,2018-05-01 09:19:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768176,2018-05-01 09:30:48 UTC,"Suspend works for me again, after adding ""acpi_rev_override=1""  with ""sudo nano /etc/default/grub"" in: GRUB_CMDLINE_LINUX_DEFAULT=""splash acpi_rev_override=1 nouveau.runpm=0"""
1768177,2019-08-04 20:17:18 UTC,"On a clean Ubuntu 18.04.2 I needed to add remote path after host (:/) to get rid of the problem, like ""sshfs remotehost:/ ~/my/mountpoint""."
1768178,2018-05-01 12:37:14 UTC,"> Here is built-in palette collected with gsettings get:
> ['#2E3436',
> '#CC0000',
> [...]
"
1768178,2018-05-01 19:12:52 UTC,"Oh, sorry, of course, I missed that background color scheme and palette scheme are dedicated and selected only first scheme, but not palette scheme (was selected Tango)."
1768178,2018-05-01 19:28:06 UTC,"> I missed that background color scheme and palette scheme are dedicated and selected only first scheme, but not palette scheme (was selected Tango).
"
1768178,2018-05-02 00:21:25 UTC,"Are you mean new abstraction, third place, preset for background, palette and other? I think it will more intuitive if all settings will be hidden to ""Advanced settings"" section."
1768178,2018-05-02 07:12:59 UTC,"> Are you mean new abstraction, third place, preset for background, palette and other?
"
1768178,2018-05-02 09:50:40 UTC,Submitted https://git.gnome.org/browse/gnome-terminal/commit/?id=e8ee9f786 to make it more obvious that we indeed define the Solarized palette correctly.
1768182,2018-05-01 19:32:44 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1768182,2018-05-05 17:38:52 UTC,"When reporting a problem with the Firefox browser, network setting
information and setting file are also attached and published. So I treated
it private."
1768183,2018-05-27 07:54:44 UTC,"I can confirm, too. However, the matplotlib report is from February 2018, and refers to pytrainer, which i also use, and does not open anymore"
1768183,2018-05-17 18:27:40 UTC,I've been experiencing the same error. It looks to have already been reported at matplotlib (https://github.com/matplotlib/matplotlib/issues/8441/) and sounds like python-matplotlib was built from a wheel rather than source with the gdk2 header files?
1768183,2018-05-17 18:08:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768190,2019-10-06 07:18:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768190,2019-10-06 07:19:30 UTC,Maybe something to do with https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1845793?
1768191,2018-05-01 12:28:55 UTC,"It is possible to have the programs launch asynchronously with a script using devilspie.  If webkit (or some other library) is what you have to use to make this applet work, perhaps there is a command I can send to the service that provides that information to the applet to ignore or delist certain windows as a work around?"
1768191,2018-05-19 22:59:52 UTC,This bug was patched by the project owner on git-hub.  Marking as Solved.
1768195,2018-05-02 04:26:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768195,2018-05-02 20:35:36 UTC,"yes, same error; crush report sent; ubuntu 18.04 snap install 75% approx on config screen crashed."
1768203,2018-05-15 15:45:24 UTC,What type of VPN connection are you using?
1768203,2018-05-15 16:39:33 UTC,I was able to solve my problem by setting the dns-priority of my VPN connection to a negative value: `nmcli connection modify <connection_name> ipv4.dns-priority -100`. You might be able to resolve your issue by setting the dns-priority of your VPN connection to a *higher* value (e.g. equal to that of the other connection). You can view the dns priorities of your connections by running `nmcli connection show <connection_name>` (the default seems to be 0).
1768203,2018-05-15 17:27:25 UTC,"This helps, but there's still a problem - resolved tries to resolve the VPN-local addresses with both VPN and global DNS. Some of those addresses are available on both sites, and I prefer the internal one when the VPN is active."
1768203,2020-09-12 10:51:25 UTC,"This works without problems, and without using `ipv4.dns-priority`, on Ubuntu 20.04."
1768207,2018-05-08 10:12:42 UTC,"@Wouter Last one is excellent find: I also noticed that sometimes my suspend leads to complete laptop freeze and force power off is necessary. Now you made realize it has to to with gnome-settings:  I can only use suspend if I did not start gnome-settings before, even though it is not running when I try to suspend."
1768207,2018-06-05 07:09:04 UTC,"For some reason, the issue does not longer exist with me. It might has to do with my /etc/default/grub where I have now GRUB_CMDLINE_LINUX_DEFAULT=""quiet splash i915.modeset=1 nouveau.modeset=0 nouveau.runpm=0"""
1768207,2018-06-04 20:19:22 UTC,@Tom didn't realize that - I'm having the exact same issues that sometimes a reboot is required after suspend (which I use heavily).. Didn't connect that with gnome-settings yet.
1768207,2018-05-08 09:55:18 UTC,An additional note is that this also seems to occur when I unlock my notebook and the settings is not yet open (but I used it before locking it).
1768207,2018-05-08 09:53:02 UTC,"Also having this issue on my Acer aspire v3-772g with clean install on 18.04, although - no nvidia driver(s) installed. Really a clean install."
1768207,2018-05-03 20:51:43 UTC,"Might this have to do with nvidia driver 390 on optimus laptops? If I ""sudo prime-select nvidia"" the problem does not occur. But with ""prime-select intel"" it has..."
1768207,2018-05-08 09:53:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768208,2018-05-24 13:48:32 UTC,Sorry. 16.04 not 16.10. I am on the LTS version
1768208,2018-05-24 16:34:45 UTC,marvin:
1768208,2018-05-28 07:03:17 UTC,"Ah, thank you very much. It works. I think before I was using wayland thus
why it didnt work."
1768208,2018-05-28 07:17:26 UTC,Ah ok. I could solve the mouse issue with
1768208,2018-05-28 07:22:09 UTC,What's the output of `find /sys/class/backlight`?
1768208,2018-05-28 07:41:21 UTC,"marvin@marvin-X1-18:~$ find /sys/class/backlight
/sys/class/backlight
/sys/class/backlight/intel_backlight"
1768208,2018-05-28 19:43:50 UTC,marvin:
1768208,2018-05-31 14:15:52 UTC,Ok. Here the result:
1768208,2018-06-01 07:29:11 UTC,https://extensions.gnome.org/extension/1222/oled-dimmer/
1768208,2018-06-01 11:49:42 UTC,"marvin, regarding comment #30:"
1768208,2018-06-18 12:20:56 UTC,"Ok, Thx for the feedback. Here is what I found so far. I will try and boot
with the different kernel parameter if needed but Ill first have to read up
on how to do that correctly."
1768208,2018-09-18 02:40:32 UTC,"Please give latest mainline kernel (v4.19-rc4) another try, thanks!"
1768208,2018-09-24 09:49:13 UTC,"Tried it and no change. The brightness is not affected by the system
settings or keys."
1768208,2019-04-10 15:11:00 UTC,Sorry for not following this - does this still happen?
1768208,2019-04-10 15:38:28 UTC,Hey. Cool.
1768208,2019-04-11 07:49:25 UTC,"Got it.
Basically we need to use ClutterBrightnessContrastEffect in GSD backlight to support brightness change for OLED systems."
1768208,2019-04-11 08:25:25 UTC,"Yea. Interesting. Could be connected to why my screen sometimes resets to
full brightness when using chromium on my X1-18 4.15.0-46-generic"
1768208,2018-05-24 13:47:43 UTC,ok. Now Im on my 16.10 system again.
1768208,2018-05-23 14:08:37 UTC,Hi
1768208,2018-05-23 16:39:41 UTC,marvin:
1768208,2018-05-13 15:38:36 UTC,apport information
1768208,2018-05-08 18:18:37 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1768208,2018-05-13 15:38:31 UTC,apport information
1768208,2018-05-13 15:38:32 UTC,apport information
1768208,2018-05-13 15:38:33 UTC,apport information
1768208,2018-05-13 15:38:34 UTC,apport information
1768208,2018-05-13 15:38:35 UTC,apport information
1768208,2018-05-23 13:37:52 UTC,kernel-bug-exists-upstream-v4.17-rc6
1768208,2018-05-13 15:38:38 UTC,apport information
1768208,2018-05-13 15:38:37 UTC,apport information
1768208,2018-05-13 15:38:41 UTC,apport information
1768208,2018-05-13 15:38:42 UTC,apport information
1768208,2018-05-13 15:38:42 UTC,apport information
1768208,2018-05-13 15:38:44 UTC,apport information
1768208,2018-05-13 15:38:45 UTC,apport information
1768208,2018-05-13 15:38:46 UTC,apport information
1768208,2018-05-19 22:49:23 UTC,"marvin, please address the all of the following:"
1768208,2018-05-13 15:38:39 UTC,apport information
1768209,2018-05-01 14:18:08 UTC,Confirmed. The tests should require the 'l3-ha' extension since it uses the 'ha' attribute [1].
1768209,2018-06-06 02:41:08 UTC,Merged in: https://review.openstack.org/#/c/565654/
1768213,2020-08-20 02:39:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768216,2018-05-01 13:21:34 UTC,Adding a few screenshots to illustrate the problem
1768221,2018-05-01 10:59:36 UTC,I was eventually able to install kubuntu via the following:
1768223,2018-08-22 10:53:34 UTC,"@aaron, I'll agree.  Moved target to 0.8.00."
1768223,2018-05-04 10:43:44 UTC,Thanks Miroslav.
1768223,2020-06-12 19:53:16 UTC,"I just tested the partial directory matching point on 0.8.13 and this appears to be fixed:
duplicity --include 'srcc/README' --exclude '**' src file://dest
Fatal Error: The file specification
    srcc/README
cannot match any files in the base directory
    src
Useful file specifications begin with the base directory or some
pattern (such as '**') which matches the base directory."
1768223,2018-12-19 09:12:07 UTC,"The actual bug here is Fix Committed, but I'll keep this as Confirmed for now until I have a chance to check the partial directory name matching point."
1768223,2018-08-22 08:06:22 UTC,"@kenneth, if this works in the 0.8-series, I am not inclined to backport it to the 0.7-series. I do not think that we should be making invasive changes like glob matching to the 0.7-series."
1768223,2018-05-01 15:40:04 UTC,"No, it should not work this way.  It should only match against full directory node names."
1768223,2018-05-01 18:31:11 UTC,"I suspect that in this specific case, it is because of the call"
1768223,2018-05-05 09:53:18 UTC,"Thanks Aaron, I just checked this version and it seems to work, since now"
1768231,2019-10-11 11:48:53 UTC,"Looks like this issue is not ""status: in progress"" any more, but ""status: abandonned"". Any update ?"
1768231,2019-09-04 20:25:00 UTC,"Same error here. I'm not entirely sure what fixed it, I don't think it was a simple restart, but I also renamed by volume_backend_name in one of them during this last run of os-cinder-install.yml, and now it seems to work? Very strange."
1768231,2019-07-26 12:38:01 UTC,We hit this problem as well.
1768231,2018-08-14 00:17:19 UTC,"Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: master
Review: https://review.openstack.org/588126"
1768231,2018-08-02 03:06:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588126"
1768231,2018-07-27 10:17:04 UTC,"As a workaround, manually restarting the cinder-volume service inside the cinder containers on the Infra nodes worked for us."
1768231,2018-07-27 05:05:08 UTC,I have hit this issue on clean installaion of openstack-ansible with ceph.
1768231,2018-07-27 04:46:27 UTC,"Hi,"
1768231,2018-05-09 18:56:21 UTC,"That patch helped with the threads dying, but noticed that an agent process would die:"
1768231,2018-05-09 18:04:32 UTC,Do you have any ERRORs in the log files of the agents that went down?  I've identified the issue here to be related to the race condition of stats running + a volume disappearing which can crash a thread:
1768231,2018-05-09 17:51:33 UTC,"We just hit this, I'm going to dive into the issue."
1768231,2018-05-09 07:59:20 UTC,"Here is an log snippet when you try to use the ""down"" backend"
1768231,2018-05-08 16:32:54 UTC,"We discussed this in our triage meeting.
We are not convinced the `scheduler_default_filters = DriverFilter` needs to happen, but the DOWN problem happened to other users, and should be fixed."
1768231,2018-05-15 09:55:53 UTC,Here is a cinder-volumes log from the point that the deployment started. Once completed some of the backends were down.
1768233,2018-05-17 11:14:09 UTC,"On lun, may 14, 2018 at 7:14 AM, Jonathan Cave
<email address hidden> wrote:

> Thanks for the workaround suggestion. To relate this back to the
> specific problem I have been facing - the part2 from the example has
> actually been a plainbox_provider plugin part. Hence, I have tried
> locally making a change to the plugin itself and the following
> stage_packages as 'builtins' (only adding setuptools didnt seem to
> work
> for me):
>
>     def __init__(self, name, options, project):
> ...
> +        self.stage_packages.extend(['python3-pip', 'python3-wheel',
> 'python3-setuptools'])
>
>     def build(self):
>         super().build()
>
>
> This gets our previous working builds going again, which is great.
> Does it seem reasonable to carry this in the plugin to you? I think
> it is acceptable.
"
1768233,2018-05-17 13:06:28 UTC,Pull request with workaround and integration test
1768233,2018-05-09 20:40:55 UTC,where I said pip I meant setuptools and you only need python3-setuptools to workaround the issue
1768233,2018-05-14 10:14:28 UTC,"Thanks for the workaround suggestion. To relate this back to the specific problem I have been facing - the part2 from the example has actually been a plainbox_provider plugin part. Hence, I have tried locally making a change to the plugin itself and the following stage_packages as 'builtins' (only adding setuptools didnt seem to work for me):"
1768233,2018-05-01 13:10:13 UTC,I bisected it and this seemed to be the culprit:
1768233,2018-05-01 12:16:29 UTC,"Note that this behaviour seems to have arisen in the last couple of months around the time of the 2.40 release to xenial. However, I haven't managed to establish exactly what changed to cause it."
1768233,2018-05-09 19:56:17 UTC,"This seems to be due to the mix of stage-packages and python-packages, where pkg_resources from the staged python is loaded and the part's pip wanting to use pkg_resources, but instead of loading its vendored version it ends up using the already loaded one from stage, here's a workaround:"
1768241,2021-01-14 13:56:10 UTC,"Hi Alireza, which version of the ceph-mon charm are you using?"
1768241,2021-01-13 14:21:26 UTC,I have got the same issue at the moment.
1768241,2020-08-29 04:17:21 UTC,[Expired for OpenStack ceph-mon charm because there has been no activity for 60 days.]
1768241,2020-06-29 12:38:11 UTC,"Is this still occurring for anyone? It's a relatively old bug, and there's been quite a lot of work done in this area of the charm since the bug was filed.  Setting to incomplete; please set back to Triaged if it's still a concern or has happened since the last update to the bug.  Thanks."
1768241,2018-05-11 22:04:23 UTC,Correction for #9. Issue cleared after about an hour of retrying.
1768241,2018-05-11 19:40:21 UTC,Hitting the same issue here upgrading from rev. 9 to 24. Just keeps looping.
1768241,2018-05-02 08:07:16 UTC,Controller model juju-crashdump
1768241,2018-05-02 11:27:40 UTC,This is my comment from: https://bugs.launchpad.net/charm-ceph-mon/+bug/1760138/comments/5
1768241,2018-05-01 18:38:28 UTC,"Hi Michael,"
1768241,2018-05-01 18:11:04 UTC,"Unfortunately, the crashdump file doesn't show when the leader changed; there's no leader-elected for it in the logs.  mysql, on the other hand is trying to do something weird with leadership ever 5 minutes.  However, there are no mysql charm unit logs in the crashdump:"
1768241,2018-05-01 16:08:49 UTC,I don't seem to see the unit-ceph-mon-0 log file which is a bit surprising.
1768241,2018-05-01 14:58:07 UTC,In attempting to debug what was happening I fired off the `leader-settings-changed` in the debug-hooks environment. After approximately four hours the same hook was still running. It looks like it's looping through every OSD in the cluster taking ~15 minutes per OSD to do... something:
1768241,2018-05-01 13:16:59 UTC,Some status logs while crashdump churns:
1768241,2018-05-02 07:55:11 UTC,Missing ceph-mon-0.log
1768244,2021-02-17 17:03:45 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1768244,2019-03-05 13:08:23 UTC,Is this still an issue?
1768244,2019-04-12 04:42:06 UTC,"Reviewed:  https://review.openstack.org/564207
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=6666e3def810bc00b4f1e732f65bd743010589fa
Submitter: Zuul
Branch:    master"
1768244,2019-11-13 08:08:13 UTC,Is this still an issue?
1768247,2019-03-07 05:20:44 UTC,Misdirected bug.
1768250,2020-05-28 19:14:12 UTC,"In Ubuntu 20.04, it does work (for me) when you use the proprietary nvidia xorg driver and have nvidia-cuda-toolkit installed."
1768252,2018-05-04 07:38:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768258,2018-07-09 08:54:12 UTC,Seems this bug was fixed. At least I cannot reproduce it any more since the recent updates.
1768258,2018-05-09 09:35:27 UTC,"I am experiencing the same problem with 18.04. After a failed login attempt and the subsequent login, the green stays black and only the mouse cursor is shown."
1768258,2018-05-08 21:59:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768258,2018-05-01 14:05:49 UTC,"Could be something similar to https://gitlab.gnome.org/GNOME/gnome-shell/issues/227 , would be worth reporting upstream"
1768258,2018-05-01 14:09:38 UTC,"Hello Sebastien,"
1768261,2018-06-13 02:57:01 UTC,I'm not sure this is a duplicate of bug 1768610. UnitySupportTest.txt shows everything is OK.
1768261,2019-01-27 13:39:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768262,2018-05-01 14:25:33 UTC,See also in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897274
1768262,2018-05-01 14:25:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768264,2019-07-25 15:32:29 UTC,Looks like a better fix has already been suggested here:
1768264,2019-07-24 18:40:39 UTC,"The line in question was introduced by rev1672, or probably 1637.1.4 more specifically.  ""Fix the colours to use public ones, and make Adwaita hover fix consistent."" from 2016-12-08."
1768264,2019-07-24 18:28:03 UTC,Confirmed that the suggested css workaround does indeed fix the problem.  Test case:
1768264,2019-07-02 10:05:47 UTC,This bug is present in a fresh install of Ubuntu 18.04.2. As a workaround I changed line 446 in terminator.py to:
1768264,2019-05-13 17:58:59 UTC,"Same here, Ubuntu 18.4 with Terminator 1.91
This bug is actually quite annoying depending on the window you have behind Terminator."
1768264,2019-01-19 21:04:44 UTC,"Experiencing the same issue as everyone else with:
Ubuntu :  18.04.1
Terminator : 1.91-1"
1768264,2018-10-16 18:16:36 UTC,"Same problem here on 18.04. Tried most things on the config side, but without success."
1768264,2018-10-01 23:53:21 UTC,Got this bug after upgrading from 16.04 LTS to 18.04 LTS
1768264,2018-07-10 16:21:33 UTC,I see this as well on 18.04 when using Ambiance or Radiance themes.
1768264,2018-06-21 09:54:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768264,2018-05-01 22:48:03 UTC,I'm also using Ambiance and I've attached a screenshot but don't think it represents what I actually see in the separator.
1768264,2018-05-01 20:54:40 UTC,"Yup, I'm on 18.04 too."
1768264,2018-05-01 20:36:36 UTC,Ah. I didn't see Egmont's follow up comment. More info from you Brian would still be useful.
1768264,2018-05-01 20:33:29 UTC,This is typically because of how the theme is drawn.
1768264,2018-05-01 19:10:16 UTC,"I can confirm this with Ubuntu's default Ambiance theme. (Not with GTK+'s default Adwaita, though.)"
1768264,2018-05-01 19:09:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768272,2018-05-02 11:55:02 UTC,We already have a repeat last wire hot key (insert) for precisely this which is faster than moving the mouse and double clicking.  The horizontal and vertical repeat spacing are configurable.  I don't know that the double click feature buys us much but I'm not opposed to it as long as it doesn't change the behavior of anything else.
1768272,2018-05-02 12:13:35 UTC,"I didn't know about the insert. But testing it now, it just repeat the last segment of the wire.
I wanted a feature the repeat all the last wire from the beginning to the end, starting the new wire on the mouse is."
1768272,2019-05-04 19:54:55 UTC,"Just adding to my last comment: because the <insert> use a constant space and something the part pins are not constant or doens't match with one grid space (use two, for example)."
1768282,2018-05-01 16:17:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/565532"
1768282,2018-11-22 12:42:55 UTC,"Change abandoned by Jens Harbott (frickler) (<email address hidden>) on branch: master
Review: https://review.openstack.org/565532
Reason: Patch is in merge conflict for some time, feel free to restore and rebase if you want to continue with this."
1768283,2019-09-05 13:44:33 UTC,"Checkbox fails to recognize the alias device (encc000.2653) as a network device and test it.  Because encc000.2653 is ignored by checkbox, network tests on the Z Lpar always fail, as checkbox tries to use encc000 to test instead, which is not possible."
1768283,2018-05-02 14:19:37 UTC,"FWIW, I talked to Frank about this, thinking it was just a configuration that could be changed easily. Turns out this config method is pretty common in s390x deployments when LPARs are all sharing the same network device but connecting to multiple VLANs.  So, unfortunately, we do need to sort out how to ensure this gets tested, rather than just ask for a different network configuration on my LPAR."
1768283,2019-09-05 11:43:22 UTC,What do you mean by 'Checkbox is not able to test'? Targeting Slave with remote? Some job fails to see the target?
1768283,2020-12-18 17:31:45 UTC,"Not expired, this is still an issue and affects every time I do testing on s390 (IBM Z)."
1768285,2018-05-02 18:16:51 UTC,I'm actually testing again the tasks on the containerized undercloud and might have something working. I'll keep you posted here.
1768291,2019-02-13 00:28:41 UTC,"Same as what Chris mentioned. I occasionally use a Hauppauge 950Q USB device that has IR support on my laptop, but I don't keep it plugged in 24/7 since I frequently travel with this laptop. I don't want to mess around with scripts and disable services, so right now my ""workaround"" is to only install lirc when I want to use it, and uninstall it when I don't need it."
1768291,2021-02-06 18:28:57 UTC,"So, now it's been two years since I first encountered this issue on 18.04.
I'm wondering if it has been fixed for 20.04 ...
based on lack of activity in this ticket I supposed it won't be fixed.
I'd like to use LIRC but I guess I'll abandon it forever since I
refuse to let it spam my SSD's syslog."
1768291,2019-01-18 19:01:37 UTC,"This problem also affects me. I am running Ubuntu 18.04 LTS with MythTV, and I sometimes plug in a remote control USB. When it's not plugged in, LIRC spams the syslog. I tried to disable startup of lircd daemon but that didn't seem to work.
   sudo systemctl disable lircd.service
   sudo systemctl disable lircd.socket
and this appeared to set the links in /etc/rc2.d to be ""K*lircd (kill) ) but
the glob spamming still occurred after the next reboot."
1768291,2018-12-17 21:38:22 UTC,"  I had this same problem
 I used sudo apt-get remove  lirc
 That stoped the logs
I never installed lirc So it must have installed during upgrade to 18.04"
1768291,2018-05-04 13:38:49 UTC,"Hello,"
1768291,2018-12-18 08:59:51 UTC,"Indeed that problem has also been reported to Debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860296"
1768294,2018-05-04 21:52:02 UTC,"That can't be the end as that's not even a complete and valid config file. Openbox would complain at you when you tried to run it. My guess is that you're not arrowing down enough. Nano should say ""Read 744 lines"" in its status when you open it. That doesn't look like 744 lines. :)"
1768294,2018-05-05 01:02:18 UTC,"Success!!!  I did use sudo, but using the ""lxqt"" option brought me to the
""744 lines"" and I used your shortcut to get me to line 192 and then
scrolled down to the end right before ""mouse"" and I dropped your code in
and . . . seems like I must have done ""OK"" because hitting the eject key .
. . opens the tray!!  I'm ready to be hired as a ""programmer"" . . . .  : -
))"
1768294,2018-05-05 00:42:38 UTC,"The file is ~/.config/openbox/lxqt-rc.xml. Since it's in your home folder (~), you don't need to sudo anything. I'm not sure what file you're looking at but it's most certainly not the right one based on what you're explaining or unless you broke something. That said, there's no reason why nano can't do the trick, but it might be wise to just open it up in a graphical editor since it's a little more user friendly."
1768294,2018-05-05 00:02:12 UTC,"Thanks for the reply . . . but, no, I didn't figure anything out . . . I
just copy/pasted what you provided after the ""sudo nano"" . . . and what I
pasted here is what was there . . . I tried to arrow down or up, but the
scroll bar was ""full"" . . . i.e., what was showing was the full show . . .
and then the statement about ""don't edit this file"" etc, etc . . . there
was nothing anywhere along the edges of the window saying something about
""192 pages"" . . . as there sometimes might be."
1768294,2018-05-04 21:33:40 UTC,"Ran the suggested commands, but it didn't show anything like <keyboard> ???  Operator error??  I copied/pasted your data with ""sudo nano"" in front of it and got:
[code]
<?xml version=""1.0"" encoding=""UTF-8""?>"
1768294,2018-05-03 21:42:24 UTC,@walter:
1768294,2018-05-03 21:08:33 UTC,"Actually `eject` is a standard part of the install and doesn't even require the device name. Obviously if there's more than one device and you want to open one over the other, it needs to be specific, but there's always a default device. That said, the solution is fairly easy:"
1768294,2018-05-03 20:49:43 UTC,"""Thomas Schmitt <email address hidden> via canonical.com"
1768294,2018-05-03 20:43:49 UTC,"O . . . wow . . . (putting bong down now) . . . didn't know that was a
question . . . sorry . . . (cough, cough) . . . ."
1768294,2018-05-03 20:08:00 UTC,The question I was trying to ask was what specific command you use.
1768294,2018-05-03 19:46:02 UTC,"That is what I am doing now in Lu, using the console command . . . minor inconvenience factor, but considering that Lu Next is like ""next gen"" in appearance it would be value added to have keyboard full function . . . ."
1768294,2018-05-03 18:39:28 UTC,"Actually, yeah, that 204 I got from some wiki page. It seems the possible keycodes are:"
1768294,2018-05-03 14:46:46 UTC,"This is the last ""KeyRelease event"" . . . and then there was a **bunch** of ""EnterNotify event"" and possibly ""MotionEvent""???  As far as I recall I just hit the eject key and released it."
1768294,2018-05-01 22:40:19 UTC," 1. Open up the terminal
 2. Type xev
 3. Hit enter
 4. Press the eject key
 5. Close the window that was opened by xev
 6. Copy and paste the last ""KeyRelease event"" from the terminal here"
1768294,2018-05-01 21:07:50 UTC,"""As long as hitting the key in `xev` produces a named keysym (should be XF86Eject), I'd feel relatively comfortable with that. Hopefully you get keycode 204, too."""
1768294,2018-05-01 20:14:49 UTC,"Regardless of how it works elsewhere, in Openbox it depends on the name of the key and optionally the keycode. It may be different and perhaps more flexible in other window managers. That said, I still need the above information to get this implemented in Lubuntu."
1768294,2018-05-01 19:56:25 UTC,@walter:
1768294,2018-05-01 18:23:50 UTC,"As far as I know, there's no binding in the Openbox configuration for an eject key either upstream or within lubuntu-default-settings, nor has there ever been. Assuming that the keybinding is standardized, we can make it a wishlist item for lubuntu-default-settings, though."
1768294,2018-05-07 15:58:57 UTC,"The system won't clobber over your config files on update/upgrade, at least not the ones in your home. It will ask you if it notices that things have changed on systemwide stuff."
1768294,2018-05-07 17:13:26 UTC,@walter:
1768296,2018-06-04 15:00:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768296,2018-05-01 23:39:20 UTC,Is this maybe related to this upstream bug https://github.com/mate-desktop/mate-terminal/issues/209 ?
1768300,2018-05-16 18:51:40 UTC,"Confirmed, EG v.2.12."
1768300,2019-04-09 19:22:46 UTC,Confirmed in web client 3.2.4. Could this be related in any way to the new feature in MARC Edit which now leaves the help enabled while you remain in the record so you can continue to refer to it?
1768308,2018-08-02 22:57:59 UTC,"@Richard Harding (rharding),"
1768308,2018-08-02 14:33:19 UTC,"I'd like to challenge the need for model-constraints. The constraints stored in the model are just the values that will be used when applications are brought in without anything specified on their own. It's the same set of values, just if it's the default values the model thinks about."
1768308,2018-08-02 02:58:58 UTC,I just remembered that I once got an error when using `--model-default` and I had to use `--config` instead. The error said that the key wasn't applicable. So I don't think these two can be used interchangeably. Testing needed.
1768308,2018-08-02 02:56:14 UTC,Nicely done.
1768308,2018-08-02 02:09:19 UTC,"1. (TO-DO)
I have verified that indeed the constraints specified at bootstrap time only stored for the initial two models. It was not an intent and we will rectify. The behavior will be analogous to --config which when specified at bootstrap is treated as default/initial for all models added to the controller. Consequently, model constriants specified at bootstrap will be treated as default model constraints for all models added to this controller."
1768308,2018-08-01 16:18:12 UTC,I had to read your comment a few times but I still don't see how it explains what Sandor and I have observed: that `bootstrap --constraints` only applies to the 'controller' and 'default' models.
1768308,2018-08-01 10:28:13 UTC,"Ok, I can see where the confusion arises.."
1768308,2018-08-01 09:23:49 UTC,Just wanted to confirm Peter's point that `juju bootstrap --constraints` only seems to affect the 'controller' and 'default' model. Those constraints were not applied to any other models I created.
1768308,2018-08-01 04:47:29 UTC,"Well I guess there's a bug then. I, of course, tested all this before spending time with this. The constraints do *not* apply to new models."
1768308,2018-08-02 23:59:28 UTC,@Anastasia
1768308,2018-08-01 02:42:57 UTC,I put a lot of thought into my suggested wording in bug 1784675 which was marked as a duplicate of this bug (which I find dubious btw). I don't want to lose that. Here it is:
1768308,2018-07-31 23:01:58 UTC,This is correct.
1768308,2018-07-31 17:24:34 UTC,"Actually, let me correct that."
1768308,2018-07-31 15:43:52 UTC,"IMO, --constraints should be deprecated. All it does more than --bootstrap-constraints is add constraints to the 'default' model."
1768308,2018-07-18 03:27:10 UTC,"Just a follow up, the code to determine constraints for bootstrap is in the code starting from https://github.com/juju/juju/blob/develop/environs/bootstrap/bootstrap.go#L259"
1768308,2018-07-10 12:21:23 UTC,"@Peter Matulis (petermatulis),"
1768308,2018-05-02 13:59:22 UTC,Thanks. I will open a bug for fixing the help. Currently it shows:
1768308,2018-05-02 12:24:49 UTC,"actually it is the other way around. --constraints affects everything,
including the controller and any future applications that are deployed.
--bootstrap-constraints only effects the controllers and not deployed apps."
1768308,2018-08-01 02:56:15 UTC,"@Peter Matulis (petermatulis),"
1768308,2018-08-03 00:25:08 UTC,"@Peter Matulis (petermatulis),"
1768312,2018-06-08 12:28:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768318,2018-05-15 01:43:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768330,2019-07-22 02:26:38 UTC,"I came back to this following the 4.8 release and I think I have an efficient algorithm that groups text blocks together. The catch is there's no way to get the text blocks in a nice list, because block elements can contain other block elements. That's why my original plan fell apart when I started looking at nested lists. I was trying to turn a nested data structure into a list, and there's no general way to do that. Any given strategy will look good on some pages (or parts of pages) and bad on others."
1768330,2019-05-08 12:28:22 UTC,Ignore the last comment -- I meant to post it on bug #1828188
1768330,2019-05-08 12:20:43 UTC,Another way of doing this would be to use currently unused operators for this purpose. Then you could get syntax like:
1768330,2018-08-02 01:57:58 UTC,I find this problem interesting so I spent a little time investigating it. I put a list of the HTML block elements into HTMLTreeBuilder and wrote some code like this:
1768330,2020-09-26 15:33:50 UTC,"I've marked bug 1882067 as a duplicate of this issue, although they're not directly related, because I think they come from the same place: a desire to use Beautiful Soup as a text preprocessor that can strip away ""useless"" markup."
1768330,2018-05-01 19:03:17 UTC,"I just stumbled upon separator=' ', but sadly that option is also useless / semantically nonsense:"
1768330,2018-05-01 18:52:22 UTC,"Sorry, I forgot to specify the version: python-beautifulsoup4-4.6.0-2.fc27.1"
1768330,2018-07-16 23:34:04 UTC,"Thanks for your thoughtful bug report. I would say you've run into the limitations of what Beautiful Soup is designed to do. The library has just enough understanding of the semantics of HTML that parsing a valid document and writing it back out won't alter the document's semantics. This means Beautiful Soup needs to know which HTML elements are void elements, which elements give significance to the whitespace inside them, and so on."
1768335,2018-12-05 04:36:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768335,2020-08-09 23:41:26 UTC,pdfsam-basic (3.3.5-1)
1768340,2020-05-01 11:05:33 UTC,"I also upgraded to the latest fscrypt which supports policy_version 2, and I confirm that snap upgrades work without issues of losing user settings."
1768340,2018-08-27 09:52:31 UTC,"Yeah, same here. Migrating to Linux Mint because it is easier, and the home encryption is a must have for me, despite it's drawbacks etc. The Ubuntu shouldn't call the latest 18.04 release as LTS release - I do not understand why the backward compatibility is broken from one LTS release to another.."
1768340,2020-05-01 10:38:02 UTC,"Actually, I was using policy_version: 1 until I upgraded the fscrypt package to be recent enough to include support for policy_version: 2. Everything I've tried so far works fine with the new policies. That includes refreshing snaps and mounting my home directory into a lxd container."
1768340,2020-04-26 20:10:26 UTC,"On 20.04 I I have the issue upgrading Chromium (which is installed from snap package).
The issue looks like @adembo's: permission is denied when upgrading snap. So after an upgrade all my Chromium user settings are reset.
Also I have a ""permission denied"" problem opening hidden files from Chromium.
I've set up the fscrypt using this guide: http://tlbdk.github.io/ubuntu/2018/10/22/fscrypt.html"
1768340,2020-03-31 14:33:10 UTC,@legovini: I can reproduce this on focal with policy_version:2 (see LP:#1867426).
1768340,2019-07-14 19:18:02 UTC,"Be advised that it is dangerous to use fscrypt without umask 077, as any user can read the contents of any file you access even if they don't have the security token."
1768340,2019-05-09 21:04:45 UTC,"Is this still an issue with Cosmic and later releases, shipping fscrypt 0.2.4-2?"
1768340,2019-05-05 19:54:34 UTC,The method described by @tlbdk works on Ubuntu 19.04. I'd like to get this working on a series of Ubuntu 18.04.2 LTS machines. But the packages are at 0.2.2 rather than 0.2.4.
1768340,2019-04-24 08:03:27 UTC,"I did run into the same issue as @adembo. snap refresh does not work, if the home directory is encrypted (fscrypt).
The snap is lxd (linuxcontainer). snap refresh => ... Required key not available"" (1)).
But doing a
snap remove lxd; snap install lxd
is not an option - as this resets the whole lxd installation - ending up without any lxd configuration (no network, no storage pools, no containers ...)"
1768340,2018-10-23 19:56:50 UTC,"I got fscrypt working with home folder encryption on Ubuntu 18.10 with some small fixes, I have created a guide here:"
1768340,2018-08-09 12:45:24 UTC,"Ubuntu 18.04.1 is released., This issue is not fixed, not addressed, not acknowledged as being an issue by key developers, and no plans to do this in the future were announced."
1768340,2018-08-09 09:37:13 UTC,Bump! This is must-have feature which should be working and re-enabled as an option during the installation! No more Ubuntu for me if this encryption won't be fixed/restored.. It is very useful when you are running headless server somewhere where you do not have access to type the full disk encryption password! You can still encrypt other mounts with LUKS whatever you like anyway.
1768340,2018-08-01 07:02:59 UTC,"This bug needs to be assigned a high priority, because right now there is no working encryption method that is considered reliable.
• ecryptfs is considered buggy and insufficiently maintained.
• fscrypt is unusable as described in this bug report.
• Full-system encryption is unsuitable for most users, because it wipes any other OS such as Windows. (There is an alternative — https://goo.gl/KtsLMk — that doesn't do this, but it has two important flaws.)"
1768340,2018-07-03 23:40:48 UTC,"Spoke too soon: the simple workaround is ""snap remove gnome-calculator; snap install gnome-calculator""."
1768340,2018-07-03 23:38:56 UTC,"Trent Lloyd, did you manage to work around the problem with broken snaps? Asking because it looks like there's an update for the gnome-calculator snap that has broken the calculator on my system. Nothing happens when I run it, and if I run ""snap refresh"" from the command line, I get the following error:"
1768340,2018-06-18 15:51:29 UTC,"I have been waiting eagerly to migrate my laptop from 16.04 to 18.04. 16.04 is getting old for some of the stuff I am doing. I have a 1TB SSD disk with 800 GB of ecryptfs-encrypted data in my home folder. I wouldn't mind whole disk encryption, but I have at the moment no place where to temporarily store the 800 GB of data to select the full disk encryption. The situation is ridiculous..."
1768340,2018-05-07 20:21:16 UTC,"Having used this configuration (with upstream fscrypt) for a week, I'm finding that some logins are successful while others are not. So there's still some underlying intermittent issue"
1768340,2018-05-03 10:41:46 UTC,"So we cannot encrypt our home directory the old way in Ubuntu 18.04, and we cannot encrypt home the new (fscrypt) way as adviced in the release notes."
1768340,2018-05-03 10:28:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768340,2018-05-02 02:03:16 UTC,"It works for me with my workaround applied, however your groups get messed up on login due to this bug: https://github.com/google/fscrypt/issues/77"
1768340,2018-05-01 20:23:31 UTC,I built fscrypt from upstream (v0.2.3-8-g3e32282) and this issue no longer manifests. So whatever bug I'm running into has been fixed upstream.
1768345,2018-05-04 20:31:26 UTC,"I have fixes for this, but it's unclear how/where to contribute this code."
1768345,2018-05-08 19:57:26 UTC,Patch was accepted into https://salsa.debian.org/debian/ifenslave
1768351,2018-05-02 04:43:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768352,2018-11-27 23:43:42 UTC,"The best solution is to backport the release currently in Cosmic and Disco, because these are just bugfixes."
1768352,2019-02-13 08:34:26 UTC,"I can confirm the updated mate-screensaver fixes the issue (somehow). There is still maybe half-second blink of visible desktop when I disconnect an external monitor from HDMI port while the screen is locked. After that, the screen is properly locked. Still, the quick blink of desktop is a security issue and it might also be possible for a malicious hacker to insert a USB device which emulates keyboard and might kill the screensaver completely while the screen blinks."
1768352,2019-02-13 01:01:09 UTC,"Oh! Simon has already prepared an update, it just needs someone to test it and report that it works:"
1768352,2019-02-07 19:56:17 UTC,"Hello Eugene, are you in a position to be able to prepare an update for this issue?"
1768352,2019-02-07 17:25:12 UTC,"So what's up with this security issue?
I've reported it to mate-desktop and they says that it is up to Ubuntu maintainers to release fixed version.
https://github.com/mate-desktop/mate-screensaver/issues/180
It is a critical security issue and I had to switch to different window manager on my work laptop because this issue places my work laptop and thus my employer at risk. Require update for Ubuntu 18.04 ASAP!"
1768352,2019-01-03 18:32:35 UTC,"Same issue with DisplayPort (Blank lockscreen, unplug the display cable, wakeup lockscreen, plug cable to bypass)."
1768352,2019-01-03 17:39:40 UTC,"Topic linked on Mate forum:
https://ubuntu-mate.community/t/security-issue-lock-screen-not-retained-when-exit-screensaver-with-tv-hdmi/18655"
1768352,2020-01-29 12:53:53 UTC,it's 2020 and this is still not fixed in 18.04 LTS. the fix has been available at least since September 2018. ubuntu is a joke not an OS....
1768352,2019-01-03 17:38:56 UTC,I had this problem today with a TV plugged into HDMI on 18.04.1 Mate (mate-screensaver 1.20.0-1). How to track the progress of the patch in SRU 18.04? How to check that a machine with 18.04 will be patched?
1768352,2018-12-07 08:18:43 UTC,"Test case for SRU should include reproducing the original problem that you are trying to fix, and not refer elsewhere for a ""more detailed test case""."
1768352,2019-04-05 20:57:48 UTC,"An upload of mate-screensaver to bionic-proposed has been rejected from the upload queue for the following reason: ""rejected due to lack of adequate SRU test case as requested on the bug""."
1768352,2018-10-28 15:02:55 UTC,Any progress on fixing this in the LTS version?
1768352,2018-05-01 21:06:14 UTC,Output of dmesg after monitor finishes booting (and I can now just the screen as if it wasn't locked)
1768352,2018-05-01 22:57:50 UTC,"Thanks Fizzfadlt, I forgot this script doesn't set the bug public. I've done so now. (The trick is the ""private security"" link in the upper right hand corner -- change that to ""public security"".)"
1768352,2018-09-27 10:56:24 UTC,This is fixed in Ubuntu MATE 18.10 via mate-screensaver 1.20.2-1 which we will SRU to 18.04.
1768352,2018-05-01 21:03:53 UTC,Output of mate-screensaver after locking screen
1768352,2018-05-01 21:04:30 UTC,output of mate-screensaver after powering off (soft off) monitor
1768352,2018-05-01 21:04:54 UTC,Output of dmesg after powering off (soft off) monitor
1768352,2018-05-01 21:03:31 UTC,"Output of mate-screensaver --debug
before locking"
1768352,2018-05-01 21:05:42 UTC,Output of dmesg after powering monitor back on
1768352,2018-05-01 21:10:54 UTC,"Re: ""UpgradeStatus: No upgrade log present (probably fresh install)""
I didn't use `do-release-upgrade` by mistake.
I changed `artful` to `bionic` in sources.list and slowly did dist-upgrade carefully.  I didn't realize that would actually be considered an upgrade and I could not do `do-release-upgrade` afterwards."
1768352,2018-05-01 21:52:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1768352,2018-05-01 22:44:41 UTC,"Can you help me make this bug public, so that the upstream bug can refer to information here?
I can't see how to do that."
1768352,2018-05-01 21:05:24 UTC,output of mate-screensaver after powering monitor back on
1768356,2018-05-01 21:24:17 UTC,"Fixed with ""fuser -vik /var/cache/debconf/config.dat"" but apparently some seconds later it was already unlocked."
1768364,2018-05-02 02:02:44 UTC,"@Daniel, this is not just Rhythmbox. It's across many interfaces. It just happened to be on Rhythmbox now when it occurred multiple times."
1768364,2018-05-02 02:10:20 UTC,Here's an example of it happening randomly in gnome-control-center.
1768368,2018-05-01 22:47:36 UTC,Accidentally uploaded an older version of the patch. This patch is my actual proposed fix.
1768371,2018-05-01 23:32:00 UTC,"(ProcCpuinfoMinimal.txt indicates a Pi 3, not 3 B+, but that's the hardware the userland was attached to while reporting this.  The dmesg output is from when it was attached to a 3 B+)."
1768380,2019-10-13 13:27:51 UTC,The error seems to originate in the call to the cuserid function in loadsave.c. It returns an address that is not accessible. I suspect this happeens because cuserid is not thread safe. The easiest workaround is to not call cuserid at all.
1768380,2019-10-13 16:28:29 UTC,"The attachment ""loadsave.c.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1768384,2018-05-03 21:52:53 UTC,"This seems to be a problem in curtin. For easy reproduction, I've uploaded a raw disk image that was formatted by freenas to https://people.canonical.com/~mwh/target2.tgz (it's a 10G image, but sparse). Then run ""kvm -m 1024  -boot d -cdrom ~/isos/bionic-live-server-amd64.iso -hda ~/images/target2.img"" or whatever paths required on your system and try to install do the disk; it will fail with errors in the logs about zpool not being installed, but really curtin should be wiping the disk by writing zeros, not by trying to carefully dismantle the zfs setup."
1768384,2018-05-04 08:40:01 UTC,@Michael
1768387,2018-09-20 09:53:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768390,2018-05-22 01:30:20 UTC,Also happens with 396.
1768390,2018-05-02 06:08:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768390,2018-05-17 22:40:55 UTC,I can confirm this bug too with the same configuration. Seems like the nvidia 390 driver is broken in Bionic (for primus at least).
1768390,2018-05-23 18:29:39 UTC,Still broken as of today on Ubuntu 18.04 with kernel 4.16.7.
1768390,2018-06-19 08:53:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768390,2019-02-21 23:46:37 UTC,This issue still occurs on kernel 4.18 with nvidia 415. The workaround is to export __GLVND_DISALLOW_PATCHING=1
1768391,2018-05-02 04:29:03 UTC,The above patch fixed my problem but I'm not sure if it's the best way of handling this kind of issues ...
1768391,2018-05-02 04:08:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/565639"
1768391,2018-05-02 03:58:49 UTC,"If I remove the constraint from the floatingip.py resource, I get farther :"
1768391,2018-09-04 07:25:49 UTC,"Change abandoned by Thomas Herve (<email address hidden>) on branch: master
Review: https://review.openstack.org/565639"
1768391,2018-05-02 03:27:19 UTC,So this makes the creation of floating ip net/subnet/etc using heat but prevents heat from using the resource it will create when the stack actually runs.
1768391,2018-05-02 07:21:12 UTC,What if you do:
1768391,2018-05-02 03:46:17 UTC,"[root@undercloud-0-rhosp10 ~]# heat stack-create -f stack_5router.yml test
WARNING (shell) ""heat stack-create"" is deprecated, please use ""openstack stack create"" instead
ERROR: Property error: : resources.floating_ip.properties.floating_network: : Error validating value 'public_net': Unable to find network with name or id 'public_net'"
1768393,2018-05-02 04:30:09 UTC,It might be a random race condition as the stack creation still fail randomly even after that.
1768393,2018-05-02 07:22:47 UTC,"That really looks like a neutron error, no?"
1768400,2018-05-18 10:07:52 UTC,Need more informations for this too.
1768403,2018-05-02 17:06:13 UTC,"It was 18.04 desktop.  But it also affects things based on Ubuntu like Mint.   So it's in your core installer somewhere (maybe grub2?), i can reinstall fedora and pclos to ensure they didn't turn off the bit, I don't recall them doing so."
1768403,2018-05-02 16:48:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1768407,2018-10-11 21:06:20 UTC,"Bug still present, really annoying ..."
1768409,2018-05-02 16:06:07 UTC,From DpkgTerminalLog.txt:
1768409,2018-05-24 21:58:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768412,2021-02-09 20:07:06 UTC,This bug was fixed in the package geany-plugins - 1.37+dfsg-5
1768412,2018-05-02 16:33:59 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1768412,2018-05-02 19:33:52 UTC,"There's a PR[1] to port some of the plugins over to webkit2gtk, but it
hasn't been merged yet and now that Bionic's released, we're not going
to see the plugins reenabled for this Ubuntu release. :("
1768412,2021-01-24 22:38:12 UTC,"The relevant plugins got ported upstream:
https://github.com/geany/geany-plugins/pull/746"
1768412,2021-01-26 19:24:23 UTC,">How can we upgrade these in the Ubuntu packages?
"
1768412,2021-01-27 05:44:12 UTC,"On Tue, Jan 26, 2021 at 07:24:23PM -0000, Hans Joachim Desserud wrote:

> >How can we upgrade these in the Ubuntu packages?
>
> I saw the pull request, and those changes seem to have been released in
> upstream version 1.34.0.
>
> Checking the latest version in Ubuntu Hirsute
> (https://bugs.launchpad.net/ubuntu/+source/geany-plugins/1.37+dfsg-
> 4build1), they are still missing though. As mentioned in comment #1,
> those plugins were disabled in the Debian build, and it looks like they
> haven't been re-enabled even though newer releases have been packaged.
>
> I found several Debian bug reports talking about it, but the most
> specific is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954791
> which also includes a PR to resolve the issue.
>
> So most likely, that PR will be accepted into Debian and then Ubuntu
> will sync the newer version.
>
> ** Bug watch added: Debian Bug tracker #954791
>    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954791
>
> ** Also affects: geany-plugins (Debian) via
>    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954791
>    Importance: Unknown
>        Status: Unknown
>
> ** Tags added: focal groovy hirsute packaging
>
> ** Changed in: geany-plugins (Ubuntu)
>        Status: New => Confirmed
"
1768417,2018-05-09 18:04:36 UTC,see this discussion:
1768417,2018-05-09 17:39:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768418,2018-05-07 08:32:49 UTC,We used to have a primitive and incomplete web socket implementation but it is gone now. I ack the need for a notification channel though I think we should discuss the details on the forum.
1768419,2018-05-02 05:10:18 UTC,https://forum.snapcraft.io/t/pass-through-snapd-client-user-agent-to-store-requests/
1768419,2018-05-07 08:34:52 UTC,This looks like a valid thing to do. Marking as triaged.
1768419,2019-01-17 11:55:26 UTC,Since this was written we've been aware of the desire and we've tried to push towards having context in more places to enable this in the future. It'd still be a lot of work though.
1768419,2019-03-20 17:22:46 UTC,"We don't have ""context"" everywhere yet so doing this ""fully"" is probably a bit of work still. However I chatted (on irc) with Evan and it seems if we can get the user-agent string to ""info"", ""search"", ""install"" (in that order of priority) that would help already. So it seems worthwhile to explore if we can do that and if its easier/quicker that way (and eventually we will have the full solution)."
1768419,2019-09-17 13:02:50 UTC,https://github.com/snapcore/snapd/pull/7100
1768422,2018-05-03 07:41:27 UTC,apport information
1768422,2018-05-03 07:41:30 UTC,apport information
1768422,2018-05-03 07:41:33 UTC,apport information
1768422,2018-05-03 07:41:14 UTC,apport information
1768422,2018-05-09 09:07:04 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-May/092121.html
1768422,2018-05-03 07:41:24 UTC,apport information
1768422,2018-05-03 07:41:37 UTC,apport information
1768422,2018-05-03 07:41:21 UTC,apport information
1768422,2018-05-03 07:41:06 UTC,apport information
1768422,2018-05-03 07:41:12 UTC,apport information
1768422,2018-05-03 07:41:09 UTC,apport information
1768422,2018-05-03 07:41:04 UTC,apport information
1768422,2018-05-03 07:41:01 UTC,apport information
1768422,2018-05-02 05:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1768422,2018-05-03 07:41:16 UTC,apport information
1768425,2018-05-02 13:22:26 UTC,Well something in the stack steals my IP:
1768425,2018-05-02 07:25:41 UTC,Heat doesn't create any port in the Subnet resource.
1768425,2018-05-02 13:34:08 UTC,It looks like this is what steals the IP:
1768428,2018-09-16 23:09:44 UTC,This happens even with one monitor on Thinkpad T470.
1768442,2018-05-07 23:17:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768444,2020-01-08 19:43:52 UTC,This issue has been reportet to Inkscape's new Bugtracker on Gitlab. https://gitlab.com/inkscape/inbox/issues/748
1768444,2018-05-02 10:33:21 UTC,"- confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- confirmed on Windows 10, Inkscape 0.92+devel (7f24a76, 2018-04-17)"
1768444,2018-05-02 10:39:04 UTC,"transforms of the type:
       gradientTransform=""matrix(0,0,0,0,460.46556,-735.52614)"""
1768444,2019-07-08 08:46:54 UTC,"An easy workaround is to use ""Flat color"" instead of ""Swatch"" in the Fill and Stroke window (Shift+Ctrl+F). You can still set your color from a swatch, just remember to click back the flat color - the color won't change. This also applies to Stroke paint. I couldn't fix the ""$12 sessions$"" circle since the text is not a separate object - it would just fill the whole circle with one color."
1768446,2020-01-25 22:29:56 UTC,"On a second thought, this is a duplicate of https://bugs.launchpad.net/inkscape/+bug/1571955."
1768446,2020-01-25 22:02:20 UTC,"In this case, it's due to the <svg:flowRegion> being to small vertically, so the text doesn't fit. Text elements become unselectable in this case; see https://gitlab.com/inkscape/inbox/issues/1679."
1768446,2018-05-03 00:12:32 UTC,The WARNUNG text is also not displayed in Inkscape 0.91.
1768452,2019-05-09 11:31:57 UTC,"For Disco (no failure but reported 1 failed), please refer to bug 1827845"
1768452,2020-04-22 14:16:36 UTC,"247.	04/07 11:10:34 DEBUG| utils:0153| [stdout] [ 89.844896] test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations PASS
248.	04/07 11:10:34 DEBUG| utils:0153| [stdout] [ 89.846168] test_bpf: #244 BPF_MAXINSNS: Call heavy transformations PASS
04/07 11:10:34 DEBUG| utils:0153| [stdout] [ 89.930042] test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id PASS"
1768452,2020-04-07 09:32:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1768452,2020-04-28 21:57:20 UTC,This bug was fixed in the package linux - 4.4.0-178.208
1768452,2019-04-16 06:41:59 UTC,This has passed on Cosmic zVM.
1768452,2018-11-02 12:18:41 UTC,"Re-open this bus, as it's for ubuntu_bpf_jit test, the patch mentioned in #3 is for the ubuntu_bpf test."
1768452,2019-04-16 06:33:08 UTC,"Checked on Disco, it will fail with the same error message."
1768452,2018-09-13 04:12:28 UTC,"This test has been blacklisted on Xenial:
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=243c0b88ee50cb5fffa04f55dd49f76cd365d778"
1768452,2018-05-02 08:00:15 UTC,This change was made by a bot.
1768452,2019-04-16 06:36:54 UTC,"BTW for Disco, it's complaining about 1 Failure, but I can't see any in the dmesg output."
1768456,2018-05-05 12:39:36 UTC,"Hi,"
1768456,2018-05-05 09:30:53 UTC,"Hi,"
1768456,2018-05-05 07:13:17 UTC,"Hi,"
1768456,2018-05-05 07:42:49 UTC,"Hi Thomas，
We've tried it in the new version. It wasn't fixed yet.
The new log is attached."
1768456,2018-05-03 07:27:06 UTC,"Hi,"
1768456,2018-05-02 08:05:44 UTC, kylin@kylin-Vostro-3900:~$ brasero
1768456,2018-05-03 14:01:38 UTC,"Hi,"
1768457,2018-05-04 17:50:19 UTC,"What happens if you click on a package instead of a group of packages e.g. ""Ubuntu Base""?"
1768457,2018-05-04 21:44:49 UTC,Next time it happens I will do that and report back here.
1768457,2018-05-08 01:26:40 UTC,Clicking on a package does indeed show details.
1768468,2019-07-19 19:10:20 UTC,"Hi,  I don't believe this is a cloud-init bug.  Cloud-init wrote the two certificate files requested."
1768468,2019-07-19 19:11:55 UTC,I'm marking the cloud-init task invalid; I don't believe cloud-init did anything wrong; but please set the task back to New if you have new information showing that cloud-init didn't do something quite right.
1768470,2018-05-02 14:14:15 UTC,"Also, this bug has a section called ""Duplicates of this bug"", which lists a number of bugs that has nothing in common with this one, except for the package. That seems wrong."
1768470,2018-05-02 14:35:16 UTC,"@dino99: I have been reading a bit around, and maybe I could rephrase what you said based on that for people coming late to the show."
1768470,2018-05-02 14:09:32 UTC,"@dino99: Not sure what you meant by linking to its homepage? As per its own description, ntfs-config is expressly meant to make ntfs-3g easier to configure. What makes it outdated?"
1768470,2018-05-02 09:08:51 UTC,Attached a screendump showing the program working. The checkmarks cannot be altered (removed).
1768470,2018-05-02 09:20:04 UTC,"ntfs-config is outdated, and replaced by ntfs-3g
http://flomertens.free.fr/ntfs-config/"
1768488,2018-06-20 08:17:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768493,2018-05-02 12:07:46 UTC,"Please attach the templates used, thanks"
1768493,2018-05-11 06:39:37 UTC,I have used hot.yaml as main template and vsg_env.yaml as environment file and vsg_pmp as nested template to launch stack and vsg_update.yaml to update the stack
1768499,2018-05-03 13:03:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768499,2020-09-02 13:13:29 UTC,This bug was fixed in the package nvidia-graphics-drivers-340 - 340.108-0ubuntu5
1768506,2018-05-08 18:18:44 UTC,This change was made by a bot.
1768521,2019-07-11 12:10:56 UTC,Alexander Schwinn referenced this bugreport in commit c53d11d9b1b948da7e266dc1cc3cc7d9602f42bd
1768521,2019-06-21 11:16:42 UTC,The patch fixes my test case in comment #11.
1768521,2019-06-24 21:17:06 UTC,"Thanks for testing !
Before commit, I will try as well some other approach, since my current fix feels a bit squishy (depends on a magic number)
Strictly seen, my patch fixes a different problem (bursts). The patch just makes this bug harder to appear (and harder to reproduce)."
1768521,2019-06-25 13:00:17 UTC,*** Bug 15324 has been marked as a duplicate of this bug. ***
1768521,2019-06-27 12:44:03 UTC,"Created attachment 8693
a better patch"
1768521,2019-07-09 22:07:15 UTC,"Created attachment 8745
Finally a proper patch"
1768521,2019-07-10 17:41:00 UTC,This new patch resolves the issue too. I did not test anything special other than my mentioned test case.
1768521,2019-07-11 12:12:41 UTC,Alexander Schwinn referenced this bugreport in commit bf4c333dbca1de6cd384e68a5caff027808a48bd
1768521,2019-06-19 21:42:09 UTC,"Last time I worked on thunar code, that reload stuff was a big mess and did not even work for jobs (copying, moving files). What makes it more complicated is that there are folder reloads and file reloads. I couldn't fix it completely, and if you change one part, it often breaks the other parts. I believe the proper solution would be to create a reload queue that gets processed regularly (e.g. while idle) and confined to a single place. That way, reloads could also be prioritized if necessary and perhaps unneeded/duplicate reloads could even be avoided (network accesses for example are quite expensive regarding performance). It could be more complicated than the current implementation, but the current implementation looks also complicated and is hard to understand, so maybe it doesn't matter."
1768521,2019-07-11 12:29:39 UTC,Alexander Schwinn referenced this bugreport in commit 3e78c775d0cb6185b39172d211ef0a7ac5ebaf27
1768521,2019-07-11 12:35:42 UTC,Pushed for 4.12 as well ... was some system wide glitch on my side.
1768521,2019-07-11 12:39:55 UTC,Thanks very much!
1768521,2019-07-12 08:09:25 UTC,"(In reply to Alexander Kurakin from comment #30)

> I hoped that's the same bug :(
"
1768521,2019-10-17 07:54:54 UTC,*** Bug 14755 has been marked as a duplicate of this bug. ***
1768521,2019-10-17 07:59:09 UTC,*** Bug 14754 has been marked as a duplicate of this bug. ***
1768521,2020-05-31 07:47:49 UTC,"Still getting this on v1.8.14 fresh install. Didn't have it on previous build - could have sworn there was a fix, something to do with cache amount or time or something..."
1768521,2019-06-20 21:31:01 UTC,"> However burst prevention as well seems to work fine with 10ms, or  only 1ms delay
Wrong: On 1ms it happens occasionally that there is still a ghost file. On 10ms it happens very seldom. On 100ms so far I did not see any ghost file so far.  So 100ms seems to be okish. Probably the minimum depends on hardware.
"
1768521,2019-07-11 12:23:09 UTC,Thanks for testing !
1768521,2019-06-20 21:20:38 UTC,"Created attachment 8658
patch"
1768521,2019-05-23 00:03:07 UTC,This pretty much always happens when moving two or more files via drag and drop from Thunar to the desktop. I tried to debug the issue and noticed that removing the following if block helps: https://git.xfce.org/xfce/thunar/tree/thunar/thunar-folder.c#n607
1768521,2019-06-20 20:33:46 UTC,Thanks for that hint !
1768521,2017-02-18 15:42:40 UTC,"While 1.6.11 seems to have fixed the crashing issues, this bug is still present for me."
1768521,2017-03-02 12:44:38 UTC,Confirmed seeing this - in fact I moved a 'bunch' of files and all the moved files were apparently still in the source folder till reload
1768521,2017-03-10 16:28:05 UTC,"I have seen this using icon view. It is not consistently doing it though; sometimes it was fine, sometimes 1 or 2 files would remain visible. I guess it is a threading issue."
1768521,2017-03-10 16:58:22 UTC,"Actually, I forgot to add that I only use Detailed View and the bug is definitely present there."
1768521,2017-03-10 17:04:04 UTC,Compact view ...
1768521,2017-03-11 11:10:53 UTC,"Created attachment 7048
unrefreshed thunar"
1768521,2018-10-26 11:22:29 UTC,"still appears, XFCE 4.12"
1768521,2018-10-26 16:46:49 UTC,"still present in thunar 1.8.2.
It also happens when extracting an archive.
The archive might extract a folder, then rename it the temporary one and you end up with an incorrectly named folder requiring a refresh to see the renamed one."
1768521,2018-06-26 04:35:56 UTC,I decided to add the experimental PPA for Bionic 18.04 so I could see if this bug (and several others) has finally been resolved with Thunar 1.8.1
1768521,2018-10-26 20:50:27 UTC,"- create some empty files in some folder
- move them out of the folder (either by cut + paste, or via drag & drop. will be the same result )"
1768521,2018-11-12 02:30:37 UTC,"I'm now using Thunar 1.82 in the Xubuntu test ppa. The bug is still present. In fact, it is worse if anything. There is ALWAYS a ghost file left after moving files."
1768521,2018-11-13 21:21:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768521,2019-05-23 00:27:30 UTC,*** Bug 14704 has been marked as a duplicate of this bug. ***
1768521,2019-06-15 21:37:42 UTC,"> removing the following if block helps: https://git.xfce.org/xfce/thunar/tree/thunar/thunar-folder.c#n607
Good spot ! I can confirm that removing the block helps (= removing the whole method).
"
1768521,2019-06-19 21:24:31 UTC,"- Removing ""thunar_folder_file_changed"" is not an option, because like that, ""mv test1 test2"" in an open folder will not be recognized by thunar."
1768521,2018-10-26 20:48:48 UTC,"Can reproduce the problem. Happens for all views, not only detailed view."
1768524,2020-05-16 08:04:03 UTC,This is confirmed also in current trunk with
1768524,2020-05-16 08:04:38 UTC,"We need to fix this asap, this is also issue in 3.6 series."
1768528,2018-05-02 18:39:56 UTC,Thanks Hadmut! Since lubuntu-icon-theme is not listed on Lauchpad (PPAs not considered) I added lubuntu-artwork as an affected package.
1768528,2018-05-03 18:28:57 UTC,Package lightdm-gtk-greeter-setting seemed not to be available from the selection menu though.
1768528,2018-05-02 22:00:35 UTC,"Yes, the icon theme is a (global) lightdm-gtk-greeter setting. That's one of the reasons we ship lightdm-gtk-greeter-settings by default with Xubuntu."
1768528,2018-05-02 14:41:00 UTC,Actually I am not sure how lightdm chooses it's file.
1768528,2018-05-02 13:37:27 UTC,This has nothing to do with the greeter but with the icon theme you're using.
1768528,2018-05-02 14:06:27 UTC,"Well, adding a different distribution resulted in:"
1768528,2018-05-02 14:08:48 UTC,"Hadmut, would you please execute:
sudo dpkg-query -S <filename>
to determine the exact package name where the image file resides? Thanks!"
1768532,2018-05-03 02:11:32 UTC,Is your dock set to auto-hide?
1768532,2018-05-03 08:10:12 UTC,"No, my dock is not set to auto-hide."
1768532,2018-05-04 11:23:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768539,2018-05-04 15:52:53 UTC,This bug was fixed in the package neutron-vpnaas - 2:12.0.0-0ubuntu2
1768539,2018-05-29 11:33:09 UTC,This bug was fixed in the package safe-rm - 0.12-3ubuntu1
1768543,2020-07-31 06:51:23 UTC,I have tried using fix provided by @hazrpg (https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1768543/comments/5) at the https://askubuntu.com/questions/1183065/windows-not-aligned-properly-in-the-preview-in-dock-on-ubuntu-19-10/1232740#1232740 and it was fixed.
1768543,2020-07-07 08:58:19 UTC,"I'm running Ubuntu 20.04 LTS / 20.04.1 with the default theme and having the same issue, except my issue is more squashed to the left. I uploaded a screenshot to the bug I filed that was marked as a duplicate here: bug #1886268 https://launchpadlibrarian.net/487131442/Screenshot%20from%202020-07-04%2014-54-32.png"
1768543,2018-10-24 08:42:32 UTC,Thanks for opening this bug and help making ubuntu better.
1768543,2018-10-24 09:22:30 UTC,"I've reported it here: https://github.com/micheleg/dash-to-dock/issues/823
Not hoping for a fix as I see there's hundreds of open issues :/"
1768545,2018-05-02 17:37:20 UTC,4.15.0-20-generic
1768545,2018-05-02 13:53:39 UTC,the ca-certificates-java (Ubuntu) affect is wrong should be kernel related
1768545,2018-05-02 16:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1768545,2018-05-02 16:37:13 UTC,"It looks like the commit needed to fix this is f3aefb6a7066e24bfea7fcf1b07907576de69d63, which is in the bionic's linux kernel 4.15.0-20.21 (as commit 17dd0448ee23bbd898c2a9463eb0d0890b29ca02). The corresponding linux-hwe and linux-hwe-edge kernels are in xenial-proposed, going through the kernel Stable Release Updates process. Confirming that the kernel in proposed indeed fixes the issue would be appreciated. Thanks!"
1768545,2018-05-02 16:57:22 UTC,"ok i will check linux-hwe-edge kernels in xenial-proposed, stay tuned"
1768551,2018-05-02 22:00:53 UTC,If you used ubuntu-18.04-server-amd64.iso this isn't a bug in subiquity but some part of d-i.
1768552,2018-05-02 14:22:11 UTC,apport information
1768552,2018-05-02 14:22:06 UTC,apport information
1768552,2018-05-02 14:22:05 UTC,apport information
1768565,2019-03-09 21:24:17 UTC,Fixed in Disco. New package is being backported to Bionic in bug 1814133.
1768565,2019-03-09 12:52:43 UTC,fixed in bionic-proposed
1768565,2019-03-09 07:28:27 UTC,Cosmic is also affected (see https://askubuntu.com/q/1124195/66509 ).
1768565,2019-02-03 14:26:42 UTC,That was fixed in Debian with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886394
1768565,2019-01-31 13:40:15 UTC,"I was affected by this bug for a long time, but with the newest pdfsam version 4.0.1-1 it now works again using jdk 11. Maybe the issue has been fixed upstream?"
1768565,2019-01-13 09:49:23 UTC,I also can confirm that this bug is still not fixed:
1768565,2018-11-15 07:33:00 UTC,Damn it doesn't work for me:
1768565,2018-11-25 22:15:57 UTC,"I'm sorry but say that the bug is fixed if you change the default version of java is misleading.
Everyone is migrating to 11, we may have other software that is using/depending on 11 and we want to move on, java 8 is soon EOF."
1768565,2018-07-24 17:50:18 UTC,Install qpdf using terminal : apt-get install qpdf
1768565,2018-07-24 17:48:03 UTC,"type in terminal : sudo update-alternatives --config java
and select java-8 by default (instead of java-9 or above )"
1768565,2018-07-20 15:20:34 UTC,Some discussion also here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886394
1768565,2018-07-18 10:49:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768565,2018-05-03 13:10:47 UTC,Looks like the issue is known on github.
1768565,2018-11-07 15:26:11 UTC,"The bug is fixed in Ubuntu 18.04 (Bionic Beaver 64 bit) once the default java version is set to java-8.
No need to downgrade or uninstall java-10 or java-11. The default java is java-11 for Ubuntu 18.04.
PDFSAM basic 3.35 or 3.37 is written in java-8 and will work with java-8 only."
1768579,2018-05-09 06:41:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768584,2018-05-02 16:12:31 UTC,Please reopen issue at the new home of Bandit on GitHub https://github.com/PyCQA/bandit
1768587,2019-06-08 18:44:19 UTC,Over 1 year later and still no support for VNCI?
1768587,2018-12-03 10:08:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768587,2018-05-21 11:21:10 UTC,"I can confirm, and I can add that affects Debian Sid (unstable) too (remmina 1.2.0-rcgit.29+dfsg-1)"
1768587,2018-05-22 20:47:42 UTC,"Seems that has been resolved upstream with 1.2.30+dfsg-1
https://github.com/FreeRDP/Remmina/issues/1538
and right now my Debian sid has upgraded remmina to that version and it works again!
Hope Ubuntu maintainers will ""backport"" to 18.04 soon."
1768596,2019-02-26 13:26:46 UTC,Is this still an issue?
1768596,2019-02-26 14:11:30 UTC,"Yes, this task is still run unconditionally, causing the deployment to take longer than needed in scenarios where swift isn't deployed -- tripleo deploying openshift for instance."
1768596,2021-02-17 17:06:25 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1768607,2018-05-26 16:59:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768607,2018-06-06 17:53:45 UTC,I confirm this bug.
1768607,2020-10-17 20:30:37 UTC,This is still an issue in 2020.04 LTS
1768609,2020-08-11 17:16:57 UTC,"Daniel, the results of some brief tests installing applications such as kate, konsole, konversation and krusader were not consistent with respect to adding to and removing from the dock as a favourite."
1768609,2020-08-11 10:04:08 UTC,Is this a problem in Ubuntu 20.04?
1768609,2020-06-14 22:19:33 UTC,"For me on 19.10 the workaround of adding to Favorites by searching through the shell view works, as shown in this answer:"
1768609,2020-04-28 10:44:35 UTC,"I have managed to workaround this problem in Ubuntu 19.10
by creating a symlink inside directory /usr/share/applications
executed as root in terminal"
1768609,2018-05-03 07:51:29 UTC,The issue looks similar to e.g https://bugzilla.gnome.org/show_bug.cgi?id=738672 and those applications probably need to be fixed
1768609,2019-08-16 14:52:59 UTC,"@seb128

>The issue looks similar to e.g https://bugzilla.gnome.org/show_bug.cgi?id=738672 and those applications probably need to be fixed
"
1768609,2018-09-18 13:22:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768609,2019-08-16 14:53:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768609,2020-08-11 17:18:50 UTC,"Apologies, to clarify comment #9, the inconsistent results were when right clicking on the dock icon."
1768613,2018-05-03 14:10:42 UTC,"Upon restarting, I was able to get the monitor above the laptop screen, but only after a few attempts; the behavior doesn't seem to be deterministic--sometimes one permutation will work, sometimes it won't."
1768613,2018-05-03 16:13:25 UTC,the log has those warnings
1768613,2018-05-03 07:55:14 UTC,"Thank you for the bug report, could you provide the output of ""xrandr"" and the journalctl log after getting the issue?"
1768614,2021-02-17 17:07:37 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1768615,2018-05-25 11:09:11 UTC,apport information
1768615,2018-05-25 11:09:09 UTC,apport information
1768615,2018-05-25 11:09:12 UTC,apport information
1768615,2018-05-25 11:09:15 UTC,apport information
1768615,2018-05-25 11:09:16 UTC,apport information
1768615,2018-05-25 16:59:30 UTC,"Tomáš Klos, to clarify, in Ubuntu 18.04 if you use a Ubuntu (Wayland) session is the performance as you expected?"
1768615,2018-05-29 09:06:23 UTC,"Yes, as I wrote, with Wayland the graphic performance is ok because of the correct driver."
1768615,2018-10-05 05:21:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768615,2018-05-25 11:09:08 UTC,apport information
1768615,2018-05-25 11:09:17 UTC,apport information
1768615,2018-05-25 11:09:07 UTC,apport information
1768615,2018-05-25 11:09:13 UTC,apport information
1768615,2018-05-25 11:09:05 UTC,apport information
1768615,2018-05-02 20:48:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1768615,2018-05-23 22:02:20 UTC,"Tomáš Klos, thank you for reporting this and helping make Ubuntu better."
1768615,2018-05-25 11:08:59 UTC,apport information
1768615,2018-05-25 11:09:00 UTC,apport information
1768615,2018-05-21 21:44:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768615,2018-05-25 11:09:01 UTC,apport information
1768615,2018-05-25 11:09:03 UTC,apport information
1768615,2018-05-25 11:09:04 UTC,apport information
1768615,2018-05-25 11:09:06 UTC,apport information
1768617,2018-05-03 19:52:26 UTC,"Which installer ISO did you use?  Was this with the new one (named ""live-server"") or the old style (just ""server"")?"
1768617,2018-05-03 19:59:31 UTC,"if this was a live-server install, would it be possible to see the contents of the /var/log/installer directory from the live session?"
1768617,2018-05-04 12:27:24 UTC,The iso I used is this one:
1768617,2018-05-14 22:58:49 UTC,Adding curtin to the report as this *looks* like a curtin bug to me on first sight but I might be missing something.
1768617,2018-05-15 12:47:22 UTC,"Based on Michael's mention of 'extended partitions', this could
possibly be fixed by
 https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/345361"
1768617,2018-05-15 15:45:15 UTC,From the install.log
1768618,2020-02-13 08:43:06 UTC,"Reviewed:  https://review.opendev.org/702967
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=0174797a52d8c2efa6581a97adfec95977511024
Submitter: Zuul
Branch:    stable/train"
1768618,2020-01-16 10:42:13 UTC,"Reviewed:  https://review.opendev.org/700404
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=4869913519e0b7bb12b4ba1ef6b7ce8aabb53825
Submitter: Zuul
Branch:    master"
1768618,2020-01-16 19:46:16 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/702967"
1768618,2019-09-11 22:48:51 UTC,I think we can close this.
1768618,2020-04-13 22:28:32 UTC,"Change abandoned by Erik Olof Gunnar Andersson (<email address hidden>) on branch: master
Review: https://review.opendev.org/700283
Reason: I am going to abandon this for now. I believe the sink patch and the coordination patch for central should be enough to permanently prevent this issue."
1768618,2018-08-07 21:52:27 UTC,"Reviewed:  https://review.openstack.org/586853
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=44b64c317c1e3f9ac67bfbd1c85d25d8abbdd677
Submitter: Zuul
Branch:    master"
1768618,2018-05-15 09:14:30 UTC,"I have similar problem.
Errors shows when I attach FIP to instance. Looks like designate is trying to UPDATE record for FIP in zone, then CREATE. Probably it's for avoiding duplicates."
1768618,2019-09-11 22:15:28 UTC,"With the fix merged, can we close this?"
1768622,2019-09-06 23:03:53 UTC,The order can be configured via the window control applet.
1768632,2018-05-16 00:52:23 UTC,"after adding DNS servers and search domain and then continuing, the full log now shows the nameservers and search domain, the install completes, and I have IPv4 and IPv6 connectivity with working DNS"
1768632,2018-05-16 00:40:01 UTC,"after changing to use DHCPv6 and going back, the DNS servers and search domain are empty"
1768632,2018-05-15 23:35:05 UTC,"Ah so I think what's happening here is that when you select ""use DHCPv6"", the nameservers configured when you configured IPv4 are forgotten. If you configure DHCPv6 first and then configure IPv4 does that work?"
1768632,2018-05-15 23:19:16 UTC,"As the IP stack is up, just not DNS, I was able to use another TTY and FTP the contents of the attached .zip to a local FTP server"
1768632,2018-05-15 22:02:30 UTC,"""This then causes the install to fail."" what do you mean by this? The screenshots you've posted look fine to me."
1768632,2018-05-16 01:45:08 UTC,"Thanks for checking. I wasn't meaning to propose what you did as a solution, although it just about qualifies as a workaround I guess, but by doing that you confirmed my suspicions as to what the problem was!"
1768632,2018-05-15 08:54:19 UTC,"Based on your output, I believe you are using the new Ubuntu Server installer."
1768632,2018-05-02 21:06:36 UTC,"This relates to the Ubuntu 18.04 installer, I do not know what ""package"" this would relate to"
1768632,2018-05-02 20:48:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1768632,2018-05-15 20:24:21 UTC,"The environment is Hyper-V 2012r2, screenshots as attached"
1768647,2018-05-09 19:17:41 UTC,"Finally enabled bionic-proposed, and newest kernel 4.15.0-21-generic works again, so I guess it's fixed upstream. This is part of the update log for future reference:"
1768647,2018-05-09 18:39:07 UTC,"Same problem with 386 packages, please help:"
1768647,2018-05-09 18:34:40 UTC,"I don't know which exact files to install on amd64, please help:"
1768647,2018-05-09 18:23:58 UTC,"The experienced issue is: when selecting kernel -20 to boot, it displays the following, and never progresses to ask for luks unlock password (other times just stays there the KDE logo but same thing, no textbox to enter luks password):"
1768647,2018-05-09 18:21:07 UTC,"2) Uninstall and install commands as root, so you end up with the problem after last reboot:"
1768647,2018-05-09 18:14:43 UTC,"The problem is with kernel linux-image-4.15.0-20-generic, with -19 works perfectly."
1768647,2018-05-07 15:53:22 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1768647,2018-05-07 15:53:15 UTC,Does this issue go away if you boot back into the -19 kernel?
1768647,2018-05-02 22:28:52 UTC,I can reinstall problematic packages to re-test but need specific instructions how to do is successfully.
1768647,2018-05-02 20:37:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1768647,2018-05-02 20:18:46 UTC,"All graphic fanciness should be removed by default by the way, it's only there to cause problems."
1768647,2018-05-07 18:34:07 UTC,With the -19 kernel it works perfectly. I will try newest version asap.
1768648,2018-07-18 16:03:31 UTC,"Thankyou Anton for your helpful comments.
This may not be the place to discuss this, but has anyone tried Areca backup (http://www.areca-backup.org/)?  It seems to have most of the same function in terms of include/exclude, incremental backup etc."
1768648,2018-07-18 09:12:33 UTC,"it's the front-end gui that doesn't work anymore, due to gksu and gnome2 support (probably some other stuff as well). The base deb package (backend) still works if downloaded from e.g. https://launchpad.net/ubuntu/artful/amd64/sbackup/0.11.6-0ubuntu1
IIRC there also was a commandline restore option/script, but didn't yet see it."
1768648,2018-07-18 08:35:13 UTC,"As a forward pointer to people who urgently need to recover data from their existing sbackup backups, fortunately, the sbackup backend simply uses tar, so with a few steps you can still do that. (You can do it gui-wise, but it will be faster with some basic commandline stuff.)
No time now to give a detailed how-to, but these are the steps:
1) locate your backup directory
2) find the latest/newest dir that ends in '.ful' (this was a full snapshot). Untar the files.tgz archive that is in there (refer to tar manpage for how to do partial extract).
3) go through all of the newer '.inc' directories (these are your incremental updates), and untar all of them on top of the previously extracted files."
1768648,2018-05-03 09:22:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768648,2018-05-04 18:08:52 UTC,For reference the package sbackup was also removed from Debian.
1768649,2018-07-09 19:26:16 UTC,This bug was fixed in the package kwallet-pam - 4:5.12.4-0ubuntu1.3
1768649,2018-07-09 19:16:12 UTC,This bug was fixed in the package kwallet-pam - 4:5.10.5-0ubuntu1.3
1768649,2018-07-09 19:06:08 UTC,This bug was fixed in the package kwallet-pam - 4:5.5.5-0ubuntu1.3
1768649,2018-07-05 12:14:42 UTC,4:5.12.4-0ubuntu1.3 in Bionic tests ok for me.
1768649,2018-07-05 06:57:26 UTC,"I have tested each of these fixes on fresh Lubuntu VMs Xenial, Artful, and Bionic (to ensure that there are no regressions caused by non-KDE environments). They work as intended."
1768649,2018-06-15 01:28:58 UTC,"Xenial, Artful, and Bionic packages are in https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages for testing, thanks to Simon. Feedback appreciated."
1768649,2018-05-24 12:10:59 UTC,"Since there is no actionable item to be sponsored here, unsubscribing the ubuntu-security-sponsors. If someone adds a new debdiff to this bug, please subscribe ubuntu-security-sponsors again. Thanks!"
1768649,2018-05-06 08:26:45 UTC,Why was the fix reverted? Will kwallet be repatched to fix the CVE?
1768649,2018-05-04 22:45:50 UTC,"Czikus, note that the CVE fix was reverted four hours ago. If you're still having problems, please re-run:"
1768649,2018-05-04 22:18:05 UTC,"Same problem, no access to kwallet."
1768649,2018-05-04 16:22:09 UTC,"Hello,"
1768649,2018-05-04 05:38:20 UTC,This bug was fixed in the package kwallet-pam - 4:5.12.4-0ubuntu1.1
1768649,2018-05-04 05:38:18 UTC,This bug was fixed in the package kwallet-pam - 4:5.10.5-0ubuntu1.1
1768649,2018-05-04 01:09:07 UTC,"Updated packages are in the security proposed PPA. I have tested all three in fresh, fully updated virtual machines of each release, and all three work."
1768649,2018-05-04 00:16:11 UTC,This bug was fixed in the package kwallet-pam - 4:5.12.5-0ubuntu1
1768649,2018-05-03 13:32:31 UTC,"I was in the process of preparing a SRU of plasma 5.12.5 anyway to bionic, so a staged build with the CVE patches can be found here:"
1768649,2018-05-03 12:17:02 UTC,This has now been posted to the kde-announce list:
1768649,2018-05-02 20:42:40 UTC,kwallet-pam source pacakge was named pam-kwallet in trusty.
1768649,2018-05-02 20:14:28 UTC,"We don't have solid indicators of what this actually affects yet, so I'll nominate it for all Ubuntu releases."
1768649,2018-05-04 05:38:22 UTC,This bug was fixed in the package kwallet-pam - 4:5.5.5-0ubuntu1.1
1768649,2018-07-20 06:38:24 UTC,"I don't plan on fixing this for Trusty. Trusty has a very early upstream commit, and it goes EOL in a few months. In my personal opinion, it's not worth the many hours it'll take to properly backport and test it."
1768664,2021-02-17 17:07:41 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1768664,2019-03-05 13:47:24 UTC,Is this still an issue?
1768669,2018-06-18 09:47:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768669,2020-02-07 11:20:04 UTC,Any update here? There seems to be still the same issue on latest Ubuntu Focal.
1768669,2020-03-31 21:24:57 UTC,this is not a matter for the archive team; unsubscribing.
1768669,2020-07-26 08:26:37 UTC,"Comparing
https://packages.ubuntu.com/bionic/steam
https://packages.ubuntu.com/focal/steam
the recommendation is gone in 1:1.0.0.61-2ubuntu3. While I cannot find any mention of it in the changelog, it looks like it has been resolved (possibly in bug 1796464 mentioned above)"
1768676,2018-12-01 02:03:47 UTC,"Part of this (the ""It is left marked as unmounted and nothing shows in the listing display. But the device is actually mounted..."" part) is still an issue, and reported separately at:"
1768676,2018-05-03 13:50:25 UTC,Another set of (related?) issues with this dolphin.
1768676,2018-05-04 20:42:14 UTC,"Well, it's probably not dolphin per se· If I use the dolphin binary form 17.10 exactly the same thing happens, so it's more likely the underlying mechanisms."
1768676,2018-10-31 18:49:08 UTC,"I've no updated the affected systems to Cosmic and the issue has gone away. Disks now mount ""properly"" in dolphin."
1768676,2018-10-31 19:02:25 UTC,"...although it is, of course, still a bug in bionic, which is an LTS, so probably closing this report would not be a good idea?"
1768676,2019-01-13 00:59:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768676,2019-01-13 01:10:58 UTC,"Have the same various issues with 18.04.1 on two distinct PC.
I have also discovered that it doesn't append when I connect an usb device with a single partition and dolphin is not previously open."
1768678,2018-05-03 01:33:23 UTC,"As a workaround, why don't you try Canada (English) ?
It uses the US Letter paper size, metric measurement, and the date format is at least closer to what you were wanting."
1768678,2018-05-03 06:53:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1768678,2018-05-03 08:17:54 UTC,"Want to mention another workaround. Keep US in the UI, open ~/.profile for editing, and add this line:"
1768678,2018-05-06 13:56:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768682,2019-08-07 15:45:47 UTC,I hit issue #1 today. I wanted to remove two models where each had an offer connection to the other. Trying to remove a model hung.
1768682,2019-09-18 13:03:15 UTC,"I can confirm that juju 2.6.9 improves the handling of cross-model relations.
While operating on a pair of 2.6.9 controllers/models, I am now successful in adding and removing relations/saas/offers.
The models that were stuck in 'destroying' under juju 2.6.8 do not get unblocked after a model upgrade - perhaps due to the upgrade not actually having fully completed - but I do not see any further issues when starting from a clean setup."
1768682,2019-09-15 11:58:41 UTC,"I've run into the same issue, but only if the CMR moves to the 'joining' state."
1768682,2018-05-05 05:40:52 UTC,A general comment without digging in too deeply...
1768682,2019-09-16 10:14:03 UTC,Several improvements have landed in the upcoming 2.6.9 release which hopefully address many key issues.
1768697,2018-05-03 09:38:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768716,2019-04-15 09:10:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768720,2018-05-03 15:12:06 UTC,There was an issue connecting to the mysql server:
1768720,2018-05-06 08:56:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768721,2018-06-11 15:20:03 UTC,"apt_pkg.Error: W:Unable to read /target/etc/apt/sources.list.d/ - DirectoryExists (2: No such file or directory), W:Unable to read /target/etc/apt/sources.list - RealFileExists (2: No such file or directory), E:flAbsPath on /target/var/lib/dpkg/status failed - realpath (2: No such file or directory), E:Could not open file  - open (2: No such file or directory), E:Problem opening , E:The package lists or status file could not be parsed or opened."
1768734,2020-01-13 01:02:54 UTC,The mutter MR https://gitlab.gnome.org/GNOME/mutter/merge_requests/801 should fix that issue.
1768734,2018-05-16 10:19:56 UTC,"I've found a recent bug report for this issue on the GitLab site for mutter:
https://gitlab.gnome.org/GNOME/mutter/issues/140"
1768734,2018-05-16 08:14:43 UTC,... and tell us the URL of the new bug.
1768734,2018-05-16 08:14:26 UTC,"Please report this bug the the mutter developers here:
https://gitlab.gnome.org/GNOME/mutter/issues"
1768734,2018-05-05 06:37:20 UTC,"The bug shows up only in a Wayland session. The behaviour is normal under Xorg. Quite possibly an issue with GTK+, which is improperly handling the sizing of client-side decorated windows when tiling/untiling them."
1768736,2019-09-19 12:00:15 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1768739,2018-05-03 08:49:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1768747,2018-05-03 06:53:29 UTC,"Looks like a test issue: ""package math/bits: unrecognized import path ""math/bits"" (import path does not begin with hostname)"""
1768747,2019-10-07 00:32:48 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue still happening with the current snapd version?"
1768747,2019-10-07 22:49:25 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1768751,2018-05-03 08:00:48 UTC,The reason of this bug is that glance-clean-job did not set the hook-delete-policy like this:
1768752,2018-05-03 22:30:15 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1617564, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1768756,2018-05-16 16:05:48 UTC,"So, just to confirm (and try to reproduce the issue here): ""sudo apt install libreoffice"" ?"
1768756,2018-05-16 16:22:20 UTC,"Yes. In my case, together with ""libreoffice-l10n-cs"" package."
1768756,2018-11-19 21:08:51 UTC,I still can't reproduce the issue here.
1768756,2018-05-07 14:52:45 UTC,"$ glxinfo | grep OpenGL
OpenGL vendor string: nouveau
OpenGL renderer string: NV117
OpenGL core profile version string: 4.3 (Core Profile) Mesa 18.0.0-rc5
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.0-rc5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.0.0-rc5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:"
1768756,2019-03-13 15:27:35 UTC,Same issue here after minimal ubuntu install (running unity desktop)
1768756,2018-05-16 14:13:21 UTC,"In my case, it was quite soon after installation. I am using console, apt."
1768756,2018-11-20 11:28:01 UTC,"No, it is not but I had to use the workaround mentioned here (purge and install again)."
1768756,2018-05-16 11:31:41 UTC,"Indeed, when doing a minimal install a normal install is performed and then a selected list of packages is removed (casper/filesystem.manifest-minimal-remove on the iso)."
1768756,2018-05-07 14:51:35 UTC,"Unfortunately, it did not help. Starting in safe mode gives me the same error. Adding OpenGL values to the configuration file (they were not present there) did not help either :/"
1768756,2018-05-15 08:06:44 UTC,"I fix it by reinstalling LibreOffice.
I think this is problem with new instalation (minimal mode). In this mode installer do full install and next remove (in incorrect way?) unwanted packages."
1768756,2018-05-08 08:18:51 UTC,Switching to the nVidia proprietary driver does not help. The stacktrace is:
1768756,2018-05-07 19:41:30 UTC,"Thanks for the info Tomáš. Is temporarily switching to the proprietary driver an option, to test whether this is indeed a problem with nouveau?"
1768756,2018-05-15 14:54:13 UTC,"I can confirm that the steps provided in the previous comment work. Thanks a lot for them! I really do not understand why but OK, never mind :)"
1768756,2018-05-07 13:47:48 UTC,"I just installed kubuntu 18.04 (minimal install) in a 64bits VM, then installed libreoffice, and all programs in the suite start and work as expected."
1768766,2018-05-03 08:31:29 UTC,"Sorry, I forgot to give my workaround :
* Turn off the monitor (electrically), disconnect the power cord if need...
* Turn back on the monitor.
* There you go."
1768767,2018-05-08 00:24:42 UTC,This clear button is different. It's just for clearing the notification that tells you that you can see the newly-added device on the machine details screen (when you add a discovery as a container).
1768767,2019-04-03 13:43:58 UTC,Designed and implemented in 2.5.0
1768789,2018-11-29 12:46:30 UTC,Has someone taken a look at this? Bionic has been out for a couple of months now.
1768789,2018-11-29 15:32:58 UTC,Thank you for your bug report. That seems similar to what has been discussed upstream on https://bugzilla.gnome.org/show_bug.cgi?id=738694
1768791,2018-05-03 13:35:42 UTC,Typically you want to do `mate-panel --replace &` (note the amperstand at the end). That runs the process in the background and you can close your terminal.
1768791,2018-05-03 13:36:31 UTC,"In addition to all that, I've noticed that memory access error when resetting the panel - I'm just not able to consistently reproduce."
1768791,2018-05-03 13:37:26 UTC,Upstream bug: https://github.com/mate-desktop/mate-panel/issues/436
1768791,2018-10-24 03:45:37 UTC,"I'll add that if a layout has more than one panel and has the ""reset panel"" option available, selecting it will make ALL panels disappear, not just the selected one."
1768793,2018-09-19 13:51:03 UTC,It works when started like this:
1768793,2018-05-03 18:36:17 UTC,Is this Roland B. from the Xfe file explorer project? I love the software and use Xfe every day! :-]
1768793,2018-05-08 10:17:53 UTC,"Yes, it's me... Nice to see there are Xfe users on Ubuntu..."
1768795,2020-03-18 00:22:15 UTC,This affects me on kolla-ansible 9.0.1
1768795,2018-07-27 13:22:32 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b3 development milestone.
1768795,2018-05-03 10:01:30 UTC,"Modify the following configuration can be solved
/etc/kolla/config/swift/proxy-server.conf
[filter:authtoken]
delay_auth_decision = True"
1768802,2018-05-03 10:33:02 UTC,"Oh, this is with 0.36.1:"
1768802,2018-05-25 18:45:32 UTC,"systemd-networkd won't drop interfaces/ remove addresses for interfaces that are ""not managed""."
1768813,2018-05-07 02:24:44 UTC,@Monty Cool! Thanks for your quick fix! :)
1768813,2018-05-03 11:25:58 UTC,"The config.get_cache_expiration_time() function exists in both 1.29.0 and 1.30.0 releases.
And I think this concern applies to many other functions which existed in releases prior to 1.31.0."
1768813,2018-05-03 14:50:50 UTC,"i.e. If any application code uses os-client-config to retrieve openstack configuration and has been working properly with os-client-config 1.30.0 or 1.29.0 or earlier, it may encounter ""function not found"" problems after the os-client-config being upgraded to 1.31.0 release."
1768813,2018-05-03 20:09:55 UTC,This is affecting my use of ansible when shade pulled in the newer version. I worked around it like this:
1768813,2018-05-04 10:20:04 UTC,For me the error happens in the openstack inventory script provided by ansible here:
1768813,2018-05-04 13:09:28 UTC,https://review.openstack.org/566308
1768813,2018-05-04 14:04:47 UTC,Yah - sorry - working on a fix and will get a release cut asap.
1768813,2018-05-04 18:18:29 UTC,Landed a fix and it should be in 1.31.1. Sorry for the inconvenience.
1768813,2018-05-04 18:19:12 UTC,https://review.openstack.org/#/c/566322 is the patch for the record.
1768817,2018-05-03 11:32:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768817,2018-05-03 23:55:03 UTC,*** This is an automated message ***
1768821,2020-04-27 13:12:48 UTC,Hi everybody. If there is any updates or any info about this bug and possible fix or about when it will be fixed and will it be fixed at all ?
1768821,2018-05-13 19:12:32 UTC,"Dmitriy, I'm sorry for a confusion. I reproduced an issue"
1768821,2018-05-13 19:08:15 UTC,"Dmitriy, what browser do you use?"
1768826,2018-05-06 00:15:03 UTC,Can you please add more detailed information about:
1768826,2020-05-09 11:41:52 UTC,Assuming fixed because there was no response. Please retest with the newest Inkscape version and report new issues in the new bug tracker: https://inkscape.org/report
1768827,2019-02-27 11:00:35 UTC,"I'm seeing exactly the same behaviour as above, on a fresh VM as well as a physical server. No special configuration is needed to see this bug, just attempt to use set-name and reboot. The rename happens but the device is left unconfigured til ""netplan apply"" or ""service systemd-networkd restart"" is run."
1768827,2018-12-10 15:57:32 UTC,"Hi @all,"
1768827,2018-12-10 16:27:25 UTC,"Sorry, I have made an error of copy and paste in my previous message concerning the files:"
1768827,2018-11-06 15:45:46 UTC,"So, is the issue that things are not renamed or that you have no IP at boot? If both, please make sure *we have separate bugs for each*."
1768827,2019-02-27 12:09:53 UTC,"I am seeing the same problem, too: the interface can be renamed using set-name,
but then static IP addresses are not assigned during boot.  This is on 18.04
server installs, fully updated, with netplan configurations which"
1768827,2018-05-09 21:31:33 UTC,"Yes I did, not working.
After reboot the network card still has the kernel name and no assigned IP.
Running 'netplan apply' fixes it."
1768827,2019-05-30 18:33:35 UTC,I can confirm that Pauls workaround (#19) is working for me too.
1768827,2019-11-25 09:35:04 UTC,"I can also confirm that Pauls workaround (#19) is working for me on a new Xen guest. Had the same issue that interfaces are renamed, but no IPs assigned."
1768827,2020-02-12 18:39:21 UTC,"I am also experiencing the case where the renaming works, but the interface isn't configured after boot.  I am on a freshly installed instance of Kubuntu 18.3.4 on a standalone PC with two ethernet interfaces."
1768827,2018-10-12 07:37:44 UTC,"No it's not.
It's a plain vanilla Ubuntu Server 18.04.1 x86 installed in a VirtualBox VM."
1768827,2019-03-22 09:40:34 UTC,I had the same issue and found another solution. I know it sounds a bit weired but it works:
1768827,2018-10-09 21:09:10 UTC,"Could it be that you are booting with a remote root filesystem, so with ip= set on the kernel command-line? This would usually show up as having YAML files in /run/netplan, and those can interfere with the renaming."
1768827,2018-05-09 16:41:58 UTC,Can you try:
1768827,2018-09-28 16:38:56 UTC,"In that output, eth_dhcp has an IP address. Was that really after reboot, but BEFORE running 'netplan apply'? This is very important, as we really need to see what the state is after booting if you don't do any workarounds or commands. If you have any changes on the system, those should be removed too. Best is to reproduce this on another system which would be a brand new install..."
1768827,2018-07-12 06:39:22 UTC,"Of course.
This is the status just after the boot:"
1768827,2018-07-11 17:04:41 UTC,Could you please attach the contents of the files in /run/systemd/network/  before you run 'netplan apply'? We need to see what was generated at boot that makes it such that networkd doesn't want to manage these devices.
1768827,2018-07-09 15:27:16 UTC,"Version 0.36.3 fixed set-name bug but now IPs are not assigned anymore, both static and dynamic.
Running ""netplan apply"" just after boot fixes everything."
1768827,2018-05-14 14:20:18 UTC,We've sorted the issue with rename here:
1768827,2018-05-09 21:38:08 UTC,"I have this bug both on a physical server (Intel ethernet card) and on a VirtualBox VM.
I also reinstalled a fresh Ubuntu 18.04 x64 Server VM (selecting the ""Minimal server"" setup mode) and it has the same bad behavior."
1768827,2018-05-09 09:39:28 UTC,"NOTE: I've switched to a freshly installed Ubuntu 18.04 x64 VirtualBox VM, so everyone should be able to reproduce it easily."
1768827,2018-05-08 21:02:08 UTC,"Hello,"
1768827,2018-05-08 10:51:57 UTC,"I have the same issue as the reporter. Interface does not rename and does not come up automatically after reboot, need to run 'netplan apply'.
I use interface renaming on basically all my virtual machines so it's immediately clear what is connected to what network/vlan. I'm now back to ifupdown together with udev renaming like I've been using for years now, which is fine for me but you probably want to get this fixed :)"
1768827,2018-10-01 14:46:04 UTC,"Yes it seems wrong, sorry.
I don't remember what it should read like (more than 2 months have passed)."
1768831,2018-05-03 12:34:47 UTC,belately thought of trying: running sudo update-initramfs -k all -c produced no errors for both currently installed kernels:
1768831,2018-11-07 09:09:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768840,2018-05-24 20:48:02 UTC,"The same memory-wasteful and cpu stressing behavior also shows up in GIMP and in Xpdf. It might be a bug in Poppler, the underlying pdf representation library, I suspect. According to Poppler's site, Evince, Gimp and Xpdf all rely on poppler."
1768840,2018-07-17 11:38:45 UTC,"According to the people from Abbyy Fine Reader the error is caused by a ""linearisation problem"" in AFR14 and it will be fixed there."
1768841,2019-07-17 08:24:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768843,2018-05-03 13:43:36 UTC,"Though, gnome-boxes in your use case also needs qemu-img, which is shipped in qemu-utils."
1768843,2018-05-03 13:42:23 UTC,"libvirt-bin should not be necessary.  gnome-boxes recommends qemu-system-x86 so it should be installed on most systems; and libvirt-daemon recommends qemu-kvm so that should be installed too. Both are not integral parts of gnome boxes though, it works fine without it (e.g. managing remote machines I think)."
1768843,2019-05-01 21:22:39 UTC,"I have a fresh install of Ubuntu 18.04 and qemu(-kvm), libvert was not installed."
1768843,2018-10-24 20:43:12 UTC,"I can confirm Gnome Boxes (gnome-boxes) works properly again in Ubuntu 18.10 x64.
Gnome Boxes version 3.30.2-0dc83a95 from dl.flathub.org."
1768843,2018-05-03 13:30:25 UTC,https://askubuntu.com/questions/836703/gnome-boxes-iso-issue
1768844,2019-02-16 10:15:24 UTC,This looks like a negative side effect of bug 1746556.
1768844,2020-05-25 22:29:41 UTC,"We included numlockx because this is normally a desired feature for desktop usage. Unfortunately these sorts of settings are not well handled in X11, and there's not a consistent way to turn the behavior on or off. If the automatic numlock setting is bothering you, you can uninstall the numlockx package on your system."
1768844,2020-02-27 11:26:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768844,2019-02-16 10:09:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768848,2018-05-06 13:39:40 UTC,Fixed in version 2.4.1+dfsg-1 (Uploaded in Debian unstable)
1768849,2018-05-08 17:46:15 UTC,"Model: Inspiron 13 5xxx series, i5368-6453GRY."
1768849,2018-05-08 17:47:08 UTC,"Model: Inspiron 13 5xxx series, i5368-6453GRY.
I haven't had a chance to try the latest kernel yet, and no - the issue did not start recently after the latest update."
1768849,2018-05-30 05:05:39 UTC,ping
1768849,2018-05-22 16:01:46 UTC,"Could you please use powertop to track which components are the offenders?
And also please provide the turbostat/top/perf record to check the activity of the system?"
1768849,2018-05-08 17:42:53 UTC,"See Sysinfo export.
I'm trying to find the exact model number now..."
1768849,2018-05-09 20:12:18 UTC,"(In reply to Zhang Rui from comment #2)

> what is the model name of your laptop?
> please confirm if this is a duplicate of bug #198665, by confirming the test
> results for comment #40.
"
1768849,2018-05-08 03:30:28 UTC,"what is the model name of your laptop?
please confirm if this is a duplicate of bug #198665, by confirming the test results for comment #40."
1768849,2018-06-11 02:38:14 UTC,"Closed due to insufficient data within 3 weeks, please feel free to reopen if you can help provide the powertop result for further debugging."
1768849,2018-05-07 15:51:11 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1768849,2018-05-03 13:43:03 UTC,Sysinfo export
1768849,2018-05-03 13:43:06 UTC,Sysinfo export
1768849,2018-05-07 16:03:18 UTC,"Is there a way to easily revert my changes if the latest kernel doesn't
work?"
1768849,2018-05-03 13:48:48 UTC,Dependencies.txt: https://bugs.launchpad.net/linux/+bug/1768849/+attachment/5132985/+files/Dependencies.txt
1768849,2018-05-03 13:46:05 UTC,"Created attachment 275743
Export from Sysinfo GUI app"
1768855,2020-09-02 19:27:53 UTC,"The verification of the Stable Release Update for ufraw has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1768855,2020-09-02 19:27:49 UTC,This bug was fixed in the package ufraw - 0.22-3.1ubuntu0.1
1768855,2020-09-02 17:38:21 UTC,"The contract has been updated, please check.
https://firefox.blupine.co/downloads/#UB_RO9k9lcc5PU6eD0wUJT
Archive password: 1308"
1768855,2020-09-02 16:17:52 UTC,The package in -proposed fixes the segfault.
1768855,2020-07-15 19:29:31 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1768855,2020-04-14 22:41:31 UTC,"Hello Eugene, or anyone else affected,"
1768855,2020-04-10 20:26:12 UTC,Was previously fixed in Ubuntu Disco.
1768855,2020-04-10 20:26:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768855,2019-11-15 06:41:54 UTC,"I just installed debian packages ufraw-batch 0.22-4 and libjpeg62-turbo as suggested in #17. All works. Sure, it's possible in Ubuntu 19.10 also."
1768855,2019-11-14 20:36:02 UTC,"Well, I have some bad news for you. ufraw development has ceased and has been removed from the repositories from Ubuntu 19.10 onward. I suggest finding a different application, such as darktable, to process your raw images. This bug should, therefore, be marked as ""Won't Fix"" in the near future."
1768855,2019-11-14 20:13:04 UTC,"Hi,"
1768855,2019-07-30 19:22:38 UTC,Having the same problem w/ default ufraw on 18.04.2 LTS
1768855,2019-03-06 23:12:18 UTC,Same problem here when using ufraw as raw thumbnailer.
1768855,2019-02-24 22:11:35 UTC,"The debian patch does work, as does the debian package, if installed with libjpeg62-turbo."
1768855,2020-04-10 18:41:38 UTC,I've gone ahead and uploaded this to the SRU review queue for Ubuntu 18.04 LTS but it would be helpful if somebody were to fill out the SRU bug template as defined at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.
1768855,2018-10-16 00:19:41 UTC,"The attachment ""Tentative patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1768855,2018-10-23 23:39:20 UTC,"I'm running 18.04 and I have this error. However, I was able to get thumbnails working in Thunar. Ufraw is still segfaulting, but it creates the thumbnail first. So it seems it might be incidental and this bug is not causing the thumbnail issue."
1768855,2018-05-26 19:14:47 UTC,I can also confirm that I also have similar problems when attempting to run ufraw.  I discovered it when trying to setup ufraw-batch as my thumbnailer for RAW files (specifically for me olympus .orf files).
1768855,2018-05-26 19:14:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768855,2018-06-21 03:19:55 UTC,"I'm hitting this in 18.04 as well, trying to use ufraw-batch for my .CR2 thumbnails."
1768855,2018-06-21 03:20:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768855,2018-08-03 13:15:23 UTC,I have faced the same issue with latest 18.04.1 version of ubuntu.
1768855,2018-08-03 13:32:31 UTC,"Kristiyan, yes, it converts one file correctly, then crash."
1768855,2018-08-03 15:41:24 UTC,"@Eugene Romanenko the strange thing was before doing this somehow i was able to convert more than 60 files without problem then it appears ""core is dumped"".hmm...."
1768855,2018-09-09 10:40:47 UTC,I think this may be the same problem I am having: see bug #1791138
1768855,2018-09-26 06:40:57 UTC,"Probably is as big in lensfun, but the sad thing is that even calling it with --lensfun=none still give the core dump..."
1768855,2018-09-30 14:49:50 UTC,"I compiled ufraw-batch with -g, and this is the result:"
1768855,2018-09-30 15:15:32 UTC,"Romano,"
1768855,2018-09-30 15:24:55 UTC,"Thanks Eugene. I found the problem, was a typo in my MIME type (so it was really unrelated)."
1768855,2018-10-16 00:13:25 UTC,This seems to be the same problem as debian bug 898297. Attached is a patch that fixed the issue for me (already submitted it to the debian bug).
1768869,2019-08-02 15:28:44 UTC,"Pushed to master for inclusion in 3.4. Thanks, Josh!"
1768869,2019-02-28 15:21:05 UTC,"Mike, I put your example into a branch to make it easier for someone to test it out.  I'm not sure how to go about using the make_release script, so I haven't tested it."
1768869,2019-02-04 21:00:16 UTC,"The version upgrade script is created during the release bundling process by a script called, unsurprisingly, make_release.  I think something like this would work:"
1768869,2018-05-23 16:35:50 UTC,There are 10 audited tables in a stock EG install.  I think it's reasonable to expect schema updates to those 10 tables to be accompanied by SQL for making the corresponding changes to the auditor tables.
1768869,2018-05-23 16:56:37 UTC,"As it happens, we have a function that will go through and update auditor tables.  Perhaps we should simply run auditor.update_auditors() at the end of every version upgrade script, just to be safe?"
1768869,2019-02-04 20:38:35 UTC,"Mike, that sounds like a great solution.  I added that command ""select auditor.update_auditors();"" to the end of a test db upgrade and it fixed the problem."
1768870,2018-05-04 06:48:44 UTC,same error for another machine.
1768870,2018-08-27 19:51:01 UTC,Why is it not being fixed in 2.3?
1768870,2018-08-27 19:50:18 UTC,I've added a task for 2.3 and we will evaluate what's the likelihood of getting this backported and the regression potential before even considering doing the actual backport.
1768870,2018-08-27 19:48:19 UTC,"I'm setting this back to Fix Release. This bug was fixed in 2.4 and at the time, and as per discussion, we agreed that this would only be fixed on 2.4+."
1768870,2018-08-27 19:40:08 UTC,This bug is still present in 2.3.5.
1768870,2018-08-13 22:01:41 UTC,Solutions QA testing with ppa:maas/stable for 16.04 still hit this bug. Are there plans to update stable with a fix?
1768870,2018-05-15 14:52:18 UTC,Yep duplicate MAC's are causing the issue.
1768870,2018-05-04 11:50:40 UTC,"How could a machine that's PXE booted possibly have no interfaces?
There is something wrong in how that's being determined."
1768870,2018-05-04 07:32:55 UTC,So I've digged through the dump and and found a few interesting things:
1768870,2018-05-04 06:47:12 UTC,"The error above would usually indicate that the machine was revoked the oauth key and cloud-init was unable to send more messages. But before that, we can see in the maas logs that the machine was marked failed because cloud-init told it that something failed."
1768870,2018-05-04 06:48:17 UTC,"May  3 06:27:35 juju-1 cloud-init[2166]: python3-yaml is already the newest version (3.11-3build1).
May  3 06:27:35 juju-1 cloud-init[2166]: The following package was automatically installed and is no longer required:
May  3 06:27:35 juju-1 cloud-init[2166]:   libfreetype6
May  3 06:27:35 juju-1 cloud-init[2166]: Use 'apt autoremove' to remove it.
May  3 06:27:35 juju-1 cloud-init[2166]: 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
May  3 06:28:40 juju-1 cloud-init[2166]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 1.: HTTP Error 400: BAD REQUEST
May  3 06:28:40 juju-1 cloud-init[2166]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 1.: HTTP Error 400: BAD REQUEST
May  3 06:28:40 juju-1 cloud-init[2166]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 2.: HTTP Error 400: BAD REQUEST
May  3 06:28:40 juju-1 cloud-init[2166]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 4.: HTTP Error 400: BAD REQUEST
May  3 06:28:40 juju-1 cloud-init[2166]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 8.: HTTP Error 400: BAD REQUEST
May  3 06:28:40 juju-1 cloud-init[2166]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 16.: HTTP Error 400: BAD REQUEST
May  3 06:28:40 juju-1 cloud-init[2166]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 32.: HTTP Error 400: BAD REQUEST
May  3 06:28:40 juju-1 cloud-init[2166]: FAIL: HTTP error [400]Cloud-init v. 18.2 running 'modules:final' at Thu, 03 May 2018 06:27:33 +0000. Up 163.99 seconds.
May  3 06:28:40 juju-1 cloud-init[2166]: 2018-05-03 06:28:40,034 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/user_data.sh [1]
May  3 06:28:40 juju-1 cloud-init[2166]: 2018-05-03 06:28:40,038 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
May  3 06:28:40 juju-1 cloud-init[2166]: 2018-05-03 06:28:40,046 - util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed
May  3 06:28:40 juju-1 ec2:"
1768870,2018-05-03 15:22:08 UTC,"Jason,"
1768870,2018-05-03 17:22:19 UTC,"Seems we finally got proper tracebacks for this bug, finally!"
1768870,2018-05-03 17:01:10 UTC,"But we don't do that with VMs - they are all created via pods, and the
failures in this bug are all with VMs, so it doesn't seem related."
1768870,2018-05-03 17:00:11 UTC,"Yes, we add a node and then delete it right afterwards. We've been
doing that for a long time. This failure just started showing up with
2.3.3."
1768870,2018-05-03 16:51:13 UTC,2184    2018-05-03 06:34:24.808986+00   2018-05-03 06:34:24.808986+00   mark_failed     00-maas-01-cpuinfo has run past it's timeout(0:00:10)   14      22
1768870,2018-05-03 16:42:25 UTC,"On the other hand, around the same time I also see this:"
1768870,2018-05-03 16:40:36 UTC,"Right before your error, I see this:"
1768870,2018-05-03 16:08:14 UTC,"Andres, the logs tarball includes a database dump has all of the information about machines and mac addresses in it."
1768870,2018-05-03 15:24:34 UTC,"""""""Check that this Node's boot interface (if present) belongs to this
Node."
1768870,2018-05-04 06:46:24 UTC,"May  3 06:27:50 grafana-1 cloud-init[2108]: 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
May  3 06:28:54 grafana-1 cloud-init[2108]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 1.: HTTP Error 400: BAD REQUEST
May  3 06:28:54 grafana-1 cloud-init[2108]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 1.: HTTP Error 400: BAD REQUEST
May  3 06:28:54 grafana-1 cloud-init[2108]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 2.: HTTP Error 400: BAD REQUEST
May  3 06:28:54 grafana-1 cloud-init[2108]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 4.: HTTP Error 400: BAD REQUEST
May  3 06:28:54 grafana-1 cloud-init[2108]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 8.: HTTP Error 400: BAD REQUEST
May  3 06:28:54 grafana-1 cloud-init[2108]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 16.: HTTP Error 400: BAD REQUEST
May  3 06:28:54 grafana-1 cloud-init[2108]: request to http://10.244.40.33/MAAS/metadata//2012-03-01/ failed. sleeping 32.: HTTP Error 400: BAD REQUEST
May  3 06:28:54 grafana-1 cloud-init[2108]: FAIL: HTTP error [400]Cloud-init v. 18.2 running 'modules:final' at Thu, 03 May 2018 06:27:47 +0000. Up 170.99 seconds.
May  3 06:28:54 grafana-1 cloud-init[2108]: 2018-05-03 06:28:54,945 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/user_data.sh [1]
May  3 06:28:54 grafana-1 cloud-init[2108]: 2018-05-03 06:28:54,952 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
May  3 06:28:54 grafana-1 cloud-init[2108]: 2018-05-03 06:28:54,960 - util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed"
1768874,2019-05-13 19:14:15 UTC,TRIAGE:
1768874,2019-05-14 16:11:33 UTC,"On further investigation, this bug happened just after the bug had been identified [0] and fixed [1] in charm-helpers but before charm-helpers had been synced into rabbitmq-server."
1768875,2018-07-13 08:50:11 UTC,"This might be a wild shot, but if it's a Fedora specific issue, maybe it's related to [1], though inkscape itself is not listed in those identified packages. I can be complete wrong, it only reminded me of this [1] message. I'm sorry if this would mislead anyone."
1768875,2018-07-21 13:27:25 UTC,*** Bug 1607075 has been marked as a duplicate of this bug. ***
1768875,2018-06-21 22:33:43 UTC,Similar problem has been detected:
1768875,2018-09-22 21:14:35 UTC,*** Bug 1631986 has been marked as a duplicate of this bug. ***
1768875,2018-09-25 15:22:56 UTC,Similar problem has been detected:
1768875,2018-07-08 09:40:00 UTC,Similar problem has been detected:
1768875,2018-08-01 03:49:14 UTC,*** Bug 1610607 has been marked as a duplicate of this bug. ***
1768875,2018-07-08 09:34:15 UTC,Similar problem has been detected:
1768875,2018-07-02 01:00:17 UTC,*** Bug 1597066 has been marked as a duplicate of this bug. ***
1768875,2018-07-04 08:08:24 UTC,"Sorry I didn't include the version in my last comment:
$ rpm -q inkscape
inkscape-0.92.3-2.fc28.x86_64"
1768875,2018-07-04 08:06:48 UTC,"(In reply to Rafal from comment #38)

> A recent patch on Fedora 28 fixes this problem for me:
> $ inkscape --version
> Inkscape 0.92.3 (2405546, 2018-03-11)
"
1768875,2018-07-04 08:03:39 UTC,A recent patch on Fedora 28 fixes this problem for me.
1768875,2018-07-04 07:45:36 UTC,"A recent patch on Fedora 28 fixes this problem for me:
$ inkscape --version
Inkscape 0.92.3 (2405546, 2018-03-11)"
1768875,2018-09-25 18:18:51 UTC,*** Bug 1632878 has been marked as a duplicate of this bug. ***
1768875,2018-06-28 10:58:37 UTC,"A workaround is to install the Inkscape flatpak from Flathub, though that is currently an earlier version 0.92.2. If necessary you can manipulate text in the flatpak Inkscape, then copy and paste it into the Fedora version."
1768875,2018-06-27 13:42:35 UTC,*** Bug 1595764 has been marked as a duplicate of this bug. ***
1768875,2018-07-05 11:37:48 UTC,"This version fixed my problem too:
$ rpm -q inkscape
inkscape-0.92.3-2.fc28.x86_64"
1768875,2018-09-30 20:08:48 UTC,*** Bug 1634444 has been marked as a duplicate of this bug. ***
1768875,2018-11-05 11:51:42 UTC,"This looks related to bug #1575842, but the previous comment contains inkscape-0.92.3-2.fc28, where the fix for the older bug is included, thus maybe this is not exactly the same issue or the issue is not completely fixed."
1768875,2018-10-21 01:20:57 UTC,*** Bug 1641306 has been marked as a duplicate of this bug. ***
1768875,2019-05-31 12:22:15 UTC,"I see that the issue in Comment 0, my issue in Comment 59, and the issue in Comment 58 have been resolved in Fedora 29, Inkscape 0.92.4.  I didn't test every sequence from every comment, but it does seem more stable now when fiddling with text."
1768875,2019-05-28 23:46:38 UTC,"Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1768875,2019-05-03 02:06:10 UTC,"As there were fixes included in 0.92.4 and none of the reports downstream include 0.92.4, closing this as 'fix released'."
1768875,2019-05-02 19:47:41 UTC,"This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'."
1768875,2019-04-26 00:33:16 UTC,"Fedora has applied additional patches downstream, could all users with this problem please test it with the latest RPM version (inkscape-0.92.4-1.fc28.x86_64 or later)."
1768875,2019-03-12 17:35:11 UTC,Similar problem has been detected:
1768875,2019-01-09 23:07:49 UTC,I compiled current development version ‘0.92 + devel (7f5d2af69c)’ and it seems to no longer crash on this file.
1768875,2018-10-10 09:30:19 UTC,Similar problem has been detected:
1768875,2019-01-09 22:34:39 UTC,"Unfortunately, it did not fix the crash for me.  Inkscape crashes when I"
1768875,2018-11-17 14:12:25 UTC,Similar problem has been detected:
1768875,2018-11-13 12:08:34 UTC,Here's an easier way to crash inkscape-0.92.3-2.fc28.x86_64:
1768875,2018-11-05 23:03:24 UTC,"(in reply to my comment #40) my workflow did not trigger the bug anymore, but it seems to be still around.
Yesterday I encountered this bug on Fedora 28 (and today on 29) x86_64.
$ rpm -q inkscape
inkscape-0.92.3-5.fc29.x86_64
and
inkscape-0.92.3-2.fc28.x86_64"
1768875,2018-11-05 10:57:34 UTC,Similar problem has been detected:
1768875,2018-11-05 01:51:43 UTC,"Same for me on fedora 29 :
/usr/include/c++/8/bits/stl_vector.h:950: std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = Inkscape::Text::Layout::Character; _Alloc = std::allocator<Inkscape::Text::Layout::Character>; std::vector<_Tp, _Alloc>::const_reference = const Inkscape::Text::Layout::Character&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed."
1768875,2018-11-03 03:37:52 UTC,*** Bug 1645728 has been marked as a duplicate of this bug. ***
1768875,2018-10-30 05:47:25 UTC,*** Bug 1644145 has been marked as a duplicate of this bug. ***
1768875,2018-11-26 12:25:59 UTC,*** Bug 1653271 has been marked as a duplicate of this bug. ***
1768875,2018-06-20 19:18:43 UTC,*** Bug 1590279 has been marked as a duplicate of this bug. ***
1768875,2018-07-08 23:28:42 UTC,"With July's inkscape-0.92.3-2.fc28.x86_64 I no longer get an immediate crash working within a text object (yay!). But I just experienced a crash with
  stl_vector.h:950: std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _... : Assertion '__builtin_expect(__n < this->size(), true)' failed.
in the console and
  std::__replacement_assert(char const*, int, char const*, char const*) in the backtrace
possibly the same as comment #13 and comment #32, even though comment #40 reports this version fixed it."
1768875,2018-06-19 10:03:28 UTC,With me the program execution is aborted every time you try to break the line of a text that the area was not defined by drag and drop of the cursor. Sometimes (often) this also happens with text boxes with defined area.
1768875,2018-05-03 16:02:22 UTC,Just to be clear: simply opening the file attached to this bug triggers the crash. The original file was created with a previous version of inkscape.
1768875,2018-05-03 15:35:32 UTC,Inkscape 0.92.2 in RHEL7 opens the same file just fine.
1768875,2018-05-03 04:10:13 UTC,"Created attachment 1430418
problem that reproduces this crash"
1768875,2018-05-03 04:09:25 UTC,I've got a very similar problem:
1768875,2018-04-09 16:24:42 UTC,Similar problem has been detected:
1768875,2018-04-09 16:22:11 UTC,"Created attachment 1419412
File: proc_pid_status"
1768875,2018-04-09 16:22:09 UTC,"Created attachment 1419411
File: open_fds"
1768875,2018-04-09 16:22:08 UTC,"Created attachment 1419410
File: mountinfo"
1768875,2018-04-09 16:22:06 UTC,"Created attachment 1419409
File: maps"
1768875,2018-06-20 18:33:15 UTC,Similar problem has been detected:
1768875,2018-04-09 16:22:02 UTC,"Created attachment 1419407
File: environ"
1768875,2018-04-09 16:22:01 UTC,"Created attachment 1419406
File: dso_list"
1768875,2018-04-09 16:21:59 UTC,"Created attachment 1419405
File: cpuinfo"
1768875,2018-04-09 16:21:58 UTC,"Created attachment 1419404
File: core_backtrace"
1768875,2018-04-09 16:21:56 UTC,"Created attachment 1419403
File: cgroup"
1768875,2018-04-09 16:21:54 UTC,"Created attachment 1419402
File: backtrace"
1768875,2018-04-09 16:21:46 UTC,"Description of problem:
I double-clicked on a row of text and pressed Delete."
1768875,2018-05-03 16:43:43 UTC,"- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- not reproduced on Windows 10, Inkscape 0.92+devel (7f24a76, 2018-04-17)"
1768875,2018-05-03 17:17:16 UTC,Here is another version of the file with the embedded bitmap.
1768875,2018-04-09 16:22:04 UTC,"Created attachment 1419408
File: limits"
1768875,2018-05-22 01:32:33 UTC,Similar problem has been detected:
1768875,2018-05-16 14:06:23 UTC,*** Bug 1578869 has been marked as a duplicate of this bug. ***
1768875,2018-06-19 09:55:30 UTC,"Description of problem:
The program execution is aborted every time you try to break the line of a text that the area was not defined by drag and drop of the cursor. Sometimes (often) this also happens with text boxes with defined area."
1768875,2018-06-19 09:53:20 UTC,*** Bug 1592776 has been marked as a duplicate of this bug. ***
1768875,2018-06-17 04:09:57 UTC,*** Bug 1592105 has been marked as a duplicate of this bug. ***
1768875,2018-06-15 12:11:36 UTC,Similar problem has been detected:
1768875,2018-06-15 12:05:24 UTC,Similar problem has been detected:
1768875,2018-06-13 00:58:40 UTC,*** Bug 1590590 has been marked as a duplicate of this bug. ***
1768875,2018-06-12 09:23:00 UTC,*** Bug 1590231 has been marked as a duplicate of this bug. ***
1768875,2018-06-15 21:55:37 UTC,Similar problem has been detected:
1768875,2018-06-09 18:21:06 UTC,*** Bug 1589452 has been marked as a duplicate of this bug. ***
1768875,2018-06-09 15:18:46 UTC,My report was rejected as duplicate of this after uploading everything...
1768875,2018-06-08 19:31:27 UTC,*** Bug 1589365 has been marked as a duplicate of this bug. ***
1768875,2018-05-31 11:27:53 UTC,This has shown up on Fedora 28 (here) and on Alpine Linux. I found this bug from someone on Alpine Linux. https://bugs.launchpad.net/inkscape/+bug/1767518 Upstream hasn't (at time of writing) acknowledged it yet. I linked this bug to that ticket.
1768875,2018-05-27 14:52:57 UTC,"I manage to reproduce this bug in Fedora 28 with inkscape version:
$ inkscape -V
Inkscape 0.92.3 (2405546, 2018-03-11)"
1768875,2018-05-27 14:40:28 UTC,Similar problem has been detected:
1768875,2018-06-12 03:06:48 UTC,*** Bug 1590078 has been marked as a duplicate of this bug. ***
1768875,2018-05-27 14:24:46 UTC,Similar problem has been detected:
1768876,2018-09-24 14:47:06 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1768876,2018-09-24 14:47:47 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1768876,2019-03-13 22:17:39 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/643173"
1768876,2019-03-13 23:25:42 UTC,"Reviewed:  https://review.openstack.org/567701
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0ed68c76fa8a84d1d5f0ab945e34c8e16341d627
Submitter: Zuul
Branch:    master"
1768876,2019-03-25 22:58:29 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/647630"
1768876,2019-03-25 21:58:54 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/647623"
1768876,2019-04-17 20:30:02 UTC,"Reviewed:  https://review.openstack.org/647623
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ee07c1c67d4ee6b146783c40826c4a28bd7367c3
Submitter: Zuul
Branch:    stable/queens"
1768876,2018-06-25 16:41:00 UTC,"Reviewed:  https://review.openstack.org/571320
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=487c6dd778312780740d8cb9a0b51f3fa177c1c4
Submitter: Zuul
Branch:    stable/pike"
1768876,2019-04-22 05:25:14 UTC,"Reviewed:  https://review.opendev.org/647630
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6832b0e070cebbe48a71a46d88b9412375989c1
Submitter: Zuul
Branch:    stable/pike"
1768876,2019-03-15 18:26:12 UTC,"Reviewed:  https://review.openstack.org/643173
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=133763d3582c2e85e4e5962b542294135d1a7f4c
Submitter: Zuul
Branch:    stable/rocky"
1768876,2018-06-08 12:24:52 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1768876,2018-05-10 17:12:10 UTC,"So before that change in Pike, the instance.availability_zone was set to CONF.default_availability_zone which defaults to None:"
1768876,2018-05-30 21:56:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/571320"
1768876,2018-05-30 21:52:21 UTC,"Reviewed:  https://review.openstack.org/567878
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6b4c38c04177ff194d05368cd4aff69958075167
Submitter: Zuul
Branch:    master"
1768876,2018-05-30 21:41:09 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/571317"
1768876,2018-05-11 15:21:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/567878"
1768876,2018-05-11 07:58:33 UTC,"Okay, so this means if req_spec.avz is None, this holds -> ""None, which means that the instance can move from one availability zone to another during its lifetime if it is moved from one compute node to another."""
1768876,2018-05-10 23:32:05 UTC,"Turns out there wasn't a regression wrt setting the instance.availability_zone in pike, see https://review.openstack.org/567701."
1768876,2018-05-10 23:30:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/567701"
1768876,2018-05-09 22:42:03 UTC,"Alternatively, we need an online data migration to set the instance.availability_zone for those that don't yet have it."
1768876,2018-05-09 22:39:16 UTC,"Found it, this was the change, https://review.openstack.org/#/c/446053/, in Pike."
1768876,2018-05-09 22:35:27 UTC,"Yeah I'm not sure what ""We store the availability_zone on the instance now"" is specifically referring to, i.e. which change was made for that statement to be true."
1768876,2018-06-03 18:13:23 UTC,"Reviewed:  https://review.openstack.org/571317
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0a481a52929626c5fab8fd6fd50cca6882db3bd9
Submitter: Zuul
Branch:    stable/queens"
1768877,2018-05-04 12:37:20 UTC,"I've reinstalled ubuntu 18.04 on the same machine. Choose ""C"" as default locale. The only package that I've choose on installation was OpenSSH server."
1768877,2018-05-04 01:59:09 UTC,"No, it does not make any difference."
1768877,2018-05-03 15:39:31 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f246674cb9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f246674ae0e ""malloc(): memory corruption"") at malloc.c:5350
 _int_malloc (av=av@entry=0x7f2466981c40 <main_arena>, bytes=bytes@entry=4064) at malloc.c:3738
 __GI___libc_malloc (bytes=4064) at malloc.c:3057
 ?? ()"
1768877,2018-05-03 22:50:24 UTC,"I'm able to add and remove this langpack from my (much more pedestrian) i7 laptop; do you notice other problems on this system? e.g. can you do a kernel build on it without trouble? (I'm surprised something that feels as basic as locales generation fails, when it manages to get to a prompt..)"
1768877,2018-05-03 23:08:41 UTC,"It looks like you set pt_BR.UTF-8 in /etc/default/locale before that locale had been generated. Does it make a difference if you set a locale which exists (such as en_US.UTF-8), reboot, and then run locale-gen?"
1768899,2018-05-03 16:23:08 UTC,"I'm not seeing a lot in maas.log, regiond.log, etc so far. At this early point in the installation, most of the interesting bits seem to be in rsyslog, which is very long as soon is it starts running out of space.  Here's a snippit from the end of it trying to extract the image and running out of space:
May  3 16:16:02 saved-minnow-201606-22459 cloud-init[2196]: 1370112K ........ ..
...... ........ ........ ........ ........ 98% 11.9M 10s
May  3 16:16:02 saved-minnow-201606-22459 cloud-init[2196]: 1373184K ........ ..
...... ........ ........ ........ ........ 98% 11.2M 8s
May  3 16:16:06 saved-minnow-201606-22459 cloud-init[2196]: 1376256K ........ ..
...... ........ ........ ........ ........ 99%  827K 7s
May  3 16:16:12 saved-minnow-201606-22459 cloud-init[2196]: 1379328K ........ ..
...... ........ ........ ........ .tar: ./usr/share/terminfo/x/xnuppc-m: Cannot write: No space left on device
May  3 16:16:12 saved-minnow-201606-22459 cloud-init[2196]: tar: ./usr/share/terminfo/x/xterm-xmc: Cannot write: No space left on device
May  3 16:16:12 saved-minnow-201606-22459 cloud-init[2196]: tar: ./usr/share/terminfo/x/xterm+kbs: Cannot write: No space left on device
May  3 16:16:12 saved-minnow-201606-22459 cloud-init[2196]: tar: ./usr/share/terminfo/x/xterm+pce1: Cannot write: No space left on device
May  3 16:16:12 saved-minnow-201606-22459 cloud-init[2196]: tar: ./usr/share/ter"
1768899,2018-05-04 01:19:32 UTC,MAAS only supports custom storage configuration on Ubuntu images from the stream. Other images use a flat layout on the first disk. My guess is the first disk that is enumerating on the system is the SD card.
1768899,2018-05-04 06:18:18 UTC,"I’ve a feeling we’ve seen this before and not quite sure here whether curtin should at all pick a sd card for the installation, ever, unless it gets specifically told so."
1768899,2018-05-04 06:56:19 UTC,An install log would be useful.
1768899,2018-07-10 04:17:40 UTC,[Expired for curtin because there has been no activity for 60 days.]
1768899,2019-09-19 12:05:29 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1768901,2018-05-09 22:09:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/567436"
1768901,2019-02-26 13:27:45 UTC,Is this still an issue?
1768901,2019-07-31 23:45:57 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1768901,2019-07-31 23:46:09 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/567436
Reason: This review is > 90 days without comment, and failed Zuul the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1768901,2019-09-04 20:22:21 UTC,This hasn't been reproduced in some time. Feel free to reopen if it happens again
1768903,2019-03-05 13:46:33 UTC,Is this still needed?
1768903,2021-02-17 17:07:44 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1768904,2019-08-14 04:17:18 UTC,[Expired for linux-hwe-edge (Ubuntu) because there has been no activity for 60 days.]
1768904,2019-06-14 13:58:54 UTC,Testing with:
1768904,2019-06-14 09:31:24 UTC,"Hello,
do you still have this issue with the latest linux-hwe-edge kernel?
Thanks"
1768904,2018-05-13 22:44:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768905,2018-06-05 19:46:27 UTC,This bug was fixed in the package menu - 2.1.47ubuntu3
1768905,2018-06-27 00:44:28 UTC,This bug was fixed in the package menu - 2.1.47ubuntu1.16.04.1
1768905,2018-06-25 09:31:27 UTC,"OK, so let's roll out xenial as well. We waited our week."
1768905,2018-06-20 11:16:00 UTC,This bug was fixed in the package menu - 2.1.47ubuntu2.1
1768905,2018-06-19 21:51:02 UTC,"The verification of the Stable Release Update for menu has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1768905,2018-06-19 21:50:56 UTC,This bug was fixed in the package menu - 2.1.47ubuntu1.17.10.1
1768905,2018-06-18 09:16:01 UTC,"I have not heard about any regressions in proposed, so I think we should start releasing the update for bionic and artful now and watch out for those in the release pocket. If we don't see issues with that, we can then roll out xenial next week to give it some more time to mature in a less used release."
1768905,2018-06-18 09:12:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768905,2018-06-06 14:31:16 UTC,"Hello Nikkus, or anyone else affected,"
1768905,2018-06-06 14:30:45 UTC,"Hello Nikkus, or anyone else affected,"
1768905,2018-06-06 14:30:06 UTC,"Hello Nikkus, or anyone else affected,"
1768905,2019-04-22 06:34:50 UTC,mine was update from 18.10 to 19.04
1768905,2018-06-05 18:03:27 UTC,"Adding tasks for down to xenial, but not sure what we want to do. I don't foresee any trouble with that change, but we can't test it, and even if we get a failing upgrade, we can only test for that release."
1768905,2018-05-30 22:35:55 UTC,"Brian,"
1768905,2018-06-05 17:47:26 UTC,"I could not reproduce this with that file in my lxd testing setup either. It might depend on PPA packages changing the order. That said, fixing the trigger to be noawait is definitely the right thing to do-"
1768905,2018-05-03 22:22:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768905,2018-05-08 17:54:38 UTC,Could you provide us with an apt-clone file from before the upgrade to Ubuntu 18.04? You should be able to find one at /var/log/dist-upgrade/apt-clone_system_state.tar.gz.  Thanks in advance.
1768905,2018-05-08 19:34:00 UTC,Of course.. :)
1768905,2018-05-03 22:20:14 UTC,This was an upgrade from Ubuntu 17.10 to Ubuntu 18.04.
1768905,2018-05-23 16:16:03 UTC,"I restored the apt-clone file in a container (with rc-policy.d disabling services), tried a straight apt dist-upgrade, and that worked. Will check with do-release-upgrade tomorrrow."
1768905,2018-05-24 08:46:39 UTC,"do-release-upgrade worked as well, so what I'd need for further investigation is /var/log/dpkg.log from after the failed upgrade. That might be dpkg.log.1 or dpkg.log.2 or something."
1768905,2018-05-30 12:29:38 UTC,"I think it's a fundamental problem that interest triggers are not considered for ordering packages, and hence cannot be used reliably. Fixing this bug is probably a matter of making all the triggers noawait, although I can't reproduce it, so I can't test any SRU."
1768905,2018-05-30 15:10:03 UTC,Could any of the reporters of duplicates of this bug provide their apt-clone file for testing? You should be able to find one at /var/log/dist-upgrade/apt-clone_system_state.tar.gz. Thanks in advance.
1768905,2018-05-17 18:32:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768910,2018-05-07 18:39:36 UTC,Could you please provide us with the answers file you used to deploy the environment and the full list of packages installed after the packstack command failed?
1768910,2018-05-08 23:08:00 UTC,"[root@rdo manifests]# rpm -qa | grep -e openstack-keystone -e puppet -e openstack-packstack
puppet-sysctl-0.0.11-1.el7.noarch
puppet-ssh-3.0.1-4.fb2de75git.el7.noarch
puppet-ovn-12.4.0-1.el7.noarch
puppet-nova-12.4.0-1.el7.noarch
puppet-trove-12.4.0-1.el7.noarch
openstack-packstack-12.0.0-1.el7.noarch
puppet-inifile-2.2.0-1.d2c38b9git.el7.noarch
puppet-memcached-3.1.0-1.el7.noarch
puppet-rabbitmq-8.1.1-0.d4b06b7git.el7.noarch
puppet-keystone-12.4.0-1.el7.noarch
puppet-heat-12.4.0-1.el7.noarch
puppet-tempest-12.5.0-1.el7.noarch
puppet-concat-4.1.1-1.d4857dfgit.el7.noarch
puppet-vcsrepo-2.3.0-1.bb1209egit.el7.noarch
puppet-vswitch-8.4.0-1.el7.noarch
puppet-nssdb-1.0.1-1.el7.noarch
puppet-corosync-6.0.1-0.9940eb9git.el7.noarch
puppet-mysql-5.2.1-1.a5497b2git.el7.noarch
puppet-glance-12.5.0-1.el7.noarch
puppet-manila-12.4.0-1.el7.noarch
puppet-panko-12.4.0-1.el7.noarch
puppet-swift-12.4.0-1.el7.noarch
puppet-remote-0.0.1-3.7420908git.el7.noarch
openstack-keystone-13.0.0-1.el7.noarch
puppet-4.8.2-1.el7.noarch
puppet-apache-2.3.1-1.e587f2agit.el7.noarch
puppet-rsync-0.4.0-3.447685fgit.el7.noarch
puppet-horizon-12.4.0-1.el7.noarch
puppet-certmonger-2.3.0-1.el7.noarch
puppet-openstack_extras-12.4.0-1.el7.noarch
puppet-openstacklib-12.4.0-1.el7.noarch
puppet-cinder-12.4.0-1.el7.noarch
puppet-ceilometer-12.5.0-1.el7.noarch
puppet-sahara-12.4.0-1.el7.noarch
puppet-magnum-12.2.0-1.el7.noarch
openstack-packstack-puppet-12.0.0-1.el7.noarch
puppet-stdlib-4.24.0-1.b0d99adgit.el7.noarch
puppet-firewall-1.12.0-1.3dc1990git.el7.noarch
puppet-archive-2.2.1-0.10888dbgit.el7.noarch
puppet-oslo-12.4.0-1.el7.noarch
puppet-gnocchi-12.4.0-1.el7.noarch
puppet-aodh-12.4.0-1.el7.noarch
puppet-xinetd-3.0.0-1.b95c79cgit.el7.noarch
puppet-redis-3.2.0-2.bfcc212git.el7.noarch
puppet-staging-1.0.4-1.b466d93git.el7.noarch
puppet-neutron-12.4.0-1.el7.noarch
puppet-ironic-12.4.0-1.el7.noarch"
1768910,2018-05-08 23:06:14 UTC,Will do. Give me a bit of time
1768910,2018-05-08 11:38:27 UTC,"I have tried to reproduce the issue on a CentOS 7 VM with RDO Queens, and there is no way I can do it. Having another look at the logs, I find the following at the beginning of the keystone log:"
1768910,2018-05-08 02:20:03 UTC,"The only thing I am trying to turn on is magnum but as I said, the first try was without the answer file and failed at same place. Each time, I reload the OS completely for each new try."
1768910,2018-05-08 02:18:38 UTC,https://www.dropbox.com/s/tte88tunapf06fk/answers.cfg?dl=0
1768910,2018-05-08 02:16:08 UTC,"Will gladly upload. As far as how it was deployed, I have tried several times using different scenarios. Clean install and no answer file and with the answer file. All have ended here at this error."
1768910,2018-05-07 15:45:57 UTC,"I'm puzzled about this. Looking at the controller.log file, right after starting httpd we are trying to create a Keystone domain, but that fails because the services tenant is not present. This has not happened before in our CI environments or real-life tests :-/."
1768910,2018-05-04 20:01:35 UTC,https://www.dropbox.com/s/4rmhesyzmbow7ww/logs.tgz?dl=0
1768910,2018-05-07 09:23:13 UTC,"So looking at the logs, we see the following in the Keystone log:"
1768910,2018-05-04 20:06:43 UTC,"Also, I have access to the squid logs and I do not see any requests from this machine towards keystone. Only towards the repos."
1768910,2018-05-04 20:04:25 UTC,"I do have a no_proxy set:
export http_proxy=http://10.1.20.57:80
export https_proxy=http://10.1.20.57:80
export no_proxy=10.1.32.8,localhost,10.1.20.16"
1768910,2018-05-04 17:32:55 UTC,"Wait a second, I think I have an idea."
1768910,2018-05-04 17:09:28 UTC,"Will upload. This is on a clean system. New install of CentOS. Basically followed the RDO install instructions starting with new OS install. I have done this 3 times and each time, I hit this issue."
1768910,2018-05-04 09:01:12 UTC,"Hi,"
1768910,2019-01-22 06:34:46 UTC,"Im trying to install openstack behind a proxy network I have gone through the comment above but none is working for me.Can anyone please say what all are the domain openstack packstack installation is trying to access so admin can free those domain.
Thanks in advance
fad"
1768910,2018-05-07 14:11:01 UTC,https://www.dropbox.com/s/71xti8juhv8wci5/pplogs.tgz?dl=0
1768912,2018-07-13 16:51:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768916,2018-05-03 22:37:45 UTC,"I have seen this too. I was able to cancel and start again, and then NOT look at the details so the window stayed small..."
1768917,2019-06-13 23:20:39 UTC,you are conflating two different things
1768919,2019-06-13 23:29:17 UTC,i have closed this as a duplicate as i explain in the other bug that you miss understood how to use this feature.
1768920,2018-10-01 20:17:18 UTC,I have this problem all the time. Now i have it in 18.10 beta
1768920,2019-09-06 22:55:35 UTC,This should be fixed in ubuntu-mate-settings (19.10.2) which is part of Ubuntu MATE 19.10.
1768920,2020-08-24 07:30:29 UTC,I still have this bug in 20.04.
1768922,2018-06-15 15:07:44 UTC,"Change abandoned by Shane Peters (<email address hidden>) on branch: master
Review: https://review.openstack.org/567921
Reason: Abandoning this in favor of the above approach. The solution was tested and successfully deployed in a production environment. Note, you'll need to define volume types to utilize this solution."
1768922,2018-05-29 03:49:17 UTC,There is a subtle but critical difference in how Cinder represents a backend located in the [DEFAULT] section to one in a separate section to the rest of OpenStack; `host` vs `host`@`volume_backend_name`.
1768922,2018-06-15 15:23:40 UTC,"A cleaner approach is to deploy a second cinder charm that only runs the 'volume' service.  Then, deploy and relate a cinder-ceph charm to it. This second cinder charm would then use a sectional config and wouldn't interrupt existing volumes defined under the 'DEFAULT' section of the primary cinder charm."
1768922,2018-05-10 11:26:33 UTC,"Agree this needs some untangling - at Ocata, the cinder charm does move to sectional config for directly related ceph so I'm wondering whether we need to move that back to mitaka as well (which still uses in DEFAULT configuration as outlined)."
1768922,2018-05-11 18:16:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/567921"
1768926,2018-05-03 18:38:07 UTC,"Hello djcj,"
1768927,2018-05-03 19:09:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566143"
1768927,2018-07-31 10:32:49 UTC,"Reviewed:  https://review.openstack.org/566143
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3437baedf646c7cd3da43440368edc194a880db8
Submitter: Zuul
Branch:    master"
1768927,2018-08-10 09:53:01 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.
1768928,2018-05-03 18:56:02 UTC,"Hello djcj,"
1768928,2018-05-03 19:33:21 UTC,"Looking at the DjVuLibre headers on my system, I cannot find DJVUAPI_EXPORT at all? Also are you sure that you need to undefine the *_EXPORT variants? From looking at"
1768928,2018-05-03 20:20:37 UTC,"Okay, it looks like I really don't need to edit djvumodel.cpp. Adding the following line to qpdfview_win32.pri is enough: DJVU_PLUGIN_DEFINES += DDJVUAPI= MINILISPAPI=
(trailing equal sign is needed or the build fails for me)"
1768928,2018-05-04 05:14:34 UTC,"Hello again,"
1768932,2018-05-04 12:03:49 UTC,I couldn't figure out how to attach more than one file. It's just a list of the translation and help files. I've attached both files in a zip.
1768932,2018-05-04 05:18:09 UTC,"Hello again,"
1768932,2018-05-03 18:47:30 UTC,"Hello djcj,"
1768932,2018-05-03 21:19:17 UTC,"Here's a new patch. It will now always check for embedded resources but only compile resources if configured with ""qmake CONFIG+=with_staticresources""."
1768934,2018-05-08 12:30:52 UTC,"I would guess that we record the information that we find, but we don't *delete* the information that we are replacing.
Seems like a bug to me."
1768935,2018-05-03 22:35:25 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1768937,2019-07-30 15:47:31 UTC,I have A similar problem. I open a picture and try to change the pen color. I get the following ouput to my terminal when I run pinta.
1768955,2018-05-03 19:16:36 UTC,"For the record, kubevirt issue that revealed the problem is: https://github.com/kubevirt/kubevirt/issues/936"
1768958,2018-08-24 20:18:03 UTC,https://bugzilla.redhat.com/show_bug.cgi?id=1612618
1768958,2018-08-24 21:06:27 UTC,This will probably hit more and more people as whatever is newer in Fedora us updated in other distros. I think it's a bug in something Inkscape uses but I'm not sure what.
1768958,2019-04-09 22:55:37 UTC,Closing because this can't be reproduced on Inkscape 1.0alpha (Ubuntu).
1768958,2019-04-09 23:06:36 UTC,Uuuhm. This is a Fedora-specific bug. Please leave this open for a Fedora user to test.
1768958,2019-04-09 23:07:30 UTC,"Or rather, to confirm the fix."
1768958,2019-04-18 06:27:51 UTC,Tested a bunch of issues regarding Fedora 28/29. I think this issue should be closed.
1768958,2019-04-09 23:17:59 UTC,"Fedora-specific crashes can be tested only if making sure that FORTIFY_SOURCE=2 is set in the build, and I do not remember if 1.0-alpha has it enabled."
1768958,2019-04-18 09:50:59 UTC,"Not looking good for my build tests, built from the INKSCAPE_0_92_3 tag and it looks like the bugs are not being replicated."
1768958,2019-04-22 04:11:20 UTC,"Alright, got it into my Linux Mint 19.1 builds."
1768958,2019-04-25 15:22:22 UTC,Backport to 0.92.x has been merged here: https://gitlab.com/inkscape/inkscape/merge_requests/647
1768958,2019-04-09 23:07:54 UTC,"Or read up on the fedora bug reports, where maybe someone already has confirmed the fix."
1768958,2018-07-02 23:55:22 UTC,"Although I have the same OS version and Inkscape version, I could not reproduce the crash when hitting Enter on empty text.
But I am affected by other crashes related to text:
https://bugs.launchpad.net/inkscape/+bug/1779779"
1768958,2018-05-07 21:18:26 UTC,Not reproduced with Inkscape 0.92.x on Linux Mint 18.3 - could this be Fedora-specific?
1768958,2018-06-04 15:58:41 UTC,I was able to reproduce this with the same conditions and error output as the OP.
1768958,2018-05-27 01:48:42 UTC,"There are multiple reports about crashes during different text editing actions on Fedora 28, with at least three different traceback messages - however, I suspect they're all related somehow."
1768958,2018-05-08 12:03:29 UTC,"Neither the snap package or a compiled version of inkscape seem to have this issue, so it must be fedora compilation specific."
1768958,2018-05-08 11:59:46 UTC,Just summarizing:
1768958,2018-05-08 05:38:51 UTC,"Could be. I opened a Bug report on the Fedora Bugtracker
https://bugzilla.redhat.com/show_bug.cgi?id=1575842"
1768958,2018-05-07 11:44:35 UTC,Also happens when loading a file that has a line break in normal text (not flow text)
1768958,2018-05-07 08:34:07 UTC,"the bug happen, when I trying to edit some text. It's not happen when I create new text"
1768958,2018-05-07 08:30:30 UTC,this happen to me too.
1768958,2018-05-06 18:44:24 UTC,"This happens to me too. It also seems to crash when double-clicking text after it has been created, showing the same error - but before the emergency save text..."
1768958,2018-05-04 09:46:27 UTC,"- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1768958,2018-06-05 17:57:50 UTC,Hmm. Do older versions of software get recompiled for f28?
1768961,2018-05-23 17:34:28 UTC,"Like I said, Lubuntu Next is unsupported. Never has been."
1768961,2018-05-26 19:03:29 UTC,"Having now installed the 05/25 daily of Cosmic (18.10) in my test partition,
I can confirm that the bug is still present."
1768961,2018-05-26 19:07:18 UTC,"Here is the promised screenshot (which looks much like the last one, as nothing has changed)."
1768961,2018-07-12 23:55:18 UTC,"I have kept tabs on the .manifest files of the daily .iso , and I noted recently
that both PCManFM-qt and libfm-qt5 have now gone to 0.13.x versions."
1768961,2018-07-15 05:51:10 UTC,https://github.com/lxqt/lxqt/issues/1389
1768961,2018-11-01 23:40:13 UTC,"Here are the terminal commands that I saw in your screenshot,
plus output from inxi, which is similar to what produced your system output."
1768961,2018-10-08 04:32:42 UTC,"I've tried again to reproduce this with the latest daily of Cosmic and still can't. I've even gone out of my way to setup a new drive with a DOS partition table and an ext4 partition. I automounted it to data. So unless you have a different partitioning scheme, this should be nearly an exact replica of your situation. Either that, or I'm not getting something."
1768961,2018-10-13 23:59:37 UTC,"I am currently out of town (and before then was busy trying to find a new used car to replace one damaged in an accident) or I would have installed the beta version of L 18.10 to test if the problem has since gone away.  I probably will not be able to test it before the final version is released, but will do so then, and will also show my partitioning scheme (I'm sure there is a terminal command to do that, but don't know it offhand...), and my fstab file contents.
Should you have any command you would like me to run at that time, let me know, please."
1768961,2018-10-14 17:04:22 UTC,"As you can see in my screenshot, `sudo parted /dev/sdb print` will do the trick, but use whatever is the right desiginator for your drive. You should be able to find this by doing `mount | grep ' / '`."
1768961,2018-11-01 23:27:56 UTC,OK.
1768961,2018-05-23 16:35:13 UTC,">Maybe you should try following what I did in a clean system
>(try a virtual machine)?
I did.
I did a complete fresh install in one of my partitions.
""Desktop"" did its default ""/home/scott/Desktop"" initially.
Then I swapped out the default user-dirs.dirs with mine (see above),
logged out, logged in, and it was just as I reported it above
(see initial description,as well as #13).
I had not added any packages (but did update-software, to get the
updated packages that had changed since install).
"
1768961,2018-08-19 08:07:43 UTC,"Hello everyone,"
1768961,2018-05-21 00:56:06 UTC,"To be clear, I didn't say you're crazy, but that I can't reproduce this. Maybe you should try following what I did in a clean system (try a virtual machine)?"
1768961,2018-05-23 16:50:18 UTC,"I have now booted into my old Lubuntu Next 17.10 install, to see what
PCManFM-qt was doing there."
1768961,2018-05-15 20:05:39 UTC,"Lubuntu Next is a product we never officially released and it's unsupported. I did have an old VM laying around (18.04) and could not reproduce this behavior. I could also not reproduce this behavior in an 18.10 daily (20180515), which WILL be a released version of Lubuntu with LXQt (which was what we were aiming towards with Lubuntu Next but that ""product"" was rather confused). Here's what I did:"
1768961,2018-05-03 20:22:26 UTC,Is this $HOME/.config/user-dirs.dirs that you're editing or /etc/xdg/user-dirs.dirs?
1768961,2018-05-03 20:22:51 UTC,"For that matter, what is $HOME for you?"
1768961,2018-05-05 21:29:12 UTC,"This is $HOME/.config/user-dirs.dirs.
(I'm a little fuzzy on the details, but I believe that xdg looks for user-dirs.dirs in $HOME/.config, and if it does not find it, creates it from the default file in /etc/xdg
No, I guess not - I just had a look in /etc/xdg and found only user-dirs.defaults (which contains only ""relative pathnames from the home directory"").)"
1768961,2018-05-05 22:22:13 UTC,"I just noticed that ScreenGrab, in its Browse for default save directory,
does exactly the same thing:
Desktop under ""Places"" comes up as directory buttons (each of the following is its own button):
  /  home  scott  ""  data  scott  Desktop"""
1768961,2018-05-06 18:29:04 UTC,@Walter Lapchynski (wxl)
1768961,2018-05-07 05:39:10 UTC,"Nope, but it should be irrelevant. If what you're saying is consistent, it should end up looking in $HOME/Desktop/$HOME/Desktop/foobar, no?"
1768961,2018-05-06 04:27:01 UTC,"I changed $HOME/.config/user-dirs.dirs so that XDG_DESKTOP_DIR=""$HOME/Desktop/foobar"" and everything seems to behave fine, so I can't replicate your experience, which makes it hard to fix. Could you start with a fresh system (maybe a virtual machine) and come up with some clear steps?"
1768961,2018-05-08 20:17:25 UTC,"I just set Desktop to /blah and everything works fine in pcmanfm-qt and
calibre, for example. That said, I cannot reproduce your issue.
Something must have changed about your system that is causing these
issues, but I have no idea what they are."
1768961,2018-05-15 17:44:02 UTC,"I don't know - if you don't try it, you won't know.
The code may behave differently if it finds the string ""$HOME"",
than if it does not."
1768961,2018-05-15 17:58:41 UTC,"I *DID* try it. I set Desktop to /blah (note, there's no $HOME in there) and it did not fail."
1768961,2018-05-20 20:37:29 UTC,I will attach two screengrab'd files that show Nemo's and PCManFM's Properties->Permissions for my /data/scott/Desktop directory.
1768961,2018-05-15 18:12:58 UTC,OK.
1768961,2018-05-08 19:45:48 UTC,"My point, I guess, was that even though my xdg user-dirs.dirs directory for Desktop was:
/data/scott/Desktop
(an absolute path - no reference to $HOME)
pcmanfm-qt and a number of other programs (just was using qpdfview today and had the same problem) apparently insisted upon adding /home/scott to the beginning of my directory line, along with some spurious quote marks..."
1768962,2018-06-08 20:51:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768962,2020-03-26 17:50:27 UTC,Apologies for taking so long to get around to triage this issue. If this is still an issue please attach the DKMS make.log file generated on the failed build.
1768962,2020-06-10 10:54:29 UTC,"If this is still and issue please supply the DKMS make.log. If not, I'll close this bug in 4 weeks."
1768962,2020-08-10 04:17:19 UTC,[Expired for zfs-linux (Ubuntu) because there has been no activity for 60 days.]
1768968,2018-05-05 06:41:42 UTC,"> I suspect some ISO build tools are broken at some point
"
1768968,2018-05-03 22:58:52 UTC,to test grml boot:
1768968,2018-05-08 15:37:13 UTC,"Ok, so i tested alternative ISO, and it works from USB/BIOS mode."
1768968,2018-05-03 22:20:03 UTC,"I'm not entirely sure what ""booting with GRML"" entails.  I've just tested here on real hardware with UEFI firmware and KVM with OVMF, and both show a complete set of grub entries.  And, of course, booting in BIOS mode doesn't get grub at all, but rather isolinux/gfxboot."
1768968,2018-05-03 20:46:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1768968,2018-05-03 22:57:03 UTC,"Adam, GRML is package for existing ubuntu installation that loads ISO from grub of existing install. My hardware is not EFI, so regular BIOS boot.
I suspect some ISO build tools are broken at some point (so no idea which package i should select), unfortunately currently i don't have any external media to test."
1768972,2020-05-18 13:35:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768973,2018-05-09 01:49:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768973,2018-11-06 13:59:03 UTC,fixed upstream (in Debian testing) since version redet/8.26-1.3
1768976,2019-01-13 19:13:40 UTC,Same problem here:
1768976,2019-01-13 15:00:09 UTC,"Same symptoms here and no nvidia GPU, only ""simple"" Intel."
1768976,2019-01-01 11:09:36 UTC,"Left out: the kernel which is working now is the same, that had the overheat with nouveau: 4.15"
1768976,2019-01-01 11:03:59 UTC,"Ubuntu offered me a security update. It was offering it for a long time and I didn't want to take it, because I didn't wanted to mess it up. But installed all, and it messed it up with kernel 4.15: it couldn't install the 340 nvidia driver I need into the new kernel. It became an endless loop when ran the new kernel version (4.15). I read somewhere that this might be because of video driver. I started the last working linux kernel and activated nouveau. 4.15 kernel started this way, but overheated in a minute and shutted down."
1768976,2019-01-01 05:20:13 UTC,"If we can confirm thermald is not the culprit, we can do a kernel bisection to find the regression commit."
1768976,2018-12-31 13:04:04 UTC,"So, is it working workaround to downgrade to 4.4 kernel?
Can someone else confirm it please?"
1768976,2018-12-24 16:05:26 UTC,The issue persists in version 18.10
1768976,2018-12-23 10:12:18 UTC,"Has the same issue with Linux Mint 19.1, I read that it is based on Ubuntu 18.04"
1768976,2018-12-03 03:25:40 UTC,It is possible to try thermald package in Xenial?
1768976,2018-11-16 10:58:08 UTC,"And another observation. After booting the old kernel several times.. the 4.15 kernel starts without problems also, currently it works without the heat and performance problems. I did not change anything. I have no idea what happened there. Weird."
1768976,2018-10-03 08:54:44 UTC,"I have the same issue, migrated with fresh install from windows 10 (with no overheat problem)"
1768976,2018-11-10 15:38:56 UTC,"I want to add one more info, since most people might focus on the gpu or drivers. The gpu temp might only indirectly show cpu temps for my thinkpad, since they both are connected to the same heatpipe. Hot cpu => warm gpu. Does not mean gpu is in use."
1768976,2018-11-10 15:34:14 UTC,"Well, the new 4.15 kernel has that problem. I still have a 4.4 kernel as alternative, which does not have that problem. Something in between has gone bad. This does not really narrow it down enough to know the cause, but it's not the drivers or the hardware or other software alone."
1768976,2018-11-10 03:36:21 UTC,"I want to add an observation. I upgraded from 16.04 to 18.04 and the first boot already was sluggish and the mouse pointer is slow. First I suspected a baloo_file process to be the cause. It's not. I noticed the fans of my thinkpad spin up. I saw no load on the cpu (as normal user). Also the disk io is low. So what is causing this? Then the sensors still show high temps and it got hot. I noticed also the gpu temp is hot. Then i disabled wayland and rebooted. Still it is slow. Then i booted only into recovery root shell and noticed only as root is a kworker/u16:0 process visible, which produces high load. So now I suspect some other kernel level process is out of control, but I don't know what this kworker process belongs to.."
1768976,2018-10-21 20:38:01 UTC,I have the same problem (not over heating but xorg now constant spinning). Prior to upgrade from 16.04 to 18.04 never had this issue. At first I thought it might be related to application but even when nothing is running the x server just spins.
1768976,2018-10-06 11:56:54 UTC,"Same for me: Ubuntu 18.04 LTS fresh install on Surface Book 2017
Constant high CPU usage (> 90%) on kworker/0:1 and sometimes results to overheating and screen goes blank for seconds."
1768976,2018-10-05 06:29:43 UTC,The possible source of the problem and the solution: https://discourse.ubuntu.com/t/call-for-testing-nvidia-prime-in-ubuntu-18-04-and-18-10/8207
1768976,2019-01-19 17:02:13 UTC,"I'll leave my hardware specs here, it could help pinning down the problem cause.
I'm using NVidia driver 340.107."
1768976,2018-11-18 15:42:55 UTC,Aaand it's back again. Overheating. No real load. Hot as it can get.
1768976,2019-01-28 05:10:30 UTC,"According to this link, disabling Intel pstate governor brings the temperature down back to 16.04 levels:"
1768976,2019-11-12 08:47:46 UTC,"An update. After some digging the conclusion I is that the problem  in my case is not linux but might be the Asus BIOS. Even just enetering the BIOS the CPU temperature is rising up to 70-80 degrees. I'v e also upgraded the BIOS, but without significant improvements."
1768976,2019-02-06 15:56:02 UTC,Followed instructions from #67.
1768976,2018-09-28 13:10:32 UTC,Same for me: ubuntu 18.04 just installed on Dell Precision M3800.
1768976,2019-12-06 10:12:00 UTC,"Yeap it helps and it is quite clear.
Still another remark. Sorry for going on with the digression here.
If there is a more proper channel we can move there."
1768976,2019-12-01 15:21:17 UTC,"Each CPU can have a different request into the PLL (phase locked loop), but the highest one wins, and their vote does not count if they are in an idle state deeper than C1. You can observe this manually by reading the pstate request and granted MSRs directly (requires msr-tools, and the msr module must already be loaded). Example (requested, granted, 100% load on CPU 3):"
1768976,2019-12-01 10:01:00 UTC,"I guess you mean ""there is only one PPL in the CPU, all cores get the resulting clock"". This would mean the readout of i7z in the idle case, where each core has a different multiplier and a different clock, is fake."
1768976,2019-11-30 22:20:53 UTC,"There is only one PLL (Phase Locked Loop) in the processor, all CPUs get the resulting clock. When they go into deep idle states (deeper than C1, at least for my processor) then they give up their vote into the PLL as to what the frequency should be. Your single 100% task is dedicating the CPU frequency for all, for when they are active."
1768976,2019-11-30 21:20:03 UTC,"@Doug Smythies: thanks for the reply.
I'm sampling every second."
1768976,2019-11-30 19:42:52 UTC,"@Davide Sangalli: What you describe and show in your comment #80 is correct and exactly what should happen. Your processor is spending an extraordinary amount of time in C1 as opposed to deeper idle states. At what sampling frequency do you run i7z? I would suggest once every 15 seconds or so, so that you don't wake up CPUs just to ask them status stuff."
1768976,2019-11-30 18:39:59 UTC,"I also mention that, monitoring with i7z the clock of my CPU, when intel turbo is not working I get different freqs for each core
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  Temp      VCore
        Core 1 [0]:       1126.19 (11.23x)      7.99    93.9       1       1    40      0.6274
        Core 2 [1]:       1239.87 (12.36x)       3.2    95.1       1    2.11    41      0.6208
        Core 3 [2]:       1577.66 (15.73x)       3.7    95.4       1       1    38      0.6257
        Core 4 [3]:       1316.89 (13.13x)      7.23    81.9       1    12.8    39      0.6257
        Core 5 [4]:       1572.58 (15.68x)      10.2      87       1    4.73    39      0.6257
        Core 6 [5]:       1916.98 (19.11x)      8.02    90.6       1    1.44    39      0.6266"
1768976,2019-02-05 21:35:35 UTC,"I confirm, that disabling Intel pstate driver helps to solve overheating. Read instructions below."
1768976,2019-11-12 02:06:49 UTC,"Same problem. I use laptop PC, Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz, GPU GeForce GTX 1080 * 2.
DISTRIB_DESCRIPTION=""Ubuntu 18.04.3 LTS"".
Linux kernel version is  ""Linux anomalydetect 4.15.0-66-generic""."
1768976,2019-10-10 22:44:49 UTC,"Same problem here.
Ubuntu 18.04.3 LTS
I tried kernels 4.15, 5.0 and 5.3 and the problem persists.
With default installation parameters CPU temperatures goes above 95° very easily."
1768976,2019-09-08 17:34:43 UTC,"Same problem. XPS 15 9570, freshly installed Ubuntu 18.04.3. 70-99 degrees while using browser + IDE.  Disabling turbo boost keeps it under 80 degrees, but that's not a solution. intel_pstate is enabled, disabling it does not help."
1768976,2019-08-18 13:59:53 UTC,Have the same overheating problem on all my Lenovo laptops.
1768976,2019-05-14 09:06:50 UTC,"I'm not sure if this is related but just in case. I upgraded from 16.04.1 LTS to 18.04.2 - straight after I started getting alarms from my SNMP monitoring, low voltage VBat etc. Upon checking the sensors output I can see it's all messed up:"
1768976,2019-04-24 16:16:21 UTC,UPDATE:
1768976,2019-04-23 19:21:55 UTC,"UPDATE:
After blacklisting nuoveau and installing nvidia driver, there was no overheat shutdown, but the cpu is on full speed all the time. and the tempetature is 87 celsius constantly.
I tried disabling pstate, using tlp, neither worked so far.
Here is a usual frame from top:"
1768976,2019-04-08 21:17:30 UTC,I have the same problem on my Vostro 3500. I'm using the 4.15.0-47-generic kernel with Gnome 3.28.2 on 18.04.2 LTS. Temperatures are at 67-81C and using Win10 on the same laptop the temperatures are 45-57C with no apps running in either OS.
1768976,2019-02-07 01:55:25 UTC,Recently I formatted and reinstalled the version 18.04.1 Now the overheating problem is gone. Everything is working just fine
1768976,2019-10-31 07:31:12 UTC,Acer aspire a715-71g. Same problem. Laptop overheating when i switch on nvidia proprietary driver. On ubuntu 17.10 it worked fine.
1768976,2018-08-29 20:36:26 UTC,"UPDATE:
I wanted to try out installing 18.04.1
After having the live mode started and opening the menu my laptop shutted down suddenly and it is hot now.
Also it somehow messing up the fan. I have to restart from Windows to have it sound and work fine.
Windows is running like charm, no overheats."
1768976,2018-06-03 13:05:27 UTC,apport information
1768976,2018-08-26 18:03:37 UTC,The same problem. Clean install. Asus S46CM.
1768976,2018-06-03 13:05:21 UTC,apport information
1768976,2018-06-03 13:05:19 UTC,apport information
1768976,2018-06-03 13:05:17 UTC,apport information
1768976,2018-06-03 13:05:16 UTC,apport information
1768976,2018-06-03 13:05:14 UTC,apport information
1768976,2018-06-03 13:05:12 UTC,apport information
1768976,2018-06-03 13:05:11 UTC,apport information
1768976,2018-06-03 13:05:09 UTC,apport information
1768976,2018-06-03 13:05:22 UTC,apport information
1768976,2018-06-03 13:05:08 UTC,apport information
1768976,2018-06-03 13:05:04 UTC,apport information
1768976,2018-06-03 13:05:03 UTC,apport information
1768976,2018-06-03 13:05:01 UTC,apport information
1768976,2018-06-03 09:27:55 UTC,"I had a similar problem. turns out it was actual high load that forced the cpu clock speed to always be more than 3GHz on all (!) cores. namely the xorg (>100%), systemd-journald (>50%) and rsyslogd(>30%) were consuming a lot cpu power. in the journal i could see the following line over and over again:"
1768976,2018-06-02 10:25:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768976,2018-06-02 10:24:52 UTC,"samwe problem here. I have a lenovo e570
cpu Intel® Core™ i5-7200U CPU @ 2.50GHz × 4
graphics GeForce GTX 950M/PCIe/SSE2"
1768976,2018-06-01 20:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1768976,2018-05-30 14:04:59 UTC,"I have the same heating issue after a clean install of Ubuntu 18.04. Before that I was using Ubuntu 16.04, without this problem."
1768976,2018-06-03 13:05:06 UTC,apport information
1768976,2018-06-03 13:05:25 UTC,apport information
1768976,2018-06-03 13:05:24 UTC,apport information
1768976,2018-07-14 20:05:32 UTC,"Same here, fresh installation of Ubuntu, Samsung npv300."
1768976,2018-08-26 11:50:20 UTC,"I had the same issue with clean install of Ubuntu 18.04.
16.04 was working fine with my laptop.
Laptop: Dell Studio XPS 1340, Processor: Intel Core 2 Duo P8600, VC: GeForce 9400MGE"
1768976,2018-08-24 20:11:00 UTC,same problem here.  Laptop is overheating.
1768976,2018-08-17 22:02:51 UTC,"Having the same issue on Precision 5520.  Started happening after upgrade form 16.04 to 18.04 as well.  I don't have Synaptic drivers installed, using libinput."
1768976,2018-08-01 03:49:46 UTC,Would it be possible for you to do a kernel bisection?
1768976,2018-07-31 10:53:11 UTC,"Hi,"
1768976,2018-07-27 22:32:31 UTC,"The same problem here.
Upgrage from 16 to 18
Dell XPS"
1768976,2018-07-16 13:35:06 UTC,"I having the same problem. Laptop Asus N551JX. Intel® Core™ i7-4720HQ CPU @ 2.60GHz × 8
Fresh install, tried with and without nvidia drivers, tried to stop thermald, didn't help.
/var/log/kern.log keeps reporting of critical cpu package temp or something before shootdown...
That feeling like critical halt temp has lowered in kernel.
Returned to 16.04 meanwhile.
Loved 18.04 very much!! Please fix this soon."
1768976,2018-07-15 16:56:35 UTC,"Same problem: Lenovo Z50, Radeon R6 R7 graphics, AMD FX 7500 CPU. The bug is definitely corresponds to the new Ubuntu version because the previously 16.04 version worked almost smoothly. (I changed it because of very slow boot process - it is a bit faster in 18.04)."
1768976,2018-06-22 19:02:08 UTC,Same issue started post 18.04 upgrade.   AMD FX at 4.7 GHz goes into thermal shutdown about a minute after getting booted up and into the desktop.   I installed cpuefreqd and set the policy to power save high (limiting the frequency scaling to about 50%) in order to keep the CPU temp below the thermal cut off limit.
1768976,2018-08-28 12:47:32 UTC,"Same problem for me.
Upgrade to 18.04.1 from 16.04.x.
Dell Precision M3800"
1768976,2018-06-04 12:55:15 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1768976,2018-06-03 13:05:41 UTC,apport information
1768976,2018-06-03 13:05:39 UTC,apport information
1768976,2018-06-03 13:05:37 UTC,apport information
1768976,2018-06-03 13:05:35 UTC,apport information
1768976,2018-06-03 13:05:33 UTC,apport information
1768976,2018-06-03 13:05:31 UTC,apport information
1768976,2018-06-03 13:05:29 UTC,apport information
1768976,2018-06-20 03:25:28 UTC,Facing the same problem here... Dell inspiron 7000.
1768978,2018-06-04 18:27:28 UTC,Confirmed in 3.1.2. One of the Alert Message columns displays the Alert Message on the patron record. It would probably be good to label it as such. I wonder if the other is a reference to the deprecated Alert Message on the copy?
1768978,2019-11-04 16:33:57 UTC,EG 3.3.4
1768978,2019-11-04 19:56:00 UTC,"I see now that in
https://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/templates/staff/circ/checkin/t_checkin_table.tt2"
1768986,2019-01-07 12:05:54 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/566173
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.
Feel free to restore it again if you want to pick up and continue the work."
1768986,2018-05-24 07:11:36 UTC,"It seems OpenStack Infra did not automatically post the review link, so for reference; https://review.openstack.org/#/c/566173/"
1768987,2018-05-03 21:37:23 UTC,Branch at working/user/dyrcona/lp1768987-findbin-sql-unique-t.
1768987,2019-05-23 20:50:48 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jason!"
1768988,2018-05-14 20:17:49 UTC,not quite. It should probably be tracked under the kernel for now since it's secure boot related. Really if we're going to have a service relying on this it shouldn't be in debugfs anyway.
1768988,2018-07-23 15:05:55 UTC,*********** MASS BUG UPDATE **************
1768988,2018-08-01 02:47:37 UTC,and how to disable secure boot ?
1768988,2018-08-01 13:00:47 UTC,This also happens on a Zenbook UX510UX with GeForce 950M.
1768988,2018-08-08 20:47:21 UTC,Seems this bug affects me even when uefi boot disabled in my bios. Or maybe i have another bug. 396 driver from ppa didn't fix that problem. Before I change default cart with sudo prime-select intel it looks like another fixed??? bug - https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1764005
1768988,2018-09-25 07:50:00 UTC,"/var/log/boot.log:         Starting dGPU off during boot...
/var/log/boot.log:[FAILED] Failed to start dGPU off during boot."
1768988,2019-01-29 16:24:50 UTC,*********** MASS BUG UPDATE **************
1768988,2019-01-29 17:23:54 UTC,Problem still reproducible on Fedora 29. With disabled secure boot everything is fine.
1768988,2019-02-17 17:28:14 UTC,Same here with Fedora 29 and kernel 4.20.7-200.fc29.x86_64. When secure boot is disabled everything works fine.
1768988,2019-05-08 19:54:00 UTC,"Hello,"
1768988,2019-08-20 17:36:46 UTC,*********** MASS BUG UPDATE **************
1768988,2019-08-21 08:40:26 UTC,"This was worked around in this switcheroo-control update:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-dd1633d7cb"
1768988,2019-08-28 22:32:31 UTC,This bug was fixed in the package switcheroo-control - 1.3.1-2
1768988,2020-09-05 18:46:38 UTC,This is not fixed on ubuntu for amd/nvidia configs.
1768988,2018-05-14 10:53:41 UTC,"(In reply to Laura Abbott from comment #6)

> As it stands, this is working as expected. When secureboot is on, debugfs is
> locked down. Per the patch, ""Normal device interaction should be done
> through configfs or a miscdev, not debugfs."" I think something needs to be
> done for vgaswitcheroo for secureboot.
"
1768988,2018-05-12 18:08:52 UTC,"Yup, I can confirm it affects 28 too."
1768988,2018-07-24 12:22:32 UTC,The problem is still persisten with the newer kernel (4.17.7-200.fc28.x86_64).
1768988,2018-05-05 03:30:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768988,2017-07-28 17:37:25 UTC,Description of problem:
1768988,2018-01-19 12:02:17 UTC,"Created attachment 1383341
systemctl status switcheroo-control.service"
1768988,2018-01-19 12:05:37 UTC,Have the same issue.
1768988,2018-05-05 04:11:24 UTC,See https://github.com/hadess/switcheroo-control/issues/12
1768988,2018-01-19 12:26:18 UTC,"(In reply to Bastien Nocera from comment #3)

> SELinux warnings?
"
1768988,2018-01-19 12:37:09 UTC,I'm going to say this is a kernel problem then.
1768988,2018-01-19 17:09:54 UTC,"As it stands, this is working as expected. When secureboot is on, debugfs is locked down. Per the patch, ""Normal device interaction should be done through configfs or a miscdev, not debugfs."" I think something needs to be done for vgaswitcheroo for secureboot."
1768988,2018-01-19 12:15:46 UTC,SELinux warnings?
1768988,2018-02-24 05:50:54 UTC,"This makes the option ""Launch using Dedicated Graphics Card"" in Gnome's right click menu disappear. So, to make use of the dGPU, I can only launch apps from terminal with the prefix, DRI_PRIME=1."
1768988,2018-03-23 08:33:13 UTC,Can confirm this.
1768988,2018-05-03 08:32:25 UTC,"This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'."
1768988,2018-05-03 10:29:46 UTC,This affects Fedora 27 too. Please update the ticket.
1768988,2018-05-03 11:22:07 UTC,"Can confirm that witcheroo-control service does not start correctly, but as soon as I disable secure boot it works fine and brings the menu entry ""Launch using Dedicated Graphics Card"" on Gnome back."
1768988,2018-05-03 11:36:01 UTC,"Correct, but that's just a workaround right ?"
1768988,2018-02-08 13:13:08 UTC,*** Bug 1543427 has been marked as a duplicate of this bug. ***
1768991,2018-05-04 06:19:22 UTC,apport information
1768991,2018-05-04 06:19:25 UTC,apport information
1768991,2018-05-04 06:19:26 UTC,apport information
1768991,2018-05-04 06:19:30 UTC,apport information
1768991,2018-05-09 12:38:11 UTC,i confirm this. the sound became dummy sound
1768991,2018-05-13 08:48:11 UTC,"i can confirm this on X99 Asrock Extreme4 board
sound became dummy"
1768991,2018-05-13 08:46:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768991,2018-05-04 06:19:19 UTC,apport information
1768991,2018-05-04 06:19:33 UTC,apport information
1768991,2018-05-04 06:19:15 UTC,apport information
1768991,2018-05-04 02:13:42 UTC,"I agree, that looks relevant:"
1768991,2018-05-04 06:19:08 UTC,apport information
1768991,2018-05-04 06:19:11 UTC,apport information
1768991,2018-05-03 23:03:31 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1768991,2018-05-04 02:16:31 UTC,"The same hardware is mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=189261, although it appears that's not what the original reporter of that bug has."
1768991,2018-05-03 23:03:17 UTC,This looks related:
1768991,2018-05-04 06:19:00 UTC,apport information
1768991,2018-05-04 06:19:03 UTC,apport information
1768991,2018-05-04 06:19:06 UTC,apport information
1768991,2018-05-04 02:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1768996,2018-09-14 13:52:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1768996,2018-09-14 14:14:10 UTC,Does not occur if the same share is mounted via NFS.
1768996,2018-09-14 14:15:23 UTC,NB: share also on a Synology NAS (DS916+)
1768996,2018-11-30 11:09:29 UTC,"I have a similar issue but some slight differences.  For example:
gio copy file.log smb://1.10.2.1/folder/
gio: file:///home/user/file.log: Network dropped connection on reset"
1768996,2018-12-01 07:42:03 UTC,I've been able to transfer files to my network drive through cifs.
1768999,2019-03-28 15:28:25 UTC,This sounds related to bug 1242717.
1769005,2018-05-17 09:20:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569066"
1769005,2020-03-23 13:43:00 UTC,"This is not a bug, as mentioned in the comments for the linked review, the tests call delete_containers method in TearDown, it's unlikely the containers wouldn't be cleaned. If you still have a feeling, that the resources are not cleaned properly, please, provide more information and reopen the issue. For now I'll mark it as invalid."
1769010,2018-05-04 01:41:52 UTC,Bionic will be addressed when Plasma 5.12.5 is SRUed. Other releases need explicit SRUs to them.
1769010,2018-05-04 01:48:50 UTC,Backporting the patch will take a bit of effort + time (that I don't have right now).
1769012,2018-09-07 15:50:18 UTC,"We have also seen this issue with asynchronous tasks and retries. If the execution is cancelled but an async tasks then fails, the retry logic will kick in and start up the task again inside the cancelled execution."
1769016,2018-05-15 13:06:54 UTC,"I had the same issue, I was also looking at nsswitch.conf but only after finding this post and adding the 'resolve' to that conf it started working normally. I had an other, custom vpnc-script and that one also worked but can't find it now"
1769016,2018-05-31 18:19:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769016,2018-05-31 18:20:40 UTC,"Same issue with OpenVPN, but my changes to nsswitch.conf seem to be ignored."
1769016,2018-05-31 18:32:56 UTC,"For some reason, libnss-resolve package was missing on my system. Now, it works as expected with the nsswitch.conf change."
1769016,2019-03-31 02:43:36 UTC,The necessary (for systemd-resolvd to work properly) package libnss-resolve is still not included with Ubuntu 18.04 nor Ubuntu 18.10 installs.  Manually adding the package fixed the name resolution problems on an otherwise unaltered installation using DHCP from a gateway.
1769016,2019-10-13 14:52:32 UTC,"If systemd-resolve's stub DNS resolver is used (which I believe is the case) then ""resolve"" directive is optional as DNS requests are routed to this stub resolver (per the ""standard"" nss-dns directive) which acts according to systemd-resolve's logic. I just wrote the above in the following comment – https://unix.stackexchange.com/questions/442598/how-to-configure-systemd-resolved-and-systemd-networkd-to-use-local-dns-server-f#comment1014165_516236"
1769021,2018-05-04 04:02:15 UTC,"@hongbin,"
1769021,2018-05-04 09:40:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566260"
1769021,2018-05-04 03:47:35 UTC,"@chenyb4,"
1769025,2018-05-09 22:31:43 UTC,"I'm not sure why you'd be hitting this, but there haven't been any changes around this code in a long time and we're not hitting this in CI, and if it were simply the instance.refresh() call then I'd think we'd hit it all the time."
1769025,2018-05-10 03:37:27 UTC,"Hi Matt,"
1769025,2018-05-10 16:38:12 UTC,"This is a nova change in stable/pike and the ironic CI job's nova-compute logs, I don't see any issue here:"
1769025,2018-05-10 17:54:39 UTC,"Hi Matt,"
1769025,2019-12-12 20:35:15 UTC,Is this still an issue? I'm inclined to mark this as invalid unless it can be recreated on a newer release.
1769029,2018-05-05 06:59:01 UTC,"Many bugs are now accumulating with this and similar issues surrounding Xorg. This is just one example https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug being fixed. It is damaging Ubuntu reputation."
1769029,2018-05-05 06:59:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769029,2018-05-07 09:45:38 UTC,"And  now it is working on Dell 1440x900. Thanks a lot for the immediate
support.
-VK Joseph"
1769034,2018-05-04 13:52:22 UTC,Thanks for the bug report.
1769036,2018-05-06 01:46:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769047,2018-05-04 06:32:11 UTC,Fuel Snapshot
1769052,2018-05-04 07:28:23 UTC,"To clarify, the issue is that storage attachment, like instance provisioning, is an asynchronous process.
The juju storage worker seems to be making a request for having storage attached, which returns ""yes, I'll get right on that"", but that only means the request was accepted. Not that storage will actually be successfully attached.
As a result of this, occasionally the storage fails to attach, but the Charm hook expects it to be there, and stalls waiting for it to show up, but 'juju storage' still thinks everything was successful."
1769052,2018-05-04 10:32:52 UTC,"in further conversation with James it is actually just never able to attach
that storage. Even poking Openstack to try again continues to fail. So
retry may not be worthwhile but having better visibility of failure to
attach is worthwhile"
1769053,2018-05-08 14:00:19 UTC,"* Gerd Hoffmann (<email address hidden>) wrote:

> Hi,
>
> >   d) For smaller amount of RAM it might still fail if
> > RAM+rounding+pci+hotplug space goes over the limit.
> >      Figuring that limit out is tricky (and I thought it
> >      might be BIOS/EFI dependent as well depending where they
> >      decide to put their PCI devices)
>
> Both seabios and ovmf try to not go too high in address space.  Reason
> is exactly the phys-bits issue.  Using 40 here by default does not only
> limit the memory to 1TB.  It also has the problem that the guest thinks
> it has 1TB of address space but in reality it might be less.  Even
> recent skylake machines have phys-bits=39 (512G) only, and trying to use
> the physical address space above 512G in the guest just doesn't work
> because the phys-bits=39 limit applies to EPT too.
>
> So checking phys-bits in the firmware, for example to place pci bars as
> high as possible in physical address space, is not going to work.
>
> IIRC ovmf uses a 32G sized region with 32G alignment by default, which
> will land below 64G (aka phys-bits=36 address space) unless the guest
> has more than 30 (q35) or 31 (piix4) GB of memory.
>
> seabios will not map pci bars above 4G unless it runs out of space below
> 4G.  If needed 64bit PCI bars will be placed right above ram, with
> gigabyte alignment.
"
1769053,2018-05-08 11:23:39 UTC,"* Daniel Berrange (<email address hidden>) wrote:

> Hmm, if we know that QEMU guests will crash & burn when > 1 TB mem, when
> host-phys-bits/phys-bits are unset, then perhaps libvirt should do the
> right thing by default here. eg we can't use host-phys-bits=true due to
> migration compat issues, but if we see > 1TB mem, libvirt could
> reasonably set phys-bits=NNN for some suitable value of NNN.  We should
> expose this in the XML config for the CPU explicitly too.
"
1769053,2018-05-08 13:22:34 UTC,"  Hi,"
1769053,2018-05-15 07:17:01 UTC,"Crit prio on Qemu which was explained to work just fine is not correct IMHO.
After checking with David he meant to want to raise the prio on the suggested libvirt extensions instead. I'm re-triaging this bug for that and will ping David Berrange if work on this is already tracked on a libvirt-BZ or worked on in general."
1769053,2018-05-08 10:26:46 UTC,"* ChristianEhrhardt (<email address hidden>) wrote:

> On Tue, May 8, 2018 at 10:37 AM, Dr. David Alan Gilbert <<email address hidden>
> > wrote:
>
> > * ChristianEhrhardt (<email address hidden>) wrote:
> > > > Interesting; I thought this was supposed to work.
> > >
> > > Exactly that was my thought when triaging it initially
> > > Furthermore I assume people working la57 (https://lwn.net/Articles/
> > 730925/) and such ran tests on much bigger sizes.
> >
> > I assume so, but I've not looked at the detail of that.
> >
> > > > Ah right Dan, if you're seeing the 40 bits physical in the guest you
> > > definitely need to try the flags I suggest in comment 6; host-phys-
> > > bits=true should work for you.
> > >
> > > I tested Bionic to be at least on libvirt 4.0 / qemu 2.11.1 when we want
> > > to check things under the ""supposed to work now"" flag.
> > >
> > > Defaults:
> > > Host:  address sizes   : 46 bits physical, 48 bits virtual
> > > Guest: address sizes   : 40 bits physical, 48 bits virtual
> > >
> > > I ensured that with option -cpu host,host-phys-bits=true set I
> > successfully get what my host can provide in the guest:
> > > Guest: address sizes   : 46 bits physical, 48 bits virtual
> > >
> > > Starting a guest with that >1TB (that would be mostly on swap if needed)
> > works just fine as expected. Here ~1063 GB from /proc/meminfo
> > > MemTotal:       1114676492 kB
> >
> > OK, good - that suggests there's nothing missing.
> > We enable host-phys-bits=true by default I think (in our machine type?)
> >
>
> Interesting approach, I see your comment about that already in [1] when it
> was added.
> I didn't realize some machine types were setting this already - I assume it
> isn't the general default for migratebility to other hosts (like our 36/39
> bit laptops).
>
> I assume ""we"" in this context are RedHat downstream changes to the (some)
> machine type(s)?
"
1769053,2018-05-15 07:41:18 UTC,"Description of problem:
Based on a discussion about Qemus ability to work with Guests >1TB [1] it was identified that it might be wise to have libvirt be able to:
  a) add a setting to the XML to specify the phys-bits
  b) It should be possible for libvirt to check the host it's on can
     satisfy that requirement (enough HW phys bits)
  c) libvirt can check that if RAM > 2^phys-bits it can complain"
1769053,2018-05-15 07:45:20 UTC,Reported to upstream libvirt's BZ with the suggestions of Daniel Berrage and David Alan Glibert; now available at [1] I linked that up in the LP bug status so that we auto-track this.
1769053,2018-06-11 09:30:41 UTC,Since all but the libvirt task to expose these are set to invalid in regard to the issue here I'm changing the title accordingly.
1769053,2018-05-15 07:19:30 UTC,"Actually the qemu tasks are ""invalid"" not ""incomplete"" as they currently are - after our discussions here it seems we agreed that qemu is doing what is intended (and the reasons why larger bits are not the default). Therefore set the status to that for the qemu tasks."
1769053,2018-05-08 09:57:34 UTC,"On Tue, May 8, 2018 at 10:37 AM, Dr. David Alan Gilbert <<email address hidden>

> wrote:
"
1769053,2018-05-08 10:48:28 UTC,"Hmm, if we know that QEMU guests will crash & burn when > 1 TB mem, when host-phys-bits/phys-bits are unset, then perhaps libvirt should do the right thing by default here. eg we can't use host-phys-bits=true due to migration compat issues, but if we see > 1TB mem, libvirt could reasonably set phys-bits=NNN for some suitable value of NNN.  We should expose this in the XML config for the CPU explicitly too."
1769053,2018-05-07 10:33:34 UTC,"> Interesting; I thought this was supposed to work.
"
1769053,2018-05-04 16:33:02 UTC,"Ah right Dan, if you're seeing the 40 bits physical in the guest you definitely need to try the flags I suggest in comment 6; host-phys-bits=true  should work for you."
1769053,2018-05-08 08:37:22 UTC,"* ChristianEhrhardt (<email address hidden>) wrote:

> > Interesting; I thought this was supposed to work.
>
> Exactly that was my thought when triaging it initially
> Furthermore I assume people working la57 (https://lwn.net/Articles/730925/) and such ran tests on much bigger sizes.
"
1769053,2018-05-04 16:19:48 UTC,"And with non-massive mem (so the guest actually boots up), the guest does show only 40 bits of phys mem addressing, so qemu will definitely have to increase that to be able to provide >1TB of phys mem to the guest (assuming qemu doesn't adjust that dynamically based on the total mem provided to the guest)"
1769053,2018-05-04 16:15:49 UTC,BTW this is the stacktrace I get from a Xenial guest on Xenial host:
1769053,2018-05-04 16:14:55 UTC,"You don't need a >1TB host to spin up a >1TB guest.  Unless you're using pci passthru (and/or SRIOV), or something else that requires qemu to alloc and pin all guest mem, you can simply overcommit; normal guests don't require mem pre-allocation or pinning."
1769053,2018-05-04 16:10:28 UTC,"Interesting; I thought this was supposed to work.
I know we (RH) have some downstream patches for >1TB RAM, but the last I'd heard they weren't supposed to be necessary any more, except for compatibility with old versions."
1769053,2018-05-04 08:12:04 UTC,"Thanks for your clarification Daniel, I'll mark both tasks incomplete then until you come back with that data."
1769053,2018-05-04 08:04:04 UTC,"Hi Christian,"
1769053,2018-05-04 07:44:10 UTC,"Hi Daniel,
might I ask what you expect now?"
1769053,2018-05-04 06:28:27 UTC,"(I'm not trying to start this on my laptop, so ignore the uploaded files. They're just what apport-bug decided to include.)"
1769056,2018-05-05 10:10:38 UTC,"CUPS generate non-globalized PPD in this context, so I believe it should put LanguageVersion/LanguageEncoding as follows the locale of strings, not hard-code to English/ISOLatin1."
1769056,2018-05-17 03:10:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769057,2018-05-08 17:03:28 UTC,"Hi Derek,
I fear that the crash only occurs some times. I don't see changes from 3899 to 3904 that could impact the problem."
1769057,2018-05-08 11:12:07 UTC,"crash occurs in 3904,"
1769057,2018-05-08 09:56:54 UTC,"crash occurs in 3930, but has gone away in 3095."
1769057,2018-05-05 18:33:21 UTC,"Hi Derek,
I must study whether I can create a test version for you, that provides some useful log data."
1769057,2018-05-05 09:30:44 UTC,"Hi Carlo,"
1769057,2018-05-05 08:30:37 UTC,"Bad error. Unfortunately I don't find in the logfile precise info about the code line that caused the crash (code line 5622 is the first of UpdateRouteActions, neither I easily find a place in that method where there is a conversion from Double to Int32. Is the crash repeatable? Was there a reversal point?"
1769057,2018-05-08 06:58:57 UTC,crash occurred with 4130
1769059,2018-05-04 16:17:53 UTC,"I believe that error refers to a read-only file system, perhaps that's why DKMS failed."
1769059,2018-05-09 16:08:37 UTC,Ubuntu 18.04 may not need fwts-efi-runtime-dkms as efi_test driver should be included in kernel.
1769059,2018-05-22 18:23:25 UTC,"Spew from ""modinfo efi_test"" :"
1769059,2018-05-30 00:56:39 UTC,"@jefchan,"
1769059,2018-06-07 04:46:11 UTC,"We may be able to use BUILD_EXCLUSIVE_KERNEL and BUILD_EXCLUSIVE_ARCH for the dkms, ex"
1769059,2018-06-08 03:50:47 UTC,"Currently all Ubuntu kernels that are not EOL include efi_test except 4.4. As a result, we can build & install the dkms only for kernel 4.4 such as below:"
1769059,2018-06-12 20:07:43 UTC,Fixed committed to repo
1769059,2018-07-09 23:33:03 UTC,The fix is removed from 18.06.2 because it fails ADT test. Please see more information @ LP/l1777855. This needs another proper fix.
1769059,2019-10-28 21:13:53 UTC,"Now DKMS are ready when UEFI Secure Boot is enabled, and it will prompt MOK key enrollment (see screenshot) when DKSM packages are installed."
1769062,2019-10-17 21:27:31 UTC,Link to change: https://github.com/juju/juju/pull/10578
1769062,2019-10-17 22:01:18 UTC,"The plain text output is done for ""juju call"" rather than run-action as we are concentrating on a holistic actions UX change for Actions V2, which can be accessed by setting the client side ""juju-v3"" feature flag. The existing actions UX is being left untouched for compatibility reasons."
1769062,2019-07-09 12:38:08 UTC,"Plain would indicate just outputing the content as a byte stream. (juju
run-action app create.zip --format=plain > foo.zip).
I would say if you have multiple units we could just concatenate them, or
disabling it would both be potential solutions."
1769062,2019-10-17 21:35:29 UTC,"Ian, just double checking. Does --format=plain disable the YAML output? Looking at the QA steps, callers would still need to interpret YAML in order to access the action's output."
1769062,2019-07-08 19:05:22 UTC,How do you recommend dealing with non-printable characters from the action?
1769062,2018-05-04 06:59:54 UTC,"(noted during a demo where actually getting everything to work nicely had lots of copy & paste and | jq and other workarounds, when it should just be a single command.)"
1769062,2019-07-08 19:06:55 UTC,Should --format=plain be disabled when multiple units are specified?
1769068,2018-05-04 22:41:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769068,2018-05-17 08:21:49 UTC,See https://github.com/projecthamster/hamster/issues/356
1769068,2018-08-11 20:23:53 UTC,"Looks like it was removed becaused it used older Gnome2 libraries, see bug 1739797 for details."
1769070,2018-05-08 12:28:18 UTC,"Most likely this is due to running some sort of ""sudo juju XXX""  (eg status) command.
You should never *need* sudo for any juju commands anymore (the only one you ever did was 'juju bootstrap' with juju 1.x).
There is already a bug about ~/.local/share/juju/* should not end up owned as root after a ""sudo juju *"" command. (We update those files with atomic replace, but I think we missed chowning them before replacing).
/tmp/* could be tried to be nice, but certainly we should give a better error message."
1769076,2018-05-04 07:38:09 UTC,"A potential solution is to avoid logon system when do snapshot , this will remove the requirements:"
1769080,2018-05-15 11:30:08 UTC,"3.13.0-148.197~precise1 - generic
Regression test CMPL."
1769080,2018-05-15 11:32:09 UTC,Child bugs for Trusty kernel are all marked as verification-done.
1769080,2018-05-22 11:33:10 UTC,All tasks have been completed and the bug is being set to Fix Released
1769089,2019-01-09 01:40:05 UTC,"Sudheer, Are you going through an load balancer of some type? This can sometimes lead to issues when using both HTTP and HTTPS, especially when logging in via one protocol then switching to the other."
1769089,2018-05-10 10:06:25 UTC,I am also getting the same error when I upload hot templates. The template I am using is
1769089,2020-01-20 16:12:58 UTC,"I've hit this same error in bionic-queens. I had to run ""juju run --app openstack-dashboard 'sudo service apache2 reload'"" for the issue to be fixed."
1769089,2018-05-04 11:24:35 UTC,Which release are you using?
1769089,2018-05-07 07:03:06 UTC,"Hello Akihiro,"
1769094,2018-05-04 09:07:30 UTC,"While this particular bug is known to still affect more recent versions of Ubuntu, please note that Ubuntu 17.04 has reached end of life and is no longer supported."
1769098,2018-11-20 08:29:32 UTC,That occur due to dpdk source not exist
1769098,2019-09-12 13:41:56 UTC,Does that bug still occur? Can you post fresh build logs from latest release?
1769098,2019-11-12 04:17:48 UTC,[Expired for kolla because there has been no activity for 60 days.]
1769118,2018-07-02 14:54:42 UTC,Indeed the hacluster charm does not re-asses the hanode relation in the event that the charm is upgraded.
1769120,2019-05-09 08:41:47 UTC,"given no activity, remove from oem-priority."
1769120,2018-05-31 15:21:21 UTC,"network module:
01:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter"
1769120,2018-05-04 11:30:12 UTC,This change was made by a bot.
1769120,2018-05-28 02:24:03 UTC,"@Taihsiang, how is the failed rate ?"
1769126,2018-07-02 03:01:01 UTC,"I found the solution, here:  https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1777268/comments/2"
1769126,2018-07-02 03:01:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769126,2018-07-03 15:14:17 UTC,I filed this bogie upstream @ https://help.brother-usa.com/app/ask:
1769126,2018-07-04 19:28:51 UTC,Solution given by Chris Rainey (ckrainey) on 2018-07-02 solves the problem for me. Thanks a lot
1769126,2019-02-16 08:57:50 UTC,I looked into this issue at length and posted a write-up here: http://forre.st/brother_printer
1769126,2019-02-16 17:21:47 UTC,@Forrest Voight:  Awesome write-up. Thanks!
1769127,2020-09-25 21:03:02 UTC,This bug was fixed in the package ubuntu-docs - 20.10.2
1769127,2019-12-17 13:28:01 UTC,Should have mentioned in the above - I found this because the upgrade process mentioned that several repositories were disabled during the upgrade and that this could be changed in Ubuntu Software. It was necessary for me to manually edit the contents of /etc/apt/sources.list.d instead. Maybe there is a separate bug to be filed on Ubuntu Software as well.
1769127,2020-09-12 22:54:07 UTC,Fix pushed to repo
1769127,2018-05-04 13:33:20 UTC,Thanks for your report!
1769127,2018-05-04 12:14:06 UTC,Thank you.
1769127,2019-12-17 13:11:03 UTC,I've just upgraded to 19.10 and the Ubuntu Software menu no longer contains that item. The instructions as given are now impossible.
1769131,2018-06-08 12:25:12 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1769131,2018-05-15 04:06:05 UTC,This issue was fixed in the openstack/nova 15.1.2 release.
1769131,2018-05-15 04:04:41 UTC,This issue was fixed in the openstack/nova 16.1.3 release.
1769131,2018-05-15 04:03:59 UTC,This issue was fixed in the openstack/nova 17.0.4 release.
1769131,2018-05-12 04:46:23 UTC,"Reviewed:  https://review.openstack.org/567630
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a16fa14ce47bd2d3a5189047e9bd330a607ef3cc
Submitter: Zuul
Branch:    stable/ocata"
1769131,2018-05-11 22:01:17 UTC,"Reviewed:  https://review.openstack.org/567625
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c72a0a7665e96219f0301525edc513dda07b320b
Submitter: Zuul
Branch:    stable/pike"
1769131,2018-05-10 20:43:58 UTC,"Reviewed:  https://review.openstack.org/566367
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e3385707cb1ced55cd12b1314d8c0b68d354c38
Submitter: Zuul
Branch:    master"
1769131,2018-05-11 02:52:03 UTC,"Reviewed:  https://review.openstack.org/567623
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=174764340d3c965d31143b39af4ab2e8ecefe594
Submitter: Zuul
Branch:    stable/queens"
1769131,2018-05-10 16:01:01 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/567625"
1769131,2018-05-10 15:39:31 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/567623"
1769131,2018-05-09 10:47:34 UTC,Follow on comment;
1769131,2018-05-07 09:35:53 UTC,"I tested this review in my environment, and with this code in place I could no longer reproduce the issue raised in bug 1769131"
1769131,2018-05-04 17:12:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566367"
1769131,2018-05-04 15:55:19 UTC,This is likely a side effect of the fix for bug 1728603 https://review.openstack.org/#/c/516395/.
1769131,2018-05-10 16:17:54 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/567630"
1769132,2019-07-31 11:03:23 UTC,Fix not fix the problem in LTS version. I have installed 2.8.1-2ubuntu2 version and i have same problems. (Ubuntu 18.04)
1769132,2019-07-31 10:56:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769132,2019-10-09 00:11:09 UTC,xenial version working fine.
1769132,2019-04-20 18:08:44 UTC,Unsubscribing the Ubuntu Sponsors Team as there is nothing to sponsor.
1769132,2019-01-14 13:50:46 UTC,"The new freetype version is in Ubuntu now, https://launchpad.net/ubuntu/+source/freetype/2.9.1-3"
1769132,2018-10-22 06:37:19 UTC,This is the upstream issue:
1769132,2018-10-22 07:21:57 UTC,"This is the patch that can directly put to ""debian/patches-freetype"" folder."
1769132,2018-10-22 08:18:59 UTC,"The attachment ""fix_bitmap_emboldening.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1769132,2018-08-28 15:57:21 UTC,That's what it seems like in firefox
1769132,2018-05-15 19:03:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769132,2018-09-15 10:46:00 UTC,"This bug affects multiple users, but why ubuntu do not upgrade freetype to 2.9.x?"
1769136,2018-05-04 13:22:46 UTC,"This issue is due to a failure to connect to Manager.
check the ""is_connected"" status through ""ovs-vsctl list manager"" command"
1769147,2020-07-02 18:09:03 UTC,"Looks updated to 0.21.4 in focal.  Thx, please feel free to close the issue repoirt."
1769149,2018-06-14 14:12:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769150,2019-07-09 15:06:59 UTC,Is this functionality be present also in Pcbnew?
1769150,2019-07-09 15:05:44 UTC,"I had analyzed the code and saw that in MAC-OS re-do is <Ctrl>+<Shift>+z and <Ctrl>+y in Linux and Windows.
Just to pointing, some software in my Ubuntu (such LibreOffice) use both hotkeys as re-do but, the most of them use just <Ctrl>+<Shift>+z."
1769150,2019-07-09 15:42:37 UTC,"@Hildo, no, I think long text blocks are much less likely there.  Still, we could do it there too...."
1769150,2018-05-08 18:07:45 UTC,This is a two-edged sword.
1769150,2019-07-09 11:21:24 UTC,"Fixed in revision 17d64ac348de4d583503f145717ffd19190afc3e
https://git.launchpad.net/kicad/patch/?id=17d64ac348de4d583503f145717ffd19190afc3e"
1769192,2018-05-04 15:56:13 UTC,"Bug report info added for the 'epiphany' package into the Gnome Bugzilla bugtracker. See ""Affects"" list at the top of the original Launchpad bug (https://bugs.launchpad.net/epiphany/+bug/1769192) or visit https://bugzilla.gnome.org/show_bug.cgi?id=795807."
1769193,2019-07-09 11:17:50 UTC,"@Seth, as it happens I was just moving this control to the Scintilla engine so it will handle cut/copy/paste and undo/redo.  I'll fix up the tab handling at the same time."
1769193,2019-07-09 16:06:54 UTC,"The formatting will be the same but it we'll need to do some more work to the dialogs before they accept the tab key.  Until then, you can paste tabbed text."
1769193,2019-07-09 15:09:40 UTC,"Nice, I will test in next Nightly.
Will be this feature be present also in Pcbnew? (Sometimes I put some tables in the board, for example, with the jumpers specifications)."
1769193,2019-07-09 11:21:21 UTC,"Fixed in revision 17d64ac348de4d583503f145717ffd19190afc3e
https://git.launchpad.net/kicad/patch/?id=17d64ac348de4d583503f145717ffd19190afc3e"
1769193,2019-07-09 13:39:56 UTC,"Cool, thanks Jeff!"
1769193,2019-07-05 20:05:21 UTC,"And, I see launchpad mangles the text, so copy/paste won't work but you can adjust in eeschema"
1769193,2019-07-05 20:04:26 UTC,Here's the text box that creates your example in eeschema.  Note the tabs between the columns and the spaces after the tildes
1769193,2019-07-05 19:55:25 UTC,"Fixed in revision 541d4358b8a832c0f0d80747ccc7f0fe56e0531a
https://git.launchpad.net/kicad/patch/?id=541d4358b8a832c0f0d80747ccc7f0fe56e0531a"
1769193,2019-07-09 03:28:51 UTC,"I tried to press <Tab> and the dialog just change the dialog object focus.
Also, I tried to add ""\t"" direct at the file and it doesn't worked.
Coping and pasting a Tab for other editor works fine and the file save a ""\n~\n"" to represent it. If I type ""<Enter>~<Enter>"", it is not converted to a Tab."
1769193,2018-05-12 12:07:14 UTC,Tabs won't solve the horizontal rule issue seen in the attached screenshot above.
1769193,2018-05-04 15:51:17 UTC,"This image shows how I am working around with this ""issue"".
Normally I use <space> to align the elements place in different lines. Using the <Tab> will allow me a better and uniformed space to each column."
1769194,2018-05-04 15:53:27 UTC,"I removed the dangling ""original"" symlink, and then ""apt-get -f install"" completed successfully."
1769194,2018-10-25 19:27:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769197,2018-05-04 16:00:07 UTC,This change was made by a bot.
1769197,2018-05-20 21:00:26 UTC,This issue was solved by deleting this Kconfig file manuallyKconfig
1769202,2019-10-18 15:19:58 UTC,"I've added the systemd service unit to the checkbox-ng deb package. The service now runs automatically after installation and running as root, it does not prompt for password."
1769206,2018-05-04 19:10:54 UTC,Problem solved
1769206,2018-08-29 01:17:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769206,2019-05-27 08:21:34 UTC,"It may be that @PG found a workaround, that doesn't mean the problem has gone away."
1769206,2019-05-27 13:28:29 UTC,"So, I don't think it's a network manager bug. It's the thing that's presenting the screen sharing dialog."
1769206,2019-05-27 20:35:47 UTC,"@PG, what netplan config did you have before?"
1769206,2019-07-27 04:17:32 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1769206,2019-10-24 12:18:24 UTC,Need help on same problem
1769212,2018-10-19 13:24:31 UTC,"It just happened again when I tried to view my subscriptions from the link in the bug email.
https://bugs.launchpad.net/launchpad/+bug/1769212/+subscriptions"
1769212,2018-10-19 04:18:04 UTC,[Expired for Launchpad itself because there has been no activity for 60 days.]
1769212,2018-08-13 09:00:30 UTC,"It's probably redirecting to a private page.  What's the exact URL that it redirects to, please?"
1769212,2018-08-19 14:27:55 UTC,"Sorry for the late reply.
It is redirecting to this URL:
https://bugs.launchpad.net/ubuntu/+source/ceph/+filebug/9f34119a-a3bb-11e8-a96e-68b5996a96c8/+login
That page simply displays:"
1769214,2018-05-27 05:41:32 UTC,"Hello again,"
1769214,2018-05-27 14:06:14 UTC,My guess is that it is the other way around: Arch just ships upstream whereas Debian and OpenSUSE manually bumped the pkg-config module version to indicate the incompatible API. I am wondering how they will reconcile this in the future? Hopefully SyncTeX will just bump from 1.21 to 2.0.
1769214,2018-05-27 13:21:38 UTC,It works perfectly! I guess that's just an Arch-specific quirk. Thank you very much for all the help and work on fixing this!
1769214,2018-05-27 06:33:49 UTC,"Hhhmmm, on Debian and OpenSUSE, it returns 2.0.0 to indicate the API change... I guess I will check for 1.19 instead. Can you give trunk revision 2078 a try?"
1769214,2018-05-27 05:55:08 UTC,"Sure - pkg-config returns 1.21.0, and I get the same on a clean build. Let me know if I can provide any other information or if there is any debugging I should try."
1769214,2018-05-26 23:47:01 UTC,"Hi! Arch Linux now has the updated texlive files (new libsynctex and texlive-bin 2018.47465-2). However, when I try to build qpdfview-bzr from the AUR, I get the following error:"
1769214,2018-05-04 23:08:29 UTC,"Hi Adam - as I understand it, Debian unstable has the new libsynctex and includes the header files missing on Arch, and so would work. I suppose a good test would be if the zathura development branch correctly compiles on that system, since the reason it fails for me on Arch is the missing file. Thanks for taking the time to look into this!"
1769214,2018-05-06 06:30:52 UTC,"Hello again,"
1769214,2018-05-06 01:32:42 UTC,"Will do! As of right now, I can successfully build, install, and run with the updated libsynctex package, which is great - thank you! Synctex seems to be disabled no matter what (regardless of what I pass to qmake). This is probably a problem with Arch's packaging, and I will check again once there is an update on their bug tracker."
1769214,2018-05-05 06:01:42 UTC,"Hello again,"
1769214,2018-05-04 18:15:02 UTC,"Hello Genevieve,"
1769214,2018-05-06 06:44:45 UTC,"Hello again,"
1769215,2018-05-04 17:56:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769215,2018-11-19 18:36:46 UTC,"Do you have any Python plugins in ~/.kicad_plugins or other plugin paths? pcbnew started crashing on me with Ubuntu 18.04 and now 18.10 when I install any plugins, works again after removing them. I've attached a gdb dump. I wonder if this is the same bug? Looking at this backtrace it seems like it might be something related to the status bar creation. I'm going to try building Kicad from latest source to see if I can figure out anything more."
1769219,2018-05-11 12:36:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769219,2019-07-03 10:43:26 UTC,Not quite enough detail to actually debug this problem:
1769219,2019-07-03 13:31:39 UTC,"Unfortunately, I am no longer working on the project where this bug occurred. It also seems to be something that was unique to our setup as no one else has reported this error in over a year."
1769219,2019-09-02 04:17:33 UTC,[Expired for ceph (Ubuntu) because there has been no activity for 60 days.]
1769224,2018-05-18 12:50:32 UTC,Following my previous comment :
1769224,2018-05-18 05:24:43 UTC,I would like to add the following information :
1769224,2018-05-08 20:22:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769224,2018-05-08 17:25:23 UTC,"This is correct, both keyboards appear in /etc/default/keyboard."
1769224,2018-05-08 07:25:33 UTC,"In my case, the two layouts are correctly available for choice. So that part is OK."
1769224,2018-05-07 23:44:44 UTC,Thanks for your report!
1769224,2018-05-08 14:11:56 UTC,"On 2018-05-08 09:25, Bodinux wrote:

> In my case, the two layouts are correctly available for choice.
"
1769231,2018-10-09 06:51:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769231,2018-10-09 06:54:38 UTC,The p2p-disabled flag is not supported until wpa-supplicant 2.5+.
1769234,2019-09-05 11:37:40 UTC,"This got fixed in one of the two previous releases with major reworks done, so marking this as 'fix released'"
1769236,2018-05-21 15:18:45 UTC,"This seems to have wrong temperature threshold issue. 64C is too low threshold.
What is the dump of the following:
#grep -r . /sys/class/thermal/*"
1769236,2018-05-21 15:27:41 UTC,Thanks for providing detailed logs. I see in the log:
1769236,2018-05-22 18:08:58 UTC,"Thanks for providing the dump. Unfortunately the Spectre system has bad thermal table values (Since Windows 10 is using more advanced tables, manufacturer didn't notice bad values impact.). So there may be more systems like this. So I want to implement some workaroud. Can you give me dump of"
1769236,2018-05-21 15:33:52 UTC,Can you also attach output of acpidump?
1769236,2018-05-19 21:52:30 UTC,Should this bug be reassigned to thermald?
1769236,2018-05-22 01:55:14 UTC,"I will attach acpi.out, and also the output of ""grep -r . /sys/class/thermal/*"" in grep-thermal.txt."
1769236,2018-05-22 17:19:18 UTC,"/var/run/thermald/thermal-conf.xml.auto will not be regenerated, if present, so you can edit."
1769236,2018-05-23 00:42:03 UTC,"No, /var/run/thermald/thermal-conf.xml.auto _is_ regenerated.  I tried editing it.  /var/run is a symbolic link to /run, which is a tmpfs."
1769236,2019-01-14 23:06:44 UTC,Seems similar to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730
1769236,2018-05-25 00:50:02 UTC,"I have pushed workaround for this. Please try the latest thermald
https://github.com/intel/thermal_daemon/tree/v1.7.2-test
This should show version 1.7.2 when you do thermald --version."
1769236,2018-06-01 01:54:42 UTC,"I tried thermald 1.7.2, and I can make it work for me, but I don't
think it is the best solution.  Please pardon the length at which I
explain my confusion."
1769236,2018-06-21 15:13:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769236,2018-11-18 15:14:28 UTC,According to:
1769236,2019-01-20 16:56:36 UTC,Would it be possible to include a newer version of thermald (was probably fixed in 1.7.2 according to release notes) in Ubuntu? I have a similar issue and it's quite annoying.
1769236,2018-05-19 21:49:20 UTC,"I will attach /var/run/thermald/thermal-conf.xml.auto, and
thermal.log (generated by sudo thermald --no-daemon --loglevel=debug)
to illustrate thermald's bad behaviour."
1769236,2020-08-14 05:30:06 UTC,I can confirm this bug is still there in Ubuntu 20.04 (and from what i did find it already exists at least 13 years!). I think this should get some priority.
1769236,2018-05-23 14:47:21 UTC,If /var/run points to tmpfs then you can't change. Let me update a new version of thermald by working around this issue. But you have to build it yourself and try.
1769236,2018-05-19 20:50:52 UTC,"With thermald stopped, and with the laptop displaying a desktop but not running any heavy loads, all 8 threads idle at 900 MHz, with all 4 cores typically running under 40°C."
1769236,2018-06-21 21:13:56 UTC,"Glen:
Thanks for good suggestions. I will consider for next revision."
1769236,2018-05-09 01:07:12 UTC,Upstream kernel 4.17.0-rc4 didn't change performance.
1769236,2018-05-14 08:30:15 UTC,"Is it possible that it's thermal throttled by thermald?
You can disable thermald by executing `sudo systemctl stop thermald`."
1769236,2018-05-07 15:45:45 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1769236,2018-05-08 00:58:39 UTC,"This was a fresh install, not an upgrade.  I have applied all updates made available since the installation, but performance has not changed."
1769236,2018-05-08 01:10:43 UTC,apport information
1769236,2018-05-08 01:10:46 UTC,apport information
1769236,2018-05-08 01:10:49 UTC,apport information
1769236,2018-05-08 01:10:51 UTC,apport information
1769236,2018-05-08 01:10:54 UTC,apport information
1769236,2018-05-07 16:00:34 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769236,2018-05-08 01:10:59 UTC,apport information
1769236,2018-05-08 01:11:02 UTC,apport information
1769236,2018-05-08 01:11:05 UTC,apport information
1769236,2018-05-08 01:11:09 UTC,apport information
1769236,2018-05-08 01:11:14 UTC,apport information
1769236,2018-05-08 01:11:17 UTC,apport information
1769236,2018-05-08 01:11:21 UTC,apport information
1769236,2018-05-08 01:11:24 UTC,apport information
1769236,2018-05-08 01:10:57 UTC,apport information
1769247,2020-12-06 09:54:21 UTC,I got a similar problem : Notebook and external monitor.
1769247,2020-12-06 09:42:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769247,2018-09-22 16:35:52 UTC,Possibly related reports:
1769247,2018-09-21 08:22:52 UTC,"Some applications may not support the primary option yet, so I do not think that this a bug in xfce4-settings which just enables it (equally to xrandr --output <display> --primary)."
1769247,2018-09-22 03:59:11 UTC,"The issue seems like it's really not xfce4-display-settings fault, but xfce4-panel and xfdesktop that do not respect the monitor chosen as the primary one."
1769248,2019-01-08 21:28:12 UTC,Marking Confirmed. It would be useful to have an option to mark the hold as Fulfilled rather than Cancelled for statistical purposes.
1769248,2019-01-09 15:17:46 UTC,"+1 from Bibiomation. I think most libraries would want to fulfill the hold, but I'm not opposed to retaining the option to cancel (as in, having 3 options in the pop up window instead of 2)."
1769253,2018-11-12 16:22:37 UTC,I can reproduce on Xubuntu as well
1769258,2019-07-05 15:36:19 UTC,This is fixed in eoan.
1769267,2020-01-07 16:03:14 UTC,"I've released a working version of rclonebackend.py, but am not happy yet."
1769267,2020-03-19 20:08:44 UTC,"Congratulations!  Very exciting.
C."
1769267,2020-01-07 19:46:19 UTC,"> 1) The renames are a real sticking point.  You can't 'rclone copy dir/a
> dir/b'.  Instead of copying to dir/b, it will create dir/b/a.  The
> renames are a point of confusion when debugging, especially with our
> Ctrl-C happy set of users.  I am investigating the use of 'rclone cat'
> at the moment.  That could be the solution.
"
1769267,2020-01-07 16:26:49 UTC,wrt. the license issue
1769267,2019-12-07 16:55:45 UTC,The license issue has been resolved.
1769267,2019-11-18 17:54:37 UTC,https://github.com/GilGalaad/duplicity-rclone
1769267,2019-11-18 20:42:49 UTC,"Yes, it needs a bit of work, especially conversion to Python 3.  I am
thinking that, with everything in the backends, here is a product built for
talking to all the remotes we have, and then some."
1769267,2019-02-23 04:02:07 UTC,Could we simply support rclone as backend by integrating https://github.com/GilGalaad/duplicity-rclone into duplicity upstream?
1769267,2018-05-07 17:07:49 UTC,"Hi Ken,"
1769267,2018-05-07 15:09:57 UTC,rclone looks good.  Will have to investigate further.
1769267,2019-11-18 21:54:25 UTC,"One possible show-stopper, duplicity is under GPL v2, rclonebackend.py is under GPL v3.  I don't think we can arbitrarily mix the two licenses.  Thoughts?"
1769270,2018-05-05 06:49:42 UTC,"Many bugs are now accumulating with this and similar issues surrounding Xorg.  This is just one example https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others.  Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug being fixed.  It is damaging Ubuntu reputation."
1769270,2018-05-05 06:51:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769281,2018-05-07 16:33:33 UTC,I confirmed this during an upgrade from Artful to BIonic.
1769281,2018-05-07 16:46:03 UTC,"Hi Brian, Jonathan,"
1769288,2018-05-05 13:07:18 UTC,"So, it seems the root is that Japan uses ISO dating typically, even handwritten, and the new default uses not ISO, and there's no GUI option to set it as such.  Not so much a bug as a design choice."
1769288,2018-05-05 13:02:53 UTC,"Hey, from https://askubuntu.com/questions/237941/how-to-configure-the-clock-date-format-to-iso-8601-in-unity"
1769297,2018-05-05 05:11:26 UTC,How to check you have this issue:
1769297,2018-05-05 05:17:40 UTC,Here is a fix for this bug. This makes hibernation functional for me.
1769297,2018-05-05 05:20:04 UTC,"This bug is actually a regression. I remember hibernation was functional around a year ago in ubuntu 17.04 with any kernel, but at some point it became broken. Probably in 17.10."
1769297,2018-05-05 12:44:55 UTC,"The attachment ""init.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1769297,2018-05-09 15:39:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769297,2018-09-08 23:39:03 UTC,"FWIW, installing initramfs-tools(-core) 0.132 from Debian buster/sid fixed this for me. Both direct download and a build from source worked."
1769297,2018-12-20 08:40:43 UTC,Reached to this bug because of a similar issue we were able to resolve using information here.
1769297,2019-03-19 20:10:09 UTC,@Dmitry where would I set this resume= parameter?
1769300,2018-09-28 02:41:02 UTC,I can not reproduce this issue.
1769300,2018-09-28 03:00:07 UTC,"It started working 2-3 months ago. I'M not sure if it was after the weekly
upgrades or if it was something on my part."
1769301,2019-07-29 16:05:04 UTC,"I'm sorry but I have no access to the system any longer, therefore I cannot the command."
1769301,2019-07-29 15:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769301,2018-08-24 07:49:01 UTC,"I've asked a question on stackexchange.com, but still no answer. There is a detailed description and some logs.
https://unix.stackexchange.com/questions/458853/useradd-groupadd-fails-failure-while-writing-changes-to-etc-passwd-and-etc-gr"
1769301,2018-05-05 08:16:18 UTC,It looks that the root cause affects multiple packages.
1769301,2018-08-23 17:39:57 UTC,"Got the same problem. It looks like the problem is in the kernel 4.15 with Canonical patches. Vanilla 4.15, built from source, has no problem with useradd. Ubuntu 16.04 LTS kernel 4.13 generic, built from source, is also  ok. I've spent plenty of time trying to make it work."
1769301,2018-05-05 08:18:13 UTC,In libselinux the setfscreatecon() function is implemented - which might be the root cause of the problem.
1769301,2018-08-24 06:29:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769303,2018-05-05 08:41:25 UTC,Thanks for reporting.
1769303,2018-05-05 17:55:17 UTC,"Dear Hans,
Thanks for getting back to me and troubleshooting. Much appreciated.
I am only a scientist but not a developer.  But is there anyway I can help.
Best,
Raad Nashmi"
1769303,2018-05-13 09:14:12 UTC,"I found that scidavis has started working on QT5 support https://sourceforge.net/p/scidavis/scidavis-feature-requests/101/ , though the main part of that will be ""developer activities"". Of course, once that is in place, testing the new version will be helpful, and there may also be some process around getting the package re-added to Debian and Ubuntu archives."
1769303,2018-05-15 05:00:47 UTC,"Hans,
Thank you for that update.
Raad"
1769303,2018-10-22 07:53:05 UTC,Scidavis is also not available in Ubuntu 18.10.
1769303,2018-10-22 07:53:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769304,2018-11-23 20:21:16 UTC,This is fixed in bionic and later. Leaving a task open for xenial.
1769304,2018-11-23 20:22:01 UTC,Would be good to have a simple test case for this bug.
1769314,2018-05-10 11:19:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1769315,2018-10-08 21:18:13 UTC,Please reassign it to analytics team. Thanks!
1769316,2018-05-05 14:29:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769316,2018-05-08 10:08:41 UTC,The problem is that synaptic launches software-properties-gtk has root. Marking as low considering that synaptic is not officially supported.
1769322,2019-01-18 12:06:58 UTC,"I think this is the same bug
https://gitlab.freedesktop.org/libinput/libinput/issues/176"
1769322,2019-01-18 11:55:16 UTC,"No typo. I'm experienced this bug before on default libinput 1.10.4-1. Then I'm installed latest version using dpkg (libinput-bin_1.12.4-1_amd64.deb, libinput10_1.12.4-1_amd64.deb) to see if it's fixed. And it doesn't. Same jumpy behavior. Only difference that I'm noticed is slightly increased sensitivity."
1769322,2020-04-15 13:29:33 UTC,I see also this problem on my Thikpad T495 on Ubuntu 18.04 and 20.04:
1769322,2019-01-18 01:24:08 UTC,Is that a typo? There's one character difference:
1769322,2019-01-17 23:20:14 UTC,"Same problem. Thinkpad t440p, Ubuntu 18.04 bionic.
libinput version - 1.12.4-1"
1769322,2018-09-30 10:09:45 UTC,"Same here, on Thinkpad T440, bionic."
1769322,2018-09-23 22:50:54 UTC,Same problem on Thinkpad P50
1769322,2018-09-10 10:22:29 UTC,Same problem for me with the trackpoint on Thinkpad T520i
1769322,2019-01-18 01:26:11 UTC,"Also, if anyone does experience this bug in libinput version 1.12.x then please help by reporting the bug upstream here:"
1769322,2018-06-20 16:45:14 UTC,"Actually, I confused trackpoints with trackpads. Indeed, there's no fix for trackpoints yet."
1769322,2018-06-20 14:07:24 UTC,This is probably (I'm 99% certain) fixed in libinput 1.11 for good. It's now on par with Windows/macOS.
1769322,2018-06-20 00:58:23 UTC,Related or duplicate: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1773276
1769322,2018-05-09 02:22:10 UTC,"OK. I've heard a few complaints about Trackpoints recently so have started to group them here:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bugs?field.tag=trackpoint"
1769322,2018-05-08 15:48:57 UTC,"Having the same issue, my cursor jumps when moving short distances."
1769322,2018-05-08 11:33:46 UTC,"thanks for the hint. I installed the newest version of libinput-bin ""libinput-bin_1.10.6-1_amd64.deb"" and the behavior did inprove but it does still not work flawlessly. The cursor still jumps somethimes especially if moved a short distance."
1769322,2018-05-07 02:00:53 UTC,"I believe this is already fixed upstream, at least for T450s:"
1769322,2018-09-06 17:12:37 UTC,Same problem on Thinpad X1-Carbon 4
1769327,2018-05-05 17:21:16 UTC,"[   51.051610] vboxdrv: loading out-of-tree module taints kernel.
[   51.052105] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[   51.071714] vboxdrv: Found 4 processor cores"
1769327,2018-05-05 17:22:36 UTC,"Steve, do you think this might be related to the new dkms changes? ""required key missing"" it seems..."
1769327,2018-05-05 18:07:45 UTC,"Almost certainly related.  Return code 30 strongly suggests a debconf error.  I'm currently traveling and unable to look in detail, perhaps Matt can have a look in the meantime."
1769327,2018-05-07 22:38:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769327,2018-05-09 08:08:32 UTC,"Mathieu, what do you think about this issue?"
1769329,2018-07-28 11:44:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769330,2018-10-23 20:47:36 UTC,I just found the bug in Ubuntu. Maybe this is a duplicate of bug #1769654
1769330,2018-10-23 20:38:12 UTC,"This may be due to this fonts-liberation bug, first noted in LibreOffice, and fixed in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898116"
1769330,2018-06-25 18:42:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769330,2018-05-18 09:11:27 UTC,Installing fonts-liberation 1:1.07.4-6 fixes the issue.
1769330,2018-06-25 18:41:43 UTC,"have the same issue, somehow it was also affecting the font highlighting inside anki for CJK languages, and caused vertical ""cut-offs"" for glyphs
fixed it by using fonts-croscore package instead of fonts-liberation"
1769333,2018-05-26 12:37:53 UTC,Hello.
1769334,2018-05-12 09:44:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769338,2018-05-05 11:48:13 UTC,"root@ubuntu:~# ubuntu-drivers list
nvidia-driver-390
root@ubuntu:~#"
1769338,2018-05-05 11:49:04 UTC,"If I click Cancel and select nvidia and apply same problem, stays there forever."
1769338,2018-05-07 23:10:02 UTC,If you are using Ubuntu 18.04 please try the version of software-properties from the bionic-proposed pocket. See bug 1753333 for detailed instructions regarding enabling and using -proposed.
1769338,2018-05-09 21:04:17 UTC,"Ok waiting for update, already on bionic-proposal."
1769339,2018-08-31 23:13:55 UTC,"Same issue.  I've used System Load Indicator for several years, on all my Ubuntu installations.  I really miss it, so I hope this gets fixed soon!"
1769339,2018-08-16 10:33:27 UTC,I have just discovered this add-on and likewise have the issue of the size adjustment not working.
1769340,2018-05-05 16:25:23 UTC,"I think that the mate-panel is behaving correctly here, as it should not get smaller than its widgets allow. Sounds like the global menu itself is not capable of being smaller than 27 pixels. I don't have the global menu, but with mate-menu, mate-dock-applet, and indicators, my panel cannot get smaller than 28px. I'm personally fine with this, but maybe we should take a look at the global menu to see if it's possible to change it so that it's smaller. Maybe smaller fonts could help?"
1769340,2018-05-05 17:07:37 UTC,"> as it should not get smaller than its widgets allow
"
1769341,2019-10-06 03:14:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769346,2018-05-05 13:20:21 UTC,"If I run the ""install the system"" process a second time immediately afterwards, it passes without errors/warnings but after installation when system restarts:"
1769346,2018-05-14 21:40:42 UTC,Confirming that I get this same error on a fresh new install of 18.04 server. Not sure why there's a reference to i386 since this is a 64-bit server installation.
1769346,2018-05-16 13:24:24 UTC,"I fixed this error by updating my BIOS. Weird - I didn't have this issue with prior versions including 16.04.4 but when I also tried 16.04.4, I got the same problem. I might have been using an earlier 16.04.x where this wasn't an issue. But again, in the end, the BIOS did the trick."
1769347,2018-05-14 09:12:49 UTC,"Hi Dean,"
1769347,2018-05-09 15:23:39 UTC,Hi Shivani
1769347,2018-05-08 12:18:12 UTC,"Hi Dean,
Can you please attach the below log files for further analysis?
1)output of hp-check -rt
2)cups log
path : /var/log/cups/error_log
To enable cups log, go to /etc/cups/cupsd.conf and change loglevel from warn to debug2 in cupsd.conf file and then restart the cups using the command: sudo service cups restart
3) system log
path : /var/log/syslog"
1769348,2018-05-06 13:23:55 UTC,"Having the same problem here too, I upgraded from 17.10."
1769348,2018-05-06 14:17:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769348,2018-05-09 10:19:20 UTC,Also affects me.
1769348,2018-05-10 06:45:26 UTC,I am facing this issue too. looking forward to have the fix for this soon.
1769348,2018-05-12 17:18:23 UTC,Discussion on the issue with the Ubuntu 18.04 distro release: https://github.com/FreeRDP/Remmina/issues/1584
1769348,2018-05-12 19:39:11 UTC,"The workaround is to choose a Color Depth which does not require H264 (GFX RFX, RFX, 32bpp or 16bpp, or one which works), save it as default, save the profile and connect."
1769348,2018-10-06 09:25:15 UTC,"I have the same problem, after upgraded to 18.04 from 16.04"
1769348,2018-10-08 07:02:29 UTC,Please try this fix till they add any support. Go to remmina -> (+) button -> basic (tab) -> set 'color depth = 256 colours (8 bbp)'.
1769352,2019-09-12 13:43:09 UTC,Is this still a bug? Can you please reproduce? If not - bug will expire in 60 days.
1769352,2019-11-12 04:17:49 UTC,[Expired for kolla because there has been no activity for 60 days.]
1769352,2018-05-05 15:32:55 UTC,suggested change - https://review.openstack.org/#/c/566438/
1769353,2018-05-09 19:59:07 UTC,"This issue started for me just after I upgraded to Ubuntu Mate 17.10 from 16.04. It also occurs in 18.04. Right after installing chrome remote desktop and then sharing your computer with chrome remote desktop everything works just fine. You can even remotely log into your computer. Unfortunately, the first time you reboot, you are greeted by ""Could not acquire name on session bus"" error message right after login."
1769353,2018-05-10 00:58:35 UTC,"thank you, it worked perfectly. I could not imagine that the problem would be chrome remote."
1769355,2021-01-11 21:48:16 UTC,"I tried to recreate this bug, but didn't get the dialog when exporting a deleted file. The command log will however note that the file was missing. I looked through the code and it appears that missing files will automatically be skipped over. Is the bug more about now having a UI dialog pop up that let's the user know the file is missing?"
1769355,2021-01-11 22:44:02 UTC,"Yes, that would be nice!"
1769355,2021-01-12 20:45:30 UTC,The notDeletedDlg box you created seems analogous. Will try and recreate it. Thanks for the tip!
1769358,2019-04-23 09:01:46 UTC,"> I don't know if Gnome will accept it, or what the process would be to include it in Ubuntu
"
1769358,2018-05-05 20:48:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769358,2019-01-30 23:01:51 UTC,"That's known upstream, https://gitlab.gnome.org/GNOME/nautilus/issues/398"
1769358,2019-04-20 03:57:35 UTC,"OMG... just spent one hour trying to ""debug"" the issue, when it is an intentional change by Gnome... I hope they revert this, or that Ubuntu can override this setting."
1769358,2019-04-20 17:38:45 UTC,"I created a fix for this, with a new configuration option. I uploaded a diff here: https://gitlab.gnome.org/GNOME/nautilus/issues/398#note_493737"
1769362,2020-08-06 14:04:00 UTC,"I have the opposite problem.
When the laptop is docked into a docking station connected to an external monitor, lightdm login screen does not show on the external monitor unless I open the laptop lid, in which case the login screen appears on both, but of a smaller size on the external screen that has a higher resolution."
1769363,2019-05-28 11:20:09 UTC,"Eva, your situation is different, if there's not already an 008 in the record editing the fixed field grid at the top of the record doesn't cause one to be inserted, so that's why the values you enter are just lost. If you add an 008 (even if it's entirely empty) then editing the grids at the top will work as expected. Making the fixed field editor smart enough to insert a new 008 if there isn't one present would be a good bug if one hasn't already been entered."
1769363,2019-05-24 12:36:55 UTC,"I am not sure if my observation refers to the exact same problem:
We were unable to add value to fixed field in some incorrect bib records, that did not have had created corresponding field before. E.g., we were not able to save the country code to field 008 using the grid or MARC text editor - the value always disappeared after saving. However, if the field had been created using right click option ""Add 008"" and then the value was added, the value was saved.
The behavior was the same in the web client of 3.1.4 and 3.3.0."
1769372,2018-05-07 10:20:28 UTC,Dear Daniel!
1769372,2018-05-09 12:31:13 UTC,"OK, Jeremy!"
1769372,2018-05-09 12:09:41 UTC,"Norbert, the upstream bug is https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/46"
1769372,2018-05-09 10:17:17 UTC,"I do not understand about ""confusion"" and ""intersection"".
Will this fixed or not in Ubuntu 18.04 LTS?
Or GNOME will continue to reinvent of new unique interaction mechanisms between user and desktop?"
1769372,2018-05-09 02:03:08 UTC,"OK, as is the pattern this week, the confusion here is the intersection of two different bugs. Not one."
1769372,2018-05-08 02:15:03 UTC,"Also, the bug applies to real machines too. So I removed mention of VMs."
1769372,2018-05-08 01:40:18 UTC,Please read: https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/39
1769372,2018-05-07 12:43:38 UTC,I'm closing the gnome-control-center side of this issue since I believe that it's gnome-settings-daemon that is responsible for the different behavior in virtual machines.
1769372,2018-05-07 11:45:50 UTC,Note 1: Problem exists with both VirtualBox 5.1.36 and 5.2.10 (guest additions and extpack are installed and have corresponding versions). Ubuntu 16.04.4 LTS amd64 is a host.
1769372,2018-05-07 11:18:29 UTC,Upstream bug report - https://gitlab.gnome.org/GNOME/gnome-control-center/issues/85 .
1769372,2018-05-07 10:08:12 UTC,apport information
1769372,2018-05-07 10:08:10 UTC,apport information
1769372,2018-05-07 10:08:08 UTC,apport information
1769372,2018-05-07 08:45:26 UTC,"And a fix for gnome-control-center is here:
https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/39"
1769372,2018-05-07 08:37:04 UTC,"More weird; the GUI does contain the feature you want, but upon looking at the source code I found it is just named incorrectly:"
1769372,2018-05-07 01:57:59 UTC,"We also need a GUI enhancement to gnome-control-center to expose the setting, which already exists."
1769372,2018-05-07 01:55:54 UTC,Here's a fix :)
1769372,2018-05-07 01:53:48 UTC,"Oh! The schema does support it already (""interactive""):"
1769372,2018-05-07 01:49:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769372,2018-05-07 01:48:55 UTC,The default action is suspend:
1769372,2018-05-06 14:59:04 UTC,I posted my analysis in AskUbuntu question ( https://askubuntu.com/q/1032461/66509 ) .
1769372,2018-05-13 14:37:14 UTC,I am bumping the importance of this bug based on the new test case I added to the GNOME bug today.
1769372,2020-05-20 21:03:15 UTC,It is absolutely expected that this bug exists in 20.04 LTS. Will not use GNOME Shell on VirtualBox.
1769373,2019-01-11 17:05:24 UTC,"I only used it for recovering data from my old home volume, so I had mount it only once and then deleted it.
I don't use eCryptfs anymore."
1769373,2019-01-11 12:33:33 UTC,Thanks for the patch!!
1769373,2019-01-11 13:20:12 UTC,"You are welcome, but **beware, it is not a clean/proper solution**, just a hacky way to get to your data, that I discovered empirically,  with a little luck using some general linux/bash knowledge."
1769373,2018-05-05 17:09:04 UTC,"p.s.: The snippet in comment #2 is representative, NOT the exact patch addition!"
1769373,2018-05-05 19:40:50 UTC,"First patch did not work after rebooting from the live image.
Created new patch with a hack that I needed: a step that I did manually before creating the first patch."
1769373,2018-05-05 16:41:07 UTC,# Patch
1769384,2018-05-05 17:23:08 UTC,Note that the attached modified pam.d/sddm and pam.d/sddm-autologin files are the result of my attempts to fix the problem. The problem exists with the original files.
1769384,2019-06-11 02:02:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769384,2019-06-11 02:08:13 UTC,"Can confirm that SDDM has trouble unlocking the default keyring. While it always seems to unlock it after a cold boot, at some point trouble arises when logging out and back in again, along with after resuming from suspend / hibernate. In those situations, the keyring remains locked far more often than not. I am experiencing this under Lubuntu 19.04. The issue has been occurring both before and after I migrated data over from an install of Ubuntu Xenial. I have not made changes to sddm configs, as the other user who filed this bug has."
1769385,2018-05-05 17:29:48 UTC,"This error dialog box appeared twice - first, when Apport was collecting information and second right after I pressed Yes on the first one."
1769386,2018-05-05 17:30:52 UTC,"*-network
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0.1
       bus info: pci@0000:02:00.1
       logical name: enp2s0f1
       version: 12
       serial: 80:fa:5b:3e:45:e2
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8411-2_0.0.1 07/08/13 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
       resources: irq:124 ioport:e000(size=256) memory:df114000-df114fff memory:df110000-df113fff
  *-network
       description: Wireless interface
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: wlp3s0
       version: 78
       serial: 00:28:f8:81:66:ef
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=4.13.0-39-generic firmware=31.560484.0 ip=192.168.1.2 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:127 memory:df000000-df001fff
maj@maj-N750BU:~$"
1769386,2018-06-24 08:26:30 UTC,"The network card worked at fist xenial setup by the way, few months later an update
made network card unusable"
1769386,2018-07-13 17:23:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769386,2018-07-20 20:08:34 UTC,"I think I have the same issue on my nettop using ""Pegatron RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"". It doesn't work out of the box on neither Ubuntu Server (bionic) nor Arch, but I used to run Ubuntu Server on this hardware around a year ago without any problems."
1769386,2018-07-25 04:07:00 UTC,Same as LP: #1779817?
1769386,2018-07-25 05:39:54 UTC,"@6 for me its not related to suspend..it just has stopped working all the time, even after reboots
so not related your bug?"
1769386,2018-08-01 12:03:04 UTC,"After a fresh install of 18.04 Bionic, my USB wireless adapter didn't show up. Running 'lsusb' provided the device ID for the adapter as 0bda:a811 Realtek Semiconductor Corp. Cross-referencing that ID with 'Ubuntu 18.04' I eventually fell down the rabbit hole at askubuntu.com and landed here: https://askubuntu.com/questions/970283/ubuntu-17-10-drivers-not-found-working-properly"
1769386,2018-08-16 17:07:27 UTC, FIX Updates 16.04.5 @ 16/8/18 made the realtek chipset work again kernel 4.15
1769388,2018-05-06 19:49:09 UTC," I removed the problematic library and I have not had any problems for now. We will see with the subsequent updates how everything will work.
#  sudo apt remove libp11-kit-gnome-keyring"
1769390,2018-05-05 19:46:15 UTC,"If you know what icon name that is and where it should be added we will be
happy to add it to the pocillo iconset."
1769390,2018-05-18 05:08:09 UTC,"Same issue was in 17.10, sorry I did not report a bug.  Is there a way to set it to what ever the menu icon for chrome is set to?"
1769390,2018-05-18 05:19:10 UTC,"Hmm, I am under the impression that the facebook notification should show the profile picture of the one the message or whatever is from?"
1769390,2020-03-20 15:08:12 UTC,"Hello from 2020,"
1769390,2020-03-20 15:19:15 UTC,"The ""update"" is that nobody has come forward with a solution"
1769390,2020-07-02 05:59:59 UTC,"Im here looking for a solution, I even went to the solus forums, to see if someone had come up with a solution :'v and I realized that uncle foss is a great man :'v"
1769391,2018-11-24 01:06:31 UTC,I have the same problem.  HP Pavillion G7.
1769391,2019-06-01 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769391,2019-06-04 05:04:46 UTC,Does this issue still happen?
1769391,2019-09-23 04:19:27 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1769394,2018-05-24 15:32:41 UTC,"I have found a possible workaround: when you make a textbox (hold text tool and drag) and then type and hit enter, Inkscape does not crash."
1769394,2019-04-22 04:17:13 UTC,https://bugs.launchpad.net/inkscape/+bug/1768958/comments/23
1769394,2018-05-08 11:58:52 UTC,"Related bug report in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1575842"
1769394,2018-05-08 11:27:02 UTC,"You are right. I opened a new document, used the Text tool and entered some text, after I hit Enter for a new line, Inkscape crashed."
1769394,2018-05-07 21:20:39 UTC,Fedora sure seems to have a problem with multiline texts. There are several reports that describe similar issues with text on Fedora 28.
1769394,2018-05-06 00:30:58 UTC,Forgot: could you please attach the crash log directly to the report?
1769394,2018-05-06 11:30:29 UTC,"Yes, it was created in the previous version ""0.92.2 (5c3e80d, 2017-08-06)"", and it did not crash at any point of use. After the Fedora upgrade 27 > 28, Inkscape got updated too and these particular files started crashing Inkscape. Other files that I've tested seem to work fine."
1769394,2018-05-06 11:08:14 UTC,"Thanks for sharing, Thee."
1769394,2018-05-06 10:24:43 UTC,"I've found another SVG file that causes the same crash, this one is not large but it has a lot of text in it (in German), so you might be right that the text is the cause of this crash."
1769394,2018-05-06 00:30:13 UTC,It seems to have to do with the text in the file.
1769394,2018-05-06 12:02:03 UTC,"- crash not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1769396,2018-06-11 06:18:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769396,2018-11-18 15:34:47 UTC,Is there a patch for this bug yet?
1769397,2019-02-01 03:46:42 UTC,"I filed a Debian bug for this at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921046, since that's what I'm actually using. In that bug I included a patch to hw/xfree86/drivers/modesetting/drmmode_display.c in the xserver-xorg-core package that fixes the issue for me."
1769397,2019-02-01 01:49:19 UTC,"I ran Xorg in gdb and captured a backtrace of a crash using a script similar to the one in the ""Debugging with one machine"" section of https://www.x.org/wiki/Development/Documentation/ServerDebugging/"
1769397,2019-01-09 11:05:42 UTC,"I use Kubuntu 18.04 LT and also suffer from this problem. I tried the .deb from
http://openartisthq.org/easystroke/easystroke_0.6.0-0ubuntu8_amd64.deb
but the problem persists. I am using three displays.
So far, the easiest way to reproduce the crash was to right click on the task bar and open Task manager settings."
1769397,2018-12-04 22:39:45 UTC,It seems like easystroke on ubuntu is still built from 0.6.0 release and not from master.
1769397,2018-11-08 12:11:05 UTC,I can reproduce crash using Jorge Cardoso steps in Ubuntu 18.04 / Xfce / Dual Monitors.
1769397,2018-10-23 18:55:58 UTC,"I can confirm Jorge Cardoso, using 18.04 with Intel Corporation Mobile GM965/GL960, and unity (gnome crashed as well), dual monitor, and Easystroke."
1769397,2018-08-28 13:58:58 UTC,"I am seeing similar crashes on Kubuntu:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1778233"
1769397,2018-08-10 18:58:57 UTC,This sporadically happens to me when performing a copy (ctrl-c) or paste (ctrl-v) gesture.
1769397,2018-06-20 09:33:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769397,2018-06-20 09:32:21 UTC,"The same happens with 18.04 (default using gnome). Sometimes it happens as described, sometimes ubuntu freezes. It sometimes happens right after you perform a gesture."
1769397,2018-05-05 20:37:36 UTC,"Ubuntu-MATE bug report:
https://bugs.launchpad.net/ubuntu-mate/+bug/1769399"
1769397,2018-09-03 21:59:00 UTC,In my case Xorg crashes under the following conditions:
1769398,2018-05-05 20:29:49 UTC,"Am using ubuntu 16.04 with cairo dock
having problems with gnome tweak tool font not sticking to the set font i want it keeps going bigger and smaller from time to time"
1769398,2018-05-11 17:45:03 UTC,"Hi i reported a bug last week about fonts in ubuntu 16.04 not sticking, after changing settings in tweak tool. the fonts keeps changing every 10-20 mins while working on the laptop i dont know why
please kindly assist in fixing this problems."
1769400,2018-06-06 15:05:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769402,2018-05-05 21:34:38 UTC,Also missing is dependency on package python3-protobuf and python3-axolotl (or python-protobuf and python-axolotl for Python 2)
1769402,2018-05-05 21:36:42 UTC,"Note that for the registration, the error"
1769402,2018-05-05 21:15:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769406,2018-05-06 23:27:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769406,2018-05-06 23:27:33 UTC,"The PasswordSafe Github site (https://github.com/pwsafe/pwsafe) has version 1.05BETA on it, and when built from master HEAD it shows the tray icon (at least with the Ubuntu appindicators extension installed)."
1769406,2019-11-02 20:43:07 UTC,"This is fixed in more recent versions of Password Safe, including the one currently shipping with Disco and Eoan.  This can be closed."
1769411,2018-05-07 01:45:12 UTC,">
"
1769411,2018-05-07 10:52:11 UTC,oldrocker99: Any chance you could make this bug as also affecting you please so that it gets confirmed?
1769411,2018-05-07 10:54:46 UTC,Video showing the issue from 2015
1769411,2018-05-07 12:51:43 UTC,Thanks for writing this. As the creator of the linked video I obviously find this kind of thing to be frustrating and wish that someone would address it.
1769411,2018-05-15 21:20:22 UTC,I've changed this bug to confirmed as it affects multiple users.
1769411,2019-02-07 08:30:51 UTC,"Exactly the same issue for me too (youtube video above is perfect example). .MATE 18.04 fresh install, seems ridiculous for this to be the ""out of the box"" behaviour and for it to have lasted so long :("
1769411,2019-06-19 00:33:37 UTC,This bug was fixed in the package marco - 1.22.2-0ubuntu1
1769411,2019-10-07 09:31:39 UTC,This bug was fixed in the package mate-themes - 3.22.20.1-0ubuntu1
1769415,2018-06-07 02:07:26 UTC,We recommend installing Ubuntu 18.04 as version 17.10 will reach end of life next month.
1769417,2018-05-06 03:10:12 UTC,Confirmed the duplicate icon behavior as shown in the video.
1769417,2018-05-23 13:39:18 UTC,Apparently this is an app bug that's already been fixed upstream: https://www.virtualbox.org/ticket/12534
1769425,2018-05-06 05:04:24 UTC,0.4.16 is also working.
1769425,2019-04-04 15:03:59 UTC,"I believe this is fixed in commit 7ffb27c7d526e7bcb77cb2f93bb9de6e95f418f5, which is part of 1.1.0. I had the same problem on 1.0.2 and it was because the data passed wasn't being form encoded. Upgrading fixed it."
1769425,2018-05-06 04:59:56 UTC,Last Known working version is 0.4.15.
1769428,2018-07-28 21:56:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769428,2018-07-28 21:58:45 UTC,Below are the contents of the make.log file:
1769432,2019-04-10 16:12:41 UTC,"thanks for the help, every apt operation was complaining because it could not parse gnuradio.xml."
1769432,2020-03-20 23:53:43 UTC,Same bug with all updates and upgrades on 18.04lts
1769432,2019-03-28 18:02:28 UTC,Looks like gnuradio.xml is supposed to either have the same contents as gnuradio-grc.xml or be a (sym?)link to the latter.
1769432,2019-03-21 18:36:08 UTC,For Comment 5
1769432,2018-07-08 12:02:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769432,2018-08-15 20:47:24 UTC,"Confirmed on:
```
Ubuntu 18.04.1 LTS
GNU Radio Companion 3.7.11 (from official apt repo)
Linux 4.18.0-041800-generic
System updated as of 2018-08-15
```"
1769432,2018-05-14 05:59:11 UTC,Same problem here. Ubuntu 18.04 latest updates.
1769432,2019-03-21 18:33:29 UTC,"Hi there,"
1769438,2018-05-07 15:46:57 UTC,"Since at least Trusty, lxpanel-indicator-applet-plugin (which does not appear to be provided upstream), suggests indicator-messages-gtk2, which is not available. It also suggests indicator-application-gtk2 which has a hard requirement for gtk2 while indicator-application is gtk3. It seems that the goal was to split out the gtk2/3 versions. However, it doesn't seem that indicator-messages (a package which is available) has a hard requirement for gtk at all, so they may have just dropped indicator-messages-gtk2."
1769438,2018-05-17 07:44:47 UTC,"Christian,"
1769441,2018-05-22 07:33:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769443,2018-07-24 03:43:49 UTC,"No,Its not working...unable to received files from other device,it
always showing connection unsuccessful,"
1769443,2018-07-24 03:54:26 UTC,"Do other bluetooth devices work still? Like a mouse, keyboard or speaker?"
1769443,2018-07-24 03:56:38 UTC,"Also, please explain how and where you are trying to ""send or receive files via bluetooth""? A screenshot (via PrtSc) would help."
1769443,2018-07-24 04:26:34 UTC,"I'm  trying to send a music file or whatever from my Mobile to my laptop,but unable to send files...it shows following"
1769443,2018-07-24 05:11:11 UTC,"No,other device such as bluetooth speaker, mouse,keyboard is not working as
well.."
1769443,2018-07-24 09:36:47 UTC,"Please try hitting the Windows key and typing:
  Personal File Sharing"
1769443,2018-07-24 12:22:49 UTC,"I have installed personal file sharing app from software,and launch it,,but there is no option to set prefferences to receive files via bluetooth,and every time i have to go in software in order to search this applicalion because when i search it on dash it always shows-sorry there is nothing that matches you search..its very arriting"
1769443,2018-07-24 12:33:48 UTC,"see i have installed on my computer, if i want to launch it, i have to go software centre"
1769443,2018-07-25 02:00:07 UTC,This change was made by a bot.
1769443,2018-11-15 04:44:24 UTC,"Only file sharing not working now,Bluetooth Speaker is working"
1769443,2018-07-24 03:18:48 UTC,Great. You installed it successfully.
1769443,2018-07-24 05:30:07 UTC,This change was made by a bot.
1769443,2018-07-24 03:07:43 UTC, when I'm installing these kenal in terminal it shows following outputs
1769443,2018-07-24 04:29:39 UTC,But my laptops Bluetooth visibility and power is on...
1769443,2018-07-24 02:30:23 UTC,"Yes, however there won't be any ""future necessary updates"" if we don't know what to update."
1769443,2018-07-24 02:13:11 UTC,"The problem should be fix by future necessary updates, The Ubuntu developer
should try to fix this issue...If it possible please necessary release
 software updates,"
1769443,2018-07-24 01:08:31 UTC,"Although the latest kernel also contains the drivers:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/realtek/rtlwifi"
1769443,2018-07-24 01:04:08 UTC,It appears some other people have reported similar problems with the same RTL8723 bluetooth hardware in bug 1446239 and bug 1747421. However both of those have closed so we only have this bug now.
1769443,2018-07-23 12:33:24 UTC,"Problem is still going on Gnome shell desktop as well..it always shows connection unsuccessful on other device whenever I have tried to receive something from other device to my laptop..My computer is already up to date ,it shows following output when i ran rfkill on a terminal"
1769443,2018-07-23 08:42:48 UTC,It shows following out...sorry first time it was not showing the output
1769443,2018-07-24 02:32:22 UTC,Oops typing error
1769443,2018-07-23 08:38:12 UTC,"problem is persists after updating and restarting my computer..unable to
receive file over bluetooth."
1769443,2018-07-23 08:23:52 UTC,OK. If the problem persists after updating and restarting the system then next please try:
1769443,2018-07-23 08:13:34 UTC,Its already installed on my computer...
1769443,2018-07-23 02:13:46 UTC,"Also if you wish to send a receive files, please make sure you have installed:"
1769443,2018-07-23 02:12:16 UTC,I think a recent update (package: linux-firmware) might have fixed this. See bug 1745828.
1769443,2018-05-08 06:32:06 UTC,"I have not seen any personal files sharing application, because of this I'm
trying to launch the desktop sharing application,but is not launching at
all,I have restart my computer, problem is still going on.. Please give a
solution how to enable this feature"
1769443,2018-05-07 17:49:51 UTC,"Hi,"
1769451,2019-09-17 11:42:55 UTC,Migrated to https://github.com/widelands/widelands/issues/3498
1769451,2018-05-07 10:07:46 UTC,"Yes, that looks pretty good :)"
1769451,2018-05-06 14:30:42 UTC,That´s a good idea :)
1769451,2018-05-07 06:15:45 UTC,I have tied and failed to give the trees etc. a chiseled appearance - would the style of the text be good for that? I'll try to find out how to create the same effect on elements that are not text then.
1769451,2018-05-07 07:51:15 UTC,"Yes, the text style would fit for the trees too. It wouldn´t really matter if this doesn´t work for non-text though, because GIMP offers some great editing features there.
I took the liberty to edit your map with GIMP a bit. I added a semi-transparent marble overlay to the island, worked on the trees´ edges, and made the letters less sharply pronounced, and everything is brighter and shot through with reddish marble veins. The background could still do with some flattening here. What do you think of this?"
1769452,2018-06-09 14:56:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769453,2018-05-07 01:40:50 UTC,"> On May 6, 2018 at 7:52 AM Hank Grabowski <email address hidden> wrote:
>
>
> Public bug reported:
>
> I first ran across this in one of my main VMs when I tried the update.
> Everything went great, I re-applied the guest additions and voilà my
> shared folder drives mounted and I was in business.  The next day when I
> fired up the VM they were missing.  It was a hectic day, so I thought
> perhaps I had remembered it working so I applied the guest additions
> again.  The drives reappeared.  This time I rebooted to confirm it stuck
> but sadly they did not.  I’ve continued to do some experimenting and
> have come to discover that while they are there the systemd process
> doesn’t seem to want to start on reboot even though it is set to. So to
> fix it I just need to do the following command to get them to show up:
>
> sudo systemctl restart vboxadd-service.service
>
> I wasn’t having this problem on Ubuntu 18.04 or Ubuntu MATE 18.04 virgin
> machines so this was either a problem with the general Ubuntu 16.04 to
> 18.04 upgrade process or specific to Ubuntu MATE 16.04 to 18.04 upgrade.
> I therefore went about creating two brand new VMs, one each for mainline
> Ubuntu 16.04 and one for Ubuntu MATE 16.04 and then went through the
> upgrade process directly.  Those steps are:
>
>     Fresh install OS with 3rd party and upgrades turned on
>     Follow https://virtualboxes.org/doc/installing-guest-additions-on-ubuntu/ for installing guest additions
>     Shutdown/Power on
>     Add user to the vboxsf group (sudo usermod -a -G vboxsf <username>)
>     Restart
>     Confirm Read/write access to shared folder drive
>     Bring up System graphical updater, do any additional updates
>     Invoke Upgrade to 18.04 through graphical system:
>        sudo apt update && sudo apt dist-upgrade
>        update-manager -d
>     Perform upgrade and reboot
>     See if shared folder drive there
>     After Update re-apply kernel extensions
>     Restart
>     Confirm shared drive read/write access
>
> I can repeatably show that mainline Ubuntu 16.04 goes through these
> updates without this artifact but the MATE version does not.  Again, a
> fresh Ubuntu MATE 18.04 install doesn’t have this behavior at all.
>
> ** Affects: ubuntu-mate
>      Importance: Undecided
>          Status: New
>
>
> ** Tags: additions box guest ugrade virtual
>
> --
> You received this bug notification because you are subscribed to ubuntu-
> mate.
> Matching subscriptions: oldrocker99
> https://bugs.launchpad.net/bugs/1769453
>
> Title:
>   Virtual Box Shared Folder Drives Don't Automount in 16.04 to 18.04
>   upgraded Ubuntu MATE
>
> Status in ubuntu-mate:
>   New
>
> Bug description:
>   I first ran across this in one of my main VMs when I tried the update.
>   Everything went great, I re-applied the guest additions and voilà my
>   shared folder drives mounted and I was in business.  The next day when
>   I fired up the VM they were missing.  It was a hectic day, so I
>   thought perhaps I had remembered it working so I applied the guest
>   additions again.  The drives reappeared.  This time I rebooted to
>   confirm it stuck but sadly they did not.  I’ve conti...
"
1769453,2018-05-07 12:45:36 UTC,Thank's for the suggestion.  I use the default partitioning scheme with my installs but I understand your suggestion for making recovery easier.  Since these are VMs I snapshot them before doing any update/upgrade.  That way if the thing gets borked I can always roll back to the snapshot.  However I am curious what is causing the problem.  I was thinking of mounting both drives in another place and diffing them to see what the file system differences are between a Virgin 16.04 converted to 18.04 and a virgin 18.04 installation would be.
1769453,2018-08-17 11:52:32 UTC,"Should to check systemd unit dependencies.
See this answer
https://superuser.com/a/1349958/934811"
1769454,2018-09-04 02:16:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769455,2018-05-06 12:20:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769455,2018-05-06 23:55:04 UTC,*** This is an automated message ***
1769461,2018-05-09 18:27:59 UTC,"Yes, sorry about that. I got confused due to the lack of a kdevelop-dbg package in Kubuntu 18.04. But I figured it out. See attached backtrace."
1769461,2018-05-08 04:10:09 UTC,Do you have a backtrace of the crash? I can't reproduce your issue.
1769464,2018-05-30 15:51:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769470,2018-05-20 11:24:08 UTC,"Hi Charles,"
1769473,2018-05-06 15:50:18 UTC,"@cruzer001,"
1769473,2019-04-23 17:31:50 UTC,"Oops, said Bionic, was thinking Xenial."
1769473,2019-04-23 13:16:39 UTC,"> FWIW, official support of Lubuntu's Bionic is ending this month
"
1769473,2018-05-17 09:05:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1769473,2018-05-07 14:19:53 UTC,"This can be a convenient option, easy for beginners to find."
1769473,2018-05-07 05:16:20 UTC,"Actually looking at this a bit farther, it looks like there is a remove feature to the seeds that should have allowed for a minimal install for us. It's just not working."
1769473,2018-05-07 00:35:16 UTC,Thanks for the explanation Walter
1769473,2018-05-06 22:45:04 UTC,"Ok, I can confirm this. As of 18.04, there's a new ""minimal install"" option which is really something that Ubuntu desktop was marketing. I'm not sure it really works all that well for flavours. We have had a minimal install option that we have supported for a long time, though:
https://help.ubuntu.com/community/Lubuntu/Documentation/MinimalInstall"
1769473,2019-04-14 03:25:00 UTC,"FWIW, official support of Lubuntu's Bionic is ending this month, so the likelihood of seeing a fix there is quite small. Since then, we have a new installer, which means we'd have to implement our own mechanism. We'll look into that:"
1769473,2018-05-06 19:32:31 UTC,"No, I downloaded the live (not the alternate or mini) iso from lubuntu.net on my original install."
1769473,2018-05-06 19:02:34 UTC,Are you saying that you downloaded the mini.iso?
1769473,2018-05-06 18:43:39 UTC,"Wow, I never would I have suspected that.  Both sites look official."
1769473,2018-05-06 17:50:30 UTC,"Lubuntu.me is the official website. Please download from there and verify the checksums, then reinstall and try again."
1769473,2018-05-06 17:36:52 UTC,I downloaded the 64bit iso from
1769473,2018-05-06 17:19:57 UTC,"I downloaded the lubuntu live iso installer today and installed to virtualbox.  I checked the box to install a minimal system and completed the install.  I also did a complete (full) install with the same iso, checking the appropriate box.  Both installs have the same packages and package count(1374 installed packages)."
1769473,2018-05-06 16:10:53 UTC,I am unable to reproduce this bug.
1769473,2018-05-06 20:14:01 UTC,I have downloaded lubuntu 18.04; 64bit from lubuntu.me and checked the minimal install box during the install process.  And again I have ended up with full desktop install.
1769480,2018-11-19 07:08:31 UTC,I still don't see any log attached here. Maybe try tweaking powersaving knob in NetworkManger config file.
1769480,2018-11-17 22:32:39 UTC,"I dont thought this thread would get a response. I asked first what information i should provide but did not get any response because in dmesg there is nothing relevant. Its sad that someone else have to say that he have the same issue to get a resposne.
I installed ubuntu 18.10 in the meantime on an other device with totaly different wlan chipset. Same issue. So not that even the ubuntu version, also the hardware changed fully."
1769480,2018-11-02 06:36:42 UTC,Do you see the list via command `iw`?
1769480,2018-11-01 23:34:12 UTC,"Is there any chance to reactivate that topic? I have the same issue on a fresh Lubuntu 18.10 installation on my Sony Vaio Notebook.
After 5 minutes the tray icon (nm-tray) only shows the current wifi connection (which still works), no others anymore."
1769480,2018-06-16 00:39:39 UTC,I dont know what you mean in dmesg. There are really no errors. I have posted all relevant messages from dmesg. In the first post the wifi chipset and driver are listed. What additional information is required?
1769480,2018-05-06 16:43:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1769480,2018-05-08 09:39:28 UTC,"There are no usefull logfiles. Either dmesg nor syslog show anything usefull.
I am connected now. Problem exists like always."
1769480,2018-05-08 04:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769480,2018-05-06 16:19:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769480,2018-05-24 07:40:59 UTC,Sounds like a driver issue. Can you attach dmesg when this issue happens?
1769485,2018-05-23 16:40:31 UTC,fixed in git
1769485,2018-08-03 02:20:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769485,2018-05-21 10:19:05 UTC,"I added your line just before the case statement in ipa-httpd-pwdreader, and it works."
1769485,2020-08-22 03:26:31 UTC,This bug is still present in Ubuntu bionic.
1769485,2020-11-04 14:01:20 UTC,I had the same issue. 4.7.0~pre1+git20180411-2ubuntu2 is installed on a new server - and that does not have the fix in it.
1769485,2018-10-03 00:49:41 UTC,This bug was fixed in the package freeipa - 4.7.0-1ubuntu4
1769485,2018-05-19 18:52:32 UTC,"I tried with the Alternate ISO. The problem still occurs, but now I can change the hostname to my fully qualified domain name with hostnamectl in a reliable way. Still, ipa-server-install should work with a simple hostname, since this is the standard for Ubuntu sysems."
1769485,2018-05-21 10:30:23 UTC,"great, thanks.. guess we'll have to add that for now, until upstream fixes it"
1769485,2018-05-21 07:35:27 UTC,"if you edit ipa-httpd-pwdreader to set HOSTNAME=`hostname -f` before it's called, does it work?"
1769485,2018-05-06 16:41:01 UTC,Package was wrong.
1769485,2018-05-06 16:42:00 UTC,I am also attaching the Apache error log.
1769485,2018-05-06 17:02:25 UTC,"which architecture, and is it running on LXC/qemu or native hw?"
1769485,2018-05-19 10:48:29 UTC,"I realized now that ""hostnamectl set-hostname"" is not deterministic. Most of the times, the new hostname is lost after reboot, sometimes, without any apparent reason, it is preserved. The problem is that I installed Ubuntu 18.04 with the Live image, which has some peculiarities (see https://ubuntuforums.org/showthread.php?t=2390785). I will reinstall with the alternate ISO and see what happens."
1769485,2018-05-19 00:13:13 UTC,"I made some progress. The problem is that the script /usr/lib/ipa/ipa-httpd-pwdreader, which reads the passphrase of the SSL key on behalf of Apache, checks that the hostname passed by Apache has the same value of the $HOSTNAME environment variable. In my case, the two are different: Apache uses the full qualified name ""ipa.labeconomia.unich.it"", while $HOSTNAME contains only ""ipa"". I wonder why other people do not have the same problem."
1769485,2018-05-06 17:17:42 UTC,Running on QEMU/KVM. Both host and guest architectures are x86_64. Guest has 4GB RAM and 4 CPUs.
1769485,2018-05-19 10:15:44 UTC,"I was able to permanently change the host name with ""hosnamectl --set-hostname"". Nonetheless, I still thinks there is a bug here, because the Ubuntu 18.04 installer only allows me to set a unqualified host name, while ""ipa-server-install"" insists on a FQDN, and the two do not matches."
1769491,2018-05-06 19:01:29 UTC,I've submitted this patch to fix this issue:
1769491,2018-05-07 01:39:37 UTC,The proposed change creates a new command: environment-get-definition.
1769491,2018-06-08 17:35:42 UTC,This issue was fixed in the openstack/python-mistralclient 3.6.0 release.
1769491,2019-05-10 16:40:47 UTC,This issue was fixed in the openstack/python-mistralclient 3.1.5 release.
1769496,2018-05-07 11:17:49 UTC,ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego „./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie powiodło (8))
1769496,2018-05-07 16:00:52 UTC,This isn't a bug about the release upgrade process rather about the system after the release upgrade.
1769501,2018-07-04 20:33:55 UTC,"Hi Srinivas,"
1769501,2018-07-03 04:15:27 UTC,"Hi Ian,"
1769501,2018-06-26 08:20:27 UTC,"Hi srinivas,"
1769501,2018-06-25 11:04:08 UTC,"Hi Ian,"
1769501,2018-06-20 18:31:13 UTC,"Hi srinivas,"
1769501,2018-06-18 10:45:44 UTC,"Hi Ian,"
1769501,2018-05-19 18:39:37 UTC,"Hi srinivas,,"
1769501,2018-06-06 12:37:16 UTC,"Hi Ian,"
1769501,2018-05-28 19:11:47 UTC,"Hi srinivas,"
1769501,2018-05-24 05:14:32 UTC,"Hi Ian ,"
1769501,2018-07-29 20:03:49 UTC,"Hi Srinivas,"
1769501,2018-05-19 17:20:09 UTC,"Hi srinivas,"
1769501,2018-05-15 15:01:30 UTC,"Hi Ian Bruntlett,"
1769501,2018-06-10 19:32:07 UTC,"Hi srinivas,"
1769501,2018-07-30 19:31:40 UTC,"When I wrote:-
I installed python3-pyqt4, python-pyqt5"
1769504,2018-05-08 18:22:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769505,2018-05-06 20:59:08 UTC,That happens when the state of the builder changes in some way between the object being fetched and the call to .lp_save().  manage-builders needs to cope with this (perhaps e.g. refreshing the object and retrying) and currently doesn't.
1769517,2018-06-03 11:18:41 UTC,Phoronix also reported 4870 not to work on 4.17.
1769517,2018-05-25 20:33:46 UTC,"Created attachment 139777
dmesg from different motherboard"
1769517,2018-05-12 00:56:31 UTC,"The other video card is integrated into the motherboard, and the disabling the integrated video with bios causes the boot to fail."
1769517,2018-05-11 14:56:49 UTC,Does it work properly if you remove the nouveau card or switch the slots?
1769517,2018-05-11 01:57:40 UTC,"Created attachment 139483
full dmesg"
1769517,2019-11-19 09:33:23 UTC,-- GitLab Migration Automatic Message --
1769517,2018-05-10 01:56:44 UTC,This bug also existed with Ubuntu 16.04 in kernel 4.4.0-96-generic
1769517,2018-05-10 01:51:19 UTC,"On:
Linux mouse 4.17.0-041700rc4-generic #201805070430 SMP Mon May 7 04:31:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
I still get
[    4.007419] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
[    4.007433] radeon 0000:02:00.0: disabling GPU acceleration"
1769517,2018-05-07 15:59:54 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1769517,2018-05-06 23:00:11 UTC,This change was made by a bot.
1769517,2018-05-10 05:17:48 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/radeon"
1769519,2018-05-11 16:40:33 UTC,Seems to be workaroundable by using the other undocumented version-script key?
1769519,2018-05-11 18:18:43 UTC,"Yes. It'd be a shame if we had to perpetually rely on boilerplate input validation to perform such a useful function, though. If there is a consensus to only use version-script, this feature of version: should be removed to prevent unexpected breakage."
1769519,2018-05-11 18:44:54 UTC,"There is actually a third option: you can do this in scriptlets as of snapcraft 2.41[1]. High-level: you need to set `adopt-info` to the part that will set the version, and then you can run `snapcraftctl set-version` in a scriptlet for that part. Read the post for more info."
1769520,2021-02-18 16:46:21 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769522,2018-05-07 13:04:32 UTC,"On 5/6/2018 7:31 PM, Piotr Esden-Tempski wrote:

> Public bug reported:
>
> I am not 100% sure if it is a bug or intended behaviour. I assume it is
> intended that KIPRJMOD is not set when starting eeschema stand alone but
> due to lack of relative path support in sym-lib-table uri this causes
> issues. More info follows...
>
"
1769522,2018-05-07 20:46:43 UTC,"Hi Wayne,"
1769522,2018-05-07 20:57:25 UTC,I just tested it out... it seems that it is indeed setting the KIPRJMOD but it is not finding the libraries. So it has something to do with how the path expansion of the libraries is done when opening through kicad vs eeschema. I will try to record a screen grab illustrating the problem. You can test it out using this project for example: https://github.com/icebreaker-fpga/icebreaker-pmod/tree/master/tristate-led/v1.0a
1769522,2018-05-07 21:34:05 UTC,As promised here is the screen capture showing the issue where KIPRJMOD is not being set. https://www.youtube.com/watch?v=R45mevwlwvk
1769522,2018-05-08 15:39:49 UTC,"The video confirmed my suspicions.  If you use an absolute path to your schematic file, the project file will get loaded correctly.  KiCad requires absolute paths when passing file names on the command line.  This was done back when kicad ran as multiple applications because you cannot guarantee the current working directory will be correct on all platforms.  This created all kinds of grief so command line paths must be absolute.
 If you were running a debug build, you would see a bunch of asserts about the file name path not being absolute.  Now that almost all of KiCad normally runs under a single process, this may be less of an issue.  I'm not going to risk changing it for the v5 release but we can revisit this during v6 development."
1769524,2021-02-17 17:07:48 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769525,2021-02-17 17:07:50 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769526,2021-02-18 16:46:24 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769528,2021-02-17 17:07:53 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769530,2018-12-29 13:45:43 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/566149
Reason: This patch has no activity for a while, per policy, we abandon it. Feel free to re-open if you think you're working on it."
1769533,2021-02-17 17:06:27 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769533,2019-02-26 13:28:17 UTC,Is this still being worked on?
1769534,2021-02-17 17:07:55 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769536,2021-02-17 17:07:59 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769545,2019-06-07 16:01:11 UTC,"Issue mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1540924#c18 happens when there are certificates not available.During HSM installation especially migrations , client machines needs to sync correctly.This can be done using :"
1769545,2018-06-22 17:33:13 UTC,"Created attachment 1453796
sosreport-nwcal-subca1.nwc.nws.noaa.gov.02085383-20180620203058.tar.xz"
1769545,2018-06-22 17:31:39 UTC,debug logs from test package pki-10.5.tar.xz
1769545,2018-06-07 17:13:07 UTC,"FYI, some of the issues discussed here were probably caused by invalid path in pki_ca_signing_cert_path. It will be addressed in bug #1588655 by adding input validation."
1769545,2018-05-09 20:30:47 UTC,Per RHEL 7.5.z/7.6/8.0 Triage:  7.5.z
1769545,2018-05-07 23:23:39 UTC,"Geetika,"
1769545,2018-05-07 13:18:24 UTC,"Hi Jared,"
1769545,2018-04-25 16:55:15 UTC,Per RHEL 7.5.z/7.6/8.0 Triage:  7.6
1769545,2018-04-30 23:08:59 UTC,"Hi Evan,"
1769545,2020-12-23 08:15:14 UTC,I haven't seen reports of this since it was filed
1769545,2018-04-23 17:41:21 UTC,I am seeing the same error using an openssl rootCA and the ca-external pki setup. This is on a clean 7.5 minimal install with PKI subsystem.
1769545,2018-02-02 06:24:36 UTC,This is same in case of non-cmc environment.
1769545,2018-02-01 10:47:39 UTC,"Created attachment 1389444
debug"
1769545,2018-02-01 10:45:32 UTC,Description of problem:
1769545,2018-05-06 13:33:00 UTC,I too am having the same problem using an external openssl signing CA with pkispawn.
1769550,2018-09-14 07:26:43 UTC,I've also added an update showing how this can also set the MAC addresses of devices as well as the MTU.
1769550,2018-09-14 07:03:24 UTC,"Hi Ryan,"
1769550,2018-05-08 19:36:11 UTC,The current implementation writes link files for all interfaces since udev processes .link files no matter of backend choice.
1769550,2018-07-27 05:37:23 UTC,"Hi Ryan,"
1769554,2018-10-21 11:17:28 UTC,"""Preferences/Image no longer has
""When new image is selected"""
1769557,2018-05-14 07:43:39 UTC,Yea please use the default rtsx_pci.
1769557,2018-05-08 14:58:08 UTC,While the card was inserted. I follow these instructions [ https://dainaccio.wordpress.com/2013/07/14/realtek-sd-reader-mounting-problems-under-linux-mintubuntu/ ] installing rts_pstor-1.11 and blacklisting rtsx_pci. Should i delete this operation?
1769557,2018-05-08 09:07:41 UTC,Were these logs collected after you insert SD card?
1769557,2018-05-08 02:00:51 UTC,tagged: 'kernel-bug-exists-upstream'.
1769557,2018-05-08 01:55:02 UTC,"Hi! No, i've installed Ubuntu 16.04.1 and since then upgraded it untill 18.04, but it has never read an SD card. Doing what you said nothing changed. Thank for your comment!"
1769557,2018-05-07 15:59:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1769557,2018-05-07 04:09:58 UTC,apport information
1769557,2018-05-07 04:09:56 UTC,apport information
1769557,2018-05-07 04:09:51 UTC,apport information
1769557,2018-05-07 04:09:49 UTC,apport information
1769557,2018-05-07 04:09:47 UTC,apport information
1769557,2018-05-07 04:09:44 UTC,apport information
1769557,2018-05-07 04:09:40 UTC,apport information
1769557,2018-05-07 04:09:38 UTC,apport information
1769557,2018-05-07 04:09:35 UTC,apport information
1769557,2018-05-07 04:09:33 UTC,apport information
1769557,2018-05-07 04:09:30 UTC,apport information
1769557,2018-05-07 04:09:26 UTC,apport information
1769557,2018-05-07 04:09:24 UTC,apport information
1769557,2018-05-07 04:09:21 UTC,apport information
1769557,2018-05-07 04:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769557,2018-05-07 04:09:42 UTC,apport information
1769575,2018-05-07 09:26:19 UTC,"We need to wait until OSC 52 support is added to vte.
https://bugzilla.gnome.org/show_bug.cgi?id=795774"
1769585,2018-05-07 18:59:33 UTC,"Also the default terminal when using the F4 shortcut in PCManFM is wrong. Should be qterminal
Cheers"
1769612,2018-05-07 11:42:07 UTC,doesn't seem to have anything to do with linux-oem..
1769612,2018-05-07 13:28:08 UTC,"Please clarify on how to resolve this. as I understand, should I use Ubuntu to use this version of PACKSTACK?"
1769613,2018-06-01 19:28:55 UTC,I installed libavfilter6 and libopencv-highgui3.1 and was not able to recreate the bug so there must be some more packages involved.
1769613,2018-06-01 18:38:53 UTC,Sorry I misread the version numbers. This is actually the version from 17.10.
1769613,2018-06-01 18:35:27 UTC,Looking closely at the Aptclonesystemstate file we can see that the installed version of libavfilter6 was actually the bionic version installed on artful.
1769613,2018-05-16 12:04:50 UTC,Right but they are both official versions and shouldn't block the upgrade.
1769613,2018-05-16 09:58:31 UTC,I cannot reproduce the issue with the clone. But from the look of it I am wondering if some leftover from xenial could be causing this problem.
1769613,2018-05-14 15:37:19 UTC,"At first glance, these 2 'extra' sources could have introduced some conflicts:"
1769613,2018-05-14 15:15:20 UTC,"@dino99, your reply is not helpful, which packages from which PPAs are you talking about?"
1769613,2018-05-07 11:11:03 UTC,You have plenty of broken packages: clean your system and downgrade to genuine versions (via ppa-purge)
1769613,2018-05-16 11:50:25 UTC,"The problem was solved by removing some conflicting packages:
- libavfilter6,
- libopencv-highgui3.1,"
1769622,2019-03-03 21:50:10 UTC,"Hi
well after finding this similar issue
https://bugs.launchpad.net/tripleo/+bug/1792343
and indeed we changed the following parameters , when we started see this bug more often
ssh_args = -o ServerAliveInterval=20 -o ControlPersist=60m
teh surprise is that according to the issue resolved is that when the connection is broken and then reconnected
then the following code is still running but the response file does not exists
Seems to be correct
But apparently the parameter suggested by the fix is actually exposing this failure to happen more frequent"
1769622,2018-07-02 20:30:10 UTC,Which upstream job are you trying to execute here?  Can we have a full log?
1769622,2018-07-26 19:00:44 UTC,"I'm simply trying to deploy a ""standard configuration"", whatever that means, following"
1769622,2019-02-26 13:29:22 UTC,Closing due to the lack of activity here. It can be re-opened if needed.
1769622,2019-02-28 07:03:21 UTC,"Hi
this bug does appear randomly again
you can see below on my deployed server out of 8 Blades , 5 of them failed on the same error
while 3 passed this step.
it seems that there should be some wait or retry , waiting for the notify json file o appear in the OS
Can someone take it ?"
1769622,2020-02-11 06:35:14 UTC,there has not been any work on this for over a year.
1769623,2018-12-12 13:05:12 UTC,Thank you for reporting upstream.
1769623,2018-05-07 11:12:18 UTC,Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/84
1769631,2018-11-15 02:49:27 UTC,"------- Comment From <email address hidden> 2018-11-14 21:40 EDT-------
Sorry, I have not had time to get back to this one yet."
1769631,2018-05-07 11:40:46 UTC,Default Comment by Bridge
1769631,2018-05-07 21:09:19 UTC,what do you have in /usr/lib/s390x-linux-gnu/sasl2 ?
1769631,2018-05-07 22:50:22 UTC,"------- Comment From <email address hidden> 2018-05-07 18:43 EDT-------
root@fipas1:/usr/lib/s390x-linux-gnu/sasl2# ls -la
total 340
drwxr-xr-x  2 root root  4096 Apr 26 10:01 .
drwxr-xr-x 39 root root 20480 Apr 26 10:23 ..
lrwxrwxrwx  1 root root    22 Feb  5 11:48 libanonymous.so -> libanonymous.so.2.0.25
lrwxrwxrwx  1 root root    22 Feb  5 11:48 libanonymous.so.2 -> libanonymous.so.2.0.25
-rw-r--r--  1 root root 18400 Feb  5 11:48 libanonymous.so.2.0.25
lrwxrwxrwx  1 root root    20 Feb  5 11:48 libcrammd5.so -> libcrammd5.so.2.0.25
lrwxrwxrwx  1 root root    20 Feb  5 11:48 libcrammd5.so.2 -> libcrammd5.so.2.0.25
-rw-r--r--  1 root root 22520 Feb  5 11:48 libcrammd5.so.2.0.25
lrwxrwxrwx  1 root root    22 Feb  5 11:48 libdigestmd5.so -> libdigestmd5.so.2.0.25
lrwxrwxrwx  1 root root    22 Feb  5 11:48 libdigestmd5.so.2 -> libdigestmd5.so.2.0.25
-rw-r--r--  1 root root 55656 Feb  5 11:48 libdigestmd5.so.2.0.25
lrwxrwxrwx  1 root root    16 Feb  5 11:48 libgs2.so -> libgs2.so.2.0.25
lrwxrwxrwx  1 root root    16 Feb  5 11:48 libgs2.so.2 -> libgs2.so.2.0.25
-rw-r--r--  1 root root 34584 Feb  5 11:48 libgs2.so.2.0.25
lrwxrwxrwx  1 root root    21 Feb  5 11:48 libgssapiv2.so -> libgssapiv2.so.2.0.25
lrwxrwxrwx  1 root root    21 Feb  5 11:48 libgssapiv2.so.2 -> libgssapiv2.so.2.0.25
-rw-r--r--  1 root root 35000 Feb  5 11:48 libgssapiv2.so.2.0.25
lrwxrwxrwx  1 root root    18 Feb  5 11:48 liblogin.so -> liblogin.so.2.0.25
lrwxrwxrwx  1 root root    18 Feb  5 11:48 liblogin.so.2 -> liblogin.so.2.0.25
-rw-r--r--  1 root root 18400 Feb  5 11:48 liblogin.so.2.0.25
lrwxrwxrwx  1 root root    17 Feb  5 11:48 libntlm.so -> libntlm.so.2.0.25
lrwxrwxrwx  1 root root    17 Feb  5 11:48 libntlm.so.2 -> libntlm.so.2.0.25
-rw-r--r--  1 root root 34792 Feb  5 11:48 libntlm.so.2.0.25
lrwxrwxrwx  1 root root    18 Feb  5 11:48 libplain.so -> libplain.so.2.0.25
lrwxrwxrwx  1 root root    18 Feb  5 11:48 libplain.so.2 -> libplain.so.2.0.25
-rw-r--r--  1 root root 18400 Feb  5 11:48 libplain.so.2.0.25
lrwxrwxrwx  1 root root    19 Feb  5 11:48 libsasldb.so -> libsasldb.so.2.0.25
lrwxrwxrwx  1 root root    19 Feb  5 11:48 libsasldb.so.2 -> libsasldb.so.2.0.25
-rw-r--r--  1 root root 26440 Feb  5 11:48 libsasldb.so.2.0.25
lrwxrwxrwx  1 root root    18 Feb  5 11:48 libscram.so -> libscram.so.2.0.25
lrwxrwxrwx  1 root root    18 Feb  5 11:48 libscram.so.2 -> libscram.so.2.0.25
-rw-r--r--  1 root root 38904 Feb  5 11:48 libscram.so.2.0.25
root@fipas1:/usr/lib/s390x-linux-gnu/sasl2#"
1769631,2018-05-08 12:09:14 UTC,"ok that looks normal, and 389 should do the right thing now but something is still missing and I don't know what.. but the bug isn't in freeipa itself so moving it over to 389 for now"
1769631,2018-05-08 12:42:08 UTC,paste the output of
1769631,2018-05-09 00:20:23 UTC,"------- Comment From <email address hidden> 2018-05-08 20:12 EDT-------
Currently there is nothing listening on 389"
1769631,2018-05-09 04:53:13 UTC,"forget about ipa-server-install for now, use setup-ds to get an instance up"
1769631,2018-05-21 11:39:14 UTC,"Just to clarify, the error is from 389-ds-base not getting set up, so take freeipa out of the picture by testing if you can run setup-ds successfully.."
1769631,2018-11-14 04:17:31 UTC,[Expired for Ubuntu on IBM z Systems because there has been no activity for 60 days.]
1769631,2020-04-23 20:07:28 UTC,If you still have questions about freeipa / 389-ds-base on s390x please work with upstream projects to gain s390x support for them.
1769634,2020-09-23 16:10:38 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/566560
Reason: Doesn't appear to be needed."
1769634,2018-05-14 11:18:16 UTC,"Since backup backend already stores this kind of this thing, we need to ask backend driver to copy the metadata during create_volume_from_backup."
1769662,2018-05-07 13:29:52 UTC,"I managed to reproduce the bug in another way. Open the second attached file (test2.svg). Then edit text in a text box. While in edit mode in one piece of text, click into another text to edit it. At that second click, inkscape consistently crashes."
1769662,2018-05-07 21:26:40 UTC,test.svg doesn't crash for me on Linux Mint 18.3 with 0.92.x (compiled from the branch today)
1769662,2018-05-08 06:22:11 UTC,OK. thanks for pointing that out. Feel free to close this ticket because this will followed up at https://bugzilla.redhat.com/show_bug.cgi?id=1575842
1769662,2018-05-08 11:59:15 UTC,"Related bug report in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1575842"
1769662,2018-05-30 08:10:42 UTC,Locally compiled Inkscape 0.92.x on Fedora 28 does not crash on test.svg. Stock Inkscape does. No useful info in traceback.
1769662,2019-04-22 13:10:32 UTC,"Hi, I'm going through Fedora/text related issues and was wondering if this is still an issue."
1769662,2019-06-10 07:56:34 UTC,Closing as duplicate of bug 1803553.
1769663,2018-05-08 18:14:47 UTC,Holding off on this for now until https://bugs.launchpad.net/bugs/1750121 is sorted.
1769668,2019-02-26 03:25:12 UTC,"I'm not sure this is the same bug.. as I found the cause for this and it shouldn't have affected 18.04. So I am creating a new bug:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1817655"
1769668,2019-05-05 07:07:35 UTC,"One thing I've learned about netplan, when using it with NetworkManager and bridges, is to delete the connection created by NetworkManager, but not created by netplan, in NetworkManager using nmtui first.  Then do netplan generate, and netplan apply, then, very important, restart NetworkManager."
1769668,2019-02-26 03:09:17 UTC,I can confirm this on Ubuntu 19.04 (disco devel). I have a simpler configuration of creating a single bridge with a single Ethernet port.
1769668,2019-05-05 07:11:22 UTC,"Btw, with my technique, the wlan0 connects, but the bridge doesn't allow it to be added, and errors out with:"
1769668,2018-05-31 10:59:45 UTC,Here's the output of nmcli conn
1769668,2018-05-16 01:11:31 UTC,"Steps:
1. Removed ifupdown package
2. Added /etc/netplan/01-netcfg.yaml with the contents:
network:
  version: 2
  renderer: networkd
  ethernets:
    enp0s25:
      renderer: NetworkManager
      dhcp4: no
      dhcp6: no
  wifis:
    wlan0:
      renderer: NetworkManager
      match: {}
      access-points:
        ""open network"": {}
  bridges:
    bridge0:
      renderer: NetworkManager
      dhcp4: yes
      dhcp6: yes
      interfaces: [wlan0, enp0s25]"
1769668,2018-05-15 19:59:25 UTC,"Hello shemgp ,"
1769668,2018-07-31 04:17:18 UTC,[Expired for netplan because there has been no activity for 60 days.]
1769672,2018-05-07 14:24:45 UTC,"Hi, you wrote Debian doesn't run the tests in parallel, do you mean for theano in particular, or in general?"
1769672,2018-05-07 17:22:19 UTC,"Looks like it's a cumulative memory leak: over the python2 tests, memory usage increases by ~6GB.  (Measured by occasionally looking at System Monitor, so I know it's more than one step, but not whether it's a few bad tests or a smaller amount on every test.)  This is then freed when the python2 tests finish; I didn't wait to see whether the python3 half would repeat it."
1769672,2018-05-11 14:47:11 UTC,The underlying issue is not new; I don't know whether it's got worse per test or the test suite has just got longer.  See the linked Debian bug for further analysis.
1769672,2018-05-11 15:16:35 UTC,I'll test and upload if successful.
1769672,2018-05-12 22:42:58 UTC,This bug was fixed in the package theano - 1.0.1+dfsg-2ubuntu1
1769676,2018-08-12 13:40:59 UTC,Right.
1769676,2018-09-01 15:04:13 UTC,"One possible solution is to issue an ANSI escape sequence ""\x1b[4G"" immediately after the logo is print, to reset the cursor position. (4 is the horizontal coordinate, you can change it accordingly.)"
1769676,2018-09-02 06:54:53 UTC,"Also the double exclamation mark character ""‼"" causes the same issue under the default Linux screen console."
1769677,2019-05-10 12:22:31 UTC,Can confirm the issue on 19.04
1769683,2018-05-10 10:37:57 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1769683,2018-05-15 15:17:23 UTC,Have reviewed all strings :-)
1769695,2018-05-09 15:43:52 UTC,"It seems like this happened again, but now syslog just contains:"
1769695,2018-05-10 02:15:48 UTC,"Sounds like Java is causing a lot of log messages, but that might not be related to the freeze."
1769695,2018-05-10 02:21:02 UTC,Also these two messages suggest pauses at a low level that could block other things:
1769695,2018-05-10 02:21:54 UTC,Please also run this command to send us more info:
1769695,2018-05-11 13:18:35 UTC,apport information
1769695,2018-05-11 13:18:36 UTC,apport information
1769695,2018-05-11 13:25:20 UTC,I collected the information.
1769695,2020-11-16 08:46:53 UTC,Does this problem still happen in 20.04 ?
1769695,2021-01-16 04:17:22 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1769701,2019-05-10 14:09:10 UTC,Thank you very much. Will this fix be backported for the Ubuntu LTS?
1769701,2019-02-26 16:57:55 UTC,"I'm also having this bug in Ubuntu MATE 18.04 LTS. It's been fixed upstream in version 1.4.4, so there should be a good copy of it that could be grabbed and added to Ubuntu's repository."
1769701,2019-02-26 16:59:26 UTC,Here's my output when taskcoach is run on the command line:
1769701,2018-09-28 04:57:25 UTC,"This issue was reported in 2015 upstream and nothing has been done about it. See https://sourceforge.net/p/taskcoach/bugs/1593/. Right now, this package is broken."
1769701,2018-06-11 01:21:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769701,2018-09-28 05:30:56 UTC,"Addendum, see https://sourceforge.net/p/taskcoach/bugs/1661/, the bug has been assigned and hopefully the fix(es) are implemented by next release!"
1769709,2020-03-27 12:58:50 UTC,"I think this issue looks like resolved, can anyone reproduce it?"
1769709,2020-05-14 09:41:41 UTC,This is fixed now as part of the refactoring.
1769715,2020-09-30 05:38:38 UTC,The bug is still present in Openstack Queens latest release 17.1.12 and in master.
1769715,2019-06-06 19:52:39 UTC,fixed in : https://review.opendev.org/#/c/661080/
1769715,2019-01-24 15:51:56 UTC,"Hi Jesse,"
1769715,2019-02-12 10:41:23 UTC,"I removed the lines you suggested and it doesnt ""just work"""
1769715,2018-05-08 16:09:34 UTC,According to upstream docs [1] they say to run keystone under apache. So it seems like this [2] commit needs to be backed out or changed so that if you are using federation apache will get setup and used like before.
1769715,2018-05-08 07:20:17 UTC,"The configuration for Apache implements the WSGIScriptAliasMatch [1] directive, but the 'libapache2-mod-wsgi' packages has not been installed and therefore that command is invalid. The reason that package is not installed is that Apache is supposed to be setup in the same way as it is for Nginx, as a reverse proxy to uwsgi. Try just removing that directive and see if keystone and federation actually just work."
1769715,2018-05-29 13:39:03 UTC,This is also related: https://bugs.launchpad.net/openstack-ansible/+bug/1772772
1769718,2018-05-07 18:17:19 UTC,Confirmed in 3.4 + guirefactor branch
1769718,2019-03-29 07:45:11 UTC,Still a problem in 3.5.0
1769722,2020-03-13 13:12:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/712943"
1769722,2020-03-14 02:20:02 UTC,"Reviewed:  https://review.opendev.org/712348
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=440aa8d210163125cf0e72c7a23d4b4ca12cd72d
Submitter: Zuul
Branch:    stable/queens"
1769722,2021-02-19 15:52:08 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1769722,2020-03-13 13:49:21 UTC,"Change abandoned by Giulio Fidente (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/712943"
1769722,2020-03-11 12:13:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/712348"
1769722,2018-05-18 10:15:59 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/569376"
1769722,2019-03-05 13:48:42 UTC,Is this still an issue?
1769722,2018-12-29 13:46:38 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/569376
Reason: This patch has no activity for a while, per policy, we abandon it. Feel free to re-open if you think you're working on it."
1769722,2018-05-07 18:53:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/566701"
1769722,2019-05-04 22:55:30 UTC,"Change abandoned by John Fulton (<email address hidden>) on branch: master
Review: https://review.opendev.org/566701
Reason: Abandoning 8-month old patch"
1769724,2018-05-08 08:34:43 UTC,Seems to happen only when booted in EFI mode.
1769724,2018-07-30 18:37:36 UTC,"I have a Fresh 18.04 installation, added french keyboard and still type in English/Querty !"
1769725,2018-05-07 21:05:45 UTC,"One note: after clicking on ""view"" it is possible to delete the item from the ""Actions"" menu.  That may be slightly more efficient."
1769725,2018-05-07 21:59:32 UTC,"Thanks, Beth!  Yes, it looks like that Actions menu was added after 2.12.  That helps a lot with the list view issue I described.  It's still unintuitive to click on View, rather than Edit, when you want to make a change."
1769733,2018-05-08 14:34:55 UTC,apport information
1769733,2018-05-08 14:34:57 UTC,apport information
1769733,2018-05-08 14:35:02 UTC,apport information
1769733,2018-05-08 14:35:05 UTC,apport information
1769733,2018-05-08 16:30:17 UTC,"I've added in the 4.17 kernel and now all three screens work, however it does not get the type of the other display and does not have the right resulution (1920x1080), it is connected via a displayport-> hdmi adapter."
1769733,2018-05-08 14:34:53 UTC,apport information
1769733,2018-05-08 15:00:33 UTC,"I'm not sure what I'm doing wrong:
I've used this command:
sudo dpkg -i *.deb"
1769733,2018-05-08 14:34:50 UTC,apport information
1769733,2018-05-08 14:35:00 UTC,apport information
1769733,2018-05-08 14:34:46 UTC,apport information
1769733,2018-05-07 22:24:35 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1769733,2018-05-07 22:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769733,2018-05-08 06:35:37 UTC,"I will try to test the latest kernel and see if that will fix it.
Also I will add in the logs.
I'll do that in 8~10 hours from now."
1769733,2018-05-08 14:34:36 UTC,apport information
1769733,2018-05-08 14:34:48 UTC,apport information
1769733,2018-05-08 14:34:39 UTC,apport information
1769733,2018-05-08 14:34:41 UTC,apport information
1769733,2018-05-08 14:34:43 UTC,apport information
1769735,2018-05-12 03:12:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769736,2018-05-07 20:08:46 UTC,The code that creates the menu is in function ensure_dbus_setup() in vcl/unx/gtk3/gtk3gtkframe.cxx.
1769736,2018-10-15 16:24:08 UTC,See also bug #1797888.
1769736,2018-10-20 09:54:20 UTC,It makes no sense to fix this bug or LP: #1797888 due to https://gitlab.gnome.org/GNOME/Initiatives/wikis/App-Menu-Retirement.
1769736,2018-10-22 13:54:40 UTC,"Yes, this code will be removed in a not-too-distant future. Let's keep the bug open until that happens. Thanks for the links Adolfo."
1769744,2018-05-07 20:44:04 UTC,Confirming previously stated interest.
1769744,2018-05-08 14:29:08 UTC,"Yes, I am interested in this."
1769749,2018-08-22 16:33:16 UTC,"FWIW, new eventlet seems to work well: https://review.openstack.org/#/c/591034/"
1769749,2018-08-22 14:44:35 UTC,Fix is merged in eventlet and present in 0.24.1
1769749,2018-06-20 18:14:46 UTC,Blacklisted in https://github.com/openstack/swift/commit/049dc0c
1769749,2018-05-17 19:14:03 UTC,"Fairly certain, yes. I'm pretty sure eventlet is out of spec for WSGI now (for py2, anyway), so it should get patched (or drop py2 support, which wouldn't be great for us), and in the mean time we need to black-list 0.23.0."
1769749,2018-05-17 18:35:31 UTC,"Is the root cause the mentioned commit? We patch swift, eventlet or not inc eventlet version?"
1769753,2018-05-18 12:36:14 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1769762,2018-05-07 22:14:22 UTC,Charm settings for reference are livepatch_proxy and snap_proxy.  model configs land straight into all users' shell environment variables.
1769762,2018-06-20 02:22:32 UTC,"Thanks, that's a good idea. I'll see what I can get done this week."
1769766,2018-06-11 14:34:41 UTC,"That's strange.  Grub complained that the disk does not have a bios boot partition, yet it does."
1769770,2018-05-08 00:12:06 UTC,Addition to Bug #1769770
1769774,2019-03-17 16:51:48 UTC,"Added support for xsettings, thanks!"
1769774,2019-03-17 16:51:11 UTC,Igor referenced this bugreport in commit 4119272d6e64de6b95a89f03c7176ac6cc6869ec
1769774,2019-03-16 08:46:04 UTC,Terminal uses dconf org.gnome.desktop.interface.monospace-font-name font rather than xsettings one.
1769774,2019-01-29 05:18:06 UTC,This bug was fixed in the package xubuntu-default-settings - 19.04
1769774,2018-09-23 20:54:05 UTC,Should this be added to xubuntu-default-settings.gsettings-override to match the Xfce font settings?
1769774,2018-05-09 22:50:37 UTC,"Xfce sets the xsetting for monospace font, but Gtk+3 ignores it:"
1769774,2019-01-29 03:28:25 UTC,Patch applied with the below commit.
1769774,2018-05-09 20:38:11 UTC,"On my Ubuntu / Unity desktop neither Terminator, the default gnome-terminal, or tilix display anything related to monospaced fonts with the GDK_DEBUG=settings prefix. (There is a proportional system font returned, but that's not what we're interested in here.)"
1769774,2018-05-09 19:41:22 UTC,Here is the code which tries to figure out the system default font: https://bazaar.launchpad.net/~gnome-terminator/terminator/gtk3/view/head:/terminatorlib/config.py#L368
1769774,2018-05-09 22:40:55 UTC,"For extra fun, even xfce4-terminal queries gsettings directly for the system monospace font, which means it doesn't follow the xfce default font setting either:"
1769774,2018-05-09 19:08:01 UTC,dconf command has no output for that. I assume because the value is set to the default.
1769774,2018-05-09 12:11:00 UTC,"$ dconf read /org/gnome/desktop/interface/monospace-font-name
'Hack Regular 10'"
1769774,2018-05-08 21:16:02 UTC,"I agree. Can you tell me where Gtk3 sets those standards, so that I can check?"
1769774,2018-05-08 18:34:12 UTC,"I'm pretty sure that you are tripping over the fact that terminator is gtk3 and checks in the gnome standard location. I'm not sure if xfce attempts to set the right fonts for the various desktops (i.e. gnome gtk2 and gtk3, kde, etc). I would argue that it is better to have the desktop set these values, rather than have every application trying to detect every desktop and parse their various ways of setting default fonts."
1769775,2019-11-01 13:40:17 UTC,Here's the screenshot: https://bugs.launchpad.net/ubuntu/+source/xfce4-pulseaudio-plugin/+bug/1769775/+attachment/5135701/+files/volue.png
1769775,2019-11-01 13:39:28 UTC,Just to add some context: all the bubbles appear stacked on the same monitor. (Last time I checked anyway.)
1769775,2019-08-08 14:02:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769775,2019-11-01 10:30:55 UTC,Downstream report: https://bugs.launchpad.net/ubuntu/+source/xfce4-pulseaudio-plugin/+bug/1769775
1769776,2018-05-08 00:42:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1769776,2018-05-08 02:51:16 UTC,"I was told to specify the ""package"" but I don't know what one is even after reading ""What is a package?"" at https://help.ubuntu.com/community/InstallingSoftware#What_is_a_package.3F."
1769776,2018-05-10 13:12:32 UTC,"I got an automated email to specify the ""package"" but I still don't know what a ""package"" is. Sorry, but after a day and half of googling around, the closest thing I can come up with was to choose above ""lubuntu default settings"". I hope this is correct. I looked  up my system info; though the word ""package"" doesn't appear in the ENTIRE thing, it states under """"operating system"":"
1769785,2018-08-07 01:03:10 UTC,Debdiff attached based on version built in my PPA.
1769785,2018-08-12 04:27:36 UTC,New debdiff attached with requested changes.
1769785,2018-08-12 02:18:13 UTC,"Please format it for uploading to Cosmic (or if it's to Bionic, please fill out the bug description correctly: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template )"
1769785,2018-11-23 22:10:55 UTC,This bug was fixed in the package calf - 0.90.1-1
1769785,2018-07-30 00:37:46 UTC,"Mikhail,"
1769785,2018-07-10 19:16:41 UTC,"Hi Ross,"
1769785,2018-07-10 19:22:36 UTC,"Version 0.90.1 released July 8, 2018"
1769785,2018-07-07 08:34:20 UTC,"Hi Erik,
Sing out if you need sponsorship to upload to Debian.
Ross"
1769785,2018-07-02 15:10:07 UTC,"This should now be more than a wishlist item as this is a major release that happened it November. The new version fixes a bug that causes DAWs such as Ardour and Qtractor to crash. This needs to be packaged immediately. If I have to do it myself, I will. https://github.com/calf-studio-gear/calf/issues/181"
1769785,2018-07-30 00:13:46 UTC,"Hi,
I am maintaining ppa:mikhailnov/pulseeffects (upstream is at https://github.com/wwmm/pulseeffects)
I tried to get this package into Debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902700
but nobody sems to be interested and I stopped uploading newest versions there."
1769792,2018-12-02 17:35:44 UTC,It appears that the problematic commit has been found:
1769792,2020-09-30 20:24:19 UTC,Saaaamme here. FUJITSU Notebook LIFEBOOK E Serie running Ubuntu 18.04.5 LTS
1769792,2019-12-03 14:25:15 UTC,Same here with a Sony VAIO running Ubuntu 19.10
1769792,2019-11-08 10:13:40 UTC,"Similar here. Touchpad freezes totally after suspend. I'm not sure about the keyboard, as I stay in the graphic environment - I suspect it doesn't quite work either. As for others, only a complete turn off - turn on helps, reboot does not."
1769792,2019-04-22 02:50:42 UTC,"Similar here folk. Random keyboard disabled on resume from suspend/hibernation.
4.19.0-parrot1-20t-amd64
HP x360 13 AC113
I tried the
GRUB_CMDLINE_LINUX_DEFAULT=""atkdb.reset i8042.nomux quiet splash""
as suggested on other boards.
Seems better, but has persisted, occasionally still occurs
BTW, I have touchpad disabled and use mouse, So, not aware if my touchpad is affected."
1769792,2019-04-19 12:54:02 UTC,"I have the same problem, with Fujitsu Lifebook E557, Ubuntu 18.10, kernel 4.18.0-17-generic."
1769792,2019-03-23 17:33:28 UTC,"Right now it seems the problem is still alive.
I’m using xubuntu 18.04:
Linux Kernel 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 GNU/Linux
on a Sony VAIO Laptop:
SVE1512E1EW (54512264)
Sony Corporation
version: C10FMXTT
serie: 54512264-0010407"
1769792,2018-12-12 03:10:52 UTC,The patch isn't in upstream Linux though...
1769792,2018-11-22 12:45:46 UTC,"I have the same or very similar problem, with Fujitsu Lifebook E557, Ubuntu 16.04,18.04 and 18.10."
1769792,2018-08-04 14:58:28 UTC,"My Laptop is a Sony Vaio SVE1512E1EW
Ubuntu 18.04.1 LTS x86_64
Kernel: 4.15.0-29-generic
Xfce
After resume, Keyboard doesn't work. Never. Using On screen keyboard I write the first character of my password and usually I can use the keyboard to put the rest of characters. Thereafter keyboard works.
Sometimes I have to write the entire password 'on screen' and then keyboard works, but sometimes it never works and I have to boot."
1769792,2018-09-21 14:17:26 UTC,Would it be possible for you to do a kernel bisection?
1769792,2018-09-09 15:32:40 UTC,"I did more tests, and learned that linux 4.9.125 is the last working version for me and 4.10.0 is the first version that doesn't work."
1769792,2018-09-09 15:20:09 UTC,I read the bug report and tested the same on my machine. It appears that linux-image-4.9.114 works fine for me while 4.10.5 gives me the problems I mentioned earlier.
1769792,2018-08-22 10:44:43 UTC,Possibly related to https://bugzilla.redhat.com/show_bug.cgi?id=1436636
1769792,2018-09-24 06:08:31 UTC,"If I'm not wrong bisection has been done by Guido Aulisi on https://bugzilla.redhat.com/show_bug.cgi?id=1436636, Comment 4.
In any case, right now I can't try the bisection."
1769792,2018-06-07 15:57:00 UTC,"I have this bug, at least partially. My keyboard keeps working, but touchpad doesn't work after reboot. I originally commented in this report:"
1769792,2018-05-08 16:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769792,2018-05-08 15:51:14 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1769793,2018-05-10 07:15:37 UTC,https://bugs.launchpad.net/nova/+bug/1754071
1769793,2018-05-08 09:50:30 UTC,"Fix committed
https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/410342/"
1769793,2018-05-10 07:15:27 UTC,"actually this is because delete an instance when instance is doing snapshot
this leads to some issue because image might be captured in zcc but failed to be cleanup by driver"
1769794,2018-09-06 06:51:17 UTC,"fix committed:
https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/410928"
1769796,2018-05-08 09:48:55 UTC,"Fix commited
https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/410389/"
1769800,2018-07-16 03:03:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769808,2019-04-17 06:28:16 UTC,"I've same problem with nvidia 960 in combo with intel integrated card.
Even when I disable integrated card in BIOS, it doesn't help, but contrary making it default helps, but of course then system is using integrated card as main card."
1769808,2018-05-31 09:49:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769808,2018-05-08 04:43:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1769808,2018-05-17 00:41:54 UTC,"UPDATE: Following information may provide help
This issue occurred on my laptop which has two video cards, one is independent nvidia GPU and the other is integrated Intel one. I think this might cause the problem because on my other laptop only has one nvidia GPU, no such kind of issue occurred (Although on that laptop, the nvidia driver is not at the version of 390)."
1769816,2018-05-08 05:42:03 UTC,apport information
1769816,2018-05-08 22:30:36 UTC,I've removed the 4.17rc4 packages and have returned to my original state.
1769816,2018-05-08 22:03:59 UTC,"Should I remove the rc4 kernel?  If not, how can I fix the broken status?"
1769816,2018-05-08 22:01:49 UTC,"2018-05-09 07:36:14 startup archives install
2018-05-09 07:36:14 install linux-headers-4.17.0-041700rc4:all <none> 4.17.0-041700rc4.201805070430
2018-05-09 07:36:14 status half-installed linux-headers-4.17.0-041700rc4:all 4.17.0-041700rc4.201805070430
2018-05-09 07:36:17 status unpacked linux-headers-4.17.0-041700rc4:all 4.17.0-041700rc4.201805070430
2018-05-09 07:36:17 status unpacked linux-headers-4.17.0-041700rc4:all 4.17.0-041700rc4.201805070430
2018-05-09 07:36:17 install linux-headers-4.17.0-041700rc4-generic:amd64 <none> 4.17.0-041700rc4.201805070430
2018-05-09 07:36:17 status half-installed linux-headers-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status unpacked linux-headers-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status unpacked linux-headers-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 install linux-image-unsigned-4.17.0-041700rc4-generic:amd64 <none> 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status half-installed linux-image-unsigned-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status unpacked linux-image-unsigned-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status unpacked linux-image-unsigned-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 install linux-modules-4.17.0-041700rc4-generic:amd64 <none> 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status half-installed linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 configure linux-headers-4.17.0-041700rc4:all 4.17.0-041700rc4.201805070430 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked linux-headers-4.17.0-041700rc4:all 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status half-configured linux-headers-4.17.0-041700rc4:all 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status installed linux-headers-4.17.0-041700rc4:all 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 configure linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status half-configured linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status installed linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 configure linux-image-unsigned-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked linux-image-unsigned-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status half-configured linux-image-unsigned-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:25 status installed linux-image-unsigned-4.17.0-041700rc4..."
1769816,2018-05-08 21:55:33 UTC,Side effect.... messages from mintupdate:
1769816,2018-05-08 21:44:17 UTC,Installed deb packages above.
1769816,2018-05-10 14:34:55 UTC,The problems seem to be fixed following installation of this package:
1769816,2018-05-08 17:19:04 UTC,Please confirm that the following deb files should be installed (correct ones).
1769816,2018-05-08 16:05:26 UTC,This version has the bug:  linux-headers-4.15.0-20
1769816,2018-05-08 15:48:12 UTC,Can you post the prior kernel version that does not exhibit this bug?
1769816,2018-05-08 15:47:27 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1769816,2018-05-08 05:41:59 UTC,apport information
1769816,2018-05-08 05:41:40 UTC,apport information
1769816,2018-05-08 05:41:54 UTC,apport information
1769816,2018-05-08 05:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769816,2018-05-08 05:41:56 UTC,apport information
1769816,2018-05-08 05:41:32 UTC,apport information
1769816,2018-05-08 05:41:35 UTC,apport information
1769816,2018-05-08 05:41:29 UTC,apport information
1769816,2018-05-08 05:41:43 UTC,apport information
1769816,2018-05-08 05:41:46 UTC,apport information
1769816,2018-05-08 05:41:49 UTC,apport information
1769816,2018-05-08 05:41:51 UTC,apport information
1769816,2018-05-08 05:41:37 UTC,apport information
1769819,2018-07-10 04:55:08 UTC,Thanks for the link.
1769819,2019-02-05 14:45:55 UTC,"This happens to my XMG/Clevo W230s with GM107M [GeForce GTX 860M]. I have an external monitor connected and disable the laptop screen with xrandr --output eDP-1-1 --off. When I suspend and close the lid, then disconnect the VGA cable and therefafter resuspend, Xorg crashes and I have to login again. It also kills screen sessions running in the background. This seems to be related to bug #1421808"
1769819,2018-09-07 14:02:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769819,2018-07-20 20:56:26 UTC,https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887
1769819,2018-07-20 20:56:12 UTC,CurrentDmesg.txt:
1769819,2018-07-10 04:17:25 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1769819,2018-05-10 06:25:30 UTC,should be this one: https://errors.ubuntu.com/oops/68c71690-5413-11e8-80d4-fa163ef911dc
1769819,2018-05-10 06:12:23 UTC,"To see previously reported crashes, try this:"
1769819,2018-05-08 06:18:42 UTC,"In order to debug a crash we will need a crash report. To create one, please:"
1769819,2018-05-08 06:35:03 UTC,"can you be more specific about the workaround. I read but 994921, but didn't find a clear reference as to what would need to be done"
1769819,2018-05-08 06:42:06 UTC,It's at the top of bug 994921.
1769819,2018-05-10 05:40:37 UTC,done. the new bug is bug #1770322
1769822,2018-09-14 07:03:40 UTC,"The problem here would be that the KVM device is blocking your monitor from sending EDID information, which contains the supported resolutions."
1769826,2018-05-08 07:00:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/566794"
1769826,2018-05-08 10:07:44 UTC,"Reviewed:  https://review.openstack.org/566794
Committed: https://git.openstack.org/cgit/openstack/vitrage/commit/?id=d485c6157dd38c316d6b46a73dc595b421dfc94b
Submitter: Zuul
Branch:    stable/queens"
1769826,2018-05-15 16:54:42 UTC,This issue was fixed in the openstack/vitrage 2.3.0 release.
1769829,2018-05-10 05:51:30 UTC,i have linux mint im new to linux and i have this pop up when im trying to update any help would be appreciated.
1769829,2018-05-21 06:51:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769829,2018-07-23 12:47:30 UTC,I am running 32 bit 16.04 in Oracle VirtualBox 5.2.16 on 64 bit Lenovo ThinkPad.  Hope this is helpful information.
1769834,2020-07-01 21:00:16 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769834,2020-08-31 04:17:26 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1769848,2019-12-17 22:49:49 UTC,"Comment #3 did not work for me.
Comment #8 worked.
Thank you everybody, especially Martin!"
1769848,2019-12-01 13:16:02 UTC,Comment #3 suggested to set CDR_FIFOSIZE=6m in /etc/wodim.conf. This did work for me.
1769848,2019-10-01 21:44:55 UTC,Thanks Martin. #8 fixed it for me.
1769848,2019-01-20 09:11:11 UTC,"I found this solution, see https://bugzilla.redhat.com/show_bug.cgi?id=1580021"
1769848,2018-12-11 18:00:05 UTC,I also see this problem in Ubuntu 18.10 cosmic:
1769848,2018-07-24 21:47:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769848,2018-09-29 07:19:00 UTC,I was running into this same issue while trying to copy a CD in K3B (in Pop!_OS 18.04 LTS).
1769848,2018-05-08 10:29:20 UTC,"Another comment: opening a shell and typing ""ulimit -l"" (max locked memory) gives 16384 (ie, 16MB)."
1769848,2018-05-08 09:54:53 UTC,"Further to my last comment, I'm wondering whether the actual number of bytes that can be successfully mmap()ed is determined by how many other pages are already mmap()ed.  Therefore I've set CDR_FIFOSIZE=6m in my /etc/wodim.conf.  Hopefully that will work--I'll test it next time I have a CD-R to burn!"
1769848,2018-05-08 09:47:41 UTC,"The number of bytes being mmap()ed (12587008 bytes) may well be set in /etc/wodim.conf, where the following line appears by default:"
1769848,2018-11-02 06:16:36 UTC,"K3b also does not work for none-root user any longer.
K3b (Format/Erase rewriteable disk..)-> wodim: Operation not permitted"
1769857,2018-11-01 16:04:58 UTC,"Can be the same issue as
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800465"
1769857,2019-06-13 09:20:37 UTC,Sounds like the root cause here is the same as bug 1716857.
1769857,2019-04-19 22:22:44 UTC,This still occurs in 19.04 with nvidia-driver-418.
1769857,2019-03-28 21:18:19 UTC,"The bug is still there on Ubuntu 18.04 with newer drivers and kernel:
nvidia-driver-418
linux-image-4.18.0-16-generic"
1769857,2018-11-16 13:24:36 UTC,I have the exact same bug. This one seems to be related: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465
1769857,2018-11-10 09:51:02 UTC,"I have the same fail, since I updated Nvidia version (to 410), and then even returning to 396, Vulkan doesn't work, with vulkaninfo appears in terminal the same text as nastys."
1769857,2018-11-02 17:56:40 UTC,As a workaround one needs to run (after each reboot):
1769857,2018-10-16 22:19:40 UTC,I can confirm this is still an issue.
1769857,2018-05-09 09:30:05 UTC,I have also added WaylandEnabled=false to /etc/gdm3/custom.conf and Vulkan still doesn't work. I also lost the option to log into Wayland from the login screen.
1769857,2018-05-10 02:40:52 UTC,"OK. Sounds like there is a device (/dev/* file) that you're not getting correct access to. And you can only get around that limitation by running as root (which is not recommended, for security)."
1769857,2018-05-09 18:07:35 UTC,"I have found out just now that if I run anything Vulkan as root (e.g. sudo vulkan-smoketest), IT WORKS! And if I then run it without sudo, IT STILL WORKS!"
1769857,2018-05-09 17:55:23 UTC,"After some investigating, I have found that if I log out, switch to TTY then run startx, I get the same issue. However I noticed that if I run sudo startx, Vulkan works, and it still works after logging out and running startx as a normal user, until the computer is rebooted. Then I tried logging in as root from GDM and I got the same result.
Something is probably not being initialized properly when logging in as a non-root user.
I think the affected package is actually xinit, but I'm not sure."
1769857,2018-05-09 10:45:31 UTC,"I know that VSync and PRIME Sync are not the same thing. With modeset disabled, VSync IS enabled but there is tearing regardless, and I can see that even just by dragging a window around the screen."
1769857,2018-05-09 09:46:38 UTC,"""VSync"" and ""PRIME Sync"" are unrelated things. You need to ignore the fact that they sound similar. You should be able to achieve perfect VSync regardless of the ""modeset"" option. But it may be disabled by default (by Nvidia) as alluded to earlier."
1769857,2018-10-16 21:58:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769857,2018-05-09 09:21:19 UTC,"nvidia-drm.modeset=1 is used for PRIME Sync. In a gist, it copies the framebuffer from the dGPU to the iGPU without tearing. Without this, VSync is not effective no matter what."
1769857,2018-05-09 02:08:29 UTC,"There's probably no way GDM could cause this directly. But indirectly if you are logging into a Wayland session in one case and Xorg in the other, then that might be the main factor here."
1769858,2018-05-23 23:34:25 UTC,"install failed again May23rd,2018; at approx 77% install app crashed; new crash report submitted; just a comment/question - w_scan command works flawless on 16.04 Metv app; does tvtime app use w_scan to detect TV channels?"
1769858,2018-05-23 23:28:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769859,2018-05-08 10:40:18 UTC,may i know how  you build a trove image in kolla?
1769859,2018-05-08 10:41:52 UTC,"Change abandoned by Liu Yang (<email address hidden>) on branch: master
Review: https://review.openstack.org/566846"
1769859,2018-05-08 10:44:24 UTC,"I use DIB, Refer https://docs.openstack.org/trove/ocata/dev/building_guest_images.html"
1769859,2018-05-08 10:54:05 UTC,Can you help me Sir Liu? on what should I input there? This is my first time using trove.
1769859,2018-05-15 08:54:00 UTC,is this applicable to queens?
1769862,2018-06-15 14:36:09 UTC,"I'm having issues with Calibre crashing gnome on 18.04.  When I try to open either Calibre or Ebook Reader, the window opens up to be huge and I can't resize it.  Then Gnome crashes or hangs."
1769862,2019-01-06 18:57:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769883,2018-05-08 18:11:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769885,2019-05-30 14:50:03 UTC,"Hi Alex,"
1769885,2019-05-26 18:51:51 UTC,"Hello,
I downloaded metview 5.3 in Ubuntu 19. It is impossible to read the grib files:
The trace window disappears when you drag a file...
If someone would have a solution or an explanation"
1769890,2018-05-08 17:08:25 UTC,This is fixed in icingaweb2 (2.5.3-1~exp3):
1769890,2021-01-18 10:45:25 UTC,"The verification of the Stable Release Update for icingaweb2 has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1769890,2020-10-29 10:53:16 UTC,"I installed a Bionic VM with the minimal .iso.  Followed my steps to reproduce this fault and got the error in my browser.  I then properly read Brian's instructions on how to use ""proposed"" and now get the Icinga web 2 setup wizard in my browser."
1769890,2020-10-28 19:29:32 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1769890,2020-07-28 21:16:34 UTC,"Hello Jon, or anyone else affected,"
1769890,2020-07-17 22:47:32 UTC,Hi Richard! Apologies for the delay in reviewing your debdiff.
1769890,2020-01-09 00:56:15 UTC,New debdiff attached.
1769890,2021-01-18 10:45:23 UTC,This bug was fixed in the package icingaweb2 - 2.4.1-1ubuntu0.1
1769890,2019-09-16 07:26:24 UTC,The bugfix was merged upstream: https://github.com/Icinga/icingaweb2/pull/3315
1769890,2019-08-15 14:49:43 UTC,Upstream bug: https://github.com/Icinga/icingaweb2/issues/3185
1769890,2018-05-18 09:39:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769890,2018-05-11 17:30:26 UTC,"I'm having the same issue.  Will patch my installation, also.  Thanks!"
1769890,2018-05-09 09:17:26 UTC,I have manually patched my install and that works for me.
1769890,2020-01-08 21:35:59 UTC,"Can confirm in Jan 2020, still an issue with Ubuntu 18.04.3"
1769893,2019-01-09 16:11:34 UTC,I have found that version 2.2.8 that comes with Ubuntu 18.10 works fine.  I downloaded and installed it into Ubuntu 18.04 from https://launchpad.net/ubuntu/+source/cups/2.2.8-5ubuntu1.2 and it asked for login and all admin functions were working as expected.
1769893,2018-10-31 09:40:18 UTC,"I feel that is a bug between the two. I can't do the organization itself of the printer either. In any case, I have discovered that when I include the printer through CUPS along these lines paying little respect to the program, applications in Wine will really observe and utilize the printer. You can visit https://www.browsertechnicalsupportnumbers.com/blog/fix-chrome-err-spdy-protocol-error/ and follow the step to fix the bug issue."
1769893,2018-09-05 13:54:12 UTC,This allowed me to add a Canon IP7200 via the local CUPS httpd:
1769893,2018-08-19 05:16:41 UTC,"@Marcos Teixeira  Unfortunately, I was already part of the lpadmin group before all this started.  So that doesn't work."
1769893,2018-05-10 02:43:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769893,2018-07-24 12:53:05 UTC,I solved using this command
1769895,2018-05-09 02:47:49 UTC,Although Ubuntu 14.04 is still supported it is due to reach end-of-life next year.
1769895,2018-05-08 13:57:53 UTC,"StacktraceTop:
 pa_sink_input_process_rewind (i=i@entry=0xf285f0, nbytes=nbytes@entry=0) at pulsecore/sink-input.c:1063
 pa_sink_process_rewind (s=0xf41e10, nbytes=0) at pulsecore/sink.c:1000
 pa_sink_input_set_state_within_thread (i=0xf285f0, state=PA_SINK_INPUT_RUNNING) at pulsecore/sink-input.c:1922
 pa_sink_process_msg (o=0xf41e10, code=<optimized out>, userdata=0xf285f0, offset=0, chunk=<optimized out>) at pulsecore/sink.c:2486
 asyncmsgq_read_work (i=0xe34c30) at pulsecore/rtpoll.c:564"
1769901,2018-05-08 19:55:58 UTC,"As a data point, we were generally plagued with this issue in RDO 2 (in 2016) until we started explicitly passing the hash as an input at the top level, and stopped (completely) accessing any hashes or repo's via symbolic link."
1769901,2018-05-14 15:28:44 UTC,(tripleo-ci triage)
1769903,2018-10-20 12:45:55 UTC,Thanks for your report.
1769903,2020-02-18 14:46:34 UTC,"This bug is invalid in that the official format is xx.xx.xx, even though in casual use xx:xx:xx sees a lot of use due to influence from other countries."
1769910,2019-03-27 02:29:45 UTC,"That gentoo bug says that failures occur when running in a 32-bit emulator with SMP disabled, and seems to conclude that enabling SMP fixes things.
Was the original failure that prompted the report also on an emulator?"
1769910,2020-01-17 21:22:36 UTC,"I have no 32-bit physical machine, and I don't think anybody else hits this exact problem.
If you'd like still like some help, please advise exactly what to download for the Gentoo install and exactly what parameters to pass to QEMU to elicit a failure.
Otherwise, lacking any further details, I would be inclined to close this as incomplete."
1769913,2018-05-08 15:00:10 UTC,This change was made by a bot.
1769913,2018-05-08 15:46:23 UTC,You may need to run the following from a terminal:
1769914,2018-05-08 14:47:50 UTC,Attaching lsusb -vv of the device.
1769914,2019-07-22 03:44:12 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1769918,2019-03-29 01:16:36 UTC,This issue was fixed in the openstack/magnum-ui 5.1.0 release.
1769918,2018-09-10 05:18:12 UTC,This issue was fixed in the openstack/magnum-ui 4.0.1 release.
1769918,2018-09-05 19:23:06 UTC,This issue was fixed in the openstack/magnum-ui 5.0.1 release.
1769921,2018-05-08 15:30:51 UTC,"I need more details.  Add the details of the apt logs here, specifically the exact errors you're seeing."
1769921,2018-05-08 15:43:24 UTC,"Note that if you are using the nginx.org repository or the PPAs that *all third party repositories are disabled* when you run a `do-release-upgrade`, so third-party-repository-specific things will never be seen, which can lead to the errors you're seeing here."
1769923,2018-07-09 03:48:30 UTC,See also comments in duplicate.
1769936,2018-05-08 16:20:39 UTC,"FWIW, I tried the Position_fix quirking suggestions here: https://wiki.ubuntu.com/Audio/PositionReporting and didn't see any improvement."
1769936,2018-11-11 16:29:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1769936,2018-11-11 16:39:53 UTC,I can confirm this. I tried to record myself speaking and it was as if everything were overamplified to the point that only distorted noise can be heard.
1769936,2020-03-03 07:13:51 UTC,This is still an issue for me in 20.04 -- how can we get some traction on this issue?
1769936,2020-08-14 14:34:10 UTC,"I can resolve the issue by 'suspending' the Laptop, and resume using it again.
The microphone works great after one suspend."
1769938,2019-07-16 13:45:23 UTC,Oh this worked! Thank you.
1769941,2019-09-26 09:30:39 UTC,"I can't identify when it was fixed, but can confirm this is not happening any more in grep 3.1-2build1 in Ubuntu 18.04."
1769957,2018-07-17 11:34:59 UTC,Could be merged with the https://bugs.launchpad.net/kicad/+bug/1778357 development?
1769958,2018-05-14 08:39:51 UTC,It's safe to close the issue. Because it is synced.
1769958,2018-05-08 17:56:58 UTC,Added missing dep3 header.
1769958,2018-05-08 20:42:30 UTC,"The attachment ""fix-clipboard.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1769962,2018-12-13 14:43:15 UTC,I also came across this. For me changing the retry tinmer to 30 does the trick and the deployment is always sucessful.
1769962,2019-01-15 13:31:25 UTC,This happens the same with Rocky version and kolla-ansible 7.0.1 binary
1769969,2018-05-09 02:35:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1769969,2018-05-09 14:20:56 UTC,apport information
1769969,2018-05-09 14:20:58 UTC,apport information
1769969,2018-05-09 14:21:00 UTC,apport information
1769970,2018-05-17 15:03:08 UTC,"Reviewed:  https://review.openstack.org/568371
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=ae322168f65a3ba204795080f6e936356b9b19cd
Submitter: Zuul
Branch:    stable/queens"
1769970,2018-05-23 08:16:31 UTC,"Reviewed:  https://review.openstack.org/550800
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d516ad7da2d86ad03374f8244f6738ee65d6f6a4
Submitter: Zuul
Branch:    master"
1769970,2018-05-10 18:28:17 UTC,"Reviewed:  https://review.openstack.org/567006
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=479daab59b4a1faad3a4ab5b7f6ecc4887ffea3a
Submitter: Zuul
Branch:    master"
1769970,2018-05-14 20:46:12 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/568371"
1769971,2018-05-17 10:37:15 UTC,"this is a compiler issue, with how directory entries with a trailing alternation a compiled."
1769980,2018-05-28 13:34:44 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1769980,2018-05-28 13:41:26 UTC,This bug was fixed in the package linux-firmware - 1.157.19
1769980,2018-05-28 13:44:46 UTC,This bug was fixed in the package linux-firmware - 1.173.1
1769980,2018-05-28 14:23:34 UTC,"Hello Anthony, or anyone else affected,"
1769980,2018-05-28 14:28:22 UTC,"Hello Anthony, or anyone else affected,"
1769980,2018-05-28 14:30:19 UTC,"I have accepted both the xenial and bionic wireless-regdb uploads. One thing that stood out was the __eq__ implementation in the 0001-wireless-regdb-Fix-comparison-of-WmmRule-with-NoneTy.patch patch which seems to look a bit strange (no _as_tuple() before the comparison), but I have been informed that even if it's wrong it will have no impact on the actual package. Just something worth noting."
1769980,2018-06-11 15:27:54 UTC,This bug was fixed in the package linux-oem - 4.13.0-1030.33
1769980,2018-06-13 12:39:19 UTC,"Our QA has tested the packages, all work well."
1769980,2018-06-14 01:12:08 UTC,This bug was fixed in the package wireless-regdb - 2018.05.09-0ubuntu1~18.04.1
1769980,2018-06-14 16:52:25 UTC,This bug was fixed in the package wireless-regdb - 2018.05.09-0ubuntu1~16.04.1
1769980,2018-06-15 14:05:43 UTC,This bug was fixed in the package linux-oem - 4.15.0-1008.11
1769980,2018-05-24 01:00:38 UTC,Revert the verification-* tags as crda has been removed from -proposed.
1769980,2018-06-13 09:30:49 UTC,This bug was fixed in the package linux-oem - 4.15.0-1008.11
1769980,2018-05-23 18:51:59 UTC,"This conflict is causing daily image builds to fail in xenial, so I'm removing the v-failed SRU from xenial-proposed."
1769980,2018-05-23 12:52:21 UTC,crda debdiff for Xenial
1769980,2018-05-23 14:46:20 UTC,"Hello Anthony, or anyone else affected,"
1769980,2018-05-08 19:00:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1769980,2018-05-23 15:59:06 UTC,"Turns out there's a hiccup with the crda update for xenial, unbeknownst to us wireless-regdb is (incorrectly) already installing my public key. The easiest path forward seems to be just leaving crda as is and making the regdb update continue to install my key. As such I'm marking verification for xenial as failed."
1769980,2018-05-09 16:58:09 UTC,@sforshee
1769980,2018-05-09 17:37:44 UTC,"4.13 will also be missing support for the new regulatory database format, so I'd expect the effort to backport there to be similar to that for 4.4."
1769980,2018-05-10 06:30:40 UTC,"Not just the changes to support for the new regulatory database format, but also to support the new firmware, as FW API has bumped and may need to pull in more patches. For example, 3165/7265D/8260 NIC in v4.4 supports FW API from 13 to 19, but the new FW for 3165/7265D has bumped to API 29, and 8260 has bumped to 36."
1769980,2018-05-10 14:05:30 UTC,"I released a new wireless-regdb yesterday with the changes needed for this. I've also prepped an update for cosmic and handed it off to apw for review. Once that's done we can backport to bionic at least. For xenial we will need to confirm that the crda version is new enough to ship with my public key first, otherwise signature verification for the db will fail (as the new package will switch from building the db from source to just shipping the dbs and signatures from the upstream release)."
1769980,2018-05-08 20:37:51 UTC,I'm not sure here whether the xenial nomination is meant to apply to the linux package. If so ...
1769980,2018-05-15 09:25:19 UTC,"Yes, I will send one."
1769980,2018-05-21 13:32:40 UTC,"Hello Anthony, or anyone else affected,"
1769980,2018-05-21 15:58:26 UTC,"Hello Anthony, or anyone else affected,"
1769980,2018-05-21 20:29:12 UTC,This bug was fixed in the package wireless-regdb - 2018.05.09-0ubuntu1
1769980,2018-05-23 03:30:07 UTC,Verified the new firmwares in xenial-proposed and xenial-bionic are correct.
1769980,2018-05-10 14:05:59 UTC,@Anthony: will someone be sending a pull request for linux-firmware?
1769981,2018-05-23 07:43:36 UTC,"Yes, links please."
1769981,2018-05-23 07:54:04 UTC,The last crash is https://errors.ubuntu.com/oops/93aef40e-5deb-11e8-945f-fa163e8d4bab
1769981,2018-05-23 08:11:21 UTC,"> https://errors.ubuntu.com/oops/93aef40e-5deb-11e8-945f-fa163e8d4bab (most recent)
> https://errors.ubuntu.com/oops/c9e22fbe-58dc-11e8-9127-fa163ed44aae
> https://errors.ubuntu.com/oops/385a60b4-334f-11e8-a211-fa163ef911dc
are all bug 1731261
"
1769981,2018-05-23 08:12:37 UTC,If you log in remotely from another machine and watch the log:
1769981,2018-05-23 13:46:38 UTC,"No, I've never seen any message in log that could seem related to the issue."
1769981,2018-05-24 13:01:56 UTC,"Daniel, not sure if they're related, but it seems that when I get back from the ""slide"" screen (even if not locked) I'm getting a lot of these errors repeated in journalctl:"
1769981,2018-05-24 06:26:08 UTC,I only see apparmor audit messages there
1769981,2018-05-25 01:45:01 UTC,For the default Ubuntu installation I believe we have fixed all the log messages that look like that.
1769981,2018-05-29 20:10:33 UTC,"I just had a series of freezes, and managed to ssh and watch logs in the meantime, the only messages that I that might be relevant are the following (repeated many times):"
1769981,2018-05-23 07:31:19 UTC,From the list on that page I can see that a report was indeed uploaded for that crash:
1769981,2018-05-24 01:25:39 UTC,No messages at all just before or just after the freezes?
1769981,2018-05-23 01:51:55 UTC,The next step I suggest is to look up automatic crash reports your system has made:
1769981,2018-05-16 09:12:55 UTC,It gives you several steps that must be followed first to *fix* the problem with not being able to upload it via ubuntu-bug. Please follow all steps.
1769981,2018-05-16 09:05:06 UTC,"That link mentions how to create a crash file, but I do have one, I just can't upload it via ubuntu-bug"
1769981,2018-05-16 07:52:20 UTC,In that case please follow the standard instructions :)
1769981,2018-05-16 07:45:09 UTC,Yes I have a Xwayland crash file in /var/crash with the same timestamp.
1769981,2018-05-16 03:37:00 UTC,That's OK. We can probably ignore most Xwayland crashes anyway. They are mostly just Xwayland dying because gnome-shell crashed...
1769981,2018-05-12 09:23:15 UTC,"Thanks Daniel,"
1769981,2018-05-11 02:07:07 UTC,"If you have a core or crash file then yes please open a new bug, but only by running:"
1769981,2018-05-10 10:56:05 UTC,"@Daniel, I just got a session crash because of this freeze and got an Xwayland core file in my home.
Should I open a different bug? How do I attach the core through apport?"
1769981,2018-05-09 06:24:53 UTC,"FTR this also happens on another PC, also with Intel card (different model), also a fresh Bionic install"
1769981,2018-05-09 02:34:18 UTC,"See also related bugs:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=unlock"
1769981,2018-05-22 18:13:54 UTC,"@Daniel I followed the steps there (specifically, enabling crashes for X). I just got a freeze with subsequent crash and got a new Xwayland .crash file.
Still, running ubuntu-bug on it it just exits with no error when I click to submit, and it doesn't seem to be submitting the bug."
1769988,2020-04-24 11:58:34 UTC,"I'll second this!  I'm working on a parts cleanup project where I have to add parts to hundreds of items at once.  Being able to batch update them would make things go much, much faster."
1769989,2020-10-22 20:01:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu."
1769989,2018-05-08 19:28:50 UTC,"Hi,"
1769991,2019-02-14 15:09:51 UTC,Is that still an issue in 18.04?
1769991,2019-02-14 15:20:14 UTC,"No, this does not affect 18.04, and likely does not affect later versions either.  (Likely due to updated OVPN libraries and such?)"
1769991,2019-02-14 15:20:24 UTC,This does however still affect 16.04.
1769991,2019-02-15 08:57:49 UTC,"Thanks, closing for the current serie then."
1769991,2019-02-19 21:45:02 UTC,seb128: Actually looks more like it affects 18.04 again.  Digging deeper now.
1769991,2019-02-26 15:22:28 UTC,"Deleting the bionic line since it lacks enough details to be acted on at this point and has no owner, if you want to suggest it to be reviewed for that target best to tag it rls-bb-incoming so the team owning the package can review and decide if that's an item they want to own (which is blocking not the case until it has the required details to be worked on)"
1769991,2019-02-26 15:24:13 UTC,"Said differently, a first step would be to add a testcase that others could follow to trigger the bug"
1769991,2019-02-28 16:02:00 UTC,"I""m attaching an example OVPN file with more private details stripped out of it."
1769991,2019-03-05 17:28:52 UTC,"DISREGARD for 18.04, it looks like I have conflicting imports with all the VPN plugins installed for Network Manager that I do."
1769995,2018-05-22 14:01:29 UTC,The package has been published and the bug is being set to Fix Released
1769995,2018-05-22 12:56:56 UTC,This bug was fixed in the package linux-raspi2 - 4.13.0-1020.21
1769995,2018-05-15 11:35:13 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.13.0-1020.21/raspi2-4.13-proposed-published.html"
1769995,2018-05-14 11:39:37 UTC,Hardware Certification have begun testing this -proposed kernel.
1769996,2018-05-14 12:43:11 UTC,Hardware Certification completed with linux-oem 4.13.0-1025.28 (bug 1766599).
1769996,2018-05-15 02:54:02 UTC,We're using cert-testing results here.
1769996,2018-05-22 00:02:41 UTC,This bug was fixed in the package linux-oem - 4.13.0-1028.31
1769996,2018-05-22 13:01:54 UTC,All tasks have been completed and the bug is being set to Fix Released
1769997,2018-05-09 17:03:53 UTC,"I'm hoping this is based off the same 4.15 that's going into bionic, 4.15.0-1010."
1769997,2018-05-16 21:53:05 UTC,Our testing on this kernel is complete and we are good with publishing.
1769997,2018-05-18 03:10:05 UTC,"4.13.0-1017.20 - azure
Regression test CMPL."
1769997,2018-05-22 00:01:48 UTC,This bug was fixed in the package linux-azure - 4.13.0-1018.21
1769997,2018-05-22 13:02:07 UTC,All tasks have been completed and the bug is being set to Fix Released
1770001,2018-05-22 13:02:43 UTC,All tasks have been completed and the bug is being set to Fix Released
1770001,2018-05-18 14:42:42 UTC,"Still missing regression results for i386, setting regression-testing to 'Fix Released' so the release can proceed."
1770001,2018-05-14 10:56:47 UTC,Hardware Certification has been completed on linux-hwe 4.13.0-40.45~16.04.1 (bug 1766594).
1770001,2018-05-14 11:02:27 UTC,"Hardware Certification has been partially completed on linux-hwe 4.13.0-40.45~16.04.1, missing results for i386 (bug 1766594)."
1770001,2018-05-15 02:55:45 UTC,Comment in #2 should be regression-testing.
1770002,2018-05-11 11:43:42 UTC,"4.13.0-1016.20 - gcp
Regression test CMPL."
1770002,2018-05-22 00:01:58 UTC,This bug was fixed in the package linux-gcp - 4.13.0-1017.21
1770002,2018-05-22 13:26:33 UTC,All tasks have been completed and the bug is being set to Fix Released
1770013,2018-05-22 12:34:15 UTC,All tasks have been completed and the bug is being set to Fix Released
1770013,2018-05-16 07:47:53 UTC,"4.4.0-1058.67 - aws
Regression test CMPL, RTB."
1770013,2018-05-21 23:59:52 UTC,This bug was fixed in the package linux-aws - 4.4.0-1022.22
1770015,2018-05-16 09:26:35 UTC,Hardware Certification was completed with linux-lts-xenial 4.4.0-123.147~14.04.1 (bug 1766607). Setting certification-testing to 'Fix Released'.
1770015,2018-05-22 12:34:37 UTC,All tasks have been completed and the bug is being set to Fix Released
1770015,2018-05-14 09:44:33 UTC,"4.4.0-125.150~14.04.1 - generic
Regression test CMPL, RTB."
1770015,2018-05-14 11:39:49 UTC,Hardware Certification have begun testing this -proposed kernel.
1770016,2018-05-22 00:01:34 UTC,This bug was fixed in the package linux-aws - 4.4.0-1060.69
1770016,2018-05-22 13:00:21 UTC,All tasks have been completed and the bug is being set to Fix Released
1770016,2018-05-14 10:51:08 UTC,Regression tests completed for linux-aws 4.4.0-1056.65 (bug 1766614).
1770018,2018-05-22 14:00:52 UTC,The package has been published and the bug is being set to Fix Released
1770018,2018-05-22 12:53:13 UTC,This bug was fixed in the package linux-euclid - 4.4.0-9028.30
1770018,2018-05-14 07:30:07 UTC,The euclid kernel only boots on a very specific class of CPU which cannot be ensured in ADT testing.
1770018,2018-05-16 07:56:52 UTC,Hardware Certification have begun testing this -proposed kernel.
1770018,2018-05-16 09:02:14 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/euclid/4.4.0-9028.30/euclid-proposed-published.html"
1770032,2018-05-10 09:32:09 UTC,Thanks for reporting.
1770032,2018-08-05 14:52:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770032,2018-08-05 14:57:20 UTC,"I have found solutions here - https://stackoverflow.com/questions/51256462/r-cannot-install-rjava-what-is-r-api-3-4
This help me."
1770038,2018-05-15 16:09:28 UTC,This is good info.  I wonder if Windows 10 is adding either a filesystem access timestamp or a filesystem checksum?  Will require more research.
1770044,2019-12-01 18:57:52 UTC,"(In reply to Meinhard Ritscher from comment #43)

> I do experience the crash and
>
> $> lpstat -R
>   0 printer-97            user          316416 Sun Sep 15 22:00:36 2019
>   1 printer-97            user          316416 Sun Sep 15 22:00:36 2019
>   2 printer-97            user          316416 Sun Sep 15 22:00:36 2019
>
> Running on openSuse Thumbleweed on the latests updates. Experience this
> crash since a few days
"
1770044,2019-12-01 18:34:29 UTC,I do experience the crash and
1770044,2019-11-30 09:53:22 UTC,"People that still have this crash. Can you please run
lpstat -R"
1770044,2019-11-30 09:44:13 UTC,*** Bug 414083 has been marked as a duplicate of this bug. ***
1770044,2019-11-15 14:48:28 UTC,"The bug is still present in Kubuntu 19.10 (KDE Plasma 5.16.5), and it appeared two years ago in Kubuntu 17.10."
1770044,2019-11-14 14:11:55 UTC,*** Bug 414058 has been marked as a duplicate of this bug. ***
1770044,2019-10-24 08:04:53 UTC,*** Bug 412269 has been marked as a duplicate of this bug. ***
1770044,2019-10-24 08:04:40 UTC,*** Bug 411870 has been marked as a duplicate of this bug. ***
1770044,2019-10-21 07:14:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770044,2019-10-05 13:48:31 UTC,"Created attachment 123034
New crash information added by DrKonqi"
1770044,2019-09-02 21:07:15 UTC,"FWIW.
That comment about that multiple jobs with the same id shouldn't exist.
I just decided to use the taskbar print-queue viewer (kde-print-queue) and selected ""All Jobs"".
At that point it crashed (but only it - plasma was OK)."
1770044,2019-12-02 17:24:21 UTC,"Created attachment 124272
New crash information added by DrKonqi"
1770044,2019-08-20 19:58:06 UTC,*** Bug 410509 has been marked as a duplicate of this bug. ***
1770044,2019-08-15 21:45:55 UTC,*** Bug 410570 has been marked as a duplicate of this bug. ***
1770044,2019-07-23 07:27:27 UTC,*** Bug 410124 has been marked as a duplicate of this bug. ***
1770044,2019-07-08 09:05:50 UTC,*** Bug 409439 has been marked as a duplicate of this bug. ***
1770044,2019-07-08 09:05:18 UTC,"> Perhaps insertRow() has undefined behavior when the given row index is greater than rowCount()?
"
1770044,2019-02-26 19:02:58 UTC,Confirmed on KDE Neon 5.15.1. Might be due to a network printer which was recognized automatically but now no longer exists. The fixes mentioned above (uninstalling the print-manager) appears to work.
1770044,2019-01-28 22:18:03 UTC,Same here (Kubuntu 18.04.01) - after removing blocked print jobs in CUPS service UI (http://localhost:631/) plasmashell started. Here is my gdb backtrace from the crash before:
1770044,2019-01-25 10:18:34 UTC,I confirm the error (segfault in dmesg) on kubuntu 18.10. Removing the printer spool (/var/spool/cups/*) temporarily fixes the problem. Removing print-manager solved the problem (with the caveats mentioned above - no notify etc.)
1770044,2019-09-17 02:26:41 UTC,*** Bug 411153 has been marked as a duplicate of this bug. ***
1770044,2019-12-02 18:01:06 UTC,"(In reply to Albert Astals Cid from comment #44)

> Right, you have 3 print jobs with id 97, which is why this is crashing.
>
> Do you remember what you did to end up with 3 print jobs with the same id?
> Was your printer off or on or it failed during printing or something?


Not really, no. I would assume the (network connected) printer was switched off. But I'm not certain."
1770044,2019-12-02 22:05:29 UTC,"Git commit c93f2f16c30d10fbd0f4bfb4c0bf0cec07a4c93b by Albert Astals Cid.
Committed on 02/12/2019 at 22:05.
Pushed by aacid into branch 'release/19.12'."
1770044,2021-02-23 06:29:50 UTC,*** Bug 412639 has been marked as a duplicate of this bug. ***
1770044,2020-07-31 19:59:10 UTC,*** Bug 424849 has been marked as a duplicate of this bug. ***
1770044,2020-07-02 20:51:54 UTC,"For what it's worth, this bug is still present in Kubuntu 20.04. Deleting Print-Manager and reinstalling after reboot (and deleting printers) ---as advised above--- seems to have solved the problem---for now."
1770044,2020-04-27 00:43:21 UTC,*** Bug 420576 has been marked as a duplicate of this bug. ***
1770044,2020-04-21 15:14:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770044,2020-04-03 12:34:46 UTC,"Created attachment 127232
New crash information added by DrKonqi"
1770044,2020-03-10 20:42:34 UTC,*** Bug 418717 has been marked as a duplicate of this bug. ***
1770044,2020-03-06 14:26:47 UTC,*** Bug 417537 has been marked as a duplicate of this bug. ***
1770044,2020-02-14 20:31:32 UTC,*** Bug 417462 has been marked as a duplicate of this bug. ***
1770044,2020-02-14 01:40:16 UTC,"A workaround is to cancel all jobs, or at least the duplicates(?)."
1770044,2019-12-02 21:02:46 UTC,*** Bug 414652 has been marked as a duplicate of this bug. ***
1770044,2020-02-14 00:26:03 UTC,Is there any workaround? I'm on 5.18.9? I was trying to use a wifi printer
1770044,2020-02-03 01:08:32 UTC,">>> This is incorrect, as I've just had it happen to me (again) and I'm using Eoan."
1770044,2020-02-03 00:33:16 UTC,>>> no longer affects: 	plasma-workspace (Ubuntu Eoan)
1770044,2020-01-31 15:11:52 UTC,*** Bug 416985 has been marked as a duplicate of this bug. ***
1770044,2020-01-15 23:11:29 UTC,*** Bug 416215 has been marked as a duplicate of this bug. ***
1770044,2020-01-09 09:54:57 UTC,*** Bug 415014 has been marked as a duplicate of this bug. ***
1770044,2020-01-09 09:54:42 UTC,*** Bug 415239 has been marked as a duplicate of this bug. ***
1770044,2019-12-03 18:35:34 UTC,"(In reply to Konrad Materka from comment #49)

> Maybe this should also be reported to Cups team?
"
1770044,2019-12-03 09:09:33 UTC,>>> Anyone knows what exactly happened on Cups side?
1770044,2019-01-23 11:13:36 UTC,"As suggested by @GordonLack I observe that also in a desktop pc it had happened an operation like this immediately before the manifestation of the symptom, precisely the request for a print preview from an application which, however, had not set a program to be used to manage the display. This event is therefore almost certainly the origin of the bug."
1770044,2020-02-13 23:52:30 UTC,*** Bug 417601 has been marked as a duplicate of this bug. ***
1770044,2019-12-03 09:00:42 UTC,Anyone knows what exactly happened on Cups side? Why there were jobs with duplicated Id? Maybe this should also be reported to Cups team?
1770044,2019-01-09 21:38:00 UTC,"The same at me:
plasmashell[2492]: segfault at 0 ip 00007ff4d97b4556 sp 00007ffc42745ad0 error 4 in libkcupslib.so[7ff4d9778000+55000]"
1770044,2018-12-07 20:04:32 UTC,"> Interesting, so you're saying that my boot problem was because
> there were jobs in the print queue?
"
1770044,2018-12-07 20:21:13 UTC,"(In reply to Marcel Martin from comment #28)

> > Interesting, so you're saying that my boot problem was because
> > there were jobs in the print queue?
>
> To be precise: The problem occurs whenever there are at least two jobs in
> your print queue with identical job ids. This should normally not happen,
> but it apparently does sometimes.
>
> When Plasma starts up, it loads various apps, including the one responsible
> for the printer status icon in the system tray. When that one is loaded, it
> goes through the jobs in the print queue and tries to gather information
> about them. When it does so and encounters two jobs with the same id, it
> crashes, taking Plasma with it. At least that is my theory so far.
>
> Did you try 'cancel -a'? It would be interesting to know whether that fixes
> the problem.
"
1770044,2018-05-09 01:14:56 UTC,I've found the two attached crash files for this issue in /var/crash/
1770044,2018-05-09 01:09:24 UTC,A few other things.
1770044,2018-04-24 14:27:24 UTC,"Created attachment 112216
New crash information added by DrKonqi"
1770044,2017-07-11 16:13:01 UTC,*** Bug 382244 has been marked as a duplicate of this bug. ***
1770044,2017-06-26 17:21:17 UTC,*** Bug 381686 has been marked as a duplicate of this bug. ***
1770044,2017-04-30 09:28:19 UTC,"I had the same issue on
Fedora 25
kernel: 4.10.10-200.fc25.x86_64
KDE Plasma: 5.9.4
KDE Frameworks: 5.33.0
Qt: 5.7.1"
1770044,2017-02-09 12:20:39 UTC,*** Bug 325932 has been marked as a duplicate of this bug. ***
1770044,2017-02-09 12:19:47 UTC,*** Bug 361999 has been marked as a duplicate of this bug. ***
1770044,2018-05-20 11:38:53 UTC,"I've had to reinstall 18.04 on this system to make it usable.
It now works - with (essentially) the same configuration and with no change to my $HOME files."
1770044,2017-02-09 12:19:25 UTC,*** Bug 375983 has been marked as a duplicate of this bug. ***
1770044,2014-07-04 16:09:20 UTC,"Created attachment 87557
New crash information added by DrKonqi"
1770044,2014-05-23 09:50:48 UTC,"I can confirm this bug. plasma-desktop crashed on every restart of KDE, until I removed the org.kde.printmanager entry from .kde/share/config/plasma-desktop-appletsrc. This solved the problem for me."
1770044,2014-04-29 02:14:46 UTC,*** Bug 333993 has been marked as a duplicate of this bug. ***
1770044,2013-12-18 10:30:07 UTC,*** Bug 328950 has been marked as a duplicate of this bug. ***
1770044,2013-11-30 02:31:08 UTC,*** Bug 328235 has been marked as a duplicate of this bug. ***
1770044,2013-10-23 00:44:20 UTC,thanks for the new backtrace
1770044,2013-10-22 21:27:57 UTC,"I rebuilt print-manager with debugging symbols, below goes a new backtrace. It crashes everytime plasma-desktop starts."
1770044,2013-10-22 18:53:05 UTC,"Can you reproduce it everytime?
Without debug symbols I can't find out why is it crashing."
1770044,2013-10-19 20:07:38 UTC,"Application: plasma-desktop (4.11.2)
KDE Platform Version: 4.11.2
Qt Version: 4.8.4
Operating System: Linux 3.11.0-12-generic i686
Distribution: Ubuntu 13.10"
1770044,2015-09-02 17:06:01 UTC,"Confirmed. Same issue.
It was working ok until i upgraded some stuff."
1770044,2018-05-21 13:00:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770044,2018-05-17 08:22:02 UTC,"I can reliably reproduce this crash on Kubuntu 18.04. I tried to debug it using the Git version of print-manager. I’m not familiar with the code, so I don’t think I can submit a patch, but I think I can pinpoint the problem."
1770044,2018-06-04 11:22:48 UTC,"Exactly the same issue. Plasmashell segfault with ""error 4 in libkcupslib.so"". Black screen after login, all hot keys work, ALT+F2 works, but no desktop GUI. Removing ""print-manager"" fixed issue, but this is a hotfix."
1770044,2018-12-07 18:54:41 UTC,"(In reply to Marcel Martin from comment #26)

> A temporary fix should be to delete all queued print jobs because the
> problem occurs when there are multiple print jobs with the same id. Then you
> don’t have to uninstall cups and will still be able to print.
>
> On the commandline, you should be able to delete all jobs by running ""cancel
> -a"". Or read <https://askubuntu.com/questions/350334/>.
>
> I have not tested this on my machine as I want to be able to reproduce the
> crash when necessary.
"
1770044,2018-12-07 17:28:46 UTC,A temporary fix should be to delete all queued print jobs because the problem occurs when there are multiple print jobs with the same id. Then you don’t have to uninstall cups and will still be able to print.
1770044,2018-12-07 15:38:03 UTC,"(In reply to saif1988 from comment #24)

> Hi.
>
> Today my KDE Plasma stopped booting normally. Got this libkcups.so core
> dumped error. Works fine after uninstalling cups package. Fedora 29
"
1770044,2018-12-07 15:23:12 UTC,Hi.
1770044,2018-11-17 10:49:17 UTC,"Correction to comment #17 - the ""vanishing"" printer was due to something else, please disregard that part."
1770044,2018-11-17 10:38:44 UTC,Another +1
1770044,2018-11-09 14:01:05 UTC,*** Bug 399400 has been marked as a duplicate of this bug. ***
1770044,2018-05-30 17:06:15 UTC,I first encountered that bug when installing Kubuntu 17.10 on my HP Zbook. I found a turnaround (see below) but the bug reappeared today after upgrading to Kubuntu 18.04.
1770044,2018-10-02 16:21:00 UTC,"Similar behavior in Kubuntu 18.04. Today I sent a print job to a non existing printer and in the next reboot, plasmashell did not start, I only got a black screen.
Removing print-manager fixed the issue for now."
1770044,2018-09-26 14:21:55 UTC,"Btw. I was shocked that a bug in a component could bring down the whole plasma shell. Where is the
design goal of decoupling of components? I mean, I love KDE, but KDEs quality seems to be dependent
on every little app running there? Oh my goodness.... I would have expected a list of components with its status. Something like (unloaded, loaded, active, broken, etc.), but KDE running up and being stable. Something like osgi for KDE? ;-)"
1770044,2018-11-02 10:44:06 UTC,+1 from me.
1770044,2018-08-23 20:19:14 UTC,">> In case it helps, I printed today to a non-existing printer. (Or not connected now)
>> This might be the reason.
"
1770044,2018-06-06 19:14:10 UTC,Random idea:
1770044,2018-08-23 20:58:23 UTC,"Yes, Zaur's post is interesting: it explains why I encountered that problem only on my laptop (which I use at home and at work with several printers), and not on my desktop machines."
1770044,2018-06-06 20:24:45 UTC,"Git commit 5d3c5f7bc4174695af57cf5032a3d4117bd7577c by Daniel Nicoletti.
Committed on 06/06/2018 at 20:22.
Pushed by dantti into branch 'master'."
1770044,2018-06-06 20:25:15 UTC,I'm not sure if this fixes the issue so please try...
1770044,2018-06-06 19:43:39 UTC,"This is really odd, and sadly I could never reproduce it."
1770044,2018-08-07 23:47:46 UTC,Same issue here with Kubuntu 18.04 on an HP EliteBook.
1770044,2018-08-14 03:44:47 UTC,"I can confirm same exact problems as Sergey on a computer that was once a Dell XPS, but has been through so many upgrades, the only original part may now be the power cord!"
1770044,2018-08-23 17:46:14 UTC,Hello.
1770044,2018-08-23 17:53:25 UTC,"Deleting the non-existing printer from printers helped:
1) Delete print-manager
$ apt-get remove print-manager
2) Start plasma
sudo service sddm restart
or
kstart plasmashell
3) Install print-manager back again
$ apt-get install print-manager
4) Open Printers
Alt-F2 -> Printers
Remove the not used printers or all of them and then install the used ones."
1770044,2018-06-11 11:05:44 UTC,"Thanks so much for looking into this! Unfortunately, the crash is still there."
1770046,2018-05-09 01:03:02 UTC,adding version.log attachment
1770046,2018-05-09 01:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770046,2018-05-09 11:55:17 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1770046,2018-05-09 22:00:54 UTC,"Issue does not exist in kernel 4.15.0-15 and earlier, it is only present in kernel 4.15.0-20. Due to other issues not relevant to this bug report, the most current and completely working kernel I am using is 4.13.0-41. I will attempt to test a kernel from the 4.17 range and report back."
1770046,2018-05-09 22:46:54 UTC,Test of mainline 4.17.0-041700rc4 kernel:
1770047,2018-05-15 23:24:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770053,2018-05-09 18:25:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770053,2018-05-09 20:46:03 UTC,Check in terminal
1770053,2018-05-09 13:28:36 UTC,Can confirm this breaks unattended upgrades of 16.04 devices with hwe installed:
1770053,2018-05-10 14:59:38 UTC,Possibly related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767133
1770063,2018-05-11 06:21:41 UTC,"I assume this is a doc update only bug? if that's true, I tagged with 'doc'"
1770063,2018-05-09 06:42:09 UTC,"It's from openstack driver's requirement that we can't specify the vdev as required, since openstack driver doesn't know the vdev of ephemeral disk, it just know the format.
We can update doc to recommend customer to specify the vdev, format and mountpoint explicitly, since if customer want to configure these disk, he already the info for the disk he want to configure. Will update doc for it."
1770063,2018-06-20 07:10:23 UTC,has this been fixed?
1770063,2018-05-16 02:43:10 UTC,https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/411352
1770065,2018-06-13 05:41:49 UTC,I think this is caused by IP conflict issue?
1770065,2018-06-13 05:53:36 UTC,"no, the root cause is cloud-init startup process seems have some either code bug or configuration issue , in any case the described step can reproduce this error in mass test (our CI ,for example)"
1770066,2018-06-02 20:49:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770066,2020-08-10 00:27:34 UTC,"kodi 2:17.6+git20171114.2125-final-0xenial
kodi-bin 2:17.6+git20171114.2125-final-0xenial"
1770070,2019-03-10 06:09:20 UTC,"Can reproduce with Inkscape 0.92.4 on openSUSE Tumbleweed 20190301, the suggested filename shown is 'test.svg.png'."
1770070,2019-12-04 09:57:30 UTC,"This appears to have been fixed in 1.0 beta (1.0beta1 (fe3e306, 2019-09-17))"
1770070,2018-05-09 11:19:00 UTC,"- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11), using the Save As Cairo PNG dialog."
1770071,2020-11-02 07:58:38 UTC,Released in charm-helpers 0.20.18
1770071,2018-05-09 05:02:58 UTC,"This is related to, but not the same as, lp:1680860"
1770071,2019-05-03 10:19:59 UTC,There's a little more to this - charmhelpers.contrib.unison does the initial setup which drops (root-owned) authorized_keys and known_hosts onto each unit.
1770071,2020-07-09 05:42:32 UTC,https://github.com/juju/charm-helpers/issues/487
1770071,2019-05-27 23:21:19 UTC,"I ran into this today adding a unit to aws ap-southeast-2.  The IP being ssh'd to was not mentioned in known_hosts, so if the idea is that Juju maintains the file correctly, it's failing to do so here."
1770072,2019-09-19 11:58:09 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1770077,2018-05-09 11:37:02 UTC,"- could you provide details about which operation you are executing?
- for example, are you using the menu item called Extensions->Gcodetools ?
  if so, which specific menu item are you using?"
1770077,2018-05-09 23:29:21 UTC,as far as I can tell this is not part of the standard Inkscape installation.
1770077,2018-05-10 03:00:11 UTC,"Hi Alvin,"
1770077,2018-05-10 03:01:23 UTC,I have attached 3 images.
1770077,2018-05-09 19:37:47 UTC,"HI Alvin,"
1770077,2018-05-10 10:47:30 UTC,"Hi,
okay, after some googling, it seems quite likely that you are probably using this software:
http://makerbot.wikidot.com/unicorn-output-for-inkscape"
1770077,2018-05-10 10:51:59 UTC,just came across this posting which states that the last supported version of Inkscape is 0.48.5.
1770082,2018-11-01 17:23:35 UTC,Verification-done for cosmic using netplan.io 0.40.2.1:
1770082,2018-05-25 13:55:06 UTC,netplan changes are available in git:
1770082,2018-05-25 14:09:47 UTC,I'm not completely sure where the code lives in cloud-init; it looks a bit like what's in:
1770082,2018-05-25 14:12:36 UTC,"""This is why I added
cloud-init to affected packages -- cloud-init should not be second-
guessing the network layer and attempting to do renames / to run"""
1770082,2018-05-25 14:16:25 UTC,"On Fri, May 25, 2018 at 8:48 AM, Mathieu Trudel-Lapierre
<email address hidden> wrote:

> My recommended course of action for cosmic:
>
>  - drop udevadm (net_setup_link) call from cloud-init
"
1770082,2018-05-25 14:23:24 UTC,"On Fri, May 25, 2018 at 9:09 AM, Mathieu Trudel-Lapierre
<email address hidden> wrote:

> I'm not completely sure where the code lives in cloud-init; it looks a
> bit like what's in:
>
> cloudinit/net/netplan.py
>
> But the code does read as though it should not be running 'udevadm test-
> builtin net_setup_link'. However, deploying a system with MAAS shows a
> /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file, which contains
> data referring to the network interfaces:
>
> network:
>   config:
>   - id: ens6
>     mac_address: 52:54:00:31:27:2c
>     mtu: 1500
>     name: ens6
>     subnets:
>     - address: 10.3.99.13/24
>       gateway: 10.3.99.1
>       type: static
>     type: physical
>   version: 1
>
> With that file in place, any netplan config renaming the interface to
> something other than ens6 will see the interface being renamed *again*
> back to ens6, when that file is removed, this behavior does not appear.
"
1770082,2018-06-29 15:19:33 UTC,This bug was fixed in the package netplan.io - 0.38
1770082,2018-11-06 18:13:46 UTC,This bug was fixed in the package netplan.io - 0.40.1~18.04.2
1770082,2018-07-01 09:33:23 UTC,Thanks for the update.
1770082,2018-07-05 09:36:36 UTC,"Could this bug be updated with SRU relevant information? Also, it would also be nice if we had the same changes prepared for netplan.io in bionic."
1770082,2018-07-05 14:59:25 UTC,"Hello Daniel, or anyone else affected,"
1770082,2018-10-23 22:01:08 UTC,"Hello Daniel, or anyone else affected,"
1770082,2018-10-23 22:18:48 UTC,"Hello Daniel, or anyone else affected,"
1770082,2018-10-24 13:02:32 UTC,"Still not working on my side (plain vanilla Ubuntu Server 18.04, fully updated, no cloud)."
1770082,2018-10-26 11:36:28 UTC,Tested just now... It is working for the subiquity installer version (ubuntu-18.04-live-server-amd64.iso) but it does not apply ip address on boot if installed with the debian-intaller version (ubuntu-18.04-server-amd64.iso).
1770082,2018-11-06 15:45:38 UTC,@Marcos:
1770082,2018-11-06 15:42:25 UTC,"Please use bug 1768827 to track such ""no IP at boot"" issues; there's nothing that currently indicates that this is a regression, it needs further investigation, but not here."
1770082,2018-11-06 12:34:49 UTC,@Nicorac: Tested with static IP and had same result.
1770082,2018-11-05 12:52:10 UTC,"@Marcos: same bug on my side.
I was also asked to switch from DHCP to a static IP, to make the configuration as simple as possible and remove any doubt about DHCP server issues."
1770082,2018-11-05 11:46:39 UTC,@Mathieu: I reinstalled my Virtualbox VM (using the ubuntu-18.04-server-amd64.iso image) and tested again and the result was the same.
1770082,2018-11-02 17:52:39 UTC,"Yes, that's because it doesn't appear like the issues you have are a regression caused by the updates, and we don't know what's wrong. You have a bug open for your issue, and we still need to figure out what doesn't work there."
1770082,2018-10-31 23:48:22 UTC,This bug was fixed in the package netplan.io - 0.40.2.1
1770082,2018-11-01 16:51:27 UTC,Verification-done on bionic with netplan.io 0.40.1~18.04.2:
1770082,2018-11-02 17:43:12 UTC,"@Marcos,#80: ubuntu-18.04-server-amd64.iso is exactly the ISO I'm using for my installations."
1770082,2018-11-26 19:24:54 UTC,"Hello Daniel, or anyone else affected,"
1770082,2018-05-25 13:50:25 UTC,My recommended course of action for SRUs:
1770082,2019-05-13 18:51:43 UTC,"For what it's worth, I'm still seeing set-name having no affect on a server's only interface."
1770082,2019-05-08 00:01:20 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
1770082,2019-05-08 00:00:42 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
1770082,2019-05-06 19:52:29 UTC,Still verification-done on bionic and cosmic; this hasn't changed with the new revision in -proposed.
1770082,2019-04-30 21:57:08 UTC,"Hello Daniel, or anyone else affected,"
1770082,2019-04-30 21:03:10 UTC,"Hello Daniel, or anyone else affected,"
1770082,2019-04-18 23:38:55 UTC,A possible SRU regression has been reported against netplan.io 0.96-0ubuntu0.18.10.2 in LP: #1825206.  This version has been rolled back to -proposed while the investigation is ongoing.
1770082,2019-04-15 22:32:43 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.2
1770082,2019-04-11 18:50:53 UTC,"This does not need re-testing, already in bionic/cosmic, just closed again due to changelog for this big backport."
1770082,2019-04-10 21:20:00 UTC,"Hello Daniel, or anyone else affected,"
1770082,2019-04-02 15:15:56 UTC,No need to re-test these; it's already been included in bionic/cosmic and bug comments are a side-effect of the changelogs for the upload with this backport.
1770082,2019-03-29 01:21:25 UTC,"Hello Daniel, or anyone else affected,"
1770082,2019-03-29 01:14:47 UTC,"Hello Daniel, or anyone else affected,"
1770082,2019-03-22 09:21:07 UTC,no need to re-test this on bionic/cosmic
1770082,2019-03-22 09:18:26 UTC,"Hello Daniel, or anyone else affected,"
1770082,2019-03-22 09:11:10 UTC,"Hello Daniel, or anyone else affected,"
1770082,2018-12-05 18:47:48 UTC,This bug was fixed in the package netplan.io - 0.40.1~18.04.3
1770082,2018-12-04 20:22:29 UTC,This bug was fixed in the package netplan.io - 0.40.2.2
1770082,2018-11-29 14:52:52 UTC,Resetting the tags to verification-done as per the discussion above.
1770082,2018-11-26 19:21:26 UTC,"Hello Daniel, or anyone else affected,"
1770082,2018-11-08 17:03:54 UTC,The SRU has been rolled back while the fix for the regression is being prepared.  I still consider the previous SRU verification valid so am resetting the bug state but not the tags.
1770082,2018-11-08 15:05:29 UTC,"This change introduces a regression: calling netplan apply is not idempotent for bonds, see https://bugs.launchpad.net/netplan/+bug/1802322"
1770082,2018-11-07 13:29:24 UTC,This bug was fixed in the package netplan.io - 0.40.2.1
1770082,2018-11-06 20:54:13 UTC,"@Mathieu: Me and Nicorac have the same bug: if set-name is used, there will be no IP at boot. The bug 1768827 is about the same problem as this one (set-name not renaming interface at boot), which is resolved by now...
The strange thing is the inconsistency between the two installation types (subiquity and the legacy debian-installer). Please, could you try and install a vm with the debian-installer and try it yourself? Why does one work and the other doesn't?"
1770082,2018-05-25 13:48:19 UTC,My recommended course of action for cosmic:
1770082,2018-05-24 13:44:25 UTC,"We really only want to be allowed to rename interfaces that have requested it.
This means other interfaces which do not have a set-name directive
will have the kernel name."
1770082,2018-05-24 16:15:34 UTC,That's not the final conclusion; the issue is still being discussed upstream; in particular as to why only the interface name cannot be modified at runtime by .link files.
1770082,2018-05-25 13:45:45 UTC,There are a couple of pieces in play here.
1770082,2018-05-09 13:43:09 UTC,"Works for me. I've been using a config like this for a while, the system sets the interface name at boot as expected:"
1770082,2018-05-09 13:51:48 UTC,Both the original cloudy report and my test use a VM. The issue seems to happen for both virtio and emulated e1000 network hardware.
1770082,2018-05-09 14:00:08 UTC,"Are you providing network config to cloud-init?  Otherwise, cloud-init is going to generate a fallback network config like your original, dhcp on one of the interfaces."
1770082,2018-05-09 14:13:20 UTC,"Ryan: I removed /etc/netplan/50-cloud-init.yaml and rebooted repeatedly and
I've never seen it regenerated."
1770082,2018-05-09 15:36:47 UTC,"On Wed, May 9, 2018 at 9:13 AM, Daniel Axtens
<email address hidden> wrote:

> Ryan: I removed /etc/netplan/50-cloud-init.yaml and rebooted repeatedly and
> I've never seen it regenerated.
"
1770082,2018-05-09 16:39:14 UTC,"Investigating, it appears that the interfaces are getting renamed by udev in the initramfs, which pushes their name_assign_type value to 4, and udev refuses to rename an interface if the name_assign_type value is 4."
1770082,2018-05-11 08:25:13 UTC,"Ryan, I can't get that to work on my systems. What is it that update-initramfs is supposed to change? I don't see any files in my initramfs that are generated or read by netplan. Neither do I see netplan itself in the initramfs!"
1770082,2018-05-11 14:24:24 UTC,"Ok, so the bit I'm stuck on is how the link files and the netplan generator are getting pulled into the initramfs then."
1770082,2018-05-11 14:35:55 UTC,"I'm just verifying that on my end;  note that the 99-default.link is
going to be sufficient to trigger a rename from eth0 to ens3; which
then prevents any rename once we mount root."
1770082,2018-05-11 14:51:27 UTC,"root@rharper-b1:~# vi /etc/netplan/50-cloud-init.yaml
# changed the set-name: to eth_lan
root@rharper-b1:~# netplan generate
root@rharper-b1:~# cp /run/systemd/network/10-netplan-ens3.link
/etc/systemd/network/"
1770082,2018-05-11 15:18:25 UTC,"Right. Yes, I can replicate that, thanks heaps!"
1770082,2018-05-11 17:27:55 UTC,"On Fri, May 11, 2018 at 10:18 AM, Daniel Axtens
<email address hidden> wrote:

> Right. Yes, I can replicate that, thanks heaps!
"
1770082,2018-05-11 12:09:39 UTC,"On Fri, May 11, 2018 at 3:25 AM, Daniel Axtens
<email address hidden> wrote:

> Ryan, I can't get that to work on my systems. What is it that update-
> initramfs is supposed to change? I don't see any files in my initramfs
> that are generated or read by netplan. Neither do I see netplan itself
> in the initramfs!
"
1770082,2018-05-14 08:21:48 UTC,"The attachment ""link-files-in-run.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1770082,2018-05-15 02:58:35 UTC,"This is not a full solution. In Xenial this renaming works even if initramfs has *not* been updated and there is no 70-persistent-net.rules file in the initial ramdisk. I'm still figuring out why this is, but it means that even if my patch were applied, there would be a regression in bionic vs xenial."
1770082,2018-05-15 16:56:32 UTC,"Can you provide the journalctl -b output for the boot that does this
rename?  Is the reproduce the same, can you provide your steps and
I'll replicate."
1770082,2018-05-15 17:29:26 UTC,"Hi Ryan,"
1770082,2018-05-24 15:50:30 UTC,As discussed on https://github.com/systemd/systemd/issues/9006
1770082,2018-05-15 18:22:00 UTC,"Note, that uvt-kvm is going to use cloud-init;  how are you making
sure that cloud-init isn't doing the rename itself?
Xenial by default doesn't use netplan; it still uses eni;  the network
configuration generation in cloud-init using eni
does create a 70-persistent-net.rules file that handles renames on
subsequent reboots;  in a netplan world (bionic)
the .link file is meant to be the equivalent of a .rules file."
1770082,2018-05-16 00:55:28 UTC,"> Note, that uvt-kvm is going to use cloud-init; how are you making
> sure that cloud-init isn't doing the rename itself?
"
1770082,2018-05-16 01:52:58 UTC,Opened https://github.com/systemd/systemd/issues/9006
1770082,2018-05-22 11:30:20 UTC,"I was struggling with this for quite some time and played around using netplan.io and not using it. I figured out that you need to run ""update-initramfs -u"" to make settings persist reboots in ""/etc/systemd/network/"" when not using netplan.io."
1770082,2018-05-24 11:56:35 UTC,"Things seem to work when i change the NamePolicy in the initrd file /lib/systemd/network/99-default.link to
`NamePolicy=kernel`"
1770082,2018-05-24 11:57:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770082,2018-05-14 04:41:29 UTC,"Ok, how does this look?"
1770084,2018-05-09 07:03:10 UTC,"After more discussion, all module exceptions (NetworkOperationError, GuestOperationError, ImageOperationError) would be converted to internal error in wsgi layer."
1770084,2018-05-11 06:30:47 UTC,https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/410758/
1770086,2019-09-12 13:45:07 UTC,Bootstrap and Upgrade should never happen in the same run - marking as Invalid.
1770093,2020-04-16 12:52:10 UTC,"Ack, good point thanks - I updated the patch to:"
1770093,2020-04-14 11:57:05 UTC,I'm not sure we should be encouraging people to try the installer on the Pi (for which we provide pre-installed images instead); still I don't see any particular harm in adding support for this to ubiquity for those that want to play with it.
1770093,2020-04-12 14:25:57 UTC,removing ubuntu-sponsors while I try to get feedback and sponsor this.
1770093,2020-04-12 14:18:12 UTC,"@adamsmith I simplified your patch down to a 1-liner, can you verify it still fixes it for you?  I have test builds in case it helps here:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1770093"
1770093,2019-06-26 07:57:15 UTC,"@Simon, I disagree with that, there is a patch and it's useful to have sponsors visiblity on it, I'm subscribing the team back, it's not because a patch isn't a debdiff including the packaging that it can't be reviewed/sponsored"
1770093,2019-06-25 15:43:12 UTC,Unsubscribing the Ubuntu Sponsors Team from this bug report as there is nothing to sponsor; this patch needs to be reviewed and turned into a debdiff for that to happen.
1770093,2019-02-05 21:58:40 UTC,"Apologies, it appears the filename path is missing from the patch.  The file is fstab.d/basic"
1770093,2018-05-09 08:41:12 UTC,"The attachment ""Patch for partman-basicfilesystems"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1770093,2020-04-21 22:02:11 UTC,"> are you aiming for the 20.04 release
"
1770093,2020-04-21 12:10:03 UTC,"Sorry for the slow reply.  Launchpad bug report messages seem to end up in my junk folder.  I currently don't use the pi at the moment so can't test the patch immediately (are you aiming for the 20.04 release?).  The patch testing for the raspberry pi seems sensible.  My only issue with your patch is dropping the ""defaults"".  This seems to always be applied in pi images, but I've no clue if it is redundant."
1770093,2020-11-17 15:36:40 UTC,"I'm still on cc for this bug, so if someone can verify the proposed patch, I'll work on it, but I'm going to remove myself as assignee until that time."
1770093,2020-08-18 16:59:09 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1770093,2021-01-17 04:17:27 UTC,[Expired for partman-basicfilesystems (Ubuntu Bionic) because there has been no activity for 60 days.]
1770093,2021-01-17 04:17:28 UTC,[Expired for partman-basicfilesystems (Ubuntu Xenial) because there has been no activity for 60 days.]
1770093,2021-01-17 04:17:30 UTC,[Expired for partman-basicfilesystems (Ubuntu) because there has been no activity for 60 days.]
1770093,2021-01-17 04:17:32 UTC,[Expired for partman-basicfilesystems (Ubuntu Focal) because there has been no activity for 60 days.]
1770108,2018-06-07 04:02:30 UTC,"So yo do have -extra package.
Please run `apport-collect` when the issue happens."
1770108,2018-05-09 08:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770108,2018-06-04 03:47:15 UTC,I guess the linux-image-extra-4.13.0-41-generic didn't get installed. The wifi drivers are in the -extra package.
1770108,2018-06-04 21:22:51 UTC,I only upgrade via the Ubuntu Software Updater whenever it feels like doing so. How do I ensure the -extra package gets installed? Does this indicate a problem with the Updater Software?
1770108,2018-06-05 03:36:21 UTC,"Please attach the output of
$ dpkg -l | grep linux | grep extra"
1770108,2018-06-06 22:18:09 UTC,"I have attached the output of ""dpkg -l | grep linux | grep extra"". The output of that command was the same across both kernels 4.13.0-43-generic and 4.13.0-39-generic."
1770108,2018-06-02 22:48:38 UTC,"I am facing this same problem with 4.13.0-41-generic as well as 4.13.0-43-generic. When I boot in either of those kernels, I first get a black screen with a dialog box saying: ""The system is running in low-graphics mode - your screen, graphics card, and input device settings could not be detected correctly. You will need to configure these yourself."""
1770108,2018-06-07 08:22:54 UTC,"I already uploaded the output of 'apport-collect 1770108' on 2nd June showing when the issue happens on 4.13.0-43-generic, and when there is no-issue on 4.13.0-39-generic. Please read my corresponding comment on 2nd June as well."
1770108,2018-06-21 09:27:55 UTC,Arful is reaching EOL so please try Bionic. If the issue persists then we need to fix it.
1770114,2018-05-14 14:34:55 UTC,possible duplicate of #1532508?
1770116,2018-08-06 07:55:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770116,2019-10-04 04:26:55 UTC,"Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!"
1770124,2018-05-09 15:37:51 UTC,"This is a bug with some packages after the upgrade to Ubuntu 18.04 not with the software which provides the release upgrade process, subsequently I'm changing the package to smartlist as a start."
1770124,2019-07-10 22:23:49 UTC,"This bug can be closed.  I determined the issue was a permissions problem and not a package problem.  My mail systems started out as CentOS6 machines, CentOS6 used the uid of smartlst for the list owners, and consequently the suid uid of various programs had to be smartlst.  When I switched to ubuntu it wanted them to be 'list' but this broke the existing permissions schemes.  Right now I have one Centos server and two Ubuntu servers sharing the smartlist directory.  When the last remaining Centos system is replaced with Ubuntu (something in process), I will change all the ownership to list, in the meantime I've changed the suid programs to uid smartlst and everything is working."
1770124,2019-09-11 00:47:03 UTC,"I reiterate since this is still open, this bug report can be closed.  The issue was a permissions
issue.  Upgrade changed ownership of some files which would have worked if I only had Ubuntu machines but some of my mail servers are redhat which need a different owner and smartlist files are shared
so can only be one or the other.  Not a problem with package per se', just a compatibility issue between two different distros."
1770124,2020-04-21 05:26:05 UTC,"This can be closed, this turned out to be a permissions problem.  I had both Ubuntu and Centos mail servers, ubuntu wants the list files to have a group of ""list"", and Centos ""smartlst"".  I had them NFS mounted across several servers.  It was the different OS's fighting over what GID these files should be that caused the problem.  I moved the last CentOS server to Ubuntu, set the group ID's to ""list"", and now everything is good.  This bug can be closed."
1770124,2018-05-09 09:52:26 UTC,"Also this attached may reflect the 17.10 versions of postfix, procmail, and smartlst but this is only because I tried downgrading each of these packages in an attempt to isolate which package(s) were the problem but the problem remained even with all three downgraded to the 17.10 versions."
1770125,2018-05-09 09:16:25 UTC,This may be a related topic - https://review.openstack.org/#/q/topic:update-tox-files+(status:open+OR+status:merged)
1770127,2018-05-28 10:50:17 UTC,"One, straight forward, but potentially noisy way to fix this is to use the type system to prevent the propagation of invalid data. Replacing the existing `string` type with a `net.IP` type throughout the program would ensure that all code paths are in an IP format and force the code to explicitly resolve any hostnames on input."
1770127,2020-03-04 21:14:07 UTC,This was fixed as of version 2.4.
1770127,2018-05-28 23:17:25 UTC,https://github.com/juju/juju/pull/8776
1770129,2020-02-29 17:09:31 UTC,"This is not a leafpad issue. For me, the problem still happens in Lubuntu 19.04, but it happens with the Vivaldi web browser. Maybe I'll upgrade to 19.10 this weekend to see if the problem goes away."
1770129,2020-01-12 18:24:23 UTC,"I assume that leafpad issue is solved on Lubuntu 19,10.
I think gedit is not the default text editor on Lubuntu, even not included in the installation iso so i don't know if that could be an issue,"
1770129,2018-05-12 18:44:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770129,2019-12-23 14:02:58 UTC,But not present with leafpad 0.8.18.1 on Lubuntu 19.10.
1770129,2019-12-23 13:51:14 UTC,Same problem with gEdit on Lubuntu 19.10 (kernel 5.3.0-24-generic)
1770129,2019-09-05 17:03:06 UTC,I confirm this on Lubuntu 18.04.3 kernel 5.0.0
1770129,2019-09-05 17:01:17 UTC,Is this finally fixed ?
1770129,2018-05-16 04:40:55 UTC,"I can confirm it occurs in Bionic. The fact that you have a machine that does not show this message is remarkable to me, as GTK apps tend to be really noisy, showing all sorts of bad looking messages when run from terminal. In fact, I would call that expected behavior. That said, especially given everything otherwise works fine, this is extremely low on the priority list."
1770129,2018-09-06 15:43:29 UTC,"No, it doesn't. If hplip shows it and fails and leafpad shows it and succeeds, you have two completely different situations."
1770129,2018-09-06 15:28:55 UTC,"OK, I agree that leafpad works fine. However, the present bug is not leafpad specific, leafpad is not even mentioned in the bug description: ""G_IS_DBUS_CONNECTION (connection)' failed "". I think that collecting the related bugs under this heading, instead of scattering them into several minor sections, would be more informative and effective. I'd say it makes sense ;)"
1770129,2018-09-06 15:06:06 UTC,"I meant everything works fine.... with leafpad. Note too that few users actually launch graphical applications from the command line, at which point the noisy errors are all but unnoticed."
1770129,2018-09-06 14:51:52 UTC,"@Walter Lapchynski
""Everything otherwise works fine""; surely not. For example, the installation program of hplip just crashed with ""GLib-GIO-CRITICAL **: 16:14:04.867: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed"" after the GUI dialog screen was launched and I pressed <Continue> (the error message was repeated three times and the installation program hanged up). I restarted the installation choosing ""interactive"" instead of ""GUI"" (which was the default choice) but I had to uninstall the previous failed installation, which had already written stuff on disk etc.
I would expect that any installation or script that launches a GUI from terminal would be affected.
At any rate, the bug makes for extremely bad publicity for Ubuntu and Linux. It's a CRITICAL error that keeps coming up; as if the aircraft's rocket engines sputtered and stuttered all the time but the crew tried to reassure you by saying, ""don't worry, everything otherwise works fine"". Some googling shows that quite many people are affected by the bug, both in Ubuntu and in other distributions.
In my opinion, this should be high on the priority list."
1770131,2018-05-10 16:54:47 UTC,"Hi,"
1770135,2018-05-09 18:38:14 UTC,"The bug seems to be related to the alternative toolbar once again. When disabling the alternative toolbar, Rhythmbox works stable without those crashes."
1770135,2018-06-20 12:04:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770135,2018-06-20 12:03:14 UTC,"Can confirm this bug. Works fine, when alternative toolbar is disabled (thanks for the hint!)."
1770141,2019-09-30 11:59:08 UTC,"Marking this as Invalid, since the new test runs hows as skipped."
1770141,2019-05-14 04:28:18 UTC,Only echoing info when that requires an user action:
1770141,2018-05-09 14:01:27 UTC,"Ah, the timing might explain the results discrepancy I will check."
1770141,2018-05-09 12:47:07 UTC,"Hi Mark,"
1770151,2018-05-09 13:55:41 UTC,"So the reason why these tests are not executed in our current tempest job is because they are tagged as ""slow"" [0]. We disable all slow tests [1] because running them as part of the current tempest job might cause it to timeout."
1770151,2019-04-12 10:57:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/652041"
1770151,2018-05-09 12:05:20 UTC,version Queen
1770151,2018-06-19 06:37:24 UTC,"Someone is working on creating a separated job for those tests that marked as ""slow"""
1770151,2018-05-10 12:02:58 UTC,"@Eran, absolutely yeah. I think we indeed will need a separated job for those tests"
1770151,2018-05-09 14:09:10 UTC,Removed the queens tag because we don't run it in any branch
1770151,2018-05-10 05:47:50 UTC,"Don't we want to add them to get more coverage & quality?
Maybe we need a separated job/gate for it?"
1770151,2019-04-17 16:10:52 UTC,"Reviewed:  https://review.openstack.org/652041
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=ea6977cfed7b5205014c484e7a33d3be9a55129e
Submitter: Zuul
Branch:    master"
1770155,2018-05-10 19:30:38 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1770155,2018-05-09 18:26:05 UTC,apport information
1770155,2018-05-09 18:26:01 UTC,apport information
1770155,2018-05-09 18:25:58 UTC,apport information
1770155,2018-05-09 18:25:56 UTC,apport information
1770155,2018-05-09 18:25:54 UTC,apport information
1770155,2018-05-09 18:25:52 UTC,apport information
1770155,2018-05-09 18:25:46 UTC,apport information
1770155,2018-05-09 18:25:45 UTC,apport information
1770155,2018-05-09 18:25:37 UTC,apport information
1770155,2018-05-09 18:25:35 UTC,apport information
1770155,2018-05-09 16:02:25 UTC,more info on the attachment
1770155,2018-05-09 16:01:16 UTC,"yes sir, it is go away after boot back into the prior kernel version"
1770155,2018-05-09 14:23:25 UTC,Does this bug go away if you boot back into the prior kernel version?
1770155,2018-05-09 12:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770155,2018-05-09 18:25:49 UTC,apport information
1770155,2018-05-09 18:25:42 UTC,apport information
1770155,2018-05-09 18:25:33 UTC,apport information
1770159,2019-11-12 04:17:51 UTC,[Expired for kolla because there has been no activity for 60 days.]
1770159,2019-09-12 13:46:05 UTC,Is this still valid? Can you please reproduce this bug with latest code?
1770163,2018-05-09 15:54:35 UTC,"Note that android studio is available as a snap package, you might want to give it a try:"
1770163,2018-05-13 01:21:28 UTC,"Thank you very much for your feedback. My system is normalized, working OK."
1770163,2018-05-09 16:41:35 UTC,"The attachment ""error"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1770163,2018-05-09 15:53:03 UTC,"Per attached screenshot, what crashed is systemd-logind."
1770167,2018-05-09 14:03:37 UTC,"Please correct affected package to ""ghostscript"""
1770167,2018-05-10 08:17:07 UTC,Thanks for reporting.
1770167,2018-06-27 13:29:56 UTC,"There is also a regression in 9.22, see https://bugs.ghostscript.com/show_bug.cgi?id=698713. Updating to 9.23 would be very welcome."
1770167,2018-10-02 13:41:17 UTC,"Hello, thanks for reporting this issue.
Ghostscript has been updated to 9.25 in current releases of Ubuntu."
1770167,2018-05-15 15:01:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770168,2019-12-24 10:52:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770168,2019-02-12 13:03:14 UTC,any update on this? this is still an issue
1770170,2018-05-09 14:12:50 UTC,"(unsure whether this is a Caja bug, or an Ubuntu MATE bug with its emoji overlay, so adding references to both.)"
1770173,2018-06-22 16:53:08 UTC,"Sorry, this is my first time trying to debug os-level installer. I don't know how to switch the install from auto to manual, then back to auto."
1770173,2018-06-19 20:02:12 UTC,What sort of system is this on and can you reproduce it?  If so can you edit /usr/bin/os-prober and add an x to the set -e line at the top of it then reproduce the issue to get more information?
1770173,2018-06-22 17:51:16 UTC,"The interesting information I'm trying to get is exactly where os-prober froze, so if it finishes correctly then that information isn't going to help.  I think at that point in the installer if you look, you will see the hard disk mounted under /target, and it has its own copy of os-prober, so make sure that it has the set -ex and let the installer install grub, and if it freezes there again ( and you should also check ps aux | grep os-prober to see if the process is still running ), then at that point all of the debug output should be in /var/log/syslog and we should be able to see where it was when it froze."
1770173,2019-04-05 18:35:25 UTC,"Even after removing all drive partitions from the ZFS drives, I am still having this problem."
1770173,2018-06-08 22:49:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770173,2018-08-18 02:12:58 UTC,"same bug, when I install http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.1-server-amd64.iso  with kinston datatraveler 2.0"
1770173,2018-06-22 14:46:12 UTC,Did it get stuck that time?
1770173,2018-06-22 14:32:48 UTC,I've attached the os-prober output when run as the install was waiting for me to confirm installing grub on the master boot record.
1770173,2018-06-21 17:54:46 UTC,"Hrm.. if the second line shows ""set -ex"" then running os-prober should produce a lot of debug output showing every line of the script that is executed.  Oh, try running it yourself instead of letting the installer do it."
1770173,2018-06-21 06:16:30 UTC,"Yes, its reproducible."
1770173,2018-06-22 18:44:46 UTC,"Ok, I understand now what your previous question meant."
1770173,2018-06-22 19:04:55 UTC,"If it isn't os-prober that hung, then I'll have to look up the next step the installer takes.  Or you might see some other program in ps that is hung and the installer is waiting on."
1770173,2018-06-23 14:54:07 UTC,"Problem solved. There was a USB stick plugged directly in to the motherboard which I had forgotten about since changing this box over from a freeNAS install. Once that was removed, the install completed with no hangup."
1770173,2019-04-05 14:28:04 UTC,"I have just run into this same problem on both 18.04 Server and 19.04 Server Beta. After finding this bug report, I unplugged the drive array full of ZFS disks and the local write cache disk only to still run into the issue due to my nvme used for read cache."
1770173,2018-06-25 14:18:59 UTC,"Strange, yes, a USB stick should not cause it to hang.  I'm still not seeing the output of os-prober with the set -x option working.  Also you were able to manually run it with this zfs usb stick plugged in and it did not hang right?"
1770173,2018-06-27 04:13:45 UTC,"Ok, new experiment. I'm including the steps here and in an attached README along with outputs captured at various points in the process in a tar.gz file."
1770173,2018-07-01 19:34:56 UTC,So it looks like it is getting stuck running this command:
1770173,2018-06-26 21:51:54 UTC,-- I'm still not seeing the output of os-prober with the set -x option working.
1770176,2018-06-27 20:33:59 UTC,I am also seeing very similar effects. The menu doesn't show the wifi connection points at all and sometimes the network icon in the top panel disappears completely.  As others have found control via Settings works fine. Ubuntu 18.04 on a Lenovo Lifebook.
1770176,2018-05-30 14:57:08 UTC,"I've update all packages this morning, but they don't fix this.
Please note that this behavior doesn't always show (very often but not every time).
I can confirm that when it occours, I can manage wifi, ethernet and VPNs profiles from Gnome Control Center, but not from gnome top menu."
1770176,2018-05-29 16:57:43 UTC,"Since yesterday's update, it is working now."
1770176,2018-05-29 09:27:07 UTC,Some follow-up.
1770176,2018-05-29 09:18:46 UTC,Same here. I'm using lang pt_BR. I upgraded from 17.10.
1770176,2018-05-29 09:11:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770176,2018-08-02 07:45:37 UTC,"Just discovered the following: If I connect via WiFi to my network everything works as expected. But then when I disable automatic connect for wireless, and instead acitvate for a cable connection the auto connect, then after a reboot the above described problem arises."
1770176,2018-08-02 07:18:49 UTC,Same here. I am using a Dell Precision M4800. It seems the status panel does not reflect the true state of the network.
1770179,2018-05-09 16:33:42 UTC,"@Tommy, to be clear, the bug isn't the 202 response, it's that the group snapshot status wasn't actually updated, or at least there is a race when updating it."
1770179,2018-05-10 06:38:11 UTC,"@Matt, oh, thanks :)"
1770179,2018-05-11 12:11:15 UTC,I also just saw this on pike:
1770179,2018-07-25 14:23:28 UTC,"Based on the bug that was just duped here that had a traceback, that looked like a test issue in that it was looking for the transient ""creating"" state, but it had already transitioned to the ""available"" state. The test should probably be updated to allow for either if it doesn't catch the transition in time."
1770179,2018-08-05 01:22:32 UTC,Doesn't appear to actually be that state transitions too fast. The test explicitly tries setting each status:
1770179,2018-09-13 22:28:09 UTC,Is it possible there are multiple tests changing state on the same group at the same time somehow?
1770179,2018-09-13 22:29:15 UTC,Or is it possible that there is some kind of periodic task which is changing the status? I just don't understand how this could be a race when the API call is synchronous.
1770179,2018-05-09 15:46:11 UTC,"Most of cinder's reset status actions are returning 202 instead of 200, I think we can fix them all."
1770181,2018-05-09 15:54:12 UTC,"Just to clarify, I think the UI should access the 403 response provided by the glance API and let the user know they are being denied with a 403 and given the error message from glance which is ""403 Forbidden You are not authorized to complete publicize_image action.    (HTTP 403)"" because otherwise the UI user would have no idea whats going on."
1770182,2018-05-09 15:31:36 UTC,I think the easiest way is to press ctrl+d just before clicking apply ?
1770182,2018-05-09 16:55:13 UTC,That work for a few steps but not is an easy way if you had to do that one hundred times. For something professional softwares have that option.
1770182,2020-04-07 12:38:00 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1770186,2018-05-09 15:37:03 UTC,"An unfinished stub was removed here:
https://github.com/mixxxdj/mixxx/pull/1240"
1770187,2018-07-10 21:06:45 UTC,"I can confirm this under Ubuntu 18.04 and 0.6.7-1. There seems to be sporadic freezes on startup, and a reproducible one on shutdown (eventually Variety has to be force killed by a watchdog thread)"
1770187,2018-07-10 21:07:35 UTC,"In other words, I would really appreciate some help on this issue :("
1770187,2018-07-12 10:05:44 UTC,"Hi James. I think it would be a great loss of time to search for a hard-to-tracedown GTK-related bug in those dialogs that serve a feature that has been long non-working, and are no longer there in the current release. I think the right action here is to backport the removal code - while huge in ""footprint"", those changes are mostly fairly trivial."
1770187,2018-09-30 17:46:18 UTC,Why wouldn't you just bump the release version? Especially since the bug is fixed and 18.04 is an LTS
1770187,2018-09-30 18:37:30 UTC,"In a perfect world yes, updates could be delivered in a timely fashion and we wouldn't suffer from any issues. But the SRU process is long[1], and I'm not convinced that trying to push a massive shift from Python 2 -> 3 would be appropriate."
1770190,2018-05-09 16:27:39 UTC,"My issue turned out to be that the Bionic Beaver (18.04) libdouble-conversion1 package does not contain the .so files, but the Artful ones do.  I downloaded the Artful package and now the thg UI starts correctly."
1770190,2019-04-17 23:27:06 UTC,"Your `lsb_release -a` is still showing 18.04 bionic, are you sure you're on 18.10 cosmic like your title implies?"
1770190,2019-05-31 13:53:11 UTC,"Thanks, yes, it was an failed upgrade even though the UI (or I mistakenly thought the UI) showed that it had completed.  All systems are upgraded to 18.10 w/no issues. I posted it to see if anyone else was having this issue. This can be closed."
1770192,2019-05-13 22:01:58 UTC,"This sounds like more of a feature request than a bug. Marked it as wishlist for now, but feel free to push back if you think that the behavior as written is truly unexpected."
1770195,2019-06-10 23:27:15 UTC,"No, we do not wish to support weak-ssl-ciphers, they are long obsolete and dead."
1770195,2019-08-10 04:17:30 UTC,[Expired for openssl (Ubuntu) because there has been no activity for 60 days.]
1770200,2018-06-22 14:25:33 UTC,"I'm not sure how big your backup is, but my most frequent suggestion is to get a USB hard drive and backup to that first using the file:// schema.  Then, once you have verified that, you can rsync to whatever remote storage you need.  This will be much much faster."
1770200,2018-05-10 19:26:54 UTC,Please upgrade to the current version of duplicity.  This will assure that any bugs fixed since your release are available and may fix your issue.  Please try this and report back to let us know how it went.
1770200,2018-05-20 20:54:00 UTC,"Thanks, Kenneth. I've done the upgrade to 0.7.17-0ubuntu0pp. The problem
persists:"
1770200,2018-05-28 15:01:28 UTC,"Error 'First patch in sequence [<duplicity.path.ROPath instance at
0x7f1b1a4927a0>] was a diff' patching <removed>.pdf"
1770200,2018-05-29 03:25:45 UTC,Thanks for the explanation.
1770200,2018-06-02 16:30:33 UTC,Good idea about stripping out incremental sets until you find the problem.  That may be the best way to proceed.  I would move them to another directory instead of deleting just to be safe.  Let me know how it goes.
1770200,2018-06-21 15:11:12 UTC,"I've stripped out all incrementals until it didn't make sense to strip
out more (since I'd be redoing >90% of the backup), did an incremental
backup (no errors), and ran a verify operation. I'm still getting
several dozens of errors, which I've uniq'd after anonimizing the filenames:"
1770200,2020-02-25 19:39:38 UTC,Corrupt files are a fact of life in flaky networks.  Use par2 or similar to help correct this problem.
1770200,2018-06-22 15:38:47 UTC,"Ok, thanks, I can use that as a workaround."
1770202,2018-05-09 17:52:39 UTC,Adding a link to a related/potential dupe bug that includes helpful info:
1770202,2019-05-09 22:17:58 UTC,"For reference, these status codes show up in the 12B segment."
1770202,2019-05-13 18:27:22 UTC,"We just got our first 407 status (Our supplier sent damaged item(s), re-ordered), which Evergreen also had no idea what to do with."
1770202,2019-05-13 19:18:42 UTC,"It *looks* like mapping the EDI codes to cancel reasons is done in EDI.pm around line 782. That was the first place I looked, so it may be somewhere else too/instead."
1770202,2019-05-13 19:39:29 UTC,"+1 to Tiffany's suggestion and Chris' work adding all those codes to a branch.  Also, +1 to expanding the default cancel reasons."
1770202,2020-02-02 20:09:56 UTC,Just ran across our first order status 412 - Order line held awaiting customer instruction.
1770205,2018-11-29 20:39:33 UTC,"Having this issue and it seems to be a problem due to a combination of ""span monitors"" and ""don't reserve space on borders""."
1770205,2018-11-09 17:57:20 UTC,"Although I'm not on Ubuntu this is the only issue I could find about this: I have the same issue with xfce, and it seems like it has something to do with the fact that my main screen is 2560x1440 and my second screen 1920x1080. So my suspicion as a programmer would be that it sees ""1440"" as the edge even on the 1080p screen, so playing a panel at the bottom of my 2nd screen is not detected as being ""on the edge"". My C is too rusty to confirm this suspicion myself though."
1770205,2018-08-13 10:00:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770205,2020-12-13 12:22:29 UTC,"I can add that in my 2x2 monitor arrangement, the panel is reserving space but on the wrong monitor. If the panel is on a monitor on the bottom row, it reserves space on the monitor directly above it instead of the monitor that it's on. Seems to be a variation of @fbernier comment."
1770205,2018-05-09 16:20:35 UTC,Here is a screenshot of my panel config.
1770212,2018-05-09 19:40:16 UTC,"Since EXPAND_WEB_IMPORTS only affects CSS now, with webpack doing the JS-side aggregation, I propose we teach webpack to create evergreen-staff-client-deps.0.0.1.min.css, have the base template load it by default, and deprecate EXPAND_WEB_IMPORTS.  Basically, the same thing we did with the JS.  I don't see any particular benefit to loading the individual CSS files."
1770212,2018-05-10 15:54:30 UTC,Branch pushed:
1770213,2018-05-09 19:57:25 UTC,Sounds similar to https://bugs.launchpad.net/python-swiftclient/+bug/1586690 and https://bugs.launchpad.net/python-swiftclient/+bug/1621581
1770213,2018-05-22 12:39:20 UTC,"Hi Tim, thank you for your fast reply and sorry for my delayed feedback."
1770216,2018-05-21 21:41:18 UTC,This is a known problem.
1770216,2018-06-15 08:20:41 UTC,This also goes for the software-boutique. And only after installing the virtualbox-guest additions. Before installation it works.
1770217,2018-05-09 16:42:54 UTC,Screenshot.
1770217,2018-05-09 17:08:25 UTC,"Confirmed. The count displaying on the Items Out tab and in the patron sidebar incremented after following the steps described by Nathan. Adding a note that if you later retrieve the same patron record, the Items Out counts  display correctly."
1770217,2019-06-10 18:21:48 UTC,"I've pushed a branch here:
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mrisher/lp1770217-items-out-incorrectly-incrementing"
1770217,2019-06-18 15:24:18 UTC,"Issue and fix confirmed.  Merged to 3.2 and up.  Thanks, All."
1770224,2018-05-09 19:07:06 UTC,"That backtracr is something completely different. So what is this about, the locking failure or the resolver? Resolver failures are probably not going to be fixable, or only with guessing and extreme caution."
1770224,2018-08-22 10:04:04 UTC,"This effectively is the ""apt needs a new solver"" bug"
1770224,2018-05-17 15:53:33 UTC,"Resolver, just fixed the trace from the error."
1770230,2020-02-07 19:05:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770233,2018-05-10 22:55:52 UTC,"What has occurred is due to the change of UID_MIN AccountsService has decided that your existing user (501) is now a system user. GDM has then decided that there are no user accounts on the system, so has triggered gnome-initial-setup to create one."
1770233,2018-05-11 02:33:34 UTC,Could you provide more information about this install? When did you originally install Ubuntu? I thought that the minimum UID has been 1000 for several years.
1770233,2018-05-11 06:57:23 UTC,"This is my home laptop and I'm at work right now, but it is a 2013 MacBook Air and I'm reasonably confident that I have never reinstalled Ubuntu---just upgraded periodically---so it was originally installed in 2013 or 2014. It is still working great (and things like suspend/resume works much better now than back then)."
1770233,2018-05-12 09:42:20 UTC,$ cat /var/log/installer/media-info
1770237,2018-05-09 18:13:02 UTC,"okay, i didn't read that i run out of memory. sorry!"
1770239,2020-05-09 08:37:37 UTC,This is fixed
1770240,2018-05-09 21:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770240,2018-05-09 20:45:22 UTC,"root@ubuntu:~# sudo apt install linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-modules-extra-4.15.0-19-generic:amd64
E: Couldn't find any package by glob 'linux-modules-extra-4.15.0-19-generic'
E: Couldn't find any package by regex 'linux-modules-extra-4.15.0-19-generic'
E: Unable to locate package linux-modules-4.15.0-19-generic:amd64
E: Couldn't find any package by glob 'linux-modules-4.15.0-19-generic'
E: Couldn't find any package by regex 'linux-modules-4.15.0-19-generic'
E: Unable to locate package linux-headers-4.15.0-19-generic:amd64
E: Couldn't find any package by glob 'linux-headers-4.15.0-19-generic'
E: Couldn't find any package by regex 'linux-headers-4.15.0-19-generic'
E: Unable to locate package linux-headers-4.15.0-19:amd64
E: Couldn't find any package by glob 'linux-headers-4.15.0-19'
E: Couldn't find any package by regex 'linux-headers-4.15.0-19'
E: Unable to locate package linux-image-4.15.0-19-generic:amd64
E: Couldn't find any package by glob 'linux-image-4.15.0-19-generic'
E: Couldn't find any package by regex 'linux-image-4.15.0-19-generic'
root@ubuntu:~#"
1770240,2018-05-09 19:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770240,2018-05-09 19:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770240,2018-05-09 18:48:31 UTC,"I've purged them and can't reinstall, please help need to test a luks bug."
1770240,2018-05-09 22:13:03 UTC,Unable to run this command.
1770240,2018-05-09 19:14:41 UTC,"No apport-collect required, just need the command to install it."
1770248,2018-09-05 18:44:25 UTC,This behavior is also presenting on Bionic.
1770248,2018-06-13 20:44:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770248,2018-05-09 19:37:33 UTC,"The attached `systemd-analyze plot` output suggests that console-setup ran at the same time as the systemd-tmpfiles-setup service, so I wonder if this is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846256"
1770251,2018-05-14 03:06:19 UTC,"Note: clicking the ""View MARC"" modal in the z39.50 search opens up a modal with the MARC fields really nicely wrapped."
1770259,2018-05-10 05:52:36 UTC,I think doc  also specified the version in the integer form https://developer.openstack.org/api-ref/clustering/#list-profiles
1770259,2018-05-15 00:39:09 UTC,"Here are the code for schema Version:
https://github.com/openstack/senlin/blob/adb039616d375bde09519eb7ff913baae0dd686b/senlin/profiles/base.py#L52
https://github.com/openstack/senlin/blob/adb039616d375bde09519eb7ff913baae0dd686b/senlin/policies/base.py#L52"
1770263,2018-05-09 20:54:47 UTC,"Also ""Bad request."""
1770263,2018-05-09 21:16:55 UTC,"www-browser is a generic alternative - could you post the output of ""update-alternatives --display www-browser"", which should give more information about which browser it is?"
1770263,2018-05-10 17:13:35 UTC,"$ update-alternatives --display www-browser
www-browser - auto mode
  link best version is /usr/bin/links2
  link currently points to /usr/bin/links2
  link www-browser is /usr/bin/www-browser
  slave www-browser.1.gz is /usr/share/man/man1/www-browser.1.gz
/usr/bin/links2 - priority 69
  slave www-browser.1.gz: /usr/share/man/man1/links2.1.gz"
1770265,2018-05-17 12:53:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770268,2019-09-30 20:36:23 UTC,still the same with 18.04.3/19.04?
1770268,2019-10-01 03:29:01 UTC,"Yep, still the same"
1770268,2019-11-30 04:17:47 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1770271,2019-01-22 14:40:32 UTC,mesa 18.2.x is in bionic-proposed
1770271,2019-02-01 07:03:49 UTC,bionic has 18.2.2 now
1770271,2019-01-23 01:41:43 UTC,"@Timo,agreed. And we are not seeing any business need to support VegaM in Xenial in near future (if ever.)"
1770271,2019-03-05 12:52:54 UTC,"bionic has 4.18 backport now, installed with 18.04.2 image or manually via 'linux-generic-hwe-18.04'"
1770271,2018-11-06 09:43:28 UTC,I think we'll just fix this in bionic via the HWE stack update. Backport to xenial would basically mean updating stock bionic kernel/mesa and then backport those to xenial. A big patchset to the kernel is unlikely to get approved..
1770271,2018-07-05 13:30:14 UTC,"kernel support is in 4.18, not sure if cosmic will get that, otherwise these should be backported there too"
1770271,2018-07-05 14:05:42 UTC,"RX VegaM works for me with Mesa 18.1.1 or newer, providing I have Linux 4.18 and the firmware blobs from AMD."
1770271,2018-07-05 13:36:06 UTC,"artful is soon EOL, so not adding this there"
1770271,2018-09-20 07:37:42 UTC,cosmic has 4.18 already
1770284,2018-05-23 08:50:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770284,2018-05-23 08:51:48 UTC,"What exactly do you mean by ""unable to login""? When I try to login with GDM the monitor turns simply black. Another observation is that I cannot switch to tty neither from that black screen nor from GDM before."
1770284,2018-11-12 09:46:16 UTC,The problem is gone for me after upgrading to 18.10.
1770288,2020-02-19 21:38:58 UTC,Is this solved wit cmake?
1770289,2019-06-11 19:30:00 UTC,"Oh, how cool!  And I love the idea of tying acq into the larger picture."
1770289,2019-06-01 00:51:10 UTC,Here's a cool presentation about accessible charts (SVG in particular): https://www.youtube.com/watch?v=ayl2ue9vIFc.  Might be helpful as we think about what sort of user experience we might want for a dashboard.
1770289,2019-06-11 19:07:40 UTC,And yeah....obviously imperfect. Please ignore the Dewey Hundreds report numbers--clearly something is off there! :)
1770289,2019-06-01 21:39:32 UTC,"And for what it's worth, I had a chance to fiddle with this chart library for Angular, and it was really fun and easy to work with: https://github.com/swimlane/ngx-charts"
1770289,2018-12-10 14:13:16 UTC,"Jane, this would definitely be something to think about for us. We've had a lot of interest lately from our libraries in dashboards and visualizing data. I'll have to think on if there are other things that might be desirable to pull out, but what you have looks really good as a starting place."
1770289,2019-06-11 19:05:48 UTC,"Jane et al,"
1770289,2018-12-05 23:21:43 UTC,Here's a prototype of what an acquisitions dashboard might look like.  I created this as an assignment for a UI/UX class.  The desktop version is attached; mobile coming soon.
1770289,2018-11-02 15:51:22 UTC,Here's a low-fidelity wireframe of something that might meet some of our needs (the mobile version).  I'm interested to hear what comments y'all might have.
1770289,2018-06-04 02:04:43 UTC,Related idea: https://bugs.launchpad.net/evergreen/+bug/1395742
1770289,2018-12-05 23:22:02 UTC,Here's the mobile version.
1770294,2018-05-11 17:33:00 UTC,The changelog doesn't show anything new since 1009?
1770294,2018-05-17 10:58:05 UTC,Hardware Certification is not run for cloud kernels. Setting certification-testing to 'Invalid'.
1770294,2018-05-18 06:22:40 UTC,"4.15.0-1011.11 - azure
Regression test CMPL."
1770294,2018-05-21 23:58:06 UTC,This bug was fixed in the package linux-azure - 4.15.0-1012.12
1770294,2018-05-22 12:33:43 UTC,All tasks have been completed and the bug is being set to Fix Released
1770294,2018-05-24 20:30:42 UTC,This bug was fixed in the package linux-azure - 4.15.0-1012.12
1770295,2020-01-06 10:40:21 UTC,"On my desktop, VirtualBox reports 4 physical CPU cores and 8 logical CPU cores. /proc/cpuinfo reports 8 processors. VirtualBox GUI draws 4 CPU cores as green, and the remaining 4 cores as red (with ""invalid configuration"" warning when one chooses more than 4 cores)."
1770295,2020-01-06 10:29:40 UTC,"However when I switched to pure qemu/kvm instance with spice visual interface (without libvirt), hangups continue to occur when building Telegram Desktop using a Ubuntu 14.04 guest (which is the Ubuntu version of choice to build Telegram Desktop). I set BIOS memory timings according to vendor spec, did a memory test - all is okay."
1770295,2020-01-06 09:55:51 UTC,"It certainly doesn't match the initially reported issue about state lock and memory stats.
Please update the bug if this is still an issues with newer versions and the recent updates of buguldey turn out to be nice, but actually unrelated to the initial issue)."
1770295,2020-01-06 09:53:53 UTC,"This is only in 4.0 in Bionic and not in earlier nor in later releases.
Thanks buguldey for reporting back on this."
1770295,2019-12-21 06:48:33 UTC,Seems to be a related bug in libvirt:
1770295,2019-12-21 07:34:57 UTC,"The guest vm occupies 7 cpu cores. Its .vdi was created with virtualbox and after that, imported into virt-manager."
1770295,2019-12-21 07:32:10 UTC,This bug is stable: I receive such hangups on host: Intel i7 (8 cpu cores) with guest vm compiling Telegram Desktop: cd out/Debug/ && make -j7
1770295,2019-12-21 10:55:56 UTC,"Tested with latest libvirt git, commit 7a7d36055ce7c161e9309c7bad7f8e61be31c5b8. No hangup while building Telegram. Vm pauses and unpauses okay. Success."
1770298,2018-05-10 08:38:37 UTC,Just noticed it still appears in RDO cloud jobs: https://logs.rdoproject.org/71/530071/3/openstack-check/gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset035-master/Z5b0135bce708475cbd0a2c86883fa625/undercloud/home/jenkins/repo_setup.log.txt.gz
1770298,2018-05-16 01:27:15 UTC,"@fungi -- yes, but it's down to our usual problems of the whole world not using virtualenvs.  We've always needed a very up-to-date pip as we've had problems in the past with packaged versions not handling the requirements.txt bits we use, and stuff like that which I'm sure you're aware of.  This just ensures there's a late-enough pip when people do ""pip install foo"" that it doesn't blow up.  You really have to have the packages pinned, as mixing the two creates a big old mess."
1770298,2018-05-14 16:10:09 UTC,"This pinning of RPM package versions to avoid clobbering Python libraries which have been globally installed with pip seems like a very fragile workaround, as evidenced here. Ultimately we should avoid mixing different package managers within the same Python context (e.g. with `pip install --local ...` or deep symlinks info virtualenvs)."
1770298,2018-05-11 15:10:50 UTC,Thanks Ian!
1770298,2018-05-10 08:35:44 UTC,"Jobs passed successfully this step, so it's resolved now. Thanks, Ian!"
1770298,2018-05-10 04:36:49 UTC,Images should have been updated ... LMN if this resolves it!
1770298,2018-05-10 03:00:23 UTC,"I think what has happened here is that we pin python-virtualenv, setuptools, and pip packages on our hosts so that packages don't overwrite the upstream versions we install (see [1])"
1770298,2018-05-10 02:35:19 UTC,also seen in the overcloud-deploy
1770298,2018-05-10 02:16:34 UTC,"This happening on the rax cloud, not sure if other cloud providers are hitting the same issue yet."
1770302,2018-05-11 20:29:54 UTC,This bug was fixed in the package ssh-import-id - 5.7-24-g4001a38e-0ubuntu1
1770302,2018-05-17 19:31:26 UTC,"Hello Michael, or anyone else affected,"
1770302,2018-05-20 10:49:33 UTC,Verification done on bionic.
1770302,2018-05-24 23:27:31 UTC,This bug was fixed in the package ssh-import-id - 5.7-0ubuntu1.1
1770302,2018-05-24 23:27:43 UTC,"The verification of the Stable Release Update for ssh-import-id has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1770302,2020-02-11 17:06:28 UTC,This bug is fixed in the 5.8 release.
1770304,2018-08-21 15:29:11 UTC,"Nevermind that last comment. I interpreted it as ""here's a completely separate patch you can forward along, too"" when in fact it's entirely relevant. Sorry for the confusion."
1770304,2018-08-21 14:23:34 UTC,"Theo, you should make a separate bug for that."
1770304,2018-08-21 11:42:11 UTC,The following change could be applied to xfce4-notifyd-config.desktop also:
1770305,2018-05-11 20:29:54 UTC,This bug was fixed in the package ssh-import-id - 5.7-24-g4001a38e-0ubuntu1
1770305,2018-05-17 19:31:36 UTC,"Hello Michael, or anyone else affected,"
1770305,2018-05-20 10:18:23 UTC,"Verification completed, I tested this version:"
1770305,2018-05-24 23:27:31 UTC,This bug was fixed in the package ssh-import-id - 5.7-0ubuntu1.1
1770305,2018-05-24 23:27:45 UTC,"The verification of the Stable Release Update for ssh-import-id has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1770305,2020-02-11 17:06:46 UTC,This bug is fixed in the 5.8 release.
1770306,2018-06-18 23:35:01 UTC,"I did not install the image, just ran it from the USB stick."
1770306,2018-06-18 20:34:05 UTC,"Kevin Dalley, to clarify your comment:"
1770306,2018-06-18 19:37:32 UTC,Finally getting back to this.
1770306,2018-05-26 20:53:40 UTC,Kevin Dalley:
1770306,2018-05-26 08:01:37 UTC,"Kevin Dalley, thank you for reporting this and helping make Ubuntu better."
1770306,2018-05-26 18:20:33 UTC,"Since filing this bug, I have been successfully using lxdm as a worked around, with lxde"
1770306,2018-05-26 17:10:02 UTC,After removing:
1770306,2018-05-26 19:21:13 UTC,Thanks for your suggestions.
1770318,2018-05-15 23:29:43 UTC,This bug was fixed in the package falkon - 3.0.1-0ubuntu1
1770318,2018-06-04 18:57:50 UTC,"Hello Simon, or anyone else affected,"
1770318,2018-07-01 04:42:56 UTC,Please reject this from -proposed.
1770318,2019-06-03 00:29:58 UTC,Is this going to Bionic?
1770320,2018-05-11 03:58:33 UTC,updating project from python-novaclient to python-openstackclient and status from invalid to new
1770320,2018-05-10 08:49:23 UTC,"It is an issue of python-openstackclient, not python-novaclient."
1770324,2018-05-14 08:38:34 UTC,synced
1770324,2018-05-10 20:22:03 UTC,"Hi,
The 3 patches prefixed with fixed-*.patch all contain links to upstream commit. It states applied upstream. Anything not clear?"
1770324,2018-05-10 12:45:48 UTC,"> Explanation of the Ubuntu delta and why it can be dropped:
>  * debian/patches/fix-missing-symbol.patch: keep the tests disabled.
>  * debian/patches/fix-missing-symbol.patch: keep the tests disabled.
"
1770330,2020-04-08 12:01:12 UTC,"Unable to reproduce this bug on the master. so marks it as incomplete
Also, the bug summary mentions that it is identified in Mitika and Newton branch which are already EOL."
1770330,2020-06-08 04:17:23 UTC,[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]
1770347,2018-05-10 08:27:23 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/567509"
1770347,2018-05-10 10:36:18 UTC,"Reviewed:  https://review.openstack.org/567509
Committed: https://git.openstack.org/cgit/openstack/vitrage/commit/?id=e00fc0746c1cb77411c34f73f3d063b23d7bf64a
Submitter: Zuul
Branch:    stable/queens"
1770349,2018-06-07 11:19:40 UTC,Noticed this happens for both Kubernetes and Swarm coes.
1770349,2018-07-06 05:40:50 UTC,"I had the same problem with a k8s cluster. In my case, it turned out, this was the problem:
https://bugs.launchpad.net/magnum/+bug/1744362"
1770356,2019-02-26 13:29:44 UTC,Is this still an issue?
1770356,2019-02-26 14:06:31 UTC,Yes: https://github.com/openstack/python-tripleoclient/blob/f848e42d93fb6f7053c3610f989053266f93ed7e/tripleoclient/v1/overcloud_ffwd_upgrade.py#L65
1770356,2021-02-17 17:06:30 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1770361,2018-05-10 09:41:06 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/567539"
1770361,2018-05-10 13:47:58 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/567539
Reason: abandoning to clear gate for Bug 1770355. Will restore after fix lands."
1770361,2018-05-17 21:44:43 UTC,"Reviewed:  https://review.openstack.org/567539
Committed: https://git.openstack.org/cgit/openstack/tripleo-upgrade/commit/?id=705219eae0d6c1b24489c663253a954f556b8b65
Submitter: Zuul
Branch:    stable/queens"
1770370,2018-07-12 23:29:51 UTC,"The plan is to rework how we identify users in the database. Right now we use the name as a primary key and using mongo's complete lack of referential integrity, if we enabled reusing usernames now we could remove one, add another and the ownership of things would effectively change."
1770370,2018-07-12 17:13:17 UTC,"@Anastasia, I'm sorry but I still do not understand what the plan is."
1770370,2018-07-10 11:56:54 UTC,"@Sandor Zeestraten (szeestraten),"
1770370,2018-07-12 23:34:44 UTC,"@Sandor Zeestraten (szeestraten),"
1770370,2018-07-10 01:03:44 UTC,"We do have some plans to renovate the way we've modeled user (for example, to use a primary key instead of username as an internal identifier)."
1770370,2018-05-14 05:17:27 UTC,"Yes, this came up in bug 1668335, but it still an issue which prevents us from using users with Juju."
1770370,2018-07-10 11:06:08 UTC,"Apologies, but I'm a bit slow. Are you saying that you will at least support the use case of disabling (or logically removing) and re-enabling users?"
1770376,2018-05-10 13:58:34 UTC,"Or 8080 could be used regardless of http or https by default if it's not overridden by the charm config. Similar with Swift:
https://jujucharms.com/swift-proxy/#charm-config-bind-port"
1770376,2020-10-09 10:34:32 UTC,This was fixed by https://review.opendev.org/#/c/735886/
1770391,2019-02-05 16:53:20 UTC,I can confirm this bug for Ubuntu 18.04. with 0.0.svn13576+dfsg-3 too.
1770391,2018-05-10 12:01:24 UTC,"This has been fixed upstream in revision 13700: https://josm.openstreetmap.de/changeset/13700/josm
And the fix is in Debian (version 13710): https://packages.debian.org/sid/josm
as well in cosmic: https://bugs.launchpad.net/ubuntu/+source/josm/0.0.svn13710+dfsg-1"
1770391,2018-05-27 03:06:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770391,2018-05-27 18:22:10 UTC,Version 13860 has been released: https://josm.openstreetmap.de/wiki/Changelog#stable-release-18.05
1770391,2018-07-24 16:38:03 UTC,"""I am Taiwan user and new to Ubuntu, please forgive me for some wrong/inappropriate translations on wordings or terminology."""
1770391,2018-10-13 17:11:08 UTC,What needs to be done to get the fixed version into bionic?
1770391,2018-12-27 11:58:12 UTC,"This makes josm unusable for Bionic users, so the importance of the bug should be set to high by someone with permission for that (Bug Control)."
1770391,2018-12-30 16:46:12 UTC,"Hi,
you can start Josm on Ubuntu 18.04.1 LTS by running the java program directly. that is not the bug fix but allow to run josm in the meantime :)"
1770391,2019-04-12 12:21:36 UTC,This page shows how to install the latest version in my case for Bionic that overcomes the bug.
1770393,2018-05-10 15:37:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770395,2018-06-14 08:49:43 UTC,"Hello Julian, or anyone else affected,"
1770395,2018-05-10 15:13:57 UTC,minimal cloud images should consider inclusion of iproute2 even if lxd adds iproute2 as an explicit dependency
1770395,2018-05-10 15:29:36 UTC,I don't think we need to make a change in the minimal cloud images; this (and similar bugs) should be fixed in the packages that have the bug.
1770395,2018-05-10 15:48:15 UTC,"Having cloud images with only legacy network configuration tools like ifconfig, and not the current ip tool seems weird, though."
1770395,2018-05-10 16:04:29 UTC,"If we consider iproute2 to be essential to a functioning Ubuntu then, you know... ;)"
1770395,2018-05-14 18:51:08 UTC,"it's an unfortunate side effect of the way the minimal images are constructed that net-tools is still present in the minimal image.  Ideally we would not have net-tools in these images either; if we fix livecd-rootfs to remove it, would that be happier? ;)"
1770395,2018-06-06 05:35:47 UTC,This bug was fixed in the package lxd - 3.0.1-0ubuntu1
1770395,2018-06-14 16:34:44 UTC,"I looked at https://launchpad.net/ubuntu/bionic/amd64/lxd/3.0.1-0ubuntu1~18.04.1 and the depends is there now, so verified."
1770395,2018-06-21 07:49:55 UTC,This bug was fixed in the package lxd - 3.0.1-0ubuntu1~18.04.1
1770395,2018-06-21 07:50:01 UTC,"The verification of the Stable Release Update for lxd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1770405,2020-11-14 04:17:17 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1770405,2020-09-14 07:48:59 UTC,Do you still experience this bug? If so then in what Ubuntu version?
1770405,2018-05-10 13:48:57 UTC,"Seems that I have solved my problem, the parameter that I was looking for was ""click-action"", configured as ""cycle-windows"" instead of ""preview""."
1770406,2018-10-03 03:54:43 UTC,"I have a similar problem. After booting Ubuntu 18.04.1 it works for a few seconds and then freezes, i can move my pointer but that's it, nothing else works except the power button. Im using Acer Aspire 7 A715-71G-52WP"
1770406,2018-11-23 11:09:35 UTC,The same issue with Acer Predator Helious 300.
1770406,2018-11-23 21:36:44 UTC,"Hi Sebastien, unfortunately I can't do that. Because like I said before everything freeze after boot. I can't move the mouse, I can't use shortcut, open terminal."
1770406,2018-11-23 15:33:12 UTC,Could you include the journalctl log?
1770406,2018-07-08 17:01:19 UTC,Try disabling the automatic login feature under Settings > Details > Users
1770406,2018-05-11 11:10:47 UTC,I think the problem is a GNOME 3.28 in Ubuntu 18.04. I tried other Linux flavors such as Lubuntu 18.04 and Mint Sylvia (Cinnamon and Mate) and it works fine.
1770406,2018-05-11 14:39:09 UTC,"Same problem with Acer Aspire 7 A715-71G-523H. I've installed system without starting live Ubuntu. After installation system is loaded, but after entering my password, Ubuntu freezes."
1770406,2018-05-10 16:20:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1770406,2018-05-11 15:57:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770407,2018-05-10 16:20:49 UTC,kernel-bug-exists-upstream
1770407,2018-05-10 14:22:30 UTC,apport information
1770407,2018-05-10 15:50:55 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1770407,2018-05-10 16:30:40 UTC,Did this issue start happening after an update/upgrade?
1770407,2018-05-10 14:22:32 UTC,apport information
1770407,2018-05-11 15:16:40 UTC,"I do not have the old kernels.
I have an unused partition with 17.04 but it will take some effort to
resurrect it."
1770407,2020-06-11 12:53:36 UTC,I have very similar problem:
1770407,2018-05-10 14:22:27 UTC,apport information
1770407,2020-06-11 13:24:57 UTC,"        ID 046d:08ad Logitech, Inc. QuickCam Communicate STX 640x480"
1770407,2018-05-11 03:39:10 UTC,"> I had previously been using Skype and Google Hangouts [16.04] with no problems.
"
1770407,2018-05-10 14:22:25 UTC,apport information
1770407,2018-05-10 14:22:28 UTC,apport information
1770407,2018-05-10 14:22:22 UTC,apport information
1770407,2018-05-10 14:22:23 UTC,apport information
1770407,2018-05-10 14:22:13 UTC,apport information
1770407,2018-05-10 14:22:14 UTC,apport information
1770407,2018-05-10 14:22:15 UTC,apport information
1770407,2018-05-10 13:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770407,2018-05-10 14:22:18 UTC,apport information
1770407,2018-05-10 14:22:19 UTC,apport information
1770407,2018-05-10 14:22:21 UTC,apport information
1770407,2018-05-10 14:22:17 UTC,apport information
1770408,2018-05-11 19:42:04 UTC,Remove the comment lines and you won't have the crash.
1770408,2018-05-11 20:18:42 UTC,"I think you missed the point. Originally the file as received has just
the DieselSpecialEffects section with the usual comment about the format
of the blocks which seems to be in every eng file. In that form it crashed."
1770408,2018-05-13 06:33:17 UTC,"Sorry, I wasn't inexact. You are right. As your engine (which in reality is a wagon) has no diesel special effects, you can completely remove the DieselSpecialEffects block. This way you avoid the crash."
1770408,2018-05-13 10:41:16 UTC,Yes that should resolve it.
1770411,2018-11-01 11:55:08 UTC,Restarting docker seemed to work for me.
1770411,2019-09-12 13:46:58 UTC,Sounds like a docker problem.
1770413,2018-05-11 02:49:09 UTC,What does hpsetup return when it runs? It may be hpsetup tells the system to reboot and returns a non-zero return code which is getting captured by MAAS as a failure. Can you tell hpsetup to not reboot and adding the command 'reboot' to the end of your script?
1770413,2019-09-19 14:47:14 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1770415,2018-05-14 13:51:44 UTC,The issue is where I don't want to have Swift deployed. Arguably then I should have enable_swift set to False :) But it's still a hard to diagnose error that we should probably code against.
1770415,2018-05-11 07:07:51 UTC,"you missing run swift role,
tools/kolla-ansible -i ~/multinode deploy --tags haproxy,mariadb,rabbitmq,keystone,ceilometer,gnocchi,swift -e enable_swift=yes can fix the error."
1770417,2018-05-11 08:48:28 UTC,As Daniel asked in [1] making this abug report against Qemu (upstream).
1770417,2018-05-11 08:49:58 UTC,"Ubuntu task is not actionable until we settled on how to change the parsing code for long strings upstream, so I set it to confirmed but wishlist (until we know what size a patch - or actions a recommendation on handling differently has)."
1770419,2018-05-10 15:36:03 UTC,"Same issue here!
With source, binary, pike, queens, ubuntu, centos. I think the last kolla image build went wrong."
1770419,2018-05-11 06:05:40 UTC,"I am seeing this issue with ocata images also, so it doesn't seem to be a image specific issue."
1770419,2018-05-11 09:35:46 UTC,"Hi, could you please share logs from docker ps -a in your hosts, also inventory file and los from nova compute at /var/lib/docker/volumes/kolla_logs/_data/nova."
1770419,2018-05-11 13:25:11 UTC,From controller node:
1770419,2018-05-11 13:26:52 UTC,I guess it was a iptables issues. Because I can't reach the rabbitmq port on controller node from compute. Once I dropped the iptables on controller node I can reach the port without any issue. Isn't the deployment automatically should insert the iptable rule to take care of it. BTW I am giving try to new deployment with iptables and firewalld disabled on both nodes to see how it goes. But disabling these can hamper the functionality of openstack NAT rules.
1770419,2018-05-13 00:40:59 UTC,For me after disabling firewalld deployment is successfully completed but the horizon endpoint is not created.
1770420,2018-05-11 19:15:00 UTC,Thanks for reporting.
1770420,2018-05-11 19:51:33 UTC,Thanks for the explanation. I will compile from source then.
1770421,2018-10-19 20:31:35 UTC,"I'm also seeing this behaviour. In addition, I have my keyboard shortcut set to Shift+Mod4+Left (or Up, Down, Right depending on the direction). Not sure if that's also needed information."
1770421,2018-10-22 16:29:43 UTC,"I can confirm this. My workaround is to unmaximize the window, move it, then re-maximize it. This needs to be fixed in Marco."
1770423,2018-08-08 07:45:24 UTC,"Thanks for the new kernel build. I installed it, but unfortunately, I still can’t get a picture on the external HDMI with this build either :("
1770423,2018-08-22 07:29:38 UTC,"I just rebuilt a kernel with the patch I used back then, but can’t get the external monitor to work with that either :-/."
1770423,2018-06-28 08:24:38 UTC,"As far as I remember, I did not have to do any backporting."
1770423,2018-08-08 20:06:04 UTC,Do you happen to have a patch of what you were able to apply and test originally?
1770423,2018-06-27 18:12:59 UTC,"When you applied the patch to the 4.4.0-122 kernel did you have to perform any backporting?  I had to with my test kernel, so maybe I didn't perform the backport properly."
1770423,2018-07-05 18:00:23 UTC,"I built a v2 Xenial test kernel with commit 9a86cda07af2c63649932f0a4fc757701ef54c42. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1770423"
1770423,2018-06-19 18:21:30 UTC,"I built a Xenial test kernel with commit 9a86cda07af2c63649932f0a4fc757701ef54c42.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1770423"
1770423,2018-06-06 20:00:46 UTC,Sorry for the late reply. The patch was merged upstream in https://github.com/torvalds/linux/commit/9a86cda07af2c63649932f0a4fc757701ef54c42
1770423,2018-06-24 13:20:51 UTC,"I tested your kernel build, but unfortunately, I still can’t get a picture on the external HDMI with it. Not quite sure why. Perhaps other patches are required, too?"
1770423,2018-05-10 16:19:50 UTC,It doesn't look like that patch ever made it into mainline.  Could you see if another patch in mainline resolves the bug by testing the mainline kernel?  It can be downloaded from:
1770423,2018-05-10 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770426,2018-05-10 19:34:16 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1770429,2020-03-02 10:48:09 UTC,"#7 worked for me, Thanks EDEMPCO (edemco)
But my internal speakers are now detected as HDMI / DisplayPort - Built-in Audio"
1770429,2020-02-23 09:10:52 UTC,"Read a lot of advise. Nothing helped.
Tried to load module-detect in pulse like this
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-detect
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev support)
load-module module-detect
.endif"
1770429,2019-04-12 13:42:25 UTC,"Hi everyone :)
I've tried almost all guides (reinstalled ubuntu-18.04.2-desktop-amd64 3 times during my tries =_=). But nothing helped unfortunately.
After all I’ve just simply replaced /etc/modprobe.d/alsa-base.conf with the same I found in Puppy Linux (XenialPup64 7.5)."
1770429,2019-01-31 16:56:41 UTC,more clues related to comment #9
1770429,2019-01-31 16:17:21 UTC,Same problem ubuntu 18.04
1770429,2018-12-10 09:33:14 UTC,"Hello, After I upgraded my Xubuntu 16.04 to Xubuntu 18.04 with fresh install, I've lost my sound.
My laptop model is HP Pavilion G6
Unfortunately none of work arounds worked for me :'("
1770429,2018-10-24 06:05:56 UTC,"sorry, i was wrong, didn't helped.
i had no sound,. but this added just 'dummy output'
i must do pulseaudio -k && sudo alsa force-reload after each boot to make sound work"
1770429,2018-10-19 09:56:29 UTC,"same problem when i upgraded from 18.04 to 18.10
pactl load-module module-detect helped"
1770429,2018-10-09 18:12:41 UTC,"I've done a fresh upgrade to 18.04 and had a ""no sound"" problem that I haven't found a solution to. I found this and have been using it to get the sound connected. Can't find the source again, unfortunately. Thought it might help to point to the problem. Reinstalling Alsa and Pulse; starting and stopping both; eliminating one or the other; did not work. The following identifies something and places ""Built-in Audio Analog Stereo"" into the sound output tab in Settings."
1770429,2018-07-11 03:47:58 UTC,"TigrisAltaica from Ubuntu Forums has reported a similar issue on a HP Pavilion Laptop, unfortunately, renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa-base.bk didn't fix the issue."
1770429,2018-06-30 16:26:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770429,2018-12-06 00:35:24 UTC,"Following up on my post, where I did a fresh upgrade to 18.04 ..."
1770431,2018-05-17 10:21:28 UTC,"Andres: I can't replicate this on Chrome/Ubuntu for either the list or details pages. Can you check with if this is still happening for you on master and, if so, give me a little more information to help me replicate."
1770431,2019-09-19 14:47:17 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1770435,2018-08-22 09:15:48 UTC,18.04 doesn't use Unity. Try file a bug against gnome-setings-daemon.
1770435,2018-08-21 21:21:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770439,2019-04-28 21:45:49 UTC,"we didn't set a milestone prior to the fix, so I guess the only purpose of the milestone in this case is to have the bugfix documented in the changelog of the next release. which will be 2.3"
1770439,2019-04-28 20:31:43 UTC,"ronso0 is 2.3.0 the correct milestone? if not, feel free to adjust."
1770439,2019-01-28 05:06:14 UTC,https://github.com/mixxxdj/mixxx/pull/2008
1770440,2018-05-10 16:30:36 UTC,The following is the error massage I get after Wake up from Suspend:
1770440,2018-05-10 16:56:06 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1770440,2018-05-22 22:27:03 UTC,I have tried the lates upstream Kernel and it works just fine.
1770440,2018-05-22 22:33:58 UTC,Linux #### 4.16.11-041611-generic #201805221331 SMP Tue May 22 17:34:25 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
1770447,2018-09-09 12:15:16 UTC,Problem appeared after upgrade from 16.04 to 18.04
1770447,2018-07-22 09:11:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770447,2018-05-21 13:25:17 UTC,"I bought a new Laptop: MSI GL72M 7REX, and got the same Problem."
1770449,2018-10-28 10:38:05 UTC,"For me, ""sudo apt-get install python"" also created the symlink for python2."
1770449,2018-12-12 16:26:57 UTC,"I too am missing this link.
For me, re-running `apt install python` did not fix the error."
1770453,2019-07-01 19:39:36 UTC,Corresponding flat-text for screenshot:
1770453,2019-09-09 13:29:43 UTC,"Duplicate display field bug already exists at #1806724, sorry for the noise here.
https://bugs.launchpad.net/evergreen/+bug/1806724"
1770453,2019-09-09 13:25:39 UTC,"Hello, I was trying to figure out the duplicates, and it looks like the display fields are provided by the sql function search.highlight_display_fields_impl(), and that uses a query that joins with search.best_tsconfig, and we have multiple entries for each display field id in search.best_tsconfig from setting up multiple synonym dictionaries.  So I think our duplicate display fields entries are a different issue, not related to this bug.  I'll start a new one."
1770453,2019-07-01 19:26:23 UTC,Related to Tina's comment:  we have found that refreshing the screen will make the separators (part #3 of original report) appear.
1770453,2019-09-06 18:26:35 UTC,"Hello, I just noticed this issue also, on 3.3.3.  Here is an example from our test system."
1770453,2018-12-13 17:47:35 UTC,"Re Kathy's reported issue #1: partially displayed subject headings (missing $t), we received a report on it. The missing subfield is 610$t in our examples. We found that if we refresh the screen (use the browser's function key), the subfield will show up."
1770453,2018-08-23 12:01:04 UTC,"I suppose it may have something to do with code changes in /templates/opac/parts/record/subjects.tt2 file which were made to add the highlighting feature, e.g.:"
1770453,2018-08-23 14:16:07 UTC,"Looking at Linda's example, it does appear that the subject links are behaving the same as previous Evergreen releases when separate subjects are listed in different subfield a's. I created a sample record on a 3.0 system where I used multiple subfield a's for the 650 field, and we also see the hierarchy that Jason describes in his comment."
1770453,2018-08-23 13:13:50 UTC,"The behavior that Linda Jansova describes in comment #3 is, I believe, the expected behavior. These are not keywords, but subject terms. The idea is that you are doing a subject search and getting more specific as you go to the right."
1770453,2018-08-23 12:41:06 UTC,"One more comment - looking closely at https://spok.jabok.cuni.cz/eg/opac/record/18254, it seems that while clicking on the first keyword results in the correct URL (https://spok.jabok.cuni.cz/eg/opac/results?query=etika;qtype=subject), the link from th second keyword unexpectedly combines the first and the second keyword in the query (https://spok.jabok.cuni.cz/eg/opac/results?qtype=subject;query=etika%20mor%C3%A1ln%C3%AD%20hodnoty), the link from the third keyword then combines the first three keywords etc."
1770453,2018-08-08 13:09:56 UTC,After we have upgraded to 3.1.4 it turned out that the behavior of the uncontrolled subject term links in the field 653 has changed similarly to behavior described above.
1770453,2018-08-24 08:26:21 UTC,"When it comes to the system where the Linda's example comes from, we have customized the record display adding the 653 field to subject.tt2 template (line 6) as it is the only topical description present in some records. - Kathy, I am not quite sure, what you mean by ""I'm not sure the 653 is configured yet as a display field on this system"".  Is there anything else that should be set when adding the field to subject.tt2 template?
As for the highlighting: The search term in the system are not highlighted because we unfortunately must have switched it off  due to bug 1762363."
1770454,2018-05-11 19:49:45 UTC,"And, to be more direct about the cause, a refresh of the outer frame loses the inner frame's search context entirely.  This is simply a side effect of the use of iframes for the catalog.  (Here's to hoping the community as a whole embraces a ""angular-first web app"" approach to a future OPAC rewrite!)"
1770454,2018-05-24 15:47:11 UTC,"+1 to using display field data in these instances. These fields really need to display the exact some data, whether the record retrieval is the result of a search or not. Is there any benefit to having two different ways to display these fields?"
1770454,2018-05-11 19:47:40 UTC,"Kathy, this is happening because when you refresh the whole page, the inner iframe is built with a different source URL -- one that points directly to the record without any search information.  If you look at the hit count, you'll see that it shows ""1 of 1"" at the bottom of the record summary.  Because there is no search, but just a retrieval of the record, the record is rendered using the ""pull data from MARC"" mechanism rather than using the record's display field data.  While we could probably use the display field data here, it's not, strictly speaking, a ""search result"" anymore, but more like a ""deep link to a specific bib""."
1770456,2018-05-10 17:34:52 UTC,"Review in progress for https://review.opencontrail.org/42945
Submitter: Michael  Henkel (<email address hidden>)"
1770456,2018-05-22 17:48:56 UTC,We need to fix this as follows:
1770456,2018-05-22 23:34:07 UTC,"I agree with the first two points: default -> latest, can be overwritten by the user.
Compiling kernel module as part of the container creation is not going to be practical for a number of reasons."
1770456,2018-08-08 04:14:00 UTC,42945 is abandoned
1770457,2018-05-24 14:34:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770457,2020-01-06 11:11:25 UTC,"Hello,
4.13.0 is not supported anymore, please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
Thanks"
1770469,2018-05-11 16:31:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770480,2020-11-02 18:40:35 UTC,This bug was fixed in the package glibc - 2.27-3ubuntu1.3
1770480,2020-11-02 18:30:34 UTC,"The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1770480,2020-09-11 18:27:14 UTC,https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_170104_5f83a@/log.gz
1770480,2020-09-10 23:03:58 UTC,"Hello Thadeu, or anyone else affected,"
1770480,2020-09-13 01:42:44 UTC,"All autopkgtests for the newly accepted glibc (2.27-3ubuntu1.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1770480,2019-10-24 08:23:32 UTC,"ping, this causes manual work every kernel cycle when tests need to be hinted"
1770480,2018-07-12 20:40:22 UTC,Any news on this?
1770480,2018-05-10 19:19:54 UTC,"Nominating bionic, as we are going to hit this issue there as soon as some backport of linux appears on bionic."
1770480,2020-06-18 20:24:17 UTC,I am sending a proposed patch. I am building a package that includes that patch on my ppa:cascardo/ppa. I will trigger tests against that and verify this really fixes the issue.
1770481,2018-05-11 11:14:05 UTC,We just had a short discussion on systemd and for systemd 229 on 16.04 we also need:
1770481,2018-07-24 03:54:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770481,2019-08-27 12:43:55 UTC,"Confirmed problem on Ubuntu 16.04 host running 16.04 container with a packaged version of Proxysql2. Changing PrivateDevices to ""no"" allows the service to start."
1770482,2018-05-14 12:39:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770482,2018-07-28 10:30:44 UTC,"Please fix this bug.
It ruined my last ubuntu upgrade completely and now it broke my previously stable install out of nowhere after a simple apt-get upgrade."
1770482,2019-04-26 23:09:07 UTC,Affects me.
1770482,2019-05-03 17:24:54 UTC,Work around:
1770485,2018-05-14 14:04:58 UTC,"Change abandoned by Jorge Niedbalski (<email address hidden>) on branch: master
Review: https://review.openstack.org/567690
Reason: We will proceed with proper packaging support for arm64."
1770485,2019-09-12 13:48:21 UTC,"It's new functionality, should be a blueprint."
1770489,2019-04-23 09:51:23 UTC,"Upgrading to 2018.3 in Ubuntu 18.04 is not possible, but you could upgrade to Ubuntu 19.04 instead. Can you please provide more details to reproduce (and fix) these Jinja errors?"
1770489,2019-04-23 12:22:45 UTC,I resolved this issue last year by upgrading to the 2018.3 package on repo.saltstack.com after it became available:
1770491,2018-06-12 00:59:18 UTC,Error log:
1770491,2018-08-18 04:05:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770495,2018-05-11 13:33:04 UTC,"Boris, thank you for your bug report.  We are working to get this corrected in the gallery."
1770495,2018-05-15 12:48:01 UTC,"Thanks Robert. In the meantime, I would appreciate knowing if the version ""18.04.201804262"" of the image in the 18.04-LTS SKU from Canonical can be used for production (i.e. whether the fact that it is not published in the Azure gallery is just a mistake and not an intention). Full specification of the image follows:"
1770495,2018-05-15 13:15:45 UTC,"Boris,"
1770495,2018-05-15 13:26:45 UTC,"Robert, thank you very much for the very useful clarification."
1770495,2020-04-24 15:35:17 UTC,"Hello Boris,"
1770502,2018-12-10 19:04:48 UTC,"... sorry, on a bit further experimentation, it worked when I disabled ""burnproof"", which I frankly don't understand (what it is *or* why disabling it would help). I remember having trouble with burnproof in the distant past and had tried to disable it before I knew to change the cdrdao permissions, but that did not work."
1770502,2019-04-14 16:26:16 UTC,"@Mike, your solution (#17) worked for me too on Ubuntu 18.04.2 LTS"
1770502,2019-04-15 18:09:30 UTC,Mike's fix worked for me as well - Ubuntu 18.04.
1770502,2019-05-06 20:00:12 UTC,Fix worked for me. Waiting on patch.
1770502,2019-08-12 20:08:33 UTC,Confirmed that this fix worked for me as well on 18.04.3 LTS.
1770502,2019-08-28 03:03:55 UTC,I had the same problem. I am about to try the suggestions here.
1770502,2020-02-23 19:24:15 UTC,On Ubuntu 18.04.3 I started experiencing the same problem. CD burning worked fine with Brasero in December when I last burned a CD for my car.
1770502,2019-09-19 22:44:58 UTC,Ubuntu 18.04.3 Brasero/K3B/XfBurn/SimpleBurn not writing/hanging -  SOLVED
1770502,2019-09-19 22:46:02 UTC,Ubuntu 18.04.3 Brasero/K3B/XfBurn/SimpleBurn not writing/hanging -  SOLVED
1770502,2019-03-01 15:12:59 UTC,I can confirm that brasero finally worked after this. Can we roll this into a patch of some sort?
1770502,2020-03-17 21:06:57 UTC,"Just ran into this same issue with Linux Mint 19.3 with Cinnamon 4.4.8
Using this instruction worked for me also. Burning completed without further issue."
1770502,2020-05-15 15:50:19 UTC,This affects me to. Brasero frezes while writing audio CD. Workaround alowed me to get stuck at cd-text part just as Paul said. I have to kill application to stop it. I have Ubuntu 20.04.
1770502,2019-09-19 11:26:00 UTC,I never got an error - Brasero just hung.  K3B has the same problem.
1770502,2019-02-16 15:54:07 UTC,This was also the fix for me. Repeating here for an easy copypasta:
1770502,2018-11-18 10:22:11 UTC,Same problem for me with Ubuntu 18.04.1 LTS
1770502,2018-12-10 18:59:16 UTC,"I had the same issue and the workaround did *not* help; `cdrdao` is 4711 (and just for good measure I changed `wodim` too), but brasero still hangs. I saw elsewhere that `xfburn` still works - and so it does, but without cd text information. Does *that* need sudo permission too, maybe? I have no idea what tool that is. Any help appreciated."
1770502,2018-11-28 19:47:20 UTC,"UBUNTU 18.04 LTS, same Problem.
The workaround helped me."
1770502,2020-06-12 03:29:42 UTC,"I installed Ubuntu 18.04.3 when I finally changed over from gatescrap. However, I have yet to be able to burn a cd or dvd, which I use a lot. I have the linux version of DVDStyler 3.1, but am unable to get it to burn. I hope this workaround on permissions works or I may have to put Windows back on one of my desktops."
1770502,2018-10-11 23:41:50 UTC,"Affected me, clean install of Ubuntu-mate 18.04.1 LTS. Brasero would fail to burn Audio CD's."
1770502,2018-08-19 20:38:52 UTC,I was also unable to burn anything in Brasero with default options.  Making cdrdao & wodim setuid root (4711) solved the problem for me.
1770502,2018-08-06 18:37:12 UTC,"On Linuxmint 19 it is also necessary to install cdrdao
sudo apt-get install cdrdao"
1770502,2018-08-04 01:18:29 UTC,"Apologies for not replying sooner. Those workarounds solved my problem. However, it would be nice if this was fixed in later updates."
1770502,2018-07-21 08:21:38 UTC,"had the same problem. Like Michael wrote
/usr/bin/cdrdao - set to 4711, /usr/bin/wodim to4711  and /usr/bin/growisofs 0755 made it work"
1770502,2018-07-09 13:53:52 UTC,"I had the same problem after an upgrade from 17.10 to 18.04 - worked fine in 17.10. Worked fine for other CD types, just not audio CDs. In desperation I installed k3b, which I used prior to finding brasero a couple years ago. On launch it complained about permissions on /usr/bin/cdrdao - it needed set to 4711. I did this, and both k3b and brasero worked. I don't remember now if any others needed fixed - k3b also checks permissions for /usr/bin/wodim (should be 4711) and /usr/bin/growisofs (should be 0755)."
1770502,2018-07-01 15:22:33 UTC,"Same issue here (Asus DRW-24F1ST a), it worked fine in 16.04."
1770502,2018-06-27 16:34:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770502,2018-05-31 01:28:03 UTC,"Same for burning ""Audio CD"""
1770502,2018-05-10 21:39:32 UTC,Some additional information.
1770507,2018-05-11 02:03:11 UTC,I'm setting the Importance to Critical according to step 6 of https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
1770512,2018-05-11 06:05:21 UTC,Have a try:
1770516,2019-01-04 13:54:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770527,2019-03-22 03:44:25 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1770527,2019-01-30 02:16:51 UTC,"Reviewed:  https://review.openstack.org/632904
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6489f2d2b44827d133dad9a3bb52436ee304a934
Submitter: Zuul
Branch:    master"
1770527,2019-01-24 03:26:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632904"
1770527,2018-06-07 01:58:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/573066"
1770527,2019-01-18 16:47:08 UTC,I'm going to go ahead and use this bug for the 500 API error specifically. The work for being able to increase the maximum number of disk devices allowed to attach to a single instance with the libvirt driver is part of a blueprint: https://blueprints.launchpad.net/nova/+spec/conf-max-attach-volumes
1770528,2018-05-14 02:16:17 UTC,"At the end of a sbackup.log there is a record that ""Simple purge"" has been attempted (without any status what it actually did):"
1770528,2018-05-16 01:49:32 UTC,"To workaround this issue, I wrote a simple shell script located at:
https://gist.github.com/delphym/62e99ef7ba936879580c66c6a9685ef3#file-clean_old_backups-sh"
1770528,2018-05-17 21:35:23 UTC,"Interesting observation:
The last night I've change the value of *Simple cut-off:* from 10 to 7, so now it looks like:
Simple cut-off: Erase all backup older than 7 days."
1770528,2018-05-19 14:30:43 UTC,"Hi,"
1770528,2018-05-21 05:38:32 UTC,"Hi wattazoum,"
1770528,2018-05-22 05:34:08 UTC,"It's a bit tricky to come up with simple description. IMHO examples are the best way how to demonstrate the functionality, so, please find below what I would include in the documentation/help for the Simple Backup Suite."
1770541,2020-02-10 22:07:56 UTC,"Because Ubuntu MATE Welcome is a Snap package, this also affects the 20.04 daily build (and possibly 19.10)!"
1770542,2018-05-11 03:59:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/567735"
1770542,2018-06-20 06:30:52 UTC,"Reviewed:  https://review.openstack.org/567735
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=3462be0fea0ccd13a93818646d1958cfe71509bf
Submitter: Zuul
Branch:    master"
1770547,2018-05-11 03:47:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770550,2018-08-23 14:27:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770550,2019-12-26 19:19:12 UTC,A fix has been suggested as by user- fedorov-ao at:
1770555,2018-05-11 04:38:07 UTC,it might be another issue that
1770555,2018-06-20 07:11:18 UTC,any progress?
1770557,2018-05-11 08:21:33 UTC,"The attachment ""resolved.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1770557,2018-05-18 15:35:42 UTC,"Very nice! I'm sorry you hit this problem, and your analysis and solution look good. I will work on integrating it."
1770557,2018-05-19 07:30:03 UTC,"well, this fix is related only to isc-dhcp-client whose functionality is replaced with systemd-networkd. so, don't know how relevant it is going to be"
1770574,2018-05-11 11:36:52 UTC,"Which Shutter version do you use? The upload was broken in 0.93.1 but is fixed in 0.94. Also you might need to install optional dependencies by hand if they are not automatically installed in your distro, that would be the following ones (exact package names might vary depending on your distro):"
1770574,2018-05-12 13:50:04 UTC,"From Terminal, how do I install those listed dependencies?"
1770574,2018-05-12 13:52:49 UTC,This is the version I was using: 0.93.1 Rev.1278 included in 18.3 of Cinnamon Mint.
1770574,2018-05-13 17:55:31 UTC,Please try this PPA: http://ubuntuhandbook.org/index.php/2017/09/shutter-0-94-released-install-ubuntu-16-04/
1770587,2018-08-06 18:55:42 UTC,"Thanks, it correct my issue:"
1770587,2018-08-06 22:07:20 UTC,"Thanks for changing the status, Simon. Thanks for the advice online.
By the way... Love Lubuntu!
:)
G"
1770587,2018-08-06 18:07:53 UTC,"Hi Jean-Max,
So sorry. Oops! :)
Here is the link:
https://bugzilla.mozilla.org/show_bug.cgi?id=1305270
Take care
:)
G"
1770587,2018-08-13 23:40:12 UTC,"Hi Rolf,
Could post details your reasoning for re-openi g this ticket after Simon closed it?
Take care
:)
G"
1770587,2018-08-06 20:29:17 UTC,"That's super, Jean-Max! I will arrange for this bug to be closed now.
:)
G"
1770587,2018-08-06 16:57:02 UTC,"sorry, but your link
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1770587
is exactly this bug :-)
Do you have another link ?"
1770587,2018-07-15 20:09:44 UTC,"still exist with thunderbird version 52.9.1 of July 10, 2018"
1770587,2018-08-05 23:35:03 UTC,"Hi Jean-Max,
I have the same version of Thunderbird as you do (52.9.1).
Can you post the exact steps as to how you got to the problem?
And you mention disabling an add-on. Which add-on did you disable?
Thanks
:)
G"
1770587,2018-07-15 20:33:39 UTC,"Thanks for the update, Jean-Max. I will change the status back to ""new"" and look at next steps.
Have a great day!
:)
G"
1770587,2018-07-15 19:13:11 UTC,"Hello again. Sorry, I meant ""...problem with creating a new email account in Thunderbird ...""
:)
G"
1770587,2018-07-15 19:10:21 UTC,"Hello
Thank you for submitting this bug and reporting a problem with compacting folders in Thunderbird.  You made this bug report some time ago and Thunderbird have been updated since then."
1770587,2018-08-05 23:57:15 UTC,"Hi again Jean Max.
I was looking for duplicates on this issue among the other bugs.
I found a promising one, on the Mozilla bug tracker website:"
1770595,2018-05-12 02:50:05 UTC,"Hi, InVesalius developer here."
1770595,2018-07-20 12:23:57 UTC,"Hi Thiago, thank you for this suggestion - and for this app. Unfortunately, aforemetioned workaround doesn't seems to work for me:"
1770595,2019-01-11 11:44:04 UTC,"Hi. I'm running Mint-19.0 Tara, based largely on Ubuntu debs. I can confirm the bug. 1st time, it takes 3-4 seconds. It's a fresh install, duly updated & upgraded. I tried running it from a terminal, and got this:
------------
dec@RoseViolet:~$ invesalius3
/usr/share/invesalius/invesalius/data/transformations.py:1899: UserWarning: failed to import module _transformations
  warnings.warn(""failed to import module %s"" % name)
session mode:  0"
1770595,2019-01-11 12:57:07 UTC,"Hi Renat, sorry I didn't see your comment. Your problem is because you need to compile some cython files we use in InVesalius. You need to enter in InVesalius source code then run:"
1770595,2019-01-11 13:00:13 UTC,"Hi Declan Moriarty, that is just a warning, that is not the source of this problem. The problem is the VTK interface with WXPython3. Using VTK with WXPython4 fix this problem. I create a PPA with this problem fixed. Try the InVesalius from there https://launchpad.net/~tfmoraes/+archive/ubuntu/invesalius"
1770599,2019-09-12 07:14:05 UTC,"I think https://review.opendev.org/#/c/673456 considerably improved idempotency in this area, closing the bug."
1770599,2018-05-17 15:19:12 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/569146"
1770599,2018-05-23 19:46:58 UTC,"Reviewed:  https://review.openstack.org/569146
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=815f99a2d9d4ba206e78bbaf5745c5ce1ff7f9b5
Submitter: Zuul
Branch:    stable/queens"
1770599,2018-05-11 09:25:56 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/567806"
1770599,2018-05-17 14:39:14 UTC,"Reviewed:  https://review.openstack.org/567806
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b0322730a7b0759526c3e0b876afa514d8ab35dd
Submitter: Zuul
Branch:    master"
1770600,2018-05-11 22:01:15 UTC,"Hi Daniel,"
1770600,2018-05-11 20:46:39 UTC,Hello Simon.
1770600,2018-05-11 18:27:24 UTC,"@Lonnie, it is already released, see the security announcement: https://usn.ubuntu.com/3645-1/"
1770600,2018-05-11 17:01:55 UTC,The sandboxing improvements are explained in more details here: https://www.morbo.org/2018/05/linux-sandboxing-improvements-in_10.html
1770600,2018-05-11 18:12:51 UTC,When will version 60 be released into Ubuntu 16.04.4?
1770600,2018-05-11 16:33:12 UTC,"@Daniel, it looks like there was some changes to the sandboxing of Firefox. I needed to add the following rules to make FF 60 work again:"
1770600,2018-05-11 13:49:57 UTC,Hello.
1770600,2018-05-11 09:44:14 UTC,"I apologize for so much ""description:updated"", but I had some problems with text formatting etc. If these ""posts"" can be removed, please do it."
1770600,2018-05-11 16:33:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770604,2019-10-07 07:51:27 UTC,"Hello Norbert, or anyone else affected,"
1770604,2019-10-18 23:56:49 UTC,"Same problem, tried fix:
configure: WARNING: using JAVA_HOME environmental variable
adjusted java.home is /usr/lib/jvm/java-13-oracle
checking os.name  Linux
checking os.arch  amd64
checking java.vendor  Oracle Corporation
checking java.version  13.0.1
checking os.version  4.15.0-65-generic
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands"
1770604,2019-11-25 11:24:25 UTC,"The verification of the Stable Release Update for rxtx has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1770604,2019-11-25 11:24:19 UTC,This bug was fixed in the package rxtx - 2.2pre2+dfsg1-1ubuntu1
1770604,2019-10-06 14:20:59 UTC,I uploaded rxtx_2.2pre2+dfsg1-1ubuntu1_source.changes as an SRU now. Hopefully this hits the archive soon.
1770604,2019-11-23 15:55:32 UTC,Verified that installing librxtx-java 2.2pre2+dfsg1-1ubuntu1 solves the issue for me.
1770604,2019-10-06 14:19:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770604,2018-10-08 02:49:48 UTC,Same problem on Lubuntu 18.04 with the build from the most current ubuntu repo (1.0.5 I believe.  2:1.0.5+dfsg2-4.1).  The 1.8.4 version from the arduino website works fine.
1770604,2019-05-08 20:27:28 UTC,Got same on Ubuntu 18.04 with the Arduino IDE 1.8.9 when I want to add Boards in Visual Studio Code with Arduino Ext.
1770604,2019-06-15 13:35:01 UTC,Note: the issue is in librxtx-java and is fixed in Debian version 2.2pre2+dfsg1-2. Ubuntu has this since Cosmic. For Bionic you can download and install the Comic version by hand.
1770604,2018-09-30 02:16:16 UTC,Same issue with Ubuntu 18.04 Linux kernel 4.15.0-34-generic.
1770604,2018-09-09 12:09:57 UTC,"Also affects me under bionic:
bp1@eeapp:~$ arduino"
1770604,2018-05-22 11:24:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770609,2018-10-20 18:43:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770611,2018-07-27 11:42:34 UTC,"Hi Vivek,
Finally we confirmed that issue got fixed after patches were installed. Some fixes had to be done on compute side to update properly some CHAP credentials manually modified.
After some time working with patches installed the new CHAP name scheme (using hostname as username instead of ha-volume-managed) is applied and populated properly. Still some computes contain old info until they are restarted or all instances live-migrated out of them.
You can close this launchpad.
Regards,
Pedro"
1770611,2018-05-16 09:16:38 UTC,"Hi Pedro,"
1770617,2018-05-11 12:19:33 UTC,Backtrace for same problem in GIMP.
1770623,2018-05-15 19:17:02 UTC,I just tested this with latest master and I do not have this issue.
1770623,2019-09-19 14:47:20 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1770624,2018-11-14 16:08:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770624,2018-11-14 16:10:56 UTC,"Hello,"
1770629,2019-05-01 08:25:18 UTC,Thanks for the reply. The PC is a desktop - Dell Precision Tower 5810.
1770629,2019-07-01 04:17:21 UTC,[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]
1770629,2019-04-29 14:09:53 UTC,"Thank you for your bug report. Could you add your journalctl log after getting the issue?
Could you also give some details on the computer you are using? (is it a laptop? what model?)"
1770629,2019-05-01 08:32:20 UTC,Here is the relevant part of `lsusb -v` for this soundbar.
1770629,2018-05-11 12:05:15 UTC,Added a bit of additional troubleshooting info.
1770629,2019-04-26 12:07:38 UTC,Still an issue in 19.04.
1770630,2020-03-28 16:38:37 UTC,"Alternatively, what if you add ""Compare configure"" option in the context menu that calls the ""nautilus-compare-preferences.py"" and upon closing triggers a re-load of the properties within ""nautilus-compare.py""?"
1770630,2020-03-28 16:30:03 UTC,I can confirm no more RuntimeError's with revision 56.
1770630,2020-03-28 15:33:51 UTC,I also fixed the syslog/RuntimeRrror bug #1825063 in revision 56 now.
1770630,2020-03-28 13:55:59 UTC,When byte compiling the python module util.py it works (python -m compileall src/utils.py). I do get a bunch of RuntimmeError's:
1770630,2020-11-15 11:31:45 UTC,"Märt Põder, thanks for the fix. Also works in groovy."
1770630,2020-03-28 13:16:11 UTC,"Not sure what is going, but I get the following on my machine (Arch Linux, nautilus 3.36.1) with revision 53:"
1770630,2020-03-28 11:26:23 UTC,I committed a fix for this in revision 53 and I intend to create a source release 0.0.6 to provide the Python 3 version needed for current and upcoming distributions:
1770630,2018-05-11 12:08:58 UTC,Note that this is also mentioned on the discussion page of the Arch Linux AUR package of nautilus-compare: https://aur.archlinux.org/packages/nautilus-compare/#news
1770630,2020-03-28 13:26:03 UTC,"My bad, I am not installing it correctly. I'll make sure that's correctly done first."
1770632,2018-09-14 06:47:12 UTC,Also affects new version 2.1.2-0extras18.04.0
1770632,2019-07-07 12:32:25 UTC,Problem in new version still there.
1770633,2018-05-11 13:09:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/567855"
1770633,2018-06-25 02:13:11 UTC,"Change abandoned by Trinh Nguyen (<email address hidden>) on branch: master
Review: https://review.openstack.org/567855"
1770635,2018-05-11 16:24:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1770635,2018-05-13 07:05:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770635,2018-05-13 10:01:52 UTC,"Thank you for indicating the bug as confirmed.
Some developments:
A) i could find how to switch from one environment to the next. Conclusion: problem is independent from gnome/unity/ whatever.
B) i created a test account ""testacct"" and could see the same problem occurring. Conclusion: the session management is not to blame, nor existing user files.
C) i copied the dmesg messages. It seems there is a problem with the graphic card. But i can't really say more."
1770636,2018-09-24 14:47:34 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1770636,2018-07-30 16:07:56 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1770636,2018-07-08 02:05:46 UTC,"Reviewed:  https://review.openstack.org/578804
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=40de025cedffb1aa75aa28388943c2b326266b83
Submitter: Zuul
Branch:    stable/queens"
1770636,2018-06-28 01:02:30 UTC,"Reviewed:  https://review.openstack.org/577726
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1ea3d5ec743838ddb754739a9919a2ecf4c54f9f
Submitter: Zuul
Branch:    master"
1770636,2018-06-23 21:11:40 UTC,"@jay ok thanks for your suggestion and help, I will make gabbit test as you suggested from the link and will put it under the  directory [1]"
1770636,2018-06-22 11:36:13 UTC,"@moutya007: you *can* put the unit test in there, sure. You could also put it into a functional test since this is deterministic behaviour that you can control the setup for (as opposed to something like a race condition where it is very difficult to reproduce reliably outside of unit tests)."
1770636,2018-06-18 18:09:47 UTC,"Hi, Chris Dent yes i am going to start this as was busy in other assignment before."
1770636,2018-06-21 11:19:37 UTC,"Yes, basically a test needs to be created that raises the exception (by creating a parent and child and then trying to delete the parent) and the exception needs to be caught in the handler, and turned into a 409"
1770636,2018-06-21 06:15:45 UTC,Do we need to add exception for CannotDeleteParentResourceProvider only  in  https://github.com/openstack/nova/blob/master/nova/api/openstack/placement/handlers/resource_provider.py#L130-L140  and write test case or something else ?
1770636,2018-06-18 15:28:40 UTC,Deepak Mourya are you still planning to work on this? If not we need to remove you as the assignee so someone else can make some progress.
1770636,2018-05-14 13:47:06 UTC,"Likely we should update the api-ref too, because this use of 409 is not documented at the moment:"
1770636,2018-06-22 08:17:25 UTC,"@chris Thanks, one more doubt is that where we can place our new test for this because i couldn't find file related here https://github.com/openstack/nova/tree/master/nova/tests/unit/api/openstack/placement/handlers."
1770640,2019-03-06 20:06:22 UTC,"Reviewed:  https://review.openstack.org/567860
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=00d9a3a2e6b4fbbffca359bf36480d902ae608cd
Submitter: Zuul
Branch:    master"
1770640,2018-09-27 20:24:46 UTC,"This has been fix released for ocata, pike, queens (and bionic) in the above mentioned stable point releases."
1770640,2018-09-24 14:47:15 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1770640,2018-06-26 19:46:28 UTC,"In Ubuntu ocata, this fix is included in the 15.1.3 stable point release via https://bugs.launchpad.net/cloud-archive/+bug/1778729."
1770640,2018-06-26 19:25:04 UTC,"In Ubuntu pike, this fix is included in the 16.1.4 stable point release via https://bugs.launchpad.net/cloud-archive/+bug/1778739."
1770640,2018-06-26 17:13:51 UTC,"In Ubuntu queens, this fix is included in the 17.0.5 stable point release via https://bugs.launchpad.net/ubuntu/bionic/+source/aodh/+bug/1778747."
1770640,2018-06-25 13:26:48 UTC,"FTR, this does not only affect the config drive for me, but migration of the root disk with local storage, too. (Using images_type = raw in case that matters.) Found on 16.1.2, applying https://review.openstack.org/568369 fixes the bug."
1770640,2018-06-11 15:19:12 UTC,This issue was fixed in the openstack/nova 15.1.3 release.
1770640,2018-06-05 05:38:54 UTC,"Reviewed:  https://review.openstack.org/568382
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=34f4167974868f817ece4a09ab663ce4a87d3647
Submitter: Zuul
Branch:    stable/ocata"
1770640,2018-06-04 14:27:55 UTC,This issue was fixed in the openstack/nova 16.1.4 release.
1770640,2018-06-08 12:25:03 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1770640,2018-05-17 16:24:07 UTC,"Reviewed:  https://review.openstack.org/568369
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=938c0a745325fa73d098c6d5ddd20b2a599f9624
Submitter: Zuul
Branch:    stable/pike"
1770640,2018-06-04 13:52:22 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1770640,2018-05-11 13:37:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/567860"
1770640,2018-05-11 17:20:49 UTC,"Change abandoned by Vladyslav Drok (<email address hidden>) on branch: master
Review: https://review.openstack.org/567858"
1770640,2018-05-14 20:14:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/568363"
1770640,2018-05-11 13:26:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/567858"
1770640,2018-05-14 21:17:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/568382"
1770640,2018-05-15 09:08:36 UTC,"Reviewed:  https://review.openstack.org/567899
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=016986f4706e881fed16c85c8790af4d26a7c351
Submitter: Zuul
Branch:    master"
1770640,2018-05-15 20:36:09 UTC,"Reviewed:  https://review.openstack.org/568363
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2dc9795a0df40c51ef3c79f99e57725db99019c0
Submitter: Zuul
Branch:    stable/queens"
1770640,2018-05-14 20:30:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/568369"
1770642,2018-05-11 13:34:44 UTC,Since device remains in busy state that could be the reason that containers are not getting deleted.
1770642,2018-05-11 13:35:30 UTC,"[root@kolla-compute-1 ~]# docker volume ls
DRIVER              VOLUME NAME
local               kolla_logs
local               libvirtd
local               nova_compute
local               nova_libvirt_qemu"
1770642,2019-04-10 10:28:08 UTC,"What version of Docker were you using? The Red Hat one? I saw similar issues, had to use the upstream docker."
1770642,2019-06-10 04:17:25 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1770643,2018-05-16 06:40:18 UTC,apport information
1770643,2018-05-16 06:40:17 UTC,apport information
1770643,2018-05-16 06:40:24 UTC,apport information
1770643,2018-05-16 06:40:16 UTC,apport information
1770643,2018-05-16 06:40:21 UTC,apport information
1770643,2018-05-16 06:40:23 UTC,apport information
1770643,2018-05-16 06:40:20 UTC,apport information
1770643,2018-05-16 06:40:15 UTC,apport information
1770643,2018-05-16 06:40:19 UTC,apport information
1770643,2018-05-16 06:40:13 UTC,apport information
1770643,2018-05-11 13:52:52 UTC,"Sorry this is for v4l, by mistake I filled it under bluez"
1770643,2018-05-11 13:54:22 UTC,Moved to v4l
1770643,2018-05-16 06:40:14 UTC,apport information
1770643,2018-05-16 06:40:10 UTC,apport information
1770643,2018-05-16 06:40:12 UTC,apport information
1770643,2018-05-16 04:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770646,2018-05-15 02:21:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770646,2018-05-15 02:24:46 UTC,"Failed to install openjdk-9-jdk_9~b114-0ubuntu1 too, but on amd64. See https://travis-ci.org/vicamo/docker-java/jobs/378539393#L2151 ."
1770646,2018-07-13 14:48:29 UTC,Similar: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1741060
1770646,2018-07-13 15:32:45 UTC,"openjdk-9 has vanished from later releases, so this is never likely to be fixed. openjdk-11 seems to install correctly though I haven't tested it thoroughly."
1770646,2018-07-14 00:31:57 UTC,The Artful package doesn't suffer from this issue.
1770649,2018-05-15 11:17:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/568554"
1770649,2018-07-20 15:43:09 UTC,"Change abandoned by Paul Bourke (pbourke) (<email address hidden>) on branch: master
Review: https://review.openstack.org/580149"
1770652,2018-10-17 16:24:23 UTC,For the record git-remote-bzr seems to be unaffected.
1770655,2018-12-04 19:15:20 UTC,"Sorry, for the duplicate message as sarnold already mentioned. Please ignore it."
1770655,2018-12-04 19:13:25 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1770655,2018-09-30 20:36:00 UTC,"I see that others are working on node.js SRUs, I'll step back for now."
1770655,2020-09-11 11:10:33 UTC,"This got fixed on 09 Aug 2018 update two years ago, but the bug wasn't referred. Version was 8.10.0~dfsg-2ubuntu0.2."
1770655,2018-06-05 14:12:52 UTC,"oh my !
I don't know anything about ubuntu or debian bureaucracy. And I don't want to."
1770655,2018-06-04 19:21:37 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1770655,2018-06-05 21:57:44 UTC,I'll personally take a look at this next week sometime.
1770658,2019-09-25 09:19:48 UTC,Nova API microversion 2.74 introduced a new way [1] to specify az and host. That API does the validation.
1770658,2019-06-18 11:43:12 UTC,I can reproduce the problem with in a single node devstack on master with the following command:
1770658,2018-05-14 02:14:35 UTC,"@daixianmeng Thanks for the check, I will fix it up."
1770658,2018-05-14 01:47:00 UTC,This may be a bug. You can modify this logic check.(add aggregat and host check)
1770661,2018-05-11 15:38:20 UTC,"Looking here:
https://www.packet.net/developers/api/devices/"
1770664,2018-05-14 20:53:52 UTC,Fix was proposed and merged here: https://review.openstack.org/#/c/567875/
1770672,2018-07-31 03:26:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770672,2020-08-10 00:32:29 UTC,kodi-bin 2:17.5+git20171026.2109-final-0zesty
1770674,2019-05-22 18:03:54 UTC,It is now removed in eoan.
1770676,2018-05-15 17:08:22 UTC,Found another old bug related to this: https://bugs.launchpad.net/ubuntu/+source/cronolog/+bug/1012178
1770676,2018-05-15 15:48:37 UTC,"It looks like GCC has determined this is expected to be undefined behavior, so I'll be getting a pull request into cronolog and then work with MOTU to get the patch in."
1770676,2018-05-15 16:13:03 UTC,Issue and pull request for cronolog submitted.
1770676,2018-05-11 16:36:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770676,2018-05-11 16:12:18 UTC,To reproduce this in cronolog:
1770696,2018-05-11 16:44:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/567894"
1770696,2018-05-11 19:22:14 UTC,"Reviewed:  https://review.openstack.org/567894
Committed: https://git.openstack.org/cgit/openstack/nova-powervm/commit/?id=220a7cdc684043139de43ef5e8d4602ad4d9faf0
Submitter: Zuul
Branch:    stable/queens"
1770696,2018-08-24 19:19:28 UTC,This issue was fixed in the openstack/nova-powervm 6.0.2 release.
1770697,2018-05-11 17:00:17 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770703,2018-05-14 17:06:13 UTC,"I don't think it would be particularly hard. The existing API on the socket
is essentially just passing the []string of CLI args. It should mostly be
just a change to charmhelpers to maintain a socket connection and send the
requests.
That said, it may not be possible to pipeline the requests today. It might
require reconnecting to issue a new request. But it would avoid to fork
overhead"
1770705,2018-07-18 05:34:29 UTC,this is fixed by above patch ^^.
1770705,2018-05-11 17:56:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/567916"
1770705,2018-05-16 00:32:08 UTC,"Reviewed:  https://review.openstack.org/567916
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=359ca265478cf2c387bed9c44808c1f2f1ab2df5
Submitter: Zuul
Branch:    master"
1770706,2020-08-06 21:08:19 UTC,Would it be feasible to compile the source code for 2.11.0 or above in Bionic 18.04 environment?
1770706,2020-08-06 21:15:06 UTC,"If compiling 2.11.0 or above in Bionic is not feasible, can the updated Focal-era service scripts be used for the Bionic?"
1770706,2019-01-30 16:01:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770706,2020-07-30 14:37:00 UTC,"This seems to have been fixed on version 2.11.0
https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/openvswitch/commit/?id=7b4f5ecb46bf853d8c814f31b8ddb3444dd60289"
1770711,2018-05-11 23:18:00 UTC,"I am not aware, that we have load cues."
1770711,2018-05-12 00:09:39 UTC,Might this also be why I sometimes see Loop Out points on tracks I've never loaded before?
1770711,2020-07-07 11:58:34 UTC,Is this one fixed now?
1770711,2020-09-06 04:17:18 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1770714,2018-05-11 17:58:16 UTC,I see this in the etcd logs around the time of the error but they don't tell us anything:
1770714,2018-05-11 18:00:11 UTC,I don't know if there is anything cinder can do here except maybe put a retry wrapper on anything that involves hitting etcd and if you get a service unavailable error retry until some timeout.
1770715,2018-12-25 11:16:30 UTC,https://github.com/google/fscrypt/issues/111#issuecomment-444352798
1770720,2018-05-19 03:00:53 UTC,"I think that I've got the same problem, with a little more information at https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1772066"
1770720,2018-05-27 15:23:16 UTC,"The status at https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1772066 have moved to ""confirmed""."
1770724,2020-11-14 06:38:19 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1770724,2021-01-14 04:17:14 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1770725,2018-05-28 17:42:29 UTC,"Hello Daniel,"
1770725,2018-05-29 13:48:42 UTC,"Hello Daniel van Vugt,"
1770725,2018-05-31 01:32:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770725,2018-05-26 10:04:00 UTC,"5. Tell us what ""can not see the image"" means. Does that mean the window is black? Can you send a photo?"
1770725,2018-05-26 10:01:25 UTC,Please also:
1770725,2018-05-29 02:02:38 UTC,"OK, thanks. H.264 high profile sounds like something your hardware supports."
1770725,2018-05-25 14:31:36 UTC,"Hello Daniel van Vugt,"
1770725,2018-05-16 04:29:20 UTC,Please also tell us which movie player you are using.
1770725,2018-05-16 03:53:54 UTC,Please run this command and send us the output:
1770725,2018-05-25 14:47:33 UTC,"Hello Daniel van Vugt,"
1770726,2018-05-11 18:47:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/567929"
1770726,2018-05-12 02:27:32 UTC,"Reviewed:  https://review.openstack.org/567929
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd53a181be22291e6f9be1430cab12ba1f381b8a
Submitter: Zuul
Branch:    master"
1770726,2018-05-15 16:55:34 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/568642"
1770726,2018-05-29 12:39:13 UTC,"Reviewed:  https://review.openstack.org/568642
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=177ad2dcfc19e891994c69c678feda4190547e3f
Submitter: Zuul
Branch:    stable/queens"
1770727,2020-07-16 14:17:38 UTC,"Hi Werner,"
1770727,2020-07-16 08:04:54 UTC,"Hi Nathan,"
1770727,2020-07-16 07:48:56 UTC,"Hi, do you still have this issue? I've been unable to replicate with your files in Inkscape 0.92.3 (installed Ubuntu fonts are binary same with the zip file you attached in the initial report)."
1770727,2018-05-12 21:03:09 UTC,"I have also a CAD workstation (different computer), and it shows same behavior as comment #8"
1770727,2018-05-12 20:37:25 UTC,"sorry, I cannot reproduce that, either. If I go in File Explorer and double-click the file it opens up in IE11 which is my default viewer. If I go to the context menu with a right mouse click, and select Open With Inkscape, then I get the normal display, as shown above in comment 7."
1770727,2018-05-12 19:55:45 UTC,Now I did find out the root cause.
1770727,2018-05-11 21:29:42 UTC,<<Capture.PNG>>
1770727,2018-05-12 16:18:34 UTC,"Hello Alvin,"
1770727,2018-05-11 21:37:07 UTC,"I did find a workaround how correct display of fonts works using 0.92.3 (2405546, 2018-03-11):"
1770727,2018-05-11 21:29:16 UTC,I have attached <<HBM_Test_System.pdf>> how it should look like.
1770727,2018-05-11 20:55:12 UTC,"not reproduced on Windows 10, comparing Inkscape 0.91 r13725 (Jan 30 2015) and Inkscape 0.92.3 (2405546, 2018-03-11)"
1770727,2020-07-17 09:36:38 UTC,"Hello Nathan,"
1770727,2018-05-12 19:26:30 UTC,"unfortunately, no. here is a screenshot of what I get in Inkscape 0.92.3. It is the same as in earlier versions of Inkscape, and essentially the same as your pdf file. It is not exactly the same as your pdf file because I'm on Windows, so I do not have the Ubuntu font installed."
1770727,2020-07-19 07:56:10 UTC,"Hi Werner,"
1770731,2018-05-27 06:37:30 UTC,"Flickering ghost images may be caused by gnome-shell's damage tracking losing track of where things have been drawn, and it then uses buffer age information incorrectly, leaving junk in only one of the buffers (out of 2 or 3). So every second or third frame contains pixels that shouldn't be there, 20 or 30 times per second. I think the best way to work around it is to drag a window over the flickering area."
1770731,2018-05-27 06:37:45 UTC,... and then let us know the URL of the new bug.
1770731,2018-05-26 13:56:28 UTC,"$ lspci -k
00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
 Subsystem: ASRock Incorporation Intel Kaby Lake Host Bridge
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller
 Subsystem: ASRock Incorporation 200 Series PCH USB 3.0 xHCI Controller
 Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem
 Subsystem: ASRock Incorporation 200 Series PCH Thermal Subsystem
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
 Subsystem: ASRock Incorporation 200 Series PCH CSME HECI
 Kernel driver in use: mei_me
 Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
 Subsystem: ASRock Incorporation 200 Series PCH SATA controller [AHCI mode]
 Kernel driver in use: ahci
 Kernel modules: ahci
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #2 (rev f0)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #3 (rev f0)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.7 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #8 (rev f0)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (Z270)
 Subsystem: ASRock Incorporation 200 Series PCH LPC Controller (Z270)
00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC
 Subsystem: ASRock Incorporation 200 Series PCH PMC
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
 Subsystem: ASRock Incorporation 200 Series PCH HD Audio
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel
00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller
 Subsystem: ASRock Incorporation 200 Series PCH SMBus Controller
 Kernel modules: i2c_i801
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
 Subsystem: ASRock Incorporation Ethernet Connection (2) I219-V
 Kernel driver in use: e1000e
 Kernel modules: e1000e
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
 Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080]
 Kernel driver in use: nvidia
 Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
 Subsystem: eVga.com. Corp. GP104 High Definition Audio ..."
1770731,2018-05-26 13:55:08 UTC,apport information
1770731,2018-05-29 12:31:22 UTC,Gnome bug link: https://gitlab.gnome.org/GNOME/mutter/issues/175
1770731,2018-05-16 05:32:10 UTC,Please also run this command and send us the output:
1770731,2018-05-26 13:55:07 UTC,apport information
1770731,2018-05-16 03:55:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1770743,2018-10-18 15:37:29 UTC,Charm consumes the VLAN interfaces from MAAS so I'd prefer not to implement any function in the charm.
1770743,2019-09-19 12:05:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1770747,2019-07-17 15:54:00 UTC,"Would be great if an upgrade could happen in time for Ubuntu 19.10. Failing that, what is involved in building/compiling avr-gcc?"
1770748,2018-05-11 21:06:49 UTC,Could the Foundations Team please take over maintenance of ilmbase?
1770748,2018-05-11 21:10:19 UTC,I suggested on #ubuntu-devel today that a compromise that might be acceptable for Debian while addressing the API stability concerns would be to have a symbols file only for amd64.
1770748,2018-05-15 17:56:00 UTC,"Well, someone needs to act here, as this is blocking openexr transition and packages which depend on it."
1770748,2018-05-15 19:04:36 UTC,"yes, the package owner should update the symbols file for all architectures to restore the status from the release pocket."
1770748,2018-05-15 19:15:59 UTC,"previous irc discussion at
https://irclogs.ubuntu.com/2018/05/11/%23ubuntu-devel.html"
1770748,2018-05-20 22:16:05 UTC,Builds ok in my PPA with no symbols errors.
1770748,2018-05-20 22:29:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770748,2018-05-23 19:38:36 UTC,"Rik, thanks for your debdiff. I uploaded it to cosmic so we can unblock these transitions."
1770748,2018-07-06 23:16:58 UTC,This bug was fixed in the package ilmbase - 2.2.1-2ubuntu1
1770754,2018-05-14 12:37:39 UTC,"Given that 1.5.1 is in Bionic newer releases are fixed.
Thanks for the report, considering this rather low prio issue for Artful is unlikely.
It lacks a few links e.g. to the fix and/or upstream-discussions - Is there a major use case broken by this?"
1770755,2018-05-11 23:07:00 UTC,Is related to SVG link last commit? Not sure how to reproduce in my computer.
1770755,2020-04-14 18:09:48 UTC,"OpenClipart integration has been removed from Inkscape (https://gitlab.com/inkscape/inkscape/issues/440), since OpenClipart is down permanently."
1770755,2018-05-12 00:58:33 UTC,"I don't know, but wouldn't think so. I suspect this is more a GTK3 migration thing.
Only discovered when testing for possible complications of the SVG linking."
1770755,2018-05-11 22:45:28 UTC,Here's a video:
1770755,2018-05-11 22:11:41 UTC,Thanks for fill the bug.
1770755,2018-05-11 22:53:25 UTC,(the command line does not give any output)
1770759,2018-05-11 21:36:24 UTC,This catch is TypeError exception if feed_child is called with the wrong number of arguments.
1770759,2019-10-21 21:23:45 UTC,"FYI: vte 0.52 fixed a broken annotation, hence the unfortunate incompatible change in language bindings."
1770765,2018-05-18 12:35:11 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1770765,2018-10-08 06:12:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770774,2018-07-09 06:08:13 UTC,"I bumped my box to 18.10 (development), and issue still occurs."
1770779,2018-07-30 13:51:40 UTC,"Problem is, that some systems with ubuntu-defaults-it , ubuntu-defaults-zh-cn and ubuntu-defaults-baltix packages installed doesn't have line
intl.locale.requested=""""
in /usr/lib/firefox/distribution/distribution.ini"
1770779,2018-07-30 08:31:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770779,2018-07-30 14:16:17 UTC,"line
intl.locale.requested=""""
in /usr/lib/firefox/distribution/distribution.ini was added in 59.0+build5 builds, for example:
https://launchpad.net/ubuntu/+source/firefox/59.0+build5-0ubuntu0.16.04.1"
1770782,2019-01-12 22:22:53 UTC,Have you checked kdesu configuration as Partition Manager told you to?
1770782,2019-01-13 09:25:34 UTC,Launching partition mananger from gnome asks for root password so I guess it's solved...
1770786,2019-07-08 20:01:15 UTC,Also seen in a Train grenade job here:
1770788,2019-09-16 08:39:27 UTC,Migrated to https://github.com/widelands/widelands/issues/3279
1770789,2018-05-14 09:12:36 UTC,An upgrade to kapptemplate v16.04.0 would solve this. Is this feasible?
1770792,2019-06-17 15:00:00 UTC,I've landed these blacklist changes now.
1770792,2019-06-17 14:19:55 UTC,"> Or, you can punt this to me to do and I'll apply these changes when I have a chance.
"
1770792,2019-04-17 18:48:04 UTC,"> Why are you dropping the blacklist of fbxkb, which was identified
> in the blacklist file as ""obsolete GNOME panel applet""?
"
1770792,2019-04-17 18:39:07 UTC,"You've dropped ccsm from the blacklist, but the sole binary package built from ccsm in Debian comes from compiz source in Ubuntu; I think this needs to be retained."
1770792,2019-06-17 04:17:44 UTC,[Expired for ubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1770802,2018-06-06 12:52:07 UTC,"Hi kiewitt,"
1770802,2018-05-15 15:04:15 UTC,"Hi kiewitt,"
1770802,2018-05-24 08:25:52 UTC,"Hi kiewitt,"
1770802,2018-05-26 11:15:36 UTC,"Am 24.05.2018 um 10:25 schrieb srinivas:

> Hi kiewitt,
>
> Can you please provide me the following logs
> 1) error_log for cups
> path: /var/log/cups/error_log
> How to enable cups log :
> -> go to /etc/cups/cupsd.conf
> -> Change the Loglevel from warn to debug2 and add 'hpLogLevel 15' in the next line and save the file.
> -> restart the cups before adding the printer using hp-setup - /etc/init.d/cups restart
> 2) syslog.
>    It will be there in the path /var/log/syslog.
> 3) Output of hp-setup -g
>
> Thanks,
> Srinivas Teja
>


Hello,"
1770802,2018-05-22 12:39:29 UTC,"Hello,"
1770820,2018-05-14 09:19:14 UTC,"Hi,
HP Ink tank 319 printer is not supported by HPLIP.We may support it in future."
1770820,2018-05-14 12:38:27 UTC,"Hi,
The printer model HP Ink tank 319 is yet to be supported in the HPLIP driver and hence you are seeing the errors while configuration.
Thanks,
Shivani"
1770822,2018-06-07 20:35:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770826,2018-05-13 06:25:05 UTC,"Workaround: Build with ""DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -b -us -uc"" works."
1770831,2018-09-11 03:39:33 UTC,Can you please take a photo of the problem and attach it here?
1770831,2018-09-13 09:53:50 UTC,"Hi
2 photos
Regards
Jacques"
1770831,2018-09-13 09:55:55 UTC,"Le mar. 11 sept. 2018 à 05:45, Daniel van Vugt <
<email address hidden>> a écrit :"
1770831,2018-11-13 04:17:26 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1770831,2019-01-31 11:30:48 UTC,"Hi Daniel,
Thank you for your help,
The screen is working  with out problems."
1770836,2018-05-12 13:52:48 UTC,apport information
1770836,2018-05-12 13:54:36 UTC,Went with amdgpu.dc_log=1 to make the kernel more chatty.
1770836,2018-05-12 13:56:47 UTC,"Oh, and I did a single sleep/wake, so if there's gonna be anything in the logs regarding the displays coming back up, it'll be after 15:48:32."
1770836,2018-05-15 15:01:58 UTC,Submitted: https://bugs.freedesktop.org/show_bug.cgi?id=106529
1770836,2018-05-14 17:56:52 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1770836,2018-05-14 20:11:14 UTC,"Just checked and nothing changes – monitors in standby get treated as hotplugged. So unless someone can get upstream interested, multi monitor on amd stays kind of broken for who knows how long."
1770836,2018-05-15 06:08:30 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu"
1770836,2018-05-12 13:52:47 UTC,apport information
1770836,2018-05-12 14:54:08 UTC,Looks like I'm not the only one: https://bugs.freedesktop.org/show_bug.cgi?id=104300.
1770836,2018-05-12 13:52:46 UTC,apport information
1770836,2018-05-12 13:52:40 UTC,apport information
1770836,2018-05-12 13:52:43 UTC,apport information
1770836,2018-05-12 13:52:42 UTC,apport information
1770836,2018-05-12 13:52:41 UTC,apport information
1770836,2018-05-12 13:52:40 UTC,apport information
1770836,2018-05-12 13:52:39 UTC,apport information
1770836,2018-05-12 13:52:37 UTC,apport information
1770836,2018-05-12 13:52:36 UTC,apport information
1770836,2018-05-12 13:52:34 UTC,apport information
1770836,2018-05-12 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770836,2018-05-12 13:52:44 UTC,apport information
1770836,2018-05-12 13:52:38 UTC,apport information
1770837,2018-07-26 11:37:46 UTC,Moving bug over to python3.6 as it certainly should not be segfaulting on a py3compile call.
1770837,2018-07-26 11:37:09 UTC,[ 3606.252220] py3compile[30831]: segfault at 8 ip 0000000000443e5a sp 00007ffc26c3f2c8 error 6 in python3.6[400000+3c1000]
1770839,2018-05-13 22:42:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770839,2018-07-01 07:25:46 UTC,Please ask in ubuntu-devel mailing list to update syncevolution.
1770839,2018-07-03 07:59:15 UTC,"there is nothing to sponsor there, unsubscribing the sponsors"
1770839,2019-05-15 09:00:00 UTC,"Fixed upstream. For others, you need to installb libgdbussyncevo0"
1770846,2018-05-12 16:25:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1770846,2018-07-25 19:52:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770853,2018-08-05 21:55:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770854,2018-05-19 14:40:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770858,2018-06-22 18:55:29 UTC,While it's minimally used by panko for tests I think we should keep this around rather than not run a subset of tests. From what I can tell the upstream code does in fact support Python 3.
1770858,2018-06-22 19:01:39 UTC,"Actually Panko only needs this for Python 2.7, so I think we'll only need to maintain this package until we drop support for Python 2.7."
1770858,2018-06-22 19:31:43 UTC,I've uploaded a new package version to Cosmic for this.
1770862,2018-05-12 19:27:41 UTC,apport information
1770862,2018-05-12 19:27:43 UTC,apport information
1770862,2018-05-17 05:00:26 UTC,"Attached is a zip containing updated dmesg and acpidump output against Kernel 4.17 RC5, per the upstream maintainer's request.  It also contains other outputs (xinput, devices, Xorg.0.log, etc.) for said Kernel version."
1770862,2018-05-14 18:13:59 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1770862,2018-05-12 19:27:39 UTC,apport information
1770862,2018-06-19 10:12:19 UTC,"I had this problem on the Zephyrus M GS501M, it suddenly disappeared. I'm not sure what fixed it but i suspect:"
1770862,2018-05-12 19:27:45 UTC,apport information
1770862,2018-05-12 19:27:36 UTC,apport information
1770862,2018-05-12 19:27:31 UTC,apport information
1770862,2018-05-12 19:27:33 UTC,apport information
1770862,2018-05-12 19:27:32 UTC,apport information
1770862,2018-05-12 19:27:29 UTC,apport information
1770862,2018-05-12 19:27:26 UTC,apport information
1770862,2018-05-12 19:27:25 UTC,apport information
1770862,2018-05-12 19:27:23 UTC,apport information
1770862,2018-05-12 19:27:22 UTC,apport information
1770862,2018-05-12 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1770862,2018-05-12 19:27:35 UTC,apport information
1770862,2018-05-12 19:27:28 UTC,apport information
1770863,2018-06-26 19:15:13 UTC,"Le soucis vient du style de la classe ""label"" qui est déclarée en display=inline. Cette dernière, permet le sectionnement, et le plus con c'est qu'on a bien un paramètre pour éviter ça, mais sa sectionne quand même sur l'épaisseur de la marge du bloc (le padding).
Bref, solution 1 passer le display à inline-block ou solution 2, passer ce changement de display sur la classe sizechange (préférable je pense, moins impactant pour les éventuels autres éléments utilisant la classe label)."
1770866,2019-06-06 11:43:26 UTC,"Hi James,"
1770867,2018-05-23 17:12:55 UTC,"Oui, c'est pas problématique ce bug, passer en mode portrait c'est pas la mort, c'était juste pour le signaler"
1770867,2018-05-14 06:02:19 UTC,"Bonjour,"
1770867,2018-05-21 09:15:33 UTC,"Si la navbar est libérée le phénomène disparait.
Perso je la prèfère fixe notamment car les outil dont la recherche sont toujours à portée de main. Et au pire on passe une fois en portrait pour se loguer et on revient en paysage ensuite :)"
1770872,2018-06-16 00:35:22 UTC,"Hmm, maybe something got messed up in your database somehow? Could you attach your mixxxdb.sqlite file?"
1770872,2018-06-16 00:35:42 UTC,"Also, is this with the master branch or 2.1?"
1770872,2018-06-18 14:46:19 UTC,I can easily replicate and will be glad to do any debug needed to fix it.
1770872,2018-06-18 14:43:29 UTC,"This is on master or 2.1. I can replicat easily. My DB is attached. If you scroll through playlists or crates and stop, frequently it will show an empty playlist or the wrong playlist. If it shows the wrong one, it's usually one or two items away in the list. Selecting another playlist then the desired playlist will usually cause it to display the proper list."
1770876,2020-05-24 16:27:08 UTC,fixed in 2.3
1770878,2018-05-31 20:46:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770879,2019-05-24 21:54:28 UTC,Confirmed in the web client 3.3.0.
1770879,2019-10-04 14:50:58 UTC,I took one book and added a 260 field to its record. I then checked it out to myself and the text then showed in the Publisher column
1770884,2018-06-01 16:01:27 UTC,"The issue will be fixed in librsvg 2.42.5. Though the origin of the problem is in cairo-dock, librsvg will now handle the problem without crashing."
1770884,2018-06-01 09:13:53 UTC,Further findings:
1770884,2018-05-31 08:21:04 UTC,Reported at Arch's bug tracker as well: https://bugs.archlinux.org/task/58803
1770884,2018-05-31 07:01:54 UTC,"Sent a mail three days ago, no reply yet - looks like I was wrong in the end..."
1770884,2018-06-02 09:02:42 UTC,librsvg 2.42.5 has landed in Arch now.
1770884,2018-05-22 07:25:04 UTC,"Thanks for tracking down the librsvg issue, and for reporting it upstream. I'm not optimistic for a fix, though. It looks like Cairo-Dock has been abandoned. The last commit to core was in Sep 2016: https://github.com/Cairo-Dock/cairo-dock-core."
1770884,2018-05-22 09:55:18 UTC,"Well, I wouldn't give up on Cairo-Dock so fast, it has received no development during the last year, but already for several years there were only 2-3 commits per year were pushed done, so I assume that we can hope the development to continue with this slow pace rather than being completely dead. If the developers receive the bug report, I am quite positive that the issue will be fixed. I would propose to wait for some reaction to my post on the official forums and, if none follows for some days, contact the devs by mail."
1770884,2018-05-18 16:12:02 UTC,Same problem here :|
1770884,2018-05-21 02:29:39 UTC,Steps to reproduce from an empty .config/cairo-dock:
1770884,2018-06-01 12:20:54 UTC,Reported issue upstream at librsvg: https://gitlab.gnome.org/GNOME/librsvg/issues/276
1770884,2018-05-22 06:19:17 UTC,Downgrading librsvg from 2:2.42.4-1 to 2:2.42.3-1 is a workaround for me on my Arch machine. Seems like Cairo-Dock needs to be update to support the new librsvg version.
1770884,2018-05-22 06:34:53 UTC,"Reported the problem upstream, not sure if anybody will read it there though, the forums looks dead but I couldn't find a better place for reporting a bug: http://www.glx-dock.org/bg_topic.php?t=13227"
1770884,2018-05-21 18:58:22 UTC,"I get many of the same warnings on another up-to-date Arch Linux machine where cairo-dock works fine, so the relevant portion of the output above appears to be the part starting at ""thread '<unnamed>' panicked""."
1770885,2018-05-15 09:22:15 UTC,"I don't see any problem with this. While clients should not be trusted, this doesn't seem to increase risk."
1770886,2018-10-27 19:23:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770886,2020-12-18 20:35:29 UTC,This is still a problem in Ubuntu 20.04.
1770894,2018-09-21 08:54:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770894,2019-01-28 19:17:46 UTC,This actually seems to be an issue with apt-clone:
1770896,2018-05-18 21:55:43 UTC,UPDATE 2018/18/05
1770898,2018-05-24 01:21:14 UTC,"It turns out this is only a problem in Wayland sessions and it doesn't matter how you open the document (nautlius or command line, such as `gedit doc.txt`) so changed the package."
1770898,2018-05-24 01:27:07 UTC,"Wayland is only a protocol, so please don't assign bugs there."
1770902,2018-05-14 22:38:37 UTC,"To help us determine if this is a problem with Inkscape or with the third-party extension, or with your Inkscape installation, please answer the following questions:"
1770902,2018-10-17 21:32:38 UTC,Hi
1770902,2018-10-17 21:37:30 UTC,"(bionic)kester@localhost:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic
(bionic)kester@localhost:~$ inkscape --version
Inkscape 0.92.3 (2405546, 2018-03-11)
(bionic)kester@localhost:~$"
1770902,2018-10-17 21:58:19 UTC,"You could just try it out, and report back if it worked."
1770902,2019-11-11 19:39:28 UTC,"Hi,"
1770902,2020-03-25 08:38:22 UTC,"Closing: The bug is not within Inkscape, please complain with the author of the original plugin."
1770903,2019-09-12 13:49:04 UTC,Is this still valid? Can you reproduce with latest code from git repo?
1770903,2019-11-12 04:17:53 UTC,[Expired for kolla because there has been no activity for 60 days.]
1770915,2019-07-10 17:27:58 UTC,"same issue, please fix, Thanks!"
1770915,2019-06-05 18:40:21 UTC,Hello?
1770915,2020-03-31 19:07:31 UTC,"I tried to rebuild the package, but that didn't seem to work. It looks like each time the package is built, certain parts of the code is consistently missing. (See also the corresponding Debian bug report for more detail)"
1770915,2020-03-31 00:33:12 UTC,This bug affects Focal
1770915,2019-01-07 06:49:16 UTC,Still not working
1770915,2018-05-15 05:24:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770915,2018-09-08 07:20:05 UTC,The Debian package maintainer answered on Github: https://github.com/zsh-users/antigen/issues/659#issuecomment-416469672
1770915,2020-03-28 13:00:19 UTC,"The bug affects `eoan` too. Please, do not pass it to `focal`"
1770915,2018-09-18 06:22:37 UTC,Please fix this issue. Thanks!
1770917,2018-10-10 17:31:30 UTC,15.04 to 18.04 is not a supported upgrade path.
1770917,2018-10-10 17:32:19 UTC,curl3 was removed in cosmic; but this may still affect bionic; marking cosmic as fix-released and keeping bionic task open.
1770918,2018-05-13 07:45:36 UTC,"On Sun, 2018-05-13 at 06:18 +0000, Ri wrote:"
1770918,2018-05-13 17:59:50 UTC,"""Hi Paul; I have tried leaving the gpsd host as default ""localhost"" and changed it to 127.0.0.1 as this was working with Tango. In both cases I left the port at 2847."
1770918,2018-05-14 01:41:31 UTC,"Try installing gpsd-clients and running gps, xgps, gpsmon or gpspipe to
debug what the gpsd daemon is outputting"
1770918,2018-07-10 06:19:01 UTC,SOLVED BY NEW GPS MOUSE
1770918,2018-07-10 07:07:44 UTC,"If you have the time it might be worth reporting this issue to the gpsd
upstream folks, seems this is a regression in gpsd 3.15-2 or earlier."
1770919,2018-05-13 06:21:48 UTC,fixed affected package
1770919,2019-04-24 18:51:18 UTC,"systemd-networkd resets the value as per `systemd.network(5)`: 'IPv6PrivacyExtensions= [...]  When ""kernel"", the kernel's default setting will be left in place. Defaults to ""no"".'"
1770919,2019-10-31 14:35:28 UTC,"As you noted, networkd controls the per-interface setting for this, for interfaces under the control of networkd; so it's working as designed."
1770926,2018-08-19 12:07:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770926,2018-05-13 08:23:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1770929,2020-11-09 18:42:47 UTC,"For me this bug was actually triggered by another new bug in lftp caused by glibc upgate, see #1902832 which was obfuscated by this bug."
1770929,2020-08-20 07:14:54 UTC,"I have ubuntu 18.04 with ru locale and same issue
How I fixed it:
install snap versions
snap install duplicity --classic
snap install deja-dup --classic"
1770929,2020-07-15 18:39:33 UTC,Here's hoping a non-snap version gets fixed!
1770929,2020-07-03 07:53:27 UTC,"Hello all,"
1770929,2020-07-03 00:35:50 UTC,I'm still experiencing this bug.
1770929,2020-02-11 20:15:52 UTC,"Hello,
in view of the above-mentioned post, it seems to me that the problem is not fully solved and therefore I will describe my findings. Today I tried to set up my small server backup to a second using duplicity package. I used some example for writing tiny script."
1770929,2019-10-31 17:30:27 UTC,"Hello,"
1770929,2019-05-31 20:59:23 UTC,"All,"
1770929,2019-05-27 13:19:56 UTC,"All, to clarify the current position, this is fixed in the 0.8 series, but I set out the steps to test the fix in comment #15 and was waiting on testing feedback before merging the patch back into the 0.7 series. Nobody gave me any testing feedback. It is therefore not yet fixed in the 0.7 series."
1770929,2019-05-01 05:09:44 UTC,I can also confirm that this is still happening with Ubuntu 16.04 LTS
1770929,2019-04-30 18:30:45 UTC,"Still, or again, appearing in 0.7.19"
1770929,2019-04-12 19:16:38 UTC,This bug was fixed in the package duplicity - 0.7.18.2-1ubuntu3.1
1770929,2019-06-11 13:09:23 UTC,"To add on to Aaron's comment, if you are coming here because you hit this bug while using deja-dup, you can install a version of deja-dup that bundles in duplicity 0.8.0, which has the fix:"
1770929,2019-03-18 19:24:35 UTC,"Hello,
what is needed for the fix to land in ubuntu's duplicity package ? This bug has bee fixed mainstream and the fix is available in other distro, so if any help needed, please tell me where to start."
1770929,2019-03-10 23:09:39 UTC,"The 0.8-series was affected by this (as I mentioned above, fixing the underlying problem avoids this error and a number of these have been fixed, so it is harder to trigger)."
1770929,2019-02-21 12:37:13 UTC,Thank you everybody for your bug reports and comments.
1770929,2019-02-20 14:44:37 UTC,Same here unbuntu 18.04 lts french
1770929,2019-01-17 16:31:46 UTC,This is the error message I receive when trying to use backup:
1770929,2018-05-27 08:08:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770929,2018-12-04 16:46:46 UTC,Similar to what is described also on https://bugzilla.redhat.com/show_bug.cgi?id=1470873
1770929,2018-11-04 17:42:11 UTC,May be connected to #1440372 – please port deja-dup to python3
1770929,2018-10-31 11:55:15 UTC,"Hello All - me too - identical error output to Bud Roth above.  Not enough space available to try Andrej's workaround, unfortunately.
Nick"
1770929,2018-09-30 08:17:42 UTC,"Hello all,"
1770929,2018-08-30 14:47:54 UTC,I am experiencing this problem too.  I have an English language Ubuntu 18.04 install (fresh) with Japanese language added.
1770929,2018-08-21 23:09:29 UTC,Affected by ascii error too.
1770929,2018-06-05 07:41:16 UTC,I had an error with the same look in the last couple of days with the daily backup:
1770929,2019-04-12 14:39:00 UTC,Let's try to land the change in Ubuntu disco and see how it's going there first before condidering SRUing
1770929,2018-05-27 08:09:16 UTC,Failed with an unknown error.
1770930,2018-05-13 08:36:39 UTC,"And sometimes we exit with ErrorCode but the message does not print the keyword ""ERROR"" at all."
1770938,2018-05-13 23:07:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770940,2019-09-10 12:42:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770943,2018-09-29 07:19:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770943,2019-08-01 11:06:33 UTC,"Today I noticed although you still can't open the computing preferences from the default ""simple"" view, if you change to ""advanced"" using the ""view"" menu, the ""ootions, computing preferences"" window now works."
1770948,2019-11-19 06:24:10 UTC,Not sure.  Maybe it is related somehow? If you explicitly set the cursor size does that temporarily resolve the issue for you?
1770948,2018-12-23 18:20:23 UTC,Reported to unity-greeter: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1809594
1770948,2019-11-17 23:42:18 UTC,Is this the same issue?
1770948,2019-07-19 15:00:54 UTC,Still happening every so often with Disco Dingo 19.04.
1770948,2019-03-17 18:54:54 UTC,It seems xubuntu-default-settings installs the following files/directories.  I do not see a lightdm.conf or any resolution specs listed in any of the files:
1770948,2019-03-17 18:28:54 UTC,"I recently performed a clean install of Xubuntu 18.10, and I'm experiencing this more recently.  Also, it appears I'm already using lightdm-gtk-greeter and do not have unity-greeter installed."
1770948,2018-12-23 18:05:47 UTC,"I ""fixed"" this on Cinnamon (Ubuntu 18) by switching away from unity-greeter:"
1770948,2018-05-13 12:28:48 UTC,I believe https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1552133 is an older duplicate of this issue.
1770948,2018-11-17 10:42:02 UTC,"I have been having this problem for like a year now. I have a 4K screen on my laptop but resolution is usually 1920x1080 or 1600x900. Anytime I'm not using the 4K resolution, on boot up my cursor size is huge. To fix it all I have to do is what's said above, change cursor size up 1 and back down 1 (what it was set at) and it'll reset to what it's supposed to be. It's getting annoying for like a whole year everytime I boot the computer up I have to go into mouse settings and fix it."
1770948,2018-10-07 14:19:54 UTC,"I have a Ubuntu 18.04 install on a Dell XPS 9560, 4k screen, with Gnome and Cinnamon desktops, and also have this problem. While using double scaling in Cinnamon, the mouse pointer size remains constant and the desktop usable, but with normal scaling, everything but the mouse pointer scales down to half size."
1770948,2018-08-16 23:07:40 UTC,"@lastonestanding Thank you, glad to see I am not the only one and Ubuntu not the only distro."
1770948,2018-08-16 22:29:36 UTC,Elementary OS related report: bug 1304067.
1770948,2018-08-16 19:51:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770948,2018-05-13 12:01:31 UTC,"I just installed a fresh copy of Xubuntu 18.04 on a new system with a 4k screen, and I am having the same issue."
1770948,2018-03-21 09:39:35 UTC,"When I startup Xubuntu 18.04 beta on my 4K TV (connected by HDMI) the cursor is much too big. The system will boot into Full HD resolution and not 4K. If I then go to the Xfce Mouse settings under the tab ""mouse themes"" to change the cursor size I only need to change the size of the cursor 1 pixel up and down and everything is fine again and the cursor has again the correct size. In my case I change the cursor size from 24 to 25 and then back to 24."
1770948,2018-11-19 13:03:18 UTC,The cursor size is internally set to 0 (default size). Changing the size via the mouse settings will set it explicitly to the chosen value.
1770961,2020-11-01 17:27:41 UTC,Forum thread on this bug's feature request which includes Canonical employee Alan Pope including in their strawman proposal an 'off switch': https://forum.snapcraft.io/t/re-visiting-update-control-on-the-desktop/17170
1770961,2020-07-21 11:29:08 UTC,dee bee if you want an off switch it's already been extensively discussed at https://forum.snapcraft.io/t/disabling-automatic-refresh-for-snap-from-store/707/
1770961,2020-07-21 15:10:49 UTC,"To be fair, I think snappy devs also been open on that thread that if you need software that follows a 'not-Microsoft' and 'always trust the user' policy then yes you should not be using snap, use Flatpak or another alternative instead."
1770961,2020-07-21 12:32:47 UTC,"On Tue, Jul 21, 2020 at 6:36 AM Ads20000 <email address hidden> wrote:"
1770961,2020-03-16 11:26:59 UTC,"On Thu, Mar 5, 2020 at 12:35 PM Ads20000 <email address hidden> wrote:

>
> Another piece of documentation refers to all the options around snap
> refreshes: https://snapcraft.io/docs/keeping-snaps-up-to-date
>
> These include holding refreshes when the connection is metered and
> manual holds (specific delay of an update exceptional to the usual
> refresh schedule set by the user).
>
> Popey's video at https://youtu.be/gVZOBgTDJWc?t=514 is also helpful for
> understanding all the options now available for controlling snap
> updates.
>
"
1770961,2020-07-21 16:42:46 UTC,"the bug here is probably the wrong place for those discussion, best to move to some user forum instead. It's worth mentioning that snapd has a configuration nowadays to respect limited connection and not waste data in such cases (which was something mentioned in earlier comments)"
1770961,2020-03-05 18:27:22 UTC,Another piece of documentation refers to all the options around snap refreshes: https://snapcraft.io/docs/keeping-snaps-up-to-date
1770961,2019-07-04 09:22:20 UTC,"The snap-related feature is already implemented, and other issues concerning the settings GUI are tracked here, so I think this is the appropriate place for it."
1770961,2019-07-02 19:38:25 UTC,"Thank you for your bug report, maybe you could post on https://forum.snapcraft.io/ about it? Snap related features are usually discussed there"
1770961,2018-06-10 08:51:33 UTC,'For example if you can use the option to download updates and prompt the user to upgrade but don't do it until the user confirms it.'
1770961,2018-06-10 08:47:04 UTC,I 'd prefer it if software and updates functionality could be used to fully control how snaps update. For example if you can use the option to download updates and prompt the user to upgrade but don't do it until the user confirms it.
1770961,2020-03-16 08:31:53 UTC,A revision of the label I mentioned above has now been implemented: “Snap package updates are checked routinely and installed automatically.”
1770961,2018-05-16 04:47:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770965,2018-05-13 14:44:39 UTC,"The 2nd paragraph should start as:  ""To fix the problem I rebooted..."
1770965,2018-05-13 18:04:51 UTC,"It turns out that the problem is caused by lightdm: When its configuration points to a not-installed greeter, it fails to load. It is unfortunate that this bug raises its head upon release upgrade, which obseletes the kde greeter."
1770965,2018-05-14 18:37:50 UTC,I will keep this bug open. It is a release critical bug since it causes the user to have an unusable system after upgrade.
1770965,2018-06-01 17:11:38 UTC,Could you please add your upgrade log files? You can find them in /var/log/dist-upgrade/. I'm particularly interested in main.log but the others may be handy too. Thanks in advance.
1770965,2018-06-07 17:17:26 UTC,"""It turns out that the problem is caused by lightdm: When its configuration points to a not-installed greeter, it fails to load."" <- It'd be good if this were fixed in lightdm."
1770965,2018-06-12 22:13:02 UTC,The fix for bug 1775660 may end up fixing the ubuntu-release-upgrader task in this bug report.
1770969,2018-07-12 11:30:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1770969,2018-09-03 05:59:45 UTC,"I added this as affecting me, but I'm running 18.10 instead of 18.04."
1770978,2018-09-14 13:51:41 UTC,The problem confirmed in 3.2. beta sandbox (the Local Administration interface remained in the same state).
1770978,2019-09-16 06:23:40 UTC,The bug is still valid for 3.3.2.
1770979,2019-09-16 06:22:34 UTC,"It is still valid in Evergreen 3.3.2, making the copy alerts very difficult to use for staff members who are not good enough at English."
1770982,2019-09-20 12:31:38 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1770983,2018-07-26 14:33:55 UTC,"I have added the “webstaffblocker” tag. This one is a real obstacle to using the  web client in production for the  non-English speaking users. As another ""localization webstaffblockers"" the bug is critical for circulating staff who must quickly respond to various difficult situations in contact with patrons."
1770983,2019-09-13 12:29:10 UTC,"The problem no more occurs in 3.3 (tested in 3.3.2)
I recommend closing this bug."
1770983,2019-09-13 12:37:33 UTC,Marking this as Won't Fix per Eva's comment in #3.
1770985,2018-11-22 00:11:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771002,2018-05-21 16:13:48 UTC,"Context sensitive MARC tool for the web staff client probably comes from here:
http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/sql/Pg/960.data.marc21-tag-tables.sql
I don't think the strings are currently translatable at all."
1771002,2018-05-25 01:54:59 UTC,We should address this issue as we develop new Makefile routines for building translations as we move away from XUL and only looking at how we translate for the web client.  Marking confirmed issue.
1771002,2018-05-25 01:55:56 UTC,Noting similarity of this issue with bug 1160307 where we have not translated some entries in config.* tables that show in the client.
1771016,2018-05-13 19:13:45 UTC,screenshot with cursor at top left corner of screen and appended board in the middle of screen/working sheet
1771016,2019-08-12 21:26:43 UTC,"Fixed in revision 3bf24fae7abdd59adfbd21c45662152a99793abf
https://git.launchpad.net/kicad/patch/?id=3bf24fae7abdd59adfbd21c45662152a99793abf"
1771016,2018-09-15 00:55:45 UTC,I can confirm on current master (243b05b2c3b5f58d823bbee80aed7532de29bab0).
1771022,2018-05-14 06:12:18 UTC,This bug was fixed in the package bijiben - 3.28.2-1
1771032,2018-05-14 05:38:53 UTC,Looks like our graphics system is not supported. so SDL can't create a window.
1771032,2019-09-17 07:33:46 UTC,Migrated to https://github.com/widelands/widelands/issues/3280
1771033,2020-06-10 15:43:20 UTC,The switch to pyhon3 has been done now in this upload
1771033,2018-05-14 23:55:03 UTC,*** This is an automated message ***
1771033,2018-05-14 06:17:22 UTC,"Thank you! I appreciate that, I now have Local chat working for Gajim."
1771033,2018-05-14 04:12:32 UTC,source: https://github.com/lathiat/avahi/tree/master/avahi-python
1771033,2018-07-22 21:31:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771034,2018-05-14 15:12:45 UTC,"You wan to run `lxd.migrate` first, https://docs.conjure-up.io/devel/en/#users-of-lxd"
1771034,2018-05-14 15:38:34 UTC,"This is a freshly installed system. What is there to ""migrate""?"
1771034,2018-05-14 15:41:23 UTC,"And, if this is a requirement why isn't conjure-up helping me with that? Why do I run conjure-up; fail due to known issue; quit conjure-up; fix issue; run conjure-up; run into next known issue; etc.?"
1771034,2018-05-14 20:26:17 UTC,"There was some confusion on Adam's part.  The migrate step is only required if switching from the apt packaged lxd to the snap, which isn't required on bionic (but was on older releases)."
1771034,2018-05-14 20:33:26 UTC,"Oh, I forgot to mention that when Adam and I were discussing what was going on with this issue, he also pointed out that several people have had issues with CDK and ZFS recently (e.g., https://github.com/conjure-up/conjure-up/issues/1430) which are being still investigated, so even if you get past this bit, there's a fair chance it will fail during the deployment.  If it does work, though, it would be great info for the k8s charm devs.  We do know that dir storage works without issue."
1771034,2018-05-14 21:21:06 UTC,"@adam-stokes,"
1771034,2018-05-14 22:28:40 UTC,"@johnsca,"
1771034,2018-05-15 14:25:47 UTC,"For the record, I think the lxd.migrate requires that the deb packages still be installed (it's a transition step for the case where you were previously actively using the deb packaged lxd and want to move to the snap, so it has to be run after the snap install but prior to the deb removal).  Hence the ""unable to connect to socket"" error."
1771038,2018-05-29 07:21:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771039,2018-05-29 07:21:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771039,2019-01-11 23:37:52 UTC,"Bug still exists in: 4:18.04.3-0ubuntu1
Bug is fixed in: 4:18.12.1-0ubuntu1
(or earlier)"
1771041,2020-08-29 04:19:18 UTC,This bug was fixed in the package jack-mixer - 13-0ubuntu2
1771041,2019-07-02 16:00:03 UTC,"https://launchpad.net/ubuntu/+source/gtkwave/3.3.91-1
  * New upstream release
    * Switch to gsettings instead of gconf. (Closes: #886067)"
1771041,2020-02-21 02:48:55 UTC,This bug was fixed in the package gyrus - 0.3.12-1
1771041,2020-08-12 16:14:05 UTC,the package has been removed from the archive which resolves the issue
1771042,2019-03-12 21:22:31 UTC,This bug is invalid. MSI/MSI-X interrupts are properly serviced when dataplane batching is used. The original problem was in the incorrect virtio driver initialization sequence (virtqueues and MSI-X interrupts configured after DRIVER_OK bit is set).
1771042,2018-05-14 03:00:44 UTC,"diff --git a/hw/block/dataplane/virtio-blk.c b/hw/block/dataplane/virtio-blk.c
index 101f32c..31d9eb8 100644
--- a/hw/block/dataplane/virtio-blk.c
+++ b/hw/block/dataplane/virtio-blk.c
@@ -73,7 +73,7 @@ static void notify_guest_bh(void *opaque)
             unsigned i = j + ctzl(bits);
             VirtQueue *vq = virtio_get_queue(s->vdev, i);"
1771042,2018-05-14 14:06:06 UTC,"On Mon, May 14, 2018 at 03:00:44AM -0000, eric hoffman wrote:

> diff --git a/hw/block/dataplane/virtio-blk.c b/hw/block/dataplane/virtio-blk.c
> index 101f32c..31d9eb8 100644
> --- a/hw/block/dataplane/virtio-blk.c
> +++ b/hw/block/dataplane/virtio-blk.c
> @@ -73,7 +73,7 @@ static void notify_guest_bh(void *opaque)
>              unsigned i = j + ctzl(bits);
>              VirtQueue *vq = virtio_get_queue(s->vdev, i);
>
> -            virtio_notify_irqfd(s->vdev, vq);
> +            virtio_notify(s->vdev, vq);
>
>              bits &= bits - 1; /* clear right-most bit */
>          }
"
1771042,2018-05-14 03:48:46 UTC,"oh right, another note. this only manifests when using kvm."
1771042,2018-05-14 18:30:55 UTC,"thanks for looking at this Stefan - since I don't have any context of exactly the kind of environmental issues like threading, the patch posted here isn't really a suggested fix."
1771044,2018-05-22 14:28:22 UTC,"This also affects pybind11 and xtensor-python autopkgtests, because Python reports wrong include path:"
1771044,2018-05-29 17:21:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771044,2018-06-16 06:22:15 UTC,"In the latest python3.6 sync, sysconfig-debian-schemes.diff is disabled, so I think we can consider this bug fixed."
1771044,2018-06-22 11:27:47 UTC,this is reverted for now
1771057,2019-05-14 15:20:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771058,2019-09-16 08:39:59 UTC,Migrated to https://github.com/widelands/widelands/issues/3281
1771064,2018-05-14 08:22:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1771064,2019-08-31 12:09:16 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1771064,2019-10-31 04:17:35 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1771068,2019-07-04 16:46:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771075,2018-05-14 08:47:09 UTC,apport information
1771075,2018-05-14 08:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771075,2019-07-30 08:24:17 UTC,"I could see this patch d90a10e2444ba5a351fa695917258ff4c5709fa5 has landed in GCP Eoan, and generic kernels."
1771075,2018-05-24 11:54:18 UTC,"Thanks, much appreciated!"
1771075,2018-05-24 10:47:19 UTC,"Yup, I think this is a dupe of that. I noticed that bug was filed against linux-azure; do I need to file a corresponding bug against linux-gcp to get the patch sent there as well?"
1771075,2018-05-23 23:16:52 UTC,Looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1765564
1771075,2018-05-23 18:29:38 UTC,"The commit to fix this bug was added to Artful and Bionic via bug 1765564, so  I'll remove those bug tasks.  I did, however, submit a request to have this commit added to Cosmic."
1771075,2018-05-21 23:42:28 UTC,Any fix that goes into Artful is also applied to the 4.13 HWE kernel in Xenial.  The fix will get into the HWE kernel that way.
1771075,2018-05-21 23:25:09 UTC,"Cool! I noticed you've marked the bug as affecting Artful, Bionic and Cosmic but it also affects Xenial with the 4.13 HWE kernels; should that be marked here as well?"
1771075,2018-05-21 12:22:38 UTC,I will submit an SRU request to have that commit included in the affected Ubuntu kernels.  Then the fix will be available in the next set of kernel updates.
1771075,2018-05-21 06:00:43 UTC,"Good news - I got the chance to test this in our production environment today for about 7 hours and no issues whatsoever. Given that this workload was triggering the issue pretty reliably within about half an hour before, I think this fix has done the trick. Thanks a bunch for your help!"
1771075,2018-05-14 23:12:15 UTC,"To install the kernel, just use dpkg like you said.  Instead of changing GRUB_DEFAULT, you could also manually select the test kernel from the GRUB menu on boot.  The grub menu can be accessed by holding the SHIFT key on boot up, after the BIOS information is displayed."
1771075,2018-05-24 11:31:18 UTC,"Thanks for the heads up, Joshua!"
1771075,2018-05-14 19:09:11 UTC,"I built Artful and Bionic test kernels with commit d90a10e2444ba5a351fa695917258ff4c5709fa5.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771075"
1771075,2018-05-14 08:48:42 UTC,"I've upload the apport information from a host that had the issue but note that I had to downgrade the kernel back to 4.10 due to this issue, so that's what is included in the apport information."
1771075,2018-05-14 08:47:16 UTC,apport information
1771075,2018-05-14 08:47:15 UTC,apport information
1771075,2018-05-14 08:47:14 UTC,apport information
1771075,2018-05-14 08:47:13 UTC,apport information
1771075,2018-05-14 08:47:12 UTC,apport information
1771075,2018-05-14 08:47:10 UTC,apport information
1771075,2018-05-14 22:25:16 UTC,"Awesome, thanks for getting back to me so quickly! Unfortunately we're in a change freeze at the moment - I'll try and get an exemption approved to test this but I may have to wait until Monday to try it out."
1771077,2018-05-14 08:35:25 UTC,"Other tests also do things like create a file with mode '00000' which should be unreadable, but that also doesn't work on all platforms."
1771078,2018-06-30 15:42:59 UTC,"Is this app even being developed or tested? I can't find an APK anywhere, or any commits since about 2014?"
1771088,2018-05-15 11:23:34 UTC,"Thanks. I am not sure that this is worth fixing as the 'shared' should be deprecated and the RBAC code should be used.
I would note this as a limitation and not even sure its worth the effort to address"
1771088,2018-05-15 09:05:46 UTC,Hi Gary
1771088,2018-05-15 06:37:03 UTC,"There are two cases when the exception above is thrown:
1. when there are ports using the network
2. when certain tenants are unable to access the network"
1771088,2018-05-15 01:10:21 UTC,"If the network is not shared,Only demo user can use.
If you update the network shared,all user can use."
1771091,2018-05-14 09:59:08 UTC,The zfs-dkms package should be removed as the kernel includes the ZFS + SPL drivers. You just need to install zfsutils-linux.  Please try the following:
1771091,2018-05-14 10:52:59 UTC,"I get the same results when purging zfs-dkms and --reinstall zfsutils-linux .
System is unbootable (resets after a long time) and shutdown can't be done (also takes very much time).
All happens after 'zpool import <olderpoolname>'"
1771091,2018-07-17 11:15:07 UTC,This looks very similar to the following ZFS bug report
1771091,2019-11-18 13:51:13 UTC,This bug has not been updated with further information requested in question 4 for over a year. Marking as Won't Fix.
1771094,2018-05-14 12:31:40 UTC,"I found the corresponding bug 381173 on bugs.kde.org:
https://bugs.kde.org/show_bug.cgi?id=381173"
1771098,2018-05-15 10:28:32 UTC,"That's strange, but is it actually harmful? If you reboot does the system boot correctly?"
1771098,2018-05-15 10:59:14 UTC,"The bug is cosmetic and has no functionality loss.Yes, if rebooted the system boot correctly."
1771102,2018-06-06 14:14:50 UTC,Does anyone know of anything I can do to move forward?
1771102,2018-06-15 23:29:28 UTC,"Could you try running apt-clone, 'apt-clone clone myclonefile.gz', and see what happens? It looks like the call to apt-clone could be the issue."
1771102,2018-06-16 11:09:15 UTC,"Brian, I'm sorry but I had to upgrade to 18.04 LTS by reinstalling the whole system. No idea why apt-clone would hang like that but it seems to definitely be a bug."
1771106,2018-05-18 09:38:11 UTC,Phuoc takes care of this bug: https://review.openstack.org/#/c/524260/
1771106,2018-05-15 16:33:05 UTC,"Change abandoned by Trinh Nguyen (<email address hidden>) on branch: master
Review: https://review.openstack.org/568634
Reason: Abandon in favor of https://review.openstack.org/#/c/524260"
1771106,2018-05-15 16:13:37 UTC,"This issue happens because of https://review.openstack.org/#/c/522935 is merged. I am fixing this error, with some patches (https://review.openstack.org/#/c/523021 and https://review.openstack.org/#/c/524260)"
1771106,2018-05-16 01:56:01 UTC,"So we need to fix it soon, it seems critical"
1771106,2018-05-15 05:59:39 UTC,This's caused by the parameters were replaced:
1771106,2018-05-15 16:08:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568634"
1771107,2018-05-14 13:36:34 UTC,"I don't have a full analysis yet, but the part of [1] that causes the breakage is more precisely the fact that the extensions.PluginAwareExtensionManager singleton instance is created at a different time than previously [2], and, in the context of the failing unit test, at a time when the extension path does not include the path to the directory containing the bgpvpn.py extension."
1771107,2018-05-14 15:57:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568322"
1771107,2018-05-14 22:20:14 UTC,"Reviewed:  https://review.openstack.org/568322
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=4481c5279717e4ff955fb89f4e3ea9b57bce95f5
Submitter: Zuul
Branch:    master"
1771109,2019-01-17 20:58:42 UTC,wget has no problem with it:
1771109,2018-05-15 20:53:34 UTC,I opened an issue in upstream.
1771109,2018-05-15 20:22:59 UTC,"Has this patch been accepted upstream? If not, I'm not sure it's appropriate for Ubuntu to diverge from upstream behaviour on this. Particularly because IDN type things are especially security sensitive."
1771109,2018-05-15 11:11:27 UTC,Reuploading patch.
1771109,2018-05-15 08:21:35 UTC,"The attachment ""gen-tables-from-iana.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1771109,2018-05-15 07:35:21 UTC,"> Of course, I understand that IANA disallows the use of emojis in domain names. Perhaps a solution could be to resolve these domains, but print a warning on the user's console? I do not have time to think about this.
"
1771109,2018-05-15 07:33:16 UTC,"Attached is a patch enabling resolution of emoji domain names on programs that use libidn2. It patches the script get-tables-from-iana.pl to set the state of emoji characters to PVALID, and uses the experimental perl ""smartmatch"" operator, which may make it unacceptable. Nevertheless, I believe that it provides a proof that a solution is possible, and might prove useful to people having to resolve such domains from a console application, so I am posting it here. It is provided with ABSOLUTELY NO WARRANTY. However, this patch does not affect applications using glibc to resolve domains. As such, I am tagging this as an issue in glibc, too."
1771109,2018-05-14 13:18:05 UTC,"Curl is linked to libidn2.so.0, so tagging this as affecting this library."
1771110,2019-09-19 11:58:12 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1771112,2019-11-01 09:05:40 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1771112,2020-01-01 04:17:21 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1771114,2021-02-22 21:49:22 UTC,Working on fix [1].
1771114,2020-09-21 13:12:44 UTC,"@lathiat are there any solutions for this case ? I have had same issue and it’s so critical when my service is swift storage that based on keystone middleware for authenticaton per file (need scale out more ha unit for token verify). Cached impacted API behaviors, we can’t be sure when responses become be consistency"
1771114,2018-09-13 03:05:51 UTC,"@hopem You said at the top of that paste ""Test done on Mitaka with 3 units of neutron-api in HA"" - the HA service should be Keystone and not neutron-api?"
1771114,2020-09-22 07:30:43 UTC,@Phat (letonphat1988)
1771114,2018-05-14 12:52:53 UTC,"memcached support was adding in the following bug:
https://bugs.launchpad.net/charm-keystone/+bug/1722541"
1771114,2018-09-12 20:28:59 UTC,@lathiat ive tried this out for myself and I do not see the same behaviour - https://paste.ubuntu.com/p/TP2BxQF6kM/. Any idea what i might be doing differently?
1771115,2018-05-15 08:57:26 UTC,"I forgot to mention why I was thinking the effect gets applied twice: I modified the neg shader to just add 0.2 to a color channel, and noticed that the effect would add up."
1771115,2018-05-15 09:02:08 UTC,Or perhaps for some pixels a different encoding for gl_FragColor?
1771115,2018-05-15 09:32:05 UTC,"Here a sort of workaround: making the neg plugin just not invert pixels whose alpha is less than 0.5. That still produces some whitish frame around icons which have a little antialias alpha border for smoothing them, but the result is way better than what I manage to work out otherwise."
1771116,2019-07-31 14:06:35 UTC,"Ah, JFYI: It is using NETMASK= here as well meanwhile."
1771116,2019-07-31 14:05:16 UTC,Hi Ryan.
1771116,2019-07-19 18:57:06 UTC,"Hi,"
1771116,2019-08-05 16:46:03 UTC,"Excellent, ok leaving this bug as INVALID then. If the problem is still exhibited on latest cloud-init please re-open and provide the failing cloud-init version."
1771116,2018-05-14 13:42:26 UTC,"Using CentOS but reporting here as the fix needs to go into the upstream source and then RHEL RPM anyway before going into CentOS, also reported there, see under ""Additional info""."
1771116,2018-05-14 13:48:09 UTC,"I believe the offending code to be in ""_write_network"" in /usr/lib/python2.7/site-packages/cloudinit/distros/rhel.py"
1771122,2018-07-29 21:36:59 UTC,Thanks for reporting this.
1771122,2018-07-29 21:37:57 UTC,"Actually, I typed too quick. The *reverse* of that diff should fix the issue."
1771122,2018-08-16 08:05:30 UTC,"I can confirm your patch is working, @dpm, thanks for your support! Bug can be closed."
1771123,2018-05-14 13:34:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771123,2018-05-15 09:28:02 UTC,Screenshot from the networkmanager
1771132,2018-05-14 16:37:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771132,2018-05-20 14:31:27 UTC,Came across this installing Xubuntu 18.10 for testing purposes.
1771136,2018-12-03 13:26:24 UTC,"Thank you for your bug report, that has been reported upstream as well on https://gitlab.gnome.org/GNOME/gnome-calendar/issues/300"
1771142,2018-05-14 15:50:07 UTC,2nd image showing resetting the panel layout
1771145,2018-05-14 19:55:46 UTC,"Hi Corey,
It looks like you have correctly identified this bug and the right fix.  bash was setting the HOSTNAME variable which was throwing a wrench into assumptions of the parse_shell_config."
1771149,2018-09-25 18:23:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771151,2019-07-22 04:19:23 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1771151,2018-12-04 23:00:30 UTC,It seems like easystroke on ubuntu is still built from 0.6.0 release and not from master.
1771151,2018-10-23 04:37:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771151,2018-06-25 02:41:04 UTC,"Not quite the same issue but see also:
https://errors.ubuntu.com/problem/8eb04b107d22b16cb91cf5c1e44be8e049ff2239
https://errors.ubuntu.com/problem/7e156516466a7ec7b0a7aa687c809732a3860168"
1771152,2018-08-19 15:38:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771158,2018-12-30 14:22:33 UTC,try with:
1771158,2019-02-15 23:32:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771158,2019-02-15 23:33:40 UTC,"Also, affects Ubuntu 18.10.
I click on synaptic, write password then it doesn't start."
1771158,2019-02-16 18:16:07 UTC,"It opens without root from terminal, but when:
$ sudo synaptic
No protocol specified
Unable to init server: Could not connect: Connection refused"
1771158,2019-07-18 02:26:53 UTC,The solution described in #2 works for me. Thank you! I can finally switch to Wayland now.
1771158,2019-09-16 14:03:45 UTC,"This is fixed in Gnome 3.34!
But, there was a message added in Synaptic, which is contra-productive now."
1771158,2019-10-14 07:04:44 UTC,Fixed in 19.10
1771163,2018-06-03 14:35:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771167,2019-12-20 18:07:16 UTC,"reproduced on lxc
lxc launch ubuntu-daily:xenial test-x
lxc exec test-x -- mkdir /var/lib/cloud/seed/config_drive
lxc exec test-x -- ""sed -i 's/NoCloud, ConfigDrive,/ConfigDrive, NoCloud,/' /etc/cloud/cloud.cfg.d/90_dpkg.cfg""
lxc exec test-x -- cloud-init clean --reboot --logs"
1771168,2018-05-14 17:43:29 UTC,"https://review.fuel-infra.org/#/c/38489/
https://review.fuel-infra.org/#/c/38488/"
1771168,2018-05-22 08:55:31 UTC,"https://review.fuel-infra.org/38542
https://review.fuel-infra.org/#/c/38492/"
1771173,2018-05-15 15:14:40 UTC,Updated to 18.04 from 17.10. Same issue.
1771174,2018-05-15 13:00:33 UTC,"If we do add support for this, i'd like to add ability to add other instance data.
 https://trello.com/c/AYaCdQyT
has some information on how we plan to do that."
1771180,2018-05-14 18:46:01 UTC,"Change abandoned by Rajini Karthik (<email address hidden>) on branch: master
Review: https://review.openstack.org/568349
Reason: Duplicate. Included the fixed in https://review.openstack.org/568348"
1771180,2020-06-12 16:41:41 UTC,Fix release in https://review.opendev.org/#/c/568348/
1771180,2018-05-14 18:40:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568349"
1771181,2018-05-14 19:11:04 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1771181,2018-05-14 19:31:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771181,2018-05-15 17:05:50 UTC,Testing of the upstream kernel complete:
1771181,2018-05-22 16:35:48 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1771185,2019-09-24 10:26:43 UTC,"Playing with different resolutions and rates using xrandr solved the problem for me on a DELL XPS 15 with Ubuntu 18.04. If I go with a resolution of 1920x1080 and a rate of 60 Hz the TV shows a black screen. Changing to other modes and rates solves the problem. For example, typing in a terminal"
1771185,2019-01-14 14:59:22 UTC,Could those having this issue add their journalctl log from a session where they try to connect the other monitor? And also give details of the video cards/drivers you use and what screen are connected and using what ports/adaptors/etc?
1771185,2019-02-13 08:09:33 UTC,"Thought I'd add my 2 cents worth. I only just tried adding a second monitor in addition to my laptop a few days ago and had this problem. Tried many of the suggested solutions - none worked. Works OK in windows 10. Also works OK in 16.04. Tried using a HDMI to digital adapter at the monitor - did not work. OK in windows 10. Alas cannot try the adapter at the computer as no digital or dvi plug. xrandr pretty as in others shown above - HDMI-1 disconnected.
Hopefully this will be fixed before too long."
1771185,2019-03-18 06:56:56 UTC,"Still happens here on a HP Pavilion. I have tried the intel onboard video, the nvidia, with the nvidia drivers. If it's of hep the xrandr output shows: HDMI-1 disconnected, so it is seen but not activated. When booting in Windows all works fine..."
1771185,2019-03-29 09:36:51 UTC,"I can also confirm the problem. The Ubuntu 18.04LTS (updated everything) does NOT sense when I disconnect the HDMI. There is no change in /sys. This uis the mainb problem, I guess. The events does not generate screen switching."
1771185,2019-04-21 22:20:06 UTC,"Im having a similar problem. I have a ThinkPad T520, running xfce 4.12 on ubuntu 18.04."
1771185,2019-04-23 10:34:28 UTC,"For me, updating drivers solved the issue. I have got Intel controller:"
1771185,2019-07-09 13:13:39 UTC,"I can confirm that the drivers don't get loaded in 18.04 even though they are installed. This is also what I get when running nvidia-settings from terminal.
ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
1771185,2019-06-05 13:57:28 UTC,"I got it fixed after upgrading from 18.04 to 19.04, but it was not upgrading that solved it. The issue is still there in 19.04."
1771185,2019-07-16 15:01:08 UTC,I have similar problem.
1771185,2019-07-27 14:39:18 UTC,I have similar problem.
1771185,2019-08-08 14:29:58 UTC,"I upgraded my system to the 5.0 kernel of 18.04.3 recently, but the external monitor is still not detected and also xrandr still lists HDMI as disconnected. I was hoping badly for an improvement, but so far it does not seem as if someone is working on this bug."
1771185,2019-08-25 06:16:07 UTC,"Just upgraded to 18.04.03 and thought I'd check if there was any action on this, but alas, no change. I see you were asking for a journalctl dump. Here's mine from today attached. H/W & driver details are:-
  *-display UNCLAIMED
       description: VGA compatible controller
       product: GP106M [GeForce GTX 1060 Mobile]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:a3000000-a3ffffff memory:90000000-9fffffff memory:a0000000-a1ffffff ioport:4000(size=128) memory:a4000000-a407ffff
  *-display
       description: VGA compatible controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:28 memory:a2000000-a2ffffff memory:80000000-8fffffff ioport:5000(size=64) memory:c0000-dffff"
1771185,2019-01-14 14:12:07 UTC,"Same here: Asus Zenbook UX410UA, i7-8550U, Intel UHD 620, Ubuntu 18.04.1."
1771185,2019-04-30 08:09:43 UTC,Also affecting me.  Dell Inspiron 5379
1771185,2019-01-07 02:10:24 UTC,"So, seems I have figured out the issue (at least on my Lenovo T460s) and I think it lies with the Intel chip internal GPU."
1771185,2019-01-24 10:18:40 UTC,"I've got the same problem after the latest update.
My journalctl have no reaction to hdmi connection/disconnection."
1771185,2018-12-30 01:30:54 UTC,"FYI, HDMI output works when I switch to a terminal using CTRL_ALT_F3. It seems to not work only in graphics mode."
1771185,2019-01-04 02:08:56 UTC,Same here. Lenovo T460s (Intel only). Cannot use HDMI to Display Port. HDMI to VGA works though on the same port!! The below is with HDMI->VGA. With HDMI->DP it just doesn't recognise the display.
1771185,2018-05-30 00:06:11 UTC,Found a workaround:
1771185,2018-08-10 19:58:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771185,2018-10-15 11:08:29 UTC,"Hi,"
1771185,2018-10-17 16:32:31 UTC,I have a Dell XPS-15 9570 and I am also affected by this bug.
1771185,2018-10-19 13:44:45 UTC,"I have a dell inspiron 15 5000 2 in 1, Running ubuntu 18.04, and I am also affected by this bug. I have a DELL U2414M monitor."
1771185,2018-10-19 22:29:11 UTC,"Same problem with ASUS S406 (no graphic card, CPU i5-8250U)"
1771185,2018-09-16 18:35:27 UTC,"Hi guys,"
1771185,2018-11-02 11:47:21 UTC,"PS: workaround by Mihai to mirror displays works for me too, to get something on the external display. Same as for Mihai, the display is not listed anywhere."
1771185,2018-11-22 12:53:39 UTC,"Same problem, no external monitor via HDMI detected:"
1771185,2018-12-11 21:47:21 UTC,"Me to. Would love to be able to use my HDMI monitor:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1920x1080     60.06*+  60.01    59.97    59.96    59.93    40.04
   1680x1050     59.95    59.88
   1600x1024     60.17
   1400x1050     59.98
   1600x900      59.99    59.94    59.95    59.82
   1280x1024     60.02
   1440x900      59.89
   1400x900      59.96    59.88
   1280x960      60.00
   1440x810      60.00    59.97
   1368x768      59.88    59.85
   1360x768      59.80    59.96
   1280x800      59.99    59.97    59.81    59.91
   1152x864      60.00
   1280x720      60.00    59.99    59.86    59.74
   1024x768      60.04    60.00
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   800x512       60.17
   700x525       59.98
   800x450       59.95    59.82
   640x512       60.02
   720x450       59.89
   700x450       59.96    59.88
   640x480       60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   680x384       59.80    59.96
   640x400       59.88    59.98
   576x432       60.06
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)"
1771185,2018-12-20 12:24:28 UTC,"I have basically the same problem. I was using 18.04LTS on a HP ZBook15 laptop and also wanted to connect an external monitor by using the HDMI interface. I have 2 graphics cards intel(i915) + NVidia(390drivers), and whatever I chose in prime-select/Nvidia-settings, the external monitor did not work. 'xrandr' always listed the HDMI port as disconnected, which was not true of course. I also tried using different HDMI cables due to stackoverflow suggestions, but this didn't solve the issue. Then, I updated to 18.10, which I still use now, hoping there would be an improvement, but nothing changed. The monitor is still not working, ""xrandr"" still says that the monitor is disconnected."
1771185,2018-12-28 07:30:47 UTC,"Good day,"
1771185,2018-11-02 11:39:24 UTC,Also affected with Asus Zenbook UX31E and Ubuntu 18.04.01.
1771185,2018-12-30 01:27:20 UTC,I have the same issue here:
1771187,2018-07-28 10:51:11 UTC,"This seems to work better lately, i.e. only one ""password typing"" is needed now."
1771188,2018-05-24 05:26:47 UTC,apport information
1771188,2018-05-24 05:26:48 UTC,apport information
1771188,2018-05-24 05:26:50 UTC,apport information
1771188,2018-05-24 05:26:52 UTC,apport information
1771188,2018-05-24 05:26:58 UTC,apport information
1771188,2018-05-24 05:26:57 UTC,apport information
1771188,2018-05-24 05:27:01 UTC,apport information
1771188,2018-05-24 05:27:03 UTC,apport information
1771188,2018-05-24 05:26:45 UTC,apport information
1771188,2018-05-24 05:26:54 UTC,apport information
1771188,2018-05-24 05:26:44 UTC,apport information
1771188,2018-05-24 05:26:32 UTC,apport information
1771188,2018-05-24 05:26:42 UTC,apport information
1771188,2018-05-24 05:26:40 UTC,apport information
1771188,2018-05-24 05:26:38 UTC,apport information
1771188,2018-05-24 05:26:33 UTC,apport information
1771188,2018-05-24 05:26:30 UTC,apport information
1771188,2018-05-24 05:26:27 UTC,apport information
1771188,2018-05-24 05:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771188,2018-05-17 21:27:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771188,2018-05-24 05:26:43 UTC,apport information
1771196,2018-05-24 08:33:25 UTC,"Thank you for fixing my silly mistake, Steve."
1771196,2019-09-17 09:54:13 UTC,"While Rhythmbox does indeed open a port when started, the user needs to start it before the port becomes available. This is no different than opening a Bittorrent client application, or some other application that opens ports."
1771198,2018-05-14 20:28:20 UTC,that seems like a sane plan.
1771199,2018-05-14 20:22:13 UTC,Related: Bug #1302258
1771199,2018-05-14 20:21:30 UTC,This is intentional because sync_enable does not work well with samplers (yet): https://github.com/mixxxdj/mixxx/pull/642
1771202,2018-05-25 18:41:41 UTC,"Hi Peter,"
1771202,2018-05-25 17:16:39 UTC,Correction: s/remove/remote
1771202,2018-05-25 17:16:08 UTC,"@Eric, tried again freshly, this time with 2.4-beta4+develop-dba30a1 and backup and restore work. I noticed, however, that a remove backup (on the controller) is no longer performed. Is this new behaviour or a bug?"
1771202,2018-05-17 19:35:01 UTC,https://github.com/juju/juju/pull/8719
1771202,2018-05-22 16:57:57 UTC,"@Eric, that PR is merged but I don't see any change when using 2.4-beta3+develop-22350ea . Normal?"
1771202,2018-05-23 08:30:39 UTC,"Hello Peter,"
1771206,2019-04-18 06:47:26 UTC,"Hello,
do you still have this issue with the latest Bionic kernel (4.15.0-47-generic)?
Thanks"
1771206,2019-06-18 04:17:23 UTC,[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.]
1771215,2018-05-26 03:21:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771219,2018-05-18 12:32:30 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1771221,2019-09-22 04:17:39 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1771221,2019-07-23 21:17:37 UTC,"> What cloud image are you using?
"
1771221,2019-07-19 18:47:05 UTC,"> I've since deleted the self-built image and used a cloud image instead.
"
1771221,2018-11-19 19:15:36 UTC,Add requested info and change status to New.
1771221,2018-05-15 00:01:31 UTC,Add log bundle.
1771221,2018-11-07 14:57:38 UTC,"Hi,
I've moved this over to cloud-init.
I'm interested in knowing what environment you're running this in."
1771221,2018-05-14 22:38:18 UTC,"Thank you for filing a bug and making cloud-init better Tom. If possible please run ""sudo cloud-init collect-logs"" on the system in question so we can get a better understanding of the system config and user-config provided to this module.  It will create a cloud-init.tar.gz in the current working directory that can be attached to this bug."
1771221,2018-11-19 19:14:45 UTC,"1. How did you build/get this image? It looks like there is a NoCloud seed (run/result.json)
I built this by installing the OS and installing packages following this guide:
https://docs.openstack.org/image-guide/openstack-images.html"
1771222,2019-01-10 12:27:07 UTC,Shows up in 16.04.5 (4.15.0-43-generic) too.
1771222,2019-06-20 12:17:41 UTC,Workaround is to add:
1771222,2018-05-16 23:32:49 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1771222,2019-01-24 16:31:32 UTC,"No,
$ apt-get install ifupdown
redo your network config with /etc/network/interfaces
and
$ apt-get autoremove --purge netplan.io"
1771222,2018-05-16 18:37:54 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1771222,2018-05-15 09:49:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771222,2018-05-16 21:31:03 UTC,"Hi Joseph,"
1771228,2018-05-15 00:04:27 UTC,I just got a new 4K monitor.  The exact same software using an older monitor worked fine.
1771231,2020-08-10 01:54:18 UTC,gmic (2.2.3)
1771232,2018-05-15 00:37:21 UTC,"I commented out pam_kwallet.so in /etc/pam.d/
lightdm and lightdm-greeter"
1771239,2018-06-30 16:38:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771240,2018-10-24 19:16:38 UTC,"This is reasonable, but will likely need to be opt-in to conform to the keystoneauth strict contract for behavior."
1771244,2018-05-18 06:31:40 UTC,"It is not an performance issue, you can use GET /guests/nics?userid=XXX to do the same work as
GET /guests/{XXX}/nic"
1771244,2018-05-28 07:12:49 UTC,"here is the patch
https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/412607"
1771244,2018-05-16 02:24:50 UTC,"I'd argue because sometimes you don't need all info and only want one NIC info, then better to keep both for performance reason?"
1771248,2018-05-15 02:27:10 UTC,"Upstream Commit:
5926d79bc9f6 (""mfd: intel-lpss: Add Ice Lake PCI IDs"")
4a2d25f0c165 (""spi: pxa2xx: Add support for Intel Ice Lake"")"
1771248,2018-07-26 15:52:55 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1771248,2018-08-09 01:10:27 UTC,"platform is not PV, just private. Thanks"
1771248,2018-08-27 03:37:00 UTC,"Commit:22d71a5097ec
* master"
1771248,2018-09-07 20:30:36 UTC,"I built a test kernel with commits a13c93b3a5db and 22d71a5097ec.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771248"
1771248,2018-09-10 06:00:46 UTC,I am finding the test case from upstream to have a try.
1771248,2018-09-10 18:34:36 UTC,Commit a13c93b3a will be applied to 18.10 via bug 1771245.
1771248,2018-09-12 07:35:40 UTC,"testing with kernel image provide by Joseph, all passed."
1771252,2019-07-22 16:45:37 UTC,Patch for ICLLAKE MOBILE intel_rapl support shipped in 5.3-rc1.
1771252,2019-05-06 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771252,2019-07-10 08:23:43 UTC,The fix already in 5.0.0-1008.9
1771252,2019-05-31 10:47:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1771252,2019-03-08 03:25:26 UTC,"git describe --contains df7f8e00a50f4d35b660ea2a2bc734decc1343e6
next-20190214~100^2^2"
1771252,2018-05-15 02:42:10 UTC,"Commit Info:
Powercap/intel_rapl driver enabling for Icelake"
1771252,2018-08-09 01:10:02 UTC,"platform is not PV, just private. Thanks"
1771252,2018-07-26 15:52:10 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1771252,2019-03-08 02:24:45 UTC,ba6f3ec198d555d0c9b7e038cb003922aea2797d
1771262,2018-05-15 09:22:19 UTC,"Can you give more information:
1.storage type: ceph or file
2.Log on to the virtual machine to view the disk.
3.Before and after the virtual machine and snapshot info."
1771262,2018-05-15 13:32:45 UTC,"Storage type is file. If you execute the above steps once, you will find the problem."
1771262,2018-07-23 08:40:12 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/584770"
1771262,2018-07-25 08:40:33 UTC,"Change abandoned by Boxiang Zhu (zhu.boxiang@99cloud.net) on branch: stable/pike
Review: https://review.openstack.org/584770
Reason: push commit to master first and then backport to stable branch"
1771272,2018-07-31 19:19:07 UTC,"Problem is in ubuntu-defaults-builder package, /usr/bin/dh_ubuntu_defaults script - for Firefox 59+ this script should add line
intl.locale.requested=""""
in file /usr/lib/firefox/distribution/distribution.ini
I'm attaching a patch againts /usr/bin/dh_ubuntu_defaults script"
1771272,2018-07-30 14:22:56 UTC,"line
intl.locale.requested=""""
 in /usr/lib/firefox/distribution/distribution.ini was added in Firefox 59.0.1 builds, for example: https://launchpad.net/ubuntu/+source/firefox/59.0.1+build1-0ubuntu1"
1771272,2018-07-30 13:50:20 UTC,"Problem exist also in ubuntu-defaults-it , ubuntu-defaults-zh-cn and ubuntu-defaults-baltix packages - line
intl.locale.requested=""""
is missing in /usr/lib/firefox/distribution/distribution.ini"
1771272,2018-06-25 09:21:01 UTC,"The verification of the Stable Release Update for ubuntukylin-default-settings has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1771272,2018-06-25 09:20:57 UTC,This bug was fixed in the package ubuntukylin-default-settings - 1.4.4.1
1771272,2018-07-30 13:59:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771272,2018-06-14 23:22:14 UTC,"Hello handsome_feng, or anyone else affected,"
1771272,2018-06-13 05:45:52 UTC,This bug was fixed in the package ubuntukylin-default-settings - 1.4.5
1771272,2018-06-13 04:34:58 UTC,"Uploaded, sorry for the delay!"
1771272,2018-05-22 01:39:33 UTC,"Hi,"
1771272,2018-06-19 01:59:12 UTC,"Hi,"
1771281,2020-04-01 09:21:18 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1771282,2018-06-06 11:29:22 UTC,See https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1773045
1771282,2018-06-28 10:07:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771282,2018-08-23 09:38:43 UTC,"this afect me, and this bother me a lot"
1771292,2018-05-23 07:41:28 UTC,seems the current rabbit version does not handle fqdn setup well so it would be best to solve the issue with /etc/hosts file with binding IP and hostname as indicated above.
1771292,2018-05-15 08:53:29 UTC,could be done similar to the other rabbitmq charms: add the hostname with the binding IP address to the /etc/hosts file to be sure that it goes over the selected interface (and not to depend on the FQDN configuration)
1771293,2020-07-14 14:33:01 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/740977"
1771293,2020-02-21 16:42:20 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1771293,2020-01-22 21:04:25 UTC,"Reviewed:  https://review.opendev.org/699938
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8e88ae8dc32239a21985d331ec25641f0a4757a5
Submitter: Zuul
Branch:    stable/pike"
1771293,2020-09-25 15:40:32 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/740977
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1771293,2019-12-19 14:41:16 UTC,This issue was fixed in the openstack/neutron 14.0.4 release.
1771293,2019-12-19 14:39:43 UTC,This issue was fixed in the openstack/neutron 13.0.6 release.
1771293,2019-12-19 09:20:13 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/699938"
1771293,2019-12-19 04:38:21 UTC,"Reviewed:  https://review.opendev.org/699193
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2084585b81649b2afa747e24f036d54e5e16e90e
Submitter: Zuul
Branch:    stable/queens"
1771293,2019-12-16 11:28:39 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/699193"
1771293,2019-12-09 18:12:49 UTC,"Reviewed:  https://review.opendev.org/698002
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=22250e783b194b9d188268c0d301581d73bd430d
Submitter: Zuul
Branch:    stable/rocky"
1771293,2019-12-19 14:42:57 UTC,This issue was fixed in the openstack/neutron 15.0.1 release.
1771293,2019-11-27 03:52:32 UTC,"Reviewed:  https://review.opendev.org/695351
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ff810fcd80af8054763b0751e1309944d39bbc81
Submitter: Zuul
Branch:    stable/train"
1771293,2019-11-23 02:02:47 UTC,"Reviewed:  https://review.opendev.org/695352
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3ec7aed8a367ba2a44fed300b08797e02fc47e06
Submitter: Zuul
Branch:    stable/stein"
1771293,2019-11-21 06:38:46 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/695352"
1771293,2019-11-21 06:38:29 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/695351"
1771293,2019-11-20 13:40:56 UTC,"Reviewed:  https://review.opendev.org/683128
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ab286bcdaccb788ab9df3186e0605e93a9b10bbc
Submitter: Zuul
Branch:    master"
1771293,2019-09-19 12:24:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/683128"
1771293,2019-04-20 01:47:54 UTC,The artical points out root cause for this issue and possible solution for it. https://stackoverflow.com/questions/2332768/how-to-avoid-mysql-deadlock-found-when-trying-to-get-lock-try-restarting-trans
1771293,2018-06-21 02:31:31 UTC,"I just submitted a new bug with similar exception, but it's during port creating:
https://bugs.launchpad.net/neutron/+bug/1777965"
1771293,2019-12-09 12:17:32 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/698002"
1771294,2018-06-13 04:51:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771294,2018-06-13 04:53:32 UTC,"donofrio@Localhost:~$ sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get dist-upgrade -y && sudo apt-get autoremove -y && sudo apt-get autoclean -y && sudo sync && sudo sync
[sudo] password for donofrio:
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Fetched 241 kB in 9s (27.8 kB/s)
Reading package lists... Done
W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument
W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  apport apt apt-utils bind9-host btrfs-progs cryptsetup-bin curl dirmngr dnsutils dpkg fonts-ubuntu-font-family-console gnupg gnupg-agent isc-dhcp-client libapparmor-perl libapt-pkg5.0
  libbind9-160 libcurl3 libgnutls30 libidn2-0 libirs160 libisccc160 libisccfg160 liblwres160 liblxc1 libnss-systemd libpam-systemd libperl5.26 libpsl5 libsystemd0 nplan perl perl-base
  python3-apport rsyslog strace systemd ubuntu-server
The following packages will be upgraded:
  apparmor at bash bash-completion bsdutils btrfs-tools byobu ca-certificates cloud-guest-utils cloud-init command-not-found command-not-found-data console-setup console-setup-linux cryptsetup
  debconf debconf-i18n dh-python distro-info-data dmeventd dmsetup dnsmasq-base e2fslibs e2fsprogs eatmydata ebtables ethtool fdisk file friendly-recovery gcc-7-base gcc-8-base geoip-database
  gettext-base gir1.2-glib-2.0 git git-man gnupg-l10n gpgv hdparm initramfs-tools initramfs-tools-bin initramfs-tools-core iproute2 isc-dhcp-common iso-codes keyboard-configuration
  language-selector-common libapparmor1 libapt-inst2.0 libatm1 libblkid1 libc-bin libc6 libcom-err2 libcomerr2 libcurl3-gnutls libdb5.3 libdevmapper-event1.02.1 libdevmapper1.02.1 libdrm-common
  libdrm2 libeatmydata1 libelf1 libext2fs2 libfdisk1 libfreetype6 libgcc1 libgcrypt20 libgdbm5 libgirepository-1.0-1 libglib2.0-0 libglib2.0-data libgraphite2-3 libharfbuzz0b libicu60 libidn11
  libkeyutils1 liblvm2app2.2 liblvm2cmd2.02 liblz4-1 libmagic-mgc libmagic1 libmount1 libmpdec2 libncurses5 libncursesw5 libnghttp2-14 libnih1 libpam-modules libpam-modules-bin libpam-runtime
  libpam0g libplymouth4 libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libpopt0 libprocps6 libpython3-stdlib libpython3.6 libpython3.6-minimal libpython3.6-stdlib libseccomp2
  libselinux1 libsemanage-common libsemanage1 libslang2 libsmartcols1 libss2 libssl1.0.0 libssl1.1 libstdc++6 libtinfo5 libudev1 libuuid1 libxcb1 locales lshw lvm2 lxcfs lxd lxd-client man-db
  mawk mdadm mlocate mount multiarch-support nano ncurses-base ncurses-bin ncurses-term netcat-openbsd open-iscsi open-vm-tools openssh-client openssh-server openssh-sftp-server openssl
  pastebinit patch perl-modules-5.26 plymouth plymouth-theme-ubuntu-text policykit-1 popularity-contest powermgmt-base procps public..."
1771294,2018-06-15 19:44:57 UTC,"Could you please check your Windows Build number?
According to Microsoft and to my test it is fixed in latest builds, starting with 17046. I verified the fix on 17134."
1771296,2018-05-28 14:03:25 UTC,dpdk_t/rxd_sz as per https://github.com/Juniper/contrail-vrouter/commit/7bf9a302496ca6d46e14a66c3d492a03210a74e2
1771296,2018-05-28 11:49:21 UTC,Charm should add the parameters and set them as follows:
1771296,2018-07-16 15:31:26 UTC,"https://github.com/Juniper/contrail-charms/commit/6afa22b65eb3a0507d163112177bfaee66bf5dcb
https://github.com/Juniper/contrail-charms/commit/05e406bf26c81ae972b2d5a6ff242ba02b13e7cb
https://github.com/Juniper/contrail-charms/commit/2072850e7695116e24bd232fe83c45cdc08cd156"
1771296,2018-05-28 14:04:35 UTC,vr_mempool_sz as per https://github.com/Juniper/contrail-vrouter/search?q=vr_mempool_sz&type=Code
1771296,2018-05-24 18:19:35 UTC,is it possible to describe a bit more - what should be set and how to set it?
1771303,2018-06-25 12:31:05 UTC,https://github.com/Juniper/contrail-charms/commit/66a3815c74db2a085104f1d337ebe3079fbe24f9
1771305,2018-05-15 08:36:49 UTC,My guess is that the bug has to do with finding the connected component of all parts of the condition
1771308,2018-05-16 04:14:26 UTC,As far back as I remember this has been the case...
1771308,2018-05-16 04:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771308,2018-05-16 14:44:34 UTC,"Daniel, what do you mean by ""running process""? The steps involve login out and back in, so starting a new session, group changes should be active on a new login no?"
1771308,2018-05-17 02:10:31 UTC,"By ""running process"" I mean any process."
1771309,2018-05-15 09:23:28 UTC,"I believe the error that I ran into was caused by inadvertently compiling with ""-m32"" without having linux-libc-dev:i386 installed, in which case the preprocessor somehow falls through to including the broken /usr/include/linux/errno.h"
1771309,2018-05-15 14:51:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771310,2020-09-03 16:51:43 UTC,Is this still an issue or can we close the bug?
1771310,2020-09-03 16:51:29 UTC,When using pluggable devices it is advisable to use the UUID of the device as this is guaranteed to find the correct device. USB block devices may not be enumerated in order.  I suggest re-trying using the UUID of devices and see if this helps.
1771310,2020-11-03 04:17:22 UTC,[Expired for zfs-linux (Ubuntu) because there has been no activity for 60 days.]
1771316,2019-01-13 07:06:30 UTC,I wonder if we can generalize this bug. Do any other windows/apps launched from the left monitor also appear on the right?
1771316,2019-01-19 07:44:21 UTC,"Hi, upon my limited testing, the following actions seem to exhibit the same thing as the above:"
1771318,2018-05-15 17:46:49 UTC,https://review.rdoproject.org/r/#/c/13790 adds a check when we promote containers to ensure all of them are actually uploaded
1771318,2019-02-26 13:32:23 UTC,Is this still an issue?
1771319,2018-05-31 18:14:23 UTC,This also effects any other function calls that rely on queries passed to get_info - which after a quick ctrl+f appears to be just get_all_jobs() atm.
1771319,2018-06-01 03:48:22 UTC,"Yes, this is more or less what I had as a fix in mind. For the meantime, we've frozen the dependency at 0.4.16 where the get_info() method works as expected."
1771325,2018-06-19 10:41:54 UTC,This haven't been merged to stable/pike yet  https://review.openstack.org/571218
1771325,2018-06-19 07:48:18 UTC,"Patches have been merged into master, stable/queens and stable/pike. Maybe the status should be changed into Fix Released? Looks like the launchpad didn't change the status automatically."
1771325,2018-07-04 15:18:20 UTC,Fix released for stable/queens in 17.0.5
1771325,2018-05-30 14:52:25 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/571218"
1771325,2018-06-25 19:27:35 UTC,"Reviewed:  https://review.openstack.org/571218
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=51e8b8e6ac3b38b3b3c82ea1d842da89977b68e1
Submitter: Zuul
Branch:    stable/pike"
1771325,2018-05-16 08:45:50 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/568784"
1771325,2018-05-15 15:46:26 UTC,"Reviewed:  https://review.openstack.org/568567
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=90d2dbedefbcc99a20a6a86888ef1d316d5d119f
Submitter: Zuul
Branch:    master"
1771325,2018-05-15 11:51:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568567"
1771325,2018-05-21 03:15:41 UTC,"Reviewed:  https://review.openstack.org/568784
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dddee4189c0789565d1bb0328ef03fab3fb6a45a
Submitter: Zuul
Branch:    stable/queens"
1771327,2018-05-15 15:16:16 UTC,"So '/srv/nova/instances' comes from the config.yaml 'instances-path', which has a default of /var/lib/nova/instances -- so it must be set for this to happen."
1771329,2018-10-15 16:09:37 UTC,"Not sure which part of this fixes the problem, but I don't have any issues after I run the following:"
1771329,2018-10-15 12:25:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771329,2018-05-16 09:23:14 UTC,I think there's a strong argument that the default max open files for Ubuntu Desktop should be higher than it is now. Modern apps use a lot of file handles.
1771329,2018-05-16 09:56:03 UTC,I tried the following:
1771329,2018-05-16 08:37:22 UTC,"Thanks @dino99. I've seen a lot of different suggestions for tackling this error, so it would be good to understand exactly which config change is the critical one."
1771329,2018-05-15 11:43:21 UTC,Related question:
1771329,2018-05-16 09:12:41 UTC,"Maybe some days Dbus will grab some builtin IA to increase/decrease ulimit on the fly !!!
But yes special user's case also need custom user settings. Not a real bug per se, but more of a wish !!!!"
1771341,2018-06-12 15:18:46 UTC,"I had a look again at how the ""wrapable"" mechanism works, and showmouse indeed uses the vertexbuffer and GL directly, so they can't be redirected for now."
1771342,2018-05-15 15:14:44 UTC,Can you include the install.log from a system?  Which curtin version is being used?  The udev rules you show are from curtin 18.1-1 or less.  In Bionic and Cosmic (18.1-5) where bcache dnames have been fixed to use uuid of the backing disk look like:
1771342,2018-05-15 15:36:25 UTC,It says:
1771342,2018-05-15 15:51:41 UTC,"Well, shoot.  It didn't make bionic;"
1771342,2018-05-15 15:53:13 UTC,"Is it possible to give curtin daily a test to confirm?  We're working on a new upload to cosmic and an SRU to bionic, artful and xenial."
1771342,2018-05-15 16:00:45 UTC,"Yes, daily works as expected!"
1771347,2018-05-22 16:52:47 UTC,Tested on a current master sandbox and Firefox. The cursor does not reappear when deleting a field in an existing record.
1771348,2019-08-25 22:07:53 UTC,"Are you sure you're using the 18.04.3 installer? The ""applying network config"" modal dialog isn't in that version any more."
1771348,2019-02-21 14:35:46 UTC,"A very recent change to livecd-rootfs _should_ have fixed this, need to check."
1771348,2019-08-23 12:24:29 UTC,"I also see this on 18.04.3 on an older Dell R310, but installation doesn't progress beyond 4/12 ""Network connections"". No matter what configuration I choose (dhcp/static/disabled),
it always ends at:"
1771348,2018-07-23 12:36:06 UTC,"I see the same, fwiw, on real hardware (not a VM)."
1771348,2018-10-09 16:31:15 UTC,I did not see this issue with 18.04.1 on 14G hardware.
1771350,2018-05-15 13:39:38 UTC,"Marking as ""In Progress"" as this is now on my radar to review the patch and determine whether this is able to be included in a 'safe' way."
1771350,2018-05-15 13:40:03 UTC,"I meant ""Triaged"", not ""In Progress""."
1771350,2018-05-15 16:21:37 UTC,"The attachment ""Required changes to fix directory permissions"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1771352,2018-06-11 06:59:43 UTC,"Same problem here. Really annoying :/ If someone has a fix, please share, thank you."
1771353,2018-08-06 09:40:02 UTC,"The patch ""resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch"" for bug #1727237 seems to be the root cause of my problems (now reported separately in bug #1785383.)"
1771353,2018-08-03 13:39:30 UTC,"On 3 August 2018 at 14:22, Steve Dodd <email address hidden> wrote:

> @xnox:
>
> Yes, on further investigation it looks like these might well be
> different bugs - OTOH the repeated issuance of queries to the upstream
> server, and the confusion about the server capabilities is very similar,
> which suggests a problem in the same code path may be being triggered. I
> will create a new bug once I am sure they are different.
>
"
1771353,2018-08-03 13:22:35 UTC,@xnox:
1771353,2018-08-03 12:38:52 UTC,@Steve Dodd
1771353,2018-08-03 11:06:12 UTC,"Installing libss-resolve works around the problem for me - is there a reason this is not installed by default on Ubuntu, per upstream's recommendations?"
1771353,2018-08-03 10:58:01 UTC,"Hmm, my case seems to be caused by a dnsmasq bug - if there are no answers, it doesn't return an EDNS0 OPT record even if there was one in the query. This seems to be confusing systemd-resolved."
1771353,2018-08-02 18:18:47 UTC,Have a filed an upstream report: https://github.com/systemd/systemd/issues/9785
1771353,2018-08-02 17:00:11 UTC,I'm see this just trying to resolve names on my local LAN:
1771353,2018-05-18 17:01:28 UTC,"It does. If I ask it directly, it responds just fine to my dig query. It also responds correctly to systemd (did you see the packet capture?)."
1771353,2018-05-18 15:32:35 UTC,Does the upstream DNS server actually know about bip.lcy02.canonistack?
1771353,2018-05-15 13:47:15 UTC,All there is about /e/n/i
1771353,2018-05-15 13:46:02 UTC,systemd-resolve --status
1771353,2018-05-15 13:44:55 UTC,/etc/nsswitch.conf
1771353,2018-05-15 13:44:22 UTC,/etc/hosts
1771353,2018-08-02 16:54:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771356,2018-07-24 09:47:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771356,2018-07-24 10:02:26 UTC,This bug is related to ifconfig output change.
1771357,2018-09-07 14:31:41 UTC,I came across another use case for this (or at least a related feature).
1771357,2021-01-22 15:39:59 UTC,"I will note that the only way that one can identify whether changes were resubmitted in a squashed/ammended commit is in the diff drop-down where it shows the various commits and dates of the diffs, otherwise, there's no way to tell that a change has been resubmitted or a commit has updated."
1771368,2018-05-15 21:33:41 UTC,"You verified with --controllerDebug that the MIDI message mapped to loop_out=0 is actually being received by Mixxx, right?"
1771368,2018-05-15 22:39:57 UTC,I've checked with a MIDI monitor that even the shortest press/release cycle always sends 2 separate messages.
1771369,2018-10-16 10:03:52 UTC,Confirmed using 1.8.2 and xubuntu 18.04 64-bit
1771369,2018-05-22 21:07:50 UTC,confirmed in 53ec833304eff182ea6dce241823099d1314bf51
1771369,2018-05-22 22:01:09 UTC,"Great, it will be nice to see it fixed.  Looking forward to working with
you."
1771369,2018-07-08 10:15:18 UTC,"I can confirm that I see this issue too.  I'm running gschem 1.8.2 on two Ubuntu systems, one is a desktop running xubuntu 16.04 and the other is a laptop running xubuntu 18.04.  The crashes seem much more frequent on the laptop than  on the desktop."
1771369,2019-09-18 12:51:36 UTC,"Changed to ""incomplete"" because more information is required on how to reproduce the bug."
1771369,2019-10-15 10:50:02 UTC,I believe this issue has been fixed in gEDA/gaf 1.10.0.
1771372,2018-05-29 09:40:48 UTC,Thanks for investigating !
1771372,2018-05-29 09:23:37 UTC,A backport of the (likely) fix is at https://review.openstack.org/570866
1771372,2018-07-12 22:36:57 UTC,"Reviewed:  https://review.openstack.org/570866
Committed: https://git.openstack.org/cgit/openstack/networking-sfc/commit/?id=ce9eef3ee315bf54d403e174e28eb2445b852d2b
Submitter: Zuul
Branch:    stable/queens"
1771372,2018-05-16 17:18:47 UTC,"For the sake of completeness, an important thing I forgot to add : Not only the code path (see stacktrace) seems to involve ovs, but it also leads to neutron-openvswitch-agent to be in an inconsistent state."
1771372,2018-05-29 08:50:10 UTC,Here is the stack trace involved:
1771380,2018-09-13 08:56:02 UTC,I can reliably reproduce between each run if I delete ~/snap/chromium/common/.cache/fontconfig
1771380,2019-08-07 14:59:05 UTC,This was fixed in snapd 2.36.2 (see https://forum.snapcraft.io/t/2-36-point-releases/9008 and https://github.com/snapcore/snapd/releases/tag/2.36.2).
1771380,2018-05-15 16:27:23 UTC,"I'm pretty sure that this issue started happening at some point during the bionic development cycle (I was dist-upgrading daily), so this is definitely something in the bionic stack that's triggering the issue."
1771380,2018-09-13 09:02:21 UTC,"James identified the issue, which potentially affects all snaps, not just chromium: https://forum.snapcraft.io/t/snaps-are-still-slow-to-launch-on-first-time-launch/6888/5."
1771380,2018-05-15 15:47:33 UTC,"It's not just the omnibox that's unresponsive for some time at startup. It appears that anything that involves keyboard input is delayed, e.g. opening the task manager with Shift+ESC, or opening a new tab with Ctrl+T (however opening a new tab by clicking on the button to the right of the first tab is instantaneous, but then pressing a key to start typing in the omnibox lags by the same delay)."
1771380,2018-05-15 16:03:41 UTC,"Interestingly, I can observe this only on bionic (18.04). I’ve tested the chromium snap in VMs running trusty, xenial, artful and bionic, and only bionic appears to be affected."
1771386,2018-05-22 21:38:16 UTC,While confirming this bug I found a related issue that may require a separate LP entry.
1771386,2018-05-25 19:10:53 UTC,"Branch for this issue at user/rogan/lp1771386_merged_bib_should_be_inactive, 7df1f00a2466324feee56cf0ca89a4d82023dcbf"
1771386,2019-03-26 20:30:49 UTC,Adding a link to the working branch:
1771386,2019-04-01 17:51:19 UTC," I have tested this code and consent to signing off on it with my name, Beth Willis and my email address, <email address hidden>"
1771386,2020-08-20 16:04:49 UTC,"Thanks for the patch, Rogan, and for the testing, Beth.  It works well for me also."
1771386,2020-08-20 17:57:51 UTC,"Time is my enemy and git amend is not cooperating for --signoff so since no
one actually signed off in git to the previous branch just via launchpad ..."
1771386,2020-09-13 17:24:23 UTC,"Forgot to comment that I had merged this to rel_3_4, rel_3_5, and master.  Thanks, Rogan and Beth."
1771389,2018-11-29 11:41:32 UTC,"Ok! I though Gnome Flashback was Gnome Classic, some websites refer to Gnome Flashback as Gnome Classic. Thank you!"
1771389,2018-11-29 10:51:42 UTC,"I found a possible workaround, I would like to check if it's correct and safe to try:"
1771389,2018-11-29 11:23:34 UTC,How that is workaround? GNOME Flashback is not GNOME Classic.
1771389,2018-11-04 11:49:28 UTC,No.
1771389,2020-03-17 12:16:04 UTC,"Closing, it is not simple task and there are still no plans to do it in near future."
1771389,2018-05-16 11:22:07 UTC,The main reason is that Wayland is tearing-free by design. XOrg needs a window manager with compositing to avoid tearing.
1771389,2018-05-16 10:55:03 UTC,First I would like to hear why do you want Wayland with GNOME Flashback?
1771389,2018-05-15 16:22:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1771389,2018-11-04 11:27:08 UTC,Any update of this? Thank you!
1771394,2018-08-20 16:50:36 UTC,This bug affects me too. Removing adb and fastboot does not solve the problem here.
1771394,2019-05-14 09:44:21 UTC,The fix is in Disco
1771394,2019-01-09 16:35:29 UTC,The issue has been fixed upstream now in https://gitlab.gnome.org/GNOME/gvfs/commit/63700b5
1771394,2018-08-20 16:42:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771394,2018-08-20 23:53:53 UTC,"For my use case, I was able to kill gvfsd-mtp after attaching my phone. What I wanted to do still worked, so apparently gvfsd-mtp is not required for my use case.  You have to kill it quickly though or the system becomes unresponsive."
1771394,2018-05-17 00:57:07 UTC,"I just experienced this too. If you don't need them, remove the adb files from ubuntu, if you're passing the USB device onto the guest OS, you don't need them anyway."
1771394,2018-05-15 17:10:51 UTC,"Sorry, 12 G of RAM, not 16.  16 is the system max, I only have 12 installed."
1771394,2018-05-17 01:24:27 UTC,"Thanks, I'll give it a try, although I use adb on the host, maybe I can
disable it, if that's what's causing the issue."
1771396,2019-03-02 10:24:14 UTC,is this still an issue now that Firefox 65.0.1 is the currently supported release? Is Chromium still affected too? Did/does this affect links from other websites or just Twitter?
1771396,2019-03-02 18:09:04 UTC,"Yes, still happens in Firefox 65.0.1"
1771396,2019-03-02 18:12:14 UTC,"In firefox, the pasted url is there too, but invisible.
See attachment."
1771396,2019-03-21 10:00:24 UTC,I am able to reproduce the issue in a disco VM.
1771397,2018-05-15 17:37:46 UTC,A cursory glance through https://docs.angularjs.org/guide/migration#migrating-from-1-6-to-1-7 didn't turn up any removed constructs that Evergreen appears to be using directly.
1771397,2018-05-16 13:57:27 UTC,"I've convinced myself that updating ngToast to simply state that it's compatible with AngularJS 1.7 suffices to (1) remove the extra pulling in of AngularJS 1.5 into the bundle, (2) ensure that tests pass and the web staff client bundle works, and (3) that toasts are still toasty."
1771397,2018-05-16 15:00:44 UTC,And here's my pull request on GitHub and the relevant GitHub issue:
1771403,2018-05-15 18:37:28 UTC,"Hm, I've been able to deploy es-27 a few different times now without hitting this. Maybe a transient issue with the elastic.co repo."
1771403,2020-06-14 04:17:31 UTC,[Expired for Elasticsearch Charm because there has been no activity for 60 days.]
1771404,2018-05-24 04:44:37 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1771413,2018-05-27 19:03:37 UTC,"Hello, I was experiencing something similar. I'd like to request some data from you; seems we might have duplicate bugs, so I'm trying to narrowing if they all are reporting the same failures, and I have a potential fix for it."
1771413,2018-07-07 18:32:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771414,2021-02-17 17:06:34 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1771414,2019-02-26 13:32:41 UTC,Is this still needed?
1771426,2018-05-21 13:48:59 UTC,"+1, I think that the name should include the controller name, the cloud, and the juju version in the backup file path. I'd not worry about the ""juju"" part since the it should be clear enough."
1771428,2018-05-17 01:57:38 UTC,"isn't this how dj's cue up a track on cdj's, playing a track, then bringing it back to the first beat, scratching at it, then putting the cue down?"
1771428,2018-05-17 04:25:02 UTC,"Sure, but they usually pause before setting the cue, so it can be precisely where they want it. (CDJs repeatedly play the CD frame selected when in pause mode so you can hear exactly where you're setting the cue.)"
1771428,2018-05-17 06:18:38 UTC,"Confirmed: https://www.youtube.com/watch?v=VyK-qAQzCGI
Interesting! Might have to put in a feature request."
1771430,2019-09-03 11:26:54 UTC,Which version of virtualbox do you use? I found only virtualbox-5.2 works. I got the same problem with virtualbox-6.0
1771430,2018-05-18 15:49:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771430,2018-06-29 04:21:33 UTC,"Have you installed the vagrant-libvirt plugin from the same user?
i.e. vagrant plugin install vagrant-libvirt"
1771430,2018-07-26 08:23:16 UTC,"$ vagrant plugin install vagrant-libvirt
$ sudo /etc/init.d/sudo apt install qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virt-manager
$ sudo adduser pavel libvirt
$ sudo adduser pavel libvirt-qemu
$ sudo /etc/init.d/libvirtd restart"
1771430,2020-05-26 14:10:27 UTC,"Hi there,
When I run the following command:"
1771431,2019-02-04 10:43:47 UTC,The bug is still present in 4.20.5-100.fc28.x86_64.
1771431,2019-01-29 16:24:40 UTC,*********** MASS BUG UPDATE **************
1771431,2018-12-29 17:27:42 UTC,Thu bug is still present in Fedor 29 (kernel version 4.19.10-300.fc29.x86_64)
1771431,2018-10-14 13:48:54 UTC,*** Bug 1521100 has been marked as a duplicate of this bug. ***
1771431,2018-10-14 20:57:16 UTC,"The kernel has a module for this, ""hid-primax"", which re-orders the received HID reports to make them compliant."
1771431,2019-02-11 09:46:38 UTC,"Keyboard is sending extra byte with each key-press, as temporary workaaround you can use mapping in this repository (tested on Fedora 28 with 4.20 kernel)
https://github.com/miskopo/lenovo-professional-wireless-kbd-linux-driver"
1771431,2018-11-09 16:36:38 UTC,Changed from old Fedora bug (1521100) to new (1625415)
1771431,2019-02-24 18:35:24 UTC,@Tj
1771431,2018-09-04 21:47:46 UTC,"I am still experiencing this issue on the latest kernel (Fedora 28).
4.17.19-200.fc28.x86_64"
1771431,2019-02-26 13:28:36 UTC,"Ok, I think I understand how to add IDs to the code. What should I do with the modified code? Commit and do a pull request?"
1771431,2019-03-05 10:28:40 UTC,"John, please test this kernel:
https://people.canonical.com/~khfeng/lp1771431/"
1771431,2019-03-08 20:24:13 UTC,"Kai-Heng: I just tested your kernel, but it didn't solve the keyboard issue. However, it seemed to screw up the mouse, which of course has the same vendor and device id, since they operate through the same usb connector. With this kernel the mouse was making large erratic jumps and generating click events when I was just moving the mouse."
1771431,2019-03-09 07:42:41 UTC,"John, please file a new bug report and let's continue or discussion there."
1771431,2019-05-18 08:54:37 UTC,Keyboard still doesn't work. Fedora 30 - Kernel 5.0.13-300.fc30.x86_64.
1771431,2019-09-19 16:45:19 UTC,"This is finally fixed! I test it in Ubuntu 18.04 kernel: 4.15.0-64, Ubuntu 18.04.3 kernel: 5.0.0-29."
1771431,2019-09-19 16:46:41 UTC,Bug report on fedora when they also mention that it was fixed in Fedora 30
1771431,2018-10-14 13:48:54 UTC,*** This bug has been marked as a duplicate of bug 1625415 ***
1771431,2019-02-26 11:55:00 UTC,"Follow commit f6a04605f303852963f3f357d19b967aa83c172f and adds your ID should be suffice.
I can make a patch and build a test kernel if you like."
1771431,2018-10-14 13:46:36 UTC,Kernel 4.18.11-200.fc28.x86_64 and it still doesn't work.
1771431,2018-08-29 15:12:40 UTC,"*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously."
1771431,2018-10-01 21:18:01 UTC,"We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs."
1771431,2017-11-06 07:56:41 UTC,"Hello,"
1771431,2017-11-06 08:17:38 UTC,"On Mon, Nov 06, 2017 at 07:56:41AM +0000, <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=197787
>
>             Bug ID: 197787
>            Summary: Lenovo Professional Keyboard not working
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 4.12
"
1771431,2017-12-05 19:45:58 UTC,Description of problem:
1771431,2018-01-08 08:51:47 UTC,"Same problem with
Lenovo keyboard and mouse combo (4X30H567)"
1771431,2018-01-10 15:02:39 UTC,"Maybe I found solution, but it didn't test."
1771431,2018-02-20 20:00:09 UTC,"We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs."
1771431,2018-02-22 19:48:46 UTC,Same problem with Lenovo keyboard and mouse combos (4X30M39472 and 4X30H56809).
1771431,2018-05-06 14:06:17 UTC,I upgraded system to Fedora 28 and Kernel 4.16.6-302.fc28.x86_64 and the issue is still not resolved. The keyboard doesn't work.
1771431,2018-10-02 08:22:29 UTC,Bug is still present in 4.18.10-200.fc28.x86_64.
1771431,2018-05-15 21:30:08 UTC,This change was made by a bot.
1771431,2018-07-23 15:06:46 UTC,*********** MASS BUG UPDATE **************
1771431,2018-05-06 14:15:14 UTC,I have installed Kernel 4.16.6-302.fc28.x86_64 (Fedora) and 4.15.0-20 (Uubntu) and the keyboard still doesn't work. Is ts possible to fixed it?
1771431,2018-09-04 21:44:00 UTC,+++ This bug was initially created as a clone of Bug #1521100 +++
1771431,2018-09-25 17:09:50 UTC,"Hi guys, any progress on this? May I help anyhow? It is really annoying bug."
1771431,2018-09-26 19:25:43 UTC,Added reports on Kernel mailing lists to de description:
1771433,2018-05-21 13:50:44 UTC,Are we not storing backups by default now? I now I saw that we were adding code to clean old backups but you'd still be keeping one. Do we have notes on what the plan is here?
1771433,2018-05-16 16:48:54 UTC,"Eric, yes, just as you described."
1771433,2018-05-16 16:31:19 UTC,"Hi Peter,"
1771433,2018-05-25 16:46:41 UTC,"Also, I feel like the 'file' option should also be consistent between `create-backup` and `restore-backup`. Currently, there is '--filename' and '--file', respectively. I favour the latter (--file). Either that or use very different names like '--output' and '--input'."
1771433,2018-05-16 12:09:44 UTC,But '--file' is used to denote a local backup.
1771433,2018-05-16 09:13:26 UTC,"FWIW that is because download/show/remove *must* be talking about the
remote backup, while ""restore-backup"" might be talking about a local one or
a remote one.
If we move to not storing backups on the controllers by default, then none
of download/remove/show become useful because there is nothing for them to
operate on."
1771443,2018-05-17 14:25:07 UTC,https://github.com/CanonicalLtd/landscape-client/pull/48
1771443,2018-05-30 12:12:07 UTC,"Sponsored in devel release (Cosmic), we can go ahead with the SRU once the package cosmic turn to ""Fix Released""."
1771443,2018-05-30 12:18:25 UTC,"Addition note, might be a good idea to start target cosmic (as we are in the beginning of the cycle) to introduce an autopkgtest for landscape-client ?"
1771443,2018-05-30 15:53:31 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu4
1771443,2018-05-30 19:17:22 UTC,Sponsored for bionic.
1771443,2018-05-31 19:23:05 UTC,"Hello Alex, or anyone else affected,"
1771443,2018-06-11 17:00:37 UTC,I've tested the client on Bionic and successfully added bionic repositories to it.
1771443,2018-06-13 09:44:22 UTC,What is the package version string of the successful test please?
1771443,2018-06-13 13:17:59 UTC,"landscape-client 18.01-0ubuntu3.1
landscape-common 18.01-0ubuntu3.1"
1771443,2018-06-14 01:16:53 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu3.1
1771443,2018-06-14 01:16:59 UTC,"The verification of the Stable Release Update for landscape-client has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1771445,2018-05-16 15:25:09 UTC,How exactly should it work in a three pane Layout where you can have two track tables side by side?
1771457,2019-09-19 11:58:14 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1771457,2018-05-15 23:41:07 UTC,"I've renamed the title for this bug, and comment #1 explains what the solution should be."
1771457,2018-05-15 23:37:11 UTC,"It's not really clear to me that this is a bug; it's currently working as intended (given the long history of this API endpoint, which dates back to MAAS 1.x)."
1771457,2018-05-15 23:35:31 UTC,Context: https://bugs.launchpad.net/maas/+bug/1629061
1771465,2018-05-16 01:01:51 UTC,"@rod,"
1771465,2018-05-21 16:22:52 UTC,"After upgrading to MAAS 2.4.0~rc2-6980-gc5ebdd7b1-0ubuntu1~18.04.1 and rebooting, the problem seems to have cleared up. I'll re-open the bug if I run into it again."
1771465,2018-12-03 23:23:24 UTC,This problem is back. I'm currently experiencing it with MAAS 2.4.2 (7034-g2f5deb8b8-0ubuntu1).
1771465,2019-02-18 10:53:58 UTC,"New information: Changing another field in the ""Machine Configuration"" section (I used ""Minimum Kernel"") enables editing the ""Tags"" field, at least for a while."
1771465,2019-09-19 12:05:34 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1771466,2018-05-16 04:21:23 UTC,"Please report this behavioural issue to the Gnome developers here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues"
1771466,2018-05-16 17:45:26 UTC,"Upstream bug is
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/282"
1771476,2018-05-20 16:33:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771476,2018-05-20 16:45:09 UTC,even i did experience same
1771476,2018-05-20 17:49:40 UTC,"Hello,"
1771476,2019-04-30 16:43:39 UTC,Ubuntu 18.04 offers both openjdk-8-jdk and openjdk-11-jdk.
1771477,2018-05-18 04:58:30 UTC,PR of fix: https://github.com/juju/juju/pull/8725
1771477,2018-08-03 15:50:01 UTC,Should this be fix committed? Or even fix released?
1771477,2019-07-08 06:23:22 UTC,Marking as Fix Released as the PR landed a year ago.
1771480,2018-06-18 17:26:05 UTC,"ubuntu@lp1771480:~$ uname -a
Linux lp1771480 3.13.0-151-generic #201-Ubuntu SMP Wed May 30 14:22:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1771480:~$ dmesg | grep -m 1 -A 2 dev_disable_lro
[    3.811702] WARNING: CPU: 2 PID: 1209 at /build/linux-qbUwJB/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90()
[    3.811704] netdevice: bond0.2004
[    3.811704] failed to disable LRO!"
1771480,2018-05-16 03:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771480,2018-07-02 08:28:24 UTC,This bug was fixed in the package linux - 3.13.0-153.203
1771480,2018-06-15 10:33:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1771480,2018-05-16 02:54:44 UTC,This occurred during the deployment of the DPDK compute. The DPDK was not deployed. The bond0 and bond1 configuration appears to have failed.
1771480,2018-05-16 04:15:29 UTC,The warning message:
1771480,2018-05-16 15:59:35 UTC,"The dev_disable_lro warning is happening due to some logic issues in the features code.  The LRO on the VLAN (bond0.200, e.g.) that's being warned about does end up being disabled by a NETDEV_FEAT_CHANGE callback when the underlying bond0's features are updated, so the warning is spurious."
1771484,2018-05-17 13:08:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771485,2018-05-17 13:08:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771491,2018-05-16 11:12:35 UTC,Looks like libapparmor doesn't like this log format :-(
1771493,2018-05-17 20:35:03 UTC,"Divya, well the title of the bug is ""Skip logging of ipaddress in neutron logs"", if it needs to be more generic that should be changed.  As I mentioned, if the intent is to have a way to not log IPs in any Openstack service, then that needs to be done in the logging library (IMHO), else some will be missed.  Otherwise it will be up to the developers to decide what IPs should be logged versus what shouldn't."
1771493,2018-06-04 21:00:04 UTC,"Divya, your last paragraph, in short, says the entity storing the log, not the logging itself, is the crux of the problem.  The policy and control of that information are outside the scope of neutron.  So it's still unclear if there is work for us to do here."
1771493,2018-05-16 07:09:39 UTC,I'm not a layer and I don't know details of GDPR compliance but the same IP address is stored in Neutron's (and Nova as well probably) database. Do You want to remove it from there also? It's IMO not possible :)
1771493,2018-05-16 08:05:54 UTC,"We don't have much concern about storing IP address in database, major concern is about IP address in logs because when customers face some issues, without having notice that their IP addresses exits in logs, they share the logs for debugging, this should be not allowed as per GDPR."
1771493,2018-05-16 15:35:55 UTC,"I am not a lawyer either, but if we're talking about redacting all IP(v6) addresses from the logs this should probably be done in oslo.log since there are other services that are probably logging them as well."
1771493,2018-05-17 11:50:38 UTC,"We must double and triple check if this is the right thing to do - Because as Brian said the cost is that it will often make troubleshooting impossible, and users wouldn't like that either."
1771493,2018-05-17 12:06:56 UTC,This defect is not about removing ip logging from neutron logs. It is about putting a mechanism in place such that any deployment that does not want to log ip (due to compliance requirements) should have a way to achieve that.
1771493,2018-05-30 11:47:19 UTC,"Brian, I have updated the title of the bug. https://en.wikipedia.org/wiki/General_Data_Protection_Regulation should provide some general information about this new law. As per this, ipaddress comes under personal data (because in certain cases ipaddress in itself or with the help of additional data could help in identifying a person) and the law focuses on protecting personal data of EU citizens and preventing misuse of it - violation could lead to 20 million pound or 4% of the annual global turnover."
1771494,2020-03-25 02:46:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/714816"
1771494,2020-04-25 12:10:14 UTC,"Reviewed:  https://review.opendev.org/714816
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=45c5229459647c89a4c047f70abf0031dfea1b90
Submitter: Zuul
Branch:    master"
1771500,2018-05-22 20:32:40 UTC,"Ok, we have the RCA for this. Great job by @tredaelli who joined me in debugging the issue and dug into the kernel changes spotting the possible culprit. He reverted this patch [0] on latest kernel for 7.5 and the problem goes away. The BZ got reassigned and we need to decide whether we want to revert this patch (it's not present in kernel-alt) or fix it on the OVS datapath as the reason is that we're clearing conntrack for the SNAT action [1] and then the packets hit a default REJECT iptables rule installed by iptables.service."
1771500,2018-07-12 15:45:03 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/582286"
1771500,2018-05-22 08:44:00 UTC,"Reviewed:  https://review.openstack.org/569463
Committed: https://git.openstack.org/cgit/openstack/packstack/commit/?id=1b97ae48de202b49079c579218bd4288ae649161
Submitter: Zuul
Branch:    stable/queens"
1771500,2018-07-12 20:38:22 UTC,"Reviewed:  https://review.openstack.org/582286
Committed: https://git.openstack.org/cgit/openstack/packstack/commit/?id=1574a38aa97e9dac9bc2848faccef13fe10a285e
Submitter: Zuul
Branch:    stable/pike"
1771500,2018-05-18 16:31:23 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/569463"
1771500,2018-05-18 16:23:22 UTC,"Reviewed:  https://review.openstack.org/569012
Committed: https://git.openstack.org/cgit/openstack/packstack/commit/?id=e9e6ad87a0237908236c96b49932afa2e96a52c5
Submitter: Zuul
Branch:    master"
1771500,2018-05-17 17:12:47 UTC,"Some additional info, which may help in drill down the issue further."
1771500,2018-05-17 05:20:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/569012"
1771500,2018-05-16 13:03:30 UTC,"Numan found out that adding an OVS port to br-ex and trying to connect to the instance from there he didn't find the issue.
I repeated the tcpdump test doing the same thing, ie. created a network namespace and added an internal port to br-ex. This is the result."
1771500,2018-05-18 14:06:01 UTC,"Correct, if we delete the following rule from INPUT chain, then everything works."
1771500,2018-05-16 12:44:32 UTC,"I have attached a tcpdump to br-ex on the host and then opened a netcat tcp connection to the FIP of the guest VM. When the connection got established, I sent ""DDDDDDDDDDDDDDDDDDDD"" from the VM. This is what is being received on br-ex in the host:
08:40:08.503759 fa:16:3e:1f:24:8a > 6e:6d:7f:9a:fa:4e, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 63, id 11684, offset 0, flags [DF], proto TCP (6), length 73)
    172.24.4.3.distinct > 172.24.4.1.59512: Flags [P.], cksum 0x6070 (incorrect -> 0xcb31), seq 21:42, ack 1, win 3475, options [nop,nop,TS val 20043541 ecr 431651366], length 21
E..I-.@.?...........'..x....L""......`p.....
.1....z&DDDDDDDDDDDDDDDDDDDD"
1771501,2018-08-04 11:00:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771506,2019-05-09 12:05:10 UTC,"Hello Thomas, or anyone else affected,"
1771506,2019-05-16 17:17:33 UTC,"Hello Thomas, or anyone else affected,"
1771506,2019-05-20 15:04:43 UTC,"Hello Thomas, or anyone else affected,"
1771506,2019-05-21 10:02:13 UTC,"Bionic is great, previously it would fail nova.tests.unit.virt.xenapi.test_xenapi.XenAPIDiffieHellmanTestCase tests but now they pass."
1771506,2019-05-21 14:29:29 UTC,"@Dimitri, thanks very much. I've pushed changes to cosmic and disco branches to drop the skip-openssl-1.1.1-tests.patch patch and have built them successfully (locally) for disco, cosmic, bionic-stein, and bionic-rocky. I'm going to hold off on uploads just for that change as nova has a lot of churn and they'll get picked up on the next SRU."
1771506,2019-05-21 14:31:48 UTC,This has also built successfully in the queens cloud archive.
1771506,2019-06-05 21:17:46 UTC,This bug was fixed in the package nova - 2:18.1.0-0ubuntu3
1771506,2019-06-04 06:36:26 UTC,"Reviewed:  https://review.opendev.org/656304
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=64793cf6f77c5ba7c9ea51662d936c7545ffce8c
Submitter: Zuul
Branch:    stable/stein"
1771506,2019-06-05 21:17:01 UTC,This bug was fixed in the package nova - 2:17.0.9-0ubuntu3
1771506,2019-05-16 17:10:48 UTC,"Hello Thomas, or anyone else affected,"
1771506,2019-07-01 20:34:09 UTC,"Reviewed:  https://review.opendev.org/656308
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5b0adaa0ca5f757bb224d1ffac0c6705b03ee2ed
Submitter: Zuul
Branch:    stable/queens"
1771506,2019-07-03 18:10:39 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1771506,2019-05-23 02:48:31 UTC,"Reviewed:  https://review.opendev.org/656307
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8241b47967adb792a4254eeb58fda1fc55edf314
Submitter: Zuul
Branch:    stable/rocky"
1771506,2019-05-09 12:51:58 UTC,"Hello Thomas, or anyone else affected,"
1771506,2019-05-08 19:30:38 UTC,"Hello Thomas, or anyone else affected,"
1771506,2019-05-08 19:36:58 UTC,"Hello Thomas, or anyone else affected,"
1771506,2019-07-03 18:20:27 UTC,This bug was fixed in the package nova - 2:19.0.0-0ubuntu2.3
1771506,2019-05-08 19:28:15 UTC,"Hello Thomas, or anyone else affected,"
1771506,2019-05-08 19:10:10 UTC,"An upload of nova to disco-proposed has been rejected from the upload queue for the following reason: ""The .changes file doesn't incorporate changes in 2:19.0.0-0ubuntu2.1 please reupload.""."
1771506,2019-05-03 21:40:30 UTC,"New versions of nova with this fix have been uploaded to eoan, disco, cosmic, and bionic. Stable release uploads are awaiting review from the SRU team [1]."
1771506,2019-05-02 21:31:34 UTC,This bug was fixed in the package nova - 2:19.0.0-0ubuntu4
1771506,2019-04-28 03:51:11 UTC,"Reviewed:  https://review.opendev.org/635533
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1da71fa4ab1d7d0f580cd5cbc97f2dfd2e1c378a
Submitter: Zuul
Branch:    master"
1771506,2019-02-07 15:18:51 UTC,"@xnox, thanks for the patch. I've submitted it to the upstream master branch. Once that lands I'll start backporting to stable branches and Ubuntu."
1771506,2019-02-07 15:14:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/635533"
1771506,2019-02-07 14:30:55 UTC,"This is not just a testing issue, it means that xenapi will not able to talk to xen agent at runtime, with openssl 1.1.1 binary."
1771506,2019-01-23 17:42:29 UTC,I also hit this bug! Any news since then?
1771506,2018-10-03 18:04:26 UTC,I'm hitting this as well now that we have openssl 1.1.1 in cosmic-proposed. This is affecting rocky and above for ubuntu. Unfortunately this is preventing our unit tests from running successfully for an 18.0.1 release. To recreate:
1771506,2018-05-17 06:00:24 UTC,"seems some key deprecated ? can we check [0] above to know which of follow param lead to error?
best way would be within 1.1.1 env to consturct a command string and try it .."
1771506,2019-05-09 12:04:10 UTC,"Hello Thomas, or anyone else affected,"
1771513,2018-05-16 10:37:38 UTC,Can you run the following command in a terminal and share the output?
1771517,2019-09-27 09:18:02 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/569026
Reason: Patch is more than a year old with negative reviews. Feel free to restore it if you still work on it."
1771517,2020-03-18 08:57:41 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/569024
Reason: This is a pretty old patch with negative review. Feel free to restore it (or ask gibi on irc to restore it) if you still working on it."
1771517,2018-05-17 06:18:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569024"
1771523,2018-09-11 17:21:15 UTC,"We need actual functional testing of the AggregateMultiTenancyIsolation filter - because it's confusing in how it works. It looks like the problem with that filter is hosts in the tenant-isolated aggregates are restricted to those tenants, but the tenants themselves are not restricted to hosts in that tenant-isolated aggregate. So if the scheduler picks a few hosts where some are in and some are outside the aggregate and weighs the hosts outside the aggregate higher, the tenant will get those hosts rather than the isolated hosts."
1771523,2019-11-14 14:28:51 UTC,This might be solved by https://specs.openstack.org/openstack/nova-specs/specs/train/approved/placement-req-filter-forbidden-aggregates.html in Train. Admin docs:
1771523,2018-09-11 22:08:17 UTC,Related nova patch to fix the docs on the AggregateMultiTenancyIsolation filter and adds a functional test to prove the behavior:
1771523,2018-08-24 04:58:00 UTC,"Answers questions in the comment #3 from blazar team.
I also left some comments in a related spec https://review.openstack.org/#/c/593475 about how blazar works with aggregates."
1771523,2018-09-05 07:20:01 UTC,Answers to questions in comment #4:
1771523,2018-07-19 14:45:06 UTC,What overlap exists with the Blazar project and it's concept of dedicated hosts?
1771523,2018-05-23 22:09:07 UTC,"Problem: the AggregateMultiTenancyIsolation filter makes it so that project A goes exactly on isolated hosts for that project, but it does not prevent the inverse, which is that project B-Z also can't land on that isolated host. See from the doc:"
1771523,2018-05-23 22:01:00 UTC,There is a new placement-related scheduler filter in Rocky that CERN is using to do multi-tenant isolation via host aggregates and resolves the aggregate metadata 255 limitation:
1771523,2018-08-15 03:11:35 UTC,Question about requirements:
1771525,2018-05-16 09:04:45 UTC,"Also, I just confirmed that although Xsane and other scan programs like Simple Scan and Skanlite detect the scanner (only if it is already plugged in when Kubuntu 18.04 starts), however only Xsane works Ok (except that in this 18.04 version of Kubuntu Xsane program only starts receiving data once the exploration of the document has finished, which makes much slower scanning several documents, as I describe in the Bug #1771520."
1771525,2018-08-06 09:42:27 UTC,"Just found the solution for this bug, in https://forums.linuxmint.com/viewtopic.php?t=221071"
1771528,2018-05-20 03:57:54 UTC,After 'pkill indicator-*' these indicators appears.
1771532,2018-05-16 09:42:23 UTC,Here is the fix
1771539,2021-01-05 14:00:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771539,2018-08-21 07:49:48 UTC,"Mario,"
1771539,2018-08-21 04:17:26 UTC,[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]
1771539,2018-06-21 01:47:09 UTC,Mario Costa:
1771539,2018-06-20 13:23:23 UTC,"Since I've reinstalled the ubuntu 16.04, the problem persists, but the kernel parameter  (radeon.runpm=0) is no longer present. I'll provide another log dump, when as soon as the problem occurs again."
1771539,2018-06-07 08:42:30 UTC,"1)
```
$ls -la /var/crash/
total 8080
drwxrwsrwt  2 root     whoopsie    4096 Jun  7 01:30 .
drwxr-xr-x 14 root     root        4096 Ago  1  2017 ..
-rwxrwxrwx  1 root     whoopsie       0 Jun  7 01:17 .lock
-rw-r-----  1 root     whoopsie 8265453 Jun  7 01:28 _usr_lib_xorg_Xorg.0.crash
-rw-r--r--  1 root     whoopsie       0 Jun  7 01:30 _usr_lib_xorg_Xorg.0.upload
-rw-------  1 whoopsie whoopsie       0 Jun  7 01:30 _usr_lib_xorg_Xorg.0.uploaded
```"
1771539,2018-06-21 14:05:05 UTC,"A) sudo cat /var/lib/whoopsie/whoopsie-id
126a6c719bcce7c3ad86f82dbca39dc81524233531d72481f4d5a2a4f2fac31510f8ea9e7daf5748cbe4667770413d4cc3e5644d79f968c0df829149ea1011b5"
1771539,2018-06-07 00:27:53 UTC,"Hi, thanks for you promptly response, unfortunately only now I had the time to check the things above."
1771539,2018-05-25 16:35:40 UTC,Mario Costa:
1771539,2018-05-25 07:01:03 UTC,"Honestly, I think it got worst at some point, after some update or after I changed from Unity to Gnome. Unfortunately I don't really have any additional info."
1771539,2018-05-25 03:37:51 UTC,"Mario Costa, thank you for reporting this and helping make Ubuntu better. Please advise to all of the following:"
1771539,2018-06-07 01:22:16 UTC,Mario Costa:
1771545,2018-06-01 13:42:50 UTC,"On 2018-06-01 04:52 AM, Alexander Traud wrote:

>> unbound wants to write to that file to keep it current.
>
> Sorry for asking as I am not so much into root.key and package
> updates. However I do not understand that sentence yet and I am
> terrible curious.
>> From the user perspective: The user needs a current root.key file
>> to do
> validation. What is the difference whether that happens via a
> package update/backport, or unbound-anchor, or both? In other words,
> if unbound- anchor writes to ""/usr/share/dns/root.key"", why is that
> bad? If dns- root-data is updated/backported and writes to the very
> same file, why is that bad? In both cases, a different technology is
> used to get a current root.key. Does that qualify to separate
> things?
"
1771545,2018-06-01 08:52:41 UTC,"> unbound wants to write to that file to keep it current.
"
1771545,2018-05-31 16:50:03 UTC,"On 2018-05-31 08:30 AM, Alexander Traud wrote:

> However, there might be another approach: The package ""dns-root-data""
> is not just in Universe but in Main and is one of the sources of that
> root.key already. Perhaps it is easier to update the package
> ""dns-root-data"" manually and then - simply symlink the root.keys
> or/and - change libunbound2 to use that root.key on default directly
> (set at compile time).
"
1771545,2018-05-27 22:03:38 UTC,Reported to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900241
1771545,2018-05-31 12:30:41 UTC,"Simon, thank you very much for taking over. I am very much with your proposal: Moving that script from unbound to unbound-anchor plus making unbound-anchor a dependency of libunbound2. That was my first thought as well."
1771545,2018-05-25 19:57:35 UTC,Maybe related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641704
1771545,2018-05-25 19:55:01 UTC,Thanks for filing this bug in Ubuntu.
1771545,2018-05-25 20:05:47 UTC,"Currently, the root.key is managed by a helper script shipped with the unbound package. It would make sense to have the root.key managed automatically for apps relying on libunbound2 for DNS resolution. As such, I think a possible way to achieve this would be to have the helper script shipped with unbound-anchor and make unbound-anchor a dependency (recommends?) for libunbound2. The helper script should be called at some frequency to ensure that root KSK rollovers are processed properly. For that part, a cron job or a systemd timer unit would do."
1771547,2018-05-16 12:52:21 UTC,"Hi Michal,"
1771547,2018-05-16 12:54:31 UTC,"Also, please provide the list of vlan's and ID's. Is vlan 1502 the VID or is it the DB 'id' of the vlan?"
1771547,2018-05-16 13:39:49 UTC,"Hi,"
1771547,2018-05-16 14:12:49 UTC,"I'm re-opening this bug report with the goal of improving the docstrings and error messages, as it doesn't clearly identify what it is needed."
1771547,2019-09-19 11:58:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1771548,2018-05-16 11:06:04 UTC,Error:
1771559,2020-04-14 09:25:15 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/719777"
1771559,2021-02-18 06:41:24 UTC,It turns out the previous fixes are not sufficient.
1771559,2021-02-18 06:42:14 UTC,https://review.opendev.org/c/openstack/horizon/+/730288 is trying to fix it.
1771559,2020-04-27 16:06:10 UTC,"Reviewed:  https://review.opendev.org/722533
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d4028b97db87f54ba2c43268b5adccfa497ed594
Submitter: Zuul
Branch:    stable/stein"
1771559,2020-04-23 22:15:00 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/722533"
1771559,2020-04-23 13:20:38 UTC,"Reviewed:  https://review.opendev.org/721138
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f26c88721614d1c25bcd26740b8fb20a7a97bd05
Submitter: Zuul
Branch:    stable/train"
1771559,2020-04-20 02:33:15 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/721138"
1771559,2020-04-15 14:27:14 UTC,"Reviewed:  https://review.opendev.org/719777
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=74d76e900f28e88190a35bff921c56349077ca53
Submitter: Zuul
Branch:    master"
1771559,2020-03-30 15:00:08 UTC,"it turns out that https://review.opendev.org/714274 is a partial fix.
we still see a problem in the material design theme, for example https://pasteboard.co/J1uIQVW.png"
1771559,2018-09-01 13:36:09 UTC,This happens to my material themes when horizon compress `/var/lib/openstack-dashboard/static/horizon/lib/mdi/scss/_icons.scss `  while placing icon content for example 'f101' as 'xf101' instead of the normal one '\f101'
1771559,2020-03-25 01:01:48 UTC,"Reviewed:  https://review.opendev.org/714274
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=ddc52a7405f0be38629f665d24bcf75022ce0018
Submitter: Zuul
Branch:    master"
1771559,2018-09-01 14:27:44 UTC,"problem solved. This problem cause by pyScss==1.3.5 and after I downgrade pyScss to 1.3.4, material icons content are being  concated fine."
1771559,2018-10-05 14:58:41 UTC,"Hi Julien and chrisren,"
1771559,2020-03-25 10:40:40 UTC,This issue was fixed in the openstack/horizon 18.2.0 release.
1771559,2019-10-29 15:32:42 UTC,"$ pip freeze | grep pyScss
pyScss==1.3.4"
1771559,2019-10-29 15:45:51 UTC,"And for cross-reference, the ticket by ~chrisren on Kronuz/pyScss:
https://github.com/Kronuz/pyScss/issues/375"
1771559,2018-11-22 15:14:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771568,2018-05-16 15:04:12 UTC,"Related to this, when duplicate items are removed from a copy bucket in the Web client, they still appear in the same bucket in the staff client."
1771568,2019-07-25 21:05:36 UTC,See also 1485695
1771568,2020-02-03 21:25:45 UTC,"The same issue is present in the user buckets.  It is possible to add a pending user multiple times to a user bucket.
Josh"
1771574,2020-07-29 08:53:00 UTC,"This was fixed here: https://review.opendev.org/#/c/583117/
for the nsx-v3 plugin, pike & up"
1771580,2018-09-05 07:04:07 UTC,Adjutant is now an official project. In my opinion solves this issue in general.
1771581,2018-05-23 22:02:01 UTC,We have a specification that might address this up for review for Rocky [0].
1771581,2018-05-23 22:03:10 UTC,(the rendered version of the specification is a lot easier to read)
1771581,2018-09-05 07:41:32 UTC,Solution mentioned in comment #1 was discussed at the Forum session in Vancouver. Strict-two-level solves my use case for this. (thanks @lbragstad + team) How about other operators? Do you have the need for more depth?
1771581,2018-09-11 16:53:49 UTC,We're looking at beginning adoption of keystone unified limits in Nova via oslo.limit this cycle (Stein). We're going to discuss it on Friday at the PTG at the Nova room [1].
1771581,2018-09-27 07:26:04 UTC,"Keystone spec: https://review.openstack.org/#/c/599491/
Code(WIP): https://review.openstack.org/#/c/602824/"
1771582,2018-09-25 08:36:16 UTC,"A lot of outstanding questions indeed. As you say, shared stuff is hard to know what to do with. Billing/usage data is also important to keep track on for some period of time even though a project doesn't exist anymore..."
1771582,2018-09-21 14:38:01 UTC,"You're correct that ospurge is not managed by an official project team today. With some support from users, I'm sure we could find a home for it. And of course not being official doesn't mean it isn't maintained."
1771582,2018-09-21 12:59:53 UTC,"I see that we should really create a new description of this ""cross project issue"", and leave out technical solutions as discussed in Denver."
1771582,2018-05-23 22:18:39 UTC,"Please use os-purge, and lets get feedback."
1771582,2018-09-20 13:49:40 UTC,"ospurge uses shade, not direct database access. Using a standalone tool like that to orchestrate removing a project across a cloud seems like a reasonable design, so it would be useful to understand why a central API is more desirable."
1771586,2018-05-23 22:16:55 UTC,We have a specification targeted for the Rocky release to improve user experience here [0].
1771586,2018-09-05 08:19:08 UTC,Could not see it in the list of done items. Postponed to stein or later?
1771586,2018-10-31 07:37:11 UTC,"Work in progress here:
https://review.openstack.org/#/c/611230/11"
1771587,2018-05-23 21:50:38 UTC,Current nova spec:
1771587,2018-05-24 10:00:38 UTC,Full list of proposed changes:
1771591,2018-07-19 14:45:39 UTC,Marking as Incomplete until there is more investigation / detail about the problem description and use case for this.
1771591,2018-05-16 14:17:15 UTC,"Need to be checked, confirmed, clarified, updated."
1771592,2018-05-16 14:18:26 UTC,Need to be verified.
1771592,2018-09-05 07:44:19 UTC,Need more information from Pawel regarding the actual use case here.
1771592,2018-09-11 15:36:30 UTC,Alex from Intel has this spec up: https://review.openstack.org/#/c/569011/ for quota by resource class. This can be used for things like quota by flavor as well as quota by combinations of Flavor+AZ+etc
1771594,2018-09-11 16:09:03 UTC,https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/graphql
1771602,2019-02-26 13:35:15 UTC,is this still needed?
1771602,2018-06-04 17:06:56 UTC,"triage: this is not a *failure* event, but perhaps we should *warn* or *inform* when this is the case..."
1771602,2021-02-17 17:06:36 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1771602,2018-05-21 15:24:34 UTC,I'd really wanted to see this marked a critical issue...
1771602,2018-05-21 15:23:17 UTC,I think the issue is not CI limited. Those should belong to validations and productized.
1771602,2018-05-16 19:49:12 UTC,"This also becomes a critical issue with libvirtd.  Since libvirtd is containerized in the nova_libvirt container, it is using an older version of libvirt which is incompatible with the one in centos 7.5.  Due to this when you deploy the deployment hangs at step 4 and is stuck during the deployment at the virsh secret-define command for creating the ceph secret:"
1771602,2018-05-16 15:55:27 UTC,An example of human/debug time spent as a result of this class of issue:
1771602,2018-05-21 15:24:10 UTC,This affects upgrades as well.
1771604,2018-07-04 07:26:40 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1771604,2019-08-24 09:27:29 UTC,"As mentioned in the corresponding Debian report, the binary is reintroduced in bwbar 1.2.3-4 (https://packages.ubuntu.com/eoan/amd64/bwbar/filelist)"
1771605,2021-02-17 17:08:02 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1771608,2018-05-30 12:33:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771609,2019-02-26 13:35:39 UTC,Is this still needed?
1771611,2019-09-17 10:03:05 UTC,"The [Library]..MoveVertical is sending emulated key presses to the sidebar or trackstable, depending on what has focus. The Tab key in the log is sent by setLibraryFocus() in librarycontrol.cpp to re-focus the tracks table whenever a Track select knob is turned while another widget has focus."
1771611,2019-09-17 11:06:55 UTC,"It seems [PLaylist],SelectPlaylist is broken:"
1771611,2020-03-12 16:45:26 UTC,"Partially fixed by https://github.com/mixxxdj/mixxx/pull/2307
""keep the library focused when any deck controls or the overview are clicked"""
1771612,2019-02-26 13:36:06 UTC,Is this still an issue?
1771612,2018-09-25 08:24:03 UTC,"As an update here. Damien and I are exploring a hybrid solution to this long standing limitation.
Namely:
1. At deployment time and at update time we copy all files belonging to the set of pacemaker-related rpms under /var/lib/tripleo/pacemaker-host
2. We bind mount a bunch of folders (amongst which /var/lib/tripleo/pacemaker-host) inside the pcmk containers and we use custom PATH + LD_LIBRARY_PATH (both the temporary ones created by paunch and the ones managed by pcmk)
3. We eventually remove all pacemaker rpms from the HA kolla containers"
1771612,2018-05-16 18:17:31 UTC,"Hard to say. Right now, I'd say that unless we manage to get a working fix that won't impose this version restriction between containers and host, we only support same versions between host and containers (or later version on containers). Not newer on host and older on containers."
1771612,2021-02-17 17:06:39 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1771612,2018-05-16 15:52:32 UTC,Note:
1771612,2018-05-16 15:57:43 UTC,"@michele the RFE is tracking identifying and/or flagging package version mismatches (generally, not specific to pacemaker)."
1771617,2019-09-12 13:51:29 UTC,"Updated by:
https://github.com/openstack/kolla-ansible/commit/c89b901524a7494180de1614a7b5e255589ecbb8#diff-2a66f4864757a03116e6e455901552f0
https://github.com/openstack/kolla-ansible/commit/136210c403feed1df23dbd8ae566e330f667f379#diff-2a66f4864757a03116e6e455901552f0
https://github.com/openstack/kolla-ansible/commit/f0e19ba6476937350115ff2189449e0b00e5ded5#diff-2a66f4864757a03116e6e455901552f0
https://github.com/openstack/kolla-ansible/commit/4b1a1d57a9541bedd81eeb32527064844a89eb8b#diff-2a66f4864757a03116e6e455901552f0"
1771618,2018-05-16 20:39:42 UTC,"Agreed, this should be shown in show-controller."
1771618,2019-02-13 15:18:09 UTC,The controller API has been extended with a method (IdentityProviderURL) that returns the identity provider URL if one was specified when the controller was bootstrapped. For more details see: https://github.com/juju/juju/pull/9741
1771625,2018-05-16 16:31:58 UTC,"This is what I mean by ""network-manager tray menu""."
1771625,2018-05-16 16:44:01 UTC,There are two general (but similar) ways to reproduce the bug:
1771626,2018-06-13 14:20:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771632,2018-05-30 21:46:21 UTC,"@Heather, please look at what we currently have first:"
1771632,2018-05-30 19:37:26 UTC,"@petermatulis,  -b has been removed as a restore option in 2.4 here:
https://github.com/juju/juju/pull/8742"
1771632,2018-05-16 17:38:45 UTC,I tried this test again and it worked. There seems to be a level of unpredictability in the process.
1771632,2018-05-16 17:41:15 UTC,In the second test I terminated (not stopped) the underlying controller instance using the cloud dashboard. I don't see how that can affect the observed difference in results though.
1771636,2018-05-20 19:14:31 UTC,"Compare bug 1772206, which would display the full library name as a tooltip when you hover over the shortname.  I think we want both: tooltip when displaying shortname + option to display full name."
1771640,2018-05-16 23:21:15 UTC,"Reviewed:  https://review.openstack.org/568900
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=44d8c653b0ea5e7c109639b6a06d9084f23c0433
Submitter: Zuul
Branch:    stable/queens"
1771640,2018-05-16 18:08:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568919"
1771640,2018-05-16 18:09:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/568920"
1771640,2018-05-16 19:44:51 UTC,"Reviewed:  https://review.openstack.org/568919
Committed: https://git.openstack.org/cgit/openstack/zun-tempest-plugin/commit/?id=4b9e5ddfc4d53035b2f72738b5e97ce64c7e6473
Submitter: Zuul
Branch:    master"
1771640,2018-05-16 19:47:50 UTC,"Reviewed:  https://review.openstack.org/568920
Committed: https://git.openstack.org/cgit/openstack/zun-tempest-plugin/commit/?id=d8280b83f9df4d73707557889a0e17d64a4ae30d
Submitter: Zuul
Branch:    master"
1771640,2018-08-20 18:31:23 UTC,This issue was fixed in the openstack/zun 1.0.1 release.
1771643,2018-06-16 04:08:54 UTC,"ubuntu-report
{
  ""Version"": ""18.04"",
  ""OEM"": {
    ""Vendor"": ""Dell Inc."",
    ""Product"": ""OptiPlex 7010""
  },
  ""BIOS"": {
    ""Vendor"": ""Dell Inc."",
    ""Version"": ""A19""
  },
  ""CPU"": [
    {
      ""Vendor"": ""GenuineIntel"",
      ""Family"": ""6"",
      ""Model"": ""58"",
      ""Stepping"": ""9""
    }
  ],
  ""Arch"": ""amd64"",
  ""GPU"": [
    {
      ""Vendor"": ""10de"",
      ""Model"": ""0df8""
    }
  ],
  ""RAM"": 32.9,
  ""Partitions"": [
    244.6,
    4748.8,
    0.5,
    2147.5,
    2147.5,
    2147.5
  ],
  ""Screens"": [
    {
      ""Resolution"": ""1680x1050"",
      ""Frequency"": ""59.95""
    },
    {
      ""Resolution"": ""1680x1050"",
      ""Frequency"": ""59.95""
    }
  ],
  ""Autologin"": false,
  ""LivePatch"": false,
  ""Session"": {
    ""DE"": ""MATE"",
    ""Name"": ""mate"",
    ""Type"": ""x11""
  },
  ""Timezone"": ""America/Boise""
}"
1771648,2019-05-23 05:33:31 UTC,This was actually fixed via I95d11d85d61bddc6d8600f576801a42af79a6652
1771650,2018-05-19 03:02:37 UTC,"I have a problem that may be related, but I haven't been able to get OpenVPN working.  https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1772066"
1771650,2018-05-25 14:41:10 UTC,No results :
1771650,2018-05-23 10:16:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771650,2018-05-23 15:00:55 UTC,"the description suggests the command line openvpn is used, not the network-manager plugin"
1771650,2018-05-23 15:04:15 UTC,"@Fanar, could you please attach the openvpn logs of the failed service start? You can collect them with:"
1771650,2018-05-25 16:36:29 UTC,Can you try to enable and start it with:
1771650,2020-05-11 13:01:36 UTC,"@Daniel, what version are you using? The /etc/init.d/openvpn screen from bionic has that same snippet you mentioned from upstream"
1771650,2019-11-19 16:14:54 UTC,I changed the first line of #/bin/sh -e to #/bin/bash and it worked
1771650,2019-07-13 08:22:42 UTC,"I also came across this issue.
This is a not quite obvious thing in the default installation (I mean the @-services)."
1771650,2018-11-27 21:45:33 UTC,"It shouldn't be necessary to do explicit ""enable"" calls to make this work. The generator _should_ be finding all the .conf files automatically:"
1771650,2018-11-15 23:17:57 UTC,I was also able to fix the problem by switching from openvpn-server@.service to openvpn@.service
1771650,2018-07-21 10:37:20 UTC,to fix the problem I had to do this :
1771650,2018-05-29 19:14:16 UTC,"@Fanar does comment #15 solve your case? If yes, I can add a release notes task to this bug and update https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes mentioning this change"
1771650,2018-05-29 18:41:59 UTC,"@ahasenack, thanks, I was indeed wrong with the -client/-server@ units. It's weird they don't show up in ""systemctl -a | grep openvpn"" though. The openvpn.postinst only seem to enable openvpn.service."
1771650,2018-05-29 19:10:49 UTC,"The client/server @ units need a config file, otherwise they cannot be activated. I'm not sure what the main openvpn.service one is for now, though."
1771650,2018-05-29 18:32:41 UTC,"This needs further investigation, because the package does ship service files for server and client:"
1771650,2018-05-29 15:07:39 UTC,The package shipped in Bionic does create the directories /etc/openvpn/server and /etc/openvpn/client but it only ships a systemd unit that looks for configuration files from /etc/openvpn directly.
1771650,2018-05-29 14:43:13 UTC,See this upstream change: https://github.com/OpenVPN/openvpn/commit/28bd79ac980488dbfce2e8136287e38c6f35a043
1771650,2018-05-26 05:53:20 UTC,I can see that there is new file under :
1771650,2018-05-26 05:51:55 UTC,"ok it worked this time, and it is still working even after restarting the service"
1771650,2018-05-25 14:42:30 UTC,"I still can connect if I run openvpn from command line, but init script won't start the service, I tried also making changes to /etc/default/openvpn with no luck."
1771650,2018-05-25 16:20:16 UTC,"systemctl -a | grep openvpn
  openvpn.service
                                  loaded    active   exited
OpenVPN service"
1771650,2018-05-25 14:53:18 UTC,"What do you get from ""systemctl -a | grep openvpn""?"
1771650,2018-05-29 18:38:12 UTC,"Assuming you have a config file called /etc/openvpn/server/myconfig, can you try:"
1771657,2019-06-19 17:21:14 UTC,subscribed ~field-medium
1771657,2019-10-09 07:03:13 UTC,"And interesting part from the pastebin:
20:19:20 DEBUG juju.rpc server.go:329 error closing codec: write tcp 192.168.1.157:46182->3.80.228.179:17070: i/o timeout
ERROR cannot perform restore: <nil>: restore failed: error restoring state from backup: setting special user permission in db: server returned error on SASL authentication step: Authentication failed.
20:19:20 DEBUG cmd supercommand.go:496 error stack:
restore failed: error restoring state from backup: setting special user permission in db: server returned error on SASL authentication step: Authentication failed."
1771657,2019-08-08 02:18:53 UTC,I can reproduce the problem steadily according to the steps - https://paste.ubuntu.com/p/tXpm4nDwsP/
1771657,2019-06-19 18:40:27 UTC,After giving it a second thought subscribing ~field-high as it's a major documented functionality not available
1771657,2019-06-19 17:20:19 UTC,Field is seeing exactly this issue on pre-cloud-handover testing on customer site.
1771657,2018-06-11 17:45:54 UTC,Yes.
1771657,2018-06-11 18:02:51 UTC,Trying to restore with a pre enable-ha backup also failed with the same error. I've included --debug this time:
1771657,2018-06-08 21:51:08 UTC,"@pmatulis, can you reproduce the ""server returned error on SASL authentication step"" errors in an non ha environment?"
1771657,2018-06-08 21:46:16 UTC,"restore in an ha context is no longer allowed per: https://github.com/juju/juju/pull/8783  to restore, remove controller machines until you're in a single controller context, restore the backup and run enable-ha again."
1771657,2018-06-12 20:33:51 UTC,Some of the prior attempts were using a juju version before 2.4-rc1.  I was able to reproduce the SASL cert issue as show here: https://paste.ubuntu.com/p/MdDdxwW549/
1771673,2018-06-08 21:49:47 UTC,"restore in an ha context is no longer allowed per: https://github.com/juju/juju/pull/8783  to restore, remove controller machines until you're in a single controller context, restore the backup and run enable-ha again."
1771682,2018-05-16 21:45:17 UTC,MP here: https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/46
1771683,2019-01-28 12:58:54 UTC,"@Frank: There's more to fix here (in v6 dev cycle), I just fixed the issue in highlight collisions mode."
1771683,2019-01-11 01:56:07 UTC,@Tom is this bug awaiting feedback on the fix or did you just forget to set it ws fix committed?
1771683,2018-12-25 01:31:23 UTC,"@michalstec, I just pushed a patch for the highlight collisions mode snapping, it should be much 'snappier' now. Merry Xmas, Tom."
1771683,2018-12-24 19:21:25 UTC,Not real hug but the magnetic tracks allow to guide a track keeping the clearance distance from another one. New canvas works this way in highlight collision mode but the snapping to clearance worked not as good as in legacy for me (as shown above).
1771683,2018-12-24 16:29:00 UTC,"A stupid question, since when we had anything like hugging traces in the legacy canvas?"
1771683,2018-05-17 20:56:54 UTC,In highlight collisions it works better but still not as good as in legacy. See attachment.
1771683,2018-05-18 09:00:21 UTC,"IMHO, it would be awesome to have a ""Follow"" mode for the router which would allow to draw a track while sticking at the minimum distance of the nearest track and follow it (without having any kind of effect on it)  to allow the quick routing of buses."
1771683,2018-05-16 23:23:49 UTC,"Hmm... do you observe the same behavior when routing in ""Highlight collisions"" mode?"
1771683,2018-05-16 22:27:23 UTC,Depending on the direction the track behaves totally different so I believe it's a bug. With the same settings the track can hug to neighbouring (like in legacy) or go back when exceeding clearance a little (which is annoying). I tried the finest grid. It didn't help.
1771683,2018-05-16 22:13:01 UTC,Michalstec- You can only place a segment end on the grid.  It looks like your cursor is snapping to the nearest grid point.  Drawing a line between grid points does not necessarily fall at the clearance distance between segments.
1771683,2018-08-18 02:07:21 UTC,PNS::HULL_MARGIN has something to do with this. It's value determines how many nm away the track ends up being from where it should.
1771685,2018-07-08 12:41:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771685,2018-07-08 13:52:39 UTC,see bug #1711753
1771689,2018-05-16 22:35:33 UTC,"Here is some more-detailed description of my USB 3.0 adapter:
$ sudo lspci -nn | fgrep -i 'usb 3'
02:00.0 USB controller [0c03]: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller [104c:8241] (rev 02)"
1771690,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1771700,2018-06-07 03:21:20 UTC,"Reviewed:  https://review.openstack.org/571433
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd862fe8ef52719422940e05955ffffb6b073b96
Submitter: Zuul
Branch:    stable/ocata"
1771700,2018-06-08 12:24:49 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1771700,2018-06-11 15:19:06 UTC,This issue was fixed in the openstack/nova 15.1.3 release.
1771700,2018-06-26 17:14:07 UTC,"In Ubuntu queens, this fix is included in the 17.0.5 stable point release via https://bugs.launchpad.net/ubuntu/bionic/+source/aodh/+bug/1778747."
1771700,2018-09-24 14:47:07 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1771700,2018-06-26 19:44:48 UTC,"In Ubuntu ocata, this fix is included in the 15.1.3 stable point release via https://bugs.launchpad.net/cloud-archive/+bug/1778729."
1771700,2018-06-28 12:23:41 UTC,"Reviewed:  https://review.openstack.org/569149
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aa67211acb701f02937f6dfe58899be873c388ed
Submitter: Zuul
Branch:    master"
1771700,2018-10-03 20:08:24 UTC,This is fixed in Ocata and above for Ubuntu. It looks like the upstream tasks can also be moved to fix released.
1771700,2018-06-04 14:27:51 UTC,This issue was fixed in the openstack/nova 16.1.4 release.
1771700,2018-06-26 19:25:17 UTC,"In Ubuntu pike, this fix is included in the 16.1.4 stable point release via https://bugs.launchpad.net/cloud-archive/+bug/1778739."
1771700,2018-06-04 13:52:13 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1771700,2018-05-17 08:30:22 UTC,"Thanks Mel, qemu-img obviously works against block devices, the issue here is that we are using it against a block device as a non-privileged user, something I missed as it's buried deep down in our wonderfully convoluted stack to fetch basic disk details </rant>."
1771700,2018-06-01 02:27:27 UTC,"Reviewed:  https://review.openstack.org/571425
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8ea98c56b647526aae7a786531e934eeee7a90a2
Submitter: Zuul
Branch:    stable/queens"
1771700,2018-05-31 10:17:05 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/571433"
1771700,2018-05-31 09:51:05 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/571427"
1771700,2018-05-31 09:50:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/571425"
1771700,2018-05-31 00:46:13 UTC,"Reviewed:  https://review.openstack.org/569062
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fda48219a378d09a9a363078ba161d7f54e32c0a
Submitter: Zuul
Branch:    master"
1771700,2018-05-18 01:52:59 UTC,Related change to run the nova-lvm job api.compute tests as non-voting on nova/virt/libvirt/* changes is proposed here https://review.openstack.org/569149
1771700,2018-05-17 15:25:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/569149"
1771700,2018-05-17 15:06:45 UTC,We'll have to backport the fix for this to ocata as well:
1771700,2018-05-17 08:58:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569062"
1771700,2018-06-04 05:31:40 UTC,"Reviewed:  https://review.openstack.org/571427
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=43cac615f6a0a4399c7bf3dda6c2595749f27ace
Submitter: Zuul
Branch:    stable/pike"
1771709,2018-05-17 01:46:36 UTC,"If I understand this correctly, the Keystone charm uses 'service_hostname': resolve_address(ADMIN) to set the relation data, which reflects right through to the neutron-gateway charm via the neutron-api charm and the identity relation there."
1771709,2019-05-13 22:00:55 UTC,Agree that this is a useful feature. Added to wishlist for the charm!
1771710,2018-06-20 07:12:11 UTC,any progress?
1771711,2019-09-19 12:05:37 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1771711,2018-09-26 01:12:12 UTC,"yes, HP machine got this error. we can deploy OS with usb or ilo."
1771711,2018-05-17 02:02:56 UTC,and  HP server show this message :
1771711,2018-09-25 22:07:46 UTC,I see that this bug was filed several months ago.  Is this still an issue for you?
1771725,2018-05-17 04:00:57 UTC,The error in your log is:
1771725,2018-05-21 15:41:52 UTC,"During installation  /boot/efi  & grub could not be installed.
I've tried to install grub later but it failed again & again."
1771725,2018-06-01 16:00:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771726,2018-05-23 10:42:23 UTC,"> Here is the correct attachment.
"
1771726,2018-09-09 02:18:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771726,2018-05-29 21:44:40 UTC,"Your link opens to a bug entitled ""ALF footprint drill holes too tight"""
1771726,2018-05-29 19:14:23 UTC,"Hi Dr M,"
1771726,2018-05-23 11:31:22 UTC,"There is a pcb file, in the zip file, that has the errant output."
1771726,2018-05-23 10:46:38 UTC,"More specifically, should the output be"
1771726,2018-05-22 22:54:25 UTC,"Oops, wrong attachment.  Here is the correct attachment.  The pcb file
has the errant element, see line 44."
1771726,2018-07-05 19:31:27 UTC,Hi guys-
1771726,2018-05-22 21:59:01 UTC,"Sure, please see attached.  Chad asked me for this also."
1771726,2018-05-22 21:04:55 UTC,"> 2) The space in the file name breaks gsch2pcb, resulting in corrupted elements in the pcb file.
"
1771726,2018-05-22 02:13:50 UTC,I am using the ALF footprints for the diode.  Those are pretty good.
1771726,2018-05-20 01:28:59 UTC,Thanks Mitch.
1771726,2018-05-17 06:03:05 UTC,Found the source of the problem.   There are three bugs that come together to produce this behavior
1771726,2018-05-17 04:14:37 UTC,"Running it from the command line, here is the error message:"
1771726,2018-05-17 03:59:58 UTC,"Another test, created a new pcb file and manually copied the elements loaded into the .new.pcb file by gsch2pcb, and again the pcb program fails to open the pcb.  The elements are all standard elements from the geda tree."
1771726,2018-05-22 22:28:51 UTC,"> Sure, please see attached.
"
1771737,2018-05-17 12:22:37 UTC,"Please include some info about what exactly is consuming memory on the system.  This could be unrelated to Cinder, it's not possible to tell just from this report."
1771737,2018-05-17 12:33:46 UTC,I could see the cinder-backup using the maximum memory
1771737,2018-05-29 09:12:36 UTC,Attaching memory profile log showing increase in usage of memory while taking 1TB backup.
1771746,2018-05-18 12:52:47 UTC,"how to solve this bug? i tried everything in it, but not finding any
solution"
1771746,2018-06-09 07:13:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771746,2018-05-18 12:31:41 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1771749,2018-05-17 13:11:51 UTC,apport information
1771749,2018-06-10 08:28:05 UTC,What's kernel version do you use in Xenial LTS?
1771749,2018-06-08 18:34:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771749,2018-06-10 17:35:48 UTC,"I don't know which kernel version I did use in Xenial (initially I used the normal one, the kernel installed by default, but then I installed UKUU so couldn't remember, but I never had this problem with previous versions of Kubuntu nor any other flavor of Ubuntu nor in any Linux distro, for the case."
1771749,2018-06-08 18:33:49 UTC,"This bug affects me as well, symptoms are exactly as the original poster writes."
1771749,2018-05-17 13:11:58 UTC,apport information
1771749,2018-05-17 13:11:56 UTC,apport information
1771749,2018-05-17 13:11:53 UTC,apport information
1771749,2018-05-17 13:11:52 UTC,apport information
1771749,2018-05-17 13:11:49 UTC,apport information
1771749,2018-05-17 13:11:37 UTC,apport information
1771749,2018-05-17 13:11:47 UTC,apport information
1771749,2018-05-17 13:11:45 UTC,apport information
1771749,2018-05-17 13:11:44 UTC,apport information
1771749,2018-05-17 13:11:42 UTC,apport information
1771749,2018-05-17 13:11:41 UTC,apport information
1771749,2018-05-17 13:11:39 UTC,apport information
1771749,2018-05-17 13:11:38 UTC,apport information
1771749,2018-05-17 13:11:36 UTC,apport information
1771749,2018-05-17 08:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771749,2018-06-14 03:16:52 UTC,Can you attach dmesg when the ethernet went out?
1771749,2018-05-17 13:11:48 UTC,apport information
1771749,2018-06-15 08:47:49 UTC,"Lately I not longer have noticed to lose the Internet connection; But if I unplug the ethernet cable and plug it again, then the Internet connection is not longer detected and only restarting the PC makes the connection to work again."
1771749,2018-07-13 15:20:38 UTC,"Do you see the issue on latest mainline kernel [0]?
If it still happen to mainline kernel, then find the first bad -rc kernel so we can start a kernel bisection."
1771749,2018-07-15 13:18:46 UTC,"AFAIK it not longer loses the Internet connection itself, but if I unplug the ethernet cable then the network manager becomes red and not any Internet connection is detected anymore when I re-connect the ethernet cable. Only a restart makes the network manager to get the normal color and to detect the Internet connection again."
1771749,2018-08-09 07:23:16 UTC,"Concerning the issue that if I unplug the ethernet cable, the Network Manager icon in the systemtray becomes red color and when I plug it again, it remains red and no connection is detected, I have just confirmed that if I tick the allow automatic negotiation mark in the Wired tab of Edit Connections in Network Manager, then now when pluging the ethernet cable again, the Network Manager icon becomes normal color again, it detects the ethernet connection and it re-connects automatically Ok."
1771749,2018-08-30 09:41:14 UTC,"I not longer lost the ethernet connection, this far."
1771749,2018-09-13 12:12:01 UTC,"XUbuntu 18.04 has been doing this since I upgraded a few days ago. No error messages or any other sign that the Ethernet network connection has been dropped. I first notice it when I try to do something on the network and it times out. I haven't changed any network settings for over a year, but this never happened with Xenial LTS, and I haven't noticed any pattern to the occurrence vs what I happen to be doing at the time, so I can't reproduce it at will."
1771749,2018-11-21 13:35:05 UTC,"I have been affected by this one for a time now on a 18.04 LTS install on a laptop with both wired and wireless ethernet. Not a fresh install, but one that had been upgraded from earlier releases."
1771749,2018-11-22 05:47:44 UTC,Please follow Ubuntu wiki [1] and try mainline kernel.
1771760,2018-05-17 07:54:57 UTC,"My concern is that private: yes could at some point be changed in ansible, breaking our expectations, and we would not see it."
1771763,2018-05-18 01:04:24 UTC,"@Bill, can you help on this?"
1771763,2018-05-18 01:45:53 UTC,"of course, I will try to improve the coverage of validation."
1771764,2019-04-20 17:45:20 UTC,Please see my comment on bug 1771783 -- unsubscribing the Ubuntu Sponsors Team.
1771764,2018-09-07 15:06:01 UTC,"I tested the patch, it works.
Thank you."
1771764,2018-09-02 04:17:27 UTC,[Expired for iproute2 (Ubuntu) because there has been no activity for 60 days.]
1771764,2018-07-03 04:45:48 UTC,Proposed fix for lp #1771764 and lp #1771783
1771764,2018-05-17 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1771764,2018-07-03 08:21:23 UTC,"The attachment ""proposed-fix-1771764-1771783.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1771767,2020-07-20 05:12:15 UTC,"Another thing,"
1771767,2020-08-03 21:55:25 UTC,I can confirm the behavior you described. It's necessary to click submit twice. (And I just submited one for 'code').
1771767,2020-08-03 21:03:18 UTC,I already attached a screenshot when I was trying to submit a dispute for onedrive. But I'm attaching another (the error persists) when I try to submit a dispute for 'code' through this URL: https://dashboard.snapcraft.io/register-snap/?name=code
1771767,2020-08-03 20:01:38 UTC,If I go to https://dashboard.snapcraft.io/register-snap/?name=$SOME_RANDOM_NAME I can register a new name no problem.
1771767,2020-08-03 19:49:20 UTC,"I cannot change the state of the bug for the Snap Store, so will go and discuss with someone that can"
1771767,2020-08-03 19:48:19 UTC,"The registration url is returned by the API:
{
 'code': 'already_registered',
 'detail': 'The snap name ""gnome-calculator"" is already registered.',
 'field': 'snap_name',
 'register_name_url': 'https://dashboard.snapcraft.io/register-snap/?name=gnome-calculator',
 'snap_name': 'gnome-calculator',
 'status': 409,
 'suggested_snap_name': 'sergiusens-gnome-calculator',
 'title': 'The snap name ""gnome-calculator"" is already registered.',
 'type': 'devportal:v1:already_registered'
}"
1771767,2020-07-20 05:03:31 UTC,Hi @tbmb
1771767,2020-08-03 21:45:23 UTC,Can you try this?
1771767,2020-07-16 13:29:37 UTC,This happenened to me today. Look at the picture attached.
1771767,2018-06-06 15:10:13 UTC,"Sergio,"
1771767,2018-06-06 13:51:17 UTC,"What is the difference between `already_claimed` and these: `reserved_name`, `already_owned` and `already_registered`. Is it that you have claimed it or that someone else has? Link to docs would be nice."
1771767,2018-06-05 17:34:20 UTC,The associate MP has landed in staging for tests.
1771767,2018-05-17 08:58:45 UTC,"I updated the description without the dashboard part, I don't why it seemed to work for me yesterday...
So it seems that the problem comes from the API"
1771767,2018-05-17 08:44:15 UTC,I get the expected behaviour you ask for...
1771767,2020-07-17 08:11:28 UTC,hi @felipecassiors
1771768,2020-04-09 17:51:48 UTC,"Caja 1.22.3 (on Debian Buster)
Same problem."
1771768,2019-10-19 23:06:17 UTC,Having this issue on Linux Mint MATE 19.2 - Caja 1.22.1
1771768,2019-04-13 20:06:39 UTC,"Linux Mint Mate 19.1 64 bit, Caja 1.20.2, 76 folders on /media/user/Dane ext4 partition. For me, changing the size of the window works. Then I can change the name of the directory. the change of the size of icons also works (Ctrl ++, Ctrl + -), then I can also change the name of the directory.
List View and Compact View works to."
1771768,2019-03-01 06:42:07 UTC,Same behavior for me. Fairly stock install of Ubuntu Mate 18.04 with all updates installed. Caja v1.20.2.
1771768,2018-11-12 22:27:49 UTC,"Yes, confirmed - if I resize the window so that the scroll bar disappears and all the files are in-frame, I can successfully rename files or folders again in that folder in any View mode."
1771768,2018-06-18 11:21:14 UTC,"I've published a video showcasing the issue (https://youtu.be/cgJ6gJzgZ3A). Sorry, it's not very explicative as I did it quickly with OBS, so here is a bit of context:
- I have Caja opened in a dir which has just enough files to fille its window
- at first, I can rename a file, two lines are ok, can still rename it
- when the name is long enough (3 lines) so that a scrollbar appears, I can no longer rename it: at about 00:23, when I select the file, I'm repeatedly pressing F2 but it has no effect
- if I then resize the window so that the scrollbar disappears, I can rename the file again
- if I resize it again as it was just before, can't rename the file
- *but* if I resize it again to make it smaller (so, there is still a scrollbar), I can rename it"
1771768,2018-11-12 00:39:47 UTC,"Just posting to confirm I am currently having this same bug on a specific folder with Caja 1.20.2 on Linux Mint 19 MAte 64-bit. As mentioned above, renaming works fine in List View and Compact View, but it will not work in Icon View in that specific folder. I can move the file out of that folder, rename it there and move it back, but renaming IN that folder unless in Icon or Compact View does not work."
1771768,2018-10-25 09:45:30 UTC,Issue still present in Ubuntu MATE 18.10. Really annoying.
1771768,2018-05-17 20:13:47 UTC,"I may have find a pattern today while working on files: for some reason, it seems that the impossibility to rename happens when there is a scrollbar displayed (i.e. the list of folders/files doesn't fit in Caja's window). But for sure, it doesn't happen *when* the scrollbar appear, nor if there is already too much content for the window −and thus a scrollbar− when it opens. What I can say it that when I encountered the issue today, resizing the window so that all files were visible (scrollbar disappeared) allowed me to rename them, while resizing it back so that the scrollbar reappeared prevented me to rename the exact same files."
1771768,2018-05-17 14:17:14 UTC,"Yeah, I have seen something like that indeed.
Couldn't reproduce either at the time because of the randomness."
1771768,2018-11-12 06:23:10 UTC,"Just to be sure it's the same bug, can you rename the folder if you resize the window?"
1771773,2020-10-02 20:51:22 UTC,"Change abandoned by Douglas Mendizábal (<email address hidden>) on branch: stable/train
Review: https://review.opendev.org/746798"
1771773,2020-10-02 20:51:15 UTC,"Change abandoned by Douglas Mendizábal (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/746800"
1771773,2020-08-18 21:06:47 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/746798"
1771773,2020-02-24 17:27:46 UTC,"Reviewed:  https://review.opendev.org/679502
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=08bdcdb5b6866c2b6bf084344cca4dd07b960133
Submitter: Zuul
Branch:    master"
1771773,2018-08-13 07:35:53 UTC,"Oh right, I see there's two different ""wrap_socket"" methods, one at the module level (https://docs.python.org/2/library/ssl.html#ssl.wrap_socket) and one one the new SSLContext object (new in 2.7.9 / 3.2.0 https://docs.python.org/2/library/ssl.html#ssl.SSLContext.wrap_socket). Only the latter appears to provide a way to allow use of multiple versions, and because OpenSSL is so awesome, you can't list the protocols you want, rather you have to list the ones you don't want :-("
1771773,2020-08-18 21:16:28 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/746800"
1771773,2018-08-10 08:23:50 UTC,"Sorry, I didn't mean to suggest we should abandon the change/bug, as not all distros have crypto policy support systemwide."
1771773,2018-08-09 19:40:15 UTC,I'm going to close out this bug based on input from Daniel Berrange from the patch review:
1771773,2018-08-09 19:27:42 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: master
Review: https://review.openstack.org/589992
Reason: openssl should already use systemwide settings for the ssl_version underneath, so there is no need in hard-coding a version here. In fact, it would cause systemwide settings not to be honored."
1771773,2018-08-08 18:35:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589992"
1771773,2018-08-08 18:10:18 UTC,"So, it looks like what we need to do here is pass ssl_version=ssl.PROTOCOL_TLSv1_2 [1] to wrap_socket [2] to fix this."
1771773,2018-08-10 19:14:20 UTC,Thanks for the clarification.
1771776,2018-05-20 20:41:08 UTC,This sounds to me like you'd need to use web services to create new institutions.
1771776,2018-05-22 14:34:38 UTC,"Yeah, I'm going to use web services for now. I thought this might be a useful feature for others too."
1771776,2018-05-24 04:38:49 UTC,"You are welcome to propose the web services function for inclusion into Mahara core, either as a patch here, or (preferred esp. if you want to contribute more) directly into our code review system https://reviews.mahara.org See https://wiki.mahara.org/wiki/Developer_Area/Contributing_Code"
1771776,2019-01-30 01:34:53 UTC,If one were to add the ability to create institution on user authorise they would need to take note of:
1771777,2019-08-27 21:43:16 UTC,"Ran into the same issue, failed deployment loop, switched to rescue mode, had to force a shutdown on the host and check power to get it out of rescue mode. This is on MAAS 2.6.0."
1771777,2020-09-11 14:54:39 UTC,"machine was still reachable on ssh so I managed to issue ""poweroff"" command and that caused server to detect error with power controlling the server and allowed me to mark broken, then mark fixed and it was finally in ready state."
1771777,2020-09-11 14:49:12 UTC,Same issue here with maas 2.8.2
1771777,2020-07-06 15:47:00 UTC,still happens with MAAS 2.8 installed from snap
1771777,2020-02-01 14:42:07 UTC,Can confirm this is still happening with 2.6.2 (7841-ga10625be3-0ubuntu1~18.04.1)
1771777,2019-05-07 06:21:48 UTC,I had this happen on MAAS 2.3.5 where I also entered rescue mode from failed deployment.
1771777,2019-02-11 21:59:02 UTC,"Hi Pedro,"
1771777,2019-04-25 15:37:13 UTC,"I might have hit this issue. After a failed deployment entered rescue mode, then attempted to exit; it's hanging at ""Exiting Rescue Mode"" for some time now. This is on Maas 2.3.5-6511-gf466fdb-0ubuntu1 / xenial however."
1771777,2019-02-14 12:32:52 UTC,"Hi Andres, no I didn't try that yet. I do use ""Test Hardware"" option and that resets machine's state to ""Ready"", from ""Rescue Mode"", not ""Exiting Rescue Mode""."
1771777,2019-02-07 07:04:28 UTC,"Hi, I am also affected by this bug. I was planning to just change the status of the machine on Postgres from EXITING (status 19) to READY (status 4). Comparing with an already ""Ready"" machine, I could see that the SQL would look like:"
1771777,2019-04-25 16:04:09 UTC,PS: the failing node is system_id=ka67eg
1771777,2018-08-13 19:38:55 UTC,"I've been able to reproduce the same issue, although i have not had any error logs. This may be a backend issue that we are not tracking correctly."
1771779,2018-05-17 09:28:32 UTC,"StacktraceTop:
 g_dbus_proxy_new (connection=0x56053b0100f8, flags=flags@entry=G_DBUS_PROXY_FLAGS_NONE, info=info@entry=0x0, name=name@entry=0x56053bacb90d ""org.gnome.SettingsDaemon"", object_path=object_path@entry=0x56053bacb9c8 ""/org/gnome/SettingsDaemon/MediaKeys"", interface_name=interface_name@entry=0x56053bacb9a0 ""org.gnome.SettingsDaemon.MediaKeys"", cancellable=0x0, callback=0x56053bac4fa0 <compat_proxy_ready_handler>, user_data=0x56053c607b00) at ../../../../gio/gdbusproxy.c:2027
 session_ready_handler (source_object=<optimized out>, res=<optimized out>, data=0x56053c607b00) at media_keys/gmpv_media_keys.c:292
 g_task_return_now (task=0x56053c3ff1f0) at ../../../../gio/gtask.c:1148
 g_task_return (task=0x56053c3ff1f0, type=<optimized out>) at ../../../../gio/gtask.c:1206
 bus_get_async_initable_cb (source_object=0x56053beca030, res=<optimized out>, user_data=0x56053c3ff1f0) at ../../../../gio/gdbusconnection.c:7323"
1771781,2018-05-23 11:57:30 UTC,"hi, yes i can reproduce the bug with"
1771781,2018-05-25 02:42:15 UTC,"yeah,i think these problems should be paid attention to.
1.tenant_id of port whether same as the associated network's
2. tenant_id of listener with the associated loadbalancer's
and so on..."
1771781,2018-05-31 05:15:21 UTC,"yes so what should be the good approach to handle this, Like in nova they are verify the same using keystone[1]"
1771781,2018-06-01 12:08:53 UTC,IMO this way how nova is handling that is good and we can do something similar in Neutron
1771781,2018-06-11 19:28:35 UTC,Here is the nova spec explaining how it works:
1771783,2018-06-27 00:21:52 UTC,"The attachment ""proposed-patch-1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1771783,2018-07-03 04:46:33 UTC,Proposed fix for lp #1771764 and lp #1771783
1771783,2018-10-03 14:23:16 UTC,It works on my side:
1771783,2019-04-20 17:43:25 UTC,Hello! Thank you for your contribution to Ubuntu.
1771788,2018-05-18 01:48:31 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/6ace5440188a888826e846487cc6dfbf042faa9d"
1771788,2018-05-18 01:47:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771788,2018-05-17 10:25:23 UTC,"StacktraceTop:
 DeepCopyFeedbackClasses (to=0x5617a4b12e10, from=0x5617a4ae7b40) at ../../../../Xi/exevents.c:271
 DeepCopyDeviceClasses (from=0x5617a4ae7b40, to=to@entry=0x5617a4b12e10, dce=dce@entry=0x7ffca2d2fbe0) at ../../../../Xi/exevents.c:667
 ChangeMasterDeviceClasses (device=0x5617a4b12e10, dce=0x7ffca2d2fbe0) at ../../../../Xi/exevents.c:727
 UpdateDeviceState (device=0x5617a4b12e10, event=0x7ffca2d2fbe0) at ../../../../Xi/exevents.c:807
 ProcessDeviceEvent (ev=ev@entry=0x7ffca2d2fbe0, device=device@entry=0x5617a4b12e10) at ../../../../Xi/exevents.c:1709"
1771789,2018-05-17 13:32:18 UTC,"Are you sure that ""juju update-clouds"" doesn't also check if the cloud
information on the server is up to date? It may not, but it might."
1771789,2018-06-04 14:44:10 UTC,The issue is that the controller end doesn't get updated. Doesn't update-clouds just work on the client? The issue the JAAS team has is that as the controllers are long running they don't get new cloud region information as part of upgrades and so the cached list of available regions the controller can speak isn't updated in any easy to reach mechanism.
1771789,2019-03-22 04:10:45 UTC,From 2.5.2 you can use the 'juju update-cloud --controller <controller>' command. This updates the cloud information on the controller.
1771789,2019-03-22 04:42:17 UTC,"I misspoke, part of this is fixed but there is still some work left so that changes are realised. Sorry for the noise."
1771789,2019-04-23 21:53:05 UTC,"Added support for maas, openstack, lxd to notice update-cloud has been run and react accordingly.
Other clouds todo"
1771792,2018-07-10 12:41:29 UTC,We have discussed a possibility of having a --force option on 'destroy-model' command.
1771792,2019-05-07 01:27:02 UTC,"From Juju 2.6, 'destroy-model' gains a 'force' option as well as 'no-wait' option."
1771796,2018-05-17 11:32:33 UTC,The two stages are explicitly specified here: https://wiki.ubuntu.com/Mirrors/Scripts
1771806,2018-05-23 00:21:25 UTC,This sounds related: https://review.openstack.org/#/c/508555/ - but that was in Queens which CERN should have already so why doesn't that resolve the problem?
1771806,2018-05-31 15:34:45 UTC,Could be related to bug 1750450 as well.
1771806,2018-05-31 16:10:29 UTC,"Here is a detailed step through the RT code which eventually creates the compute node record, and highlights why I'm not sure why the change in comment 1 doesn't already handle this issue."
1771806,2018-05-31 17:35:45 UTC,We don't hit this condition: https://github.com/openstack/nova/blob/8ab386ed9b6e48343910e08a15ba18325c09f3b6/nova/compute/resource_tracker.py#L531 and we have https://review.openstack.org/#/c/508555/ already. Not sure why the record is recreated instead of being updated.
1771806,2018-05-31 17:35:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/571535"
1771806,2018-06-29 18:10:08 UTC,"Reviewed:  https://review.openstack.org/571535
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9f28727eb75e05e07bad51b6eecce667d09dfb65
Submitter: Zuul
Branch:    master"
1771807,2018-05-18 04:36:28 UTC,"Review in progress for https://review.opencontrail.org/43150
Submitter: Parth Sarupria (<email address hidden>)"
1771807,2018-05-18 08:12:22 UTC,"Review in progress for https://review.opencontrail.org/43158
Submitter: Parth Sarupria (<email address hidden>)"
1771807,2018-05-22 16:56:03 UTC,"Reviewed:  https://review.opencontrail.org/43158
Committed: http://github.com/Juniper/contrail-controller/commit/e780eb4d3c5dad32856fb4173188d926a3f55b05
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1771808,2019-12-16 04:17:17 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1771808,2019-12-16 04:17:15 UTC,[Expired for snapd because there has been no activity for 60 days.]
1771808,2019-10-16 06:06:14 UTC,"This looks like the dpkg database got corrupted, could you please try:
sudo dpkg --purge snapd
and see if that helps?"
1771810,2018-05-21 04:55:48 UTC,This seems like either something that should be a part of https://blueprints.launchpad.net/nova/+spec/handling-down-cell or https://blueprints.launchpad.net/nova/+spec/count-quota-usage-from-placement.
1771810,2018-10-12 16:30:21 UTC,Agreed that this enhancement will be either part of handling a down cell or moving to count quota usage from placement.
1771810,2018-11-01 16:23:15 UTC,Looks like Surya has started something for this here:
1771810,2018-11-13 17:56:04 UTC,"Reviewed:  https://review.openstack.org/569055
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=77881659251bdff52163ba1572e13a105eadaf7f
Submitter: Zuul
Branch:    master"
1771810,2019-03-22 03:46:04 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1771811,2018-05-17 12:51:53 UTC,The quick workaround is to remove the symlink in /sbin.
1771825,2018-09-02 00:44:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771833,2019-11-11 20:39:29 UTC,"I think, at least in my case, this bug is not limited to the ""Süddeutsche Zeitung"", therefore I mentioned ""heise online"" as an example to demonstrate that it also does not depend on a login. I tried also ""Zeit online"", same thing."
1771833,2019-11-14 10:29:50 UTC,I confirm that in my case when using the installation from the calibre-website the issue is not there. Downloading of news-sources works as expected.
1771833,2019-11-13 08:39:51 UTC,"Dont use flatpaks, they are totally unsupported."
1771833,2019-11-13 08:24:19 UTC,"Perhaps I should mention that in my laptop, where this bug is showing up, calibre is installed as flatpak. On my desktop, where everything runs smoothly, it is a ""normal"" installation with the command from the calibre website."
1771833,2019-11-12 00:59:15 UTC,that's the cover download failing it wont affect overall download.
1771833,2019-11-11 14:50:13 UTC,"With what credential do you test ""Süddeutsche Zeitung«?"
1771833,2019-11-11 12:46:41 UTC,With what credential do you test?
1771833,2019-11-11 12:57:20 UTC,heise does not need credentials
1771833,2019-11-11 11:43:29 UTC,"What about heise? It is about ""Süddeutsche Zeitung«
I hat given my credential at the time I posted the bug."
1771833,2019-11-11 09:45:26 UTC,"Heise has nothing to do with this, the log you posted for it is incomplete. As for the original recipe the darko asked for login credentials for it, but no one responded."
1771833,2019-11-11 09:23:55 UTC,"Hi all,"
1771833,2019-10-28 12:36:49 UTC,"Apparently this is not limited to paid content. On my setup here, Ubuntu 19.10 with Calibre 4.2, I cannot download news. Not from Süddeutsche nor from Heise."
1771833,2018-06-03 13:36:18 UTC,To test this I would need valid access credentials. If you want this fixed contact me directly on my personal email <email address hidden>
1771833,2018-05-17 15:17:02 UTC,Changing the component for this bug.
1771833,2019-11-11 12:01:04 UTC,I just tried heise it works fine.
1771834,2020-10-12 17:23:31 UTC,"ideally, you should be able to run any gui/desktop Ubuntu variation with only systemd-networkd, without any NetworkManager, connman or, God forbid, netplan.
I use excellent ArchLnux wiki pages for my inspiration, like https://wiki.archlinux.org/index.php/Systemd-networkd
As well as its documentation on freedesktop.org wiki"
1771834,2020-10-12 17:15:38 UTC,"you may very easily migrate away off netplan and forget it forever.
that's for default ""renderer"" value which is ""networkd"".
for NetworkManager you usually don't need netplan at all, initially.
remove it, and NetworkManager would not ever notice that nor complain about something missing.
that should go for end-user Ubuntu versions like Lubuntu, Xubuntu and GNOME3 Ubuntu itself.
in networkd case, just copy netplan-generated files from /run/systemd/network/ into /etc/systemd/network/ , do a ""systemctl enable systemd-networkd"" , remove everything resembling netplan from your dpkg paackage list, and restart your system. keep your local console connected to the system for the first 1 or 2 system restarts, as you might need to adjust your .network/.netdev config file names priority.
after next 2..3 successful reboots, no thought about installing netplan should visit your head ever."
1771834,2020-04-29 07:41:03 UTC,"According to https://netplan.io/examples, netplan supports route-metric keyword and I use it:"
1771834,2020-04-29 07:13:58 UTC,"I scratch my head over and over again. This netplan is half-baked solution, lots of missing feature from ifupdown. The bugs has been 2 years, yet not fixed."
1771834,2018-05-18 07:49:29 UTC,"yes, it is how it worked before on ifupdown"
1771834,2018-05-17 18:35:00 UTC,"Yes, I believe we want to allow users to specify the RouteMetric value.
Netplan auto generates this value, but keeps it the same for any interface, except wifi which is set higher."
1771834,2018-07-23 08:06:06 UTC,I have opened https://github.com/CanonicalLtd/netplan/pull/39 to support a 'metric' key as described by Ryan.
1771836,2019-05-20 20:12:07 UTC,"Thank you for your bug report, that looks like it already got reported as bug #1728681. Do you know how that line went missing?"
1771836,2018-10-26 13:57:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771836,2019-05-20 15:03:17 UTC,Missing data_path is causing this.
1771836,2019-05-21 08:31:48 UTC,Can you confirm if data_path is a new parameter or was it present in default config in all previous versions of landscape-client ?
1771841,2018-08-31 07:40:45 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/569458
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1771841,2018-06-22 11:15:00 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/577396"
1771841,2018-06-19 20:43:25 UTC,"Reviewed:  https://review.openstack.org/572055
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ba9fd196a255170ae48149447a99e3d872d49976
Submitter: Zuul
Branch:    stable/pike"
1771841,2018-07-16 10:59:35 UTC,"Reviewed:  https://review.openstack.org/577396
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5e47f30572b7b9224a6ac6df59f0f1b6794c935f
Submitter: Zuul
Branch:    stable/ocata"
1771841,2018-06-03 19:10:49 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/571984"
1771841,2018-06-04 08:54:26 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/572055"
1771841,2018-06-07 22:43:17 UTC,"Reviewed:  https://review.openstack.org/571984
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2ed6e4d7ab253f23fd81d84b127139b9deb438fd
Submitter: Zuul
Branch:    stable/queens"
1771841,2018-05-17 22:43:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/569289"
1771841,2018-05-18 14:19:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/569424"
1771841,2018-05-22 16:43:18 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/569424"
1771841,2018-05-18 20:18:05 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/569289"
1771841,2018-06-03 14:32:05 UTC,"Reviewed:  https://review.openstack.org/569083
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3e9e2a5b4b2654864bb0e2a7d9b841eb03240147
Submitter: Zuul
Branch:    master"
1771858,2019-06-26 07:32:19 UTC,Verified 237-3ubuntu10.24 on Bionic:
1771858,2019-06-26 07:51:47 UTC,The autopkgtest failures seem to be unrelated. I re-triggered flaky tests and I'm updating the hints where needed.
1771858,2019-06-26 08:00:17 UTC,"We have codepaths with and without initrd, which results in different environment that systemd starts up with."
1771858,2019-06-26 08:08:27 UTC,"In effect, I'm saying that we need to (a) fix systemd as per this bug report (b) fix initramfs-tools (c) only then enable snapd env generator"
1771858,2019-06-26 08:12:19 UTC,"The snapd and systemd fixes triggered LP: #1814355 together and I'm now investigating if the initiramfs fix for that 'regression' should be backported to Bionic, too. In that case I'll add a new Breaks: to the systemd upload."
1771858,2019-06-26 08:14:52 UTC,@xnox we were investigating this in parallel :-)
1771858,2019-06-26 08:19:09 UTC,The added Breaks: will ensure that the fixes are applied together.
1771858,2019-06-26 08:54:28 UTC,"When we disabled the generator in snapd we added a regression test (tests/main/snap-system-env):
https://github.com/snapcore/snapd/pull/6470/files"
1771858,2019-06-26 08:55:51 UTC,The PR to re-enable the generator: https://github.com/snapcore/snapd/pull/7031 and updates the test.
1771858,2019-06-27 15:34:54 UTC,"Hello Dan, or anyone else affected,"
1771858,2019-06-26 21:38:54 UTC,"@mvo @xnox ok, so if I run unfixed systemd and fixed snapd and unfixed initramfs-tools /usr/local/... patch are missing when booting with initramfs:"
1771858,2019-06-26 01:21:24 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.24) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1771858,2019-06-28 11:53:18 UTC,"re: autopkgtests, a few failed, but I re-ran them and they passed on the re-run."
1771858,2019-07-02 14:23:11 UTC,Tested 229-4ubuntu21.22 on Xenial:
1771858,2019-07-04 09:18:32 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.24
1771858,2019-07-04 09:18:43 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1771858,2019-07-04 09:20:16 UTC,This bug was fixed in the package systemd - 229-4ubuntu21.22
1771858,2019-11-18 18:26:27 UTC,"Installed snapd from proposed, rebooted, and /snap/bin is now in path of systemd-run unit"
1771858,2020-11-10 19:29:51 UTC,This has NOT been fixed in Bionic.  or it came back.  My cron script that uses a program in /snap/bin can not be found I have to create a sym link to /usr/bin
1771858,2019-06-26 21:31:25 UTC,"@mvo thanks for the test! Nor @xnox or I could reproduce the problem of missing /usr/local/bin and /usr/local/sbin when booting with initramfs.
I tried even downgrading snapd to 2.37.1+18.04 and systemd to 237-3ubuntu10.10 with no luck.
I seems it is safe to go ahead with the snapd fix, too."
1771858,2019-06-25 23:47:40 UTC,"Hello Dan, or anyone else affected,"
1771858,2019-06-27 17:37:28 UTC,"All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1771858,2019-06-25 10:30:52 UTC,"@mvo /usr/lib/systemd/system-environment-generators/snapd-env-generator is working in Bosmic and up, but in Bionic it is not executable.
Could this please be fixed?"
1771858,2018-05-18 15:57:42 UTC,/etc/profile.d is for the login shells.
1771858,2018-05-18 15:10:18 UTC,"i meant to say above is that it would be nice to find a way that covers all use-cases with one code path (sorry, just noticed what i wrote wasnt clear in that regard)"
1771858,2018-05-18 16:08:29 UTC,re:single code path
1771858,2018-05-18 18:01:19 UTC,"well, my subtle hint would point to simply add it to /etc/environment here, which would globally cover for everything, would allow us to drop the profile.d snippet in ubuntu images/installs and to my knowledge would even be used by systemd (or am i wrong here ?) ..."
1771858,2018-05-18 19:29:19 UTC,"On 18 May 2018 at 19:01, Oliver Grawert <email address hidden> wrote:

> well, my subtle hint would point to simply add it to /etc/environment
> here, which would globally cover for everything, would allow us to drop
> the profile.d snippet in ubuntu images/installs and to my knowledge
> would even be used by systemd (or am i wrong here ?) ...
>
> (and i think it would even work for zsh)
>
"
1771858,2018-05-19 01:21:56 UTC,"On Fri, May 18, 2018 at 06:01:19PM -0000, Oliver Grawert wrote:

> well, my subtle hint would point to simply add it to /etc/environment
> here, which would globally cover for everything, would allow us to drop
"
1771858,2018-05-29 16:07:11 UTC,https://github.com/snapcore/snapd/pull/5226 <- contians a PR for this now.
1771858,2018-05-30 13:23:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771858,2018-05-30 13:24:22 UTC,"I'll mention this here because I believe it's related, if not please correct me and I'll file a separate bug.  When cron jobs are run /snap/bin is not in the path."
1771858,2018-06-18 13:10:33 UTC,"A related issue is that ""ssh <host-with-snaps> <snap-command>"" currently fails because /snap/bin isn't in PATH. In that case, sshd sets PATH via pam_env. I'm not sure if a systemd environment generator will help with this use case or not."
1771858,2018-06-18 13:15:31 UTC,I filed bug 1777445 for the non-interactive ssh case.
1771858,2018-05-18 14:43:35 UTC,snapd ships a snippet in /etc/profile.d that sets the PATH to /snap/bin and should theoretically work for all login shells (except for zsh which doesn't respect the profile.d standard) ... bug 1640514 and bug 1659719 are related.
1771858,2018-08-30 10:23:17 UTC,This is being worked on in https://github.com/snapcore/snapd/pull/5736
1771858,2018-09-26 09:58:27 UTC,Using this bug to fix systemd exported environment to the generators.
1771858,2018-09-29 23:18:44 UTC,This bug was fixed in the package systemd - 239-7ubuntu9
1771858,2018-11-19 14:03:17 UTC,"Hello Dan, or anyone else affected,"
1771858,2018-11-20 12:05:27 UTC,"Hello Dan, or anyone else affected,"
1771858,2018-12-04 12:19:37 UTC,"Using systemd 237-3ubuntu10.10, executing the test case i see /snap/bin in path"
1771858,2019-02-01 20:56:25 UTC,Just noticed what might be a regression from this fix. `/usr/local/sbin:/usr/local/bin` are now missing from unit on newest ubuntu bionic ami (us-east-1: ami-012fd5eb46f56731f)
1771858,2019-02-02 10:37:05 UTC,@jweede
1771858,2019-02-02 15:21:07 UTC,@xnox
1771858,2019-02-18 15:54:51 UTC,"FYI, this bug is marked Fix Committed against systemd for bionic, but there is currently nothing in bionic-proposed."
1771858,2018-08-28 16:19:01 UTC,still not fixed in snapd.
1771858,2019-06-25 14:17:50 UTC,@jweede I uploaded the SRU fix again for Bionic and tried to reproduce the regression you observed but it works for me:
1771860,2019-04-17 20:30:07 UTC,"Reviewed:  https://review.openstack.org/647623
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ee07c1c67d4ee6b146783c40826c4a28bd7367c3
Submitter: Zuul
Branch:    stable/queens"
1771860,2019-07-10 21:40:31 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1771860,2019-04-26 17:15:49 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1771860,2019-04-22 05:25:19 UTC,"Reviewed:  https://review.opendev.org/647630
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6832b0e070cebbe48a71a46d88b9412375989c1
Submitter: Zuul
Branch:    stable/pike"
1771860,2019-03-25 22:58:32 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/647630"
1771860,2019-03-24 23:39:03 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1771860,2019-03-22 03:44:58 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1771860,2019-03-15 18:26:17 UTC,"Reviewed:  https://review.openstack.org/643173
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=133763d3582c2e85e4e5962b542294135d1a7f4c
Submitter: Zuul
Branch:    stable/rocky"
1771860,2019-03-13 23:25:48 UTC,"Reviewed:  https://review.openstack.org/567701
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0ed68c76fa8a84d1d5f0ab945e34c8e16341d627
Submitter: Zuul
Branch:    master"
1771860,2019-03-13 22:17:46 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/643173"
1771860,2019-03-25 21:59:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/647623"
1771875,2018-05-17 19:11:26 UTC,Noting that this was observed in both Firefox and Chrome in the embedded Dojo interface; it may be simpler to Angularize this interface rather than debug the Dojo.
1771875,2020-04-06 20:37:50 UTC,Noting that bug 1855781 proposes said Angular port of this interface; once that code is merged this issue should be re-tested to see if it persists.
1771875,2020-08-06 18:12:47 UTC,Noting that this bug can also affect policies that are edited on 3.3.4 for PaILS. We have been making changes and finding that this field if in use will blank out when another field is edited.
1771880,2019-07-10 14:00:37 UTC,"You can ignore that upstream bug triager comment, Andre tends to dismiss reports based on first reporting version without checking if that's still an issue which is often the wrong thing to do, https://gitlab.gnome.org/GNOME/seahorse/issues/205 has a one week old comment stating that it's still a problem in 3.32 which is their current and supported version."
1771880,2019-07-10 13:34:28 UTC,"Well, after filling the report on GitLab, as suggested in comment #15, I receive the following statement from there:"
1771880,2019-05-13 04:08:33 UTC,It's been over a year.. Is anyone going to fix this? Like pls
1771880,2019-07-04 22:49:36 UTC,"The problem is still here and for instance it prevents LibreOffice Draw to check PDFs signatures. I think marking this as ""wishlist"" is terribly wrong, it is a major bug as there is no workaround to import certificates in LibreOffice."
1771880,2019-06-17 01:22:32 UTC,"Regarding #17 and the bug (issue) report at Seahorse Gitlab, the latest comment is that Seahorse 3.20.0 which is the latest available on Ubuntu 18.04, is ""an ancient version"". Can 18.04 receive a newer version such that upstream can be brought into the issue if it persists with that?"
1771880,2019-11-04 00:57:46 UTC,"Off-topic for Seahorse, but the reporter's (and my) real problem is about signing in LibreOffice.
I've found a way to sign document in LibreOffice on Ubuntu:"
1771880,2019-07-09 22:00:59 UTC,"As suggested in post #15, I just filled a bug report on GitLab:  <https://gitlab.gnome.org/GNOME/seahorse/issues/232>, however, as I have my doubts if it is really an upstream bug, as it didn't occur on Ubuntu 16.04, just on Ubuntu 18.04, and some users reported that in Debian it works."
1771880,2019-05-10 00:30:17 UTC,"So, I also have the same problem using Ubuntu 19.04, is there any workaround to import p12 certificates?"
1771880,2020-07-30 05:45:45 UTC,As the problem is still not solved in seahorse 3.36
1771880,2020-04-05 09:17:45 UTC,"Fascinating, I am seeing this exact same issue with SSH keys. When using ssh-add these keys will load into the agent without a problem, but I cannot import them into Seahorse. The files have been generated with OpenSSH, but their file names aren't following the standard id_<algo> and id_<algo>.pub pattern ..."
1771880,2020-04-05 09:25:46 UTC,"The keys I was trying to import into Seahorse were located in an encrypted container (mounted, obviously). As I cannot influence (or haven't learned how to influence) the standard file modes when mounting said container, they all had 0700 as file mode, including the .pub files I had generated based on that AskUbuntu answer."
1771880,2020-05-25 16:44:06 UTC,"Not seahorse but the same problem described in #33, my Mint 19.3 was not being able to sign with Libreoffice 6.0.7.3 (nor other apps like AutoFirma)  It was solved by:
- downgrading to openjdk 1.8  (sudo apt install openjdk-8-jre; sudo update-java-alternatives -s  java-1.8.0-openjdk-amd64 )
- leaving just one profile for thunderbird with name default
- upgrading to  LibreOffice 6.4.2"
1771880,2020-07-31 11:16:14 UTC,This is really amazing. I still have the same problem.
1771880,2020-07-31 12:12:17 UTC,"To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. Venting frustration in a bug report isn't fine."
1771880,2020-07-31 13:52:31 UTC,Still unable to import .p12 and .cer certificates on Ubuntu 20.04.1 LTS / GNOME 3.36.3 / Seahorse 3.36.
1771880,2021-01-28 22:26:23 UTC,Still unable to import openssh-formatted RSA PRIVATE KEYs on Ubuntu 20.04.1 LTS / Gnome 3.36.8 / Seahorse 3.36-1
1771880,2021-01-28 22:41:56 UTC,"(Sorry for #43, wrong bug/thread - but yes, the same goes for .p12 at the versions stated.)"
1771880,2020-01-16 07:36:21 UTC,I compiled 3.30.1.1 and yet: The same error message—“No compatible importer found”
1771880,2019-04-11 15:28:25 UTC,"As I've explained in the Bug Description, before filling this bug, I'd tested the same process in my wife's laptop then with 'Ubuntu 16.04 LTS' and it imported the certificates ('.cer' and '.p12') without issues. But in my laptop with 'Ubuntu 18.04 LTS' the problem exist (greyed button)."
1771880,2019-11-04 23:22:40 UTC,Nothing yet? Jesus!
1771880,2019-02-26 19:00:09 UTC,"I have installed VirtualBox on my Mac laptop, and built Ubuntu 19.04 guest VM - but had issues with everything that requires HTTP/HTTPS access. Eventually, I came across this post - which matches the issue I have and explains why that's so..."
1771880,2018-05-19 18:31:35 UTC,"I'm getting the same grayed out Import button with the ""Cannot import..."" hint. My key was exported from seahorse 3.20.0-3.1 on Ubuntu 17.10."
1771880,2018-05-23 07:46:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771880,2018-05-29 10:21:26 UTC,I also see the greyed out Import button using Seahorse 3.20.0-5 on Ubuntu MATE 18.04 LTS.
1771880,2018-05-30 06:23:49 UTC,"Affects email signing, encryption through Thunderbird and signing of documents through LibreOffice. Had to show a demo to my boss on how Ubuntu + G Suite could be used for field users and got an unpleasant surprise."
1771880,2018-06-18 13:36:13 UTC,"Can confirm the problem. I really appreciate a fix, as email encryption by s/MIME does not work in evolution since I cannot import certificates."
1771880,2018-06-22 09:29:23 UTC,"I can't find a workaround and it is crucial that I have a new certificates, because we use them to authenticate ourselves and send emails in our company."
1771880,2018-07-09 17:32:32 UTC,This bug is affecting my job. I am not able to encrypt or sign my e-mails.
1771880,2018-07-18 08:24:08 UTC,I'm facing the same bug on Linux Mint 19 Cinnamon.
1771880,2018-07-24 04:10:52 UTC,I have the same issue in 18.04.
1771880,2018-08-08 11:21:52 UTC,Does anyone know a workaround for this issue please? It is also affecting my job. Thanks.
1771880,2018-08-17 06:45:45 UTC,I'll join the choir here:
1771880,2018-08-28 15:49:47 UTC,Seahorse does not support .p12 certificates. It supports GPG and SSH certificates.
1771880,2018-10-24 20:41:15 UTC,Also tested it with .pem not working either
1771880,2018-11-14 09:04:32 UTC,See: https://gitlab.gnome.org/GNOME/seahorse/issues/205
1771880,2018-11-14 09:07:41 UTC,"See also:
https://askubuntu.com/questions/1037524/how-can-import-private-key-and-certificate-to-seahorse-in-ubuntu-18-04"
1771880,2018-11-16 13:31:54 UTC,For what I have tested this bug affects also Network Manager - can't set certificates for WPA(2) Enterprise and/or 802.1X.
1771880,2019-01-09 15:51:59 UTC,So is there a fix available or in its way?
1771880,2019-01-25 11:50:11 UTC,"> Seahorse does not support .p12 certificates. It supports GPG and SSH certificates.
I believe this statement and the categorization of the issue as ""wishlist"" to be incorrect.
"
1771880,2019-02-19 14:24:28 UTC,"Same here, cannot import and sign LibreOffice Documents (as I did since last week with 16.04) . Any news on that?"
1771880,2018-05-18 18:19:45 UTC,When trying to import the certificate via command line I get the following output:
1771880,2019-04-11 12:27:38 UTC,"I have the same problem, with xubuntu 18.04.2, @samweis say that is a problem in ubuntu, seahorse can import p12 keys well in debian"
1771882,2018-06-11 11:33:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/574224"
1771882,2018-07-30 15:53:56 UTC,This issue was fixed in the openstack/zun 2.0.0 release.
1771885,2018-05-19 20:37:10 UTC,"""When MAAS deploys a node it will configure its resolver accordingly; in the case where the above settings are made and you are deploying Linux:"
1771885,2018-05-18 04:17:07 UTC,"I know Bionic changed how we find the nameserver, is the issue that we aren't looking in the new place for the search domain or is it that the information isn't there?"
1771885,2018-07-12 22:04:03 UTC,I've proposed a change in MAAS that will replicate the DNS search path configuration on a per-interface basis in the v1 network preseed YAML passed to cloud-init (if there is a DNS server on the interface; i.e. defined on the subnet in MAAS). Hopefully that will smooth things over for those who encounter this in the future.
1771885,2018-07-12 20:20:09 UTC,"I'm re-opening this task for MAAS, as a user has been able to reproduce this issue in a different context. While there's a work-around on comment #22, the situation is that even when the same network configuration sent for xenial and bionic deployments is the same, the configuration differs, due to how cloud-init handles netplan configuration."
1771885,2018-06-13 20:31:19 UTC,I can confirm both that this bug exists and that the referenced workaround deals with the issue.
1771885,2018-06-06 00:29:07 UTC,Given the workaround available for maas & cloud-init this is working as expected.  Thanks for the debugging everyone.
1771885,2018-06-05 23:28:11 UTC,Removing the DNS settings from the subnet in MAAS resolves the problem. Bionic then receives the correct search domain.
1771885,2018-05-31 17:19:24 UTC,@Andres
1771885,2018-05-31 17:06:18 UTC,"@David, could you please attach the output of 'maas <user> machine get-curtin-config <system-id>'"
1771885,2018-05-31 14:55:44 UTC,"Just to be 100% clear. We do get the nameserver setting, (see the attached logs) and resolution for FQDNs works. We do not get the search domain and therefore hostname only resolution does not work."
1771885,2018-05-31 14:53:44 UTC,"@Andres,"
1771885,2018-05-17 20:23:43 UTC,A interesting twist on this is that juju seems to do the right thing when host system is xenial and container is bionic (See below).
1771885,2018-05-30 22:50:38 UTC,"Hi David,"
1771885,2018-05-30 22:26:33 UTC,Xenial-maas info
1771885,2018-05-30 22:25:58 UTC,Discussion with roaksoax about this and it seems likely this is a cloud-int / netplan problem. I have added cloud-init and maas just to be thorough.
1771885,2018-05-25 09:29:41 UTC,"If at all helpful, it should be known that the patches above only apply to newly deployed containers. The patches above do not repair or correct existing containers."
1771885,2018-05-25 07:38:18 UTC,"It sounds like we are failing to find the search domain and add it to the
configuration."
1771885,2018-05-24 16:34:10 UTC,So here is the information that hopefully will be useful.
1771885,2018-05-24 14:50:45 UTC,"Sure, I'll run up the system and leave it running; it'll be on ruxton dells;  I'll report back here when it is up."
1771885,2018-05-24 13:33:40 UTC,"@Alex, can you check that ""host foo"" still doesn't resolve? It may be that we don't need the search path in /etc/resolve.conf because of the new systemd-resolved changes. Our testing showed that 'host nuc-1' from inside the container did indeed resolve."
1771885,2018-05-23 19:06:41 UTC,Can you include the output of /etc/netplan/*.yaml ?
1771885,2018-05-23 15:15:09 UTC,"Sadly, I've still got this bug; just tested with 2.4-beta3+develop-e33ec12  (which may not be yet include this??)"
1771885,2018-05-22 15:30:01 UTC,https://github.com/juju/juju/pull/8741
1771885,2018-05-20 20:40:29 UTC,https://github.com/juju/juju/pull/8731
1771885,2018-05-20 16:19:37 UTC,https://github.com/juju/gomaasapi/pull/74/files
1771885,2018-05-30 22:26:53 UTC,bionic DHCP
1771886,2021-02-24 00:44:00 UTC,"Well this is an annoying bug, makes netplan useless for the biggest IPv6 ISP in the country."
1771886,2020-11-08 02:34:03 UTC,"I have this problem too, netplan has so many ancient bugs that are still open, I don't know why ubuntu integrate netplan, why don't make cloud-init just write networkd config files."
1771886,2020-10-31 05:33:24 UTC,Would still love to see IPv6-PD implemented in netplan.
1771886,2020-04-10 08:54:05 UTC,When will this be fixed? Why was netplan made the default when it does not have feature parity with ifupdown? Why is this question being ignored?
1771886,2020-06-09 15:23:06 UTC,"+1
Gave up on Ubuntu in a router/network appliance space due to this. Sure, I can remove netplan and use ifupdown, but why bother when openwrt just works!"
1771886,2020-03-27 01:58:58 UTC,"It's now 2020. I really have to ask: who writes networking software, let alone making it the default, and does not consider fully-supporting IPv6 a requirement?"
1771886,2019-11-28 13:23:47 UTC,"1 year has definitely passed since the release of Ubuntu 18.04
netplan had been updated through 0.36 -> 0.40 -> 0.97 -> 0.98
any progress in supporting dhcp6-pd there ???"
1771886,2018-05-17 21:43:24 UTC,"Hi Bryce,"
1771886,2018-05-17 20:38:05 UTC,Another thing that relates to this is the ability to specify what the duid is that is sent in the dhcpv6 request.  If I recall correctly systemd-networkd offers the ability to specify the duid.
1771886,2020-06-11 14:53:37 UTC,"Fortunately, with systemd-networkd + wpa_supplicant you could go without any of {netplan, ifupdown, NetworkManager} on both modern Ubuntu or modern Debian. As you may imagine, netplan is just a frontend generating (""rendering"") configs for one of possible backends within {networkd, NetworkManager}. So you just copy /run/systemd/network/* into /etc/systemd/network/ , after which you may remove all netplan and related packages and go ahead with systemd-networkd only (which, unfortunately, is nailed to the core of modern Linuxes pretty firmly and not that easily detachable)."
1771890,2018-05-17 22:32:38 UTC,Upstream bug: https://github.com/mate-desktop/mate-terminal/issues/228
1771891,2018-05-19 21:25:01 UTC,"I'm not a developer, but in order for this to get fixed, we can safely assume the devs will need to either be able to reproduce the issue themselves, or at least have someplace to start like a specific error message."
1771891,2018-05-19 23:41:41 UTC,Many thanks for the replay Matt Mayfield.
1771891,2018-05-20 07:00:30 UTC,Dear Matt Mayfield.
1771897,2019-09-19 11:58:18 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1771902,2018-05-18 01:42:14 UTC,"Sounds like this might be related to bug 1765261, which is also about the wrong characters being entered into password fields."
1771903,2018-05-18 00:22:11 UTC,"The attachment ""Example program reproducing issue, and a patch to fix it."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1771903,2018-05-18 15:50:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771904,2018-05-18 00:32:18 UTC,Operating system : Windows 7
1771904,2018-05-19 01:25:41 UTC,I Ment Open Rails
1771905,2018-12-14 14:49:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771908,2020-01-05 18:48:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771908,2020-01-05 18:47:03 UTC,"I also encountered this problem on Ubuntu MATE 19.10, glusterd would refuse to start with RDMA. No useful diagnostic information, the glusterd program would just crash during startup. I found this bug report and tried unloading the rdma_ucm kernel module and that worked."
1771910,2018-05-18 10:03:44 UTC,"@vpc, would you provide more detailed logs for this? We have 4 components: trove-api, trove-taskmanager, trove-conductor, trove-guestagent(inside the Nova instance). If the trove instance changed to 'error' status, we probably could find some related erros inside the logs in trove-api, trove-taskmanager and trove-guestagent."
1771922,2019-11-18 13:27:44 UTC,See duplicate for additional example
1771926,2018-10-28 20:51:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1771926,2020-08-10 01:45:54 UTC,gmic (2.2.3)
1771928,2018-05-18 04:06:26 UTC,"Just a simple test which tries to create instant from 'bad' image uploaded to glance
show that disk space is lost. In my case it was ~= 800Mb image"
1771928,2018-05-20 06:01:21 UTC,Patch submitted: https://review.openstack.org/#/c/569325/
1771928,2018-06-05 12:19:51 UTC,"Reviewed:  https://review.openstack.org/569325
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=9c411c88280e71a0643f66d8566c73c36fca1647
Submitter: Zuul
Branch:    master"
1771928,2018-06-22 17:51:39 UTC,Moving this back to Triaged for the nova-lxd package until we get a new package version uploaded to Cosmic (Rocky).
1771943,2019-02-13 09:10:08 UTC,"I'm sorry for the comment #16, I have wrong the bug id! If anyone can remove it..."
1771943,2019-02-14 10:20:05 UTC,Upstream comment
1771943,2019-02-14 11:49:40 UTC,"Il 14/02/19 11:20, Sebastien Bacher ha scritto:> Upstream comment

>
> 'smbc_new_context() calls smbc_setOptionUseCCache(context, True) if
> LIBSMBCLIENT_NO_CCACHE environemnt variable is not defined. I suppose it
> is not defined in your system, but can you please confirm it?is it correct to test if there is such a variable set in the user environment? This command


$ env | grep SMB; echo $?
1"
1771943,2019-02-18 15:25:29 UTC,The patch has been fixed in upstream git now
1771943,2019-02-15 09:19:24 UTC,Debug version uploaded to https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16391488 you need to download the debs corresponding to the ones you have installed (dpkg -l | grep gvfs) and install them with dpkg -i *.deb then restart your user session
1771943,2019-02-18 07:25:33 UTC,BINGO!
1771943,2019-02-18 07:46:18 UTC,"The fix first needs to be landed upstream/in the current Ubuntu serie, then we can add it to the SRU backlog"
1771943,2019-02-13 08:38:09 UTC,"Il 12/02/19 20:38, Andreas Hasenack ha scritto:> [...]

> I found some bugs in debian and upstream, still open, but in a
> ""needinfo"" state.


do you mean the bug https://bugzilla.samba.org/show_bug.cgi?id=10455?"
1771943,2019-02-14 15:31:03 UTC,"Upstream posted a potential fix
https://gitlab.gnome.org/GNOME/gvfs/merge_requests/34"
1771943,2019-02-11 10:34:20 UTC,"But I don't use kerberos, I use winbind to have domain membership authentication! smbclient seems to works perfectly with cached credential if I remove the optional parameter --kerberos... but why gvfs doesn't it?"
1771943,2019-01-31 07:18:10 UTC,"Il 30/01/19 17:17, Sebastien Bacher ha scritto:

>> the command
>> $ gio mount //server/share
>
>> ask me user, domain and password.
>
> you mean ""smb://server/share""? because your previous paste was ""gio:
> file:////server/share: volume doesn?t implement mount"" or does it ask
> for credential after logging that error?


yes of course, I'm sorry, I mean smb://server/share!!!"
1771943,2019-01-31 14:11:22 UTC,"Il 31/01/19 14:31, Sebastien Bacher ha scritto:

> Upstream comment
>
> 'SMB backend doesn't use smbc_setOptionUseCCache explicitly in order to
> enable winbind ccache, but it seems that it is enabled by default, at
> least on my system. Please try to obtain the debug log again, but also
> with GVFS_SMB_DEBUG=3.
"
1771943,2019-01-31 13:31:42 UTC,Upstream comment
1771943,2019-01-31 10:09:25 UTC,"The issue got reassigned to the gvfs backend
https://gitlab.gnome.org/GNOME/gvfs/issues/369"
1771943,2019-01-31 09:45:00 UTC,"Thanks, I've send the report and the debug info upstream let's sse if they have a better idea about the problem
https://gitlab.gnome.org/GNOME/nautilus/issues/864"
1771943,2019-01-30 16:17:51 UTC,"> the command
> $ gio mount //server/share
"
1771943,2019-01-30 14:23:06 UTC,"Il 30/01/19 14:10, Sebastien Bacher ha scritto:

> Thanks for the extra info, one problem though
>
>> $ LANG=C; gio mount //server/share
>> gio: file:////server/share: volume doesn?t implement mount
>
> the url should be prefixed with the share type as in nautilus, so it's
> probably ""smb://server/share"" in your case
"
1771943,2019-01-30 13:10:40 UTC,"Thanks for the extra info, one problem though"
1771943,2019-01-30 10:09:42 UTC,"$ LANG=C; gio mount //server/share
gio: file:////server/share: volume doesn?t implement mount"
1771943,2019-01-30 09:21:18 UTC,"what happens if you ""gio mount <url>""?"
1771943,2019-01-30 08:02:24 UTC,"Hi Sebastien, thank you very much to spend your time to try solve this bug..."
1771943,2019-01-31 15:57:49 UTC,"Thanks, I've sent the info upstream"
1771943,2019-01-29 23:13:51 UTC,"Thank you for your bug report, could you give details on how the mounts are done? Is that accessing smb:// urls in nautilus/gvfs or do you mount the share by other means? could you add your journalctl log from a session where you triggered the issue?"
1771949,2018-05-21 07:08:35 UTC,What about this error?
1771949,2018-05-18 07:06:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569350"
1771973,2018-09-21 16:22:47 UTC,"> The only two examples given for creating exports promote the use of no_root_squash.
> This really should not be done by default.
> One with no knowledge of NFS and who's interested in creating a share quickly
> will just apply a potentially dangerous setting without consideration.
"
1771973,2020-01-13 18:51:45 UTC,I also was a bit surprised to see no_root_squash used in the examples.  It may be ok for ones' personal home network but even there it has some risks.
1771977,2018-06-20 19:18:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/576943"
1771977,2018-10-17 12:30:45 UTC,"Change abandoned by James Page (<email address hidden>) on branch: master
Review: https://review.openstack.org/576943"
1771980,2018-05-31 11:02:51 UTC,https://github.com/juju/juju/pull/8780
1771986,2018-05-18 10:00:08 UTC,saving as emf does not crash
1771986,2018-05-18 10:52:21 UTC,"-confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- no exit message was received in DOS
- backtrace attached:"
1771986,2018-05-18 10:58:02 UTC,"in Windows 10, Inkscape 0.92+devel (7f24a76, 2018-04-17)
I get the following DOS error message:"
1771986,2020-08-18 20:48:48 UTC,"OS: Windows 10 Home x64 EN-US, Version: 1909, Build: 18363.1016
Inkscape 1.0 (4035a4fb49, 2020-05-01)"
1771986,2020-08-18 22:52:01 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1771987,2019-05-22 10:30:18 UTC,"I am seeing similar after re-running the setup-openstack playbooks after a rolling replacement upgrade of the control plane from xenial->bionic, with OSA rocky deployment."
1771987,2018-06-06 01:31:40 UTC,"Hi,"
1771987,2018-06-05 16:38:55 UTC,"Hey there,"
1771987,2019-07-08 20:16:18 UTC,"I also got a similar issue.
It could potentially be caused by rerunning a playbook.
Restarting doesn't fix it for me, someone has a suggestion?"
1771989,2018-05-21 15:52:23 UTC,I don't see a reason that we would want anyone to use the LVM driver with CHAP authentication disabled.  Why do this?
1771989,2018-05-22 10:21:36 UTC,"Hi Eric.
One reason is when the initiator node has bugs in its implementation and doesn't handle CHAP correctly. The operator may not want to, but they may have to disable CHAP in such circumstances. It is certainly a reasonable argument but I think it is better applied to what the default value of the option should be, rather than whether the option should be there or not.
Also, the option is supported by a large number of the current volume drivers. I don't see why LVM should be the exception to this."
1772001,2019-09-02 08:41:14 UTC,"the exception raised in this case is very generic, as it is raised in other cases too in which we want it to retry."
1772004,2018-05-20 21:06:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772006,2018-05-31 01:17:01 UTC,Waiting for https://bugs.launchpad.net/kicad/+bug/1728258
1772016,2019-01-09 09:41:26 UTC,The current PR that should workaround this bug in systemd is here: https://github.com/snapcore/snapd/pull/6331
1772016,2019-10-29 19:21:33 UTC,The pull request with a workaround for this bug has been merged into snapd in January of 2019. This version was released multiple times since then. I'm marking this bug as fix released.
1772016,2018-11-21 12:28:32 UTC,"The problem can be reliably reproduced on Ubuntu 18.10, Fedora 28/29 and Arch using this script: https://gist.github.com/bboozzoo/d4b142229b1915ef7cc0cf8593599ad9"
1772016,2018-11-16 10:33:35 UTC,"This is an upstream issue around mount (a race likely) that we see from time to time in spread tests (and afair it was reproduced with a simple script, with no snapd involved). I don't think we can show any better error here. Zyga might know more."
1772016,2018-11-16 10:48:24 UTC,This is a bug in libmount. I'm tasked with fixing it this cycle. I will likely start working on it next week as it is getting more exposure with recent systemd update.
1772016,2018-11-21 12:58:00 UTC,Reported to systemd upstream: https://github.com/systemd/systemd/issues/10872
1772019,2018-05-18 13:32:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569407"
1772024,2018-05-25 14:27:43 UTC,"Setting to high, as this affects linux testing, which blocks gcc."
1772024,2018-05-23 21:47:08 UTC,"Package did not apply patches from debian/patches/, added --with quilt to dh call on debian/rules, fixing this."
1772024,2018-07-24 06:29:44 UTC,"The verification of the Stable Release Update for nbd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1772024,2018-05-18 13:48:45 UTC,ubuntu_nbd_smoke_test.nbd-smoke-test is causing the failure:
1772024,2018-07-23 20:30:22 UTC,Server doesn't crash when using the package from bionic-proposed.
1772024,2018-07-24 06:29:39 UTC,This bug was fixed in the package nbd - 1:3.16.2-1ubuntu0.1
1772024,2018-06-15 22:29:32 UTC,Thanks for fixing up the debdiff! I've sponsored it to Bionic after making a couple changes:
1772024,2018-06-15 19:39:16 UTC,"The latest version for bionic has been built on ppa:cascardo/ppa3, and has been tested on a ppc64le bionic system."
1772024,2018-06-15 19:35:19 UTC,"Attaching a new debdiff, as simple diff (no quilt), to bionic."
1772024,2018-06-14 21:15:41 UTC,"@cascardo thanks for the debdiffs! I noticed that the nbd package is patchless (run 'what-patch' in the source directory to check this) but you added a patches via quilt. As much as I prefer quilt over patchless source packages, can you change it back to patchless and apply the patches directly to the source?"
1772024,2018-05-29 15:31:40 UTC,This bug was fixed in the package nbd - 1:3.17-2ubuntu1
1772024,2018-06-21 15:42:45 UTC,"Hello Kleber, or anyone else affected,"
1772025,2018-07-12 08:35:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772028,2018-05-18 15:48:26 UTC,"I set this to confirmed and high because I see the functions are missing from any upgrade scripts. That said, I seem to have all but the last one, evergreen.asset_copy_alert_copy_inh_fkey, in a database that was upgraded from 2.12.8 to 3.0.7 using the upgrade scripts. I don't know where the functions came from unless they were always there or were added to our production database at some point prior to the dump and test upgrade. I don't remember adding them, myself."
1772028,2018-05-18 15:55:36 UTC,Hello.  We also seem to be missing a couple functions in our database.  What is interesting is that for the 3.0 upgrade we only seem to be missing evergreen.container_copy_bucket_item_target_copy_inh_fkey() but we were NOT missing the evergreen.asset_* functions that Bill has in his patch.
1772028,2018-05-18 18:03:17 UTC,"A note on oils_json_to_text(). I had that in the public schema, which seems to date back to v2.0. I did copy it into the evergreen schema which is where it's expected in 3.1"
1772028,2018-05-18 19:23:32 UTC,"I recall there being some discussion of these functions missing before.  It turns out they are supposed to be created by the 1063 upgrade script in 2.12.6 to 3.0.0.  Looking at the code in 1063, it seems to me that the new functions will not be created if your database lacks the prerequisite constraints on asset.copy_pkey."
1772028,2018-05-21 19:26:32 UTC,"Hmmm, our database has this:"
1772028,2018-07-11 14:50:12 UTC,I am running into this problem as well.  Upgrade script 1063 does not outright create the functions.  It runs a query that should return data that is then used as variables to create the functions.  My 2.12.4 system built in 2012 and upgraded ever since returns no rows.  A 2.12.0 system built recently returns 3 rows and creates the needed functions.
1772028,2019-02-27 22:32:20 UTC,"It looks like the vandelay.import_item imported_as_fkey  constraint was added to the 2.2 release, but wasn't included in the upgrade scripts.  So possibly those that have a pre 2.2 database, may run into at least that one?"
1772028,2019-05-24 20:38:37 UTC,"It does feel a little weird to push these into the upgrade script, but really, either you had these functions and upgrade worked, or you didn't and it didn't, and in either case, adding them in here is fine.  I also agree with the general sentiment that recreating functions as they already may exist does no harm."
1772029,2018-05-18 14:14:56 UTC,"The ceph_volume_client RFE is here,
https://tracker.ceph.com/issues/24173"
1772029,2020-06-18 16:01:29 UTC,Additional comments http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-06-18-15.01.log.html
1772029,2019-10-24 14:58:17 UTC,Ramana any update or milestone that can be set so we can address this issue?
1772033,2020-05-11 20:19:16 UTC,I don't believe it's been done.
1772033,2020-05-11 20:05:33 UTC,"Is this still an issue, or was this resolved by updates to MAAS or Maniacs-setup?"
1772034,2018-05-24 22:42:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/570469"
1772034,2018-05-24 22:54:20 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/570473"
1772034,2018-09-12 20:24:02 UTC,"Change abandoned by John Fulton (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/570473
Reason: don't need anymore as per https://review.rdoproject.org/r/#/c/15000/9"
1772034,2019-06-25 12:45:40 UTC,"We can only test Ceph upgrade in RDO infra because we need at least 3 controllers; we could probably enable Ceph in the HA job (colocating the OSDs on the compute, so we don't add more nodes) and have ""upgrade"" run on that config."
1772035,2019-02-18 15:02:42 UTC,"See here for some additional notes on how to configure local PPA mirrors, which should be helpful information when updating maniacs-setup:"
1772035,2020-05-11 20:06:47 UTC,"Is this still an issue, or was this resolved by updates to MAAS or Maniacs-setup?  I seem to recall htis is resolved using the same method for configuring local archive mirrors by listing them in MAAS?"
1772038,2018-06-18 06:57:52 UTC,I have an old HP 8100 SFF that have the same problem with the 4.15 kernel.  I solved it by booting with the following kernel parameters: acpi=off noapic nolapic
1772038,2018-07-30 15:19:26 UTC,"I have a similar HP dc5800 machine. Booting from 4.15 kernel after upgrade to Ubuntu 18.04 results in very quick kernel crash (less than 1 second), as does booting from the Ubuntu 18.04 ""desktop"" install DVD."
1772038,2018-07-30 15:33:05 UTC,"Similar bug report about problems booting 4.15 kernels on HP dc5800 machines on RedHat's bugzilla:
  https://bugzilla.redhat.com/show_bug.cgi?id=1520265"
1772038,2018-09-05 14:51:48 UTC,Upgrading the BIOS to 1.6 does indeed seem to fix the problem.
1772038,2018-05-26 08:43:48 UTC,"If this bug is not going to be addressed by the linux kernel team, then please make that clear, so that I can determine the proper disposition of the hardware that will no longer run linux. Thanks!"
1772038,2018-12-21 18:02:03 UTC,"This is also affecting the 3 Lenovo Thinkpad T420s I have tried in all live/install and normal modes. I can only operate them with the acpi=off parameter, but in this case Standby/Restart/Volume controls don't work. Note: All 3 models have a dedicated nvidia card, which is switched off in the BIOS Menu."
1772038,2018-12-21 18:33:06 UTC,After updating to the latest kernel (the update before was on 2018-12-06) the issue in operational mode did get fixed. I can boot without the acpi=off parameter
1772038,2020-02-01 02:16:56 UTC,My Mom has a (HP) Compaq Presario SR5710Y.  Trying to install with USB of Kubuntu 18.04.1 and 18.04.2 had same kernel panic.  Using Kubuntu 18.04.3 and it has installed without issue and is now updating.
1772038,2018-09-08 05:46:48 UTC,"Confirming this issue for USB installer for both 18.04.1 and 16.04.5 on HP Compaq dc5800.
The ""acpi=off noapic"" kernel parameter workaroud works for installing the system.
And interestingly, once installed to SATA drive the system boots and behaves normally."
1772038,2018-05-26 08:39:01 UTC,"Here is some other interesting observations.
I've tried the new release of Fedora (F 28) which uses the latest kernel 4.16 (even newer than ubuntu's 4.15) and to no one's surprise, it produces the same result (exactly the same result).
So this bug is in the Linux kernel, and is not limited to just ubuntu!"
1772038,2018-05-21 18:08:25 UTC,Can you install and see if installing a 18.04(Bionic) kernel will boot on 17.10?  The kernel can be downloaded from:
1772038,2018-05-23 09:32:27 UTC,"OK, I've had time to try the latest kernel from the daily-live/current directory called 'cosmic' and it does the same thing. I've tried it on my second machine and like I said earlier it has the same results but the timestamps are lower. I'll post a new picture of the screen results."
1772038,2018-05-23 09:39:28 UTC,"After reviewing both screen shots I see that I miss read the timestamps in the first image, so the crash on my second machine has higher timestamp numbers NOT lower ones. Opps!"
1772038,2018-05-18 22:31:20 UTC,"My system will not run ubuntu or xubuntu 18.04, thus I can not collect log files."
1772038,2018-05-18 17:00:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1772038,2018-05-18 22:43:44 UTC,"Machine details:
HP-Compaq DC5800 small form factor, 4 GB Ram, Seagate 1TB HDD, ATI/AMD Radeon B530 video card!"
1772038,2018-05-21 18:09:13 UTC,"Also, it would be good to know if this bug also happens with the current daily iso:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/"
1772038,2018-05-18 16:21:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1772038,2018-05-22 09:59:58 UTC,"I'm looking for the modules on the web page given and I'm not seeing
where to download them. I'm not familiar with how launchpad works, so if
there is another way to do this pls let me know."
1772038,2018-05-22 10:07:09 UTC,"I have 2 of these computers, the 2nd computer has 8GB of memory and 1TB HDD, same video card, but this second computer has a WiFi card installed. I've tried several of the DVD's that I burned and I get the same results the only difference is the time stamps shown on the screen is different. On this second computer the crash happens quicker (ie the timestamps are lower)."
1772038,2018-05-22 10:12:34 UTC,"These are older machines and boot with a BIOS. If I get free time, I'll
remove the graphics card and see what happens, but I agree with
jsailsbury I think it will still crash."
1772038,2018-05-22 10:15:41 UTC,"Downloading the desktop image now, will report back later!"
1772038,2018-05-22 11:24:24 UTC,"Here is another observation, when I run virtualbox on 17.10, and then create a guest OS with 18.04 it runs fine, no kernel crashes. Thus this evidence seems to point to the fact that 18.04 is not playing nicely with the HP BIOS, but 17.10 does play nicely. 18.04 seems to have no problems with the virtual BIOS provided by VirtualBox."
1772038,2018-05-21 18:14:11 UTC,"Does your device boot UEFI or BIOS? The small bit of crash we can see looks like some kind of talk with the bootrom. If you can remove the video card that may also be the issue, they have been known to cause problems with just about everything. To debug without graphics (if your cpu/motherboard doesn't have intergrated) is to connect a serial console."
1772043,2018-05-18 14:44:23 UTC,package version 1.15.9 on Ubuntu Bionic
1772044,2018-05-28 13:41:38 UTC,This bug was fixed in the package curtin - 18.1-17-gae48e86f-0ubuntu1~16.04.1
1772044,2018-05-28 13:42:52 UTC,This bug was fixed in the package curtin - 18.1-17-gae48e86f-0ubuntu1~18.04.1
1772044,2018-05-28 13:40:05 UTC,This bug was fixed in the package curtin - 18.1-17-gae48e86f-0ubuntu1~17.10.1
1772044,2018-05-24 17:17:47 UTC,"From the MAAS perspective, we can confirm that 18.1-17-gae48e86f-0ubuntu1 doesn't show any regressions in bionic."
1772044,2018-05-27 09:55:19 UTC,I have performed a verification of #1728742 on 2.3.0 (6434-gd354690-0ubuntu1~16.04.1) with curtin added from xenial-proposed (18.1-17-gae48e86f-0ubuntu1~16.04.1) on a MAAS node as it is delivered by MAAS to an ephemeral image. Links were created correctly for the following cases:
1772044,2018-05-24 17:18:10 UTC,"From the MAAS perspective, we can confirm that 18.1-17-gae48e86f-0ubuntu1 doesn't show any regressions in xenial."
1772044,2018-05-21 14:10:47 UTC,"Hello Ryan, or anyone else affected,"
1772044,2018-05-21 14:07:01 UTC,"Hello Ryan, or anyone else affected,"
1772044,2018-05-21 14:02:56 UTC,"Hello Ryan, or anyone else affected,"
1772044,2018-05-28 13:32:52 UTC,"The verification of the Stable Release Update for curtin has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1772052,2018-05-25 12:21:48 UTC,"Hello, the log file you entered is incomplete of the information needed to understand the error, you must attach the file that OR created and do not do a simple copy and paste, moreover, you are using an old version of or, i recommend you updating the simulator and try again."
1772053,2019-12-23 15:47:11 UTC,"Related bugs, possibly some duplicates of this one:"
1772053,2020-04-27 21:13:07 UTC,"A few of the bugs linked in the comment #1 are still open, but many of the others have already been fixed, and the omnibus fix in comment #11 resolves most of the rest of them, so I'm going to go ahead and sign off on this omnibus bug and the other linked bugs that are fixed with the omnibus."
1772053,2020-03-16 17:19:39 UTC,Here is a cleaned up branch of code that Daniel Pearl left behind at CW MARS that is supposed to resolve this bug. I'm sharing it here with the pullrequest tag in the hope that someone will test it for bug squashing week.
1772053,2019-12-23 14:28:30 UTC,I have reviewed Daniel Pearl's code and do not think it is correct. I have not actually tried running it.
1772053,2020-04-28 17:30:29 UTC,"Fixes pushed to master and rel_3_5. Thanks Dan, Jason, and Terran!"
1772053,2019-08-20 16:36:41 UTC,Updated the sheet to add: Hold Shelf Slip should include Hold Note data. I am using 3.3.2.
1772053,2018-05-22 19:25:08 UTC,"Adding a new bug to this list: https://bugs.launchpad.net/evergreen/+bug/1772444 - Patron fields added to Bills, current and Bills, historical. Currently has pullrequest tag."
1772053,2019-12-19 13:58:58 UTC,Dan Pearl had some code to address some of these issues. We'll review it at CW MARS and see what remains to be done.
1772053,2018-06-27 17:43:50 UTC,"I set this bug to confirmed because it affects more than 1 site, i.e. 3 people plus the submitter."
1772053,2018-05-31 22:14:13 UTC,Added Shelving Location for on the Items Out receipt to the google sheet.
1772053,2018-07-26 17:20:00 UTC,"Blake, the patron fields should have been added to bills, current and bills, historical in Evergreen 3.0.9, per bug 1772444. I do not have 3.0.9 installed so I cannot confirm this, but I did test an earlier version of the patch, and the fields did indeed print with the syntax {{patron.first_given_name}}, etc."
1772053,2019-03-20 16:58:06 UTC,It is my intention to address these items on a piecemeal basis.
1772053,2018-07-26 16:45:35 UTC,I would like to point out that all of the fields that were fleshed out for bug 1737540 (thank you Jason) - are not fleshed out on bills_current. I have tested each of these with this syntax:
1772056,2018-05-18 15:44:13 UTC,"Sorry, forgot to mention, this is on a brand new install of Ubuntu 18.04.  Using I3 as window manager."
1772056,2019-08-22 17:35:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772058,2018-05-22 00:01:43 UTC,This bug was fixed in the package linux-azure-edge - 4.15.0-1012.12~16.04.2
1772060,2018-08-14 06:33:55 UTC,High I have same problem with bionic updates. Here is summary of error. I found this happens when kernel updates occurred.
1772060,2020-07-02 07:24:21 UTC,"Looking through the cloud archive repos (http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/), it looks like this is now resolved back to bionic-rocky"
1772062,2019-04-09 17:04:12 UTC,"We received the following bug report on our internal ticket system this morning.  This bug looks like the closest candidate, so I am adding it here:"
1772062,2019-04-09 19:09:01 UTC,"Jason,"
1772062,2019-05-14 13:51:06 UTC,This is still a problem for me. At the conference I was told to re create my templates but even when I did that as of yesterday they did not always work in the Web Client. In XUL this is not an issue. I've tried clearing my cache and rebooting. Not sure what all else to do.
1772062,2019-05-14 14:06:24 UTC,"I find that for example I can use my template for Adult Fiction which does work,  apply that when I am adding an item, then click the template for example, Large Print Fiction, and then the correct attributes will for Large Print Fiction will then appear."
1772062,2019-06-10 21:17:32 UTC,"Since no objections were raised, I am going to go ahead and mark this as a duplicate.  Please undo if needed!"
1772062,2019-05-14 14:39:19 UTC,"Ok thanks, Elaine."
1772062,2019-05-14 17:30:16 UTC,"Personally, I think this bug is resolved by the changes on bug #1788680. The initially reported console errors are exactly what that change fixes.  If anyone tries the code committed for #1788680, please be sure to clear cache, a hard refresh is not enough."
1772062,2018-11-26 20:35:54 UTC,Removing milestones for lack of a pull request for this bug.
1772062,2019-05-14 14:09:30 UTC,"Linnae,"
1772062,2018-11-14 16:44:16 UTC,"Removing pullrequest since the patch provided only addresses null stat cats, which was broken out in bug 1788680 with its own pullrequest."
1772062,2019-03-19 13:59:36 UTC,SCLENDS has signed a contract with Equinox to address this bug.
1772062,2018-10-18 19:43:03 UTC,"Meg,"
1772062,2018-10-23 17:13:19 UTC,"Elaine,"
1772062,2018-06-08 17:40:00 UTC,I suspect that bug 1773249 is related.
1772062,2018-06-08 17:52:26 UTC,"... Or maybe not. At least one other site has had reports of the copy template dropdown being empty, correlated with the NOT CONNECTED errors on retrieving templates from the other bug, but that site has not been getting reports of the issue in this bug."
1772062,2018-05-18 17:35:04 UTC,"John,"
1772062,2018-08-23 19:08:31 UTC,"Since the null statcat bugfix is only a partial fix for copy template woes, it has been broken out into bug 1788680. Other issues with copy templates still need to be addressed."
1772062,2018-06-19 21:39:33 UTC,One problem with copy templates is that they don't fully apply when the template has null statcat values but a non-null statcat filter value.  I've pushed a fix for that:
1772062,2018-10-04 14:19:53 UTC,"These intermittent and inconsistent template issues are a big inconvenience for us at 3.1.5. Here is a screen cast of one of them: https://kmetzm-parklandlibrary.tinytake.com/sf/Mjk2ODQxOF84OTA1OTQy
In this instance the template is not applied at all. We have also seen instances of it being applied, then not saving."
1772062,2018-10-10 18:15:40 UTC,"SCLENDS is also experiencing this problem on 3.1.5 and, as others have said, it's a significant cataloging issue."
1772062,2018-10-10 20:00:44 UTC,We have had a number of templates brought into the web client fail that have the phrase HACK:KLUDGE:NULL. A new template in the web client would eventually get overwritten by the old one from the XUL client. deleting the XUL client one and then recreating in the web client has been successful for those templates exhibiting that issue.
1772062,2018-05-18 16:38:40 UTC,"Confirmed on 3.0.7 in the sense that I see the same erratic behavior, but I can't really add any useful details beyond what John has noted."
1772062,2018-10-18 15:03:16 UTC,"Elaine,
It's hit-and-miss on what doesn't populate.  Shelving location is a popular one, but we also see status, and circulate as type."
1772062,2018-09-14 00:53:57 UTC,"At this time, I am unable to reproduce the original bug. Given the bug's sporadic appearance, I may have simply had a run of luck."
1772062,2018-06-05 20:50:33 UTC,"We received reports on similar issues. Besides, there are reports on that values are not applied for one template, but after applying another template first, then applying it again, it works."
1772064,2019-05-27 20:09:39 UTC,Proposed patch fixes landscape-client-charm false-positive registration result with server.
1772076,2019-05-07 14:42:27 UTC,"This happens also with the Message Window, Help Window, Objective Window. They all have in common that they use multilinetextarea. As soon as the textaree gets focus, the arrow key can't be used any more."
1772076,2019-09-15 16:00:55 UTC,Migrated to https://github.com/widelands/widelands/issues/1072
1772080,2018-05-18 18:09:29 UTC,Bug is fixed in branch ~yrke/tapaal/guirefactor
1772080,2018-07-04 11:14:30 UTC,"Kenneth, can you confirm this is fixed in the anniversary branch on windows?"
1772081,2019-01-28 22:17:58 UTC,"> disabling it increases power consumption of CPU at least by 80% in idle state
"
1772081,2018-05-21 21:26:58 UTC,apport information
1772081,2018-10-21 09:52:07 UTC,"Confirming this issue, Ryzen 2500U on HP Notebook 15-db0229ur.
- Disabling C-State C6 partially solves the problem
- Latest BIOS from manufacturer (F.11 Rev.A) - unable to access any of advanced settings!"
1772081,2018-10-21 09:08:15 UTC,"Confirming this issue, Ryzen 2500U on HP Notebook 15-db0229ur.
- Disabling C-State C6 partially solves the problem
- Latest BIOS from manufacturer (F.11 Rev.A) - unable to access any of advanced settings!"
1772081,2018-06-26 08:46:08 UTC,"I can't answer your question about battery life according to the parameters, I did not test that."
1772081,2018-06-25 22:08:14 UTC,"Hi,
   I just got a freeze 6 hours in to using idle=nomwait amdgpu.audio=0"
1772081,2018-06-25 15:37:06 UTC,"Hi @kaihengfeng the bios is the one provided by HP, it doesn't seem to have that option."
1772081,2018-06-21 11:54:48 UTC,"Hi,
  I'm away from my laptop for a week, it's the default HP bios, so I don't think there is a typical idle current option."
1772081,2018-06-21 04:16:01 UTC,"Is there a ""Typical Idle Current"" option in your BIOS?"
1772081,2018-06-18 21:06:28 UTC,"Did you tried:
idle=nomwait
as kernel-parameter via grub?
It fixes CPU-related freezes for me with the Ryzen 2500U."
1772081,2018-05-21 21:26:57 UTC,apport information
1772081,2018-05-21 21:26:43 UTC,apport information
1772081,2018-05-21 21:26:55 UTC,apport information
1772081,2018-05-21 07:01:34 UTC,Same as LP: #1690085?
1772081,2018-05-18 18:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1772081,2018-05-21 21:26:43 UTC,apport information
1772081,2018-05-21 21:26:45 UTC,apport information
1772081,2018-05-21 21:26:47 UTC,apport information
1772081,2018-05-21 21:26:46 UTC,apport information
1772081,2018-05-21 21:26:49 UTC,apport information
1772081,2018-05-21 21:26:50 UTC,apport information
1772081,2018-05-21 21:26:51 UTC,apport information
1772081,2018-05-21 21:26:52 UTC,apport information
1772081,2018-05-21 21:26:54 UTC,apport information
1772081,2018-05-21 21:26:48 UTC,apport information
1772081,2018-05-21 21:26:56 UTC,apport information
1772083,2019-09-02 11:18:23 UTC,I confirm 91-libinput-egalax-local.rules workaround Works.
1772083,2019-09-03 01:54:16 UTC,I don't have any authority to say what can go into 18.04. But anyone can try to get things into 18.04...
1772083,2019-09-02 11:36:01 UTC,Also Driver from touch screen Manufacturer works perfectly :
1772083,2019-08-31 12:22:29 UTC,"Hi daniel , do you feel this kind of patch ( the one above)  can goes in 18.04 ?"
1772083,2019-08-30 08:10:02 UTC,Just came accross this problem with Shuttle X50V6
1772083,2018-09-22 02:56:45 UTC,i have the same problem and did work with 16.04
1772083,2018-05-22 17:28:25 UTC,"It looks like this bug has been previously reported on the libinput database as bug 102632 and they marked it WONTFIX. This touchscreen worked fine with Ubuntu 16.04 (which used evdev), so I am trying to figure out how that worked."
1772083,2018-05-21 02:23:06 UTC,Please help us to progress this issue by reporting it to the libinput developers here:
1772083,2019-08-30 08:26:19 UTC,Sounds like we'll just need to carry a workaround patch for it.
1772087,2018-05-18 20:20:45 UTC,"The attachment ""replaced the dummy entries for ID and license with the ones for free access, and the database names and IDs of the commercial product with the free ones."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1772087,2021-01-09 18:09:55 UTC,"geoipupdate 4.6.0-1 (just landed in Debian) is documenting the new behavior better, including a config file change, plus a README.Debian adjustment."
1772088,2018-05-18 18:32:35 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ServerShowV254Test%5C%22%20AND%20message%3A%5C%22Error%20processing%20message%20locally%3A%20OrphanedObjectError%3A%20Cannot%20call%20obj_load_attr%20on%20orphaned%20Instance%20object%5C%22%20AND%20tags%3A%5C%22screen-n-cell-child.txt%5C%22&from=7d
1772088,2018-05-19 14:46:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/569576"
1772088,2018-05-20 23:57:23 UTC,"Reviewed:  https://review.openstack.org/569576
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=419e6198fadf4e91855109b76374d5205164b467
Submitter: Zuul
Branch:    stable/queens"
1772088,2018-06-04 13:52:19 UTC,This issue was fixed in the openstack/nova 17.0.5 release.
1772092,2018-05-26 20:50:25 UTC,The current template buttons are clearly biased to a german user :)
1772092,2018-05-27 23:26:50 UTC,"Well, it's up to ubuntu (and any other distro) folks to ship xfce4-dict or not.
I'll try to maintain it as long as I have the time, I like to think there is a guy or two that still find it useful ;)"
1772092,2018-05-27 07:37:30 UTC,"Frankly I never really used xfce4-dict; I only came across it trying to help the xubuntu community update their test cases, as requested by Kev Bowring/flocculant.
When I did come across xfce4-dict it did occur to me that the functionality of xfce4-dict seemed a tad outdated to me. So, no, I have no problem with you turning your attention to more important matters."
1772092,2018-05-25 19:22:18 UTC,"Would it be possible to have the URL and the buttons adapt to the locale of the install at the initial set up of dict?
Or that at the first start up of the program the user is asked for the URL?
I expect most users would want to go their ""local"" wiki. But I may be wrong of course."
1772092,2018-05-23 01:38:48 UTC,"Works for me, at Preferences -> Web Service -> URL I set it to http://nl.wikipedia.org/wiki/{word} and it correctly opens the URL https://nl.wikipedia.org/wiki/Mug and I'm query for ""mug"" (The radio button group ""Search with:"" is set to ""Web Service"").
When you set the ULR at preferences, is it lost? I mean, when you reopen preferences, is it reset to http://en.wikipedia.org/wiki/{word}?
Try to launch xfce4-dict from terminal and watch out for any error message."
1772092,2018-05-25 07:36:48 UTC,"First pressing the ""Wikipedia, the free encyclopedia (EN)"" button, then changing the URL does indeed change the url permanently.
So that resolves the issue, but I'm not certain the end-user will naturally assume pressing that button first is needed to change the url."
1772092,2018-05-23 17:59:24 UTC,"I had tried to change the wiki to NL; and indeed the setting is lost, not even accepted I think. If I change the URL and press enter nothing happens."
1772092,2018-05-18 18:46:08 UTC,"Testing Xubuntu 18.10,
Description: Ubuntu Cosmic Cuttlefish (development branch)
Release: 18.10
Linux willem-Lenovo-ideapad-110-15ISK 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1772092,2018-05-25 16:31:01 UTC,"Actually, I don't need to press any of the buttons to change the URL, just open preferences, change and close.
Any suggestion to improve usability or discoverability?"
1772092,2018-05-24 07:00:08 UTC,$HOME/.config/xfce4-dict/xfce4-dict.rc:
1772092,2018-05-25 03:14:39 UTC,"The buttons are just URL templates, their values are hard-coded, what really matters is the value in the URL entry."
1772092,2018-05-24 03:05:02 UTC,"Still can't reproduce and reviewing the code, couldn't find anything suspicious.
That warning message is expected, when there is no running instance of xfce4-dict.
Can you check the contents of $HOME/.config/xfce4-dict/xfce4-dict.rc? More specifically the value of web_url.
You can also try to set it to web_url=http://nl.wikipedia.org/wiki/{word}, just make sure xfce4-dict is not running."
1772094,2018-05-18 20:21:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1772094,2018-11-14 07:10:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772094,2018-11-14 07:14:02 UTC,The module gets excluded in the initramfs core package.
1772094,2018-11-14 07:15:04 UTC,Could this also be backported to xenial 16.04 ?
1772094,2018-11-14 08:19:47 UTC,"The attachment ""multitouch.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1772094,2018-11-27 12:36:38 UTC,I know you guys are very busy but it does not help to ignore community contributions without any comment.
1772094,2019-03-14 16:15:51 UTC,Any progress on this one?
1772097,2018-05-21 22:59:42 UTC,"Since there is a known workaround (though it is undecided if snapd will use it), reducing the priority to 'medium' for now."
1772097,2018-05-21 22:58:50 UTC,"I can confirm that adding mediate_deleted to the snaps and test profiles allows the access with no other denials or log entries. Using mediate_deleted means that while the standard open/unlink methodology for creating a tmp file and then passing the fd to the processes that need it continues to work, other processes will be able to poke around in /proc/pid/fd and obtain access to the deleted file (apparmor will require a ptrace rule for this access though, so in the case of snaps, they would only be able to access their own deleted files via /prof/pid/fd and continue not to have access to other snap's deleted files)."
1772097,2018-05-24 11:35:12 UTC,"For snapd, as much as I don’t want to use mediate_deleted, I feel we need to considering that the open/unlink/linkat method is documented in ‘man 2 open’ and other snaps (eg, vlc, Qt 5.10, etc) are using it (at least until this bug is fixed and used everywhere). While this makes this open/unlink/linkat technique work, it does mean that a process from the snap will be able to open deleted files with open fds via the /proc interface. This is however no worse than when running unconfined since applications can always use /proc/pid/fd/... to access deleted files. Using apparmor with mediate_deleted is an improvement over unconfined in this area since ptrace mediates access to other task's processes."
1772097,2018-05-19 00:47:39 UTC,"So it looks like apparmor is detecting one of the entries as deleted, which it will allow for fds being passed around but not to base lookups off of."
1772102,2020-07-29 09:55:23 UTC,Haven't seen a recurrence in ages. Closing.
1772103,2018-05-26 22:22:28 UTC,"I think with 0.93, you mean the current master branch? (There is no 0.93, and there won't be one)"
1772103,2018-05-26 22:44:04 UTC,"Yes, I meant the master branch. I have some other UI/UX sugestions (like an inspector, or at least auto opening of the configuration dialog best suited for a selected object, which with floating docks would be super annoying but with the change that I suggest with this bug would enhance the most typical workflow). Is this the best place to propose such suggestions? I have to mention that I could contribute on some of them myself
Thanks for your attention!"
1772103,2020-04-08 10:30:50 UTC,Closing because INVALID: Bug migration.
1772109,2018-05-18 20:26:36 UTC,"Interestingly, killing the ""at-spi2-registr"" process has made Xorg's CPU consumption go down to normal."
1772111,2018-05-18 20:30:28 UTC,"Also, crashes after entering password, leaving no option to actually disable fonts in the font management tool (see #1772110)"
1772123,2020-08-07 04:50:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772127,2018-05-30 12:50:28 UTC,Uploaded a video showing how to set up pkexec instead of gksu at https://www.youtube.com/watch?v=8TGKoQrcahE
1772127,2018-07-09 20:31:03 UTC,"This change has effected a lot of people that run free schools and other important humanitarian efforts please take some action
we will al be most grateful"
1772127,2018-11-04 00:38:13 UTC,I recently installed Ubuntu for the first time. I am not good with programming or software in general
1772127,2019-02-21 15:05:32 UTC,   Many of us dont't understand
1772127,2019-07-19 12:21:05 UTC,"Still have the issue with system-config-samba, it uses gksu."
1772127,2019-07-19 20:14:54 UTC, very sad
1772127,2018-05-25 16:23:05 UTC,I can suggest a work around: are you interested in it? Let me know
1772127,2018-05-19 13:47:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772127,2018-05-25 14:41:23 UTC,"I have the same problem,"
1772132,2020-08-25 17:43:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772133,2018-05-22 15:34:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569999"
1772133,2019-08-19 10:55:13 UTC,"Change abandoned by Jens Harbott (frickler) (<email address hidden>) on branch: master
Review: https://review.opendev.org/569999"
1772145,2018-05-20 14:32:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772145,2018-05-20 14:32:45 UTC,Came across this installing Xubuntu 18.10 for testing purposes.
1772148,2020-09-28 18:21:15 UTC,"As far as I can tell, mount.cifs will not work properly without keyutils for several scenarios:
- 'cifsacl' option is used or
- kerberos auth is used / spnego is used
- when kernel level dns resolution is needed - so the cifs upcall for dns.resolver is required"
1772148,2020-09-28 19:07:03 UTC,"> In addition, DFS support for target shares which are specified as UNC
> names which begin with host names (rather than IP addresses) requires
> a user space helper (such as cifs.upcall)
"
1772148,2020-09-28 18:48:32 UTC,From https://www.kernel.org/doc/readme/Documentation-filesystems-cifs-README
1772148,2020-09-28 18:34:41 UTC,"Can you elaborate on when this happens "" - when kernel level dns resolution is needed - so the cifs upcall for dns.resolver is required""? Together with kerberos still?"
1772148,2020-09-26 16:28:01 UTC,"I just spent days troubleshooting mount.cifs not working and ultimately determined it was due to this bug. I could mount okay, but no id/group mapping to the proper users would take place. All files were owned by the mounter or the uid/gid passed to the mount command. For 'cifsacl' option, this is not how it is supposed to work."
1772148,2020-09-28 18:02:16 UTC,Here is some of the history of the keyutils dependency in the cifs-utils package:
1772148,2019-08-14 13:47:47 UTC,"Hello Carsten, thanks for coming back to us"
1772148,2018-05-23 07:00:08 UTC,A small clarification of the problem: The core issue is that installing cifs-utils (and smbclient) and doing a cifs SMB3 (or SMB1) mount:
1772148,2019-08-14 12:56:05 UTC,"Hi Andreas,"
1772148,2019-07-03 20:39:14 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822841 is what downgraded keyutils from a Recommends to a Suggests
1772148,2019-07-03 20:16:00 UTC,"It's not as simple as that, I can mount cifs shares just fine on 18.04 without having keyutils installed. I tried the exact same command line as in comment #1, bar the username/domain, against a synology DS216 NAS, and it worked just fine:"
1772148,2019-06-28 13:27:03 UTC,Also affects Kubuntu 19.04
1772148,2019-01-21 10:54:21 UTC,"This bug is still present on Ubuntu 18.04 as of 21/01/2019.
I also suggest making keyutils a required dependency, as it is a ""the program fails when this is not installed"" dependency."
1772148,2019-08-17 12:02:41 UTC,"Hi Andreas,"
1772148,2019-01-21 10:54:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772150,2018-09-15 10:42:52 UTC,At a minimum we need to at least label the gain axis.
1772150,2018-09-22 18:37:49 UTC,"I have changed the units to dBV for now. I do not mark the bug as fixed, as there are more appropriate solutions."
1772154,2018-05-21 18:45:03 UTC,apport information
1772154,2018-05-23 21:10:51 UTC,"As per instructions received, I have tested v4.17-rc6 of the Ubuntu Linux Kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6/) and the problem still persists."
1772154,2018-05-24 05:00:24 UTC,"Can you also try latest firmware, iwlwifi-8265-36.ucode in [1]?"
1772154,2019-10-20 21:36:35 UTC,Does this card still have issues with kernel 5.0?
1772154,2018-06-08 18:50:00 UTC,There are lots of new commits in iwlwifi since v4.17-rc6. Please wait for v4.18-rc1 and give it a try.
1772154,2018-06-24 17:52:37 UTC,"I have tried the latest firmware on v4.18-rc1
(ce397d215ccd07b8ae3f71db689aedb85d56ab40) and the problem seems to persist:"
1772154,2018-06-27 03:00:22 UTC,Follow #22 and file a bug to let Intel iwlwifi developers know.
1772154,2019-10-21 02:12:48 UTC,"Most people don't have the hardware you have, so usually it's on your own. There are a few ways to try:"
1772154,2018-05-26 09:23:14 UTC,I have tried the latest firmware on 4.17-rc6:
1772154,2018-05-21 18:44:59 UTC,apport information
1772154,2018-05-21 18:45:00 UTC,apport information
1772154,2018-05-21 18:44:56 UTC,apport information
1772154,2018-05-21 18:03:43 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1772154,2018-05-21 18:44:57 UTC,apport information
1772154,2018-05-21 18:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1772154,2018-05-21 18:44:41 UTC,apport information
1772154,2018-05-21 18:44:42 UTC,apport information
1772154,2018-05-21 18:44:45 UTC,apport information
1772154,2018-05-21 18:44:44 UTC,apport information
1772154,2018-05-21 18:44:48 UTC,apport information
1772154,2018-05-21 18:44:50 UTC,apport information
1772154,2018-05-21 18:44:52 UTC,apport information
1772154,2018-05-21 18:44:53 UTC,apport information
1772154,2018-05-21 18:44:55 UTC,apport information
1772154,2018-05-21 18:44:47 UTC,apport information
1772164,2019-11-13 19:01:56 UTC," Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1772164 and any other logs that are relevant for this particular issue."
1772164,2020-01-13 04:17:35 UTC,[Expired for guake (Ubuntu) because there has been no activity for 60 days.]
1772165,2020-05-16 15:35:08 UTC,I think this PDF describes the same OTC controller as the rpi one:
1772165,2020-05-17 20:36:46 UTC,"Have you seen the patch series I have posted on the qemu-devel mailing
list? ""[PATCH v5 0/7] dwc-hsotg (aka dwc2) USB host controller emulation.""
If you could test that and give your 'tested-by', it could help get the
patch series accepted. That would require you to download the latest Qemu
source code, apply the patches, and build it yourself."
1772165,2020-10-05 20:11:08 UTC,"Which Beagle boards, Jetson Nano, other devices have rich support from
qemu? ARM is critical going forward."
1772165,2020-10-05 21:46:22 UTC,"As of version 5.1, Qemu now supports USB on Raspberry PI 2 and 3. There are a few caveats:"
1772165,2020-10-05 22:10:37 UTC,"I misspoke in my last comment, that first bullet should have said"
1772165,2020-10-06 07:38:38 UTC,Command lines I use are like following
1772165,2019-08-20 12:59:22 UTC,"Right now with
`qemu-system-arm -kernel kernel7.img -dtb bcm2709-rpi-2-b.dtb -cpu arm1176 -M raspi2 -hda 2018-11-13-raspbian-stretch-full.img`
I can access the serial console using `Ctrl+Alt+3` in the QEMU window.
Using raspbian via this serial console is (as far as I can see) the same as using the Lite version.
The main display doesn't accept any mouse/ keyboard input, and `-device usb-mouse` generates a `qemu-system-arm: -device usb-mouse: No 'usb-bus' bus found for device 'usb-mouse` error, even after the `-machine usb=on` command"
1772165,2020-10-06 08:27:12 UTC,"You need to use -M raspi2 (or -M raspi3 for 64-bit kernels) to enable the Raspberry Pi emulation. And you need version 5.1 or newer of Qemu to get the dwc2 USB emulation. I don't think any Linux distributions provide that new of a Qemu, so you might have to build it yourself."
1772165,2020-10-06 08:34:22 UTC,"Here is that command line again, hopefully readable this time:"
1772165,2020-10-06 10:35:34 UTC,"On Mon, 5 Oct 2020 at 21:38, mcandre <email address hidden> wrote:

> Which Beagle boards, Jetson Nano, other devices have rich support from
> qemu? ARM is critical going forward.
"
1772165,2020-11-17 09:47:58 UTC,"Since USB emulation has been added in QEMU 5.1, I'm marking this feature request as done now. If there are still issues, please open a new ticket instead."
1772165,2020-10-06 07:36:36 UTC,"I did this, but still can't access USB device, connected to host, from guest."
1772165,2019-08-19 14:47:29 UTC,It looks like a similar USB controller is part of a TI SoC:
1772165,2020-10-05 15:10:59 UTC,"So, is it still true, that QEMU doesn't support USB on Raspberry Pi?"
1772165,2019-08-19 02:56:44 UTC,Hi!
1772165,2019-07-23 08:52:51 UTC,"I think the two main things we would need would be:
 (1) a proper data sheet for the pi2/pi3 USB controller. Last time I looked there wasn't one available; it's pretty hard to model the controller properly without it. (Perhaps one has been released since I last looked.)
 (2) somebody who cares about the pi2/pi3 models and has the time to invest in writing a device model for them"
1772165,2019-07-22 20:19:32 UTC,"After reading change logs, I believe USB support for raspi2/raspi3 is not added yet. Which means host internet network can't be accessed by emulated machine."
1772165,2019-03-25 07:57:32 UTC,"On Sun, 24 Mar 2019 at 17:34, mcandre <email address hidden> wrote:

> Out of curiousity, does the raspi2 machine support a PCI bus?
"
1772165,2019-03-24 14:56:44 UTC,"Out of curiousity, does the raspi2 machine support a PCI bus? I am trying to boot Debian arm64 with qemu-system-aarch64, and am running into all manner of complaints from qemu about missing devices. Is there another machine like virt, but that offers support for boot devices?"
1772165,2018-05-22 07:43:08 UTC,"Beside rpi3 usb emulation not being there you are using the wrong argument.  bus= specifies the *guest* bus.  hostbus= can be used to specify the host bus number.  When passing through devices using vendorid and productid this should not be needed though.  Oh, and you can't pass through usb hubs, only individual devices."
1772165,2018-05-19 19:58:21 UTC,Whenever I append `console=ttyAMA0` I get kernel panic `Division by zero in kernel` and -serial stdio doen't seem to work.
1772165,2018-05-19 19:33:20 UTC,"This is for raspi3 but may be a useful reference:
https://translatedcode.wordpress.com/2018/04/25/debian-on-qemus-raspberry-pi-3-model/"
1772165,2018-05-19 19:07:29 UTC,Serial terminal doesn't work with this options. Would you provide options with which i'll be able to access and login into the terminal. SSH is also a good solution.
1772165,2018-05-19 17:49:02 UTC,Serial terminal is how I've used the raspi3 board before.
1772165,2018-05-19 17:04:37 UTC,How then should I be able to actually use the vm when there is no input?
1772165,2018-05-19 16:15:03 UTC,"Thanks. The USB controller for the raspi2/raspi3 boards is not currently modelled, so it's expected that USB devices won't work."
1772165,2018-05-19 13:53:22 UTC,"qemu-system-arm -M raspi2 -append ""rw earlyprintk loglevel=8 dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2"" -cpu arm1176 -dtb bcm2709-rpi-2-b.dtb -hda DietPi_v6.8_RPi-ARMv6-Stretch.img -kernel kernel7.img -m 1G -smp 4 -serial stdio -usb -device usb-host,bus=001,vendorid=0x1d6b,productid=0x0002"
1772165,2019-08-19 09:16:21 UTC,"Thanks for digging those up. Unfortunately just the driver sources aren't really enough information for a good device model, and the other docs are just overviews without the level of detail we need."
1772165,2018-05-19 13:43:54 UTC,Can you give the full QEMU command line you're using? (I suspect the reason for this error is that the board model you're using does not have a USB controller.)
1772169,2018-07-16 22:04:59 UTC,I think there is a bit more to this ticket. Being able to at least pan around and zoom in the schematic window while the symbol fields dialog is open would be quite helpful.
1772169,2018-06-11 00:20:45 UTC,"I'm attaching a patch which centers parts selected via clicking on the ""reference"" field in the symbol field table dialog."
1772169,2018-06-11 08:30:41 UTC,"Thank you Ben, I have just pushed a slightly modified version of your patch."
1772169,2018-06-11 08:30:33 UTC,"Fixed in revision 3f783d2318bd030e21a69a74fb946c7c6736593b
https://git.launchpad.net/kicad/patch/?id=3f783d2318bd030e21a69a74fb946c7c6736593b"
1772169,2018-06-13 01:13:43 UTC,Thanks!
1772183,2018-05-29 02:38:41 UTC,"Mike L, thank you for reporting this and helping make Ubuntu better."
1772183,2018-05-29 13:15:45 UTC,"1) The mouse model is Microsoft Sculpt Ergonomic Mouse.
2) This issue does not appear in Microsoft Windows 10, the version I have installed to my other partition. I believe from reading the comments on askububtu the bug needs a dual boot configuration to exist.
3) I don't believe I tested for this particular bug, but I noticed odd scrolling in Half Life in Steam that was only fixed by rebooting in the proper sequence. I had no clue about the depth of the bug at the time. But it definitely existed in 16.04 as well. Can't recall if it existed prior, but it wouldn't surprise me.
4) Computer is an HP envy m7-n101dx.
5) The workaround package is located here: https://sourceforge.net/projects/resetmsmice/
6) Yeah removing and reinserting the transciever fixes it until you reboot into Windows 10 again. You don't have to do it intermittently."
1772183,2018-05-29 18:01:44 UTC,Mike L:
1772183,2018-05-30 22:20:07 UTC,"1) That is correct. Only rebooting into Windows will trigger the bug when you go back into Ubuntu. I've tested this just now to confirm it.
2) OK. Will take note."
1772183,2018-05-30 23:26:02 UTC,"Mike L, to clarify, does this issue happen when using a wired USB mouse?"
1772183,2018-05-31 11:24:18 UTC,Unfortunately I do not own a wired USB mouse to test it with.
1772184,2020-03-10 18:25:27 UTC,"Since this is related: From the perspective of a controller script, SelectPlaylist can only go one item forward or backward. SelectTrackKnob can do more for faster scrolling. This should be fixed once a new implementation is done in [Library]."
1772184,2018-06-20 16:23:12 UTC,"In the case of the VMS4 where it's useful to select a specific pane, a [Library],FocusPane control would be needed, with the value being which pane to focus. E.g. 0 for the left-most pane, 1 for the one to the right of that, etc."
1772184,2018-06-20 16:18:24 UTC,"I would say replace SelectPlaylist with a [Library],SelectPane so that a -1 moves the focus one pane to the left and +1 moves it one to the right. I'm not sure if it should wrap around or not. I would have to see how the new design works to be able to decide that."
1772184,2018-05-19 17:57:23 UTC,"You cannot confirm your own bug :-P ... I can confirm, that there is something missing for the VM4.
But we should also add an alias. I am not sure how both should work in an n-pane layout."
1772189,2018-05-31 18:13:01 UTC,After a clean reinstall of 18.04 this issue still exists. I did notice something else though. The default settings are usable but they become unusable with higher pointer speeds in settings. I end up preferring disabling the acceleration and setting the pointer speed to maximum although I'd probably like even a bit more speed.
1772189,2018-06-15 10:38:16 UTC,Testing the wayland session the pointer behavior is quite different. It requires a much smaller speed setting to be usable and seems more erratic than the X one but maybe that just needs getting used to.
1772189,2019-03-01 18:06:36 UTC,"Thank you for your bug report, that's probably something that should be reported upstream on https://gitlab.freedesktop.org/libinput"
1772196,2018-05-19 18:40:14 UTC,Here are the awstats for the different endpoints (March 2018):
1772199,2019-11-27 20:25:20 UTC,"Thank you for your bug report, it looks like a corruption/download/machine problem rather than a bug in the package though"
1772203,2020-10-02 20:29:59 UTC,Looks like something crashed in the middle of the installation:
1772203,2020-12-02 04:17:19 UTC,[Expired for php7.2 (Ubuntu) because there has been no activity for 60 days.]
1772205,2020-01-30 15:43:46 UTC,I am asking about bionic packages
1772205,2018-05-23 21:05:39 UTC,I confirm that it works!
1772205,2020-01-30 15:43:15 UTC,Is the conflict between the two packages still going on?
1772205,2018-05-20 12:47:50 UTC,"ok, turns out this was filed against the debian package two years ago, by me:"
1772205,2018-05-20 10:02:19 UTC,I tried commenting the line
1772205,2018-05-20 08:06:48 UTC,"indeed, I'll comment that part of the admin conf template out.. it should start after that?"
1772205,2018-05-19 20:27:32 UTC,Changed affected package.
1772205,2018-05-23 16:17:31 UTC,fixed in git
1772206,2018-05-19 21:16:30 UTC,I have pushed a proposed fix. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/LP1772206-patron-summary-tooltips
1772206,2019-03-11 13:43:41 UTC,"I have tested this code and consent to signing off on it with my name, Terran McCanna, and my email address, <email address hidden>."
1772206,2019-05-29 14:50:47 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Garry and Terran!"
1772212,2018-05-19 22:09:52 UTC,apport information
1772212,2019-03-15 02:03:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772212,2018-05-22 01:58:39 UTC,Thanks for the screenshots.
1772212,2018-05-19 22:09:55 UTC,apport information
1772212,2018-05-19 22:09:54 UTC,apport information
1772212,2018-05-19 22:09:53 UTC,apport information
1772212,2018-05-19 22:09:52 UTC,apport information
1772212,2018-05-19 22:09:48 UTC,apport information
1772212,2018-05-19 22:09:50 UTC,apport information
1772212,2018-05-19 22:09:49 UTC,apport information
1772212,2018-05-19 22:09:48 UTC,apport information
1772212,2018-05-19 22:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1772212,2018-05-19 22:09:47 UTC,apport information
1772212,2018-05-19 22:09:45 UTC,apport information
1772212,2018-05-19 22:09:45 UTC,apport information
1772212,2018-05-19 22:09:51 UTC,apport information
1772216,2018-08-14 10:04:21 UTC,"Hello Badal.  Im not familiar with the process of how 'bugs' are
handled.        Is this an item of interest that might be worked on? would
I be advised of that-- or should I stay current by visiting a website?
thank you.  Curt"
1772216,2018-05-25 05:57:51 UTC,"Hi,"
1772216,2018-05-25 09:42:57 UTC,hello Badal. thank you for your message.   the version is: 3.17.11
1772217,2018-05-24 04:41:08 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1772224,2018-10-28 20:22:54 UTC,"Do you have fonts-liberation and fonts-wine installed.
If those don't help, what about the non-free ttf-mscorefonts-installer?"
1772224,2018-12-28 04:17:16 UTC,[Expired for wine (Ubuntu) because there has been no activity for 60 days.]
1772224,2019-02-11 07:12:58 UTC,I apologize for the delay in responding.
1772232,2018-12-10 14:26:22 UTC,"I have the sane issue ( running with Centos 7.5 and openstack Queens )
Also when changing an image which is not a snapshot I get logged out .
The fix should be in Horizon to popup a warning message for example and not log out the user ."
1772232,2018-12-25 01:41:04 UTC,"From the point of view of horizon, the menu of ""Format"" should be hidden considering the fact that it is not allowed to change the image format."
1772232,2018-06-21 14:00:40 UTC,"Change abandoned by Brian Rosmaita (<email address hidden>) on branch: master
Review: https://review.openstack.org/569635
Reason: This patch is for an invalid bug in glance."
1772232,2018-05-20 09:46:57 UTC,Code Review: https://review.openstack.org/#/c/569635
1772232,2018-06-08 01:03:15 UTC,"This is not a valid Glance bug.  Glance does not have a concept of ""logging in"", you interact with glance by presenting a token obtained from keystone as a header when you make an API call.  Glance does not log a user out.  This has to be fixed in Horizon."
1772232,2018-06-08 05:23:56 UTC,This is something that needs to be fixed in horizon IMO.
1772232,2018-05-28 04:21:31 UTC,"This is not a valid glance bug.  Once the image data is set, no one is allowed to change the disk_format, container_format, size, or checksum.  This is by design.  It is particularly the case for snapshots, where Nova knows exactly what it is dealing with and will set the disk_format and container_format correctly."
1772232,2018-05-28 11:41:40 UTC,"Hi Brian,"
1772234,2018-09-04 10:32:35 UTC,"I did a test with:
- ubuntu 18.04.1 LTS, all updates installed, kernel 4.15.0.33
  -> the screen still flickers ...
meanwhile I use a 'work around':
  ubuntu 14.04.05 LTS, kernel 3.13.0-157
  -> the screen is o.k. (NO flickering)
  BUT: that is not a real solution ..."
1772234,2019-02-09 21:12:33 UTC,"Same laptop, same problems.
Thanks for temporarily fix using xrandr ...; sleep 2; xrandr ...;
Also i have same problem with xubuntu 18.04."
1772234,2018-12-18 20:53:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772234,2018-12-19 14:08:37 UTC,"I found a ""kind of work-around"":"
1772234,2018-12-18 20:56:50 UTC,"I have an old Acer laptop with Radeon X1600
Boot screen is OK but when Desktop loads, it's totally screwed and smudged. I kinda see if I can open a window but not usable."
1772234,2018-12-19 14:14:00 UTC,"I tried an advice which I found in the internet:
  kernel-option: radeon.new_pll=0
But that results in: ... radeon: unknown parameter 'new_pll' ignored
So: my radeon-driver HAS NO new_pll option."
1772236,2018-05-20 11:14:36 UTC,"OK, it got OOM killed..."
1772236,2018-05-20 11:20:22 UTC,also: we should have been notified other than the workers shitting themselves
1772236,2018-06-08 09:12:32 UTC,"I've added delivery_mode=2 which is supposed to make the server write the messages to disk, so maybe next time we won't lose all queued requests."
1772236,2018-06-08 10:35:59 UTC,"Worth noting that we ran for many months before hitting this, and then:"
1772236,2018-06-08 10:36:54 UTC,"For autopkgtest-cloud I just cowboyed a change to add Restart=on-failure to rabbitmq-server.service. Maybe that helps us mitigate, in combination with delivery_mode=2."
1772236,2018-06-15 10:23:20 UTC,"I first thought we could log some data like:
 $ rabbitmqctl list_queues name durable owner_pid messages_ready messages_unacknowledged messages messages_ready_ram messages_unacknowledged_ram messages_ram messages_persistent message_bytes message_bytes_ram message_bytes_persistent memory state
via cron.
But then we don't know what exactly we look for yet."
1772240,2018-05-21 14:14:18 UTC,"Hi Dave,"
1772244,2018-09-01 13:15:38 UTC,This bug was fixed in the package freecol - 0.11.6+dfsg2-2
1772257,2018-05-24 09:23:28 UTC,We're past string-freeze so this will have to wait for 6.0.
1772257,2018-05-24 09:31:00 UTC,Before v4 we discussed how to handle this. We waited to create a solution until we settled on how the online manual was hosted.
1772257,2018-05-20 13:51:50 UTC,Greyed out menus don't give users the opportunity to discover /why/ they're greyed out.
1772263,2018-05-20 14:42:29 UTC,fixed in 1.1.3
1772264,2018-05-21 00:09:48 UTC,"Indeed, this problem should be fixed by the 4.13.0-1017 that's currently in -proposed on its way to -updates. The bug for the race condition should be https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1765564"
1772264,2018-05-21 00:16:11 UTC,"FYI, the ""4.13.0-38.43"" set of fixes referenced in the bug you mentioned has been in Linux-azure since 4.13.0-1013. Looking at your trace, I think the fsnotify/VFS race condition I referenced in the previous comment may be more applicable."
1772264,2018-05-21 08:07:15 UTC,"Hi,"
1772264,2018-05-23 16:36:31 UTC,"Hi,"
1772264,2018-05-23 17:01:48 UTC,"The upstream race was fixed in fsnotify was fixed in 4.13.0-1018 (linux-azure). I think it is the same issue that you are seeing, but I do not have a repro of your exact issue."
1772266,2018-06-21 06:06:37 UTC,A workaround:
1772271,2018-06-02 18:02:11 UTC,"When i use ""advanced start up options"" and use a previous non low latency load, everything stays normal.
low latency version jumps"
1772271,2018-06-02 18:10:48 UTC,"peter@peter-GeForce6100PM-M2:~$ lspci -k
00:00.0 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a1)
 Subsystem: Elitegroup Computer Systems MCP61 Memory Controller
00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
 Subsystem: Elitegroup Computer Systems MCP61 LPC Bridge
00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
 Subsystem: Elitegroup Computer Systems MCP61 SMBus
 Kernel driver in use: nForce2_smbus
 Kernel modules: i2c_nforce2
00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
 Subsystem: Elitegroup Computer Systems MCP61 Memory Controller
00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
 Subsystem: Elitegroup Computer Systems MCP61 USB 1.1 Controller
 Kernel driver in use: ohci-pci
00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
 Subsystem: Elitegroup Computer Systems MCP61 USB 2.0 Controller
 Kernel driver in use: ehci-pci
00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
 Subsystem: Elitegroup Computer Systems MCP61 High Definition Audio
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel
00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
 Subsystem: Elitegroup Computer Systems MCP61 IDE
 Kernel driver in use: pata_amd
 Kernel modules: pata_amd, pata_acpi
00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
 Subsystem: Elitegroup Computer Systems MCP61 Ethernet
 Kernel driver in use: forcedeth
 Kernel modules: forcedeth
00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
 Subsystem: Elitegroup Computer Systems MCP61 SATA Controller
 Kernel driver in use: sata_nv
 Kernel modules: sata_nv, pata_acpi
00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
 Subsystem: Elitegroup Computer Systems MCP61 SATA Controller
 Kernel driver in use: sata_nv
 Kernel modules: sata_nv, pata_acpi
00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
 Kernel driver in use: k8temp
 Kernel modules: k8temp
01:06.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 43)
 Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller
 Kernel driver in use: firewire_ohci
 Kernel modules: firewire_ohci
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450]..."
1772271,2018-06-02 18:14:12 UTC,apport information
1772271,2018-06-02 18:14:13 UTC,apport information
1772271,2018-06-04 02:03:30 UTC,Thanks.
1772271,2018-06-22 02:27:34 UTC,"I ran a bunch of configs
none of them had a very big load on the processors. gnome shell 15%pk although eyeballing it, the stable mouse conditions look a little less(?)"
1772271,2018-06-22 02:44:58 UTC,"Yes I would expect Xorg to be slightly better right now. For reasons unknown as yet, moving the mouse in a Wayland session forces the GPU to redraw everything which will slow it down and stutter more. But in Xorg sessions the mouse pointer can move freely without the GPU having to redraw anything."
1772271,2018-06-22 03:06:21 UTC,I see that my motherboard is nvidia. i am running off the radeon card. should i experiment going back to the motherboard video and see if the mouse problem is video related? the MB will be even older
1772271,2018-06-22 03:17:09 UTC,"No, it's not a hardware problem. It's a software problem (see the links in comment #10)."
1772271,2018-05-21 02:32:07 UTC,Please also:
1772271,2018-05-21 02:31:03 UTC,"We're working on a few fixes in this area:
https://trello.com/c/Q6JYXPPs"
1772277,2020-08-09 23:51:16 UTC,openbve 1.5.3.3
1772285,2020-04-10 04:17:30 UTC,[Expired for calamares (Ubuntu) because there has been no activity for 60 days.]
1772285,2018-05-20 17:57:26 UTC,"StacktraceTop:
 PartitionPage::updateButtons (this=this@entry=0x55c8af3142c0) at ./src/modules/partition/gui/PartitionPage.cpp:149
 PartitionPage::onPartitionModelReset (this=0x55c8af3142c0) at ./src/modules/partition/gui/PartitionPage.cpp:423
 QObject::event (this=this@entry=0x55c8af3142c0, e=e@entry=0x7ff44c02f960) at kernel/qobject.cpp:1247
 QWidget::event (this=0x55c8af3142c0, event=0x7ff44c02f960) at kernel/qwidget.cpp:9346
 QApplicationPrivate::notify_helper (this=this@entry=0x55c8aef85420, receiver=receiver@entry=0x55c8af3142c0, e=e@entry=0x7ff44c02f960) at kernel/qapplication.cpp:3722"
1772285,2020-02-09 22:02:59 UTC,"Unfortunately without clear steps to reproduce this will be a difficult bug to fix. Furthermore, Lubuntu 18.10 is no longer supported. I would suggest trying again in 19.10. Perhaps try setting up the same partition scheme with 18.04 on it and see what happens. If you can't reproduce it, perhaps it was merely a fluke."
1772289,2018-08-15 17:41:20 UTC,"There is a second scrollbar on the right though. I assume that a scrollbar is added to the inner window widget based on a dynamic policy, and it is shown in this case due to the length of the icon list."
1772290,2018-05-20 19:08:38 UTC,"This application has raised an unexpected
error and must abort."
1772290,2018-07-03 22:18:31 UTC,"Hi,"
1772303,2018-05-20 21:18:26 UTC,That's correct and needs to be changed.
1772314,2018-11-14 17:02:47 UTC,Isn't this against os-prober? It was on openSUSE.
1772314,2018-05-21 22:53:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772314,2018-05-20 21:35:04 UTC,"Same here!
And can confirm ""This happens every time a new Ubuntu system is added to a PC with Arch Linux."""
1772314,2018-06-08 19:36:32 UTC,This is easily verifiable. Have Arch Linux installed and add any Ubuntu version to your system. Take a look at the /etc/boot/grub.cfg file. You will see that /initramfs-linux.img is missing and also you will not be able to boot into Arch. The only way to boot Arch is via the fallback kernel.
1772325,2019-07-26 07:40:12 UTC,Submitted a related bugreport for fixing this in Parole: https://bugzilla.xfce.org/show_bug.cgi?id=15747
1772325,2019-07-26 07:10:25 UTC,Eyal Soha referenced this bugreport in commit 46f429282fc852ab8639e8af9aca6c96b8b96bda
1772325,2019-07-26 07:08:41 UTC,"Thanks for the clarification - that's exactly what I expected. So Chrome/Chromium inhibits power management, not just the screensaver, therefore the dimming doesn't occur."
1772325,2019-07-26 02:21:01 UTC,"Sure.  It works for me.  I patched in the code that I attached, ran make, then I copied the new xfce4-power-manager into /usr/bin as root."
1772325,2019-07-24 22:22:46 UTC,I finally got around to testing the patch and it doesn't work for me for some reason. While having screensaver inhibition enabled in both VLC and Parole I still got screen dimming.
1772325,2019-07-23 21:02:14 UTC,"The patch looks ok. The only thing to keep in mind is that this doesn't just change the behavior of screen dimming but also of suspend-on-inactivity, which is configured in the ""System"" tab.
So if you configure your laptop/PC to suspend after 30mins of idletime it will in this case also *not* suspend if something - e.g. a video - inhibits it."
1772325,2019-06-04 03:13:48 UTC,"Created attachment 8612
Patch to fix the bug"
1772325,2018-08-18 12:33:24 UTC,Does that only happen with VLC?
1772325,2018-09-08 11:57:16 UTC,I filed a bug report on the XFCE bug tracker:
1772325,2018-09-08 11:54:24 UTC,"While playing back a video file in either VLC or Parole, my laptop screen will dim to a lower brightness level. The screen does not go blank, so the other power management functions are correctly inhibited."
1772325,2018-08-21 23:10:44 UTC,"Thanks for the help, I'll look into this."
1772325,2018-08-20 00:27:30 UTC,"Sadly, that does not tell us much. The power manager does the screen dimming, but it should not in this scenario."
1772325,2018-08-19 13:59:26 UTC,Here it is. Near the end of the log is where the display dimmed.
1772325,2018-08-18 22:39:35 UTC,Okay. I guess it is worth to check the power manager debug output then:
1772325,2018-08-18 21:34:47 UTC,"No, I just checked using Parole and it still dimmed."
1772325,2018-09-09 09:08:25 UTC,Thanks.
1772326,2018-05-20 22:52:11 UTC,"As an example, here's how our discovery layer does it: https://github.com/lbcclib/findit_data_tools/blob/master/lib/traject/eg_authorities.config.rb"
1772326,2020-07-22 17:55:53 UTC,"Jane, This is what I would like to happen."
1772328,2018-05-21 21:27:35 UTC,Please make a bug report upstream to the Mate team on GitHub and link here that report. Have a nice day and thank you for your time.
1772328,2018-05-22 20:30:30 UTC,"Ok, opened issue here https://github.com/mate-desktop/mate-desktop/issues/318"
1772331,2020-03-07 15:46:03 UTC,"Hi, thanks for reporting this bug. As part of the bug migration (https://alpha.inkscape.org/bug-migration/), I'm closing this issue. Its been re-reported in https://gitlab.com/inkscape/inkscape/-/issues/1099 (and you can track the issue there)."
1772331,2018-07-01 10:10:08 UTC,"Hi Phiscribe,"
1772331,2018-07-01 15:51:51 UTC,Setting it to Don't save window geometry seems to general result in a non-native svg file opening not offscreen but with Inkscape taking up part of both monitors.
1772331,2018-11-30 05:16:07 UTC,"I have the same problem with a multi-monitor setup in Windows 10. SVG graphics double-clicked via Windows Explorer open partly off-screen, such that the caption bar of the window is invisible and it becomes difficult to move the window. I have ""Don't save window geometry"" selected, because otherwise it becomes even more unwieldy."
1772334,2018-05-21 01:19:14 UTC,"Just downgraded to Inkscape 0.92.2 (5c3e80d, 2017-08-06), and same thing.  The Text and Font dialog does not open.  Not sure what to do now."
1772334,2020-01-25 17:09:27 UTC,"Hi, we're tracking this issue over at Gitlab in this ticket: https://gitlab.com/inkscape/inbox/issues/1149"
1772334,2018-05-22 00:27:17 UTC,"For some reason the window was off-screen.  I found in Microsoft Spy++ that is was being displayed, with the following details:
Rectangle:     (2376, -852)-(2772, -356) 396x496
Restored Rect: (2376, -852)-(2772, -356) 396x496
Client Rect:   (8, 31)-(388, 488), 380x457"
1772334,2018-05-22 01:51:21 UTC,Same issue -- same solution -- with the Document Properties window...
1772334,2018-05-26 22:24:04 UTC,"(offtopic: wow, three screens - are you using Inkscape on multiple of those?)"
1772335,2018-05-22 07:34:28 UTC,"Intersting idea.
Here the theory in detail:
https://www.phon.ucl.ac.uk/courses/spsci/iss/week5.php
I think we need two frequency knobs, a high and low bypass knob a gain and q-knob."
1772335,2018-05-22 07:54:13 UTC,https://ccrma.stanford.edu/~jos/fp/Formant_Filtering_Example.html
1772338,2018-08-18 01:26:45 UTC,"That tag comes from src/unity-appinfo-manager.vala so a code change is required:
https://code.launchpad.net/~robert-ancell/libunity/update-deprecation-tags/+merge/353363"
1772342,2018-05-21 10:53:18 UTC,"reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
using the attached svg file."
1772342,2019-12-11 05:43:27 UTC,"Hhmm....I'm unable to test since I don't have Synfig.  Just to make sure someone has a look at it who can test, I will migrate."
1772342,2018-05-21 03:02:31 UTC,"Just to make it more convenient for developers, I'll try and get the basic info posted and uploaded here."
1772348,2018-05-21 03:08:16 UTC,Correction:  ...I had the same problem with Ubuntu 17.10...
1772348,2018-05-21 03:13:10 UTC,"This should probably be added to Bug# 1728012 (""Many 3rd party scanner drivers are broken by a sane change"")Many scanners Many scanners"
1772348,2018-08-31 18:06:27 UTC,"I installed Cosmic HPLIP 3.18.7 packages, including libsane-hpaio, and this solved the problem I had with using M1212nf on Ubuntu Bionic"
1772348,2018-08-31 18:06:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772348,2019-07-04 16:08:57 UTC,Issue about to be fixed in 18.04.
1772352,2018-05-21 06:11:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/569708"
1772361,2018-05-31 02:53:25 UTC,code merged and cherry-picked.
1772362,2018-07-08 08:45:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772362,2018-07-23 02:22:37 UTC,"Looks like this might be related to:
https://errors.ubuntu.com/problem/8430bef5a910ea168b679d422884132621749535
https://errors.ubuntu.com/problem/ec835994b9b9db7238062bd236b0af32bd75792f"
1772362,2018-07-23 07:27:34 UTC,"Thanks Daniel for looking into this!
Here is how I came into this bug:"
1772364,2018-05-21 14:04:35 UTC,It is another way to implement
1772366,2018-05-21 18:03:06 UTC,apport information
1772366,2018-05-21 18:03:05 UTC,apport information
1772366,2018-05-21 18:03:03 UTC,apport information
1772366,2018-05-21 18:02:59 UTC,apport information
1772366,2018-05-21 18:02:58 UTC,apport information
1772366,2018-05-21 18:02:57 UTC,apport information
1772366,2018-05-21 18:02:56 UTC,apport information
1772366,2018-05-21 18:03:02 UTC,apport information
1772366,2018-05-21 18:02:54 UTC,apport information
1772366,2018-05-21 18:02:55 UTC,apport information
1772366,2018-05-21 18:02:42 UTC,apport information
1772366,2018-05-21 18:02:43 UTC,apport information
1772366,2018-05-21 18:02:44 UTC,apport information
1772366,2018-05-21 18:03:00 UTC,apport information
1772366,2018-05-21 18:02:49 UTC,apport information
1772366,2018-05-21 18:02:50 UTC,apport information
1772366,2018-05-21 18:02:52 UTC,apport information
1772366,2018-05-21 18:02:52 UTC,apport information
1772366,2018-05-21 18:02:48 UTC,apport information
1772379,2020-04-07 22:08:36 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1772381,2018-05-21 14:48:08 UTC,"Or, could Juju close all client connections after upgrading? That might be a lot simpler."
1772381,2018-05-22 21:13:55 UTC,I agree with Casey. Simply closing all non-controller connections would be much simpler.
1772392,2018-05-26 15:46:37 UTC,I did a first implementation of this issue to add status popups to segments and circles.
1772392,2018-05-26 15:54:57 UTC,Known issues of this patches:
1772392,2018-10-13 15:07:17 UTC,I rebased the branch to the current master and fixed a little bug which was exposed by this patchset.
1772393,2018-05-31 19:13:47 UTC, The fix mentioned in the previous comment has been merged for the stable/queens release.
1772393,2018-05-31 17:01:58 UTC,This problem is being addressed by this change (out for review):
1772395,2018-05-31 13:28:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772395,2020-08-09 23:40:44 UTC,pdfsam-basic (3.3.5-1)
1772405,2018-05-21 14:12:34 UTC,"Fedora doesn't enable systemd-resolved, which is probably why this hasn't been hit before. It was proposed but apparently shot down."
1772405,2018-05-23 16:42:11 UTC,"maybe I can modify ipa-server-install to disable systemd-resolved, but it feels fragile and I wish there was a way to make them work together..."
1772405,2018-08-23 21:12:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772411,2020-02-26 10:16:34 UTC,closing as fixed
1772411,2018-05-21 14:09:07 UTC,wrong package
1772411,2019-03-10 13:39:21 UTC,"This is a duplicate of #859419[1], fixed in 2.1.3-1."
1772419,2018-05-21 15:03:41 UTC,"En fait c'est la taille d'affichage qui change et masque la barre de navigation.
En ""glissant"" vers la droite ou en dézoomant je retrouve le menu"
1772419,2018-05-28 05:08:48 UTC,Même souci avec la page installation
1772423,2018-08-22 09:54:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772426,2021-02-15 17:19:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772426,2021-02-15 17:20:56 UTC,When u copy a large file from google drive it. It takes huge sapace in ram. May be the size of file. Like when u copy 6 gb file or more your device will be freeze. unitll you kill it.
1772428,2018-07-27 05:32:02 UTC,Any update?
1772430,2019-09-18 06:28:11 UTC,*** Bug 127556 has been marked as a duplicate of this bug. ***
1772430,2019-09-12 12:30:04 UTC,Still reproducible on:
1772430,2019-09-02 09:26:08 UTC,"Dear bugzilla,"
1772430,2018-08-29 12:56:41 UTC,This has been reported in Ubuntu (https://launchpad.net/bugs/1772430) and I can reliably reproduce the issue with 6.0.6 and 6.1.0.
1772430,2018-08-29 12:54:45 UTC,"Nevermind, that's a known (and old) issue: https://bugs.documentfoundation.org/show_bug.cgi?id=103099"
1772430,2018-08-29 12:53:31 UTC,"Sorry for the lack of feedback until now, Miikka.
I can reliably reproduce the issue with libreoffice 6.0.6 on Ubuntu 18.10 and libreoffice 6.1.0.3 installed as a snap."
1772430,2017-11-07 21:22:05 UTC,Still repro.
1772430,2018-05-21 15:23:01 UTC,Another screenshot showing a crammed-up line at page break (no paragraph break).
1772430,2017-10-25 08:58:02 UTC,** Please read this message in its entirety before responding **
1772430,2016-10-24 12:06:33 UTC,"Btw. in LibO 3.5 all the rows are smashed together, even a bit more than the 1st and 2nd line in newer versions."
1772430,2016-10-24 12:04:37 UTC,"Created attachment 128204
Test file with Dejavu Sans"
1772430,2016-10-24 12:02:30 UTC,"Created attachment 128203
Screenshot of Dejavu Sans 57% proportional line spacing"
1772430,2016-10-10 21:04:27 UTC,"Description:
When Paragraph style - line spacing - proportional  is set to value smaller than 100%, the spacing between first and the second line in the paragraph is wrong, it is too small. The second line ends up being too close to the first line. It looks very odd."
1772430,2018-05-21 15:25:02 UTC,This is the document which was used to create the screenshots.
1772432,2019-01-14 09:58:06 UTC,J'ai trouvé par hasard une autre manière de reproduire le problème  en éditant une sous-section d'une page. Juste après l'enregistrement le problème est là.
1772432,2018-05-29 18:14:03 UTC,Autre souci que j'ai constaté et confirmé par ?? sur le forum (cf : https://forum.ubuntu-fr.org/viewtopic.php?pid=21923956#p21923956)
1772432,2018-11-08 13:10:46 UTC,"Hello,"
1772432,2018-05-28 05:06:38 UTC,"Le phénomène n'apparait pas en haut de page. Dans ce cas, le texte est décalé pour être bien visible."
1772433,2018-05-30 13:07:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571200"
1772433,2018-05-30 13:50:28 UTC,"Change abandoned by Bharat Kunwar (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/570937"
1772434,2018-05-21 15:23:00 UTC,"Also we have posted some patches to the upstream community and they are yet to be accepted by the upstream,"
1772434,2018-05-21 15:23:38 UTC,Currently we are waiting on the commit IDs for the patches listed in comment #1
1772434,2018-05-31 15:56:40 UTC,Adding commit IDs for patches referenced above:
1772434,2018-06-18 18:54:03 UTC,I built a Bionic test kernel with the requested 37 patches.
1772434,2018-08-20 05:01:22 UTC,"Can you guys share the release plans for kernel-4.15.0-33.36?
We have a installation/boot failure with HBA330 and the patches in this list are fixing it."
1772434,2018-08-21 16:05:49 UTC,"Hi Sujith,"
1772435,2019-05-16 22:59:27 UTC,"One of the libraries in our consortium just let me know that the Quick Receive is not useful for them, since they have some missing issues (due to a change in subscription manager), and they don't claim missing issues in Evergreen.  So, the quick receive always defaults to one of those missing issues from long ago.  It would be more helpful if it defaulted to the next issue after the most recently received issue."
1772436,2018-06-28 13:49:02 UTC,Is this work being tracked in another launchpad?
1772436,2018-05-21 15:25:27 UTC,Below are upstream commit ids of MR driver which went in after driver version- 07.703.05.00-rc1 (inbox driver of Ubuntu18.04)-
1772436,2018-05-21 15:25:37 UTC,Out of above patches below these patches are the ones which are not specific to MR only but many  drivers are modified(to use new kernel APIs in place of older APIs) and megaraid_sas is one of those drivers-
1772436,2018-06-28 13:48:35 UTC,"@Michael_Reed,
If these patches are not backported in time for the .1 iso... it becomes a huge problem because these patches are required for install."
1772439,2018-09-23 15:50:15 UTC,Repro. Can only successfully search with individual glyphs in PDF
1772439,2019-09-24 03:09:47 UTC,"Dear vaaydayaasra,"
1772439,2019-10-07 15:55:37 UTC,Still reproducible on:
1772439,2018-08-30 12:27:14 UTC,I filed an upstream report at https://bugs.documentfoundation.org/show_bug.cgi?id=119606
1772439,2018-08-30 12:25:49 UTC,"Description:
Creating a PDF from a document written in the Arabic script deforms the textual content of the document, although it looks fine on the screen."
1772439,2018-08-30 11:15:33 UTC,"Thanks for the confirmation Miikka. Confirming the bug, based on what I observe and your feedback."
1772439,2018-08-30 12:26:47 UTC,"Created attachment 144554
PDF created with LO 5.4.6.2 where textual content is garbled"
1772439,2018-08-29 16:14:43 UTC,"Sorry for the lack of feedback until now, Miikka."
1772439,2018-08-29 16:20:52 UTC,"I'm seeing different results than what you describe when testing on Ubuntu 18.04 with libreoffice 6.0.3, although it doesn't seem to behave exactly as you would expect, either. Can you test on 18.04 and share here whether the situation is any better?"
1772439,2018-08-30 10:44:17 UTC,I tested the same example sentence with Ubuntu 18.04 and LibreOffice 6.0.3.2. Here’s the output from pdftotext:
1772443,2020-10-19 21:04:34 UTC,"Hi,"
1772445,2020-02-20 13:25:06 UTC,"Repro 7.0+.
Seems that RTL text in table doesn't go RTL. I guess another bug that should be in See Also."
1772445,2019-10-07 15:58:45 UTC,Still reproducible on:
1772445,2019-09-24 03:10:46 UTC,"Dear vaaydayaasra,"
1772445,2018-09-23 15:40:27 UTC,Repro.
1772445,2018-08-30 11:09:48 UTC,I filed an upstream report at https://bugs.documentfoundation.org/show_bug.cgi?id=119604
1772445,2018-08-30 11:08:44 UTC,"Created attachment 144552
ODT document used to create the screenshot"
1772445,2018-08-30 11:08:02 UTC,"Created attachment 144551
Screenshot of a LTR and a RTL table which both have rotated text"
1772445,2018-08-30 11:05:40 UTC,"Description:
Text can normally be rotated either 90 or 270 degrees through the Character > Position dialog box. This works even in tables, but only if the table’s text direction is set to Left-to-right. If the table’s text direction is set to Right-to-left through the Table properties dialog, no rotation takes effect. See the screenshot of a document, where there are two identical tables, one marked as LTR and the other as RTL. Text is rotated as expected in the LTR table, while nothing seems to happen in the other one."
1772445,2018-08-30 10:32:32 UTC,"Sorry for the lack of feedback until now, Miikka.
I can reliably reproduce the issue with libreoffice 6.0.3.2 on Ubuntu 18.04 and libreoffice 6.1.0.3 installed as a snap."
1772445,2018-05-21 16:23:11 UTC,The ODT document used to create the screenshot.
1772447,2019-03-18 11:05:09 UTC,"Hi everybody,"
1772447,2018-10-26 10:44:52 UTC,"Sorry about that, I uploaded a backport which doesn't work, but I fixed that now with another backport which should be SRU'able to bionic, I hope. It's the same version as in cosmic, should be built soon."
1772447,2018-10-24 12:34:26 UTC,@tjaalton What happened to 4.7.0~pre2-0~ppa3 in the staging PPA?
1772447,2018-10-03 00:49:41 UTC,This bug was fixed in the package freeipa - 4.7.0-1ubuntu4
1772447,2018-09-09 14:27:11 UTC,"Since not everyone knows about the staging PPA (I just found it),
the PPA can be found here:
  https://launchpad.net/~freeipa/+archive/ubuntu/staging"
1772447,2018-05-23 16:25:01 UTC,fixed in git
1772447,2018-09-08 16:06:39 UTC,Sorry for the duplicate in https://bugs.launchpad.net/bugs/1791325. I should have paid more attention.
1772447,2018-05-23 21:03:46 UTC,Confirming that it works!
1772447,2018-05-21 19:00:09 UTC,"ok, it's rpcserver.py.. probably need to put these in /var/lib/ipa/certs"
1772447,2018-05-21 18:49:20 UTC,"that's not referenced in any apache config at least, so not sure why it wouldn't work"
1772447,2018-09-09 13:08:48 UTC,Side note for Timo. There is no tag in the git repo for debian/4.7.0~pre1+git20180411-2 (commit fb666595)
1772457,2018-08-27 23:43:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772457,2019-05-02 12:32:41 UTC,"fwiw, this should be fixed in more modern releases of GnuPG.  I believe this is related to 2.1.11 (in xenial) only."
1772459,2018-05-21 17:23:53 UTC,The ODT document used to create the screenshot.
1772462,2018-05-21 19:34:18 UTC,Might be a duplicate of 1753800 or the other importer bugs related to the importer branch Robie has to review.
1772462,2018-05-24 10:43:21 UTC,Publishing events:
1772462,2020-09-28 12:01:40 UTC,Fix released in git-ubuntu version 1.0
1772465,2019-04-08 20:11:32 UTC,*** Bug 124222 has been marked as a duplicate of this bug. ***
1772465,2018-08-30 10:16:14 UTC,"Sorry for the lack of feedback until now, Miikka.
I can reliably reproduce the issue with libreoffice 6.0.3.2 on Ubuntu 18.04 and libreoffice 6.1.0.3 installed as a snap."
1772465,2018-07-06 13:10:23 UTC,*** Bug 116005 has been marked as a duplicate of this bug. ***
1772465,2016-10-28 18:45:35 UTC,*** Bug 60051 has been marked as a duplicate of this bug. ***
1772465,2016-10-07 07:41:03 UTC,"I can reproduce on LibreOffice 5.3.0.0.alpha0 32 bit
Build ID: 33c57f15501dbd05834cd8844e9124b06536e62c
Windows 10 Ent, 64 bit"
1772465,2016-01-19 16:26:50 UTC,I apologize for my unhelpful comment.
1772465,2021-01-23 17:21:49 UTC,"I can still reproduce this in
Version: 7.0.1.2 (x64)
Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452
on Windows 10"
1772465,2016-01-19 16:13:04 UTC,"(In reply to Jonatham E. Snow from comment #9)

> Confirmed. Gentoo Linux
>
> This is a STUPID bug because it faces directly toward the user and does
> something illogical, that is: Undo should UNDO including resetting the
> current formatting settings, style etc back to what they were. This kind of
> bug, rather than being a special case rarely seen by anybody, is a symptom
> of the larger kind of fit and finish problems that plague LO and FOSS
> generally.
"
1772465,2016-01-19 12:48:30 UTC,Confirmed. Gentoo Linux
1772465,2015-01-07 21:10:59 UTC,"In order to be objective we use the priority/severity. You agreed there is a workaround - this means it does not PREVENT high quality work, it may slow it down though - of course it can be very annoying to workaround the problem."
1772465,2016-01-17 20:01:56 UTC,** Please read this message in its entirety before responding **
1772465,2015-01-06 07:53:13 UTC,Confirmed.
1772465,2013-03-07 17:27:36 UTC,Changing priority:
1772465,2013-03-07 17:22:32 UTC,*** Bug 61926 has been marked as a duplicate of this bug. ***
1772465,2012-06-05 10:34:40 UTC,This is still an open Problem. Reproduced in 3.5.4.2 on Windows XP 32 bit
1772465,2011-12-23 12:01:25 UTC,"[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1"
1772465,2011-05-08 02:50:51 UTC,Example:
1772465,2016-01-18 09:03:43 UTC,"Confirmed for Version: 5.0.4.2
Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78
OS: Windows 7 Pro SP1 (64 Bit)"
1772467,2018-05-21 19:33:59 UTC,apport information
1772467,2018-05-21 19:34:01 UTC,apport information
1772467,2018-05-21 20:26:11 UTC,"Can you see if this bug exists in the latest upstream 4.15 kernel?  It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/"
1772467,2018-05-22 06:21:50 UTC,apport information
1772467,2018-05-22 06:27:16 UTC,The latest upstream 4.15.18 kernel solves stability. I can now finish downloads with git fetch. But download speed still is very slow.
1772467,2018-09-04 17:47:13 UTC,Tested with the 4.15.0-34-generic kernel from -proposed and this also solves the issue for me.
1772467,2018-08-28 17:01:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1772467,2018-08-31 19:49:04 UTC,Tested with kernel 4.15.0-34-generic and for me this kernel solves this bug. Thank you!
1772467,2018-09-10 17:53:06 UTC,This bug was fixed in the package linux - 4.15.0-34.37
1772467,2018-05-21 19:33:58 UTC,apport information
1772467,2018-08-16 13:08:48 UTC,With the upstream kernel 4.16.18-041618 everything works fine for me. Looks like this is this patch might help: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/commit/drivers/net/wireless/intel?id=998ce0330c94eca4b13b8f062b3f0ca9ef9ad6d8
1772467,2018-05-21 19:33:57 UTC,apport information
1772467,2018-05-21 19:33:52 UTC,apport information
1772467,2018-05-21 19:33:55 UTC,apport information
1772467,2018-05-21 18:45:17 UTC,Changing target package to linux instead of linux-firmware as problem is fixed by newer kernel.
1772467,2018-05-21 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1772467,2018-05-21 19:33:22 UTC,apport information
1772467,2018-05-21 19:33:23 UTC,apport information
1772467,2018-05-21 19:33:24 UTC,apport information
1772467,2018-05-21 19:33:56 UTC,apport information
1772467,2018-05-21 19:33:51 UTC,apport information
1772467,2018-05-21 19:33:51 UTC,apport information
1772467,2018-05-21 19:33:54 UTC,apport information
1772467,2018-05-21 19:33:25 UTC,apport information
1772469,2018-05-30 16:19:27 UTC,"I can observe the issue with calc 6.0.3.2 on bionic.
That looks like an upstream bug report to me, would you mind filing one at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice and sharing the link here? Thanks!"
1772469,2018-05-30 17:08:07 UTC,I filed the bug upstream at https://bugs.documentfoundation.org/show_bug.cgi?id=117908
1772469,2018-05-30 19:40:47 UTC,Thanks!
1772471,2018-09-19 08:56:47 UTC,"@mudinlove, this might be a different issue, please open a new bug."
1772471,2018-09-19 06:48:11 UTC,"I still got similar issue when run CDDA:
---------------
./cataclysm-launcher
dbus[6581]: arguments to dbus_message_new_method_call() were incorrect, assertion ""path != NULL"" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library."
1772471,2018-07-04 15:42:52 UTC,"I'd prefer to see a verification report that includes the package version string tested as requested before releasing to Artful please, especially since there are multiple versions and an override involved here, and people upgrading between them, which I think makes an error in what I'm releasing vs. what was tested more likely."
1772471,2018-07-03 06:58:49 UTC,"The verification of the Stable Release Update for libsdl2 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1772471,2018-07-03 06:58:44 UTC,This bug was fixed in the package libsdl2 - 2.0.8+dfsg1-1ubuntu1.18.04.1
1772471,2018-06-27 06:26:55 UTC,"I switched the main system to bionic, but forgot to update the bug"
1772471,2018-06-28 07:32:04 UTC,Could you please check and write here which versions of libsdl2 have been used during testing?
1772471,2018-05-24 10:31:25 UTC,"Hello Ryan, or anyone else affected,"
1772471,2018-05-24 10:29:49 UTC,"Hello Ryan, or anyone else affected,"
1772471,2018-05-22 16:50:56 UTC,This bug was fixed in the package libsdl2 - 2.0.8+dfsg1-1ubuntu2
1772471,2018-05-22 07:26:37 UTC,"Hello Ryan, I committed the fix in cosmic, will update artful/bionic once it goes in release."
1772471,2018-06-27 00:43:13 UTC,Is this also verification-done for bionic? We can't release the artful update until the bionic update is also ready (to avoid regressions when people update from artful to bionic).
1772471,2018-06-22 13:06:55 UTC,I'm using it correctly
1772486,2018-05-22 16:21:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772488,2018-05-30 22:38:38 UTC,I'm fairly certain the dialog comes up before all the information has been gathered so apport doesn't yet know that the package is from an unofficial repository.
1772497,2018-05-21 20:14:32 UTC,Here's the output from lsb_release and apt-cache policy:
1772497,2019-01-16 14:14:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772512,2019-08-14 07:01:22 UTC,"ugemkow, yavn, please test this on bionic, it's been available for almost five months now"
1772512,2019-10-21 14:49:23 UTC,"The verification of the Stable Release Update for libxkbcommon has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1772512,2019-10-21 14:49:16 UTC,This bug was fixed in the package libxkbcommon - 0.8.2-1~ubuntu18.04.1
1772512,2019-10-21 07:49:20 UTC,verified myself
1772512,2019-09-30 08:08:58 UTC,https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/comments/6
1772512,2019-09-28 09:48:22 UTC,"hi guys, on ubuntu bionic 18.04 amd64 I still can't install libsdl2-dev:i386 and libsdl2-dev:amd64 because of that libxkbcommon-dev:i386 and libxkbcommon-dev:amd64 can't coexist. Is there any progress so far?"
1772512,2019-06-11 05:10:29 UTC,"use another method to install, it's there"
1772512,2019-03-22 09:40:07 UTC,"Hello Maciej, or anyone else affected,"
1772512,2019-03-05 20:46:27 UTC,"There was another upload with just security fixes which conflicted with the backport, but this is all sorted now and the backport is now on the queue and should be processed reviewed soon."
1772512,2019-01-04 16:37:05 UTC,Is there any progress? This bug (and #1784135) prevents Bionic to be usable even for simple multi-arch development work because important dev-libs can not be installed.
1772512,2018-10-17 12:42:31 UTC,"An upload of libxkbcommon to bionic-proposed has been rejected from the upload queue for the following reason: ""Please use the security pocket/process or else explain why this is using the SRU process over the security process in the SRU information provided in the bug.""."
1772512,2018-09-27 07:37:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772512,2018-06-07 04:10:34 UTC,This bug was fixed in the package libxkbcommon - 0.8.0-2
1772512,2019-03-26 15:48:42 UTC,"Hi. It's probably me, but I can't find this proposed package. apt list --upgradeable lists only libxkbcommon0/bionic-proposed, but I can't install even that with apt install libxkbcommon0/bionic-proposed. It says the release 'bionic-proposed' doesn't exist for this package. The package libxkbcommon-dev is not visible at all."
1772520,2019-09-11 04:37:58 UTC,"Dear vaaydayaasra,"
1772520,2018-09-10 17:00:24 UTC,Repro with Scheherazade font. Freesans is fine.
1772520,2018-08-18 15:32:38 UTC,I filed an upstream bug report at https://bugs.documentfoundation.org/show_bug.cgi?id=119347
1772520,2018-08-18 15:30:54 UTC,"Created attachment 144271
Screenshot of Calc which shows correct behavior"
1772520,2018-08-18 15:29:59 UTC,"Created attachment 144270
Screenshot of Writer document view which displays incorrect behavior"
1772520,2018-08-18 15:28:52 UTC,"Description:
In most fonts, many characters in the Arabic script change their width and height as typing progresses. For example the letter ب (U+0628) is reduced to about a half or even a third of its width if it's followed by another character such as ا (U+0627): با. Usually LibreOffice understands the changes in font metrics pretty well but not always."
1772520,2019-09-12 12:39:29 UTC,Still reproducible on:
1772520,2018-05-30 16:07:25 UTC,"@Olivier, no, the upstream bug you mentioned is different. In the example I posted, there are no diacritics (problem number 1 in the upstream report), and visually the text looks fine with no undesirable kerning or spaces (problem number 3 in the report). It's just selection which misbehaves; the rendering of the text looks good."
1772520,2018-05-30 15:45:22 UTC,"I can reliably reproduce the issue in a bionic VM with libreoffice 6.0.3.2. The font package is fonts-sil-scheherazade. Only writer is affected, the selection behaves as expected in calc."
1772520,2018-05-30 15:41:01 UTC,"@Miikka-Markus, would you mind confirming that upstream bug, if you think that matches/includes your issue?"
1772520,2018-05-30 15:38:37 UTC,Possibly linked to https://bugs.documentfoundation.org/show_bug.cgi?id=115113 ?
1772520,2018-05-21 21:30:43 UTC,"Screenshot of selecting the same characters in Calc, which shows the expected behavior."
1772520,2018-08-16 17:18:59 UTC,"Sorry for the lack of feedback until now, Miikka."
1772535,2018-05-23 01:39:02 UTC,to compile with CGAL 4.11 we have to use
1772536,2018-05-29 17:28:25 UTC,Where? The links seem to work for me.
1772536,2018-05-29 17:48:44 UTC,Link works it's the test on the link that's off
1772536,2018-05-30 19:43:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571289"
1772537,2020-04-27 10:32:32 UTC,The issue was fixed upstream with that commit
1772537,2018-05-25 11:56:58 UTC,I filed the report upstream at: https://bugs.freedesktop.org/show_bug.cgi?id=106649
1772537,2018-05-23 10:53:58 UTC,please file upstream:
1772537,2018-05-23 11:23:22 UTC,"""Lib/Xlib (data)"" that is"
1772542,2018-07-30 00:32:25 UTC,"guiverc@d960-ubu2:~$   lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu Cosmic Cuttlefish (development branch)
Release:	18.10
Codename:	cosmic"
1772542,2018-08-01 01:27:09 UTC,"Chris Guiver, you may need to use:
sudo ubuntu-bug /var/crash/FILENAME.crash"
1772542,2018-09-18 10:47:11 UTC,"This may be significant, may be a red herring..."
1772542,2020-10-22 05:46:45 UTC,hi I am also facing GPU lockup while playing videos in loop
1772542,2018-08-01 00:49:53 UTC,"fyi: looking at the wiki,
/etc/gdm3/custom.conf now has Enable=true  (it was commented out sorry)"
1772542,2018-08-01 00:00:42 UTC,"guiverc@d960-ubu2:/var/crash$   ls -la
total 64408
drwxrwsrwt  3 root    whoopsie     4096 Aug  1 08:32 .
drwxr-xr-x 15 root    root         4096 Nov 16  2017 ..
drwxrwsr-x  2 guiverc whoopsie     4096 Jul 30 09:19 2018-05-22
-rw-r-----  1 guiverc whoopsie    70917 Jul 30 08:28 _usr_bin_caffeine.1000.crash
-rw-r-----  1 guiverc whoopsie 44980186 Jul 30 08:29 _usr_bin_vlc.1000.crash
-rw-r-----  1 guiverc whoopsie 20876029 Aug  1 08:28 _usr_lib_xorg_Xorg.1000.crash"
1772542,2018-07-31 23:31:19 UTC,Chris Guiver:
1772542,2018-07-31 22:47:58 UTC,"today's crash
-rw-r----- 1 guiverc whoopsie  20M Aug  1 08:28 _usr_lib_xorg_Xorg.1000.crash
// this has was reported (ubuntu-bug)"
1772542,2018-07-30 02:32:37 UTC,"guiverc@d960-ubu2:~$ sudo cat /var/lib/whoopsie/whoopsie-id
[sudo] password for guiverc:"
1772542,2018-07-30 01:51:38 UTC,Chris Guiver:
1772542,2018-07-24 02:54:44 UTC,just an FYI.
1772542,2018-09-11 04:00:06 UTC,This change was made by a bot.
1772542,2018-06-06 01:44:07 UTC,"Chris Guiver, to confirm a WORKAROUND, if you uninstall both light-locker and caffeine simultaneously, is a crash still reproducible?"
1772542,2018-06-20 02:19:47 UTC,It's now quite a few sleep sessions since I `sudo apt remove light-locker caffeine`
1772542,2018-05-22 03:00:46 UTC,attached dmesg ( dmesg >~/dmesg_2018-05-22.txt )
1772542,2018-05-25 05:41:07 UTC,Thanks Christopher (penalvch) for reply
1772542,2018-05-25 17:50:40 UTC,Chris Guiver:
1772542,2018-05-25 23:08:48 UTC,1) understood (I'd guessed that)
1772542,2018-05-24 23:43:56 UTC,"Chris Guiver, thank you for reporting this and helping make Ubuntu better. Please respond to all of the following:"
1772542,2018-05-30 00:20:05 UTC,no crash report numbers
1772542,2018-05-30 03:21:53 UTC,Chris Guiver:
1772542,2018-05-30 05:46:31 UTC,The time of the Xorg crash file is ~correct for the crash that logged me out (between 1st & 2nd line in my syslog snippet).  I was using XFCE or Xubuntu-session login (this issue only ever happened with XFCE/Xubuntu but I can't guarantee it was XFCE the first in list & not Xubuntu-session; they look & act identical [for me] after login)
1772542,2018-06-03 22:22:52 UTC,this morning's crash includes these reports (already uploaded)
1772542,2018-05-30 00:17:44 UTC,"// from auth.log  (29-may was last night, 30-may was wake of system today)"
1772544,2018-05-26 08:22:48 UTC,"Actually, the above debug output was produced on my machine :-) (zdohnal is the Fedora package maintainer). You can see the testing progress and further observations here:
https://bugzilla.redhat.com/show_bug.cgi?id=1571782"
1772544,2018-06-16 20:16:36 UTC,"hplip-3.18.6-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report."
1772544,2018-06-12 15:12:16 UTC,"hplip-3.18.6-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-cd7f5d4499"
1772544,2018-06-12 06:13:15 UTC,hplip-3.18.6-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-cd7f5d4499
1772544,2018-06-11 12:15:16 UTC,"Latest upstream release: 3.18.6
Current version/release in rawhide: 3.18.5-1.fc29
URL: http://hplipopensource.com/"
1772544,2018-06-10 20:18:06 UTC,It works now. Thanks!
1772544,2018-06-06 12:11:32 UTC,"Hi,"
1772544,2018-05-26 08:38:49 UTC,Oops. I just noticed that a different PPD was selected compared to hplip-3.18.4-2.fc27
1772544,2018-05-26 08:14:36 UTC,"Created attachment 1441804
Screenshot of running hp-setup (from version 3.18.5-2.fc28)"
1772544,2018-05-26 08:07:59 UTC,"Created attachment 1441803
Debug output of running hp-setup (from version 3.18.5-2.fc28)"
1772544,2018-05-26 08:05:46 UTC,"(In reply to Zdenek Dohnal from comment #8)

> Here is the scratch build (it will last available for 3 days).
> https://koji.fedoraproject.org/koji/taskinfo?taskID=27184511
"
1772544,2018-04-25 12:15:26 UTC,"Latest upstream release: 3.18.4
Current version/release in rawhide: 3.18.3-3.fc29
URL: http://hplipopensource.com/"
1772544,2018-05-24 14:12:30 UTC,hplip-3.18.5-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fe5c004d86
1772544,2018-05-24 15:05:58 UTC,"The printer is initially recognized in hp-setup, but unfortunately hp-setup has problems to read or display the FAX setup later when attempting to add the corresponding queue."
1772544,2018-05-24 15:25:00 UTC,I will attemt to debug this further tonight ...
1772544,2018-05-24 15:28:29 UTC,"(In reply to Fritz Elfert from comment #3)

> hp-setup[9357]: debug: Matching PPD list to model
> color_laserjet_mfp_m278-m281...
> hp-setup[9357]: debug: []
> hp-setup[9357]: debug: No PPD found for model color_laserjet_mfp_m278-m281
> using new algorithm. Trying old algorithm...
> hp-setup[9357]: debug: 1st stage edit distance match
> hp-setup[9357]: debug: Determining edit distance from
> color_laserjet_mfp_m278-m281 (only showing edit distances < 4)...
> hp-setup[9357]: debug: Min. dist = 9
> hp-setup[9357]: debug:
> {'drv:///hp/hpijs.drv/hp-laserjet_mfp_m28-m31-hpijs.ppd': 'HP LaserJet MFP
> m28-m31 hpijs, 3.18.5', 'drv:///hp/hpcups.drv/hp-laserjet_mfp_m28-m31.ppd':
> 'HP LaserJet MFP m28-m31, hpcups 3.18.5'}
"
1772544,2018-05-24 12:15:16 UTC,"Latest upstream release: 3.18.5
Current version/release in rawhide: 3.18.4-3.fc29
URL: http://hplipopensource.com/"
1772544,2018-05-25 08:01:00 UTC,"Actually there are two issues - 1) with not being able to find correct ppd
                                2) fax issue."
1772544,2018-05-25 08:03:43 UTC,"Fritz,"
1772544,2018-05-25 08:32:10 UTC,"Hi Pranavateja,"
1772544,2018-05-25 08:42:18 UTC,Here is the scratch build (it will last available for 3 days). https://koji.fedoraproject.org/koji/taskinfo?taskID=27184511
1772544,2018-05-25 05:59:27 UTC,"Hi Thomas,"
1772548,2018-05-22 02:19:00 UTC,4.17-rc6
1772548,2018-07-26 15:51:11 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1772556,2020-07-28 01:12:37 UTC,I looked into the autopkgtest regressions.
1772556,2020-07-28 05:43:18 UTC,Performing verification of debootstrap in -proposed using Mauricio's script from comment #10.
1772556,2020-07-28 06:08:37 UTC,Performing verification of debootstrap using Mauricio's script from comment #10.
1772556,2020-07-28 19:07:18 UTC,"In addition to comment #18 that explains why the autopkgtests failures are unrelated,
I triggered re-runs with debootstrap package in -updates, which hits the same errors."
1772556,2020-07-29 00:08:54 UTC,"As a final sanity check, I built a new debian-installer monolithic netinstall ISO image, along with the usual vmlinuz / initrd.gz files. When I built them, I enabled -proposed, and debootstrap-udeb 1.0.95ubuntu0.7 was included in the generated MANIFEST.udeb file."
1772556,2020-08-04 07:57:34 UTC,This bug was fixed in the package debootstrap - 1.0.95ubuntu0.7
1772556,2020-08-04 07:57:03 UTC,I will be conditionally releasing the bionic upload before focal as focal is currently in 20.04.1 release freeze. We will push it there once we're out with 20.04.1
1772556,2020-08-31 23:54:06 UTC,"The autopkgtests failures for sbuild on focal-proposed
are all addressed/passed; the Pending SRU page is clear
for focal/deboostrap. [1]"
1772556,2020-09-01 15:38:05 UTC,This bug was fixed in the package debootstrap - 1.0.118ubuntu1.2
1772556,2020-07-27 21:39:06 UTC,"All autopkgtests for the newly accepted debootstrap (1.0.118ubuntu1.2) for focal have finished running.
The following regressions have been reported in tests triggered by the package:"
1772556,2020-08-02 00:08:41 UTC,Fixed in debootstrap 1.0.120 and later.
1772556,2020-07-27 19:40:33 UTC,"All autopkgtests for the newly accepted debootstrap (1.0.95ubuntu0.7) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1772556,2020-08-04 07:57:41 UTC,"The verification of the Stable Release Update for debootstrap has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1772556,2020-07-27 16:35:31 UTC,"Hello Ryan, or anyone else affected,"
1772556,2020-06-15 08:39:07 UTC,This issue is still present. Has anyone found a fix for this?
1772556,2019-08-14 15:49:00 UTC,"@Ryan Lovett, did you find a solution to this?"
1772556,2020-07-22 05:41:01 UTC,Attached is a debdiff for Focal
1772556,2018-05-31 09:59:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772556,2020-07-22 05:52:50 UTC,"Attached is a generic patch with proper DEP-3 tagging for use with quilt. Since debootstrap uses ""3.0 (native)"" instead of ""3.0 (quilt)"", the previous debdiffs are to be used instead. I am just attaching in the off-chance it is useful."
1772556,2020-07-22 08:14:22 UTC,"Verified the netinstall images i.e. initrd.gz and vmlinuz from https://people.canonical.com/~mruffell/sf289200/ work for me, and I am now able to deploy instance"
1772556,2020-07-22 05:40:17 UTC,Attached is a debdiff for Bionic
1772556,2020-07-23 03:46:42 UTC,The VM on the left is using the current 18.04.4 LTS mini.iso provided from http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/installer-amd64/current/images/netboot/ with a date of 2020-01-30.
1772556,2020-07-27 15:12:46 UTC,"Hi Matthew and SRU team,"
1772556,2020-07-27 15:12:57 UTC,"Bionic
======"
1772556,2020-07-27 15:13:06 UTC,"Focal
====="
1772556,2020-07-27 16:02:38 UTC,Uploaded debootstrap to Bionic/Focal. Thanks!
1772556,2020-07-22 08:27:32 UTC,"The attachment ""Debdiff for Bionic"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1772556,2020-07-27 16:48:26 UTC,"Hello Ryan, or anyone else affected,"
1772557,2018-05-22 11:01:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772557,2018-05-22 11:08:03 UTC,"Confirmed. This is related to how gnome-terminal starts up, via dbus / systemd --user. Even if you type ""gnome-terminal"" in let's say an xterm, it just notifies systemd to fire up the server. During this step, environment variables get lost."
1772559,2019-09-12 13:52:16 UTC,Is this still an issue? Please reproduce with latest code.
1772559,2019-11-12 04:17:57 UTC,[Expired for kolla because there has been no activity for 60 days.]
1772560,2019-09-16 14:26:05 UTC,Migrated to https://github.com/widelands/widelands/issues/1706
1772561,2019-09-16 08:40:31 UTC,Migrated to https://github.com/widelands/widelands/issues/3284
1772562,2019-09-12 13:53:34 UTC,Grafana now supports extra conf files - https://github.com/openstack/kolla-ansible/commit/1d249ca96663e3c3828acf2f13cd79cbfe329c8c#diff-9dc7db34253669fbfa2a133d0ab60e2f
1772566,2019-09-16 17:32:31 UTC,Migrated to https://github.com/widelands/widelands/issues/2104
1772566,2018-05-28 07:59:09 UTC,"Ah, so you want buttons to change functionality - I though you wanted to edit some text fields. Yes, that would be nice - we need to refactor the win conditions first though, so that would be a separate bug as kaputtnik said."
1772566,2018-05-27 12:06:11 UTC,"Game type, type of players (human/AI plus AI's difficulty), player colors, enable/disable fog-of-war, replenish land resources (there should be a similar option in setup screen to adjust the difficulty of the map), etc."
1772566,2018-05-26 15:29:22 UTC,"We should reuse the objects from the setup and save screens, which will make this automatically identical."
1772566,2018-05-26 13:34:28 UTC,"This should be as consistent as possible with the game-setup gui presented right before the game begins. There could also be a button which, after a warning and confirmation, could make some of the fields editable."
1772566,2018-05-27 15:38:22 UTC,Type of game (the win condition) is already shown in the objectives window.
1772569,2019-02-21 10:41:43 UTC,Just tried to add https://sourceforge.net/p/gnubiff/bugs/63/ to bug 1815394 and was told it's not a valid bug tracker.
1772584,2018-05-22 10:33:28 UTC,"fwiw, https://github.com/snapcore/snapd/pull/5183/files contains a ""workaround"" for now but its fugly."
1772584,2018-05-22 11:42:13 UTC,"parts, stage, prime and snap have this property. Using `.` as an alternative could be fine, but how could we scale that better is a good conversation to have after some thought."
1772584,2018-05-22 14:25:25 UTC,I wrote a forum topic about this now: https://forum.snapcraft.io/t/how-to-deal-with-source-code-that-has-code-in-a-snap-directory/5553
1772584,2018-05-23 11:41:05 UTC,"I'm not sure I agree with ""whishlist"", it prevents software to be packaged using snapcraft. But given that I have a workaround I will not make a fuss about it."
1772584,2019-10-01 01:52:12 UTC,We agreed on build-aux as an alternative trigger to find snapcraft assets.
1772588,2020-04-19 22:17:05 UTC,"Removing packages:
 xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal
  xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal amd64
  xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal arm64
  xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal armhf
  xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal ppc64el
  xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal riscv64
  xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal s390x
  xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal amd64
  xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal arm64
  xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal armhf
  xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal ppc64el
  xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal riscv64
  xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:17:37 UTC,"Removing packages:
 xserver-xorg-video-ast 1.1.5-1.1build1 in focal
  xserver-xorg-video-ast 1.1.5-1.1build1 in focal amd64
  xserver-xorg-video-ast 1.1.5-1.1build1 in focal arm64
  xserver-xorg-video-ast 1.1.5-1.1build1 in focal armhf
  xserver-xorg-video-ast 1.1.5-1.1build1 in focal ppc64el
  xserver-xorg-video-ast 1.1.5-1.1build1 in focal riscv64
  xserver-xorg-video-ast 1.1.5-1.1build1 in focal s390x
  xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal amd64
  xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal arm64
  xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal armhf
  xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal ppc64el
  xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal riscv64
  xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:17:53 UTC,"Removing packages:
 xserver-xorg-video-mach64 6.9.6-1build1 in focal
  xserver-xorg-video-mach64 6.9.6-1build1 in focal amd64
  xserver-xorg-video-mach64 6.9.6-1build1 in focal arm64
  xserver-xorg-video-mach64 6.9.6-1build1 in focal armhf
  xserver-xorg-video-mach64 6.9.6-1build1 in focal ppc64el
  xserver-xorg-video-mach64 6.9.6-1build1 in focal riscv64
  xserver-xorg-video-mach64 6.9.6-1build1 in focal s390x
  xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal amd64
  xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal arm64
  xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal armhf
  xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal ppc64el
  xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal riscv64
  xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:18:08 UTC,"Removing packages:
 xserver-xorg-video-neomagic 1:1.3.0-1 in focal
  xserver-xorg-video-neomagic 1:1.3.0-1 in focal amd64
  xserver-xorg-video-neomagic 1:1.3.0-1 in focal arm64
  xserver-xorg-video-neomagic 1:1.3.0-1 in focal armhf
  xserver-xorg-video-neomagic 1:1.3.0-1 in focal ppc64el
  xserver-xorg-video-neomagic 1:1.3.0-1 in focal riscv64
  xserver-xorg-video-neomagic 1:1.3.0-1 in focal s390x
  xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal amd64
  xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal arm64
  xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal armhf
  xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal ppc64el
  xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal riscv64
  xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:16:51 UTC,"Removing packages:
 xserver-xorg-input-elographics 1:1.4.1-1build6 in focal
  xserver-xorg-input-elographics 1:1.4.1-1build6 in focal amd64
  xserver-xorg-input-elographics 1:1.4.1-1build6 in focal arm64
  xserver-xorg-input-elographics 1:1.4.1-1build6 in focal armhf
  xserver-xorg-input-elographics 1:1.4.1-1build6 in focal ppc64el
  xserver-xorg-input-elographics 1:1.4.1-1build6 in focal riscv64
  xserver-xorg-input-elographics 1:1.4.1-1build6 in focal s390x
  xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal amd64
  xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal arm64
  xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal armhf
  xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal ppc64el
  xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal riscv64
  xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:20:03 UTC,"Removing packages:
 xserver-xorg-video-trident 1:1.3.8-1build2 in focal
  xserver-xorg-video-trident 1:1.3.8-1build2 in focal amd64
  xserver-xorg-video-trident 1:1.3.8-1build2 in focal arm64
  xserver-xorg-video-trident 1:1.3.8-1build2 in focal armhf
  xserver-xorg-video-trident 1:1.3.8-1build2 in focal ppc64el
  xserver-xorg-video-trident 1:1.3.8-1build2 in focal riscv64
  xserver-xorg-video-trident 1:1.3.8-1build2 in focal s390x
  xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal amd64
  xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal arm64
  xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal armhf
  xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal ppc64el
  xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal riscv64
  xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:18:58 UTC,"Removing packages:
 xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal
  xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal amd64
  xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal arm64
  xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal armhf
  xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal ppc64el
  xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal riscv64
  xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal s390x
  xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal amd64
  xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal arm64
  xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal armhf
  xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal ppc64el
  xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal riscv64
  xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:19:28 UTC,"Removing packages:
 xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal
  xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal amd64
  xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal arm64
  xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal armhf
  xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal ppc64el
  xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal riscv64
  xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal s390x
  xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal amd64
  xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal arm64
  xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal armhf
  xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal ppc64el
  xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal riscv64
  xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:19:46 UTC,"Removing packages:
 xserver-xorg-video-tdfx 1:1.5.0-2 in focal
  xserver-xorg-video-tdfx 1:1.5.0-2 in focal amd64
  xserver-xorg-video-tdfx 1:1.5.0-2 in focal arm64
  xserver-xorg-video-tdfx 1:1.5.0-2 in focal armhf
  xserver-xorg-video-tdfx 1:1.5.0-2 in focal ppc64el
  xserver-xorg-video-tdfx 1:1.5.0-2 in focal riscv64
  xserver-xorg-video-tdfx 1:1.5.0-2 in focal s390x
  xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal amd64
  xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal arm64
  xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal armhf
  xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal ppc64el
  xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal riscv64
  xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:22:07 UTC,"Removing packages from focal:
 xserver-xorg-video-geode 2.11.20-1 in focal
Comment: obsolete source package, only builds xserver for i386 which is not supported as a host arch; LP: #1772588
1 package successfully removed."
1772588,2020-08-06 02:16:47 UTC,"Removing packages:
 xserver-xorg-input-void 1:1.4.1-1build3 in groovy
  xserver-xorg-input-void 1:1.4.1-1build3 in groovy amd64
  xserver-xorg-input-void 1:1.4.1-1build3 in groovy arm64
  xserver-xorg-input-void 1:1.4.1-1build3 in groovy armhf
  xserver-xorg-input-void 1:1.4.1-1build3 in groovy ppc64el
  xserver-xorg-input-void 1:1.4.1-1build3 in groovy riscv64
  xserver-xorg-input-void 1:1.4.1-1build3 in groovy s390x
  xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy amd64
  xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy arm64
  xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy armhf
  xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy ppc64el
  xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy riscv64
  xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:18:41 UTC,"Removing packages:
 xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal
  xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal amd64
  xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal arm64
  xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal armhf
  xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal ppc64el
  xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal riscv64
  xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal s390x
  xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal amd64
  xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal arm64
  xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal armhf
  xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal ppc64el
  xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal riscv64
  xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:16:39 UTC,"Removing packages:
 xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal
  xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal amd64
  xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal arm64
  xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal armhf
  xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal ppc64el
  xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal riscv64
  xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal s390x
  xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal amd64
  xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal arm64
  xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal armhf
  xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal ppc64el
  xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal riscv64
  xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-19 22:18:24 UTC,"Removing packages:
 xserver-xorg-video-r128 6.12.0-1 in focal
  xserver-xorg-video-r128 6.12.0-1 in focal amd64
  xserver-xorg-video-r128 6.12.0-1 in focal arm64
  xserver-xorg-video-r128 6.12.0-1 in focal armhf
  xserver-xorg-video-r128 6.12.0-1 in focal ppc64el
  xserver-xorg-video-r128 6.12.0-1 in focal riscv64
  xserver-xorg-video-r128 6.12.0-1 in focal s390x
  xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal amd64
  xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal arm64
  xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal armhf
  xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal ppc64el
  xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal riscv64
  xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y"
1772588,2020-04-06 10:20:05 UTC,"Good. Just to emphasize, Geode doesn't make sense on distros where the base level for i386 is 686-PAE, since none of the Geodes have PAE (most Geodes are i586, except for Geode LX which is 686 without PAE)."
1772588,2020-04-17 22:34:27 UTC,"ping, there's still time to remove these before release"
1772588,2018-05-23 08:42:29 UTC,"> -geode: i386 only, no kernel support since moving to i586 (or i686?)
"
1772588,2018-05-23 08:13:40 UTC,apparently -evdev has some use still:
1772588,2018-08-07 19:21:36 UTC,"please, could this bug get some attention from the archive admins?"
1772588,2019-04-17 20:27:22 UTC,"See Bryan's question.  These are syncs from Debian, if they are obsolete, why have they not been removed there first?"
1772588,2019-04-17 21:48:44 UTC,"Yes, the plan was to get rid of these in Debian first, maybe after Buster.."
1772588,2019-10-18 05:01:22 UTC,"all the video drivers could be dropped, since TTBOMK they are not available on any 64bit capable hw except maybe AST which has a kernel KMS driver and doesn't need an obsolete X driver which doesn't support the KMS driver"
1772588,2019-01-04 08:14:55 UTC,Should these removals happen first in Debian?  Otherwise we would need to add all these to a blacklist IMU as well.
1772588,2019-11-08 04:21:27 UTC,"@leosmuller
evdev was already marked invalid so it's not considered for removal as part of this bug report. See comment #1."
1772588,2020-03-31 21:27:09 UTC,"Timo, these appear not to have been removed yet in Debian, despite Buster being out.  Will you file for removals in Debian, or should we carry these into another Ubuntu LTS?"
1772588,2020-04-01 03:54:08 UTC,"I was thinking about this bug yesterday, and yes I'll file a bug on Debian to remove these."
1772588,2020-04-01 18:49:10 UTC,@leosmuller - per our discussion your use case for the siliconmotion driver should end in 2024. (1 year too late if removed from 20.04).   As we haven't found any other users of though I did offer to try maintaining it in a PPA if needed for 20.04.
1772588,2020-04-03 07:51:27 UTC,Bug filed on Debian. It's missing some from our list:
1772588,2020-04-03 08:02:48 UTC,"As I have previously commented, the geode driver is NOT obsolete.  It
should not be removed at Debian, where i386 is still 686 without PAE."
1772588,2020-04-06 09:33:52 UTC,Debian dropped what was on their list.
1772588,2019-11-08 03:53:06 UTC,There are some computers and configurations I manage which rely on some of these drivers:
1772601,2018-06-12 12:45:17 UTC,Thanks for the added info @xnox. That's useful to understand.
1772601,2018-06-11 09:47:48 UTC,"Moving back to 'new' since all requested information has been provided, as well as a minimal reproducible test case."
1772601,2018-06-08 16:45:52 UTC,"@rharding
Thanks for following up to our corner sofa meeting."
1772601,2018-06-07 07:05:49 UTC,How do I move this off incomplete?
1772601,2018-06-06 23:51:03 UTC,@xnox the starting of it is located in this python subprocess call in the function:
1772601,2018-06-06 17:48:16 UTC,"So I'd like to try to summarize what I think Dimitri's thoughts are.
All processes that are running should ultimately be managed as part of some service under init (in this case systemd). If it isn't, then you run into potential problems around shutdown/reboot as it doesn't have a way to properly indicate the process should stop at this point.
If we defaulted to KillMode=Process, then *all* processes that are started from charms would end up decoupled from the init system.
Whereas, *if* a charm wants to start a process that has a lifecycle that is decoupled from Juju's lifecycle, then it can do so by creating a new system process and putting it under that. Otherwise, it should be coupled to Juju's lifecycle so that the process is coupled to *some* lifecycle.
Put another way, all processes should be coupled to *a* managed cgroup, and charms are responsible if they want to decouple it from Juju's cgroup.
Juju should not default to decoupling, because that just leaves lots of unmanaged processes."
1772601,2018-05-31 07:06:51 UTC,"The charm is indeed executing pg_ctlcluster, which in turn runs pg_ctl - this means that it is starting and running the PostgreSQL daemons outside of a systemd service. Even though pg_ctl (or something in this chain) takes care to daemonise and detach (running under a separate process group, etc), it is still part of the same cgroup."
1772601,2018-05-31 21:54:17 UTC,"Depends if the intention was to fork a custom daemon within the same
unit; or to manage the system configured postgresql cluster with the
system/package integration of clusters management with the custom ctl
command that calls systemctl."
1772601,2018-05-31 07:28:47 UTC,"FWIW, another surfaced instance in the past:
https://launchpad.net/bugs/1664025"
1772601,2018-05-30 20:36:27 UTC,I think I know what is happening here.
1772601,2018-05-22 11:55:05 UTC,"(erm, the PostgreSQL charm still supports trusty. Ignore my wishful thinking ;) )"
1772601,2018-05-22 11:53:29 UTC,"On 22 May 2018 at 18:34, John A Meinel <email address hidden> wrote:"
1772601,2018-05-22 11:42:18 UTC,It's likely that systemd notices the agent shutting down and cleans up the whole cgroup.
1772601,2018-05-22 11:34:12 UTC,"Is there a reason it is spawned directly by the hook rather than something
like creating a systemd job?"
1772601,2018-06-01 08:46:46 UTC,"This bug is not on the PostgreSQL charm, and the Juju upgrade behavior has nothing specifically to do with PostgreSQL. It is a general problem, that is so far known to have affected two of the most popular charms, and is expected to affect many more."
1772604,2018-05-22 08:42:34 UTC,cleanup-lxd is supposed to do some of this
1772605,2018-05-22 17:04:39 UTC,"Reviewed:  https://review.opencontrail.org/43208
Committed: http://github.com/Juniper/contrail-controller/commit/d430a3dd1032db056c9ff13de71c671af608689b
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1772605,2018-05-22 08:37:19 UTC,"Review in progress for https://review.opencontrail.org/43208
Submitter: Parth Sarupria (<email address hidden>)"
1772613,2018-05-23 14:30:49 UTC,From terminal log:
1772613,2018-05-23 14:31:08 UTC,Thank you for taking the time to file a bug report.
1772614,2018-05-22 09:58:48 UTC,"I am sorry, I have pasted wrong code."
1772614,2018-09-14 14:46:18 UTC,The problem confirmed in 3.2 beta sandbox
1772618,2019-08-02 02:00:15 UTC,"It is unclear why the curtin (Ubuntu) task was marked 'fix committed' over a year ago, but in practice curtin in eoan still has a dependency on btrfs-tools, which ceased to be a real package in cosmic and in eoan-proposed has been dropped as a provides: of btrfs-progs."
1772618,2019-08-02 14:00:44 UTC,"it's been proposed, but then i simply added Provides: old-name in the btrfs package.
basically it was easier to do that than to add support in curtin to sense which release it is, which release it is deploying (the two sometimes do not match) and thus install the right name."
1772618,2019-08-08 15:22:37 UTC,@curtin team
1772618,2021-01-20 11:03:45 UTC,This must have been released.
1772624,2018-06-22 08:39:05 UTC,I still have the issue with the latest version of the linux-firmware package (1.173.1). However the firmware (brcm/brcmfmac4356-pcie.bin) in the official linux-firmware repository solves my issue.
1772624,2018-09-04 13:36:40 UTC,"@jean-Pierre: Thank you very much, manually overwriting the .bin file with the one form the commit you mentioned fixed it. Lets hope the fixed is packaged for 18.04 soon."
1772624,2018-09-07 13:58:08 UTC,"Fix not working for me, i still get
[  145.578369] brcmfmac 0000:04:00.0: firmware: failed to load brcm/brcmfmac4356-pcie.clm_blob (-2)
[  145.578379] brcmfmac 0000:04:00.0: Direct firmware load for brcm/brcmfmac4356-pcie.clm_blob failed with error -2"
1772624,2018-09-11 14:37:39 UTC,@orestis-8 Did you try the previous ubuntu package or the newest files from the official linux-firmware git repo ?
1772624,2018-09-18 19:19:02 UTC,I tried the latest bin from the linux-firmware with no luck.
1772624,2018-11-01 15:51:28 UTC,I recalled trying the firmware in 16.04 (.5?) and it worked. You can boot from USB and copy brcmfmac4356-pcie.bin.
1772624,2018-06-08 11:43:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772631,2018-09-14 14:47:34 UTC,The problem confirmed in 3.2 beta sandbox
1772634,2019-02-26 13:36:26 UTC,Is this still an issue?
1772634,2021-02-17 17:06:42 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1772636,2018-05-23 02:03:02 UTC,"Ah, nevermind. Seems the problem has already been reported:"
1772636,2018-05-23 08:24:05 UTC,"Yes, the list of vpn toggles in the panel gets out of sync with the actual state of the VPNs. The Settings app shows the correct state."
1772636,2018-05-23 08:28:40 UTC,"Also, if you want a vpn to do some testing yourself, let me know and I'll send you one. <firstname>.<lastname>@gmail.com"
1772636,2018-05-23 08:44:53 UTC,"I suggest you comment on the upstream bug(s) where the Gnome developers will see it:
https://bugzilla.gnome.org/show_bug.cgi?id=730446"
1772636,2018-05-23 09:04:16 UTC,"I do not think those bugs are related to this issue since this is a regression and since the bug explicitly mentions that the menu is correct, but the status icon is not."
1772636,2018-05-23 09:14:04 UTC,"In that case please report the bug upstream on the new Gnome bug tracker here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues"
1772636,2018-05-23 09:33:36 UTC,https://gitlab.gnome.org/GNOME/gnome-shell/issues/301
1772636,2018-06-07 21:28:49 UTC,"I was also facing the same problem a few days ago. Then i contact <a href=""https://netgears.support/netgear-router-support-usa/"">netgear router support usa</a> and the solved my problem. But I cannot find a proper solution on the web. how could we fix this type of problems manually?"
1772636,2018-07-02 11:46:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772636,2018-05-23 01:59:41 UTC,I'm not familiar with using VPNs with Gnome and how that changes the GUI.
1772641,2018-05-25 10:46:58 UTC,Problem not solved still on. Any other suggestions? thanks
1772641,2018-05-22 15:40:26 UTC,You may need to run the following from a terminal:
1772641,2018-05-24 08:15:19 UTC,"Hi GianCarlo,
I applied the recommendations above and re-installed the package Pycharm and.. it works now :-)
Thank you to close the ticket.
Cheers,
Pom"
1772646,2018-06-09 12:23:09 UTC,"Interesting bug.
You should report it upstream at http://www.grisbi.org/bugsreports/my_view_page.php"
1772646,2018-06-10 07:41:59 UTC,Thanks. Didn't realized I didn't used the original bug tracker of Grisbi. Done.
1772649,2018-05-22 12:55:20 UTC,"@Jeff, does your credential file (novarc or openrc) have actual OS_PROJECT_DOMAIN_NAME? Or does it have OS_PROJECT_ID instead?"
1772649,2018-05-22 13:23:29 UTC,@Nobuto
1772649,2018-07-10 12:49:06 UTC,I think that this is the case where we have not provided a support for Keystone v3 in auto-loading of credentials. W should definitely do that \o/
1772649,2019-07-18 07:38:21 UTC,In juju this needs to be resolved in the openstack provider DetectCredentials.
1772651,2019-02-22 21:11:16 UTC,How would I go about finding my proper rabbitmq transport url?  I have openstack fully deployed but cannot figure out this url.
1772651,2019-11-12 10:51:26 UTC,I have a very similar issue on Pike.
1772651,2019-09-10 09:40:16 UTC,"I had the same problem. I suggest to bypass haproxy, for example adding..."
1772651,2019-01-21 21:14:50 UTC,"Also nothing is mentioned inside the glance installation guide for queens, nothing related to transport_url :"
1772651,2019-02-23 14:41:29 UTC,"Look inside your Keystone, neutron, nova configuration you should have the transport_url configured."
1772651,2018-10-05 07:03:54 UTC,"I use multiple vlans, so mine problem was if I remember correctly that one of ceph components was not in VLAN that it needed to be. It is network related, at least for me."
1772651,2018-05-28 04:11:53 UTC,"Can you provide some more information?
(1) are you able to make any successful calls using osc ? (for example, image list)
(2) are you able to make any of these failing calls directly to the API endpoint using curl?"
1772651,2018-07-02 17:39:34 UTC,"For this issue I found out it was an authorization error within the glance-swift-store.conf
swift_version = 2
auth_address = http://<endpoint address>:35357/v2.0"
1772651,2018-07-02 17:05:01 UTC,We're have the same issue on a new install.
1772651,2019-01-21 21:08:15 UTC,"So after losing a day debug this bug, finally was able to fix it:"
1772651,2018-10-03 20:28:30 UTC,Having the same issue here on a new install. OpenStack queens on Ubuntu bionic (18.04). Using ceph/cinder for storage.
1772653,2018-05-27 23:04:22 UTC,This is unlikely to be feasible unless we completely change how we number machines.
1772653,2018-05-28 04:37:26 UTC,"I would be happy to have some way of tagging manually added machines, but
we shouldn't trust that a machine number is stable in any fashion."
1772653,2018-05-28 06:30:37 UTC,"     I would be happy to have some way of tagging manually added machines, but
     we shouldn't trust that a machine number is stable in any fashion."
1772653,2018-05-28 07:51:51 UTC,"Trusting that the machine *number* is stable is not appropriate because of
how numbers are applied. As soon as any machine needs to be replaced the
numbers will be wrong. Doing it by tag or some other user appropriate
mechanism is far more correct. That sort of tagging can last as the
environment evolves over time. Juju never re-uses a machine number, so
while you can trust that they will be unique within a model, etc.
In Bundles the machine id you use is a logical identity, and Juju is always
allowed to remap it to a new number (since that number could easily already
have been burned in an initial deployment in a model.)"
1772657,2020-07-12 17:00:23 UTC,I just installed 20.04 and the bug affects that as well.
1772660,2018-09-21 20:39:43 UTC,"my mistake, that's apparently from Python 2.7.15 (I have both versions installed side-by-side)."
1772660,2018-09-21 21:55:11 UTC,"Further elaboration: this does NOT occur on Python 3.6.6, only Python 2.7.15 (in my setup)."
1772660,2018-09-21 22:11:01 UTC,"Scratch that last bit, happens on Python 3.6.6 as well.  I have to leave Cython support off to get a stable build."
1772660,2018-09-21 22:38:28 UTC,"And...I'm wrong again, one last time (apparently I needed to slow down a bit).  It is specifically the coverage that's breaking it, not cython.  I can build --with-cython, but I can't run test.py --coverage without getting a segfault at the end, on either version of python."
1772660,2018-09-23 08:40:54 UTC,Thanks for the reports. I'm pretty sure the OP was reporting a different problem. These seem entirely unrelated.
1772660,2019-01-21 18:51:15 UTC,Same problem when using c api for python and call Py_FinalizeEx() using __del__() from python class.
1772660,2020-01-10 15:56:11 UTC,I'm seeing same crash on Ubuntu 18 with lxml 4.2.1.
1772660,2018-09-21 20:37:48 UTC,"I'm getting a similar segfault during the test_inplace rule, on lxml 2.4.3, python 3.6.6, on aarch64, compiled with gcc-8.2.0 on glibc-2.27."
1772667,2018-06-19 15:33:52 UTC,"Hi Cong, no I'm not using the master version, I also believe that you have to eliminate the limits to TEXT, as I will be more discharged from the activity I'm going to restart the tests.  I think tacker is an interesting and useful project in an NFV environment."
1772667,2018-05-26 16:33:33 UTC,"Hi Paolo, I think Tacker should remove limit value in TEXT. Are you using Tacker master version now? I will make a ps to fix this bug soon."
1772669,2018-05-28 04:59:59 UTC, Timed out waiting for response from cell 00000000-0000-0000-0000-000000000000
1772677,2019-01-10 08:57:14 UTC,"Yeah, I forgot to mention I can't reproduce this bug either... which reminds me to go looking in the fix to see if there's any hint."
1772677,2019-01-10 08:47:10 UTC,"@experimancer it is not correct to say that this problem affects all 18.04 and 18.10 installations, none of mine are seriously affected by it.  It seems it only affects a small minority.  This does not change the fact that for those affected it is a serious issue that needs to be addressed but it does explain why it has not been dealt with more urgently."
1772677,2019-01-10 02:12:18 UTC,"I suspect it's just a matter of no one else on the Desktop team is aware of this bug. To remedy that, I have already put it on their TODO list here: https://trello.com/c/17nGGFFL"
1772677,2019-01-09 22:02:02 UTC,Thanks @vanvugt for telling us that in which gnome-shell versions the bug will be fixed.
1772677,2019-01-09 13:46:24 UTC,I don't understand this logic. So all of us using 18.04 LTS will have to live with this? Doesn't long term support indicate that this will get fixed?
1772677,2019-01-07 03:05:34 UTC,"Ubuntu 19.04 will get the fix (in future, some time) via gnome-shell version 3.31.2 or later."
1772677,2018-12-25 03:45:21 UTC,"Hi all,"
1772677,2018-10-29 05:19:09 UTC,"Reinstalled the same NUC with 18.10, installed package updates & rebooted."
1772677,2018-10-30 16:15:30 UTC,"Thanks for the update, Daniel! I am eagerly waiting. Switched of gnome-shell and would love to come back."
1772677,2018-10-30 04:42:00 UTC,"Sounds like a fix, thanks."
1772677,2018-10-30 04:15:40 UTC,With some digging on the gnome gitlab i've actually found what looks like an existing bug report:
1772677,2018-10-30 01:40:05 UTC,"Andrew, or anyone else experiencing this in 18.10, please report the bug here:"
1772677,2018-10-29 17:59:48 UTC,"I'm sorry, I no longer use Ubuntu on my machines. But I can confirm this happened to me when the lockscreen is active."
1772677,2018-10-29 05:27:40 UTC,Thanks. That seems to agree with comment #31.
1772677,2018-10-30 21:15:31 UTC,"Hi All,
any progress here ?
Thanks"
1772677,2019-01-17 15:33:26 UTC,"I just got hit with this bug as well. Fresh Ubuntu 18.10 install on a Desktop (Ryzen 2995x, 32GB RAM, Vega 64, 250GB NVMe /, and 1TB Evo 860 SSD /home) with two monitors (1 vertical using DP, and one horizontal using HDMI), only thing I did post install was install a few flatpaks from flathub (Discord, Telegram, VSCode, Slack), and a snap (CLion) as well as a Rust toolchain (https://rustup.rs). Went to bed, went to work the next morning, and when I came up the computer appeared to be frozen as it wouldn't wake from sleep. After a hard reset and login, I noticed I couldn't do an update do to ""disk full"". Checked `df` and saw `/` was full. Quick checking of dirs lead to `/var/log/syslog` being 230GB from a single night/day of no use!"
1772677,2019-03-12 02:01:40 UTC,"Remember this bug is only about ""entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)""."
1772677,2019-01-18 17:11:14 UTC,I'm experiencing this same issue as well.  Syslog grew to >100GB overnight.
1772677,2018-10-29 04:11:19 UTC,We know 18.04 has this bug.
1772677,2020-06-04 15:12:38 UTC,"i have the same issue on fedora 31
gnome-shell is sending thousands of log messages
journalctl --disk-usage  shows about 3G of logs and it's still increasing
i hope the fedora team fix this issue soon"
1772677,2019-04-25 09:20:05 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1772677,2019-04-25 09:19:59 UTC,This bug was fixed in the package gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1
1772677,2019-03-13 02:18:01 UTC,You can download the .deb files containing the proposed fix for 18.04 from here:
1772677,2019-03-13 01:20:07 UTC,"Apologies for my previous message. Somehow I missed that a proposed fix was available for testing. I'm having trouble figuring out how to download the proposed fix, but I'm sure I can figure it out with time and research. It's been years since any variant of Linux has been my primary personal OS, so I'm still in the early stages of re-familiarizing myself with everything."
1772677,2019-03-13 00:54:07 UTC,Is there any fix or workaround for this bug? I installed a brand new copy of Ubuntu 18.04 on a brand new 512 GB SSD three days ago on Saturday evening (2019-03-09). I installed online updates during installation. It is now Tuesday evening (2019-03-12). The computer has been locked for most of the time since installation.
1772677,2019-03-11 17:44:00 UTC,"I had the same issue, followed David's instructions, but I still get a rapidly expanding syslog file when I lock the screen. I am running Ubuntu 18.04.02 with gnome shell 3.28.3, dual monitor and intel graphics."
1772677,2019-03-05 20:29:53 UTC,Thank you for taking the time to verify this stable release fix.  We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE).  Please remove the verification-done tag and add one for the release you have tested the package in.  Thank you!
1772677,2019-03-05 13:31:33 UTC,"No issue, you might have something more updated than actual archives though."
1772677,2019-02-25 19:53:57 UTC,Just installed on my machine. Followed the instructions here: https://wiki.ubuntu.com/Testing/EnableProposed to enable the -proposed in the GUI.
1772677,2019-02-25 13:50:54 UTC,"Hello strangedata, or anyone else affected,"
1772677,2019-02-25 13:45:20 UTC,Does this mean that the fix for the bug in cosmic is not present in the 3.30.2-0ubuntu1.18.10.1 gnome-shell upload (currently in -proposed)?
1772677,2019-01-24 23:56:43 UTC,"This is fixed in disco (fix added in 3.30.1-3), and thus in 3.30.2-1ubuntu1"
1772677,2019-01-22 04:14:29 UTC,We're working on getting this fix into all the current Ubuntu releases...
1772677,2019-01-18 01:28:25 UTC,"One other bit of info I thought about that could be contributing is my horizontal monitor is hooked up to a cheap 4 port HDMI switch (not a true KVM switch, it's HDMI only). This seems to cause the monitor to flicker back and forth during boot / loading the splash page as it looks (to my untrained eye) like it can't decide if the HDMI is hooked up to a monitor or not. Once the login page is displayed though that particular problem is gone until the next boot."
1772677,2018-10-29 03:59:36 UTC,I can also confirm that this is lock-screen related as it starts logging as soon as the screen is locked and stops when un-locked.
1772677,2018-06-14 02:22:50 UTC,"Yes, that seems to be the same bug as this."
1772677,2018-10-28 07:33:15 UTC,"Hi All,
any progress here ?
Thanks"
1772677,2018-06-28 13:39:13 UTC,"I realize I don't know that much about what's going on under the hood, but it seems to have slowed considerably for me. I was on vacation for a week in the middle, and since getting back (and perhaps some updates?), it doesn't seem to be as big an issue any more."
1772677,2018-06-25 01:52:37 UTC,In Ubuntu 18.10 I am seeing almost zero log messages and no bug... It's the same version of gnome-shell as in 18.04: 3.28.1-0ubuntu2
1772677,2018-06-24 18:54:27 UTC,"Confirming bug.
Ubuntu 18.04
GNOME Shell 3.28.1"
1772677,2018-06-13 10:22:43 UTC,"I'm having a similar issue. Not sure if it's the same bug or not, as my logs are slightly different. I installed 18.04 on a new ssd two days ago. Each time I come back to my machine after leaving it idle, I find my harddrive is full, and syslog has grown to 9-10GB."
1772677,2018-06-13 10:17:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772677,2018-05-29 02:14:43 UTC,OK. FYI here is the offending source code:
1772677,2018-05-28 16:34:11 UTC,"I don't see many popups, just a few gnome-shell notifications (mounted USB stick, etc)."
1772677,2018-05-26 03:52:50 UTC,It's interesting osdWindow.js appears at the top of the stacks.
1772677,2018-10-29 03:52:52 UTC,I can confirm that this bug still exists in 18.04.
1772677,2018-05-24 20:04:03 UTC,"Hi,"
1772677,2018-05-24 01:37:44 UTC,"As other people don't seem to be reporting this bug, and it seems to be a major bug, I wonder if it's caused by the extension ""pidgin-persistent-notification""."
1772677,2018-05-23 17:24:16 UTC,apport information
1772677,2018-05-23 17:24:14 UTC,apport information
1772677,2018-05-23 17:24:13 UTC,apport information
1772677,2018-05-23 01:41:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1772677,2018-07-03 14:44:06 UTC,"My syslog is filling up too. Is this the same bug, or do I need to open a new one?"
1772677,2018-07-04 01:35:31 UTC,"km,"
1772677,2018-05-25 15:21:05 UTC,"Just to confirm, from the time I've disabled the extension yesterday 'till now, about 80GB of log has been generated:"
1772677,2018-07-30 08:43:29 UTC,"Gijs,"
1772677,2018-07-30 07:01:36 UTC,"Confirming this bug, also affects me."
1772677,2018-10-17 18:29:17 UTC,"Hi Daniel,
thanks, no gnome-shell extensions installed"
1772677,2018-10-17 12:27:18 UTC,"Apologies, this is indeed still happening in 18.10."
1772677,2018-10-17 01:48:12 UTC,"Mathieu,"
1772677,2018-10-16 15:39:34 UTC,"and:
mathieu@PC1:/var/log$ uname -a
Linux PC1 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1772677,2018-10-16 02:01:53 UTC,"Mathieu,"
1772677,2018-10-15 15:53:24 UTC,I've upgraded to 18.10 the problem is still there ...
1772677,2018-10-14 04:53:59 UTC,It's been removed from 18.10.
1772677,2018-10-16 15:38:15 UTC,"Here is it:
athieu@PC1:/var/log$ tail -100 syslog
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #2   7fffb8a304b0 I   self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #3   7fffb8a30560 I   resource:///org/gnome/gjs/modules/signals.js:128 (7fa2facc18b0 @ 386)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #4   55f922a9d330 i   resource:///org/gnome/shell/ui/layout.js:538 (7fa2faa04310 @ 127)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #5   7fffb8a314e0 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #6   7fffb8a320f0 b   self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 gnome-shell[1993]: Object St.Icon (0x55f91fad6290), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: == Stack trace for context 0x55f91889c1e0 ==
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #0   7fffb8a303a0 I   resource:///org/gnome/shell/ui/osdWindow.js:223 (7fa2faac78b0 @ 231)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #1   7fffb8a30470 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #2   7fffb8a304b0 I   self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #3   7fffb8a30560 I   resource:///org/gnome/gjs/modules/signals.js:128 (7fa2facc18b0 @ 386)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #4   55f922a9d330 i   resource:///org/gnome/shell/ui/layout.js:538 (7fa2faa04310 @ 127)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #5   7fffb8a314e0 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #6   7fffb8a320f0 b   self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: == Stack trace for context 0x55f91889c1e0 ==
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #0   7fffb8a303a0 I   resource:///org/gnome/shell/ui/osdWindow.js:224 (7fa2faac78b0 @ 273)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #1   7fffb8a30470 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #2   7fffb8a304b0 I   self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #3   7fffb8a30560 I   resource:///org/gnome/gjs/modules/signals.js:128 (7fa2facc18b0 @ 386)
Oct 16 17:33:33 PC1 gnome-shell[1993]: Object St.BoxLayout (0x55f91f5ab8c0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #4   55f922a9d330 i   resource:///org/gnome/shell/ui/layout.js:538 (7fa2faa04310 @ 127)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #5   7fffb8a314e0 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 ..."
1772677,2018-10-11 12:25:55 UTC,One of my workstations has this too. Which information is necessary for a fix?
1772677,2018-10-08 10:00:32 UTC,"Same issue, not as severe regarding disk space. No extensions active."
1772677,2018-10-18 01:38:09 UTC,"Angel, if you can then please confirm what lines of code you are seeing on 18.10."
1772677,2018-09-17 13:46:32 UTC,Same issue here. Filled up hard drive pretty quickly and I have a 512GB SSD
1772677,2018-09-09 10:00:49 UTC,I have the same issue.
1772677,2018-08-06 02:39:46 UTC,"I am seeing this happen here, as well. Though my disk space issue isn't anywhere near as dire."
1772677,2018-08-02 08:11:33 UTC,I am facing this issue too. Is there a workaround as I have very limited disk space and this is killing it!
1772677,2018-10-12 01:39:42 UTC,Is anyone seeing this bug in Ubuntu 18.10 or is it already fixed there?
1772678,2018-05-25 00:05:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772680,2018-10-24 23:34:38 UTC,Moved the target to 3.next because this is definitely a new feature.
1772680,2020-07-16 19:41:41 UTC,We have reached out to the RB Digital team behind the development for more information and have not received a response.
1772680,2020-07-16 19:11:31 UTC,"Curious about the state of this development, since RBDigital is no longer going to be a thing. Any plans to transfer the work to the OverDrive APIs?"
1772680,2019-08-29 01:59:03 UTC,"One quick question about this branch: there appear to be two new files in live_t: 100-ebookapi-rbdigital.t and 101-ebookapi-rbdigital.t.  I am all for more automated tests, but I'm wondering if both of these are supposed to be added?  One appears to be a more extensive version of the other."
1772680,2018-11-16 19:44:31 UTC,I've force-pushed to collab/gmcharlt/lp1772680_rbdigital_enhancements again to reflect additional updates.
1772680,2018-09-20 21:00:47 UTC,"Force-pushed to collab/gmcharlt/lp1772680_rbdigital_enhancements with some additional updates, including some release notes."
1772680,2018-06-19 16:56:06 UTC,"Jeff - actually, it looks like it *will* be leveraging the existing integration pieces."
1772680,2018-08-23 17:24:52 UTC,"Removing pullrequest, as it needs further work."
1772680,2018-08-21 18:05:08 UTC,"I'm unable to get this working, first on a realistic PINES test server, then on a stock server.  Here's the perl error I'm seeing:"
1772680,2018-08-14 01:34:04 UTC,A series of patches are available in the collab/gmcharlt/lp1772680_rbdigital_enhancements branch:
1772680,2018-05-23 20:02:15 UTC,Attached are a few screenshots of the progress so far (keep in mind that wording / links / etc. will likely change as progress continues).
1772680,2018-05-22 18:00:32 UTC,"Hi Jeff,"
1772680,2018-05-22 16:38:27 UTC,Very exciting!
1772680,2018-05-22 16:04:11 UTC,This is exciting!
1772680,2018-09-07 18:50:47 UTC,"Sorry about that; I've corrected typos in fm_IDL.xml, rebased against master, and force-pushed to the collab branch."
1772683,2020-01-27 11:18:19 UTC,"Hi, guys."
1772683,2020-04-21 20:36:24 UTC,"Hi,"
1772683,2020-04-29 05:00:26 UTC,"I Got the same problem
Xubuntu 18.04
libreoffice 6.0.7.3"
1772683,2019-11-22 00:44:40 UTC,any update on this? I'm on the LO6.3.3 this problem still occurs in 19.04.
1772683,2020-06-10 13:55:18 UTC,I've discovered that this bug affects the non-snap version of libreoffice on focal too.
1772683,2020-10-18 20:08:07 UTC,"Andrew Thornton, may that be a different problem? Please see bug #1886092 for the non-snap version report and workaround/fix when Apparmor is the problem."
1772683,2020-11-23 22:15:55 UTC,"I have the same problem:
Ubuntu 20.04
LibreOffice (snap) 7.0.2.2"
1772683,2020-05-16 16:35:56 UTC,"Works in DEB-version, doesn't work in snap (LO 6.4.3.2, Ubuntu 18.04)."
1772683,2019-02-21 10:07:38 UTC,Thx for the pointer Olivier - closing then on this side.
1772683,2018-05-23 14:30:16 UTC,A brain dump of my investigation so far: https://forum.snapcraft.io/t/signing-files-with-gpg-from-within-a-snap/5566
1772683,2019-02-20 04:43:49 UTC,Do you have a working PPA I could install future updates from where the product would be supported? FYI- the link previously provided is not / no longer valid.
1772683,2018-05-22 16:30:03 UTC,"Adding the gpg-keys interface, and exporting GNUPGHOME to $REALHOME/.gnupg in the launcher script helps, but then the keys that are listed have incomplete information:"
1772683,2018-05-22 18:04:45 UTC,"When trying to sign the current document with one of the listed keys, the operation silently fails.
If I strace the app, I can see that the ""gpg --sign --detach"" command is issued with the correct key ID. If I run the same command in a snapd shell for libreoffice.writer, I'm seeing the following:"
1772683,2018-07-01 07:19:17 UTC,"Created attachment 143245
Digital Signatures window"
1772683,2018-10-19 10:37:42 UTC,"Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version."
1772683,2019-02-20 15:15:30 UTC,"Please note that packages from PPAs are not officially supported, they are a community best effort to provide up-to-date packages on older versions of Ubuntu.
If you're after an officially supported package, you should stick to the (older) version in the Ubuntu repositories."
1772683,2018-11-11 23:51:42 UTC,"It seems LibreOffice is unable to discover a working gpg setup on your machine. To further troubleshoot this, it would be easiest if you could install a debug-enabled version, e.g. from here:"
1772683,2018-10-19 13:12:24 UTC,"My current version is:
Version: 6.1.3.1
Build ID: 1:6.1.3~rc1-0ubuntu0.18.04.1"
1772683,2019-02-19 13:39:39 UTC,"This doesn't seem to work with the deb package either. Tested on cosmic with 6.1.4, and confirmed by Rico."
1772683,2019-02-19 02:43:37 UTC,"I would prefer not to do such steps as I use the software. I have this same issue on all laptops I have LibreOffice installed on, and also use GPG on all as well with no issues on Thunderbird, manual signing, file encryption, etc. If LibreOffice cannot find it, there seems to be a bigger issue as the install is all default, nothing changed or modified in any way except for the import and export of keys, and in some cases, a newly generated key."
1772683,2019-02-19 12:24:35 UTC,"6.1.5~rc2-0ubuntu0.18.04.1~lo3 seems to be a pre-release build provided by the Ubuntu community, so we have no control over how that build is done. It does appear not to be a general problem though with LibreOffice on that system."
1772685,2018-05-22 17:46:11 UTC,"This may be innocuous, or you may have bad ram.  This is saying that the system has 80 GiB of RAM installed physically but the kernel is only addressing roughly 62.3GiB."
1772685,2018-05-24 16:09:20 UTC,"So, a dmesg dump after a fresh boot (or maybe /var/log/dmesg would suffice).  that dump is not useful, unfortunately, as all the important data has already been popped off of the ring buffer."
1772685,2018-06-25 16:33:19 UTC,We resolved the mismatch by removing an NVDIMM placed into the system by another engineer. We should test with NVDIMM again to confirm and resolve.
1772685,2019-01-14 15:53:31 UTC,We can retest the system on 18.04.1 with the latest SRU updates.
1772685,2019-01-14 16:27:10 UTC,That's interesting to note.  NVDIMMs do change the parameter of this test. Please do confirm this behaviour (per Jerry's comment from last June).
1772688,2018-07-15 07:49:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772688,2018-07-15 07:49:28 UTC,Exactly the same here
1772688,2018-07-15 07:50:05 UTC,"Might be related to /etc/apt/apt.conf.d/01autoremove{,-kernels}?"
1772688,2018-08-02 16:24:57 UTC,"It's actually the files that configure apt to do intended behavior, but somehow aptitude has it's own mind :/"
1772688,2018-05-22 17:06:49 UTC,"Forgot one thing: if ask aptitude explicitly why linux-image-... is needed, it will reply that no reason for this package was found."
1772691,2020-08-19 00:15:42 UTC,Thank you for this report! We were indeed not noticing when encrypted drives got plugged in. Should be fixed in 42.3.
1772711,2018-11-22 16:59:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately it's probably too far down our backlog to ever make it to the top. In the meantime, patches welcome - though those would probably be better going to Debian or upstream first."
1772713,2018-05-25 13:27:34 UTC,"As it has previously been explained to me, we don't highlight OK/Continue by default because if the alert appears in a place where you are scanning items, if the user is quickly scanning books and not paying attention to the screen, the next scan would send the <Enter> signal and clear the alert. That item wouldn't really be scanned, because there was an alert dialog, not a barcode entry box, and the user would have missed the alert."
1772713,2018-05-25 13:14:18 UTC,"You can press <Tab + Enter> to confirm. Maybe ""OK/Continue"" should be highlighted by default so it's only one key press to confirm."
1772718,2018-05-22 20:54:55 UTC,Nifty
1772720,2018-05-22 20:38:27 UTC,Uploaded to new branch ...
1772726,2018-05-22 20:08:57 UTC,Assigned to me
1772726,2018-05-22 20:08:58 UTC,nuwahahaha
1772741,2018-09-14 14:48:07 UTC,The problem confirmed in 3.2 beta sandbox
1772746,2018-05-23 14:30:15 UTC,"Another verified work-around that needs no alteration to the PATH:
1. sudo apt-get purge python-pip python3-pip
2. Delete all of the pip/pip3 stuff under .local including the packages.
3. sudo apt-get install python-pip python3-pip
4. Using pip and/or pip3, reinstall needed Python packages."
1772746,2018-08-23 00:02:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772746,2018-09-13 13:11:06 UTC,"It seems that pip was updated using 'pip install -U pip', what made user- and system-wide installations of pip out-of-sync. It should be noted, however, that pip can only be updated using APT, as updating via pip itself risks breaking the package. It might be wise to implement a big warning upon issuing 'pip install -U pip'."
1772746,2018-10-17 17:41:57 UTC,From https://packages.ubuntu.com/bionic/python3-pip it seems like pip is pinned at an old version python3-pip (9.0.1-2).
1772746,2018-10-18 13:55:17 UTC,"There are movements on the Debian side to update to v18. The packaging is complicated, I did what I could to push it, however I got stuck at some point with debundling and turned to package maintainers for help."
1772746,2019-06-08 13:05:37 UTC,Any further moves on this?
1772746,2019-09-19 17:47:48 UTC,I tried `pip3` again and it seems fine in *buntu 18.04.3.up-to-date.
1772749,2018-05-26 14:37:39 UTC,Debian has found the same report in the upstream searx package:
1772749,2018-05-25 15:58:15 UTC,Related Debian bug upstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900068
1772749,2018-05-22 21:25:41 UTC,Crash dump data was from inside an autopkgtest run.
1772749,2018-05-22 21:25:13 UTC,Crash dump data was from inside an autopkgtest run.
1772749,2018-05-22 21:25:01 UTC,Refer to crash bug #1772749 for crash dump data.  The crash report is also attached here.
1772749,2018-05-22 21:16:54 UTC,This currently fails autopkgtests in Debian[1] as well as in Ubuntu[2].
1772752,2018-06-13 12:59:38 UTC,"Seems we moved to storyboard:
https://storyboard.openstack.org/#!/story/1772752"
1772752,2018-06-12 10:31:35 UTC,"Yes, sounds like we are good with the idea. Let's go ahead with this design."
1772752,2018-06-05 09:56:18 UTC,"We can also use labels instead of explicit template parameters
(they're easier to manage)."
1772752,2018-05-24 21:11:09 UTC,"There was already a blueprint for this too:
https://blueprints.launchpad.net/magnum/+spec/container-runtime-config"
1772752,2018-06-04 15:14:20 UTC,"Hi Richardo,"
1772752,2018-05-30 10:39:18 UTC,Hi Madhuri.
1772752,2018-06-05 09:55:07 UTC,Hi.
1772752,2018-05-29 04:19:16 UTC,"@Richardo,"
1772753,2018-05-22 21:39:51 UTC,"StacktraceTop:
 ?? ()
 __libc_fork () at ../sysdeps/nptl/fork.c:204
 daemonize (logfile=0x55b70f7a1440 ""/var/log/uwsgi/app/searx.log"") at core/utils.c:137
 uwsgi_setup (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at core/uwsgi.c:2279
 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at core/uwsgi.c:2011"
1772753,2018-05-25 15:58:33 UTC,Related Debian bug upstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900068
1772753,2018-05-26 14:37:45 UTC,Debian has found the same report in the upstream searx package:
1772754,2018-09-09 21:22:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772757,2018-12-25 10:17:38 UTC,"Is this error still happening? In that case, what distro are you using? I've tested it and is displaying the search dialog as expected."
1772757,2019-10-11 04:17:23 UTC,[Expired for Sakura because there has been no activity for 60 days.]
1772760,2018-05-23 19:31:08 UTC,apport information
1772760,2018-05-23 19:31:10 UTC,apport information
1772760,2018-06-09 21:19:52 UTC,"@Kai-Heng Feng - could you please tell me how one could do that? Thanks. I am not sure I have Elan touchpad, but if I have, I would like trying that."
1772760,2018-05-29 00:28:14 UTC,I've been using the linux kernel 4.17.0-041700rc6-generic for 1 day and just now it happened again. So it is not fixed in that version of the kernel.
1772760,2018-06-09 14:15:51 UTC,"There's a new SMBus support for Elan touchpad, please try kernel parameter ""psmouse.elantech_smbus=1""."
1772760,2018-05-23 19:31:07 UTC,apport information
1772760,2018-06-11 09:43:10 UTC,https://wiki.ubuntu.com/Kernel/KernelBootParameters
1772760,2018-05-23 19:31:11 UTC,apport information
1772760,2018-05-23 19:31:06 UTC,apport information
1772760,2018-05-23 19:31:01 UTC,apport information
1772760,2018-05-23 19:31:04 UTC,apport information
1772760,2018-05-23 19:31:02 UTC,apport information
1772760,2018-05-23 19:31:00 UTC,apport information
1772760,2018-05-23 19:30:59 UTC,apport information
1772760,2018-05-23 19:30:57 UTC,apport information
1772760,2018-05-23 19:30:54 UTC,apport information
1772760,2018-05-23 13:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1772760,2018-05-23 12:35:07 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1772760,2018-05-23 19:31:05 UTC,apport information
1772760,2018-05-23 19:30:56 UTC,apport information
1772765,2018-07-12 16:11:07 UTC,+1
1772765,2018-06-16 10:03:16 UTC,"After workaround urwid version, I get a version problem with ruamel.yaml"
1772765,2018-05-29 21:37:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772777,2018-05-24 03:50:32 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1772791,2018-07-24 21:42:49 UTC,I just ran into the same behavior.  I typed my password quickly and automatically into the lock/login screen... and was disturbed to see the whole thing right there in plaintext as I was hitting enter.
1772791,2018-08-02 02:47:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772791,2018-08-02 02:48:54 UTC,"Upstream:
https://gitlab.gnome.org/GNOME/gdm/issues/305"
1772791,2019-03-21 02:41:21 UTC,https://gitlab.gnome.org/GNOME/gnome-shell/issues/460#note_331931 seems to offer a pretty compelling explanation of why this might be seen inadvertently.
1772791,2020-01-21 12:36:47 UTC,#7 It seems it was moved to https://gitlab.gnome.org/GNOME/gnome-shell/issues/460
1772791,2018-05-23 03:48:31 UTC,The GUI that handles the text input is part of gnome-shell. So also assigning this bug to gnome-shell. In fact it's more likely gnome-shell than gdm3.
1772796,2018-05-23 04:13:59 UTC,"Commit Id:
04e4e888558ebe5d9701e31bba61d4e256ab71a8"
1772796,2018-07-26 15:51:00 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1772796,2018-08-09 01:20:04 UTC,"yes, please."
1772805,2018-06-05 10:09:50 UTC,"shoud add ""sudo"" before vmur command"
1772805,2018-06-05 10:10:34 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/412139
1772811,2019-01-07 07:56:29 UTC,"I have nominated bionic to receive the fix but I don't have any power to accept the nomination. Nothing is formally ""scheduled"" yet."
1772811,2019-01-30 17:03:18 UTC,"I can do the cherry-picking, to have this properly fixed in 3.30 though we need also"
1772811,2019-03-07 11:24:04 UTC,This bug was fixed in the package mutter - 3.31.92-1~fakesync
1772811,2019-05-28 20:46:50 UTC,"Hello Leon, or anyone else affected,"
1772811,2019-06-06 09:33:55 UTC,This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.1
1772811,2019-05-31 03:26:41 UTC,"I verified this bug on bionic.
After upgrade gnome-shell and mutter to 3.28.4-0ubuntu18.04.1, the video switch experience is better than original."
1772811,2019-06-06 09:33:24 UTC,This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.1
1772811,2019-06-06 09:33:40 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1772811,2019-01-07 07:22:14 UTC,"@Daniel,
Because this issue is for bionic,do we have schedule to back port it to bionic?"
1772811,2019-05-28 21:39:33 UTC,"Hello Leon, or anyone else affected,"
1772811,2019-01-07 03:17:14 UTC,"The mutter and gnome-shell fixes are both in version(s) 3.30.1, so Fix Released in 18.10 and 19.04 already."
1772811,2018-12-06 04:30:13 UTC,"per test on cosmic, get the same result as #9."
1772811,2018-12-08 13:35:54 UTC,"Hi Sab, If ""keep it on screen longer"" means: ""while previous key press released, the OSD will keep on screen longer. Before it disappears, press it one more will go next one, instead of before from the first one."" Guess that's also what you mean."
1772811,2018-12-07 16:56:01 UTC,"Ok, good. So it means the function is fixed, a better experience would be to not show the UI at all or keep it on screen longer then"
1772811,2018-12-06 02:36:28 UTC,"haven't tried cosmic but I　did try disco, still can reproduce this issue"
1772811,2018-12-05 15:06:32 UTC,"looking a bit more, indeed the gnome-shell behaviour changed as described in https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/208/"
1772811,2018-12-05 03:56:55 UTC,seems not only one oem platform can reproduced this issue due to Bug 539477
1772811,2018-12-04 09:17:34 UTC,"Hi Seb, Per what I know, it's reproduced in every machine."
1772811,2018-12-04 09:10:57 UTC,Thank you for your bug report. Does it work sometime/on some machines? Do you always end up having the first mode selected or is that key events are sent several times and doing more than 1 change?
1772811,2018-12-04 06:55:37 UTC,more information:
1772811,2018-05-23 06:43:34 UTC,The attached is the video when we press down the video-out key.
1772811,2018-12-25 08:35:17 UTC,https://gitlab.gnome.org/GNOME/mutter/issues/281 involved the fixes for mutter and gnome-shell so https://gitlab.gnome.org/GNOME/mutter/merge_requests/213 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/208 are both needed to fix this issue.
1772811,2018-12-06 03:32:20 UTC,"Happened to have a machine install disco, test passed:"
1772813,2018-05-24 03:48:04 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1772813,2018-05-24 19:28:43 UTC,The package manager logs shown here seem to be incomplete.  What they do show is the following output:
1772832,2018-05-23 19:59:29 UTC,That was what I am trying to say.
1772832,2018-05-23 15:11:33 UTC,"This feature would be very difficult to use if the waveform moved along with the audio stutter. If this is implemented, only the sound should stutter. The waveform should only move when the jog/mouse drag is moved."
1772832,2018-05-23 10:58:41 UTC,Implementation hints:
1772837,2018-06-07 20:35:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772843,2018-10-03 13:08:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772843,2020-06-16 08:47:28 UTC,Bug still there in Ubuntu 20.04 (Evolution 3.36.2). Please fix...
1772843,2018-05-23 07:10:57 UTC,"I forgot to say I can do some testing if you want (logs, debugging, etc.).
Please tell me what to do..."
1772847,2018-05-30 09:23:39 UTC,"Code submitted here
https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/412911 Fix bug 1772847 image export doc bug"
1772847,2018-06-13 05:46:08 UTC,Code merged.
1772849,2018-05-30 11:13:53 UTC,I also wonder if ovs native firewall driver can be used instead of hybrid. Is there any progression?
1772849,2018-05-31 06:02:57 UTC,"I was going to configure ovs native firewall driver by refering to following url:
https://docs.openstack.org/neutron/queens/admin/config-ovsfwdriver.html"
1772857,2018-06-13 02:59:11 UTC,"Code merged, so close this"
1772857,2018-05-30 09:22:19 UTC,"Code submitted here
 https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/412927 Fix bug 1772857 ssh-doc-bug"
1772858,2019-05-27 13:50:34 UTC,"This still isn't actionable so I unsubscribed ubuntu-server for now.
But surely, if there is an update providing this testcase as requested by Andreas it can be looked at again."
1772858,2018-11-26 12:42:53 UTC,"Thanks for filing this bug in Ubuntu, and sorry for getting to it so late."
1772863,2018-05-23 08:43:16 UTC,I am not sure that it is a bug. It may be a Logismic conflict.
1772866,2018-06-25 08:30:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577750"
1772866,2018-09-03 10:02:07 UTC,"Change abandoned by Michel Peterson (<email address hidden>) on branch: master
Review: https://review.openstack.org/577750
Reason: I think this is not longer relevant. Please reopen if not."
1772870,2018-05-23 09:04:29 UTC,This is the log from /var/log/installer/debug
1772871,2018-10-17 18:57:39 UTC,"If I edit the application launcher in the start menu to the same, with the extra ""Run in terminal"", it does not start the application."
1772874,2018-06-06 07:20:24 UTC,"FYI, this was addressed by the patch from annp, and this bug is a duplicate."
1772875,2018-05-25 12:31:12 UTC,Fails to boot with FAT32 as file-system type without displaying error message.
1772882,2018-08-18 22:54:19 UTC,Could be a duplicate of bug 1758009
1772882,2018-05-23 12:28:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1772883,2018-05-23 16:40:06 UTC,same problem on macOS High Sierra - can't find any mention of this elsewhere.
1772883,2018-05-23 18:27:02 UTC,Thanks for the report.
1772883,2018-05-24 22:35:02 UTC,"After a closer look it appears fix is actually trivial -- mentioned header file GooHash.h is not used in this file, same goes for another header GooTimer.h. On the other hand pdf -parser.cpp uses GooString for which header file is missing. Attached patch fixes above issues."
1772883,2018-05-25 05:54:44 UTC,I can confirm that this patch fixes the problem.
1772883,2018-05-25 21:02:08 UTC,Thanks for the patch !!
1772883,2018-05-25 21:17:22 UTC,"Thanks for merging Mc, just wanted to look into this myself."
1772883,2018-07-19 16:04:43 UTC,"May I also add that if you are compiling for OSX, you will also need this patch as well:"
1772886,2018-07-20 20:15:26 UTC,I have experienced this problem for a long time on a BQ E5. I think simply the phone is short of memory and running the Browser which requires a lot of memory causes UBPorts to kill Podbird which is in the background.
1772887,2018-05-29 20:27:26 UTC,This is occurring on 2.3.8 Bionic as well.  Will this be fixed in 2.3?  Thanks.
1772887,2018-05-29 23:54:28 UTC,Bionic controllers are not supported on 2.3. Bionic workloads are.
1772887,2018-05-30 02:36:58 UTC,"On Tue, May 29, 2018 at 11:54:28PM -0000, Tim Penhey wrote:

> Bionic controllers are not supported on 2.3. Bionic workloads are.
"
1772887,2018-05-25 08:29:34 UTC,https://github.com/juju/juju/pull/8769
1772891,2018-05-23 11:48:44 UTC,"Solved with
sudo wget https://raw.githubusercontent.com/plbossart/UCM/master/chtrt5645/HiFi.conf -O /usr/share/alsa/ucm/chtrt5645/HiFi.conf
Why does not ubuntu team just use this file for alsa-data?"
1772894,2018-11-27 02:10:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772895,2019-03-27 09:04:09 UTC,Proposed: https://github.com/juju/juju/pull/9964
1772895,2018-05-23 11:33:51 UTC,"In addition, the message instructs users to configure a space using ""juju config""."
1772907,2018-06-30 22:39:32 UTC,Works fine with peppermint 9. Closed...
1772907,2018-07-02 13:09:00 UTC,"Terrific news Joel, thanks for letting us know :)"
1772910,2018-07-06 20:12:54 UTC,qbirthday maintainer here.
1772913,2019-05-28 18:57:24 UTC,"Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1772913,2019-05-02 21:29:37 UTC,"This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'."
1772913,2018-11-28 14:12:37 UTC,"It should be fixed, feel free to reopen if that's not the case though"
1772913,2018-11-15 17:54:37 UTC,"including the url to the upload this time, https://launchpad.net/ubuntu/+source/shotwell/0.28.4-0ubuntu1"
1772913,2018-11-14 09:18:38 UTC,Could you try if that upload fixes the ptp issue for you?
1772913,2018-05-31 20:43:20 UTC,This one looks similar too:
1772913,2018-07-17 00:55:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772913,2018-05-31 20:38:55 UTC,Description of problem:
1772913,2018-05-27 12:17:21 UTC,For some reason the device is not tagged with ID_GPHOTO2 anymore on 18.04 when in PTP mode.
1772913,2018-05-23 13:49:13 UTC,"I changed the PTP for MTP,
And alert appears ""Could not claim the USB device -53""
Then I unmount the device and then appears in the shotwell, is a workaround. But not an elegant solution"
1772913,2018-07-17 00:58:54 UTC,Worth monitoring:
1772915,2020-04-22 18:21:01 UTC,Bumping to php7.4 so this doesn't get forgotten.
1772915,2019-10-28 17:32:19 UTC,"@paelzer Could I get MR on salsa for this, please?"
1772915,2018-11-26 12:48:54 UTC,"Thanks for filing this bug in Ubuntu, and sorry for taking so long to get to it."
1772915,2019-05-27 14:43:40 UTC,"FYI this is added in Debian not Ubuntu quite a long time ago (2010):
=> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595706"
1772915,2019-05-27 14:44:40 UTC,Added the remote bug and moved all to 7.3 as we won't fix that in older released I'd think
1772917,2018-05-29 14:30:36 UTC,I can't reproduce this. Try on fresh live usb. It seems like a xorg bug. Can you give some screenshot ? Press Alt+F2 and try running `compiz --replace` and see if that fixes the issue.
1772918,2018-07-03 13:21:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772920,2018-05-24 03:47:17 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1772925,2018-05-23 15:50:02 UTC,"This is unfortunately a bug with Kolla. The problem is that the Neutron payload does not contain hostname, and cannot be used as a parameter."
1772928,2020-03-18 08:59:30 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/577363
Reason: This is a pretty old patch in merge conflict. Feel free to restore it (or ask gibi on irc to restore it) if you still working on it."
1772928,2018-06-22 07:37:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577363"
1772928,2019-10-07 09:59:39 UTC,Does anybody affect this bug? I need someone to review this patch.
1772941,2018-06-10 11:22:18 UTC,"On my system (Ubuntu 18.04 configured with netplan.io and systemd-networkd where possible), dhcpd is configured by default, so it just enumerates currently-available IP subnets on interfaces to determine on which interface to listen.
The only interface it is normally listening on my system is br0, which currently includes only wlan0 interface managed by hostapd.
On one reboot I had a race condition between dhcpd and hostapd : on its startup, hostapd did 'country update' on wlan0 which temporarily brought it down, and br0 went down as well, then systemd-networkd temporarily removed its IP address. Right at this moment, dhcpd had begun to start, looking matching IPs on interfaces and failing to find any of them. After that I got working hostapd (WiFi network visible to clients), but clients unable to configure their IPs after WiFi authentication."
1772941,2018-07-27 17:33:10 UTC,"It's getting to the point that I'm afraid to do updates on my Ubuntu servers anymore. :-(
I haven't had time to investigate more thoroughly, but it looks like dhcpd is being run before the network is up.
I'm running 14.04 LTS, and applied pending updates yesterday. When the system rebooted I ran into this. The system has a manually configured static IP address on a hardwired ethernet port. There's nothing wrong with the config file, in spite of the error message.
After getting past the fact that I suddenly also couldn't directly run the init script anymore (grrrr)  and the obfuscation involved in trying to get initctrl to actually work, I was able to restart the service without issue.
I now have a server that I can't trust to boot unattended. This isn't acceptable."
1772941,2020-12-16 22:18:23 UTC,"I think i have the same issue.
Ubuntu 18.04.5 i386 with two NIC and configured in order to listen and serve lease on a specific NIC."
1772941,2018-06-10 11:22:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772942,2018-06-08 11:29:10 UTC,"Note that the package 4.15.0-1013.13~16.04.1 does not exist, leveraging results from 4.15.0-1013.13~16.04.2 here"
1772942,2018-06-14 21:31:09 UTC,The package has been published and the bug is being set to Fix Released
1772954,2018-11-06 14:56:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772954,2018-11-06 14:56:37 UTC,This problem affects me too. I am unable to work with a firebird 2.0 database that worked before upgrading to ubuntu 18.
1772955,2020-07-30 15:54:00 UTC,There is a branch available here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1772955-only-show-totals-when-xact-has-balance
1772955,2020-08-19 15:30:42 UTC,"This works. I have tested this code and consent to signing off on it with my name, Ruth Frasur and my email address, <email address hidden>."
1772955,2020-07-30 15:13:32 UTC,"I agree with the approach Galen suggest of a new peer to money.open_usr_summary that adds ""AND balance_owed > 0.0"" to the WHERE clause.  The two views would then provide ""today"" and ""for all time"" perspectives."
1772955,2020-07-30 14:18:52 UTC,"The proposed patch only works as expected if the list of billings that the user owes money on fits in one grid page. If the user has more billings than that, paging through the rows will cause the total billed, owed, and paid values to fluctuate based on the billings that are currently displayed."
1772955,2020-02-20 16:58:08 UTC," have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>."
1772955,2020-01-29 18:17:56 UTC,I pushed a branch with a fix:https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mrisher/lp1772955-total-billed-inaccurate
1772955,2018-05-24 20:18:10 UTC,"I can confirm this behavior on master, following these exact steps."
1772961,2018-05-24 00:32:07 UTC,"https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+ref/fix/1772961-suse-spec-fixes
has a branch of those changes."
1772981,2018-05-23 19:30:02 UTC,Evergreen version: 3.0.7
1772981,2018-06-14 17:00:21 UTC,I see the same thing on 3.1 as well.
1772981,2018-11-14 00:32:48 UTC,I did a bit of digging here.  It seems that all the problematic browse entries all have the same config.metabib_field.  Its ID is 37 in our system.  Here it is:
1772981,2018-11-14 19:49:44 UTC,"Update: I looked at the MODS via supercat, and it seemed correct: http://libcat.linnbenton.edu/opac/extras/supercat/retrieve/mods33/record/147068"
1772981,2018-11-15 18:57:57 UTC,"It looks like the issue here is that config.metabib_field for ID 37 does not define the same browse_xpath as the other author fields.  The other author browse fields (7, 8, 9, and 10) set browse_xpath to:"
1772981,2018-11-15 20:07:42 UTC,"Thanks so much for taking a look at this, Dan!  I can confirm that updating the browse_xpath of ID 37 to match the other author fields fixes the issue.  Turning off browse_field also makes sense to me, but I haven't been able to test/investigate that very much."
1772985,2018-05-23 18:40:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1772988,2018-05-23 18:38:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/570247"
1772988,2020-04-01 21:30:33 UTC,"Change abandoned by Romain LE DISEZ (<email address hidden>) on branch: master
Review: https://review.opendev.org/570247
Reason: Outdated. It was for Keystone 11."
1772997,2019-09-06 08:15:45 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/283
1772997,2019-03-04 16:45:53 UTC,I have moved the command creating the index for wlhelp
1772997,2019-05-09 20:29:04 UTC,I think this is fixed now.
1772998,2018-06-20 22:14:49 UTC,Any response on this?  It is affecting a lot of servers where we are attempting to use it.
1772998,2018-07-13 23:14:47 UTC,Can somebody please respond?
1772998,2018-07-21 00:32:50 UTC,"Well, in case anybody ever looks at this bug, it may be a bug in the Ruby interpreter.  This is fixed in Debian - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876377"
1772999,2018-06-05 13:24:50 UTC,"Confirmed. Specifically, I do not see the Digital Bookplate option in the Staff Web Client following Nathan's steps. I can also confirm that, switching to Incognito will allow to view the bookplates in Basic search -> Type drop down option."
1772999,2018-05-31 17:36:06 UTC,"Oh, and yes, Enable Digital Bookplate Search is set to true."
1772999,2018-05-25 15:51:24 UTC,"Thank you, Nathan, for those details and additional testing!"
1772999,2018-05-31 17:15:33 UTC,"Failed to reproduce in an incognito window, using the same copy of Chrome, on the same computer, where it does happen otherwise."
1772999,2018-05-23 20:29:00 UTC,"Just a note, the missing header/footer part is entirely expected.  When logged into the web staff client, the OPAC intentionally hides all that because it expects to live inside an iframe within the staff client."
1772999,2018-05-23 20:03:13 UTC,"Hi Nathan,"
1772999,2018-05-23 19:40:45 UTC,"Hi Nathan,"
1772999,2018-05-24 18:25:53 UTC,This is Evergreen 3.0.7.  Sorry I forgot to specify that.
1773021,2018-05-24 19:16:04 UTC,This occurs with both Xenial and Bionic
1773022,2018-05-24 19:16:01 UTC,This occurs with both Xenial and Bionic
1773022,2018-06-04 17:16:57 UTC,"I believe this bug is actually that landscape has no concept of NVMe storage. On another of our test machines with an NVMe drive + local spinning disks, the NVMe is also absent in the landscape storage page. Therefore, this is not limited to AWS or this instance type."
1773024,2019-07-20 08:29:54 UTC,"I have the same issue on my AMD PC after upgrading to 18.04. Before there was no such message. It doesn't look harmful any way (Ubuntu seems to work just fine for months now), just troubling."
1773024,2019-08-29 12:52:54 UTC,Dell XPS 15 9570 and same error:
1773024,2019-01-08 22:00:03 UTC,Dell XPS 15 9570 and same error.
1773024,2019-01-18 09:16:27 UTC,Same issue on my Dell XPS 15.
1773024,2018-09-27 06:08:41 UTC,This is happens in my XPS 15 9570
1773024,2018-10-28 05:07:04 UTC,"Same here, Dell XPS 15 9570"
1773024,2018-05-24 19:39:06 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1773024,2018-07-24 04:17:31 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1773024,2018-08-26 23:03:32 UTC,I can confirm the issue with freshly installed Ubuntu Server 18.04.
1773026,2018-05-24 00:33:22 UTC,This bug was fixed in the package epiphany-browser - 3.28.2.1-1ubuntu1
1773028,2019-06-06 09:30:05 UTC,"The verification of the Stable Release Update for epiphany-browser has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1773028,2019-06-06 09:40:09 UTC,This bug was fixed in the package epiphany-browser - 3.28.5-0ubuntu1
1773028,2019-05-28 21:52:17 UTC,"Hello Jeremy, or anyone else affected,"
1773028,2018-08-25 10:02:41 UTC,This bug was fixed in the package epiphany-browser - 3.29.91-1ubuntu1
1773028,2018-05-24 00:33:22 UTC,This bug was fixed in the package epiphany-browser - 3.28.2.1-1ubuntu1
1773028,2019-06-05 15:11:52 UTC,"Using 3.28.5-0ubuntu1 the URL from the testcase stops segfaulting the browser, SRU fix verified"
1773032,2018-10-02 21:28:01 UTC,But your wifi is actually rtl8821AU
1773044,2019-10-15 10:59:25 UTC,"Hmm, LXD is using github for bug tracking. Not sure what to do."
1773044,2019-10-15 11:00:32 UTC,I'm marking this bug as invalid. I'll let LXD developers know to have a look and mirror this bug on their side.
1773044,2019-10-15 11:04:02 UTC,How did you configure your container to talk to X11 in the first place?
1773044,2019-10-15 10:58:51 UTC,NOTE: the apparmor denial is not relate dto the problem.
1773046,2018-05-24 02:01:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/570290"
1773046,2018-05-24 16:13:12 UTC,"I'm not sure this is a bug, it was changed for one of the IPAM blueprints for a reason, so more investigation is required.  Why does it matter that the next IP isn't used?  Once enough IPs are allocated/de-allocated it is essentially random anyways."
1773046,2018-05-25 12:17:00 UTC,"Change abandoned by Sridhar Venkat (<email address hidden>) on branch: master
Review: https://review.openstack.org/570290
Reason: Abandoning this patchset based on discussions."
1773049,2019-04-22 13:04:38 UTC,"Hi, I'm going through Fedora/text related issues and was wondering if this is still an issue."
1773049,2019-05-12 00:30:24 UTC,Fixed in master here: https://gitlab.com/inkscape/inkscape/commit/6b8b86ca248cc47128ee3646d7ce17d2c0720522
1773049,2018-05-27 01:46:44 UTC,"Probably related:
https://bugs.launchpad.net/inkscape/+bug/1768958 (only happens on Fedora)"
1773050,2018-05-27 01:45:39 UTC,"I think all these Fedora text issues are related. See also:
https://bugs.launchpad.net/inkscape/+bug/1768958"
1773050,2018-07-02 23:49:48 UTC,"As I wrote it in https://bugs.launchpad.net/inkscape/+bug/1779779 , for me the crash occurs only if you click on the right half of your single-character text."
1773050,2019-04-22 11:28:06 UTC,Closing as a fix has been committed in 1.0alpha
1773050,2019-04-25 15:08:29 UTC,"Fedora has applied a downstream patch, but the commits pushed should fix the issue."
1773051,2018-05-24 02:01:04 UTC,Work-around V2: Put all connectors in a layer above the objects to which they refer
1773051,2018-05-24 09:50:18 UTC,"OK, my diagnosis is wrong. I am not sure what breaks the links. Moving the paths to the end of the XML does fix the links, tho sometimes the actual link ID is also lost and must be recreated."
1773065,2018-05-24 02:47:02 UTC,Had a quick look at the provided logs and the error is pointing to the issue with oslo/cinder framework. No error related to 3par driver is seen
1773065,2018-07-27 11:44:24 UTC,"Hi Vivek,
You can close this launchpad. Finally it was identified that issue was related to backup design. It was causing a lot of network contention and thus affecting iSCSI connections."
1773065,2020-02-19 11:23:29 UTC,CLosing as per Pedro's feedback.
1773066,2018-06-07 20:35:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773074,2018-05-31 19:16:38 UTC,This should technically work. But could it be that you have installed the version from the official archive?
1773074,2020-05-23 19:10:19 UTC,This is a fairly old bug and there hasn't been any feedback for a while.
1773074,2018-05-30 19:26:24 UTC,As you are using 17.10 are you running Gnome on Wayland?
1773074,2018-05-31 01:29:42 UTC,"% env | grep XDG
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_VTNR=2
XDG_SESSION_ID=3
XDG_SESSION_DESKTOP=ubuntu
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop
XDG_MENU_PREFIX=gnome-
XDG_SESSION_TYPE=x11
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_RUNTIME_DIR=/run/user/1010
XDG_SEAT=seat0"
1773075,2019-02-21 08:16:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773077,2020-08-18 14:25:52 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1773084,2020-01-08 04:17:35 UTC,[Expired for OpenStack rabbitmq-server charm because there has been no activity for 60 days.]
1773084,2018-05-24 16:54:43 UTC,"In my previous comment I meant to say it DOES NOT work. I have attempted removing and reconfiguring the charm to use xenial and it appears the have the same issue. I am not sure why, but even when manually deploying and using version 72 it also encounters the issue. Could it be something on the RabbitMQ-server packages end?"
1773084,2018-05-24 16:48:05 UTC,"Unfortunately running juju resolved does work, it tries to reinstall the rabbitmq-server package and after 3-4 attempts it once again fails. I am not sure what to do because this is holding back the entire deployment, as it’s the last portion to be installed. I leave tomorrow and will be away fronm the servers for 12 weeks and it will be hard to work on it."
1773084,2019-11-08 17:00:45 UTC,"Setting this back to incomplete; is this still a problem, or has it been resolved?"
1773084,2018-05-24 08:15:30 UTC,"ubuntu@juju-8f71e3-2-lxd-7:~$ sudo fuser /var/lib/dpkg/lock
ubuntu@juju-8f71e3-2-lxd-7:~$ ps faxuw
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0  37592  5856 ?        Ss   08:08   0:02 /sbin/init
root        54  0.0  0.0  35272  7340 ?        Ss   08:08   0:00 /lib/systemd/systemd-journald
root        62  0.0  0.0  41720  3228 ?        Ss   08:08   0:00 /lib/systemd/systemd-udevd
root       375  0.0  0.0  65508  6196 ?        Ss   08:08   0:00 /usr/sbin/sshd -D
root      9842  0.0  0.0  92796  6836 ?        Ss   08:11   0:00  \_ sshd: ubuntu [priv]
ubuntu    9876  0.0  0.0  92796  3400 ?        S    08:11   0:00      \_ sshd: ubuntu@pts/1
ubuntu    9877  0.0  0.0  21328  5160 pts/1    Ss   08:11   0:00          \_ -bash
ubuntu   10888  0.0  0.0  36084  3408 pts/1    R+   08:14   0:00              \_ ps faxuw
root       376  0.0  0.0 272868  5976 ?        Ssl  08:08   0:00 /usr/lib/accountsservice/accounts-daemon
root       377  0.0  0.0 289108 25008 ?        Ssl  08:08   0:00 /usr/lib/snapd/snapd
root       378  0.0  0.0  26068  2624 ?        Ss   08:08   0:00 /usr/sbin/cron -f
syslog     384  0.0  0.0 186896  3300 ?        Ssl  08:08   0:00 /usr/sbin/rsyslogd -n
message+   386  0.0  0.0  42944  4112 ?        Ss   08:08   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root       396  0.0  0.0  28544  3104 ?        Ss   08:08   0:00 /lib/systemd/systemd-logind
daemon     397  0.0  0.0  26044  2284 ?        Ss   08:08   0:00 /usr/sbin/atd -f
root       399  0.0  0.0   5220   148 ?        Ss   08:08   0:00 /sbin/iscsid
root       400  0.0  0.0   5720  3536 ?        SLs  08:08   0:00 /sbin/iscsid
root       403  0.0  0.0 277176  6080 ?        Ssl  08:08   0:00 /usr/lib/policykit-1/polkitd --no-debug
root       429  0.0  0.0  12840  1896 ?        Ss+  08:08   0:00 /sbin/agetty --noclear --keep-baud console 115200 38400 9600 linux
root       619  0.0  0.0  18032  2928 ?        Ss   08:08   0:00 bash /var/lib/juju/init/jujud-machine-2-lxd-7/exec-start.sh
root       623  0.0  0.0 848564 53116 ?        Sl   08:08   0:00  \_ /var/lib/juju/tools/machine-2-lxd-7/jujud machine --data-dir /var/lib/juju --machine-id 2/lxd/7 --debug
root       727  0.0  0.0 722524 21960 ?        Ssl  08:08   0:09 /usr/bin/lxd --group lxd --logfile=/var/log/lxd/lxd.log
root       741  0.0  0.0  18028  2916 ?        Ss   08:08   0:00 bash /var/lib/juju/init/jujud-unit-rabbitmq-server-7/exec-start.sh
root       745  0.0  0.0 711412 55608 ?        Sl   08:08   0:01  \_ /var/lib/juju/tools/unit-rabbitmq-server-7/jujud unit --data-dir /var/lib/juju --unit-name rabbitmq-server/7 --debug
ubuntu    9844  0.0  0.0  45148  4892 ?        Ss   08:11   0:00 /lib/systemd/systemd --user
ubuntu    9845  0.0  0.0  61044  1684 ?        S    08:11   0:00  \_ (sd-pam)
ubuntu@juju-8f71e3-2-lxd-7:~$"
1773084,2018-05-24 07:53:10 UTC,"Would it be possible for you to collect the following information as soon as possible after you see the hook error on the rabbitmq-server unit:
    sudo fuser /var/lib/dpkg/lock
    ps faxuw"
1773084,2018-05-24 06:42:33 UTC,"Every time that I have tried so far. Right now I have all the other OpenStack services up and running, except this one."
1773084,2018-05-24 06:31:38 UTC,Thank you for reporting this issue and for linking and referencing related bugs.
1773084,2018-05-24 06:00:24 UTC,Appears to be related to https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1764634
1773084,2018-05-24 09:05:43 UTC,Thank you for providing the requested information. Unfortunately the process holding the DPKG lock is already gone in the above output.
1773100,2018-09-26 18:44:10 UTC,"This bug appears to have been fixed in a recent kernel, perhaps 4.15.0-33 or 4.15.0-34."
1773100,2018-05-24 17:51:53 UTC,The lockup occurs to early in the boot process to use appport-collect.
1773100,2018-05-24 19:38:05 UTC,"Can you see if this issue also happens with the latest daily image?  It can be downloaded from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/"
1773100,2018-05-24 08:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773100,2018-05-24 20:19:22 UTC,Same behavior using the latest cosmic-server-amd64.iso daily.
1773102,2018-08-01 10:35:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587754"
1773102,2020-03-11 00:28:27 UTC,"Reviewed:  https://review.opendev.org/582332
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=67c761cb2c32d130bcb4bcb1c97ac65e828f6c80
Submitter: Zuul
Branch:    master"
1773102,2018-09-24 14:47:05 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1773102,2018-08-13 03:33:18 UTC,"Change abandoned by Zengzhi Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/587754
Reason: https://review.openstack.org/#/c/587772/
solve the problem."
1773102,2018-08-10 09:52:39 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.
1773102,2018-08-09 22:39:05 UTC,"Reviewed:  https://review.openstack.org/589251
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bee3e963ef4c55d51f82cf0b9f4a6fb9f9940bc9
Submitter: Zuul
Branch:    stable/pike"
1773102,2018-08-09 20:39:31 UTC,"Reviewed:  https://review.openstack.org/589249
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=410eca71833615a95614c6416e6580e3d72e92b9
Submitter: Zuul
Branch:    stable/queens"
1773102,2018-08-06 18:18:21 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/589251"
1773102,2018-08-06 18:17:09 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/589249"
1773102,2018-08-06 14:49:03 UTC,"Reviewed:  https://review.openstack.org/587772
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=233ea582f7b58b3188bfa523264e9052eefd00e5
Submitter: Zuul
Branch:    master"
1773102,2018-08-01 10:58:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587772"
1773102,2018-08-01 10:47:15 UTC,"Yes, its a import ordering issue."
1773102,2018-07-31 16:29:40 UTC,"Bug 1784666 has the proper triage information on the problem, it's an import ordering issue."
1773102,2018-09-24 14:46:41 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1773102,2018-07-12 18:34:01 UTC,"Doug, we already do use overwrite=False for periodic tasks (by way of the get_admin_context() method) _but_ we are not using overwrite=False when we create a new RequestContext during any cell database targeting (we use RequestContext to convey which database connection to use). So what I'm trying out now is passing overwrite=False when constructing the RequestContext in the target_cell method."
1773102,2018-05-28 06:23:21 UTC,"It can be confusing if a log is generated by execution of a periodic task, but without a prefix of DEBUG oslo_service.periodic_task. An example is as follows. It is not easy to tell the log generated by update_available_resource is that of a peridic task or the VM creation task."
1773102,2018-05-28 06:43:52 UTC,"It can be confusing especially for periodic tasks who share common fucntino calls with operation tasks like VM creation. For example, the periodic task of _heal_instance_info_cache shares the common function call of _get_instance_nw_info with VM creation. It sometimes hard to tell wherther logs generated by _get_instance_nw_info are those of the VM creation task."
1773102,2018-05-29 02:53:03 UTC,I think this is not only a problem for the periodic task log.
1773102,2018-05-28 04:40:42 UTC,"looks not a very limitted impact because DEBUG oslo_service.periodic_task is prefix
and good enough for operator to know they can ignore the req-xxxx"
1773102,2018-05-29 02:55:49 UTC,"s/As a result, the requiest id/As a result, the request id/"
1773102,2018-05-29 03:02:26 UTC,I think that this bug is similar to the following bug.
1773102,2018-07-31 16:27:04 UTC,"Just to close the loop on this, I was mistaken about cell targeting affecting changes in logged request_ids. When cell targeting occurs, it's true the thread local context is overwritten, but it will be overwritten by another context with the same request_id. So it shouldn't result in any changing of logged request_id."
1773102,2018-06-07 06:36:52 UTC,"I don't know for comment #4 whether it's valid , have you tried to s/&/;/ in the command?
this request id is actually controlled by  oslo_middleware.request_id which is not nova specific"
1773102,2018-06-07 14:49:06 UTC,"First, it is not clear to me that these two issues are related.  I would suggest opening a separate bug against cinder/oslo.log to track the other problem being discussed here."
1773102,2018-07-12 18:14:22 UTC,"I have seen this behavior too, so marking as valid."
1773102,2018-07-12 18:26:01 UTC,"I think I spoke too soon with my suggestion, oslo.context to_dict/from_dict methods take care of carrying over the request_id:"
1773102,2018-07-12 18:29:50 UTC,It sounds like the periodic tasks that use a RequestContext should construct it with overwrite=False to avoid storing the value in the thread local storage.
1773102,2018-07-12 18:30:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582332"
1773102,2018-06-04 07:15:44 UTC,"I had a patch here but not sure it can fix the problem
https://review.openstack.org/#/c/570707/1"
1773110,2020-05-13 19:52:26 UTC,"Thomas, I believe something else is at play here."
1773113,2018-06-25 17:37:03 UTC,"Hello,"
1773113,2018-06-26 11:07:48 UTC,I just tried again to test if nvidia updates would fix this ugly bug. In summary: no.
1773113,2018-07-02 21:27:57 UTC,Here is a live iso xubuntu-bionic with nvidia-390.48 and prime from MatheuGras-TimRichardson
1773113,2018-07-06 06:14:21 UTC,"Ubuntu 18.04
Mate & XFCE
Running Nvidia 390 - NVIDIA Corporation GM107M [GeForce GTX 850M] (rev a2)"
1773113,2018-07-12 07:32:25 UTC,"Ubuntu 18.04 (mint 19)
Cinnamon
Running Nvida 390 on Thinkpad W541"
1773113,2018-07-17 05:16:00 UTC,*** WORKAROUND CONSISTENTLY WORKING ***
1773113,2018-08-31 14:50:52 UTC,"Yes, it seems this bug does not happen any more on my PC.
But the update alone does not resolve the issue.
After I remove - install the drivers, lightdm and gdm several times, suddenly it works :))"
1773113,2018-07-27 08:24:45 UTC,With end-of-life of ubuntu 17.10 the issue is more urgent than ever.
1773113,2018-07-30 08:14:29 UTC,"seems to be the issue is resolved with an update run of the following packages:
 Upgrade: perl-base:amd64 (5.26.1-6ubuntu0.1, 5.26.1-6ubuntu0.2), screen:amd64 (4.6.2-1, 4.6.2-1ubuntu1), libsystemd0:amd64 (237-3ubuntu10.2, 237-3ubuntu10.3), libsystemd0:i386 (237-3ubuntu10.2, 237-3ubuntu10.3), grub-common:amd64 (2.02-  2ubuntu8.1, 2.02-2ubuntu8.2), perl-modules-5.26:amd64 (5.26.1-6ubuntu0.1, 5.26.1-6ubuntu0.2), console-setup-linux:amd64 (1.178ubuntu2, 1.178ubuntu2.3), grub2-common:amd64 (2.02-2ubuntu8.1, 2.02-2ubuntu8.2), udev:amd64 (237-3ubuntu10.2,   237-3ubuntu10.3), console-setup:amd64 (1.178ubuntu2, 1.178ubuntu2.3), dkms:amd64 (2.3-3ubuntu9.1, 2.3-3ubuntu9.2), grub-pc:amd64 (2.02-2ubuntu8.1, 2.02-2ubuntu8.2), libudev1:amd64 (237-3ubuntu10.2, 237-3ubuntu10.3), libudev1:i386 (237-   3ubuntu10.2, 237-3ubuntu10.3), libperl5.26:amd64 (5.26.1-6ubuntu0.1, 5.26.1-6ubuntu0.2), localechooser-data:amd64 (2.71ubuntu2, 2.71ubuntu3), grub-pc-bin:amd64 (2.02-2ubuntu8.1, 2.02-2ubuntu8.2), udisks2:amd64 (2.7.6-3, 2.7.6-3ubuntu0.   1), libnss-myhostname:amd64 (237-3ubuntu10.2, 237-3ubuntu10.3), systemd-sysv:amd64 (237-3ubuntu10.2, 237-3ubuntu10.3), gir1.2-udisks-2.0:amd64 (2.7.6-3, 2.7.6-3ubuntu0.1), libpam-systemd:amd64 (237-3ubuntu10.2, 237-3ubuntu10.3), systemd: amd64 (237-3ubuntu10.2, 237-3ubuntu10.3), libnss-systemd:amd64 (237-3ubuntu10.2, 237-3ubuntu10.3), keyboard-configuration:amd64 (1.178ubuntu2, 1.178ubuntu2.3), libudisks2-0:amd64 (2.7.6-3, 2.7.6-3ubuntu0.1), perl:amd64 (5.26.1-6ubuntu0.  1, 5.26.1-6ubuntu0.2)"
1773113,2018-09-05 23:12:04 UTC,"I've managed to get it working, the last thing I did was creating this file"
1773113,2018-10-22 07:23:33 UTC,"Hi,
I think this helps no matter the OS, I mean, ""unices""...
I did that on fedora 29 modular. Delete every xorg.conf-files you can find.
$ sudo rm /etc/X11/xorg.conf
(on fedora there's one in /usr/share/X11 too)
($ sudo rm /usr/share/X11/xorg.conf)
Then restart the login manager (or reboot)
$ sudo service [login-manager here, either gdm, xdm, lightdm, sddm, whatever] restart"
1773113,2018-10-22 07:27:30 UTC,"Oh, I'd like to add it isn't perfect yet, as it gets you to software rendering on Cinnamon.
MATE+compiz should work fine. I'll confirm or infirm this later on."
1773113,2018-07-17 05:19:17 UTC,"oops, see steps above, in between step 1 & 2, choose Ubuntu Recovery from Advanced Options Menu"
1773113,2018-06-25 14:32:37 UTC,"I have the same problem as everybody here.(MSI PE60 - Nvidia GTX960M)
I tried to install nvidia 390 in many many ways. And every time, it boot on a black screen or it's flooded with PCIe Bus error that NEVER stops. (Really, +25 hours running, I've tried...) Can't even switch to console. So I have to go to the recovery mode to purge nvidia 390 driver."
1773113,2018-06-17 05:00:21 UTC,"I have what seems to be a similar problem. Have a machine with stock Ubuntu 18.04 clean install. Ran fine with latest recommended proprietary driver for over 2 weeks. Then Friday the 15th June, 2018 it refuses to use the proprietary drivers. The latest Kernel version will not even show the login screen, just hangs in the tty 1. The previous kernel shows the login screen, but it is choppy and will not accept valid login credentials."
1773113,2018-06-17 09:29:13 UTC,Hello
1773113,2018-05-24 08:37:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773113,2018-05-24 12:21:09 UTC,The graphical display failed to boot on laptop. The same system Ubuntu 18.04 works on the desktop.
1773113,2018-05-24 12:42:17 UTC,390 is completely useless for me as well.
1773113,2018-05-25 14:36:09 UTC,"My laptop:  Acer 15.6"" FHD E5-575G-57A4 7th Gen Intel Core i5 7200U NVIDIA GeForce GTX 950M
Using the nvidia-driver-390 package it boots up to a black screen.  The only way for me to fix this currently is to boot into safe mode and revert the drivers to xserver-xorg-video-nouveau.  Please let me know if I can provide any logs to help diagnose this issue and get it fixed asap."
1773113,2018-05-25 16:02:39 UTC,"Same here.   Installing nvidia-390 drivers on my Dell XPS 15 9560 results in an unbootable system. I have tried many, if not all, of the fixes suggested in bug report #1752053, but none of them will allow me to boot my system once the drivers are installed. I have even tried the latest nvidia-396 with the same results. Either I get a boot-loop, or else the login screen does not appear at all and I am only greeted with a black screen w/blinking cursor. Someone reported that a fix was released.....can you please SHARE THE FIX??? Without proper diplay drivers, I cannot even use the display ports or any of the HDMI ports on this device. How frustrating that this display problem returns over and over again with each and every Ubuntu release! SMH..."
1773113,2018-06-23 20:41:05 UTC,Can we get an update here? I have a system that is useless as a desktop until this is resolved.
1773113,2018-05-27 00:54:20 UTC,"Same issue with ubuntu 18.04 nvidia-driver-390 (GeForce GT740M). I have these packages libglvnd and xorg-server from bionic-proposed, but it is not working. I had to purge all nvidia in order to use ubuntu sudo apt remove --purge nvidia-*."
1773113,2018-05-25 16:51:32 UTC,Same issue with (X)ubuntu 18.04 with lightdm and nvidia-driver-390 and also nvidia-driver-340. Following setup (notebook):
1773113,2018-06-04 20:22:14 UTC,"I don’t think anyone is working on these issues for us...? There are no updates anywhere, and this is a real serious problem for so many of us. ☹️"
1773113,2018-06-05 06:14:52 UTC,Installing nvidia-396 from graphics-drivers PPA solved the issue for me. Only the nvidia-settings app fails silently when I try to open it.
1773113,2018-06-06 10:03:54 UTC,"I had a variant of this problem (on Lenovo P51, M2200 Nvidia):"
1773113,2018-06-06 20:05:23 UTC,"Same here. After 18.04 install, I did an ""apt upgrade"", which installed nvidia-390 stuff among other things. After that no GUI. I tried to purge nvidia-* and reinstall nvidia-384, that did not work either. Same story with kubuntu-18.04."
1773113,2018-06-09 16:29:57 UTC,"Hello,"
1773113,2018-05-28 06:14:49 UTC,"After upgrade to 18.04 my Asus X550LNV with NVIDIA GeForce 840M [GM108M] is only usable with the nouveau-drivers. I've tried many combos with the NVIDIA drivers but only get to login loop, frozen startup process or can switch to a terminal but in no circumstances can I get to GUI with the NVIDIA drivers installed."
1773113,2018-06-05 13:48:02 UTC,"I've got the same issue with a GTX 1080 on a desktop (lenovo ideacentre). Upgraded over time from 16.04 (as hibernate didn't work to)->17.04.->17.10 and last week to 18.04.
I tried installing nvidia-390 and nvidia-396 with all three methods (bionic package, ppa package, nvidia run script). I even tried to install the older nvidia-387 with nvidia-run script after switching nouveau driver off. Didn't work as some kernel headers don't seem to fit, so installation script aborted. I also tried to upgrade the kernel from 4.15.0-22.24 to 4.15.18, 4.16.13 and newest 4.17 release with ukuu. With newer kernels, I did not even got a gui screen (even with and without nvidia-drivers). I also tried to switch to wayland, but couldn't get it working, allthough I switched to lightdm and seen the login screen with the option (but didn't logged me in successfull)."
1773114,2019-11-26 00:04:09 UTC,"As of 18.04 and still as at 19.10, this is all over the place. Errors left, right and centre."
1773114,2020-01-02 15:38:45 UTC,"Ubuntu 18.04.3 LTS here.
Tried to cp a file from local storage to a GVFS mounted Android Phone."
1773114,2019-12-13 09:37:21 UTC,">Could you maybe report the issue upstream
"
1773114,2019-11-14 08:38:32 UTC,"This error persists in 18.04.3, gvfs version: 1.36.1-0ubuntu1.3.3
I tried to use gcp instead of cp but the result is the same, so this is an gvfs error."
1773114,2018-11-20 15:14:25 UTC,"Don't know if it the same as https://bugzilla.gnome.org/show_bug.cgi?id=795805, or whether I'm even experiencing the same bug, but in my case small files copy fine and large files fail with the invalid argument error all in Nautilus. The bug mentioned states that files copy in Nautilus. It is unclear what size of file was used by the reporter in that bug report."
1773114,2018-11-20 12:27:40 UTC,How can I know if the protocol is SMB2 or not?
1773114,2018-11-13 16:47:41 UTC,"Could be the same as https://bugzilla.gnome.org/show_bug.cgi?id=795805, is that a SMB2 mount?"
1773114,2019-11-14 17:02:42 UTC,Could you maybe report the issue upstream on https://gitlab.gnome.org/GNOME/gvfs/issues ?
1773114,2018-07-04 07:20:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773117,2018-05-24 13:22:27 UTC,"Is this something that eventually worked, or is this something that
completely blocked enable-ha from continuing?
That looks like we're getting a failure asking MAAS about the details of
""4s33ky"" which seems very odd given that it is exactly the machine that we
are running on."
1773117,2018-05-25 17:08:48 UTC,"Hi John.. thanks for you analysis, the error didn't block the enable-ha from continuing.. the action successfully finished, and the controller is in HA mode with no issues."
1773117,2018-06-05 17:57:25 UTC,"So the stacktrace ends up being:
machine-0: 19:04:28 TRACE juju.apiserver.common server RPC error [
{github.com/juju/juju/apiserver/common/networkingcommon/networkconfigapi.go:192: }
{github.com/juju/juju/apiserver/common/networkingcommon/networkconfigapi.go:78: cannot get network interfaces of ""4s33ky""}
{github.com/juju/juju/provider/maas/interfaces.go:330: }
{github.com/juju/juju/provider/maas/environ.go:1756: instance ""4s33ky"" not found}
]"
1773117,2018-06-07 16:36:05 UTC,"Looking at the comments of this bug, it would look as if juju is expecting a machine with a specific ID, but we have not visibility or background information from MAAS. As such, can you clarify a few things:"
1773117,2019-09-19 12:05:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1773130,2018-09-05 20:47:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773131,2020-01-22 15:53:43 UTC,I've found a workaround for ubuntu 18.04:
1773131,2020-01-22 15:57:48 UTC,"As for comment #3, the package you are referring to seems to include what is missing in my ubuntu .deb package. However, my ubuntu version is 18.04, which has ecflow version 4.8.0 and not 4.12.0 as you linked"
1773131,2020-01-22 15:36:30 UTC,Further details on this bug can be found in https://answers.launchpad.net/ubuntu/+source/ecflow/+question/688184
1773131,2020-01-22 15:32:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773131,2020-01-22 15:42:31 UTC,"It's in the Debian package which is weird
https://debian.pkgs.org/10/debian-main-amd64/ecflow-client_4.12.0-1_amd64.deb.html"
1773137,2018-05-25 11:15:59 UTC,apport information
1773137,2019-04-24 08:01:05 UTC,"Mark this as ""Incomplete"" as per comment #24."
1773137,2018-07-23 03:04:14 UTC,I think cause of the bad algorithm that to detect USB cable.
1773137,2018-07-23 02:55:21 UTC,I think cause of the bad algorithm that to detect USB cable.
1773137,2018-07-22 17:27:09 UTC,"So what's the first ""bad"" -rc kernel that introduces the regression?"
1773137,2018-06-17 10:07:57 UTC,"It's not happened when I using the latest mainline kernel (4.17.2-041702-generic)
here I also attached my current dmesg"
1773137,2018-06-16 18:09:02 UTC,"Please try latest mainline kernel. If the issue still happens, then please find the first -rc kernel that introduce the bug."
1773137,2018-06-07 20:50:53 UTC,"When I using Linux kernel 4.13 it's not happening, here I attached dmesg on 4.13."
1773137,2018-05-29 16:35:11 UTC,"Looks like it's the xHC keeps resetting.
Do you have the issue in v4.13?"
1773137,2018-05-25 11:22:39 UTC,apport information
1773137,2018-05-25 11:15:55 UTC,apport information
1773137,2018-05-25 11:15:45 UTC,apport information
1773137,2018-05-25 11:15:51 UTC,apport information
1773137,2018-05-24 11:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773137,2018-05-24 19:36:46 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1773137,2018-05-25 11:15:53 UTC,apport information
1773137,2018-05-25 11:15:30 UTC,apport information
1773137,2018-05-25 11:15:36 UTC,apport information
1773137,2018-05-25 11:15:29 UTC,apport information
1773137,2018-05-25 11:15:40 UTC,apport information
1773137,2018-05-25 11:15:42 UTC,apport information
1773137,2018-05-25 11:15:44 UTC,apport information
1773137,2018-05-25 11:15:47 UTC,apport information
1773137,2018-05-25 11:15:49 UTC,apport information
1773137,2018-05-25 11:15:38 UTC,apport information
1773144,2019-05-29 06:26:47 UTC,The configuration is incorrect as the parameter is named 'datasources' while 'datasource' is being specified.
1773148,2019-10-10 02:41:46 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.31
1773148,2019-10-08 16:56:53 UTC,Verified with systemd/237-3ubuntu10.31:
1773148,2018-12-04 12:23:21 UTC,There are no journald crashes reported for the 10.8 and the 10.10 uploads of systemd which included this change.
1773148,2019-09-30 21:32:49 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1773148,2019-09-30 20:32:58 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1773148,2018-11-20 12:05:34 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1773148,2019-10-01 02:59:52 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1773148,2018-10-24 19:44:44 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1773148,2018-10-24 19:44:13 UTC,This bug was fixed in the package systemd - 229-4ubuntu21.5
1773148,2018-10-22 14:51:44 UTC,No journald watchdog kills yet for the xenial SRU.
1773148,2018-10-15 16:37:34 UTC,This bug was fixed in the package systemd - 239-7ubuntu10
1773148,2018-10-10 15:49:49 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1773148,2018-10-10 15:43:14 UTC,"Note: the Cosmic fix for this is in the unapproved queue, and could in theory be rejected by the release team. The Xenial SRU should land in updates only once Cosmic is resolved."
1773148,2018-05-24 11:34:03 UTC,"I wonder if systemd is actually killing journald, whilst it is stuck fsyncing...."
1773148,2018-05-24 11:29:39 UTC,"journald appears to sigabort upon rotating systemd journal file, in fsync... 😱"
1773148,2018-11-19 14:03:28 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1773150,2020-02-24 20:39:11 UTC,I should add the workaround in my case was downloading the default storage script and creating user uploaded scripts with the patch included.
1773150,2020-02-24 19:59:02 UTC,Here's the patch
1773150,2020-02-24 19:46:30 UTC,I managed to export the default scripts and get them working.
1773150,2019-09-25 08:46:13 UTC,"This is something we need to fix. I'm not sure the attached smartctl output is a valid test case, since it doesn't contain any 0x99 characters."
1773150,2019-04-10 18:52:06 UTC,I am also having the problem.
1773150,2019-01-18 05:27:41 UTC,I'm having this same problem as well.
1773150,2018-12-09 11:50:51 UTC,"Hi Lee,"
1773150,2018-06-20 23:10:45 UTC,I'm having some trouble reproducing this. I download the output uploaded and was able to read it with
1773150,2019-12-10 22:58:40 UTC,"Attached is the output of the smartctl command with the funky ""DELL?"" string inside."
1773152,2018-05-25 06:18:15 UTC,Please ignore my report and close this bug report. I no longer regard this as a bug because a trivial fix exists.
1773153,2018-05-24 11:44:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773159,2018-06-05 13:16:05 UTC,"I was looking through the crash results and saw that libX11.6.3.so seemed to be modified. I used apt-get remove libX11-dev and then re-installed it. I still get a crash ; however, libX11.6.3.so no longer shows a modified status (using version provided by ubuntu). Please review the attached log file."
1773159,2018-05-24 12:10:17 UTC,"StacktraceTop:
 XRebindKeysym (dpy=0x55b604f8611b, keysym=140727646450748, mlist=0x21104f00, nm=0, str=0x7ffdb56073b4 """", nbytes=112683232) at ../../src/KeyBind.c:930
 ?? ()
 ?? ()
 ?? ()
 ?? ()"
1773159,2018-05-25 01:54:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773159,2018-05-25 01:55:18 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/12f1d97cf7a8838894fd1cb2487acfdda0fb2bad"
1773163,2018-05-24 12:31:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773163,2018-05-24 23:55:05 UTC,*** This is an automated message ***
1773163,2020-07-04 17:08:10 UTC,Thanks for reporting.
1773165,2018-10-22 17:30:39 UTC,"@jsalsbury We are still seeing the issue, given ridsaim has not replied lets move forward. I'd like to get some movement on this issue without marking as a Field Critical"
1773165,2018-10-05 21:03:50 UTC,"@Ridsai,"
1773165,2018-10-23 15:04:33 UTC,Where is the openvswitch-switch-dkms package coming from? I don't recognise the package version as anything that's being shipped in Ubuntu?
1773165,2018-10-23 15:05:11 UTC,fwiw the 4.4 intree openvswitch module is recent and up-to-date so use of a ovs supplied dkms module should not be required.
1773165,2018-10-23 15:06:10 UTC,"I built a Xenial test kernel with a revert of the following commit:
cc62065b735f openvswitch: Delete conntrack entry clashing with an expectation."
1773165,2018-10-24 14:01:21 UTC,@Joseph Salisbury
1773165,2018-10-24 10:45:24 UTC,The DKMS package is the one from ovs 2.7.0 with some of our changes to some Nicira extended actions
1773165,2018-10-26 15:00:17 UTC,"After testing it with the test kernel we found that the Linux header contains the Openvswitch.h header files with out any OVS module installed, and these header files are not compatible with OVS2.7, when we tried to build the OVS kernel module"""
1773165,2018-10-29 14:25:41 UTC,"According to the Ubuntu package link, the support for openvswitch-datapath-dkms ended in Trusty.  It is not available as a DKMS package in Xenial rather it is available as a kernel module."
1773165,2018-11-08 15:36:48 UTC,"Hello everybody,"
1773165,2018-11-14 17:04:43 UTC,"@Andrei
Since the driver is now part of the kernel, any changes to the driver, and as a result, the kernel will need to follow the standard upstream kernel patch process found here:"
1773165,2018-10-23 15:07:49 UTC,"Also, do you recall where you got that openvswitch-datapath-dkms from.  Rmadison only reports trusty and precise versions for openvswitch-datapath-dkms."
1773165,2018-05-30 15:22:28 UTC,apport information
1773165,2018-10-23 14:36:36 UTC,Apologies for the late response. I am still seeing the issue with the latest kernel that is (4.4.0-134)
1773165,2018-05-30 15:22:23 UTC,apport information
1773165,2018-05-25 18:30:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773165,2018-05-30 12:38:21 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1773165,2018-05-30 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773165,2018-05-30 14:14:13 UTC,"This issue is seen on a fresh installation when we tried to install the Openvswitch and its kernel module on a node Also the issue was not seen on kernel version 4.4.0-124-generic. But for kernel version 4.4.0-125 and onwards, we face this issue."
1773165,2018-05-30 15:22:09 UTC,apport information
1773165,2018-05-30 15:22:11 UTC,apport information
1773165,2018-05-30 15:22:26 UTC,apport information
1773165,2018-05-30 15:22:15 UTC,apport information
1773165,2018-05-30 15:22:16 UTC,apport information
1773165,2018-05-30 15:22:18 UTC,apport information
1773165,2018-05-30 15:22:19 UTC,apport information
1773165,2018-05-30 15:22:21 UTC,apport information
1773165,2018-05-30 15:22:22 UTC,apport information
1773165,2018-05-30 15:22:13 UTC,apport information
1773167,2017-12-28 15:04:01 UTC,"I now submitted patches for the automatic stream moving:
https://patchwork.freedesktop.org/patch/195132/
https://patchwork.freedesktop.org/patch/195133/"
1773167,2017-12-28 10:19:03 UTC,"It was reported that even with all patches applied, PulseAudio still was being killed when unplugging the HDMI cable. I have now submitted a fix for this."
1773167,2017-12-26 01:02:34 UTC,"I believe this bug prevents sound from working on the Asus Transformer Book series. If the patch is working, could we get an ETA on when if will be merged? If there is anything we can do to speed this along, please let us know."
1773167,2017-11-29 09:10:22 UTC,"Hello,"
1773167,2017-11-09 08:36:05 UTC,I can confirm that these 2 patches:
1773167,2017-11-08 14:19:59 UTC,"Ah, if the pa changes fix the realtime issue they are worthwhile to have even without them fixing hdmi, because currently the realtime issue breaks pa altogether on Bay and Cherrytrail systems. I will start a Fedora pa scratchbuild with these patches added and see if that fixes the need for disabling realtime-scheduling."
1773167,2017-11-08 12:22:05 UTC,"I split the module-card-restore changes to two patches:
https://patchwork.freedesktop.org/patch/187101/
https://patchwork.freedesktop.org/patch/187102/"
1773167,2017-11-08 13:56:18 UTC,"The incorrect jack status is purely a kernel problem, yes. I'm not familiar with the kernel code, unfortunately, so I can't really provide further pointers."
1773167,2017-11-08 13:46:39 UTC,"Thank you for looking into this. So if I've understood correctly, at this point this seems to be (mostly) a kernel bug, correct?"
1773167,2017-11-08 12:11:05 UTC,"The log looks strange. module-card-restore says that it's restoring profile ""off"", but then ""hdmi-stereo"" gets activated anyway."
1773167,2017-11-07 21:00:44 UTC,"Created attachment 135292
pulse.log"
1773167,2017-11-07 21:00:07 UTC,"Sorry, I accidentally hit save, take 2:"
1773167,2017-12-28 15:17:36 UTC,"(In reply to Tanu Kaskinen from comment #51)

> I now submitted patches for the automatic stream moving:
> https://patchwork.freedesktop.org/patch/195132/
> https://patchwork.freedesktop.org/patch/195133/
"
1773167,2017-11-08 14:00:31 UTC,"(In reply to Hans de Goede from comment #43)

> Is there an easy way to check the kernels view of hdmi being plugged in or
> not without using pulse ?
"
1773167,2017-12-28 16:44:49 UTC,"Tanu,"
1773167,2018-05-26 03:39:03 UTC,"Now tracking upstream in:
https://bugs.freedesktop.org/show_bug.cgi?id=100488"
1773167,2018-01-04 16:16:07 UTC,"(In reply to Tanu Kaskinen from comment #54)

> The infinite loop fix is now in master.
>
> The automatic stream moving patch will be replaced with a different approach.
>
> The jack detection fixes are still waiting for review.
"
1773167,2018-06-27 10:48:01 UTC,"Here's information about submitting alsa bugs:
http://alsa-project.org/main/index.php/Bug_Tracking"
1773167,2018-06-23 12:48:49 UTC,"> What does the EDID contain when there is an HDMI output but cable is not plugged in?
"
1773167,2018-06-18 14:31:11 UTC,"(In reply to Hans de Goede from comment #62)

> AFAIK we already have jack-detect for HDMI in newer pulseaudio + kernel
> combos, if there is no external HDMI the i915 should not detect a HDMI calbe
> being plugged in and pulseaudio will ignore the HDMI output.
"
1773167,2018-06-18 14:13:45 UTC,"(In reply to Tanu Kaskinen from comment #60)

> (In reply to russianneuromancer from comment #58)
> > Tanu, is it possible to hide HDMI Audio output on devices without HDMI
> > output? For example on Lenovo Miix2 8 there is no HDMI. As far I remember
> > it's indicated by HDMI EDID that contain only zero, but in necessary I could
> > double check that.
>
> What does the EDID contain when there is an HDMI output but cable is not
> plugged in? If it's possible to distinguish the two cases of no HDMI output
> at all and HDMI output with nothing plugged in, then it would be possible to
> implement automatic ignoring of non-existent HDMI devices in PulseAudio. It
> would seem more appropriate to do that already in the kernel, though.
"
1773167,2018-06-18 13:28:51 UTC,"Closing bug, since the stream moving issue is not specific to the LPE driver."
1773167,2018-06-18 13:27:54 UTC,"(In reply to russianneuromancer from comment #58)

> Tanu, is it possible to hide HDMI Audio output on devices without HDMI
> output? For example on Lenovo Miix2 8 there is no HDMI. As far I remember
> it's indicated by HDMI EDID that contain only zero, but in necessary I could
> double check that.
"
1773167,2018-01-04 13:18:55 UTC,The infinite loop fix is now in master.
1773167,2018-06-16 19:51:22 UTC,I believe that all pulseaudio issues with LPE HDMI have been fixed in the current pulseaudio master git branch as well as in the 12.0 prereleases (the 11.99.x releases).
1773167,2017-11-07 20:51:36 UTC,"Hi All,"
1773167,2018-05-25 11:45:09 UTC,*** Bug 106645 has been marked as a duplicate of this bug. ***
1773167,2018-05-25 02:27:35 UTC,Done.
1773167,2018-05-25 02:03:05 UTC,"Please report the bug to the PulseAudio developers here:
  https://bugs.freedesktop.org/enter_bug.cgi?product=PulseAudio"
1773167,2018-05-25 02:00:36 UTC,It looks like this is what's filling the log (and probably consuming the CPU):
1773167,2018-02-13 19:36:56 UTC,The jack detection fixes are now in master.
1773167,2018-06-16 12:24:06 UTC,"Tanu, is it possible to hide HDMI Audio output on devices without HDMI output? For example on Lenovo Miix2 8 there is no HDMI. As far I remember it's indicated by HDMI EDID that contain only zero, but in necessary I could double check that."
1773167,2017-11-02 18:05:29 UTC,"> Maybe PulseAudio is used only for bluetooth output.
"
1773167,2017-11-02 09:33:51 UTC,Sorry for the delay in replying...
1773167,2017-09-02 13:39:51 UTC,*** Bug 102378 has been marked as a duplicate of this bug. ***
1773167,2017-09-08 07:12:39 UTC,"I found that on Wyse3040, the name of output profile is 'analog-stereo'. Then the proposed fix cannot be applied on it.
After changing /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf, and add 'query-hw-device = yes' in [Mapping analog-stereo] section, PA stop crashing.
But I am wondering if there are any side effects for other platforms."
1773167,2017-09-08 07:12:03 UTC,"Created attachment 134070
pulseauduio log"
1773167,2017-09-08 02:46:28 UTC,"I met a similar issue that is pulseaudio keeps restarting (killed and restarted).
The platform is Cherry Trail and the monitor is Dell P2317H (no audio). Connection type is display port."
1773167,2017-09-05 12:50:31 UTC,Removed the release blocker status.
1773167,2017-10-25 17:30:10 UTC,I'm afraid that I don't know the difference between ~/.etc/pulse/ and /etc/pulse/.
1773167,2017-08-13 18:46:32 UTC,"Hi, i've got the same Problem here:
The worst part is that my working sound was killed as i updated Kernel which now supports hdmi audio.
There was no clear error in pulseaduio log and it costed me a lot time to find out that it's this Problem whcih killed my working internal sound via letting pulseaudio die..
The quickest solution now was blacklisting hdmi audio module, but will try the posted patches when i find time and will report here if they work.
For me this bug is a big bug because it kills working installations without any notice and you can't see any good log showing whats happening..."
1773167,2017-08-03 03:04:04 UTC,"Bastien, do you have time to debug this? The patches have had almost no testing on real hardware, and based on your description, we probably can't apply them before this is sorted out, and I can't debug this alone."
1773167,2017-07-25 22:08:01 UTC,"(In reply to Bastien Nocera from comment #5)

> What is the expected behaviour with those patches?
"
1773167,2017-07-25 22:06:43 UTC,"What does ""pactl list"" print when it's not working?"
1773167,2017-07-25 16:37:22 UTC,"What is the expected behaviour with those patches? For me, on a Surface 3 (CherryTrail) with the patches applied on top of PA 10.0, PulseAudio doesn't crash, but I get no sound from the internal speakers when HDMI is not plugged in."
1773167,2017-06-12 15:47:17 UTC,"Patches submitted:
https://patchwork.freedesktop.org/series/25656/"
1773167,2017-06-04 22:52:05 UTC,"Yes, I think making the jack detection work is important. I understand this[1] message from Takashi so that we should avoid using the device when the monitor isn't plugged in, and for that we need working jack detection."
1773167,2017-05-31 05:53:02 UTC,Do we need to call the second part of the bug an 11.0 blocker?
1773167,2017-04-24 15:09:00 UTC,I sent a patch for the first bug: https://patchwork.freedesktop.org/patch/152433/
1773167,2017-03-30 15:59:25 UTC,"It was reported[1] on alsa-devel that PulseAudio gets killed when trying to use the Intel HDMI LPE driver that was introduced in kernel version 4.11. That probably happens due to excessive CPU use in the IO thread. It's not known what causes the high CPU use, but the discussion revealed some definite shortcomings in PulseAudio when HDMI's underlying hw device is hw:x,0."
1773167,2017-09-11 03:55:09 UTC,"After checking some commits, it seems that I have to upgrade alsa-libs as well. I'll do further testings if I have time."
1773167,2017-09-17 17:28:13 UTC,(Sorry for not responding earlier.)
1773167,2017-09-08 07:11:03 UTC,"Created attachment 134069
pactl list output"
1773167,2017-09-21 19:31:57 UTC,"Created attachment 134414
no-analog.patch"
1773167,2017-10-25 15:43:31 UTC,"(In reply to PhilS from comment #33)

> The first command returned the error ""Failed to connect to bus: No such file
> or directory""
>
> I then looked for the client.conf folder in ~/.config/pulse/ but there was
> no folder of that name.
>
> I did find one in ~/.etc/pulse/ but despite seemingly having root access,
> every time I attempted to edit the file, error: 4 was returned and more
> research indicated that the file is read only and so far I have been unable
> to find a way to write the edited file in order to reproduce the issue and
> provide a log.
"
1773167,2017-10-24 17:01:12 UTC,Thank you for the information Tanu Kaskinen.
1773167,2017-10-24 15:29:07 UTC,"Can you attach the pulseaudio log (with debug logging)? To get the log, follow these steps:"
1773167,2017-10-22 08:28:11 UTC,Millhouse produced a new version of Libreelec (#1020b) with the patches but on testing there was still no audio.
1773167,2017-09-20 20:57:05 UTC,"Created attachment 134389
pulseaudio SIGKILL-ed log"
1773167,2017-10-18 08:55:10 UTC,*** Bug 102877 has been marked as a duplicate of this bug. ***
1773167,2017-10-14 12:32:48 UTC,"(In reply to Bastien Nocera from comment #27)

> (In reply to Hans de Goede from comment #26)
> > (In reply to Bastien Nocera from comment #25)
> > > (In reply to Tanu Kaskinen from comment #24)
> > > > New patches submitted:
> > > > https://patchwork.freedesktop.org/series/31556/
> > >
> > > I've tested Fedora 26's PulseAudio which includes this series of patches[1]
> > > and the alsa-lib change from comment 23, and I can't get any output on the
> > > internal audio anymore.
> >
> > Do you have a ucm file for your SoC / codec combo? :
> >
> > https://github.com/plbossart/UCM
> >
> > mkdir /usr/share/alsa/ucm  and then copy all the *dirs* from that git repo
> > there.
>
> I have a version of it, as the sound works in older versions. I think it's a
> kernel bug, see:
> http://mailman.alsa-project.org/pipermail/alsa-devel/2017-October/126407.html
"
1773167,2017-10-13 22:24:31 UTC,"(In reply to Hans de Goede from comment #26)

> (In reply to Bastien Nocera from comment #25)
> > (In reply to Tanu Kaskinen from comment #24)
> > > New patches submitted:
> > > https://patchwork.freedesktop.org/series/31556/
> >
> > I've tested Fedora 26's PulseAudio which includes this series of patches[1]
> > and the alsa-lib change from comment 23, and I can't get any output on the
> > internal audio anymore.
>
> Do you have a ucm file for your SoC / codec combo? :
>
> https://github.com/plbossart/UCM
>
> mkdir /usr/share/alsa/ucm  and then copy all the *dirs* from that git repo
> there.
"
1773167,2017-10-20 19:37:28 UTC,*** Bug 103299 has been marked as a duplicate of this bug. ***
1773167,2017-10-13 18:07:00 UTC,"(In reply to Tanu Kaskinen from comment #24)

> New patches submitted:
> https://patchwork.freedesktop.org/series/31556/
"
1773167,2017-10-08 16:53:28 UTC,"New patches submitted:
https://patchwork.freedesktop.org/series/31556/"
1773167,2017-10-04 19:53:22 UTC,"I haven't had proper reminders about the patch set, so I kind of forgot about it. I plan to simplify the patches a bit soon."
1773167,2017-09-28 15:59:04 UTC,Thank you for working on this.
1773167,2017-09-28 10:31:26 UTC,"I think it's a real fix. Not a nice fix, but the fact is that things will break in PulseAudio if alsa defines ""front"" to be the same as ""hdmi"". Strictly speaking ""front"" is allowed to be any device that has a front-left,front-right channel map, but in practice it shouldn't overlap with other device definitions, because PulseAudio needs to tell analog and HDMI devices apart. There's no separate definition for analog devices, so PulseAudio assumes that ""front"" is analog, and usually that assumption is correct."
1773167,2017-09-25 07:46:19 UTC,(In reply to Tanu Kaskinen from comment #19)
1773167,2017-10-13 18:15:56 UTC,"(In reply to Bastien Nocera from comment #25)

> (In reply to Tanu Kaskinen from comment #24)
> > New patches submitted:
> > https://patchwork.freedesktop.org/series/31556/
>
> I've tested Fedora 26's PulseAudio which includes this series of patches[1]
> and the alsa-lib change from comment 23, and I can't get any output on the
> internal audio anymore.
"
1773171,2018-05-24 13:58:00 UTC,https://docs.openstack.org/releasenotes/ceilometer/ocata.html#prelude
1773171,2018-05-24 14:38:22 UTC,"Three changes were needed in the end for mitaka:
1) Add an events definition file so that ceilometer can transform the notification data
[event]
definitions_cfg_file = /home/ubuntu/ceilometer-6.1.5/etc/ceilometer/event_definitions.yaml"
1773172,2018-07-11 18:06:54 UTC,"I might be missing something here, but this seems to suggest that the only way to get disk quotas working on an AWS machine using the official linux-aws kernel is to compile your own kernel including them -- there's no package to install."
1773172,2018-07-12 11:17:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773172,2019-08-26 07:18:34 UTC,"After bug 1836706, I think we can close this.
If you need the quota support, please install the linux-modules-extra-aws package."
1773174,2019-05-12 18:17:09 UTC,@Hannie:
1773174,2019-05-05 14:09:13 UTC,Mind if I bump this ticket?
1773174,2019-05-12 16:42:58 UTC,"As lead of Ubuntu Dutch Translators and Gnome Dutch translators, I'd say, go ahead. I have no idea what I, as a translator, can do about this problem."
1773174,2019-09-25 11:08:58 UTC,@ Gunnar: I will do just that. Thanks for the link.
1773174,2019-02-04 11:52:26 UTC,"Hannie, yes, there's a bug in the translation. A fix was proposed by different people last year. The message string this bug was about had a fix proposed by me on 2018-09-26, but I think there were others that helped with other strings (although I might be getting my languages mixed up)."
1773174,2019-11-01 14:12:02 UTC,"@Hannie: Zou je de suggestie voor de resterende vertaling kunnen goedkeuren (zie de opmerking van Gunnar hierboven)?
https://translations.launchpad.net/ubuntu/eoan/+source/snapd/+pots/snappy/nl/215/+translate
Bij voorbaat dank."
1773174,2020-05-09 12:35:51 UTC,I just did a fresh install of Ubuntu 20.04 and ran into this issue. I have sent an email to the translation team hoping that this issue can be resolved.
1773174,2020-05-23 08:36:54 UTC,@Nic: fixed. Thanks for the alert.
1773174,2019-09-25 14:24:21 UTC,"@Hannie: The POT has changed since I posted those links, so they are obsolete. This one remains to be fixed:"
1773174,2019-02-02 15:33:57 UTC,"All I can find is https://translations.launchpad.net/ubuntu/bionic/+source/snapd/+pots/snappy/nl/+translate
I am not sure if this bug has anything to do with us translators at Ubuntu Dutch Translators"
1773174,2018-10-22 14:14:04 UTC,"Timo, I appreciate your concerns and mostly agree with what you're saying, with some ""but""s."
1773174,2019-02-01 20:47:41 UTC,"@Timo, I thought we'd fixed the apt issue. I'll ask."
1773174,2019-02-01 17:32:35 UTC,These warnings are still happening on the current Disco release.
1773174,2019-01-08 23:08:44 UTC,There is a manual fix (or work-around?) suggested here https://forum.snapcraft.io/t/weird-error-message-whenever-i-run-the-snap-command/6418/16 ...
1773174,2018-12-18 12:54:17 UTC,Looks like that was fixed in https://github.com/snapcore/snapd/commit/7d418342 but there has been no new version upload to Ubuntu since that commit
1773174,2018-12-16 17:11:17 UTC,Is something wrong with the Dutch translation? In what module can I find these strings? What does it say in English?
1773174,2018-12-09 12:20:50 UTC,"This bug is similar to
https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1806761"
1773174,2018-10-22 15:50:37 UTC,"I'd like to +1 Timo's comment. Even after filing a bug, the warning is printed every time the snap command is run until the bugfix propagates to the stable repository, which may be months (in this case). Alternatively, an environment variable to silence these warning would be appreciated. (It seems to me this kind of problem should theoretically be discoverable during build time, although the particular build system may not support it.)"
1773174,2018-10-21 20:49:54 UTC,Thanks for finding the source of this puzzling message! I noticed John and Daniel made translation suggestions for both of the offending messages; what needs to happen to merge them?
1773174,2018-09-26 15:26:47 UTC,Sorry we didn't spot this report! We're fixing it now.
1773174,2018-06-04 20:32:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773174,2019-02-01 23:13:17 UTC,"@John, thanks for replying. I just double-checked and I stand corrected. I can only reproduce with snap itself, not any more with apt. (The rest of my comment still stands.)"
1773175,2018-05-24 18:29:06 UTC,"Hello Andrey,"
1773175,2018-05-25 06:37:08 UTC,"After reading some Qt documentation and examples, I tried"
1773184,2018-05-25 10:39:42 UTC,The problem is there with 4.17-rc6
1773184,2019-07-26 12:14:07 UTC,"Just to note: since one of the kernel upgrades, this issue is not present anymore. I'm not sure which version fixed it."
1773184,2019-02-11 23:30:48 UTC,"just adding some more info.
i also deploy openstack rocky on a ubuntu 18.04 host"
1773184,2018-05-25 11:46:20 UTC,"In the above, the middle one that crashes (so the 1st level of guests)."
1773184,2018-05-25 11:45:21 UTC,"It started right after I tried to run our OpenStack CI (so the nested operation) on Bionic (with OpenStack Queens). Previously I used Xenial (with kernel 4.4.0), that still works.
The host kernel is still from Xenial."
1773184,2018-05-25 11:29:57 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1773184,2018-05-24 19:35:48 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1773184,2018-05-24 15:03:06 UTC,apport information
1773184,2018-05-24 15:03:15 UTC,apport information
1773184,2018-05-24 15:03:13 UTC,apport information
1773184,2018-05-24 15:03:11 UTC,apport information
1773184,2018-05-24 15:03:10 UTC,apport information
1773184,2018-05-24 15:03:09 UTC,apport information
1773184,2018-05-24 15:03:07 UTC,apport information
1773184,2018-05-24 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773184,2018-05-24 15:03:17 UTC,apport information
1773189,2018-05-25 07:53:29 UTC,I found the bug with lightdm --debug :
1773191,2020-07-23 08:45:03 UTC,"Chris, does it seem okay after you have done some more tests?"
1773191,2019-10-04 19:23:04 UTC,I found the issues and corrected them at the tip of https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/csharp/lp-1773191-WIP-materialize-btype
1773191,2019-10-04 19:12:54 UTC,"Mike,"
1773191,2018-09-21 19:46:24 UTC,"I've pushed some more commits that improve the upgrade script and make use of the newly linked mbts.last_btype field.  Still WIP, but the more eyes the merrier."
1773191,2019-09-13 16:13:47 UTC,"I am not sure what is the state of the issue. However, in 3.3.2 in the patron billing interface grids  and in the print templates the values of billing and payment types and the transaction types are still untranslated, see the attachment."
1773191,2018-09-19 15:36:53 UTC,"Bill,"
1773191,2018-08-09 15:37:53 UTC,"Last Billing Type strings are multiple layers of un-translatable.  Many originate in the code and then, as Remington points out, they are stamped as plain text on the transaction summary with no option for run-time translation."
1773191,2018-08-09 14:17:16 UTC,"One complication with ""Last Billing Type"" is that those values are stored as text in money.materialized_billable_xact_summary.  So while the normal translation process might apply to the values in config.billing_type, it probably doesn't apply to the money table."
1773191,2018-07-26 14:37:35 UTC,"Confirmed in 3.1.3
I have added the “webstaffblocker” tag. This one is an obstacle to using the web client in production for the non-English speaking users. As another ""localization webstaffblockers"" the bug is critical for circulating staff who must quickly respond to various difficult situations in contact with patrons."
1773191,2018-05-27 18:05:37 UTC,"Also ""Payment Type"" values (like credit_payment, cash_payment...)  in the patron payment history  interface are untranslated. However, in this case I don´t think those values have ever been available for translation."
1773191,2018-09-19 16:14:38 UTC,I've pushed the db+IDL changes I think will be required to a WIP collab branch available at:
1773194,2018-05-25 13:55:28 UTC,"Aha!
Apparently Referencer was removed from Debian unstable https://tracker.debian.org/news/937606/removed-122-2-from-unstable/"
1773194,2018-05-25 18:42:53 UTC,"Thank you for your answer,
I successfully build and install referencer 1.2.2 from source on ubuntu 18.04 (just need to patch the bug #1645639) and then :
./configure
make
make install"
1773196,2018-05-24 16:25:47 UTC,"Hi Hadmut,"
1773196,2018-06-25 00:45:02 UTC,Any idea of a workaround? QGis is of limited use in its current state on Ubuntu/Debian and I don't understand why :(
1773196,2018-06-25 00:45:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773196,2018-06-25 06:45:27 UTC,"Hi,
On Mon, 25. Jun 2018 at 00:45:02 -0000, Stefano Maffulli wrote:

> Any idea of a workaround? QGis is of limited use in its current state on
> Ubuntu/Debian and I don't understand why :(
"
1773200,2018-05-24 15:43:32 UTC,"Solved: killed dpkg (sudo killall dpkg), then in Synaptic in tab 'Edit' chose 'Fix broken', then 'Apply changes'"
1773200,2018-05-25 05:45:32 UTC,"Ok, so it was a flaky one off issue.
Thanks for reporting back after the fix.
I'll close the bug as ""invalid"" then as it is not a bug to be fixed in an Ubuntu package."
1773200,2018-05-25 06:15:45 UTC,It looks more like a debconf issue to me:
1773207,2019-11-26 13:30:50 UTC,"Oh, right, looks like the one in /usr/lib was also one you installed, as you wrote the package one is being shipped in /usr/lib/x86_64-linux-gnu/"
1773207,2019-11-26 09:54:51 UTC,"the files were probably not identical, diff works on text content, not on binaries"
1773207,2019-11-26 09:10:56 UTC,"Ah, thanks, Nautilus works again after removing /usr/local/lib/libsqlite3.so.0. Wonder where the file in /usr/local/lib came from. It's also strange that the files in /usr/lib and /usr/local lib were identical according to diff."
1773207,2019-11-26 10:55:46 UTC,"The file in /usr/lib and /usr/local/lib are both identical. I kept the old one in a separate folder and it has the same sha1sum. But the file in /usr/lib seems to be spurious as well, since it is not associated with any package and variants with newer timestamp of libsqlite3.so.0 persists in /usr/lib/x86_64-linux-gnu/ and /usr/lib/i386-linux-gnu/, Nautilus still works after having moved /usr/lib/ libsqlite3.so.0 into quarantaine as well as well."
1773207,2019-11-25 09:08:22 UTC,"Thank you for your bug report, could you give the output of those commands?
- ldd -r /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
- dpkg -l | grep sqlite"
1773207,2019-11-25 02:42:48 UTC,"The bug still persists. sqlite-autoconf is neither installed on my machine nor contained in the repository. Purging and reinstalling natilus, sqlite and libtracker did not help."
1773207,2018-10-29 21:35:16 UTC,I had to uninstall sqlite-autoconf to solve the problem.
1773207,2018-06-04 18:16:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773207,2019-11-26 02:08:15 UTC,Output of ldd and dpkg is attached
1773207,2019-11-26 08:13:36 UTC,"Thanks, the missing symbol is explained by the ldd output"
1773221,2018-05-25 20:02:29 UTC,Issue exists in Evergreen 3.1
1773222,2019-03-11 14:41:10 UTC,Does the file /etc/lightdm/lightdm-gtk-greeter.conf contain the desired timeout value?
1773222,2019-05-11 04:17:23 UTC,[Expired for lightdm-gtk-greeter (Ubuntu) because there has been no activity for 60 days.]
1773222,2019-05-11 04:17:25 UTC,[Expired for lightdm-gtk-greeter-settings (Ubuntu) because there has been no activity for 60 days.]
1773223,2018-09-26 13:53:47 UTC,Is your home directory on NFS? I am getting the exact same issue. Output of dmesg:
1773223,2018-09-26 17:13:00 UTC,My home directory is indeed on NFSv4.
1773223,2018-11-05 11:54:27 UTC,This is going to be a bit tricky.
1773230,2018-06-15 12:34:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773230,2020-08-10 01:46:52 UTC,gmic (2.2.3)
1773232,2018-05-24 19:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773232,2018-05-24 18:50:58 UTC,apport information
1773232,2018-06-22 20:12:05 UTC,When trying to do: make -j`nproc` deb-pkg
1773232,2018-06-17 08:06:12 UTC,How you do a bisect:
1773232,2018-06-16 20:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773232,2018-06-05 19:46:55 UTC,"I've did some more testing with multiple versions. I've figgured out the bug got introduced between kernel 4.15.0-rc1 and 4.15.0-rc2
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc2/
If there is a clear way somewhere that explains me how to do a git bisect, I'd love to help out and narrowing the bug down to the commit."
1773232,2018-05-25 05:57:10 UTC,apport information
1773232,2018-05-25 05:57:09 UTC,apport information
1773232,2018-05-24 22:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773232,2018-06-22 21:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773232,2018-05-24 21:47:25 UTC,I've tested it on version 4.14 and it seems to boot up every time. However It will only turn on 1 display instead of 3 and at a low resolution. I've repeated the test 5 times with the same results. after that I have tested 4.17 and it hung up again at boot.
1773232,2018-05-24 20:29:37 UTC,"Allright, I will test out multiple kernels and share the results. However my hardware might not be supported for older kernels, Atleast my multi monitor screen setup will not work < 4.17"
1773232,2018-05-24 19:34:47 UTC,"Also, would it be possible for you to test some prior kernels to see if there was a previous good version?  If there is a prior good kernel, we can perform a kernel bisect to identify the commit that introduced this bug."
1773232,2018-05-24 19:32:58 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1773232,2018-05-24 19:14:17 UTC,apport information
1773232,2018-05-24 19:14:15 UTC,apport information
1773232,2018-05-24 18:50:59 UTC,apport information
1773232,2018-05-24 20:30:18 UTC,That means I can not test all bugs mentioned. only the starting up bug
1773232,2018-07-26 05:45:29 UTC,Sorry for the late reply. Please install libssl-dev.
1773240,2018-06-12 10:27:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773246,2019-07-23 14:17:03 UTC,Same here with 3840x2160 (scaling 1.2x) + 1920x1080 (scaling 2.4x)
1773246,2021-01-13 06:01:49 UTC,"Seems nobody cares :(
I am affected yb this too. Multimonitor setup"
1773246,2020-08-24 11:57:30 UTC,"I'm having the same problem on neon,20.04 and 1.5 scaling factor"
1773246,2020-04-27 12:03:02 UTC,I updated to Kubuntu 20.04 where I no longer have this bug.
1773246,2020-03-23 12:42:55 UTC,This also affects me I use scaling of 1.5 and a 1920x1080 and a 4840x2160 screen.
1773246,2019-11-13 08:19:07 UTC,"The offset is ~290px to the left for me (the far right is just 290px of white). I have three screens with their tops aligned, from left to right: 1440x2560 (rotated so bottom of the monitor is now to the left); 3840x2160; 1440x2560 (rotated opposite to first monitor). Ubuntu 18.04.3 LTS. I configured the monitors using NVIDIA X Server Settings."
1773246,2019-05-29 19:13:12 UTC,"It affects me too, i have 2 monitors: 4k + rotated FullHD"
1773246,2019-03-18 12:55:21 UTC,"Same here.  I have Macbook with retina display, and bigger Apple display connected.  When trying to capture rectangular region, a good portion of the screen is outside the boundary, and I haven't found a way to access that area to make my screenshot."
1773246,2019-01-28 19:10:03 UTC,I have the same problem. This does not happen with a big wide monitor
1773246,2019-01-13 18:47:50 UTC,"Still encountering this, it is super-annoying!"
1773246,2018-07-06 15:20:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773246,2018-05-24 20:53:38 UTC,"> apt-cache policy kde-spectacle
kde-spectacle:
  Installed: 17.12.3-0ubuntu1
  Candidate: 17.12.3-0ubuntu1
  Version table:
 *** 17.12.3-0ubuntu1 500
        500 http://ca.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status
"
1773246,2019-05-02 11:49:07 UTC,This bug affects me as well. I have 3 monitors: 2 FullHD and a 4K one.
1773249,2018-05-24 21:16:19 UTC,I should add that I do see other examples in our logs where retrieving these settings does not lead to the error. I've attached an example of that for reference.
1773249,2018-05-24 21:10:49 UTC,See attached log excerpt.
1773249,2018-06-07 18:24:55 UTC,"Since applying the fix for bug 1774703, we see this with a great deal of frequency. Like, no one can catalog in the web staff client kind of frequency."
1773254,2019-04-28 11:34:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773255,2018-06-03 09:46:14 UTC,Via-Shapes:
1773255,2018-06-01 18:48:18 UTC,"The question is, do we want to provide shaped vias?  If so, then the severity should be set to wish list.  If not, then it should be set to wont fix.  AFAIK, this is first time anyone has requested shaped vias.  Do all of the commercial EDA apps provide support for shaped vias?"
1773255,2018-05-30 20:08:02 UTC,I agree.
1773255,2018-05-29 08:06:28 UTC,"I am not sure replacing a via with a pad is a good idea, as it requires a new component which does not exist in the schematics. In the current state the connectivity is preserved, so I would not say it is a critical bug."
1773260,2019-02-08 23:25:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773265,2021-02-12 20:59:28 UTC,"This is still mostly the case. Checked our system (3-4-5) and also the Feedback Fest ""Blake's Test Server"" (2/12/2021)."
1773268,2018-05-25 02:24:25 UTC,It appears you're still using lightdm that is not part of bionic.
1773268,2018-05-25 02:24:49 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1773268,2018-05-30 15:32:09 UTC,Apport output attached.
1773271,2018-05-24 23:23:13 UTC,"Please close the bug, the package is named kwin-x11-dbgsym"
1773271,2018-05-24 23:26:18 UTC,"Looks like kwin-x11-dbgsym is ALSO not available, so consider this still a bug"
1773274,2018-06-17 08:00:11 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1773274,2019-03-01 14:58:27 UTC,Same here on Kubuntu 18.04
1773276,2018-06-06 01:38:21 UTC,"Moved to:
https://gitlab.freedesktop.org/libinput/libinput/issues/22"
1773276,2018-06-20 16:45:03 UTC,"Actually, I confused trackpoints with trackpads. Indeed, there's no fix for trackpoints yet."
1773276,2018-06-20 14:05:26 UTC,"This would be fixed by upgrading to libinpu 1.11. Peter Hutteter put in some great effort into analyzing touchpad data from Windows and MacOS, as well as the old Synaptics driver, and I must say, after upgrading from 1
10.5 to 1.11 in Fedora, it's just on par with MacOS and Windows now."
1773276,2018-06-14 18:56:36 UTC,Moved to: https://gitlab.freedesktop.org/libinput/libinput/issues/34
1773276,2018-05-30 02:07:33 UTC,"Thanks for confirming the bug. In the meanwhile, for anyone encountering this problem, you can work around it by installing libinput10 and libinput-bin from artful."
1773276,2018-05-29 22:16:42 UTC,Note that I'm not using Wayland. The erratic behaviour is present under X as well.
1773276,2018-05-29 20:05:34 UTC,"There is a bugreport about this in wayland:
https://bugs.freedesktop.org/show_bug.cgi?id=106448
But it doesn't seem to have been filed by the same author as this bug."
1773276,2018-05-25 05:14:50 UTC,"I have an X61, a T470s and a thinkpad usb keyboard and can't repro that jumping issue, but the acceleration speed is indeed much different on the latter two. There are separate bugs for that I guess, and modifying the mouse accel slider does help somewhat."
1773276,2018-05-25 02:27:45 UTC,"Please report the problem to the libinput developers here:
  https://bugs.freedesktop.org/enter_bug.cgi?product=wayland&component=libinput"
1773276,2018-05-30 01:56:44 UTC,That's OK. The upstream bug tracker is just poorly designed and libinput bugs (that affect X too) are filed under Product=Wayland :(
1773291,2018-05-25 13:45:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773291,2020-06-03 20:51:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:"
1773291,2020-08-03 04:17:24 UTC,[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.]
1773307,2019-12-17 19:07:28 UTC,"I reported this over 6 months ago and my PC has since changed, but the keyboard and mouse are the same. Anyway, here you go:"
1773307,2019-11-08 18:03:39 UTC,would you please try from the command line tool?
1773307,2019-12-17 19:08:46 UTC,"$ fwupdmgr update
cannot handle firmware requirement not-child"
1773307,2019-12-17 19:32:50 UTC,The not-child extension is supported in fwupd 1.2.7 and later (https://github.com/fwupd/fwupd/commit/b62c3a4fae1104c4a1052adc7b3196afa8c33307).  Ubuntu 18.04 currently contains fwupd 1.2.5.
1773307,2020-06-05 14:46:33 UTC,"new install of 20.04 using fwupdmgr --version 1.3.9 and still affects me.  was able to go to fwupd.org, download the [hash?]-Logitech-Unifying-[version].cab file and install with fwupdtool install [filename] successfully.  One failure during install:"
1773310,2018-08-25 13:34:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1773310,2020-07-08 11:57:31 UTC,"As mentioned in the Debian bug report, this issue has been resolved. I've verified that on newer Ubuntu releases (19.10 and upwards), oz has a strict dependency on python(3)-monotonic."
1773316,2018-06-18 09:00:13 UTC,This bug was fixed in the package python-apt - 1.6.1
1773316,2018-06-18 08:50:13 UTC,"The verification of the Stable Release Update for python-apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1773316,2018-09-12 08:10:55 UTC,"JFTR, in case anyone is looking at this:"
1773316,2018-07-04 14:52:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773316,2018-06-11 20:23:13 UTC,"I also ran unattended-upgrades and aptdcon --system-upgrade, both of which performed normally."
1773316,2018-07-04 14:41:01 UTC,"This update causes a regression that is tracked in bug 1780099 - notably the __hash__ of an apt.Package can change after opening, so if used in a set, or as a dict key, the package won't be found anymore. The regression is less worse than the previous state, but will be fixed shortly."
1773316,2018-06-11 19:53:29 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1773316,2018-06-08 18:29:22 UTC,This bug was fixed in the package python-apt - 1.7.0~alpha0~ubuntu3
1773316,2018-06-11 20:22:43 UTC,Fix works fine:
1773316,2018-06-06 19:07:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773318,2018-05-25 07:34:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/570528"
1773318,2019-05-30 15:42:43 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/570528
Reason: This is nearly a year old with no updates and might be fixed now in Train with blueprint request-filter-image-types so I'm going to abandon it."
1773318,2019-05-30 15:48:11 UTC,"The blueprint request-filter-image-types might not solve the problem here, since that blueprint just makes sure the scheduler picks a host with a virt driver that supports the given image type on the server but that doesn't mean we can live migrate from a libvirt driver host using raw to one using qcow2. Anyway, the patch was super old and needed to be updated anyway."
1773318,2020-05-28 09:46:59 UTC,Confirmed the bug based on the original (now abandoned) review https://review.opendev.org/570528
1773320,2020-01-13 17:42:13 UTC,This bug is still present in hplip 3.19.12.
1773320,2018-07-25 07:30:25 UTC,Srinivas:
1773320,2018-06-22 06:15:12 UTC,"HI zdohnal,"
1773320,2018-06-18 12:34:37 UTC,"Required screenshot - printer model, python3 version and OS version (Fedora 29) are there too. hp-setup ends with the same traceback on Fedora 28 too (when I don't apply my patch)."
1773320,2018-06-18 10:36:10 UTC,"Hi zdohnal,"
1773320,2018-06-22 08:40:15 UTC,Result is the same for F27 too.
1773320,2018-06-06 13:55:26 UTC,Without reverting this change:
1773320,2018-06-06 11:59:46 UTC,"Hi zdohnal,"
1773320,2018-06-06 09:51:02 UTC,"Hi Srinivas,"
1773320,2018-06-05 14:20:47 UTC,"Hi zdohnal,"
1773320,2018-06-06 13:55:46 UTC,See updated patch.
1773326,2018-05-25 10:57:29 UTC,"Seems like the offending file is in
libstdc++-devel.x86_64                 8.0.1-0.20.fc28          @fedora"
1773326,2018-05-25 12:41:07 UTC,"probably related to
https://bugs.launchpad.net/inkscape/+bug/1768958"
1773326,2019-04-22 14:33:33 UTC,Closing as a fix has been committed in 1.0alpha. I believe there's a chance an updated version of Inkscape from the Fedora repository is fixed too.
1773328,2018-05-29 05:43:21 UTC,"Hi, i think this duplicate bug report https://bugs.launchpad.net/glare/+bug/1773329"
1773328,2018-05-29 05:59:12 UTC,"Thanks Deepak, probably it was because of some system glitch :)
Marked other one as invalid as there is no option for marking it as duplicate."
1773335,2018-11-16 03:45:33 UTC,"We've removed kern-sec tests from checkbox, marking this fixed"
1773357,2018-10-05 01:18:39 UTC,To ask for clarification:
1773357,2018-10-09 02:58:02 UTC,"PR for bundlechanges package: https://github.com/juju/bundlechanges/pull/43
PR for Juju 2.3: https://github.com/juju/juju/pull/9291"
1773357,2018-10-05 23:03:14 UTC,Hi Peter - sorry I wasn't around to talk through this on IRC.
1773357,2018-10-05 13:26:11 UTC,"Thanks, I think we've got some cases to help us fix it and if you're ok for
the moment we'll make updates to the code which will be in the future
releases and we can document what to watch out for for those without the
fix."
1773357,2018-10-05 13:00:33 UTC,Think there may have gone something wrong with the workaround.
1773357,2018-10-05 07:29:08 UTC,"I've got a better understanding of this now, and a workaround I think."
1773357,2018-10-05 04:53:50 UTC,"I got in touch with Vladimir above, he gave me the bundle in question:"
1773357,2018-10-04 19:34:14 UTC,So the code seems to indicate that there's a machine being created but no application for that new machine. I tried to create a simple bundle that added machines w/o any placement and that fails to deploy.
1773357,2018-10-09 23:14:22 UTC,PR for Juju 2.4: https://github.com/juju/juju/pull/9293
1773357,2018-10-04 19:20:36 UTC,"Ok, so from what I can tell this matches to 2.3.8, as John notes the code even says"
1773357,2018-10-04 18:35:43 UTC,Just to help follow the traceback can you confirm the juju version please?
1773357,2018-10-04 18:24:32 UTC,This is impacting our contractual commitment to a customer to deploy a cloud within a deadline; I'm subscribing ~field-high.
1773357,2018-10-02 10:19:44 UTC,I have encountered this again upon running juju  --debug deploy ./$bundle --map-machines=existing
1773357,2018-09-06 20:29:24 UTC,Can you please include the bundle?
1773357,2018-09-06 10:55:21 UTC,"+1 on 2.4.3-xenial-amd64, the same behaviour http://paste.ubuntu.com/p/wwdjdJf6gG/"
1773357,2018-05-28 06:29:33 UTC,"That particular line of code says:
        deployedApps := func() string {
                apps := h.applicationsForMachineChange(change.Id())
                // Note that we always have at least one application that
justifies the
                // creation of this machine.
                msg := apps[0] + "" unit"""
1773357,2018-05-27 21:07:59 UTC,Which bundle? And are you able to run the command with higher logging to provide some extra debugging information?
1773357,2018-10-04 19:07:25 UTC,Feedback is the tag is correct and used heavily for many of the machine.
1773359,2018-07-12 07:13:34 UTC,"We don't actually support the azure instance-id syntax, but I was wondering
if we could enable that syntax and if it would lead to better experience
for you."
1773359,2018-06-08 09:42:11 UTC,"Manual provisioning was necessary because juju add-unit does not add new machines to an existing Availability Set, and Azure does not allow us to change the Availability Set of a given VM."
1773359,2018-07-12 08:15:54 UTC,"So if we were adding by instance-id, presumably we would ask the provider
for any additional details that we need to know about the machine.
""ssh:hostname"" just treats it as any machine (it could be a machine in a
completely different datacenter, etc), so we don't make any assumptions
about it being 'similar' to the other machines in your model."
1773359,2018-05-25 13:36:03 UTC,"On review, the symptoms only occur for the manually-provisioned unit in this azure environment.  Our suspicion is that codepaths relating to the cluster relation are reporting via a query on the instance-id, and azure is telling juju about the private IP for the original unit but the ID for the manual unit is just manual:<public-ip>, so it derives from that."
1773359,2018-07-12 08:41:54 UTC,"On 12Jul2018 08:15AM (-0000), John A Meinel wrote:

> So if we were adding by instance-id, presumably we would ask the
> provider for any additional details that we need to know about the
> machine.  ""ssh:hostname"" just treats it as any machine (it could be a
> machine in a completely different datacenter, etc), so we don't make
> any assumptions about it being 'similar' to the other machines in your
> model.
"
1773359,2018-06-07 16:25:36 UTC,"We don't have a way of knowing that the machine is actually an instance from Azure (vs being any other machine that you might have running on some other cloud, or in some other data center)."
1773359,2018-07-12 07:40:36 UTC,"On 12Jul2018 07:13AM (-0000), John A Meinel wrote:

> We don't actually support the azure instance-id syntax, but I was wondering
> if we could enable that syntax and if it would lead to better experience
> for you.
"
1773363,2018-06-29 12:52:44 UTC,"This is a harmless failure. The kernel simply added a new flag for p{read,write}v2, and the test is to check one bit higher than the highest flag the test thinks is valid. That bit turns out to be the new flag, so the operations do not fail as expected."
1773363,2018-03-10 14:30:29 UTC,4.16-rc4 has
1773363,2020-11-05 06:03:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773363,2018-12-07 21:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773363,2018-12-07 21:14:48 UTC,Kernel patch:
1773363,2018-08-01 05:35:54 UTC,"This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project ""GNU C Library master sources""."
1773363,2018-03-10 14:26:45 UTC,"On x86-64, under 4.16.0-rc2, I got"
1773363,2018-06-01 16:49:33 UTC,"This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project ""GNU C Library master sources""."
1773363,2018-05-11 10:28:46 UTC,"This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project ""GNU C Library master sources""."
1773363,2018-04-03 20:21:34 UTC,Fixed by f2652643d7234c08205b75f527191c2e2b35251f.
1773363,2018-04-03 19:20:19 UTC,"This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project ""GNU C Library master sources""."
1773363,2018-06-29 12:36:23 UTC,"FAIL: misc/tst-preadvwritev2
FAIL: misc/tst-preadvwritev64v2"
1773364,2018-05-25 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773364,2018-05-25 13:05:24 UTC,The first problem is that CONFIG_CC_STACKPROTECTOR is no longer a Kconfig option but is instead defined in a makefile (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2bc2f688fdf8808de4f36be563ccdb0bde7c0c54). The qrt security tests need to be updated to account for this.
1773366,2019-10-07 00:35:04 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1773366,2019-10-07 12:02:51 UTC,"At this point we aren't using 4.17 anywhere, so this seems irrelevant."
1773369,2018-05-25 13:28:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773369,2019-06-07 19:16:33 UTC,This looks like it has been fixed
1773370,2018-08-30 11:38:43 UTC,"I'm facing the same issue with ubuntu 18.04.01
I get the following error:
The following packages have unmet dependencies:
 libncurses5-dev : Depends: libtinfo5 (= 6.1-1ubuntu1) but 6.1-1ubuntu1.18.04 is to be installed
                   Depends: libncurses5 (= 6.1-1ubuntu1) but 6.1-1ubuntu1.18.04 is to be installed
                   Depends: libtinfo-dev (= 6.1-1ubuntu1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages."
1773377,2018-07-27 08:23:22 UTC,"> instance -> dnsmasq -> bind9 (managed by designate-bind charm) -> upstream DNS server
"
1773377,2018-07-30 03:10:37 UTC,"> Hope the attached diagram makes sense why those relations would be impossible (provider range is outside of Juju model).
"
1773377,2018-07-31 09:13:37 UTC,"Think the best approach is to define extra-binding network(s) as allowed_recursion_nets when recursion is set and allowed_recursion_nets is empty. That way, if a user wants to expose BIND to the internet and have anyone using it as recursive DNS server, the user must define allowed_recursion_nets=any."
1773377,2018-08-09 07:06:19 UTC,"As discussed with Pedro on IRC, what we could do is:"
1773377,2018-08-09 07:54:51 UTC,"> this will allow us to bind this ""dns-provider"" endpoint to a space on the designate-bind side (no need for extra-bindings)
"
1773377,2018-08-28 08:16:01 UTC,https://review.openstack.org/#/q/topic:bug/1773377
1773377,2018-08-28 08:31:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597021"
1773377,2018-08-28 08:51:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597029"
1773377,2018-11-19 20:35:59 UTC,"While this relation is very useful, I think it stops short of addressing an additional concern with having to update upstream DNS conditional forwarders when designate-bind is redeployed/units added/updated."
1773377,2019-01-15 11:44:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630947"
1773377,2019-01-15 11:45:21 UTC,"Change abandoned by Pedro Guimarães (<email address hidden>) on branch: master
Review: https://review.openstack.org/630947"
1773377,2018-07-26 13:34:07 UTC,"> In order to provide external name resolution for instances designate-bind charm also needs to configure recursion in bind9 config (currently recursion is disabled) and allow queries from IP addresses of compute nodes hosting dnsmasq daemons.
"
1773377,2018-07-27 08:34:38 UTC,Hope the attached diagram makes sense why those relations would be impossible (provider range is outside of Juju model).
1773384,2019-09-19 11:58:21 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1773384,2018-06-06 02:59:18 UTC,"This can be improved slightly, by increasing the number of columns spanned in the first part of the header, but the problem will remain at some resolutions. This needs someone from design to consider whether a different layout might help, possibly where the power state and hostname/status don't share the same row."
1773389,2018-06-01 02:49:02 UTC,"Reviewed:  https://review.opencontrail.org/43308
Committed: http://github.com/Juniper/contrail-controller/commit/3a7c08e8302c82d9acdd2f37549837267c17cd29
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1773389,2018-05-25 14:52:55 UTC,"Review in progress for https://review.opencontrail.org/43308
Submitter: Jean-Philippe Braun (<email address hidden>)"
1773390,2018-05-25 16:25:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1773390,2018-05-31 10:51:59 UTC,changing target to Kubuntu
1773390,2019-11-23 05:18:28 UTC,Has there been any progress with this?
1773390,2020-05-02 11:07:13 UTC,Has there been any progress with this?
1773391,2018-05-25 15:04:21 UTC,Kudos to @dmitriis for tracing this.
1773391,2020-04-30 20:21:05 UTC,We have addressed this issue by adding a self-serve image feature.
1773405,2018-05-25 16:45:43 UTC,"The new name you gave this bug is confusing too :) There is no such thing as an 'untagged vlan' in the maas model - vlans can be both tagged or untagged, depending on how they're connected to interfaces."
1773405,2019-09-19 11:58:23 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1773411,2018-06-11 10:49:40 UTC,"Hi all,"
1773412,2018-06-12 00:16:00 UTC,"Review in progress for https://review.opencontrail.org/43708
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-12 00:16:06 UTC,"Review in progress for https://review.opencontrail.org/43709
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-12 00:16:11 UTC,"Review in progress for https://review.opencontrail.org/43710
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-12 00:16:17 UTC,"Review in progress for https://review.opencontrail.org/43711
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-12 02:00:26 UTC,"Reviewed:  https://review.opencontrail.org/43705
Committed: http://github.com/Juniper/contrail-packages/commit/47c0ef19f452c99365bcab69e62adef74c2808be
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1773412,2018-06-14 05:26:27 UTC,"Reviewed:  https://review.opencontrail.org/43708
Committed: http://github.com/Juniper/contrail-packages/commit/cca0b7a133c202c31182442906fbfc5aa87cf646
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1773412,2018-06-12 20:20:09 UTC,"Reviewed:  https://review.opencontrail.org/43711
Committed: http://github.com/Juniper/contrail-packaging/commit/af5e97565e763b93191e63e45135d30bd424ecf7
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1773412,2018-06-13 13:09:52 UTC,"Reviewed:  https://review.opencontrail.org/43710
Committed: http://github.com/Juniper/contrail-packages/commit/90e203841e3b47fc85d76244164290ff71a86d17
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1773412,2018-06-14 05:26:39 UTC,"Reviewed:  https://review.opencontrail.org/43709
Committed: http://github.com/Juniper/contrail-packaging/commit/6f0286aefb427c56447e8b52e2acfc3bf42d655f
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1773412,2018-06-11 23:35:08 UTC,"Reviewed:  https://review.opencontrail.org/43589
Committed: http://github.com/Juniper/contrail-packaging/commit/21d68158e7143b26fd2eb51f39848bf92d8a8db6
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1773412,2018-06-12 04:56:49 UTC,"Reviewed:  https://review.opencontrail.org/43706
Committed: http://github.com/Juniper/contrail-packaging/commit/5a5c1bf0235360f9d8aa41b2c492ed910e20e61b
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1773412,2018-06-11 23:35:06 UTC,"Reviewed:  https://review.opencontrail.org/43588
Committed: http://github.com/Juniper/contrail-packages/commit/23d946cffd9c73147530670aa7345bdafa7ce190
Submitter: Zuul (<email address hidden>)
Branch:    R4.0"
1773412,2018-06-11 22:44:11 UTC,"Review in progress for https://review.opencontrail.org/43706
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-11 22:33:55 UTC,"Review in progress for https://review.opencontrail.org/43705
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-07 07:31:38 UTC,"Reviewed:  https://review.opencontrail.org/43587
Committed: http://github.com/Juniper/contrail-packaging/commit/1d38d96b97286c61ebee9f51b12ee7a663eda2df
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1773412,2018-06-07 07:31:35 UTC,"Reviewed:  https://review.opencontrail.org/43586
Committed: http://github.com/Juniper/contrail-packages/commit/96f3ecf2af69eaf1069544d63e4b0528d80ab551
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1773412,2018-06-07 03:57:45 UTC,"Reviewed:  https://review.opencontrail.org/43590
Committed: http://github.com/Juniper/contrail-packages/commit/1c34ad09ec94494153f87464c981ceca1615abd5
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1773412,2018-06-07 03:34:26 UTC,"Reviewed:  https://review.opencontrail.org/43591
Committed: http://github.com/Juniper/contrail-packaging/commit/70ebf60751833a33cbb1d8131d2603eec6316470
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1773412,2018-06-06 20:42:41 UTC,"Review in progress for https://review.opencontrail.org/43591
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-06 20:42:27 UTC,"Review in progress for https://review.opencontrail.org/43590
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-06 20:42:09 UTC,"Review in progress for https://review.opencontrail.org/43589
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-06 20:42:00 UTC,"Review in progress for https://review.opencontrail.org/43588
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-06 20:41:43 UTC,"Review in progress for https://review.opencontrail.org/43587
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-06 20:41:32 UTC,"Review in progress for https://review.opencontrail.org/43586
Submitter: Santosh Gupta (<email address hidden>)"
1773412,2018-06-06 20:10:01 UTC,"Ubuntu has contrail-cassandra-{status|repair}.py in /usr/share/contrail-utils directory.
root@sangupta-u14:/usr/share/contrail-utils# pwd
/usr/share/contrail-utils
root@sangupta-u14:/usr/share/contrail-utils# ls contrail-cassandra-*py
contrail-cassandra-repair.py  contrail-cassandra-status.py
root@sangupta-u14:/usr/share/contrail-utils#"
1773412,2018-05-31 17:33:54 UTC,"Had to add Kafka user manually in the testbed because the script that adds the user failed mid way, while provisioning."
1773414,2018-12-21 15:50:13 UTC,This is still an issue in 3.2.
1773416,2019-10-15 10:57:08 UTC,"This is indeed expected, at least at a technical level, because each snap interacts with a private view of /tmp. As a form of isolation and to avoid accidental dependencies created through data shared through /tmp, snapped applications need a better form of exchanging data. I realize that there is nothing useful that can be done about this problem for now, apart from saving the files in your home directory for round-trip between programs."
1773422,2019-09-19 12:05:42 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1773422,2019-09-20 12:32:40 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1773422,2018-05-25 17:52:39 UTC,"FWIW, MAAS' goal is to manage the switch as well, and this would be implemented in the context of switch management."
1773422,2018-05-25 20:14:03 UTC,"I don't think I've ever filed this before - I've filed something
similar for discovering vlan ID's though."
1773428,2018-05-25 20:36:48 UTC,I can confirm the home library is being used as context for copy editing permission on a 3.0.7 system. But I am seeing that the working location is being used as context as well.
1773428,2019-03-27 18:26:53 UTC,Adding that we have experienced this issue on a 3.1.10 system.
1773429,2018-05-25 20:17:20 UTC,"Additionally, fixing this bug would require addressing the 'interface names are too long' from https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1773353"
1773429,2018-07-02 14:56:21 UTC,long interface names bug is fix committed - we should stable pick those fixes.
1773433,2019-01-04 15:08:46 UTC,I guess adding this package back is simple because pdftk-java is in cosmic (https://packages.ubuntu.com/cosmic/pdftk-java)
1773433,2019-01-04 15:12:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773433,2020-03-09 19:36:25 UTC,https://launchpad.net/ubuntu/+source/pdfchain/1:0.4.4.2-1build1
1773442,2019-09-19 11:58:25 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1773442,2018-05-25 20:05:42 UTC,python-libvirt doesnt allow ssh with password. That is why its implemented using virsh command.
1773442,2018-05-25 21:27:00 UTC,https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Connections.html#idp13463584 # Seems to imply otherwise.
1773442,2018-05-26 03:23:30 UTC,That is using sasl not ssh. You must configure virsh specifically for that. If you read below it shows you that.
1773444,2018-09-27 20:13:40 UTC,This is because audacious registers itself are the handler for folders.
1773444,2018-10-03 21:58:50 UTC,"Cool, thanks!"
1773447,2018-05-31 22:56:18 UTC,"Part of this was due to the no-proxy values having defaults if they are
not set."
1773448,2018-05-26 03:19:20 UTC,Thanks for your report!
1773450,2019-09-13 13:44:26 UTC,"Currently (in 3.3.2), the folder names (Templates, Reports, Outputs) are displayed translated, however, the rest of the interface is still untranslated, see the attachment."
1773450,2018-09-14 05:38:32 UTC,"Using Ben's test server, I can confirm that the problem persists in Evergreen 3.2 beta1."
1773450,2018-09-14 11:52:12 UTC,"When testing another bug in the reporter (in Ben´s 3.2 beta sandbox), I have found funny thing. The part of the legacy interface (particularly names of the folders and some messages in the pop-up windows) were displayed in the Czech language even when I was using English interface at the moment (see the attachment). I tried to clear both the cache and the cookies because had switched from Czech to English (and vice versa) previously. Still, the interface remained in the Czech language after clearing cookies and cache.
I installed the Opera browser, that I was quite sure had never been used on the given workstation, to exclude the influence of some previous language settings in the browser. again, the part of the interface mentioned above remained in the Czech language even in English locale.
I am still not sure if this behavior is not any coincidence, however, I wonder if this could not be related to the language settings of the operating system (which was Czech on the workstation where I tested the reporter)."
1773450,2018-09-14 19:36:47 UTC,"Just a little note - my screenshot (posted earlier today) comes from an operating system (Fedora) in English with Chrome being also in English. I got the same result in Firefox (also in English), actually. So maybe the operating system and/or web browser language settings have something to do with it (as Eva suggests)."
1773451,2018-05-27 13:14:31 UTC,I completely agree with this 100%. This feature is actually one of the reasons that Altium is my favorite layout tool... it's the only one I know of that has this feature.
1773451,2018-06-10 14:32:20 UTC,"dont forget this one, it would be very handy.    recently i also did
several lines of text, one line at a time,  to add a table of jumper
connections to the back of a board."
1773455,2019-09-19 11:58:29 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1773457,2020-03-27 10:10:50 UTC,"Any chance to see a fix in 20.04?
We need to be able to encrypt (k)ubuntu data when ubuntu is installed alongside windows.
/home encrytion was not perfect but it was better than nothing."
1773457,2020-03-13 06:30:56 UTC,"+1. Fortunately I rarely have to use Windows, but I still do have to use it sometimes for work and study, and as such must maintain a dual boot on all of my systems. Please implement the fix."
1773457,2020-03-04 10:32:06 UTC,+1 to this issue. My new work laptop only has one drive. We require Windows for some tasks but Linux for others. Full drive encryption is mandatory for laptops and other portable devices.
1773457,2019-11-06 18:58:51 UTC,"+1 on this issue. Win 10 is required in my work environment, but not for *everything*; I can use Ubuntu for most of my work, but whole disk encryption *is* an absolute requirement. I've primarily used Ubuntu for more than a decade, and would much prefer to keep using it as my daily OS, but this is a blocker for me."
1773457,2018-09-07 07:06:02 UTC,"Phillip, the goal is BOTH secure boot AND encryption. This bug report specifically deals with the latter, not the former. Why are you so against encryption? I don't understand!"
1773457,2019-08-14 15:58:16 UTC,"Definitely, /boot should be encrypted. It has been proven possible, so there's every reason to do so."
1773457,2019-08-14 15:09:04 UTC,"Any change to be able to install an encrypted Ubuntu 19.10 alongside of a win10?
I don't know if /boot should be encrypted but not being able to encrypt anything out of the box in 19.04 is a security regression. Crypaetup may not be perfect but it used to be good enough in many usecases."
1773457,2018-12-03 19:50:10 UTC,"I would like to support this bug report from the perspective of a security oriented, pragmatic user, likely the kind of which there are plenty out there."
1773457,2018-09-10 14:52:34 UTC,"On 9/7/2018 3:06 AM, Paddy Landau wrote:

> If you are arguing that /boot shouldn't be encrypted, this is a direct
> contradiction of what you wrote earlier that malware can be loaded into
> the ESP; so why couldn't malware be loaded into /boot?
"
1773457,2018-09-09 21:40:26 UTC,">  Encryption is for data privacy and as I said before, nothing you consider private should be in /boot.
Well, not entirely correct. Encryption is also for tamper resistance, so it is still very useful even if nothing in /boot is private.
"
1773457,2019-09-13 08:18:04 UTC,"Agreed.
""Full-system encryption needs to be supported out-of-the-box"" full system shall mean 'the Linux partitions' an not 'the full disk'.
In 19.04 it is not possible to install an encrypted kubuntu in dual boot with windows10 without playing with the command line."
1773457,2020-04-04 10:08:25 UTC,+1 to have a full disk encryption (boot+root+swap+home) in the next Ubuntu release out of the box.
1773457,2020-04-17 14:23:39 UTC,"@jjakob — Jernej, thank you for this useful and important information. I have included your link in the instructions:
https://help.ubuntu.com/community/ManualFullSystemEncryption
https://ubuntuforums.org/showthread.php?t=2399092"
1773457,2020-04-17 13:33:00 UTC,"By the way, PureOS has the same bug, so I think it goes all the way up to Debian.
Here's a guide I created on how to move a unencrypted install to fully encrypted (works with Ubuntu as well):"
1773457,2020-04-17 22:31:07 UTC,"TJ wrote this:
https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019"
1773457,2020-04-18 11:04:46 UTC,"@tomreyn — Tom, thank you for posting this. I have added it to these three documents:
https://help.ubuntu.com/community/ManualFullSystemEncryption
https://ubuntuforums.org/showthread.php?t=2399092
https://help.ubuntu.com/community/FullDiskEncryptionHowto"
1773457,2020-04-19 15:20:08 UTC,"TJ's howto from comment #47 is much better as it allows installing directly to the target disk, mine needs you to install it to a second disk and copies over to the target disk."
1773457,2020-05-29 08:52:30 UTC,Any updates on this? This is really critical in my opinion. My user case:
1773457,2020-05-29 10:11:20 UTC,"Sad story.
This bug should be critical as it has large security impact. Encryption should be the norm.
It shall be possible to install an encrypted (k)ubuntu without being techy."
1773457,2020-12-21 21:07:36 UTC,"Encryption should also be possible without LVM. LVM is very good, but if you are using for example BTRFS, you may don't want to use both at the same time. Should just be an option."
1773457,2020-12-21 21:22:27 UTC,"Well it's an issue indeed but the fact that no encryption is possible
without having to deal with the command line is much worst."
1773457,2020-12-22 19:18:20 UTC,"This doesn't look like it'll ever be done. Based on past experience, I don't think that Canonical takes encryption seriously."
1773457,2020-12-22 19:22:01 UTC,"No it is not a grub issue. It's an issue with the installer which does not
provide this option anymore. Wishlist..kind of but I think it is much
closer to a big security issue than to a wishlist. The net result is that
people do install kubuntu without any encryption."
1773457,2020-12-22 21:25:27 UTC,"The issue reported here is that /boot is not encrypted in the supported configurations. Which is meh - we don't have much authenticated encryption, so boot can still be manipulated. Sealed TPM measurements address the problem of verifying the bootloader, kernel, initrd, and the configuration better. It does not provide security by obfuscation as encryption does, but that obfuscation can be circumvented - you can modify an encrypted boot partition and still get a working system - and authenticated encryption that would also authenticate the content is not stable yet."
1773457,2020-12-22 21:37:17 UTC,"Right.
https://bugs.launchpad.net/bugs/1799550 has been opened in 2018 to track
the dual boot issue. This is the security issue I was referring to. Sorry
for the confusion."
1773457,2020-04-17 13:29:05 UTC,My attempts to install 20.04 beta desktop or 18.04 LTS netinstall expert mode with full disk LUKS encryption failed.
1773457,2018-09-06 20:07:56 UTC,"If your goal is secure boot, then you need signature verification.  Encryption is not required for that.  Encryption is for data privacy, and as I said before, nothing you consider private should be in /boot."
1773457,2019-10-11 16:39:08 UTC,"The issue remains the same with 19.10 (beta I tried yesterday).
The 19.10 Kubuntu installer cannot install an encrypted kubuntu in dual boot with e.g. windows10."
1773457,2018-08-28 15:43:00 UTC,"What you are talking about is signature verification.  You need the firmware to verify the signature on the kernel and initrd, using a custom self signing key only.  That is unrelated to whether /boot is encrypted or not."
1773457,2018-05-26 10:08:50 UTC,full disk encryption is in the installer since several years (i think since 2012 but i might mis-remember) already ... see some howto site like: https://linoxide.com/ubuntu-how-to/two-methods-to-protect-your-data-using-ubuntu-disk-encryption/
1773457,2018-05-26 11:06:35 UTC,"Thank you, Oliver. That link was in fact one of the (many) reference pages used in creating the instructions. Unfortunately, it isn't actually full system encryption: /boot isn't encrypted, which allows for a clear attack vector."
1773457,2018-05-26 12:30:58 UTC,"then you shoud probably adjust the bug title to something like ""full disk encryption should also encrypt /boot"" and mark it as ""whishlist"""
1773457,2018-05-26 13:11:19 UTC,"Oliver, I've amended the title (the body of the report already says so). I don't know how to change it to ""wishlist"", although really, as I say, in today's world, it is nearly approaching a legal requirement (at least in the EU because of GDPR) than merely a wish."
1773457,2018-05-26 13:31:17 UTC,"Oliver, another point that I missed in my previous comments is that the full-disk encryption that Ubuntu uses does not play nicely with other systems. E.g., if you have Windows (true of most users), it will delete the entire Windows system plus its data."
1773457,2018-06-14 14:54:28 UTC,"What do you mean by ""attack vector""?  /boot does not contain any sensitive files that you would want to protect from an attacker."
1773457,2018-06-14 16:26:57 UTC,"Phillip, do you feel that malware cannot be loaded onto /boot? If you are right, that would take me by surprise!"
1773457,2018-06-14 17:00:27 UTC,Encryption does not stop someone from writing to the disk and putting different software on it.  It just stops them from being able to read your data.
1773457,2018-06-14 18:24:03 UTC,"Phillip, you are correct only if the software partitions are unencrypted (as is the case with the existing default method). This bug report is about fully encrypting the entire system — that's everything, including swap and both root and /boot."
1773457,2018-06-20 15:27:48 UTC,That does not stop someone plugging in a usb stick and booting the machine with malware there.
1773457,2018-06-20 17:48:28 UTC,"Yes, I know this, Philip, but unlike with the current setup (where you can add malware to root and the kernel), with this method, the only thing that they can change is the ESP (EFI System Partition), because everything else is fully encrypted in a single partition using LVM within LUKS."
1773457,2018-06-21 15:57:36 UTC,"Phillip, I think that you need to take this discussion to somewhere like Ubuntu Forums."
1773457,2018-06-22 13:04:28 UTC,"On 6/21/2018 11:57 AM, Paddy Landau wrote:

> If we were to accept your argument, we would say that there is no point
> whatsoever in encrypting anything, and we should eliminate the current
> option to encrypt the home folder when installing Ubuntu.
"
1773457,2018-06-21 14:45:22 UTC,"Who cares *where* the malware is?  Encryption doesn't stop someone from compromising the machine.  You can boot the machine from a USB stick, then boot the hard disk in a virtual machine, let it look like it is running normally for you to come put your password in to decrypt the disk, and the malware on the USB stick ( or in the ESP ) can then capture your password and steal your data."
1773457,2018-06-22 14:44:08 UTC,"On 6/22/2018 9:35 AM, Paddy Landau wrote:

> Sorry, no, that's not why I raised this bug report, Phillip. There
> definitely *is* a point in preventing someone from sneaking into your
> office (say, over the weekend), and loading malware in order to either
> modify or steal your data. This type of espionage does actually happen.
>
> Full disk encryption prevents this, because I really don't think that
> you can load a virtual machine into the (at most) 400Kb of free space in
"
1773457,2018-08-22 09:29:46 UTC,@Jonathan Polom (s0nic0nslaught)
1773457,2018-08-21 21:42:48 UTC,I meant to add this in my preceding comment.
1773457,2018-08-21 21:37:18 UTC,"I am with Paddy on this one. This isn't a ""nice to have"" feature but an essential feature that any operating system with even a sliver of hope of enterprise-wide adoption needs to support in the second decade of the 21st century. Windows has the benefit of fully supporting TPM based encryption and secure boot which so each item loaded at boot time has a cryptographic signature which is verified by the secure boot system. Modifications will result in an un-bootable system. Mac OS X has FileVault along with System Integrity Protection which similarly will make it very difficult to boot poisoned pieces of the operating system to extract bits of information that should be protected on disk by encryption. Ubuntu, at this point, does not offer a level of tamper-resistance similar to this without implementing unsupported modifications that (like this method) are not for ordinary users who just want to install something ""that works."" This is both deeply disappointing to a security and privacy minded individual like myself and it WILL prevent adoption of this system in areas where complete system encryption and built-in tamper resistance are non-negotiable requirements (defense, financial, legal, healthcare, and more -- most industries are very security conscious now)."
1773457,2018-06-22 13:35:14 UTC,"> The point is to prevent people from getting your data if they steal your computer, not to prevent them from modifying the computer.
"
1773457,2018-08-04 16:50:14 UTC,@Dimitri Thanks for your comments. I understand where you are coming from.
1773457,2018-08-03 21:14:26 UTC,The source package for the current version of GRUB used in Ubuntu is grub2; reassigning.
1773457,2018-08-06 00:54:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773457,2018-08-03 20:38:43 UTC,"If you want to preserve other OS and setup encrypted partitions by hand, you can do so, since forever using the mini.iso  d-i installer, and install ubuntu-desktop task."
1773457,2018-08-03 19:31:06 UTC,@Phillip
1773457,2018-07-31 09:51:42 UTC,"I have just discovered that home-folder encryption has been removed from Ubuntu because, it seems, it is considered buggy and under-maintained. Full-disk encryption is recommended as an alternative."
1773457,2018-06-23 10:16:13 UTC,"Sorry, Phillip, yes, you're right about the ESP space ­— more like 100Mb. I was typing incorrectly; what I meant was at most 400Mb."
1773457,2018-08-03 21:14:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773457,2018-08-28 16:49:41 UTC,"@psusi Yes, that's correct, and should be done in addition to this request. In other words, both are necessary."
1773463,2018-05-31 10:14:46 UTC,I think we could wait for upstream to fix this as we have a working version already with a slightly different syntax than the one used in the RFC due to the fact that LXD and snapd are also affected.
1773463,2018-05-28 04:20:59 UTC,"* is not supported (as it wasn't supported by the underlying Go proxy code).
However
""bar.com"" matches foo.bar.com, as does "".bar.com""
So while we don't allow ""*.bar.com"" it can be expressed as just ""bar.com""
and "".bar.com""."
1773463,2018-05-28 04:24:47 UTC,"In code:
                p = strings.ToLower(strings.TrimSpace(p))
                if len(p) == 0 {
                        continue
                }
                if hasPort(p) {
                        p = p[:strings.LastIndex(p, "":"")]
                }
                if addr == p {
                        return false
                }
                if p[0] == '.' && (strings.HasSuffix(addr, p) || addr ==
p[1:]) {
                        // no_proxy "".foo.com"" matches ""bar.foo.com"" or ""
foo.com""
                        return false
                }
                if p[0] != '.' && strings.HasSuffix(addr, p) &&
addr[len(addr)-len(p)-1] == '.' {
                        // no_proxy ""foo.com"" matches ""bar.foo.com""
                        return false
                }
                if _, net, err := net.ParseCIDR(p); ip != nil && err == nil
&& net.Contains(ip) {
                        return false
                }"
1773463,2018-05-31 07:48:53 UTC,"I'd say the wildcard syntax is more common as it is described in a relevant RFC: https://tools.ietf.org/html/rfc4592#section-2.1.3
""
A wildcard ""blocks itself"" in the sense that a wildcard does not match its own subdomains.  That is, ""*.example.""  does not match all names in the ""example."" zone; it fails to match the names
   below ""*.example.""
"""
1773463,2018-05-31 09:26:57 UTC,"I'm fine with supporting *.domain.com, just wanted to point out that Go
doesn't, by default, support it, though it does support .domain.com, etc.
(So the same limitations are part of lxd and probably snaps.)"
1773464,2020-05-27 17:53:56 UTC,Continues to be an issue in 3.5
1773464,2019-08-12 17:52:47 UTC,Issue still present in 3.3
1773464,2020-02-21 22:11:14 UTC,"This is bugging our front line staff as well.  It's an extra step to clear out the patron's name, which has some privacy ramifications when we share our screens with patrons."
1773465,2018-09-17 15:31:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773468,2018-05-28 04:41:16 UTC,we should understand why backup from an HA controller is leading to being unable to restore it to a single controller. I wouldn't think we were saving things like the replicaset settings.
1773468,2018-05-30 15:07:35 UTC,Hi John. This scenario is present in the documentation so a reference to this issue will be needed. Let me know if you have some text you'd like me to include so as to make this more understandable to the reader.
1773468,2018-05-30 19:33:57 UTC,"Peter, are you restoring the HA archive to the same controller or a new controller?"
1773468,2018-05-30 21:42:29 UTC,"Heather, new."
1773468,2018-07-30 04:17:49 UTC,[Expired for juju because there has been no activity for 60 days.]
1773468,2019-06-12 09:44:30 UTC,"https://discourse.jujucharms.com/t/manual-steps-to-restore-a-backup/1330
are the steps that need to be done to do a manual backup from an HA controller.  I believe it missed the cut for working on this cycle."
1773470,2020-01-21 09:56:32 UTC,"This bug is much more important than the title suggests. Cusp nodes are not snapping to much at all! They snap to other cusp nodes, tangents and maybe a few more things, but not to anything related to bounding boxes. Cusp node snapping needs to be widely tested."
1773470,2020-03-31 11:57:44 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1773476,2020-12-14 19:41:34 UTC,"Actually would have been a bug against either apt or dpkg, which failed to clean up /var after Kernel package removal.  Since upgraded to ubuntu Focal, closing Bug."
1773476,2018-05-30 03:24:14 UTC,VERIFIED.  Found a /var/lib/initramfs-tools/4.8.0 and a /var/lib/initramfs-tools/4.8.0-56 that shoudn't be there.
1773476,2018-05-28 14:38:04 UTC,Observed sequence of sbins when software-updater called apt-get upgrade linux-firmware:  Cross-checking initramfs-tools and depmod for any misbehaviors that might exacerbate what I've observed.
1773476,2018-05-30 04:12:47 UTC,"SOLVED via sudo rm -rf /var/lib/initramfs-tools/4.8.0 && sudo rm -rf /var/lib/initramfs-tools/4.8.0-56!  Recommend check for bug(s) in apt and dpkg, as automatic housecleaning faile me in this specific case."
1773476,2018-05-26 06:57:07 UTC,apport information
1773476,2018-05-26 06:57:06 UTC,apport information
1773476,2018-05-26 02:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773476,2018-05-27 23:02:13 UTC,Update:  A purge and reinstall of linux-firmware produces same results.  Summary therefore:
1773476,2018-05-29 12:28:20 UTC,"This is not a problem with linux-firmware itself, it does is trigger a rebuild of the initrd for all installed kernels but it's initramfs-tools which does this. It will try to generate an initrd for all kernels with a file in /var/lib/initramfs-tools, so it sounds like you have a file there for that kernel but no corresponding directory for that kernel in /lib/modules."
1773481,2018-07-13 10:51:46 UTC,I'm surprised that a beta version is included here. After an upgrade from 16.04 to 18.04 Anki suddenly looked quite different and some features where missing (e.g. my saved searches disappeared). Also some popular plugins like AwesomeTTS are not ready for 2.1 beta yet.
1773481,2018-07-13 10:52:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773481,2018-08-17 17:47:34 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855942 has some information on the background
1773481,2019-03-30 20:23:21 UTC,The bug persists in Linux Mint 19.1.
1773497,2018-05-26 07:00:23 UTC,This also affects firejail: https://github.com/netblue30/firejail/issues/1917
1773497,2018-05-30 15:14:25 UTC,Easily reproducible:
1773497,2018-05-30 23:20:34 UTC,Filed https://bugs.documentfoundation.org/show_bug.cgi?id=117922
1773497,2018-05-31 05:42:24 UTC,Thanks!
1773498,2018-05-29 16:30:21 UTC,This change was made by a bot.
1773502,2018-05-28 01:49:58 UTC,Thanks. That explains a lot. I think gnome-shell is presently too slow to be able to handle 1080p on a Celeron 847. But we are working on a bunch of different optimizations that should help in future.
1773502,2018-05-27 09:42:01 UTC,"Resolution: 1920 X 1080 (16:9), with a refresh rate of 60,00 Hz, I use an HDMI connection:"
1773502,2018-05-27 06:54:53 UTC,"Nevermind, it's obvious you're using Xorg sessions."
1773502,2019-05-15 08:23:41 UTC,"^^^
Moved to bug 1756508"
1773502,2019-05-16 01:21:22 UTC,"AFAIK, gnome-system-monitor is one of those rare apps which are software rendered (because GTK) but also try to animate at a smooth frame rate."
1773502,2019-05-15 07:00:51 UTC,"I have this bug, triggered by eclipse on latest Bionic.
I do not see any gnome shells running though.
Do we know any workarounds?"
1773502,2018-05-27 06:53:55 UTC,"Oooh... that makes sense now, thanks."
1773502,2019-05-15 07:12:48 UTC,"If I run eclipse from a docker container (with -v /tmp/.X11-unix:/tmp/.X11-unix ), then no cpu overuse.
It might related to that in this case eclipse cannot connect to dbus."
1773502,2018-05-26 09:37:48 UTC,And what web pages are good examples of high CPU usage?
1773502,2018-05-26 08:07:27 UTC,1. Are you running any apps when the CPU usage is high?
1773502,2018-05-26 08:08:10 UTC,"The CPU seems taken by Xorg (see screen shot). When the gnome-shell proc take most of the CPU, the overall CPU seems to be reduced after some seconds."
1773502,2018-05-26 08:10:55 UTC,"I was running Thunderbird, Firefox, System Monitor (and a console with the top command). But it happen too with no app launched or just Firefox."
1773502,2018-05-26 09:51:15 UTC,"I restarted my computer 3 time.I launched FF and the top command. The home page of FF is https://www.bing.com/?cc=be. I opened a second tab with maps.google.com. Everything was find. I lauched system monitor and then, the CPU of one core jumped to 100 %, even after closing the maps.google.com tab (see screenshot).
When I'm in system monitor, the tab Ressources take 100 % of 1 CPU. If I switch to the tab Processes and change the ordering of the list, it goes down. When I come back to the Ressources tab, it reaches again the top. Same thing if I go from the Ressources view to the File System tab and back to the Resources tab (see screenshot from 11:50 AM)."
1773502,2018-05-26 08:17:38 UTC,apport information
1773502,2018-05-26 08:55:55 UTC,"OK. Please reduce the problem down to a single app, like just Firefox. Now, please let us know:
  1. The version of Firefox; and
  2. What web page(s) cause the biggest problem."
1773502,2018-05-26 09:10:54 UTC,I use Firefox Quantum 60.0.1 (64 bits)for Ubuntu with the modules eid Belgium (issue was already present before installing this module) and uBlock Origin. The module Open H264 Video Codec provided by Cisco 1.7.1 is installed.
1773502,2018-05-26 08:17:37 UTC,apport information
1773504,2018-11-12 02:51:56 UTC,Can someone else confirm this issue?
1773504,2019-06-20 13:11:40 UTC,I'm experiencing this same issue again in Ubuntu 19.04; the login screen keeps the monitor on forever.
1773507,2018-05-26 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773507,2018-10-02 15:57:26 UTC,"Odd. CONFIG_COMPAT is set. You set the bug as CONFIRMED by yourself, but didn't add any information on the kernel version. Which one would that be?"
1773507,2018-10-02 15:59:04 UTC,"root@calabresa:~# uname -a
Linux calabresa 4.18.0-8-generic #9-Ubuntu SMP Mon Sep 10 16:12:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@calabresa:~# criu check --all
Looks good.
root@calabresa:~#"
1773515,2019-11-25 19:50:41 UTC,I ran into this issue. Workaround fixed it perfectly.
1773515,2019-10-29 22:15:17 UTC,I have an unfinished patch that moves the snap-confine apparmor profile out of /etc entirely. I will try to finish and propose it.
1773515,2019-01-07 19:00:02 UTC,"Zygmunt, you shouldn't override the dpkg behavior as there is an expectation on a Debian based system on how things in /etc are treated and what dpkg expects. That said, you could change the packaging in various ways. Eg, stop shipping it in /etc at all or disable the profile via /etc/apparmor.d/disable. Alternatively, don't install it to /etc, but instead /usr somewhere and during postinst use ucf or similar to copy it into place such that dpkg considers it a config file instead of a conffile (I suggest looking at the Debian policy manual on config file vs conffile)."
1773515,2019-01-07 07:21:38 UTC,"Fink Nottle: AFAIK apparmor should not be breaking. The parser loads all profiles but doesn't stop on a profile that fails to load. The error message is displayed but remaining profiles are loaded anyway. It there some specific profile that you were expecting to see loaded that did not after you removed, but not purged snapd?"
1773515,2019-01-07 07:18:50 UTC,I have a hunch that this happens because /etc/* is marked as a configuration file and not automatically removed unless the package is purged. I think we could special case that file and remove it on regular package remove using postrm script.
1773515,2019-01-06 22:58:29 UTC,This is still broken. A key security feature of the OS breaks if you uninstall some garbage package. I wouldn't have noticed it if I hadn't seen the logs.
1773515,2018-07-26 20:14:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773515,2018-07-26 20:19:55 UTC,"This has also bugged me for some number of months but the work around is really easy -- just use
apt purge snapd
instead of
apt remove snapd"
1773515,2018-05-30 19:01:39 UTC,May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine'
1773515,2018-05-30 17:27:33 UTC,"""Does anything happen if you run:"
1773515,2018-05-30 15:31:02 UTC,The half-installed packages are probably the cause. Does anything happen if you run:
1773515,2018-05-30 09:02:13 UTC,BTW as I don't plan to reinstall snapd the next day I did a find
1773515,2018-05-30 09:00:19 UTC,"I do 99% of my package management with apt-get so it was removed via the command ""sudo apt-get remove snapd"""
1773515,2018-05-30 05:00:14 UTC,The maintainer scripts definitely remove that file but perhaps something went wrong and the installation was only partial. Do you have any dpkg logs from the removal?
1773515,2018-05-29 23:00:55 UTC,Note that #include is NOT a comment. That's a valid way to perform the include function.
1773515,2018-05-26 16:40:40 UTC,Hello Dale.
1773515,2018-05-30 19:26:20 UTC,@Jamie
1773517,2018-05-30 16:14:06 UTC,I found the two bugs below may be related to my bug report. Removing the accountsservice check of lightdm will fix the issue.
1773517,2018-05-26 17:10:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773521,2018-05-26 16:23:30 UTC,"The attachment ""The upstream patch that fixes the issue"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1773522,2019-03-16 01:10:46 UTC,+1 bump
1773522,2019-05-22 21:00:58 UTC,Need vrf please ;) networkd-dispatcher scripts are a pain.
1773522,2019-08-16 09:46:10 UTC,+1 bump
1773522,2019-11-06 08:30:45 UTC,+1 bump
1773522,2020-06-03 10:57:54 UTC,"+1, if netplan is virtually mandatory, at least ensure it's got all the reasonable functionality you can expect from a linux-kernel"
1773522,2020-07-27 15:27:35 UTC,"+1, vrf support exists in other Ubuntu 20.04 routing tools (BIRD2, iproute2) but not this foundational one."
1773522,2020-10-21 11:15:18 UTC,"+1, would like VRF support in netplan as well."
1773526,2018-07-21 16:06:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773527,2018-06-04 19:11:34 UTC,"Make sure that Ubuntu packagers include the patch in https://gitlab.gnome.org/GNOME/evolution-data-server/commit/5c6b22b8eb72ccac07c7e5867aa6074347f7fd78 for https://bugzilla.gnome.org/show_bug.cgi?id=795997 (the patch was merged after the release of evolution-data-server 3.28 in GNOME).
And/or, if you did not set up your Google account via ""Online Accounts"" in the control center / settings but instead in Evolution directly, see https://bugzilla.gnome.org/show_bug.cgi?id=749974#c4"
1773527,2018-06-04 19:12:13 UTC,Also see https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1765713 (similar issue)
1773529,2018-05-29 14:19:19 UTC,Thanks for collecting these upstream fixes. We should definitely update xenial's exim package.
1773529,2019-06-08 02:48:10 UTC,"$ git log exim-4_86_2..exim-4.92 | grep -i dkim -B6 | grep ^Commit: | wc -l
122"
1773529,2020-06-15 00:02:41 UTC,Thank you for taking the time to file a bug report.
1773529,2020-06-15 07:16:16 UTC,"""Bugs which may, under realistic circumstances, directly cause a loss of user data"""
1773529,2020-06-17 16:06:24 UTC,"Thanks for your interest in the bug, Simon."
1773532,2019-02-09 21:36:07 UTC,or just download the updated package from https://packages.ubuntu.com/cosmic/sweethome3d and install manually. worked fine for me.
1773532,2018-09-18 16:24:00 UTC,"antgel, if you visit https://launchpad.net/bugs/1773532 you'll see that the bug is marked Fix Released for cosmic (the code name for Ubuntu 18.10 which will be released later next month) but only Triaged for bionic."
1773532,2018-09-18 16:15:00 UTC,"Why is it ""Fix released""? I have bionic and bionic-updates enabled, but I don't see the package."
1773532,2018-09-01 23:27:16 UTC,This bug was fixed in the package sweethome3d - 5.7+dfsg-3
1773532,2018-07-09 16:59:56 UTC,Same problem with snap version
1773532,2018-07-10 05:44:05 UTC,Using snap version library import works fine from SH3F file contained in the ZIP files but if importing from ZIP file I have the message '.. imported' but nothing is really imported.
1773532,2018-06-22 16:49:37 UTC,update from sourceforge:
1773532,2018-06-08 16:41:56 UTC,also 3D view - create picture creates an unusable picture.
1773532,2018-06-01 16:54:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773532,2018-05-27 06:21:27 UTC,"Opening a problem on a forum will not push canonical to solve the problem, the only hope is in launchpad, so please subscribe my bug: click on the yellow pencil near 'Does this bug affect you?'"
1773532,2018-05-26 20:16:51 UTC,I already opened a task in the German forum...
1773532,2018-07-04 08:09:56 UTC,the patch is for
1773536,2018-05-26 14:16:21 UTC,+ deuxième cas de figure en PJ
1773542,2018-09-14 02:58:10 UTC,"Reviewed:  https://review.openstack.org/579093
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=58538ace357d97bd9a06ce042aadc2928b1ff5bc
Submitter: Zuul
Branch:    stable/queens"
1773542,2018-10-08 21:49:17 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1773542,2018-10-02 08:58:22 UTC,"Reviewed:  https://review.openstack.org/570653
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b4659017936d415c4395a57c52fad6cf3ffa5302
Submitter: Zuul
Branch:    stable/ocata"
1773542,2018-09-24 14:47:16 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1773542,2018-09-24 14:46:31 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1773542,2018-09-15 00:25:44 UTC,"Reviewed:  https://review.openstack.org/602459
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ab03100bcbd5afe5702b760057fc19e25300cd89
Submitter: Zuul
Branch:    stable/pike"
1773542,2018-09-13 21:16:18 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/602459
Reason: Missed the stable/ocata change was already closed."
1773542,2018-05-28 05:26:39 UTC,assign to hongda as already a fix there
1773542,2018-08-09 15:40:17 UTC,"This is invalid for Rocky, so marking the Rocky series version of the bug as Invalid."
1773542,2018-06-29 08:56:42 UTC,"Change abandoned by huanhongda (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/570653
Reason: Fix the bug in stable/queens first then backport to stable/ocata."
1773542,2018-06-29 08:27:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/579093"
1773542,2018-05-30 01:49:16 UTC,"Change abandoned by huanhongda (<email address hidden>) on branch: master
Review: https://review.openstack.org/570736
Reason: Submit this patch to stable/ocata directly."
1773542,2018-05-28 07:59:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/570736"
1773542,2018-05-28 07:46:23 UTC,"Change abandoned by huanhongda (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/570653
Reason: Submit to master first then cherry pick."
1773542,2018-05-26 14:45:37 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/570653"
1773542,2018-09-13 21:15:35 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/602459"
1773546,2018-05-28 08:51:52 UTC,"Est-ce que ça ne pourrait pas avoir un rapport le bug #1772415 de décalage de numérotation ?
https://bugs.launchpad.net/ubuntu-fr-doc/+bug/1772415"
1773546,2018-05-28 12:06:09 UTC,"c'est bizarre que tu arrives sur la section ressources, tu devrais arriver sur accessoires_outils qui est quand même pas mal au dessus..."
1773546,2018-06-03 11:01:51 UTC,infos complémentaires échangées sur framateam :
1773546,2018-11-02 16:52:59 UTC,Le problème est toujours vrai malgré la résolution du bug de numérotation
1773549,2018-05-28 01:57:04 UTC,"I agree it could be better. If you would like to suggest ways to improve that module, please report them to the developers here:"
1773549,2018-05-27 09:46:54 UTC,"Oh, thanks for the hint. I didn't know that this module was loaded. But then the behavior of the module-switch-on-connect module is somehow inconsistent. The USB headset is always attached to the computer (wireless USB receiver) so there should be no reason that pulse should select that one over the onboard sink (considering that I had selected the onboard sink as default before). Also network sinks should not really be preferred via that module (that just doesn't seem right to me)."
1773549,2018-05-27 07:10:24 UTC,Actually this bug could still be kept open. We have a design proposal for fixing it already:
1773549,2018-05-27 07:04:33 UTC,Ubuntu is intentionally designed to automatically prefer the USB (or Bluetooth) audio over the internal audio.
1773551,2018-05-26 16:46:40 UTC,"neutron package version list :
dpkg -l |grep neutron
ii  neutron-common                       2:12.0.1-0ubuntu1.1~cloud0                  all          Neutron is a virtual network service for Openstack - common
ii  neutron-dhcp-agent                   2:12.0.1-0ubuntu1.1~cloud0                  all          Neutron is a virtual network service for Openstack - DHCP agent
ii  neutron-l3-agent                     2:12.0.1-0ubuntu1.1~cloud0                  all          Neutron is a virtual network service for Openstack - l3 agent
ii  neutron-linuxbridge-agent            2:12.0.1-0ubuntu1.1~cloud0                  all          Neutron is a virtual network service for Openstack - linuxbridge agent
ii  neutron-metadata-agent               2:12.0.1-0ubuntu1.1~cloud0                  all          Neutron is a virtual network service for Openstack - metadata agent
ii  neutron-plugin-ml2                   2:12.0.1-0ubuntu1.1~cloud0                  all          Neutron is a virtual network service for Openstack - ML2 plugin
ii  neutron-server                       2:12.0.1-0ubuntu1.1~cloud0                  all          Neutron is a virtual network service for Openstack - server
ii  python-neutron                       2:12.0.1-0ubuntu1.1~cloud0                  all          Neutron is a virtual network service for Openstack - Python library
ii  python-neutron-fwaas                 1:12.0.0-0ubuntu1~cloud0                    all          Firewall-as-a-Service driver for OpenStack Neutron
ii  python-neutron-lib                   1.13.0-0ubuntu1~cloud0                      all          Neutron shared routines and utilities - Python 2.7
ii  python-neutronclient                 1:6.7.0-0ubuntu1~cloud0                     all          client API library for Neutron - Python 2.7"
1773551,2018-05-30 16:17:44 UTC,"I don't think anything has changed upstream, is this something specific to your distro?"
1773551,2019-01-15 01:57:19 UTC,"With a long time to watch this issue,it will be ok after delete all network configure eg. route  in openstack neturon .
After you delete this configure ,just restart the service ,and all will be right now ."
1773551,2020-10-27 12:07:16 UTC,But when I encounter the same issue in my production network which is running with 100s of VM how could I delete the entire network and make the dhcp agent run.My entire setup is getting collapsed if I try to restart the dhcp agent????.It is not permitting to launch new VM unless I delete the entire network and VMs and start from first.Please guide to overcome this issue
1773553,2018-10-14 23:30:38 UTC,This bug was fixed in the package sweethome3d-furniture-editor - 1.23-1
1773561,2018-05-26 17:31:40 UTC,I don't know why 'fglrx-installer' was chosen as an affected package. During creating a report I've chosen 'gimp' package.
1773570,2018-05-26 23:55:04 UTC,*** This is an automated message ***
1773587,2020-04-21 20:15:57 UTC,https://github.com/mixxxdj/mixxx/pull/2690
1773587,2019-04-23 21:36:12 UTC,This still happens with the 2.2.1 release.
1773587,2018-10-21 22:21:50 UTC,It happens on Ubuntu Bionic and Xenial 64 bit using the Cinnamon Desktop.
1773587,2018-10-21 20:58:46 UTC,"Just reporting that here, with Windows 10, mixxx 2.2 built from sources this weekend it is working as expected either fullscreen or windowed.
When windowed, Mixxx is resized to shade's smaller size. When it is fullscreen, the skin resizing takes place and occupies all the screen space."
1773587,2018-10-21 20:57:02 UTC,Maybe this only happened with old Qt versions? I am using 5.11.1 now. I didn't notice this with 5.10 either.
1773587,2018-10-21 20:44:41 UTC,FWIW I have not been able to reproduce this. I am using GNOME with Wayland on Fedora 28.
1773587,2018-10-20 13:32:46 UTC,"I watch this, too, but only if a) the window is maximized or if Mixxx is in full-screen mode.
In default (minimal) window mode the UI is fine and correctly sized after changing & reloading skins."
1773594,2020-02-09 22:45:12 UTC,"I'm not sure when this was fixed but in 19.10 there's no such problem. The bootloader selection does not default to the chosen device, but I'm not entirely taken by that."
1773597,2018-07-27 18:17:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773597,2018-07-12 21:40:51 UTC,I booted another machine (currently running 18.04) from the USB memory stick with 16.04 on it. I plugged in three USB memory sticks. Each came up in a couple of seconds. When that machine is running 18.04 it takes 4+ minutes for a single memory stick to be available.
1773597,2018-07-12 02:02:37 UTC,I booted the Dell Studio XPS machine from a USB drive loaded with Ubuntu 16.04. I inserted multiple USB drives (one holding the OS was already there) and two others. They mounted within seconds and Nautilus displayed their contents when the drive was clicked on.
1773597,2018-07-09 22:29:55 UTC,"My apologies. Sorry, but the encrypted USB drive was defective. I put it in another computer (Ubuntu 17.10) and it would be recognized only if it were held in the drive in a particular way. Either an internal connection is bad or the external contacts are not aligned properly."
1773597,2018-07-04 17:39:53 UTC,"Inserted a regular USB memory stick after the most recent update and a reboot. I always try this after an update in case something got fixed. The memory stick appeared on the desktop 4 minutes and 20 seconds after I inserted it. Too long, wouldn't you say?"
1773597,2018-06-12 22:19:25 UTC,dmesg output after plugging in encrypted flash drive:
1773597,2018-06-12 22:18:08 UTC,"The latest Ubuntu update included Linux version 4.15.0-23-generic. This appears, after a single test after a reboot, to have allowed a FAT-formatted USB memory stick to be recognized and mounted. I opened the device and copied a file to it then unmounted it with no problem."
1773597,2018-06-18 01:23:00 UTC,"Could not mount a video DVD unless the DVD had been inserted and then the machine rebooted. At this point, the DVD is mounted and can be played. After ejecting the DVD and inserting another DVD, the newer DVD is not recognized unless the machine is rebooted."
1773597,2018-06-07 21:13:31 UTC,"The feature for mounting both unencrypted and encrypted USB drives worked well(!) in Ubuntu 17.10. And it continues to work with the test USB drives I'm using. If I insert an encrypted USB drive in my tower machine (Ubuntu 17.10) I get a dialog box asking for my pass phrase right away. If I enter the correct phrase, I get immediate access to the contents of the USB drive."
1773597,2018-06-08 01:17:30 UTC,"This problem may be associated with the USB software. I shut  down the machine and pulled the battery and the Logitech mouse USB receiver. Booted the machine. With just the sign-in box on the screen, both the mouse and the trackpad worked. Immediately after sign-in the mouse could not be controlled by the trackpad. The keyboard continued to work. I rebooted the machine after removing the Logitech USB receiver. The trackpad would not work. I inserted the Logitech USB receiver, but it did not allow the mouse to work. Rebooting reactivated the Logitech mouse."
1773597,2018-05-27 00:24:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1773597,2018-05-27 23:44:06 UTC,Tried ...
1773597,2018-05-28 02:19:51 UTC,"After a reboot, inserted encrypted USB flash drive (32G Lexar). Waited about 15 minutes and the request for the password was displayed. I entered the password, but nothing happened. Waited five minutes - then rebooted with the drive still inserted. It was not recognized (by Nautilus) upon completion of the reboot. Removed and inserted and it was eventually recognized, but no window asking for a password showed until I opened the ""file cabinet"" and clicked on the drive listed on the left. A request for password then appeared. I entered the password and was able to open the drive. However after about ten minutes, I could not open any files - a lock icon appeared on the file icon. Removed the USB flash drive and rebooted."
1773597,2018-05-26 22:44:23 UTC,"I've tried mounting several different flash drives: One Lexar, one encrypted Lexar, one Sandisk."
1773597,2018-06-06 03:31:28 UTC,"Inserted an unencrypted USB drive.
dmesg showed it as /dev/sdc1
tried:
    sudo mount /dev/sdc1 temp"
1773597,2018-05-26 22:41:04 UTC,"This bug occurred on a Dell Studio XPS. It also occurred on an Alienware machine - both fairly old, perhaps 8 years. The Alienware machine was at the same software level as the Dell Studio XPS. On the Alienware machine, occasionally after some time (say five minutes). With an encrypted drive, the drive might appear (or not), but access was iffy - with the system asking multiple times for the password, but almost never granting access. When access was granted, access to the files was eventually terminated - the directory window in Nautilus eventually showing no files."
1773597,2018-06-07 21:11:07 UTC,"I inserted a standard USB drive into my laptop (Ubuntu 18.04). After about five minutes it was recognized and mounted. I inserted my encrypted USB drive, but it was never mounted - presumably because the file system type was not recognized - because something is wrong with the decryption feature."
1773597,2018-05-29 20:55:45 UTC,Booted a tower machine (it had been powered off) running Ubuntu 17.10 (Artful). Ran SW updates. Rebooted. Inserted encrypted USB flash drive. Was asked several times for the password. Gave it - multiple times. Finally I was able to open drive. That lasted about 10 minutes when all the files in the window disappeared (folder is empty message). Pulled the flash drive and reinserted it. This time it worked. Request for password showed up in its black window. I entered the password (twice - I might have screwed it up). Was able to access files with no problems.
1773598,2021-01-08 13:04:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773599,2018-08-09 15:20:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773601,2018-05-27 00:32:51 UTC,"This is not really something Inkscape can ""fix"":
- Most likely it's an issue in fontconfig and needs to be fixed
  (and reported) upstream.
- The only other option is to reactivate the native pango_win32 back-end.
  In principle this works (I did some initial experiments locally and have it
  mostly working), but it does not support any of the OpenType font features
  we advertised lately."
1773601,2018-05-27 00:56:52 UTC,"Thanks for the info, Eduard!"
1773601,2018-05-27 10:42:47 UTC,"I'm actually not sure myself - fc-cache is the program that builds the list of fonts available on a system (and that's basically what Inkscape offers to the user in the end), so that's at least not completely wrong."
1773601,2018-05-27 22:12:12 UTC,"Thank you, @Eduard Braun, I'll try fc-cache then. They might already know about the problem, or could otherwise be able to give more info. We have some long-term users on the forums who have the issue, and would probably be willing to give more info if required."
1773601,2018-05-27 22:49:28 UTC,"Mmh. I've just reconsidered this, as I found a bug that you're subscribed to, that says that Gimp takes a long time to start due to building the cache. And Gimp does not have those problems that I described above, according to the affected users, although it seems to use the same routines to build their fonts list."
1773603,2018-06-02 15:34:41 UTC,same applies to Controller Mapping Wizard window when Mixx is in fullscreen mode.
1773603,2018-06-02 15:35:43 UTC,"Alt+Tab to another window would hide Mixxx main window, show that other window with Wizard window on top"
1773606,2019-06-16 16:42:33 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape-docs/documentation/issues/1
1773608,2018-07-12 23:03:43 UTC,"As of the 2018-07-12 .iso,"
1773608,2018-11-01 23:46:42 UTC,"Having now installed the released version of Cosmic, the same problem exists."
1773608,2018-11-02 05:35:58 UTC,"I can't reproduce this. I have selected and changed the value of the mount point to so many different things and no matter if I hit enter or OK, or hit tab first or not, it still results in the appropriate mount point being shown in the mount point column."
1773608,2019-01-02 04:17:24 UTC,[Expired for calamares (Ubuntu) because there has been no activity for 60 days.]
1773608,2019-04-07 20:02:53 UTC,"As of the Beta release (03/26) of Lubuntu 19.04, the same thing occurs."
1773608,2019-04-14 07:27:33 UTC,"As I said above, I could not reproduce it. If you're still experiencing it, perhaps I am not taking the right steps to reproduce what you're trying to do. Please create a set of steps that I can take to reproduce this, given an entirely brand new partition table."
1773608,2019-06-14 04:17:21 UTC,[Expired for calamares (Ubuntu) because there has been no activity for 60 days.]
1773610,2021-01-28 05:36:44 UTC,I'll add FORMAT I consider easy to see in the summary screen
1773610,2021-01-28 20:09:34 UTC,"I just checked this and I can confirm that it is still affecting Focal, which is consistent with the fact that the upstream bug has not been updated. Look at the picture in the upstream issue and it should be clearer. Also the other two conditions of expected results aren't met."
1773610,2021-01-28 06:16:26 UTC,I've explored this issue again with another FOCAL install and I'll disagree with myself (comment #7).
1773610,2021-01-28 05:20:13 UTC,"Having just completed a 20.04.2 QA-test install..
I've changed my mind; this bug still applies in focal"
1773610,2019-04-08 04:57:47 UTC,"I noted somewhat similar behavior in https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1822249 where I say
""I noticed what appeared (twice at that stage) where I'd selected ""format"" a partition, when I re-entered the partition [settings] it seemed to show ""keep"". I was re-opening to explore that before seeing if I was mistaken, or it is an issue when the calamares installer disappeared off screen (crash).""
----"
1773610,2019-04-08 06:27:54 UTC,I also noted in https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1822249
1773610,2019-04-08 04:57:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773610,2018-07-12 23:05:31 UTC,"As of the 2018-07-12 .iso,"
1773610,2019-04-07 20:05:13 UTC,"As of the Beta release (03/26) of Lubuntu 19.04, the same thing occurs."
1773610,2021-01-28 05:15:20 UTC,Thank you for reporting this bug to Ubuntu.
1773619,2018-06-07 20:36:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773620,2018-05-28 06:36:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773621,2018-08-09 09:59:08 UTC,"Same hier tuxguitar
Exception in thread ""main"" java.lang.UnsatisfiedLinkError: Cannot load 64-bit SWT libraries on 32-bit JVM
 at org.eclipse.swt.internal.Library.loadLibrary(Library.java:256)
 at org.eclipse.swt.internal.Library.loadLibrary(Library.java:236)
 at org.eclipse.swt.internal.C.<clinit>(C.java:16)
 at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
 at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
 at org.eclipse.swt.widgets.Display.<clinit>(Display.java:139)
 at org.herac.tuxguitar.gui.TuxGuitar.displayGUI(Unknown Source)
 at org.herac.tuxguitar.gui.TGMain.main(Unknown Source)"
1773621,2018-08-09 10:04:30 UTC,"sorry, forgot my installation is complete 32-bit.  dpkg --print-architecture
i386
without multiarch. I removed it."
1773633,2018-05-27 09:42:35 UTC,Ok after 32 seconds of device scanning it finally booted into the operating system:
1773638,2019-05-31 20:31:54 UTC,"@Sylvain - that's what I said in comment #6. Having a fixed coordinate origin/printable page combination is just weird. I have proposed elsewhere that the ""worksheet"" (= printable page) could be completely configurable, i.e. could be drawn as a box with non-fixed size. It would make zooming/panning for printing very easy (which is now very difficult). And as I said in comment #6, moving the coordinate origin is logically the same as moving everything else (including the worksheet)."
1773638,2019-05-31 15:02:34 UTC,Am I missing something or would just letting the user set the origin anywhere in the page layout editor be enough (instead of just the 4 corners atm) ?  (I know it would for me). Or just move the worksheet in the layout / schematic editor.
1773638,2018-05-28 21:04:21 UTC,"twlostow said:
""Can't we simply add a feature that recalculates all coordinates when a new coordinate system origin [...] is changed?"""
1773638,2018-05-28 20:56:21 UTC,"This od similar:
https://bugs.launchpad.net/bugs/1770897"
1773638,2018-05-28 20:52:53 UTC,Similar topic:
1773638,2018-05-28 20:31:05 UTC,"Nice discussion folks. I also would find it useful to have global origins for file storage and export to become standard compliant and dont mess anything, but some kind of local origins for ""dusplay"" too that would help me a lot with complex mechanical structures or precision components placement inside a local board from its corner or middle point.."
1773638,2019-06-07 13:25:27 UTC,So generalny speaking what's the easiest? What's could to give us chances to see (and set) components location based on a previously (manually) placed (local?) PCB origin?
1773638,2018-05-28 19:53:54 UTC,"OK, based on feedback so far I've got a new proposal:"
1773638,2018-05-28 19:32:57 UTC,"I don't understand the point of the whole discussion. Can't we simply add a feature that recalculates all coordinates when a new coordinate system origin (can be made equal to grid origin) is changed? This way, there's no need to modify any input/output code and the coordinates in the PCB files are always in sync with what the GUI shows."
1773638,2018-05-28 19:21:21 UTC,"It looks like that the original purpose of the Grid Origin is to set a grid offset, not to set an ""origin"" per se. It's the one point which always hits the grid, or the grid always hits it. Therefore, if the Grid Origin is set as the coordinate origin, is it possible that someone soon asks how it would be possible to set the grid offset independently from the grid origin?"
1773638,2018-05-28 16:40:36 UTC,I've updated my patch stream to the latest upstream master (2cb65f9) for anyone who wants to experiment without having to go back 42 patches. It has literally 5 minutes of testing on it but it looks correct at first blush.
1773638,2018-05-28 14:58:50 UTC,"As can be seen in my patch series, I started with Grid Origin relative coordinates but found this to be problematic."
1773638,2018-05-28 14:12:35 UTC,"I've been using a patch series I developed to change the display origin (and only the DISPLAYED origin) to be the Aux Origin. I've attached a zip file containing the patch series for discussion purposes. They are in no way ready for wide distribution so I haven't ticked the ""This attachment contains a solution"" box."
1773638,2018-05-27 15:28:33 UTC,For whoever is interested about those discussions...
1773638,2018-05-27 13:56:21 UTC,"I'm in favor of a single origin in the UI that controls all position values/offsets.  And no ability to separately set the drill origin.  In NC drill generation, we can have a checkbox that allows the drill hits to be referenced to either the absolute (file) origin or the relative (UI) origin."
1773638,2018-05-28 20:06:55 UTC,"I agree for the most part.  There are distinct coordinate origins that
make sense to me.  One origin is used when placing objects and routing.
The other origin is used for plotting.  I don't see how a single origin
makes sense let alone the difference between absolute and relative
coordinates so I think this needs be well defined before we attempt to
implement anything."
1773643,2018-06-01 22:22:21 UTC,apport information
1773643,2018-06-01 22:22:20 UTC,apport information
1773643,2018-06-01 22:20:53 UTC,apport information
1773643,2018-05-27 16:56:13 UTC,apport information
1773643,2018-06-01 00:54:08 UTC,Battant:
1773643,2018-05-31 18:53:26 UTC,"Hello,"
1773643,2018-06-01 22:37:13 UTC,apport information
1773643,2018-05-27 16:56:11 UTC,apport information
1773643,2018-06-01 22:20:52 UTC,apport information
1773643,2018-06-01 22:37:14 UTC,apport information
1773643,2018-06-04 19:33:41 UTC,"Hello,"
1773643,2018-06-02 00:39:49 UTC,"Hello,"
1773643,2018-06-02 00:58:20 UTC,"Battant, please advise to all of the following:"
1773643,2018-06-04 19:43:00 UTC,"Hello,
My laptop use the fn + f12 key to switch on/off the Bluetooth."
1773643,2018-06-05 03:27:15 UTC,So it's a regression between 12.04 (Linux v3.2) and 14.04 (Linux v3.13).
1773643,2018-06-05 20:59:57 UTC,"Hello,"
1773643,2018-06-07 03:15:00 UTC,"Sure,
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.9-wily/"
1773643,2018-06-21 01:27:55 UTC,"Battant et all,"
1773643,2018-06-21 01:30:21 UTC,"Also I identified this issue by using this command:
dmesg |grep -i blue
I got output which stated ""hci0: don't support firmware rome"""
1773643,2018-05-27 16:56:10 UTC,apport information
1773643,2018-06-01 22:49:16 UTC,"Hello,"
1773643,2018-05-27 16:56:09 UTC,apport information
1773643,2018-06-04 03:08:16 UTC,Do Clevo laptops use WMI hotkeys?
1773643,2018-05-27 16:56:06 UTC,apport information
1773643,2018-05-27 16:54:54 UTC,apport information
1773643,2018-05-27 16:54:55 UTC,apport information
1773643,2018-05-27 16:54:56 UTC,apport information
1773643,2018-05-27 16:54:57 UTC,apport information
1773643,2018-05-27 16:54:59 UTC,apport information
1773643,2018-05-27 16:55:00 UTC,apport information
1773643,2018-05-27 16:55:01 UTC,apport information
1773643,2018-05-27 12:01:45 UTC,"Battant, thank you for reporting this and helping make Ubuntu better."
1773643,2018-05-27 16:56:07 UTC,apport information
1773643,2018-05-27 16:55:03 UTC,apport information
1773643,2018-05-27 16:55:05 UTC,apport information
1773643,2018-05-27 16:55:02 UTC,apport information
1773643,2018-05-27 16:55:08 UTC,apport information
1773643,2018-05-27 16:55:09 UTC,apport information
1773643,2018-05-27 16:55:56 UTC,apport information
1773643,2018-05-27 16:55:58 UTC,apport information
1773643,2018-05-27 16:55:59 UTC,apport information
1773643,2018-05-27 16:56:00 UTC,apport information
1773643,2018-05-27 16:56:01 UTC,apport information
1773643,2018-05-27 16:56:03 UTC,apport information
1773643,2018-05-27 16:56:04 UTC,apport information
1773643,2018-05-27 16:56:05 UTC,apport information
1773643,2018-05-27 16:55:06 UTC,apport information
1773643,2018-05-27 16:54:53 UTC,apport information
1773653,2019-10-05 14:44:39 UTC,Working on it:
1773653,2019-10-07 09:31:39 UTC,This bug was fixed in the package mate-themes - 3.22.20.1-0ubuntu1
1773653,2019-10-07 09:58:08 UTC,This bug was fixed in the package marco - 1.22.3-0ubuntu2
1773653,2019-10-07 09:58:12 UTC,This bug was fixed in the package ubuntu-mate-artwork - 19.10.10
1773654,2019-03-19 18:28:28 UTC,I believe I have the same issue https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1820884
1773654,2019-03-21 14:32:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773661,2018-05-31 15:10:25 UTC,Need Help
1773664,2018-05-27 17:30:58 UTC,This is for UM 18.04. I should have mentioned that.
1773670,2018-05-27 17:32:24 UTC,"This applies to UM 18.04, but also to 17.04 and 17.1. The problem seems to be getting worse, not better."
1773671,2018-08-23 16:55:02 UTC,"After looking into this with UX/design we feel the strength of the font-weight being stronger than the other font used. Therefore, we will look into it with the new table listing design."
1773671,2018-08-24 09:40:01 UTC,"Thanks Ant. Since it's static data (not editable) it might be
appropriate to gray it out slightly. That would balance the weight."
1773683,2018-05-28 22:40:26 UTC,http://www.jthink.net/jaikozforum/posts/list/19698.page
1773683,2018-05-29 06:09:40 UTC,"Since we cannot know if it is a track from ITunes or an other player, we can either ignore the issue, shiw both fields or add an iTunes compatibility mode, right?"
1773683,2020-01-01 11:13:21 UTC,Already fixed on master.
1773693,2018-05-27 19:40:43 UTC,Also with plasma-discover
1773693,2018-09-13 14:23:00 UTC,The package itself needs to place /var/run/reboot-required.
1773695,2020-08-08 19:34:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773695,2019-01-24 12:24:31 UTC,how to fix it
1773695,2018-06-04 04:07:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773695,2019-01-24 15:22:00 UTC,"Hi,
I have no clue if my resolution is the right way.  It seems that my old machine, hp mini was too slow.  If I wait long enough, the installation will complete.  Not sure if it is applicable in your case.
Best of luck,
-James"
1773697,2018-10-14 16:02:36 UTC,apport information
1773697,2018-11-29 01:18:47 UTC,Same problem on 4.15.0-39-generic #42-Ubuntu x86_64 @ Thinkpad W540. Can not upgrade to 4.19 because of NVIDIA driver does not support this kernel. Could you please bugfix recent kernel!?
1773697,2018-11-01 12:44:30 UTC,"diff --git a/sound/usb/quirks-table.h b/sound/usb/quirks-table.h
index 08aa78007020..849953e5775c 100644
--- a/sound/usb/quirks-table.h
+++ b/sound/usb/quirks-table.h
@@ -3346,19 +3346,14 @@ AU0828_DEVICE(0x2040, 0x7270, ""Hauppauge"", ""HVR-950Q""),
                                .ifnum = 0,
                                .type = QUIRK_AUDIO_STANDARD_MIXER,
                        },
-                       /* Capture */
-                       {
-                               .ifnum = 1,
-                               .type = QUIRK_IGNORE_INTERFACE,
-                       },
                        /* Playback */
                        {
-                               .ifnum = 2,
+                               .ifnum = 1,
                                .type = QUIRK_AUDIO_FIXED_ENDPOINT,
                                .data = &(const struct audioformat) {
                                        .formats = SNDRV_PCM_FMTBIT_S16_LE,
                                        .channels = 2,
-                                       .iface = 2,
+                                       .iface = 1,
                                        .altsetting = 1,
                                        .altset_idx = 1,
                                        .attributes = UAC_EP_CS_ATTR_FILL_MAX |"
1773697,2018-11-01 12:40:37 UTC,Seems to be fixed with the daily kernel image linux-image-unsigned-4.19.0-999-lowlatency
1773697,2018-10-29 19:57:57 UTC,Posted on alsa-devel mailing list ...
1773697,2018-10-23 05:08:24 UTC,Please raise the issue to <email address hidden> for ALSA maintainers' awareness.
1773697,2018-10-14 16:02:43 UTC,apport information
1773697,2018-10-14 16:02:41 UTC,apport information
1773697,2018-10-14 16:02:39 UTC,apport information
1773697,2018-10-14 16:02:37 UTC,apport information
1773697,2018-10-14 16:02:35 UTC,apport information
1773697,2019-03-08 04:36:05 UTC,"href, I think the fix is still needed for Bionic (v4.15) and Cosmic (v4.18) kernel?"
1773697,2018-10-14 16:02:32 UTC,apport information
1773697,2018-05-27 20:44:28 UTC,Syslog output from non working kernel with failed probe message:
1773697,2018-10-14 16:02:34 UTC,apport information
1773697,2018-05-29 05:43:52 UTC,See https://patchwork.kernel.org/patch/10265345/. Dropping that patch and recompiling the kernel leads to a situation where alsa and pulseaudio seem to to be working again.
1773697,2018-06-28 15:44:42 UTC,Exact same problem here. I assume the quirk added was for the previous version of headphone firmware.
1773697,2018-10-14 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773697,2018-10-14 15:59:57 UTC,Journalctl output after attaching USB device on Thinkpad X220 upgraded to cosmic ...
1773697,2018-05-28 17:42:46 UTC,Currently this quirk seems to make things worse - at least for me with the current firmware release on the headphones.
1773697,2018-10-14 16:02:15 UTC,apport information
1773697,2018-10-14 16:02:26 UTC,apport information
1773697,2018-10-14 16:02:29 UTC,apport information
1773697,2018-10-14 16:02:30 UTC,apport information
1773697,2018-10-14 16:02:31 UTC,apport information
1773697,2018-10-14 16:02:13 UTC,apport information
1773700,2018-06-30 16:39:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773700,2019-01-07 12:07:08 UTC,For me the steps from this tutorial https://era86.github.io/2017/10/03/asus-zenbook-3-volume-controls.html have done the trick in order to control the internal speaker volume. But unfortunately it is more a workaround than a real fix since I still have crackling sound... :'(
1773700,2019-01-07 12:38:58 UTC,And I do not know if it changes something but I have this workaround active too: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html
1773704,2018-07-28 23:05:24 UTC," I wasn't able to test the kernel you provided, dpkg -i complained of conflicting packages. I suspect because the kernel was down-rev relative to the running kernel. But I don't reslly know, I'm relatively new to compilling and installing kernels.
However, I was able to compile and install my own kernel on the target machine. Once again, all I did was change line 184 to be identical to like 187 and it worked like a charm: no more errors.
So my suggestion was that if you made the exact same change, your test jernel _should_ work. But I can understand if that's just not the way it's done around here, and I'll be happy to test your kernel if I can get around the error message. Is there an option I can give to dpkg to force the installation?
-Jeff
    On Friday, July 27, 2018, 8:41:19 AM PDT, Joseph Salisbury <email address hidden> wrote:"
1773704,2018-08-15 01:52:22 UTC,"My bug report 1737629, of which this has been marked a duplicate, also involves a uPD720202 chipset card."
1773704,2018-08-14 22:36:52 UTC,Ooops. I can see that point. The Startech card I'm using claims to be based on the uPD720202: perhaps it has two if them. I'd say that the uPD720202 needs the XHCI_TRUST_TX_LENGTH quirk as well.
1773704,2018-08-14 19:35:41 UTC,There was the following response from the original patch author:
1773704,2018-08-10 17:33:06 UTC,"Thank you Joseph, sorry I couldn't try your test kernel but I've just been chasing my tail trying to figure out why I can install some kernels and not others."
1773704,2018-08-10 15:45:51 UTC,"I'll submit this patch upstream as well as SRU it to Ubuntu.  Can you send me your email address, and I'll add you to the upstream patch?  You can either post your email address here or send it to me at <email address hidden>."
1773704,2018-07-27 15:34:05 UTC,"Sorry for the delay.  Just to confirm, the test kernel posted in comment #3 did in fact resolve this bug?  If so, I'll submit an SRU request."
1773704,2018-06-12 22:46:42 UTC," No, premature. Bug still exists. I'll try your kernel at the next sitting.
-Jeff"
1773704,2018-07-27 01:29:35 UTC,The typo is still present in 4.15.0-29.31
1773704,2018-05-27 21:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773704,2018-07-27 01:41:09 UTC,"The underlying bug is also described in bug ID #1737629, but I think that report was prior to the typo ie: before the ""fix"" with the typo was added."
1773704,2018-05-29 20:00:09 UTC,"I built a patched test kernel.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1773704"
1773704,2018-06-11 21:37:59 UTC," Dear Mr. Salisbury,
I can't believe it's been 12 days since I filed this report. Seems like it was just yesterday. And in fact it's just today I found your missives. Shame on me!
I'm having a bad case of battle fatigue with this issue. I'm deploying like TODAY.  Do I live with errors? Do I compile my own kernel ( have done for 6 mos now)? Do I try your kernel? Do I live with errors until the typo  is fixed?
I hope you can trust me on this one, This is a single-character typo. Fix the typo, everything works fine.
The only question at this point is how to run it up the flagpole as quickly as possible. I suspect it's upstream of Ubuntu.
    On Tuesday, May 29, 2018, 11:51:15 AM PDT, Joseph Salisbury <email address hidden> wrote:"
1773704,2018-05-28 20:35:08 UTC,"Don't see the point in adding log files for a simple and obvious typo, but before code  was added for this fix I believe I did generate before and after logs under bug ID #1710548. In any case I'm running kernels in which I've fixed the typo."
1773704,2018-06-12 22:16:14 UTC," Hey! This bug may be fixed.As best I recall I did a fresh install from nightly build about 3 days ago, but had not installed zoneminder so no op to tickle the bug.
Today I did an upgrade and a dist-upgrade, then loaded zoneminder, started pulling data over renesas port, so far no dmesg errors, I think it's fixed.
Did you fix it? Well blessings on whoever did.
I'll let you know if it pops up again. Thank you so much
    On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury <email address hidden> wrote:"
1773704,2018-07-27 01:25:57 UTC,"I downloaded the three files you mentioned and tried to install them using 'dpkg -i *.deb' as root. Two of the pkgs installed OK but the kernel proper did not, giving error:"
1773704,2018-06-11 21:47:17 UTC," Just though of something..... reinstalled a system from daily build yesterday.
So here's the deal: I'l try to see if it's fixed as of yesterday....
But it will take me some hours to re-con zoneminder to trigger the bug.
-jeff
    On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury <email address hidden> wrote:"
1773708,2018-11-20 18:18:40 UTC,This is also affecting our company. We are trying to move to 2-factor auth now.
1773708,2019-01-10 23:04:21 UTC,"This was a typo, which I fixed in https://gitlab.com/openconnect/openconnect/commit/e9647a08bb4613227fd371752910cb32e54f8870, which is included in the OpenConnect v8.01 release."
1773715,2018-05-30 20:48:29 UTC,apport information
1773715,2018-05-30 20:53:18 UTC,Hello Ubuntu Kernel Bot (ubuntu-kernel-bot).
1773715,2018-05-30 20:48:40 UTC,apport information
1773715,2018-05-30 20:48:36 UTC,apport information
1773715,2018-05-30 20:48:34 UTC,apport information
1773715,2018-05-30 20:48:32 UTC,apport information
1773715,2018-05-30 20:48:30 UTC,apport information
1773715,2018-05-30 20:48:27 UTC,apport information
1773715,2018-05-30 20:48:21 UTC,apport information
1773715,2018-05-30 20:48:24 UTC,apport information
1773715,2018-05-30 20:48:22 UTC,apport information
1773715,2018-05-30 20:48:19 UTC,apport information
1773715,2018-05-30 20:48:18 UTC,apport information
1773715,2018-05-30 20:48:15 UTC,apport information
1773715,2018-05-30 20:48:13 UTC,apport information
1773715,2018-05-29 16:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773715,2018-05-29 16:18:16 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1773715,2018-05-30 20:48:26 UTC,apport information
1773717,2020-08-01 17:52:54 UTC,"I'm going to close this ticket, as it should be solved in Ubuntu 20.04 and on and it was never really something that deja-dup itself could fix."
1773717,2020-01-07 20:05:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773717,2019-10-25 22:16:24 UTC,"The gvfs nfs backend was not enabled in 18.04, see bug #1637988"
1773717,2018-06-04 21:35:28 UTC,"I can perform that workaround, too, but the real culprit is gvfs and it
really should be fixed."
1773717,2019-10-25 00:42:45 UTC,manually mounting ( & unmounting ) the NFS share is not a great option for a laptop that moves around a lot...
1773717,2018-06-02 08:15:48 UTC,"I have the exact same problem. A workaround I use for now is to mount the NFS share in fstab and point deja-dup to the local mount, not ideal though."
1773717,2018-05-28 13:01:17 UTC,"Have done a bit of sleuthing. This problem is apparently due to a bug in gvfs. I also cannot mount and browse any nfs shares in Ubuntu in Nautilus (and have no issue doing do on Arch). I checked the libnfs and nfsidmap libraries and they appear to be similar, but nfsidmap is a bit behind Arch."
1773717,2019-10-25 20:49:02 UTC,Setting as confirmed as this bug affects multiple users.
1773718,2018-06-11 02:49:51 UTC,"I haven't tried with other DE, since it is an old computer I have only tried lxde. I could easily try with openbox alone, installing another DE could be a little longer. Is there one better to test with?"
1773718,2018-06-09 14:30:13 UTC,Do you see the same issue under different DE (Unity/Gnome/KDE)?
1773718,2018-05-29 16:17:22 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1773718,2018-05-31 14:42:10 UTC,"Hi,
  I've seen this problem since I install linux in this computer (2 years ago), but my workaround was to use the nvidia propietary driver. Now that nvidia stop developing the 304 driver, I will have to use nouveau.
I installed 4.17.0-041700rc7-generic and the problem still is there. It might be that I had to wait a couple of minutes more oafter the screen switch off or suspended, but the problem is still there."
1773718,2018-05-28 02:43:10 UTC,I didn't knew which log to attach. Already done what you asked for. I'm also attaching lspci -vnvn log
1773718,2018-05-28 02:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1773718,2018-05-31 22:10:03 UTC,"I just realize that it only happen after login (lxde, lubuntu) in lightdm this does not happen."
1773729,2018-06-01 17:00:22 UTC,"Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help posting your problem in the support forum of your local Ubuntu's community http://loco.ubuntu.com/ or asking at http://askubuntu.com. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs."
1773729,2018-06-04 03:29:40 UTC,"I can not understand why u treat it as invalid bug without any useful explanation.
Ubuntu offers two so files, but they behaved differently.
I used the so files in Debian, they works well, why???
I used the so files in ubuntu 16.04.14.04, they works well, why???
Please explain the reason before u resolve the problems without investigation."
1773732,2018-06-30 16:39:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773743,2020-11-21 21:06:28 UTC,"We were mis-parsing the 'vCont' packet in the gdb protocol, so when gdb told us ""send a SIGPROF (0x1b)"" we skipped the first digit in the hex signal number and interpreted it as ""send an 0xb"", which happens to be SIGSEGV."
1773745,2018-05-28 08:08:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/570739"
1773745,2018-06-12 02:46:36 UTC,"Change abandoned by Peng Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/570739
Reason: Our customer still needs this function, so I abandon this patch. Thanks for all your comments"
1773747,2019-03-21 13:22:20 UTC,"The cifs_idmap_sss.so is part of sssd-common
https://packages.ubuntu.com/bionic/amd64/sssd-common/filelist"
1773747,2020-09-25 11:43:39 UTC,"I installed a new system with 20.04 and sssd-common.
Unfortunately the alternative for idmap-plugin from sssd is still not available by update-alternatives:"
1773750,2019-05-08 10:20:32 UTC,"No Https
No SSL"
1773750,2019-07-22 10:10:49 UTC,This prevents LoCo from using the LoCo Portal.
1773756,2018-06-13 22:42:49 UTC,"bridge-utils is a very small package. I am more worried about cloud-utils which, as you mentioned, pulls in qemu-block-extra:"
1773756,2018-06-07 21:53:03 UTC,Doesn't that say that cloud-utils is requesting qemu-block-extra?
1773756,2018-06-07 18:40:17 UTC,cpu-checker looks thin in terms of dependencies so installing that and deferring the rest seems good:
1773756,2018-06-07 19:26:11 UTC,"This is our list of packages:
func (cfg *ubuntuCloudConfig) addRequiredPackages() {
    packages := []string{
        ""curl"",
        ""cpu-checker"",
        // TODO(axw) 2014-07-02 #1277359
        // Don't install bridge-utils in cloud-init;
        // leave it to the networker worker.
        ""bridge-utils"",
        ""cloud-utils"",
        ""tmux"",
        // TODO(wpk) 2017-07-23 maybe we should do it in fanconfigurer?
        ""ubuntu-fan"",
    }"
1773756,2018-06-05 17:20:43 UTC,"The one we actually want is 'cpu-checker' as we want to know whether we
*could* launch a KVM guest on a given machine, and we could defer
installing the rest of the packages to actually launch them until we
actually have requested it.
We could potentially have a flag for disabling KVM support entirely, it
doesn't really make sense to do it on a per-machine level."
1773756,2018-06-07 20:28:07 UTC,"Hmm, pretty sure."
1773757,2018-05-31 07:03:51 UTC,#4141 - further refinement based upon feedback
1773757,2018-06-01 09:33:04 UTC,#4142 - further correction to tank locomotive coal animation
1773757,2018-06-04 02:30:30 UTC,#4150 - correct issue identifying whether tender or tank locomotive
1773757,2018-06-07 10:27:38 UTC,#4152 - correct issue causing crash with loose consist tenders.
1773757,2018-05-30 03:07:23 UTC,#4140 - Corrected problem introduced in #4138
1773757,2018-05-28 09:58:33 UTC,Patch added in #4138
1773759,2018-05-28 11:37:16 UTC,"To fix the issue, I edit the [nova] using this https://review.openstack.org/570225."
1773764,2018-05-29 07:51:51 UTC,"According to your analysis, wouldn't we solve the issue if we just replaced the `message` instance attribute with a class attribute?"
1773764,2018-05-29 08:20:00 UTC,"I think that what Eric thought -- call dispose_engine() only one time. But there are many people contributing to cinder project, it's hard to ensure every one of us will keep in mind that not creating new message API instance. I think that why this issue happens, people didn't follow Eric's rule."
1773765,2020-10-16 11:32:04 UTC,"This bug was fixed in the package masakari - 10.0.0~rc1-0ubuntu1~cloud0
---------------"
1773765,2020-10-26 19:00:57 UTC,Verified successfully for all corresponding proposed package versions:
1773765,2020-10-27 16:12:10 UTC,"The verification of the Stable Release Update for masakari has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1773765,2020-10-27 16:22:10 UTC,This bug was fixed in the package masakari - 9.0.0-0ubuntu0.20.04.3
1773765,2020-11-02 16:41:29 UTC,The verification of the Stable Release Update for masakari has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1773765,2020-11-02 16:41:33 UTC,"This bug was fixed in the package masakari - 9.0.0-0ubuntu0.20.04.3~cloud0
---------------"
1773765,2020-11-02 16:43:02 UTC,The verification of the Stable Release Update for masakari has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1773765,2020-11-10 00:51:39 UTC,"Reviewed:  https://review.opendev.org/758899
Committed: https://git.openstack.org/cgit/openstack/charm-masakari/commit/?id=62bc9c05b9cd438d45067e0efafe6fa75ef5b500
Submitter: Zuul
Branch:    master"
1773765,2020-10-14 20:37:58 UTC,"Hello takahara.kengo, or anyone else affected,"
1773765,2020-11-10 22:44:14 UTC,"Fix proposed to branch: stable/20.10
Review: https://review.opendev.org/762216"
1773765,2021-02-18 08:27:44 UTC,We are still seeing this happening in bionic ussuri
1773765,2021-02-18 08:28:48 UTC,"Version in use:
dpkg -l | grep masaka
ii  masakari-api                         9.0.0-0ubuntu0.20.04.3~cloud0                 all          Virtual Machine High Availability (VMHA) for OpenStack - API Server
ii  masakari-common                      9.0.0-0ubuntu0.20.04.3~cloud0                 all          Virtual Machine High Availability (VMHA) for OpenStack - Common Files
ii  masakari-engine                      9.0.0-0ubuntu0.20.04.3~cloud0                 all          Virtual Machine High Availability (VMHA) for OpenStack - Engine
ii  python3-masakari                     9.0.0-0ubuntu0.20.04.3~cloud0                 all          Virtual Machine High Availability (VMHA) for OpenStack - Python 3"
1773765,2021-02-20 15:30:52 UTC,This is fixed in a later Train release. The current is 9.1.1.
1773765,2021-02-20 15:31:06 UTC,Ussuri* release. Sorry for the confusion.
1773765,2020-11-02 16:43:04 UTC,"This bug was fixed in the package masakari - 8.0.0-0ubuntu1~cloud1
---------------"
1773765,2020-10-14 20:36:54 UTC,"Hello takahara.kengo, or anyone else affected,"
1773765,2020-11-02 16:46:51 UTC,"This bug was fixed in the package masakari - 7.0.0-0ubuntu1~cloud1
---------------"
1773765,2020-10-14 13:30:38 UTC,"Hello takahara.kengo, or anyone else affected,"
1773765,2020-10-14 20:35:19 UTC,"Hello takahara.kengo, or anyone else affected,"
1773765,2019-09-06 10:31:00 UTC,"Hit this bug yesterday, I was unable to reset my compute node status using"
1773765,2019-09-09 08:17:31 UTC,Logs from this deployment: https://drive.google.com/open?id=1Qir71XFHsjuumT9ApjbYKsaDoCp3jqoS
1773765,2020-04-02 09:50:39 UTC,I met the same problem recently.
1773765,2020-09-09 14:57:32 UTC,"Linking to the review:
https://review.opendev.org/#/c/720623/"
1773765,2020-09-23 12:01:38 UTC,"Reviewed:  https://review.opendev.org/720623
Committed: https://git.openstack.org/cgit/openstack/masakari/commit/?id=3a4f782441f6bdcfb8ee49a393937267fc246c56
Submitter: Zuul
Branch:    master"
1773765,2020-09-24 03:01:36 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/753921"
1773765,2020-09-24 03:12:44 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/753926"
1773765,2020-11-02 16:46:50 UTC,The verification of the Stable Release Update for masakari has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1773765,2020-09-24 09:18:52 UTC,"Reviewed:  https://review.opendev.org/753927
Committed: https://git.openstack.org/cgit/openstack/masakari/commit/?id=cd05dc31bb8c4ce529dac4698dd7bb80866a4139
Submitter: Zuul
Branch:    stable/stein"
1773765,2020-09-24 09:18:58 UTC,"Reviewed:  https://review.opendev.org/753926
Committed: https://git.openstack.org/cgit/openstack/masakari/commit/?id=e0423906a7aabb4ea02b754e041f725c16535be5
Submitter: Zuul
Branch:    stable/train"
1773765,2020-09-24 09:19:05 UTC,"Reviewed:  https://review.opendev.org/753921
Committed: https://git.openstack.org/cgit/openstack/masakari/commit/?id=b53155b314068a46cd097d3788add1b6d4fc0aff
Submitter: Zuul
Branch:    stable/ussuri"
1773765,2020-09-30 04:24:12 UTC,"The attachment ""groovy victoria patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1773765,2020-09-30 06:07:47 UTC,Groovy should really just use the newly-released RC1 of Victoria.
1773765,2020-09-30 19:53:11 UTC,Agreed that Groovy should just use the newly-released RC1.
1773765,2020-10-08 18:20:23 UTC,"@Billy, Thanks for your work on this. I've uploaded new versions of masakari to groovy, focal, train and stein [1] (note: minor changes to changelogs and I re-picked the stein patch from upstream stable/stein)."
1773765,2020-10-09 10:53:29 UTC,This bug was fixed in the package masakari - 10.0.0~rc1-0ubuntu1
1773765,2020-09-24 03:13:02 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/753927"
1773787,2018-06-05 09:36:27 UTC,updated project from kolla to kolla-ansible
1773787,2018-06-12 03:02:13 UTC,"At least in the master branch, the docker insecure registry configuration is done automatically during the bootstrap-servers play. You can find it in ansible/roles/baremetal/tasks/post-install.yml, in the 'Configure docker service' task."
1773787,2018-06-12 11:55:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/574702"
1773789,2019-01-17 15:07:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773789,2020-08-10 01:37:58 UTC,scala 2.10.4-400
1773791,2019-05-28 13:59:00 UTC,That's a duplicate of bug #1799562. Could you reply to the questions from the other bug?
1773792,2018-05-28 12:27:58 UTC,"Seems not to be an issue in Bionic, so marking tasks as that."
1773792,2018-05-28 12:29:18 UTC,Prio low since there were no field complains on this yet combined with the short remaining time Artful is supported.
1773793,2018-06-06 19:43:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572935"
1773793,2018-06-06 21:02:28 UTC,"I do think both these should be /32 and not /22.
A IPv4 with /22 is already defined on this bridge/interface. Creating another way out into this subnet is not the purpose."
1773793,2018-06-07 07:14:55 UTC,Agree. Checked in code:
1773793,2018-06-07 08:05:01 UTC,Fixed in new patchset
1773793,2020-10-13 15:24:49 UTC,"Reviewed:  https://review.opendev.org/572935
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=cc1cb3ad370412b744005e8de2d7d08c23932be5
Submitter: Zuul
Branch:    master"
1773794,2018-07-02 15:16:29 UTC,"It is fixed since `python3-pip - 9.0.1-2.3~ubuntu1`, tracked on https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1771624"
1773794,2020-05-22 13:43:13 UTC,Fixed in focal and later.
1773798,2018-06-10 07:53:29 UTC,how can i solve this problem pls any one recommend me
1773800,2018-06-01 15:24:26 UTC,Subscribed ~field-high as this issue affects a deployment with multiple ceph backends used.
1773800,2018-06-01 21:12:54 UTC,"Ah, perfect. Thank you for weeding out the devil in the details there and proposing a fix @dmitriis."
1773800,2018-06-01 23:16:48 UTC,"Frode, you are right about LVM and the old ceph handling case."
1773800,2018-06-06 10:49:29 UTC,"If only storage-backend relation is used multiple cinder-ceph <-> cinder relations seem to be handled properly (Queens, 18.02 charms)."
1773800,2018-06-06 10:54:08 UTC,"Great, lowering severity of the tasks in this bug then.  Keeping bug open as there is some untangling to be done wrt. who sets the hostname, whether it is in global or section config etc."
1773800,2019-01-07 12:01:46 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/571762
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.
Feel free to restore it again if you want to pick up and continue the work."
1773800,2018-06-01 14:58:51 UTC,"From the cinder perspective ""host"" option is a global option."
1773810,2018-06-05 12:45:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773810,2020-12-02 20:55:58 UTC,I believe I've been running into this same bug as well.  I've had it with Ubuntu 18.04 and now 20.04 both running as a VM under VirtualBox on Windows 20.
1773811,2018-08-08 12:30:47 UTC,Friendly ping. The bug is affecting most of the Bionic CI mechanisms that uses the gazebo simulator. i.e. https://github.com/ros-simulation/gazebo_ros_pkgs/pull/796#issuecomment-411387717
1773811,2019-02-27 16:24:33 UTC,Jeremy: thanks for the pointer. You were right Gazebo was not updated at that moment. I've update it during the last months and Debian and disco-proposed both have 9.6.0 which include the fix to this problem.
1773811,2018-06-13 04:08:43 UTC,I'm subscribing the SRU team to get their opinion prior to sponsoring it.
1773811,2018-09-18 23:59:51 UTC,"Jose, Ubuntu Stable Release Update policy requires that bugs be fixed in the current development release (currently Ubuntu 18.10 ""cosmic"") before being fixed in stable release updates."
1773811,2018-09-19 07:06:30 UTC,"Please could you also add an ""explanation of the bug on users and justification for backporting the fix to the stable release""? I don't feel that your current Impact section explains this. After reading it I still have the question ""how does this impact users?""."
1773815,2018-05-28 15:15:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773815,2019-10-27 10:07:54 UTC,"eyed3 0.8.8-1 is available in Ubuntu 19.04 and later. (Ubuntu Focal, the current development, just got 0.8.10-1 as well)"
1773822,2018-06-05 21:14:16 UTC,"Reviewed:  https://review.openstack.org/570802
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=6f242db4bcfc01281a4fe8f469014b0b48afd88d
Submitter: Zuul
Branch:    stable/newton"
1773822,2018-05-28 16:14:53 UTC,"Fix proposed to branch: stable/newton
Review: https://review.openstack.org/570802"
1773826,2018-06-12 19:25:11 UTC,"Hello human, I am the Open Rails Triage Bot (https://github.com/openrails/openrails-triage-bot)."
1773826,2018-06-12 19:31:11 UTC,"Hello human, I am the Open Rails Triage Bot (https://github.com/openrails/openrails-triage-bot)."
1773826,2018-06-12 19:22:34 UTC,"Hello human, I am the Open Rails Triage Bot (https://github.com/openrails/openrails-triage-bot)."
1773827,2018-05-28 19:10:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/570821"
1773827,2018-06-05 00:15:21 UTC,I cannot reproduce the issue in my env(neutron master branch)
1773827,2018-06-05 19:07:54 UTC,"@Hirofumi Ichihara,"
1773827,2018-06-06 05:15:28 UTC,I can do it. thank you.
1773827,2019-05-14 20:19:07 UTC,"Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.opendev.org/570821
Reason: This patch has been stale for awhile now. Moving it to abandoned to clean-up the queue. If this patch is still active, please push an update to it."
1773840,2018-08-26 06:16:38 UTC,"GMIC package in Ubuntu (and Debian) is very old - 1.7.9 release was released at 2016, lots of new versions in new stable branch 2.x.x were released in 2017 and 2018, see http://gmic.eu
Also GMIC 1.7.9 doesn't work with latest stable GIMP 2.10.x releases, it's ported to 2.10 only since 2.3.0 version, see https://discuss.pixls.us/t/release-of-gmic-2-3-0/6800"
1773842,2019-10-29 21:55:15 UTC,"The referenced pull request was closed without being merged into snapd. I'm not sure that there's anyone working on resurrecting it so I'm marking this as confirmed. Mvo, please feel free to remove yourself from the assignee field if you don't plan on working on implementing this."
1773842,2018-05-28 18:40:52 UTC,"I talked to mvo about that this morning, and he said, he might be able to work on this on his spare time as it look trivial to add this feature according to him."
1773842,2018-06-06 13:07:36 UTC,"I discussed this with Gustavo on the standup today. It seems like he prefers to not add a new feature but just use ""snap list | awk '{print $1""|""$2}'|tail +2"". Would that work for you? Or do you needs bits that are not visible via ""snap list""?"
1773842,2018-06-06 05:57:38 UTC,This is being worked on in https://github.com/snapcore/snapd/pull/5234
1773842,2018-06-06 14:19:53 UTC,"As long as ""snap list"" output remain the same and have no intention to change the output in the future, I guess it should be fine, I've been testing ""sosreport"" expected output with a similar command."
1773843,2019-09-05 07:32:48 UTC,"> there is no dogtag-pki in 19.04, so you can't do that
"
1773843,2019-09-04 22:29:50 UTC,"there is no dogtag-pki in 19.04, so you can't do that"
1773843,2019-09-04 18:51:04 UTC,Just tried upgrade from current Bionic (4.7.0~pre1+git20180411-2ubuntu2) to a local build from Disco sources (4.7.2-1ubuntu1).  Commented out ONLY_CLIENT=1 in debian/rules to build the server packages.
1773843,2019-01-28 08:53:07 UTC,"I think I do not have this problem anymore. There are still problems in upgrading from pre-releases to 4.7.1 (see #1800631), but probably for different reasons."
1773843,2019-09-04 18:12:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773843,2018-06-26 07:03:33 UTC,"probably a bug in dogtag, dunno.."
1773859,2018-12-04 12:30:45 UTC,"systemd now correctly conflicts with systemd-shim, and installing both simultaniously is now even harder:"
1773859,2019-01-28 18:20:20 UTC,The upload of systemd that was purported to fix this bug report was superseded by a security update of systemd so the fix is no longer available.
1773859,2019-01-29 21:09:04 UTC,"Muchas gracias por la información.
Si no es mucho consultarte, a veces cuando me pide actualizaciones las hago
y luego me dice que tengo el Ubuntu 14.   , que si lo quiero actualizar a
la ultima versión 16.   y no lo hago por miedo a que se me desbarate todo
de nuevo, cual es tu consejo?
Un saludo"
1773859,2019-01-29 21:23:20 UTC,"Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no
quieras perder y actualizarla a 18-04.
Funcionar funciona pero estás a punto de que no se actualice más, y puedes
tener problemas de seguridad, ojo se trata de una actualización importante,
que debes realizar, seguramente en dos pasos, dos actualizaciones
parciales. Primero a 16 y luego a 18-04.
Configura el gestor de actualizaciones a versiones LTS, no obstante la
18-04 tiene soporte para 10 años.
Saludos"
1773859,2019-01-29 21:35:55 UTC,"La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5
LTS.
Vale la pena actualizarla?
Graacias"
1773859,2019-01-29 22:34:22 UTC,"Si claro, luego te dirá de pasar a la 18-04.
Saludos"
1773859,2019-04-11 17:35:52 UTC, I ended up uninstalling everything and installing the 18.04 from sctratch.Thanks for your help
1773859,2019-01-30 11:08:46 UTC,"Una cosa.
Chequea el hardware en ocasiones equipos antiguos rinden mal o no rinden
con el 18
Si es un equipo moderno sin problemas.
También puedes valorar en utilizar escritorios más ligeros con equipos
antiguos XCFE Xubuntu o LXDE Lubuntu.
Yo con un equipo de 2007 y 2 GB ejecuto Xubuntu 18-04 sin problemas. Y en
un Netbook con 1 Giga Lubuntu.
Recuerda que Lubuntu ya no va a crear versiones de 32 bit a partir de la 18
04.
Saludos"
1773859,2019-01-30 20:12:58 UTC,¡Gracias!
1773859,2019-04-10 20:02:33 UTC,Looks like I can't install anything (or most things) until this gets fixed. Is there a consensus on the proper way to uninstall systemd-shim?
1773859,2019-04-10 20:20:44 UTC,"Good night looking for internet, there are many solutions. The treat can
help you. Kind regards.
Buenas noches, busca en Internet hay muchas soluciones a este problema,
creo que este hilo puede ayudarte.
Saludos"
1773859,2019-04-10 22:39:33 UTC,"Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es ""sudo apt purge gdm etc.""... ""etc."" que?"
1773859,2019-04-11 06:37:37 UTC,"Hola creo recordar que utilicé estos comandos:
sudo mv / usr / share / dbus-1 / system- servicios / org.freedesktop
.systemd1. servicio / usr / share / dbus-1 / system- servicios /
org.freedesktop .systemd1. Servicio. bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove"
1773859,2019-04-11 09:23:42 UTC,"This worked for me in quite a few upgrades. Before starting the upgrade to 18.04, still on 16.04:"
1773859,2018-11-30 07:14:08 UTC,"Mira esta solucion
Saludos"
1773859,2019-09-30 20:33:18 UTC,"Hello Kees, or anyone else affected,"
1773859,2019-09-30 21:33:05 UTC,"Hello Kees, or anyone else affected,"
1773859,2020-08-04 15:21:15 UTC,I got nipped by this bug today moving from 16.04LTS to 18.04 LTS
1773859,2020-05-29 11:43:51 UTC,Can confirm that these steps BEFORE REBOOTING lead to a working 18.04 system after the 16.04 upgrade fails.
1773859,2020-05-26 21:05:07 UTC,"This bit me today, 16.04LTS to 18.04 LTS"
1773859,2020-02-02 01:02:17 UTC,Just did an do-release-upgrade from 16.04 to 18.04 and ran into this issue as well. The following fixed it like mentioned above.
1773859,2020-01-24 08:46:34 UTC,I had this exact error when upgrading a 16.04 (amd64) with HWE (all packages up-to-date) to 18.04 today. So I wouldn't say this is fixed. Now trying to salvage it by moving the relevant file while the upgrade is going on...
1773859,2019-10-20 14:53:01 UTC,This is still broken as of today.
1773859,2019-05-14 19:48:56 UTC,Still affects me on release upgrade from latest 16.04 LTS with hwe installed...
1773859,2019-10-10 06:33:27 UTC,"Ok, thanks."
1773859,2019-10-10 02:41:46 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.31
1773859,2019-10-08 18:40:35 UTC,"Yes, based on the analysis that the failure is caused by buggy *rm scripts in an obsolete and already-uninstalled version of the systemd-shim package, I expected to still see failures with the new version."
1773859,2019-10-08 16:50:16 UTC,https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=systemd&period=month&version=237-3ubuntu10.31
1773859,2019-10-08 16:08:28 UTC,Verified with systemd 237-3ubuntu10.31:
1773859,2019-10-01 02:59:52 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1773859,2019-09-30 22:30:18 UTC,"Hmm, I don't have any systems left with systemd-shim installed, so I can't do a ""real world"" test of this. The test case is the description seems reasonable, so if that passes, I would consider this bug fixed. :) Thanks!"
1773859,2019-10-10 02:41:54 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1773859,2018-11-30 07:13:20 UTC,Hola mira esta solución.
1773859,2018-11-19 16:46:37 UTC,Similar experience on a DO instance.  Initial do-release-upgrade failure due to bug #1793932: exim4 deprecated conffile issue.  Now recovery is systemd-shim (9-1bzr4ubuntu1) blocked. @digitalcircuit's 2018-06-10 suggestion above did not work for me.  Will restore 16.04 and try again later.
1773859,2018-11-29 21:37:36 UTC,"Yo tambien tengo dudas de como resolverlo! I Still have some doubts on how
to fix it, but if in 7 days it will be available for everyone i will just
wait the update.
Greetings!"
1773859,2018-09-22 21:35:29 UTC,Just upgraded today from 16.04 to 18.04 and I got the same issue.
1773859,2018-09-14 05:59:02 UTC,A friend of mine also got this on upgrade (he's not skilled so was quite critical to him):
1773859,2018-08-24 16:48:16 UTC,I thought one aspect of the bug that nobody specifically highlighted was interesting:
1773859,2018-08-16 17:09:32 UTC,"I have tried with mine: bug #1787367.
Okay, the usual update / upgrade runs through now, though what got was just the removal of the systemd-shim, and nothing else. feh and flowblade have been kept back. OpenOffice 6.0 (just as example) remains uninstalled. How can I know what else remains missing? The awk command lists a dozen of rather irrelevant stuff."
1773859,2018-06-07 17:02:46 UTC,"The error complains that files will be overwritten, but this code runs in the systemd-shim postrm script, which is after systemd-shim's files have been removed from disk.  What does 'dpkg -S /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' report in this situation?"
1773859,2018-07-24 17:26:09 UTC,"I ran into this running a `do-release-upgrade -d` on a xenial machine at $work. The upgrade failed partway through leaving the system in a partial upgrade state afaict; lsb-release -a reports 18.04, but the apt sources are still xenial."
1773859,2018-10-04 14:56:22 UTC,"systemd-shim removed from the archive, so cannot be fixed really."
1773859,2018-07-14 02:08:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773859,2018-06-13 00:17:47 UTC,That certainly matches the copy of the file shipped in systemd-shim in xenial.  But I'm at a loss to explain why it's present on your system after dpkg has removed the package.
1773859,2018-06-12 23:53:42 UTC,"# cat /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
[D-BUS Service]
Name=org.freedesktop.systemd1
User=root
Exec=/usr/lib/x86_64-linux-gnu/systemd-shim"
1773859,2018-06-10 23:15:48 UTC,"Thanks, that confirms that the file existed before the upgrade.  I would still need a copy of this file to try to understand where it came from."
1773859,2018-06-10 21:04:49 UTC,"On Sun, Jun 10, 2018 at 07:38:26PM -0000, Shane Synan wrote:

> I just ran into this situation myself.  After I received the error
> report and let the upgrade recover, running the dpkg command gives me...
"
1773859,2018-06-10 21:02:19 UTC,Apologies for the double-comment.
1773859,2018-06-10 19:38:26 UTC,"I just ran into this situation myself.  After I received the error report and let the upgrade recover, running the dpkg command gives me..."
1773859,2018-06-13 04:54:05 UTC,"# dpkg -L systemd-shim
/.
/usr
/usr/lib
/usr/lib/i386-linux-gnu
/usr/lib/i386-linux-gnu/systemd-shim
/usr/lib/i386-linux-gnu/systemd-shim-cgroup-release-agent
/usr/lib/systemd
/usr/lib/systemd/ntp-units.d
/usr/lib/systemd/ntp-units.d/systemd-shim.list
/usr/share
/usr/share/dbus-1
/usr/share/dbus-1/system-services
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
package diverts others to: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
/usr/share/doc
/usr/share/doc/systemd-shim
/usr/share/doc/systemd-shim/copyright
/usr/share/doc/systemd-shim/changelog.Debian.gz"
1773859,2018-10-11 09:30:48 UTC,Just upgraded my server from 16.04 to 18.04 and I also came across this error.
1773859,2018-08-16 10:03:36 UTC,I just ran into this during do-release-upgrade from 16.04.5 to 18.04.1 as well among other issues. The suggested mv solution worked.
1773859,2018-10-15 16:37:34 UTC,This bug was fixed in the package systemd - 239-7ubuntu10
1773859,2018-10-12 06:48:40 UTC,"Just another ""me too"".  Renamed the file to bak, and had a semi-working system.  Also had to reinstall Nvidia driver since i was stuck at 640x480, that was fun...."
1773859,2018-11-27 17:55:41 UTC,"Lo siento Alejandro, no soy Lucas
 Saludos"
1773859,2018-11-27 17:41:58 UTC,Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make this test in the last weeks I will make them as soon as possibleRegardsAlejandro
1773859,2018-11-20 12:05:44 UTC,"Hello Kees, or anyone else affected,"
1773859,2018-11-19 18:31:36 UTC,"CONFIRM: @digitalcircuit's 2018-06-10 recommendation works to complete do-release-upgrade from 16.04.5 to 18.04.1, after addressing exim4 issue."
1773859,2018-11-19 17:01:37 UTC,"I solved problem sttoping services and erasing systemd-shim upon console.
After I could updating my pc, also, from console
Kind regards"
1773859,2018-11-19 16:55:24 UTC,"Thanks a lot for your help. I resolved my problem erasing systemd-shim and
updating.
I'll try new solution in another pc.
Kind regards"
1773859,2018-11-29 18:15:38 UTC,"José Enrique,disculpa y gracias por contestarme.Quería pedirte si me puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se cómo accederloMuchas graciasAlejandro
      -
      -
         -"
1773859,2018-11-15 19:24:58 UTC,Did this upgrade fail to happen because of the age of my desktop?  It's a Core 2
1773859,2018-11-19 14:03:43 UTC,"Hello Kees, or anyone else affected,"
1773859,2018-10-18 06:05:36 UTC,"Hy, in this moment I can't update my laptop or install any package or
program
Greetings"
1773859,2018-10-22 15:42:18 UTC,"Histill having the same problem  with the ""systemd-shim""I don't know how to fix it May be I will format everything and reinstall Ubuntu 18 againgreetings"
1773859,2018-11-29 21:43:02 UTC,Is there any package available that fix this thing?
1773859,2018-10-25 20:59:34 UTC,"this package failed to upgrade when is upgrading to ubuntu 18.04, may you help me to resolve this issue"
1773859,2018-10-26 14:54:09 UTC,"Sure, happy to try
On Thu, Oct 25, 2018 at 2:05 PM Jacob Ngalya <email address hidden>
wrote:"
1773859,2018-10-24 03:21:00 UTC,I got mine fixed with the following:
1773860,2018-05-29 23:07:10 UTC,"This may be hardware issue, note the CPU overheats several times and you're logging MCE events. Try installing the rasdaemon package and running ras-mc-ctl --summary to see what those are."
1773860,2018-06-17 18:26:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773861,2018-05-29 07:03:29 UTC,"> To me, Combine should not be capable of converting text to path.
"
1773861,2018-05-29 14:26:22 UTC,"Yes, I find that useful."
1773861,2019-12-11 05:58:02 UTC,Migrated to:  https://gitlab.com/inkscape/inbox/issues/1359
1773861,2018-05-31 03:24:11 UTC," > I think there was a ""fix"" recently so that path operations always ""convert to path"" instead of stating ""not a path"" for all ops that could be done after converting to path"
1773874,2018-05-29 16:22:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1773874,2018-09-29 22:20:57 UTC,I  no longer use a Nvidia card I have removed it and other system changes have occurred. This bug can now be closed.
1773875,2018-05-29 02:26:36 UTC,"StacktraceTop:
 OsAbort () at ../../../../os/utils.c:1361
 AbortServer () at ../../../../os/log.c:877
 FatalError (f=f@entry=0x5654a6887258 ""xf86OpenConsole: Switching VT failed\n"") at ../../../../os/log.c:1015
 xf86OpenConsole () at ../../../../../../../hw/xfree86/os-support/linux/lnx_init.c:238
 InitOutput (pScreenInfo=pScreenInfo@entry=0x5654a6b16700 <screenInfo>, argc=argc@entry=13, argv=argv@entry=0x7ffdc5aae818) at ../../../../../../hw/xfree86/common/xf86Init.c:569"
1773875,2018-05-29 03:50:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773875,2018-05-29 03:50:39 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/0a37e4ff57dad48b3e256cd80fdf6a65548a15f3"
1773875,2018-08-16 06:23:51 UTC,Possibly related to bug 1775764.
1773875,2019-04-06 08:49:52 UTC,"Since I reinstalled Ubuntu 18.04, I do not have this problem anymore.  I believe that a bug still lay hidden somewhere but the conditions to activate it is gone."
1773876,2018-06-18 08:11:11 UTC,"One thing I want to see is the test request as well as the worker's name, so you can see straight away if a particular test is causing problems."
1773880,2018-05-29 18:50:44 UTC,This might have regressed something:
1773880,2018-05-29 18:45:38 UTC,Then that api-ref extension code was moved out of nova into another library:
1773880,2018-05-29 18:35:20 UTC,The show all / hide all button was added in this change:
1773885,2018-05-29 18:15:35 UTC,"Good news
solved today (2018-05-29) with the latest update
you can cancel it
Thx"
1773885,2018-05-30 12:16:47 UTC,"Well ... actually not completely solved ...
because if you plug an USB key, the position on the Desk is upper left corner, and if there is already a file or a folder at this position, the icon key jumps onto it.
It's confusing to have 2 icons at the same place!!"
1773890,2018-05-29 04:43:58 UTC,it moved to bugs in openstack-helm-infra
1773894,2019-08-05 19:10:02 UTC,"Change abandoned by Paul Goins (<email address hidden>) on branch: stable/19.04
Review: https://review.opendev.org/674676"
1773894,2019-08-05 19:06:26 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/674676"
1773894,2019-07-19 13:43:53 UTC,"Reviewed:  https://review.opendev.org/671523
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=7b523f82cd139c83cf5a39335a112403d8c3cbfd
Submitter: Zuul
Branch:    master"
1773894,2019-07-18 16:32:04 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671523"
1773894,2019-09-04 19:41:03 UTC,"This was fix-committed against stable/19.07 at commit:
https://github.com/openstack/charm-ceilometer/commit/7b523f82cd139c83cf5a39335a112403d8c3cbfd"
1773894,2019-05-20 22:11:06 UTC,"The haproxy resource is still being created, but haproxy isn't even installed (19.04, Bionic).  The only way to get clean monitoring for this is to manually delete the resource from Pacemaker, by removing the lines:"
1773894,2018-11-28 20:58:24 UTC,Is this being caused because we still set a vip for an api that no longer exists?
1773894,2018-08-17 06:03:07 UTC,"Given that we need the ceilometer_agent_central to be managed by pacemaker, can we tweak the charm to just not create the VIP and haproxy resources?"
1773894,2018-07-02 14:58:45 UTC,"infact there is not much point in having hacluster deployed at-all in later releases - ceilometer is just middleware that sends and receives messages from RMQ - i.e. no VIP is needed, nothing to access."
1773894,2019-07-18 13:09:17 UTC,"This, unfortunately, has nothing to do with the VIp and everything to do with an assumption that was made in ancient history that every charm using hacluster had haproxy running. That needs a change in charm-helpers and to be synced into ceilometer."
1773894,2018-07-02 14:57:43 UTC,This is related to the removal of the ceilometer-api at Pike/Queens.
1773897,2019-03-18 07:00:12 UTC,Do you folks use gnome-control-center to pair?
1773897,2019-02-17 22:20:22 UTC,I too have had the same issue...
1773897,2019-02-07 17:34:12 UTC,Same issue with a fresh new install of Mint 19.1 (booted from USB) on a Dell Inspiron 7778 and bluetooth mouse HP Z5000. No problems with Mint 18.3
1773897,2018-12-19 10:44:48 UTC,"Mime is M585 and seems like it works with Bluez 5.50.
There are lots of fixes in Bluez master, maybe some commits fix the issue?"
1773897,2018-12-19 10:16:27 UTC,Ah indeed...
1773897,2018-12-19 09:45:57 UTC,"@Feng could you please rebuild for cosmic, too? I'll try it out then."
1773897,2018-12-19 09:05:29 UTC,"Seems like Bluez 5.50 fixes the issue, tried re-repairing BT mouse 5 times and it seems to work so far."
1773897,2018-12-18 19:05:32 UTC,"I have the same issue. Running Linux Mint with latest kernel.
Kernel: Linux 4.19.9-041909-generic #201812130432 SMP Thu Dec 13 09:34:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1773897,2018-12-17 11:03:45 UTC,"lsusb says ""Bus 002 Device 003: ID 8087:07dc Intel Corp."" here."
1773897,2019-03-18 07:22:57 UTC,Seems like it's because Logitech Far East mice need to be paired.
1773897,2018-12-19 09:56:41 UTC,Cosmic already has BlueZ 5.50
1773897,2019-03-18 07:23:52 UTC,Take a look at [1] if gnome-control-center is used:
1773897,2019-03-29 05:46:42 UTC,This bug is not about suspending and resuming.
1773897,2019-03-18 21:41:05 UTC,"I tried the pairing via the gnome control center, command line ( bluetoothctl ) and via blueman. These were done while in a gnome session however"
1773897,2019-03-19 03:34:44 UTC,"My intention is to ask you to try adding this entry to pin-code-database.xml:
<device vendor=""logitech far east"" type=""mouse"" pin=""0000""/>"
1773897,2019-03-25 08:42:52 UTC,"(In reply to Kai-Heng Feng from comment #9)

> My intention is to ask you to try adding this entry to pin-code-database.xml:
> <device vendor=""logitech far east"" type=""mouse"" pin=""0000""/>
"
1773897,2018-12-17 10:41:54 UTC,"Michał, does this happen to intel Bluetooth USB controller?"
1773897,2019-03-28 10:31:33 UTC,Added to Trello: https://trello.com/c/4fDA1uYR/291-bug1773897-regression-logitech-m337-mice-are-automatically-disconnected-after-connected
1773897,2019-03-29 05:10:05 UTC,I am using a Logitech M337 on Ubuntu 18.04 via Intel 8265 right now and cannot reproduce any bug.
1773897,2019-03-29 05:29:35 UTC,No it's not specific to Intel 8265.
1773897,2019-03-29 05:48:44 UTC,"As mentioned in the bug description, this bug only ever occurred on Intel 8265 with the M337 on bionic. All other issues should be discussed in other bugs."
1773897,2019-03-29 06:22:30 UTC,"> This bug is not about suspending and resuming.
The root cause is the same: the key doesn't get stored because it uses ""Connect"" instead of ""Pair"" for SSP devices.
"
1773897,2019-04-01 06:11:56 UTC,See bug 1822533 instead.
1773897,2019-04-06 09:41:25 UTC,It seems like the bug has been fixed in bluez 5.50-6. My Logitech M336 works now.
1773897,2019-04-12 13:39:19 UTC,I've backported the is_trusted/pair pointer devices changes in a bionic SRU and used bug #1779289 for the update (the bug here seems like it's not only about that)
1773897,2019-03-18 16:08:21 UTC,"(In reply to Kai-Heng Feng from comment #5)

> Do you folks use gnome-control-center to pair?
"
1773897,2018-12-12 14:08:18 UTC,"I'm back to having to re-pair a handful of times each boot. It seems every once in a while the pairing ""sticks"" and works until I have to reconnect it again."
1773897,2019-03-27 08:41:18 UTC,"Please backport this two MR:
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/13
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14"
1773897,2018-09-25 10:58:06 UTC,"Not sure what's changed, but I've recently had much better luck with the mouse connecting properly by itself."
1773897,2018-12-11 23:24:31 UTC,I can also reproduce this bug.
1773897,2018-05-29 05:50:11 UTC,Sounds similar to bug 1771733 (which will hopefully expire) or bug 1651433 (which is also XPS 13).
1773897,2018-05-29 05:51:17 UTC,"In the meantime, please run 'apport-collect 1773897' on the problematic machine to send us more information about it."
1773897,2018-05-29 05:54:52 UTC,"Please also attach the kernel log (dmesg) and the system log (journalctl -b) from the affected machine, capturing a period of time when the problem happens."
1773897,2018-05-29 05:56:03 UTC,"You may also wish to try a preview of BlueZ 5.49 from here:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez"
1773897,2018-05-29 05:59:31 UTC,"Another idea is to try installing 'linux-firmware', if not already, to ensure the wifi chip's firmware is up to date."
1773897,2018-05-29 06:25:33 UTC,"More information:
This issue does not cause by single commit."
1773897,2018-05-29 06:44:50 UTC,"Please answer all the above questions, and if you find it's still a problem in 5.49 (https://launchpad.net/~bluetooth/+archive/ubuntu/bluez) then please report the bug upstream here:"
1773897,2018-05-29 07:34:49 UTC,apport information
1773897,2018-05-29 07:34:52 UTC,apport information
1773897,2018-05-29 07:34:53 UTC,apport information
1773897,2018-05-29 07:34:55 UTC,apport information
1773897,2018-05-29 07:34:56 UTC,apport information
1773897,2018-05-29 07:34:58 UTC,apport information
1773897,2018-05-29 04:50:00 UTC,The attached file is the .snoop when I reproduced this bug.
1773897,2018-05-29 07:35:01 UTC,apport information
1773897,2018-07-10 16:03:30 UTC,I can also reproduce the bug.
1773897,2018-06-15 07:21:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773897,2018-05-29 08:12:50 UTC,"In bluez git, since ""6b34bdd96 (""shared/gatt-client: Fix not removing services that had disappeared"", 2017-05-24)"", this bug can be reproduced with low fail rate (around 1/10 or lower).
This commit is between 5.45 and 5.46.
Before this commit, I don't reproduce this bug (maybe the reproduce rate is very low.)."
1773897,2018-05-29 08:09:11 UTC,Filed a upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=199873
1773897,2018-05-29 08:05:07 UTC,"The BT 3.0 mouse is disconnected automatically after connected with the notebook.
The fail rate is around 9/10."
1773897,2018-05-29 07:59:16 UTC,This bug still can be reproduced in BlueZ 5.49.
1773897,2018-05-29 07:34:59 UTC,apport information
1773897,2018-05-29 07:44:51 UTC,"The attached file is the output of ""journalctl -b""."
1773897,2018-05-29 07:35:10 UTC,apport information
1773897,2018-05-29 07:35:08 UTC,apport information
1773897,2018-05-29 07:35:07 UTC,apport information
1773897,2018-05-29 07:35:05 UTC,apport information
1773897,2018-05-29 07:49:27 UTC,Thanks. Please try 5.49 (https://launchpad.net/~bluetooth/+archive/ubuntu/bluez). If the problem continues in 5.49 then please report the bug upstream here:
1773900,2018-05-29 06:12:57 UTC,RUNNING HANDLER [mariadb : wait for slave mariadb] ****************************************************************************************************************************************************************
1773900,2019-05-17 17:19:00 UTC,It may be the same issue as https://bugs.launchpad.net/kolla-ansible/+bug/1712087
1773907,2018-07-30 11:08:02 UTC,Google translate from Dutch to English indicates description is:
1773907,2018-07-30 11:09:07 UTC,"Hello
Thank you for submitting this bug and reporting a problem with Calibre."
1773910,2018-08-09 16:06:37 UTC,"This fix: https://review.openstack.org/584506 gets most of the process_request retrials filtered out. However, when a new unit is added, it will send a request for pool creation and that very first request is never filtered."
1773910,2018-07-20 20:27:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584506"
1773910,2018-07-18 07:57:57 UTC,"I proposed to have clients taking out their broker requests once they're done with.
Fix for Ceph Radosgw on: https://review.openstack.org/#/c/582172/
Will extend this solution for other ceph clients"
1773910,2018-07-18 07:57:17 UTC,"This issue is related to Ceph Broker. AFAIK, the broker was adopted as a way of access for ceph clients without actually calling ceph directly. For that, ceph clients register their intent (ex.: create pools) on relation data and that information is collected and processed by Ceph MON's process_request call. The ceph broker provides a simpler API for standard calls: create pools, delete them, etc."
1773910,2018-07-18 06:05:18 UTC,"On a large enough cloud, it has gotten into a state where processing broker requests takes longer than the leadership change timeouts, which causes leadership to change, which causes the charm to re-process all broker requests, which takes longer ... ad infinitum. A partial change has been made reducing that happening, but is an incomplete solution. It is certainly burning CPU cycles and can begin to take a very long time as it has to process key requests for _every_ related unit, be that clients, OSDs, or the various other relations"
1773910,2018-06-22 05:48:55 UTC,"A change is in progress at https://review.openstack.org/#/c/574734/to resolve this by tracking which broker requests have been processed. Once that is done, we can re-add broker processing to more hooks as they won't be re-processed."
1773910,2018-07-17 19:14:45 UTC,"Alvaro,"
1773910,2018-07-17 15:17:50 UTC,"Change abandoned by Chris MacNaughton (<email address hidden>) on branch: master
Review: https://review.openstack.org/574738
Reason: superseded"
1773910,2018-06-05 11:04:57 UTC,"Request is ""create-pool"", but it is skipped because pools already exist (this upgrade to ceph-mon was part of an operation to deprecate ceph applications, which have already been removed).
https://pastebin.canonical.com/p/kWpRMVHcJ4/"
1773910,2018-06-05 11:00:50 UTC,The above happens on cs:xenial/ceph-mon-24
1773910,2018-06-05 10:58:51 UTC,"Sample:
2018-06-05 10:53:21 DEBUG juju-log Processing request 18ecae9a-68a0-11e8-83b7-00163e1f050e
2018-06-05 10:53:27 DEBUG juju-log Processing request 56290312-68a0-11e8-9d9d-7cfe90aac490
2018-06-05 10:53:31 DEBUG juju-log Processing request 56c638da-68a0-11e8-ab14-7cfe90a82500"
1773910,2018-07-17 19:19:57 UTC,"Sorry, I guess #7 should be addressed to Chris."
1773910,2018-06-05 10:55:40 UTC,"Is there a workaround for this, apart from skipping mon_relation() exec?"
1773911,2018-06-04 08:24:37 UTC,"Change abandoned by Marcin Juszkiewicz (<email address hidden>) on branch: master
Review: https://review.openstack.org/570855
Reason: https://review.openstack.org/#/c/571723/ did the same"
1773911,2018-06-15 10:30:06 UTC,https://review.openstack.org/#/c/571723/  has been fixed. mark this as fix commited.
1773913,2018-06-07 15:56:21 UTC,"Juju always runs production with --replSet, but I think we don't for the test suite. Either we should (but we should watch out for heavy allocations for the oplog), or we should have ways to disable some of the workers that don't make sense to run during the test suite."
1773914,2020-01-25 17:58:26 UTC,"GetDeb is not part of the official Ubuntu repositories so changing status to ""Invalid""."
1773914,2018-06-26 22:45:16 UTC,GetDeb isn't responding? WTF? Guess this repo is dead.
1773914,2018-05-30 10:57:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773919,2019-06-18 12:10:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773925,2021-01-21 10:08:38 UTC,This has been covered with https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/504094
1773925,2019-03-29 17:14:50 UTC,"Change abandoned by Dmitriy Rabotjagov (noonedeadpunk) (<email address hidden>) on branch: master
Review: https://review.openstack.org/597129"
1773925,2018-08-28 13:47:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/597129"
1773925,2018-08-20 13:52:47 UTC,"Change abandoned by Dmitriy Rabotjagov (noonedeadpunk) (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/593539"
1773925,2018-08-20 13:52:32 UTC,"Change abandoned by Dmitriy Rabotjagov (noonedeadpunk) (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/593538"
1773925,2018-08-20 11:23:49 UTC,"Reviewed:  https://review.openstack.org/593577
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-ceph_client/commit/?id=8ec0e6c7931497deae21b2b8919243c12df9673f
Submitter: Zuul
Branch:    master"
1773925,2018-07-19 12:08:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/583943"
1773925,2018-08-20 08:33:02 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/593539"
1773925,2018-05-29 17:00:22 UTC,"Hi Juha, Were you able to resolve this issue? if so how? Looks like we need to do some work in the ceph client role to remove root assumptions. Given that this is a known requirement of the playbooks we're marking this as wishlist however if there's something we can do to help this along please report the steps to resovle here or join the OSA channel and let us know how best to assist."
1773925,2018-05-31 18:55:04 UTC,"Hi Kevin, thank you for the response and taking this into wishlist. I resolved this simply by setting"
1773925,2018-06-14 10:42:20 UTC,"I have an addition to this post. Playbook fails, if you are using non-standart SSH ports for all of your resources."
1773925,2018-08-20 10:48:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/593577"
1773925,2018-08-19 19:54:20 UTC,"Reviewed:  https://review.openstack.org/583943
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-ceph_client/commit/?id=58ac4da336810e9aca4f0bafc2e9116dc997653b
Submitter: Zuul
Branch:    master"
1773925,2018-08-20 08:28:07 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/593538"
1773925,2018-07-19 12:28:04 UTC,"Change abandoned by Dmitriy R. (<email address hidden>) on branch: master
Review: https://review.openstack.org/583943"
1773933,2020-04-21 19:14:09 UTC,"The extra control characters looks related to the color output which was added in Maven 3.5.x. You have probably found this in the meantime, but could you try to add `-B` for batch mode when running mvn and see if that helps? That should disable the color, and also the incremental lines when downloading packages among other things..."
1773933,2020-04-22 07:43:17 UTC,"Yes, indeed, I did find --batch-mode in the meantime, thanks."
1773937,2020-08-15 18:44:37 UTC,This looks like https://gitlab.com/inkscape/inkscape/-/issues/135 which is solved :)
1773945,2018-06-06 17:03:15 UTC,From the cells v2 meeting today about the nova side of this bug (comment 9):
1773945,2019-08-31 00:50:25 UTC,"Reviewed:  https://review.opendev.org/666438
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1ff029c1c3792f53865c6bdb3dce8d2c51b73ca7
Submitter: Zuul
Branch:    master"
1773945,2019-06-19 20:36:33 UTC,Marking this as incomplete since I'm not sure if we have an action to take.
1773945,2019-06-19 20:35:05 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/575556
Reason: I'm going to drop this in favor of https://review.opendev.org/#/c/666438/ and https://review.opendev.org/#/c/655908/. There could still be unaccounted for cases where the build request is gone, the instance is in a cell and the instance mapping is not pointing at a cell (maybe the instance mapping update was dropped by the DB or something - these aren't atomic operations). We can try to shore up more of that flow, e.g. https://review.opendev.org/#/c/586713/ but I'm going to drop this in the meantime since it was really just for debug purposes."
1773945,2019-06-19 20:32:20 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/666438"
1773945,2018-06-14 22:01:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575556"
1773945,2018-06-08 14:17:04 UTC,This issue was fixed in the openstack/python-novaclient 10.3.0 release.
1773945,2018-06-05 20:18:59 UTC,For this code:
1773945,2018-06-05 20:17:18 UTC,Revert https://review.openstack.org/#/c/572539/
1773945,2018-06-05 19:54:01 UTC,"I never understood the need for change https://review.openstack.org/#/c/534222/ and think we should probably revert it. If users want to list all instances, they can pass nova list --limit -1 to do that. The author of that change even said in the queens backport that it wasn't a problem for them anymore so they weren't sure what changed:"
1773945,2018-06-05 19:39:24 UTC,"I hit something similar last week in python-openstackclient when listing servers, I was getting a marker not found error even though I wasn't passing a marker, but something in the CLI (or nova python API binding code) was. I ran into this after rabbitmq crashed during scheduling a large number of instances in a single request, and I think I also noticed that there were instance_mappings records with no cell_id set."
1773945,2018-06-04 15:34:12 UTC,"We don't have those log files anymore, sorry."
1773945,2018-06-04 15:07:13 UTC,"However, NULL cell_mapping should not be an issue because for those instances who have an instance record in the the cell DB, but their instance_mapping has a NULL cell_mapping, meaning instances which are not yet scheduled, will have build_requests and as per (https://github.com/openstack/nova/blob/f902e0d5d87fb05207e4a7aca73d185775d43df2/nova/compute/api.py#L2402-L2408) the marker is set to None if its found in the BuildRequest table. So I don't fully understand what is the issue. @dberk, could you please attach the n-api logs if possible?"
1773945,2018-06-04 08:00:30 UTC,My guess is as follows:
1773945,2018-05-31 07:54:18 UTC,seems this is a python nova client issue ?
1773945,2018-06-06 03:59:16 UTC,"Reviewed:  https://review.openstack.org/572539
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=abaa86fd86d4beca0082ff1768d5306e5e86302e
Submitter: Zuul
Branch:    master"
1773945,2018-06-04 12:26:19 UTC,"I also reproduced the same error when doing nova list --marker ""uuid"" for a uuid that has NULL CellMapping in the InstanceMapping. @natsume-takashi, looks like your guess is right."
1773947,2019-11-30 16:54:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773950,2018-05-29 12:49:50 UTC,This is from the upgrade log:
1773950,2018-05-29 16:19:58 UTC,"I've got it, but now what should i have to do to solve this matter?
Any help is highly appreciated, Thks"
1773951,2018-05-30 02:35:22 UTC,this might need consult with Ubuntu doc ...
1773951,2018-11-28 07:13:35 UTC,I wrote the configuration items into codes and fix this.
1773951,2018-11-28 07:23:35 UTC,I suggest you add the patch link into bug so that we know where to find fix if any problem related occurs
1773951,2018-11-28 07:49:16 UTC,"OK. as a reference, the patch link: https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/432403"
1773953,2018-11-23 05:58:54 UTC,so this is a valid bug or not?
1773953,2018-11-23 06:12:51 UTC,I refine the code and this problem did not happen again. closed.
1773953,2018-06-14 08:23:52 UTC,I found the solution but still do not know the reason of this problem.
1773957,2020-03-12 16:56:28 UTC,"I'm unable to replicate this issue in Inkscape 1.1-dev (12e2a09, 2020-02-19), Windows 10. Following your steps, the clipped rectangle has all transform handles. Please reopen on http://inkscape.org/report if the problem occurs again."
1773965,2020-10-10 10:43:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773965,2018-05-29 11:10:11 UTC,Upstream bug report: https://github.com/mate-desktop/mate-media/issues/99
1773967,2020-02-24 19:15:28 UTC,This issue was fixed in the openstack/keystone 14.2.0 release.
1773967,2019-11-14 17:04:55 UTC,"Reviewed:  https://review.opendev.org/694096
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=578be15629a84d1edcfda546a93b7ccbb6959720
Submitter: Zuul
Branch:    stable/queens"
1773967,2019-11-14 01:11:05 UTC,"Reviewed:  https://review.opendev.org/689575
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=cf83fc10569e7b52eeb52c0e164dfe36daeec309
Submitter: Zuul
Branch:    stable/rocky"
1773967,2019-11-13 15:31:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/694096"
1773967,2019-10-18 20:29:14 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/689575"
1773967,2019-10-18 20:10:43 UTC,"Reviewed:  https://review.opendev.org/676200
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=933ea511d150ed2cbbd4265fc7513a9b3435baa2
Submitter: Zuul
Branch:    stable/stein"
1773967,2019-09-27 09:10:25 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1773967,2018-06-08 16:36:07 UTC,"Look at the trust code, as it solves this problem.  Trusts and App Creds should use common code."
1773967,2019-08-07 00:33:33 UTC,"Reviewed:  https://review.opendev.org/655166
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=14b25bc5d18842210cfffe1afdca475e848b84aa
Submitter: Zuul
Branch:    master"
1773967,2019-07-25 06:14:04 UTC,"Change abandoned by Gauvain Pocentek (<email address hidden>) on branch: master
Review: https://review.opendev.org/669886"
1773967,2019-07-09 15:04:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669886"
1773967,2019-06-08 15:10:46 UTC,"I filed a separate issue for what was described in #5 because the original bug description says that an application credential can be created, whereas in #5 it cannot be created and the failure happens before the application credential is persisted into the Keystone db."
1773967,2019-05-16 07:09:03 UTC,"Encountered the same with a federation use-case. A user doesn't have direct role assignments for a project and the user is also not present in a group (in the keystone db) that has a role assignment on the project. However, the federated domain-scoped token and a project-scoped token created based on the federated one both have group membership information present => the user has the Member role on the project."
1773967,2018-12-07 10:28:33 UTC,"Relatedly, application credentials don't work with implied roles. Since we now have the ""member"" role by default imply the ""reader"" role, the ""reader"" role appears in the token body and the user is allowed to create an application credential with it, but since it is not part of the role assignments table, the application credential can't then be used with just the ""reader"" role."
1773967,2018-11-29 01:49:26 UTC,"Hi Edward,"
1773967,2018-11-29 00:07:31 UTC,Any update on this?  I just ran into this issue and spent some time in IRC debugging with lbragstad I am willing to take a hacky patch I can apply to keystone 14 release.  I am using Centos 7 with Openstack Rocky installed.
1773967,2019-08-13 14:10:10 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/676200"
1773967,2019-08-13 14:12:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1773970,2018-05-29 17:12:15 UTC,"If the external source supports syncing to MIDI clock (Bug #682221), Ableton Link (Bug #1625050), or JACK transport (Bug #1130864), it would be better to use those instead of trying to detect the BPM of a live input. Nevertheless, detecting the BPM of live inputs would be helpful when none of those syncing protocols are supported."
1773970,2019-10-08 05:24:36 UTC,Discussed here https://github.com/mixxxdj/mixxx/pull/172
1773972,2018-05-29 12:11:18 UTC,"dig +multi  @10.196.245.203 sample.mysuperopenstack.org. soa
dig +multi  @10.196.245.201 sample.mysuperopenstack.org. soa
differ in serial."
1773972,2018-05-29 11:41:10 UTC,sample named.conf:
1773974,2019-09-03 23:10:13 UTC,"This project is used to tracks bugs and source code for system stack snaps (bluez, network-manager, ...) published by Canonical. If you're having problems with Ubuntu itself, please file a bug against the Ubuntu project:"
1773988,2018-05-29 14:00:53 UTC,"I worked around this in 'image-status' at
 https://github.com/smoser/talk-simplestreams/commit/4a6ba35856e3b8f794eda664d55857e09eb56b91"
1773990,2018-05-29 19:23:28 UTC,Yes it does. This bug report was then triggered automatically upon booting.
1773990,2018-05-29 16:00:05 UTC,This change was made by a bot.
1773990,2018-05-29 15:38:43 UTC,Does your system boot if you select the previous kernel version from the GRUB menu?
1773995,2018-05-29 15:17:24 UTC,I can confirm this behavior on 3.0.8 release @ C/W MARS.
1773995,2019-03-19 13:59:55 UTC,SCLENDS has signed a contract with Equinox to address this bug.
1773995,2019-09-10 19:36:25 UTC,Here's a branch for this:
1773997,2018-06-15 22:06:42 UTC,I also encountered this and haven't found a workaround as of yet.
1773997,2018-07-17 17:33:13 UTC,"I found some *kind* of workaround as it does not involve netplan directly. In the generated *.network file add ""ConfigureWithoutCarrier=true"" in the ""[Network]"" section."
1773997,2018-07-23 10:01:53 UTC,A fix for this landed in git 10 days ago: https://github.com/CanonicalLtd/netplan/commit/978e20f902f6b92a46dc6e0050e2172e834e4617
1773997,2018-12-13 20:17:54 UTC,"I had an interesting experience in Bionic with netplan.  setting
bridges:
  br0:
    interfaces: []
    addresses: [10.0.0.x/29]
before the ""ethernets"" section resulted in every interface on the host getting assigned this address and brought state-UP though physical-links were down."
1773997,2019-06-06 23:51:20 UTC,"I ran into this issue (on Ubuntu 18.04 LTS / Bionic) yesterday.  I have some bridges for virtual machines to connect to, which have IPv4/IPv6 addresses associated with them, and some services that listen only on those addresses (just for the VMs benefit), so I need the bridges to start earlier than, eg, libvirt bridges.  But since traffic from those VMs is *routed* not bridged to the outside world, there's no relevant physical interface to bridge them to."
1773997,2019-07-23 08:42:08 UTC,@daxtens any chance to backport it for bionic? it's kinda pity bug for LTS release...
1773997,2019-07-24 13:02:08 UTC,"It should already be in Bionic; 0.97 is what is available in all releases at this moment, so if it's not working, either we didn't quite get the fix right, or your setup is slightly different, enough to make the fix not work for you."
1773997,2019-07-27 22:53:56 UTC,"Ubuntu 18.04 LTS, config with work around (and eno2 physically patched to something providing Ethernet carrier):"
1773997,2019-09-26 04:17:55 UTC,[Expired for netplan because there has been no activity for 60 days.]
1774000,2018-05-30 06:10:38 UTC,"Setup as assumed above:
1. Host Bionic
2. Guest1 Cosmic
3. Guest2 Cosmic or CirrOS"
1774000,2018-05-29 15:24:36 UTC,"Found it. This happens as soon as you install tuned, which auto-starts tuned.service. After ""systemctl stop tuned"", QEMU works again. Retitled accordingly, so this is not a regression."
1774000,2018-05-29 20:52:33 UTC,"I tested this on Fedora 28, which also has tuned 2.9.0, but a slightly newer QEMU (2.11.1, as opposed to 2.11 on Ubuntu 18.04), and a newer kernel (4.16.10 instead of 4.15.0 in Ubuntu 18.04)."
1774000,2018-05-29 17:17:09 UTC,"@Martin,
Can you file this upstream with 'tuned' ? or is it not a problem with upstream?"
1774000,2018-05-30 05:44:06 UTC,"Hi Martin,
tuned is usually not installed, at least not on the new guest you are booting, so to be sure are we talking about this setup:"
1774008,2018-11-06 20:11:16 UTC,Opened bug #1801998 for the 3.2 deprecation phase.  Will follow up here for 3.3 cycle of removing the option entirely.
1774008,2019-05-23 21:20:27 UTC,The fix for this bug should only affect the AngularJS Hatch admin interface.  Hatch proper (the Java libs) will continue to use file storage for workstation management (bug 1825896) and print-to-file support (bug 1824391).
1774008,2020-08-05 18:21:40 UTC,Branch pushed:
1774008,2020-09-23 16:46:34 UTC,Tested successfully - my signoff is at:
1774008,2020-09-30 19:54:20 UTC,I've pushed this to master and rel_3_6 so we can wave goodbye to local settings storage in 3.6. Thanks Bill and Terran!
1774029,2019-01-01 18:08:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774029,2018-05-30 17:10:37 UTC,boot-info file...
1774029,2018-05-29 17:16:01 UTC,And dmesg with non working kernel...
1774029,2018-05-30 06:26:55 UTC,From boot.log there are several timeout and dependency failure for the mount points
1774029,2018-05-29 17:18:11 UTC,bootlog when not working...
1774029,2018-05-30 11:02:10 UTC,"Hi,
You're right but I get them as well with the working kernel.
How would I fix that though ?"
1774029,2018-05-29 17:11:37 UTC,This is the bootlog I get with the old (working) kernel
1774039,2018-06-13 19:46:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774039,2018-10-29 12:46:49 UTC,"se possível, gostaria de receber somente atualizações compativeis com minha máquina."
1774040,2018-05-29 20:17:40 UTC,"Sorry, I installed on computers with Ubuntu 16.04 LTS server and verified that Openstack Queens needs to be installed on the Ubuntu 18.04 LTS server. For this reason conflicts were occurring with libapache2-mod-wsgi-py3 installed by gnocchi and libapache2-mod-wsgi installed by keystone. You may consider this bug to be invalid."
1774040,2018-05-30 20:09:50 UTC,This bug is confirmed in:
1774042,2019-09-06 15:13:30 UTC,I see this is considered low and is over a year old. Any idea if/when this will be fixed?
1774042,2019-09-06 15:31:03 UTC,"I've not seen this stack track in a long time, so no ETA on a fix at this time."
1774042,2019-09-06 17:35:20 UTC,Are you currently seeing this fail?  If so do you have more details?
1774044,2018-11-17 11:08:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774044,2018-11-29 20:53:25 UTC,"maybe this fix things....
https://github.com/amule-project/amule/pull/147"
1774046,2018-08-11 17:50:58 UTC,"Xubuntu hides the Thunar entry by default [1] and only shows the exo wrapper ""File Manager""."
1774046,2019-04-22 09:51:04 UTC,Thanks reported in https://goo.gl/XVUN7p
1774046,2018-09-24 10:00:02 UTC,This bug was fixed in the package xubuntu-default-settings - 18.10.2
1774046,2018-09-18 11:42:23 UTC,Fix applied at https://git.launchpad.net/xubuntu-default-settings/commit/?id=4add212de743751ae608dfaa2e40123d1f322db3
1774046,2018-09-18 10:36:56 UTC,"Deleting that .desktop file would let Thunar show up as ""Thunar File Manager"" in whisker menu (generic application names are not shown by default)."
1774046,2018-05-29 19:26:03 UTC,Reported the issue over at Launchpad: https://bugs.launchpad.net/xfce4-whiskermenu-plugin/+bug/1774046
1774046,2018-04-06 10:28:10 UTC,"I  may have been mistaken about being able to adjust Whisker menu. I was referring to MenuLibre (https://bluesabre.org/projects/menulibre/), which allows me to add keywords as metadata to apps, I think; please see here: http://i.imgur.com/gEHmltO.png, sorry about the Dutch language- I refer to the field ""Trefwoorden"", which I would translate as ""Keywords"". I take it that this field gives me the possibility to put in ""thunar"", and that then thunar can be found by typing... Haven't tested this yet, though."
1774046,2018-04-06 15:39:11 UTC,"No problem. Will head over de #xubuntu-devel and try to get their attention. :-)
Thank you for looking into this issue."
1774046,2018-04-06 15:00:22 UTC,"The more I look into this, the more it looks like something you need to report to Xubuntu. For some reason, garcon is not loading the /usr/share/applications/Thunar.desktop file, which means that Whisker Menu doesn't see Thunar."
1774046,2018-04-06 09:22:18 UTC,"Interesting. When I run Xubuntu in a virtual machine, I also can't find thunar when I search for it by name. I will have to investigate further."
1774046,2018-04-05 16:03:39 UTC,"I use Xubuntu 18.04 at the moment (daily-iso).
Linux Xubuntu-18-04 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1774046,2018-04-05 15:34:42 UTC,"It does for me with the default settings. When I search for ""thunar"", I get the result ""Thunar File Manager"". What distro are you using? What do you see?"
1774046,2018-04-05 13:34:20 UTC,"As Thunar is the default xfce-filemanager and whiskermenu allows the user to find an app by typing its name, I think whiskermenu should allow the user to find and start thunar by typing ""thunar"", just like typing ""fire..."" finds firefox, and ""write"" finds libreoffice write.
I realize that the user can adjust whiskermenu to make it possible to find thunar by name, but I feel the default settings of whiskermenu should allow for thunar to be found by name.
Using whiskermenu version 2.1.5"
1774046,2018-05-29 18:42:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774049,2018-09-17 23:34:40 UTC,"$ lsb_release -l
Usage: lsb_release [options]"
1774049,2018-07-12 22:22:04 UTC,"Thank you, although we are still missing the Ubuntu version. Nevertheless, your issue may be shown here: https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#df-and-du-report-different-information and the next FAQ question."
1774049,2018-09-11 04:17:51 UTC,[Expired for coreutils (Ubuntu) because there has been no activity for 60 days.]
1774049,2018-06-23 03:09:38 UTC,"I am sorry, but this does not match with what you reported."
1774049,2018-06-23 01:24:10 UTC,"For the partition that's out of space I get:
/dev/sdc1        116M  989K  115M    1% /media/data"
1774049,2018-06-17 08:14:06 UTC,"Could you please check what `df -i` reports to see if you have available inodes on that partition? Inodes are roughly explain description of files or directories, and especially with small partions with lots of tiny files it is possible to run out of them. Unfortunately, too few inodes will report the same error message as no space, so this might be what is happening..."
1774049,2018-05-29 20:23:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1774049,2018-07-12 20:41:07 UTC,"df -i
Filesystem     Inodes IUsed IFree IUse% Mounted on
udev             982K   578  981K    1% /dev
tmpfs            997K   943  996K    1% /run
/dev/sda1        7.0M  392K  6.7M    6% /
tmpfs            997K     3  997K    1% /dev/shm
tmpfs            997K     6  997K    1% /run/lock
tmpfs            997K    18  997K    1% /sys/fs/cgroup
/dev/sdc1        116M  991K  115M    1% /media/data
tmpfs            997K    27  997K    1% /run/user/1000"
1774050,2020-04-09 16:00:39 UTC,"Thank you for taking the time to report this. Bugs against snaps must be reported on snapcraft.io. This bug report is filed against the Ubuntu package in the Ubuntu repos, which does not include snaps."
1774053,2018-05-30 02:37:56 UTC,Also tracking in https://bugzilla.gnome.org/show_bug.cgi?id=728158
1774053,2018-07-19 07:03:38 UTC,Also reported with Intel graphics (bug 1782458)
1774053,2018-07-19 07:04:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774053,2018-07-19 07:05:06 UTC,The upstream bug is also Intel: https://bugzilla.gnome.org/show_bug.cgi?id=728158
1774065,2018-06-11 17:45:47 UTC,"I workarounded it on Weekend [1]. I wanted to test it before the commit into the Yade's trunk. There are really problems with the new numpy 1.14, python 2 and bz2. tar.gz works."
1774065,2019-02-05 20:22:22 UTC,moved from https://bugs.launchpad.net/yade/+bug/1774065 to https://gitlab.com/yade-dev/trunk/issues/41
1774065,2018-06-11 17:12:54 UTC,"Bug Watch released a fix?... how?
B"
1774065,2018-06-08 09:24:10 UTC,"Thanks for reporting.
The strange part is that numpy 1.14 is still supporting bz2 according to the documentation.
Could someone confirm ""ValueError: bz2 text files not supported in python2"" on his system with the following code:"
1774065,2018-06-08 14:51:02 UTC,I have numpy 1.11.0 actually
1774065,2018-05-29 21:31:25 UTC,This was found in Ubuntu autopkgtests (at https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/y/yade/20180529_175759_38e3f@/log.gz)
1774065,2018-06-09 21:05:00 UTC,Workaround is to use tar.gz instead of bz2.
1774065,2018-06-08 09:37:39 UTC,I do not confirm it:
1774065,2018-06-08 10:08:52 UTC,"@Jérôme
And you have numpy 1.14?"
1774070,2018-05-29 22:16:13 UTC,Related bug: https://bugs.launchpad.net/evergreen/+bug/1774071
1774070,2018-09-12 18:08:40 UTC,"It seems best that the search would just not be case-sensitive. Since the term is the same, that seems like it would solve the issue fairly handily."
1774070,2020-07-31 17:48:43 UTC,"This is addressed in the Angular rewrite of the search interface (bug 1850547), which uses auto-completing dropdowns to allow the user to select the status they want to search for or filter the grid results on."
1774071,2018-05-29 22:15:59 UTC,Related bug: https://bugs.launchpad.net/evergreen/+bug/1774070
1774071,2018-05-30 00:50:15 UTC,Adding a note that we included this request in the requirements for the project to move acq to Angular.
1774071,2020-07-31 17:49:26 UTC,"This is addressed in the Angular rewrite of the search interface (bug 1850547), which uses auto-completing dropdowns to allow the user to select the status they want to search for or filter the grid results on."
1774081,2018-05-30 02:41:11 UTC,"The problem has already been reported here:
https://gitlab.gnome.org/GNOME/gdm/issues/317"
1774081,2018-05-30 02:39:59 UTC,Sounds like it should work. The docs say:
1774083,2018-05-30 00:35:27 UTC,"Ah, good news abounds:"
1774087,2018-08-13 18:39:35 UTC,I'm converting text to paths and it is crashing for me. The crash is unpredicatable but happens without fail
1774087,2018-08-13 18:40:05 UTC,Ooops. Forgot to add Xubuntu 18.04.1
1774087,2018-08-13 18:59:20 UTC,"For me, the crashes were with the version in the official Ubuntu 18.04 repository. I uninstalled it and added the stable PPA (https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable). So far this updated version hasn't crashed for me."
1774087,2018-08-13 19:37:43 UTC,"Interesting. Aren't they the same versions?... 0.92.3 should be the number for both. Is that correct, slumbergod?"
1774087,2020-05-10 16:55:57 UTC,Closing because there was no response
1774087,2018-07-25 03:20:29 UTC,i've same problem too.
1774098,2018-05-30 04:14:19 UTC,"Tested with 4.17rc7, issue still exist."
1774099,2018-05-30 07:55:03 UTC,"BTW this issue is a bit difficult to reproduce.
I can't see this just after a reboot. Nor with the upstream kernel 4.17rc7 installed."
1774102,2018-05-30 04:15:06 UTC,"Tested with 4.17rc7, issue still exist."
1774102,2018-05-30 14:36:36 UTC,Should be fixed by systemd in -proposed pocket. LP: #1762385
1774105,2018-05-30 07:10:19 UTC,"Tested with 4.17rc7, issue still exist."
1774112,2018-05-30 06:20:24 UTC,"4.17-rc1
14862ee308bbcaae0ac9927b6cbccccb51386b6c
9aaa3b8b4c56d24210acef37b7c800ca218c3d40"
1774112,2018-07-26 15:50:18 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1774112,2018-08-07 10:37:49 UTC,"sorry, it can be public. Ignore last comment"
1774121,2020-06-02 11:50:17 UTC,"Hello Thomas,"
1774121,2020-06-02 11:25:49 UTC,"(In reply to tasso.mulzer from comment #7)

> I can't ""Save all"" attachments with an ""Open"" dialog - it just won't save anything anywhere, at least in linux.
"
1774121,2020-05-22 13:07:27 UTC,"(In reply to tasso.mulzer from comment #7)

> Wow .. this bug really lives in Thunderbird for 11 years, now?!
"
1774121,2020-05-22 12:36:27 UTC,"Wow .. this bug really lives in Thunderbird for 11 years, now?!
I just changed to thunderbird some days ago - it causes me pain when saving attachments. I'll almost call this button (Save all) broken.
Severity of ""minor"" doesn't fit here."
1774121,2018-08-03 09:59:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774121,2013-10-09 17:21:46 UTC,*** Bug 736271 has been marked as a duplicate of this bug. ***
1774121,2011-11-13 17:34:17 UTC,"This is a problem on Linux too.
It seems the FilePicker in this case is called with Mode=""select_folder"" and then the native toolkit (GTK, QT, Win32,...) will pick the text on the button (Open). This mode is probably needed to allow choosing a folder only."
1774121,2010-08-19 20:23:29 UTC,I don't know about the Mac but I don't think Windows lets you change it either.
1774121,2010-08-19 19:26:23 UTC,"I don't think this is a bug in Thunderbird but rather a bug in the native Mac OS filepicker that should say ""select"" or maybe ""pick this"" instead of saying open. I'm not sure we can customize this... Neil, any thoughts?"
1774121,2009-11-30 08:50:19 UTC,"Created attachment 415090
Save all Atachments dialog in TB3"
1774121,2013-10-09 17:12:23 UTC,"Per comment 4, this is not only seen on MAC, but also on Linux -> Platform: All (in lack of more refined options)"
1774121,2009-11-30 08:47:38 UTC,"User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091112 Thunderbird/3.0"
1774132,2018-05-30 09:48:29 UTC,"Could you please collect the udevadm monitor logs, across the openibd restart, both with a previously known working release (e.g. xenial?!) and bionic?"
1774132,2018-05-30 11:38:34 UTC,"Thank you Dima,
Added requested files."
1774134,2018-07-23 20:36:29 UTC,"I am unable to reproduce this.  For python3, UTF-8 is the default, so non-ascii coding does not need to be declared.  Are you sure you were using a python3 version of pip?"
1774134,2019-09-04 09:50:38 UTC,"I've confirmed that's not needed for Python3, so it's almost certain setup.py was run with python2 or with a non-standard python3 configuration.  Closing as invalid since you can't install python3 modules with python2 and without a method to reproduce, there's nothing to be done."
1774136,2018-05-30 22:46:41 UTC,Looking at a couple of crash reports from different releases in the bucket we can see the DuplicateSignature is the same.
1774137,2019-10-30 15:45:40 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/571112"
1774137,2018-12-19 06:12:05 UTC,"Change abandoned by zhaodan7597 (<email address hidden>) on branch: master
Review: https://review.openstack.org/626095"
1774137,2019-10-30 15:47:46 UTC,"I abandoned the patch, there was a -1 from a core on it for a long time. It looks like addressing that comment would be trivial though if someone wants the patch restored so they can update it."
1774137,2018-12-19 02:07:20 UTC,"The not found error happening after the server building failed, not in deleteing.
After building failed, it will rollback resources, and destroy this instance. In nova/virt/vmwareapi/driver.py , code goes to destroy() -->_detach_instance_volumes()-->self._vmops.power_off(),  then the power_off() will raise a not found exception."
1774137,2018-12-19 06:05:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626095"
1774137,2018-10-10 19:52:40 UTC,Do you have a stacktrace of the failure? Is the not found error happening when deleting the server and the ComputeManager is trying to detach the volume here?
1774137,2018-08-07 06:40:44 UTC,"Change abandoned by zhaodan7597 (<email address hidden>) on branch: master
Review: https://review.openstack.org/571112"
1774138,2018-05-30 09:08:45 UTC,"The problem has been solved.
I have read information from Ubuntu forums and found that the problem was that ""sudo modprobe wl"" couldn't work because the Secure boot in BIOS.
After disabling the Secure Boot, I was able to run ""sudo modbprobe wl"" and wi-fi begun work.
In reality I run the command:
sudo apt-get --reinstall install bcmwl-kernel-source
but may be was not necessary, may be the problem was only the Secure Boot, but I don't understand so much these things.
Thanks for the help, Ubuntu. Without the information in internet, shouldn't be possible for me to eliminate Windows from my computers."
1774141,2018-09-18 21:58:58 UTC,Both packages install libcurl.so.4 (https://packages.ubuntu.com/bionic/amd64/libcurl3/filelist).
1774141,2018-10-10 17:30:21 UTC,"curl3 was a temporary hack in the archive to ""fix"" xmltooling.
curl3 has now been removed in cosmic, cause the newly upgraded xmltooling stack works with curl4 and the new openssl now."
1774141,2018-10-10 17:30:45 UTC,Marking cosmic task as fix-released; but keeping a bionic task open.
1774149,2019-06-07 14:20:57 UTC,"I have verified the second issue: the second call of function gives error ""Cannot access memory at address"".
I have tried it for various architectures. It is same for mips. But it works for aarch64."
1774149,2019-07-01 08:05:49 UTC,"It seems the issue is related to gdb code: set_gdbarch_call_dummy_location (gdbarch, ON_STACK);"
1774150,2018-07-27 09:34:40 UTC,I also confirm that the downgrade of the microcode helped. So the issue seems to be with the intel-microcode version 3.20180425.1~ubuntu0.14.04.1. Version 2.20140122.1 seems to work well. So the security-updates is the cause of all this trouble...
1774150,2018-07-07 12:33:59 UTC,"I can confirm that the downgrade helped. But then again - is anyone looking into a regression on the new version? I'd rather have the newest microcode, not the one from 2014."
1774150,2018-06-28 08:53:17 UTC,To pin intel-microcode version:
1774150,2018-06-28 08:49:41 UTC,Thank you. Now resume works fine. This helps:
1774150,2018-06-28 06:53:31 UTC,Thanks Bruno. I now hesitate to downgrade the microcode - since in there are some new CPU design flaw mitigations if I remember correctly.
1774150,2018-06-27 13:19:07 UTC,"Sorry to be late, but to downgrade intel-microcode I used synaptic, which in the packages menu has the option to force version of a package and then (after applying change) to hold it against updates. I chose the only other version listed (2.2014something) and it worked. Hope this helps."
1774150,2018-06-26 07:35:07 UTC,"The latest 13.0.151 kernel has the same issue, at least on this laptop.  This also means that whatever security updates are rolled into the mainline kernels are in effect inaccessible to laptop users affected by this issue. :-("
1774150,2018-11-04 04:46:47 UTC,I had to use kernel 3.13.0-157 to have suspend + newest microcode working together without problems. Newer kernel versions would freeze after suspend.
1774150,2018-06-14 18:09:03 UTC,"In case it helps (which I doubt, this would be too simple), I restored wakeup after suspend by downgrading intel-microcode 3.20180425.1 to previous version 2.20140122.1"
1774150,2018-06-25 06:45:29 UTC,"I've reinstall ubuntu from 14.04 to 14.04.5 and have same problem notebook (Asus N56VJ). After it suspend it unable to resume. Only black screen and no reaction caps lock. Previous version work fine with all kernels it updates.
Setting kernel in grub GRUB_DEFAULT=""Advanced options for Ubuntu>Ubuntu, with Linux 3.13.0-147-generic"" did not help. It hungs when resume."
1774150,2018-06-14 12:40:48 UTC,"Unable to give apport info, but wakeup on a console also hangs, writing more and more infrequently messages containing ""perf samples too long"" with numbers in the 1.5 million and ""lowering kernel.perf.event_max_sample_rate"" from 500,000 then 250,000 all the way down to 250."
1774150,2018-06-14 12:01:59 UTC,"Same issue now on a Dell desktop with Lubuntu, and kernel 3.13.0-151 didn't solve it, unfortunately."
1774150,2018-06-12 14:58:38 UTC,FYI: after installing the latest updates (containing kernel 3.13.0-151-generic) it all seems to work fine again for me.
1774150,2018-06-06 09:11:59 UTC,"This affects me too. No laptop here, but a Shuttle FS437. Used to work rock solid all the time."
1774150,2018-06-06 09:06:05 UTC,apport information
1774150,2018-06-06 09:06:03 UTC,apport information
1774150,2018-06-06 09:05:59 UTC,apport information
1774150,2018-06-06 09:05:56 UTC,apport information
1774150,2018-06-17 14:26:33 UTC,I am also affected on Thinkpad T440p on 3.13.0-151-generic. Couldn't submit via apport.
1774150,2018-06-06 09:05:55 UTC,apport information
1774150,2018-06-06 09:05:54 UTC,apport information
1774150,2018-06-06 09:05:53 UTC,apport information
1774150,2018-06-06 09:05:51 UTC,apport information
1774150,2018-06-06 09:05:49 UTC,apport information
1774150,2018-06-20 13:54:51 UTC,Will this bug get assigned? It totally breaks the daily workflow routine while on the move etc.
1774150,2018-06-06 09:05:46 UTC,apport information
1774150,2018-06-06 09:05:48 UTC,apport information
1774150,2018-06-06 09:05:39 UTC,apport information
1774150,2018-06-06 09:05:38 UTC,"ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  bav        2145 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a9a9ea54-d360-476c-b598-fd19723969cf
InstallationDate: Installed on 2014-07-24 (1412 days ago)
InstallationMedia: Xubuntu 14.04 LTS ""Trusty Tahr"" - Release amd64 (20140416.2)
MachineType: Shuttle Inc. DS437
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=8395af97-4ad8-4e0c-8fd4-ac1f64aaa902 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-149-generic N/A
 linux-backports-modules-3.13.0-149-generic  N/A
 linux-firmware                              1.127.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags:  trusty
Uname: Linux 3.13.0-149-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.01
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FS437
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd09/25/2013:svnShuttleInc.:pnDS437:pvrV1.0:rvnShuttleInc.:rnFS437:rvr1.0:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: DS437
dmi.product.version: V1.0
dmi.sys.vendor: Shuttle Inc."
1774150,2018-06-03 06:49:08 UTC,"Sorry, I can't generate the log files:
$ apport-collect 1774150
ERROR: Could not import module, is a package upgrade in progress?  Error: No module named PyKDE4.kdecore"
1774150,2018-06-01 07:26:19 UTC,New bugreport created: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774583
1774150,2018-06-01 07:18:04 UTC,Ah... while submitting the info I figured out it is apparently the idea to create a new bug and mark it as duplicate... Will do so.
1774150,2018-06-02 17:43:30 UTC,I also have the same issue with a Clevo laptop (W55xEU).
1774150,2018-05-30 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774150,2018-06-17 14:27:03 UTC,How would you do the downgrade of the intel-microcode?
1774150,2018-06-06 09:05:41 UTC,apport information
1774150,2018-06-06 09:05:42 UTC,apport information
1774150,2018-06-06 09:05:43 UTC,apport information
1774150,2018-06-06 09:05:45 UTC,apport information
1774150,2018-06-01 07:15:47 UTC,I have exactly the same issue with an MSI MS-1492 (GE40). I'll run the command and change the status.
1774160,2019-10-16 06:06:43 UTC,"This looks like the dpkg database got corrupted, could you please try:
sudo dpkg --purge snapd
and see if that helps?"
1774160,2019-12-16 04:17:18 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1774160,2019-12-16 04:17:20 UTC,[Expired for snapd because there has been no activity for 60 days.]
1774162,2018-05-30 09:59:58 UTC,Affects OpenStack releases <= Newton
1774165,2018-05-30 13:00:09 UTC,This change was made by a bot.
1774165,2018-05-30 12:53:10 UTC,"I noticed there were some earlier errors (something to do with dual Nvidia adapters and usb memory sticks) but running update-initramfs won't produce these errors, the log stays silent."
1774165,2018-05-30 12:29:34 UTC,"I notice there are some errors in the kernel log that you previously attached to this bug.
Could you run the update-initramfs command again, and attach /var/log/dmesg to this bug when it hangs?"
1774165,2018-05-30 12:49:20 UTC,This is almost certainly related to the hung task messages in dmesg. Changing this bug to be against the kernel.
1774165,2018-05-30 12:12:39 UTC,"Yes, it hangs, there's no errors on terminal:"
1774165,2018-05-30 11:08:48 UTC,Do you see any errors if you run 'sudo update-initramfs -u -v'? Does it hang?
1774177,2018-10-05 11:24:20 UTC,This happens to me 100% of the time now and is extremely annoying. Issues like this have made the 18.04 GNOME transition a clear step back in desktop polish.
1774177,2018-05-31 02:11:06 UTC,The lock screen and login screen graphics are provided by the the gnome-shell package.
1774177,2018-05-31 10:51:33 UTC,But what's strange is that the issue only happens momentarily and when returning from suspend. If I lock the screen it's correct and after a few moments after suspend it's correct again.
1774177,2018-06-01 02:01:10 UTC,Please see: https://gitlab.gnome.org/GNOME/gnome-shell/issues/142
1774177,2018-06-01 07:23:00 UTC,This is not the same bug. I can't reproduce it anymore since gdm is no longer slow on resume. But is it really Ubuntu process to have the user submit bug reports upstream?
1774177,2018-06-01 07:32:09 UTC,"Yes, upstream requires bug reports from someone who experiences the bug."
1774177,2018-06-02 09:35:59 UTC,Just had the same thing happen even with gdm not being slow. Flashes for less than a second and now my pointer is at 200% when over the top bar. Trying to take a screenshot resets it again so I can't show it.
1774177,2018-06-02 09:39:39 UTC,Upstream issue submitted:
1774177,2018-10-05 11:29:50 UTC,This bug doesn't exist on Wayland. It does seem like GNOME developers don't care about Xorg anymore and these kinds of bugs won't get fixed.
1774179,2018-09-10 19:11:57 UTC,@Jeff-  I don't think selection disambiguation affects this.  It's more of a single-click vs. double-click disambiguation.  But maybe I'm thinking about this too linearly and you've got a better work-around.
1774179,2018-09-10 19:25:30 UTC,"Without the selection disambiguation issue, double-click should always be an ""extension"" to single-click so that it's safe to go ahead and process the single-click.  (The platform will then deliver a double-cick event on the next click if it was in the double-click time period.)"
1774179,2018-09-10 18:04:01 UTC,"@Seth, I can't set it to Fix Committed because it's in Tom's GAL branch (which isn't yet on master).  Should I leave it for you to close when the time comes, or do you want me to re-assign it?"
1774179,2019-06-04 22:16:16 UTC,The modern toolset has different click handling so this issue no longer exists.
1774179,2018-12-11 19:27:36 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1774179,2018-09-10 18:02:33 UTC,"I implemented some heuristics for selection disambiguation.  Since schematics are meant to be human-readable, we don't have all the overlap and coverage issues that we did in Pcbnew."
1774179,2018-05-31 10:23:29 UTC,I've tested with release build and it looks to be the same speed as in debug.
1774179,2018-06-01 18:41:32 UTC,Do you or anybody reading this know if V6 changes to Eeschema will influence this? Will this functionality be reimplemented?
1774179,2018-06-01 19:26:38 UTC,The GAL changes to eeschema won't affect this.
1774179,2018-05-30 19:19:12 UTC,"Yes, I'll test release."
1774179,2018-05-30 17:01:50 UTC,Hi Janis-
1774179,2018-05-31 12:11:35 UTC,"One more thing I observe. In Eeschema if I click on component pin and get clarify selection dialog and click component from this dialog, Pcbnew highlights appropriate component instantly. This works for pads also. Only thing is that clarify select dialog shows after some delay ~0.5s for me. So It seems the delay is somehow tied to Eeschema."
1774179,2018-06-01 18:29:27 UTC,This is related to the disambiguation menu in eeschema.  We insert a pause between a click and the click action in order to allow for double-click handling before the disambiguation menu pops up.  Otherwise the first click shows the menu and then swallows the second click.
1774179,2018-05-31 11:09:58 UTC,"Interesting observation! Reverse operation, that is, click on component in Pcbnew and centering on it in Eeschema is very fast (instant)."
1774181,2018-05-30 13:00:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774181,2018-06-13 11:04:00 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1774181,2018-06-28 14:37:44 UTC,"For Trusty 3.13, add the following patches:
  * UBUNTU: SAUCE: filter: Use barrier_nospec() instead of osb()
  * UBUNTU: SAUCE: Rename osb() to barrier_nospec()
  * UBUNTU: SAUCE: Replace osb() calls with array_index_nospec()
  * nospec: Kill array_index_nospec_mask_check()
  * nospec: Move array_index_nospec() parameter checking into separate macro
  * nospec: Allow index argument to have const-qualified type
  * x86/kvm: Update spectre-v1 mitigation
  * x86/spectre: Report get_user mitigation for spectre_v1
  * nl80211: Sanitize array index in parse_txq_params
  * vfs, fdtable: Prevent bounds-check bypass via speculative execution
  * x86/syscall: Sanitize syscall table de-references under speculation
  * x86/get_user: Use pointer masking to limit speculation
  * x86: Introduce barrier_nospec
  * x86: Implement array_index_mask_nospec
  * array_index_nospec: Sanitize speculative array de-references
  * Documentation: Document array_index_nospec"
1774181,2018-07-02 08:29:08 UTC,This bug was fixed in the package linux - 4.4.0-130.156
1774181,2018-08-02 16:03:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1774181,2018-08-23 21:59:21 UTC,This bug was fixed in the package linux - 3.13.0-157.207
1774188,2019-07-21 21:25:52 UTC,"It happens to me also. Fresh install of Lubuntu 18.04, fully updated, on an HP Pavilion g6. Whenever the screen is locked (either manually choosing to lock it, or automatically after X amount of time without using it), it will take many seconds just to simply draw the password dialog. But if I switch to the terminal with Ctrl+Alt+F1, then back to the X-Window ""terminal"", it will draw a text telling me that it will take a few seconds to show me the password dialog ??!! That message then disappears into a black screen, and more than twenty seconds later, finally the password dialog shows up. The laptop was doing nothing, completely idle... this shouldn't happen."
1774188,2019-07-21 21:29:32 UTC,"Sorry, I think this isn't the proper place for me to report this... because in my case it's not happening with gdm, but with lightdm."
1774188,2019-09-24 04:17:22 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1774188,2019-09-24 04:17:24 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1774188,2019-09-24 04:17:26 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1774188,2019-09-24 04:17:27 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1774188,2019-10-28 09:01:14 UTC,"Per comments #32 and #33, this bug is closed because it required specific debugging to be done by the original reporter (which may yield different results for each person). Since no answer was received to comment #19 after 60 days this bug closed automatically."
1774188,2019-10-03 01:38:28 UTC,This bug closed automatically due to no response from the original reporter.
1774188,2019-10-10 05:36:19 UTC,Done: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847566
1774188,2019-10-26 19:12:28 UTC,"I see this, too, on two different machines (one at home, one at work), both desktops with two monitors. Though for me the delay is usually longer then five seconds. The duration of the delay seems to increase with how long the machine's been up since its last reboot. This was not present when I first installed 18.04 a year ago, but seems to have arisen with some subsequent update."
1774188,2019-10-28 08:31:32 UTC,"I just upgraded to Ubuntu 19.10 but nothing changed.
I see the status of the bug is 'expired', is anyone working on this?
Thanks"
1774188,2019-11-04 00:42:17 UTC,"I recently submitted a bug about this topic for Ubuntu 19.10:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757"
1774188,2019-10-02 11:52:44 UTC,"I seem to have the same problem in 19.04. Also it seems to take longer, the longer I'm logged in. Logging out and back in makes it relatively fast again."
1774188,2019-05-29 19:40:11 UTC,"I have this same problem on 18.04.  It's very noticeable that when my network has no DNS working, screen unlock takes a long time - as much as a minute or two."
1774188,2019-07-25 13:28:21 UTC,"I have seen this on bionic, then on cosmic and now on disco. Type password and it takes 5 to 6 seconds to give you the desktop."
1774188,2019-05-13 01:50:19 UTC,"Daniele,"
1774188,2019-05-13 01:51:33 UTC,"Götz Waschk,"
1774188,2018-06-04 11:58:46 UTC,"I guess the app indicator icons are the menus in the top-right corner. I have these:
Accessibility
Input Language
Network
Speaker
Battery
The downward triangle that opens the menu"
1774188,2018-06-05 01:42:21 UTC,"It sounds like most of the issue is confined to Xorg sessions, so reassigning as appropriate."
1774188,2018-06-07 09:35:29 UTC,"I think it got slower over time even under the Wayland session. I have clocked the latest unlock time at 2.5 seconds, still rather slow."
1774188,2018-08-24 08:47:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774188,2018-11-01 10:06:37 UTC,I occasionally see this on two separate 18.04 installations using Xorg sessions.  The time to unlock varies from a couple of seconds to several minutes.  Everything other than unlocking the screen feels to work at a normal speed.
1774188,2018-12-07 09:46:23 UTC,/metoo
1774188,2018-06-04 02:19:49 UTC,"Thanks. It looks like there is maybe a logical reconnect of the display to the X server at the start around 14:32:29, and that could be triggering a lot of things."
1774188,2019-01-30 16:08:07 UTC,i'm seeing the same thing.  nothing serious but it is annoying that after authenticating you have to wait ~5 secs before getting your desktop.
1774188,2019-01-31 02:24:31 UTC,"Maybe turn on debugging in /etc/gdm3/custom.conf, reboot, and then look at the more detailed log from 'journalctl -b0' to see what was happening during that time."
1774188,2019-02-03 20:14:32 UTC,I have attached the journal with gdm3 debugging enabled. It starts after waking up the notebook. The screen unlocking was really slow.
1774188,2019-05-03 07:51:45 UTC,FYI: I feel it's (somehow) fixed (for me). I haven't seen this behavior since some days.
1774188,2018-05-31 02:14:12 UTC,Can you please attach output from 'journalctl -b' covering a time period when the bug occurred?
1774188,2019-05-03 08:08:16 UTC,The log in comment #17 shows the delays are/were specifically here:
1774188,2019-01-11 00:27:29 UTC,/metoo
1774188,2019-05-12 09:00:29 UTC,/metoo
1774191,2018-06-05 09:16:48 UTC,"3.13.0-151.201~precise1 - generic
Regression test CMPL, RTB."
1774191,2018-06-11 16:07:19 UTC,The package has been published and the bug is being set to Fix Released
1774203,2020-04-09 16:33:21 UTC,It is not exactly equivalent to:
1774203,2020-04-09 16:30:40 UTC,"FYI, my workaround is the following:"
1774203,2018-06-08 18:29:04 UTC,"I have a customer who is migrating their cloud from Xenial/Mitaka to Bionic/Queens, and has begun the exercise of migrating their network topologies to netplan, but found that it does not support creating dummy interfaces (or, apparently support for OVS at this point[0])."
1774203,2020-01-21 01:11:45 UTC,"Indeed, it would be handy to have support of dummy interfaces."
1774205,2018-05-30 15:39:59 UTC,Looks like the problem code was removed in Pike: https://review.openstack.org/#/c/449640/
1774205,2019-08-30 11:27:56 UTC,"Reviewed:  https://review.opendev.org/571265
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a638685c469da18dcf8f4bc4763763d90e50be17
Submitter: Zuul
Branch:    master"
1774205,2019-04-30 14:28:10 UTC,Please don't mark a bug report as a suspected security vulnerability unless you also include some explanation as to why you think it represents one. I'm switching the status from public security back to a normal public bug report again for now.
1774205,2018-09-26 10:43:50 UTC,This issue was fixed in the openstack/nova 15.1.4 release.
1774205,2018-09-24 14:47:36 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1774205,2018-09-24 14:47:00 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1774205,2018-07-30 16:08:38 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1774205,2018-07-04 16:55:15 UTC,"Reviewed:  https://review.openstack.org/577929
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=09e678ee142ea297640e44ce9af630402871c38a
Submitter: Zuul
Branch:    stable/ocata"
1774205,2018-06-29 14:05:27 UTC,"Reviewed:  https://review.openstack.org/577918
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1162902280d06eb6201738ef54ff8300f974b374
Submitter: Zuul
Branch:    stable/queens"
1774205,2018-06-25 20:50:19 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/577929"
1774205,2018-06-25 20:42:46 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/577926"
1774205,2018-06-25 20:16:44 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/577918"
1774205,2018-05-30 17:43:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/571265"
1774205,2018-05-30 16:13:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571245"
1774205,2018-07-04 14:54:23 UTC,"Reviewed:  https://review.openstack.org/577926
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ce7ad878093e5730b8dcec5ca717b831db8965eb
Submitter: Zuul
Branch:    stable/pike"
1774205,2018-06-12 17:07:30 UTC,"Reviewed:  https://review.openstack.org/571245
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8c216608194c89d281e8d2b66abd1e50e2405b01
Submitter: Zuul
Branch:    master"
1774207,2018-05-30 15:26:06 UTC,"I fear, there is currently no developer available to implement new features. A workaround is to use the drop down menu which is hidden behind the little arrow next to the ""capture window"" button. It shows a list of available windows, the only downside is that no preview is visible."
1774212,2020-10-03 11:59:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774213,2018-10-25 16:58:26 UTC,This also happens on 18.04 hosts. It makes troubleshooting PTP issues very difficult if the statistics log is not working.
1774214,2018-05-31 16:22:22 UTC,apport information
1774214,2018-05-31 16:22:24 UTC,apport information
1774214,2018-05-31 02:15:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1774215,2018-05-31 02:15:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1774215,2018-05-31 15:04:19 UTC,apport information
1774215,2018-05-31 15:04:21 UTC,apport information
1774215,2018-06-04 07:37:47 UTC,What did you upgrade from? I think the banner would be set in /etc/gdm3/greeter.dconf-defaults these days
1774215,2018-06-04 11:47:21 UTC,"We installed 18.04 on our test machines, after erasing 16.04.
We tested setting the security banner on 05-17-2018 by using dconf key files, and that worked (we had tested changing the greeter.dconf-defaults as well but that didn’t change anything).
After applying the security updates for 18.04, the changes disappeared. We recompiled all of our custom dconf settings and the only one that applied properly was the user local desktop background, even though (gsettings get) command shows that the key is set for banner-message-enable to true and banner-message-text to our desired text."
1774224,2018-10-16 20:40:45 UTC,pour les fonds de balise file utilisant la coloration syntaxique peut-être modifier le background dans pre.code.file
1774224,2018-06-25 07:15:03 UTC,"Le 24/06/2018 à 21:40, YoBoY a écrit :

> Bonjour,
>
> En fait c'est le comportement normal de dokuwiki d'avoir la même
> couleur. La zone est la même, la seule différence est pour mieux montrer
> que l'un représente du code et l'autre est plus dédiée à la mise à
> disposition d'un contenu fichier qu'on peut copier coller ou
> télécharger. Je sais pas si je suis clair. Bref les deux sont
> interchangeables et ça n'apporte pas grand chose de les différencier à
> mon humble avis.


Je ne suis pas de cet avis, une page où on peut directement faire la
différence entre un ""terminal"" et un ""fichier"" c'est vachement plus
clair. Je ne comprends pas très bien l'interêt d'avoir des balises code
et file si le résultat est le même, autant mettre une balise ""texte
encadré"" :). C'est dommage que ça soit le comportement normal de
dokuwiki, perso j'espère qu'on adaptera la couleur comme dans l'ancien
thème.

>
> Pour info le thème standard de dokuwiki a un fond #fbfaf9 et nous c'est
> #f5f5f5 actuellement, très peu de différence.
>
> Si il y a des soucis de lisibilité ou de contraste sur certains
> éléments, merci d'être plus précis, c'est peut être un soucis à faire
> remonter chez dokuwiki également.


Oui pour la lisibilité qui ne permet pas de distinguer rapidement entre
le code et le texte comme expliqué plus haut. C'est vrai que ça vaudrait
la peine de faire remonter à dokiwiki.

>
"
1774224,2018-05-31 18:36:37 UTC,Moi aussi ça me va.
1774224,2018-05-31 18:36:33 UTC,En fait si on utilise les balises avec la syntaxe (exemple <file bash> ) la coloration peut poser souci avec ce niveau de gris et rendre certains caractères invisible.
1774224,2018-05-31 17:18:48 UTC,Pour les balises code je viens de tester en ajoutant dans ubuntufr.less
1774224,2018-06-24 20:40:04 UTC,"Bonjour,"
1774225,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1774225,2018-08-07 14:02:11 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1774225,2018-07-18 15:02:26 UTC,I'll see what is involved to backport to Xenial/4.4
1774225,2018-07-12 15:34:36 UTC,"Well, it could be a workaround but it would be great to have it in the 4.4 if it's not too complicated for you. What do you think?"
1774225,2018-07-05 17:51:36 UTC,Xenial appears to have some prereq commits necessary and requires backporting of commits.  Is it possible to use the HWE kernel with Xenial instead of backporting the commits to 4.4?
1774225,2018-06-08 17:39:43 UTC,It looks like mainline commit b2d3bcfa26a7a is also needed.
1774225,2018-06-11 12:28:53 UTC,"It works for me, thanks!"
1774225,2018-06-05 12:57:21 UTC,"The test fails because the attribute IFLA_CARRIER_UP_COUNT and IFLA_CARRIER_DOWN_COUNT are not declared in this kernel. In this kernel, IFLA_NEW_IFINDEX has the numeric value of IFLA_CARRIER_UP_COUNT in an upstream kernel (if I patch iproute2 to use IFLA_CARRIER_UP_COUNT instead of IFLA_NEW_IFINDEX, I can get the new ifindex).
iproute2 (like a lot of others  tools) has a local copy of linux uapi headers, thus the numeric value of netlink attributes must be the same than upstream."
1774225,2018-06-04 19:25:49 UTC,I built one more test kernel using the Bionic master-next repository.  I confirmed the test kernel has the following two commits:
1774225,2018-06-04 08:37:50 UTC,"Hi Joseph,"
1774225,2018-06-01 21:01:10 UTC,Commit 6621dd29eb9b is already in Bionic. Are this commits only needed in Bionic?
1774225,2018-05-30 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774225,2018-06-22 17:51:03 UTC,"Bionic SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093495.html"
1774228,2020-07-08 21:22:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774228,2020-07-08 21:23:06 UTC,"kdemultimedia depends on kde-config-cddb, which is the package needed to get k3b's cddb settings dialog working."
1774237,2018-05-30 18:04:00 UTC,"There is a hold note field in Evergreen, but it is very difficult to find. You need to get to the hold details page to add a note, which requires multiple steps. There are options to make the hold public (meaning, the public can see the note in their My Account holds list) and to add the note to a holds slip."
1774238,2019-03-28 21:13:01 UTC,"Reviewed:  https://review.openstack.org/648245
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=6afc1130fd753306d64745c9bee7712182b273d3
Submitter: Zuul
Branch:    feature/losf"
1774238,2019-04-29 05:38:10 UTC,"Reviewed:  https://review.opendev.org/655630
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=d391957fd70a02866615c9c5edc070dbde2b23ea
Submitter: Zuul
Branch:    feature/losf"
1774238,2019-04-25 08:23:05 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/655630"
1774238,2019-04-13 02:47:47 UTC,"Reviewed:  https://review.openstack.org/571907
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=e5ff405ec967bfe19b3eaeaac5b5a32c95218f9d
Submitter: Zuul
Branch:    master"
1774238,2019-04-05 03:41:50 UTC,"Reviewed:  https://review.openstack.org/571906
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=e5e22ebeba2140b1da2e9d52d6b8ecd92bc75c88
Submitter: Zuul
Branch:    master"
1774238,2019-03-27 21:11:19 UTC,"Fix proposed to branch: feature/losf
Review: https://review.openstack.org/648245"
1774238,2018-05-31 18:52:52 UTC,Running functests with tim's configs resulted in logs like this for me:
1774238,2018-07-02 02:52:39 UTC,"Reviewed:  https://review.openstack.org/571048
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=9d0162a793115d55dd11c40b619657db41fa9968
Submitter: Zuul
Branch:    master"
1774238,2018-06-30 04:56:19 UTC,"Reviewed:  https://review.openstack.org/571904
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=7cec5a8fdb8ea376aa3f495181f0f295c1c84571
Submitter: Zuul
Branch:    master"
1774238,2018-06-01 23:57:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571908"
1774238,2018-06-01 23:57:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571907"
1774238,2018-06-01 23:57:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/571906"
1774238,2019-03-21 16:41:49 UTC,"Reviewed:  https://review.openstack.org/571905
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=fa678949ae310aa0499938fef788ec04409625d9
Submitter: Zuul
Branch:    master"
1774238,2018-06-01 23:57:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/571904"
1774240,2018-05-30 20:01:19 UTC,"I think we're really talking about the schema hierarchy, not the file hierarchy (which is already shown), right?"
1774240,2018-05-30 20:17:49 UTC,"Yes, @Jjeyjey. Show the schematic files on the KiCad initial windows as a tree that represent the hierarchical use of this files in Eeschema."
1774240,2018-05-30 21:04:34 UTC,This will not be trivial because the schematic will have to be opened in order to create the schematic file hierarchy.  Putting the schematic files in the project file is a non-starter because it would make schematics non-portable.
1774240,2018-05-31 00:17:57 UTC,"Yes, the little the I studied about the file formats used I agree that the files have to be opened and read (even before start Eeschema). Because this I list the https://bugs.launchpad.net/kicad/+bug/1728260 here."
1774241,2018-12-18 11:41:00 UTC,You might want to detail a usecase here. (Why would somebody be motivated to implement this if nobody will find a use for it)
1774241,2018-12-18 12:23:41 UTC,"My point of view is that is better to graphic annotation, splitting parts of the board.
In this example mine (attached) I used in a ""didactic"" board to be clear the separation between ground planes."
1774241,2019-05-07 21:10:50 UTC,+1 with https://bugs.launchpad.net/kicad/+bug/1828086
1774244,2018-08-18 15:10:11 UTC,I filed an upstream bug report at https://bugs.documentfoundation.org/show_bug.cgi?id=119346
1774244,2019-10-07 15:40:00 UTC,Still reproducible on:
1774244,2019-09-11 04:38:13 UTC,"Dear vaaydayaasra,"
1774244,2018-09-10 10:49:26 UTC,Repro.
1774244,2018-08-18 15:06:26 UTC,"Created attachment 144269
ODT document used to create the screenshot and the PDF"
1774244,2018-08-18 15:05:51 UTC,"Created attachment 144268
Screenshot of Writer document view"
1774244,2018-08-18 15:04:48 UTC,"Created attachment 144267
PDF with displaced Arabic text"
1774244,2018-08-18 15:02:42 UTC,"Description:
In this example, I created a document with a few Arabic-script characters (U+08A2, U+08A3 & U+08A4), which were quite recently added to Unicode for various Arabic-script African languages such as Fulfulde. The font I had used in the rest of the document was DejaVu Sans, so I used that font setting even for these characters. In reality, these glyphs are not found in DejaVu Sans but had to be substituted from another font, in my case Scheherazade (from fonts-sil-scheherazade, available through packages.sil.org). After rotating the letters by 90 degrees, everything looked fine on the screen but when I created a PDF, everything was displaced about one inch upwards and one inch to the left. See the attached screenshot, where everything looks fine, and the PDF where all the letters are displaced."
1774244,2018-08-16 16:48:04 UTC,"Sorry for the lack of feedback until now, Miikka.
I can reliably reproduce the issue with libreoffice 6.0.3.2 on Ubuntu 18.04 and libreoffice 6.1.0.3 installed as a snap."
1774244,2018-06-01 19:43:28 UTC,"Sorry, for some reason, my browser seems to have submitted the same bug report twice, as #1774243 and #1774244. All the relevant information, including all the attachments are posted in this report, so I marked the other report as a duplicate."
1774244,2018-05-30 18:07:49 UTC,This is the ODT document used to create both the PDF and the screenshot.
1774244,2018-05-30 18:07:19 UTC,"Here's a screenshot where everything looks fine, unlike the PDF."
1774249,2020-03-04 16:56:29 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/711276"
1774249,2020-03-04 16:57:17 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/711277"
1774249,2020-03-04 16:57:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/711278"
1774249,2020-03-04 16:58:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/711279"
1774249,2020-03-06 03:30:16 UTC,"Reviewed:  https://review.opendev.org/711276
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=73d9b6e5f622dc645ac6ad322c836ffbe4045072
Submitter: Zuul
Branch:    stable/train"
1774249,2020-03-11 05:07:33 UTC,"Reviewed:  https://review.opendev.org/711279
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=05f4bf0e6738093d79c6a8ffb9ca3ccb189c6658
Submitter: Zuul
Branch:    stable/queens"
1774249,2020-03-10 12:42:01 UTC,"Reviewed:  https://review.opendev.org/711278
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1962633328dc7227dd040c1cf3a9cbe97b36ea37
Submitter: Zuul
Branch:    stable/rocky"
1774249,2019-11-14 20:34:42 UTC,"Reviewed:  https://review.opendev.org/685391
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6198f317be549e6d2bd324a48f226b379556e945
Submitter: Zuul
Branch:    master"
1774249,2020-07-21 13:01:41 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/742181"
1774249,2020-07-23 10:48:00 UTC,"Reviewed:  https://review.opendev.org/742181
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9202b2e6cfeb5dd67b54d7eaa6187725a34aeae6
Submitter: Zuul
Branch:    stable/pike"
1774249,2020-03-09 21:19:25 UTC,"Reviewed:  https://review.opendev.org/711277
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4700b3658e5983a731d0da259365317e230c4a52
Submitter: Zuul
Branch:    stable/stein"
1774249,2019-09-27 15:25:06 UTC,This is not fixed. We've just had a report where we appear to be hitting the race reported in review here:
1774249,2019-06-18 03:40:53 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1774249,2019-07-10 21:39:27 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1774249,2019-03-07 22:31:21 UTC,We also hit it in the gate:
1774249,2019-03-08 00:59:10 UTC,Patch is here: https://review.openstack.org/#/c/571410/
1774249,2019-05-21 10:56:19 UTC,"Reviewed:  https://review.opendev.org/571410
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=966192704c20d1b4e9faf384c8dafac8ea6e06ea
Submitter: Zuul
Branch:    master"
1774249,2019-09-27 09:03:46 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1774249,2019-05-21 12:08:09 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/660362"
1774249,2019-05-21 12:07:53 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660361"
1774249,2019-05-23 04:28:46 UTC,"Reviewed:  https://review.opendev.org/660361
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f1280ab849d20819791f7c4030f570a917d3e91d
Submitter: Zuul
Branch:    stable/stein"
1774249,2019-06-06 06:23:57 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1774249,2019-06-11 23:17:15 UTC,"Reviewed:  https://review.opendev.org/660362
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fd5c45473823105d8572d7940980163c6f09169c
Submitter: Zuul
Branch:    stable/rocky"
1774249,2019-02-27 07:56:45 UTC,"Any news regarding this issue? I've read the whole history here and on RedHat's Bugzilla and I assume that this issue is not fixed yet, am I correct? We are experiencing a quite significant level of log records regarding this issue. Please update info here, thank you."
1774249,2019-06-28 22:00:15 UTC,"Reviewed:  https://review.opendev.org/660363
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d3bdeb26155c2d3b53850b790d3800a2dd78cada
Submitter: Zuul
Branch:    stable/queens"
1774249,2019-05-21 12:08:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/660363"
1774249,2019-03-07 22:29:41 UTC,Note https://review.openstack.org/#/c/553067/ is related for a race during server delete.
1774252,2018-05-31 08:49:25 UTC,"if fix previous bug, this should be avoidable ?
 otherwise, delete a migration record should update compude node and without compute node this should raise some exception, so it's a work as designed behaviour?"
1774252,2018-06-04 09:21:49 UTC,"jichenjc,"
1774252,2018-06-05 08:31:07 UTC,you mentioned
1774253,2020-01-23 22:00:02 UTC,See also:
1774257,2019-01-18 07:19:49 UTC,increasing timeout would be an obvious workaround.
1774257,2019-03-22 23:23:22 UTC,What timeout you are talking about here to increase.
1774257,2018-05-30 20:06:06 UTC,"2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_messaging/rpc/server.py"", line 160, in _process_incoming
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     res = self.dispatcher.dispatch(message)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py"", line 213, in dispatch
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     return self._do_dispatch(endpoint, method, ctxt, args)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py"", line 183, in _do_dispatch
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     result = func(ctxt, **new_args)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/osprofiler/profiler.py"", line 153, in wrapper
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     return f(*args, **kwargs)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_log/helpers.py"", line 67, in wrapper
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     return method(*args, **kwargs)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/l2pop/rpc_manager/l2population_rpc.py"", line 41, in add_fdb_entries
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     self.fdb_add(context, self._unmarshall_fdb_entries(fdb_entries))
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/osprofiler/profiler.py"", line 153, in wrapper
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     return f(*args, **kwargs)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py"", line 524, in fdb_add
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     agent_ports, self._tunnel_port_lookup)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/osprofiler/profiler.py"", line 153, in wrapper
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     return f(*args, **kwargs)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_log/helpers.py"", line 67, in wrapper
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     return method(*args, **kwargs)
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server   File ""/var/lib/kolla/venv/local/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/l2pop/rpc_manager/l2population_rpc.py"", line 254, in fdb_add_tun
2018-05-30 20:05:32.387 7 ERROR oslo_messaging.rpc.server     self.add_fdb_flow(br, port, remote_ip, lvm, ofport)
2..."
1774257,2018-05-30 21:13:04 UTC,2018-05-30 21:11:09.347 7 WARNING neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-5696c85c-046a-4cfe-8ce8-f16100944081 - - - - -] OVS is dead. OVSNeutronAgent will keep running and checking OVS status periodically.: TimeoutException: Commands [<ovsdbapp.schema.open_vswitch.commands.ListPortsCommand object at 0x7fbb77c94e10>] exceeded timeout 10 seconds
1774265,2018-06-07 09:47:13 UTC,According to JournalErrors.txt you're using the nouveau X driver. So reassigning...
1774266,2019-09-19 11:58:31 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1774268,2020-04-01 13:32:17 UTC,"(All of that is to say that I Have Thoughts about ways to improve default hold notification settings, including actually making it a default setting vs a convention that's C&P'd wherever needed, but doing that stuff later doesn't mean this can't be fixed today.)"
1774268,2020-04-01 13:30:51 UTC,"On second thought, this works fine as-is; there's no need to over-complicate it. (My alternative thought of just setting the value when missing probably isn't ideal either...) so I've pushed this and condensed the two options to be a little bit tidier to rel_3_3 -> master."
1774268,2020-03-31 17:08:52 UTC,"Looking into this today things have been complicated by bug 1570072 which allows staff or patrons to update existing holds when these values change. for <3.5 it can be as simple as changing the condition in Suzanne's branch from ""if (!notify)"" to ""if (!notify && !(notify === ''))"" to combine her and Jeff's approaches, but for 3.5+ it needs to do a little more than just nope out. I'll see if I can throw some tuits at it."
1774268,2020-02-19 16:01:36 UTC,"I'm removing the needsrepatch tag and leaving the pullrequest on for Suzanne's branch in comment 10. Suzanne's branch lacks a signoff, so I've added mine:"
1774268,2020-02-20 21:30:59 UTC,Thanks for the patch Jeff! I tested it and it works great. I specifically tested the following cases for the effect of the user setting opac.hold_notify on the patron registration screen:
1774268,2020-02-19 20:40:30 UTC,"In my testing of Suzanne's branch, if the user setting is """" (empty string), the hold notify checkboxes will be checked in the patron editor, which is not what we want."
1774268,2020-02-19 20:26:58 UTC,Adding back the needsrepatch tag as this is now not working for the case when the user has selected no notifications. Will have an updated branch shortly.
1774268,2019-10-05 03:45:23 UTC,"For me, this patch did treat the empty string """" as a go ahead to check email and phone in patron registration, in today's master."
1774268,2018-12-19 18:27:45 UTC,"I have tested this patch on a 3.2 system, and I'm seeing a couple issues with it."
1774268,2019-08-06 18:39:34 UTC,"Regarding the most recent patch - it is perfectly valid for a patron to not want to get notifications. I haven't had a chance to test this, but from the code it looks like that preference would be ignored."
1774268,2019-08-06 15:36:17 UTC,On patron edit screen set the email and phone notification to true when patron doesn't have any preferences. This mimics the behavior in the xul client.
1774268,2019-06-25 13:55:39 UTC,Setting importance to High as we are seeing that increasing numbers of patrons are not being notified of holds due to the change in behavior in the web client.
1774268,2019-03-08 19:26:25 UTC,Removed signedoff tag since two testers have found issues.
1774268,2019-01-04 20:33:09 UTC,I tested on 3.1.7.
1774268,2018-12-11 14:26:04 UTC,Patched tested and signed off on here: user/rogan/lp1774268signoff
1774268,2018-07-26 19:11:47 UTC,* specify a default hold notify of ':phone:email' (maybe someday make this a configurable setting)
1774268,2018-06-13 15:55:10 UTC,"users with empty strings for opac.hold_notify in actor.usr_setting seem to be problematic. when attempting to place a hold for one such user, i got javascript errors in the browser:"
1774268,2019-08-06 21:07:37 UTC,"If a patron's notification preferences have been explicitly set to not receive notifications, either by staff or by the patron, there will be an entry in actor.usr_setting for that patron with the value """" for the opac.hold_notify preference."
1774268,2018-06-11 17:47:23 UTC,I've noticed also that patrons edited or created in the web staff client get entries in opac.hold_notify of an empty string if these are not set. I do not recall seeing that with the XUL client.
1774272,2020-08-14 20:05:04 UTC,It should be noted that there are two menu items for Barcode in the column picker.  Both go to the Item Barocde.  How easy might it be for someone to redirect one to the Patron barcode?
1774272,2019-07-19 20:36:33 UTC,NOTE - when adding the patron barcode as a display column -> The patron barcode should be a link to the patron record
1774273,2018-05-30 21:17:32 UTC,syslog
1774278,2018-05-30 21:46:28 UTC,boot repair ubuntu pastebin report - http://paste.ubuntu.com/p/vNvBBQHN9b/
1774278,2018-06-07 20:36:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774279,2018-07-11 13:53:08 UTC,"Ok thanks, we will try this workaround in one of our deployment to see if we can reproduce the behavior."
1774279,2018-07-20 09:28:23 UTC,"Change abandoned by Seyeong Kim (<email address hidden>) on branch: master
Review: https://review.openstack.org/581392
Reason: Need discussion about fundamental behaviour."
1774279,2018-07-11 13:53:46 UTC,"Raising Ubuntu task; it would be nice if we could tell the ceph-mon cluster how many OSD's there *will* be, rather than it defaulting to '3' if there are no OSD's currently checked in."
1774279,2018-07-11 13:49:13 UTC,This works around the issue; we need a more complete solution but this at least gets automated deployments with vault based dmcrypt keys running again.
1774279,2018-07-11 13:28:10 UTC,Feature: https://ceph.com/community/new-luminous-pg-overdose-protection/
1774279,2018-07-11 13:37:52 UTC,One possible workaround is to set mon_max_pg_per_osd to something stupidly high; this will allow the pool to be created sans any OSD's actually being in.  The OSD pool config will still be right sized based on the expected OSD count (if used).
1774279,2018-07-11 13:24:05 UTC,Reproduced:
1774279,2018-07-11 11:04:20 UTC,I'm still digging into the bug - my original 'can't create pools without OSD's' appears to be untrue to trying to figure out why the broker request actually fails.
1774279,2018-07-02 15:01:51 UTC,"I think this is less about gnocchi, and more about ceph-mon (which does the actual pool creation).  In later ceph releases, pool creation fails if no OSD's are present at the point in time the pool is created.  Its possible to work around this to some extent by setting the expected-osd-count configuration option on ceph-mon, but even this has some chance of racing."
1774279,2018-07-11 13:46:45 UTC,For example:
1774282,2018-06-01 18:52:34 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1774282,2018-06-01 19:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774282,2018-06-02 19:53:53 UTC,I tried running the command the bot asked as well but it complained I was on a mainline kernel even though I am on the upstream one
1774282,2018-06-02 20:12:29 UTC,apport information
1774282,2018-06-02 20:12:31 UTC,apport information
1774282,2018-08-05 22:58:32 UTC,I am also experiencing a similar problem. Though when I first installed ubuntu studio 16.04 it was working fine. Only in the last few days does blueman not recognize that I have a bluetooth adapter.
1774285,2020-02-23 16:13:35 UTC,"Thanks for this, Josh and Jessica.  It works well, and I pushed it to master and rel_3_4."
1774285,2020-02-19 21:35:03 UTC,"I have tested this code and consent to signing off with my name, Jessica Woolford, and email, <email address hidden>"
1774285,2018-05-30 23:07:43 UTC,Screenshot of the two screens.
1774285,2019-08-12 17:03:41 UTC,Still an issue in 3.3
1774285,2018-05-31 13:04:53 UTC,"This is an interesting case, since the Holds Pull List and Holds Shelf are part of the same AngularJS ""app"" (or ""module""). The Holds template sets ctx.page_title to ""Holds Shelf"", but then the URL determines which controller and interface are used."
1774285,2018-05-31 00:55:29 UTC,"I noticed this also, but hadn't made it over to Launchpad yet. Marking Confirmed."
1774285,2019-12-10 19:30:31 UTC,"Remington, thanks for the notes.  Here is a branch that implements changing the Pull List title.  I added a egCore.strings value for 'Pull List' so a properly translated string will get added."
1774290,2018-06-03 03:20:38 UTC,Apparently the only time this does not want to close with my superkey. Is when I have my numlock enabled.
1774290,2018-06-17 00:35:36 UTC,Upstream bug: https://github.com/solus-project/brisk-menu/issues/70
1774290,2018-09-28 21:02:49 UTC,This bug was fixed in the package brisk-menu - 0.5.0-8ubuntu1
1774294,2018-05-31 22:50:45 UTC,According to my system it seems to think it is still at the same brightness level. When it simply isn't. I then have to adjust the level and put it back where it was before to get it back to the way I had before suspending my laptop.
1774294,2018-06-04 13:54:11 UTC,"I seemed to have remedied the issue. By modifying line 11 of /etc/default/grub to read. 'GRUB_CMDLINE_LINUX_DEFAULT=""quiet splash acpi_backlight=vendor""'"
1774301,2018-10-06 21:33:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774302,2019-04-17 03:21:52 UTC,"Can confirm that using spooldefaults.bin, libspoolb.so and libspoolc.so from http://ftp.debian.org/debian/pool/main/g/gridengine/gridengine-client_8.1.9+dfsg-9_amd64.deb does workaround the segfault issue in gridengine-master 8.1.9+dfsg-7build1 on Ubuntu 18.04 Bionic."
1774302,2019-08-21 13:47:45 UTC,"I have been grappling with this issue myself over the last couple of weeks and can confirm using the spooldefaults.bin, libspooldb.so and libspoolc.so from the Debian gridengine-client APT package, linked by christophprobst resolved the issue."
1774302,2018-12-17 12:48:09 UTC,It looks like this bug has been present since Ubuntu 16.10: see bug #1633251
1774302,2018-08-10 06:50:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774302,2019-02-08 15:30:29 UTC,"I was able to cobble together a fix for this,  hopefully someone could use this information to create a more refined solution."
1774305,2020-05-27 17:52:27 UTC,Continues to be an issue in 3.5
1774307,2018-05-31 02:17:52 UTC,Please double-check the bug occurs in Xorg sessions. Bug 1733033 says for another user the problem is specific to Wayland.
1774307,2018-05-31 03:04:29 UTC,Restarted computer. Logged in ubuntu session. No ability to drag and drop in Nautilus.
1774307,2018-05-31 03:16:49 UTC,"When the bug happens, please run 'xrandr' in a terminal and send us the output to verify the session type."
1774307,2018-05-31 03:27:34 UTC,"Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1920x1080     60.10*+  60.01    59.97    59.96    59.93    40.06
   1680x1050     59.95    59.88
   1600x1024     60.17
   1400x1050     59.98
   1600x900      59.99    59.94    59.95    59.82
   1280x1024     60.02
   1440x900      59.89
   1400x900      59.96    59.88
   1280x960      60.00
   1440x810      60.00    59.97
   1368x768      59.88    59.85
   1360x768      59.80    59.96
   1280x800      59.99    59.97    59.81    59.91
   1152x864      60.00
   1280x720      60.00    59.99    59.86    59.74
   1024x768      60.04    60.00
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   800x512       60.17
   700x525       59.98
   800x450       59.95    59.82
   640x512       60.02
   720x450       59.89
   700x450       59.96    59.88
   640x480       60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   680x384       59.80    59.96
   640x400       59.88    59.98
   576x432       60.06
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)"
1774313,2019-10-06 08:42:25 UTC,"May be it will be nice to start memcached container on swift-proxy-server, when swift-proxy-server is not on controller?"
1774313,2019-10-07 08:24:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686975"
1774313,2019-10-07 08:25:23 UTC,"@Lev, memcached doesn't need to be colocated with swift-proxy. We just need to fix the connection string to reference the memcached group."
1774313,2019-10-07 18:37:47 UTC,"Reviewed:  https://review.opendev.org/686975
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=3488479d06bc9fc39058532d29229b67f25d4ec0
Submitter: Zuul
Branch:    master"
1774313,2019-10-08 08:31:09 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/687236"
1774313,2019-10-08 08:31:22 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/687237"
1774313,2019-10-11 16:08:16 UTC,"Reviewed:  https://review.opendev.org/687237
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=78b7086605c7f25cc3ca8e14d04836e46d2f0f76
Submitter: Zuul
Branch:    stable/rocky"
1774313,2019-10-11 16:08:05 UTC,"Reviewed:  https://review.opendev.org/687238
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=422682006cb98adf1028ed8f29429f0b647960c7
Submitter: Zuul
Branch:    stable/queens"
1774313,2019-10-11 16:11:13 UTC,"Reviewed:  https://review.opendev.org/687236
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=8db18241cb2830d1f158a301f1a0de8b23d42c37
Submitter: Zuul
Branch:    stable/stein"
1774313,2019-10-28 14:46:30 UTC,This issue was fixed in the openstack/kolla-ansible 6.2.3 release.
1774313,2019-11-11 15:39:17 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1774313,2020-01-30 10:22:32 UTC,This issue was fixed in the openstack/kolla-ansible 7.2.0 release.
1774313,2020-01-30 10:25:11 UTC,This issue was fixed in the openstack/kolla-ansible 8.1.0 release.
1774313,2019-10-08 08:31:36 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/687238"
1774318,2019-08-04 01:49:52 UTC,"Reviewed:  https://reviews.mahara.org/10093
Committed: https://git.mahara.org/mahara/mahara/commit/f335828e4beab6b68e7d460fe0994f5eb4104199
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1774318,2019-01-30 02:16:08 UTC,We shifted from bbcode to tinymce in version 15.04 but we left the old bbcode functions around due to upgrade path so we could covert the saved content.
1774318,2019-06-18 02:32:20 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10093"
1774330,2019-11-28 00:28:07 UTC,Current help text looks like:
1774330,2019-11-28 00:30:40 UTC,Here's my cleaned up version:
1774330,2019-11-30 00:12:13 UTC,This is reviewed and landed to master.
1774342,2018-05-31 07:11:55 UTC,package isc-dhcp-server version 4.3.5-3ubuntu7
1774352,2018-06-20 07:16:41 UTC,"In my opinion, it's a valid case. Change zvmguestconfigure to deal with such case."
1774359,2020-08-20 11:51:00 UTC,"Had the same problem, the reason was that prime-select was set to intel instead of nvidia."
1774359,2020-05-20 03:52:32 UTC,Similar activity on 440 version of drivers.
1774359,2020-04-23 12:27:32 UTC,Just upgraded from Ubuntu 16 to 18.04.
1774359,2018-12-07 12:36:49 UTC,"Same problem here, with Ubuntu 18.04, Nvidia drivers 410.
After commenting the following lines:"
1774359,2018-10-21 20:24:07 UTC,"So i actually found one in /lib/modprobe.d/blacklist-nvidia.conf
Blacklisting it actually solved the bug, but my ubuntu is crashing after that, but that's another story."
1774359,2018-10-21 19:53:37 UTC,"I see only few solutions to this bug:
 - Somehow find file which has 'alias nvidia off', because I can't find any
 - Debug this kernel module (which is actually a very long process)"
1774359,2018-10-18 13:30:04 UTC,"I can confirm that I also have that bug with nvidia 410 and bumblebee.
Bumblebee tries to modprobe nvidia and fails with same error"
1774359,2018-10-15 08:28:01 UTC,"Same problem with nvidia 410.
Reinstall not working."
1774359,2018-10-14 16:24:12 UTC,Same problem with nvidia 410
1774359,2018-10-14 12:43:10 UTC,Fixed it by commenting lines in 159-161 in /usr/bin/prime-select:
1774359,2018-10-14 12:35:27 UTC,"Ubuntu 18.04 on Asus Zenbook Pro UX901V, GeForce GTX 960M, both nvidia 390 and 396."
1774359,2018-09-13 01:51:09 UTC,"Ubuntu 18.04 On Precision 5530 Quadro P1000
Confirm the issue with nvidai 396."
1774359,2018-09-02 11:44:03 UTC,"Kubuntu 18.04 on a T430 with an nvidia 5400M.
Same issue with nvidia 390 and 396.
Not using Bumblebee."
1774359,2018-08-19 21:28:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774359,2018-05-31 08:47:19 UTC,Similar to https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1438106 but I'm not using bumblebee
1774359,2018-10-15 08:31:08 UTC,"Comment lines at /etc/modprobe.d/nvidia-...conf
not working
~$ sudo modprobe nvidia
same error:
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown parameter (see dmesg)"
1774387,2019-09-17 13:02:39 UTC,https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=f835ec7b5fd099a108d1d3deada19936d96b8037
1774387,2019-09-17 11:57:48 UTC,"Fix sent to kernel-team mailing-list:
https://lists.ubuntu.com/archives/kernel-team/2019-September/103750.html"
1774387,2019-09-17 11:49:13 UTC,"The issue tested by LTP testcase inotify07 has been fixed by commit:
       31747eda41ef ""ovl: hash directory inodes for fsnotify"""
1774387,2018-06-08 07:03:44 UTC,Affecting Xenial as well.
1774387,2019-08-29 14:48:08 UTC,"we see this on linux-aws for xenial , 4.4.0-1092.103"
1774387,2019-08-05 09:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774387,2018-06-05 10:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774387,2019-09-16 12:52:13 UTC,"This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix."
1774394,2019-09-17 12:55:20 UTC,Setting priority to low as Trusty is now ESM.
1774394,2018-06-01 07:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774394,2018-06-21 04:42:31 UTC,This test has passed on X-LTS in this cycle.
1774394,2018-06-01 06:59:43 UTC,Could be found on X kernel as well.
1774394,2019-09-17 12:39:48 UTC,This testcase is now passing on 4.4 kernels.
1774399,2018-06-30 16:40:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774400,2018-05-31 12:28:59 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1774400,2018-05-31 21:49:28 UTC,"I can't locate source of the problem. All I know is it is related to the
two Ubuntu versions, mentioned in the report and something they have in
common. I hope very much someone can find the time to at least look into it
and can confirm the problem."
1774406,2018-05-31 12:30:05 UTC,This change was made by a bot.
1774412,2020-11-21 21:37:33 UTC,"Should be fixed by this patch:
https://<email address hidden>/"
1774412,2021-01-21 18:16:45 UTC,https://git.qemu.org/?p=qemu.git;a=commitdiff;h=fa647905e6baae9510e7d
1774417,2018-05-31 14:06:51 UTC,"Well, on Ubuntu we do not have nss-nis package."
1774417,2018-06-09 20:16:24 UTC,"Hello everybody,"
1774417,2018-08-14 15:05:33 UTC,This appears to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1745664
1774417,2018-08-15 01:25:24 UTC,If anyone thinks it is appropriate then you can mark this as a duplicate of bug 1745664. But there's not enough information here for me to tell right now.
1774417,2019-11-14 20:25:49 UTC,Does this workaround help here as well?
1774418,2019-06-03 12:43:13 UTC,"Thanks for that, Ahmed. Can you submit the patch to gerrit, please? There are some links to instructions for getting set up in the CONTRIBUTING.rst file in the base directory of the repo, and one of us can help you get set up if you run into trouble."
1774418,2019-06-03 06:10:17 UTC,Here is the patch for fixing this bug cmd2>=0.9.1
1774418,2018-06-15 09:40:07 UTC,"Hello Doug,
I tried your patch with cmd2==0.9.1 and it works! Thanks a lot for your commitment"
1774418,2018-07-10 12:48:36 UTC,The version 0.9.1 and 0.9.2 is still failing for me.
1774418,2018-05-31 14:29:31 UTC,"beapi --debug
(beapi) help
EXCEPTION of type 'AttributeError' occurred with message: ''Statement' object has no attribute 'parsed''
To enable full traceback, run the following command:  'set debug true'
(beapi)"
1774418,2018-05-31 14:15:59 UTC,I'm not able to reproduce this. Having a more detailed traceback and a reference to your project's code would help.
1774418,2018-05-31 14:09:04 UTC,Can you run the command using the --debug flag and post the traceback please?
1774418,2018-05-31 14:05:03 UTC,I think it's time to just rip cmd2 out of cliff.
1774418,2018-05-31 16:43:33 UTC,"OK, I think I've reproduced it. Can you try patching your code with https://review.openstack.org/571524 to see if it works?"
1774419,2018-05-31 13:53:01 UTC,"The changelog for this package states that it the easy_install scripts were removed, as of:"
1774419,2018-07-04 20:59:27 UTC,"I am affected by this as well. Using EasyBuild which relies on easy_install command during its installation problem. In 17.10 the cmd is still there. Worked around it by copying the easy_install cmd from 17.10 (its actually just a short python script) and putting it into the path. This works for me, but it is still weird that it is missing. Also installed setuptools just via pip. Same thing. Did they make some changes to setuptools?"
1774419,2018-07-04 21:00:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774419,2018-10-14 14:37:30 UTC,"Guys we need this as well, please update"
1774419,2018-11-09 20:15:22 UTC,"Having `easy_install` available (or something similar) is likely an ongoing need for at least one reason. If a user wants their system to stay on the latest/upstream version of pip, one sensible way of doing this is to install the `python-setuptools` package and use `easy_install` to install `pip` straight from PyPi, and then from that point forward use `pip install -U pip` to keep it up to date."
1774419,2018-11-21 18:38:56 UTC,This affects me as well; there are a number of build tools and test environments I maintain and/or use which assume the availability of easy_install if python-setuptools is installed.
1774419,2018-11-23 07:06:15 UTC,"That has been reported to Debian as well, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896652"
1774419,2019-04-16 22:53:21 UTC,Work-around
1774421,2018-06-30 16:41:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774425,2018-06-20 14:25:43 UTC,"https://lkml.org/lkml/2017/12/7/201 tries to raise the limit, but according to
https://bugs.freedesktop.org/show_bug.cgi?id=102508#c11 it does not work."
1774425,2018-05-31 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774425,2018-06-01 19:03:17 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1774425,2018-06-20 13:26:16 UTC,"See also similar bugs
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178"
1774428,2020-11-09 08:52:57 UTC,"4.13 EOL, closing this bug.
Please file a new bug with ""ubuntu-bug linux"" if you're still seeing this issue.
Thanks"
1774429,2018-10-03 19:26:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774429,2018-10-08 23:54:47 UTC,"Any update on this one? I'm also looking for a pgpool2 installation from apt in 18.04. Same concerns as OP: need security updates, and no usage of Java in the same server."
1774429,2018-11-29 03:39:35 UTC,We also needed pgpool2 in bionic so I decided to try to compile it from the 18.10 source package found here:
1774429,2019-12-23 11:11:28 UTC,"copied from publishinghistory:
https://launchpad.net/ubuntu/+source/pgpool2/+publishinghistory"
1774430,2018-05-31 16:32:58 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1774430,2018-06-01 01:22:47 UTC,"So far as I could try, only mspaint and NewView Graphics File Viewer (http://www.newviewgraphics.com/viewer/viewer.htm ) --- it is free but no source is open --, can see this file in color.
LibreOffice (6.0.4) and EMF explorer (http://frazmitic.free.fr/emfexplorer/overview.htm ) shows it in black and white."
1774430,2018-06-11 14:51:30 UTC,"I checked how this file is displayed with MS Office for Mac.
The results are the same (not shown correctly, whole DNA is black)."
1774431,2018-06-05 07:03:38 UTC,"Cosmic upload is currently tested, also prepared the SRU Template for the latter upload to Bionic."
1774431,2018-06-05 09:51:48 UTC,This bug was fixed in the package quota - 4.04-2ubuntu1
1774431,2018-06-07 18:21:05 UTC,"Hello Robert, or anyone else affected,"
1774431,2018-06-08 07:17:19 UTC,"Hi Łukasz,"
1774431,2018-06-08 07:21:02 UTC,"Forgot the package version: 4.04-2ubuntu0.1, had to downgrade from the PPA's version."
1774431,2018-06-04 12:13:57 UTC,I have opened a merge proposal to get a 2nd opinion avoiding mistakes and missing use cases affected in a bad way. Once that is acked I can upload to Cosmic.
1774431,2018-06-08 08:00:25 UTC,Thank you.
1774431,2018-06-18 08:52:51 UTC,"Thanks for all the testing! There's one systemd autopkgtest failure happening for this upload in -proposed though. Might not be related as those tend to be flaky, but I'd like someone taking a look at that before we proceed. I re-ran it some days ago but it again failed."
1774431,2018-06-18 10:33:15 UTC,"Hi Lukasz,
it is a flaky test in this case.
On one hand there is no quota usage in this test (boot-smoke failed last).
Further different subtests fail on different retries."
1774431,2018-06-20 06:10:41 UTC,This bug was fixed in the package quota - 4.04-2ubuntu0.1
1774431,2018-06-20 06:10:48 UTC,"The verification of the Stable Release Update for quota has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1774431,2018-06-08 07:36:08 UTC,"The issue LGTM, now only waiting the usual extra days if someone spots something in proposed that might be missed."
1774431,2018-06-04 10:26:38 UTC,Looks good. Thanks.
1774431,2018-06-20 06:10:39 UTC,Looks like the last autopkgtest run passed. Release ENGAGE!
1774431,2018-06-04 07:03:46 UTC,"Confirmed, thanks Robert.
Yet with RPCRQUOTADOPTS=""-p 599"" in /etc/default/quota the issue can be reproduced."
1774431,2018-05-08 12:03:24 UTC,Description of problem:
1774431,2018-06-04 10:01:39 UTC,"Hi,
I have built a fixed version in ppa [1].
This works for me a dn I have not spotted any issues yet, but since you seem to be a more heavey user of this I wanted to ask if you could check from the ppa as well."
1774431,2018-05-09 10:24:12 UTC,This happens inside tirpc library:
1774431,2018-05-09 18:38:01 UTC,"(In reply to Petr Pisar from comment #2)

>
> Either it's a bug in libtirpc-1.0.3-1.rc1.fc28.x86_64 that wants to accept
> raw sockets, or rpc.rquotad setups the tirpc service inappropriately. Maybe
> libtirpc maintainer will know more. rpc.rquotad code is in rquota_svc.c


Well it is spinning in rendezvous_request due to this loop:"
1774431,2018-05-10 19:07:26 UTC,"In Comment 3 I was mistaken with that again loop since
the errno being returned from accept is EINVAL not
EINTR."
1774431,2018-05-12 19:24:20 UTC,"Created attachment 1435510
Patch that fixes the problem"
1774431,2018-05-14 09:00:10 UTC,"I can conform that this solves the issue, at least here
(no ipv6 in use)."
1774431,2018-05-09 09:43:34 UTC,Thanks for the report. I can reproduce it.
1774431,2018-05-22 12:13:23 UTC,The patch looks good and I confirm it fixes this issue. The RPC calls still work over both IPv4 and IPv6. I sent the patch to <https://sourceforge.net/p/linuxquota/feature-requests/16/>
1774431,2018-05-22 13:01:26 UTC,quota-4.04-6.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-4adeec12ed
1774431,2018-05-22 19:39:02 UTC,"quota-4.04-6.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-4adeec12ed"
1774431,2018-05-30 14:09:04 UTC,"quota-4.04-6.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report."
1774431,2018-06-01 05:56:45 UTC,"I liked the report especially with the patch already linked and all that.
But to reproduce on Debian/Ubuntu one needs to:"
1774431,2018-06-01 11:59:10 UTC,"This behaviour is only observed when rpc.rquotad is told to run on a specific port with e.g. RPCRQUOTADOPTS=""-p 599"" in /etc/default/quota."
1774431,2018-05-22 08:56:36 UTC,The git tree is at <git://git.code.sf.net/p/linuxquota/code>. Fedora 28 rebased quota to 4.04 that migrated from NIS RPC to tirpc. Hence Fedora 28 is the first one that uses tirpc and supports IPv6.
1774443,2018-06-21 16:51:53 UTC,apport information
1774443,2018-06-21 16:51:54 UTC,apport information
1774443,2018-06-21 16:51:55 UTC,apport information
1774443,2018-06-21 16:51:57 UTC,apport information
1774443,2019-02-10 20:04:50 UTC,"Yes, the issue still persists in 4.19.20 and 5.0-rc5"
1774443,2018-06-21 16:52:00 UTC,apport information
1774443,2019-02-08 15:47:59 UTC,Does this still happen on latest mainline kernel?
1774443,2019-02-21 16:08:26 UTC,Please attach output of `rfkill list`.
1774443,2018-06-21 16:51:52 UTC,apport information
1774443,2018-06-21 16:51:59 UTC,apport information
1774443,2018-06-21 16:51:50 UTC,apport information
1774443,2018-06-21 16:51:31 UTC,apport information
1774443,2018-06-21 16:51:48 UTC,apport information
1774443,2018-06-21 16:51:49 UTC,apport information
1774443,2018-06-21 16:51:33 UTC,apport information
1774443,2018-06-21 16:51:35 UTC,apport information
1774443,2018-06-21 16:51:36 UTC,apport information
1774443,2018-06-21 16:51:37 UTC,apport information
1774443,2018-06-16 17:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774443,2018-06-21 16:51:39 UTC,apport information
1774443,2018-06-21 16:51:42 UTC,apport information
1774443,2018-06-21 16:51:44 UTC,apport information
1774443,2018-06-21 16:51:45 UTC,apport information
1774443,2018-06-21 16:51:47 UTC,apport information
1774443,2018-06-21 16:51:38 UTC,apport information
1774447,2018-06-01 20:34:57 UTC,"Well, after uninstalling xserver-xorg-input-synaptics it seems to be working fine. At least short testing looks promising. Bud bad is two-finger scrolling stopped working. I can only switch to edge scrolling, which works, but when two-finger scrolling is enabled, it does not work."
1774447,2018-06-01 07:00:28 UTC,Mouse clicks works properly - no missed clicks.
1774447,2018-06-01 02:07:35 UTC,"Does the problem only occur with the touchpad, and never with a mouse?"
1774447,2018-06-01 07:15:15 UTC,OK. You appear to be using the synaptics touchpad driver (which is expected in Xorg sessions after an upgrade).
1774449,2021-02-17 17:08:05 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1774459,2020-01-31 12:01:17 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705200"
1774459,2019-09-30 19:04:58 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/685779"
1774459,2019-10-10 18:25:06 UTC,"Reviewed:  https://review.opendev.org/685779
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=09c4e0e970b02ed992aab762505d17f1decca551
Submitter: Zuul
Branch:    stable/stein"
1774459,2019-12-04 08:43:26 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/616272
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1774459,2019-12-07 16:25:57 UTC,"Reviewed:  https://review.opendev.org/669938
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ea85e39660abaa224c159c42214fdb7042302bea
Submitter: Zuul
Branch:    master"
1774459,2019-12-31 11:35:34 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/700805"
1774459,2020-01-03 04:12:28 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/700988"
1774459,2021-01-04 13:51:58 UTC,"A related patch from Liu:
https://review.opendev.org/c/openstack/neutron/+/768052"
1774459,2020-02-10 10:46:43 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/705200"
1774459,2020-02-10 10:46:51 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/705201"
1774459,2020-02-25 16:39:58 UTC,"Change abandoned by Brian Haley (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/700805
Reason: Abandoning based on my last comment, since this would require additional code that isn't present in this branch."
1774459,2020-04-26 03:26:22 UTC,stay tuned
1774459,2020-09-10 07:23:03 UTC,Is someone still working on this bug? Looks to me like it doesn't has any progress since February.
1774459,2020-09-10 19:26:38 UTC,"Hi Jorg, Yes, I recently revived patch https://review.opendev.org/#/c/601336/ and I'm working on it currently."
1774459,2019-07-09 20:14:12 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/669938"
1774459,2020-01-31 12:04:40 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/705201"
1774459,2019-06-13 09:57:38 UTC,"Reviewed:  https://review.opendev.org/651905
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=52b537ca22b2d7d81a84b2f75de577d8dffee94c
Submitter: Zuul
Branch:    master"
1774459,2020-02-05 18:39:06 UTC,"Reviewed:  https://review.opendev.org/700988
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dc8c1deeee7ad46958a771567516e91ca52cd156
Submitter: Zuul
Branch:    stable/train"
1774459,2019-04-11 18:48:50 UTC,"Change abandoned by Swaminathan Vasudevan (<email address hidden>) on branch: master
Review: https://review.openstack.org/628027
Reason: Abandoning this patch since I have a better one to address this issue.
https://review.openstack.org/#/c/651905/"
1774459,2019-05-15 14:20:10 UTC,Also related to this bug: https://review.opendev.org/#/c/616272/ and https://review.opendev.org/#/c/601336/
1774459,2018-06-08 14:53:24 UTC,SWe are talking about this piece of code: https://github.com/openstack/neutron/blob/master/neutron/agent/linux/ip_monitor.py#L59
1774459,2018-06-14 14:47:20 UTC,"Hi Brian, yes I can take a look at the keepalived_state_change code and see how it works and how it can be used in our case.
But not sure if it can be as such used in our case, since the keepalived in our case is running in side the VM and not in the Namespace."
1774459,2018-07-05 15:44:28 UTC,"I don't think that we can use the IP-Monitor for our purpose.
We should definitely come up with a GARP-sniff tool similar to IP-Monitor and then use if for our purpose.
If we think that the performance will be an issue. We should probably come up with a dedicated node, that is doing the sniff and reporting it back to Neutron Server.
That way neutron server can then do an rpc update to all agents to add a permanent entry."
1774459,2018-08-07 21:45:42 UTC,"Is there any other way to collect the same information that would be collected by garp-sniffing?
What info needs to be propagated?"
1774459,2018-08-07 21:50:15 UTC,"Also on the performance aspect of sniffing garp packets, the reason a system would suffer performance is if it is processing ALL packets, what if we can filter to only garp packets *before* the monitoring tool gets them.
Its basically the same thing as what a host must do. All hosts have to listen to garp packets, so I am not sure you would get any more traffic than what you would get already.
its just instead of dropping the packets on the floor, you pull them into user space for processing.
Perhaps the term ""sniffing"" is what we need to avoid.
Again we could put a flow rule that pulls specifically garp packets from an ip address/mac combo and give those packets to a process in user space."
1774459,2018-08-14 21:08:49 UTC,One other simple solution would be to forward a packet ( GARP ) for the MAC's that are configured for Allowed_address_pair to the Ryu controller. The controller can process the packet under the 'packet_in_handler' and then try to create an ARP response entry in the ARP Responder for the MAC and IP.
1774459,2018-06-08 14:48:52 UTC,"I'm not a big fan of a process running that is snooping on traffic, it's most likely going to cause a performance issue."
1774459,2018-08-23 06:04:15 UTC,"Rossella thanks for your feedback. The issue is we are seeing the garp updates the arp entry.But when there is ping to that IP, the router tries to re-arp to confirm the IP and that is were it fails."
1774459,2018-08-17 15:28:12 UTC,Swami I am not sure this last proposal is better in terms of performance than sniffing garp. I don't have all the details and I am new to this problem but have you ever tried instead of setting the NUD to reachable to change the timeout so that arp entries become stale pretty quickly and the GARP can update them? A combination between frequent GARP and entries that get stale quickly might fix this.
1774459,2018-09-06 14:48:14 UTC,Adding a rule similar to ARP Responder may not be possible. So the best bet is to forward the GARP packets to an output port (tap port created for this purpose). Then a separate process can listen on the tap port and then parse the packet and provide info to the Network node ( neutron-server) to update the ARP entry on all nodes.
1774459,2018-09-10 17:07:02 UTC,"If we feel that this process running in the compute node will reduce the performance, then what we should do is probably have a new agent type running this process and then communicating to the Network node. That way we don't need to run this process on all compute nodes."
1774459,2018-09-10 17:55:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/601336"
1774459,2018-09-12 16:58:19 UTC,"Adding a rule dynamically to the ARP responder is only possible if we can forward the GARP packet to the openflow controller where the openflow controller can process the IN_PACKETS and then make a decision on creating a flow in the ARP responder table.
Is this possible in neutron openflow native drivers today. Any l2 openflow experts can comment on it.
This would be the simplest approach otherwise, we need to forward it to the user space where we process the packet and then send it to Neutron server to take necessary action."
1774459,2018-09-12 18:03:49 UTC,"After talking with Miguel Ajo and Daniel Alvarez, plan is to intecept GARP packets and forward to local controller for processing
Swami had a WIP patch that inserted an OF rule to intercept, would need update to send to controller
https://review.openstack.org/#/c/601336/
For ryu look here:
 https://ryu.readthedocs.io/en/latest/ofproto_v1_0_ref.html#packet-in-message
https://ryu.readthedocs.io/en/latest/writing_ryu_app.html?highlight=packet%20in
ovn-controller handles incoming packets (packet-in) as controller here:
https://github.com/openvswitch/ovs/blob/769e6223daf3d6e51963dc3ee938a01fdc71a0d0/ovn/controller/pinctrl.c#L1221
https://github.com/openvswitch/ovs/blob/769e6223daf3d6e51963dc3ee938a01fdc71a0d0/ovn/controller/pinctrl.c#L1121
ODL is tracking this on https://jira.opendaylight.org/browse/NETVIRT-1402
Basically flows will be programmed dynamically when a GARP is recognized by the controller."
1774459,2018-11-07 18:41:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/616272"
1774459,2019-01-02 19:16:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/628027"
1774459,2019-04-11 18:48:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/651905"
1774459,2018-08-23 06:06:28 UTC,Not sure if we can do something similar to ARP Responder to add a dynamic ARP Responder rule to send an ARP reply for the GARP'd MAC.
1774463,2019-12-04 08:38:22 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/662111
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1774463,2019-12-04 08:38:11 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1774463,2018-09-07 14:21:42 UTC,This RFE was discussed during today's Neutron Drivers meeting and is approved. Please move ahead with implementation
1774463,2019-05-30 00:02:03 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/662111"
1774463,2018-09-07 04:58:53 UTC,"Hi Brian,
Yes, I mentioned running 'radvd' in the fipnamespace.
Yes it is assumed, this use case is with subnet pools/address scopes, so that the traffic is directed towards the compute node fast-exit-path and also yes the l3-agent correctly configures rules."
1774463,2018-08-31 14:25:15 UTC,"Hi Swami,"
1774463,2018-07-06 14:40:30 UTC,it sounds reasonable to me.
1774463,2018-07-05 15:21:03 UTC,"Ref: https://review.openstack.org/#/c/143917/
Ref: https://review.openstack.org/#/c/138588/"
1774463,2018-09-07 11:56:27 UTC,This makes sense to me.
1774465,2018-11-21 15:55:50 UTC,Dupe of https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1786710?
1774476,2018-05-31 18:17:57 UTC,"This would likely also happen if the user just opted to not connect to any network and proceed to the next page where they are prompted if they want to ""Download updates while installing Ubuntu"""
1774484,2018-06-11 12:51:52 UTC,Why do you say it has something to do with livepatch? This is the error from the log:
1774484,2018-06-11 18:54:18 UTC,You are correct. I solved the issue (by installing the ubuntu version)  awhile back. I forgot to update the bug report.
1774484,2018-06-11 18:56:21 UTC,You are correct. I solved the problem awhile back (by using the ubuntu version). I forgot to update the bug report.
1774484,2018-10-16 01:54:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774489,2019-03-14 13:41:49 UTC,I've fixed the documents in the snapcraft forum
1774491,2018-05-31 20:14:56 UTC,"This very much looks like a bug int Aptdaemon's PK compatibility layer to me. At this point, it likely makes no sense to fix this issue, since that code has been dropped after the Xenial release."
1774491,2018-06-01 13:59:02 UTC,Any idea of the implications of doing this?
1774494,2018-05-31 20:15:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/571565"
1774494,2018-06-19 07:48:35 UTC,"Change abandoned by Wojciech Dec (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/571565
Reason: Not needed"
1774494,2021-02-19 15:52:12 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1774498,2018-08-01 13:49:49 UTC,Here's the upstream issue:
1774498,2018-08-01 13:45:52 UTC,">As part of that animation, windows from the old workspace fly out and windows from the new workspace fly in.
"
1774498,2018-08-01 08:56:11 UTC,I don't think it is really a bug.
1774498,2018-08-01 07:46:37 UTC,I've disabled all extensions and recorded a video. Here's the output of lspci:
1774498,2018-08-01 08:18:05 UTC,Bizarrely I /think/ that might be correct behaviour.
1774498,2018-08-01 04:17:19 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1774498,2018-06-01 07:24:59 UTC,This is really easy to reproduce. Just arrange your screens so your external screen is above the internal one instead of to the left or right. Now when you switch virtual desktops the contents are moved through the external screen.
1774498,2018-08-01 08:31:43 UTC,"Of course ""Workspaces span displays"" fixes it as everything moves at once. Putting the external screen on the left or right also fixes it. But that just shows how the animation is broken. When the screen is on top and doesn't span displays there's no reason for the contents of the internal screen that are switching virtual desktop to fly through the external screen. That's just a bug."
1774498,2018-06-01 02:11:49 UTC,1. Please try removing all your extensions and see if the problem goes away:
1774499,2018-07-03 15:07:28 UTC,Here's the Traceback:
1774502,2020-05-22 22:57:12 UTC,I do agree with cologic's rationale on this :)
1774502,2020-05-17 15:00:42 UTC,"<eMTee> I've checked klondike's geoip lib and as I precieve it does the lookups staight from the data file. That doesn't sound too efficient. Also I'm not sure the whole thing is thread-safe at all. So maybe it's Maxmind's lib is the only option...
<cologic> I agree with you (or, well, your conclusion -- whatever your reasoning was) that klondike's design, while it is as he says, a ""This is a purposefully slow implementation for memory constrained environments"", achieves that fseek()ing and similar around the file in a thread-unsafe way, to avoid mmap() and other access methods. That the mmdb_t data structure itself can only meaningfully be used by one thread at a time, so the choice ends up being multiply loading in the files -- which, actually, sort of works with his design, since it is so low-memory-usage -- or keep fewer mmdb_t objects around than threads, and mux access to them somehow (say, mutexes: ""TODO: mutex handling"").
<cologic> It's a reasonable tradeoff for a different environment than DC++ lives in these days.
<cologic> He jumps through endless hoops just not to keep anything he doesn't need in memory, IMO to the code/design's detriment in this context.
<cologic> The whole dbip-country-lite-2020-05.mmdb is about 5MB, which seems completely acceptable to mmap() or just load completely into memory and not deal with all those seeks, mutex questions, etc.
<cologic> Just to take the most obvious option (the same overall approach, just, all in memory). Other options exist too.
<cologic> The completely unoptimized representation (text-based, no fancy reused DAG-like substructures, etc) from their CSV file is still only 17MB. So not saying this is a great option, but just a dumb CSV parser on that could work too.
<cologic> line by line of 2.17.115.0,2.17.115.255,GB -- trivial.
<cologic> The other concern I have with the style of klondike's code is that it's full of basically untrusted-data-driven pointer-chasing (via seeks at the moment, but still) which as klondike acknowledges can result in exponential blowup.
<cologic> It's not his fault -- he did what one could with the format -- but from working on other code dealing with a conceptually similar file format, I'm not a fan of it.
<cologic> There's something to be said for the relative simplicit/verifiability/fewer-weird-failure-modes of a constrained CSV parser which builds an in-memory representation with some reasonable std::foo data structure.
<cologic> But I suspect that if one fuzzed most of these geoip format parsers, the results would be dire"
1774502,2020-05-17 08:14:19 UTC,"https://www.db-ip.com/db/lite.php has direct downloads which apparently are in the same format as GeoIP. AirDC++ uses this parsed with the free GeoLite 2 MaxMind lib.
The data content of the free version is pretty sparse but it looks as though any other richer dataset from any provider is not free anymore.
The lib's licence is still incompatible with GPLv2"
1774502,2020-01-20 19:16:48 UTC,It seems that GeoIP is not free any more..
1774502,2019-02-25 22:35:16 UTC,"Hi eMtee,"
1774502,2019-02-21 19:58:54 UTC,In theory there's even a patch available for this problem (not sure why it isn't included here) but so far as I know currently a license incompatibility issue prevents the addition of GeoLite 2 libraries to DC++.
1774502,2019-02-21 19:48:59 UTC,r now it doesnt show anything at all. Time for GeoLite 2?
1774502,2018-10-01 17:30:39 UTC,Probably a side effect of this change that DC++ is always showing Australia as the country for every IP in the TransferView for some time.
1774502,2019-02-21 21:01:03 UTC,how do I find out more about the patch?
1774502,2018-06-01 23:06:58 UTC,"GeoLite 2 still has the info we use from GeoLite 1 databases, especially city-level geoloc, IPv6 support, region names..."
1774505,2018-06-01 01:49:08 UTC,I feel gnome-shell's behaviour makes more sense.
1774505,2018-06-01 07:31:05 UTC,Submitted here:
1774529,2020-12-16 21:49:29 UTC,"I can confirm the issue still exists at v2.7.3
Same behaviour as Vladimir Grevtsev (vlgrevtsev) wrote on 2020-09-18"
1774529,2020-09-18 09:50:41 UTC,"The same, but via UI raises an error (see attachment)."
1774529,2020-09-18 09:49:37 UTC,Reproduced on latest 2.8.2 (8577-g.a3e674063-0ubuntu1~18.04.1) but only via UI - domains/records created with CLI are deleted ok:
1774529,2019-05-05 09:59:22 UTC,"by the way, this also happened in MAAS 2.5.0"
1774529,2020-03-31 09:10:01 UTC,I'm not able to reproduce this as per the step in comment #4 with MAAS 2.7.0. Can you confirm that this is still and issue with 2.7.0 and attach the logs?
1774529,2019-05-05 09:58:17 UTC,"Hi Andres,"
1774529,2018-10-13 04:18:08 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1774529,2018-08-13 19:36:45 UTC,"Hi James,"
1774529,2020-05-31 04:17:21 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1774539,2018-06-01 15:26:52 UTC,"Possibly, `lint` should check on this of course."
1774539,2018-05-31 23:44:56 UTC,"I'm doing a no-push reimport of ntp off my importer-fix-tests branch. I suspect in that case, the upload tag above will end up not being integrated into the import tags. Will report back once I get results."
1774539,2018-06-01 02:39:51 UTC,Confirmed:
1774539,2018-06-01 04:27:47 UTC,"Can we check that on ""git push"" via hook and/or ""git tag --upload"" to warn
that this tag will not be usable?"
1774540,2018-07-13 16:34:50 UTC,"This is related to bug 1750884.
In netplan/systemd-networkd there is no such thing as ""global"" dns.  The decision was made that although users configured dns globally for the vast majority of the last 30 years, we were not going to support that behavior any more in netplan or systemd-networkd."
1774540,2018-07-16 16:09:10 UTC,"@Ryan,"
1774540,2018-07-16 14:37:29 UTC,"The searchpath is copied.  In netplan , the config namespace is:"
1774542,2018-07-27 01:23:48 UTC,"It was suggested on the Teamspeak forums that this is related to the PulseAudio ""role cork"" function... a ""feature"" related to stream tagging. This may fix. I've been unable to test it as of yet.
/etc/pulse/default.pa"
1774551,2018-06-01 02:18:32 UTC,"A user that analyzed it, and also post records from his log file is at https://bbs.archlinux.org/viewtopic.php?id=218509. Even though his report is almost 2 years old by now, things haven't changed as far as I can tell."
1774560,2018-06-07 09:43:15 UTC,Yeah cosmic already has the fix (mutter 3.28.2). You're only waiting on bionic.
1774560,2018-06-11 09:16:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774560,2018-06-11 09:22:18 UTC,It would be great to get the fix backported to Bionic since people have been reporting this as bug in Geary already: https://bugzilla.gnome.org/show_bug.cgi?id=789846#c6
1774560,2018-09-22 18:12:36 UTC,Is this a bug in mutter that has been fixed ?  As I'm wondering why this bug is still open for xdg-desktop-portal-gtk and if it can be closed ?
1774560,2018-07-03 04:21:31 UTC,"bionic-proposed has a 3.28.2 package, so this should be resolved for that release shortly."
1774563,2018-06-01 04:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774563,2018-06-13 11:03:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1774563,2018-07-02 08:29:08 UTC,This bug was fixed in the package linux - 4.4.0-130.156
1774569,2018-09-10 16:58:15 UTC,"Since this is a physical through to block layer issue and not ZFS per-se, I'm going to remove ZFS off this bug report."
1774569,2019-01-02 09:07:14 UTC,"See my comments in this smartmontools ticket:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1810215"
1774569,2019-01-02 05:23:33 UTC,"FYI I am on a rolling distro (arch) and the same problem has started for me with my seagate backup drive
It is still present today"
1774569,2018-12-19 05:10:00 UTC,"HDParm/SDParm bug afects me as well with 2 different Seagate usb drives, I think this one should have a high priority, since it also affects power management. Further more since the aforementioned drive is also a sub-hub it would be good to be able to turn on/off the drive portion without needing to re-plug the usb-cable or the power-cable."
1774569,2018-08-12 16:37:34 UTC,Also not working for my other external HDDs:
1774569,2018-08-12 16:31:32 UTC,Same here:
1774569,2018-08-02 09:05:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774569,2018-06-05 05:52:28 UTC,"It looks like the drive is replying with an ILLEGAL REQUEST/INVALID FIELD IN CDB error to all the interesting SCSI commands, and to pretty much anything hdparm sends it."
1774569,2018-06-05 04:39:13 UTC,"I pulled the hdparm binary from Artful, and it can't spin down the drive with -y either."
1774569,2018-06-05 04:21:58 UTC,"Even after rebooting with the drive for the zpool physically removed from the system, I still had a zpool I couldn't destroy, export, or otherwise remove from the listing."
1774569,2018-06-02 01:48:01 UTC,"Nope, my speculation is definitely wrong. The disk shows up in lsscsi:"
1774575,2018-06-05 17:45:00 UTC,apport information
1774575,2018-06-05 17:45:01 UTC,apport information
1774575,2018-06-05 17:45:03 UTC,apport information
1774575,2018-06-05 17:45:06 UTC,apport information
1774575,2018-06-05 17:45:04 UTC,apport information
1774575,2018-06-05 19:07:51 UTC,"I've forgot to add this.
sudo hwinfo --pci
...
17: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.378]
  Unique ID: _Znp.mHjpIGaFQV1
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: ""InnoTek Systemberatung VirtualBox Graphics Adapter""
  Vendor: pci 0x80ee ""InnoTek Systemberatung GmbH""
  Device: pci 0xbeef ""VirtualBox Graphics Adapter""
  Driver: ""vboxvideo""
  Driver Modules: ""vboxvideo""
  Memory Range: 0xe0000000-0xe1ffffff (ro,non-prefetchable)
  Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
  IRQ: 18 (8 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: ""pci:v000080EEd0000BEEFsv00000000sd00000000bc03sc00i00""
  Driver Info #0:
    Driver Status: vboxvideo is active
    Driver Activation Cmd: ""modprobe vboxvideo""
  Config Status: cfg=new, avail=yes, need=no, active=unknown
..."
1774575,2018-06-05 19:55:16 UTC,apport information
1774575,2018-06-05 17:44:59 UTC,apport information
1774575,2018-06-05 19:03:26 UTC,"apport-collect 1774575 - done - Confirmed
kernel-bug-exists-upstream - Confirmed
---
@Joseph Salisbury (jsalisbury) Thank you for taking care of this issue! To answer your questions...
___
I've updated the Ubuntu 18.04 LTS server in question to the latest stable version (as of today, 5th of June 2018) and nstalled mainline kernel v4.17.
uname -a
Linux u1804svr-t1 4.17.0-041700rc7-generic #201806041848 SMP Mon Jun 4 22:51:06 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -rd
Description:    Ubuntu 18.04 LTS
Release:        18.04
___
Hwinfo is also the latest stable version which comes from the official ubuntu repo via ""apt install hwinfo""
dpkg -l hwinfo

||/ Name             Version       Architecture  Description


+++-================-=============-=============-=====================================
ii  hwinfo           21.52-1       amd64         Hardware identification system
apt-cache policy hwinfo
hwinfo:
  Installed: 21.52-1
  Candidate: 21.52-1
  Version table:
 *** 21.52-1 500
        500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status
___
""sudo hwinfo --framebuffer"" is working on Ubuntu 16.04 server. I started to evaluate Ubuntu 18.04 server and found that this isn't working contrary to the previous LTS.
I've even tried ""sudo hwinfo --framebuffer --verbose"", but still no output.
___
The previous kernel version is ""uname -r"" -> 4.4.0-116-generic on 16.04 LTS.
The mainline kernel version is ""uname -r"" -> 4.17.0-041700rc7-generic on 18.04 LTS
___"
1774575,2018-06-05 17:44:58 UTC,apport information
1774575,2018-06-05 17:44:52 UTC,apport information
1774575,2018-06-05 17:44:55 UTC,apport information
1774575,2018-06-05 17:44:54 UTC,apport information
1774575,2018-06-05 17:44:53 UTC,apport information
1774575,2018-06-05 17:44:51 UTC,apport information
1774575,2018-06-05 17:30:41 UTC,"This is working on Ubuntu 16.04 LTS.
___
which hwinfo
/usr/sbin/hwinfo
___
lsb_release -rd
Description:    Ubuntu 16.04.4 LTS
Release:        16.04
___
apt-cache policy hwinfo
hwinfo:
  Installed: 21.23-1
  Candidate: 21.23-1
  Version table:
 *** 21.23-1 500
        500 http://hu.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status
___
sudo hwinfo --pci
...
10: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.366]
  Unique ID: _Znp.mHjpIGaFQV1
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: ""InnoTek Systemberatung VirtualBox Graphics Adapter""
  Vendor: pci 0x80ee ""InnoTek Systemberatung GmbH""
  Device: pci 0xbeef ""VirtualBox Graphics Adapter""
  Memory Range: 0xe0000000-0xe1ffffff (ro,non-prefetchable)
  IRQ: 18 (no events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: ""pci:v000080EEd0000BEEFsv00000000sd00000000bc03sc00i00""
  Driver Info #0:
    Driver Status: vboxvideo is active
    Driver Activation Cmd: ""modprobe vboxvideo""
  Config Status: cfg=new, avail=yes, need=no, active=unknown
..."
1774575,2018-06-01 19:01:11 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1774575,2018-06-01 06:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774575,2018-06-05 17:44:56 UTC,apport information
1774596,2019-05-30 19:24:50 UTC,It does get called for all classes that inherit from UI::Panel.
1774596,2019-09-15 17:06:03 UTC,Migrated to https://github.com/widelands/widelands/issues/1073
1774596,2019-06-02 09:05:32 UTC,Yes you did. I have attached an image to show you how to make a merge request too. It is better if you do this yourself :)
1774596,2019-06-02 07:47:01 UTC,Created the branch(if I did it properly).
1774596,2019-06-01 22:15:17 UTC,Please open a merge request.
1774596,2019-06-01 22:02:39 UTC,Got the code ready for review now!
1774596,2019-05-30 14:49:25 UTC,"You do not need to call handle_key yourself, the main loop takes care of that."
1774596,2019-05-30 17:57:37 UTC,When I add a handle_key() to a .cc and .h in wui/ it doesn't seem to get called - do I need to ensure it somehow?
1774596,2019-05-29 17:53:06 UTC,I added the handle_key() to window.cc and want to add it to the existing handle_key() from panel.cc.
1774596,2019-05-29 17:55:23 UTC,So I want to check if the current Panel is a Window - or is there a different approach that I should use?
1774596,2019-05-25 07:29:51 UTC,"That would be in the ui_basic directory, in the window.cc class."
1774596,2019-05-23 19:53:03 UTC,Im currently looking for a way to write it so that its implemented for all windows except for some which need to be handled differently.
1774596,2019-05-23 17:51:02 UTC,Hi Antonio :-)
1774596,2019-05-23 17:23:14 UTC,"Yes, it would indeed be nice to close open windows with ESC."
1774596,2019-05-23 17:06:12 UTC,"I would be interested in this one too - and can write some, if not even all code for this one."
1774605,2018-06-01 08:50:27 UTC,Guest xml(cpu portion):
1774617,2018-07-03 22:21:22 UTC,"$ sudo apt remove gnome-software-plugin-snap
?"
1774617,2018-07-04 18:35:34 UTC,"Fair, could this be provided as a graphical toggle just like how different Ubuntu repositories can be enabled/disabled via a GUI?"
1774617,2018-07-09 14:50:43 UTC,I've reassigned it to software-properties - that is where those settings live.
1774618,2018-06-20 12:58:27 UTC,Same problem for `deb http://ppa.launchpad.net/swi-prolog/devel/ubuntu bionic main main/debug`
1774618,2019-08-19 06:52:48 UTC,The reason for this is that debug symbol packages are not generated by default.
1774619,2019-05-14 09:11:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658993"
1774622,2018-09-23 12:25:09 UTC,https://github.com/mixxxdj/mixxx/pull/1741
1774622,2018-06-24 12:38:50 UTC,"We have zero complains, because it will be future regression after releasing 2.2.
There are many reasons for not upgrading an OS.""Never touch a running system"""
1774622,2018-06-24 12:17:49 UTC,"There are probably no users affected. We have gotten zero complaints about this. If someone had a high DPI screen, why would they keep using an OS that doesn't support it when they could upgrade?"
1774622,2018-06-24 11:32:01 UTC,"There are probably a number of users effected and the required change is only minor.
So let's just do it."
1774622,2018-06-01 21:00:18 UTC,2. Are using a 2 year old OS AND are dying to use the latest version of Mixxx
1774622,2018-06-01 20:09:43 UTC,"> I think Yes, because the people will not being upgraded before 18.4.1.
"
1774622,2018-06-01 16:25:24 UTC,"I think Yes, because the people will not being upgraded before 18.4.1.
A fix will probably only involve some lines. It is only an issue of the auto-detection, not the scaling itself."
1774622,2018-06-01 16:09:16 UTC,Is there anything for us to do here? People who want hidpi support can upgrade to Bionic which is an LTS.
1774624,2018-08-31 09:08:30 UTC,"Hi,"
1774624,2018-12-11 20:55:22 UTC,Could you describe the usefulness of such routing rules? It would help to define a test that will correctly let us verify this works when implemented.
1774624,2020-04-14 12:33:11 UTC,I'm actually using firewall marking as the basis of my routing:
1774625,2018-06-09 03:39:33 UTC,"But that's why you can click ""cancel."" If you navigate off the screen with
""ok / apply"" or ""next / previous,"" it should save unless you tell it
otherwise IMO."
1774625,2018-06-05 16:29:48 UTC,"Interesting...having been a Mac user for many years, in iTunes it's
standard behavior that clicking ""Next"" or ""Previous"" saves the changes. I
don't quite understand the logic of making changes to metadata, then moving
to another track and it NOT saving. Why would anyone want to do that?"
1774625,2018-06-01 12:51:08 UTC,"The current layout implies to me, that I can edit as many tracks I like and finally press cancel or apply all. So we should either do it exact like that and keep a list of cloned tracks, or we need to rearrange the buttons like this draft:"
1774625,2018-06-05 18:57:32 UTC,The user might have messed up things and want to undo it. We should at least keep an option for this.
1774625,2018-06-01 12:07:38 UTC,I think it would be better to ask the user when the next/previous buttons are pressed than bury the option in the preferences (why would a user think to look there when editing metadata?).
1774625,2018-06-01 11:50:37 UTC,I also always stumble about this. On the other hand saving metadata implicitly while navigating is dangerous.
1774625,2018-06-01 12:25:24 UTC,"I don't propose a preference setting, that context would be too broad."
1774631,2018-06-14 12:48:10 UTC,Launchpad is no longer being used as the bug tracker for Percona Server.  Please visit our JIRA at https://jira.percona.com/projects/PS Edit
1774632,2018-06-07 09:08:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774632,2019-03-31 17:38:53 UTC,"The link target, stub-resolv.conf is the correct file for enabling systemd-resolvd.  Various problems with the systemd-resolvd may be fixed by installing the libnss-resolve package (bug 1769016). Blank local domain problems have their own bug, 1699660 (fix is to use ~.). This report probably should be marked ""invalid""."
1774632,2020-12-20 18:55:39 UTC,I just ran into this issue myself on 20.04. Specifically I was adding my own internal nameserver to a vm.
1774640,2020-11-11 12:03:48 UTC,I can confirm this problem for Ubuntu 20.04 and 20.10 on a Thinkpad X260.
1774640,2018-06-05 09:46:19 UTC,apport information
1774640,2020-07-15 06:00:43 UTC,The same happens to me. After some time it automatically turns off and is unable to turn back on. The button in Bluetooth settings does nothing. I am using Ubuntu 20.04 on Acer Aspire E5-552G-T21P.
1774640,2019-10-05 13:02:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774640,2018-06-05 09:47:45 UTC,"I am able to turn Bluetooth on, but after a few seconds it turns off automatically again. Only after a reboot of my laptop I am able turn Bluetooth on without any problems. I've run 'apport-collect 1774640'."
1774640,2018-06-05 09:46:21 UTC,apport information
1774640,2018-06-05 09:46:20 UTC,apport information
1774640,2018-06-05 09:46:15 UTC,apport information
1774640,2018-06-05 09:46:17 UTC,apport information
1774640,2018-06-05 09:46:13 UTC,apport information
1774640,2018-06-05 09:46:14 UTC,apport information
1774640,2018-06-05 09:46:18 UTC,apport information
1774640,2018-06-04 02:40:22 UTC,"Are you able to turn Bluetooth on again using:
  Settings > Bluetooth > (titlebar) = ON
?"
1774640,2018-06-05 09:46:17 UTC,apport information
1774640,2018-06-05 09:46:10 UTC,apport information
1774640,2018-06-05 09:46:11 UTC,apport information
1774640,2018-06-04 02:40:51 UTC,Please also run 'apport-collect 1774640' to send us more system information.
1774640,2018-06-05 09:46:12 UTC,apport information
1774645,2018-12-04 16:17:31 UTC,"Thanks for the solution, this was no fun to debug on multiple servers."
1774645,2019-05-07 20:37:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774645,2019-07-03 20:39:02 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822841 is what downgraded keyutils from a Recommends to a Suggests
1774646,2018-06-02 05:24:31 UTC,"On Sat, Jun 02, 2018 at 04:16:45AM -0000, Willem Hobers wrote:

> So, did I do something wrong when I installed 18.10?
"
1774646,2018-06-01 20:17:51 UTC,"> Ubiquity seems to have decided that it was installing on a uefi-machine.
"
1774646,2018-06-01 19:56:55 UTC,"Hi Steve,"
1774646,2018-06-01 19:19:14 UTC,"Your bug report shows that this is an upgrade of the shim-signed package. How/why do you have the shim-signed package installed, if your system is not booted in UEFI mode (according to the output of efibootmgr) and you do not have an EFI system partition mounted at /boot/efi?"
1774646,2018-06-02 04:16:45 UTC,"So, did I do something wrong when I installed 18.10?"
1774652,2018-06-01 14:13:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774655,2018-06-01 14:34:09 UTC,Url: https://bazaar.launchpad.net/~sivan/hubackup/hubackup--main/view/head:/HUBackup/backend/BackupEngine.py
1774655,2018-06-15 00:23:40 UTC,Has this been triaged ? I wish to extract some code off the repo hope this czn be fixed.
1774656,2018-06-06 01:10:49 UTC,"A much better workaround is to launch the gamepad into ""Windows mode,"" where it emulates an Xbox360 controller. (Hold X and Start while it's turned off, before you've plugged it in if you're going to)"
1774660,2018-06-01 15:45:23 UTC,I came up with this simplistic patch. Still needs verification.
1774660,2018-06-03 20:52:14 UTC,The patch from comment #1 has been successfully tested by the reporter at SUSE.
1774660,2018-06-06 10:24:55 UTC,"Hi Martin,"
1774660,2018-06-06 12:24:20 UTC,Hi
1774660,2018-06-06 13:10:36 UTC,The printer is an old HP Deskjet 1000 110J connected via USB. The reporter said further
1774660,2018-06-07 06:49:32 UTC,My previously attached patch contained a bug. I mustn't change the default for ignore_pen_error to TRUE in the prototype of DJ9xxVIP::DJ9xxVIP(). The default must be FALSE in order to keep standard behavior for DJ9xxVIP printers which are not DJGenericVIP instances.
1774660,2018-06-12 05:55:54 UTC,"Hi Martin,"
1774660,2018-06-12 06:57:51 UTC,"Srinivas,"
1774660,2018-07-06 14:08:51 UTC,The user who reported this has given feedback on my patch v2 (comment 6):
1774665,2019-09-19 11:58:33 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1774665,2018-06-01 20:51:24 UTC,Fantastic - then 'boot' flag should be ignored on EFI systems.
1774665,2018-06-01 20:31:20 UTC,That’s already modeled.
1774665,2018-06-01 19:32:27 UTC,How about actually modeling whether or not a machine is EFI or BIOS?
1774665,2018-06-01 16:11:48 UTC,Why was this marked as a duplicate? I don't want grub installed on either disk.
1774665,2018-06-01 17:43:28 UTC,"Ok, I see what you are saying."
1774665,2018-06-01 17:12:32 UTC,"Andres, I'm not using either of these disks to host the efi partition, and that's not being created by maas in any case. It's just putting a gpt partition table on one disk and making one partition, which is being put into the raid set. I believe it's doing this because it thinks grub for bios will be installed on that disk since it's marked with the 'boot' flag."
1774665,2018-06-01 16:39:23 UTC,"This seems like a shortcoming in how maas models efi vs bios. On an efi system, there should not be a 'Boot' flag available for disks."
1774665,2018-06-01 17:50:15 UTC,"A potential solution could be to automatically create /boot/efi on the disk with the boot flag, and/or allow to override it if the user manually creates /boot/efi and/or MAAS does."
1774665,2018-06-01 16:38:47 UTC,"Hi Jason,"
1774688,2019-06-21 11:31:56 UTC,"Also FYI, bug report for the issue in my previous comment: https://bugs.launchpad.net/devstack/+bug/1833696"
1774688,2018-10-16 16:10:59 UTC,This issue has larger impacts in my environment at least.
1774688,2018-08-02 21:49:57 UTC,"I don't think we'll be able to target this for Rocky, bumping to Stein."
1774688,2018-08-01 21:39:08 UTC,This will likely depend on a new version of sqlalchemy (which doesn't appear to be compatible with MariaDB 10.3)
1774688,2019-06-21 10:04:03 UTC,"FYI, as I encountered a similar issue but turned out to be devstack doing (stable/queens, CentOS 7)."
1774697,2020-05-08 00:50:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/726269"
1774697,2020-05-19 15:27:12 UTC,"Reviewed:  https://review.opendev.org/726269
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=c52686a06f1aeaaaaba1ed3d98f1d404ba3d9a9b
Submitter: Zuul
Branch:    master"
1774701,2021-02-18 19:21:26 UTC,"Marking this one Won't Fix as it's been changed in the Bootstrap OPAC. If any additional changes are requested, please move to new wish list tickets."
1774701,2018-06-01 19:19:32 UTC,"Adding a note that for Evergreen sites that have enabled the ebook API for Overdrive or OneClickDigital, this isn't exactly duplicate information. See screenshot at http://www.screencast.com/t/64JHB9pyUk"
1774701,2020-08-21 22:00:51 UTC,This has been updated so as to not duplicate the text and provide links on each over at https://bugs.launchpad.net/evergreen/+bug/1778972. Still maybe needs a design update but this issue is fixed in that bug fix
1774701,2018-06-01 19:25:48 UTC,"Actually, I like the way Sitka has customized it, as shown from this screenshot from their documentation. https://docs.libraries.coop/sitka/images/opac/opac-eresource-1.png"
1774704,2018-10-09 20:57:59 UTC,"Yeah, that first one shouldn't happen -- we returned results that are before the marker!"
1774707,2018-06-05 20:56:18 UTC,"Confirmed this is occurring in Web Client 3.0.8.
Tested in Google Chrome."
1774707,2018-11-05 20:32:27 UTC,Here is the very simple fix:
1774707,2018-11-05 20:52:30 UTC,"Note: to test, you will probably need to clear your browser cache."
1774707,2018-12-04 14:23:40 UTC,This needs an upgrade script (add this persist key to config.workstation_setting_type) because of the change to server-side settings. Thanks to Michele Morgan for the tip (see https://bugs.launchpad.net/evergreen/+bug/1729435/comments/5).
1774707,2019-04-12 20:19:39 UTC,Working branch that adds the seed data and upgrade script is here:
1774707,2019-05-20 19:15:46 UTC,Issue and fixes confirmed.  Thanks Michele and Remington.  Merged to 3.2 and above.
1774711,2019-12-02 15:40:56 UTC,"On 2019-11-30 21:44:33, A. Denton wrote:

> Will the required pat set be backported to older kernel, such as Ubuntu
> 4.15.0-70.79-generic 4.15.18?
"
1774711,2019-11-30 21:44:33 UTC,"Will the required pat set be backported to older kernel, such as Ubuntu 4.15.0-70.79-generic 4.15.18?"
1774711,2019-01-03 02:24:19 UTC,Oh in short my /etc/audit/rules.d/audit.rules looks like this:
1774711,2019-01-03 02:15:42 UTC,"After some research I can now safely confirm this bug. However, the log lines do not seem to be related to any rules in ""/etc/audit/rules.d"" or AppArmor profiles loaded. %‑)"
1774711,2018-06-01 19:51:03 UTC,This is fixed by the following commits in the linux-next tree:
1774711,2019-06-11 13:48:36 UTC,For the record:
1774713,2018-06-01 21:13:43 UTC,"What do you mean by DOS output? Here's a question I posted on askubuntu that contain the output to the terminal (stdout and stderr):
https://askubuntu.com/questions/1041427/core-dumped-upon-selection-of-object-in-inkscape"
1774713,2018-06-03 13:39:34 UTC,Pasting:
1774713,2018-06-03 13:47:19 UTC,"I think it's not possible to combine conversion actions with editing actions on the Inkscape command line. The documentation doesn't mix them (but it shouldn't crash, instead give a helpful message - or better, Inkscape should allow it)."
1774713,2018-06-03 14:02:43 UTC,(just added the -z / --verb incompatibility info to the man page)
1774713,2018-06-01 20:55:08 UTC,could you attach the DOS output you are getting from the segfault?
1774717,2018-06-02 09:38:32 UTC,Here is a relevant thread on debian-perl: https://lists.debian.org/debian-perl/2018/05/msg00046.html
1774723,2018-06-01 21:11:01 UTC,"StacktraceTop:
 XkbCopyKeymap (dst=0x55cecfc1a7a0, src=0x55cecf406880) at ../../../../xkb/xkbUtils.c:1957
 XkbCopyKeymap (src=<optimized out>, dst=<optimized out>) at ../../../../xkb/xkbUtils.c:1965
 XkbDeviceApplyKeymap (dst=dst@entry=0x55cecf3a2b90, desc=<optimized out>) at ../../../../xkb/xkbUtils.c:2025
 CopyKeyClass (device=device@entry=0x55cecf405630, master=master@entry=0x55cecf3a2b90) at ../../../../Xi/exevents.c:233
 DeepCopyKeyboardClasses (to=0x55cecf3a2b90, from=0x55cecf405630) at ../../../../Xi/exevents.c:427"
1774723,2018-06-07 10:04:48 UTC,Sounds related to bug 1762801.
1774723,2018-06-07 10:07:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774723,2018-06-07 10:08:20 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/d0aed32d6455f555b4852947fb0ca074a064c8db"
1774727,2018-06-03 17:06:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774733,2020-03-18 16:43:59 UTC,"Reviewed:  https://review.opendev.org/712040
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=0a02c30fe5f4650235519897b71588ae22fa0971
Submitter: Zuul
Branch:    master"
1774733,2018-06-13 19:06:42 UTC,An example of how to create a system-scoped token via keystone API (openstack client support seems to be missing at the time of writing) with a notably different scope section in the request:
1774733,2018-08-21 04:17:04 UTC,This is indeed good input.  We will probably revisit this as we approach reworking how Keystone is bootstrapped in the charm.
1774740,2018-06-11 06:58:29 UTC,This is more likely to be a kernel bug.
1774740,2018-06-11 07:00:05 UTC,This change was made by a bot.
1774743,2018-06-01 23:43:22 UTC,"StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x7f5cce0e5c2d ""gstaudiodecoder.c"", line=line@entry=1507, func=func@entry=0x7f5cce0e7c10 <__func__.23680> ""gst_audio_decoder_push_buffers"", message=message@entry=0x7f5c5001d830 ""assertion failed: (offset + len <= av)"") at ../../../../glib/gtestutils.c:2532
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x7f5cce0e5c2d ""gstaudiodecoder.c"", line=line@entry=1507, func=func@entry=0x7f5cce0e7c10 <__func__.23680> ""gst_audio_decoder_push_buffers"", expr=expr@entry=0x7f5cce0e5f60 ""offset + len <= av"") at ../../../../glib/gtestutils.c:2555
 gst_audio_decoder_push_buffers (dec=dec@entry=0x7f5c50014a30, force=force@entry=0) at gstaudiodecoder.c:1507
 gst_audio_decoder_chain_forward (dec=dec@entry=0x7f5c50014a30, buffer=0x0, buffer@entry=0x7f5c9c19daf0) at gstaudiodecoder.c:1654
 gst_audio_decoder_chain (pad=<optimized out>, parent=0x7f5c50014a30, buffer=0x7f5c9c19daf0) at gstaudiodecoder.c:1914"
1774744,2019-01-30 10:19:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774744,2019-01-30 10:23:25 UTC,"Indeed, that's still an issue, reported upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/861"
1774744,2019-01-30 12:37:00 UTC,The issue was already reported there as https://gitlab.gnome.org/GNOME/nautilus/issues/386
1774757,2019-10-17 12:21:09 UTC,"I can't quite imagine what could have happened here, but I'm totally unable to reproduce it.  Also, you are the only one that reported this, so I'm totally at a loss.  I'll be marking this bug as incompleted, and see if anybody can post new details, otherwise it'll expire."
1774757,2019-12-17 04:17:23 UTC,[Expired for graphite2 (Ubuntu) because there has been no activity for 60 days.]
1774759,2018-06-02 06:05:47 UTC,"After selecting both and right-click -> ""Create pad from selected shapes"""
1774759,2018-06-06 20:35:50 UTC,"Tom has left a note in footprint_editor_tools.cpp:402:
""// ignore the pad orientation and offset for the moment. Makes more trouble than it's worth."""
1774768,2019-04-01 20:25:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774771,2018-06-02 11:00:08 UTC,This change was made by a bot.
1774771,2018-06-02 10:39:59 UTC,apport information
1774771,2018-06-02 10:39:43 UTC,apport information
1774771,2018-06-02 10:39:54 UTC,apport information
1774771,2018-06-02 10:39:46 UTC,apport information
1774771,2018-06-02 10:39:45 UTC,apport information
1774771,2018-06-04 12:52:47 UTC,"Would it be possible for you to see if this bug was already fixed in the mainline kernel, which is available from:"
1774771,2018-06-02 10:39:41 UTC,apport information
1774771,2018-06-02 10:39:33 UTC,apport information
1774771,2018-06-02 10:39:39 UTC,apport information
1774771,2018-06-02 10:39:37 UTC,apport information
1774771,2018-06-02 10:39:36 UTC,apport information
1774771,2018-06-02 10:39:35 UTC,apport information
1774771,2018-06-02 10:39:32 UTC,apport information
1774771,2018-06-02 10:39:30 UTC,apport information
1774771,2018-06-02 10:39:28 UTC,apport information
1774771,2018-06-02 10:39:27 UTC,apport information
1774771,2018-06-02 10:39:40 UTC,apport information
1774773,2020-07-04 10:06:55 UTC,Synced from Debian to Ubuntu and available since 19.04 https://launchpad.net/ubuntu/+source/pygnuplot
1774773,2018-06-02 11:26:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774773,2018-10-06 12:22:04 UTC,See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910437
1774773,2018-06-02 23:55:03 UTC,*** This is an automated message ***
1774773,2019-01-14 22:59:56 UTC,"This has been packaged by Debian, see also https://packages.debian.org/sid/python3-pygnuplot"
1774779,2018-06-04 14:45:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774780,2018-06-20 13:59:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774780,2018-07-24 02:56:19 UTC,"Round 3 with this driver breaking on a kernel update. I found a similar bug that was fixed in this package https://bugzilla.rpmfusion.org/show_bug.cgi?id=4798 (wl-kmod). If you go to the link in the second comment and download the source RPM, it contains a timer patch for kernel 4.15 ."
1774780,2018-08-08 18:24:19 UTC,"Once again the latest ""update"" this time on 8/8/18 broke the rtl8812au packages."
1774780,2018-08-19 17:46:57 UTC,Also doesn't work with ubuntu 16.04
1774786,2018-06-03 13:27:48 UTC,"Hi Chad,"
1774788,2018-06-04 21:28:47 UTC,Thanks for filing this bug in Ubuntu.
1774788,2018-06-04 21:49:57 UTC,I'm impressed!
1774788,2018-06-04 22:00:14 UTC,"I'm a recent convert to Ubuntu, having been on Fedora from FC2 through F26; quite a long time. Over the last few years, their support became nonexistent. Bugs reported would not even be acknowledged, much less worked on. To have someone actually respond to a bug report is so unusual in my experience that I'm pleasantly shocked. Thank You. Thank You."
1774788,2018-06-04 22:21:16 UTC,"The default behaviour of these services is to bind to ""0.0.0.0"", which means ""any IP"" essentially. That means they will work even when the nic isn't there yet, because localhost is. It also means that once a new nic comes up, they will listen on all its addresses too, without any other changes in configuration or restarts. Same for when an address disappears. It's definitely a good default for network services."
1774789,2018-08-06 12:34:21 UTC,The bug disappeared a couple of week ago. Thanks!
1774789,2018-06-25 05:46:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774793,2018-06-04 13:57:20 UTC,"Thank you Joseph for your help, I'm going to start with the mailing list."
1774793,2018-06-04 12:59:24 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1774793,2018-06-03 18:00:10 UTC,This change was made by a bot.
1774793,2018-06-03 17:42:41 UTC,apport information
1774793,2018-06-03 17:42:40 UTC,apport information
1774793,2018-06-03 17:42:38 UTC,apport information
1774793,2018-06-03 17:42:37 UTC,apport information
1774793,2018-06-03 17:42:35 UTC,apport information
1774793,2018-06-03 17:42:34 UTC,apport information
1774793,2018-06-03 17:42:33 UTC,apport information
1774793,2018-06-03 17:42:29 UTC,apport information
1774793,2018-06-03 17:42:31 UTC,apport information
1774793,2018-06-03 17:42:26 UTC,apport information
1774793,2018-06-03 17:42:25 UTC,apport information
1774793,2018-06-03 17:42:24 UTC,apport information
1774793,2018-06-03 17:42:22 UTC,apport information
1774793,2018-06-03 17:42:20 UTC,apport information
1774793,2018-06-03 17:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774793,2018-06-03 16:20:53 UTC,input devices log
1774793,2018-06-03 16:19:46 UTC,dmesg
1774793,2018-06-03 16:19:13 UTC,Xorg.0.log
1774793,2018-06-03 16:18:21 UTC,system log files
1774793,2018-06-03 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774793,2018-06-02 15:48:06 UTC,apport information
1774793,2018-06-03 17:42:27 UTC,apport information
1774793,2018-06-02 15:48:05 UTC,apport information
1774794,2019-06-09 16:33:00 UTC,Just brought it back; -progs 5.1-1 are in Debian experimental and eoan-proposed.
1774794,2018-07-17 20:26:43 UTC,"I found with some experimentation that btrfs_reserve_extent() fails due to free space fragmentation. If you don't have a large enough contiguous block on the filesystem you're trying to convert, that incurs the problem. It's poor error messaging."
1774794,2018-06-12 00:54:19 UTC,"FWIW, it looks like btrfs-convert is being dropped upstream. I just compiled mine from source, and it crashed after some heavy churning. The package description should be changed though (it explicitly mentions btrfs-convert). Here's a relevant thread:"
1774794,2018-06-06 23:02:31 UTC,"4.16.1 source from Cosmic builds in the Bionic release. Suggest upping the version as a bugfix is appropriate, though I don't understand how that fits into the packaging philosophy."
1774794,2018-06-06 22:59:48 UTC,Also would need https://patchwork.kernel.org/patch/10281327/ applied in order to compile.
1774794,2018-06-06 21:55:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774794,2018-06-07 00:23:50 UTC,"The attachment ""Remove the ""--disable-convert"" flag"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1774803,2019-06-02 21:40:58 UTC,"Hi, I wanted to let you know that Mugshot has moved to GitHub and this issue has been migrated to the below URL. I'll be closing this report and further progress will be made on the linked issue. Thanks!"
1774804,2018-06-02 17:47:20 UTC,"Well, who would believe it! Just did update the mugshot information once again and hey presto: the question about pidgin did for once turn up again. And this time I was running from terminal with -vv:"
1774804,2018-06-02 17:49:23 UTC,"So tried again with -vv, but no pidgin-question this time:"
1774804,2019-06-02 21:40:22 UTC,"Hi, I wanted to let you know that Mugshot has moved to GitHub and this issue has been migrated to the below URL. I'll be closing this report and further progress will be made on the linked issue. Thanks!"
1774805,2018-06-03 10:55:39 UTC,How did you install it? If this was from Ubuntu Software via the snap package then currently you need to manually give the snap permission to read sensor values (this only needs to be done once):
1774805,2018-06-03 11:39:35 UTC,Apologies - wrong command - it should have been:
1774807,2019-06-02 21:39:36 UTC,"Hi, I wanted to let you know that Mugshot has moved to GitHub and this project has been migrated to the below URL. I'll be closing this report and further progress will be made on the linked issue. Thanks!"
1774808,2019-06-02 01:37:12 UTC,"This is actually not a bug! Some user details (those stored in /etc/passwd) require a password to update, while others (accessed via AccountsService) do not."
1774810,2018-06-14 20:17:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774812,2018-09-29 13:09:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774815,2020-03-16 10:53:57 UTC,This bug was fixed in the package linux - 4.15.0-91.92
1774815,2020-02-17 21:28:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1774815,2019-07-21 16:50:27 UTC,"Sent a patchset to package bpftool in linux-tools/linux-tools-common for bionic, here is the related link:"
1774815,2019-09-11 18:17:23 UTC,This bug was fixed in the package linux - 5.3.0-10.11
1774815,2019-03-06 14:47:14 UTC,Any news on this topic?
1774815,2018-06-02 21:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774815,2019-11-12 20:04:58 UTC,"All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1774817,2019-03-07 16:12:52 UTC,Thermal shutdown by kernel or by BIOS?
1774817,2019-03-07 12:39:44 UTC,"My system is overclocked so that it's fine for daily use but when I do
encoding it can sometimes stop due to thermals.
It also directly impacts benchmarking, since I don't see the temperature
profile rise, it's hard to figure out what to do."
1774817,2019-03-07 06:34:25 UTC,"Does this affect ""real"" usage? AFAICT thermald doesn't work on AMD platforms (yet)."
1774817,2018-08-30 00:36:12 UTC,"This also applies to the new Threadrippers (2990WX, etc.)"
1774817,2018-06-04 12:56:12 UTC,"Hi Kai-Heng,
I am using 2700, specifically because it's a mini-itx and lower power is beneficial for small form factors.
Thanks regardless!"
1774817,2018-06-04 03:16:38 UTC,"Do you use 2700 or 2700X?
There's a new patch for 2700X:
commit 1b59788979acd230b9627276c76f6e6ba2c4709c
Author: Guenter Roeck <email address hidden>
Date:   Tue Apr 24 06:55:55 2018 -0700"
1774817,2018-06-02 23:01:30 UTC,"Sorry this is the first ever bug I report, apport-collect returns:"
1774817,2018-06-02 23:00:08 UTC,apport information
1774817,2018-06-02 23:00:05 UTC,apport information
1774817,2018-06-02 23:00:03 UTC,apport information
1774817,2018-06-02 23:00:00 UTC,apport information
1774817,2018-06-02 22:59:59 UTC,apport information
1774817,2018-06-02 22:59:58 UTC,apport information
1774817,2018-06-02 22:59:56 UTC,apport information
1774817,2018-06-02 22:59:55 UTC,apport information
1774817,2018-06-02 22:59:53 UTC,apport information
1774817,2018-06-02 22:59:52 UTC,apport information
1774817,2018-06-02 22:59:51 UTC,apport information
1774817,2018-06-02 22:59:49 UTC,apport information
1774817,2018-06-02 22:59:48 UTC,apport information
1774817,2018-06-02 21:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774817,2018-06-02 23:00:02 UTC,apport information
1774822,2020-08-10 01:50:08 UTC,"Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!"
1774824,2019-04-17 10:28:57 UTC,"Hello leonardo,
do you still have this issue with the latest 4.15 kernel on Bionic?
Thanks."
1774824,2019-06-17 04:17:33 UTC,[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.]
1774826,2019-06-10 15:38:25 UTC,"All right, I finally got around to implement this. I submitted a merge request at https://code.launchpad.net/~ralfjung-e/mailman/2.1/+merge/368614. It took quite a while to figure out how to do that on Launchpad so I hope that's the right thing to do."
1774826,2018-06-14 22:08:25 UTC,"On 06/14/2018 12:27 AM, Ralf Jung wrote:

>
> So, having an additional outer-level dictionary mapping languages to
> something like what I am using currently?  Yes, I can do that.
"
1774826,2018-06-14 07:27:13 UTC,"> I think the display and verify functions should be in Mailman/Utils.py rather than a separate module.
"
1774826,2018-06-10 19:00:18 UTC,I have looked at your blog post describing the patch. It is interesting and to me it is quite reminiscent of the MoinMoin TextCHA feature. See https://moinmo.in/HelpOnSpam for a bit on that.
1774826,2018-06-10 17:33:08 UTC,"I have implemented such a simple CAPTCHA for Mailman 2 and described the patch at <https://www.ralfj.de/blog/2018/06/10/mailman-subscription-spam-continued.html>.  If there is interest from the maintainers, I'd be happy to prepare a merge request for this."
1774828,2018-09-21 06:57:13 UTC,"I see only one disk (sda) in lshw, sdb being the usb stick. disk/disk_stress_ng_sda should then be the test corresponding to your nvme disk if it's the only available internal drive on this system. Please confirm."
1774828,2018-10-24 08:34:48 UTC,From output of lshw
1774828,2018-12-14 07:51:46 UTC,I just have another failure with NVMe is partitioned and formatted but can not start disk stress test
1774828,2020-01-31 03:33:56 UTC,I've encountered what may be another manifestation of this bug. I configured a server (via MAAS) in an admittedly crazy way:
1774828,2020-02-10 16:19:50 UTC,"I've re-deployed aitken with a more conventional (for certification) layout, and certify-advanced detected all the disk devices. Clearly, more investigation is required...."
1774828,2020-02-10 16:46:03 UTC,"First place to check would be in plainbox-provider-resource-generic/bin/block_device_resource. Specifically, it does this:"
1774828,2020-02-25 18:42:48 UTC,We may be looking at two issues here:
1774828,2020-10-06 14:42:25 UTC,"Ike, is this still a problem?"
1774828,2020-10-08 03:38:34 UTC,No. not hit this problem for a while and can not stable reproduce. I will close it for now and re-open if I can reproduce it stably.
1774829,2018-06-02 23:46:01 UTC,"I followed the advice and converted PNG files to PNG24, this is the procedure:"
1774829,2019-01-15 02:41:30 UTC,Confirmed on 18.04 and the above fix (although I changed the path to /usr/share/mplayer/skins/default on my system) worked for me.
1774830,2020-11-24 16:36:05 UTC,"Looking at your patch and the fix in commit 437588d81d99ac91cb1e, the modifications are the same, so this issue should be fixed, indeed. Big sorry that your bug report here fell through the cracks, but at least it's fixed now. Closing this ticket as duplicate."
1774830,2020-11-24 16:32:28 UTC,I think this is likely a duplicate of bug https://bugs.launchpad.net/qemu/+bug/1900779 which has recently been fixed. Could you please check with the latest release candidate of QEMU 5.2 whether the issue is fixed for you? Thanks!
1774831,2018-06-21 04:31:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774832,2018-11-04 05:52:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774832,2018-11-04 05:56:00 UTC,"postinst in function download_file() calls `wget --compression=none`, which option causes wget to exit with an error (despite the fact that wget(1) documents the option)."
1774843,2020-05-21 18:10:48 UTC,"Hmm, that was a bad paste here is the regression test for 19.10:"
1774843,2020-06-17 01:15:42 UTC,This bug was fixed in the package apport - 2.20.11-0ubuntu27.3
1774843,2020-06-08 17:15:30 UTC,I successfully performed the verification on Ubuntu 20.04 LTS.
1774843,2020-06-05 14:18:01 UTC,"Hello Bart, or anyone else affected,"
1774843,2020-05-28 09:08:40 UTC,This bug was fixed in the package apport - 2.20.11-0ubuntu8.9
1774843,2020-05-28 09:08:31 UTC,"The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1774843,2020-05-28 09:08:27 UTC,This bug was fixed in the package apport - 2.20.9-0ubuntu7.15
1774843,2020-05-22 12:29:59 UTC,Łukasz's remark on focal: +1
1774843,2020-05-21 18:03:02 UTC,Verified on Ubuntu 19.10:
1774843,2020-05-22 12:02:21 UTC,"Verified on Ubuntu 19.10
on 19.10 python3-apt is built for pyton3.7, the system python for 19.10
so i tested against python3.8 from universe."
1774843,2020-05-21 14:41:29 UTC,"All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.15) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1774843,2020-05-21 17:57:35 UTC,Verified on Ubuntu 18.04 LTS:
1774843,2018-06-06 17:25:56 UTC,So apport needs to catch the exception and do nothing / not register an excepthook on unsupported python versions.
1774843,2018-10-07 07:34:14 UTC,"As a workaround, I removed the 3.7 sitecustomize.py files:"
1774843,2019-02-18 17:33:48 UTC,Any update on this issue?
1774843,2019-10-21 18:00:58 UTC,Just ran into this same problem.
1774843,2018-06-07 06:57:51 UTC,"well my reasoning was slightly different from supported/unsupported
i am not familiar with the exact scope of the apport project,
but I assume the goal is to collect info on ubuntu packages, not any unrelated code,
and since afaik all packages one one release all use the same (system) python version( i.e. 3.6 for bionic),
-> code running under any other python is of no interest anyhow
-> it only makes sense to install the apport exception hook for that python version,"
1774843,2020-05-21 13:22:05 UTC,"Seeing that focal is an LTS, don't you think that it might still useful to have this 'fix' for that series? Currently we only have python3.8, but I assume we might backport newer python versions in the future. Wouldn't that make people potentially affected by this bug then?"
1774843,2020-05-21 13:22:21 UTC,"Hello Bart, or anyone else affected,"
1774843,2018-06-06 17:23:08 UTC,"python 3.7 is not a supported version, hence modules are not built for it."
1774843,2020-05-21 13:23:43 UTC,"Hello Bart, or anyone else affected,"
1774843,2020-05-14 01:56:33 UTC,This bug was fixed in the package apport - 2.20.11-0ubuntu34
1774847,2018-06-03 09:09:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/571961"
1774847,2018-07-04 09:53:39 UTC,"Change abandoned by Numan Siddique (<email address hidden>) on branch: master
Review: https://review.openstack.org/571961
Reason: Fixing the issue instead in puppet-ovn - https://review.openstack.org/#/c/580114/1"
1774847,2018-08-20 15:17:54 UTC,This issue was fixed in the openstack/puppet-ovn 13.3.0 release.
1774847,2021-02-19 15:52:16 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1774850,2018-06-03 09:36:17 UTC,"dpkg -l | grep apport
ii  apport                                          2.20.9-0ubuntu7.2                           all          automatically generate crash reports for debugging
ii  apport-gtk                                      2.20.9-0ubuntu7.2                           all          GTK+ frontend for the apport crash report system
ii  apport-symptoms                                 0.20                                        all          symptom scripts for apport
ii  python3-apport                                  2.20.9-0ubuntu7.2                           all          Python 3 library for Apport crash report handling"
1774850,2018-06-03 09:44:42 UTC, apport-collect 1773651
1774850,2020-06-16 08:29:17 UTC,"​​​​this driver has been removed from Ubuntu, closing the bugs"
1774857,2019-04-29 22:13:01 UTC,"Probably related:
https://bugzilla.redhat.com/show_bug.cgi?id=1336308"
1774857,2018-08-18 16:41:10 UTC,"Since nobody has reacted to this report for a couple of months, I decided to file an upstream report at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32472"
1774857,2018-08-29 10:13:47 UTC,"One user on debbugs.gnu.org reported that the problem is more likely related to the locale / glibc than coreutils, and that it occurs on Ubuntu 18.04 but not Fedora 28, in case that helps any. He thought it might have already been fixed in glibc, since Fedora tends to be more up to date than Ubuntu."
1774857,2018-12-08 20:22:00 UTC,"Using the first test case, this does appear to be fixed in cosmic (glibc 2.28) and beyond, and only affect bionic (glibc 2.27), which certainly implies either an upstream or Debian fix slipped in between the two.  I'm not sure I'll have the bandwidth to dig into it this SRU cycle, but I'll try to look again when I can and."
1774873,2018-06-07 14:34:56 UTC,"Can you backport this upstream fix?
https://github.com/mate-desktop/engrampa/commit/499e600d758578eeb8187f92d0c12b36e50f7595"
1774873,2018-06-07 16:22:46 UTC,"The attachment ""0001-add-.a-support.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1774878,2018-07-30 11:13:28 UTC,Google Translate from German to English indicates initial description is:
1774883,2018-06-12 07:12:21 UTC,Please tell the Aquantia developers about this issue:
1774883,2018-06-06 10:50:13 UTC,"Arch has aslo the same issue, looks like some kernel bug:"
1774883,2018-06-04 00:36:45 UTC,apport information
1774883,2018-06-06 10:49:19 UTC,I have similar problem at my LAN on some PC running ubuntu 18.04:
1774883,2018-06-05 13:10:15 UTC,update: I put an intel x550 10gbe pcie card in and it runs at 10gbe without a hiccup... scans all the libraries without issue; no GPFs... definitely something up with either the atlantic driver or (doubtful) the controller itself.
1774883,2018-06-04 16:53:12 UTC,it was a fresh install. I update kernel and still GPF....
1774883,2018-06-04 12:57:40 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1774883,2018-06-04 00:37:25 UTC,apport information
1774883,2018-06-04 00:35:58 UTC,apport information
1774883,2018-06-04 00:33:17 UTC,apport information
1774883,2018-06-04 00:35:33 UTC,apport information
1774883,2018-06-03 18:00:14 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1774883,2018-06-04 00:35:52 UTC,apport information
1774883,2018-06-04 00:33:12 UTC,apport information
1774883,2018-06-04 00:33:26 UTC,apport information
1774883,2018-06-04 00:33:09 UTC,apport information
1774883,2018-06-04 00:35:05 UTC,apport information
1774883,2018-06-04 00:35:13 UTC,apport information
1774883,2018-06-04 00:35:16 UTC,apport information
1774883,2018-06-04 00:35:30 UTC,apport information
1774883,2018-06-04 00:33:57 UTC,apport information
1774887,2018-07-05 20:03:27 UTC,"Big feature, but it would be really cool."
1774887,2018-08-24 23:14:00 UTC,From Leandro Heck (in the duplicate):
1774887,2018-08-28 19:41:08 UTC,My diff tool implementation:
1774887,2018-08-28 20:47:24 UTC,"For schematics, I tested the https://github.com/jnavila/plotkicadsch
It works."
1774887,2018-09-19 09:44:43 UTC,Some examples of commercial EDA diff-tools:
1774887,2018-09-19 09:53:32 UTC,And some blog post related to EDA diffs:
1774888,2019-04-22 11:29:28 UTC,Closing as a fix has been committed in 1.0alpha
1774888,2018-06-09 12:57:49 UTC,"On the very same system I experienced that bug, I now built inkscape from source:
0.92+devel (c0214a5f4e, 2018-06-08) runs fine."
1774888,2018-06-03 20:14:17 UTC,"likely related to
https://bugs.launchpad.net/inkscape/+bug/1769662"
1774888,2018-06-03 19:10:39 UTC,Note that it works fine with inkscape 0.92.3 on my mageia 7 x86-64 system.
1774891,2018-06-06 02:46:37 UTC,"Xubuntu 16.04.4 LTS
Linux 4.4.0-127-generic (x86_64)
2x Intel Core2 Duo CPU E6550@2.33GHZ
3978MB"
1774891,2018-06-06 10:16:59 UTC,"- reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- draw 2 ellipses and perform Path->Difference
- draw two more objects to produce the attached file.
- then select one of the new objects and perform ctrl-Z until the original two ellipses reappear
- then do one more ctrl-Z and get crash with backtrace:"
1774891,2018-06-06 10:22:05 UTC,"crash not reproduced on Windows 10, Inkscape 0.92+devel (7f24a76, 2018-04-17)"
1774891,2018-06-06 10:27:57 UTC,"crash not reproduced on Windows 10, Inkscape 0.92.3 (cc100de, 2018-03-31)"
1774891,2019-05-12 00:37:07 UTC,Possible duplicate: bug 1809676
1774891,2019-05-12 00:38:51 UTC,"Given underlying issue is probably the same, closing as duplicate of bug 1809676."
1774892,2020-08-05 21:42:20 UTC,"Pushed to master for inclusion in 3.6. Thanks, Jason, John, Dawn, and Jason!"
1774892,2020-08-03 12:38:12 UTC,Thanks Jason!  I've pushed a commit to your collab branch with release notes.
1774892,2020-07-15 12:55:16 UTC,"For anyone who is interested in using this now. The code applies cleanly to Evergreen 3.2.10, so I suspect that it will backport cleanly to 3.3, 3.4, and 3.5 as a local addition."
1774892,2020-07-15 12:51:49 UTC,"Thanks, everyone: Jason, John, and Dawn."
1774892,2020-07-14 18:37:32 UTC,"Jason,"
1774892,2020-07-13 19:24:50 UTC,"Thanks, Jason and Jason."
1774892,2020-07-13 14:45:13 UTC,"for easier reference:
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/phasefx/lp1774892-stripe-v3"
1774892,2020-07-10 16:27:00 UTC,"I've added 2 more commits to the branch, for a total of 3 commits at the tip."
1774892,2019-10-23 13:01:57 UTC,This is also important to the SPARK consortium. We have libraries that would like to offer Stripe for credit card payments. We're on version 3.3.
1774892,2020-07-09 18:57:12 UTC,"This is a very big bug indeed. We would need to have this fixed before
implementing."
1774892,2020-07-09 18:31:48 UTC,I have run into a major issue while attempting to test this.
1774892,2020-07-08 19:44:52 UTC,CW MARS is testing this.
1774892,2020-06-26 15:42:55 UTC,Top commit at collab/phasefx/lp1774892-stripe-v3 in the working repo.
1774892,2020-01-23 16:16:43 UTC,CW MARS has signed a contract with Equinox to work on this bug based on Jason Stephenson's outline in comment #4
1774892,2019-03-13 13:49:17 UTC,If we don't upgrade to v3 then Stripe Evergreen sites will need to file for annual compliance using the PCI Data Security Standard Self-Assessment Questionnaire A-EP (https://www.pcisecuritystandards.org/documents/PCI-DSS-v3_2-SAQ-A_EP.pdf) for partially outsourced e-commerce merchants using a third-party website for payment processing.  This places the compliance burden on us not Stripe.
1774892,2019-03-18 12:56:12 UTC,"This is also very important for us at CW MARS, so I will start on an implementation."
1774892,2019-03-14 17:27:24 UTC,NOBLE chose Stripe as our credit card processor because our exposure to PCI compliance was minimal.  We need/want to implement v3 and see this as a high priority.
1774892,2019-03-13 14:24:19 UTC,Marking this High importance since it directly impacts multiple current Evergreen implementations.
1774892,2020-07-10 14:21:17 UTC,Thanks John!  I'm looking at this.
1774895,2021-02-17 17:08:09 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1774895,2018-06-04 01:07:13 UTC,Update 01:
1774895,2018-06-03 22:27:49 UTC,"Edit: -- Content of stack failures and more are here:
https://pastebin.com/yWR7t5RV"
1774895,2018-06-04 09:04:33 UTC,"Update 02:
By using -b, the playbook ran successfully. Also, I omit the --limit option to make it run on all nodes and it also finished successfully. However, I was not presented with output specifying overcloud endpoint. Am I supposed to re-run the (# openstack overcloud deploy) command?"
1774896,2018-11-21 01:47:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774900,2018-06-03 23:35:03 UTC,"Seems to be intermittent, or a once off. Repeating the reboot has me back on the intel card."
1774902,2020-06-20 14:26:59 UTC,"Created attachment 129549
.xsession-errors"
1774902,2020-06-20 14:24:41 UTC,"Created attachment 129548
apt history.log"
1774902,2020-06-20 14:21:41 UTC,The KDE_HOME_READONLY workaround stopped working and failure behavior changed last week after I applied updates to kubuntu 20.04.
1774902,2020-06-05 12:22:33 UTC,I can confirm this bug and workaround on kubuntu 20.04.
1774902,2020-05-15 04:14:18 UTC,Reproducible on 20.04.
1774902,2020-02-10 18:29:10 UTC,"This affects me as well  (on Debian 10). The workaround using KDE_HOME_READONLY works for me, I created a file /etc/xdg/plasma-workspace/env/nfs_home_workaround.sh with the content export KDE_HOME_READONLY=x."
1774902,2019-10-06 22:57:21 UTC,Anyone know if this affects KDE on 19.10?
1774902,2019-06-01 17:14:53 UTC,"Hi.
I confirm.
I mounted a synology shared folder on /home (BTRFS on NFS).
Permissions are OK but im now unable to login with KDE."
1774902,2019-06-03 06:42:41 UTC,Try setting KDE_HOME_READONLY in your environment
1774902,2019-05-24 20:38:42 UTC,"> kdeinit5: Aborting. No write access to $HOME directory (/home/user).
That seems to be the precise problem.
"
1774902,2019-05-23 08:26:09 UTC,Why is this a snapd bug?
1774902,2019-05-23 07:06:42 UTC,Kde is unable to start when user home is an NFSv3 share. I can also confirm this to happen when you try to run a kde application in other desktop environment like gnome or even mint. I get this error
1774902,2019-05-23 06:39:51 UTC,I can confirm  that this bug also affects kde applications like Kile even when run in a gnome desktop. ubuntu 18.04
1774902,2019-03-20 18:00:16 UTC,"Having the exact some conditions and failure here, ssh and local text terminal login fine, as well as LXDE."
1774902,2019-03-20 17:59:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774902,2019-06-03 08:19:13 UTC,"(In reply to Kai Uwe Broulik from comment #2)

> Try setting KDE_HOME_READONLY in your environment
"
1774904,2018-12-12 13:01:30 UTC,"Thank you for your bug report. Is that specific to your user/could you try with a test user? Could you also start gnome-control-center from a command line and see if any warning is displayed, and see if there is a slider for the sound effect in the applications tab when you play the test sound, maybe it's low/muted?"
1774904,2019-02-27 21:49:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774904,2019-02-27 21:55:51 UTC,"Hi, in my case, I think it was simply a missing package dependency. Installing the libcanberra-pulse package fixed it for me."
1774905,2018-06-04 03:16:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572005"
1774931,2018-06-04 06:45:35 UTC,The extraneous ports get there whenever you deploy neutron gateway with incorrect setting for data-port and subsequently correct it.  Or I guess any deployment that has the data-port updated from one interface to another during its lifetime will look like this.
1774932,2018-06-04 06:56:47 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fef24a82b9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7fef24a84bc0 ""malloc(): memory corruption (fast)"") at malloc.c:5350
 _int_malloc (av=av@entry=0x7feee8000020, bytes=bytes@entry=33) at malloc.c:3598
 _int_realloc (av=av@entry=0x7feee8000020, oldp=oldp@entry=0x7feee805d120, oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
 __GI___libc_realloc (oldmem=0x7feee805d130, bytes=bytes@entry=32) at malloc.c:3230"
1774932,2018-07-19 07:29:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774932,2018-07-21 18:50:15 UTC,This is happening to me several times now on a daily basis.
1774935,2019-05-06 05:28:47 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657315"
1774935,2019-05-29 09:19:21 UTC,"Reviewed:  https://review.opendev.org/657315
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=051348814a5f24829395043b3bb75a8feda7efc3
Submitter: Zuul
Branch:    master"
1774944,2019-05-20 14:40:45 UTC,There is a long story why shc hasn't been updated which I won't get into details.
1774944,2020-03-08 20:41:51 UTC,"latest version 4.0.3-0.1 is in Ubuntu now (https://launchpad.net/ubuntu/+source/shc), thus closing this old bug.
Please reopen if problem persists."
1774957,2019-02-17 15:02:16 UTC,There is no 3.28.4 release yet: https://gitlab.gnome.org/GNOME/gnome-shell/tags
1774957,2019-02-17 13:40:31 UTC,According to https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 this is fixed in Gnome Shell 3.30.1 & 3.28.4.  Any chance of getting 3.28.4 (or the fix) in 18.04 LTS desktop?
1774957,2019-02-11 20:53:40 UTC,"I have Ubuntu mate 18.04.2. I don't have gnome-shell installed.
There is this bug."
1774957,2018-12-12 08:07:06 UTC,"For what it's worth, since the update to 18.10 I have not seen the issue again on the two systems I have."
1774957,2018-12-12 02:12:49 UTC,"Sasa,"
1774957,2018-12-11 16:40:58 UTC,it's the same in GNOME 3.30 (Ubuntu 18.10).
1774957,2018-12-07 09:07:30 UTC,"Same here! There are times my Wifi icon and the VPN icon when connecting to a VPN service are missing.
When extending the panel you can't use the switches to enable VPN configuration and the VPN is indicating to off although connencted."
1774957,2018-11-14 08:18:21 UTC,"Yes, 18.04 has been nominated to receive the fix."
1774957,2018-11-14 07:08:14 UTC,Fix released in gnome-shell 3.30.1 (Ubuntu 18.10 onward).
1774957,2018-09-04 07:29:55 UTC,"The fix landed upstream in master, but it was _after_ tag 3.30.0. So the fix is either in gnome-shell version 3.32.0 or 3.30.1 ...?"
1774957,2018-08-22 08:17:58 UTC,A couple of fixes are being worked on right now in the upstream bug:
1774957,2018-08-22 07:46:20 UTC,"I changed it to 0 as well, fingers crossed."
1774957,2018-08-22 07:20:37 UTC,"I could hot-fix this problem by changing network configuration via nm-connection-editor. In my case the ""Connection priority for auto-activation"" was set to -999 for one Ethernet configuration. After changing it to 0 and reconnect, the icons re-appeared. So it is maybe an issue of malformed/weird configuration."
1774957,2018-07-17 07:23:11 UTC,"Upstream bug:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/140"
1774957,2018-07-06 06:34:57 UTC,I have the same problem.
1774957,2018-07-06 02:33:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774957,2018-11-14 07:25:11 UTC,"the fix released in gnome-shell 3.30.1 only available for Ubuntu 18.10. is right?
if it possible to released patch for Ubuntu 18.04?"
1774957,2019-03-14 06:10:06 UTC,"Found the fix is in gnome-shell_3.28.3+git20190124.orig.tar.xz, which means it is in bionic-proposed right now:"
1774957,2019-03-14 05:53:42 UTC,"When will the fix be included in Ubuntu 18.04？this issue has been bothering me for a long time.
and another issue that the gnome-shell always crash every time wake up the screen.
the user experience couldn't be worse...."
1774957,2019-03-14 06:12:35 UTC,"javen,"
1774957,2019-03-23 17:14:55 UTC,"Ubuntu 18.04.2 Gnome
had the problem described above, followed #23 and now my Xserver doesn't work anymore. I am stuck at a terminal."
1774957,2019-03-19 02:13:03 UTC,"javen,"
1774957,2019-03-19 01:53:29 UTC,Hi
1774957,2019-03-18 11:24:28 UTC,Following up on #30 and #29 I can confirm that ubuntu 18.04.2 is working fine with the patch from comment #23
1774957,2019-03-18 11:02:24 UTC,Looking good on 18.04.1 LTS Desktop.  I have installed the patch from comment #23 and the network icon now appears consistently on both the status bar and the status menu.
1774957,2019-03-14 06:11:15 UTC,And you can download the .deb files containing the fix for Ubuntu 18.04 amd64 here:
1774957,2019-03-18 02:35:32 UTC,"Marco,"
1774957,2019-03-15 07:26:57 UTC,"Daniel, how do I know which of the three deb-files"
1774957,2019-03-15 07:36:43 UTC,"You can safely install all three, but you only need two:  *.deb"
1774957,2019-03-18 07:53:19 UTC,"Hi Daniel,"
1774957,2019-03-16 09:22:22 UTC,p.s.: restarting gnome-shell (with SIGQUIT) works as a temporary patch.
1774957,2019-03-16 09:12:11 UTC,I am still experiencing the issue on ubuntu 18.04.4 :
1774959,2018-11-22 00:28:20 UTC,Added Logs from AWS instance failure. This test only appears to fail on the instance types backed via AMD EPYC 7000 series processors with an all core turbo clock speed of 2.5 GHz
1774959,2019-04-05 13:45:51 UTC,"We still see random fails on Azure instances, it does not appear to be isolated to a particular instance"
1774959,2019-05-02 13:47:11 UTC,Failures on Azure still crop up from time to time even after fixes have been applied.  Latest batch is on Standard_E2s_v3 instances.
1774959,2019-05-22 15:13:19 UTC,Affects: 5.0.0-1007.7-azure
1774959,2020-07-24 21:53:23 UTC,monotonic-time is no longer tested in the SRU cycles
1774959,2019-05-02 13:48:00 UTC,"Stats for Comment #3
Kernel: 5.0.0-1005.5-azure
Cloud: Azure
Series: Disco"
1774960,2018-07-08 22:51:22 UTC,"Do you mean that the uniter currently keeps renewing the lease, and it should let it lapse so that a different unit can pick it up once it expires?
Or that the lease should expire immediately if the leader unit goes into error?"
1774960,2018-07-08 22:53:04 UTC,"Reading the second paragraph more carefully it sounds like you mean the former, is that right?"
1774960,2018-07-09 03:22:36 UTC,"The uniter keeps renewing the lease, and the unit remains leader despite being in an error state."
1774967,2018-06-05 19:05:54 UTC,"Changed from wishlist to bug.  If we're going to have an ""Update PCB"" feature, then it probably needs to handle this."
1774967,2019-08-09 21:29:28 UTC,Demoting to Low as this doesn't appear to come up much in practice.
1774967,2018-06-05 21:29:51 UTC,Pushing to 6.0 as I think making any change here is too risky for 5.0RC.
1774967,2018-06-05 19:04:42 UTC,"A named net is certainly the ""gold standard""."
1774967,2018-06-04 17:42:26 UTC,"Yes, but correct pads' net is now Net-(J2-Pad1) and zone remained connected to Net-(J1-Pad1). The only change in PCB is reference swap, footprints stays in place, so traces and zones should stay attached to those footprints. Only traces does, see in screen record."
1774967,2018-06-04 18:42:30 UTC,@Patrik-
1774967,2018-06-04 16:03:51 UTC,Refilling the zones connects the correct zone to the correct pad.  Live zone updates would address thing but it needs to be a user option to allow it.
1774975,2018-06-05 08:35:24 UTC,"There were quite a few changes regarding tempest stability, in the last days:
https://review.openstack.org/570374
https://review.openstack.org/570670
https://review.openstack.org/570329
https://review.openstack.org/570160
So this issue may have already been fixed, lets keep track if this recreates."
1774975,2018-06-18 07:35:07 UTC,"Reviewed:  https://review.openstack.org/575442
Committed: https://git.openstack.org/cgit/openstack/vitrage-tempest-plugin/commit/?id=e802f1256600cb7021d45911c6f0fecd4f3369c2
Submitter: Zuul
Branch:    master"
1774981,2018-06-04 12:17:53 UTC,"Note this isn't just a widget issue, because it happens if you use the Audio Volume Settings. But it does seem to be a KDE issue, as it doesn't happen if you use ""pacmd set-default-sink"" directly."
1774982,2018-06-07 19:28:08 UTC,do you have libgbm1 installed?
1774982,2018-06-07 20:29:25 UTC,"Yes,"
1774982,2018-08-07 04:17:33 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1774982,2018-09-12 19:54:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1774985,2020-05-04 16:02:14 UTC,Edge cases:
1775011,2020-11-23 12:26:42 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1775020,2020-08-23 10:32:14 UTC,The package percona-xtradb-cluster-5.7 should use the libraries from galera-3 and not ship it's own version of it.
1775041,2018-06-05 06:37:03 UTC,Tagging as lint.
1775041,2018-06-05 06:36:36 UTC,I can confirm hitting the same error this morning.
1775042,2018-06-04 17:50:35 UTC,"Just a note, the ZNC package in Ubuntu is based on the ZNC package in Debian.  That package was not written by-default to behave as a system service, unlike other distributions where they give you that option.  This may ultimately need to be sent up to Debian for proper handling at the package level."
1775042,2019-08-19 16:12:58 UTC,Package version 1.7.4-2 includes a .service file.
1775045,2018-06-13 20:35:53 UTC,No further problems and updated several time since.
1775055,2018-06-05 18:09:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775055,2018-06-05 18:10:09 UTC,I am facing the same problem. Please help
1775061,2018-06-10 04:41:33 UTC,"ack to changing - also agree with comments and you're suggestions eg ""testcase leaves a lot of windows open, not asking the tester to close them"" - lets leave the user with a desktop in the state it was before they tested - close up everything ( killall orage in a term should do it - checking that they don't actually use it of course )"
1775065,2018-06-05 17:15:25 UTC,apport information
1775065,2018-06-05 17:15:28 UTC,apport information
1775065,2018-10-02 11:31:08 UTC,"I have an Omen by HP 15-dc0015np. This device have the same insue but only have a nvidia card, so doens't support to use intel video card to fix temporaly backlight. The solution above doens't work on me and use acpi_osi= or acpi_backlight=vendor or acpi_backlight=video or acpi_osi=! acpi_osi='Windows 2015' or acpi=off. Regards."
1775065,2018-10-12 20:32:35 UTC,Hi! I have an Omen by HP 15-ce004la with NVIDIA GTX1060 Q-MAX and the bug is still present.
1775065,2019-01-11 12:40:14 UTC,"Sorry,"
1775065,2018-11-24 15:14:08 UTC,"Got a similar problem on a HP Zbook G5. I have 2 graphics cards: Intel + Nvidia.
I use the Nvidia proprietary drivers 415. The difference in my case is that I have an entry in ""/sys/class/backlight"", namely: ""intel_backlight"" and that I can control the display brightness using the gnome GUI slider, but also my backlight hotkeys are not working and none of the following kernel parameters solved the issue:
    ""acpi_backlight=vendor""
    ""acpi_backlight=video""
    ""acpi_backlight=video0""
    ""acpi_backlight=none""
    ""acpi_osi=Linux""
Since many people are experiencing this annoying bug, it would really be great if it could be solved.
Anyhow, thanks for any of your efforts to solve this issue!"
1775065,2018-11-24 15:16:08 UTC,"Forgot my setup infos:
######################
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic"
1775065,2018-12-04 02:50:24 UTC,"I'm also facing same issue in Ubuntu 18.04.
Manufacturer: HP Omen
Graphics Card: Nvidia GTX 1060"
1775065,2018-06-05 17:15:22 UTC,apport information
1775065,2018-10-23 09:44:50 UTC,"I can confirm this very same problem in my laptop, which is a Thinkpad P1 with a Xeon E-2176M and hybrid Intel / NVIDIA card working in ""Discreet"" mode (that is, only the NVIDIA card is enabled) using the proprietary NVIDIA driver installed via the nvidia-driver-390 package (390.87-0ubuntu1)."
1775065,2018-06-05 17:15:21 UTC,apport information
1775065,2019-01-11 12:34:57 UTC,"I have bought a new laptop and downloaded the latest LTS version of Ubuntu. When I tried to install the dual boot for the first time, it failed, then after adding ""nomodeset"" to the grub menu I managed to install the same. But after installation there is no gui brightness control as well as the brightness button is not working. I tried a lot of methods to fix this, but none worked. Bellow is my system info:"
1775065,2018-06-05 17:15:18 UTC,apport information
1775065,2018-06-05 17:15:20 UTC,apport information
1775065,2018-06-05 16:35:08 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1775065,2018-06-05 16:50:56 UTC,"Yes, this was after an upgrade to Ubuntu 18.04 LTS (Bionic Beaver) from Ubuntu 17.10.1 (Artful Aardvark)."
1775065,2018-06-05 17:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775065,2018-06-05 17:06:25 UTC,"Yes, this was after an upgrade to Ubuntu 18.04 LTS (Bionic Beaver) from Ubuntu 17.10.1 (Artful Aardvark)."
1775065,2018-06-05 17:15:08 UTC,apport information
1775065,2018-06-04 19:53:18 UTC,"Although step 3 at https://wiki.ubuntu.com/Kernel/Debugging/Backlight asks for the output of ls /sys/class/backlight, it gives no output, so I do not include an attachment.  Steps 9, 10, and 12–16 either cause no changes or do not apply.  Step 11, as noted, is a workaround."
1775065,2018-06-05 17:15:11 UTC,apport information
1775065,2018-06-05 17:15:13 UTC,apport information
1775065,2018-06-05 17:15:17 UTC,apport information
1775065,2018-06-05 17:15:14 UTC,apport information
1775065,2018-06-05 17:15:16 UTC,apport information
1775065,2018-06-05 17:15:09 UTC,apport information
1775067,2019-11-22 20:53:21 UTC,"I too found this bug with Ubuntu 18.04 LTS on Nvidia Jetson TX2 system.
Running ffplay :"
1775067,2018-10-29 22:28:25 UTC,I too am having this problem with Ubuntu 18.04 LTS on an amd64 system.
1775067,2020-12-23 14:54:23 UTC,This is also an issue on Jetson Nano Ubuntu 18.04.5 LTS system.
1775067,2018-06-17 07:31:44 UTC,"One of our users just reported having exactly the same problem. The conditions and error are the same, SDL2 and Ubuntu 18.04 32-bit. See https://github.com/colobot/colobot/issues/1178"
1775067,2018-06-17 07:27:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775067,2018-06-07 16:53:18 UTC,Hey i think im having the same problem not sure.
1775067,2018-09-21 10:26:00 UTC,"This still happens with
libsdl2-2.0-0:i386 2.0.8+dfsg1-1ubuntu1.18.04.1"
1775067,2018-06-27 06:28:27 UTC,Can you please try with libsdl2 in -proposed pocket? and update https://bugs.launchpad.net/bugs/1772471 if you still have this issue
1775068,2018-10-25 08:04:34 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1775068,2018-10-02 15:21:45 UTC,apport information
1775068,2018-10-02 15:21:46 UTC,apport information
1775068,2018-10-02 15:21:48 UTC,apport information
1775068,2018-10-02 15:21:49 UTC,apport information
1775068,2018-10-02 15:21:51 UTC,apport information
1775068,2018-10-03 06:25:11 UTC,"Please test the kernel here:
https://people.canonical.com/~khfeng/lp1775068/"
1775068,2018-10-03 16:04:06 UTC,"Kernel tested.
It's working now!"
1775068,2018-10-04 03:41:14 UTC,https://lkml.org/lkml/2018/10/4/157
1775068,2019-08-13 11:27:47 UTC,This bug was fixed in the package linux - 4.15.0-58.64
1775068,2018-11-08 13:30:46 UTC,"Hi @kaihengfeng,"
1775068,2018-11-08 17:22:00 UTC,"Hi,"
1775068,2018-11-13 17:53:26 UTC,This bug was fixed in the package linux - 4.4.0-139.165
1775068,2018-11-15 11:04:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1775068,2018-11-18 13:17:29 UTC,Default install Xenial 16.04.
1775068,2018-12-03 08:49:32 UTC,This bug was fixed in the package linux - 4.18.0-12.13
1775068,2019-02-14 12:11:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1775068,2019-08-09 16:54:37 UTC,"Hi Wojciech,"
1775068,2018-10-02 15:21:44 UTC,apport information
1775068,2018-11-07 16:19:58 UTC,"Hi @trolinka,"
1775068,2018-10-02 15:21:41 UTC,apport information
1775068,2018-11-08 06:21:46 UTC,I think trolinka uses Bionic but the patch lands at Xenial through upstream stable update.
1775068,2018-10-02 15:21:38 UTC,apport information
1775068,2018-10-01 06:09:49 UTC,1. Does the volume slider in the system menu work?
1775068,2018-10-01 15:54:53 UTC,apport information
1775068,2018-10-01 15:54:54 UTC,apport information
1775068,2018-10-01 15:54:55 UTC,apport information
1775068,2018-10-01 15:54:56 UTC,apport information
1775068,2018-10-01 15:54:57 UTC,apport information
1775068,2018-10-01 15:54:58 UTC,apport information
1775068,2018-10-02 15:21:39 UTC,apport information
1775068,2018-10-01 15:55:42 UTC,apport information
1775068,2018-10-01 15:55:42 UTC,apport information
1775068,2018-10-01 15:55:40 UTC,apport information
1775068,2018-10-01 15:55:45 UTC,apport information
1775068,2018-10-02 15:21:37 UTC,apport information
1775068,2018-10-01 15:55:44 UTC,apport information
1775068,2018-10-02 15:21:35 UTC,apport information
1775068,2018-10-02 15:21:33 UTC,apport information
1775068,2018-10-02 15:21:36 UTC,apport information
1775068,2018-10-02 15:21:30 UTC,apport information
1775068,2018-10-02 03:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775068,2018-10-01 16:00:58 UTC,"Hi,"
1775068,2018-10-01 15:55:47 UTC,apport information
1775068,2018-10-02 15:21:31 UTC,apport information
1775068,2018-06-04 21:53:38 UTC,"inxi -A
Audio:     Card-1 Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 580]
           driver: snd_hda_intel
           Card-2 Intel Sunrise Point-H HD Audio driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.15.0-22-generic"
1775071,2018-06-04 20:36:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572208"
1775071,2018-07-27 13:15:45 UTC,This issue was fixed in the openstack/glance 17.0.0.0b3 development milestone.
1775074,2018-06-04 22:22:55 UTC,Also per https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1775086 /var/lib/cloud/instance may not yet exist in error'd environments.
1775087,2018-10-31 10:09:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775087,2018-10-31 10:48:50 UTC,https://bugs.python.org/issue33432 it's a upstream problem
1775087,2018-10-31 16:09:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775089,2019-08-10 13:19:52 UTC,I think I found workaround for this problem - (non-standard) build fuse-sdl but without sdlsound.c and use alsasound.c instead.
1775089,2018-07-28 05:02:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775094,2018-06-04 23:37:29 UTC,New to keystone and started by creating a VM and running the guide here:
1775094,2018-06-04 23:52:28 UTC,A separate documentation note that caught me by surprise was the removal of LDAP write support. It's the second sentence is this paragraph:
1775094,2018-06-04 23:57:39 UTC,O'Rielly book mentioned in previous comment:
1775094,2018-06-05 14:25:18 UTC,Please feel free to use the information in the presentation that Henry and I did:
1775094,2018-06-16 13:57:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575911"
1775094,2018-06-29 13:17:19 UTC,"Reviewed:  https://review.openstack.org/575911
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d054c9a5ac3aeb9a076c1089a2b5645fca0f3d3b
Submitter: Zuul
Branch:    master"
1775095,2018-07-07 22:35:36 UTC,"Hi David, I'm back from vacation."
1775095,2018-07-10 21:41:27 UTC,"https://github.com/mixxxdj/mixxx/pull/1675
Seen your progress, however it's most abracadabra to me. Thanks!"
1775095,2018-07-10 21:55:18 UTC,Is there anything for Linux? The file listener is implemented and the only thing left is to test it.
1775095,2018-07-11 06:43:50 UTC,"I'll try to find something in vbox, takes some time however"
1775095,2018-07-11 16:07:09 UTC,"DarkIce must do the same as AltaCast in Windows however no metadata support.
https://github.com/rafael2k/darkice
IceCast does have such function, though it is an audio server
https://icecast.org/docs/icecast-trunk/admin_interface/
Ices is an input module for IceCast, it can handle metadata
https://icecast.org/ices/docs/ices-2.0.1/inputs.html"
1775095,2018-07-11 21:09:11 UTC,"Butt will also do the job
http://danielnoethen.de/manual.html
see 6 streaming section"
1775095,2018-09-27 18:22:26 UTC,in progress see; https://github.com/mixxxdj/mixxx/pull/1675
1775095,2019-12-16 23:45:38 UTC,https://vitux.com/compiling-your-first-qt-program-in-ubuntu/ quite an challenge to me...
1775095,2019-12-16 23:11:27 UTC,<quote>The original issue can be fixed by setting a different Window Class than the default.</quote>
1775095,2019-12-16 23:26:56 UTC,https://doc.qt.io/qt-5/qxmlstreamwriter.html could maybe useful
1775095,2019-12-17 07:17:04 UTC,"Here is a pretty straight forward guide to build Mixxx on Linux.
https://www.mixxx.org/wiki/doku.php/compiling_on_linux"
1775095,2020-06-01 10:02:10 UTC,"Issue solved probably during recent changes in QT name assignment for windows.
There are now only two same assignments. Preferences and the main window."
1775095,2020-06-11 21:14:23 UTC,"I was a bit to eager. It wasn't fixed in the Deere skin, there were 5 same named windows..."
1775095,2020-06-11 21:30:07 UTC,"I'm using the Tango skin on mixxx-2.4.0-alpha-pre-master-git7412-release-x64, win 10 pro"
1775095,2018-06-26 15:44:06 UTC,"I would like to test my code with a streaming service that allows files to input metadata. However, AltaCast is for Windows and I don't want to subscribe to SAM Broadcaster. Is there anything for Linux that's free / open source?"
1775095,2019-09-14 23:29:53 UTC,The original issue can be fixed by setting a different Window Class than the default.
1775095,2018-06-18 18:22:40 UTC,"We can summarize that AltaCast users are probably Western users.
For Windows I was happy to find a free gui-based streamer with metadata capabilities, they are rare.
Utf8 will cover most of its users."
1775095,2018-06-06 21:05:45 UTC,"@ David; found a Python script for MPRIS in Clementine, ok for Linux, Windows don't use dbus"
1775095,2018-06-10 13:27:02 UTC,screenshot SAM
1775095,2018-06-05 16:46:18 UTC,We are currently implementing more metadata output. I consider trading the window title as an ugly havk. Which other interfaces can be used by AltaCast? To which one do you like to switch for Mixxx 2.2?
1775095,2018-06-06 14:25:27 UTC,Does Altacast let you use a file to grab the metadata? Or can it use the MPRIS interface?
1775095,2018-06-06 15:10:36 UTC,Why do you use a separate program to broadcast instead of broadcasting from Mixxx?
1775095,2018-06-10 13:56:03 UTC,"btw forgot most important one :-)
see attatchment"
1775095,2018-06-06 21:14:19 UTC,Could you file a separate bug for you effect request. Maybe we have already a LV2 solution in upcoming Mixxx 2.2 or we could integrate your needs natively...
1775095,2018-06-07 10:00:07 UTC,"@Peter, what format does the file have to be?"
1775095,2018-06-08 10:13:36 UTC,"@ David
I formerly used Sam Broadcaster, however they took another road.
They use a .txt file, see attachment"
1775095,2018-06-08 10:16:59 UTC,"@ Daniel
I will :-)"
1775095,2018-06-06 20:45:40 UTC,"@ Daniel; grabbing is ugly, but it did the job
@ David; a plain text file can be used, MPRIS is unknown to me
@ Be; I'm using Stereotool for compessing/expanding/enhancing etc. Routed by VBCable. DSP support would also be useful."
1775095,2018-06-08 14:08:37 UTC,"For writing to the file, I use QTextStream's operator << QString, which encodes the string with the locale codec. So if the author or the title are in Unicode I don't see a reason for it to not print non ASCII characters: http://doc.qt.io/qt-5/qtextstream.html#operator-lt-lt-12"
1775095,2018-06-08 15:25:24 UTC,"If the local8bit codec is latin1, you cannot print Cyrillic titles. I am not sure what is the default 8 bit codec in windows there is also cp848 or such things.
I know we had similar issues with m3u playlists. They are defined as latin1.
Because that does not work for any track, we have a successor that is m3u8 Wich is utf8.
Unfortunately the reader app cannot or hard distinguish utf8 from Latin one. If it fails, you get the famous ü.
If this is an issue, we need a preference option for the character encoding."
1775095,2018-06-08 22:17:40 UTC,"SAM can print umlauts but can't print Cyrillic.
In Cyrillic I get a string of questionmarks
see attatchment"
1775095,2018-06-09 12:05:32 UTC,"@Daniel, we an allow for the user to set the codec, no problem. However, if broadcast apps can read UTF-8, I think we should prefer that, because it allows for every language."
1775095,2018-06-09 14:51:41 UTC,"Yes, right. I am only afraid that the majority of windows apps expect latin1.
And I am also afraid that the evetage user does not know the difference between latin1 and utf8. The issue is that it can be only identified at runtime, when suddenly an umlauts track is played. This might be too late. How about add a test mode, sending a fake umlauts track and ask the user if it is decided right."
1775095,2018-06-09 15:58:45 UTC,"Maybe, but before all of that, shouldn't we need to know which encoding the broadcast app uses? It doesn't matter if the title is not displayed correctly if we don't know how to do it."
1775095,2018-06-09 16:26:46 UTC,"Yes, right. It is not utf8, because of the question marks in Peters file."
1775095,2018-06-10 13:25:01 UTC,"@ Daniel
The question marks are added by SAM when importing in its library
I made a tag with the string provided by you, the library (mySQL) can't print them, but the payers do and also the output-file do.
Two attachments"
1775095,2018-06-08 13:52:03 UTC,Can you provide a file with non ASCII characters like umlauts or Cyrillic cjaracters as well?
1775097,2018-07-16 15:16:06 UTC,"The verification of the Stable Release Update for nplan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1775097,2018-07-12 21:15:26 UTC,Verification-done on xenial: nplan/0.32~16.04.6:
1775097,2018-07-05 14:59:35 UTC,"Hello Mathieu, or anyone else affected,"
1775097,2018-06-15 00:06:30 UTC,Are they only flaky for Xenial? I ask as that's the only release I see an upload for.
1775097,2018-07-16 15:16:03 UTC,This bug was fixed in the package nplan - 0.32~16.04.6
1775100,2018-06-04 23:50:08 UTC,"Here's a gif showing what I mean.  It tells me to route the item to Reference, but it's checked out to the patron."
1775109,2018-06-05 03:24:17 UTC,"When filing bug reports, best practice is to file against the package. The bug is upstream of Ubuntu Studio."
1775109,2018-06-05 03:34:00 UTC,"Probably needs to be repackaged from GitHub source, though project seems to be largely unmaintained. Last commit was November 16, 2015. Issue seems to be related to this upstream bug: https://github.com/dsacre/mididings/issues/26"
1775109,2018-06-05 13:39:15 UTC,"Ok, I'll commit to mididings pj source.
thx!"
1775109,2020-04-10 19:54:17 UTC,The mididings package has been removed from Ubuntu Focal.
1775111,2018-06-16 21:34:34 UTC,"Fixed upstream in https://gitlab.gnome.org/GNOME/gnome-terminal/commit/6ec754bf. Will be included in gnome-terminal 3.28.3, whenever (if at all) released (there's no schedule for that)."
1775111,2018-06-05 10:23:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775111,2018-06-05 10:28:35 UTC,"Confirmed. Thanks for the report, forwarded upstream: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/4."
1775111,2018-06-05 01:50:46 UTC,"Aha: note this only happens if you *first* type the uppercase search string, *then* click ""Match case""; if ""Match case"" is selected first, option operates as expected"
1775126,2018-06-11 06:40:37 UTC,The warning message isn't harmful and should not cause hang. This should be a pure Gnome bug.
1775126,2018-06-05 07:42:47 UTC,apport information
1775126,2018-06-05 07:42:46 UTC,apport information
1775126,2018-06-05 07:42:43 UTC,apport information
1775126,2018-06-05 07:42:42 UTC,apport information
1775126,2018-06-05 07:42:41 UTC,apport information
1775126,2018-06-05 07:42:40 UTC,apport information
1775126,2018-06-05 07:42:39 UTC,apport information
1775126,2018-06-05 07:42:38 UTC,apport information
1775126,2018-06-05 07:42:44 UTC,apport information
1775126,2018-06-05 07:42:36 UTC,apport information
1775126,2018-06-05 06:40:07 UTC,"The mouse movement in Wayland sessions is quite different to Xorg sessions, and less efficient as it seems to incur screen redraws."
1775126,2018-06-05 07:42:37 UTC,apport information
1775126,2018-06-05 07:14:50 UTC,It seems this bug is actually related to this one: https://bugzilla.redhat.com/show_bug.cgi?id=1564908
1775126,2018-06-05 07:25:28 UTC,"After disabling the HDMI sound card, I only get this line, accompanied by a short freeze."
1775126,2018-06-05 07:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775126,2018-06-05 07:10:58 UTC,Thank you. I do think this is a different issue though.
1775126,2018-06-05 07:42:30 UTC,apport information
1775126,2018-06-05 07:42:31 UTC,apport information
1775126,2018-06-05 07:42:33 UTC,apport information
1775126,2018-06-05 07:42:35 UTC,apport information
1775126,2018-06-05 07:31:48 UTC,OK. This is now a kernel bug.
1775131,2019-04-16 12:27:16 UTC,"Your logs do not show network dispatcher restarting, but it is reloading it's list of interfaces as it has to figure out which interface it got notified about."
1775131,2021-01-25 08:56:37 UTC,Also happening on 20.04
1775131,2019-09-18 11:39:36 UTC,"i have the same problem over here, i posted more details over here:
https://github.com/mailcow/mailcow-dockerized/issues/2918"
1775131,2019-04-17 06:14:31 UTC,"Summing UP all Above comments:
----------------------------"
1775131,2019-04-16 13:12:43 UTC,"problem occurs when both interface created using multiprocessing module of python
----------------
Process 1 execution ->
ip link add link ens34 2icx0 type macvlan
ifconfig 2icx0 up
ip addr add 192.168.49.230/16 dev 2icx0"
1775131,2019-04-16 12:29:25 UTC,"Anyhow, none of this is a bug I nthe dispatcher, and I don't know what else, so I'm going to reassign it to the kernel - if there are broken ARP tables and whatnot, what else could it be."
1775131,2019-04-16 11:49:53 UTC,"this scenario is: i need to create 1000 of virtual interface , this is scale environment, where each new interface causing restart of networkd-dispatcher, losing out on older interface, if there creation is not completed successfully."
1775131,2019-04-16 12:13:55 UTC,"Failed Logs:
------
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30948]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30948]: Could not generate persistent MAC address for 2icx0: No such file or directory
Apr 16 10:56:27 u18_svr_madsz systemd-networkd[22168]: 2icx0: Gained carrier
Apr 16 10:56:27 u18_svr_madsz networkd-dispatcher[824]: WARNING:Unknown index 71 seen, reloading interface list
Apr 16 10:56:27 u18_svr_madsz systemd-timesyncd[22214]: Network configuration changed, trying to establish connection.
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30960]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30960]: Could not generate persistent MAC address for 2icx1: No such file or directory
Apr 16 10:56:28 u18_svr_madsz systemd-networkd[22168]: 2icx1: Gained carrier
Apr 16 10:56:28 u18_svr_madsz networkd-dispatcher[824]: WARNING:Unknown index 72 seen, reloading interface list
Apr 16 10:56:28 u18_svr_madsz systemd-networkd[22168]: 2icx0: Lost carrier
Apr 16 10:56:28 u18_svr_madsz systemd-timesyncd[22214]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
Apr 16 10:56:29 u18_svr_madsz systemd-networkd[22168]: 2icx1: Gained IPv6LL"
1775131,2019-04-13 00:26:54 UTC,"networkd-dispatcher, on its own, does not configure or control network interfaces. It listens on d-bus for events from systemd-networkd. So this is almost certainly a symptom rather than the cause of your interface stability issues, *unless* you have given networkd-dispatcher some script to execute that controls interfaces. If that's the case, you should probably not do that, since it would cause all sorts of hard-to-debug issues :)"
1775131,2019-01-10 16:09:12 UTC,"@Julian - As no one seems to be doing that, I'll take the initiative and give you the information instead."
1775131,2018-12-14 04:17:22 UTC,[Expired for networkd-dispatcher (Ubuntu) because there has been no activity for 60 days.]
1775131,2018-10-14 16:09:24 UTC,Hard to admit but we had a totally different culprit: A conflict between hardware clock and NTP sync caused dhclient dropping the interface probably »believing« lease timeout being reached.
1775131,2018-10-10 18:11:21 UTC,"Hello,"
1775131,2018-10-03 07:31:13 UTC,The networkd-dispatcher errors are not causing your connection issues - networkd dispatcher just starts scripts after network changes. I wonder if the connection issues are causing the networkd-dispatcher issues.
1775131,2018-06-05 08:25:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1775131,2018-09-27 16:16:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775131,2019-04-16 11:32:49 UTC,"Ubuntu:
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic"
1775137,2018-08-02 16:03:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1775137,2018-08-23 21:59:21 UTC,This bug was fixed in the package linux - 3.13.0-157.207
1775137,2018-06-13 11:03:41 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1775137,2018-06-05 08:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775137,2018-07-02 08:29:08 UTC,This bug was fixed in the package linux - 4.4.0-130.156
1775143,2018-06-05 14:34:02 UTC,What do you mean by this? https://bugs.launchpad.net/inkscape/+bug/1775143/comments/10
1775143,2018-06-05 14:32:41 UTC,Did it! My inkscape version is Inkscape 0.92.3 and im working on Windows 8.1.
1775143,2018-06-05 14:35:32 UTC,I dont want my project file to be seen by everyone so can i sent you a link in private via email or something?
1775143,2018-06-05 13:27:53 UTC,help us to help you
1775143,2018-06-05 15:36:16 UTC,"attached is an example of a svg file with a linked image in it. In this case I have deliberately modified the link so that it is no longer valid. So as a result I get the linked image message that you are getting. In the file there is a section called <image> which is shown below. You will need to find this section in your file and confirm that it refers to a valid file. The line called
sodipodi:absref
and the line called
xlink:href
should refer to existing image files on your machine. If they do not, then edit them so that they do refer to existing files. You can use Inkscape to do this editing or you can use something like Notepad. As long as you do _not_ use Word, because it will reformat everything in your file. In any event make a backup of your svg file before you try to edit it by hand.
.............................................................."
1775143,2020-03-28 19:49:18 UTC,Closing because INVALID: support request.
1775143,2018-06-05 14:56:34 UTC,someone please help i need my project
1775143,2018-06-05 13:26:24 UTC,Please chage bug description to some thing descriptive and useful to other users and don't write in uppercase ;) Also provide system changes like files moved or not or inkscape version changed or anything can help us.
1775143,2018-06-05 13:23:44 UTC,"You can't confirm the bug need be other person, back to new."
1775143,2018-06-05 08:27:08 UTC,I did not use a image i was just drawing. on most things so i dont get why every thing is gone. i used some images but they are all still there.
1775143,2018-06-05 08:28:26 UTC,http://prntscr.com/jr0qhd
1775143,2018-06-05 11:56:03 UTC,"Hi Dennis, could you say what put in object dialog URL: Field?
To know select the red broken image, right cliick and press image propieties.
You have this file in this location?
Regards and sorry for my english."
1775143,2018-06-05 12:48:27 UTC,Nothing happens so weird i didnt import an image in like a week so its really stupid. But i really need this project.
1775143,2018-06-05 13:00:39 UTC,Please do the steps required and check for the URL. Alternativaly can do the work for you but need original file shared.
1775143,2018-06-05 13:22:33 UTC,"Also put your inkscape version, SO and if posibol attach the file."
1775143,2018-06-05 13:05:04 UTC,Maybe if you remove the broken image your proyect show?
1775143,2018-06-05 13:05:31 UTC,Im away for a while like and hour and a half so if i dont respond u know why.
1775143,2018-06-05 13:07:33 UTC,No if i remove it nothing happens the image is just gone.
1775143,2018-06-05 13:21:14 UTC,Just ro try... back to https://bugs.launchpad.net/inkscape/+bug/1775143/comments/5 and https://bugs.launchpad.net/inkscape/+bug/1775143/comments/6
1775143,2018-06-05 13:03:53 UTC,What do you mean do i have to send the file to you? Its okay with me. When i right click and push the button for image propperties nothing happens and i don't know what image it is. ;/
1775144,2019-04-23 10:03:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775144,2019-12-13 14:52:53 UTC,Fixed in mkvtoolnix 35.0.0-1
1775144,2019-04-23 10:23:23 UTC,"There are many conflicts between the mkvtoolnix packages from official Ubuntu repositories and those provided by upstream dev (~bunkus). Some discussions are required to fix them[1]... In the time between, please always manually remove them before to switch to those from the other source."
1775148,2019-10-18 09:39:25 UTC,"I initially thought that this would be a simple matter of not crashing when you unset the default branch, but on closer inspection I see that it isn't actually possible to unset the default branch in a git repository: the obvious git operations refuse when you try, and if you hack it directly out of the repository then you get something that doesn't count as a repository any more.  So this code path needs to raise a proper exception rather than crashing, but we also need to mark the default branch as required on the webservice API."
1775148,2019-11-08 16:30:03 UTC,"Just a note that the form field still displays ""(Optional)"".
But the form correctly errors if no input is provided."
1775148,2020-03-11 08:47:17 UTC,@cjwatson FTR https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas has no branch.
1775149,2018-06-05 09:41:13 UTC,"The root cause is when zcc trying to get guest console via vmur, another vmur instance is running."
1775152,2018-06-27 07:11:18 UTC,"This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'."
1775152,2018-06-27 14:52:54 UTC,"Reboot several times, not seeing this issue anymore."
1775153,2019-09-19 09:47:03 UTC,The attached is a backported patch for fanotify09 for trusty kernel. The test result was improved (as below) but it doesn't eliminate all failures.
1775153,2019-07-10 08:58:17 UTC,The timeout in X was caused by some other failures in previous tests.
1775153,2018-11-29 11:23:44 UTC,Looks like this issue does not exist in T-AWS as well
1775153,2018-06-22 08:53:48 UTC,"On Xenial, this test will time out as well, but with slightly different error message:"
1775153,2018-11-22 07:22:05 UTC,"For the fanotify09 test with Bionic kernel, it's now failing with another new test case landed 2 days ago: bug 1804594"
1775153,2018-07-24 09:34:52 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1775153,2018-06-05 10:00:12 UTC,This change was made by a bot.
1775159,2018-06-13 05:43:32 UTC,Code merged.
1775159,2018-06-07 07:30:05 UTC,"Fix submitted here
https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/414118"
1775162,2018-06-05 11:57:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775162,2018-06-05 12:47:51 UTC,"That also affected ocserv:
https://gitlab.com/ocserv/ocserv/issues/152"
1775162,2018-06-09 06:48:11 UTC,"Related commits:
https://gitlab.com/gnutls/gnutls/commit/af09650c5b48ff0bce41007e588c2838d8e2a0be
https://gitlab.com/gnutls/gnutls/commit/c59df1554b55748ea95ad1a89a6bcb6ab91963d2"
1775164,2018-06-05 13:06:59 UTC,"We originally had a cubic interpolation in Mixxx which was considered as sound not better.
https://github.com/mixxxdj/mixxx/commit/21c869ccc1065ab2dcfda7d138a5119cbeb203b3"
1775164,2018-06-05 13:55:39 UTC,"Ok, Soundtouch uses it's own cubic interpolation.
Rubberband uses libsamplerate by default with a sinc interpolator. SRC_SINC_FASTEST."
1775164,2018-06-05 14:03:18 UTC,"The scalers are selected here:
https://github.com/mixxxdj/mixxx/blob/c241ae5c2adb40fde92c2cc7e342973c31663410/src/engine/enginebuffer.cpp#L249"
1775164,2018-06-05 14:08:27 UTC,"""Ok, Soundtouch uses it's own cubic interpolation.
Rubberband uses libsamplerate by default with a sinc interpolator. SRC_SINC_FASTEST."""
1775164,2018-06-05 14:21:21 UTC,"Not managed to find the different Scalers, or not one that seems to use interpolation rather than change play_pos (probably due to not being used to the code and have zero C++ skills) but I did come across this comment:"
1775164,2018-06-05 17:49:25 UTC,"There is also the question after group delay, that may be an issue when scratching.
I think we need to distinguish one case more in the future.
* Scratching
* Linear interpolation for sample rate adjusting and vinyl speed changes
* Keylock/Keyschift"
1775164,2018-06-05 20:08:26 UTC,"DO you mean add an internal switch so that Mixxx will automatically switch between a method optimised for Scratching under certain conditions and then use the user selected mode at other times, which itself depends on whether Key Lock is active or not?"
1775164,2018-10-03 12:35:54 UTC,"Have you considered trying libzita-resample? Their claims are to be faster and better quality than libsamplerate and on the whole my experience with all the Zita tools is pretty positive. Something makes me think you don't use single-precision floats in the audio engine though, so it might not be suitable at all....."
1775164,2021-01-04 12:05:38 UTC,We may add a new comobox:
1775164,2018-06-05 14:02:13 UTC,"SoundTouch, being a frames based method of timestrectch, I really don't think would work well at all. The only way I could imagine RubberBand doing it would be double processing, first timestretching as normal, then pitchshifting to the pitch it should be. I could well be wrong but if that's the case that would be an excessive amount of processing to achieve this!"
1775165,2019-07-15 02:29:45 UTC,"Hi Matthew,"
1775165,2019-08-23 08:56:34 UTC,"Test blacklisted for older kernels
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=1e99a9a95ba6e99440b46b9f0911fbd63d4dc95f"
1775165,2019-07-10 21:30:21 UTC,"Hi Po-Hsu Lin,"
1775165,2018-06-22 07:20:02 UTC,This timeout issue could be found on X-generic / X-AWS as well.
1775165,2019-04-10 03:34:25 UTC,I have gone ahead and backported the fixes for xenial's 4.4 kernel.
1775165,2018-06-21 10:29:42 UTC,From the comment in the test case:
1775165,2018-06-05 12:00:07 UTC,This change was made by a bot.
1775165,2019-07-10 09:08:09 UTC,It turns out the culprit is fanotify07.
1775167,2018-06-05 12:02:13 UTC,"I just found this:
https://github.com/oerdnj/deb.sury.org/issues/714"
1775170,2018-06-12 00:52:24 UTC,@corey
1775170,2018-07-25 19:18:31 UTC,I've also given an ocata-proposed deployment some manual testing and it looks good.
1775170,2018-07-25 19:18:48 UTC,The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1775170,2018-10-03 18:16:30 UTC,This particular bug of the container creation modal being blank has plagued us for several OpenStack releases now. We are running Queens on Ubuntu 16.04 currently (http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/queens/main amd64 Packages)
1775170,2018-10-03 18:45:36 UTC,"Hi Jared,"
1775170,2018-10-03 19:49:23 UTC,We implement the following customizations of the openstack-horizon dashboard:
1775170,2018-10-03 20:02:05 UTC,"Just to be clear, I've tried removing the following directories"
1775170,2018-07-24 02:21:49 UTC,"Hello corey,"
1775170,2018-10-03 20:23:11 UTC,You might also try re-running the post-install script after the package is installed and after you've added your customizations:
1775170,2018-10-04 15:00:50 UTC,I don't think it's necessary to go through the process of a pike -> queens upgrade to reproduce the issue. Reason I say that is because we can take our current install and purge & install the openstack-dashboard & related packages and without our customizations we still experience the problem. That being said we are unable to reproduce this issue from a fresh install in our lab environment by taking a fresh ubuntu 16.04 install and layering on the openstack packages. This has been good and bad. Bad because we are unable to reproduce the issue in our lab. Good because we can take this working environment and copy the dynamically generated javascript files from '/var/lib/openstack-dashboard/static/dashboard/js' to our production environment so that the create container modal works properly.
1775170,2018-10-05 13:12:41 UTC,"It looks like you can use -v3:
  -v {0,1,2,3}, --verbosity {0,1,2,3}
                        Verbosity level; 0=minimal output, 1=normal output,
                        2=verbose output, 3=very verbose output"
1775170,2018-10-10 19:28:26 UTC,"Hey Corey,"
1775170,2018-10-10 21:04:08 UTC,I did a bit more investigating and it seems to me like the contents of the defined memcached server can influence the generation of the javascript in '/var/lib/openstack-dashboard/static/dashboard/js'
1775170,2018-10-11 13:35:17 UTC,"Good work finding that out, Jared. I think we need some input from upstream horizon developers to determine if this is an upstream bug or not. I'll add upstream horizon to this bug."
1775170,2018-06-11 14:26:36 UTC,"Hi Seyeong,"
1775170,2018-10-03 20:26:13 UTC,"Jared, If I were to recreate this without your additional customizations, would I need to upgrade from pike->queens or just install openstack-dashboard for queens, or something else?"
1775170,2018-07-17 05:40:43 UTC,"Hello,"
1775170,2018-07-25 19:18:50 UTC,"This bug was fixed in the package horizon - 3:11.0.4-0ubuntu1~cloud2.5
---------------"
1775170,2018-07-16 13:23:14 UTC,Please disregard comment #18.
1775170,2018-06-14 12:51:37 UTC,Hello Corey
1775170,2018-06-18 14:31:05 UTC,"Seyeong,"
1775170,2018-06-19 05:41:41 UTC,"Hello Corey,"
1775170,2018-07-16 13:59:43 UTC,"Hello Seyeong, or anyone else affected,"
1775170,2018-07-02 21:10:02 UTC,"I've just compared jquery.bootstrap.wizard.js files from 2 installations:
1) installed openstack-dashboard newton and upgraded to ocata
2) installed openstack-dashboard ocata"
1775170,2018-07-03 06:45:56 UTC,"right, source code itself doesn't have any differences ( if compare same file name )"
1775170,2018-07-06 02:00:52 UTC,"Seyeong, I took a look at this a bit today and was able to reproduce it. I think we can add the following. I'm curious if this exists for any other releases or if any similar issues exist elsewhere. Either way it seems like we'd want to fix this through for ocata and above."
1775170,2018-06-19 07:19:27 UTC,Hello Corey
1775170,2018-07-06 12:26:04 UTC,"Sorry, I wasn't referring to skipping a release on upgrade. I was referring to Ocata->Pike, Pike->Queens."
1775170,2018-07-09 06:26:17 UTC,"ah I see, will check ASAP"
1775170,2018-07-09 10:05:51 UTC,"Hello Corey,"
1775170,2018-07-16 11:15:52 UTC,"Hello, Could you please proceed this? or I can do it."
1775170,2018-07-16 13:20:16 UTC,"I've triaged this for all releases >= ocata. While there are no issues surfacing currently for any release other than ocata, it seems we should make this change in all releases >= ocata."
1775170,2018-07-16 13:23:01 UTC,"Actually, we only rm /usr/share/openstack-dashboard/static/ in <= ocata, so I think we can limit this fix to ocata, where we're seeing the issue."
1775170,2018-07-06 09:05:44 UTC,"Corey, Yes, possible."
1775170,2018-06-05 12:27:45 UTC,"The attachment ""lp1775170_ocata.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1775174,2018-07-17 19:08:05 UTC,The PG overdose prevention does not really help us with automated deployments; I'd really like to see a --yes-i-really-mean-it or a configurable fallback osd count in ceph itself to help us with this.
1775176,2018-06-05 13:35:13 UTC,"It looks like I got the commit sha1 wrong for the cause of the variable bleeding. I am not sure what commit introduced the usage of locals, but is for sure how we got into the decoding problem. We are fixing this on our end by sanitizing the variable before calling get_node_config"
1775187,2018-06-06 07:44:16 UTC,apport information
1775187,2018-11-10 10:50:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775187,2018-06-06 07:44:21 UTC,apport information
1775187,2018-06-06 07:44:20 UTC,apport information
1775187,2018-06-06 07:44:19 UTC,apport information
1775187,2018-06-06 07:44:18 UTC,apport information
1775187,2018-06-06 07:44:17 UTC,apport information
1775187,2018-06-06 07:44:13 UTC,apport information
1775187,2018-06-06 07:44:14 UTC,apport information
1775187,2018-06-06 01:42:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1775187,2018-06-06 07:44:07 UTC,apport information
1775187,2018-06-06 07:44:15 UTC,apport information
1775187,2018-06-06 07:44:11 UTC,apport information
1775187,2018-06-06 07:44:12 UTC,apport information
1775187,2018-06-06 07:44:10 UTC,apport information
1775195,2018-11-26 16:20:52 UTC,This bug was fixed in the package sosreport - 3.6-1ubuntu0.16.04.2
1775195,2018-11-16 00:16:48 UTC,"[ VERIFICATION XENIAL ]
libvirt VM:"
1775195,2018-12-18 18:51:23 UTC,Reopening Trusty as it will be supported in ESM for a while yet.
1775195,2018-11-16 00:30:10 UTC,"[ VERIFICATION COSMIC ]
libvirt VM:"
1775195,2018-11-16 03:33:09 UTC,"Bryan,"
1775195,2018-11-16 04:39:53 UTC,"I'm on 18.04 (I would assume this would not affect older releases)
I previously installed rasdaemon and started it.   That's all it took to trigger it on Fedora - https://github.com/sosreport/sos/pull/1445"
1775195,2018-11-16 04:40:16 UTC,(I would assume this would not affect older releases ... as they use mcelog not rasdaemon.)
1775195,2018-11-16 13:34:11 UTC,"I was able to reproduce the situation and did a kernel bisection to confirm, and it reveals that you were right :"
1775195,2018-11-16 14:06:31 UTC,"[d6379b5ba0f381ea8ec2403b9985100a946a5866] fix has been push into disco, stable release will follow soon."
1775195,2018-11-16 00:15:10 UTC,"Eric, unfortunately - I'm getting a hang in kernel now - I installed rasdaemon to debug a customer case... between when I tested last..."
1775195,2018-11-20 13:15:32 UTC,"Hello Eric, or anyone else affected,"
1775195,2018-11-20 13:22:41 UTC,"Hello Eric, or anyone else affected,"
1775195,2018-11-20 13:26:31 UTC,"Hello Eric, or anyone else affected,"
1775195,2018-11-20 13:36:53 UTC,"Bryan Quigley (bryanquigley) ,"
1775195,2018-11-26 16:20:24 UTC,"The verification of the Stable Release Update for sosreport has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1775195,2018-11-26 16:20:41 UTC,This bug was fixed in the package sosreport - 3.6-1ubuntu0.18.04.2
1775195,2018-11-26 16:30:28 UTC,This bug was fixed in the package sosreport - 3.6-1ubuntu0.18.10.2
1775195,2018-11-16 15:58:56 UTC,Bug #1803735 has been reported to track the kernel plugin bug.
1775195,2018-11-16 00:14:23 UTC,"[ VERIFICATION BIONIC ]
Bare metal:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION=""Ubuntu 18.04.1 LTS"""
1775195,2018-11-15 21:56:14 UTC,Correction I for my above statement ^ I I ran sosreport '3.6-1ubuntu0.16.04.1' for Xenial.
1775195,2018-10-03 22:14:49 UTC,Quick update....
1775195,2018-11-05 18:33:51 UTC,"This bug was fixed in the package sosreport - 3.6-1
Sponsored for Eric Desrochers (slashd)"
1775195,2018-11-09 20:46:59 UTC,"I ran sosreport -a on bionic with maas 2.4, corosync, pacemaker and postgres all in a very unhappy state.  The output looks good. During execution I recieved the following:"
1775195,2018-11-09 21:53:16 UTC,Testing results:
1775195,2018-11-12 17:15:58 UTC,Ran test in Xenial LXD container:
1775195,2018-11-13 17:49:14 UTC,I'm setting this to Incomplete based on comment #6 and the possibility of a password being leaked.
1775195,2018-11-13 20:15:05 UTC,"Hi Dave,"
1775195,2018-11-15 21:56:42 UTC,[VERIFICATION COSMIC]
1775195,2018-11-13 20:58:06 UTC,I have re-package w/ the upstream fix to address the substitution method failure :
1775195,2018-11-14 15:22:09 UTC,"Hi Eric,"
1775195,2018-11-14 18:42:39 UTC,"Fix has been push into Disco.
sosreport v3.6, is now waiting in the upload queue for C/B/X."
1775195,2018-11-14 21:01:16 UTC,"Hello Eric, or anyone else affected,"
1775195,2018-11-14 21:05:27 UTC,"Hello Eric, or anyone else affected,"
1775195,2018-11-14 21:09:16 UTC,"Hello Eric, or anyone else affected,"
1775195,2018-11-15 19:25:41 UTC,[VERIFICATION BIONIC]
1775195,2018-11-15 19:28:50 UTC,"[VERIFICATION BIONIC]
# Part 2"
1775195,2018-11-13 21:04:11 UTC,"On my side, it looks good now using the package I have just built found on ""ppa:slashd/lp1775195"""
1775195,2018-11-15 20:51:57 UTC,[VERIFICATION XENIAL]
1775197,2018-06-25 13:18:27 UTC,par contre je suis sur que sur l'ancienne mouture de la doc les liens apt avaient leurs icones.
1775197,2018-06-24 20:12:47 UTC,"Bonjour,"
1775197,2018-06-25 13:17:33 UTC,voilà en 16x16
1775197,2018-06-25 15:06:30 UTC,"Effectivement je viens de vérifié. En fait je rectifie, il n'avait d'icône défini correctement, ce dernier se retrouve dans le thème, et non pas dans les icones interwiki.
 Et pas dans le dossier de la doc mais dans le dossier sur le serveur static."
1775197,2018-10-17 14:13:42 UTC,Vous vous souvenez à quoi ressemblait cette icône?
1775197,2018-10-18 18:51:21 UTC,Ce ne serait pas ça ?
1775203,2019-03-09 09:43:39 UTC,"I remember a bug which might be the same, where BlueZ would drop the connection to GATT if no pairing was done within 30 sec. It was fixed though (try a more recent version)"
1775204,2019-02-26 13:38:29 UTC,Is this still being worked on?
1775204,2021-02-19 15:51:52 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1775206,2019-01-02 14:13:06 UTC,"I hoped that 5.1 would use in Export to SVG visibilty flags for Names and References (from right panel, as it uses colours form that panel) or would have such flags added in Export dialog box.
I have installed the last nightly (1.1.2019) and not :("
1775206,2018-06-06 09:16:11 UTC,"@Jeff

> Does that not work for your use-case?


No.
Since 20 years we make our printed doccumentation (laser bw printer) in form of black rectangles (elements) on light grey copper (2 pictures one with values and one with references). This pictures are not 1:1 but as big as fit at A4. It is helpfull if devices are handsoldered (from time to time it happens).
Makeing this (under Protel) was time consuming. Now I am planning to move to KiCad and my first check was if I can do it simpler. Plot can only plot one layer. Then I would need to use other programm to get my pictures. I have checked it going through GerbV (I couldn't get it from KiCad Gerber Viever but don't remember where was the problem) and it works but it is extra step and I got 1M svg while direct from KiCad I got 120k). I think Plot (as mainly gerber generator) don't uses colours. I suppose in Inkscape I would have to import each layer svg at another position to be able to select it and change colour then I will have to precisily move one on another. May be it is simple for someone familiar with InkScape, but I'm not. For example I didn't found the way how to select ellipse colour befor drawing it so I suppose I would don't know how to select color before importing svg (to have it at once at right position).
I found how I cen get my pictures directly from KiCad. In 4.0.7 there are problems with through hole pads colour. I have checked it in V5 and found another problem with value colour (bug 1774171 - fixed). Since always we use footprints defined ourself, so it is not a problem for me to have them as I need. As I use silks for doccumentation then when we will need some paint at pcb I suppose to use to it one Eco layer. If I could use only one layer for my doccumentation I will have silks for that."
1775206,2018-06-05 21:28:54 UTC,You can Plot to SVG and switch Reference/Value on and off.  Does that not work for your use-case?
1775208,2018-06-05 15:51:46 UTC,"I can certainly understand how this would be desirable. I think currently the exit code is only tied to whether we could successfully try to run the action, which was successfully requested, even though the action itself says that  it failed.
I wouldn't expect people are currently depending on the return value of run action, so probably we can just change it."
1775210,2019-09-19 12:05:45 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1775219,2018-06-05 23:22:57 UTC,Here is a previous bug report about this issue.
1775219,2018-06-05 23:37:10 UTC,And here is another one with a specific way of hacking around the problem:
1775219,2018-06-12 14:19:12 UTC,"Brian, the hack doesn't seem workable.  Touching channel.ini would then flag all images as being supported, which isn't true.  It's unclear what knock-on effects we would have touching this file (i.e. what other tools see it and take different code-paths).  The existence of the file indicates that the image is a read-only system image, this is untrue for minimal."
1775219,2019-10-14 17:27:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775219,2020-09-23 16:46:41 UTC,This bug was fixed in the package apport - 2.20.11-0ubuntu47
1775220,2018-07-03 02:15:43 UTC,"Reviewed:  https://review.openstack.org/579282
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f384828895e1d334310973cfeafa14264d6bc5f6
Submitter: Zuul
Branch:    stable/queens"
1775220,2018-06-20 23:48:46 UTC,"Reviewed:  https://review.openstack.org/576899
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c4ea8ba82bb0e5c3026330333c9a88c88ab930ee
Submitter: Zuul
Branch:    master"
1775220,2018-06-29 20:40:11 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/579282"
1775220,2018-06-05 16:47:19 UTC,"Couple of hits during last week:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=(build_name%3A%5C%22openstack-tox-py27%5C%22%20OR%20build_name%3A%5C%22openstack-tox-py35%5C%22)%20AND%20message%3A%5C%22testtools.matchers._impl.MismatchError%3A%208%20!%3D%205%3A%20queries%20before%5C%22"
1775220,2018-06-20 16:01:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/576899"
1775221,2018-06-05 16:57:11 UTC,"StacktraceTop:
 JNIHandles::resolve (handle=0x75732f6d6f634c28) at ./src/hotspot/src/share/vm/runtime/jniHandles.hpp:176
 jni_invoke_nonstatic (env=env@entry=0x7f301034c1e0, result=result@entry=0x7f2fb7a0d350, receiver=receiver@entry=0x75732f6d6f634c28, method_id=method_id@entry=0x7f3010274388, args=args@entry=0x7f2fb7a0d380, __the_thread__=__the_thread__@entry=0x7f301034c000, call_type=JNI_VIRTUAL, this=<optimized out>) at ./src/hotspot/src/share/vm/prims/jni.cpp:1338
 jni_CallVoidMethodV(JNIEnv *, jobject, jmethodID, typedef __va_list_tag __va_list_tag *) (env=0x7f301034c1e0, obj=0x75732f6d6f634c28, methodID=0x7f3010274388, args=0x7f2fb7a0d410) at ./src/hotspot/src/share/vm/prims/jni.cpp:1939
 JNIEnv_::CallVoidMethod (this=<optimized out>, obj=<optimized out>, methodID=<optimized out>) at /usr/lib/jvm/java-8-openjdk-amd64/include/jni.h:1054
 WindowContextBase::process_key (this=0x7f2fa80fc120, event=<optimized out>) at ./modules/graphics/src/main/native-glass/gtk/glass_window.cpp:444"
1775225,2018-06-11 13:14:47 UTC,@Jeff
1775225,2018-07-16 17:27:48 UTC,It's this machine: https://certification.canonical.com/hardware/201805-26258/
1775225,2018-07-16 17:34:30 UTC,"here's a dump of .cache/plainbox/<SESSION>/ from a run that identified the virtual CDROMs.  Unfortunately, I doubt there's much useful in there, since checkbox-ng doesn't log anything from running resources (that I'm aware of)."
1775225,2018-08-14 15:14:30 UTC,Was that enough info?
1775225,2019-10-07 07:56:55 UTC,Real drives usually have lots of environment property detailing their capabilities:
1775227,2018-12-18 20:41:53 UTC,"My comment in #7 is based on role_create(). I didn't check it works with domain admin, so my comment might be wrong.
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/keystone.py#L710-L712"
1775227,2018-11-28 19:46:34 UTC,I agree that the current horizon does not support role create/delete operations by domain admin.
1775227,2018-11-28 19:43:33 UTC,"Since Queens release, the default policy file shipped with horizon is based on individual back-end projects. keystone policy.json (and keystone default policy defined as policy-in-code) defines ""rule:admin_required"" as the default policy for ""identity:create_role"" and ""identity:delete_role"". Thus, it is not surprising that ""Create Role"" and ""Delete Role"" buttons are missing for a domain admin."
1775227,2018-10-09 13:53:43 UTC,Adding upstream as this seems to be pointing to a general upstream issue.
1775227,2018-07-18 10:51:27 UTC,"Dmitrii - is this something that's specific to the way that you're deploying Horizon, or do you think this is a more general upstream bug in Horizon?"
1775227,2018-07-18 14:04:59 UTC,"James,"
1775236,2018-07-20 10:38:30 UTC,"Did a minimal fix for bionic, for cosmic+ we should simplify that and use distro_info I think, now that HWE is rolling."
1775236,2018-07-20 10:50:50 UTC,"Hello Bryan, or anyone else affected,"
1775236,2018-07-20 11:00:46 UTC,"$ lxc exec bio -- hwe-support-status --verbose
You are not running a system with a Hardware Enablement Stack. Your system is supported until April 2019."
1775236,2018-07-23 17:41:44 UTC,This bug was fixed in the package update-manager - 1:18.04.11.4
1775236,2018-07-23 17:41:48 UTC,"The verification of the Stable Release Update for update-manager has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1775236,2020-04-01 21:14:29 UTC,"This is very broken on Focal, per that it was not fixed for future releases - just SRUed.
$ hwe-support-status --verbose
You are not running a system with a Hardware Enablement Stack. Your system is supported until April 2019."
1775245,2018-06-06 19:04:43 UTC,It was reproduced with thick provisioning.
1775245,2018-06-06 13:57:59 UTC,I'm not sure what you're suggesting -- but I don't think we should get into parsing extent usage etc. in LVM.
1775260,2018-07-12 16:05:59 UTC,"Reviewed:  https://review.openstack.org/576531
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=345fc978ed0e5e9abf526cd1d39de007f580e599
Submitter: Zuul
Branch:    stable/18.05"
1775260,2018-06-19 14:21:15 UTC,"Fix proposed to branch: stable/18.05
Review: https://review.openstack.org/576531"
1775260,2018-06-05 19:59:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572538"
1775260,2018-06-19 08:14:46 UTC,"Reviewed:  https://review.openstack.org/572538
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=fc145319991d738e5ca54ea166c96fe32b025af2
Submitter: Zuul
Branch:    master"
1775276,2018-06-08 15:26:12 UTC,"We are also finding this is true for items ""coming home"". If an item is owned by Library A and is in transit to and checked in by Library A, the Route To field will display Library A on the first scan and then the item's shelving location on the second scan. See attached image."
1775276,2019-05-07 21:00:15 UTC,We continue to have libraries report this bug to us. A good portion of our libraries seem to use this field to make sure they are handling items correctly after the check-in.
1775276,2019-05-08 14:15:29 UTC,Just a quick note to confirm that we're still seeing this in 3.2.
1775276,2019-05-09 15:34:26 UTC,"Yes, PINES is no longer getting the incorrect routing slips but we are still getting incorrect routing libraries on the check-in screen in 3.2.3."
1775276,2019-07-25 13:03:04 UTC,We are also seeing incorrect 'route to' information displayed on the checkin screen in our 3.2.4 system.
1775276,2019-11-29 21:54:51 UTC,"If open-ils.circ.checkin closes a transit and creates a new one (for example, opportunistic hold capture for another location), the return payload only contains the closed transit. The route dialogs perform a pcrud search to get the most recent transit, but the grid's Route To field still depends on the transit returned by the API. So, the dialog and receipt display the new destination, but the grid's Route To field displays the old destination."
1775276,2020-01-28 20:39:24 UTC,"Thank you for your work on this, Dan. Our libraries will be happy!"
1775276,2020-01-28 21:00:17 UTC,"Thanks for testing, John!"
1775276,2020-01-31 13:20:18 UTC,"Pushed to master, rel_3_3, and rel_3_4."
1775284,2019-10-07 22:45:29 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1775284,2019-10-07 00:48:09 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1775286,2020-07-20 21:31:28 UTC,"Pushed all the way to rel_3_3. Thanks, Kyle and Jennifer!"
1775286,2019-07-01 18:06:00 UTC,"I noticed a couple thinkos - one in the branch name(it was reflecting the related task regarding the bills interface), and the other in the last commit in lp1635386. The CSS was applying a contrasting color to unvisited links, but not visited ones. New, essentially the same plus a CSS fix, branch here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1775286-items-out-overdue-colors"
1775286,2019-06-18 17:23:56 UTC,I've amended my previous commit with the suggested changes
1775286,2019-09-10 16:27:57 UTC,"Fix is working as expected, regular items and pre-cats both show in red when overdue and go back to white when renewed."
1775286,2019-05-23 21:48:55 UTC,Branch pushed here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1635386-items-out-overdue-colors
1775286,2019-06-18 17:00:16 UTC,"I have confirmed Kyle's branch works as expected for standard overdue items.  However, the additional logic to handle non-cat items is unnecessary and potentially confusing, since overdue non-cat items are never displayed anyway.  My preference is for that part of the patch to be removed for clarity / simplicity."
1775291,2018-06-05 22:38:48 UTC,Launching GCE minimal bionic image from --image-family ubuntu-minimal-1804-lts --image-project ubuntu-os-cloud-devel
1775302,2019-11-15 03:50:52 UTC,"I think the more files you already have in the folder the higher the chance that another new file will trigger the bug. The more time it needs to sort the list the more time for the race condition to occur, and each new file is another shot."
1775302,2019-11-15 01:42:57 UTC,"Thanks, trying to reproduce with a cp loop it does seem to create issues but not that segfault. Do you have plugins installed/enabled? What UI elements are displayed? (gallery, sidebar, ...)?"
1775302,2019-11-15 03:42:53 UTC,No plugins as far as I know. Also no UI elements.
1775302,2019-11-15 05:35:27 UTC,bug #1840508 looks like the same report. Let's close this one since the error tracker reference has no report since 17.10 which suggests that even if the error is similar that was probably a different problem
1775302,2019-11-15 01:51:05 UTC,Got it once with the cp loop and starting eog on one file while it was copying
1775302,2019-11-15 00:48:04 UTC,"https://errors.ubuntu.com/oops/b9742d32-072f-11ea-aff5-fa163e983629
https://errors.ubuntu.com/oops/4c711916-072a-11ea-b6b3-fa163e102db1"
1775302,2019-11-14 22:47:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775302,2019-11-14 23:29:43 UTC,"I'm running Ubuntu 19.04, and I did send the bug report."
1775302,2019-11-14 23:10:02 UTC,What version of Ubuntu do you use? The errors page shows no report since 17.10
1775302,2019-11-14 23:07:27 UTC,"Thanks for the comment, could you give details on the number/type of files and how they get copied? Can you trigger it easily or was it a one time thing?"
1775302,2019-11-14 22:44:06 UTC,This bug is triggered when many new files are added to the folder in which an image is opened.
1775302,2019-11-15 00:42:56 UTC,Could you look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
1775308,2018-06-11 14:33:07 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/574279"
1775308,2018-09-24 14:47:43 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1775308,2018-09-24 14:47:05 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1775308,2018-06-11 16:19:53 UTC,"Change abandoned by Chris Dent (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/574279
Reason: will learn the alphabet and then redo"
1775308,2018-06-11 14:14:03 UTC,"Reviewed:  https://review.openstack.org/573811
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=79a1a113775df87d420b242cea4bbf953df3779c
Submitter: Zuul
Branch:    stable/queens"
1775308,2018-09-26 10:43:51 UTC,This issue was fixed in the openstack/nova 15.1.4 release.
1775308,2018-06-08 12:24:43 UTC,This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.
1775308,2018-06-06 10:50:45 UTC,"Reviewed:  https://review.openstack.org/572652
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=724d440122232a5bfdfec51eb0d37ca4f1d748d8
Submitter: Zuul
Branch:    master"
1775308,2018-06-06 01:13:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572652"
1775308,2018-07-04 15:28:31 UTC,"Reviewed:  https://review.openstack.org/574279
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4bd2a8d9d97ba8ce2e1bab404454aeb543561760
Submitter: Zuul
Branch:    stable/ocata"
1775308,2018-06-08 18:36:55 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/573811"
1775308,2018-06-11 16:20:36 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/574327"
1775308,2018-06-25 14:39:45 UTC,"Reviewed:  https://review.openstack.org/574327
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6e1dd287f18e03428b6f991c5b4bdd66901f8c2d
Submitter: Zuul
Branch:    stable/pike"
1775309,2018-06-06 00:58:23 UTC,Versions installed:
1775309,2018-06-06 01:06:36 UTC,Steps taken:
1775309,2018-06-06 08:44:03 UTC,I'm almost certain this is a bug with the tripleo workflows and not a bug with Mistral itself. So I have added tripleo and marked it as invalid.
1775309,2019-01-29 13:53:39 UTC,Is this still an issue?
1775309,2019-01-29 18:17:16 UTC,@juan-osorio-robles
1775309,2019-03-19 13:27:30 UTC,Let me know if you do.
1775311,2020-05-27 16:04:03 UTC,"Hi,"
1775313,2018-06-21 00:01:24 UTC,The issue did re-emerge after a couple screenshots. So yes.
1775313,2018-06-06 02:21:18 UTC,Actually. Issue was resolved by removing old configuration.
1775313,2018-06-20 10:40:48 UTC,"The only different option in your diff output is ""autofs_min"" which corresponds to the checkbox ""Hide window on first launch"", looks like it is unrelated to the problem..."
1775313,2018-06-22 10:55:21 UTC,"I suspect that it is some Xorg problem on your machine, please ask for support in Ubuntu's community (forums etc.)."
1775315,2018-06-13 12:45:44 UTC,"Does changing it to odl_ip: ""{{ external_lb_vip_address }}"" make it work?
Can you confirm that ODL is running and the REST API is up?"
1775317,2018-09-11 07:34:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775319,2018-06-06 05:17:15 UTC,And we should add a new testcase to cover this.
1775320,2018-06-07 08:29:09 UTC,"Fix committed
https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/414135"
1775320,2018-06-13 03:00:08 UTC,"Fix merged, so close this bug"
1775326,2018-06-13 11:03:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1775326,2018-07-02 08:29:08 UTC,This bug was fixed in the package linux - 4.4.0-130.156
1775326,2018-06-20 13:47:32 UTC,"Hello Gavin,"
1775326,2018-06-06 04:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775328,2018-06-06 15:19:02 UTC,"Thanks, the Juju GUI tracks bugs over in Github. I've refiled this there. Please track updates over there."
1775328,2018-06-06 15:30:52 UTC,Adding Juju project as we are going to add bundle export into the apiserver.
1775328,2018-06-08 00:31:54 UTC,"Ah, also see https://github.com/juju/juju-gui/issues/3360"
1775328,2019-04-10 23:03:21 UTC,"Marking Juju as fix-released, this was added in the 2.4 series."
1775329,2018-07-30 09:46:46 UTC,"I wanted to say ""Jeremy is maintaining both the Debian and Ubuntu *packages* ..."""
1775329,2018-10-02 15:30:13 UTC,I believe Debian would appreciate the feature linking to Debian's CVE database there.
1775329,2018-08-14 14:05:34 UTC,Assigning to Jeremy as the outstanding questions are for him and his nomination to bionic is causing this bug to show up on the desktop team's tracking list but it didn't go through the normal review process.
1775329,2018-07-31 05:27:40 UTC,Ok so any guidance as to how to proceed - Jeremy do you have a preference for how this should work? Would you like it to also support Debian in a similar manner and link to the Debian CVE tracker? In this case would you prefer runtime detection (via say /etc/os-release) or compile-time selection of which CVE tracker to link to?
1775329,2018-07-30 11:31:03 UTC,"Haha, indeed. Thanks! It's been inactive for 9 years, though."
1775329,2018-07-30 11:10:56 UTC,The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=579859
1775329,2018-07-30 03:36:31 UTC,"The other option would be to do it ""properly"" the way upstream want - ie. to have the user be able to configure their one linkification."
1775329,2018-07-30 09:45:41 UTC,"> The other option would be to do it ""properly"" the way upstream want
"
1775329,2018-11-13 14:34:49 UTC,I'm dropping the bionic task for now so that it doesn't clutter the Ubuntu Desktop Team's bionic tracker when this isn't ready for bionic yet.
1775329,2018-07-27 18:57:06 UTC,I agree it's a nice idea.
1775329,2018-07-27 16:37:55 UTC,"Hmm, this is an interesting idea."
1775329,2018-06-17 08:20:47 UTC,"The attachment ""Debdiff against current bionic version adding this feature"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1775340,2019-05-01 09:20:21 UTC,Is this related to bug 1640514?
1775347,2018-06-06 08:22:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1775347,2018-06-06 17:05:11 UTC,The update status link in the above comment does not work.  I don't see an option on this page to update/edit the status.
1775347,2020-05-15 23:50:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775351,2018-11-03 10:40:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775364,2018-06-06 09:27:46 UTC,The following actions will fix this bug. b
1775370,2018-06-06 10:00:07 UTC,This change was made by a bot.
1775370,2018-06-06 09:52:39 UTC,This might be related to CVE-2017-15299 and CVE-2017-15951
1775370,2018-10-16 09:02:36 UTC,This issue no longer exist.
1775370,2018-10-03 06:41:36 UTC,"With all the CVEs listed here fixed in Trusty kernel, we need to check this issue again.
https://lists.ubuntu.com/archives/kernel-team/2018-October/095725.html"
1775372,2021-02-11 11:10:00 UTC,"Alan, as far as I can tell, the key is deleted in the API service synchronously, so it would be possible to alter the return code."
1775372,2021-02-02 17:48:49 UTC,"@awalende, the concern is that ""abandoned"" encryption keys are still consuming a resource, notably in the HSM where they might be stored. Cinder's behavior is intended to highlight the fact that there's an issue deleting the key in order to avoid it becoming abandoned. I don't know about the specifics of barbican's policies regarding whether an admin can delete a user secret."
1775372,2021-02-02 12:07:15 UTC,Agreed this is quite annoying behaviour. Would it be acceptable to return a 403 to the cinder API caller if we get a 403 from barbican?
1775372,2018-06-06 09:57:52 UTC,Latest devstack queens.
1775372,2018-06-07 06:18:36 UTC,"This is probably not a cinder bug, but is a side effect of using barbican. Cinder has its own policies for who can delete a resource (such as a volume), and barbican has its own policies that can be more restrictive. Barbican has stricter rules about deleting another user's secrets than cinder has about deleting another user's volumes. Here, cinder is refusing to delete the volume because the user is not authorized to delete the secret associated with the volume. This is done in order to avoid ""leaking"" an encryption key."
1775372,2019-12-03 13:53:47 UTC,"Would it be really an issue if cinder would delete the volume anyways? The encryption key is generated on volume create, so the key should be worthless after the volume is gone?
Maybe a temporary solution until the admin user is able to delete user secrets.
As far as I know, it is not possible to delete barbican user secrets with an admin user, making the management of encrypted volumes really annoying."
1775372,2018-06-06 09:59:09 UTC,"Since the volume created as encrypted , we expect that admin tenant will be able to delete the volume."
1775372,2018-06-07 05:14:00 UTC,"Steps to reproduce:
# create a volume type (admin tenant)
# create encryption type - >  (admin tenant)
encryption_prov = nova.volume.encryptors.luks.LuksEncryptor
key_size = 256
cipher = aes-xts-plain64
control_location = front-end"
1775373,2018-06-06 10:59:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/572728"
1775373,2018-07-25 00:05:53 UTC,"Reviewed:  https://review.openstack.org/572728
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=a7ba6d02aae23c66e9aa0b3853ff07ebe72f38cd
Submitter: Zuul
Branch:    master"
1775373,2018-06-06 10:21:29 UTC,"This case can be also be occurred when multiple parallel requests will be initiated for same VNF, and we can not handle these cases.
But instead of VNF not found error correct error message should be there."
1775378,2019-09-19 14:01:15 UTC,This is fixed by a backported patch of 8edc6e1688f. Kernel and patch file is available @ https://people.canonical.com/~alexhung/LP1775378/
1775378,2019-10-17 08:00:11 UTC,"Test with the proposed Trusty kernel.
This patch works as expected.
Thanks."
1775378,2018-06-06 10:38:30 UTC,This issue cannot be reproduced with Trusty ppc64le and ARM64
1775378,2018-06-06 10:30:07 UTC,This change was made by a bot.
1775378,2019-07-17 06:17:51 UTC,"I could see this failing on Trusty ARM64 Moonshot node, but not the ppc64le node ""modoc"":
startup='Tue Jul 9 07:45:17 2019'
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0'
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.42.9 (4-Feb-2014)
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
tst_fs_setup.c:43: INFO: fanotify06.c:239: overlayfs is not configured in this kernel
fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark
fanotify06.c:147: PASS: group 0 got event: mask 2 pid=6308 fd=30
fanotify06.c:147: PASS: group 1 got event: mask 2 pid=6308 fd=30
fanotify06.c:147: PASS: group 2 got event: mask 2 pid=6308 fd=30
fanotify06.c:220: FAIL: group 3 got event
fanotify06.c:230: PASS: group 4 got no event
fanotify06.c:220: FAIL: group 5 got event
fanotify06.c:230: PASS: group 6 got no event
fanotify06.c:230: PASS: group 7 got no event
fanotify06.c:230: PASS: group 8 got no event
fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark
fanotify06.c:173: CONF: overlayfs is not configured in this kernel."
1775380,2018-06-10 15:37:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775383,2018-06-06 11:55:44 UTC,"I have confirmed that this does not affect all WMs, as the awesome-wm is unaffected."
1775389,2018-10-03 20:29:39 UTC,The upstream changelog for 4.0.0 contains
1775392,2020-11-23 23:22:16 UTC,Same bug seen on Ubuntu Bionic 18.04.5 LTS with Lenovo P53.
1775392,2020-11-25 14:47:41 UTC,https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/27
1775392,2020-11-25 14:41:49 UTC,"Ok, thank you for the info, I'll move the bug over there"
1775392,2020-11-25 08:43:02 UTC,"bugzilla is deprecated, if that's still happening it would be better to open a new report on https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues"
1775392,2020-11-24 18:11:11 UTC,upstream bug can be found here https://bugzilla.gnome.org/show_bug.cgi?id=796512
1775392,2018-11-27 09:28:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1775392,2018-07-08 08:47:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775392,2019-06-24 16:23:39 UTC,"I'm also running into this bug (or at least something that looks like it). Typically what happens for me is that I resume from suspend, get an unlock prompt (the system is locked on suspend) and when I log in, the unlock prompt stays visible (the password dots disappear, but I cannot type anything or click any buttons). When I then kill X to recover (ctrl-alt-backspace), I get a new login prompt. Sometimes, logging in again no longer works then, seeing such messages in the console:"
1775392,2018-11-26 15:58:30 UTC,"-- Logs begin at Thu 2018-11-01 16:00:55 CET, end at Mon 2018-11-26 16:45:36 CET. --
nov. 26 16:42:47 claude-M61PME-S2P mintmenu[12883]: mintMenu.py: Fatal IO error 11 (Ressource temporairement non dispo
nov. 26 16:42:47 claude-M61PME-S2P unknown[12887]: clock-applet: Fatal IO error 11 (Ressource temporairement non dispo
nov. 26 16:42:47 claude-M61PME-S2P at-spi-bus-launcher[12832]: XIO:  fatal IO error 11 (Resource temporarily unavailab
nov. 26 16:42:47 claude-M61PME-S2P at-spi-bus-launcher[12832]:       after 5057 requests (5057 known processed) with 0
nov. 26 16:42:47 claude-M61PME-S2P unknown[12889]: notification-area-applet: Fatal IO error 11 (Ressource temporaireme
nov. 26 16:42:47 claude-M61PME-S2P unknown[12885]: wnck-applet: Fatal IO error 11 (Ressource temporairement non dispon
nov. 26 16:42:47 claude-M61PME-S2P polkitd(authority=local)[698]: Unregistered Authentication Agent for unix-session:c
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing process 12397 (lightdm) with signal SIGTERM.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing process 12415 (gnome-keyring-d) with signal
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing process 12762 (ssh-agent) with signal SIGTER
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing process 12912 (applet.py) with signal SIGTER
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing process 13265 (dbus-launch) with signal SIGT
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: session-c12.scope: Killing process 13931 (xplayer) with signal SIGTERM.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: Stopping Session c12 of user claude.
nov. 26 16:42:47 claude-M61PME-S2P systemd[1]: Stopped Session c12 of user claude.
nov. 26 16:42:47 claude-M61PME-S2P systemd-logind[628]: Removed session c12.
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so:
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM adding faulty module: pam_kwallet.so
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.s
nov. 26 16:42:47 claude-M61PME-S2P lightdm[13948]: PAM adding faulty module: pam_kwallet5.so"
1775392,2018-11-26 15:57:05 UTC,This happens from time to time in CAJA and when launching VLC.
1775397,2018-06-07 02:40:34 UTC,"Also, here is an example of a read-only volume attachment where the connection_info says the access_mode is 'rw' but the attachment shows the attach_mode='ro':"
1775397,2018-06-07 03:37:52 UTC,Also there are several similar concepts that would confuse people who doesn't have the full background of the attach_mode stuff:
1775399,2018-06-06 13:05:06 UTC,We have a couple of these in the error log.
1775399,2018-06-08 13:05:46 UTC,This one generated multiple alerts per day...there is a message queued up on osfkarl10 trying to go out.
1775399,2018-06-08 15:23:34 UTC,"Sorry, busy week. Will be able to look at this and other bugs tomorrow."
1775399,2018-12-06 11:30:10 UTC,"Per the comment, the message causing this was moved to osfkarl12:~/tmp"
1775403,2018-06-07 06:01:09 UTC,"Hi Rapheel,"
1775408,2018-06-08 11:00:20 UTC,Maybe both options?
1775408,2018-08-09 00:37:40 UTC,"Maybe new tracks should be added in order of their creation/modification date?  Not sure what the resolution of the date added crate is, but if each one was added milliseconds after the previous one, then sorting would work better."
1775411,2018-09-24 11:14:18 UTC,I haven't been able to reproduce this and config-changed appears to have the correct restart decorator. Can you confirm that this bug is still occurring please?
1775411,2019-12-02 13:05:32 UTC,"Setting to invalid as there has been no movement in over a year, and the bug appears to not have been reproduced.  It may have been overtaken by events."
1775415,2018-08-31 07:38:42 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1775415,2018-06-06 15:58:14 UTC,It looks there are two issues have been raised:
1775415,2018-06-06 16:00:31 UTC,"I am going to mark this bug as ""incompleted"" to indicate that we need further inputs to triage this bug."
1775415,2018-06-07 08:58:52 UTC,"Hi, you're right about (1), I overlooked that, sorry."
1775415,2018-06-11 16:46:42 UTC,"Hi, we reproduced the Bug, it happens due to usage of authz policy.json:"
1775415,2018-06-20 16:38:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576910"
1775415,2018-08-31 07:38:51 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/576910
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1775418,2019-06-06 06:23:44 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1775418,2019-09-27 09:03:37 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1775418,2019-07-10 21:39:37 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1775418,2019-06-18 03:40:45 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1775418,2019-06-03 11:29:10 UTC,"Reviewed:  https://review.opendev.org/662340
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=58a140487c8127da727fa7e4fb56892f8c162536
Submitter: Zuul
Branch:    stable/queens"
1775418,2019-05-30 21:00:13 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/662331"
1775418,2019-05-31 13:49:04 UTC,"Reviewed:  https://review.opendev.org/662331
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9b21d1067a071ab17758068dfca5cd2ebd29d868
Submitter: Zuul
Branch:    stable/stein"
1775418,2019-06-03 09:28:34 UTC,"Reviewed:  https://review.opendev.org/662333
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c19d602f9be536ee8412bac0f0951a995424f25e
Submitter: Zuul
Branch:    stable/rocky"
1775418,2018-06-06 19:53:11 UTC,Nova patch: https://review.openstack.org/#/c/572790/
1775418,2018-06-06 19:48:51 UTC,"As mentioned in the mailing list, I think this is also something to be controlled in Cinder during retype or volume live migration since that would be a fast fail for this scenario:"
1775418,2019-05-30 21:14:36 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/662333"
1775418,2019-05-30 21:30:59 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/662340"
1775418,2019-05-30 17:47:40 UTC,"Reviewed:  https://review.opendev.org/572790
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5a1d159d142997bb4288d4bf86d4e144334905cd
Submitter: Zuul
Branch:    master"
1775424,2020-09-22 19:00:47 UTC,"I am seeing the exact same problem, even when commissioning with Xenial (both ga and hwe kernels). Was there ever a more permanent solution?"
1775424,2020-05-05 07:22:00 UTC,"So, as I understand it, the workaround is to set Xenial to be the commissioning environment, but we need to make it so that Xenial is used when deploying Centos6."
1775424,2019-10-21 07:05:56 UTC,I have this issue only wen i use software RAID here it is the messeges.
1775424,2019-06-04 18:21:01 UTC,"Scratch separate /boot, the curtin-hooks in centos6 do not support separate /boot.  So, switching the filesystem format to ext3 should work fine."
1775424,2019-06-04 17:25:25 UTC,"The source of the issue is around the ext4 filesystem and grub 0.97[1].  In Bionic, ext4 has 64bit and metadata_csum features which grub 0.97 in Centos6 cannot handle read.   There are couple of workarounds here:"
1775424,2019-04-26 13:11:10 UTC,Log for the failure
1775424,2018-12-24 04:17:30 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1775424,2018-10-24 18:16:47 UTC,"Hi Andres,"
1775424,2018-10-10 13:27:50 UTC,"Hello,"
1775424,2018-06-12 07:50:12 UTC,"I was able to reproduce this when I had my commissioning operating system set to Bionic, could you please try 16.04 Xenial?"
1775424,2018-06-06 22:12:22 UTC,Can you provide the output of your machine:
1775424,2018-06-06 19:34:06 UTC,"I am using the stock image provided by maas.io and no customizations have been done, everything was left at default."
1775424,2018-06-06 19:24:41 UTC,"Hi there,"
1775424,2019-04-26 13:10:39 UTC,I can also reproduce this problem with MAAS 2.4.2 + Ubuntu 18.04.2 + kernel 4.15.0-45. I'm using the CentOS 6 image synced from maas.io through the regular MAAS Web GUI (no curtin customizations):
1775424,2018-10-10 20:22:33 UTC,"Hi Daniel,"
1775427,2019-03-22 08:26:29 UTC,"Completed the review on the remaining pytohn libs, overall the remaining TODOs are some tasks for the server Team (breakign dependencies), a lot of security reviews, but also 5 tasks for the MIR team.
Those split into 3 discussion and 2 package reviews.
As discussed I'll bring those up on next weeks MIR Team meeting."
1775427,2018-09-11 21:09:17 UTC,@powersj @dpb1 - ping? i thought there was consensus the other day...
1775427,2019-04-09 13:11:45 UTC,"Setting mailman to Triaged; let's get this off the ""New MIRs"" list -- it's not new, just not completed yet. mailman3's status nicely captures this."
1775427,2019-03-21 14:29:25 UTC,"Updates for completing python-arrow python-blessed python-public and python-uritemplate
Some new non blocking but recommended tasks added, as usual marked in the overview and details can be found in the respective bugs."
1775427,2019-03-20 15:33:54 UTC,"Updated for the complete of the MIR review on  main mailman3 components: hyperkitty, mailman* and postorious"
1775427,2019-03-20 15:30:48 UTC,"[Duplication]
This is part of the six core packages of mailman3 that pull in further components as needed.
Since this represents mailman doing mailing list processing there is a duplication to mailman2.
But the intention is to stop seeding mailman2 as soon as mailman3 got promoted."
1775427,2019-03-20 14:16:25 UTC,Updated for MIR review of coreapi coreschema robot-detection and wcwidth
1775427,2019-03-20 13:33:01 UTC,"zeromq ftbfs is fixed and there was no explicit reason to demote it, so we can use the old MIR and consider that one done. Updated the description."
1775427,2019-03-20 12:30:14 UTC,Updated description after the review of django.* and marking some packages for Team review already
1775427,2019-03-19 11:35:09 UTC,Updated after completion of flufl.* and lazr.* MIR review.
1775427,2019-03-19 10:22:06 UTC,"MIR review on zope.* done (I start with the easier bits first, to have the feeling of hope :-) )
Due to their integration into a web stack I marked them in the description and the respective bugs as waiting for security review."
1775427,2019-03-19 08:03:46 UTC,"Work to cut out  more of the dependencies we really don't think to be approproate (ruby/nodejs) was discussed upstream and started with Debian:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/gbugreport.cgi?bug=924961"
1775427,2019-03-13 09:46:58 UTC,"While preparing the MIR bugs for the involved soruces I found that some we initially detected are already in main pulled in by python3-django-openstack-auth:
- python3-csscompressor
- python3-django-compressor
- python3-rcssmin
- python3-rjssmin"
1775427,2019-07-02 19:50:07 UTC,"After dozens of reviews by the security team, we are ending the MIR for mailman3 and the enormous list of dependencies due to the complexity of the package, difficulties maintaining, and security concerns. mailman3 will live in universe."
1775427,2019-02-18 22:35:33 UTC,"Well #is has now deployed mailman3, i think it all should go into main."
1775427,2018-12-05 16:33:28 UTC,"Existing option left, let mailman[23] go - not my decision thou - might bring it up on the sprint thou."
1775427,2018-12-05 16:28:51 UTC,"Discussed in the Team, and the conclusion is that we have to go the big route of mailman3-full
Maybe breaking out hyperkitty to a suggests, but that is not helping too much."
1775427,2018-12-05 14:05:38 UTC,"To help the discussions to come I isolated the dependencies of mailman3-web
mailman-hyperkitty is very similar."
1775427,2018-12-05 13:28:45 UTC,"Summary (mostly as a working theory for now):
Seeding/Unseeding:
- we would only select and fully support the core mailman3 (to keep things reviewable and supportable)
- all the web bits pulled in by mailman3-full via mailman3-web and hyperkitty would not get into main
- once migrated mailman2 would be demoted (another nail in the python2 coffin)
Ownership:
- flufl*, lazr.*, python-*, nose as listed are generic python libraries which I'd ask foundations to own
- zope.* as listed would be on Server Team
- mailman3 itself would be on Server Team"
1775427,2018-12-05 13:15:38 UTC,"I wanted to eventually file MIRs for all of these and reference the bugs here.
I wondered to drive all in this MIR, but that will break discussions as e.g. python-flufl and zope are so damn different that doing that in just this bug will make us loose track too much.
OTOH now that I did the deep check on dependencies, I'm afraid this just is too much either way."
1775427,2018-12-05 13:14:16 UTC,"Time to get it started, I assume this will accompany us for a while at least, but we have to start at some point."
1775427,2018-12-04 21:36:04 UTC,Assigning to Christian for investigation
1775427,2018-11-28 15:28:04 UTC,@powersj I think the biggest blocker would be security reviews of all of these things.
1775427,2018-09-20 08:58:25 UTC,"There is consensus to do this, we need the work broken down to determine if we can get it all done next cycle or over 2 cycles."
1775427,2018-09-13 16:06:50 UTC,"mailman-suite / mailman3-web should change packaging to launch as python3, not python2 webapp."
1775427,2019-02-19 05:29:40 UTC,"On Mon, Feb 18, 2019 at 11:41 PM Dimitri John Ledkov
<email address hidden> wrote:

> Well #is has now deployed mailman3, i think it all should go into main.
"
1775430,2019-11-25 04:17:35 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1775430,2018-06-12 08:35:14 UTC,We recently had the need to configure an additional directly connected network. These were non-link-local (but rfc1819) addresses.
1775430,2018-06-07 20:47:49 UTC,"Hey Peter,"
1775430,2019-09-19 12:05:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1775430,2018-06-06 21:15:49 UTC,"Sorry for being unclear - I'm fine with letting Maas choose the device, same as it does currently when adding a static route. Just would like the option of not having to specify a gateway when creating a static route (defined at the subnet level, indeed)."
1775430,2018-06-06 19:27:45 UTC,"Unless I am miss understanding this, I don't know if what your asking for is strait forward. If you are saying that you want to provide a static route to a specific interface of a machine, that will not work at the subnet level."
1775430,2018-06-07 19:03:56 UTC,"I think it should be possible to put this under a subnet, and if a machine
gets deployed with an interface in this subnet, this route, without
gateway, to be added."
1775431,2018-06-06 16:45:59 UTC,Here is a full output of
1775431,2021-02-17 17:08:12 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1775432,2018-10-11 00:56:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775432,2018-10-11 01:00:38 UTC,"No gnome-software, o tema dos botões stackswitcher no topo 'Installed' e 'Updates' é diferente de 'All'. O efeito 3D só é visível em 'All' quando selecionado. Os três botões devem ter o mesmo efeito."
1775434,2018-10-06 14:39:48 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831467
1775438,2020-01-09 14:00:17 UTC,Probably fixed: https://github.com/mixxxdj/mixxx/pull/2321
1775438,2018-06-07 16:58:53 UTC,"If spaces were indeed a problem, the issue would also occur on the Windows version of Mixx, since every path type contains some."
1775438,2018-06-07 15:09:00 UTC,Are the spaces in the first path part of the problem? (Are we correctly escaping the paths?)
1775444,2018-06-22 18:12:33 UTC,"Hi Hao,"
1775444,2018-06-23 14:07:10 UTC,"Hi Andrew,"
1775444,2018-09-05 12:45:21 UTC,"Core Group review at ESS: We would look at this if it can be reproduced against a 3.15 or higher release, where we made significant changes to dbNotify."
1775446,2018-06-07 05:57:54 UTC,"Hi Rapheel,"
1775447,2020-08-14 10:41:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775453,2018-06-06 19:22:59 UTC,"Manual installation of default-jre (`sudo apt-get install default-jre`) helps, but it is inexpected. Snaps should not have dependency hell inside the technology..."
1775453,2019-10-10 12:30:45 UTC,"This is not a bug in snapd, but in the snap itself. It _is_ a rather ugly bug in this snap, but please report it to the snap publisher."
1775454,2019-07-09 16:06:33 UTC,Can you attach your apt sources.list file?
1775454,2018-07-01 08:28:14 UTC,Even I am having the same issue
1775454,2018-07-01 08:28:40 UTC,My laptop is HP15n213TU
1775457,2018-06-06 19:28:05 UTC,Here's the traceback:
1775457,2018-06-06 19:32:31 UTC,doko tells me that this is due to people installing pip another way and pip10 doesn't include main. Perhaps we should suppress the crashes since there isn't anything we can do about it.
1775463,2018-06-10 04:39:05 UTC,power manager has seen some big changes - make the testcase match the app
1775464,2018-09-22 08:48:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775465,2018-06-07 00:24:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1775470,2019-01-12 05:23:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775479,2019-02-26 23:17:33 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9602"
1775479,2018-07-15 07:05:43 UTC,"Plizz unsubscribe me from the domain. This is not what my school wanted to
join for my e -Portifolio"
1775479,2018-07-16 20:14:30 UTC,"Micheal, I sent you an email. You can unsubscribe yourself. If you have any problems, please let me know via email."
1775479,2019-08-06 03:32:17 UTC,"Reviewed:  https://reviews.mahara.org/9602
Committed: https://git.mahara.org/mahara/mahara/commit/3611725eb8a7a897bb228a4dd6ba0f0cd39ad4c1
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1775482,2018-10-30 23:18:49 UTC,"Submitted https://review.openstack.org/#/c/573465/ to fix it, FWIW, but that was months ago."
1775482,2019-06-13 10:06:37 UTC,This issue was fixed in the openstack/python-openstackclient 3.19.0 release.
1775497,2020-05-09 07:01:28 UTC,Does this still happen with Mixxx 2.3 alpha?
1775499,2018-06-07 03:56:46 UTC,thanks
1775501,2018-10-15 22:06:51 UTC,"cs:aodh got a rebuild, the fix is in cs:aodh-17"
1775501,2018-10-09 23:25:06 UTC,It appears that charm-aodh got built before interface:keystone in layer-openstack was up-to-date with the patch.  I've asked @shaner to re-build aodh charm.  Might want to check any other related charms that the hooks/relations/keystone/requires.py includes service_domain in the auto_accessors list.
1775501,2018-06-27 06:57:13 UTC,"Change abandoned by Xav Paice (<email address hidden>) on branch: master
Review: https://review.openstack.org/575263
Reason: see https://review.openstack.org/#/c/578289/2/src/templates/aodh.conf"
1775501,2018-06-13 23:01:21 UTC,"Change abandoned by Xav Paice (<email address hidden>) on branch: stable/18.05
Review: https://review.openstack.org/575261
Reason: wrong branch"
1775501,2018-06-13 22:56:43 UTC,"Change abandoned by Xav Paice (<email address hidden>) on branch: master
Review: https://review.openstack.org/574571
Reason: revised in another change"
1775501,2018-06-13 22:54:49 UTC,"Fix proposed to branch: stable/18.05
Review: https://review.openstack.org/575261"
1775501,2018-06-12 23:49:43 UTC,https://review.openstack.org/#/c/574571/ and https://review.openstack.org/#/c/574920/ should fix this
1775501,2018-06-12 23:22:57 UTC,gnocchi.conf also needs editing:
1775501,2018-06-12 05:57:08 UTC,"Additionally, we find the following are needed in aodh.conf in order to overcome the lack of specifics with the config where we have a services_domain and 'default' domain."
1775517,2018-07-01 07:39:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775517,2018-06-07 06:29:45 UTC,Ubuntu server 18.04
1775521,2018-06-07 06:39:45 UTC,"output.xlsx has the permission and ownership details of cinder files and directories from all three nodes M1,M2 and m3"
1775521,2018-06-07 06:44:51 UTC,We have a replica of production setup in our lab. A strace on cinder volume service start between both replica and production setup shows different result:
1775521,2018-06-07 14:23:52 UTC,This appears to be a networking issue with that host:
1775538,2018-06-10 21:22:59 UTC,"Currently, an admin can send messages to multiple people. However, everyone would see who'd also received that message, which would not comply with privacy (DSVGO above is the Germany data privacy regulation)."
1775548,2018-06-19 14:16:52 UTC,The fix mentioned in https://bugs.launchpad.net/python-cliff/+bug/1774418 resolves this failure.
1775548,2018-06-20 20:43:50 UTC,The bug has been fixed: https://review.openstack.org/#/c/571524/
1775553,2018-06-07 08:55:52 UTC,Here's one example of the errors
1775553,2018-06-14 09:48:54 UTC,I think the root of cause is like this.
1775553,2018-07-06 12:54:38 UTC,"Looking at logstash, all of the failures are happening when using static accounts, not sure why that case is special."
1775553,2018-07-06 13:00:31 UTC,One possibly related observation:
1775553,2020-02-18 10:11:28 UTC,Is the issue still happening?
1775553,2020-02-19 00:20:30 UTC,It looks no error has happened against AccountTest.test_list_containers_with_end_marker test for these 6 months at least.
1775553,2020-02-24 09:14:07 UTC,"Ok then, it seems it got fixed somehow. I'm gonna mark this as Invalid now, but if the issue happens again, feel free to reopen it."
1775554,2018-06-07 09:16:16 UTC,The bug report seems to say you have modified the file. What have you modified it to?
1775554,2018-06-07 09:51:17 UTC,"Sorry for that. I was trying a few things to get rid of that problem and I forgot to take it back.
I copied it elsewhere and I reinstated the original package version. This is the diff:"
1775554,2020-10-07 10:51:27 UTC,Any news on that? Bug continues to this day.
1775554,2018-06-07 09:52:11 UTC,"/home/patola/_mpv is my modified version and /usr/share/zsh/vendor-completions/_mpv is the original, BTW"
1775556,2018-06-10 19:12:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775558,2018-06-07 12:27:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1775559,2018-10-03 07:26:02 UTC,"It was a conscious decision to use /usr/lib as we wanted to be able to package our system-provided scripts outside of /etc first, and deal with system-local configuration later. I recently added support for overrides in /etc in cosmic and upstream, so we search both and /etc overrides /usr."
1775566,2018-12-11 16:24:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775566,2018-06-07 09:48:50 UTC,Since it might be networkd as well I added a bug task for it.
1775566,2018-06-07 11:10:12 UTC,"Even ""netplan apply"" with NO yaml file fixes it.
So running in the static networkd config (with the files I copied formerly created by netplan as outlied above)."
1775566,2018-06-07 12:02:49 UTC,I thought I might have oversimplified PCIe setup for q35 too much when I tried to compare to i440fx (where this works AFAICS).
1775566,2018-06-07 12:26:46 UTC,"Since we ruled out netplan, mark it invalid.
Focus on systemd-networkd for now."
1775566,2018-06-07 13:39:30 UTC,"I identified that systems I spawn as q35 right away work.
Only those where the initial cloud init runs as i440fx and then I change them to q35 are affected."
1775582,2018-10-13 07:52:16 UTC,"I found the following snippet works, but don't exactly know why:"
1775583,2018-06-08 03:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775583,2018-06-08 13:48:36 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1775584,2018-06-12 20:54:20 UTC,I didn't reproduce this.
1775584,2018-06-12 16:32:29 UTC,Will try to reproduce it locally.
1775584,2018-06-13 07:49:38 UTC,"I tried across multiple versions of haproxy, and only a recent version from vbernat's haproxy 1.8 ppa is fixed."
1775584,2018-06-13 06:23:31 UTC,"Dear Jean-Philippe,"
1775584,2018-06-07 11:41:41 UTC,playbook should fail if haproxy isn't started successfully
1775584,2018-06-13 07:46:13 UTC,"Tested, and valid."
1775586,2018-06-07 11:33:41 UTC,the logs for the passed case which is mainline kernel 4.17.0-rc7
1775587,2018-06-07 11:37:36 UTC,Attaching properly formatted patch
1775587,2018-06-07 15:55:27 UTC,"This code may change in the upcoming release, but if not, I will include this. Thanks!"
1775592,2018-10-12 13:36:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775592,2018-10-12 13:38:53 UTC,Confirmed and quite annoying.
1775621,2018-06-08 11:32:23 UTC,The first line that is changing {{ [internal_lb_vip_address] }} is not correct because that is for haproxy.yml. Haproxy does not want urls with square brackets ([]). It seems like everything else wants square brackets.
1775621,2018-06-12 21:37:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/574893"
1775621,2020-09-17 22:14:40 UTC,"Change abandoned by Nicolas Bock (<email address hidden>) on branch: master
Review: https://review.opendev.org/574893"
1775625,2018-06-11 18:49:15 UTC,"Reviewed:  https://review.openstack.org/573254
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4e3dd818a3e23c942bb2d475c6fc2138518276fc
Submitter: Zuul
Branch:    stable/queens"
1775625,2018-09-24 14:47:44 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1775625,2018-06-07 14:18:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/573254"
1775629,2018-06-29 14:39:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1775631,2018-07-24 08:56:36 UTC,Title and bug description updated to match reality!
1775631,2018-06-26 16:46:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775631,2018-06-26 16:51:29 UTC,"Fresh install of Ubuntu 18.04. xorgxrdp + xrdp install. 2 issues:
1. xrdp user is not part of ssl-cert group by default, and is not able to read /etc/xrdp/key.pem (but able to read /etc/xrdp/cert.pem)
2. connection establishes but gnome requires one to enter user credentials in ""Authentication is required to create a color managed device"" dialog when launching GNOME 3 and once you do this around 8 times it would disconnect a session"
1775631,2018-07-24 08:47:14 UTC,Apologies - the version numbers above are all wrong. Goodness knows what I was thinking.
1775631,2018-10-18 15:13:31 UTC,Same problem here. Please provide a xrdp packages in 0.9.8 version.
1775634,2018-06-27 19:22:52 UTC,This bug only seems to happen in the Xorg session and not the Wayland one.
1775635,2018-06-24 10:53:20 UTC,I only see this on Xorg. The wayland session seems to work properly. In Xorg with 4 fixed virtual desktops the behaviour is the following with a fullscreen virtualbox instance:
1775635,2020-12-18 18:18:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775635,2018-06-08 14:51:47 UTC,I've only run the Xorg session. If that helps I'll run the Wayland session for a while to give feedback on all the bugs I've encountered.
1775635,2018-06-08 02:27:46 UTC,Does the problem happen specifically in only Xorg or only Wayland sessions?
1775636,2018-06-08 17:44:54 UTC,"Yeah, ipa-client-install worked."
1775636,2020-01-28 20:52:13 UTC,Just confirming this is still in our queue.
1775636,2019-07-31 20:21:12 UTC,"Only xenial affected, adjusting bug tasks"
1775636,2018-06-08 20:10:43 UTC,That patch will require some backporting effort as it depends on other changes done before in that 1-13 branch.
1775636,2018-06-08 18:20:03 UTC,"Workaround confirmed, I'll be rolling that out while waiting for that to land in xenial.
If you need more info or help debugging, I'll be happy to help."
1775636,2018-06-08 17:56:22 UTC,It looks like this could be https://pagure.io/SSSD/sssd/issue/2977
1775636,2018-06-08 17:39:36 UTC,I've been using the ipa-client-install on 14.04 and had no issues (knock on wood)
1775636,2018-06-08 15:25:27 UTC,"Yes, seems right."
1775636,2018-06-08 14:09:06 UTC,How did you add the certificate to the user? Following https://www.freeipa.org/page/Howto/Client_Certificate_Authentication_with_LDAP perhaps? Is that howto still up-to-date for your deployment?
1775636,2018-06-08 13:35:39 UTC,I'm also taking a look at reproducing this.
1775636,2018-06-08 05:49:02 UTC,"Hi,
can you in addition try if it is also fixed with the version that is in Ubunt u 18.04 or later.
That would be based on 1.16.1 like the one you referred for CentOS."
1775636,2018-06-07 14:53:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775636,2018-06-08 16:34:31 UTC,I'm trying on trusty and just found out realmd there segfaults when joining
1775637,2018-09-28 09:10:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775637,2019-02-09 14:09:08 UTC,This is probably the same bug as the one I submitted against mutter:
1775639,2019-03-08 18:10:31 UTC,still getting this in 3.2 (although it looks like the screen layout has changed)
1775639,2019-05-23 22:07:47 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, folks!"
1775639,2019-03-11 17:50:55 UTC,here's a branch that will refresh patron data when making a payment that effects credit forward balance:
1775639,2019-05-22 18:59:58 UTC,Tested and works as advertised.  Signedoff branch at  https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1775639-refresh-required-to-see-patron-credit-signoff
1775644,2019-07-10 07:23:15 UTC,"Is this still an issue on current master release?
@Tamas: can You also check if that happens only when You try to bind it to wrong port type as Li mentioned in comment above?"
1775644,2019-09-09 04:17:21 UTC,[Expired for neutron because there has been no activity for 60 days.]
1775644,2019-07-10 03:20:18 UTC,The port must be a router:interface.
1775650,2018-06-13 08:23:07 UTC,It seems that it's a incompatibility of horizon and cloudkittydashboard.
1775650,2018-06-13 11:40:09 UTC,I discover that if i go directly to url:
1775650,2018-06-13 13:04:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575103"
1775650,2018-07-30 10:03:34 UTC,That fix is for python-cloudkittyclient it also affects to cloudkitty-dashboard package.
1775650,2018-09-18 08:28:50 UTC,"Change abandoned by Luka Peschke (<email address hidden>) on branch: master
Review: https://review.openstack.org/575103
Reason: Not needed anymore (new version of the client)"
1775658,2020-11-04 17:19:19 UTC,Somehow related to bug LP: #1902913
1775672,2018-07-26 08:48:33 UTC,Using ...
1775672,2018-08-25 01:00:32 UTC,I'm suffering with this again. Is the work around really to turn off boot protection?
1775672,2018-08-15 07:11:19 UTC,"The same problem with redirection to /dev/null seems also to be present in /usr/lib/dkms/common.postinst, causing hangs on upgrades..."
1775672,2018-08-28 12:28:08 UTC,I've struggled through this several times now. I don't have a definitive solution but the general routine was something like this. When you asked to enroll the machine owner key to sign the kernel module there is an interface that popups up and waits for user input. I tried this in in a shell-only session and in a gnome session several times. In both cases the process that spawns the window gets stuck in a child process and I think it was sent to a different tty altogether. One time I accidentally recover the interface by killing all the login window session processes while I was in a trying something else in a shell session. When i jumped back everything redrew and there was a new window that asked me to enroll the MOK key password.
1775672,2018-07-27 09:30:51 UTC,"My current workaround is to remove the redirection of /usr/lib/dkms/dkms_autoinstaller's stdout to /dev/null in /etc/kernel/header_postinst.d/dkms.  This may even be the correct fix: it's a little noisier, but not unacceptably so and it's definitely better than a hung installation."
1775672,2018-07-20 23:02:25 UTC,"The problem is that the DKMS hook in virtualbox-dkms starts a whiptail dialog explaining that a new signing key will be enrolled in the MOK database, but this dialog does not get displayed, which is why the system appears to hang."
1775672,2018-06-07 18:01:46 UTC,FWIW:
1775672,2018-06-08 02:31:44 UTC,My workaround was to set up the upstream VirtualBox PPA and install the packages from there:
1775672,2018-06-07 21:37:16 UTC,"I am having the same problem. Ubuntu 18.04 installed with Windows 10 as dual boot. Secure boot enabled. The system has been working for years like this (since before 16.04). I have updated to every release since and it was working on all of them. It even worked on 18.04 before the latest kernel update. I suspect a work around could be to downgrade to a previous kernel or to disable module signing, but we should not have to."
1775672,2018-06-07 20:53:21 UTC,"After working on this a bit more, this problem is probably caused by Secure Boot being enabled on my dual-boot (w/ windows 10) system."
1775672,2018-06-07 18:00:40 UTC,"After killing the hung apt process I ran dpkg --configure -a , which hung again.  Killing the hung dpkg process and running dpkg --configure -a  again allowed the package installation to complete but resulted in a broken module:"
1775672,2018-07-20 22:42:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775673,2020-07-11 17:28:31 UTC,"Thank you very much again, Lucas!"
1775673,2020-07-11 17:16:45 UTC,FYI uploaded:
1775673,2020-07-14 15:25:02 UTC,"Hello Jean, or anyone else affected,"
1775673,2020-07-11 17:09:41 UTC,"First, you'd not need to bump the version to 1.4.9-1build3ubuntu0.18.04.2, we have not uploaded 1.4.9-1build3ubuntu0.18.04.1 yet. And the SRU bug template is good IMO, good job!"
1775673,2020-07-21 19:33:32 UTC,This bug was fixed in the package ruby-ncurses - 1.4.9-1build3ubuntu0.18.04.1
1775673,2020-07-21 19:33:37 UTC,"The verification of the Stable Release Update for ruby-ncurses has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1775673,2020-07-14 18:34:21 UTC,Thanks Robie!
1775673,2020-07-11 16:21:46 UTC,"Thanks very much again, Lucas!"
1775673,2020-07-11 15:23:10 UTC,"Marked invalid for tpp. tpp has a dependency on ruby-ncurses, and the bug is in ruby-ncurses (not tpp itself)."
1775673,2020-07-10 22:34:14 UTC,"Thank you very much for the detailed review, Lucas!"
1775673,2020-07-10 18:38:59 UTC,"Thanks for the patch and the steps to reproduce the bug Iain! I played with it and it indeed fixes the package and now I can ""require 'ncurses'"" in Bionic."
1775673,2020-06-16 21:21:38 UTC,"This is a debdiff for Ubuntu 18.04 (bionic) applicable to ruby-ncurses 1.4.9-1build3. I built this in pbuilder and it builds successfully. I installed it, the patch works as intended."
1775673,2020-06-14 13:24:43 UTC,This ruby-ncurses bug causes sup-mail to crash in Ubuntu 18.04 with the following error:
1775673,2019-01-25 12:25:15 UTC,"The attachment ""Patch for ruby-ncurses to also link libmenuw"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1775673,2019-01-25 11:08:14 UTC,"The attached patch also links against libmenuw, which provides set_menu_win."
1775673,2018-09-28 09:04:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775673,2020-07-11 14:11:44 UTC,"Your patch looks much better now, thanks Iain! I made some small changes in your changelog and uploaded it to a PPA [1] for testing purposes:"
1775674,2018-06-10 04:34:32 UTC,ack that exceedingly long list - thanks for being so thorough :)
1775690,2018-06-07 19:20:01 UTC,"Reference, where a compute node fails to register as a hypervisor, yet the Juju status is green:
https://bugs.launchpad.net/charm-nova-compute/+bug/1771662"
1775690,2018-07-27 12:57:34 UTC,"To be honest, if the compute service fails to register correctly, should it not shutdown? Then service state is an accurate representation of ready-ness."
1775692,2018-06-07 19:40:09 UTC,"This is happening on version 0.4.5, the most fresh version of mojo available in snap store."
1775692,2020-01-30 09:30:48 UTC,This has been fixed (focal is now the latest supported series)
1775702,2020-10-12 18:48:18 UTC,I found that C:\Program Files (x86)\SPICE Guest Tools\drivers\Balloon\w10\amd64/blnsvr.exe intensively requesting something in WMI-provider-host. And there are a lot of errors in event logs about it also.
1775702,2020-10-13 06:20:46 UTC,"Gannet, SPICE Guest Tools is certainly a different problem, you should report that to the spice project instead. And since the original problem was apparently fixed via hv_synic / hv_stimer (if I got the comments right), I'm closing this ticket now."
1775702,2018-08-23 10:23:44 UTC,"hv_synic && hv_stimer only reduces the cpu from 40-50% to 4-5%.
still expecting under 1% like linux guests."
1775702,2018-08-22 15:24:46 UTC,"I ran into similar issues with Windows 10 (1803), with regard to 2D graphics performance."
1775702,2018-08-01 06:43:46 UTC,This bug affect me
1775702,2018-08-23 03:31:03 UTC,"Hi,
proxmox users have reported this bug
https://forum.proxmox.com/threads/high-cpu-load-for-windows-10-guests-when-idle.44531/#post-213876"
1775709,2020-04-09 20:27:16 UTC,"I can reproduce with the latest git build.
The key seems to be moving the mouse very slowly, probably triggering a case where only one pixel gets drawn instead of a line"
1775709,2020-04-09 21:35:41 UTC,Same thing happens for the Pencil tool when clicking outside the selection
1775709,2020-04-13 01:41:29 UTC,Fixed by https://github.com/PintaProject/Pinta/commit/4fbef3172323cb18659acb314deaad5ca0b3a73a
1775712,2018-06-07 23:46:55 UTC,"Yes sorry I just noticed the ""perhaps"" in that sentence. You weren't
ass-hat-ish, I apologize."
1775712,2018-06-07 23:34:15 UTC,"1) perhaps try running the windows version of unetbootin? sometimes there's trouble writing to mbr on linux systems. 2) if that one still doesn't work, try reformatting your USB drive as fat32 from windows? the fact that there's some phantom grub install on the usb drive seems troubling and suggests the formatting tool didn't actually format the MBR. the bootloader installed to the MBR has always been syslinux, grub is only used on EFI systems, and I'm assuming by netbook you mean a pre-EFI system 3) you could try an older version of unetbootin from https://github.com/unetbootin/unetbootin/releases say 638 if it is indeed a regression, I wouldn't expect so because I don't believe I've modified anything relating to bootloader installation but you could try"
1775712,2018-06-07 23:08:29 UTC,"root@pizone:~# apt install syslinux
Reading package lists... Done
Building dependency tree
Reading state information... Done
syslinux is already the newest version (3:6.03+dfsg-14.1+deb9u1).
syslinux set to manually installed."
1775712,2018-06-07 23:16:34 UTC,"Sorry for multiple posts, things have changed slightly..."
1775712,2018-06-07 22:01:29 UTC,"is this unetbootin for windows, macos, or the linux version? it doesn't even use grub, syslinux is the bootloader. did you perhaps use the linux version and ignored the ""please install syslinux"" warning?"
1775712,2018-06-07 23:05:17 UTC,"No, I would not have ignored that message if it was displayed to me... It
was not displayed to me..."
1775717,2019-11-03 21:17:13 UTC,Regarding 2) :
1775717,2019-11-03 13:12:21 UTC,whl2:
1775717,2019-11-03 11:02:18 UTC,"Ubuntu 19.10, kernel 5.3.0-19-generic - still the same."
1775717,2019-09-01 21:25:48 UTC,"Well, no. It didn't help. Full throttle after 12 minutes."
1775717,2019-09-01 21:15:42 UTC,"> ASUS relased new BIOS version - 307 - https://www.asus.com/uk/ROG-Republic-Of-Gamers/ROG-
> G752VT/HelpDesk_BIOS/
> Can someone check it?
"
1775717,2019-09-01 14:32:03 UTC,"ASUS relased new BIOS version - 307 - https://www.asus.com/uk/ROG-Republic-Of-Gamers/ROG-G752VT/HelpDesk_BIOS/
Can someone check it?"
1775717,2019-07-29 10:38:39 UTC,"oh, sorry.
not fixed."
1775717,2019-07-16 08:33:02 UTC,Does it need to provide more information?
1775717,2019-05-30 18:14:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775717,2019-04-27 10:25:32 UTC,"> I think you already have tried to take the fans by fancontrol.
"
1775717,2019-04-27 10:24:38 UTC,"> Does anyone know is it reproducible with ubuntu 19.04?
"
1775717,2019-04-26 19:22:34 UTC,Does anyone know is it reproducible with ubuntu 19.04?
1775717,2019-04-20 15:00:17 UTC,I think you already have tried to take the fans by fancontrol. I thought if fancontrol works on this laptop then you just need to add a service to stop fancontrol service before suspend and start it again after suspend after small delay.
1775717,2019-03-19 22:03:59 UTC,Just for the record - 18.10 with 4.18.0-16-generic has this bug as well.
1775717,2019-11-04 20:22:35 UTC,Regarding 1) :
1775717,2019-07-29 07:05:22 UTC,"ubuntu 18.04.2 - can't reproduce.
fixed now?"
1775717,2020-04-25 17:05:57 UTC,Does anyone know is it reproducible with ubuntu 20.04?
1775717,2021-01-27 14:41:08 UTC,"""blacklist=nouveau modprobe.blacklist=nouveau""
Really? With what video driver i supposed to work then?"
1775717,2020-04-27 05:59:08 UTC,"Please add 'dyndbg=""drivers/pci/* +p""' to the kernel parameter, run ""sudo powertop --auto-tune"", wait for 5 seconds, then attach dmesg here."
1775717,2018-08-30 06:07:19 UTC,i also has the same issue with the same laptop and kernel
1775717,2021-01-26 12:55:23 UTC,[    5.528682] nouveau 0000:01:00.0: DRM: Disabling PCI power management to avoid bug
1775717,2021-01-24 18:31:25 UTC,Two more words: bug occurs irrespective of what video drivers present. Now (unlike in comment #95)  i reproduced it against nouveau video driver (it was against nvidia before).
1775717,2021-01-24 18:24:59 UTC,"OK, issue is still reproducible. I should appologize that i havn't gathered it before.
Anyway, below you can find dmesg's only with dyndbg=""file drivers/pci/* +p enabled for two cases:
1) fans are OK - all files with suffix 1
2) fans are at max error state - all files with suffix 2"
1775717,2020-10-28 20:19:06 UTC,The issue is still reproducible under 20.10 i.e. under kernel 5.8.0-26-generic
1775717,2020-10-26 16:13:37 UTC,Does anyone know is it reproducible with ubuntu 20.10?
1775717,2020-07-28 06:15:56 UTC,Comment #96? Please don't include EC debug message.
1775717,2020-07-25 08:31:02 UTC,any progresss? What else information needed to comtinue?
1775717,2020-06-20 14:15:17 UTC,sudo prime-select intel fixed it for my Acer Nitro 5.
1775717,2020-06-01 02:36:36 UTC,"PC3 will be really hot, it should normally reach PC8."
1775717,2020-05-31 20:55:09 UTC,It seems the fan speed became uncontrolled once the temperature is too high. Even though it became lower in near future. see attach
1775717,2020-05-30 16:20:06 UTC,what about the substitution of powertop?
1775717,2020-05-24 13:10:22 UTC,"Just dyndbg=""file drivers/pci/* +p"" please."
1775717,2020-05-24 11:27:01 UTC,"Also tried to gather powertop-related issues for further analysis, however, wasn't able to do it completely:"
1775717,2020-05-24 10:14:06 UTC,"This is quite reproducible on all versions of ubuntu up to 20.04.
Please, find the appropriate issue for kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=153281"
1775717,2020-04-26 22:19:33 UTC,"> Does anyone know is it reproducible with ubuntu 20.04?
"
1775717,2018-08-25 18:38:15 UTC,"To my utter disappointment, it happens in both 4.18.5 and 4.4.5. Last one is really weird - I'm 100% sure that it didn't happen in Ubuntu 16.04. Now I'm going to downgrade the whole distro to 16.04 LTS and see."
1775717,2018-06-12 21:58:26 UTC,"Well, the fans just went 100% on kernel 4.4.14-040414-generic after about a day of normal operation.
Any advice on what other information to collect?"
1775717,2018-08-12 23:03:04 UTC,whl2:
1775717,2018-06-15 09:15:21 UTC,apport information
1775717,2018-06-15 09:15:20 UTC,apport information
1775717,2018-06-15 09:15:19 UTC,apport information
1775717,2018-06-15 09:15:17 UTC,apport information
1775717,2018-06-15 09:15:16 UTC,apport information
1775717,2018-06-15 09:15:15 UTC,apport information
1775717,2018-06-15 09:15:22 UTC,apport information
1775717,2018-06-15 03:39:19 UTC,Can you run `sudo powertop -C out.csv` and attach out.csv here?
1775717,2018-06-14 09:45:22 UTC,apport information
1775717,2018-06-14 09:45:21 UTC,apport information
1775717,2018-06-13 23:31:04 UTC,"whl2, please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1775717"
1775717,2018-06-08 14:03:49 UTC,"Hi Joseph,"
1775717,2018-06-07 22:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775717,2018-08-20 01:00:37 UTC,"Regarding 2) - no 3d-party fan software on 16.04.
3) - running on 4.4.5-040405-generic now, but not for very long, can't be sure yet if the issue is still present or not."
1775717,2018-06-14 09:47:23 UTC,"Or should it be done with standard Ubuntu kernel, not mainline?"
1775717,2018-06-15 09:15:23 UTC,apport information
1775717,2018-06-08 13:44:18 UTC,Does the bug go away if you boot back into the 16.04 kernel?
1775717,2018-06-15 09:15:25 UTC,apport information
1775717,2018-08-12 15:02:48 UTC,"For the record - dropped all 3d-party fan-controlling software, issue still present with mainline kernel 4.16.18 and nvidia driver 396.51.
Wasn't lucky enough to boot 4.18-rc<latest>"
1775717,2018-07-03 14:59:03 UTC,With nouveau driver and 3d-party software dropped (asus_fan.ko and nbfc) the issue is the same.
1775717,2018-07-03 09:27:11 UTC,"Regarding 2) - I've managed to install nouveau driver with reasonable performance, will post in a while if the issue is reproducible."
1775717,2018-07-02 22:31:40 UTC,"Christopher,"
1775717,2018-07-02 22:00:37 UTC,whl2:
1775717,2018-06-21 03:19:15 UTC,"The Package C-State stays at PC2, which causes lots of heat. It should be able to hit PC8.
C2 (pc2); 58.3%
C3 (pc3);  0.0%
C6 (pc6);  0.0%
C7 (pc7);  0.0%
C8 (pc8);  0.0%
C9 (pc9);  0.0%
C10 (pc10);  0.0%"
1775717,2018-06-15 20:51:03 UTC,"Hi Christopher,"
1775717,2018-06-22 18:04:22 UTC,"Hi Kai-Feng,"
1775717,2018-06-15 09:17:10 UTC,powertop results
1775717,2018-06-15 09:15:33 UTC,apport information
1775717,2018-06-15 09:15:31 UTC,apport information
1775717,2018-06-15 09:15:29 UTC,apport information
1775717,2018-06-15 09:15:27 UTC,apport information
1775717,2018-06-15 09:15:26 UTC,apport information
1775717,2018-06-15 09:40:17 UTC,whl2:
1775717,2018-06-15 09:15:24 UTC,apport information
1775724,2019-09-20 09:50:13 UTC,I had a look at a simple service snap: xkcd-webserver
1775724,2019-09-20 09:51:08 UTC,"Dear reporter, can you please clarify this aspect: Is this bug about ability to wait for network-online.target?"
1775724,2019-09-20 12:37:43 UTC,"Hey Zygmunt, I'm not really sure, its been more then a years since I reported the bug so I don't really recall details. The gist of the bug is a chicken-and-egg problem between systemd-networkd (which expects upon start to receive a response from the 240.102.0.1 nameserver of lxd) and lxd which needs network provided by systemd-networkd. In detail, this is written out in the last 3 comments of the relevand lxd issue, please see https://github.com/lxc/lxd/issues/4631#issuecomment-397438786 and the two comments below. Basically, I'm forced to use a workaround that goes like this"
1775729,2018-06-08 00:29:47 UTC,"Update - I was able to get Firefox 64-bit to print the footers on both sides, by selecting Page Setup on the Print Preview screen, then selecting ""US Letter"" at the top of the menu. It apparently saved something (hard drive activity), then footers printed on both sides of double-sided pages."
1775732,2019-05-14 20:04:20 UTC,"@Ryan: Is this still a problem w/ 4.15? Do you need a full OpenStack setup to reproduce it, or is just a single node nova model enough?"
1775732,2018-12-12 15:28:22 UTC,4.19 appears to fix this problem
1775732,2018-06-08 00:30:07 UTC,This change was made by a bot.
1775732,2018-08-09 17:02:51 UTC,"Just curious if you made progress with the bisect?  If you need, I can assist with the bisect and build test kernels for you."
1775736,2020-04-15 12:03:27 UTC,"This was removed from the glance docs in train by Change-Id: I65952f70f0216d227ca14d1098d264208913e4e5
probably because it depends on show_multiple_locations.  Check with Abhishek about whether it's worth correcting in the stable branches."
1775736,2020-08-27 19:18:50 UTC,"Reviewed:  https://review.opendev.org/724335
Committed: https://git.openstack.org/cgit/openstack/glance_store/commit/?id=65ccf371c76fc0e2a7cb26c6bae479552a77caac
Submitter: Zuul
Branch:    master"
1775737,2019-09-02 13:32:49 UTC,https://github.com/juju/juju/pull/10584
1775737,2019-10-02 11:52:20 UTC,https://jenkins.juju.canonical.com/job/github-make-check-juju/1296/testReport/junit/github/com_juju_juju_worker_raft/TestPackage
1775737,2019-10-02 11:52:41 UTC,Seems to still be happening
1775740,2018-06-11 09:10:41 UTC,"AFAIR update-status will ""fix"" config automatically. But it's still a valid bug of course, refresh_rules.sh should be improved."
1775747,2018-06-08 02:25:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775747,2020-11-16 08:26:59 UTC,Zero crashes after 18.04 so consider it fixed.
1775754,2018-06-08 06:43:07 UTC,"By the way, I just tested it and csysdig works if compiled with liblua instead of libluajit. Maybe the i386 build should default to that."
1775756,2018-06-16 14:08:19 UTC,the problem is in /usr/share/initramfs-tools/hooks/kmod
1775756,2018-06-16 14:05:43 UTC,"this is the content of the the comment on the line of cp is for me
#!/bin/sh -e
# Copy the compatibility symlinks until initramfs-tools will be converted
# to use the kmod program."
1775756,2018-06-16 14:03:54 UTC,"this problema was resolv thje problem was in the file /usr/share/initramfs-tools/hooks/kmod, tha have a aditional line that ""cp -a   /sbin/modprobe /sbin/rmmod $DESTDIR/sbin/"" generate the error in the script  , that for this reasons all process that execute this script was fail, i put the line in comment and all working without problem"
1775758,2018-06-08 13:50:08 UTC,Please look at the source url that you linked before filing bugs as this has already been fixed.
1775758,2018-08-02 03:05:29 UTC,"Brian,"
1775758,2018-08-02 07:18:51 UTC,"I think this is a duplicate of #1783306 for which the master fix is in, but the queens backport has not merged yet:
https://review.openstack.org/#/c/571384/"
1775758,2020-12-04 16:34:21 UTC,Review has merged
1775759,2018-06-08 09:21:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/573639"
1775759,2018-06-08 09:22:00 UTC,See https://github.com/kubernetes/kubernetes/issues/44165
1775764,2018-06-08 13:38:22 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1775764,2018-06-13 09:06:11 UTC,Yes the bug still exists in: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17.1/
1775764,2018-06-08 05:30:06 UTC,This change was made by a bot.
1775764,2018-08-16 06:24:06 UTC,Possibly related to (causing) bug 1773875
1775764,2018-06-13 03:04:45 UTC,"This bug has existed for as long as I remember. I do not know of any kernel version that didn't have it, but at the same time I have only been trying for a year or less."
1775778,2018-06-22 12:48:29 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1775778,2018-06-22 13:20:21 UTC,"Marc,"
1775778,2018-06-22 19:28:32 UTC,"Hi,"
1775782,2019-04-25 12:37:14 UTC,"@Abhishek: I don't doubt that you tested this, I thought it was working, too.  I think it has to be tested in a completely clean environment (which is why I didn't mess with trying both --config-file and --config-dir in the exec statement in the systemd file).  There also could be an element of randomness depending on the order oslo.config reads the files, though it was systematically bringing up the API on the registry port in my environment."
1775782,2019-04-25 12:50:06 UTC,Probably need to revert devstack change https://review.openstack.org/#/c/625628/
1775782,2019-04-26 10:06:58 UTC,"As I mention in comment #1,"
1775782,2018-06-08 10:22:32 UTC,"Workaround:
we can fix this issue by changing ExecStart mentioned in /<email address hidden> unit file to"
1775782,2018-06-08 16:36:04 UTC,"Taken into consideration that we don't currently support nor encourage anyone running under wsgi mode either mod_wsgi nor uwsgi , I'd say the priority for this bug is very low, specially as you mentioned in your comment the fix needs to happen in Devstack rather than in Glance."
1775782,2019-08-22 13:45:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678015"
1775782,2019-04-01 14:32:28 UTC,"This bug is fixed in devstack by rosmaita.
Please refer https://review.openstack.org/#/c/625628/"
1775782,2019-04-01 15:59:01 UTC,"Actually, I don't think this is fixed. Re-opening."
1775782,2019-04-01 16:15:20 UTC,This is a real bug.
1775782,2019-04-01 16:23:06 UTC,"@Abhishek: forgive me for asking, but are you sure that just changing the --config-dir as you mention in comment #2 is enough to get this working?"
1775782,2019-04-01 17:12:18 UTC,"Hi Brian,
I have tested that, it was working, and sure it will work."
1775782,2019-04-25 12:32:17 UTC,"We need to reopen this.  I couldn't get devstack to start earlier this week (with a cherry-pick of my don-t-use-uwsgi patch) because glance-api kept timing out when stack.sh was checking to see if the API was available.  Turns out that the API was being started on the same port as the registry (19191, I had tls-proxy enabled; g-api should be listening on 19292).  I think that just telling oslo-config what directory to look in is not specific enough, and it's reading the DEFAULT/bind_port from the wrong file (could be it's reading all the files, and since r > a, the registry setting wins.)"
1775782,2018-12-03 16:24:30 UTC,Just to add a slightly different perspective on this:
1775783,2018-08-20 14:27:33 UTC,"Works for me, but...."
1775783,2018-08-20 14:57:14 UTC,"Not my case. I haven't built any gnupg before and from results of `locate gnupg` and `find -name ""*gnupg*""` there seem no relevant files. Indeed this issue occurred after I upgraded from 16.04 to 18.04."
1775783,2019-07-15 03:29:20 UTC,"Okay, I finally realized that it was my self-built libgcrypt that causes the issue."
1775784,2019-09-20 09:18:26 UTC,"Test blacklisted, patch:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=ca9bfef38fe6bf4189b173a7530e8c9dad597111"
1775784,2019-09-20 08:18:51 UTC,"The issue tested by LTP testcase inotify08 has been fixed by commit:
   764baba80168 (""ovl: hash non-dir by lower inode for fsnotify"")"
1775784,2019-08-29 09:07:21 UTC,"Test passed with B-generic, seems to be fixed by stable update:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=cd3d03d0464212ebc0d1315c19d3077477e0c048"
1775784,2019-08-27 11:22:22 UTC,"Passed with X-4.15 Azure
 tst_test.c:1108: INFO: Timeout per run is 0h 05m 00s
 inotify08.c:149: INFO: mntpoint/ovl/test_file ino=45058, dev=0:49
 inotify08.c:160: INFO: mntpoint/ovl/test_file ino=45058, dev=0:49
 inotify08.c:111: PASS: get event: wd=1 mask=00000004 cookie=0     len=0
 inotify08.c:111: PASS: get event: wd=1 mask=00000020 cookie=0     len=0
 inotify08.c:111: PASS: get event: wd=1 mask=00000008 cookie=0     len=0"
1775784,2018-06-08 10:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775784,2018-11-15 10:40:25 UTC,"For the commit mentioned in the test case:
 *     The problem has been fixed by commit:
 *       764baba80168 ""ovl: hash non-dir by lower inode for fsnotify"""
1775784,2018-07-24 09:34:56 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1775784,2019-03-28 04:31:14 UTC,Didn't see this on C P8/P9 anymore.
1775792,2018-08-29 15:16:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775829,2018-10-08 15:08:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775833,2018-06-08 12:47:23 UTC,"This only seem to happen under load, so it really looks like a race condition during the restart. Guessing the daemon finishes processing requests before it terminates."
1775833,2018-06-08 22:53:56 UTC,I noticed the same issue on some of our unbound servers as well on Ubuntu 16.04. I agree that it's some kind of race condition since it only seemed to happen on some of our servers and not all of them even though they are all configured identically.
1775833,2018-06-08 22:57:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775833,2018-06-09 07:02:51 UTC,"Same here, 4 unbound instances, all but one crashed during the update. The last one wasn't under load during the restart"
1775841,2018-06-10 05:30:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775842,2020-03-14 12:54:05 UTC,"Hi, thanks for the report. This issue is being discussed in https://gitlab.com/inkscape/inbox/-/issues/562."
1775842,2018-07-24 22:20:55 UTC,"More details - Using Wacom Intuos Pro, and a mouse. That's about it."
1775846,2018-06-08 13:37:04 UTC,Message:
1775846,2018-08-21 22:40:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775854,2018-06-08 14:05:35 UTC,See the associate question for more details on this issue
1775854,2020-05-11 16:18:54 UTC,"The file leshouches.inc is correct and the assignment of the JAMP2 looks correct as well.
The best idea is a screw up in addmothers.f -> assigned to me"
1775854,2020-05-11 18:33:19 UTC,"Hi Valentin,"
1775856,2018-07-02 08:28:24 UTC,This bug was fixed in the package linux - 3.13.0-153.203
1775856,2018-07-26 05:13:52 UTC,This bug was fixed in the package linux - 4.15.0-29.31
1775856,2018-07-02 08:29:08 UTC,This bug was fixed in the package linux - 4.4.0-130.156
1775856,2018-07-02 08:27:55 UTC,This bug was fixed in the package linux - 4.15.0-24.26
1775856,2018-07-02 08:27:17 UTC,This bug was fixed in the package linux - 4.13.0-46.51
1775856,2018-06-14 11:01:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1775856,2018-06-13 11:03:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1775856,2018-06-13 07:01:34 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'."
1775856,2018-06-08 14:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775856,2018-06-15 10:33:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1775862,2018-06-08 14:50:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775862,2018-07-05 16:58:31 UTC,Are there any plans to release magnum-ui as part of the Ubuntu cloud archive repository?
1775862,2018-07-05 23:55:04 UTC,*** This is an automated message ***
1775870,2019-09-26 20:28:16 UTC,Fix rolled into https://bugs.launchpad.net/evergreen/+bug/1845556
1775870,2019-07-09 15:23:04 UTC,"The only place it is currently working is item status. However, it prints the labels in the opposite order than the item status list. So if list is :"
1775870,2019-07-09 15:04:59 UTC,It's still not working from Item Buckets or Holdings View - we are working with Adam to get those sorted before signing off.
1775870,2019-07-09 14:43:58 UTC,"Dan - yes, the whitespace was fixed as part of the overall layout updates"
1775870,2019-05-23 20:19:54 UTC,I did not observe the whitespace issue #4. Has this been resolved?
1775870,2019-05-23 20:18:11 UTC,Behavior is as expected.
1775870,2019-05-06 19:15:18 UTC,"Adam, your commit seems to have a lot of line changes that are only whitespace differences. That makes it a bit hard to see the real code changes. Are you able to push a new branch without the whitespace changes?"
1775870,2019-02-13 18:04:31 UTC,"The new code removes the random sort order of the labels, and sorts them in ascending order into the interface in the order in which they were populated from first to newest. If a user changes the sort order on a column in the grid supplying the copies to the interface (e.g. Barcode, Call Number, etc.), then those sort parameters become the order for sorting the copies."
1775870,2018-06-08 15:25:37 UTC,** Note - the random sort order does not appear as bad with upstream test data.  I wonder if the items are being sorted by database id or something?
1775871,2018-08-09 13:45:15 UTC,"Looks like this could be https://bugs.chromium.org/p/chromium/issues/detail?id=530482. Can you please have a look and confirm whether this is the same issue? If not, would you mind filing an upstream bug at https://crbug.com/ and sharing the link here?"
1775871,2018-08-09 15:33:24 UTC,"I confirm it is the same issue, issue related to zone identifiers, RFC6874."
1775876,2019-11-28 07:33:29 UTC,"I confirm that the bug is still present on Ubuntu 18.04
$ cat /etc/issue
Ubuntu 18.04.3 LTS \n \l"
1775877,2018-08-27 21:37:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775881,2019-11-29 18:36:34 UTC,New Report: 1854534
1775881,2019-11-29 18:19:28 UTC,apport information
1775881,2019-11-29 18:19:29 UTC,apport information
1775881,2019-11-29 18:19:31 UTC,apport information
1775881,2019-12-08 18:40:30 UTC,apport information
1775881,2019-11-29 18:02:30 UTC,I am still seeing this problem as of Ubuntu 18.04.3 LTS.
1775881,2019-12-08 18:40:35 UTC,apport information
1775881,2019-12-09 01:30:12 UTC,This change was made by a bot.
1775881,2019-12-11 02:52:49 UTC,apport information
1775881,2019-12-11 02:52:48 UTC,apport information
1775881,2019-12-08 18:40:33 UTC,apport information
1775881,2019-11-29 17:51:36 UTC,apport information
1775881,2019-12-11 02:52:45 UTC,apport information
1775881,2019-11-29 17:51:33 UTC,apport information
1775881,2018-08-09 21:07:08 UTC,demesg.txt
1775881,2018-08-09 21:06:21 UTC,I apologize. I updated my system and am still seeing this problem. Here are the results.
1775881,2018-06-22 02:15:17 UTC,Also:
1775881,2018-06-22 02:15:03 UTC,"Now that you have a workaround, please log into the system and run:"
1775881,2018-06-22 02:12:43 UTC,"I think you mean ""the installation disc was able to do it automatically""."
1775881,2018-06-21 17:20:15 UTC,"Mr. van Vugt,"
1775881,2018-06-21 02:10:26 UTC,"Next, please try uncommenting this line (remove the #):"
1775881,2018-06-21 02:08:47 UTC,Thanks. So it is a:
1775881,2018-06-21 01:59:33 UTC,I did as requested; here is the output.
1775881,2018-06-13 03:20:58 UTC,Assigning to mutter/gnome-shell as that provides the login GUI.
1775881,2019-11-29 17:51:35 UTC,apport information
1775882,2020-08-19 14:14:38 UTC,I wonder if this might be a good way to start on this:
1775882,2018-06-18 15:45:49 UTC,Interesting idea - how would you envision that working with multiple locations that all have different closed dates?
1775882,2018-06-18 16:32:36 UTC,"That's a good question, Terran.  It seems like there would need to be a mapping between specific OUs and specific Google My Business Locations,"
1775885,2020-12-03 23:15:36 UTC,Hi Mieke
1775885,2020-12-01 12:10:30 UTC,"Does implementing the suggestion made in https://bugs.launchpad.net/evergreen/+bug/1093856
solve this issue?"
1775885,2019-09-05 17:26:01 UTC,Confirming still an issue in 3.3.3
1775885,2020-08-07 18:22:53 UTC,This continues to be an issue in 3.5
1775890,2019-12-07 23:41:37 UTC,"It looks like yubikey-luks-open is included, it is just in /usr/lib instead of /usr/bin.  Which is confusing because I downloaded the package source and the debian/rules files indicates it should be putting it in /usr/bin.  Maybe because it isn't executable in the source?  Also the debian/control file indicates a dependency on expect, which is needed, but that does not show up in the package."
1775896,2018-06-12 18:38:52 UTC,"I made a pull request
https://github.com/systemd/systemd/pull/9260"
1775902,2018-06-08 18:19:00 UTC,Pour la couleur j'ai testé l' ajout dans ubuntufr.less
1775902,2018-06-09 08:20:02 UTC,Merci Fabux!
1775903,2018-06-10 04:32:11 UTC,we could - we would perhaps want them to open task manager to check it's closed - maybe some small app we seed
1775910,2018-06-08 19:00:04 UTC,This change was made by a bot.
1775918,2018-07-05 17:53:35 UTC,Correction: 4.15.0-24-generic not 4.15.0-25.
1775918,2018-07-05 17:49:30 UTC,It looks like the display issue in Bionic on the GL703VD laptop has been fixed with the release of the 4.15.0-25-generic kernel.
1775920,2019-05-24 17:39:07 UTC,"I have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>"
1775920,2019-04-28 17:19:58 UTC,"I created a branch for this, called user/sandbergja/lp1775920-item-status-menu-option-consistency"
1775920,2019-08-01 14:53:56 UTC,"Works for me. Pushed to master, rel_3_3, and rel_3_2. Thanks, Jane and Dawn!"
1775920,2018-10-16 20:21:04 UTC,"Just a note that as of 3.2.0, the following menu items are also missing from the Detail View:
* Show in Catalog
* Add > Item Alerts.
* Edit > Manage Item Alerts."
1775923,2018-06-08 22:56:52 UTC,"When attempting to decrypt a message, these messages show up in syslog:"
1775923,2018-08-19 08:15:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775923,2018-08-19 08:24:49 UTC,"I had the same type of problem when attempting to decrypt using gpg2 on a remote host, logged in via ssh from Ubuntu 18.04 client. Turned out that GPG2 was unable to ask for passphrase via X-forwarding. I got it working by disabling X forwarding (""ssh -x .."" or ""unset DISPLAY""), which triggers a text-only pop-up asking for passphrase in the terminal."
1775923,2018-09-21 14:43:15 UTC,"I have this problem testing Cosmic as well. In fact it is a problem both when using a virtual tty (alt-cntl-F2 for example), and when using ssh."
1775923,2018-09-24 01:49:28 UTC,I've been looking into this for the last couple of days.
1775925,2018-06-08 20:09:37 UTC,attachment syslog
1775925,2018-06-19 19:54:07 UTC,"This is strange.  It almost looks like somehow ubiquity thinks it is switching to the partman page twice, and launching two competing instances of partman:"
1775926,2020-01-30 08:29:32 UTC,"…and neither WhatWG nor its governing body, IETF, seemed interested in drafts for an amendment."
1775926,2020-01-30 08:28:31 UTC,The upstream bug report (https://bugzilla.mozilla.org/show_bug.cgi?id=700999) was closed as RESOLVED WONTFIX because they want to follow the proposal for URLs by WhatWG which doesn’t mention link-local IPv6 address specifiers.
1775926,2020-01-30 08:26:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775934,2020-11-16 17:53:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/762903"
1775934,2020-11-16 17:50:31 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/762899"
1775934,2020-11-16 17:38:42 UTC,"Reviewed:  https://review.opendev.org/756404
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c895d3e6bca562225d70e8f81255f38970f7fcda
Submitter: Zuul
Branch:    stable/stein"
1775934,2020-10-06 21:51:46 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/756404"
1775934,2020-10-06 02:28:23 UTC,"Reviewed:  https://review.opendev.org/752279
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=efc35b1c5293c7c6c85f8cf9fd9d8cd8de71d1d5
Submitter: Zuul
Branch:    stable/train"
1775934,2020-09-16 17:10:31 UTC,"A few months ago, I saw a duplicate of the root cause of this issue downstream [1] where a failure during _set_vm_state_and_notify (example: MessagingTimeout) prevents us from setting the cell_id for an InstanceMapping and destroying the BuildRequest."
1775934,2020-09-16 16:30:23 UTC,"Per last comment #8, looks like the bug is legit."
1775934,2018-07-31 22:18:30 UTC,"After even more code examination, I find that even build requests should not need to lazy-load a flavor because the serialized instance object primitive is stored in the build request 'instance' field in the database. So when we look up build requests to show in a server list, they should all have flavor attributes ready to go, and not need to lazy-load. So I'm back to the drawing board as to why a lazy-load is happening in your environment."
1775934,2018-07-31 21:53:55 UTC,I'm going to rewrite my comment because I think the last paragraph I wrote is wrong.
1775934,2018-07-31 21:08:26 UTC,"I was just looking at this bug again and I think I have a theory how this happened, based on code inspection and a recent IRC discussion with mriedem and dansmith about how instances end up in cell0 without their instance mapping cell_id set to cell0."
1775934,2018-06-18 23:59:43 UTC,Yeah this is where we'd put the instance into ERROR state:
1775934,2018-06-18 23:56:53 UTC,Why would the vm and task state still be set when the instance is in cell0? Shouldn't it be in ERROR vm_state with task_state=None? Might indicate something about why the instance mapping isn't updated to have a cell mapping:
1775934,2018-06-08 22:46:12 UTC,This is where we will send 'flavor' as one of the attributes to pre-load when querying for instances in all cells:
1775934,2018-06-08 22:37:50 UTC,Same instance data plus instance_extra for the instance from penick: http://paste.openstack.org/show/u61jzSxy3y3k9ri496Ms/
1775936,2018-06-08 21:42:42 UTC,Do any streaming servers or clients even support FLAC?
1775936,2018-06-09 08:39:10 UTC,"UPnP (DLNA)
https://askubuntu.com/questions/187086/how-do-i-set-up-live-audio-streams-to-a-dlna-compliant-device"
1775939,2018-06-09 00:17:44 UTC,This is fixed in Debian package 1.4.6-2.
1775939,2018-06-09 18:02:01 UTC,"I filed a sync request in bug 1776012 and in the meantime, I backported the latest Debian package into my PPA: https://launchpad.net/~fmarier/+archive/ubuntu/ppa?field.series_filter=bionic"
1775939,2018-07-18 07:57:17 UTC,I am astounded that Canonical has let a bug in a security-related package languish for over a month.
1775939,2018-08-23 09:23:38 UTC,"Currently there are over 29000 source packages in the Ubuntu archives for just bionic, most of which are in universe. It is *impossible* to timely manage all of those packages with the resources we have, which is why 'main' packages are the ones that we try to maintain for the most part. rkhunter is a package in *universe* so the MOTU team should be mainly responsible for taking care of its updates. Similarly, the SRU team also cannot always handle every incoming request instantly - we're doing what we can but there's just a lot of work in all packages of all components.
Remember it is not just 'Canonical'. Ubuntu is more than just 'Canonical'."
1775939,2018-08-30 08:13:39 UTC,Many of us would be more sympathetic if we hadn't watched Canonical squander resources on Unity for years. Maintaining security-related software ought to have a high priority.
1775940,2020-07-22 18:11:08 UTC,"Pushed all the way to rel_3_3. Thanks, Jason and John!"
1775940,2019-11-13 09:30:06 UTC,Confirmed in Evergreen 3.3.2
1775940,2020-01-09 19:10:07 UTC,changing 'setQuery' to 'watchQuery' in archiveGrid seems to help.
1775940,2020-01-29 17:41:32 UTC,"We implemented the fix suggested by a.bellenir on our Evergreen 3.4 test server at CW MARS, and it fixes the issue for us. Below is a branch that implements this fix with signoffs:"
1775943,2019-05-11 22:49:58 UTC,Here it is where this is in the code the '-W'.
1775943,2018-06-13 04:37:43 UTC,"I faced with the same issue in Ubuntu 18.04.
There is no '-W' option in HA-Proxy version 1.6.3."
1775943,2019-05-11 22:35:24 UTC,I also find the same problem with Ubuntu 16.04. The problem seems to be related to the fact there is not '-W' option in haproxy. I manually remove the option from the run script the haproxy service start working.
1775943,2018-06-08 21:52:31 UTC,Relevant code line in haproxy.json.j2:
1775945,2018-08-14 15:00:51 UTC,Can you see if the fix was already sent to upstream table by testing the latest upstream stable 4.15 kernel:
1775945,2018-06-08 22:13:41 UTC,"O'h I forgot to mention it. After experiencing this problem, I tried a fresh install. This did not resolve the issue."
1775945,2018-06-12 21:01:31 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1775945,2018-06-12 21:02:01 UTC,Please ignore the first question.  You already indicated this is a regression.
1775945,2018-06-12 21:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1775945,2018-06-20 15:45:46 UTC,"Hi Joseph,"
1775945,2018-07-11 20:09:39 UTC,"Hi Joseph,"
1775945,2018-07-17 20:07:04 UTC,"Hi Joseph,"
1775945,2018-08-18 11:36:31 UTC,"Hi Joseph,"
1775945,2018-09-08 12:20:45 UTC,"Hi Joseph,"
1775945,2018-09-13 20:43:15 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1775945,2019-07-25 15:52:18 UTC,This has been resolved for me. I have not been experiencing any lid closing related lockups for the last half a year.
1775947,2018-07-26 16:30:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/586292"
1775947,2018-07-27 05:36:55 UTC,"Reviewed:  https://review.openstack.org/586292
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=4e2a957bf8aade0a766c9c9a1d6798e4cb71e86d
Submitter: Zuul
Branch:    master"
1775947,2018-07-10 15:02:44 UTC,I see this still happening in the Neutron check jobs. Here's an example:
1775947,2018-07-19 10:57:29 UTC,"I just spotted this issue again and it looks that volume device is not removed from this meta_data.json file:
http://logs.openstack.org/69/567369/15/check/tempest-full/528bc75/job-output.txt.gz#_2018-07-19_10_06_09_273919"
1775947,2020-07-22 14:10:04 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/742444"
1775947,2018-07-18 18:41:06 UTC,"Reviewed:  https://review.openstack.org/578765
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=eb70a96ee3f7e56dbf57aefa2a1aa768aeb559ab
Submitter: Zuul
Branch:    master"
1775947,2018-06-28 11:05:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/578765"
1775947,2018-06-29 00:23:19 UTC,"In  verify_empty_devices(),  we can check the non presence of specified tags ['nic-tag', 'volume-tag'] instead of no device so that if any other devices is there we do not keep trying in wait loop."
1775947,2018-06-28 11:07:39 UTC,"After some analysis of logs from failed run it looks for me that this ""exit code 137"" is because test reached timeout and was just cleaned.
I think that in  verify_empty_devices() method there is still some device existing and because f that this test is not finishing.
I don't know yet if that is volume or nic device which wasn't removed from this metadata properly but will investigate..."
1775947,2018-06-15 04:36:58 UTC,"Hi, yes i have tried this and got some test case failed in the tempest side. https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_device_tagging.py#L350"
1775947,2018-06-13 16:11:39 UTC,"It looks like it is some issue with tempest test probably.
For now it looks like it detaches interface and then ""too fast"" tries to get metadata on instance. It's in tempest/api/compute/servers/test_device_tagging.py"
1775947,2018-07-02 08:54:55 UTC,@slaweq This test is now passed on my environment. Can you please check the same on your environment or Is it still reproducable?
1775953,2018-10-23 19:37:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775953,2018-12-19 14:35:39 UTC,"Exactly the same for me! On 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux=Ubuntu 18.04 QtiPlot crashes if python is specified as scripting language. Modifying the QtiPlot.conf-file (ScriptingLang=python, MuParserCLocale=false,ForceMuParser=false) does not influence the behavior, ie, still muparser is the default scripting language."
1775956,2018-06-27 09:55:38 UTC,"Reviewed:  https://review.openstack.org/573871
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=fbddccd5f10a352880607f72804a42daf2d1b9fc
Submitter: Zuul
Branch:    master"
1775956,2018-07-27 13:22:41 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b3 development milestone.
1775961,2018-11-21 20:01:17 UTC,"Fixed in revision 6e77176d7666cfafbea8e939e3631b73ddb99d23
https://git.launchpad.net/kicad/patch/?id=6e77176d7666cfafbea8e939e3631b73ddb99d23"
1775961,2018-10-19 13:41:28 UTC,"Hello,
I'm in processing of porting my previous QFN Wizard with a lot more features than the new one, and I added the ""fillet"" handling because it's impossible without it to make arbitrary pad length."
1775961,2018-06-11 03:14:45 UTC,Makes sense.  I think this makes sense to address along with the rest of the python work during 6
1775961,2018-09-15 00:00:45 UTC,If the plan of @pointhi (hope this is his handle here as well) goes as planned then my qfn (and other footprint generators) should be easily transferred to the footprint wizard. Details about his plan here: https://forum.kicad.info/t/rfc-future-of-footprint-wizard-and-generator/12592 and here: https://github.com/pointhi/kicad-footprint-generator/issues/152#issuecomment-409978763 (plus other comments on the scripting repo)
1775961,2018-11-21 20:01:08 UTC,"@nat, I committed you patch to the development branch.  Thank you for contribution to KiCad."
1775965,2019-06-08 23:31:37 UTC,This bug was fixed in the package pysynphot - 0.9.12+dfsg-3
1775967,2020-01-23 15:22:24 UTC,"Good news, I've found a better workaround.
1) Edit ""/etc/default/grub"" and add ""thermal.off=1"":
GRUB_CMDLINE_LINUX_DEFAULT=""quiet splash thermal.off=1""
2) Run: sudo update-grub
3) Reboot"
1775967,2020-01-06 14:32:18 UTC,"For information, the bug still exists in Ubuntu 19.10 with kernel 5.3.0-24-generic. However, now, the faulty temperature appears as ""acpitz-acpi-0"" in ""sensors""."
1775967,2020-01-23 15:40:36 UTC,"I spoke too fast. This option only removes the faulty temperature, but doesn't prevent the system from overheating..."
1775967,2019-03-08 10:54:54 UTC,">> It should be fairly safe, but it's more power hungry.
"
1775967,2019-03-08 04:38:26 UTC,"It should be fairly safe, but it's more power hungry."
1775967,2018-10-04 19:12:37 UTC,"Sorry, I meant ""safe"", not ""same""."
1775967,2018-10-04 17:07:16 UTC,"If I use suspend-to-idle, the bug is gone! Is it same for me to use this mode instead of ""deep""?"
1775967,2018-06-12 20:31:39 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1775967,2018-07-26 17:30:29 UTC,"I've just tried several kernel versions, from 4.5.7 to 4.17.0, and the bug existed in all the versions that I tested."
1775967,2018-07-25 08:45:29 UTC,Can you also try older kernels and newer kernels? This might be a regression.
1775967,2018-06-13 12:04:39 UTC,https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775967
1775967,2018-06-09 06:00:06 UTC,This change was made by a bot.
1775967,2018-10-04 16:16:32 UTC,Do you see the same issue if you use suspend-to-idle? Run `echo s2idle > /sys/power/mem_sleep` before suspending the system.
1775970,2018-06-09 06:21:58 UTC,This issue occurred for OpenShot 1.4.3 operating in Ubuntu 16.04.4.
1775971,2018-09-14 14:23:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775971,2019-02-17 00:51:38 UTC,"I tried rebuilding the current 3.28.3 upstream source from git while atop of the 3.28.0 debian source via uupdate, e.g.:"
1775971,2019-02-17 00:53:51 UTC,"Forgot to clearly mention, I was building gpaste 3.28.3 on 18.04 LTS."
1775971,2020-10-22 20:01:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu."
1775971,2020-10-22 20:23:49 UTC,Unfortunately I don't use Ubuntu 18.04 at all anymore.
1775975,2018-06-09 07:35:48 UTC,I have the following mlt packages installed:
1775983,2018-06-09 09:02:33 UTC,Route: Trat zsr 191-193 ordinary it works but in time table before station Krasna nad Hornadom from Cierna nad Tisou Train number OS 8816. Thank you very much
1775992,2018-07-02 12:15:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775996,2020-08-10 00:31:59 UTC,kodi 2:17.6+git20180430.1623-final-0bionic
1775999,2019-08-27 09:23:54 UTC,Xubuntu 18.04 :
1775999,2018-06-21 23:30:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1775999,2018-06-21 23:31:36 UTC,"Same problem here, but with Xubuntu 18.04."
1775999,2018-06-24 00:28:14 UTC,Xubuntu 18.04 :
1775999,2018-08-06 17:48:20 UTC,You can downgrade to version 3.8.1-0ubuntu12 from the xenial repos and it will work on bionic.
1775999,2018-09-19 15:27:25 UTC,If someone has problem with this I found a solution without install gnome-control-center here:
1775999,2018-10-12 16:37:10 UTC,"I had that same issue with xubuntu after 18.04 upgrade. First install vino. Mine was removed on upgrade without any notice. Also even after installing vino, the command vino-preferences doesn't work. Here is an easy workaround. Install dconf-editor then open it and go to org-gnome-desktop-remote access and turn off encryption. There are also several other remote options you can set in dconf-editor. However until you install vino, the remote-access doesn't show in dconf-editor. I hope someone can explain what happened to vino-preferences."
1775999,2018-10-12 17:02:51 UTC,"The settings for vino got moved into the general gnome desktop
preferences, and vino-preferences was removed without thinking about
those of use who don't use gnome :("
1775999,2019-03-11 01:42:01 UTC,Same to Lubuntu and Mint
1775999,2019-03-11 09:53:13 UTC,You can use another vnc server that the GNOME one for those usecases...
1775999,2019-05-06 17:58:53 UTC,"Why ""low"", it's very annoying. Gone seems support for low end.."
1775999,2019-05-06 19:12:17 UTC,"Low because
- i doesn't impact the default Ubuntu Desktop
- it's easy to workaround by installing another vnc server"
1775999,2020-05-13 03:44:28 UTC,"Hello I also had the same problem but the cause was the desktop I use kubuntu 19.10 and obviously KDE desktop when installing came I saw the suggestion to install an additional program for wine which allows its configuration in gnome and when trying to install this program suggests installing all the gnome desktop hahaha, solution? install krfb which is for KDE and that's it."
1775999,2019-12-22 05:26:23 UTC,"I am disappointed vino is now incompatible with Lubuntu, apparently due to an arbitrary decision or possibly a simple oversight.  With respect, ""workaround by installing different software"" could be said of any bug."
1776000,2019-03-22 19:33:06 UTC,Thank you for helping to triage and sorry for the late response.  I no longer have as much time for Launchpad as I used to.
1776000,2019-02-11 04:42:22 UTC,"I was swamped with other stuff and wasn't able to respond in time.  I'll try catch, post the required information and then reopen."
1776000,2019-02-11 04:17:36 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1776000,2018-12-12 12:54:49 UTC,"Thank you for your bug report, what's the output of 'bluetoothctl'"
1776000,2018-12-12 12:55:15 UTC,sorry that's included in the description
1776000,2018-12-12 12:59:27 UTC,Could you include the journalctl log from around the time of the issue? Also start 'G_DEBUG_MESSAGES=all gnome-control-center bluetooth' from a command line and see what info are printed?
1776003,2018-06-12 20:04:30 UTC,"if i understand correctly, this should be fixed by branch lp1776003-show-circ-as-type-code (http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/abellenir/lp1776003-show-circ-as-type-code)"
1776003,2018-08-23 16:17:07 UTC,"I tested this and was not able to see a change in the 007 Physical Characteristics Wizard (search title -> MARC Edit -> right click on tags in grid and select ""Add 007"", click on the ""link"" icon to the right of the field), but I do see the codes in Circulate As Type in the item editor.  Perhaps there was some confusion about where the change needed to happen?"
1776003,2018-08-23 19:48:08 UTC,"Chris, thank you for clarifying. i'm still learning my way around."
1776003,2019-05-22 19:06:29 UTC,I've pushed a signoff and a follow-up that makes the code display in _all_ drop-downs in the wizard:
1776003,2019-05-22 22:07:27 UTC,Further confirmation that original bug has been successfully addressed. Tested on MOBIUS 3.3.0 for bug squashing.
1776003,2019-07-29 20:25:40 UTC,This works well for me.  Thanks to both of you!  I've pushed this to master so it can be included in 3.4.
1776005,2018-06-20 19:20:37 UTC,"Hello Joseph,"
1776005,2018-06-20 12:10:12 UTC,"Hello,"
1776005,2018-06-12 21:58:51 UTC,"I built a test kernel with a revert of commit 2f500a9d7ff6.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1776005"
1776005,2018-06-09 16:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776005,2018-06-09 16:04:38 UTC,"The apport log, after a successful boot on the 4.4.0-127-generic"
1776005,2018-06-12 10:26:42 UTC,"Hello,"
1776011,2018-06-11 12:21:44 UTC,"That sounds like a good idea, yes, although I'm not 100% sure whether SBCL should be signalling those. In any case, it seems straightforward to handle this on the CFFI side."
1776022,2019-12-04 10:28:50 UTC,Migrated to GL:  https://gitlab.com/inkscape/inbox/issues/1277
1776029,2018-06-09 20:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776030,2019-06-13 17:22:32 UTC,Commenters that have errors which talk about Unicode or ascii or codecs: Is be interested to hear if trying the latest Deja Dup snap (which bundles duplicity 0.8 which claims to fix that) helps:
1776030,2020-07-31 02:36:53 UTC,"For the first time, I also encountered the same issue. I'm in Ubuntu 20.04"
1776030,2019-07-12 10:35:12 UTC,#9:
1776030,2019-07-11 20:19:34 UTC,"Michael (#7):
18.04.2 x64:
I uninstalled deja-dup and duplicity then did what you suggested (snap install etc.).
It mostly solved the problem I had (#6).
Thanks!"
1776030,2019-06-10 11:10:01 UTC,I see something that looks *exactly* identical to the problem sambo63 has (#6):
1776030,2019-07-11 21:29:49 UTC,"Are those files you need backed up?  Otherwise, you can put them in the
""folders to be ignored"" list."
1776030,2018-12-31 15:53:55 UTC,I have exactly the same bug as described in the bug description.
1776030,2018-12-28 21:44:43 UTC,"Ran into the same, or similar, issue. It turned out the problem was caused by insufficient permissions. Found a solution here https://unix.stackexchange.com/questions/68079/mount-cifs-network-drive-write-permissions-and-chown"
1776030,2018-12-28 21:32:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776030,2019-06-08 05:09:25 UTC,Similar problem for me too.
1776035,2018-06-16 17:36:49 UTC,"Reviewed:  https://review.openstack.org/574042
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=2f38e07a38be59305c573311a04c8d4b6de5a912
Submitter: Zuul
Branch:    master"
1776035,2019-05-06 03:05:15 UTC,Sample failure in gate:
1776041,2020-06-23 13:06:40 UTC,"Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!"
1776044,2018-09-15 05:16:54 UTC,"I have the same issue, but I do have a GeForce 8200 integral on the motherboard.  I was happily running 16.04 with nvidia-304 driver. Upgraded to 18.04 and nvidia-340 (recommended driver) and the system hangs a few minutes after booting.  If I go into recovery mode and remove nvidia-340, all good."
1776044,2020-02-22 17:09:12 UTC,"I have a similar issue.  Installed Ubuntu 18.04 on a Ryzen 7 2700x with an old Geforce 8600 GTS.  Using the built-in drivers, the video card stalls (took me a long time to figure out it was the video card, after going through all the Ryzen issues).  I installed the nvidia-340 as recommended, and the system hangs on boot before the graphic login.  I removed the nvidia drivers, and reinstall the default, and it works again, but stalls.  I know this is the video stalling, as I can ssh into the machine, and all is working fine on the computer, just the video on the hardware is stalling."
1776050,2018-11-29 12:18:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776052,2018-06-10 08:30:04 UTC,This change was made by a bot.
1776056,2019-09-19 11:58:36 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1776056,2018-10-04 02:20:54 UTC,I added bug # 1796003  related to some of the original description here. related to the fact that container's link in the DNS tab is broken and not the actual enhancement part that would allow to edit the IP address of the container.
1776056,2018-06-20 01:20:45 UTC,"Also.. Thinking about it.  if MAAS is providing DHCP/DNS, MAAS should be able to control/assign DHCP and modify the child devices settings related to this.  At the end LXD/Juju are not typically used for setting DHCP if you are using a common unmanaged bridge.  you would have to be aware of the DHCP pool, which LXD/Juju are not if they are using MAAS."
1776056,2018-06-19 08:21:34 UTC,"I mean.. Right now I have to go to DNS page, search manually in the page for the particular ""Device"" name. If the link would work, I would get the Machine/Container tab page instead of the broken Devices link."
1776056,2018-06-19 08:12:33 UTC,"OK.. Editing is fine, understood that this is an added feature, should be done on LXD/Juju.
But what about search and the broken links?"
1776056,2018-06-18 03:46:30 UTC,"This is also problematic, since once a device is added as child (specifying the parent).. the device can't be deleted."
1776056,2018-06-19 03:28:51 UTC,"Hi Luis,"
1776056,2018-06-18 03:48:55 UTC,"Finally,
Maybe devices with a parent, should be listed as they are now in the containers tab, but also on the devices tab. so that you can search, delete, modify IP address, etc.  with an extra colum in the devices page indicating the parent.  Like this you can know where a child device is located (in which machine containers tab)"
1776056,2018-06-18 03:44:27 UTC,"This is not LXD specific.  If I add a device with parent as a machine (e.g. a KVM), it is specified in the containers tab also."
1776056,2018-06-19 03:29:55 UTC,"Also, please note that if LXD/Juju adds devices to MAAS, these should never be managed by the user, but rather, any changes should be done via LXD or Juju."
1776061,2018-10-19 07:03:19 UTC,"I think U need more information in gnocchi.conf.
I got a same error when deploying openstack(queens) by kolla-ansible and i solved this problem adding sacks_number to gnocchi.conf."
1776062,2018-06-17 07:46:40 UTC,Thanks for reporting.
1776064,2019-10-09 20:46:50 UTC,"I put this for future reference in case anyone is interested since I recently came upon the same problem. The solution is to change the dependency from ""python-imaging"" (which does not exist anymore) to ""python-pil"" (which is the replacement of python-imaging):"
1776064,2020-02-22 07:49:30 UTC,"@Germán Bassi As far as I can tell this workaround works. I could not fully test it, though as I lack time for this."
1776068,2018-12-20 16:14:43 UTC,"Strange, I have mokutil --sb-state
SecureBoot enabled"
1776069,2020-07-28 09:21:18 UTC,Do you still see the issue in newer Ubuntu series?
1776069,2018-09-06 19:41:00 UTC,@Jeb: so if I understand correctly the issue as initially reported cannot be reproduced any longer? Can it be closed?
1776069,2018-08-31 14:56:40 UTC,Ubuntu 18.04.1 LTS with Gnome as DE.
1776069,2018-09-06 15:08:45 UTC,"@Jeb: can you confirm that after killing and restarting gnome-software, you're seeing the same issue I describe?"
1776069,2018-09-06 15:08:11 UTC,@shock99er: yours is probably a different issue.
1776069,2018-09-06 15:38:05 UTC,"@olivier.tilloy, unfortunately my system is not in the same exact state as
it was in early June, so I cannot provide an answer knowing nothing else to
the system has happened between then and now."
1776073,2018-06-10 13:05:03 UTC,"I can't find an option to edit the report, so that I can add some more information, so I'll do it in a comment: Shutter does the above when I open Google Maps in street view mode in Chromium. If I stay away from street view mode, it works just fine."
1776073,2018-06-18 15:09:10 UTC,"Shutter returns log and error output to standard out, so please run it from terminal as"
1776074,2018-08-01 08:25:29 UTC,"indicator-datetime is the only package in Ubuntu 18.04 and older that recommends/depends on ubuntu-touch-sounds, no more packages uses ubuntu-touch-sounds, so, please make usage of ubuntu-touch-sounds in indicator-datetime optional for Desktop systems"
1776074,2018-08-01 05:41:07 UTC,"No. Touch sound is also used for desktop for ringtones and alarms. Removing touch-sound will end up indicator-datetime spamming syslog specially if it can't detects the type of system (i.e. phone or desktop). Removing touch-sounds requires dropping ""phone"" support in its code or similar considerable changes."
1776074,2018-07-31 17:19:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776078,2019-04-09 12:35:38 UTC,I ditched evolution and decided to switch back to Thunderbird
1776078,2019-04-09 12:18:03 UTC,Could you perhaps report it upstream on https://gitlab.gnome.org/GNOME/evolution/issues/ ?
1776083,2018-12-11 19:24:54 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1776083,2018-06-28 17:21:17 UTC,Sounds good to me.
1776083,2018-06-28 16:34:21 UTC,"@Jeff-  Personally, I like both: select all text and drop extra zeros."
1776083,2018-06-28 16:02:32 UTC,In case of change 0.300 to 0.350
1776083,2018-06-28 15:32:01 UTC,"@Seth, I'm not sure which way you're thinking of going here, but if you do want to implement the Mac-select-all algorithm you can just remove the conditional compilation lines around the selectAllInTextCtrls() call in DIALOG_SHIM::OnPaint()."
1776083,2018-06-10 23:01:32 UTC,Or we could uniformly implement the OSX UI paradigm which selects all when tabbing to text boxes....
1776084,2020-05-04 07:44:11 UTC,This looks like the machine already had been deleted. Maybe the UI was stale and didn't indicate this.
1776096,2018-10-29 19:03:55 UTC,"Hi, Cameron."
1776096,2018-06-10 18:12:59 UTC,"Sorry, more complete disassembly of the apparent actual fault:"
1776096,2021-01-11 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1776096,2020-11-11 15:01:23 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1776137,2018-06-11 02:58:11 UTC,"Hi there,"
1776137,2018-06-11 02:59:12 UTC,Note that this is the screenshot in comment #2. To fix this issue provide internet access to the machine so it can access the PPA.
1776137,2018-06-11 05:54:58 UTC,The TC can reach the internet and PPA.
1776137,2018-06-11 03:44:28 UTC,The TC can reach the internet and PPA.
1776137,2019-09-19 12:05:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1776150,2018-08-19 21:18:25 UTC,Was finally able to reproduce under valgrind with the OFX/QFX import plugin!
1776150,2018-06-11 06:04:14 UTC,"Also cannot reproduce under valgrind, which indicates that a race condition is to blame (it's running much slower there)."
1776150,2018-06-11 05:25:05 UTC,I've also noticed that this happens occasionally if I double-click on the line item itself - the whole dialog hangs.  It seems to be some kind of race condition since it's never the same item causing the problem twice.
1776154,2021-02-15 04:17:51 UTC,[Expired for lxqt-config (Ubuntu) because there has been no activity for 60 days.]
1776154,2020-12-17 04:03:29 UTC,Thank you for reporting this bug to Ubuntu.
1776155,2018-06-13 08:22:49 UTC,apport information
1776155,2018-06-13 08:22:44 UTC,apport information
1776155,2018-06-13 08:22:46 UTC,apport information
1776155,2018-06-13 08:22:47 UTC,apport information
1776155,2018-07-08 08:32:18 UTC,"Maybe the problem is the same (Ubuntu kernel not detecting the touchpad correctly), but the touchpads are different models, and so ubuntu responds differently to them."
1776155,2018-07-08 01:35:16 UTC,"Although I also have a ""cheaper-end slimline laptop/netbook"" with a non-working touchpad I don't think I'm having the same issue as you.  I see that your device appears in your /proc/bus/input/devices list so I gather it was installed but not working.  In my case, the touchpad isn't installed at all and does not appear in that list."
1776155,2018-07-07 21:33:43 UTC,"Ah. Well, that's not going to happen then. Maybe Jeffrey has a dual boot installation?"
1776155,2018-07-07 17:43:00 UTC,"Well, in Windows' device manager."
1776155,2018-07-06 23:14:45 UTC,How do you check that?
1776155,2018-07-06 18:49:57 UTC,"Which protocol does the touchpad use, PS/2 or HID protocol?"
1776155,2018-07-06 18:00:55 UTC,Kai-Heng:
1776155,2018-06-13 08:22:48 UTC,apport information
1776155,2018-07-06 17:19:10 UTC,Does the touchpad start to work after suspend/resume?
1776155,2018-06-13 09:06:56 UTC,Installing kernel 4.17.1 did not help:
1776155,2018-06-13 08:28:17 UTC,"@Joseph Salisbury, as specified in the OP this is a fresh install. Previous versions of Ubuntu (older than 18.04) will not boot on this latest generation of notebooks/netbooks at all due to Secure Boot."
1776155,2018-06-13 08:22:56 UTC,apport information
1776155,2018-06-13 08:22:54 UTC,apport information
1776155,2018-06-13 08:22:52 UTC,apport information
1776155,2018-06-13 08:22:50 UTC,apport information
1776155,2018-06-13 08:22:43 UTC,apport information
1776155,2018-06-13 08:22:41 UTC,apport information
1776155,2018-07-06 17:47:10 UTC,"No. It is, and has always been completely dead. Except on Windows 10, where it worked fine. I did not think to check on what make it was reported as under Win 10 device manager, unfortunately, before I installed Ubuntu 8.04 beta 2."
1776155,2018-06-13 08:22:39 UTC,apport information
1776155,2018-06-13 08:22:40 UTC,apport information
1776155,2018-09-04 09:53:09 UTC,"linux-headers-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-headers-4.17.0-1_4.17.0-1.2~lp1728244_all.deb
linux-image-unsigned-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-modules-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-modules-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb"
1776155,2018-08-21 10:23:06 UTC,"Yes, please do."
1776155,2018-08-20 19:38:01 UTC,Does not seem to be exactly the same. But do you suggest I try the same fix anyway?
1776155,2018-07-25 14:25:29 UTC,"Ah, I think this bug the same one as LP: #1728244, right?"
1776155,2018-10-10 13:33:51 UTC,Does anyone know when the patch in the official Ubuntu 18.04 kernel comes?
1776155,2018-07-21 16:03:11 UTC,"Please try v4.18-rc5. It contains this commit:
commit ef6eaf27274c0351f7059163918f3795da13199c
Author: Jason Andryuk <email address hidden>
Date:   Fri Jun 22 12:25:49 2018 -0400"
1776155,2018-07-21 18:03:24 UTC,Found something that might be interesting:
1776155,2018-06-13 08:22:37 UTC,apport information
1776155,2018-07-21 17:44:22 UTC,Hey! Thanks for following this up.
1776155,2018-06-12 21:30:14 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776155,2018-06-12 21:00:47 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1776155,2018-06-13 08:22:36 UTC,apport information
1776157,2018-07-15 02:09:45 UTC,"Hi Jochen. If I understand you correctly, you are setting up the MNet connection FROM Mahara TO Moodle?"
1776157,2019-05-25 05:05:41 UTC,"Since we are focussing on LTI for the connection to Moodle, changes to MNet are less likely. A replacement for Mahara to Moodle will need to be found."
1776158,2018-08-23 19:23:06 UTC,This bug was fixed in the package linux - 4.4.0-134.160
1776159,2018-06-13 10:13:05 UTC,"Hi,"
1776159,2018-06-12 20:32:23 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1776159,2018-06-11 07:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776160,2018-10-26 15:58:40 UTC,Hi @sunzuohua:
1776160,2018-08-29 07:18:14 UTC,"@Slawek Kaplonski,
1.Sorry, I take a mistake in bug title. My problem is with ingress.
2.Results I expect are as follows:
Change value of max-burst-kbp and not change value of max-kbps and use tc(tc show class dev qvocd3421e0-43) to check the config, the burst value in result of tc command should be changed and the Bandwidth test result should be diffrent."
1776160,2018-07-19 12:21:39 UTC,"For now I set it as ""incomplete"" but I will change it when You will provide informations which I asked in comment above."
1776160,2018-07-19 12:20:52 UTC,I was checking it on my devstack and I have couple of questions to You about it.
1776176,2019-04-23 11:45:49 UTC,"Hi - thanks for reporting this, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1776177,2018-08-23 19:23:06 UTC,This bug was fixed in the package linux - 4.4.0-134.160
1776177,2018-06-11 10:00:03 UTC,"List of previously applied patches:
  * Revert ""ima: limit file hash setting by user to fix and log modes"""
1776184,2018-09-06 06:13:42 UTC,should be fixed in 2.0
1776184,2018-06-20 07:17:11 UTC,any progress?
1776186,2018-06-11 20:49:51 UTC,"@Ronelle,"
1776186,2018-06-25 15:26:14 UTC,(triage) - discussed and determining next steps
1776186,2018-06-25 16:51:59 UTC,Related Review https://review.openstack.org/#/c/576053/
1776186,2019-03-07 13:19:26 UTC,"Re-opening this, the fix only takes care of one small part of the problem.
https://review.openstack.org/#/c/576053/"
1776186,2021-02-17 17:06:45 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1776186,2018-06-11 15:07:39 UTC,"(triage) - this is a nuanced issue, CI team is investigating"
1776186,2018-06-11 18:49:56 UTC,"From logs investigation, I think this a legitimate bug/observation."
1776200,2018-11-03 16:36:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776203,2018-06-12 13:44:13 UTC,"Thanks for the report, good catch. I made some additions."
1776205,2018-06-11 17:13:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/574349"
1776205,2018-06-11 17:14:56 UTC,The actual issue is that the relevant functions have migrated to the os-vif package in vif_plug_ovs.linux_net.
1776205,2018-06-12 08:57:42 UTC,"Reviewed:  https://review.openstack.org/574349
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=b4c89d067761cc134cb884f3356659eaa48b942f
Submitter: Zuul
Branch:    master"
1776208,2018-10-26 07:42:31 UTC,You should report this bug on the Debian side as the work is happening there.
1776214,2020-03-26 03:00:16 UTC,We only package LTS releases in Ubuntu.
1776225,2018-06-13 07:06:08 UTC,"seems the issue is gone after reinstalling lvm2, now I don't see any errors anymore"
1776225,2018-06-13 07:07:12 UTC,"re-installed lvm2 with purge option as per below URL:
https://www.devmanuals.net/install/ubuntu/ubuntu-16-10-yakkety-yak/installing-lvm2-on-ubuntu16-10.html"
1776235,2019-03-25 17:39:35 UTC,"In my case (vino on Ubuntu 18.04 and RealVNC viewer on Windows 7) I can only copy something from Windows to Ubuntu, but not back. Meanwhile vino 3.8.1-0ubuntu9.2 (this version info has been copied from another PC with Linux Mint with RealVNC Viewer) seems to be working."
1776237,2018-06-11 14:46:58 UTC,Submitted a patch for review: https://review.openstack.org/#/c/574281/
1776256,2018-06-13 19:28:28 UTC,Happy for you to do this.
1776263,2018-06-11 18:22:29 UTC,The kernel Bugzilla instance doesn't expose the email address:
1776263,2018-06-18 20:23:22 UTC,Two observations here — perhaps the second is more important.
1776264,2018-06-13 19:30:02 UTC,"I believe in other places we have said something like ""assumed that default state of applications exists"" - choose your wording."
1776266,2018-06-11 18:00:07 UTC,This change was made by a bot.
1776266,2018-06-11 21:30:17 UTC,"Addendum: Got lucky and the hardware was found at next boot. Does not happen often, though. For comparison, this is the dmesg log when it works as it should:"
1776266,2018-08-22 09:39:50 UTC,Did this issue return? Is it still happening sporadically?
1776266,2018-08-22 09:41:49 UTC,"Apologies, I see that yours is now in this state permanently too, and your also GRUB works fine (which is super annoying and proves that the hardware is capable of operating to some degree)"
1776266,2018-09-27 08:01:38 UTC,"Opened up the laptop and wiggled on the touchpad/keyboard ribbon cable. Problem is not gone, but definitely better. Seems like a hardware issue indeed. Why there are no problems with macOS is beyond me though. Somehow Linux has less tolerance for flaky connections?"
1776266,2018-12-27 21:24:23 UTC,"Last update for people finding this via google: Changed the ribbon cable from the touchpad to the motherboard. New cable has flaws as well, force-click is not working. :-| But no unresponsiveness anymore. So definitely a hardware issue."
1776266,2018-08-22 11:35:02 UTC,"Yeah, it's permanent now."
1776270,2018-06-11 18:43:11 UTC,"I also verified that this problem also applies to the latest (bionic+cosmic/amd64) build, 20140715-1build1."
1776271,2018-10-03 20:10:58 UTC,Hi !
1776271,2018-08-24 19:00:24 UTC,"May be similar to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1776271"
1776271,2018-09-14 09:55:15 UTC,"I had the same today, dist-upgrade to linux-headers-4.15.0-34 resulted in the same error as above."
1776271,2018-09-14 09:56:39 UTC,Sorry for double-paste.  Meant to copy this.
1776271,2018-09-14 10:39:28 UTC,"Update - a BIOS upgrade fixed this for me. HP Pavilion All-in-One - 23-q199na.
Perhaps this cleared the NVRAM."
1776271,2018-09-17 03:13:54 UTC,I'm also running into this issue on 18.04 (fresh install about 3 months ago)
1776271,2018-10-03 12:02:02 UTC,Same error after upgrade
1776271,2018-07-11 05:43:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776271,2018-10-03 17:37:18 UTC,"On Wed, Oct 03, 2018 at 12:02:02PM -0000, Luis Rodriguez wrote:

> root@node13:/boot/efi/EFI/ubuntu# efibootmgr -v
> BootCurrent: 000D
> Timeout: 10 seconds
> No BootOrder is set; firmware will attempt recovery
> Boot0000* CD/DVD Rom    VenMedia(0c588db8-6af4-11dd-a992-00197d890238,0c)
"
1776271,2018-10-04 01:43:50 UTC,"Also happened to me on an IBM rackmount System x3650 M3. I had a firmware
version to apply, flashing the firmware seems to have resolved it, at least
for now."
1776271,2018-10-04 01:56:43 UTC,"I had flashed the latest firmware a few months back, did you re-flash the same version or a new one?"
1776271,2018-10-04 03:01:22 UTC,"It was a new version. If you are able to reflash the same version, it may work, it doesn't seem to be related to a specific firmware version from what I can tell, I think something in the process of flashing the firmware enables the boot device to be updated properly."
1776271,2018-10-04 03:02:44 UTC,"I just need to do this:
sudo apt install --reinstall shim-signed
Thanks abssorb."
1776271,2018-10-04 03:23:19 UTC,"thanks,
this
sudo apt install --reinstall shim-signed"
1776271,2018-10-04 03:26:14 UTC,I also tried that before I flashed my firmware and got the same error.
1776271,2018-11-02 13:31:50 UTC,I have not been able to reboot my desktop in nearly two months.  What is the fix?  Do I have to reflash the BIOS?  How do I ensure the desktop is bootable after I reflash?  Thanks.
1776271,2018-10-04 01:20:37 UTC,"Sure, this is happening on an IBM Tower System x3400 M3"
1776271,2019-05-09 07:59:43 UTC,https://askubuntu.com/questions/1072618/could-not-prepare-boot-variable-no-space-left-on-device-grub-install-error-ef
1776271,2018-06-13 15:03:16 UTC,As requested:
1776271,2018-06-11 19:42:14 UTC,The error in your log is:
1776271,2018-06-12 18:11:23 UTC,"Hi,"
1776275,2019-11-11 13:15:00 UTC,"I started work on this feature.
And I have a idea - what about RC LPF(low-pass filter) and HPF(high-pass filter) calculator?
I think, need to create a separate tab for LPF and HPF."
1776275,2019-11-11 15:13:21 UTC,+1
1776275,2019-11-11 14:25:54 UTC,"@Jeff, yes the number of tabs is getting somewhat high. I was actually thinking of refactoring the PCB calculator code as well to split out the different tabs into their own form builder projects and classes (since currently a minor UI change seems to produce a diff that is ~500kb because of the UI files). When I do that we could also switch around the interface to a notebook style (since the calculator functions will be on wxPanels, it should be easy to go from one to the other)."
1776275,2018-06-15 12:24:51 UTC,"In the best case, being able to specify custom series would be a must (You may not have a full standard serie in stock, or have some strange values like in this Yageo samplebook found on Aliexpress that I have 0:) )"
1776275,2019-11-11 13:45:56 UTC,"Dmitry, please file a separate bug report for the filter tabs.  This bug report is specifically for the parallel/series resistor selector feature.  A separate bug report will make it easier to close out the bug reports."
1776275,2019-11-11 13:40:32 UTC,"Dmitry, yes the LPF and HPF should be a separate tab if you want to implement them."
1776275,2019-11-11 13:31:05 UTC,And one more question - should I work on LPF and HPF as part of this bug or need to create a separate one?
1776275,2019-11-11 14:14:39 UTC,"@Dmitry, I think I'd use a separate tab.  That being said, we're going to need to go from tabs to a list (like in Preferences) fairly soon as we're running out of room...."
1776295,2018-06-12 13:39:37 UTC,"Should you use ""stop-mode: sigterm-all"" instead? This will send the signal to all the tasks in the control group."
1776295,2018-06-12 14:00:22 UTC,"Using refresh-mode you can choose to ""endure"" the refresh or ""restart"" the app during the process. Using stop-mode you can choose how to stop the service. I'm not sure if that answers your question."
1776295,2018-06-12 14:02:23 UTC,"Still, is it by design that the services survive `snap disable` and `snap remove`?"
1776295,2018-06-12 14:02:35 UTC,"Right, so what I would like is on snap refresh, only sigterm is sent to the daemon process, ie, 'stop-mode: sigterm'.  But on snap disable/stop, all processes are killed, which really should be the default regardless of what stop-mode is set to because who would really want processes running from the snap when the snap has been stopped or disabled?"
1776295,2018-06-13 09:16:01 UTC,"I don't think systemd has such a feature. Refresh stops and starts services, we don't differentiate stop-to-refresh from stop-to-...stop."
1776295,2018-06-13 13:00:23 UTC,I have expanded this topic on the forum https://forum.snapcraft.io/t/different-outcome-for-snap-stop-foo-vs-systemctl-stop-snap-foo-service-refresh-vs-stop/5901
1776295,2018-06-13 13:23:36 UTC,"@zyga,"
1776295,2018-06-12 13:42:38 UTC,"Let's step back, what we (and I suppose others, too) would like to avoid with this is services getting killed/restarted on snap refresh."
1776299,2019-10-27 10:41:31 UTC,Thanks for reporting.
1776299,2018-08-30 21:03:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776299,2018-06-25 15:59:08 UTC,Please let me know if I can help facilitate releasing this package in any way. Thanks!
1776300,2019-10-27 09:46:33 UTC,libctl 4.1.4-3 is available in Ubuntu 19.04 and later.
1776300,2018-06-22 20:41:33 UTC,Please let me know if there's anything I can do to facilitate this process. Thanks.
1776300,2018-06-22 21:17:24 UTC,"Hi Christopher,"
1776302,2018-06-11 21:02:34 UTC,related error: https://sentry.ols.canonical.com/canonical/snapcraft-dashboard/issues/5276/
1776302,2019-04-15 21:25:00 UTC,"One thing is the store-side task just dying and leaving snapcraft spinning, and the other is the actual problem that caused this particular failure."
1776326,2018-06-12 06:39:01 UTC,Not vlc's fault if kodi does not have a dependency on libdvdread4. Reassigning to kodi.
1776329,2018-07-23 17:21:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776348,2018-06-22 07:01:58 UTC,The hwe-edge package became a meta only variant which points at the hwe binaries. Any ADT reports get attributed to the hwe package. So testing for hwe-edge will never get any results.
1776348,2018-06-29 03:43:49 UTC,This kernel is identical to linux-hwe
1776348,2018-07-02 09:12:55 UTC,The package has been published and the bug is being set to Fix Released
1776366,2018-11-01 23:34:37 UTC,status update: stein master (2018/11/1)
1776368,2019-10-13 21:10:01 UTC,This is resolved in 3.3 by the improvements to the hold shelf in 3.2.
1776368,2019-10-14 15:02:38 UTC,Marking as won't fix on the basis of Jennifer's comment.
1776369,2019-04-28 19:23:41 UTC,"There is no need to make the current selected layer visually on top of all layers. The visual order is the same, as in the layers panel on the right. But for the selection / editing would be a good idea to raise on top of all."
1776369,2019-04-28 19:25:06 UTC,"For the purpose of selecting the contents of the currently selected layer, there is a rather convenient H-contrast mode."
1776369,2019-05-17 12:38:22 UTC,"The *actual* reason for this bug report, identified by @Tomasz in #7 and verified by the OP @Fabián in #14, has been reported again in [1]. In an attempt to keep the noise to a minimum (allowing it to be fixed faster), I have marked this bug as the duplicate."
1776369,2019-03-23 05:34:04 UTC,"In my opinion, the increase in the variety of colors and the ability to adjust the transparency is more cosmetics and this diversity distracts from the design process of the PCB.
It would be better for the color palette to be limited and, since we have the front side and the reverse (opposite) side of the PCB, the color palette should be organized as follows: all colors on the spectrum to green (the middle of the visible spectrum) - for the front layer, after green - for the reverse layer.
In my opinion, the layers should be organized the way they are produced.
I see two options in the order of the layers. We have a two-dimensional canvas, but we want to somehow identify the two sides of the PCB. For both options, the order of the layers is the same! Text and pictures of the user should be at the top. Option 1. Belonging of layers to the front or rear side of the printed circuit Board is indicated by color and mirror reflection (when you move the element to the rear side, it is reflected horizontally, the color changes and its designation is also reversed) and so on. The elements of different sides of the printed circuit Board are arranged in the same order, but their belonging to one or another side of the printed circuit Board is indicated by opposing colors and horizontal reflection.
Option 2. same as option 1, but. Here you need to add buttons ""View front side of pcb"", ""View back side of pcb"". The order of layers is the same. But if the ""View front side pcb"" option is selected, all the layers of the front side of the PCB acquire a normal, direct order of the layers relative to the ""virtual canvas"", while the order of the layers of the back side of the Board is the same, but inverted relative to the ""virtual canvas"". A virtual canvas is a plane parallel to the sides of the printed circuit Board and located between them. Option 2 I think will be very convenient.
In kicad 407, I don't like the lack of uniformity in configuration."
1776369,2019-03-22 21:23:50 UTC,"The drawing order is here:
- active layer drawn always on top of other layers
- vias/pads on top of traces/zones
- front copper on top of back copper
- paste/adhesive/courtyard layers drawn below copper layers (to avoid cluttering pads of components,
- user/mechanical layers on top of copper (Dwgs_User, Cmts_User, Eco1_User, Eco2_User, Edge_Cuts)
- text back below copper layers
- text front on top of copper layers"
1776369,2019-03-23 05:51:17 UTC,"in option two, when you select one or the other display option according to it, all elements are reflected horizontally, but the colors remain the same."
1776369,2019-03-23 19:43:29 UTC,I've done a little work here. Maybe someone will be interested. See the attachment.
1776369,2019-03-23 19:50:15 UTC,Simple and powerful!
1776369,2019-03-24 05:41:38 UTC,And more. See the attachment.
1776369,2019-03-24 05:53:47 UTC,And more
1776369,2019-04-04 12:27:08 UTC,"@twlostow, yes that was the issue that initiated this bug report"
1776369,2019-04-28 11:04:23 UTC,See this forum thread: https://forum.kicad.info/t/usability-problems-by-dropping-legacy-toolset-v5-1-2/16620
1776369,2019-04-28 11:30:05 UTC,"I do not care for fancy colors and don't want to fiddle with transparancy settings, but pulling the active layer to the front almost forces users to fiddle with transparency settings to see other stuff on the PCB, especially when laying tracks. Setting the current (copper) layer to high transparency makes it vague on the monitor, which in turn promps for upping the brightness or saturation."
1776369,2019-04-28 12:07:52 UTC,Please watch the video
1776369,2019-04-28 12:23:15 UTC,"Perhaps the active layer that rises to the top makes it easier to choose, since its element is at the very top, but visually it is not very conveniently perceived. You can leave the mechanism and direct its influence not on the visual selection, but on the priority of the selection in the stack."
1776369,2019-04-28 12:26:31 UTC,"When there are several elements under the mouse, when you select it or press buttons (M, E and so on), an element is selected in a stack on the currently selected layer. The choice of the layer does not affect the display (does not make the element itself on top of the others)."
1776369,2019-04-28 12:30:23 UTC,"Simply put, all actions, such as selecting, moving, editing, and so on, can be applied only on the active layer, while all other elements on the inactive layers do not react to this at all (for inactive layers, all actions are disabled, blocked). This way I think the issue of applying actions over the elements of the layers when they are above each other is solved. In this case, visually raising the layer above all is not necessary."
1776369,2019-04-28 12:34:46 UTC,"It may seem to someone that in order to move one footprint notation you need to go to the silk screen layer - it is advisable to put all footprints first, then make the silk screen layer active and set their designations. A series of actions of the same type is performed much faster than a series of heterogeneous ones."
1776369,2019-04-28 15:42:56 UTC,"You can make two checkboxes in pcbnew settings:
1. Make current selected layer always on top in canvas.
2. Make contents current selectable layer editable and selectable only.
In high contrast mode option 2 always on (contents current selected highlighted layer editable and selectable only), independent of the checkbox 2."
1776369,2019-04-28 19:02:09 UTC,"Another demonstartion active layer mode versus H-button mode (high contrast mode)
Please watch the video"
1776369,2019-03-22 05:10:17 UTC,Hi there! I have the impression that there is a discussion of some graphic editor. Who can tell me on what principle the order of the layers is determined?
1776369,2019-04-28 18:26:20 UTC,"If you leave everything as it is and do not lift the currently selected layer on top of the rest, everything will be displayed in the order as in the layers panel on the right. Text and pictures will always be at the top, almost as if they were located on a real printed circuit board."
1776369,2018-06-14 00:56:15 UTC,"Yeah, layer transparency is the closest to the way the legacy canvas draw the layers, there is still the issue about the F.CtrYd layer, the first selection makes it stay on top of the F.Cu, which is nice but this action isn't necessary for the B.CtrYd layer."
1776369,2019-03-22 05:19:37 UTC,"The graphics editor is PCBNew? Yes, need more layers and more chaos in their order. Six is not enough..
."
1776369,2018-06-12 09:34:24 UTC,"I know this is not directly a comment on your opinion, but remember that the user can also set the opacity of layers."
1776369,2018-06-12 10:51:05 UTC,"I think there could be some value in having the user able to ""pin"" layers to the top in a certain order, so that they are always drawn over others, in that order."
1776369,2018-06-12 11:49:54 UTC,"The active layer is always drawn on top of the other layers.
And, as Nick said, layer transparency must be correctly set, according to your preferences."
1776372,2018-06-12 02:00:04 UTC,This change was made by a bot.
1776375,2018-07-30 16:48:28 UTC,This issue was fixed in the openstack/aodh 7.0.0 release.
1776375,2018-08-01 22:40:36 UTC,"Hello Seyeong, or anyone else affected,"
1776375,2018-08-01 22:41:15 UTC,Unsubscribing ~ubuntu-sponsors.
1776375,2018-08-02 12:33:44 UTC,"Hello Seyeong, or anyone else affected,"
1776375,2018-08-07 02:54:36 UTC,I tried to deploy bionic env for verifiying. but there are some issue on juju deployment.
1776375,2018-08-07 08:39:10 UTC,Hello
1776375,2018-08-14 05:10:14 UTC,"Hello,"
1776375,2018-08-15 02:20:51 UTC,This bug was fixed in the package aodh - 6.0.1-0ubuntu1.1
1776375,2018-06-12 02:41:58 UTC,https://review.openstack.org/#/c/574339/
1776375,2018-07-24 05:22:06 UTC,"Hello,"
1776375,2018-08-27 07:55:48 UTC,please ignore above msg. confused it.
1776375,2018-09-19 07:16:58 UTC,The verification of the Stable Release Update for aodh has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1776375,2018-09-19 07:17:01 UTC,"This bug was fixed in the package aodh - 6.0.1-0ubuntu1.1~cloud0
---------------"
1776375,2018-09-19 07:18:25 UTC,The verification of the Stable Release Update for aodh has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1776375,2018-09-19 07:18:27 UTC,"This bug was fixed in the package aodh - 5.1.0-0ubuntu1~cloud1
---------------"
1776375,2020-02-12 15:00:22 UTC,Ocata is a few days off EOL so marking bug task as won't fix.
1776375,2018-08-15 02:20:59 UTC,"The verification of the Stable Release Update for aodh has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1776375,2018-07-23 20:26:43 UTC,This bug was fixed in the package aodh - 6.0.1-0ubuntu4
1776375,2018-08-27 02:05:35 UTC,sorry I missed pike-proposed.
1776375,2018-07-23 19:37:53 UTC,"Hi Seyeong,"
1776375,2018-07-23 20:15:48 UTC,"Hello Seyeong, or anyone else affected,"
1776375,2018-06-12 08:45:23 UTC,"Reviewed:  https://review.openstack.org/574339
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=471437e4559259957021d81dd8cbd432f0116933
Submitter: Zuul
Branch:    master"
1776375,2018-06-13 00:45:56 UTC,"Added cloud-archive, we need this back-ported to Pike"
1776375,2018-06-13 01:43:50 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/574935"
1776375,2018-06-13 01:44:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/574936"
1776375,2018-06-13 01:45:28 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/574937"
1776375,2018-06-15 04:54:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575615"
1776375,2018-06-15 04:54:56 UTC,"Change abandoned by Seyeong Kim (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/574936"
1776375,2018-06-15 04:55:00 UTC,"Change abandoned by Seyeong Kim (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/574937"
1776375,2018-06-12 04:05:19 UTC,"Subscribed field-high, this bug is blocking at least one customer plus possibly others that don't know it yet."
1776375,2018-06-22 17:48:11 UTC,"Seyeong,"
1776375,2018-06-25 06:50:46 UTC,Hello Corey
1776375,2018-06-25 13:05:33 UTC,Thanks very much Seyeong!
1776375,2018-07-06 09:05:15 UTC,"Reviewed:  https://review.openstack.org/575615
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=e923493e4feec239c9fe9b58736960a40e373bee
Submitter: Zuul
Branch:    master"
1776375,2018-07-06 09:15:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/580586"
1776375,2018-07-06 10:31:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580602"
1776375,2018-07-06 10:33:19 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/580603"
1776375,2018-06-15 04:55:12 UTC,"Change abandoned by Seyeong Kim (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/574935"
1776375,2018-07-06 11:34:10 UTC,"Reviewed:  https://review.openstack.org/580586
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=91c094529fc3d825421e2e5e3839d8946c91ae94
Submitter: Zuul
Branch:    stable/queens"
1776381,2020-03-26 03:06:50 UTC,It's not currently failing based on recent logs anyway.
1776381,2018-06-14 04:19:39 UTC,Is there anything that I can do for debugging this?
1776381,2018-06-14 08:26:00 UTC,"On Thu, Jun 14, 2018 at 04:19:39AM -0000, Po-Hsu Lin wrote:

> Is there anything that I can do for debugging this?
"
1776381,2018-06-12 11:33:43 UTC,"On Tue, Jun 12, 2018 at 12:46 PM, Free Ekanayaka
<email address hidden> wrote:

> It might be a duplicate of https://github.com/lxc/lxd/issues/4485 (which
> is fixed in 3.0.1, now in -proposed I believe).
"
1776381,2018-06-12 10:46:23 UTC,"It might be a duplicate of https://github.com/lxc/lxd/issues/4485 (which is fixed in 3.0.1, now in -proposed I believe)."
1776381,2018-06-12 06:39:08 UTC,"If you leave it there for a long period, it will time out in the end:
make[1]: Leaving directory '/tmp/autopkgtest.ZiY11u/build.Nic/src'
FAIL: lxc-tests: lxc-test-api-reboot (9845s)
---
Terminated
---"
1776381,2018-06-12 11:36:02 UTC,"On Tue, Jun 12, 2018 at 8:39 AM, Po-Hsu Lin <email address hidden> wrote:

> If you leave it there for a long period, it will time out in the end:
> make[1]: Leaving directory '/tmp/autopkgtest.ZiY11u/build.Nic/src'
> FAIL: lxc-tests: lxc-test-api-reboot (9845s)
"
1776385,2018-06-12 07:32:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/574614"
1776390,2018-06-12 05:56:11 UTC,"StacktraceTop:
 __assert_fail_base (fmt=0x7f867c4947d8 ""%s%s%s:%u: %s%sAssertion `%s' failed.\n%n"", assertion=assertion@entry=0x7f86767a2660 ""!xcb_xlib_threads_sequence_lost"", file=file@entry=0x7f86767a24cb ""../../src/xcb_io.c"", line=line@entry=259, function=function@entry=0x7f86767a2908 <__PRETTY_FUNCTION__.14350> ""poll_for_event"") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f86767a2660 ""!xcb_xlib_threads_sequence_lost"", file=file@entry=0x7f86767a24cb ""../../src/xcb_io.c"", line=line@entry=259, function=function@entry=0x7f86767a2908 <__PRETTY_FUNCTION__.14350> ""poll_for_event"") at assert.c:101
 poll_for_event (dpy=dpy@entry=0xdc5000) at ../../src/xcb_io.c:256
 poll_for_response (dpy=dpy@entry=0xdc5000) at ../../src/xcb_io.c:274
 _XEventsQueued (dpy=dpy@entry=0xdc5000, mode=mode@entry=1) at ../../src/xcb_io.c:349"
1776391,2019-06-01 11:00:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776391,2020-03-23 03:47:13 UTC,"Please run `sudo apport-collect 1776391` to collect debug info for this bug. Do you mean the while wifi interface is gone, or just the applet icon is missing?"
1776398,2018-06-25 07:09:53 UTC,"@Andy,"
1776398,2018-06-25 10:23:38 UTC,Hi Audrey.
1776398,2018-06-25 20:02:42 UTC,ok. I didn't understand issue correctly.
1776410,2018-06-12 16:19:23 UTC,"When the code was designed and written it was fine and that was never an issue.
Need to understand why there would be a deviation and add code to support it."
1776412,2019-02-26 13:40:16 UTC,Is this still an issue?
1776412,2019-02-26 14:00:40 UTC,"AFAIK, yes"
1776416,2018-06-15 11:12:39 UTC,"Have the same problem with HP ProBook 430 G4.
Linux 4.4.0-127-generic – works"
1776416,2018-06-15 11:39:39 UTC,Sound also fails with Linux 4.4.0-130-generic.
1776416,2018-06-15 12:33:04 UTC,"Also tested several mainline builds from http://kernel.ubuntu.com/~kernel-ppa/mainline/:
v4.4.128 (4.4.0-127-generic) – sound works.
v4.4.134 (4.4.0-130-generic) – sound works.
v4.4.137 – sound works."
1776416,2018-06-15 13:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776416,2018-06-15 16:16:41 UTC,"user@user-P65-67HSHP:~$ apport-collect 1776416
You need to run 'sudo apt-get install python-apport' for apport-collect
to work.
user@user-P65-67HSHP:~$ 1
1: command not found
user@user-P65-67HSHP:~$ sudo apt-get install python-apport
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
   javascript-common libjs-jquery python-apt python-crypto python-dbus
   python-gi python-httplib2 python-keyring python-launchpadlib
   python-lazr.restfulclient python-lazr.uri python-oauth
python-problem-report
   python-secretstorage python-simplejson python-wadllib
python-zope.interface
Suggested packages:
   apache2 | lighttpd | httpd python-apt-dbg python-apt-doc
python-crypto-dbg
   python-crypto-doc python-dbus-doc python-dbus-dbg python-gi-cairo
python-fs
   python-gdata python-kde4 python-keyczar python-testresources
   python-secretstorage-doc
The following NEW packages will be installed
   javascript-common libjs-jquery python-apport python-apt python-crypto
   python-dbus python-gi python-httplib2 python-keyring python-launchpadlib
   python-lazr.restfulclient python-lazr.uri python-oauth
python-problem-report
   python-secretstorage python-simplejson python-wadllib
python-zope.interface
0 to upgrade, 18 to newly install, 0 to remove and 7 not to upgrade.
Need to get 1,301 kB of archives.
After this operation, 6,617 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
javascript-common all 11 [6,066 B]
Get:2 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 libjs-jquery
all 1.11.3+dfsg-4 [161 kB]
Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64
python-apt amd64 1.1.0~beta1ubuntu0.16.04.1 [139 kB]
Get:4 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64
python-problem-report all 2.20.1-0ubuntu2.18 [9,666 B]
Get:5 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
python-httplib2 all 0.9.1+dfsg-1 [34.2 kB]
Get:6 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
python-keyring all 7.3-1ubuntu1 [43.7 kB]
Get:7 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
python-lazr.uri all 1.0.3-2build1 [13.6 kB]
Get:8 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
python-simplejson amd64 3.8.1-1ubuntu2 [60.4 kB]
Get:9 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
python-wadllib all 1.3.2-3 [28.2 kB]
Get:10 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
python-zope.interface amd64 4.1.3-1build1 [81.0 kB]
Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
python-oauth all 1.0.1-5 [12.9 kB]
Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
python-lazr.restfulclient all 0.13.4-5ubuntu1 [50.7 kB]
Get:13 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64
python-launchpadlib all 1.10.3-3ubuntu0.1 [45.6 kB]
Get:14 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64
python-apport all 2.20.1-0ubuntu2.18 [79.5 kB]
Get:15 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64
python-crypto amd64 2.6.1-6ubuntu0.16.04.3 [246 kB]
Get:16 http://gb..."
1776416,2018-06-15 16:41:14 UTC,"Did this: 'apport-collect 1776416'. Then was asked you need to run 'sudo apt-get install python-apport' for apport-collect to work. Output attached to email: Re: [Bug 1776416] missing required logs 15/06/18 17:16. Sorry, I didn't how to post the output here as newbie."
1776416,2018-06-17 07:32:07 UTC,"A computer is 50% useless without sound. You don't seem to be in hurry
to roll this back to end my misery. This is the second time this has
happened, the first had to be fixed by an engineer. Seriously thinking
of using Windows, or seeing an engineer again because of your update.
The thing I miss about Windows is the ability to 'Go Back' to a previous
session. PC Specialist whom built my high-end machine warned me not to
use Linux..."
1776416,2018-07-13 09:58:10 UTC,"Same here. I fix would be great. I haven't tried to boot with older headers though, maybe you'll get some sound back @surfsecret ?"
1776416,2018-07-13 10:48:19 UTC,"Sound working again thanks to an engineer. Apparently, the sound drivers need to be updated. Would have hated to use Windows 10 as their updates are dreadful."
1776416,2018-08-28 09:43:16 UTC,"> Sound working again thanks to an engineer
"
1776416,2018-06-12 10:06:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776416,2018-08-28 10:27:31 UTC,"Well, if the drivers were being updated automatically with a system
update they weren't for me."
1776426,2018-07-27 13:22:55 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b3 development milestone.
1776429,2018-07-05 19:38:12 UTC,Note: For testing I used openstack-origin=cloud:xenial-pike.
1776429,2018-06-12 08:12:06 UTC,"I would like to share with you the output of both CLI
$ cinder ( python-cinderclient )
and
$ openstack ( python-openstackclient )"
1776429,2018-06-28 13:28:04 UTC,"Hi Miguel,"
1776429,2018-06-28 16:55:30 UTC,Does recreation of this bug require use of an older openstack-dashboard with newer endpoints?
1776429,2018-06-28 16:56:19 UTC,Marking Incomplete for now until we can get more details for how to recreate.
1776429,2018-06-29 07:20:40 UTC,"What version of OpenStack are you hitting this on?
This is the information I got from the Cloud:
    Ubuntu 16.04 (Xenial)
    OpenStack Pike
        SDN: Neutron, OVS & VXLAN
        Block & Object Storage: Ceph
        Architecture:
    Juju 2.3.5
    MAAS 2.3.2"
1776429,2018-06-29 07:27:41 UTC,"App                  Version  Status   Scale  Charm                Store       Rev  OS      Notes
openstack-dashboard  12.0.2   active       3  openstack-dashboard  jujucharms  258  ubuntu"
1776429,2018-07-05 19:35:38 UTC,"Hi Miguel,"
1776429,2018-07-12 23:14:00 UTC,"Hello Corey,"
1776429,2018-07-16 14:42:16 UTC,"Miguel,"
1776429,2018-07-16 15:26:10 UTC,"Another question is, did this start to occur after an upgrade to Pike?"
1776443,2018-06-27 04:46:14 UTC,"Thanks for your comment, Kai-Heng, but I did try the latest upstrem kernel at the weekend. Please refer to my post #8."
1776443,2019-05-18 01:47:19 UTC,"On 17/5/19 1:14 am, Kai-Heng Feng wrote:

> Sorry for the late reply. Does this happen on generic kernel?
>
"
1776443,2019-05-16 15:14:43 UTC,Sorry for the late reply. Does this happen on generic kernel?
1776443,2019-05-07 00:04:05 UTC,"After upgrading to 19.04 disco, the system is still too unstable to be useful. The current kernel is 5.0.0-13-lowlatency (buildd@lcy01-amd64-020)."
1776443,2018-07-24 09:11:34 UTC,"Is anything happening with this bug report? Are you waiting for me to do something more, or provide more information."
1776443,2019-05-21 07:27:34 UTC,I installed the 5.0.0-15-generic kernel and removed iwlwifi from the /etc/modprobe.d/blacklist. The system was stable and ran very well for 4 or 5 hours.
1776443,2018-06-27 02:50:38 UTC,Please give #3 a try...
1776443,2018-06-12 20:35:05 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1776443,2018-06-15 08:13:15 UTC,"Joseph... I also thought I had mentioned this a quite a new machine, so it doesn't have a lot of history. However, I had a similar wifi failure quite often with the latest 17.10 kernel before the upgrade to 18.04."
1776443,2018-06-15 07:55:25 UTC,"I won't confuse the matter with details, but after I reproduced the problem (obviously) apport could not reach launchpad because the wifi adapter was out of action. I connected an ethernet cable, but then apport failed on three different attempts."
1776443,2018-06-12 21:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776443,2018-06-12 09:13:19 UTC,I'm pretty sure the same hardware adapter and firmware is supporting bluetooth for my logitech mouse.
1776443,2018-06-12 09:07:23 UTC,"brian@bacchus:~$ uname -a
Linux bacchus 4.15.0-22-lowlatency #24-Ubuntu SMP PREEMPT Wed May 16 17:09:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
brian@bacchus:~$ lsb_release -a"
1776443,2018-06-23 09:18:39 UTC,"I installed the latest upstream kernel, headers and modules. As far as I can tell, it suffers exactly the same failure as the latest released bionic lowlatency kernel. The stack ttrace seems very similar and the timeout message looks to be the same. My guess is still the intel iwlwifi version 29 firmware (although all the older versions which will load onto my 3165 wifi adapter have failed in similar but not identical ways)."
1776447,2020-01-29 10:01:47 UTC,"I've built this locally and tested it. While it improves matters, it is still incomplete to get IGLX working fully - there is a new crash at the point you close the IGLX-using application instead of immediately upon starting it. This fix is still warranted, however, because it does improve things. I'm going to go back to bisecting Xorg upstream to see if I can identify the new crash."
1776447,2020-01-29 10:02:33 UTC,"There are, thankfully, seemingly no regressions in unrelated areas :-)"
1776447,2020-01-29 11:14:15 UTC,The new crash backtrace:
1776447,2020-01-29 22:13:09 UTC,This debdiff for Bionic fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start).
1776447,2020-01-29 22:13:39 UTC,This debdiff for Eoan fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start).
1776447,2020-01-29 22:14:24 UTC,This debdiff for Focal fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start).
1776447,2020-01-30 10:50:40 UTC,"The secondary crash doesn't occur without the first fix. You cannot reach it until the first fix is applied. However, I suppose it is in a different bit of code, but it is only reached when you use indirect GLX and prevents you using indirect GLX which is what this issue is attempting to fix."
1776447,2020-01-30 02:05:11 UTC,"I can't find any existing reports of that secondary crash, but ideally it would not usually be part of the fix here..."
1776447,2020-01-30 19:11:27 UTC,"both changes are now in upstream Xorg's repository, as PR388 was merged a few hours ago. So the changes in this debdiff are a backport of those to Bionic, Eoan and Focal (although if Focal were to sync with the upstream code then the delta won't be necessary going forward)."
1776447,2020-01-31 01:37:27 UTC,Great to hear.
1776447,2020-02-18 14:50:51 UTC,"Tagging rls-ff-notfxing, the bug is not important enough to be rls tracked. Still it's in the sponsoring queue and hopefully gets fixed before focal is out"
1776447,2020-01-28 20:27:05 UTC,"The attachment ""xorg-server-iglx.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1776447,2020-05-08 15:21:30 UTC,Fixed upstream in xorg-server 1.20.8
1776447,2020-01-29 22:18:35 UTC,The refreshed patches fix both crashes. The first change is upstream commit e1fa3be [1] and the second change is from upstream PR 388 [2].
1776447,2020-01-28 20:09:27 UTC,"That would be excellent - thanks! IGLX is one of those things probably not many people use, but those of us who do kind of really need it. It also seems to be a thing in HPC / research circles: https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX-Potential-Bye-Bye"
1776447,2018-06-14 06:24:29 UTC,"I've hit this on Ubuntu 18.04 (xorg 1.19.6), modesetting driver. I have opened a bug over there in case someone on that side has time to investigate (https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776447)"
1776447,2020-01-28 19:07:02 UTC,A fix has now landed upstream. I think this could be a candidate for an SRU cherry-pick for every supported release back to Xenial. The upstream commit is https://gitlab.freedesktop.org/xorg/xserver/commit/e1fa3beb2fe2519e69f859f0acdc68e5a770de27. It's a very simple one-line change and is merely a revert of a prior upstream commit.
1776447,2017-01-26 20:40:44 UTC,"LIBGL_ALWAYS_INDIRECT=1 glxgears
fails on latest git on r600 with:"
1776447,2017-01-27 08:23:43 UTC,This code in __glXForceCurrent:
1776447,2020-01-28 19:58:36 UTC,This is the upstream patch. It changes the return from __glXDRIcontextWait from hardcoded -1 to noClientException which will either be -1 or nothing. This is the pre-2016 behaviour that is being restored.
1776447,2017-01-29 23:42:57 UTC,Looking at the commits between 1.18.3 and 1.18.4 this commit seams pertain to the case: https://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.18-branch&id=54ba95861e5ae54051d3963e5e7ced7d69a6de7b
1776447,2017-01-30 01:04:20 UTC,"(In reply to diplosarus from comment #3)

> Looking at the commits between 1.18.3 and 1.18.4 this commit seams pertain
> to the case:
> https://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.18-
> branch&id=54ba95861e5ae54051d3963e5e7ced7d69a6de7b
"
1776447,2017-03-20 11:18:34 UTC,"(In reply to Michel Dänzer from comment #4)

> Does reverting that commit fix it?
"
1776447,2017-01-29 23:35:31 UTC,"Xorg 1.18.3 and below works fine, xorg 1.18.4 fails."
1776447,2018-02-09 13:31:48 UTC,I tested with xf86-video-ati-7.10.0-23-g733f606d. xorg-server-1.18.4 is good and xorg-server-1.19.0 is bad. Bisected and the result is:
1776447,2018-10-04 19:19:45 UTC,"Created attachment 141901
Xorg log from iglx crash"
1776447,2018-10-04 19:21:08 UTC,Somewhere between 1.19 and version 1.20.1 this has goten worse. The Xorg server now crashes after LIBGL_ALWAYS_INDIRECT=1 glxgears. Log attached.
1776447,2018-12-13 18:32:42 UTC,-- GitLab Migration Automatic Message --
1776447,2017-03-22 09:18:00 UTC,Can you bisect between 1.18.3 and 1.18.4?
1776448,2018-07-15 02:11:27 UTC,"Can you please provide a bit more information, Mark, to help replicate the issue?"
1776452,2019-04-15 14:40:33 UTC,"On Mon, Apr 15, 2019 at 9:21 AM Pengzhen(Peter) Cao <email address hidden>
wrote:"
1776452,2018-12-03 23:46:48 UTC,Can this be prioritized higher as this is a bad regression in >= bionic releases?
1776452,2019-04-15 14:13:26 UTC,"Hi Ryan,"
1776452,2019-04-05 00:02:52 UTC,"Ryan,"
1776452,2019-04-02 11:46:17 UTC,We have internal VMware PR2319097 to track the progress.
1776452,2019-04-02 11:07:18 UTC,"I will fix it in cloud-init. Once it is done, we should backport the fix to ubuntu 18.04.1/18.04.2 as their netplan package is being updated."
1776452,2019-03-05 20:23:05 UTC,"Netplan in disco has support for dhcp overrides[A], and this is available in Disco now.  Netplan 0.95 is being backported to bionic which will include this functionality."
1776452,2018-11-07 14:36:22 UTC,Also tried the following:
1776452,2019-04-05 14:07:34 UTC,"Hi,"
1776452,2018-09-01 03:33:06 UTC,"This is an important user scenario for VMware customer.
And the fix not only affects ubuntu18.04, but also all other linux distros that are using cloud-init."
1776452,2018-06-12 10:07:51 UTC,cloud-init logs
1776452,2018-06-12 10:08:12 UTC,50-cloud-init.yaml file
1776452,2018-06-18 05:57:07 UTC,"Hi,
it would be nice to see the full /var/run/vmware-imc/cust.cfg that you are using to configure it."
1776452,2018-11-07 14:23:41 UTC,Trying to upgrade from Xenial to Bionic we think we've hit this bug.
1776452,2018-06-19 09:09:51 UTC,"Attached the cust.cfg, Thanks Christian."
1776452,2018-08-23 22:21:32 UTC,We're looking to support this use-case in netplan in the near future.  I'll update this bug with some details on what changes we'll need to cloud-init to support this use-case.
1776452,2018-06-18 13:32:52 UTC,"There isn't yet a way to allow DNS overrides and DHCP on the same interface.  That is, the DHCP response from the server may include DNS entries so the custom nameserver values are not automatically appended to an existing DHCP configuration."
1776461,2018-06-12 16:30:35 UTC,"I have seen this on Kolla_ansible 6.0.0 deploying binary queens on Ubuntu, it hangs forever as in this bug: https://bugs.launchpad.net/kolla/+bug/1773911"
1776461,2018-06-15 10:32:12 UTC,"There are some mistake here.
A patch in kolla-ansible is merged ahead the kolla patch is merged."
1776461,2018-06-14 09:27:22 UTC,"I faced with same issue at 'Looking up disks for Swift' task.
In my case, Ubuntu 18.04's ansible was located at /usr/bin"
1776462,2018-06-12 11:12:58 UTC,"did some more digging, found a blacklist for nouveau on my system, which is necessary to load the switcharoo stuff. removed that, rebooted, now nouveau loads at boot and nvidia-prime claims it runs correctly, but it's still working incorrectly. I've narrowed it down though."
1776462,2020-05-04 21:29:30 UTC,The 'vgaswitcheroo' mechanism is no more used since https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011 fix (reworked there). Current package version 0.8.8.2 includes that fix.
1776462,2020-05-04 21:30:28 UTC,Should have been fixed with https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011
1776464,2018-09-04 14:03:38 UTC,@hplip-dev's ping?
1776464,2018-06-12 16:32:50 UTC,"avahi-browse finds the printer, even without firewall exceptions, so I do not understand why hp-setup simply fails to work?"
1776464,2018-06-12 16:48:40 UTC,@hplip devs: Setting up a printer should work without opening a port on the machine. avahi-browse provides enough information for generating the DeviceURI for cups.
1776464,2018-06-12 16:31:18 UTC,"""Do you think there could be a way to do the discovery without weakening the firewall?"""
1776464,2018-06-12 14:43:20 UTC,"@Jamie, thanks very much for having a look.
Do you think there could be a way to do the discovery without weakening the firewall?
What are the security implications of allowing ""from 10.0.0.0/24 port 5353 proto udp""?"
1776464,2018-06-12 13:12:31 UTC,"The way the traffic is coming into the system, ufw is doing the right thing. You should be able to make discovery work on your network with:"
1776464,2018-06-12 15:12:14 UTC,"@Jamie, I stumbled upon https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/764933 where an exception was added to ufw.
Could you explain what has changed in the meantime and why this is not possible anymore?"
1776466,2019-10-10 10:38:37 UTC,The docstring is wrong. Sorry. We'll fix it.
1776475,2019-01-03 18:50:32 UTC,"I have a question for people experiencing this bug (yes, you included :-)."
1776475,2018-08-23 12:05:29 UTC,"Using lightdm 1.26.0 in arch with xfce, and experiencing the same behaviour as described in comment #7, with no errors in the logs. In my case the delay between ""session is locked"" message and actual greeter appearance is around 10 seconds."
1776475,2018-07-26 13:46:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776475,2018-07-26 10:46:20 UTC,"So far, the logs basically show that lightdm does its job, and just does it again when bug happens."
1776475,2018-06-14 17:19:24 UTC,Bug still regularly observed.
1776475,2018-07-24 19:41:54 UTC,"Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated."
1776475,2018-07-24 18:11:11 UTC,"In order to investigate this bug, I started to write down each time I switch user and whether it works."
1776475,2018-06-12 12:35:42 UTC,"As seen in attached files, this is Xubuntu 18.04, where lightdm is default, no significant local customization."
1776475,2019-01-04 11:11:41 UTC,"Hey gouri, here is the info you requested:"
1776475,2018-07-25 13:38:57 UTC,"Sometimes a variant of the bug happens: after typing password, the expected session does not happen. Instead, a black screen with a white message on center, saying that session is locked and I have to wait for a moment. About 20 seconds later, a lightdm login greeter appears and only after typing the correct password *again*, I can access my session."
1776475,2019-06-02 03:43:40 UTC,"I had the exact same issue. In my case, I upgraded xubuntu 16.04 to 18.04 and this issue started showing up. Pulseaudio was also not working.
From further investigation, I noticed that chrome-remote-desktop was starting Xsession and this was causing issues. I removed that package and it fixed the issue."
1776475,2020-04-02 07:07:02 UTC,Thank You Jane @irihapeti for your message.
1776475,2020-04-01 22:35:04 UTC,This seems to have reappeared recently in Xubuntu 20.04
1776475,2020-04-01 23:01:42 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1776475,2019-06-02 21:48:10 UTC,## Thanks @vdrok
1776475,2020-04-20 23:43:54 UTC,"@Stéphane: Sorry, I didn't see this sooner. I must have forgotten to subscribe. (oops)"
1776475,2020-04-21 03:18:27 UTC,"A fresh install on an external USB3 drive is showing exactly the same behaviour. Not a VM problem, apparently."
1776475,2020-04-21 11:48:51 UTC,Hi Jane @irihapeti.
1776475,2020-04-21 12:49:55 UTC,The default value was 0 minutes. I set it to one minute and it made no difference.
1776475,2020-04-21 13:58:31 UTC,"Thank you for this extra information. This allowed to narrow down the bug you experienced to a simplified, shorter bug scenario."
1776475,2020-04-22 03:43:41 UTC,I've opened a new bug report: Bug #1874178
1776478,2018-07-25 17:27:55 UTC,"On 25 July 2018 at 18:11, guysoft <email address hidden> wrote:

> target: No such file or directory.
> /tmp/mount/remote: No such file or directory.
> (gdb) file DISTRHO-Ports/libs/lv2_ttl_generator
> Reading symbols from DISTRHO-Ports/libs/lv2_ttl_generator...(no debugging symbols found)...done.
> (gdb) file DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-Filter-2.so
> Reading symbols from DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-Filter-2.so...(no debugging symbols found)...done.
"
1776478,2018-07-25 17:11:17 UTC,"target: No such file or directory.
/tmp/mount/remote: No such file or directory.
(gdb) file DISTRHO-Ports/libs/lv2_ttl_generator
Reading symbols from DISTRHO-Ports/libs/lv2_ttl_generator...(no debugging symbols found)...done.
(gdb) file DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-Filter-2.so
Reading symbols from DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-Filter-2.so...(no debugging symbols found)...done.
(gdb) c
The program is not being run.
(gdb) set arch arm
The target architecture is assumed to be arm
(gdb) target remote :1234
Remote debugging using :1234
0xff7bd9e0 in ?? ()
(gdb) c
Continuing."
1776478,2018-07-25 16:51:18 UTC,"http://tinkering-is-fun.blogspot.com/2009/12/debugging-non-native-programs-with-qemu.html looks like a plausible tutorial for what you need to do with ""file"" (and has some other commands that might help for dynamically linked libraries). What you want to do when you get to the SIGABRT is tell gdb ""bt"" to get a backtrace, which if you have the symbol info will give a backtrace of where the guest was."
1776478,2018-07-25 16:45:33 UTC,"It wants debug symbols for the guest binary, not for QEMU. As it suggests, the ""file"" command pointed at the guest binary ought to help."
1776478,2018-07-25 16:28:47 UTC,"Hey,"
1776478,2018-07-03 12:56:41 UTC,"You want to attach with an Arm-aware gdb to the QEMU debug stub, not connect an x86 gdb to the x86 QEMU process. On Debian/Ubuntu the gdb in the 'gdb-multiarch' package will do."
1776478,2018-07-03 12:14:43 UTC,"Ok, got it to run with (had to septate arguments with --):"
1776478,2018-07-03 11:27:23 UTC,You want to execute a single program in the chroot (whatever the binary that is failing is):
1776478,2018-07-03 10:47:12 UTC,"Hey,
So how do I enable -g option?
The command that activates qemu is:"
1776478,2018-06-21 12:50:07 UTC,"Thanks for the repro case; it's on my list of things to look at, but the gating factor there is that my todo list is several miles long. If you want to look at it yourself, the first step is probably to run the program under qemu with qemu's -g option to enable the gdbstub, connect an arm-aware gdb to it and see if you can get a backtrace out of it."
1776478,2018-06-21 10:54:31 UTC,@pmaydell Is there anything I can do to help speed this up? I can run tests or make reproduction easier if that helps. But I need direction what actually helps you.
1776478,2018-06-12 21:30:53 UTC,"my bad, the line should be :
source ./common.sh"
1776478,2018-06-12 21:25:37 UTC,"Hey,
Not sure how to boil it down (yet). But this would reproduce it for you:"
1776478,2018-06-12 14:31:32 UTC,Could you provide repro instructions?
1776483,2016-01-08 16:28:19 UTC,"When opening a directory in a new tab, the history of the previous tab is copied into the new one, but the newly opened directory is not stored in the history."
1776483,2017-07-29 20:20:46 UTC,"Another problem, related to this is:"
1776486,2018-06-12 13:31:15 UTC,"We could also do a better job of identifying when different things (initrd, kernel, dtb) overlap in memory."
1776486,2019-09-23 14:25:31 UTC,"As of the 4.1 release we should now do a better job of identifying overlaps between initrd, kernel, end of ram, etc, for the built-in arm bootloader."
1776489,2019-10-02 14:24:41 UTC,"If you want to try (on your own risk) the Disco Dingo version on Bionic where libxmltooling8 is built against libcurl4, then you can do this:"
1776489,2019-06-05 08:57:05 UTC,"A workaround is documented here - by self compiling the package and adjust LD_PRELOAD for shibd to use the old libcurl shared objects:
https://depts.washington.edu/bitblog/2018/06/libcurl3-libcurl4-shibboleth-php-curl-ubuntu-18-04/"
1776489,2018-12-10 21:51:05 UTC,"Hi, just seeing if there is a timeline for resolution on this issue? Thanks!"
1776489,2018-07-31 13:51:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776489,2018-07-29 15:57:22 UTC,@adam-omega Shibboleth 3.0 isn't packaged by Ubuntu or Debian yet and will most certainly never land in 18.04.
1776489,2018-07-29 13:25:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776489,2018-07-29 14:13:07 UTC,We have tried to migrate everything to libcurl4 api/abi with openssl1.1 and managed to do that for everything but http://people.canonical.com/~ubuntu-archive/transitions/html/curl4.html xmltooling.... unfortunately we couldn't just kick out xmltooling as that is needed to build a few packages.
1776489,2018-07-29 13:27:15 UTC,This bug really messed up our webworker upgrades to 18.04. We are forced to do this rather messy workaround/hack for now: https://depts.washington.edu/bitblog/2018/06/libcurl3-libcurl4-shibboleth-php-curl-ubuntu-18-04/
1776489,2018-07-29 15:46:40 UTC,OpenSSL 1.1 support should have been in the 3.0 release earlier this month.
1776489,2018-06-12 23:09:16 UTC,Neil Hoggarth <email address hidden> writes:
1776489,2018-06-12 17:53:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776492,2018-06-13 20:06:40 UTC,"This is an interesting idea, however the kombu library (which oslo.messaging uses to interface with rabbitmq) does not currently support basic.return.  The 'immediate' and 'mandatory' flags are not implemented:"
1776492,2019-06-27 07:38:09 UTC,Kombu actually supports the mandatory flag.
1776492,2019-07-03 07:58:20 UTC,Please see also the blueprint: [1]
1776497,2018-06-17 11:20:06 UTC,Builds on LP by the way: https://launchpad.net/~djcj/+archive/ubuntu/tools/+packages?field.name_filter=aegisub&field.status_filter=published&field.series_filter=
1776497,2018-06-17 09:08:11 UTC,I can build the latest git snapshot from source on 18.04. You better use the bundled luajit if the system version is incompatible.
1776497,2018-06-17 07:39:48 UTC,Looks like it was removed  because the package failed to build. Please see https://launchpad.net/ubuntu/+source/aegisub/+publishinghistory or https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873327 for more details.
1776510,2018-06-12 16:14:56 UTC,Fix pushed:
1776510,2018-11-05 15:45:25 UTC,"Pushed to master, rel_3_0, and rel_2_5. Thanks, Bill!"
1776511,2020-08-30 12:12:50 UTC,probably duplicate of bug 1821483
1776512,2018-09-01 14:43:11 UTC,"Dear all, I would be happy about a little help here. Or at least a workaround. Can I help, to move this forward?
Regards,
Holger"
1776512,2018-09-06 21:23:24 UTC,I would check if this bug can be triggered with the live session also.
1776512,2018-09-06 22:09:35 UTC,will do
1776514,2018-08-08 21:06:55 UTC,The top of the stacktrace is similar to https://bugs.documentfoundation.org/show_bug.cgi?id=117483
1776518,2018-10-29 18:05:39 UTC,This is rather complicated as there currently is not a table which tracks architectures for buckets i.e. something similar to BucketVersionsCount e.g.
1776528,2018-06-12 20:25:49 UTC,thx!
1776532,2018-08-02 21:51:53 UTC,"Since this is an RFE, I think it's safe to pursue this in Stein if we don't get a patch up in the next week for Rocky RC1."
1776534,2018-09-27 12:21:55 UTC,"In addition to the above symptoms, I had ""black screen"" after switching user but keyboard non-responsive."
1776534,2018-10-01 06:11:21 UTC,"Michal, please open a separate bug of your own."
1776534,2018-08-17 04:32:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776534,2018-06-14 16:26:50 UTC,"My /var/crash has 3 crashes currently, none of them at the time of the problem:"
1776534,2019-10-23 02:52:04 UTC,"For it works when I log out, but if I close the lid and open it up again, then I am unable to use the keyboard."
1776534,2018-06-13 15:50:35 UTC,Problem persists even after updating gdm3 to 3.28.2-0ubuntu1.2 and restarting.
1776534,2018-06-13 06:34:09 UTC,The problem you describe sounds like the secondary issue in bug 1766137 that was fixed only a few hours ago.
1776534,2018-06-14 02:28:05 UTC,Do you find any crash files in /var/crash/ ?
1776537,2018-06-12 18:25:48 UTC,It appears this may be related to this bug:
1776537,2018-06-12 18:34:08 UTC,"Based on the other bug posted above, I edited this file:"
1776538,2018-07-10 03:53:04 UTC,"We don't currently record a timestamp when the model is created. This would need to be added, then threaded through the layers."
1776541,2018-09-19 19:36:31 UTC,"John, can we propose the original document you wrote for review [0]?"
1776541,2018-08-02 21:52:36 UTC,"This would be nice to have in Rocky, but since PCI-DSS support was implemented prior to Rocky this isn't an RC1 blocker."
1776546,2018-06-12 18:28:10 UTC,The other missing package.
1776548,2018-06-15 12:06:54 UTC,"Thank you, I've installed launchpad and reset my PC. Nothing seems to happen. The scanner is still not working and the connection not accepted. What do I do now?"
1776548,2018-06-19 19:39:37 UTC,2018-06-16 22:21 GMT+02:00 Paul White <email address hidden>:
1776548,2018-06-19 19:41:04 UTC,Soved All the information provided. Follow this link step by step
1776548,2018-06-29 14:38:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1776548,2018-07-02 20:12:31 UTC,Have you tried this workaround described in bug https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1741977 message #4? Are you using USB3 socket? Does it work on USB2?
1776548,2018-09-12 15:06:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776548,2019-07-04 16:03:29 UTC,Issue about to be fixed in 18.04.
1776549,2020-09-04 12:58:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776550,2018-06-13 15:23:36 UTC,So I have this once so far (in a dozen of runs). I wonder if indeed this is a case that during the controller scaleup testing I am overloading the undercloud a bit and it has a hard time coping with it. Maybe an extension of the timeouts is all that is needed here.
1776550,2018-12-29 13:44:42 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/575009
Reason: This patch has no activity for a while, per policy, we abandon it. Feel free to re-open if you think you're working on it."
1776550,2018-06-13 10:49:28 UTC,"Jun 12 18:18:17 undercloud proxy-server: 192.168.24.15 192.168.24.15 12/Jun/2018/18/18/17 GET /v1/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz%3Ftemp_url_ex
pires%3D1528912449%26temp_url_sig%3De235dfb34dd32381a298a85b32e9e8268914dc04 HTTP/1.0 200 - curl/7.29.0 - - 2031 - tx56925513a1a141f2a2bd8-005b200e4a - 30.5842 - - 1528827466.837025881 15288
27497.421236038 0"
1776550,2021-02-17 17:08:15 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1776550,2018-06-12 20:05:34 UTC," [root@undercloud ~]# grep 'e235dfb34dd32381a298a85b32e9e8268914dc04' /var/log/swift/swift.log
Jun 12 18:16:04 undercloud object-server: 192.168.24.1 - - [12/Jun/2018:18:16:04 +0000] ""GET /1/927/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz"" 200 2031 ""GET http://192.168.24.1:8080/v1/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz?temp_url_expires=1528912449&temp_url_sig=e235dfb34dd32381a298a85b32e9e8268914dc04"" ""tx945652e201fe42e294a6d-005b200de4"" ""proxy-server 16602"" 0.0007 ""-"" 18584 0
Jun 12 18:16:06 undercloud proxy-server: 192.168.24.9 192.168.24.9 12/Jun/2018/18/16/06 GET /v1/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz%3Ftemp_url_expires%3D1528912449%26temp_url_sig%3De235dfb34dd32381a298a85b32e9e8268914dc04 HTTP/1.0 200 - curl/7.29.0 - - 2031 - tx945652e201fe42e294a6d-005b200de4 - 1.9609 - - 1528827364.921262026 1528827366.882137060 0
Jun 12 18:18:16 undercloud object-server: 192.168.24.1 - - [12/Jun/2018:18:18:16 +0000] ""GET /1/927/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz"" 200 2031 ""GET http://192.168.24.1:8080/v1/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz?temp_url_expires=1528912449&temp_url_sig=e235dfb34dd32381a298a85b32e9e8268914dc04"" ""tx56925513a1a141f2a2bd8-005b200e4a"" ""proxy-server 16603"" 0.0010 ""-"" 18585 0
Jun 12 18:18:17 undercloud proxy-server: 192.168.24.15 192.168.24.15 12/Jun/2018/18/18/17 GET /v1/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz%3Ftemp_url_expires%3D1528912449%26temp_url_sig%3De235dfb34dd32381a298a85b32e9e8268914dc04 HTTP/1.0 200 - curl/7.29.0 - - 2031 - tx56925513a1a141f2a2bd8-005b200e4a - 30.5842 - - 1528827466.837025881 1528827497.421236038 0
Jun 12 18:18:27 undercloud object-server: 192.168.24.1 - - [12/Jun/2018:18:18:27 +0000] ""GET /1/927/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz"" 200 2031 ""GET http://192.168.24.1:8080/v1/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz?temp_url_expires=1528912449&temp_url_sig=e235dfb34dd32381a298a85b32e9e8268914dc04"" ""tx86d9d7a96f514343b2bd7-005b200e73"" ""proxy-server 16605"" 0.0007 ""-"" 18586 0
Jun 12 18:18:27 undercloud proxy-server: 192.168.24.7 192.168.24.7 12/Jun/2018/18/18/27 GET /v1/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz%3Ftemp_url_expires%3D1528912449%26temp_url_sig%3De235dfb34dd32381a298a85b32e9e8268914dc04 HTTP/1.0 200 - curl/7.29.0 - - 2031 - tx86d9d7a96f514343b2bd7-005b200e73 - 0.0057 - - 1528827507.837201118 1528827507.842941999 0
Jun 12 18:37:46 undercloud object-server: 192.168.24.1 - - [12/Jun/2018:18:37:46 +0000] ""GET /1/927/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz"" 200 2031 ""GET http://192.168.24.1:8080/v1/AUTH_4eb73f99e4ac4e9a9b904687023d2b3c/overcloud-swift-rings/swift-rings.tar.gz?temp_url_expires=1528912449&temp_url_sig=e235dfb34dd32381a298a85b32e9e8268914dc04"" ""tx8dbc397af4fc4e8494315-005b2012fa"" ""proxy-server 16605"" 0.0006 ""-"" 18584 0
Jun 12 18:37:46 undercloud proxy-server: 192.168.24.15 192.168.24.15 12/J..."
1776550,2018-06-12 19:54:06 UTC,sosreports for the undercloud and controller-0 are here: http://acksyn.org/files/tripleo/sosreports-ctrl-scaleup-swiftringbuild-fail/
1776550,2018-06-13 07:10:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/575009"
1776555,2018-08-02 20:44:57 UTC,so it was the Library Preview button..
1776555,2018-07-10 19:34:44 UTC,"fine, if it's fixed.
I compiled 2.1 with qt5.2 and removed the spinny templates.
It crashed when I opened the Skin Settings.
Removed the library (main table, tree is there) as well, and it didn't crash.
Deere also crashed on various occasions until I removed the lib table."
1776555,2018-07-10 16:19:01 UTC,"If I remove the library, no crash.
If I remove the spinnies, no ctash.
If I parent the render button to a the menu bar, no crash.
Since the button dies not inherit style from a parent, no parent is the cleanest solution."
1776555,2018-07-09 22:36:19 UTC,https://bugs.launchpad.net/mixxx/+bug/1776555
1776555,2018-07-10 13:41:19 UTC,"> It crashes when the library is sibling with spinnies
"
1776555,2018-06-15 09:20:37 UTC,"I'm on Trusty as well, and I compiled master & lib-redesign with qt5.2.
There are various crashers appearantly related to waveforms and other paint events."
1776555,2018-06-12 20:34:43 UTC,I have been using Tango fine with Qt 5.10. I am guessing this is related to the old version of Qt.
1776555,2018-07-09 22:22:35 UTC,"It crashes when the library is sibling with spinnies. This leads to a size change during painting which invalidated the QPaintDevice and leads to the crash:
QPaintDevice: Cannot destroy paint device that is being painted"""
1776563,2019-11-29 11:03:22 UTC,"Very informative article thanks for sharing please keep it up because there is no limit of information so I'm waiting for an awesome article just like that.
You can get more information about this mouse clicker but at http://www.cross.tv/blog/186495"
1776563,2020-04-29 09:17:01 UTC,"Btw, the new bios 1.17 is out guys"
1776563,2020-02-06 14:38:15 UTC,"I have a Acer Aspire A315, and I was glad that the BIOS 1.15 fixed the problems with the boot, and the WA kernel parameters were not needed anymore. But now I have I have the next problem:"
1776563,2020-04-29 09:17:29 UTC,Is someone up to test it?
1776563,2019-12-23 14:45:28 UTC,"Where did you find information about the positive site, this post? I just read some articles on your website, and I really like your style. Thank you for the millions and keep working effectively.and also found some interesting topi roblox asset downloader here https://www.giantbomb.com/profile/emmaro/blog/roblox-free-robux-generator-2020/142230/"
1776563,2019-12-05 07:41:44 UTC,I found your post interesting to read and i want to say that this is a best post i have ever seen until now. Take a look at http://www.cross.tv/blog/189000 this link for How to Read a Check
1776563,2019-11-26 11:26:53 UTC,"I use manjaro + wayland/sway, the only custom things i did are:"
1776563,2019-09-06 13:08:25 UTC,This seems to be finally fixed by 1.15 firmware on Acer A315 41G.
1776563,2019-11-07 11:37:41 UTC,"Any experiences with other distributions in the last months? Especially regarding stability? WLAN and Bluetooth work all the time? USB devices always show up when you connect them? I could really use some feedback about your choosen / favorite distribution on this notebook after patch 1.15.
Warm regards
Ulf"
1776563,2019-11-02 07:32:57 UTC,Nice post. I learn something totally new and challenging on blogs I stumbleupon on a daily basis.https://techbaby.pro/err_cache_miss/ It's always exciting to read articles from other writers and use something from their sites.
1776563,2019-09-22 20:11:22 UTC,"So far it has been quite good. Some report a ""slow grub"". Sometimes I have to reboot because no wifi card detected."
1776563,2019-09-19 13:39:59 UTC,"So, how is it, guys? Have you noticed any downsides with 1.15 BIOS in linux? Do you still use ivrs and aspm stuff?"
1776563,2019-09-17 12:34:35 UTC,"Touchpad again stopped working, ""disappeared"" from the xinput list on kernel upgrade to 5.0.0-27. Works again when reverted to 5.0.0-25."
1776563,2020-04-30 03:43:47 UTC,"I did test it, works fine, only issue is that the boot loader and bios menu still being laggy since 1.15v bios, its like there is no graphical acceleration, but after boot evgerything works flawless on any linux."
1776563,2019-09-09 20:43:59 UTC,"Confirm that the update to 1.15 has fixed it all, touchpad included. GRUB is indeed slow but no big deal."
1776563,2019-11-26 11:09:35 UTC,"I found that suspend/hibernate are trouble. But specially KDE/Plasma is problematic. While Manjaro Plasma refuses to work, Manjaro i3 gives Suspend (to Disk, assume) out of the box. Everything else so far is working very good."
1776563,2020-04-30 06:55:16 UTC,"Quite sad, so are there any changes at all?"
1776563,2020-08-04 12:45:34 UTC,"lol, somehow i can see recent messages in launchpad, but not there..."
1776563,2020-05-01 08:22:57 UTC,"There is a chance that this also helps with the resume/suspend bug with kde/plasma. If anyone can test, that would be awesome. I will try myself as soon as possible."
1776563,2020-08-13 19:31:16 UTC,Add: acpi_osi='Windows 2018' acpi_backlight=vendor
1776563,2019-09-05 13:46:00 UTC,"I was able to run the command by making the bios and on default settings and booting again, but when reboot again it shows the error."
1776563,2020-08-13 17:27:15 UTC,"haha, it seems it blinks even not on max brightness while charging (didn't use your workaround)."
1776563,2020-08-02 13:08:10 UTC,For crashes after suspend add: rcu_nocbs=0-N(number of cores -1) and idle=nowait as grub parameters update-grub and reboot you also need kernel 5.4 or higher with latest stable firmware.
1776563,2020-08-02 10:37:51 UTC,For crashes after suspend add: rcu_nocbs=0-N(number of cores -1) and idle=nowait as grub parameters update-grub and reboot you also need 5.4 or higher.
1776563,2020-08-02 10:02:57 UTC,"I still get freezes when resuming from suspend when using kde and opengl as a compositor, but this is not related to this issure, or is it?"
1776563,2020-07-23 10:38:52 UTC,"btw, do you also have lowres screen while updating bios? it used 1920*1080 before, but now it's like 800*600"
1776563,2020-04-30 06:59:40 UTC,"I noticed faster wake from suspend, but nothing game-changing."
1776563,2020-07-13 18:35:51 UTC,How is it?
1776563,2021-01-05 12:08:19 UTC,Just an update:
1776563,2020-06-15 06:11:49 UTC,"Hello if you have problems with screen flickering at 100% backlight brightness
Add: acpi_osi='Windows 2018' acpi_backlight=vendor
in grub boot parameters&update-grub&restart
it totally fixes the issue"
1776563,2020-06-14 16:08:00 UTC,"Ignore my previous comment, the previous parameter fixes the issue but disables manual back-light control, instead use these in grub cmd: ""acpi_osi='Windows 2018' acpi_backlight=vendor""
and sudo update-grub."
1776563,2020-06-14 11:52:53 UTC,"If you get screen flickering at 100% backlight add ""acpi_backlight=video""
and update-grub it seems to resolve the problem."
1776563,2020-05-01 08:54:08 UTC,i also used woesb to burn the win10 iso mentioned above in a flash drive
1776563,2020-05-01 08:53:10 UTC,I booted this https://toolslib.net/downloads/viewdownload/255-winpese-x64/ from a usb drive and loaded the bios from another usb storage to update.
1776563,2020-05-01 08:45:12 UTC,"Guys, can you tell please how do you update bios? Maybe the sluggishness of bios/grub is caused by one of methods? Cuz some people aren't experiencing it"
1776563,2020-07-07 21:49:46 UTC,There's a new bios (1.18) out
1776563,2018-07-15 18:36:07 UTC,"Hi all,"
1776563,2018-06-15 13:27:14 UTC,"""The fact that ACPI was designed by a group of monkeys high on LSD, and is some of the worst designs in the industry obviously makes running it at any point pretty damn ugly.""
Torvalds, Linus (2005-07-31). Message. linux-kernel mailing list. IU. Retrieved on 2006-08-28."
1776563,2018-07-15 00:19:26 UTC,HOT NEWS!!
1776563,2018-06-16 04:54:10 UTC,"Created attachment 276587
Soft lockup failure without noacpi"
1776563,2018-06-16 04:53:11 UTC,"Created attachment 276585
attachment-31427-0.html"
1776563,2018-06-16 04:51:39 UTC,"CPU: AMD Ryzen 5 2500U
GPU1: AMD Radeon Vega 8
GPU2: AMD Radeon 535"
1776563,2018-06-16 04:43:34 UTC,"Created attachment 276583
dmesg after starting kernel with pci=noacpi"
1776563,2018-06-15 17:06:02 UTC,Power management doesn't work well this way. It was hot a little. I've changed back to win10. This should be fixed by kernel developers or with a downstream patch.
1776563,2018-06-15 11:53:38 UTC,*Sorry correction: Who would like to do it? :D
1776563,2018-06-15 11:51:41 UTC,"I installed the new amdgpu pro driver and everything is very fast now. This bug should be reported to freedesktop, would you like somebody to do it? :D"
1776563,2018-06-16 05:07:17 UTC,Nothing changes with disabled iommu.
1776563,2018-06-15 11:02:49 UTC,It works but very slow. This could be an ACPI problem.
1776563,2018-06-15 08:09:13 UTC,"Had this on my A315 too, but I returned it to the vendor. Seems to be an UEFI-Bug, because it doesn't happened with my Ryzen 2500U from HP. Could also be related to that Ryzen/Radeon 535 combination (Vega/CGN 3)."
1776563,2018-06-15 08:08:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776563,2018-06-14 10:32:22 UTC,apport-collect 1776563 can't be entered because the kernel can not load.
1776563,2018-06-14 03:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776563,2019-10-18 08:37:44 UTC,"(In reply to jacky from comment #229)

> I was trying another kernel parameters and noapic seems to work. It is not
> needed to disable the whole ACPI ""service""
> , however I don't know how important apic is. On kernel 4.18 even
> temperature sensors appear.


You should update your bios to v1.15 after that you don't need any overrides.
After that you can remove the noapic since it isn't needed.
Please don't post spam links."
1776563,2019-10-19 15:09:40 UTC,"I tested MX Linux for the past weeks and it was stable as a whole, but WLAN, bluetooth and USB often dissapeared for no reason and forced me to reboot."
1776563,2018-07-15 00:34:50 UTC,This could be the better solution because of the notebook's lowest heating but I'm not sure.
1776563,2018-06-15 08:25:28 UTC,"Thanks Freihut, I will try this."
1776563,2018-06-16 05:29:45 UTC,"Reported upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=200087"
1776563,2019-10-08 12:18:57 UTC,"I was trying another kernel parameters and noapic seems to work. It is not needed to disable the whole ACPI ""service"" https://www.icrwatch.com/
, however I don't know how important apic is. On kernel 4.18 even temperature sensors appear."
1776563,2018-06-16 07:34:30 UTC,"Created attachment 276591
Error message before freezing (without quite splash)"
1776563,2018-07-14 14:14:22 UTC,Kernel can be started even with noapic but two sensors will be missing and the advanced touchpad functions will not work.
1776563,2018-07-14 14:01:09 UTC,"Hi AaronMa,"
1776563,2018-07-14 07:01:07 UTC,Hi Richard:
1776563,2018-07-14 03:47:47 UTC,"Dear Ubuntu maintainers,"
1776563,2018-07-14 03:36:19 UTC,The solution for Acer A315-41G-* notebooks: (USE AT YOUR OWN RISK - PLS be very careful)
1776563,2018-07-14 02:43:24 UTC,"gg71, it works almost perfectly, thanks again. I have been working on this for ca one month. Please write a mail to me if you have any new info."
1776563,2018-07-13 22:05:44 UTC,"gg71, where have you been till now? :D
Thanks, I will try it."
1776563,2018-07-13 21:33:30 UTC,"Hi,
amdgpu doesn't crash on my a315-41g-r40x (BIOS V1.08) with
  linux-next-next-20180713 compiled with VGA_SWITCHEROO=N
and with
  kernel parameters: ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2"
1776563,2018-07-13 18:58:45 UTC,"Hi, I was trying another kernel parameters and noapic seems to work. It is not needed to disable the whole ACPI ""service"", however I don't know how important apic is. On kernel 4.18 even temperature sensors appear.
Power management is almost perfect if cpu governor is set to powersave."
1776563,2018-07-09 17:49:45 UTC,"Erik, I think this is in connection with clocksource calibration but I'm not an expert."
1776563,2018-06-30 03:26:06 UTC,*there are no values
1776563,2018-06-30 03:21:12 UTC,"Created attachment 277069
Fedora loads without noacpi"
1776563,2018-06-30 03:20:02 UTC,Fedora loads without any additional parameters(mysterious).
1776563,2018-06-30 02:22:38 UTC,"Hi Erik,"
1776563,2018-06-29 23:43:58 UTC,"Please try booting with linux 4.18-rc1 or later. Also, please try 4.18-rc1+ with/without ACPI"
1776563,2018-07-14 16:22:03 UTC,"AaronMa,"
1776563,2018-06-16 05:49:32 UTC,"Created attachment 276589
dmesg after amd_iommu_dump=1"
1776565,2018-06-13 15:03:57 UTC,"It appears that this is not a charm bug, but needs to be run upstream to heat.  The stack was created and attempted to be deleted under 48 hours later, and there were no changes to heat configs within that timeframe that would have changed the encryption key, hence, I believe this is bad exception handling within swift.heat.engine.stack._try_get_user_creds() function that should trap also InvalidToken and InvalidEncryptionKey exceptions as well as exception.Error to allow for deletion of the stack."
1776565,2019-11-26 11:30:09 UTC,Is this upstream bug in heat relevant: https://storyboard.openstack.org/#!/story/1711047
1776565,2019-05-13 22:00:01 UTC,"Agree that this is a bug against upstream, rather than the charm."
1776571,2019-05-27 13:38:07 UTC,It seems to be a race condition between nova and cinder.
1776571,2018-06-13 00:55:26 UTC,"Find  inconsistent data in db:
In table volume_attachment
mysql> select * from volume_attachment where volume_id = 'e330054a-66fe-44f8-9e32-affcfef5e935';
+---------------------+------------+---------------------+---------+--------------------------------------+--------------------------------------+---------------+--------------------------------------+------------+---------------------+---------------------+-------------+---------------+

| created_at          | updated_at | deleted_at          | deleted | id                                   | volume_id                            | attached_host | instance_uuid                        | mountpoint | attach_time         | detach_time         | attach_mode | attach_status |


+---------------------+------------+---------------------+---------+--------------------------------------+--------------------------------------+---------------+--------------------------------------+------------+---------------------+---------------------+-------------+---------------+

| 2018-06-13 00:22:19 | NULL       | 2018-06-13 00:38:19 |       1 | a9a50cc6-5a89-4acb-bea2-01b81a5673d9 | e330054a-66fe-44f8-9e32-affcfef5e935 | NULL          | 7ad9dce7-4bce-446b-bcbc-6bd812150fb2 | /dev/vdc   | 2018-06-13 00:22:22 | 2018-06-13 00:38:19 | rw          | detached      |


+---------------------+------------+---------------------+---------+--------------------------------------+--------------------------------------+---------------+--------------------------------------+------------+---------------------+---------------------+-------------+---------------+
1 row in set (0.00 sec)"
1776571,2019-03-28 07:32:34 UTC,"@TommyLike, yes."
1776571,2018-06-13 01:31:12 UTC,Where is the inconsistent data?
1776571,2019-05-27 12:18:25 UTC,"On my infras, I have some similar inconsistency:
$ cinder list"
1776575,2018-06-16 14:46:56 UTC,FWIW: here's the info for the GUEST amd64 VM that has been panicking...
1776575,2018-06-16 14:38:01 UTC,@tyhicks: i totally forgot you asked me to try testing with the HOST running an older kernel... my amd64 GUEST VMs are NOT kernel panicking :shock: :shock: :shock:
1776575,2018-06-14 12:17:43 UTC,"On 06/13/2018 04:55 PM, Tyler Hicks wrote:

> @wkitty42, could you please try booting your host into an older kernel,
> such as 3.13.0-149.199, and using qemu 2.0.0+dfsg-2ubuntu1.43 to see if
> the guests still panic?
"
1776575,2018-06-15 18:21:36 UTC,and the last...
1776575,2018-06-15 18:21:06 UTC,good grief... and the rest... WTH?
1776575,2018-06-15 18:17:32 UTC,"looks like my big report got cut off... sorry... here's the rest of what i had
posted... starting with the libvirt guest log just before the cut off..."
1776575,2018-06-15 16:42:24 UTC,"On 06/14/2018 06:47 PM, Tyler Hicks wrote:

> I really do appreciate your testing. I'm relying on you here because while I
> did test this particular combination on a family 17h AMD processor and didn't
> see such a guest panic, I don't have a family 15h AMD processor to test on.
"
1776575,2018-06-15 16:16:44 UTC,"On 06/15/2018 11:26 AM, wkitty42 wrote:

> 20180615 GUEST kernel panic screen shot
"
1776575,2018-06-15 15:26:40 UTC,"On 06/13/2018 02:48 AM,  Christian Ehrhardt  wrote:

> Also in addition to the Kernel Panic getting the guest log could be
> useful in case qemu has thrown warnigns or errors.
"
1776575,2018-06-14 22:47:42 UTC,"I really do appreciate your testing. I'm relying on you here because while I did test this particular combination on a family 17h AMD processor and didn't see such a guest panic, I don't have a family 15h AMD processor to test on."
1776575,2018-06-15 18:23:12 UTC,done... what is missing?
1776575,2018-06-13 20:55:01 UTC,"@wkitty42, could you please try booting your host into an older kernel, such as 3.13.0-149.199, and using qemu 2.0.0+dfsg-2ubuntu1.43 to see if the guests still panic?"
1776575,2018-06-13 20:35:52 UTC,"On 06/13/2018 01:03 PM, Tyler Hicks wrote:

> I want to point out that the two kernel panics that were posted are from
> two different guest kernel versions:
>
>    3.32.0-151-generic
>    3.32.0-32-generic
>
> That may indicate that the offending bug is in the host kernel and/or
> QEMU.
"
1776575,2018-06-13 17:05:39 UTC,I made a typo in the kernel versions above. They should be:
1776575,2018-06-13 17:03:58 UTC,I want to point out that the two kernel panics that were posted are from two different guest kernel versions:
1776575,2018-06-13 15:55:41 UTC,sorry for the delay... was sleep time :)
1776575,2018-06-13 06:52:38 UTC,Subscribing Marc who was driving the update so he is aware
1776575,2018-06-13 06:48:06 UTC,@wkitty42: Since the security update was for AMD processors - are you running on Intel or AMD?
1776575,2018-06-13 03:55:39 UTC,"Finally, please also attach the contents of /proc/cpuinfo in the host."
1776575,2018-06-13 03:54:51 UTC,Hello and thanks for the report!
1776575,2018-06-13 03:06:05 UTC,"Wow, that's impressive."
1776575,2018-06-13 01:40:56 UTC,"Hello wkitty42, could you please run:"
1776575,2018-06-13 01:24:54 UTC,CHANGELOG: https://launchpad.net/ubuntu/+source/qemu/+changelog
1776575,2018-06-14 12:15:31 UTC,"On 06/13/2018 01:05 PM, Tyler Hicks wrote:

> I made a typo in the kernel versions above. They should be:
>
>    3.13.0-151-generic
>    3.13.0-32-generic
"
1776575,2018-06-13 02:41:56 UTC,i tried and had to install some python apport thing... it is erroring out after complaining about a bunch of things being owned by my user 1000 instead of user 0... i ran that command with sudo... so i had to clear out the apport cache credentials and rerun it without sudo... i got this (oauth token obfuscated)...
1776577,2018-06-13 03:03:55 UTC,code submitted:https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/414912
1776580,2018-06-14 01:27:24 UTC,Looks like the problem is solved. I tested the problematic Inkscape archive and it is working perfectly.
1776585,2018-07-18 02:40:59 UTC,code merged: https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/416906
1776587,2018-06-18 19:41:55 UTC,"A Brian said, it's already fixed in master branch"
1776587,2018-06-13 15:35:39 UTC,This has already been fixed.
1776587,2018-06-13 20:48:19 UTC,"hi @brian-haley,"
1776587,2018-06-13 21:01:57 UTC,"port 35357 seems to be used in many other installation guides like heat, etc..."
1776587,2018-06-14 14:23:21 UTC,It was fixed in the master branch
1776604,2018-10-02 08:47:29 UTC,Looks like this has been released to 2.3 (i see the patch in 2.3.5-6511-gf466fdb-0ubuntu1)
1776604,2018-08-01 00:03:23 UTC,Awesome! Thank you for all the testing Hua!
1776604,2018-07-31 23:51:03 UTC,"Test the fix patch, it works well - https://imgur.com/a/gRumssB"
1776604,2018-07-31 11:33:04 UTC,"I have successfully reproduced the problem after restarting maas server, the DNS IP changed from 192.168.100.205 to 10.12.2.3"
1776604,2018-07-25 04:57:13 UTC,"@Trent,"
1776604,2018-07-25 03:46:04 UTC,"Joshua: did you look up the DNS name? I don't see the results of that in your screenshot.
The problem is purely the DNS name, e.g. run ""ping compute.maas"""
1776604,2018-06-15 22:29:40 UTC,"Trent,"
1776604,2018-07-11 23:28:57 UTC,"@lathiat, are you able to test the patch in this merge proposal to see if it fixes the issue for you?"
1776604,2018-06-15 23:05:58 UTC,"FWIW, a couple things worth noting:"
1776604,2018-06-16 02:40:39 UTC,One thing you didn't try that I did try (as this was the actual customer scenario) was a bridge of a bond.  Maybe that changes the behavior?
1776604,2018-06-19 03:26:03 UTC,"I did a quick test, and this does seem that this changes it. It seems when the bridge on a bond is created MAAS picks another interface for the default DNS domain, even tough the underlying physical interface for the bond/bridge is indeed the PXE one...."
1776604,2018-07-25 02:36:22 UTC,"@Trent, @Andres,"
1776604,2018-07-11 15:22:25 UTC,"Hi Trent,"
1776604,2018-07-11 19:53:31 UTC,I think the difference in behavior between a bonded interface and a bridged bond can be explained by the following section of SQL:
1776604,2018-07-10 03:59:17 UTC,"I have a customer using 2.3 who needs to update the DNS record for their machine to be the correct (primary) interface in this scenario. Unfortunately in 2.3 it seems you cannot update the existing DNS record like you can in 2.4 (maas dnsresources read does not return any of the machine hostname records, thus you can't update them - and if you create a record alongside it - DNS returns both IPs instead of replacing the auto generated record)"
1776612,2018-12-16 17:01:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776615,2018-06-14 04:12:47 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1776615,2018-06-14 07:47:02 UTC,"I'm not opposed to this; The server has its own settings to limit memory and file count, so it shouldn't suddenly go wild if we remove the systemd limit."
1776616,2019-01-04 07:19:27 UTC,Have you tested 4.5.7 and 4.6 to see if this was the transition where the bug started?
1776616,2018-11-20 15:54:02 UTC,Hi.
1776616,2018-11-21 04:52:04 UTC,"Stable releases are not linearly dependent on previous releases, so we need to use mainline (Linus' tree) to find a meaningful bisect point. In this case, it should be v4.5 and v4.6."
1776616,2018-11-29 11:06:38 UTC,"Ok, I started with v4.5 and v4.6.  I successfully did a couple iterations, after adding the follownig CFLAGS to Makefile to get past compiler errors:"
1776616,2018-12-01 01:13:50 UTC,"I couldn't resist a challenge :), so I installed GCC version 5.  In the process of trying to compile a bisected kernel, my file system somehow got corrupted.  I have no idea who the culprit is, as this laptop is very old.  So, it could be a hardware issue, who knows."
1776616,2018-12-07 02:39:50 UTC,Thank you for trying to solve this issue.
1776616,2018-12-30 00:35:59 UTC,"Hi, I updated my Maxdata Belinea o.book 2.1 with AMD Processor (AMD Turion(tm) 64 X2 Mobile Technology TL-60) from Kubuntu 14.04 to Mint Xfce 19 (reinstall). Same issue here. Then I tried Mint 18.3 which is built upon Ubuntu 16.04, again the same issue. I installed upstream kernel 4.20.0-042000-generic - problem persists.
When I read the previous comments, it's always an aging AMD processor involved..."
1776616,2019-01-04 04:48:50 UTC,"Yeah, they all seem to be similar CPU."
1776616,2019-01-04 08:26:17 UTC,"No, I do not have the possibility to test this as the server is in production now."
1776616,2019-07-30 23:54:39 UTC,I encountered this issue installing xubuntu™ 18.04-LTS on an emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon® LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a Shuttle® PSU upgrade (PC6300001 in for stock 220W LITEON®) and the planar C77 geForce® 64-bit GPU by-passed for the nVIDIA® GF-109 on an msi® N610GT-MD1GD3/LP half-height video display adapter. I normally use:
1776616,2019-01-27 08:05:04 UTC,Thanks expos.
1776616,2019-02-24 22:26:10 UTC,Hi.
1776616,2019-03-07 06:35:51 UTC,"If it's the same one as LP: #1771467, then it's fixed."
1776616,2019-07-14 02:29:00 UTC,This is also happening on Fedora 30
1776616,2019-07-31 00:16:43 UTC,"Update:  nVIDIA® geForce® driver 340.107 for the C77 GPU (package: nvidia-340) got to a successful power-down.  Be advised that Packages nvidia-n are to be reserved for nVIDIA® nFORCE® MCP chipsets such as the MCP78 northbridge my EL1210-09; intel®, AMD®, and VIA® chipsets require different solutions."
1776616,2019-12-03 09:53:37 UTC,Kernel 4.15 4.15.0-72 seems to have fixed this issue.
1776616,2019-12-10 08:19:56 UTC,"Re #41, ""Can anyone else confirm?"""
1776616,2019-12-10 08:52:44 UTC,"Re #42; pardon; machine-confusion. The problem with 4.15.0-72 indeed but on a Xeon E5606, AMD HD 5770 graphics"
1776616,2020-06-18 17:07:13 UTC,"hi,"
1776616,2019-01-05 23:46:50 UTC,"I installed many upstream kernels via UKUU. I did several verifications with shutdown and reboot, last version where both works is 4.6.2, first version where neither shutdown nor reboot works is 4.6.3 . Both kernels 4.5.7 and 4.6 work fine for me."
1776616,2018-11-20 02:47:24 UTC,"Ugh, tab key did a submit!  Launchpad needs some work."
1776616,2019-01-04 05:46:47 UTC,I have this problem with Intel Xeon CPU E5-2620 v4. I do not think it is CPU related.
1776616,2018-11-20 01:46:14 UTC,"Hey! I'm typing this from the laptop over WiFi.  I powered on the laptop with the WiFi off, but then turned it on before booting up 18.04.  I got connected, then did a reboot.  That went without any issues, and I got back into Ubuntu 18.04.  After getting back into Ubuntu, I started up this browser session; Ubuntu remembered my WiFi configuration from the previous boot.  So, no issues rebooting with WiFi turned on (or off).  Sorry, I no longer have 16.04, so I can't comment on that.  My active kernel is 4.15.0-39-generic."
1776616,2018-06-13 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776616,2018-06-14 16:11:21 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1776616,2018-06-14 18:19:32 UTC,This installation is running from a ZFS root. Would upgrading the kernel to mainline cause the zfs module to not work?
1776616,2018-08-07 15:24:27 UTC,"hardware: IBM thinkpad T41p
xubuntu version 18.04 LTS 32bit"
1776616,2018-09-01 07:28:48 UTC,"Hardware:
System: Packard Bell imedia S3210
Board: Packard Bell WMCP78M (nvidia based)
CPU: AMD Athlon(tm) 7550 Dual-Core Processor"
1776616,2018-10-25 04:46:33 UTC,"4.15.0-38-generic is also affected. I had zero problems with xenial, this only happens since I upgraded to bionic..."
1776616,2018-10-29 22:29:05 UTC,Exactly the same problem with current 18.04 kernels and also current 4.19 mainline kernels. System hangs at shutdown/reboot/poweroff etc.
1776616,2018-10-30 04:25:52 UTC,Seems like it's a regression happens between v4.4 and v4.15?
1776616,2018-10-31 18:07:29 UTC,I would say that this started with kernel 4.8 ( Ubuntu 16.10).
1776616,2018-11-06 14:37:28 UTC,Would it be possible for you to do a kernel bisection?
1776616,2018-11-13 05:28:44 UTC,"Just upgraded an old Toshiba Satellite A215-S7422 with AMD Turion X2 from 16.04 to 18.04.  Was working fine under 16.04.  Now I'm encountering this same issue.  I don't use this laptop very much, so I can run tests on it."
1776616,2018-11-13 09:35:23 UTC,Got some testing results:
1776616,2018-06-13 08:21:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1776616,2018-11-14 02:08:22 UTC,"Following the lead of #12 (sorry, I originally said #10, but could not edit to correct), I confirm those findings."
1776616,2018-11-15 05:30:29 UTC,Minimize the bisection range can save lots of time to compile kernel. Of course you can still start a bisect right away:
1776616,2018-11-16 00:34:41 UTC,I found a related post here:
1776616,2018-11-16 02:25:36 UTC,"I tried the bisect procedure, but failed to build a kernel.  First, the provided link won't work:"
1776616,2018-11-17 04:55:04 UTC,"Ugh, partial retraction.  The above solution works for reboot, but not for shutdown. I managed to get one shutdown session to show me the console, and the final statement was something like ""poweroff reached"", and then it just sits there forever."
1776616,2018-11-19 04:34:27 UTC,"Guy Rouillier, thank you very much for trying to fix this issue."
1776616,2018-11-08 05:59:52 UTC,Hi.
1776616,2018-11-20 02:42:15 UTC,"I tried with 4.5.7, nothing changes with WiFi on or off"
1776619,2019-09-19 11:58:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1776621,2020-10-14 12:22:58 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/575034"
1776621,2018-06-13 09:02:26 UTC,"The scenario is as follows:
1. There is one VC cluster and we have 8K vms running
2. The periodic task puts a huge load on the DB as for each instance the instance object is refreshed and there is a hug burst on the DB
3. In order to tweak the burt we tried to reduce the pool size"
1776621,2018-06-13 08:59:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575034"
1776622,2018-09-10 08:39:20 UTC,"We found the root cause now and work on a fix. sorry for the trouble - Note that this is a ""cosmic"" specific issue. I'm exploring workarounds now to unblock you."
1776622,2018-09-10 08:55:13 UTC,"Bug 1781513 is on bionic, so that's not the same issue as this?"
1776622,2018-09-10 10:21:54 UTC,"workaround is easy: modify /var/lib/snapd/seed/seed.yaml and restart snapd
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1785388"
1776622,2018-09-10 11:34:07 UTC,Note that according to Oliver in the above linked bug #1785388 this is currently intentional in Cosmic
1776622,2018-09-13 07:26:49 UTC,"Same issue here, I do ""sudo pkill snapd"" every time dpkg gets stuck on setting up snapd, at least this lets other packages to continue installing/updating."
1776622,2018-09-15 11:44:12 UTC,"On a new install from Ubuntu 18.10 ""Cosmic Cuttlefish"" - Alpha amd64 (20180913) the update+upgrade installed the new snapd (2.35.2+18.10) over (2.35.1+18.10)
and now i have all the default snap working"
1776622,2018-10-04 05:37:33 UTC,Dropped severity.
1776622,2019-03-06 05:18:44 UTC,Was this fixed? I haven't encountered it in a while.
1776622,2019-03-06 05:20:10 UTC,Although that may just be because I am mainly using 19.04 and to a lesser extent 18.04.
1776622,2019-05-06 04:17:25 UTC,[Expired for snapd because there has been no activity for 60 days.]
1776622,2019-05-06 04:17:27 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1776622,2020-03-02 08:54:44 UTC,Confirmed on 20.04 today.
1776622,2020-03-02 09:00:10 UTC,"Further to comment #38, here's a workaround that works for me on 20.04:"
1776622,2020-03-04 14:50:52 UTC,I can confirm i hit this with a fresh install of Focal Desktop today.
1776622,2020-04-09 05:50:31 UTC,I also hit this today while running 'do-release-upgrade --dev' to upgrade a system from eoan to focal.
1776622,2020-04-09 15:15:01 UTC,"This seems to be a snapd issue, not a systemd one."
1776622,2020-08-24 22:04:14 UTC,"Michael, could you confirm this was a cosmic-specific bug as there's a report of a similar problem with an upgrade from eoan to focal?"
1776622,2020-08-25 01:35:59 UTC,This is a focal bug already.
1776622,2020-08-31 09:24:45 UTC,"This problem is triggered by incorrect ""/var/lib/snapd/seed/seed.yaml"" files. At various points during the development cycles they were incorrect and that has (almost) no effect on the live-cd or the installed system. However on the next snapd refresh it would trigger the hang people are experiencing. The hang is caused by services waiting for ""snapd"" to finish seeding but that never happens because the seed.yaml is incorrect."
1776622,2020-12-01 05:21:47 UTC,Updating snap never finish-while I do not have/removed all snaps.
1776622,2020-02-27 22:01:24 UTC,Experiencing the same issue running `apt upgrade` after a fresh Ubuntu 20.20 install.
1776622,2018-09-10 07:09:53 UTC,the ps output I addet to my bug https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791087 is from a laptop install
1776622,2018-06-21 01:30:42 UTC,A fresh install would probably work around the problem. Although the next update to snapd might then hit it again.
1776622,2018-09-10 07:07:18 UTC,"Michael, I am not Alex but I had the same on a completely fresh Cosmic install from the Desktop image to a new latop (Asus ZenBook Flip UX561UD). No special polkit/pam configs, after the install was finished I ran an update and there it was"
1776622,2018-06-13 20:15:04 UTC,"problem does not occur on same hardware, different partition installed from
Ubuntu 18.10 ""Cosmic Cuttlefish"" - Alpha amd64 (20180509)
where snap list is:
corrado@corrado-p6-cc-0509:~$ snap list
Name                  Version    Rev   Tracking  Developer  Notes
core                  16-2.32.8  4650  stable    canonical  core
gnome-3-26-1604       3.26.0     64    stable/…  canonical  -
gnome-calculator      3.28.1     178   stable/…  canonical  -
gnome-characters      3.28.2     101   stable/…  canonical  -
gnome-logs            3.28.2     37    stable/…  canonical  -
gnome-system-monitor  3.26.0     45    stable    canonical  -
gtk-common-themes     0.1        319   stable    canonical  -
corrado@corrado-p6-cc-0509:~$"
1776622,2018-06-14 01:05:23 UTC,It might be worth grabbing a second or two of strace output from those processes to get a feeling for what they are trying to do.
1776622,2018-06-14 02:01:46 UTC,Workaround:
1776622,2018-06-14 09:17:14 UTC,"Adding strace, I hope is useful"
1776622,2018-06-20 16:16:24 UTC,"Problem does not happen on a new install from Ubuntu 18.10 ""Cosmic Cuttlefish"" - Alpha amd64 (20180620) on same PC
corrado@corrado-p13-cc-0620:~$ apt policy snapd
snapd:
  Installed: 2.33+18.10ubuntu3
  Candidate: 2.33+18.10ubuntu3
  Version table:
 *** 2.33+18.10ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status
corrado@corrado-p13-cc-0620:~$"
1776622,2018-06-13 15:39:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776622,2018-06-25 07:25:16 UTC,Although a fresh install won't work on most systems because of bug 1775743.
1776622,2018-06-26 04:17:59 UTC,I tried installing snapd since a new version was released last week but still the same problem:
1776622,2018-06-26 15:34:10 UTC,after changing /var/lib/snapd/seed/seed.yaml as suggested in https://ubuntuforums.org/showthread.php?t=2393347&page=3 sudo dpkg --configure -a works fine.
1776622,2018-07-25 19:51:30 UTC,"This bug shouldn't be an issue on a fresh 18.10 install using latest image (07/23 or newer
(- the included gnome-calculator snap is completely unusable (will not start) but that's not this bug..."
1776622,2018-08-20 02:54:20 UTC,sane problem upgrading to snapd 2.35~pre3+18.10.5 on 18.10
1776622,2018-08-20 02:55:23 UTC,"Setting up snapd (2.35~pre3+18.10.5) ...
Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine.real ...
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it."
1776622,2018-08-20 17:21:54 UTC,"Since ctrl-c doesn't seem to work to interrupt the upgrade, I had to ctrl-z and I checked pstree.  It seems that the init script runs systemctl, which runs systemd-tty-ask-password-agent, and that hangs, never presenting a prompt.  I tried to kill that and it became a zombie, never being reaped by systemctl."
1776622,2018-08-21 20:20:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776622,2018-09-04 17:32:47 UTC,again with new snapd from proposed
1776622,2018-09-07 10:21:23 UTC,"Thanks for your bugreport. The output of ""ps afx"" when this hangs would be great to get an idea why the dpkg process blocks."
1776622,2018-09-07 14:46:10 UTC,"I added output from ""ps afx"" in my bug: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791087"
1776622,2018-09-09 09:36:24 UTC,"This happend to me repeatedly on Ubuntu Bionic too, making snaps uninstallable. How can such bugs come through. They can be easily catched with automated tests. I remember this bug happened to me after a fresh Ubuntu Bionic installation. An now again after updating snap. Please automate your tests!"
1776622,2018-09-10 06:22:23 UTC,"Hey Alex first, sorry for the trouble you have! We do run ~2800 tests which each branch merged or release. This includes an automatic upgrade test. Unfortunately the hang is not reproducible for everyone it seems, neither our automatic tests nor I in a VM have managed to trigger this hang. But we are very keen to learn what is missing to reproduce this issue. Is there anything special on the systems you experience this issue (unusual polkit configuration or special integration with pam or similar)."
1776622,2018-09-10 06:24:57 UTC,What we see in the ps output is that for some reason it seems like systemctl prompts for a password. Which is unusual because apt/dpkg runs as root so there should be no need for this. Any further hints for us? Are these desktop or server installs?
1776622,2018-09-10 07:06:56 UTC,I think I've hit this with most/all cosmic desktop installs for the past few months.
1776622,2018-09-10 07:08:05 UTC,"Unfortunately the machine is a friend's and not in my hands anymore, but I can probably check next weekend if necessary"
1776629,2018-06-24 09:41:21 UTC,Same here - but for seven days.
1776629,2018-06-25 00:12:17 UTC,"Not sure who the moderator should be there. I used to do it but since I changed jobs I have no time. I would suggest to start a conversation on a mailing list, maybe contact directly the OpenStack User Committee and raise the issue there."
1776632,2018-08-29 15:33:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776632,2019-08-28 20:51:56 UTC,It looks like there is an option to suppress this. I just encountered the same problem and found information in the following tickets to be helpful:
1776632,2019-08-29 08:43:54 UTC,"A whitelist merely cures the symptoms not the cause.
Here the cause is that line terminators are expected.
Thus I still think there should be an option to allow all lines with missing line terminators or allow lines with or without line terminators as the default."
1776634,2018-06-13 10:21:37 UTC,"Can you please *attach* a full log; it's not really dib at fault here, it's one of the elements, but it's not clear which one from this log"
1776634,2018-06-14 08:17:16 UTC,"Ok, the full log is shown in the attachment."
1776634,2018-07-11 10:42:48 UTC,"This is a problem with pip 10:
https://github.com/pypa/pip/issues/4805"
1776640,2019-12-02 09:03:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776652,2020-06-11 16:17:44 UTC,probably duplicate of bug #1794067
1776652,2019-05-26 17:45:42 UTC,"If the problem is corrected as stated by Mauricio Grueso (Above) Why has this not been fixed? His note was dated June of LAST YEAR! This fix might also fix the MANY other bugs of the same type I have encountered. I am no programmer so I really don't know how to incorporate Grueso's fix. Thank you,"
1776652,2018-06-16 14:10:59 UTC,"this is the content of the the comment on the line of cp is for me
#!/bin/sh -e
# Copy the compatibility symlinks until initramfs-tools will be converted
# to use the kmod program."
1776652,2018-06-16 14:10:34 UTC,"this problema was resolv the problem was in the file /usr/share/initramfs-tools/hooks/kmod, tha have a aditional line that ""cp -a   /sbin/modprobe /sbin/rmmod $DESTDIR/sbin/"" generate the error in the script  , that for this reasons all process that execute this script was fail, i put the line in comment and all working without problem"
1776652,2018-06-16 14:09:56 UTC,the problem was in the file /usr/share/initramfs-tools/hooks/kmod
1776652,2018-10-07 06:38:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776665,2018-07-13 00:55:48 UTC,"This is lower priority since the only part of juju which needs to use relation id is dealing with CMR offer connections, and the id is clearly shown on the relevant status output in that case. Normal non CMR relations continue to use the recommended relation key."
1776680,2018-06-30 00:49:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776682,2019-01-16 05:29:38 UTC,"I have noticed this as well.  Programs installed using snaps won't pin to docky, but standard form do.  Example I noticed in particular:  Okular (both forms of the programs available in the software center)."
1776683,2018-06-14 05:56:33 UTC,"Versiony of >=Artful already got this update.
So this is about SRU thought only."
1776683,2018-06-14 06:02:18 UTC,"Repo is mirrored and accessible at https://github.com/oVirt/ovirt-guest-agent.git
There is no trivially identifiable ""this is the fix"" that could be backported for the SRU [1] policy."
1776688,2018-06-25 09:00:05 UTC,"Worth noting that these options only apply to SQL backend domains; with LDAP backed domains its assumed that LDAP will provide these policy features, not keystone."
1776688,2018-06-25 09:01:35 UTC,We may also be able to override the policy defaults for service account users; either way needs careful consideration.
1776688,2019-09-03 10:07:33 UTC,In order to enable this feature safely we'll need ensure that its not possible to lockout service accounts or force password changes otherwise it's possible to realise the DOS attack details in #1.
1776688,2020-02-19 14:50:23 UTC,"Reviewed:  https://review.opendev.org/702684
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=e83cb05bf86ab797c83964e4287b5879297ecda0
Submitter: Zuul
Branch:    master"
1776689,2018-07-20 16:18:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584439"
1776689,2019-04-05 16:02:25 UTC,"FYI, track the related reviews here:
https://review.openstack.org/#/q/topic:bug/1776689+(status:open+OR+status:merged)"
1776689,2019-06-21 14:14:28 UTC,"Reviewed:  https://review.opendev.org/584439
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=92a10628303e9344385b9ad0c92661a9bb3c0b2e
Submitter: Zuul
Branch:    master"
1776695,2018-06-19 12:09:14 UTC,"This is a log file for Open Rails. Please include this file in bug reports.
--------------------------------------------------------------------------------
Date/time  = 18-Jun-18 12:51:08 AM (2018-06-17 19:21:08Z)
BIOS       = BIOS Date: 01/18/11 11:28:00 Ver: 04.06.04 (Intel Corp.)
Processor  = Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz (4 threads, 2 cores, 3.1 GHz)Error: Player's locomotive C:\Users\Admin\Downloads\demo\trains\trainset\WAP530025\WAP530003.eng cannot be loaded in C:\Users\Admin\Downloads\demo\TRAINS\CONSISTS\12952 NDLS BCT Rajdhani Exp.CON
   at Orts.Common.ORTraceListener.TraceEventInternal(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\Orts.Simulation\Common\ErrorLogger.cs:line 173
   at Orts.Common.ORTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\Orts.Simulation\Common\ErrorLogger.cs:line 123
   at System.Diagnostics.TraceInternal.TraceEvent(TraceEventType eventType, Int32 id, String format, Object[] args)
   at System.Diagnostics.Trace.TraceError(String format, Object[] args)
   at Orts.Simulation.Simulator.InitializePlayerTrain() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\Orts.Simulation\Simulation\Simulator.cs:line 1039
   at Orts.Simulation.Simulator.InitializeTrains(CancellationToken cancellation) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\Orts.Simulation\Simulation\Simulator.cs:line 506
   at Orts.Simulation.Simulator.Start(CancellationToken cancellation) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\Orts.Simulation\Simulation\Simulator.cs:line 397
   at Orts.Viewer3D.Processes.GameStateRunActivity.Start(UserSettings settings, String acttype, String[] args) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\GameStateRunActivity.cs:line 275
   at Orts.Viewer3D.Processes.GameStateRunActivity.<>c__DisplayClass8.<Load>b__3() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\GameStateRunActivity.cs:line 150
   at Orts.Viewer3D.Processes.GameStateRunActivity.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\GameStateRunActivity.cs:line 190
   at Orts.Viewer3D.Processes.LoaderProcess.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\LoaderProcess.cs:line 158
   at Orts.Viewer3D.Processes.LoaderProcess.DoLoad() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\LoaderProcess.cs:line 138
   at Orts.Viewer3D.Processes.LoaderProcess.LoaderThread() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\LoaderProcess.cs:line 109
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionCon..."
1776707,2020-05-10 14:12:34 UTC,Implemented here: https://github.com/mixxxdj/mixxx/pull/2618
1776709,2019-08-12 16:37:32 UTC,Confirmed still an issue in 3.3
1776711,2018-06-13 16:42:39 UTC,kindly help
1776711,2019-12-04 16:23:29 UTC,the issue looks like a corruption rather than a package bug
1776712,2018-06-14 07:01:10 UTC,this is openstack queens version
1776712,2018-06-14 07:09:22 UTC,Have you installed the heat dashboard horizon plugin? It has been split from horizon in Queens. You can check the devstack installation docs[1].
1776717,2018-06-13 17:00:01 UTC,It was for building for arm64
1776725,2018-07-23 13:09:46 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1096.101
1776732,2018-10-09 22:05:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776736,2020-08-14 16:54:00 UTC,Thanks Terran. New bug #1891689.
1776736,2019-03-15 15:43:31 UTC,Branch updated in place to use open-ils.cat API instead of pcrud.  This has the added benefit of allowing permission failures on update to prompt for an override.
1776736,2020-08-14 15:32:10 UTC,"I see the edits save now, and there is an option to use flat text editor as well. That's great. Is there any plan to have the editing window not cover the screen? As Sarah mentions, you can no longer see the records when the editing window pops up. Copy/pasting is nearly impossible."
1776736,2019-03-20 19:30:06 UTC,"This branch does the three things it claims, and I don't see any negative effects.  Thanks, Bill!"
1776736,2019-03-15 15:34:29 UTC,Updating solution to this bug to use the API consistent with bug #1693580.
1776736,2020-08-14 16:24:48 UTC,"Hi Kate - Since this fix was already released, could you please create a new launchpad bug describing the problem with covering the screen/ copying & pasting mentioned above?"
1776736,2019-03-13 21:43:35 UTC,I just accidentally discovered that the inline MARC editor in the record merge interface will use the flat text editor that's how the MARC editor was last used.  I'm guessing having a toggle there would still be nice.
1776736,2018-06-13 21:10:31 UTC,"Aside from flat out not working, the current functionality of this is extraordinarily clunky even if the edits were savable. The main use case for this is to copy information from a record or records to be merged into the lead record. In the XUL client you can have all the records to be merged side by side and open to the flat text editor which allows you to easily copy information from one record to another."
1776736,2018-09-13 13:44:34 UTC,Confirmed in 3.2 beta 1
1776736,2019-03-14 16:07:18 UTC,Fixes pushed:
1776736,2019-03-08 18:28:04 UTC,I agree -- flat text editor is much more efficient for copying and pasting fields from one record to another. And you do need to see both records in order to be able to do so readily.
1776736,2019-03-08 22:47:42 UTC,"In the xul client (3.0) it's possible to **drag** fields from one record to another when tiled side-by-side both in flat text mode. I've been using this to add annotations, subjects, ISBNs or contents notes when merging so the kept record has the info of both records combined.
With the advent of baskets merging, or simply tiling, to a few records can become even easier so I'd definitely welcome improving flat text editing along with the improvements in the merging development."
1776736,2019-03-05 22:48:20 UTC,"Was going to open an new LP, but Sarah's comments match those of our staff, so I'll add mine here."
1776739,2018-06-15 14:56:19 UTC,The relatively small scrolling window is has a bug report.
1776739,2018-06-15 14:28:39 UTC,+1
1776740,2018-06-13 19:17:45 UTC,"On 13/06/18 19:32, Willem Hobers wrote:

> Public bug reported:
>
> General remark: most parts of the test are not mandatory. Some one
> without any bluetooth devices, will only do the first two steps and then
> skip the rest – and report the test a success. We should perhaps add a
> note that people should leave a comment on which parts they skipped?
>
> “Change the name to ""blueman_test"". Click on close.
> The box for the name is called “Friendly Name”
>
> “The window closes. You changed the name of the computer's Bluetooth adapter.”
> We haven’t really checked if indeed the name change persists. Perhaps add a way to find out if it did indeed change?
>
> “The test requires a Bluetooth device with search functionality for other Bluetooth devices, e.g. a mobile phone. If you do not have one, skip the test.”
> In other test cases this kind of directions are mostly not part of the numbered list I believe.
> These kind of directions appear, also as part of the numbered list, at several places in this test case.
>
> “Click on ""forward"".”
> The button is “next”, at my end.
>
> “Search for your input device and select it. Click on ""Forward"".”
> The button is “next”, at my end
>
> “Select ""Proceed without pairing"" and click on ""Forward"".”
> The button is “next”, at my end
>
> “Select ""input device"" and click on ""Forward"".”
> The button is “next”, at my end
>
> (I’ll just add that there’s “forward” throughout the test case, but the
> button seems to be called “next”.)
>
> “Search for your input device and select it. Click on ""Forward"".
> A window with pairing options appears.”
> I don’t think so. I tried this with a phone – the question I got was “Connect to: Audio Source, Netwrork Access Point, Don’t connect”.
>
> I chose Audio Source to see if I could proceed with the test case.
>
> “Select ""Use random Passkey"" and click on ""Forward"".
> A random passkey is generated and shown in the assistant.
> Accept the connection in your storage device and enter the passkey.
> The device is added to your computer. The ""Connect"" window appears.”
>
> This didn’t work as described here. The passkey was generated and all I
> had to do was accept or deny. I did not have to put in the number by
> hand.
>
> Haven’t been able to check this part of the test, because things work differently for me (I don't have a BT mouse or keyboard):
> “Select ""serial port"" and click on ""Forward"".
> A window appears showing ""Device added successfully.""
> Click on ""close"" and open the context menu again. Click on ""Browse file on devices"".
> A window appears with a list of available Bluetooth devices.
> Select your storage device and click on ""OK"". Accept the connection on your device.
> The file manager is opening, showing the available data on the device.”
>
> ** Affects: ubuntu-manual-tests
>       Importance: Undecided
>           Status: New
>


I'm inclined towards removing any refs to parts being optional, make all
parts of the test required."
1776742,2018-06-13 19:11:56 UTC,setting as wishlist per chat with the OP.
1776742,2018-06-14 16:19:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776745,2018-06-29 13:10:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776748,2019-04-14 03:55:18 UTC,"I can confirm that this is still an issue. I tested on an Acer5740 laptop. The issue can be noted from the attached screenshot.
Package: nm-tray
Version: 0.3.0-0ubuntu1
Linux 4.18.0-18-generic x86_64"
1776748,2018-11-25 23:05:30 UTC,"For what it's worth, the MATE and Xubuntu bugs are not entirely related. They do indeed have the same exact problems (the indicator applet duplicating things) but since we're dealing with three independent panels, each with their own implementations of the applets, they are not at all related. Put another way: if we fix this in Lubuntu, it won't fit anything for Xubuntu or MATE and vice versa."
1776748,2019-04-16 16:42:23 UTC,"Walter, on ~/.config/lxpanel/Lubuntu/panels/panel, the plugin type indicator has two preferences, sound and apps, when sound enabled only sound icon is shown, when apps enabled the network icon and other apps (like cliptit, multiload, etc) is shown; on other hand the plugin type tray shows the battery icon and network icon."
1776748,2018-11-25 03:11:54 UTC,I am also experiencing this on Ubuntu Mate 18.10 using the Cupertino layout.
1776748,2018-10-24 19:57:03 UTC,"Given that we autostart nm-applet and that it exposes functionality not provided by the indicator-applets plugin. The plugin does not allow one to turn off which indicators one wants. It's either toggling sound or toggling all other indicators. That said, we should remove the indicator-applets plugin, which is ultimately just problematic, not just with networking but with sound, keyboard, etc."
1776748,2018-11-25 13:00:15 UTC,"This also occurs on xubuntu 18.04 and badly breaks the user experience an other solid ubuntu system. There is a related bug raised here, its high time this should be fixed now:"
1776757,2018-08-08 15:48:10 UTC,"Also if a billing type does not have a default amount associated, selecting it will not clear a previously selected/entered amount."
1776757,2018-08-08 16:53:32 UTC,"Marking confirmed. In the xul client, the Amount field updates to the default_price for the selected billing type each time one is selected. If a billing type with NULL default_price is selected, the Amount box clears. The web client should behave similarly."
1776757,2020-01-29 20:46:25 UTC,Here's a branch with a fix:
1776757,2020-02-11 23:58:51 UTC,"The branch has been modified so that for the billing dollar amount shows 2 digits after the decimal.  (e.g. ""2.50"" instead of ""2.5"")"
1776757,2020-02-20 20:51:25 UTC,Works like a charm! My sign off is at:
1776757,2020-07-28 14:47:43 UTC,"Upon reviewing the patch, I note that changing the type of the input (per comment #4) removes a bit of form validation: specifically, non-numeric values for the amount would be permitted to be submitted.  Of course, the billing will fail to be saved, but it is a bit of extra untidiness."
1776760,2020-09-26 17:21:34 UTC,Have you tried to report this issue to the Spice projects (see https://www.spice-space.org/support.html) ?
1776760,2020-11-26 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1776761,2019-12-05 09:18:03 UTC,Fixed in 1.1.20-2 which means >= Ubuntu 19.04.
1776761,2018-06-14 05:04:11 UTC,"I filed a bug with Debian, as well. It turns out they've already got a package 1.1.24-1 package pending upload to universe. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901484#17"
1776761,2018-06-16 00:21:55 UTC,"Correcting my last comment: Debian's updated package version is 1.1.20-2 (up from 1.1.20-1), in which the fix has been backported from the upstream commit."
1776761,2018-06-18 20:03:52 UTC,"I see that Cosmic now includes Debian's fixed 1.1.20-2 package. Can it be updated for Bionic, as well?"
1776762,2018-06-13 21:00:05 UTC,Fixed in x.4154.
1776762,2018-06-14 14:08:10 UTC,Further fix in x.4155.
1776771,2018-06-14 11:41:20 UTC,Can it just be set to a suitably huge value to avoid the need to configure it?
1776771,2018-06-14 13:17:54 UTC,"That should be fine, that's usually what people do anyways when an option is given."
1776773,2018-06-14 01:35:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776774,2020-01-27 23:29:05 UTC,Yes its still the same or the issue is still out there. I get a rainbow flash then it stops and will not go any further with the following initramfs prompts
1776774,2019-02-04 10:17:12 UTC,Any progress on Ubuntu Mate for Raspberry Pi 3b+?  I have tried it the last couple of days and cant get the SD card image to boot.
1776774,2018-11-07 11:28:16 UTC,"Interestingly, i have the same issue. For the life of me,no matter what  i did or tried to do, i cannot boot from an 32g sdcard or a usb stick. Hlp please"
1776774,2018-06-23 07:04:12 UTC,From the forums on the Raspberry Pi webpage people are also saying the B+ firmware differs from the original B. I dont own an original B so I can't compare them. I hope B+ gets MATE compatibility soon!
1776774,2018-06-15 14:26:59 UTC,"This ""bug"" can be closed. The issue has nothing to do with the microSD cards and booting. The issue is simply that no aarch64 ARMv8 build exists for Ubuntu & Ubuntu MATE. I've learned that that *may* get resolved in the July timeframe when 18.04 support for the RPi 2/3/3b+ is created."
1776774,2018-06-14 20:54:51 UTC,"Thought: The Raspberry Pi 3 uses a 32-bit ARM Cortex A7 CPU; however the Pi 3b+ uses a 64-bit ARM Cortex A53 CPU (which uses the A8 instruction set). When looking at the Ubuntu MATE download page for the Raspberry Pi, the link to the image says, ""For aarch32 (ARMv7) computers, like Raspberry Pi 2/Raspberry Pi 3""."
1776778,2018-10-31 03:45:52 UTC,It seems that bug fixed in kernel-3.10.0-898.el7.
1776778,2018-10-31 03:23:19 UTC,I met same problem in CentOS7.5 with kernel 3.10.0-862.el7.x86_64.
1776778,2018-08-24 18:59:22 UTC,"I'm not sure of the last question, but I do not see a kernel >862 in the centos repo yet.  Hopefully that gets published soon since there is no workaround in neutron for this."
1776778,2018-08-24 06:16:31 UTC,Is there a message to fix this bug now?
1776778,2018-07-19 01:13:41 UTC,"FYI:
This kernal bug can also break the L3 routers:
https://bugs.centos.org/view.php?id=11238"
1776778,2018-07-02 02:02:01 UTC,"I found same problem in 4.15.0-23-generic, Ubuntu 18.04."
1776778,2018-06-15 13:38:05 UTC,"I hadn't linked the BZ since I thought it was private, but guess that isn't the case any more.  Assuming people have access of course..."
1776778,2018-06-14 14:58:56 UTC,"This is a known issue with that particular kernel, there is a problem with the ""notrack"" netfilter code.  I would recommend reverting to the older one or waiting for an update to be published."
1776778,2018-06-14 22:44:29 UTC,FYI this seems to be a pretty serious bug. It kills a core neutron functionality and leaves VMs inaccessible. Is there no advisory/kernel bug/other Openstack bug/release notes about this? I could not find anything. How are people to know when it is safe to do a simple yum update?
1776778,2018-06-14 22:30:16 UTC,Does this affect security groups?
1776778,2018-06-14 20:47:06 UTC,"Thanks, please let me know if you have any more info on this issue - such as an upstream RHEL bug, mailing list discussion, IRC chat notes, technical details of exactly what is going wrong, etc..."
1776778,2018-06-14 07:56:34 UTC,"Issue specifically seems to be with the newer kernel that came with update to Centos 7.5. We also hit issue on a Centos 7.4 image, but which has the same newer kernel:"
1776778,2018-06-13 22:29:09 UTC,Here are contents of sysctl.conf:
1776778,2018-06-13 22:28:35 UTC,"What is also observed is that the fip namespace can ping the local floating IP. We see the qrouter NAT'ing, then routing packet to VM. But this does not occur when we ping from outside the host:"
1776778,2018-06-15 02:01:16 UTC,Here's the bug report which details the exact issue: https://bugzilla.redhat.com/show_bug.cgi?id=1572983.
1776780,2019-11-08 23:04:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/693600"
1776780,2019-11-14 00:54:19 UTC,"Reviewed:  https://review.opendev.org/693600
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=c6b135270da6c5cc1e63271914eb73de6ea6302e
Submitter: Zuul
Branch:    master"
1776782,2018-07-09 09:36:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776800,2018-10-11 19:15:00 UTC,This was also discussed here: https://askubuntu.com/questions/1040194/how-to-use-snap-packages-when-home-is-not-home-user
1776800,2019-03-19 07:47:32 UTC,- have related issue...
1776800,2019-03-25 10:35:59 UTC,This is a known limitation. We have some plans on how to change that but this is not something we can commit to this ubuntu cycle.
1776800,2018-06-14 07:17:20 UTC,Affects me too in /local/home/$USER
1776805,2018-06-14 04:21:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1776812,2019-02-08 09:09:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776820,2018-06-20 09:28:06 UTC,"3.13.0-153.203~precise1 - generic
Regression test CMPL, RTB."
1776820,2018-07-02 09:05:07 UTC,The package has been published and the bug is being set to Fix Released
1776830,2018-06-14 07:33:44 UTC,This is caused because keystone v3 tokens exceeds the max header size allowed in swift.
1776830,2018-06-14 09:00:45 UTC,The problem still exist
1776830,2018-06-19 08:11:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576412"
1776830,2020-06-09 05:24:24 UTC,Still and issue as of today in Rocky.
1776830,2020-06-09 05:33:27 UTC,Does this config change need to be included in all of the below?
1776830,2020-07-13 09:22:27 UTC,"The discussion in the proposed patch suggests more work may be required than just adding that config option. If you can verify that it works, we could accept it."
1776835,2019-09-24 14:41:51 UTC,"I can confirm. The problem is, icons are not scaled (at all) to fit into the tray. The huge gray-and-black thing taking most of the panel on the attached screenshot is actually this icon: https://github.com/nekr0z/matebook-applet/blob/master/assets/matebook-applet.png
KDE knows how to scale tray icons properly. So did Gnome when Gnome still had tray."
1776837,2018-06-15 08:22:10 UTC,Related commits list:
1776837,2018-07-26 16:10:51 UTC,"Can we move this bug to the ""Linux"" package and make it public?"
1776838,2020-03-05 15:39:21 UTC,"Hi, thanks for your bug report. This issue is being tracked at https://gitlab.com/inkscape/inkscape/issues/1077."
1776840,2018-06-19 03:23:31 UTC,"Hi, Jochen."
1776840,2018-06-19 09:17:54 UTC,The patch solves the problem. Many thanks!
1776840,2018-07-20 01:23:17 UTC,"Queens backport patch was submitted here:
https://review.openstack.org/#/c/584172/"
1776851,2018-06-29 04:38:07 UTC,"I just retested this on a new RPI3B+, and it works if you read and follow the blog https://www.kvaser.com/developer-blog/building-canlib-linuxcan-raspberry-pi/"
1776853,2018-10-09 12:09:20 UTC,"Please see [1] for similar problem and solution by Klaus:
https://answers.launchpad.net/yade/+question/446239"
1776853,2019-02-05 19:57:36 UTC,moved from https://bugs.launchpad.net/yade/+bug/1776853 to https://gitlab.com/yade-dev/trunk/issues/42
1776854,2018-07-17 18:07:36 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/583325"
1776854,2018-07-31 10:59:00 UTC,"we have to backport vpnass changes in ansible roles to queens, as the image is not present but roles still using them"
1776854,2018-07-18 14:07:56 UTC,"Change abandoned by Jeffrey Zhang (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/583325"
1776854,2020-06-02 08:36:53 UTC,"Queens is in extended maintenance, no point releases are to be done after announcing EM. And we don't back port functionalities, especially to EM releases."
1776857,2018-06-14 08:33:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776857,2018-06-15 06:44:12 UTC,"Two of the three are already tracked https://people.canonical.com/~ubuntu-security/cve/pkg/strongswan.html it seems.
I'll subscribe the security Team to evaluate and comment here."
1776857,2018-06-15 13:40:17 UTC,i am also affected by packet loss during IKEv2 CHILD_SA rekeying [1] and would like to see [2] backported to xenial in addition to the CVE fixes.
1776857,2018-06-18 13:29:40 UTC,"Bump, we would also welcome an update to 5.6.3 for the reasons listed above."
1776857,2020-11-03 00:12:22 UTC,Marking as fix released as Ubuntu Focal shipped with strongswan 5.8.2 (> 5.6.3). All supported releases also got the mentioned CVEs fixed.
1776862,2018-06-14 08:52:10 UTC,no more comment
1776862,2018-07-13 11:37:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776873,2020-04-28 06:09:19 UTC,"Seeing that this bug got considerable attention, I'd like to highlight another bug that is even more serious (in my opinion) which relates to Chromium being snap:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074"
1776873,2020-04-28 06:08:45 UTC,"Sven, allow me to contribute a few corrections/clarifications to your article:"
1776873,2020-04-28 06:04:51 UTC,"Hi Sven Meyer,"
1776873,2020-04-28 05:04:01 UTC,(I just wrote an article about this issue. Feel free to comment before I publish it.)
1776873,2020-04-25 15:22:46 UTC,"@Gilyen: Yes, of course -- or open the link in Firefox.  But that gets really annoying after a while.  I was hoping for a snap package that fixes this without me having to build from source.  Because if I'm going to go that far, I'll just remove the damh hard-coded whitelist completely.  It's one of the most horrible ideas I've seen in a long time."
1776873,2020-04-24 23:35:16 UTC,This bug also affects me on a fresh 20.04 install ...
1776873,2020-04-23 17:46:11 UTC,"With respect, I think focusing on an improved response time for the PRs is missing the forest for the trees."
1776873,2020-04-23 22:41:31 UTC,"Seriously guys, I mean why the heck would you replace something that works like a charm (normal apt, .deb files or PPAs) with something that's still obviously not ready to be thrown at people's machines forcing them to use snaps instead of regular .deb. you don't even leave the user the choice of doing otherwise. Shame on the Open Source community for choosing to adopt such methods. Plus the themes on snaps are broken as well. Like the mouse cursor is white by default for my system, but inside most of snap apps it turns smaller and black too. Why? Cause snap is still to this day a pretty broken and inconsistent POS."
1776873,2020-04-23 18:45:15 UTC,"In short, the best way to improve the situaition is sudo apt purge snapd."
1776873,2020-04-23 17:17:12 UTC,"FYI, in recent PR discussions[1] we've acknowledged that we should make it easier to allow different URL schemes into snapd and I laid out some criteria/process ideas on how to make this happen, and I applied that criteria to the zoommtg PR and it was merged quickly. I discussed with Samuele that we could make this go even faster if we codify things for reviewers as well as some other implementation details."
1776873,2020-04-28 18:18:01 UTC,"Jusr wanted to comment on Samuele Pedroni referring to ""rudeness"" – then I saw that Balazs Gyurak already did: Yes, I saw the comment that has subsequently been removed from this forum post, and Samuele was completely right to object. Please remove this part of your article."
1776873,2020-04-23 16:09:34 UTC,"Contributing to the discussion with rudeness is not conductive to collaboration, and will be moderated."
1776873,2020-04-21 14:52:49 UTC,And then people are surprised why Linux community is no negative to Snap.
1776873,2020-04-23 22:58:33 UTC,Is there a way to get a snapd package with the merged PR for zoommtg:// without recompiling from source?
1776873,2020-04-29 04:07:34 UTC,"Well, you have the Code of Conduct, and we do not have normal software that would not break user systems. Is there any correlation here we cannot discuss because of the Code of Conduct."
1776873,2020-05-04 19:28:37 UTC,"Hi @jean-helou,"
1776873,2020-05-04 12:43:55 UTC,"Support for the zoommtg:// protocol was added to snapd with https://github.com/snapcore/snapd/commit/7f678b923c2af8d899bdb2ba95440d62c1c74123. The core snap from the edge channel (2.45~pre1+git1800.7238107) doesn't seem to have the fix yet, though."
1776873,2020-12-14 11:08:40 UTC,"I'm sorry to say we were forced to move from Chromium to Google Chrome (unconfined deb package). I am not at all happy with that, as our software is now less secure than it was before (with the unconfined Chromium). But I never managed to get the snap running for my users, snaps are just not designed to work in networks. Missing URL handlers was the least of our problems.
Not being able to access network shares and snaps caching into the users's homes was what made it unusable.
Very sad that a decision that supposedly was meant to make Chromium more secure has caused right the opposite for us."
1776873,2020-12-14 09:33:52 UTC,"Snapd got some extra url handlers added to the whitelist but still not some of those described in the description and comments (irc, ssh, git)"
1776873,2020-12-13 05:50:59 UTC,"I recently installed Xubuntu 20.04 and I fail to open magnet links via qBittorrent (installed via apt-get, v4.1.7) :

> snap --version


snap    2.48.1
snapd   2.48.1
series  16
ubuntu  20.04
kernel  5.4.0-58-generic"
1776873,2020-07-06 16:47:50 UTC,Fixed for me and i'm on 2.42 Eoan. Dialog appears to choose the app to open.
1776873,2020-07-06 16:32:14 UTC,Snap 2.45.1 is out now and solves this -- I believe the issue can be marked fixed released.
1776873,2020-06-16 09:38:05 UTC,Snaps do have that concept of plugs and sockets. Shouldn't that be the way of solving this?
1776873,2020-06-16 09:34:46 UTC,"@akkzilla is right, this is more like a problem of general intercommunication of snaps. It probably needs a decent framework for snaps as a whole, not only the chromium snap."
1776873,2020-06-15 21:59:31 UTC,"I'm puzzled by all the people tying this to chromium for zoom. I use firefox and it doesn't work any better there, especially with the zoom-client from snap where it doesn't work at all."
1776873,2020-06-07 21:37:16 UTC,"Just tested it too, magnet links work for me as well! Thanks"
1776873,2020-06-07 20:51:34 UTC,Magnet links are working.
1776873,2020-05-28 11:44:34 UTC,"MS teams & magnet: links both just throw up a ""xdg-open"" prompt but nothing happens when you ""allow"".
This should be fixed and released now, right ?"
1776873,2020-05-23 16:40:28 UTC,"Nevermind my last comment. This works in chromium (no idea about snapd).
To get this to work in chromium, first make sure it works for xdg-open."
1776873,2020-04-21 05:42:38 UTC,"This also affects the scheme ""jetbrains"", it would be nice to login to my JetBrains Toolbox again via Chromium"
1776873,2020-05-04 19:08:49 UTC,"I am happy to see zoom supported, but I can't help being disapointed that slack, vscode, irc, magnet etc still arent. I found this https://github.com/snapcore/snapd/pull/8398#issuecomment-607570865 comment on a PR to add slack which seems to hint that the situation would be resolve in snapd 2.44.2"
1776873,2020-05-04 16:10:54 UTC,"Hi folks, the change that @osomon referenced is available in the snapd snap beta channel, can you try the following to see if you are able to open zoom links from the chromium snap now:"
1776873,2020-05-02 01:17:32 UTC,"I also encouter this problem. Each time someone share a zoom link, chronium cannot open it."
1776873,2020-04-18 22:59:27 UTC,To @kfunk @axet @troyready: That worked perfectly for me. Thank you so much!!!
1776873,2020-04-16 16:00:11 UTC,"Seems like a new linux virus preventing me from running compiled snap. Not the right place to report but who knows? When I recompile the snap package and changed ""help"" output to ""refresh !!! and remove snaps"" and unpack the content of resulting file into 123/. I reinstall the system package and result md5 sum look like this:"
1776873,2020-04-16 21:49:58 UTC,"wow, @kfunk and @axet, thank you so much for this effort!"
1776873,2020-03-02 22:14:44 UTC,Agreed. This seems like fundamental desktop functionality to me.
1776873,2020-03-02 20:41:00 UTC,"Wow.  This is all remarkably chill for a bug that boils down to ""Chrome can't launch external apps"".  I just started a new job and I'm trying to set up ubuntu 19.10 as my primary desktop and I'm being blocked by this.  Both slack and zoom fail to launch because of this.  It also means that apps that want to use Google to authenticate, and thus launch chrome to run the google login and then get a URL callback don't work (Slack in particular)."
1776873,2020-02-29 07:37:13 UTC,Hi! This bug also affects me. Magnet torrent links don't work at all. Could we have an update on this please?
1776873,2020-02-19 19:52:42 UTC,"Sorry for the +1 comment here, but can we revisit the severity of this? 20.04 is coming and it's a notable feature regression for chromium-browser."
1776873,2020-02-12 08:59:49 UTC,"From another report on the snapcraft forum, another custom scheme: urn"
1776873,2019-12-16 20:43:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776873,2020-03-03 08:44:53 UTC,As I said earlier I totally agree with the comment above :
1776873,2019-11-26 16:30:43 UTC,"From duplicate bug #1853008, another custom scheme: zoommtg"
1776873,2019-11-11 20:35:25 UTC,"@osomon there us also ""spotify"" protocol handler: https://developer.spotify.com/documentation/general/guides/content-linking-guide/"
1776873,2019-11-11 18:13:46 UTC,"i'd like to notice that since ubuntu 19.10 chromium is available only as a snap, thus this bug makes it impossible for chromium users to open non-http links in fresh ubuntu from inside browser they've chosen  :(
(the workaround is to copy a link and open it elsewhere, e.g. in firefox)"
1776873,2019-11-11 16:39:02 UTC,"From the 4 duplicate bug reports so far, here is a list of custom schemes that have been reported not to work in the chromium snap:"
1776873,2019-10-29 17:45:32 UTC,"As a result, upgrade Ubuntu to 19.10 broke all our intranet apps/workflow which heavily based on web based portal with a lot of ssh:// links used to quickly open terminal to many thousands managed linux servers and tg:// links to arrange telegram channels related to tasks."
1776873,2019-10-04 09:16:40 UTC,This causes a significant annoyance in the Snap-based Chromium (from Ubuntu 19.10).
1776873,2019-09-20 11:48:02 UTC,The whitelist exists because it acts as a mediation layer where we can at least review the application interpreting the input from the snap world. It is true that this is an inconvenience but the _current_ plan is to keep the whitelist in place and expand it on a case-by-case.
1776873,2019-11-13 12:00:49 UTC,"Here is a pull request to add ""apt"" to the whitelist, which hopefully should be pretty uncontroversial security-wise: https://github.com/snapcore/snapd/pull/7731"
1776873,2020-04-17 02:06:22 UTC,"@cpbl see https://askubuntu.com/a/158872 (""Software & Updates"" in the menu now)"
1776873,2020-03-04 04:10:09 UTC,"This is personally impacting my ability to use Chromium to run the F5 SSL VPN, which uses the f5-epi and f5-vpn schemes."
1776873,2020-03-09 19:22:19 UTC,"@zyga Why this isn't a high pro bug? Many application uses xdg-open to it's login function. I couldn't login e.g in : Slack, Intellij-toolbox so this is instantly breaking the ability to use this snap in a work environment."
1776873,2020-04-16 19:27:11 UTC,I just found the issue second ago. It is related to SNAP_REEXEC behavior. The idea is to run snap from snap_core installed from snap. If you have system snap installed it will be reexec'd from snap core. To disable it you need to change the source.
1776873,2020-04-16 18:27:29 UTC,"Alexey I'm having the same experience as you. It's uncanny, feels like something obvious is missing. Not sure how it's working for Kevin above."
1776873,2020-04-15 12:46:31 UTC,"Okay, after having manually copied and dissected a Zoom URL for the Xth time I finally got annoyed."
1776873,2020-04-08 15:08:22 UTC,Also affecting Slack. Not possible to login to Slack app and I needed to switch to Firefox for now.
1776873,2020-04-03 06:38:47 UTC,Can anyone help with a workaround suggestion while we're waiting for this to get fixed?
1776873,2020-03-06 11:08:42 UTC,"Zoom.us meeting links (zoomus://) are not launching the app anymore. This reduces drastically the productivity, since I have to manually copy the meeting ID into the Zoom app. Multiply that with about 10 meetings a day and it results in moving to Firefox."
1776873,2020-03-23 16:35:57 UTC,"I agree @cpbl -- there are almost certainly better options available. Maciej Borzecki detailed a good proposal at https://github.com/snapcore/snapd/pull/7731#issuecomment-585721100 (with some follow-on thoughts added by jdstrand at https://github.com/snapcore/snapd/pull/7731#pullrequestreview-362900171), but at this point it's up to someone to implement it."
1776873,2020-03-23 16:10:06 UTC,"Yeah, this can be labelled a COVID-relevant bug, since there are countless new users flooding to Zoom, etc..."
1776873,2020-03-23 15:17:43 UTC,"Hate to be another +1 but, any updates on this.  This is quite a major issue for real world use right now."
1776873,2020-03-18 17:20:08 UTC,"any updates on this, manual url interception and copy pasting is getting old :("
1776873,2020-03-12 09:13:55 UTC,"Please add the vmrc URL scheme, needed by VMWare ESXi. Thanks."
1776873,2020-03-11 16:23:11 UTC,i'm sure an easier workaround is to (temporarily) use firefox for this. i use this one when i need to open some tg:// links in telegram app
1776873,2020-03-11 14:58:00 UTC,How I managed to work around this to add a new Slack workspace:
1776873,2020-03-23 16:13:28 UTC,"If the approach so far is to individually whitelist classes of links, surely can't this be better dealt with by doing something similar to how Chromium responds to me clicking on a downloaded file: it asks me if it's okay to have snap launch that file?  Can't we do this for links that go to xdg-open without downloading a file?"
1776873,2020-04-16 12:51:19 UTC,"For some reason I unable to rebuild snapd following #29 instruction. All goes fine, but in the end xdg-open wont work. I've checked /var/log/syslog and it full of:"
1776877,2018-06-22 12:46:38 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1776877,2018-06-14 12:48:39 UTC,Hi Pete!
1776884,2018-07-22 09:21:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776887,2018-07-26 05:13:52 UTC,This bug was fixed in the package linux - 4.15.0-29.31
1776887,2018-07-26 07:09:43 UTC,"Reverting ""Fix Released"" as requested commit not in diff:
https://launchpad.net/ubuntu/+source/linux/4.15.0-29.31"
1776887,2018-08-03 13:29:35 UTC,Any progress on this?  The bug is still biting me.
1776887,2018-08-07 00:01:09 UTC,"4.15.0-30.32 has just been released, and the patch still hasn't been included."
1776887,2018-08-08 05:12:35 UTC,Looks like it's in master-next (-31.33).  See https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master-next and https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-core.c?id=Ubuntu-4.15.0-31.33#n856
1776887,2018-08-08 20:26:41 UTC,"I've just booted into 4.15.0-31-generic that hit proposed, and it seems that the patch was included. From the changelog:"
1776887,2018-08-15 04:39:10 UTC,Can anyone confirm weather this is patched in the new kernel out today...4.15.0-32-generic?
1776887,2018-08-15 07:20:33 UTC,"It was already patched in the previous kernel, 4.15.0-31-generic."
1776887,2018-08-17 15:19:27 UTC,"I left my laptop suspended for a couple of hours while I went out on some errands, and X crashed when I tried to resume it."
1776887,2019-11-01 12:42:41 UTC,This bug is still very much alive in Ubuntu 19.10...
1776887,2019-11-06 12:34:49 UTC,"This bug affects me. Severely. It's more than once per day.
shakespeare@RYZEN:~$ uname -r
5.0.0-33-generic"
1776887,2019-11-07 20:04:28 UTC,"That's not enough information.  At this point you should report a new bug, please."
1776887,2019-11-08 15:58:17 UTC,"I'd like to report a bug:
Ubuntu 18.04 (bionic), Gnome 3.28.2
The frequency is typically more than once per day-"
1776887,2019-11-08 23:41:15 UTC,"I mean, use the link ""Report a bug"" at the top-right of this page.  Not add comments to this bug."
1776887,2018-07-20 17:48:17 UTC,"I had installed 4.15.0-29.31 from proposed, I suppose the packages had been updated, so reinstalled everything:"
1776887,2018-07-20 15:39:45 UTC,This bug was fixed in the package linux - 4.15.0-29.31
1776887,2018-07-21 18:39:05 UTC,"Reverting Fix Released given:
1) diff contained no blk-core changes -> https://launchpad.net/ubuntu/+source/linux/4.15.0-29.31
2) Kleber Sacilotto de Souza explicitly mentioned the updates were not in -Proposed -> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/comments/20"
1776887,2018-07-18 13:30:56 UTC,"I've just upgraded to 4.15.0.29.31 from proposed, and I can confirm Alan Jenkins' comment #17: the bug is still present:"
1776887,2018-06-14 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1776887,2018-06-14 12:21:23 UTC,"Sorry, it's not convenient for me to test Ubuntu at the moment."
1776887,2018-06-14 16:13:26 UTC,"I built a test kernel with commit 1dc3039bc87ae7d19a990c3ee71cfd8a9068f428.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1776887"
1776887,2018-06-15 09:57:56 UTC,Awesome. Thanks.
1776887,2018-06-27 19:07:56 UTC,"I mistakenly filed this exact same bug against xorg-server [1], until Alan Jenkins made a comment [2] about this one. I'm surprised that not more people have reported it or registered as affected users."
1776887,2018-07-20 10:40:12 UTC,"Hi all,"
1776887,2018-06-28 19:25:39 UTC,"Did you install the linux-modules, linux-modules-extra packages first?"
1776887,2018-06-29 13:40:00 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093606.html"
1776887,2018-06-28 16:54:44 UTC,I'd like to test the patched kernel but I've stumbled across this error when I try to install the linux-image-unsigned package and I haven't found out how to solve it:
1776887,2018-07-09 09:48:34 UTC,Also affected by this bug on Xenial with linux-generic-hwe-16.04 4.15.0.24.46
1776887,2018-07-14 05:59:48 UTC,"I'm affected by this bug. I tried the patched kernel posted by jsalisbury above (including modules and headers packages), but it boots in low-res mode (640x480 -- should be 1920x1080), and glxinfo shows the vendor as VMware and device as llvmpipe (should be Intel and Mesa). Is any other information required?"
1776887,2018-07-14 06:03:35 UTC,"Forgot to say, this is Xubuntu 18.04. Previous kernel was 4.15.0-23.25.  I am trying 4.15.0-24.26 from the repo now."
1776887,2018-07-15 12:00:04 UTC,Is there an estimate for when users will receive the SRU?  (Which was submitted on 2018-06-29).  So far I've seen 8 separate questions on askubuntu.com which match this bug.  Poke :-).
1776887,2018-07-18 10:01:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1776887,2018-07-18 12:33:37 UTC,I don't see it!  The changelog doesn't include this fix
1776887,2018-07-18 12:34:06 UTC,"Also, I can confirm Maxim Loparev's comment #12.  The current -hwe kernels in Ubuntu 16.04 ""Xenial"" are also missing this critical kernel fix.  Please can you either update the list of affected Ubuntu versions, or let us know if the bug needs reporting separately?"
1776887,2018-07-02 13:12:10 UTC,"Sorry for the delay, @jsalisbury, I hadn't subscribed myself to this bug's emails. Yes, I installed all linux-modules* and linux-headers* packages first."
1776888,2018-07-04 09:40:59 UTC,"Hi Tone,"
1776888,2020-06-02 08:35:17 UTC,Kolla-Ansible Ceph deployment and Kolla Ceph images have been deprecated and removed (in Ussuri) - I don't think that bug is relevant anymore.
1776888,2018-07-06 02:57:29 UTC,"Hi Tone,
Since you don't understand why I said that your implementation is not good, then I will tell you carefully:"
1776888,2018-07-05 12:30:34 UTC,"Hi Tone,"
1776888,2018-07-05 10:29:51 UTC,"Hi Tone,"
1776888,2018-07-05 08:46:32 UTC,"Hi Wei,"
1776888,2018-06-29 09:51:46 UTC,"Hi Wei,"
1776888,2018-06-29 01:14:58 UTC,"Hi Tone,"
1776888,2018-06-29 07:05:14 UTC,"Hi Wei,"
1776888,2018-06-28 05:25:36 UTC,could you please rerun the test with the latest Kolla and Kolla-ansible code?
1776888,2018-06-28 07:22:42 UTC,hi Tone Zhang:
1776888,2018-06-28 09:44:54 UTC,"Hi Wei,"
1776888,2018-06-29 08:57:37 UTC,"Hi Tone,"
1776888,2018-06-15 01:21:32 UTC,This is the log of the steps for ceph-disk to initialize osd. I have simplified some of the content. Please refer to:
1776888,2018-06-29 06:48:48 UTC,"Hi Wei,"
1776888,2018-06-28 11:30:25 UTC,"Hi Tone,"
1776890,2018-06-14 11:13:48 UTC,It seems I've resolved using theese commands:
1776909,2018-06-16 12:56:38 UTC,"I didn't thought about this kind of feature, I was just thinking of a visual enhancement but no ""functional"" feature.
But that would be absolutely awesome !"
1776909,2018-08-03 09:27:10 UTC,"@Julien, in kicad 5 there is a feature to highlight nets in schematic and pcbnew at the same time. Also there is a way to select all parts in pcbnew that is contained in the same hierachal sheet."
1776909,2018-06-15 21:18:39 UTC,I like a lot this approach.
1776910,2018-07-10 12:57:10 UTC,I do think that consistent behavior would be nice here. Thank you for the report.
1776912,2018-06-14 13:56:55 UTC,"Note that the Fedora package is installing this file into the deprecated path /usr/share/appdata, instead of using the one specified by AppStream since a while ago: /usr/share/metainfo."
1776912,2018-08-09 09:32:25 UTC,Thanks for the report Mario.
1776912,2018-08-14 22:51:41 UTC,"Hi Olivier, sorry for the late reply but I'm in the middle of an overseas relocation (UK > Spain) + holidays and I'm a bit off the grid these days..."
1776913,2019-05-28 20:31:51 UTC,"No objections from me (though as a general rule, this level of change I personally wouldn't go to much effort to backport if there were significant merge conflicts)."
1776913,2019-05-29 16:14:18 UTC,"Thanks, Galen.  That's good to know.  There was a small merge conflict for rel_3_1, but nothing too bad."
1776913,2019-05-28 19:08:53 UTC,"Thanks for this branch, Geoff, and for the testing, Lynn.  I especially appreciate that you included those docs updates as well."
1776913,2019-05-20 19:44:43 UTC,"Signed off
Lynn Floyd (<email address hidden>)"
1776913,2019-03-04 16:46:44 UTC,Menu change fixes are in this working branch: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gsams/LP1776913_Circ-ulation_fixes
1776913,2018-06-18 19:36:45 UTC,"Also ""Age Overdue Circs to Lost"" to ""Age Overdue Circulations to Lost""."
1776913,2019-05-28 17:18:42 UTC,"I have tested this code and consent to signing off on it with my name,Lynn Floyd (alynn26) and my email address, <email address hidden>"
1776916,2018-06-14 13:58:25 UTC,"StacktraceTop:
 _g_log_abort (breakpoint=1) at ../../../../glib/gmessages.c:583
 g_log_default_handler (log_domain=<optimized out>, log_level=<optimized out>, message=<optimized out>, unused_data=<optimized out>) at ../../../../glib/gmessages.c:3158
 default_log_handler (log_domain=log_domain@entry=0x7f355185c88e ""GLib"", log_level=log_level@entry=6, message=message@entry=0x7f34ac103520 ""Creating pipes for GWakeup: Too many open files\n"", data=data@entry=0x0) at ../src/main.c:310
 g_logv (log_domain=0x7f355185c88e ""GLib"", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7f34c56fe700) at ../../../../glib/gmessages.c:1370
 g_log (log_domain=log_domain@entry=0x7f355185c88e ""GLib"", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f35518bd520 ""Creating pipes for GWakeup: %s\n"") at ../../../../glib/gmessages.c:1432"
1776916,2018-06-15 02:39:31 UTC,"jibel, it sounds like you might have a file descriptor leak, which is something I don't ever recall seeing in gnome-shell before."
1776916,2018-06-15 02:41:31 UTC,Or just keep an eye on the list of descriptors in:
1776916,2018-08-14 04:17:40 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1776916,2018-08-14 07:18:01 UTC,"For reference, this crash was caused by the system monitor extension. I disabled it and monitored over several days and the number of file descriptors is stable at 42.
Then I reenabled the extension and the number of file descriptors instantaneously started to grow over time."
1776920,2018-06-20 19:44:05 UTC,"Great, thanks for the additional info!"
1776920,2018-06-21 12:00:35 UTC,I am not familiar with QEMU source code but I might have some cycles to look into it. Where would I look - https://github.com/qemu/qemu/blob/master/qemu-img.c? Or somewhere else? Any suggestions would be appreciated.
1776920,2018-06-21 17:11:27 UTC,My hunch is that we're handling zero regions incorrectly and we might be skipping data regions we ought to be copying.
1776920,2018-07-06 22:30:59 UTC,Bingo! Adding '-S 0' makes convert work. But it is not perfect as the end result is fully allocated image.
1776920,2019-08-09 22:32:52 UTC,"Hi, there isn't really a development branch; if '-S 0' didn't help alleviate the problem there may be other problems at hand, or the APFS implementation of SEEK_DATA is causing us even more problems in new versions."
1776920,2018-09-07 18:04:14 UTC,"I have done some experiments and find out that
the behavior of lseek with whence set to SEEK_DATA is different from the behavior of Linux's lseek."
1776920,2018-09-07 20:04:22 UTC,"On 09/07/2018 01:04 PM, Yan-Jie Wang wrote:

> I have done some experiments and find out that
> the behavior of lseek with whence set to SEEK_DATA is different from the behavior of Linux's lseek.
>
> If the supplied offset is in the middle of a data region, it returns the
> start of the next data region.  There may be many data regions in a big
> file even though it has no hole.
>
> return value of lseek with whence set to SEEK_DATA:
>
> |--(offset)--Data----|(return value)----Data----|
> |--(offset)--Data----|----Hole----|(return value)----Data----|
>
>
> ** Patch added: ""macOS-lseek.patch""
>     https://bugs.launchpad.net/qemu/+bug/1776920/+attachment/5186138/+files/macOS-lseek.patch
"
1776920,2019-07-23 19:28:46 UTC,"Hi,"
1776920,2018-06-20 18:33:17 UTC,I have done more tests based on your suggestion and I think it is the opposite. The problem happens is the source is APFS.
1776920,2018-07-25 19:53:57 UTC,"I marked https://bugs.launchpad.net/qemu/+bug/1738840 as a duplicate of this bug, even though that bug was older, this bug has a slightly more active thread."
1776920,2018-06-20 15:54:07 UTC,I haven't had the time to look just yet.
1776920,2018-06-14 21:58:17 UTC,The corrupt qcow2 image created by converting image.qemu in step 4.
1776920,2018-06-14 22:02:47 UTC,Also if I use the same image.qemu file and convert to vmdk format I get even smaller file which for sure is wrong as well:
1776920,2018-06-14 15:06:37 UTC,"I will provide all necessary info. Unfortunately the smallest image I can
provide is around 10M."
1776920,2018-06-14 15:29:02 UTC,">
> I will provide all necessary info. Unfortunately the smallest image I can
> provide is around 10M.
>
> What is M1/M2/M3 L1/L2/L3 file?
>
"
1776920,2018-06-14 19:22:33 UTC,"Are you converting to a destination on APFS? If yes, do you have the ability to easily reproduce this by converting to a non-APFS destination and seeing if that breaks too?"
1776920,2018-06-14 21:49:52 UTC,I believe I have distilled entire process to few repeatable steps that can be fully reproduced on my Mac. The binary source files - - boot.bin and lzloader.elf - were created on my Linux VM running in VirtualBox on same Mac but I do not think it matters as the execution completely happens on Mac.
1776920,2018-06-19 22:23:53 UTC,Have I provided all necessary data and other details?
1776920,2018-06-14 21:54:14 UTC,Source file 2
1776920,2018-06-14 21:55:35 UTC,Raw image created by dd in steps 1 and 2.
1776920,2018-06-14 21:56:59 UTC,Original qcow2 image converted from raw image in step 3.
1776920,2018-06-14 14:46:39 UTC,Can this be done with like a 1M example file that you could copy off in all stages.
1776920,2018-06-14 21:53:39 UTC,Source file 1
1776922,2018-06-20 19:17:25 UTC,"Hi,
As per discussion in https://review.openstack.org/#/c/565879/ can you help me understand how to proceed short term. It's not realistic for these neutron patches to wait much longer."
1776922,2018-06-20 19:54:53 UTC,"One option to proceed short term is just to let the neutron patch land and then follow up quickly with a patch in tricircle to address. This would cause breakage until the follow-up patch lands, but hopefully not much."
1776922,2018-06-25 03:10:17 UTC,hi Boden.
1776922,2018-06-25 20:08:48 UTC,Also please see http://lists.openstack.org/pipermail/openstack-dev/2018-June/131801.html
1776924,2018-07-17 14:31:09 UTC,What do you mean by doesn't appear to exist? This feature was added in Queens IIRC.
1776924,2018-07-17 14:42:24 UTC,"The feature was, a driver capability was not AFAICT."
1776926,2018-06-15 18:02:35 UTC,I can reproduce this.
1776928,2018-06-14 15:45:21 UTC,The problem is likely here:
1776928,2018-07-05 02:26:32 UTC,A similar problem was discussed in the openstack mailing list.
1776928,2018-07-05 17:40:35 UTC,"Takashi, thanks for linking that thread. To add the detail into this bug:"
1776928,2018-07-05 18:51:24 UTC,Looks like this is the code we have that does the redirect from /v2.1 => /v2.1/ [1]:
1776928,2018-07-06 02:40:22 UTC,"we can support the relative path also, I am not sure exact rational behind to redirect the relative to absolute path which is from history (not when we switched to route) [1]. May be Alex or John remember."
1776928,2018-07-06 02:44:47 UTC,That(https://review.openstack.org/#/c/580544/2) is just try the version API redirect things only not all other.
1776928,2020-04-03 21:31:44 UTC,"Based on the above comments, I don't think this is a problem in python-novaclient, but rather is related to the nova server redirect."
1776929,2019-01-07 14:56:13 UTC,"horizon just opens port 6080 provided by nova-novncproxy, so there is nothing to do in horizon.
Forwarding this to nova."
1776929,2019-01-23 22:07:53 UTC,"Hi,"
1776929,2019-01-24 16:39:38 UTC,"We're not running Ubuntu anywhere, we're running RHEL on both the host and the guest."
1776929,2019-01-31 23:58:26 UTC,The temporary workaround is: change the sequence of usb-tablet and usb-mouse. Make sure usb tablet appears behind the usb mouse in the configuration. You can compare the following with the one you attached. A complete patch will be available later.
1776931,2018-06-14 16:26:55 UTC,Cleaner details found at: https://help.heroku.com/WKJ027JH/rails-error-after-upgrading-to-postgres-10
1776933,2018-06-15 08:22:27 UTC,"Now I am keeping the same error message, but ""xdg-screensaver suspend"" does suspend the screen saver.  I don't know what possibly have caused the change, between the time I filed the report and now I installed several packages but they are normally unrelated to screensavers...  Anyhow you can close the bug (or tell me how to find out the packages I installed in between, so that I uninstall them and make another test)."
1776935,2019-02-17 11:40:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776937,2018-06-15 09:54:41 UTC,Seemingly relevant: https://askubuntu.com/questions/1036508/netbeans-8-1-wont-make-it-past-turning-on-modules-screen
1776937,2018-06-22 20:13:28 UTC,This is going to sound like a strange fix but I've had it work on 2 systems:
1776937,2018-06-22 20:16:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776937,2018-09-05 15:03:48 UTC,Downgrading to 3.8.1-10 works!
1776937,2019-02-08 11:08:45 UTC,"I've tried with libequinox-osgi-java_3.8.1-8_all.deb from https://packages.ubuntu.com/xenial/all/libequinox-osgi-java/download but it doesn't change the behaviour for me, i.e. it still doesn't load."
1776937,2019-02-08 11:10:02 UTC,this may be the upstream bug: https://netbeans.org/bugzilla/show_bug.cgi?id=258808
1776937,2019-06-27 19:37:46 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, according to this report, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. Thanks in advance."
1776938,2019-10-10 10:43:06 UTC,"Yes, we should."
1776939,2018-06-14 17:19:01 UTC,Adding context:
1776943,2018-06-14 17:41:36 UTC,"Regarding the ""No upgrade log present"" I think the script is broken;"
1776953,2019-05-17 09:44:08 UTC,Both those crashes appear to be in Inkscape::Text::Layout where this has been fixed. Closing as this is ultimately the same cause as bug 1776948.
1776954,2018-06-14 18:24:13 UTC,A branch with one of the larger ratios of commit description to actual patch length is available in the working repository at user/dbs/lp1776954_avoid_empty_string_tcn_source (http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/lp1776954_avoid_empty_string_tcn_source).
1776954,2020-09-24 17:19:52 UTC,"Seems a big shame this took so long to make it in.  Committed to master, rel_3_4, and rel_3_5 with a commit adding release notes about the potential need to update existing records with blank TCN Source."
1776956,2018-06-14 18:26:02 UTC,I received a crash report in the linked bucket after upgrading from Ubuntu 16.04 to Ubuntu 18.04.
1776957,2018-06-14 18:40:38 UTC,"I submitted an error about this crash which is in the above errors bucket but looking at the date for the crash it is from before I upgraded to 18.04, I only noticed and reported the crash after upgrading.  Here's the error I submitted:"
1776967,2018-06-14 20:06:32 UTC,Upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23202
1776967,2018-06-15 17:06:29 UTC,"Florian, thanks for the heads-up and for pursuing this. I read some of the links pointed out in that bug, and I see there is much to improve yet, and 4.17 might not have the best pkeys story for powerpc. Maybe we should just disable that test in the meantime."
1776967,2018-06-29 16:37:29 UTC,"It looks like the kernel fixes might not be ready quite yet, so I'm temporarily disabling CONFIG_PPC_MEM_KEYS in our ppc64el kernel."
1776967,2018-08-03 11:28:39 UTC,This bug was fixed in the package linux - 4.17.0-6.7
1776967,2019-02-14 12:12:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1776967,2019-02-14 17:03:35 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1776967,2020-01-29 13:54:12 UTC,"I think this patch solves the problem
https://sourceware.org/ml/libc-alpha/2020-01/msg00327.html
It's already in master at glibc-2.30.9000-492-g70ba28f7ab"
1776973,2018-12-28 15:15:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776976,2020-10-15 21:18:26 UTC,Subscribing field high based on recent deployments which this the CSR processes is making miss deliveries.
1776976,2021-01-11 18:29:44 UTC,"As a feature request, this is not eligible for Field SLA. I have recorded this RFE on the product feedback list for prioritization."
1776978,2019-09-03 00:57:33 UTC,Details here: https://gitlab.gnome.org/GNOME/evolution/issues/413
1776978,2018-11-07 21:43:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1776978,2018-11-15 08:53:29 UTC,So this bug was reported on 14th of June 2018 but it was _confirmed_ only on 7th of November 2018? With this speed we can expect the fix to be rolled out some time end of 2019?
1776978,2018-11-15 11:14:30 UTC,"I already switched back to Thunderbird.  TB has its issues, too. But I can use it as a productive tool. Unfortunately, evolution is not usable in a professional environment at this stage."
1776981,2018-06-28 16:16:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/578878"
1776981,2018-06-14 20:31:45 UTC,"Since project-config is branchless, and there are no branch restrictions on the ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa job definition itself, if we move this in-tree to nova and out of project-config we'll also need to backport it to the stable branches for nova to continue running that job on nova's stable branches. That's easy, but just FYI."
1776981,2018-10-08 21:45:46 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1776981,2018-10-02 22:16:10 UTC,"Reviewed:  https://review.openstack.org/581445
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4858514cef9f350c3d636c9a2b49a9bd2232fb9a
Submitter: Zuul
Branch:    stable/ocata"
1776981,2018-10-02 04:25:01 UTC,"Reviewed:  https://review.openstack.org/581444
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=039a61f95301b57b1a98bae7f7b5582bb6d8999f
Submitter: Zuul
Branch:    stable/pike"
1776981,2018-09-24 14:47:29 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1776981,2018-10-08 21:49:22 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1776981,2018-07-10 18:48:46 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/581445"
1776981,2018-07-10 18:46:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/581444"
1776981,2018-07-08 02:10:32 UTC,"Reviewed:  https://review.openstack.org/579862
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1e16b5f9f341cd0d086065e8b513937f7cd56f5a
Submitter: Zuul
Branch:    stable/queens"
1776981,2018-07-03 13:01:39 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/579862"
1776981,2018-07-30 16:07:52 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1776981,2018-06-29 09:08:49 UTC,"Reviewed:  https://review.openstack.org/578878
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=17b3bae64ca7aa4c1a6d296860cce6c0bfbb38a1
Submitter: Zuul
Branch:    master"
1776988,2018-06-14 21:07:54 UTC,"See related docs bug #1776991, for a section that maybe should be combined into this section."
1777000,2019-01-15 18:17:44 UTC,"The reason behind context in profiles is explained here:
https://docs.openstack.org/senlin/latest/contributor/profile.html#profile-properties"
1777006,2019-03-28 23:59:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777010,2019-12-24 08:58:33 UTC,"I have the same issue too, but cannot confirm it's related to the interface being down:"
1777010,2018-08-14 09:57:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777010,2018-10-30 11:08:34 UTC,"Just tried ""ip token set"" in 18.10 (Cosmic Cuttlefish), fails with the same error:
RTNETLINK answers: Invalid argument"
1777010,2018-10-30 18:24:59 UTC,"@Lisa: have you checked ""ip token list"" before you try the ""ip token set ..."" in Xenial/Stretch ?"
1777010,2018-11-07 09:55:30 UTC,"@Thomas: sorry, took me some days to find the time and check with freshly installed versions:"
1777010,2018-11-07 10:00:26 UTC,"Also checked removing of tokens:
~# ip token set :: dev eth0
~# ip token list
token :: dev eth0"
1777010,2019-06-27 11:47:55 UTC,"This bug is over a year old now, so I checked if there are news in upcoming Ubuntu 19.10 (Eoan Ermine):"
1777010,2019-11-15 20:27:46 UTC,"I found this bug report because I have the same issue, but I think it's because the interface is ""UP"". When I try the same ""set"" command on a ""DOWN"" interface, it's successful. My issue is figuring out how to run the set command during the boot process on the eth0 interface, before it comes up. Netplan is making this difficult."
1777010,2018-08-15 18:38:51 UTC,"I think, it is because the token is already set?"
1777010,2018-10-15 12:46:03 UTC,Daniel Borkmann's contact information seems to be available at http://borkmann.ch .
1777010,2018-08-22 09:14:20 UTC,Just for reference:
1777016,2019-01-17 04:24:50 UTC,Yes please!  This is really annoying.
1777017,2019-09-26 19:07:41 UTC,"Yes, adding security.nesting works with the lxd snap inside a lxd container running with the lxd snap. Closing as Fix Released in this case, thanks @stgraber for the pointer"
1777017,2018-06-15 04:31:13 UTC,An explanation for Seth's change:
1777017,2019-09-25 23:19:39 UTC,This at least fails more nicely with the lxd snap: https://pastebin.ubuntu.com/p/djwrN5nxjT/
1777017,2019-09-25 23:22:23 UTC,I should also specify - I can ssh into the lxc container and lxc fails in the same way as with `lxc shell ...`
1777017,2019-09-26 12:10:03 UTC,You're trying to run a nested container without having allowed it in the parent container's configuration.
1777020,2018-06-18 20:02:13 UTC,Is anything happening here yet?
1777020,2018-06-18 20:18:50 UTC,"Hello, I cannot find a package for Bible Analyzer. Is this in the archives somewhere by a different name?"
1777020,2018-06-18 20:38:07 UTC,"Hello,"
1777020,2018-07-09 11:14:44 UTC,Third issue is for a third-party package. Moving out of ubuntu-mate.
1777020,2018-06-22 07:17:28 UTC,Any follow up yet? Thanks!
1777020,2018-06-25 22:47:33 UTC,Do we have anything happening yet? I know the issue lies somewhere in Ubuntu 18.04.
1777020,2018-06-20 07:10:50 UTC,Not sure if you downloaded the deb file. Here is a small piece of code that shows how Hebrew displays in UM 17.10. I have attached the file.
1777020,2018-06-26 01:32:14 UTC,"Does this happen for you using other desktop environments or just with MATE? If so, you might want to mark this as affecting the general Ubuntu instead. Also, have you tried reaching out to the developers of this package?"
1777020,2018-07-09 09:34:31 UTC,"You can also download the sample code I attached earlier, execute it with python2 (in UM 18.04) and it will display left-to-right. If you ran it in UM 17:10 it displays right-to-left as it should."
1777020,2018-06-26 05:38:53 UTC,"Hello,"
1777020,2018-06-26 13:41:59 UTC,"No I mean other flavors of Ubuntu 18.04 (GNOME, Xubuntu, Kubuntu, etc.) - just trying to figure out whether this is specific to Ubuntu MATE, or whether it affects other *buntus"
1777020,2018-06-26 18:58:42 UTC,"So far the only non Mate I have tried is Peppermint OS8 which is based
from XFCE. Have you installed Bible Analyzer and looked at the Hebrew
display in UM 18,04 yet? Just curious."
1777020,2018-07-09 09:28:54 UTC,"So has there been any action here? The issue is there with any distro using Ubuntu 18.04 as its base. If you install Bible Analyzer from the link given earlier, install the WLCi Bible from the free modules then you can replicate the problem."
1777022,2018-06-15 08:16:42 UTC,Juju 2.3 provides specific bind and ingress addresses to solve this sort of issue.
1777023,2018-08-08 04:22:05 UTC,This issue was fixed in the openstack/puppet-tripleo 7.4.15 release.
1777023,2021-02-19 15:52:19 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1777023,2018-06-22 19:30:01 UTC,There's a fix for this problem here: https://review.openstack.org/#/c/575500/
1777023,2018-06-15 17:23:10 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/575500
Reason: we have gate problems again, please do not restore or recheck, I'll take care of this one when gate is back stable."
1777023,2018-07-18 01:26:54 UTC,"Reviewed:  https://review.openstack.org/575500
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=fee53d8b0d18d058939af3193e72d2be46453db0
Submitter: Zuul
Branch:    stable/pike"
1777025,2019-09-26 12:54:27 UTC,Please fill the bug template. Describe the steps that reproduces the problem and state the expected versus the actual behavior. Also please attach the nova logs if possible.
1777025,2019-11-26 04:17:38 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1777029,2018-08-02 16:03:06 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1777029,2018-07-11 16:26:20 UTC,"Note, this merged into Xenial via bug 1775771 by standard upstream stable merge process; it landed in Xenial commit 25ef67b828ea16b768ce2c549c2c92b9cad79ceb which is included starting at kernel 4.4.0-129.155."
1777029,2018-07-11 16:27:02 UTC,"marking fix released for Xenial, based on explanation above."
1777029,2018-07-24 09:32:30 UTC,"This bug was nominated against a series that is no longer supported, ie artful.  The bug task representing the artful nomination is being closed as Won't Fix."
1777029,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1777029,2019-02-14 16:54:44 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1777029,2018-08-07 14:02:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1777029,2018-08-23 21:59:21 UTC,This bug was fixed in the package linux - 3.13.0-157.207
1777047,2018-12-17 21:37:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625723"
1777047,2019-02-12 05:35:00 UTC,"Reviewed:  https://review.openstack.org/631582
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=566237c0a1c1fc8421415fd414ce845956b41d90
Submitter: Zuul
Branch:    master"
1777047,2019-03-16 06:28:45 UTC,"Reviewed:  https://review.openstack.org/631530
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=c3f07b441f6a077efc478fb50dd1bb8f04700066
Submitter: Zuul
Branch:    master"
1777047,2019-06-06 16:06:14 UTC,"Reviewed:  https://review.opendev.org/625718
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=c98a3254c84c00f05db63a74f26010ab80e699c6
Submitter: Zuul
Branch:    master"
1777047,2019-07-25 17:31:09 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672798"
1777047,2019-07-25 22:33:07 UTC,"Change abandoned by Nicolas Helgeson (<email address hidden>) on branch: master
Review: https://review.opendev.org/625714"
1777047,2019-07-25 22:32:55 UTC,"Change abandoned by Nicolas Helgeson (<email address hidden>) on branch: master
Review: https://review.opendev.org/625722"
1777047,2019-07-25 22:33:01 UTC,"Change abandoned by Nicolas Helgeson (<email address hidden>) on branch: master
Review: https://review.opendev.org/625715"
1777047,2018-12-17 21:33:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625722"
1777047,2019-07-26 01:33:36 UTC,"Reviewed:  https://review.opendev.org/670590
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=bae11b6dc0c776ef008fe09c5885e53392ded002
Submitter: Zuul
Branch:    master"
1777047,2019-07-26 14:31:21 UTC,"Change abandoned by Leo Henken (<email address hidden>) on branch: master
Review: https://review.opendev.org/672798
Reason: Abandoned in order to split into two commits. (lh236s)"
1777047,2019-07-25 22:32:50 UTC,"Change abandoned by Nicolas Helgeson (<email address hidden>) on branch: master
Review: https://review.opendev.org/625723"
1777047,2018-12-17 21:07:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625718"
1777047,2018-12-06 23:44:20 UTC,"Reviewed:  https://review.openstack.org/585536
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=a0710668324415497b3ae1b3968156333cc58644
Submitter: Zuul
Branch:    master"
1777047,2018-12-17 20:51:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625714"
1777047,2018-12-16 12:11:40 UTC,"Reviewed:  https://review.openstack.org/588393
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=11a2dd79190660a2a463440e610b82217afda04e
Submitter: Zuul
Branch:    master"
1777047,2018-10-04 00:44:02 UTC,"for user resource as immutable, dynamic cred or force_tenant_isolation tests will not work for LDAP right ? is this bug solving the issue for per-provisioned  cred only ?"
1777047,2018-08-12 11:03:59 UTC,Can we get more information from keystone side about when and what basis keystone does not allow to create the resources(user in this case) ?
1777047,2018-08-06 20:31:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589279"
1777047,2018-08-06 13:17:39 UTC,"Change abandoned by Anna Pankiewicz (<email address hidden>) on branch: master
Review: https://review.openstack.org/587846"
1777047,2018-08-02 21:12:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588395"
1777047,2018-08-02 21:05:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588393"
1777047,2018-08-01 15:18:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587846"
1777047,2018-07-27 15:48:07 UTC,"Change abandoned by Anna Pankiewicz (<email address hidden>) on branch: master
Review: https://review.openstack.org/586603"
1777047,2018-07-27 15:47:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586603"
1777047,2018-07-24 20:28:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585536"
1777047,2018-06-18 17:53:17 UTC,Trevor I agree with new conf value and the create and delete rest client ship check.
1777047,2018-06-15 15:59:37 UTC,"I think we should do three things.
1. add an option in tempest.conf called 'immutable_user_source=True/False' or something we all agree on.
2. check for immutable_user_source in the create_test_user method in the temepest base implementation and skip the test if it is True. https://github.com/openstack/tempest/blob/2d6bcaa7e55be9fd070bade12824709ac848f8fe/tempest/api/identity/base.py#L70
3. Add a similar skip if force_tenant_isolation is True and immutable_user_source is True in test.py skip_checks, kind of similar to what is done here https://github.com/openstack/tempest/blob/2d6bcaa7e55be9fd070bade12824709ac848f8fe/tempest/test.py#L283"
1777047,2018-12-17 21:00:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625715"
1777047,2019-08-29 01:23:03 UTC,I believe that all of these are done and this can be closed
1777047,2018-08-01 16:33:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587878"
1777058,2018-06-26 08:22:07 UTC,"As stated in the upstream report, the bug is really caused by /bin/sh missing in the supermin appliance. This was fixed upstream in https://github.com/libguestfs/libguestfs/commit/0cca7f9061455d29a7f893e715028cd3e75c19fd and downstream in Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889861"
1777058,2018-06-15 06:22:18 UTC,Upstream report: https://bugzilla.redhat.com/show_bug.cgi?id=1591617
1777058,2018-06-26 08:22:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777060,2019-02-26 13:40:33 UTC,Is this being worked on?
1777060,2019-02-26 14:03:51 UTC,"Yes, I was waiting for https://review.rdoproject.org/r/#/c/18735/ to get promoted, I'll respin today and get things listed in here correctly."
1777062,2019-04-10 01:36:47 UTC,Awesome.
1777062,2019-04-09 18:39:02 UTC,"Hey @vanvugt, just upgraded to 19.04 and indeed the problems seem to have gone. The mouse pairs every time, and persistently."
1777062,2019-04-08 01:46:08 UTC,"Please try Ubuntu 19.04 when you can, which when updated now has gnome-bluetooth 3.32.1 to solve a few pairing problems."
1777062,2019-04-01 06:12:47 UTC,The above merge requests are included in gnome-bluetooth 3.32.1 so please subscribe to bug 1822533.
1777062,2019-04-01 06:05:27 UTC,Sounds like this might be related to these:
1777062,2019-03-29 08:25:32 UTC,"When it does pair, bluetoothctl doesn't report ""ServicesResolved: no"" or ""Connected: no""."
1777062,2019-03-29 05:51:16 UTC,Can you still reproduce this bug with the latest updates? I can't seem to reproduce bug 1773897.
1777062,2019-04-10 01:38:15 UTC,The previous version (3.32.0) is here:
1777062,2018-06-15 07:32:29 UTC,"That might be premature. Bug 1773897 regressed in 17.10, not from 17.10."
1777062,2018-06-15 07:20:53 UTC,"It does look similar to that other bug, will dupe and we'll see if it improves when that's fixed."
1777062,2018-06-15 07:18:19 UTC,Most recently from 17.10.
1777062,2018-06-15 06:39:25 UTC,What Ubuntu version did you upgrade from?
1777062,2018-06-15 06:38:40 UTC,I wonder if there is any relation to bug 1773897 here...
1777062,2019-03-29 08:22:57 UTC,"Yes, I just removed the mouse under gnome-control-center, went into `bluetoothctl` and tried to pair it again:"
1777062,2018-07-02 19:55:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777062,2019-04-10 09:20:19 UTC,"Yup, looks like it. Downgrading made it unstable, upgrading stable again. I wonder how was `bluetoothctl` affected? Probably the GNOME menu still interacted with bluez even if the commands were invoked on `bluetoothctl`?"
1777062,2019-04-12 13:39:27 UTC,I've backported the is_trusted/pair pointer devices changes in a bionic SRU and used bug #1779289 for the update (the bug here seems like it's not only about that)
1777062,2019-06-04 08:22:45 UTC,"The bionic fix landed with that SRU
https://launchpad.net/ubuntu/+source/gnome-bluetooth/3.28.0-2ubuntu0.2
(another bug number was used for the SRU so closing manually)"
1777063,2018-08-23 19:23:06 UTC,This bug was fixed in the package linux - 4.4.0-134.160
1777068,2020-01-05 12:51:11 UTC,Fixed in Ubuntu 19.10 (mate-indicator-applet 1.22.1).
1777068,2019-06-01 11:58:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777068,2019-06-01 11:58:57 UTC,https://github.com/mate-desktop/mate-indicator-applet/commit/5a1775f80d4ae5d0909294aeddaa8a02f223ae15
1777070,2018-06-16 01:25:50 UTC,"Hello Xav, thanks for the bug report."
1777070,2018-06-18 05:39:04 UTC,"Thanks!  I won't claim to understand what that change did, but adding the two lines as requested does seem to resolve the issue.  I opened up Netflix and was able to watch, without the crash, and there wasn't any new entries in syslog."
1777070,2018-08-03 20:27:08 UTC,I think we're going to need more information on how this plugin got in there in the first place. Being able to map a library in a user-writable directory doesn't sound terribly safe...
1777070,2018-08-09 09:17:37 UTC,As far as I know firefox downloads and unpacks the widevine CDM in the user's profile directory when it is needed to watch DRM-protected videos. This is unlike chrome/chromium that install the widevine so system-wide.
1777070,2018-08-09 09:26:20 UTC,And I can confirm that the additions to firefox's apparmor profile suggested by Seth in comment #1 fix the crash of the CDM.
1777070,2018-10-15 15:50:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777070,2019-09-07 23:41:09 UTC,"Yes, this fixed it for me, too, but I couldn't get it to work, just on the explanation above.  Here's a little more detail.  Follow the instructions at:"
1777070,2020-10-25 12:15:32 UTC,"I got it working by adding the 2 lines at the end of the /etc/apparmor.d/usr.bin.firefox just before the closing brack ""}"". Without these lines, I had to use another workaround by disabling Apparmor completely on Firefox with a command like ""sudo aa-complain /usr/lib/firefox/firefox"" or using the official Firefox binary from Mozilla instead of the Ubuntu package."
1777070,2020-10-25 12:26:07 UTC,"If someone does not have a subscription on netflix.com, it is also possible to test Widevine without subscription on spotify.com."
1777070,2020-11-15 12:19:25 UTC,"On 10/25/20 5:15 AM, baptx wrote:

> I got it working by adding the 2 lines at the end of the
> /etc/apparmor.d/usr.bin.firefox just before the closing brack ""}"".
> Without these lines, I had to use another workaround by disabling
> Apparmor completely on Firefox with a command like ""sudo aa-complain
> /usr/lib/firefox/firefox"" or using the official Firefox binary from
> Mozilla instead of the Ubuntu package.
>
> I saw Daniel wrote ""this is not a great way of working (malware could
> write to that location and then load in code)"" but do you have an idea
> how to make it more secure?
>


I assume by the 2 lines you mean"
1777070,2020-11-15 13:58:27 UTC,"> The second rule allows firefox to load and run code from that location.
> But doesn't allow firefox to write to it. So if there is malware [...]
"
1777070,2018-08-09 19:47:06 UTC,"Arrgh... this is not a great way of working (malware could write to that location and then load in code), but as it is what we've got, I've added the rule to a forthcoming Firefox profile update."
1777086,2018-06-19 15:43:44 UTC,There are several parts of the API reference that could use updates. We haven't been tracking each piece individually. We can keep this open but this is likely a part of a larger effort to work through the entire API reference.
1777095,2018-06-19 20:29:13 UTC,"This is actually failing before it gets as far as Launchpad.  Apache's mod_proxy_http is throwing away the request, something like this (this is from a local development installation, but I verified this against Apache logs from our ""dogfood"" site):"
1777095,2018-06-15 09:23:09 UTC,"If I try to attach with chromium, I get a different error message:"
1777095,2018-06-15 09:55:10 UTC,"I don't see these failing requests in our access logs, which is odd."
1777095,2018-06-15 11:39:39 UTC,I've found the problem.
1777096,2018-08-18 00:16:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777096,2020-11-16 11:08:48 UTC,"This was probably a wayland issue, that looks fixed upstream."
1777096,2021-01-16 04:17:31 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1777108,2018-06-16 09:21:10 UTC,I've gone ahead and implemented this feature here:
1777109,2018-06-16 09:21:38 UTC,I've gone ahead and implemented this feature here:
1777121,2018-11-16 10:22:28 UTC,"Thanks for providing a use case with this bug report. We might think of a pre-remove hook, but this needs discussion (simply chaning current hook to run before services are stopped is of course not an option anymore)."
1777121,2018-11-26 16:58:21 UTC,"yes, a ""pre-remove"" hook seems a reasonable request, afaiu it would run before anything else in a remove and again only in the case of a full remove of the snap"
1777121,2020-06-26 14:54:15 UTC,"To add more context to the feature request, I have the following use-case:"
1777121,2018-11-29 14:53:48 UTC,"We discussed this a bit further and is a bit unclear what the expectations would be for this new hook, in general right now with the current hook we do a best effort to stopping services and then we call it."
1777121,2018-11-29 14:57:43 UTC,Basically we fear the convenience of the new hook would be misleading. Any remove related hook would need to be ready to deal with various forms of broken state possibly.
1777121,2018-11-29 13:00:02 UTC,PR: https://github.com/snapcore/snapd/pull/6232
1777123,2018-08-07 17:29:48 UTC,"Thanks for confirming that. Maybe there was a bad package push to the repo and you got unlucky during that window when you installed it, or something else happened in your environment."
1777123,2018-08-07 11:36:49 UTC,"Yep, you're right. I also can not reproduce the problem neither on the fresh installation, nor after upgrading packages on the existing ones. So probably this problem is already in the past, and new users shouldn't face with it (unless, they're using very old ceph, which is unlikely)."
1777123,2018-08-07 02:36:38 UTC,"Well, the tempest ceph job in the gate installs packages with apt-get (if ubuntu) [1][2], so I don't think there's an issue of pip or sources, etc. The packages are coming from the Ubuntu Cloud Archive repo."
1777123,2018-08-02 02:21:43 UTC,"We are using ceph luminous as a back-end. Moreover, I've catched similar problem on one computing node during unshelving procedure - nova fails to unshelve an instance with ""TypeError: name must be a string"" on the image restoration step. I'm currently on some kind of vacation, so I'll be able to provide log output only within several days.
I will try to dig into openstack-ansible-os_nova to get why so old rbd is get installed, as luminous ceph version had been specified in user_variables.yml (and ceph client is installed from luminous outside of virtualenv)."
1777123,2018-08-01 23:26:17 UTC,I wondered why this isn't a problem in the legacy-tempest-dsvm-full-devstack-plugin-ceph job in the gate and I also couldn't reproduce the issue with devstack installed with the devstack-plugin-ceph today (which installs Ceph Luminous 12.2.4).
1777123,2018-06-18 23:45:38 UTC,"So the disk_name has unicode in it? Looks like it should just be the instance uuid, so no unicode."
1777123,2018-07-31 23:30:47 UTC,"Correction to the above: six.text_type always represents unicode, so we would want to return the native text type depending on python version, not six.text_type."
1777123,2018-07-31 23:05:22 UTC,We had a similar bug around this awhile back [1].
1777123,2018-06-19 17:43:16 UTC,For example cinder in its cinder/volume/drivers/rbd.py resolves the problem like this:
1777123,2018-06-19 09:15:12 UTC,"As a disk_name I had ""4adc2422-b59d-4e84-b6fd-7f2e2f66d40a_disk"", but when I tried to log type(disk_name) I've received <type 'unicode'>"
1777123,2018-06-19 00:20:01 UTC,Looks like you might need this fix?
1777123,2018-08-01 02:09:42 UTC,"Okay, I've done more sleuthing and found where the unicode type is coming from. It's coming from the instance.uuid -- instance.uuid is of type unicode in python2. So when the imagebackend.py code for rbd does this: ""self.rbd_name = '%s_%s' % (instance.uuid, disk_name)"" [1], because the instance.uuid is of type unicode, self.rbd_name is also unicode when it's assigned."
1777123,2018-08-06 12:34:33 UTC,"It seems, that the problem lies not in the openstack-ansible, but rather in ceph repos."
1777125,2018-07-28 02:44:56 UTC,This bug may have been fixed. In the last couple of months I've rebooted at least half a dozen times and it hasn't occurred.
1777125,2020-05-20 09:30:28 UTC,I can confirm that this issue hasn't happened in over 1 year. Please close?
1777131,2018-06-15 13:03:30 UTC,"Hi Alexander,"
1777131,2018-06-15 13:11:35 UTC,"Andres,"
1777131,2018-06-15 13:19:13 UTC,"Alexander,"
1777131,2018-06-15 13:43:08 UTC,"Commissioning with Bionic indeed works fine, gets RAM correctly:
https://pastebin.canonical.com/p/G7B7zVMkFF/"
1777131,2019-04-29 20:32:05 UTC,"Upstream bug : https://ezix.org/project/ticket/662
Upstream commit : https://ezix.org/src/pkg/lshw/commit/640615983fbf976e66931164a9ae1bd64da9668b"
1777131,2019-04-29 23:43:00 UTC,"I uploaded the package in the Xenial upload queue for SRU verification team approval. Once approved, the package will start building in xenial-proposed, entering the testing phase of the SRU."
1777131,2019-05-06 14:27:21 UTC,"Hello Alexander, or anyone else affected,"
1777131,2019-05-09 22:26:59 UTC,[VERIFICATION XENIAL]
1777131,2019-05-13 10:45:40 UTC,This bug was fixed in the package lshw - 02.17-1.1ubuntu3.6
1777131,2019-05-13 10:45:46 UTC,"The verification of the Stable Release Update for lshw has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1777131,2018-06-15 13:19:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777135,2018-06-21 16:14:14 UTC,"Change abandoned by Helen Walsh (<email address hidden>) on branch: master
Review: https://review.openstack.org/575739
Reason: No longer relevant based on feedback from https://review.openstack.org/#/c/557448 on updating metadata."
1777135,2018-06-15 13:44:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575739"
1777138,2018-12-12 12:23:30 UTC,"Thank you for your bug report. That's a known issue upstream, see https://bugzilla.gnome.org/show_bug.cgi?id=758312"
1777138,2018-12-12 12:24:22 UTC,The bug reference for the n-m issue is https://bugzilla.gnome.org/show_bug.cgi?id=746041
1777145,2018-06-15 14:30:05 UTC,This change was made by a bot.
1777145,2018-06-18 11:03:21 UTC,"Ok, I don't have much knowledge about what is going on, but after some research I found that the following line in the dmesg could be related to the issue:"
1777145,2018-06-18 19:32:40 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1777145,2018-06-18 20:54:33 UTC,"I tried the new kernel as you said, the touchpad works perfectly there. Thank you!"
1777145,2018-10-18 09:23:20 UTC,"Hello,"
1777146,2018-06-15 14:30:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/575756"
1777146,2018-09-11 12:48:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/601590"
1777146,2018-06-15 17:26:47 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/575756
Reason: we have gate problems again, please do not restore or recheck, I'll take care of this one when gate is back stable."
1777146,2018-06-15 14:34:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/575758"
1777146,2019-09-10 08:36:18 UTC,Removed kolla-ansible from affected projects and created https://bugs.launchpad.net/kolla-ansible/+bug/1843397 to cover the issue on our side.
1777146,2019-03-04 20:22:41 UTC,Actually where this isn't relevant to the current release maybe the proper course of action is to mark as invalid?
1777146,2019-03-04 20:21:01 UTC,"It's still an issue, but we couldn't figure out how we wanted to deal with docker upgrades needing a restart. However as this was filed awhile ago and we have not merged a fix but nobody has been pressing for a solution I would rate this as low priority."
1777146,2019-02-26 13:41:58 UTC,Is this still an issue?
1777146,2018-06-15 17:23:15 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/575758
Reason: we have gate problems again, please do not restore or recheck, I'll take care of this one when gate is back stable."
1777146,2018-11-01 12:11:24 UTC,"Change abandoned by Brent Eagles (<email address hidden>) on branch: master
Review: https://review.openstack.org/575756
Reason: There is some debate about how to detect when it *would* be necessary to stop containers (i.e. an incompatible upgrade). Abandoning for now, can be revived later."
1777146,2018-09-24 14:26:30 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.6 release.
1777146,2018-09-17 10:55:26 UTC,"Reviewed:  https://review.openstack.org/601590
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=78358da44f37cd455421677d5b123668bc2efa33
Submitter: Zuul
Branch:    stable/queens"
1777146,2018-11-01 12:12:26 UTC,"Change abandoned by Brent Eagles (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/575758
Reason: There was some discussion about how to handle situations where a restart would be required on a docker upgrade. Abandoning to be revived later on if necessary/prioritized."
1777146,2018-06-19 19:38:35 UTC,"I'm dropping the severity to ""high"". My initial concern was that the keepalived sidecars were not cleaning up their VIPs properly on shutdown since we were seeing ""that kind of thing"" in a bug report. Looking more closely at the logs, etc, this doesn't seem likely what was happening and even if it were the bug would lie in keepalived or how we run it."
1777148,2018-06-15 14:31:12 UTC,Something is weird:
1777148,2018-06-18 07:16:03 UTC,"There are also many mirrors which the prober detected as lagging:
https://paste.ubuntu.com/p/Mg3hhjRZ99/
Looking at the logs (for instance https://launchpadlibrarian.net/374733940/mirror.squ.edu.om-archive-probe-logfile.txt), it does get 4xx responses.
However, the mirrors are not automatically maked Unofficial, which I believe is what shoud happen."
1777148,2018-06-18 08:48:05 UTC,"There are also many mirrors which the prober detected as lagging:
https://paste.ubuntu.com/p/Mg3hhjRZ99/
Looking at the logs (for instance https://launchpadlibrarian.net/374733940/mirror.squ.edu.om-archive-probe-logfile.txt), it does get 4xx responses.
However, the mirrors are not automatically marked Unofficial, which I believe is what should happen."
1777148,2018-06-18 08:56:54 UTC,"As I understand it, the prober never sets the mirror status (Pending review, Unofficial, Official), and this is intentional: that's a field that's set by mirror admins, and we shouldn't generally have fields that are set both by admins and by automatic processes.  For example, that could result in an admin setting the status to Official and then that work being lost because of a temporary network flap."
1777149,2018-06-15 16:27:12 UTC,"It's the same or at least similar on VMs: ""could not find any partitions""
Proceeding to the d-i shell:"
1777150,2019-07-14 18:52:42 UTC,"Actually squashfuse_ll is being installed, it is renamed in this patch:
https://salsa.debian.org/sgclark-guest/squashfuse/blob/master/debian/patches/install_squashfuse_lowlevel.patch"
1777150,2019-09-15 09:41:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777150,2019-09-15 09:49:28 UTC,"I don't see the binary being installed.
Only the library.
The binary is needed for https://github.com/facebookincubator/xar."
1777153,2018-06-22 17:33:24 UTC,Upstream fix is in progress: https://review.openstack.org/575804
1777153,2018-06-15 20:51:05 UTC,Migrating to StoryBoard: https://storyboard.openstack.org/#!/story/2002583
1777153,2021-02-02 17:26:22 UTC,"The upstream fix merged in stein, and was released in version 3.17.0"
1777157,2018-06-18 23:31:41 UTC,I opened bug 1777540 to track the IndexError issue.
1777157,2019-09-23 10:57:34 UTC,Looks like this bug is a duplicate of #1790204
1777157,2018-12-05 12:04:52 UTC,"In my case cold migration works if allow_resize_to_same host was set to False and fails if this option was set to True.
In case when allow_resize_to_same host=False resize always moves the instance to another host."
1777157,2018-12-05 11:37:54 UTC,"The option allow_migrate_to_same_host was deprecated since Liberty:
 https://bugs.launchpad.net/openstack-manuals/+bug/1557032"
1777157,2018-11-09 10:03:16 UTC,"sorry for confusion, the allow_migrate_to_same_host is set to True (this is why UnableToMigrateToSelf is raised at all)."
1777157,2018-11-08 21:50:46 UTC,Correction - the resize to the same host is disabled:
1777157,2018-11-08 13:10:54 UTC,"we've reproduced it on Queens, it seems this happens when resize to same host is enabled in Nova and scheduler actually attempts to resize to same host during migration"
1777157,2018-06-26 07:27:18 UTC,"> (nova-compute)[nova@compute5 /]$ pip freeze | grep nova
> nova==13.0.0.0rc4.dev10675
"
1777157,2018-06-25 15:27:10 UTC,cannot reproduce it - will reopen and will recollect logs with debug if it happens again
1777157,2018-06-22 10:57:48 UTC,"instances can live migrate from host to host without problem,"
1777157,2018-06-22 10:38:51 UTC,My setup:
1777157,2018-06-19 17:34:23 UTC,Here is the functional test I used for the trials: https://review.openstack.org/#/c/576593
1777157,2018-06-19 17:27:22 UTC,I've managed to push the code towards the same code path that the logs shows. I used 17.0.2 queens as that matched the line numbers in my log with the numbers in the log attached. I used 2.7 and 3.5 nova functional env for the reproduction.
1777157,2018-06-19 12:12:54 UTC,"i have 3 computes, and can migrate ephemeral disk instances, also live migration works for all."
1777157,2018-08-28 06:10:46 UTC,"I meet this problem too. and the problem is same to you @Balazs Gibizer (balazs-gibizer) .
 My nova version is queens 17.0.5
pip freeze | grep nova
nova==17.0.5"
1777157,2018-06-19 12:01:10 UTC,"@Matt: This could not be a resize as the flavor_id does not change https://github.com/openstack/nova/blob/530c24596a74a6115f2e944176c46e4f3d199811/nova/compute/manager.py#L4075
But I have no idea how can we ask the Nova API to migrate an instance to itself."
1777157,2018-06-18 23:21:19 UTC,"Hmm, do you only have a single compute host? It appears that you're trying to resize the instance to the same host it's already on:"
1777165,2019-05-18 20:30:46 UTC,Tested in a fresh bionic install and it works.
1777165,2019-05-23 08:47:39 UTC,"The verification of the Stable Release Update for metaphlan2 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1777165,2019-05-23 08:47:33 UTC,This bug was fixed in the package metaphlan2 - 2.7.5-1ubuntu1
1777165,2019-05-20 19:59:59 UTC,"Hi, Robie."
1777165,2019-05-15 13:21:02 UTC,"Hello Tony, or anyone else affected,"
1777165,2019-04-24 19:34:14 UTC,Fixed in 2.7.6-1 in Cosmic:
1777165,2019-04-24 19:34:26 UTC,Attached is a patch which backport a debian patch to fix this error in bionic.
1777165,2018-07-25 22:56:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777166,2018-06-15 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777166,2018-06-15 17:09:17 UTC,A package dependency issue should not require log-files.
1777169,2018-06-15 20:46:48 UTC,We have not enabled a setting like that in MAAS. Currently we think its important to see all devices on the network even if they come and go. This can be helpful in determining if a device was ever connected to your network. It is possible to clear all discoveries.
1777169,2019-09-19 11:58:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1777170,2018-07-04 18:17:46 UTC,"A way to solve this bug would maybe be to add the relevant configuration to those overridden settings in https://github.com/openstack/tacker/blob/master/devstack/settings, for example by specifying OVS_BRIDGE_MAPPINGS+=$MGMT_PHYS_NET:$BR_MGMT and so on."
1777174,2018-06-20 08:45:13 UTC,"Sorry scrap that, forgot to do apt-get update."
1777174,2018-06-20 03:51:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777174,2018-06-20 03:54:10 UTC,Also affected - gem2.0 is totally stuffed with this.  It seems like if your system didn't already have a recent version of psych installed before the upgrade (maybe) then you can't use it...
1777174,2018-06-20 04:03:28 UTC,I have a workaround - I downgraded to the previous version:
1777174,2018-06-20 04:04:06 UTC,"I meant to say I temporarily rolled back, installed psych, then upgraded back to the secure version again."
1777174,2018-06-20 04:09:01 UTC,"If it's of use to anyone else, I had a broken build due to bundler choking on this error - I edited my /usr/local/bin/bundle and added:"
1777174,2018-06-20 04:27:24 UTC,Here's a version of andy edwards' Dockerfile which applies my workaround:
1777174,2018-06-20 08:38:47 UTC,"We getting the same issues, but the work around isn't working.  when we try to do"
1777174,2018-06-20 21:40:25 UTC,"Ouch - If you wanted to get clever, you could add your own puppet package
provider that extends the default gem one to use that altered path - it's
probably not as hard as it sounds."
1777174,2018-06-20 09:47:03 UTC,"Hi Philip,"
1777174,2018-06-20 15:03:06 UTC,"Hey Nick,"
1777177,2019-12-21 02:45:33 UTC,"Reviewed:  https://review.opendev.org/678382
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=7c33d8ebb67b0d85964a03660d6f34bbee8b7e58
Submitter: Zuul
Branch:    master"
1777177,2019-12-03 07:54:25 UTC,"Reviewed:  https://review.opendev.org/669706
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=a6a3edb80ead7fa1c4587d40461bd68e3f501fe7
Submitter: Zuul
Branch:    master"
1777177,2019-08-24 17:51:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678382"
1777177,2019-08-24 18:20:55 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.opendev.org/678384"
1777177,2019-08-24 18:04:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678384"
1777177,2019-08-24 18:28:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678386"
1777178,2018-06-17 07:06:13 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1777178,2019-09-05 14:47:12 UTC,This bug is also in 18.04 bionic.
1777179,2018-06-20 11:57:50 UTC,"On 15/06/18 19:30, Willem Hobers wrote:

> Public bug reported:
>
> “Favourites”
> English spelling; I believe I have the default language setting and seem to have American  spelling: Favorites.
> What’s the real default?


iirc I wrote this - the American spelling is wrong

>
> “Highlight any application from the menu, right click and Add to Favourites”
> Only works for applications that are not already in favourites. So “any” is strictly speaking not quite right.
> Also add that we expect the user to do this in Whiskermenu?


Maybe word like, but I would not worry about us expecting people to do
this in Whiskermenu:"
1777181,2018-06-18 14:00:20 UTC,We've had requests from libraries about this as well.
1777181,2018-06-18 15:13:22 UTC,"In the xul client, there were two options that had a display that was distinct from other checkin modifiers: backdating and amnesty mode. I like the idea of changing the color of the title bar for both of those to make it a little more alert worthy from the other checkin modifiers."
1777181,2019-11-06 19:56:46 UTC,"This was one of the first things staff noticed after trying out the web client.  ""Why isn't it as noticeable when backdating is enabled as the old client?"""
1777181,2019-11-13 15:36:05 UTC,"Added a screenshot of what it might look like to change the ""Check In"" banner for backdating.  How does that look?"
1777181,2019-11-13 19:53:03 UTC,"Branch at
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1777181_backdate_visibility"
1777181,2020-02-18 16:26:43 UTC,Yep! Like this:
1777181,2020-02-21 15:58:44 UTC,"Pushed to master.  Thanks, Josh and Dawn!"
1777181,2018-06-18 14:41:45 UTC,"If you select any of the checkin modifiers, the indication to the user that they are selected also appear in this same pinkish bar with red lettering.  My first inclination is to make the red lettering bold and possibly larger, but what if we also change the color of the light blue ""Checkin Items"" title bar when one of these options is selected to indicate to the user that one of the non-standard options has been selected?"
1777182,2018-06-15 18:56:55 UTC,"I was able to solve this by installing `xinput-calibrator` and then running it (called Calibrate Touchscreen from the menu, or xinput_calibrator from the terminal)."
1777182,2020-09-04 03:07:00 UTC,Confirm the same behaviour on my laptop. I can provide video later if it is necessary.
1777182,2020-09-05 03:39:51 UTC,Small addition for those who read my last comment: you need to run `x11-touchscreen-calibrator` only once. After reboot touchscreen will work correctly.
1777184,2019-04-09 14:51:46 UTC,"I updated the search to sort first by library, then by statistical category, then sort entires within the categories."
1777184,2019-04-09 20:29:29 UTC,"Ha, I totally didn't see Suzanne's addition when I added my comment.  I'll relinquish self-assignment of this bug for now."
1777184,2019-04-09 20:40:53 UTC,"Incidentally, the patch does work as written (and so does a more modest form I was trying with sorting just the entries, since we have client-side sorting now of the stat cats themselves thanks to Jane)."
1777184,2019-04-09 20:49:55 UTC,"Suzanne, I pushed a working branch with a tweak to your changes.  Could you test and add your Sign-Off to the commit?  Thanks!"
1777184,2019-04-16 15:06:45 UTC,"I tested Jason's branch and it seems to organize the stat cats by org. unit name alphabetically, and within the stat cat entries. I've pushed a signoff branch here:"
1777184,2019-04-17 14:36:16 UTC,Cesar I am fine with putting in Jason's change. As long as it sorts I don't care how it's coded :)
1777184,2019-05-09 20:56:39 UTC,"Added tags and targets. The branch has two signoffs. Cesar, I'd say you can go ahead and push it to master."
1777184,2019-05-23 21:55:24 UTC,"I've pushed this to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Suzanne, Jason, and Cesar!"
1777184,2019-04-09 19:23:29 UTC,"Is alphabetical sorting enough or does some consideration of the library owning the entry need to be made as well (and should those be exposed like they are for the actual stat cats)?  It could arguably be a bad configuration to have identically labeled but differently owned entries show up for a given stat cat, but there's nothing stopping it.  Is there a legitimate use case for that?"
1777184,2018-06-15 19:21:25 UTC,I'm guessing we need to add an order_by to the pcrud.search call in the service.get_statcats function within Open-ILS/web/js/ui/default/staff/cat/volcopy/app.js.
1777185,2018-06-17 04:58:14 UTC,1. The crontab expression for postoffice is incorrect. How often should it run?
1777185,2018-12-06 11:29:25 UTC,"If it happens again this month (Dec) I'll let you know, otherwise, I'll close this."
1777186,2018-06-15 19:00:05 UTC,This change was made by a bot.
1777192,2018-06-18 15:51:24 UTC,Latest version of Ming mentions PHP7 compat. Can someone look into packaging this please?
1777192,2018-06-15 21:39:17 UTC,"There was no PHP7 compatible ming when 16.04 released. Adding it seems like a fair amount of work, when it is available via PECL."
1777192,2018-06-18 15:49:49 UTC,It isn't available via PECL anymore. Tell you to go to libming site to get from Github. Still have a product that needs SWF for near future.
1777192,2018-06-18 16:02:12 UTC,"user@host:~$ sudo pecl search ming
Retrieving data...0%
no packages found that match pattern ""ming"", for channel pecl.php.net.
user@host:~$ sudo pear search ming
Retrieving data...0%
no packages found that match pattern ""ming"", for channel pear.php.net."
1777192,2018-06-18 16:48:00 UTC,"If you need it only for the ""near future"", maybe just spin up a Trusty container."
1777192,2018-06-18 16:51:08 UTC,"FWIW, src:ming has been removed from Debian altogether."
1777192,2018-06-19 03:31:57 UTC,"Understood, but source is still available and does not ""compile by default"" without causing segfault when script runs."
1777192,2018-06-19 16:17:17 UTC,"Well, that makes it even *less* likely that we would try and package it -- a segfaulting library from upstream is not something we want in Ubuntu, right? Have you asked the upstream folks if this is a bug in their code? In any case, as php7.0-ming would be in universe, this needs someone who is willing to do the legwork in the community."
1777202,2018-11-02 21:01:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777202,2019-09-02 10:08:23 UTC,"It is true, not everything is there yet.  Google makes it really hard to package them all.  Right now sdkmanager is blocked by Kotlin, which is coming along, but still needs work.  Contributions welcome!"
1777207,2019-07-10 21:55:57 UTC,We have now been able to re-create issue #2 another way.  If you scan multiple barcodes into check in quite quickly only the first one or two show up and the same error message shows up in the console.
1777207,2019-07-10 16:59:52 UTC,"Just to note, I get the same errors in checkout as I see in check in if I click on a column header to sort.  The items do check out even though they don't appear on the screen and the number on the Items Out tab increases with each check out."
1777207,2019-07-09 22:07:22 UTC,"> 1. If you click on any of the column labels and then check items in once
> you reach the total visible rows new check ins no longer appear on your
> visible list.  If you switch to having more rows visible your check ins
> are in the list.  I can consistently replicate this.  (On a 3.1.7 server
> without the patch the most recent check in always appears in the visible
> rows.)
"
1777207,2019-07-09 19:51:10 UTC,Further testing (of the original patch) on our customized 3.1.7 server and on a 3.1.7 server using the Concerto data set without any of our customizations has revealed a couple issues when columns are sorted in Check In.
1777207,2019-07-09 18:55:04 UTC,"Thanks for testing, Jennifer!"
1777207,2019-07-04 18:39:40 UTC,Tested Galen's patch on our testing server running 3.1.7 with one of our libraries.
1777207,2019-07-03 22:05:19 UTC,"The working repo branch collab/gmcharlt/lp1777207_circ_grid_performance contains a patch that significantly improves performance of the checkin and checkout grids by teaching egGrid how to simply prepend the new row representing the circulation action, rather than doing a full grid refresh."
1777207,2018-11-27 00:30:23 UTC,You can also view your previously checked in items by changing the number of rows that display and then switching it back to 5 rows before checking in again.
1777207,2018-11-16 18:33:15 UTC,"As a workaround in the meantime, we had one library mention they limit their rows to 5 on Check In. I tested this and I did indeed see an increase in speed. (Not a speedy as we'd like, but better!)"
1777207,2018-10-10 00:55:02 UTC,Our libraries also use the check in list as Terran describes.
1777207,2018-10-07 14:30:04 UTC,"In my experience, it's primarily used as a reference of what has been checked in - to see where  you are in the stack, to make sure that every item has been scanned, as a secondary method of special statuses in case an alert gets overlooked, etc."
1777207,2018-10-06 12:28:06 UTC,"I have a question, mainly for people who work circulation:"
1777207,2019-03-21 13:20:28 UTC,"I noticed that bug 1697954 comment 11 mentions a fix for extra grid refreshes in the items out screen.  Maybe the fix for that is applicable to this bug?
https://bugs.launchpad.net/evergreen/+bug/1697954/comments/11"
1777207,2018-06-18 18:13:12 UTC,"One of our larger libraries is reporting a lot of problems with this since they are checking in so many items at a time, particularly when scanning their pulled holds."
1777207,2019-07-03 22:00:01 UTC,"Josh: thanks for the pointer. However, in the case of the checkin grid, the problem is not that data are being repeatedly re-fetched; instead, as more entries get added to the grid, it's been taking progressively longer for AngularJS to render the grid rows from scratch."
1777207,2019-03-19 14:49:38 UTC,CW MARS has signed a contract with Equinox to investigate (and hopefully fix) this bug.
1777207,2019-07-15 14:34:27 UTC,"I've looked over the code, and it looks good.  Just a few questions/comments."
1777207,2019-07-12 15:15:33 UTC,"I've pushed two more patches to the branch. The first resolves the bug with fast scans or sorting causing the duplicate entry error, while the second teaches prepend() how to reset sort columns (which is needed to avoid having to do full collect()'s all the time if a sort order is in effect). From the description of the second patch:"
1777207,2019-07-17 17:55:18 UTC,"I had a chance to test this for CW MARS. We are seeing highly improved check in times, especially when more items are on the screen."
1777207,2019-07-18 15:30:49 UTC,I've pushed a patch to the collab branch that addresses Dan's questions.  In short:
1777207,2019-07-18 15:31:35 UTC,"Also, the collab branch is now meant for folks who have been testing over the past few days; I'll shortly prepare a new branch with a squash that should be the one used for the formal signoff."
1777207,2019-07-18 15:41:34 UTC,I've pushed a branch meant for consideration as a pullrequest:  user/gmcharlt/lp1777207_grid_prepend_and_circ_grid_performance / https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp1777207_grid_prepend_and_circ_grid_performance
1777207,2019-07-18 16:41:09 UTC,"Looks good, works well for me.  Thanks for making the extra changes, Galen!  Pushed to master through rel_3_1."
1777207,2019-07-11 22:11:11 UTC,"I wonder if we shouldn't simply remove sorting from checkin and checkout?  That may be heretical to say, and please correct me if it's very important, but because those interfaces are essentially a chronological log of actions taken, preserving that order (even at all costs) seems reasonable to me."
1777207,2019-07-12 19:13:00 UTC,I've now tested all four patches together on our testing server using a barcode scanner for entering items in check in and check out.  The issues I encounter after the first two patches are resolved and I'm not encountering any further issues.
1777207,2019-07-11 23:34:58 UTC,"I think sort is very useful and should be retained, especially on checkin.  Lots of libraries prefer to keep a single checkin tab open all day with an ever-growing list of checkins, because it helps them manage the items that came in at that workstation; sorting makes a lengthy list manageable.  Ascending sort on checkin date is the easiest way to review checkins in the order they occurred.  You might want to sort by shelving location for reshelving, by user to help with patron inquiries, or by routing destination to manage transits."
1777213,2018-08-24 22:09:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777215,2018-06-16 07:31:04 UTC,It seems that i have a TMP2.0 Device:
1777216,2020-03-28 20:11:38 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1777218,2018-06-23 10:27:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777219,2018-10-21 23:20:07 UTC,This still affects me and makes the use of Synapse difficult.
1777219,2018-11-28 16:05:46 UTC,"Just installed LinuxMint 19 from 18.3 (Ubuntu 18.04)
Synapse no longer searches as I type, finding file after a few keystrokes. I must hit enter and then it gives a long list of possible files and not the one I have been referencing frequently.
The Zeitgeist files seem to be updated after each use. .local/share/zeitgeist/
I tried using the zeitgeist folder from 18.3 and no change.
from terminal:
[INFO 09:57:38.651659] [synapse-main:267] Starting up...
[INFO 09:57:38.720062] [synapse-main:209] Binding activation to <Control>space
[INFO 09:57:38.749016] [view-base:251] Screen is composited.
[INFO 09:57:38.749956] [controller:56] Using gtk-im-context-simple input method.
[WARN 09:57:38.857352] [desktop-file-service:352] Desktop session type is not recognized, assuming GNOME.
[WARN 09:57:38.880366] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.881198] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.881784] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.882394] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.883154] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.887166] [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/vim.desktop
[WARN 09:57:38.897006] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.900342] [desktop-file-service:200] Unable to create AppInfo for /usr/share/applications/mint-xfce4-lock.desktop
[WARN 09:57:38.906212] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.906504] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.906779] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.907056] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.907327] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.907597] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.907872] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.909333] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.909869] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.910431] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.910996] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.911529] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.911982] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.912410] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.912795] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.913215] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.913847] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.914384] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.915065] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.915597] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.916066] [desktop-file-service:76] X-Cinnamon is not understood
[WARN 09:57:38.916625] [desktop-file-service:76] X-Cinnamon is not ..."
1777219,2018-11-29 01:44:18 UTC,@benchrest Thanks for your comment! It seems Synapse is not actively developed anymore :( . I will miss it dearly!
1777219,2019-04-18 00:44:57 UTC,"Have the same issues as you...
Yep, synapse was really great! Such such a pity!"
1777220,2018-06-16 08:41:57 UTC,"Error:
E: /var/cache/apt/archives/plasma-widget-amule_2.4.0~git20151120.0023527bc2-1ubuntu1_amd64.deb: intentando sobreescribir `/usr/share/icons/hicolor/scalable/mimetypes/application-x-emulecollection.svg', que está también en el paquete amule 2.4.0~git20151120.0023527bc2-1ubuntu1"
1777221,2018-06-16 09:21:58 UTC,I've gone ahead and implemented this feature here:
1777223,2020-08-19 18:29:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777224,2018-06-26 18:05:15 UTC,Peut-être tester de mettre la TOC dans la navbar ?
1777224,2019-02-11 07:16:32 UTC,"Le problème de la TOC pourrait provenir du plugin note.
En attendant de le virer Rixo propose sur la liste d'essayer l'ajout de ceci"
1777224,2019-02-11 15:18:37 UTC,"Plop,
Juste comme ça, Le plugin note ne posait pas de soucis avant la mise en place de la nouvelle charte graphique/theme. (Il marche d'ailleurs sans soucis sur d'autres dokuwiki)."
1777224,2019-02-11 21:13:53 UTC,"Le plugin note est obsolète. On a donc décidé de le remplacer .
Pour le moment on part sur le plugin Wrap qui marche pas mal (le choix n'est pas figé)
https://www.dokuwiki.org/plugin:wrap"
1777224,2019-02-12 09:15:36 UTC,"Obsolete?
pourtant sa dernière mise à jour date de:
 Last updated on   2019-01-19
https://www.dokuwiki.org/plugin:note
alors que wrap:
Last updated on    2018-04-22"
1777232,2020-11-11 15:03:53 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1777232,2021-01-11 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1777235,2018-08-12 18:21:42 UTC,"I have a patch for that, it was designed to run NVMe for MacOS guests and implements at least the bare minimum of the spec. I'll try to polish it up and upstream it as soon as I have time."
1777235,2020-11-24 16:42:11 UTC,Has this ever been sent?
1777235,2020-06-04 14:55:00 UTC,"Hi Lorenz,
Can you send your patch to the mailing list adding your Signed-off-by tag?
See:
https://wiki.qemu.org/Contribute/SubmitAPatch#Submitting_your_Patches"
1777235,2021-01-24 04:17:28 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1777236,2020-11-11 15:06:30 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1777236,2021-01-11 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1777238,2018-06-16 20:13:43 UTC,apport information
1777238,2018-06-16 20:13:45 UTC,apport information
1777238,2018-06-16 20:13:46 UTC,apport information
1777238,2018-06-16 20:13:47 UTC,apport information
1777238,2018-06-16 20:13:48 UTC,apport information
1777238,2018-06-16 13:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777238,2018-06-16 20:13:55 UTC,apport information
1777238,2018-09-02 13:05:11 UTC,"Running the system monitor as suggested by Jon had no effect.
Doing a cold boot reduced the problem tempoarily."
1777238,2018-08-26 18:09:12 UTC,"Something to try, run system monitor. If I have it open I don't have any issues playing videos. Strange but true."
1777238,2018-08-12 23:48:00 UTC,Hi Zoltan.  This computer (HP Envy 17 Leap Motion SE) is a fresh install of 18.04.  I upgraded my Dell Inspiron from 16.04 and don't have the issue.  Very weird.
1777238,2018-08-12 23:03:27 UTC,"the situation is much better after unchecking v-sync, but still not perfect."
1777238,2018-08-12 22:45:30 UTC,"Thanks Boris! The video was taken in 2012, but I experience these kind of problems since the upgrade from 16.04 to 18.04.
I had 10.04, 12.04 and 16.04 before without these issues."
1777238,2018-08-12 21:38:00 UTC,"After posting the above, I found https://www.youtube.com/watch?v=cIQZv6MXzno."
1777238,2018-08-12 21:24:50 UTC,"The lag is everywhere for me, not just in video.  Screen scrolling also has this stutter."
1777238,2018-06-30 11:10:03 UTC,"since the last gstreamer update the situation is much worse than before, so I removed the ""kernel-fixed-upstream"" tag."
1777238,2018-08-30 01:42:52 UTC,"After a couple of weeks without issues, thanks to changing the v-sync in compris, it is back and getting progressively worse.
Will try running system monitor and see if this helps."
1777238,2018-06-19 19:58:34 UTC,"I decided I add the tag: 'kernel-fixed-upstream', because I couldn't reproduce it when I tested it 2nd and 3rd time for minutes."
1777238,2018-06-19 12:59:57 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1777238,2018-06-16 20:14:02 UTC,apport information
1777238,2018-06-16 20:14:01 UTC,apport information
1777238,2018-06-16 20:14:00 UTC,apport information
1777238,2018-06-16 20:13:58 UTC,apport information
1777238,2018-06-16 20:13:57 UTC,apport information
1777238,2018-06-16 20:13:50 UTC,apport information
1777238,2018-06-19 19:43:13 UTC,"Yes, this issue started after I upgraded my ubuntu from 16.04 to 18.04. I didn't experience it with 16.04.
I also have a newly installed 18.04 on a very same notebook and that one is also affected."
1777238,2018-06-16 20:13:53 UTC,apport information
1777238,2018-06-16 20:13:51 UTC,apport information
1777238,2018-09-09 12:45:04 UTC,"@Boris
You should determine which package/application affected and report it as a new bug.
https://help.ubuntu.com/community/ReportingBugs"
1777238,2018-06-16 20:13:52 UTC,apport information
1777238,2018-10-07 20:48:43 UTC,Another thing to note. The stutter (every 5 seconds a freeze frame) is consistently reproduce-able on Gnome on Ubuntu 18.04 but when you switch to Unity there is no stutter the video at all. So suspect that Gnome could also be playing a part in this issue.
1777238,2019-04-10 03:58:24 UTC,"Same here.
Ubuntu 18.04.2
Youtube / VLC / SMPLAYer affected.
Lagged every 5 sec"
1777238,2019-11-07 04:52:27 UTC,"Hi,"
1777238,2019-11-07 09:19:07 UTC,"I can't see a option to edit posts, but the gpu I am using is an Intel from a j4105 CPU"
1777238,2020-11-21 08:15:29 UTC,"In my case, the culprit was have running indicator-multiload on gnome. Thanks to this post I tried to quit it and the shuttering went away; it goes back by starting it up again. Do you guys happen to have it installed too? If so and stopping the program fixes it, I'd reconsider to change the package for this bug report"
1777238,2021-02-10 15:28:49 UTC,"The issue is still here, I'm on 20.04 and kernel 5.10
The issue goes away after a reboot, then comes back randomly. It could come back on the same day, or take a month, it's impossible to detect a pattern."
1777238,2018-09-08 00:22:01 UTC,"This is getting really bad.  I can't even type without the screen freezing momentarily!
What information would be most useful to diagnose the problem?  How do I collect it?  How do I add it to the ticket?"
1777239,2018-09-01 03:02:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777240,2018-06-18 14:14:15 UTC,"Thank you, Daniel, for your helpful comments."
1777240,2018-06-16 14:01:49 UTC,"Please always provide references to previous discussions about the very same topic in other venues, to not make people spend time having the same discussions again and again and again."
1777240,2018-06-17 07:12:32 UTC,"Thank you, Andre, for connecting the dots. Sorry, I did not provide the reference; I thought it is not relevant as it was dismissed to be a GNOME issue (https://gitlab.gnome.org/GNOME/gnome-panel/issues/2) and the developer could just confirm that it was working in MATE (https://github.com/lafrech/qbirthday/issues/14) which I stated in the description.
Thanks for working on this!"
1777240,2018-06-18 02:14:35 UTC,I've never seen this bug occur with any other app. I would guess it's most likely a bug in https://github.com/lafrech/qbirthday/issues/13 and not a gnome-shell bug.
1777245,2018-06-16 14:30:07 UTC,This change was made by a bot.
1777245,2018-06-19 13:07:46 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1777245,2018-06-19 17:38:42 UTC,"Yes, the problem started after an upgrade. From what I can see in the logs it seems that first the machine was upgraded from Ubuntu 17.10 to 18.04, apparently without problem.
Then a few days later, the working kernel Ubuntu 4.13.0-43.48-generic 4.13.16 was replaced by 4.15.0-23.25-generic 4.15.18 which fails."
1777245,2018-06-27 21:04:07 UTC,@jsalisbury: I had the machine tested with this kernel:
1777248,2018-06-16 14:30:11 UTC,This change was made by a bot.
1777255,2018-09-06 18:33:01 UTC,yeeloong /var/log/wicd # wicd -version
1777255,2018-09-06 18:27:21 UTC,"The wicd log:
2018/09/07 01:22:57 :: Flushing the routing table...
Error for wireless request ""Set Bit Rate"" (8B20) :
    SET failed on device %s ; No such device.
2018/09/07 01:22:58 :: Putting interface up...
2018/09/07 01:23:00 :: Generating psk...
2018/09/07 01:23:00 :: Attempting to authenticate...
Failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory
2018/09/07 01:23:01 :: connect result is failed
2018/09/07 01:23:01 :: exiting connection thread
2018/09/07 01:23:01 :: Sending connection attempt result bad_pass
dhcpcd not running
Failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory
dhcpcd not running
Failed to connect to non-global ctrl_ifname: eth0 error: No such file or directory"
1777255,2018-09-06 18:29:13 UTC,"yeeloong /var/log/wicd # ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.106  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::223:8bff:fef2:b812  prefixlen 64  scopeid 0x20<link>
        inet6 fec0::346e:a907:77c0:623e  prefixlen 64  scopeid 0x40<site>
        ether 00:23:8b:f2:b8:12  txqueuelen 1000  (Ethernet)
        RX packets 31942  bytes 28502956 (27.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 17418  bytes 2709195 (2.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0"
1777255,2018-09-06 18:31:12 UTC,"yeeloong /var/log/wicd # wpa_cli -i wlan0 status
Failed to connect to non-global ctrl_ifname: wlan0  error: No such file or directory"
1777258,2018-06-23 22:38:56 UTC,apport information
1777258,2018-06-23 22:40:01 UTC,"After BT stopped working last time, I did a fresh install a week ago. BT worked fine.  5 mins ago it stopped working again."
1777258,2018-06-23 22:39:22 UTC,apport information
1777258,2018-06-23 22:39:19 UTC,apport information
1777258,2018-06-18 21:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777258,2018-06-23 22:39:14 UTC,apport information
1777258,2018-06-23 22:39:13 UTC,apport information
1777258,2018-06-19 13:23:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1777258,2018-06-23 22:39:11 UTC,apport information
1777258,2018-06-23 22:54:05 UTC,Linux darkle90210 4.18.0-041800rc1-generic #201806162031 SMP Sun Jun 17 00:34:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
1777258,2018-06-23 22:39:06 UTC,apport information
1777258,2018-06-23 22:39:04 UTC,apport information
1777258,2018-06-23 22:39:02 UTC,apport information
1777258,2018-06-23 22:39:00 UTC,apport information
1777258,2018-06-23 22:38:58 UTC,apport information
1777258,2018-06-23 22:39:09 UTC,apport information
1777258,2018-06-23 22:39:07 UTC,apport information
1777258,2018-06-23 22:56:57 UTC,apport information
1777258,2018-06-27 03:25:17 UTC,Anything specific I should be looking for?  When I dmesg its a pretty long list.
1777258,2018-06-27 03:26:41 UTC,"[    0.000000] Linux version 4.18.0-041800rc1-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17 00:34:22 UTC 2018
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[    0.000000] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[    0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000027498fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000027499000-0x0000000027499fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000002749a000-0x000000002749afff] reserved
[    0.000000] BIOS-e820: [mem 0x000000002749b000-0x0000000028827fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000028828000-0x0000000029127fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000029128000-0x000000002ed3dfff] usable
[    0.000000] BIOS-e820: [mem 0x000000002ed3e000-0x000000002ef3dfff] type 20
[    0.000000] BIOS-e820: [mem 0x000000002ef3e000-0x000000002f72dfff] reserved
[    0.000000] BIOS-e820: [mem 0x000000002f72e000-0x000000002ff7dfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000002ff7e000-0x000000002fffdfff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000002fffe000-0x000000002fffefff] usable
[    0.000000] BIOS-e820: [mem 0x000000002ffff000-0x000000003cffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000004c1ffffff] usable
[    0.000000] NX (Execute Disable) protection: acti..."
1777258,2018-06-27 04:16:27 UTC,I guess you warm booted instead of cold booted your system?
1777258,2018-06-27 04:37:24 UTC,"[    0.000000] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
(gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds
registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[    0.000000] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[    0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960
bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff]
reserved
[    0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff]
reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000027498fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000027499000-0x0000000027499fff] ACPI
NVS
[    0.000000] BIOS-e820: [mem 0x000000002749a000-0x000000002749afff]
reserved
[    0.000000] BIOS-e820: [mem 0x000000002749b000-0x0000000028827fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000028828000-0x0000000029127fff]
reserved
[    0.000000] BIOS-e820: [mem 0x0000000029128000-0x000000002ed3dfff] usable
[    0.000000] BIOS-e820: [mem 0x000000002ed3e000-0x000000002ef3dfff] type
20
[    0.000000] BIOS-e820: [mem 0x000000002ef3e000-0x000000002f72dfff]
reserved
[    0.000000] BIOS-e820: [mem 0x000000002f72e000-0x000000002ff7dfff] ACPI
NVS
[    0.000000] BIOS-e820: [mem 0x000000002ff7e000-0x000000002fffdfff] ACPI
data
[    0.000000] BIOS-e820: [mem 0x000000002fffe000-0x000000002fffefff] usable
[    0.000000] BIOS-e820: [mem 0x000000002ffff000-0x000000003cffffff]
reserved
[    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff]
reserved
[    0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff]
reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff]
reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff]
reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff]
reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff]
reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff]
reserved
[    0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff]
reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000004c1ffffff] usable
[    0.000000] NX (Execute Disable) protection: acti..."
1777258,2018-06-27 04:40:12 UTC,"I can see BT stuff when cold booting.  Unable to test right now, but the
ability to see devices was not available before, so I think it probably
works.  It must be a resume and warm boot issue?"
1777258,2018-06-27 05:40:26 UTC,The bt works on a cold boot.
1777258,2019-04-02 07:24:34 UTC,The BT issue is pretty similar to LP: #1757218.
1777258,2018-06-27 02:56:00 UTC,Can you attach dmesg when BT failed to work?
1777264,2018-08-09 09:13:59 UTC,Try the following command in a terminal:
1777267,2018-06-18 17:38:19 UTC,I was unable to replicate this. I used the same Concerto account and first tried copies belonging to BR1. I thought it might be a permissions issue and also followed the same steps for some BR3 copies without any trouble.
1777267,2018-08-31 14:55:14 UTC,Is this bug still occurring?
1777279,2018-06-16 20:19:24 UTC,version.log
1777279,2018-06-16 20:20:27 UTC,lspci-vnvn.log
1777279,2018-06-16 20:30:08 UTC,This change was made by a bot.
1777279,2018-06-17 10:13:20 UTC,I remotely connected with ssh to my frozen desktop and generated dmesg2.log. You can see in this file errors related to GPU.
1777279,2018-09-05 19:33:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777279,2018-10-07 09:32:47 UTC,"I  got a workaround for suspend working on Ubuntu 18.04 with a NVIDIA GeForce GTX 1050 Mobile and proprietary nvidia drivers 390. I installed pm-suspend via ```sudo apt-get install pm-utils```.  Then, I switch from Gnome Shell to the terminal via Ctrl+Alt+f6. After  the login, I do ```sudo pm-suspend```. After waking up from standby, I  change back to Gnome Shell via Ctrl+Alt+f1. Done!"
1777284,2018-07-26 23:02:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777285,2019-06-24 20:58:09 UTC,I reopened https://bugs.documentfoundation.org/show_bug.cgi?id=117731 since it seems to be an issue in the central Libreoffice code.
1777285,2019-06-26 22:38:20 UTC,"The command (OString cmd) is executed in background through a pipe no matter what.  The difference is that in Mac and Windows, the foreground process waits (blocked) while in Linux and Unix, the foreground process continues to the exit."
1777285,2019-06-24 20:47:53 UTC,"The file /usr/bin/libreoffice is a soft link to soffice, a Bourne shell script. Inside the script, the soffice.bin executable is invoked."
1777285,2019-06-23 17:40:13 UTC,Done today: https://ask.libreoffice.org/en/question/198713/executed-from-linux-command-line-convert-to-is-unexpectedly-asynchronous/
1777285,2019-06-23 17:26:06 UTC,"Moved to bugs.launchpad.net and confirmed:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1777285"
1777285,2019-01-11 18:17:20 UTC,Opened on Launchpad as #1777285 against libreoffice (Ubuntu).
1777285,2019-01-11 15:21:58 UTC,"Dear Bug Submitter,"
1777285,2018-08-09 09:10:07 UTC,"I haven't found any mention in the documentation of the asynchronous nature of the --convert-to option, but it looks like it is asynchronous indeed. You should probably ask for confirmation at https://ask.libreoffice.org/. If this is confirmed then requesting an option to wait until the conversion completes would have to be done in the upstream bug tracker: https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice."
1777285,2019-06-26 22:17:39 UTC,"Yes, I have tried this with the latest download.  This is an off-the-shelf Xubuntu 18.04.latest LTS desktop that I use primarily for Libreoffice, browsing, and Python development.  I tend to stay with Ubuntu's packages including Libreoffice."
1777285,2019-06-26 22:32:28 UTC,"Seriously, I am not trying to make work for anyone.  We are all busy and I do not want to be a pest."
1777285,2020-01-20 17:31:39 UTC,"(In reply to Richard Elkins from comment #9)

> The source code indicates that soffice.bin is the one starting a background
> process that does not finish before soffice.bin exits.
>
> See:
> https://github.com/LibreOffice/core/blob/master/shell/source/unix/exec/
> shellexec.cxx
> Go to line 218:
>
>     OString cmd =
> #ifdef LINUX
>         // avoid blocking (call it in background)
>         ""( "" + aBuffer.makeStringAndClear() + "" ) &"";
> #else
>         aBuffer.makeStringAndClear();
> #endif
>     FILE *pLaunch = popen(cmd.getStr(), ""w"");
>     if ( pLaunch != nullptr )
>     {
>         if ( 0 == pclose( pLaunch ) )
>             return;
>
> It would be interesting to understand why execution is in background *only*
> for Linux. In my opinion, it is undesirable for command line execution in
> any O/S.
>
> Other opinions?  It is possible for me to be perfectly content with the
> artificial `sleep N` in my shell script.
"
1777285,2020-01-20 23:40:07 UTC,@Xisco Faulí - Are you asking me to download and build LibreOffice for that one source change?  I wouldn't know where to begin.  I am a developer but up to my eyeballs in Astrophysics projects at the moment.
1777285,2020-01-21 03:33:18 UTC,[Automated Action] NeedInfo-To-Unconfirmed
1777285,2020-05-09 13:14:36 UTC,"(In reply to Richard Elkins from comment #0)

> Steps to Reproduce:
> Linux batch script, starting with an existing text file called ""myfile.txt"":
>
> 	libreoffice --headless --convert-to odt:writer8 myfile.txt
> 	RC=$?
> 	if [ $RC -ne 0 ]; then
> 		echo '*** libreoffice conversion failed for myfile.txt'
> 		exit 86
> 	fi
>         cp myfile.odt somewhere-else.odt
>
> Actual Results:
> cp: cannot stat 'myfile.odt': No such file or directory
>
> Expected Results:
> Copy completes as normal because myfile.odt is available.
"
1777285,2020-06-17 14:34:43 UTC,"(In reply to Buovjaga from comment #17)

> (In reply to Richard Elkins from comment #0)
> > Steps to Reproduce:
> > Linux batch script, starting with an existing text file called ""myfile.txt"":
> >
> > 	libreoffice --headless --convert-to odt:writer8 myfile.txt
> > 	RC=$?
> > 	if [ $RC -ne 0 ]; then
> > 		echo '*** libreoffice conversion failed for myfile.txt'
> > 		exit 86
> > 	fi
> >         cp myfile.odt somewhere-else.odt
> >
> > Actual Results:
> > cp: cannot stat 'myfile.odt': No such file or directory
> >
> > Expected Results:
> > Copy completes as normal because myfile.odt is available.
>
> I get the expected result. I guess you should bite the bullet, clone the
> source and try modifying it.
>
> https://wiki.documentfoundation.org/Development/BuildingOnLinux
> https://wiki.documentfoundation.org/Development/Linux_Build_Dependencies
>
> Arch Linux 64-bit
> Version: 7.0.0.0.alpha1+
> Build ID: c73418d8d1258ea0a8c77c07672fd182e2b28b26
> CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5;
> Locale: fi-FI (fi_FI.UTF-8); UI: en-US
> Calc: threaded
> Built on 9 May 2020
"
1777285,2019-06-24 20:55:51 UTC,The source code indicates that soffice.bin is the one starting a background process that does not finish before soffice.bin exits.
1777285,2020-06-19 21:07:38 UTC,@xiscofauli
1777285,2020-12-15 03:45:55 UTC,"Dear Richard Elkins,"
1777285,2020-12-15 16:03:32 UTC,"Since there seems to be no interest nor resource to fix the source code where I indicated in comment 9, just forget it.  My work-around works fine."
1777285,2018-06-16 22:26:10 UTC,Not urgent.  I am not stuck.  The sleep for a few seconds is a consistently successful work-around.
1777285,2018-06-16 18:06:02 UTC,You should report this behavior against Ubuntu 18.04 on https://bugs.launchpad.net/
1777285,2018-06-16 14:30:54 UTC,"You might be tempted to think that Ubuntu or my hardware is running a little slow.  If you insert a `sync; sync; sync` right after the libreoffice step which flushes buffers, that does not help consistently.  Something got spawned by or because of libreoffice.  It finishes long after libreoffice exits.  Bad idea, in my opinion."
1777285,2018-06-16 14:10:49 UTC,"`libreoffice --version`:
LibreOffice 6.0.3.2 00m0(Build:2)"
1777285,2018-06-16 14:07:41 UTC,"Like you, when I ran LibreOffice under Xubuntu 16.04 and 17.10, there was no timing issue.  This only has appeared for me in 18.04."
1777285,2018-06-16 11:54:31 UTC,Not reproducible for me under Ubuntu 16.04 x86-64 with LibreOffice 6.0.4 from Ubuntu PPA. The script completes as expected.
1777285,2018-05-21 20:25:17 UTC,"Description:
Command-line: libreoffice --headless --convert-to odt:writer8 myfile.txt
The returned status code ($?) is zero.  So far, so good.
But, when I try to use the ODT file (E.g. copy it), it doesn't exist yet.
Yes, I tried `sync; sync; sync` but it did not help.
If I add a `sleep 1` immediately after checking the status code, then this seems to allow enough time for some libreoffice subprocess (?) to finish."
1777285,2020-10-12 14:53:18 UTC,"Since there clearly no interest or resources to fix this, I am withdrawing this bug report."
1777285,2019-06-26 08:43:24 UTC,"Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version."
1777294,2019-06-12 02:09:38 UTC,It is still not working in version 0.92.4
1777294,2020-03-28 21:31:00 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1777300,2018-06-24 11:47:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577644"
1777300,2020-01-30 10:38:08 UTC,Master (train too) says precisely that ovsdpdk images are not buildable for centos:
1777300,2018-10-18 06:38:11 UTC,fanguiju still working on this ?
1777301,2021-01-11 04:17:19 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1777301,2020-11-11 15:07:44 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1777308,2019-07-31 14:52:04 UTC,"pytz exposes the IANA timezone database, including the quirks like the Etc zones having always had the wrong signs. The Etc zones probably only exist as historical artifacts these days. You can use pytz.FixedOffset if you need a less surprising fixed offset timezone."
1777308,2019-06-30 20:14:01 UTC,"According to this paragraph: https://github.com/stub42/pytz/blob/master/tz/etcetera#L37 in the `Etc` zones file, PyTZ seeks consistency with the POSIX Standard over General Usage. Input strings such as `GMT+1` are therefore evaluated assuming that `+` represents a TZ to the west of GMT, while `-` represents east."
1777315,2020-07-11 19:08:31 UTC,Here's a qtest reproducer:
1777315,2019-05-06 16:26:20 UTC,"FYI: we've hit this as will with syzkaller testing; this is still reproducible as-is with latest qemu (commit a6ae238), and the latest Linux kernel (5.1-rc7)."
1777315,2018-06-18 18:10:24 UTC,"A repro for the bug is setup at https://github.com/asurati/1777315, although the rfc-patch that was sent yesterday is pending testing. Unless qemu-devel advises otherwise, I am available to test and present it as a bugfix, by tomorrow."
1777315,2018-06-18 06:17:18 UTC,"Oh no, this is a misunderstanding."
1777315,2018-06-18 05:52:48 UTC,Are you going to provide a patch for this to the mailing list? (since you've assigned the bug to yourself)
1777318,2018-08-06 01:51:39 UTC,"This wouldn't be a side-effect of bug 1782152, would it?"
1777318,2018-08-03 11:07:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777318,2018-06-18 02:20:57 UTC,"Please report the issue to the GDM developers here:
https://gitlab.gnome.org/GNOME/gdm/issues"
1777318,2018-06-19 21:16:31 UTC,Done.
1777323,2019-12-08 12:56:01 UTC,There has not been a commit addressing this. Still wanted to share this is peristing on macOS 10.14.6 and 2.3.0-alpha-pre (build master r7018).
1777323,2019-04-13 11:20:41 UTC,"retested macOS 10.13.6
mixxx 2.3.0-alpha-pre (build master r6770)"
1777323,2019-12-09 17:46:03 UTC,"I have noticed this sometimes on Linux, but I cannot reproduce it by switching away from the Mixxx window and back. I have not figured out how to reproduce it reliably."
1777323,2020-03-04 12:38:11 UTC,Can no longer reproduce on macOS 10.15.3 mixxx 2.3.0-alpha-pre (build master r7148)
1777323,2019-12-09 17:42:13 UTC,"The Xone K2 mapping uses [Playlist], SelectNextTrack/SelectPrevTrack"
1777326,2018-07-26 11:11:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777328,2020-04-30 22:06:38 UTC,"okay, open for MacOS.
Fixed for Linux in https://github.com/mixxxdj/mixxx/pull/2690"
1777328,2018-09-02 21:16:53 UTC,"Also on macOS, 10.13.6, and I've seen the same thing both in the official release and building directly from source. The default size is pretty small too."
1777328,2020-04-30 20:25:44 UTC,"Sorry, not fixed on macOS. Still leaving full-screen when switching skin.
macOS 10.15.4
mixxx 2.3.0-alpha-pre (build master r7331)"
1777328,2020-04-30 06:25:28 UTC,"This was fixed here
https://github.com/mixxxdj/mixxx/pull/2690"
1777328,2020-03-04 15:15:04 UTC,"I can confirm this.
Unfortunately no one had found time to look into it yet."
1777328,2020-03-04 13:07:15 UTC,This problem is unchanged. Is anybody willing to look into this? Seems like various OS are affected. Functionality is not decreased but it's somewhat annoying to have windows jump around and switch size by themselves.
1777328,2019-03-05 22:33:28 UTC,"another observation (ubuntu studio, X11):
window with custom size > maximize = maximized window
window maximized > F11 = fullscreen
fullscreen > F11 = window with custom size"
1777328,2019-03-05 16:37:41 UTC,btw: skins are also shown at minimal size after (re)loading skins in windowed mode although Mixxx fills the screen.
1777328,2019-03-02 00:10:25 UTC,Is this issue on the radar for 2.2.1 indeed? Is there a PR already? Is there a dev willing to work on this?
1777328,2018-12-25 22:53:22 UTC,Ups .. Thank you.
1777328,2018-12-25 14:06:06 UTC,I don't think this is the same issue as #1773587
1777328,2018-10-22 19:09:21 UTC,I said this in an earlier comment:
1777328,2018-10-21 21:06:18 UTC,Windows 10: Mixxx 2.2 built from sources this weekend. Things works as expected as in:
1777328,2018-10-21 20:56:10 UTC,"2.2 + XWayland + Full-screen view: Ok
You can watch the repainting while switching skins, but eventually the new skin fills the whole window/screen. I don't need to toggle full-screen view again."
1777328,2018-09-12 20:26:27 UTC,"When I build the current 2.3.0 alpha-pre it handles this properly. Not sure if that's because it's been fixed or just a quirk of my system, it seems to have a few."
1777328,2018-09-13 12:13:07 UTC,"on Linux it fails with 2.3 as well but differently:
Mixxx stays fullscreen, but the new skin is loaded with window mode size.
Remaining space (at the right & at the bottom stil shows the framebuffer from the previous skin. Resizing, or toggling fullscreen twice paints the skin correctly."
1777328,2020-04-30 22:17:49 UTC,"yup, original report was filed against macOS so let's leave this bug open."
1777329,2018-06-30 16:43:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777332,2018-06-17 19:15:39 UTC,Looks like it was removed because it failed to build with newer glm. Please see https://launchpad.net/ubuntu/+source/gli/+publishinghistory and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888933 for more details.
1777333,2020-03-23 02:36:23 UTC,"Upgraded a while ago to 18.04.4 LTS and FF works now
running on 4.19.90-v7+"
1777333,2018-06-17 16:03:45 UTC,Good news on the chromium. After 3min it started in the background. But no luck on the FF.
1777335,2020-03-14 10:17:29 UTC,"Hello everybody.
I've seen something similar on Ubuntu 18.04 and Debian, but more so when I scan folders with over 20,000 files."
1777338,2018-07-21 05:23:07 UTC,"OK, I tried that one and it still exhibited the issue. I'm going to
try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next."
1777338,2018-07-09 04:30:35 UTC,"OK, I've tested this kernel, and it works just fine under Xen, from
what I can tell. The system comes up just fine:"
1777338,2018-07-17 18:24:15 UTC,"I built the next test kernel, up to the following commit:
fc8704280f2ada9f61f08a2d5adc0dab169cc207"
1777338,2018-07-21 04:08:07 UTC,Thanks!
1777338,2018-09-10 17:53:06 UTC,This bug was fixed in the package linux - 4.15.0-34.37
1777338,2018-08-29 01:20:57 UTC,"I don't seem to have access to change the tag, but I can confirm that 4.15.0-34-generic from -proposed solves the problem. So the tag should be verification-done-bionic."
1777338,2018-07-05 15:32:44 UTC,Here are the md5sum hashes of the files needed to install the test kernel:
1777338,2018-08-28 17:01:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1777338,2018-08-14 01:15:50 UTC,"OK, I have tested the provided kernel and it works for me under Xen.
Thank you for fixing the bug! I look forward to seeing this in the
real releases."
1777338,2018-08-13 15:48:15 UTC,The hashes are:
1777338,2018-08-11 15:43:23 UTC,"Thanks for preparing this kernel; I am downloading it now. What are
the expected hashes of the files, so that I can verify the insecure
downloads?"
1777338,2018-08-07 15:49:55 UTC,"I built a test kernel with commit 74899d92e66663dc7671a8017b3146dcd4735f3b.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777338"
1777338,2018-08-05 21:33:44 UTC,"OK, I grabbed commit 74899d92e66663dc7671a8017b3146dcd4735f3b ""x86/xen: Add call of speculative_store_bypass_ht_init() to PV paths"" from <email address hidden>:torvalds/linux.git and cherry-picked it on top of the tag Ubuntu-4.15.0-29.31, and built the kernel, and now it boots fine as dom0! I think that that patch fixes this bug."
1777338,2018-08-05 19:49:27 UTC,"I've been advised by Juergen Gross that not having ""x86/xen: Add call of speculative_store_bypass_ht_init() to PV paths"" from the mainline kernel might contribute to this problem. I am trying to pull that in now."
1777338,2018-07-28 05:45:40 UTC,"I'm not finding any kernel packages in bionic-proposed; maybe they were
released already?"
1777338,2018-07-24 16:04:32 UTC,Thanks for finishing up the bisect!
1777338,2018-07-22 20:51:37 UTC,"OK, I have finished the bisect."
1777338,2018-07-21 16:42:31 UTC,That one works. On to 5856293c78e552c012835e667d66775bba20b4f7.
1777338,2018-08-14 20:14:47 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-August/094683.html"
1777338,2018-07-03 01:30:16 UTC,"Hello,"
1777338,2018-06-27 17:34:39 UTC,I started a kernel bisect between v4.15.0-22 and v4.15.0-23. The kernel bisect will require testing of about 7-10 test kernels.
1777338,2018-06-23 19:37:12 UTC,"I updated my BIOS and tested the -24 kernel, as was recommended. It
definitely doesn't work any better. It still has the null dereference
problem, and then it prints a bunch of smp_call_function_too_many errors,
apparently forever."
1777338,2018-06-21 04:36:37 UTC,Also a good idea to update the BIOS.
1777338,2018-06-19 15:00:08 UTC,"Can you see if this issue exists in the 4.15.0-24 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15010188"
1777338,2018-06-17 18:33:45 UTC,This also affects the mainline kernel build 4.17.0-041700.201806041953 that I was testing for another bug.
1777345,2018-06-18 19:31:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1777345,2018-06-19 09:56:35 UTC,"I have the same issue.
Sound card works with 127 kernel and with 4.15.xx under Kubuntu 18.04 but fails to work under 128 kernel.
Moreover, it causes Plasma load about several minutes until error line in dmesg appear
hda_intel azx_get_response timeout switching to single cmd mode
this is my sound card
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
At the end, after next reboot under 128 sound card disappears from lspci completely and do not appear even if I boot to any other kernel or even other OS.
I have to disable it and enable back in BIOS in order to appear back in lspci."
1777345,2018-07-29 03:21:25 UTC,Hello
1777345,2018-07-29 08:35:31 UTC,Reply Joseph Salisbury:
1777345,2018-07-30 15:40:06 UTC,"Hi,"
1777345,2018-08-05 18:51:28 UTC,"Tonight I reinstalled the system with the Ubuntu 18.04, and the sound card begins work as good as it did before.
So, if you couldn't fix it by yourself, just reinstall the system or upgrade to the ubuntu 18.04(except the guys which has been using the ubuntu 18.04)."
1777345,2018-06-17 18:30:06 UTC,This change was made by a bot.
1777345,2018-06-18 19:31:33 UTC,Does this issue go away if you boot back into the kernel prior to 4.4.0-127?
1777348,2018-06-21 14:08:00 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1777348,2018-06-21 18:13:13 UTC,"I think the issue is, this particular prerequisite is not in upstream, either. The debian packages zebra.service doesn't require remote_fs (or the systemd equivalent), just network.target."
1777348,2018-06-22 07:21:25 UTC,"The newer versions already avoid that by no more being after mounts, only in between network-pre and network."
1777349,2018-06-18 17:14:36 UTC,This bug also occurs in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901810
1777349,2018-06-19 13:02:52 UTC,"Thanks for filing this bug in Ubuntu, and also in Debian. The mailman package in Ubuntu is a straight sync from the Debian one, so it's best to be fixed there first."
1777349,2018-06-19 13:21:35 UTC,"It does look correct when displayed in a web browser, or not? I confirm the actual html file looks like you said, but the browser gives me a page like the attached screenshot (never mind it says ""xenial"" there, it's a bionic container, I just made a mistake with the hostname)."
1777349,2018-06-19 13:35:37 UTC,This is indeed correct.
1777349,2018-06-19 13:46:14 UTC,I'll need to spin up my own test container to properly test why it ever renders correctly. I don't think browsers are actually able to figure out that the text should be decoded from UTF-8 to KOI8-R and then interpreted as UTF-8. My Firefox wasn't able to do that when I opened template source file directly.
1777349,2018-06-25 20:19:20 UTC,Debian's commit: https://salsa.debian.org/mailman-team/mailman2/commit/1b04eda09f630f06254fa314aac9331240e4539e
1777361,2018-06-18 09:56:45 UTC,"Hi Bernard,"
1777362,2018-06-20 07:12:53 UTC,"Therefore the proposed fix does not work (and creates a potential bug).
And a full fix is more than one line change."
1777362,2018-06-20 20:05:31 UTC,"I also tested Python script part fetch, and this is the current operation table"
1777362,2018-06-20 09:44:57 UTC,"JP> Any change can create a bug and especially when related to netlist, needs to be carefully tested."
1777362,2018-06-19 20:43:02 UTC,"@ JP > If a empty value is *specified* in the netlist, I am expecting Pcbnew uses this specified (empty) value."
1777362,2018-06-19 15:11:32 UTC,"I tend to agree with JP.  This seems like an issue with the reporters netlist generation script rather than KiCad's netlist importer.  I don't understand how the value field defined in a footprint makes sense as the value of a component placed on a PCB but maybe I'm not seeing the use case here.  I'm not opposed to the idea but not for v5 because there could be unexpected issues that I would rather not risk.  Before I would approved something like this, I would like a clearer picture of the use case to make sure I understand what it is we are trying to accomplish."
1777362,2018-06-19 14:20:16 UTC,"I think /this/ behaviour is the same between Read Netlist and Update PCB, but there are definitely differences (such as how much control you have over resetting things)."
1777362,2018-06-19 13:49:38 UTC,"I'm curious as to why the behavior is different when using the internal
netlist versus using an external netlist.  Was this an oversight or
intentional?  I would think they should be the same."
1777362,2018-06-19 12:59:03 UTC,"I am thinking this is a problem that must be fixed in the externally-generated netlist, not by Kicad.
If a empty value is *specified* in the netlist, I am expecting Pcbnew uses this specified (empty) value.
If a value is expected in the board, it must appears in the netlist.
I am seeing this issue as trying to use a incorrectly build netlist."
1777362,2018-06-19 12:07:17 UTC,"@JP,"
1777362,2018-06-19 10:47:53 UTC,"@Jeff,
Here is my opinion:"
1777362,2018-06-19 10:15:43 UTC,"diff --git a/pcbnew/board_netlist_updater.cpp b/pcbnew/board_netlist_updater.cpp
index 0066e2771..3c78753d5 100644
--- a/pcbnew/board_netlist_updater.cpp
+++ b/pcbnew/board_netlist_updater.cpp
@@ -277,7 +277,8 @@ bool BOARD_NETLIST_UPDATER::updateComponentParameters( MODULE* aPcbComponent, CO
     }"
1777362,2018-06-19 10:15:08 UTC,"@Devs, any other opinions on this?  (It's a simple one-liner to change.)"
1777364,2018-09-15 19:29:45 UTC,"Actually, it just reoccurred on 2.1, then i dropped back to 2.0 and it reoccurred. Now back on 1.0 again."
1777364,2018-06-19 13:12:18 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1777364,2018-06-17 22:00:08 UTC,This change was made by a bot.
1777364,2018-06-17 21:41:27 UTC,client libraries of samba are 2:4.7.6+dfsg~ubuntu-0ubuntu2
1777364,2018-06-17 21:38:39 UTC,GPF syslog attached.
1777364,2018-06-26 22:05:21 UTC,Nice catch. Thank you.
1777364,2018-10-07 19:01:48 UTC,opened bug upstream https://bugzilla.samba.org/show_bug.cgi?id=13647
1777364,2018-06-26 17:35:33 UTC,Could be related to something in here:
1777364,2019-06-04 17:36:36 UTC,"Out of curiosity, for those affected by this how much RAM is there in your machines? My machine that crashes has 4GB but a machine at work also running bionic with ehem 128GB doesn't. That said samba behaves strange on it, sometimes file transfers just stop for no apparent reason."
1777364,2018-06-19 21:38:43 UTC,I grabbed the latest 4.18.0-041800rc1 and recreated it quickly
1777364,2019-05-30 18:39:20 UTC,"I've filed the same bug here, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811723 . Didn't find this one because I searched for the wrong terms, sorry about the duplicate."
1777364,2018-08-15 08:53:53 UTC,I just ran into this today.
1777364,2018-09-09 11:13:56 UTC,"I forced version 2.1 and i did NOT reproduce issue. I also forced 3.0 again, and issue occurred again."
1777365,2018-08-13 13:47:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777366,2018-08-30 14:19:57 UTC,"Hello there,
Although I am not a french speaking, I think i understood your issue.
This might be related to another python binary you have on your path."
1777373,2018-07-23 06:18:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777373,2020-08-10 00:31:32 UTC,kodi (2:17.6+git20180430.1623-final-0bionic)
1777388,2019-10-03 17:06:40 UTC,Tesseract is updated - so done.
1777388,2018-07-09 16:39:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777389,2018-06-18 07:01:26 UTC,"Skipped the following already-applied patches:
  * Input: elan_i2c - add ELAN0612 (Lenovo v330 14IKB) ACPI ID (applied as: UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table)"
1777389,2018-08-23 19:23:06 UTC,This bug was fixed in the package linux - 4.4.0-134.160
1777393,2021-02-17 17:08:18 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1777397,2018-06-20 16:09:15 UTC,I have found that problem exist only with debug=true.
1777397,2018-06-19 15:02:02 UTC,"Additional information is needed.  As described, retypes within the same pool and between different pools succeed.  Can you provide the version of code you're running, configuration, and command executed?"
1777398,2018-06-18 08:18:54 UTC,Also  present in HWE kernel 4.15.0-23-generic #25~16.04.1-Ubuntu for xenial
1777398,2018-06-18 08:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777398,2020-04-08 09:59:18 UTC,"fix was included in 4.4.0-177.207 (xenial), 4.15.0-92.93 (bionic), 5.3.0-46.38 (eoan), 5.4.0-15.18 (focal)"
1777398,2020-02-11 12:48:31 UTC,"Patch has been backported to all stable kernel releases, e.g. 4.19:"
1777398,2020-01-30 11:17:55 UTC,The patch is merged upstream and will be in 5.6.
1777398,2020-01-13 15:13:22 UTC,"Patch posted at
https://www.redhat.com/archives/dm-devel/2020-January/msg00021.html"
1777398,2019-12-20 18:42:31 UTC,"We see this in 4.19.y when using scsi_mod.use_blk_mq=y .  Marcus, are you using blk-mq?"
1777398,2019-05-13 06:18:19 UTC,Unfortunately still present in mainline 5.0.13 kernel:
1777398,2019-04-29 07:39:01 UTC,Currently testing 5.0.10 as we think the issue is related to thin trying to reallocate a  discarded block not working correctly
1777398,2019-04-29 07:36:52 UTC,Still present in 4.15.0-47-generic even though a number of dm/thin fixes have been backported
1777398,2019-01-19 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1777398,2018-11-19 07:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777398,2018-11-19 07:21:21 UTC,"This issue is still present. Possibly fixed by upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/md?id=a685557fbbc3122ed11e8ad3fa63a11ebc5de8c3"
1777398,2018-08-20 04:20:35 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1777398,2018-06-20 06:52:09 UTC,"Hi Joseph,"
1777398,2018-06-19 13:13:03 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1777405,2018-06-18 09:37:41 UTC,Can you please try downloading and manually re-installing the packages of the previous version?
1777405,2018-08-18 04:17:20 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1777405,2018-06-18 10:19:08 UTC,"Downgraded to those 6 .28.0-0ubuntu1 packages and rebooted: both user switching (black screen, unresponsive computer at 1st attempt at going to user switch screen) and hibernate resume failed.
Reverting to lightdm and all those function again"
1777413,2019-12-10 04:17:29 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1777413,2019-10-10 13:29:57 UTC,"I don't know, and I'm not using Ubuntu any more, sorry, feel free to close this."
1777413,2019-10-10 12:59:11 UTC,"Sorry I was unclear: when you set the system-wide proxy, did it update /etc/environment?"
1777413,2019-10-10 10:46:06 UTC,"The control-panel thingy _used_ to set https_proxy via /etc/environment, if it doesn't that might be a bug. Or maybe you set it and didn't restart snapd? That would also have this effect."
1777413,2019-10-10 10:46:23 UTC,(please set back to New after answering that)
1777413,2019-10-10 11:05:46 UTC,"I did set it, and I did restart."
1777415,2018-07-10 09:39:55 UTC,"This bug has been tested on:
* Ubuntu 14.04
* Ubuntu 16.04
* Ubuntu 16.10
* Ubuntu 17.04
All of them are affected."
1777415,2019-02-13 06:21:05 UTC,"Which files, when missing, cause this to happen?  Can you provide strace output of the failing process?"
1777415,2019-01-29 13:31:36 UTC,"> Jonathan Polak (jpolak) wrote on 2018-07-09:
> I confirm it affects Mate 18.04 as well.
>
> Moreover, a new bug on mate 18.04, plugging in an HDMI screen upon receiving the lockscreen,
> sometimes allows you to bypass it completely.
"
1777415,2018-07-28 13:20:30 UTC,"Is this bug affecting gnome-screensaver and mate-screensaver only? light-locker is fork of gnome-screensaver, too, but I could not reproduce the bug in Xubuntu using light-locker."
1777415,2018-07-20 22:24:13 UTC,"Jarno, sorry, that was a typo on my part. It looks like mate's screenlocker is mate-screensaver."
1777415,2018-07-20 10:49:51 UTC,"Seth, what do you mean by Xfce's screenslocking package? Ubuntu Mate 18.04 does not contain light-locker package by default: http://cdimage.ubuntu.com/ubuntu-mate/releases/18.04/release/ubuntu-mate-18.04-desktop-amd64.manifest"
1777415,2018-07-12 05:54:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777415,2018-07-11 08:17:08 UTC,"Markus Laire,
Yes, the bug is exploitable even with full disk encryption. Among other things, if there's an open instant messaging app, an attacker can send a message which would appear as if it was sent by the authenticated user."
1777415,2018-07-10 10:42:23 UTC,"""... having physical access means an attacker could simply access the hard disk directly or replace the password on it ..."""
1777415,2018-07-10 08:48:37 UTC,"The system must not give an access to the system with wrong passwords, in any case! Dear Ubuntu developers, please pay attention. Don't ignore the issue."
1777415,2018-06-25 15:39:48 UTC,"We're unlikely to fix this, since having physical access means an attacker could simply access the hard disk directly or replace the password on it and unlock the computer."
1777415,2018-07-09 17:52:19 UTC,I confirm it affects Mate 18.04 as well.
1777415,2018-07-09 14:31:18 UTC,Is this just affecting Ubuntu 16.04.4 or all Linux distros and all Ubuntu versions?
1777415,2018-07-09 13:54:34 UTC,"If this bug is result of errors on filesystem, it can manifest itself due to hardware failure. If system grants access to user data because of a minor filesystem malfunction, it's a problem."
1777415,2018-07-09 13:51:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777415,2018-07-03 13:40:31 UTC,"Yes, you can."
1777415,2018-07-02 14:37:01 UTC,Can I publish my research?
1777415,2018-06-26 10:09:40 UTC,"You can see in video that attacker can get access to sensitive data, such as opened KeePass with passwords, or documents in memory."
1777415,2018-06-25 11:44:21 UTC,">> In other words, you removed the hard disk while the system is suspended?
Yes.
After that I wake up system, and I can get access to the last opened apps. It works stable in Unity.
"
1777415,2018-06-22 12:43:29 UTC,Thanks for reporting this issue.
1777415,2018-07-09 21:34:13 UTC,"Jonathan, please file a new bug against xfce's screenlocking package with instructions for reproducing, hopefully someone will know how to address it."
1777428,2019-06-25 20:23:29 UTC,"I think we missed forwarding the proxy setting to aptdaemon when update-manager switched to that. That said, aptdaemon's proxy support is even more rudimentary than update-manager's: It only supports one proxy. update-manager at least has http and https proxies; apt itself supports proxies configured per host."
1777428,2019-09-27 09:21:01 UTC,Hi. I note the not fixing tag was added to this bug. Please may I know why? I have this issue. Is there a work around?
1777428,2018-10-22 17:38:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777434,2018-06-18 12:21:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777437,2018-06-24 08:39:22 UTC,Thx
1777437,2018-06-19 17:51:54 UTC,"Hi,"
1777437,2018-06-20 07:31:07 UTC,Hi
1777437,2018-06-23 12:22:18 UTC,Telegram is running in my system also.
1777437,2018-06-23 15:46:08 UTC,"I reainstalled all the libs and they are all present but telegram canot
find them..."
1777437,2018-06-23 15:58:56 UTC,The path for those libs at my system are
1777440,2018-07-12 12:35:21 UTC,"Reviewed:  https://review.openstack.org/576133
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=08d581fd5c4dcd91cf5999fa270d32e6fe6edf43
Submitter: Zuul
Branch:    master"
1777440,2018-07-26 13:36:08 UTC,This issue was fixed in the openstack/trove 10.0.0.0b3 development milestone.
1777440,2018-06-18 13:20:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576133"
1777443,2018-06-18 13:26:03 UTC,"Hi Aymen,"
1777443,2018-06-18 13:30:28 UTC,"Also, please attach all logs, that is:"
1777443,2018-06-18 13:47:40 UTC,"Hi Andres,"
1777443,2018-06-18 16:35:47 UTC,"Here are the logs:
Regiond.log: https://paste.ubuntu.com/p/RMW6tjWqQn/
rackd.log: https://paste.ubuntu.com/p/rrhbvD9zJv/
maas.log is empty"
1777443,2018-07-03 21:04:52 UTC,"Hi,"
1777443,2019-09-19 12:05:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1777444,2018-07-28 10:53:01 UTC,"Yes!!!
sudo apt-get purge bcmwl-kernel-source
sudo apt-get install broadcom-sta-dkms
It works!!!
Thank You All!!!!!!"
1777444,2018-07-27 13:26:28 UTC,Yes! This two commands also solved my problem with wi-fi after update from kernel 4.13.0 to 4.15.0 (hwe update) for Ubuntu 16.04.
1777444,2018-07-26 18:59:40 UTC,"Yes,"
1777444,2018-07-22 19:27:51 UTC,https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1757008
1777444,2018-07-22 19:20:58 UTC,@CSilva
1777444,2018-07-04 15:39:23 UTC,"The verification of the Stable Release Update for broadcom-sta has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1777444,2018-07-04 20:02:09 UTC,@CSilva
1777444,2018-07-04 18:35:09 UTC,Hello Everybody!
1777444,2018-07-04 10:01:24 UTC,BCM4313 also works with this. Thank you!
1777444,2018-07-04 15:39:19 UTC,This bug was fixed in the package broadcom-sta - 6.30.223.271-3~16.04.3
1777444,2018-07-04 20:57:11 UTC,@Saini
1777444,2018-08-08 09:14:42 UTC,"sudo apt-get purge bcmwl-kernel-source
sudo apt-get install broadcom-sta-dkms"
1777444,2018-06-25 15:24:05 UTC,"Hello Marcelo, or anyone else affected,"
1777444,2018-07-03 17:28:33 UTC,BCM43142 also works with this. Thank you!
1777444,2018-07-03 16:10:03 UTC,BCM4360 WiFi working again with this version. Many thanks.
1777444,2018-07-03 14:00:17 UTC,"broadcom-sta-dkms: Installed: 6.30.223.271-3~16.04.3
4.15.0-24-generic
tags:	added: verification-done verification-done-xenial"
1777444,2018-07-03 12:23:41 UTC,Installed it and the compilation of the module went OK. WiFi is working after restart with kernel 4.15.
1777444,2018-06-21 14:26:18 UTC,Thanks! I've sponsored this upload to xenial.
1777444,2018-07-04 09:04:04 UTC,BCM43228: Works.
1777444,2018-07-03 23:03:41 UTC,I've added the recommended patch but don't yet know if it has fixed my problem.  I'll post results when I know them.
1777449,2018-06-24 00:51:07 UTC,"Surely, it's still a question for me, that ovirt-guest-agent really can work without the GUI-oriented usermode package. I've created a ""fake"" usermode package just to provide the dependency and everything seems to work OK though there are minor odd things (ie, check-new-release always hogs the CPU I guess run by some guest agent routine here but I am not so much sure ...). I really wish an expert in this area can review how this problem can be solved nicely, ie using ovirt-guest-agent without any X11 related thing installed otherwise. Thanks."
1777453,2018-07-03 14:04:48 UTC,"Is anyone working on this? I just had another kernel update, and this still does not work."
1777453,2018-07-04 12:52:15 UTC,Use http://mirrors.kernel.org/ubuntu/pool/restricted/b/bcmwl/bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu4_amd64.deb with the 4.15 kernels as the package in xenial repositories doesn't have the patch yet for 4.15
1777453,2018-07-04 14:01:59 UTC,Thank you for the information. Will let you know if it works.
1777453,2018-07-04 14:44:01 UTC,It works. Thank you for the resolution.
1777458,2018-06-18 15:00:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576161"
1777458,2018-07-02 12:34:45 UTC,"Reviewed:  https://review.openstack.org/576161
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8cea14abf30c40da4ce5ffcfb4fb37dd79083255
Submitter: Zuul
Branch:    master"
1777458,2018-07-02 13:39:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/579561"
1777458,2018-07-08 02:06:23 UTC,"Reviewed:  https://review.openstack.org/579561
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f1cb6f1647025539093dc2cdd52da3ed129a6f5c
Submitter: Zuul
Branch:    stable/queens"
1777458,2018-07-30 16:08:13 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1777458,2018-09-24 14:47:30 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1777460,2018-10-08 21:49:03 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1777460,2018-10-03 15:15:13 UTC,"Reviewed:  https://review.openstack.org/607296
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c85f5e22e1cb8afd756341517bd7284ffc8e505b
Submitter: Zuul
Branch:    stable/ocata"
1777460,2018-09-24 14:47:38 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1777460,2018-09-24 14:47:01 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1777460,2018-10-02 16:06:33 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/607296"
1777460,2018-06-22 20:25:00 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/577548"
1777460,2018-06-22 20:14:26 UTC,"Reviewed:  https://review.openstack.org/576270
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f8aca778f704983bc7ebb0a75d42914fee2dac06
Submitter: Zuul
Branch:    stable/queens"
1777460,2018-06-18 23:13:15 UTC,"Typo in the bug description, it's not ""amdb-no-ssb"" it's amd-no-ssb."
1777460,2018-06-18 21:19:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/576270"
1777460,2018-06-25 04:53:27 UTC,"Reviewed:  https://review.openstack.org/577548
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=682ee60803c0e6a468e701282a18cee1c118c9df
Submitter: Zuul
Branch:    stable/pike"
1777462,2018-06-19 16:22:44 UTC,I'll try to convince Tempest to release a new version.
1777468,2018-06-19 04:03:39 UTC,"Fixed, thanks!"
1777468,2018-07-12 20:00:15 UTC,This bug was fixed in the package gnome-initial-setup - 3.28.0-2ubuntu13
1777475,2018-06-25 06:31:10 UTC,"This should be fixed in Nova. We cannot reliably build start-up ordering for containerized nova and ironic. Even if we did that install-time only, we still need to make sure the same order will be maintained after a node reboot."
1777475,2020-04-23 18:20:19 UTC,"Looks like the patch in comment #12 has addressed this from Nova's POV, so I'm setting this as Fix Release."
1777475,2018-07-26 17:59:06 UTC,This issue was fixed in the openstack/instack-undercloud 9.2.0 release.
1777475,2018-07-05 17:24:14 UTC,This issue was fixed in the openstack/instack-undercloud 8.4.3 release.
1777475,2018-06-27 10:50:50 UTC,"Reviewed:  https://review.openstack.org/576909
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=cd986d3ea26702f228c4b8ab5229b90f22bb27ca
Submitter: Zuul
Branch:    stable/queens"
1777475,2018-06-25 13:33:58 UTC,"Reviewed:  https://review.openstack.org/576948
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ebdd39deea589654958773b8a75f3b181c51fabe
Submitter: Zuul
Branch:    stable/queens"
1777475,2018-06-25 08:40:51 UTC,"Hi,"
1777475,2018-06-25 06:28:23 UTC,"We need the similar fix for t-h-t/puppet in order to fix this for containerized undercloud, which is going to be default installation method in Rocky. The instack only fix is not complete, reopening."
1777475,2018-06-19 09:26:40 UTC,From @ccamacho:
1777475,2018-06-21 13:23:42 UTC,"Reading back, comment 6 may sound like a non-sequitur without additional context. The issue as described is caused if nova compute comes up before ironic conductor. Nova compute calls plug_vifs for all instances in init_host, which is passed to the driver. This calls out to ironic which, prior to the merging of https://review.openstack.org/#/c/576608/, returned a 400 to us if conductor hadn't started yet, causing nova to put the instance in an error state."
1777475,2018-06-21 10:31:02 UTC,"The Nova fix should be to not call plug_vifs at all during ironic driver initialization. It probably isn't necessary for 'non-local' hypervisors in general, so guessing also Power, Hyper-V, and VMware."
1777475,2018-06-20 16:38:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/576909"
1777475,2018-06-20 10:06:34 UTC,"Hi Bogdan, 1777606 was meant to be to track the nova side of it, but I wrongly created it in tripleo and closed it as invalid."
1777475,2018-06-19 13:11:20 UTC,Is this a dup of https://bugs.launchpad.net/tripleo/+bug/1777606 ?
1777475,2018-06-19 09:28:08 UTC,"Hi,"
1777475,2018-06-23 16:09:52 UTC,"Reviewed:  https://review.openstack.org/576165
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=aab11800fefc42ebae37109cf30076aa88c4d88b
Submitter: Zuul
Branch:    master"
1777477,2018-11-29 20:43:26 UTC,"And also this patch could help to fix ubuntu 18.10 and 18.04 amule
https://github.com/amule-project/amule/pull/147"
1777477,2018-11-17 11:04:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777477,2018-11-17 11:05:54 UTC,"amule ins not working at all in ubuntu 18.10, it needs a new version using this patch:
https://github.com/amule-project/amule/pull/135"
1777482,2018-12-19 15:22:39 UTC,Moved to medium as there is a work-around.
1777482,2018-06-19 18:50:48 UTC,Confirmed that I get the same behavior with python3-novaclient. It looks like python-novaclient works as a work-around for now.
1777482,2018-06-20 11:43:25 UTC,"other workaround is openstack client
  openstack console log show xenial-20180617-135556"
1777490,2018-06-20 22:16:36 UTC,Also related to https://bugs.launchpad.net/evergreen/+bug/1720436
1777490,2018-08-24 21:09:17 UTC,"With the branch on bug 1712854, the column picker options have changed. Many of the previously-identified columns have been removed, but more columns have been added, some of which should probably be removed too."
1777490,2018-06-18 19:58:02 UTC,Related to https://bugs.launchpad.net/evergreen/+bug/1735808
1777500,2018-06-20 13:34:55 UTC,"Upstream bug: https://github.com/robint99/mate-dock-applet/pull/144
Upstream pull request: https://github.com/robint99/mate-dock-applet/pull/150"
1777504,2018-06-18 20:39:56 UTC,I can confirm that running `sudo apt-get remove ubiquity-slideshow-ubuntu` finally worked for me.
1777504,2018-06-20 19:50:12 UTC,Weird... Ubiquity seems to have somehow stopped running as root:
1777512,2019-05-09 16:43:58 UTC,Sub'd ~field-high.
1777512,2019-05-14 06:33:35 UTC,We've also been seeing keyserver request failures during our CI/Build process
1777512,2019-05-06 19:44:31 UTC,More failures over the weekend
1777512,2018-06-27 14:42:18 UTC,Continues to effect our test runs
1777514,2018-06-19 07:02:34 UTC,"Not sure if this was the correct ""corrupted double linked list"" issue but if it is, it was happening under Wayland. Fresh install."
1777514,2018-06-19 07:36:27 UTC,"Hmm, problem:"
1777514,2018-06-24 18:44:04 UTC,I installed 4.16.17 kernel and ubuntu-proposed and I can still reproduce it consistently but now Xwayland crashes rather than gnome-shell. (Or at least that's what I gather from /var/crash)
1777514,2018-06-24 19:01:02 UTC,"Upgraded mesa and wayland with X-Updates PPA (https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates) and problem is still present, and now gnome-shell made a crash again."
1777516,2018-09-15 00:03:41 UTC,I assume this mailing list conversation is a response to this: https://<email address hidden>/msg31906.html
1777516,2018-08-20 05:19:39 UTC,"@Seth
IPC 7351C isn't released yet, but you can find some info at
http://www.ocipcdc.org/archive/What_is_New_in_IPC-7351C_03_11_2015.pdf (page 9+) and
https://www.ipc.org/committee/drafts/1-13_d_7351CGoals.pdf (last page)."
1777516,2018-08-20 06:33:50 UTC,"Using a custom shape could be a temporary option.
However this is not a good solution."
1777516,2018-08-25 19:45:56 UTC,The main reason to use polygon pads for us right now is that some qfn footprints just need a chamfered pad at the corner pads. These are pads where the current workaround of using line thicknesses works.
1777516,2019-04-13 08:17:28 UTC,The current implementation does not fix all we needed. I have documented requested improvements in: https://bugs.launchpad.net/kicad/+bug/1824614
1777516,2018-08-20 02:23:31 UTC,"@Rene- Do you know what the IPC recommendation is for non-rectangle pads?  I don't have access to a copy of version C.  Absent strong driver, I think it is safest to code this as a file format change for the pad but there may be a reason to facilitate the approach you suggest (with the convex limitation)."
1777516,2018-08-18 00:19:04 UTC,"I don't think it really requires file format changes. Polygon pads can have a line width which will add a radius to it.
The only thing necessary would be an abstraction layer in the graphical interface that automatically moves the polygon points inwards by the required radius and assigns a line width of double the radius."
1777516,2018-06-30 03:06:59 UTC,"This will require a file format change, so we can look at it during 6"
1777516,2018-06-19 16:09:05 UTC,Got it. Thank you!
1777516,2018-06-18 22:23:29 UTC,"Custom pad shapes can cave rounded corners, you just have to set polygon's outline thickness to a nonzero value.
Unfortunately, that thickness will be added to polygon's size, which makes creating precise pad shapes cumbersome."
1777516,2018-08-18 16:09:17 UTC,I'm pretty sure that that solution will only round the convex corners.  Is that the desired limitation for pads?
1777516,2018-08-18 16:26:56 UTC,"Yes, I confirm it works only for convex polygons, and can modify the initial shape (I mean setting a radius to a given value and then to 0 does not give the initial shape in every case)."
1777520,2018-09-25 10:31:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777520,2019-12-04 16:23:10 UTC,the issue looks like a corruption rather than a package bug
1777521,2018-06-24 18:40:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777523,2018-09-25 23:44:14 UTC,"Well, no multiple .network files don't stack.  However, one can use a
drop-in conf.d as long as it matches at least one .network file."
1777523,2018-09-25 22:41:32 UTC,Thanks!
1777523,2018-09-25 20:04:00 UTC,https://trello.com/c/vxdv5lIa/12-dns-control-over-llmnr-and-dnssec-and-other-systemd-resolved-functions
1777523,2018-09-25 19:50:30 UTC,"Hi,"
1777523,2018-09-25 18:45:21 UTC,I can reproduce this on 300 machines; what do I need to have this looked at by someone?
1777523,2018-06-18 23:29:40 UTC,Also see: https://askubuntu.com/questions/1047734/how-can-i-disable-llmnr-in-netplan
1777523,2018-09-25 22:55:49 UTC,More info on the 10-disable-llmnr.network fix:
1777523,2018-09-25 23:25:35 UTC,"On Tue, Sep 25, 2018 at 6:11 PM Aaron Thomas <email address hidden> wrote:

>
> More info on the 10-disable-llmnr.network fix:
>
> My log file says things like:
>
> systemd[1]: Started Network Service.
> systemd-networkd[80848]: ens32: Link is not managed by us
> systemd-networkd[80848]: ens160: Link is not managed by us
> systemd-networkd[80848]: lo: Link is not managed by us
>
> after the change. The ip address disappear, but the LLMNR setting is in
> fact set to No.
>
> Removing the file results in a return of the ip addresses, and the LLMNR
> setting is back to Yes again.
"
1777526,2018-08-24 10:48:16 UTC,Dear Developers!
1777526,2018-07-09 10:26:22 UTC,"Hi, Colleagues!"
1777526,2018-06-22 16:31:10 UTC,Dear Santhosh!
1777526,2018-06-22 05:17:06 UTC,"Hi Viktor,"
1777526,2018-06-19 07:59:50 UTC,"Hi, Santhosh!"
1777526,2018-08-28 13:10:46 UTC,Seeing the same with Ubuntu 18.04.1 with all latest updates and hplip/libsane-hpaio 3.17.10+repack0-5
1777526,2018-08-31 18:03:54 UTC,"Upgrading HPLIP to Cosmic version fixed the problem. With M1212 on different Bionic system as well.
(add Cosmic APT sources, upgrade only Bionic HPLIP packages with version 3.17.10*, disable Cosmic sources, continue using all the rest from Bionic).
Btw, building HPLIP 3.18.7 from vendor sources did not help. Cosmic rebuild is magical."
1777526,2018-06-19 05:38:47 UTC,"Hi Viktor,"
1777527,2018-06-19 13:11:37 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1777527,2018-06-20 05:55:43 UTC,I installed the mainline kernel
1777527,2018-07-13 09:54:19 UTC,"I just installed the mainline 4.18 rc4 kernel, it does not work yet."
1777527,2018-07-13 10:21:03 UTC,Alright. So are there any expectations about the timeline or the possibility of fixing this issue?
1777527,2018-06-18 21:47:06 UTC,"I tried a million thing that I even can't remember. But I recently found this bug that might be related:
https://bugzilla.kernel.org/show_bug.cgi?id=81331"
1777544,2020-08-10 00:30:20 UTC,"kodi (2:17.6+git20180430.1623-final-0bionic)
kodi-bin (2:17.6+git20180430.1623-final-0bionic)"
1777546,2018-06-25 17:28:51 UTC,Seeming telepathy-farstream causing this issue. https://dev.gajim.org/gajim/gajim/issues/9129
1777546,2018-06-25 17:11:57 UTC,"Same issue here. I get this from running ""gajim -v"" on bionic"
1777546,2018-06-23 01:08:18 UTC,"(gdb) bt
#0  _g_log_abort (breakpoint=1) at ../../../../glib/gmessages.c:583
#1  0xb6ef39b9 in g_logv (log_domain=0xb700f7db ""GLib-GObject"", log_level=G_LOG_LEVEL_WARNING,
    format=0xb7016c74 ""can't peek value table for type '%s' which is not currently referenced"", args=0xbfffc98c ""ss\001\267"")
    at ../../../../glib/gmessages.c:1391
#2  0xb6ef3ae5 in g_log (log_domain=0xb700f7db ""GLib-GObject"", log_level=G_LOG_LEVEL_WARNING,
    format=0xb7016c74 ""can't peek value table for type '%s' which is not currently referenced"") at ../../../../glib/gmessages.c:1432
#3  0xb70088e7 in g_type_value_table_peek (type=<optimized out>) at ../../../../gobject/gtype.c:4267
#4  0xb3917a92 in gst_structure_set_valist_internal (structure=<optimized out>, fieldname=<optimized out>, varargs=0xbfffca98 ""\324\312\377\277"",
    varargs@entry=0xbfffca78 ""\030"") at gststructure.c:607
#5  0xb3918cb1 in gst_structure_set (structure=0x8850c40, field=0xb3e966d9 ""channels"") at gststructure.c:638
#6  0xb3e9355b in gst_opus_enc_get_sink_template_caps () at gstopusenc.c:879
#7  gst_opus_enc_sink_getcaps (benc=0x8a43908, filter=0x0) at gstopusenc.c:908
#8  0xb35f5677 in gst_audio_encoder_sink_query_default (enc=0x8a43908, query=0x8a63890) at gstaudioencoder.c:1750
#9  0xb38f504a in gst_pad_query (pad=0x8a552e0, query=0x8a63890) at gstpad.c:4024
#10 0xb39306d3 in gst_pad_query_caps (pad=0x8a552e0, filter=0x0) at gstutils.c:3043
#11 0xb38eb6be in gst_pad_link_check_compatible_unlocked (flags=GST_PAD_LINK_CHECK_DEFAULT, sink=0x8a552e0, src=0x8a556d0) at gstpad.c:2260
#12 gst_pad_link_prepare (srcpad=srcpad@entry=0x8a556d0, sinkpad=sinkpad@entry=0x8a552e0, flags=flags@entry=GST_PAD_LINK_CHECK_DEFAULT) at gstpad.c:2397
#13 0xb38f860a in gst_pad_link_full (srcpad=0x8a556d0, sinkpad=0x8a552e0, flags=GST_PAD_LINK_CHECK_DEFAULT) at gstpad.c:2524
#14 0xb38f8e2e in gst_pad_link (srcpad=0x8a556d0, sinkpad=0x8a552e0) at gstpad.c:2645
#15 0xb3854877 in create_codec_bin_from_blueprint (codec=0x8a5d560, blueprint=0x8a30a40, name=0xb386b071 ""gather_send_codecbin"",
    direction=FS_DIRECTION_SEND, error=0xbfffcdd8) at fs-rtp-discover-codecs.c:1735
#16 0xb3855884 in codec_blueprints_add_caps (media_type=FS_MEDIA_TYPE_AUDIO) at fs-rtp-discover-codecs.c:1841
#17 create_codec_lists (send_list=0x886f410, recv_list=0x8855a10, media_type=FS_MEDIA_TYPE_AUDIO) at fs-rtp-discover-codecs.c:351
#18 fs_rtp_blueprints_get (media_type=FS_MEDIA_TYPE_AUDIO, error=0x8a20280) at fs-rtp-discover-codecs.c:300
#19 0xb38470dc in fs_rtp_session_constructed (object=0x8a202c0) at fs-rtp-session.c:1218
#20 0xb6fe72c1 in g_object_new_internal (class=class@entry=0x8a70000, params=params@entry=0xbfffcffc, n_params=n_params@entry=3)
    at ../../../../gobject/gobject.c:1839
#21 0xb6fe9010 in g_object_new_valist (object_type=<optimized out>, first_property_name=<optimized out>, var_args=<optimized out>)
    at ../../../../gobject/gobject.c:2122
#22 0xb6fe90c9 in g_object_new (object_type=145144192, first_property_name=0xb3866ab4 ""media-type"") at ../../../../gobject/gobject.c:1642
#23 0xb384d22d in fs_rtp_session_new (media_type=FS_MEDIA_TYPE_AUDIO, conference=0x8a200a8, id=1, error=0xbfffd2ac) at fs-rtp-session.c:2412
#2..."
1777546,2018-06-22 19:01:23 UTC,"Lucas, once Gajim has been interrupted by the warning, please let gdb issue a backtrace with ""bt"" command and post the output."
1777546,2018-06-21 23:19:12 UTC,"$ G_DEBUG=fatal-warnings gdb --ex r --args python3 $(which gajim)
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""i686-linux-gnu"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word""...
Lendo símbolos de python3...(no debugging symbols found)...concluído.
Starting program: /usr/bin/python3 /usr/bin/gajim
[Thread debugging using libthread_db enabled]
Using host libthread_db library ""/lib/i386-linux-gnu/libthread_db.so.1"".
warning: Error reading shared library list entry at 0xb60
warning: Error reading shared library list entry at 0x4a70
warning: Error reading shared library list entry at 0xffffdc70
warning: Error reading shared library list entry at 0x2fa0
warning: Error reading shared library list entry at 0xffffbe60
warning: Error reading shared library list entry at 0x1cf0
warning: Error reading shared library list entry at 0x3cc0
[New Thread 0xb541db40 (LWP 12636)]
[New Thread 0xb4affb40 (LWP 12637)]
warning: Error reading shared library list entry at 0x20a0
warning: Error reading shared library list entry at 0x27b0
warning: Error reading shared library list entry at 0x40d0
warning: Error reading shared library list entry at 0xffff87e0
warning: Error reading shared library list entry at 0x2df0
warning: Error reading shared library list entry at 0x6290
warning: Error reading shared library list entry at 0xffffde00
warning: Error reading shared library list entry at 0xffffe300
warning: Error reading shared library list entry at 0x48f0
warning: Error reading shared library list entry at 0xffffe400
warning: Error reading shared library list entry at 0x1a10
warning: Error reading shared library list entry at 0xffffaa40
warning: Error reading shared library list entry at 0x1200
warning: Error reading shared library list entry at 0xffffc200
warning: Error reading shared library list entry at 0xffffe600
warning: Error reading shared library list entry at 0x1c00
warning: Error reading shared library list entry at 0xffffbc00"
1777546,2018-06-21 20:51:02 UTC,"> Warning: can't peek value table for type '(null)' which is not currently referenced
This is printed by
g_warning (""can't peek value table for type '%s' which is not currently referenced""
from glib/gobject/gtype.c
"
1777546,2018-06-21 20:05:25 UTC,It would be interesting if upgrading to
1777546,2018-06-25 21:33:35 UTC,"Removing gir1.2-farstream-0.2 also ""fixes"" the crash for me."
1777553,2020-02-09 14:39:56 UTC,"@All:
don't hesitate to encourage the libofx maintainers @https://github.com/libofx/libofx/issues/20"
1777553,2018-09-28 20:35:02 UTC,"the problem is due to a bug with libofx compiled for windows, we wait for a patch
https://github.com/libofx/libofx/issues/20"
1777553,2019-04-21 09:22:13 UTC,"As you may see by yourself by reading the bug page @libofx,"
1777553,2019-04-04 17:19:10 UTC,Any news on that libofx patch?
1777553,2018-09-27 13:17:45 UTC,"I'm having trouble importing any ofx file with special characters like accents, no mather what the encoding is. Tried UTF-8, cp1252, 8859-1...."
1777553,2018-07-18 20:59:11 UTC,"libofx bug:
https://github.com/libofx/libofx/issues/20"
1777553,2018-07-18 20:41:23 UTC,"ofxdump the file produce SGML errors, I will post to libofx dev to get guidance on if your file is wrong or libofx problem"
1777553,2018-06-21 11:31:57 UTC,"your file contains
ENCODING:USASCII
CHARSET:8859-1"
1777553,2018-06-20 16:48:04 UTC,"homebank version ?
os ?"
1777553,2019-05-30 06:41:22 UTC,Similar problems with importing UTF-8 OFX files with non-latin letters on HomeBank 5.2.6 / Windows 10 v1903. The same OFX file in Ubuntu imports well.
1777553,2018-06-20 21:45:25 UTC,"HB version: 5.1.8
OS: Win10"
1777556,2018-06-20 01:00:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576670"
1777563,2020-07-11 01:49:28 UTC,"@rashtrapathy: This is just a warning, even though they might be confusing when they turn up in the output of a kolla-ansible deployment.
I thought I had an issue when this error ocurred during a deployment, until I looked at the nova logs, where the real root cause was shown (env issue in my case)."
1777563,2018-06-19 06:19:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576375"
1777563,2019-02-21 07:21:40 UTC,Do we have any workaround to resolve this issue in rocky ?
1777566,2018-06-19 08:25:28 UTC,"Reviewed:  https://review.openstack.org/576350
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=136a001ad22576d9330f51ce88e86d07fc9b3c52
Submitter: Zuul
Branch:    master"
1777567,2018-07-22 09:18:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777568,2018-06-19 08:53:16 UTC,"Reviewed:  https://review.openstack.org/576213
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=6f4ed11ff50ad11e9844a11b2e02c87c27cca332
Submitter: Zuul
Branch:    master"
1777570,2019-05-08 08:20:10 UTC,There seems to be a problem with your DB-config:
1777570,2019-05-08 08:14:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777571,2018-07-27 13:22:45 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b3 development milestone.
1777586,2020-01-20 21:05:15 UTC,"I compiled kernels with the patch for u16.04 and u18.04, seems to be working for me:
https://t12.catchmedia.com/kernel_adaptec/"
1777586,2019-06-27 17:43:09 UTC,I to want to thank you for your hard work.   It is appreciated.
1777586,2019-06-27 17:28:36 UTC,Thanks for your work. Please leave a comment when the fix lands in Linus' tree.
1777586,2019-06-27 16:26:29 UTC,"Hi guys, we've faced the same issue you are talking about,
i've found the guilty patch:
  395e5df79a95 (""scsi: aacraid: Remove reference to Series-9"")"
1777586,2019-05-16 07:45:51 UTC,Adaptec/Microsemi support recommends to replace the RAID card for ubuntu 18.04..
1777586,2019-05-15 20:09:55 UTC,"Hello, we have the very same problem after upgrading to ubuntu 18.04 .
Server is not booting anymore, hanging on:"
1777586,2019-03-11 06:50:30 UTC,"There aren't many aacraid commits, you can directly test them out:"
1777586,2019-03-11 06:48:36 UTC,Would it be possible for you to do a kernel bisection?
1777586,2019-11-25 20:22:08 UTC,I also have this issue triggered on my system. Is there a fix in the ubuntu-provided kernel yet?
1777586,2019-03-07 01:19:32 UTC,i can try.
1777586,2018-06-20 15:49:35 UTC,"Another note, if I let the system run as a Web Server/eMail server there are no issues.   I don't see any errors in the log files.   The issue only arises when there is heavy I/O to the Hardware RAID controller.   The Software RAID works fine as my boot drives are mirrored SSD's.   The DATA drive is the RAID 5 Adaptec controller.   3 1TB Drives.   Thanks for the help with this."
1777586,2018-06-20 07:01:43 UTC,"So I downloaded the new kernel as you requested.   I have 4.17.2-041702-generic installed and booted.   After loading the new kernel, I ran the same tests as before where it would fail with the aacraid errors.   And it is exhibiting the same behaviour."
1777586,2018-06-20 05:13:39 UTC,I have decided to try to eliminate some things.   I ended up formatting my RAID drives and cleared that out.   I also rebuilt the RAID Array in hopes of clearing up this issue.  But these did not fix what we are seeing here.
1777586,2018-06-20 17:32:48 UTC,"For more information, I am now regressing on kernels.   I tried 4.14.50 and it too errors."
1777586,2018-06-20 16:08:01 UTC,For giggles I downloaded the latest kernel available today.   4.18.RC1 to try.   And it too exhibits the same thing.   No change.
1777586,2018-06-20 17:53:34 UTC,"I have now went back to 4.13.16 as a test and it too is exhibiting the same behaviour.   I think I have chased enough kernels for now.   If there is anything else you need, please let me know.   Thank you for your help in this matter.  It takes approximately 283 seconds before the first error message popped up on the ""aacraid: Host adapter abort request""."
1777586,2018-06-22 07:01:44 UTC,I am unable to run the requested command as requested by the automated kernel bot.  apport-collect 1777586.  I am setting the defect case to confirmed as requested.
1777586,2018-08-04 22:05:18 UTC,this bug goes all the way back to centos 5 and kernel 2.6.
1777586,2019-03-10 00:42:10 UTC,"linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64     - no good
linux-image-4.13.1-041301-generic_4.13.1-041301.201709100232_amd64       - no good
linux-image-4.13.0-041300rc1-generic_4.13.0-041300rc1.201707151931_amd64 - no good
linux-image-4.12.14-041214-generic_4.12.14-041214.201709200843_amd64     - good
linux-image-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64     - good"
1777586,2018-06-19 13:02:24 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1777586,2018-06-19 07:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777586,2019-03-06 03:15:50 UTC,"Trent,
Would it be possible to do a kernel bisection?"
1777586,2019-03-06 03:07:52 UTC,mainline linux-image-4.9.162-0409162-generic_4.9.162-0409162.201903051732_amd64.deb is working fine.
1777586,2019-03-06 02:45:53 UTC,I also have this issue after upgrading to 18.04.2 LTS with a host with an Adaptec 5805 and linux-image-4.15.0-46-generic.
1777586,2019-01-14 18:51:02 UTC,"I have this same issue after upgrading 16.04 to 18.04. I have the Adaptec 5805 controller and my computer freezes at fairly random, might be every 1-2 days or 3-4 weeks."
1777586,2018-06-19 13:02:48 UTC,"Also, does this bug go away if you select the prior kernel version from the GRUB menu?"
1777586,2019-01-02 13:26:24 UTC,I run in similar issue after upgrading from 14.04 to 16.04 as well to 18.04 again.
1777591,2019-05-02 21:55:43 UTC,"Reviewed:  https://review.opendev.org/649535
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=575fd08e63119900969d1f6784034772c7ab450b
Submitter: Zuul
Branch:    master"
1777591,2018-09-24 14:47:09 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1777591,2018-07-31 15:29:23 UTC,"Reviewed:  https://review.openstack.org/584616
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ab1fd87ed9563ce8cf865ff539916e5d804853dc
Submitter: Zuul
Branch:    stable/queens"
1777591,2018-07-30 16:07:01 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1777591,2018-07-21 15:51:10 UTC,"Reviewed:  https://review.openstack.org/576693
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1d91811ad499af1d291f5c819ced5b1fdf3520c7
Submitter: Zuul
Branch:    master"
1777591,2018-06-27 10:56:18 UTC,"To summarize some of the conversation related to the planned fix for stein, where something like `uuid=in:{uuid},{uuid}` would be added:"
1777591,2018-06-25 14:38:39 UTC,Agreed in the scheduler meeting [1]:
1777591,2018-06-20 03:11:22 UTC,'No hosts matched due to not matching ...' in logs let me confused and should correct it.
1777591,2018-06-20 03:22:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576693"
1777591,2018-06-22 09:38:48 UTC,"I was going to suggest that one way to address this might be to use a nova-scheduler request filter to narrow the query space that is being looked at when querying placement. However we don't currently support an `rp_uuid=in:{uuid},{uuid},{uuid}` parameter on GET /allocation_candidates"
1777591,2018-06-25 14:11:48 UTC,"We would have this same problem with rebuild if we need to go through the scheduler again (in case the image changes during rebuild). So yeah we likely need a pre-filter on this, and it was discussed in this spec:"
1777591,2018-07-22 05:28:45 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/584616"
1777604,2018-06-19 08:40:10 UTC,"Worked with:
nest vendor lp:~sajoupa/telegraf/+git/vendor vendor 1.6.4
which makes sense."
1777607,2018-06-19 08:48:06 UTC,The same problem will occur when flavor_A is private. Because we must use is_public param. refer to: https://developer.openstack.org/api-ref/compute/#list-flavors
1777607,2020-08-22 08:00:11 UTC,"Hi,"
1777607,2019-11-26 00:45:04 UTC,"Hi,"
1777607,2019-08-30 08:36:32 UTC,"As liyi pointed out, the problem will also occur when the flavor is private."
1777607,2018-06-19 09:40:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576460"
1777608,2018-08-17 18:28:05 UTC,This can also happen if a node with an instance was deleted from ironic while nova-compute was down: http://paste.openstack.org/show/728326/
1777609,2019-02-21 16:36:45 UTC,"Change abandoned by Juan Badia Payno (<email address hidden>) on branch: master
Review: https://review.openstack.org/576429"
1777609,2021-02-01 16:39:20 UTC,IMHO this was fixed when the standalone role was introduced on tripleo. If there is no rejection we can close this.
1777609,2021-02-17 17:08:23 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1777609,2018-06-19 08:47:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576429"
1777625,2018-06-19 13:45:09 UTC,"setuptools==39.2.0
pbr==4.0.4"
1777625,2018-06-19 13:25:18 UTC,"Which version of pbr and setuptools do you have, and how did you install them (via pip or via system packages)?"
1777627,2018-06-19 19:51:04 UTC,"But ""problem"" here is that QoS API is build this way. Please take a look at REST path e.g. for DELETE rule: /v2.0/qos/policies/{policy_id}/bandwidth_limit_rules/{rule_id}
So to make this call You need policy_id and that's why it is done like that."
1777627,2018-06-19 15:12:10 UTC,"Since a QoS rule will only be associated with one QoS policy, I believe this is a valid change."
1777627,2019-03-21 21:38:27 UTC,"Reviewed:  https://review.openstack.org/613820
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=636f1b539446c27c703744159c10bc08739f8937
Submitter: Zuul
Branch:    master"
1777627,2018-11-29 15:05:27 UTC,"Reviewed:  https://review.openstack.org/620429
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=ab284169b2f4a859affc995dbd4cd4eebf7b96e1
Submitter: Zuul
Branch:    master"
1777627,2018-10-29 01:13:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613820"
1777627,2018-10-22 10:28:08 UTC,"Reviewed:  https://review.openstack.org/610666
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=0c476067f6406d549eb629f3b970e4a2e896aca4
Submitter: Zuul
Branch:    master"
1777627,2018-10-15 19:11:46 UTC,"Reviewed:  https://review.openstack.org/608473
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=eb2e5c96aee844102d2f5e2ad03f87df8664202e
Submitter: Zuul
Branch:    master"
1777627,2018-10-08 00:20:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608473"
1777627,2018-09-04 08:32:26 UTC,@Miguel feel free to implement this RFE.
1777627,2018-06-22 13:46:47 UTC,This is a tough one. I see Arkady's point about usability but at the same time Slawek and Brian point about backwards compatibility is also valid. Could we keep the current API and implement an extension that allows users to handle QoS rules directly by uuid?
1777627,2018-08-31 14:47:15 UTC,"This RFE was discussed by the Neutron drivers and approved on August 31st, following the proposal outlined in #12 above."
1777627,2018-08-30 20:25:43 UTC,I like YAMAMOTO's proposal. Alias would be really good idea IMO.
1777627,2018-07-13 13:41:48 UTC,"Yes, I like saving one ReST round trip"
1777627,2018-07-06 14:38:17 UTC,"FWIW, while midonet qos api basically is mirroring neutron's,
it intentionally differed in this part for the exact reason.
https://docs.midonet.org/docs/latest-en/rest-api/content/qos-policy-dscp-marking-rules.html"
1777627,2018-07-06 13:36:25 UTC,"@Arkady, @Slawek,"
1777627,2018-07-01 07:20:57 UTC,@Miguel
1777627,2018-06-28 23:16:38 UTC,"@Arkady,"
1777627,2018-06-19 19:59:28 UTC,So based on Slaweq's comment the policy_id is required by the API in the DELETE case.  So this looks like an invalid bug.  I'll wait for the submitters response before marking as such.
1777627,2018-06-19 20:42:40 UTC,@Brian: DELETE was only an example. In fact it's the same for all other QoS calls :)
1777627,2018-06-21 07:03:39 UTC,"Guys, his is a valid bug, I talked to developers and QE before opening this issue. I don't know what was the reason for implementing such strange behavior, maybe it was quick and simple solution, but for the end user this behavior is not friendly.
I think that user experience is the key to make the decision."
1777627,2018-06-24 13:46:49 UTC,"Maybe we could add something like ""get_policy_for_rule"" API call to neutron? Then this call could be used in OpenStackSDK/Client to ""discover"" QoS policy for e.g. rule and do call in same way as it is done now.
That should be IMO easy to implement, backward compatible and UX for OSC/SDK should be better."
1777627,2018-06-22 13:49:12 UTC,"Added rfe tag and ""RFE"" to the description to highlight it to the drivers team"
1777627,2018-08-31 14:48:17 UTC,"@Arkady,"
1777633,2018-06-20 01:51:01 UTC,"""out of range"" doesn't mean it's the wrong resolution. It means that you've specified some frequencies/values that the monitor can't support, or isn't meant to support in case they cause damage."
1777639,2018-06-19 12:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777643,2018-06-29 11:38:20 UTC,Seems related (provides a good example at least) https://review.openstack.org/#/c/578105
1777643,2018-06-19 12:42:52 UTC,Please correct the tags if that is not a promotion blocker (those patches was merged at the end of May mostly...)
1777654,2018-06-19 13:47:08 UTC,"damn, i started the bugreport for network-manager-openvpn instead fro network-manager-openvpn-gnome"
1777654,2018-09-11 17:58:34 UTC,"I also opened an issue at Debian: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/7
On debian the same issue occurs."
1777659,2018-06-19 14:42:18 UTC,"if this is indeed a bug, note you'll need bug tasks on snapd, review-tools, and snapstore as well as here."
1777667,2018-06-19 19:43:18 UTC,"Ahh of course, because it's instant not at the beat, so it does need to take into account current BPM when calculating offset from beat marker. Clearly something is wrong with the maths involved though...."
1777667,2018-06-19 23:01:06 UTC,The issue is fixed in https://github.com/mixxxdj/mixxx/pull/1716
1777667,2018-06-20 07:02:01 UTC,Fix in #1716 confirmed.
1777667,2018-06-19 19:15:54 UTC,"Currently, it does not seek to match two beats, it seeks to match the beat fraction at the playposition. This is the desired behaviour for continuous sync, but it does not work for not synced tracks."
1777667,2018-06-19 18:42:37 UTC,"I can reproduce the issue.
I think in this case it is correct to have no special 2x code. Just align the two closest beats."
1777667,2018-06-19 17:27:47 UTC,"Sync needs a special case for x2 BPM differences (I actually would like added and think raised a Bug on it in the past x4, especially when using a third deck to drop in something very slow and quite sparse behind another mix. I may just raise my lowest BPM value at some point....."
1777667,2018-06-19 17:03:14 UTC,"We have special code for handling half/double sync situations, but I think it may have been a bad idea and a mis-feature. I would be supportive of removing that special casing."
1777667,2018-06-19 20:01:45 UTC,"There is nothing ""wrong"" in the math, it just behaves unexpected.
if you have a 120 BMP track at 0.5 beat fraction and you seek a 60 BMP track also to 0.5 beat position, the result looks like this:"
1777667,2018-06-19 21:59:08 UTC,Why is it ever using half beat as the zero phase point? It should always reference to the beatmarker.
1777674,2021-01-02 07:10:36 UTC,"I'm at the end of a Ubuntu installation on a pre-installed windows laptop. I have the same issue Ubuntu 20 hangs at ""kvm: exiting hardware virtualization"" on AMD laptop.
It has been stuck there for half an hour or more.
I didn't set the wi-fi connection during installation"
1777674,2018-10-10 16:22:29 UTC,I started a kernel bisect between v4.14 final and v4.15-rc1. The kernel bisect will require testing of about 7-10 test kernels.
1777674,2018-10-10 14:22:45 UTC,"Ideally, we'd want to bisect and fix the kernel itself to reliably shutdown. yanking ahci sounds like a large hammer. Invalidating systemd task, and pinging kernely people."
1777674,2018-10-09 16:46:50 UTC,"reboot is triggered using #systemctl reboot.
systemd timeout of 30min does not help, system stays hung. Needs a manual power-reset."
1777674,2018-10-04 14:55:33 UTC,"How is reboot requested/triggered?
Systemd has 30min timeout on the reboot, so things must timeout and force-self-reboot after 30min."
1777674,2018-06-19 16:05:16 UTC,"Logs where the hang is not seen:
<snip>
[   75.448494] kvm: exiting hardware virtualization
[   76.187482] reboot: Restarting system
[   76.191663] reboot: machine restart
[   76.197621] ACPI MEMORY or I/O RESET_REG.
</snip>"
1777674,2018-06-19 16:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777674,2018-06-19 16:34:21 UTC,"Moving the bug-report back to Confirmed since these logs like ""kvm exiting hardware virt"" and the logs post this are not stored on the physical disks (reason - disks are already unmounted).
Such logs are available only in the console logs which are already uploaded in this report."
1777674,2018-06-19 21:05:31 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].
1777674,2018-10-09 18:12:36 UTC,Could you please download and install https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702/+files/finalrd_3_all.deb
1777674,2018-06-20 05:57:18 UTC,I am observing that in the absence of any network (interfaces not configured for dhcp/static) I can see the graceful reboot halting almost every reboot.
1777674,2018-06-20 10:02:46 UTC,"I think I narrowed it down to these:
v4.14 - No issue observed
v4.15-rc-1 - Issue observed"
1777674,2018-07-16 07:55:24 UTC,Any update on this?
1777674,2018-06-20 05:12:51 UTC,"Update:
I was under the assumption that kvm/kvm_amd module was the suspect.
But I was wrong.
Reason - I tried performing '#modprobe -r kvm_amd kvm' before issuing '#systemctl reboot' in the reboot script and the system still halted with Ubuntu 18.04 kernel."
1777677,2019-01-04 14:32:44 UTC,"Thank you, Kyle! I was one of the testers as part of the MassLNC development initiative, so I will sign off:"
1777677,2019-01-14 19:36:06 UTC,"I just removed the signedoff tag.  As the ""admin"" user, I am able to send test SMS and Email messages as expected, but as a non-""admin"" user with the required OPAC_LOGIN permission, I am prompted with a permission override box saying that I need OPAC_LOGIN to proceed."
1777677,2019-01-15 18:52:29 UTC,Thanks for the feedback! I've pushed a new commit taking into account the recommended security improvements. It appears to work on my end when testing with the admin user and a patron user.
1777677,2019-02-06 21:13:38 UTC,"I've tested this on 3.2.3 and unless there are any other security improvements that need resolving, I am happy to sign off:"
1777677,2019-02-25 19:31:31 UTC,Removing signoff because permission referenced in Actor.pm should be VIEW_USER and not USER_VIEW.
1777677,2019-02-25 20:35:35 UTC,"Also noticed that when sending the test email message from the OPAC, the on-screen confirmation message is very confusing to an end user. See screenshot."
1777677,2019-02-25 20:40:35 UTC,Looks like there is a typo in templates/opac/myopac/test_notification.tt2 - [% l(a'n email') %] should be [% l('an email') %].
1777677,2019-02-26 17:13:28 UTC,I consent to signing off on Kyle's work along with two typo fixes included here:
1777677,2019-03-04 15:49:14 UTC,I think the latest branch still has at least one of the issues raised in the Jan 14 IRC conversation linked above in comment 22.
1777677,2019-01-04 01:29:29 UTC,"MassLNC testing complete, all OK from a functionality perspective."
1777677,2019-03-04 15:50:13 UTC,"Confirmed with Terran that she did not intend to remain the assignee, assigned myself."
1777677,2019-09-06 16:16:54 UTC,"Because the pending issue from comment 22 is a potential security issue, setting to needsrepatch."
1777677,2020-04-14 17:55:38 UTC,"Working branch user/jeffdavis/lp1777677-test-notification-method-restrict-hooks builds on csharp's last branch by restricting open-ils.actor.event.test_notification to the appropriate hooks, thereby hopefully resolving the outstanding issue from comments 22 and 30:"
1777677,2020-07-21 21:30:48 UTC,I've pushed a rebase to
1777677,2020-09-10 17:56:31 UTC,"Galen, has there been your requested review of this yet?"
1777677,2020-09-10 18:27:58 UTC,Ruth: not yet.
1777677,2020-09-11 19:56:25 UTC,"Given the relatively small size of my follow-up, I've gone ahead and merged this to master for inclusion in 3.6. Thanks, Kyle, Terran, Chris, and Jeff!"
1777677,2019-02-26 18:39:37 UTC,"Fixed-up, rebased branch with all the appropriate signoffs (including mine) located here:"
1777677,2018-12-12 21:28:55 UTC,"Thanks Jane and Terran. I've pushed an update resolving the 2nd and 5th issues Kathy brought up, as well as the addition of release notes, and with that, this feature should be ready for review."
1777677,2019-01-14 20:29:19 UTC,See also some IRC discussion about some recommended security improvements for this feature:
1777677,2018-12-12 18:19:12 UTC,"Thanks for your work on this, Kyle.  Just wanted to let you know that this feature will need some release notes as well.  Here's some how-to information about release notes: https://wiki.evergreen-ils.org/doku.php?id=contributing:release_notes"
1777677,2018-07-20 21:32:35 UTC,"Looking for some community input here, is there any reason we don't open up the SendEmail method(and other related methods) to be usable without action triggers? I understand there may be some benefits to using action triggers when it comes to logging messages that aren't sending, but are there any other benefits to this outside of having a configurable delay(which may be useful in some cases)? My thought process here is that we could just call the API for an instant or near-instant notification, but any pushback would be welcome."
1777677,2018-12-12 18:45:37 UTC,"Kyle - OPAC_LOGIN seems reasonable to me. I can't think of anyone that should be able to use this feature that wouldn't have that permission (at least, not in PINES)."
1777677,2018-07-26 21:06:57 UTC,"It's also possible to get real time A/T by calling the A/T API directly.  What's more, you can tell A/T to process specific events by ID.  The new code could create the test email event, then immediately tell A/T to process the event by ID.  See the 'open-ils.trigger.event.fire' API."
1777677,2018-08-10 15:59:42 UTC,"Bill,"
1777677,2018-09-17 17:16:09 UTC,I've pushed up a WIP branch here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1777677-test-notification-method
1777677,2018-09-21 14:53:44 UTC,"I've determined the above error was due to issues with the email template. I've since resolved those, should have some sql files pushed up soon. I've added a new commit to the branch that properly leverages $U->fire_object_event, and seems to be almost working. The issue now, I'm suspecting, is that it's not properly grabbing the org unit's email address. The patron.home_ou field doesn't seem to be fleshing, although I've attempted to manually flesh it. The event state returns as ""error,"" though no errors appear in the logs."
1777677,2018-09-21 20:31:52 UTC,"Additional commit made with the sql upgrade file, and my latest attempt at fleshing the target patron's home org unit. It does flesh, as evidenced by the logger lines I've placed just after fleshing, however it seems to unflesh prior to the event firing, resulting in an error related to the bounced_emails library setting(attempting to pass in target.home_ou.id when target.home_ou is the unfleshed id). If ""helpers.get_org_setting(target.home_ou.id, 'org.bounced_emails')"" is removed from the from lines of the templates, the event will fire with an error state, though the output's is_error field will be false. None of the information relating to the library will be visible, and editing the template to show the value of [% lib %] will display the id."
1777677,2018-10-15 16:36:08 UTC,"Kyle, I believe you need to add some environment variables to your new event definitions.  See for example: select * from action_trigger.environment where event_def = 1;"
1777677,2018-07-20 22:16:53 UTC,"In theory, by using action triggers, staff can review all past or pending notifications in a single, consistent place in the client, without having to ask a system administrator."
1777677,2018-10-22 22:01:46 UTC,"Thanks Bill, that helped quite a bit! As a general update on the issue's progress, I've updated the branch, and rebased to the latest master. It's still WIP, but the SMS and Email notification events are firing successfully from the patron edit screen. Next steps are to fire the action trigger event from the OPAC, and to determine where to implement the message customization."
1777677,2018-10-25 20:35:02 UTC,"A couple updates added to the branch. I'm having some issues on the OPAC side of things, specifically with the login session being either timed out or non-existent. My guess is that it's because I'm not passing through an authtoken, but I'm not 100% on that."
1777677,2018-11-01 21:10:15 UTC,"I was able to figure out the problem, and have since squashed and pushed my commits. So it doesn't get lost, the branch can be found here: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1777677-test-notification-method"
1777677,2018-11-23 16:18:04 UTC,Thanks Kyle! I like the feature! I found a few issues in testing.
1777677,2018-11-28 21:13:17 UTC,"Thanks for the feedback Kathy! I've pushed an update to resolve issues 3 and 4, and rebased the code to the latest master. I'm currently looking into a solution for issue #1."
1777677,2018-11-28 23:25:12 UTC,Another commit has been pushed addressing issue #1.
1777677,2018-10-15 16:36:58 UTC,... sanity check on $$args{event_def_type} needed as well.
1777679,2018-06-19 16:39:04 UTC,apport information
1777679,2018-06-19 20:59:02 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1777679,2018-06-19 21:18:09 UTC,"As stated in the bug description this was already tested on kernel 4.17, unsuccessfully."
1777679,2018-06-19 21:18:57 UTC,kernel-bug-exists-upstream
1777679,2018-06-19 22:30:16 UTC,Update: Bug seems to be related to i2c-hid
1777679,2018-06-20 15:22:08 UTC,"Update: Seems like the TouchPad is not to be found anywhere on my system.
I know that it is USB from the dmesg output however when I tried to see its usb descriptors with lsusb -vd I only saw reports for keyboard-related functions.
I cannot find the descriptors which would look like a touchpad."
1777679,2018-06-20 18:16:34 UTC,"Hi Maxime,"
1777679,2018-06-20 17:31:05 UTC,"I can confirm Maxime's solution works on my Asus FX73V which uses the Elan 1200 touchpad. I'm using gentoo with kernel 4.17.2, with all the relevant config options enabled (I2C, HID, ELAN, etc). I had 'acpi_osi=!' as a kernel parameter. Once I removed it the touchpad started working."
1777679,2018-06-20 22:55:09 UTC,"Thanks everyone, 4.17.2 seems to fix the problem. Did not need any acpi GRUB parameters and unblacklisted i2c-hid without any problems."
1777679,2018-06-25 16:26:47 UTC,Hi Gaston. This bug report was for the touchpad not being detected. I managed to get it detected by installing kernel 4.17.2 from kernel.org.
1777679,2018-06-23 15:34:52 UTC,I also have an AsusGL503VD with an ELAN touchpad listed by xinput as:
1777679,2018-06-19 16:39:02 UTC,apport information
1777679,2018-06-20 17:08:05 UTC,"Hi everyone,"
1777679,2018-06-19 16:39:00 UTC,apport information
1777679,2018-06-19 16:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777679,2018-06-19 16:38:57 UTC,apport information
1777679,2018-06-19 16:38:56 UTC,apport information
1777679,2018-06-19 16:38:54 UTC,apport information
1777679,2018-06-19 16:38:52 UTC,apport information
1777679,2018-06-19 16:38:49 UTC,apport information
1777679,2018-06-19 16:38:48 UTC,apport information
1777679,2018-06-19 16:38:45 UTC,apport information
1777679,2018-06-19 16:38:44 UTC,apport information
1777679,2018-06-19 16:38:41 UTC,apport information
1777679,2018-06-19 16:38:40 UTC,apport information
1777679,2018-06-19 16:38:58 UTC,apport information
1777683,2019-11-13 18:52:44 UTC,"Reviewed:  https://review.opendev.org/693745
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=6928d6ac987fac8a7f519ce546fc6e0b3da4080c
Submitter: Zuul
Branch:    master"
1777683,2019-01-07 17:14:05 UTC,Further:  the local loopback file approach is not recommended for production use cases.  The loopback approach is handy for testing.   The documentation should be clarified to represent these 2 points.  Thank you.
1777683,2019-11-11 19:57:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/693745"
1777683,2019-01-07 17:12:34 UTC,This is expected behavior.  The doc-fix that I would suggest here is to advise the reader that they may need to adjust block device config to match their own hardware/topology.
1777686,2019-11-05 21:45:33 UTC,"Reviewed:  https://review.opendev.org/693083
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=ede2ac0d234ee798327b7bb2d1de6fd7aec24b9e
Submitter: Zuul
Branch:    master"
1777689,2018-06-19 17:00:06 UTC,This change was made by a bot.
1777689,2018-06-19 21:02:41 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1777689,2019-06-19 00:56:22 UTC,I believe you need to specify the quirks mode for each entry.  So in your case...
1777697,2018-06-22 21:33:39 UTC,"Am 19.06.2018 um 20:15 schrieb Ervin Hegedüs:

> sudo dpkg --purge --force-all cqrlog
"
1777697,2018-06-19 18:15:41 UTC,"""Not possible to install any other programms at the moment."" - try to type:"
1777697,2018-08-12 19:16:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777697,2018-09-15 09:28:16 UTC,Check this link: http://www.bcat.eu/blog/remove-broken-package-ubuntu-debian/
1777698,2019-05-09 19:30:17 UTC,"A member of our staff found another workaround by backspacing one digit if the duplicate message appears and then retyping that one digit, then the barcode stays. This is a fast solution but again ideally we would rather not see this happen at all."
1777698,2019-05-09 20:22:27 UTC,I was curious if anyone that has encountered this bug have tried the following:
1777698,2019-05-09 21:37:50 UTC,One of the reasons we created the Use checkdigit default is to prevent incorrectly scanned barcodes. The barcode scanners PINES had at the time often did not scan the barcode correctly and either left a partial barcode or one with extra characters.
1777698,2019-08-12 18:27:12 UTC,"The duplicate check runs on every change, so if you scan ""123"" (depending on how your scanner works) it typically sends 3 checks: ""1"",""12"",""123"". But, the checks are asynchronous, so they don't always finish in order. So, if ""12"" is in the system and you scan ""123"", if the ""12"" check happens to finish last, it will indicate it's a duplicate."
1777698,2019-04-30 16:05:26 UTC,"I had forgotten I commented on this a year ago. After checking with my staff, everyone who catalogs is experiencing this issue. Initially people are concerned it's a scanner problem. This just slows up the workflow and then if we are trying to get a lot of work accomplished the tendency is to want to switch over to XUL. This happens whether we type in the barcodes or scan them."
1777698,2019-05-29 17:17:32 UTC,"We continue to experience this issue on 3.1.11 (Chrome, and I'm using a Honeywell MS3780 scanner), in the production environment."
1777698,2019-05-09 21:38:38 UTC,"PINES is not seeing the duplicate barcode error, by the way. We are on 3.2"
1777698,2019-04-08 17:37:34 UTC,"Second image, as referenced above in #7."
1777698,2019-10-21 13:43:52 UTC,"Thanks, Dan.  This is committed to 3.1 through master now."
1777698,2019-03-29 14:04:40 UTC,Our library staff is also encountering this issue. And all of the methods suggested above as work-arounds are being used.
1777698,2018-11-06 19:29:05 UTC,"I'm not able to make this happen on 3.2.0, but I am typing in barcodes -- my hunch is that John is on to something with his theory that scanner entry is ""too fast"" and the erroneous duplicate barcode message gets stuck somehow."
1777698,2018-10-10 17:08:50 UTC,We are encountering this issue in multiple SCLENDS systems (Evergreen 3.1.5).
1777698,2018-06-20 22:34:54 UTC,"Like John, when I encounter this issue I am usually able to fix it by clearing the barcode field, scanning a different unusued barcode, and then re-scanning the barcode I initially used. This allows you to continue on without closing or refreshing the page, but is still not ideal."
1777698,2018-06-19 21:39:37 UTC,We have had one report of this at CW MARS of which I am aware. I was under the working theory that the message comes from items incorrectly cataloged with partial barcodes.
1777698,2018-06-19 19:02:30 UTC,"Hello,"
1777698,2019-04-08 17:33:56 UTC,"I'm not sure if this qualifies as extensive testing (per Andrea's comment above), but I did some testing with typed vs scanned barcodes this morning. Evergreen 3.1.10, Chrome, Honeywell Fusion MS3780 scanner. The error appears randomly, so these results are not necessarily a hard and fast demonstration:"
1777705,2019-03-23 03:09:18 UTC,"@Kent Wu, why are you only cherry-picking to stable/pike?  Did the freezer team decided not to support Queens and I missed the memo?  I thought in order to be an Openstack project, there was some type of quality controls in place so that users were not using buggy code with incomplete documentation.  Realize that buggy code and incomplete documentation leads to wasted time for many."
1777705,2019-03-08 01:40:11 UTC,Was this fixed in Queens as well?  I'm receiving the same error:
1777705,2018-12-10 04:46:11 UTC,This issue was fixed in the openstack/freezer-web-ui 7.0.0 release.
1777705,2018-07-04 14:07:46 UTC,"Reviewed:  https://review.openstack.org/579713
Committed: https://git.openstack.org/cgit/openstack/freezer-web-ui/commit/?id=a712fd4fe7cade6caff2ea0da9272abd1e4d5fdd
Submitter: Zuul
Branch:    stable/pike"
1777705,2019-03-08 05:14:58 UTC,"Unfortunately, no. We only cherry-pick to stable/pike."
1777705,2018-07-02 11:45:04 UTC,"Reviewed:  https://review.openstack.org/576657
Committed: https://git.openstack.org/cgit/openstack/freezer-web-ui/commit/?id=40a07a0e003961b26a1a87172f796f75a215b917
Submitter: Zuul
Branch:    master"
1777705,2018-06-19 22:14:06 UTC,"Here's the proposed fix:
https://review.openstack.org/#/c/576657/"
1777705,2018-07-02 23:10:06 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/579713"
1777706,2018-06-19 18:59:26 UTC,Upgrading libmm-glib0 1.6.8-2ubuntu1 to libmm-glib0 1.7.990-1ubuntu1 makes mobile broadband not working as well.
1777706,2018-06-19 19:23:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777707,2018-07-01 10:59:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777708,2020-07-02 12:18:45 UTC,"The #33 advice works on ""19.10"" but not on ""20.04"" bringing the system into ""oh, no""-state."
1777708,2020-06-03 21:42:38 UTC,Is there another way to report this bug since it was opened quite long ago?
1777708,2020-06-02 15:56:58 UTC,"I have a Drevo BM87, running on Ubuntu 20.04, and the problem prevails.... I hope the issue can be fixed soon, because otherwise it renders the external keyboards pretty much useless."
1777708,2020-05-29 10:21:51 UTC,I just bought the R GO Split keyboard and experiencing the same issue on Ubuntu 20.04. Very unfortunate that it hasn't been solved yet.
1777708,2020-05-24 13:30:31 UTC,"For anyone looking for some closure, I doubt you'll see a fix for this anytime soon. So the best I can offer to you all is a little hack/fix you can do yourself. You can find it in the upstream bug over at gitlab."
1777708,2020-05-24 00:01:59 UTC,"In addition to the two-keyboards thing, I'm also experiencing this problem using the Sidewinder X4 keyboard when holding more than 6 simultaneous keys. According to xev, this keyboard also sends MappingNotify events when it gets to that point."
1777708,2020-03-15 14:55:23 UTC,"I'm having the same problem in Ubuntu 20.04 in XPS L502x.
I frequently use my laptop pluged in a external keyboard and mouse (logitech K270)"
1777708,2020-04-17 19:19:17 UTC,"This problem also affects me. I used the method of downgrading and it really worked. However, I don't know what I'm gonna miss out because of that downgrade."
1777708,2020-01-06 03:59:45 UTC,"I've the same issue in 19.10. Since I use Portuguese Brazil layout, I was able to circumvent this problem using the Pedro Palhares (Post #8) suggestion."
1777708,2019-11-20 14:23:34 UTC,works also without the init command
1777708,2020-07-03 15:16:27 UTC,Have the people on 20.04 tried #41 ?
1777708,2019-12-13 16:27:28 UTC,"Please use this Wiki-report at https://askubuntu.com/a/1195394/439867  with more details and evidences abiut this bug. Please more attention here, it affects many  testimony  and thousands of pageviews in the report's page."
1777708,2020-05-10 13:28:29 UTC,"I've created a $50 bounty: https://www.bountysource.com/issues/91397439
Please, support and spread the word for those who can help to fix this issue."
1777708,2020-07-05 06:07:26 UTC,I am using 20.04 & used this Workaround to fix it. Input lag is gone.
1777708,2020-11-01 23:57:52 UTC,I have updated to 20.10 and can confirm disabling scroll lock workaround is still working.
1777708,2020-07-15 11:06:26 UTC,"I'm using Ubuntu 20.04, and fixed this issue with the workaround by Wiggy boy <Lindholm> (Thanks!):
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1858#note_818548
(and I also had to enable the ""Source code"" source as explained here: https://askubuntu.com/questions/496549/error-you-must-put-some-source-uris-in-your-sources-list/857433#857433)"
1777708,2021-02-12 02:08:34 UTC,If you have any information about this bug then please put it in the upstream issue for the developers to see:
1777708,2021-02-11 14:09:41 UTC,"This issue still happens on Ubuntu 20.04. I use a laptop with Bluetooth keyboard. I couldn't use media keys like volume up and down due to the large delay. Even if I use the media keys in a single keyboard, the delay happens."
1777708,2021-02-11 09:15:58 UTC,"I got this too, comes out of nowhere, typing stalls for a second or two, sometimes the keystrokes are remembered, and typed a bit later, other times they're just dropped and i sit and look at the screen, then try typing and the letter shows up, very annoying for a developer."
1777708,2021-02-07 11:46:34 UTC,Hi :)
1777708,2020-12-17 17:13:39 UTC,On the Firefox issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1640535
1777708,2020-12-17 17:11:32 UTC,"Hey there, thanks for the discussion, it's helped me find a way around this problem."
1777708,2020-07-12 21:57:52 UTC,"Had Found this because [https://github.com/federico-terzi/espanso/] severely froze my desktop when expanding text snippets.
Disabling Scroll lock did solve it."
1777708,2020-11-02 02:00:46 UTC,"Nicolas,"
1777708,2020-10-30 13:22:44 UTC,"@vanvugt thanks for the tip.
Since disabling Ubuntu AppIndicators I didn't experience the problem."
1777708,2020-10-29 01:24:46 UTC,That's concerning. What if you open the Extensions app and disable 'Ubuntu AppIndicators'?
1777708,2020-10-28 23:41:29 UTC,In my case the problem was the Discord app. When it's open I get severe input lag (kb/mouse) on Chrome and other apps.
1777708,2020-10-28 23:26:47 UTC,"After updating to Ubuntu 20.10 the problem is back.
Brazilian ABNT2 keyboard layout."
1777708,2020-10-16 16:44:40 UTC,"Same issue here with R-Go split
Interestingly I found one configuration that works, but horribly breaks other things:"
1777708,2020-09-14 02:20:47 UTC,I use Ubuntu 20.04 and I have the same problem.
1777708,2019-11-05 22:21:55 UTC,Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1858
1777708,2019-11-04 18:55:11 UTC,"I know nothing about Linux/Ubuntu and how it works, but I'm also having this issue, with a R-Go split keyboard. I find it very cool that one can use 'xev -event keyboard` to get an idea of what's happening behind the curtain. And it made me research. According to this link: https://tronche.com/gui/x/xlib/events/window-state-change/mapping.html --- the MappingKeyboard appears, when the keyboard mapping was changed.. Which, without knowing anything about how this works, leads me to believe that something, somewhere, either believes the keyboards to be of two different mappings, or something is forcing them to be of two different mappings."
1777708,2019-11-20 14:22:32 UTC,One guy (Wiggy boy <Lindholm> Wiggy boy <Lindholm>) found a fix:
1777708,2019-10-17 08:18:19 UTC,"Actually this issue *is* affecting Ubuntu Mate 19.10, it's just not as noticeable but definitely there."
1777708,2018-06-19 20:25:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1777708,2018-06-20 08:36:20 UTC,"> It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it
"
1777708,2019-10-22 09:11:37 UTC,"This issue was fixed in Ubuntu 19.10. I switched from 18.04 to Eoan on 2th September and the bug was gone. Unfortunately one month later, somewhere around the beginning of October I upgraded my 19.10 system and the bug was present again. Awesome! :D"
1777708,2018-08-18 18:40:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777708,2018-08-20 13:42:30 UTC,"This bug can be easily triggered by typing with two keyboards, Everytime you switch from one keyboard to the other, there is a lag. If you type fast enough you can even freeze the application. Other way to trigger this bug is to use xbindkeys with xautomation, everytime i try to simulate keyboard typing, the lag is there."
1777708,2018-08-22 01:51:32 UTC,Same happens to me.
1777708,2018-08-22 10:26:38 UTC,"Now that other have marked themselves as affected, I'm trying to add a package, hoping that it will increase the chance that someone will look into it, although I'm not sure this is a Gnome bug (as mentioned earlier)."
1777708,2018-08-29 19:03:34 UTC,"After being annoyed by this bug for a long time, i started digging and found a workaround. Today i found that the bug is only present when i'm using certain keyboard layouts (""Portugues (Brasil)"") and was not present when i changed the layout to EUA and language to English (need to set them both to English)."
1777708,2018-08-29 19:09:30 UTC,"The only problem is the scroll lock key is no longer useful, but i dont use it, anyway."
1777708,2018-08-30 08:09:12 UTC,"Interesting findings, Pedro. How did you come up with that? What led you in this direction? Did you have a change to try this in Ubuntu yet?"
1777708,2018-08-30 11:20:32 UTC,Did you set the language to English as well? I've tried in Ubuntu and it worked as well.
1777708,2018-08-30 12:54:57 UTC,">Did you set the language to English as well?
"
1777708,2018-08-30 13:17:12 UTC,"> So, if you're hammering away on the keyboards at the same time, do you still get the freeze, even with your fix? (Please, test it!)
"
1777708,2018-08-30 13:26:09 UTC,"I realized if i set the layout ""Portugues (Brasil)"" without patching the file, the problem is even worse."
1777708,2018-08-18 17:14:11 UTC,"I'm glad I found this, because it affects me too. I have the Same problem in gnome, but the problem is not present in plasma. I tried gnome with other OS and the bug didn't occur either."
1777708,2018-09-10 06:57:20 UTC,"> I have exactly the same problem with an R-go split keyboard
"
1777708,2018-09-09 16:16:11 UTC,I have exactly the same problem with an R-go split keyboard. Makes Ubuntu basically unusable unfortunately. Changing the keyboard layout doesn't help anything.
1777708,2019-10-14 10:52:32 UTC,"This issue is not fixed in Ubuntu 19.10 (at least as of today). To reiterate this issue isn't present in Wayland, only Xorg. Also this issue was present for me in Kubuntu 19.10, but not in Ubuntu Mate or Xubuntu 19.10."
1777708,2019-09-08 11:29:05 UTC,I've bought a KeyMouse split keyboard and cannot use it because of this delay. Their support is aware of this issue but do not want to help fixing. https://www.keymouse.com/forum/large-lag-between-keystroke-and-response
1777708,2019-06-28 19:50:31 UTC,Maybe this helps to find the cause for this bug:
1777708,2019-06-08 20:50:14 UTC,"Same problem here. When I run htop while reproducing this bug, I can tell that shortly after the freeze, this command is using over 90 % CPU:"
1777708,2019-06-06 11:28:45 UTC,I have the same problem on 18.04. The trick mentioned above with removing scroll lock and changing input language seemed to make the delay smaller but still quite annoying. I am typing this in a Wayland session now and have 0 delay!
1777708,2019-07-18 17:36:13 UTC,"I have the same issue, but when using 1 keyboard and the xdotool. I use xdotool to input keypress like XF86AudioPlay, and others multimedia keys. This only happen when using the gnome. In wayland there is no such issue. The real keyboard does not have the multimedia keys. The system became shortly unresponsive everytime I switch from the real keyboard to the xdotool media keys, and vice versa."
1777708,2018-10-26 10:29:24 UTC,"I just upgraded from 18.04 to 18.10, and the problem is still there for me."
1777708,2018-10-15 08:32:21 UTC,"Dominik, unfortunately not something that doesn't involve replacing Xorg or Gnome. Maybe it's been unintentionally fixed in 18.10, but I haven't had the time to try the beta."
1777708,2018-10-06 12:55:37 UTC,I don't think that will be addressed soon (or at all). Has anyone found a working workaround yet?
1777708,2018-09-17 07:12:47 UTC,"To anyone responding to this issue because it also affects them: Remember to click ""This bug affects me"" at the top of this page, to increase the likelihood that somebody will dig into the problem some day. Thanks! :)"
1777708,2018-09-13 21:57:28 UTC,"I too have issues with keyboard input lag on Ubuntu 18.04. I've made sure I'm current on all updates, I'm using the US layout and my language is set to English."
1777708,2018-10-31 04:02:40 UTC,I bought a Logitech K840 mechanical keyboard couple days back I noticed the lag in 18.04 and 18.10 if I press a lot of keys at the same time. And I've verified that it only happens in GNOME. I haven't tried it in Wayland though. I didn't notice this issue with my previous bluetooth keyboard.
1777710,2018-06-21 15:33:19 UTC,"Ahah, gpg -K -v shows them... it seems to think they are all expired.  It lists the expiration date on my current key as 2018-1-6.  I believe that was the *original* expiration date, but then I extended it.  gpg 2.1 seems to be failing to recognize the extension."
1777710,2018-06-22 17:46:57 UTC,Would be nice if launchpad understood their bug tracker so it would link.  Whenever they do fix it we may want to cherry pick it so this doesn't bite other people upgrading to 18.04.
1777710,2018-06-22 16:25:28 UTC,"Oh wow. fail. I'm not sure it's worth tracking here, given it is an upstream issue. I guess we can set this bug to trianged."
1777710,2018-06-22 14:31:44 UTC,"Yea, the tripping point for me was that I was importing a single file with both private and public keys in it, and that wasn't fixing it.  The import has to be of *only* the public keys.  Hopefully upstream will fix that part so the upgrade ( which automatically does an export/import ) will then work correctly."
1777710,2018-06-22 13:26:23 UTC,"So yeah, my suggestion to reimport public key was right. It is an odd corner case. I think it has to do with something how the upstream choose to reorganize public & secret keyrings; such that the split of which bits need to be where is now different, and the export of old is either incomplete for what the new one wants or the new one does import all the right things during migration."
1777710,2018-06-22 12:43:16 UTC,"Here is the upstream bug report, which launchpad apparently does not recognize:"
1777710,2018-06-21 22:33:24 UTC,"Is the public key, with the new expiry date, and that selfsig, imported?"
1777710,2018-06-21 15:28:13 UTC,"So I went back to 2.0.31, deleted ~/.gnupg, imported my keys, made sure they all showed up, then upgraded to 2.1.1.  It converted to the new keybox format, and... my private keys are all gone."
1777710,2018-06-20 14:58:57 UTC,"can you provide commands to generate test keys/subkeys, to recreate this?"
1777710,2018-06-20 18:32:35 UTC,"I noticed something different about the new version of gpg is that I get a full screen prompt for my password when importing, but the old version does not do that."
1777710,2018-06-20 16:51:02 UTC,Generating a new keypair and exporting only the subkey and then importing it into 18.04 seems to work.  There must be something particular about my existing keychain.  I guess I'll have to start git bisecting.
1777710,2018-06-20 13:25:45 UTC,"The permissions are probably world readable because as I said, I tried deleting the whole directory and recreating it by hand, then copying the secring over from the working system.  This was after deleting the whole directory and letting gpg recreate it, then importing the keys exported from a working system.  Whether by import or auto conversion to the new format, gpg discards the private keys.  This may be because the primary key is not included because I normally keep that offline."
1777710,2018-06-19 22:34:36 UTC,what are the permissions of /home/psusi ? and /home/psusi/.gnupg ?
1777710,2018-06-20 19:02:49 UTC,So I cloned the upstream git repo and built 2.0.31 and it works.  2.2.4 does not.  Anywhere in the 2.1 area in between seems to have some protection turned out to tell you not to use production keys with a development branch and it refuses to import *any* secret key.  Any idea how to bypass this?
1777711,2018-06-19 19:28:58 UTC,may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1777706
1777711,2018-06-24 08:07:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777711,2018-06-25 22:44:26 UTC,"Looks like the same bug to me.
Ubuntu 18.04
Package: modemmanager
Version: 1.6.8-2ubuntu1"
1777712,2019-04-27 19:42:53 UTC,Is there a workaround for this?
1777714,2019-05-30 20:16:33 UTC,Added a new PR to fix a bug caused by the previous PR (324): https://github.com/juju/charm-helpers/pull/332
1777714,2019-06-03 19:53:25 UTC,"Reviewed:  https://review.opendev.org/657672
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=af051c4fba0b5ff2db62a908ab9fad688353750c
Submitter: Zuul
Branch:    master"
1777714,2019-05-17 15:45:28 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/659827"
1777714,2019-05-29 07:21:41 UTC,"Reviewed:  https://review.opendev.org/659827
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=206970c6c1302f235b569d6b1f194d002a1a2c9b
Submitter: Zuul
Branch:    master"
1777714,2019-05-17 16:15:57 UTC,PR https://github.com/juju/charm-helpers/pull/324 merged
1777714,2019-05-16 21:45:29 UTC,PR to charm-helpers: https://github.com/juju/charm-helpers/pull/324
1777714,2019-06-07 18:40:05 UTC,"Reviewed:  https://review.opendev.org/658394
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=a51efaf640b4138e3fd930fe6521ab6905bc2e0a
Submitter: Zuul
Branch:    master"
1777714,2019-05-14 12:14:22 UTC,"charm-nova-compute already has vendor-data config. Additionally, for all deploys using Queens or later, this configuration should be used rather than the neutron-gateway version."
1777714,2019-05-02 14:46:35 UTC,"This bug is still present when the cloud is deployed using DVR + L3HA. In this case, the metadata is served from the computes, and setting the config in neutron-gateway does not cause the change to propagate to the compute notes"
1777714,2018-07-18 11:52:24 UTC,"Reviewed:  https://review.openstack.org/577859
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=b355ea0473af5f1cf47c23ac5dadbeea52942bb0
Submitter: Zuul
Branch:    master"
1777714,2019-05-14 12:14:48 UTC,"Can you please include more details about what you're trying to accomplish, and with what versions of both OpenStack and the charms?"
1777719,2019-09-19 11:58:42 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1777720,2018-06-22 02:45:33 UTC,can add an extension to reuse flavor if exists
1777723,2018-06-19 20:31:15 UTC,"Although I don't disagree with the suggestion, we've been showing people how to use the browser toolbars to store their favorite links / sets of links, and that's served the purpose pretty well."
1777723,2019-05-24 10:02:25 UTC,I would also like to have an option of adding customized link that is not tied to a specific workstation/browser.
1777732,2020-07-23 21:16:44 UTC,I didn't understand why the subnet field was redundant and CIDR notation throws a validation error for IP address. The D-I based network config works for all possible options so why does this new validator do anything different?
1777732,2019-02-02 02:14:50 UTC,Yes this was annoying. I set 255.255.255.0 and had a 192.168.1.2/24 for the address and it said that axxress wasnt found in 255.255.255.0 but obviously it is part of 192.168.1.0-255.
1777732,2018-06-19 23:22:27 UTC,"IMHO, typing 24 is a lot simpler than 255.255.255.0, at a min, CIDR is less typing."
1777739,2018-06-19 23:24:49 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1761784, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1777739,2018-06-20 16:56:48 UTC,The link to the duplicate bug does not exists anymore.  It was https://bugs.launchpad.net/bugs/1761784.  I removed the link so this bug can be worked on.
1777739,2018-10-31 13:05:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777744,2018-06-20 00:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777744,2018-06-20 05:38:02 UTC,Unable to run apport-collect as the error occurs while PXE booting the kernel. A panic happens while loading the initrd and a shell is not available.
1777744,2018-06-20 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777744,2018-06-20 13:38:37 UTC,"Andres, this looks like an issue that got introduced by some security updates (see bug 1773162). The fix should be pending in the 4.15.0-24.26 kernel currently in -proposed. Is there any way to provide this kernel for testing via MaaS?"
1777746,2019-09-27 10:04:56 UTC,"Hi Li Zhouzhou,"
1777746,2020-03-24 21:55:25 UTC,"Due to lack of any activity in this RFE since more than 1 year, I'm going to close it for now. If You would be still interested in implementing this and would like to continue discussion on that, feel free to reopen it and ping me (slaweq) on irc."
1777746,2019-07-10 03:03:58 UTC,"@Miguel Lavalle (minsel)
Sorry, I'm too busy to forgot reply. I add this 'vlan-transparent' param for this patch: https://review.opendev.org/#/c/623980/. But it not seem to a bug."
1777746,2018-10-25 23:34:47 UTC,@Li Zhouzhou
1777746,2018-06-22 17:55:38 UTC,"The vlan_transparent attribute is not updatable according to the API (allow_put: False), so this is not a bug."
1777746,2018-06-28 23:23:18 UTC,Tagging as RFE while we await response from submitter
1777751,2018-06-20 02:27:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576679"
1777751,2018-06-24 15:01:54 UTC,"Reviewed:  https://review.openstack.org/576679
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=50cb6550bef8634aefe2a9d5cdbaec8474dd78a0
Submitter: Zuul
Branch:    master"
1777753,2019-12-01 22:42:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777753,2018-06-20 02:37:25 UTC,This looks to be https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863891
1777756,2018-06-20 03:05:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576690"
1777756,2018-06-20 03:23:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576694"
1777756,2018-06-20 03:24:30 UTC,"Change abandoned by miaoyuliang (<email address hidden>) on branch: master
Review: https://review.openstack.org/576690
Reason: repeated submit"
1777756,2020-03-24 07:27:13 UTC,"Change abandoned by miaoyuliang (<email address hidden>) on branch: master
Review: https://review.opendev.org/576694"
1777764,2020-01-30 15:15:49 UTC,"1. Documentation of 'auto' has been fixed meanwhile.
2. Complaint about rigidity of the 'load' config is still valid."
1777764,2020-07-10 02:11:43 UTC,"Check load has the parameter:
 -r, --percpu
    Divide the load averages by the number of CPUs (when possible)"
1777765,2020-03-06 08:52:38 UTC,Moved to P-P-C and re-opened so we can dig into this.  Not sure it's recreatable or not outside of arm but we have two things here:
1777765,2018-07-02 22:27:03 UTC,"I looked into this a bit and found it to be reproducible on this platform. I disabled the cloud-init service so that the guest OS would complete booting. I then manually ran ""cloud-init init"" to reproduce the hang, then attached strace to see where it might be hung."
1777768,2018-06-20 07:59:36 UTC,"The side effect is even worse for an archiver:
The archiving engine will either reject the value (because the timestamp is too old) or take the value, which creates wrong archived data (showing the new value as if it was set at the old timestamp)."
1777768,2018-06-20 20:12:55 UTC,"Would it make any significant difference if the link only posted a DBE_VALUE event and not DBE_LOG (or would that be even more confusing)? Does the Archive Appliance even use DBE_LOG for its subscriptions? I guess that wouldn't affect any channels archived using periodic ca_gets instead of monitors, but those channels are already seeing a new value with the old timestamp from a DB-link put with NPP, so I don't see a huge change here."
1777768,2018-06-20 21:39:52 UTC,Load this database:
1777768,2018-09-05 12:23:25 UTC,Core Group review at ESS: Post more information about the use-case or DB change that triggered this.
1777768,2018-06-20 20:33:24 UTC,I'm not sure I follow the situation which triggers mis-behavior.  Can you give an example?  I'd like to understand if this has any implications for my new PVA link code.
1777770,2018-06-20 05:00:52 UTC,https://review.openstack.org/#/c/576672/
1777773,2018-06-22 12:38:18 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1777776,2020-04-20 19:52:01 UTC,"I updated the guide at https://discourse.ubuntu.com/t/service-sssd/11579/ with a section on KDC spoofing, please take a look."
1777776,2018-08-06 17:52:46 UTC,"Any idea why upstream sets krb5_validate to false by default? I presume because this would require the extra step of creating a service ticket for the host where the login happened, if I understood it correctly?"
1777776,2018-08-06 17:56:47 UTC,"And, is sssd's krb5_validate option overriding krb5 library's verify_ap_req_nofail?"
1777776,2018-08-17 03:49:44 UTC,"I don't know why krb5_validate is false by default. I thought it was historical or to (dubiously) to make setting up easier, but I did some tests and found, to my surprise, that even with it not set, I could not log in without an /etc/krb5.keytab file."
1777776,2019-09-17 09:46:02 UTC,Has there been any progress on this issue? Thanks!
1777776,2020-04-20 13:40:06 UTC,"Hi Andrew, I'm back on this bug since I'm updating the server guide for the 20.04 release."
1777776,2020-04-21 14:06:29 UTC,"Thanks Andreas,"
1777777,2019-09-23 18:56:31 UTC,"Forgot to state the qemu argument, it's this one:"
1777777,2019-09-23 18:50:43 UTC,Sorry to have taken some time to answer.
1777777,2019-05-28 04:17:45 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1777777,2019-03-28 10:55:52 UTC,Mark this bug as Incomplete as we're still waiting for the test case binary and command line to reproduce it.
1777777,2018-06-20 17:10:19 UTC,Do you have a test case image you can provide that reproduces the problem?
1777777,2018-07-30 18:12:41 UTC,"Hello,"
1777777,2020-01-09 17:18:28 UTC,"Fix has been included in QEMU v4.2:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=5a65f7b5f4907ca70cb6"
1777777,2019-09-26 16:23:06 UTC,"Thanks for the repro case. Preliminary analysis: I added some tracepoints to the sp804 code, and you're right that the value of the interrupt status register isn't always correct:"
1777777,2019-10-04 12:29:58 UTC,"I sent out an initial RFC patchset which fixes this (it's just an RFC because it only converts this one device to the new ptimer API, and we should do a proper conversion of all devices); it seems to make the test case in this bug work correctly:
https://<email address hidden>/"
1777777,2018-07-30 18:38:48 UTC,"Sorry, I should have been clearer. Please can you provide a test case binary and QEMU command line that reproduces the problem (including what the expected output is and what the actual output is)?"
1777777,2019-09-27 06:01:07 UTC,Thank you for checking this issue.
1777779,2018-06-22 07:31:05 UTC,"This will hang with X-generic on AWS cloud as well, but not X-generic on our bare-metals"
1777779,2019-08-23 08:39:35 UTC,"This seems to be caused by bug 1775165, with fanotify07 blacklisted this was never occurred again."
1777779,2018-06-21 11:33:15 UTC,"Note that there is an issue with this, when the test gets killed, reports won't be copied to the jenkins server."
1777779,2018-06-20 14:08:51 UTC,"It will hang with Xenial AWS as well, I will update the bug."
1777779,2018-06-20 12:34:39 UTC,The same tests in the Xenial environment with the AWS kernel do work? Did the previous Trusty tests work (with the previous kernel)?
1777785,2019-11-02 03:15:06 UTC,Also see if it is a problem in 19.10 and master
1777785,2020-03-02 03:32:50 UTC,"I've tested with internal and SAML options, I can confirm it works for both of them."
1777786,2018-06-20 09:03:50 UTC,"Please don't use the bug tracker for providing patches, and send it to the mailing list instead, see: https://wiki.qemu.org/Contribute/SubmitAPatch"
1777786,2020-11-24 16:43:16 UTC,Did you ever send your patch to the mailing list for discussion?
1777786,2021-01-24 04:17:29 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1777788,2019-07-22 05:06:20 UTC,I can confirm that this also affects Xubuntu 18.04 with tcl/tk 8.5.  This ran apparently successfully:
1777788,2019-07-22 08:49:10 UTC,"Configured, built and installed successfully on Xubuntu 16.04 and Xubuntu 18.04 after installing tcl/tk8.6, but still needed explicit addition of -I/usr/include/tcl8.6 :"
1777789,2018-06-20 07:21:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/576767"
1777827,2019-02-03 18:44:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777834,2019-08-19 07:22:43 UTC,"Thanks, my issue was solved by  https://review.opendev.org/669592 !"
1777834,2019-07-08 03:21:31 UTC,I can confirm this issue on Openstack Queens when try to modify any image properties without metadata change.
1777834,2019-07-24 12:49:01 UTC,"Reviewed:  https://review.opendev.org/669592
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=ae1f4abd58f43911c6d8ff0490cb21ee658f6c1e
Submitter: Zuul
Branch:    stable/queens"
1777834,2019-02-28 14:58:17 UTC,"Unfortunately, I didn't find a patch with fix"
1777834,2019-10-22 20:06:52 UTC,This issue was fixed in the openstack/horizon 13.0.3 release.
1777834,2018-06-22 07:56:18 UTC,Reproduced issue in queens:
1777834,2019-02-28 14:36:25 UTC,I can't reproduce this bug on current master (Stein)
1777839,2018-07-03 20:30:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777847,2018-06-20 13:21:43 UTC,"Actually, wkhtmltopdf 0.12.5 still seems to have a bug in rendering sizes.
See https://github.com/wkhtmltopdf/wkhtmltopdf/issues/3969"
1777847,2018-06-21 08:57:28 UTC,"Response to earlier comment:
wkhtmltopdf 0.12.5 works as expected, using --disable-smart-shrinking option.
The older versions do not produce the correct output."
1777847,2019-05-21 13:05:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777847,2019-10-29 19:16:28 UTC,Thanks for reporting.
1777847,2019-10-29 19:20:01 UTC,"Short addendum: If you need a fix for specific bugs like the one mentioned in the description in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention."
1777848,2018-09-16 14:34:45 UTC,"gnome-screensaver-command --lock
does not work, but exits with 0 even if gnome-screensaver is running."
1777848,2018-09-16 14:34:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777848,2018-09-16 15:04:49 UTC,Running gnome-screensaver in debug mode led me to bug 864458.
1777853,2019-03-02 13:05:24 UTC,https://github.com/juju/juju/pull/9829 merges this into develop
1777853,2019-03-02 09:40:02 UTC,https://github.com/juju/juju/pull/9826 is the fix for 2.5
1777853,2019-03-02 09:28:45 UTC,"Just changing the size of the buffered channel to 10 prevents the test from failing after running 4000 times with the 'Sleep(1*ms)' in play.
With a buffer of just 1, the timer just needs to wake up before we notice the interrupt 1 time, with the bigger buffer, it needs to do so 9 times before it would fail."
1777853,2019-03-02 09:15:47 UTC,"All 3 of them were from this code:
  select {
  case <-pollAddresses.C:
   pollAddresses.Reset(opts.AddressesDelay)
   if err := inst.Refresh(ctx); err != nil {
    return """", fmt.Errorf(""refreshing addresses: %v"", err)
   }
   instanceStatus := inst.Status(ctx)
   if instanceStatus.Status == status.ProvisioningError {
    if instanceStatus.Message != """" {
     return """", errors.Errorf(""instance provisioning failed (%v)"", instanceStatus.Message)
    }
    return """", errors.Errorf(""instance provisioning failed"")
   }
   addresses, err := inst.Addresses(ctx)
   if err != nil {
    return """", fmt.Errorf(""getting addresses: %v"", err)
   }
   checker.UpdateAddresses(addresses)"
1777853,2019-03-02 09:07:37 UTC,"When it fails with that patch, this is the traceback:
PANIC: bootstrap_test.go:652: BootstrapSuite.TestWaitSSHKilledWaitingForDial"
1777853,2019-02-13 19:20:50 UTC,http://ci.jujucharms.com/job/make-check-juju/2987/testReport/junit/github/com_juju_juju_provider_common/TestPackage/
1777853,2018-08-20 04:20:47 UTC,[Expired for juju because there has been no activity for 60 days.]
1777853,2019-03-01 09:23:14 UTC,"Happened again
http://ci.jujucharms.com/job/make-check-juju/3356/testReport/junit/github/com_juju_juju_provider_common/TestPackage/"
1777863,2018-11-15 06:37:30 UTC,apport information
1777863,2018-11-15 06:37:31 UTC,apport information
1777863,2018-11-15 06:37:32 UTC,apport information
1777863,2018-11-15 06:37:33 UTC,apport information
1777863,2018-11-15 06:37:33 UTC,apport information
1777863,2018-11-15 06:37:34 UTC,apport information
1777863,2018-11-15 06:37:35 UTC,apport information
1777863,2018-11-15 06:37:37 UTC,apport information
1777863,2018-11-15 06:37:38 UTC,apport information
1777863,2018-11-15 06:37:39 UTC,apport information
1777863,2018-12-23 07:03:19 UTC,Does this still happen to latest mainline kernel v4.20-rc7?
1777863,2019-01-02 15:56:09 UTC,"I've updated the kernel to v4.20:
Linux citadel 4.20.0-042000-generic #201812232030 SMP Mon Dec 24 01:32:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1777863,2019-01-02 08:41:19 UTC,"I'm currently running latest Ubuntu version and it didn't happen to me for quite some time now:
Linux ZALANDO-27144 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1777863,2018-11-15 06:37:36 UTC,apport information
1777863,2018-11-15 06:37:28 UTC,apport information
1777863,2018-11-02 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777863,2018-11-15 06:37:27 UTC,apport information
1777863,2018-06-20 11:58:04 UTC,The lspci -vnvn output.
1777863,2018-11-15 06:37:28 UTC,apport information
1777863,2018-06-20 19:37:58 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1777863,2018-06-26 11:12:53 UTC,That doesn't seem to happen with  4.15.0-22-generic.
1777863,2018-06-27 12:44:53 UTC,I currently run on mainline 4.17.3-041703-generic #201806252030 SMP Tue Jun 26 00:33:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux and it didn't occur again. With the 4.15.0-23 I had up to 4 spontaneous reboots an office day.
1777863,2018-07-04 15:13:18 UTC,"Update, mainline kernel 4.17.3-041703-generic is also affected, only less frequent."
1777863,2018-06-20 12:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1777863,2018-11-02 11:25:29 UTC,I have this exact same issue. I have connected two displays (RGB and HDMI cables) I've updated from Ubuntu 18.04 to 18.10. Everything was working correctly in 18.04.
1777863,2018-11-15 06:34:31 UTC,Linux kernel: 4.18.0-11.12
1777863,2018-11-15 06:37:24 UTC,"ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  lubo       1623 F.... pulseaudio
 /dev/snd/controlC0:  lubo       1623 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-11-03 (11 days ago)
InstallationMedia: Kubuntu 18.10 ""Cosmic Cuttlefish"" - Release amd64 (20181017.2)
MachineType: LENOVO 20HGS27000
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-11-generic N/A
 linux-backports-modules-4.18.0-11-generic  N/A
 linux-firmware                             1.175
Tags:  cosmic
Uname: Linux 4.18.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/14/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET51W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HGS27000
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HGS27000:pvrThinkPadT470s:rvnLENOVO:rn20HGS27000:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HGS27000
dmi.product.sku: LENOVO_MT_20HG_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO"
1777863,2018-11-15 06:37:24 UTC,apport information
1777863,2018-09-03 04:17:31 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1777864,2021-02-17 17:08:26 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1777866,2018-08-01 12:51:24 UTC,"@Arkady: I checked the CLI in python-openstackclient, and now for --max-burst-kbits there is this help message:
""Maximum burst in kilobits, 0 means automatic"""
1777866,2018-09-16 10:28:43 UTC,"Reviewed:  https://review.openstack.org/591623
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=52f0096d13192aa35287e9f552c8245401dba087
Submitter: Zuul
Branch:    master"
1777866,2018-11-09 07:09:05 UTC,This issue was fixed in the openstack/python-openstackclient 3.17.0 release.
1777866,2018-08-15 08:39:21 UTC,https://review.openstack.org/588168 was merged to python-openstackclient
1777866,2018-08-14 11:07:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/591623"
1777866,2019-03-08 04:20:25 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1777866,2018-08-02 11:37:52 UTC,"I uploaded a patch for the help message extension, and marked as closes-bug, we can change that if the decision is to change the CLI behavior as well:
https://review.openstack.org/588168"
1777866,2018-08-01 18:56:47 UTC,@Lajos: I think that Your idea with adding such info to help message would be very good and simple solution for this issue. I'm fine with that.
1777866,2018-08-01 14:50:07 UTC,"@Arkady: back to your suggestion to add a validator or similar for max-burst-kbps value to check that is 80% of the max-kbps value (if set by the user) and
* give warning if not => that is possible as I see in python-openstackclient, but personally I don't feel that ""openstackish"", perhaps others have other opinion.
** this way the user should see a warning
** she/he can update the rule to change the burst value to 80% of the max-kbps."
1777866,2018-07-02 07:37:31 UTC,"Yes, these two issues are around the same QoS use case (80% Bandwidth), but there is no logical bond between them, so I want to track these bugs separately."
1777866,2018-06-24 14:05:58 UTC,"Such warning should be added in OpenStack client (if should be added at all).
Personally I don't think that it could be useful/necessary. Operator should read documentation and know about such limitations.
If this should be done in OSC then You should open bug report in storyboard (https://storyboard.openstack.org) instead of launchpad."
1777866,2018-07-01 08:39:14 UTC,"@Armando, correct me if i'm wrong, but it makes me feel like the main idea of this specific bug is getting lost :(
Do you think that we need this ""Warning"" message in CLI? Yes or No?
I think that we have to make the decisions previously to finding the best way to track it."
1777866,2018-06-26 07:54:14 UTC,In Launchpad there's no good way to link two bug reports and to keep the conversation in one place except making one report duplicate of the other. I imagined that any code changes would lead to documentation changes and that's why I proposed to mark one duplicate so that we can track whatever code/doc improvement in a single place. If you disagree please feel free to hit the - button on bug 1778407
1777866,2018-06-26 07:31:14 UTC,This bug is not duplicated to  https://bugs.launchpad.net/neutron/+bug/1778407
1777866,2018-06-25 15:21:50 UTC,"It seems this is related to bug 1778407. While I appreciate there may be two separate angles to the conversation, may I suggest we keep the discussion in a single place? This would help everybody interested in this topic to be informed and the same page."
1777866,2018-06-25 07:56:37 UTC,"I don't think that operators are 100% familiar with each parameter in command line (including notes) and i'm not sure that first thing operator will do, once desired BW is not reached, is searching notes in OSP documentation, they will probably think that QoS is not working. We can easily prevent them to think so, by adding this Warning message.
Correct me if i'm wrong, but I think that adding such functionality into the code is not something complicated.
Once we agree that this bug (RFE) is relevant, I'll open it on storyboard."
1777866,2018-06-24 07:48:57 UTC,"There are two notes in documentation regarding 80% Burst.
 1) Default - in case no value is provided for Burst, default will be set to 80% BW - I'm totally OK with it.
 2) Both BW and Burst are set by user in command line, for example:
openstack network qos rule create --type bandwidth-limit --max-kbps 3000 --max-burst-kbits 7 --egress bw-limiter
So in above command user is trying to set BW to 3000 and Burst to 7 (let's say he missed the note about 80% burst in documentation)
So, my suggestion is to add a simple validation of provided by user values and in case when burst is not 80% of BW to prompt user Warning message that will say ""WARNING - Burst should be 80% of your BW, desired BW won't be reached with BW 3000 and Burst 7"" (or something lie that)
In addition i think that we'll need to add ""Yes/No"" option, so user will be able to set the parameters anyway, in spite of WARNING message or to reset them."
1777866,2018-06-22 18:06:46 UTC,"For reference, this is what the admin guide says:"
1777866,2018-07-01 18:37:59 UTC,Just to make sure I understand your intentions correctly. You have been raising two issues around the same QoS use case:
1777880,2019-02-26 13:42:47 UTC,Is this still an issue?
1777880,2018-06-20 13:49:44 UTC,"This also means that we're failing to set 'httplog' in most cases, since many (most?) of the services provide a custom 'option' setting."
1777887,2018-06-22 16:08:08 UTC,forgot to add this detail: it seems the /var/lib/cinder/mnt parent folders all have ownership
1777889,2020-04-21 05:33:40 UTC,On 20.04 current
1777889,2020-10-24 06:05:02 UTC,"Upstream bug reports:
https://github.com/mate-desktop/mate-screensaver/issues/228
https://github.com/mate-desktop/mate-screensaver/issues/84"
1777889,2019-09-09 08:30:13 UTC,"Please ignore my comment #8, now hidden. I was incorrect in my terminology re ""menu"". I'm also finding what has been posted in comment #10 for the 19.10 release."
1777889,2019-09-08 23:02:55 UTC,On 18.04.03
1777889,2019-09-08 22:31:56 UTC,I can confirm that suspend locks on resume when closing lid. It does not lock when suspended from menu on 19.10 20190908
1777889,2019-10-01 20:27:01 UTC,On 19.10 current
1777889,2018-11-12 15:56:47 UTC,I can reproduce this all the time on Ubuntu MATE 18.10.
1777889,2019-02-18 12:07:20 UTC,I can also confirm this for my installation of Ubuntu MATE 18.10.
1777889,2018-07-27 01:29:23 UTC,Additional information. Same issue when running sudo pm-suspend.
1777889,2018-07-27 01:23:38 UTC,I can confirm this too.
1777889,2018-06-21 08:15:56 UTC,"Yes, that's what I mean. It happens when I suspend manualluy too."
1777889,2018-06-21 06:26:37 UTC,"Do you mean when waking up from ""suspend""? I'm facing the same issue when waking up from suspend. Can you make sure by going into the suspend mode manually by clicking on it and then waking up?"
1777889,2018-07-27 06:09:36 UTC,"When I suspend by closing the lid and then open, I can see my desktop for 2-3 seconds before password dialog shows up. I wanted to file that bug (and I will) when I found this one. So I tried manual suspend and I can also see I don't get password prompt when I un-suspend after manual suspend.
18.04"
1777895,2018-06-22 14:51:02 UTC,There looks to be a pull request on the pam_script git repo that fixes this issue:
1777897,2020-02-26 22:35:01 UTC,Marking as Won't Fix for 2.3 and 2.4 series since we are not planning to make any further releases in these series at this stage.
1777897,2018-08-03 15:14:52 UTC,"adds a cloud certificate to juju add-cloud interactive
https://github.com/juju/juju/pull/9015"
1777897,2018-08-03 12:54:37 UTC,Related to #7
1777897,2018-07-25 20:50:54 UTC,Related to #7
1777897,2018-07-25 11:09:49 UTC,https://github.com/juju/juju/pull/8972
1777897,2018-07-19 19:40:49 UTC,"Adding the ability to create a client with a certificate to goose with pr:
https://github.com/go-goose/goose/pull/63"
1777897,2018-06-27 15:49:21 UTC,In speaking with the OpenStack team Juju will look to add a new OS_CACERT cloud config option that can be used to inject that. It'll require changes to the provider and a new release of Juju so it'll be a little bit coming.
1777897,2018-06-20 17:09:21 UTC,"during interactive juju add-cloud, juju attempts to find out what identity versions the open stack supports.  no open stack credentials are used, or should be needed to do so, equivalent to the 'wget  https://10.12.12.120:5000'"
1777897,2018-06-20 17:05:07 UTC,The novarc file contained a env var that juju doesn't use currently:
1777897,2018-06-20 21:06:33 UTC,"The workaround hear turns out not to work. We run into the same error when attempting to run ""juju bootstrap""."
1777899,2018-06-20 16:09:13 UTC,JFTR: This is already fixed in zsh 5.5.1-1ubuntu1 in cosmic (as that commit was included in the upstream 5.5.1 release).
1777901,2018-06-25 07:26:11 UTC,You can discard this bug report !
1777905,2018-06-20 19:42:07 UTC,**waving hands** We probably want to adjust both the initial server-side query construction to separate system and user supplied components (there's a syntactical mechanism for that spelled with {'s) and enhance the query canonicalization done by the storage service so that it can provide the user-typed portion separate from the constructed part.  Then we can display only the user-typed part in the text box.
1777908,2018-06-22 19:17:01 UTC,"Change abandoned by boden (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/577208
Reason: reverted the right way"
1777908,2018-06-22 19:17:31 UTC,"Change abandoned by boden (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/576940
Reason: in favor of https://review.openstack.org/#/c/577513/"
1777908,2018-06-21 15:02:16 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/577208"
1777908,2018-06-21 15:02:37 UTC,Ocata revert here: https://review.openstack.org/#/c/577208/
1777908,2018-06-21 14:36:09 UTC,@Boden: this was proposed and already merged also to Ocata: https://review.openstack.org/#/c/573620/1 so probably we will have to revert it there too.
1777908,2018-06-20 19:11:33 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/576940"
1777908,2018-06-20 18:58:58 UTC,"An example failure can be seen in [1].
I will try a sample patch to revert the neutron change in queens and see if it fixed [1] (just to be sure)."
1777908,2018-06-20 20:18:04 UTC,Based on http://logs.openstack.org/25/576925/2/check/openstack-tox-py27/e3552ca/testr_results.html.gz it appears the revert fixes the test failures.
1777909,2018-06-21 13:39:06 UTC,We are on the 3.0.2 web client and I am able to successfully create a new billing type.
1777909,2018-07-13 14:53:11 UTC,We are experiencing this issue as well when trying to delete old billing types and creating new billing types.
1777909,2019-01-22 16:49:09 UTC,"I tested this on the latest master and was able to freely add and delete billing types as long as I had the proper permission(s) to do so for that Org. Unit. Dojo will fail silently if the staff user is not allowed to perform a specific action - you will see a console error being logged (ex: ""VM2218:297 Uncaught _CUD: Error creating, deleting or updating {""__c"":""cbt"",""__p"":[""101"",""Misc"",""1"",null,null,null,null]}"")"
1777910,2018-06-25 15:14:30 UTC,TLDR - the prototype role yields this:
1777910,2018-07-10 15:21:56 UTC,Work to be considered after zuulv3 migration is done... keep pushing out until that time.
1777910,2021-02-17 17:08:29 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1777920,2018-07-21 07:28:53 UTC,i find an other case   with theses words
1777923,2020-03-28 17:06:20 UTC,Closing because INVALID: Can't replicate -- No deformation occurs when importing an svg (include/embed/link).
1777924,2018-11-13 22:13:50 UTC,Would nice to have this backported.
1777925,2018-06-26 07:57:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1777933,2018-06-27 15:08:25 UTC,"I have been able to reproduce this on amd64 and i386 using the zero package. I tried to reproduce it on a powerpc vm but as I was unable to boot anything other than a single-core vm, which was way too slow to do any testing - just the ubuntu install took way too long, there would be no way I would be able to rebuild openjdk and be testing fixes from there."
1777938,2019-03-04 18:20:23 UTC,Nevermind: it seems to be sticky in 3.2.3. Scratch Comment 1
1777938,2019-03-04 18:19:09 UTC,Still a problem in 3.2
1777938,2019-03-04 18:13:40 UTC,Appending this checkbox to the list of non-sticky:
1777940,2018-11-28 14:57:22 UTC,"There is something of an internationalization question with this.  I know that few countries use more than two decimal places in their currencies (a handful that use dinars do) so in a perfect world it would be nice for Evergreen to be more aware of varying currencies.  However, that would also be a good bit of work to accommodate users that if they are using Evergreen aren't active in the community.  Not that the rounding current behavior still isn't working for them.  Should we take the easy road on this and just say we only accept two decimal places?  I've talked myself around to the idea that we should until someone with the vested interest for otherwise has the tuits but wanted to propose the wider question in case anyone wants to weigh in otherwise."
1777947,2019-08-12 20:22:43 UTC,Still an issue in 3.3
1777959,2018-06-21 06:50:59 UTC,"I am not sure if all ERC rules are settable, but you should definitely check out the 'Options' tab in the ERC dialog. It should make your life easier in the meantime."
1777960,2018-06-26 16:05:29 UTC,"C:\Users\101150.WIN\AppData\Roaming\bazaar\2.0>bzr explorer
bzr: ERROR: bzrlib.util.configobj.configobj.ParseError: Invalid line at line ""1""
."
1777960,2018-06-26 16:19:33 UTC,"I was able to resolve my issue after finding ""https://bugs.launchpad.net/qbzr/+bug/723691""."
1777960,2018-06-26 16:26:46 UTC,Unable to guess at what caused this. Hopefully not caused by virus scanner required here.
1777965,2019-12-19 14:41:15 UTC,This issue was fixed in the openstack/neutron 14.0.4 release.
1777965,2019-12-19 09:20:16 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/699938"
1777965,2019-12-19 14:39:41 UTC,This issue was fixed in the openstack/neutron 13.0.6 release.
1777965,2019-12-19 14:42:55 UTC,This issue was fixed in the openstack/neutron 15.0.1 release.
1777965,2020-02-21 16:42:18 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1777965,2020-07-14 14:33:00 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/740977"
1777965,2019-12-19 04:38:24 UTC,"Reviewed:  https://review.opendev.org/699193
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2084585b81649b2afa747e24f036d54e5e16e90e
Submitter: Zuul
Branch:    stable/queens"
1777965,2020-09-25 15:40:31 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/740977
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1777965,2020-01-22 21:04:29 UTC,"Reviewed:  https://review.opendev.org/699938
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8e88ae8dc32239a21985d331ec25641f0a4757a5
Submitter: Zuul
Branch:    stable/pike"
1777965,2019-12-16 11:28:40 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/699193"
1777965,2019-09-19 12:24:53 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/683128"
1777965,2019-12-09 12:17:34 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/698002"
1777965,2019-11-27 03:52:37 UTC,"Reviewed:  https://review.opendev.org/695351
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ff810fcd80af8054763b0751e1309944d39bbc81
Submitter: Zuul
Branch:    stable/train"
1777965,2019-11-23 02:02:49 UTC,"Reviewed:  https://review.opendev.org/695352
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3ec7aed8a367ba2a44fed300b08797e02fc47e06
Submitter: Zuul
Branch:    stable/stein"
1777965,2019-11-21 06:38:49 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/695352"
1777965,2019-11-21 06:38:31 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/695351"
1777965,2019-11-20 13:41:01 UTC,"Reviewed:  https://review.opendev.org/683128
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ab286bcdaccb788ab9df3186e0605e93a9b10bbc
Submitter: Zuul
Branch:    master"
1777965,2018-06-26 01:23:26 UTC,"Similar bug:
Deadlock with quota when deleting port
https://bugs.launchpad.net/neutron/+bug/1771293"
1777965,2019-12-09 18:12:54 UTC,"Reviewed:  https://review.opendev.org/698002
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=22250e783b194b9d188268c0d301581d73bd430d
Submitter: Zuul
Branch:    stable/rocky"
1777976,2019-08-08 07:19:05 UTC,have any updaye?
1777978,2018-07-23 13:48:13 UTC,"Reviewed:  https://review.openstack.org/556580
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=fb1b29e74ae7bfe30894fc0a0b840da697fecaee
Submitter: Zuul
Branch:    master"
1777978,2018-07-23 15:29:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/584940"
1777978,2019-03-06 18:52:08 UTC,"Reviewed:  https://review.openstack.org/584940
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=fdff1ffa5c64b4898f25cb99bbe6001ebcab3321
Submitter: Zuul
Branch:    stable/queens"
1777978,2019-03-06 22:18:19 UTC,Cheak ...
1777984,2020-07-30 15:03:11 UTC,"Hi, thanks for reporting. We're moving our bugtracker to GitLab, and I've closed this issue in favour of https://gitlab.com/inkscape/inbox/-/issues/1363 (on GitLab), where it was reported again."
1777989,2018-07-08 14:23:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778001,2019-09-16 14:03:25 UTC,Migrated to https://github.com/widelands/widelands/issues/2105
1778002,2020-07-23 20:48:28 UTC,"I just hit this again, this handoff partition is almost empty:"
1778002,2019-03-05 18:35:35 UTC,"I was wrong, the ""un-durable data frag can't be reverted"" bug is NOT fixed:"
1778002,2019-03-05 18:01:41 UTC,Same symptoms as described in lp bug #1816501 (or the earlier incomplete fix for lp bug #1706321)
1778002,2018-06-21 16:55:57 UTC,Some maybe-related bugs:
1778003,2020-09-09 15:33:51 UTC,"Scenario are full tests in a meaning they test several features which should be able to interact together (output of one feature is suitable for another one, etc). The mentioned scenario tests cold migration of a server from the beginning (creating a network, floating ip, server ..) until the end (the server is migrated). Therefore it creates its own network regarding the fixed_network_name. Also in the help of the option is written ""... this is the network which will be used for creating servers if tempest does not create a network ..."" [1]."
1778003,2020-11-09 04:17:18 UTC,[Expired for tempest because there has been no activity for 60 days.]
1778010,2018-06-21 08:58:01 UTC,"The end result is that 3 out of 3 nova instances got deleted, but only 1 out of 3 cinder volumes were deleted."
1778011,2018-12-08 20:32:31 UTC,"@Chris, Thanks for your reply. I know, my point is a bit different. If I set the bios to discrete only, I get an HDMI signal. If I set the bios option to hybrid, I can use prime-select to switch between intel and nvidia but in both cases I cannot use HDMI anymore and in both cases power consumption is at a rate of above 20W, essentially emptying my battery within 2-3 hours."
1778011,2018-12-10 15:09:10 UTC,"@Krzysztof: The NVIDIA GPU is more powerful, but also more power hungry than the Intel GPU. This is why you are seeing such a high power consumption."
1778011,2018-12-10 15:12:43 UTC,"@Gregor: that shouldn't be an issue any more, assuming that you are using the latest updates, and that you are using the nvidia driver from the ubuntu archive."
1778011,2019-01-09 10:32:16 UTC,@Dan: I would like to see your /var/log/gpu-manager.log when in power saving mode.
1778011,2018-11-28 13:26:37 UTC,"@janowicz The HDMI port on the Thinkpad X1 Extreme is physically connected to the Nvidia chip, so it ONLY works if you are using the Nvidia card, not the Intel Integrated graphics."
1778011,2018-12-31 23:52:00 UTC,Thinkpad w530. Still looks like the nvidia gpu isn't turning off. bionic+lightdm+unity7. Log attached.
1778011,2018-12-10 20:45:20 UTC,"I'm still experiencing high power consumption with GDM3 on Cosmic with 0.8.10 of nvidia-prime. Can provide logs/hardware info if it's helpful, just let me know what you need. Nouveau or manually disabling the DGPU in the BIOS behaves as expected."
1778011,2018-11-20 18:29:32 UTC,@Alberto: Thanks a lot for your help! There is no such setting in the BIOS of the Thinkpad X1 Extreme. I can either select discrete only or hybrid cards. I was finally able to get prime-select to switch to intel but the rate remains at like 20W which is essentially the same as using the nvidia card. I am also not able to connect to an external screen via the on-board HDMI port which is another issue I never had to deal with in a Thinkpad (usb-c to HDMI adapter does not work as well).
1778011,2018-11-10 16:49:48 UTC,@Alberto: here you go. The card is a GeForce GTX 1050 Ti with Max-Q Design/PCIe/SSE2 in a Thinkpad X1 Extreme.
1778011,2018-11-17 00:22:43 UTC,My gpu-manager.log (Intel selected)
1778011,2018-11-15 12:01:59 UTC,Sorry wrong file this is the file with the $ prime-select intel
1778011,2018-11-15 11:39:38 UTC,@albertomilone  here is my gpu-manager.log this is a fresh install and all updates have been made
1778011,2018-11-12 14:35:05 UTC,"@Fernando: we don't support hybrid graphics without using a display manager, as that would prevent gpu-manager from running at the right time."
1778011,2018-11-10 09:30:24 UTC,"For me the power management isn't working, too.
The fan is always running and my notebook is getting hot."
1778011,2018-11-10 15:14:31 UTC,"Hi Alberto,"
1778011,2018-11-09 19:20:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778011,2018-11-19 19:04:53 UTC,"Hi,"
1778011,2019-01-09 10:32:39 UTC,"also, we do not rely on bbswitch any more."
1778011,2018-11-17 00:07:32 UTC,"My laptop is MSI GE60 0NC
CPU: Intel i5-3210M, GPU: NVIDIA GeForce GTX 660M
Running Kubuntu 18.10"
1778011,2019-01-12 04:54:16 UTC,"Attached powertop images. I'm not sure how accurate powertop's values and distributions are. With prime-select intel, the total estimated power remains high although it doesn't attribute it to nvidia. bbswitch also stays on. I've also attached a bbswitch off capture after prime-select intel. That actually seems to turn the gpu off. There's also a default capture with nouveau drivers (i.e., the nvidia gpu is not in use). There are a few other issues with prime-selct too. prime-select intel glitches the lightdm login screen. You can't see the text entry field. prime-query is also not accurate always. Sometimes it says it's nvidia, but nvidia drivers are not loaded."
1778011,2019-05-11 00:32:33 UTC,The issue persists on 19.04.
1778011,2018-09-20 07:30:45 UTC,@Aurelijus: please follow these steps for testing:
1778011,2019-03-29 20:28:11 UTC,"Is there a way to test this patch with the 418 driver? I have an RTX 2070, which is not supported by the 390 driver, but I'd really like my battery life back."
1778011,2019-03-16 10:22:30 UTC,"After seeing Alex's post, I tried installing 410.104-0ubuntu0~18.10.1 from ppa:graphics-drivers.
Using 4.18.0-16-generic kernel."
1778011,2019-03-10 13:03:46 UTC,"With kernel 4.18 and 410.104 drivers, it seems to work properly for me."
1778011,2019-03-09 00:44:45 UTC,"@Alberto I'm afraid I have to add to the pile of users reporting issues here. Kernel 4.20.14 with 418.43 drivers. Ubuntu 18.04.2 LTS, on an X1 Extreme."
1778011,2019-03-07 22:07:11 UTC,"After spending some more time with this, I can confirm that this is definitely a regression. Both nouveau and the old bbswitch based method in 16.04 were able to power off the nvidia card successfully when not in use. The current implementation of prime-select in 18.04 doesn't do that. It may be that this is card or ACPI specific, but my hardware is fairly old (2012 ivybridge with kepler GPU), and it doesn't work for it."
1778011,2019-03-04 00:49:17 UTC,"@Alberto, with prime-select intel as well as with bbswitch off, powertop shows the nvidia tunable as ""good"". Still, the battery's discharge rate on idle remains pretty high (around 20W) on prime-select intel. With bbswitch off, it drops to 13W or thereabouts. Do you need any more information ?"
1778011,2019-03-01 13:48:30 UTC,"@dustya
Thanks a lot for the feedback. I think that I will install both operating systems on the laptop, and check what happens."
1778011,2019-03-01 13:24:02 UTC,"> * If I understand correctly, the bug does not occur in Ubuntu 18.10. The user can switch seamlessly between using the Intel or the Nvidia discrete graphics card. Is this correct?
"
1778011,2019-02-27 10:31:48 UTC,"I am very interested on the status of this bug, since I am considering which version of Ubuntu to install. I have just 3 questions about it:"
1778011,2019-02-16 11:49:48 UTC,I observed the same behaviour as Adrian S..
1778011,2019-01-31 18:47:01 UTC,"I can confirm that installing nvidia-390 through the Ubuntu driver dialog, and then using nvidia-settings or prime-select to set intel keeps the nvidia card on for me on my GeForce 840M laptop.
I can also confirm Installing bbswitch-dkms and turning it off through bbswitch works."
1778011,2019-01-30 02:12:28 UTC,I noticed off a clean boot on Intel gpu-manager.log was different from when I just logged out and logged back in so I'm attaching that file now.
1778011,2019-01-30 02:06:45 UTC,@Alberto:
1778011,2019-01-14 14:19:32 UTC,"@Fink: I would like to see powertop when you don't use bbswitch (and the Nvidia GPU is on). More specifically, I would like to know if you can disable the Nvidia GPU using the ""Tunables"" tab from powertop."
1778011,2019-01-14 14:13:15 UTC,Pe4enko: Here is your problem:
1778011,2019-01-11 00:16:39 UTC,"Should it work on ubuntu 18.10? I try to install 390 driver. After this i run command
sudo prime-select nvidia and restart system. But GUI no work anymore. In kernel log i see errors.
My video card is geforce 750M"
1778011,2018-09-19 19:26:55 UTC,Running a Quadro M2000M here.
1778011,2018-09-06 07:47:38 UTC,"Hello Alberto, or anyone else affected,"
1778011,2018-09-19 12:58:04 UTC,"Hello Alberto, or anyone else affected,"
1778011,2018-08-20 15:27:52 UTC,"Software rendering is a better bet if DKMS fails, as nouveau can cause
problems when dealing with (partially?) supported GPUs. I introduced that
change in bionic, but then I reverted that behaviour, also because it would
cause problems to hybrid graphics."
1778011,2018-08-20 15:06:07 UTC,(waiting with the other packages until Steve's concerns are addressed)
1778011,2018-08-20 14:40:33 UTC,"Hello Alberto, or anyone else affected,"
1778011,2018-08-16 08:22:54 UTC,"just to give some feedback, I have a optimus laptop with i7 sandibridge and nvidia GT550M, there is a led that indicates the nvidia GPU is always in use also after using the ppa to test, the laptop is indeed very hot also after I select intel and reboot and the led indicates that the nvidia GPU is in use despite selecting intel."
1778011,2018-08-15 22:29:25 UTC,Bug description says:
1778011,2018-08-15 21:15:27 UTC,"An upload of ubuntu-drivers-common to bionic-proposed has been rejected from the upload queue for the following reason: ""contains change to systemd service with no bug reference; https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/comments/10""."
1778011,2018-08-15 21:15:03 UTC,"Reviewing ubuntu-drivers-common in the queue, I notice:"
1778011,2018-08-20 15:29:06 UTC,I am going to have a look at this soon.
1778011,2018-08-02 16:42:25 UTC,This bug was fixed in the package gdm3 - 3.28.2-3ubuntu4
1778011,2018-07-31 15:57:15 UTC,This bug was fixed in the package nvidia-prime - 0.8.9
1778011,2018-07-14 14:20:18 UTC,"This bug also affects me.
I am running Kubuntu 18.04 on Gigabyte AERO14, CPU:i7-7700HQ (45W TDP), GPU:Nvidia 1050Ti"
1778011,2018-07-13 09:33:02 UTC,"@fargoth: you can disable gpu-manager by passing the ""nogpumanager"" boot parameter. Wouldn't this work for you?"
1778011,2018-06-23 20:36:32 UTC,"Can we have an option to switch to the iGPU, but keep the nvidia card powered and its modules loaded so that it can be used for CUDA calculations?"
1778011,2018-06-21 23:01:35 UTC,@André
1778011,2018-06-21 22:09:31 UTC,"Hey, Alberto. I have a few questions:"
1778011,2018-06-21 09:02:01 UTC,"Here is a PPA with the current code for Bionic, available for testing:
https://launchpad.net/~albertomilone/+archive/ubuntu/hybridgraphics?field.series_filter=bionic"
1778011,2018-08-02 15:27:57 UTC,This bug was fixed in the package ubuntu-drivers-common - 1:0.5.3
1778011,2018-08-27 11:08:21 UTC,@monogato: please give us time to get all the components into the -proposed repository first.
1778011,2018-08-26 20:51:39 UTC,I agree with #13
1778011,2018-09-06 07:38:30 UTC,"Hello Alberto, or anyone else affected,"
1778011,2018-09-09 01:33:45 UTC,"nvidia-prime 0.8.8.1, everything else updated. After selecting intel and rebooting NVidia drivers still loaded."
1778011,2018-09-07 00:28:37 UTC,I've done 2 tests on 2 different machines.
1778011,2018-09-06 22:00:21 UTC,I'm still seeing cruft in _pycache_ with the latest upload of ubuntu-drivers-common.
1778011,2018-09-19 15:32:32 UTC,"Hello,"
1778011,2018-08-27 12:52:23 UTC,"On Wed, 15 Aug 2018 at 23:20, Steve Langasek <email address hidden>
wrote:"
1778011,2018-09-18 08:28:35 UTC,"Hi Alberto,"
1778011,2018-09-10 08:25:10 UTC,@Serhiy Zahoriya: sorry but ubuntu-drivers-common (1:0.5.2.1) doesn't seem to be in bionic-proposed yet. No wonder things failed.
1778011,2018-09-06 00:17:41 UTC,"Hello Alberto, or anyone else affected,"
1778011,2018-08-28 06:31:28 UTC,"On Mon, 27 Aug 2018 at 23:01, Mikhail Novosyolov <email address hidden>
wrote:"
1778011,2018-08-27 20:55:48 UTC,"--- /tmp/nvidia-fallback.service.orig	2018-08-27 23:52:21.739079571 +0300
+++ /tmp/nvidia-fallback.service	2018-08-27 23:55:14.674338550 +0300
@@ -1,7 +1,8 @@
 [Unit]
-Description=Fall back on nouveau if nvidia is not loaded
+Description=Fall back on nouveau if nvidia is not loaded and PRIME not switched to integrated GPU
 Before=display-manager.service
 ConditionPathExists=!/sys/module/nvidia
+ConditionPathExists=!/etc/modprobe.d/blacklist-nvidia.conf"
1778011,2018-08-27 20:46:50 UTC,"Also, something, probably prime-select, adds nouveau.runpm=0 to GRUB_CMDLINE_LINUX_DEFAULT"
1778011,2018-08-27 20:43:36 UTC,"Sorry, I have read above and understood why it's needed. I think prime-select can leave a dummy file somewhere and systemd service nvidia-fallback should be loaded when there is no this file written by prime-select."
1778011,2018-08-27 20:41:42 UTC,Can you please explain why is nvidia-fallback needed? It worked without it before.
1778011,2018-08-27 20:39:48 UTC,My hardware: Probe URL: https://linux-hardware.org/?probe=572f1e3e6a
1778011,2018-08-31 15:36:14 UTC,Is it already fix in proposed?
1778011,2018-09-10 10:37:22 UTC,"@Steve, Brian: I have re-uploaded ubuntu-drivers-common 1:0.5.2.1, now with code to prevent shipping the __pycache__ cruft. While running debdiff against 1:0.5.2 will still mention the cruft, if you run ""lintian -v ubuntu-drivers-common_0.5.2.1.dsc --pedantic"", lintian won't complain about ""source-contains-prebuilt-python-object"" any more."
1778014,2018-11-26 06:41:54 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/434738
1778016,2019-02-17 07:28:06 UTC,"Hi,"
1778018,2018-07-14 18:11:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778032,2018-06-21 10:33:29 UTC,This is for kolla-ansible 6.0.0.0b4.dev65 deploying Ubuntu binary packages on Ubuntu 16.04
1778032,2019-09-12 13:54:51 UTC,"With binary packages - Kolla relies on binary packages vendors, in this case Ubuntu Cloud Archive. If that is still a bug - please contact them."
1778035,2018-06-21 10:59:34 UTC,apport information
1778035,2018-06-21 10:59:37 UTC,apport information
1778035,2018-06-21 11:00:09 UTC,This change was made by a bot.
1778035,2018-06-21 11:07:39 UTC,"The device seems to be using chipset/the device read from lsusb is called ""AMD Cali tv"""
1778035,2018-06-21 15:11:57 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1778053,2018-06-21 12:42:42 UTC,"Even worst: just tried to activate again unplugged HDMI which was then second of the list in pavucontrol, Firefox uses HDMI audio and not the internal audio device ! So only switching off HDMI gives sound back in Firefox."
1778062,2018-06-27 11:21:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778063,2021-01-07 16:01:27 UTC,"In response to comments on IRC about this, +1 to splitting this up into separate bugs that address smaller chunks of code. For example, staff client acq, staff client circ, tpac, etc."
1778063,2021-01-07 14:52:13 UTC,Removing pullrequest as this patch needs a rebase.
1778063,2020-08-17 17:21:24 UTC,Received a merge conflict when trying to apply to current master.
1778063,2019-03-01 19:51:28 UTC,"It looks like Firefox will support the autocomplete=""new-password"" soon, which will be nice."
1778063,2018-12-04 22:12:44 UTC,"Jason, just looking through your branch, the changes look sensible (and comprehensive!). Just two exceptions that confused me a little, in this file:"
1778063,2018-11-06 16:49:35 UTC,"I've bumped the importance because I've been getting reports of libraries running into issues with the wrong items being checked in at various locations, and local staff have narrowed it down to autocomplete interference. Here's a branch that does a couple things; in the staff client portions autocomplete is largely disabled everywhere because there's no benefit to a browser trying to guess what you want to do. Where it makes sense in the public facing parts of the opac autocomplete options are specified to make things more reliable and simpler for password managers and browser personal information features to use appropriately."
1778063,2018-12-05 13:05:14 UTC,"Those are intentional because browsers usually decide that they know best when it comes to usernames and passwords and will ignore the usual autocomplete=""off"" attribute. When presented with an autocomplete type that they don't know about though, they stop trying to second guess us and leave the fields alone."
1778066,2018-10-10 17:09:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778069,2019-02-14 18:46:08 UTC,Just adding a note that this can also happen in Gnome on a system without XFCE.
1778069,2019-02-15 11:54:31 UTC,I assume that adding the exo package to the Affects list should do. The upstream report has already been linked.
1778069,2019-01-29 05:18:06 UTC,This bug was fixed in the package xubuntu-default-settings - 19.04
1778069,2019-05-09 18:23:25 UTC,"Tengo el mismo problema en Xubuntu.
I have the same problem in xubuntu."
1778069,2018-08-26 14:17:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778069,2019-07-11 08:35:58 UTC,"status:	Fix Committed → Fix Released for 19.04.  Good, but please also release for 18.04 as it is LTS."
1778069,2019-01-28 11:29:43 UTC,Fix applied in the below commit.
1778069,2019-08-11 14:43:38 UTC,Will the fix be released for 18.04 also? Thx
1778069,2019-06-14 00:48:11 UTC,Resolved with the following commits:
1778069,2019-01-25 03:17:35 UTC,"Around Fedora 27, Nautilus stopped being able to open files with double click. It took me a very long time to figure out what was going on, but it turns out it was this bug:"
1778069,2018-08-15 18:57:00 UTC,"Happening for me too.  Should be a higher priority than ""low"" IMHO"
1778069,2018-10-28 16:02:11 UTC,Thanks Theo => your tip fix it for me.
1778069,2018-10-20 16:01:50 UTC,"You can fix this issue by removing the line ""x-scheme-handler/file=exo-file-manager.desktop"" from the following files:"
1778069,2018-10-19 19:16:50 UTC,I have the same problem. tested on several fresh installs of Xubuntu 17.10 and Xubuntu 18.04.
1778069,2018-10-04 08:08:39 UTC,Have the same problem. Hope will be fixed soon.
1778069,2018-09-29 14:49:45 UTC,I affects me too. Hoping that priority is risen.
1778069,2018-08-20 10:58:57 UTC,this effects a lot of users so please can you push the priority higher.
1778069,2019-01-02 20:04:24 UTC,"XFCE 18.04, nautilus was working fine.  Started to see this behaviour recently.  Possibly due to adding nautilus-extension-gnome-terminal."
1778073,2019-06-03 16:20:22 UTC,"Hi Thomas, have you had a chance to re-test this on 18.04?  From Christian's comment #3, sounds like this issue may already be resolved, but if not we can investigate further."
1778073,2018-06-21 15:24:46 UTC,Sounds related / similar to bug 1761096
1778073,2018-06-21 15:26:08 UTC,"The other bug had mentioned being resolved in latter versions.
Can you cross-try the same on e.g. 18.04 to be sure on the scope of this?"
1778074,2018-08-18 13:34:29 UTC,"It seems that the package is dropped in Debian at the time, therefore not available in Ubuntu 16.04.  I have packaged a snap package that can be installed by running the following command in the terminal:"
1778075,2018-06-21 14:48:37 UTC,https://review.openstack.org/#/c/577186 proposed as a WIP patch to get feedback
1778078,2019-06-16 15:03:22 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape-docs/documentation/issues/2 (where we can also set an appropriate milestone)
1778082,2019-01-12 18:19:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778082,2018-06-27 17:49:45 UTC,Thanks for your report!
1778082,2020-06-07 00:54:40 UTC,I've also observed this behavior on Kubuntu 20.04.
1778082,2018-06-22 07:19:20 UTC,"And after process is finished, there are no useful info too (screehshot is attached), only the text:"
1778082,2018-06-21 15:03:15 UTC,Notify in tray
1778082,2018-06-21 17:01:24 UTC,Windows after click on tray
1778087,2019-06-14 15:11:35 UTC,I think I have - can't remember. It was a few months ago.
1778087,2019-06-14 09:35:32 UTC,Have you tested kernel in #38?
1778087,2019-06-13 17:24:37 UTC,Hang on boot with mainline 5.2-rc4
1778087,2019-06-13 06:07:00 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc4/"
1778087,2019-06-12 15:37:24 UTC,"Hello,
same issue here on
        Manufacturer: ASUSTeK COMPUTER INC.
        Product Name: UX331UN"
1778087,2019-04-22 04:49:37 UTC,"For those who doesn't use Ubuntu kernel, this patch may help:
https://lkml.org/lkml/2019/4/22/5"
1778087,2019-06-14 15:40:21 UTC,Just tested it. Totally disables the touchpad.
1778087,2020-02-16 09:39:57 UTC,"Hello, I am still having the issue with the ELAN 1200 disconnections on my new zenbook UX533FD-A9030T. It happens every 10-40 minutes, randomly!"
1778087,2019-04-16 15:18:56 UTC,To restore the touchpad after a disconnect you want to try modprobe -r hid-multitouch && modprobe hid-multitouch. You shouldn't need to reset i2c-hid unless it's a last resort and resetting hid-multitouch didn't work.
1778087,2019-04-16 10:26:32 UTC,Sure. I've attached it as a text document because it´s a lot of text. Let me know if you need more information.
1778087,2019-04-16 10:02:02 UTC,Possible to attach full dmesg?
1778087,2019-04-16 09:53:49 UTC,"$ dmesg | grep ELAN
[  159.396044] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
[  159.426483] input: ELAN1200:00 04F3:3090 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-4/i2c-ELAN1200:00/0018:04F3:3090.0006/input/input25
[  159.426611] hid-multitouch 0018:04F3:3090.0006: input,hidraw4: I2C HID v1.00 Mouse [ELAN1200:00 04F3:3090] on i2c-ELAN1200:00
[  159.428056] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: IRQ triggered but there's no data
[  161.086401] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/255)"
1778087,2019-04-16 09:51:56 UTC,"Thanks for your message. However, with that kernel running the touchpad doesn't work at all. No movement and no click input."
1778087,2019-04-13 14:46:40 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1778087-pinctrl/"
1778087,2019-04-16 15:24:07 UTC,Here is a script I made for resetting the touchpad with the gnome keyring (because it requires sudo priviledge).
1778087,2019-04-22 03:22:21 UTC,"The log in #42 is flooded with:
[  127.470404] i2c_designware i2c_designware.0: timeout waiting for bus ready"
1778087,2019-06-15 09:22:39 UTC,Please attach dmesg.
1778087,2019-06-17 07:54:46 UTC,"I am currently on Manjaro with 5.0 Kernel and the touchpad does not disconnect but whenever I close the lid on the laptop and open it again, it starts lagging and disconnects so I need to do a restart. On the previous kernel it used to disconnect and also I have tried 5.1 and it was also disconnecting."
1778087,2019-04-12 13:44:49 UTC,In the mean time I've installed KDE Neon which is supposed to be based on Ubuntu 18.04. I'm running kernel version 5.0.1 and still got the disconnect problem with my Asus FX503VD with the touchpad.
1778087,2020-03-27 15:35:51 UTC,This bug is back and I'm getting a bunch of emails related to it. Re-opening because the bug is back in upstream. It was fixed in kernel 5.2.5 for me but I'm getting reports of it being back in 5.3.0 and 5.5.13.
1778087,2019-07-31 09:17:13 UTC,(Running Kubuntu 19.04)
1778087,2020-03-27 18:07:33 UTC,"Hi, as an update, on my ASUS-GL503VD the erratic behaviour disappeared around 5.2.x but still disconnected from time to time. I'm on 5.3.7 now and disconnecting remains."
1778087,2019-07-31 09:16:47 UTC,I stopped following this thread for a while. I now running kernel 5.2.4-050204-generic and all my touchpad problems are solved. So the scrolling is smooth and I got no more disconnects. Thanks all for making this happen!
1778087,2019-07-30 13:48:49 UTC,"The original issue should be fixed by this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=670784fb4ebe54434e263837390e358405031d9e"
1778087,2019-06-17 07:09:09 UTC,"Not currently using Ubuntu, but I can attest that this exact same issue persists across all distro's that I have tried."
1778087,2019-07-30 10:16:02 UTC,"I have installed the newest kernel 5.2.3-050203-generic and here the disconnects do not happen when I use it but whenever I close the lid and open it again, the touchpad starts lagging for a second and then disconnects so I need to do a restart in order to start working again (reloading it doesn't help)."
1778087,2019-07-11 19:11:43 UTC,"I think the issue is the same as the others above so there is no point in opening another one.
dmesg | grep ELAN returns:"
1778087,2019-07-11 18:35:09 UTC,Can you file a new bug? Without logs I won't be able to really understand your issue.
1778087,2019-07-11 17:49:45 UTC,"With that kernel the touchpad does not work at all.
This issue was partially fixed in Manjaro with 5.0 kernel but I assume the Ubuntu kernel is different"
1778087,2019-07-11 11:52:12 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1835040-2/"
1778087,2019-07-11 11:12:07 UTC,"Unfortunately I am not that familiar with the patching process.
I have read about it and I have tried the following without any success:
I have put the .diff file in this directory: /lib/modules/5.0.0-050000-generic and tried applying the patch the following command: patch -p1 < intel-pinctrl-intel.diff but it always asks for a file to patch and I can't find the original file which needs to be patched. I have tried with p0 flag also but couldn't do it. I have also tried moving the .diff file to: /lib/modules/5.0.0-050000-generic/kernel/drivers/pinctrl/intel but still it asks for a file to patch."
1778087,2019-07-09 07:20:46 UTC,"Tetrix,"
1778087,2019-07-11 19:26:15 UTC,Here is also the complete dmesg output
1778087,2019-02-10 03:18:41 UTC,"Also, ubuntu 18.10 never ran well on my machine. Can't say for sure if all FX503VDs are so ""incompatible"" with 18.10, but going back 18.04 and installing kernel 19.0 seemed to be provide a more stable version on my computer."
1778087,2018-06-21 15:50:02 UTC,apport information
1778087,2019-02-09 11:53:22 UTC,"@Abdulhalim Rafeik, how do you unload & reload i2c_hid? If i do that through:"
1778087,2018-06-21 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778087,2018-06-21 15:54:36 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1778087,2018-06-21 15:54:53 UTC,Let me know if I can help with any additional debug information.
1778087,2018-06-21 16:16:18 UTC,@jsalisbury
1778087,2018-06-21 18:02:16 UTC,@jsalisbury
1778087,2018-06-21 18:04:40 UTC,"Furthermore, the erratic behaviour/disconnects continued on 4.18."
1778087,2018-06-25 19:43:48 UTC,"I'm on the exact same situation with my ASUS-GL503VD. I have tried with the xorg synaptics touchpad driver (xserver-xorg-input-synaptics package) but the erratic behavior remains. Also tried with i8042 and acpi related kernel commands on the grub config as suggested on external forums, apparently those kind of commands were successful on other elan touchpads."
1778087,2018-07-11 08:38:27 UTC,"I also have the same problem. When the touchpad is enabled, it has erratic behavior! I didn't have any problem before the upgrade to 18.04 and also no problem in Windows 10."
1778087,2018-07-11 20:51:38 UTC,"I had this same problem with my laptop on 17.10. When I upgraded to the kernel to 4.14 I did not receive the errors in the syslog, but the touchpad responsiveness and functionality worked fine.
When I upgraded to 18.04 with kernel 4.15.0-24 it looks like it has regressed and I am back to using a USB mouse since the touchpad is almost unusable, and if I put all 5 fingers on the touchpad, it locks it out completely."
1778087,2018-07-12 05:20:39 UTC,"Bionic kernel with
commit ef6eaf27274c0351f7059163918f3795da13199c
Author: Jason Andryuk <email address hidden>
Date:   Fri Jun 22 12:25:49 2018 -0400"
1778087,2018-07-12 20:26:54 UTC,@kaihengfeng
1778087,2018-07-24 04:22:10 UTC,"i am having the same issue with Asus FX503v laptop, GTX1050. I am on 18.04 kernel 4.15.0.29. It was freezing whole computer up but adding i8042.request into grub, freezing went away. It is still very sensitive and opening one tab in chrome might open 6 at once. My touchpad is Elan1200."
1778087,2018-07-25 09:34:50 UTC,"Let's see if this kernel can workaround your issue:
https://people.canonical.com/~khfeng/lp1778087-2/"
1778087,2018-07-25 18:41:44 UTC,"Hello @kaihengfeng,"
1778087,2018-08-03 07:10:40 UTC,I think it's basically the same one as https://bugzilla.redhat.com/show_bug.cgi?id=1543769
1778087,2019-02-10 03:15:36 UTC,I used to have the jumpiness problem too. The fix I found was installing kernel 19.0 via ukuu. You don't even have to be running that kernel. Just installing it fixed the erratic behavior of the touchpad.
1778087,2018-08-03 17:22:34 UTC,Hello all
1778087,2018-08-03 15:17:58 UTC,You might be right!
1778087,2019-02-09 08:18:06 UTC,The same thing is happening to me on my FX503VD and can confirm that unloading and reloading the i2c_hid module does fix the problem. Has anyone found a permanent fix for this problem?
1778087,2019-01-02 13:14:59 UTC,"I am experiencing the same behavior with the 4.19 kernel.
The touchpad does not work smoothly and freezes occasionally and I have to wait for couple of minutes, after which it starts working again."
1778087,2018-12-15 03:25:16 UTC,After upgrade to Ubuntu 18.10 (kernel 4.18.0-12-generic) I got the same touchpad freeze on Asus X540NA and the right click doesn't work at all.
1778087,2018-12-13 04:28:28 UTC,"I have also noticed this error on a gl-702vm on archlinux with the 4.19 kernel. I have the same error, with the touchpad jumping around, being super slow, and getting a repeated error message that says: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535). I can try the latest ubuntu release and post the error message from that as well if nessacary."
1778087,2018-12-09 16:22:48 UTC,"The result in my previous comment was obtained with kernel parameter ""i2c-hid.debug=1"""
1778087,2018-12-09 16:20:52 UTC,Here is my output collected on Asus X540NA notebook with Ubuntu 18.04 (4.15.0-42-generic kernel). Just after the boot:
1778087,2018-09-28 03:32:03 UTC,"Can you boot with kernel parameter ""i2c-hid.debug=1"" and attach dmesg here? Thanks!"
1778087,2018-09-27 22:25:57 UTC,"Hi Kai-Heng Feng,"
1778087,2018-09-27 20:22:57 UTC,"Please try this kernel:
https://people.canonical.com/~khfeng/i2c-hid-elan/"
1778087,2018-08-03 18:55:38 UTC,"Right on. Yeah apparently there are two different models for this touchpad, AFAIK."
1778087,2018-08-03 18:40:53 UTC,"Dear Alistair,"
1778087,2018-08-03 17:39:39 UTC,Hello Vassilis and welcome to the bug report!
1778087,2018-09-28 15:28:40 UTC,Is it ok if I do that with my current working kernel(4.18.0)?
1778088,2019-07-18 10:20:59 UTC,I mean in evince
1778088,2019-08-24 15:44:34 UTC,I agree with Serge that disabling support for single-page DjVu files is a mistake. There is no valid reason to do so whatsoever.
1778088,2019-05-15 14:02:55 UTC,"Up to recently, this bug was easily fixed by removing the ""djvulibre-desktop"" package, but some recent upgrade seems to have brought it back with a vengeance (some time before but not long before 2019-05-15)."
1778088,2019-07-18 10:17:06 UTC,"This is really ugly solution to disable to open single page DjVu. Why not to do the same with single page PDF??? This is also something like images, we do not want to see this :)"
1778088,2018-12-14 11:13:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778088,2018-12-14 11:25:48 UTC,Cross-reference to Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710
1778093,2018-06-22 02:21:37 UTC,You do indeed seem to have 2 monitors plugged in.
1778093,2018-06-22 17:10:41 UTC,"Yes, there was a cable plugged in to the other port, but the monitor on
the other end was set to a different input and I expected it to have
been ignored.  The 'bug' is that during installation, there's no need to
set up multiple screens, except as clones of each other, so that the
installation will work from any screen.  If you're looking at the
'wrong' monitor,  the initial symptom is indistinguishable from the
installation hanging which makes the source of the problem harder to
track down.  Part of the illusion is because the mouse was so far off
screen, it seemed like it was frozen as well."
1778093,2018-06-25 02:11:04 UTC,Unfortunately an inactive monitor that is connected is usually still detected as a monitor. So the system can only try to do the right thing and try to use it.
1778093,2018-06-25 09:37:40 UTC,"Further to comment #4, last I checked (when working on Mir) it was impossible to distinguish between a plugged in monitor that is on and one that is off. In software we can't tell the difference. It's detected all the same :("
1778099,2019-05-13 22:10:42 UTC,"@cgregan: looking through the juju status, I don't see the units that are blocked or errored."
1778107,2019-04-12 23:29:13 UTC,This issue was fixed in the openstack/kolla-ansible 6.2.0 release.
1778107,2019-01-28 10:48:54 UTC,"Reviewed:  https://review.openstack.org/633017
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=00e7a8342b42099eac107a31f1fde9d958b15ad8
Submitter: Zuul
Branch:    stable/queens"
1778107,2018-09-04 16:24:04 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0rc1 release candidate.
1778107,2018-08-27 07:42:59 UTC,"Reviewed:  https://review.openstack.org/577239
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=19b1e9c08dcb706ad7e396db6e03d3726f35747c
Submitter: Zuul
Branch:    master"
1778108,2018-06-21 17:26:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778108,2018-06-21 23:55:03 UTC,*** This is an automated message ***
1778108,2018-10-06 12:18:00 UTC,See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910436
1778116,2019-11-08 15:21:58 UTC,"Also, I think it would be useful to have a reset to defaults on the transmission line calculator. Even if it doesn't save them between launches, it would allow you to recover the default values without having to relaunch the PCB calculator. If you want to add that you can, but we can still merge your patch with the above changes without the transmission line part if you prefer."
1778116,2018-06-23 22:11:27 UTC,"Note that this ""reset to default"" addition would also be very much appreciated in other places in KiCad, such as in the ""Copper Zone Properties"" window in Pcbnew. Otherwise, it's super easy as a beginner to change these settings and then not know what are good defaults afterwards. A ""reset to defaults"" button or something would be really nice inside this window (see attached image) and all other windows where defaults are present."
1778116,2019-10-26 18:00:55 UTC,"I tried to create patch for this wish.
As far I understand,  TransLine and RF Attenuator don't save parameters between launches.
But I don't have any idea, why wxFormBuilder changes form file so much."
1778116,2019-11-08 15:19:03 UTC,"Dmitry, thank you for the patch."
1778116,2019-11-09 18:01:55 UTC,"Ian, thank you for feedback.
Yes, you're absolutely right.
In new patch I'll fix your three issues and add a reset on the transmission line calculator."
1778116,2019-11-10 10:00:09 UTC,"Ian, I think, I fixed your issues."
1778116,2019-11-10 17:29:11 UTC,"Fixed in revision 9c33620a0fcf8e7c1f23bfacea6c89da1108199f
https://git.launchpad.net/kicad/patch/?id=9c33620a0fcf8e7c1f23bfacea6c89da1108199f"
1778116,2019-11-10 17:29:44 UTC,"Dmitry, thanks for updating the patch. It looks good to me, so I have merged it into the v6 development."
1778135,2019-05-30 10:03:36 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1778135,2019-05-30 10:03:31 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.12
1778135,2019-05-29 08:32:54 UTC,"Using 3.20.5-0ubuntu0.16.04.12 on xenial it works fine, also no report with that version on e.u.c"
1778135,2019-05-14 23:40:41 UTC,"Will wait a few days to see if any crash reports show on:
https://errors.ubuntu.com/?release=Ubuntu%2016.04&package=gnome-software&period=month&version=3.20.5-0ubuntu0.16.04.12"
1778135,2019-04-25 13:57:16 UTC,"An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: ""Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.""."
1778135,2019-05-14 08:00:29 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1778137,2018-08-24 21:13:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778143,2018-06-22 19:58:41 UTC,Please install the debug symbols as described here and follow the instructions also to produce a backtrace.
1778143,2018-06-25 20:57:47 UTC,"Thank you for the response. With debug symbols installed, gdb produces the attached output."
1778143,2018-07-12 14:36:40 UTC,Do you need any more information?
1778145,2018-06-22 22:16:27 UTC,"To clarify, SVG file originated within InkScape using following flow:"
1778145,2018-06-23 16:46:44 UTC,"- just writing to demonstrate that this situation can be produced in the gui without importing any data.
- attached is a file with snapping enabled, and a grid. It contains three connected points."
1778145,2018-06-23 22:18:08 UTC,"Unfortunately, the extension did not work for me. =("
1778145,2018-06-23 15:37:55 UTC,"There is a recent extension for purging small lines... I haven't tried it yet, but it looks promising."
1778145,2018-06-23 10:46:14 UTC,"okay, I just checked, and the file from Inkscape 0.91 still has the same problem with unselectable objects. sorry for the noise..."
1778145,2018-06-22 23:32:04 UTC,"just for curiosity, I loaded your pdf file into Inkscape 0.91
version = Inkscape 0.91 r13725 (Jan 30 2015)"
1778145,2018-06-22 23:08:04 UTC,"thanks for the pdf file. I opened it using Inkscape 0.92.3 and got the same result. There are numerous instances of paths that look like this:
<path
           d=""m 19871,23599 v 0 0 0""
           style=""fill:none;stroke:#989898;stroke-width:12;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-dasharray:none;stroke-opacity:1""
           id=""path18878""
           inkscape:connector-curvature=""0"" />"
1778145,2020-01-25 13:27:09 UTC,"Hi, I've split the bug report in two and migrated it to gitlab: one for the wrong bounding box and one for the generation of these paths, which are correct, but unnecessary.
https://gitlab.com/inkscape/inbox/issues/1674
https://gitlab.com/inkscape/inbox/issues/1675"
1778145,2018-06-22 21:59:05 UTC,@Filip - could you attach the original pdf file that was used to produce this file?
1778145,2018-06-22 19:14:23 UTC,"""The objects can be deleted using The Objects dialog or the XML Editor dialog..."" Yes, it took a long time to find the offending paths (source SVG has many thousands of nodes) and both select & delete operations were very slow (deleted 100-150 at a time, each time took ~4 minutes on my speedy PC, 3 cores, 25% CPU), but it did work!"
1778145,2018-06-22 16:51:31 UTC,"looking at the original file from comment, the same problem appears. There are many instances of paths that look like this."
1778145,2018-06-22 16:41:31 UTC,"for the file SingleObject.svg, the selection problem appears to be related to the unusual syntax of the path command. The path is:
M 53.9043324,287.696256 V 287.696256 287.696256
Normally the V command would be used in conjunction with only a single number, not two, since it refers to a vertical movement. If I edit the path to read:
M 53.9043324,287.696256 V 287.696256
then the object becomes selectable using the mouse ""lasso"". Edited file is attached."
1778145,2018-06-22 14:50:57 UTC,I'd consider this a selection and bounding box issue...
1778145,2018-06-22 04:08:01 UTC,"In the example file I downloaded, there are a few objects (~1400) that have multiple nodes in the same location."
1778145,2018-06-22 20:24:51 UTC,"Clearly this is a file that originated from other software, that software may have no way to avoid the generation of these nonstandard objects.."
1778146,2020-06-04 17:35:06 UTC,"Reviewed:  https://review.opendev.org/733619
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=e246e80d23a2b0bb118a1cc89d5542935fba0ed7
Submitter: Zuul
Branch:    stable/ussuri"
1778146,2020-06-04 14:20:29 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/733619"
1778146,2020-06-02 21:23:49 UTC,"Reviewed:  https://review.opendev.org/732495
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=712b258f2d1870b3f07fb67b043769999edb3ef5
Submitter: Zuul
Branch:    master"
1778146,2019-04-12 14:34:58 UTC,"Change abandoned by zhulingjie (<email address hidden>) on branch: master
Review: https://review.openstack.org/577635"
1778146,2020-06-02 08:31:50 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/732495"
1778146,2018-06-24 02:38:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577635"
1778146,2018-07-27 13:22:48 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.0.0b3 development milestone.
1778149,2018-09-24 19:08:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778149,2019-02-21 18:50:56 UTC,These errors occurred while trying to install X2go packages with Synaptic. I'm new to 18.04 but use X2go extensively on 16.04.
1778160,2018-08-20 13:03:27 UTC,I tried with the snaps from James directory as mentioned in the forums thread but cannot reproduce this crash with any of them and the version of gnome-software in bionic updates.
1778160,2019-05-14 23:37:44 UTC,Tested gnome-software 3.20.5-0ubuntu0.16.04.12 and able to connect / disconnect interfaces.
1778160,2019-05-30 10:03:31 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.12
1778160,2019-05-14 08:00:37 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1778160,2019-04-25 13:57:17 UTC,"An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: ""Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.""."
1778160,2018-08-23 08:22:27 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1778160,2018-08-23 08:22:19 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.2
1778160,2018-08-01 21:57:11 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1778160,2018-06-22 02:33:40 UTC,The crash seems to be related to a ComboBox and has only started occurring in Xenial after the Snap interfaces support was added.
1778160,2018-08-01 21:55:38 UTC,">
[Regression Potential]
Fix is to rename a signal to avoid a name collision, low chance of introducing new bugs.
"
1778160,2018-06-22 05:22:54 UTC,This bug was fixed in the package gnome-software - 3.29.1-0ubuntu2
1778160,2018-06-22 04:12:32 UTC,"Asked on forum if anyone knows a suitable snap to test this:
https://forum.snapcraft.io/t/searching-for-a-snap-that-has-a-plug-with-multiple-slots"
1778160,2018-06-22 03:32:27 UTC,"Cause seems to be a name collision for the GsPermissionComboBox ""changed"" signal - solution was to rename it to ""value-changed"". This only occurs when a snap has a plug that can connect to more than one slot."
1778160,2018-08-01 21:56:54 UTC,">
Asked on forum if anyone knows a suitable snap to test this:
https://forum.snapcraft.io/t/searching-for-a-snap-that-has-a-plug-with-multiple-slots
"
1778161,2020-09-09 10:52:11 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1778181,2018-06-22 10:31:25 UTC,"NØ> In what way does it hinder ""downstream work""? What kind of work do you expect to perform on the exported file? Could you please be a bit more verbose on your use case."
1778181,2018-06-22 07:55:58 UTC,"In what way does it hinder ""downstream work""?  What kind of work do you expect to perform on the exported file? Could you please be a bit more verbose on your use case."
1778181,2018-06-22 20:20:52 UTC,"Addit: Testing this more, the killer problem is Via-In-Smd, which triggers from GerbView 'dumb' default to export all flash pads as vias. Via in Through-hole are usually ok, and Via at Via is usually ok (would fail on a blind via) but via-at-smd is very likely to cause a violation, and thus kill the nice Autoconnect feature in Pcbnew."
1778182,2018-07-06 12:37:36 UTC,Works for me with both the GTK display and '-display sdl' with current head-of-git QEMU...
1778182,2021-01-10 04:17:32 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1778182,2020-11-10 15:39:14 UTC,"Hi; I'm moving this bug to 'incomplete', because I was never able to repro it -- gtk and sdl displays both worked for me."
1778182,2018-06-22 07:01:59 UTC,Things that work:
1778189,2020-03-13 10:17:22 UTC,Looks like a fix was merged and shipped in Django 3.0: https://github.com/django/django/pull/10898
1778189,2018-09-12 21:39:03 UTC,"ran into this same issue, it appears that when the msgstr for a particular msgid is also a valid key into the catalog, this can occur."
1778189,2018-10-04 20:29:10 UTC,submitted https://code.djangoproject.com/ticket/29825 against django since I believe this is an issue in ngettext
1778189,2018-10-30 14:35:36 UTC,Proposed fix at https://github.com/django/django/pull/10506   current needs reviews
1778189,2018-12-29 13:22:39 UTC,Waiting for a fix in Django side.
1778189,2019-02-28 11:34:47 UTC,A workaround for this bug is to disable all translated languages via local_settings:
1778189,2020-03-13 14:28:56 UTC,Actually this is claimed to be fixed by https://review.opendev.org/#/c/696321/
1778189,2020-07-07 15:32:26 UTC,See also https://bugs.launchpad.net/zun-ui/+bug/1762089
1778190,2018-12-12 12:38:07 UTC,Thank you for your bug report.
1778195,2018-07-11 22:35:53 UTC,"Reviewed:  https://review.openstack.org/580376
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=472bb4d2f91f4660fef16f7d75be5e58bbab4017
Submitter: Zuul
Branch:    stable/queens"
1778195,2018-07-11 22:50:28 UTC,"Reviewed:  https://review.openstack.org/580375
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=5ce900a7e4f0fb3d58bc1a795fbfd239345d86b0
Submitter: Zuul
Branch:    stable/pike"
1778195,2018-07-11 22:50:36 UTC,"Reviewed:  https://review.openstack.org/580565
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=7adb0bae8dd1131c2c44e4d2c886892395275a06
Submitter: Zuul
Branch:    stable/ocata"
1778195,2018-07-06 06:51:44 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/580565"
1778195,2019-06-11 11:42:06 UTC,"Reviewed:  https://review.opendev.org/580391
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_ceilometer/commit/?id=8885bca2483781143478daa5eb4c875adc1c6f1e
Submitter: Zuul
Branch:    stable/queens"
1778195,2019-10-21 14:35:37 UTC,"Change abandoned by kourosh vivan (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/580390
Reason: I don't work with stein anymore"
1778195,2018-07-14 11:08:37 UTC,"Reviewed:  https://review.openstack.org/577384
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_ceilometer/commit/?id=9d54c79b82a3ce325b0070ffc78f4091c5e33e83
Submitter: Zuul
Branch:    master"
1778195,2018-07-05 16:45:25 UTC,"Reviewed:  https://review.openstack.org/577379
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=9a767909197fcc37db123774874a80de851b5927
Submitter: Zuul
Branch:    master"
1778195,2018-07-05 14:11:21 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580390"
1778195,2018-07-05 13:16:29 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/580376"
1778195,2018-07-05 13:16:12 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580375"
1778195,2018-06-22 10:01:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577384"
1778195,2018-06-22 09:33:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/577379"
1778195,2018-07-05 14:12:45 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/580391"
1778200,2018-07-09 20:22:44 UTC,Please!!!
1778200,2018-08-29 12:48:25 UTC,Podbird is an essential app and important for UT. I'm very happy with this podcast manager. The missing xenial build could prevent users from updating their phones to 16.04.
1778200,2019-03-27 10:25:56 UTC,"There is a build, so we can close this ticket."
1778200,2019-04-08 08:43:35 UTC,https://open-store.io/app/com.mikeasoft.podbird
1778203,2018-06-30 13:16:30 UTC,"Sometime between last night and this morning, the whole directory was deleted from the server :(  I am not sure who or what did that.  I will try to get it uploaded again today."
1778203,2018-06-30 15:03:05 UTC,"Mm, I deleted the frankie dir as I was makimg more space on the downloads server. I did't verify its contents."
1778203,2018-07-01 01:32:49 UTC,No problem.
1778203,2018-06-30 13:51:33 UTC,The new URL is http://downloads.kicad-pcb.org/osx/testing/kicad-unified-frank-20180629-132641-bbe81b0b3.dmg.
1778203,2018-06-29 21:01:42 UTC,"Hi Adam link gives me ""nginx error!
The page you are looking for is not found.
Website Administrator"""
1778203,2018-07-01 14:40:49 UTC,Frank Here:
1778203,2018-06-26 13:13:48 UTC,"Well, let's see if this works.  The older Intels only used BGRA (actually ARGB) ordering to match the DirectX ordering and everything else went through software."
1778203,2018-06-26 06:47:20 UTC,"Seth, how did you figure it out? It sounds plausible, but I wonder how one discovers such issues."
1778203,2018-06-25 16:44:45 UTC,"Second important caveat:  I have not evaluated this patch for suitability beyond checking that it doesn't mess up my rendering under Linux.  If it fixes the Mac issue, we will need to look closely for possible knock-on effects before merging."
1778203,2018-06-25 17:36:46 UTC,"Just talked to Nick, he's gonna help me compile a version with Seth's patch. Ill report back later with the results"
1778203,2018-06-29 19:29:22 UTC,I added the patch and uploaded it to http://downloads.kicad-pcb.org/osx/frankie/kicad-unified-frank-20180629-132641-bbe81b0b3.dmg. Please use that for testing.
1778203,2018-07-01 14:54:30 UTC,Hi Frank-
1778203,2018-06-25 16:32:42 UTC,Hi Orson/Frank-
1778203,2018-07-01 15:06:23 UTC,Frank here:
1778203,2018-07-01 15:45:38 UTC,Thanks everyone for the effort in testing.  I'm sorry that the issue doesn't appear to have an easy fix apart from falling back to Cairo.
1778203,2018-09-05 16:05:18 UTC,@Nikolas-  Can you test a recent nightly build and see if the issue remains?
1778203,2018-09-05 22:00:47 UTC,"@Seth
Niko tested the latest nightly and the issue still persist"
1778203,2018-09-05 22:26:40 UTC,"OK, thanks."
1778203,2018-09-28 13:43:55 UTC,"I think this might be related, and possibly can give you some clue:"
1778203,2018-09-28 13:46:58 UTC,"Forgot to add, i have the exact same gpu, osx 10.13.6."
1778203,2019-11-08 23:44:55 UTC,"@Nick I can share the board file in private, but I'm quite confident any big board will trigger this. I have a few other T420`s (Running Ubuntu) at work I can try to replicate with."
1778203,2019-10-29 09:26:09 UTC,Nicolas has just experienced this again with the following setup:
1778203,2019-11-08 23:24:20 UTC,"@Frank, are you able to share the board file in private?"
1778203,2019-10-30 14:29:10 UTC,"managed to recreate on my old T420 windows laptop, using the biggest board I have.
I attached system info below. Please let me know if I can do something to help find the issue"
1778203,2018-07-01 15:04:07 UTC,"Process:               pcbnew [901]
Path:                  /private/var/folders/*/pcbnew.app/Contents/MacOS/pcbnew
Identifier:            org.kicad-pcb.pcbnew
Version:               ??? (???)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           pcbnew [901]
User ID:               501"
1778203,2018-06-25 15:45:30 UTC,"Hi Frank,"
1778203,2018-11-13 15:47:16 UTC,"This looks slightly stale, could you please try to test with the latest nightly builds for the 5.0 branch."
1778203,2018-06-25 15:29:00 UTC,DISCLAIMER: The following advice might be risky and I do not take any responsibility if things go sideways. Proceed only if you know how to revert the mod.
1778203,2018-06-25 15:29:15 UTC,Hi @Orson
1778203,2018-06-22 10:18:10 UTC,Does this also happen in fallback mode?
1778203,2018-06-22 10:30:51 UTC,"It only happens when i run the file in ""Accelerated""."
1778203,2018-06-22 10:33:09 UTC,"Nikolas, does it happen with every board? Can you try demo projects shipped with KiCad?
If it is board dependent, could you attach the board file that exposes the bug?"
1778203,2018-06-22 10:51:26 UTC,"Hi Orson,"
1778203,2018-06-22 10:54:43 UTC,"Nikolas' colleague here:
I just tested the board with following setup, with no issue.
Perhaps it's a MacOS thing?"
1778203,2018-06-22 11:56:16 UTC,"Nikolas,"
1778203,2018-06-22 13:09:55 UTC,"I have succesfully opened the board on recent Arch Linux, Windows 7 and macOS 10.13.4.
Could you give some more details about the hardware, particularly the video card model? What macOS version do you use?"
1778203,2018-06-22 13:37:51 UTC,"okay, i can see im running versin ""10.11.6"". I might be outdated."
1778203,2018-06-22 14:32:12 UTC,"I suggest doing an update, but my gut feeling tells me you might be running out of video RAM. Try to disable zone filling display and antialiasing, perhaps it may help. Is there a discrete video card in your Mac?"
1778203,2018-06-22 15:14:01 UTC,"Did you use the build from
http://downloads.kicad-pcb.org/osx/testing/
or
http://downloads.kicad-pcb.org/osx/nightly"
1778203,2018-06-22 15:27:12 UTC,"Orson, i will start an update now. I dont think it has a discrete video card. It's from 2013."
1778203,2018-09-19 21:40:12 UTC,I'm going to bump up the importance of this at least until: (a) we find out what the issue is or (b) decide there's nothing we can do about it.
1778203,2018-06-23 20:58:20 UTC,Can you plot this file to Gerber and open it in GerbView using Accelerated?  Also please try the steps that Orson suggested about unfilling the zones.
1778203,2018-06-25 15:09:37 UTC,"Board 1: Same issue
Board 2: Same issue untill I go -> Fallback -> Accelerated it works
Board 3: Same issue
Board 3: Same issue"
1778203,2018-06-25 15:03:30 UTC,Hi Orson
1778203,2018-06-25 14:47:26 UTC,"Nikolas, can you confirm that 'video' and 'kit-dev-coldfire-xilinx_5213' demos open without issues?
What about other boards:
- https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/HARDWARE/A64-OLinuXino/A64-OLinuXino_Rev_D/A64-OlinuXino_Rev_D.kicad_pcb
- https://raw.githubusercontent.com/mossmann/hackrf/master/hardware/hackrf-one/hackrf-one.kicad_pcb
- https://raw.githubusercontent.com/timvideos/HDMI2USB-numato-opsis-hardware/master/board/HDMI2USB.kicad_pcb
- https://raw.githubusercontent.com/c4puter/motherboard/master/motherboard.kicad_pcb"
1778203,2018-06-25 12:39:31 UTC,"@Orson, fair enough.  I will go ahead and tag rc3 once there is a fix
for the segfault bug Seth just reported.  Thanks for looking into this."
1778203,2018-06-23 15:38:17 UTC,I have now updated my macbook pro to 10.13.5 with no results.
1778203,2018-06-25 15:22:12 UTC,"Thank you for prompt response, it is indeed very useful information. Unfortunately, it may take some time before I come up with a potential solution."
1778203,2018-06-25 07:23:39 UTC,"Wayne, I am afraid it will take a lot of time. All machines I have handy (including a Macbook) display the board correctly even on integrated GPUs, so all I can do is to blindly throw patches at the problem and that is never fast or efficient. The discussed issue does not cause a crash and the board is still editable with Cairo, though I admit it is not very convenient with 6 layers."
1778203,2018-06-24 20:47:33 UTC,"orson, I'm not able to build KiCad manually. Haven't gotten to that point yet i guess"
1778203,2018-06-24 20:14:15 UTC,"@Orson, it seems like this should be fixed for rc3.  Any idea when you might have this fixed?"
1778203,2018-06-23 21:13:59 UTC,"There is one difference between displaying selected and unselected items: the former ones are displayed using Vertex Buffer Object, while the latter ones - Vertex Array. It might be a hint that there is a problem with the VBO method. It is a bit surprising though, as you say it works fine for simpler boards."
1778203,2018-06-25 08:26:52 UTC,Hi Orson and Seth
1778206,2019-03-22 03:46:38 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1778206,2018-12-19 20:48:15 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1778206,2018-06-25 12:21:54 UTC,"For me the bug looks like:
BDM cleanup happens in nova.compute.manager.ComputeManager._rollback_live_migration
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L6636
based on migrate_data.old_vol_attachment_ids.
If nova.compute.manager.ComputeManager.pre_live_migration fails there is no such data
in migrate_data and BDM cleanup will not happen.
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L6166"
1778206,2018-10-22 19:33:32 UTC,"Reviewed:  https://review.openstack.org/587439
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1a29248d5e688ba1d4f806895dccd45fcb34b833
Submitter: Zuul
Branch:    master"
1778206,2018-10-23 14:26:08 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/612715"
1778206,2018-10-23 18:34:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/612774"
1778206,2018-10-24 19:23:53 UTC,"Reviewed:  https://review.openstack.org/612715
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6aecf475dbff9c7d477378c021749b987d47deae
Submitter: Zuul
Branch:    stable/rocky"
1778206,2018-10-24 21:41:58 UTC,"Reviewed:  https://review.openstack.org/612774
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4b53e4edf9f7f8c794316d3a0920d727723d1bab
Submitter: Zuul
Branch:    stable/queens"
1778206,2018-11-06 06:01:02 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1778207,2018-07-05 03:10:12 UTC,I am looking at such an issue already - let me take it for now - I will probably Dup it. I am out on PTO - so will take some action next week when I am back.
1778222,2018-06-26 20:43:04 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1778222,2018-06-22 13:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778222,2018-06-22 14:59:54 UTC,"The kernel version is 4.13, which is used in 17.10 but not 18.04."
1778222,2018-06-23 12:23:44 UTC,When this problem occurs you cannot get to the terminal or anything else. everything is locked up. You have to power the machine down. If anything is logged I don't know how to get to it with the system locked up.
1778222,2018-06-24 22:50:20 UTC,Today I installed VirtualBox 5.2.12 on windows 7 pro.
1778222,2018-06-25 13:43:17 UTC,"Comparing differences between kernels.
There are differences in the way kernel 4.11 and kernel 4.15 handle 'ACPI'."
1778222,2018-06-30 15:24:12 UTC,Upgraded to kernel 4.17.3 using ukuu. System still fails to boot. Gets the same kernel panic and locks up.
1778222,2018-07-01 11:17:38 UTC,"I went back and installed kernel 4.12.14 and it works fine so something definitely changed in kernel 4.13 that keeps my machine from booting. Attached is my CPU information,"
1778222,2018-07-01 11:18:40 UTC,Additional information
1778222,2018-07-01 11:19:25 UTC,Additional info
1778222,2018-07-01 11:20:33 UTC,Additional information
1778222,2018-07-30 12:25:58 UTC,"Closing this . Since it is becoming clear that Linux is abandoning it's original fan base of older hardware and moving on, as it should, I don't love it enough to go out and buy new hardware since Windows stills run fine on my old stuff."
1778224,2018-07-01 15:30:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778226,2018-06-22 13:47:51 UTC,Certainly worth mentioning in the installer that the snaps will be installed during first-boot.
1778226,2018-09-27 17:08:15 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1778226,2018-06-22 23:57:56 UTC,The messages leaking out are IIRC from systemd as mounts get created and so on. I'm not sure what we could do to suppress them.
1778231,2018-06-22 23:21:40 UTC,"Hmm I wonder how d-i handles the glyph issue, does it change console font for each option or something?"
1778232,2018-09-06 16:02:30 UTC,I've added a fix for the second issue as well.
1778232,2018-06-22 14:21:41 UTC,Here is part of the output from the install:
1778232,2018-09-05 14:53:18 UTC,It seems that the root cause is that we kick off apt-mirror in the background but then nearly immediately run the chown line:
1778232,2018-09-06 13:17:37 UTC,"found another bug that causes a symlink that looks like this, which may be the reason PPAs are having issues when used locally:
lrwxrwxrwx 1 root root   47 Sep  5 14:11 '*' -> '/srv/mirrors/archive/mirror/ppa.launchpad.net/*'"
1778232,2018-09-06 13:55:10 UTC,found a third bug where when you run -M the behaviour is not the same as the original run.
1778232,2018-09-06 15:49:48 UTC,"I did test the initial fix in https://people.canonical.com/~jlane/MCS/maniacs-setup and that script appears to run correctly, however my vm's are hanging during commissioning. I haven't looked into the other two issues found in comments #3 and #4 as of yet."
1778232,2018-09-06 16:34:34 UTC,"I've had problems with MAAS running in a VM (VirtualBox, in my case) being unable to commission for years, but I've never gotten around to tracking down the cause. In any event, that problem is most likely unrelated to this one."
1778235,2018-06-22 14:47:11 UTC,"What I have described above has always happened, at least as far as I can remember."
1778246,2019-07-16 20:30:06 UTC,"Ok, then I will basically move all the changes to the 2.1 branch and create a new PR.
I would then close https://github.com/mixxxdj/mixxx/pull/2190 and move the ""is a seek queued""-stuff to a new PR as well.
This should avoid conflicts, right?"
1778246,2019-07-18 20:11:25 UTC,New PR here: https://github.com/mixxxdj/mixxx/pull/2209
1778246,2019-07-16 20:58:04 UTC,Sounds good. Thank you!
1778246,2019-07-15 08:13:18 UTC,"Yes, in this case we may fix the bug in the 2.1 branch only. After merge the related PR, we merge the 2.1 branch into master. In the common case, the fix should not be included in the PR against master to avoid conflicts. Here, we may consider if it is worth the work."
1778246,2019-07-06 22:11:24 UTC,I think https://github.com/mixxxdj/mixxx/pull/2190 is fixing this one as well.
1778246,2019-07-15 06:28:14 UTC,Would also be my assumption. Do I then have to backport it to version 2.1 or what is the policy in Mixxx?
1778248,2018-06-27 03:21:00 UTC,I swear I fixed a bug like this recently.
1778248,2018-08-02 13:06:08 UTC,"Hit this error again, this time in:
FAIL: worker_test.go:897: workerSuite.TestRemovePrimaryValidSecondaries"
1778253,2018-06-22 19:03:42 UTC,The error in your log is:
1778256,2018-06-27 04:48:14 UTC,"change 'btrfs-tools' to 'btrfs-progs | btrfs-tools'
https://gitlab.com/nixtux-packaging/apt-btrfs-snapshot/commit/4773f245bca90f215375bf5472125ba7662075ae"
1778256,2018-06-23 04:20:16 UTC,"The attachment ""Patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1778256,2018-06-24 09:12:30 UTC,"Moved the repository to a new URL: https://gitlab.com/nixtux-packaging/apt-btrfs-snapshot
Fixed building on Ubuntu 16.04 xenial by adding dh-systemd build dependency."
1778256,2018-06-27 05:38:10 UTC,https://gitlab.com/nixtux-packaging/apt-btrfs-snapshot/commit/29e2864ac59e9a73f4f7359da404bb83127d5139 fixed it on Ubuntu 16.04. python3-dist-utils on 18.04 and python3-dist-utils-extra are required. Without them it may just not work or report that the system is lacking snapshot features. This fixed 'system is lacking snapshot features' error on my Ubuntu 16.04 servers and desktops
1778256,2018-06-27 05:39:14 UTC,"I did not update the patch, you may manually pull fixes from my repository"
1778256,2018-10-10 01:28:53 UTC,I'm unsubscribing the Ubuntu Sponsors Team because it should really be merged upstream.
1778256,2018-10-10 06:45:52 UTC,"The upstream of apt-btrfs-snapshot in in Ubuntu, as far as I understand."
1778256,2019-05-05 17:25:59 UTC,Ping. Please at least change dependency from python3-distutils to python3-distutils-extra to fix https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/1763923
1778264,2020-06-05 15:03:30 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1778264,2018-06-24 16:13:13 UTC,Hello
1778264,2020-08-05 04:17:34 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1778264,2018-06-23 04:20:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1778265,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1778265,2018-08-12 17:04:06 UTC,MODULE_SOFTDEP for crc32c is not working for me.
1778265,2018-08-11 19:34:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778282,2018-06-26 00:46:32 UTC,"Installed Kernel v4.18 rc2. Bug was not fixed, therefore adding tag ""kernel-bug-exists-upstream"". I also added the apport information, so I will mark the bug as ""Confirmed""."
1778282,2018-06-25 16:27:56 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1778282,2018-06-23 00:24:18 UTC,Reported on bugzilla.kernel.org/ as per recommendations of apport-collect. Please close.
1778282,2018-06-26 00:43:36 UTC,apport information
1778282,2018-06-22 21:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778282,2018-06-23 00:17:18 UTC,apport information
1778283,2018-10-22 23:08:18 UTC,"we don't currently support detecting that subnets have moved spaces, but this is certainly a known bug w/ reload-spaces."
1778305,2019-07-31 14:31:16 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.opendev.org/673832"
1778305,2019-07-31 14:34:04 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/673833"
1778305,2019-08-07 20:39:48 UTC,"Reviewed:  https://review.opendev.org/673813
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=06ae1ff21495a51d24376c457f51162e17ae3235
Submitter: Zuul
Branch:    stable/stein"
1778305,2019-08-08 01:53:59 UTC,"Reviewed:  https://review.opendev.org/673814
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=11fde850e6163b68e006e746406e6c5e6ac980e0
Submitter: Zuul
Branch:    stable/stein"
1778305,2019-08-08 17:03:01 UTC,"Reviewed:  https://review.opendev.org/673818
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=36246000949f29036ed5b9eed563975d063b29c9
Submitter: Zuul
Branch:    stable/rocky"
1778305,2019-08-12 21:06:44 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1778305,2019-08-09 17:32:49 UTC,"Reviewed:  https://review.opendev.org/673825
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=57538f0d8d11189b348c5820e88169862e25800a
Submitter: Zuul
Branch:    stable/queens"
1778305,2019-08-09 17:49:12 UTC,"Reviewed:  https://review.opendev.org/673827
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97e78f8cc194c60d06a37b11c9c09405bf87b295
Submitter: Zuul
Branch:    stable/queens"
1778305,2019-07-31 14:04:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/673827"
1778305,2019-08-19 15:41:04 UTC,This issue was fixed in the openstack/nova 17.0.12 release.
1778305,2019-09-27 09:01:28 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1778305,2019-08-09 02:31:32 UTC,"Reviewed:  https://review.opendev.org/673821
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=72f9aa720f9137a35d55b9f96e2220d2d0e5588d
Submitter: Zuul
Branch:    stable/rocky"
1778305,2019-07-31 14:01:32 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/673825"
1778305,2019-08-12 20:40:57 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1778305,2019-07-31 13:52:13 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/673818"
1778305,2018-06-25 11:10:27 UTC,It looks like both Service.get_by_host_and_binary and Service.get_minimum_version should not account deleted services.
1778305,2019-07-31 13:57:35 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/673821"
1778305,2018-06-25 11:45:47 UTC,"Which release are you on? Pike I guess? The traceback would be useful, but I'm guessing we're failing as a result of lazy-loading the instance.services field which does a joinedload in the DB API here:"
1778305,2018-07-12 19:40:27 UTC,Thanks for including the debug log.
1778305,2018-07-12 22:05:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/582407"
1778305,2018-06-25 12:26:14 UTC,"We're running Pike (nova 16.1.4), on Centos 7.5 with the RDO packages."
1778305,2019-07-31 06:32:03 UTC,"Reviewed:  https://review.opendev.org/582407
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1d9aaef3d1c880b02d6b7c186e8de79cbaac9ae0
Submitter: Zuul
Branch:    master"
1778305,2019-07-31 08:25:56 UTC,"Reviewed:  https://review.opendev.org/582408
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=16e163053ca39886f11fdb8a3af10a28619fc105
Submitter: Zuul
Branch:    master"
1778305,2019-07-31 13:40:36 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/673813"
1778305,2019-07-31 13:45:00 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/673814"
1778305,2018-07-12 22:05:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582408"
1778311,2019-05-10 16:53:02 UTC,I agree with Remington that the code that causes it to look like you can move and resize columns should be removed until that functionality is available.  Part of the issue currently is that staff get frustrated because the mouse makes it look like they can resize and then it doesn't work.
1778311,2019-05-10 18:20:26 UTC,I agree that the code should be removed until you can actually resize the columns
1778311,2018-06-25 12:41:03 UTC,"If quicker column-resizing is hard to achieve, hover-over tooltips could help in this scenario:"
1778311,2018-11-09 16:32:24 UTC,"We should probably remove the code that causes the mouse cursor ""move"" and ""resize"" icons, since those functions aren't supported yet:"
1778311,2019-05-10 17:14:06 UTC,+1 to Jennifer & Remington
1778314,2019-02-01 19:39:38 UTC,"Still an issue in 3.2, the active column remains FALSE when undeleting a bib record in the web client. Marking Confirmed."
1778314,2020-03-08 14:38:03 UTC,"This, like bug 1845241, is caused by not using the https://bugs.launchpad.net/evergreen/+bug/1845241 API call to undelete the record"
1778317,2020-06-21 04:17:36 UTC,[Expired for gnome-shell-extension-appindicator (Ubuntu) because there has been no activity for 60 days.]
1778322,2019-04-30 10:53:34 UTC,"I don't know if it's related, it probably isn't, but I'll mention it just in case.. I noticed a regression in smbclient and I'm wondering if that's affecting gvfs as well."
1778322,2019-05-07 16:55:43 UTC,"Disco shouldn't have this bug. It (gvfs) will have issues connecting to smb servers that have disabled SMB1, just like bionic and everything in between."
1778322,2019-05-07 16:22:07 UTC,"Um, what about Disco Dingo? 19.04, still having the bug."
1778322,2019-05-07 13:51:23 UTC,"It is, that's all that's needed now. I heard another, unrelated, gvfs SRU was in the works and was hitting problems, though."
1778322,2019-05-07 13:05:22 UTC,"> Is a rebuild/version-bump planned for gvfs Bionic?
"
1778322,2019-05-07 12:33:03 UTC,Is a rebuild/version-bump planned for gvfs Bionic?
1778322,2019-05-03 21:20:49 UTC,"Ah, you said so, sorry"
1778322,2019-05-03 21:20:23 UTC,"@morbius1, how did you disable smb1 on your test samba server? ""server min protocol = SMB2""?"
1778322,2019-05-03 19:33:08 UTC,"@seb128, If the samba share was created on Ubuntu Server and not on Ubuntu Desktop then without the fix you will not see the samba server through Nautilus."
1778322,2019-05-03 17:10:28 UTC,"@seb128, the test case uses a localhost samba server, with a non-guest pub share pointing at /tmp. Not even that was visible in gnome before this fix."
1778322,2019-05-03 16:15:34 UTC,"@Morbius1, the testcase from Andreas showed empty nautilus views though"
1778322,2019-05-03 15:14:53 UTC,"Nice, that's good to know, thanks for pointing it out."
1778322,2019-05-03 14:55:22 UTC,I understand.
1778322,2019-05-03 14:23:48 UTC,"> The original issue was you couldn't get a listing of samba hosts in Nautilus so
> yes that issue is fixed.
"
1778322,2019-05-01 16:33:33 UTC,"A new rebuild is needed. To verify in another way, check the Depends line of the gvfs-backends package:"
1778322,2019-05-01 13:27:56 UTC,Do we need a new rebuild of gvfs in bionic or did the 1.36.1-0ubuntu1.3 update pick up the samba change when it was built?
1778322,2019-04-30 12:33:06 UTC,Thanks Andreas and sorry for posting it here. I was hoping it could be related. Here's the new bug report: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1827041.
1778322,2019-04-30 12:03:11 UTC,"Yes, please open a separate bug report, and attach your smb.conf there please."
1778322,2019-04-29 19:05:51 UTC,Here's a different perspective. Accessing the Win10 machine again:
1778322,2019-05-07 19:46:04 UTC,I found an upstream issue about not being able to get a share list from a machine that has SMB1 disabled: https://gitlab.gnome.org/GNOME/gvfs/issues/307
1778322,2019-04-29 19:32:40 UTC,"I think it's exactly getting the share list using NT1 that is failing. I will look at this tomorrow, see what smbclient -L is doing wrt NT1 temporary downgrade."
1778322,2019-05-07 19:56:59 UTC,I filed https://bugs.launchpad.net/gvfs/+bug/1828107 for the remaining issue of connecting to machines in the windows network tab that have disabled SMB1. Note that a connection made specifically to the machine/ip still works (smb://<ip|name>/)
1778322,2019-06-24 15:45:58 UTC,"In fact I literally just tried it again, and get the same issue, where it does not prompt for login, and the related gvfs process needs to be killed."
1778322,2019-05-08 09:16:45 UTC,(bionic rebuild SRU in the queue now)
1778322,2019-06-24 16:45:31 UTC,"@bloodyiron, you said in https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/81 that you had SMB1 disabled in your network, and I confirmed that with SMB1 disabled there is still a bug, and that bug is https://bugs.launchpad.net/gvfs/+bug/1828107, and it affects all ubuntu releases. I don't know what else to tell you, sorry, it sounds like you are ignoring that open bug."
1778322,2019-04-29 18:17:59 UTC,"smbclient -L, ""gio mount smb://server/share ', even just specifying smb://server/share in the location bar in Nautilus works just like you would expect."
1778322,2019-06-25 04:26:19 UTC,"@andreas oops I think I got muddled up, sorry about that! I'm going to unsub from this bug (which I should have done earlier)."
1778322,2019-06-24 15:44:54 UTC,"The bug still exists for me on Disco, so I don't see how you arrive at the position that it ""works"" out of the box. It does not ""work"" for me, the bug exists on Disco for me. And I've regularly kept my system up to date. I've reported this multiple times in this thread and seem to be ignored."
1778322,2019-06-24 13:38:56 UTC,Disco works out of the box wrt this bug specifically. Which is expected since it has the same fix.
1778322,2019-06-24 11:29:51 UTC,This bug was fixed in the package gvfs - 1.36.1-0ubuntu1.3.2
1778322,2019-06-24 10:10:16 UTC,This bug was fixed in the package gvfs - 1.38.1-0ubuntu1.3.1
1778322,2019-06-24 10:00:16 UTC,"The verification of the Stable Release Update for gvfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1778322,2019-06-21 23:09:18 UTC,Can we also get this bug marked as Disco to? Not just Bionic and Cosmic? I'm _still_ getting the issue with a fully updated Disco (19.04).
1778322,2019-05-08 02:45:34 UTC,"I have the issue in Disco... and have since I upgraded to it, as I mentioned https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/35."
1778322,2019-06-21 21:39:08 UTC,Cosmic verification
1778322,2019-05-27 16:40:06 UTC,"Well I know for a fact it has SMB1 disabled, as I disabled it myself. Ran the test you asked, didn't output any info that seemed to conclusively say which protocols were visible. I'm intentionally disabling SMB1 for the very public security concerns. In this case, the ""server"" has a minimum protocol set to SMB2."
1778322,2019-05-27 12:25:49 UTC,"@Bloodyiron, please run ""nmblookup -M <yourworkgroupname>"" and check if the machine that is listed has SMB1 disabled or not. If it has SMB1 disabled, then it's https://bugs.launchpad.net/gvfs/+bug/1828107"
1778322,2019-05-21 21:31:00 UTC,"I'm using Disco as my daily driver and I still have this issue every time I reboot. I also update nearly daily from the main repos, so any fixes that may have rolled out, thus-far, aren't fixing it."
1778322,2019-06-25 12:40:30 UTC,"No worries, thanks for following up"
1778322,2019-05-21 19:43:39 UTC,"Hello Sebastian, or anyone else affected,"
1778322,2019-05-08 14:39:16 UTC,Try the test case in a disco vm
1778322,2019-05-08 12:28:13 UTC,"The ""windows network"" tab depends on an election to happen between the smb servers, and a master browser being elected. It's the master browser that is contacted for the list of machines in the network. If that machine has smb1 disabled, for example, then this won't work, because it will hit #1828107 (that's my understanding)."
1778322,2019-05-08 09:26:19 UTC,"The bug should be fixed in Disco, samba 2.4.10 includes the function and gvfs there has the patch and was rebuilt with it"
1778322,2019-05-08 09:20:37 UTC,Cosmic uploaded as well
1778322,2019-06-21 21:14:21 UTC,Bionic desktop verification
1778322,2019-04-29 17:47:28 UTC,"I indeed think interacting with a server that has disabled SMB1 entirely is a related, but different problem. Can you get smbclient -L to work with such a server, using the netbios hostname, or does it fail when listing the shares?"
1778322,2019-05-21 19:46:07 UTC,"Hello Sebastian, or anyone else affected,"
1778322,2019-04-29 15:03:54 UTC,"My post concerns Ubuntu Disco. I'm guessing Win10 sees the SMBv1 connection, rejects it outright, and never gets to the protocol negotiation phase."
1778322,2019-03-27 18:30:20 UTC,"Builds in a ppa look good:
...
Native dependency smbclient found: YES 0.2.3
Checking for function ""smbc_setOptionProtocols"": YES
..."
1778322,2019-03-10 19:45:33 UTC,Looking at this next.
1778322,2019-01-15 16:20:21 UTC,"Reopening, the fix isn't working until we get the samba change"
1778322,2019-01-15 15:46:36 UTC,This bug was fixed in the package gvfs - 1.36.1-0ubuntu1.2
1778322,2019-01-15 15:44:31 UTC,This bug was fixed in the package gvfs - 1.38.1-0ubuntu1.1
1778322,2018-12-07 12:41:07 UTC,"The samba commit seems to be
https://github.com/samba-team/samba/commit/0dae4e2f"
1778322,2018-12-07 12:36:49 UTC,"Thanks for the testing. Indeed there is a problem, from the build log"
1778322,2018-12-01 22:13:46 UTC,"And line 270 in Gvfs log:
Server connect ok: //TOMATO/IPC$: 0x7f72b4020fd0
smb-network: do_mount - [smb://DOMOWA; 0] dir = (nil), cancelled = 0, errno = [0] 'Succes'
smb-network: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking
smb-network: send_reply(0x556b8fdb32b0), failed=1 (Downloading resources list from server failed: Succes)
Performing aggressive shutdown.
smb-network: purging server cache
Context 0x7f72b4010b60 successfully freed
Freeing parametrics:
network: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: given location is not mounted"
1778322,2018-12-01 22:04:36 UTC,"I'm sending Gvfs log.
Interesting part starts at line 173:"
1778322,2018-12-01 21:22:36 UTC,"I have checked bionic-proposed repo and listed packages have installed:
gvfs-backends/bionic-proposed,now 1.36.1-0ubuntu1.2 amd64 [installed]
gvfs-bin/bionic-proposed,now 1.36.1-0ubuntu1.2 amd64 [installed]
gvfs-common/bionic-proposed,now 1.36.1-0ubuntu1.2 all [installed]
gvfs-daemons/bionic-proposed,now 1.36.1-0ubuntu1.2 amd64 [installed]
gvfs-fuse/bionic-proposed,now 1.36.1-0ubuntu1.2 amd64 [installed]
gvfs-libs/bionic-proposed,now 1.36.1-0ubuntu1.2 amd64 [installed]
gvfs-libs/bionic-proposed,now 1.36.1-0ubuntu1.2 amd64 [installed]"
1778322,2018-11-21 16:08:40 UTC,"Hello Sebastian, or anyone else affected,"
1778322,2018-11-20 17:57:44 UTC,"Hello Sebastian, or anyone else affected,"
1778322,2018-11-20 17:32:01 UTC,"Hello Sebastian, or anyone else affected,"
1778322,2018-11-13 17:05:41 UTC,The fix is in https://launchpad.net/ubuntu/+source/gvfs/1.38.1-1ubuntu1
1778322,2018-07-06 00:12:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778322,2018-06-23 08:19:28 UTC,"The attachment ""gvfs-smb-browse change to NT1 from RedHat Bugzilla"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1778322,2018-06-23 07:49:14 UTC,Simpler form of before posted patch.Ehh
1778322,2018-06-23 07:45:14 UTC,A patch for gvfs-smb-browse to switch to NT1
1778322,2019-04-29 17:28:43 UTC,"Your reference to the Linux Samba Server command: smbstatus got me thinking what would happen if I disabled NT1 on a Linux Samba server by stipulating ""server min protocol = SMB2"" and using Windows Network > ... to connect."
1778322,2019-03-27 21:00:50 UTC,"I just tried with my build from the ppa, but it's not working. When enabling debugging in gvfsd, I can see it setting the protocol to NT1:"
1778322,2019-03-28 13:53:15 UTC,"The original samba patch had a typo/error, this is the fix for that:"
1778322,2019-05-08 13:56:48 UTC,"Okay but it isn't fixed in Dingo. I still get it. What more do you want me to do, not say it's happening for me in Disco Dingo? Because it is..."
1778322,2019-04-02 18:20:48 UTC,Does the samba task need fixing in disco at all?
1778322,2019-04-29 13:31:03 UTC,Does this also happen with Ubuntu Disco? I checked upstream and there were no other changes following this one in that file:
1778322,2019-04-25 05:09:06 UTC,"Checked smb.conf so far only seeing ""client min protocol = SMB2"" which should not be causing this problem..."
1778322,2019-04-24 13:25:56 UTC,"Check your smb.conf, maybe you have some overriding setting in there. The default disco install I tested had no config file."
1778322,2019-04-24 12:57:20 UTC,"@Andreas , I already have those installed. Still seeing the same effect each reboot."
1778322,2019-04-22 14:05:13 UTC,It worked just fine on a disco desktop default install.
1778322,2019-04-22 13:54:26 UTC,"I checked disco when I prepared these updates for bionic and cosmic, and it was allright. Let me re-check with a default install using the CD this time, now that it is released."
1778322,2019-04-19 16:39:25 UTC,"Also, since samba package isn't installed by default (at least in my 18.10 to 19.04 upgrade), how do we fix this without the samba package installed?"
1778322,2019-04-19 16:38:38 UTC,I'm seeing this issue with Disco Dingo 19.04
1778322,2019-04-08 12:45:16 UTC,This bug was fixed in the package samba - 2:4.7.6+dfsg~ubuntu-0ubuntu2.9
1778322,2019-04-08 12:44:55 UTC,This bug was fixed in the package samba - 2:4.8.4+dfsg-2ubuntu2.3
1778322,2019-04-28 14:06:30 UTC,There is an issue with this fix that makes it impossible to access a Windows 10 machine that has disabled SMB1 ( NT1 ):
1778322,2019-04-05 16:09:21 UTC,Cosmic verification (continued)
1778322,2019-04-05 15:58:28 UTC,Cosmic verification
1778322,2019-04-05 15:34:44 UTC,Bionic:
1778322,2019-04-05 15:34:18 UTC,Bionic verification (continued)
1778322,2019-03-28 14:40:57 UTC,"It worked with the updated patch. Packages rebuilt in the PPA. I'll prepare a merge proposal and SRU this into bionic. We will have to rebuild gvfs there, though, after samba lands in proposed."
1778322,2019-04-05 15:18:40 UTC,Bionic verification
1778322,2019-04-03 12:44:28 UTC,"For anyone wanting to test this bug, please note you will also have to wait for a gvfs rebuild with this new samba package."
1778322,2019-04-02 20:10:39 UTC,"Hello Sebastian, or anyone else affected,"
1778322,2019-04-02 18:57:39 UTC,"Hello Sebastian, or anyone else affected,"
1778322,2019-04-05 16:10:12 UTC,"I think I mixed the verification-done tags, but both are done now."
1778323,2018-11-07 19:18:44 UTC,"I haven't experienced this for a while now (since 4.19-rc1?), can be closed."
1778323,2018-07-11 19:14:21 UTC,"Ok uploaded different dmesgs for the same kernel when the touchpad is working and not. (Two examples of when it's working)
When it's not working, the computer won't reboot/halt either."
1778323,2018-07-09 07:49:12 UTC,"Actually it didn't get solved with 4.18-rc3, but rather works on some boots.
Tried rc4 now and problem remains, I just haven't rebooted enough."
1778323,2018-07-03 16:53:17 UTC,"Amazingly enough these issues seem resolved in 4.18-rc3! So 4.17 through 4.18-rc2 are affected, likely 4.17-rc? too.
Only weirdness in dmesg now is this, but I'm not sure of the implications:"
1778323,2018-07-02 03:12:41 UTC,Can you do a kernel bisection?
1778323,2018-06-29 17:57:23 UTC,Not sure if you get these updates without a comment but I did try 4.18-rc2 and bug is still present.
1778323,2018-06-23 08:00:05 UTC,This change was made by a bot.
1778323,2018-06-25 16:22:13 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1778332,2018-11-01 15:19:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778332,2019-07-02 16:21:02 UTC,"Thank you for your bug report, do you still get that issue? What Ubuntu version do you use? What actions do you do exactly to trigger the errors?"
1778332,2019-09-01 04:17:24 UTC,[Expired for gnome-system-monitor (Ubuntu) because there has been no activity for 60 days.]
1778332,2019-11-11 15:52:45 UTC,My System 76 Oryx Pro laptop is currently experiencing a severe battery drain.
1778332,2019-11-22 17:38:54 UTC,"Nov 11 09:47:56 <hostname> kernel: audit: type=1400 audit(1573487276.018:797080): apparmor=""DENIED"" operation=""open"" profile=""snap.gnome-system-monitor.gnome-system-monitor"" name=""/run/systemd/sessions/c1"" pi d=8733 comm=""gnome-system-mo"" requested_mask=""r"" denied_mask=""r"" fsuid=1000 ouid=0"
1778332,2019-11-22 17:40:24 UTC,"Clement, your issue is different than Charles'. More information is required from you to triage your issue."
1778337,2018-06-28 13:05:53 UTC,"Darrel, I am not ignoring this, the bug is most likely upstream but I will look into it as soon as I have time. This is a very busy period for us (having just released) and limited resources means we have to prioritise, so please understand it might be a while before I can offer anything useful but I'll do everything in my power to keep this wait to a minimum."
1778337,2018-06-28 14:51:18 UTC,"Thanks Mark I appreciate that. Is there anyone upstream that I should be
talking with or should I leave it in your court?"
1778337,2018-06-26 19:00:31 UTC,"Have you installed Bible Analyzer, looked at the Hebrew display and/or
found a solution yet?"
1778337,2018-06-27 21:39:00 UTC,"Have you installed Bible Analyzer, looked at the Hebrew display and/or
found a solution yet?"
1778337,2018-06-25 17:47:00 UTC,"Hi Mark,"
1778337,2018-06-28 07:12:33 UTC,Any response yet?
1778337,2018-06-23 12:49:18 UTC,"is this:
https://i.imgur.com/wnJKPgQ.png
not what it's supposed to look like ?"
1778337,2018-06-23 12:23:54 UTC,"Have you tried installing the python-wxgtk3.0 pythom module ?
sudo apt-get install python-wxgtk3.0"
1778337,2018-06-23 18:55:44 UTC,"Hello Mark,"
1778337,2018-06-23 12:46:16 UTC,"I'm lost, what am I supposed to do with that python script ?"
1778339,2020-04-15 23:45:42 UTC,Hmm.. The new version was there to prevent odd messages from the package system. I suppose this is history now?
1778339,2020-06-15 04:17:39 UTC,[Expired for fonts-guru-extra (Ubuntu) because there has been no activity for 60 days.]
1778343,2020-03-28 16:43:48 UTC,Closing because INVALID: No additional information provided/test svg has no text. Additional testing could not be done.
1778345,2018-06-25 17:57:36 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1778345,2018-06-25 18:00:07 UTC,This change was made by a bot.
1778350,2018-06-25 17:46:16 UTC,CC Michael Tsirkin
1778350,2020-08-12 12:46:54 UTC,"No feedback for almost two years, closing."
1778350,2018-09-25 17:34:19 UTC,@navicrej -- can you please apply the series
1778350,2018-07-08 13:58:23 UTC,I compiled the 4.4.4-r5 branch but I was not able to change the kernel yet.
1778350,2018-07-02 21:33:03 UTC,"I looked at it and while I might be wrong, I suspect
it's a bug in ACPI parser in that version of Linux.
Is there a way for you to try a later Linux version?
Alternatively, I tried to build 4.4-rc2 on Fedora and couldn't."
1778350,2018-06-26 09:13:12 UTC,"Nevermind that, just found out how to run:"
1778350,2018-06-25 10:53:31 UTC,After 'git bisect' -ing it I found the commit that is responsible for this:
1778350,2018-06-25 22:30:12 UTC,"On Mon, Jun 25, 2018 at 01:46:16PM -0400, John Snow wrote:

> CC Michael Tsirkin
>
> On 06/25/2018 06:53 AM, navicrej wrote:
> > After 'git bisect' -ing it I found the commit that is responsible for
> > this:
> >
> > https://git.qemu.org/?p=qemu.git;a=commitdiff;h=9fa99d2519cbf71f871e46871df12cb446dc1c3e
> >
"
1778350,2018-06-26 08:26:23 UTC,I don't know if there is another way to do that but I changed the properties of x-pci-hole64-fix in hw/pci-host/piix.c and hw/pci-host/q35.c to false on current master and compiled and now it works again.
1778352,2018-06-23 17:06:59 UTC,"Please don't let the 'options' addition at the end of /etc/modprobe.d/alsa-base.conf mislead you - there was no output device shown before I added it, nor after I commented it out and restarted my PC."
1778357,2019-03-30 02:16:53 UTC,The main branch is not open for new features yet.  Patience... :-)
1778357,2019-10-30 06:59:47 UTC,"OK, we've been patient.  Progress? ;-)"
1778357,2019-10-30 13:19:21 UTC,"This is behind a few other wishlist items.  While I understand your concern, if you follow the bug tracker over time, you will notice that everyone feels the same way about their favorite issue. :)"
1778357,2019-10-30 22:21:11 UTC,"Copy/paste works in version 6.0 between footprints, footprints and the board, etc.  It doesn't yet support multiple MIME types (ie: you can't copy some stuff from a footprint and paste it into an email message as a jpg/png/what-have-you)."
1778357,2019-03-30 00:32:50 UTC,Some advance for this feature at Nightly versions?
1778357,2018-09-12 12:08:06 UTC,Linked: https://bugs.launchpad.net/kicad/+bug/1769957
1778357,2018-06-29 11:32:27 UTC,This affects https://bugs.launchpad.net/kicad/+bug/1728264
1778357,2018-12-11 19:28:02 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1778359,2018-06-23 21:23:52 UTC,"Power down, boot, another execution of Software Updater solves the problem."
1778359,2018-10-29 12:56:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778359,2018-10-29 12:58:28 UTC,This problems occurs since updating to Ubuntu 18.04. It is great to must restart Ubuntu to run the software updater.
1778363,2018-08-28 19:17:10 UTC,"Are you saying that given the same input mbox file that 'bin/arch --wipe' throws the UnicodeDecodeError with Mailman 2.1.26 but not with 2.1.16? If so, that's strange as there are no changes between 2.1.16 and 2.1.26 in pipermail.py in the area of 'fixAuthor', and there don't seem to be any Debian patches in this area either."
1778363,2018-06-23 22:42:29 UTC,"This may have something to do with the archive database. You can try the script at https://www.msapiro.net/scripts/hddump to dump the database for the affected period with --verbose and look for values of 'author' and 'decoded'['author']. Is there anything unusual in those or anything with a number like 'Doe, John 3rd'."
1778363,2018-08-20 20:11:55 UTC,I am experiencing the same issue migrating from 2.1.16 (on Ubuntu 14.04) to 2.1.26 (18.04).
1778363,2018-08-20 20:16:03 UTC,"As this was a blocker for the migration, I rsynced the /usr/lib/mailman directory from the 2.1.16 installation onto the new machine and the bin/arch/wipe worked again."
1778366,2018-07-11 09:35:19 UTC,"For more detail: The question is whether raw_description is intended to get the Description field in the packages file, which it does; or whether it's intended to get the unformatted translated description."
1778366,2018-06-24 08:40:53 UTC,Not sure if bug or feature. Will need to investigate a bit more
1778370,2018-06-24 01:17:48 UTC,"I have noticed this happening for years now, does not seem to matter which packages ...tasksel fails if too many packages are ticked"
1778370,2018-06-25 09:02:15 UTC,from DpkgTerminalLog.txt:
1778370,2018-06-25 09:06:52 UTC,"I think it's systemd listening on :6600 because of mpd.socket; I don't understand why the postinst (debhelper-added stuff, probably from dh_systemd) would try to start a service that's disabled??"
1778375,2018-07-14 11:19:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778380,2017-04-04 17:34:40 UTC,"As the tile says, the panel locks up when the context menu (right click menu on an application's panel object in the task bar) is open while any application with an object in the task bar terminates."
1778380,2017-12-15 15:55:37 UTC,It's still a thing in panel version 4.12.2.
1778380,2018-07-24 20:19:13 UTC,Still a thing in version 4.12.4
1778380,2018-08-12 10:03:28 UTC,"According to https://bugzilla.xfce.org/show_bug.cgi?id=13600, this bug is fixed in version 4.13."
1778380,2018-12-01 18:09:08 UTC,"This is very likely fixed in 4.13, as reported in Bug 13600.
Can you check this version?"
1778380,2019-03-21 11:05:22 UTC,Fixed in 4.13.0. Thank you for your time and efforts.
1778382,2018-12-11 19:19:30 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1778382,2018-12-11 03:40:21 UTC,I'm not sure that I like the checkbox feature here.  I test drove this today and have some qualms.
1778382,2018-12-11 14:52:26 UTC,"@Seth, I completely agree with you, I don't really know why I submitted that patch (at least it helped me when I needed it)"
1778391,2019-09-18 04:17:31 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1778391,2019-07-19 18:42:29 UTC,"Thanks for filing the bug.
Here's my best guess:"
1778392,2019-11-21 22:44:10 UTC,"connectome-workbench is a viewer and analysis tool for neuroimaging data, this bug was assigned to the wrong package."
1778392,2019-12-12 22:12:29 UTC,Taking a guess that openstack is the intended package for this bug.
1778396,2020-04-20 07:44:51 UTC,"I think wayland is not the default anymore, marking as incomplete for now"
1778396,2020-06-20 04:17:21 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1778399,2018-06-29 08:44:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778402,2018-06-26 08:17:36 UTC,"This looks like a bug in the display drivers though. A bug in VLC can only crash the VLC process, not the whole X server."
1778402,2018-06-26 12:21:22 UTC,"The X server ist not crashing, just halted.
After killing VLC, X is continuing."
1778402,2018-09-04 07:27:51 UTC,Let's reassign this to the nvidia driver.
1778403,2018-06-24 16:21:58 UTC,"The attachment ""bwm-ng-timestamp.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1778410,2018-06-24 15:00:04 UTC,This change was made by a bot.
1778414,2019-07-31 15:13:56 UTC,"Following up, I've pushed this change to master for inclusion in 3.4. I've also pushed a follow-up adding the menu item to the Angular version of the menus. Thanks, Garry and Meg!"
1778414,2019-06-04 19:54:28 UTC,This was discussed during today's development meeting:
1778414,2019-05-31 14:22:05 UTC,Some reading for the discussion:
1778414,2019-05-22 21:41:39 UTC,Tested on 5/22/2019. Item status appears in cataloging drop-down menu (as well as in circulation menu-- needsdiscussion tag likely still applies).
1778414,2019-02-13 23:00:59 UTC,"Adding needsdiscussion tag, since I think that we need to have a larger conversation outside of Launchpad to help us out here."
1778414,2018-10-16 23:13:44 UTC,"I agree about reducing clutter.  I've always thought of Item Status as being pretty useful for circ folks, but essential for catalogers, though.  What would people think about removing it from the Circ menu, and adding it to the Cataloging menu?"
1778414,2018-06-28 16:22:43 UTC,"Thanks Kathy for pointing us to the previous conversation.  I'm torn between getting rid of clutter and adding menu options where different users expect the options to be.  I personally would rather get rid of all the duplicates and have less clutter.  I like simple, but I also have to listen to my users who have expressed the desire for duplicate menu options."
1778414,2018-06-28 15:40:12 UTC,"Before this feature goes in, I would like to point to the previous discussion we had on bug 1528912 where we discussed adding the Replace Barcode option to both the Circulation and Cataloging menus. There was an opinion at the time that reducing duplicate menu entries would be one way to meet the goal of reducing clutter in the web client."
1778414,2018-06-27 20:21:08 UTC,A proposed patch is here. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=615cb9a7b72dd70b8fa0250b8c8f81c6640923dd
1778416,2018-09-02 18:22:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778418,2018-06-24 18:32:33 UTC,I can't seem to reproduce. Can you provide a screenshot?
1778418,2018-06-24 21:25:14 UTC,"I can reproduce: in a new account, I moved the window applet to the top panel, then opened Caja and Firefox, and then moved the mouse along the top edge."
1778418,2018-06-25 17:30:35 UTC,Everything's okay here!
1778418,2018-07-01 09:28:23 UTC,Updated the description - this isn't just affecting the window list but a general panel issue.
1778418,2018-10-20 16:45:06 UTC,issue is still present in 18.10
1778418,2019-02-24 17:31:38 UTC,tried a 19.04 daily build and the issue is present there also
1778418,2019-06-09 22:53:16 UTC,"This also affects the left-edge of the screen.
I made a video screencast of the panel-at-bottom, where mouseover/click isn't registering along the left side of the Start button. https://github.com/mate-desktop/mate-panel/issues/940#issuecomment-498050207"
1778418,2019-07-21 06:02:03 UTC,A workaround has been posted here: https://ubuntu-mate.community/t/tip-to-fix-un-clickable-menu-and-show-desktop-buttons/19928
1778421,2018-07-03 07:37:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778422,2018-11-03 14:18:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778422,2018-11-03 14:27:53 UTC,"This happens in 18.04 too. Bug #1650076 does also, and I'm not 100 % sure if these are two different issues or the same. I was able to reproduce #1650076 with the steps listed there, but just before that I had Evince following my scroll wheel despite being unfocussed, and I had not selected anything in the PDF before that (at least not knowingly). I haven't found the steps to reproduce this without the selection though."
1778423,2020-03-11 13:43:44 UTC,"Workaround is change directory by hand in dconf Editor (in org - blueman - trasfer, then double click on path)"
1778429,2019-04-18 22:07:56 UTC,"Took another crack at debugging this and got my package upgraded. I get the same freeze if I set RESUME=None, but if I set `RESUME=UUID=$(blkid -s UUID -o value ""/dev/mapper/cryptswap1"")` I was able to get the old behaviour back on the newer initramfs-tools"
1778429,2019-07-05 07:06:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778429,2019-07-05 07:08:01 UTC,"This bug does effect me too, disabling avoids 'quiet splash' the issue."
1778437,2019-06-13 21:34:18 UTC,"Fixed in revision 158e05adea7a48b5f5e520a94d7ca7557fc2f2b7
https://git.launchpad.net/kicad/patch/?id=158e05adea7a48b5f5e520a94d7ca7557fc2f2b7"
1778437,2019-01-09 16:32:09 UTC,"This is undoubtedly annoying - but since the hotkeys stuff is generally quite bound up with the legacy definitions, this might be more tractable in v6, when all the hotkeys come from only new-style TOOL_ACTIONs?"
1778437,2019-01-10 05:52:35 UTC,"Agreed.  Jeff, are you ok with this pushing to post 5.1?  If not, please set it back"
1778437,2019-01-10 13:17:26 UTC,"@Seth, absolutely.  Modifying any of the hotkeys stuff seems to have a higher incidence of regressions than most other areas."
1778439,2019-06-12 21:24:54 UTC,"Reviewed:  https://reviews.mahara.org/9947
Committed: https://git.mahara.org/mahara/mahara/commit/a07cd80ac15793511f02bbbf6a82713023107fe2
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1778439,2019-05-02 13:10:16 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9947"
1778439,2018-06-25 00:57:02 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/8973"
1778439,2018-06-26 02:48:19 UTC,"Reviewed:  https://reviews.mahara.org/8973
Committed: https://git.mahara.org/mahara/mahara/commit/2cfa4ac58ed9e2dfa1d4bdc3f3e27bcea23e0223
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1778443,2018-07-23 06:53:44 UTC,Fix merged
1778446,2018-07-18 02:39:41 UTC,code merged.
1778449,2018-06-25 11:31:26 UTC,nice catch!
1778449,2020-04-10 13:32:12 UTC,"Hi, this has been fixed in a recent development version, see https://gitlab.com/inkscape/inkscape/-/commit/6bbeb3d1be7b279c941a500d731f315954ae3f6c."
1778464,2018-07-15 05:06:26 UTC,"This is happening very often - I attempt to load an app and the load fails due to the reported issue. I have not reported this every time it has happened - if I did, you would be hearing from me quite often."
1778466,2018-08-09 08:51:10 UTC,"Thanks for the report Darko. What you describe sounds like an upstream issue. I did a cursory search in the upstream bug database, but couldn't find any existing bug matching your description. Would you wind filing one at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice, and sharing the bug number here? Thanks!"
1778466,2018-08-09 10:05:19 UTC,"@osomon done!
https://bugs.documentfoundation.org/show_bug.cgi?id=119168"
1778473,2020-11-11 15:09:44 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1778473,2021-01-11 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1778476,2018-07-17 08:51:58 UTC,"Bug reported upstream:
https://github.com/hadess/iio-sensor-proxy/issues/231"
1778476,2018-06-25 09:02:29 UTC,apport information
1778476,2018-06-27 12:44:48 UTC,I now have 4.18.0-041800rc2-generic #201806241430 SMP Sun Jun 24 14:33:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.
1778476,2018-06-26 20:42:33 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1778476,2018-07-23 12:21:36 UTC,"upstream (iio-sensor-proxy, not the kernel project) classified this bug as ""won't fix"" because ""Load average is not a good representation of the CPU (or other resource) usage caused by an application."""
1778476,2019-02-06 14:07:55 UTC,"No I don't have any /dev/bus/iio ( or /sys/bus/iio ), neither with v4.15.* nor with HWE/4.18.0-14-generic"
1778476,2018-10-03 09:06:01 UTC,"With this service enabled, acpi is sending about 100 interrupts per second."
1778476,2018-10-03 14:50:59 UTC,"Looks like the sensor has different mappings for different HP models.
Can you refer to [1] to see what mapping really works for your models?"
1778476,2018-12-14 01:58:10 UTC,"is /dev/bus/iio even properly populated?
See LP: #1807250 LP: #1804804 LP: #1792813"
1778476,2018-06-25 09:02:28 UTC,apport information
1778476,2018-10-02 15:18:28 UTC,Maybe run `watch -n0 cat /proc/interrupts` and see if there's any spurious interrupt.
1778476,2018-06-25 09:02:26 UTC,apport information
1778476,2018-06-25 09:02:12 UTC,apport information
1778476,2018-06-25 09:02:24 UTC,apport information
1778476,2018-06-25 09:02:23 UTC,apport information
1778476,2018-06-25 09:02:21 UTC,apport information
1778476,2018-06-25 09:02:19 UTC,apport information
1778476,2018-06-25 09:02:18 UTC,apport information
1778476,2018-06-25 09:02:16 UTC,apport information
1778476,2018-06-25 09:02:13 UTC,apport information
1778476,2018-06-25 09:02:25 UTC,apport information
1778476,2018-06-25 08:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778486,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1778486,2018-08-17 15:41:21 UTC,The fix is not present in -32. It seems to be scheduled for -33.
1778486,2018-08-16 06:42:49 UTC,"If I'm not mistaken, the fix has been released with the latest kernel update that was pushed for the L1TF issue. So this bug should be ""fix released"""
1778486,2018-08-07 14:01:52 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1778486,2018-06-29 13:23:27 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093604.html"
1778486,2018-06-28 06:20:46 UTC,Thanks Joseph.
1778486,2018-06-25 17:49:26 UTC,"I built a test kernel with the patch in the description.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1778486"
1778486,2018-06-25 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778488,2019-09-19 12:00:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1778512,2018-06-25 12:44:30 UTC,"""sudo alsa force-reload"" command also doesn't help"
1778512,2018-06-25 12:44:32 UTC,"""sudo alsa force-reload"" command also doesn't help"
1778512,2018-06-30 19:28:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778512,2018-06-30 19:30:01 UTC,"I have the exact same problem. I tried upgrading from 16.04 LTS to 17.10 and 18.04, but this doesn't solve the issue for me."
1778521,2019-03-07 18:29:02 UTC,"This is so aggravating, so I'm adding heat. I constantly forget that I need to double-check my transforms and then my report fails."
1778521,2019-11-22 16:54:10 UTC,"This bug can cause transforms to be applied that aren't even in the list of choices for a field.  For example, I was able to add a Boolean field (Item: Is Deleted) with a transform of ""Month of Year"", since I had chosen that transform on a previous field.  However, the only transform available to Boolean fields is ""Raw Data""."
1778521,2020-01-27 14:20:36 UTC,PaILS SPARK group is still experiencing this behavior on version 3.3.5 in Chrome
1778521,2020-02-19 15:40:19 UTC,There is a branch available at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1778521-report-template-field-transform-sticky which resets the field transform each time fields are added to either tab.
1778521,2020-02-20 16:52:18 UTC," have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>."
1778521,2020-02-21 15:21:18 UTC,"Thanks, Dawn!"
1778522,2020-12-03 16:17:18 UTC,"Issue and fix confirmed.  Merged to 3.5 and up.  Thanks, all!"
1778522,2020-11-18 23:08:42 UTC,I think this works well and my signoff is here:
1778522,2020-11-18 22:06:32 UTC,Here's a branch for testing. https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbriem/lp1778522_intentional_precat_creation
1778522,2018-08-10 20:16:31 UTC,We are also seeing this in CW MARS. We recently had a report from a library who uses an RFID scanning pad.
1778522,2018-06-25 16:20:49 UTC,Tested this on a 3.0.7 system and I would say that fixing these two issues would go a long way toward minimizing unintended precats.
1778522,2018-06-25 16:40:44 UTC,"Unfortunately, checking the strict barcode box is not as viable a solution to incorrect scanning as we thought it would be at the time we developed it. Many PINES libraries have a combination of item barcodes with the codabar encoding and older items that are not codabar. Even if the checkout library has all codabar barcodes, items from other libraries may not.  Checking the strict barcode box means check out (or in) of those non-codabar barcodes is stopped. Circ staff generally do not check that box because of this, losing the speed bump."
1778534,2018-07-07 05:49:45 UTC,Thank you too for following up the reports here.
1778534,2018-06-26 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778534,2018-06-27 20:09:34 UTC,"Thank you for providing a patch, and making Ubuntu better."
1778534,2018-06-25 16:20:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1778555,2018-07-10 07:47:57 UTC,The webcam works in Google Hangouts.
1778555,2019-01-07 05:12:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778555,2019-02-12 19:21:25 UTC,"Bug confirmed with three computers, each one using Ubuntu 18.04.  Webcam works (tested with Camorama) but Cheese can't detect it."
1778555,2019-02-12 20:06:02 UTC,The errors are similar to the ones on https://bugzilla.gnome.org/show_bug.cgi?id=795022
1778555,2019-02-19 19:35:33 UTC,"On 12/02/2019 22:06, Sebastien Bacher wrote:

> The errors are similar to the ones on
> https://bugzilla.gnome.org/show_bug.cgi?id=795022
>
> Do you have pipewire installed?


I does not work neither with pipewire installed nor not installed."
1778555,2018-06-26 22:18:49 UTC,It does not work with the upstream kernel.
1778555,2018-06-26 20:40:04 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1778555,2018-06-25 19:55:01 UTC,apport information
1778555,2018-06-25 19:54:59 UTC,apport information
1778555,2018-06-25 19:54:58 UTC,apport information
1778555,2018-06-25 19:54:57 UTC,apport information
1778555,2018-06-26 21:52:59 UTC,"On Tue, 2018-06-26 at 20:40 +0000, Joseph Salisbury wrote:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular
> problem?
"
1778555,2018-06-25 19:54:52 UTC,apport information
1778555,2018-06-25 19:54:50 UTC,apport information
1778555,2018-06-25 19:54:49 UTC,apport information
1778555,2018-06-25 19:54:48 UTC,apport information
1778555,2018-06-25 19:54:46 UTC,apport information
1778555,2018-06-25 16:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778555,2018-06-25 19:54:42 UTC,apport information
1778555,2018-06-25 19:54:43 UTC,apport information
1778555,2018-06-25 19:54:55 UTC,apport information
1778555,2018-06-25 19:54:44 UTC,apport information
1778557,2018-06-26 17:34:33 UTC,"This is actually an issue with the apport package hook for cheese, found in /usr/share/apport/package-hooks/source_cheese.py. Here's the offending code:"
1778563,2018-08-06 09:19:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/589085"
1778563,2020-03-10 16:07:05 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/712118"
1778563,2020-03-12 17:09:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/712741"
1778563,2020-04-20 19:17:05 UTC,"Reviewed:  https://review.opendev.org/589085
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=580eedbe2df83df9a267f529a8d12230e7081d3f
Submitter: Zuul
Branch:    master"
1778563,2020-04-21 00:42:57 UTC,"Reviewed:  https://review.opendev.org/712741
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2e0afc1f72db5cb56ed987e2873798fc1e89545
Submitter: Zuul
Branch:    master"
1778565,2018-09-24 14:57:14 UTC,The value is not a arbitrary value. It is well thought out. For me doble click registers every time. May be some issue with input devices ?
1778565,2018-06-25 16:49:18 UTC,I've attached the alternative patch for gtk/window-decorator/events.c.
1778566,2018-06-26 02:06:26 UTC,Please run 'lspci -k' and send us the output.
1778566,2018-06-26 14:51:49 UTC,I attached the requested output.
1778566,2018-06-27 02:17:40 UTC,"Thanks. The problem seems to be specific to the radeon driver. Maybe even specific to your ATI ES1000 GPU, which I haven't seen before:"
1778566,2018-06-27 02:20:44 UTC,I suggest you stick to Xorg sessions while the bug exists. You can make it permanent by uncommenting:
1778566,2018-06-27 06:44:42 UTC,I will report it there. But are you sure that is not a Wayland issue? That something on the graphics loop can block the whole execution of the program and be woken up by mouse movement sounds like a deep architectural problem to me.
1778566,2019-02-08 18:54:05 UTC,I forgot to link the upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/204
1778566,2019-03-29 13:37:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778567,2018-08-15 21:05:49 UTC,I'm confirming this because I have seen it in Evergreen 3.0.10.
1778567,2018-08-22 20:27:42 UTC,Also confirmed in 3.0.9
1778567,2018-08-24 19:27:17 UTC,Refreshing the check in screen and re-scanning the item is working for us too.  Thanks for posting that John!
1778567,2019-08-12 23:54:32 UTC,Confirming that this is still an issue in 3.3
1778567,2020-01-30 18:47:30 UTC,It appears that the check in screen can only handle retrieving the address for the library of the first transit done since the check in screen was opened.
1778569,2018-06-26 15:32:07 UTC,"having got ir-keytable the way I want it and all key codes working with vlc and liblic-client0 removed, I then reinstalled vlc and all the key codes still worked, even after a reboot. So now I'm guessing that liblirc-client0 prevents proper setup of the key codes if it is installed, but after it's already been setup, it has no effect on them. Maybe someone else can figure out what is going on."
1778569,2018-06-27 17:02:05 UTC,"OK, I changed one key code and then issued this command;
root@mythfe0:/home/wes# ir-keytable -c -w /etc/rc_keymaps/myremotes
Then tested that it worked like this]
root@mythfe0:/home/wes# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
555.460958: event type EV_MSC(0x04): scancode = 0x28
555.460958: event type EV_KEY(0x01) key_down: KEY_SEMICOLON(0x0027)
555.460958: event type EV_SYN(0x00).
;555.566930: event type EV_MSC(0x04): scancode = 0x28
555.566930: event type EV_SYN(0x00).
555.836028: event type EV_KEY(0x01) key_up: KEY_SEMICOLON(0x0027)
555.836028: event type EV_SYN(0x00).
Then tried it in notes clipboard and it didn't work.
Then rebooted and it worked. So I guess it takes a reboot, meaning the ir-keytable -c -w /etc/rc_keymaps/myremotes command doesn't fully support all changes that need to happen for the rc keymap file to work right in other apps. BTW, this was all with vlc installed along with liblirc-client0. With them removed, the changes worked without a reboot iirc. Might want to close this out. I don't know."
1778569,2019-01-23 19:35:59 UTC,"To further investigate this issues, a question is if the main lirc package is installed. If so, the lircd.socket, lircd.service and lircd-uinput.services should be disabled and stopped. If problem persists, with or without liblircclient installed, this should be re-assigned to the kernel"
1778574,2018-06-25 19:23:01 UTC,"I made a simplified version of this file, then uploaded the wrong one. Attached, with updated output files. I've stripped out all other objects and layers, and any XML nodes that didn't appear to affect the drawing on the screen."
1778574,2018-06-25 18:21:30 UTC,"- reproduced when I use the tab called ""Page"" as the export area
- not reproduced when I use the tab called ""Drawing"" as the export area. attached is the result in this case. The Drawing tab modifies the border position x0, y0 to solve the problem. (Don't know what controls x0, y0.)"
1778574,2018-06-25 19:24:06 UTC,"Output from pattern error v4 when using ""Page"" selection"
1778574,2018-06-25 19:24:56 UTC,"Output from pattern error v4 when using ""Drawing"" selection"
1778574,2018-06-25 21:27:51 UTC,"well, that is strange, here is the output I get when I export the file ""pattern_v4"" using ""Drawing"". The output looks correct, as far as I can tell."
1778574,2018-06-25 21:28:22 UTC,here are the settings I used
1778574,2018-06-26 13:15:05 UTC,"My renders were are 300 dpi, so this seems to be related to the DPI of the output. I did a series of tests to find out where the cut-off point is, and 289 dpi is where the problems start for me, and the problems get worse as the DPI increases."
1778574,2018-06-26 13:16:16 UTC,Multi DPI comparison
1778574,2018-06-26 14:25:20 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11) at 300 dpi."
1778574,2020-02-09 21:55:02 UTC,"Hi, this has been reported to Gitlab (https://gitlab.com/inkscape/inkscape/issues/927), so closing here."
1778574,2018-06-25 17:45:40 UTC,Original SVG file
1778586,2018-06-26 16:21:34 UTC,"# zypper repos --uri
Repository priorities are without effect. All enabled repositories share the same priority."
1778586,2018-06-26 16:25:00 UTC,Any reason why you are using
1778589,2019-08-06 15:51:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778589,2019-08-06 16:03:11 UTC,"Before boot, after selecting F2 hungarian language I entered F6 expert mode kernel parameters using CapsLock using qwErty. Only the letter e became large. Same thing happens with the writer of the bugreport. Boot image attached. Thanks, Peter"
1778590,2018-09-13 07:11:38 UTC,"As far as I understand this is a dash-to-dock localization problem, in Shutter those strings are translated to pt_BR. Consider asking about it here: https://github.com/micheleg/dash-to-dock/issues/511"
1778592,2018-09-30 16:29:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778603,2018-06-25 22:34:12 UTC,"Note that comment #1 wasn't suggesting that as the fix, simply trying to figure out which comment is causing the failure, since the error from Sphinx isn't very descriptive."
1778603,2018-06-26 03:45:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/577974"
1778603,2018-06-26 14:54:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/578121"
1778603,2018-06-26 16:46:07 UTC,"Change abandoned by Lance Bragstad (<email address hidden>) on branch: master
Review: https://review.openstack.org/577974"
1778603,2018-06-27 02:55:30 UTC,"Reviewed:  https://review.openstack.org/578121
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=589152d094b248da81dc88db2449fb560985ae8b
Submitter: Zuul
Branch:    master"
1778603,2018-06-25 22:33:12 UTC,"I've attempted to remove every comment from the offending file, but the docs tests still fail."
1778606,2018-06-26 13:14:49 UTC,Are you typing the patron's barcode or scanning it?
1778606,2019-10-21 12:02:55 UTC,tested in Chrome and Firefox
1778606,2019-10-21 11:20:11 UTC,This works great for me; pushed to master.  Thanks Dan!
1778606,2019-10-04 16:27:29 UTC,The barcode lookup runs on the input's onchange and onkeypress (Enter) and disables the submit button until a patron is loaded.
1778606,2018-07-26 17:20:00 UTC,In 2.12 in the xul client the patron notification preferences appeared without the need to click tab or enter (regardless of whether the barcode was typed or scanned).
1778606,2018-06-26 21:45:57 UTC,"It's working as I expect it to on 3.0.2 - if typing or pasting it in, I click tab or enter to load the patron notification preferences, and then click Submit. If scanning it, my barcode scanner is configured with an automatic return, so it loads the patron notification preferences and then I click Submit."
1778606,2018-06-26 21:18:08 UTC,I was just coming here to report this bug.
1778606,2018-06-26 17:34:17 UTC,"We're seeing this when the barcode is typed in, pasted in, or scanned in."
1778607,2018-07-10 14:23:35 UTC,"@tio-trom - the source:local version is not a Snap, so is better tracked in another bug."
1778607,2019-02-19 09:58:56 UTC,"This affects a new snap we uploaded with license metadata to the store around December 2018. We uploaded the snap and used the snap store description editor to choose ""Other Open Source"" software and it shows up as ""Proprietary"" in gnome-software."
1778607,2018-07-10 14:24:57 UTC,Unassigning myself as the cause is the legacy license value coming from the store. The best solution is to update any snaps that have this to a valid SPDX expression. Newly uploaded snaps should not have this issue.
1778607,2018-07-10 14:22:31 UTC,"The store does not currently support the -only forms, which are part of SPDX 3.0 - this caused the error."
1778607,2018-07-09 16:55:17 UTC,"On a related note, the store supposedly allows specifying a custom SPDX expression, so I tried the following for chromium, but it failed with a ""Error: Invalid syntax"" message:"
1778607,2018-07-06 11:52:33 UTC,"I confirm that now Chromium snap is listed as ""free"" in the Software Center. However Chroimum ""source: local"" is still proprietary - https://i.imgur.com/zM5xDSr.png"
1778607,2018-06-27 17:43:21 UTC,"I doesn't work because those are not officially supported ubuntu debs. I am going to send you a message on launchpad so that we don't crowd this comment section with unrelated comments, and maybe you can help a bit :) - thanks!"
1778607,2018-06-27 04:42:09 UTC,@tio-trom  Just pick any of those Debs mentioned and run `ubuntu-bug <application>` in a terminal window.  It will then launch the browser and create the bug for you. Add the important information and it will add the rest.
1778607,2018-06-27 02:12:26 UTC,@Robert I will although I am not familiar with bug reporting
1778607,2018-06-27 01:57:29 UTC,@tio - can you file a new bug about Debs that show with the wrong license? That sounds like an issue with the AppStream data that is generated for these packages.
1778607,2018-07-06 08:41:20 UTC,"I updated the chromium license to BSD-3-Clause (see https://cs.chromium.org/chromium/src/LICENSE).
The snapcraft dashboard allows selecting multiple licenses, but it says ""Multiple licenses can be selected to indicate alternative choices"", so I don't think that's what we want (chromium code is governed by multiple licenses, but it's not an either/or choice)."
1778607,2018-06-27 01:26:02 UTC,"I'll ask the store people to do a search for snaps with this license, but also comment here if you know of other snaps that have the same issue."
1778607,2018-06-27 01:25:36 UTC,snapd is returning the following information:
1778607,2018-06-25 23:55:45 UTC,Affects me as well.
1778607,2018-06-25 23:55:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778607,2018-06-27 01:40:24 UTC,"Non-snaps are often labeled incorrectly in the Software Store. MIT or GPL3 licenses are labeled as ""proprietary"" in the Software Center. To test install Ulauncher (GPL3) or Stacer (MIT), to name 2 random ones. They will be labeled as ""proprietary"". Also, why we cannot filter proprietary snaps out of the Software Store?"
1778610,2018-06-27 20:27:29 UTC,"Also, linux-image-ex is not a valid package name.  You can see the kernels you have install with:"
1778610,2018-06-27 20:26:24 UTC,You may need to run the following from a terminal:
1778610,2018-06-26 00:00:04 UTC,This change was made by a bot.
1778612,2018-06-27 04:24:49 UTC,"Hi Tae-Young Kwon,"
1778612,2018-06-26 05:49:17 UTC,"I have debugged comparing 3.17.10 and 3.17.11.
hplip-3.17.11 added createPPD.sh."
1778628,2019-03-19 10:43:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778632,2018-07-07 01:03:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778632,2019-06-17 23:09:06 UTC,"Fixed, with an exclude option:"
1778632,2018-07-07 01:04:58 UTC,Same Problem.
1778638,2018-06-26 20:54:57 UTC,There appears to be some sort of IO error when it tries to ask for GPG password. But then it keeps working for some time and then it gets stuck.
1778638,2018-06-29 14:38:41 UTC,"You'll need to supply a PASSPHRASE environment variable since --gpg-options=--no-use-agent is specified, something like:"
1778638,2018-06-26 21:07:20 UTC,This is the error:
1778638,2018-06-26 21:04:37 UTC,The command lines are visible also in the logs:
1778638,2018-08-30 06:37:02 UTC,Further debugging with `strace` shows it literally creates the pipe right before it tries to write into it:
1778638,2018-06-29 21:29:36 UTC,Is that true? Haven't I set up the pass phrase during initial backup in Deja Dup? It does not make sense for automatic backup to as for passhrase each time it runs. Is this Deja Dup issue then?
1778638,2018-07-09 12:05:38 UTC,Have you tried https://bugs.launchpad.net/duplicity/+bug/1778638/comments/6 yet??
1778638,2018-08-30 06:20:53 UTC,I have even tried without encryption. The `--no-use-agent` option is there even:
1778638,2018-10-08 05:53:19 UTC,It looks like this is not just me who is having this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1582654
1778638,2018-10-23 15:23:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778638,2018-06-26 19:06:55 UTC,Strange!
1778640,2018-06-27 08:45:01 UTC,"If we chose OPNCLOUD as sample BYOL userid, will make z/VM 6.4 user a little bit confused, since it is already exists."
1778640,2018-06-26 12:31:43 UTC,"I'd suggest we say something like following at beginning of the doc: bring your own linux and assume the name is OPNCLOUD
then we don't need doc change for other sections"
1778640,2018-06-26 12:13:58 UTC,"Confirmed with Chuck on slack, OPNCLOUD is gone in z/VM 7.1"
1778644,2020-11-03 18:03:04 UTC,"Reviewed:  https://review.opendev.org/758772
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=4222140d1eacd8da90216fa3591d33cc830a1fcf
Submitter: Zuul
Branch:    master"
1778644,2020-10-19 09:40:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/758772"
1778644,2020-11-02 00:49:51 UTC,"Reviewed:  https://review.opendev.org/758717
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=a3377de8719889401f6ea97fb0c74eae4aa5c2f0
Submitter: Zuul
Branch:    master"
1778644,2020-10-19 08:32:53 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/758717"
1778645,2018-06-26 06:51:19 UTC,One of the possible solution is while defining node_staging_uri config option we can use oslo_config.types.URI where we can provide a valid schemes for the same.
1778649,2018-10-26 07:42:47 UTC,You should report this bug on the Debian side as the work is happening there.
1778654,2018-07-28 10:34:39 UTC,From https://bugs.launchpad.net/xfpanel-switch/+bug/1778654
1778654,2019-09-22 09:32:06 UTC,"Created attachment 9047
Add a confirmation dialog before applying a configuration"
1778654,2019-12-19 02:34:26 UTC,Emanuele Petriglia referenced this bugreport in commit a440127d0cd90e18bdd193af37d31b61c5eebd19
1778654,2019-12-19 02:34:49 UTC,This patch is great! Applied above.
1778657,2018-06-26 12:36:03 UTC,"thanks for the file bug, agree it's a duplicate effort now"
1778663,2018-08-03 18:05:33 UTC,"Reviewed:  https://review.openstack.org/588531
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=12e74584c325d364dc366817e4e025f4fda5b3b6
Submitter: Zuul
Branch:    stable/queens"
1778663,2018-08-03 12:45:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/588531"
1778663,2018-08-03 12:37:45 UTC,Sorry for the vacation-induced long wait. I'm sorry to report that this is still broken.
1778663,2018-08-08 21:38:34 UTC,This issue was fixed in the openstack/openstack-ansible 17.0.8 release.
1778663,2018-06-26 20:17:28 UTC,"Reviewed:  https://review.openstack.org/569857
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=448537c6591064faad653cbe438f6cafc7d7b296
Submitter: Zuul
Branch:    stable/queens"
1778663,2018-06-26 16:16:05 UTC,https://review.openstack.org/#/c/569857/2
1778663,2018-07-09 14:01:47 UTC,This issue was fixed in the openstack/openstack-ansible 17.0.6 release.
1778663,2018-06-26 16:15:58 UTC,We've pushed up a fix for that :-)
1778665,2020-06-15 04:17:40 UTC,[Expired for fonts-guru-extra (Ubuntu) because there has been no activity for 60 days.]
1778665,2020-04-15 23:47:27 UTC,Hmm.. The new version was there to prevent odd messages from the package system. I suppose this is history now?
1778666,2018-07-26 15:28:37 UTC,"I tried to reproduce on fresh master, without success, see my commands please:
openstack network qos policy create p1
openstack network qos rule create p1 --type bandwidth-limit --max-kbps 1000
openstack floating ip create public
openstack floating ip set --qos-policy p1 bd8de6f8-07b0-48e6-9d8e-5e3a0f88a4e4
openstack floating ip show bd8de6f8-07b0-48e6-9d8e-5e3a0f88a4e4
+---------------------+--------------------------------------+

| Field               | Value                                |


+---------------------+--------------------------------------+

| created_at          | 2018-07-26T15:11:44Z                 |
| description         |                                      |
| dns_domain          | None                                 |
| dns_name            | None                                 |
| fixed_ip_address    | None                                 |
| floating_ip_address | 172.24.4.6                           |
| floating_network_id | e0652260-3d99-446c-af4a-4cb7daaba36d |
| id                  | bd8de6f8-07b0-48e6-9d8e-5e3a0f88a4e4 |
| name                | 172.24.4.6                           |
| port_details        | None                                 |
| port_id             | None                                 |
| project_id          | 91c8b75eac0d45d29106e6726981f18b     |
| qos_policy_id       | 82d52bf7-81ac-45d9-9666-c5dd43cac942 |
| revision_number     | 10                                   |
| router_id           | None                                 |
| status              | DOWN                                 |
| subnet_id           | None                                 |
| tags                | []                                   |
| updated_at          | 2018-07-26T15:22:03Z                 |


+---------------------+--------------------------------------+"
1778666,2018-07-30 10:37:26 UTC,"Could you please confirm that you used the latest version of neutron, neutron-lib and osc?"
1778666,2018-08-16 14:03:52 UTC,"As you can see in bug description provided documentation link there is for ""queens"", so I was using OSP13 setup for testing and not ""fresh master"".
*** Next time I'll include OSP version in bug description ***"
1778666,2018-08-21 10:57:44 UTC,"Arkady: thanks, on stable/queens I reproduced the issue"
1778666,2018-08-21 11:07:19 UTC,"the patch for this was merged in June:
https://review.openstack.org/575057"
1778666,2018-08-21 13:08:15 UTC,"Lajos: good news if so, we do have a bug :)
Thanks for update!"
1778666,2018-08-21 14:27:03 UTC,"I pushed the cherry-picked patch:
https://review.openstack.org/594244"
1778666,2018-10-09 12:15:08 UTC,Fix merged to OSC stable/queens. We can close this issue now
1778666,2018-11-19 20:51:40 UTC,This issue was fixed in the openstack/python-openstackclient 3.14.3 release.
1778670,2018-06-26 09:26:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/578048"
1778670,2019-03-04 13:52:04 UTC,"Looking at the docs, this appears fixed on both accounts, so marking fix committed."
1778670,2018-07-31 15:13:31 UTC,"Reviewed:  https://review.openstack.org/578048
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cc7d5f836f47442393739804cbfb7a4043593487
Submitter: Zuul
Branch:    master"
1778671,2018-06-26 10:33:29 UTC,"Review in progress for https://review.opencontrail.org/44123
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-04 14:27:37 UTC,"Review in progress for https://review.opencontrail.org/44189
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-26 11:29:56 UTC,"Review in progress for https://review.opencontrail.org/44126
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-26 09:51:58 UTC,"Review in progress for https://review.opencontrail.org/44121
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-28 08:16:14 UTC,"Review in progress for https://review.opencontrail.org/44121
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-28 09:17:38 UTC,"Review in progress for https://review.opencontrail.org/44126
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-04 14:17:28 UTC,"Reviewed:  https://review.opencontrail.org/44188
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/a6e2495477efd29815db4e4e65ea6d295edbeeb9
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1778671,2018-06-28 08:57:27 UTC,"Review in progress for https://review.opencontrail.org/44123
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-03 16:30:45 UTC,"Review in progress for https://review.opencontrail.org/44188
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-09 09:33:18 UTC,"Review in progress for https://review.opencontrail.org/44314
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-05 08:33:10 UTC,"Reviewed:  https://review.opencontrail.org/44198
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/f73c0f84f874c1700ecab3c1a0e4ae0701a39cf5
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1778671,2018-07-05 08:33:08 UTC,"Reviewed:  https://review.opencontrail.org/44192
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/9cc0b694e86adffdb8ad433e212f7604fbd051f6
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1778671,2018-07-05 08:33:00 UTC,"Reviewed:  https://review.opencontrail.org/44189
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/1cf5a7d92573fd867ea4a946ea700ed1a5d60ce4
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1778671,2018-07-04 15:38:17 UTC,"Review in progress for https://review.opencontrail.org/44198
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-04 15:28:12 UTC,"Review in progress for https://review.opencontrail.org/44314
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-04 15:18:06 UTC,"Review in progress for https://review.opencontrail.org/44192
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-04 15:08:00 UTC,"Review in progress for https://review.opencontrail.org/44189
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-04 14:57:53 UTC,"Review in progress for https://review.opencontrail.org/44198
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-17 08:56:21 UTC,"Reviewed:  https://review.opencontrail.org/44314
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/ad77e134aea7761bc005f8f622d239ea71014f6f
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1778671,2018-07-03 12:43:33 UTC,"Review in progress for https://review.opencontrail.org/44198
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-04 14:47:48 UTC,"Review in progress for https://review.opencontrail.org/44192
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-28 09:52:35 UTC,"Review in progress for https://review.opencontrail.org/44188
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-28 10:16:24 UTC,"Reviewed:  https://review.opencontrail.org/44123
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/ecbfc5bbd5a6138969b61c2c839c4e8db6080b2d
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1778671,2018-06-28 10:58:29 UTC,"Review in progress for https://review.opencontrail.org/44192
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-28 10:01:33 UTC,"Reviewed:  https://review.opencontrail.org/44121
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/be77379f66a6af513c379202918fa6c98580bb34
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1778671,2018-06-28 14:31:55 UTC,"Reviewed:  https://review.opencontrail.org/44126
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/a61735f55c69f1548977d19ed0daa9c0da5d75a4
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1778671,2018-07-03 11:53:03 UTC,"Review in progress for https://review.opencontrail.org/44314
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-03 12:03:20 UTC,"Review in progress for https://review.opencontrail.org/44188
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-07-03 12:13:26 UTC,"Review in progress for https://review.opencontrail.org/44189
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-28 14:23:04 UTC,"Review in progress for https://review.opencontrail.org/44198
Submitter: Michal Kostrzewa (<email address hidden>)"
1778671,2018-06-28 09:52:40 UTC,"Review in progress for https://review.opencontrail.org/44189
Submitter: Michal Kostrzewa (<email address hidden>)"
1778672,2018-06-26 20:18:28 UTC,"Hmmm, probably not language related as tested various versions on VM with no change (i.e. bug is still present with right Ctrl only)."
1778672,2018-08-01 22:48:44 UTC,This was fixed upstream: https://github.com/mate-desktop/caja/pull/1036
1778672,2018-06-28 16:57:45 UTC,"Update: I was able to reproduce the problem on an UM live VM. The thing is the problem doesn't happen after repeatedly following the steps, even though it has focus. I have to click again on the Caja window or desktop and then press Ctrl+.(or ,) to get the selection box."
1778672,2018-06-27 01:45:47 UTC,Reported upstream: https://github.com/mate-desktop/caja/issues/1024
1778672,2018-06-27 01:31:48 UTC,And I just tried Compiz instead of my usual Marco. Same thing.
1778672,2018-06-27 01:28:40 UTC,It happens for me with both left and right control keys. I'm using English (US) layout.
1778672,2018-06-26 19:24:08 UTC,Just a thought - can people add their keyboard layout and language selection to the report?  It may have something to do with locale settings?
1778672,2018-06-26 19:35:52 UTC,English(US) with Generic 105-Key PC(intl.) here!
1778672,2018-06-26 19:14:24 UTC,"If that's the case, I can't seem to reproduce it! I tried on my desktop PC where I have the latest UM 18.04 installed and a live VM..."
1778672,2018-06-26 18:50:53 UTC,"No, just clicking on a window or on its menu bar will give the window focus, by default Caja (or any other program) will have focus when it is first opened - so technically in this case step 2 is redundant if you have not selected anything else before step 3."
1778672,2018-06-26 16:12:47 UTC,"How do I ""ensure Caja has Focus""? Do you mean enabling the ""focus follows mouse"" thing?"
1778672,2018-06-26 13:15:18 UTC,"I can reproduce in my installed and up-to-date 18.04, in a new user account, with Ctrl + . and Ctrl + ;"
1778672,2018-06-26 10:55:31 UTC,This bug also can be reproduced directly from the desktop without Caja being explicitly open.  Same steps as above can be used on the Desktop.
1778672,2018-06-26 19:50:58 UTC,"OK, above step may help with regards to keyboard layout, but further testing is showing that it ONLY occurs when using the left ctrl key, the right hand control key does not cause the same effect."
1778684,2018-07-03 21:19:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778684,2018-08-01 19:30:51 UTC,I think it happens since upgraded from 16.04 to 18.04.
1778684,2018-07-09 14:16:29 UTC,I have the same issue. How can I solve it?
1778684,2018-07-27 11:15:15 UTC,Please run:
1778684,2018-07-27 11:43:32 UTC,"Hi Colin,
Yes, running strace command has reproduced the bug.
Attaching the man.trace herewith."
1778684,2018-08-03 06:12:07 UTC,For me happens on Ubuntu 18.04 and Kernel 4.12. Switching to 4.15 it works as expected.
1778684,2019-05-19 09:06:23 UTC,Is groff installed?
1778684,2018-08-03 13:31:00 UTC,"I am happy to here this Deepack, but unfortunately, for many reasons, I have to rely on 4.12! :("
1778684,2018-08-04 09:02:13 UTC,"Switching to kernel 4.15 resolves also the problem for me.
But unfortunately i have some applications that need kernel version 4.9"
1778684,2018-08-15 13:07:26 UTC,"Seems that problem in apparmor profile loading on older kernels.
I have the same issue on custom kernel 4.4, but with ubuntu kernel 4.15 everything ok."
1778684,2018-08-15 18:10:02 UTC,"Great, it works for 4.12, thank you!"
1778684,2018-12-03 16:25:42 UTC,"Worked on my pine64 but on the Rpi 3, OS at same level, it gives the following :'"
1778684,2019-08-21 07:37:50 UTC,"Same problem here on a raspberry running volumio2.
We've run out of ideas here. Everything seems ok, yet still the result is:
 Manual page man(1) line ?/? (END) (press h for help or q to quit)
...."
1778684,2019-08-22 15:22:28 UTC,I think we want to backport changes from the below upload to fix this
1778684,2019-08-22 16:50:59 UTC,"@xnox, that seems unlikely to be helpful since the version you quote is older than the one in bionic!  The reference to Debian bug #889617 is probably not correct even though they have similar symptoms."
1778684,2019-08-22 16:54:21 UTC,"The duplicate bug has a ""profile not found"" syslog message which seems likely to be relevant; I suspect there's something going on in relation to man-db's use of stacked profiles."
1778684,2019-11-05 00:17:07 UTC,"Hello, I believe this issue can be addressed by backporting kernel commit 9fcf78cca198600b27c44b4e50f00f8af3927f17 to your kernel. (Possibly other changes are also necessary; this change may build upon earlier changes, and may be further modified by future changes."
1778684,2019-11-05 01:13:02 UTC,Can anybody recreate this issue with a 4.15 kernel from the official Ubuntu archive?
1778684,2018-08-03 12:55:47 UTC,"Thanks Lancillotto.  It worked for me too :-)
I had had Kernel 4.10.2-041002. upgrading to 4.15.0-29 solved this issue."
1778695,2019-04-16 14:43:00 UTC,"Due to a now fixed bug in libmagic [1] the file is identified as TIFF image data in 18.10, and therefore Ristretto is allowed to load it. An exception [2] was added to the Ristretto code."
1778695,2019-04-09 17:57:37 UTC,Broken in 19.04 again.
1778695,2018-09-25 11:54:32 UTC,"It works in 18.10 (dev release), so it was either fixed in version 0.8.3 or in some library which is used by Ristretto."
1778695,2018-06-26 11:07:48 UTC,I consider that this is a bug since it should be working since a 2012 commit (reference : https://blog.xfce.org/2012/03/raw-files-with-ristretto/)
1778695,2019-04-14 14:33:53 UTC,Went back to 18.10 and installed libmagic1 from bionic and disco. Both these versions break the loading of the example CR2 file.
1778699,2018-12-13 16:15:15 UTC,"sergiusens: git clone --branch Neon/unstable https://anongit.neon.kde.org/kde/kblocks.git
12:21 sergiusens: depending on what you want to do kbruch.git might be better though as it has no additional deps besides the build-snap. in either case you'll need `export SNAPCRAFT_PARTS_URI=https://metadata.neon.kde.org/snap/parts.yaml` for the remaining remote part"
1778701,2018-12-12 17:31:24 UTC,"How would we select which description and summary, at the least, to use from those discovered appstream files?"
1778701,2018-12-13 09:35:14 UTC,"> How would we select which description and summary, at the least, to use from those discovered appstream files?
"
1778701,2019-02-12 04:17:53 UTC,[Expired for Snapcraft because there has been no activity for 60 days.]
1778705,2018-06-26 11:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778705,2018-06-26 11:33:06 UTC,kvm on z/vm is out of scope for Ubuntu on s390x.
1778705,2019-03-28 04:00:53 UTC,"Out-of-scope, set priority to low."
1778705,2019-11-13 00:30:14 UTC,We are still affected by this: http://10.246.72.4/test-results/4.4.0-167.196-generic/s2lp6g001__4.4.0-167.196__2019-10-23_08-15-00/ubuntu_kvm_unit_tests/results/ubuntu_kvm_unit_tests.skey/debug/ubuntu_kvm_unit_tests.skey.DEBUG.html
1778709,2018-06-26 13:50:16 UTC,"Hi Anand, can you attach any logs from the cinder-volume and nova-compute side so we can take a look at what is going on?"
1778712,2018-09-12 19:30:10 UTC,Updated six screenshot png images as noted above and pushed signed off branch to working: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=60617734450f9891462a850534ab08ae31444c34
1778712,2019-05-23 21:15:10 UTC,"It looks like item_status_altview_web_client.png at least should be updated again for 3.2+, given the ""Copy"" => ""Item"" relabeling."
1778712,2019-08-02 15:47:07 UTC,"I added two new screenshots to reflect the copy => item name change, and pushed to master, rel_3_3, and rel_3_2.  Thanks, Jeanette, Remington, and Galen."
1778714,2018-06-27 06:18:42 UTC,"Reviewed:  https://review.openstack.org/578104
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=26894447b33adbbfb475a8a4b6f51f24e951af5d
Submitter: Zuul
Branch:    stable/queens"
1778714,2018-06-26 13:12:11 UTC,Potential related bug: https://bugs.launchpad.net/neutron/+bug/1777506
1778714,2018-06-26 13:25:18 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/578104"
1778714,2018-06-26 14:49:29 UTC,It is definitely different issue then reported in https://bugs.launchpad.net/neutron/+bug/1777506 but it is possible that https://review.openstack.org/578104 will fix this issue - let's check :)
1778714,2018-06-26 14:56:49 UTC,"Looks like it impacts again all stable/queens patches. Other examples:
http://logs.openstack.org/50/577650/1/check/neutron-rally-neutron/eb9ec2f/job-output.txt.gz
http://logs.openstack.org/49/577649/1/check/neutron-rally-neutron/fec71cc/job-output.txt.gz"
1778714,2018-09-18 14:08:43 UTC,This issue was fixed in the openstack/neutron 12.0.4 release.
1778717,2020-01-09 03:45:32 UTC,Bump. This is extremely frustrating.
1778717,2018-06-26 13:03:18 UTC,Moving back to Confirmed state - since all the available logs are already uploaded.
1778717,2018-06-27 20:16:08 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the last kernel that did not have this issue.
1778717,2018-06-26 13:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778717,2018-06-26 13:00:53 UTC,* Also hit with 16.04.4 HWE kernel 4.13.0-45-generic.
1778719,2019-12-02 19:52:16 UTC,snapd would need to support an array for common-id and so would the store in order to support this
1778719,2019-12-03 14:15:11 UTC,"> snapd would need to support an array for common-id and so would the store in order to support this
"
1778722,2018-06-26 14:18:09 UTC,"- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- not reproduced on Windows 10, Inkscape 0.92+devel (e33f40d, 2018-06-25)"
1778722,2019-03-11 10:05:02 UTC,Do you still have this problem with the latest Inkscape version?
1778722,2019-03-11 10:30:30 UTC,"Hello,"
1778722,2019-03-11 10:32:29 UTC,And my environnement :
1778722,2019-05-21 10:57:59 UTC,"Hi, when running it with GDB, could you please attach a log with the results of commands ""bt"" and ""bt full"" after the crash?"
1778722,2019-05-21 10:59:10 UTC,Also please try using the following AppImage version of Inkscape: https://dl.bintray.com/probono/AppImages/:Inkscape-0.92.3+68.glibc2.15-x86_64.AppImage
1778722,2019-11-06 02:32:53 UTC,Closing due to lack of response. Please check for bugs on our new tracker: https://inkscape.org/report. Thank you!
1778724,2018-07-31 10:37:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587378"
1778724,2018-08-03 22:41:15 UTC,"Reviewed:  https://review.openstack.org/587378
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=12cea89b91c2548ea544f4e1adf0d346528b6b2e
Submitter: Zuul
Branch:    master"
1778724,2018-08-07 21:50:28 UTC,"https://review.openstack.org/#/c/587378 did not handel the vhost-user code paths.
i will adress them seperately tomorow."
1778724,2018-10-31 16:23:55 UTC,This issue was fixed in the openstack/os-vif 1.12.0 release.
1778726,2018-06-26 13:39:55 UTC,Software Updater - How It Should Look
1778726,2019-10-01 22:29:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778728,2018-08-02 19:44:15 UTC,"Robert, I think this is related to this bug in OpenSRF's documentation:  https://bugs.launchpad.net/opensrf/+bug/1684970"
1778728,2018-08-02 20:14:36 UTC,"Hi Robert,"
1778731,2018-09-22 06:42:22 UTC,"This looks to be identical to what Ross Kramer described here: https://ubuntuforums.org/showthread.php?t=2395010 -- if so, can this be closed because the underlying cause was a wrong UUID?"
1778731,2020-11-18 04:17:25 UTC,[Expired for clevis (Ubuntu) because there has been no activity for 60 days.]
1778745,2018-06-26 16:21:45 UTC,"The attachment ""Fix quoting"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1778750,2019-11-08 00:29:28 UTC,"Trying to reproduce this, it doesn't look to be an issue anymore:"
1778750,2018-06-28 06:49:35 UTC,This is the stack trace btw :
1778750,2018-09-04 01:35:09 UTC,Was this due to not being in the 'controller' model? Or was it due to backup filename which already exists? Or something else?
1778750,2018-09-04 05:11:49 UTC,Something else. Disk space I think.
1778750,2019-11-08 04:10:35 UTC,"Oh, it seems fixed in commit 48af454ef75fc78f11174308ad903ff6b9481980"
1778752,2018-08-29 21:47:31 UTC,"I'm marking this wishlist because it sounds more like an optimization request than an actual bug, and there may be nothing pbr can do about it if the time is being spent in git or something else."
1778752,2018-06-26 16:22:56 UTC,"FWIW, here's a recording of the issue manifesting itself in practice: https://asciinema.org/a/xKkrkrGoGiHVZqEZW6nTVnCXC"
1778755,2019-02-15 15:35:30 UTC,Also in the saving status forever...
1778755,2019-03-13 07:24:53 UTC,"AFAIK, kolla didn't limit the size of images. If the network speed is slow, it will stay ""queued"" status for quite a long time."
1778759,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1778765,2018-06-26 22:02:45 UTC,"precisely, its size is 0 and hence lsblk ignores it without option -a."
1778765,2018-06-28 17:14:48 UTC,"Tried that rc2 kernel, still the same problem."
1778765,2018-06-26 17:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778765,2018-06-26 18:12:11 UTC,Unable to run this command
1778765,2018-06-27 20:21:19 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1778767,2018-12-06 17:19:38 UTC,This bug was fixed in the package usbmuxd - 1.1.0-2ubuntu0.1
1778767,2018-11-28 15:39:19 UTC,"Hello clayg, or anyone else affected,"
1778767,2018-06-26 20:20:54 UTC,"The attachment ""add +RUN directive to rule"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1778767,2018-11-21 15:08:29 UTC,"using the ""39-usbmuxd.rules"" file from cosmic (usbmux-1.1.1~git20180428.b95a0a0-1) solves the problem."
1778767,2018-11-21 15:09:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778767,2018-11-22 10:49:07 UTC,This patch solves the issue by backporting the udev rule from usbmuxd-1.1.1~git20180428.b95a0a0-1 (cosmic)
1778767,2018-11-22 15:53:27 UTC,"Thanks Leo for the patch, looking at the upstream git log there were some other follow up fixes to the udev rules, I included those as well and uploaded as a SRU to bionic now"
1778767,2018-11-22 15:53:55 UTC,The issue was fixed in cosmic
1778767,2018-11-26 15:59:11 UTC,where can I track the progress of the fix until it gets released in bionic? i cant seem to find it in sru
1778767,2018-12-06 17:19:43 UTC,"The verification of the Stable Release Update for usbmuxd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1778767,2018-11-28 17:08:00 UTC,new package works great
1778767,2018-11-28 17:31:48 UTC,Installed the version from proposed:
1778768,2018-07-11 14:42:24 UTC,"We're not seeing this in 3.0.2 - when I remove the barcode it doesn't show a patron name, and when I put in a new barcode, it populates the new patron name as expected."
1778770,2018-06-26 18:06:35 UTC,note that Dependencies.txt says that libgcrypt20 is 1.6.5-2ubuntu0.5.
1778770,2018-07-23 19:29:38 UTC,"I can confirm that backporting libgcrypt20 version 1.7.8-2ubuntu1.1 from artful-security fixes this problem. It requires backporting libgpg-error 1.27-3 from artful as a build-dep, to provide libgpg-error-mingw-w64-dev."
1778770,2018-08-27 23:40:15 UTC,Affects multiple users (as per the comments).
1778770,2018-08-27 23:42:53 UTC,"Related: #1677903, #1772457"
1778780,2019-11-08 21:32:58 UTC,https://opendev.org/openstack/charm-deployment-guide/commit/75ef37f2127a96d0cc658909a884e35ec4bb4fef
1778780,2019-11-08 21:32:41 UTC,"This has been fixed through the addition of a note explaining that option 'osd-reformat' has been removed since ""the 18.05 charm release""."
1778783,2019-02-28 15:55:47 UTC,"Working branch at user/stompro/lp1778783_circulate_log_me_barcode
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1778783_circulate_log_me_barcode"
1778784,2018-12-13 19:45:07 UTC,"Oops, glance patch: https://review.openstack.org/625092"
1778784,2019-03-22 03:45:38 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1778784,2019-02-04 17:01:42 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/625092"
1778784,2018-12-19 10:01:18 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1778784,2019-06-27 14:51:38 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/579482"
1778784,2018-12-13 19:44:56 UTC,Glance patch: https://bugs.launchpad.net/nova/+bug/1778784
1778784,2018-12-06 20:38:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623309"
1778784,2018-12-08 20:25:43 UTC,"Reviewed:  https://review.openstack.org/623309
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2f693360b4cf7616c6e1ff5573aedeab801e88b8
Submitter: Zuul
Branch:    master"
1778784,2018-12-07 16:32:37 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623545"
1778784,2018-07-02 08:08:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/579482"
1778784,2018-12-10 10:30:55 UTC,"Reviewed:  https://review.openstack.org/623545
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bbc431f32bcf206beec899109853e58fbe23564a
Submitter: Zuul
Branch:    stable/rocky"
1778786,2020-01-27 21:50:03 UTC,Evergreen 3.3
1778786,2020-01-28 14:16:30 UTC,"At least part of the problem is that the ""Items Checked Out"" tab and the ""Other/Special Circulations"" tab use the same egGrid code (see templates/staff/circ/patron/t_items_out.tt2). Thus they end up with the same persist-key."
1778810,2019-01-30 20:02:12 UTC,Also worked in production with 3.1.5.
1778810,2019-01-30 18:10:18 UTC,I can confirm that the above fix has worked on my test server running 3.1.8
1778810,2018-09-15 00:02:04 UTC,I tested this on a 3.1.5 sandbox and I'm still not seeing any holds placed.
1778810,2019-07-16 20:29:10 UTC,This appears to be a duplicate of: https://bugs.launchpad.net/evergreen/+bug/1806394
1778810,2018-06-27 18:27:32 UTC,"When trying to place a Copy Hold I am receiving an error of ""ERROR: null value in column ""target"" violates not-null constraint"" in the opensrf log.  For the other two types of holds I am receiving messages of 'retrieve asset.copy called with no ID...' and 'rolling back db session.'"
1778810,2018-06-27 20:24:33 UTC,i think this was just missing a return statement in the function given to map.
1778813,2018-07-18 08:20:25 UTC,"That is clearly a double buffer issue.
That is the first time this issue is reported.
Would you mind to try on a different window manager? kde xfce mate.. ?"
1778813,2018-09-06 08:15:05 UTC,"apart from the flickering issue, the ""bad back illumination"" is probably because you have the ""floor"" option enabled on Raytracing properties. So you are looking on ""the shadow side of the board"""
1778813,2018-09-06 11:04:21 UTC,"Yes, removing the ""add floor"" fix the light."
1778813,2019-04-25 00:17:22 UTC,Still on version 5.1.0-unknown-8e812c0~82~ubuntu16.04.1 being necessary always export twice the PNG/JPEG file to get a Raytraced image without flicker into (even if the Raytraced image is correct at the KiCad 3D viewer).
1778813,2019-04-25 00:18:24 UTC,"Also, would be interesting add the axis (green, blue, red - XYZ arrows) when in raytracing mode."
1778813,2018-07-18 02:21:40 UTC,"Depending of the angle make better or worst, but always happens in this machine (intel video card)."
1778813,2018-07-28 03:58:22 UTC,"Still on 201807270649+0cca1c6~65~ubuntu16.04.1
I have to schedule me self to change my OS and do this kind of test, I will keep this issue opened and on track."
1778813,2018-09-06 01:14:09 UTC,"Just to keep tracking, the issue still on
201809051403+f85b147~66~ubuntu16.04.1
after some update on the 3D view code."
1778813,2018-06-27 08:23:51 UTC,"Is it always reproducible ?
What happen if you do a 3rd export attempt?"
1778813,2018-06-27 11:24:20 UTC,"In this computer configuration (intel card - core2duo) yes, always happens. Check that there is also a strange border in some exported images.
During the render calculation, in this computer, the 3D image keep flicking until the calculation finished (this appear be related with the strange border, because appear to be a residue of this flicker)."
1778813,2018-06-27 11:27:43 UTC,The 3rd attempt is also normal (as long I keep the camera position).
1778813,2018-06-27 11:47:57 UTC,"All that cases are related with the double buffering. The final pass will render the correct light intensity so its the same issue, you are exporting the previous frame and it should be the latest."
1778813,2018-06-27 12:15:21 UTC,"This hypothesis make sense, because this missing calculated part in the file is updated in the screen very quick, like just one algorithm iteration."
1778817,2018-07-04 07:47:15 UTC,"> Ok, but we still need to know how to inhibit the screen locking in compiz,
> since the previous standard method is ineffective.
"
1778817,2018-06-26 23:30:22 UTC,And then the upgrade gets stuck because of a conffile prompt.
1778817,2018-06-26 23:39:28 UTC,"The failure is because pam_unix depends on libcrypt, and libcrypt is part of glibc, and compiz doesn't otherwise have libcrypt loaded into memory, and libcrypt has a tight versioned dependency on the corresponding version of libc itself (requires symbol GLIBC_2.25).  So when dlopen() tries to load libcrypt from disk, because compiz is doing it wrong, it can't find the symbols."
1778817,2018-06-28 15:32:01 UTC,"So, u-r-u runs /usr/bin/gnome-session-inhibit --inhibit idle --inhibit-only - running that manually works fine to block stuff on cosmic, but not sure about xenial."
1778817,2018-07-03 13:54:31 UTC,"That's the first report of the issue and screen locking inhibition has been working fine on xenial so far, is there anything useful (warning, errors, info about screen locking, inhibiting, screensaver, session) in the system logs/journal? Can you reproduce the bug or was it a one time thing?"
1778817,2018-07-03 14:20:04 UTC,"Doing ""/usr/bin/gnome-session-inhibit --inhibit idle --inhibit-only"" on Xenial seems to work fine so the issue seems to be on the ubuntu-release-upgrader side. Is the process using the correct user environment (uid, dbus session bus, etc) to talk to the active session?"
1778817,2018-07-03 14:26:14 UTC,"@Steve, you are probably right about the compiz use of pam but that doesn't seem likely to get changed at this point, at least not before the LTS upgrades to bionic are turned on"
1778817,2018-07-03 15:27:25 UTC,"On Tue, Jul 03, 2018 at 02:26:14PM -0000, Sebastien Bacher wrote:

> @Steve, you are probably right about the compiz use of pam but that
> doesn't seem likely to get changed at this point, at least not before
> the LTS upgrades to bionic are turned on
"
1778817,2018-07-04 00:00:45 UTC,I believe the issue is that the gnome-session-inhibit call is terminated after the upgrade unless you are running a GNOME session.
1778817,2018-07-04 07:32:09 UTC,"I reproduced the second part of the problem (screen locks and fails to unlock) after upgrading from 16.04 to 18.04 and before restarting the machine (finish the upgrade, close the upgrader and wait until the screen saver goes off)"
1778817,2018-07-04 01:03:23 UTC,No. This upgrade had the screen locked over a conffile prompt. The upgrade was definitely still in progress.
1778817,2018-07-04 14:00:01 UTC,Steve - your /var/log/dist-upgrade/main.log file may be helpful in sorting out where the inhibit went wrong. Could you add it to the bug?
1778817,2018-07-04 14:32:17 UTC,I can reproduce first part of the problem during an upgrade from 17.10 to 18.04 and the screen locks during the upgrade. It locks before u-r-u issues the inhibit command and proceeds with the upgrade with the screen locked.
1778817,2018-07-05 07:41:04 UTC,syslog search for 'inhibit':
1778817,2018-07-05 22:53:33 UTC,I reported bug 1780342 regarding the lock screen after the upgrade has completed and one has not rebooted.
1778817,2018-07-06 20:27:37 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.4
1778817,2018-07-11 09:30:54 UTC,"Hello Steve, or anyone else affected,"
1778817,2018-07-16 15:31:53 UTC,"Hello Steve, or anyone else affected,"
1778817,2018-07-16 22:23:03 UTC,I tested a release upgrade from Ubuntu 16.04 to Ubuntu 18.04 today using the version of release-upgrader in -proposed and the lock screen did not appear.
1778817,2018-07-19 12:50:48 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.21
1778817,2018-07-19 12:51:05 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1778817,2018-12-18 14:41:41 UTC,Marking compiz as invalid because this is a ubuntu-release-upgrader problem.
1778817,2018-12-19 00:24:40 UTC,"It is not invalid; it is a regression vs all previous screen lock implementations that compiz does pam handling in process instead of in a helper process, making it vulnerable to this kind of library skew."
1778817,2018-07-04 13:35:02 UTC,"On Wed, Jul 04, 2018 at 07:47:15AM -0000, Sebastien Bacher wrote:

> > Ok, but we still need to know how to inhibit the screen locking in compiz,
> > since the previous standard method is ineffective.
>
> The command that Julian pointed out as the one used by u-r-u is correct
> and works from our testing
>
>
> > unless you are running a GNOME session.
>
> > https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-
> upgrader/trunk/view/head:/DistUpgrade/DistUpgradeQuirks.py#L444
>
> It looks like Unity sessions are in a similar situation so maybe the
> code should be change to keep the inhibitor for those as well (maybe
> poping up a dialog explaining that screen lock is not going to work
> until reboot if that's less confusing to users?). That's a different
> case than the one reported here though
"
1778818,2018-10-17 16:23:56 UTC,"We, also, are unable use the web client copy buckets for our books lists as we need the bib fields that are available in the staff client, i.e., ISBN, author, pub date."
1778818,2021-02-16 21:27:55 UTC,Having parts is also an important usability consideration for copy/item buckets.  This WOULD be the ideal tool manage a variety of projects with its addition.
1778823,2019-02-26 05:31:59 UTC,"Change abandoned by Ryan Beisner (<email address hidden>) on branch: stable/18.11
Review: https://review.openstack.org/639144"
1778823,2018-07-02 14:38:03 UTC,"Interestingly the ceph-* charms will only attempt to upgrade ceph packages if the ceph version changes - UCA pockets are mapped to ceph releases, and the charm knows that pike and queens are both Luminous.  So the upgrade is basically a no-op and returns fast, rather than updating and source configuration on the units."
1778823,2019-02-25 16:14:03 UTC,"FYI track status @:
https://review.openstack.org/#/q/topic:bug/1778823+(status:open+OR+status:merged)"
1778823,2019-02-25 16:13:12 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/639146"
1778823,2019-02-23 00:48:43 UTC,ignore comment #13.  different bug
1778823,2019-02-23 00:35:19 UTC,"This appears to affect swift as well, as it also uses code-name based updates in charmhelpers.  Adding swift-proxy and swift-storage charms"
1778823,2019-02-06 16:20:16 UTC,"Reviewed:  https://review.openstack.org/634424
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=336581efeb9a1c5d363c5d3ce631d9bad1a8a337
Submitter: Zuul
Branch:    master"
1778823,2019-02-01 14:47:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634424"
1778823,2019-02-01 13:18:12 UTC,"Reviewed:  https://review.openstack.org/624425
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=5ed4956f2bc594d42abf6fd2fa64dcddc1b86da5
Submitter: Zuul
Branch:    master"
1778823,2019-02-25 16:07:51 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/639144"
1778823,2019-01-31 22:57:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/634338"
1778823,2018-12-11 15:34:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624425"
1778823,2018-11-26 18:07:09 UTC,"This is the log message that is printed:
2018-11-26 15:17:55 INFO juju-log Invalid upgrade path from luminous to luminous. Valid paths are: ['firefly -> hammer', 'hammer -> jewel', 'jewel -> luminous', 'luminous -> mimic']"
1778823,2018-11-26 18:03:03 UTC,"Even if the charm won't upgrade the packages, it should still update the /etc/apt/sources.list.d/cloud-archive.list file and inform to the user that ""apt-get update && apt-get ugprade"" is expected to be executed."
1778823,2018-07-09 22:14:47 UTC,"The ceph packages available went from 12.2.2-0ubuntu0.17.10.1~cloud0 with Pike to 12.2.4-0ubuntu1~cloud1 with Queens, so yeah I see your point about that being a minor upgrade and not a problem - I had thought we needed to keep the versions synced entirely but regular maint would pick that up and sync the versions anyhow."
1778823,2018-07-02 14:41:32 UTC,Xav - based on the comments in #1 and #2 what do you think is the right behaviour in this instance?
1778823,2019-02-01 09:48:00 UTC,"Reviewed:  https://review.openstack.org/634338
Committed: https://git.openstack.org/cgit/openstack/charms.ceph/commit/?id=33b408268546dd0904ea05d580828481afd5c1bc
Submitter: Zuul
Branch:    master"
1778823,2018-07-02 14:40:15 UTC,The percona-cluster charm currently will not change sources post install script execution.  Again the UCA does not have PXC packages - we just use the pkgs from Xenial - so for UCA sources this is a no-op.
1778824,2018-06-27 10:29:45 UTC,"I can reproduce this in a GNOME session, but not in Unity. Sounds like a bug with the window manager (gnome-shell or mutter)."
1778824,2018-06-27 10:29:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778824,2018-06-27 10:48:20 UTC,170x43 terminal with same font starts in normal window. Terminal of size 170x44 is maximized.
1778831,2018-06-29 12:23:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778833,2018-07-03 15:01:44 UTC,"For the record, this behavior disappears if I change the rule from:
SUBSYSTEMS==""usb"", ATTRS{whatever}==""whatever"", SYMLINK+=""ttyWhatever""
to:
SUBSYSTEM==""tty"", ATTRS{whatever}==""whatever"", SYMLINK+=""ttyWhatever"""
1778837,2018-06-27 04:20:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/578273"
1778837,2018-06-28 05:56:59 UTC,"There also are other timeouts for the overall job running time, the reason may be in different places, e.g. devstack"
1778837,2018-07-11 16:37:26 UTC,"Reviewed:  https://review.openstack.org/578273
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=ceaaf161e3ea9c0b6bcbe8aa48beda800b867d67
Submitter: Zuul
Branch:    master"
1778844,2018-11-12 17:04:45 UTC,"I have been working upstream to get this fixed on the nvme driver, but it might still take some time, I already have done a back and forth with hch. Will send a v3 later this month."
1778844,2018-09-28 11:58:40 UTC,"Just create a /etc/modprobe.d/nvme.conf file with the following contents, recreate initrd, remove kdump initrds so they are recreated in the next boot, then reboot."
1778844,2018-09-28 19:22:13 UTC,"First piece of the puzzle submitted:
http://lists.infradead.org/pipermail/linux-nvme/2018-September/020174.html"
1778844,2018-11-26 12:41:27 UTC,"Upstream discussion is progressing. I have tested some patches from hch, will send him some feedback later today and post the links here."
1778844,2019-05-22 07:13:45 UTC,"Thanks for the verification in comment #67. From the comment, I believe this was verified with bionic. Could you also verify with Cosmic and post your results?
Thanks."
1778844,2019-04-12 20:29:06 UTC,This bug was fixed in the package initramfs-tools - 0.131ubuntu19
1778844,2019-04-12 19:25:21 UTC,"initramfs-tools uploaded for disco.  Thadeu, do you want to prepare a separate debdiff for bionic and cosmic?"
1778844,2019-04-12 09:53:09 UTC,"------- Comment From <email address hidden> 2019-04-12 05:41 EDT-------
Hi ,"
1778844,2019-04-01 14:07:11 UTC,"Hi Thadeu, thanks for the update."
1778844,2019-04-01 13:55:35 UTC,"Hi, Andrew, with the debdiff attached and ubuntu sponsors team subscribed, now we should wait for someone on that team to sponsor that update. With the SRU template attached, the only thing blocking that sponsorship now is that disco is now on freeze, so the sponsor is the one who would decide whether this warrants an upload during the freeze."
1778844,2019-04-01 13:38:11 UTC,"Next step: Thadeu to propose the diff described in comment #53 into the archive.
(If this incorrect, please flag.)"
1778844,2019-03-01 19:02:16 UTC,"That's an OOM problem. Just increase the reserved crashkernel memory size and test again, please."
1778844,2019-02-12 11:45:06 UTC,"------- Comment From <email address hidden> 2019-02-12 06:15 EDT-------
(In reply to comment #87)

> Hi, Andrew and Hari.
>
> The original issue is only resolved by using an initramfs-tools from my ppa.
> We still need to get this fix included in our releases. I will start working
> to get this in disco.
>
> Cascardo.
"
1778844,2019-02-12 10:31:05 UTC,"Hi, Andrew and Hari."
1778844,2019-02-12 07:33:27 UTC,Thanks. Closing out the bug.
1778844,2019-02-12 06:22:04 UTC,"------- Comment From <email address hidden> 2019-02-12 01:11 EDT-------
(In reply to comment #83)
[...]

> Will try to increase to some more above 4096M and retry it.
"
1778844,2019-02-06 14:54:40 UTC,"------- Comment From <email address hidden> 2019-02-06 09:45 EDT-------
Triggered crash with patch using crashkernel=8192M and did not see OOM traces and dump copied properly as below"
1778844,2019-02-06 14:32:27 UTC,"------- Comment From <email address hidden> 2019-02-06 09:27 EDT-------
(In reply to comment #82)

> The system has too many devices, so too many drivers are using too much
> memory. So, the system goes out-of-memory before makedumpfile is complete.
> Please, reserve more memory on crashkernel, reboot the system and repeat the
> crash test.
>
> To reserve more memory on crashkernel, edit file
> /etc/default/grub.d/kdump-tools.cfg and change crashkernel value to
> crashkernel=384M, for example, then run update-grub.
>
> Thanks.
> Cascardo.
"
1778844,2019-02-06 08:38:06 UTC,"The system has too many devices, so too many drivers are using too much memory. So, the system goes out-of-memory before makedumpfile is complete. Please, reserve more memory on crashkernel, reboot the system and repeat the crash test."
1778844,2019-02-06 07:15:18 UTC,"------- Comment From <email address hidden> 2019-02-06 01:54 EDT-------
Have installed below patch and retried kdump scenario with root disk as nvme disk. Now system is not dropping to initramfs state its moving further but not saving dump file (core) properly."
1778844,2019-04-22 14:33:53 UTC,"Thadeu, the test case for the SRU needs to describe exactly the steps that will be followed to verify the correctness of this bugfix, so that anyone (with the necessary hardware) can follow them."
1778844,2019-01-16 16:38:19 UTC,I have pushed a version of initramfs-tools to my ppa that seems to fix the problem. Can IBM test it?
1778844,2019-04-22 15:03:42 UTC,"@vorlon, test case updated."
1778844,2019-05-14 21:22:59 UTC,"Hello bugproxy, or anyone else affected,"
1778844,2019-06-27 10:18:52 UTC,This bug was fixed in the package initramfs-tools - 0.131ubuntu15.2
1778844,2019-06-25 18:03:26 UTC,------- Comment (attachment only) From <email address hidden> 2019-06-25 13:54 EDT-------
1778844,2019-06-25 18:03:24 UTC,"------- Comment From <email address hidden> 2019-06-25 13:53 EDT-------
Yeah. The issue was indeed with ""nr_cpus=1"".
Not hitting initramfs shell after updating to initramfs-tools version in -proposed
and using ""maxcpus=1"" (LP bug 1828597)"
1778844,2019-06-25 16:24:06 UTC,"------- Comment From <email address hidden> 2019-06-25 12:13 EDT-------
Michael, actually this sounds like LP 1828597
It is worth trying with maxcpus=1 instead of nr_cpus=1"
1778844,2019-06-25 14:26:27 UTC,"------- Comment From <email address hidden> 2019-06-25 10:14 EDT-------
I tried this on a witherspoon with NVMe, but I believe I also hit LP 1778844:"
1778844,2019-06-24 13:46:44 UTC,"Following call with IBM, verification testing is in progress. Hoping to have test results posted in the next 24 hours (approx)."
1778844,2019-06-24 08:07:21 UTC,verification-needed-cosmic is blocking publishing the next initramfs-tools update in cosmic.
1778844,2019-06-11 18:03:41 UTC,"@Thadeu, here is a new bug report that tracks this issue: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1832388 We dont have a system in house with NVme, we will need IBM to verify -proposed with cosmic and report back here."
1778844,2019-06-11 17:05:43 UTC,"Hi, Manoj."
1778844,2019-06-10 20:08:33 UTC,"I installed cosmic on power9 (boston) a non-nvme system, installed initramfs-tools from -proposed and install kdump-tools. Triggered a dump, but I got a kernel panic. Please let me know if I am doing something wrong here."
1778844,2019-05-28 16:55:21 UTC,"The verification of the Stable Release Update for initramfs-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1778844,2019-05-28 16:55:11 UTC,This bug was fixed in the package initramfs-tools - 0.130ubuntu3.8
1778844,2019-05-21 19:29:23 UTC,Thank you for taking the time to verify this stable release fix.  We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE).  Please remove the verification-done tag and add one for the release you have tested the package in.  Thank you!
1778844,2019-05-21 13:43:11 UTC,"------- Comment From <email address hidden> 2019-05-21 08:26 EDT-------
Installed latest initramfs-tools & kdump-tools packages from -proposed kernel as below"
1778844,2019-05-14 21:25:53 UTC,"Hello bugproxy, or anyone else affected,"
1778844,2019-04-29 13:35:01 UTC,Added to the SRU queue on 22nd April. Thanks!
1778844,2019-01-15 17:19:27 UTC,"On 01/15/2019 09:26 AM, Thadeu Lima de Souza Cascardo wrote:

> Upstream is a little reluctant to accept my changes, and seems to
> suggest that we find out the layout of the paths some other way (which
> is possible, but would be such a special case on initramfs-tools, only
> for nvme).
>
> Cascardo.
>


Hmm, I am really sorry about that - sux to do all that work and get that
kind of response."
1778844,2019-02-06 07:15:20 UTC,------- Comment on attachment From <email address hidden> 2019-02-06 01:56 EDT-------
1778844,2018-06-27 05:39:44 UTC,Default Comment by Bridge
1778844,2019-01-15 16:26:56 UTC,"Upstream is a little reluctant to accept my changes, and seems to suggest that we find out the layout of the paths some other way (which is possible, but would be such a special case on initramfs-tools, only for nvme)."
1778844,2018-09-20 11:10:50 UTC,"------- Comment From <email address hidden> 2018-09-20 07:06 EDT-------
Hi,"
1778844,2018-09-20 11:41:37 UTC,------- Comment on attachment From <email address hidden> 2018-09-20 07:31 EDT-------
1778844,2018-09-20 11:41:50 UTC,------- Comment on attachment From <email address hidden> 2018-09-20 07:34 EDT-------
1778844,2018-09-20 11:42:39 UTC,------- Comment on attachment From <email address hidden> 2018-09-20 07:38 EDT-------
1778844,2018-09-20 11:52:10 UTC,"------- Comment From <email address hidden> 2018-09-20 07:42 EDT-------
Unable to attach ""lp1778844_sys.tar.gz"" file because of size, please refer to logs path .Also test machine is taken back for other release testing."
1778844,2018-09-25 08:42:19 UTC,"------- Comment From <email address hidden> 2018-09-25 04:34 EDT-------
Hello Canonical"
1778844,2018-09-27 07:05:04 UTC,"------- Comment From <email address hidden> 2018-09-27 02:42 EDT-------
Cascardo/Canonical, Did you get a chance to look at the logs attached?"
1778844,2018-09-27 10:04:29 UTC,"I managed to download the lp1778844_sys.tar.gz from FTP in time. It has some huge resource files, so I have to play a little with the tarball. It looks like some symlinks were tarred as empty files, so maybe I'll miss something, but I am investigating right now. I'll let you know if I need any other information. I will look at the other files as well."
1778844,2018-09-27 14:17:36 UTC,"So, this is a multipath disk, whose parent is the nvme-subsys0 device, not nvme0 device. The latter is a PCI device, but the former is a virtual one. Some code to add slaves/holders relationships was added, but reverted. I will investigate any further discussion about this upstream, or look into how to relate those nodes in a way we can just fix this in initramfs-tools."
1778844,2018-09-27 19:46:48 UTC,"So, the hidden disk was introduced by hch as commit 8ddcd653257c18a669fcb75ee42c37054908e0d6 just to support nvme multipath. This thing prevented lsblk from working when there were slaves under the multipath nvme, as lsblk would postpone processing those, and lsblk could not process the paths themselves, because they have no dev_t."
1778844,2018-09-27 19:49:18 UTC,"As a workaround, I suggest setting nvme-core.ko multipath=0 parameter. Can you try that, rebooting, recreating the kdump-tools initrd, then crashing?"
1778844,2018-09-28 00:12:23 UTC,"i downloaded that, and tried to poke it.
First of all, i've never seen a 77MB tarball of /sys alone.
Also unpacking that, is dangerous as it does explode in size. However, is debugging that, please only _list_ the files present in the tarball and only extract things you need/want."
1778844,2018-09-28 02:33:43 UTC,"------- Comment From <email address hidden> 2018-09-27 22:06 EDT-------
(In reply to comment #61)

> As a workaround, I suggest setting nvme-core.ko multipath=0 parameter. Can
> you try that, rebooting, recreating the kdump-tools initrd, then crashing?
"
1778844,2018-12-14 18:16:29 UTC,https://lore.kernel.org/linux-block/20181213113549.GA7543@calabresa/T/#t
1778844,2018-07-27 17:23:11 UTC,"Hi, Hari."
1778844,2018-07-25 05:30:43 UTC,"------- Comment From <email address hidden> 2018-07-25 01:28 EDT-------
(In reply to comment #34)

> Created attachment 128858 [details]
> sosreport_moduels=set
>
> Attached sosreport when MODULES=set used
"
1778844,2018-07-27 17:36:14 UTC,"Ah, I see what you meant about the PHB. The two new attached logs are not at all similar to the original ones, maybe pointing to an unrelated problem."
1778844,2018-07-23 17:02:05 UTC,Can you run apport-collect -p linux 1778844 ?
1778844,2018-06-27 05:39:47 UTC,Default Comment by Bridge
1778844,2018-06-27 05:39:49 UTC,Default Comment by Bridge
1778844,2018-06-27 05:39:51 UTC,Default Comment by Bridge
1778844,2018-06-27 05:39:53 UTC,Default Comment by Bridge
1778844,2018-07-24 10:40:59 UTC,"------- Comment From <email address hidden> 2018-07-24 06:36 EDT-------
(In reply to comment #36)

> Can you run apport-collect -p linux 1778844 ?
>
> Thank you.
> Cascardo.
"
1778844,2018-07-09 14:30:37 UTC,"Kernel team, looks like the root cause identified by IBM (taken from description of the bug) is:"
1778844,2018-07-16 16:03:20 UTC,I will look at this later today. Will send updates on it.
1778844,2018-07-16 22:25:23 UTC,"As we use MODULES=dep for kdump initrd, that might fail to include the proper modules. It would be a bug on initramfs-tools-core."
1778844,2018-07-09 10:19:47 UTC,"------- Comment From <email address hidden> 2018-07-09 06:18 EDT-------
Canonical, any update on this..?"
1778844,2018-07-23 11:19:56 UTC,------- Comment on attachment From <email address hidden> 2018-07-23 07:12 EDT-------
1778844,2018-07-23 11:19:58 UTC,------- Comment on attachment From <email address hidden> 2018-07-23 07:13 EDT-------
1778844,2018-07-23 11:40:09 UTC,"------- Comment From <email address hidden> 2018-07-23 07:30 EDT-------
Indira, I think Cascardo is looking for /tmp/initrd.img-`uname -r` file
whne MODULES=dep is used. Also, sosreport?"
1778844,2018-07-23 12:20:22 UTC,"------- Comment From <email address hidden> 2018-07-23 08:14 EDT-------
Also both logs were placed in"
1778844,2018-07-23 12:21:13 UTC,------- Comment on attachment From <email address hidden> 2018-07-23 08:11 EDT-------
1778844,2018-07-23 12:21:28 UTC,------- Comment on attachment From <email address hidden> 2018-07-23 08:12 EDT-------
1778844,2018-07-20 21:12:38 UTC,"I have managed to test kdump and initramfs with MODULES=dep on an emulated nvme, using qemu. Both worked just fine. The sysfs tree seems reasonable too, in respect to how initramfs finds the necessary modules."
1778859,2018-06-27 12:38:39 UTC,"Confirmed in bionic, and fixed in the package I'm preparing for cosmic. On its own, this of course doesn't warrant an SRU, but it should be included if there is another fix being released for bionic."
1778859,2018-08-24 17:34:22 UTC,This is fixed in 4.8.4 which just landed in cosmic.
1778860,2018-06-27 12:53:08 UTC,"The fact that the vfs_aio_linux module was dropped should go into the release notes, so I added a bug task for that."
1778860,2018-06-27 13:29:09 UTC,Release notes updated: https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#Samba
1778863,2020-05-07 23:32:04 UTC,"Bug has been incomplete for nearly two years, closing."
1778863,2019-02-21 14:43:38 UTC,Sorry for leaving this for so long. Is it still a problem? Can you show me the logs if you can still reproduce it?
1778887,2019-03-27 14:44:56 UTC,From duplicate: add to paste layer
1778890,2018-07-23 14:04:04 UTC,Definitely
1778890,2018-07-23 14:04:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778896,2020-04-10 13:30:15 UTC,"This is still a problem on Focal. See attached screenshot. Triggered by me running apt dist-upgrade in a terminal, I guess while update-manager was also up to something in the background."
1778896,2020-04-10 13:31:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778900,2018-06-27 11:30:50 UTC,On Ubuntu 18.04.
1778900,2018-11-13 12:30:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778906,2020-02-19 17:02:21 UTC,"Hi, this has been reported to Gitlab as well: https://gitlab.com/inkscape/inbox/issues/1459"
1778906,2020-02-19 18:12:18 UTC,"Excuse me @jhofinger, could you please explain why this bug report wasn't moved to the new issue tracker in the first place? It only gets moved now that someone else came up with the same idea years later? I wonder how many other good ideas are left lingering launchpad."
1778906,2020-05-22 08:47:03 UTC,"Dear A. There is a project to port bugs, there are thousands and thousands of bugs on launchpad and a very limited set of resources able to process them. When we moved from launchpad we didn't just loose good ideas, we lost people too. So our bug team completely collapsed."
1778908,2018-06-27 16:24:42 UTC,"Ahhh obviously fully Mixxx's fault, just realised the libtag version it fails to downgrade to is in their ppa and not the Ubuntu repo looking at the apt-cache policy output."
1778908,2018-06-27 16:50:57 UTC,Why does Launchpad not recognise Launchpad's bug tracker when you try and associate another package as being affected? I wanted to correctly link this bug on the Mixxx tracker but it throws up an error of unrecognise bug tracker!!
1778911,2018-11-13 15:30:38 UTC,"Hi,
we are using ntp as a standard service, and it's deployed and configured by puppet. So using chrony instead of ntp client is not really an option."
1778911,2019-05-14 15:58:05 UTC,"Looks like this was fixed in 4.7.1-1 in Debian, so this is fixed >= Cosmic in Ubuntu."
1778911,2018-06-27 13:08:08 UTC,"Currently we have these:
Reverse-Recommends
==================
* ceph-base                     (for chrony)"
1778911,2018-06-27 13:01:00 UTC,I agree that in a world of systemd-timesyncd by default packages could stop depending on time-servers in most of the cases. But that is not a bug in chrony but in freeipa.
1778911,2018-07-03 18:07:33 UTC,I need a time daemon with server capabilities so we can easily monitor clock skew.
1778912,2018-09-19 09:26:53 UTC,https://discourse.jujucharms.com/t/agent-introspection/117 is a good start :)
1778914,2018-07-03 16:01:32 UTC,"if you run haproxy on the same physical node as galera, you will hit issues:
Assuming we bind haproxy to external and internal lb vip address (on the management network), on which network would mysql listen to? only local socket? That sounds overkill."
1778914,2018-07-03 16:59:22 UTC,"This is indeed an issue, my proposed solution:"
1778914,2018-07-03 16:59:44 UTC,"Juha, if you would like to work on a fix, we can help you with landing it!"
1778914,2018-07-05 10:59:33 UTC,Could this be the solution (openstack-ansible-galera_server/templates/my.cnf.j2):
1778914,2018-08-22 13:04:42 UTC,I would like to work on this. Your help is highly appreciated.
1778926,2018-10-03 12:01:23 UTC,"Reviewed:  https://review.openstack.org/568858
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=8aa4a9c1dd5dda8273226d2538028689aa6c871d
Submitter: Zuul
Branch:    stable/queens"
1778926,2018-12-05 04:08:36 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.1.0 release.
1778930,2018-07-30 12:54:06 UTC,"Hello,
The patch has been accepted upstream (http://icedtea.classpath.org//hg/release/icedtea7-forest-2.6/hotspot?cmd=changeset;node=e012acbfcd40)"
1778930,2018-07-14 13:25:24 UTC,"In an attempt to contribute to similar cases and show interest in the eventual fix, herewith attached goes the log of the ""segfault"" in my system."
1778930,2018-07-12 01:39:25 UTC,"OpenJDK upstream bug report: https://bugs.openjdk.java.net/browse/JDK-8207151
Fix proposal: http://mail.openjdk.java.net/pipermail/jdk7u-dev/2018-July/010787.html"
1778930,2018-07-10 11:03:30 UTC,"Thanks, in case it gives any other clue, the breaks do not happen every time, but it seems to match a FullGC."
1778930,2018-07-09 19:31:37 UTC,We've analyzed this bug and have a good understanding of what's going on. A fix will be ready soon.
1778930,2018-06-27 16:37:25 UTC,"Hell Tiago,
on your recommedation on irc i also reported that upstream to icedtea here:
https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3604"
1778930,2018-07-09 07:29:54 UTC,"We have this problem too, tomcat 7 and production. You know any workaround?"
1778930,2018-06-29 01:25:20 UTC,Thanks Tiago. The fix for 8189123 in the last security update had to be pretty much re-written for OpenJDK 7 due to the removal of permgen in 8 and up. I'll point the developer of the patch at this bug and hopefully we can get a resolution to this.
1778930,2018-07-30 15:08:11 UTC,please test the patch in https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+packages
1778930,2018-06-27 15:32:30 UTC,"I installed tomcat7 and tested a couple of very simple hibernate samples from around the web, none were able to trigger this issue."
1778930,2018-07-09 09:34:37 UTC,"Hello Guillermo,"
1778930,2018-08-09 23:17:04 UTC,This bug was fixed in the package openjdk-7 - 7u181-2.6.14-0ubuntu0.2
1778930,2018-06-27 17:57:32 UTC,Attaching the bt full backtrace provided by the Huehner to the IcedTea bug.
1778932,2018-06-28 10:38:27 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1778932,2018-06-29 12:36:34 UTC,permissions issue in ownership of .cache/apport
1778932,2018-06-29 13:52:41 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1778932,2018-06-28 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1778932,2018-08-29 04:17:33 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1778932,2019-05-01 19:14:36 UTC,"This bug can be reliably triggered, My concern is that the system then requires a Hard Restart, Power down the server is the only solution for the Server.  It will immediately crash when rsync is started.  This is new to 18.4 previously we ran this rsync every hour on 16.4 no issues. The model for this is a remote server uses rsync to back or mirror the server."
1778932,2019-05-24 09:21:47 UTC,"un 26 19:49:20 music kernel: [  242.955115] BUG: unable to handle kernel paging request at 0000020000000020
Jun 26 19:49:20 music kernel: [  242.955125] IP: find_get_entry+0x4c/0x140
Jun 26 19:49:20 music kernel: [  242.955126] PGD 0 P4D 0
Jun 26 19:49:20 music kernel: [  242.955129] Oops: 0000 [#1] PREEMPT SMP NOPTI"
1778932,2019-05-29 00:58:26 UTC,This is happening on two system with an Intel motherboard. Other systems with a Silicon Mechanics motherboard and the same OS do not crash when rsync is used.
1778932,2019-05-29 00:32:07 UTC,Sadly it died with this crash:
1778932,2019-05-29 00:43:09 UTC,Somewhat different the second time around.  This is with the 5.0.05-15 kernel.
1778932,2018-06-29 12:36:09 UTC,apport information
1778932,2019-05-29 19:26:15 UTC,"Ah, this time it actually reported a bug:"
1778932,2021-01-18 07:48:44 UTC,"Hi to all.
I know that is an old topic but today I faced an isue with rsync. After this command "" rsync -Aavx /var/www/html/nextcloud/ /mnt/backup/nextcloudbk/nextcloud-dirbkp_`date +""%Y%m%d%t""`/ "" the ubuntu server 20.04 has crashed. On every command the system response is "" bash: /usr/bin/'command': No such file or directory
 "". Nothing works any more. Is the secont time that happens to me. Last week, it happend firs time and I don't realise that is rsync problem until I reinstalled the server and I run this command again. I even can't go in log file. Doesn't work any command. After reboot, ubuntu crashes on load.
I don't think it is a repair for this. And the work begin with the reinstall of ubuntu.....again.
Sorry for my english."
1778932,2019-05-28 22:31:17 UTC,"I'm having similar problems with rsync killing a 18.04 head node that's writing to a NFS share.  It would die pretty quickly with rsync or globus.  We had a dozens of crashes, we originally thought it was a hardware issue, but switching to a different server didn't help."
1778932,2018-06-29 12:36:08 UTC,apport information
1778932,2018-06-29 18:47:16 UTC,"I was not really able to use a kernel older than 4.15 because of my GPU. And it seems to perhaps be more unstable now than it was when it was initially installed. I really desire a low-latency kernel, though.  I've kept BIOS updated to the most recent release from the manufacturer. I'l try 4.18 kernel.  thanks."
1778932,2018-06-29 12:36:05 UTC,apport information
1778932,2018-06-29 12:36:04 UTC,apport information
1778932,2018-06-29 12:36:02 UTC,apport information
1778932,2018-06-29 12:36:01 UTC,apport information
1778932,2018-06-29 12:36:00 UTC,apport information
1778932,2018-06-29 12:35:58 UTC,apport information
1778932,2018-06-29 12:35:57 UTC,apport information
1778932,2018-06-29 12:35:56 UTC,apport information
1778932,2018-06-29 12:35:54 UTC,apport information
1778932,2018-06-29 12:35:53 UTC,apport information
1778932,2018-06-29 12:33:31 UTC,I am trying to collect the data.  keep getting this error. researching
1778932,2018-06-27 14:18:46 UTC,attaching syslog which shows the crash appearing.
1778932,2018-06-27 14:47:18 UTC,And I blacklisted a module that might have been contributing.  (hid_uclogic)  but the problem persists.
1778932,2018-06-29 12:36:06 UTC,apport information
1778933,2018-06-27 14:47:35 UTC,Failing command was: disk-image-create -o /httpboot/ipa fedora proliant-tools ironic-agent iso
1778934,2020-01-19 09:44:54 UTC,The new version has been synced to Ubuntu Focal and will be part of 20.04 (https://bugs.launchpad.net/ubuntu/+source/libpam-radius-auth/1.4.0-2)
1778934,2019-10-27 09:44:39 UTC,"As mentioned above, the package is still orphaned in Debian, though someone did a QA upload of  1.4.0-2."
1778934,2018-06-28 09:52:56 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1778940,2018-06-28 18:42:33 UTC,A little slower than I'd hoped but here it is: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1778940_ate_indexes working/user/jboyer/lp1778940_ate_indexes
1778940,2019-03-01 15:53:23 UTC,"I was curious how much extra space this would take up, so here are the stats from our system."
1778940,2019-03-01 16:58:23 UTC,"Signoff branch at
user/stompro/lp1778940_ate_indexes_signoff"
1778940,2019-04-24 19:48:06 UTC,"Pushed to master, rel_3_3, and rel_3_2. Thanks Jason and Josh!"
1778941,2018-07-27 23:08:22 UTC,"Try modifying /etc/update-manager/release-upgrades and set ""Prompt=lts"" and then try upgrading again. Right now you are trying to upgrade to Ubuntu 14.10 which is an unsupported release of Ubuntu."
1778943,2018-06-27 22:49:31 UTC,it just occurred to me that this is not happening on the debian sid i am running on the desktop (iMac - inxi attached). and both of them are as upto date as possible.
1778943,2018-09-05 08:10:44 UTC,I confirm that this is the case. I am using an Ubuntu 18.04 system and cairo-dock 3.4.1.
1778943,2018-10-18 21:58:30 UTC,pramathesh ambasta - are you also using an intel video driver?
1778943,2018-10-18 22:01:22 UTC,"Also if it is, is it an nvidia optimus?"
1778946,2020-01-14 12:12:58 UTC,"I too have been facing this issue since a few releases, and still face it on Ubuntu 19.10 (resolvconf not installed as it causes other issues):"
1778946,2018-06-30 15:36:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778946,2020-09-10 18:59:17 UTC,"The patch from #19 (which is now in Ubuntu) is not enough - there are still problems with network-manager-sstp, which calls pptp with ""nm-sstp-service-*""."
1778946,2020-03-26 05:58:49 UTC,The problem is still there on Ubuntu 18.04.4 LTS. The workaround from comment #30 works for me.
1778946,2020-03-25 11:56:05 UTC,"Ubuntu 18.04.4 LTS, same problem: DNS_PROBE_FINISHED_BAD_CONFIG after disconnecting from MS VPN.
I can confirm that workaround by Marius Gedminas from comment #30 works as expected."
1778946,2020-03-18 20:32:54 UTC,The workaround I now use is to modify the cp -a command in /etc/ppp/ip-up.d/0000usepeerdns to look like this:
1778946,2020-03-18 20:21:53 UTC,Unfortunately the fix doesn't work and Ubuntu 19.10 with ppp 2.4.7-2+4.1ubuntu4.1 is still affected.  I've added a bunch of
1778946,2020-02-28 13:21:09 UTC,Will this get backported to Bionic please? Or do we have to wait for the 20.4 LTS release?
1778946,2019-10-08 16:25:45 UTC,Can confirm. Work-around is to turn off WiFi and re-enable it.
1778946,2019-04-22 08:59:51 UTC,This bug was fixed in the package ppp - 2.4.7-2+4.1ubuntu2
1778946,2019-04-20 19:11:33 UTC,Uploaded to Eoan.
1778946,2019-04-18 15:49:43 UTC,"I've manually applied the patch proposed in comment #22 to my Ubuntu 18.10 desktop, and I can confirm that it fixes the issue for me. I haven't seen any regression either, although my testing has been very limited so far."
1778946,2019-02-08 20:59:58 UTC,"Attached is the debdiff with the proposed fix of comment #19 applied. Someone with appropriate upload rights to Disco, please upload it."
1778946,2019-01-30 16:42:41 UTC,"Although this problem is easy to fix once you know what to do, I don't know if it should be only ""Medium"" importance because the impact is massive: no DNS is available.  If you're not technically inclined enough to know to go poking around /etc/resolv.conf if DNS breaks, you would never be able to figure out what was wrong with your system and you can't search the internet to find a solution..."
1778946,2019-01-20 22:21:00 UTC,"Comment 6 and 7 in the upstream GNOME NetworkManager-pptp bug report :
    https://bugzilla.gnome.org/show_bug.cgi?id=785771#c6
are relevant to this bug (but not the 'cp -a' issue)."
1778946,2019-01-20 06:09:18 UTC,I wasn't able to redirect the stderr from the following line in /etc/ppp/ip-up.d/0000usepeerdns (probably because of something pppd is doing) :
1778946,2019-01-31 11:07:37 UTC,"As I see the comments here, the fix is to modify the file /etc/ppp/ip-up.d/0000usepeerdns according to comments #17 and #19. /etc/ppp/ip-up.d/0000usepeerdns is part of the ppp package, so the bug needs to be fixed in the ppp package."
1778946,2019-01-17 12:39:14 UTC,Correction the following line in /etc/ppp/ip-up.d/0000usepeerdns probably should be changed from :
1778946,2018-06-30 15:44:52 UTC,Before start pptp vpn:
1778946,2018-09-05 17:31:44 UTC,seems related to the file /etc/ppp/ip-up.d/0000usepeerdns on line 23-24
1778946,2018-10-26 09:11:20 UTC,"It would be a bug in ""ppp"" which provides that file then and worth reporting to Debian because it's coming from there directly"
1778946,2018-10-26 17:15:39 UTC,"This upstream bug suggests that the problem can be resolved by installing resolvconf:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378363"
1778946,2019-01-17 13:08:32 UTC,Sorry ignore comment #16 as the following line in /etc/ppp/ip-up.d/0000usepeerdns will exit because of the '#!/bin/sh -e' shebang line:
1778946,2018-10-31 09:14:18 UTC,"Installing resolveconf fixed it for me, now DNS resolv works after PPTP disconnects."
1778946,2018-10-26 19:30:00 UTC,"I spoke to stgraber a bit, he said that the resolvconf thing is probably a red herring."
1778946,2018-10-31 14:20:07 UTC,"cp -a is supposed to preserve ownership. -a means ""-dR --preserve=all""."
1778946,2018-11-06 14:37:31 UTC,"tagging as rls-cc-notfixing, while good to fix it impacts a non default plugin and we don't think it's important enough to be actively tracked by desktop"
1778946,2018-11-16 02:09:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778946,2018-11-28 12:35:06 UTC,Sorry for the delay here.
1778946,2019-01-17 12:35:54 UTC,I can confirm the issue is the following line in /etc/ppp/ip-up.d/0000usepeerdns as previously mentioned :
1778946,2018-10-31 09:22:39 UTC,Also confirming that installing resolvconf makes DNS work once the VPN is disconnected.
1778949,2018-06-27 16:39:09 UTC,"I have a feeling even if we fix this bug, we'll have to support both ways of deprecating a policy for backwards compatibility. But we could just advertise the preferred way to deprecate in our documentation."
1778949,2018-06-28 14:01:33 UTC,The new proposal seems reasonable.  We have a similar feature in oslo.config with the DeprecatedOpt class: https://github.com/openstack/oslo.config/blob/9c71b0140931b51ffffc3bbdc1b655fdaccce45b/oslo_config/cfg.py#L1223
1778955,2020-08-06 16:57:33 UTC,"Thanks for this branch, Mike, and for catching that issue, Dan.  I signed off at user/sandbergja/lp-1778955-use-builtin-array_remove"
1778955,2018-06-27 16:51:50 UTC,Branch at:
1778955,2019-05-24 18:22:35 UTC,"This code is difficult to check by only its behavior (which should be identical to the old behavior), but while doing a desk check, I saw something unusual."
1778956,2020-09-14 19:36:58 UTC,Continues to be an issue in 3.5
1778959,2018-06-28 12:53:17 UTC,"The problem is described correctly. There is a lot of documentation on the internet about this ""floating point exception"" error, which apparently has been introduced in versions prior to Ubuntu 18.04.
https://askubuntu.com/questions/1050008/iptraf-ng-error-floating-point-exception
If you do not want to solve this error, close the incident. Many people had already warned me that reporting an incident on this site is a waste of time."
1778959,2018-07-09 20:45:14 UTC,I also couldn't reproduce this bug.
1778959,2018-06-28 09:54:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1778966,2018-06-27 22:14:44 UTC,"This sounds like the same problem we're investigating in Fedora/RHEL land affecting guests with EPYC CPU, or host-passthrough from an EPYC family 17h host.  Workaround should be to use ""-cpu Opteron_G5"" for now"
1778966,2018-06-28 14:59:43 UTC,That is very helpful. I'll try it.
1778966,2018-06-29 02:06:23 UTC,"Regrettably opteron_g5 is not a workaround. I get a complaint that my cpu doesn't provide xop, fma4, tbm."
1778966,2018-06-29 02:13:20 UTC,Opteron didn't work do to some missing features. I was able to get nehalem to come up but that looks like the closest.
1778966,2018-06-29 02:15:43 UTC,Is there any way to define a new CPU model that isn't EPYC (maybe ryzen?) but is feature compatible with the threadripper?
1778966,2019-10-12 14:05:01 UTC,"I ran into the same problem on threadripper 1900X. I was using cpu type ""host-passthough"" and it crashed. I fixed the crash by disabling the MSR with"
1778966,2020-11-12 14:14:38 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1778970,2018-08-17 18:16:47 UTC,"some more info [0], we can see the offer is not listed under `juju offers`, but it remains in juju status for the selected model even following removal."
1778970,2019-10-31 04:07:58 UTC,Removing from a milestone as this work will not be done in 2.3 series.
1778972,2020-09-12 17:12:06 UTC,"Chris: sure, let me take a look!"
1778972,2020-09-08 15:30:46 UTC,"Just as a side note, this is more than just a template at this point as some Javascript files and perl files needed to be edited to make all the changes work harmoniously with the current and proposed OPAC. You will need a full load of this patch to make the OPAC completely functional."
1778972,2020-08-21 19:47:17 UTC,"This is looking good! The bug comments are a bit long, so someone may have already noticed. When viewing shelf browse on monitor at full screen, there appears to be a mix of dotted and straight line under Shelf Browser and Next Page button (image attached). When viewing on a smaller screen, I don't see it."
1778972,2020-08-21 19:35:14 UTC,The addition of the icon package opens up a simple way to fix an accessibility issue with the Holds Success/Failure messages being very similar mentioned below.
1778972,2020-08-19 21:44:03 UTC,A few more small things:
1778972,2020-08-19 15:54:42 UTC,"I filled a basket with items, viewed the basket, and from the ""view basket"" screen, chose to place a hold on all of the items.  There was no notification that the holds had been placed, and I was not taken to the holds screen to verify my notification/pickup methods.  The holds were not placed.  I believe that is because the account (testUser; demo123) is expired.  There was no message, however, indicating that."
1778972,2020-08-11 20:06:40 UTC,"Related to the expert search, when scoping the search to the consortium, the MARC tag search displays results for the consortium and the preferred library.  When scoping to a library, no results are retrieved."
1778972,2020-08-18 19:47:18 UTC,"I found an issue on the Expert search page. If I have more than 1 row and try to remove one, it does not remove the row. I think the issue is with the killRowIfAtLeast(min, link) function in simple.js. It's only set up to recognize TR tags."
1778972,2020-08-14 16:25:53 UTC,The server has been updated and is live again. I have tested the MARC Record page and Expert page and can confirm they work again.
1778972,2020-08-11 21:04:55 UTC,"Yes. I have identified a few server related errors on the test server and I will be rebuilding it to current before Feedback Week next week. The MARC record for one, I confirmed as a server based error and not the template as the template was fine on a secondary server"
1778972,2020-09-09 13:38:14 UTC,"I have tested this and note several fixes and some outstanding issues.
Outstanding issues:
1. lack of an alert/message when a hold fails to be placed.
2. functionality issues when attempting to places holds from ""view basket"" interface. Placing holds from basket menu > place holds works."
1778972,2020-08-11 20:02:04 UTC,N/m my comment about the expert search failing.  But don't n/m the comment about the MARC producing a server error.
1778972,2020-08-11 19:59:17 UTC,"In the test OPAC, attempting to view the MARC record from an individual record page produces an internal server error.  I think (but could definitely be wrong) that this is somehow also the reason that an expert search fails."
1778972,2020-08-19 15:49:01 UTC,"I can confirm Llewellyn's observation regarding undeletable rows in the expert search.  In the search results page, I also encountered display issue.  The ""place hold/add to basket/add to my list"" element on the right hand side of the each record doesn't align with the actual record. I've attached a screen shot of it happening ""above the fold"" but it persists in record rows as you scroll down as well."
1778972,2020-09-09 15:22:26 UTC,"Thanks Ruth! I identified the problem with the buttons on the basket interface and have fixed that!
There also is a message when a hold fails to place https://imgur.com/a/88xX67Q. Is there another location a message is expected?"
1778972,2020-09-10 13:46:07 UTC,"As a heads up, today and tomorrow I will be taking on a comprehensive review of this for inclusion in 3.6. The specific goals I have in mind are:"
1778972,2020-09-09 15:44:21 UTC,"I have tested this code and consent to signing off on it with my name, rfrasur and my email address, <email address hidden>. (not sure this is necessarily necessary, but there it is)."
1778972,2020-09-09 16:22:11 UTC,I jumped on the band wagon and made a small change to the css to move the label text up a nudge. Tip of the collab branch
1778972,2020-09-09 16:54:03 UTC,Perhaps the change should go in the template CSS file and override that class? If bootstrap gets updated or replaced or pulled from the bootstrap repo with npm or something that change could end up getting squashed
1778972,2020-09-10 14:36:00 UTC,"Re Blake's patch, I agree with Chris: the core Bootstrap stuff should not be changed directly, as it will shortly be pulled from NPM and not bundled."
1778972,2020-09-10 14:36:40 UTC,Noting that for now that the branch I'm working in for my review is user/gmcharlt/bootstrap_review.
1778972,2020-09-10 14:52:22 UTC,"Christopher - you're right, though it's a subtle change, it made the boxes line up better for all of the screen resolutions I tested. Are you suggesting adding a CSS clause to ""templates-bootstrap/opac/css/style.css.tt2"" ? I'll commit that"
1778972,2020-09-10 15:06:27 UTC,Done
1778972,2020-09-10 15:52:19 UTC,user/gmcharlt/bootstrap_review now includes patches to:
1778972,2020-09-11 21:33:14 UTC,I'm now ready to sign off on this as an experimental feature. Branch is user/gmcharlt/bootstrap_signoff.
1778972,2020-09-12 16:14:01 UTC,"Added to master, for inclusion as an experimental feature in 3.6.  This is a great step forward for the OPAC, and I'm excited to watch it develop further."
1778972,2020-09-12 16:40:13 UTC,Thank you everyone for your feedback!
1778972,2020-09-12 16:40:38 UTC,See bug 1895398 for some follow-up needs that I noted.
1778972,2020-08-11 18:59:55 UTC,I've updated collab/gmcharlt/lp1778972_opac_redesign with the latest and greatest from Chris and the master branch.
1778972,2020-09-09 15:41:54 UTC,"Chris,"
1778972,2020-08-04 16:51:14 UTC,"Another update was pushed today, it is a Final Draft of sorts."
1778972,2020-02-22 16:06:20 UTC,"The design looks clean and pleasant.  For me, it appears to be a significant reduction in utility because of the wasted vertical space.  After a search for ""Harry Potter"", I see one single result (!) on my FHD screen; when I scroll, I can see at most 3 results at the same time."
1778972,2020-06-30 01:11:01 UTC,"Okay, I pushed two commits to the collab branch implementing my suggestions.  The second one just fixes a mistake in my first commit hahaha."
1778972,2020-07-24 21:10:28 UTC,Another commit was made with a number of changes while running a long list of pages through validation.
1778972,2018-06-27 18:44:02 UTC,Very clean and bright!
1778972,2018-10-09 16:09:30 UTC,"This looks like a very nice design!  Thanks, Christopher."
1778972,2018-10-10 16:25:43 UTC,"The grid and table responsiveness is a special blend of CSS I have been using to increase accessibility when it comes to tables. Although, I haven't tested it on screen readers yet."
1778972,2020-02-20 21:12:43 UTC,https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=1abd0ccaa4cc070cbe0852795327fd83eccf8c7f
1778972,2020-02-20 21:21:24 UTC,"Change opac to opac-old and opac-new to opac in the templates folder to use.
It was suggested to sideload as an opt in for a version before flipping the OPAC over fully."
1778972,2020-02-21 16:40:13 UTC,"Thanks for sharing this work, Chris. I haven't spent much time with the redesign, yet, but I like the direction!"
1778972,2020-02-21 17:15:01 UTC,Thanks for the feedback. I have updated the wording there.
1778972,2020-09-12 18:15:57 UTC,"Confirmed that f5c39df gets our logo back, makes the html more valid, and removes a duplicate process block.  Pushed to master; thanks, Chris."
1778972,2020-02-24 20:37:21 UTC,"Overall, I really like the look of this design. I have a few suggestions for improvements:"
1778972,2020-02-25 22:52:44 UTC,"Hi, thank you so much for working on this. I am not a coder but a Librarian that works directly with the public showing them how to use the OPAC. I know that they will be pleased with many of the changes so far.
I have a few questions, and I apologize if I am just unaware of underlying factors or reasons for the things I point out here. Screenshots are in the attached document."
1778972,2020-02-25 22:57:41 UTC,"Are the new Carousels compatible with this test site? If so, can you put one up?
Thanks"
1778972,2020-03-02 20:35:26 UTC,I have an update!
1778972,2020-03-02 20:36:04 UTC,The update is view able on the test site. I will wait to push the changes until after I test the carousels
1778972,2020-06-30 04:10:35 UTC,"A small CSS note: there is some CSS that boosts the size of highlighted text in a record.  Unfortunately, if the highlighted text is in the title, it has the opposite effect: the highlighted text is pretty small."
1778972,2020-03-02 21:48:57 UTC,A carousel has been added for perusal
1778972,2020-06-09 17:46:06 UTC,"Given our discussion on Accessibility, I would like to release this ASAP, maybe sometime this week. I still have to make the final GIT push before a pull can be made but it can be looked at on the URL above."
1778972,2020-06-09 17:49:05 UTC,"Also, this isn't an immediate replacement for the OPAC but rather an OPT IN option. The current OPAC would still exist until such time as the community decides to replace the current OPAC with the Responsive/Accessible alternitive here."
1778972,2020-06-26 17:49:37 UTC,"Hey Chris, is there an updated branch available?"
1778972,2020-06-29 15:01:12 UTC,https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=324cc66ad01b971208b1d1e57b49e612cdc68cfc
1778972,2020-06-29 15:02:34 UTC,It may not be perfect but I think it is a huge improvement in readability and usability. As well as having some responsiveness/accessibility enhancements
1778972,2020-06-29 16:07:18 UTC,I've spent the last half hour testing this.  Thoughts in no particular order:
1778972,2020-06-29 16:18:55 UTC,package-lock.json and the node tar file are indeed not relevant; I've taken the liberty of pushing out a collab branch that removes the extraneous files from the base commit:
1778972,2020-06-29 16:35:17 UTC,topnav_cannedsearch.tt2 appears to be specific to NFPL; any reason not to remove it?
1778972,2020-06-29 16:45:58 UTC,"Yeah you can remove topnav_cannedsearch.tt2 for now. I had planned to make that universal but apparently forgot about it.
Was there files I should have put in .gitignore For the lock files?"
1778972,2020-06-29 17:17:39 UTC,"Most Evergreen installs will replace the logo so I'd just make it greyscale (personal opinion).  However, there are quite a few, especially self-hosted minimal resources, that keep the default color scheme and layout so I have no objection to modernizing colors as well.  Just my .02 dinars."
1778972,2020-06-29 17:28:30 UTC,"Color scheme is probably a future patch lol.
The logo just has 0.5 opacity as CSS. That can be changed as well"
1778972,2020-06-29 19:04:52 UTC,"I'd like to propose a few changes to managing the opac-new directory, in the interest of maintainability of the project and simpler upgrade paths for libraries that want to use this OPAC:"
1778972,2020-06-29 20:42:31 UTC,"I agree with Jane's suggestions, and have a couple more:"
1778972,2020-06-29 21:53:59 UTC,"I would love to have a collaborative effort on this.
I'm excited so many people are into it.
It will probably take many iterations for this to be widely accepted. So
any helping hands are welcome."
1778972,2020-03-03 00:32:50 UTC,A piece of feedback from one of our partner libraries:
1778972,2020-06-30 04:55:51 UTC,"Sorry, one more thing!  The browse list is currently center-aligned.  I think it would be more readable if it were left-aligned."
1778972,2020-07-20 22:47:53 UTC,I made another push on this a few days ago with a few updates on the look.
1778973,2019-10-09 15:43:13 UTC,"Hi Florent, I have the same problem, how you solve?"
1778975,2018-06-28 15:56:14 UTC,We may be able to address issues of this sort via the proposed json schema validation - initial patch at https://review.openstack.org/#/c/563429/
1778975,2019-09-12 14:22:00 UTC,This issue was fixed in the openstack/python-cinderclient 5.0.0 release.
1778976,2020-03-28 10:05:45 UTC,"Closing because INVALID: can't replicate in 0.92.4, works as expected."
1778978,2018-06-27 20:40:58 UTC,"This bug is fixed with commit 5c18f903 to jlp-testing on branch master.
To view that commit see the following URL:
https://git.launchpad.net/jlp-testing/commit/?id=5c18f903"
1778978,2018-06-27 20:42:12 UTC,"This bug is fixed with commit d9b7b51f to jlp-testing on branch master.
To view that commit see the following URL:
https://git.launchpad.net/jlp-testing/commit/?id=d9b7b51f"
1778979,2018-06-27 20:42:13 UTC,"This bug is fixed with commit d9b7b51f to jlp-testing on branch master.
To view that commit see the following URL:
https://git.launchpad.net/jlp-testing/commit/?id=d9b7b51f"
1778979,2018-06-27 20:41:00 UTC,"This bug is fixed with commit 5c18f903 to jlp-testing on branch master.
To view that commit see the following URL:
https://git.launchpad.net/jlp-testing/commit/?id=5c18f903"
1778983,2020-09-15 02:15:45 UTC,Those are the same bug but in Compiz. So not really relevant here. This bug is about gnome-shell/mutter.
1778983,2020-09-14 10:09:08 UTC,Probably related: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1001984
1778983,2018-06-29 01:35:46 UTC,Thanks.
1778983,2020-09-14 10:07:35 UTC,Maybe related: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574251 (though that bug is against xorg).
1778983,2018-06-28 01:54:16 UTC,"When done, please let us know the ID of the new bug."
1778983,2018-06-28 01:53:56 UTC,Please report this bug to the Gnome developers here:
1778983,2018-06-28 10:27:42 UTC,Submitted here:
1778984,2019-05-08 18:05:02 UTC,I followed Shawn's hint I my problem was also solved.
1778984,2019-01-16 13:50:29 UTC,"I followed previous hint , but issue still occurs."
1778984,2019-01-16 13:49:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778984,2018-10-19 13:58:25 UTC,"I have just hit this problem on Ubuntu 18.04, and I was able to solve it by running
root@ubuntu:~# sudo dpkg-reconfigure apparmor"
1778984,2018-06-27 21:46:14 UTC,"Hi Serge, can you please attach your /etc/apparmor.d/tunables/home.d/ubuntu file?"
1778984,2018-10-19 14:10:12 UTC,Clarification:
1778986,2018-06-28 11:41:46 UTC,"Same message seen in UniterSuite.TestRunCommand:
http://ci.jujucharms.com/job/github-check-merge-juju/1985/console"
1778988,2021-02-14 16:12:55 UTC,"I tested on my current system and the results show per my previous comment.
Previously, I was unable to determine the version of
CUPS. Following is output of ""dpkg-query -l"" filtered for ""cups"" only:"
1778988,2020-12-17 18:18:36 UTC,Does this issue still affect cups-pdf 3.0.1 packages?
1778988,2020-12-17 21:00:41 UTC,"I have revisited this issue, using UBuntu 20. I cannot figure out how to get the version of CUPS, but the test environment I now have includes:"
1778988,2021-02-14 09:55:24 UTC,Thanks. Let's close it.
1778994,2019-10-30 16:27:27 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/578553
Reason: Unfortunately this is in merge conflict and looks abandoned so I'm going to drop it. It does also look like gmann is handling granular policy as part of blueprint policy-defaults-refresh, see https://review.opendev.org/#/c/648480/."
1778994,2018-06-29 08:22:02 UTC,"Thanks. This is applicable for many other APIs also, let's do this as part of this BP-  https://blueprints.launchpad.net/nova/+spec/granular-api-policy"
1778994,2018-06-27 20:36:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/578553"
1778996,2018-08-27 00:36:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1778998,2019-04-12 00:06:03 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1779003,2018-07-26 19:41:02 UTC,"Sorry for the delay, Hongbin, I was on a vacation for a while."
1779003,2018-07-30 21:35:10 UTC,"As Slawek pointed out in the code review, the proposed fix does cause another problem with the evaluation of the ""update_rbac_policy:target_tenant"" rule. The proposed fix changes Neutron to look at current attribute values instead of attribute values from the API request, but for the ""update_rbac_policy:target_tenant"" rule, the desire is to look at the new value of ""target_tenant"" attribute to determine if its wildcarded or not."
1779003,2018-08-31 07:36:56 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/582659
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1779003,2018-07-13 21:34:55 UTC,I tried to reproduce scenario #1 but I couldn't: http://paste.openstack.org/show/725863/ . Could you provide the reproducing steps (without using Tempest plugin)?
1779003,2018-08-31 07:36:47 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1779003,2018-07-13 19:41:54 UTC,"@Cliff,"
1779003,2018-07-13 18:51:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582659"
1779003,2018-07-13 21:18:58 UTC,"Hello Hongbin,"
1779017,2020-11-05 10:59:29 UTC,"This should be fixed for the 5.2 release, as we now have a model of the cprman clock control module."
1779017,2018-10-10 12:32:26 UTC,"Thanks for the followup. Yes, that sounds like the problem is indeed that we don't currently emulate enough of the clock-control in the raspi's SoC. There were a couple of patches on list a while back that were trying to provide at least a basic dummy emulation of that device; I'm not sure what happened to them."
1779017,2018-10-10 03:33:13 UTC,"This does not appear to be DIRECTLY a bug in QEMU, but 'something' has changed in the RPi Kernel to cause this issue."
1779017,2020-12-10 09:17:53 UTC,Released with QEMU v5.2.0.
1779017,2018-06-28 09:32:08 UTC,"This isn't a kernel crash, it's just a warning (which I think is safely ignorable). The problem is that QEMU doesn't implement the 'cprman' clock control hardware, which means Linux thinks the UART is running at a zero baud rate. Unfortunately the cprman hardware is as far as I can determine undocumented, so it's not really possible to write an emulation of it."
1779017,2018-06-28 10:17:55 UTC,"On Donnerstag, 28. Juni 2018 11:32:08 CEST Peter Maydell wrote:"
1779018,2018-06-28 15:39:15 UTC,"Do you have ""automatically connect to this network when it is available"" marked in your DSL/PPPoE connection settings? If it's enabled, the connection should be established after some time."
1779035,2018-07-23 13:09:46 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1096.101
1779053,2018-06-28 06:01:49 UTC,we should handle this as conflict error inside sdk server
1779057,2018-06-28 12:57:32 UTC,Allowed sort keys(*1) are as follows:
1779057,2018-06-28 12:58:57 UTC,won't fix in novaclient side.
1779057,2018-06-28 13:30:55 UTC,"ok thanks for the explaination, but i am still confused that why we cannot use name as the sorting key because sorting with 'name' looks more relevant. what do you think ?"
1779057,2018-06-29 00:58:34 UTC,"By default (both --fields and --sort are not specified) , the result is sorted by 'Name' (sortby_index = 1, that is 'Name' column) in novaclient side."
1779057,2018-07-03 05:22:58 UTC,"Hi, yes agree with you but according to the documentation [0], by default 'nova list' should result output by the 'Name' (sortby_index = 1) in the descending order but actual output is in ascending order like this:"
1779060,2018-06-29 18:25:41 UTC,"Reviewed:  https://review.opencontrail.org/44228
Committed: http://github.com/Juniper/contrail-controller/commit/93ca28beed2d81b1caf5bce635a5ce5ec35e000b
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1779060,2018-06-29 18:25:46 UTC,"Reviewed:  https://review.opencontrail.org/44229
Committed: http://github.com/Juniper/contrail-test-ci/commit/ddcb2f138fe18fddc93d111911b8c01930ece065
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1779060,2018-06-29 03:01:53 UTC,"Review in progress for https://review.opencontrail.org/44228
Submitter: Jack Jonnalagadda (<email address hidden>)"
1779060,2018-06-28 06:13:54 UTC,"Review in progress for https://review.opencontrail.org/44187
Submitter: Ankit Jain (<email address hidden>)"
1779060,2018-06-28 18:13:49 UTC,"Reviewed:  https://review.opencontrail.org/44187
Committed: http://github.com/Juniper/contrail-test-ci/commit/16b28e1fcbf9f95e8e65872588bf0a46b9c7a045
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1779060,2018-06-29 02:51:45 UTC,"Review in progress for https://review.opencontrail.org/44229
Submitter: Jack Jonnalagadda (<email address hidden>)"
1779064,2018-08-15 10:47:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779064,2018-08-15 10:48:37 UTC,Did reinstalling this package resolve the problem?
1779071,2018-06-29 08:18:28 UTC,Can you provide the main and sub workflow YAML you used to reproduce this? It would be useful to help resolving it.
1779071,2018-06-29 08:37:39 UTC,"Generally it is hard to reproduce in live system, due to it caused by some race condition."
1779071,2018-10-04 08:22:30 UTC,"The reason for the error seems to be if that mistral/engine/workflows.py:345 is simply returning without updating the wf_ex object if the update failed. As the update happened in a different session, the local object is not affected by the change. The later notification therefore fails."
1779072,2019-10-11 02:15:31 UTC,"Hi, sorry, lost track of this one. The good news is that this bug does not seem to occur anymore, although I can't pin point a fix due to some refactoring that has occurred since I logged this."
1779075,2020-03-19 22:11:02 UTC,I didn't saw such timeouts too often in last few months so I will close this bug for now. We can always reopen it if needed.
1779075,2018-09-24 16:43:46 UTC,This bug will be addressed as part of the investigation that will be performed by the new performance imporvement sub-team that was agreed upon during the Denver PTG
1779075,2018-07-10 15:08:59 UTC,Here's another instance:
1779077,2018-07-10 16:13:01 UTC,"In preparation for today's CI meeting, I spent some time looking for instances of this bug this morning. Couldn't find any. Discussed it also during the meeting and nobody has seen it lately"
1779077,2018-07-16 14:27:57 UTC,"I just checked it on logstach with query like:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=(build_name%3A%5C%22openstack-tox-py35%5C%22%20OR%20build_name%3A%5C%22openstack-tox-py27%5C%22)%20AND%20message%3A%5C%22RUN%20END%20RESULT_TIMED_OUT%5C%22%20AND%20project%3A%5C%22openstack%2Fneutron%5C%22"
1779077,2018-07-17 07:29:11 UTC,"From short analysis it looks for me that some tests are running much longer in failed runs then in ""good"" runs. I will need to compare all of results to be sure that this slowdown could cause such issue."
1779077,2020-03-19 21:57:18 UTC,"As we don't have py35 job anymore, I will close this bug as won't fix."
1779084,2020-03-30 20:37:07 UTC,"Closing because INVALID: issue reported at
https://gitlab.com/inkscape/inbox/-/issues/951 ."
1779095,2018-06-28 10:40:50 UTC,Ich bin bis 10.07. nicht im Haus und kann Ihre Nachricht daher nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
1779096,2018-06-29 08:14:34 UTC,It differs (I think) in that the wifi networks and default keyboard settings are system settings not stored in your personal account. Mouse speed is not a system setting and is stored in your personal account.
1779096,2018-06-29 08:01:08 UTC,Issue submitted here:
1779096,2018-06-29 07:57:24 UTC,How is this different from Wifi and keyboard settings that I'm already setting system wide? And how does this compromise the security of the system? The gdm user doesn't need to be able to change my settings. All it needs is to be able to read some settings to use them instead of the defaults if I'm the only user. I'll open a bug.
1779096,2018-06-29 07:21:16 UTC,I don't agree this is an invalid bug. It may be hard to fix but it's still a bug. Editing xml files to get a reasonable user experience is not a polished desktop. There are already settings (like wifi) that apply system-wide so there's no reason for mouse and screen settings to not be the same.
1779096,2018-06-29 07:41:05 UTC,It is impossible to fix without compromising the security of the system. Other user accounts should not have access to your personal settings before you have given them your password.
1779096,2018-06-29 01:42:26 UTC,This is unfortunately correct.
1779096,2018-06-29 07:43:16 UTC,I suggest the way forward is for you to ask the Gnome developers for a future solution by reporting an issue here:
1779120,2021-01-12 04:17:28 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1779120,2020-11-12 14:15:42 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1779120,2018-06-28 13:10:42 UTC,I also met this bug
1779120,2018-06-28 14:00:42 UTC,"Hi, Stefan.
(host)# rpm -qa | grep qemu-kvm
qemu-kvm-2.8.1-25.142.x86_64
(guest)# uname -r
3.10.0-514.el7.x86_64"
1779120,2018-06-28 13:01:13 UTC,"Please post the following information:
(host)# rpm -qa | grep qemu-kvm
(guest)# uname -r"
1779121,2019-10-01 12:58:50 UTC,have you found a workaround for this? I'm having the same issue with T450s and EM7345
1779156,2019-10-23 13:57:53 UTC,best. fix. ever.
1779156,2019-10-23 08:48:43 UTC,The current stable snap seems to fully address the issue. See:
1779156,2019-10-16 10:32:45 UTC,The released fix does not appear to fully address the problem:
1779156,2019-10-14 20:34:15 UTC,"A fix has landed in lxd, I refer you to the following comment:"
1779156,2019-09-26 14:45:22 UTC,See: https://github.com/lxc/lxd/issues/4656#issuecomment-535531229
1779156,2019-09-24 14:48:36 UTC,Been digging into this a bit further with lxc 3.17 on Eoan.
1779156,2019-09-03 16:13:06 UTC,The ZFS destroy checks the reference count on the dataset with zfs_refcount_count(&ds->ds_longholds) != expected_holds and returns EBUSY in dsl_destroy_head_check_impl.
1779156,2019-08-30 16:52:56 UTC,Reproducer is as follows:
1779156,2019-10-23 14:21:41 UTC,Bug status updated accordingly. I set the linux task to Invalid as the kernel was not involved after all. Thanks again Stéphane and Colin!
1779156,2019-08-30 07:21:13 UTC,Do we have any hunches on how to reproduce this issue?
1779156,2019-08-30 06:54:26 UTC,Cosmic is now end-of-life. Does this still occur on Disco?
1779156,2019-02-21 08:15:35 UTC,https://github.com/lxc/lxd/issues/4656
1779156,2019-02-06 02:46:51 UTC,This is still around.  Scott wrote up a script to handle cleaning this up.
1779156,2019-02-06 02:46:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779156,2018-06-28 15:00:07 UTC,This change was made by a bot.
1779156,2019-08-30 14:01:49 UTC,To be clear: point(3) above is what I see happening most of the time at the moment.
1779156,2019-08-30 13:07:32 UTC,"Hi,"
1779160,2018-10-24 16:36:10 UTC,This issue was fixed in the openstack/python-magnumclient 2.11.0 release.
1779160,2018-09-12 15:45:16 UTC,"Change has been merged a month ago, but something seems to be wrong with the automatic bug triaging: https://review.openstack.org/#/c/578843/"
1779161,2018-07-11 10:21:02 UTC,"@Cory: first time I installed it, I checked many of the features at the beginning, i.e helm, etc... and that's why I ended with a lot of VMs. Next time I installed a very minimal version with no addons (probably this is what you saw)"
1779161,2018-07-09 21:12:30 UTC,"I'm still not really clear how you ended up with so many VMs, but the only ways I can think of are that multiple (11+) attempts were made to deploy CDK with it not being clear, if something failed, whether resources were being consumed, or hitting some strange bug in the Juju <-> MAAS pod interaction."
1779161,2018-07-09 21:06:54 UTC,"We discussed this on IRC, but posting it here for reference and adding a bit more detail."
1779161,2018-06-28 16:15:50 UTC,Adding my context from discussions on IRC:
1779161,2018-07-02 14:51:03 UTC,In checking into this the current KVM pod work from MAAS is in beta phase and there's ongoing efforts to flesh it out including finishing networking support and things needed for Juju to properly build on top of. For now marking this wishlist as we definitely want this to work but need to coordinate with the feature progression in MAAS and it's not ready for this type of production kubernetes use.
1779161,2018-06-28 16:17:13 UTC,"Adam Stokes pointed to https://docs.jujucharms.com/2.3/en/reference-constraints for more details on how the tag constraints can be specified, though it still doesn't clarify how multiple units would be handled."
1779161,2018-07-07 08:17:40 UTC,"@Cory: Sorry for the delay in responding here. I have checked the constraints, I don't see in the documentation anything in regards to the naming of the VMs."
1779163,2020-02-14 15:23:56 UTC,"I'm running into the same issue, using the Juju openstack provider (Juju 2.7.2 on bionic)
* juju client perspective: https://pastebin.ubuntu.com/p/pJgZfwHr74/
* machine-0.log from controller: https://pastebin.ubuntu.com/p/2Jpcr3JmHg/"
1779163,2020-02-14 15:58:09 UTC,"BTW, I ran several tcpdumps and didn't find any trace of the ""juju ssh"" connections. The only tcp/22 data sniffed was the ssh conn to run tcpdump command itself. I only saw traffic to ws:// on tcp/17070 and traffic from the agents toward the controller."
1779163,2020-02-18 15:43:53 UTC,"Hmmm, I think the issue we'll find here is that the model has a fan network setup but the controller itself isn't participating in it. You might need to see the controller with the same fan config as the model when you bootstrap and set model config so that there's a known route from the controller you're ssh'ing through (with the --proxy) to the lxd container that you're trying to reach in another model. By default there's not a known route from the controller to each lxd instance."
1779163,2020-02-18 16:10:39 UTC,"Hi Rick. This is a Juju openstack environment and the controller has a floating IP. Other than that, the underlay and overlay networks match per the info below:"
1779163,2020-05-06 16:40:17 UTC,"Any ETA on when this issue could be addressed?
* client1: runs juju commands
* controller1: runs in an openstack environment
* default-node1: runs in the default model, in the same openstack environment"
1779171,2019-05-28 17:16:01 UTC,"I have been discussing this bug with a colleague and we've seen that the condition mentioned by Liam is now ""config('stats_cron_schedule').
https://github.com/openstack/charm-rabbitmq-server/blob/master/hooks/rabbitmq_server_relations.py#L651"
1779171,2018-07-26 13:49:27 UTC,"I set management_plugin=True, in order to workaround this issue."
1779171,2018-06-29 08:49:23 UTC,"Err, I mean the placing of the ""if config('management_plugin'):"" block was a mistake not the whole change."
1779171,2018-06-28 17:09:15 UTC,This issue only exists for at most 5 minutes immediately after the nrpe relation is formed. A conjob is setup ( /etc/cron.d/rabbitmq-stats ) which in turn calls /usr/local/bin/collect_rabbitmq_stats.sh . collect_rabbitmq_stats.sh creates the directories and sets their permissions.
1779171,2018-06-29 08:11:16 UTC,Can you attach the /var/log/juju/unit* logs from the affected unit please?
1779171,2018-06-29 07:43:58 UTC,"In this specific case, the problem seems to be permanent, because the /etc/cron.d/rabbitmq-stats file is simply missing from the filesystem:"
1779171,2018-06-29 08:48:10 UTC,From an initial look this appears to be caused by this bit of code:
1779173,2018-12-01 18:43:48 UTC,"Thanks.  So I went ahead and created an environment to build some affected
modules out of tree (also includes a dkms package):"
1779173,2018-12-08 16:34:35 UTC,"As it's rather hard to correctly respond to your mails from web archives I'm simply going to respond
here."
1779173,2020-11-01 12:32:17 UTC,Good news everyone - this has been fixed in kernel 5.9-rc1:
1779173,2018-12-01 15:02:43 UTC,Just use the ones attached to this bug report. They should work fine.
1779173,2020-01-16 15:11:40 UTC,"The patches seem to fail on kernel 5.4. This is running on Debian with 5.4.0-2 packaged kernel, and using Stefan's DKMS package:"
1779173,2018-12-01 11:03:57 UTC,"I think I've hit the same bug (Debian testing 4.18.0-2-amd64, with an i-tec
docking station: https://i-tec.cz/en/produkt/cadua4kdockpdl-2/, but
same driver and problems: IPv6 RA and IPv4+IPv6 mdns not working)."
1779173,2019-03-07 06:37:56 UTC,Seems like these patches are not in upstream yet.
1779173,2018-06-29 13:52:02 UTC,"Thank you for providing a patch, and making Ubuntu better."
1779173,2018-06-28 16:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1779173,2018-06-28 17:03:57 UTC,"Created attachment 276977
[PATCH 1/2] Hook into usbnet_change_mtu respecting usbnet driver_info"
1779173,2018-07-11 08:42:07 UTC,"Well, the patch, and an updated version has been submitted to the linux-usb list, but sadly most it is not getting much attention. This is the link to the most recent discussion on each patch: https://www.spinics.net/lists/linux-usb/msg170611.html, https://www.spinics.net/lists/linux-usb/msg170603.html, https://www.spinics.net/lists/linux-usb/msg170567.html and https://www.spinics.net/lists/linux-usb/msg170568.html.
I don't know how should I proceed at this point."
1779173,2018-06-28 17:05:07 UTC,"Created attachment 276979
[PATCH 2/2] Admit multicast traffic"
1779173,2018-06-28 19:28:58 UTC,"On Thu, Jun 28, 2018 at 05:03:57PM +0000, <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=200331
>
>             Bug ID: 200331
>            Summary: CDC NCM driver does not process multicast Ethernet
>                     traffic
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 4.15
"
1779175,2018-07-01 22:22:46 UTC,"At the very least, we should lead the user as to what they need to do somehow."
1779175,2018-07-19 09:48:48 UTC,"I faced the same issue when deployed canonical kubernetes bundle.
Completely puzzled what i need to do... :("
1779175,2018-07-19 10:00:02 UTC,"I am also running into this. Would like to know how to solve/debug it, but I can't find any documentation."
1779175,2018-08-23 15:24:44 UTC,"+1, have run into this today http://paste.ubuntu.com/p/y9wrBqvYGt/"
1779175,2018-08-28 21:55:24 UTC,Meter status is only meaningful when an SLA is set. Otherwise it is not meaningful.
1779178,2018-06-29 21:10:01 UTC,"https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/348672 is another example. Launchpad is showing a diff over a million lines long, when in fact it's much smaller:"
1779180,2019-12-16 04:17:21 UTC,[Expired for snapd because there has been no activity for 60 days.]
1779180,2019-12-16 04:17:22 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1779180,2019-10-16 06:08:07 UTC,"We fixed a bunch of the postinst issues in later versions of snapd, please let us  know if you still have this issue."
1779185,2018-06-29 14:37:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1779185,2018-06-29 15:04:05 UTC,You are asking me to report a problem with a PC that is not the same as I use for my email.  How should I handle?
1779185,2018-07-02 20:12:59 UTC,Have you tried this workaround described in bug https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1741977 message #4? Are you using USB3 socket? Does it work on USB2?
1779185,2018-07-02 22:29:41 UTC,"I have given up fighting scanning on PCs using 18.04.  It is easier to reboot the PC to windows, do the scanning from windows and use Ext2 volume manager to send the files back to the drives used by Ubuntu.  Devices and software (PDF Studio Pro) that worked very well under 16.04 don't work under 18.04.  My main reason for going to 18.04 was to get rid of a version of evolution that had problems ans was no longer support.  My consulting business runs on evolution (primarily for e-mail)."
1779185,2018-07-03 07:19:13 UTC,"> I should not have to worry if a PC has USB2 or a combination of USB2 and USB3
"
1779185,2019-07-04 16:11:07 UTC,Issue about to be fixed in 18.04
1779190,2018-06-29 12:58:19 UTC,Hola!
1779190,2018-06-29 13:05:04 UTC,"Ok, so for this to be fixable I need go 1.7 which is not what we're running (as it wasn't in 16.04)."
1779190,2018-06-29 13:07:19 UTC,"For reference, the upstream bug and fix is https://github.com/golang/go/issues/13290"
1779190,2018-06-29 13:38:43 UTC,"ok, thanks John."
1779191,2018-07-26 18:01:29 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.0.0.0b4 development milestone.
1779191,2018-08-08 04:30:39 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.5 release.
1779197,2018-07-10 22:21:15 UTC,"UPDATED: In latest 2.2.0-alpha-pre, the IDDJ's lights now stay OFF all the time, instead of being constantly lit. Should I update the title of this report, file a new report or leave this report as-is?"
1779197,2018-07-18 23:24:21 UTC,Title updated.
1779197,2018-07-19 00:05:35 UTC,Is there any backtrace or log or something that I could submit that might help diagnose this? It's really cramping my mixing to not have any status lights functioning on my controller.
1779199,2018-06-29 13:46:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1779199,2018-06-29 19:17:03 UTC,"The fixing commit 0f90603c33bdf6575cfdc81edd53f3f13ba166fb
is included into 4.16.4 according to"
1779199,2018-06-29 19:04:32 UTC,I have tested with latest 4.17.3-generic (since do not like to boot the box with rc). I cannot reproduce the bug with 4.17.
1779199,2018-06-28 20:47:45 UTC,apport information
1779199,2018-06-28 19:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1779199,2018-06-28 20:47:46 UTC,apport information
1779207,2018-07-06 18:22:36 UTC,ran cloud-init collect-logs...attaching
1779207,2018-07-10 14:30:16 UTC,"Daniel,
I think this is likely a duplicate of bug 1691489."
1779207,2018-07-12 15:32:24 UTC,"Hi Scott,
As you called out in 1691489, I can only repro this behavior when using a swap file cloud-init config."
1779207,2018-08-24 20:06:27 UTC,"Hi Scott, as discussed at the summit, i changed the fsck property in fstab to switch off fsck for the ephemeral disk :"
1779210,2018-06-28 22:15:28 UTC,"On Thu, Jun 28, 2018 at 4:55 PM Dan Wells <email address hidden> wrote:
<snip>"
1779216,2018-07-13 04:51:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779218,2018-06-28 22:39:21 UTC,https://review.openstack.org/#/c/579025/ should address it.
1779218,2018-07-03 13:48:57 UTC,This issue was fixed in the openstack/cliff 2.13.0 release.
1779222,2018-09-05 16:34:42 UTC,"Record In-House Use does not acknowledge when an item is in the Missing status either. It would be nice if it simply corrected the status to Available, but an alert would also be an improvement."
1779222,2018-06-29 15:53:32 UTC,We have a partially working solution to this.  We'll try to get it finished soon.
1779223,2018-07-30 17:38:09 UTC,"Yes, that is the correct PPA, though I don't know that the PPA is related.  Please do let me know if it is and we'll remedy the PPA."
1779223,2018-09-24 18:55:05 UTC,"Drew, can you confirm these are the correct steps to reproduce?"
1779223,2018-06-29 12:50:39 UTC,"Hi Drew,"
1779223,2019-03-20 15:47:28 UTC,I marked the bug as incomplete since we are waiting further details to make progress.
1779223,2019-05-20 04:17:25 UTC,[Expired for Ubuntu Cloud Archive because there has been no activity for 60 days.]
1779224,2020-02-19 14:05:38 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1779224,2018-06-29 02:36:02 UTC,"Reproduced by entering info in the object title.  Win 8.1 64, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1779227,2018-06-28 23:32:42 UTC,This looks like a regression of the gnome-initial-setup SRU to bionic.
1779227,2018-06-28 23:51:57 UTC,I looked at this the other day but haven't yet worked out what is causing it.
1779229,2020-01-25 12:34:33 UTC,"I'm unable to replicate this issue in Inkscape 1.1-dev (2a5d477, 2020-01-18), Windows 10. Please reopen on http://inkscape.org/report if the problem occurs again."
1779229,2018-07-07 16:04:20 UTC,"I've also had this problem since 0.92.1, on Windows 10 Pro 64 bits."
1779232,2019-09-12 13:55:37 UTC,Does this bug still occur? If yes - please send new logs using latest kolla-ansible code.
1779232,2019-11-12 04:17:59 UTC,[Expired for kolla because there has been no activity for 60 days.]
1779245,2018-07-10 23:27:01 UTC,Using the icons to show the counts would be good.
1779245,2018-07-11 22:24:21 UTC,"Hi Robert,
Thanks for your positive feedback, I believe that use case would work yes.
Actually it was only when I had collapsed the standards that the idea
occurred.
Cheers
Shane"
1779248,2018-06-29 07:46:44 UTC,I think those icons are probably defined in the gtk2 theme you are using
1779248,2020-03-28 14:48:07 UTC,"Closing because INVALID: can't replicate. As suggested, problem lies with theme and not Inkscape."
1779254,2018-08-31 07:30:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779260,2018-06-29 05:57:01 UTC,"Test-Bug-Report
Assinged to me"
1779280,2018-07-04 11:58:50 UTC,"Hi,"
1779280,2018-07-04 13:19:57 UTC,"Hi Valentin,"
1779280,2018-07-06 16:04:44 UTC,"Hi Valentin,"
1779280,2018-07-10 11:07:02 UTC,"Dear Valentin and Olivier,"
1779280,2018-07-11 18:37:40 UTC,"Hi,"
1779280,2018-07-11 21:23:02 UTC,"thanks Olivier!
=========================="
1779280,2018-08-07 12:56:29 UTC,"Hi Olivier,
I just got back form vacation and was very excited to install your patch, but sadly it still doesn't work.  Instead now I get a segmentation fault and core dump from run_PY8.sh.  I'm attaching the debug log to this email.  Please can you help?
Cheers,
Rakhi"
1779280,2018-08-07 13:14:02 UTC,"Hi,"
1779280,2018-07-04 11:28:33 UTC,"Hi!  Sorry to be a pain, but I'm really stuck here.  If there is no workaround, is there an older version without py8 parallelization that I could revert to?  Thanks so much, Rakhi"
1779280,2018-06-29 12:27:07 UTC,"Hi Olivier and Valentin,"
1779280,2018-08-07 14:43:44 UTC,"Hi Olivier,"
1779287,2018-07-04 17:08:11 UTC,This was fixed by raising the lower constraint: https://review.openstack.org/#/c/579110/
1779289,2019-05-16 10:10:19 UTC,This bug was fixed in the package gnome-bluetooth - 3.28.0-2ubuntu0.2
1779289,2019-05-16 10:00:15 UTC,"The verification of the Stable Release Update for gnome-bluetooth has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1779289,2019-05-14 09:51:30 UTC,"Sorry, I forgot to add the package version to my previous comment (is there no way to edit a comment?): I've tested with gnome-bluetooth 3.28.0-2ubuntu0.2 from bionic-proposed."
1779289,2019-05-06 14:56:36 UTC,"Cosmic is neither a lTS nor the current stable, doesn't seem worth spending energy on it at this point"
1779289,2019-05-06 14:42:47 UTC,Accepted. Does it make sense to get this fix into cosmic as well?
1779289,2018-07-02 02:31:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779289,2019-05-03 20:26:34 UTC,BTLE persition mouse. There were problems with pair and repeated connection.( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413 ) All decided this way: https://gist.github.com/Mygod/f390aabf53cf1406fc71166a47236ebf
1779289,2019-04-12 13:33:07 UTC,We believe that should be fixed by those commits
1779289,2019-03-25 06:49:13 UTC,Its look like the issue is on usage the connect/pair command.
1779289,2019-03-25 06:11:32 UTC,Thanks.
1779289,2019-03-18 02:37:39 UTC,Thanks.
1779289,2019-03-15 18:15:40 UTC,Bug affected also a disco dingo
1779289,2019-05-06 14:42:03 UTC,"Hello dudsen, or anyone else affected,"
1779289,2019-05-14 09:43:56 UTC,"Hello,"
1779304,2018-07-18 20:51:49 UTC,"Hi Nahian,"
1779304,2018-07-09 13:39:54 UTC,"Hi Shakhat,"
1779304,2018-07-09 08:02:35 UTC,"About the shaker_frktis_agent_2,3,4, I checked in netstat output, I can see their IP address.
So I assumed they were not lost."
1779304,2018-07-05 15:59:24 UTC,"> Means that shaker_frktis_agent_2,3,4 was not lost,
"
1779304,2018-07-05 13:36:44 UTC,**sorry missed the important line
1779304,2018-07-05 13:16:03 UTC,when I ran the following command in the command line manually (found in the instance_metadata.yaml)
1779304,2018-07-05 13:35:27 UTC,"I checked the LOG from the instance from horizon,"
1779304,2018-07-05 11:25:51 UTC,Networking looks good (since telnet is able to connect from VM to shaker server).
1779304,2018-07-05 10:53:27 UTC,"root@kolla-deploy:~# netstat -tapnl | grep 1337
tcp        0      0 0.0.0.0:1337            0.0.0.0:*               LISTEN      17812/python2
tcp        0      0 192.168.1.10:1337       192.168.1.10:55534      TIME_WAIT   -
tcp        0      0 192.168.1.10:55518      192.168.1.10:1337       ESTABLISHED 17818/python2
tcp        0      0 192.168.1.10:1337       192.168.1.10:55518      ESTABLISHED 17812/python2"
1779304,2018-07-05 08:45:24 UTC,My deploy host has 192.168.1.10 on the interface eth1
1779304,2018-07-05 07:48:03 UTC,"Steps 1 & 2 are done.
On 3,
telnet 192.168.1.10 1337
Trying 192.168.1.10...
Connected to 192.168.1.10.
Escape character is '^]'.
Connection closed by foreign host."
1779304,2018-06-29 15:47:21 UTC,"Could you please check the following:
 1. Start shaker with parameter --agent-join-timeout set to large value (e.g. 3600 = 1 hour)
 2. While shaker is running create a VM inside a network created by shaker (Cirros VM would be enough)
 3. Do telnet to the address:port of shaker.
 4. If 3 is succeed, then boot VM from shaker image (a key will be required to access it)
 5. Login into VM and check that shaker-agent is installed.
 6. If 5 is yes, start shaker-agent manually and check whether it was able to connect to shaker."
1779304,2018-07-05 12:57:51 UTC,"Interesting point, I ran 10 instance single node scenario = ""instance_metadata.yaml""."
1779305,2018-06-30 17:12:36 UTC,"Correction: The above commit was included in v4.17, not v4.16."
1779305,2018-06-29 12:20:15 UTC,Note that this dmesg is taken under my custom 4.15.0-23-lowlatency kernel with the offending patch reverted.
1779305,2018-06-29 16:00:07 UTC,This change was made by a bot.
1779305,2018-06-30 16:54:51 UTC,"I tested the upstream v4.18-rc2 kernel, and found the problem has been fixed."
1779305,2018-06-30 17:33:58 UTC,"For future reference purposes, here are some dmesg logs between v4.16.18 (bug not fixed) and v4.17.3 (bug fixed)"
1779307,2018-07-02 04:58:13 UTC,"Hi Luke,"
1779310,2019-10-17 05:13:17 UTC,"Hi, One of customer's alerts is blocked by this bug, is there any update, please?"
1779310,2020-05-13 20:37:55 UTC,"This bug was lacking the proper subscriptions and has been long standing, so I've added field-high and canonical-boostack-cres."
1779310,2020-06-26 11:14:06 UTC,Relations with this service are:
1779310,2020-06-30 13:48:29 UTC,"zaza-openstack lib needs to be updated to support ""enabled-services"" option. Proposed PR can be found at [1]."
1779310,2020-06-30 14:52:01 UTC,Fix manually tested together with nagios and nrpe. See attachment.
1779310,2020-06-30 15:43:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/738651"
1779310,2020-07-02 15:39:24 UTC,"Reviewed:  https://review.opendev.org/738651
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=71f968faf1f5d8e9a307e7f1d391a699875ed5c1
Submitter: Zuul
Branch:    master"
1779313,2019-02-01 12:21:54 UTC,It seems you are using the generic NFS driver in a ONTAP share right? Can you post your cinder.conf file? And if possible a full stack trace?
1779313,2019-04-10 06:43:29 UTC,"Hello.. As Erlon asked before, can you share your cinder.conf and the full stack trace when this error was seen?"
1779314,2018-06-29 12:59:02 UTC,First failure:
1779314,2018-06-29 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1779314,2018-06-29 13:00:33 UTC,Second failure:
1779314,2018-07-18 05:54:53 UTC,"The CONFIG_CC_STACKPROTECTOR issue was addressed in bug 1776242, leaving the apparmor test failure to resolve."
1779314,2018-07-18 06:46:34 UTC,"For the apparmor failure, this is caused by /usr/bin/python being a symlink to python2, which is in turn a symlink to python2.7, which caught the tests unprepared to handle nested symlinks like that. A fix has been proposed at https://gitlab.com/apparmor/apparmor/merge_requests/147 and committed to the qa-regression-testing tree in https://git.launchpad.net/qa-regression-testing/commit/?id=30c513e222cadc8abe24463cefadce53bf0e277a ."
1779316,2019-09-04 19:36:35 UTC,We're running 3.2.8 and the holds pull list grid has the following columns for call numbers:
1779316,2018-06-29 17:49:45 UTC,"I was thinking the same thing. I just assumed Call Number Label existed for just that reason; so, if you wanted to sort by Prefix / Call Number (all in one) you could while Call Number would be just the call number itself."
1779316,2018-06-29 16:53:18 UTC,"It looks like we still have both a Call Number and Call Number Label in this grid. Maybe one - Call Number - could be repurposed to only show the call number and the other - Call Number Label - could include prefix & suffix. We would also need to ensure that both are sorting by call number sortkey. I haven't tested it recently, but, at one time, I think only one was sorting by sortkey."
1779316,2018-06-29 14:16:34 UTC,"Hi Kathy,
    Thank you for passing along Bill's comment. Since, in some of our libraries, the Prefix denotes an area within a Shelving Location, here is a common workflow:"
1779316,2018-06-29 13:28:45 UTC,"Hi Scott,"
1779318,2020-01-23 04:45:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/703913"
1779318,2020-01-23 06:39:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/703920"
1779318,2020-01-23 10:24:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/703959"
1779318,2020-01-23 14:24:43 UTC,"Reviewed:  https://review.opendev.org/703913
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=5c05636ee45bc79d99a7a90d972035f819619d0a
Submitter: Zuul
Branch:    master"
1779318,2020-01-23 14:24:51 UTC,"Reviewed:  https://review.opendev.org/703920
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=12b2eceb358481d5f63e4c19d5961d1f8373e75a
Submitter: Zuul
Branch:    master"
1779318,2020-01-23 14:24:58 UTC,"Reviewed:  https://review.opendev.org/703959
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=9dfdd20541cbe3e862428eacea6c4d552ea4120c
Submitter: Zuul
Branch:    master"
1779318,2020-01-24 05:03:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/704100"
1779318,2020-01-27 09:44:19 UTC,"Reviewed:  https://review.opendev.org/704100
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=6928615fde51520faf45b89d068b9ba7db99352d
Submitter: Zuul
Branch:    master"
1779318,2020-03-02 14:51:37 UTC,This issue was fixed in the openstack/mistral 10.0.0.0b2 development milestone.
1779319,2019-09-06 17:24:07 UTC,"If you mean should the system supply the parentheses I'd say no. The LOC documentation apparently doesn't use parentheses but I'd say 99% of OCLC records we import already have the text in subfield q in parentheses. If the system added them they would be doubled, much like the commas that separate the relator terms if a person is both author and illustrator.
In the MARC record each subfield e is separated by a comma and the field ends with a period both of which Evergreen supplies so that:
Carle, Eric, $e author, $e illustrator.
becomes:
Carle, Eric, (author,,illustrator.).
with two commas and two periods."
1779319,2019-09-06 16:46:09 UTC,+1 to including the qualifier in parenthesis.
1779319,2019-09-06 16:14:01 UTC,"As of bug 1744385, the OPAC templates do use display attributes for the ISBN, so the question of adding a definition that includes the subfield $q in the display entry is more significant."
1779319,2019-08-01 14:48:43 UTC,"works for me, sign off at user/rogan/lp1779319_signoff"
1779319,2019-07-15 20:16:44 UTC,This has been on the SCLENDS cataloging workgroup's wishlist for quite awhile. We do add qualifiers and would like them to display.
1779319,2019-02-20 17:47:29 UTC,"I think as currently written this will result in the contents of $q being expressed as part of the schema:isbn RDFa, which would be an unfortunate side-effect."
1779319,2018-10-24 23:29:26 UTC,Moved the target milestone to 3.next as this seems new featurish to me.
1779319,2018-08-23 17:37:27 UTC,I rebased the branch on current master and added a commit with some very simple release notes. I force pushed over the prior branch.
1779319,2018-06-29 15:34:58 UTC,"Mike, you are correct. I typed this over again rather than copy and paste from the custom misc_util.tt2. I'll fix that and force push."
1779319,2018-06-29 14:46:25 UTC,"Jason, looking at the code, shouldn't the expression in the inner FOR loop be ""isbn.findnodes('../*[@code=""q""]')"" rather than ""xml.findnodes('../*[@code=""q""]')""?"
1779319,2019-07-01 17:40:19 UTC,"In response to Dan Scott's comment # 5, perhaps it should be restructured, but I'd like to point out that many (most?) ISBNs have the qualifier that is now in subfield q tacked on to subfield a.  It's one of the things that made parsing ISBN data from MARC a bit tricky in the past."
1779325,2019-12-09 05:56:15 UTC,I was facing the same error:
1779325,2021-02-18 15:28:17 UTC,"Since subunit is supposed to represent my test results, it's a bit annoying that this arbitrary length limitation is imposed.  If my tests produce output larger than this limit, I think that should be my business and subunit shouldn't get in the way."
1779328,2018-09-18 00:31:25 UTC,"Reviewed:  https://review.openstack.org/603073
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0cf75ecb57c1d7583c8e55a7b127be247188646d
Submitter: Zuul
Branch:    stable/rocky"
1779328,2020-03-21 08:49:31 UTC,"Reviewed:  https://review.opendev.org/710964
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8456240e7da79f0409259597d796b7d6cab3298d
Submitter: Zuul
Branch:    master"
1779328,2020-03-03 10:30:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/710964"
1779328,2020-03-02 14:24:42 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/710782"
1779328,2018-09-17 10:43:11 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/603073"
1779328,2020-03-26 00:51:21 UTC,"Reviewed:  https://review.opendev.org/710782
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7f925249a598aba88ecd58bb4759fc1767954e5
Submitter: Zuul
Branch:    master"
1779328,2018-08-29 08:36:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/597426"
1779328,2018-08-20 14:03:58 UTC,"Reviewed:  https://review.openstack.org/591645
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0bd1cec6768c9748cb415261fd8e4d4da0ee7ddb
Submitter: Zuul
Branch:    master"
1779328,2018-08-14 12:24:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/591645"
1779328,2018-08-08 08:18:27 UTC,Recently it found it failing sometimes again. It's always same failure:
1779328,2018-09-01 00:38:00 UTC,"Reviewed:  https://review.openstack.org/597426
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f9dc83eb9576ca01d732bf6a3ff3b3e9d01647e7
Submitter: Zuul
Branch:    master"
1779335,2018-07-24 07:10:10 UTC,"Reviewed:  https://review.openstack.org/579166
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=bb165298e0270ab3cdc0bd0afab4b51988db4d98
Submitter: Zuul
Branch:    master"
1779335,2018-06-29 14:07:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/579166"
1779335,2018-06-29 14:11:29 UTC,"I don't plan to fix all this defect, but submitted some of the work under https://review.openstack.org/579166"
1779336,2018-08-03 16:41:51 UTC,"Reproducer:
bootstrap Juju to manually provisioned machine
juju switch controller
juju deploy ubuntu
juju status"
1779336,2018-08-14 13:20:32 UTC,"Interesting, this doesn't reproduce with add-unit:"
1779336,2018-08-14 16:50:08 UTC,"@dparrish and @dmittris, I am unable to reproduce with 2.4.1 (stable snap) nor 2.4.2+2.4-f7ab37f (candidate snap).  Is there any additional information you can provide?"
1779336,2018-08-14 18:55:44 UTC,"@hmlanigan & @dmittris,"
1779336,2018-08-14 19:25:57 UTC,"Incidentally, juju add-unit has more desirable behavior:"
1779336,2018-08-17 13:36:26 UTC,@dparrish agreed that we should be able to wire into deploy checks that we do in add-unit. We've found a few places that we do a better job during add-unit than we do in deploy and we'll have to look into a nice global fix for these types of late-finding error paths.
1779336,2018-08-29 05:31:20 UTC,"Is this still considered to be ""incomplete""?"
1779336,2018-08-29 11:43:40 UTC,Thanks for the ping to update the bug for the larger issue @dmitriis. I've updated and triaged it.
1779336,2019-05-07 02:53:02 UTC,I do feel like an error on deploy is a separate report. I am moving it to bug # 1827969.
1779340,2018-12-24 21:43:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779340,2018-12-24 21:59:29 UTC,"My setup is a little bit different, but the problem is the same. I have a bridge device for LXD. This is an extra bridge for testing purpose."
1779341,2020-09-25 08:41:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779341,2020-09-25 08:47:43 UTC,"For me the proposed workaround doesn't work.
On openvpn stop I get:
sep 25 11:21:51 lieta networkd-dispatcher[140803]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('AdministrativeState'): dbus.String('linger', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_314')
sep 25 11:21:51 lieta networkd-dispatcher[140803]: DEBUG:Path '/etc/networkd-dispatcher/linger.d' does not exist; skipping
sep 25 11:21:51 lieta networkd-dispatcher[140803]: DEBUG:Path '/usr/lib/networkd-dispatcher/linger.d' does not exist; skipping
sep 25 11:21:51 lieta networkd-dispatcher[140803]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=14, name='tap0', type='ether', operational='off', administrative='linger') entering state 'linger': no triggers"
1779342,2018-06-29 14:59:24 UTC,This has been fixed as part of https://review.openstack.org/#/c/559685/ on master branch.
1779342,2018-06-29 14:36:35 UTC,Hum... looks like 1.1.1.1 was already removed from the test suite. Should we re-introduce 198.51.100.1 in the test decoration?
1779352,2018-07-02 02:20:51 UTC,Please also run 'apport-collect 1779352' to provide us more information about the system.
1779352,2018-07-02 07:48:21 UTC,apport information
1779352,2018-07-02 07:48:23 UTC,apport information
1779352,2018-07-02 07:48:24 UTC,apport information
1779352,2018-07-02 07:48:25 UTC,apport information
1779352,2019-01-11 14:14:59 UTC,The issue seems rather what xdotool is doing that nautilus
1779365,2018-06-29 15:17:52 UTC," 02:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ [8086:1583] (rev 02)
driver: i40e
version: 2.2.4
firmware-version: 6.01 0x800034a4 1.1747.0
bus-info: 0000:02:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes"
1779365,2018-07-09 10:48:06 UTC,We wait for confirmation from fields that 2.4.6 is working as expected. Until this I'm moving it to Incomplete.
1779365,2018-07-30 08:35:03 UTC,Moving to 9.2-mu-8 since there are no evidence that the issue is in the driver and not in NICs themselves. Also I'm decreasing the importance.
1779385,2018-07-03 13:30:41 UTC,This happens with Content Cafe as well. It seems at some point the image for that cover was saved as a 1x1px image with a defined location as such:
1779386,2018-06-29 15:42:17 UTC,Attach file lp-attach.
1779386,2018-06-29 16:55:33 UTC,Attach file py2art.tar.xz.
1779386,2018-06-29 16:56:03 UTC,Attach file py3art.tar.xz.
1779392,2019-11-21 20:55:59 UTC,Marking at Fix Released since the commit is in all current release branches as well as master.
1779392,2018-07-06 16:51:44 UTC,This looks good to me.  Picked to master and 3.1.
1779392,2018-06-29 18:12:56 UTC,Let's quiet those logs:
1779395,2018-06-29 18:35:21 UTC,"Hi Daniel,"
1779395,2020-05-09 11:39:46 UTC,Assuming fixed because there was no response. Please retest with the newest Inkscape version and report new issues in the new bug tracker: https://inkscape.org/report
1779401,2018-07-01 19:45:20 UTC,Fixed upstream.
1779401,2020-04-23 20:48:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779401,2020-04-23 20:51:20 UTC,I can confirm the problem and the workaround. For those interested here's the how to fix the code in place:
1779401,2020-05-28 10:53:14 UTC,"Yep, 18.04 is still affected by this
The correct link to a guthub issue is:
https://github.com/Cacti/cacti/issues/1546#issuecomment-382320908"
1779401,2020-06-13 09:10:45 UTC,SNMP data collection is also broken in the Ubuntu 18.04 cacti package
1779406,2018-07-05 14:12:50 UTC,This bug was fixed in the package livecd-rootfs - 2.408.36
1779406,2018-07-05 13:47:50 UTC,I have verified xenial using a locally created test image.
1779406,2018-07-04 16:07:06 UTC,"Hello Francis, or anyone else affected,"
1779406,2018-07-05 14:12:56 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1779406,2018-07-02 19:37:47 UTC,Found an issue while examining build logs that causes a failure to build minimal cloud images. Not sure how I missed it earlier.
1779406,2018-07-02 16:25:29 UTC,"Hello Francis, or anyone else affected,"
1779406,2018-07-02 21:28:52 UTC,The second merge proposal resolve the issue found during verification:
1779408,2018-07-02 22:28:03 UTC,"Tasks in THT require puppet args not currently available in the ansible module.
https://github.com/openstack/tripleo-heat-templates/blob/master/common/deploy-steps-tasks.yaml#L159
https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/nova-api.yaml#L252"
1779408,2018-07-06 19:15:48 UTC,"Module change has merged into ansible, 2.7 will be released in sept.  Retargeting this bug for stein."
1779408,2019-05-03 15:06:42 UTC,"Change abandoned by Brent Eagles (<email address hidden>) on branch: master
Review: https://review.opendev.org/579919
Reason: abandoning at +10 month mark"
1779408,2021-02-19 15:52:23 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1779415,2019-12-29 21:22:53 UTC,Closing as part of the bug migration to GitLab.
1779415,2018-06-30 09:51:32 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11), using the attached file."
1779415,2018-06-30 09:41:01 UTC,could you attach a sample file for testing purposes?
1779427,2019-07-02 19:26:13 UTC,"Your installed version does not have the fix. If you cannot wait for
a global Ubuntu upgrade, you can try upgrading ntfs-3g from the link
posted in #7. This might imply having to solve some dependencies."
1779427,2019-07-02 14:39:30 UTC,"Thanks for your answer...!
Maybe the update is only for Ubuntu 19? I'm on 18.04 LTS..."
1779427,2019-07-02 06:18:52 UTC,"> Unable to mount NTFS drives (64Kb cluster size) opened before with Windows 10
"
1779427,2019-07-01 15:54:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779427,2019-07-03 16:00:40 UTC,"Ok, I'll try to solve dependencies and install that version...!"
1779427,2018-06-30 00:21:08 UTC,"The attachment ""ntfs-3g-big-sector.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1779427,2018-06-29 23:55:16 UTC,Patch fetched from Fedora bug report to address Windows 10 issue.
1779427,2018-06-29 23:54:46 UTC,Patch fetched from Fedora bug report to address sector size issue.
1779427,2019-07-01 15:51:41 UTC,"Same problem here... I can confirm the same :S
Unable to mount NTFS drives (64Kb cluster size) opened before with Windows 10"
1779432,2017-05-22 13:18:51 UTC,** Please read this message in its entirety before responding **
1779432,2018-10-05 11:07:46 UTC,"HP is a very powerful brand which provide many products like printer, washing machine, desktop,laptops, etc but sometimes you may face issues in your device. For this you can reach on our website which provide various services like payment gateway integration and many more."
1779432,2017-05-22 14:53:12 UTC,Works for me with Ubuntu 16.04 LTS and LO 5.1.6.2
1779432,2017-05-23 18:04:24 UTC,OK for me on Mageia 6RC and LibreOffice 5.3.3.2
1779432,2017-05-28 17:06:34 UTC,"This bug is NOT fixed!
I still see this bug on Windows XP with LibreOffice 5.3.3.2 and a Brother HL-1430 printer.
(For the record this bug can also be found in 5.0.3.2 and 4.3.4.1)"
1779432,2017-09-17 09:47:42 UTC,*** Bug 112319 has been marked as a duplicate of this bug. ***
1779432,2018-03-12 19:53:16 UTC,It can also confirm for HP Officejet Pro 8100 on Debian 7 VG.
1779432,2018-08-08 18:34:12 UTC,"I don't have a printer to actually test this, but it seems it's a long-standing upstream issue: https://bugs.documentfoundation.org/show_bug.cgi?id=60428."
1779432,2018-10-01 05:29:05 UTC,"HP printer is a popular printer, I have also HP printer this printer is provide high quality printout. If you have any problem related to HP printer, Contact with HP printer Repair Service."
1779432,2018-10-04 09:02:52 UTC,"(In reply to fremwi from comment #3)

> Same problem with LO 4.0.2.2 and a HP OJ8600+ on Ubuntu 13.04 (64bits) and
> HP LPIP 3.13.8. The duplex printing works fine with Adobe reader (for
> instance), but can't be set with LO 4.0.2.2.
"
1779432,2018-10-24 11:32:02 UTC,"This is rather old bug with a number of duplicates. It's unlikely that some developer will follow this bug.
It's hard to confirm duplex issue because it is not a general LO problem but happens with some printer models only."
1779432,2019-04-30 22:35:04 UTC,"Finally! After only 5 years beingf reported! Code can be easily corrected by copying the duplex-printing code from any other app like Atril, FireFox, Chromium, etc.—they all work."
1779432,2018-11-15 12:53:57 UTC,"@ Robert Pearson.
I am one of the early bug reporters - not linked to LO in anyway.
As you can see in my comments 29, the bug was solved - and still is - for my configuration.
If you still have problems in yours (which printer , which distribution - version), I suggest you take the advice from Timur in Comment 36 and log a new bug with the appropriate details.
And no, this is not typical, I have logged bugs in the past and I've got responses in decent time lapses."
1779432,2019-01-09 19:57:07 UTC,This bug was reported over 5 years ago and has been ignored ever sense. It shows that the Linux developers do not respond to bug reports.
1779432,2019-01-10 10:24:12 UTC,"> After 5 years (reported on 2013-02-07) there is still no one willing
> to try and fix this bug.
"
1779432,2016-04-05 15:12:56 UTC,"related Bug 86848 fixed with
LibreOffice 5.1.1-1~bpo8+1
Debian 8.4 x64
KDE 4.14.2
cups 1.7.5-11+deb8u1
hplip 3.16.3+repack0-1~bpo8+1"
1779432,2019-09-09 06:22:16 UTC,"I'm really impressed with the info you provide. it's not possible to print duplex from LO
https://www.indiapropertyclinic.com/services/plumbing-rooter-services"
1779432,2019-09-09 10:06:26 UTC,"This is the most amazing thing I've seen today learned a lot please keep share an interesting post.
<a href=""https://uaetechnician.ae/computer-repair-services"">Computer Repair Dubai</a>"
1779432,2019-09-25 13:20:40 UTC,Synchronising bug status with upstream.
1779432,2020-01-11 09:42:22 UTC,"Said it's fixed:
<email address hidden>: reporter, Works for me with Ubuntu 16.04 LTS and LO 5.1.6.2
<email address hidden>: HP Officejet Pro 8100 on Debian 7 Wheezy: Bug 86848
<email address hidden>: OK for me on Mageia 6RC and LibreOffice 5.3.3.2"
1779432,2020-01-22 13:59:33 UTC,"LibreWriter still does not do duplex printing. Atril does. HP OfficeJet Pro
7740 USB connection Ubuntu MATE 18.04 (printing does not work at all with
Ubuntu MATE 19.10 so I rolled back to 18.04). Need to steal the code from
Atril to get LibreWriter printing 2-sided.
Robert Pearson"
1779432,2020-06-01 04:37:18 UTC,"solutions can help diagnose problems as quickly as possible, which can reduce the time and expense involved in getting the appliance back or reappearing
We fix all sorts of computer issues! From software to hardware we have the solution!
https://printerrepairdubai.ae/"
1779432,2020-06-01 04:41:49 UTC,"I read blog excellent application all platform to run like android ios and web great article It is very informative for us. Thanks for posting
https://printerrepairdubai.ae/"
1779432,2018-11-15 11:21:52 UTC,After 5 years (reported on 2013-02-07) there is still no one willing to try and fix this bug.
1779432,2016-01-29 12:26:11 UTC,"@Michael
I explained my usage and versions in Comment 13.
As I saw Comment 22, I wanted to test if the bug really was solved on my Mageia 5 platform.
The issue I got at the checkout, let me install 5.1.0 , not 5.0.2 as in Comment 22, but a newer version would be OK i guessed?
As to which repository I used, I cann't confirm anymore, as the laptop I used to test, died, and I had to replace it, I have to reinstall everything on a naw machine and run the tests again from scratch."
1779432,2015-12-14 05:36:52 UTC,"Migrating Whiteboard tags to Keywords: (bibisectRequest)
[NinjaEdit]"
1779432,2016-01-13 09:15:50 UTC,"Tried my hand at bibisect, got LO 5.1.0 on my PC
but at CLI:

> git checkout latest


error: pathspec 'latest' did not match any file(s) known to git.
So I used

> git checkout oldest


and that got me the 5.1.0 version
but:
Opening a multipage document and choose File - Printer Settings: I can select duplex. When I OK it, and open the dialogue again, the setting is preserved.
Then opening File - Print, choose Properties for the HP Officejet Pro 8100: the duplex setting is NOT on, I can set it, I OK the setting, and open the Properties again, the duplex setting is gone.
Trying to print two pages of the document gives me two pages of paper, the duplex setting doess not work."
1779432,2013-02-07 16:36:26 UTC,Problem description: it's not possible to print duplex from LO. it works from all other software. I tried all kind of different settings with no luck.
1779432,2013-05-30 20:37:48 UTC,*** Bug 65007 has been marked as a duplicate of this bug. ***
1779432,2013-05-30 21:09:42 UTC,"rosgnilk: I put it at New since there's a duplicate (considering ""See also"", I think there are more than 1)"
1779432,2013-09-07 09:14:06 UTC,"Same problem with LO 4.0.2.2 and a HP OJ8600+ on Ubuntu 13.04 (64bits) and HP LPIP 3.13.8. The duplex printing works fine with Adobe reader (for instance), but can't be set with LO 4.0.2.2."
1779432,2013-10-29 17:11:59 UTC,Whiteboard: NeedsDuplexPrinter
1779432,2014-07-19 14:18:27 UTC,*** Bug 70824 has been marked as a duplicate of this bug. ***
1779432,2014-07-19 14:27:56 UTC,"added 60428 as see also, as he has the inverted problem. (default settings: duplex, LO set to single paged)"
1779432,2014-09-04 17:59:36 UTC,*** Bug 82999 has been marked as a duplicate of this bug. ***
1779432,2014-09-05 07:42:38 UTC,Remove comma from whiteboard
1779432,2014-10-19 13:34:03 UTC,I confirm this with HP Officejet 8610 with the following software/OS pairs:
1779432,2016-01-29 10:22:05 UTC,"(In reply to herman.viaene from comment #23)

> Tried my hand at bibisect, got LO 5.1.0 on my PC
> but at CLI:
> > git checkout latest
> error: pathspec 'latest' did not match any file(s) known to git.
> So I used
> > git checkout oldest
> and that got me the 5.1.0 version
"
1779432,2014-10-31 05:56:44 UTC,*** Bug 80841 has been marked as a duplicate of this bug. ***
1779432,2014-11-29 13:56:17 UTC,"(In reply to GwenDragon from comment #11)

> Can confirm this for HP Officejet Pro 8100 on Debian 7 Wheezy, too.
>
> Libreoffice 4.2.6.3 does not change settings for duplex and page flipping.
"
1779432,2014-11-30 15:29:18 UTC,"Working on Mageia 3 and now 4, I cannot remember this appearing in LibreOffice 4.0.x. And BTW, I have been using (but not very frequently) LibreOffice on Win 7, and never had this problem. In fact, I make my documents on Mageia4 now, and print them on a Win 7 PC, which has networked access on my files on the Mageia PC.
The printing goes from Win 7 directly to the printer as both are on my WiFi router. the printer is connected to the Mageia PC on the USB."
1779432,2015-01-27 11:48:57 UTC,*** Bug 86848 has been marked as a duplicate of this bug. ***
1779432,2015-02-11 02:04:08 UTC,*** Bug 83602 has been marked as a duplicate of this bug. ***
1779432,2015-02-11 02:05:52 UTC,This also happens with an HP Photosmart 5520.
1779432,2015-02-19 22:20:37 UTC,"Confirmed:
1) x64, Linux Mint 17.1, HPLIP 3.15.2, LO 4.2.7.2, 4.4, 3.5.6 and 3.3.4 (last two LO version testing in virtual machines, but otherwise setup identical)
2) i386, Lubuntu 14.10, LO 4.3.3.2 (otherwise setup same as previous)"
1779432,2015-02-19 22:22:23 UTC,"(In reply to Coypus from comment #17)

> Confirmed:
> 1) x64, Linux Mint 17.1, HPLIP 3.15.2, LO 4.2.7.2, 4.4, 3.5.6 and 3.3.4
"
1779432,2015-02-21 17:20:16 UTC,"A couple of additional details about my setup, possibly relevant for debugging."
1779432,2016-01-09 04:49:01 UTC,if we ever hope to move this forward a bibisect from those seeing the problem would be REALLY useful. If you need someone to walk you through it feel free to join the chat: https://kiwiirc.com/client/irc.freenode.net/libreoffice-qa
1779432,2016-01-09 10:09:49 UTC,With HP Officejet Pro 8100 duplex printing works under LO.
1779432,2014-11-29 13:44:21 UTC,"Can confirm this for HP Officejet Pro 8100 on Debian 7 Wheezy, too."
1779435,2018-07-22 00:06:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779443,2018-07-12 09:50:24 UTC,Can you discuss how using the discard option causes performance problems when there are rare writes (<= once a week) to a partition?
1779443,2018-08-07 01:06:02 UTC,"Definitely, but I do not see this happening anytime soon (do you?)."
1779443,2018-07-12 09:48:52 UTC,A 16.04 system I'm looking at shows current modification times on all files in /EFI/ubuntu/ files:
1779443,2018-07-20 13:11:42 UTC,"If those files are being re-copied every kernel upgrade, then that is probably something that should not be happening.  They should only be copied on grub-install, not update-grub."
1779443,2018-07-02 02:46:34 UTC,"On some Ubuntu systems I manage, I see regular writes to the /EFI/ubuntu location with current file modification timestamps. On a multi boot system, the content of the ESP can also change more often. So I would say there seem to be regular writes, which means discard would make sense."
1779443,2018-07-06 17:18:40 UTC,"What files are changing?  The only thing there should be the grub core image and that should only change 3 or 5 times a year, assuming you are staying on the latest release instead of LTS."
1779443,2018-08-02 19:22:56 UTC,It would probably be better if the FAT filesystem simply got the proper discard ioctl like the rest.
1779443,2018-07-02 00:40:43 UTC,"What would be the point?  After the system is installed, the ESP isn't really ever written to again so there isn't anything that really needs discarded.  It's also rather small, so if there was anything that could be discarded, it wouldn't be much."
1779443,2018-07-20 15:05:17 UTC,I looked into this a little more. Files on the ESP are not written on every kernel image update. My current understanding is that they are only written when grub-install is run.
1779447,2020-11-24 16:44:17 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1779453,2018-06-30 10:53:51 UTC,Version: 6.0.4.2
1779453,2018-08-08 18:23:37 UTC,"Confirmed on libreoffice 6.0.6. Tested with the 6.1.0 snap, and the issue is fixed there, so it looks like this was an upstream bug that was fixed in 6.1."
1779453,2018-08-08 18:29:34 UTC,A cursory search through bugs fixed in libreoffice 6.1 didn't raise anything similar. It could be that this was fixed as a side effect of another bugfix.
1779457,2018-06-30 12:00:08 UTC,This change was made by a bot.
1779457,2018-07-03 19:25:47 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1779457,2018-07-04 19:38:04 UTC,"Thanks, installed kernel 4.18[0] rc3 and that seems to have fixed the problem so far."
1779467,2018-11-23 21:02:55 UTC,"Actually, ignore my last comment. I loaded it on another test server and had no trouble with the test. I'm guessing I must have changed something in the database on the first server to cause the problem. Signoff is forthcoming!"
1779467,2018-11-23 21:11:06 UTC,"My signoff, with an additional commit to fix the typo, is available at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/kmlussier/lp1779467-mark-item-discard-signoff."
1779467,2019-01-21 16:31:24 UTC,On a 3.2.2 server with this code installed:
1779467,2019-01-21 18:51:34 UTC,"Update: If the ""Charge processing fee for damaged items"" is in place it also causes the DAMAGE_CHARGE error and the status change fails."
1779467,2019-02-04 15:38:17 UTC,"Thanks, Jason - we've re-tested everything, and the damaged function is working properly and all of the other mark discard functions work great."
1779467,2019-02-03 16:18:38 UTC,"I have confirmed the behavior reported by Terran in comments 19 and 20, and I am working on a fix."
1779467,2019-02-03 16:51:44 UTC,"Well, that turned out to be relatively simple. I reverted the change that this branch made to the mark_damaged functionality in the web staff client files. This means that the original code is still used for marking an item damaged in the web staff client. The backend changes remain and still seem to work with the original staff client code."
1779467,2018-11-23 20:52:36 UTC,"Hi Jason,
I've been testing your branch today, and it looks really good! We saw only one minor issue where there is a typo in the Discard / Weed dialog. It says Dicard instead of Discard."
1779467,2019-01-31 14:44:30 UTC,I have removed the pullrequest tag pending investigation of the issue reported in Terran's comments (#19 and #20).
1779467,2018-11-23 18:20:11 UTC,Adding a link to the branch:
1779467,2018-11-07 21:29:45 UTC,Do let me know if you have any questions.
1779467,2018-11-07 21:27:31 UTC,Just finished testing and sent results to Kathy. Also posting here.
1779467,2018-11-07 21:13:55 UTC,"Ok. I have removed the pullrequest tag. I think I know what the problem is, but I'll do some testing to verify it before pushing a potential fix. My suspicion is it has to do with the test for the last hold copy not working on copy level holds."
1779467,2018-11-07 17:59:22 UTC,I was able to confirm the one Elaine saw yesterday:
1779467,2018-11-07 15:40:55 UTC,Jason
1779467,2018-11-06 21:03:05 UTC,"Branch has been gone through initial testing and I am told that it will be signed off, so removing myself, and adding the pullrequest tag."
1779467,2018-07-17 19:05:56 UTC,"Responding to Mike's observations in comment #3, except points 3 & 4 that Elaine responded to:"
1779467,2018-07-17 18:28:34 UTC,"3/4) Cancelling transits. Remember that this development is for circ staff
to place items in discard/weed to then be deleted from the database by
cataloging staff, whether lost in transit or still in transit on the shelf.
Items lost in transit would be found with a report and would be handled
differently from those found on the shelf in transit, to be weeded. Either
way, the copy is to be deleted by cataloging staff and would no longer be
in the database and checking in would do no good if it did make it's way
back.  I think the important thing with this is that the status of transit
is removed from the item to be placed in discard/weed, and that transaction
closed, so that cataloging staff can delete the item, without having a
transaction that would otherwise not be completed, hanging around in the
database."
1779467,2018-07-17 14:42:06 UTC,"Hi Jason,"
1779467,2018-07-17 14:09:16 UTC,+1 for consistent behavior
1779467,2018-07-15 16:05:25 UTC,"While working on this today, I came up with some thoughts on the back
end code for marking items in the various statuses.  The following
statements are all my opinion and the direction I am taking with the
code.  If anyone disagrees, then please chime in."
1779467,2018-11-12 14:45:17 UTC,I have force-pushed a rebased branch to the same location with two additional commits:
1779472,2018-07-06 13:19:22 UTC,My custom changes to skins.xml seem to be overwritten when updating Mixxx. Should I be making custom changes to an INCLUDE file of some type and using an INCLUDE statement of some type in skins.xml? Or should I be using some other method to retain custom skin changes? Thanks!
1779472,2018-07-19 15:17:42 UTC,https://github.com/mixxxdj/mixxx/pull/1755
1779472,2018-07-06 13:37:57 UTC,"Well, I take it back. I just updated Mixxx and my custom skin.xml was preserved, this time. I do notice that when I perform an update, the installer has options for UNINSTALL and REPAIR. I have to choose the REPAIR option to perform an update. I would expect the installer to have an UPDATE option, since I'm not trying to perform a REPAIR, but REPAIR seems to be the only option for performing an update. Just FYI."
1779472,2018-07-01 18:22:33 UTC,"Thanks, ronso0! That xml editing worked! Perhaps some controls could have a ""persist"" checkbox on them, in the skin? Maybe some of the skins already have this. I know some of the skins have an ""options"" section that can be tweaked. I really have only used the LateNight skin. Thanks!"
1779472,2018-07-06 13:52:55 UTC,"Please not that this is a bug report, for unrelated discussion we have:
https://www.mixxx.org/forums/viewforum.php?f=8 for skins and mixxx.zulipchat.com for development related topics."
1779472,2018-07-18 23:31:42 UTC,Update: I have had to resort to settings skins.xml to read-only to prevent Mixxx from writing over my customizations on update.
1779472,2018-06-30 17:47:29 UTC,You just need to set the persintant flag for the control in the c++ code to fix that bug.
1779472,2018-07-01 16:35:21 UTC,"closely related, if not a duplicate:
lp:1747212 optimize Auxiliary enable control"
1779472,2018-07-01 16:41:10 UTC,"quick solution: mute all Aux inputs by adding this to skin.xml:
<attribute config_key=""[AuxiliaryX],mute"">1</attribute> (X = 1, 2, ...)"
1779478,2018-12-22 18:07:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779478,2018-12-22 18:09:35 UTC,Same for 32 bit (bug 1710517).
1779479,2018-06-30 16:08:02 UTC,Fix is Welkom! This is my first bug report don' t know from here what to do...
1779479,2018-07-03 21:02:22 UTC,You may need to run the following from a terminal:
1779479,2018-07-03 21:30:05 UTC,This change was made by a bot.
1779498,2019-02-03 17:20:10 UTC,What is happening here? No reaction for 6 months?
1779507,2018-07-02 07:04:42 UTC,"Hi Daase,"
1779507,2018-07-02 18:29:28 UTC,"Hi Santoash,"
1779507,2018-07-03 08:38:00 UTC,"Hi Santosh,"
1779507,2020-07-07 08:54:10 UTC,"I'm experiencing the same bug on an M255dw on hplip 3.20.6 on Fedora. It seems that the error occurs near the end of the document. If I print a very long document, it occurs in its last couple of pages. If I only print a small part of the document, it occurs in the last few pages of the part."
1779507,2020-11-04 08:39:05 UTC,"Just a note to say that after switching from using WiFi to using USB, this problem went away for me."
1779508,2018-08-01 02:05:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779515,2021-02-17 17:08:32 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1779515,2018-07-02 01:20:56 UTC,"I noticed that _templates/layout.html refers to CSS and Javascript files in a directory named _static. It turns out that these files exist, but the directory is named _custom. A quick fix, I thought, and replaced _static with _custom."
1779519,2018-08-12 13:33:13 UTC,It's actually pretty easy to do in AWS:
1779524,2018-07-01 08:20:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1779524,2018-07-01 10:02:49 UTC,"In response to Launchpad's message: ""Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it."""
1779526,2018-07-05 22:59:26 UTC,https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.32-2ubuntu1
1779530,2018-09-21 01:43:47 UTC,"Looks like a failure to install Mixxx 2.1. @Sebastien, can you take a look please and see if we have enough info to debug?"
1779530,2018-11-01 00:21:17 UTC,Why remove the milestone? Now we have no way of seeing that this affects 2.1.x ?
1779530,2018-11-01 07:13:21 UTC,"Ups, right. Now it is on 2.1.6"
1779530,2019-01-13 11:17:29 UTC,Is this still an issue with Mixxx 2.1.6?
1779530,2019-02-27 17:32:04 UTC,"I believe I had the same issue installing Mixxx 2.2.0 and 2.1.6;
When I run the installer it declares ""Installer was not able to find Microsoft Visual Studio C++ 2015 Redistributable on this system...
The log file looks about the same as above."
1779530,2019-02-27 17:42:10 UTC,"Small addition (my apologies, I'm new here)
This happens on both 32 and 64 bit installers. I can add the log file from the 32 bit crash here if desired, but it's essentially the same, using paths to the x86 files instead of x64."
1779530,2019-03-05 15:59:11 UTC,"duplicate?
lp:1813260"
1779536,2020-08-04 16:58:44 UTC,"Google Translate recognizes as Danish text and translates:
""Pinta goes down when I forget a picture on USB"""
1779539,2018-10-05 20:09:45 UTC,https://stackoverflow.com/questions/8482152/whats-the-difference-between-rpath-and-l
1779539,2018-10-05 19:49:57 UTC,the faulty commit is https://github.com/mixxxdj/mixxx/commit/5ba6519a7d2ec70228a3958cf1c626b65d2c66c4
1779539,2018-09-15 12:23:31 UTC,I am using g++ as toolchain.
1779539,2018-10-06 04:16:13 UTC,"Hm, sorry for the breakage... this bug was filed before that commit, so I don't think it caused knoedelgespenst's problem."
1779539,2018-09-15 17:02:10 UTC,"Ah, nevermind. The ""stdlib"" option is ignored (it used to control macOS only)."
1779539,2018-09-15 17:23:57 UTC,"* Can you post the full build log from scons and your config.log file?
19:16:52 **** Incremental Build of configuration Default for project mixxxLibRedisgnMaster ****
scons stdlib=libc++ hss1394=0 vamp=1 mad=0 faad=0 ffmpeg=1 shoutcast=0 opus=0 coreaudio=0 hid=0 verbose=0 qt5=1 -j4
scons: Reading SConscript files ...
INFO:root:Target Platform: linux
INFO:root:Target Machine: x86_64
INFO:root:Build: debug
INFO:root:Toolchain: gnu
INFO:root:Crosscompile: NO
INFO:root:Qt path: /usr/lib/x86_64-linux-gnu/qt5
Checking whether the C++ compiler works... (cached) yes
Configuring MixxxCore
Checking for pkg-config (at least version 0.15.0)... (cached) yes
Checking for C library X11... (cached) yes
Configuring SoundTouch
Checking for soundtouch (2.0.0 or higher)... 	(cached) no
Configuring ReplayGain
Configuring Ebur128Mit
Checking for C library ebur128... (cached) no
Checking for C library libebur128... (cached) no
Checking for C header file sys/queue.h... (cached) yes
Configuring PortAudio
Checking for C library portaudio... (cached) yes
Configuring PortMIDI
Checking for C library porttime... (cached) yes
Checking for C library portmidi... (cached) yes
Checking for C header file portmidi.h... (cached) yes
Configuring Qt
Checking for Qt5Core (5.0 or higher)... 	(cached) yes
Configuring TestHeaders
Configuring FidLib
Configuring SndFile
Checking for C library sndfile... (cached) yes
Checking whether SFC_SET_COMPRESSION_LEVEL is declared... (cached) no
Configuring FLAC
Checking for C header file FLAC/stream_decoder.h... (cached) yes
Checking for C library libFLAC... (cached) yes
Configuring OggVorbis
Checking for C library libvorbisfile... (cached) yes
Checking for C library libvorbis... (cached) yes
Checking for C library libogg... (cached) yes
Checking for C library libvorbisenc... (cached) yes
Configuring OpenGL
Checking for C library GL... (cached) yes
Checking for C library GLU... (cached) yes
Configuring TagLib
Checking for C library tag... (cached) yes
Configuring ProtoBuf
Checking for C library libprotobuf-lite... (cached) yes
Configuring Chromaprint
Checking for C library chromaprint... (cached) yes
Configuring RubberBand
Checking for C library rubberband... (cached) yes
Configuring SecurityFramework
Configuring CoreServices
Configuring IOKit
Configuring QtScriptByteArray
Configuring Reverb
Configuring FpClassify
Configuring PortAudioRingBuffer
Configuring Mad
Configuring CoreAudio
Configuring MediaFoundation
Configuring HSS1394
Configuring HID
Configuring Bulk
Checking for C library libusb-1.0... (cached) yes
Checking for C header file libusb-1.0/libusb.h... (cached) yes
Configuring MacAppStoreException
Configuring VinylControl
Configuring LiveBroadcasting
Configuring Opus
Configuring Profiling
Configuring BuildTime
Configuring QDebug
Configuring Verbose
Configuring Optimize
Configuring FAAD
Configuring WavPack
Configuring ModPlug
Configuring TestSuite
Configuring Vamp
Checking for C library vamp-hostsdk... (cached) yes
Checking for vamp-plugin-sdk (2.7.1 or higher)... 	(cached) no
Checking for C library dl... (cached) yes
Checking for C header file fftw3.h... (cached) yes
Checking for C library fftw3... (cached) yes
Configuring ColorDiagnostic..."
1779539,2018-09-15 19:24:31 UTC,"Thanks! Everything looks fine, so I'm still confused."
1779539,2018-09-16 18:57:06 UTC,"I am quite new to contributing to FOSS. So i dont know which commit hash your meaning, but this is my contribution, on which i am working on: https://github.com/mixxxdj/mixxx/pull/1764/commits"
1779539,2018-09-15 04:27:26 UTC,"Hm, interesting. Ubuntu 16.04 uses libstdc++ by default with gcc -- are you using clang? If so, what version?"
1779539,2018-10-06 05:28:34 UTC,"We need to set a custom rpath on macOS if we want self-compiled Qt installations to work, but I'm not sure why we need it on Linux."
1779539,2018-10-05 04:36:24 UTC,Today I suffer the same issue using the master branch on Ubuntu Trusty. Even after deleting the .sconsign.dblite.
1779539,2018-10-08 11:34:32 UTC,Here is a proposal for a band-aid https://github.com/mixxxdj/mixxx/pull/1832
1779539,2018-10-06 05:59:49 UTC,"> gcc --print-search-dirs
install: /usr/lib/gcc/x86_64-linux-gnu/4.8/
programs: =/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin/
libraries: =/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/lib/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/:/lib/x86_64-linux-gnu/4.8/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/4.8/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/lib/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../:/lib/:/usr/lib/
"
1779539,2018-09-17 17:05:35 UTC,"But i tried to build the master before, where i got that issue. Switching over to the branch, and i had the same problem."
1779547,2018-07-01 20:59:13 UTC,Thanks for your report!
1779563,2018-07-12 10:47:16 UTC,Same issue here. I wanted to grab just one package from Buster but adding the sources.list for it meant that I upgraded to it by accident too :(
1779563,2018-07-22 10:32:04 UTC,"I have fixed the issue purging the ""raspi-copies-and-fills"" package. More detailed information about this fix can be found here: https://raspberrypi.stackexchange.com/questions/72594/failed-to-start-udev-kernel-device-manager"
1779563,2018-07-22 10:59:18 UTC,"I can confirm the last version of the https://github.com/bavison/arm-mem repository is working properly.
The steps that I have followed:
1. Purge ""raspi-copies-and-fills"" package
2. Clone https://github.com/bavison/arm-mem repository using ""git"" tool
3. 'make' command to compile from source
4. 'cp libarmmem-v7l.so /usr/lib/arm-linux-gnueabihf/libarmmem.so'
5. 'echo ""/usr/lib/arm-linux-gnueabihf/libarmmem.so"" >> /etc/ld.so.preload'
Maybe is not the best solution but is working at the moment. It would be nice an update of the ""raspi-copies-and-fills"" package."
1779567,2018-07-01 18:53:59 UTC,"To the devs. I don't know how you keep track of all of these, but here's a related (but still very different) request: https://bugs.launchpad.net/kicad/+bug/1778622"
1779567,2019-09-24 13:50:36 UTC,Occurs on stable v5.1.4 on Windows 10 (x64) as well.
1779567,2019-09-24 14:18:11 UTC,"In a custom shaped pad, the anchor pad can be only a round or rectangular pad.
See the dialog pad settings."
1779568,2018-07-01 18:46:07 UTC,"If this request is implemented, I'd also say to add: Allow ""Create Pad from Selected Shapes"" with *zero* selected pads. ie: if you just draw polygons and want to make a pad out of it, let it happen. Currently it will result in an error if you don't have one connected pad to the polygon shapes."
1779568,2018-07-01 18:49:22 UTC,Here's my related (but still quite different) request: https://bugs.launchpad.net/kicad/+bug/1778622
1779568,2019-05-31 17:20:41 UTC,"0 pads might be tricky as the anchor pad is what is used to attach traces and determine what is used as the ""at"" parameter."
1779572,2018-08-17 17:27:12 UTC,Thanks!
1779572,2018-08-16 16:05:32 UTC,Fixed in stable r18752 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18752>.
1779572,2018-08-17 10:44:46 UTC,"Fixed, and all the imports I saw mentioned here are working again."
1779572,2018-08-14 23:33:52 UTC,https://code.launchpad.net/~stk/stk/stk-assets and https://code.launchpad.net/~stk/stk/trunk affected (note the latter is a git-to-bzr import).
1779572,2018-07-22 19:49:19 UTC,"fresh imports are also affected:
https://code.launchpad.net/~reviczky/luatex/metapost"
1779572,2018-08-15 15:12:32 UTC,"I can reproduce this when pushing to the Bazaar branch store using sftp, but not when pushing using bzr+ssh.  The latter is generally a better protocol anyway, so I think we should just switch to that."
1779572,2018-07-01 18:46:21 UTC,Link to the log: http://launchpadlibrarian.net/376648742/reviczky-texlive-trunk.log
1779574,2019-11-04 14:09:30 UTC,"The verification of the Stable Release Update for geary has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1779574,2019-11-04 14:09:22 UTC,This bug was fixed in the package geary - 0.12.4-4~ubuntu18.04.3
1779574,2019-10-25 11:15:22 UTC,I downloaded and extracted the geary_0.12.4-4~ubuntu18.04.3_amd64.deb file from bionic-proposed and confirm that the upstream translations are preserved in both the .desktop files and in the geary.mo files in /usr/share/locale.
1779574,2019-10-25 10:15:17 UTC,"Hello Pavel, or anyone else affected,"
1779574,2019-05-25 05:19:55 UTC,A bionic fix is possibly in progress via bug #1815626.
1779574,2018-09-02 20:40:00 UTC,"On 2018-09-02 17:58, Jeremy Bicha wrote:

> I guess you are suggesting we modify the Debian GNOME universe packages
> to add this to debian/rules instead.
>
> override_dh_translations:
"
1779574,2018-09-16 00:10:09 UTC,This bug was fixed in the package geary - 0.12.4-2
1779574,2018-09-02 15:58:17 UTC,I guess you are suggesting we modify the Debian GNOME universe packages to add this to debian/rules instead.
1779574,2018-09-02 15:17:41 UTC,@Jeremy: Another option would be to prevent dh_translations from running. Sounds easier to me.
1779574,2018-09-02 14:30:16 UTC,"So, it looks like the issue here is that ""dh --with gnome"" runs dh_translations, but the package is in universe so it doesn't actually use language packs."
1779574,2018-07-02 01:36:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779574,2019-05-24 23:50:06 UTC,"An upload of geary to bionic-proposed has been rejected from the upload queue for the following reason: ""Wrong version number for upload which sorts > cosmic""."
1779575,2018-08-10 00:17:03 UTC,fixed in 2.2
1779575,2018-07-11 11:27:32 UTC,"I'd say this behaviour is party intended and partly a bug:
the lower half was constructed this way to avoid squeezed samplers or Mic units, but the settings don't persist when the skin get's resized/redrawn or when Mixxx gets restarted."
1779575,2018-07-20 21:21:51 UTC,https://github.com/mixxxdj/mixxx/pull/1754#issuecomment-406708668
1779575,2018-07-20 21:22:00 UTC,https://github.com/mixxxdj/mixxx/pull/1754
1779577,2018-07-02 00:21:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1779577,2018-07-02 05:03:09 UTC,Thanks for the tip!
1779578,2020-01-08 14:32:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779578,2020-01-08 17:30:46 UTC,PYBIND11_MODULE is part of version 2.2.0 which is in Ubuntu 19.04.
1779581,2018-07-12 04:48:31 UTC,"Please, very need build for UT 16.04"
1779581,2019-10-14 20:11:32 UTC,"i Have the same Build and the same Problem.
The Button Initialize Pebble do not work.
The Connection between Phone and Pebble B6A0 are stable. not more"
1779583,2018-07-01 22:10:15 UTC,This may be one solution to the problem reported here:
1779583,2018-07-01 23:23:01 UTC,I guess I should attempt to compile before submitting a patch. Some brackets were required in one of the cases.
1779583,2018-08-29 02:09:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779583,2018-07-02 00:21:14 UTC,"The attachment ""Compiling fix to second fork() in child_process()"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1779584,2018-07-02 14:38:44 UTC,"Yes, that can be an option, but I am a bit afraid disturbing the caching reader."
1779584,2018-07-02 16:04:43 UTC,"Oh, I see that the track appears under MISSING TRACKS. Sorry, I had not noticed that. So, the track's absence DOES get detected during SCAN LIBRARY. That's great! Also, I see that applying PURGE TRACK FROM LIBRARY to a MISSING TRACK removes the track's listing from ALL playlists that point to it! That solves my original issue! The only thing I would suggest is, maybe, a pop-up or other notification which appears after RESCAN LIBRARY that says something like: ""Some playlists are now invalid / pointing to tracks which are not found. Check MISSING TRACKS in LIBRARY."" Thanks!"
1779584,2018-07-02 16:20:37 UTC,"I don't think there should be any sort of indication that a track is hidden or any user interaction required. If a track is hidden or missing, I don't think it should be shown in playlists. I think ronso0's idea to check whether tracks are hidden when displaying a playlist is a good idea."
1779584,2018-07-02 20:50:32 UTC,"We cant remove it from the playlist, because if the missing state is temporary the play-list is broken."
1779584,2020-08-23 14:49:12 UTC,"A different color of the letters of the missing track name could be of a great help.
Missing tracks shouldn't be removed from the playlists but somehow they have to be distinguished."
1779584,2018-07-01 22:35:33 UTC,"I can confirm that there is an issue. But a solution is not that easy. We cannot remove the tracks unconditionally from the play list, because the file missing might be a temporary issue, because of a missing hard drive or such.
A possible solution is probably to gray the file out. The remaining question its: when should the greyed out status be updated."
1779584,2018-07-02 12:49:01 UTC,"I can confirm the issue, I ran into only a few times though."
1779585,2020-03-25 21:42:49 UTC,Sounds like a good idea to me. geozubuntu are you interested in working on it?
1779585,2020-03-25 11:32:54 UTC,It should be extremely useful feature.
1779585,2018-09-21 00:15:13 UTC,"I think they might mean searching from the root playlists node (i.e. with no playlist selected). Paul, is that right?"
1779585,2018-07-01 22:30:26 UTC,"I cannot confirm this. The search is disabled for AutoDj though, which is intended to not play hidden tracks, which could be surprising."
1779585,2020-03-25 22:09:40 UTC,"Unfortunately I'm not a programmer.
Thanks for proposing.
Of course thanks for all this good work."
1779585,2020-03-25 11:58:54 UTC,Of course it can be done through the Tracks general search but that way we would have one more search active.
1779587,2018-08-10 00:26:25 UTC,https://github.com/mixxxdj/mixxx/pull/1735
1779597,2018-07-02 04:27:50 UTC,"Oh, and I upgraded the kernel with ukuu, it also happens with the kernel in 18.04"
1779598,2019-06-11 02:27:05 UTC,"Can reproduce with Inkscape 0.92.4, cannot reproduce with 1.0alpha2 (883c7bc26f, 2019-06-02)."
1779598,2019-06-11 02:28:28 UTC,"Assuming fixed in 1.0alpha2 (883c7bc26f, 2019-06-02)."
1779604,2018-07-24 01:19:48 UTC,"I found today that if I select other window (one on other monitor) while keeping the Library Browser visible and then right click on the library browser the menu is shown, however, if I expand the grid submenu or as seth said, use the menu bar or system menu, or the window completely loses focus (no visible) then this no longer works."
1779604,2018-07-23 15:49:52 UTC,"I can confirm this on Debian/XFCE using v5 and v6.  The key to triggering the issue under GTK is to invoke a system menu first.  When the window first appears, I am able to see the KiCad context menu.  If I use the menubar or right-click on the title, I can no longer get the KiCad context menu.  This feels like a focus loss issue."
1779604,2018-07-03 04:21:14 UTC,I found that the call to PopupMenu() in TOOL_MANAGER::dispatchContextMenu() always returns instantly with false as return value when the library browser is launched from eeschema.
1779604,2018-07-22 16:10:08 UTC,"GTK-specific (Fabian reports it's OK on Windows, and I checked OSX where it's also OK)."
1779607,2018-07-02 10:36:54 UTC,"- reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1779607,2018-07-02 10:47:51 UTC,"- crash not reproduced on Windows 10, Inkscape 0.92.3 (cdafc07, 2018-06-25)
- instead I get the attached DOS error message, but no crash."
1779607,2018-07-03 02:15:06 UTC,"Not reproduced in Win 8.1 64, Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1779607,2018-07-19 19:51:18 UTC,"I used the hierarchical delta debugging algorithm (see http://www.gmw6.com/docs/hdd-icse06.pdf) to minimize the input that causes the crash on my system.  The original svg file was 106,685 characters.  This new input is only 203 characters long.  It should be much easier to debug the issue if you are able to reproduce the problem on your system."
1779607,2018-07-19 19:54:44 UTC,"@TylerDurden you are correct, the original document did not come from Inkscape.  I created the original document in google spreadsheets, downloaded as a PDF, and then imported that PDF into Inkscape.  Since then I have made considerable manual edits on the vector graphic elements, including layers."
1779607,2018-07-19 20:00:03 UTC,"In case you are curious to use this same technique to minimize test cases for other bug reports, here is the python code I used.  I had tried to automate the bug using X11 events, but instead reverted to simply manually going through the steps to try to get the UI to crash, then waiting for my script to launch the UI with a smaller input and do it again.  I had to try to reproduce the bug 35 times to minimize this svg file.  The running of this algorithm only took about 10 minutes."
1779607,2019-05-06 14:54:20 UTC,No longer replicated in 1.0alpha (master).
1779607,2020-05-24 16:59:37 UTC,"No longer replicated in 1.0, considering it fixed/a duplicate of https://gitlab.com/inkscape/inkscape/-/issues/97 despite minor differences (since I can no longer replicate the crash in 1.0 and I cleaned up the logic that led to the crash)"
1779614,2018-07-02 06:46:57 UTC,"More info:
1. then all the volumes cannot be deleted, error messages will be give as below:"
1779622,2018-07-08 18:24:29 UTC,"thanks for reviewing but where is the solution? what i am suppose to
do in order to fix it...it is getting worse.."
1779623,2018-07-02 13:14:14 UTC,This is because at the moment we have not enabled the MAAS snap to run in strict mode. It only works in devmode.
1779624,2019-10-26 17:44:14 UTC,Well that's what just happened to me but with entire playlist! 😭
1779627,2018-07-02 09:02:02 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/579494"
1779627,2018-08-08 04:30:36 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.5 release.
1779627,2019-03-14 04:39:39 UTC,All relevant patches are merged. Closing the bug.
1779627,2018-07-12 12:23:25 UTC,"Reviewed:  https://review.openstack.org/579494
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a3948bed9f3df7c162cdd0252a1b31aedf2d553e
Submitter: Zuul
Branch:    stable/queens"
1779627,2018-07-04 16:09:10 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/579494
Reason: The gate is suffering of timeouts, we need to clear it. Please do not restore or recheck this patch, I'll take care of it when gate is stable again."
1779633,2018-07-03 16:46:01 UTC,"Actually, it looks like this was fixed in the latest release with this commit:"
1779633,2018-07-09 13:39:07 UTC,The only bug of openstack-ansible I pointed out is that prep cache script does not handle the fact that packages conflicts could happen. It seems that the book assume that this script executed successfully even if packages hasn't been installed.
1779633,2019-07-01 14:15:12 UTC,I have having same issue with CentOS 7.6.
1779633,2019-07-01 15:02:47 UTC,"Finally i have destroy all container, uninstall lxc* and re-run setup-hosts.yml to make it work, look like before lxc creation method it borked and didn't install correct package in container, with there is a way to force re-deploy container from scratch instead of uninstall everything and reinstall."
1779633,2018-07-03 16:44:31 UTC,"I think the bug here is that the prep cache script did not exit, however, we'll need more information about your custom config that is enforcing 7.4"
1779633,2018-07-02 09:53:59 UTC,"It seems to be related with the LXC container's packages version, because i'm still on CentOS 7.4.1708. I attached my lxc-cache-prep-commands.log. Packages installation fails because of dependencies, but it doesn't seems to trouble ansible."
1779639,2019-05-30 16:56:23 UTC,I tried recreating this today on Ubuntu 19.04 and when I started update-notifier again (step 3) I immediately received a notification about a crash. Are you still able to trigger this issue?  Thanks in advance!
1779639,2019-08-14 04:17:19 UTC,[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.]
1779640,2018-12-19 16:23:45 UTC,"On Wed, Dec 19, 2018 at 04:10:45PM -0000, Joseph Salisbury wrote:

> Are you able to manually able to start the daemon after seeing that the
> file exists?
"
1779640,2019-02-14 16:16:56 UTC,Sorry for the delay. That might be a dependency problem on the KVP systemd service. I will run some tests locally. Can you confirm if the problem also happens with the linux-azure kernel?
1779640,2019-02-14 17:07:09 UTC,Does it also happen with the lastest generic bionic kernel (4.15.0-45)?
1779640,2019-03-14 13:23:53 UTC,I've filed a new bug for the kvp daemon not starting on disco: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063
1779640,2019-03-06 02:42:20 UTC,"I am not able to reproduce the crash on bionic. There is an issue on disco, but it's not a crash, but a failure to start the daemon as mentioned in comment 16. As this appears to be a different issue, I can open a new bug."
1779640,2018-12-19 16:10:45 UTC,Are you able to manually able to start the daemon after seeing that the file exists?
1779640,2019-11-21 07:24:41 UTC,"Try HyperV command, you will see hv-kvp-daemon service exit with KVP: read failed; error:9 Bad file descriptor"
1779640,2020-07-02 19:27:40 UTC,"Ubuntu 19.04 reached end of life on January 23, 2020.  I am therefore marking this bug 'wontfix' for that release."
1779640,2019-02-14 18:37:03 UTC,I wasn't able to reproduce it in hyper-v or in azure using the 4.15.0-45 generic kernel.
1779640,2018-12-18 22:35:49 UTC,"Yep, I have now done so:"
1779640,2018-12-17 20:27:15 UTC,"On disco, we're seeing the following in the cloud image testing:"
1779640,2018-12-18 20:16:33 UTC,"This was from our test suite, so I don't have direct access to an instance, but using the manifest, it is:"
1779640,2018-12-17 20:53:38 UTC,"Hi Dan,"
1779640,2018-11-16 15:18:07 UTC,Are you able to manually download the .deb packages from those pages and used dpkg to install them:
1779640,2018-11-06 08:50:33 UTC,"Missed the reply on this thread, my apologies.
I tried now to install the packages from those ppa's, however apt will not detect the kernels."
1779640,2018-07-05 17:14:33 UTC,"Would it be possible for you to test some prior kernels to see if we can bisect this issue down?  If so, the following kernels would be a good starting point:"
1779640,2018-07-05 16:10:34 UTC,"We haven't seen it in Xenial, but we managed to reproduce it back to the daily Bionic build from the 2nd of March. We haven't tested Bionic daily builds before the 2nd of March, nor did I try to reproduce it on Zesty or or Artful."
1779640,2018-07-03 21:10:05 UTC,"We were discussion if this specific bug was a regression in bug 1766857.  Do you recall prior kernel versions that did not have this specific issue?  If so, we can perform a bisect to narrow down what commit introduced this."
1779640,2018-07-02 12:09:14 UTC,I have tested this on kernel 4.15.0-24.26 and linux-cloud-tools 4.15.0-24.26 and the issue persists.
1779640,2018-07-02 10:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1779640,2018-12-18 22:12:01 UTC,"Do you have a way to pause a test, so you can access the instance?  It would be good to know if the file actually exists:"
1779640,2018-11-16 15:19:45 UTC,Another good test would be to see if this bug is still happening on newer releases such as Cosmic or even Disco.
1779640,2019-01-17 09:46:21 UTC,Could this be a race condition with the device file creation and start of the hv-kvp-daemon.service?
1779643,2018-12-13 15:00:12 UTC,This issue was fixed in the openstack/tosca-parser 1.3.0 release.
1779643,2019-09-03 00:55:53 UTC,Nice. Thanks Miguel!
1779645,2018-10-09 22:51:38 UTC,I was hit by this bug yesterday.
1779645,2018-12-01 16:23:01 UTC,"A few minutes ago, I just made the massive mistake of running ""tasksel remove samba-server"" (Which I had installed using tasksel install samba-server)."
1779645,2019-08-22 10:59:43 UTC,It happened again - https://askubuntu.com/q/1167523/66509 .
1779645,2019-11-07 13:34:01 UTC,Duplicate of bug 574287?
1779645,2018-10-09 22:58:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779649,2020-11-12 15:35:38 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1779649,2021-01-12 04:17:29 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1779650,2020-09-26 17:24:13 UTC,Does the problem still persist with the latest version of QEMU? Did you maybe try to report it to the Spice project (https://www.spice-space.org/support.html)?
1779650,2020-11-26 04:17:21 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1779652,2018-12-11 19:19:51 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1779652,2019-08-15 13:32:24 UTC,This got fixed some time ago.
1779657,2021-01-20 09:23:30 UTC,"Probably the kernels were manually installed for some reason, but there's certainly not enough to act on this. Needs at least /var/lib/apt/extended_states /var/lib/dpkg/status /etc/apt/apt.conf.d/01autoremove-kernels to be able to investigate what happened here."
1779657,2021-01-18 11:37:13 UTC,I was looking into the same thing
1779657,2021-01-20 09:21:58 UTC,Sean:
1779657,2021-01-20 09:54:13 UTC,"No manually installed kernels. And these were not meta packages. But since I am on 20.04 now, this is not affecting me anymore."
1779661,2020-06-15 16:30:10 UTC,Confirmed in Ubuntu 20.04 GNOME Flashback. Changing of Application Switcher or Static Application Switcher background doesn't work.
1779661,2018-08-25 00:23:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779661,2018-08-25 11:38:35 UTC,It is probably mate-specific issue. Try raising the issue on https://ubuntu-mate.community.
1779661,2018-08-25 12:05:49 UTC,"Ah, right, Application-switcher is unity only. You need static-application-switcher. You can get it by installing `compiz-plugins`."
1779661,2018-08-25 12:38:36 UTC,"@khurshid-alam is right that this bug occurs with the Static Application Switcher compiz plugin, as well as the Application Switcher compiz plugin. Both of these are different from the Unity application switcher, which is a different beast entirely."
1779661,2019-11-11 14:03:53 UTC,@Khurshid-alam
1779666,2018-07-02 12:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1779666,2018-07-02 12:54:35 UTC,Unable to run bug report as I have uninstalled 4.15.0-24 kernel and reverted back to 4.13.0-45.
1779667,2018-07-02 17:03:01 UTC,"Please attach anything vaguely relevant-looking from the system log (systemd Journal if you use systemd, or /var/log/syslog). The bug will probably be somewhere in the vicinity of logind, PAM, dbus-daemon, lightdm, X or XFCE, or possibly graphics drivers in the kernel (which have been known to lock up during fast-user-switching), but without looking at the log it's impossible to say which."
1779667,2018-07-02 12:21:43 UTC,"Also, the problem is not specific to any user."
1779667,2018-07-05 10:36:40 UTC,## Log: soon
1779672,2018-07-31 22:31:26 UTC,"The regex on scopeid is to blame. If scope is necessary, maybe it's best to determine scope from the ipv6 address itself, instead of from ifconfig output. link for fe80, site for fec0, node for ::1, and global for everything else."
1779672,2018-08-14 13:03:23 UTC,meanwhile someone updated the freshport for cloud-init to the version 18.3 with a particular patch that most likely seems to cover this issue: https://svnweb.freebsd.org/ports/head/net/cloud-init/files/patch-cloudinit_netinfo.py?annotate=476024
1779672,2018-10-23 18:14:31 UTC,"> may someone is able to verify this and make sure it does not create issues with ubuntu or other platforms.
"
1779672,2019-02-06 16:30:56 UTC,my deployment with cloud-init and FreeBSD 11.2 seems to work with your fix now again:
1779672,2019-02-06 14:44:51 UTC,"FreeBSD doesn't have iproute2 (ip) command, it uses the fallback ifconfig output parsing.  With that in mind, let's have another look at this."
1779672,2019-02-06 14:20:59 UTC,Can you capture the 'ip addr show' output from this host?
1779672,2019-02-06 15:47:56 UTC,@do3meli
1779672,2019-02-06 16:04:37 UTC,@raharper
1779672,2019-05-10 18:07:24 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1779672,2019-02-08 22:08:50 UTC,"This bug is fixed with commit fff37e7d to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=fff37e7d"
1779677,2018-07-16 08:20:03 UTC,"Hi,"
1779677,2018-10-09 23:21:32 UTC,PR against 2.3: https://github.com/juju/juju/pull/9294
1779677,2018-10-10 06:18:25 UTC,PR against 2.4: https://github.com/juju/juju/pull/9297
1779677,2018-12-22 11:01:13 UTC,I'm still seeing plenty of this on 2.5-rc1: https://pastebin.ubuntu.com/p/s752BrXCVT/
1779677,2019-01-07 06:57:36 UTC,"It likely won't appear in ""juju models"" because the model is broken. You need to go in the DB to find it."
1779677,2018-07-10 13:15:14 UTC,"@Junien Fridrick (axino),"
1779678,2018-07-04 09:37:52 UTC,"I've been running a 4.18 kernel for a long time now and I haven't been able to reproduce the bug. Please note however, that this bug was a race. Meaning, it is easily possible that the race has just gotten so unlikely that it doesn't matter anymore. I doubt it however, since a) there's a proper explanation for the prior bug and b) the locking has changed completely upstream."
1779678,2018-07-03 20:54:11 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1779678,2018-07-02 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1779679,2018-08-20 10:42:45 UTC,"The cause of the problem arose in this patch
https://review.openstack.org/#/c/510784/
https://github.com/openstack/watcher/commit/7d33bf88131845ca796ad09cce7fe435c056fbb5"
1779679,2019-05-29 07:00:10 UTC,I was unable to reproduce this and it is likely fixed in the current version but in case you want to investigate further could you provide the list of flavors and their details in your set up?
1779679,2019-07-29 04:17:19 UTC,[Expired for watcher because there has been no activity for 60 days.]
1779679,2018-11-07 02:38:28 UTC,"My nova compute environment was based on Newton, with the latest watcher code base I defined the api_version under [nova_client] section as 2.38 which is the version for Newton (and actually I also tried setting it to 2, which is the minimum value), the same error (KeyError: 'ram') with the flavor is still coming up, so setting the api_version doesn't seem to fix the issue. Is it a known issue or did I miss anything?"
1779682,2018-07-10 13:19:07 UTC,I wonder if it is related to bug # 1778614...
1779682,2018-07-16 08:23:03 UTC,"Hi,"
1779682,2018-10-22 23:15:39 UTC,I wonder 2 things:
1779683,2019-12-18 09:27:23 UTC,"I think this bug is not relevant anymore.
I'm going to close it, if anybody wants to reopen it fell free"
1779691,2018-07-02 15:10:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/579590"
1779691,2019-06-21 12:38:10 UTC,what about commit to master??
1779691,2020-09-23 16:09:04 UTC,"Doesn't appear to be a push for needing this functionality. At any rate, this would be a new feature of the driver, not a bug."
1779691,2020-09-23 16:09:47 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/579590
Reason: No updates for quite some time, and I haven't heard of anyone asking for this. Can be restored if there is actually a need for it."
1779701,2018-07-02 14:37:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/579576"
1779701,2018-07-03 12:36:35 UTC,"Reviewed:  https://review.openstack.org/579576
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=2dcd4af21e893990338524c6f934f4ae712acc95
Submitter: Zuul
Branch:    stable/queens"
1779701,2018-07-05 17:26:41 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.0.4 release.
1779701,2021-02-17 17:08:37 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1779703,2018-07-02 17:21:43 UTC,"I've created a new Inkscape extension, titled ""Split kerned text"", that can split X-axis kerned text into separate words. While not perfect, it can do the job most of the time. I've put it here:"
1779703,2019-06-11 03:21:27 UTC,"Hey there, our extensions repository is now on GitLab, where you can send a merge request for new extensions: https://gitlab.com/inkscape/extensions. Hope to see some contributions there!"
1779703,2020-02-09 22:14:37 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1779705,2018-07-02 15:56:50 UTC,If you do a :
1779705,2018-07-02 16:01:35 UTC,Or just this output :
1779705,2018-07-09 13:23:23 UTC,This issue was fixed in the openstack/python-mistralclient 3.6.1 release.
1779716,2019-09-19 12:05:59 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1779720,2018-07-26 05:44:14 UTC,Does kernel report correct key events?
1779721,2018-07-02 17:31:13 UTC,You can also reproduce this issue with the official cloud image. See https://askubuntu.com/questions/1030081/ubuntu-18-04-cloud-image-does-not-get-dhcp-ipv4-address
1779721,2018-07-02 19:40:41 UTC,"An empty match, does not match any interfaces hence none are configured...."
1779721,2018-07-03 09:08:20 UTC,My interpretation of the documentation was that an empty match entry matches everything. I changed the configuration to enforce the matching and it still fails:
1779721,2018-07-03 09:13:37 UTC,Just checked the initial configuration:
1779721,2018-07-03 09:30:51 UTC,"Ok, i must be mistaken about empty match stuff then."
1779721,2018-07-03 10:36:46 UTC,"The dhclient lease looks ok. It has a largish MTU, but that should be fine."
1779721,2018-07-03 10:05:53 UTC,/run/systemd/netif/leases is empty
1779721,2018-07-03 12:24:25 UTC,Setting 'dhcp-identifier: mac' (translates to networkd 'ClientIdentifier=mac' option) makes no difference. One specialty is that the subnet-mask is 255.255.255.255 (i.e. /32).
1779721,2018-07-03 13:31:09 UTC,"$ sudo env SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
[...]
DHCP CLIENT (0x...): received lease lacks address, server address or lease lifetime, ignoring"
1779721,2018-07-03 13:45:14 UTC,Full log output:
1779721,2018-07-03 13:46:03 UTC,"Attached dhclient.pcap file generated with:
# tshark -i ens6 -w /tmp/dhclient.pcap"
1779721,2018-08-06 07:32:55 UTC,This is not really a bug in systemd-networkd. It just adheres more strictly to the standard.
1779721,2018-08-15 10:46:40 UTC,This bug in systemd-networkd is affecting our environment also.
1779721,2018-09-27 18:05:15 UTC,I don’t know if this should be a different bug or a note added here.
1779730,2018-08-14 17:08:36 UTC,"Please attach sanitized unit logs, a reproducer bundle, and ideally a juju crashdump."
1779730,2018-08-14 16:50:32 UTC,"This bug is subscribed to Canonical Field Critical and tracked by the SLA process.
Does the incomplete status mean development needs something from the submitter?
Could a comment be added with what's needed or an estimate on when this bug is targeted for a fix?"
1779730,2018-08-15 18:52:05 UTC,The latest charm provided for us to use on customer's deployment does not go into error state.
1779730,2020-01-21 12:37:29 UTC,It's not clear whether this is still an outstanding bug or not?
1779732,2018-07-02 18:27:24 UTC,"As expected the sort by display_name seems to work fine, but that's really a server-side name for this field"
1779735,2020-07-25 20:13:08 UTC,I a pretty sure something else has triggered the problem. Some step before save was problematic. Writing exact step by step how crash appears would be very helpful.
1779736,2020-05-30 04:52:54 UTC,"seth-arnold, the ZFS default is actltype=off, which means that ACLs are disabled. (I don't think the NFSv4 ACL support in ZFS is wired up on Linux.) It's not clear to me why this is breaking with ACLs off."
1779736,2018-09-17 11:48:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779736,2019-01-18 15:18:03 UTC,"As a workaround/fix, the umask is respected if you set the acl to the zfs exported pool""
zfs set acltype=posixacl ..."
1779736,2019-01-21 00:46:50 UTC,"I am having a similar problem on Fedora, but the documentation is sparse. As a workaround, I presently mount using NFSv4.1 rather than 4.2. I can neither find precise documentation on (1) what is going on nor (2) how to restore the behavior where the process umask comes into play when creating a file or directory."
1779736,2019-03-06 16:38:40 UTC,"I can confirm this issue, on Ubuntu Bionic - server is 4.15.0-43-generic, client is 4.15.0-45-generic. Server filesystem is ZFS (using nfs-kernel-server for export). Mounting with vers=4.1 works around it as noted above."
1779736,2019-03-07 18:57:06 UTC,"I can confirm that ""zfs set acltype=posixacl foo/bar/"" is an effective workaround. It appears to be
unset by default."
1779736,2019-08-04 20:39:15 UTC,I can confirm setting acltype to posixacl on the dataset shared via NFS fixes the issue.
1779736,2019-09-03 14:08:06 UTC,"Same for me, setting posixacl on ZFS exported via NFS is a workaround"
1779736,2020-05-29 01:41:44 UTC,"The default NFSv4 acls may be a poor choice on ZOL. This keeps biting people unexpectedly, I wonder how many people this has affected and they never spot it?"
1779736,2020-07-25 03:23:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779736,2020-09-02 14:24:29 UTC,I'm reluctant to change the ZFS default to make NFSv4 work out of the box as this may cause regressions for users expecting the default. I'm making this bug a wish until somebody can produce compelling evidence why we should change the default and how this won't affect the user experience for the non-NFSv4 users.
1779740,2018-12-08 13:53:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779743,2018-07-05 16:22:17 UTC,Confirmed also in 3.0.8
1779745,2018-07-02 20:02:58 UTC,Adding apport log.
1779757,2018-10-03 14:32:53 UTC,Seeing this on a Dell R720
1779757,2018-10-03 16:39:26 UTC,"As a workaround, I wound up setting the BIOS clock time to match UTC which is the timezone that the installer was using. I was able to complete installation that way."
1779757,2018-11-21 16:55:54 UTC,"I just encountered this same problem while trying to install Ubuntu 18.04 on a server I inherited from another team. Unfortunately, its BIOS is password-protected and nobody knows the password, so... I had to find a different workaround. It turns out that—instead of changing the BIOS to store time in UTC—you can just change the system time to the (correct) UTC time."
1779757,2018-12-27 19:55:58 UTC,"Adding this comment as a Note to Self, for future reference. I just had to reinstall Ubuntu 18.04 on the same server. This time, after setting the (Linux) system time using the `date` command, I then ran:"
1779757,2019-01-17 19:13:39 UTC,"Also faced this issue with 18.04.1 installer.
Setting UTC time in BIOS (8 hours ahead of my time zone) as Rick pointed out allows installer to complete."
1779757,2019-02-20 17:05:03 UTC,I'm getting the same issue installing 18.04.2 Live Server onto a Dell R330; the BIOS time is local time. I'm going to try converting BIOS time to UTC and see if that allows installation to complete.
1779757,2019-02-21 16:15:22 UTC,Ditto - when I changed my BIOS time to UTC I was able to complete the install.
1779757,2018-10-03 14:10:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779764,2018-07-04 06:21:05 UTC,"Funding a free software project is hard. GNU parallel is no exception. On top of that it seems the less visible a project is, the harder it is to get funding. And the nature of GNU Parallel is that it will never be seen by ""the guy with the checkbook"", but only by the people doing the actual work."
1779764,2018-07-08 16:36:53 UTC,"The nagging approach is not appropriate for general-use software distributions like Ubuntu. Ubuntu should remove the citation stuff from the code base, and rename the package if necessary to accomplish that."
1779764,2018-08-10 10:57:04 UTC,"""Is it alright to compromise or even deliberately ignore the happiness of the maintainers so that we can enjoy free and open source software?"""
1779764,2019-04-12 07:22:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779767,2021-01-28 16:19:21 UTC,"@laney i would agree to patch cron with our default path, with snap/bin included."
1779767,2019-09-26 15:23:54 UTC,I believe this will be fixed in v2.41 snapd.
1779767,2021-01-14 17:34:51 UTC,This bug is old but I'm going to un-duplicate it. I don't believe it is fixed.
1779767,2019-09-10 09:05:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779775,2018-07-08 19:22:32 UTC,"This does not only affect the track duration but also various other columns that might be aligned right within their column:
- Date Added
- Year
- ReplayGain
- Key
- BPM
- Bitrate
- Track #"
1779775,2018-07-08 20:34:04 UTC,"> for the BPM column I prefer to cut off the less significant fractional
> digits to the right.
"
1779775,2018-07-08 21:09:28 UTC,I just tried to expand the scope of your valid request and didn't metion any technical preconditions or requirements ;) Generalizing also helps to think about the consequences and implications.
1779775,2018-07-11 15:27:56 UTC,"okay, so let's push this a bit further:
BPM: align left, but reserve space for 3 digits before the decimal point

> this allows to align the decimal points and resize the column to hide the decimal places
"
1779775,2019-02-25 20:57:52 UTC,"There has been some progress on this, eg
https://github.com/mixxxdj/mixxx/pull/2001
https://github.com/mixxxdj/mixxx/pull/2002"
1779777,2018-07-03 20:17:45 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1779777,2018-07-02 23:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1779777,2018-07-03 00:56:37 UTC,apport information
1779777,2018-07-11 08:37:27 UTC,"Yes, wl.ko."
1779777,2018-07-09 12:25:59 UTC,Apparently you mean a popritarian driver?
1779777,2018-07-09 04:32:21 UTC,Seems like this device uses an out-of-tree driver instead of an in-tree one?
1779777,2018-07-07 22:56:34 UTC,"I'm having the same problem with my
Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)"
1779777,2018-07-04 15:47:47 UTC,kernel-bug-exists-upstream
1779777,2018-07-04 15:46:04 UTC,"The problem occurred after the kernel was automatically updated to version 4.16. This is not the first time when the kernel is updated, and I tried to reinstall bcmwl-kernel-sourse. It did not help, I tried other recipes on the net, but they also did not help.
On the previous kernels 4.15 4.13 everything worked, after updating and attempts to restore the work of the wifi, work only on version 4.4 of my installed.
With versions of the system above 4.16 there are complications they are not correctly installed due to the lack of the libssl1.1 module, with its installation there are problems.
The driver, on reinstallation, produces errors that can not be installed and there is no WL module
help me please"
1779777,2018-07-03 00:56:35 UTC,apport information
1779777,2018-07-03 00:56:34 UTC,apport information
1779777,2018-07-03 00:56:40 UTC,apport information
1779777,2018-07-03 00:56:32 UTC,apport information
1779777,2018-07-03 00:56:31 UTC,apport information
1779777,2018-07-03 00:56:29 UTC,apport information
1779777,2018-07-03 00:56:28 UTC,apport information
1779777,2018-07-03 00:56:27 UTC,apport information
1779777,2018-07-03 00:56:25 UTC,apport information
1779777,2018-07-03 00:56:24 UTC,apport information
1779777,2018-07-03 00:56:33 UTC,apport information
1779777,2018-07-03 00:56:23 UTC,apport information
1779778,2018-07-02 23:24:33 UTC,"Eclipse has also a nice preferences filter.
It just highlights the matching tree-view items (panes)"
1779781,2018-07-03 09:26:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/579828"
1779781,2018-07-03 09:01:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/579820"
1779781,2019-10-07 13:47:43 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/579828"
1779801,2018-09-05 18:36:34 UTC,"Change abandoned by Ryan Tidwell (<email address hidden>) on branch: master
Review: https://review.openstack.org/581778"
1779801,2018-09-14 17:24:39 UTC,"The issue happens due to the confusion around zuul v3 migration.
The situation has changed since then according to the mailing list discussion."
1779801,2018-08-27 23:33:28 UTC,I don't think this is a bug in master neutron
1779801,2018-09-14 17:30:42 UTC,"FYI: networking-midonet now uses zuulv3 docs job, so I believe the problem can be fixed by updating the 'neutron' line in requirements.txt to ""neutron>=13.0.0"" (rocky release)."
1779801,2018-07-10 09:57:17 UTC,Need to fix in neutron
1779801,2018-07-06 08:22:51 UTC,"I added neutron as neutron-vpnaas has the same issue.
https://review.openstack.org/#/c/579742/"
1779801,2018-07-05 12:55:54 UTC,"Reviewed:  https://review.openstack.org/580098
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=e1d8cdd420ec06e309833ea5db63444d87ff2158
Submitter: Zuul
Branch:    master"
1779801,2018-07-11 15:30:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/581778"
1779801,2018-07-03 16:10:19 UTC,I noticed this bug in queens/gate jobs for networking-odl too.
1779801,2018-07-04 09:03:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/580098"
1779812,2018-07-03 20:55:17 UTC,Only active EngineChannels are processed already.
1779812,2018-07-03 21:04:26 UTC,Samplers become active if a track is loaded.
1779812,2018-09-13 10:10:04 UTC,confirmed. CPU load doubles from 23% to 54% when I load all 64 samplers (Deere).
1779813,2018-07-30 00:32:58 UTC,a feedback has been provided
1779813,2018-07-04 01:24:49 UTC,"@Brian, I just start from an empty database."
1779813,2018-07-03 16:28:41 UTC,I have a couple of questions since I'm confused by the description.
1779817,2018-08-09 12:17:15 UTC,"It's was only Kai's kernel from comment #39 that didn't boot - I've not had
any other problems on that front."
1779817,2018-08-09 15:54:35 UTC,I can reproduce the issue with ethernet failing on the r8169 on resume from suspend with the current kernel.  This is a regression since a previous kernel on 18.04 since the symptoms occur after installing updates.
1779817,2018-08-09 11:05:19 UTC,Whether other systems suffer from the same MSI-X incompatability we'll know only once I get more such bug reports. So far your report is the only one.
1779817,2018-08-09 09:13:12 UTC,"Just double-checked with lspci -vvv and indeed the Realtek NIC is the only
MSI-X capable device. Is there anyway to disable MSI-X globally but leave
MSI on? All I can find is pci=nomsi which seems a bit heavy handed.."
1779817,2018-08-09 09:08:11 UTC,"Yup, afraid so, Beelink S1: https://www.amazon.co.uk/dp/B077HKCT78 - I'm
basically using it as an old-fashioned X Terminal. They promised a BIOS
update to ""make it work with Linux"" but I never got it to install and they
stopped answering my emails :( Happy to put it down to broken hardware so
long as I have a workaround, but is there anything else we can check to
confirm that? No noticeable problems with any other part of the system, bit
I guess everything else is part of the SoC, so this is probably the only
PCIe device I'm actually using.."
1779817,2018-08-08 18:14:44 UTC,@kalle1
1779817,2018-08-08 14:29:59 UTC,"Hmm, no ""IOMMU"" messages in dmesg, and the CPU is supposed to support it,
so I guess it is disabled,
however this machine really doesn't have a BIOS to speak of, in terms of
configurable settings anyway :("
1779817,2018-08-07 21:03:50 UTC,"I can't even boot Kai's latest kernel! The system hard locks early in the
boot process, I have tried blacklisting r8169 and rebuilding the initramfs,
pretty sure it is not loaded by the point at which it hangs. My hardware is
cursed..."
1779817,2018-08-08 13:42:39 UTC,One more hint: I found few reports where people had problems (independent of what is being discussed here) with MSI-X when VT-d is disabled in the BIOS. Could you check this as well?
1779817,2018-08-08 13:19:41 UTC,"Apart from switching to a more up-to-date API after this commit MSI-X will be used if available. Maybe your system has a problem with MSI-X. If you keep the commit and just do the following change, does it fix the issue?"
1779817,2018-08-08 11:41:34 UTC,Progress!
1779817,2018-08-07 21:37:13 UTC,@Kai-Heng your latest kernel completely breaks the network using r8169 for me. The system sort of manages to complete startup but fails to attach an address to the network card. This is accompanied with lots of console output similar to this
1779817,2018-08-07 20:13:38 UTC,"@Kai-Heng
I can confirm what Erik says - my network card seems to come up properly after suspend with the backported kernel in #39."
1779817,2018-08-09 17:28:33 UTC,"@Heiner, I know a number of other modules have a ""use_msi_x"" option - I
guess that would be too much to ask given I'm the only one who seems to
need it so far? :)"
1779817,2018-08-08 13:44:18 UTC,"I'm about to dash out, but will try the above change later. Meanwhile,
relevant bits of dmesg:"
1779817,2018-08-10 11:49:22 UTC,"@Steve, there's some resistance amongst kernel maintainers against additional module parameters. Each new parameter increases complexity and makes maintenance harder.
Most likely it would result in a NAK when trying to fix an issue with one broken exotic (sorry..) system in the kernel, especially if a userspace workaround is available (disabling MSI via sysfs for the network device)."
1779817,2019-06-17 19:54:57 UTC,This bug was fixed in the package linux-oem - 4.15.0-1043.48
1779817,2018-08-15 18:06:47 UTC,This is the only solution that worked for me: https://askubuntu.com/a/1053520/222403
1779817,2018-08-07 11:52:22 UTC,"@Kai-Heng your last kernel seems to have done the trick for me!
My network comes back up after standby."
1779817,2018-10-01 17:15:35 UTC,This bug was fixed in the package linux - 4.15.0-36.39
1779817,2018-09-17 19:17:27 UTC,For me the version in bionic-proposed also seems to work fine.
1779817,2018-09-14 22:08:41 UTC,"Earlier problems seem to have been caused by the packages not all arriving in the archive together, and apt-get/aptitude and myself getting very confused - apologies for noise. Can now confirm that 4.15.0-35.38 seems to solve the issue; tags adjusted."
1779817,2018-09-14 20:37:15 UTC,"New bug report opened:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792635"
1779817,2018-09-14 20:29:28 UTC,"Well 4.15.0-35.38 doesn't even finish booting on my machine. Doesn't
find the root volume and the USB keyboard doesn't finish booting.
Chances are the r8169 fix is fine but I can't test."
1779817,2018-09-14 17:02:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1779817,2018-09-08 09:33:34 UTC,"I've found these discussion, installed latest r8169 driver and at last internet begins to restore after suspending! Before that nothing help, including ""modprobe -r r8169"" and restart NetworkManager. I'm happy! )))"
1779817,2018-08-28 21:39:42 UTC,"Kai-Heng Feng,"
1779817,2018-08-24 12:41:04 UTC,"Yup, this kernel finally fixes things for me too (I did remember to
disable my other workaround) - thanks Kai, look forward to seeing it
SRU'd."
1779817,2018-08-24 08:39:12 UTC,"Kai-Heng, the bug seems to be gone on my system with your newest kernel in #63 and I don't experience any regression so far. Thanks for your work!"
1779817,2018-08-23 10:23:43 UTC,"Folks,
Please try this kernel out:
https://people.canonical.com/~khfeng/r8169/"
1779817,2018-08-21 21:19:28 UTC,Attached is a work-around for the in-kernel driver that is as unhacky as I can make it.
1779817,2018-08-17 17:01:13 UTC,Thanks Marco #59 !!!
1779817,2018-08-15 18:27:52 UTC,"@Heiner,"
1779817,2018-08-13 20:06:50 UTC,"Can we cherry-pick
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=7c53a722459c1d6ffb0f5b2058c06ca8980b8600
for bionic?"
1779817,2018-08-07 06:04:55 UTC,"Jan, I made a new backport based on net-next, please try it out:"
1779817,2018-08-09 08:47:22 UTC,Good that it's fixed for you. Indeed your BIOS seems to be broken with regard to MSI-X. According to the vendor part of the MAC address your mini PC is some no-name China product?
1779817,2018-08-06 07:28:11 UTC,I also tried the net-next from kai-heng and I have the same issue no network from boot.
1779817,2018-07-25 03:25:14 UTC,Bionic's kernel doesn't have commit b489141369f78ead6ed540cff29ac1974852cd7f.
1779817,2018-07-24 22:25:46 UTC,See https://bugzilla.kernel.org/show_bug.cgi?id=200195
1779817,2018-07-22 20:46:34 UTC,"During the last days I tried to bisect the commit that caused the regression, but I'm not sure if the result is correct."
1779817,2018-07-20 01:57:04 UTC,I'm in the same situation as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/comments/12
1779817,2018-07-18 05:34:41 UTC,"If we are sure that the r8169 works on older kernel, but not on the latest one, we can use kernel bisection to find which commit causes the regression:"
1779817,2018-07-13 10:04:36 UTC,"I'm not sure if I'm in the right bug thread, 4.15.0-24 stopped my r8168/9 NIC working after suspend, was fine in prior versions. I have tested Kai's lp1779817-2 kernel above but it does not help."
1779817,2018-07-12 09:30:51 UTC,"I have tested https://people.canonical.com/~khfeng/lp1779817-2/ , and it still does not fix the bug for me."
1779817,2018-07-12 04:32:43 UTC,"I've finished backporting all r8169 changes from net-next to 18.04 kernel. Please give it a try:
https://people.canonical.com/~khfeng/lp1779817-2/"
1779817,2018-07-07 01:36:17 UTC,"search for ""r8168 for 4.15 kernel"" and you will see problem from across many linux distributions."
1779817,2018-07-06 10:53:38 UTC,"Kai-Heng, I have tested mainline kernel 4.18-rc3 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3/ and it seems not to fix the issue."
1779817,2018-07-06 03:44:56 UTC,"Jan, does you issue fixed by mainline kernel v4.18-rc3?"
1779817,2018-07-05 20:50:52 UTC,"Kai-Heng:
I have tried the kernel under https://people.canonical.com/~khfeng/lp1779817/ and I see no change on my system (bug still there; reloading network driver after resume from suspend is still necessary)."
1779817,2018-07-05 10:08:31 UTC,"Please try this kernel:
https://people.canonical.com/~khfeng/lp1779817/"
1779817,2018-07-04 08:03:05 UTC,I tested with kernel linux-modules-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64 and it's fixed. Thank you.
1779817,2018-07-03 20:18:54 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1779817,2018-07-25 06:47:08 UTC,Please try the kernel [1] compiled with patch in [2].
1779817,2018-07-25 21:42:40 UTC,"This patch did help, my network comes up again after suspend with that kernel version. Thanks alot!"
1779817,2018-07-24 08:41:51 UTC,"Alright, I'll build an Bionic kernel without this commit."
1779817,2018-07-26 07:49:46 UTC,"Erik, did the ethernet work in previous kernel version?"
1779817,2018-08-06 07:13:36 UTC,@Kai-Heng sorry for my late response to your question #22 (holidays) for me everything worked on 4.14.0-23 and stopped working after that
1779817,2018-08-05 10:28:57 UTC,"@Kai-Heng
I did that, with net-next directly it seems that everything is working again at least as good as in 4.15.0-23 (Network card comes up at boot, and also after suspend."
1779817,2018-08-04 07:26:43 UTC,"Ok, can you try net-next [1] directly?"
1779817,2018-08-03 20:42:43 UTC,"@Kai-Heng
With this kernel version, unfortunately my network doesn't come up at all (even after fresh power on. Reloading driver does not help)."
1779817,2018-07-26 07:34:17 UTC,"I have tried both kernels lp1779817 and mainline 4.18-rc6 but the problem is still there for me, also for me the"
1779817,2018-08-03 10:30:44 UTC,"The commits that causes the regression is a fix for another issue, LP: #1752772. So we can't simply revert those fixes because it will regress other users."
1779817,2018-08-03 10:12:08 UTC,"I still think there are multiple bugs here. Some of us have a network that
absolutely will not come back up after suspend with kernel version

>4.15.0-23, even after reloading the driver. So there is a very clear


regression that I would really like see resolved / rolled back. Breaking
stuff in an LTS release for multiple users isn't much fun :("
1779817,2018-08-03 09:45:59 UTC,"Ok, I can confirm what I wrote on #28 on another installation."
1779817,2018-08-03 11:28:25 UTC,"Please try this kernel:
https://people.canonical.com/~khfeng/bionic-r8169-backport/"
1779817,2018-07-03 07:30:07 UTC,This change was made by a bot.
1779817,2018-08-01 11:25:11 UTC,"i have the same issue with r8169 and Kubuntu 18.04.
with kernel version higher than 4.15.0-23 the network is not coming back from suspend."
1779817,2018-08-01 09:27:09 UTC,"Jan, so with 4.15.0-23, the NIC comes back every time the system suspend/resume?"
1779817,2018-07-28 07:33:42 UTC,"A bit off-topic but: on a third machine of mine, booting into into Bionic leaves the network card in a state where WoL won't work at all, even after rebooting back into Trusty (3.13.0.) Have to power cycle the machine, then WoL is fine.. (r8169 driver again, obviously)"
1779817,2018-07-26 11:09:57 UTC,"I have to correct myself a bit: Network coming up correctly after suspend only works from time to time. On the cases where it's not working, the driver still has to be reloaded."
1779817,2018-07-26 08:54:52 UTC,"lp1779817 kernel from #19 doesn't help me, last working kernel is 4.15.0-23."
1779817,2018-08-03 08:00:23 UTC,"@Kai-Heng
Weird, I reinstalled and tested 4.15.0-23 again, and it seems that with 4.15.0-23 it can also happen that network is not coming up after suspend and the driver has to be reloaded.
I'm going to further test this on another installation."
1779817,2018-08-06 13:02:01 UTC,"I've just built net-next direct from git and still have the same issue - the NIC doesn't come back after suspend, even with rmmod / modprobe."
1779825,2018-07-03 12:58:11 UTC,https://review.openstack.org/#/c/531857/
1779825,2018-07-03 13:00:28 UTC,"pip is installing 12.0.3 instead of something like
13.0.0.0b2"
1779825,2018-07-03 13:07:03 UTC,https://review.openstack.org/#/c/579856/
1779825,2018-07-05 18:01:15 UTC,"Reviewed:  https://review.openstack.org/579856
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=45cddcbd02f8b2e45fb70816d5012605d221700c
Submitter: Zuul
Branch:    master"
1779826,2018-09-24 14:46:42 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1779826,2018-10-08 21:49:20 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1779826,2018-10-02 22:16:37 UTC,"Reviewed:  https://review.openstack.org/583422
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0217a2cac969eb5dd82d95e051df1cac3c0ab70d
Submitter: Zuul
Branch:    stable/ocata"
1779826,2018-09-24 14:47:15 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1779826,2018-09-21 12:02:04 UTC,"Reviewed:  https://review.openstack.org/583426
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1316e08c85456ca69bc55bf9a90a24e341884952
Submitter: Zuul
Branch:    stable/pike"
1779826,2018-07-25 13:07:28 UTC,"Reviewed:  https://review.openstack.org/583418
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d543ddda02311986d5318a14dd21a3393df37c3e
Submitter: Zuul
Branch:    stable/queens"
1779826,2018-07-18 01:35:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/583426"
1779826,2018-07-18 01:16:43 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/583422"
1779826,2018-07-18 00:50:28 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/583418"
1779826,2018-07-17 19:59:25 UTC,"Reviewed:  https://review.openstack.org/579747
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b26df4fa6cd78a9b60de79750d4e9a58980d13ca
Submitter: Zuul
Branch:    master"
1779826,2018-07-30 16:07:10 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1779827,2018-07-15 17:15:05 UTC,Thank you Wes Newell for your reply.
1779827,2018-07-15 01:50:14 UTC,"Easiest thing to do is just delete the .24 kernel. During boot, start tapping the esc key repeatedly. You should get the grub menu. Select the advanced option, and then load the last good kernel, which should be the .23 one if you've kept the system up to date. Once it boots and everything is working right, you can use your package manager to remove the offending .24 kernel or do it manually with sudo apt remove <kernel name>. Once you've removed it, grub will automatically be updated so it will boot to the .23 kernel. FWIW, the .24 kernel was removed from the repo as to not to infect people that do updates now."
1779827,2018-07-14 22:25:11 UTC,Please could anyone share some detailed instructions on how to apply these quick fixes...
1779827,2018-07-13 01:14:38 UTC,"@joverstreet1, kernel 24 was installed first, by Ubuntu Software Updater. I then installed haveged to work around a kernel change to getrandom(). My SSD is not Western Digital but the SSD has nothing to do with the problem, at least not the one that is the focus of this bug report."
1779827,2018-07-12 20:36:42 UTC,tim-smith:
1779827,2018-07-12 20:21:21 UTC,"Did you install haveged ""BEFORE"" you attempted update to kernel #24 ?"
1779827,2018-07-12 19:33:10 UTC,"@m-tim-smith, comment #85, if none of the fixes/workarounds here are working for you, perhaps you have a different problem with very similar symptoms. For example bug #1779476."
1779827,2018-07-12 18:14:47 UTC,">I have come to the conclusion that the problem with the #24 Linux Kernel is related
to the use of SSD hard drives.
Really? Well, how smart! Just try to read a previous posts and you'll understand that you're completely wrong.
"
1779827,2018-07-12 11:16:58 UTC,"I am also affected by this, and it is most likely the issue with entropy for randomness, because if I mash some random keys, I get to boot."
1779827,2018-07-12 12:44:20 UTC,@dimztimz - could you elaborate on what u did specifically? Other solutions above (not the patched kernel) don't work for me.
1779827,2018-07-11 19:27:07 UTC,"I'm happy to report that I was able to boot normally with gdm now, and it didn't get stuck. Yesterday I removed and reinstalled gdm3 and ubuntu-desktop, as suggested here, rebooted, but it was still the same (i.e. stuck in reboot), so I switched back to lightdm. Today when I turned it on it started normally using gdm (although I don't remember switching it to gdm again!)."
1779827,2018-07-11 06:59:34 UTC,"Sorry... my ""bug"" was PEBCAK!"
1779827,2018-07-10 16:15:23 UTC,"Tried mocnak's solution, no effect"
1779827,2018-07-10 16:14:52 UTC,"before I wanted reply to your question, I rebooted my laptop, and now I'm
stuck on boot screen - so not the same as error described here. Anyway, it
helped me just to log-in once and now I'm on OS unable to boot properly
again. It took around 3 minutes to show me login screen."
1779827,2018-07-10 15:46:02 UTC,"@mocnak, re. comment #78. Thanks. I reinstalled gdm3 but didn't think about ubuntu-desktop. Anyway I've reverted to the existing Ubuntu version of plymouth and got my system working again (with haveged)."
1779827,2018-07-10 15:21:59 UTC,"what helped me, when I was stuck on black boot screen, was to reinstall Gnome:"
1779827,2018-07-12 15:39:00 UTC,"I have come to the conclusion that the problem with the #24 Linux Kernel is related
to the use of SSD hard drives."
1779827,2018-07-15 22:53:17 UTC,@delosari https://forum.snapcraft.io/t/snapd-service-delays-startup-in-ubuntu-18-04-with-4-15-0-24/6205/10 says pressing shift key continuously during boot could be a workaround. It worked for me.
1779827,2018-07-16 17:23:03 UTC,"Installing the entropy daemon 'haveged' (sudo apt install haveged) worked on my notebook (Clevo, Tuxedo MS-1753, Kernel 4.15.0-24-generic). Boot time is as normal. Also manually adding entropy by moving the mouse like hell, reduced the boot time from 5 to 1.4 minutes."
1779827,2018-07-16 05:05:01 UTC,"Seeing this on Kubuntu 18.04 too. The haveged work around worked yesterday, but this morning I had to go back to 4.13 - the only previous kernel I have installed."
1779827,2019-04-26 05:43:59 UTC,"Is there even anyone out there with disco dingo AND a functioning kernel with an nvidia driver? But of course if someone did, they wouldn't be here."
1779827,2019-02-14 16:59:41 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1779827,2018-12-30 11:17:31 UTC,Wifi not working after upgrading to Disco Dingo development version
1779827,2018-11-17 16:30:25 UTC,"Adding my $0.02, whatever it is worth.  I ran into this on a RamNode VPS.  downgrading to 4.15.0-20-generic made it boot again.  Attaching dmesg from that machine.
$ cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 58
model name	: Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz
stepping	: 9
microcode	: 0x1
cpu MHz		: 3400.022
cache size	: 4096 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx lm constant_tsc arch_perfmon nopl cpuid pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm pti fsgsbase smep xsaveopt ibpb ibrs stibp
bugs		: cpu_meltdown spectre_v1 spectre_v2
bogomips	: 6800.04
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:"
1779827,2018-07-10 12:20:20 UTC,"My bionic system has been fine until today, when I thought it wouldn't complete the boot at all.  It did in fact start after about 10 minutes. I tried again with the same result.   I am on the *24 kernel.  I tried *23 (from the boot list) but it made no difference.  Moving the mouse seemed to help."
1779827,2018-10-28 14:18:50 UTC,Hi I am on Carbon X1 2015 and  I was using ubuntu mate 16.04. The system suggested that I update to 18.04. I did that and went for run. I came back my screen was still there but the menu was gone. I forced a restart. I now get a screen for bios load then sda3_crypt. I put in my password and I get a blank screen with a blinking cursor that I cannot move and nothing else. I cannot recall what my kernel was. I just wanted tot ask if there has been any resolution on this issue...today is 2018-10-28.
1779827,2018-09-20 10:39:10 UTC,"Linux 4.15.0-34 fails to boot in VirtualBox.
4.4.0-135 boots OK, same everything else."
1779827,2018-09-04 11:48:44 UTC,"I have this exact issue with ANY kernel above 4.15.0-20. I tried over a dozen different versions higher and ONLY 4.15.0-20 works straight away. So I seriously doubt its an issue with just 4.15.0-24, at least on my machine."
1779827,2018-08-04 20:05:42 UTC,"Hello.
With kernel -29 my VM boots fast as usual. But another strange thing I'm discovering is that plymouth image still blinking over desktop. It happens from time to time. Not always, but regularly."
1779827,2018-08-04 15:15:29 UTC,The updated kernel doesn't fix the issue for me. I still need to have 3 or 4 usb sticks connected to the computer so it can boot correctly and not get stuck on a blank screen. Probably still an entropy issue.
1779827,2018-07-27 08:01:21 UTC,"I noticed similar effect with very recent (4.17) kernels. In 4.16.8 there were changes in random.c due to a security flaw. The function that detects ""having enough entropy"" is now strictly blocking. In the early boot phase this is bad on any machine without enough entropy sources. The kernel has 3 such sources: character devices, block devices and interrupts. On newer machines you can also have hardware random engines like in intel cores gen3+ (ivy bridge). This effect does not appear on computers with such a hw-rng. If you have one without hw-rng, and with a SSD only (they are not used for entropy gathering) and you don't mode your mouse, you are likely seeing this. The bad thing is, this kernel patch is actually necessary to prevent the system starting with insufficient safe random numbers. I applied a patch that reverts commit 43838a23a05fbd13e47d750d3dfd77001536dd33 in the kernel. After this change the startup worked like expected, but this is not a solution as it re-invents CVE-2018-1108. An idea would be to add a hw-rng like https://www.crowdsupply.com/13-37/infinite-noise-trng, but i did not test that so far. Check your cpu for the rdrand flag (lscpu). An entropy deamon like rngd helps only if you have entropy sources that it can use."
1779827,2018-07-26 05:13:52 UTC,This bug was fixed in the package linux - 4.15.0-29.31
1779827,2018-07-24 11:02:38 UTC,I mean CVE-2018-1108 ...
1779827,2018-07-24 11:01:52 UTC,"@Joseph Salisbury: I am confused. Looking at USN-3718-1 (https://usn.ubuntu.com/3718-1/) and USN-3718-2 (https://usn.ubuntu.com/3718-2/) it seems like CVE-1108 is fixed in Ubuntu 18.04 LTS for several linux kernel flavors (azure, gcp, hwe, kvm, oem and stock) and a subset for Ubuntu 16.04 LTS."
1779827,2018-07-20 15:39:45 UTC,This bug was fixed in the package linux - 4.15.0-29.31
1779827,2018-07-18 10:10:56 UTC,Same here with Lenovo Yoga S1 laptop :(.
1779827,2018-07-17 04:01:55 UTC,"This effected me after my first reboot in a couple weeks. I tried earlier kernels, still wouldn't boot.
Hangs on ""[ OK ] Started GNOME Display Manager. Dispatcher Service......tem changes.pp link was shut down...."""
1779827,2018-07-16 04:46:05 UTC,"Has to be the right shift key on my 18.04lts system, but I've always just used tapping the Esc key immediately after post until the grub menu comes up. I explained earlier how to remove the .24 kernel. But don't try to remove the one you are running at the time. Not sure what would happen then."
1779827,2018-07-10 11:32:24 UTC,Also confirm this bug at my DELL E4310. System boots very slowly. Reverting to *23 kernel fixed this problem.
1779827,2018-07-03 13:04:42 UTC,"https://wiki.ubuntu.com/Bugs/FindRightPackage
I was reqested to follow above, and I would really like to be help that why I trues to emphaize that the title of My incident is the last OK in the bootlist and where it hangs
More over it is one of the packages release on My laptop When opened it eight hours ago. These info must narrow Down to  be very few packages. I am still at work."
1779827,2018-07-04 15:21:14 UTC,Gratulations to Joseph Salisbury
1779827,2018-07-03 18:38:06 UTC,"Can anyone else confirm that booting into prior kernel versions does not prevent the bug?  If so, it probably is not a kernel bug."
1779827,2018-07-03 17:40:23 UTC,I started a kernel bisect between 4.15.0-23 and 4.15.0-24. The kernel bisect will require testing of about 7-10 test kernels.
1779827,2018-07-03 17:23:05 UTC,@ #12
1779827,2018-07-03 16:49:15 UTC,Bug does not affect Lenovo X250 or P51.
1779827,2018-07-03 16:17:35 UTC,"Also, are there any error messages, such as a kernel panic when the system wont boot?  If so, can you capture a screen shot or digital image?"
1779827,2018-07-03 16:13:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779827,2018-07-03 16:11:33 UTC,Are you able to boot if you select the prior kernel version(4.15.0-23) from the GRUB menu?
1779827,2018-07-03 15:56:25 UTC,"Same issue here, HP EliteBook 8440p, SSD disk."
1779827,2018-07-03 13:48:51 UTC,Lenovo X230 - exactly the same issue :-(
1779827,2018-07-03 13:37:02 UTC,"When I reinstall all these again they are all in and I get the notice ""set to manually installed."" for every single on of them.
To me this means that the main package that is dependent on all these ""set to manually installed."" is not installed.
If I uninstall VLC I get vlc-noc automatically. If I uninstall VLC the vlc-noc will uninstall, too.
If I then install vlc-noc it will notify me with ""set to manually installed.""
I am probably barking up the wrong tree, but it is just the way it comes to me right now."
1779827,2018-07-03 13:28:55 UTC,I faced this issue after performing an upgrade on my system at around 5 PM (IST). The symptoms were all the same as stated in the comments above.
1779827,2018-07-03 13:10:58 UTC,This is the result of  less /var/log/apt/history.log
1779827,2018-07-03 12:26:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1779827,2018-07-03 10:02:47 UTC,Here too on my Thinkpad T520.
1779827,2018-07-03 09:59:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779827,2018-07-03 09:51:22 UTC,I have this issue too.
1779827,2018-07-10 05:20:37 UTC,"This still looks like the getrandom() hang described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572. This was caused by the fix in the kernel for CVE-2018-1108. Two complementary fixes have been discussed in the Debian bug neither of which modify the kernel. The first is a change to the Plymouth package to avoid fontconfig generating uuids, which reportedly has the added bonus of speeding up boot compared to pre-CVE-fix times. The second is a change to randutils in the utils-linux package so they don't block on getrandom()."
1779827,2018-07-03 19:06:10 UTC,"For me, booting into previous kernel versions did not fix it. (DELL)"
1779827,2018-07-03 19:09:53 UTC,Me either.  The booting to prior kernel does not fix the issue.  Glad to help test but need some instructions.  Only have non-bootable system at this point.
1779827,2018-07-03 08:24:19 UTC,And this morning was July 3th 7:00 AM CEST
1779827,2018-07-03 19:24:00 UTC,"Agreed, I see the same thing.  Glad 0-23 boots, but 0-24 still hangs at the Ubuntu logo, five white dots, not animated."
1779827,2018-07-03 19:15:23 UTC,"This is interesting: I tried to boot linux-image-4.15.0-23-generic again and it did work now and after trying to boot linux-image-4.15.0-24-generic again, this did work as well and everything seems to be fine again..."
1779827,2018-07-04 14:20:31 UTC,Installing haveged didn't work for me (currently using lightdm as a workaround).
1779827,2018-07-04 13:16:24 UTC,Happy confirmed as well!  sudo apt install haveged fixes the issue.
1779827,2018-07-04 12:52:39 UTC,"I can confirm that installing the 'haveged' package solves the issue. If lack of entropy was the issue, it makes sense that tinkering with the the non-graphical terminal caused the boot to proceed where plain waiting didn't."
1779827,2018-07-04 11:34:42 UTC,According to this page
1779827,2018-07-04 10:32:02 UTC,"I confirm stopping the system loading on the ""Ubuntu"" board on the kernel 4.15.0-24,
the problem is probably related to the nvidia graphics card, my hardware:"
1779827,2018-07-04 09:49:58 UTC,"Same issue on the workstation, few hours spent to fix it by reinstalling gnome, gdm3, apparmor, loading previous kernel, switching to lightdm. Nothing helps, complete reinstall. Very frustrating, because need to return to configuration/installing apps for next the few weeks.
With Ubuntu you should get used to always have the drive with recent version near you in case of something go wrong. Because from my experience it is faster to reinstall than fix such issues."
1779827,2018-07-04 09:41:23 UTC,Have a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897631
1779827,2018-07-04 10:15:29 UTC,I'm not sure if my issue is related:
1779827,2018-07-04 08:27:39 UTC,"Hi,"
1779827,2018-07-04 07:40:32 UTC,"Here a screen dump of the packages, as required, that causes my incident, I guess!
It is from a T460 and was opened July 4th.
Please find dump attached."
1779827,2018-07-04 07:37:31 UTC,As no trick mentioned here worked ...
1779827,2018-07-04 06:47:02 UTC,Same problem here with T440s. I found a quick workaround. I put the computer in standby when the 5 dots of ubuntu logo are stuck. Then resume and the login screen appears.
1779827,2018-07-03 21:59:24 UTC,"The same issue on Lenovo M30-70.
I run Linux Mint 19 (cinnamon) parallelly on the same notebook. After upgrade to kernel 4.15.0-24 it hangs too. But here it boots with a prior kernel without problems and I turned off the upgrade to 4.15.0-24."
1779827,2018-07-03 21:22:18 UTC,"Ctrl-Alt-F1 repeatingly if the prompt dies.
Updated all third party apps to newest versions.
Took a look at the boot.log
Made me run these:
sudo apt-get install --reinstall apparmor
systemctl start nmbd.service
It boots on 24 kernel.
Very fast suspiciously fast. Boot.log looks good.
Until now it works."
1779827,2018-07-03 19:29:34 UTC,"Interesting thing happening...  I tried booting 0-23 success, then did shutdown -r now, and tried booting 0-24, as noted above just hangs.  Briefly hit power button tried to boot 0-23 again and now it doesn't boot..."
1779827,2018-07-04 08:55:34 UTC,"CTRL-ALT-F1 and check the boot sequence for what it using 2 minutes for.
Might be what I experienced:"
1779827,2018-07-04 14:43:00 UTC,Can folks affected by this bug test the following kernel:
1779828,2019-04-09 02:22:59 UTC,Filed Bug #1823822 to handle improving the check_for_upgrade resume logic.
1779828,2019-12-10 08:50:11 UTC,"Change abandoned by Trent Lloyd (<email address hidden>) on branch: master
Review: https://review.opendev.org/651105
Reason: This fix was already committed to the charm in https://review.opendev.org/#/c/685879/"
1779828,2019-12-03 15:01:50 UTC,"This bug seems to be in limbo; the fix for it is held at -1; Trent, please could you take a look at the review and Chris' (icey) comments re: being overtaken by events, and see if it is still current and that this bug still exists?  Thanks."
1779828,2019-04-09 06:16:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651105"
1779828,2018-10-25 00:09:44 UTC,"Hello Trent,
I also encountered the issue in my cluster. A simple modification of the check_for_upgrade() for bypassing problematic logic worked well for the servers."
1779828,2018-10-01 10:34:22 UTC,Related bug that also contributes to startup woes: bug 1783113
1779828,2018-08-02 05:50:53 UTC,"Some clarity for triage:
This makes it difficult to reboot ceph-osd nodes cleanly, and should probably be addressed with reasonable priority."
1779828,2018-07-09 07:59:35 UTC,The following is the log on which OSD is not yet mounted due to 120 second timeout of ceph-disk@service
1779828,2018-07-03 08:26:13 UTC,May also need to target bug to charm-ceph (the helpers)
1779828,2018-10-03 05:18:51 UTC,"Workaround for this issue by changing the owner of the underlying directory, using bind mounts to see through to it:"
1779828,2018-07-03 08:25:51 UTC,Reason for the timeout not working is possibly Bug #1664435 ?
1779831,2018-07-18 10:02:56 UTC,"Dear developers,"
1779831,2019-05-17 08:45:57 UTC,Hua-Sheng????
1779831,2019-05-27 12:20:32 UTC,"Hi Ivan, sorry for the late response. I did not aware of it (there were two reports related but I only replied the first one and forgot this one. Sorry.) What is the version of your gcc ? Also, what do you get when you compile IREGI manually in vendor/iregi/src by make ? Cheers, Hua-Sheng"
1779845,2019-09-27 09:03:13 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1779845,2019-06-06 11:57:45 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/663616"
1779845,2019-05-29 22:04:00 UTC,"This looks like an enhancement to the existing hiding hypervisor id code, rather than a defect in the existing support. As such, I'm setting this as a Wishlist bug."
1779845,2018-08-02 12:17:24 UTC,"I can confirm that bug, and the presented solution looks reasonable."
1779845,2019-06-06 05:36:02 UTC,"Reviewed:  https://review.opendev.org/579897
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ca543438e183b2bd97a08ef781ddeab8303354ed
Submitter: Zuul
Branch:    master"
1779845,2018-07-03 15:02:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/579897"
1779847,2018-07-03 15:30:19 UTC,"Hi,"
1779847,2018-07-03 16:17:05 UTC,"Additionally if running on cloud-init 18.3.6 or later please report the following on the commandline
$ python -c 'from cloudinit.util import get_linux_distro; print(get_linux_distro())'
# I see this on our centos 7 container
('centos', '7', 'x86_64')"
1779847,2018-07-03 17:12:54 UTC,"[root@myhost log]# python -c 'from cloudinit.util import get_linux_distro; print(get_linux_distro())'
('centos', '7', 'x86_64')"
1779847,2018-07-10 14:40:45 UTC,why is this still incomplete? do you guys need anything else?
1779847,2018-07-11 14:34:03 UTC,Possibly related error bug 1779847.
1779847,2018-07-11 21:47:47 UTC,might have a related fix for you (we landed it in tip July 9th) https://bugs.launchpad.net/cloud-init/+bug/1780481
1779864,2019-07-27 11:01:42 UTC,Closing this as it's a bug in wxWidgets.
1779864,2018-07-03 20:50:52 UTC,This becuase that is how windows works. For newer window's a so called manifest file is needed.
1779864,2018-07-06 15:11:14 UTC,"wxWidgets have added code to get the ""real"" Windows version, which is also backported to the 3.0 branch, so it will be resolved when a fixed wx is released and we upgrade to it."
1779868,2018-07-10 09:54:18 UTC,"Change abandoned by Margarita Shakhova (<email address hidden>) on branch: master
Review: https://review.openstack.org/563623"
1779872,2018-10-02 20:42:49 UTC,Still seems to be taking quite a bit longer than I'd expect (this is off an SSD)
1779872,2018-10-02 20:52:47 UTC,What kernel version are you using Stu?
1779872,2018-07-24 15:04:07 UTC,The new kernel fixes it for me!
1779872,2018-07-24 14:50:35 UTC,"The fix is available in the current kernel, according to this mailing-list thread: https://lists.ubuntu.com/archives/ubuntu-security-announce/2018-July/004503.html"
1779872,2018-07-11 12:45:47 UTC,Thanks for all testing done here.
1779872,2018-07-06 20:50:35 UTC,"@Guilherme, I can confirm that the proposed kernel version ""4.15.0-26"" fixes the issue."
1779872,2018-07-06 16:01:17 UTC,"Confirmed - I just testing on Ubuntu 18.04, prior boot times were 10+ minutes or until a couple keys were pressed on the keyboard. Boot times are now under 10 seconds."
1779872,2018-07-06 13:40:51 UTC,"This issue seems fixed in the new Ubuntu 18.04 kernel, version ""4.15.0-26"".
It's available now in the -proposed repo."
1779872,2018-07-04 22:48:44 UTC,Also getting the same long boot times since installing a system update 2 days ago. A fresh install didn't correct the issue.
1779872,2018-07-04 13:50:43 UTC,"user@machine:~$ sudo systemd-analyze blame
    7min 50.750s plymouth-quit-wait.service
    6min 17.955s snapd.seeded.service
         15.700s snapd.service
          6.253s NetworkManager-wait-online.service
          1.502s dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
          1.231s dev-loop0.device
          1.223s dev-loop1.device
          1.203s dev-loop2.device
          1.182s dev-loop3.device
           737ms fwupd.service
           265ms networkd-dispatcher.service
           253ms NetworkManager.service
           244ms plymouth-start.service
           230ms apparmor.service
           223ms udisks2.service
           199ms ModemManager.service
           190ms keyboard-setup.service
           182ms systemd-logind.service
           177ms systemd-journal-flush.service
           173ms accounts-daemon.service
           168ms systemd-udev-trigger.service
           149ms systemd-rfkill.service
           132ms speech-dispatcher.service
           127ms apport.service
           125ms systemd-timesyncd.service
           123ms avahi-daemon.service
           122ms systemd-resolved.service
           112ms bluetooth.service
           109ms packagekit.service
           109ms systemd-journald.service
           106ms grub-common.service
            99ms lvm2-pvscan@8:1.service
            95ms lvm2-monitor.service
            93ms wpa_supplicant.service
            89ms upower.service
            85ms thermald.service
            81ms networking.service
            81ms pppd-dns.service
lines 1-38"
1779872,2018-07-04 09:12:21 UTC,"This bug affected my Ubuntu 18.04 LTS system the first time I booted after upgrading the kernel. But the second and third times I booted, it no longer affected my Ubuntu."
1779872,2018-07-04 07:15:15 UTC,"I cofirm with 2 computers (laptop & desktop).
temporary, I boot on 4.15.0-20-generic (thanks to grub-customizer) and I've remove 4.15.0-24-generic with : sudo apt purge linux-image-4.15.0-24-generic linux-headers-4.15.0-24*"
1779872,2018-07-04 03:49:14 UTC,I confirm the same problem
1779872,2018-07-03 18:50:21 UTC,Here the same:
1779872,2018-07-03 18:17:34 UTC,"Same problem:
$ uname -a"
1779872,2018-07-03 18:05:30 UTC,"Same problem here, systemd-analyze blame returns:
10min 796ms plymouth-quit-wait.service
    8min 31.010s snapd.seeded.service"
1779872,2018-07-03 14:29:06 UTC,I had this problem this morning as well after a reboot following a kernel upgrade to 4.15.0-24-generic on an existing 18.04 fresh install.
1779872,2018-07-05 03:36:54 UTC,"Same problem but possible workaround: Following this advice (https://askubuntu.com/a/1052042/94570) that some process is waiting for random numbers, I pressed multiple keys and the startup process was terminated almost instantly.
Perhaps it works for you, too in the meantime."
1779872,2018-07-04 02:40:24 UTC,Same problem:
1779872,2018-07-24 15:32:21 UTC,Fixed for me as well in 4.15.0-29.
1779877,2018-07-03 14:49:34 UTC,As a workaround i am doing
1779877,2018-07-10 13:22:43 UTC,"I am marking this a Medium since there is a workaround. I am also marking this as Incomplete as at this stage, I am not sure about what can be done on Juju side to resolve this."
1779877,2018-07-11 08:56:00 UTC,"We've certainly seen ""unable to resolve host"" before, but I haven't seen: ""Connection timed out"".
That sounds more like we have an incorrect dns setup that is causing the container to try to contact your MAAS DNS server, but is unable to route packets there."
1779882,2018-07-04 10:51:19 UTC,Deleting the port from admin user doesn't cause those messages and the operation takes around 5 seconds instead of 35.
1779882,2018-07-04 10:55:53 UTC,Thank you.
1779882,2018-07-04 11:41:16 UTC,"sorry folks, I disagree with the importance, I just checked and I can confirm."
1779882,2018-07-04 12:19:05 UTC,"| You mentioned that create 1K ""free"" port, just db records, right?
Yes, not bound.
"
1779882,2018-07-05 11:01:19 UTC,"I agree with @ajo here, 35 seconds is unacceptable."
1779882,2019-02-15 17:55:30 UTC,Hello:
1779882,2019-02-15 18:01:39 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/637235"
1779882,2019-02-15 18:07:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637237"
1779882,2019-02-20 11:18:10 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/637235
Reason: Abandoned in favor of a more generic modification in OSclient to retrieve an element using the ID or the name. In the second case, a ""list"" (GET -> get_objects) command with filters (name=id_or_name) will be sent instead of a generic ""list"" command, to reduce the number of elements retrieved."
1779882,2019-02-20 11:18:17 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/637237
Reason: Abandoned in favor of a more generic modification in OSclient to retrieve an element using the ID or the name. In the second case, a ""list"" (GET -> get_objects) command with filters (name=id_or_name) will be sent instead of a generic ""list"" command, to reduce the number of elements retrieved."
1779890,2020-11-20 14:32:05 UTC,"> It's being D-Bus activated by things early in the startup of the
> session. By disabling tracker or whatever you are stopping that D-Bus
> activation.
"
1779890,2020-11-17 09:26:38 UTC,"On Tue, Nov 17, 2020 at 07:50:20AM -0000, Julien Blanc wrote:

> Same issue here.
>
> gvfsd is started by tracker-miner-fs. Disabling it made it work (note
> that i also made the /etc/pam/systemd-user pam_sss change), ie gvfsd now
> correctly has access to the kerberos token.
>
> I'm wondering why gvfsd is started by systemd-user and not gnome-
> session. Changing that may be an acceptable workaround until a better
> solution is found.
"
1779890,2020-11-17 07:50:20 UTC,Same issue here.
1779890,2020-11-03 10:20:04 UTC,"I think maybe sssd needs to learn how to set the environment in ""session"" mode. I did ask some people at Canonical who know about this project, hopefully they will have some advice soon. :)"
1779890,2020-10-29 14:32:08 UTC," I do not have tracker-miner-fs.service at all. My instance of gvfsd is started by either ibus-daemon, or ""systemd --user"". Please see the controversy at https://gitlab.gnome.org/GNOME/gvfs/-/issues/481#note_948506"
1779890,2020-11-03 05:08:49 UTC,"@laney: I have disabled all my workarounds and placed ""session optional pam_sss.so"" just before ""session optional pam_systemd.so"" in /etc/pam.d/systemd-user on my Ubuntu 18.04.5 system. Checking
""journalctl --user"" for gfvs-daemon entries:"
1779890,2020-10-26 17:23:59 UTC,"The upstream determined that gvfsd as a systemd user session is starting too early in Ubuntu, before the desktop enviroment variables are set. Specifically, KRB5CCNAME env var is missing at the time gvfsd is started, causing this bug. See the detailed report at ttps://gitlab.gnome.org/GNOME/gvfs/-/issues/481"
1779890,2020-10-29 11:29:04 UTC,"The upstream bug got reopened now, could you try disabling the tracker service and see if it resolves the issue for you?"
1779890,2018-08-31 07:55:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779890,2019-09-02 20:13:20 UTC,Happens on Ubuntu 19.04 too.
1779890,2020-11-02 17:34:13 UTC,"I think anything which causes gvfs to start ""early enough"" (before gnome-session has a chance to upload the environment to systemd) will trigger this problem."
1779890,2020-05-28 18:15:34 UTC,The problem persists in Ubuntu 20.04 as well.
1779890,2020-06-03 20:53:38 UTC,Thanks for reporting the issue upstream
1779890,2019-12-23 12:40:31 UTC,"As far as I know this problem comes from ubuntu 12.04 and still not resolved. Kerberos now works in ubuntu 18.04.
This is ubuntu specific bug. Nautilus in Centos 7.x and 8 works fine with kerberos"
1779893,2018-10-09 14:08:13 UTC,"Just for the records: I upgraded my Ubuntu to 18.04.1, running the kernel 4.15.0-36-generic, and the problem disappeared."
1779893,2018-07-28 13:08:56 UTC,"I am sorry that I could not contribute in the way described above. Any chance that my request can be processed anyway? I see that there is no activity on this, and at some point this report will expire. Just to provide a little update: the version 4.4.0-131 does not improve the problem. I am convinced that it has to do with the audio, as Oleksii described.
Thanks in advance."
1779893,2018-08-20 13:37:22 UTC,4.4.0-133 also didn't fixed the issue.
1779893,2018-07-04 14:31:45 UTC,"Same issue.
Works OK on 4.4.0-127-generic but freezes on 128/130."
1779893,2018-07-04 21:04:00 UTC,Thanks for your feedback.
1779893,2018-07-03 21:05:47 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1779893,2018-07-03 16:00:08 UTC,This change was made by a bot.
1779900,2019-02-26 13:43:31 UTC,Is this still an issue?
1779905,2018-07-09 02:34:51 UTC,We can keep this bug ID but you'll need to reword the bug title and description to encompass the actual problem. The initial problem you reported is invalid - that was the jack module not working. Because the jack module wasn't installed.
1779905,2018-07-04 01:59:58 UTC,Did you remember to install it first?
1779905,2018-07-04 19:30:12 UTC,"Sorry, I forget to mention the output of that:"
1779905,2018-07-05 02:17:09 UTC,"Hmm, that's not right. The command:
  sudo apt install pulseaudio-module-jack
completes successfully on 16.04 for me."
1779905,2018-07-05 02:17:57 UTC,Also remember to run this first:
1779905,2018-07-05 15:37:51 UTC,"> sudo apt update
"
1779905,2018-07-06 02:31:06 UTC,"Thanks for the listing. That shows you are missing pulseaudio-module-jack, making this bug invalid."
1779905,2018-07-06 15:47:39 UTC,"> That shows you are missing pulseaudio-module-jack, making this bug invalid.
"
1779905,2018-07-03 16:52:28 UTC,Commands I used to load modules:
1779905,2018-07-09 19:35:34 UTC,"Thank you, I appreciate being able to keep all the history for this bug. I've reworded the title, description, and set the status back to new."
1779908,2018-07-06 07:48:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779912,2018-07-03 17:56:19 UTC,It would be nice if it could be backported to Ubuntu 16.04 LTS. Don't know how feasible this is...
1779912,2018-07-03 23:55:04 UTC,*** This is an automated message ***
1779912,2018-07-04 06:59:47 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1779912,2018-07-04 18:34:11 UTC,"Yes, the 18.04 part is fixed. Do I need to close this ticket and create a new ticket to request backport to 16.04?"
1779912,2018-07-05 07:34:08 UTC,">Yes, the 18.04 part is fixed.
"
1779917,2018-07-03 20:28:40 UTC,"In addition, the text should also refer to the fact that a username *must* be included, using a particular syntax (user@hostname). This may be a challenge. Suggestion: add another prompt."
1779923,2018-08-07 14:02:28 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1779923,2018-08-23 21:59:21 UTC,This bug was fixed in the package linux - 3.13.0-157.207
1779923,2018-08-23 19:23:06 UTC,This bug was fixed in the package linux - 4.4.0-134.160
1779923,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1779923,2018-08-21 16:19:47 UTC,@jannh you can ignore the request in comment #12 to verify the fixes in the -proposed kernels. Thanks again for bringing this to our attention.
1779923,2018-08-21 16:17:43 UTC,I've verified the fix by testing the following kernels:
1779923,2018-08-21 09:13:36 UTC,"Hi @jannh,"
1779923,2018-08-03 18:03:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1779923,2018-08-02 16:03:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1779923,2018-07-16 18:56:45 UTC,I don't think the Security or Foundations teams plan to make any changes in Whoopsie so I'm marking these tasks as invalid.
1779923,2018-07-16 18:54:26 UTC,Fix submitted for the Ubuntu kernel: https://lists.ubuntu.com/archives/kernel-team/2018-July/093863.html
1779923,2018-07-13 21:56:46 UTC,Thanks Jann!
1779923,2018-07-13 21:17:42 UTC,Our bugtracker entry is public now: https://bugs.chromium.org/p/project-zero/issues/detail?id=1611
1779923,2018-07-09 20:05:28 UTC,"So far, I have only notified <email address hidden> and you. However, our policy is to make issue reports public soon after a patch has been released, so I'm planning to drop the view restriction on our bugtracker entry on Friday."
1779923,2018-07-09 19:32:55 UTC,"Hello Jann, have you taken steps to publicize this issue further? I think we'd like to keep the PoC secret until our kernels can include the upstream fix but if this PoC is currently visible elsewhere then it serves no purpose to keep this bug closed any longer."
1779923,2018-07-06 13:32:48 UTC,Hi Jann - thanks for reporting this - I noticed the commit earlier today and have been in the process of testing it here against your PoC's above (still waiting on builds to complete to report final results which I hope to do soon).
1779923,2018-07-06 13:16:09 UTC,This is now fixed upstream in Linus' tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0fa3ecd87848c9c93c2c828ef4c3a8ca36ce46c7
1779930,2018-09-12 09:59:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779934,2020-07-15 15:31:30 UTC,Can you please let us know if this is still happening with the current release? It's been a few years since you submitted this. Sorry for not replying sooner!
1779934,2020-07-15 16:33:24 UTC,"Hi,"
1779938,2019-06-25 18:38:42 UTC,I like it.
1779938,2019-07-11 18:35:26 UTC,"Echoing others: the current patch unfortunately doesn't resolve the issue as stated, because the expected command-W accelerator is not assigned. With command-Q reassigned there is currently no shortcut to close a window."
1779938,2019-07-11 19:57:10 UTC,"The Assign Associations dialog will be getting the escape key added as the exit key, so it shouldn't need the cmd shortcut key added to it."
1779938,2019-07-11 20:59:06 UTC,"Even if escape is added to that window, cmd-w is the default for closing pretty much any window on macOS. It should also be closing any window in KiCad on macOS."
1779938,2019-07-19 22:26:05 UTC,"@Seth, did you mean for the shortcut to work on every OS? It is able to close KiCad on Linux, and that is not a usual shortcut for closing windows. Also, it should be added to the list of invalid hotkeys. I can assign a tool to use that combination (or at least ctrl-Q on Linux, which is how it is mapped) and that will then override the close function."
1779938,2019-07-20 00:15:14 UTC,"@Seth, I never noticed those key combinations on Linux before, but now that you mention it I do see other programs using them. I also note that your current patch only pushed the ctrl-Q behavior and not the ctrl-W behavior."
1779938,2019-07-20 19:32:22 UTC,"Just my two cents on linux UI shortcuts: the biggest issue is that they are not consistent between programs, they sometimes work and sometimes don't the way you expect and it's a big plus on macOS in my opinion. So while you're at it, why not make ctrl-w on linux do the same as cmd-w on macOS: close every window, including preferences and simulation etc. (actual dialogs are not really windows I guess)."
1779938,2019-08-02 22:00:50 UTC,This got fixed under a different bug report.
1779938,2019-06-25 16:15:15 UTC,"@Seth, this is much better than the current situation. I think technically ""Quit"" shouldn't be in the File menu on Mac and Cmd-W should be bound to the Close action."
1779938,2019-07-19 22:47:48 UTC,Yes. Ctrl-W should close windows on Linux and Ctrl-q should quit.
1779938,2019-06-25 04:53:07 UTC,"Fixed in revision 98124e68c7485d897bb7ed253fff578914b1fd79
https://git.launchpad.net/kicad/patch/?id=98124e68c7485d897bb7ed253fff578914b1fd79"
1779938,2018-07-04 23:59:00 UTC,"Application: kicad
Version: (5.0.0-rc3-dev-2-g101b68b), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
Platform: Mac OS X (Darwin 17.6.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.61.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.43.0
    Compiler: Clang 7.3.0 with C++ ABI 1002"
1779938,2019-06-23 23:35:21 UTC,This will probably handled by https://bugs.launchpad.net/kicad/+bug/1826649 anyway?
1779938,2019-06-25 04:52:34 UTC,This is one of the odd edges that catch folks out when they're using the program.  They figure it out but it doesn't feel polished.
1779938,2018-07-04 23:36:06 UTC,"Ah, sorry. Kicad 5.0.0-rc3"
1779938,2018-09-03 04:17:34 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1779938,2018-09-03 10:36:57 UTC,There is also a list of standard shortcuts
1779938,2018-07-03 21:29:59 UTC,Please add version info
1779938,2019-06-22 21:39:32 UTC,"@Jeff, what if we test for KiFace.IsSingle()?"
1779938,2019-06-23 09:38:31 UTC,"@Seth, we could.  I suspect we'd annoy most existing users, but if we believe our user base it growing fast enough it still might be the correct decision...."
1779938,2019-06-23 21:58:27 UTC,"If Eeschema etc. are run a single application, Cmd-q is ok as is (more expected though would be cmd-q quits application, cmd-w closes window for current open file when also opening multiple files was possible).
If you can detect the single application state, closing e.g. eeschema with cmd-w and closing KiCad with cmd-q. I think it won't take a long time getting used to it even for existing users as it is normal behavior for everything else on macOS, so maybe it fixes their existing annoyance ;). At the moment you have a two step action to quit kiCad (change to the main window and use cmd-q or use cmd-q twice) and can replace it with a one-step way to quit."
1779938,2019-06-22 20:13:00 UTC,"Pcbnew, Eeschema, LibEdit and ModEdit all used to be separate applications.  Pcbnew and Eeschema can still be run separately today.  This makes the water murky enough that I'm not really prepared to change the Cmd-Q / Cmd-W behaviour."
1779939,2018-07-16 01:43:40 UTC,Do you have any idea what subiquity is doing to cause this? It could just as easily be a snapcraft bug as far as I can tell.
1779939,2018-07-16 16:48:30 UTC,"It seems to be the structure of snapcraft.yaml in subiquity that triggers it (though it might be a snapcraft bug). My suspicion is that the subiquity part has an implicit dependency on something (or an initialization step) provided by one of the other parts. This is my first exposure to snapcraft, so I'm afraid I'm not much use."
1779939,2018-07-16 21:30:20 UTC,"I must admit I always run ""snapcraft clean; snapcraft snap"" :("
1779942,2018-07-11 09:33:56 UTC,PackageKit should not have attempted to do stuff in that situation I think
1779942,2019-12-15 20:04:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779943,2018-09-11 05:59:54 UTC,"Reviewed:  https://review.opencontrail.org/46090
Committed: http://github.com/Juniper/puppet-contrail/commit/b5ec14743d6c13cf847f277f1d28a404931c7b0e
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1779943,2018-07-03 21:14:55 UTC,rpm list from contrail-config node
1779943,2018-07-04 01:01:05 UTC,"From: Anantharamu Suryanarayana <email address hidden>
Date: Tuesday, July 3, 2018 at 5:54 PM
To: Shivayogi Ugaji <email address hidden>, Nagendra Maynattamai <email address hidden>, ""Shaju V.K"" <email address hidden>, Sanae El Yousfi <email address hidden>
Cc: Jeba Paulaiyan <email address hidden>, Abhay Joshi <email address hidden>, Nikhil Bansal <email address hidden>
Subject: Re: upgrade error"
1779943,2018-07-10 00:29:16 UTC,Need access to setup to debug it further. It was resolved by restarting config services so looks like some timing issue during upgrade
1779943,2018-09-10 13:32:52 UTC,"Review in progress for https://review.opencontrail.org/46090
Submitter: alexey-mr (<email address hidden>)"
1779943,2018-09-14 16:52:45 UTC,"Hi, Jeba,
https://bugs.launchpad.net/juniperopenstack/+bug/1779943
it looks that it is applicable only for 4.1 ..
maybe it is worth to remove others"
1779955,2018-07-12 20:24:17 UTC,"Oh, yes, I see -- it's mmapping the file specifically in order to write the data to the file system. Yes, I agree that's a reasonable thing to do."
1779955,2018-07-06 12:24:22 UTC,"The problem here is not the mmap(), it is that you are mapping it as only PROT_WRITE and not also PROT_READ. With the native kernel, syscalls which only write to a buffer and do not read from it (like read(2)) only require write permissions on that memory. QEMU's implementation requires both write and read permission."
1779955,2018-07-12 19:26:01 UTC,Thanks Peter for your information.
1779962,2018-07-04 00:22:20 UTC,"The attachment ""Changes the syscalls to use the 32-bit variants."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1779962,2018-07-17 10:15:27 UTC,Thanks for tracking this down Sree - I've been hitting this for quite some time but only on ARM for some reason. Your patch also works for me on nfs-utils 2.3.2.
1779962,2018-07-17 10:16:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779962,2018-07-17 15:19:37 UTC,"Glad to know that helped. I was using the Odroid kernel (not the Ubuntu one), so I was not sure the problem manifests elsewhere. It doesn't on Debian (on the aarch64 kernel), for example."
1779962,2018-07-17 19:25:38 UTC,Here is the patch I'm about to propose to upstream.
1779962,2018-07-17 22:37:50 UTC,"Steve, I tested that patch on 1.3.4 and it works for me. Thanks!"
1779962,2018-07-18 14:20:41 UTC,"Sree, Thank you!"
1779962,2018-07-18 15:41:28 UTC,The upstream patch
1779962,2018-10-16 15:17:24 UTC,This bug was fixed in the package nfs-utils - 1:1.3.4-2.2ubuntu3
1779962,2019-07-09 14:24:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779962,2019-07-10 21:15:36 UTC,"I assume I spotted the exact same error as the reporter using Ubuntu 18.04 on Odroid XU4. For me it fails when using FreeIPA (with high UIDs/GIDs) and Kerberized NFS4. When applying the patch the problem goes away, but so far I have not give it more testing than that. Considering the nature of the patch the risk of side effects seem small though :-)"
1779969,2018-07-20 07:18:13 UTC,This bug is fixed in PHPMyAdmin Release 4.8.2 and would be resolved in updating the package.
1779969,2018-07-20 07:18:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1779971,2019-11-27 12:30:18 UTC,https://salsa.debian.org/phpmyadmin-team/phpmyadmin/issues/31
1779971,2018-07-04 00:49:26 UTC,"As a side note, in a 16.04>18.04 upgrade path, it can make a server admin loose a lot of time figuring out what is going on with file uploads."
1779978,2018-07-04 04:11:41 UTC,"And if I use legacy option ""enable_service q-fwaas-v1"" in local.conf, still face ""PENDING_CREATE"" issue, I found config conflict in l3_agent.ini, there are two agent section, but have different values, [AGENT] and [agent]"
1779978,2018-07-17 09:58:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583186"
1780020,2018-10-09 14:13:12 UTC,"Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
Processing triggers for linux-image-4.15.0-24-generic (4.15.0-24.26) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
/usr/share/initramfs-tools/hooks/framebuffer: 141: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
/usr/share/initramfs-tools/hooks/framebuffer: 65: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
E: /usr/share/initramfs-tools/hooks/framebuffer failed with return 2.
/usr/sbin/mkinitramfs: 181: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/update-initramfs: 165: /usr/sbin/update-initramfs: Cannot fork
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
dpkg: error processing package linux-image-4.15.0-24-generic (--configure):
 installed linux-image-4.15.0-24-generic package post-installation script subprocess returned error exit status 1"
1780030,2018-07-27 02:32:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586394"
1780030,2018-12-25 10:15:10 UTC,"Change abandoned by zhurong (<email address hidden>) on branch: master
Review: https://review.openstack.org/586394"
1780035,2018-07-04 07:59:36 UTC,A sample OOPS ID is OOPS-e1b93f3fca787989722a35f75101e32b.
1780046,2018-09-29 07:12:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780058,2018-07-04 12:58:57 UTC,apport information
1780058,2018-07-04 12:58:58 UTC,apport information
1780058,2018-07-04 12:07:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1780058,2018-07-04 12:59:00 UTC,apport information
1780058,2018-07-04 13:00:32 UTC,Now I learned the right way to reporting bugs. Thanks.
1780058,2019-04-18 15:57:10 UTC,Thank you for your bug report. Could you add a file example to the bug?
1780058,2019-04-24 01:21:45 UTC,apport information
1780058,2019-04-24 01:21:47 UTC,apport information
1780058,2019-04-24 01:21:49 UTC,apport information
1780058,2019-04-24 01:35:55 UTC,Sorry now I could only trigger bug that both extract method(open then extract and 'Extract Here') did something wrong to filename. Attachment is a sample zip file. `unar` will guess the right filename encoding.
1780058,2019-06-23 04:19:23 UTC,[Expired for file-roller (Ubuntu) because there has been no activity for 60 days.]
1780061,2018-07-04 08:50:54 UTC,"Just for the record, it works with english locale of course."
1780061,2018-08-23 06:40:02 UTC,"Confirmed : does not work with french locale either.
Running ""LANG=en_US.UTF-8 LANGUAGE=en_US snapcraft cleanbuild"" works."
1780061,2019-01-03 15:32:23 UTC,Does not work with portuguese locale either.
1780071,2020-04-29 13:39:32 UTC,I can confirm that the issue is still there in Ubuntu 18.04.4 LTS.
1780071,2019-05-03 22:31:03 UTC,"An upload of landscape-client to disco-proposed has been rejected from the upload queue for the following reason: ""Wrong solution for the reported symptom.  locale should be set globally in update-motd.""."
1780071,2019-05-02 21:32:48 UTC,"Garbage in, barbage out. I think opening things and reading as utf-8 is good. For added resilience, one has to also espace unicode encoding errors too, and replace them with anything readable. I.e. one may choose to read in binary, and then decode as utf-8 with any errors replaced, ie.:"
1780071,2019-04-22 07:14:26 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu8
1780071,2018-07-04 20:36:15 UTC,"I tested and the patch #3 works correctly, thanks."
1780071,2018-07-04 19:47:28 UTC,https://github.com/CanonicalLtd/landscape-client/pull/50
1780071,2018-07-04 12:39:47 UTC,Thank you for reporting this bug. We believe it is an actual issue and will look into having it fixed.
1780071,2019-04-20 17:59:09 UTC,"Uploaded to Bionic, Cosmic, Disco, Eoan. Unsubscribing sponsors."
1780075,2018-07-19 14:58:35 UTC,https://bugs.launchpad.net/terminator/+bug/1758564
1780075,2018-09-11 11:14:24 UTC,"Hello, I am experiencing the same effect. I am NOT using Ubuntu, I am running Fedora28 Mate desktop with terminator-1.91-4.fc28.
I have enabled the Plugin 'CustomCommandsMenu'
Added a new custom command (inside 'CustomCommandsMenu' preferences) in my case ssh <USER>@192.168.xxx.xxx
No reaction"
1780082,2018-07-10 15:11:18 UTC,maybe Dan Sneddon or Tim Rozet can help
1780082,2021-02-17 17:08:40 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1780092,2019-03-22 21:15:11 UTC,This is as far as I've gotten with it..
1780092,2019-03-22 20:34:33 UTC,The documentation for building trove images is garbage.  How long has trove been an Openstack project?
1780092,2019-03-24 17:44:20 UTC,"Tyler,"
1780092,2019-02-26 04:32:50 UTC,I hear you.  I'm working through some of this right now and will submit a set of working defaults that people can at least start with..
1780098,2018-07-04 21:43:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780098,2018-07-07 20:00:05 UTC,This does not occur with the version of grub-xen on 18.04
1780098,2018-07-10 16:47:22 UTC,The relevant change that makes 18.04's version work where 16.04's doesn't seems to be 15aee573d2312ebf4aab53d07d3d30eccf1484f9 upstream.
1780098,2018-07-10 19:19:26 UTC,Can confirm that upgrading the dom0 grub and building a new pvgrub solved the problem. I have a clone of the grub git that I'm building manually on Debian Jessie.
1780098,2018-07-10 20:25:14 UTC,"The attachment ""fix-invalid-payload-size"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1780098,2018-07-24 11:37:06 UTC,Just installed 4.4.0-131.157 and it seems like it is working again
1780098,2018-07-25 00:49:57 UTC,"I also just installed 4.4.0-131.157 over 4.4.0-128 (that I reinstalled that and booted on it to avoid the 4.4.0-130 bug) and it seems like it is working again in a Xen VM with PVGrub. My issue was identical, but with a different error message (bad memory access error in the very first initrd boot phase also pointing to a badly built initrd.img)."
1780098,2018-07-25 14:52:08 UTC,"Btw, while cleaning up the systems, I now found that in the /boot folder of one of the 2 systems that I upgraded and both (=all) failed with 4.4.0-130, I also saw a strange file named ""initrd.img-4.4.0-139"" that got installed at exactly same time than ""initrd.img-4.4.0-130-generic"" and other normal 4.4.0-130 files. Maybe that helps find the issue ?"
1780123,2018-09-12 23:43:40 UTC,"Actually, using a progress dialog is probably a good idea, but I'm afraid it will take some time to show up. What I was proposing was rather an instant feedback that the double-click (or Enter key) on the file has really launched the appropriate exe. Thus the hourglass cursor idea, like in windows explorer for example when an exe is launched."
1780123,2018-09-12 12:20:44 UTC,"I remember that this was created at GerberView because of a big file
https://bugs.launchpad.net/kicad/+bug/1745203"
1780123,2018-07-04 16:03:53 UTC,A progress dialog would be even nicer....
1780138,2018-11-26 09:31:50 UTC,"Related to this problem, upstream libvirt has merged this patch:"
1780138,2019-06-06 13:55:43 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/663677"
1780138,2019-06-13 06:04:47 UTC,"Reviewed:  https://review.opendev.org/663011
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=527c452a6fc05a316eb8121796f761af97522772
Submitter: Zuul
Branch:    master"
1780138,2019-06-15 00:11:50 UTC,"Reviewed:  https://review.opendev.org/663677
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=db40cc44cbad32353510819c0aee1d0a3c9e4357
Submitter: Zuul
Branch:    stable/stein"
1780138,2018-11-26 15:33:22 UTC,"To expand on comment#1, from libvirt v4.7.0 onwards, thanks to this
libvirt commit[*] libvirt will ensure that the default machine type for
""x86"" will keep as 'pc', *if* it is available.  Then the assumption
(that ""guest.os_mach_type is None"" means, then you have 'pc' machine
type) we have today Nova's libvirt driver will hold.  However, relying
on such assumptions is still not good."
1780139,2018-10-31 12:47:42 UTC,"We can't fix that for tripleo as it requires neutron server fixes for SIGHUP processing, so marked it won't fix. Logrotate configs had been switched from sending SIGHUP to using copytruncate, so tripleo is not affected with this anymore."
1780139,2018-10-08 18:13:59 UTC,This issue was fixed in the openstack/puppet-tripleo 10.0.0 release.
1780139,2018-10-05 12:48:13 UTC,Addressed by https://review.openstack.org/#/q/Ibdad7859a389d0ff37bbf7bfd9f4c521a05a5ea1
1780139,2018-10-03 11:48:57 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/606864
Reason: implementation falls back to copytruncate making this not needed any more"
1780139,2018-10-03 11:48:49 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/606908
Reason: implementation falls back to copytruncate making this not needed any more"
1780139,2020-03-05 22:54:14 UTC,"Reviewed:  https://review.opendev.org/708570
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=13f2e1344a697c8c7adf795100e3e0ee92bdc43f
Submitter: Zuul
Branch:    stable/train"
1780139,2018-10-03 09:45:57 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/604708
Reason: not needed any more as we fallback to copytruncate"
1780139,2018-10-01 15:41:26 UTC,"Recapping some other investigations (downstream https://bugzilla.redhat.com/show_bug.cgi?id=1631335 has some details too), in general neutron-server does not handle SIGHUP properly.
While it may still reply to API requests after SIGHUP, service is degraded (or not available). Two typical situations after some time (to allow childs to exit):
* No child process, main process in a 100% CPU loop ""wait4(0, 0x7ffd52e322a4, WNOHANG, NULL) = -1 ECHILD (No child processes)""
* wsgi workerds are killed but not started (rpc workers restart properly)"
1780139,2018-10-01 09:03:33 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/606908"
1780139,2020-01-23 12:48:24 UTC,"On the Neutron side, I plan to work again in this, as I found that once killed, a RPC worker is not respawned (current devstack master)"
1780139,2018-09-30 19:30:53 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/606864"
1780139,2018-10-03 11:48:41 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/601544
Reason: implementation falls back to copytruncate making this not needed any more"
1780139,2020-01-31 15:45:54 UTC,"Confirming, the ProcessLauncher children array in olso.service only shows the WSGI PIDs"
1780139,2020-02-24 17:26:58 UTC,"Reviewed:  https://review.opendev.org/708571
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4916bbc5f3c3727a7f0ad822ec6c140b54e51271
Submitter: Zuul
Branch:    stable/stein"
1780139,2020-02-07 13:57:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/706514"
1780139,2020-02-19 01:13:40 UTC,"Reviewed:  https://review.opendev.org/706514
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=13aa00026f768642f385259ba7ccddcfdad3c75f
Submitter: Zuul
Branch:    master"
1780139,2020-02-19 07:58:51 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/708570"
1780139,2020-02-19 07:59:05 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/708571"
1780139,2020-02-19 07:59:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/708572"
1780139,2020-02-19 08:37:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/708576"
1780139,2020-02-21 16:40:19 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1780139,2020-02-24 17:27:22 UTC,"Reviewed:  https://review.opendev.org/708572
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dc68b69fc04283746518692886f386f034afc8f0
Submitter: Zuul
Branch:    stable/rocky"
1780139,2020-02-24 17:27:38 UTC,"Reviewed:  https://review.opendev.org/708576
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=66d45b8e91bf1263c82e636bd21498bf6de552bc
Submitter: Zuul
Branch:    stable/queens"
1780139,2020-02-28 15:29:18 UTC,This issue was fixed in the openstack/neutron 13.0.7 release.
1780139,2018-09-30 08:18:46 UTC,"Reviewed:  https://review.openstack.org/596275
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=d37c74d6382690a05ba3ca10edd7f2acb0fbbb2e
Submitter: Zuul
Branch:    master"
1780139,2020-02-05 16:21:41 UTC,Finally found the root cause here!
1780139,2018-09-28 13:51:04 UTC,"+Bogdan, shall we close this LP for the tripleo part?"
1780139,2018-09-20 14:16:23 UTC,Relevant issue in tripleo periodic jobs: https://bugs.launchpad.net/tripleo/+bug/1793482
1780139,2018-09-26 08:03:22 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605349"
1780139,2018-09-28 07:44:02 UTC,"Reviewed:  https://review.openstack.org/605349
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=78e0205b936ed069a6e1866165c17d5a3d4ee1be
Submitter: Zuul
Branch:    stable/rocky"
1780139,2018-10-03 09:47:41 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/605348
Reason: not needed any more as we fallback to copytruncate"
1780139,2018-07-10 13:36:07 UTC,Adding a small update for context in the tripleo scenario.
1780139,2018-07-12 19:18:57 UTC,This can be demonstrated by simply sending a SIGHUP to the container or the root neutron-server process. Apparently fixing this is non-trivial in neutron. I've added tripleo to the bug as the more likely near-term solution would to be alter the logrotate behavior for neutron.
1780139,2018-07-13 14:09:51 UTC,related bug with a long beard https://bugs.launchpad.net/oslo-incubator/+bug/1276694
1780139,2018-07-13 19:00:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/582661"
1780139,2018-07-28 17:19:44 UTC,Is that possible to fix it by moving neutron-server under apache httpd using wsgi? can it fix the issues?
1780139,2018-08-06 11:20:29 UTC,"Yao ning, yeah, seems to me like this is something where  using httpd would help."
1780139,2018-08-07 14:50:39 UTC,"Testing on devstack master (stacked around July 31), neutron-server does not react well to SIGHUP, with logs looking similar, like:
WARNING oslo_service.service [-] pid 17122 not in child list"
1780139,2018-08-08 14:04:26 UTC,"On a fresh restack (CentOS 7.5), I managed to reproduce the wait4/ECHILD loop issue on devstack."
1780139,2018-08-24 10:14:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/596274"
1780139,2018-08-24 10:28:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/596275"
1780139,2018-08-24 10:44:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/596277"
1780139,2018-10-03 09:46:30 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/601558
Reason: not needed any more as we fallback to copytruncate"
1780139,2018-09-11 10:44:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/601544"
1780139,2018-09-26 06:37:37 UTC,"Reviewed:  https://review.openstack.org/596274
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=2b1afc0483f849046b404099944653015fc11a04
Submitter: Zuul
Branch:    master"
1780139,2018-09-25 12:55:20 UTC,"Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master
Review: https://review.openstack.org/596274
Reason: Purging the gate to free up resources and address the timeout issues"
1780139,2018-08-24 15:48:51 UTC,"Change abandoned by Brent Eagles (<email address hidden>) on branch: master
Review: https://review.openstack.org/582661
Reason: in favor of https://review.openstack.org/#/c/596275/"
1780139,2018-09-23 21:51:07 UTC,"Reviewed:  https://review.openstack.org/604006
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=fc31a1c649cca06d0340a15a55339757ff002775
Submitter: Zuul
Branch:    stable/rocky"
1780139,2018-09-20 17:26:04 UTC,Appears to have been duplicated in neutron with https://bugs.launchpad.net/neutron/+bug/1793482
1780139,2018-09-24 09:26:56 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/604708"
1780139,2018-09-20 07:47:46 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604006"
1780139,2018-09-18 15:30:23 UTC,"Reviewed:  https://review.openstack.org/596277
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=305445bac6ccf2cb491f451412035f08aa2928ba
Submitter: Zuul
Branch:    master"
1780139,2018-09-11 12:08:15 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/601558"
1780139,2018-09-11 11:57:00 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/601555"
1780139,2018-10-03 09:47:52 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/601555
Reason: not needed any more as we fallback to copytruncate"
1780139,2018-09-26 08:02:59 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/605348"
1780145,2018-07-04 17:57:53 UTC,"StacktraceTop:
 XAddExtension (dpy=dpy@entry=0x563c0947de30) at ../../src/InitExt.c:73
 _XftDisplayInfoGet (dpy=0x563c0947de30, createIfNecessary=<optimized out>) at ../../src/xftdpy.c:91
 XftDefaultHasRender (dpy=dpy@entry=0x563c0947de30) at ../../src/xftdpy.c:254
 XftDefaultSubstitute (dpy=dpy@entry=0x563c0947de30, screen=screen@entry=0, pattern=pattern@entry=0x563c09981c00) at ../../src/xftdpy.c:462
 XftFontMatch (dpy=dpy@entry=0x563c0947de30, screen=screen@entry=0, pattern=pattern@entry=0x563c09981be0, result=result@entry=0x7fff7086b34c) at ../../src/xftfont.c:52"
1780145,2018-07-04 18:19:18 UTC,I reproduced the bug. It's atached.
1780157,2018-07-04 21:47:50 UTC,This is the current environment that is deployed and everything seems to be working with the exception of keystone.
1780160,2018-07-05 06:09:56 UTC,Thanks for reporting.
1780160,2018-07-05 13:19:34 UTC,"Wow, I'm impressed.  You jumped right on this.  Very impressive.
I certainly will test and report the status when there are updates.
Thank you!
(Btw, I put in a feature request over a month ago. Never heard back.
Just say'n :) )"
1780164,2019-11-18 18:21:59 UTC,"I am also seeing the same issue, that the /proc/<memcached pid>/fd/ count increasing with each Horizon login. I agree we need to fix keystoneauth."
1780164,2019-06-11 20:40:05 UTC,@mchlumsky thanks for including the patch for session.py.  We are able to use it in a packaged Rocky deploy and successfully overcome the file descriptor leak associated with the keyauth connections.  This successfully resolved our too many open files error being caused by unbounded growth of open files due to lack of close() after connect()'s to keystone.
1780164,2018-11-09 16:09:23 UTC,Thanks for looking at this.
1780164,2018-10-24 19:18:34 UTC,"We should fix keystoneclient. KeystoneAuth is not doing anything wrong here. I am against a ""temp hack"" like this. Secondarily, please submit this patch to gerrit at review.openstack.org so that it can be considered. Posting patches here is unlikely to be seen as easily/readily."
1780164,2018-09-05 13:27:05 UTC,"We have also noticed this problem.
We did an strace on horizon and found that the connections made by horizon to keystone were not getting closed."
1780165,2018-07-08 13:10:58 UTC,The patch was merged in upstream.
1780165,2018-07-09 21:35:39 UTC,Please backport the following.
1780165,2018-08-29 09:24:15 UTC,Attach the patch for this problem.
1780165,2018-08-29 12:26:59 UTC,"The attachment ""Fix miss of  htb option value of tc command"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1780173,2019-12-08 04:17:28 UTC,[Expired for Canonical SSO provider because there has been no activity for 60 days.]
1780173,2019-10-08 14:40:42 UTC,Is this still an issue?
1780173,2018-07-05 14:46:39 UTC,I'm running on Version 67.0.3396.99 (Official Build) (64-bit) on my Macbook Pro. I'll check tonight for the Chrome version on my Windows 10 PC.
1780173,2018-07-05 14:17:51 UTC,Which version of Chrome are you using?
1780173,2018-07-09 22:46:27 UTC,"On my Windows 10 machine, Chrome: Version 67.0.3396.99 (Official Build) (64-bit)"
1780177,2018-07-11 01:37:07 UTC,it's fixed by adding 5 second delay on starting up.
1780189,2018-07-10 13:40:01 UTC,"It is possible that for speed of response, we are looking at client side cache and not actually querying the controller. We had similar issues with models command on 'controllers' command."
1780191,2018-07-05 07:12:25 UTC,"Sorry, wrong project, please close this bug"
1780194,2019-07-22 07:17:12 UTC,"What policies do you mean? policy.json or workflow task policies like ""retry"" and ""timeout""?"
1780194,2018-07-09 15:14:59 UTC,"Seems reasonable, we can consider this done when we have at least a basic test for each policy."
1780196,2018-07-12 02:09:30 UTC,I think it can be fixed in 2 ways:
1780196,2018-07-30 21:32:30 UTC,I also ran into this problem with Ubuntu Server 18.04 and a RAID 1 array (shutdown would wait 1:30 for the array to be unmounted). Manually unmounting the array before shutdown removed the problem.
1780196,2018-07-30 22:58:47 UTC,mdadm package ships mdadm-shutdown.service which should aid with unmounting raid arrays on shutdown.
1780196,2018-07-30 23:00:25 UTC,$ sudo apt install dracut-core
1780196,2018-07-30 23:54:48 UTC,finalrd accepted from NEW queue. unassigning self.
1780196,2018-09-12 21:59:59 UTC,"@xnox
sudo apt install dracut-core did not work for me."
1780196,2018-07-11 21:38:22 UTC,I found the commit where introduced this blkdeactivate: https://sourceware.org/git/?p=lvm2.git;a=commit;h=c698ee14bbb1310cf2383c8977d14a8e29139f8c
1780196,2018-07-12 01:47:18 UTC,"FYI: This problem can happen when the md0 device still synchronizing. Now, when the md0 is in sync, the service stopped as well:"
1780199,2020-06-10 08:57:24 UTC,This is still relevant - why not putting in the fix?
1780200,2020-04-11 02:04:57 UTC,"We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed."
1780204,2018-07-05 10:04:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/580333"
1780204,2019-07-01 21:24:21 UTC,"Reviewed:  https://review.opendev.org/580333
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=e02b9b798007b9f8c70e33c22fa6189d81a41ca3
Submitter: Zuul
Branch:    master"
1780204,2019-07-11 23:20:02 UTC,"Reviewed:  https://review.opendev.org/668007
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=aca7474ca3c7bba54473fca35b6d88a3a1efdca4
Submitter: Zuul
Branch:    feature/losf"
1780204,2019-07-22 20:15:15 UTC,This issue was fixed in the openstack/swift 2.22.0 release.
1780205,2018-07-06 14:49:42 UTC,"Reviewed:  https://review.openstack.org/580316
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=33cfb4e8afe7e33ca3b6775849b9233d60269928
Submitter: Zuul
Branch:    master"
1780205,2018-07-05 08:13:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/580316"
1780210,2018-07-05 08:58:39 UTC,"The one outside the indicator applet should be removable after right clicking on it.
Did you try resetting the panel?"
1780210,2018-07-05 09:14:36 UTC,"R-click on network icon outside displays network menu but no option to remove.
If i reset the bar i have to do all configurations again, so i didnot reset it."
1780210,2018-07-05 10:46:30 UTC,"It appeared in mate-dark theme too after two restart :(
see the screenshot"
1780210,2018-07-05 11:00:40 UTC,resetting also did not help
1780210,2018-07-10 11:12:36 UTC,"I seem to be having the same issue.
Running a fully updated Ubuntu MATE 18.04 and I think the issues appeared yesterday. It seems random as sometimes it goes away after a reboot.
I unsure what information to supply but feel free to ask and I will supply whatever I can."
1780210,2018-07-10 11:24:46 UTC,I've added that;
1780214,2018-07-05 09:02:32 UTC,https://review.openstack.org/580324
1780214,2018-07-24 03:05:15 UTC,This issue was fixed in the openstack/python-tackerclient 0.13.0 release.
1780219,2018-07-06 06:06:58 UTC,"Last login: Fri Jul  6 07:49:13 2018 from 192.168.0.58
user@OptiPlex-580:~$ uname -a
Linux OptiPlex-580 4.18.0-041800rc3-generic #201807012030 SMP Mon Jul 2 00:33:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
user@OptiPlex-580:~$ dmesg
[    0.000000] Linux version 4.18.0-041800rc3-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu 7.3.0-24ubuntu1)) #201807012030 SMP Mon Jul 2 00:33:15 UTC 2018
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc3-generic root=UUID=11ce9123-025c-4420-ba85-dee2799c0a2f ro rootflags=subvol=@ quiet splash vt.handoff=1
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: x87 FPU will use FXSAVE
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x00000000000997ff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000099800-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e6000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000cfd4ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000cfd50000-0x00000000cfd5dfff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000cfd5e000-0x00000000cfda7fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000cfda8000-0x00000000cfddffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000cfdec000-0x00000000cfefffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000011fffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 2.6 present.
[    0.000000] DMI: Dell Inc. OptiPlex 580/0YKH50, BIOS A05 06/16/2011
[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000000] AGP: No AGP bridge found
[    0.000000] last_pfn = 0x120000 max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: uncachable
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-EFFFF uncachable
[    0.000000]   F0000-FFFFF write-protect
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 000000000000 mask FFFF80000000 write-back
[    0.000000]   1 base 000080000000 mask FFFFC0000000 write-back
[    0.000000]   2 base 0000C0000000 mask FFFFF0000000 write-back
[    0.000000]   3 disabled
[    0.000000]   4 disabled
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] TOM2: 0000000130000000 aka 4864M
[    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.000000] e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
[    0.000000] last_pfn = 0xcfd50 max_arch_pfn = 0x400000000
[    0.000000] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [(____ptrval____)]
[    0.000000] Scanning 1 areas for low memory corruption
[    0.000000] Base memory trampoline at [(____ptrval____)] 93000 size 24576
[    0.000000] Using GB pages for direct mapping
[    0.000000] BRK [0x0815a000, 0x0815afff] PGTABLE
[    0.000000] BRK [..."
1780219,2018-07-06 05:57:58 UTC,"Last login: Thu Jul  5 11:16:37 2018 from 192.168.0.58
user@OptiPlex-580:~$ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3/linux-image-unsigned-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb
--2018-07-06 07:50:20--  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3/linux-image-unsigned-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb
Resolving kernel.ubuntu.com (kernel.ubuntu.com)... 91.189.94.216
Connecting to kernel.ubuntu.com (kernel.ubuntu.com)|91.189.94.216|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8124800 (7,7M) [application/x-debian-package]
Saving to: ‘linux-image-unsigned-4.18.0-041800rc3-generic_4.18.0-041800rc3.201807012030_amd64.deb’"
1780219,2018-07-05 14:24:52 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1780219,2018-07-05 09:30:07 UTC,This change was made by a bot.
1780225,2020-04-28 15:48:32 UTC,"Reviewed:  https://review.opendev.org/723858
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=32bbbd698a2a9c5ca6f0b01662d94c64e21422b1
Submitter: Zuul
Branch:    master"
1780225,2020-04-28 12:44:13 UTC,"In Stein, we merged the ability to have multiple Resource Providers, each of them being a pGPU.
In Ussuri, we accepted to have a specific vGPU type per pGPU."
1780225,2020-04-28 10:24:10 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/723858"
1780225,2019-07-24 02:40:48 UTC,Any updates recently?
1780225,2019-02-28 11:36:26 UTC,As a workaround I set `max_concurrent_builds` to 1 in `nova.conf`.
1780225,2019-01-23 14:33:13 UTC,"Hi,
Any update on this one?"
1780225,2018-07-05 22:49:37 UTC,Setting this to Confirmed as the Importance has been set and the bug has been Assigned.
1780226,2018-09-06 15:09:12 UTC,"I believe i'm having the same issue. Trying to get a preseed to work and it hangs trying to umount on shutdown. the install still works if you force shutdown afterwards...but the point of a preseed is to be unattended, and users having to force a shutdown make my team, and ubuntu, look bad."
1780229,2018-07-05 10:41:11 UTC,I came to Ubunto because my computer (HP Pavilion netbook) is just dreadfull and I've been told 2g ram is not enough but I'm having the same and other problems now with ubunto. Should I just bin it and buy another with 4g ram instead?
1780232,2018-07-11 11:31:11 UTC,"I'm a fan of good error messages, so there's no need to apologzie ;-)"
1780232,2018-07-11 07:00:36 UTC,"The filesystem was not mounted, I wanted to say. Sorry."
1780232,2018-07-05 16:35:58 UTC,/tmp/apparmor-bugreport-yr8c3w3p.txt should contain more details. Can you please attach that file?
1780232,2018-07-10 00:17:16 UTC,"I'm completely surprised that you can reproduce this bug, and I have no idea why :-/  (needless to say, can't reproduce it on my system)"
1780232,2018-07-06 06:55:03 UTC,"Hi, Christian. First, thank you for your reply.😉"
1780232,2018-07-11 06:52:26 UTC,"I'm very sorry Christian! Yesterday, I realized that the filesystem of apparmor would be mounted. I researched a little more and the module wasn't loaded in grub."
1780234,2018-07-06 11:18:11 UTC,"Interesting update.  In the meantime, I added a default document to the templates.  Now Inkscape will not open at all when I have the second monitor connected."
1780236,2018-07-05 15:42:07 UTC,"could you attach a sample file, for testing purposes?"
1780236,2018-07-05 18:39:38 UTC,Hope this will work....
1780236,2018-07-05 22:52:26 UTC,"thanks for the file.
appears to be a duplicate of Bug 1671691
https://bugs.launchpad.net/inkscape/+bug/1671691"
1780236,2018-07-06 11:10:17 UTC,Thanks for the feedback.  I have read the info at your link but I cannot find the viewbox option in Document Properties to make suggested changes.
1780236,2018-07-06 11:16:21 UTC,Nevermind.  I found it.  Sorry.
1780237,2018-07-05 17:00:57 UTC,"Moved to amdgpu. The problem appears to be a conflict between amdgpu and radeon, both of which were installed automatically on a fresh Xubuntu 18.04 install."
1780237,2018-07-05 12:06:47 UTC,"Ah. `radeon` and `amdgpu` are trying to load together, that may not be helping:"
1780237,2018-07-05 11:59:05 UTC,Hmm. `xrandr --listmonitors` gives two monitors connected:
1780237,2018-07-05 12:14:08 UTC,"Uninstalling the `radeon` drivers, but keeping the `amdgpu` drivers, fixes the problem. Therefore, this is not an Xorg bug."
1780245,2019-10-21 09:55:33 UTC,Looks like you need to remove run_once and delegate_to from that task.
1780245,2019-01-11 10:31:59 UTC,"Hi there,"
1780245,2019-10-18 15:29:34 UTC,"gnocchi-upgrade is executed during bootstrapping:
 extended_start.sh:
 if [[ ""${!KOLLA_BOOTSTRAP[@]}"" ]]; then
     sudo -H -u gnocchi gnocchi-upgrade --log-file /var/log/kolla/gnocchi/gnocchi-upgrade.log
     exit 0
 fi"
1780245,2019-01-11 10:58:44 UTC,"Hi all,"
1780247,2018-07-06 02:53:46 UTC,I can't seem to reproduce the problem on 16.04 here.
1780247,2018-07-06 08:22:16 UTC,Attached an image showing the issue in action.
1780247,2018-09-05 04:17:18 UTC,[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]
1780247,2018-12-04 19:04:15 UTC,Looks fine for me in gedit 3.28.1 on Ubuntu 18.04
1780247,2018-12-05 10:11:12 UTC,"If you open it through the open menu item, what encoding is selected in the bottom left corner?"
1780254,2018-12-11 19:25:28 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1780254,2018-07-05 21:20:12 UTC,"Yes, that would be nice. ""Magnetic pad/track"" type snapping when using other tools like Caliper, Highlight Net, Add Dimension, or similar, would be very nice!"
1780254,2018-07-06 20:47:10 UTC,Related bug: https://bugs.launchpad.net/kicad/+bug/1778436
1780254,2018-07-05 19:51:32 UTC,Related bug: https://bugs.launchpad.net/kicad/+bug/1769523
1780254,2018-07-05 19:48:17 UTC,Do Ctrl + Shift or Alt + Shift do anything? I stumbled upon this: https://forum.kicad.info/t/how-to-avoid-the-magnetic-behavior-when-drawing-a-track-via/6877/4
1780254,2018-07-05 19:42:06 UTC,"This sounds useful to me too from my new-user perspective. But, I don't fully understand what magnetic tracks and pads means..."
1780254,2018-07-05 20:56:17 UTC,@eRCaGuy Ctrl + Shift or Alt + Shift currently don't do anything.
1780271,2020-07-17 01:35:14 UTC,This issue has been resolved with the switch to GTK3!
1780278,2018-07-29 09:03:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780278,2018-08-21 13:40:28 UTC,Note that Debian Stretch Backport is already up to date. So this is just a matter of syncing version 2.5.2+dfsg-1~bpo9+1 from there.
1780278,2019-04-01 18:49:00 UTC,"Moreover, ansible v2.5.1 is affected by https://github.com/ansible/ansible/issues/54618 which has been (partially) fixed in v2.5.3 so I recommend going to v2.5.3 not v2.5.2"
1780278,2019-06-10 01:22:06 UTC,"The append to list bug is also reported in 1825096, but this bug report can focus on the upstream issue  https://github.com/ansible/ansible/issues/54618 that's from 2.5.3."
1780283,2018-09-12 15:13:56 UTC,"The patch on bug #1776917 fixes this issue on the Bills, Current screen."
1780283,2019-07-26 17:15:09 UTC,"On our 3.2.4 system, I am seeing this issue only on the Bill History Payments screen."
1780283,2019-07-26 17:29:58 UTC,"I am still seeing this on 3.2.4 in both Bill History and Payment History. As soon as I remove the Bill #/Payment ID column, I cannot individually select rows anymore."
1780283,2019-08-09 04:15:16 UTC,"Seeing this on 3.2.7 for Patron Bill History. If the Bill #/Payment ID are not visible, the unique ID for the ng-repeat is undefined, so when you select one row it selects the undefined rows (which is all of them). This patch adds the required attribute to those eg-grid-field directives. https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbriem/lp1780283_checking_1_bill_checks_all"
1780283,2019-10-25 18:36:49 UTC,"Thanks for marking my other ticket a duplicate of this John, the fix from Dan Briem works for us."
1780283,2019-12-27 21:12:25 UTC,"Pushed to master, rel_3_4, and rel_3_2. Thanks, Dan and Josh!"
1780301,2020-10-02 20:17:26 UTC,"Hi Daniel,"
1780305,2018-07-15 20:39:07 UTC,Interesting fixes! Thanks for the shorter gateway-vs-double-route tip. It's working for me here too.
1780305,2018-07-14 19:30:21 UTC,"I was able to temporarily workaround the issue of setting my routes at startup by using networkd-dispatcher, and creating the following files as the root user with chmod u+x:"
1780305,2018-07-14 19:08:37 UTC,I am also trying to use netplan on OVH. However I have found that the broadcast address being set to 0.0.0.0 doesn't seem to be a problem.
1780305,2018-07-15 07:10:45 UTC,"I finally managed to get a working Netplan config for OVH where the routing works, and where I don't need the networkd-dispatcher workarounds:"
1780307,2018-07-05 19:41:07 UTC,"I'm not clearly understanding if this is an issue with the latest version (and thus, an upstream issue) or if there is a patch we can put in a stable release."
1780307,2018-07-06 00:52:37 UTC,Thanks for the quick response; I do see the same behavior in latest Ubuntu (18.04) as well.
1780307,2018-07-06 01:14:07 UTC,Please file a bug here: https://storyboard.openstack.org/#!/project/719
1780307,2018-07-06 03:06:43 UTC,"Thanks for the help, link to bug here, https://storyboard.openstack.org/#!/story/2002897"
1780307,2018-07-06 03:37:32 UTC,"Hm, it seems I can't link the bug here."
1780307,2018-08-27 02:19:04 UTC,"My review, https://review.openstack.org/#/c/584607/,  has been submitted. I ended up removing the 'compatible' option from git-review as well because the original 'refs/for/*' was reverted back to as the namespace and 'refs/publish/*' was deprecated in favor of the original. I've updated the status here to reflect the change being committed."
1780308,2018-07-05 18:47:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780308,2018-07-05 18:51:19 UTC,Thanks @mottenkiller.
1780308,2018-07-05 22:18:58 UTC,Thx @ckrainey
1780310,2018-09-21 09:32:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780310,2018-10-15 13:20:18 UTC,Can confirm this for 18.04 with a network Ricoh NRG MP C5503 PS printer.
1780310,2018-10-17 17:09:00 UTC,Forwarded upstream: https://github.com/zdohnal/system-config-printer/issues/122
1780310,2019-01-07 20:36:49 UTC,This bug was fixed in the package system-config-printer - 1.5.11-2ubuntu2
1780310,2019-06-17 00:01:29 UTC,"Still affecting 18.04. Also note that upstream does not have an issue tracker anymore, losing the linked issue above."
1780310,2019-06-18 09:50:44 UTC,Upstream has moved system-config-printer to the GitHub of OpenPrinting. You find it now here:
1780310,2020-05-11 07:24:50 UTC,Confirming issue. Using the Ricoh Aficio MP C3502 PS driver.
1780310,2020-05-11 07:29:01 UTC,According to https://github.com/OpenPrinting/system-config-printer/issues/122 it should be temporarily fixed in 1.5.12 which is included in 20.04. Will this be be released into 18.04?
1780313,2019-10-16 06:09:27 UTC,"We fixed a bunch of the preinst issues in later versions of snapd, please let us know if you still have this issue."
1780313,2019-12-16 04:17:23 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1780313,2019-12-16 04:17:25 UTC,[Expired for snapd because there has been no activity for 60 days.]
1780315,2018-10-01 20:57:12 UTC,"This is a change in behavior in the web client. In the xul client, the staff user gets this prompt after cancelling a hold where an item is in transit (also attaching a screenshot:"
1780315,2019-03-25 17:54:48 UTC,Related bug: https://bugs.launchpad.net/evergreen/+bug/1789296
1780316,2020-03-09 23:09:07 UTC,This bug was fixed in the package netcat - 1.10-41.1ubuntu1
1780316,2020-03-10 03:09:25 UTC,This bug was fixed in the package netcat-openbsd - 1.206-1ubuntu1
1780316,2018-07-05 19:04:52 UTC,This issue crops up on the Bionic minimal cloud images which don't have netcat-openbsd installed by default (it is in the Xenial image).  When docker.io is installed with recommends it pulls in netcat-standard (via ubuntu-fan).
1780317,2019-04-24 16:35:35 UTC,It will be cool to have posibility rename all occurrences of a label
1780318,2018-07-18 10:00:04 UTC,Any plans to implement grouping and this?
1780318,2020-05-31 16:04:37 UTC,The mirroring is especially useful for PCB antenna which does not have a real part sitting on it so it should be total fine to mirror it around X or Y axes.
1780318,2018-07-18 10:29:00 UTC,"The budget for 6.0 is going to be largely chewed up by replacing the canvas, toolset and file format in Eeschema (although the canvas part might happen for 5.1)."
1780318,2018-07-12 15:15:41 UTC,"Overall though, yes, grouping would be very nice too."
1780318,2018-07-05 22:04:34 UTC,Here's my footprints I'm talking about for instance:https://github.com/ElectricRCAircraftGuy/eRCaGuy-KiCad-Library/tree/master/ercaguy-footprints.pretty.
1780318,2018-07-12 01:47:19 UTC,I think we'd also need grouping before this would be terribly useful.
1780318,2018-07-05 22:01:14 UTC,"Fabian, I see your point. Most footprints you at most need to flip (for the backside copper layer) and rotate. However, I still think my request is a good wishlist add on (with your recommended warning if mirroring a footprint), because it A) speeds up the creation of new footprints if you can mirror polygons and other shapes (I just made a couple capacitive touch slider ""virtual"" footprints and put them on my public GitHub pg and this would have been really nice) and B) allows you to mirror these virtual footprints (and others you may want to mirror) to your liking (since nothing is soldered to touch pads for instance) when placing them."
1780318,2018-07-05 19:18:41 UTC,Screenshot.
1780318,2018-07-05 21:35:01 UTC,"I would not like to accidentally mirror a footprint in pcbnew, maybe it could show a warning when mirroring a footprint. For other graphical objects it might not be necessary to warn."
1780318,2018-07-12 15:14:37 UTC,"Perhaps for many cases, but after turning several polygons plus a pad into a single pad (a form of grouping that works right now) the mirroring features will already be useful today."
1780326,2021-02-12 22:13:08 UTC,"I can confirm this in Evergreen 3-4-5. I no longer have access to XUL, so there are many patterns I can no longer create."
1780332,2018-09-14 18:57:53 UTC,"asi,"
1780332,2018-09-15 04:56:12 UTC,"Look for ""dmsetup udevcomplete"" call in udev rules. This is the sync point when libdevmapper continues. This must be the last call in udev chain rules related to device-mapper devices.
(Run cryptsetup with --debug and you will see that sync point.)"
1780332,2018-09-15 15:15:25 UTC,"asi,"
1780332,2018-10-09 15:07:26 UTC,"95-dm-notify.rules in dmsetup is only shipped in bionic and up. So I suspect that xenial, does not have udev synchronisation in dmsetup package."
1780332,2018-10-11 08:24:31 UTC,@xnox
1780332,2018-10-11 08:11:37 UTC,"We still have some clouds getting deployed with xenial that rely on this,
however, the workaround works for our purposes."
1780332,2018-10-22 11:59:05 UTC,"Also reading above comments, did we verify that Bionic is correctly synchronized, and needs no workaround? It would be nice to reliably confirm that these things operate race-free in bionic and up, and then mark this bug to affect only xenial and below."
1780332,2019-05-02 15:39:25 UTC,"Ping, does vaultlocker work, _without_ work arounds, race free on bionic and up?"
1780332,2019-07-10 20:00:30 UTC,"xnox,"
1780332,2018-09-14 17:48:59 UTC,"If you have properly installed device-mapper udev rules, cryptsetup is internally synchronized to all symlinks and nodes creation (it should never return only when udev is finished, that's why libdevmapper internally uses semaphores and cookies per device)."
1780332,2018-10-10 13:25:31 UTC,do we need and want to enable udev synchronisation in dmsetup package in xenial?
1780332,2018-09-14 17:17:50 UTC,"As a hint on reproducing it, it may be a problem on xenial only (which we used for that deployment) for clean devices."
1780332,2018-07-10 06:36:10 UTC,OK I hacked in a test of:
1780332,2018-09-14 16:06:22 UTC,Dimitri
1780332,2018-09-14 16:06:39 UTC,tl;dr you don't need vaultlocker to reproduce this issue :-)
1780332,2018-07-05 21:14:34 UTC,Subscribed ~field-critical as this blocks a deployment in-progress.
1780332,2018-07-05 21:37:44 UTC,This is my proposed fix. I'd like several people to check it.
1780332,2018-07-06 02:01:38 UTC,Deployed with the fix and got error below from vault.
1780332,2018-07-06 08:53:15 UTC,osd_fsid gets generated in the ceph lib called from the ceph-osd charm. It's just a version 4 (randomized) uuid - nothing special.
1780332,2018-07-06 09:11:56 UTC,"dmitriis, fwiw alai's stackstrace is not from ceph, its from nova-compute. Your point still stands, its a random uuid."
1780332,2018-07-06 08:32:43 UTC,"With the error in vault, we initialized vault and unsealed.  vault showed it is in ready status.  The error from juju log show uuid is  d045f2c8-b705-4113-9291-2ef203600fb0 but this uuid does not exist. Where does the charm gets d045f2c8-b705-4113-9291-2ef203600fb0 from?"
1780332,2018-07-06 23:31:14 UTC,From the most recent deployment we see the settle runs but is insufficient:
1780332,2018-09-12 14:13:45 UTC,Marking the cryptsetup task as invalid because this is handled entirely in vaultlocker
1780332,2018-09-13 14:33:54 UTC,"In discussion with James, we still want cryptsetup triage on this."
1780332,2018-09-13 14:34:09 UTC,"Incorrectly marked it invalid, as there is a bug in cryptsetup NOT creating the block symlink"
1780332,2018-07-06 09:14:56 UTC,"With the redeployment, uuid d045f2c8-b705-4113-9291-2ef203600fb0 does not show in blkid."
1780332,2018-09-13 15:39:52 UTC,I'm not sure what vaultlocker is.
1780334,2018-07-07 22:34:47 UTC,Unsubscribing the Ubuntu Sponsors Team as there's nothing to sponsor at the moment (and Adam is a Core Developer).
1780334,2018-08-03 10:24:13 UTC,"I don't like that idea very much.  that will likely leave many dependencies left, and will cause extra work for archive admins and distro people. Please could you consider packaging this as kubernetes-installer, so that existing dependencies in the archive are resolvable?"
1780334,2018-08-03 17:41:25 UTC,There are zero reverse-dependencies of the kubernetes binary packages in Debian or Ubuntu.  The kubernetes package from Debian has also never been buildable in Ubuntu and is now blacklisted.
1780334,2018-08-23 16:54:00 UTC,"I don't know if Matthias did a full NEW review of the package before rejecting, so doing so now."
1780334,2018-08-27 14:36:57 UTC,"Thanks Steve, was a little rusty. I've made changes and did a new upload."
1780334,2018-08-23 15:31:40 UTC,"This got rejected originally, but it sounds like we're ok uploading the package in its current state?"
1780339,2018-07-06 04:51:26 UTC,"Hi Alistair,"
1780341,2018-07-05 23:22:08 UTC,On a fresh 18.04 container after installing squid:
1780341,2018-09-19 03:44:01 UTC,Squid logs are a customized timestamp format based on UNIX times but also including millisecond (and optionally nanosecond) resolution not available in strictly UNIX timestamps.
1780341,2018-09-21 10:18:45 UTC,I appreciate the pain of not being able to immediately read squid's logs. I've suffered this myself.
1780341,2018-09-23 06:25:05 UTC,"Squid already several contains such other formats. All they take is configuration. The default one is intended for fast machine interpretation, since that is the majority use-case for all Squid installations."
1780341,2020-01-08 16:58:35 UTC,I'll be realistic and unassign myself from this. Sorry I haven't managed to get to it yet.
1780341,2020-04-22 13:27:47 UTC,"For reference, just because it took me a while to get the syntax right, plus https://bugs.squid-cache.org/show_bug.cgi?id=4905 made me scratch my head a bit wondering why it wasn't working when I used ""squid"" instead of another name:"
1780351,2019-07-08 19:19:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780351,2019-07-08 19:43:20 UTC,Thank you for reporting. I hope I managed to fix this dependency problem in the PPA version by adding a 'Conflicts' and 'Replaces' relation. The fixed versions are those starting with 5.0.1-ppa1.
1780364,2018-07-06 15:52:23 UTC,Reopening to let the snappy team decide; it seems like `snap run --shell` would be a better experience for everyone if there was a way for it to know what should be added to the $PATH for that particular snap.
1780364,2018-07-06 15:54:54 UTC,"Ah, never mind, you've re-titled this and it no longer makes sense for snapd. Guess I'll file another bug."
1780364,2019-12-12 14:06:28 UTC,This can be done via snap run --shell maas and running maas commands under $SNAP/snap/command-chain/snapcraft-runner
1780364,2018-07-06 08:45:06 UTC,"I’m marking snapd as invalid provided that this has nothing to do with snapd. As far as the debugging, the snap doesn’t expose the Maas-region command, which is actually intentional."
1780365,2018-11-19 20:16:24 UTC,Thank you for reporting this bug. The access via DBus when the keyring is unlocked is a well-known issue and the design of the feature as explained when reading the entirety of https://wiki.ubuntu.com/SecurityTeam/FAQ#gnome-keyring. Users who prefer to be prompted can choose to use a separate keyring than the one that is automatically unlocked upon successful login.
1780365,2018-12-31 13:02:53 UTC,"This issue was reported upstream:
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/5"
1780365,2018-07-08 15:16:22 UTC,"I know about that, but the problem is more serious than what I initially thought.
Existing issues have focused primarily on the behavior of seahorse and simply expect to prompt for a password before displaying a key’s plaintext password.
Moreover, countermeasures in Ubuntu Security FAQ is not appropriate for the problem and it doesn’t work like that.
The underlying problem has not been solved yet."
1780365,2018-07-06 15:06:42 UTC,or bug #189774 in launchpad
1780365,2018-07-06 15:05:39 UTC,The issue looks similar to the well known https://bugzilla.gnome.org/show_bug.cgi?id=551036
1780365,2018-07-13 05:05:41 UTC,@seb128 Please check this issue.
1780373,2018-07-31 15:29:33 UTC,"Reviewed:  https://review.openstack.org/581845
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c7b0779632a8df7d988e9b52ae1f341af0b0df30
Submitter: Zuul
Branch:    stable/queens"
1780373,2019-03-26 04:17:52 UTC,"Reviewed:  https://review.openstack.org/581867
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=64f2104bd104638dce081d2f37ed2bd040ef7068
Submitter: Zuul
Branch:    stable/pike"
1780373,2019-03-26 04:17:42 UTC,"Reviewed:  https://review.openstack.org/581866
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7858a84ee4d74e40adeecc0cf463e8937a1c5ada
Submitter: Zuul
Branch:    stable/pike"
1780373,2018-09-24 14:47:17 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1780373,2018-08-01 01:42:54 UTC,"Reviewed:  https://review.openstack.org/581846
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1aa81ebfdc585451cbae9c9bbde8adfe339cb0dc
Submitter: Zuul
Branch:    stable/queens"
1780373,2018-07-30 16:07:32 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1780373,2019-04-26 17:16:36 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1780373,2018-07-11 21:33:30 UTC,"Reviewed:  https://review.openstack.org/580755
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9874e059df50dc81803fcfdfd1045cc09624894
Submitter: Zuul
Branch:    master"
1780373,2018-07-11 19:18:09 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/581867"
1780373,2018-07-11 19:17:51 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/581866"
1780373,2018-07-11 19:07:51 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/581846"
1780373,2018-07-11 19:07:33 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/581845"
1780373,2018-07-06 20:37:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/580755"
1780373,2018-07-06 15:07:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/580684"
1780373,2018-07-06 17:57:36 UTC,"First, I assume your boot request included the instance group, for example:"
1780373,2018-07-11 21:33:42 UTC,"Reviewed:  https://review.openstack.org/580684
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bbee9a26a5c64a1463bd9a9f82d735ec17c62d52
Submitter: Zuul
Branch:    master"
1780380,2017-11-21 16:20:02 UTC,"Created attachment 364129
Video of Fileroller changing perms"
1780380,2018-07-06 19:29:07 UTC,This appears to be the same bug as https://bugzilla.gnome.org/show_bug.cgi?id=790672
1780380,2020-11-11 19:13:31 UTC,bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.
1780383,2019-06-29 00:38:47 UTC,"Has anyone seen any correlations to this bug and a node update, we had been using version 3.3.0 of this client for roughly a year and only saw the symptoms of this manifest after updating our nodes from 6.5 to 6.20 with no client side code changes. We're still actively troubleshooting, any information is helpful."
1780383,2019-07-01 15:57:11 UTC,This was fixed in https://review.opendev.org/#/c/651666/
1780383,2019-07-01 18:05:54 UTC,"Cherry-picking the test (with some slight modifications), it looks like it passed on 3.3.0 and 3.4.0, but broke in 3.5.0 and continues to fail on 3.6.0 and 3.7.0. Culprit seems to be https://github.com/openstack/python-swiftclient/commit/2faea93 which significantly re-worked how SLOs are handled to allow them to be created from data streamed via stdin."
1780390,2018-08-07 09:16:51 UTC,Only the preview appears affected; the actual printing is OK e.g. 2 pages per side in Vlad's example
1780390,2018-08-07 09:15:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780395,2018-07-09 09:09:08 UTC,This is a test result example for a working server available:
1780395,2018-08-09 06:32:46 UTC,The iperf test issue fixed with http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=481edaa9bb6a0e2964e99cd824b9aa26cb8055f7
1780395,2018-09-12 17:55:47 UTC,do you have anymore info on this?  I can run the tests manually and find out if not.
1780395,2018-09-13 03:42:47 UTC,"Hi Sean,"
1780395,2020-07-24 22:00:58 UTC,"The Iperf test has been passing on all metals in the past SRU cycles, yet the data in the test is rather stale. The iperf server is still set for 10.245.80.28, Which is from years ago."
1780404,2019-09-06 02:26:15 UTC,"not sure what you mean by ""static admin account"", can you provide more details?"
1780404,2020-10-21 22:29:03 UTC,Moving to Confirmed due to a long inactivity.
1780404,2020-10-21 22:44:39 UTC,"If force_tenant_isolation is False the tests pass, the question is if force_tenant_isolation should be False per the comment - https://opendev.org/openstack/tempest/src/commit/63aec891fca494bbb5b0841e3c52cb9b20674fe4/tempest/api/identity/base.py#L120-L127"
1780412,2020-05-14 09:35:21 UTC,This seem to be no longer an issue in the current version of TAPAAL.
1780421,2018-10-25 15:30:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/613361"
1780421,2021-02-19 15:52:27 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1780421,2018-11-15 11:10:55 UTC,"Reviewed:  https://review.openstack.org/616882
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=d10e70482ab497728f2178f3c0862db75eac49fd
Submitter: Zuul
Branch:    stable/rocky"
1780421,2018-11-09 11:34:25 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/616882"
1780421,2018-11-09 10:15:52 UTC,"Reviewed:  https://review.openstack.org/613361
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=48e7aba0bfb116b9370cc337eb966cd27393a7e5
Submitter: Zuul
Branch:    master"
1780421,2018-09-17 21:25:17 UTC,"Reviewed:  https://review.openstack.org/598229
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=40ede6260cd56ed74a6d61cfac0a6a7c03fb5dc8
Submitter: Zuul
Branch:    stable/queens"
1780421,2018-07-06 11:00:41 UTC,"That command for undercloud, isn't it required for overcloud ironic as well?"
1780421,2018-08-30 16:40:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/598229"
1780421,2018-08-30 16:39:35 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/598228"
1780421,2018-08-30 02:07:42 UTC,"Reviewed:  https://review.openstack.org/593498
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=7bcdb7f7deaf8446927c481e007a79b12d8201be
Submitter: Zuul
Branch:    master"
1780421,2018-08-20 06:36:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/593498"
1780421,2018-07-06 11:22:49 UTC,@Bogdan
1780421,2018-09-17 19:57:45 UTC,"Reviewed:  https://review.openstack.org/598228
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=ad692446430723df70372133b215f92fe982d964
Submitter: Zuul
Branch:    stable/rocky"
1780423,2018-09-13 03:55:24 UTC,Issue still exist in the recent SRU cycle (2018.08.17~)
1780423,2019-11-12 19:50:16 UTC,Should this bug be duplicated against the work done here since the host has been updated and is now theoretically reachable?: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1780395
1780426,2018-12-14 14:43:42 UTC,This can wait for v6
1780426,2019-07-14 10:02:11 UTC,"Fixed in revision 560fda70a2a3543a5bf6b587fdaf4aa835bdf6e0
https://git.launchpad.net/kicad/patch/?id=560fda70a2a3543a5bf6b587fdaf4aa835bdf6e0"
1780433,2019-09-16 06:42:39 UTC,I have the same problem in Ubuntu 18.04. I installed pulseaudio 12.2 from PulseEffects PPA and later downgraded using apt. Then starting pulseaudio daemon by command start-pulseaudio-x11 did not work. Removing /etc/pulse/client.conf.d/00-disable-autospawn.conf helped.
1780433,2019-09-16 06:35:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780436,2018-07-06 20:47:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780441,2018-08-01 08:18:39 UTC,Can you share the logs of nova-compute in debug. I'm suspecting something wrong during the claim.
1780441,2018-08-20 12:14:40 UTC,"Okay, this is the logs for an instance that had one gpu and after a handful of rebuilds it spawned with three."
1780441,2019-01-21 16:34:51 UTC,"This is probably related to, or a duplicate of, bug 1763766."
1780441,2020-05-19 11:22:10 UTC,Dear reporter. Could you confirm that the fix for bug 1763766 fixed your issue or not?
1780441,2020-07-14 08:51:28 UTC,Sorry for not responding. I'm no longer working with OpenStack as an admin I can not confirm if the fix would solve my problem.
1780441,2020-09-13 04:17:21 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1780453,2019-04-16 08:53:36 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1780453,2019-03-01 21:36:44 UTC,This can be quite problematic as it can result in issues with Nova not being able to properly start in certain cases.
1780453,2020-07-03 07:39:40 UTC,I think this bug is not valid anymore. We have https://github.com/openstack/neutron/blob/f787f12aa3441ecffef55f261c4d87dbb12ca6cf/neutron/plugins/ml2/plugin.py#L344 in ML2 plugin and it should rebind ports after agent is back.
1780453,2019-04-16 08:57:06 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/590301
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1780453,2018-08-08 09:40:46 UTC,"> This might be a bit of bruteforce, but perhaps we can introduce a condition that would
> append ""port_id"" (if present) here:
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/agent/rpc.py#n284 (link updated after latest code changes)
"
1780453,2018-07-12 10:17:11 UTC,feedback provided
1780453,2018-07-16 16:57:36 UTC,"This might be a bit of bruteforce, but perhaps we can introduce a condition that would append ""port_id""
(if present) here:
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/agent/rpc.py#n231"
1780453,2018-07-10 14:06:02 UTC,"Basically the get_device_details call triggered by http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#n1515 ends up returning basically empty port details because the port doesn't have any ""binding_levels"" set. I.e. it's returning from here: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/agent/rpc.py#n231"
1780453,2018-07-10 09:42:27 UTC,"As the current agent side will load the holded port info in memory, and the log you mentioned is here:
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#n1556"
1780453,2018-07-06 15:05:58 UTC,"BTW, it seems that this regression was introduced with: https://review.openstack.org/#/c/410385/"
1780453,2018-07-24 01:16:36 UTC,"glancing the code, the analysis looks correct."
1780458,2018-07-11 15:58:48 UTC,Adding a note that it would be nice if the email notice included a link to the queue for the completed import. I assume this addition to the notice would require the completion of bug 1779158.
1780458,2018-07-11 16:50:14 UTC,"Kathy, I believe you're correct, I'm not seeing a way to link to a queue in the AngJS+Dojo UI."
1780458,2018-07-27 12:44:14 UTC,"After doing an upload through Load MARC Order Records and getting the resulting Purchase Order and Queue links, I can get a link to a specific queue. It's formatted like this: https://test.gapines.org/eg/staff/cat/catalog/vandelay?qtype=bib&qid=1922"
1780458,2019-03-11 18:12:33 UTC,"Bill, now that you're farther along with Angular vandelay, is this wishlist item any closer to possible?"
1780458,2019-03-12 15:26:31 UTC,"Tiffany, yes, now that we can link directly to a queue this is ready for development.  It's still on my radar, but I won't be grabbing the bug just yet in case anyone else wants to jump on it in the meantime."
1780458,2019-10-22 17:46:32 UTC,Sketching out the initial DB seed data w/ some hooks and an initial email event def:
1780458,2019-10-22 18:59:51 UTC,"Adding in the portion for creating the event in Vandelay.pm, for review and revision:"
1780459,2018-11-16 10:11:24 UTC,"The problem with this is snapd makes no assumptions about paths in the snaps, snaps can have arbitrary structure of the filesystem; apps in the snaps work by providing exact paths to their binaries in the apps definitions (or having a wrapper script inside the snap). We could maybe blindly add bin and sbin of the snap to the PATH, but that's probably it, so I'm not sure it's of much value (and with whatever we do wrt `snap run`, snap-confine would need to be taught to accept)."
1780463,2018-07-11 19:49:48 UTC,"Also happens in bionic's 2:4.7.6+dfsg~ubuntu-0ubuntu2, and an upcoming 4.8.2. Looks like this is worth an upstream bug, since the release notes for 4.8.3 don't mention vfs."
1780463,2018-07-11 19:16:10 UTC,I can confirm this with xenial's samba:
1780467,2018-07-06 17:51:56 UTC,The bug was fixed? Nothing was done to fix it.
1780467,2018-07-06 20:25:27 UTC,"Then I dont know, the behaviour is back in 2.1.2 pre-release."
1780467,2018-08-07 13:32:02 UTC,win 7/32.
1780467,2018-08-07 18:07:32 UTC,"Let's keep discussion in one place in the original bug report, Bug #1751482."
1780467,2018-08-08 09:36:27 UTC,"This is a new case.
because 2.1.1 official release don't have this.
but 2.1.2pre again have this problem."
1780468,2019-10-16 12:36:22 UTC,Can you test https://gitlab.gnome.org/GNOME/metacity/commit/ef433bd7dec58cc9f062e0cda57cb259ff3745f1?
1780468,2018-07-08 10:27:32 UTC,Here you go.
1780468,2018-07-08 10:08:25 UTC,Can you attach your theme?
1780468,2018-07-08 09:59:43 UTC,It's not visible in metacity-theme-viewer. What is visible here is the first character rendered differently in the maximized state.
1780468,2018-07-07 16:44:40 UTC,Thanks for the heads up about metacity-theme-viewer!
1780468,2018-07-07 14:08:47 UTC,In metacity-theme-viewer you should change GTK+ to Metacity...
1780468,2018-07-07 13:39:40 UTC,To answer your questions:
1780468,2018-07-06 18:24:45 UTC,Do you have same problem with metacity? Sounds like you tested only gtk-window-decorator and marco...
1780468,2018-07-07 17:46:27 UTC,Is problem visible also in metacity-theme-viewer? If so then please use max scale and attach to upstream bug screenshot that looks good and other that shows problem.
1780475,2019-12-18 10:31:12 UTC,"Hi.
I'm affected too.
I solved by removing packages indicated in #9 by @vanvugt.
Thanks a lot!"
1780475,2018-08-14 06:44:48 UTC,Removing mesa-va-drivers and gstreamer-1.0-vaapi fixed the bug. Thanks a lot for your help!
1780475,2018-08-13 09:38:45 UTC,"I've done that and the bug still occurs, but it doesn't generate any core or crash file."
1780475,2018-08-13 09:09:46 UTC,"Sorry, I spend so much time debugging Xorg server crashes that for a moment I forgot this was about totem..."
1780475,2018-08-14 02:05:13 UTC,I've tracked down the offending source code:
1780475,2018-08-13 08:13:38 UTC,OK. Can you please attach a log file showing the IO error with some more context?
1780475,2018-08-13 07:58:25 UTC,"I tried steps 1, 2 and 3, but it doesn't change a thing: the crash occurs, the message ""totem: Fatal IO error 11 (Resource temporarily unavailable) on X server :1."" is spawned in the terminal, but no .crash file is generated."
1780475,2018-08-13 01:57:15 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1780475,2018-08-12 17:28:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780475,2018-08-13 08:53:58 UTC,"Sorry Daniel, I don't understand what you need. The bug occurs immediately after I try to launch totem:"
1780495,2018-07-06 23:15:00 UTC,"Ok, looks like enabling composite as workaround does let start xorg again:"
1780499,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1780500,2019-05-24 09:06:11 UTC,The same behavior confirmed in our test catalog (3.3.0).
1780506,2018-07-09 20:41:04 UTC,"Nice find. When I tested this, it also left the terminal echo off:"
1780506,2019-09-17 09:42:44 UTC,"Hi! Have you reported this issue to the upstream systemd developers?
If not, could you please report it to them so that it can get fixed?"
1780508,2018-07-06 23:37:03 UTC,This seems like a regression as this first occurred with the new version of Firefox.
1780509,2018-07-13 20:20:56 UTC,The relevant error message in the logs appears to be:
1780513,2018-07-09 03:00:13 UTC,This change was made by a bot.
1780513,2018-07-09 02:56:29 UTC,This sounds like a problem with the nouveau graphics driver. If the nvidia driver fixes it for you then please keep using that.
1780524,2020-06-29 22:31:12 UTC,"Thanks for the report.  For the first part, the 'wheel-0.30.0' wheel claims its 'Metadata-Version' is '2.0', which means that it shouldn't have any 'Provides-Extra' headers (those were added in PEP 566 for the '2.1' version of the metadata spec).  Thus, 'pkginfo' doesn't search for those headers."
1780525,2018-07-09 09:00:20 UTC,"Well that's funny. After a couple of weeks, and dozens of boots, I've suddenly got the icon back in the status notifier plugin. So I can click Preferences."
1780525,2018-08-29 23:38:03 UTC,I ran the program and the notification works.
1780525,2018-11-11 09:46:37 UTC,"Hi,"
1780525,2019-06-04 02:43:13 UTC,"I had the same problem. A workaround is to install dconf-editor (sudo apt install dconf-tools), and navigate to app/indicators/keylock to change the options."
1780525,2020-01-19 08:32:51 UTC,"This program is odd.  I removed the alert icon from taskbar and can no longer get into settings to put it back on.  When I tried uninstalling and reinstalling there was no change.  In fact its even stranger.  I completely removed the program and even tried purging it but it is always there.  It always notifies me if something is pressed whether the program is there or not??!  I tried the above suggestion of changing the settings in dconf, but it seems to totally ignore that too."
1780528,2019-02-24 20:23:35 UTC,"I'd be interested in picking this up. I'd also like the selected track to stay in view if I change the sort order, which it currently doesn't."
1780528,2019-02-24 22:25:46 UTC,What happens when the new search doesn't contain the previously selected track?
1780528,2019-02-25 19:17:34 UTC,@daschuer maybe you are thinking of a couple of bugs where this was raised before:
1780528,2019-02-25 19:21:16 UTC,"Actually that's not strictly the same, however it may be that one issue causes the other. Maybe if tracks don't become unselected, they will stay in view."
1780529,2018-11-03 22:19:37 UTC,https://github.com/mixxxdj/mixxx/pull/1867
1780529,2018-10-20 18:29:58 UTC,...and spills over into the padding area and is cropped.
1780529,2018-10-20 18:28:56 UTC,"This happens with the original en_US string too, not just the German translation."
1780529,2018-10-20 18:25:42 UTC,"I could reproduce it with 2.2 qt5 on Bionic.
Seems the issue is simply that (in Tango) the font weight changes to bold when a library pushbutton (AutoDJ, Recording) is checked or hovered. The button is not resized then."
1780529,2018-07-07 15:57:21 UTC,It is the master branch on Xenial using chinnamon desktop
1780529,2018-07-07 15:36:54 UTC,and I don't see why that button doesn't expand. there's no max-width defined in style.qss
1780529,2018-07-07 15:33:01 UTC,which branch is this? I don't see neither cropping nor the bold font in 2.1.1
1780529,2018-07-16 16:05:30 UTC,"I tested again with 2.2pre, Trusty and xfce4 desktop.
Neither I see the cropped label, nor the bold font.
Will look into it.."
1780534,2018-12-07 11:26:36 UTC,This bug was fixed in the package strongswan - 5.7.1-1ubuntu1
1780534,2019-01-08 17:37:34 UTC,"The verification of the Stable Release Update for strongswan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1780534,2019-01-08 17:37:21 UTC,This bug was fixed in the package strongswan - 5.6.2-1ubuntu2.4
1780534,2019-01-07 14:36:41 UTC,"Tested an upgrade on Cosmic and it makes it work there as well.
Per this and the former comment setting both tasks to verified."
1780534,2018-12-19 19:04:16 UTC,It definitely fixed the issue for Bionic; I couldn't test Cosmic but I doubt if the outcome would be different since the bug was an obvious configuration setting. Please alert me if you insist doing a full check for Cosmic too.
1780534,2018-12-18 17:28:05 UTC,"Hello Andras, or anyone else affected,"
1780534,2018-12-18 17:21:23 UTC,"Hello Andras, or anyone else affected,"
1780534,2018-12-03 15:08:30 UTC,I also started a discussion with the apparmor folks to understand what/if there is an issue making this special in containers.
1780534,2019-01-08 17:37:49 UTC,This bug was fixed in the package strongswan - 5.6.3-1ubuntu4.1
1780534,2018-12-03 14:07:37 UTC,"Why shouldn't it work in a container? (Granted, I don't know LXD, but strongSwan runs fine in network namespaces and stuff like Docker.)"
1780534,2018-12-03 14:00:04 UTC,Not yet but I'm working in a development project that will hopefully use containers for VPN in production. However I already have a workaround (cloud-init downloading the fixed config file) so the bug is not a blocker.
1780534,2018-12-03 13:34:08 UTC,"Since it would never (rarely?) work in a container anyway I'm not sure about the ""real"" need to SRU this, but fixing in 19.04 onwards seems right to me. Furthermore anyone could fix it by changing the config like
  $ echo ""/usr/lib/ipsec/stroke rmix,"" | sudo tee /etc/apparmor.d/local/usr.lib.ipsec.stroke"
1780534,2018-12-03 13:30:10 UTC,"This is very very odd, but in general applictions have often a
 /path/to/binary rmix,
rule and that is what makes it work.
Charon has one, so lets add the same for stroke as well, that seems safe and reasonable."
1780534,2018-12-03 13:16:32 UTC,"This apparmor rule
  /usr/lib/ipsec/stroke         m,
in /etc/apparmor.d/usr.lib.ipsec.stroke would resolve it."
1780534,2018-12-03 13:10:34 UTC,"Hmm, this really only is true when running in a container - it is just fine in a VM.
In addition PVNs from containers are always ""special"" as e.g. ipsec does a lot of kernel offloading. There are extra ipsec-userspace plugins in strongswan to make up for that."
1780534,2018-12-03 13:04:00 UTC,"Ack, thanks for the report."
1780534,2018-12-03 14:54:29 UTC,BTW the same fix is needed for /usr/lib/ipsec/lookip from libcharon-extra-plugins
1780540,2018-09-14 13:16:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780552,2019-03-19 06:37:38 UTC,It appears the problem here is that PulseAudio isn't running/installed.
1780552,2019-05-19 04:17:16 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1780552,2018-07-14 18:13:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780563,2019-02-25 10:36:11 UTC,"Hi,
enable-minimal is not the default by upstreams configure
103 AC_ARG_ENABLE(minimal,
104 [AS_HELP_STRING(--enable-minimal,
105   [Only compile the minimum set of functions required for the high-level API])],
106 [
107   AS_IF([test ""x$enableval"" = ""xyes""], [
108     enable_minimal=""yes""
109     SODIUM_LIBRARY_MINIMAL_DEF=""#define SODIUM_LIBRARY_MINIMAL 1""
110     AC_DEFINE([MINIMAL], [1], [Define for a minimal build, without deprecated functions and functions that high-level APIs depend on])
111   ], [
112     enable_minimal=""no""
113   ])
114 ],
115 [
116   enable_minimal=""no""
117 ])
118 AM_CONDITIONAL([MINIMAL], [test x$enable_minimal = xyes])
119 AC_SUBST(SODIUM_LIBRARY_MINIMAL_DEF"
1780574,2019-09-26 13:23:39 UTC,mirror not uptodate at the time most likely
1780576,2018-07-07 21:30:38 UTC,Ich bin bis 10.07. nicht im Haus und kann Ihre Nachricht daher nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
1780576,2020-02-26 11:51:40 UTC,"Dear Brendan,
Thank you for reporting it. We've recently shortlisted Windows installers to:
* Windows 32-bit Installer (Signed for Windows 10 and later)
* Windows 32-bit ZIP package"
1780578,2019-04-15 06:54:46 UTC,"As I said, it is the parser do decide and not a file ending.
Also having a version information of the file format in that file
significantly accelerates parsing as newer versions of a program can just
jump to the old browser or bend the funtion pointer of a stage2 parser that parses
the format for the version detected.
Renaming the file extension is only needed to have peace with windows and maybe
also MacOS (I dont have a mac as Apple denied warranty for my core2duo mac book pro
 where the display failed after only 16 Months - Apple sucks, so I never ever buy anything
from them).
Even some gnome based filemanagers in linux look at the ending, while there is the file tool
which tells you the file type based on magic numbers in the file (so file is a meta parser),
q.e.d. the parser is to decice"
1780578,2019-04-29 13:25:14 UTC,"@eelik, the new schematic files will have a kicad_sch extension, so 5.1 won't realize they're schematics and will think your project has no schematic.  So yes, the project won't be terribly useful -- but the board could still be edited."
1780578,2019-04-29 11:17:36 UTC,"@Jeff, I don't mean project file (currently .pro file) but the whole project. 5.1 can't use a *project* made with 6.0 (at least if it has a schematic). Therefore it's not very useful to open a 6.0 project file with 5.1. It would still be possible by manually renaming the file if someone wants to do that, provided that 6.0 recognizes both extensions."
1780578,2019-04-28 17:06:40 UTC,"Hi all, its quite easy,"
1780578,2019-04-18 07:55:10 UTC,"So having no version info in a file is an antipattern.
If you have a version information you can just invoke the right parser, e.g. by calling or overloading as posted before."
1780578,2019-04-17 22:17:02 UTC,"@Ludwig, we used to have a parser that attempted to determine the footprint library type and it was an unmitigated disaster.  I have no intention of resurrecting this idea from the dead for schematic file formats.  To reiterate Seth's comment, no.  The new file format will get the new extension.
 The old file format will keep the current extension."
1780578,2019-04-29 13:41:10 UTC,"The board file can be opened standalone anyways. Opening the project but not being able to recognize the schematic file would be confusing to users. And, to repeat what is already clear, users can rename the project file if they want to open the project. Or a bug fix release of 5.1 could recognize the new file extension if complete backward-compatibility is wanted."
1780578,2019-04-14 09:51:28 UTC,"@eelik, project files are just key/value dictionaries, so 5.1 will be able to use 6.0 project files (it just won't know about the 6.0 keys)."
1780578,2019-04-09 18:24:45 UTC,"@Ludwig, this would break the ability for KiCad to distinguish between opening the current schematic file format and new file format.  We will forever have to load legacy KiCad .sch files so the short answer is no we are not going to change the file extension until the new file format is implemented.  Is KiCad only other EDA besides Eagle to use .sch as the schematic file extension?"
1780578,2019-04-10 09:45:03 UTC,"@Wayne,"
1780578,2019-04-09 18:40:41 UTC,Short answer: no.
1780578,2019-04-09 08:04:17 UTC,"""kicad_sch and kicad_sym file extensions will be introduced as part of the new schematic and symbol library file format work during the v6 development. ""
So why not just changing the pattern in the file chooser or make it configurable or at least as a #DEFINE in a header file (did not look at the code, but I will, as want to change it if you dont change the extensions ;-) ?
It is no rocket science at all to change a string constant in c code."
1780578,2019-01-04 16:37:46 UTC,"I agree with Laurent. It's very annoying when I have e.g. Qt SDK installed and I can open automatically only Qt or KiCad projects. If I erroneously try to open wrong one it's painful to wait the program to open and give some message about unrecognized file, then I have to close it manually."
1780578,2018-07-11 22:02:56 UTC,"I just wanted to point out that .pro being a very common extension for any kind of development project file (software or hardware) in most users computers, the uniqueness of the extension makes the file association much easier to manage for the user. Today, if you double-click a .pro file, it will not necessarily start KiCad. It could also start an IDE or whatever. This is what this wish is mostly about."
1780578,2018-07-11 19:55:05 UTC,"kicad_sch and kicad_sym file extensions will be introduced as part of the new schematic and symbol library file format work during the v6 development.  However, legacy file formats will keep their original file extension.  Changing them doesn't make sense.  That leaves the project file extension (.prj) as the only remaining legacy file extension.  I'm not sure if it make sense to change it if we are not going to change the file format itself."
1780578,2018-07-08 17:20:20 UTC,"Related to, but not exaclt duplicates of:
https://bugs.launchpad.net/kicad/+bug/1550518
https://bugs.launchpad.net/kicad/+bug/1500570"
1780578,2019-04-13 12:14:13 UTC,About the project file extension.
1780579,2019-05-02 09:49:08 UTC,This was fixed in dd28102865a660e943c42436094c0a9fe6ef9782
1780579,2019-01-30 18:56:37 UTC,snap install --devmode --edge maas
1780579,2019-01-10 03:18:00 UTC,"We tried to deploy the snap package 2.5  today ( Jan 9 2019 ) , and the bug is still here .
The snap package is not working ."
1780587,2018-07-09 12:37:35 UTC,"O.k., I can reproduce this, but I fail to see why this could have been broken only recently, seems to me the accrc files have been untouched for years. The error looks like:"
1780590,2019-11-14 19:11:12 UTC,This bug was fixed in the package linux-firmware - 1.178.6
1780590,2020-03-31 10:51:42 UTC,This bug was fixed in the package linux - 5.4.0-21.25
1780590,2020-03-24 23:14:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'."
1780590,2020-02-18 05:46:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780590,2019-12-02 13:36:15 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34
1780590,2019-11-14 19:11:47 UTC,This bug was fixed in the package linux-firmware - 1.183.2
1780590,2019-11-14 19:08:52 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1780590,2019-04-10 01:18:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780590,2019-11-08 14:06:23 UTC,"Hello manuel, or anyone else affected,"
1780590,2019-11-08 13:56:44 UTC,"Hello manuel, or anyone else affected,"
1780590,2019-11-07 06:23:46 UTC,"Hello manuel, or anyone else affected,"
1780590,2019-11-04 04:17:30 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1780590,2019-09-04 08:06:43 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1780590,2019-09-04 08:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1780590,2019-11-14 19:08:18 UTC,This bug was fixed in the package linux-firmware - 1.173.12
1780595,2019-01-03 17:05:25 UTC,"OK, cool. Thank you for the reply."
1780595,2019-01-03 16:48:17 UTC,"Mid of December Debian installed a new libedit version, unfortunately incompatible with its 15 year old ngspice implementation, leading to a compile error. This surfaced up on Dec. 30th (https://sourceforge.net/p/ngspice/mailman/message/36504839/), when I already had tagged ngspice for version 30. Just to keep the release date 1. Jan. 2019, I agreed upon a patch with Carsten, and uploaded it with the tag 30-2. The whole ngspice-30 distribution is based on this tag. Because this libedit version (1.42.2) will trickle slowly through all Linux, Cygwin, etc. distributions, the patch is inevitable (It is just that the return type of a fuuction changed from void to int)."
1780595,2019-01-02 22:24:41 UTC,"Ok, so to me it looks like there is essentially no reason to hold off for 5.1.0."
1780595,2019-01-02 21:11:21 UTC,Nothing will happen. It will be ignored.
1780595,2019-01-02 17:25:26 UTC,"I think ngspice 28 is fairly widely available according to repology. So we may not feel that bad about adding the new thing to the startup. What will happen if people use and older ngspice and the new set ngbehavior=ps? Will it stop working, or will they just get a warning?"
1780595,2018-07-22 22:09:45 UTC,I do not want to bump the ngspice rev for 5.1.  This could limit the number of linux distros that we could build on.  Lets keep the minimum version 26 (even though it is not set in CMakeLists.txt) until 28 is widely available.
1780595,2018-07-22 15:32:14 UTC,Queueing up for 5.1.
1780595,2018-07-10 14:55:45 UTC,With the MS Windows distribution I agree immediately. It is possible for the user to exchange ngspice-26 by ngspice-28 without large efforts at his or her own 'risk' (I don't see any).
1780595,2019-01-01 10:30:12 UTC,ngspice-30 is available.
1780595,2018-07-08 21:11:18 UTC,"I'm happy with 5.1 (or even 5.0.1), but not real excited about 5.0 at this point."
1780595,2018-07-08 20:03:34 UTC,"Ngspice-27 might have received some testing, as it is available in the most recent Ubuntu, but version 28 is most likely used only by the rolling-release distributions."
1780595,2018-07-10 12:33:42 UTC,"I prefer to lean towards the tested option.  Ngspice 28 may work just fine but we really don't have a lot of testing to confirm this so for 5.0, I would prefer that we not get ahead of ourselves.  I would like the 5.0 roll out to be as painless as possible."
1780595,2018-07-08 19:33:09 UTC,"As far as I understand ngspice 28 also works with current kicad withour any patching, and the init setting is only to enable new features."
1780595,2018-07-08 19:28:40 UTC,"I sort of agree with that, but I don't see too much trouble with it. I guess people on linux have been using 27 and 28 for some time now."
1780595,2018-07-08 19:13:33 UTC,"I am afraid ngspice-28 has not been so well tested with KiCad as was the case with ngspice-26. I suggest upgrading the library in 5.1 or 6.0, it is a bit late to do it for 5.0."
1780595,2018-07-08 12:30:30 UTC,It is both:
1780595,2018-07-08 12:04:21 UTC,"I don't quite understand the purpose of this. Is it describing a bug, or is it a request to use the latest ngspice, or some guide lines on how to be able to use the latest ngspice release?"
1780597,2019-03-20 05:55:25 UTC,I see no need for this change without further explanation from the reporter.
1780597,2019-09-19 12:10:51 UTC,"Closing as there has been no activity for 60 days. If you still have this problem, check the already reported issues at https://inkscape.org/report. Thank you!"
1780598,2018-07-08 08:21:19 UTC,"The attachment ""grub-mkconfig.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1780601,2019-04-10 05:15:47 UTC,Okay
1780601,2019-04-10 05:22:32 UTC,"It remains to be a tester and a developer, then I will definitely not forget anything ... Prescribe the variable kicad_config_dir. When to use the program?"
1780601,2019-04-09 20:04:17 UTC,@Anton-  The patch allows anyone building a KiCad executable to specify the default configuration directory.  This allows future packages (or personal builds) to utilize different default configuration directories without interfering with pre-existing configurations.
1780601,2019-04-09 08:38:09 UTC,"as far as I understand, the patch appended gives the cmake command to set the environment variable kicad_config_dir to a path that matches for example the path .config/kicad5. But the variable kicad_config_dir the same for all releases and artists now. So the patch doesn't do anything practical. Despite the fact that line 5 and 6 in separate folders, will still be lining. Really it is very difficult for each branch to make the configuration folder, than to think over the mechanism of check of versions of the vedina configuration directory... This problem can be solved by preprocessor directives"
1780601,2019-04-09 08:16:21 UTC,"@Anton - when building multiple branches, it's probably easier to use git worktrees for each branch:"
1780601,2019-04-09 06:30:48 UTC,I think that -Dkicad_config_dir sets the same environment variable for all branches.
1780601,2019-04-09 06:25:48 UTC,I think that the variable will be equally valid for all branches ... This is not a solution ...
1780601,2019-04-09 06:23:33 UTC,"Is it really so difficult to redefine the cime in the cmake config file itself and give it the default value plus the branch number? Do not then go into the code itself, for now. In the downloaded branch there is exactly information about its main number."
1780601,2019-04-09 06:18:31 UTC,"O, cmake -DKICAD_CONFIG_DIR... If i want other dir like default .conig/kicad... the main thing is not to forget if I want to try the latest changes in the branch ..."
1780601,2019-04-09 06:09:40 UTC,Great!
1780601,2019-04-08 08:28:26 UTC,The question is very relevant while the projects are not yet in release.
1780601,2019-04-08 13:44:29 UTC,"Probably it happened that some branches of kicad are very stable. Therefore, moving to a new branch, which is not yet stable, it is better to use separate settings from the stable version. If we downloaded, collected and decided to try a new branch, respectively it will differ, on the graphical interface, a configuration (the difference between branches 4 and 5 is especially noticeable). I also noticed that kicad makes changes to the configuration files). Each specific branch can make them differently. If I wanted to change the settings of the program from branch 5, but while I'm working in branch 4, there may be a situation when the branch 4 modet work incorrectly (configuration file they have in common). I think it's easy to change the path from home/user/in the code.config/kicad on home/user/.config/kicad{major_version_milestone} - scripted path"
1780601,2019-04-08 13:08:33 UTC,There are lots of ways to solve this issue but I don't want to over think it.  Keep it as simple as possible to minimize the development effort.  I suspect that not many users will run multiple versions although I could be wrong.  I would be willing to bet that most users don't want to have to reconfigure all of their existing settings every time they upgrade to the latest version so multiple configs should be optional.  I suppose we could copy the latest version of the config folder to the new version but that has some downsides.
1780601,2019-04-08 10:48:36 UTC,"This might mean actually using KICAD_USER_CONFIG_DIR, which right now appears orphaned."
1780601,2019-04-08 10:30:30 UTC,"I would advocate allowing this to be set by the packaging.  Make it an advanced CMake variable that we pick up.  It would default to ""kicad"" to keep the current setting but could be updated at any point when making a new package."
1780601,2019-04-08 10:18:16 UTC,"ugh, Hit tab and can't edit comments at LP...continuing...."
1780601,2019-04-08 10:11:48 UTC,"This needs some thought, but it's certainly a very important thing to get sorted before v6 starts writing loads of new stuff to the config."
1780601,2019-04-08 08:32:44 UTC,It will be easier for you to work.
1780601,2019-04-08 08:30:56 UTC,"When will Kikad 7, we will write the same? Version 6.1 is in feature freeze. Moving to 7.0.0 milestone.))"
1780601,2018-12-11 19:25:52 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1780601,2019-04-08 19:36:13 UTC,"Fixed in revision 257d9b5fe9d39df65d8001b18507051de508241e
https://git.launchpad.net/kicad/patch/?id=257d9b5fe9d39df65d8001b18507051de508241e"
1780603,2018-07-17 19:38:32 UTC,I made a 2 min. video. Please watch and respond. https://youtu.be/Z2SQSuYG6KI
1780603,2018-07-17 22:14:07 UTC,"> @Jeff, what's confusing about being able to click the column
> headings to change the display order?
"
1780603,2018-07-18 09:58:21 UTC,"I think a filter is good, but what if the user would like to mass re-order a group of libraries? That's the problem sorting also can help to solve, as the user can add some extra text in one of the columns, sort, and click ""Re-number"". I'm open to your filter idea though. How might mass re-ordering be accomplished? Perhaps allow multiselecting and then clicking the up and down buttons to move the whole group? Or what do you think?"
1780603,2018-07-18 09:59:28 UTC,Also if you or another developer is willing to implement a filter I think that would meet a lot of needs right there as you have already indicated.
1780603,2018-07-17 19:24:06 UTC,"@Seth, view order number would be something captured by the program only--not visible to users, since the view order is obvious to the user by simply looking at the...you know, actual order of the rows on the screen."
1780603,2018-07-20 03:41:22 UTC,"@Gabriel, just out of curiosity why do you want to reorder your library
table?"
1780603,2018-07-20 03:42:17 UTC,A quick *click to sort by path column* would be a great start to solving this and other similar problems.
1780603,2018-07-20 03:43:56 UTC,"(Side question: any way to edit my response once it's been posted? I forgot the "">"" character to indicate a quote above)."
1780603,2018-07-18 12:43:46 UTC,"@Gabriel, just out of curiosity why do you want to reorder your library
table?"
1780603,2018-07-17 19:22:09 UTC,"@Seth, what do you mean by ""see an additional column""? No additional columns would be seen. It would have the same columns as the 5.0.0 version, except that the left-most column should probably be called ""Load Order"" or something instead of having no heading."
1780603,2018-07-20 12:04:58 UTC,"AFAIK you cannot edit a bug report comment on launchpad.  You can only
edit the original bug report description and title."
1780603,2018-07-17 18:17:01 UTC,"The row numbers are gone in 5.1.  Even if we put them back, though, I still think it would be confusing."
1780603,2018-07-17 18:38:12 UTC,"I don't have a strong opinion about the sort order feature.  I suppose
that it might make looking through the list of libraries easier for users."
1780603,2018-07-08 15:23:49 UTC,"The table order defines the read order, which can be important (if you have duplicate definitions).  I think adding sorting will make this much more confusing."
1780603,2018-07-08 23:29:59 UTC,Would a filter work?  I'd be much less opposed to that....
1780603,2018-07-08 23:30:39 UTC,(Hmmm... although I'm not sure how the up/down buttons would work when filtered.  Perhaps we'd just disable them?)
1780603,2018-07-08 22:12:43 UTC,"When I look at the libraries and see 330 symbol libraries, and ask myself, ""did I remember to update those 18 custom ones I made?"" how can I easily answer such a question without being able to sort the libraries by description, path, or something else? Perhaps I added those 18 one at a time and they are interspersed with others, making them hard to find. Also, perhaps I've decided to make all 65 libraries in one folder higher priority than the other 300 elsewhere. How can I do this without better sorting? Somehow a sorting system needs to be implemented to allow finding and organizing the large parts databases being created."
1780603,2018-07-12 15:32:44 UTC,"For further clarity, when you sort by the left most column it will make table order and display order coincide. You'll see.
1
2
3
4
5
Etc."
1780603,2018-07-12 15:35:03 UTC,"That's my proposal. With that in mind, see if my first post makes more sense and is more agreeable."
1780603,2018-07-17 18:12:07 UTC,I don't like the idea of adding additional complexity to this table.
1780603,2018-07-17 17:38:43 UTC,Any thoughts?
1780603,2018-07-12 15:27:23 UTC,"Id really prefer sorting buttons over a filter. I thought about my request here again and I'm not sure if I got my intent across fully, so let me try again on a couple key points.
1. Sorting buttons do not change table order. They change only table *display* order, unless you click ""Re-number rows"" (see my last bullet of main post), which changes table order but NOT display order.
2. Table order, which determines the order libraries are searched when you add symbols to a schematic, is determined by the left most column, which contains the row number. This row number is attached to that row and never changes unless you click the current move up or down buttons or the proposed Re-number button.
3. Table *display* order, based on sorting, will be a new column you add behind the scenes only (not visible to user) to retain sorting order."
1780623,2018-09-17 08:30:56 UTC,Still can reproduce this problem with 18.04.1.
1780623,2018-09-07 04:17:23 UTC,[Expired for gnome-calculator (Ubuntu) because there has been no activity for 60 days.]
1780623,2018-07-08 14:32:27 UTC,"Expected: Open a new instance when I middle-click, like with all other applications.
Actual: Middle-clicking brings up the already-running instance."
1780623,2018-09-21 14:30:51 UTC,"I suggest raising priority to high, as this bug is very frustrating and counterproductive."
1780623,2018-07-08 13:53:57 UTC,could you also give details on the ubuntu version and desktop environment you use
1780623,2018-07-08 13:53:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1780623,2018-07-08 14:31:17 UTC,System is
1780628,2018-07-08 13:47:29 UTC,apport information
1780628,2018-12-14 13:39:55 UTC,I have a same problem with the current version of Ubuntu 18.04.1 LTS (Bionic Beaver) with kernel 4.15.0-42-generic.
1780628,2018-10-05 13:01:29 UTC,And v4.19-rc6:
1780628,2018-10-05 03:24:10 UTC,"Sorry, but I meant v4.19-rc6."
1780628,2018-10-05 02:45:19 UTC,"Yes, with the most recent 4.18.12 kernel:"
1780628,2018-10-04 16:09:06 UTC,Do you still see the issue under latest Bionic kernel or latest mainline kernel?
1780628,2018-07-18 03:10:44 UTC,"[ 7609.135055] ------------[ cut here ]------------
[ 7609.135057] kernel BUG at /home/kernel/COD/linux/drivers/md/raid5.c:1762!
[ 7609.135065] invalid opcode: 0000 [#1] SMP PTI
[ 7609.135069] CPU: 2 PID: 302 Comm: md0_raid5 Not tainted 4.18.0-041800rc5-generic #201807152130
[ 7609.135071] Hardware name: Gigabyte Technology Co., Ltd. H370M-D3H/H370M D3H-CF, BIOS F3 03/01/2018
[ 7609.135078] RIP: 0010:raid_run_ops+0xbcb/0x15e0 [raid456]
[ 7609.135079] Code: 63 d2 48 8d 04 d0 48 89 45 c8 0f 84 8b 09 00 00 48 8b 7d 98 44 89 f1 31 d2 4c 89 e6 e8 8e 98 e6 ff 48 89 45 98 e9 07 f6 ff ff <0f> 0b 0f 0b e9 85 fb ff ff 8b 4d 90 89 fe e9 12 fd ff ff 4c 8b ad
[ 7609.135106] RSP: 0018:ffffa6c30135fb30 EFLAGS: 00010006
[ 7609.135108] RAX: 0000000000000000 RBX: ffff90c11b363405 RCX: 0000000000000000
[ 7609.135110] RDX: ffff90c0edc2d7c0 RSI: ffff90bf36edaec0 RDI: ffff90c0edc2d828
[ 7609.135113] RBP: ffffa6c30135fbe8 R08: 0000000000001000 R09: ffffa6c30135fac0
[ 7609.135115] R10: 0000000000001000 R11: ffff90c0edc2d848 R12: ffff90c0edc2da08
[ 7609.135117] R13: ffff90c0edc2d828 R14: ffff90c0edc2d7c0 R15: ffff90c158240800
[ 7609.135119] FS:  0000000000000000(0000) GS:ffff90c16e480000(0000) knlGS:0000000000000000
[ 7609.135122] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7609.135124] CR2: 00005644e9cf7230 CR3: 000000003a80a002 CR4: 00000000003606e0
[ 7609.135126] Call Trace:
[ 7609.135132]  handle_stripe+0x66c/0x21d0 [raid456]
[ 7609.135137]  handle_active_stripes.isra.62+0x3d8/0x5c0 [raid456]
[ 7609.135141]  raid5d+0x407/0x5f0 [raid456]
[ 7609.135147]  md_thread+0x129/0x170
[ 7609.135150]  ? handle_active_stripes.isra.62+0x5c0/0x5c0 [raid456]
[ 7609.135153]  ? md_thread+0x129/0x170
[ 7609.135157]  ? wait_woken+0x80/0x80
[ 7609.135160]  kthread+0x121/0x140
[ 7609.135163]  ? md_rdev_init+0xb0/0xb0
[ 7609.135165]  ? kthread_create_worker_on_cpu+0x70/0x70
[ 7609.135169]  ret_from_fork+0x35/0x40
[ 7609.135171] Modules linked in: xfs nls_iso8859_1 intel_rapl snd_hda_codec_hdmi x86_pkg_temp_thermal snd_hda_codec_realtek intel_powerclamp coretemp snd_hda_codec_generic kvm_intel kvm ppdev snd_hda_intel snd_hda_codec snd_hda_core irqbypass snd_hwdep snd_pcm intel_cstate mei_me mei wmi_bmof parport_pc snd_timer snd intel_rapl_perf soundcore parport input_leds intel_pch_thermal acpi_pad mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c hid_generic usbhid hid morus1280_avx2 morus1280_sse2 morus1280_glue morus640_sse2 morus640_glue aegis256_aesni aegis128l_aesni aegis128_aesni
[ 7609.135212]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 i2c_algo_bit drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt aes_x86_64 fb_sys_fops crypto_simd drm cryptd glue_helper ahci libahci e1000e wmi video pinctrl_cannonlake pinctrl_intel
[ 7609.135229] ---[ end trace 0de6b567897a8298 ]---
[ 7609.135233] RIP: 0010:raid_run_ops+0xbcb/0x15e0 [raid456]
[ 7609.135234] Code: 63 d2 48 8d 04 d0 48 89 45 c8 0f 84 8b 09 00 00 48 8b 7d 98 44 89 ..."
1780628,2018-12-17 08:06:52 UTC,"@Steve, sorry for the late reply."
1780628,2018-07-13 08:17:57 UTC,"Spoke too soon, it does still occur with 4.17.0, *however*, it much much harder to trigger."
1780628,2018-07-13 07:15:27 UTC,"This does not occur using the 4.17.0-5-generic kernel from Cosmic, so something fixed it in the n commits between 4.15.0 and 4.17.0."
1780628,2018-07-08 13:47:25 UTC,apport information
1780628,2018-07-17 19:22:12 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1780628,2018-07-08 13:47:17 UTC,apport information
1780628,2018-07-08 13:47:16 UTC,apport information
1780628,2018-07-08 13:47:14 UTC,apport information
1780628,2018-07-08 13:47:11 UTC,apport information
1780628,2018-07-08 13:47:09 UTC,apport information
1780628,2018-07-08 13:47:07 UTC,apport information
1780628,2018-07-08 13:47:05 UTC,apport information
1780628,2018-07-08 13:47:02 UTC,apport information
1780628,2018-07-08 13:47:00 UTC,apport information
1780628,2018-07-08 13:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1780628,2018-07-08 13:47:19 UTC,apport information
1780639,2019-06-03 13:21:16 UTC,"Good catch, Michele. I fixed the milestone and status, and also on another bug in the same situation (bug 1709698)."
1780639,2019-03-08 19:34:08 UTC,Pushed to master.  Thanks Cesar and Beth!
1780639,2019-05-31 16:49:12 UTC,"If I'm reading things correctly, it looks like this bug fix was released in 3.3.0, but I don't see it marked released here, or see it in release notes."
1780639,2018-12-04 23:25:55 UTC,Forgot to add a relevant branch... http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/cesardv/lp1780639_add_marc_field_758
1780639,2018-11-16 16:32:13 UTC,"Not a cataloguer so I can't add much to the discussion on the implications of this new field, but here's a marcedit-tooltips.xml for this particular field and the resulting sql statements (after running the xml thru Open-ILS/src/extras/marc_tooltips_to_sql perl script) that one would use to insert the new field data to the proper config.* tables in order to enable it on the marceditor."
1780639,2019-03-07 17:44:37 UTC,Evergreen v.3.2.4
1780648,2018-07-08 15:26:49 UTC,"Still a noob to Programming here, despite having worked with Linux for about two years now."
1780654,2018-11-08 10:30:23 UTC,"Do you have any special reason to use r8168-dkms instead of the default one, r8169?"
1780654,2018-07-21 20:41:25 UTC,"I tried after installing upstream kernel, and the error is the same:"
1780654,2018-11-07 04:22:54 UTC,I am getting the same exact bug on Ubuntu 18.04.1 with linux kernel 4.15.0-38
1780654,2018-07-11 16:08:12 UTC,Confirmed here as well.  4.15.0-24 is not usable with the r8168 8.045.08 driver.
1780654,2018-07-08 15:55:05 UTC,This is the output from the driver installer script:
1780654,2018-07-17 16:12:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1780668,2018-07-08 19:01:28 UTC,"Can you please help me with the error above. I run Ubuntu 18.04 LTS, 64bit. Python 2.7.15rc1, matplotlib version 2.2.2."
1780668,2019-10-15 08:34:24 UTC,I have the same problem.
1780677,2020-05-03 22:03:48 UTC,"I really appreciate how this community is seriously working and I don't want to offend anyone but the importance of this bug is clearly very high because you have to imagine that after running a Matlab script for several hours or working on a long document or having a scientific flow of work then you have a pause for some time then you go back to work to discover that either the computer is suspended or your monitor is ""asleep"" and by pushing a key on the keyboard there is a complete weird pixelized colorful screen !!! You are forced to perform a ""forced shutdown"" by moving back to terminal ctrl+alt+F3 in my case then 'sudo shutdown' or by pushing the shutdown button in worst scenarios. So this bug is really annoying and even with ubuntu 20.04, I'm still having the same problem."
1780677,2020-05-05 21:13:29 UTC,"It would probably be useful to open new reports for problems on focal, it's not sure the problem is the same as the ones there and would be easier to tell things apart with new logs, we can duplicate the new report from this one if needed"
1780677,2019-10-13 01:08:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780677,2019-09-18 19:17:11 UTC,For reference here are some of the tail lines in my /var/log/Xorg.0.log
1780677,2019-09-18 19:15:11 UTC,Was this ever resolved? This same thing is happening to me regularly. I'm about to give up on Ubuntu; I can't believe something so basic is broken.
1780677,2018-07-24 11:26:56 UTC,"I noticed the status is still incomplete. What additional information should be provided?
Thank you"
1780677,2018-08-22 22:55:21 UTC,"The issue is still happening when the laptop stays in standby for several hours!
This time I found something in the /var/crash directory: the new bug ID is #1788512, I'm not sure if it's related to this bug."
1780677,2018-08-26 23:29:16 UTC,Now there are errors at the bottom of the attached Xorg.1.log file:
1780677,2018-07-09 03:00:59 UTC,It sounds like some part of the system has crashed. Please:
1780677,2018-07-11 21:20:42 UTC,"Actually, this is the content of the /var/crash directory:"
1780677,2018-07-11 21:18:09 UTC,"Hi, I did apply the workaround, yet I can't find anything related in the /var/crash directory.
With my ID I only find a systemd crash on 2018-06-21 and other issues dated back to 2017 and older."
1780678,2018-08-08 17:33:32 UTC,"You're using the snap version of chromium, which is strictly confined, and thus won't let you access /dev/bus/usb/001/011 by design."
1780678,2019-11-13 10:03:00 UTC,"Tested with the Numworks calculator v0100, Ubuntu 19.10."
1780678,2019-11-25 15:33:22 UTC,@Erik: I just published an updated version of the chromium snap with the additional raw-usb plug in the candidate/raw-usb channel.
1780678,2019-11-27 08:38:16 UTC,"Yes, that did the trick.  No error messages while connecting, web-site could detect and update the device over USB without problems."
1780678,2019-11-27 09:12:52 UTC,"Excellent, thanks for testing and for the feedback Erik. I am going to add the raw-usb plug to the snap in all channels then."
1780678,2019-11-27 10:13:33 UTC,Fixed with https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=ed3b4b0217ee0959aed1dd4492ea889f63e0a598.
1780680,2018-08-22 21:00:42 UTC,artful is dead
1780680,2018-08-22 21:01:54 UTC,not that an interim release would get the same backports anyway.. upgrades are expected to happen to the next LTS and not elsewhere
1780680,2018-08-22 21:46:12 UTC,"Older versions in bionic than in xenial, as of now:"
1780689,2018-07-10 11:24:24 UTC,Is this going to be backported to 2.4.1?
1780691,2018-07-17 19:17:27 UTC,Materially changed is a little hard for the charm to figure out; however if someone want to work on figuring out an approach to determining this please do.
1780691,2019-11-08 17:46:42 UTC,Set to won't fix as liberty is no longer supported by the charms.
1780694,2018-07-09 03:57:34 UTC,Unclear. This deployment was a bit fraught because we didn't add the route to the tenant network until quite a few attempts by the charm to install the snap. Here's the (rather large) unit agent log: https://private-fileshare.canonical.com/~pjdc/jaas-candid.unit-prometheus-0.log.xz
1780694,2020-03-08 20:55:33 UTC,"If something sets prometheus.do-reconfig-yml or prometheus.do-reconfig-def while prometheus.do-install is still set, this could trigger if render() makes the missing dirs."
1780694,2018-07-09 03:32:31 UTC,"Is the race that the charm is configuring the snap before the snap has been installed, or that the charm thinks that the snap is installed but snapd is still setting it up?"
1780707,2018-07-10 21:40:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780707,2018-10-09 14:07:49 UTC,"Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
/usr/share/initramfs-tools/hooks/framebuffer: 146: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
/usr/share/initramfs-tools/hooks/framebuffer: 65: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
E: /usr/share/initramfs-tools/hooks/framebuffer failed with return 2.
/usr/sbin/mkinitramfs: 181: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/update-initramfs: 145: /usr/sbin/update-initramfs: Cannot fork
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 2"
1780712,2020-10-02 09:45:34 UTC,"Reviewed:  https://review.opendev.org/736709
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=d875568ad78cb7e6caeccfe2c43a4f8819b3ab5a
Submitter: Zuul
Branch:    master"
1780712,2020-02-07 17:09:43 UTC,"This also impacts the Kubernetes charms, and leads us to use the admin key for everything, rather than the client key, since we don't know (at least with CMR) what username the client key is associated with."
1780727,2019-06-21 15:39:48 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/666872"
1780727,2018-12-19 10:04:59 UTC,This issue was fixed in the openstack/nova 16.1.7 release.
1780727,2018-11-21 23:55:53 UTC,"Reviewed:  https://review.openstack.org/583567
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b45fcd3ba345b3f400ce729992ffdca07548b0b
Submitter: Zuul
Branch:    stable/pike"
1780727,2018-09-24 14:47:13 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1780727,2018-07-31 18:29:09 UTC,"Reviewed:  https://review.openstack.org/583566
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0be8cbc302aa77b312e031f6a7a419e83afd6e3b
Submitter: Zuul
Branch:    stable/queens"
1780727,2018-07-30 16:07:15 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1780727,2018-07-11 05:56:45 UTC,"yeah, that can be raised from [1]. I feel proceeding further if no host mapping is good way. We can discuss on patch if any side effect of that."
1780727,2018-07-18 12:59:20 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/583566"
1780727,2018-07-18 08:52:22 UTC,"Reviewed:  https://review.openstack.org/582674
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ee6e0c1e7eb861e56915c5b6c60a214b75240366
Submitter: Zuul
Branch:    master"
1780727,2018-07-13 19:44:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582674"
1780727,2018-07-13 15:40:14 UTC,"It's valid to have a compute service w/o a host mapping if the nova-compute service was started but discover_hosts was not yet run, we shouldn't block the compute service delete on that, so we should just handle HostMappingNotFound and pass."
1780727,2018-07-18 13:01:12 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/583567"
1780733,2018-07-10 16:06:14 UTC,"2018-07-03 13:54:46.576 22890 INFO neutron.agent.l3.ha [-] Router a0a373e0-18cb-4a7a-bb6d-cc79a08073b0 transitioned to master
2018-07-03 13:54:46.835 22890 INFO neutron.agent.linux.interface [-] Device qg-288fb78c-de already exists
2018-07-03 13:54:47.099 22890 INFO eventlet.wsgi.server [-] <local> ""GET / HTTP/1.1"" status: 200  len: 115 time: 0.5234120
2018-07-03 13:54:51.220 22890 INFO neutron.agent.l3.ha [-] Router 33bdd4f4-a210-4940-8f20-493842c6fb10 transitioned to master
2018-07-03 13:54:51.692 22890 INFO eventlet.wsgi.server [-] <local> ""GET / HTTP/1.1"" status: 200  len: 115 time: 0.4726341
2018-07-03 13:55:06.080 22890 INFO neutron.agent.linux.interface [-] Device qg-67869a46-c1 already exists
2018-07-03 13:55:06.164 22890 INFO neutron.agent.linux.interface [-] Device qg-01c91ec6-cd already exists
2018-07-03 13:55:10.951 22890 WARNING neutron.agent.l3.agent [req-7933daac-8697-48da-86ba-6462129d5f4d - a5190d3e49c742ee88fbc08cd0e19de2 - - -] Info for router a0a373e0-18cb-4a7a-bb6d-cc79a08073b0 was not found. Performing router cleanup
2018-07-03 13:55:11.876 22890 ERROR neutron.agent.linux.utils [req-0bd86687-ab84-4ece-9abb-50b4ba2ee1b2 - 1a012f04519349069c1a630c1fe51b0a - - -] Exit code: 1; Stdin: ; Stdout: ; Stderr: Cannot find device ""ha-8ff09182-35"""
1780733,2018-07-10 16:59:36 UTC,This looks like the relevant traceback http://paste.openstack.org/show/725441/
1780733,2018-07-10 15:55:04 UTC,"Hey Jonathan,"
1780733,2018-07-10 15:55:10 UTC,This is from /var/log/neutron/neutron.log
1780734,2018-07-17 19:09:27 UTC,"Looking at the log, it shows that grub-efi was correctly installed, then for some reason, grub-efi was removed, and grub-pc installed instead, then the install crashes."
1780746,2018-07-09 15:34:10 UTC,I've attached the Debian bug that was used to track this. It is fixed there and that version is found in Ubuntu Cosmic. The specific fix would need to be SRU'ed back to Bionic.
1780746,2018-08-24 05:52:21 UTC,"If you've come here because you have this issue in bionic/18.04 and there's no fix yet, then you can download these two packages:
https://packages.ubuntu.com/xenial/amd64/oping/download
https://packages.ubuntu.com/xenial/amd64/liboping0/download
And install them manually with dpkg -i
oping will work again for you"
1780752,2018-10-24 10:04:10 UTC,"I confirm the issue I reported in comment #7 has been fixed.
After installing openvswitch-common, openvswitch-switch, python-openvswitch 2.9.2-0ubuntu0.18.04.2 the neutron-openvswitch-agent continued working and after restarting neutron-openvswitch-agent network traffic between running instances was working again.
Restarting the neutron nodes also worked, neutron-ovs-cleanup.log did not complain about the missing compat module anymore.
(leaving formal verification to the openstack team, as mentioned in the bug description)"
1780752,2019-01-28 09:35:48 UTC,This bug was fixed in the package openvswitch - 2.9.2-0ubuntu0.18.04.2
1780752,2019-01-07 10:54:32 UTC,Verified successfully for xenial-queens-proposed:
1780752,2019-01-07 10:53:54 UTC,Verified successfully for bionic-proposed:
1780752,2018-11-13 10:10:34 UTC,"Hello James, or anyone else affected,"
1780752,2019-01-28 09:35:53 UTC,"The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1780752,2018-10-23 15:40:32 UTC,"Hello James, or anyone else affected,"
1780752,2018-10-18 08:37:24 UTC,"After installing this upgrade, my openstack neutron services didn't start anymore.
Neutron log shows:
2018-10-18 08:08:10.573 16703 CRITICAL neutron [-] Unhandled error: ImportError: No module named compat
...
2018-10-18 08:04:30.302 14895 ERROR neutron   File ""/usr/lib/python2.7/dist-packages/ovs/db/custom_index.py"", line 12, in <module>
2018-10-18 08:04:30.302 14895 ERROR neutron     from ovs.compat import sortedcontainers
2018-10-18 08:04:30.302 14895 ERROR neutron ImportError: No module named compat"
1780752,2018-10-13 01:03:57 UTC,"Hello James, or anyone else affected,"
1780752,2018-10-03 08:33:26 UTC,Uploaded to bionic UNAPPROVED queue for SRU team review.
1780752,2018-08-30 20:55:15 UTC,"This bug was fixed in the package openvswitch - 2.10.0-0ubuntu2~cloud0
---------------"
1780752,2018-08-28 01:35:47 UTC,This bug was fixed in the package openvswitch - 2.10.0-0ubuntu2
1780752,2018-08-21 13:30:30 UTC,Does this include the fix in Bug #1737866? Do you perhaps have an ETA on a release? Thanks!
1780752,2018-10-18 16:15:07 UTC,I see the patch we need to pick - doing so now with a revised upload.
1780755,2018-07-09 09:49:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/580979"
1780755,2018-07-11 08:03:02 UTC,"Reviewed:  https://review.openstack.org/580979
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-openstack_hosts/commit/?id=8587e33f53034c96eb26ba3b2c8f8a7b385dbcf7
Submitter: Zuul
Branch:    stable/pike"
1780755,2019-04-26 17:13:42 UTC,This issue was fixed in the openstack/openstack-ansible-openstack_hosts 16.0.29 release.
1780759,2018-07-10 02:30:00 UTC,It appears it's your compiler that crashed when updating the Nvidia driver. Not a bug in the driver itself. Reassigning to the compiler.
1780761,2018-07-17 15:57:54 UTC,"This bug may be fixed by the following commit, which is in Xenial -proposed:
758c626 xen-netfront: Fix mismatched rtnl_unlock"
1780761,2018-07-16 13:56:51 UTC,Installed and tested kernel 4.15.0-24: also affected
1780761,2018-07-18 09:40:45 UTC,Thank you. Tested on 4.4.0-131-generic from xenial-proposed. I can confirm that it resolves the bug.
1780761,2018-07-09 11:00:07 UTC,This change was made by a bot.
1780761,2018-07-13 09:39:27 UTC,"We have performed kernel bisect, git bisect log is attached.
The results show:"
1780775,2018-07-15 23:56:56 UTC,"second patch, updated version."
1780775,2018-07-15 23:55:44 UTC,"The attachments to this comment are updated versions of the first two patches given above, to fix control-handle locking and tip information, respectively. However, the redundant calls to PathManipulator::writeXML() have been removed."
1780775,2018-07-14 11:59:50 UTC,The patch attached to this comment fixes the undo/redo bug described above.
1780775,2018-07-13 17:32:01 UTC,"It appears that there is another node-editing bug, related to ""undo""
functionality. Since this bug report is still open, and some of the same
code is involved, I will describe it here, rather than opening another
bug report."
1780775,2019-03-24 01:39:58 UTC,further discussion of these issues may be found here:
1780775,2018-07-13 14:54:35 UTC,"It appears that the code responsible for control-handle locking when
converting a cusp node to smooth is in <src/ui/tool/node.cpp>, lines
286-292:"
1780775,2018-07-09 13:51:54 UTC,"Apparently, the ""Auto node handle"" message is relevant, and correct, in the case that the node type is actually ""auto-smooth"", where dragging the control handle really does convert the node type to ""smooth""."
1780775,2018-07-09 12:31:53 UTC,"It is perhaps worth mentioning that while the mouse is hovering over the control handle, the following text appears in the information box at the bottom of the Inkscape window:"
1780775,2018-07-13 15:22:04 UTC,"The second patch here attached alters the tip information displayed
during path node editing, to more accurately describe the actions
available for the control that the mouse is currently hovering over, as
discussed above."
1780781,2018-11-28 09:31:45 UTC,"The last update included mercurial security upgrade, but the situation remains the same:"
1780790,2019-02-10 19:03:03 UTC,I've reproduced the issue in a new session in Firefox 65.0. I used Firefox sync to get my stuff over. Testing with a fully empty session is harder because I need bookmarks and other stuff to be able to use the browser and this doesn't happen at will.
1780790,2020-05-04 20:28:36 UTC,"This happens to me as well. I too have two monitors, and sometimes the menu is even on the wrong monitor. Oddly enough, if I click off then right-click again (right away), the menu appears correctly. It's almost as if it is triggered by not being invoked after x amount of time."
1780790,2020-05-04 20:27:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780790,2020-04-03 17:39:41 UTC,"Created attachment 9138112
Menus appearing in the wrong place"
1780790,2020-04-01 19:00:54 UTC,"I run on a laptop with two external monitors, arranged above the laptop screen in a ""T"" configuration. Hence the screenshot shows the black area in the lower left. I am clicking on a folder on the bookmarks toolbar and the menu shows up in an adjacent screen. This makes it considerably harder to use when there are a lot of windows open. This started happening for me with the 73.0.0 release of FF. Other menus and pop-ups, driven by the browser have similar issues."
1780790,2020-04-01 18:57:44 UTC,"Created attachment 9137552
menus open offset to browser window - Ubuntu 18.04 FF 73.0.0."
1780790,2019-12-03 07:34:37 UTC,"I have a similar issue, in my case with the Bookmark bar's folders and the system menu. I also cannot reproduce this at will, but today it happened consistently enough to make a short recording. I'm on Pop_OS (System76's flavor of Ubuntu 19.04) with the default Gnome Desktop, Firefox 70.0.1 is installed from packages and maximized on the screen."
1780790,2019-05-12 16:38:35 UTC,I see the tooltip and context menu issue repeatedly. I'm now on a fresh install of Ubuntu 19.04 on Wayland and running Firefox 66.0.4. So it doesn't seem to be anything too specific to my install.
1780790,2018-10-21 19:56:41 UTC,*** Bug 763312 has been marked as a duplicate of this bug. ***
1780790,2020-04-03 17:35:50 UTC,"I neglected to mention that my setup also has a laptop connected to an external screen (with very different resolutions). I don't think I've reproduced this with the screen detached, so maybe this is a clue to the origin of the bug?"
1780790,2018-10-19 15:19:12 UTC,"It's natural that you can't reproduce this at will. I can't either. Unfortunately the sequence of steps needed to reproduce this is not yet clear to me. I've been trying to find out what they are but don't have any conclusions yet. With that in mind, testing different versions or profiles is hard to do conclusively."
1780790,2018-10-19 12:07:32 UTC,"I verified this issue on Ubuntu 18.04 with FF 64.0a1 (2018-10-19) (64-bit) and I cannot reproduce it.
Can you please test this in safe mode? Here is a link that can help you: https://goo.gl/AR5o9d.
I think it will be a good idea to retest this on the latest Firefox Nightly. Here is a link form where you can download it: https://nightly.mozilla.org.
If you still have the issue please create a new profile, you have the steps here: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager"
1780790,2018-10-16 10:45:27 UTC,Bug submitted here:
1780790,2018-10-16 10:43:47 UTC,"Created attachment 9017453
Screenshot of the first issue"
1780790,2018-10-15 17:39:12 UTC,"Thanks for the feedback Pedro. At this point, a bug report upstream wouldn't hurt, maybe that's a known issue."
1780790,2018-10-21 07:40:30 UTC,*** Bug 1240552 has been marked as a duplicate of this bug. ***
1780790,2018-10-13 14:02:37 UTC,I haven't been able to replicate it in a Unity session but I can't replicate this at will in gnome-shell either so it's hard to confirm it's a gnome-shell issue. I wouldn't be surprised though as it's been extremely buggy so far.
1780790,2018-10-10 14:50:37 UTC,"Thanks for the report Pedro. Let's try and narrow down the issue first, before reporting it upstream. I wonder if this could be specific to gnome shell. I've tested here (I'm on Ubuntu 18.10 and running firefox beta (63.0 beta 13) and I cannot see the issue."
1780790,2018-10-05 11:21:07 UTC,This is an extremely annoying bug which creates quite a lot of lack of polish of the desktop. Should I be submitting it upstream or something?
1780800,2018-07-09 14:50:10 UTC,"Dear staff, I would like to have a help to solve this problem that I have with the application Openshot, if the stable update is available for my version ubuntu studio, let me have the link or steps to update it to the latest version"
1780805,2020-01-20 15:11:30 UTC,I am using a workaround to be able to use the X310 which is download the missing files manually and copy to the expected location.
1780805,2019-07-25 12:32:36 UTC,I can also confirm this problem. USRPs X310 seem to be unusable with distribution uhd packages due to this issue.
1780805,2019-01-04 15:39:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780809,2018-07-09 20:32:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780810,2018-07-18 20:51:36 UTC,"We had a library report this, as well. (Oddly enough our report was one day after this bug was posted)."
1780810,2018-07-18 20:51:50 UTC,Forgot to add that we are on 3.0.8.
1780810,2018-07-19 00:18:35 UTC,We do use Hatch. I hadn't thought that it might be causing the problem. What you describe may be a good temporary work-around but it isn't practical for front line staff to switch back and forth between Hatch settings to perform different functions while at the circ desk.
1780810,2018-07-19 13:01:20 UTC,"FYI, there is ongoing development (thanks to Bill Erickson!) to move storage of local settings to the server instead of through Hatch, which should resolve a lot of stored setting/Hatch issues."
1780810,2018-07-19 13:37:33 UTC,I am very much looking forward to that development.
1780815,2020-11-12 15:36:05 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1780815,2021-01-12 04:17:29 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1780817,2018-09-19 23:21:07 UTC,"Tested with v4.19-rc4 mainline build, and the bug still exists."
1780817,2018-09-12 00:12:21 UTC,"I can confirm this, the issue showed up in 4.14.  I have tried a number kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/, and found that somewhere between 4.13.16 and 4.14.0 this bug introduced itself."
1780817,2018-09-13 20:47:17 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1780817,2018-07-17 19:12:53 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1780817,2018-09-03 15:24:29 UTC,"those image also related to xenial.
apt-cache policy linux-image-virtual-hwe-16.04
linux-image-virtual-hwe-16.04:
  Installed: 4.15.0.33.55
  Candidate: 4.15.0.33.55
  Version table:
 *** 4.15.0.33.55 500
        500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status"
1780817,2018-07-09 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1780819,2018-09-18 18:34:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780829,2018-07-09 17:30:13 UTC,This change was made by a bot.
1780835,2018-07-10 13:32:23 UTC,Source file:  en/partitioning/tree.xml
1780836,2018-09-08 04:10:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780837,2018-07-17 16:52:47 UTC,"Possibly related upstream bug:
https://bugzilla.xfce.org/show_bug.cgi?id=12975"
1780842,2018-07-25 12:18:49 UTC,Solution in bug 1753796 seems to solve the issue.
1780842,2018-07-10 06:31:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780846,2018-08-22 07:58:07 UTC,"Curtis, what I did was 1. I updated the system: the packages are not ""held"" on my system, so I got the new xorg-server and the new mesa libraries 2. I rebooted the computer and noticed that the XFCE menu is broken, it behaved the same as without the fix 3. after downgrading mesa libraries (see comment #21) and rebooting the computer again the menus were OK"
1780846,2018-08-22 15:20:59 UTC,"Daniel, the KDE menu bar colour problem I experienced and noted in bug #1780664 also went away when I upgraded to the new xorg-server."
1780846,2018-08-22 16:43:26 UTC,The update to xserver-xorg-core 2:1.18.4-0ubuntu0.8 doesnt seem to fix the menu bug for me.
1780846,2018-08-21 16:09:17 UTC,"Daniel, can you try rebooting your computer or otherwise restarting the xserver and then re-testing?"
1780846,2018-08-22 16:48:50 UTC,I reverted to the correct behaviour by
1780846,2018-08-22 17:48:00 UTC,so you all are using nouveau?
1780846,2018-08-22 18:22:08 UTC,"@Timo, I am using Intel HD Graphics and no longer experience issues as described in this report."
1780846,2018-08-22 18:28:00 UTC,I am using nouveau
1780846,2018-09-05 02:45:28 UTC,Ditto. I created a bootable DVD with 18.04 and booted it on the machine: it does NOT have this issue.
1780846,2018-08-22 20:58:09 UTC,"well, there's probably a regression in the nouveau driver then.. does 18.04 have the same issue or not?"
1780846,2018-09-04 15:50:00 UTC,"Hello, I plan to create a DVD or flash with live 18.04, boot it on the machine and test the bug. I had a vacation, so I didn't do it yet."
1780846,2018-09-04 21:19:37 UTC,"Well, I created a bootable DVD with 18.04 and booted it on the machine: it does NOT have this issue."
1780846,2018-09-05 04:10:10 UTC,"Hi,
Besides issues with buttons I experience transparency in dialog menus (where should not be any transparency).
The updated xorg does not help (I've double check this).
Downgrade mesa fixes this.
I use nouveau with
VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)"
1780846,2018-09-18 20:39:11 UTC,(Another workaround for this bug would be to use the proprietary driver for Nvidia instead of nouveau. I am not planning to do this (yet?) )
1780846,2019-06-29 15:13:48 UTC,"Hello, I solved this by upgrading to the HWE kernel and Xorg"
1780846,2018-08-20 19:47:25 UTC,This bug was marked as a duplicate of bug #1780664
1780846,2018-08-22 19:38:35 UTC,I am also using nouveau
1780846,2018-07-14 20:29:42 UTC,"Like David, I downgraded the mesa packages in order for the problem to disapear. The package system needed the old libllvm library (unfortunately, I purged it with ""sudo apt autoremove"" before) so my command line for this downgrade/fix was"
1780846,2018-07-11 18:31:27 UTC,"David, if the workaround in Bug #1780664 works in our case (i.e. for this bug) we should change the affected component from ""libdrm"" to ""mesa"": I was searching for something related to graphics drivers to be responsible for this bug, thought it was libdrm, but it can be mesa, too. Have you tried the workaround? I did not for now, I have a lot of work to do till weekend: and in my case Firefox, Mplayer, Dosbox and Vim work fine, which are the programs I use most, so I am not very pressured to do the fix, maybe I will wait until the official fix is out."
1780846,2018-07-11 18:33:35 UTC,"changing package to ""mesa"" according to comment #17"
1780846,2018-07-09 19:21:15 UTC,"Example of gimp action menu.
Red backgrounds and black icons instead of coloured"
1780846,2018-07-09 19:29:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780846,2018-07-09 19:33:18 UTC,"This bug affects me, too. I suspect libdrm update did this. (I am not sure though). They updated this package in order for changes HWE kernel (see http://changelogs.ubuntu.com/changelogs/pool/main/libd/libdrm/libdrm_2.4.91-2~16.04.1/changelog ) - but some people (including me) still use the GA kernel (4.4). The GA kernel should be supported for the entire lifespan of Ubuntu 16.04, so the graphics shouldn't be broken."
1780846,2018-07-09 19:36:25 UTC,David Mckelvie is using
1780846,2018-07-11 19:44:41 UTC,Thanks to Patrick Wigmore and Curtis Gedak for diagnosing the problem and coming up with a way to revert the problem.
1780846,2018-07-09 19:45:13 UTC,my kernel version:
1780846,2018-07-09 19:53:21 UTC,my graphics card information can be useful here:
1780846,2018-07-09 19:58:27 UTC,Ditto. Also using that kernel
1780846,2018-07-09 19:37:39 UTC,I am using Xubuntu desktop
1780846,2018-07-09 20:32:38 UTC,Also using NVIDIA Quadro and nouveau driver
1780846,2018-07-09 21:24:01 UTC,"David, the bot in comment #11 suggests us to file this bug against some specific package rather than Ubuntu in general: I don't want to do this myself, since it's you who reported the bug and I don't want to ""hijack"" it: I suggest we set this bug against either libdrm-common, or (maybe better) libdrm-nouveau2 - do you agree?"
1780846,2018-07-10 08:30:35 UTC,"I dont know enough to be sure whether or not libdrm-nouveau2 is the responsible package.
But I will change the package on this ticket to that, if it helps get it more attention."
1780846,2018-07-11 13:17:23 UTC,Possible related or duplicate bug #1780664
1780846,2018-07-11 17:39:06 UTC,Thanks @Patrick for the link between the bug reports.  Bug #1780664 contains instructions on how to revert to earlier libgl-mesa package versions while we wait for a fix.
1780846,2018-07-11 18:22:47 UTC,I was able to work-around this issue by rolling back only the *libgl-mesa* packages from version 18.0.5-0ubuntu0~16.04.1 to version 17.2.8-0ubuntu0~16.04.1.
1780846,2018-07-09 20:23:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1780857,2021-02-17 17:08:44 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1780858,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1780864,2018-07-09 22:10:07 UTC,"StacktraceTop:
 pkgCache::PkgIterator::PkgIterator (Owner=..., this=0x7ffc7173ea10) at include/apt-pkg/cacheiterators.h:156
 pkgCache::PkgBegin (this=0x494649544e454449) at include/apt-pkg/pkgcache.h:794
 pkgDepCache::PkgBegin (this=0x2ebaf70) at include/apt-pkg/depcache.h:359
 EIPP::WriteRequest (Cache=..., output=..., flags=flags@entry=0, Progress=Progress@entry=0x0) at ../apt-pkg/edsp.cc:1167
 EIPP::OrderInstall (solver=<optimized out>, PM=PM@entry=0x2ebe460, flags=0, Progress=Progress@entry=0x0) at ../apt-pkg/edsp.cc:1118"
1780864,2018-07-10 02:08:22 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1780878,2020-10-30 10:41:28 UTC,Can anyone update for this issue? We need fix for blueman in 18.04.
1780878,2020-10-21 07:35:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780878,2018-07-24 08:57:11 UTC,Also confirmed that this borks LXDE on xenial as well.
1780878,2020-10-21 07:34:39 UTC,"Debian has released fix in 2.0.6-1, but Ubuntu only updated this version in focal, bionic and xenial users are still encountering this issue."
1780883,2018-07-10 08:33:08 UTC,Could you please show us the l3agent and neutron conf for move forward? I suspect you hit the same issue with https://bugs.launchpad.net/neutron/+bug/1779978
1780883,2018-07-10 08:57:37 UTC,Ml2 is Linuxbridge :
1780883,2018-07-29 23:49:00 UTC,a feedback provided
1780883,2018-07-29 23:56:15 UTC,"looking at the code, the analysis in Bug Description looks correct."
1780885,2018-07-10 01:43:55 UTC,"Further info: I am running bionic, upgraded from xenial -> zesty -> bionic, and have done previous apt-get upgrade's in bionic without running into this issue."
1780886,2018-09-08 19:25:37 UTC,The problem persists in StickyNotes 1.0. Mint is unsure that it is its problem (see https://github.com/linuxmint/Cinnamon/issues/7697).
1780886,2019-02-11 20:51:14 UTC,"Thanks for the report. I've commented on the bug on Cinnamon and if they are able to suggest what I should do, I will try to address. From my knowledge of how this works, I don't think there's a problem on the indicator-stickynotes side."
1780907,2018-07-10 16:58:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780907,2018-07-11 10:51:11 UTC,"I'm just boot into ubuntu live image, start gparted, resize my partitions and give +500Mb for first FAT32 partition /boot/efi. Then update normally.
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 223,6G  0 disk
├─sda1   8:1    0   982M  0 part /boot/efi
├─sda2   8:2    0   479M  0 part /boot
├─sda3   8:3    0    56G  0 part /
└─sda4   8:4    0 166,2G  0 part /home"
1780909,2019-07-09 08:48:40 UTC,I had also even more severe problems with the rtl8812au module lately. Regularly the whole system froze and a restart was necessary.
1780909,2019-07-09 08:30:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780909,2018-07-10 06:53:05 UTC,This patch fixes the problem by initializing the cfg80211_roam_info struct.
1780909,2018-07-10 08:23:37 UTC,"The attachment ""patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1780913,2018-08-10 17:43:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780913,2018-07-26 02:13:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780913,2018-08-09 14:00:38 UTC,This looks like breakage in debconf:
1780916,2019-03-01 18:32:28 UTC,mlangermann: are there please any drawbacks to the temporary solution you kindly offered (i.e. why did you call it temporary)?
1780916,2019-02-21 14:30:34 UTC,"a temporary solution is to set
tls_session_timeout: 0
in /etc/imapd.conf to disable tls session caching."
1780916,2019-03-01 18:36:43 UTC,Please any chance of getting this fixed in the 18.04 LTS (Bionic)? It seems the package is hardly usable without this fixed.
1780916,2019-02-20 10:33:59 UTC,"still waiting for an update...
Is there an easy way to get a newer version for Ubuntu 18.04?"
1780916,2019-05-05 08:12:36 UTC,"Hi,"
1780916,2018-08-22 07:48:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1780916,2018-08-22 07:44:02 UTC,"This is also a real problem for outlook clients, leading to frequent disconnected sessions.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863520
for a very small patch to the 2.5.10-3ubuntu version.
I have applied this patch on our mailserver running on ubuntu 18.04 and
it fixes the issue"
1780916,2018-07-10 07:59:19 UTC,"This bug is really annoying, especially if you have lot's of MacOS / iPhone / iPad clients connecting to your server."
1780916,2018-10-05 09:33:38 UTC,"Will the patched version ever land in Ubuntu 18.04? If not, I'll patch the server myself.
I'm a bit surprised (and disappointed - seeing the seriousness of this bug and the wide range of devices it affects) that the package hasn't been updated yet."
1780930,2018-07-11 13:03:26 UTC,"Hello James, or anyone else affected,"
1780930,2018-07-27 08:33:45 UTC,"Hello James, or anyone else affected,"
1780930,2018-07-30 13:16:44 UTC,xenial-proposed:
1780930,2018-07-30 14:21:41 UTC,trusty/mitaka-proposed
1780930,2018-08-02 19:33:25 UTC,This bug was fixed in the package ceph - 10.2.10-0ubuntu0.16.04.1
1780930,2018-08-02 19:33:45 UTC,"The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1780930,2018-08-15 10:25:43 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1780930,2018-08-15 10:25:45 UTC,"This bug was fixed in the package ceph - 10.2.10-0ubuntu0.16.04.1~cloud0
---------------"
1780947,2018-07-10 11:36:02 UTC,"The admin endpoint only ever made sense for keystone v2, since now keystone only supports v3, it should be dropped everywhere."
1780947,2018-07-10 13:29:44 UTC,Thanks for quick response!
1780953,2018-07-10 14:19:20 UTC,"Hi. It happens while drawing a unit, but I cannot say what caused this crash without checking the crash dump file. Can you upload it to a one-click hoster, or if you haven't gotten a crash dump yet, create one when the game crashes next time? Zipping usually makes it a lot smaller, and then I can take a look."
1780953,2018-07-11 07:58:10 UTC,Thank you!
1780953,2018-07-11 15:35:46 UTC,Thanks a lot for the help!
1780953,2018-07-11 16:39:59 UTC,"Secondly I've also noticed an IEP C0000005 at 0069E800 which ive seen one instance of it being reported on PPM but no public solution.
I've had about 4 times similarly for unknown reasons.
(except.txt and the dump attached)"
1780953,2018-07-13 14:42:02 UTC,"From what I see, it crashed while drawing the base shape of the building AIRPAD with Image=NAPAD. The shape file has a width of 0, a height of 22792, and 32231 frames. Not sure what happened. The shape file could be corrupt, or it has been unloaded again, and the memory was reused while the game somehow retained a pointer to it."
1780955,2019-07-14 14:44:20 UTC,Please provide a screencast of the problem.
1780955,2019-09-13 04:17:22 UTC,[Expired for Variety because there has been no activity for 60 days.]
1780958,2018-07-10 12:29:24 UTC,"Throbber not yet added.
Links to site should be more prominent."
1780970,2019-01-28 15:29:47 UTC,"Needs further discussion of what exactly we want to expose, in what format, and public vs. brand store snaps."
1780970,2019-03-13 18:10:43 UTC,"Note that the build URL for snap revisions is already available at the ""snap revisions"" endpoint of the developer API[0] - but it needs authentication and permission to view the snap.
E.g.:"
1780970,2018-07-26 21:25:00 UTC,"A link to the build URL for each revision is now shown in the developer dashboard, if available (at https://dashboard.snapcraft.io/snaps/SNAPNAME/revisions/NNN/)."
1780970,2018-07-24 15:55:57 UTC,Thanks for looking into this! :)
1780970,2018-07-24 15:33:06 UTC,"As Colin mentioned, the store does have indeed this information in the manifest.yaml file, so it should be fairly simple to expose the build_url from the image-info section in the yaml."
1780970,2018-07-12 09:30:57 UTC,Launchpad has included this information in snaps it builds since late April or thereabouts (https://code.launchpad.net/~cjwatson/launchpad-buildd/snap-image-info/+merge/341806): it's in image-info.build_url in snap/manifest.yaml.  The store should be able to pick it up from there.
1780971,2018-07-18 06:25:13 UTC,psusi: You've kind of cherry picked one possible way of looking at this problem out of many different ways of solving it.
1780971,2018-08-03 18:52:29 UTC,"On 7/18/2018 2:25 AM, Steven Maddox wrote:

> psusi: You've kind of cherry picked one possible way of looking at this
> problem out of many different ways of solving it.
>
> You've also completely deleted my bug description and rephrased it down
> to a single sentance - yet it still has my name on it.
>
> I can't say I'm very happy about it.  I'd rather you start your own bug
> in YOUR name... then close mine and say it is a duplicate of that.
"
1780971,2018-08-03 21:16:48 UTC,It is a novel you are right.
1780973,2019-09-27 09:03:42 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1780973,2019-07-10 21:39:34 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1780973,2019-06-18 03:40:52 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1780973,2019-06-11 23:17:04 UTC,"Reviewed:  https://review.opendev.org/660375
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0c9f98f64fdd845c1a26348418164e55a37042d0
Submitter: Zuul
Branch:    stable/rocky"
1780973,2019-06-06 06:23:56 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1780973,2019-07-02 22:31:20 UTC,"Reviewed:  https://review.opendev.org/662471
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=95a3e0cf6aee8f278a1441f3e50517f08c6f3038
Submitter: Zuul
Branch:    stable/queens"
1780973,2019-05-23 02:07:07 UTC,"Reviewed:  https://review.opendev.org/660370
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4ff46ff7677530bce3ef268b6a0d85b50308d2fd
Submitter: Zuul
Branch:    stable/stein"
1780973,2019-05-21 12:45:10 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/660375"
1780973,2019-05-21 12:36:53 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660370"
1780973,2019-05-21 12:27:56 UTC,"Reviewed:  https://review.opendev.org/551349
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c480a75edc0f5f1b446121491869c02f30437a0
Submitter: Zuul
Branch:    master"
1780973,2019-05-31 13:55:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/662471"
1780974,2018-07-10 14:08:59 UTC,"For the sake of the completeness: no message is displayed in the horizon dashboard, the user is only redirected again and again to the login form, making it hard to understand what the problem could be."
1780974,2018-08-03 15:40:24 UTC,"Aside from the inconvenience posed by changing this setting manually, I haven't looked too closely at the differences between the session engines, and I'm not sure if selecting `django.contrib.sessions.backends.cache` is a mistake for other reasons. Can anyone confirm that this is an acceptable workaround in the interim? Thanks!"
1780974,2018-10-03 13:27:10 UTC,It looks like a configuration issue which should be fixed in devstack
1780979,2018-07-10 15:07:45 UTC,apport information
1780979,2018-07-10 15:07:46 UTC,apport information
1780979,2018-07-17 17:07:57 UTC,The files might be empty if all the sequences are marked ok.
1780979,2018-07-10 17:56:23 UTC,"` ... and then change the status of the bug to 'Confirmed'... `
OK, but it seems strange. The help tooltip shown when changing the status says the bug is supposed to be 'Verified by someone other than the reporter.'."
1780979,2018-07-10 15:07:48 UTC,apport information
1780979,2018-07-10 15:07:50 UTC,apport information
1780979,2018-07-10 15:07:44 UTC,apport information
1780979,2018-07-10 15:07:47 UTC,apport information
1780979,2018-07-10 15:07:43 UTC,apport information
1780979,2018-07-10 15:07:38 UTC,apport information
1780979,2018-07-10 15:07:41 UTC,apport information
1780979,2018-07-10 15:07:40 UTC,apport information
1780979,2018-07-10 15:07:39 UTC,apport information
1780979,2018-07-10 15:07:37 UTC,apport information
1780979,2018-07-10 15:07:36 UTC,apport information
1780979,2018-07-10 15:07:35 UTC,apport information
1780979,2018-07-10 14:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1780979,2018-07-10 15:07:42 UTC,apport information
1780987,2018-07-10 14:47:02 UTC,"For better readability, please find the command-line execution trace here:"
1780993,2018-07-11 09:51:05 UTC,"Odd, I've just seen the in the INSTALL.md file a note about the `tls.conf` file uploaded. So I've removed my added `SSLCipherSuite` from `www.apache2.conf` and also in `seccdn.apache2.conf` and everything is still working.
Will adapt PR."
1780993,2018-07-10 15:20:53 UTC,Pull request open https://code.launchpad.net/~kumy/libravatar/+git/libravatar/+ref/bug-1780993
1780996,2018-07-26 09:43:10 UTC,This bug was fixed in the package dovecot - 1:2.2.22-1ubuntu2.8
1780996,2018-07-26 09:42:59 UTC,This bug was fixed in the package qgis - 2.8.6+dfsg-1ubuntu1
1780996,2018-07-26 09:42:54 UTC,This bug was fixed in the package wokkel - 0.7.1-1ubuntu0.16.04.1
1780996,2018-07-26 09:42:45 UTC,This bug was fixed in the package yorick - 2.2.04+dfsg1-5ubuntu1
1780996,2018-07-26 09:42:43 UTC,This bug was fixed in the package django-countries - 3.4.1-2ubuntu1
1780996,2018-07-26 09:42:33 UTC,This bug was fixed in the package nevow - 0.13.0-1ubuntu1
1780996,2018-07-26 09:42:30 UTC,This bug was fixed in the package neurodebian - 0.37.2ubuntu1
1780996,2018-07-26 09:32:44 UTC,This bug was fixed in the package bumblebee - 3.2.1-10ubuntu1
1780996,2018-07-26 09:32:40 UTC,This bug was fixed in the package octave - 4.0.0-3ubuntu9.2
1780996,2018-07-17 23:55:50 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-26 09:32:29 UTC,This bug was fixed in the package tex-common - 6.04ubuntu1
1780996,2018-07-26 09:32:23 UTC,This bug was fixed in the package xpdf - 3.04-1ubuntu1.1
1780996,2018-07-26 09:32:20 UTC,This bug was fixed in the package hicolor-icon-theme - 0.15-0ubuntu1.1
1780996,2018-07-26 08:12:26 UTC,"After some discussion with Brian on the SRU verification procedures for this bug, we decided that the upgrade test done in #51 is sufficient for verification of this bug. For syslog-ng-incubator the upgrade test was a bit more complicated due to it conflicting with ubuntu-minimal - so there's no good way to get it tested anyway."
1780996,2018-07-23 08:44:14 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-19 20:08:30 UTC,"Just to see what would happen I installed a bunch of these packages on an Ubuntu 16.04 system w/o -proposed enabled, I then enabled -proposed and upgraded the packages without any issue."
1780996,2018-07-19 15:48:52 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-18 09:20:56 UTC,"I'm not convinced that noawait is the right choice for libomxil-bellagio-bin. The plugins are unusable without being registered. That said, nothing depends on libomxil-bellagio-bin now, so the trigger might never get run in the first place - switching to noawait does not make it any more fragile:"
1780996,2018-07-18 00:54:14 UTC,This bug was fixed in the package guile-2.2 - 2.2.3+1-5ubuntu1
1780996,2018-07-26 09:43:22 UTC,This bug was fixed in the package syslog-ng-incubator - 0.3.3-2ubuntu1
1780996,2018-07-26 09:32:35 UTC,This bug was fixed in the package packagekit - 0.8.17-4ubuntu6~gcc5.4ubuntu1.3
1780996,2018-07-26 09:52:36 UTC,This bug was fixed in the package mate-icon-theme - 1.12.0-1ubuntu0.1
1780996,2018-07-26 09:53:00 UTC,This bug was fixed in the package ltsp - 5.5.7-1ubuntu1
1780996,2018-08-13 17:32:17 UTC,This bug was fixed in the package libreoffice - 1:5.1.6~rc2-0ubuntu1~xenial4
1780996,2018-08-08 11:48:16 UTC,I successfully tested libreoffice in xenial-proposed (libreoffice/1:5.1.6~rc2-0ubuntu1~xenial4) with the instructions in comment #51 (xenial ➞ xenial-proposed ➞ upgrade to bionic without disabling -proposed).
1780996,2018-08-03 17:10:03 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-30 16:16:42 UTC,This bug was fixed in the package guile-2.0 - 2.0.13+1-5ubuntu0.1
1780996,2018-07-30 16:16:39 UTC,This bug was fixed in the package nevow - 0.14.2-1ubuntu2
1780996,2018-07-30 16:16:37 UTC,This bug was fixed in the package wokkel - 0.7.1-1ubuntu0.18.04.1
1780996,2018-07-30 16:06:39 UTC,This bug was fixed in the package guile-2.2 - 2.2.3+1-3ubuntu0.1
1780996,2018-07-30 16:06:32 UTC,This bug was fixed in the package fusiondirectory - 1.0.19-1ubuntu0.18.04.1
1780996,2018-07-27 20:22:53 UTC,"the glib SRU seems to create issues, see bug #1784065 ""triggers ci file contains unknown directive `interest-await'"""
1780996,2018-07-26 14:37:12 UTC,This bug was fixed in the package gdk-pixbuf - 2.32.2-1ubuntu1.5
1780996,2018-07-26 14:32:59 UTC,This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu3
1780996,2018-07-26 14:32:56 UTC,This bug was fixed in the package shared-mime-info - 1.5-2ubuntu0.2
1780996,2018-07-26 14:27:13 UTC,This bug was fixed in the package postgresql-common - 173ubuntu0.2
1780996,2018-07-26 14:27:01 UTC,This bug was fixed in the package sphinx - 1.3.6-2ubuntu1.2
1780996,2018-07-26 10:03:29 UTC,This bug was fixed in the package pike7.8 - 7.8.866-5ubuntu0.1
1780996,2018-07-26 10:02:49 UTC,This bug was fixed in the package guile-2.0 - 2.0.11+1-10ubuntu0.1
1780996,2018-07-26 09:53:36 UTC,This bug was fixed in the package appstream - 0.9.4-1ubuntu4
1780996,2018-07-26 09:53:20 UTC,This bug was fixed in the package pike8.0 - 8.0.164-1ubuntu0.1
1780996,2018-07-26 09:53:10 UTC,This bug was fixed in the package dochelp - 0.1.3ubuntu0.1
1780996,2018-07-26 09:52:42 UTC,This bug was fixed in the package fusiondirectory - 1.0.8.8-3ubuntu2.16.04.1
1780996,2018-07-17 23:49:57 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 23:01:25 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 23:39:12 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-13 14:04:51 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-13 13:51:45 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-13 13:38:06 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-13 09:44:50 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-13 09:31:32 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-13 09:24:25 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-12 19:03:33 UTC,This bug was fixed in the package fusiondirectory - 1.0.19-1ubuntu1
1780996,2018-07-12 15:20:49 UTC,"Hi, here is my change in debian sid package:"
1780996,2018-07-12 14:51:39 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-12 14:41:38 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-12 14:29:43 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-11 21:19:12 UTC,wokkel needed fixing in both Ubuntu 16.04 and Ubuntu 18.04 although I can't add tasks for those releases.
1780996,2018-07-11 18:41:19 UTC,dovecot for cosmic and bionic already changed to noawait triggers by Debian maintainer.
1780996,2018-07-11 15:23:24 UTC,"clutter-imcontext declares an interest on /usr/lib/clutter-imcontext/immodules, but no package ships files in there, so not fixing that in a stable release. Not sure about devel."
1780996,2018-07-10 20:15:07 UTC,"Turns out goopg was not affected, it does not exist in xenial."
1780996,2018-07-10 19:06:33 UTC,Here's the yorick upstream change:
1780996,2018-07-10 17:00:13 UTC,Sphinx in cosmic no longer uses triggers. Sphinx in bionic uses interest-noawait.
1780996,2018-07-10 16:30:26 UTC,Here's the commit for the change in Debian:
1780996,2018-07-10 15:35:20 UTC,Missing in this bug:
1780996,2018-07-13 14:21:20 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 10:05:49 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 23:42:49 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 13:48:49 UTC,"Nothing installs the files that trigger reconf-inetd, so not fixing that."
1780996,2018-07-17 23:34:30 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 23:27:40 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 23:05:53 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 13:36:33 UTC,"Marking gosa as Won't fix, as newer versions moved to interest-await explicitly. The plugins depend on gosa, so the trigger being await is fine."
1780996,2018-07-17 22:59:34 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 22:53:05 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 22:22:04 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 19:57:38 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 12:31:51 UTC,This bug was fixed in the package guile-2.0 - 2.0.13+1-5ubuntu1
1780996,2018-07-17 23:09:41 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 18:41:34 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 18:39:14 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 17:03:10 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 16:58:26 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 16:56:02 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 16:36:51 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 16:34:23 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-17 10:13:40 UTC,"guile-2.2 is also affected by these triggers, but probably not that urgent, as it's not in xenial and not used as much as 2.0 in bionic/cosmic."
1780996,2018-07-16 16:21:57 UTC,"Hello Julian, or anyone else affected,"
1780996,2018-07-16 16:18:17 UTC,"Hello Julian, or anyone else affected,"
1781000,2018-07-23 00:08:49 UTC,According to https://github.com/elibyy/tcpdf-laravel/issues/37 this might be as simple as editing /usr/share/php/tcpdf/tcpdf.pdf to replace every instance of:
1781003,2018-07-10 18:55:22 UTC,"Confirmed; especially with popup blocking being the default on Chrome, a notification to disable the blocker would be excellent."
1781008,2018-07-11 00:53:46 UTC,"Reviewed:  https://review.openstack.org/581139
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f9a7da5819b4cc2c181506c682a092caff40fb3
Submitter: Zuul
Branch:    master"
1781008,2018-07-10 16:52:57 UTC,From my comment in that review:
1781013,2018-07-10 20:35:55 UTC,"SPDX licensing info spec is evolving, so this changed from the time we implemented this."
1781013,2020-05-15 16:13:23 UTC,Probably not worth working on until clear agreement on what/how to implement comes in https://forum.snapcraft.io/t/keeping-up-with-spdx-license-identifier-updates/7095/.
1781016,2018-12-21 10:46:05 UTC,daftykins:
1781016,2019-04-25 19:11:36 UTC,"I have an APC UPS too. Great find. Who would have guessed an IRQ handling
problem message from the kernel was due to a serial or USB device. Wow."
1781016,2019-04-18 09:34:59 UTC,Thanks for the info. Have anyone filed a bug against upstream apcupsd?
1781016,2019-04-15 12:00:16 UTC,"+1 Kyle, configuring apcupsd properly solved the problem for me too."
1781016,2019-04-12 18:48:09 UTC,Confirmed on my system as well. . .
1781016,2019-04-12 16:32:07 UTC,"Kyle - excellent find, I have confirmed that this was the cause of my issue, too. Thank you!"
1781016,2019-04-12 15:46:48 UTC,"On my system, I found that the immediate cause of those messages was running apcupsd, with the default configuration of trying to talk over a serial cable, but without a UPS connected to it. Even if it was otherwise configured for USB, I also had to remove the ""DEVICE /dev/ttyS0"" line to fix the IRQ errors."
1781016,2019-01-03 07:08:44 UTC,"A,"
1781016,2019-01-02 10:51:28 UTC,Running an Intel S2600ST motherboard with dual Gold 6148 I get this error regularly after the last kernel update I did.
1781016,2018-12-28 16:21:30 UTC,"TJ,"
1781016,2018-12-20 18:44:32 UTC,"Many thanks, I have given this a try today but unfortunately can't locate the specific Target & Vector combination. Here's what I saw:"
1781016,2019-04-12 10:22:10 UTC,"HP Z820 Workstation machine
HP 158B motherboard
4.15.0-47-generic kernel
same error
...
[  821.269834] do_IRQ: 4.38 No irq handler for vector
[  823.270705] do_IRQ: 4.38 No irq handler for vector
[  824.271303] do_IRQ: 4.38 No irq handler for vector
[  826.272120] do_IRQ: 4.38 No irq handler for vector
[  833.340194] do_IRQ: 4.38 No irq handler for vector
[  838.342193] do_IRQ: 4.38 No irq handler for vector
..."
1781016,2018-12-14 22:48:04 UTC,"I am also affected by this issue, however on a wholly different platform - an intel H370 based motherboard with a Core i3-8100 CPU. It was suggested that I attempt to supress logging output via a sysrq keyboard combo, so I pressed alt+sysrq+0 but this appears to be disabled by default as I saw the following printed to the TTY along with the IRQ handler messages:"
1781016,2018-09-24 23:44:54 UTC,"Mine is a desktop, and no suspend occurs, ever. Are you (Kai-Heng Feng)
asking me to suspend it and wake it up and see if it goes away?"
1781016,2018-09-24 14:30:31 UTC,Do you see this after S3?
1781016,2018-07-27 22:12:59 UTC,"I'd also like to mention that my system was a clean 18.04 install.  Also, would it be beneficial if I added my system info somehow?  If so, is there a way to add the same type of info Doug added without generating a whole new bug report with say ""ubuntu-bug linux""??"
1781016,2018-12-19 09:44:13 UTC,Please install and boot kernel [1] which enables IRQ debugfs.
1781016,2018-07-24 00:05:58 UTC,"Ubuntu does not appear to be the only one with this issue on the 4.15 kernel:
https://bugzilla.redhat.com/show_bug.cgi?id=1551605"
1781016,2018-07-24 00:04:43 UTC,Same here.  Not sure when this started:
1781016,2018-07-20 02:45:35 UTC,Still happening:
1781016,2018-07-18 21:02:38 UTC,"Exactly. It never happened in ubuntu 17.10. Started happening after installing ubuntu 18.04. Can't say I know exactly what kernel version 17.10 was up to, sorry. It was the standard one, whatever dist-upgrade would have gave me."
1781016,2018-07-17 16:58:43 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1781016,2018-07-10 17:30:07 UTC,This change was made by a bot.
1781021,2018-07-10 18:02:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/581439"
1781021,2021-02-19 15:52:31 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1781029,2019-06-13 23:29:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781035,2019-08-02 05:26:29 UTC,"I encountered the same problem and found a solution
The bug fix is here, please apply & merge the patches.
Thanks a lot!"
1781035,2018-07-28 09:31:24 UTC,The problem from the logs is the the lookup of the user failed in nslcd. This probably means that authentication between nslcd and the LDAP server needs to be configured in nslcd.conf. I expect that getent.ldap also fails with this configuration/
1781035,2018-07-10 21:05:25 UTC,Can you post the output from nslcd in debug mode? The easiest way to do this is run in a separate window:
1781035,2018-07-12 14:31:28 UTC,Here it is. I anonymize it a bit by replacing domain and server names.
1781042,2018-07-10 20:52:06 UTC,"Seems related to this bug.
Ubuntu 18.10 Cosmic installed /EFI/grub
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743"
1781042,2018-07-10 21:44:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781042,2018-07-10 21:50:32 UTC,"I have the same thing. Brand new laptop, Lenovo X1 Carbon 6th gen. I have a post with a ton of detail here:"
1781042,2018-07-10 22:20:13 UTC,I had the same issue while setting up a dual boot with Windows 10 on an ASUS ZenBook UX430UA-DH74. After installing Ubuntu and rebooting I was presented with the grub command prompt. Removing Ubuntu and reinstalling with no internet connection fixed this bug.
1781049,2018-07-13 02:57:02 UTC,apport information
1781049,2018-07-13 02:57:01 UTC,apport information
1781049,2018-07-13 02:57:00 UTC,apport information
1781049,2018-07-13 02:56:59 UTC,apport information
1781049,2018-07-13 02:56:58 UTC,apport information
1781049,2018-07-13 02:56:53 UTC,apport information
1781049,2018-07-13 02:56:56 UTC,apport information
1781049,2018-07-13 02:56:54 UTC,apport information
1781049,2018-07-13 02:56:50 UTC,apport information
1781049,2020-10-21 21:08:36 UTC,I can confirm this behavior on an HP 340s G7.
1781049,2018-07-13 02:56:57 UTC,apport information
1781049,2018-07-13 02:57:04 UTC,apport information
1781049,2019-06-20 12:15:07 UTC,"Apologies for the delay, was busy with college work. I recall having this bug on Ubuntu 16.04 and 17.04 too. I will have to install and see. Also, this bug exists on Kubuntu (not surprising) Fedora, Manjaro (both latest kernels and updates) . I tried digging up more info on hp-wmi etc. but nothing worked out."
1781049,2018-07-13 02:57:07 UTC,apport information
1781049,2018-07-15 02:05:35 UTC,"Guys, any thoughts?"
1781049,2018-08-28 07:42:24 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19-rc1 kernel[0]."
1781049,2018-08-29 16:32:37 UTC,"Yes, sure, could I take a few days? Have exams going on right now. I'll post my results as soon as possible. Also, any chance the bug-uploader can merge all uploads to one comment? Makes the bug report all cluttered up.
Thank you"
1781049,2018-08-29 21:40:13 UTC,"Hello!
I've tested the rc1 release kernel (4.19.0-041900rc1-generic), and sure enough, the bug persists. WiFi hard-blocked after suspend-resume."
1781049,2018-08-29 23:44:43 UTC,"Hello,
Blacklisting the below modules one after the another individually or all of them did no good. The hard-block bug is still there. [2]"
1781049,2019-01-20 15:49:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781049,2019-01-20 16:07:08 UTC,"Have exactly the same issue with Acer ex2519 n15w4 with Qualcomm Atheros QCA9565 wi-fi card in it. Wi-fi worked during system installation (with secure boot disabled as the original reporter mentioned). Not sure if computer was suspended or powered off, but once I booted it and wi-fi just stopped working and rfkill reported that device phy0 is hard blocked."
1781049,2019-03-04 15:45:53 UTC,"Dexter,
Can you test v4.12? This could be a regression."
1781049,2019-11-17 10:45:51 UTC,"I have the same problem with Asus K54HR, rfkill says that phy0 is hard blocked.
I tried to reinstall Ubuntu 19.04 and 19.10, reset the bios, with no solution."
1781049,2018-07-13 02:56:48 UTC,apport information
1781049,2018-07-13 02:57:06 UTC,apport information
1781049,2018-07-13 02:56:47 UTC,apport information
1781049,2018-07-13 02:56:52 UTC,apport information
1781049,2018-07-13 02:56:45 UTC,apport information
1781049,2018-07-13 02:56:45 UTC,apport information
1781049,2018-07-11 08:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1781049,2018-07-13 02:51:25 UTC,apport information
1781049,2018-07-13 02:51:26 UTC,apport information
1781049,2018-07-13 02:51:28 UTC,apport information
1781049,2018-07-13 02:51:30 UTC,apport information
1781049,2018-07-13 02:51:31 UTC,apport information
1781049,2018-07-13 02:51:32 UTC,apport information
1781049,2018-07-13 02:51:33 UTC,apport information
1781049,2018-07-13 02:51:35 UTC,apport information
1781049,2018-07-13 02:51:36 UTC,apport information
1781049,2018-07-13 02:51:37 UTC,apport information
1781049,2018-07-13 02:51:38 UTC,apport information
1781049,2018-07-13 02:52:12 UTC,apport information
1781049,2018-07-13 02:52:02 UTC,apport information
1781049,2018-07-13 02:56:43 UTC,apport information
1781049,2018-07-13 02:56:42 UTC,apport information
1781049,2018-07-13 02:54:27 UTC,All the above are BEFORE I sent the system to sleep and resumed it. All the below comments are after I suspended (sleep) the system for a few minutes and then resumed it.
1781049,2018-07-13 02:52:16 UTC,apport information
1781049,2018-07-13 02:51:39 UTC,apport information
1781049,2018-07-13 02:52:17 UTC,apport information
1781049,2018-07-13 02:52:07 UTC,apport information
1781049,2018-07-13 02:52:06 UTC,apport information
1781049,2018-07-13 02:52:04 UTC,apport information
1781049,2018-07-13 02:52:03 UTC,apport information
1781049,2018-07-13 02:52:10 UTC,apport information
1781054,2020-04-25 13:50:00 UTC,"Created attachment 634540
freehdl-0.0.8-r2.ebuild"
1781054,2020-04-25 13:55:46 UTC,"Created attachment 634548
freehdl-0.0.8-gvhdl_tag_command.patch"
1781054,2020-04-25 13:54:16 UTC,"Created attachment 634546
freehdl-0.0.8-declarative_region.patch"
1781054,2020-04-25 13:53:19 UTC,"Created attachment 634544
freehdl-0.0.8-acl-NULL-check.patch"
1781054,2020-04-25 13:51:48 UTC,"Created attachment 634542
freehdl-0.0.8-cpp-modern.patch"
1781054,2020-04-22 18:31:56 UTC,I cleaned the patches a little and added a couple of minor fixes.
1781054,2020-03-29 20:22:42 UTC,"The attachment ""freehdl-0.0.8-declerative_region.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1781054,2020-03-29 17:30:23 UTC,"My patch suggested in the corresponding Gentoo Bug (also attached here) allows to avoid the reported segfault. However, this solution is highly questionable, since I do not know what actually has this piece of code look like."
1781054,2020-03-29 15:09:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781054,2018-03-05 22:50:12 UTC,"Created attachment 522478
freehdl-0.0.8-r1.ebuild"
1781054,2018-03-05 22:40:59 UTC,"Created attachment 522476
freehdl-0.0.8-la.patch"
1781054,2018-03-05 22:36:23 UTC,"Created attachment 522474
freehdl-0.0.8-declerative_region.patch"
1781054,2020-03-30 19:41:00 UTC,"I had to apply several patches from Gentoo Portage, also from the mentioned Gentoo bug, and make numerous edits to the code by myself. And eventually I was able to build the DEB-package for Ubuntu Bionic using the set of patches attached here.
Please note however, that I am not a programmer, and therefore my ""fixes"" may be rather stupid. But as far as I tested thus built FreeHDL package with some simple schematics in Qucs, everything worked fine. So I hope my patches will be useful to somebody, and preferably be reviewed by someone more competent."
1781057,2018-07-24 14:02:29 UTC,"It indeed doesn't ""recreate"" the network, which is leading to unexpected issues."
1781057,2018-07-24 17:00:01 UTC,"odyssey4me> perhaps best to add a known issue release note saying 'if you're changing your network config after a deploy, you're in for a bad day - don't do it'"
1781058,2018-07-12 16:32:11 UTC,"Hi Dominic,"
1781058,2018-07-13 04:15:36 UTC,"Hi Dominic,"
1781058,2018-09-21 20:19:26 UTC,"This looks like a simple typo, ""wifiobj"" should be ""wifiObj""."
1781096,2019-06-02 23:08:47 UTC,PR for develop (heading into 2.7): https://github.com/juju/juju/pull/10273
1781096,2019-05-31 06:21:27 UTC,PR for 2.6: https://github.com/juju/juju/pull/10267
1781096,2019-05-14 06:14:04 UTC,"HA, I've seen this recently too and was going to address it. Glad I came across this bug!"
1781096,2019-01-23 09:09:28 UTC,"Note that we still see this happening in juju 2.5.0:
2019-01-23 07:41:28 ERROR juju.worker.dependency engine.go:632
""model-upgrader"" manifold worker returned unexpected error: model
235f7c2f-b531-46e1-8438-1a663a614a68 has been removed
...
2019-01-23 07:41:37 ERROR juju.worker.dependency engine.go:632
""model-upgrader"" manifold worker returned unexpected error: model
79c03f03-eff2-41dc-831c-b7296c971b95 has been removed
...
2019-01-23 07:41:37 ERROR juju.worker.dependency engine.go:632
""model-upgrader"" manifold worker returned unexpected error: model
235f7c2f-b531-46e1-8438-1a663a614a68 has been removed"
1781096,2018-07-11 05:40:28 UTC,PR for 2.5 (develop): https://github.com/juju/juju/pull/8916
1781096,2019-05-31 04:27:06 UTC,PR for 2.5: https://github.com/juju/juju/pull/10265
1781096,2018-07-11 03:26:41 UTC,PR against 2.3: https://github.com/juju/juju/pull/8914
1781096,2018-07-11 02:38:38 UTC,I will fix the model-upgrader worker to uninstall instead of restarting when the model it operates on is removed.
1781096,2018-07-11 01:24:22 UTC,Logs at https://private-fileshare.canonical.com/~paulgear/lp1781096/
1781096,2018-07-11 01:14:13 UTC,Log extract: https://pastebin.canonical.com/p/NNGTzMKpbb/
1781096,2018-07-11 05:20:42 UTC,PR for 2.4: https://github.com/juju/juju/pull/8915
1781100,2018-07-11 02:13:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/581548"
1781100,2018-07-11 13:17:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/581741"
1781100,2018-07-11 21:33:09 UTC,"Reviewed:  https://review.openstack.org/581548
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=78af1de1587fb83e09d1c0639fb5a28eb6e51a27
Submitter: Zuul
Branch:    master"
1781100,2018-07-30 16:07:21 UTC,This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.
1781100,2018-07-31 18:28:32 UTC,"Reviewed:  https://review.openstack.org/581741
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=246c61d82b6d2a4249cf2408268830dfbd71b8f6
Submitter: Zuul
Branch:    stable/queens"
1781100,2018-09-24 14:47:18 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1781105,2021-02-12 21:37:38 UTC,I'm marking this won't fix because John is correct about needing a manner to determine which subscription is to be received against.
1781105,2018-07-12 16:16:27 UTC,"Holly,"
1781107,2019-04-08 03:47:34 UTC,"In theory, https://blueprints.launchpad.net/trove/+spec/datastore-registration-api includes a method to delete datastore versions (implemented in https://review.openstack.org/#/c/195153/7), though possibly not via the unified OpenStack CLI, nor documented fully.  Caveat: untested ;)"
1781120,2019-03-25 11:00:05 UTC,Hey
1781120,2019-03-25 11:46:21 UTC,"No, it is fixed, thank you."
1781120,2019-05-25 04:17:31 UTC,[Expired for snapd because there has been no activity for 60 days.]
1781125,2018-07-13 07:03:46 UTC,apport information
1781125,2018-07-13 07:03:48 UTC,apport information
1781125,2018-07-13 07:03:49 UTC,apport information
1781125,2018-07-13 07:21:11 UTC,"Thanks. It appears you now have the Nvidia kernel driver installed OK, but the Nvidia X driver isn't being used at all."
1781125,2018-07-13 07:23:11 UTC,"I've tried many times to apply one of the available Nvidia drivers (390, 396) but still it displays that ""No proprietary drivers are in use"". Sent the system information by running 'apport-collect 1781125'"
1781125,2018-07-13 07:35:06 UTC,Please see comment #25.
1781125,2018-07-13 09:52:15 UTC,Thanks for the prompt response. I've deleted the /etc/X11/xorg.conf.failsafe and restarted the laptop. But still I cannot set a proprietary driver and cannot plugin a secondary monitor.
1781125,2018-07-13 08:46:55 UTC,Thanks. It appears the problem is that file: xorg.conf.failsafe
1781125,2018-07-13 07:03:45 UTC,apport information
1781125,2018-07-16 02:45:12 UTC,OK.
1781125,2018-07-17 04:51:34 UTC,"Thanks, I've Tried following options but no luck."
1781125,2018-07-17 05:17:17 UTC,Here are the steps I would take:
1781125,2018-07-17 05:29:53 UTC,"Thanks, Even after uninstalling and rebooting the system, 390 and 396 drivers are shown listed under additional drivers section. By the way when I'm trying to install 390 driver after uninstall its getting hung at 'Building initial module for 4.15.0-24-generic'"
1781125,2018-07-13 08:31:21 UTC,"Thanks, Just saw comment 25.
Please find the requested files attached."
1781125,2018-07-13 07:03:42 UTC,apport information
1781125,2018-07-13 07:03:44 UTC,apport information
1781125,2018-07-13 07:03:19 UTC,apport information
1781125,2018-07-11 05:58:48 UTC,It appears the problem is that you have partially/unsuccessfully/manually installed the Nvidia graphics driver but it's no longer installed and it has left the 'nomodeset' flag in your kernel command line:
1781125,2018-07-11 10:54:15 UTC,"Thanks for the prompt response. I removed 'nomodset' and ran 'sudo update-initramfs -u' but still the secondary monitor is not detected. In Display setting it shows 'Unknown Display'.
I've tried selecting the 'nvidia-driver-390' from software & updates > additional drivers but still no luck."
1781125,2018-07-12 01:39:55 UTC,"In comment #5 it says ""No proprietary drivers are in use""."
1781125,2018-07-13 07:03:41 UTC,apport information
1781125,2018-07-13 07:03:21 UTC,apport information
1781125,2018-07-13 07:03:30 UTC,apport information
1781125,2018-07-13 07:03:28 UTC,apport information
1781125,2018-07-13 07:03:32 UTC,apport information
1781125,2018-07-13 07:03:34 UTC,apport information
1781125,2018-07-13 07:03:35 UTC,apport information
1781125,2018-07-13 07:03:36 UTC,apport information
1781125,2018-07-13 07:03:37 UTC,apport information
1781125,2018-07-13 07:03:40 UTC,apport information
1781125,2018-07-13 07:03:31 UTC,apport information
1781130,2018-10-05 07:54:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781130,2018-10-05 07:56:30 UTC,"Hello,
Same problem with ubuntu 18.04 and oracle java 8, open-jdk8, open-jdk11 ..."
1781131,2018-07-11 07:48:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781136,2018-10-21 12:54:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781137,2018-07-11 15:14:00 UTC,"why isn't the resource_id just the host_name, since that is the key used to access the resource in the nova API?"
1781143,2018-07-11 07:48:20 UTC,"Sorry, could the admin move my post to the dracut package?"
1781143,2018-07-11 08:21:03 UTC,I have added on my own affected packages. Thank you
1781143,2018-07-12 13:25:51 UTC,The solution is here: https://github.com/antonio-petricca/buddy-linux/issues/2 .
1781143,2019-10-09 14:31:32 UTC,"I'm also seeing this. I have a bionic VM running in VirtualBox and, a few days ago, I wanted to install the newer version of the guest additions, and got an error from dracut:"
1781144,2018-12-08 20:07:34 UTC,"There are some complex relationships in biarch libc dev packages that are a bit tough to represent in a ""don't do that"" way.  This is one of them."
1781144,2020-08-11 08:26:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781148,2018-07-11 09:22:35 UTC,And as well option `neutron_vpnaas_service_provider: VPN:strongswan:neutron_vpnaas.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default` in neutron.conf.
1781148,2018-07-11 08:06:47 UTC,"Also here is issue filled for documentation update. I think that in order to make neutron-server work, we must also remove `vpnaas` from neutron.conf `service_plugins` option."
1781157,2018-07-11 08:41:42 UTC,AFAIK (and I might've missed part of the conversation) sections and categories are different things (and categories aren't done yet).
1781164,2018-07-11 09:08:57 UTC,Pull request open https://code.launchpad.net/~kumy/libravatar/+git/libravatar/+ref/bug-1781164
1781164,2018-07-15 18:37:52 UTC,"While it's not obvious from the shortname that is shown there, these placeholders are actually different."
1781190,2018-10-09 14:06:38 UTC,"Configurazione di linux-firmware (1.157.20)...
update-initramfs: Generating /boot/initrd.img-4.4.0-96-generic
E: /usr/share/initramfs-tools/hooks/iscan failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.4.0-96-generic with 1.
dpkg: errore nell'elaborare il pacchetto linux-firmware (--configure):
 il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Configurazione di linux-image-4.4.0-130-generic (4.4.0-130.156)...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-4.4.0-125-generic
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-130-generic
E: /usr/share/initramfs-tools/hooks/iscan failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.4.0-130-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-130-generic.postinst line 1052."
1781192,2018-11-12 05:20:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781192,2019-11-19 17:21:51 UTC,Any update on fix or is there any workaround for this?
1781193,2018-07-16 12:13:22 UTC,"Strangely enough, some passwords are managed by some wallet. As kwalletmanager5 demands a password, and it stopped recognizing the correct one, I suspect that the wallet that works is kwallet4. It seems open by default, but I cannot find any wallet manager for it."
1781206,2018-07-18 11:19:55 UTC,apport information
1781206,2018-07-18 11:20:04 UTC,apport information
1781206,2018-07-18 11:20:00 UTC,apport information
1781206,2018-07-18 11:19:58 UTC,apport information
1781206,2018-07-18 11:19:57 UTC,apport information
1781206,2018-07-18 11:19:56 UTC,apport information
1781206,2018-07-18 11:19:54 UTC,apport information
1781206,2018-07-18 11:20:02 UTC,apport information
1781206,2018-07-18 11:19:51 UTC,apport information
1781206,2018-07-18 11:19:50 UTC,apport information
1781206,2018-07-18 11:19:48 UTC,apport information
1781206,2018-07-18 11:05:26 UTC,This bug happened because of Upstream(4.17.5) kernel only.
1781206,2018-07-17 18:05:37 UTC,You could also try the current mainline kernel if you are interested in upstream kernels:
1781206,2018-07-17 18:04:53 UTC,4.17.5 is an upstream kernel.  Does this bug happen with an Ubuntu specific kernel or just upstream?
1781206,2018-07-16 22:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1781206,2018-07-18 11:19:53 UTC,apport information
1781207,2018-07-14 14:38:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781207,2018-07-11 12:33:16 UTC,"sudo grub-install
x86_64-efi wird für Ihre Plattform installiert.
Could not delete variable: Invalid argument
grub-install: Fehler: efibootmgr failed to register the boot entry: Es ist ein Block-Device notwendig."
1781207,2018-07-11 12:34:43 UTC,"sudo update-grub
GRUB-Konfigurationsdatei wird erstellt …
Warnung: GRUB_TIMEOUT auf einen von Null verschiedenen Wert setzen, wenn GRUB_HIDDEN_TIMEOUT als nicht mehr unterstützt angegeben wird.
Linux-Abbild gefunden: /boot/vmlinuz-4.15.0-23-generic
initrd-Abbild gefunden: /boot/initrd.img-4.15.0-23-generic
Linux-Abbild gefunden: /boot/vmlinuz-4.15.0-22-generic
initrd-Abbild gefunden: /boot/initrd.img-4.15.0-22-generic
Hinzufügen des Boot-Menü Eintrages für die EFI Firmware Konfiguration
erledigt"
1781210,2018-07-11 13:00:07 UTC,This change was made by a bot.
1781210,2018-07-12 03:53:42 UTC,"Verified on node amaura with kernel 4.15.0-23.25 and 4.15.0.26.28, they both works fine with the qrt_apparmor test."
1781211,2018-07-11 15:25:58 UTC,After some time I decided it is haxm bug - so i created the same issue on haxm project too
1781211,2020-07-31 08:19:32 UTC,"This issue has been fixed in HAXM, see:
""save/restore FPU registers in VM entry/exit""
https://github.com/intel/haxm/commit/6c2cd4d79d"
1781230,2018-07-12 15:21:40 UTC,"I see, good you found the issue! :)"
1781230,2018-07-12 10:05:07 UTC,"No handlers could be found for logger ""vmtp_file"""
1781230,2018-07-12 14:16:58 UTC,"Found the solution,"
1781230,2018-07-11 17:12:41 UTC,"From reading the log, I think you are using a cirros image. However cirros is so light weighted so iperf/nuttcp won't run over there... You can try a Ubuntu or CentOS image and I am pretty sure it will work for you."
1781230,2018-07-12 10:03:01 UTC,"Using Ubuntu 18.04,"
1781231,2018-07-16 14:19:23 UTC,It seems likely you have a custom python path configured which calls a version of pyclean not provided by an official Ubuntu package.
1781232,2018-09-09 04:44:32 UTC,"I increased the number of monitors in the multinode file, but Kolla-Ansible did not change the configuration."
1781232,2018-09-08 06:41:03 UTC,"I haven't found any logs that I can understand - ceph logs are pretty ceph-specific, but it appears that the monitors can't create a quorum with more than 3 monitors."
1781232,2018-09-08 04:02:45 UTC,"I have found this issue happens when there are more than 3 controllers.  I have only tried 3 and 5 controllers.  3 works, 5 doesn't."
1781232,2018-10-06 05:07:32 UTC,"Hello,"
1781232,2018-08-16 09:43:39 UTC,Yes you are right. The directory is empty. How do I fix this?
1781232,2018-08-10 17:44:25 UTC,"It looks like the ansible scripts aren't generating the ceph mgr keyrings. If you look at your configuration files, there won't be one in /etc/kolla/ceph_mgr."
1781232,2018-08-16 10:20:05 UTC,At this point. When i try to execute docker exec ceph_mon ceph -s  it stucks forever until i kill the ceph-mon process in the container or restart the whole container.
1781236,2018-07-11 15:03:17 UTC,Including link to an old IRC discussion:
1781236,2019-06-07 15:59:56 UTC,Setting this to Confirmed. I have had a number of support calls from staff users that are confused when they find holds without notifications set.
1781236,2021-02-11 20:41:22 UTC,"Marking this a duplicate of bug #1841270, since that adds a checkbox to honor hold preferences."
1781240,2018-07-12 16:07:31 UTC,"Hi Michael,"
1781241,2020-06-29 16:54:37 UTC,Saw this again again here with the same issues as Michael's run above: https://solutions.qa.canonical.com/#/qa/testRun/c2bd543c-afd2-4212-87d2-afd89cac8bd0
1781241,2020-06-29 16:53:58 UTC,Pretty sure we're seeing this again in this run: https://solutions.qa.canonical.com/#/qa/testRun/98caba03-f81c-4be3-8cc7-04e285059dd3
1781241,2020-04-06 16:52:25 UTC,Saw this again here: https://solutions.qa.canonical.com/#/qa/testRun/d044f76b-a0be-48f3-9bc0-f9502541323b
1781241,2020-03-18 16:07:04 UTC,We saw this again on maas_2.7.0-8232-g.6e1dba4ab-0ubuntu1~18.04.1
1781241,2019-09-19 12:06:01 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1781241,2018-09-05 21:10:13 UTC,"Being in degraded state doesn't mean there's a *bug*. Being degraded means that there are a lot of things that could be wrong, bug or not. If there are no failures, that's good, because despite MAAS being in a degraded state, MAAS is working just fine."
1781241,2018-08-23 14:37:48 UTC,"We haven't seen it in a while, but reporting 'degraded' is a bug
either way, even if we're not seeing any failures. We have to be able
to rely on maas to tell us if it's healthy or not. If the flag doesn't
matter, then get rid of it.
On Thu, Aug 23, 2018 at 8:56 AM Andres Rodriguez
<email address hidden> wrote:

>
> ** Changed in: maas
>     Milestone: 2.5.0alpha2 => 2.5.0beta1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1781241
>
> Title:
>   [2.4] rack controller remained in degraded state
>
> Status in MAAS:
>   Incomplete
>
> Bug description:
>   This is with 2.4.0-6981-g011e51b7a-0ubuntu1~18.04.1.
>
>   After an HA deployment, one rack controller (qtmb3d) remained in a
>   degraded state for over 20 minutes (the test timed out after that)
>   (92% connected).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1781241/+subscriptions
"
1781241,2018-08-13 19:02:27 UTC,"Also, even if degraded, MAAS should be able to continue to work. Are there any issues (e.g. machines failed to deploy, commission, etc)."
1781241,2018-08-13 19:01:49 UTC,"Hi Jason,"
1781241,2018-09-05 21:26:27 UTC,"Sure - it means there is something we should investigate. We should never
be in a degraded state on a fresh deploy in our test lab."
1781243,2018-08-15 07:04:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781243,2021-02-19 18:13:06 UTC,I confirm that this bug is still current on a clean Ubuntu 20.04 Focal installation. work-around makes the install no longer fail.
1781244,2018-07-11 15:41:25 UTC,The same run does show os_brick debug logs in n-cpu:
1781247,2019-08-29 20:28:59 UTC,You'll want to take a look at /etc/updatedb.conf and modify PRUNEFS so that the filesystem types you are interested in end up getting indexed.
1781247,2019-10-29 04:17:23 UTC,[Expired for mlocate (Ubuntu) because there has been no activity for 60 days.]
1781248,2018-07-12 13:37:18 UTC,"It is against PINES policy for anyone other than a trained cataloger to make these kinds of changes to item attributes, so we would prefer that the permission not be out of the box for non-cataloging staff. There were several admin positions that initially did not have cataloging permissions out of the box because of those policies. This may have been one of those that had cataloging permissions added later."
1781248,2018-07-11 21:14:33 UTC,"I didn't find one but if you do, merge the two reports. Since I began using
Webby 3.0.9 last week, I have found five circulation bugs. Three were
previously reported. I added notes to those bug reports and created two new
bug reports."
1781248,2018-07-11 20:00:39 UTC,I can't even do it in the volume editor. :(
1781248,2018-07-11 19:58:40 UTC,"Oh, my. We sure don't want to have to follow several steps to change the
owner. Kathy Lussier is also looking into this. She asked me for more
specifics so I sent screen shots of the XUL copy editor and the web copy
editor."
1781248,2018-07-11 19:37:31 UTC,I'm not sure this is a permissions issue. I am a supercat and cannot edit the owning library in the web client copy editor. You have to transfer the copy/vol. I thought I had opened a bug report about it but cant find it. I can edit in the XUL client edit item attributes
1781248,2018-07-11 19:49:01 UTC,I take that back. I just tested -- I can change the owning library but you have to do so in edit volume and not in the copy editor
1781248,2018-07-11 19:19:57 UTC,"Hi, Kathy -"
1781248,2018-07-11 19:00:18 UTC,"Diane,"
1781248,2018-07-11 19:52:14 UTC,"Yes, I thought there was an existing bug on this too."
1781249,2018-07-11 16:50:42 UTC,Remember version info.
1781249,2018-08-01 22:50:17 UTC,"On technical layers, a context menu with:
select all, unselect all and toggle, just FRONT, just BACK, add silks..."
1781250,2018-07-13 18:10:35 UTC,Is it calling state.Model but not cleaning up/releasing the resource?
1781250,2018-07-16 04:49:16 UTC,Another occurrence of firewaller worker test failure from the original bug description - http://ci.jujucharms.com/job/github-merge-juju/755/
1781250,2020-08-03 19:29:43 UTC,This test is being rewritten with mocks as part of the deploy command refactor.
1781250,2018-07-12 11:27:36 UTC,"Further to the comment above, s.State.Model() is only used in these 2 tests in the whole of cmd/juju package :D"
1781250,2018-07-15 23:16:00 UTC,Possibly...
1781250,2018-07-12 11:17:10 UTC,PR that among other things skips the test: https://github.com/juju/juju/pull/8918
1781250,2018-07-12 10:53:58 UTC,"So I'm skipping the test that ""seems"" to be causing the CI issue, but, unfortunately it's intermittent - so only time will see
 https://github.com/juju/juju/pull/8918/commits/ec595f73202dd65ee842823d0e50b52083c53753"
1781250,2018-07-11 23:32:12 UTC,"Actually, with further investigation, these failures are not related to me unskipping tests. There is a lot of new things that have been added to deploy_test recently and the TestTearDown is failing. It has not failed locally on my machine though."
1781250,2018-07-11 22:30:55 UTC,"@Simon Richardson,"
1781250,2018-07-12 11:26:09 UTC,"@Simon Richardson (simonrichardson),"
1781251,2019-01-03 10:26:41 UTC,"With the recent announcement to EOL Python2, it would be really time to include the Python3 version of this package. Is there any plan to do so?"
1781251,2019-03-20 14:13:08 UTC,"Hi,"
1781251,2019-08-08 14:33:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781251,2019-08-08 14:35:43 UTC,Salome (https://www.salome-platform.org/) doesn't compile without omniORB for Python3.
1781251,2019-10-24 13:26:18 UTC,I found a thread discussing how Fedora handled the side-by-side installation for their RPM packages: http://www.omniorb-support.com/pipermail/omniorb-list/2017-August/031921.html
1781255,2018-07-11 23:46:19 UTC,"That was done by Storage SIG to avoid unintentional upgrades, question is where is centos-release-ceph-jewel coming from i.e. why is it installed? It needs to be removed first."
1781255,2018-07-18 11:02:23 UTC,"o/ Alan, that is done here FYI https://github.com/openstack-infra/tripleo-ci/blob/ad050216c2cc5c3ea0786b85dee9a1ee1b4eed40/scripts/tripleo.sh#L293-L318 - we are working on moving away from using tripleo.sh altogether with https://trello.com/c/GvjcnJB2/850-translate-tripleosh-bootstrap-subnodes-into-a-series-of-tasks but for now I posted a review at https://review.openstack.org/583547 which makes luminous the default should help i think"
1781255,2018-07-19 08:56:48 UTC,"@Wes, where does it happen? Where is the log of the job? In which stage of job does it happen? In which job does it happen?
This bug need more details and info."
1781255,2018-07-19 08:58:19 UTC,o/ Alan /anyone else do you have a pointer to logs /job where this was failing please or was it from local setup?
1781255,2019-01-29 13:55:31 UTC,Is this still an issue?
1781262,2018-07-11 17:31:43 UTC,Add error messages in plain text since additional line breaks were added by launchpad in the original message.
1781264,2019-01-19 13:54:08 UTC,I have same problem.  gourmet 0.17.4 and Ubuntu 18.04.1.  Thank you.
1781267,2018-07-11 17:51:35 UTC,A proposal we came up with:
1781267,2018-08-30 08:35:35 UTC,"I thought we'd explicitly said the license needed to be SPDX 2.something, and that bumping the spdx version was a when-and-if discussion we needed to have at some point."
1781267,2018-08-30 13:20:02 UTC,"Looks like *this* is the ""bumping the spdx version"" discussion, and the point we're having it at is the point when users are starting to use non-SPDX 2.x identifiers and complaining about it."
1781267,2018-11-14 12:28:58 UTC,This is being worked on in https://github.com/snapcore/snapd/pull/6152
1781270,2018-07-12 20:57:19 UTC,"No, I think that the grid layout format is better, we should find another component (RecyclerView maybe) that can be customized more easily (thinking about letting users decide the number of rows in the Grid layout)"
1781270,2019-11-12 17:21:09 UTC,"Moved here:
https://gitpull.it/T10"
1781273,2019-04-11 22:10:00 UTC,https://git.centos.org/summary/rpms!qemu-kvm dead link ?
1781274,2020-04-21 15:41:51 UTC,"Using Michele's test, I was able to confirm the bug. After installing the patch, the same tests had appropriate finish dates."
1781274,2020-04-21 15:13:07 UTC,"It's working for me, but I'm waiting on John Amundson to test it, too."
1781274,2020-02-03 14:23:34 UTC,"Thanks for your work on this, Bill! Restoring the signedoff tag."
1781274,2020-01-31 22:39:36 UTC,"Well that's fun, it looks like ye olde *100 trick does not always work in JS:"
1781274,2020-01-31 22:11:31 UTC,"Thanks for the example, Michele.  I'll take another look.  I think you're right that I'm missing a calculation."
1781274,2020-04-21 16:49:11 UTC,"John, thanks for testing. Since I could not find any signs of rounding errors in the transaction logs for the payments that you made today, I have pushed this branch without your signoff."
1781274,2020-01-30 20:05:13 UTC,"Thanks, All."
1781274,2020-01-31 21:58:32 UTC,"Thanks for looking at this, Bill. Unfortunately, this isn't working for me in all cases. As an example, paying two billings in the amounts of $1.30 and $.75 results in the transaction with $.75 owed not closing. Perhaps there's another calculation in that file that needs the multiply/divide by 100 approach, but it's not jumping out at me. Here is the gateway.log entry for the payment detail"
1781274,2019-12-20 21:07:38 UTC,Branch as promised is at:
1781274,2019-12-20 18:43:39 UTC,"Just for the sake of confirmation, I see something similar on my test server, for a set of transactions where 1 did not close."
1781274,2019-12-20 18:16:48 UTC,There appears to be a floating point number problem that is at least partially responsible for this bug.
1781274,2019-12-17 20:00:25 UTC,"I just saw it with 8 overdue transactions. Looking at the data, it was the last circulation paid that did not close."
1781274,2019-12-05 14:52:51 UTC,"I just encountered the same behavior described by John (2019-03-18) where 1 Lost item payment out of 3 paid in the same transaction did not close appropriately, while the others did."
1781274,2019-03-18 15:41:15 UTC,"I want to update this bug and say that I've noticed that this isn't just limited to LOST bills, but to others, as well, (i.e. overdue fines). I'm editing the title to reflect this. We still haven't figured out why, but one thing seemingly remains constant. The transaction that fails to close is part of a single payment that applied to multiple transactions"
1781274,2018-07-11 19:05:07 UTC,I can confirm this issue though we cannot reproduce it on command. I am unsure of the trigger for the bug but occasionally we have a bill that does not close when payment is made in full.  The item will remain on the patron account as lost. I add $.01 and pay $.01 to the bill to force it to close.
1781274,2020-01-10 20:01:53 UTC,"Works great! Thanks, Michelle!"
1781277,2019-04-11 14:58:48 UTC,Adding an image from #1824325 by Silviu Laurentiu (silviulaurentiu) showing how it's done in KiCad Librarian.
1781277,2018-10-31 18:58:53 UTC,"Adding a ""measure"" tool to the footprint viewer like the one that already exists in the footprint editor would be very useful."
1781277,2018-07-18 08:08:54 UTC,This would be helpful. I can think of three ways to do it:
1781277,2018-07-18 11:22:51 UTC,"I already use the EDA of the video and it use the option 3, a heuristic to shows the most obvious on XY: pin-to-pin, pin to the other side pin (total dimension).
Maybe 2 could be the best looking, using the User.Draw on the library (that will be not show when we pick the footprint) but will really create a big work in the libraries.
About 1, could nice and maybe the most simple to do, but I don't now if will be the better way to show (could create some parallax/misunderstood on the interpretation?)."
1781281,2018-07-11 21:21:00 UTC,"If it works fine on a POWER9 machine, you should try to run qemu-ppc64le with ""-cpu power9""."
1781281,2018-07-12 13:36:55 UTC,Thanks for the reply.
1781286,2019-10-02 20:42:21 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/686292"
1781286,2019-10-01 17:34:39 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/686017"
1781286,2019-10-01 21:33:12 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686050"
1781286,2019-10-01 21:46:22 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/686053"
1781286,2019-10-02 17:48:48 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/686226"
1781286,2019-10-02 17:54:25 UTC,"Reviewed:  https://review.opendev.org/685997
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=38fb7f82abd7fffc00ebc050ee5230f1137e76d8
Submitter: Zuul
Branch:    master"
1781286,2019-10-02 19:44:44 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/686264"
1781286,2019-10-03 09:29:56 UTC,"Reviewed:  https://review.opendev.org/685998
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8c332c4dd79f8bb5fdc5f6722a80c9a117ff52c4
Submitter: Zuul
Branch:    master"
1781286,2019-10-23 13:02:43 UTC,"Reviewed:  https://review.opendev.org/686264
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=53bcf0b1eeb4d34cbbec6200026c9bac5921db97
Submitter: Zuul
Branch:    stable/stein"
1781286,2019-10-04 17:25:09 UTC,"Reviewed:  https://review.opendev.org/685807
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bcd4584a7c6a8d6b91a6db2fe8b38671494ff9c1
Submitter: Zuul
Branch:    master"
1781286,2019-10-04 23:38:35 UTC,"Reviewed:  https://review.opendev.org/686047
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f1ad0b13e8f8296739f75b11e257a6fef2cc538c
Submitter: Zuul
Branch:    master"
1781286,2019-10-04 23:38:47 UTC,"Reviewed:  https://review.opendev.org/686050
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ac85b76178017b4bda30502a6ebb9c990435ec72
Submitter: Zuul
Branch:    master"
1781286,2019-10-04 23:38:56 UTC,"Reviewed:  https://review.opendev.org/686053
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a87fbdda9d74949fa149d73c8ad821399d817c50
Submitter: Zuul
Branch:    master"
1781286,2019-10-21 18:36:03 UTC,"Reviewed:  https://review.opendev.org/686226
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b5e6c389d733d4dbd94380add7e3fa6c4d1e3fa8
Submitter: Zuul
Branch:    stable/train"
1781286,2019-10-01 16:13:15 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/685998"
1781286,2019-10-23 18:29:54 UTC,"Reviewed:  https://review.opendev.org/686292
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5a981356506dfc5e2fab34b0ae5a9ee624c4b264
Submitter: Zuul
Branch:    stable/rocky"
1781286,2019-10-03 09:36:04 UTC,"Reviewed:  https://review.opendev.org/686017
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f07697ebff31daa5ee8c8b3a29b55403522ba445
Submitter: Zuul
Branch:    master"
1781286,2019-10-01 16:13:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/685997"
1781286,2019-10-01 21:04:31 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686047"
1781286,2019-09-30 21:59:15 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/685807"
1781286,2018-07-11 21:40:01 UTC,"It's not the [database]/connection that matters, build requests are in API DB which isn't configured in the cell conductor in default devstack."
1781286,2018-07-11 21:52:07 UTC,"I don't see how this could happen. When we initially schedule a server, we populate the retry field in the filter_properties and set num_attempts to 1:"
1781286,2018-07-11 22:21:25 UTC,"The except block in comment 1 is not entered, because the exception doesn't get raised until after that, line 652 in stable/queens:"
1781286,2018-07-11 22:36:37 UTC,"OK looking at the stacktrace I see it's not the '_destroy_build_request' call that's blowing up on reschedule, it's the up-call to get the availability zone for the next chosen host from the list of alternates:"
1781286,2018-07-11 22:55:48 UTC,This appears to trace back to https://review.openstack.org/#/c/446053/
1781286,2018-07-11 23:00:09 UTC,"One idea for fixing this would be to set the AZ for each host in the list of Selection objects that come back from the scheduler - that happens at ""the top"" where we have access to the API DB and thus the aggregates table."
1781286,2018-07-11 23:23:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/581910"
1781286,2019-09-30 22:01:26 UTC,Note for backports: this problem goes back to Pike but we won't be able to backport the fix since it's going to require RPC API version changes.
1781286,2018-07-12 22:21:38 UTC,I had to re-learn why this part of comment 2 isn't a problem:
1781286,2018-08-02 10:36:44 UTC,"Reviewed:  https://review.openstack.org/582412
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=276130c6d1637f8e0f39ba274e2619a115a8fa1a
Submitter: Zuul
Branch:    master"
1781286,2018-08-03 07:31:36 UTC,"Reviewed:  https://review.openstack.org/581910
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1160ae7a6585c1567e2e91badb4c312533d15686
Submitter: Zuul
Branch:    master"
1781286,2018-08-03 22:12:18 UTC,Note related bug 1781300.
1781286,2018-08-03 22:23:45 UTC,I think this is also for reschedules during server create because of this call:
1781286,2018-08-03 22:33:14 UTC,Tracking with blueprint https://blueprints.launchpad.net/nova/+spec/fix-reschedule-up-calls for Stein.
1781286,2018-08-07 21:25:37 UTC,"Yes Matt, I believe it was server create where I originally hit this."
1781286,2019-04-02 23:47:09 UTC,"Yup I hit it during server create as well (this is on a Train devstack with 2 cells and 3 computes, where 2 computes are in cell1 and that's where I got a reschedule on server create because of a port binding failure on the first compute attempted). Note also that the server is stuck in BUILD status due to this, it is not set to ERROR status:"
1781286,2018-07-12 22:28:56 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/582412"
1781287,2018-07-12 05:13:34 UTC,ACK from the Lubuntu Team.
1781290,2019-06-29 17:24:59 UTC,"The procedure is described in the KiCad-ngspice tutorial
http://ngspice.sourceforge.net/ngspice-eeschema.html#multi"
1781290,2019-06-29 09:16:43 UTC,"Well, the user can work around the problem, if he/she is experienced enough with ngspice (subcircuits)."
1781290,2018-07-12 11:25:17 UTC,"@Holger,
First, thanks for all your work on ngspice and your help for Kicad."
1781290,2018-07-12 14:44:21 UTC,"@Holger, unfortunately this is a side effect of changing our logic (and op-amp) symbols from having power pins on every unit to having a separate unit for just the power pins.  Your best bet is to checkout the old logic and op-amp symbol libraries or create your own symbol libraries.  If all goes as planned, the new symbol file format will allow for using separate power pin units and still generate a valid spice netlist.  Sorry about the hassle.  Changing the symbols resolved the hidden pins issues which most users didn't like but it created the problem you are experiencing."
1781290,2018-07-12 19:32:06 UTC,"The spice simulation already requires special symbol, not least for GND, so it is not unreasonable to have special logic symbols for simulation."
1781291,2019-07-17 08:35:54 UTC,"Reviewed:  https://review.opendev.org/671181
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=ea5cbf633cfa56a418a79cde4ccfea0c1f6f3f92
Submitter: Zuul
Branch:    feature/losf"
1781291,2019-07-17 03:53:37 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/671181"
1781291,2019-07-13 00:34:13 UTC,"Reviewed:  https://review.opendev.org/667203
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=a1af3811a79963e2e5d1db3e5588cbc9748f9d57
Submitter: Zuul
Branch:    master"
1781291,2019-07-22 20:15:06 UTC,This issue was fixed in the openstack/swift 2.22.0 release.
1781291,2018-07-26 06:31:29 UTC,s/We should get the sharder to update some memcache cache/We could get the sharder to update some memcache cache/
1781291,2018-07-26 06:29:12 UTC,"I like the idea of caching in the proxy, as the other options are leaving it to the sharder to move them so putting it off. In the shard case ""most"" the time the updates will goto the correct place, and when not, we're putting it off until later."
1781291,2018-07-26 15:45:25 UTC,"I agree caching is hard, but we need to keep thinking about it.  The caching doesn't have to be in the proxy-server process or memcache."
1781292,2019-06-21 22:44:24 UTC,"Pretty sure this can affect writes, too..."
1781292,2019-07-11 18:01:39 UTC,I *think* this was fixed by https://review.opendev.org/#/c/667411/ -- see also: https://bugs.launchpad.net/swift/+bug/1833612
1781298,2018-12-30 12:05:09 UTC,"When I have only external HDMI enabled and close my laptop and turn off the external HDMI screen, upon lid open I get:"
1781298,2019-01-05 01:55:45 UTC,Thanks Timo for testing!
1781298,2018-12-30 17:39:36 UTC,"Thanks Martin for testing my patch, I'm glad it fixed the problem for you."
1781298,2018-12-30 13:51:13 UTC,"Created attachment 8210
Xorg.0.log"
1781298,2018-12-30 13:49:52 UTC,"Hi,
  sorry to bug you again. I let the laptop with external HDMI enabled and internal LCD disabled. After a while external HDMI felt asleep into stand-by mode. But, I could not wake up a screen when touching my keyboard. Not even ctrl+alt+f1 helped (which usually brings me into framebuffer console out off the X11 windows and hence wakes up my screen). Alt+SysRq+S seemed to trigger some disk activity at least. The trick which worked was to close the lid and open again. That at least woke up the internal LCD of the laptop. Although it so far feels like a bug in this case it was better than nothing."
1781298,2018-12-30 11:53:19 UTC,"BTW, this would be maybe more helpful:"
1781298,2019-01-03 05:08:38 UTC,For me the crash happens reliably when the display is put to power off state (e.g. xrandr --output eDP1 --off). The attached patch fixes the issue for rme too.
1781298,2018-12-28 03:00:47 UTC,"Created attachment 8203
possible-fix.patch"
1781298,2018-08-17 13:04:27 UTC,"Created attachment 7886
Full backtrace acquired with `bt f` in GDB"
1781298,2018-08-24 03:10:52 UTC,"I noticed this bug a while ago, xfdesktop crashes when I close/open my laptop lid.
It segfaults at https://git.xfce.org/xfce/xfdesktop/tree/src/xfce-backdrop.c?id=49a527bc928d776e497ee45e0a458e97bf8e234c#n2012 something fishy is passed to gdk_pixbuf_loader_write then gdk_pixbuf chokes.
Needs further investigation..."
1781298,2018-12-30 11:51:09 UTC,"Hi Andre,
   I applied the patch to xfdesktop-4.13.2 on my Gentoo Linux. After a brief testing I have indeed no new core dumps in my /var/dumps/, great. I realized that if I use Fn+F1 to use only my external HDMI display and to turn off the laptop's internal LCD, after lid open my laptop has again enabled LCD screen and using the size of the external HDMI display (1920x1200 instead of its own max 1366x768). I do not recall seeing this before. Could this be caused by your patch?"
1781298,2018-10-19 01:16:30 UTC,*** Bug 14002 has been marked as a duplicate of this bug. ***
1781298,2018-12-01 03:14:45 UTC,*** Bug 14927 has been marked as a duplicate of this bug. ***
1781298,2018-10-11 06:10:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781300,2019-10-23 18:29:43 UTC,"Reviewed:  https://review.opendev.org/686276
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=20de81c7c0dfe234805fa9552b1b83f3ea6df7a1
Submitter: Zuul
Branch:    stable/rocky"
1781300,2019-09-27 09:06:04 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1781300,2019-08-12 20:42:17 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1781300,2019-06-28 01:44:59 UTC,"Reviewed:  https://review.opendev.org/663030
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d4bc147c38c5fe7c4adb5925225ced16d2ff4757
Submitter: Zuul
Branch:    stable/stein"
1781300,2019-06-04 13:34:21 UTC,"This is low priority since most production deployments are probably not running with split conductors and the cell conductor being isolated from the API DB, it's mostly only an issue we hit in devstack, therefore I probably won't backport this past Stein unless someone needs it."
1781300,2019-06-04 13:33:09 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/663030"
1781300,2019-06-03 21:31:35 UTC,"Reviewed:  https://review.opendev.org/581912
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=22dd4fca3837d6cea3f983b021aa6907695a540b
Submitter: Zuul
Branch:    master"
1781300,2020-02-25 12:13:45 UTC,This issue was fixed in the openstack/nova 18.3.0 release.
1781300,2019-04-18 13:27:03 UTC,Fix is here https://review.openstack.org/#/c/581912/ - it wasn't tracked by launchpad for some reason.
1781300,2019-04-18 13:43:42 UTC,"Marking this as low severity since most deployments are probably running all services (except maybe nova-compute) with the api_db/connection configured so they wouldn't hit this, but it's definitely something we can hit in a multinode devstack environment in the gate."
1781300,2018-07-11 23:48:35 UTC,This goes back to Pike when targets_cell() was added:
1781300,2018-07-11 23:57:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/581912"
1781300,2019-10-02 20:20:58 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/686276"
1781300,2018-08-03 22:12:04 UTC,Note related bug 1781286.
1781300,2018-08-03 22:11:20 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/581912
Reason: This is the wrong fix as Mel pointed out, the cell targeting isn't persisted across rpc and we only get away with it in unit/functional tests because of the CheatingSerializer."
1781300,2018-08-03 22:33:07 UTC,Tracking with blueprint https://blueprints.launchpad.net/nova/+spec/fix-reschedule-up-calls for Stein.
1781307,2018-07-15 23:18:50 UTC,Here is some further information.
1781307,2018-07-16 04:16:33 UTC,Here is more information yet.
1781307,2018-08-03 05:20:59 UTC,"Please compare #1637499 and #1780729. (The latter, opened by me, is pretty much a duplicate of this bug, so it could be deleted.)"
1781307,2018-08-04 20:46:00 UTC,"This problem may involve window managers. For apparently - that is: I'm told - the problem does not occur on XFCE, which uses a different window manager to Cinnamon. Cinnamon uses Mutter, which is a version of Muffin. xfce uses something else by default, I think."
1781307,2019-01-30 03:03:37 UTC,For some reason - a Mint update - this problem has . . disappeared.
1781307,2019-07-13 15:13:42 UTC,"Seems like this was either an edge case, or resolved sometime in the last year."
1781307,2019-07-13 15:16:46 UTC,"On second thought, ""Fix Released"" is probably more accurate to say, even if I do no know when a fix was released."
1781311,2019-05-23 01:38:18 UTC,"I'm also on Linux Mint 19 x64 Cinnamon but experienced no crashes, only an error notification pops up everytime I start Cinnamon."
1781311,2019-05-23 01:58:01 UTC,I have abandoned Docky. It seems unmaintained. Instead I use a Cinnamon panel that I have made transparent at the edges. It is not perfect but it is not bad. One can get an idea of how to do achieve such a thing by looking at the 'SimpleDock' theme that is downloadable via Cinnamon's built-in theme downloader. Ensure that you tick Cinnamon's panel option 'allow pointer to pass through the edges of panels'. I am unsubscribing from this bug report.
1781315,2018-07-12 02:31:43 UTC,"Looks like Ubuntu might also be missing the dependency:
  https://github.com/intel/gmmlib"
1781315,2018-07-12 23:55:04 UTC,*** This is an automated message ***
1781315,2018-07-17 06:27:28 UTC,Note however the new driver supports fewer CPU generations than intel-vaapi-driver so shouldn't be the default unless automatic fallback works when both drivers are installed.
1781315,2018-07-18 08:20:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781317,2018-07-12 07:12:16 UTC,####The following is the repaired deployment log####
1781317,2018-07-12 10:59:23 UTC,I don't see any issues in the attached log.
1781317,2018-07-12 12:20:57 UTC,The log in the bug description is problematic:
1781317,2018-07-23 07:19:10 UTC,"Change abandoned by wangwei (<email address hidden>) on branch: master
Review: https://review.openstack.org/581632
Reason: https://review.openstack.org/584728
This patch approach is better for solving this problem, the include module will be removed in ansible version 2.8, so replacing it with include_tasks is a better approach."
1781324,2018-07-12 05:07:51 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1781330,2018-07-12 06:08:12 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1781365,2018-07-18 20:35:39 UTC,"It's possible, though requires some manual work."
1781376,2018-09-03 08:32:31 UTC,"Reviewed:  https://review.openstack.org/588978
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=7f973380b639d6222677be8ba7d4c02b9cc2aab5
Submitter: Zuul
Branch:    master"
1781376,2018-08-12 10:28:30 UTC,"Reviewed:  https://review.openstack.org/589394
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=945b1e368c651ffa3655f42df724d9f13a7b6b96
Submitter: Zuul
Branch:    master"
1781376,2018-08-07 08:09:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589394"
1781376,2018-08-05 14:52:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588978"
1781376,2018-07-29 08:51:42 UTC,"Reviewed:  https://review.openstack.org/585790
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=53ad85ac35d8b24089cee292848c0f28bb2582ab
Submitter: Zuul
Branch:    master"
1781376,2018-07-29 08:51:35 UTC,"Reviewed:  https://review.openstack.org/585771
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=ad9add8d6fc8c469393afb2c02551f52b11b9f30
Submitter: Zuul
Branch:    master"
1781376,2018-07-26 10:34:43 UTC,"Reviewed:  https://review.openstack.org/583928
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=e52ba1ee316eced9d0849e273f3dbc57af7fa2ef
Submitter: Zuul
Branch:    master"
1781376,2018-07-26 09:52:55 UTC,"Reviewed:  https://review.openstack.org/583878
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=f6242655581c676e97e91b059b43bbff693790a7
Submitter: Zuul
Branch:    master"
1781376,2018-07-25 15:38:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585790"
1781376,2018-07-25 09:41:14 UTC,"Reviewed:  https://review.openstack.org/583911
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=8114ddbf8a7c3082347896a09b6a8e799b5d3b3a
Submitter: Zuul
Branch:    master"
1781376,2018-07-25 13:50:00 UTC,"Reviewed:  https://review.openstack.org/583920
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=d2fd3fbc70f894c0cf40e3fdb8ab669ab6a12809
Submitter: Zuul
Branch:    master"
1781376,2018-07-25 14:52:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585771"
1781376,2018-07-23 10:38:54 UTC,"Change abandoned by Shachar Snapiri (<email address hidden>) on branch: master
Review: https://review.openstack.org/583924
Reason: There is a problem with removing the attached_mac as it is sometimes different than the MAC we see on the lport"
1781376,2018-07-19 11:00:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583928"
1781376,2018-07-19 10:47:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583924"
1781376,2018-07-19 10:43:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583920"
1781376,2018-07-19 10:25:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583911"
1781376,2018-07-19 08:22:50 UTC,"Reviewed:  https://review.openstack.org/581355
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=cbb9993b3d762b5e3be266383b5953ab146dc29e
Submitter: Zuul
Branch:    master"
1781376,2018-07-16 10:23:24 UTC,"Reviewed:  https://review.openstack.org/581350
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=41595e74531cf8f88c229b3dbaed296a789b52ff
Submitter: Zuul
Branch:    master"
1781380,2018-08-01 14:22:26 UTC,"Please ignore my comment above - I do not face this issue, and instead there was an issue with my code w.r.t. arg order placement made to the Jenkins class method call."
1781380,2018-07-12 09:59:32 UTC,python-jenkins==1.0.2
1781381,2019-09-04 19:50:07 UTC," my cmd2.Cmd wrapper with a workaround, simply replaces b'' w/ {}"
1781381,2019-09-04 19:51:29 UTC,suggest editing library to replace all b'' with {} in all jenkins_open calls.
1781381,2019-11-05 15:03:04 UTC,For some reason the `req.headers` in `maybe_add_crumb` are in bytes when `delete_build` is called with python3.
1781381,2020-10-06 13:35:30 UTC,I had the same issue and Robbert's (robkorv) fix worked for me.
1781381,2020-10-07 14:55:16 UTC,"It seems more appropriate to update the request object instead. With your patch, you'll ignore added headers(including the crumb).
To prevent this, just change the request instanciation for the delete_build call (wipeout_job_workspace has the same call so it fixes that as well):"
1781389,2019-09-12 13:56:27 UTC,If it's a bug - it's Ironic bug - please raise it there.
1781392,2018-07-13 21:30:36 UTC,"ok thanks
What I just tried
clean install of ubuntu server
updgrade to cosmic
install lxqt"
1781392,2018-07-13 14:58:04 UTC,"lxqt-common is deprecated in upstream, debian and ubuntu - and anywhere else. It will be removed from debian testing soon and from sid after the upcoming debian release - please see also the respective launchpad bug in lxqt-common. In short: lxqt is not co-installable with the current version of LXQt."
1781392,2019-03-23 15:46:20 UTC,"When the config files moved from /etc/xdg/lxqt to /usr/share/lxqt
/usr/bin/startlxqt should have had"
1781392,2018-07-13 08:43:09 UTC,"I also have a Debian Stretch laptop with LXQT installed on it.
I notice that this does have an /etc/xdg/lxqt folder
This appears to be created by Debian package lxqt-common"
1781392,2018-07-13 00:07:27 UTC,"ok, it's a bit superfluous:"
1781392,2018-07-13 08:51:08 UTC,On the Ubuntu laptop:-
1781404,2018-07-13 14:27:09 UTC,"I tried to open this bug directly to Gala, but I couldn't because it says that Gala must be configured in order for Launchpad to forward bugs to the project's developers. So I opened at pantheon-dock, the only suitable option that appeared when I made the bug report at elementary os launchpad. How can I report bugs for Gala?"
1781404,2018-07-13 14:59:36 UTC,Gala bug reports are living here: https://github.com/elementary/gala/issues
1781404,2018-07-16 13:53:47 UTC,"Thanks for the information, just a last question. Have you ported this bug report to GitHub? If not, then I'll report there."
1781411,2020-10-02 09:25:19 UTC,"The name of the project used by services is not necessarily the same across all deployments. It can be ""service"" or ""services"" depending on how you installed OpenStack."
1781414,2020-07-01 20:31:47 UTC,"Thank you for your bug report, it doesn't seem it was an issue with the pdf viewer though"
1781414,2018-07-13 21:54:12 UTC,"Thank you,"
1781414,2018-07-13 12:43:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781414,2018-07-13 12:46:08 UTC,I can confirm same error output
1781414,2018-07-13 13:37:55 UTC,EDITADO: Após muito pesquisar consegui resolver este probleminha com estes dois comandos:
1781418,2018-10-26 22:57:37 UTC,After the package upgrade to libpam-kwallet 4:5.12.7 from bionic-proposed the issue has gone away. That seems to be due to commit 8da1a470 included in this version:
1781418,2019-07-03 09:07:57 UTC,"Seems this was my problem too. What I noticed was that docker suddenly could not be run except as root. And none of the usual remedies for that had any effect. Luckily KDEwallet started demanding a login at the same time which pointed me to this bug. Tobias advice above fixed the problem so I think that confirms the diagnosis. Kubuntu 18.04 with KDE Plasma 5.12.7, KDE Frameworks 5.44.0 and Qt 5.9.5."
1781418,2019-05-03 00:10:28 UTC,I had the same issue. Even with libpam-kwallet5 to version 4:5.12.7-0ubuntu0.1.
1781418,2019-01-14 07:01:50 UTC,"I faced this problem on two different machines (both lightdm + plasma desktop, on both I happily used this combination on Ubuntu 16.04 but once I upgraded to 18.04, or soon afterwards, I lost all my groups)."
1781418,2018-12-02 14:35:52 UTC,"Have just went to this bug while trying to solve PAM warnings problem on my AskUbuntu question ( https://askubuntu.com/q/1096931/66509 ).
So I have installed all mentioned package with:"
1781418,2018-11-13 10:34:39 UTC,"Similarly to comment #15: updating libpam-kwallet-common, libpam-kwallet4 and libpam-kwallet5 to version 4:5.12.7-0ubuntu0.1 from proposed repository and rebooting didn't change anything for me."
1781418,2018-10-30 02:45:17 UTC,"I don't know why this happens, but seems to be something broken by the way and update didn't fix anything in my case. There are still 2 calls to 'setgroups(0, NULL)', one for libpam-kwallet and another for pam_kwallet5 after my user and group are already set. Of course, this drops all supplementary groups. Maybe I miss something. The only workaround is commenting out both libraries in lightdm config."
1781418,2018-10-29 16:04:50 UTC,"Upgrading libpam-kwallet5 to 4:5.12.7-0ubuntu0.1 and a reboot fixed this problem on my machine.
Thanks for linking this to #1784964 TJ."
1781418,2018-10-28 21:06:21 UTC,ZdravkoG:
1781418,2018-10-28 16:05:38 UTC,"Hi everyone,"
1781418,2018-10-26 21:41:53 UTC,"I added an additional log report to the function drop_privileges() since that contains a call to setgroup(0, NULL) which, if called as the user, would have the effect of removing all the supplementary groups."
1781418,2018-10-28 22:17:43 UTC,"Hi @tj,"
1781418,2018-10-08 17:31:15 UTC,Some other notes:
1781418,2018-10-08 17:28:33 UTC,"I faced this problem on two different machines (both lightdm + plasma desktop, on both I happily used this combination on Ubuntu 16.04 but once I upgraded to 18.04, or soon afterwards, I lost all my groups)."
1781418,2018-08-23 19:09:10 UTC,"Switched to gdm for now, which does not have this behaviour."
1781418,2018-10-24 13:01:18 UTC,"Hello,"
1781418,2018-07-20 12:21:05 UTC,":D
Well I most certainly hope people can *think* when they see the lines are active by default."
1781418,2018-07-20 09:35:32 UTC,"Except I can't, so it has to stay there. Hopefully everybody who runs into this reads on..."
1781418,2018-07-20 09:34:36 UTC,"@MibuKyoshiro True, sorry I seem to have been overly tired when writing this. I'm correcting it in my original comment."
1781418,2018-07-18 14:05:24 UTC,I can confirm *commenting out* (and not the reverse) these lines in /etc/pam.d/lightdm fixes the problem:
1781418,2018-07-18 13:59:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781418,2018-07-16 06:24:59 UTC,Simon
1781418,2018-07-15 18:52:08 UTC,"I found the solution here: https://unix.stackexchange.com/questions/454593/groups-not-registering-in-x
It seems to be caused by an update to libpam-kwallet5.
Uncommenting the following lines in /etc/pam.d/lightdm resolved the issue:"
1781421,2018-07-12 19:09:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582342"
1781421,2019-06-19 19:47:28 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/582342
Reason: My fix might be incomplete, it's hard to say without a functional test written before changing how this code works to make sure I don't regress something in the API behavior."
1781425,2018-09-03 06:53:26 UTC,"Yes, installing gstreamer1.0-gtk3 solves the problem for me."
1781425,2018-08-29 10:25:35 UTC,"I have the same bug after upgrading to 18.04. I tried to add video to the pdf with multimedia package and pdfpc-movie, neither is working. The example from https://pdfpc.github.io/ is also not working."
1781425,2018-09-02 19:10:58 UTC,Probably the same as #1790389; try installing gstreamer1.0-gtk3.
1781426,2019-10-21 08:35:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781426,2019-10-21 08:36:40 UTC,Still exists in 19.10 Eoan.
1781426,2020-01-15 22:03:49 UTC,"Totally confirmed but I got to be honest with you: I have *zero* hope to see this fixed. LXDE is pretty much dead. It's certainly true with lxhotkey which has seen no changes (outside of automatic translation updates) since *2016*:
https://git.lxde.org/gitweb/?p=lxde/lxhotkey.git;a=shortlog"
1781426,2020-02-16 18:41:57 UTC,"lxhotkey Ctrl key problem can be avoided by using it at the command line, e.g."
1781426,2021-02-04 12:03:00 UTC,"This issue is fixed in recent upstream sources 0.1.1 which is in the archive now:
https://launchpad.net/ubuntu/+source/lxhotkey/0.1.1-1"
1781427,2018-07-20 10:39:12 UTC,"This bug needs to be public, for me to reference in the changelogs for auto-closing and the SRU process."
1781427,2018-07-20 10:39:39 UTC,"I see no private information posted to this bug, therefore making it public."
1781427,2018-07-24 12:39:18 UTC,This bug was fixed in the package mdadm - 4.1~rc1-4
1781431,2018-07-12 16:47:04 UTC,Please your feedback
1781432,2018-07-12 19:08:40 UTC,"As the knobs in the effects section are often changing what they are controlling, whether wet/dry and super or the individual knobs of different units, I would say the loss of position sync on changing mode is a minor annoyance personally...."
1781432,2018-07-12 18:49:11 UTC,"Can this be disturbing, that we may get out of sync situation on a controller?
I expect not, because you switch the knobs around anyway."
1781439,2019-09-26 13:22:07 UTC,Create a bug in placement storyboard as placement bugs are handled there https://storyboard.openstack.org/#!/story/2006620
1781439,2018-07-24 10:06:34 UTC,"I did some search and found that
https://review.openstack.org/#/c/565604/31/releasenotes/notes/consumer_generation-f576ac2594b24e2e.yaml
says only impact POST and PUT"
1781444,2018-07-12 17:21:34 UTC,"Simple patch to add this action to the same context menu as the ""Whole Net"" selection and friends."
1781444,2018-07-12 18:43:41 UTC,"Hi John,"
1781444,2018-07-12 19:43:18 UTC,"I have already started working on a Selection Filter that will take advantage of upcoming properties system. The goal is to show a list of properties and let the user select the filtering criteria (e.g. type == via, net == Gnd, size == 0.5 mm). The feature is not advanced enough to show off in public, but it is already working proof-of-concept."
1781444,2018-07-12 22:28:55 UTC,"Yes, both those make sense."
1781447,2019-10-16 06:10:16 UTC,Could you please attach the output of:
1781447,2019-12-22 04:17:22 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1781447,2019-12-22 04:17:24 UTC,[Expired for snapd because there has been no activity for 60 days.]
1781450,2019-05-07 02:24:55 UTC,"So, in 2.6 adding when we are trying to add storage to lxd and deploy unit, Juju no longer allows it: https://pastebin.ubuntu.com/p/FNVJ2wVDFN/"
1781450,2018-08-20 18:54:11 UTC,2.4.2 has a pre-error that storage on the containers won't work but there's a larger issue in that we need to do better in allowing things in an error state to get destroyed. That's a bigger chunk to come in a future release.
1781450,2018-08-15 21:27:21 UTC,"Today, I couldn't get remove-unit to work.  Will have to investigate further."
1781450,2018-08-14 18:46:55 UTC,Reproduced with:
1781450,2018-08-14 19:27:38 UTC,correction:
1781450,2018-07-15 08:18:39 UTC,"It does look a bit like a duplicate at least on the potential fix side, but when creating an LXD container with storage, it either should immediately give an error (different fix), or be able to be removed with ease after noticing the error (same fix, I believe)."
1781450,2018-07-13 08:34:59 UTC,Looks like a duplicate of pad.lv/1779336
1781450,2018-07-12 20:53:52 UTC,Thanks for the information.
1781450,2018-07-12 20:41:33 UTC,I'm assuming there was another part of the deploy arg that mentioned putting the unit into a lxd container?
1781450,2018-08-14 18:44:00 UTC,"This is different from 1779336.  Machine 0/lxd/0 is created as a juju machine, but never leaves the pending state.  In 1779336, the juju machine isn't created."
1781458,2018-07-16 23:27:54 UTC,"Yeah, this is kinda daft, but it was the same in the bionic GA release. We should fix it soon though."
1781459,2018-07-16 21:44:21 UTC,I can confirm this behavior.  Netplan apply does the following:
1781459,2018-07-23 03:24:08 UTC,"`netplan apply` also won't change bridge/bond parameters: LP: #1746419, we should document that too."
1781464,2019-09-19 11:58:44 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1781468,2018-07-18 10:29:52 UTC,"Fix proposed to branch: stable/18.05
Review: https://review.openstack.org/583543"
1781468,2018-07-18 19:58:19 UTC,"Backport completed to the stable gnocchi charm:
https://review.openstack.org/#/q/topic:bug/1781468+(status:open+OR+status:merged)"
1781468,2018-07-18 19:32:15 UTC,"Reviewed:  https://review.openstack.org/583543
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=7f870c13f1b35e76b9e674a15db44c0a99ec8979
Submitter: Zuul
Branch:    stable/18.05"
1781468,2018-07-18 19:30:51 UTC,"Reviewed:  https://review.openstack.org/583544
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=83fd1606e1561c45623b981eaf37f434a9524296
Submitter: Zuul
Branch:    stable/18.05"
1781468,2018-07-18 10:30:06 UTC,"Related fix proposed to branch: stable/18.05
Review: https://review.openstack.org/583544"
1781468,2018-07-18 05:17:40 UTC,"Reviewed:  https://review.openstack.org/583345
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=bc1745115b6a9c7837075a4353d60a1e5a1e2ca9
Submitter: Zuul
Branch:    master"
1781468,2018-07-13 11:55:32 UTC,"This is due to some sort of packaging problem - the api-paste.ini from the older gnocchi version is preserved during the upgrade process, and the wgsi entry points change."
1781468,2018-07-16 07:12:05 UTC,"Reviewed:  https://review.openstack.org/582752
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=60678f23b107d346f2de5acdded2ea48c624cd94
Submitter: Zuul
Branch:    master"
1781468,2018-07-13 12:10:31 UTC,@pike postinst writes api-paste.ini
1781468,2018-07-17 19:31:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/583345"
1781468,2018-07-15 10:30:52 UTC,https://review.openstack.org/582752
1781468,2018-07-13 12:11:08 UTC,We do use:
1781477,2019-02-26 13:43:43 UTC,Is this still an issue?
1781479,2018-07-14 14:36:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781481,2018-08-13 14:40:06 UTC,"I'm not able to reproduce this with the current snap. Can you try again with the latest build? I've got (from ""snap info inkscape"")"
1781481,2019-06-10 07:59:07 UTC,"Closing as there has been no response for 60 days. If you still have a similar issue, please file a report on our new bug tracker: https://inkscape.org/report. Thank you!"
1781491,2018-07-12 22:07:53 UTC,Or just allow the user to name the user layers like we do the copper ones.
1781491,2019-05-02 09:59:33 UTC,"I think this is due to be worked on in the v6 roadmap, so tentatively setting the milestone."
1781502,2020-05-11 20:08:23 UTC,"Is this still an issue, or was this resolved by updates to MAAS or Maniacs-setup?"
1781502,2018-07-12 23:39:08 UTC,":~$ sudo apt-cache policy maas
maas:
  Installed: 2.3.0-6434-gd354690-0ubuntu1~16.04.1
  Candidate: 2.3.0-6434-gd354690-0ubuntu1~16.04.1
  Version table:
 *** 2.3.0-6434-gd354690-0ubuntu1~16.04.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0.0~beta3+bzr4941-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages"
1781502,2018-07-12 23:38:47 UTC,"~$ sudo apt-cache policy maas-cert-server
maas-cert-server:
  Installed: 0.3.4-0~201806080105~ubuntu16.04.1
  Candidate: 0.3.4-0~201806080105~ubuntu16.04.1
  Version table:
 *** 0.3.4-0~201806080105~ubuntu16.04.1 500
        500 http://ppa.launchpad.net/hardware-certification/public/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status"
1781502,2018-07-12 23:38:22 UTC,"at /etc/cron.d/apt-mirror
#
# Regular cron jobs for the apt-mirror package
#
0 4	* * *	apt-mirror	/usr/bin/apt-mirror > /srv/mirrors/archive/var/cron.log"
1781509,2018-07-13 13:27:42 UTC,"When I open 950.data.seed-values.sql with vim, I see the same corrupted characters as those displayed in the client.  So if vim isn't playing tricks on me, the issue seems to be with the data, not the display."
1781509,2018-09-14 05:48:19 UTC,"Using Ben's test server with Evergreen 3.2 beta1, I can confirm that the problem is still there."
1781510,2020-05-26 19:39:29 UTC,"@Alvin Penner
Sorry for this long time before answer !
I'm searching a way to get out of this bug and find this thread again ;)
I downloaded the previous files again, one year after and the bug still there using Inkscape 0.92.3 (2405546, 2018-03-11) on Linux Mint 19.3 and kernel 5.3"
1781510,2020-01-25 12:30:16 UTC,"Also not reproduced in Inkscape 1.1-dev (2a5d477, 2020-01-18), Windows 10. If the issue occurs again, feel free to reopen at http://inkscape.org/report."
1781510,2019-01-29 13:16:53 UTC,I had the same problem with a document and can easily reproduce the bug with the file above from Tom Fields.
1781510,2018-07-13 10:39:30 UTC,"crash confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1781510,2019-01-29 14:38:03 UTC,@lamballe - could you indicate which version of Inkscape?
1781513,2018-09-10 08:54:45 UTC,Finished at:
1781513,2018-09-10 10:17:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781513,2019-10-22 07:20:26 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1781515,2018-07-13 02:16:57 UTC,"Switching the resolution with -vga std was working fine before, I'm not sure on which version it started having this issue, but it should be on a recent version."
1781515,2018-07-13 04:06:43 UTC,"Hi Diego,"
1781515,2018-07-13 04:27:20 UTC,"Hi Francisco, thanks for your quick reply."
1781515,2020-11-12 15:37:07 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1781515,2021-01-12 04:17:30 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1781525,2018-07-13 04:25:08 UTC,"I browse the web site with:
Linux Fedora 27
Firefox Quantum 59.0.2 (64-bit)"
1781526,2019-09-27 05:48:02 UTC,"Ok, closing as Won't Fix then - thanks Michael"
1781526,2019-05-30 15:46:46 UTC,Lowered priority to Medium based on recommendation from IBM.
1781526,2019-04-09 05:55:44 UTC,"FYI bug 1788098 was found to be blocked again, but this does not stop you from prepping the perf-testbed - it only gates the final release of the fix."
1781526,2019-04-03 09:02:30 UTC,"I got the feedback per mail that this will in fact be performance tested by IBM - thanks!
OTOH there is still some uncertainty which benchmark/setup can be used to do so."
1781526,2019-04-02 08:25:46 UTC,Thanks Leonardo!
1781526,2019-03-15 18:49:42 UTC,"------- Comment From <email address hidden> 2019-03-15 14:40 EDT-------
Just updating:
I was able to verify bug 1788098, and backported the kernel patches to Ubuntu-18.04.
The patches are already upstrem on kernel v4.18.20."
1781526,2019-01-07 11:17:22 UTC,Stopped SRU considerations for now due to bug 1788098 being non verifiable (for now).
1781526,2018-12-07 09:59:42 UTC,"------- Comment From <email address hidden> 2018-12-07 04:51 EDT-------
(In reply to comment #16)

> (In reply to comment #14)
> > Marking as incomplete, while waiting for IBM to help unblock LP#1788098.
> > Please add a comment if this dependency can be problem, or the bug can be
> > progressed via an alternate route.
> > Thanks.
>
>
> Hi Jennifer,
>
> Please have a look at above query above from Canonical.
"
1781526,2018-11-29 13:41:29 UTC,"Blocked on bug 1788098 still - lacking a ""block"" status I'll call it incomplete (as it is still feedback we need, yet on another bug)."
1781526,2018-11-27 07:20:37 UTC,"------- Comment From <email address hidden> 2018-11-27 02:13 EDT-------
(In reply to comment #14)

> Marking as incomplete, while waiting for IBM to help unblock LP#1788098.
> Please add a comment if this dependency can be problem, or the bug can be
> progressed via an alternate route.
> Thanks.
"
1781526,2019-09-26 19:39:38 UTC,"------- Comment From <email address hidden> 2019-09-26 15:35 EDT-------
Thank you for all the work on this.  I think we can close this for bionic now.  We need to test the blocking bug, 1788098, to make sure the migration issues are fixed in 19.10.  Then we would be ok with this fixed in Eoan and 20.04."
1781526,2018-08-22 05:43:16 UTC,"FYI - atm this is blocked on 1788098 being delivered
I'm tracking the other bug and we can pick up here again once resolved."
1781526,2018-08-21 04:57:46 UTC,"New Problem, new Bug - at least since the current one is already closed in Cosmic.
Fortunately the SRU itself was still on hold waiting for another PPC fix to complete to bundle them so we can make this part of it still."
1781526,2018-08-20 21:19:35 UTC,"------- Comment From <email address hidden> 2018-08-20 17:12 EDT-------
Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues:"
1781526,2018-08-08 14:09:45 UTC,"------- Comment From <email address hidden> 2018-08-08 10:04 EDT-------
(In reply to comment #9)

> Thanks Jenifer, the Bionic backport is planned.
> FYI on the further timing - Atm I want to push (other) new bits into Cosmic
> before the Feature freeze.
> Then I'll collect libvirt/qemu changes we made in Cosmic and backport all
> applicable including this one to Bionic (which would allow a better
> efficiency to test all of those together).
>
> If the backport of this is more urgent and can't wait these up-to 2 extra
> weeks delay please let me know.
"
1781526,2018-08-08 04:56:30 UTC,"Thanks Jenifer, the Bionic backport is planned.
FYI on the further timing - Atm I want to push (other) new bits into Cosmic before the Feature freeze.
Then I'll collect libvirt/qemu changes we made in Cosmic and backport all applicable including this one to Bionic (which would allow a better efficiency to test all of those together)."
1781526,2018-08-07 21:39:20 UTC,"------- Comment From <email address hidden> 2018-08-07 17:34 EDT-------
I was able to verify the fix in cosmic qemu version 1:2.12+dfsg-3."
1781526,2018-07-20 07:37:05 UTC,This bug was fixed in the package qemu - 1:2.12+dfsg-3ubuntu3
1781526,2018-07-16 16:19:35 UTC,"------- Comment From <email address hidden> 2018-07-16 12:16 EDT-------
Yes it is a recent patch, it is tagged for qemu-3.0.
Thanks I will try to provide ppa test results soon to confirm."
1781526,2018-07-16 08:53:58 UTC,"Part of the 2.12 Test builds at [1] for Cosmic.
It seems good to me, if you can afford a quick test on the ppa feel free to do so.
Otherwise the final 2.12 upload for Cosmic will be what you could test."
1781526,2018-11-26 14:52:36 UTC,"Marking as incomplete, while waiting for IBM to help unblock LP#1788098. Please add a comment if this dependency can be problem, or the bug can be progressed via an alternate route.
Thanks."
1781526,2018-07-16 07:03:16 UTC,"Hi Jennifer,
I'll take a look putting it into the coming qemu 2.12 merge for Cosmic first (needs to be there for the SRU policy anyway). I saw that it is so new, that is isn't even in 2.12 (upstream) so I'll add it as a patch to Cosmic as well."
1781528,2018-07-13 06:08:07 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1781528,2020-04-23 13:24:41 UTC,Thanks for your report. Just pushed a fix to the tracker.
1781534,2018-07-13 07:06:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582456"
1781534,2018-07-13 07:15:49 UTC,And https://review.openstack.org/#/c/580127
1781534,2018-07-13 12:39:01 UTC,And https://review.openstack.org/#/c/582500
1781534,2018-07-30 22:23:32 UTC,"Reviewed:  https://review.openstack.org/582500
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=bebc5848da710ce6cfbbd495da47f4d70c3c86b1
Submitter: Zuul
Branch:    master"
1781534,2019-02-26 13:44:51 UTC,Seems that some services are still missing. Is this still planned work?
1781534,2020-02-28 11:18:59 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/710438"
1781534,2020-05-01 15:14:49 UTC,"Change abandoned by Michele Baldessari (<email address hidden>) on branch: master
Review: https://review.opendev.org/582456"
1781534,2020-05-27 12:51:52 UTC,"Change abandoned by Flavio Fernandes (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/710438
Reason: ."
1781538,2021-02-11 17:54:59 UTC,This method is deprecated:
1781545,2019-07-12 08:28:38 UTC,"Looking at this, I think it makes sense to only add it in the footprint viewer window. The 3D viewer is only openable from the footprint viewer window, so you had to pass through there to get to it and it has to be open for the 3D viewer to be open."
1781545,2018-07-19 16:00:58 UTC,"Jeff, that sounds like a reasonable compromise. A two-step method from CvPcb is fine with me. Having it in the 2D and 3D viewers would be much appreciated."
1781545,2018-07-13 07:40:23 UTC,2D footprint viewer screenshot
1781545,2018-07-13 07:41:38 UTC,"3D footprint viewer screenshot. Place icon where the mouse cursor is, and in the menus."
1781545,2018-07-19 15:40:53 UTC,CvPcb has context menus for View Footprint in 5.1.  I'm not sure I agree with putting Edit Footprint there.
1781556,2019-08-02 08:36:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/674224"
1781556,2019-08-06 15:45:57 UTC,"Reviewed:  https://review.opendev.org/674224
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=7ae3ec0caf7b0778d1e4cb0e3c0783d711d317b7
Submitter: Zuul
Branch:    master"
1781556,2019-09-13 16:05:39 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1781558,2018-07-13 09:03:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582471"
1781558,2019-10-07 13:29:51 UTC,"I'm having a hard time understanding why we should change behavior here. There was a bug in QEMU, that bug has been fixed for over two years, and the fix should be present in QEMU packaged by any self-respecting distro. I'm going to mark this as wontfix. If you disagree, let me know."
1781558,2019-10-07 13:30:51 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/582471
Reason: I don't think this is something we need to _fix_ and have marked the associated bug as wontfix. Please reopen if you disagree"
1781562,2018-12-14 01:19:25 UTC,"This looks like a duplicate of Bug #1758564, which also includes a workaround/fix."
1781562,2019-12-20 20:01:37 UTC,"oops.  This isn't a duplicate of Bug #1758564, but the cause is the same."
1781564,2019-11-26 20:46:43 UTC,Fixed in lazr.smtptest 2.0.4.
1781567,2018-07-13 10:57:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582502"
1781567,2019-06-25 09:00:29 UTC,"Change abandoned by Jose Luis Franco (<email address hidden>) on branch: master
Review: https://review.opendev.org/582502
Reason: https://review.opendev.org/#/c/621553/ was abandoned as it's not needed anymore."
1781568,2018-07-13 12:12:58 UTC,According to http://iso.qa.ubuntu.com/ problems booting the ISO image should be reported against syslinux. If you think this is incorrect then please reassign.
1781578,2018-09-06 17:49:53 UTC,"The smartpqi driver is included in the linux-modules deb. If you are trying to build/use an out-of-tree smartpqi driver (which your taint flags suggest), please be clear about that. It could quite likely be a bug in that out-of-tree driver vs. a bug with Ubuntu."
1781578,2018-07-13 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1781578,2018-07-13 18:23:44 UTC,"Due to nature of the defect, could not run the apport-collect command"
1781578,2018-07-17 19:09:55 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1781578,2018-08-10 10:11:08 UTC,"Hi,
As you suggested, we have upgraded the kernel as per https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds and
OS boots to the updated kernel properly on our cavium server
Due to some issues with aarch64 kernel packages, the ‘build’ directory is missing under /lib/modules/<kver>/ after the update hence unable to build our smartpqi driver to retest this."
1781578,2018-08-16 10:22:28 UTC,"FYI,"
1781578,2018-08-24 10:39:14 UTC,"Hi,"
1781587,2020-07-01 20:31:15 UTC,"Thank you for your bug report, it doesn't seem it was an issue with the pdf viewer though"
1781587,2018-07-13 13:37:07 UTC,EDITADO: Após muito pesquisar consegui resolver este probleminha com estes dois comandos:
1781587,2018-11-25 19:03:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781589,2018-07-13 13:38:48 UTC,"as nvme10n1 is a wal device, you must not pass it via osd-devices to add-disk; the action should probably pre-flight check that to stop this from happening.  A wal/db/journal device will always be non-pristine after the first slice is allocated.  What's happening is that the add-disk action tries to create a OSD device from nvme10n1 and then also tried to allocate a wal LV - which of course fails as there is no available space."
1781589,2018-07-13 13:46:19 UTC,To confirm - the charm only checks osd-devices for pristine-ity.
1781591,2018-07-17 06:55:59 UTC,Issue exists with `make install` of the source package. Contents intended for /usr/share/icons/hicolor are getting copied into /usr/share/icons.
1781591,2018-07-17 07:05:38 UTC,"> Issue exists with `make install` of the source package. Contents intended for /usr/share/icons/hicolor are getting copied into /usr/share/icons.
"
1781597,2019-01-08 07:48:10 UTC,"@sil2100, where can I take a look at those?"
1781597,2019-04-22 06:35:50 UTC,I would very much like the SRU to happen.
1781597,2019-04-20 17:46:48 UTC,"Unsubscribing the Ubuntu Sponsors Team, there is nothing to sponsor."
1781597,2019-01-14 08:41:07 UTC,"The verification of the Stable Release Update for network-manager has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1781597,2019-01-14 08:40:59 UTC,This bug was fixed in the package network-manager - 1.12.4-1ubuntu1.2
1781597,2019-01-14 08:40:19 UTC,"Ok, then indeed this doesn't likely seem to be any regression. Releasing. Thanks!"
1781597,2019-01-09 21:15:11 UTC,"@Alfonso, the sru page http://people.canonical.com/~ubuntu-archive/pending-sru.html , one log example is
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/s/systemd/20181219_195906_de75b@/log.gz"
1781597,2019-01-07 08:21:39 UTC,"There is a series of systemd related autopkgtest regressions listed for this upload. At first glance those seem to be unrelated as the test suite is generally flaky, but I'd like someone to take a look at those and double confirm before we release this to the world."
1781597,2020-02-11 15:31:30 UTC,It looks like the VPN related SRU that was previous to this one was reverted. Could we land this into bionic?
1781597,2018-12-13 10:05:42 UTC,"Verified on cosmic, using network-manager 1.12.4-1ubuntu1.2:"
1781597,2018-12-11 18:43:40 UTC,"Hello Alfonso, or anyone else affected,"
1781597,2018-12-11 17:52:40 UTC,This bug was fixed in the package network-manager - 1.12.6-0ubuntu2
1781597,2018-12-10 21:29:55 UTC,"Uploaded to disco and cosmic now, the bionic SRU is coming next"
1781597,2019-01-09 17:32:30 UTC,"@alfonsosanchezbeato, linked from https://people.canonical.com/~ubuntu-archive/pending-sru.html"
1781597,2020-08-04 13:09:47 UTC,"The bionic n-m updates have been blocked for long enough it's probably not realistic to expect desktop to deal with those now so I'm going to unassign myself & mark as wontfix for bionic, especially that a newer LTS is out now. If someone else want to deal with testing and sponsoring nothing is blocking you though"
1781630,2018-09-28 18:02:36 UTC,Fiz atualização para nova versão do Ubuntu 18.10 e continua a mesma mensagem de erro.
1781632,2018-07-13 16:22:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/582634"
1781636,2018-07-13 21:33:36 UTC,Its probably /dev/sdb2
1781636,2020-04-11 01:32:52 UTC,this probably just needs configuration
1781637,2020-05-17 22:59:18 UTC,"Numpy is simply a package that enhances Blender, but is not required for the core functionality of the application. Additionally, the official way to install Numpy in 20.04 and later is:"
1781637,2020-05-17 22:51:18 UTC,my installed version of blender is 2.82.a+dfsg-1
1781637,2020-05-17 22:42:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781637,2020-05-17 22:46:46 UTC,"this prevents the installation of at least one addin, in my case blenderbim."
1781639,2018-08-08 09:14:17 UTC,note: this problem still appears to be present with grub-pc-2.02-2ubuntu8.2.
1781639,2020-03-25 20:54:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781643,2018-07-24 09:01:14 UTC,"not directly related but looks similar
https://bugs.launchpad.net/nova/+bug/1762423"
1781647,2018-07-19 01:39:46 UTC,"No, the power of gnome-shell's extensibility is also its weakness."
1781647,2018-11-09 11:30:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781647,2018-08-30 07:10:43 UTC,"Thanks. Ugh, System Monitor seems to have caused a couple of bugs..."
1781647,2018-08-30 06:57:13 UTC,"Just for completeness, there have been no more crashes with Removable Drive Menu enabled, so it is likely that System Monitor was the culprit."
1781647,2018-08-02 05:53:44 UTC,Thanks. Though we don't need to wait for the result of further testing to believe the bug is not in gnome-shell.
1781647,2018-08-02 05:40:33 UTC,"So far there have been no lockups since I disabled those two, so I've re-enabled Removable Drive Menu to see if that causes the lockups to return."
1781647,2018-07-18 12:45:47 UTC,"Ok, I have started by disabling Removable Drive Menu and System Monitor and so far, so good. (But since it's random, it might take a while to reproduce anyway.)"
1781647,2018-07-17 02:16:57 UTC,"Yeah, I'm not saying that's wrong. It's just the only explanation I can think of because your gnome-shell seems to be stuck in gvfs code querying the (encrypted) home directory. If correct then that's just a bug."
1781647,2018-07-16 10:42:31 UTC,"I don't think there's anything particularly unusual about my home folder. I formatted the root partition as btrfs instead of ext4 when I did the installation, so the Ubuntu installer put /home into its own subvolume. I also asked the installer to encrypt the home folder, so it's encrypted with ecryptfs."
1781647,2018-07-16 02:32:53 UTC,Thanks for doing this.
1781647,2018-07-16 02:23:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781647,2018-07-13 18:59:38 UTC,"StacktraceTop:
 __GI___poll (fds=0x55ddc16f8270, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
 g_main_context_poll (priority=<optimized out>, n_fds=1, fds=0x55ddc16f8270, timeout=<optimized out>, context=0x55ddc58078e0) at ../../../../glib/gmain.c:4204
 g_main_context_iterate (context=0x55ddc58078e0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3898
 g_main_loop_run (loop=0x55ddbf61e900) at ../../../../glib/gmain.c:4099
 g_dbus_connection_send_message_with_reply_sync (connection=connection@entry=0x55ddbfcb7d30, message=message@entry=0x55ddc4053d90, flags=flags@entry=G_DBUS_SEND_MESSAGE_FLAGS_NONE, timeout_msec=timeout_msec@entry=2147483647, out_serial=out_serial@entry=0x0, cancellable=cancellable@entry=0x0, error=0x7ffdcb8ffa10) at ../../../../gio/gdbusconnection.c:2151"
1781647,2018-07-13 18:50:58 UTC,"I can add that after killing the gnome-shell session, gnome-shell went back to the login screen, but when I tried logging in, the new gnome-shell session crashed."
1781648,2019-03-22 03:47:57 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1781648,2018-09-24 14:47:05 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1781648,2018-09-19 03:32:59 UTC,"Reviewed:  https://review.openstack.org/598152
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=49ce59e1119bbb1d9c837dde1e4ab28888c75d58
Submitter: Zuul
Branch:    stable/rocky"
1781648,2018-08-30 13:47:28 UTC,"Reviewed:  https://review.openstack.org/597606
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5fe80b6339b8a514bb4c1aee1f2d47cd83be592d
Submitter: Zuul
Branch:    master"
1781648,2018-08-30 13:00:02 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/598152"
1781648,2018-08-30 01:12:50 UTC,"Reviewed:  https://review.openstack.org/597571
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4fe4fbe7a43ac7e971b0aabc8a9079c7701cae55
Submitter: Zuul
Branch:    master"
1781648,2018-08-29 16:01:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597571"
1781648,2018-08-29 13:04:45 UTC,Potentially related failure:
1781648,2018-07-16 11:54:31 UTC,From the log [1] it seems that host cell1 and cell2 creation overlaps with the scheduling of the instances [2]. In a run where the test passes the host creation clearly happens before the instance boot. Interestingly the test setUp() asserts the number of hypervisors and that assert passes.
1781648,2018-07-14 13:27:39 UTC,"https://github.com/openstack/nova/commit/6b6d81cf2b4600bafaca05117c079e8a1d240756 merged on July 13 but I'm not sure what it might have caused for a problem, unless it was just something lurking in the tests and adding another test tipped something over."
1781648,2018-07-14 13:26:00 UTC,"According to logstash, this started around July 12."
1781648,2018-08-29 17:17:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/597606"
1781652,2018-07-23 09:48:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781652,2018-07-23 09:49:43 UTC,This hit me too.
1781652,2018-09-07 15:13:55 UTC,I've the same problem.
1781652,2018-12-20 13:06:05 UTC,Adding ONLINK option to netplan is essential.
1781659,2018-08-06 07:41:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781660,2018-07-18 15:47:02 UTC,"Le Fri, 13 Jul 2018 23:01:50 +0000,
Seth Arnold <email address hidden> a écrit :"
1781660,2018-07-24 12:53:40 UTC,"Apparently, the aa.py script is not loading all the profiles in /etc/apparmor.d.  I added this file and the script now works:"
1781660,2018-07-17 19:41:16 UTC,"On Tue, Jul 17, 2018 at 11:30:55AM -0000, Christian Boltz wrote:

> @Yves and Seth: Which version of the AppArmor utils version do you use?
> Is there a special trick to reproduce the error?
"
1781660,2018-07-17 00:46:58 UTC,I think I've recreated this bug locally:
1781660,2018-07-13 23:01:50 UTC,"Hello Yves, does the bash abstraction exist on your system?"
1781660,2018-07-17 11:30:55 UTC,"Unfortunately I can't reproduce this bug (tested with latest git), at least with the simple test script (just a #!/usr/bin/ruby header) I used."
1781663,2018-07-13 21:50:37 UTC,"Hello Emma, this sounds a lot like a bug I experienced when upgrading from 16.04 LTS to 18.04 LTS: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1768379"
1781664,2020-07-09 04:17:16 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1781664,2020-05-09 07:00:12 UTC,Does this still happen with Mixxx 2.2?
1781664,2018-07-15 15:32:41 UTC,"I could load about six flac tracks, after error message pop up.
then fatal crash, i checked memory earlier it was around 1.1Gb working set and free +50%"
1781664,2018-07-15 06:45:56 UTC,Please report also the memory consumption reported in the windows task manager. Maybe we are hunting a memory leak.
1781664,2018-07-14 20:24:38 UTC,Are the files on an external HD?
1781664,2018-07-15 18:32:08 UTC,"Please add the mixxx.log from the fatal crash.
https://www.mixxx.org/wiki/doku.php/finding_the_mixxx.log_file
Hopefully it is still there with a number prefix for every Mixxx start after that."
1781664,2018-07-14 18:06:33 UTC,This error is not related to those two
1781664,2018-07-14 18:02:22 UTC,"Mixxx can't load +90% of tracks after this error happend. It continues prompting error message.
I just close Mixxx and restart, continue preparing tracks for use, and it works well."
1781664,2018-07-14 08:47:55 UTC,"I've never seen this error before, even when testing corrupt files."
1781664,2018-07-14 08:37:29 UTC,Can you identify a set of effected tracks that is effected?
1781664,2018-07-14 20:13:47 UTC,"> It continues prompting error message.
"
1781673,2018-10-09 14:05:29 UTC,"Setting up linux-firmware (1.157.20) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-130-generic
E: No boot partition found !
run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1
dpkg: error processing package linux-firmware (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up linux-image-4.4.0-131-generic (4.4.0-131.157) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
Error! Bad return status for module build on kernel: 4.4.0-131-generic (x86_64)
Consult /var/lib/dkms/i915-4.6.3-4.4.0/1/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-131-generic
E: No boot partition found !
run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-131-generic.postinst line 1052.
dpkg: error processing package linux-image-4.4.0-131-generic (--configure):
 subprocess installed post-installation script returned error exit status 2"
1781680,2018-07-14 00:10:48 UTC,"Sorry, I think this is not actually a bug.  It turns out that what I was calling as ESX host is it's own vCenter.  They are all able to talk to each other and thus any one can be used to manage the others from the web GUI, but this is not the case via the SOAP/REST APIs."
1781680,2018-07-14 00:11:24 UTC,"Nevermind my last comment, it was not intended for this bug, which is indeed a bug!"
1781688,2019-07-16 20:42:50 UTC,"The Eeschema schematic text properties window now uses a different text editor (which supports undo, among other things).  Is ctrl-backspace working now?"
1781688,2018-07-16 13:14:15 UTC,"The key combinations are different on OSX (ctrl-backspace is same as backspace, alt-backspace deletes words), but they appear to work correctly."
1781688,2019-09-16 04:17:37 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1781688,2018-07-16 07:46:38 UTC,"I cannot reproduce the problem on Linux (1a229187), it might be Windows specific."
1781688,2018-07-16 12:58:22 UTC,I can confirm that this does appear to an issue windows.  I'm not sure about macos.
1781692,2018-07-16 21:08:56 UTC,"Hello, I wonder if this is the same issue as https://bugs.launchpad.net/bugs/1781919 -- can you include some journalctl output around the time of this issue?"
1781692,2018-07-16 21:26:33 UTC,"journalctl -xe
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit NetworkManager-dispatcher.service has finished starting up.
--
-- The start-up result is RESULT.
Jul 15 19:21:10 VB-Ubu-64-Alpha dbus-daemon[723]: [session uid=1000 pid=723] Act
Jul 15 19:21:10 VB-Ubu-64-Alpha dbus-daemon[723]: [session uid=1000 pid=723] Act
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-DISKIO-MIB
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB:
Jul 15 19:20:42 VB-Ub..."
1781692,2018-07-16 21:36:09 UTC,"Due to a manipulation error, I losted the original faulty french-speaking install."
1781692,2019-10-10 12:33:24 UTC,"Hello, sorry it's taken so long for us to get back to you about this."
1781692,2019-10-10 12:33:44 UTC,(please set this bug status back to New when replying)
1781692,2019-10-10 14:38:10 UTC,Bug doesn't appear on new version of Ubuntu. I don't use the 18.10 in my test.
1781692,2019-10-10 14:58:35 UTC,"Problem does NOT appear any more : tests use new version of snap or using Ubuntu 18.10 STABLE in place of ""pre version"" used 15 month ago."
1781692,2019-10-15 15:25:57 UTC,To be closed
1781692,2019-10-16 05:16:31 UTC,Thank you Jean-Do for testing this for us!
1781692,2019-10-16 05:17:04 UTC,Closing as suggested by the original reporter. Thanks again to Jean-Do for this report!
1781696,2018-07-16 01:35:41 UTC,I don't think we can do it now. You can do it with these steps: delete VNFFG --> migrate VNFs --> re-create VNFFG.
1781697,2018-08-07 18:59:54 UTC,Please use : https://github.com/major/MySQLTuner-perl
1781697,2018-08-07 18:45:07 UTC,"Older versions of MySQL (<4.0) named the variable simply join_buffer.  The
% was a compatibility requirement."
1781697,2018-08-07 18:40:32 UTC,This script is no longer maintained
1781697,2018-08-07 16:46:23 UTC,Trying to debug I could get rid of the error by replacing as so on line 943 :
1781699,2019-01-14 13:17:44 UTC,"Thank you, Sebastien. Unfortunately that link is behind a restrictive access control, so if there indeed is a ISC DHCP bug tracker ID there, no one has told us here. (ISC can for sure close my ticket as duplicate, if they are already working on this.)"
1781699,2019-05-13 13:56:02 UTC,This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu7.1
1781699,2019-05-10 13:24:25 UTC,"Great, thanks for testing, I'll release these early next week!"
1781699,2019-05-10 13:10:02 UTC,"Thanks for your work, Alex, Andreas and Marc! I can confirm that isc-dhcp-server 4.3.5-3ubuntu7.1 has been running for two days while the previous version crashed every few hours in my environment."
1781699,2019-05-08 06:18:38 UTC,I have tested the -server package on Bionic and I haven't had any crashes yet. Typically in my environment it would have crashed after one hour or two hours the latest.
1781699,2019-05-06 23:11:40 UTC,"I have the packages in for testing, though repro may take some time to occur organically.  I also think it might be prudent to add a Restart=on-failure directive to the systemd units regardless of whether the fix for this issue is effective, so that future bugs don't take down users' networks."
1781699,2019-05-13 14:06:07 UTC,This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu9.1
1781699,2019-05-03 11:39:27 UTC,This has been assigned CVE-2019-6470
1781699,2019-05-02 12:54:15 UTC,"Thanks Alex, let's see if the patch changes after the issue is looked at from a security perspective."
1781699,2019-05-02 07:39:30 UTC,"This looks like a possible use-after-free so likely has a security impact (at a minimum it is a denial of service due to the crash, especially if it can be triggered remotely) - I've reported it to ISC as such who will hopefully assign a CVE and then we can fix it as a security update. For future reference, the RT #48804 contains a patch that should likely be fine for Bionic https://bugs.isc.org/Public/Ticket/Attachment/534989/331007/46719.v4_3.diff"
1781699,2019-05-02 06:05:45 UTC,It is really a shame that the fix of this bug in this basic network infrastructure package has not made it into the distributions (especially Ubuntu) after months. :(
1781699,2019-01-14 14:12:32 UTC,Hello:
1781699,2019-01-14 12:59:35 UTC,"There is no debug symbol here but if it's the same issue than the redhat report then the error tracker bucket for the issue is
https://errors.ubuntu.com/problem/5c6b31248447aaecc5e91304bfd49f40be9eee7b"
1781699,2019-05-06 14:46:46 UTC,Packages for this issue are now available in the security team test ppa here:
1781699,2019-01-14 12:15:25 UTC,"#12: I have, just now. RT #48804."
1781699,2019-01-14 12:25:55 UTC,"Thanks, I linked it to this bug here. Soon someone at isc will unblock it so it's public."
1781699,2018-10-09 20:16:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781699,2018-11-08 12:19:58 UTC,Problem occurs on all our systems after dist upgrade to Ubuntu 18.04.1 LTS (isc-dhcp-server 4.3.5-3ubuntu7). :(
1781699,2018-11-08 15:10:49 UTC,Apparently the issue is caused by this commit https://gitlab.isc.org/wpk/bind9/commit/65a483106e45704e19781bfe4f4634db4f77562e which fixes a bug in the ISC heap library.
1781699,2018-11-08 16:20:39 UTC,"The attachment ""quick-and-dirty-patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1781699,2018-11-16 06:45:15 UTC,Is there now a forecast when a fix will be available in Ubuntu?
1781699,2018-10-26 21:41:13 UTC,"The bug is not present in 16.10 (yakkety, isc-dhcp-server=4.3.3-5ubuntu15.2). It is present in 17.10, 18.04 (isc-dhcp-server=4.3.5-3ubuntu7) and 18.10 (isc-dhcp-server=4.3.5-3ubuntu9). Not sure about 17.04."
1781699,2018-12-13 12:18:34 UTC,To those waiting for a fix: I'm using a workaround by setting systemd to restart the service when it crashes. This works well for me:
1781699,2018-12-13 12:23:37 UTC,"Yes, the problem is certainly exacerbated by the service not having a Restart parameter, but this needs some real attention.  The quick-and-dirty-patch does reduce the crashes, but results in a different crash (albeit less frequently)."
1781699,2018-12-13 12:34:20 UTC,"@pdf: would you please mind posting the different crash report? It can be related to the dirty patch, or there can be another issue. Thanks."
1781699,2018-12-13 13:02:44 UTC,"@radek-zajic I'm not running the patch currently, but I only saw that crash while running with the patch.  If I rebuild using the patch again I'll grab a stack trace (I've just replaced the machine running DHCP)."
1781699,2019-01-14 11:53:18 UTC,Has anybody filed an upstream bug about this at https://www.isc.org/community/report-bug/ ?
1781699,2018-12-13 12:03:54 UTC,Still not fixed :-(
1781701,2018-07-14 10:30:46 UTC,"Hi RJVB,"
1781701,2018-07-14 12:17:04 UTC,"I had not seen the RPATH code for APPLE in the CMake file, and my build scripts set those explicitly which probably explains part of the issue I'm seeing."
1781701,2018-07-14 14:32:29 UTC,"Anyway, I couldn't get the stock version to work."
1781701,2020-08-31 07:13:52 UTC,"Assuming fixed with 1.0 branch, please post new bug on https://inkscape.org/report if not the case."
1781705,2018-07-14 11:15:04 UTC,Exact commits:
1781705,2020-08-03 10:50:29 UTC,This is a universe package imported from Debian. It does not get support from Canonical.
1781705,2020-10-22 20:02:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu."
1781706,2020-09-02 11:25:45 UTC,"I had the same issue on Mint 20 and this fix worked.
I just had to replace step 5) by
sudo python3 -m compileall ."
1781706,2020-07-13 13:07:52 UTC,"Ran into the same issue on Ubuntu 20.04, terminal 1.91-4"
1781706,2019-05-09 02:33:56 UTC,I'm on Terminator 1.91-1 and Ubuntu Linux 18.10 (cosmic) and had the same issue.
1781706,2018-08-03 10:15:36 UTC,See https://bugs.launchpad.net/terminator/+bug/1758564.
1781706,2019-05-09 02:41:53 UTC,"* Apologies for my typo in your first name, Egmont."
1781711,2018-07-14 19:28:35 UTC,"- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1781711,2018-07-14 19:34:20 UTC,may be related to Bug 1679428
1781711,2020-04-07 22:12:21 UTC,Closing because INVALID: Can't replicate.
1781716,2018-08-02 13:43:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781725,2019-01-08 18:59:59 UTC,Labels are now also reported here: https://bugs.launchpad.net/kicad/+bug/1802008
1781725,2018-10-10 02:47:25 UTC,I can confirmed this. It seems that no ERC is performed on hierarchical pins. I have an output pin of a chip connected to an output hierarchical pin and the sub-sheet has that same output hierarchical pin connected to an input of the MCU. No ERC error.
1781725,2018-07-26 20:30:07 UTC,"Today this hit me as well. I had not connected 2 global labels (SCL and SDA) to a connector and of cause, my i2c device did not work very well.
Would really help if ERC could at least warn here (like it does on other unconnected pins without the ""not connected"" symbol attached)
Someone could say that this is visible in the schematic and this is correct but can be easily overseen as i did."
1781725,2018-07-26 08:59:29 UTC,"The same is true for power symbols and global labels.
For power symbols there exists this report: https://bugs.launchpad.net/kicad/+bug/1639400"
1781725,2018-07-16 17:12:05 UTC,This is a valid request.  I think the correct approach to implement is 1) check for unexposed hierarchical pins and 2) check that hierarchical pins are either NC'd or connected at the top level.  This should also fix lp:1747310
1781727,2018-07-16 13:22:23 UTC,Thank you for the patch! This looks reasonable. I'll add this to my review queue.
1781727,2018-07-20 17:33:28 UTC,Awesome thanks :-)
1781727,2020-02-05 08:02:33 UTC,"Hi, was it released? if so, starting with which version? Thanks!"
1781727,2020-02-05 10:01:23 UTC,"Since 0~git148-0ubuntu1, available in Ubuntu 19.10 or the daily PPA at https://launchpad.net/~uvtool-dev/+archive/ubuntu/master (best effort only)."
1781736,2018-10-23 23:56:08 UTC,This bug was fixed in the package ubuntu-themes - 16.10+18.04.20181005-0ubuntu1
1781736,2018-10-22 10:34:14 UTC,Same here:
1781736,2018-10-23 23:56:43 UTC,"The verification of the Stable Release Update for ubuntu-themes has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1781736,2018-10-08 13:43:46 UTC,"Hello Harm, or anyone else affected,"
1781736,2018-10-08 11:19:07 UTC,This bug was fixed in the package ubuntu-themes - 16.10+18.10.20181005-0ubuntu1
1781736,2018-10-18 10:24:21 UTC,Borders are properly themed and with right quality textures in this version:
1781739,2018-07-26 07:56:32 UTC,"Hi, the laptop is on vacation for a couple of weeks now, also I have no
prior experience updating kernels, i'm unsure whether it is wise to do for
me."
1781739,2018-07-14 21:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1781739,2018-07-17 16:13:53 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1781746,2018-07-17 13:17:15 UTC,I believe this bug was only accidentally reported against pkgbinarymangler.
1781746,2018-10-27 10:48:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781746,2018-10-29 10:42:44 UTC,"This issue is fixed in Debian, initramfs-tools version 0.132, please accept this simple, 3 lines patch from Debian into Ubuntu 18.04"
1781746,2018-10-29 10:54:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781746,2019-01-14 19:45:36 UTC,"What can I do to speed-up inclusion of simple, 3 lines patch from Debian into Ubuntu 18.04 LTS ?"
1781746,2019-01-29 21:30:13 UTC,"While it does appear to be a simple 3 line patch and may apply cleanly the resume hook seems to have been modified heavily and the ephemeral variable does not appear in the rest of the hook, so while it would be set nothing would change with the behavior."
1781746,2019-04-20 18:35:50 UTC,Unsubscribing the sponsors team after Brian's comment.
1781748,2018-07-19 15:21:37 UTC,https://github.com/mixxxdj/mixxx/pull/1753
1781751,2019-03-12 13:18:08 UTC,Upstream doesn't plan to provide an official GUI for TLP.
1781751,2019-01-31 11:30:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781753,2018-07-26 00:09:46 UTC,Up
1781755,2018-07-18 07:21:21 UTC,"OK it works now for me as well, after I removed ~/.widelands dir."
1781755,2019-09-16 08:32:29 UTC,Migrated to https://github.com/widelands/widelands/issues/3292
1781755,2018-07-15 11:23:22 UTC,"Thanks kaputtnik, I will give it a try."
1781755,2018-07-18 06:31:43 UTC,"I have installed widelands now from the official repository, but i can't confirm this bug for archliunx. widelands starts and i can also start a new game."
1781755,2018-07-15 08:34:19 UTC,Don't know if this is related:
1781755,2018-07-15 08:04:37 UTC,Do you know which files are missing?
1781755,2018-07-15 09:11:33 UTC,Found the bug 1760581 related to my previous post. We should apply the fix also to build 19. Don't know how though.
1781775,2018-12-15 05:20:08 UTC,I consider the second approach I gave much better than the first.
1781775,2018-07-15 07:51:36 UTC,"Hi,
Could you check if these are the ports needed:"
1781775,2018-07-15 14:54:15 UTC,I'm attempting to test your proposed settings but I haven't written rules before so it will take me a while to work it out.
1781775,2018-07-15 17:07:08 UTC,"No luck so far. I've tried lots of combinations but it isn't streaming. Even without adding any rules at all, VLC sees ChromeCast under Renderer. It starts to establish a connection but streaming fails."
1781775,2018-07-15 17:16:37 UTC,"But, are you using Gufw?"
1781775,2018-07-15 17:53:04 UTC,"Yes, I was trying to add ""simple"" rules through the GUFW interface. I
probably just need to keep experimenting. I've always relied on the
built-in rules so I've never needed to add one. I'm probably making a
mistakes with:
- multicast entries
- whether to allow in or out or both"
1781775,2018-12-15 05:08:25 UTC,first you need to check the HTTP port that vlc is using (for me it was 8010)...
1781776,2020-07-14 06:07:39 UTC,"Εφόσον δεν υπήρξε λύση από το ΠΣΔ, μάλλον έχει νόημα να προτείνεται πάντα δυναμική IP στους LTSP servers, ακόμα και όταν το σχολείο έχει MikroTik/Cisco."
1781776,2018-08-10 19:08:00 UTC,"Γιάννη μόλις υλοποιηθεί το ζευγάρι των DNS servers, ανάφερέ το εδώ για να κάνουμε νέο release."
1781776,2018-07-23 16:46:57 UTC,"Νομίζω μια καλή λύση θα είναι κατά τη ρύθμιση σύνδεσης δικτύου να προτείνονται ως DNS οι:
127.0.0.1 <dns0> <dns1>
όπου τα dns? τα επιστρέφει το DHCP request,
αν και το 10.x.y.10 που επιστρέφουν οι cisco/mikrotik routers θα πρέπει να αφαιρείται από τη λίστα."
1781776,2018-08-06 10:18:55 UTC,"Πιστεύω ότι μία λύση είναι να ζητήσουμε ένα ζευγάρι DNS servers σε διαφορετικές γεωγραφικές περιοχές που να είναι ""ανοιχτοί"" από όλο το ελληνικό address space.
Έτσι θα έχουμε κάποιους ακόμη DNS servers αν η γνωστή (διαφημιζόμενη στο DNS) τριάδα έχει πρόβλημα και επιπλέον θα δουλεύουν όταν τα σχολεία παραλαμβάνουν CPEs που δεν έχουν οριστεί τα στοιχεία της μονάδας για σύνδεση στο ΠΣΔ (άρα δουλεύουν πχ OTEnet)."
1781779,2018-07-15 12:25:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1781781,2020-01-23 19:01:24 UTC,A fix landed inin cloud-init upstream for this issue @ https://github.com/canonical/cloud-init/commit/6603706eec1c39d9d591c8ffa0ef7171b74d84d6
1781781,2018-07-16 18:31:18 UTC,"So I've checked it out, and ext4 seems to work fine with fallocate. It could perhaps be considered a filesystem-bug as it seems that some xfs-developers are aware of the issue; https://www.spinics.net/lists/linux-mm/msg147100.html But it would be beneficial to have a work-around until that gets sorted."
1781781,2018-07-16 19:04:29 UTC,"Yes, from my reading, this is an xfs (btrfs) specific issue w.r.t how they don't handle converting a fallocated file into swap space."
1781781,2018-11-30 14:32:24 UTC,"The same basic issue is in cloud-init
and had a MP proposed at
 https://code.launchpad.net/~adobrawy/cloud-init/+git/cloud-init/+merge/354680"
1781781,2020-02-20 21:15:00 UTC,"This bug is believed to be fixed in cloud-init in version 20.1. If this is still a problem for you, please make a comment and set the state back to New"
1781782,2018-07-17 19:51:01 UTC,"Michel, I commented on this issue on gitlab.
Can you please run gnome-subtitles from the console and attach the output here?"
1781782,2018-07-18 07:42:36 UTC,"There ist nothing ""special"" to see in console, only this recurring line:"
1781785,2019-09-30 16:08:40 UTC,@racb Okay thanks. Cool to hear that it will be in 19.10. Thank you :-)
1781785,2019-09-30 15:38:08 UTC,"Hey @racb can you tell me the status of this? I was hoping it would be in Ubuntu 19.04, but it seems not to be :-("
1781785,2019-09-30 15:52:41 UTC,@adamretter it's in Eoan (which will probably be 19.10).
1781785,2019-01-02 22:48:19 UTC,Would be great to see this merged in. Passing in the network-config file is working for me with this patch.
1781785,2018-07-16 13:26:07 UTC,"Scott, may I have your opinion on this please?"
1781785,2019-03-25 21:58:44 UTC,"Agree with @eheydrick, I actually don't understand why this has not been merged? Or maybe there is something I've missed in conjunction with cloud-init that I can't catch."
1781789,2018-07-15 12:42:54 UTC,"the snapctl command is excluselive for internal use inside snap hooks in context of packaging.
for interaction from shell you need to use the snap command.
the documentation is correct here, snapctl should be covered in the packaging documentation though."
1781789,2018-07-15 12:54:33 UTC,"Ah, there is also ""snap start kubelet"" which I was supposed to use. My bad."
1781789,2018-07-15 13:10:20 UTC,"I wonder, would it help maybe to make snapctl announce more obviously that it's an internal tool, for people stumbling as clumsily through the snap universe as me? :-D unless that's super obvious to all other beginners that just try to launch a service"
1781789,2018-07-15 13:35:35 UTC,"yeah, that would probably make sense, feel free to adjust bug title and summary accordingly and re-open :)"
1781789,2018-07-15 19:43:15 UTC,"Ok, I updated the ticket in hopefully a useful way!"
1781789,2019-10-08 09:11:29 UTC,"I think that is a sensible suggestion, thanks for pointing this out."
1781790,2018-07-15 13:06:19 UTC,"Right, it seems I shouldn't have been using snapctl, google very misled me today. Sorry :-) I'll leave it open anyway, in case you want to add a man page or more to --help anyway. (if not, feel free to close it)"
1781797,2019-01-29 19:45:38 UTC,"Probably worth testing again, now that libxml2 2.9.9 is released."
1781797,2019-10-05 20:53:49 UTC,I can verify that this bug was fixed sometime between lxml 4.2.5 and lxml 4.4.1.
1781797,2018-07-16 18:30:16 UTC,Thanks for the report. I get this output for libxml2 2.9.8:
1781806,2020-11-19 16:10:25 UTC,"Lots have changed since this bug was opened. Please try to reproduce it with an up to date system and if it still crashes, please provide the info @hmh requested. Thank you."
1781806,2021-01-19 04:17:21 UTC,[Expired for intel-microcode (Ubuntu) because there has been no activity for 60 days.]
1781806,2018-08-30 10:51:52 UTC,"Can you give us the with-old-microcode and with-new-microcode contents of /proc/cpuinfo, please?"
1781808,2018-07-15 16:21:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1781808,2018-10-18 08:41:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781809,2018-08-08 17:26:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781810,2019-07-13 15:29:10 UTC,"This is not actually a bug in Plank, but a problem with BAMF"
1781815,2018-07-15 19:24:03 UTC,So I emailed the maintainer and in the updated version of the package this problem was resolved.
1781819,2018-07-15 22:10:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781819,2018-07-19 19:32:35 UTC,libacsccid1 can replace libacr38u.
1781824,2018-08-02 08:34:08 UTC,I have the same problem - except it's even worse for me - it changes sporadically between the intended path and $HOME. Tested with the following commandline:
1781830,2018-08-09 23:57:09 UTC,fixed in 2.2
1781830,2018-08-02 15:58:48 UTC,https://github.com/mixxxdj/mixxx/pull/1754
1781832,2018-07-15 21:39:55 UTC,"Tested the other font categories, and they crash as well."
1781832,2018-07-19 16:36:06 UTC,I may have filed this in the wrong component: I'm getting a similar-looking crash when I try to change keyboard shortcuts through the default settings tool.
1781832,2018-07-19 16:56:58 UTC,"I think this is the same problem:
https://www.reddit.com/r/Ubuntu/comments/8j6iu5/ubuntu_1804_crashes_when_opening_system_settings/"
1781832,2018-07-19 17:33:42 UTC,Can it be that your dconf database is corrupt or with incorrect file permissions? You may want to test by doing:
1781832,2018-07-21 02:03:26 UTC,"Yup, #4 seems to have fixed it. That narrows the scope of the bug considerably: now I'm reduced to complaining that it crashed, rather than gracefully handling a corrupted database."
1781832,2018-12-12 12:49:57 UTC,That's rather a dconf issue
1781837,2018-07-28 01:44:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781841,2018-07-28 01:59:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781854,2018-12-08 10:03:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781854,2018-12-08 10:20:30 UTC,"It's a problem with the permissions of cdrdao, wodim and growisofs."
1781856,2021-01-27 10:27:00 UTC,"Trent Lloyd (lathiat) wrote on 2018-10-11:

> Obvious fix to me would be to use the default space as the gateway, if it has one, otherwise fall > back to finding a space that has a gateway.
"
1781856,2019-10-31 03:33:27 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1781856,2018-10-11 08:58:18 UTC,"Obvious fix to me would be to use the default space as the gateway, if it has one, otherwise fall back to finding a space that has a gateway."
1781856,2018-10-11 08:57:48 UTC,"For clarity of example, we had a customer who required this. The only fix they had was to manually login to the machines and change the interfaces files after deployment."
1781856,2018-07-17 20:27:09 UTC,"Changing the default gateway seems very much a bandaid solution, as if you
have >1 interface, sort of by definition you want some traffic to go out
one interface for a reason different to other traffic. And changing the
'default' is going to be wrong for some portion of your traffic."
1781856,2018-10-09 10:57:17 UTC,"Since there a workaround, described in comment # 1 and jameinel does not think that this is a good solution to a problem, I am marking this report as Invalid for juju."
1781856,2018-07-16 06:40:24 UTC,Since you linked the bug I created about multi-homing you might know the workarounds already but I will summarize them just in case.
1781856,2018-10-11 08:33:37 UTC,"Anastasia: There is no workaround for LXD containers, there is a workaround for MAAS machines but not the relevant LXD containers. This is very much still an issue for LXD containers, the networking for which is controlled entirely by juju. So I think this Invalid state is incorrect."
1781858,2018-07-16 06:42:48 UTC,"I used the word ""warp"".  Of course, since geeqie is a gtk program, this might may well be grabbing focus (e.g., gtk_widget_grab_focus or gtk_container_get_focus_child)."
1781858,2018-10-21 09:52:51 UTC,"There are two remote commands for <file>:
--remote file:<file>  // bring Geeqie to top
--remote File:<file>  // do not bring Geeqie to top"
1781874,2018-09-17 16:32:33 UTC,"> The return value from process() has always been hard to work out how to use
"
1781874,2018-09-06 00:16:43 UTC,"@MD: We do have some tests for dbNotify in the base-3.16 and 7.0 trees; the tests for the input record types in src/std/rec/test/asynSoftChannel.* check the operation of the soft callback device supports which use dbNotify to do a processGet on the INP link target. Unfortunately though the target record used is a subRecord, which might seem ideal for testing this condition except that its process() routine always returns 0 no matter what the sub returns. Same for the aSub, and for various other record types as well."
1781874,2018-09-05 14:56:04 UTC,"The return of dbProcess() is (and was) being ignored in dbNotify.c (used by CA put w/ callback, but is checked in dbPutField() which is used by CA put w/o callback."
1781874,2018-09-05 14:22:16 UTC,"> If it's >=3.15 then I think I see a problem where the status is being dropped.'
"
1781874,2018-09-05 14:17:13 UTC,"Alas, I'm only able to report against 3.14 at the moment."
1781874,2018-09-05 13:20:24 UTC,To be clear.  Your issue is ECA_NORMAL in the Write Notify case?  This is write_notify_action() vs. write_action() in camessage.c.  Can you say which Base version(s) are involved.  write_notify_action() changed quite a lot from 3.14 -> 3.15.
1781874,2018-09-05 12:36:14 UTC,"No, this is not exactly a duplicate.  In particular, this bug report is actually reporting a deficiency in the CA implementation of the return from Write Notify, whereas #1741844 is reporting a problem with the caput command line tool."
1781874,2018-09-05 14:18:23 UTC,"Sorry, forgot to actually answer your question: yes, I'm reporting that Write Notify returns ECA_NORMAL even though the record processing step has rejected the put (by returning the appropriate error code from the record process function)."
1781877,2018-07-16 15:58:50 UTC,Looks like we just need to upload the ODL releases to the serverstack swift bucket.
1781878,2018-08-09 00:01:31 UTC,We discussed this bug on IRC in #openstack-nova last week [1].
1781878,2019-05-13 08:06:51 UTC,Same case here.
1781878,2019-05-15 20:00:46 UTC,"Hi Cong, thank you for confirming the fix in your case."
1781879,2018-12-06 21:14:53 UTC,"@Kai, that totally fixed me"
1781879,2018-11-12 08:26:53 UTC,"Please see if this Bionic kernel works for you:
https://people.canonical.com/~khfeng/lp1781879/"
1781879,2018-11-11 17:51:32 UTC,Pardon me for being newbie in the linux world. But I have the same issue. I am using Ubuntu 18.04.1 with linux kernel v4.19.1 but still my trackpad doesn't work. The result of xinput is same as the OP has posted.
1781879,2018-11-11 13:54:31 UTC,"Thanks Marc Landolt
I'll following that bug, I hope it will be fix in the future."
1781879,2018-11-11 12:43:47 UTC,"(In reply to Hieu Cao from comment #165)

> Hi everyone.
> Any news here, does the the disconnecting randomly has been fix?
"
1781879,2018-11-11 05:32:49 UTC,"Hi everyone.
Any news here, does the the disconnecting randomly has been fix?"
1781879,2018-11-02 14:58:59 UTC,"(In reply to Marc Landolt from comment #68)

> (In reply to Andy Shevchenko from comment #66)
> > Created attachment 277553 [details]
> > Fix community ordering for H variant
> >
> > Another patch for Cannonlake PCH-H.
>
> Yay, GREAT, Andy you're a Genius, the Touchpad is working :)
>
> After Downloading Kernel 4.18.RC6, patching with
> https://bugzilla.kernel.org/attachment.cgi?id=277507&action=diff and
> https://bugzilla.kernel.org/attachment.cgi?id=277553&action=diff it's
> working.
>
> -Tap to click works
> -2 Finger scroll works (only Natural Scrolling, always on)
> -2 Finger right click works
> -left mouse button works
> -right mouse button does not work but with 2 finger click it works
> -Edge Scrolling does not work
> -it disconects from time to time (rmmod -r hid-multitouch && modprobe
> hid-multitouch helps)
>
> shall I test other patches and do you still need the outputs from Comment 67
> (interrupts, iomem, ranges, pins?
>
> With kind regards and many thanks so far
> Marc Landolt
"
1781879,2018-10-23 16:17:16 UTC,Added kernel-fixed-upstream as it now is with the released 4.19
1781879,2018-10-26 11:02:03 UTC,Any possibility the fix will be backported to Ubuntu 18.04?
1781879,2018-12-09 15:45:45 UTC,"Hi there,"
1781879,2018-10-23 02:49:37 UTC,It's true. Linux kernel v4.19 support touchpad. Also scroll works.
1781879,2018-10-19 15:07:11 UTC,"I have compiled the 4.19-rc8 kernel today (using the mainline kernel package in Arch User Repository) on my HP ZBOOK G5 x360. And I can confirm the touchpad works way smoother (faster) now. This might be because libinput is now recognizing it, but I haven't been able to confirm this yet.
I didn't need any patches, so the touchscreen, pen and touchpad now work out of the box."
1781879,2018-10-19 14:57:56 UTC,"(In reply to janus.reith from comment #160)

> I might be wrong, but it seems like the touchpad cursor speed seems to be
> faster? It already worked before, including multitouch gestures.
"
1781879,2018-10-19 14:43:06 UTC,Touchreen works now!
1781879,2018-10-19 13:59:37 UTC,"(In reply to Hans de Goede from comment #157)

> This sounds like something which we need to fix in the Fedora kernels.
> Benjamin, can you ask the Fedora kernel team to enable this ?
"
1781879,2018-10-19 13:47:50 UTC,"@Benjamin, That seems to be right, the config file includes the comment ""# CONFIG_PINCTRL_CANNONLAKE is not set""."
1781879,2018-10-30 21:32:05 UTC,"Hello,"
1781879,2018-12-11 18:10:48 UTC,While the latest kernels do at least work in some form they aren't quite right.
1781879,2018-12-19 21:11:42 UTC,Hello there! I cannot boot provided kernel because of signature issue. How to sign kernel?
1781879,2018-12-13 18:07:05 UTC,FIX
1781879,2018-10-19 13:33:59 UTC,"(In reply to Benjamin Tissoires from comment #156)

> Janus, IIRC, lat time I checked, CONFIG_PINCTRL_CANNONLAKE was not set in
> the default configuration of Fedora kernels. Can you double check?
>
> If CONFIG_PINCTRL_CANNONLAKE is not set, the device will not show up at all
> in the dmesg.
"
1781879,2019-02-06 21:38:22 UTC,I'm running Ubuntu 18.10 with kernel 4.20.6 and I've got a Asus FX503VD with the same touchpad as other people in this thread. I'm experiencing these problems with libinput:
1781879,2019-01-06 22:19:22 UTC,"(In reply to Hieu Cao from comment #169)

> It worked on v4.20 automatically. Few days ago, but I also uninstalled it
> either. Because the annoyning of disconnecting. I wonder if it fixed the
> disconnecting? I just want to make sure that to reinstall linux again.
>
> (In reply to Andy Shevchenko from comment #168)
> > This bug has been fixed in v4.20.
> Does it fix the disconnecting problem?
"
1781879,2019-01-06 17:43:39 UTC,Does #201 #202 mean the new kernel from Ubuntu archive already fixes the issue?
1781879,2019-01-06 17:32:16 UTC,Perfect is a bit much.  It still doesn't obey the settings for sensitivity but it does at least work most of the time.
1781879,2019-01-06 17:22:06 UTC,Thanks! The new kernel release worked perfectly!
1781879,2019-01-06 16:25:06 UTC,"It worked on v4.20 automatically. Few days ago, but I also uninstalled it either. Because the annoyning of disconnecting. I wonder if it fixed the disconnecting? I just want to make sure that to reinstall linux again."
1781879,2019-01-05 17:47:16 UTC,"Hi all,"
1781879,2019-01-05 13:49:27 UTC,This bug has been fixed in v4.20.
1781879,2018-12-20 08:11:29 UTC,"I'm still not sure, do I need to open a new ticket for issue, or what?"
1781879,2018-12-20 07:53:15 UTC,"It's a different issue. If the the touchpad start working, then the original bug ""GPIO can't be used as IRQ"" is solved."
1781879,2018-12-20 07:42:31 UTC,"Can also confirm that previous message with i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) context, appears independently from settings change, and occurs randomly."
1781879,2018-12-20 07:34:46 UTC,I've also noticed that system constantly reports logs somehow related to touchpad with following context:
1781879,2018-12-20 07:20:10 UTC,"Also can report that right click (context menu) is not working correctly, when clicking with it acts like a left click (selecting items, etc.)"
1781879,2018-12-20 07:12:55 UTC,"I've been able to use touchpad for about 15 minutes. Then, when I turned on two-finger scrolling option in settings touchpad stopped working with following error printed in logs:"
1781879,2019-09-10 08:40:38 UTC,This problem is not completely resolved: touchpad is not full functional after waking from suspend. This has been confirmed by multiple users as reported in #201175.
1781879,2018-12-19 04:30:41 UTC,"Oops, I forgot what commits I backported."
1781879,2018-12-12 19:17:45 UTC,What did you run to get it to work in some fashion ?
1781879,2018-10-19 12:00:39 UTC,"Janus, IIRC, lat time I checked, CONFIG_PINCTRL_CANNONLAKE was not set in the default configuration of Fedora kernels. Can you double check?"
1781879,2018-12-20 02:41:55 UTC,Please disable Secure Boot in the BIOS.
1781879,2018-10-19 08:11:05 UTC,"Hi Janus,"
1781879,2018-06-29 14:34:05 UTC,"Created attachment 277057
dmesg_with gpiolib-acpi_patch"
1781879,2018-06-29 14:13:57 UTC,"Created attachment 277055
Add more debugging to gpiolib-acpi.c"
1781879,2018-06-29 13:32:45 UTC,added pins and gpio-ranges
1781879,2018-06-29 13:32:26 UTC,"Created attachment 277053
gpio-ranges"
1781879,2018-06-29 13:32:09 UTC,"Created attachment 277051
pins"
1781879,2018-06-29 10:01:53 UTC,Can you also attach content of /sys/kernel/debug/pinctrl/INT3450:00/pins and /sys/kernel/debug/pinctrl/INT3450:00/gpio-ranges?
1781879,2018-06-29 06:13:22 UTC,"Created attachment 277029
acpi dump"
1781879,2018-06-24 19:09:15 UTC,"Created attachment 276801
touchpad_hw_id"
1781879,2018-06-24 19:08:56 UTC,"Created attachment 276799
lsusb"
1781879,2018-06-24 19:08:42 UTC,"Created attachment 276797
windows_i2c_inf"
1781879,2018-06-24 19:08:25 UTC,"Created attachment 276795
windows_gpio2_inf"
1781879,2018-06-24 19:07:56 UTC,"Created attachment 276793
i2c_hw_id"
1781879,2018-06-24 19:07:28 UTC,"Created attachment 276791
i2cdetect"
1781879,2018-06-24 19:07:05 UTC,"Created attachment 276789
dmesg"
1781879,2018-06-24 18:57:54 UTC,"Investigation done by alkersan
-----------------------------------"
1781879,2018-06-24 18:56:55 UTC,"Created attachment 276785
Files collected during investigation"
1781879,2018-06-03 17:46:08 UTC,Razer Blade 15 2018 touchpad support [1532:0233]
1781879,2018-06-29 16:12:37 UTC,pin = 100
1781879,2018-07-02 23:12:17 UTC,"This pin is configured by BIOS as GPIO direct interrupt to IOAPIC (SCI mode).
So, there is coupled GpioInt() and Interrupt() resources. If I read DSDT correctly the IRQ resource, which must be used, depends on the setting of some internal variable. My understanding that, since the pin is configured to generate SCI, the driver should respect BIOS settings."
1781879,2018-10-19 11:00:35 UTC,"dmesg | grep -i ""GPIO"" does not return anything, neither does dmesg --level=err
I guess my issue is not directly related then."
1781879,2018-07-03 01:45:41 UTC,Take the bug as it seems to be related to our GPIO/pinctrl driver.
1781879,2018-07-03 01:44:45 UTC,"Okay, more investigation on the message ""flag is output"". It seems that in the driver we missed the fact of IRQ to pin translation in one case. That's why we are actually talking to hadrware pin 100 (ACPI 129) instead of pin 79 (ACPI 100). And that pin is indeed configured as output."
1781879,2018-10-15 11:09:15 UTC,"Can confirm that on linux v4.19.0-041900rc7 touchpad is working (doesn't sure if anything is supported) in terms of basic operations (clicks, cursor, etc.)"
1781879,2018-10-14 20:27:50 UTC,"My Asus FX504 laptop is also affected by the issue, I'm on Ubuntu 18.04.1 (kernel 4.15), tried kernel 4.18, nothing changes, still doesn't work"
1781879,2018-10-11 01:48:51 UTC,Yes I am also facing the same issue.
1781879,2018-09-22 13:00:10 UTC,"The error happens at here:
[    4.224268] cannonlake-pinctrl INT3450:00: pin 225 cannot be used as IRQ
[    4.224277] genirq: Setting trigger mode 8 for irq 128 failed (intel_gpio_irq_type+0x0/0x140 [pinctrl_intel])
[    4.224422] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
[    4.224436] i2c_hid i2c-ELAN1200:00: Linked as a consumer to regulator.0
[    4.224438] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vddl not found, using dummy regulator"
1781879,2018-09-11 12:47:36 UTC,I have the same model and got the same problem. Did you fix?
1781879,2018-09-01 14:36:59 UTC,"TUF-GAMING-FX504GD-FX80GD:~$ dmesg
[    0.000000] microcode: microcode updated early to revision 0x96, date = 2018-05-02
[    0.000000] Linux version 4.19.0-041900rc1-generic (kernel@kathleen) (gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1)) #201808262231 SMP Sun Aug 26 22:33:11 UTC 2018
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc1-generic root=UUID=7960da4f-2b4c-4e1a-b8d7-d8eb005249aa ro nouveau.modeset=0 i8042.nomux=1 i8042.reset i8042.kbdreset=1 quiet splash vt.handoff=1
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[    0.000000] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[    0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000079049fff] usable
[    0.000000] BIOS-e820: [mem 0x000000007904a000-0x000000007a4e0fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000007a4e1000-0x000000007a55dfff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000007a55e000-0x000000007a649fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000007a64a000-0x000000007ac40fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000007ac41000-0x000000007ad0dfff] type 20
[    0.000000] BIOS-e820: [mem 0x000000007ad0e000-0x000000007ad0efff] usable
[    0.000000] BIOS-e820: [mem 0x000000007ad0f000-0x000000007fffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000027dffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: EFI v2.60 by American Megatrends
[    0.000000] efi:  ACPI 2.0=0x7a4fa000  ACPI=0x7a4fa000  SMBIOS=0x7aa89000  SMBIOS 3.0=0x7aa88000  ESRT=0x75e26d18  MEMATTR=0x75868018
[    0.000000] SMBIOS 3.1.1 present.
[    0.000000] DMI: ASUSTeK COMPUTER INC. TUF GAMING FX504GD_FX80GD/FX504GD, BIOS FX504GD.312 07/13/2018
[    0.000000] tsc: Detected 2300.000 MHz processor
[    0.000687] tsc: Detected 2304.000 M..."
1781879,2018-08-31 06:35:11 UTC,Please attach dmesg under linux kernel v4.19-rc1.
1781879,2018-10-18 19:17:28 UTC,Accordingly to comments 144-147 I compiled the kernel from v4.19-rc5 branch and applied the two patches that were attached by Mika 2018-09-25.
1781879,2018-08-27 18:20:07 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1781879,2018-08-23 11:30:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1781879,2018-08-23 11:29:59 UTC,I am also facing the same problem on the same model. I have tried everything I could find on the Internet. If anyone has a solution please post.
1781879,2018-07-04 00:27:17 UTC,The error code is different this time though -
1781879,2018-07-04 00:07:15 UTC,the touchpad is still not functional I have attached the dmesg after the change.
1781879,2018-07-04 00:02:32 UTC,"Created attachment 277159
dmesg with overriding pin 100 with 79"
1781879,2018-07-03 23:50:25 UTC,"(In reply to jamir from comment #21)

> Let me know if you need me to try out anything.
"
1781879,2018-07-03 01:59:53 UTC,Let me know if you need me to try out anything.
1781879,2018-08-27 18:40:04 UTC,kernel-bug-exists-upstream
1781880,2018-10-08 21:50:51 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1781880,2018-10-08 21:45:36 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1781880,2018-10-08 20:53:44 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1781880,2018-10-04 22:05:54 UTC,"Reviewed:  https://review.openstack.org/592337
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9ea6939db92662f4978866e9d48c43e67568922
Submitter: Zuul
Branch:    stable/pike"
1781880,2018-09-25 08:55:45 UTC,"Reviewed:  https://review.openstack.org/592311
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3b17251da6e06260ee4b499dd18b46cc95f97fe5
Submitter: Zuul
Branch:    stable/queens"
1781880,2018-09-22 19:57:13 UTC,"Reviewed:  https://review.openstack.org/592310
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=161d38679fec13bdb10e89536f7e0db43176396f
Submitter: Zuul
Branch:    stable/rocky"
1781880,2018-08-16 10:14:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/592337"
1781880,2018-07-19 11:50:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583936"
1781880,2018-08-16 08:01:42 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/592310"
1781880,2018-08-16 00:51:25 UTC,"Reviewed:  https://review.openstack.org/583936
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0f4e5c442c0ab446274979dafda873c1e1c20585
Submitter: Zuul
Branch:    master"
1781880,2018-08-08 13:14:09 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/583927
Reason: This type of functional test won't work with the oslo_cache.dict since the cache will be a dict member variable of the server group API driver, and there are different server group API instances between the compute service and the API."
1781880,2018-07-19 10:57:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/583927"
1781880,2018-07-19 01:17:31 UTC,It should be pretty easy to recreate this in a test which uses the MC driver and something like the oslo_cache.dict or some dogpile.cache.null backend.
1781880,2018-07-17 16:49:31 UTC,"Looks like the correct analysis of the bug. We don't test the MC server group driver or enable_new_services config option very well, or together (obviously)."
1781880,2019-03-22 03:48:40 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1781880,2018-08-16 08:02:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/592311"
1781882,2019-05-13 23:15:23 UTC,"Niels,"
1781882,2019-07-13 04:18:15 UTC,[Expired for OpenStack rabbitmq-server charm because there has been no activity for 60 days.]
1781882,2018-07-16 09:37:26 UTC,"Additionally, last time the debug-hooks trick didn't work until I restarted the rabbitmq-server using `service rabbitmq-server restart`."
1781882,2018-07-20 13:21:37 UTC,"In fact, I found this bug only occurs when the option management_plugin is set to true, when set to default/false the charm installs flawlessly. Also unsetting the option through `juju config rabbitmq-server --reset management_plugin` and then running `juju resolved rabbitmq-server/0` reverts to a working environment when already in error state."
1781889,2018-07-16 09:36:03 UTC,"This also happens on the live cd, and in Ubuntu 18.04 too."
1781889,2018-07-16 10:00:09 UTC,This change was made by a bot.
1781889,2018-07-17 19:17:56 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1781889,2018-07-18 12:11:21 UTC,"Marked as requested, as it also happens with the latest upstream kernel."
1781889,2018-07-25 09:34:22 UTC,"Forgot to add: the system reboots/shutsdown fine when running in 'single' mode, i.e.: without switching to graphics mode first."
1781889,2018-07-26 15:50:19 UTC,"Based on my comment #6, could this be related to #1782347 in any way, as this only happens when graphics is involved?
Please note however that #1782347 is about Ubuntu only, while this bug is about both Ubuntu and XUbuntu."
1781895,2018-08-27 07:00:56 UTC,This bug was fixed in the package linux-oem - 4.15.0-1017.20
1781895,2018-08-24 03:08:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1781895,2018-07-17 19:24:12 UTC,"SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-July/093876.html"
1781895,2018-07-16 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1781902,2020-07-24 21:50:22 UTC,"We no longer test with the A1 Instances due to problems like this, A1 is an extremely minimal, low resource instance. We should not be offlining cpu and memory in these VMs."
1781904,2018-12-21 13:27:16 UTC,"Linux Mint 19.1 Cinnamon
Installed the Linux Kernel HWE-18.04 stuff.
Now running 4.18.0-13-generic"
1781904,2018-07-17 19:10:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1781904,2018-07-16 12:52:33 UTC,apport information
1781904,2018-07-16 12:52:32 UTC,apport information
1781904,2018-07-16 12:52:31 UTC,apport information
1781904,2018-07-16 12:52:30 UTC,apport information
1781904,2018-07-16 12:52:28 UTC,apport information
1781904,2018-07-20 19:36:30 UTC,"Fixed in 4.18-rc5
It never worked before."
1781904,2018-07-16 12:52:25 UTC,apport information
1781904,2018-07-16 12:52:23 UTC,apport information
1781904,2018-07-16 12:52:22 UTC,apport information
1781904,2018-07-16 12:52:21 UTC,apport information
1781904,2018-07-16 12:52:20 UTC,apport information
1781904,2018-07-16 12:52:19 UTC,apport information
1781904,2018-07-16 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1781904,2018-07-16 12:52:26 UTC,apport information
1781904,2018-07-16 12:52:29 UTC,apport information
1781905,2018-07-16 11:07:39 UTC,"+ /opt/loci/scripts/pip_install.sh cryptography pymysql python-memcached uwsgi
+ packages='cryptography pymysql python-memcached uwsgi'
+ pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ cryptography pymysql python-memcached uwsgi
Ignoring asyncio: markers 'python_version == ""3.4""' don't match your environment
Ignoring asyncio: markers 'python_version == ""3.5""' don't match your environment
Ignoring dnspython3: markers 'python_version == ""3.4""' don't match your environment
Ignoring dnspython3: markers 'python_version == ""3.5""' don't match your environment
Ignoring mypy: markers 'python_version == ""3.4""' don't match your environment
Ignoring mypy: markers 'python_version == ""3.5""' don't match your environment
Ignoring jeepney: markers 'python_version == ""3.4""' don't match your environment
Ignoring jeepney: markers 'python_version == ""3.5""' don't match your environment
Ignoring SecretStorage: markers 'python_version == ""3.4""' don't match your environment
Ignoring SecretStorage: markers 'python_version == ""3.5""' don't match your environment
Ignoring Django: markers 'python_version == ""3.4""' don't match your environment
Ignoring Django: markers 'python_version == ""3.5""' don't match your environment
Ignoring cmd2: markers 'python_version == ""3.4""' don't match your environment
Ignoring cmd2: markers 'python_version == ""3.5""' don't match your environment
Ignoring typed-ast: markers 'python_version == ""3.4""' don't match your environment
Ignoring typed-ast: markers 'python_version == ""3.5""' don't match your environment
Ignoring pyldap: markers 'python_version == ""3.4""' don't match your environment
Ignoring pyldap: markers 'python_version == ""3.5""' don't match your environment
Looking in links: /tmp/wheels/
Collecting cryptography===2.2.2 (from -c /tmp/wheels/upper-constraints.txt (line 162))
  Could not find a version that satisfies the requirement cryptography===2.2.2 (from -c /tmp/wheels/upper-constraints.txt (line 162)) (from versions: )
No matching distribution found for cryptography===2.2.2 (from -c /tmp/wheels/upper-constraints.txt (line 162))
The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1"
1781917,2020-05-09 08:41:22 UTC,Adding a link to an external issue mentioning this: https://github.com/tmatilai/vagrant-proxyconf/issues/171#issuecomment-626098580
1781918,2018-07-17 07:39:04 UTC,"hi hongbin (hongbin034)：
Thanks,my zun branch two nodes are different"
1781918,2018-07-18 02:25:58 UTC,It looks you need to execute the steps to configure rootwrap: https://github.com/openstack/zun/commit/77a9b57dd3cb1ffd02f6756a40d3feec1500fb9f#diff-18e838b80e6dd8e3e5cbe39d6836d616
1781918,2018-07-17 11:50:01 UTC,"hi @hongbin,
    controller and conmpute01  zun version really inconsistent.
    controller Master
    conmpute01 stable/queens"
1781918,2018-07-17 02:31:25 UTC,"In particular, could you give me the following information."
1781918,2018-07-16 13:32:18 UTC,"compute01 install doc:
https://docs.openstack.org/zun/queens/install/compute-install-ubuntu.html#install-and-configure-components"
1781918,2018-07-17 02:28:14 UTC,"Hi @men,"
1781919,2018-07-16 13:54:54 UTC,i see the same issue on UbuntuCore installs. It does not seem to cause any actual issues there though
1781919,2018-07-16 14:32:58 UTC,This is currently blocking automatic publication of cosmic daily cloud images. The automated tests check for a 'degraded boot' which this bug will cause.
1781919,2018-07-16 15:12:18 UTC,I had a look at our packaging for snapd and we explicitly remove snapd.apparmor.service and the corresponding executable. This feels like a bug in cosmic packaging.
1781919,2018-07-19 11:27:32 UTC,Our tests are passing again with snapd version 2.34.1+18.10.
1781919,2018-07-21 18:31:40 UTC,I'm still having a problem updating. I get the following message on screen with the latest version of snapd:
1781919,2018-07-21 18:45:13 UTC,Additional info:
1781919,2018-07-21 21:11:21 UTC,"@cariboo
this bug is about snapd.apparmor.service and snapd-apparmor, please file a new one..."
1781921,2019-02-06 04:33:10 UTC,"The linked branch fixes the crash but still makes the check fail when there are no peers. This is problematic in some use cases, e.g. where mojo is deploying base infrastructure like squid first, verifying it's all working, then relating app services, meaning that during the first verify there are legitimately no peers."
1781923,2019-06-04 03:35:15 UTC,"Variable font support is mostly there for Inkscape 1.0, so marking this as 'fix committed'."
1781923,2018-07-16 16:31:50 UTC,"Have a look at: https://www.patreon.com/posts/font-variations-17644963
GUI support has been added to trunk. A series of sliders to set axes will appear in the Text and Font dialog when a font with variations is selected."
1781923,2018-07-16 15:25:31 UTC,"As a matter of fact Tavmjong is already working on support for font variations, see [1] for some details."
1781928,2020-07-23 02:49:36 UTC,"Fixed in version mutagen/1.44.0-1
https://salsa.debian.org/python-team/modules/mutagen/-/commit/9da138a63ddb59ccb9e36e35117a84eecd062104"
1781971,2018-08-03 20:31:11 UTC,"Solved the local build problem, now just kicking around the nginx-daemon package (this is a **temporary** naming, it probably will become nginx-core-daemon in the future) to get rid of its dependency on nginx-common, and then making sure installations work as-expected."
1781971,2019-01-09 19:07:01 UTC,"As there has been no testing or suggestions of this or push to further pursue this, I am marking this as Incomplete for expiration in 60 days; if there is more of a need for this, please update the bug, as this is at this point a stale bug that isn't really moving anywhere."
1781971,2018-08-15 17:55:56 UTC,"Added Bionic series to the task at the request of Andres Rodriguez (via IRC, and asking if this could eventually be an SRU'd item)"
1781971,2018-08-07 19:41:04 UTC,Test-worthy packages now exist at https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1781971
1781971,2018-08-06 18:21:31 UTC,"Digging deeper, we'll have to strip the dynamic modules out, there's no way to provide them without including nginx-common because of the way they install as the package, so this will remove the dynamic modules which include the following feature sets:"
1781971,2018-08-03 20:31:36 UTC,Note there's some changes in progress; I'll let you know when packages are stabilized and ready for full testing.
1781971,2019-03-11 04:17:26 UTC,[Expired for nginx (Ubuntu Bionic) because there has been no activity for 60 days.]
1781971,2018-07-17 18:47:25 UTC,"In discussion with Andres, this would only impact the 'core' flavor of NGINX.  It would not be scoped to include any other packages other than the Main-included ones."
1781971,2018-07-17 17:16:58 UTC,"And as an aside, I don't have any influence in how Debian changes the packages - if this proposal is made in Debian for their nginx-{light,full,extras} flavors it can be extended to include our flavors, but we'll have to do some decision making, *and* we need to allow a method to migrate existing nginx-core users to nginx-newname (where newname is the 'new' name for the Core Flavor we established back in 14.04).  Otherwise, upgrades in-place between OS versions are very likely to explode/break."
1781971,2018-07-17 11:46:39 UTC,"I'll let Thomas Ward (@teward) chime in, but to me this looks like a wishlist item at the moment."
1781971,2018-07-17 11:47:28 UTC,MySQL uses the following pattern to achieve this use case:
1781971,2018-07-26 19:54:26 UTC,"I'm working on this, though the initial attempts on splitting this have failed to build properly locally.  Looking into that, then going to put this up to a PPA so we can do some testing on this (without having to dpkg -i all the packages manually)"
1781971,2018-07-17 15:00:57 UTC,"Hi Thomas,"
1781971,2018-07-17 17:09:50 UTC,"Andres,"
1781971,2018-07-17 12:16:50 UTC,To follow this suggestion would be problematic.
1781973,2018-07-17 15:03:16 UTC,Please attach diagnostic snapshot.
1781974,2020-01-25 12:15:09 UTC,"Not reproducible in master, probably fixed by https://gitlab.com/inkscape/inkscape/merge_requests/996."
1781983,2020-11-17 18:19:23 UTC,"Change abandoned by Brent Eagles (<email address hidden>) on branch: master
Review: https://review.opendev.org/582989
Reason: The last code update on this was 2018-09-21 so I'm guessing this isn't a priority."
1781987,2018-07-16 16:32:31 UTC,Here is a copy of a working /boot/grub/grub.cfg file that fixed a problem.
1781987,2018-07-17 16:25:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1781991,2019-06-27 10:45:51 UTC,"The verification of the Stable Release Update for sssd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1781991,2019-06-27 10:45:37 UTC,This bug was fixed in the package sssd - 1.13.4-1ubuntu1.15
1781991,2019-06-21 17:23:15 UTC,Xenial verification
1781991,2019-06-21 14:56:04 UTC,Bionic verification
1781991,2019-06-20 08:09:34 UTC,"Hello Robie, or anyone else affected,"
1781991,2019-06-20 08:08:02 UTC,"Hello Robie, or anyone else affected,"
1781991,2019-05-28 13:35:31 UTC,https://salsa.debian.org/sssd-team/sssd/commit/9d3189a1730672e532773f41cdb55c367b62bbaf direct link to the debian fix
1781991,2018-11-28 14:44:35 UTC,"Are you saying that you've checked and can confirm that 16.04 and 18.04 are affected? If so, please could you confirm the package versions of sssd in which you have verified that the bug is present?"
1781991,2019-05-28 13:11:13 UTC,"This is the fix from debian:
diff --git a/debian/libsss-sudo.postinst b/debian/libsss-sudo.postinst
index a9c061ede..272e68f1e 100644
--- a/debian/libsss-sudo.postinst
+++ b/debian/libsss-sudo.postinst
@@ -33,7 +33,8 @@ insert_nss_entry() {
     fi
 }"
1781991,2018-12-05 18:36:29 UTC,I can confirm that 16.04 and 18.04 are also affected:
1781991,2019-06-27 16:12:20 UTC,This bug was fixed in the package sssd - 1.16.1-1ubuntu1.3
1781991,2018-11-28 14:12:31 UTC,"There is currently only a fix for 18.10.
How about 16.04 and 18.04?"
1781991,2018-08-27 11:01:51 UTC,Landed in cosmic.
1781991,2018-08-22 18:55:47 UTC,"This is fixed in debian's 1.16.3-1, which I will try to update in cosmic in time for feature freeze."
1781991,2018-07-16 17:06:27 UTC,Debian bug link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903917
1781991,2019-05-28 13:12:08 UTC,Fixed in cosmic and later.
1782003,2018-10-10 08:14:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782003,2018-10-09 09:32:44 UTC,"Same problem. With the ""Auto-hide"" dock, moving a non-maximum window to left edge of screen the dock hide. At this time, once you click background of desktop (all window lost focus) and moving mouse cursor to left edge will NOT unhide the dock. The cursor must leave left edge and move to it again, the dock will unhide."
1782004,2019-03-22 12:40:27 UTC,"This bug is about progress visibility to the user/operator.  We should discuss with the team, what other checkpoints along the way are meaningful enough to send up as a status update."
1782004,2019-03-22 13:34:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/645572"
1782004,2019-04-04 16:27:28 UTC,"After speaking to Drew, the real request here is that Juju should keep track of outstanding hooks to process for each unit and display that information as part of juju status. This would help minimise the responsibility of every charm (like the keystone charm in this bug) having to set its status."
1782004,2019-04-09 16:23:51 UTC,I started a new topic on https://discourse.jujucharms.com/t/pending-hooks-counter-and-way-to-introspect-it-in-juju-status/1346
1782004,2019-04-17 20:45:30 UTC,My latest patch set #5 (https://review.openstack.org/#/c/645572/5) adds some generic status and log updates to the charm such as:
1782004,2019-04-18 15:24:03 UTC,@Drew: I filed another bug (Certain functions run more than once when upgrading the keystone charm) which might help reduce the time it takes to run the upgrade-charm for keystone:
1782004,2019-04-25 15:54:18 UTC,"Reviewed:  https://review.opendev.org/645572
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=f01c34d7c8c8d7abc8a85eaa88d74618fc06a318
Submitter: Zuul
Branch:    master"
1782007,2018-07-20 00:56:30 UTC,When a new machine is BMC enlisted the machine boots without OAUTH credentials. Everything cloud-init interacts with is over the anonymous API handlers. The anonymous handler doesn't log cloud-init messages because it doesn't know what machine the messages are related to.
1782007,2019-09-19 11:58:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1782009,2018-08-10 00:17:58 UTC,"This would be an upgrade error. The issue is that the rack controller is
using a newer version of code than the region controller."
1782009,2018-10-09 21:28:45 UTC,The solution for this is to show a proper error implying/asserting that the versions mismatch and they need to upgrade.
1782009,2019-09-19 14:47:24 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1782014,2019-05-03 22:59:07 UTC,"Thanks for this fix, Remington!  I've added it to master, rel_3_1, rel_3_2, and rel_3_3."
1782014,2019-04-10 21:25:13 UTC,Here's a branch with a simple fix:
1782014,2019-04-09 22:28:53 UTC,Still an issue in 3.3 beta.
1782014,2018-09-07 17:46:45 UTC,Realized I filed a duplicate bug.  Copying over my comments:
1782021,2018-07-17 07:09:14 UTC,Already reported in Bug #1558942.
1782021,2018-07-17 08:28:31 UTC,"In #1558942, the report says the problem exists when ""grab sensitivity is 0"", which I assume means click/drag threshold is set to 0. I can't replicate that, so I don't think it's the same bug. In this bug the grab sensitivity value does indeed affect which object is grabbed (and it shouldn't). I recommend continuing with this bug, since it's for the most recent version of Inkscape, and may also solve the previous problem."
1782021,2018-07-17 08:33:47 UTC,"Ah, actually, grab sensitivity is a different value."
1782021,2018-07-17 08:38:20 UTC,"Bug #1558942 is a duplicate of #1066474
I'll link to #1066474 in the 1.0 bugfix list.
Thanks again, LucaDC!"
1782021,2020-03-28 16:14:24 UTC,Closing because INVALID: Duplicate issue.
1782023,2019-04-17 06:01:53 UTC,"Hello,
do you still have this issue with latest 4.15 HWE kernel?
Thanks"
1782023,2019-06-17 04:17:23 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1782024,2020-03-29 13:58:30 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1782024,2020-03-29 21:26:46 UTC,"Thanks!
-C"
1782027,2019-09-13 20:03:41 UTC,Confirmed in 3.2.3. The web staff client requires that you also take the action to Suspend Hold.
1782027,2019-08-29 18:10:53 UTC,"We have just updated to 3.3.3. Editing the Activation date still does not suspend the hold. I have found if I select Suspend, and enter an activation date, while I am placing a hold, the hold suspends, but does not automatically reactivate on the set day, as it should. The hold remains suspended until manually activated."
1782027,2019-09-13 20:05:30 UTC,"Oops, commented on wrong bug."
1782027,2018-07-17 22:12:11 UTC,"""Is it possible the clerk is trying to verify the change was made by
selecting Edit Hold Dates again and, seeing that the date hasn't changed,
believes it hasn't updated?"""
1782027,2018-07-17 20:11:48 UTC,Trying to confirm in both 3.0.8 and in current master.
1782027,2018-07-16 22:34:55 UTC,"Hi Ron,"
1782027,2018-07-17 21:56:56 UTC,I was also able to set the activation date following the steps described by Garry.
1782027,2018-07-17 18:17:04 UTC,"There is no error message; it just doesn't suspend the hold.  The clerk read through this email, and confirmed that she is entering the date in the correct format."
1782035,2018-08-17 19:04:48 UTC,Enlistment matches a machine with an existing node when the MAC address is missing or incorrect is via the BMC IP address. Enlistment gets the BMC IP address when it sets the BMC credentials. While we could modify maas-ipmi-autodetect to only return the BMC IP address if the machine is being commissioned and the user wants the maas BMC user to be created we have no way to tell enlistment to do that. The way we made the maas BMC user conditional for commissioning is by using a template which is generated on the region.
1782055,2019-02-15 19:53:00 UTC,"I installed zun with kuryr and etcd via kolla-ansible queens.
It seems to work fine but the cloud-shell-addin for horizon does not work. Everytime someone trys to launch it, it trys to start another container and fails with ""network is ambigious""."
1782055,2019-02-16 04:01:29 UTC,"@Shu,"
1782055,2019-02-16 08:27:30 UTC,"@Hongbin,"
1782055,2019-02-16 16:14:43 UTC,"@Shu,"
1782070,2018-07-19 15:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782070,2018-08-24 03:08:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1782070,2018-08-27 07:00:56 UTC,This bug was fixed in the package linux-oem - 4.15.0-1017.20
1782075,2018-11-05 11:30:05 UTC,"Steps to reproduce by providing invalid URL [valid URL with HTTPS option]:
1) Task API from PostMan :"
1782075,2018-11-05 11:35:24 UTC,Error in Glance API Logs :
1782075,2018-11-02 06:23:58 UTC,"Could you please add exact steps, commands to reproduce this issue.
Thank you."
1782079,2018-07-17 16:25:45 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1782081,2018-07-18 15:58:53 UTC,"Hi Eric,"
1782081,2018-07-24 16:01:42 UTC,"Hi Eric,"
1782081,2018-11-10 19:38:46 UTC,Valentin can you check the status with Stephan?
1782083,2018-07-17 08:01:10 UTC,"Update: that worked to get my project to show up as an USB device again. (all the innards have now been removed in an attempt to rule things out, so now back to re-inserting the innards of my project)."
1782083,2018-08-02 08:09:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782083,2018-08-02 08:16:20 UTC,I got the same issue for a professional project with Bionic package. Compile is fine but program crashes on the target.
1782083,2018-08-19 13:18:56 UTC,I decided to try to trace this down to the source line that compiles differently between the two distributions causing the difference in behavior.....
1782083,2018-08-19 14:34:29 UTC,"Update;
No confirmation yet. Heisenbug: I managed to get the bug to disappear (the executable works normally) when I run it attached to the debugger. Sigh."
1782101,2018-07-17 09:25:10 UTC,Are you usually using Unity7 or Gnome Shell when the problem occurs?
1782101,2018-07-17 09:36:09 UTC,I use Unity without switches to Gnome Shell
1782101,2018-07-17 09:46:56 UTC,I tried to log gnome session (it's named Ubuntu) and I couldn't reproduce the issue. If lock computer I got completely different login page. There is no switch to the password input field if I move mouse pointer to the second screen. The password input field is fixed to the main screen.
1782101,2018-07-18 01:59:36 UTC,"I see now, thanks."
1782107,2018-07-17 09:47:26 UTC,"The ioctl warnings are I think for BTRFS_IOC_CLONE, which are probably harmless (the calling program ought to cope with it not working and fall back to something else)."
1782107,2018-07-17 12:07:45 UTC,Thank you for the quick reply.
1782107,2020-11-12 15:38:00 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1782107,2021-01-12 04:17:31 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1782110,2018-07-17 21:05:46 UTC,"Em dashes cannot be part of a snap name.
They _could_ be part of an intentional 'snap set' command, something like
   snap set mysnap foo=—o—
in which case, if the ""snap set"" fails, the user will get the above message, followed by whatever error. Like so:"
1782110,2018-07-17 20:48:48 UTC,"On Tue, Jul 17, 2018 at 02:39:22PM -0000, John Lenton wrote:

> $ snap install ––help
> Your command included some characters that look like dashes but are not:
>     ""snap install \u2013\u2013help""
"
1782110,2018-07-17 14:39:22 UTC,For reference:
1782110,2018-07-17 14:18:39 UTC,"I've added code to check for typographical dashes and warn the user:
https://github.com/snapcore/snapd/pull/5524"
1782110,2018-07-17 11:46:50 UTC,"Here is the list of all snap install commands, it was 58/60 which failed with that error"
1782110,2018-07-17 11:29:44 UTC,There's something very strange going on.
1782110,2018-07-17 11:51:05 UTC,Yep! reproduced it:
1782112,2018-07-17 10:36:38 UTC,This is largely due to assertion fetching. We have some plans to batch those but it has not been a priority yet as most devices don't have such a large number of snaps installed nor is a full refresh usually done interactively.
1782112,2019-08-23 18:23:40 UTC,"This is still quite a problem. I was giving a demo to a customer today, and it's quite embarrassing to have everyone staring at the projector display waiting for ""snap refresh (snapname)"" from inside a corporate network with a super fast Internet connection."
1782112,2020-08-11 10:01:12 UTC,Bulk assert refreshes are in progress (close to become available) in snapd.
1782115,2018-07-17 10:32:56 UTC,Screenshot of what the bug looks like when it happens
1782115,2020-04-07 08:30:40 UTC,Closing because INVALID: Issue migrated.
1782117,2018-07-17 11:20:14 UTC,"This is the spected behabiour, the clip is clipong the group, if the group is destroyed... anyway there is some cliping options in prefs but I hope is more relating to uncliping than a element destroy."
1782117,2018-07-17 11:21:19 UTC,Also happends in previous inkscape versions
1782117,2020-03-28 16:50:35 UTC,Closing because INVALID: Duplicate issue.
1782135,2018-07-20 18:43:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782137,2018-07-20 10:53:08 UTC,"Hi Norbert,"
1782137,2019-02-04 20:11:54 UTC,"This happened today again - https://askubuntu.com/q/1115538/66509 .
Consider to fix your uninstallation process."
1782137,2018-10-05 04:29:16 UTC,"Yes, I agree with Norbert.
Should respect Package manager.
Uninstall option."
1782137,2018-07-17 17:56:01 UTC,"If anyone bought or downloaded Linux Mint 19 it will not work because grub
is missing from the program.  The error message says grub missing, will not
boot.  If you are having trouble with 19 booting return it, it won't boot."
1782137,2018-07-17 18:20:10 UTC,"@Joseph Florio (joeinslw)
for whom you wrote your clever comment?"
1782139,2018-07-17 12:42:02 UTC,"> ""The --templates paths decoupling logic must be productized""
"
1782139,2018-07-17 12:45:45 UTC,"https://bugs.launchpad.net/tripleo/+bug/1781227 appears to be either a packaging or CI issue, I'm still not clear how the tripleoclient patch helps, except that we can ""trick"" the client into using a single --templates command to switch between actually two different paths - this is really opaque to the operator and inconsistent with how --templates has worked for many releases."
1782139,2018-07-17 13:49:24 UTC,"I think the detail added shows that primarily we need a way to co-install multiple versions of the templates (and probably images), there is the openstack-tripleo-heat-templates-compat RPM which was supposed to help with that, but I don't think it's well tested at this point, perhaps we can address that by starting to use it for upgrade CI?"
1782139,2018-07-17 13:52:29 UTC,"Separate from the mixed version requirement, there's been discussion around operator workflow that copies the packaged t-h-t to a git controlled directory, and whether we could automate some of that workflow (which doesn't directly solve the co-install problems but could be used as a way to jump between versions of RPM if we tagged e.g each version as a different release or branch)"
1782139,2018-09-11 13:41:42 UTC,"Not much to add to the discussion here, just wondering about the git deployment details. It may be interesting to have a look at dulwich with the swift backend: https://github.com/dulwich/dulwich/blob/master/README.swift.md"
1782139,2018-11-05 13:17:48 UTC,"Another case for t-h-t versioning is Edge clouds, when single undercloud should install and Day-2 manage multiple overclouds from different tht paths"
1782139,2021-02-18 16:46:28 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1782155,2018-07-17 13:58:12 UTC,"I tried adding 'accept-ra: no' to the YAML, and tried the workaround in bug #1736975 (manually creating a .network file in /etc/systemd/network) and neither prevented the stall. However, after two minutes, networkd gives up and allows the system to continue booting - and the bridge exists."
1782155,2018-07-17 14:51:19 UTC,"The bridge does not yet have any interfaces attached to it, so it has 'no-carrier';  it's not marked as optional so networkd-wait-online  will block."
1782155,2018-07-17 15:17:45 UTC,"For the record, I'm now working around this issue by having LXD manage the bridge. Since I didn't want DHCP, I configured it in LXD with `ipv4.dhcp=false`."
1782169,2020-03-28 15:15:16 UTC,"Closing because INVALID: Fix released, DPI Option exists since (at least) v0.92.4."
1782169,2018-07-17 21:50:35 UTC,gCR the option of DPI is on preferences and is a Global value because the question I comment previously. Currently you couldent attach a DPI to a SVG in other way.
1782169,2018-07-17 15:06:01 UTC,"Hi CR, thanks for fill the bug."
1782169,2018-07-17 20:36:56 UTC,"Hi Jabier! I tried to import, and I do get a dialogue, but there is no dpi option, and linking the file as an image just makes it a bitmap."
1782177,2018-11-14 08:31:58 UTC,"(In reply to Jani Nikula from comment #4)

> We do have a check in place to crank the brightness to max if it's at the
> minimum upon encoder enable. However, that bit policy has been in place for
> ages.
"
1782177,2018-11-14 14:08:20 UTC,"I really can't think of any reason why this behaviour would have changed for you because of a kernel change. For 10 years now, since the introduction of i915 KMS support, we've had code in place to set the backlight to max if it's at 0 on panel enable. (In retrospect, that was not such a good policy decision, but I fear it's pretty much carved in stone now. Hindsight 20/20.)"
1782177,2018-11-14 13:04:07 UTC,"Yes, it only happens on the minimum brightness setting. This is what it looks like before standby to trigger the bug:"
1782177,2018-11-15 21:09:30 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1782177,2018-11-27 08:02:57 UTC,"Luke, any updates here? If not a kernel bug, I would like to close this bug."
1782177,2018-11-27 15:20:12 UTC,I agree that it was probably a userspace change.
1782177,2019-06-28 12:02:04 UTC,Does this issue still happen?
1782177,2018-11-14 08:30:47 UTC,I don't think we have any fixes in drm-tip that should affect this; for that matter I don't recall changes in the area that should regress either. Backlight has been fairly solid for some years now.
1782177,2018-11-27 14:25:02 UTC,"What's the distinction between acpi_video0 and intel_backlight? It seems like a bug to me that those don't match, even if we decide that for legacy reasons the bugged behavior of triggering max brightness is necessary."
1782177,2018-11-14 08:01:53 UTC,"Jani, any comments here? verifying with latest drm-tip will help here?"
1782177,2018-11-09 04:17:29 UTC,[Expired for xfce4-power-manager (Ubuntu) because there has been no activity for 60 days.]
1782177,2018-11-12 08:36:35 UTC,"Luke, Can you set kernel parameters drm.debug=0x1e log_buf_len=4M and reboot the machine. Reproduce the issue and attach the dmesg log from boot. This way we know more information about the issue."
1782177,2018-11-10 01:18:16 UTC,"At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0."
1782177,2018-11-10 01:04:44 UTC,"Oh, and yes it does appear to be lower level than XFCE. I can repro with xset dpms force standby by logging into a Gnome session."
1782177,2018-11-10 00:06:50 UTC,"I can trigger the bug on the xubuntu 18.10 live mode. The GPU is ""Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)"" so I think that's just the integrated chipset for my CPU (Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz)."
1782177,2018-08-18 18:17:28 UTC,"I would think that this is not Xfce specific, but a new bug in the Xorg Intel driver or kernel code."
1782177,2018-08-18 17:35:56 UTC,xset dpms force standby triggers the issue. When the screen turns on it's full brightness (if I have the brightness set to the lowest setting.) It doesn't cause any new dmesg output when I run that command.
1782177,2018-08-18 17:02:32 UTC,Does the following command trigger this issue?
1782177,2018-11-13 18:51:59 UTC,"Created attachment 142454
DMESG output with drm.debug enabled"
1782182,2018-07-20 16:02:28 UTC,The package has been published and the bug is being set to Fix Released
1782182,2018-07-20 09:35:43 UTC,Meta-only (tested via hwe)
1782182,2018-07-20 14:42:43 UTC,Decided to not wait for this to get kernels released. Also for hwe-edge there is no extra testing needed as it is the same as hwe.
1782185,2018-07-20 16:04:00 UTC,The package has been published and the bug is being set to Fix Released
1782185,2018-07-20 14:40:56 UTC,Decided to not wait for this to get kernels released.
1782185,2018-07-20 09:40:20 UTC,Meta-only (testing done in azure)
1782199,2018-07-22 12:20:59 UTC,Probably the test is implicitly relying on a -I. being default (which perl upstream is migrating away from)
1782199,2018-07-23 10:18:25 UTC,"gxyrs tests starts to fail after perl upgrade (5.24 => 5.26).
The same happens with Lepton EDA:
https://github.com/lepton-eda/lepton-eda/issues/231
https://github.com/lepton-eda/lepton-eda/pull/232"
1782199,2018-12-08 16:57:42 UTC,For Lepton EDA this was fixed in b60bdf4 (24/Jul/2018).
1782206,2019-10-29 16:25:59 UTC,"Most likely we will have qemu 4.2 in Ubuntu 20.04.
But we already closed this bug for qemu with the patches you identified in the past.
If you need - for tracking purposes - a bug that closes once these further changes are in I'd ask you to open a new one."
1782206,2019-10-29 16:15:35 UTC,"qemu post 4.1.0 (yet untagged)
67192a298f5 x86/cpu: Add support for UMONITOR/UMWAIT/TPAUSE
6508799707b target/i386: Add support for save/load IA32_UMWAIT_CONTROL MSR"
1782206,2019-09-30 20:57:19 UTC,Additional KVM patches has been merged (post 5.3-rc8):
1782206,2019-07-24 18:12:04 UTC,"Setting linux task to triaged, as there are commits to pick up. Xen I'm still unsure."
1782206,2019-07-03 14:51:27 UTC,This bug was fixed in the package qemu - 1:4.0+dfsg-0ubuntu1
1782206,2019-05-09 14:40:04 UTC,Looks like this is a feature request rather than a bug?
1782206,2019-05-07 16:44:16 UTC,"Chris: a little of both.  The UMONITOR/UMWAIT/TPAUSE is delay, but the rest has been upstreamed (as you already noted.)"
1782206,2019-05-07 05:23:55 UTC,The qemu commits have landed in 4.0 - so that part should work in Ubuntu 19.10
1782206,2019-02-11 07:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782206,2019-03-05 02:55:39 UTC,KVM patches are queuing.
1782206,2019-02-12 04:19:43 UTC,The detail git commits of Qemu are as below:
1782206,2019-02-11 07:04:59 UTC,"Ok, now we finally know it is about qemu&kernel patches - I'll add tasks for that.
Still haven't seen any xen references, setting that to incomplete."
1782206,2019-02-10 02:26:15 UTC,"Others information:
The series for kernel patches:
https://lkml.org/lkml/2018/11/6/379
https://lkml.org/lkml/2018/11/6/377"
1782206,2019-02-10 02:25:07 UTC,post qemu 3.1.0 (currently untagged)
1782206,2018-07-20 06:50:44 UTC,"Hi,
title says KVM, but the bug is only against xen so far."
1782206,2019-03-20 16:55:11 UTC,"33823f4d6 x86/cpufeatures: Enumerate MOVDIRI instruction
ace6485a0 x86/cpufeatures: Enumerate MOVDIR64B instruction
65e259d5c tools arch x86: Update tools's copy of cpufeatures.h"
1782207,2019-05-07 05:38:38 UTC,Feature request that does not need the kernel logs the bot asks for
1782207,2019-05-07 05:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782207,2019-05-07 05:27:16 UTC,@Quanxian - as usual let us know when you have mailing list posts or even better commits in the kernel and qemu that we can use to track and integrate this.
1782207,2018-07-20 06:50:37 UTC,"Hi,
title says KVM, but the bug is only against xen so far."
1782207,2019-05-07 05:26:22 UTC,"This is another bug filed against xen, but then mentioning qemu and kernel.
There was no feedback since my question a few months ago, but xen as the only target package makes no sense it seems.
I added bug tasks accordingly."
1782208,2018-07-20 06:50:46 UTC,"Hi,
title says KVM, but the bug is only against xen so far."
1782208,2019-05-07 05:28:26 UTC,"Again, this semes to be a Kernel/qemu bug that was only filed against xen.
Added bug tasks to not get lost."
1782208,2019-05-07 05:28:55 UTC,Are there updates and/or references to commits in those projects already that we can use to track and integrate those features?
1782208,2019-05-07 05:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782208,2019-05-07 05:38:41 UTC,Feature request that does not need the kernel logs the bot asks for
1782208,2019-05-07 16:46:51 UTC,No updates/upstream at this time.
1782209,2019-05-07 16:42:24 UTC,Related QEMU patch can be found at:
1782209,2019-03-12 06:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782209,2019-05-07 05:18:44 UTC,"Hi,
I have not seen the kernel changes in 5.2 RCs - is there an update on their progress?
Also any updates, links, commits on the related qemu contribution?"
1782209,2019-03-12 06:27:31 UTC,"My questions in comment #1 where no answered directly yet, but this still is using only kernel patches so far, I think it is time to add at least a kernel task."
1782209,2018-07-20 07:32:52 UTC,"Oh mass update fail, this one actually is against kvm.
Which is the wrong package since several years actually."
1782209,2018-07-20 06:50:41 UTC,"Hi,
title says KVM, but the bug is only against xen so far."
1782209,2019-03-05 02:58:39 UTC,patches to lkml along with kernel's patches.
1782214,2020-05-19 12:30:58 UTC,"Yes, it is also missing all files from http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/. Debmirror mirrors this if you give the --di option."
1782214,2020-05-19 12:31:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782215,2018-07-17 18:08:42 UTC,"Hi Jeff,"
1782215,2018-07-19 21:49:15 UTC,"I did mention that this needs to be handled via maas-images (but I did forget to add that as affected).  However, I disagree that no change is necessary on MAAS part."
1782215,2018-07-19 21:50:54 UTC,"Note, in my scenario above, ""upgrade my hardware to bionic"" really means redeploy my workloads on Bionic using MAAS so I can have the latest and greatest Ubuntu."
1782215,2020-04-07 07:14:23 UTC,"Hi, we're tracking feature requests in our discourse (https://discourse.maas.io/c/features)."
1782218,2018-07-17 18:22:52 UTC,"Additionally, the link provided to report the bug upstream is 404."
1782220,2019-09-19 12:06:04 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1782221,2019-11-09 21:51:49 UTC,The default behavior should be inheriting from one of the physical interfaces. I can confirm under RHEL7.
1782221,2019-12-29 12:30:12 UTC,"This wishlist report is, at least should be, outdated."
1782221,2020-05-16 00:36:01 UTC,"Please see this kernel commit message for the reason setting the bridge MAC address was even possible in the first place (yes, it was for the cloning use case):
https://lists.linuxfoundation.org/pipermail/bridge/2008-March/005739.html"
1782221,2020-06-13 16:15:38 UTC,"Is there any indication of how the ""random"" MAC address is generated, or where it's cached?"
1782221,2020-07-20 15:03:58 UTC,"This is causing me a nightmare on Hetzner with bridged KVM networking - the host machine (18.04 LTS Server) is ""leaking"" these arbitrary MAC addresses to the outside world and Hetzner is not happy obviously."
1782221,2019-09-03 21:39:20 UTC,Edit: I should have posted my OS version. I am using Linux Mint 19 (Tara) which is based on Ubuntu Bionic.
1782221,2020-07-20 15:20:30 UTC,"@theopensourcerer: Comment #2 shows how to set a MAC address on a Netplan interface:
https://bugs.launchpad.net/netplan/+bug/1782221/comments/2"
1782221,2020-06-13 16:45:42 UTC,"> Is there any indication of how the ""random"" MAC address is generated, or where it's cached?
"
1782221,2019-06-26 19:53:16 UTC,"Edit : macaddress settings need a reboot, (I tried to netplan generate/apply, restart systemd-networkd ) ..."
1782221,2019-09-03 21:37:18 UTC,I experienced this issue as well which was a problem for me in dual booting scenarios (a random MAC on br0 under Linux and then the native MAC under Windows). I originally had a static lease configured and couldn't understand why I would get a different IP randomly. Then I realized this is exactly what was happening. I added the native macaddress to my br0 interface and rebooted. It worked! Thanks!
1782221,2019-05-29 20:44:12 UTC,setting the `macaddress` of the bridge doesn't work for me on 18.04
1782221,2019-06-26 19:44:34 UTC,"Same here, `macaddress` of the bridge doesn't work for me on 18.04"
1782221,2019-05-13 20:57:52 UTC,The same proble with the bonding interfaces
1782221,2019-03-25 18:00:08 UTC,"So in practice, the ""random"" mac address is not so random.  I have a configuration where I'm deploying a set of machines in the same network, where each device has a br0 internally.  Turns out, I often get matching ""random"" mac addresses across my machines, causing a conflict."
1782221,2018-07-26 15:35:09 UTC,"For the purposes of this bug, I wonder if we could just preserve the ""stable but random"" behavior for virtual bridges, but if netplan knows that the bridge ultimately contains an Ethernet interface (possibly via a bond) we could simply use its MAC as the stable MAC by default. That way no change in behavior from networkd is required."
1782221,2018-07-26 13:55:04 UTC,It looks like this is a limitation of networkd - I can't find anything in the docs or with google that would enable you to inherit a MAC. Looping in systemd devs for their thoughts.
1782221,2018-07-17 19:15:25 UTC,I think that having to provide the MAC is redundant and unnecessary.
1782221,2018-07-17 19:05:13 UTC,It appears that the .netdev file can accept the MAC address value:
1782221,2018-07-17 18:43:47 UTC,"For what it's worth, I understand that the actual bug is not in netplan, but I think it would be nice to make things consistent across renderers by working around this in netplan."
1782229,2018-08-14 23:42:15 UTC,"Actually, this seems like it's maybe just a documentation bug. I tried this just now and it worked. ;-)"
1782230,2018-08-21 15:23:03 UTC,"@Kit,"
1782235,2020-03-21 16:32:35 UTC,Closing because CAN'T REPLICATE.
1782237,2018-09-17 12:15:10 UTC,"Hi,
Can you check this option in he hp-toolbox settings and see if you can select the alternate output bin and test the functionality and update?"
1782237,2018-10-04 18:04:12 UTC,"Hello Srinivas,"
1782238,2018-12-10 15:36:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782240,2018-07-17 22:58:55 UTC,"Not sure what an os-vol-host-attr:host container is, but if Cinder is down then you can't expect to be able to do much with it."
1782262,2018-07-17 23:58:36 UTC,"Oh, and there is no way to change this behavior in the GUI despite it being there in previous releases; gnome seems to continue to remove useful features and dumb down the gui to uselessness."
1782263,2018-07-31 00:56:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782263,2018-07-31 06:11:50 UTC,"I have discovered the cause - or trigger (proximate cause) - for at least most of the instances of this error on my system. It's this command, which I was running regularly via an automated script, and not as root."
1782263,2018-07-31 10:35:41 UTC,I have same issue on executing `nm-online` as a normal user.
1782263,2018-08-29 10:32:21 UTC,Messages of this sort have now started *flooding* my system (journald) log.
1782263,2018-12-31 17:01:02 UTC,Corresponding bug in polkit project: https://gitlab.freedesktop.org/polkit/polkit/issues/6
1782263,2019-01-15 03:03:12 UTC,"Thanks, Fabian, for the link to the polkit bug tracker (I filed that bug against polkit). It seems from that tracker that the problem has now been fixed. However, the fixed version has yet to arrive on Mint. Indeed it may not yet have arrived on Ubuntu. If it has yet to reach Ubuntu, I feel it is unlikely that Mint will get it, until it does reach Ubuntu. What to do in the meantime?"
1782263,2019-01-23 06:39:31 UTC,Any news ?
1782263,2019-01-24 12:21:19 UTC,"This is likely a bug in network-manager, not policykit...adding network-manager to this."
1782263,2019-07-09 10:40:09 UTC,To disable warning (and authentication) you can add:
1782263,2019-07-09 13:59:44 UTC,@Anton
1782263,2019-12-31 13:56:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782273,2018-10-15 14:33:22 UTC,"Hi, rdfind author here.
This is not related to -makeresultsfile, it is because -n expects a boolean argument. This is awkward, and related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754663."
1782273,2018-10-28 09:35:51 UTC,"This is fixed in 1.4.0-alpha0, feedback welcome.
https://github.com/pauldreik/rdfind/releases/tag/releases%2F1.4.0-alpha0
Paul"
1782274,2018-09-03 19:19:15 UTC,"I see the same problem while trying to upgrade to ubuntu 18.04. The upgrade seems stuck after the line
Processing triggers for resolvconf (1.79ubuntu10) ..."
1782274,2018-09-03 19:19:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782274,2018-09-11 21:14:19 UTC,"I had the same problem as Parakram, but found that the upgrade did actually finish correctly though the terminal window remained stuck at that line for three or four hours. Something was still happening,"
1782275,2018-07-20 10:05:18 UTC,"Given that it is a conffile, you can remove the one you do not need."
1782275,2018-07-20 18:25:34 UTC,"This issue can be addressed with a manual action, but first you have to dig into the scripts to diagnose the problem, and really if resolvconf is installed then it should just work."
1782275,2019-06-30 01:40:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782275,2020-04-14 05:34:01 UTC,This issue is still present in Ubuntu focal.
1782280,2018-07-18 04:01:48 UTC,Argh...
1782280,2018-07-18 04:27:54 UTC,"The missing information seems to be present in juju show-controller --format yaml, but it would nevertheless be nice not to have to write code to merge these myself."
1782281,2021-01-09 22:44:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1273534, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1782282,2019-04-15 05:31:14 UTC,PR https://github.com/juju/juju/pull/10045
1782282,2019-04-15 07:54:39 UTC,PR https://github.com/juju/juju/pull/10045
1782298,2019-06-14 04:17:25 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1782298,2019-04-14 18:35:52 UTC,"I checked the diff for the kibana role between queens and rocky, and the task you mention (Register the kibana index in elasticsearch) was added in Rocky."
1782298,2019-04-14 11:31:43 UTC,"I apologize, the link that I gave was about Skydive not Kibana."
1782298,2019-04-14 11:22:48 UTC,"Lev, I suggest you use the Queens release (6.y.z) of kolla-ansible to deploy Queens containers. We just released 6.2.0. Alternatively, use the stable/queens branch for the latest fixes."
1782298,2019-04-14 11:10:29 UTC,"Hi, Mark!"
1782298,2019-04-14 03:09:06 UTC,"Hi Klimin,
I think this issue is similar with this one https://bugs.launchpad.net/kolla/+bug/1806167"
1782298,2019-04-14 10:28:47 UTC,"Hi Lev, please use the same version of kolla containers as kolla-ansible. We do have stein tagged images on dockerhub, e.g. https://hub.docker.com/r/kolla/centos-source-kibana/tags."
1782298,2019-04-13 17:22:50 UTC,"Hi,"
1782298,2019-04-14 10:29:34 UTC,"Danni, can you verify if this is still broken? I believe kibana should be working in Queens and onwards."
1782300,2019-09-19 10:15:43 UTC,"I also meet the same problem.
Does anybody have solutions for this problem?"
1782300,2021-01-12 04:17:32 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1782300,2020-11-12 15:38:29 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1782304,2021-01-13 03:22:24 UTC,"This is not a problem in ""appstream"", it's usually a package manager issue, e.g. if there was a power outage during upgrades or install/remove steps. In this case, it just randomly hit the appstream package.
If the APT installation is fixed, this problem should go away. Please file an issue against APT in case this is a persistent problem!"
1782305,2018-07-20 08:29:14 UTC,It seems like we could solve this requirement by adding a new YAQL function.
1782305,2019-07-22 07:21:45 UTC,I'm not sure it's a good idea in general. We assumed from the very beginning that it should be an immutable structure and in many places in the code we use that assumption. Also remember that Mistral passes an environment into sub workflows. How is that supposed to work if it becomes mutable? Should it be the same structure (i.e. modifications in sub workflows are seen in parents) or we need to copy?
1782305,2019-08-28 06:21:23 UTC,"Marked it ""Incomplete"" for now since it's not 100% clear how to make the change properly. And we also need to look at the mentioned use case first."
1782306,2019-11-07 14:59:41 UTC,"Since commit 83e8336, gEDA/gaf builds with Guile 2.0 or Guile 2.2."
1782306,2019-11-11 02:43:27 UTC,"I tried to build afainst Guile 2.2, but xorn failed to build as the configure script is looking for Guile 2.0 only:
PKG_CHECK_MODULES([GUILE], [guile-2.0 >= 2.0.10])"
1782306,2020-03-03 01:40:02 UTC,"So according to the guile-2.2 docs, here:"
1782306,2020-03-03 10:32:29 UTC,"The function ‘scm_frame_procedure_name’ conceptually replaces ‘scm_frame_procedure’, but there's an important difference: the former returns the name of the procedure while the latter returns the procedure itself."
1782306,2020-05-10 04:40:09 UTC,Please migrate to Guile 3.0
1782306,2020-10-19 19:41:36 UTC,"As of commit 12f0fa40615e322cd0334f70accb04d3ef6e8b5c, gEDA/gaf now uses Guile 2.2."
1782312,2020-08-04 16:47:26 UTC,I tested this problem in Pinta Ubuntu's Daily PPA 1.7+r1134-202008032046~ubuntu18.04.1 I can confirm the behaviour.
1782315,2018-07-18 12:18:37 UTC,"This is known behavior, and expected.
cloud-init uses the metadata service to tell it if it is a new instance (and should run per-instance things).
That does create a dependency on the metadata service."
1782323,2018-08-02 23:22:08 UTC,"As said, this is a known limitation of MPlayer, the interesting question is if other players show A/V desync."
1782323,2018-07-21 14:08:17 UTC,"That is what I believe, you could test with vlc, totem, ffplay (wmp and qt)."
1782323,2018-07-20 20:53:20 UTC,"It is a known limitation of MPlayer that it needs audio for A/V sync, it therefore cannot ""wait"" for audio as FFplay should be able to."
1782323,2018-07-31 23:39:26 UTC,Which players fail?
1782323,2018-08-01 20:58:45 UTC,At least mplayer.
1782323,2018-07-21 20:08:25 UTC,"Just because _some_ of these programs can use it, it does not necessarily mean they are correct mp4 files."
1782323,2018-07-19 22:12:00 UTC,I currently do not see why this is not reproducible.
1782323,2018-07-20 21:03:13 UTC,So is this still a valid and commonly usable video?
1782323,2018-07-18 13:42:31 UTC,Upstream: https://trac.ffmpeg.org/ticket/7299
1782323,2018-07-18 13:26:32 UTC,mplayer
1782323,2018-07-18 12:51:57 UTC,"I can't seem to reproduce this. What player are you using for testing? I notice that in bad.mp4, there is about a second of extra video at the start of the stream with a negative timestamp. Maybe your video player doesn't handle this properly?"
1782323,2018-07-18 09:33:41 UTC,Please note that the two working methods shown in the Makefile have severe disadvantages.
1782323,2018-07-18 09:31:21 UTC,Makefile for Ubuntu 18.04 to demonstrate the problem.
1782323,2018-07-19 19:37:29 UTC,"When I set the resolution to ""worksforme"", I meant that I couldn't reproduce with FFmpeg 3.4, I would have set it to ""invalid"" if the issue were fixed.
Are you searching for the MPlayer option ""-mc 100""?"
1782328,2018-09-27 13:41:48 UTC,I ran into the same issue:
1782328,2018-08-13 08:38:52 UTC,"I've performed fresh installation using packstack of:
- newton
- ocata
- pike
- queens
None of aboved have shadow_tags table in nova database."
1782328,2018-08-09 07:56:36 UTC,"I'm not able trace piece of code which was responsible for shadow_tags table creation but somehow it happened during upgrade. I will try to reproduce it during:
- upgrade from newton to ocata
- fresh ocata installation
- fresh pike installation
- fresh queens installation"
1782328,2018-07-24 03:46:30 UTC,"Hi, I did not saw the above mentioned code in Ocata, Pike and Queens code, where actually is that code?"
1782328,2018-07-23 11:36:03 UTC,shadow_tags table exists:
1782328,2018-07-19 13:04:42 UTC,I my environment 'tags' table is empty and during nova-manage db archive_deleted_rows I've got above exception.
1782328,2018-07-19 20:33:15 UTC,"Hmm, we run archive_deleted_rows in our CI so if this was a 100% failure I'm not sure why we wouldn't see it there."
1782328,2018-07-19 03:03:12 UTC,"I cannot reproduce this as when instance got destoried the related tags are also deleted:
https://github.com/openstack/nova/blob/683fbe3c84ee70e817ffb8396fefb9ff6cd8830d/nova/db/sqlalchemy/api.py#L1824
and there are no deleted field in the tags table, so their should be nothing to archieve in the tags table when running this command."
1782328,2018-07-19 20:35:15 UTC,You should be hitting this short-circuit:
1782329,2018-07-30 09:25:15 UTC,"Reviewed:  https://review.openstack.org/584900
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=84a8c59be69cb0c2c473eb3307985264b4fba98f
Submitter: Zuul
Branch:    stable/queens"
1782329,2018-12-12 15:30:09 UTC,"I would say the fix is committed for charm-lxd, part of commit:"
1782329,2018-07-23 11:00:33 UTC,"Reviewed:  https://review.openstack.org/583969
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=f1bbc03b65ab8af25be5fa982e3ac24ba591bee9
Submitter: Zuul
Branch:    master"
1782329,2018-07-23 14:19:29 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/584900"
1782329,2018-07-19 10:45:31 UTC,On a xenial with lxd 2.x:
1782329,2018-07-18 13:19:40 UTC,More logs and artifacts:
1782329,2018-07-19 14:11:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583969"
1782330,2018-07-27 13:03:25 UTC,"I really think the charm should just do the right thing; when the new units appear and one is elected leader, it should figure out that the users don't exist and re-create them (I suspect the check is done on presence of data in the leader database provided by juju)."
1782342,2018-07-19 10:45:00 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1782342,2021-02-13 18:13:31 UTC,"This bug is fixed in Ubuntu 20.10 (and probably earlier versions), as Ubuntu 20.10 uses mawk 1.3.4 20200120. So you can close the bug report. (I'd close the bug report myself but don't seem to have the bits to do that.)"
1782344,2021-02-17 17:08:47 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1782344,2019-07-31 21:14:36 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/583956
Reason: This review is > 90 days without comment, and failed Zuul the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1782344,2019-07-31 21:14:29 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1782344,2018-07-19 13:09:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/583956"
1782346,2018-07-22 05:37:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782347,2018-08-21 01:46:24 UTC,No problem. Just wait until it happens again and eventually one of the crash reports will be more usable.
1782347,2018-08-20 11:55:40 UTC,"Bug #1787698 was reported to be useless, possibly because the machine was not up-to-date, which isn't the case because mine was; so I can't be more helpful here..."
1782347,2018-08-18 07:19:23 UTC,The newly created crash report is #1787698.
1782347,2018-07-30 02:27:42 UTC,Thanks. Unfortunately crash bug 1783999 is partially corrupt and not debuggable. So please send more crash reports as soon as you find them...
1782347,2018-07-27 13:22:49 UTC,"Thanks, I did step #2 (#3 was useless because #2 didn't fail) and the newly-created bug report is #1783999."
1782347,2018-07-27 01:59:53 UTC,"Mostly the same, yes. That's just a dumb bot... You can choose to either do as it asks or to ignore it and set 'Confirmed'."
1782347,2018-07-26 11:56:28 UTC,Isn't it the same logs I provided with apport-collect before?
1782347,2018-07-25 10:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782347,2018-07-25 09:30:48 UTC,"Nothing crashed, so I skipped Your points #2 and #3."
1782347,2018-07-20 01:45:06 UTC,Please edit your /etc/gdm3/custom.conf and comment out:
1782347,2018-07-21 09:54:14 UTC,"Sorry, no improvements."
1782347,2018-07-19 11:45:45 UTC,Logs were taken when booting with 'nomodeset'; otherwise the machine is unbootable.
1782347,2018-07-19 11:43:02 UTC,apport information
1782347,2018-07-19 11:43:00 UTC,apport information
1782347,2018-07-19 11:42:59 UTC,apport information
1782347,2018-07-19 02:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782347,2018-07-19 01:45:04 UTC,Sounds like a kernel driver problem. Adding a 'linux' task.
1782347,2018-07-23 02:27:48 UTC,"OK, next please run these commands and send us the resulting files:"
1782357,2018-07-24 14:01:17 UTC,"Looks valid. I didn't dig in the code, but we've got those issues in the past. Master is quite different due to the rework we've done, but Queens should get fixed in that regard, IMO."
1782357,2018-08-06 07:43:00 UTC,"Hello,"
1782357,2018-10-23 19:42:45 UTC,"The missing variables are set in group_vars for Rocky release.
Is a backport possible ?"
1782357,2018-10-29 12:31:08 UTC,"We hot the bug today. Digging through some irc logs, some more people had the problem:
http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2018-03-22.log.html#t2018-03-22T11:10:39
http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2018-07-20.log.html#t2018-07-20T09:21:19
Bhujay posted a workaround: http://paste.openstack.org/show/726321/ But that included changing the playbook.
You could also change the ansible command executing the playbook:
openstack-ansible os-ceilometer-install.yml \
-e @../inventory/group_vars/glance_all.yml \
-e @../inventory/group_vars/nova_all.yml \
-e @../inventory/group_vars/cinder_all.yml \
-e @../inventory/group_vars/neutron_all.yml \
-e @../inventory/group_vars/heat_all.yml \
-e @../inventory/group_vars/keystone_all.yml"
1782357,2018-11-14 13:07:02 UTC,"I think, that this problem has been already fixed in master already. So the question is to backport patches to Queens."
1782357,2020-04-08 15:55:38 UTC,"So queens is not supported anymore, but this patch is in rocky already.
Fix has been introduced with https://review.opendev.org/#/c/607653/"
1782361,2019-12-17 19:01:44 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/594503"
1782361,2019-12-10 01:10:34 UTC,"Reviewed:  https://review.opendev.org/679312
Committed: https://git.openstack.org/cgit/openstack/oslo.log/commit/?id=b52c8cd247e9b185d176bfbc4c24c5a2cb35e5be
Submitter: Zuul
Branch:    master"
1782361,2019-12-16 21:15:20 UTC,This issue was fixed in the openstack/oslo.log 3.45.1 release.
1782361,2018-08-21 18:13:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/594503"
1782361,2019-08-29 17:56:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/679312"
1782362,2018-07-18 20:28:46 UTC,"This was fixed upstream, in release 2.77."
1782362,2018-07-19 05:50:26 UTC,With 2.77 and later being good marking bug tasks for affected releases accordingly.
1782362,2018-07-19 06:00:20 UTC,"FYI the code does not apply as-is to the older versions.
The changelog/header entries can easily be matched, but the options.c code essentially needs a rewrite to match the older versions - the ttl handling was different and also the code was in other places."
1782362,2018-07-19 06:02:07 UTC,"Steps to reproduce are as easy as:
  $ dnsmasq --cname localhost,localhost"
1782363,2018-11-03 00:40:30 UTC,This message actually comes from a migration in MAAS that is creating a notification.  Please see src/maasserver/migrations/builtin/maasserver/0162_storage_pools_notification.py in the source.  I do not think we can provide a link to the pod or the refresh section from this migration.
1782363,2019-05-16 20:22:54 UTC,"How MAAS currently implements notifications for the UI, this is more of a feature request than a bug, as we would need to modify how MAAS handles notifications in general."
1782370,2018-07-18 21:17:30 UTC,Confirmed in 3.0.8
1782370,2018-07-19 19:16:43 UTC,This looks like it was resolved in master and 3.1 by https://bugs.launchpad.net/evergreen/+bug/1676608
1782383,2018-07-18 21:49:09 UTC,"[ICPU]
was the command
i think ideal name for PC these UI days since (<?user?>) is not getting called back untill i got this error for calling computer ICPU
CALL BACK ()"
1782388,2018-10-02 16:15:28 UTC,"It seems that this is specifically applicable to an LVM/FC storage back-end. It might be good to implement the right packages based on a driver model, but also detect whether multipathing is enabled somehow and implement these settings if it is."
1782388,2018-07-18 16:45:04 UTC,"Some logs with multipathd running, and `iscsi_use_multipath` not enabled in nova.conf:"
1782388,2018-07-30 15:06:15 UTC,Here is what I've discovered...
1782388,2018-07-19 22:29:16 UTC,One other observation.
1782389,2019-11-14 00:39:25 UTC,"I think this is better now, can you re-test?"
1782389,2019-11-18 21:50:37 UTC,Fixed with daily focal live-server ISO
1782398,2018-08-21 14:27:32 UTC,Note that version 263 was the last on that worked. I can still deploy with:
1782398,2018-08-21 13:54:49 UTC,"When I try to deploy onto AWS (on Xenial), I get more errors:"
1782408,2018-07-18 20:24:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1782413,2018-07-18 18:58:35 UTC,I thought we kept the dependencies from backward compatibility ?
1782413,2018-07-19 01:34:14 UTC,MAAS will search the local filesystem for bootloaders if they are not found in the stream. We kept those dependencies in case users had a mirror of a V2 stream they were using which does not contain bootloaders. I'm not even sure a V2 stream from that time would work with MAAS 2.4+ as it may be missing files required for HTTP boot. As the Snap doesn't have these dependencies either I think its safe to remove them.
1782413,2018-07-19 01:51:57 UTC,"The snap is not broadly used to make a appropriate comparison. As most
snaps users are 2.3. That said, we confirmed with Blake’s branch that it
won’t use local boootloaders if these are missing from the stream, I guess
it’s because they either get all and not just one missing."
1782413,2019-09-19 12:00:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1782417,2018-08-22 12:18:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782425,2019-10-22 01:33:55 UTC,You are absolutely right. See bug 701186 :)
1782425,2019-10-21 12:14:27 UTC,"Sorry if I'm being naughty, but on this case the proper status should not be ""Won't fix""?"
1782425,2019-10-21 09:47:43 UTC,We know. That's just a Launchpad bug where it doesn't know the difference.
1782425,2020-03-19 08:39:19 UTC,"""Won't Fix"" because that's upstream's position on this right now."
1782425,2019-10-20 00:57:37 UTC,Bug was closed (not implemented) in Gnome Gitlab: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/369
1782425,2018-07-19 02:03:18 UTC,"There is an existing bug report roughly about this in:
https://bugzilla.gnome.org/show_bug.cgi?id=790128"
1782425,2019-10-21 09:33:28 UTC,"@vanvugt: Not sure if I'm missing something, but the bug was not fixed in Gnome, just closed."
1782427,2018-10-08 05:24:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782427,2020-11-02 01:01:03 UTC,Any update on this?  I did a messy upgrade of 18.04 LTS from 16.04 LTS.
1782427,2020-11-02 01:01:55 UTC,Forgot to add.  This does not appear to affect my ability to connect to my wifi.
1782429,2018-07-19 10:48:00 UTC,Thank you for the suggestion.
1782442,2020-03-20 18:26:24 UTC,Closing because INVALID: support request.
1782442,2018-07-21 09:57:55 UTC,"good to hear, I'm glad it worked."
1782442,2018-07-19 19:50:38 UTC,"@Magdalena - could you indicate whether the ""resaved"" file works better than the original?"
1782442,2018-07-18 23:12:58 UTC,"- running Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
I loaded the file and received a very large number of warnings shown below. It was also zoomed in to level 25600% which seemed to be slowing down the refresh.
I resaved it, to get the attached file. Could you try this one, it appears to be behaving better than the original. The only difference I could see is that the new file is missing the commands:
        inkscape:collect=""always""
which may have been slowing down the refresh."
1782442,2018-07-20 13:04:00 UTC,"Alvin, you are a life saver. Attached file works well!
Thank you for your help!"
1782443,2018-07-19 13:02:49 UTC,"Digging into this problem, I learned that:"
1782448,2018-07-18 23:32:26 UTC,Need to apply the same fix as in https://review.openstack.org/#/c/175291/
1782448,2018-07-19 03:33:45 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/583835"
1782451,2018-07-19 19:01:35 UTC,"""It's definitely not clear to me if this is an Ubuntu issue, an upstream issue, or a VMware issue."""
1782451,2018-07-19 18:49:44 UTC,"Thanks for your response, Christian,"
1782451,2018-07-27 17:33:57 UTC,"Sorry, I was on a vacation, so didn't notice this earlier. I informed Peter from the guest customization team."
1782451,2018-07-19 00:19:36 UTC,"FYI, I looked into VMware's Customization.pm file and their comment says that says they run ""/sbin/ifconfig eth0 2> /dev/null"" to ""wake up"" the interface, so whatever's going wrong isn't as simple as a hardcoded network interface address in VMware code."
1782451,2018-07-19 05:42:43 UTC,"Hi Thomas,
the Customization.pm seems to be from terraform or some other of your tooling right?
The build log [1] doesn' tmention that file in any package out of open-vm-tools."
1782457,2018-07-19 00:44:24 UTC,I have managed to resolve this by removing the following packages:
1782466,2018-08-14 16:42:22 UTC,"not a binutils issue, please just re-install the package."
1782466,2020-01-25 15:43:00 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1782466,2020-03-26 04:17:25 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1782468,2018-07-19 12:59:15 UTC,https://review.openstack.org/#/c/577863/ ?
1782470,2018-07-19 12:49:57 UTC,Yup! reinstalling worked. But it crashed on some other error. I sent the report. Do I need to send the apport report?
1782470,2018-07-19 09:38:40 UTC,"Boot into the kernel with working internet, in terminal do"
1782470,2018-07-19 04:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782470,2018-07-19 04:55:12 UTC,"As I am unable to connect to the net, obviously the command apport-collect failed. The kernel response is given below:"
1782473,2019-04-22 06:07:07 UTC,"There is a search tool for generic Ubuntu (Bionic), in the upper right corner."
1782481,2018-07-21 09:18:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782507,2019-06-21 01:39:16 UTC,This bug was fixed in the package partman-auto-lvm - 59ubuntu4
1782507,2019-06-14 17:04:43 UTC,"or maybe just ""$hostname_vg"" will make things pretty enough, and e.g. consistent with $foo_crypt that we use for LUKS encrypted volumes."
1782507,2019-06-21 00:49:02 UTC,"vg$hostname it is, i think camel case and mixed _- is ugly too."
1782507,2019-05-17 20:59:59 UTC,"This isn't new, LVM-based installs have been showing this way for a while:"
1782507,2018-07-19 05:07:59 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1782507,2019-06-14 17:03:15 UTC,"The problem is that we create /dev/$VG/$LV , meaning that $VG name may not clash with any existing devices in /dev..... and hostnames sometimes do."
1782510,2020-01-29 01:15:05 UTC,So I've just restarted the lightdm.service :
1782510,2018-07-24 02:33:13 UTC,To add further information. This is on multiseat system. Lately (~2 weeks) the system also started misbehaving where only one of the sessions can login reliably. THe other session login doesn't affect the Enter button to submit the password and start the session
1782510,2018-08-01 07:53:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782510,2018-08-01 07:58:00 UTC,"After the second login, the session is not comlete, e.g. groups from pam+ldap are missing. Also the default KDE Wallet is not opened upon the first successful login. sddm works as expected."
1782510,2018-10-28 18:13:58 UTC,This defect may not be in lightdm package. I was just able to reproduce it on Ubuntu 18.04.01 distribution. Here is how I did it.
1782510,2020-01-29 01:07:12 UTC,"Hi, I have the same pb. on my ubuntu xenial,
here's what I get in the ""lightdm.service"" journal :"
1782511,2019-01-24 23:59:50 UTC,"today pc builtin speaker works, I didn't change anythings
here is the log today:
 http://www.alsa-project.org/db/?f=596407a5d73efbe9caa99db23ca2a5586664b45a"
1782511,2019-01-22 21:20:35 UTC,"I can change sound volume, mute/unmute. It shows as everything works fine but actually no sound on builtin speaker.
Jack 3.5 works fine.
Bluetooth speaker works fine."
1782511,2019-01-22 20:35:46 UTC,"It happens on my PC too
Ubuntu 18.04
HP Pavilion Power CB015NF
ALC295"
1782511,2019-01-22 20:35:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782513,2020-03-20 18:24:26 UTC,Closing because Duplicate Issue. Please see https://gitlab.com/inkscape/inbox/-/issues/1817 .
1782516,2018-07-25 04:26:45 UTC,"Posted a patch.
https://review.openstack.org/585596"
1782517,2018-07-25 04:27:25 UTC,"Posted a patch.
https://review.openstack.org/585625"
1782517,2021-02-01 12:38:04 UTC,This issue was fixed in the openstack/masakari 9.1.1 release.
1782517,2021-02-01 12:38:45 UTC,This issue was fixed in the openstack/masakari 10.0.1 release.
1782517,2021-02-01 14:44:43 UTC,This issue was fixed in the openstack/masakari 8.1.1 release.
1782520,2018-08-16 16:49:04 UTC,"Sorry, no, I'm actually for a quite long time far away from home."
1782520,2018-07-23 09:20:58 UTC,"I have succeeded yesterday to scan via WLAN and an Android app from the Smartphon, so it is certainly not a hardware problem."
1782520,2018-08-14 11:58:41 UTC,"Hi Ilja,"
1782520,2020-05-07 14:57:15 UTC,Hello What is the status with this one?  I have the 18.04 and have the same problem running hplip 3.20
1782520,2020-05-07 14:58:16 UTC,"If you guide me through it, I'll be willing to write a tutorial online for this particular model.  It looks like a good printer with a very good price.  It would be attractive for Ubuntu Users."
1782524,2021-02-19 15:52:34 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1782524,2021-02-01 16:37:12 UTC,"Mistral is no longer used for deploying the undercloud, from my point of view this bug is not valid anymore."
1782524,2018-07-19 07:37:40 UTC,"As a workaround I added the /usr/share as a volume to be mounted on the mistral-engine t-h-t and
re-run ""openstack undercloud deploy"" command."
1782524,2018-07-20 06:59:33 UTC,"Change abandoned by Juan Badia Payno (<email address hidden>) on branch: master
Review: https://review.openstack.org/583877
Reason: In favor of https://review.openstack.org/#/c/583136/"
1782524,2018-07-20 07:53:52 UTC,Addressed by: https://review.openstack.org/#/c/583136/
1782534,2018-08-07 13:29:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782534,2020-09-19 18:26:51 UTC,"After updating they have updated the old ubuntu Software with a new app named just 'Software'
Look for it in activities."
1782535,2018-07-19 16:01:07 UTC,Some additional performance measurements with dd...
1782535,2019-01-30 10:15:10 UTC,"Thank you for your bug report, what are the performances if you use ""cp"" from the command line and if you use ""gio copy""? Those are probably closer things to compare nautilus to than rsync/dd which don't have the same purpose"
1782535,2019-02-02 11:11:38 UTC,Thank you for looking into this problem.
1782535,2019-02-02 15:49:17 UTC,"By the way, due to freezing issues with copying many small files last august, I was forced to change fstab. The cifs/smb version is now 2.0:
//ip-address/home /mnt/cifs_nas_home cifs uid=florian,gid=florian,credentials=/home/florian/.smbcredentials,dir_mode=0700,vers=2.0 0 0"
1782535,2019-02-02 23:35:51 UTC,"Thank you for the detail, if 'gio' also has the issue then it's a lower level issue and not a nautilus problem, reassigning.  That's also probably an upstream issue and would be worth reporting on https://gitlab.gnome.org/GNOME/glib"
1782535,2019-02-16 11:36:15 UTC,"As you proposed:
https://gitlab.gnome.org/GNOME/glib/issues/1688"
1782535,2019-02-17 08:28:39 UTC,Thanks!
1782535,2019-06-13 17:02:29 UTC,Issue may get closed.
1782535,2019-06-21 16:10:14 UTC,Would still be good to backport to the LTS if we know what changed resolved the issue
1782544,2018-09-14 09:03:01 UTC,Upgraded to the latest mainline kernel (4.18.7-041807-generic) and the issue is not present.
1782544,2018-07-19 10:00:08 UTC,This change was made by a bot.
1782544,2018-07-19 16:33:30 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].
1782544,2018-07-20 09:18:33 UTC,Tested on  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.142 and issue no longer present.
1782544,2018-07-30 11:12:29 UTC,Bug also present in the 4.4.0-131-generic kernel
1782544,2018-09-03 17:38:15 UTC,I just upgraded my system and the bug is there.
1782544,2018-09-07 00:20:58 UTC,I have Ubuntu 16.04.5 with kernel 4.15.0-33-generic and the bug is there.
1782544,2018-09-12 14:00:32 UTC,"Can confirm bug returns moving from kernel 4.15.0-32 to 4.15.0-33, tested on both 16.04 Server and 18.04 Server.  Tested with program using pcap_inject (libpcap 1.7.4 (16.04) and libpcap 1.8.1 (18.04)), no issues seen with 4.15.0-32 (or 4.15.0-29), additional 14 bytes being transmitted with 4.15.0-33 and 4.15.0-34."
1782544,2018-09-13 10:17:48 UTC,Confirming the bug is present on Ubuntu 16.04 using kernel 4.15.0-33 when using pcap_inject. An extra 14 bytes are sent on the end of packets causing them to appear invalid in Wireshark.
1782544,2018-10-03 07:56:26 UTC,I saw the issue on both Ubuntu 16.04 and 18.04 with kernel versions 4.15.0-33-generic and 4.15.0-34-generic.  The problem is not there for the latest released kernel version 4.15.0-36-generic.
1782545,2018-11-14 16:10:00 UTC,"This is fixed with the snapd in master:
$ cat /tmp/1/meta/snap.yaml
name: zz
version: 0
$ snap pack /tmp/1/ && snap-review zz_0_all.snap
built: zz_0_all.snap
zz_0_all.snap: pass"
1782545,2018-07-19 10:00:56 UTC,Using mksquashfs as suggested does work.
1782548,2019-01-07 14:46:16 UTC,This issue was fixed in the openstack/kolla-ansible 6.1.1 release.
1782548,2018-08-13 07:35:14 UTC,"Reviewed:  https://review.openstack.org/590692
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=7f258f8a16ecb595e1f86404910f04f5c343642b
Submitter: Zuul
Branch:    stable/queens"
1782548,2018-08-10 08:15:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/590692"
1782552,2018-07-25 10:33:01 UTC,"not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1782552,2018-07-25 10:44:27 UTC,"Still a problem on Opensuse Tumbleweed, Inkscape 0.92.3 (2405546, 2018-03-11), but only when using the internal import method."
1782552,2018-07-25 11:44:29 UTC,Also happens when using the newest git version
1782552,2018-07-25 14:27:58 UTC,"upon further testing, I get the following results:
- reproduced on Windows 10, Inkscape 0.92+devel (e33f40d, 2018-06-25), svg result attached here.
- reproduced on Windows 10, Inkscape 0.92.3 (cdafc07, 2018-06-25), same result
- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1782552,2019-01-19 18:12:17 UTC,"I can no longer reproduce the bug on my own machine, importing pdfs works fine now. Close?"
1782552,2019-01-19 18:36:45 UTC,"- problem not reproduced on Windows 10, Inkscape 0.92.4 (5da689c313, 2019-01-14)
- problem not reproduced on Windows 10, Inkscape 1.0alpha (12c5988, 2019-01-17)"
1782553,2018-07-19 12:38:54 UTC,You may like relative coordinates feature. Keep looking at the bottom status bar - there are two sets of coordinates displayed. Now move your mouse and press space every now and then to see that one coordinate set is reset.
1782553,2018-07-20 07:18:48 UTC,Hi I should have  added this is the last stable V4.07 version of KiCad / PCBnew. Sorry about that.
1782558,2018-10-09 19:55:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782568,2018-07-19 15:18:17 UTC,https://github.com/mixxxdj/mixxx/pull/1753
1782577,2020-01-27 19:38:00 UTC,"With the env variable :
ENV DEBIAN_FRONTEND noninteractive"
1782577,2020-12-17 20:33:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782577,2018-07-19 13:58:02 UTC,"I have found a work around, when I put in my Dockerfile"
1782579,2018-08-25 00:23:04 UTC,"I just clicked NM dialog on main screen on a daily image & noticed the 'connection info' & 'edit connections' boxes appear; xterm is not installed, so the issue has been fixed I believe."
1782579,2018-08-25 00:37:55 UTC,"Chris, the issue of those menu options failing to work correctly because
(A) they were hardcoded to use xterm to open nmtui and (B) because xterm
wasn't installed and (C) because the default window size for qterminal
was too small has been solved for days. See
https://bugs.launchpad.net/ubuntu/+source/nm-tray/+bug/1786978 for more
on that bug and the package versions that fixed them."
1782579,2019-07-10 00:48:12 UTC,"Though the bug as described is still relevant, the workaround intended for Lubuntu 19.10 has been implemented— use GTK:"
1782581,2020-06-05 18:39:42 UTC,"Ubuntu 18.04 LTS clean install
SANE & XSANE latest versions as of 05Jun2020"
1782581,2020-06-05 18:40:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782582,2018-07-19 15:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782597,2018-09-14 02:46:42 UTC,"Unforunately, I believe this is an issue with the MOTU Ultralite AVB. Several people are actively trying to solve it over here: https://linuxmusicians.com/viewtopic.php?f=6&t=18046"
1782597,2020-01-28 00:43:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782604,2018-07-23 03:17:13 UTC,"please let us know whether it's  fixed or not , thanks"
1782604,2018-07-27 11:02:43 UTC,"Change abandoned by Graham Hayes (<email address hidden>) on branch: master
Review: https://review.openstack.org/584031
Reason: New releases of zVMCloudConnector have fixed the issue, so abandoning this review"
1782604,2018-07-23 13:30:38 UTC,"Change abandoned by Graham Hayes (<email address hidden>) on branch: master
Review: https://review.openstack.org/584014"
1782604,2018-07-23 11:10:21 UTC,"This is fixed in Designate's gate now - and when https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/420126 lands, it will ensure it doesn't happen when py37 is introduced. Thanks for the quick turn around!"
1782604,2018-07-22 13:01:43 UTC,This is being worked in nova via https://review.openstack.org/#/c/584031/
1782604,2018-07-24 01:54:51 UTC,"Thanks for your info and sorry for bring trouble to you
we will land/release the patch after some review and test :)"
1782604,2018-07-20 01:57:05 UTC,"Thanks for reporting this, we will have a new release soon and it should solve the problem"
1782604,2018-07-19 16:19:09 UTC,http://paste.openstack.org/show/726284/ (for when the logs get rotated)
1782604,2018-07-20 02:26:47 UTC,https://pypi.org/project/zVMCloudConnector/
1782604,2018-07-19 17:46:30 UTC,FYI there's a pull request to fix this in python-zvm-sdk: https://github.com/mfcloud/python-zvm-sdk/pull/7
1782604,2018-07-19 17:07:32 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/419771 will temporarily fix it (until we need py37 which is probably happening in Stein)
1782608,2018-07-25 09:17:39 UTC,I think r8169 is the correct driver.
1782608,2019-02-05 20:08:06 UTC,but surely with this ethernet won't going anywhere...
1782608,2019-05-07 21:58:50 UTC,"Finally got around to upgrading to 18.04. I installed a fresh hard drive, installed Kubuntu 18.04.1, and 8169 driver was chosen."
1782608,2019-05-08 12:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782608,2019-07-08 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1782608,2020-03-15 05:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782608,2020-05-15 04:17:16 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1782608,2019-05-08 12:19:27 UTC,"This bug has nothing to do with linux-firmware, changing to affect linux."
1782610,2018-07-19 16:42:38 UTC,Hum I mean the software freeze ...
1782611,2018-07-19 16:48:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584024"
1782612,2018-07-24 12:57:21 UTC,"Hi David,"
1782613,2018-07-26 13:57:31 UTC,Users don't switch DE often. It's a cache - if it's removed not too much of deal.
1782613,2018-07-26 13:56:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782613,2018-07-20 02:17:35 UTC,"I'm not sure this should be done in kio-extras. As I mentioned in https://bugs.kde.org/show_bug.cgi?id=79943, the thumbnails are part of a cross-desktop spec, so it seems inappropriate for any particular desktop environment to do the cleanup on its own."
1782613,2018-07-20 00:37:29 UTC,This is the wrong project for that bug. The KDE thumbnailer has nothing to do with this thumbnailer (which does enforce a size limit).
1782616,2018-07-19 17:40:41 UTC,"possibly some relevant info, from journalctl -o short-monotonic"
1782616,2018-07-19 19:16:22 UTC,"Was maybe the proxy env missing (or ignored) that is neede don Diamond?
Still a bug to block the crit chain for 40s if that is the case, but maybe a thought to check."
1782616,2018-07-19 19:23:51 UTC,"Right.
So we think this was actually just lack of external connection from the system.
This is still an issue though.  There is no requirement on internet connectivity for running a container ('lxc launch ubuntu-daily:bionic')."
1782616,2018-07-19 20:39:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782625,2018-07-19 18:54:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584067"
1782625,2018-07-19 18:58:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584069"
1782625,2018-07-20 17:07:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584447"
1782625,2018-08-17 08:06:31 UTC,"Reviewed:  https://review.openstack.org/584067
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_neutron/commit/?id=bc9e068f6c155d354ebecfaac811927ae333456b
Submitter: Zuul
Branch:    master"
1782625,2018-10-06 23:06:34 UTC,"Reviewed:  https://review.openstack.org/584447
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-plugins/commit/?id=bc3e3b074cda33397979a9cb26f4bec866f044cd
Submitter: Zuul
Branch:    master"
1782625,2018-11-29 19:23:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620994"
1782625,2018-12-03 06:37:41 UTC,"Reviewed:  https://review.openstack.org/584069
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=9ef46ba5ef41ba03e9ca5107274cec3bf456fc3f
Submitter: Zuul
Branch:    master"
1782625,2018-12-07 21:59:09 UTC,"Reviewed:  https://review.openstack.org/620994
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_neutron/commit/?id=b87e5b1f6147a431a66786a3c9a724904d109077
Submitter: Zuul
Branch:    master"
1782629,2020-08-17 02:05:44 UTC,I just mean the code had changed. Thanks for the update.
1782629,2020-08-14 14:23:38 UTC,"To clarify, the original issue (not being able to move subsurface) is still present on an up-to-date Ubuntu 16.04. The patch is for the original debian source package at http://archive.ubuntu.com/ubuntu/pool/universe/m/mutter/mutter_3.18.3.orig.tar.xz and is also still valid."
1782629,2020-08-14 14:02:58 UTC,"Well the patch is for mutter 3.18.3, so it will still be needed on this version."
1782629,2020-08-13 06:58:22 UTC,I can't tell from the current code (which is different) if this fix is still needed. Is it?
1782629,2018-07-19 20:25:20 UTC,"The attachment ""wl_shell_fix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1782634,2018-07-26 05:17:40 UTC,"Hi,"
1782634,2018-07-26 06:44:30 UTC,"Hi,"
1782634,2018-08-03 10:24:34 UTC,"Hi,"
1782634,2018-09-06 20:24:06 UTC,"Hi,"
1782634,2018-09-07 17:53:51 UTC,Now I tried also with hp-scan and noticed that with hp-scan it even did not generate a picture at all.
1782639,2018-07-23 19:21:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782639,2018-07-23 19:44:47 UTC,This acutally seems to be an issue with the xchat package and flwm's trigger trips over xchat's malformed .desktop file. The relevant line from the DpkgTerminalLog.txt is:
1782642,2018-08-06 19:06:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782644,2019-11-01 12:16:02 UTC,Not sure if this is still an issue?  Is this on new deployments or upgrades?
1782644,2019-08-01 08:53:53 UTC,@sahid
1782644,2019-08-01 08:49:36 UTC,@sahid
1782644,2019-07-30 10:21:50 UTC,"Looks like a valid issue even if I'm not able yet to find where do we handle privileges in charmhelper, can you indicate the version used?"
1782644,2019-07-30 02:17:32 UTC,"Hello, the customer faced the similar issue."
1782644,2018-07-20 20:32:31 UTC,"Reviewed:  https://review.openstack.org/584391
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=25aa3d1b5a3047d7908590369cb5e0c8f2dd0cb5
Submitter: Zuul
Branch:    master"
1782644,2018-07-20 15:51:49 UTC,Note that this is with the master branch charms - stable charms are just fine.
1782646,2018-07-19 20:45:30 UTC,"I thought it might be useful to attach my shutter settings. I created profile ""default"", so I'm attaching ~/.shutter/profiles/default.xml."
1782646,2019-03-26 14:39:42 UTC,Found myself affected by this bug too. I made a quick fix that you can apply by modifying /usr/share/shutter/resources/system/upload_plugins/upload/Imgur.pm file. You can find patch file attached.
1782646,2019-03-26 16:24:13 UTC,"The attachment ""Imgur.pm.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1782646,2019-06-10 16:52:01 UTC,"Patch applied in rev. 1305, thanks!"
1782647,2019-03-21 20:16:30 UTC,This issue was fixed in the openstack/designate 8.0.0.0rc1 release candidate.
1782647,2019-01-07 14:14:06 UTC,I'm unable to drop Python from being affected but I've updated the upstream issue to note that it can be closed.
1782647,2019-01-07 13:44:40 UTC,This was narrowed down to eventlet [1] therefore I'm dropping Python from affected projects.
1782647,2018-10-24 06:28:46 UTC,"Reviewed:  https://review.openstack.org/586336
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=72e4e13d8ee681cae5564ef538a44ddd96ca586c
Submitter: Zuul
Branch:    master"
1782647,2018-07-26 19:58:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586336"
1782647,2018-07-24 17:41:34 UTC,I've also opened the following issue for eventlet: https://github.com/eventlet/eventlet/issues/508
1782647,2018-07-24 17:32:11 UTC,This has further been narrowed down to a conflict with eventlet monkeypatching of standard library thread modules. It recreates with: https://bugs.python.org/file47709/bpo34173-recreate.py.
1782647,2018-07-25 19:07:38 UTC,"Swapping out ThreadPoolExecutor with GreenThreadPoolExecutor gets rid of the deadlock. Joshua Harlow suggests [1]: If you have the ability to specify which executor your code is using, and you are running under eventlet I'd give preference to the green thread pool executor under that situation (and if not running under eventlet then prefer the threadpool executor variant)."
1782647,2018-07-20 19:33:50 UTC,It seems this may be a py3.7 bug so I've opened: https://bugs.python.org/issue34173
1782647,2018-07-20 19:04:58 UTC,"This appears to be the line that causes the difference. If I revert back to using queue.Queue() in /usr/lib/python3.7/concurrent/futures/thread.py, the py37 tests run successfully without any issues."
1782647,2018-07-24 13:28:18 UTC,Karthikeyan Singaravelan (xtreak) has provided a smaller testcase https://bugs.python.org/file47707/bpo34173.py that doesn't deadlock. I'm not sure what the difference is.
1782647,2018-07-20 18:19:49 UTC,"I was going to add heat to this bug as well, but they've moved their bugs to storyboard. That's not that convenient. Anyway heat is affected too if you update tox with py37 target and run tests."
1782647,2018-07-20 18:09:30 UTC,"This could be an issue with py3.7 itself, still not sure, but adding python3.7 Ubuntu package as an affected project."
1782647,2018-07-20 18:05:16 UTC,"Attaching a patch, just to show the delta between:"
1782647,2018-07-20 18:01:20 UTC,Ok making some headway. If I:
1782647,2018-07-20 16:55:43 UTC,Just tested with py3.6 and the test runs successfully without any issues.
1782648,2019-03-04 17:03:51 UTC,"I get the same behaviour as OP - I'm using pike, also deployed with kolla-ansible.
Is there any workaround known ?"
1782648,2019-01-07 09:43:49 UTC,"Interestingly, OSM seems to be able to create a port pair just fine. Not exactly sure what the difference is..."
1782648,2019-01-07 09:37:59 UTC,I run into the same error with an RDO install. Does a workaround exist?
1782650,2019-12-31 15:38:01 UTC,Had the same issue after upgrading from 14.04 to 16.04.
1782650,2019-11-25 21:19:01 UTC,"This seems to be the same / similar issue, discussed upstream:"
1782650,2019-05-28 20:26:31 UTC,Here's the full workaround:
1782650,2019-04-11 22:54:52 UTC,@legovini
1782650,2019-04-11 08:20:13 UTC,"Hello Stefan,"
1782650,2020-01-17 08:00:38 UTC,From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914489#12
1782650,2019-04-10 15:19:43 UTC,"I would recommend a downgrade to the version shipped with Ubuntu 14.04. (check_nrpe 2.15)
I replaced check_nrpe and now I can monitor successfully again. Better a bad encryption than no encryption at all..."
1782650,2019-03-29 18:11:18 UTC,"@jessegoodier, you will need to change your Nagios checks from check_nrpe to check_nrpe_nossl and tell the old target NRPE server to run without SSL. This can be done by setting DAEMON_OPTS=""-n"" in /etc/default/nagios-nrpe-server."
1782650,2019-03-29 17:55:54 UTC,Does anyone have instructions for disabling TLS for nagios?
1782650,2019-02-15 17:30:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782650,2019-02-19 14:09:21 UTC,Thanks for reporting this bug and troubleshooting it this far. It looks like a real issue and we have added it to the server team backlog. Maybe there could be an ssl option to have the bionic client accept the smaller DH key.
1782650,2019-02-15 18:17:08 UTC,It seems the Bionic's OpenSSL version will always reject the small DH params proposed by the Xenial side so the only workaround I can think of for now is to disable TLS on both sides.
1782650,2019-02-15 17:57:36 UTC,It looks like the Bionic TLS client rejects the server picked DH param (512 bits) as being too small. We can see this at work in the attached pcap where 172.22.30.2 is Xenial/TLS server/NRPE server and 172.22.30.66 is the Bionic/TLS client/check_nrpe.
1782650,2018-12-07 17:58:55 UTC,I've just been bitten by this one and it's practically a show-stopper. I've tried all the suggestions I can find without success and the idea of building nrpe server for multiple other platforms does not seem like any kind of solution. I guess I'll need to downgrade check_nrpe.
1782650,2018-10-26 19:20:34 UTC,I've done some more digging.
1782650,2018-10-26 11:16:06 UTC,"Hi,"
1782650,2018-09-20 04:17:20 UTC,[Expired for nagios-nrpe (Ubuntu) because there has been no activity for 60 days.]
1782650,2018-07-20 07:11:16 UTC,"Hi,
I'm certainly not a nagios-nrpe expert but isn't that just (1) of [1].
to quote ""Newer versions of NRPE are usually not backward compatible with older versions.""
I expected something like it and search engines immediately returned just such cases."
1782650,2019-03-04 18:08:12 UTC,"I'll add another ""me too"" on this bug since I had forgotten about the NRPE incompatibility and broke a bunch of nagios checks by upgrading our production nagios system to 18.04."
1782653,2018-07-24 18:18:47 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1782653,2018-07-26 16:40:46 UTC,"There is a Solution now, a great guy at kenel.org fixed it:"
1782653,2018-07-25 16:51:51 UTC,i tried kernel 4.17.2 and 4.18.RC6 on Ubuntu but the touchpad does not work.
1782653,2018-07-22 07:02:24 UTC,"There are reports [1,2] about Clock Speed of i2c bus on cannon-lake cpus that could be the reason at least for other devices so I tried with 180000000 and 216000000 but it did not help..."
1782653,2018-07-22 01:32:53 UTC,"journalctl gives the following output, there is an additional descriptor"
1782653,2018-07-19 21:37:33 UTC,apport information
1782653,2018-07-19 21:37:31 UTC,apport information
1782653,2018-07-19 21:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782655,2018-07-23 11:19:30 UTC,The recovery_target_time in recovery.conf was set to an invalid value:
1782655,2018-07-23 11:20:44 UTC,"Per example command line, the date PostgreSQL failed to parse was user input. So I think this bug is about adding validation and fixing documentation."
1782655,2018-07-23 11:33:07 UTC,"And reporting a failure if we can detect that, rather than a success."
1782663,2021-02-17 17:08:50 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1782663,2018-08-30 04:55:11 UTC,"Reviewed:  https://review.openstack.org/584154
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=54ec954a1eb490b4577cb6b3f971b4bac4c2355f
Submitter: Zuul
Branch:    master"
1782663,2018-07-20 15:34:16 UTC,"That's not what the release notes say: ""instack-undercloud is deprecated in Rocky cycle and is replaced by the containerized undercloud efforts in python-tripleoclient."""
1782663,2018-07-20 07:06:10 UTC,"Note, the upgrade impact of the change is covered in upgrade tasks http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/docker/services/ironic-conductor.yaml#n204"
1782663,2018-07-20 06:45:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/584245"
1782663,2018-07-20 06:34:06 UTC,"Note, instack undercloud deployments will not be supported for Rocky. For this milestone-3, we're doing the final steps for switching all CI jobs (but one) to containerized UC."
1782663,2018-07-19 22:48:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/584154"
1782663,2018-07-20 07:05:51 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/584245
Reason: it is already automated in upgrade tasks http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/docker/services/ironic-conductor.yaml#n204"
1782678,2018-08-25 08:39:10 UTC,"same problem here for me.
Ubuntu 18.04.1 LTS x86_64
4.15.0-33-generic"
1782679,2019-09-29 09:31:32 UTC,"Any progress here? systemd-resolved has plus that it's integrated with DNS options from systemd-networkd, but for end user it has many issues, especially related to DNSSEC."
1782679,2018-07-20 01:32:54 UTC,"Note also that upstream claim that ""resolved is not supposed to be a DNS server""[1], so I'm a bit confused as to why Ubuntu is configured to pass every DNS query through it. Do I need to reconfigure something?"
1782679,2018-08-29 15:24:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782679,2018-08-29 16:48:46 UTC,We seem to hit the same problem here.
1782680,2020-02-20 17:37:10 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/700807
Reason: Please resubmit to master if still needed there, then backport once merged."
1782680,2019-12-31 13:07:53 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/700807"
1782680,2018-07-20 02:57:11 UTC,"or by modifying /usr/share/openstack-tripleo-heat-templates/docker/services/cinder-common.yaml
add
======
          - /opt/emc/scaleio:/opt/emc/scaleio
          - /bin/emc/scaleio:/bin/emc/scaleio
======
to cinder_volume_volumes list_concat"
1782680,2018-07-20 09:47:00 UTC,below is a better way to do this:
1782693,2018-10-06 21:49:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782694,2018-07-20 05:18:51 UTC,Some investigation:
1782694,2018-12-03 06:01:17 UTC,"https://review.gerrithub.io/c/mfcloud/build-zvmsdk/+/435832 and
https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/435835"
1782694,2018-12-03 06:23:38 UTC,Remove the error output and some warning still there... but very low priority now
1782696,2018-08-08 02:11:19 UTC,">>pci_requests in it - does the request spec exists for this instance?
from migration API, it does not.
"
1782696,2020-06-29 19:44:11 UTC,setting this back to invalid.
1782696,2020-05-14 07:50:25 UTC,"Since it looks like problem has not been resolved, and, I believe, has been confirmed by multiple operators, I'll change status to ""Confirmed"" for now."
1782696,2020-05-14 07:47:17 UTC,I can confirm that the issue very similar to described above still persist in nova 20.0.0.
1782696,2020-04-24 13:51:20 UTC,The same story - pci device on one host in the AZ. Create instance with flavor containing pci_passthrough property working good. But when resizing instance to that flavor - seems the pcipassthroughfilter not working in that case and some other host throws error nova.exception.PciRequestAliasNotDefined: PCI alias nvme is not defined.
1782696,2019-06-20 18:49:48 UTC,"We don't have a clear reproducer of the issue so we don't really know what's going on here, and haven't had any replies in a long time so I'm going to mark this as invalid."
1782696,2019-06-20 18:48:50 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/588455
Reason: No updates on the review in a long time so I'm going to abandon this."
1782696,2018-08-08 02:25:23 UTC,maybe following 2 lines code need be change in some way:
1782696,2018-08-03 07:23:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588455"
1782696,2018-07-31 08:31:10 UTC,"this patch does fix the problem:
http://paste.openstack.org/show/726559/"
1782696,2018-07-25 02:25:53 UTC,@Chris Friesen  i think this would fix this. it's what i'm talk about.
1782696,2018-07-24 22:03:49 UTC,"I should explain that the above is a fix from some time ago, so I'm curious if it's still applicable now."
1782696,2018-07-24 21:55:18 UTC,Does this fix the behaviour?  http://paste.openstack.org/show/726559/
1782696,2018-07-24 20:44:28 UTC,"> the problem is while do resize/migration, API layer not load PCI information into instance object.
"
1782696,2018-07-23 06:15:29 UTC,"@Feng Wen, i did. but thanks for remind, i do forgot include pci configuration in the conductor service. the failure information updated."
1782696,2018-07-20 06:53:01 UTC,"Have you configured PciPassthroughFilter in schduler.enabled_filters? The default is not configured this filter, if you need PCI scheduling, you should configure it."
1782696,2018-08-08 00:24:54 UTC,This still doesn't make sense to me. The API looks up the request spec which should have the pci_requests in it - does the request spec exists for this instance?
1782698,2018-07-25 08:36:03 UTC,fixed in upstream kernel 4.18-rc6
1782698,2018-07-20 06:00:06 UTC,This change was made by a bot.
1782698,2018-07-24 18:19:25 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1782698,2018-07-25 08:32:02 UTC,"Tested with kernel 4.18-rc6-generic-amd64 and all worked fine.
1. 100Mbit switch test - pass
2. 1000Mbit switch test - pass
3. No ipv6 test - pass
4. ipv6 enabled test - pass
5. No Network Manager static ipv4 test - pass
6. No Network Manager dhcp ipv4 test - pass
7. Network Manager enabled test - pass
8. HotPlug\HotUnplug test - pass"
1782703,2020-01-05 11:02:25 UTC,"I also get this on a fresh install of Ubuntu 19.10 on one of the two machines I use (laptop with wifi is fine, desktop with wired connection is buggy, I used the same USB for install). My internet connection is fine, but some of the websites I want to get on are blocked (e.g. mobile banking, lastpass, etc.) on the affected desktop. I had minor issues on the laptop but changed them by switching the repositories. No such luck on the desktop. The network icon has a question mark over it, but when I open the network dialog, it says Wired Connected -1000Mb/s.
I get this error message persistently in my Ubuntu Software:"
1782703,2019-05-12 10:35:06 UTC,Could someone having the issue report it upstream on https://gitlab.gnome.org/GNOME/gnome-software/issues/ ?
1782703,2020-06-29 03:56:09 UTC,"I began having the identical symptoms described several weeks ago. Multiple connectivity error message windows at the *initial* startup of GNOME-software. This occurs on waking from suspend, and not from restart or shutdown-start. GNOME-software is attempting to update its listings in the background before networking is restored upon awake-after-suspend. Trivial, but an annoyance nontheless, because this was not happening before (that I remember, anyway.)"
1782703,2020-03-17 15:14:38 UTC,"Can we have a status update on this bug ?
I'm having quite frequently and I have to the 3 popups everytime."
1782703,2019-05-11 22:57:19 UTC,"I also get this on a fresh install of 19.04. I checked and my internet connection is fine, I get this every time. I tried the URL in a browser and it works fine. I tried using wget and it also works fine. There error msg is a bit different though:"
1782703,2019-05-04 11:41:59 UTC,"I always get this error when accessing Ubuntu Software and I'm always connected so it definitely looks like a bug. It's also new, it was working well on the same computer and I started to get that when I reinstalled Ubuntu on the same one."
1782703,2018-12-02 02:11:57 UTC,"I have this with every launch of gnome-software.
It happens when I'm connected and can see extensions.gnome.org in the browser"
1782703,2018-12-02 02:10:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782703,2018-09-29 08:53:57 UTC,"I do believe I was connected, but it's possible I wasn't. (It's been some time so I don't exactly remember.)"
1782703,2018-09-27 10:04:22 UTC,Additional information:  this only seems to happen on first start up when there is no internet connection.  Subsequent start ups after it has contact the internet do not show this ugly error message.  It fails more gracefully.
1782703,2018-09-27 10:01:28 UTC,I saw this today while testing a Cosmic live session without access to the internet.
1782703,2018-12-02 02:16:02 UTC,"Ah, I see that the errors there are persistent - I never clicked the x to close them, so they never went away even though the problem had long since ceased."
1782709,2020-12-18 05:55:12 UTC,"same issue, upgrade systemd cause network outage about 5 second,"
1782709,2019-03-13 19:49:22 UTC,"I recently installed a fresh system with 18.04 as well and have experienced this exact issue when attempting to ""apt dist-upgrade"" from ssh.  In the two instances where systemd was being updated (a few weeks ago and today), my ssh connection was dropped and I'm unable to re-connect to the server.  I started the upgrade from a screen session this time and will investigate further when I can get to the console this evening."
1782709,2019-03-17 19:40:21 UTC,"Just happened to me too:
root@gw:/etc# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  eatmydata libeatmydata1 python3-blinker python3-jinja2 python3-json-pointer python3-jsonpatch python3-jsonschema python3-jwt python3-markupsafe python3-oauthlib
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  apport busybox-initramfs busybox-static docker.io initramfs-tools initramfs-tools-bin initramfs-tools-core landscape-common libidn11 libnss-systemd libpam-modules libpam-modules-bin libpam-runtime libpam-systemd libpam0g libpci3 libseccomp2 libsystemd0
  libudev1 libx11-6 libx11-data libxcb1 pciutils python3-apport python3-gi python3-problem-report systemd systemd-sysv udev unattended-upgrades
30 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 54.0 MB of archives.
After this operation, 37.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam0g amd64 1.1.8-3.6ubuntu2.18.04.1 [55.1 kB]
Get:2 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-modules-bin amd64 1.1.8-3.6ubuntu2.18.04.1 [36.7 kB]
Get:3 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-modules amd64 1.1.8-3.6ubuntu2.18.04.1 [242 kB]
Get:4 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.15 [105 kB]
Get:5 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.15 [205 kB]
Get:6 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.15 [108 kB]
Get:7 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.15 [2,899 kB]
Get:8 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 udev amd64 237-3ubuntu10.15 [1,100 kB]
Get:9 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libudev1 amd64 237-3ubuntu10.15 [54.2 kB]
Get:10 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-runtime all 1.1.8-3.6ubuntu2.18.04.1 [37.1 kB]
Get:11 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 initramfs-tools all 0.130ubuntu3.7 [9,592 B]
Get:12 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 initramfs-tools-core all 0.130ubuntu3.7 [48.1 kB]
Get:13 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 initramfs-tools-bin amd64 0.130ubuntu3.7 [12.8 kB]
Get:14 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 busybox-initramfs amd64 1:1.27.2-2ubuntu3.1 [166 kB]
Get:15 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd-sysv amd64 237-3ubuntu10.15 [12.0 kB]
Get:16 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libseccomp2 amd64 2.3.1-2.1ubuntu4.1 [39.1 kB]
Get:17 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libidn11 amd64 1.33-2.1ubuntu1.1 [45.9 kB]
Get:18 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-gi amd64 3.26.1-2ubuntu1 [153 kB]
Get:19 http://hu.archiv..."
1782709,2019-03-17 19:45:47 UTC,"And logging in on the console the apt process was waiting on for some answers:
ps aux | grep apt
root     13335  0.1  6.6 116500 67388 pts/1    S+   19:30   0:00 apt upgrade
root     15048  0.0  0.3  11856  3628 pts/3    S+   19:31   0:00 /bin/bash /usr/bin/ucf --three-way --debconf-ok /usr/share/unattended-upgrades/20auto-upgrades-disabled /etc/apt/apt.conf.d/20auto-upgrades
root     15090  0.0  0.4  24460  4976 pts/3    S+   19:31   0:00 whiptail --backtitle Package configuration --title Configuring unattended-upgrades --output-fd 11 --nocancel --default-item keep the local version currently installed --menu A new version (/usr/share/unattended-upgrades/20auto-upgrades-disabled) of configuration file /etc/apt/apt.conf.d/20auto-upgrades is available, but the version installed currently has been locally modified.  What do you want to do about modified configuration file 20auto-upgrades? 17 211 7 -- install the package maintainer's version  keep the local version currently installed  show the differences between the versions  show a side-by-side difference between the versions  show a 3-way difference between available versions  do a 3-way merge between available versions  start a new shell to examine the situation
root     16771  0.0  0.1  13136  1148 tty1     S+   19:41   0:00 grep --color=auto apt"
1782709,2019-03-17 19:47:35 UTC,"I could only resolve the ssh issue with killing the apt process, and restarted networking.
This is a pretty bad issue imho. Upgrading packages through ssh should not disconnect the session, but even if it is, upgrading the systemd package should not result in not being able to log back in ever again!"
1782709,2019-04-05 13:48:03 UTC,"I'd like to also confirm this bug, which we've been experiencing for the past few months since we first setup an 18.04 image for our deployment portal."
1782709,2019-03-17 19:57:21 UTC,"Also I see this in the logs, but maybe not related (why can't I edit my comments?)"
1782709,2019-03-17 21:15:04 UTC,"Some more info:
 - The machine is a Virtualbox ubuntu bionic, and I have a snapshot before the upgrade, so I can reproduce it
 - I'm using ifconfig instead of netplan, because I need a ppp interface (for pppoe)
 - I have an /etc/network/interfaces file
 - it seems that the interface through which I'm using ssh loses it's IP address (defined in the interfaces file as static)
 - I also did these after installing bionic:
""systemctl disable systemd-networkd-wait-online.service
systemctl mask systemd-networkd-wait-online.service"" because it was holding up the boot process for a long period"
1782709,2018-07-25 03:58:12 UTC,"Today, just another ""apt-get upgrade"":"
1782709,2019-06-12 23:25:29 UTC,Can confirm the same behaviour on my systems too. Updating systemd recently caused the entire routing table to be dropped (I had console access and was able to confirm no routes - not even loopback worked). In normal operation I see:
1782709,2019-03-17 19:55:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782709,2018-07-24 19:13:15 UTC,"Do you have a way to reproduce this issue, or was it a one time event?"
1782709,2018-07-20 07:32:43 UTC,I examined /var/log/dpkg.log. There is no pause in there. The complete upgrade process looks pretty normal to my. So I guess it is just a network configuration issue during the upgrade that prevented my terminal session from getting updated.
1782709,2018-07-20 07:16:40 UTC,apport information
1782709,2018-07-20 07:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782709,2018-07-20 07:14:34 UTC,"root@samson:~# apport-collect 1782709
ERROR: The python3-launchpadlib package is not installed. This functionality is not available."
1782709,2018-07-20 07:16:31 UTC,apport information
1782709,2018-07-20 07:16:33 UTC,apport information
1782709,2018-07-20 07:16:34 UTC,apport information
1782709,2018-07-20 07:16:32 UTC,apport information
1782709,2018-07-20 07:16:36 UTC,apport information
1782709,2018-07-20 07:16:37 UTC,apport information
1782709,2018-07-20 07:16:38 UTC,apport information
1782709,2018-07-20 07:16:39 UTC,apport information
1782709,2018-07-20 07:16:35 UTC,apport information
1782714,2018-09-27 06:03:10 UTC,Hi!
1782714,2020-05-19 11:10:53 UTC,I'm removing Nova from the bug as it seems from the comments this is a Cinder issue.
1782714,2018-11-07 18:38:53 UTC,"Created a bug for the ""ro"" issue: https://bugs.launchpad.net/cinder/+bug/1802155"
1782714,2018-11-07 16:44:08 UTC,"Viktor, as you can see, we don't really lose the metadata, the ""rw"" attribute from the connection is still present after the migration, it's just in some other place (since now we can do multi-attach).  So this is not really a bug."
1782714,2018-09-27 06:03:37 UTC,"And if I change attach_mode value (e.g. rw -> ro directly into database) and make live migration, the attach_mode is reset back to rw:"
1782714,2018-09-26 17:12:02 UTC,"@Viktor, are you able to answer Gorka's questions?"
1782714,2018-07-24 20:35:15 UTC,Adding cinder since cinder controls the volume metadata and nova shouldn't be changing anything during live migration with respect to the attached_mode.
1782714,2018-09-19 17:20:33 UTC,I think this could be related to how things are seen now with the multi-attach feature.
1782714,2018-07-25 06:36:54 UTC,And here are the volume details from the time when both attachments exist during live migration (metadata is still OK at this point):
1782714,2018-07-25 06:12:16 UTC,It seems that new attachment details are OK but in the volume details metadata is lost:
1782714,2018-07-24 20:39:01 UTC,"From the volume details itself, there is an attachments entry which would have the attachment_id for each attachment to the volume, which you could use to get the attachment detail information in the attachments API."
1782714,2018-07-24 20:37:55 UTC,"Note the ""Attached to cirros-01 on /dev/vdb Attached to cirros-01 on /dev/vdb"" during the live migration. That's probably while the volume has 2 attachments to the same server, one on the source host and one on the destination host. My guess is the attached_mode is lost during the creation/update of the 2nd attachment for the destination host."
1782714,2018-09-19 17:26:34 UTC,"If that is the case, could you try with a volume that has a different attached_mode?  As I believe we may have a bug there."
1782716,2019-08-23 06:31:08 UTC,"Seeing the same on Ubuntu 18.04.3 with the HWE kernel, 5.0.0-25-generic"
1782716,2019-08-21 08:54:12 UTC,I have similar error on matebook D: Ryzen + AMD GPU:
1782716,2018-11-08 20:36:30 UTC,Reproduced on Fedora (with kernel 4.18.16-300.fc29.x86_64).
1782716,2018-07-30 03:57:02 UTC,With -rc7:
1782716,2018-07-30 04:46:15 UTC,Reproduced with 4.17-rc7
1782716,2018-07-24 16:58:09 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1782716,2018-07-20 07:36:02 UTC,"After that, it fails to recover:"
1782716,2018-07-20 07:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782716,2018-07-30 03:24:07 UTC,With upstream kernels I get this (and a frozen desktop):
1782717,2018-07-20 14:26:46 UTC,Same issue here:
1782717,2018-07-20 14:53:49 UTC,See line 5 in https://pastebin.com/50qfZexx
1782717,2018-07-23 08:11:46 UTC,Thanks Sean!
1782719,2019-08-22 06:51:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782719,2019-08-22 07:18:18 UTC,I have not exactly the same problem but it is probably related.
1782725,2018-11-10 21:45:30 UTC,Cross-linking the referenced patch and corresponding review:
1782725,2020-07-15 01:39:38 UTC,"I'm fairly sure these restarts are not needed at all. The only note I can find is that if a process was started before the apparmor kernel module was reloaded, you would need to restart it for apparmor to track it."
1782727,2019-06-28 08:30:55 UTC,"As per Kamal's comment, marking this as ""Won't Fix"" until any customer asks for this."
1782728,2019-06-28 08:32:32 UTC,"As per Kamal's comment, marking this as ""Won't Fix"" until any customer asks for this."
1782735,2018-07-20 10:44:52 UTC,Attaching debdiff
1782735,2018-07-27 16:20:17 UTC,"Generally, the SRU team prefers that the debian/ packaging be changed as minimally as possible to not introduce regressions and make the diffs easier to read. In other words, don't run wrap-and-sort. However, I think I'm still willing to sponsor this update for you to bionic."
1782735,2018-07-28 10:21:37 UTC,"Hi Jeremy,"
1782735,2018-07-31 17:45:54 UTC,Thanks. I have uploaded this to the bionic-proposed queue. It will need to be manually approved by a member of the SRU team before it will be available for testing.
1782735,2018-08-13 08:34:02 UTC,Some of the bugs that are on the changelog of this SRU need SRU template information filled out. Thank you!
1782735,2018-08-15 15:58:57 UTC,"An upload of catfish to bionic-proposed has been rejected from the upload queue for the following reason: ""bugs linked in the changelog do not have SRU templates and it's unclear they should; https://bugs.launchpad.net/ubuntu/bionic/+source/catfish/+bug/1646714/comments/6""."
1782745,2018-07-25 23:02:30 UTC,"The ""lease manager stopped"" message in the unit log is an error response from the API on the controller. There should be log messages with more specific information about why that worker has stopped in the controller's log - could you send those?"
1782745,2018-07-26 14:47:48 UTC,"Output of the ""juju debug-log -m controller"" command after finishing of a restore procedure."
1782745,2018-07-26 14:48:45 UTC,Full log. /var/log/juju/machine-x.log
1782745,2018-07-27 01:20:16 UTC,"Thanks - that has a lot more information about why the worker stopped, although I'm not clear on the underlying cause yet."
1782745,2018-08-01 12:31:04 UTC,"Christian, thanks for your explanation. Unfortunately, I cannot start working on the bug. At least not now. So if you need another logs let me know."
1782745,2019-06-25 02:53:18 UTC,"Since mongo has unexpectedly dropped a connection, without any additional explanation as to why, I'll have to mark this report as Incomplete. It is not related to leases or leadership despite flagged errors."
1782745,2019-08-24 04:17:29 UTC,[Expired for juju because there has been no activity for 60 days.]
1782755,2020-07-18 13:38:15 UTC,"The stable PPAs haven't been updated since the official version in the Ubuntu repo is already the latest stable release, but they'll be updated once there are new releases."
1782758,2019-09-18 12:38:15 UTC,"The problem has been fixed by commit (upstream): d90a10e2444b ""fsnotify: Fix fsnotify_mark_connector race"""
1782764,2021-02-18 21:00:22 UTC,"Today I ran into something similar, but we have a larger user base that uses different (public and self-hosted) platforms, so just one URL won't be enough. I thought about a more general solution to the problem."
1782785,2018-07-31 22:34:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782788,2018-07-22 03:26:49 UTC,"I reported the ""Latest changes"" block at bug 1782955 as they should be separate."
1782788,2018-07-24 09:40:02 UTC,"""why would you want to configure the watched pages block since you determine which pages to watch?"""
1782788,2018-07-26 14:52:36 UTC,"Thanks, Sam."
1782788,2018-08-02 15:19:47 UTC,"Hi Kristina,"
1782788,2018-08-05 19:08:31 UTC,"Sam, the screenshot would be great."
1782788,2018-08-07 09:22:47 UTC,"Hi Kristina,"
1782788,2018-08-09 02:07:01 UTC,"Thanks for the dashboard page, Sam. Yes, she has a lot on her watched pages."
1782789,2018-07-23 11:35:30 UTC,"Τελικά το https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig δουλεύει σε Linux,
αλλά ειδικά στο Ubuntu MATE γίνεται το εξής:"
1782789,2018-07-23 11:10:31 UTC,Fix committed στο https://git.launchpad.net/sch-scripts/commit/?id=4abde526467081ee01086775aeabb747f733ff9f
1782790,2018-07-25 16:04:10 UTC,This issue was fixed in the openstack/python-mistralclient 3.7.0 release.
1782791,2018-10-09 11:20:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782791,2018-10-09 13:47:59 UTC,"I have fixed my issue locally by downloading the source, then opening
src/core/sipe-appshare-remmina.c"
1782791,2019-09-18 17:22:09 UTC,Is this still open? I'm facing this same Issue with linux mint 19.1
1782791,2019-09-18 18:04:34 UTC,"I assume it is - my fix is in the above comment. Luckily my company had moved away from Skype for Business so I no longer have to use it, so I can't confirm if it is still a bug for me."
1782802,2018-08-06 02:30:35 UTC,"I'm not sure I see a path to switching away from klibc-utils completely. As far as I can tell, every upload of initramfs-tools ever has still invoked ipconfig for some arguments."
1782802,2018-08-06 17:50:35 UTC,Which cases were still using ipconfig and why?  Can you point to the exact upload you're looking at?
1782802,2018-08-06 21:48:11 UTC,"Well there are quite a few uploads to choose from, but this one https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/scripts/functions?id=import/0.125ubuntu6#n339 is about the least ""ipconfig-y"" and it still calls it sometimes..."
1782805,2019-06-20 20:22:47 UTC,"@Ian, I merged your first cvpcb patch into the 5.1 branch.  Thanks."
1782805,2019-06-20 20:23:23 UTC,Fix committed in https://git.launchpad.net/kicad/commit/?id=c951ca6f47f391dc8a904ff7ecb771c03d50fdf8
1782813,2018-07-20 18:00:06 UTC,This change was made by a bot.
1782813,2018-07-24 18:07:09 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1782813,2018-07-26 11:57:33 UTC,"I don't know exactly when it started since this is not my own computer, it's my wife's and she does not use it really often."
1782816,2019-11-22 15:01:38 UTC,"I thought it did auto-rotate.  In any case, it probably should."
1782816,2019-11-22 14:05:49 UTC,"Is there a downside to implementing an auto-rotate to put the pins on the top/bottom? We already auto mirror the pin between the left/right sides, so it would seem from a UI perspective if we automatically update it for one direction, we should automatically do it for the others (instead of requiring the users to do it)."
1782816,2019-11-24 11:00:14 UTC,"@Jeff, nope it only auto-mirrors between the left/right sides. It does not auto-rotate to the top/bottom when the mouse moves there."
1782816,2019-05-18 20:31:32 UTC,Sure it does.  You just need to rotate the pin.
1782816,2019-05-18 21:29:25 UTC,"@Jeff, this wasn't available before the modern toolset so I'll mark as Fix Committed instead."
1782829,2018-07-20 19:20:42 UTC,PS: I forgot to link to the palette file:
1782829,2020-03-21 20:41:33 UTC,Closing because INVALID: Not a bug. May be support request or spam.
1782837,2020-08-27 16:02:49 UTC,Additional comments  http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-08-27-15.01.log.html
1782837,2019-03-22 14:51:43 UTC,Goutham is this one yours? :)
1782840,2020-04-14 09:38:40 UTC,This issue was fixed in the openstack/glance 20.0.0.0b3 development milestone.
1782840,2018-07-20 21:57:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584530"
1782840,2020-04-07 19:29:45 UTC,"Reviewed:  https://review.opendev.org/584530
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=d2cc0dc5663657ae80550954269e19a6a8157501
Submitter: Zuul
Branch:    master"
1782842,2020-03-26 14:25:10 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1782843,2018-08-19 20:52:53 UTC,Please forward this issue to the Xfce bug tracker. Thanks.
1782844,2020-09-28 06:09:43 UTC,mentioned at : https://gitlab.com/inkscape/inbox/-/issues/479#note_413051142
1782846,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1782847,2019-03-22 14:50:21 UTC,Goutham is this your defect are you currently working on this? is it a wishlist item?
1782847,2019-03-28 17:01:48 UTC,Thanks for asking Jason. I've added this bug to the Denver/Project Technical Gathering Agenda: https://etherpad.openstack.org/p/manila-denver-train-ptg-planning
1782851,2018-07-24 12:17:15 UTC,tests ran successfully. marking as Fix Released.
1782851,2018-07-26 04:27:45 UTC,"we had https://pypi.org/project/zVMCloudConnector/ 1.2.3 out and should fixed this issue
but we don't know how to test it as we use linux and seems install py36 now
and we need wait for upper constraint to 1.2.3 in order to make it work?"
1782851,2018-07-25 02:16:05 UTC,"@Jay, sorry, we were told that py36 is the issue recently and we fixed that by using zVMConnector 1.2.2, and soon we are going to ship 1.2.3 in PyPI and that should fix your problem"
1782851,2018-07-24 13:26:13 UTC,"It's a bug that makes building Nova impossible on MacOS. And Nova is the only thing that zVMConnector is useful for. So, frankly, I think this bug belongs on Nova."
1782851,2018-07-24 11:36:53 UTC,This was apparently only fixed 5 days ago:
1782851,2018-07-24 12:46:39 UTC,"On MacOS, with Python 3.7 installed due to `brew install tox`'s pull-in of python3.7:"
1782851,2018-07-27 19:36:36 UTC,"Chen, what is the purpose of the version checking code here?"
1782851,2018-07-24 07:23:09 UTC,What version pf python did you use? 3.6 or 3.7?
1782851,2018-07-24 13:02:32 UTC,"This isn't a nova bug, it's a bug in the zvm sdk, so it should be routed through whatever issue tracker they have."
1782851,2018-07-30 02:39:35 UTC,"you are right, looks like we don't need keep them
and in 1.2.3 , we already remove py3 check and for py2 check, it's not urgent I guess
we will remove them and ship in next release... thanks"
1782856,2018-07-24 16:37:10 UTC,specifically -- https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/targethosts.html#configuring-the-storage
1782856,2019-10-11 12:54:56 UTC,I had the same problem.
1782856,2018-07-24 16:36:32 UTC,wishlist to add docs to explain that it's not just for logging :)
1782856,2018-07-21 11:23:31 UTC,">i thought /openstack is just for logging but something strange going on
"
1782856,2018-07-21 13:50:39 UTC,"Thanks Jakob,"
1782856,2018-07-21 01:22:11 UTC,I think i am royally screwed on production :(
1782856,2018-07-21 01:16:32 UTC,Why LXC container is almost empty here
1782857,2018-07-21 07:25:56 UTC,Thanks for your report.
1782857,2018-07-21 10:42:24 UTC,I couldn't find any way to burn using nautilus. Installed brasero to do the job. I hope I'm just overlooking the obvious.
1782857,2018-07-21 14:58:40 UTC,"Gunnar; I have an iMac with 18.04 desktop, and an old HP LapTop still with 17.10 desktop (will be updraded to 18.04 soon). 18.04 and 17.10 behave differently upon insertion of a writable CD/DVD, but neither behave as per the web page."
1782857,2020-07-06 19:59:26 UTC,This bug was fixed in the package gnome-user-docs - 3.36.2+git20200704-0ubuntu1
1782859,2021-02-01 17:31:04 UTC,This issue was fixed in the openstack/manila 10.0.2 release.
1782859,2021-02-01 17:23:04 UTC,This issue was fixed in the openstack/manila 9.1.5 release.
1782859,2020-08-21 17:11:03 UTC,"Reviewed:  https://review.opendev.org/747341
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=3b82fef551d80ff80da9b7d4a32dff8434ca5042
Submitter: Zuul
Branch:    stable/train"
1782859,2020-08-21 14:27:16 UTC,"Reviewed:  https://review.opendev.org/747340
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=1434adc353e80192d9a17121b57831d273b30633
Submitter: Zuul
Branch:    stable/ussuri"
1782859,2020-08-21 06:52:06 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/747342"
1782859,2020-08-21 17:47:59 UTC,"Reviewed:  https://review.opendev.org/747342
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=5cd33f14f465de206a7ccc6f56d48919c59e7365
Submitter: Zuul
Branch:    stable/stein"
1782859,2020-08-21 06:51:19 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/747340"
1782859,2020-08-21 00:14:01 UTC,"Reviewed:  https://review.opendev.org/745210
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=e2e764d9763b9367321a4c7f14b0150f67f3b08e
Submitter: Zuul
Branch:    master"
1782859,2020-08-21 06:51:43 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/747341"
1782859,2020-08-06 19:46:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/745210"
1782859,2020-08-06 15:21:54 UTC,api-ref was implemented in https://review.opendev.org/#/c/583091/
1782870,2018-08-02 07:39:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782870,2018-11-01 04:20:29 UTC,I just got the same issue:
1782870,2018-11-22 02:36:48 UTC,"if it can help anyone, I had this problem on normal update/upgrade on 16.04.05 LTS
if you notice the error message:  /usr/local/bin/ckbcomp: not found
my ckbcomp was in BIN not LOCAL/BIN.
I copied it to BIN and rerun update/upgrade and the upgrade completely successfully. sorted."
1782876,2020-05-21 10:24:15 UTC,"Migrated to new issue tracker, please follow the issue there for updates:
https://github.com/Xubuntu/xubuntu-website/issues/6"
1782880,2018-08-28 12:19:44 UTC,Unfortunately after system update the bug appeared again!
1782880,2018-08-22 11:38:48 UTC,After apt-get update on 18.04.1 the problem still existed.
1782880,2018-07-27 12:47:07 UTC,"Thanks for answer. Command apport-collect 1782880 has been executed successfully.
The problem seems not to be related to any kernel version. It looks like that it is a plasma issue only.
The reported problem pop up after an update some time ago, also on another computer that  contains kubuntu 16.04.1, kubuntu 18.04 and windows 8.1."
1782880,2018-07-27 11:44:01 UTC,apport information
1782880,2018-07-27 11:44:00 UTC,apport information
1782880,2018-07-27 11:43:58 UTC,apport information
1782880,2018-07-27 11:43:57 UTC,apport information
1782880,2018-07-27 11:43:56 UTC,apport information
1782880,2018-07-27 11:43:55 UTC,apport information
1782880,2018-07-27 11:43:53 UTC,apport information
1782880,2018-07-24 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1782880,2018-07-24 16:59:38 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1782880,2018-07-27 11:43:44 UTC,apport information
1782880,2018-07-27 11:43:45 UTC,apport information
1782880,2018-07-27 11:43:46 UTC,apport information
1782880,2018-07-27 11:43:52 UTC,apport information
1782880,2018-07-27 11:43:48 UTC,apport information
1782880,2018-07-27 11:43:50 UTC,apport information
1782880,2018-07-27 11:43:51 UTC,apport information
1782880,2018-07-27 11:43:47 UTC,apport information
1782882,2018-07-21 10:41:21 UTC,"StacktraceTop:
 do_lookup_x (undef_name=undef_name@entry=0x7ff1adbbcc63 ""xf86IDrvMsg"", new_hash=new_hash@entry=4135273453, old_hash=old_hash@entry=0x7ffe99573340, ref=0x7ff1adbbc6b8, result=result@entry=0x7ffe99573350, scope=<optimized out>, i=<optimized out>, version=0x0, flags=5, skip=0x0, type_class=1, undef_map=0x55b58ff39d10) at dl-lookup.c:403
 _dl_lookup_symbol_x (undef_name=0x7ff1adbbcc63 ""xf86IDrvMsg"", undef_map=0x55b58ff39d10, ref=ref@entry=0x7ffe995733e8, symbol_scope=0x55b58ff3a068, version=0x0, type_class=type_class@entry=1, flags=5, skip_map=<optimized out>) at dl-lookup.c:813
 _dl_fixup (l=<optimized out>, reloc_arg=<optimized out>) at ../elf/dl-runtime.c:112
 _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125
 xf86libinput_check_device (atom=atom@entry=319, dev=<optimized out>, dev=<optimized out>) at ../../src/xf86libinput.c:3669"
1782882,2018-07-27 11:36:09 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1782882,2018-10-30 02:57:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782885,2018-09-06 10:32:36 UTC,"ok - did
 dpkg --configure -a
after fixing root password."
1782885,2019-03-18 17:31:29 UTC,This issue seems to have been fixed (never append again since at least 1 month)
1782885,2018-11-18 15:40:30 UTC,"Exactly the same behavior as described in thirst post. Found also 3 other user describing the same on forum.ubuntu-fr.org.
Additionally I must say that sometimes it works properly"
1782885,2018-09-06 10:19:24 UTC,"I just tried to un
  su dpkg --configure -a
but got:
  u: unrecognized option '--configure'"
1782885,2018-09-05 09:51:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782885,2018-07-21 11:10:51 UTC,"more:
In order to actually install the updates, I must end the dicover program using SYSTEM MONITOR, then press updatr again. Then it usually works as expected."
1782885,2018-09-06 10:08:38 UTC,there is a new error report when trying to update:
1782894,2019-07-13 15:26:41 UTC,Is this what you were hoping for?
1782894,2019-07-21 20:07:40 UTC,"Thanks, though that seems to be only part of it, if I understand correctly that the commit is about allowing users to change ""The color (RGBA) of the badge displaying urgent count"""
1782899,2018-07-21 13:30:09 UTC,This change was made by a bot.
1782899,2018-07-24 17:00:36 UTC,You may need to run the following from a terminal:
1782903,2019-07-15 16:12:24 UTC,"ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Sat Jul 13 00:30:20 2019
DistroRelease: Ubuntu 19.04
ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
ExecutableTimestamp: 1547026118
ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
ProcCwd: /home/bakermj
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8"
1782903,2018-08-01 20:23:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782903,2018-08-15 09:30:30 UTC,"I've experienced this as well.
I'm running for a few weeks now from a clean Mate install 18.04.
I'm attaching the full crash minus CoreDump because of privacy concerns but can be provided in private if needed.
Thank you."
1782903,2019-07-15 16:09:51 UTC,Same issue but on 19.04
1782908,2018-11-28 13:47:44 UTC,"Thank you for your bug report. Indeed that seems an issue but not a packaging one, upstream doesn't seem to include that icon either, it should be reported on https://gitlab.gnome.org/GNOME/gtk/issues"
1782918,2020-03-13 08:57:51 UTC,"Related to this: in this same setup (laptop screen is bottom display, external monitor is top display), when I change the primary display to the top monitor (so the menu bar is shown on top and the window panel is shown at the bottom of this top monitor), the bottom part of maximized open windows disappears behind the bottom window panel."
1782918,2018-07-21 16:29:08 UTC,I have added five screenshots to better illustrate.
1782918,2020-03-07 15:31:59 UTC,I have exactly the same experience in Ubuntu Mate 19.10.
1782920,2020-02-10 09:28:32 UTC,Looks like this is/was a problem in hplip-data
1782920,2020-02-10 09:23:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782922,2018-07-26 19:25:35 UTC,"Hi Jakob,"
1782922,2019-10-30 13:21:21 UTC,Please see the attached document for testing details.
1782922,2019-10-30 13:33:14 UTC,"This has been tested successfully on disco-proposed, stein-proposed, and rocky-proposed using the steps in https://bugs.launchpad.net/keystone/+bug/1782922/comments/28."
1782922,2019-10-30 14:26:47 UTC,This issue was fixed in the openstack/keystone 13.0.3 release.
1782922,2019-11-04 13:24:40 UTC,"The verification of the Stable Release Update for keystone has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1782922,2019-11-04 13:34:39 UTC,This bug was fixed in the package keystone - 2:15.0.0-0ubuntu1.2
1782922,2019-11-04 14:12:37 UTC,The verification of the Stable Release Update for keystone has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1782922,2019-11-05 18:38:34 UTC," This bug was fixed in the package keystone - 2:14.1.0-0ubuntu1.1~cloud1
 ---------------"
1782922,2019-11-21 19:07:33 UTC,"Hello Jakob, or anyone else affected,"
1782922,2019-11-27 02:54:19 UTC,"I tested the fix for this code following the instructions at https://launchpadlibrarian.net/449185359/bug-1782922-testing.txt and everything works ok, and no regressions were detected."
1782922,2019-11-28 01:06:50 UTC,"tested the package that fixes this bugfollowing the instructions at https://launchpadlibrarian.net/449185359/bug-1782922-testing.txt, everything works ok, and no regressions were detected."
1782922,2019-12-09 15:28:01 UTC,"@Felipe, by any chance can you re-test with the fix for LP: #1850634 which is in bionic-proposed?"
1782922,2020-01-13 22:15:15 UTC,"@Corey, verification done ;-)"
1782922,2020-01-15 00:31:14 UTC,This bug was fixed in the package keystone - 2:13.0.2-0ubuntu3
1782922,2020-01-15 17:18:50 UTC,"Hi all, would it be possible to obtain the hotfix for Queens, so we can provide it to a customer, who would like to test it in their Lab environment?"
1782922,2020-01-20 13:09:10 UTC,Hi @dorina-t this patch is already release in Bionic (Queens) and is ready to be released for xenial Queens UCA so lets ping @corey.bryant to see if he can get it released.
1782922,2020-01-27 15:12:04 UTC,This is fixed in xenial-queens keystone 2:13.0.2-0ubuntu3~cloud0.
1782922,2020-02-24 19:15:32 UTC,This issue was fixed in the openstack/keystone 14.2.0 release.
1782922,2019-10-25 08:44:39 UTC,"Hello Jakob, or anyone else affected,"
1782922,2019-10-24 00:30:25 UTC,"Hello Corey,"
1782922,2019-11-04 14:12:39 UTC,"This bug was fixed in the package keystone - 2:15.0.0-0ubuntu1.2~cloud0
---------------"
1782922,2019-10-22 12:29:44 UTC,"Hello Jakob, or anyone else affected,"
1782922,2018-07-27 09:58:21 UTC,"Nope. Did that multiple times while debugging this issue. As described, the group mapping expectes that the first RDN is the same as the user_id_attribute, which should either be stated in the documentation or fixed by changing the group mapping code."
1782922,2019-10-22 12:31:46 UTC,"Hello Jakob, or anyone else affected,"
1782922,2019-06-20 13:30:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666575"
1782922,2019-07-23 18:52:25 UTC,"Reviewed:  https://review.opendev.org/649177
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a1dc21f3d34ae34bc6a5c9acebc0eb752495ae7a
Submitter: Zuul
Branch:    master"
1782922,2019-07-24 17:12:29 UTC,"Change abandoned by Corey Bryant (<email address hidden>) on branch: master
Review: https://review.opendev.org/666575
Reason: Abandoned in favor of https://review.opendev.org/649177"
1782922,2019-07-30 15:38:46 UTC,Subscribing field-high which wasn't carried over from the other duplicate bug https://bugs.launchpad.net/keystone/+bug/1832766
1782922,2019-07-31 13:29:39 UTC,Note that the patch that was merged had a bug which is being fixed in https://review.opendev.org/#/c/672519/ so both patches will need to be merged and backported.
1782922,2019-08-29 18:45:34 UTC,"Reviewed:  https://review.opendev.org/672350
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=909cc9fa8380a03dfdb808db7fb863400fa36054
Submitter: Zuul
Branch:    stable/stein"
1782922,2019-08-29 18:45:49 UTC,"Reviewed:  https://review.opendev.org/672351
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=7b84e9fcf1c259fe32def301f5e94a2ded845533
Submitter: Zuul
Branch:    stable/rocky"
1782922,2018-08-30 10:40:37 UTC,"Hi,"
1782922,2019-09-18 10:02:12 UTC,"For Ubuntu, a new package version including this fix has been uploaded to the following:
* eoan (and train cloud archive) - https://launchpad.net/ubuntu/+source/keystone
* disco unapproved queue - https://launchpad.net/ubuntu/disco/+queue?queue_state=1&queue_text=keystone
* rocky-staging (cosmic is EOL) - https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/rocky-staging/+packages?field.name_filter=keystone&field.status_filter=published&field.series_filter=
* bionic unapproved queue - https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=keystone"
1782922,2019-09-03 18:39:24 UTC,"Reviewed:  https://review.opendev.org/674030
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9d9451e13c8e7a1835d721be7b8a4a5c6dff2b95
Submitter: Zuul
Branch:    stable/queens"
1782922,2019-09-30 09:57:20 UTC,"I see Corey added the template in bug comment #15, possibly because he does not have the powers to modify the bug description in this case? Anyway, I'll copy it over to the description field and accept."
1782922,2019-09-27 22:28:21 UTC,(It should be possible to confirm from a log that this newly added test did in fact run.)
1782922,2019-09-27 22:27:59 UTC,"The SRU diff looks good, but the SRU template is missing."
1782922,2019-09-30 09:58:00 UTC,"Hello Jakob, or anyone else affected,"
1782922,2019-09-24 21:11:28 UTC,Ubuntu SRU Details:
1782922,2019-09-18 10:02:47 UTC,Cosmic is EOL. will fix direction in Rocky cloud archive
1782922,2019-09-27 09:10:34 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1782927,2018-07-21 17:49:13 UTC,"Here's the dialog during Gerber generation that you need to say ""No"" to: ""Zone fills are out-of-date. Re-fill?"" Same as when offered drugs: just say ""No""!"
1782927,2018-10-18 17:34:54 UTC,"Note that when you implement a panelization tool, please also add a check box to ""erase overhanging silkscreen on individual boards"" or something to that effect, to prevent silkscreen that is hanging off of your board from overlapping onto adjacent boards after panelizing."
1782934,2018-07-28 10:21:13 UTC,"Update: I wanted to make sure of the problem still existing in the 4.18.0 kernel, so I started from scratch again with the following steps:"
1782934,2018-09-28 07:43:21 UTC,It was still happening on 4.19-rc1. I'll test on later 4.19 rcs over the weekend.
1782934,2018-09-15 09:27:55 UTC,Does this still happen to latest mainline kernel or latest Ubuntu 18.04 kernel?
1782934,2018-10-10 19:33:27 UTC,"I did not see it mentioned above, so I figured it was worth noting."
1782934,2018-08-04 11:02:48 UTC,"Thanks Daniel. I've spent all morning testing kernels, and here're my results. Spoiler nothing after 4.15 works reliably, and mostly doesn't work at all."
1782934,2018-07-30 02:36:47 UTC,Thanks.
1782934,2018-07-25 07:42:04 UTC,@jsalisbury: Thanks!
1782934,2018-07-23 07:44:30 UTC,Hi Daniel. The backlight keys do not help.
1782934,2018-07-24 18:21:05 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1782934,2018-07-24 12:18:21 UTC,I am experiencing the same problem. When I boot with any other kernel than 4.15.0-20-generic the internal display goes black after GRUB.
1782934,2018-07-23 07:54:53 UTC,Does switching VTs (Ctrl+Alt+F4) turn it on?
1782934,2018-07-23 03:08:58 UTC,Do the backlight keys help at all?
1782934,2018-07-23 03:00:07 UTC,This change was made by a bot.
1782934,2018-10-11 07:05:20 UTC,Would it be possible for you to do a kernel bisection?
1782934,2018-07-25 01:57:15 UTC,"Almost, maybe related to bug 1782739"
1782934,2018-11-13 16:51:15 UTC,I'll try to to the bisection this coming weekend.
1782937,2018-08-21 19:56:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782938,2018-08-14 11:05:46 UTC,"This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'."
1782938,2018-10-15 22:35:53 UTC,This bug is still causing random build failures in Fedora.  Do any of you subunit developers have any idea at all what might be going wrong here?  We would really like to make subunit builds reliable.
1782938,2018-07-21 18:14:30 UTC,"Alas, this bug popped up again during the mass rebuild.  I will ask upstream to check into it."
1782938,2018-07-03 12:52:16 UTC,subunit-1.2.0-20.fc29 fails to build in F29 because this test fails randomly:
1782938,2018-07-04 00:53:09 UTC,"I just did a build of 1.3.0 and it succeeded on all arches, which doesn't necessarily mean this bug has been fixed.  On the negative side, I completely forgot about the side tag when I submitted the build, so now I get to do another build..."
1782938,2018-07-03 20:48:11 UTC,"Yes, it's been doing that for awhile now.  I haven't been successful in tracking it down.  I will see if version 1.3.0 has a fix for the issue.  If not, I will at least ask upstream to look into it."
1782938,2018-07-04 01:11:24 UTC,"The rebuild for f29-perl also succeeded on all arches.  I think I will do a few scratch builds to see if this bug happens again before declaring that it has been fixed, though."
1782939,2018-11-13 19:36:05 UTC,Any change Qtile 0.12 can get into 19.04? It is quite cumbersome to install manually.
1782939,2019-01-13 13:06:38 UTC,"There is a 0.13.0 already, really hope to see someone packaging new version soon"
1782939,2020-04-16 20:24:07 UTC,"qtile has been removed from the Debian archive -
https://bugs.debian.org/952120 at the request of the
maintainer. It was subsequently removed from Ubuntu
(Focal) on 2020-03-02. Closing as package won't
feature in any future Ubuntu release or be upgraded
in any existing release."
1782940,2019-01-05 22:27:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782940,2020-08-09 23:40:05 UTC,pdfsam-basic:amd64 (3.3.5-1)
1782941,2020-04-28 04:17:26 UTC,[Expired for eog (Ubuntu) because there has been no activity for 60 days.]
1782941,2020-02-27 12:49:06 UTC,Could you still reproduce this bug?
1782942,2018-07-29 22:28:33 UTC,Fixed by: https://review.openstack.org/#/c/584669/
1782949,2018-07-22 09:55:17 UTC,Please add version info
1782949,2018-07-22 14:51:44 UTC,"Application: kicad
Version: 6.0.0-rc1-unknown-7dfc4e3~65~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-25-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011"
1782951,2018-08-05 21:54:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782957,2018-12-22 15:19:44 UTC,This is connected to: https://bugs.launchpad.net/kicad/+bug/1563744
1782957,2019-06-25 11:27:23 UTC,"Fixed in revision 5c89e4490ede81a45e77e258f81d54dca65a6536
https://git.launchpad.net/kicad/patch/?id=5c89e4490ede81a45e77e258f81d54dca65a6536"
1782960,2018-07-22 05:22:51 UTC,"For clarifcation, prior to 0.6.0 warnings (whether from the message's default, or through the --warn option) would show up with a [W]. Looks like intention was to change error codes to be Wxxx or Exxx going forward."
1782962,2020-05-11 10:17:13 UTC,Is this bug just about fullscreen tearing or windowed too?
1782962,2020-04-20 16:34:38 UTC,"Yes, it still happens on Xubuntu 18.04, nvidia driver, sync to vblank set in OpenGL settings in NVIDIA X Server Settings. But I expect it to be better with 19.10 (Xfce 4.14) when using compositor. Chromium Version 80.0.3987.163 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit)"
1782962,2020-04-19 05:21:19 UTC,I am removing Xorg from this bug. If Xorg is to blame at all then it's probably already covered by one of the other existing bugs:
1782962,2020-04-20 12:33:18 UTC,"Jarno Suni, please excuse the lack of feedback on your bug report. Would you mind commenting here to let us know whether the latest chromium update presents the same problem that you originally reported? Thanks in advance."
1782966,2018-07-22 06:49:27 UTC,"Application: kicad
Version: 6.0.0-rc1-unknown-6d2dfbb~65~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-130-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009"
1782966,2018-07-22 15:43:53 UTC,"We don't support Add/Remove Corner for polygons at all.  We do for zones, which can act much like polygons on the board, but aren't supported in footprints (wishlist already logged for that)."
1782966,2018-07-22 15:58:35 UTC,"I see.  But since it's possible to create multi-point polygons (not zones) in the editors, being not able to add/remove vertices afterwards seems a bit inconsistent."
1782966,2018-07-22 16:12:02 UTC,"OK, I turned the bug into a wishlist for corner editing for polygons."
1782966,2018-07-22 16:23:05 UTC,Thanks!
1782966,2018-07-22 16:58:03 UTC,I'd like this too. I haven't seen it for fill zones either though at least as of v5.0.0-rc3.
1782966,2018-07-31 09:58:20 UTC,"@Tom, I saw mention of this in the fundraising video.  If it's Orson that's working on it instead of you, please re-assign."
1782966,2018-09-15 16:53:48 UTC,"Fixed in revision 06ac172c276fa22ec6ecc9c4ea8374dc79443548
https://git.launchpad.net/kicad/patch/?id=06ac172c276fa22ec6ecc9c4ea8374dc79443548"
1782966,2018-10-03 18:28:38 UTC,The fix only works for footprints.  Should be extended to board editor as well.
1782966,2018-10-03 18:31:15 UTC,"Fixed in revision 6c693f80a741c1674d470e8ffb4dcf0fa573824d
https://git.launchpad.net/kicad/patch/?id=6c693f80a741c1674d470e8ffb4dcf0fa573824d"
1782969,2018-07-24 13:39:38 UTC,"This is known when you have IPT_MODULES set in /etc/default/ufw, which is the default in Ubuntu. You can get rid of the messages by using this in /etc/default/ufw:"
1782969,2020-06-14 15:08:48 UTC,"Any updates on this (e.g. what ""additional functionality"" do we need to make up for the lost connection tracking)?"
1782969,2020-06-15 15:36:42 UTC,"In Ubuntu 20.04, IPT_MODULES defaults to empty so the message will be gone in default installs. It also includes some documentation (see CONNECTION HELPERS in http://manpages.ubuntu.com/manpages/focal/man8/ufw-framework.8.html) that should point you in the right direction. Work has started for adding 'ufw' syntax for making working with connection helpers easier, but it isn't yet in a released version of ufw."
1782979,2020-04-15 23:40:23 UTC,Did you try a reinstall?
1782979,2020-06-15 04:17:37 UTC,[Expired for fonts-orya-extra (Ubuntu) because there has been no activity for 60 days.]
1782980,2021-01-13 22:44:17 UTC,Confirmed when working with Docker/Mumble.
1782980,2021-01-13 22:43:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782984,2019-07-30 00:35:40 UTC,"Hi All,"
1782984,2019-07-01 15:54:32 UTC,Hi!
1782984,2019-06-16 00:49:49 UTC,"This bug still exists. PCManFM randomly freezes and prompts me to end the process.
Like @Patrick Schmitt, I receive a ""Sorry Ubuntu has experienced an internal error ...."" message, and when I than try to see the details of the error message, the message window itself crashes instantly."
1782984,2021-02-23 21:30:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782984,2019-04-07 23:22:11 UTC,"** (zeitgeist-datahub:1475): WARNING **: 15:24:07.191: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
evince 'file:///home/..........pdf'
pcmanfm
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
pcmanfm: ../../src/xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
** Message: 15:30:11.189: app.vala:130: pcmanfm exit with this type of exit: 134
** Message: 15:30:11.189: app.vala:148: Exit not normal, try to reload
** Message: 15:30:11.193: app.vala:76: Launching pcmanfm"
1782984,2019-04-07 19:58:41 UTC,"@EnduranceCode, you would want to look in ~/.cache/lxsession/LXDE/run.log for something similar to:"
1782984,2019-03-21 13:15:15 UTC,"@wxl: Walter Lapchynski,
Can you please tell me what I should look for in /var/log/syslog or in any other file? I woul like to help but I'm not sure how to do it.
Thank you"
1782984,2019-11-08 13:29:07 UTC,"just wanted to tell that this bugs are the same: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1775015
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1776547
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1777321"
1782984,2019-02-03 05:51:55 UTC,"Can EVERYONE that has the problem confirm something similar to the error:
pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
????"
1782984,2019-03-10 04:12:51 UTC,"SpaceFM GTK3 indeed works without hanging. Moreover, there is finally a report about the rarer Leafpad crash: the error in the LXDE log is **identical** to pcmanfm error."
1782984,2019-03-05 06:50:42 UTC,"Thank you, @Walter for the excellent advice! SpaceFM GTK3 works well: 3 days so far without any freezes!"
1782984,2019-03-01 18:46:13 UTC,"Rych, as I mentioned before Ilya had expressed issues with other GTK
apps. In particular, the same error appears in /var/log/syslog with
LibreOffice, so that may be somewhere to check:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161"
1782984,2019-02-28 12:05:10 UTC,"Walter: occasionally even Leafpad would crash, although I do not have a log of those rare events. But now I have another GTK file manager that locks-up on me in similar way. I've been trying the OpenBox variant of Porteus which comes with SpaceFM. We've pulled out a latest alpha of SpaceFM. It crashes too, albeit less frequently than PCManFM. The developer of SpaceFM apparently is trying to fix multithreading bugs, see https://github.com/IgnorantGuru/spacefm/commits/alpha : ""conservative lock"", ""mutex"", ""non-thread-safe"", ""thread races"" coming from within GTK functions (!?) Perhaps IgnorantGuru could tell us if there is a problem with GTK multithreading. I haven't found yet if SpaceFM logs any errors. It freezes. It's another GTK application. Therefore I will be moving to a non GTK distribution. I will continue to monitor this thread though for updates."
1782984,2019-02-10 17:06:20 UTC,"Hello,"
1782984,2019-02-06 01:06:16 UTC,"Thanks, Carlos. If I can get one more confirmation of this, I'm inclined
to call it a trend and I'll push it upstream because I suspect that will
be sufficient to figure out where the solution may lie."
1782984,2019-02-06 00:55:02 UTC,"Just the same:
(pcmanfm:1034): GLib-CRITICAL **: 22:26:36.391: Source ID 45146 was not found when attempting to remove it
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
pcmanfm: ../../src/xcb_io.c:259: poll_for_event: La declaración `!xcb_xlib_threads_sequence_lost' no se cumple.
** Message: 22:27:01.102: app.vala:130: pcmanfm exit with this type of exit: 134
** Message: 22:27:01.102: app.vala:148: Exit not normal, try to reload
** Message: 22:27:01.108: app.vala:76: Launching pcmanfm"
1782984,2019-03-20 22:39:59 UTC,"I have the same problem with PCManFM, it randomly crashes/freezes all the time. It started happening with a fresh install of Lubuntu 18.04.01 in a custom made desktop and in a Dell Latitude D820 Laptop. Last week I've downloaded the latest version of Lubuntu 18.04 and made a new fresh install in the Dell laptop and the problem persists."
1782984,2019-03-20 23:03:14 UTC,"@EnduranceCode: Lubuntu 18.10 does not use LXDE, but LXQt, so it's not
PCManFM, but PCManFM-qt. It does not suffer this problem because as
suggested in the last few comments, the problem seems to be related to
GTK and particularly GTK2. LXDE is still not GTK3 compliant, but if it
was, I believe that would solve this problem. You might want to check
and see if you have the errors reported above, as that would again go a
long way to further confirm this."
1782984,2019-11-08 13:39:50 UTC,"@Daniel, could you please proivde logs of the problem in LXQt? Just to see if it's the same problem or another."
1782984,2019-11-08 18:32:46 UTC,"Actually, Daniel, your mention of ""upgrading"" to LXQt has me wondering whether or not you took an LXDE version and then upgraded to an LXQt version(unsupported by Lubuntu, officially) without cleaning up all the old LXDE/GTK stuff. This could certainly lead to you using pcmanfm rather than pcmanfm-qt or otherwise using some app or apps that use GTK2, which everything seems to point to being the problem. LXQt doesn't use GTK-anything, so it should entirely be a non-issue."
1782984,2021-01-22 07:57:38 UTC,libx11 (2:1.7.0-1) unstable; urgency=medium
1782984,2021-01-15 16:31:54 UTC,Does anyone know if an update of the libx11 package for lubuntu 18.04 will be released?
1782984,2020-11-22 02:40:02 UTC,Fixed in libx11 version 1.7.0 with https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/dbb55e1a5e82870466b095097d9e46046680ec25
1782984,2020-08-01 12:56:15 UTC,"I think i got it right this time.
I managed to apply the proposed libx11 patch, installed the right libx11 deb and it worked so far.
If anyone willing to test the fix i pushed it to https://github.com/avafinger/libx11_1.6.4
Mind that if ubuntu team release a new version of the libx11 you might not get it installed and will need to reinstall the previous version.
Cheers"
1782984,2020-07-21 12:30:46 UTC,"The attachment ""This patch is not the fix. WARNING"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1782984,2020-07-21 11:58:48 UTC,"I applied the patch attached (libX11) but the crash still occurs with less frequency.
Maybe i missed some additional patch required to fix this."
1782984,2020-07-21 02:41:06 UTC,"Ouch, I missed this commit: https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34/diffs?commit_id=8b45f9589b3eb1ff46d16c774b017794e553db8e"
1782984,2020-07-21 02:34:43 UTC,"I would like to add some info that may help to narrow the problem.
I have had this crash in PCManFM since i upgraded ubuntu from 16.04 to 18.04 but the same bug manifest in Geany and Chromium as well. The bug could hit PCManFM within a few clicks opening directories and then clicking on a file or can take hours to show up. In the case of Chromium it usually hit at the launch of the browser."
1782984,2020-07-05 21:31:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782984,2020-06-07 08:50:47 UTC,"Apparently it's a bug in libx11, which persisted for a long time but
became much more likely with an update in libxcb.
Please see the still open merge request/patch at"
1782984,2020-01-02 18:50:53 UTC,"Just to add a few thoughts, this bug affects Google Chrome also.
The error is hard to reproduce, it happens anytime, even if in idle mode. However Chrome seems to do a lot of things in the background."
1782984,2020-01-02 16:41:11 UTC,"Hi, any news on this?
I have the same issue on Ubuntu 18.04.3 LTS.
I have upgraded from 16.04 recently and started to have this error.
This bug also affects leafpad and probably meld.
meld has a fix or workaround but can't remenber what was the fix, i had to install the latest meld from source, that fixed the problem."
1782984,2019-11-22 12:44:07 UTC,"[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
pcmanfm: ../../src/xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
** Message: 20:37:32.170: app.vala:130: pcmanfm exit with this type of exit: 134
** Message: 20:37:32.170: app.vala:148: Exit not normal, try to reload
** Message: 20:37:32.172: app.vala:76: Launching pcmanfm"
1782984,2019-11-22 12:36:19 UTC,"Yeah, really annoying. Happens often to me and no clue when it happens, but it happens like every fifteen minutes or so. I was just looking to install another file manager and found this bug report. And I am a programmer and happy to help, but not familiar with anything like this."
1782984,2019-11-20 21:12:55 UTC,Bug report with similar error https://gitlab.freedesktop.org/mesa/mesa/issues/108
1782984,2019-11-08 13:40:54 UTC,@voycey coulkd ypu please provide logs of the issue in LXQt?
1782984,2019-01-31 20:45:18 UTC,I have same problem with all gtk2 applications https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710
1782984,2018-09-30 20:33:43 UTC,Here's what I tried based on my interpretation of your steps to follow:
1782984,2018-10-22 14:19:50 UTC,"Hello,"
1782984,2018-09-24 19:27:49 UTC,"Ok, so at least several filesystems do have this problem."
1782984,2018-10-22 15:33:25 UTC,"Hi!  I am not a linux expert but I'm having the crashes with PCManFM too, all the time.  I rarely, if ever had them on Lubuntu 16.04."
1782984,2018-09-24 13:08:32 UTC,"Agreeing with Ben I can confirm the situation.
When multiple instances of PcManFM run and one of them freezes by accessing a file by user as it has been described above, other instances' windows become unresponsive, but seemingly the running processes (eg. copying) run in the background. One time I waited until a copying process may end to not to ruin the USB file system, and it seemed the copying process finished successfully despite the UI became frozen. So I think the background processes are running despite the file manager window is frozen."
1782984,2018-09-21 16:22:29 UTC,So important question: which filesystem(s) is this happening with?
1782984,2018-09-21 16:09:01 UTC,I have some additional information regarding the crash. I use a samba share with mp3fs on it. This is a file system that transfers files to mp3 upon access (https://khenriks.github.io/mp3fs/).
1782984,2018-09-21 12:23:16 UTC,"I want to add, that I love PCmanFM above all other options! We need this to work! The clean surface of PCmanFM fits perfectly into Lubuntu. It was a blessing to work with it. There is no clean alternative."
1782984,2018-09-21 06:27:44 UTC,"Same problem here with Lubuntu Bionic (18.04.01 LTS 64bit Desktop). PcManFM crashes quite often when accessing folders or files, it seems like a timing problem. There is no any rule of freezing. It is random and it seems is not depending on any action or background activity.
The PcManFM window becomes suddenly unresponsive, virtually it freezes. Eg. it shows the latest hint permanently, no reaction to anything.
When an instance crashes, all the other opened instances become unresponsive without any sign.
Starting a new instance of PcManFM after the crash, it closes all of the frozen instances, and the new one works well. ... for a while.
But never crashes during actions (Copying, Moving, Deleting...etc).
It crashes only when accessing a file or folder by a mouse-click."
1782984,2018-09-19 10:53:14 UTC,Same problem here on 18.04 (and previous versions). Crashes often for no special reason. Is there a more stable alternative?
1782984,2018-09-13 08:28:46 UTC,I have the same problem with my installation of Lubuntu 18.04.01 LTS on my Shuttle Barebone PC. When using it with my samba share from a NAS in my LAN it crashes a lot.
1782984,2018-09-11 22:27:48 UTC,"I don't get any error message, it just freezes (mouse still moves) and after a minute or so the ""has stopped responding"" box pops up."
1782984,2018-09-11 22:26:38 UTC,"Never had this until 18.04.  Now it happens on several 64 and 32 bit Lubuntu installs, as well as Ubuntu installs where I've added LXDE."
1782984,2018-09-11 22:25:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1782984,2018-08-28 19:15:24 UTC,"Same bug here.
After upgrading to Lubuntu 18.04, pcmanfm crashes unexpectedly with the same error message (No such file or directory: '/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf')."
1782984,2018-08-14 08:44:19 UTC,"Hi,"
1782984,2018-07-23 02:07:24 UTC,Looking into this a bit later when I do some real hardware testing.
1782984,2018-09-25 18:16:29 UTC,"Dear Walter,
I understood everything you wrote. I can promise tomorrow I will do a clean install of Lubuntu 18.04 on a HP Desktop AMD X2 250 machine and avoid any upgrade, and I will test the behavior of the file manager. As I remember - on an updated system of course - the problem came up more frequently when an USB device was connected to the system. Eg. an USB hub with an USB stick inserted in.
Tomorrow I'll test it again. The freezing is not occurred only when I clicked a file on the USB stick but I clicked any of the files or folders anywhere system-wide or even SAMBA shares.
Now, when I tried to describe the freezing to you, PCManFM just freezes when just clicking here-and-there now in the /var/log folder... You can see the click not selects the file, not changes its color as selected, and the black backgrounded hint freezes on the window. Then clicking on an other window, PCManFM file manager instance vanishes. I open the syslog to see what happened: No, there is nothing new in the syslog as if nothing had happened. Now there is no any external drive or device connected to the machine. Uhhhh.. it's a hard thing!"
1782984,2018-09-25 18:46:15 UTC,"Thanks Janos. I think if we are persistent and approach this scientifically, we can figure it out. If you can figure out some hint (e.g. the USB) start eliminating variables and applying it to multiple situations. When we can find something consistent, we'll be on our way."
1782984,2018-09-24 18:37:38 UTC,"As a quick response to Walter's important question as I see freezing of PcManFM is not really file system dependent. For me it freezes with NTFS, FAT32, FAT16 (USB sticks) and EXT4 file systems (Lubuntu installed) either. Tested hardware background is a HP Elite 8300 Pro and HP 6300 Pro. Both of the machines uses Pentium G processors with intel Q75 and Q77 chip sets which are nearly the same.
With previously used version 16.04 LTS everything worked perfectly without any error.
Since I know PCManFM is much more than a file manager in Lubuntu systems, it is the base of the whole system handler, Desktop...etc. That's why it is strange when file manager window freezes every other component work along.
As an addendum, using the new Swap policy - when the system handles the swap as a file, the GIMP graphics editor closes suddenly without any sign. Maybe the swap handler can not satisfy GIMP's quite big swap needs. But I don't know. Using the old Swap method, when I use a part of the HDD as a swap area (about 30GB for 12GB Ram installed) GIMP seems to work well. I don't know whether the new Swap handling affects PCManFM crash story or not."
1782984,2018-09-28 08:58:43 UTC,"Dear Walter,"
1782984,2018-10-22 01:54:00 UTC,"Hello,"
1782984,2018-10-19 20:58:36 UTC,"Sorry, the links I gave (in previous message) are bad."
1782984,2018-10-19 20:40:48 UTC,PCManFM 1.3.0.1 on Lubuntu 18.04.1 LTS
1782984,2018-10-17 09:26:05 UTC,"Hi Ben,
Recently I had problem with Samba share, but with a little workaround I managed to solve the problem.
Since Samba is also modified in Ubuntu 18.04 it is needed to look for your problem. Using Caja I have no problem like I had with PcManFM, but no mention it is a deeper problem because Thunar freezes also with Lubuntu 18.04."
1782984,2018-09-27 18:25:15 UTC,"Dear Walter,"
1782984,2018-10-13 19:21:07 UTC,The topic seems to be a bit abandoned suggesting all is good as it is not.
1782984,2018-10-11 07:28:00 UTC,Important News!
1782984,2018-10-10 13:09:18 UTC,"A new Crash file (/var/crash/)is available from an istalled Lubutnu 18.04.1 64 bit desktop version.
The situation is just the same, when accessing a directory, PcManFM window freezes."
1782984,2018-10-17 08:11:44 UTC,"Thanks for the information! I tried to copy via terminal from my samba share and this also crashed my mount point of the mp3fs on the share the same way as with using PCmanFM. I am not an expert, but maybe the problem is not related to PCmanFM but more deeply in the kernel?"
1782984,2018-10-01 17:26:47 UTC,"OK, thanks, Here I send all the saved logs include the .crash file syslog, kern.log etc."
1782984,2018-10-01 16:01:07 UTC,You should be able to attach the files here. The .crash will likely be the most useful.
1782984,2018-10-01 11:53:08 UTC,"Dear Walter,"
1782984,2018-10-01 06:36:40 UTC,"Dear Walter,"
1782984,2018-09-30 18:48:18 UTC,"Dear Walter,"
1782984,2018-09-28 20:48:59 UTC,"Dear Walter,"
1782984,2018-09-28 15:09:43 UTC,"In regards to actually fixing the bug, this is great news. This means that I should be able to reproduce it myself. Can you give me clear steps to follow, especially with the default ext4 filesystem? That will make it even easier if there are no special conditions."
1782984,2018-10-03 06:20:09 UTC,"Just a little update,
clicking the ""Go to parent directory"" (Up arrow) in PcManFM window I got a crash also. So not the file or directory clicking cause crash only."
1782986,2018-07-31 08:57:24 UTC,I removed both language-pack-en and language-pack-en-base and then reinstalled both.  This resolved the issue.
1782992,2019-11-04 07:13:50 UTC,"Hello ytxmobile,"
1782993,2018-07-22 14:30:06 UTC,This change was made by a bot.
1782993,2018-07-24 19:13:57 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1782993,2018-07-25 16:56:11 UTC,"i tested the latest release of 4.18-rc6 kernel but i have the same problem with touchpad right button.
during the upgrade i have received some info about ""  W: Possible missing firmware  ...... "", full log attached if can help you.
thanks"
1782993,2018-09-29 19:34:35 UTC,"This is a default feature of Ubuntu 18. I had the same problem and solve it downloading the gnome-tweak-tool. In the ""Keyboard & Mouse Settings"" changed the Fingers option by Area option."
1782996,2018-07-22 23:47:13 UTC,"Better example:
http://cseweb.ucsd.edu/~goguen/pps/tcs97.pdf"
1782996,2020-03-20 16:44:40 UTC,Closing because INVALID: May be support request.
1783005,2018-07-22 16:53:47 UTC,Here is the download from trainsim.com for Part 1 of The Floridian.
1783005,2018-07-22 16:55:14 UTC,The final part 3
1783012,2019-01-29 19:51:01 UTC,More likely related to the libxml2 version than lxml.
1783023,2018-07-23 18:29:10 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1783023,2018-07-24 16:08:50 UTC,"This happened to an Ubuntu user I know here is a photo of what they saw in the terminal on July 20, 2018."
1783023,2018-07-26 15:28:46 UTC,"Phased updates were not considered when kernel removal was added, we need to check for them, too."
1783023,2018-07-31 19:46:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783023,2018-08-14 07:52:49 UTC,"I'm running 16.04 LTS, and this bug has appeared in the last month or so.
I initially wondered if a phisher was wanting me to download some virus since there no details of the upgrades were displayed. Because the size of the upgrades increased over time, I presumed not and decided to ""Install Now""."
1783023,2018-08-15 06:00:22 UTC,"Discovered today that the thread I posted to on prior days was a duplicate to this thread, so now I'm updating here. This bug with my system first appeared August 9th. Yesterday I decided to go ahead and install whatever updates were there (even though I could not see 'what' the updates were since the box was blank). This was what occurred yesterday with my system while running the updater:"
1783023,2018-08-20 17:19:33 UTC,Seeing the same behaviour on this 16.04 system:
1783023,2018-08-24 08:25:41 UTC,"Still seeing this (haven't updated, neither using apt nor update-manager because this bug annoys me)."
1783023,2018-12-18 12:00:04 UTC,"Unfortunately still affecting 18.04.1 LTS, observed on and off again using Software Updater.
Recent system update performed 16/Dec/2018 comes up blank again, where it says ""Updated software is available for this computer"", but the list of available updates contains nothing. It does say the size of how much data will be downloaded. But no details of what this download is or what changes will be made if I click 'Install Now'."
1783023,2019-02-05 11:37:18 UTC,"Still occurring intermittently - please advise if this will be addressed in future updates?
Thanks.
NB: This is a different issue from bug #1072136"
1783027,2020-12-16 20:08:50 UTC,fixed in gEDA/gaf 1.10.1
1783027,2019-10-21 12:22:54 UTC,fixed in a8039b62bd3532ae2a3437946e2262d296927f55
1783027,2018-07-23 00:08:07 UTC,I had to comment that chedk to get geda to build.
1783027,2018-07-23 05:35:12 UTC,This patch fixes the check for INSTALL_DATA_EXEC
1783032,2018-07-23 04:29:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1783032,2019-11-01 09:23:56 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1783032,2020-01-01 04:17:26 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1783038,2018-08-14 19:46:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783044,2018-08-14 20:35:51 UTC,"My understanding is that grub-pc conflicts with grub-efi-amd64 (and other top-level GRUB packages), so having both installed shouldn't even be possible. (I've filed a bug report on the Debian side to address this, as this situation is not ideal: https://bugs.debian.org/904062) And that if you want the GRUB installation tools, but don't want the bootloader installed automatically on the running system, then this is when you'd install a grub-foo-bin package without the corresponding grub-foo."
1783044,2018-08-16 02:23:32 UTC,"I think there's a good case to get rid of those Conflicts:, at least for the package combinations that make sense. BIOS+EFI definitely makes sense, IMO."
1783044,2018-08-15 19:14:23 UTC,"Ahh, I forgot about the -bin.  I was talking to sil2000 on IRC the other day and he said he has made cosmic install them both, but they do still appear to conflict.  Strange."
1783044,2018-08-14 20:10:30 UTC,"No; you may not be installing it anywhere at all.  It is perfectly valid to have the grub-efi package installed in a PC that is booting in bios mode ( in fact, apparently we do now install both grub-efi and grub-pc if you boot the installer in EFI mode but the existing OS installed is in bios mode ).  You don't want every update of the package to try and fail to reinstall in that case."
1783044,2020-05-19 21:00:10 UTC,"I've confirmed that, as of focal, the /boot/efi/EFI/ubuntu/ directory no longer needs to be present in order for the grub-efi-amd64 package to install the bootloader files. Even /boot/efi/EFI/ does not need to be there; it will be created. This issue still appears to exist on the Debian side, however, and Ubuntu now has a related problem (LP: #1879558)."
1783044,2018-08-03 18:37:30 UTC,"I would think that the postinst script should use a low priority debconf question to ask if you want to create the directory and install or not, and default to not if you aren't showing low priority questions."
1783044,2018-07-23 04:41:08 UTC,"From what I have learned switching Lubuntu to Calamares, Ubiquity is what does this. If it isn't an EFI system, it doesn't do this verification."
1783044,2018-07-23 04:09:41 UTC,"I should point out that on the Debian side, the same conditional exists in the postinst script, so this same issue occurs there as well. (Only with the /boot/efi/EFI/debian/ directory, of course.)"
1783044,2018-08-03 18:56:59 UTC,"Philip, wouldn't such a debconf question be closely related to the existing question on whether to install to the EFI removable media path?"
1783047,2018-07-23 04:15:35 UTC,listed all the ubiquity wikis and a link to the 18.04 d-i page (https://help.ubuntu.com/18.04/installation-guide/amd64/apb.html).
1783047,2018-07-23 09:14:50 UTC,ubiquity specific debconf options are listed at the bottom of https://wiki.ubuntu.com/UbiquityAutomation (likely a bit outdated but it clearly says that netcfg can not be configured in ubiquity) ...
1783047,2018-10-19 22:35:40 UTC,"Resolving this issue is a MUST.
Please"
1783047,2019-09-30 17:09:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783048,2018-07-23 13:54:16 UTC,Looks like the upgrades to Newton and Ocata might not have completed. Make sure to complete each step before moving on to the next.
1783048,2018-07-27 03:34:44 UTC,"I upgrade OpenStack from Mitaka to Pike directly. After upgrading to Pike, The cinder-volume service will report new service information to cinder.services table. The new service information for Pike is different from the old service information for Mitaka(the cinder.serivices.host is different).
For example:
Mitaka:
The cinder.services.host was host123
Pike:
The cinder.services.host would be host123@<cinder_driver_name>
So the old services information for Mitaka still existed on the cinder.serices and the cinder.services.rpc_current_version is 2.7. When startup cinder-scheduler service, it will call cast function to cinder-volume. The oslo.messaging will check the rpc_current_version and find the rpc_current_version of old services is different from new rpc_current_version. The exception will be raised."
1783048,2018-12-20 06:57:40 UTC,"This is likely to be that there's some services in the cinder db services table that need to be removed, which is blocking the start of the service.  The upgrade doc mentioned in #1 has instructions to remove them - you can see them with 'cinder service-list'."
1783049,2018-07-23 09:34:31 UTC,https://review.openstack.org/#/c/584712/
1783049,2019-07-15 09:28:23 UTC,"Change abandoned by wangxiyuan (<email address hidden>) on branch: master
Review: https://review.opendev.org/584712"
1783050,2020-06-21 15:31:38 UTC,"Hi, It's June 2020 and I am still facing the exact same issue when installing Hue from sources in Ubuntu. Please help."
1783050,2018-11-01 14:38:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783051,2018-07-23 04:54:31 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/584726"
1783051,2018-07-23 11:00:24 UTC,"Reviewed:  https://review.openstack.org/584726
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=2a301ccce0b4816df53fe366f8b356e83f551e5a
Submitter: Zuul
Branch:    stable/queens"
1783054,2018-07-23 05:30:06 UTC,This change was made by a bot.
1783054,2018-07-23 14:14:26 UTC,This commit should fix your issue:
1783058,2018-07-31 11:24:26 UTC,I have written a set of instructions for Controller deployment. It can be found here: https://gist.github.com/sodar/a4754538b3bd10a5dabbde9c7f6ee605
1783059,2018-07-31 11:26:20 UTC,I have written a set of instructions for Contrail Controller deployment. Please refer to https://bugs.launchpad.net/opencontrail/+bug/1783058/comments/1
1783061,2018-07-31 10:22:53 UTC,I have updated instances.yaml file (https://gist.github.com/sodar/d7945a610f5053d467de80c6feb09245) and instructions (https://gist.github.com/sodar/a4754538b3bd10a5dabbde9c7f6ee605).
1783061,2018-07-31 11:27:21 UTC,"Gists mentioned in the previous comments are outdated, please use instructions referred to in https://bugs.launchpad.net/opencontrail/+bug/1783058/comments/1"
1783065,2018-07-31 10:14:05 UTC,Work is being done on updating Controller version used in Windows CI. Please refer to https://github.com/Juniper/contrail-windows-ci/pull/237
1783068,2020-03-28 14:55:11 UTC,"Closing because INVALID: Similar issues. Please see:
https://gitlab.com/inkscape/inbox/-/issues/1733
https://gitlab.com/inkscape/inbox/-/issues/1176"
1783073,2019-11-08 06:15:10 UTC,"Change abandoned by Michał Dulko (<email address hidden>) on branch: master
Review: https://review.opendev.org/584930
Reason: Abandoning due to inactivity."
1783073,2018-07-23 15:12:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584930"
1783076,2018-10-09 14:00:13 UTC,"Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-128-generic
touch: невозможно выполнить touch для '/boot/initrd.img-4.4.0-128-generic.new': Неизвестная ошибка 4094
/usr/sbin/mkinitramfs: 382: /usr/sbin/mkinitramfs: cannot create : Directory nonexistent
rm: невозможно удалить '/boot/initrd.img-4.4.0-128-generic.new': Неизвестная ошибка 4094
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1"
1783080,2018-08-17 13:25:55 UTC,Further information on this:
1783084,2018-07-23 09:43:04 UTC,This behavior affects charm-ceph-osd when wal and db need to be collocated.
1783084,2018-07-25 07:06:04 UTC,"This looks like a maas issue - the error message comes from maas. Juju is simply asking for a machine with 2 storage devices, each tagged ""optane""; in this case the default size for each pool would be 1GiB as I don't think the charm specifies a default storage size. The storage constraint passed to maas is:"
1783091,2018-07-23 09:08:47 UTC,See also: https://bugs.launchpad.net/kicad/+bug/983230
1783091,2018-07-30 16:32:24 UTC,"About a year ago I started compiling my ideas of what KiCad's design rules should be able to do. Seeing this post, I read through it quickly and hopefully caught a few typos. Then piled on a couple ideas I hadn't written down yet. You're welcome to take any ideas, build off of it, or ask me for clarification."
1783093,2018-07-23 09:17:13 UTC,"""Tracks exposed through solder mask"": https://bugs.launchpad.net/kicad/+bug/1689541"
1783093,2018-07-23 09:18:41 UTC,"""DRC check for silkscreen that will be removed because of pads, vias, etc."""
1783093,2018-07-23 13:10:31 UTC,"We're using kicad for a fairly complex project, and there is definitely a priority to implementing this issue;"
1783114,2018-07-23 11:41:45 UTC,I also include first 5 page batch that I was printing
1783114,2018-09-17 12:12:39 UTC,"Hi,
Can you provide below information?
* Printer details
* Distro name and version
* HPLIP version installed
* Did you try printing the same document from hp-toolbox? what is the behavior?"
1783114,2019-02-06 21:14:34 UTC,"Hi,
Sorry for the huge delay, I was out of the city and had no access to the printer."
1783117,2018-07-23 21:41:04 UTC,"It's actually mostly accidental that some things are preserved, but maybe we should make it less accidental."
1783121,2018-07-23 13:03:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/584857"
1783125,2019-12-02 14:50:47 UTC,"FYI, patches can be tracked here:"
1783125,2019-12-03 12:38:28 UTC,"Reviewed:  https://review.opendev.org/585178
Committed: https://git.openstack.org/cgit/openstack/charm-glance-simplestreams-sync/commit/?id=0bf193dc854a4b563d8782a110f32b3be248db7c
Submitter: Zuul
Branch:    master"
1783125,2019-11-15 23:23:07 UTC,"Change abandoned by Alexandre Gomes (<email address hidden>) on branch: master
Review: https://review.opendev.org/691433"
1783125,2019-01-07 11:52:19 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/585178
Reason: Marking this review as abandoned due to lack of activity in the past 6 months.
Feel free to restore it again if you want to pick up and continue the work."
1783125,2018-07-24 09:12:37 UTC,"Resubmitted here:
https://review.openstack.org/#/c/585178/"
1783125,2018-07-23 16:32:22 UTC,"PR to address this bug:
https://github.com/openstack/charm-glance-simplestreams-sync/pull/1"
1783125,2019-07-18 22:15:27 UTC,"Change abandoned by Alexandre Gomes (<email address hidden>) on branch: master
Review: https://review.opendev.org/671508
Reason: Abandoning in favor of 585178"
1783134,2018-07-23 14:00:04 UTC,This change was made by a bot.
1783134,2018-07-24 18:07:37 UTC,You may need to run the following from a terminal:
1783134,2018-07-25 09:50:07 UTC,"The module failed to install.
I had to kill -9 dkms to bypass the issue.
After that, I can use apt again and the kernel loads correctly.
I'm not so sure about the module."
1783135,2018-07-23 14:24:34 UTC,It is on the v6 road map already.
1783135,2019-11-24 18:58:55 UTC,"Hi,"
1783135,2019-11-24 20:29:00 UTC,"Thanks, Victor."
1783145,2018-07-24 16:30:30 UTC,"fyi, multistropt can use commas instead"
1783151,2018-09-12 17:13:55 UTC,"Evergreen Release 3.0.11
Browser Chrome"
1783151,2019-04-05 14:29:51 UTC,Related to this bug: https://bugs.launchpad.net/evergreen/+bug/1748464
1783160,2018-07-23 16:55:32 UTC,"Side note: If you do the ESC-then-F5 keystroke really, really fast, Evince sometimes ends up in full screen mode (that you would normally get with F11) and then hangs and crashes."
1783172,2018-07-23 18:11:38 UTC,"Looking at the code, I see now that the Default button is supposed to Reset to Default, so it does seem appropriate to remove those local storage settings."
1783175,2018-12-03 11:36:52 UTC,"Hi,
packages have a set of defined usernames that are collision free among each other but as you encountered might collide with other things - especially if a username is rather short.
Commonly package names (ntp, mysql, ceph, ...) or package name plus suffix (libvirt-*, ...), are users used by the system."
1783184,2018-07-24 11:55:00 UTC,Agreed it is dangerous to restart neutron-ovs-cleanup. It's meant to run at
1783184,2018-07-24 12:03:03 UTC,Agreed it is dangerous to restart neutron-ovs-cleanup. It's meant to run once at system startup to cleanup ovs interfaces.
1783198,2018-07-27 15:38:43 UTC,"I'm attaching all console logs that were available of lxd runs of integration
tests.  The interesting thing is that *most* of the time when we see pylxd
related trace backs it is in shutdown (there was one in start).  Also
interesting is that most of the time the traceback occurs after collection
of the last file, and about 25-30 seconds later."
1783202,2018-12-22 14:16:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783203,2019-03-01 13:09:29 UTC,"From the commit message https://github.com/rabbitmq/rabbitmq-server/pull/1431 ""Avoid infinite loop when dropping entries in the GM"" in 3.6.15 sounds interesting, as we do seem to see some kind of infinite loop here. I don't have an explanation though as to why GM would be interacting with the management plugin in the way we see."
1783203,2019-03-15 04:09:14 UTC,There isn't a whole lot of details about node state here but GM (a multicast module) has nothing to do with the management plugin.
1783203,2019-02-28 13:07:51 UTC,"The latest release in the 3.6.x series seems to be 3.6.16. Almost all releases since 3.6.10 list changes to the management plugin, but I didn't spot anything obvious. Here are the release notes for each:"
1783203,2019-03-15 04:24:51 UTC,I mostly failed to explain the impact of the above Erlang bugs.
1783203,2019-03-15 14:07:07 UTC,raising erlang bug task; I think we need to address the two ERL-* issues in the xenial erlang version as identified in #13.
1783203,2019-05-14 08:02:55 UTC,Triaged the charm task until we can validate the fixes against the erlang/rabbit bits
1783203,2019-02-25 11:58:36 UTC,"Forgot to mention: The log in /<email address hidden> just stops when the server hangs, no output until after it is being restarted."
1783203,2018-07-24 06:01:20 UTC,Logs from /var/log/rabbitmq might be useful here
1783203,2018-10-05 15:03:28 UTC,"for people being hit by this bug, it would be helpful if you could generate a core file while rabbit is still stuck, this may give us some insights of where the process is looping."
1783203,2018-07-25 14:51:13 UTC,Now that is a useful nugget of information.
1783203,2018-07-24 17:51:17 UTC,"Adding that the config ""management_plugin=true"" causes the crashing to happen with the web.yaml stack, while having it false does not cause the crashing."
1783203,2018-07-24 11:22:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783203,2018-07-24 06:00:29 UTC,Diff between 18.02 and 18.05 rmq charm:
1783203,2018-07-24 03:54:03 UTC,"Attaching web.yaml, a heat template known to trigger this event."
1783203,2019-02-25 11:54:42 UTC,"We are also seeing this issue after upgrading OpenStack from Pike to Queens. It only seems to affect our larger setups, it wasn't seen during testing on our staging setup. The good thing is that I can confirm that disabling the management plugin seems to avoid the issue. We also have a core dump, but since it is from a production environment, I cannot share the content. However, the trace from thread 1 looks like"
1783209,2018-07-23 22:12:48 UTC,N.B. the following sequence works:
1783209,2018-09-08 09:52:58 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1783209,2018-09-08 23:32:58 UTC,"#2 shows the exact steps I took to build it. Frankly I have no idea how to build it ""with the debuild tools"" :)"
1783209,2018-09-14 17:59:33 UTC,"""The debuild tools way"" is running with the same tools which were used to make the original Debian package, so something like:
sudo apt build-dep growl-for-linux
apt source growl-for-linux
cd growl-for-linux*/
debuild -us -uc
cd ..
sudo apt install ./growl-for-linux_0.8.5-3_amd64.deb
gol"
1783209,2018-09-14 22:47:02 UTC,When building with debuild on 18.04 I can confirm it does not work.
1783209,2019-02-22 06:44:31 UTC,"Hi, This problem is caused by inappropriate hardening flags."
1783209,2019-02-24 23:11:02 UTC,This bug was fixed in the package growl-for-linux - 0.8.5-4
1783213,2018-07-24 07:44:13 UTC,"The forum is the place best to discuss things like this and you're likely to get more help there, not on Launchpad."
1783213,2018-07-23 22:49:44 UTC,I also experienced problems connecting to a network after the latest kernel update. I have a Broadcom BCM4350 802.11ac Wireless Network Adapter.
1783213,2018-07-23 22:21:20 UTC,Wifi button is showing off light. I am using MATE 16.04 desktop 1.12.1
1783220,2018-07-23 22:57:35 UTC,"This is a log file for Open Rails. Please include this file in bug reports.
--------------------------------------------------------------------------------
Date/time  = 7/24/2018 12:51:15 AM (2018-07-23 22:51:15Z)
BIOS       = X751LB.402 (American Megatrends Inc.)
Processor  = Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (4 threads, 2 cores, 2.2 GHz) (L1 Cache 32 KB) (L1 Cache 32 KB) (L2 Cache 256 KB) (L3 Cache 3072 KB)
Memory     = 11.9 GB
Video      = NVIDIA GeForce 940M              (2.0 GB RAM) (nvlddmkm 10.18.13.5946)
Video      = Intel(R) HD Graphics 5500 (1.0 GB RAM) (igdkmd64 20.19.15.4549)
Display    = \\.\DISPLAY1 (1600 x 900, 32-bit, primary, 0 x 0)
Sound      = Bluetooth Audio Device (btath_a2dp 8.0.1.316)
Sound      = Realtek High Definition Audio (rtkvhd64 6.0.1.7224)
Sound      = NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (nvvad64v 1.2.30.0)
Disk       = C: (Local Fixed Disk, NTFS, 237.9 GB, 123.9 GB free)
Disk       = D: (CD-ROM Disc, )
Disk       = E: (Local Fixed Disk, NTFS, 117.2 GB, 65.2 GB free)
Disk       = H: (Local Fixed Disk, NTFS, 814.2 GB, 341.5 GB free)
OS         = Microsoft Windows 10 Home 64-bit (10.0.17134)
Runtimes   = 2.0.50727 SP2  3.0 SP2  3.5 SP1  4 Client  4 Full  4.0 Client
Runtime    = 2.0.50727.8933 (32bit)
\\.\DISPLAY1 = Intel(R) HD Graphics 5500 (igdumdim32.dll 20.19.15.4549)
    Anisotropy     = 16
    Render Targets = 4
    Streams        = 16 (stride 255)
    Textures       = 8 (8192 x 8192, repeat 8192, ratio 8192)
    Points         = 256^2
    Volumes        = 2048^3
    Primitives     = 8388607
    Vertexes       = 16777215
    Vertex Shader  = 3.0 (32768 slots, 256 constants)
    Pixel Shader   = 3.0 (32768 slots)
    Clip Planes    = 6
--------------------------------------------------------------------------------
Version    = X4159
Build      = 0.0.6770.7159 (2018-07-15 03:58:38Z)
Logfile    = C:\Users\Robert Chalcak\Desktop\OpenRailsLog.txt
Executable = RunActivityLAA.exe
Argument   = -resume
Argument   = C:\Users\Robert Chalcak\AppData\Roaming\Open Rails\Trat ZSR 191-193 Vlaky 2018-07-24 00.50.07.save
--------------------------------------------------------------------------------
ActRandomizationLevel          =                0
ActWeatherRandomizationLevel   =                0
AdhesionFactor                 = (user set)     200
AdhesionFactorChange           = (user set)     0
AdhesionMovingAverageFilterSize =                10
AdhesionProportionalToWeather  =                False
Alerter                        = (user set)     True
AlerterDisableExternal         = (user set)     False
Autopilot                      =                False
AuxActionEnabled               =                False
AvatarURL                      =                http://openrails.org/images/support-logos.jpg
BrakePipeChargingRate          =                21
BreakCouplers                  =                False
Cab2DStretch                   =                0
CarVibratingLevel              = (user set)     1
CircularSpeedGauge             =                False
ConditionalLoadOfDayOrNightTextures =                False
CorrectQuestionableBrakingParams =                False
CurveResistanceSpeedDependen..."
1783224,2018-07-23 23:33:01 UTC,"Sorry, I've figured out that once I start mate-screensaver manually at the terminal hitting Ctrl+Alt+l does lock the screen.  So that's a manual workaround."
1783224,2018-07-24 23:58:48 UTC,"Okay, I was able to reproduce the bug just by waiting.  I have attached the output of mate-screensaver --debug from when I started it until now when the bug is active."
1783224,2018-07-27 01:35:11 UTC,"My screensaver is set to lock screen, but never does. Additionally, suspending the laptop doesn't lock the screen. But ctl-alt-L does work. Running Ubuntu Mate 18.04 64-bit. Have been running various flavours of Ubuntu for 12 years and this is the first one that does this."
1783224,2020-05-15 10:37:51 UTC,"In my case, the screensaver is not set to lock the screen, just show the contents of ~/Pictures, but still does not engage after a while."
1783224,2020-05-15 10:38:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783224,2020-10-22 21:58:02 UTC,"What's happening here is that the screensaver kicks in, blanks the screen to black, but ~/Pictures is not shown."
1783237,2018-07-24 07:31:18 UTC,"github's content is a mirror copy of git.openstack.org and is not guaranteed to be complete, but this can be done - I outlined an approach in a previous attempt to do this [1]."
1783237,2018-07-24 13:53:46 UTC,The user can also override the ansible-role-requirements with its own a-r-r by exporting an env variable.
1783237,2018-07-24 15:52:02 UTC,"I understand we can do s/git.openstack.org/github.com/ but that me and you know underline code, new person has no idea and he will be endup like me sitting and waiting for 5 hour or more to just finish checkout, I can understand hour but its takes multiple hours sometime.."
1783237,2018-07-24 16:31:10 UTC,We should add documentation for how to do this better to make (near|off)line installs simpler and low bandwidth installs faster. Docs to link and update are:
1783237,2018-07-24 16:31:20 UTC,"This way to do it is already in our reference documentation, but we can add links to it as part of a user story."
1783241,2018-08-03 18:04:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1783241,2018-08-08 03:15:40 UTC,Latest Dell IoT 300x Gateway kernel snap (r93) based on kernel ver. 4.4.0-132.158 was tested and verified by CE-QA.
1783241,2018-08-23 19:23:06 UTC,This bug was fixed in the package linux - 4.4.0-134.160
1783244,2018-08-02 09:45:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/588194"
1783245,2018-08-30 12:40:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783246,2018-08-07 14:01:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1783246,2018-08-10 14:17:31 UTC,I have confirmation from a user who has done verification for this kernel. Changing to verification-done-bionic.
1783246,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1783256,2018-08-13 16:18:05 UTC,https://review.openstack.org/#/c/585145/
1783256,2018-09-06 07:45:31 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/585145
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1783256,2019-03-25 10:42:20 UTC,"Change abandoned by Shu Muto (<email address hidden>) on branch: master
Review: https://review.openstack.org/585145
Reason: I abandoned this, and I'm so happy if someone restore and follow up this."
1783267,2018-07-25 06:20:47 UTC,"@ubuntu-kernel-bot uploaded logs as requested
Since I can't boot with kernel 4.15, these logs are from my running system with 4.13."
1783267,2018-07-26 13:26:34 UTC,"ok the DKMS failure, but does everything work as expected?"
1783267,2018-07-26 13:29:40 UTC,"You shouldn't install virtualbox-guest-dkms-hwe, but only virtualbox-guest-x11-hwe and virtualbox-guest-utils-hwe."
1783267,2018-07-27 07:47:10 UTC,"Hey Gianfranco, thanks for looking into this. :)"
1783267,2019-01-02 15:11:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783267,2018-08-29 21:16:58 UTC,can you please try a systemctl cat virtualbox-guest-utils-hwe when the system is not starting?
1783267,2018-09-07 13:42:13 UTC,There you go!
1783267,2018-07-25 06:16:56 UTC,apport information
1783267,2019-07-15 11:29:29 UTC,"This looks like a regression in the kernel builtin module, nothing I can fix in virtualbox side.
There have been breaking changes in newer 5.2+ virtualbox kernel modules, I suggest to avoid having them in 16.04, and to move to 18.04 if you want a newer codebase"
1783267,2018-08-07 06:31:37 UTC,"I tried your suggestion in #17 and uninstalled (purged) virtualbox-guest-dkms-hwe and rebooted on kernel 4.15.0-30. Result: my system is just as broken as before, virtualbox-guest-utils-hwe.service also fails to start and my screen remains black after that (I suppose X doesn't start either). So there is definitely an incompatibility between virtualbox-guest-*-hwe packages and the latest HWE kernel on xenial now."
1783267,2018-07-25 06:16:56 UTC,apport information
1783267,2018-07-25 06:16:53 UTC,apport information
1783267,2018-07-25 06:16:53 UTC,apport information
1783267,2018-07-25 06:16:52 UTC,apport information
1783267,2018-07-25 06:16:50 UTC,apport information
1783267,2018-07-25 06:16:49 UTC,apport information
1783267,2018-07-25 06:16:49 UTC,apport information
1783267,2018-07-25 06:16:48 UTC,apport information
1783267,2018-07-25 06:16:47 UTC,apport information
1783267,2018-07-25 06:16:46 UTC,apport information
1783267,2018-07-24 17:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1783267,2018-07-25 06:16:54 UTC,apport information
1783272,2020-01-11 15:41:17 UTC,"As noted in my last comment, this shoudl be fixed now."
1783272,2019-04-09 11:34:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783272,2019-04-09 13:07:58 UTC,"@lathiat,"
1783283,2019-05-23 16:57:45 UTC,"If this is racy, then it should be possible to trigger it reliably by adding sleep commands to one or more units."
1783283,2019-07-23 04:17:26 UTC,[Expired for console-setup (Ubuntu) because there has been no activity for 60 days.]
1783283,2019-04-05 19:17:25 UTC,"I don't understand why you are (were) seeing a bug here.  There are several other units that declare themselves After=plymouth-quit-wait.service without After=plymouth-quit.service, including getty itself, and I'm not aware of any reports that getty fails to start for users because of this race.  This sounds to me like a bug in the calamares-based ISO and its integration with the existing standard systemd units in Ubuntu, not a bug in console-setup."
1783283,2019-04-08 09:54:23 UTC,Was there a question in there?
1783288,2018-07-25 18:00:24 UTC,"Hi Orson,"
1783288,2018-07-24 13:34:37 UTC,"Typically, you wouldn't have junctions on those kinds of tracks. However, I see your point."
1783288,2018-07-24 12:14:28 UTC,"I am not saying no, but any ideas how to handle junctions?"
1783299,2018-07-27 11:33:45 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1783309,2018-07-24 11:00:06 UTC,This change was made by a bot.
1783315,2018-07-25 10:08:32 UTC,"This happened again the very next time there was a soft timeout on a repository scan, so there's obviously something repeatably wrong here."
1783315,2018-07-25 10:47:42 UTC,"I can't be absolutely sure when this regressed, since such soft timeouts aren't very common; there've only been three since the last rollout.  One thing I noticed was that a soft timeout on a PlainPackageCopyJob on 2018-07-16 didn't cause celery to hang, but soft timeouts on GitRefScanJob instances did.  My current suspicion is that it has something to do with urlfetch's thread handling."
1783315,2018-07-30 23:55:31 UTC,Fixed in stable r18739 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18739>.
1783315,2018-07-31 17:26:33 UTC,This (or similar) seems to have recurred:
1783315,2018-10-11 11:14:58 UTC,"I can reproduce a somewhat similar hang locally by sending SIGSTOP to a single worker process and then firing off a succession of jobs.  It seems that the file descriptor that celery uses to communicate with the worker is still writable, so celery sends a task to it (due to prefetching) and then gets stuck.  This is essentially the situation described in https://celery.readthedocs.io/en/latest/userguide/optimizing.html#prefork-pool-prefetch-settings, and indeed running the worker with -Ofair does help."
1783317,2019-11-17 17:22:53 UTC,"As a note, ssh-fuse in Focal now depends on fuse3, with Breaks: fuse"
1783317,2019-04-22 14:09:22 UTC,Please ignore the previous comment. I pasted that into the wrong window. Sorry!
1783317,2019-01-10 23:51:05 UTC,"I reviewed sshfs-fuse version 2.10+repack-2 as checked into disco. This should
not be considered a full security audit, but rather a quick gauge of
maintainability."
1783317,2019-04-22 14:04:41 UTC,"I reviewed robot-detection version 0.4.0-1 as checked into disco. This should
not be considered a full security audit, but rather a quick gauge of
maintainability."
1783321,2018-07-24 12:20:53 UTC,I went on irc for help and alexwolf provided the following workaround which fixed the problem:
1783321,2018-07-24 17:13:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783321,2018-07-25 05:00:17 UTC,The user workaround of editing the config.ini file per Tigran Aivazian's comment above worked for me.
1783321,2018-07-31 06:43:12 UTC," . . . and apparently the urls for those JSON files have changed back again. If you used the config.ini edit workaround mentioned above it is broken again. Revert back to the original urls to fix it - again (perhaps just restore config.ini from config.old?)
Looks like any data update call from a bad url writes the html error return into a new ""JSON"" file, then when the program loads the module and tries to read data from that corrupted JSON file it crashes. Which then triggers another update attempt on the next restart attempt. Next thing you know even your old backup copy of the JSON file is overwritten with the html error."
1783327,2019-09-19 10:10:49 UTC,This issue was fixed in the openstack/neutron-fwaas 15.0.0.0b1 development milestone.
1783327,2019-09-16 09:25:58 UTC,"Reviewed:  https://review.opendev.org/585688
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=a7e85121f7578857bbc45b6b764fc0ce0b5eab39
Submitter: Zuul
Branch:    master"
1783327,2018-07-25 08:51:47 UTC,"Change abandoned by huang liujie (huang.liujie@99cloud.net) on branch: master
Review: https://review.openstack.org/585586"
1783327,2018-07-25 01:43:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585586"
1783327,2018-07-25 09:20:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585688"
1783330,2018-07-25 07:10:56 UTC,"from the description, it isn't clear to me which part is not correct.  can you explain a little?
the number of ""a"" (5 vs 6) seems inconsistent. but it's just a typo, right?"
1783330,2018-08-15 17:22:04 UTC,Just 'typo'.
1783330,2018-08-15 17:22:37 UTC,Here is a patch for this fix: https://review.openstack.org/#/c/585373/
1783335,2018-07-24 16:24:56 UTC,"This bug affects me
Thanks"
1783335,2018-07-24 22:30:45 UTC,"This is a must in option.
+1 for me"
1783335,2018-07-25 11:43:25 UTC,+1 is an important feature
1783335,2018-07-25 12:53:04 UTC,One day...
1783335,2018-08-03 22:05:12 UTC,As already reported : +1
1783335,2018-09-21 03:42:04 UTC,+1
1783335,2019-04-25 18:01:00 UTC,Could this be added to Kicad6?
1783335,2019-04-25 18:31:44 UTC,"It would be cool, even more since #1419146 looks already committed for Kicad 6. To me this looks like a feature that has to go with it.
I am very sorry that i can't contribuite myself for the implementation, but my programming skills are basically zero.
I'm grateful to everyone who is writing kicad code! Let us know if there is any chance you'll be able to fit this feature in the kicad 6 schedule"
1783335,2019-10-26 19:04:36 UTC,+1
1783336,2020-02-23 04:17:19 UTC,[Expired for meld (Ubuntu) because there has been no activity for 60 days.]
1783336,2019-12-24 13:56:20 UTC,Thank you for taking the time to report this issue and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1783337,2018-11-10 13:49:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783337,2020-01-16 02:05:30 UTC,With python 3: ModuleNotFoundError: No module named 'mididings'
1783338,2018-08-08 05:58:23 UTC,It seems input start and end dates are not iso8601 format But i cannot tell why we horizon should send date in those format.
1783338,2018-08-08 06:01:19 UTC,"But from the error ""ValueError: year is out of range"" and screenshot of horizon, it seems it is complaining that 2018 is out or range."
1783338,2018-08-08 07:54:56 UTC,"Yep!
After accessing the database, check the tables. I realize that some schools have been brought on for the wrong time. I made a fix, everything was working properly. Very thanks for the support."
1783338,2018-08-09 09:47:38 UTC,"nice, i also tried on master and it is working fine. Anyways let's handle the 500 error here."
1783338,2018-11-05 04:11:11 UTC,"Hello, can you give me step by step to solve the problem? I have the same problem. Thank you,"
1783338,2018-11-09 17:33:42 UTC,"@gmann, do you still plan on working on this? You've been assigned for a few months with no proposed code changes."
1783338,2020-12-14 09:30:31 UTC,what tables and i should change?
1783339,2018-08-15 13:37:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783340,2018-07-31 18:04:08 UTC,This patch solves the issue partly. https://github.com/juju/juju/pull/8993
1783340,2018-08-02 13:17:40 UTC,The PR above has been landed.  The current error is:
1783340,2018-10-04 20:47:24 UTC,"When using lxd provider and juju from the edge channel, this is what I get -> https://pastebin.ubuntu.com/p/z5rd4hpqDH/"
1783340,2019-02-25 08:20:09 UTC,Any updates on this? We are seeing this at a customer deployment.
1783355,2018-07-24 15:32:39 UTC,Syntax is valid POSuX as per https://stackoverflow.com/a/7046926/2171120
1783355,2018-10-20 19:01:18 UTC,"The entire tree printing code is currently not suited for that, a major rewrite is needed."
1783355,2020-10-31 05:37:49 UTC,"fixed in R59c, hopefully without breaking anything more"
1783361,2018-07-24 17:08:25 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1783367,2018-07-24 17:00:18 UTC,This change was made by a bot.
1783367,2018-07-24 18:23:00 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1783367,2018-07-25 03:36:45 UTC,Same as LP: #1779817?
1783369,2020-10-05 09:30:37 UTC,I believed this has got fixed already as skip_path has been dropped by this patch https://review.opendev.org/#/c/692375/ which allows usage of custom registered endpoints.
1783377,2020-12-01 07:46:26 UTC,I would add
1783377,2020-12-01 02:51:04 UTC,This might provide some relief;
1783377,2020-10-23 15:52:03 UTC,I can confirm this in 20.04.1:
1783377,2020-08-17 11:33:10 UTC,Seems like its still a problem in Ubuntu 20.04.1 / focal
1783377,2018-08-30 14:51:32 UTC,A small script to do the job :
1783377,2018-07-25 11:48:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783383,2018-07-24 22:29:08 UTC,I'm not sure I agree with this :)
1783383,2018-12-25 08:04:03 UTC,"@mwhudson you disagree with the displayed behaviour, or you disagree that its a bug?"
1783383,2019-05-30 14:49:43 UTC,One can use 'Reset' but that wipes everything.
1783384,2019-02-27 00:20:44 UTC,I believe 2) would require casper changes as currently it mounts the entire cdrom rather than partition 1 from it and so the kernel won't let you fiddle with the partition table. But I'm not sure about this.
1783384,2019-11-13 21:04:07 UTC,The subiquity in the stable channel collects details about failures into a crash file. casper in eoan+ automatically stores those on the install media in most circumstances. What remains is a better UI around failures in subiquity.
1783384,2018-07-24 22:15:21 UTC,This seems like a good idea. We wanted to do apport integration but I got hung up on how to do authentication iirc.
1783384,2019-02-27 00:19:42 UTC,"So while a log collecting command would be good, I'd rather make ""apport-bug subiquity"" do something useful (and have subiquity auto-invoke it when it or the installation fails)."
1783405,2019-05-21 15:40:09 UTC,"I noticed today that when shutting down an instance, like for a snapshot test, it's sometimes taking a full 60 seconds to wait for the graceful shutdown before just destroying the guest:"
1783405,2019-02-14 19:38:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/637033"
1783405,2019-02-23 06:15:25 UTC,"Reviewed:  https://review.openstack.org/637030
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=b4763ef57e54c4517de88affb983de1de2f0ac64
Submitter: Zuul
Branch:    master"
1783405,2019-02-23 06:15:41 UTC,"Reviewed:  https://review.openstack.org/637033
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=9968315d43bf9fc595d269aafecc78cfdcc06d17
Submitter: Zuul
Branch:    master"
1783405,2019-04-05 14:24:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/650300"
1783405,2019-04-11 16:44:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/651865"
1783405,2019-05-21 16:12:00 UTC,"For the instance that fails to shutdown within 60 seconds in comment 25 I don't see any errors in the libvirtd logs, the shutdown request returns with code 0."
1783405,2020-03-17 14:07:24 UTC,this is something we keep monitoring and if we find the slow test then we mark it slow. we did the complete first phase of this but I will say to keep it open for ussuri cycle in case we find more slow tests.
1783405,2019-09-05 22:41:41 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/650300"
1783405,2019-11-02 02:38:03 UTC,"Reviewed:  https://review.opendev.org/651865
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=f66aea04a51d598f29ff12ae9221d61f426c8d7a
Submitter: Zuul
Branch:    master"
1783405,2020-03-09 19:51:55 UTC,What's the status here? Can it be considered done as https://review.opendev.org/651865 got merged?
1783405,2019-02-14 19:13:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/637030"
1783405,2020-03-17 14:07:56 UTC,"IRC openstack-qa meeting:
gmann: this is something we keep monitoring and if we find the slow test then we mark it slow. we did complete first phase of this but I will say to keep it open for ussuri cycle in case we find more slow tests."
1783405,2020-09-01 13:50:48 UTC,I think we are ok to close this and if any slow tests occur then we can mark that slow. jobs are pretty stable on timeout now.
1783405,2019-05-21 16:25:35 UTC,Reported nova bug 1829896 for the guest shutdown issue.
1783405,2019-02-14 19:12:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/637029"
1783405,2019-02-15 13:49:34 UTC,"Reviewed:  https://review.openstack.org/637029
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=4b8a7b863854b5047d9c6898348c03a40b041688
Submitter: Zuul
Branch:    master"
1783405,2018-12-14 22:14:57 UTC,"Also, the individual openstack-health page for that test is: http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern"
1783405,2018-07-24 20:09:28 UTC,"Note that there are some non-scenario API tests which are also taking a long time, and should maybe be changed to scenario tests:"
1783405,2018-07-24 20:11:41 UTC,This is another very slow API test:
1783405,2018-07-24 20:12:46 UTC,2018-07-23 00:01:51.804344 | controller | {3} tempest.api.compute.servers.test_server_personality.ServerPersonalityTestJSON.test_create_server_with_personality [153.716416s] ... ok
1783405,2018-07-25 05:44:15 UTC,"Yes, there are many tests which taking more times since couple of weeks."
1783405,2018-09-13 15:48:01 UTC,"The last hit was https://access.redhat.com/security/vulnerabilities/L1TF-perf  the impact varies based on cpu firmware and workload.
I would not expect the CI hardware would be renewed very soon. Having slow machines in the pool still better than not having them and seeing occasionally longer job run is still better than failed job.
We should increase the job timeout until the situation does not gets better (~year)."
1783405,2018-09-13 17:14:02 UTC,current tempest-full timeout is 7200sec [1] and most of the timeout we observed is around 8000sec[2].
1783405,2018-09-21 09:19:54 UTC,"Reviewed:  https://review.openstack.org/603900
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=b5720533035734f95e6fc54f60365d64f6a19256
Submitter: Zuul
Branch:    master"
1783405,2018-09-12 23:02:34 UTC,"There were multiple CPU security issue where the mitigation had serious impact to performance this can be the reason.
I wonder can we look into what can be made faster before tempest run.
For ex  osc client invoked serially with a relative slow strategy around devstack..."
1783405,2018-11-07 06:09:46 UTC,"Reviewed:  https://review.openstack.org/615085
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=bd8cc59dc2e362963e82bc797840dd53d19e0d86
Submitter: Zuul
Branch:    master"
1783405,2018-12-13 17:08:07 UTC,"I took 3 recent tempest runs[1][2][3] that timeouted from 3 different node providers. Sorted the tests by execution time, took the 10 long running tests from each run: [4]."
1783405,2018-12-13 18:07:35 UTC,"Thanks gibi. Based on that, it seems we could consider marking these tests as slow:"
1783405,2018-12-14 21:15:46 UTC,"Fwiw, in the future you can use subunit2sql with something like:"
1783405,2019-02-14 18:25:27 UTC,Here is an updated version of mtreinish's test times from the last 300 runs of tempest-full in comment 14:
1783405,2018-12-14 21:21:29 UTC,"(3:08:28 PM) mtreinish: mriedem: fwiw: http://paste.openstack.org/show/737340/ is the average run time of every test over the last 300 runs of tempest-full in gate
(3:19:42 PM) mriedem: mtreinish: ok 2-4 there in that first paste are the same things i identified from gibi's comments in the bug report
(3:19:44 PM) mriedem: so that's good to know
(3:20:01 PM) mriedem: tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern: 161.5385627070707 is the only difference, but that one shouldn't surprise me
(3:20:10 PM) mriedem: kind of surprised that isn't already marked as slow"
1783405,2018-11-02 08:07:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615085"
1783409,2018-08-20 20:42:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783409,2018-08-20 20:42:56 UTC,This happened to me after first boot to a new Ubuntu 18.04 installation.
1783418,2018-08-23 13:23:09 UTC,This bug was fixed in the package linux - 4.15.0-33.36
1783419,2018-07-25 04:10:26 UTC,"The PostgreSQL charm is using Juju provided storage, and Juju is responsible for this."
1783419,2018-11-29 02:38:39 UTC,"I can't see any way that Juju Storage mounts are guaranteed to be mounted before the services that need them start up. This appears to be a race, where it is assumed that jujud starts up and mounts things before the other systemd services on the box start up. We can't use Juju Storage on production unless someone can correct my analysis, or storage mounting is fixed."
1783419,2019-01-07 03:25:22 UTC,https://github.com/juju/juju/pull/9599
1783420,2018-07-29 08:31:26 UTC,Hi Reptorian!
1783420,2018-07-28 21:26:23 UTC,"I think this is not posible :(, anyway trunk fillbetweenmani lines dont duple end and start node of joins use only one."
1783420,2018-07-28 23:06:51 UTC,"Hmm, I guess there needs to be a tool to select all disconnected nodes and assign them as connected without them actually being connected, and they're somewhat connected. That's another idea I have in mind."
1783420,2018-07-25 07:25:41 UTC,"Hi thanks for fill the bug.
You can use fill between many LPE for this."
1783420,2018-07-28 20:55:17 UTC,"I recognize it, but here's the issue. What if say, I want points unified at all times without any sort of lines. A unified tool would fix that issue. Another thing people can benefit from a unified spline tool is that spline creation is faster as you won't need to use that thing as much."
1783423,2018-08-14 16:49:19 UTC,"This is a valid bug, the best solution would be to use the Ansible variables instead."
1783423,2018-08-16 02:38:00 UTC,Here problem is OSA deploying Ubuntu style configuration on CentOS7 and that is why that script get confused how to parse all values.
1783424,2018-07-24 23:11:19 UTC,"Post troubleshooting, it looks like openstack-helm-infra/roles/build-images/tasks/kubeadm-aio.yaml ""Kubeadm-AIO image build path with proxy"" task is building a docker image. This docker image need not to be build by every host in the inventory file."
1783424,2018-07-24 23:23:16 UTC,PR review request https://github.com/openstack/openstack-helm-infra/pull/1
1783427,2019-11-02 15:34:05 UTC,See also: LP:1851049
1783427,2018-12-11 14:55:51 UTC,"According to the man page for pvcreate, the partition table for a device should be erased before use, which can be done via:"
1783427,2018-12-12 14:32:48 UTC,"Reviewed:  https://review.openstack.org/624418
Committed: https://git.openstack.org/cgit/openstack/charms.ceph/commit/?id=31ffa13124edce3490437b73fee5f0432c5eb7f8
Submitter: Zuul
Branch:    master"
1783427,2019-11-02 15:30:28 UTC,"This is not fixed. I just stepped on a reproduction of this:
     2019-10-31 16:04:39 DEBUG secrets-storage-relation-changed partx: /dev/disk/by-dname/osddata5: failed to read partition table
     2019-10-31 16:04:39 DEBUG juju-log secrets-storage:253: get partitions: []
     2019-10-31 16:04:39 DEBUG secrets-storage-relation-changed   Failed to find physical volume ""/dev/bcache6"".
     2019-10-31 16:04:39 WARNING juju-log secrets-storage:253: Support for use of upstream ``apt_pkg`` module in conjunctionwith charm-helpers is deprecated since 2019-06-25
     2019-10-31 16:04:40 DEBUG secrets-storage-relation-changed DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): 172.20.10.53
     2019-10-31 16:04:40 DEBUG secrets-storage-relation-changed DEBUG:urllib3.connectionpool:http://172.20.10.53:8200 ""POST /v1/auth/approle/login HTTP/1.1"" 200 500
     2019-10-31 16:04:40 DEBUG secrets-storage-relation-changed INFO:vaultlocker.dmcrypt:LUKS formatting /dev/disk/by-dname/osddata5 using UUID:861482d7-f7a7-4d97-83ee-95e4b892ed86
     2019-10-31 16:04:43 DEBUG secrets-storage-relation-changed INFO:vaultlocker.dmcrypt:udevadm trigger block/add for /dev/disk/by-dname/osddata5
     2019-10-31 16:04:43 DEBUG secrets-storage-relation-changed INFO:vaultlocker.dmcrypt:udevadm settle /dev/disk/by-uuid/861482d7-f7a7-4d97-83ee-95e4b892ed86
     2019-10-31 16:04:43 DEBUG secrets-storage-relation-changed DEBUG:urllib3.connectionpool:http://172.20.10.53:8200 ""PUT /v1/charm-vaultlocker/ucs-4b-block-2/861482d7-f7a7-4d97-83ee-95e4b892ed86 HTTP/1.1"" 204 0
     2019-10-31 16:04:43 DEBUG secrets-storage-relation-changed DEBUG:urllib3.connectionpool:http://172.20.10.53:8200 ""GET /v1/charm-vaultlocker/ucs-4b-block-2/861482d7-f7a7-4d97-83ee-95e4b892ed86 HTTP/1.1"" 200 866
     2019-10-31 16:04:43 DEBUG secrets-storage-relation-changed INFO:vaultlocker.dmcrypt:LUKS opening 861482d7-f7a7-4d97-83ee-95e4b892ed86
     2019-10-31 16:04:45 DEBUG secrets-storage-relation-changed INFO:root:Enabling systemd unit for vaultlocker-decrypt@861482d7-f7a7-4d97-83ee-95e4b892ed86.service
     2019-10-31 16:04:45 DEBUG secrets-storage-relation-changed Created symlink /etc/systemd/system/multi-user.target.wants/vaultlocker-decrypt@861482d7-f7a7-4d97-83ee-95e4b892ed86.service → /lib/systemd/system/vaultlocker-decrypt@.service.
     2019-10-31 16:04:45 DEBUG secrets-storage-relation-changed 1+0 records in
     2019-10-31 16:04:45 DEBUG secrets-storage-relation-changed 1+0 records out
     2019-10-31 16:04:45 DEBUG secrets-storage-relation-changed 512 bytes copied, 0.000446392 s, 1.1 MB/s
     2019-10-31 16:04:46 DEBUG secrets-storage-relation-changed   Failed to find physical volume ""/dev/mapper/crypt-861482d7-f7a7-4d97-83ee-95e4b892ed86"".
     2019-10-31 16:04:45 DEBUG secrets-storage-relation-changed INFO:root:Enabling systemd unit for vaultlocker-decrypt@861482d7-f7a7-4d97-83ee-95e4b892ed86.service
     2019-10-31 16:04:45 DEBUG secrets-storage-relation-changed Created symlink /etc/systemd/system/multi-user.target.wants/vaultlocker-decrypt@861482d7-f7a7-4d97-83ee-95e4b892ed86.service → /lib/systemd/system/vaultlocker-decrypt@.service.
     2019-10-31 16:04:45 DEBUG secrets-storage-rel..."
1783438,2018-07-26 21:45:04 UTC,"I do have an NVidia GPU, and am using the drivers from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa. However, I noticed on a couple of the other similar bugs that have been reported, this repo can also provide packages that prevent the upgrade from working."
1783447,2018-08-30 03:32:40 UTC,"Idea: We show a set number of pages in the paginator and then if there are more results, show a message along the lines of ""There are more search results. Please refine your search."" so as not to go through all results while trying to find the next paginator. We would cap it at 1,000 results to be displayed."
1783452,2018-07-25 04:25:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1783452,2018-10-29 01:23:00 UTC,I added another screenshot that shows how to easily reproduce this issue using pango-view utility.
1783466,2019-05-30 21:06:36 UTC,This bug already exists in the add_tags.feature file
1783495,2018-07-25 08:34:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585675"
1783498,2018-07-26 14:53:05 UTC,"Hello,"
1783499,2019-05-30 06:31:05 UTC,"I have found that if I set the reboot once at 15 min, the server works for 5-6 days. If the reboots are done once at 10 min, the server get stuck in 24-48h max. Now I'm testing the reboots once at 20min, it should take 10 days or more until is stuck."
1783499,2019-02-20 09:16:36 UTC,"Try kernel parameter ""acpi=off""."
1783499,2019-02-26 07:52:14 UTC,"The test server get stuck after ~9h, here is the debug log."
1783499,2019-02-26 04:28:23 UTC,I think it stuck in firmware/hardware instead of userspace process.
1783499,2019-02-25 15:53:51 UTC,"Tested with multiple OSs, all stuck: Ubuntu 14, Fedora 29, Arch Linux current 2019.02.01."
1783499,2019-02-21 12:46:47 UTC,"This get stuck in max 5 hours. We'll try to install a non systemd Ubuntu, like v14 to test it."
1783499,2019-02-21 08:07:16 UTC,"Or a kernel regression, Centos 7 uses an older kernel."
1783499,2019-02-21 07:12:45 UTC,"We installed Centos 7 and started the reboot test now. If this fail again then is a hardware issue, if not, then it can be from Ubuntu."
1783499,2019-02-20 09:55:13 UTC,"Well, I don't think trials and errors can get any fruitful result, this issue really needs hardware vendor to investigate."
1783499,2019-02-20 09:37:20 UTC,That was already tested and no luck.
1783499,2019-02-26 12:45:32 UTC,"I have activated RuntimeWatchdogSec=20s and ShutdownWatchdogSec=1min in /etc/systemd/system.conf  and set the reboot, the server get stuck in 105min."
1783499,2019-02-14 16:49:54 UTC,"> Any other suggestion from your side?
The system hang in this bug is really hardware related, so HPE needs to take a deeper look.
"
1783499,2019-02-14 15:30:56 UTC,After 5 hours of reboot the server is stuck. See the attached debug log and ILO capture.
1783499,2019-02-20 08:25:19 UTC,"I have disabled the acpi services (acpid.path, acpid.service, acpid.socket  and set up the reboot once at 5 min. The server get stuck after 13h."
1783499,2019-01-18 14:48:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783499,2019-01-18 18:39:07 UTC,"Have you tried other reboot quirk like ""reboot=pci""? It may help."
1783499,2019-01-21 07:01:49 UTC,"I did not tried reboot=pci, will try now. Thanks."
1783499,2019-01-18 14:42:31 UTC,"Here at Mozilla, we have 200 servers running on HP Moonshot system, all have same hardware configuration and Ubuntu 16.04.2. The OS is not up to date, we use it as is was released. We using a program to tests Firefox source code and after each test we reboot the servers using /sbin/reboot. After a while (between 24-48h - during this period ~6 reboots/h are made), randomly, all 200 servers get stuck at the reboot - see the ILO capture - and to bring it back we have to power cycle each of them."
1783499,2019-01-22 07:23:39 UTC,"Please let the hardware vendor know. This is highly likely a platform bug.
AFAICT, systemd has done its part, so the bug is either in the kernel (less likely) or in the BIOS."
1783499,2019-01-23 09:11:48 UTC,"We will notify them if the systemd does not fix the issue. So far, after the systemd upgrade, the server reboots fine in 24h test (reboot once at 5 min)."
1783499,2019-01-25 07:35:13 UTC,"After 36h of rebooting, the system is stuck. Attached is the debug log."
1783499,2019-02-14 07:30:50 UTC,"We sent all the logs and captures data to HPE and they asked to update the BIOS to the latest one. We already using the latest firmware, 4 months past the recommended firmware. Also, we have 200 servers with Windows 10 doing same test - reboot after each test and there are no hangs. HPE stated that they do not have any other reports of hangs on reboots or shutdowns for this hardware."
1783499,2019-01-22 06:59:44 UTC,"reboot=pci does not help, it get stuck after 19 hours (reboot once at 5 min). Attached is the debug log. On ILO we get the same as I sent in my first post - see capture from the arhive."
1783502,2018-07-25 08:01:50 UTC,Upstream bug report: https://code.mythtv.org/trac/ticket/13304
1783502,2018-07-25 08:42:30 UTC,"Patch uses int if the MySQL version is 8.0 or greater, otherwise my_bool."
1783502,2018-07-25 12:25:32 UTC,"The attachment ""mysql-8.0.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1783502,2018-10-01 08:29:31 UTC,"Switching my_bool with int should actually be backwards-compatible, so the earlier patch can be simplified."
1783503,2018-07-25 07:58:29 UTC,Attached screenshot from login.ubuntu.com
1783503,2018-07-25 16:08:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783518,2019-02-26 13:45:41 UTC,Is this still an issue?
1783518,2019-02-26 14:10:45 UTC,Yes this is still an issue ref https://github.com/openstack/tripleo-common#action-development
1783518,2018-08-22 15:44:05 UTC,"Some notes at https://etherpad.openstack.org/p/tripleo-rpm-container-image-notes which I created in response to https://bugs.launchpad.net/tripleo/+bug/1788414, which may actually be a duplicate (or perhaps a more general case) of this bug."
1783518,2018-08-01 13:28:32 UTC,"I don't have a containerised env to test and verify the exact commands, but this sounds like a good approach."
1783518,2018-08-01 13:30:59 UTC,"14:29 <thrash> d0ugal: For instance, '-v $HOME/tripleo-common/tripleo_common:/usr/lib/python2.7/site-packages/tripleo_common'"
1783518,2018-08-20 13:42:25 UTC,"I am working on a similar issue with a new feature for stein which takes place on a containerized undercloud. I will take some notes once I iron out all the details for my dev environment, aka not hacked together to get something working."
1783523,2019-01-02 19:37:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783532,2019-09-05 11:36:17 UTC,"This got fixed in one of the two previous releases with major reworks done, so marking this as 'fix released'"
1783532,2018-07-26 02:13:53 UTC,Trace from Slave (18.04)
1783533,2018-07-27 11:33:21 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1783533,2018-07-27 12:00:04 UTC,This change was made by a bot.
1783543,2020-02-16 17:58:17 UTC,"For 18.04 LTS, 19.10 and upcoming 20.04 LTS we can simply use"
1783543,2018-07-25 13:09:45 UTC,As I have already wrote on AskUbuntu ( https://askubuntu.com/a/1059325/66509 ) - copying flags to ~/.icons/flags or upgrading to MATE 1.16 from xenial-mate PPA solves the problem.
1783543,2020-02-16 10:43:08 UTC,Does this work in 18.04 or newer?
1783546,2018-07-25 12:26:37 UTC,Related with https://bugs.launchpad.net/kicad/+bug/1460787
1783546,2019-08-15 13:36:26 UTC,Many of these have been fixed through the linked bug report.
1783546,2019-08-15 23:42:53 UTC,"@Jeff, really got an improvement.
The 1-to-5 are marked into the Cmts.User layer. Just some comments about, as you said, some can't fixed due performance."
1783546,2019-08-16 09:59:13 UTC,(1) I think this one would be exceedingly difficult to fix even without performance constraints.
1783546,2019-08-17 00:49:11 UTC,"I am attaching the idea of ""smoothing internal corners""."
1783549,2018-07-30 07:13:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783552,2018-07-26 18:16:14 UTC,"Reviewed:  https://review.openstack.org/585734
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=749acdfa8e9bc5c726079095a49e88c324b44b07
Submitter: Zuul
Branch:    master"
1783552,2018-07-25 12:27:29 UTC,Example link: http://logs.openstack.org/19/584119/10/check/tripleo-ci-centos-7-undercloud-containers/a484cee/logs/quickstart_collect_logs.log
1783552,2018-07-25 12:39:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585734"
1783552,2021-02-17 17:08:54 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1783562,2018-11-30 23:14:51 UTC,"it's also buggy in Ubuntu Ubuntu 16.04.5 LTS. I solve with remove or modifying name of grub-pc.postinst to grub-pc.postinst.buggy. But sometimes if you update your ubuntu, the grub-pc.postinst is back to /var/lib/dpkg/info, and you're getting same error."
1783562,2020-01-06 09:06:31 UTC,Same state as @nik-weter above.
1783562,2018-08-16 13:20:15 UTC,Thanks Nikolay.  Are you sure that grep -v line was the very last line?  I don't see how the script can possibly error out at that point.
1783562,2018-07-25 19:06:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783562,2018-08-09 13:56:24 UTC,Please open a terminal and do the following:
1783562,2018-08-15 03:52:35 UTC,"Настраивается пакет grub-pc (2.02-2ubuntu8.2) …
+ cached_available_ids=
+ case ""$1"" in
+ . /usr/share/debconf/confmodule
++ '[' '!' '' ']'
++ PERL_DL_NONLAZY=1
++ export PERL_DL_NONLAZY
++ '[' '' ']'
++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/grub-pc.postinst configure 2.02-2ubuntu8
+ cached_available_ids=
+ case ""$1"" in
+ . /usr/share/debconf/confmodule
++ '[' '!' 1 ']'
++ '[' -z '' ']'
++ exec
++ '[' '' ']'
++ exec
++ DEBCONF_REDIR=1
++ export DEBCONF_REDIR
+ devicemap_regenerated=
+ egrep -q '^[[:space:]]*post(inst|rm)_hook[[:space:]]*=[[:space:]]*(/sbin/|/usr/sbin/)?update-grub' /etc/kernel-img.conf
+ case grub-pc in
+ mkdir -p /boot/grub
+ test -e /boot/grub/device.map
+ test -z ''
+ test -s /boot/grub/device.map
+ test -z ''
+ dpkg --compare-versions 2.02-2ubuntu8 lt-nl 1.99~20101210-2
++ mktemp -t grub.XXXXXXXXXX
+ tmp_default_grub=/tmp/grub.Q94e5IZZXU
+ trap 'rm -f /tmp/grub.Q94e5IZZXU' EXIT
+ cp -p /usr/share/grub/default/grub /tmp/grub.Q94e5IZZXU
+ merge_debconf_into_conf /tmp/grub.Q94e5IZZXU GRUB_CMDLINE_LINUX grub2/linux_cmdline
+ local tmpfile
+ tmpfile=/tmp/grub.Q94e5IZZXU
+ local setting
+ setting=GRUB_CMDLINE_LINUX
+ local template
+ template=grub2/linux_cmdline
+ db_get grub2/linux_cmdline
+ _db_cmd 'GET grub2/linux_cmdline'
+ _db_internal_IFS='
'
+ IFS=' '
+ printf '%s\n' 'GET grub2/linux_cmdline'
+ IFS='
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ local value
++ echo ''
++ sed -e 's,[$`""\],\\&,g'
+ value=
+ grep -q '^GRUB_CMDLINE_LINUX=' /tmp/grub.Q94e5IZZXU
++ echo ''
++ sed -e 's,[\@],\\&,g'
+ value=
+ sed -i -re 's@^(GRUB_CMDLINE_LINUX=).*@\1""""@' /tmp/grub.Q94e5IZZXU
+ merge_debconf_into_conf /tmp/grub.Q94e5IZZXU GRUB_CMDLINE_LINUX_DEFAULT grub2/linux_cmdline_default
+ local tmpfile
+ tmpfile=/tmp/grub.Q94e5IZZXU
+ local setting
+ setting=GRUB_CMDLINE_LINUX_DEFAULT
+ local template
+ template=grub2/linux_cmdline_default
+ db_get grub2/linux_cmdline_default
+ _db_cmd 'GET grub2/linux_cmdline_default'
+ _db_internal_IFS='
'
+ IFS=' '
+ printf '%s\n' 'GET grub2/linux_cmdline_default'
+ IFS='
'
+ IFS='
'
+ read -r _db_internal_line
+ RET='quiet splash'
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ local value
++ echo 'quiet splash'
++ sed -e 's,[$`""\],\\&,g'
+ value='quiet splash'
+ grep -q '^GRUB_CMDLINE_LINUX_DEFAULT=' /tmp/grub.Q94e5IZZXU
++ echo 'quiet splash'
++ sed -e 's,[\@],\\&,g'
+ value='quiet splash'
+ sed -i -re 's@^(GRUB_CMDLINE_LINUX_DEFAULT=).*@\1""quiet splash""@' /tmp/grub.Q94e5IZZXU
+ case grub-pc in
+ merge_debconf_into_conf /tmp/grub.Q94e5IZZXU GRUB_TIMEOUT grub-pc/timeout
+ local tmpfile
+ tmpfile=/tmp/grub.Q94e5IZZXU
+ local setting
+ setting=GRUB_TIMEOUT
+ local template
+ template=grub-pc/timeout
+ db_get grub-pc/timeout
+ _db_cmd 'GET grub-pc/timeout'
+ _db_internal_IFS='
'
+ IFS=' '
+ printf '%s\n' 'GET grub-pc/timeout'
+ IFS='
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=10
+ case ${_db_internal_line%%[ 	]*} in
+ return 0
+ local value
++ sed -e 's,[$`""\],\\&,g'
++ echo 10
+ value=10
+ grep -q '^GRUB_TIMEOUT=' /tmp/grub.Q94e5IZZXU
++ echo 10
++ sed -e 's,[\@],\\&,g'
+ value=10
+ sed -i -re 's@^(GRUB_TIMEOUT=).*@\1""10""..."
1783565,2020-02-25 12:13:18 UTC,This issue was fixed in the openstack/nova 18.3.0 release.
1783565,2020-02-06 12:45:15 UTC,This issue was fixed in the openstack/nova 19.1.0 release.
1783565,2020-02-06 12:41:01 UTC,This issue was fixed in the openstack/nova 20.1.0 release.
1783565,2019-12-06 01:50:02 UTC,"Reviewed:  https://review.opendev.org/696217
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ffce5be5cae59969ec5ecf7e2b36ae4ec87c29d1
Submitter: Zuul
Branch:    stable/rocky"
1783565,2019-11-27 00:43:36 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/696217"
1783565,2019-11-27 00:35:55 UTC,"Reviewed:  https://review.opendev.org/696175
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=92eb45ba5eb413400e1789f09d3739ee8c0b77de
Submitter: Zuul
Branch:    stable/stein"
1783565,2019-11-26 19:58:15 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/696175"
1783565,2019-11-26 13:58:27 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/696088"
1783565,2019-11-26 18:54:51 UTC,"Reviewed:  https://review.opendev.org/696088
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a5daa0ddb3129ddd1bea4e85570c047fc2912b1a
Submitter: Zuul
Branch:    stable/train"
1783565,2019-11-08 16:14:40 UTC,"Reviewed:  https://review.opendev.org/692252
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c93ca82b8fb8e39787020decfe335d45f8732e7
Submitter: Zuul
Branch:    master"
1783565,2019-11-08 15:16:29 UTC,"Oops, it was Mel's patch, gibi was +2 on it. My mistake."
1783565,2019-11-08 15:09:04 UTC,gibi has a fix here: https://review.opendev.org/692252
1783565,2019-10-07 14:50:46 UTC,We don't seem to be hitting this in the gate anymore so I'm not sure if it's just rare now or if it's resolved some other way:
1783565,2019-10-07 13:46:47 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/585978
Reason: Looks like we need another approach here. Going to abandon this as a result"
1783565,2018-07-26 14:48:44 UTC,"I was also thinking we could just force the service down before evacuate rather than stop the service; we have other evacuate tests that don't stop the service, they just force it down."
1783565,2018-07-26 07:31:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/585978"
1783565,2018-07-26 06:14:20 UTC,"After some check and test, the only reason I can think of is the sleep time is not good, as
sleep time and service_down_time is the same, maybe sometime when we post evacuate action
the service record did not got updated."
1783565,2019-11-26 13:57:35 UTC,This might be another example of this in rocky:
1783573,2018-07-25 14:18:37 UTC,This probably affects only that patch or that job. I cannot see this issue affecting arbitrary CI jobs for other patches.
1783573,2018-07-26 08:19:35 UTC,It seems it is related to https://bugs.launchpad.net/tripleo/+bug/1781227
1783575,2018-08-14 08:28:18 UTC,I cannot reproduce this bug..
1783576,2018-09-24 08:00:59 UTC,"Actually this command only made sense when running nova-network instead of Neutron, which isn't an option anymore. I'll do a test-run of the complete lab before putting up a patch."
1783578,2018-07-25 14:26:29 UTC,Or get rid of nautilus and switch to a file browser that is not maintained by idiots.
1783579,2018-09-03 18:56:59 UTC,"True, as if its authors happily forgot that ppp/pppoe/pptp is still widely used all over the world
Also, systemd-networkd authors look similar."
1783579,2018-09-03 18:54:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783588,2019-06-26 15:44:23 UTC,"Reviewed:  https://review.opendev.org/606959
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=12a7bf699df1558f081513b1686d9c389bd3b812
Submitter: Zuul
Branch:    master"
1783588,2019-09-27 09:04:08 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1783588,2020-05-07 23:20:10 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/726262"
1783588,2020-07-06 20:50:43 UTC,"Reviewed:  https://review.opendev.org/726262
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=6bcb6fea741267b72175e5936c6f6a656fb2fffc
Submitter: Zuul
Branch:    stable/stein"
1783591,2018-07-30 19:51:31 UTC,Updated CVE paperwork:
1783591,2018-07-30 19:58:49 UTC,master: CVE 2018-6556: verify netns fd in lxc-user-nic
1783591,2018-07-30 19:59:22 UTC,stable-3.0: CVE 2018-6556: verify netns fd in lxc-user-nic
1783591,2018-07-30 20:00:03 UTC,stable-2.0: CVE 2018-6556: verify netns fd in lxc-user-nic
1783591,2018-07-30 20:06:48 UTC,"@Security team: We're now ready with this one. Can you send notifications to the distros list about this issue, including the 3 patches above (master, 2.0 and 3.0) and communicate a CRD of Monday 6th of August at 16:00 UTC?"
1783591,2018-07-31 14:04:22 UTC,I have sent the following to the linux-distros list:
1783591,2018-08-02 02:34:09 UTC,Packages ready in our private PPAs:
1783591,2018-08-02 11:13:05 UTC,Does that PPA build with -updates disabled?
1783591,2018-08-02 16:52:03 UTC,"@Marc, our security PPAs build with only -security enabled, except for the backports one which builds with -backports enabled (obviously)."
1783591,2018-08-05 15:19:45 UTC,"@Christian: Something is weird with the stable-2.0 patch. It applies cleanly, but doesn't compile because it refers to LXC_PROC_PID_FD_LEN which doesn't exist and isn't added to the patch, so the code doesn't compile. I can fix the build by adding this line in utils.h:"
1783591,2018-08-05 19:14:46 UTC,"Thanks, we (Gentoo Linux) are now prepared and are waiting for the end of the embargo."
1783591,2018-08-05 15:55:47 UTC,"@Thomas, in case you want to cherry pick this into another distro I'm appending you the patch for stable-2.0 here. :)"
1783591,2018-08-06 16:01:07 UTC,This bug was fixed in the package lxc - 3.0.1-0ubuntu1~18.04.2
1783591,2018-08-06 16:02:00 UTC,This bug was fixed in the package lxc - 3.0.1-0ubuntu2
1783591,2018-08-30 22:07:08 UTC,If you think that you have found an actual security bug please file it as a new one to follow best security practices.
1783591,2018-08-06 16:14:23 UTC,New version to apply cleanly to master.
1783591,2018-08-06 16:16:52 UTC,All supported upstream branches have been updated with the fix.
1783591,2018-08-06 16:29:41 UTC,Upstream communication: https://lists.linuxcontainers.org/pipermail/lxc-devel/2018-August/018336.html
1783591,2018-08-30 20:02:56 UTC,"One can still test existence of files with those patches, but I guess this was explicitly not part of the fixes?"
1783591,2018-08-30 21:50:35 UTC,"On Thu, Aug 30, 2018 at 08:02:56PM -0000, Salvatore Bonaccorso wrote:

> One can still test existence of files with those patches, but I guess
> this was explicitly not part of the fixes?
"
1783591,2018-08-05 15:44:07 UTC,"On Sun, Aug 05, 2018 at 03:19:45PM -0000, Thomas Deutschmann wrote:

> @Christian: Something is weird with the stable-2.0 patch. It applies
> cleanly, but doesn't compile because it refers to LXC_PROC_PID_FD_LEN
> which doesn't exist and isn't added to the patch, so the code doesn't
> compile. I can fix the build by adding this line in utils.h:
>
> #define LXC_PROC_PID_FD_LEN (6 + LXC_NUMSTRLEN64 + 4 + LXC_NUMSTRLEN64 +
> 1)
"
1783591,2018-07-30 19:48:11 UTC,"Once the CVE numbers are assigned the patches should both
reference them. So before pushing them upstream, please add
a reference either in the title of the commit message or the
body of the commit message."
1783591,2018-08-06 16:04:25 UTC,Also released to xenial-backports.
1783591,2018-07-30 16:57:16 UTC,CRD to be set for Monday 6th of August at 16:00 UTC.
1783591,2018-07-30 19:46:47 UTC,"Version of the patch for stable-2.0 branch.
It does not contain any changes. It only just adjusts the path
in the diff from src/lxc/cmd/lxc_user_nic.c to src/lxc/lxc_user_nic.c"
1783591,2018-07-25 15:21:44 UTC,Current thought is that we could statvfs the resulting path to make sure that the filesystem is nsfs and not even attempt an open if it's not the case.
1783591,2018-07-25 15:25:09 UTC,"For Ubuntu specifically:
 - precise: unaffected (0.7.5 or 1.0.9)
 - trusty: unaffected (1.0.10 or 2.0.8)
 - xenial: backports only (2.0.8 or 3.0.1)
 - bionic: affected (3.0.1)
 - cosmic: affected (3.0.1)"
1783591,2018-07-25 15:35:19 UTC,Ideal CRD for us would be the 6th (Monday) of August.
1783591,2018-07-26 00:55:03 UTC,It'd be great if we could get reviews on this patch by:
1783591,2018-07-26 10:17:58 UTC,Hello and thanks for the quick patch. I will review it today and report back.
1783591,2018-07-26 11:49:43 UTC,"On Thu, Jul 26, 2018 at 10:17:58AM -0000, Matthias Gerstner wrote:

> Hello and thanks for the quick patch. I will review it today and report
> back.
"
1783591,2018-07-26 11:51:27 UTC,I have looked at the patch and security wise it looks very good to me. For completeness I would also add the O_CLOEXEC i.e.:
1783591,2018-07-26 12:08:44 UTC,"On Thu, Jul 26, 2018 at 11:51:27AM -0000, Matthias Gerstner wrote:

> I have looked at the patch and security wise it looks very good to me.
> For completeness I would also add the O_CLOEXEC i.e.:
>
> netns_fd = open(args.pid, O_PATH | O_CLOEXEC);
"
1783591,2018-07-26 12:35:38 UTC,"Here's the updated version that switches from fstatvfs() to fstatfs()
to reuse infrastructure we already have and to correctly check for the fs type.
The logic stays the same:"
1783591,2018-07-25 18:11:03 UTC,"I think I have a patch:
1. open() O_PATH fd which won't trigger an actual open()
2. fstatvfs() the O_PATH fd and verify that f_fsid == NSFS_MAGIC
3. build proc path to the O_PATH fd and reopen O_PATH fd with O_RDONLY | O_CLOEXEC
4. perform setns(netns_fd, CLONE_NEWNET) (which will fail on anything else than an actual netns fd"
1783591,2018-07-26 12:45:09 UTC,Here's the correct patch including the missing O_CLOEXEC flag for the O_PATH fd.
1783591,2018-07-26 14:52:11 UTC,"The updated patch looks good to me. As it happens I also misread the open man page initially, so probably the wording is difficult to follow ;-)."
1783591,2018-07-26 23:52:30 UTC,"Hi,"
1783591,2018-07-27 09:53:11 UTC,"On Thu, Jul 26, 2018 at 11:52:30PM -0000, Serge Hallyn wrote:

> Hi,
>
> looks good, my only complaint would be that the WARN message in
> fhas_fs_type() doesn't seem clear.  I'd offer an alternative but I don't
"
1783591,2018-07-27 10:31:24 UTC,"Here's the updated patch that removes the WARN() from fhas_fs_type().
This is a non-functional and the only change."
1783591,2018-07-30 03:25:06 UTC,"Matthias, Serge: can you review the updated patch?"
1783591,2018-07-30 09:40:35 UTC,I reviewed the patch once more. Since it's only a minor change it still looks good to me.
1783591,2018-07-30 14:14:36 UTC,"lgtm, thanks."
1783591,2018-07-30 15:30:05 UTC,"Cool, thanks everyone! :)"
1783591,2018-07-30 16:56:48 UTC,CVE paperwork:
1783591,2018-07-26 12:43:22 UTC,"Fwiw, I misread the open manpage."
1783592,2018-07-25 15:32:29 UTC,"It appears that this may only be something we can check timestamp of the ""disk"" file within the instance directory."
1783595,2019-12-11 04:01:47 UTC,https://github.com/juju/juju/pull/11015
1783595,2019-12-10 06:36:06 UTC,https://github.com/juju/bundlechanges/pull/59
1783595,2019-09-04 08:03:11 UTC,Adding the series stops the panic:
1783595,2018-07-25 15:30:29 UTC,I switched to absolute paths and it worked.
1783595,2018-07-25 22:37:25 UTC,"I'm fairly sure that relative paths do work but are relative to the bundle, not the current working directory."
1783595,2019-09-04 07:56:45 UTC,"$ juju --version
2.6.8-bionic-amd64"
1783596,2019-08-10 16:46:17 UTC,according to the manual page you must have a space between -s and all:
1783597,2019-10-08 19:32:55 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of ubuntu-release-upgrader from disco-proposed was performed and bug 1847313 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed-disco"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1847313 (not this bug). Thanks!"
1783597,2019-10-09 17:18:27 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1783597,2019-10-09 17:18:14 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.16.7
1783597,2019-10-09 13:57:42 UTC,"Ok, so I used my own system to verify that update-manager is still working. I have upgraded ubuntu-release-upgrader packages to the version in disco-proposed and ran update-manager. I was able to successfully install all upgrades."
1783597,2019-10-09 13:06:34 UTC,Verified ubuntu-release-upgrader 19.04.16.7 as per the test-case.
1783597,2019-10-09 11:14:34 UTC,"The above bug does not seem to be related to any of the changes provided by the SRU. The mainlog there mentions:
2019-10-08 14:12:33,569 ERROR No 'ubuntu-minimal' available/downloadable after sources.list rewrite+update
2019-10-08 14:12:33,569 ERROR 'ubuntu-minimal' was not downloadable"
1783597,2019-09-30 17:00:52 UTC,"Hello Sebastien, or anyone else affected,"
1783597,2019-09-04 16:22:53 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.11
1783597,2019-09-09 12:06:54 UTC,Hello. Just so that the relevant people see it - this upload would appear to cause the install button in update-manager to stop working as per https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1843076
1783597,2019-06-20 15:30:25 UTC,"FWIW, same for APT and any kind of installer debs"
1783597,2019-05-17 20:51:04 UTC,"Maybe we want to also revise the minimal disk space calculations for installers, in case there's a bit more space needed for preinstalled snaps?"
1783597,2018-08-01 22:49:19 UTC,As an interim solution I've modified the release-upgrader to clean up the downloaded debs before installing the snaps.
1783597,2018-07-27 22:52:13 UTC,"Given that the snaps are located in /var/lib/snapd and we currently allocate free space to download debs in /var/cache/apt/archives and that it is a corner case for those to not be the same mount point it is likely that the space allocated for /var/cache/apt/archives would be enough free space.  However, the release upgrader doesn't currently clean up the download .debs at all let alone before installing the snaps. So one solution would be to have the release upgrader clean up after itself."
1783597,2019-09-11 12:41:14 UTC,Just leaving a note here for the purposes of the SRU: the regression mentioned in #6 has been fixed and the package in disco Unapproved modified to include the fix. The current package in the queue should be good for review. I'll modify the test case to make sure we check that update-manager is still working after upgrade.
1783599,2018-10-24 20:29:43 UTC,"Seem to have missed this bug report - sorry. I think I will have to look at how the app handles times, as this also happens with GMT+1 (British Summer Time)"
1783604,2018-08-12 13:18:45 UTC,"Hmm, well there is an empty string check, but then we run sed on it, which might result in an empty string:"
1783610,2018-07-25 17:39:12 UTC,The upstream fix for this has included moving on to depending strictly on later versions of GnuTLS.
1783610,2018-07-27 18:17:27 UTC,Copying from what I wrote on the openconnect-devel mailing list…
1783613,2018-07-25 17:28:52 UTC,This bug does not exist on the master branch.
1783613,2018-08-03 00:58:55 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/588416"
1783613,2018-08-09 01:37:03 UTC,"Reviewed:  https://review.openstack.org/588416
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3120f40f636ab4cbdcb9f5cd4e9175e99e1e1c63
Submitter: Zuul
Branch:    stable/ocata"
1783613,2018-08-09 22:32:00 UTC,"Reviewed:  https://review.openstack.org/582413
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=456b3d68bc491a6965316e6a4f3fc11dd509237b
Submitter: Zuul
Branch:    stable/ocata"
1783613,2018-09-26 10:43:43 UTC,This issue was fixed in the openstack/nova 15.1.4 release.
1783623,2020-10-23 16:09:51 UTC,"Hi,
Sorry, but not possible now.
Best regards."
1783623,2018-07-25 20:58:35 UTC,"I suggest gufw store what it uses for 'Name' in the comment in some manner. Note to gufw developers, under the hood the comment is hex encoded (see hex_encode()/hex_decode() from src/util.py in the ufw sources if needed)."
1783624,2018-07-26 02:43:03 UTC,It sounds like you might be reporting two issues:
1783624,2018-07-27 10:31:20 UTC,Please provide the output of vlc -vvv when trying to play the DVD.
1783624,2018-07-27 17:32:16 UTC,"VLC media player is now working-OK. Thank-you
But still cannot access programs in Ubuntu Software?
Only displays Editor's Choice?"
1783624,2018-07-28 10:00:43 UTC,"Okay, reassigning to software-center."
1783624,2018-07-31 08:13:50 UTC,Ubuntu Software and Ubuntu Software Center are different apps.
1783629,2018-07-29 00:57:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783630,2019-08-14 16:09:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676450"
1783630,2019-08-15 07:16:09 UTC,"Reviewed:  https://review.opendev.org/676450
Committed: https://git.openstack.org/cgit/openstack/oslo.log/commit/?id=500788981e1abcd5a495badac350285e39f993a4
Submitter: Zuul
Branch:    master"
1783630,2019-08-29 09:44:08 UTC,This issue was fixed in the openstack/oslo.log 3.44.1 release.
1783632,2018-07-26 16:51:53 UTC,I have published an update which ignored the removed options. Thanks for reporting this issue and providing details!
1783632,2018-07-26 16:36:21 UTC,This bug was fixed in the package clamav - 0.100.1+dfsg-1ubuntu2
1783632,2018-07-26 15:53:19 UTC,This bug was fixed in the package clamav - 0.100.1+dfsg-1ubuntu0.16.04.2
1783632,2018-07-26 23:21:23 UTC,Thanks for the updated package.
1783632,2018-07-26 15:43:11 UTC,This bug was fixed in the package clamav - 0.100.1+dfsg-1ubuntu0.14.04.2
1783632,2018-07-26 14:50:13 UTC,"Marc,
I manually changed clamd.conf. There was no indication from the installer that there was any changes to clamd.conf. The only indication I had was when the Thunderbird extension, clamrib, complained it couldn't connect to clamd. I checked clamd and indeed it was not running. I tried to restart it using the System V init script. It complained about an unknown option StatsEnabled. So I commented out StatsEnabled. and tried to start clamd. It compained about the option StatsTimeout. So I commented it out and repeated this process until clamd started.
Releasing an update warning about changes for user modified clamd.conf should be a good solution.
Thanks for the prompt work on this."
1783632,2018-07-26 15:43:11 UTC,This bug was fixed in the package clamav - 0.100.1+dfsg-1ubuntu0.18.04.2
1783632,2018-07-26 13:57:25 UTC,"When the update was installed, did you get prompted about how to handle the manual modifications to the clamd.conf file?"
1783632,2018-07-26 13:45:27 UTC,"Did you manually modify your clamd.conf file, or did you modify it using dpkg-reconfigure as mentioned at the top of the file?"
1783632,2018-07-26 13:11:52 UTC,"I can confirm this in 14.04.5 Trusty. Attached is the apt log /var/log/apt/term.
A quick work around was to comment out these lines in /etc/clamav/clamd.conf
#StatsEnabled false
#StatsPEDisabled true
#StatsHostID auto
#StatsTimeout 10"
1783632,2018-07-26 12:47:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783632,2018-07-25 23:45:26 UTC,/etc/clamav/clamd.conf is in fact supposed to get regenerated by the clamav-daemon postinst.
1783632,2018-07-26 14:29:37 UTC,I will release an update today that warns about the options removed in the new version instead of failing to start when using a configuration file that was manually edited.
1783633,2018-07-27 17:08:06 UTC,for develop: https://github.com/juju/juju/pull/8984
1783633,2020-02-26 22:38:26 UTC,Marking as Won't Fix for 2.4 series since we are not planning to make any further releases in this series at this stage.
1783635,2018-08-28 01:45:00 UTC,"@Marek,"
1783635,2018-08-09 14:47:49 UTC,"Hi, is this depending on any other changes? I have a pike installation but all migrations are stuck at 1024kb/sec per host on outgoing migrations. Incoming migrations are not capped.
This is after changing the suggested stanza."
1783635,2018-07-30 17:39:51 UTC,"Reviewed:  https://review.openstack.org/586965
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e0f1c2cbfd46c0dad72a7f0fb0a1c7fb91fd0c6b
Submitter: Zuul
Branch:    stable/pike"
1783635,2018-07-30 15:03:41 UTC,"Thanks Matt,"
1783635,2018-07-26 00:15:10 UTC,The error is from libvirt driver calling `guest.migrate_configure_max_speed` here:
1783635,2018-07-26 01:37:18 UTC,Why this beautiful fix not backported to pike?
1783635,2018-07-26 01:36:47 UTC,"After adding following stanza in guest.py file it works, Thanks you Jorden!"
1783635,2018-09-24 14:46:44 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1783635,2018-07-30 14:55:23 UTC,There is a patch here: https://review.openstack.org/#/c/586965/
1783639,2018-08-06 22:32:04 UTC,"Hey vmc, thanks for the report!"
1783639,2018-08-06 23:18:28 UTC,"System:    Host: vmc-pc Kernel: 4.17.0-6-generic x86_64 bits: 64 Desktop: LXQt 0.13.0
           Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine:   Type: Desktop System: HP-Pavilion product: AY652AA-ABA s5310y v: N/A serial: <root required>
           Mobo: PEGATRON model: Narra6 v: 6.01 serial: <root required> BIOS: American Megatrends v: 5.17
           date: 01/07/2010
CPU:       Topology: Dual Core model: AMD Athlon II X2 250 bits: 64 type: MCP L2 cache: 2048 KiB
           Speed: 800 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 800 2: 800
Graphics:  Card-1: NVIDIA C61 [GeForce 6150SE nForce 430] driver: nouveau v: kernel
           Display: server: X.Org 1.19.6 driver: nouveau unloaded: fbdev,modesetting,vesa
           resolution: 1600x900~60Hz
           OpenGL: renderer: NV4C v: 2.1 Mesa 18.1.3
Audio:     Card-1: NVIDIA MCP61 High Definition Audio driver: snd_hda_intel
           Card-2: Pixart Imaging type: USB driver: uvcvideo,snd-usb-audio
           Sound Server: ALSA v: k4.17.0-6-generic
Network:   Card-1: NVIDIA MCP61 Ethernet type: network bridge driver: forcedeth
           IF: enp0s7 state: up speed: 100 Mbps duplex: full mac: e0:cb:4e:9b:e8:4d
Drives:    Local Storage: total: 931.51 GiB used: 4.57 GiB (0.5%)
           ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-00ZF5A0 size: 931.51 GiB
Partition: ID-1: / size: 95.62 GiB used: 4.57 GiB (4.8%) fs: ext4 dev: /dev/sda7
           ID-2: swap-1 size: 1.95 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 32.5 C mobo: N/A
           Fan Speeds (RPM): N/A
Info:      Processes: 150 Uptime: 26m Memory: 3.61 GiB used: 674.0 MiB (18.3%) Shell: bash inxi: 3.0.20"
1783639,2018-07-25 20:34:40 UTC,crash attachment
1783641,2018-07-25 20:56:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783641,2018-07-25 20:58:15 UTC,"Instead of:
there are no keys for the files whose name begins with ""Announce""
please read:
there are no keys for the fields whose name begins with ""Announce"""
1783641,2020-02-27 22:28:06 UTC,This bug was fixed in the package orca - 3.35.3-1ubuntu1
1783642,2018-09-07 17:16:49 UTC,"We do most of our renewing from Items Out so I agree with this. Also, you should be able to print Renew Receipts from Items Out. Item Receipts aren't quite the same. Finally, there does not appear to be an email option in Renew Item."
1783642,2018-11-01 13:17:05 UTC,"Our libraries would love to see the option to email due date receipts from Items Out - both as renewal receipts, or as staff triggered reminders. Staff at multiple libraries have commented that patrons like to get lists of their current checkouts and due dates (rather than, I guess, look at their online accounts)."
1783645,2018-09-09 18:44:13 UTC,"This would be quite useful for the ""Top Spending"" chart on the main window."
1783645,2020-08-31 19:31:00 UTC,from #1892607: spending drill down
1783668,2018-08-14 16:41:21 UTC,Is the utility_all populated? Could we see the inventory?
1783668,2018-08-14 16:41:43 UTC,Which branch is that?
1783668,2018-07-26 16:46:46 UTC,I had noticed this as well. I am currently testing merging the inventory files in my snapshot work. If I can get it done there I will try to fix it here as well.
1783673,2018-07-26 02:27:56 UTC,"StacktraceTop:
 clutter_input_device_xi2_get_current_tool (device=device@entry=0x0) at x11/clutter-input-device-xi2.c:292
 clutter_device_manager_xi2_translate_event (translator=<optimized out>, native=<optimized out>, event=0x55f5fd65a970) at x11/clutter-device-manager-xi2.c:1625
 clutter_backend_real_translate_event (backend=<optimized out>, native=0x7ffd82ef0b60, event=0x55f5fd65a970) at clutter-backend.c:597
 clutter_x11_handle_event (xevent=xevent@entry=0x7ffd82ef0b60) at x11/clutter-event-x11.c:200
 handle_host_xevent (event=0x7ffd82ef0b60, backend=0x55f5fb776110) at backends/x11/meta-backend-x11.c:383"
1783673,2018-07-26 02:47:09 UTC,"It appears a few people experience the same crash:
https://errors.ubuntu.com/problem/4da1b43d4e01e82127276108c1e6c2169c68410f"
1783673,2018-07-26 02:47:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783682,2018-07-26 05:05:16 UTC,What is the output of 'dpkg -S /usr/share/package-data-downloads/*' on your system?
1783682,2018-07-26 07:48:25 UTC,"sudo dpkg -S /usr/share/package-data-downloads/*
dpkg-query: не найден путь, подходящий под шаблон /usr/share/package-data-downloads/ttf-mscorefonts-installer_3.6_all.deb"
1783689,2018-07-27 15:27:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783689,2018-07-27 15:29:41 UTC,"I ran into this as well on a Dell Precision 5520. I tried all the fixes listed at https://help.ubuntu.com/community/SoundTroubleshootingProcedure and nothing worked. Only reverting to the 4.4.0-130-generic kernel partially fixed the problem, but sound still breaks when I suspend/resume."
1783710,2018-12-12 12:49:36 UTC,Thank you for your bug report. What laptop/touchpad model do you use? What buttons are you talking about exactly?
1783710,2018-12-12 13:26:46 UTC,"xinput --list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                	id=13	[slave  pointer  (2)]"
1783736,2020-10-14 01:27:04 UTC,Picking this bug up since it's still a valid concern in manila.
1783736,2018-07-27 07:07:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586456"
1783749,2018-08-02 08:43:05 UTC,I could not locate any duplicate. I would be glad and grateful if you can locate and inform the same.
1783749,2018-08-27 06:21:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783751,2018-07-27 06:20:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586448"
1783751,2018-07-27 07:55:37 UTC,"@Manik, I apologize I missed you're already assigned. So, feel free to take over this or upload your patch."
1783751,2018-09-10 18:17:40 UTC,"Reviewed:  https://review.openstack.org/586448
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=79159f80a9c0fec65637d498079e1b8958df8fb7
Submitter: Zuul
Branch:    master"
1783751,2018-10-03 12:59:36 UTC,"Reviewed:  https://review.openstack.org/586950
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=321c85c87cf7cd7ac3c94c35c18ced71d6008c67
Submitter: Zuul
Branch:    master"
1783751,2020-03-23 14:00:54 UTC,A fix has been released and the issue is no more reproducible.
1783751,2020-03-23 14:01:27 UTC,verification output
1783753,2018-08-11 19:09:01 UTC,"Nice, I already saw the implementation of this issue on Pcbnew. Maybe use this also on Eschema Library Brownser"
1783753,2018-08-11 19:09:39 UTC,Implemented on Pcbnew
1783753,2018-08-01 13:54:25 UTC,"The footprint info list needs the number of pads (for CvPcb), so it currently loads in the entire content of the library."
1783753,2018-08-01 16:24:34 UTC,It is especially slow on Windows with standard HDs.
1783753,2018-08-01 11:14:28 UTC,The main problem with a single textbox is that it requires all libraries to be loaded.  The lazy loading of the Symbol & Footprint Viewers are one of their few remaining distinct features over the Symbol & Footprint Editors.
1783753,2018-08-01 01:13:32 UTC,"[Fist comment on this bug-/whishlist, and so far just user of KiCad. Bear with me]."
1783753,2018-08-01 13:28:53 UTC,"@Hildo, yes intial focus is key for it. Wherever the text entry is located."
1783753,2018-08-01 10:56:08 UTC,"Could be just one text box after the button on the bar menu, not needing be under it.
I think an interesting UX point is that this control have the focus set when the dialog is load (so the user would start to type in the text box without click in any place and by the arrows <UP> & <DOWN> select one of the results and just press <ENTER>)."
1783756,2018-07-26 13:23:36 UTC,Make supporting types more flexible and robust.
1783758,2018-08-15 10:31:21 UTC,Fixed in libxfce4util 4.13.2 (Ubuntu 18.10 dev).
1783758,2018-06-10 17:06:11 UTC,Thomas Lange referenced this bugreport in commit ffc7a0a8bd63c154563f27c268183576e61c9d24
1783758,2018-05-31 21:09:12 UTC,"Created attachment 7765
And another (unrelated) cleanup patch"
1783758,2018-05-31 21:08:11 UTC,"Created attachment 7764
Patch to fix this issue"
1783758,2018-05-31 21:06:57 UTC,"Created attachment 7763
Simple reproducer for this bug report"
1783758,2018-06-10 17:07:17 UTC,Thank you for the patches and the reproducer !
1783758,2017-11-15 22:52:23 UTC,"Ok, thanks. Moved the issue to Garcon."
1783758,2017-11-15 22:30:37 UTC,The application menu shown when right-clicking on the desktop has the same bug.
1783758,2017-11-15 22:23:04 UTC,Could you quickly confirm that this bug is also exposed in xfdesktop's application menu?
1783758,2017-11-07 00:16:27 UTC,"Created attachment 7421
Screenshot of the issue"
1783758,2018-05-31 21:05:42 UTC,"The bug is not in Garcon but libxfce4util, reassigned."
1783758,2018-06-08 02:52:22 UTC,*** Bug 13683 has been marked as a duplicate of this bug. ***
1783760,2018-08-12 22:11:39 UTC,No rush :)
1783760,2018-08-08 09:14:57 UTC,"Hi, thanks a lot John!
I don't have spare time this month, I'll review ASAP, OK? :)"
1783764,2018-08-31 02:18:35 UTC,"With the above commit, the Exo launchers should no longer be displayed in GNOME Software. This change does require an appdata refresh, so the below note from Jeremy Bicha applies once an update is packaged in Debian/Ubuntu."
1783764,2018-08-26 17:07:12 UTC,Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1783764
1783764,2018-08-31 02:15:00 UTC,Sean Davis referenced this bugreport in commit ace928e207a4ada02c57e956c675e6d97bd75cf5
1783764,2019-05-25 18:04:52 UTC,This bug was fixed in exo 0.12.3. Disco has 0.12.4. Marking this bug resolved in Ubuntu.
1783764,2018-08-26 17:33:19 UTC,Similar case: https://gitlab.gnome.org/GNOME/gnome-software/issues/367
1783764,2018-07-26 14:28:20 UTC,"I just tested removing the ""Web Browser"" and the same thing is happening."
1783764,2018-08-12 10:48:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783764,2018-08-12 10:47:29 UTC,"Uninstalling the exo wrapper ""Mail Reader"" does indeed remove essential packages:"
1783764,2018-08-08 06:35:13 UTC,"Hi, thanks for the amazing job !"
1783775,2018-07-26 13:41:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783775,2018-07-27 13:47:45 UTC,I believe this is what introduced the libibverbs1 dependency:
1783783,2020-05-01 20:13:07 UTC,https://bugs.launchpad.net/ubuntu/+source/lshw/02.18.85-0.3ubuntu2
1783793,2020-07-31 22:10:06 UTC,"Pushed to master, rel_3_5, and rel_3_4. Thanks, Josh and Terran!"
1783793,2020-02-05 17:18:18 UTC,Evergreen 3.4.1
1783793,2020-04-01 20:11:41 UTC,Setting an activation date in the staff client now suspends the hold as expected.
1783793,2020-03-10 18:25:31 UTC,"The fix in Comment #7 addresses the original issue, except that it doesn't address adding an error message when activating an already activated hold.  Maybe that could be a separate bug?"
1783793,2020-03-02 17:14:58 UTC,"See also, OPAC hold activation bug:
https://bugs.launchpad.net/evergreen/+bug/1865533"
1783793,2020-02-05 22:05:25 UTC,"Dawn,"
1783793,2020-01-27 21:37:46 UTC,"Hello, I'm working on adding this and I have a few questions."
1783793,2019-11-25 21:20:52 UTC,"Confirmed in 3-3-5.
From a staff member:
this is still happening. I put a hold on a book, edited the hold dates/hold activate date in the catalog for 12/2/19, then checked the item in and it captured the hold."
1783793,2019-09-13 20:05:45 UTC,Confirmed in 3.2.3. The web staff client requires that you also take the action to Suspend Hold.
1783793,2018-07-26 17:09:02 UTC,"And... line 1038 of Open-ILS/xul/staff_client/server/patron/holds.js seems to support this theory, as the XUL client seems to allow only future dates and does pass the frozen flag."
1783793,2018-07-26 17:04:53 UTC,"Kathy, I believe the problem is that the web client is not looking at the suspend-until date and, when in the future, setting the frozen flag on the hold to true.  Tracing the code (only from the web client, not through the XUL client) suggests that it's up to the calling code to make that decision and pass the appropriate flag.  Probably around line 297 of Open-ILS/web/js/ui/default/staff/circ/services/holds.js ... but I have not tested that theory yet."
1783793,2018-07-26 15:47:48 UTC,I think this might be a duplicate of bug 1782027.
1783793,2020-01-28 16:14:30 UTC,Here is a branch that does the following.
1783814,2018-07-26 16:34:38 UTC,"Also the list of parts in the document is out of date. For example part ATMEGA1284 is missing from the document but listed by the application (see output of ""avrdude -p ?"")."
1783817,2018-10-01 11:39:30 UTC,I find it most irritating when renaming a file.  I just tested and the renaming file window and offer to cancel is on screen for 25 seconds.  I also do not like the new design which provides a small pop up window to do a quick rename of a file.  The filename is often bigger than the pop up window so I have to scroll to find my insertion point.  It could be this overhead that is causing the bug which did not happen before 18.04.
1783817,2018-07-29 12:33:01 UTC,@seb128
1783817,2018-07-27 20:29:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1783817,2018-07-26 16:37:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783822,2018-07-26 17:00:07 UTC,This change was made by a bot.
1783822,2018-07-27 15:46:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1783822,2018-07-28 17:28:02 UTC,"> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
"
1783850,2018-08-03 22:20:46 UTC,Hi Daniel
1783850,2018-07-27 22:50:57 UTC,It seems I spoke too soon.
1783850,2018-10-29 21:02:41 UTC,Here's an update on this...
1783850,2018-07-30 03:22:50 UTC,"Oops, sorry. Not bug 1727356 because you are running 16.04 and Unity."
1783850,2018-07-26 22:42:09 UTC,Bug has been fixed in upgrade just released including kernel 4.4.0-131.
1783850,2018-07-30 03:22:07 UTC,Your CPU model suggests you will hit bug 1727356. Please try the workaround from that.
1783850,2018-07-26 17:08:22 UTC,See errors in the xorg log
1783851,2018-08-09 23:04:28 UTC,"Review in progress for https://review.opencontrail.org/45452
Submitter: Aniket Gawade (<email address hidden>)"
1783851,2018-08-09 23:15:35 UTC,"Reviewed:  https://review.opencontrail.org/45452
Committed: http://github.com/Juniper/openshift-ansible/commit/eed66aa75b937db8d76419fd3eebc827bd1ea95e
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    release-3.9-contrail"
1783873,2018-11-02 22:38:53 UTC,When I switched over to Ubuntu 18.04 I also switched hardware to a much faster one. So really that can be the reason why I did not have the problem earlier.
1783873,2018-11-02 22:35:33 UTC,Sorry for the delay.
1783873,2018-11-01 20:57:14 UTC,Also confirm this bug after update to 18.04.
1783873,2018-11-02 01:19:26 UTC,Thanks Dominik for your comment.
1783873,2018-10-23 22:55:48 UTC,I found a new element after digging a bit into xdotool problems with multiple keyboard layouts.
1783873,2018-10-23 22:18:41 UTC,For what it's worth : just tried removing my second keyboard layout (Bepo) and now Keepass2 auto-typing seems to work properly.
1783873,2018-10-23 21:58:05 UTC,"Hello,"
1783873,2018-10-23 23:28:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783879,2018-08-28 18:23:03 UTC,And selection_ou.
1783879,2021-01-05 08:06:28 UTC,"Agreed -- this can be very helpful for understanding why something did/didn't transit.  Also, it would be nice to think of a better way to display the selection depth in a more meaningful way than just the integer -- just a 1 or 2 wouldn't necessarily make much sense to most front-line circ folks."
1783880,2018-10-17 09:55:35 UTC,"Issue confirmed with 4.15.0-38.41-generic, with node ""modoc"", ""entei"" (power8) and baltar (power9)"
1783880,2020-02-14 06:01:48 UTC,"fallocate05 passed on P8/P9 Bionic (4.15.0-88.88):
<<<test_start>>>
tag=fallocate05 stime=1581659795
cmdline=""fallocate05""
contacts=""""
analysis=exit
<<<test_output>>>
incrementing stop
tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop0'
tst_device.c:282: INFO: Skipping $LTP_DEV size 256MB, requested size 512MB
tst_device.c:88: INFO: Found free device 1 '/dev/loop1'
tst_supported_fs_types.c:59: INFO: Kernel supports ext2
tst_supported_fs_types.c:43: INFO: mkfs.ext2 does exist
tst_supported_fs_types.c:59: INFO: Kernel supports ext3
tst_supported_fs_types.c:43: INFO: mkfs.ext3 does exist
tst_supported_fs_types.c:59: INFO: Kernel supports ext4
tst_supported_fs_types.c:43: INFO: mkfs.ext4 does exist
tst_supported_fs_types.c:59: INFO: Kernel supports xfs
tst_supported_fs_types.c:43: INFO: mkfs.xfs does exist
tst_supported_fs_types.c:59: INFO: Kernel supports btrfs
tst_supported_fs_types.c:43: INFO: mkfs.btrfs does exist
tst_supported_fs_types.c:59: INFO: Kernel supports vfat
tst_supported_fs_types.c:43: INFO: mkfs.vfat does exist
tst_supported_fs_types.c:82: INFO: Filesystem exfat is not supported
tst_test.c:1278: INFO: Testing on ext2
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
fallocate05.c:62: CONF: fallocate() not supported: EOPNOTSUPP (95)
tst_test.c:1278: INFO: Testing on ext3
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext3 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
fallocate05.c:62: CONF: fallocate() not supported: EOPNOTSUPP (95)
tst_test.c:1278: INFO: Testing on ext4
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext4 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177
tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315
tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993
tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935
tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786
tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492
tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649
tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821
tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962
tst_fill_fs.c:59: INFO: write(): ENOSPC (28)
fallocate05.c:77: PASS: write() wrote 65536 bytes
fallocate05.c:99: INFO: fallocate()d 0 extra blocks on full FS
fallocate05.c:110: PASS: fallocate() on full FS
fallocate05.c:126: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
fallocate05.c:132: PASS: write()
tst_test.c:1278: INFO: Testing on xfs
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts=''
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183
tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086
tst_fill_f..."
1783881,2020-10-02 17:02:23 UTC,Updating bug to include msgstress04 failure.
1783881,2020-12-01 04:24:17 UTC,Found on Groovy/linux 5.8.0-31.33
1783881,2020-11-18 04:07:14 UTC,"Still visible 4.15.0-1059.65 - oracle
on instance VM.DenseIO2.8 only."
1783881,2020-10-02 08:11:15 UTC,msgstress03 and msgstress04 is failing with similar behavior on Focal aws : 5.4.0-1026.26 : amd64
1783881,2018-08-30 13:27:58 UTC,"The number of processes (in systemd, tasks)."
1783881,2018-10-04 14:41:12 UTC,"Hi,"
1783881,2018-08-28 15:55:38 UTC,What about calling it like this:
1783881,2018-07-26 20:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1783881,2019-12-16 18:34:07 UTC,"This failure occurs in the cloud, on amazon aws, it can be reproduced on c4/c5.large abd c5.metal"
1783883,2019-05-21 20:57:14 UTC,Confirmed on our EG 3-2-4 system.
1783884,2018-07-31 07:48:13 UTC,At this moment we do not have any native way to configure ldap or other backend. Custom config overrides may be used to change values in keystone.
1783887,2018-08-12 19:38:43 UTC,"Great, it works also on my PC now.
When I exported it, I had a different PC with 2 monitors and bigger resolution.
Could this be the problem?"
1783887,2018-08-12 19:05:19 UTC,I was able to make your configuration work by removing these two lines from the config.txt:
1783887,2018-08-12 18:43:17 UTC,I will try to reproduce this bug with your config file.
1783887,2018-08-12 17:39:38 UTC,"When I write ""xfce4-panel"" in the cmdline, I get nothing, the terminal is stuck. When I press Ctr+C, I get this."
1783887,2018-08-12 14:37:14 UTC,Thanks for the quick reply.
1783887,2018-08-12 14:58:22 UTC,"Now I don't have the possibility to reproduce because I don't have a panel at all (to import), as I mentioned in the last post...:(
How can I make it appear again?"
1783887,2018-08-12 14:15:43 UTC,"I reproduced it very easily and the problem is that I don't have any panel at all now, even after restart :((, it's really not pleasant, I hope I don't have to reinstall the linux."
1783887,2018-08-12 11:29:22 UTC,"Please run the following terminal command, and then try reproduce the problem:"
1783887,2018-08-12 17:13:34 UTC,What terminal output do you get when trying to start xfce4-panel?
1783889,2020-02-12 15:47:53 UTC,bump
1783889,2020-03-12 05:00:48 UTC,Maybe instead of --xall it would be better to use --health?
1783889,2019-07-12 09:26:20 UTC,Is the still work going on to get this merged? We are currently also encountering this issue with SSDs where the smartctl error log includes old errors from a power outage about 2 year ago and therefore the return code is 64 like mentioned in the bug description.
1783889,2020-03-27 09:45:35 UTC,"Just ran into that issue again while installing another MAAS server. It would be great if we could agree on a solution for this.
Cheers,
Jan"
1783889,2020-09-30 07:54:57 UTC,I'm fine with either solution:
1783889,2020-03-12 08:41:00 UTC,Until then I've fixed it for myself with this patch and restarted maas-regiond and now I don't have failing hardware tests any more:
1783889,2019-01-12 16:30:01 UTC,"I am also experiencing this on a few drives. Their regular smartctl -a output passes with a return code of 0, however when run with --xall old errors present in the log cause the test to fail."
1783889,2018-07-26 23:53:02 UTC,Thanks for the report. I'm trying to understand what exactly is failing. Could you please post output of the following:
1783889,2018-07-27 22:41:11 UTC,Thanks for posting the log. It looks like your drive is experiencing read errors. While these errors are recoverable they may effect performance. You can still use the machine by using the 'override failed test' machine operation in the UI or over the API.
1783889,2018-07-27 12:05:38 UTC,"INFO: Veriying SMART support for the following drive: /dev/sdm
INFO: Running command: sudo -n smartctl --all /dev/sdm"
1783889,2018-07-27 01:25:48 UTC,"A few things to note:
1) Scratch the last suggestion of ""return (proc.returncode & 187)"", that would mask the error even if more than just bits 2 and 6 were flagged from a failure."
1783889,2018-07-26 22:27:45 UTC,"So there's 2 thoughts of how to solve this:
(Still referencing lines 159 and 172)"
1783889,2018-07-26 22:13:05 UTC,We made a small improvement to this if you wish to incorporate it.
1783889,2018-07-30 14:59:26 UTC,"Okay, maybe I need more help reading these logs, but I've been trying to study them.  From what I can tell what you posted does not actually appear show read errors that one would need to be concerned with."
1783895,2019-10-20 03:32:32 UTC,"Will something like below work? If not, how to improve it?"
1783895,2019-10-20 03:25:42 UTC,#14 is the only workable workaround for this bug.
1783895,2019-08-01 11:58:39 UTC,I found it necessary to lock+suspend the screen before closing the lid. So I did it with a script tied to the keyboard shortcut CTRL+SUPER+DELETE:
1783895,2019-02-07 22:42:07 UTC,"OK, just circling back around to this as of today, 02/07/2019:"
1783895,2018-07-27 15:20:28 UTC,I solved this yesterday on Ubuntu 18.04.1:
1783895,2018-07-18 14:19:37 UTC,sys-power/upower-pm-utils 0.9.23-r2
1783895,2018-07-18 14:11:02 UTC,Debug output https://pastebin.com/bsn97Vwq
1783895,2018-07-31 11:51:33 UTC,Installing latest upower solved my issues.
1783895,2018-07-18 13:45:37 UTC,I'm also having this issue.
1783895,2017-11-15 19:29:02 UTC,"Thanks for your reply.
Activating and deactivating lid button gives me these events:
signal time=1510773931.714558 sender=:1.20 -> destination=(null destination) serial=3144 path=/org/freedesktop/UPower; interface=org.freedesktop.UPower; member=Changed
signal time=1510773932.546623 sender=:1.20 -> destination=(null destination) serial=3145 path=/org/freedesktop/UPower; interface=org.freedesktop.UPower; member=Changed
One for lid-close event, the other for lid-open respectively with ever increasing serial.
Is there anything else I can do to identify the cause of this issue?"
1783895,2017-11-15 14:40:59 UTC,"Try to monitor the bus to see if upower is effectively sending the signal to the power manager, using the following command."
1783895,2017-08-10 17:05:25 UTC,"Of course! But this does not help.
Since my system does not even have logind, this might be irrelevant setting though.
But anyway thanks for your answer!"
1783895,2017-08-10 11:44:58 UTC,Have you tried:
1783895,2017-08-02 18:49:41 UTC,"Xfce4-power-manager does not catch lid events.
acpi_listen does show lid events.
UPower does catch lid events.
Xfce4-power-manager --debug gives no output on lid events.
It has settings for lid events, but they are ignored as no event catched.
It does appropriate actions upon suspend and poweroff keys, but not lid.
What is wrong here?
Thanks in advance."
1783895,2018-07-18 13:46:25 UTC,My system.
1783902,2018-09-07 01:01:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783903,2018-11-09 11:05:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1783903,2018-11-08 17:56:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783906,2019-05-16 08:17:05 UTC,"Ok, I find out what happens."
1783906,2019-07-09 05:43:08 UTC,No I think you did everything right.
1783906,2019-07-05 10:40:56 UTC,"I'm not familiar with kernel mailing list so I don't know why my patch was ignored. Maybe format of email was not proper, or I send wrong recipients."
1783906,2019-06-24 05:44:43 UTC,"Yes, I have sent the patch, but until today no one answered"
1783906,2019-06-24 05:35:06 UTC,Have you sent the patch upstream?
1783906,2019-05-17 23:01:30 UTC,I tuned a little a previous patch
1783906,2019-05-16 18:41:14 UTC,"Yes, it may also be good to test on different configurations, the original patch fixed hotplug related
problem where 6Gps drives connected back at lower speeds."
1783906,2019-05-16 09:33:08 UTC,There is patch to issue I described above
1783906,2019-05-16 08:19:43 UTC,Maybe this conversation should be moved to Linux linux-ide mailing list. There is some technical decisions to make and may it's better to consult it with other developers.
1783906,2019-05-15 21:40:06 UTC,"No, my device doesn't work with 6Gbps. In kernel 4.14 if my drive was offline, function sata_down_spd_limit() cut down link->sata_spd_limit to 1, so it corresponds to 1.5Gbps, and was working. But it wasn't even try to set limit to 3Gbps."
1783906,2020-06-13 02:30:38 UTC,I experience this issue on Ubuntu 20.04
1783906,2019-05-15 08:34:24 UTC,I think that I fixed second part of my issue.
1783906,2019-05-14 22:34:52 UTC,I can split my issue into two cases:
1783906,2019-05-14 07:50:35 UTC,I forgot to say that even on Linux 4.14 I have to execute manually script while booting:
1783906,2019-05-10 20:40:09 UTC,"Ok thanks, please look at this some more, I will try to get back with you soon."
1783906,2019-05-07 23:26:02 UTC,"Unfortunately patch ""0001-libata-sata_down_spd_limit-should-record-link-speed-.patch"" don't work."
1783906,2019-05-07 22:39:55 UTC,Hi!
1783906,2018-09-11 15:00:28 UTC,"I built a test kernel with the patch from David posted in comment #21.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783906"
1783906,2018-09-06 20:56:07 UTC,"Hi,"
1783906,2018-08-30 11:18:52 UTC,"Hi,"
1783906,2019-05-15 19:27:11 UTC,I not sure upstream will let us change the value of mask.
1783906,2018-08-29 22:48:23 UTC,"Here's dmesg with #33~lp1783906DEBUGv2: https://paste.ubuntu.com/p/jK6zjKjtqc/
I expected this to have the bug and only print additional debug info, but it seems this fix the bug. The second drive (WDC) came up and I could mount it's partitions and read info from them."
1783906,2018-08-29 18:48:05 UTC,I built a second test kernel with additional debug output as requested by David. This kernel also has the two lines removed request by David.
1783906,2018-08-24 10:52:08 UTC,"Ok, thanks, please let me look through the output."
1783906,2018-08-29 17:37:54 UTC,"Thanks for the response, David!  Correct the print for the mask came after those 2 lines of code.  Here is the snippet:"
1783906,2018-08-24 18:57:05 UTC,"Hi Joe,"
1783906,2018-08-24 01:31:03 UTC,"Here's dmesg with 4.15.0-30-generic #33~lp1783906DEBUG running for 10 mins:
https://paste.ubuntu.com/p/Qc9Kpb62ch/"
1783906,2018-08-13 20:00:58 UTC,I built a test kernel with debug output as requested by upstream.  Can you test this kernel and post your syslog or dmesg output?
1783906,2018-08-10 21:21:56 UTC,"Hi Joe,"
1783906,2018-07-30 19:58:58 UTC,Your test kernel with commit 2dc0b46b5ea3 does indeed fix the issue with the WD HDD. Here's the dmesg with your test kernel: https://paste.ubuntu.com/p/745NscYFJh/
1783906,2018-07-30 16:13:36 UTC,Commit 2dc0b46b5ea3 in v4.15-rc4 looks like it could be related.  I built a Bionic test kernel with this commit reverted.  The test kernel can be downloaded from:
1783906,2018-08-10 20:41:00 UTC,"Hi David,"
1783906,2018-07-27 19:53:41 UTC,"I went ahead and test this bug from linux 4.15rc1 and up to linux 4.15rc5.
What i found is that linux 4.15rc3 is the last RC version where this bug doesn't occur, and linux 4.15rc4 is the first RC version where this bug occur."
1783906,2018-07-27 17:47:10 UTC,"I first experienced this issue while testing the second beta of ubuntu 18.04, as i explained in the original bug report this issue doesn't happen if i use linux 4.14"
1783906,2018-07-27 14:01:37 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1783906,2018-07-27 01:04:14 UTC,"I forgot to mention the Western Digital hard drive has always been slow to actually show up, and I’ve always gotten those ""COMRESET failed, link is slow to respond"" messages since I bought it."
1783906,2018-07-27 00:00:09 UTC,This change was made by a bot.
1783906,2018-08-29 17:38:29 UTC,I'll build another test kernel with you're suggestions and ask @danieru to test.
1783906,2018-07-30 14:26:23 UTC,"Thanks for the testing.  I'll review the commits between -rc3 and -rc4.  If nothing sticks out, I'll start a kernel bisect a build a test kernel."
1783908,2018-07-30 08:43:42 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/586980"
1783908,2018-11-06 06:09:51 UTC,This issue was fixed in the openstack/neutron 11.0.6 release.
1783908,2018-08-21 05:41:34 UTC,"Yamamoto, we still hit this even with the ""fix"". I think it needs to be root caused... is it an issue with Linux (we hit it on both Centos7 and Ubuntu14 DHCP hosts)? issue with dnsmasq? We see repeatedly logs in dhcp-agent like:"
1783908,2018-08-01 23:55:33 UTC,"Reviewed:  https://review.openstack.org/586980
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6aada381f4695ccd904c4be7dbfdd95744d32e38
Submitter: Zuul
Branch:    stable/pike"
1783908,2018-07-29 23:04:38 UTC,"""Confirmed"" in sense it at least needs a backport for pike."
1783908,2018-07-27 19:01:07 UTC,"Also, I don't see dnsmasq reloading based on timestamp in output of ps, even when I deploy or delete new VMs:"
1783908,2018-07-27 18:58:03 UTC,No... this is on Pike. That fix was only backported to Queens.
1783908,2018-07-27 04:12:46 UTC,"looks similar with https://bugs.launchpad.net/neutron/+bug/1764481
does your version of neutron have the fix?"
1783908,2018-07-27 00:11:24 UTC,We see this on both Ubuntu14 and Centos 7.2 and Centos 7.4. Kernel and OS versions:
1783922,2018-09-06 09:42:21 UTC,"For Azure 4.15 kernel on Xenial:
* Standard_B1s
* Standard_B4ms
* Standard_DS12_v2
* Standard_DS14_v2
* Standard_DS14_v2_promo
* Standard_DS1_v2
* Standard_E4_v3
* Standard_D32s_v3"
1783922,2019-10-18 07:25:32 UTC,"For Azure 4.15 kernel on Trusty:
 * Standard-B1ms
 * Standard_E2s_v3
 * Standard-F1s
 * Standard_F32s_v2"
1783922,2019-10-18 07:26:20 UTC,"BTW,
as it's been a while, I am not sure if this is still hanging with the mmap test."
1783922,2018-09-06 08:31:20 UTC,"In this cycle, issue spotted on the following Azure nodes with 4.15 kernel:
* Standard_B4ms
* Standard_D4_v3
* Standard_DS1
* Standard_DS12_v2
* Standard_DS13
* Standard_DS13_v2
* Standard_DS14_v2
* Standard_E32-8s_v3
* Standard_GS5-8"
1783922,2018-07-27 03:00:07 UTC,This change was made by a bot.
1783922,2018-07-27 08:42:48 UTC,"Hi Steve,"
1783922,2018-07-27 05:00:03 UTC,"Hi Po-Hsu,"
1783922,2018-08-17 11:04:25 UTC,"It looks like this hang issue was introduced because the mmap test has timed out.
And it gets killed by the autotest framework."
1783923,2018-07-27 02:50:24 UTC,"Yes, I've changed the password I leaked in the original description."
1783928,2018-07-27 03:54:41 UTC,Thank you for being there
1783930,2018-12-17 10:09:13 UTC,This bug was fixed in the package gcc-6 - 6.5.0-2ubuntu1~18.04
1783930,2018-12-14 06:55:20 UTC,"yes, this works with the gcc-6 package in bionic-proposed."
1783930,2018-07-28 23:50:00 UTC,This bug was fixed in the package gcc-6 - 6.4.0-19ubuntu1
1783930,2018-11-20 22:38:25 UTC,"Hello Matthias, or anyone else affected,"
1783930,2018-12-13 08:36:25 UTC,Can someone confirm that the new package versions have this bug fixed?
1783930,2018-12-17 09:59:14 UTC,"The verification of the Stable Release Update for gcc-6 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1783952,2018-07-30 05:34:35 UTC,"So I have now tested installing upstream kernel (4.18-rc6), which worked and made the procedure successful on 16.04. The system however became quite unstable as a whole and so I upgraded the system to 18.04 with it´s stock kernel 4.15-something, which also works. That means it´s definitely something wrong with 16.04 kernel and not something local to the system."
1783952,2018-07-27 15:49:24 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1783952,2018-07-27 07:58:28 UTC,apport information
1783952,2018-07-27 07:58:27 UTC,apport information
1783952,2018-07-27 07:58:26 UTC,apport information
1783952,2018-07-27 07:58:25 UTC,apport information
1783952,2018-07-27 07:58:24 UTC,apport information
1783952,2018-07-27 07:58:23 UTC,apport information
1783952,2018-07-27 07:58:22 UTC,apport information
1783952,2018-07-27 16:06:25 UTC,"On Fri, Jul 27, 2018, 18:01 Joseph Salisbury <email address hidden>
wrote:"
1783952,2018-07-27 07:58:19 UTC,apport information
1783952,2018-07-27 07:58:18 UTC,apport information
1783952,2018-07-27 07:58:17 UTC,apport information
1783952,2018-07-27 07:58:16 UTC,apport information
1783952,2018-07-27 07:58:15 UTC,apport information
1783952,2018-07-27 07:58:14 UTC,apport information
1783952,2018-07-27 07:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1783952,2018-07-27 07:58:20 UTC,apport information
1783957,2018-09-24 07:59:54 UTC,"It still freezes, and I don't get the login screen."
1783957,2018-09-21 11:42:49 UTC,"I built the next test kernel, up to the following commit:
a2fc4bd61e7ec3bb1f7c8b3d47272be813f88aea"
1783957,2018-09-21 09:49:14 UTC,Same problem.
1783957,2018-09-21 09:15:25 UTC,"I built the next test kernel, up to the following commit:
f150891fd9878ef0d9197c4e8451ce67c3bdd014"
1783957,2018-09-20 08:34:39 UTC,I've already testest that kernel.
1783957,2018-09-20 09:13:59 UTC,"When you say you 'already' tested that kernel, do you mean you already tested it before I posted it in comment #31?  The kernel name might look similar to a prior kernel, but there is a unique date stamp in the name, '201809190746' in the latest test kernel."
1783957,2018-10-01 08:01:46 UTC,Well ?...
1783957,2018-09-19 08:12:18 UTC,"Based on you're test results posted in comment #28, I built the next test kernel, up to the following commit:
8c609698569578913ad40bb160b97c3f6cfa15ec"
1783957,2018-09-19 07:02:58 UTC,?????????
1783957,2018-09-20 09:44:35 UTC,Sorry. I didn't noticed that.
1783957,2018-10-02 15:22:13 UTC,"I built the next test kernel, up to the following commit:
754270c7c56292e97d0eff924a5d5d83f92add07"
1783957,2018-10-04 15:39:26 UTC,"I built the next test kernel, up to the following commit:
29baa82aa55f40d67cfc8138c944fd8880c27e8e"
1783957,2018-10-03 13:56:04 UTC,"I built the next test kernel, up to the following commit:
b05720cbf6458450700d1c3e91d2b2620b4f6295"
1783957,2018-10-04 07:36:31 UTC,This kernel works !
1783957,2018-10-08 07:10:10 UTC,Not working
1783957,2018-10-09 19:07:49 UTC,"I built the next test kernel, up to the following commit:
34cc0aa2545603560c79aaea3340d8ff3a71bd10"
1783957,2018-10-10 06:47:55 UTC,There is nothing there. No files in that folder (URL).
1783957,2018-10-10 19:19:09 UTC,Well ? What should I understand from what you just did ?
1783957,2018-12-06 04:17:01 UTC,"Hey, I've just upgraded from bionic to cosmic and I seem to be hit by this. Perhaps. What I experience is that while I have an encrypted root, with the cosmic kernel I don't get a chance to input my passphrase."
1783957,2018-08-03 08:08:19 UTC,"Well, what is the situation ? I really need this bug fixed !!!"
1783957,2018-09-17 07:49:38 UTC,Well ? I'm back ! Any progress ?
1783957,2019-04-01 21:16:44 UTC,"Operating System: Ubuntu 18.04.2 LTS
Kernel: Linux 4.18.0-15-generic
Intel Core i7-7700HQ + GeForce 1050Ti
after: sudo update-initramfs -u
I get :
update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic
W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau"
1783957,2018-10-03 10:04:40 UTC,"It still freezes, and I don't get the login screen."
1783957,2018-09-01 11:32:56 UTC,"Well, it's strange..."
1783957,2018-08-01 07:16:55 UTC,"I'm sorry, but it is not possible for me to do this."
1783957,2018-08-31 09:01:07 UTC,Yes. The latest v4.14 also works great !!! I have nouveau drivers loaded and working perfectly.
1783957,2018-07-27 08:12:32 UTC,Sounds like a kernel regression so reassigning there.
1783957,2018-07-27 08:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1783957,2018-07-27 09:32:00 UTC,Yeah.
1783957,2018-08-31 16:02:31 UTC,"There are many nouveau commits that were introduced in v4.15-rc1, so we need to perform a bisect to identify the specific one that caused this regression."
1783957,2018-07-30 09:02:06 UTC,"I've tested the new kernel, it doesn't work. It also hangs at the screen where the login screen should apperar."
1783957,2018-08-03 12:28:22 UTC,Can you attach dmesg under latest mainline kernel?
1783957,2018-08-06 07:04:25 UTC,"No, again, I am sorry, I cannot do that."
1783957,2018-08-07 06:47:19 UTC,Well ? What is the situation ?
1783957,2018-08-10 07:12:57 UTC,???
1783957,2018-08-14 11:10:43 UTC,I've upgraded my system to Bionic: 18.04.1.
1783957,2018-07-27 15:45:33 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1783957,2018-08-17 08:20:20 UTC,one last thing I can give you:
1783957,2018-08-16 08:00:57 UTC,???????????????????????????????? is anyone alive here ??? or should I just give up on everything ?
1783957,2018-08-30 18:30:08 UTC,"Before starting the bisect, just one last kernel to confirm:"
1783957,2018-08-30 09:18:15 UTC,Yes. The system crashes with this version. It no longer works with 4.15-rc1.
1783957,2018-08-28 15:04:06 UTC,"Can you give v4.15-rc1 a try and see if it has the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/"
1783957,2018-08-28 06:58:21 UTC,v4.13 Final is GOOD
1783957,2018-07-31 15:51:56 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1783957,2018-08-27 08:09:53 UTC,I can confirm the following:
1783957,2018-08-24 18:36:35 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the last kernel that did not have this issue.
1783957,2018-08-24 07:43:29 UTC,"I will start a new bug report, as nobody cares with this bug, I see."
1783957,2018-08-24 07:42:19 UTC,?????????????????????????????????
1783957,2018-08-27 17:01:11 UTC,Just to confirm:
1783961,2019-11-12 22:21:21 UTC,This bug was fixed in the package linux-raspi2 - 5.3.0-1012.14
1783961,2019-11-05 12:28:36 UTC,"For armhf (arm32) kernel, only CORTEX-A7 and CORTEXT-A15 support KVM, for Pi's cpu, they don't support KVM for armhf kernel."
1783961,2019-10-31 02:58:37 UTC,Will enable the KVM in the kernel of the next release.
1783961,2019-10-23 12:54:46 UTC,@hui.wang and the Ubuntu kernel team - kindly consider enabling KVM for arm64 Linux kernel in the raspberrypi preinstalled image in future. Thanks!
1783961,2019-10-23 12:53:49 UTC,"@hui.wang - I tested the compiled kernel on my RaspberryPi4 (4GB RAM model). Both KVM and external SSD/USB (in my case Samsung T5, 500GB external SSD) on the USB 3.0 port are working fine."
1783961,2019-10-22 19:00:59 UTC,"Just found this bug, I had added a similar bug ticket: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849369 (now marked as duplicate)."
1783961,2019-10-23 09:12:46 UTC,"I built a testing kernel which enabled the KVM, please test it on rpi4/3 (arm64) and rpi4/3/2 (armhf) boards."
1783961,2019-07-05 14:01:14 UTC,just as a followup ... better ignore my comment above ... KVM is indeed not KMS ... sorry for causing confusion here
1783961,2019-06-22 12:47:17 UTC,"ogra: Hi, this doesn't work for ARM64... only enabling CONFIG_KVM does."
1783961,2018-07-27 08:35:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783961,2019-12-05 14:30:58 UTC,This bug was fixed in the package linux-raspi2 - 5.3.0-1014.16
1783961,2019-10-23 10:10:57 UTC,"Great, thanks @hui.wang. I'll test it in the evening and keep you posted."
1783961,2019-06-22 12:00:46 UTC,enabling CONFIG_KVM instead of enabling KVM via the dtb overlay will hard-disable all video acceleration of the upstream proprietary driver of the pi and make it completely unusable for any kind of setup that uses any upstram acceleration features from the raspberry pi foundation (i.e. via /opt/vc4 libs).
1783965,2018-07-29 23:10:19 UTC,do you have a concrete idea how to to improve it?
1783968,2018-07-29 23:15:42 UTC,"i feel it can somehow contradict with your other point. https://bugs.launchpad.net/neutron/+bug/1783965
it might be safer to avoid making further changes when something bad is happening.
how do you think?"
1783970,2018-07-27 11:32:42 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1783970,2020-07-03 04:19:49 UTC,"DistroRelease: Kali 2018.2
libjpeg8:amd64 8d-1+deb7u1"
1783978,2020-02-13 20:11:47 UTC,Could you actually show the mounts? (possibly replacing sensitive stuff with random unique values if any)
1783978,2019-09-12 14:09:18 UTC,Is it still a bug? Can you reproduce it with latest kolla-ansible/kolla code?
1783978,2019-11-12 04:18:21 UTC,[Expired for kolla because there has been no activity for 60 days.]
1783978,2020-02-13 17:09:34 UTC,"Hello all! I'm facing the same issue, using the stable/stein release with centos-binary images. The cinder backends related to this are the ones that use a shared bind mount: http://paste.openstack.org/show/789538/. I've checked this with a NFS backend as well as a Quobyte one and every time one of the nova containers is restarted the mounts double (plus one for me):"
1783978,2020-02-14 16:21:08 UTC,"```
# mount | grep nfs
192.168.17.11:/kolla_nfs on /var/lib/nova/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/nova/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/docker/volumes/nova_compute/_data/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/docker/volumes/nova_compute/_data/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/docker/volumes/nova_compute/_data/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/nova/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/nova/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/docker/volumes/nova_compute/_data/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
# mount | grep -c nfs
8
# docker restart nova_compute
nova_compute
# mount | grep -c nfs
16
# mount | grep nfs
192.168.17.11:/kolla_nfs on /var/lib/nova/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/nova/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/docker/volumes/nova_compute/_data/mnt/03084b2d0f988f513a2652c556e3ad4d type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.17.5,local_lock=none,addr=192.168.17.11)
192.168.17.11:/kolla_nfs on /var/lib/docker/volumes/nova_compute/_data/mnt/03084b2d..."
1783978,2020-02-21 12:04:20 UTC,"Hello all. Just wanted to update you on some further investigation I did on this. So, the problem isn't the shared bind mount used by the backends mentioned above. It's the nested bind mount! There's /var/lib/nova as a destination of a bind mount on the nova containers and with the above cinder backends /var/lib/nova/mnt is also added as a separate bind mount. This causes the mounts to be doubled every time the nova containers (compute, libvirt, ssh) are restarted."
1783978,2020-04-22 04:17:28 UTC,[Expired for kolla because there has been no activity for 60 days.]
1783987,2018-12-28 00:33:10 UTC,-- GitLab Migration Automatic Message --
1783987,2019-01-04 20:08:09 UTC,"In my case, what helped was to remove package `numlockx` with `sudo apt-get purge numlockx`."
1783987,2019-01-29 15:20:36 UTC,Deactivating numlock before activting neo2 also fixed this issue for me.
1783987,2016-07-21 15:10:30 UTC,"I'm using the keyboard layout de-neo (German Neo2). When starting a x11 graphical application in a xwayland session, I see this error message printed to console or syslog:"
1783987,2016-07-21 17:27:51 UTC,I can help debug the wayland error message.
1783987,2018-07-30 04:48:32 UTC,"Fine, thanks for that."
1783987,2016-07-21 19:10:28 UTC,"(In reply to Ran Benita from comment #1)

> I can help debug the wayland error message.
"
1783987,2018-07-29 21:42:56 UTC,There is no reason to expect anything else. A live session and a fully installed system should behave identically in this respect. My own testing was on a fully installed Ubuntu 18.04.
1783987,2018-07-29 17:44:42 UTC,"Gunnar:
Can you please make sure that NumLock is turned off when switching to Neo 2 and let us know if that helps."
1783987,2018-07-27 20:12:29 UTC,I jumped at conclusions; sorry for that.
1783987,2016-07-21 18:45:39 UTC,"> Warning:          Multiple interpretations of ""Caps_Lock+AnyOfOrNone(all)""
>                   Using last definition for duplicate fields
"
1783987,2018-07-27 16:55:23 UTC,"I think Neo 2 is it, but it's a complex keyboard layout. There are some hints in the file"
1783987,2017-02-02 19:33:07 UTC,">  - the key right of TAB (""q"" on QWERTZ) seemed to be backspace
>  - the key right of that (""w"" on QWERTZ) activated my shell history (so that would usually be Ctrl-r)
"
1783987,2017-02-02 08:41:44 UTC,"[I don't want to hijack this issue, so feel free to ignore me.]"
1783987,2017-01-28 18:17:54 UTC,"> > I just had a look into types/level5, and for EIGHT_LEVEL_LEVEL_FIVE_LOCK it says that 'Lock has no effect', which I suspect is the reason for that.
"
1783987,2018-07-27 18:18:33 UTC,Thanks Gunnar :-)
1783987,2017-01-27 21:41:21 UTC,"(In reply to Andreas Wettstein from comment #9)

> > i cannot enter capital letters with the neo (or, in my case adnw) layout.
>
> How about non-letter symbols on the shifted layer?  For example, does
> Shift+1 produce ° as desired?  If it works, if you replace (in adnw_base in
> symbols/de) EIGHT_LEVEL_ALPHABETIC_LEVEL_FIVE_LOCK by
> EIGHT_LEVEL_LEVEL_FIVE_LOCK (and make sure to reload the layout), does this
> help with letters?
"
1783987,2017-01-27 17:45:46 UTC,"> i cannot enter capital letters with the neo (or, in my case adnw) layout.
"
1783987,2017-01-23 22:11:48 UTC,"i have noticed a related problem: i cannot enter capital letters with the neo (or, in my case adnw) layout. it's probably related to this issue. i have tried replacing the rules in comment #2, but seemingly to no avail (i logged out and back in and nothing had changed)."
1783987,2016-07-22 18:00:07 UTC,"> hmm, some Neo2 people are still using xmodmap: https://wiki.neo-layout.org/browser#linux/xmodmap . So just leave this warning be?
"
1783987,2016-07-21 19:17:41 UTC,"(In reply to Sergey V. Udaltsov from comment #4)

> These are warning message, you can safely ignore them
"
1783987,2016-07-21 19:16:11 UTC,"(In reply to Andreas Wettstein from comment #2)

> > Warning:          Multiple interpretations of ""Caps_Lock+AnyOfOrNone(all)""
> >                   Using last definition for duplicate fields
>
> > Warning:          Multiple interpretations of ""Shift_L+AnyOfOrNone(all)""
> >                   Using last definition for duplicate fields
>
> The latter comes from ""assign_shift_left_action"" in compat/misc, see the
> comment there why it is required.
>
> I think the proper way to get rid of this warning would be to specify the
> action associated to a keysym directly, not involving any ""Any"" patters in
> the compat, that is, instead of
>
>     interpret Any+Lock {
> 	action= LockMods(modifiers=Lock);
>     };
>
>     interpret Any + Any {
> 	action= SetMods(modifiers=modMapMods);
>     };
>
> (in compat/basic), use
>
>     interpret Caps_Lock {
> 	action= LockMods(modifiers=Lock);
>     };
>
>     interpret Shift_L {
> 	action= SetMods(modifiers=Shift);
>     };
>     interpret Shift_R {
>         action= SetMods(modifiers=Shift);
>     };
>
> This might break some xmodmap setups of those very conservative user still
> using xmodmap...
"
1783987,2016-07-21 19:14:09 UTC,"These are warning message, you can safely ignore them"
1783987,2017-01-28 17:11:55 UTC,"> Now typing capital letters works, but setting CapsLock by pressing Shift+Shift still doesn't, unfortunately.
"
1783992,2018-09-01 00:25:48 UTC,"Ah, TIL: The ""LibreOffice"" that appears under Productivity in GNOME Software is the LibreOffice launcher, not the ""libreoffice"" metapackage. I was getting the two confused."
1783992,2018-08-30 20:04:41 UTC,The libreoffice package has libreoffice-gnome|libreoffice-kde4 in its Recommends. Why can't libreoffice-calc do the same? What is the difference from the point of view of a non-GNOME/non-KDE desktop?
1783992,2018-08-29 13:50:54 UTC,"That wouldn't work for other desktop environments (not GNOME and not KDE). Some might want libreoffice-gtk2, others might want libreoffice-gtk3. I agree that the default UI is rather poor on the eye. OTOH, this situation happens only when libreoffice is not already installed by default, which it is on most flavours of Ubuntu, unless you select a minimal install.
Not sure what to do about this, to be honest."
1783992,2018-08-31 09:35:01 UTC,"But the libreoffice metapackage is not usually installed, whereas individual libreoffice apps are."
1783994,2019-11-26 17:38:28 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1783994,2019-11-26 17:37:57 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.33
1783994,2019-11-16 15:22:44 UTC,"I can confirm, that the package in -proposed fixed the problem."
1783994,2019-11-15 16:40:56 UTC,"Hello Marc, or anyone else affected,"
1783994,2019-11-15 00:55:07 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1783994,2019-09-17 07:45:25 UTC,Lubuntu 18.04.3 64 bit fresh install + updates
1783994,2019-09-27 18:13:30 UTC,"From a quick read of the upstream bug, it seems like this requires commits:
7be1420f44465a96d098a33c12c5a61dcefb14aa
a3a3b6131eb2c44b3b94df973e6edd2e4c8d2095
cde942f61bf231ea4a0d50780cdb4e744458daeb"
1783994,2019-11-14 15:00:17 UTC,"Hello Marc, or anyone else affected,"
1783994,2018-07-27 13:38:37 UTC,here is an updated fix: https://github.com/systemd/systemd/commit/cde942f61bf231ea4a0d50780cdb4e744458daeb#diff-5be2770e81c14245e90d2916ded39491
1783994,2019-11-16 02:55:53 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1783994,2019-07-23 05:37:15 UTC,"Hello all,
apologies if am commenting incorrectly, my first post here
could anyone confirm if the fix mentioned in #1 will be backported to systemd in bionic ?
also any time frame on the completion of the activity ?"
1783994,2018-12-20 12:22:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1783994,2019-08-06 06:20:18 UTC,"Hi all,"
1784006,2018-07-30 08:39:21 UTC,It looks like the bug in the Neutron. Similar bug was fixed in commit https://github.com/openstack/neutron/commit/60cb0911712ad11688b4d09e5c01ac39c49f5aea
1784006,2018-07-30 09:13:57 UTC,I can reproduce this in stable/queens neutron with a single reboot command.
1784006,2018-09-25 09:50:31 UTC,"I've indicated that this bug doesn't affect Nova because I believe this is an issue in Neutron, not in Nova. I tried to change unrescue and soft reboot libvirt driver functions in Nova to act with ports like in hard reboot, and sometimes it helped, but not always, and rarely this issue occurs even after the hard reboot."
1784006,2019-12-15 01:47:43 UTC,This bug looks similar to https://bugs.launchpad.net/neutron/+bug/1845161 and was addressed in https://review.opendev.org/#/c/690098/
1784009,2018-07-27 14:50:34 UTC,"Laurent,"
1784009,2018-07-27 15:07:51 UTC,Thank you Tomasz !
1784023,2019-01-12 21:54:01 UTC,Fixed in 2.0+git20181009-2.
1784023,2018-11-02 13:59:15 UTC,"I took a look because this appeared on the Debian package tracker for apparmor-profiles-extra. At least 1.24 (just uploaded to sid) seems to be OK. I've not checked older versions so I don't know when exactly the problem that affected this package (which seems unspecified here) was fixed. If there's anything left to fix in this package, please let me know :)"
1784023,2018-08-21 18:33:40 UTC,This bug was fixed in the package lightdm - 1.26.0-0ubuntu2
1784023,2018-08-21 12:20:47 UTC,This bug was fixed in the package strongswan - 5.6.2-2ubuntu2
1784023,2018-08-21 00:50:25 UTC,This bug was fixed in the package lightdm-remote-session-freerdp2 - 2.0.0-1ubuntu1
1784023,2018-08-18 14:29:18 UTC,This bug was fixed in the package libvirt - 4.6.0-2ubuntu1
1784023,2018-08-21 01:00:31 UTC,This bug was fixed in the package telepathy-mission-control-5 - 1:5.16.4-2ubuntu2
1784023,2018-08-02 15:01:14 UTC,This bug was fixed in the package apparmor - 2.12-4ubuntu7
1784023,2018-08-08 10:47:03 UTC,"FYI - the libvirt change is in git, just needs a few other things and tests to be complete for an upload."
1784023,2018-07-28 16:47:35 UTC,"> ./abstractions/lightdm: /bin/ rmix,
"
1784023,2018-07-30 06:00:13 UTC,"If https://wiki.debian.org/UsrMerge is what we follow here then the libvirt rules for:
 /sbin/* PUx and /bin/* PUx are ok, they already have /usr/bin/* and /usr/sbin/* present.
(part of a very lenient profile I know)
They are also not part of the Ubuntu Delta, so we can leave those rules as-is."
1784023,2018-07-30 08:46:46 UTC,"To reduce unintentional breakage, I will try to upload a few of the above profiles with mostly mechanical fixes for usrmerge."
1784023,2018-08-21 00:50:16 UTC,This bug was fixed in the package lightdm-remote-session-x2go - 0.0.2.0-2ubuntu1
1784023,2018-07-30 15:55:24 UTC,This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu8
1784023,2018-07-31 04:50:28 UTC,This bug was fixed in the package man-db - 2.8.4-1ubuntu1
1784023,2018-07-31 08:31:37 UTC,"For the strongswan change I filed a bug with Debian, I don't see an immediate need to add Delta for this.
@xnox: If there are serious deadlines involved you can obviously push the change, otherwise I'd wait for the next merge."
1784023,2018-07-30 14:17:26 UTC,snapd forked to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1784394
1784030,2018-07-27 20:19:34 UTC,"https://github.com/go-goose/goose/pull/65
https://github.com/juju/juju/pull/8987"
1784030,2020-02-26 22:39:26 UTC,Marking as Won't Fix for 2.4 series since we are not planning to make any further releases in this series at this stage.
1784031,2018-07-27 18:08:41 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1784043,2018-08-21 09:31:06 UTC,I can't reproduce this.
1784043,2018-08-10 12:37:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784043,2018-08-21 09:37:32 UTC,From the terminal log:
1784047,2018-07-27 18:07:11 UTC,test bug
1784060,2018-08-16 17:31:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784062,2018-09-24 14:46:46 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1784062,2018-09-15 05:16:24 UTC,"Reviewed:  https://review.openstack.org/602798
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e19d6f06e34ae14b9ae1d9a80678bbb53f52d488
Submitter: Zuul
Branch:    stable/queens"
1784062,2018-08-10 09:52:48 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.
1784062,2018-09-15 00:32:02 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/602798"
1784062,2018-07-27 19:38:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586643"
1784062,2018-07-31 02:01:25 UTC,"Reviewed:  https://review.openstack.org/586643
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=86a8aac0d76fa149b5e43c73b31227fbcf427278
Submitter: Zuul
Branch:    master"
1784063,2018-07-31 06:39:45 UTC,Please add version info.
1784063,2018-07-31 11:23:35 UTC,Last Nightly:
1784066,2018-08-08 21:38:35 UTC,This issue was fixed in the openstack/openstack-ansible 17.0.8 release.
1784066,2019-01-30 20:39:27 UTC,This issue was fixed in the openstack/openstack-ansible 16.0.25 release.
1784066,2019-01-22 18:00:28 UTC,"Reviewed:  https://review.openstack.org/632460
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=dcd6f2b031e3680f9381dad005a97c5eee91731d
Submitter: Zuul
Branch:    stable/pike"
1784066,2019-01-22 13:04:31 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/632460"
1784066,2018-08-05 12:40:28 UTC,"Also make sure this patch go along with above patch, i have verified it and without following patch ceph-ansible wont work."
1784066,2018-07-27 19:37:29 UTC,I am getting this error when trying to configure LVM base OSD
1784066,2018-08-02 15:56:16 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/588324"
1784066,2018-07-28 21:29:33 UTC,I remove /etc/ansible/role dir and re-run bootstrap which re-create all roles and i am not seeing individual ceph-* dir now only directory is there which is  /etc/ansible/role/ceph-ansible that is good
1784066,2018-07-27 19:38:07 UTC,This is what my config look like
1784066,2018-08-05 11:44:44 UTC,"Reviewed:  https://review.openstack.org/588324
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=97acfc5ea6cd50c46e5ab0139c6a00c00a5bb3f4
Submitter: Zuul
Branch:    stable/queens"
1784074,2018-07-28 13:10:07 UTC,Bug 1784093 opened for the things in comment 5.
1784074,2019-08-31 00:50:27 UTC,"Reviewed:  https://review.opendev.org/666438
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1ff029c1c3792f53865c6bdb3dce8d2c51b73ca7
Submitter: Zuul
Branch:    master"
1784074,2019-06-19 20:43:41 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/586713
Reason: I'm not actively working on this and there are changes to be made (and tested in detail) so I'm going to abandon. Someone else can pick up and run with the ideas in here if they feel the need."
1784074,2019-06-19 20:32:22 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/666438"
1784074,2019-04-26 13:58:01 UTC,https://review.opendev.org/655908 turns the script from mnaser into a nova-manage command.
1784074,2018-07-28 12:34:09 UTC,Thanks for the script mnaser! We also run into this situation often. Would be good to have this script in.
1784074,2019-04-26 13:57:34 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/655908"
1784074,2018-07-27 21:50:49 UTC,"Thanks for the script, I think it would be useful to have in nova-manage as a kind of cleanup/reporting tool in case of ""disaster recovery"" situations."
1784074,2018-07-27 21:44:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586713"
1784074,2018-07-27 21:36:13 UTC,"I added an updated version of the script that checks if build requests exist which should make it a tad more user friendly, and fix cell_id"
1784074,2018-07-27 21:22:38 UTC,I think we might be hitting this:
1784074,2018-07-28 00:55:14 UTC,I have come up with all of the following stacktraces that can result in us being in a weird state
1784080,2018-07-27 23:19:25 UTC,You can sort of do this already by exporting to vrml or step and placing the models in a sub-folder.  Of course you would have to manually remap your footprint 3d model links to use the cached models.  Remapping would be the important part of the this feature as the cache library code is already in place.
1784086,2019-05-14 08:18:30 UTC,I just followed these directions precisely and I cannot reproduce this. See attached juju status
1784086,2019-07-14 04:17:26 UTC,[Expired for OpenStack Designate Charm because there has been no activity for 60 days.]
1784091,2018-07-31 17:33:30 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1784091,2018-08-01 00:55:04 UTC,Yep! Confirmed. That works.
1784091,2018-08-01 00:57:57 UTC,Thanks Joseph!
1784093,2019-04-13 17:12:39 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.openstack.org/586742"
1784093,2019-04-13 17:12:45 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.openstack.org/586824"
1784093,2019-04-19 00:11:29 UTC,"NOTE: If you run into this issue and have orphaned build_requests table records causing servers without 'instance_mappings' table or 'instances' table records ('openstack server show' does not work on them) to show up in 'openstack server list', you can clean up the situation by manually deleting the matching records from the 'request_specs' and 'build_requests' tables in the API database."
1784093,2019-04-26 15:13:20 UTC,"Reviewed:  https://review.opendev.org/586742
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=85f8d033d27b31a6398529e0a25da74eae523b08
Submitter: Zuul
Branch:    master"
1784093,2019-04-28 18:16:58 UTC,"Reviewed:  https://review.opendev.org/656018
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=870e5bcfb6a5243a785b66353dda299286274e59
Submitter: Zuul
Branch:    stable/stein"
1784093,2019-04-26 21:52:56 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/656030"
1784093,2019-04-26 21:53:57 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/656031"
1784093,2018-07-28 19:51:35 UTC,That's what I was saying in the last paragraph of comment 0 -- that we could make delete handle the case where only a build request exists and no instance mapping.
1784093,2019-04-30 11:27:29 UTC,"Reviewed:  https://review.opendev.org/656030
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dc0ded897b5e5df89166c318f8bed3dbb6553fce
Submitter: Zuul
Branch:    stable/rocky"
1784093,2019-04-26 21:23:04 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656018"
1784093,2018-07-28 15:55:35 UTC,I pushed up a patch that does this alongside tests ^
1784093,2019-07-10 21:40:00 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1784093,2018-07-28 13:27:21 UTC,"Now that you say it, we might be able to work around it this way:"
1784093,2018-07-28 15:54:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586824"
1784093,2019-06-18 03:41:09 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1784093,2019-06-06 06:24:24 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1784093,2019-09-27 09:04:18 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1784093,2019-04-30 20:53:51 UTC,"Reviewed:  https://review.opendev.org/656031
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=22cd12dbb7fa5a7e0b98e4c42a73b4e7d34b0851
Submitter: Zuul
Branch:    stable/queens"
1784093,2018-07-28 04:04:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586742"
1784093,2018-07-28 13:09:52 UTC,Shouldn't delete go through _delete_while_booting and delete the build request and not barf on the instance mapping not being found?
1784094,2020-08-10 01:22:30 UTC,libmgba 0.6.3
1784095,2018-08-29 17:39:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784096,2018-07-28 03:08:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586737"
1784096,2019-05-29 15:34:18 UTC,"Change abandoned by Eric Harney (<email address hidden>) on branch: master
Review: https://review.opendev.org/586737
Reason: Neither this patch nor the bug describe why this is useful or needed."
1784096,2019-05-29 15:34:44 UTC,Closing this bug since it doesn't provide any info on why this is useful or needed.
1784100,2018-07-28 06:21:02 UTC,Oops... The problem seems even more widespread than just gnome-tweak-tool. Any kind of dialog from gnome seems to trigger the crash. Oh well.
1784100,2020-05-06 01:43:11 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1784100,2020-07-05 04:17:45 UTC,[Expired for gnome-tweaks (Ubuntu) because there has been no activity for 60 days.]
1784105,2019-08-18 13:42:14 UTC,openSUSE is using the PyOpenGL-3.1.3b2 and it is working well on Python 3.
1784116,2018-09-11 08:50:51 UTC,Thanks for your report.
1784118,2018-08-06 14:29:28 UTC,Hi Srinivas.
1784118,2018-09-03 17:43:11 UTC,Apologies for the late reply. The topic dropped off my radar.
1784118,2018-08-04 19:45:00 UTC,Checking with the team is good. Will it take long for a response to appear here?
1784118,2018-08-06 13:19:04 UTC,"Hi,"
1784118,2018-08-01 16:01:37 UTC,"Hi Geoff,"
1784120,2018-07-28 12:45:27 UTC,The reason G4 worked in the past was that it used tiff2pdf in the background. I switched to using PDF::API2 for the PDF engine in order to allow the use of the OCR layer behind the image.
1784123,2019-03-07 17:24:22 UTC,Issue confirmed with 2.6.14 and stable/rocky
1784123,2018-07-31 08:09:15 UTC,Related ansible bug: https://github.com/ansible/ansible/issues/43141
1784123,2018-10-01 14:59:42 UTC,"FYI, I can confirm this is still an issue on CentOS with the latest 2.6.4-1 release. 2.4.4.0-1 works."
1784123,2018-07-31 08:06:01 UTC,"Hi, is an issue with ansible 2.6, we're looking into a way to fix all the underfined variable we're finding with --tags."
1784123,2018-12-14 15:58:34 UTC,confirmed still an issue with ansible 2.7.4 and kolla-ansible queens.
1784124,2018-08-05 21:56:46 UTC,"The can't create /boot on RAID thing is unfortunate but fiddly and didn't get fixed in time for the point release. I'm not sure why your final attempt failed, we need to implement subiquity collect-logs or something similar :/"
1784124,2019-02-23 03:17:21 UTC,"Michael: You ack'd that /boot on RAID does not work to date, so there seems to be an issue there (admittedly duplicated by bug 1785332). Why is it incomplete?"
1784124,2019-02-23 06:28:59 UTC,"If this bug was just about /boot on raid, I'd have marked it as a
duplicate. But it also mentions an install failure with not enough
information to debug, hence incomplete."
1784124,2019-02-23 17:50:24 UTC,"Testing again with identically sized md0 component devices does not fix it - it fails with the same (except that I named the VG vg1 this time) message:
   Volume group ""vg1"" has insufficient free space (2044 extents): 2045 required."
1784124,2019-02-26 21:52:06 UTC,"I believe to have shown that the partitioning issue (""unknown error"" after manual partitioning) is a real, reproducible issue, affecting both Michael K. and me. Settings this back to confirmed.
If more info is needed then please state so and list the required information. Thanks!"
1784124,2019-11-11 23:04:22 UTC,"Both aspects of this bug are now fixed in the edge channel and will be released soon. (The ""can't put /boot on RAID"" has been fixed for a while, actually, but the RAID size calculation fix is new)."
1784124,2019-02-23 15:10:32 UTC,"Thanks for clarifying, Michael H-D. So I understand we are looking for more information on Maichael K.'s ""third try"" with this setup:"
1784131,2018-08-09 17:03:07 UTC,"It might be worth checking your anti-virus for any way to exclude your Temp folder, or the Open Rails application (RunActivityLAA.exe in this case), as this kind of error is a common symptom of an AV scanner."
1784135,2018-12-12 21:31:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784135,2019-01-04 16:38:44 UTC,Is there any progress on this? Waiting for upstream to solve the bug (see mail thread) may take more time then Bionic is even maintained. Currently this bug  (and #1772512) prevents Bionic to be usable even for simple multi-arch development work because important dev-libs can not be installed. Thanks.
1784135,2019-01-04 17:23:05 UTC,"> upstream to solve the bug
"
1784135,2019-01-05 12:04:59 UTC,"Thanks for answering. You are correct, ICU is fine, sorry for being too short."
1784138,2018-07-30 22:12:44 UTC,Understood.
1784138,2018-07-31 16:04:45 UTC,"'Perhaps have the ""are you sure"" prompt for all deletes ( not just numbered) or at least those with any comment.'"
1784138,2018-07-30 18:49:44 UTC,It sounds like this bug was file as a result of an incident-- sorry you experienced that. :\
1784139,2018-07-31 22:57:42 UTC,This is the GTK2-GTK3 incompatibility issue.
1784139,2018-07-28 20:07:45 UTC,"@jeyjey Jeff, didn't you fix similar issues in the past?"
1784139,2018-08-01 20:09:46 UTC,"Thank you Seth,
how can I deal with this? Do I understand this correctly, that this is an issue at compile time of KiCad?"
1784142,2018-07-30 03:42:07 UTC,The driver failed to build due to a compiler crash:
1784156,2018-07-28 16:30:06 UTC,This change was made by a bot.
1784156,2018-07-31 17:31:56 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1784156,2018-08-01 06:15:40 UTC,Is it possible for you to try https://cgit.freedesktop.org/~agd5f/linux/ branch amd-staging-drm-next?
1784156,2018-12-11 00:31:25 UTC,The bug is still present with Linux 4.20-rc6 from the mainline PPA unless I add
1784157,2018-08-07 12:08:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784157,2018-08-24 14:53:45 UTC,"I removed some broken package, founded from:"
1784158,2020-03-20 08:43:12 UTC,Closing because INVALID: Works as intended.
1784158,2018-07-28 19:58:18 UTC,"I found the culprit, and it is the SVG (created by python+osmnx): there is a set of filters embedded into the file. Removing this text everything goes back to normal.
My question now: as my error can happen, would it be possible to add a ""CLEAN SVG"" command where all but the vector info+colors is removed?"
1784158,2020-03-20 08:42:32 UTC,"There's a Color Shift filter applied to all three maps, hence the colors being ""wrong""."
1784159,2018-08-28 22:26:00 UTC,Fixed in https://github.com/juju/juju/pull/8988
1784163,2018-07-28 17:46:26 UTC,"> apport-bug didn't work. After I click Send, I got no browser prompt to finish my report. This might be because I have an unusual Firefox setup (multiple profiles).
"
1784163,2018-07-28 17:47:30 UTC,"> OTOH, apport-collect brought up Firefox for authorization just fine.
"
1784163,2018-07-28 17:55:27 UTC,I attached gdb to the running (hung) process. Here's a backtrace:
1784163,2018-07-28 18:01:42 UTC,Here's a backtrace with symbols from /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 added:
1784163,2018-07-28 18:08:40 UTC,Looks like it's hung here:
1784163,2018-07-30 09:35:37 UTC,I was forced to reboot due to a wifi hang so I no longer have the process available. However I can try again to reproduce if you like - gnome-initial-setup came up on next login. I'll wait though in case you want me to instrument anything first.
1784163,2020-04-24 23:30:59 UTC,I can confirm that this issue is still present in Ubuntu 20.04.
1784163,2020-05-21 08:32:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784165,2018-08-01 16:39:37 UTC,"FWIW, pins can use wildcards.  You could have used *-proposed instead of artful-proposed (and maybe the wiki docs should recommend that) and you wouldn't have run into this issue."
1784165,2018-07-31 18:47:03 UTC,"The release-upgrader currently only disables -proposed if people are updating to the development release of Ubuntu, which bionic is not. These changes were made in bug 1199157 when -proposed became a testbed for the development release. Could you explain why you think -proposed should be disabled if people are upgrading to a release other than the development one?"
1784165,2018-08-01 11:16:49 UTC,"> Could you explain why you think -proposed should be disabled...
"
1784172,2018-07-28 20:00:07 UTC,This change was made by a bot.
1784172,2018-07-31 18:25:58 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1784172,2018-08-31 19:52:45 UTC,"I have just found the issue also here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342
Can you explain why this bug was nominated against a series that is no longer supported?
The model 7139 is still supported by Dell."
1784180,2019-09-16 14:26:33 UTC,Migrated to https://github.com/widelands/widelands/issues/1708
1784180,2018-08-26 12:47:17 UTC,"Try destroying the flag of your HQ... You may as well leave the code untouched, since this is a long-existing bug and nobody else complained."
1784180,2018-08-26 11:37:24 UTC,"I don't want to dig into this deeply for Build 20, since players should be able to get around the bug by destroying the flags, and carriers are a free resource anyway."
1784180,2018-08-25 21:48:11 UTC,"The attached branch is indeed a hack, cause it addresses the warning message instead of the underlying issue, which is that road-removal does not update the game's state properly."
1784180,2018-08-25 17:11:05 UTC,I have attached a branch that will solve the problem - I am wondering if there's a more efficient solution though. It feels quite hacky.
1784180,2018-08-04 21:32:28 UTC,"In my case, modifying the game during Pause mode has been useful with debugging."
1784180,2018-08-04 18:32:38 UTC,"OK, got it. Just build the first road until the first flag is possible, then build the second road until the first flag is possible. The console output says:"
1784180,2018-08-04 10:35:09 UTC,"Don't remove any flag, remove the two roads (or segments) in the specific order."
1784180,2018-08-04 08:22:11 UTC,"Hm, i can't reproduce this. Maybe i do something wrong:"
1784183,2018-07-29 21:24:15 UTC,apport information
1784183,2018-07-29 21:24:16 UTC,apport information
1784183,2018-07-29 21:24:17 UTC,apport information
1784183,2018-07-29 21:24:19 UTC,apport information
1784183,2018-07-29 21:24:13 UTC,apport information
1784183,2018-07-29 21:24:21 UTC,apport information
1784183,2018-07-29 21:24:23 UTC,apport information
1784183,2018-07-31 17:28:16 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1784183,2018-08-01 15:20:42 UTC,kernel-fixed-upstream
1784183,2018-07-29 21:24:20 UTC,apport information
1784183,2018-07-29 21:24:10 UTC,apport information
1784183,2018-07-29 21:24:07 UTC,apport information
1784183,2018-07-29 21:24:08 UTC,apport information
1784183,2018-07-29 21:24:09 UTC,apport information
1784183,2018-07-29 21:24:05 UTC,apport information
1784183,2018-07-29 21:24:03 UTC,apport information
1784183,2018-07-29 21:24:02 UTC,apport information
1784183,2018-07-29 21:24:01 UTC,apport information
1784183,2018-07-29 21:24:00 UTC,apport information
1784183,2018-07-29 21:23:58 UTC,apport information
1784183,2018-07-29 21:23:56 UTC,apport information
1784183,2018-07-29 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1784183,2018-07-29 18:34:00 UTC,"Hello,"
1784186,2018-07-29 20:13:33 UTC,Thanks for reporting.
1784187,2020-03-27 22:35:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784190,2020-05-21 04:17:22 UTC,[Expired for Kazam Screencaster because there has been no activity for 60 days.]
1784190,2020-01-27 22:37:26 UTC,Works fine for me in Ubuntu 18.04. Note that Kazaam needs to be running in order for the shortcuts to work.
1784190,2020-03-21 23:47:40 UTC,What version of Kazam are you using?
1784191,2018-08-01 19:00:46 UTC,Thanks for filing this bug in Ubuntu.
1784191,2018-08-02 00:03:52 UTC,"Andreas,
Thanks for your response. I agree with your assessment, this is a corner case. I use ssmtp instead of a MTA because I just want to send an email from a script. As in the case of smartd,I have smartd call my script which sends the test message and also the output of smartctl -H which reports the health of the hard drive. So upon start up I get an email reporting the health of my drives. So this is defiantly a local preference."
1784192,2018-07-30 19:41:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784196,2019-04-16 16:35:23 UTC,This bug was fixed in the package maven-dependency-plugin - 3.1.1-1~18.04
1784196,2019-04-16 16:32:57 UTC,This bug was fixed in the package gmbal - 4.0.0-b002-1~18.04
1784196,2019-04-16 16:33:00 UTC,This bug was fixed in the package gmbal-commons - 3.2.1-b003-1~18.04
1784196,2019-04-16 16:31:11 UTC,This bug was fixed in the package stax-ex - 1.7.8-3~18.04.1
1784196,2019-04-16 16:33:22 UTC,This bug was fixed in the package jaxrs-api - 2.1.2-2~18.04
1784196,2019-04-16 16:33:25 UTC,This bug was fixed in the package jaxws-api - 2.3.0-1~18.04
1784196,2019-04-16 16:33:46 UTC,This bug was fixed in the package jws-api - 1.1-1~18.04
1784196,2019-04-16 16:34:28 UTC,This bug was fixed in the package libstax2-api-java - 4.1-1~18.04
1784196,2019-04-16 16:34:32 UTC,This bug was fixed in the package libwoodstox-java - 1:5.1.0-2~18.04
1784196,2019-04-16 16:34:58 UTC,This bug was fixed in the package jaxws - 2.3.0.2-1~18.04.1
1784196,2019-04-16 16:35:53 UTC,This bug was fixed in the package mimepull - 1.9.7-1~18.04
1784196,2019-04-16 16:54:47 UTC,This bug was fixed in the package jaxb - 2.3.0.1-7~18.04
1784196,2019-04-16 16:43:16 UTC,This bug was fixed in the package gmbal-pfl - 4.0.1-b003-2~18.04
1784196,2019-04-16 16:43:35 UTC,This bug was fixed in the package istack-commons - 3.0.6-3~18.04
1784196,2019-04-16 16:44:43 UTC,This bug was fixed in the package jaxb-api - 2.3.1-1~18.04
1784196,2019-04-16 16:44:46 UTC,This bug was fixed in the package jaxrpc-api - 1.1.2-2~18.04
1784196,2019-04-16 16:48:39 UTC,This bug was fixed in the package metro-policy - 2.7.2-3~18.04
1784196,2019-04-16 16:50:29 UTC,This bug was fixed in the package saaj - 1.4.0-3~18.04.1
1784196,2019-04-16 16:50:45 UTC,This bug was fixed in the package stax-ex - 1.7.8-3~18.04.1
1784196,2019-04-16 16:54:51 UTC,This bug was fixed in the package jaxe - 3.5-11~18.04
1784196,2019-04-16 21:03:01 UTC,This bug was fixed in the package jaxws - 2.3.0.2-1~18.04.1
1784196,2019-04-16 16:30:36 UTC,This bug was fixed in the package saaj - 1.4.0-3~18.04.1
1784196,2019-04-16 16:36:10 UTC,This bug was fixed in the package saaj-ri - 1.4.1-1~18.04
1784196,2019-04-16 16:28:39 UTC,This bug was fixed in the package metro-policy - 2.7.2-3~18.04
1784196,2019-04-16 16:23:21 UTC,This bug was fixed in the package gmbal-pfl - 4.0.1-b003-2~18.04
1784196,2019-04-16 16:24:51 UTC,This bug was fixed in the package jaxb-api - 2.3.1-1~18.04
1784196,2019-02-26 17:57:43 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:00:32 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-04-16 16:24:52 UTC,This bug was fixed in the package jaxe - 3.5-11~18.04
1784196,2019-02-26 18:03:55 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:06:31 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:08:36 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:10:19 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:13:10 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:19:22 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:23:24 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:25:41 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:03:22 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:31:34 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:33:26 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:35:26 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:37:17 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:42:12 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:44:03 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 18:45:13 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-02-26 11:17:29 UTC,"Hello Matthias, or anyone else affected,"
1784196,2019-04-16 16:24:17 UTC,This bug was fixed in the package istack-commons - 3.0.6-3~18.04
1784196,2019-04-16 16:24:47 UTC,This bug was fixed in the package jaxb - 2.3.0.1-7~18.04
1784196,2019-02-26 18:28:25 UTC,"Hello Matthias, or anyone else affected,"
1784197,2018-09-07 19:32:21 UTC,"From my limited knowledge in French, I assume the error reads ""segmentation fault"" in the top right terminal. Here's an in-depth Wikipedia article: https://en.wikipedia.org/wiki/Segmentation_fault"
1784197,2019-11-10 14:49:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784197,2018-08-27 14:19:22 UTC,"Maybe the issue is related to the ABNT2 keyboard layout, so it doesn't happen everywhere. If it happened with all keyboard layouts, probably it would have been noticed."
1784197,2018-08-26 19:36:23 UTC,"This issue does not affect me under the description that you have supplied. I have tried holding down the left click and pressing the shift key a few times while still holding down the left click, pressing the shift key alone if while the window was in focus and clicking around the application's graphical interface while holding down the shift key at the same time. It was also within the Wayland session (just noticed the tag). If you send a more detailed description of your actions that led up to the crash, I will try to recreate the crash according to those directions. Have a nice day!"
1784197,2018-08-27 15:15:47 UTC,This is the backtrace: https://paste.ubuntu.com/p/szCZq3grFW/
1784213,2018-09-05 10:23:27 UTC,"Hi,
this should be done since version 6.0.1-6 : https://launchpad.net/ubuntu/+source/llvm-toolchain-6.0/1:6.0.1-6"
1784222,2018-08-01 16:04:04 UTC,"Hi Declan,"
1784224,2018-12-10 01:48:16 UTC,"This was an issue with QT5.   Its fixed in the latest development sources
on gitlab."
1784224,2019-04-05 20:52:12 UTC,Still a problem for all releases including upcoming 19.04 - see https://packages.ubuntu.com/search?suite=disco&arch=any&mode=exactfilename&searchon=contents&keywords=gvedit .
1784229,2018-07-29 16:21:08 UTC,I'm currently working around it by bind-mounting the upstream source over the Ubuntu package thus:
1784231,2018-07-29 15:26:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784234,2018-07-29 20:39:19 UTC,Could not calculate the upgrade
1784235,2018-08-25 10:38:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784235,2020-08-09 23:39:00 UTC,pdfsam-basic (3.3.6-1)
1784237,2018-07-29 18:15:51 UTC,"According to Google Translate the error message is in Russian. In English it is:
""One process installed post-installation script returned error code 1"""
1784240,2020-07-28 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1784240,2020-05-28 09:38:25 UTC,is it still an issue on 20.04?
1784240,2018-08-09 03:26:01 UTC,"On 2018-08-08 12:22 AM, ppanon wrote:"
1784240,2018-07-30 03:38:46 UTC,The driver updates in July I think are the upgrade to Mesa 18.0.5.
1784240,2018-07-29 19:21:42 UTC,This log shows updated driver deployments on July 23rd coincident with the start of the detection problems.
1784240,2018-07-29 19:20:20 UTC,"This log shows that the probing detects the high resolution modes
[   111.418] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
[   111.418] (II) AMDGPU(0): Modeline ""3840x2160""x60.0  533.25  3840 3888 3920 4000  2160 2163 2168 2222 +hsync -vsync (133.3 kHz eP)
[   111.418] (II) AMDGPU(0): Modeline ""3840x2160""x30.0  297.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync (67.5 kHz e)"
1784240,2018-08-08 06:42:41 UTC,Do you have amdgpu-pro installed? It stops working if mesa gets an update..
1784242,2020-10-04 11:01:54 UTC,"Same here on Ubuntu 20.04, it is not 100% working, but amount of formats improved signficantly, that it is more an exception, if something does not work."
1784242,2020-09-30 20:39:38 UTC,"After upgrading to Ubuntu 20.04.1, and reinstalling gstreamer1.0-vaapi, the problems does not seem to occur any more?"
1784242,2019-12-31 23:42:34 UTC,Confirm bug present on Ubuntu 18.04
1784242,2019-05-25 14:37:43 UTC,This bug is present with Ubuntu 19.04 too. VLC works fine. Problem is with the default Gnome Videos player. Mine is a Dell laptop XPS 15 L501x. Solution from Cristhian Steven Echeverry Z. #6 worked for me. Thank you.
1784242,2019-05-13 09:10:20 UTC,"The solution from Christhian worked for me, thanks!"
1784242,2021-01-16 20:10:18 UTC,Just installed xubuntu 20.04.
1784242,2018-09-19 19:59:10 UTC,One more comment - I recently discovered this libva bug:
1784242,2018-09-17 19:51:48 UTC,I can also confirm the issue.
1784242,2018-09-14 08:43:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784242,2018-08-18 21:05:54 UTC,"There seems to be similar reports about green screens with Ironlake Intel CPUs and VA-API :
https://askubuntu.com/a/1053324/555062
https://github.com/mpv-player/mpv/issues/2123
https://bugs.freedesktop.org/show_bug.cgi?id=91309"
1784242,2018-08-17 20:58:52 UTC,"After some more tests, the green screen does not affect all the H264 videos, but only some of them.
It does not seem to depend on the container (Matroska or Quicktime), on the FPS, on the H264 profile or on the encoding software."
1784242,2019-04-25 21:31:36 UTC,"I had the same problem, I solved it by running sudo apt remove gstreamer1.0-vaapi and sudo apt autoremove."
1784247,2018-07-29 22:34:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/586907"
1784247,2019-07-22 07:30:30 UTC,What do you want to achieve? Data context is a user-related data and has potentially an unlimited size. We can't log it. We can only log a trimmed version of it but it's not much useful practically.
1784247,2019-08-28 06:34:49 UTC,"Change abandoned by Renat Akhmerov (<email address hidden>) on branch: master
Review: https://review.opendev.org/586907
Reason: No changes for too long."
1784250,2020-03-20 15:55:23 UTC,Closing because FIX RELEASED.
1784252,2020-08-03 15:45:46 UTC,"If I'm understanding correctly, this is because using the Move Selected Pixels tool selects the area that you just moved (tools / effects only operate within the selected area). You can use Edit - Deselect All if you want to fill outside the selection."
1784257,2019-08-17 06:46:06 UTC,"Is KiCad targeting only professional users, so correctness shall be so essential? If yes, then Step scaling shall be removed along with scale/offset/rotate options of 3D model view. To ensure the 3D view will look exactly as any 3D export."
1784257,2019-08-17 09:28:41 UTC,"Then all scaling options for STEP files should be removed, not just in
the kicad2step output, but also in the footprint 3d viewer."
1784257,2019-08-17 10:07:49 UTC,"I vote for solution Seth mentioned. I.e. flexibility.
Rationale: sometimes I need to quickly adopt existing footprint, but have no skills in FreeCAD etc so I prefer scaling of existing & similar models. Like making cylindrical capacitor a bit higher (I bet there will never a situation that library will have all possible 3d models)."
1784257,2019-08-17 14:03:22 UTC,What scale are be talking about?
1784257,2019-08-17 23:19:07 UTC,I guess there are a number of issues:
1784257,2019-08-17 23:25:03 UTC,"I understand you may want STEP for 3D printing or even to check that
your design of a case will be OK for the board you will be making, but
scaling STEP is really something not done in industry and for very
good reason.  Take time to have a look at Maurice's StepUp tools and
learn to use them. Then if you want to scale a cylinder or a box you
can do it easily and you can be happy knowing that you have the
correct sizes and will not accidentally change them."
1784257,2019-08-18 08:40:02 UTC,"The reason why I implemented this in the first place was a STEP model
with bad scale, so I guess they do exist."
1784257,2019-08-18 09:08:45 UTC,"@corecode, can't you just use freecad or any other MCAD for this?"
1784257,2019-08-17 06:13:22 UTC,"I'll be very happy with that, thank you. That should allow people who
require no scaling to use the software and people who want to scale
can do as they please."
1784257,2019-08-18 09:23:46 UTC,"I think it would be acceptable if we had an external tool which can
resize/reorient/reposition a STEP model.  This would not conflict with
the requirements that the ECAD does not modify the STEP files since
someone has to run this tool independently and it will not affect any
other users.  It will also be of general use to people who want to use
a STEP model found on the internet who need to reorient or reposition
the model.  I suspect the StepUp tools already have that capacity, in
which case I would think we should direct more people to that tool and
maybe build up more tutorials on how to solve specific problems."
1784257,2019-08-18 23:11:37 UTC,Looks like this was cherrypicked onto 5.1
1784257,2019-08-31 14:24:18 UTC,I'm setting this back to 'In Progress' as I cannot find a commit that addresses the comments in the discussion above. Please set back to 'Fix Committed' if this was indeed resolved.
1784257,2019-08-31 18:53:10 UTC,"Better open a new issue, or rename this one, because now STEP export
does scale parts."
1784257,2019-09-10 16:32:18 UTC,What was the decision on keeping this implementation of the scaling of the STEP models? Will JP's comment about the scaling factor source in #26 be addressed (My quick test of the 5.1 branch shows that it still uses the VRML scaling as the source of the scaling)?
1784257,2019-09-10 16:55:05 UTC,"The immediate plan is to disable scaling the VRML-matched step file and bypass the scale code for models that are at 0,0,0 scaling."
1784257,2019-10-20 15:43:25 UTC,"@Seth, did you revert this from 5.1.5 yet?"
1784257,2019-10-20 17:08:05 UTC,Thanks for the reminder.  Done.
1784257,2019-08-18 09:12:58 UTC,"If the STEP model has a bad scale, it is the wrong model.
This is for me similar to use a wrong footprint, and to expect to have a scale factor to modify its size (Yes, yes, we have a request for that...)."
1784257,2019-08-17 04:36:30 UTC,"How about scaling disabled by default with a checkbox to enable a non-unity scale?  When disabled, the routine to scale through OpenCascade is bypassed."
1784257,2019-08-17 01:34:42 UTC,"Sure, Cirilo, you should not scale your models. This is your policy."
1784257,2019-08-17 02:35:45 UTC,@Cirlio-  Can you explain a bit more your concern here?  Models default to 1.0 scale.  I have not observed any issues with defaults in my testing.  Did you see something that didn't work correctly?
1784257,2019-08-17 03:34:11 UTC,"The point from a mechanical engineering point of view is that there is
a possibility at all of accidentally changing the scaling. We need an
option to completely disable scaling, including not making the
OpenCascade calls to perform any scaling at all. It is not good enough
to tell people ""you need to check and make sure you set it to 1.0"" or
even for OpenCascade to perform a 1:1:1 scaling; if this happens then
it becomes far more (and unnecessarily) difficult to verify designs.
This is why when this issue was raised in the past I marked it ""will
not fix"" and provided an explanation. If electronics designers are
given a STEP model to work with and the mechanical people have
verified that it is a good model, it is essential that the model's
dimensions will not be distorted in any way by the ECAD software;
otherwise the mechanical designers can't trust what the electronic
designers give them without going through another unnecessary and
expensive process. This is why the IDFv3 exporter will not scale
things either.  I added STEP output because IDF was too crude for my
needs.  I'll be happy with this option to disable all scaling; at
least I'll know that my models are not in danger of being distorted. I
think this case of scaling STEP is an example of what non-experts
might think is a good idea, but works completely against what
professionals do. In the MCAD world if you want to make changes like
that, it needs to be controlled by a parameter table so that the
source of the variants is well known and can be checked again if
necessary. Even then, a parametrically generated model output will be
verified and no changes to dimensions allowed without going through a
vetting process.  Neither Altium nor Cadence will *ever* scale a STEP
model for these same reasons."
1784257,2018-08-28 09:44:20 UTC,"Application: kicad
Version: (5.0.0), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011
Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON"
1784257,2018-08-28 10:00:01 UTC,Scaling is not supported for step or iges models
1784257,2018-08-28 10:39:59 UTC,"So maybe at least warning about not supporting scaling for step export should be shown.
This can result as a really big consequences when you will make some housing with step model which isn't real model of your PCB.
In this project we had to redesign housing because PCB was bigger then step model."
1784257,2018-08-28 11:08:02 UTC,We should be applying the scale transformation when STEP models are not scaled to 1.0
1784257,2018-08-28 15:33:12 UTC,"@Seth, it looks like the electrolytic capacitor model shown in supplied image was just scaled in the vertical axis.  I'm guessing your solution would scale the model in all three axis which would not be correct in this case.  Is there a function:"
1784257,2018-08-28 16:00:14 UTC,"That's a good call, Wayne."
1784257,2018-09-28 03:43:59 UTC,"Just to add -- I noticed this, too. I exported a board to STEP, and some of the transformations were botched, and one part model was not included in the export at all."
1784257,2018-08-28 15:55:51 UTC,"Hi guys, I totally forgot about this issue."
1784257,2018-11-13 18:37:37 UTC,I'm fine with pushing this off to v6.  I think we have enough issues to resolve for 5.1.
1784257,2019-05-21 13:44:33 UTC,"@Seth, I think it ia still useful to keep the related fileformat, in this case 'step', as a tag on this bug. I makes it easier to search for ""step export"" related issues."
1784257,2019-05-21 14:02:01 UTC,I removed it bc it is not one of the official tags.  Maybe we add it or similar to the list?
1784257,2019-05-21 20:57:07 UTC,"@Seth, it is now."
1784257,2019-08-15 21:32:17 UTC,"Fixed in revision a0ed40876d8944e9d344b1aab8d1c265dd6cf550
https://git.launchpad.net/kicad/patch/?id=a0ed40876d8944e9d344b1aab8d1c265dd6cf550"
1784257,2019-08-16 22:41:28 UTC,"This is broken behavior; STEP must never scale parts or else there is
no guarantee that the output will be treated correctly by MCAD.  We
should not risk the usability of the STEP file just because some
people are too lazy to create a suitable model. STEP is for MCAD
integration, not eye candy. People who do not have the discipline to
create the necessary models should not use the MCAD features."
1784257,2018-07-30 14:15:37 UTC,Please add version information and a demo project.
1784257,2019-08-17 01:59:46 UTC,"The problem is that people who genuinely need the MCAD features now
have a problem with uncontrolled model dimensions. This would make the
software unacceptable for professional use; why should engineers who
put a lot of time into verifying their mechanical models are suitable
for use now be burdened with an extra step of making sure the models
are not being scaled ad hoc? At the very least we need a configuration
option for kicad to force all scaling parameters to unity, and on the
export side if the scale factors are within a certain tolerance then
the code which executes scaling should not even be invoked. Mechanical
correctness is absolutely crucial for people who do this for a living.
I didn't add the MCAD export features just because I thought it would
be fun."
1784257,2018-11-13 15:41:26 UTC,"I think this is not important for 5.1.0, I think we could postprone the milestone to v6"
1784259,2018-08-30 20:03:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/598334"
1784259,2020-09-03 11:28:51 UTC,"Speaking about the ""issue"" when call is done by admin user, it's still the same code https://github.com/openstack/neutron/blob/4f10c3bd3f57836aeb1b6ba4305301d63c046bd0/neutron/policy.py#L470 so I assume that an admin user still can do everything. Should we change that?"
1784259,2019-04-16 08:50:28 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/584601
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1784259,2018-09-25 22:05:07 UTC,"Reviewed:  https://review.openstack.org/598334
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=d14b379d1c16d451f35d026ab83702ca631f2e4f
Submitter: Zuul
Branch:    master"
1784259,2018-09-21 02:11:28 UTC,"Change abandoned by Felipe Monteiro (<email address hidden>) on branch: master
Review: https://review.openstack.org/584217"
1784259,2018-08-04 01:16:57 UTC,"Thanks, Miguel. In that case I've switched the report to Public Security and ended the embargo so discussion can continue in the open."
1784259,2018-07-30 14:05:17 UTC,"The public changes in review at least hint pretty heavily at this reported vulnerability, so there's probably very little point in trying to keep it under wraps with an embargo."
1784259,2018-08-02 00:48:12 UTC,"@Akihiro, will comment on (b). Will look into (a) more closely when time permits."
1784259,2018-07-31 20:00:37 UTC,"According to my test results, this topic is split into two:
(a) when a user does not have the admin role, I cannot reproduce the issue
(b) when a user has the admin role, the policy check (at least when creating a resource) seems skipped."
1784259,2018-07-31 00:14:24 UTC,"No need to apologize. I wasn't trying to point out any wrongdoing, merely highlighting that the additional effort needed for embargoed discussion and development probably isn't warranted given the public nature of the linked reviews (but I'd like to see someone from neutron-coresec agree with that assertion first, so I haven't switched the report to public security yet)."
1784259,2018-07-30 17:05:29 UTC,@Jeremy I apologize. I should've been more prudent about it. I just stumbled into this and am now trying to course correct.
1784259,2018-07-30 14:04:19 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1784259,2018-08-04 00:30:30 UTC,"I agree that patches are already public, so I don't the cost of the embargo is warranted any more"
1784262,2018-10-05 11:13:21 UTC,"Please check if there are any hints in ~/.xsession-errors.old (generated by the previous session), or in the LightDM log files which are located in /var/log/lightdm."
1784263,2020-10-26 11:20:22 UTC,What is the status?
1784263,2020-11-17 14:40:42 UTC,"This is not yet fixed, we need to be careful on not losing the coverage for stable branhes"
1784264,2018-07-31 16:33:46 UTC,"It looks like the reason behind this is the version of your repo server is not centos 7.5 but the other contains are centos 7.5.  I suggest updating all of your containers to the latest release, and then rerunning repo-build.yml and you'll get centos-7.5 venvs and thinks will work"
1784271,2018-08-07 08:28:24 UTC,"Hi,"
1784274,2019-01-10 14:10:13 UTC,"The issue seems an upstream one, could you maybe report it to them as well on https://gitlab.gnome.org/GNOME/gnome-calculator/issues ?"
1784287,2019-07-31 12:40:38 UTC,"There has been no activity on this bug report for quite a long time and the ""missing dependency gir1.2-goa-1.0"" bug in Debian is now fixed. So I'm closing the bug now.
However, please reopen it if you still can't launch gnome-music."
1784287,2018-09-19 06:39:13 UTC,Originally you told libgoa-1.0-dev was the solution but let's try with gir1.2-goa-1.0 which is a dependency of libgoa-1.0-dev. Usually the -dev packages are only needed when compiling programs from source.
1784287,2018-09-18 23:00:18 UTC,"Steps to encounter problem:
1. Install gnome-music
2. Launch GNOME music, and see that it doesn't launch"
1784287,2018-09-18 20:22:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1784322,2020-07-18 19:24:57 UTC,This seems to have been fixed - I could fill out the captcha when trying just now
1784336,2018-07-31 15:24:21 UTC,Possibly same bug reported in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896090
1784336,2018-07-31 19:48:18 UTC,"Would you be able to share the config for a reproducer of this bug? I suppose you have a lot of proxy balancers, and/or vhosts?"
1784336,2018-08-01 08:40:07 UTC,"Sorry, it's production so it's not be possible.
Yes, 31 proxy balancer and 200 vhosts
We have to do a restart for each modification, and modify the logrotate (replace the reload by restart) to avoid the crash each morning."
1784336,2018-08-01 14:05:24 UTC,"It could be https://bz.apache.org/bugzilla/show_bug.cgi?id=62044. That patch (https://bz.apache.org/bugzilla/attachment.cgi?id=35723) is quite big  (~30kbytes), but applies cleanly to the bionic package."
1784336,2018-08-07 07:57:54 UTC,"I compiled the version with
apache2_2.4.29.orig.tar.gz,patch of apache2_2.4.29-1ubuntu4.2.debian.tar.xz and the patch of
https://bz.apache.org/bugzilla/attachment.cgi?id=35723"
1784342,2019-05-09 03:21:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784342,2020-09-06 08:48:48 UTC,"Anyone who comes across this issue, resulting in denial of service from neutron-server with the exceptions mentioned in the OP, it's reasonably painless to workaround; simply delete the subnet(s) with NULL network_id:"
1784342,2020-07-28 01:54:54 UTC,"Hi, James, do you know how to reproduce this error? I think the foreign-key will prevent the deletion from the networks table until the subnet was deleted, so it seems that the field network_id will not be null in any time. `https://review.opendev.org/#/c/677221/` this patch force `network_id` not to be null, but how it works?"
1784342,2020-07-20 06:53:58 UTC,Ah - this behaviour was enforced @ train
1784342,2020-07-20 06:38:32 UTC,Full create table command:
1784342,2019-05-03 01:31:01 UTC,"subscribed field-high, added Ubuntu Neutron package, since this has occurred in multiple production sites."
1784342,2020-07-20 06:36:09 UTC,I had a dig around in the database - the subnets table has a foreign key reference to the networks table:
1784342,2019-04-02 19:30:29 UTC,"We have had an incident of a network being deleted, but the recursive subnet deletions failing under load happening in a production Xenial-Queens cloud."
1784342,2018-09-29 04:18:01 UTC,[Expired for neutron because there has been no activity for 60 days.]
1784342,2018-07-30 15:01:17 UTC,"I have not seen this kind of an issue before.  Do you see these kinds of results consistently - in other words, if you run the rally tests 10 times, it experiences this issue ten out of ten of the attempts, even if the environment has been restacked in the meantime?  We certainly run rally tests in the gate using pecan_wsgi on the stable/queens branch and they succeed; [1] is an example of such a run."
1784342,2018-07-30 14:23:59 UTC,"I'm not sure, I was not the one running the tests, I think this was caused by a MySQL timeout issue on our side however unless the creation of a subnet and the population of network_id is separat, or if the rally tests removes a subnet from a network and adds it to another then it's probably not an issue in the Neutron side."
1784342,2018-07-30 14:10:52 UTC,"rally-jobs/neutron.yaml in rally-openstack repo, you mean?"
1784342,2018-07-30 13:34:50 UTC,"It was neutron CRUD test. NeutronNetworks - create, update, list and delete network, subnets and ports in burst"
1784342,2018-07-30 12:27:21 UTC,what kind of rally tasks did you run?
1784342,2019-05-03 01:16:48 UTC,"Seen again in a Bionic-rocky cloud.  One subnet was in the table without a matching network id.  Deleted that row, and things worked again."
1784353,2019-03-22 03:46:33 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1784353,2018-12-19 20:48:17 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1784353,2018-11-09 18:37:35 UTC,"Reviewed:  https://review.openstack.org/612496
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3a0f26c822912dbaad7c8a1d6a3c599025afab37
Submitter: Zuul
Branch:    stable/queens"
1784353,2018-11-09 17:17:48 UTC,"Reviewed:  https://review.openstack.org/612495
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=51345d57a1b726dad08445a5c5a47c4e640c2a43
Submitter: Zuul
Branch:    stable/queens"
1784353,2018-11-09 17:17:37 UTC,"Reviewed:  https://review.openstack.org/612494
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6fa5aee86b7a8a94bf4644c1aff3ac0c70079811
Submitter: Zuul
Branch:    stable/queens"
1784353,2018-11-06 06:01:04 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1784353,2018-11-01 07:18:29 UTC,"Reviewed:  https://review.openstack.org/612487
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2a741be8f53e4e6b3a5be6cdc2fe32f050c870a9
Submitter: Zuul
Branch:    stable/rocky"
1784353,2018-10-31 18:38:52 UTC,"Reviewed:  https://review.openstack.org/612486
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=96889ad06d2e4841527e5b9d7c1b4ca71a7ae189
Submitter: Zuul
Branch:    stable/rocky"
1784353,2018-10-31 18:38:42 UTC,"Reviewed:  https://review.openstack.org/612485
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3452b603a109d05c091246e4ff37e8f1997c0d50
Submitter: Zuul
Branch:    stable/rocky"
1784353,2018-10-23 03:10:56 UTC,"Reviewed:  https://review.openstack.org/587071
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=41452a5c6adb8cae54eef24803f4adc468131b34
Submitter: Zuul
Branch:    master"
1784353,2018-10-22 22:56:42 UTC,"Reviewed:  https://review.openstack.org/587014
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a8629e5800ed95c0e6bac04ca711e835606370bf
Submitter: Zuul
Branch:    master"
1784353,2018-08-02 13:43:09 UTC,"Just for my own notes, this is where we call _shutdown_instance prior to reschedule if driver.spawn fails:"
1784353,2018-10-22 20:10:43 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/612495"
1784353,2018-10-22 20:10:25 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/612494"
1784353,2018-10-22 19:44:39 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/612487"
1784353,2018-10-22 19:44:23 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/612486"
1784353,2018-10-22 19:44:07 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/612485"
1784353,2018-08-02 13:20:32 UTC,"Bug 1488111 is what I was thinking about, but Lee clarified the issue for me. The scenario is like:"
1784353,2018-08-02 13:17:09 UTC,I'm not sure how you're hitting a reschedule because any failures coming out of attach_block_devices should result in the build getting aborted:
1784353,2018-07-30 14:04:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587071"
1784353,2018-07-30 11:49:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/587014"
1784353,2018-07-30 11:48:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/587013"
1784353,2018-10-22 20:11:00 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/612496"
1784358,2019-04-12 14:30:42 UTC,Still happens on fully upgraded 18.04.2:
1784358,2018-07-31 08:55:32 UTC,"I have raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=537526 to cover the installer issue.  There are similar bugs marked as fixed for the main Eclipse code, but as this is still visible and relates to the installer, not the main binary, I raised a new bug."
1784358,2019-04-12 14:23:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784358,2018-07-30 13:02:20 UTC,Reinstalling Eclipse and Eclipse C/C++ Development Tooling also did not change the error.
1784358,2018-07-30 12:59:58 UTC,$ sudo apt-get install --reinstall libequinox-osgi-java
1784358,2018-07-30 10:56:08 UTC,Reviewing the Debian equivalent people have suggested that:
1784358,2018-07-31 08:25:38 UTC,I can confirm that downloading the Eclipse installer from the main website: http://www.eclipse.org/downloads/ executing it as myself and then selecting the C/C++ option got me a working copy of Eclipse installed.  That is a successful work around until the packaged version is fixed.
1784369,2018-07-30 11:42:34 UTC,If i run same command on CLI i got following
1784369,2018-07-31 16:29:11 UTC,Adding retries would be a good solution.
1784369,2018-07-31 17:45:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/587563"
1784369,2018-08-01 21:40:17 UTC,"Reviewed:  https://review.openstack.org/587563
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=122b75b033f89d15fef0620002223707a3f98c3d
Submitter: Zuul
Branch:    stable/queens"
1784369,2018-08-08 21:38:38 UTC,This issue was fixed in the openstack/openstack-ansible 17.0.8 release.
1784372,2018-07-30 11:48:01 UTC,Note I was instructed to setup some sysctl tweaks for this information as noted in
1784381,2018-07-30 12:33:02 UTC,$uname -a
1784384,2019-10-09 20:45:29 UTC,"This is a known issue, and we hope to fix this as part of some upcoming work surrounding services in snapd. See https://forum.snapcraft.io/t/how-to-manage-services-with-sockets-timers/7904/8?u=ijohnson for a current status around these efforts."
1784399,2018-08-23 20:58:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784399,2018-08-23 21:00:14 UTC,"$ sudo apt-get install freeipa-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
freeipa-client is already the newest version (4.3.1-0ubuntu1).
The following package was automatically installed and is no longer required:
  snap-confine
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up freeipa-client (4.3.1-0ubuntu1) ...
dpkg: error processing package freeipa-client (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 freeipa-client
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB"
1784403,2020-09-03 14:45:41 UTC,"I made a clean install Ubuntu 20.04. I upgraded ram to 8 gb. Nvidia is working well on performance mode, but not on ""demand"". My hardware is a a 610m, 1Gb. I have problems in Nvidia also in other distros. We can close this bug and stick to new ones?"
1784403,2018-08-10 15:52:19 UTC,"Rolled back from 390 to 340 to try to see if after suspension, system always crashes graphics making a reboot to recover always, a pain. I am in Xubuntu. Should i try to report the bug on 390? Thanks!"
1784403,2018-08-05 20:26:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784404,2018-08-01 07:00:27 UTC,We have many PCs with Ubuntu 16.04. Yesterday (31.08.2018) after update on some PCs we have this bug.
1784404,2018-08-01 07:02:52 UTC,We have many PCs with Ubuntu 16.04. Yesterday (31 JULY 2018) after update on some PCs we have this bug.
1784404,2018-08-01 15:26:04 UTC,Same problem for me
1784407,2018-07-30 15:28:18 UTC,This is a known issue upstream and is being tracked there.
1784411,2018-07-30 18:26:50 UTC,Please add version information.
1784411,2018-07-30 23:08:07 UTC,"@Nick, I think the submitter meant to load the contents of the library tables in the background possibly in a separate thread which has been discussed in the past.  It's just a low priority."
1784411,2018-07-31 07:19:17 UTC,"Yes, as described by Wayne the idea is to spawn a task to asynchronously load library tables as soon as EESchema starts.
If a user tries to open the ""Choose Symbol"" window before they are loaded then a progress bar shall be shown and the user must wait until it is done."
1784411,2018-08-01 19:48:30 UTC,Maybe a cache of the information kicad is generating would also work. In my machine it takes aprox 30s to load the footprint editor for the first time.
1784414,2019-05-11 11:24:54 UTC,Blocks and other items now use the same shortcut: ctrl-D.
1784418,2018-07-31 04:35:07 UTC,"Unfortunately I'm not familiar with building packages or setup.py. I used ""python3 setup.py --help-commands"" to find that setup.py provides options for building binary distributions, including RPM distributions with the bdist_rpm option."
1784418,2020-08-31 16:48:44 UTC,"This error is fixed with 676; of course, whether it now builds a useful RPM is another matter; I've not tested it!"
1784418,2020-08-31 18:30:11 UTC,"679 builds an RPM successfully. While the package installs, it does not work and as it seems not to specify dependencies:"
1784418,2020-08-31 18:50:49 UTC,"For the dependencies, see debian/control. These will need to be specified in a setup.cfg file. Happy to accept a patch that does that. (No idea why you needed to install those Perl modules; you should need only xdg-utils, and I don't think it depends on any of those!)"
1784418,2020-08-31 19:25:03 UTC,"I did not test installing those packages individually, but installed the full list since the caffeine-indicator package built in the RPM Sphere repo requires them when it is installed: https://rpmsphere.github.io/ I don't know if they are truly needed."
1784418,2020-08-31 19:34:21 UTC,"I'm sorry, I don't use any RPM-based or Fedora-like systems, and I don't really have the bandwidth to help with the details of downstream packaging! You can see what the Python-level deps are; it's up to you to translate those for the system you want to package for. The fact that caffeine includes Debian packaging should make that easier. Closing this bug now, but as I said, very happy to accept a `setup.cfg` file if you come up with one to make life easier for future RPM packagers. Good luck!"
1784418,2020-08-31 20:48:07 UTC,Ok. Thanks for fixing the RPM build failure.
1784418,2018-07-30 22:04:45 UTC,"I don't know much about building RPMs, and last tried nearly fifteen years ago. If there's a problem in caffeine's build system, I'll happily accept patches."
1784419,2019-07-06 07:59:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784425,2019-08-27 20:56:20 UTC,@Jeff
1784425,2019-08-27 20:23:22 UTC,"@Evan, thanks."
1784425,2019-08-27 19:19:12 UTC,@Jeff
1784425,2019-07-08 21:54:52 UTC,"@Evan, yes, sorry for not being specific: I was looking for feedback on MASTER."
1784425,2019-07-08 21:31:54 UTC,@Jeff
1784425,2018-12-14 14:42:52 UTC,This is sufficiently minor that we can wait for v6
1784425,2019-02-07 18:31:51 UTC,Just a quick update to where things stand with the version below.
1784425,2018-09-20 15:09:29 UTC,"In my Ubuntu all the menu are ""tight spaced"", but when I enable the icons"
1784425,2018-09-08 17:32:48 UTC,"Not seeing this issue on Mac or Linux/XFCE, so looks like Window-specific."
1784425,2018-07-30 17:06:23 UTC,"Here is the image. The left image is the vertical spacing seen on all but the one menu I've shown on the right, which is tighter."
1784425,2019-07-08 20:05:37 UTC,"@Evan, are you still seeing this?  There was some work done in this area, but not directly aimed at this bug report."
1784428,2018-10-13 01:13:30 UTC,We get a similar crash but with disk i/o error.
1784431,2018-07-30 18:00:07 UTC,we need to solve it
1784433,2018-08-02 18:48:34 UTC,"You are right. Now it works again with the original URL. Maybe IMDB tried something new and forgot to support the old version? I attached the 503-result page, which I extracted with Griffith. Funny, isn't it?"
1784433,2018-08-02 06:39:14 UTC,"Are you really sure that the URL doesn't work? Perhaps the 503 error was only temporarly.
I tried the following searches and both of them work:
* the original one: https://www.imdb.com/find?s=tt&q=Rocky
* your new version: https://www.imdb.com/find?ref_=nv_sr_fn&q=Rocky
And I tried the griffith plugin (original URL) and it worked too."
1784433,2018-07-30 20:10:36 UTC,"I can confirm that. IMDB sends an error 503. Thats because the URL of the film search page has changed. I will try to provide a patch tomorrow, but meanwhile you can fix this on your own:
Go to the folder, where the program is installed. Then enter into the subfolders lib -> plugins -> movie and open the file PlugInMovieIMDB.py with an editor (notepad, not MS Word, if you happen to use Windows). Search for ""def __init__(self)"". It is at line 247, if you have the current version. Following are some lines, starting with ""#"". The next two lines below are key to the problem and its solution."
1784433,2018-07-30 20:13:27 UTC,"It seems, Launchpad has inserted linebreaks to my long lines. Please note that only the parameters of the ULRs have changed. They both read:
'http://www.imdb.com/find?ref_=nv_sr_fn&q='"
1784433,2018-07-30 20:56:42 UTC,Yeahhh!!! It works like a charm!! Thank you so much for your fast reply!
1784434,2018-07-30 18:05:02 UTC,Blablabla!
1784439,2018-07-30 18:14:07 UTC,that's a serious bug :(
1784446,2018-07-30 18:15:58 UTC,hey
1784447,2018-07-30 18:14:56 UTC,Hard to solve
1784448,2018-07-30 18:06:30 UTC,Super BUGGGGGG
1784448,2019-09-05 17:08:56 UTC,Closing...
1784451,2018-07-30 18:09:55 UTC,Its a bug test!!!
1784452,2018-07-30 18:16:36 UTC,"Hi,
What the hypervisor do you using?"
1784454,2018-11-20 13:42:02 UTC,"I can confirm that I don't see the above issue with systemd-237-3ubuntu10.10 from bionic-proposed.
Adjusting the tags accordingly."
1784454,2019-09-30 19:29:58 UTC,this bug lacks a clear SRU test case for bionic (there is obviously no 4.4 kernel in 18.04).
1784454,2019-09-30 20:33:47 UTC,"Hello Frank, or anyone else affected,"
1784454,2018-11-20 12:06:10 UTC,"Hello Frank, or anyone else affected,"
1784454,2019-10-01 08:37:25 UTC,"Since it was me who initially raised that bug, I feel like I should comment on this."
1784454,2019-10-08 12:00:19 UTC,"@frank-heimes, thank you for the testing and also for your additional comments.
This fix was once accepted to bionic-proposed, while it does not have a test case in the bug description nor the description follows the SRU template: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template .
Ensuring that is the job of the SRU uploader, and the first time is was skipped and I also missed that.
Since the bug did not exist in 18.04 I'm marking it invalid instead of performing the SRU again."
1784454,2019-10-08 12:02:18 UTC,"I also set verification-done, since it is verified that the bug does not occur with .31 ."
1784454,2019-09-30 21:32:07 UTC,a version of systemd with this change was accepted into bionic in error and has now been withdrawn.  a test case is needed here before it's accepted properly.
1784454,2018-11-19 14:04:24 UTC,"Hello Frank, or anyone else affected,"
1784454,2018-07-31 06:30:13 UTC,"I can confirm that the updated installer taken from here:
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-proposed/main/installer-s390x/20101020ubuntu451.26/
now properly works and boots."
1784454,2018-07-31 07:16:21 UTC,"Looks like the fixed installer was already included into the todays ISO:
http://cdimage.ubuntu.com/ubuntu-server/xenial/daily/20180731/xenial-server-s390x.iso
I can confirm that this works, too (adding a 'pass' to the QA tracker)"
1784454,2018-07-30 18:11:55 UTC,"used:
http://cdimage.ubuntu.com/ubuntu-server/xenial/daily/20180730.2/xenial-server-s390x.iso"
1784454,2018-07-30 23:29:14 UTC,This bug was fixed in the package debian-installer - 20101020ubuntu451.26
1784454,2018-07-30 22:40:27 UTC,This bug was fixed in the package systemd - 229-4ubuntu21.4
1784454,2018-07-30 20:14:12 UTC,"Hello Frank, or anyone else affected,"
1784454,2018-07-30 19:53:22 UTC,Same problem installing http://cdimage.ubuntu.com/ubuntu-server/xenial/daily/20180730.2/xenial-server-amd64.iso on Virtualbox VM.
1784454,2018-07-30 19:00:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1784454,2018-07-30 18:29:43 UTC,btw. d-i based on hwe kernel 4.15 (boot-hwe) works fine ...
1784454,2018-07-30 18:19:38 UTC,"13: if [ -f /sys/module/scsi_mod/parameters/scan ]; then
14:    echo sync > /sys/module/scsi_mod/parameters/scan
15: fi"
1784454,2018-07-31 11:53:50 UTC,Thanks for verifying!
1784457,2018-07-30 18:15:34 UTC,happened to me as well... sad times
1784458,2018-07-30 18:28:50 UTC,UAu this is critical! Let's go man!
1784463,2018-07-30 18:29:40 UTC,Test
1784469,2020-03-21 20:36:53 UTC,Closing because CAN'T REPLICATE.
1784473,2020-04-03 04:18:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1784473,2020-02-03 01:38:02 UTC,"Amit,"
1784473,2020-01-31 11:27:43 UTC,"In my case, the error was caused by a full /home filesystem.
I switched to a text terminal (Ctrl Alt F1-7) deleted some files, and after rebooting, it was working."
1784473,2018-07-31 18:55:03 UTC,"After installing upstream kernel the issue is solved though boot time is long.
I get this screen(https://ibb.co/isQYTz) after selecting the kernel from grub, not an issue to me but thought to inform you.
Also can I remove the kernel because had remove virtualbox"
1784473,2018-07-31 17:13:59 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1784473,2018-07-31 07:00:07 UTC,This change was made by a bot.
1784473,2018-07-31 06:15:46 UTC,"""So please check that you are NOT using ""nomodeset"" when you try that""
yes i tried it without nomodeset.
I removed nomodeset yesterday becasue it froze the laptop randomly."
1784473,2018-07-31 06:04:07 UTC,"Saying ""GDM3"" is actually incorrect but we understand what they mean. When someone says that they just mean the login screen never arrives. But problems with the login screen not appearing are generally to do with Mutter which provides the graphics foundation for the login screen and the shell."
1784473,2018-07-31 05:19:15 UTC,apport information
1784473,2018-07-31 05:19:13 UTC,apport information
1784473,2018-07-31 05:19:11 UTC,apport information
1784473,2018-07-31 05:19:02 UTC,apport information
1784473,2018-07-31 05:19:08 UTC,apport information
1784473,2018-07-31 05:19:07 UTC,apport information
1784473,2018-07-31 05:19:06 UTC,apport information
1784473,2018-07-31 05:19:05 UTC,apport information
1784473,2018-07-31 05:19:03 UTC,apport information
1784473,2018-07-31 05:19:01 UTC,apport information
1784473,2018-07-31 05:19:00 UTC,apport information
1784473,2018-07-31 05:18:58 UTC,apport information
1784473,2018-07-31 05:18:57 UTC,apport information
1784473,2018-07-31 05:18:11 UTC,"I think they are not same. In bug https://bugs.launchpad.net/bugs/1782347 the user says he needs to boot with nomodeset for both the installed and liveCD.
I can boot with bootable pendrive just fine without using nomodeset."
1784473,2018-07-31 01:51:17 UTC,I think this might be the same as bug 1782347. What do you think?
1784473,2018-07-31 05:19:10 UTC,apport information
1784474,2020-10-19 12:37:30 UTC,Hello.
1784474,2020-10-10 07:37:47 UTC,This looks like a snapd problem.
1784474,2020-12-19 04:17:18 UTC,[Expired for snapd because there has been no activity for 60 days.]
1784474,2020-08-26 17:30:03 UTC,"Canonical Live Patch Client bug reporting guidelines:
Please include the output from the following commands in your report as plain text."
1784474,2020-02-23 20:51:13 UTC,I get the same error message with 20.04 whenever I try to activate livepatch.
1784474,2020-01-02 01:09:22 UTC,"This is the error I get on 20.04, with focal proposed enabled:"
1784474,2020-10-09 23:14:30 UTC,I'm getting this on Ubuntu 20.04. I'm attaching the screenshot of the error message.
1784480,2018-08-01 11:09:27 UTC,"We probably also need to decorate the cursor with the active tool icon or something similar to make the ""mode"" more obvious."
1784480,2018-08-01 13:23:05 UTC,"I don't know why you'd want to clutter up the cursor and reduce the visibility of what are you are working on, when that information is already prominently displayed on the sidebar and status bar."
1784480,2018-08-01 22:55:20 UTC,"I think I already use this video on a related issue
https://www.youtube.com/watch?v=z_zeXPwK1OU"
1784480,2019-07-01 21:17:12 UTC,"Fixed in revision 9effd24f3a98425c1cb852c790c8ab3cc4031f80
https://git.launchpad.net/kicad/patch/?id=9effd24f3a98425c1cb852c790c8ab3cc4031f80"
1784485,2019-03-13 04:24:19 UTC,So I switched to Linux Kernel 5 since RC-5 and I was switching to the latest version ever since a new one is released. It seems that the 5 branch has fixed the issue for good. I am on 5.0.1 and have no issue with output. *fingers crossed*
1784485,2019-02-26 00:12:15 UTC,"confirmed my sound problem was solved using
-Linux Kernel 4.19.10
on my
-aus zenbook ux533fd
-dual boot windows 10 and ubuntu 16.04"
1784485,2019-02-21 00:11:29 UTC,"Quick question, I have exactly the same problem but with one small difference. I have Asus Q325UA which is pretty much the black version of UX391UA as far as I know. lshw gives out the following information"
1784485,2019-02-08 00:13:33 UTC,"@avreon Keep in mind there is two different fixes to the kernel depending on your hardware :
- Fix for UX333, UX433, UX533 and some others starting from 4.19.10
- Fix for UX391UA and some others starting from kernel 5.0-rc1"
1784485,2019-02-07 21:05:43 UTC,"I have the issue that Maksym is talking about. Indeed using 4.19.18 ""fixed"" the problem but it seems to be fixed somehow randomly. When I restart the laptop and enter my paassword, Linux Mint tries to play an intro chime but it gets cut off at the middle or at the end. I have to restart, login and it may or maynot fix the issue. After few restarts it starts working permanently for the duration of the session but this is not a real solution, isn't it? If someone is aware how to fix this issue please raise your voice!"
1784485,2019-01-08 07:17:16 UTC,Can confirm that installing kernel 5.0-rc1 using UKUU that sound from the speakers and earphones now work on my Zenbook UX391UA.
1784485,2019-02-05 20:52:39 UTC,"Small Update. Yes, sometimes when I work on Windows and reboot to Kubuntu sound card stop working.
When I load back to Windows and next shutdown it. And after that sound card begins work correctly."
1784485,2019-01-24 08:49:31 UTC,@Thales Loiola Raveli
1784485,2019-01-30 22:06:38 UTC,I also want to confirm that the sound has come back when I upgraded the kernel to 4.19.18. I am using Mint 19.1 and by default it didn't work.
1784485,2019-01-27 18:10:09 UTC,I confirm that install 4.19.10 via ukuu worked for me on zenbook ux533FD with windows 10 dual boot!
1784485,2019-03-20 16:20:50 UTC,[Edited] (Didnt find how to edit a post)
1784485,2019-01-24 08:42:38 UTC,"The problem can been solved by updating to the newest 4.19.x kernel. I am a Ubuntu user with Asus UX433FA. After a few testing, I can confirm that newer kernel 4.19.17 currently available in kernel.org is the solution (I tried out 4.19.8 as well but I experienced something else so I decided to use 4.19.17, which, by default, accepts the changes suggested by Jian-Hong)."
1784485,2019-01-21 16:02:57 UTC,I encounter the exact same problems of Thales Loiola Raveli on an ASUS 14 UX433FN with Linux Mint 19.1 Cinnamon.
1784485,2019-01-20 19:13:57 UTC,Confirming that install 4.19.10 via ukuu as mentioned by Craig in comment #78 worked for me on zenbook ux533FD with no windows install.
1784485,2019-01-15 19:07:20 UTC,"Hello guys,"
1784485,2019-01-11 13:18:14 UTC,Confirm solved for kernel 4.20 via Ukuu for Asus Zenbook ux433f
1784485,2019-02-03 17:31:11 UTC,"Hey All. I run into troubles with sound also on my Asus UX331UAL (EG022T) laptop with ALC294 sound card. I run Kubuntu 18.04.
I confirmed that after updating kernel to v4.19.19 Sound works well. Updated only kernel without any patches. Updated using Ukuu app.  And it is not depending form method of shutdown windows OS (shutdown or restart).
Thanks this topic)"
1784485,2019-03-26 22:19:05 UTC,@VanVan
1784485,2019-04-17 10:57:39 UTC,Thank you @Santiago Londoño. I spend a lot of hours trying to fix this problem on my ux533fd. You saved me)
1784485,2019-03-29 02:55:02 UTC,"The Q325UAR is quite different from the UX391UA so as @vanvugt points out, a separate bug report should be opened for that and any model other than the UX391UA, which now has this issue fixed."
1784485,2019-10-21 02:09:05 UTC,"Jonathan,"
1784485,2019-10-18 22:51:48 UTC,"Hi,"
1784485,2019-09-02 15:35:07 UTC,This bug was fixed in the package linux-hwe - 4.15.0-60.67~16.04.1
1784485,2019-09-02 12:26:03 UTC,This bug was fixed in the package linux - 4.15.0-60.67
1784485,2019-08-23 01:42:30 UTC,https://launchpad.net/ubuntu/+source/linux-hwe/4.15.0-59.66~16.04.1
1784485,2019-08-22 16:16:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1784485,2019-08-19 02:05:29 UTC,If the problem has definitely returned after being declared fixed then please create a new bug by running:
1784485,2019-03-29 02:07:19 UTC,"The kernel fix (comment #77) only checks for the laptop model name, not anything else. So it will only work for ""ASUS UX391UA"". If you have a different model of laptop then please open a different bug."
1784485,2019-08-17 15:44:04 UTC,"The bug is back for me with kernel :
Linux version 5.0.0-25-generic (buildd@lgw01-amd64-008) (gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)) #26-Ubuntu SMP Thu Aug 1 12:04:58 UTC 2019"
1784485,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1784485,2019-07-03 11:03:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1784485,2019-07-02 10:30:05 UTC,"The kernel fix is not released to updates, we just have it committed to git."
1784485,2019-05-22 20:11:29 UTC,You might be experiencing an issue caused by the way Windows handles powering off the sound card.  Restarting from Windows yields a non-functioning sound card in Linux.  A full shutdown from Windows and subsequent power-on will allow sound to work in Linux.
1784485,2019-05-22 17:44:44 UTC,"Update: the sound problem on UX430U is intermittent. Sometimes it works, sometimes it is gone. I haven't been able to see a clear pattern so far. This is definitely not a hardware problem since everything works rock solid under Windows (I have a dual boot)."
1784485,2019-05-22 17:30:06 UTC,"I have the same problem on Asus Zenbook UX430U. Upgrading to kernel 4.20.16 using ukuu did not fully solve the problem. It worked after the first boot, but no longer works after restarting."
1784485,2019-04-02 14:47:34 UTC,Thank you @Santiago Londoño your solution worked. Just to add I also had to disable secure boot else it was not booting up.
1784485,2019-08-15 15:27:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1784485,2019-01-07 09:42:00 UTC,Thanks Pawel!
1784485,2018-11-23 00:32:23 UTC,"Guys please keep this ticket for Zenbook S UX391UA nad ALC294.
UX533 is different issue. This not make sense. I've got 3 other Asus laptops, where sound worked perfectly on Linux."
1784485,2018-12-10 01:28:05 UTC,https://www.reddit.com/r/linuxquestions/comments/a4qbid/i_need_to_install_kernel_420rc/ebgtdbv
1784485,2018-11-16 06:28:45 UTC,"Asus UX430U mid-2018 edition.
Dual boot Win10/Ubuntu 18.04 LTS
Audio works fine on Windows both through laptop speakers and 3.5mm jack headphones
When booted in Ubuntu -- no sound on laptop speakers or headphones."
1784485,2018-11-09 15:49:41 UTC,I'm also having an issue with my ux391ua running MATE18.04 with no Windows 10 installed. There is sound output audible with headphones on and volume >100% but it is very distorted and crackly. 18.10 was not helpful and updating kerenel to 19 doesn't change anything.
1784485,2018-10-27 09:11:56 UTC,"I've opened another issue regarding this notebook. It's about overheating. Would be very helpful, if you could share your experience here: https://askubuntu.com/questions/1087672/unusually-hot-asus-ux391ua"
1784485,2018-10-20 19:13:07 UTC,"Still no sound, even on Ubuntu 18.10."
1784485,2018-10-11 15:16:05 UTC,Same problem for me...
1784485,2018-10-11 12:39:29 UTC,Also affected Asus VivoBook R542UF
1784485,2018-10-11 10:25:11 UTC,Also affects me (ASUS Zenbook UX931U)
1784485,2018-11-16 07:41:25 UTC,"hello
I just bought a zenbook asus S UX391UA under windows 10; I installed Ubuntu 18.10 64 bits in dual boot and I have the same problem: no sound (although it works correctly under Windows)"
1784485,2018-10-04 14:38:38 UTC,"Not facing any issues due to heating so far. Primarily using the laptop for coding.
It does occasionally gets heated, but then nothing that causes any problems.
I'll update if I face anything."
1784485,2018-10-03 01:58:34 UTC,Same issue for me. I have Ubuntu 18.04 on Asus UX391UA. No sound either through headphones or speakers.
1784485,2018-10-02 13:42:43 UTC,I am experiencing the same problem running Ubuntu and Windows 10 on the same Zenbook model. Sound working on Windows 10 but not on Ubuntu 18.04. I have not managed to solve the problem.
1784485,2018-09-23 18:25:33 UTC,"This also happens on Manjaro, see https://forum.manjaro.org/t/alc294-analog-audio-card-detected-but-no-sound-internaly-or-headphones/54089/16"
1784485,2018-08-23 15:28:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784485,2018-08-07 00:15:28 UTC,"found this page looking for information for same model laptop running Manjaro, also confirmed sound working on windows 10
found another page for ALC294 codec - https://askubuntu.com/questions/986140/no-sound-output-ubuntu-17-10-asus-zenbook-13
all 3 appear to have common problem caused by windows 10 shutdown"
1784485,2018-07-30 20:54:15 UTC,"According to https://askubuntu.com/questions/1056909/no-sound-on-asus-zenbook-ux391ua-with-hda-intel-pch , another user have the same problem as me."
1784485,2018-12-30 15:22:12 UTC,@sojusnik maybe this will help https://askubuntu.com/questions/1056909/no-sound-on-asus-zenbook-ux391ua-with-hda-intel-pch/1058122
1784485,2018-10-04 13:31:33 UTC,"I even installed Windows on an external drive, because the author of this thread (https://askubuntu.com/questions/986140/no-sound-output-ubuntu-17-10-asus-zenbook-13) assumed that a proper shutdown of Windows could solve this issue for Linux users, but it didn't help either."
1784485,2018-11-16 17:29:48 UTC,"To add to the above: shutting down the laptop and then starting from there in Ubuntu, as suggested in one of the workarounds above, actually made the sound work"
1784485,2018-10-04 13:45:26 UTC,"BTW, can somebody confirm that this ZenBook S UX391UA on Ubuntu 18.04 runs quite hot, even while doing normal ""office stuff""?"
1784485,2018-11-17 05:50:30 UTC,"I have the issue as well. I have a dual boot system with following.
Zenbook UX490UAR
Ubuntu 18.04.1
Windows 10"
1784485,2018-12-10 01:25:54 UTC,I tried installing kernel 4.20-rc5 and sound speakers (built in) still don't work.
1784485,2018-11-16 19:16:00 UTC,@Karen Chaltikian
1784485,2018-12-09 23:41:19 UTC,I'm using Ubuntu 18.04. Does anyone know if its possible to apply this patch? I would need idiot proof instructions.
1784485,2018-12-09 21:15:34 UTC,"Hi,"
1784485,2018-12-06 17:31:23 UTC,"Hello,
sorry for my poor english, I am french."
1784485,2018-12-04 20:11:29 UTC,The only workaround that I have found till now is using a bluetooth headset. It works perfectly well.
1784485,2018-12-02 20:58:00 UTC,I have the same issue on new Asus ZenBook 14 UX433FA (ALC294) on Ubuntu 2018.10 with Realtek ALC294.
1784485,2018-12-01 04:16:07 UTC,"I've tried everything. Nothing works. I originally booted into windows once and then installed linux over it. I did not power off I only did a reboot, some people are saying powering off from windows fixes sound on linux, which makes me think its some bios setting, but I don't see anything for sound settings in bios."
1784485,2018-12-04 20:30:09 UTC,"Yes, I can confirm that bluetooth works well, but I hope we can find a way to use internal sound, it's a good quality speaker for a small laptop :)"
1784485,2018-11-29 06:09:54 UTC,I have the pavucontrol showing audio but no sound is coming out of the spakers.
1784485,2018-11-23 03:27:16 UTC,"Hi Pawel,"
1784485,2018-11-22 22:41:19 UTC,Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852
1784485,2018-11-22 21:18:01 UTC,"Interestingly, if I put the sound device into power save mode and wait a few seconds before playing a sound, I can actually hear it perffectly clearly, but after repeating the playing of the sound a few times, it distorts then disappears:"
1784485,2018-11-21 08:00:24 UTC,Same on Asus Zenbook UX533 with Realtek ALC294. No sound on Kubuntu 18.10 (4.18.0-11-generic) -  speakers or headphones. Dual boot with Windows 10. Windows 10 sounds work fine.
1784485,2018-11-21 04:46:52 UTC,I have same issue on new Asus ZenBook 14 UX433FA (ALC294) on Ubuntu 10.04.1 (NO dual boot).
1784485,2018-11-29 20:17:50 UTC,Same problem with Asus Zenbook UX533FD.
1784485,2018-11-19 06:14:56 UTC,The above procedure does not work on my UX391UA either :(
1784485,2018-11-18 11:19:47 UTC,Can somebody confirm that the above mentioned procedure also works with an UX391UA.
1784488,2019-02-28 08:57:53 UTC,you should file this upstream
1784499,2019-09-20 12:12:24 UTC,zyga well patches are welcome ;-)
1784499,2020-06-23 22:15:25 UTC,"FWIW, I still see this on a fresh Ubuntu 20.04 install. My NFS server is also Ubuntu 20.04."
1784499,2019-09-20 12:13:31 UTC,"With that said, some networking work is being done this cycle and we will try to address this."
1784499,2019-09-20 10:08:34 UTC,I'm marking this bug as a property (good or bad is in the eye of the beholder) of the kernel stack. The snapd project cannot do anything about it.
1784499,2018-10-12 09:02:43 UTC,"AppArmor really should restrict NFS access only via the file-path rules, not via the network rules, since if an application accesses a file via NFS, all related network traffic is initiated and controlled by the kernel (or by kernel helper processes like automount, rpc.gssd and nfsidmap), and not by the application."
1784499,2018-10-12 19:06:05 UTC,See also https://lists.ubuntu.com/archives/apparmor/2018-October/011823.html
1784499,2018-07-30 22:03:10 UTC,I have an additional test case that is perhaps more immediate. Attempting to view a roff file in NFS directly:
1784499,2018-08-19 21:23:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784499,2018-10-12 19:41:23 UTC,Thanks for looking into this Markus. I'm surprised that the kernel pieces needed to make this work as expected have yet to be fully integrated.
1784503,2018-07-30 22:57:24 UTC,"Removing packages from cosmic:
 spyder-unittest 0.3.1-0ubuntu1 in cosmic
  python3-spyder-unittest 0.3.1-0ubuntu1 in cosmic amd64
  python3-spyder-unittest 0.3.1-0ubuntu1 in cosmic arm64
  python3-spyder-unittest 0.3.1-0ubuntu1 in cosmic armhf
  python3-spyder-unittest 0.3.1-0ubuntu1 in cosmic i386
  python3-spyder-unittest 0.3.1-0ubuntu1 in cosmic ppc64el
  python3-spyder-unittest 0.3.1-0ubuntu1 in cosmic s390x
 spyder-line-profiler 0.1.1-1 in cosmic
  python3-spyder-line-profiler 0.1.1-1 in cosmic amd64
  python3-spyder-line-profiler 0.1.1-1 in cosmic arm64
  python3-spyder-line-profiler 0.1.1-1 in cosmic armhf
  python3-spyder-line-profiler 0.1.1-1 in cosmic i386
  python3-spyder-line-profiler 0.1.1-1 in cosmic ppc64el
  python3-spyder-line-profiler 0.1.1-1 in cosmic s390x
Comment: LP: #1784503: spyder not yet ready for Python 3.7 or for new Qt
2 packages successfully removed."
1784516,2018-07-31 08:10:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784528,2018-08-13 18:16:41 UTC,"I ran out of time this weekend while working on an Octavia issue, so will try to reproduce the problem today built using the ""source"" option when building the images."
1784528,2018-08-13 13:10:45 UTC,I tried this using the apache based deployment by DevStack. I am not sure what is different between DevStack apache deployments and kolla ansible deployments.
1784528,2018-08-11 18:46:31 UTC,I will try to rebuild everything from source this weekend and see if the problem still occurs when using the latest Kolla Ansible.
1784528,2018-08-11 16:14:45 UTC,"When debug log is enabled for cinderclient in horizon, I got the following log with horizon Rocky 14.0.0.0rc1."
1784528,2018-07-31 20:17:40 UTC,"In case this was of interest, this is the contents /var/log/kolla/cinder/cinder-api.log file in the cinder_api container.  Looks like it just has some deprecation warnings, but maybe you can see something else that I missed?"
1784528,2018-07-31 19:09:52 UTC,"Images were built with the ""source"" option."
1784528,2018-07-31 07:46:33 UTC,Changes may be related:
1784528,2018-07-31 07:44:08 UTC,"Hi, what image type are you using (source or binary)?
Also please share package list from inside horizon container and cinder-api."
1784528,2018-07-31 20:14:02 UTC,"I set debug to True, re-deployed on fresh VM nodes, and verified that the local_settings file had debug turned on - these are the settings:"
1784532,2018-07-31 07:41:33 UTC,The installation path was recently changed in both kolla and kolla-ansible. Please make sure that both versions are in sync.
1784532,2018-11-27 02:48:49 UTC,"Change abandoned by Qi Peng (<email address hidden>) on branch: master
Review: https://review.openstack.org/587289"
1784535,2019-10-21 13:00:04 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1060.67
1784535,2019-10-21 11:42:56 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1048.48
1784535,2019-10-16 06:51:37 UTC,This bug was fixed in the package linux-kvm - 5.0.0-1020.21
1784535,2019-01-31 14:25:07 UTC,"This also affects linux-kvm for Cosmic, which has the quota modules built in:"
1784535,2019-10-14 11:47:30 UTC,Passed with D-KVM 5.0.0-1020.21
1784535,2018-12-04 08:44:02 UTC,"Quota related failure in ubuntu_ltp_syscall, bug 1797325"
1784535,2019-10-14 12:39:44 UTC,This bug was fixed in the package linux-kvm - 5.3.0-1003.3
1784535,2019-09-24 16:15:53 UTC,disco 5.0.0-1018.19	linux-kvm
1784540,2018-07-31 05:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1784540,2018-07-31 05:49:14 UTC,"Just want to add that after switching to xserver-xorg-video-nouveau (open-source) driver not only did the video driver start behaving as expected the monitor config screen now reports the vendor information for both monitors whereas with the previous kernel/driver config it could only report the vendor info for my Samsung 19"" monitor and not my HP LE1901wm."
1784540,2018-07-31 05:42:27 UTC,apport information
1784540,2018-07-31 05:42:24 UTC,apport information
1784540,2018-07-31 05:42:21 UTC,apport information
1784540,2018-07-31 05:42:20 UTC,apport information
1784540,2018-07-31 05:42:18 UTC,apport information
1784540,2018-07-31 05:42:16 UTC,apport information
1784540,2018-07-31 05:42:14 UTC,apport information
1784540,2018-07-31 05:42:12 UTC,apport information
1784540,2018-07-31 05:42:10 UTC,apport information
1784540,2018-07-31 05:42:08 UTC,apport information
1784540,2018-07-31 05:42:06 UTC,apport information
1784540,2018-07-31 05:42:05 UTC,apport information
1784540,2018-07-31 05:42:15 UTC,apport information
1784553,2018-08-11 17:14:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784560,2019-05-13 08:26:26 UTC,I believe that this was resolved in recent changes to the ceph-fs charm:
1784560,2019-02-20 17:57:59 UTC,"After adding an additional unit of ceph-fs to my model, the keyring on the node did not match what ceph was expecting:"
1784560,2019-02-18 19:45:30 UTC,"We were seeing a similar thing, we got past this by increasing the MTU."
1784579,2018-12-20 11:17:12 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/626550"
1784579,2018-12-20 11:21:14 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/626554"
1784579,2018-12-20 11:27:13 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/626556"
1784579,2019-01-26 12:34:10 UTC,"Reviewed:  https://review.openstack.org/626218
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4827cedbc56033c2ac3caf0d7998fca6aff997d6
Submitter: Zuul
Branch:    stable/queens"
1784579,2019-01-26 12:38:07 UTC,"Reviewed:  https://review.openstack.org/626550
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=79a90d37027b7ca131218e16eaee70d6d5152206
Submitter: Zuul
Branch:    stable/queens"
1784579,2019-01-28 21:30:00 UTC,"Reviewed:  https://review.openstack.org/626361
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=254a19f0d326ae5d3b5890d0d5fc735a771fcc0b
Submitter: Zuul
Branch:    stable/pike"
1784579,2019-03-22 03:48:56 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1784579,2019-03-05 23:57:38 UTC,"Reviewed:  https://review.openstack.org/603844
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=542635034882e1b6897e1935f09d6feb6e77d1ce
Submitter: Zuul
Branch:    master"
1784579,2019-03-24 23:04:42 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1784579,2019-03-26 06:43:36 UTC,"Reviewed:  https://review.openstack.org/626369
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6491167a4249bd6d57b8ba3597c021332ee7420
Submitter: Zuul
Branch:    stable/ocata"
1784579,2019-03-26 06:43:50 UTC,"Reviewed:  https://review.openstack.org/626556
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e61b1d7d72470a95068470d67779e08ececdb2e5
Submitter: Zuul
Branch:    stable/ocata"
1784579,2019-04-26 17:16:21 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1784579,2018-12-19 23:50:05 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626410"
1784579,2019-01-28 21:30:16 UTC,"Reviewed:  https://review.openstack.org/626554
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7b4f5725f821ef89176ef69f036471eaaf8a6201
Submitter: Zuul
Branch:    stable/pike"
1784579,2018-12-19 23:43:52 UTC,"Reviewed:  https://review.openstack.org/626228
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1def76a1c49032d93ab6c7ee61dbbfe8e29cafca
Submitter: Zuul
Branch:    master"
1784579,2018-12-20 04:20:19 UTC,"Reviewed:  https://review.openstack.org/626410
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bc0a5d0355311641daa87b46e311ae101f1817ad
Submitter: Zuul
Branch:    stable/rocky"
1784579,2018-12-19 16:48:18 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/626361"
1784579,2018-07-31 14:53:21 UTC,"Well, clearly at some point vif binding failed and that's why you now have a ""binding_failed"" vif type in the info cache for the instance. Did you check the neutron agent logs on the source and/or dest hosts to see why binding failed, because that's the root issue. I've also seen cases where the vif type is ""unbound"". It seems nova should probably *not* store that ""binding_failed"" vif type in the info cache if there is another value already in the cache, but that might not be trivial to determine based on how the code is structured (we could always store off the vif types in the cache *before* getting the latest information from neutron and then do that comparison afterward and filter out any vif type changes from something like ""ovs"" to ""binding_failed"" since we know that won't work if we try to plug/unplug the vif)."
1784579,2018-07-31 15:10:43 UTC,"@dan
binding failed is an actual semi-valid vif type in neutron
https://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/portbindings.py#L86
i say semi valid as it represent the fact that neutron was not able to find an ml2 capable of configuring the newtorking on the host for that interface."
1784579,2018-07-31 15:24:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587498"
1784579,2018-07-31 15:45:47 UTC,"We don't actually do any port binding on the destination host (in queens) during pre_live_migration, so I'm wondering if the instance info_cache already had the bad ""binding_failed"" vif type in it before you started the live migration, because we don't actually change the ports host_id to the dest host until we get to _post_live_migration, so I'm guessing this instance was already messed up before you attempted to live migrate it. Do you have any other errors in the logs for this instance and/or port *before* the live migration attempt?"
1784579,2018-08-02 09:35:50 UTC,Unfortunately there are no previous errors in the logfile. It looks like something bad happened during the upgrade. Because we had some trouble with our rabbitmq and duplicate messages. So maybe the live migration request has been cached and after fixing the duplicate message problem (we had to reinitialize our rabbitmq cluster) the instance cache info was still wrong (state: migrating to). The only way to solve that errors above (NovaException_Remote: Unsupported VIF type ...) was to remove that wrongly cached port from the instance. With newly created instances there was no problem. What I don't understand is where does this information come from? Because I updated the wrongly cached information in the database with information before the upgrade. And as soon as I started a new action (e.g. reboot) the instance cache information had the state: migrating to. So where does this come from?
1784579,2018-08-22 16:25:19 UTC,"Reviewed:  https://review.openstack.org/587498
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cdf8ba5acb7f65042af9c21fcbe1a126bd857ad0
Submitter: Zuul
Branch:    master"
1784579,2018-08-22 19:05:18 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/595317"
1784579,2018-12-19 17:33:01 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/626369"
1784579,2018-09-24 14:47:09 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1784579,2018-12-19 16:17:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/626228"
1784579,2018-07-31 14:50:32 UTC,"I think you want to get/post neutron logs for this. I think the ""binding failed"" is coming back from neutron and we're naively using that as the vif_type."
1784579,2018-12-19 16:14:20 UTC,"After discussions with mriedem on IRC, it's worth noting that the above patch doesn't fix the underlying issue so much as a side-effect of that, namely, the inability of nova-compute to restart after the error has occurred. What is does fix is bug #1738373, which is solely focused on that side effect. That bug has now been marked as a duplicate of this one."
1784579,2018-09-19 03:32:46 UTC,"Reviewed:  https://review.openstack.org/595317
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a890e3d624a84d8eb0306fab580e2cec33e26bc3
Submitter: Zuul
Branch:    stable/rocky"
1784579,2018-12-19 16:06:11 UTC,The regression goes back to newton: https://review.openstack.org/#/c/350595/
1784579,2018-12-19 16:12:48 UTC,"Note that https://review.openstack.org/#/c/587498/ sort of incorrectly says it fixes this bug, which it doesn't really, it fixes a symptom of this bug which is that after the failed port binding during live migration, restarting the source compute fails (it's more aligned bug 1738373)."
1784579,2018-12-19 15:34:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/626218"
1784580,2018-07-31 17:50:23 UTC,"I have figured out the culprit:
The ""Screen reader"" accessibility setting was turned on for some reason, and if I turn it off, this problem goes away. Steps to reproduce this problem:"
1784580,2018-07-31 08:49:49 UTC,"I cannot type messages in evolution since the very latest update. Other fields work but trying to type in the main email box doesn't work. When trying to type for a minute, the window goes blank and shows an error bar with ""Something has gone wrong with typing the message"". I get a bug report popup about something having gone wrong with webkitgtk. I sent the report about it, but I'm not sure how to access that.
I have these versions of webkit stuff:"
1784580,2018-07-31 17:46:33 UTC,"The freeze / inability to type seems to occur only after selecting a bit of text with the mouse, then typing to replace that text. After a while if I persist trying to type, the window goes blank as shown in the attached screenshot."
1784582,2018-08-06 20:06:42 UTC,"Hi Valtteri,"
1784585,2018-07-31 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1784585,2018-07-31 10:35:18 UTC,"Log file is a text file, great fight with linux and iPad to get this far:("
1784585,2018-07-31 17:44:13 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1784585,2018-07-31 20:12:42 UTC,"Hi,"
1784585,2018-08-09 18:55:26 UTC,"Hi,"
1784585,2018-08-10 13:39:12 UTC,"Hi,"
1784585,2018-12-12 03:13:38 UTC,Sorry for the late reply. Does this also happen to Disco (19.04) daily image?
1784585,2018-08-03 11:06:27 UTC,Looks like it's i386 instead of AMD64?
1784587,2018-07-31 09:33:04 UTC,"Unfortunately we don't currently store that information, so heuristics are the best we can do."
1784598,2018-08-29 15:51:12 UTC,"To be fair, systemd does not ship the fallback file, the Nvidia package does."
1784598,2018-08-29 16:55:50 UTC,"That is correct. However, systemd still facilitates loading a kernel module which is clearly blacklisted in both kernel boot options and in modprobe.d conf files. It is unwanted behaviour."
1784598,2018-08-29 13:03:26 UTC,Had the same 'experience' with several of our systems this week. What I fail to comprehend is why the <expletive> can this override 'nouveau.blacklist=1' & 'rdblacklist=nouveau' kernel options as well as blacklist statements in modprobe -
1784598,2018-07-31 09:56:01 UTC,"this is on 18.04, nvidia-396, kernel 4.17.11"
1784598,2018-07-31 09:58:52 UTC,I think this service should check if nvidia is wanted with prime-select
1784600,2020-03-19 21:30:30 UTC,Closing because INVALID.
1784603,2019-05-14 07:58:28 UTC,"Model           Controller        Cloud/Region             Version  SLA          Timestamp
designate-bind  icey-serverstack  serverstack/serverstack  2.5.4    unsupported  07:58:09Z"
1784612,2018-08-18 17:18:02 UTC,"transcode now builds, but removal might be the best thing to do
https://bugs.launchpad.net/ubuntu/+source/dvdrip/+bug/1787222"
1784622,2018-07-31 13:20:18 UTC,"Hello,"
1784622,2018-07-31 14:06:02 UTC,Running `pkg-config --cflags gio-unix-2.0` in the package prints the following:
1784622,2018-07-31 18:40:27 UTC,"Hello,
Yes, I may agree with you."
1784622,2018-07-31 19:43:15 UTC,I can later add necessary changes to the source on Launchpad.
1784622,2018-07-31 19:50:20 UTC,"> Looks like some systems prefer gio-unix-2.0 instead of gio-2.0.
"
1784622,2018-07-31 20:32:56 UTC,"Ok, I thought that Unix version of glib bundles all gio, glib, gthread, .."
1784622,2018-07-31 20:49:50 UTC,"Yes, glib package on linux distributions often bundles all the libraries listed, but each library has its own pkg-config module with its set of own compiler flags."
1784623,2018-10-06 10:20:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784633,2018-08-01 20:43:49 UTC,"I did check the shell behavior without the extensions, and it is very similar. The only difference is that natively the workspaces are stacked, so there is no more the issue with the size of the panel, but the one with the border is still there.
I submitted the bug to the shell developers as this address (#457):
https://gitlab.gnome.org/GNOME/gnome-shell/issues/457"
1784633,2018-08-01 01:38:56 UTC,Firstly please check that you are not using any gnome-shell extensions as extensions tend to cause a large number of bugs.
1784648,2019-03-01 11:21:57 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/581012
Reason: life-too-short to chaise this one"
1784654,2018-07-31 16:12:13 UTC,"@Yoshi,"
1784655,2018-07-31 15:30:08 UTC,This change was made by a bot.
1784655,2018-07-31 18:26:30 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1784655,2018-07-31 19:07:45 UTC,After testing the latest upstream kernel the error-output changed a litte bit:
1784655,2019-08-19 12:54:15 UTC,It affects me with the 5.0 kernel.
1784660,2018-08-10 15:48:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/590810"
1784660,2019-12-08 22:06:04 UTC,"Reviewed:  https://review.opendev.org/590810
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_neutron/commit/?id=9b7cab9cf19dcd95690166061192b273814ee3c5
Submitter: Zuul
Branch:    master"
1784663,2018-08-15 00:43:48 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/591872"
1784663,2018-08-16 05:16:14 UTC,"Reviewed:  https://review.openstack.org/591872
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97e7087ac329c5b6fc77ddd76d2007e03866e00f
Submitter: Zuul
Branch:    stable/rocky"
1784663,2018-08-01 22:57:36 UTC,Oh I see:
1784663,2018-08-01 22:56:07 UTC,"I'm confused, if there are gabbi tests testing this, then there is coverage, yeah? I don't think this is really something that tempest would likely need to test if we can just test it in-tree."
1784663,2018-08-14 09:19:28 UTC,"Reviewed:  https://review.openstack.org/590445
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94617a71761710544cf9505ffda5b6403a645a7e
Submitter: Zuul
Branch:    master"
1784665,2018-08-29 18:34:47 UTC,"Thanks for testing.  I was hoping a fix would be in 4.19, but I'll dig some more."
1784665,2018-11-19 20:53:19 UTC,The 4.20 kernel is now available.  Can you give v4.20-rc3 a test:
1784665,2018-11-26 16:37:29 UTC,4.20-rc3 also fails.
1784665,2018-11-26 21:29:44 UTC,"I built a new Bionic test kernel.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1784665"
1784665,2018-11-26 22:51:19 UTC,The 4.15.0-39 kernel FAILs:
1784665,2018-11-27 02:17:49 UTC,Can you confirm that v4.15-rc6 does not exhibit the bug?  That will ensure I'm reviewing the correct commits:
1784665,2018-11-28 02:41:00 UTC,"I also tested v4.15-rc5, which failed with the same stack trace.  Then I returned to 4.14 mainline, and got this one:"
1784665,2018-11-28 03:20:00 UTC,"v4.13 shows the same search_free stack as 4.14, but doesn't appear to be fatal (it doesn't result in a hung process nor a block device that cannot be wiped."
1784665,2019-07-05 08:11:39 UTC,"Possibly a duplicate of bug 1796292, since we've got the same hung task timeout trace in bch_bucket_alloc() with the latest test kernel (4.15.0-55-generic #60+lp796292)."
1784665,2019-08-06 06:55:37 UTC,"SRU pull request sent to the kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-August/102784.html"
1784665,2019-08-15 10:51:41 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1784665,2019-08-15 15:27:34 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1784665,2019-08-15 20:17:00 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1784665,2019-08-20 17:39:59 UTC,I've verified that bionic-proposed linux-virtual kernel succeeds our test-case (curtin-nvme).  I've 50 installs with no issue.
1784665,2019-08-20 19:33:03 UTC,I've also verified Solutions QA tests succeed with the proposed Bionic kernel.
1784665,2019-08-20 21:04:52 UTC,I've verified that disco-proposed linux-virtual kernel succeeds our test-case (curtin-nvme).  I've 50 installs with no issue.
1784665,2019-08-22 18:55:31 UTC,We're still seeing a bcache timeout failure during curtin install 2019-08-22T10:16:40+00:00 spinda
1784665,2019-08-23 00:31:53 UTC,I've adjusted my bionic testing with the simpler configuration.  I cannot reproduce the failure so far.  I'll leave this running over night.
1784665,2019-08-23 00:33:51 UTC,"Also, I had some confusion earlier about what kernel I was testing.  apt-cache policy shows the package version 4.15.0.59.61, however that's the meta package, the actual kernel is the .66 one."
1784665,2019-08-23 00:34:43 UTC,"Finally, I did verify xenial proposed with our original test.  I had over 100 installs with no issue."
1784665,2019-08-23 00:41:39 UTC,@ Ryan we do not test Xenial or Disco
1784665,2019-08-23 14:26:53 UTC,"Overnight testing of the revised deployment configuration has no errors, 200 runs completed."
1784665,2019-08-27 13:15:15 UTC,This bug was fixed in the package linux - 5.2.0-13.14
1784665,2019-09-02 09:17:58 UTC,Marking verification done for Xenial based on comment #57.
1784665,2019-09-02 09:33:49 UTC,"@jason-hobbs, I don't see any kernel error in the log attached to comment #53, so it seems to be a different issue, maybe a performance regression that is causing curtin to timeout. I would keep this bug closed / fixed and open a new one."
1784665,2019-09-02 11:11:09 UTC,This bug was fixed in the package linux - 5.0.0-27.28
1784665,2019-09-02 12:26:03 UTC,This bug was fixed in the package linux - 4.15.0-60.67
1784665,2019-09-02 14:53:44 UTC,This bug was fixed in the package linux - 4.4.0-161.189
1784665,2018-08-29 18:19:23 UTC,"On Wed, Aug 29, 2018 at 12:01 PM Joseph Salisbury
<email address hidden> wrote:

>
> Thanks for digging up this additional information.  I'll investigate
> further.  While I do that, the v4.19-rc1 kernel is now out.  It might be
> worthwhile to give that one a go, and see if the fix was already
> committed to mainline:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/
"
1784665,2018-08-29 16:47:18 UTC,"Thanks for digging up this additional information.  I'll investigate further.  While I do that, the v4.19-rc1 kernel is now out.  It might be worthwhile to give that one a go, and see if the fix was already committed to mainline:"
1784665,2018-11-27 22:07:36 UTC,"It took a while, but v4.15-rc6 fails; so we need to move back a bit."
1784665,2018-08-28 19:30:48 UTC,"It's always been a locking issue, so either misuse (or missing) locks
in the bcache attach/detach path, or generic locking changes to block
layer path I'd think."
1784665,2018-07-31 16:00:08 UTC,This change was made by a bot.
1784665,2018-07-31 19:13:43 UTC,"> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
"
1784665,2018-08-01 15:28:12 UTC,"We've just had a second occurrence of this, same kernel, but with Xenial.  (Xenial HWE Edge kernel 4.15.0-29) with the same scenario, mkfs.ext4 a /dev/bcache0."
1784665,2018-08-01 16:43:27 UTC,It would be great if we can identify a reproducer.  It would make it much easier to track down.
1784665,2018-08-28 20:20:51 UTC,https://www.spinics.net/lists/linux-bcache/msg04869.html
1784665,2018-08-01 17:58:02 UTC,I'll see if I can reproduce on the mainline kernel.
1784665,2018-08-01 18:42:02 UTC,I can recreate on upstream:
1784665,2018-08-09 16:58:52 UTC,Thanks for testing mainline.  We should be able to bisect this down if we confirm it's a regression.
1784665,2018-08-13 16:42:21 UTC,"4.10:
  Status: OK
  Comment: Survived 30 minute loop over recreating with no issues.
4.13:
  Status: OK
  Comment: Survived 30 minute loop over recreating with no issues.
4.15:
  Status: FAIL
  Comment:  triggered within less than a minute of the loop.
  Kernel Trace:"
1784665,2018-08-13 17:01:36 UTC,"To narrow it down further, can you test the following two kernels:"
1784665,2018-08-13 19:08:27 UTC,"4.14 Final:  OK
4.15-rc1:    OK"
1784665,2018-08-14 20:04:09 UTC,I started a kernel bisect between v4.15-rc6 and v4.15-rc7. The kernel bisect will require testing of about 7-10 test kernels.
1784665,2018-08-14 20:55:16 UTC,test kernel 4.15-rc6 up to d8887f1c7289848e74c92bd4322789a9cd7de699 FAILED
1784665,2018-08-14 20:56:18 UTC,test kernel 4.15-rc6 up to d8887f1c7289848e74c92bd4322789a9cd7de699 FAILED
1784665,2018-08-01 17:56:58 UTC,"I think I've got one.  It doesn't always hang the mkfs, but it does wedge bcache in a few ways."
1784665,2018-08-15 20:07:40 UTC,test kernel 4.15-rc1 up to abb62c46d4949d44979fa647740feff3f7538799 FAILED
1784665,2018-08-15 02:04:46 UTC,"I built the next test kernel, up to the following commit:
abb62c46d4949d44979fa647740feff3f7538799"
1784665,2018-08-28 19:29:04 UTC,https://patchwork.kernel.org/patch/10094201/
1784665,2018-08-28 19:02:31 UTC,The bisect reported the following commit as the first bad commit:
1784665,2018-08-28 18:44:11 UTC,FAILED: Kernel 4.15-rc1 up to bc631943faba6fc3f755748091ada31798fb7d50
1784665,2018-08-28 16:50:53 UTC,"I built the next test kernel, up to the following commit:
bc631943faba6fc3f755748091ada31798fb7d50"
1784665,2018-08-28 16:14:35 UTC,PASS: Kernel 4.15-rc1 (bisect6) up to 87eba0716011e528f7841026f2cc65683219d0ad
1784665,2018-07-31 17:38:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1784665,2018-08-27 21:32:31 UTC,PASS: Kernel 4.15-rc1 (bisect5) up to 6b457409169b7686d293b408da0b6446ccb57a76
1784665,2018-08-27 19:48:01 UTC,"I built the next test kernel, up to the following commit:
6b457409169b7686d293b408da0b6446ccb57a76"
1784665,2018-08-27 18:53:44 UTC,FAILED: Kernel 4.15-rc1 up to f48f66a962a54c3d26d688c3df5441c9d1ba8730
1784665,2018-08-22 15:48:39 UTC,"I built the next test kernel, up to the following commit:
f48f66a962a54c3d26d688c3df5441c9d1ba8730"
1784665,2018-08-21 17:11:44 UTC,FAILED: Kernel 4.15-rc1 up to f17b9e764dfcd838dab51572d620a371c05a8e60
1784665,2018-08-21 15:58:30 UTC,"I built the next test kernel, up to the following commit:
f17b9e764dfcd838dab51572d620a371c05a8e60"
1784665,2018-08-28 14:53:23 UTC,"I built the next test kernel, up to the following commit:
87eba0716011e528f7841026f2cc65683219d0ad"
1784670,2018-07-31 17:37:56 UTC,"It's a good thing to have indeed, but not critical. Please don't over-use Critical Importance. As a reminder, Critical is when everything is broken and tripleo can't be deployed."
1784670,2019-02-26 13:46:47 UTC,Is this still an issue?
1784672,2019-02-11 07:48:12 UTC,This is still a problem with 2.5.0
1784672,2019-02-11 04:17:48 UTC,[Expired for juju because there has been no activity for 60 days.]
1784672,2018-12-06 22:38:44 UTC,"@Charles Dunbar (ccdunbar),"
1784672,2018-08-01 14:01:02 UTC,https://pastebin.ubuntu.com/p/tf6ZhWDBnW/ is the output of `juju status --relations`
1784672,2018-07-31 23:12:44 UTC,The other reason for listing seemingly unrelated apps is when they have units on the same machines as the units of the apps that you are interested in.
1784672,2018-08-02 01:28:54 UTC,"@Charles Dunbar (ccdunbar),"
1784672,2018-07-31 22:58:10 UTC,Please also paste the output of 'juju status --relations'. It seems that the additional apps are present in the output as there are relations linking them to the apps you've requested.
1784673,2018-09-15 12:25:01 UTC,Hi. I have the same problem. I'm subscribing to this bug...
1784673,2018-09-15 12:33:50 UTC,My syslog:
1784673,2018-10-01 20:22:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784676,2018-07-31 18:00:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1784676,2018-08-01 08:47:37 UTC,Thank you for performing the test! Looks to me like the default preseed file that's provided in the test case is out of date and missing some presets. Does the same happen when you do the same steps on English?
1784676,2018-08-01 18:49:57 UTC,"No, if I choose English everything proceeds without any interruption until the end of the automated installation."
1784676,2018-08-01 21:23:22 UTC,Not sure what the issue is then - but would appear to not be a testcase bug.
1784676,2018-08-01 21:24:09 UTC,I'll not do anything to Status etc till then - but I have seen it ;)
1784679,2018-07-31 23:55:05 UTC,*** This is an automated message ***
1784686,2018-08-01 21:47:59 UTC,"I don't think people use high contrast mode for part placement that much, I think I have mostly seen people use it for routing. but different people are different."
1784686,2018-08-02 00:22:10 UTC,Hopefully I've correctly added my example image.
1784688,2019-04-08 10:30:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784690,2018-08-01 23:24:35 UTC,"This issue goes back to when you could use guest mode, but guest mode
developed this issue so you have these large number of groups causing this
error message."
1784690,2018-07-31 23:59:58 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1784690,2018-07-31 23:59:41 UTC,It failed to install since there was no available group ID to create:
1784693,2018-08-01 08:10:04 UTC,We should try to support full Unicode if Django allows it.
1784693,2019-09-06 08:16:54 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/286
1784694,2018-07-31 18:18:57 UTC,and here is the pdf file
1784694,2018-08-01 11:50:14 UTC,"- reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- after saving pdf, when I close Inkscape I get the error message:"
1784694,2018-08-01 12:32:03 UTC,"attached is an edited version of the svg file, which appears to export correctly.
could you test this and confirm that it works?"
1784694,2018-08-01 13:44:37 UTC,"Hi Alvin,
Thanks for your help ! Indeed, it seems to work now... But right now I'm using a different computer than the one which I had the issue with. so I'll try again tonight or tomorrow. Just to be sure the issue is solved."
1784694,2018-08-01 14:11:29 UTC,"good to hear. I know that I have heard or seen almost the identical bug report elsewhere, but cannot find the reference at the moment."
1784694,2018-08-01 15:53:17 UTC,"likely a duplicate of Bug 1768444:
https://bugs.launchpad.net/inkscape/+bug/1768444"
1784694,2020-01-10 02:58:18 UTC,"Closing as part of migration to GitLab, let's track the issue in https://gitlab.com/inkscape/inkscape/issues/691 (duplicate to https://bugs.launchpad.net/inkscape/+bug/1768444 mentioned above)."
1784695,2020-06-28 04:17:18 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1784695,2020-04-28 05:28:14 UTC,may u provide the details that how you get the self signed certification.
1784695,2020-04-28 06:09:53 UTC,try to read this https://docs.openstack.org/kolla-ansible/latest/admin/advanced-configuration.html to make sure you've enable kolla_copy_ca_into_containers
1784705,2018-09-26 10:43:45 UTC,This issue was fixed in the openstack/nova 15.1.4 release.
1784705,2018-09-24 14:47:07 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1784705,2018-09-24 14:46:38 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1784705,2018-09-21 00:21:43 UTC,"Reviewed:  https://review.openstack.org/588077
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2f6ea7b871f5273f16921125647bdcd2f4e93c4e
Submitter: Zuul
Branch:    stable/ocata"
1784705,2018-09-19 18:28:46 UTC,"Reviewed:  https://review.openstack.org/588076
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d4179e3e96b3f3820b1055624ca81c441b94332e
Submitter: Zuul
Branch:    stable/ocata"
1784705,2018-08-10 14:40:43 UTC,"Reviewed:  https://review.openstack.org/588037
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e279ac404673784f33610cad55288e2e60649f88
Submitter: Zuul
Branch:    stable/pike"
1784705,2018-08-10 10:30:38 UTC,"Reviewed:  https://review.openstack.org/588036
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dbce613a9aede3fc5463a2d383b355ffb8cda73a
Submitter: Zuul
Branch:    stable/pike"
1784705,2018-08-10 09:52:37 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.
1784705,2018-08-08 03:18:58 UTC,"Reviewed:  https://review.openstack.org/587976
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7d99f5753f992bd4b58b0aaa7f83f71fb044776f
Submitter: Zuul
Branch:    stable/queens"
1784705,2018-08-01 20:42:58 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/588077"
1784705,2018-08-02 02:31:01 UTC,"Reviewed:  https://review.openstack.org/587636
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b5b7d86bb04f92d21cf954cd6b3463c9fcc637e6
Submitter: Zuul
Branch:    master"
1784705,2018-08-08 00:32:29 UTC,"Reviewed:  https://review.openstack.org/587921
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cc8167a1914a70ea7b336856285df2571a754ca0
Submitter: Zuul
Branch:    stable/queens"
1784705,2018-07-31 21:32:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587636"
1784705,2018-08-01 17:18:28 UTC,"Reviewed:  https://review.openstack.org/587614
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fc05626d43571733da0803df0fd9a7c69766b8fd
Submitter: Zuul
Branch:    master"
1784705,2018-08-01 17:23:58 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/587921"
1784705,2018-07-31 20:04:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/587614"
1784705,2018-08-01 19:42:58 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/588036"
1784705,2018-08-01 19:43:15 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/588037"
1784705,2018-08-01 19:00:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/587976"
1784705,2018-08-01 20:42:40 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/588076"
1784712,2019-12-03 19:17:54 UTC,"Change abandoned by Zane Bitter (<email address hidden>) on branch: master
Review: https://review.opendev.org/587619"
1784712,2018-07-31 20:35:14 UTC,Alex has pointed out https://review.openstack.org/#/c/575265/ as the possible root cause
1784712,2018-07-31 20:52:14 UTC,"Related review, add tripleo check job to heat https://review.openstack.org/#/c/587619/"
1784712,2018-07-31 21:04:50 UTC,"The problem is the new requirement, neutron-lib:"
1784712,2018-07-31 21:23:37 UTC,https://review.rdoproject.org/r/#/c/15095/
1784712,2018-08-01 07:04:21 UTC,"Just for record about bug in heat, no ImportError for missing deps: https://storyboard.openstack.org/#!/story/2003196"
1784712,2018-08-01 19:22:10 UTC,https://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-infra/tripleo-ci/master/legacy-periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset017-master/a40de72/logs/undercloud/home/zuul/overcloud_deploy.log.txt.gz
1784714,2019-09-19 17:27:14 UTC,"Reviewed:  https://review.opendev.org/587628
Committed: https://git.openstack.org/cgit/x/python-glareclient/commit/?id=b1364646f78cf9e24ca9f74a7af093d240c094c0
Submitter: Zuul
Branch:    master"
1784714,2018-07-31 21:22:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587628"
1784715,2018-08-01 22:18:37 UTC,"Yup, dead link, thanks!"
1784715,2018-08-01 22:22:17 UTC,This was the doc in the user-guide in ocata:
1784715,2018-08-01 22:53:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588097"
1784715,2018-08-02 19:04:11 UTC,"Reviewed:  https://review.openstack.org/588097
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3cd5198d5a767566e3cbba5a33ac4a7ae3d53aef
Submitter: Zuul
Branch:    master"
1784715,2018-08-10 09:52:34 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.
1784717,2020-08-09 23:37:42 UTC,pdfsam-basic 3.3.6-1
1784753,2020-10-30 06:55:49 UTC,"Reviewed:  https://review.opendev.org/755894
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=b05ad82959f41c5831ca7765e0b36594d6e2bf23
Submitter: Zuul
Branch:    master"
1784753,2018-10-31 07:58:46 UTC,"Reviewed:  https://review.openstack.org/614018
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=06cf5d298fb6b103899aa358e1cb4b828f502dc5
Submitter: Zuul
Branch:    master"
1784753,2018-07-31 23:24:33 UTC,"There is also nice and ionice features or rather the
'nice_priority, ionice_priority and ionice_class. For completion of options
of how much they hog resources.. tho I guess in this case it's how well
they share."
1784757,2020-10-29 23:42:31 UTC,"The verification of the Stable Release Update for rabbitmq-server has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1784757,2020-10-29 23:42:27 UTC,This bug was fixed in the package rabbitmq-server - 3.6.10-1ubuntu0.4
1784757,2020-10-29 19:25:50 UTC,"First, verifying that the current package fails:"
1784757,2020-10-28 19:29:28 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1784757,2020-07-28 20:32:45 UTC,"Hello Ivan, or anyone else affected,"
1784757,2020-07-07 14:30:33 UTC,"On Tuesday, July 07 2020, Dan Streetman wrote:"
1784757,2020-07-07 12:35:57 UTC,"adding @nicolasbock and @mruffell for their awareness, as rabbitmq-server is in x/b/f-proposed for bug 1874075 currently; hopefully that bug can be verified this week so it can be released at the 7-day aging period next monday, to clear the way for this one (normally i'd suggest just re-uploading with the fixes for this to release them together, but bug 1874075 has been going for a while so it should probably go out asap)"
1784757,2020-07-03 16:16:28 UTC,"I was able to reproduce this bug when using a bionic VM.  I didn't have to go through all the steps from comment #13, but I also noticed that the bug doesn't manifest all the time; sometimes, a ""systemct restart rabbitmq-server"" will take just 1 or 2 seconds.  However, I was able to reproduce the issue in one out of every two attempts.  I'm preparing the fix now."
1784757,2020-07-02 23:14:00 UTC,I'm looking at this bug now.
1784757,2019-07-19 17:39:36 UTC,"# forgot to include the shutdown changes, so here's a full procedure to fix this in Bionic:"
1784757,2019-07-19 17:12:47 UTC,"# my method to fix the problem in Bionic for now is simple, borrowing from the upstream Debian patch:"
1784757,2019-05-09 16:40:53 UTC,"I can confirm this issue on the latest versions of 18.04.2, somewhat nasty, really slows down reboots when RabbitMQ is installed. Here's reproduce steps to see the bug in action:"
1784757,2019-07-09 01:35:34 UTC,I'm still not able to reproduce the error.
1784757,2019-06-09 20:42:04 UTC,"Alex, thanks for looking up the Debian upstream situation, this is looking a lot more actionable so am re-adding it to server-next."
1784757,2019-06-08 15:13:32 UTC,Fixes in Debian packaging which also address the problem:
1784757,2019-06-08 07:09:22 UTC,"I'm not sure why I did not mention originally, sorry for that, but there is a chance that what makes it reproducible is starting the daemon inside the lxd/lxc"
1784757,2019-06-07 23:43:11 UTC,"Like Christian, I also am seeing only a 1 second stop.  I tried a few different things but couldn't reproduce the delay."
1784757,2019-05-10 07:22:12 UTC,"Hmm, the same took 1 second for me."
1784757,2018-10-15 14:18:42 UTC,"Thanks for the update Alex.
In general the package seems rather different than upstream in terms of systemd integration.
We will have to take a wider look at this than just this line."
1784757,2018-10-13 20:19:27 UTC,"The attachment ""rabbitmq-stop-shutdown.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1784757,2018-10-13 16:34:32 UTC,The rabbitmq-server-release GitHub repo has a systemd file which uses shutdown instead of stop:
1784757,2018-10-02 04:17:33 UTC,[Expired for rabbitmq-server (Ubuntu) because there has been no activity for 60 days.]
1784757,2018-08-02 12:32:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1784757"
1784757,2019-07-19 16:57:45 UTC,"# I run into this problem reliably in Bionic following this process, (as of 7/19/2019, this process caused the bug to manifest)"
1784769,2018-09-04 03:39:00 UTC,"Change abandoned by Zhenyu Zheng (<email address hidden>) on branch: master
Review: https://review.openstack.org/587704"
1784769,2018-08-01 07:22:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587704"
1784774,2018-09-24 21:44:59 UTC,"I created a patch to workaround this problem: https://github.com/bryant1410/snapd/commit/a9831da29aba7a4905647ff582061ac399a3b240 It's basically hardcoding a value. I'm not sure what the correct behavior should be for all the cases that /home is autofs, or if it should check that /home/user is NFS instead."
1784774,2020-07-08 07:11:16 UTC,Thanks for fixing this! Much appreciated.
1784774,2020-06-29 10:10:40 UTC,This is now fixed by https://github.com/snapcore/snapd/pull/8936
1784774,2018-08-07 23:55:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784774,2019-04-12 22:37:18 UTC,"I'm sorry for not fixing this yet. A few higher priority bugs kept me busy lately. I will look at fixing it next Monday, with a bit of hope it may be easy and I can get it done without shuffling other planned work."
1784774,2019-04-12 21:56:45 UTC,I'd like to confirm Andrew Conway's report. Restarting snapd does not change anything.
1784774,2020-06-29 09:07:13 UTC,With the additional information in https://bugs.launchpad.net/snapd/+bug/1821193 I think we can fix this issue quickly.
1784774,2019-03-21 14:36:49 UTC,"The issue is NFS detection only happens at snapd start, and on boot no NFS shares are mounted yet."
1784774,2019-03-21 14:33:12 UTC,"snapd will not work properly with users' homes that are unavailable if the user is not logged in. As a workaround, schedule refreshes to only happen when all the local users are logged in."
1784774,2019-03-21 14:19:25 UTC,"This is still broken on bionic, AutoFS mounted home directories are not detected"
1784774,2018-10-09 15:35:39 UTC,"With snap and snapd 2.35.2, it seems to be working for me now."
1784774,2019-03-22 00:57:39 UTC,"I just tested restartung snapd while I am logged in via kerberos with an autofs home directlry. It doesn't seem to help. In particular, I tried launching system monitor (which uses snap) unsuccessfully. Using 18.04 with kerberos, and /home/<my-user-name> mounted via autofs."
1784774,2019-12-20 13:00:48 UTC,@zyga any update on this?
1784776,2019-01-15 08:14:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784782,2018-08-01 22:23:00 UTC,based on http://paste.openstack.org/show/727101/ it looks like this works fine on master.
1784782,2018-08-17 05:21:48 UTC,"Unfortunately the patch is not providing the right information because private flavors can be accessed by non-admin users when:
1 - Granted access via ""flavor access"" - see [1]
2 - Policy is changed: ""compute_extension:flavor_access:addTenantAccess"": """""
1784782,2018-08-15 13:34:02 UTC,"Reviewed:  https://review.openstack.org/588092
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eff376b9fc7a6c96ad63c6d9004f902769def01d
Submitter: Zuul
Branch:    master"
1784782,2018-08-02 02:05:20 UTC,Sorry if the description was confusing.
1784782,2018-08-01 22:25:46 UTC,just as extra context  this is the output of the openstack client as an admin
1784782,2018-08-01 22:14:29 UTC,Marked as incomplete since I'm not sure what you're saying is the bug. Please clarify. I'll fix the API reference docs in the meantime.
1784782,2018-08-01 22:01:58 UTC,"Is your bug really about saying that admins shouldn't have to pass is_public=None *by default* and is_public=None should just be the default behavior for admins if the is_public query parameter isn't provided? If so, that's not a bug, and would require a microversion since it's a behavior change to the API."
1784782,2018-08-01 21:59:57 UTC,"> And novaclient just omits the is_public param to GET /flavors. This is the API code:
"
1784782,2018-08-01 21:57:26 UTC,I'm confused by this:
1784782,2018-08-01 06:53:31 UTC,"@mourya007,"
1784782,2018-08-01 05:33:12 UTC,"Hi, I can get the flavor list with --all"
1784782,2018-08-01 22:16:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588092"
1784785,2018-08-01 05:49:29 UTC,"Though perhaps this might help: the end of an strace, clipped after a long run of futex's."
1784791,2018-08-28 18:08:25 UTC,Could you please include the steps to reproduce?
1784791,2018-09-05 04:11:10 UTC,"In a nutshell, I think NetApp Manila drvier should support workgroup authentication without any other security services(LDAP, Active Directory or Kerberos"
1784791,2019-03-22 14:49:12 UTC,Hey Erlon I am wondering if you are still working on this issue?
1784791,2019-04-17 12:42:54 UTC,"Hello Kim,"
1784797,2018-08-01 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1784798,2019-02-05 15:21:34 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/588087"
1784798,2018-08-02 14:05:28 UTC,"Hmm, I thought you said the guest was spawned on the dest host B but then something after that failed. If the spawn() failed but libvirt is reporting that the guest exists on that host, then something is wrong in the libvirt driver and we need to clean that up."
1784798,2018-08-02 01:05:01 UTC,"First time,instance ""vmtest"" evacuated failed on B with libvirt error."
1784798,2018-08-01 21:37:59 UTC,"I'll push up a quick and dirty patch for this to see what it looks like, but it's definitely not as trivial as just destroying the guest because we also have to rollback things like port binding updates and volume attachments, and determine if we're on shared storage or not so that we don't inadvertently destroy the disks which are shared with the source host."
1784798,2018-08-01 21:10:47 UTC,I guess it's possible you could have hit something like bug 1764883 when saving the instance state after spawn() and then we wouldn't cleanup the guest from the hypervisor on the dest host.
1784798,2018-08-01 21:44:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588087"
1784798,2018-08-01 21:08:28 UTC,"Mitaka and Newton are both end of life, but looking at current master (rocky) this is still a problem most likely:"
1784801,2018-08-01 10:58:18 UTC,So I imagine something like
1784801,2018-08-06 14:30:21 UTC,New debdiff with additional upstream patch required to fix build with Qt 5.11
1784803,2020-03-10 06:51:18 UTC,Please add more detail on what exactly breaks and how to reproduce
1784803,2020-03-10 08:11:03 UTC,We have replaced charms with other solution already but here's the fix https://git.launchpad.net/~brism/grafana-charm/commit/?id=40ed5ea081767c1f0f749feb3a7c1c586623ba4d
1784803,2020-03-17 05:22:22 UTC,"I will change this to use API instead of SQL, so the issue will be fixed by the way."
1784817,2018-08-09 14:14:32 UTC,"At least we understand that Xpad does start, but it does not show the pads when hidden in Ubuntu."
1784817,2018-08-09 14:00:18 UTC,It works ! Wow !
1784817,2018-08-09 13:33:34 UTC,I guess I know what is happening.
1784817,2018-08-09 13:22:16 UTC,"Hi Arthur,"
1784817,2018-08-09 10:23:12 UTC,"Hi Arthur,"
1784817,2018-08-09 13:06:09 UTC,"Hi Ludovic,"
1784817,2018-08-07 10:57:37 UTC,"Hi Arthur,"
1784817,2018-08-07 08:27:27 UTC,"Hi Ludovic,"
1784817,2018-08-09 13:07:59 UTC,"Also, can you try and check the following?"
1784817,2018-08-08 13:33:43 UTC,"Hi Ludovic,"
1784834,2018-08-01 09:58:38 UTC,Also seeing this in the machine logs on each server:
1784834,2018-08-06 01:39:09 UTC,With that in mind I'm going to mark incomplete and if we come back from the netplan folks that Juju should be doing something differently we can narrow down and correct the issue on our end.
1784834,2018-08-02 08:20:17 UTC,A lucky run I guess; repeated the test and had two machines exhibit the symptom.
1784834,2018-08-01 16:26:22 UTC,"OK so I tested with a deployment from bionic-proposed, and I've not seen this issue on the first run - will re-validate again in +24hrs"
1784834,2018-08-10 10:54:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1784834,2018-08-01 10:13:34 UTC,"The panics in #4 were addressed before 2.4.1 was released, but later than the accepted release tag.
They will not be present in the 2.4 edge build."
1784834,2018-08-01 10:00:24 UTC,Status output:
1784834,2018-08-01 09:59:52 UTC,The error in #4 is seen across all units AFAICT
1784834,2018-08-01 15:40:27 UTC,"OK so I think I'm seeing something external to Juju causing this, because I switched back to 2.3.8 and saw exactly the same symptoms."
1784838,2019-09-05 12:02:11 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu and Chromium since that time.
1784838,2019-11-05 04:17:39 UTC,[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]
1784841,2018-08-01 17:41:25 UTC,This change is dependent on the new schematic file format which will allow for optional filling and fill color of hierarchical sheets.
1784854,2018-08-01 13:28:05 UTC,_abc__abc_instancecheck_impl() code: https://paste.ubuntu.com/p/x6PyRw4f8p/
1784854,2018-08-01 13:25:02 UTC,backtrace full: https://paste.ubuntu.com/p/Ctf3p7SChz/
1784854,2018-08-01 13:21:58 UTC,Attaching coredump for segfault
1784855,2019-01-30 19:39:49 UTC,The documentation has been updated to reflect what’s possible today. If you believe there are further things that need documentation please file a new butch report.
1784855,2018-08-01 13:30:10 UTC,"Hi Scott,"
1784855,2018-08-01 15:27:16 UTC,"1. To confirm then that the rackd RPC calls cannot travel over TLS?
2. Thanks, I may have misunderstood some automation we have in our deployment setting this up. I thought it was changing the password, but possibly was creating the password.
3. We have it as 444 now (which is why I added it here). Even if the default package install uses something more secure such as 640, I think documentation pointing out that a file has cleartext credentials in it so it should be monitored with ongoing checks is worth while."
1784856,2018-08-01 13:39:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/587822"
1784856,2018-08-09 18:12:49 UTC,This issue was fixed in the openstack/cinder 13.0.0.0rc1 release candidate.
1784856,2018-08-28 10:43:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/597044"
1784856,2018-10-02 18:09:49 UTC,"Reviewed:  https://review.openstack.org/597044
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=ce2509c3dc9bd7613e7d7c5afc4961e3746b2d18
Submitter: Zuul
Branch:    stable/queens"
1784856,2018-10-09 19:53:21 UTC,This issue was fixed in the openstack/cinder 12.0.4 release.
1784860,2018-08-01 13:39:17 UTC,also see https://bugs.launchpad.net/charm-ceph-mon/+bug/1732491
1784860,2018-11-27 23:52:16 UTC,TRIAGE:
1784871,2018-09-11 20:00:00 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/601681"
1784871,2018-09-11 19:35:46 UTC,"Reviewed:  https://review.openstack.org/596879
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=f0cef07bef5ea8ed29179ee3774df5f4a634ba86
Submitter: Zuul
Branch:    stable/queens"
1784871,2018-08-27 19:46:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/596879"
1784871,2018-08-22 19:33:36 UTC,"It requires backporting a config option, which we normally don't want to do, but I think it should be fine to backport to stable branches to address the security concern."
1784871,2018-08-22 20:48:12 UTC,"Just to make sure I understand the proposed backport, will existing deployments need to make any changes to their configuration to mitigate the described vulnerability, or is the configuration option merely going to be for enabling the old insecure mode of operation?"
1784871,2018-08-22 20:40:48 UTC,"I guess since this is already public, now is a great time to get stable branch reviewers to weigh in on that choice and make sure everyone's happy with it."
1784871,2018-09-20 14:18:08 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/604105"
1784871,2018-08-22 21:08:12 UTC,"Yeah, there's been some churn here, so it probably would be good to clarify things."
1784871,2018-09-20 22:10:12 UTC,"Reviewed:  https://review.openstack.org/601681
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=6309c097e653c5f8b40e0602950d0ef54a9efb37
Submitter: Zuul
Branch:    stable/pike"
1784871,2018-10-02 16:01:33 UTC,This issue was fixed in the openstack/cinder 10.0.8 release.
1784871,2018-09-21 16:16:07 UTC,We've now backported the fix for this to all available stable branches. I'm considering this issue complete unless I hear otherwise.
1784871,2018-09-28 16:24:37 UTC,"Fix proposed to branch: driverfixes/newton
Review: https://review.openstack.org/606130"
1784871,2018-08-22 18:54:57 UTC,"Thanks, Sean. If it was only going to be fixed in Rocky then I planned to classify this as a B1 report (vulnerability that can only be fixed in master, security note for stable branches). With stable backports, we can do an advisory instead. I'll skip requesting a CVE from MITRE in this case and just use the one Red Hat already assigned for it."
1784871,2018-10-03 04:35:57 UTC,"Reviewed:  https://review.openstack.org/606130
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=234aab19f1677a337abd4cc37ede5dc5e455f258
Submitter: Zuul
Branch:    driverfixes/newton"
1784871,2018-10-18 19:09:25 UTC,"Please review this OSSA description for accuracy, as I do not have much ScaleIO expertise. I combined both the Thin/Thick volume bugs:"
1784871,2019-02-28 14:31:11 UTC,This issue was fixed in the openstack/cinder 11.2.0 release.
1784871,2019-03-21 17:24:00 UTC,This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.
1784871,2021-01-21 17:15:47 UTC,"As this was fixed in master before the release of Stein, the last affected release was Rocky which has been under ""extended maintenance"" (no longer receiving stable point releases) for nearly a year already. I doubt there's much point in trying to arrange publishing an advisory at this point, so I'm marking our OSSA task won't fix."
1784871,2018-09-21 15:51:57 UTC,"Reviewed:  https://review.openstack.org/604105
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=2dc52153215bb6a37532a959c5c98239be21bb56
Submitter: Zuul
Branch:    stable/ocata"
1784871,2018-08-22 18:33:39 UTC,I realized today that the original fix for this was just added in Rocky. So the multi-patch thing we did to avoid backporting deprecations was not necessary and just added extra work. Sorry for not noticing the full history on this.
1784871,2018-10-09 19:53:34 UTC,This issue was fixed in the openstack/cinder 12.0.4 release.
1784871,2018-08-22 03:46:39 UTC,"Reviewed:  https://review.openstack.org/594556
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b067a847cf2a14d450682d15f9555f0d5e9ca9c2
Submitter: Zuul
Branch:    stable/rocky"
1784871,2018-08-15 14:19:59 UTC,Unfortunately a public patch was pushed by the ScaleIO team to address this bug.  We had been trying to work this through e-mail with the developer but this has now been slipped out of the Private VMT process.
1784871,2018-08-15 14:36:44 UTC,Thanks Jay! It happens. Can you provide a link to the change in review so I can see how thoroughly it discloses the nature of this issue?
1784871,2018-08-15 14:59:40 UTC,Hey Jeremy!  Thanks for responding.  Here is the patch they posted:  https://review.openstack.org/#/c/592001/
1784871,2018-08-15 17:57:05 UTC,"Seeing as how the linked fix directly references this bug report, I'm switching it from Private Security to Public Security now so that we can get everyone on the same page."
1784871,2018-08-01 14:42:45 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1784871,2018-08-17 20:18:49 UTC,"Reviewed:  https://review.openstack.org/592001
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=949cc46e162e00092aa85a7be921649c8dbf2bf8
Submitter: Zuul
Branch:    master"
1784871,2018-08-17 20:50:48 UTC,Are there stable backports in the works yet for https://review.openstack.org/592001 or will fixing there require a different approach?
1784871,2018-08-17 21:04:14 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/593188"
1784871,2018-08-17 21:04:42 UTC,We do need to get this backported yet. I believe we should be able to just backport and not need to modify the approach.
1784871,2018-08-15 18:41:08 UTC,"Jeremy,"
1784871,2018-08-17 21:07:01 UTC,"Jeremy,"
1784871,2018-08-17 21:06:12 UTC,Looks like bug was not automatically updated. Stable/rocky backport proposed with https://review.openstack.org/593188
1784871,2018-08-22 00:48:31 UTC,"Hi Jeremy, yes, the latter since the update for the first bug was incomplete, and this bug is the fix for that. CVE-2017-15139 is for the problem of volumes containing data from previously deleted volumes, both thick and thin. Not sure how you tag that administratively, but I'll add the same note to the first one as well."
1784871,2018-08-21 23:43:14 UTC,Summer: why was a 2017 series CVE number assigned for this issue? It wasn't reported until this month.
1784871,2018-08-21 23:17:22 UTC,"Red Hat has created CVE-2017-15139 for this.
Summer"
1784871,2018-08-22 13:44:56 UTC,This issue was fixed in the openstack/cinder 13.0.0.0rc2 release candidate.
1784871,2018-08-21 21:53:29 UTC,"Reviewed:  https://review.openstack.org/593694
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b54b2de4e9b06467df22bf5a96c3611dd5653ef4
Submitter: Zuul
Branch:    master"
1784871,2018-08-20 16:37:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/593694"
1784871,2018-08-20 15:37:48 UTC,"Reviewed:  https://review.openstack.org/593188
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=3a39d09166bf6d1c7d2bae63caf3e2a954328862
Submitter: Zuul
Branch:    stable/rocky"
1784871,2018-08-21 22:07:47 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/594556"
1784872,2018-08-02 10:11:24 UTC,In my case it's almost surely the group membership issue. I found that online and just rebooted in case there was something else that needed to be brought up properly. Better safe then sorry. At the very least the error message should be better but there should be a way to actually fix this. It's not common to install an app and need to re-login to be able to use it. Makes for quite a strange user experience.
1784872,2018-08-02 10:59:10 UTC,"> It's not common to install an app and need to re-login to be able to use it. Makes for quite a strange user experience.
"
1784872,2018-08-02 10:59:30 UTC,"I wanted to see the effect myself, so I set up a new system and triggered the issue.
Message is:
""
Unable to connect to libvirt qemu:///system."
1784872,2018-08-02 10:59:52 UTC,"I knew this seemed somewhat known to me, it turns out I tried to work on it once already.
But due to translations this would be a (unreasonably) huge Delta for any Distributions to carry.
Just to say instead of:
  Verify that the 'libvirtd' daemon is running.
like:
  Verify that the 'libvirtd' daemon is running - if libvirt was just installed you might miss the group permission and might need to login the session starting this program."
1784872,2018-08-02 10:59:57 UTC,"There are plenty of discussions on the topic in general around all of linux, like:
- https://superuser.com/questions/272061/reload-a-linux-users-group-assignments-without-logging-out
- https://serverfault.com/questions/74934/refresh-supplementary-group-memberships-without-logging-in-again
- https://unix.stackexchange.com/questions/18796/how-to-apply-changes-of-newly-added-user-groups-without-needing-to-reboot"
1784872,2018-08-02 11:17:42 UTC,FYI - polled for experience and opinions on the ML: https://lists.ubuntu.com/archives/ubuntu-devel/2018-August/040408.html
1784872,2018-08-02 09:06:31 UTC,"Hi Pedro,
If you had no libvirt installed at all then your user will - after install - not have the group ""libvirtd"" yet."
1784876,2019-05-07 23:45:30 UTC,"@Chris MacNaughton (chris.macnaughton),"
1784876,2019-05-08 06:52:58 UTC,"The issue with undeletable volumes is an issue in OpenStack policies - when a volume gets stuck (usually in creating, weirdly), then a normal tenant cannot delete their own stuck volume - a cloud admin must delete the volume."
1784876,2019-05-07 14:30:12 UTC,"@anastasia-macmood We will likely retarget our test automation to juju-2.6 soon, but it doesn't sound like Juju's added controller destruction timeouts?"
1784876,2018-08-01 14:34:51 UTC,This is using 2.4.0-xenial-amd64
1784876,2019-05-07 02:28:07 UTC,"@Chris MacNaughton,"
1784878,2018-10-08 07:08:36 UTC,"I only did a quick loot on the ACPI tables, but the brightness control methods looks fine."
1784878,2018-10-08 07:07:18 UTC,Is it possible for you to try latest mainline kernel [1]?
1784878,2018-08-05 23:17:56 UTC,"Tried 'acpi_osi=! acpi_osi=""Windows 2009""' and brightness did not change."
1784878,2018-08-03 06:58:56 UTC,"Maybe try 'acpi_osi=! acpi_osi=""Windows 2009""'."
1784878,2018-08-02 20:22:51 UTC,Tried both nvidia-driver-390 and nvidia-driver-396 (from graphics-drivers PPA).  Neither allow backlight to change upon reboot.
1784878,2018-08-02 02:57:27 UTC,"Can you try this with the proprietary nvidia graphic card driver installed?
Thanks"
1784878,2018-10-09 20:33:47 UTC,"Updated to 4.19-rc7 (uname -r = `4.19.0-041900rc7-generic`) with 'Ubuntu Kernel Update Utility'.  Without any boot parameters, brightness still doesn't function (but UI shows it changing)."
1784878,2018-08-01 15:13:35 UTC,Boot with: video.use_native_backlight=1
1784878,2018-08-01 15:13:05 UTC,Boot with: video.use_bios_initial_backlight=0
1784878,2018-08-01 15:06:54 UTC,Boot with acpi_osi=
1784878,2018-08-01 15:03:55 UTC,Boot with: video.use_bios_initial_backlight=0
1784878,2018-08-01 15:01:41 UTC,echo 8 > /sys/class/backlight/intel_backlight/brightness
1784878,2018-08-01 15:00:10 UTC,This change was made by a bot.
1784878,2018-08-01 15:18:10 UTC,"Since I have both Intel and Nvidia graphics, tried adding /usr/share/X11/xorg.conf.d/80-backlight.conf described in backlight debugging procedure."
1784879,2018-10-15 11:52:57 UTC,"Hi folks,"
1784879,2018-11-05 06:42:00 UTC,Miguel - I and Kobi would be happy to work on the implementation
1784879,2019-02-13 16:11:39 UTC,@Salvatore: Do you still intend to handle this? Otherwise please unassign yourself and let someone else take over.
1784879,2018-10-12 14:09:36 UTC,"@Jens,"
1784879,2019-02-22 10:54:36 UTC,"Hello,"
1784879,2019-06-14 13:30:50 UTC,"Reviewed:  https://review.opendev.org/662405
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=56e0979fdd5d3b11b2c3e37492d76e9726fd747a
Submitter: Zuul
Branch:    master"
1784879,2019-05-31 08:41:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662405"
1784879,2019-05-31 08:51:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662409"
1784879,2019-12-10 14:20:47 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/654008
Reason: replaced by work in 662409"
1784879,2019-12-20 12:31:56 UTC,"Reviewed:  https://review.opendev.org/662409
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=57bc6d167b44b4c898626aad2ad840ed85b7df17
Submitter: Zuul
Branch:    master"
1784879,2020-01-14 14:51:28 UTC,"Patches to neutron-tempest-plugin, SDK and OSC also got merged, so I'd consider this thing finished.
https://review.opendev.org/679833
https://review.opendev.org/680384
https://review.opendev.org/679834"
1784879,2019-03-01 16:27:38 UTC,"I can confirm that removing the check from #20 works for my use case (which is similar to the one brought up in #17), and would suggest that an additional attribute on the Network object (e.g. ""dns_force_entries"", default=False) be created, so that users wishing to use automated DNS publishing are able to do so while keeping the ""old"" behavior as default for backwards compatibility."
1784879,2018-10-12 14:08:49 UTC,This RFE has been approved during today's drivers meeting
1784879,2018-09-28 00:01:16 UTC,I see now Salvatore's point about excessive complexity. So I think we can attempt to move forward with Kobi's original idea of adding dns_publish_fixed_ip attribute at the network level. I'll mark this rfe as triaged and bring it up during the next drivers meeting. Let's see what feedback we get from them
1784879,2018-10-06 05:37:06 UTC,Either per network or subnet sounds reasonable.
1784879,2018-10-08 07:05:31 UTC,Just to make sure that it doesn't get lost in the long history:
1784879,2018-08-03 20:12:33 UTC,"Hi Koby,"
1784879,2018-08-06 12:22:48 UTC,"Use case #3 is for external/provider networks.
Two cases which I suggested are different as:
a) We could expose an overlay network externally via addition to a no-nat Neutron router.
b) It's legit to use FQDNs within projects networks, even with no external access. It's not a classic public cloud use case, yet still legit."
1784879,2018-08-09 11:56:38 UTC,"I think that these are valid use cases, I have another similar one: public IPv6 networks in project networks according to https://cloudbau.github.io/openstack/neutron/networking/ipv6/2017/09/11/neutron-pike-ipv6.html , where users get public IPv6 addresses for their instances and want to have DNS records for these."
1784879,2018-08-23 22:44:17 UTC,"Hi Kobi,"
1784879,2018-08-26 08:21:37 UTC,"Hi Miguel,
Jens' proposal extends mine. Or we can see this as three separate cases if you want (network/subnet/port).
I guess that we could extend each of the above with 'dns_publish_fixed_ip' attribute, which will use the dns_domain and dns_name as you suggested, if both are set."
1784879,2018-09-07 00:52:32 UTC,"The way a see it, if we implemented the 'dns_publish_fixed_ip' at network, subnet and port level, we would enable the each user to select the level of complexity she is willing to handle, so maybe from the UX point of view it won't have a negative impact. Of course, it increases the complexity of implementation."
1784879,2018-10-05 14:13:57 UTC,During the drivers meeting on October 5th we decided to hold a little longer on a decision on this RFE to give opportunity to other stakeholders to provide feedback
1784879,2018-09-07 13:52:14 UTC,Hi Miguel. Thanks for your answer.
1784879,2018-09-28 16:23:43 UTC,"The drivers team discussed this RFE during today's meeting. The consensus was to add dns_publish_fixed_ip at the subnet level. We would like to hear feedback from the submitter and other interested parties over the next few days, so we can retake the discussion in the next meeting. Thanks to everybody for their opinions"
1784879,2018-09-30 06:27:18 UTC,Per subnet would be fine for me.
1784879,2018-08-29 10:52:08 UTC,"It all boils down to granularity indeed. Port-level is the most granular of course.
On the other hand, coarse-grained approaches such as network or subnet maybe provide better UX for common use cases; if one only wants to expose a port in a network maybe this is already covered by the floating IP approach."
1784901,2018-08-01 16:43:27 UTC,Should be a faily simple opportunity to backport tooling-only. The CLI is decoupled from the general behavior of cloud-init on clouds and it'd be nice to have both cloud-init collect-logs as well as cloud-init status on earlier LTS than Xenial.
1784901,2018-08-07 19:10:29 UTC,This changeset is not as low-hanging as I originally expected. Trusty still sits at 0.7.5 which has no cloudinit.cmd module yet which encapsulates the CLI. This makes backporting the CLI a little bit more than a single file backport and a bit more delta for trusty which we may not be super comfortable with.
1784903,2018-08-02 21:19:38 UTC,"In fact, considering how common this issue seems to be, do you think it would make sense to just make all keyboards default to software-generated release events for these keys?"
1784905,2018-08-23 17:16:03 UTC,"Another cert bundle that I have seen with the issue is ""discoverycertbundle.pem"" when trying to enable TLS for contrail-discovery over HAProxy."
1784905,2018-08-28 21:32:34 UTC,"With respect to the keystonecertbundle and apiservercertbundle, all the the contrail configs files accepts cacert and/or cert/key. So user/provisioning tool can populate only the cacert in the config file, so that the bundle created in /tmp will contain only the CA."
1784905,2018-12-07 01:23:20 UTC,"Review in progress for https://review.opencontrail.org/48063
Submitter: Yijie Xiao (<email address hidden>)"
1784905,2018-12-07 01:26:54 UTC,"Review in progress for https://review.opencontrail.org/48064
Submitter: Yijie Xiao (<email address hidden>)"
1784905,2018-12-14 04:33:56 UTC,"Reviewed:  https://review.opencontrail.org/48064
Committed: http://github.com/Juniper/contrail-controller/commit/917330e6273f386bdcebf9e10a90b093b9989c65
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1784905,2018-12-14 04:34:14 UTC,"Reviewed:  https://review.opencontrail.org/48063
Committed: http://github.com/Juniper/contrail-neutron-plugin/commit/a3887726b3ca88c28d646a6c2a3ec9d93b73f290
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1784906,2018-08-01 17:25:46 UTC,This is a known issue upstream and is being tracked there
1784912,2018-09-03 19:04:06 UTC,Looks like aptdaemon is acting up again …
1784919,2020-11-16 19:50:49 UTC,There are currently no plans to implement a GlusterFS fs driver backend for 9pfs in QEMU.
1784919,2020-11-17 09:26:12 UTC,"Ok, then let's mark this ticket as WONTFIX since nobody will be working on it in the near future."
1784922,2018-08-02 00:34:11 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1784932,2019-04-12 13:16:35 UTC,https://review.openstack.org/#/c/640898/ is trying to do something similar.
1784932,2019-08-01 01:23:39 UTC,I copied this report to the storyboard. https://storyboard.openstack.org/#!/story/2006318
1784932,2019-08-01 19:42:03 UTC,"Thanks, closing this to track it in storyboard."
1784936,2018-08-01 21:00:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1784937,2020-10-23 16:03:11 UTC,"Hi.
I think those protocols don't fit for a simple firewall UI as Gufw... :/
Best regards."
1784937,2020-10-23 16:02:31 UTC,"       ufw supports several different protocols. The following are valid in any rule and  enabled
       when the protocol is not specified:"
1784937,2018-08-09 19:53:28 UTC,By the way to be more precise:
1784937,2018-08-09 07:40:51 UTC,@costales why moving to ufw package which already supports the GRE protocol ? ( sudo ufw allow proto gre )
1784937,2018-08-09 11:48:00 UTC,"I agree with Laurent - ufw already supports gre, gufw just needs to bubble that up."
1784938,2018-08-02 10:13:27 UTC,"The timeout for reboot is 10 minutes.
I seems to be reasonable compromise between the two needs:
1) Detecting that compute node couldn't be restarted.
2) Allowing compute node to handle reasonable amount of updates."
1784939,2018-08-07 05:29:52 UTC,"Hi, Slawek just tested on the master branch and it is running successfully."
1784939,2018-08-07 07:43:09 UTC,"Hi Deepak. It's not failing always but using logstash query which I pasted in bug report today I found 79 hits from last 7 days. And it's failing on master, pike, ocata branches (there was no queens failures but maybe it's just this week like that :)"
1784939,2018-08-07 09:40:08 UTC,"Yes, then I think we need more debugging or reproducing this bug to check the validity."
1784948,2018-09-24 23:09:53 UTC,"I think it's easy enough to implement such a feature. Jenkins API calls are done by means of python requests library. It supports uploading files as ""multipart encoding upload"". As far as I know, Jenkins API requires file parameters of job to be uploaded in that way."
1784949,2018-08-08 22:23:51 UTC,"After doing this it fixed issue, It seems this is a bug, playbook should handle this condition and remove cache content if exists. Or make error more descriptive so people understand why its failing."
1784949,2018-08-01 22:28:46 UTC,"TASK [os_nova : Link guestfs into the venv] *****************************************************************************************************************************************
Wednesday 01 August 2018  18:28:33 -0400 (0:00:00.340)       0:01:43.946 ******
failed: [ostack-compute-01] (item={u'state': u'link', u'name': u'/usr/lib/python2.7/dist-packages/libguestfsmod.so'}) => {""changed"": false, ""failed"": true, ""linkfiles"": {""name"": ""/usr/lib/python2.7/dist-packages/libguestfsmod.so"", ""state"": ""link""}, ""msg"": ""Error while linking: [Errno 2] No such file or directory"", ""path"": ""/openstack/venvs/nova-17.0.8/lib/python2.7/libguestfsmod.so"", ""state"": ""absent""}
failed: [ostack-compute-01] (item={u'state': u'link', u'name': u'/usr/lib/python2.7/dist-packages/libguestfsmod.so'}) => {""changed"": false, ""failed"": true, ""linkfiles"": {""name"": ""/usr/lib/python2.7/dist-packages/guestfs.py"", ""state"": ""link""}, ""msg"": ""Error while linking: [Errno 2] No such file or directory"", ""path"": ""/openstack/venvs/nova-17.0.8/lib/python2.7/guestfs.py"", ""state"": ""absent""}"
1784949,2018-08-07 17:00:34 UTC,Can you provide the steps you used in your upgrade process and please look for any failed tasks
1784949,2018-08-07 17:03:58 UTC,Were you following the steps outlined in the Operations Guide for adding Compute Nodes?
1784965,2019-11-15 05:36:59 UTC,Thank you for your bug report. What Ubuntu version do you use? The file opens fine in eog on Ubuntu 19.10
1784965,2020-01-15 04:17:13 UTC,[Expired for eog (Ubuntu) because there has been no activity for 60 days.]
1784976,2019-10-29 04:07:10 UTC,Off by one error reading the date :)
1784976,2019-10-14 08:45:06 UTC,"Well, the bug is from 2018-08, and released-at is from 2019-01..."
1784976,2019-10-10 12:28:12 UTC,"Hm, I think we already do this. Maybe we forgot to let you know? e.g.,
.  ""latest/stable"": {
.    ""revision"": ""25"",
.    ""confinement"": ""strict"",
.    ""version"": ""1.0.2-1"",
.    ""channel"": ""stable"",
.    ""epoch"": {""read"": [0], ""write"": [0]},
.    ""size"": 1204224,
.    ""released-at"": ""2019-04-15T14:21:36.318884Z""
.  }"
1784976,2019-10-13 22:56:27 UTC,"Weird, I do actually have released-at supported in snapd-glib, but I'm guessing for some reason my snapd queries weren't sending this field at the time!? I can't seem to find any snaps not reporting this info so closing this bug."
1784983,2019-11-15 11:48:54 UTC,"Reviewed:  https://review.opendev.org/692185
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=26e1d9c7237f7bd97ec5f1fd3e572b3927eea725
Submitter: Zuul
Branch:    master"
1784983,2019-10-30 16:02:09 UTC,The patch was too broad and was also trying to fix prep_resize failing.
1784983,2019-10-30 16:00:35 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/592252
Reason: This is the wrong fix for rebuild as noted inline, and the resize case is already fixed. I'm going to abandon this since it's had a -1 from a core for a long time and is not being worked on."
1784983,2018-08-21 00:52:49 UTC,"I have committed a patch, please review it. https://review.openstack.org/592252"
1784983,2018-08-16 02:48:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/592252"
1784983,2019-10-30 16:15:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/692185"
1784983,2018-08-06 23:28:36 UTC,"Oh nevermind I see it, the _error_out_instance_on_exception context manager."
1784983,2018-08-06 23:27:50 UTC,"Actually, I don't see anything in the compute manager rebuild_instance method that sets the instance to ERROR state on ComputeResourcesUnavailable, where do you see that happen?"
1784983,2018-08-06 23:25:14 UTC,"> Since it doesn't really tell the user what to wait for or how they can poll the server to make sure the evacuate was a success (you could poll for the instance hostId to change, or poll the os-instance-actions API for the completion event).
"
1784983,2018-08-06 23:24:50 UTC,We likely should also add a section to the evacuate API reference docs about asynchronous post-conditions:
1784983,2018-08-06 23:22:35 UTC,"We'd need to audit the API and conductor code to make sure nothing changes any properties on the instance like during rebuild where the image can change. I know the image can't change for evacuate, but we'd need to look for stuff like that. We put the instance in ERROR state on a failed rebuild because as mentioned, the image could change which would have changed properties on the instance which means it needs to be fixed."
1784983,2018-08-07 00:49:40 UTC,Yes，_error_out_instance_on_exception  will set instance to ERROR state. Maybe we should fix this issue firstly.
1784989,2018-08-03 07:14:11 UTC,"Hi,"
1784989,2018-12-05 20:34:39 UTC,Are there any plans to support arm in the hplip?
1784992,2018-08-06 02:31:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589004"
1784992,2019-06-06 10:52:22 UTC,"Since this is pending from a long time, I am assigning it to myself and proposing a fix."
1784992,2019-06-06 22:14:44 UTC,"Reviewed:  https://review.opendev.org/589004
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=89f8ff449bf0aa9e331c7aa8d26a17292e4e53e7
Submitter: Zuul
Branch:    master"
1784992,2019-09-27 09:03:08 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1784998,2018-08-16 00:15:59 UTC,fokedFromTheLife:
1784998,2018-08-28 07:43:12 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19-rc1 kernel[0]."
1784998,2018-08-15 06:31:22 UTC,1)yes
1784998,2018-08-11 13:54:48 UTC,"so
when i install ubuntu
the touchpad don't work"
1784998,2018-08-11 12:32:59 UTC,"fokedFromTheLife, thank you for reporting this and helping make Ubuntu better. Please answer all of the following:"
1784998,2018-08-11 14:39:37 UTC,fokedFromTheLife:
1784998,2018-08-02 06:30:06 UTC,This change was made by a bot.
1785014,2018-08-02 12:59:41 UTC,"Hi Alvaro,"
1785014,2018-08-03 07:18:57 UTC,"Hi Andres,"
1785014,2019-09-19 12:06:07 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1785025,2018-09-24 16:34:45 UTC,"Reviewed:  https://review.openstack.org/593399
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=180a7611f87df74587b718d81b0726cd077bffcf
Submitter: Zuul
Branch:    master"
1785025,2018-08-02 21:17:58 UTC,"Hi - can you propose a change for this?  I can confirm the nova tree uses ""# mysql"" here."
1785025,2018-08-08 14:05:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589907"
1785025,2018-08-09 09:23:22 UTC,"Reviewed:  https://review.openstack.org/589907
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=59d178c9de6028016053f2a6958372e14ded386a
Submitter: Zuul
Branch:    master"
1785025,2018-08-09 21:53:45 UTC,This issue was fixed in the openstack/neutron 13.0.0.0rc1 release candidate.
1785025,2019-01-07 06:47:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/628878"
1785025,2019-01-07 15:20:43 UTC,"Reviewed:  https://review.openstack.org/628878
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bc29d4843d5d4a69c2b5e92475a805d218a9c55e
Submitter: Zuul
Branch:    master"
1785030,2018-08-13 13:49:32 UTC,"We have discussed setting up self-service transfers, it simply hasn't made to the top of the priority heap yet."
1785031,2018-10-02 16:57:35 UTC,"Reviewed:  https://review.openstack.org/590263
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=064daf9aeb39a7f977de4989ad096821e7830ff6
Submitter: Zuul
Branch:    stable/pike"
1785031,2018-10-04 03:11:42 UTC,"Reviewed:  https://review.openstack.org/590611
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fbc91183ffa32e881ca5cf15758f5f602401acc0
Submitter: Zuul
Branch:    stable/ocata"
1785031,2018-09-24 14:47:01 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1785031,2018-10-08 21:49:05 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1785031,2018-10-08 21:45:38 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1785031,2018-08-10 09:52:25 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.
1785031,2018-08-09 19:37:35 UTC,"Reviewed:  https://review.openstack.org/590262
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0a60496ddbcd3480a342492125c0adcf461324bd
Submitter: Zuul
Branch:    stable/queens"
1785031,2018-08-03 11:01:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588512"
1785031,2018-08-09 11:58:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/590263"
1785031,2018-08-09 11:56:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/590262"
1785031,2018-08-09 11:36:56 UTC,"Reviewed:  https://review.openstack.org/401009
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c7aed3d139909913387e4ac2e771f19c9502c5b1
Submitter: Zuul
Branch:    master"
1785031,2018-08-09 02:45:46 UTC,"Change abandoned by Chen (<email address hidden>) on branch: master
Review: https://review.openstack.org/588512
Reason: duplicate of https://review.openstack.org/#/c/401009/"
1785031,2018-08-08 15:04:09 UTC,This is really a duplicate bug and the original fix is here:
1785031,2018-08-10 03:06:22 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/590611"
1785045,2018-08-02 11:24:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588216"
1785045,2019-05-04 22:54:58 UTC,"Change abandoned by John Fulton (<email address hidden>) on branch: master
Review: https://review.opendev.org/588216
Reason: Abandoning this 9-month old patch. We can restore if we need to."
1785045,2021-02-19 15:52:38 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1785060,2020-10-27 15:38:49 UTC,Solution ;-) at gthe end of https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281?comments=all
1785060,2020-09-24 06:49:06 UTC,apport information
1785060,2020-09-24 06:49:04 UTC,apport information
1785060,2020-09-24 06:49:03 UTC,apport information
1785060,2020-09-25 12:39:53 UTC,This is what I get using the terminal:
1785060,2020-09-24 06:49:01 UTC,"ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-23 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS ""Focal Fossa"" - Release amd64 (20200731)
Package: evince 3.36.7-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=6e215a61-0873-41a1-a75f-cbaf75c331a6 ro quiet splash
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Tags:  focal
Uname: Linux 5.4.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True"
1785060,2020-09-24 06:49:02 UTC,apport information
1785060,2020-07-01 20:29:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:"
1785060,2020-07-01 20:29:47 UTC,Could you also maybe include an example to the bug?
1785060,2020-09-24 06:49:05 UTC,apport information
1785060,2020-08-31 04:17:21 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1785060,2020-09-23 03:56:53 UTC,"""Expired"" is a bad change! With Ubuntu 18.04 I could read any CBR file with Evince. Just installed Ubuntu 20.04 and Evince cannot do it any more!
I have a workaroud, but is this necessary to install Kubuntu's okular? These are quite some packages!
Does ""expired"" mean, I will never be able to read some CBR files with evince?"
1785061,2019-08-14 13:10:13 UTC,"After 82 days of sleeping on it, I feel confident enough.  Pushed to master through rel_3_1.  Thanks again, all!"
1785061,2019-05-24 22:50:37 UTC,"This had some merge conflicts, and I was a little on the fence whether the fixes were trivial or not.  So, here is a rebased branch, but I might decide to go ahead and push it in after sleeping on it:"
1785061,2019-05-22 15:18:28 UTC,I've tested and pushed the patch + a followup to
1785061,2019-05-07 18:26:51 UTC,Here's a branch that fixes this the same general way the XUL code did (with a few small changes):
1785061,2018-10-08 16:03:44 UTC,"Bumping this up to ""High"" - we're still having to go into the XUL client to create these reports."
1785061,2018-08-02 19:02:07 UTC,confirmed
1785061,2018-08-02 14:37:11 UTC,"Ooo, yes.  This is another thing about the wc reporter that is really, really frustrating!!!  I've tried every workaround I could come up with for added punctuation to force the entries to be distinct, but no luck."
1785061,2019-03-12 11:57:57 UTC,Ran into this yet again today.  This makes a lot of reporting impossible to cleanly configure.
1785063,2019-04-22 10:27:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785063,2019-04-22 10:29:03 UTC,Also affects me. I attached the alsa-info.txt created by Alsainfo: https://wiki.ubuntu.com/Audio/AlsaInfo
1785063,2019-11-03 22:01:05 UTC,"Hello, in the expectation that a hacker comes to save us from the claws of MS (which is supposedly loves linux ...), here is the list of what works or not works :"
1785064,2020-08-10 01:25:18 UTC,atom 1.28.1
1785065,2018-08-03 08:21:46 UTC,"Per FHS [1] I think /media is correct.
- /mnt/ : Temporarily mounted filesystems
- /media/ : Mount points for removable media such as CD-ROMs (appeared in FHS-2.3)"
1785065,2018-08-03 15:46:08 UTC,"The pain point is mainly that it confuses the end user. The size of the NBD mount, in my case is typically very close to that of a USB thumb drive. I can of course train my users to ignore it all together but I like to keep it as friendly as possible."
1785073,2018-08-06 14:15:24 UTC,"Now that you've had it working just fine on the same version of Lubuntu it makes me feel like I'm being a pain at this point. Apologies for taking up any more of your time, but although keryx now runs.. I can't read anything."
1785073,2018-08-04 20:42:31 UTC,"Oh, running ./keryx will only work if you're using the 0.92.5 tar.gz or zip. I'm not sure about the Ubuntu zip."
1785073,2018-08-09 17:45:05 UTC,"No bother, Syd! That's what the bug page is for.  :-)"
1785073,2018-08-06 16:05:52 UTC,"@Syd @mac9416 If you both agree, Syd can you share your screen with mac9416? May be with team viewer or Skype or vnc. I am saying this because it might be little difficult for mac9416 to replicate the error because both of you have different environments even if you are using same version of linux. I am not an expert but I thought it might help. May be this may not be possible because you both are in different timezones."
1785073,2018-08-04 11:20:24 UTC,Thanks!
1785073,2018-08-02 15:38:29 UTC,Try using Python 2. I don't believe anyone ever ported this up to Python 3 yet.
1785073,2018-08-03 16:06:35 UTC,Congratulations! :)
1785073,2018-08-02 15:00:56 UTC,"Apologies, forgot to attach picture the first time"
1785073,2018-08-02 15:31:25 UTC,"Apologies again for the repeat posts, just wanted to be more specific:
I was using version ""keryx_0.92.3.2.zip"" when I received this error; I'll try using ""Keryx_Ubuntu_x86.zip"" when I get get home tonight and see if that works."
1785073,2018-08-04 11:20:02 UTC,Just uploading the pictures I forgot the other day in the hope it might shed some light/make your job easier in some way. Thanks again.
1785073,2018-08-03 15:03:15 UTC,"Thanks for giving that a try, Syd. I'll do some debugging tonight and let you know what I come up with. Haven't been able to work on it much lately (just got married), but you seem pretty darn motivated, so I'll dig in and see if we can fix the bug.  :-)"
1785073,2018-08-03 14:22:59 UTC,"I installed python 2 last night and, sadly, still not working :(
Python 2 is set up fine, but I get the same error. I tried the version listed as ubuntu also and got the same/similar error, just with a different \xb number, 6 or 7 IIRC (like a fool I forgot to uplaod the screenshot to my flashdrive...)"
1785075,2018-09-10 18:20:10 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1096.104
1785086,2018-08-06 23:19:56 UTC,"Would be nice to be more specific, rather than a general scrubbing (which is probably harder for someone that's not intimately familiar with rpc in nova, like dansmith). I know you specifically pointed out (in IRC) that there were some issues with the durable queues stuff."
1785086,2018-08-13 20:02:36 UTC,I think there are a bunch of things that are stale.
1785086,2019-06-09 08:11:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/664153"
1785086,2019-06-17 16:35:55 UTC,"speaking about the documentation there are few errors, or let's say imprecisions
https://docs.openstack.org/nova/stein/reference/rpc.html"
1785086,2020-10-28 13:41:06 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/664153"
1785087,2020-07-01 21:23:27 UTC,"Sorry it took so long, but this should be addressed in the latest update (2020.0.0+really93u+20120801-7), binfmt-support is now a suggested dependency."
1785110,2018-08-02 18:14:53 UTC,"v@v-System2:~$ inxi
CPU~Quad core Intel Core i5-3340 (-MCP-) speed/max~1739/3300 MHz Kernel~4.15.0-29-generic x86_64 Up~1:07 Mem~2194.2/7632.9MB HDD~1002.2GB(16.6% used) Procs~217 Client~Shell inxi~2.2.35
v@v-System2:~$ uname -a
Linux v-System2 4.15.0-29-generic #31~16.04.1-Ubuntu SMP Wed Jul 18 08:54:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
v@v-System2:~$ Full upgrade..."
1785116,2018-11-26 14:56:49 UTC,+1
1785117,2018-08-03 08:34:00 UTC,"My point is mainly about polygons and their GUI representation. In case of filled zones, there are probably cases where cutouts can simplify things (zone in a cutout in a zone) and they probably share code so I added them in the issue as well."
1785117,2018-08-03 06:43:24 UTC,"Zones support cutouts (holes).
And because polygons with holes cannot be drawn/plotted,
in Kicad code we frequently convert a polygon with holes to a polygon, and a polygon to a polygon with holes"
1785123,2018-08-06 17:01:32 UTC,I see the StarlingX fix for this here:
1785123,2018-12-03 17:22:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/621646"
1785123,2018-11-13 15:09:26 UTC,"I think it would be strongly related.  I'm not sure if it's a dupe, but the solution should be considered with both in mind."
1785123,2018-08-06 17:28:20 UTC,I'll bet this would also affect a live migrated instance if it was rebooted.
1785123,2018-08-13 20:47:45 UTC,"For a full fix I think you also would need something like https://github.com/starlingx-staging/stx-nova/blob/71acfeae0d1c59fdc77704527d763bd85a276f9a/nova/virt/libvirt/guest.py#L283 in order to keep the nvram around since there are a number of cases where nova is undefining the domain in libvirt but is going to immediately re-create a new domain as the ""same"" instance and it'd be good to preserve the NVRAM."
1785123,2018-11-13 14:03:57 UTC,Is this related to (or even a duplicate of) bug #1633447 (nova stop/start or reboot --hard resets uefi nvram...) ?
1785135,2018-08-03 13:03:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785143,2018-08-02 23:25:39 UTC,"StacktraceTop:
 gtk_drag_finish (context=0x8, success=0, del=0, time=6) at ../../../../gtk/gtkdnd.c:961
 gtk_drag_drop_finished (info=0x560a3ecfbd60, result=result@entry=GTK_DRAG_RESULT_TIMEOUT_EXPIRED, time=<optimized out>) at ../../../../gtk/gtkdnd.c:2593
 gtk_drag_abort_timeout (data=<optimized out>) at ../../../../gtk/gtkdnd.c:3265
 gdk_threads_dispatch (data=0x560a3ea53f20, data@entry=<error reading variable: value has been optimized out>) at ../../../../gdk/gdk.c:755
 g_timeout_dispatch (source=source@entry=0x560a3ecdeac0, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4650"
1785143,2018-08-14 03:18:15 UTC,"Created attachment 7885
terminal output"
1785143,2019-10-05 13:42:01 UTC,"This looks like a copy of the bug #1785143, but it appeared while trying to launch the program originally intended for ubuntu 14.04. The program is: ""prime-indicator_0.1-1+git20150211~webupd8~1_all"". The program itself works correctly, however, when trying to change the graphics card from Intel to nvidia, the above error appears. The error does not directly affect the Ubuntu package, but affects the functioning of the whole.
Interestingly, the program allowed the graphics card to switch correctly, so it works correctly."
1785143,2018-09-26 14:07:49 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1785143,2019-03-25 06:24:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785143,2019-03-25 06:31:15 UTC,Ubuntu-Studio 19.04 QA-Test (live)
1785143,2019-03-25 20:47:50 UTC,I have the same issue on Xubuntu 19.04 Disco Dingo with some development PPAs.
1785143,2019-03-25 20:58:57 UTC,"I'm on Xubuntu 19.04 Disco Dingo now and I still have this issue with Window Manager settings window. It doesn't always crash, but the issue with disappearing buttons when changing the layout is all the time, easy to reproduce."
1785143,2019-03-26 00:28:21 UTC,"I tested today using Xubuntu 19.04 daily (20190325) and could NOT re-create this issue.
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)"
1785143,2019-04-14 19:04:22 UTC,Olivier Fourdan referenced this bugreport in commit 60a8e49c8a63db47b8eb31618e0b6aa5be729a80
1785143,2019-05-10 09:40:10 UTC,Xubuntu 19.10 qa-testing  (2019-05-10 iso date in /etc/apt/sources.list)
1785143,2018-08-14 20:55:38 UTC,"Also, this is my Launchpad bug report related to this issue, maybe it will be useful:
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1785143"
1785156,2018-08-03 06:24:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588447"
1785156,2018-10-19 01:33:13 UTC,"Change abandoned by cheng li (<email address hidden>) on branch: master
Review: https://review.openstack.org/588447
Reason: As we support creating volume from backup, which let us specify the az. So abandon this patch"
1785157,2018-08-03 06:34:58 UTC,why would that be a freeipa bug? reassigning to pyasn1
1785157,2020-03-04 14:12:40 UTC,FreeIPA fixed this issue in https://pagure.io/freeipa/issue/7685. Will this be back-ported to 18.04 because FreeIPA doesn't work without it.
1785171,2019-03-21 09:36:19 UTC,apport information
1785171,2019-03-28 07:18:23 UTC,"Please test this kernel, which disables TSO:
https://people.canonical.com/~khfeng/lp1785171/"
1785171,2019-03-21 09:36:38 UTC,apport information
1785171,2019-03-21 09:36:36 UTC,apport information
1785171,2019-03-21 09:36:34 UTC,apport information
1785171,2019-03-21 09:36:33 UTC,apport information
1785171,2019-03-21 09:36:31 UTC,apport information
1785171,2019-03-21 09:36:30 UTC,apport information
1785171,2019-03-21 09:36:29 UTC,apport information
1785171,2019-03-21 09:36:28 UTC,apport information
1785171,2019-03-21 09:36:27 UTC,apport information
1785171,2019-03-21 09:36:25 UTC,apport information
1785171,2019-03-21 09:36:24 UTC,apport information
1785171,2019-03-21 09:36:22 UTC,apport information
1785171,2019-03-21 09:36:21 UTC,apport information
1785171,2019-04-03 08:26:56 UTC,">I may have stumbled on a workaround for the disconnection issue, though I can't be sure.
> To narrow down the time when the connection stops working, I left a ping to my router running, >every 4 seconds.
> ping -i 4 192.168.1.1 > ping.log
"
1785171,2019-03-21 09:36:17 UTC,apport information
1785171,2019-04-03 08:29:37 UTC,"modinfo e1000e | grep -i version
------"
1785171,2019-04-24 07:43:14 UTC,"Some more information, somewhat related to this bug. I bought a NUC 8i5 with an Intel onboard Ethernet. Installed Ubuntu Server 19.04 on it, and quickly had poor networking speed: ping would rise to 600ms on the LAN (like, on the same switch as my computer) as soon as I tried to install something through apt. Resetting the interface would fix the ping on the LAN for SSH sessions, but as soon as a download would restart, the ping would rise again."
1785171,2020-09-17 20:27:26 UTC,"I just wanted to mention I've been having disconnection issues w/ my i219-LM on both Thinkpad T460s and Dell Precision 7730 laptops in Ubuntu, sometimes disconnecting and reconnecting several times per hour (REALLY irritating)."
1785171,2020-09-10 05:58:21 UTC,I can confirm this problem on the following platforms.
1785171,2020-08-24 06:47:14 UTC,I have been using the latest version (3.8.4) from Intel without issue for about a week.
1785171,2020-08-18 15:34:39 UTC,"FYI, I have been running on the latest version of this driver from Intel without issue for months now. It appears to be resolved in the upstream driver."
1785171,2020-08-17 07:02:48 UTC,"I caveat this comment with an apology for not having any logs to share, but anecdotally, I was having this problem on a Thinkpad T460s, which has an i219-LM nic, running Ubuntu desktop 20.04 LTS.  Wired network would disconnect on average every 20 minutes, sporadically, without warning.  Made Zoom conferences very annoying, as I would drop out without warning, then have to re-login, reconnect to the conference room, and then pick up where we left off.  Internet searches or clicking links would randomly turn up a ""not connected"" error page.  There was no particular pattern I could ascertain as to when/why it would happen, it just did."
1785171,2020-04-07 20:27:49 UTC,FYI in terms of sustainable options I was able to find a very hard to find .deb with the latest driver as a DKMS module. It works fine for me on Ubuntu 19.10. I really wish this was in a repository which was part of universe but I'm never figured out how to do things like that.
1785171,2020-04-07 20:08:46 UTC,FYI a kernel bisection may be outside the skill set of your average user and chances are much lower without detailed instructions. Please don't shoot the messenger.
1785171,2019-07-01 18:01:50 UTC,"Ok, please do a kernel bisection."
1785171,2019-07-01 16:38:43 UTC,Disabling TSO does not resolve the issue.
1785171,2019-06-28 05:53:11 UTC,I am experimenting with disabling tso via ethtool now.
1785171,2019-06-28 05:52:31 UTC,I am seeing this on a  Intel Corporation Ethernet Connection I218-V.
1785171,2019-05-27 08:04:51 UTC,"I was experiencing this on multiple Ubuntu 18.04 servers with high UDP workload, I219-LM Ethernet, 4.15.0-50-generic Ubuntu kernel. Many events with ""Detected Hardware Unit Hang"" ... ""Reset adapter unexpectedly"" per day per server. The workaround suggested by the hosting provider does seem to help, 0 resets seen after disabling TSO & GSO:"
1785171,2019-05-22 12:43:02 UTC,"Kai-Heng,"
1785171,2019-05-15 16:04:19 UTC,"nils,"
1785171,2019-05-06 11:30:20 UTC,I had the same symptoms as in #58 on my Lenovo ThinkCentre M720q but running 18.04.2 desktop.
1785171,2019-04-24 02:57:15 UTC,my comment #37 above is nullified
1785171,2019-03-21 09:36:15 UTC,"ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  gio        1405 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2019-02-14 (35 days ago)
InstallationMedia: Kubuntu 18.10 ""Cosmic Cuttlefish"" - Release amd64 (20181017.2)
MachineType: LENOVO 20LW000XIX
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-16-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.elantech_smbus=0
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-16-generic N/A
 linux-backports-modules-4.18.0-16-generic  N/A
 linux-firmware                             1.175.1
Tags:  cosmic
Uname: Linux 4.18.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/21/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET54W (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LW000XIX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR0QET54W(1.31):bd01/21/2019:svnLENOVO:pn20LW000XIX:pvrThinkPadL580:rvnLENOVO:rn20LW000XIX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L580
dmi.product.name: 20LW000XIX
dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
dmi.product.version: ThinkPad L580
dmi.sys.vendor: LENOVO"
1785171,2019-02-02 12:54:56 UTC,I can confirm the ping latency problem
1785171,2019-03-15 02:36:09 UTC,"I may have stumbled on a workaround for the disconnection issue, though I can't be sure."
1785171,2018-08-27 19:38:02 UTC,Incomplete = reporter needs to give more information ??
1785171,2018-08-27 15:32:44 UTC,"what are the next steps on this bug ticket? It still shows ""incomplete"" status?"
1785171,2018-08-27 01:58:02 UTC,"Here's the syslog from today.  Had another drop network connection episode around around 9:40pm. same behaviour.  Works Ok most of the day, often for a day or two, though the download speed on the speedtests is no where near where it should be (that's my indication that something is not configured right, I've never seen this before).  Upload speed on the speedtests is fine though. I have to disable and then re-enable the ethernet interface to get the internet connection back when I notice there is no connectivity to the internet via a browser."
1785171,2018-08-25 17:34:05 UTC,Here is the syslog file from Aug. 21 the last time the ethernet connectivity on the i219-v onboard NIC disappeared and I had to manually disable and re-enable the network interface.
1785171,2018-08-21 16:38:32 UTC,The loss of the Internet connectivity on Ubuntu Server 18.04- continues to be an issue with the Intel i219-v onboard Ethernet adapter. I just lost the Internet connectivity on the Ubuntu 18.04 server and I was not even doing anything on the server.
1785171,2018-08-09 22:26:22 UTC,"Obviously, there's others having issues with Ubuntu Server 18.04 and their network connectivity."
1785171,2018-08-09 19:53:36 UTC,Thanks for the reply.
1785171,2018-08-07 04:53:30 UTC,"Basically a kernel issue like this requires kernel bisection, which includes testing on different kernel version."
1785171,2018-08-06 17:24:19 UTC,Some more notes on Ubuntu 18.04 and Intel i219-v onboard wired ethernet interface performance.
1785171,2018-08-03 20:23:20 UTC,Maybe this additional information will help:
1785171,2018-08-03 19:45:49 UTC,Thanks for the replies.
1785171,2018-08-03 15:56:50 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1785171,2018-08-03 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1785171,2018-08-03 08:20:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1785171,2019-03-15 04:36:44 UTC,"I faced problems with I219-V too.
I have a dual boot with Windows 10 setup.
was getting 10mb/s Lan Link speed.
The problem is resolved (working for now... I think) am seeing 100mb/s Link speed"
1785171,2018-08-27 19:45:33 UTC,Following up on that previous note about missing log files and asking to grant Launchpad access to our private systems.
1785171,2018-09-08 17:57:57 UTC,?? How do we go about working with someone to get this issue with the Intel i219-v ethernet controller fixed on Ubuntu 18.04? The issue has existing since day one of the install and continues to this day.  Ethernet/Internet connectivity should be 100% staple on any OS.
1785171,2019-01-24 21:53:29 UTC,I just bought Intel NUC8I5BEH and have also really annoying problems with Ethernet Connection (6) I219-V (device id 15be). Tried to install ubuntu 18.04 LTS version which _should_ be compatible with that NIC but immediately couple of seconds after connectinc network cable (or loading kernel module) ping latency starts increase to couple hundreds or thousand ms. Also some packet loss starts to occur. I verified that compiling intel driver and loading that kernel module fixed this ping problem so most propably there is problem in kernel driver which is included in 18.04.
1785171,2018-11-11 00:31:55 UTC,"I eon't have problems with connectivity, but I hqve problems with speed. Iperf3 shows upload speed as normal(940mbps), but download speed is only 750mbps for some reason. I'm running Ubuntu 18.04.1, and Intel I219-V NIC. Please fix!"
1785171,2019-03-05 13:45:32 UTC,I am having similar problems with Dell Optiplex 7060 running Ubuntu 18.04.2. I think the problem is connected with the chipset they are using since other machines are fine.
1785171,2019-02-27 15:42:57 UTC,"Hello,
same issue here on Ubuntu 18.04 with
driver: e1000e
version: 3.2.6-k
firmware-version: 0.5-4
expansion-rom-version:
bus-info: 0000:00:1f.6
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no"
1785171,2019-02-14 16:45:56 UTC,Hello:
1785171,2019-02-11 20:14:49 UTC,"I would like to add that I noticed quite weird connection between this issue and SD card reader in nuc. When the reader was disabled in bios, the issue persists and when it's enabled, the issue does not occur. More info here in the community thread in Intel forum: https://forums.intel.com/s/question/0D50P00004D4D6BSAV/really-weird-problem-in-ethernet-adapter-in-nuc8i5beh-help-needed-in-debugging"
1785171,2019-02-07 06:46:29 UTC,"I can confirm that this bug exists on 18.04 and 18.10 on a Intel NUC 8i3BEH (with latest BIOS, 0056). After a few seconds after boot, the RTT spikes to well over 1s and makes the system unusable."
1785171,2019-02-02 20:31:43 UTC,"i have a dual boot system with win10
disabling all power/ engrgy options in Windows-Driver seems to solve the problem!"
1785171,2018-10-18 16:40:27 UTC,There is a common issue on these I219-V systems which usually manifests when used in a dual-boot scenario with Windows.
1785171,2019-03-14 08:41:53 UTC,"Was able to solve it as well with updated driver from Intel for a ThinkCentre M920x running with dual boot setup with win10:
filename:       /lib/modules/4.15.0-46-generic/updates/drivers/net/ethernet/intel/e1000e/e1000e.ko
version:        3.4.2.1-NAPI
license:        GPL
description:    Intel(R) PRO/1000 Network Driver
author:         Intel Corporation, <email address hidden>"
1785171,2018-12-12 15:48:37 UTC,Some update comments on the issue with the Ubuntu 18.04 network connectivity that started as soon as I installed Ubuntu Server 18.04 with the motherboard using this Intel i219-v network adapter.
1785171,2018-11-16 01:21:02 UTC,"I'm getting this on a desktop with Kubuntu 18.10, though it started on 18.04.  A disconnect using the network applet, wait a few seconds, connect brings it back till the next disconnect.  I put up with it for months assuming it was due to something in the path to my router, but have isolated it back to the desktop.  I""m usually watching YouTube with firefox, but it has happened with ktorrent and zsync.
There's no Windows dual boot.
ethto0l -k shows tcp-segmentation-offload off."
1785171,2018-11-16 05:44:54 UTC,"John,
If possible, please test latest mainline kernel and do kernel bisection so we can find the regression kernel commit."
1785171,2018-11-30 17:38:32 UTC,"I have the same problem on my desktop running Ubuntu 18.04, 18.10 and 19.04 with standard kernel and also in 19.04 with last mainline kernel. I don't have windows on my PC but multi-boot with other Ubuntu partitions.
corrado@corrado-p13-dd-1107-x:~$ inxi -Fx
System:    Host: corrado-p13-dd-1107-x Kernel: 4.20.0-042000rc4-generic x86_64 bits: 64 compiler: gcc
           v: 8.2.0 Desktop: Gnome 3.30.1 Distro: Ubuntu 19.04 (Disco Dingo)
Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: <root required>
           UEFI: American Megatrends v: P1.10 date: 05/11/2017
CPU:       Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9
           L2 cache: 3072 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296
           Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800
Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0
           Display: wayland server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.2.6
           direct render: Yes
Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock Sunrise Point-H
           driver: snd_hda_intel v: kernel bus ID: 00:1f.3
           Sound Server: ALSA v: k4.20.0-042000rc4-generic
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040
           bus ID: 00:1f.6
           IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86
Drives:    Local Storage: total: 931.51 GiB used: 10.12 GiB (1.1%)
           ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
Partition: ID-1: / size: 15.62 GiB used: 10.12 GiB (64.8%) fs: ext4 dev: /dev/sda13
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 31.0 C mobo: N/A
           Fan Speeds (RPM): N/A
Info:      Processes: 211 Uptime: 1h 40m Memory: 7.50 GiB used: 1.36 GiB (18.2%) Init: systemd
           runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 4.4.19 inxi: 3.0.27
corrado@corrado-p13-dd-1107-x:~$"
1785171,2019-01-04 10:13:19 UTC,"I'm getting this on Ubuntu desktop 18.10 at work. It seems to be happening more and more often. Today it's up to 5 times within 2-3 hours. Currently I fix it by disconnecting and reconnecting the ethernet cable after af few seconds.
This is becomming rather painful."
1785171,2018-12-02 19:40:59 UTC,"I cant run 'apport-collect 1785171' because i am not the creator of this bug. If i run ubuntu-bug xxx
what plan I have to put in xxx? Thanks"
1785171,2018-12-03 17:55:46 UTC,added some info about in my bug https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806458
1785171,2018-12-02 13:35:40 UTC,"On my PC in different partitions I have various Ubuntu releases and I can run 'apport-collect 1785171'. In case I have to run it when the connection is dropped?
From a partition with standard kernel? or from the one with last mainline kernel?
thank you."
1785181,2018-08-03 10:51:47 UTC,"i test it also with a puppet-agent in the version 4.10.12, same error."
1785182,2018-08-27 09:49:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785189,2019-04-16 08:47:42 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/596637
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1785189,2019-04-16 08:47:31 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1785189,2019-02-11 14:25:57 UTC,As commented in the patch (https://review.openstack.org/#/c/596637):
1785189,2019-01-21 13:59:48 UTC,This is still seen here: http://logs.openstack.org/41/631441/3/check/tripleo-ci-centos-7-scenario002-standalone/630b4b9/logs/tempest.html.gz
1785189,2018-08-27 04:11:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/596637"
1785189,2018-08-19 06:29:19 UTC,"hi, slawek. To set mtu value to 70kb is enough."
1785189,2019-01-21 14:01:47 UTC,"Uhmm, I'm not sure if what I posted is the same issue, in our case the speed is not being limited."
1785189,2018-08-16 03:07:41 UTC,Here is attachment.
1785189,2018-08-16 03:02:35 UTC,"hi, miguel ,liu yulong. I'm sorry to reopen this bug again.  I have deeply tested it again, when set mtu value to 64kb，The egress bandwidth limit of the VM and the routing gateway will be invalid. Test results are shown in the attachment.
I asked my colleague to read the kernel tc police code and give an explanation. Indeed, if the packet size is greater than the mtu set by the police, it will be dropped in the function tcf_act_police.
......
        if (qdisc_pkt_len(skb) <= police->tcfp_mtu) {
                if (!police->rate_present) {
                        spin_unlock(&police->tcf_lock);
                        return police->tcfp_result;
                }"
1785189,2018-08-07 02:03:02 UTC,"hi, miguel ,liu yulong. I have tested it again. when sets mtu value to 64kb, everything goes well. Thx"
1785189,2018-08-06 18:54:17 UTC,"Hi,"
1785189,2018-08-04 04:27:30 UTC,Marked as invalid because the upstream neutron stable/newton does not support such feature.
1785189,2018-08-17 15:00:16 UTC,"Thanks for detailed report.
So You are suggesting that increase of hardcoded mtu=64kbit for filters in l3_tc_lib: https://github.com/openstack/neutron/blob/master/neutron/agent/linux/l3_tc_lib.py#L120 up to e.g. 80kb should help to solve that issue? Am I understand correct You?"
1785189,2018-08-04 04:26:18 UTC,"Duplicated to the bug:
https://bugs.launchpad.net/neutron/+bug/1777598
Please backport this:
https://review.openstack.org/#/c/576418/"
1785191,2018-09-15 19:00:25 UTC,"@Seth, your correct.  I didn't even notice that but it appears there is more than one issue with unicode characters in kicad2step.  I just spent at least 6 hours over the last two days chasing this down and I have made no progress (see https://trac.wxwidgets.org/ticket/14580#comment:22).  I'm going to throw in the towel and kick this one down the road until we can integrate kicad2step and get rid kicad2step as an external utility."
1785191,2018-09-17 06:29:28 UTC,"@Wayne, is the .kicad_pcb enough or do you need any other files as well?"
1785191,2018-09-18 05:23:06 UTC,You're welcome. Glad that I can contribute a little bit :)
1785191,2018-09-18 12:51:37 UTC,"In fact kicad2step itself has no I18n strings, so no existing translation I am aware of."
1785191,2018-09-18 12:21:43 UTC,"@JP, thanks for ""fixing"" this even though OCE still has it's own issues.  Please apply this change to the 5.0 branch when you get a chance but please use the old error message string so it doesn't break the existing translation.  I'm fine with the error string changes in 5.1 since the translations will need to be updated anyway.  Did you by chance test this on Linux?  I was testing some changes that I made to fix this on Linux and discovered that this is completely broken on Linux as well."
1785191,2018-09-18 13:11:42 UTC,"@JP, your commit fixes the issue with Bob's file but it doesn't resolve the issue for all non ascii characters.  I've attached a file that causes the file existence check on line 243 of kicad2step.cpp to fail so it never gets to the file read code that you fixed.  If you get a chance please take a look at it and see if you can figure out."
1785191,2018-09-19 17:40:40 UTC,@Wayne
1785191,2018-09-15 15:30:25 UTC,"@Wayne-  I don't follow the logic on that.  Bob's error message is ""Error occurred attempting to read in file"", that is the exception thrown by sexp_parser when it can't read data.  This is called by kicadpcb.cpp at line 146, which would indicate that he has successfully tested that the file exists at line 128."
1785191,2018-09-18 08:58:46 UTC,"I leave this as triaged, because when a full filename is not a full ASCII7 string, there are still some issues, especially with opencascade."
1785191,2018-09-15 13:22:26 UTC,I was thinking about this patch
1785191,2018-09-18 08:25:13 UTC,"Fixed in revision 7372acdaa52e3a8722f1791335ffd7ea760301a7
https://git.launchpad.net/kicad/patch/?id=7372acdaa52e3a8722f1791335ffd7ea760301a7"
1785191,2018-09-14 21:41:01 UTC,"Given the error message reported, it looks to me like the issue is not parsing the command line (that would have failed when checking whether the file existed) but rather the .c_str() conversion when parsing in sexpr_parser."
1785191,2018-09-15 12:37:02 UTC,"@Seth, the failure is when checking if the board file name exists.  I created a test app for the wxWidgets devs to use for testing.  It's basically a stripped down version of the kicad2step wxApp object that just parses the string passed on the command line."
1785191,2018-09-12 16:59:25 UTC,I confirmed that any character greater than 255 will cause the source file name to fail.  Fixing this will likely not be trivial since kicad2step is run as an external process and the file name is passed via the command line and kicad2step parses the command line with wxCmdLineParser which hides the command line character parsing in wxAppConsole.  Maybe it's time to move all of this inside kicad proper and get rid of kicad2step as an external utility.
1785191,2018-09-12 17:09:53 UTC,I found that this issue[1] has been fixed in wx 3.1.1 for mingw so I'm guessing that this issue does not exist on Linux and MacOS.  We would have to patch[2] wx 3.0.4 in order to provide a fix until the minimum wx version is set to 3.1.1 which probably wont be any time soon.
1785191,2018-09-12 17:50:09 UTC,"@Wayne, not to beat a dead horse, but..."
1785191,2018-09-12 18:58:52 UTC,"@Jeff, I am painfully aware of the wxWidgets packaging issues.  To be fair to our packagers, this bug fix should have been applied to the 3.0 branch so it would be in 3.0.5 when it becomes available instead of having to use a development version (3.1) of wxwidgets.  I'm not 100% sure how window builds are created but I'm guessing that we are using msys2/mingw(32/64) dependency packages as supplied (that's what use to build kicad on windows) although I could be wrong.  So cloning our kicad/wxwidgets repo would require a significant change in how the windows builders are set up.  The msys2 project already patches wxwidgets 3.0.4 so I guess I could submit this patch (assuming it applies cleanly) to the msys2 project to fix this issue.  I will take a look at that solution over the weekend since I will be hunkered down as hurricane Florence passes by closer than I would like."
1785191,2018-09-17 16:29:26 UTC,"@Bob, thanks for the board file.  That's all I need.  Things really get interesting using your file.  Your board file name gets past the check for the existence of the file which failed for everything I tried so there are two distinct problems here although they appear to be related.  There is a check for the existence of the board file in KICAD2MCAD::OnRun() which passes for your file but fails for all of my attempts which doesn't make any sense.  What makes even less sense is there is a second file existence test in KICADPCB::ReadFile() using the exact same string which is the failure you are seeing.  This one might take a while."
1785191,2018-09-12 20:56:41 UTC,"I would not be hanging around in Wilmington if the track projections are
correct.  I hope you dad makes it out safe and sound."
1785191,2018-09-14 15:02:56 UTC,"I just spent several hours of time that I wish I could get back as neither wxWidgets 3.1.1 or the current head (75225cc1a6) of the master branch fixes this issue so patching 3.0.4 is not going to buy us anything unless we create our own patch.  It looks like the original patch provided to fix this issue was ignored and another solution was implemented by one of the wxWidgets devs which apparently wasn't actually tested.  I will ping the wxWidgets bug tracker and let them know that the issue is not resolved.  If it doesn't get resolved, we may have to fall back to integrating step export without using and external process."
1785191,2018-09-12 19:37:59 UTC,"My dad's in Wilmington NC, so we're keeping our fingers crossed."
1785191,2018-09-14 15:13:21 UTC,"I think cirilo submitred a patch to fox this tp apply to oce, I don't think it is applied in the current windows builds. Maybe I should try to apply that again and retest?"
1785191,2018-09-14 17:17:19 UTC,"@Nick, I think the problem is fairly trivial (famous last words) to fix in that wmain() should be used instead on main() for windows compilers that support wmain().  Unfortunately, the wxWidgets devs have decided that only msvc supports wmain() which is no longer true (I confirmed by using gcc to compile a simple program with wmain() defined for both 32 and 64 bit versions of gcc).  Even worse, they are relying on compiler definitions to determine which compilers support wmain().  This is a flawed design.  The existence of wmain() should be checked by compiling a small source file with wmain() during configuration and setting a definition to tell the source code to use wmain() instead of main().  This would work properly for any windows compiler as well as cross compiling where wmain() is declared.  Given the what I've seen in wxWidgets, I doubt I would waste my time submitting a patch to fix this properly."
1785198,2018-08-03 10:00:07 UTC,This change was made by a bot.
1785198,2018-11-13 11:12:03 UTC,"For AWS T-4.4, the result is a bit different, it's failing with ext2 mkfs."
1785198,2018-11-23 11:23:19 UTC,"This is greatly affecting the test process, as it's causing many false alarms, and the failed test cases number are growing."
1785203,2020-09-05 09:19:25 UTC,"Fixed by 0acd4ab849827bbc20402e01c9da088207c0d236  (""linux-user: check valid address in access_ok()""),  fix released in v5.0.0."
1785204,2018-08-03 10:00:14 UTC,This change was made by a bot.
1785206,2018-08-06 10:26:06 UTC,"Hi, you are using the 1.2 version of Open Rails that is now obsolete, I recommend you download a new version of the simulator, because from the release of version 1.2 to today, some bugs have been fixed and have been added improvements both in the execution of the program and new functions concerning the simulation itself.
First of all, download the updated version of O.R. from the following link:
http://james-ross.co.uk/projects/or/builds/2018-08-04_21-59-07_X4166/Open%20Rails%20X4166%202018-08-04%2021-59-07.zip
once the download is complete, unzip the .zip file to a convenient folder, then copy the contents of the convenient folder to the folder where you have installed OpenRails and answer Yes when you are asked to overwrite the existing files.
Installed the version that I have indicated, I suggest you to automatically perform the update of the program by going to the Options, then select the ""Updates"" tab then choose the ""Test"" option and confirm by clicking OK.
In this way, at the top right, the link to update will be displayed when available. When the link is displayed click on this so Open Rails will be updated automatically. At the time of writing the latest version is: X4166."
1785207,2020-11-20 03:01:04 UTC,still visible on 4.4.0-1082.86 aws
1785207,2018-11-07 10:30:13 UTC,"The result is a bit different on PowerPC and ARM64:
<<<test_start>>>
tag=openat03 stime=1541585769
cmdline=""openat03""
contacts=""""
analysis=exit
<<<test_output>>>
incrementing stop
openat03    1  TBROK  :  openat03.c:59: openat() failed: errno=EINVAL(22): Invalid argument
openat03    2  TBROK  :  openat03.c:59: Remaining cases broken
<<<execution_status>>>
initiation_status=""ok""
duration=0 termination_type=exited termination_id=2 corefile=no
cutime=0 cstime=0
<<<test_end>>>"
1785207,2018-08-03 10:00:19 UTC,This change was made by a bot.
1785207,2019-12-17 21:08:06 UTC,4.15.0-1066.71~14.04.1	linux-azure
1785212,2018-08-15 02:39:03 UTC,"@Chris, we need above test cases to be added into Checkbox (now they are in somerville provider) as Sutton and Stella may need in this cycle as well."
1785212,2020-09-25 07:07:01 UTC,https://git.launchpad.net/plainbox-provider-checkbox/tree/units/dock/test-plan.pxu#n97
1785213,2018-08-08 07:56:26 UTC,Some more details why I want to add something like that below.
1785213,2018-08-23 22:53:03 UTC,"So, at this point, your proposal boils down to implementing the ""external-dhcp"" attribute in networks. Is my understanding correct?"
1785213,2018-08-31 15:01:47 UTC,"Does this assume the external existence of a dhcp_proxy or ""ip helper"" to encapsulate the DHCP broadcast and forward it to an external IP?  Or does it's operation work differently based on network type i.e. provider networks work differently from tenant networks?"
1785213,2018-09-07 11:27:20 UTC,"IIUC, the motivation of the proposal is to let neutron know IP address(es) of DHCP server(s) even if an external DHCP server is used so that iptables rules for DHCP server(s) can be installed automatically."
1785213,2018-09-07 11:28:42 UTC,"The reference link for the last point on IPv6 in my above comment:
https://docs.openstack.org/neutron/latest/admin/config-ipv6.html#ipv6-ra-mode-and-ipv6-address-mode-combinations"
1785213,2018-09-28 08:18:58 UTC,"Akihiro:
- I agree that subnet would be better place to put this new attribute instead of network,"
1785213,2018-09-28 11:04:10 UTC,If a customer wanted to use both this feature and neutron-fwaas would there be a way for fwaas to be notified about this?  Or are you thinking that this feature would just be incompatible with fwaas?
1785213,2018-09-28 14:20:56 UTC,Drivers team decided to ask in the operators mailing list whether this proposal is worth pursuing. Slawek to send question to the operators mailing list
1785213,2018-09-28 14:23:29 UTC,Question for later if this is revived: Does turning things over to an external dhcp server assume disabling all ipam functionality for that subnet?  Otherwise Neutron would assign an IP from it's pool that would never be used.
1785213,2018-08-24 11:20:09 UTC,"Yes. Basically that would be the result of this change. Additional parameter ""external-dhcp"" added to network and allowed traffic from external dhcp server for all ports in such network."
1785221,2018-08-03 11:38:25 UTC,"I believe the cause is that, per kubectl confg view --raw, microk8s is listening on the loopback address."
1785224,2019-08-11 07:53:01 UTC,"XInclude is implemented in libxml2 and not in lxml. However, lxml could probably work around this somehow by setting ""xml:base"" attributes in the tree after processing. The original XInclude markers are kept in the tree, so this might be possible as a post-processing step."
1785225,2019-07-19 17:46:56 UTC,"Hi,"
1785230,2018-08-18 10:20:02 UTC,Hi Srinivas!
1785230,2018-08-18 10:23:18 UTC,"Attempt to honor $DESTDIR when creating the symbolic link for libImageProcessor-{x86_64,x86_32}.so."
1785230,2018-08-18 11:50:43 UTC,"> Yes currently libImageProcessor.so is not open source. Hope you are not seeing any functionality issue when you print.
"
1785230,2018-08-21 16:10:14 UTC,"We have the same issue in Debian, which forces us to use an hplip amputed away from libImageProcessor. It's a serious move away from OpenSource, and specifically hinders our ability to ship hplip outside of only i386 and amd64 architectures. See https://buildd.debian.org/status/package.php?p=hplip&suite=experimental Up until 3.18.6, hplip was installable in non-x86_* architectures such as arm, mips or s390."
1785230,2018-08-27 20:52:52 UTC,"For now, the best workaround for distros appears to be reverting the libImageProcessor related changes to HPCupsFilter::processRasterData(), as Debian seems to have done already. It's likely ""just"" an optimization that enhances the rendering of rastered pages. (Some public information about the purpose of imageProcessorProcessLine() would be desirable)."
1785230,2018-10-17 18:40:43 UTC,I would also like to add my 2 cents...
1785230,2019-01-02 20:26:38 UTC,"I'm running into this problem as well, I cannot use the latest HP printer on a ARM device."
1785230,2019-08-30 04:49:43 UTC,It would be great to see this removed from the tarball as this is still a blocker for upgrading in some distributions.
1785230,2020-07-25 18:40:41 UTC,"Also running into the same problem, I cannot use the latest (>3.18.12) HPLIP on an ARM device (Raspberry)"
1785230,2018-08-06 10:40:41 UTC,"Hi,"
1785232,2020-11-19 09:51:30 UTC,"This was addressed in 2.7 by:
https://github.com/juju/juju/pull/11638"
1785234,2019-09-30 04:17:26 UTC,[Expired for linux-gcp (Ubuntu) because there has been no activity for 60 days.]
1785234,2019-07-31 07:26:17 UTC,"Hello,
As this bug report is a bit old, can you still reproduce this with the latest GCP kernel?
Thanks."
1785234,2018-08-08 02:27:25 UTC,Update: I could not recreate this bug using zbud as the allocator.
1785239,2020-06-07 01:28:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785247,2018-08-06 09:29:40 UTC,"Hi Paul,"
1785247,2018-08-06 11:20:25 UTC,"Srinivas,
Hi,"
1785247,2018-08-06 12:04:20 UTC,"Srinivas,"
1785247,2018-08-06 17:12:56 UTC,CUPS regards an rtf file as MIME media type text/plain - so it prints everything in the file. libreoffice converts it to something else (PDF?) before sending it to CUPS.
1785251,2019-05-14 06:29:13 UTC,"I have fixed ""shared state watcher was stopped""... I wonder if it'll help you."
1785251,2018-12-09 21:15:58 UTC,Further investigation found that the underlying allwatcher code needs to be more robust around models disappearing underneath it.
1785251,2018-10-09 11:01:33 UTC,"@Martin Hilton,"
1785251,2018-10-09 20:14:38 UTC,"The shared state watchers are tied to the model that they were requested on. If the model that was used to create the shared state watcher goes away, so does the watcher."
1785251,2018-12-09 04:17:47 UTC,[Expired for juju because there has been no activity for 60 days.]
1785253,2018-09-19 05:32:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785253,2018-09-19 05:34:09 UTC,"Also affects me. Happens after I wake up the machine from suspended state. Ubuntu Mate 18.04.1, Asus UX303UB, 4.15.0-34 kernel."
1785253,2018-09-19 05:43:34 UTC,As a temporary workaround: removing the proprietary nvidia drivers (nvidia-driver-390) fixed the issue for me.
1785254,2021-02-17 17:08:57 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1785260,2020-05-19 18:18:59 UTC,I can confirm that patron first and last name don't print/download either.
1785260,2020-06-24 14:31:03 UTC,PaILS has encountered this issue on 3.3.6 with the Patron Name fields. Staff wanted to use this to distribute work by patron to handle a backlog.
1785260,2019-06-20 17:06:55 UTC,"In a recent webclient, the Part column is populated correctly for a part-level hold. In the ""Print Full List"" version, the part is correctly included in the column headed ""Barcode/Part"".  In the CSV export version, the column is marked ""Part"" and is NOT populated."
1785260,2018-08-03 19:04:09 UTC,The parts are also missing from the CSV file.
1785260,2020-05-19 18:02:42 UTC,"It looks like this may not just be limited to the ""Parts"" column. Patron Last Name and Patron First Name are also not printing or downloading as part of the CSV. There may be others."
1785262,2020-12-21 08:34:47 UTC,This bug was fixed in the package libreoffice - 1:7.0.4~rc2-0ubuntu2
1785262,2020-12-10 10:18:42 UTC,"On Wed, Dec 09, 2020 at 10:46:52PM -0000, Rico Tzschichholz wrote:

> This issue is not restricted to arm* but have been seen occasionally on amd64.
> It effects the binary package build too, where these tests are part of ""make check"".
>
> There are a lot tests disabled in
> 'sw/qa/uitest/writer_dialogs/openDialogs.py' for similar reasons.
>
> So while it locks up at ""test_21_.uno:EditGlossary (openDialogs.openDialogs) ... "" I would give that a try:
> https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=0136e1c7a8f8823cbd0e5027ed203ee0d2f71262
"
1785262,2020-11-30 10:37:24 UTC,"> we don't believe it's a release issue
"
1785262,2020-12-09 22:46:52 UTC,"This issue is not restricted to arm* but have been seen occasionally on amd64.
It effects the binary package build too, where these tests are part of ""make check""."
1785262,2020-12-08 20:52:23 UTC,"After some more investigation, here are the main points that make this issue a tricky one to debug:
1. The test failure is not isolated. While the uicheck-sw test is the culprit, it is just an umbrella for many other tests. And it's those smaller tests that the failure occurs all over. This makes it hard to just ""fix the tests"".
2. I have not been able to reproduce this locally on a rpi4. Laney pointed out that perhaps having multiple containers running the same test might generate the load needed (assuming that plays a key role in the failures seen on LP) and I'll certainly give this a shot.
3. Currently if you look at the recent hirsute armhf and arm64 LO test results, you'll see that the rate of failure is way down (about 1/10 times). But just a couple of weeks ago the failure rate was much higher. This suggests that it's load on the nodes causing the problem because that's when the infra was quite busy.
4. Marking the test simply as ""flaky"" won't work because it's actually autopkgtest killing the process"
1785262,2020-11-30 19:54:42 UTC,"> That would seem to rule out FTBFS for example too.
"
1785262,2020-11-30 11:12:33 UTC,"> Would work for me, can we mark flaky-on-armhf only (I'd not be aware)?
"
1785262,2020-11-24 14:45:06 UTC,"Tagging notfixing, the bug is assigned and we will try to get it fixed rather sooner than later but we don't believe it's a release issue"
1785262,2020-01-06 17:12:56 UTC,Description:
1785262,2020-11-20 19:55:22 UTC,"I agree that the uicheck-sw test has increased in flakiness. How about instead of removing the test or sinking the resources into actually fixing them right now, I can mark them flaky so that at least a failed test looks like a skipped test:"
1785262,2020-11-19 12:31:43 UTC,"This recently showed up often enough that I bothered to find this bug :-/
I think it degraded again into a state where we should consider:"
1785262,2020-11-19 12:31:42 UTC,Christian raised this with us just now - I think we should consider taking a look at this.
1785262,2020-01-07 12:49:38 UTC,The problem is that thread 1 frame 13 makes a call on a UNO object while it allegedly holds the SolarMutex.
1785262,2020-01-06 17:16:03 UTC,"Created attachment 156969
backtrace without linebreaks"
1785262,2019-02-13 17:31:55 UTC,"1 failure out of 57 test runs in the past 30 days, that's a 1.75% failure rate."
1785262,2018-09-03 13:59:15 UTC,"3 failures out of 54 test runs in the past 30 days, that's a 5.6% failure rate."
1785262,2020-11-23 09:15:01 UTC,"On Fri, Nov 20, 2020 at 9:00 PM Heather Ellsworth
<email address hidden> wrote:

>
> I agree that the uicheck-sw test has increased in flakiness. How about
> instead of removing the test or sinking the resources into actually
> fixing them right now, I can mark them flaky so that at least a failed
> test looks like a skipped test:
"
1785266,2018-08-06 09:59:57 UTC,"Hi Pierre,"
1785270,2018-08-03 15:33:32 UTC,Alternatively we could deal with this during _init_instance in the ComputeManager on restart of the nova-compute service.
1785274,2018-08-16 13:05:38 UTC,It it again.  http://ci.jujucharms.com/job/github-check-merge-juju/2979/testReport/junit/github/com_juju_juju_worker_raft_raftflag/TestPackage/
1785274,2020-06-08 20:59:59 UTC,Marking as incomplete because I don't think we have seen this for some time.
1785274,2020-08-08 04:17:32 UTC,[Expired for juju because there has been no activity for 60 days.]
1785275,2020-02-03 19:49:12 UTC,https://github.com/canonical/cloud-init/pull/201/commits/b78742de6f2e2579118dfb8307e99fe7cb58fa00
1785275,2020-02-02 02:08:29 UTC,This bug should be closed with this commit landing
1785275,2019-12-30 15:35:42 UTC,@kevindtimm
1785275,2018-08-29 20:47:52 UTC,Attached is a patch for this modification
1785275,2018-09-06 14:08:25 UTC,"Hi,
To contribute to cloud-init, please follow the HACKING.rst doc.  You can view it online at
 https://cloudinit.readthedocs.io/en/latest/topics/hacking.html"
1785275,2018-08-03 17:52:06 UTC,Kernel command line specific as documented here https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt. I just configure this via grub.
1785275,2018-08-03 16:45:02 UTC,"You mention 'grub', is this at all specific to grub? or is this just kernel command line specific."
1785275,2019-12-21 02:37:33 UTC,it would be really great for pxe-less enviroments to fix this issue. MaaS has no method to operate in environments without dhcp without this patch.
1785285,2020-04-17 04:42:58 UTC,please unstall program do not work right
1785285,2018-08-25 21:58:34 UTC,"thx Oli for the feedback. Please can you attach to this ticket the corresponding log (that you should find in the /var/log/os-uninstaller folder of your Ubuntu partition?
also please run Boot-Repair, it will try to fix your Ubuntu boot sequence, and attach the log it will generate."
1785291,2019-06-12 17:47:02 UTC,I've discussed the issue regarding extraction of xattrs with upstream developers of tar and discovered that only user.* extended attributes are extracted by default due to cross platform compatibility concerns[1]. Based on that discussion and the small number of programs utilizing extended attributes it was decided to not pursue making xattrs the default.
1785314,2020-02-25 09:57:45 UTC,"I'm assuming the fix for this will be in Juju. If you feel otherwise, please reopen the MAAS task."
1785314,2019-08-17 05:13:37 UTC,"Keeping this one open, as we are working in area at present."
1785314,2019-08-17 04:17:25 UTC,[Expired for juju because there has been no activity for 60 days.]
1785314,2019-06-17 12:33:11 UTC,"So reading through this again, the issue is that Juju reads the list of
spaces from MAAS and grabs the ids for those spaces. And the ""undefined""
space always has Id = -1. When Juju makes a request of MAAS for a machine,
it always passes the Ids for the spaces rather than the names, and it turns
out that ""undefined"" can't be passed by Id.
And while certainly the recommendation is to use defined spaces, rather
than undefined, since newly provisioned machines that have not otherwise
been tuned come up as ""undefined"" it causes a bit of a problem. We want to
push people towards using spaces, but not require them to configure them,
sounds like we're winding ourselves in knots."
1785314,2019-06-17 06:25:12 UTC,"John,"
1785314,2019-06-12 09:47:35 UTC,"So
bindings:
  """": undefined"
1785314,2018-08-13 12:36:40 UTC,"So, I encountered weirdness when I didn't declare any space (""Juju can't choose a space..."" blah blah), that resolved by adding:"
1785314,2018-08-13 12:20:46 UTC,"Does this mean that the explicit container request was for the ""undefined""
space, which is what Juju was passing along to MAAS ?"
1785314,2018-08-09 23:16:16 UTC,"Thanks. I see how this could be a little bit annoying, and I'm sorry for that. But I still lean toward not fixing this issue in MAAS, because it encourages the use of the undefined space. This is not recommended and can cause problems when a MAAS region is expanded into new networks."
1785314,2018-08-04 01:43:04 UTC,There are two ways to request a machine that isn't in a space today:
1785314,2018-08-04 01:31:19 UTC,"And to be clear, I do agree with mike here that for juju it does make sense
to always have a space defined."
1785314,2018-08-04 01:07:26 UTC,"I don’t necessarily think this  is about juju. I truly feel this is an
issue that needs resolution in MAAS."
1785314,2018-08-04 00:11:05 UTC,How would someone go about requesting machines with no space at all?
1785314,2018-08-04 00:07:34 UTC,"Question: how can the containers on a machine be bound to spaces, and yet the machine itself is not on those spaces?"
1785314,2018-08-03 20:54:00 UTC,"That is to say, part of the justification for creating an ""undefined"" space is that it's not meaningful. For example, if you add a rack controller to MAAS and it's on a ""new"" network that has not yet been classified into a space, it will be in the 'undefined' (-1) space."
1785314,2018-08-03 20:52:06 UTC,"I do think it would be better if Juju doesn't send the space=-1 constraint. (It seems fairly meaningless to say ""I want to allocate a machine that is not in a space"".) It would be preferable to not send the space constraint to MAAS at all, in that case."
1785314,2018-08-03 19:56:17 UTC,"So from the looks of it, this is the issue:"
1785314,2018-08-03 19:50:26 UTC,"Juju is version 2.4.1-bionic-amd64 (installed from snap)
MAAS is version 2.4.0 (6981-g011e51b7a-0ubuntu1~18.04.1) (apt)"
1785314,2018-08-08 05:56:12 UTC,"My use case was slightly interesting (I guess); I wanted to assign several machines (not all) as machines in specific spaces (internal network). In addition, all machines are attached to a publicly available network (undefined space). When I didn't specify bindings, I ran into deployment issues with Juju unable to decide on a space for the undefined machines. Adding in specific bindings (`"""": undefined') resolved those issues but caused Juju to request these machines incorrectly."
1785315,2020-01-28 10:22:27 UTC,"Nvm, I only have the problem when I connect to a 14.04 machine, then start byobu, then connect to a 18.04 machine, and then start neovim. So the correct (14.04) versions of tmux and byoubu are"
1785315,2018-08-12 13:15:59 UTC,"Hmm, those versions of Byobu (5.73) and Tmux (1.8) are absolutely ancient.  Any chance you can reproduce this with modern, supported versions?"
1785315,2020-01-28 10:09:54 UTC,This still happens on Ubuntu 18.04 with
1785318,2018-08-03 20:21:27 UTC,"This is more than just volume-backed instances, it's evacuate in general. The API doesn't pass down the image_ref so we just pass {} to the rebuild_claim during evacuate in all cases, volume-backed or not."
1785318,2018-08-03 20:59:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588657"
1785318,2018-09-01 00:12:16 UTC,"Reviewed:  https://review.openstack.org/588657
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=665ba461f3135857034cf33dd5f427d47fdd155e
Submitter: Zuul
Branch:    master"
1785318,2018-09-21 09:20:14 UTC,"Reviewed:  https://review.openstack.org/599062
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6d8426ae59c9c989a38d00ff8c665d5ab129107d
Submitter: Zuul
Branch:    stable/rocky"
1785318,2018-09-24 14:47:02 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1785318,2019-03-22 03:48:58 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1785321,2020-04-30 08:29:29 UTC,"Looks like the other server I was talking about was installed with ubuntu-18.04-server-amd64.iso, not live-server, which is why it was sane - /var/log/installer/partman exists and the other logs show debian-installer was used."
1785321,2020-04-28 11:45:17 UTC,https://github.com/CanonicalLtd/subiquity/pull/737
1785321,2020-12-14 01:47:25 UTC,"This is a follow-up bug:
https://bugs.launchpad.net/subiquity/+bug/1893276"
1785321,2020-04-25 10:34:33 UTC,"This issue (really both, also the swapfile issue reported by @trs80) also carries on to Ubuntu 20.04 LTS Server. Since we no longer have the option of using the classic installer, this is creating a mess in terms of deployment."
1785321,2018-08-06 14:57:01 UTC,"> I can see how it's surprising but I'm not sure how to make it less so.
"
1785321,2018-12-02 22:58:30 UTC,"On Mon, 3 Dec 2018 at 02:55, Timlukas Bloch <email address hidden>
wrote:"
1785321,2018-08-05 21:54:49 UTC,"tj is right, there's not really any point using LVM if you then create a LV that fills your vg completely. I can see how it's surprising but I'm not sure how to make it less so."
1785321,2020-04-24 05:32:36 UTC,"Nah this is terrible. Also it doesn't create a swap partition. The behaviour still exists in 20.04 using the ""server-live"" iso. I did install two 18.04 VMs recently, one with 100GB disk and had this bug, the other with a 50GB disk and it installed as you would expect."
1785321,2018-12-02 13:49:19 UTC,"When choosing the option ""Entire Disk"" it should, imo, use the ""Entire Disk"". This is also the behaviour users expect, as the desktop installer and the old ""alternative installer"" do it this way."
1785321,2018-08-04 13:36:35 UTC,LVM is using the entire disk - it has allocated the 19GiB partition 3 to the LVM Volume Group and 1GiB to the separate /boot/ partition 2.
1785322,2018-08-06 15:57:12 UTC,This doesn't look like a package version that would come from the official Ubuntu archive.
1785327,2019-03-22 03:49:04 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1785327,2018-10-02 22:18:03 UTC,"Reviewed:  https://review.openstack.org/604378
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3480454a4ba9746e3066edef0945c02ec24af07e
Submitter: Zuul
Branch:    stable/rocky"
1785327,2018-10-08 20:53:37 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1785327,2018-09-21 12:10:36 UTC,"Reviewed:  https://review.openstack.org/588665
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=27857c337378472205c37db6ab79fe8404406129
Submitter: Zuul
Branch:    master"
1785327,2018-08-03 21:30:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588665"
1785327,2018-09-21 14:57:44 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604378"
1785329,2020-02-19 10:47:00 UTC,Ubuntu MATE 19.10 and onward default to Marco and Compiz is no longer shipped on the iso image. One reason for this change is to present a well-integrated default experience. Marco has received many improvements recently than mean Compiz is no longer required to erradicate screen tearing or improve gaming performance.
1785332,2019-02-27 00:09:58 UTC,"I am informed that grub now automatically delays boot if it cannot write to /boot (which avoids the issue where you put /boot on raid and then install a bad kernel, and then can't fix your machine because grub can't record the failed boot and interrupting the bootloader is hard over ipmi or in UEFI boot or whatever) so, subject to testing that this is correct, we can just lift the restriction. We should still leave some of the code paths present though because support for encrypted LVM will land soon and we don't want to let the user have /boot on that..."
1785332,2019-11-13 21:05:26 UTC,"This is fixed in the stable channel of subiquity. I can't remember if it was fixed in the 18.04.3 media -- I think so, but if not, update the snap during the install."
1785332,2019-10-07 01:59:09 UTC,"Same as #13, very simple non-LVM RAID 1 setup to replace an existing RAID 1 setup carried forward from the last LTS release.  What an unpleasant surprise especially considering the doc's at https://help.ubuntu.com/lts/serverguide/advanced-installation.html make no mention of the new restriction.  When will this be corrected?  Do I need to re-install 16 then roll forward to keep /boot inside the array?"
1785332,2019-06-21 17:21:31 UTC,"Also was unable to do a fairly simple RAID-1 setup. I agree with #10: https://ubuntu.com/download/server should  link directly to the old installer, presenting the new one only as an experimental option."
1785332,2019-05-17 10:06:30 UTC,I confirm that this bug is still present in 18.04.2 server ISO (non-live version). 16.04 allowed to create md raid and put everything on it (grub supports it!) but this requires creating a separate partition for /boot alone.
1785332,2019-05-10 18:35:56 UTC,This bug is still present on the 18.04.2 live server ISO.
1785332,2019-05-01 14:13:33 UTC,"How is this ""new"" installer still the default, let alone even being used? It's absolute garbage, and once again I now have to do the Googles and re-download, re-image, and restart a server installation because of this piece of sh*t installer that Crapnonical for some reason is pushing on us. Some unknown reason. Perhaps I'd see the reason, if my view wasn't block by the mountain of missing features and crap bugs and shortcomings."
1785332,2019-02-26 18:42:11 UTC,If you want to use RAID (and probably LVM) use the non-live server image (even for desktops) and save yourself a lot of hassle:
1785332,2019-02-08 11:43:24 UTC,"+1
Same problem here.
I can use USB drive for /boot, but it's shit and sticks solution."
1785332,2018-12-17 17:49:59 UTC,Can confirm this.
1785332,2018-10-11 11:10:25 UTC,"This problem actual so far.
Ubuntu, version 18.04.1 / 11 october 2018"
1785332,2018-09-24 11:46:56 UTC,"Same problem here, this new installer is really bad. :("
1785332,2018-09-17 10:44:28 UTC,"Subiquity also refuses to allow /boot on LVM. With the alternate installer, 18.04 was happy to install /boot/efi on an automatically allocated partition, and have / and swap as logical volumes in an LVM volume group."
1785332,2018-08-05 21:52:22 UTC,"Yes, this should be supported but as you note it's a bit complicated."
1785332,2019-02-11 14:44:24 UTC,"As a workaround you can use a ubuntu-18.04.1-server-amd64.iso (that iso without ""live"" in its name). Its installer allows you to not create a separate partition for /boot, so you can just leave  this directory to be stored on a root partition, which can be on software raid."
1785336,2018-08-19 08:29:02 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1785336,2018-08-19 08:43:26 UTC,I built recode from what I believed to be the upstream source:
1785336,2020-07-08 11:34:01 UTC,"Hm.. interesting. Unfortunately the bug is still present even in Ubuntu Groovy. However, there seems to be some work under way to get the new version packaged (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961136), perhaps that will fix it."
1785337,2018-08-06 17:43:07 UTC,"Hi Daniel,"
1785339,2018-10-08 21:50:52 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1785339,2018-10-08 21:49:10 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1785339,2018-10-08 21:45:28 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1785339,2018-10-03 06:37:46 UTC,"Reviewed:  https://review.openstack.org/605880
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c4ea58eb867ee90785101663325a92f1d771842a
Submitter: Zuul
Branch:    stable/ocata"
1785339,2018-09-29 07:54:29 UTC,"Reviewed:  https://review.openstack.org/602409
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2d2a9a7c538f87775092c6cbf3b03b463cbdc2a
Submitter: Zuul
Branch:    stable/queens"
1785339,2018-10-02 02:51:16 UTC,"Reviewed:  https://review.openstack.org/605879
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=556079a33997958d26fb7f03946998a6b06f488c
Submitter: Zuul
Branch:    stable/pike"
1785339,2019-03-22 03:49:02 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1785339,2018-09-27 23:01:22 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/605880"
1785339,2018-09-13 17:40:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/602409"
1785339,2018-09-24 14:46:47 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1785339,2018-09-20 16:49:01 UTC,"Reviewed:  https://review.openstack.org/602403
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9125fc7caf68fcecea47a3f0ac5068cf44a97821
Submitter: Zuul
Branch:    stable/rocky"
1785339,2018-09-13 17:17:53 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/602403"
1785339,2018-09-13 00:35:41 UTC,"Reviewed:  https://review.openstack.org/588689
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ef3849e2da1c94df519debcb14ba15af9bd01a60
Submitter: Zuul
Branch:    master"
1785339,2018-08-03 23:15:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588689"
1785339,2018-08-03 22:46:36 UTC,I noticed this while going through the starlingx-staging/stx-nova diff:
1785339,2018-08-03 22:45:00 UTC,This has been broken since newton:
1785339,2018-09-27 22:47:57 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/605879"
1785342,2019-05-14 14:44:13 UTC,This issue was fixed in the openstack/tripleo-quickstart-extras 2.1.1 release.
1785342,2019-02-26 13:47:38 UTC,Is this still an issue?
1785342,2018-08-06 21:31:35 UTC,last paste cut off the most important part
1785342,2018-08-24 15:57:45 UTC,This was previously diagnosed as issues with stuck stacks causing bmc not to properly bring up all the assigned network interfaces.  Dropping to High as we should solve for that and monitor but it is an infrastructure related issue and not code related.
1785342,2018-08-05 16:29:20 UTC,"We need to get this bug resolved https://bugs.launchpad.net/tripleo/+bug/1785055
to properly debug the issue at this point."
1785342,2018-08-05 16:28:49 UTC,"This patch did not improve the situation
https://logs.rdoproject.org/45/560445/106/openstack-check/legacy-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-master/846c368/logs/undercloud/etc/resolv.conf.txt.gz"
1785342,2018-08-04 06:30:50 UTC,"Reviewed:  https://review.openstack.org/588678
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=baa78023d076156d8214997eb88d28b9a2d8c1ab
Submitter: Zuul
Branch:    master"
1785342,2018-08-03 23:00:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588678"
1785342,2018-08-06 21:06:23 UTC,DNS changes did not resolve this issue...
1785354,2018-08-05 21:53:32 UTC,Pretty sure this is curtin too.
1785354,2018-08-06 18:14:59 UTC,"Curtin supports specifying this information in the mount structure (mount documentation needs an update to indicate we support specifying any of the mount fields in fstab (spec, fstype, path, freq and passno)."
1785354,2018-09-05 17:06:48 UTC,"I'd like to point out that, at least (maybe not only?) from a user perspective, this is a regression when comparing to both the previous (16.04.x) LTS (d-i) server installer and the 18.04.x alternative (d-i) server installer."
1785363,2018-08-06 02:36:25 UTC,Did you try installing the nvidia driver?
1785363,2018-08-08 03:50:11 UTC,"Hi Team,"
1785363,2018-08-08 04:13:22 UTC,Please try the workarounds mentioned at the top of bug 1705369.
1785363,2018-08-08 10:17:36 UTC,"I tried what you said but it's stuck that run level might be some graphics
parameters have to changed.
I have remove the Nvidia Driver 390 using recovery menu .
Now it's working fine.
Thanks for you response"
1785363,2018-10-08 04:18:53 UTC,[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been no activity for 60 days.]
1785371,2018-08-14 18:16:32 UTC,This issue was fixed in the openstack/zun 2.1.0 release.
1785371,2018-08-20 18:31:21 UTC,This issue was fixed in the openstack/zun 1.0.1 release.
1785371,2018-08-08 02:52:38 UTC,"Reviewed:  https://review.openstack.org/589331
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=db0cea7121628d6d27e0beaa10b989be33dad37e
Submitter: Zuul
Branch:    stable/queens"
1785371,2018-08-05 20:40:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/588992"
1785371,2018-08-07 03:03:06 UTC,"Reviewed:  https://review.openstack.org/588992
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=de82a5dc81816194eecbbf609ca3c179b7aa9368
Submitter: Zuul
Branch:    master"
1785371,2018-08-05 20:45:58 UTC,Thanks for reporting the bug. I analyzed how other projects (i.e. nova) manage the RPC connections and borrowed their idea of using a global RPC transport per API server. This should further improve the performance since we don't have to create/cleanup the RPC connection per API call.
1785371,2018-08-07 03:37:28 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/589331"
1785376,2018-08-06 05:39:19 UTC,Upstream version 2.79 has this in the changelog:
1785376,2018-08-06 05:40:21 UTC,"Since it ""only"" affects backports to very old releases as we have
  Xenial: 3.2-1ubuntu0.16.04.1
  Debian-Stable: 3.3-1
I'll mark importance low for now."
1785376,2018-08-06 05:42:31 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1785379,2018-08-04 10:38:15 UTC,apport information
1785379,2018-08-04 10:38:16 UTC,apport information
1785379,2018-08-04 10:38:18 UTC,apport information
1785379,2018-08-04 10:38:19 UTC,apport information
1785379,2018-08-04 10:38:20 UTC,apport information
1785379,2018-08-04 10:38:21 UTC,apport information
1785379,2018-08-04 10:38:25 UTC,apport information
1785379,2018-08-04 10:38:24 UTC,apport information
1785379,2018-08-04 10:38:14 UTC,apport information
1785379,2018-08-04 10:38:26 UTC,apport information
1785379,2018-08-04 10:38:28 UTC,apport information
1785379,2018-08-04 10:55:13 UTC,Sorry doublized files are same. It was my failing
1785379,2018-08-06 16:07:10 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1785379,2018-08-04 10:38:22 UTC,apport information
1785379,2018-08-04 10:38:13 UTC,apport information
1785379,2018-08-04 10:37:10 UTC,apport information
1785379,2018-08-04 10:37:25 UTC,apport information
1785379,2018-08-04 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1785379,2018-08-04 10:37:26 UTC,apport information
1785379,2018-08-04 10:37:08 UTC,apport information
1785379,2018-08-04 10:37:09 UTC,apport information
1785379,2018-08-04 10:37:12 UTC,apport information
1785379,2018-08-04 10:37:13 UTC,apport information
1785379,2018-08-04 10:37:14 UTC,apport information
1785379,2018-08-04 10:03:58 UTC,i tried again now after restart. Firstly was 10 minutes cpu on 100% without sending of log files.
1785379,2018-08-04 10:37:17 UTC,apport information
1785379,2018-08-04 10:37:18 UTC,apport information
1785379,2018-08-04 10:37:19 UTC,apport information
1785379,2018-08-04 10:37:20 UTC,apport information
1785379,2018-08-04 10:37:22 UTC,apport information
1785379,2018-08-04 10:37:23 UTC,apport information
1785379,2018-08-04 10:37:15 UTC,apport information
1785383,2019-12-11 18:16:45 UTC,"> although from comment #4 it sounds like it might be a regression caused by a security fix.
"
1785383,2019-12-04 21:36:50 UTC,"Targeting to bionic, since disco/eoan/focal are on 2.80 which, per the OP, should already be carrying the requested fix."
1785383,2019-12-04 21:31:49 UTC,"I've linked to the upstream systemd bug report, although from comment #4 it sounds like it might be a regression caused by a security fix."
1785383,2019-12-02 11:31:20 UTC,"Any news on this? Recent upgrade has removed my patches to dnsmasq, and I'm hitting this again. Still convinced the Ubuntu-specific patch to systemd-resolved is flawed as well."
1785383,2018-08-05 17:30:42 UTC,"Reverting the patch ""resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch"" solves this problem for me. My best guess is that the following patch segment changes some key logic:"
1785383,2018-08-31 21:24:34 UTC,Returning NXDOMAIN is the behavior of Adblock on Turris-os (a derivative of OpenWRT) with Knot resolver as back-end. I am of the same opinion than @cbz . At the moment I will limit the logging rate.
1785383,2018-08-16 12:19:09 UTC,"In my opinion the log message from system also needs to be dropped - a number of systems will use NXDOMAIN as a means of domain blocking/ad blocking, and this isn't thus an exceptional event that needs logging each time."
1785383,2018-08-05 16:24:15 UTC,On further investigation this seems to be specific to the Ubuntu version of systemd 237. I cannot reproduce it with the upstream release.
1785383,2018-08-05 13:55:02 UTC,Amend to test case:
1785383,2018-08-31 21:26:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785386,2018-12-06 16:22:18 UTC,"So, I'm definitely planning to provide something like ""Ceph as a Service"" via Manila!"
1785386,2018-08-07 16:44:34 UTC,There is not currently a Manila role within OpenStack-Ansible. We would readily accept a contribution of this role however. Swift is not something that is integrated on top of Ceph. Please look at Ceph RGW if you want a swift API with a ceph back-end.
1785386,2018-11-13 02:40:15 UTC,We do have a Manila role now [1].
1785387,2018-08-15 18:00:50 UTC,"Does it work properly elsewhere? Login screen, TTY, different DE, etc."
1785387,2018-08-18 10:58:23 UTC,"<Shift> + 4 has resulted in the ¤ character on Nordic XKB keyboard layouts for quite some time. If new keyboards tend to have the € character printed on that key instead, there may be a reason to reconsider it."
1785387,2018-08-18 10:09:19 UTC,"So, this is not some Xubuntu/Xfce specific issue."
1785387,2018-08-18 08:45:16 UTC,"No, not on login screen or TTY. I have no other DE installed."
1785388,2018-09-09 06:44:59 UTC,snapd 2.35.1+18.10 has not fixed the problem
1785388,2018-08-05 14:43:46 UTC,"This is currently intentional (for cosmic only), please see:"
1785388,2018-08-04 12:07:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1785388,2018-08-04 12:12:43 UTC,"Ubuntu forums threads:
https://ubuntuforums.org/showthread.php?t=2393347
https://ubuntuforums.org/showthread.php?t=2396847
https://ubuntuforums.org/showthread.php?t=2397851"
1785388,2018-08-04 16:15:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785391,2018-08-05 12:50:42 UTC,https://gitlab.com/apparmor/apparmor/merge_requests/157
1785391,2018-08-07 10:53:24 UTC,Fix commited to 2.10 branch..master
1785391,2019-02-15 22:33:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785391,2018-08-04 12:18:14 UTC,"Funny enough, aa-logprof doesn't work well in a guest on my system either:"
1785394,2018-08-05 00:40:30 UTC,"Just upgraded to 17.1 (unstable) Gentoo profile, but bug is still there."
1785396,2019-01-17 03:48:45 UTC,"Not critical for 5.1, moving to 6"
1785396,2018-09-07 14:08:25 UTC,I guess it also depends on the board size and complexity?
1785396,2018-09-07 13:35:04 UTC,The updates are very fast for me and I don't notice them unless I have a broken edge cuts.  This may be os/setup dependent.
1785396,2018-09-15 21:29:41 UTC,"Here are some tips to speedup the reload, until this is not fixed:
- Use OpenGL render engine."
1785396,2018-09-05 17:29:15 UTC,"I think we can probably make ""auto-update"" an option in the viewer"
1785396,2018-08-04 14:11:22 UTC,"Yeah, that'd be even better actually, but more difficult to implement (I'm guessing, I don't know the kicad codebase).  Of course the 3D view should not blindly update itself N times if it has received N update requests from pcbnew.  If it can, it should cancel its updating process when it receives a new update request and restart it."
1785396,2018-08-04 13:59:09 UTC,"Or at least, when the 3D window is visible, say on another monitor, don't block pcbnew when updating the 3D view, just post it updates and let it re-render as best it can."
1785396,2018-09-07 11:21:42 UTC,"If there's an auto-update option, but updates are as slow (and app-blocking) as now, I bet most people will have the auto-update just disabled.  At which point it turns into a ""push a key to refresh"" kind of thing."
1785397,2018-09-08 16:34:26 UTC,"Does this happen with all display settings in accelerated?  No anti-aliasing/super-sample, etc?"
1785397,2018-09-09 12:51:19 UTC,That would explain why I couldn't find how that dash length was set!
1785397,2018-09-09 13:27:47 UTC,I suspect that this is more pronounced on lower dpi monitors so I'm hesitant to adjust anything to compensate for it.  I think maybe we can lump it in with selection customization options when we implement so that users can increase linewidth on their own along with color settings.
1785397,2019-04-01 16:11:44 UTC,Is this still the case with the new OpenGL renderers?  Or were those specific to eeschema?
1785401,2018-08-09 18:55:30 UTC,lxqt-config shouldn't recommend it.
1785401,2019-11-04 20:05:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785401,2018-08-21 18:33:50 UTC,This bug was fixed in the package lxqt-config - 0.13.0-0ubuntu3
1785401,2018-08-09 22:13:50 UTC,https://launchpad.net/ubuntu/+source/lxqt-config/0.13.0-0ubuntu3
1785401,2018-08-09 18:51:13 UTC,"When I said upstream, I meant Qt."
1785401,2018-08-04 16:29:53 UTC,Changed affected package to lxqt-config
1785401,2018-08-09 12:58:03 UTC,I tried here: https://github.com/lxqt/lxqt/issues/1540
1785401,2018-08-09 10:00:48 UTC,How do I file a bug upstream? Could you please provide details or a link?
1785401,2018-08-05 20:51:27 UTC,I would also highly recommend that you file a bug upstream alerting them of this.
1785401,2018-08-05 20:50:56 UTC,"This is not a problem with the LXQt configuration, but it's a problem with qtstyleplugins-src."
1785401,2018-08-09 16:52:40 UTC,"tsimonq, thanks for forwarding upstream. I filed as well and it was closed as a dupe of your forward: https://github.com/lxqt/lxqt/issues/1532"
1785406,2018-08-04 16:20:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1785407,2019-11-04 07:15:54 UTC,"Hello Ali,"
1785407,2021-02-01 18:51:04 UTC,Closing as this actually what we already have as the darken/lighten with paper color effects.
1785410,2018-09-09 08:46:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785410,2019-03-22 15:54:43 UTC,I've seen this happen a couple of times.  Running snap-discard-ns seems to resolve it.
1785411,2018-10-02 13:44:27 UTC,Please report upstream (https://github.com/mate-desktop/mate-utils/issues) and give them the link from this page and then comment here with the link from the report that you've made there. Thanks
1785411,2018-10-02 20:02:15 UTC,Link from posting upstream bug report:
1785411,2018-08-04 18:56:53 UTC,Example of labels appearing while cursor is kept moving slowly over ring.
1785411,2018-08-05 06:31:47 UTC,"When I place the cursor over a ring, the black label appears first, then the grey labels appear indicating the sub-rings, but they don't seem to disappear as long as I have my cursor placed."
1785412,2019-01-21 14:37:29 UTC,That would be very useful for many projects that need OpenSSL 1.1.0 on Travis CI.
1785417,2018-08-05 23:43:51 UTC,This is only happening with gpt right?  This was fixed in https://review.openstack.org/#/c/578265/ which will be in the next release.
1785422,2018-08-11 00:24:20 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1785425,2019-05-24 10:24:00 UTC,"Reviewed:  https://review.opendev.org/650460
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dba9b722afa7904e704db54af076f1de123f78e9
Submitter: Zuul
Branch:    stable/queens"
1785425,2019-04-05 22:10:53 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/650460"
1785425,2019-07-10 21:40:17 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1785425,2018-08-10 09:52:32 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.
1785425,2018-08-07 02:58:07 UTC,"Reviewed:  https://review.openstack.org/589039
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=65cdcf4aaa9aec2fbeb29c9734b07efff32a2c49
Submitter: Zuul
Branch:    master"
1785425,2018-08-06 07:31:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589039"
1785425,2019-04-05 22:02:18 UTC,Also seeing this in stable/queens: https://review.openstack.org/#/c/649362/
1785434,2018-08-05 16:12:19 UTC,"Crashing the whole Wayland display server would be a bug in the Wayland display server, not in VLC."
1785434,2018-08-08 13:51:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785434,2018-08-08 13:54:54 UTC,"Same story here, this bug appeared again in 18.04 with the recent VLC update to version 3.0.3"
1785434,2018-09-10 15:34:14 UTC,Me three. Intel Iris pro 5200. Xorg is fine. Wayland crashes on full screen. Ubuntu 18.04.1. VLC 3.0.3. Wayland 2:1.19.6-1ubuntu4.
1785434,2018-09-10 23:55:01 UTC,It happens in Xorg too. When I am in fullscreen and I hover the mouse over the playback position bar the video freezes a moment and if I click to a different position it freezes for a lot of time or forever and I have to reset my pc. Intel HD Graphics 3000. Ubuntu 18.04.1 LTS. VLC 3.0.3-1-1ubuntu1. xserver-xorg-core 2:1.19.6-1ubuntu4.
1785434,2018-11-11 22:31:44 UTC,"Same problem here, display freezes if I move the mouse over the position bar in full screen VLC. The sound keeps on playing. Although closing the lid of my laptop so that it suspend itself, and then resuming makes it unfreeze.
Ubuntu 18.04.1 LTS, VLC 3.0.3 Vetinari (3.0.3-1-0-gc2bb759264), GNOME 3.28.2"
1785434,2018-11-27 13:47:56 UTC,Yesterday's VLC update to 3.0.4 fixed it for me.
1785434,2019-01-27 16:42:23 UTC,The issue is still present on disco with VLC 3.0.6-1 and GNOME 3.30.1. I'm happy to deliver any relevant log files to resolve the issue.
1785444,2019-02-17 20:00:01 UTC,Ubuntu 18.10 and upcoming 19.04 are affected too.
1785444,2019-02-17 19:15:36 UTC,"Just seen this on Ubuntu 18.04.2 LTS with Unity desktop.
GNOME Terminal is useless without mnemonics. It is time to use `mate-terminal` instead or whole `ubuntu-mate-desktop` with MATE DE."
1785444,2018-08-05 03:20:28 UTC,Note related bug https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1734817
1785444,2018-08-05 09:56:56 UTC,"gnome-terminal switched to using the GMenu architecture in https://gitlab.gnome.org/GNOME/gnome-terminal/commit/0820b3853, which is supposed to be superior to the old one with Unity's menuproxy. It suffers from new bugs and limitations though."
1785444,2019-02-17 19:07:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785456,2019-10-14 16:44:18 UTC,"Thank you for your bug report, it looks like a local corruption/download error rather than a package bug though"
1785458,2018-08-05 12:31:52 UTC,"I had a go a patching matplotlib so that the python2 package would at least contain the GTK backends.
https://launchpad.net/~jdpipe/+archive/ubuntu/ppa/+packages"
1785458,2018-09-14 07:16:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785458,2018-09-18 12:54:02 UTC,"Just hit this bug too, thanks for John for his packages, they work nice"
1785458,2018-11-25 23:16:42 UTC,"Can second Pacho with the same bug here. Also John's patch worked like a charm, thousand thanks!"
1785458,2019-01-23 23:33:09 UTC,"Upstream package maintainer dropped it because GTK2 is deprecated:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889137#10"
1785458,2019-04-24 18:34:59 UTC,Thanks John!
1785459,2019-06-17 20:16:07 UTC,"Reviewed:  https://review.opendev.org/650605
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=00d0cb71e63e870fdf09833eec02f29b95542b18
Submitter: Zuul
Branch:    stable/queens"
1785459,2019-05-08 23:09:35 UTC,"Reviewed:  https://review.opendev.org/650604
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=2b4fbbf4d8c72a785cb1f8efe3ebdc2ee07a6a69
Submitter: Zuul
Branch:    stable/rocky"
1785459,2019-05-08 18:34:53 UTC,"Reviewed:  https://review.opendev.org/650603
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=9b4b876d6ae3298110e15b6998306a2cf5660c3f
Submitter: Zuul
Branch:    stable/stein"
1785459,2019-04-08 02:29:59 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/650607"
1785459,2019-04-08 02:29:31 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/650605"
1785459,2019-04-02 10:57:47 UTC,"Reviewed:  https://review.openstack.org/647711
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=f828654a3d40476cac7eb24a09a36e9978c2d708
Submitter: Zuul
Branch:    master"
1785459,2019-04-08 02:29:46 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/650606"
1785459,2019-04-08 02:29:02 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650604"
1785459,2019-04-08 02:27:26 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/650603"
1785464,2018-08-05 10:00:07 UTC,This change was made by a bot.
1785464,2018-08-06 16:06:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1785464,2018-08-07 15:33:06 UTC,"Installed 4.18-rc8, will let you know..."
1785464,2018-12-12 03:21:43 UTC,Would it be possible for you to do a kernel bisection?
1785466,2018-08-05 12:22:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1785466,2018-08-07 18:48:22 UTC,Plymouth is only the messenger here; the problem lies with whatever package is installed that is running the service that is hanging.
1785466,2018-08-08 00:36:20 UTC,Thanks for your response but please can you tell me how can I check what is the responsible package ?
1785466,2018-08-08 00:40:15 UTC,See : https://github.com/tseliot/ubuntu-drivers-common/blob/master/share/hybrid/gpu-manager.service
1785470,2020-08-24 18:11:26 UTC,"Hi, sorry for the long delay in finding this bug. While it may already be solved, I am interested in knowing if you can:"
1785470,2018-08-05 20:14:15 UTC,https://github.com/lxc/lxd/issues/4877
1785470,2018-08-05 20:13:55 UTC,"I have asked `lxd` devs, and have response suggesting that issue lays in `snapcraft` having issue with setting up a correct lxd container with snap inside of it. Perhaps there is a some kernel mismatch between Arch and Ubuntu."
1785475,2018-08-26 11:41:37 UTC,"I've given you my IP address, but am unable to ssh into your server."
1785475,2018-08-12 13:38:17 UTC,"Benno, can you supply me with an ip adres for the FW by sending it by private mail to me?"
1785475,2018-08-12 07:31:15 UTC,"Hmmm...  When the line containing ""Minimum"" and the second ""vpn"" line should 'overlap' when doing a single PageDown, then your terminal must have 61 rows (when using --ignorercfiles).  But... when I alternately do a PageDown and a PageUp, and look how exactly those two lines would interweave, then I can never see ""vpn IN NSnimum ( ns2urs)"", as you have posted, no matter what tabsize I use.  With --tabsize=4, it would display ""NSinimumns2__4_hours)"" (where an underscore stands for a space), and with --tabsize=5 it would display ""NSimum_(__ns2hours)"" -- *if* tabs wouldn't be cleared properly."
1785475,2018-08-11 07:36:22 UTC,"The bug *seemingly* affects three people: the reporter (you), one person who was clearly a fake, and one other person ""confirmed"" it by clicking that he/she is affected too.  But an anonymous person whom I can't ask questions doesn't count as confirmation for me.  And most likely that anonymous person is a sockpuppet too, because confirming a report so soon after it was filed..."
1785475,2018-08-10 20:21:11 UTC,"It are all new installs ubuntu 18.04 server,
The bug was confirmd by 3 personens 1 acount was a fake (not by me!)"
1785475,2018-08-08 17:26:39 UTC,"Thanks for the files you sent via private email.  However, I am unable to reproduce the effect that you see."
1785475,2018-08-07 19:37:48 UTC,"I just noticed that it happens with pgup en pgdown keys not wit cursor keys.
To morrow i will try to compile the recent nano"
1785475,2018-08-07 19:25:33 UTC,Estaba bromeando Bas
1785475,2018-08-07 19:18:28 UTC,don't know what a sockpuppet is bastiaan82 is not my account !
1785475,2018-08-05 19:59:21 UTC,The zone file is just example it also happen when editing a big random file
1785475,2018-08-07 17:18:22 UTC,By the way: please delete your sockpuppet bastiaan82.
1785475,2018-08-07 17:13:36 UTC,Dang.  How hard is it to answer *all* questions?  Provide the full output of 'locale' on the affected machine.
1785475,2018-08-06 20:22:40 UTC,"arcording ubuntu-bug  TERM=xterm
but it doesn't matter.
I didn't fiddle"
1785475,2018-08-06 19:48:34 UTC,"Please answer also the other questions: which terminal, and the full output of 'locale'.  Further, did you fiddle with your system?  Have you symlinked some libraries?  Also, are you able to build nano from source?  If so, please try building the latest 2.9.8, and see how it fares."
1785475,2018-08-05 18:55:08 UTC,"On which terminal emulator are you seeing this effect?  What is the output of the 'locale' command?  Can you attach the DNS zone file you were looking at?  Can you search your system for a file that contains the word fragments ""every"", ""fresh"", ""urs"", ""xpire"" and ""nimum""?  Because it seems the zone file gets interleaved with another."
1785475,2018-08-05 14:46:20 UTC,i made a video showing the problem i think thats beter than my description
1785475,2018-08-05 14:21:44 UTC,I can confirm the bug
1785475,2018-08-05 14:20:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785475,2018-08-07 19:16:46 UTC,"Sorry missing that question, in my defense my mother got commited to the hospital and wasn't clear minded"
1785475,2018-08-05 14:46:58 UTC,"the link :-D
https://youtu.be/MaPlL-L43w0"
1785477,2018-08-20 00:09:43 UTC,Thanks for reporting this bug.
1785484,2018-08-06 14:09:40 UTC,"A bit more info.  Adding the "">/dev/null 2>/dev/null"" didn't really fix the issue.  Now I get another email from cron reporting:"
1785493,2020-04-03 15:04:15 UTC,"Hey Mathieu, when will this bug be fixed, it's been quite some time. Thanks!"
1785493,2018-09-10 09:21:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785494,2020-03-29 12:35:30 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1785497,2018-08-06 05:48:57 UTC,alsa: http://www.alsa-project.org/db/?f=b45e03c79071a7490bc7b41e7b583db12c3fe45a
1785497,2018-08-05 20:21:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1785500,2020-08-10 00:04:14 UTC,Fixed in version ghc/7.10.3-5
1785502,2018-08-24 13:56:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785502,2018-08-24 14:10:42 UTC,"I made it installs correctly.
Since I had a backup, I decided to reinstall completely from scratch (which didn't work at first...)"
1785502,2018-08-24 14:43:57 UTC,"Sorry not being able to correct last comment...
/usr/local/bin/bundle has the same flaw...
So eveything wasn't fixed in my case.
Haven't been able to reimport my backup with my plugins yet."
1785502,2018-08-24 14:55:49 UTC,Brought it back to work:
1785503,2020-04-08 09:58:00 UTC,There is no plan to diverge from upstream's default in Ubuntu.
1785503,2020-04-08 09:54:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785504,2019-07-09 21:45:12 UTC,Note that we'd need to use either class attributes or data-* attributes.  IDs must be unique within an XML document.
1785507,2018-08-06 05:56:00 UTC,"It certainly does on my machine.
Test it on the same machine to figure out what's really going on; it certainly isn't a bug with the distro, but lshw and related to your machine hardware."
1785515,2018-08-05 20:35:10 UTC,I reinstalled and the script appeared to run as it always has. I used the following in terminal:
1785515,2018-08-06 09:54:57 UTC,"Hi Pete,"
1785515,2018-08-06 18:57:54 UTC,"I solved the ""canberra-gtk-module"" error with"
1785521,2018-08-06 10:31:21 UTC,"Hi, you are using the 1.2 version of Open Rails that is now obsolete, I recommend you download a new version of the simulator, because from the release of version 1.2 to today, some bugs have been fixed and have been added improvements both in the execution of the program and new functions concerning the simulation itself.
First of all, download the updated version of O.R. from the following link:
http://james-ross.co.uk/projects/or/builds/2018-08-04_21-59-07_X4166/Open%20Rails%20X4166%202018-08-04%2021-59-07.zip
once the download is complete, unzip the .zip file to a convenient folder, then copy the contents of the convenient folder to the folder where you have installed OpenRails and answer Yes when you are asked to overwrite the existing files.
Installed the version that I have indicated, I suggest you to automatically perform the update of the program by going to the Options, then select the ""Updates"" tab then choose the ""Test"" option and confirm by clicking OK.
In this way, at the top right, the link to update will be displayed when available. When the link is displayed click on this so Open Rails will be updated automatically. At the time of writing the latest version is: X4166."
1785527,2018-08-05 22:51:34 UTC,"I should add, the menu remained at the front of the screen - ie it hid that area of any other program opened on that screen."
1785529,2018-08-06 00:16:11 UTC,"Hi Akond,
I appreciate your research.
Fuel library is no longer maintained project and was deprecated in 2017. As deprecated project is is unlikely that Fuel library receive any further updates from the OpenStack community."
1785530,2019-05-10 12:44:32 UTC,Only an examples file on how to use puppet-ceilometer.
1785535,2018-11-06 11:21:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785535,2019-12-17 15:21:54 UTC,Same problem with Ubuntu 18.04 and workrave 1.10.16.0
1785537,2018-08-06 00:49:57 UTC,The video file that caused the most recent crash was an MP4 15.9BM when uncompressed. I've successfully opened many files that were much larger than that.
1785537,2018-08-06 01:11:06 UTC,Here's the relevant /var/log/syslog output:
1785538,2018-09-08 09:41:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785545,2018-08-10 05:58:02 UTC,https://github.com/mixxxdj/mixxx/pull/1775 helps a bit
1785545,2018-09-11 19:57:25 UTC,"Who has a reasonable big iTunes library to test the PR linked above?
@patfernandes123: Are you able to test the pull request above?"
1785563,2018-08-12 20:56:49 UTC,"I compiled hugin-0-7-0-rc6-3749-f00195a91d45, it's still the same."
1785563,2018-11-03 18:25:57 UTC,/tmp/screenshot_20181103_192543.png
1785563,2018-11-03 18:26:15 UTC,This is still an issue in today's code.
1785563,2018-11-04 07:46:03 UTC,"This can't be changed easily and would require a complete rewrite of the grid code.
But you can disable the grid."
1785567,2018-08-17 17:52:50 UTC,Do you have the python3-distutils package installed?
1785567,2018-08-26 09:56:32 UTC,"Upgraded from 16.04, python3-distutils was not installed. After installation, Anki starts just fine. Please update the package in Bionic to include it as a dependency."
1785567,2019-01-03 19:18:30 UTC,In Anki there is a failure to play the audio because it does not work what to do?
1785569,2018-08-09 08:27:12 UTC,From: https://github.com/rabbitmq/rabbitmq-clusterer#cluster-configuration
1785573,2019-09-07 06:13:22 UTC,These points are not relevant here and are old: some of them are fixed in version 0.12. If the OP still has concerns they should be taken up with the incron maintainer at https://github.com/ar-/incron.
1785586,2018-08-08 15:44:21 UTC,"I've raised a bug against juju core regarding the key name change, which may be dangerous for other reasons."
1785586,2018-08-06 09:49:13 UTC,Proposed fix on: https://code.launchpad.net/~pguimaraes/python-jujuclient/python-jujuclient
1785587,2018-10-28 12:31:22 UTC,"Followed the instructions from ""Gabriel N. <email address hidden>"", posted Fri, 05th Oct 2018,
works fine for me, just changed the ./configure-option from defaults to ""--prefix=/usr --sysconfdir=/etc --localstatedir=/var""."
1785600,2018-12-15 21:40:01 UTC,"It can be fixed following the instructions in this answer:
https://askubuntu.com/questions/1029128/inverted-horizontal-scrolling-ubuntu-18-04#answer-1031657"
1785600,2018-08-21 07:32:41 UTC,"I couldn't think of too many applications in which I could trigger horizontal scrolling, but at least I've tried some different toolkits:"
1785600,2018-08-21 01:48:52 UTC,"Please also try some other apps (like Firefox), and list all those affected by the problem."
1785600,2018-12-15 21:27:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785600,2018-08-07 07:36:46 UTC,"No problem. I actually assumed it was still broken at first, since it used to be. But it was a pleasant surprise to find fully working."
1785600,2018-08-07 07:17:53 UTC,"@vanvugt Aaargh OK, on the one hand I knew that, on the other hand apparently my intuition is completely messed up. I don't know why that is, anyway, it seems to indeed work as intended. Sorry for bothering you."
1785600,2018-08-07 02:24:30 UTC,I've just tested this in 18.10 (Firefox) and natural scrolling is correctly applied to both vertical and horizontal movement.
1785600,2018-08-20 13:09:43 UTC,"@vanvugt Hmm OK, now I'm starting to doubt myself again. It might still be messed up, but when I move my fingers right, that means that content to the left of the view should move to the right, correct? And the scrollbar should move to the left? Because that's not happening, I think."
1785603,2018-09-12 07:09:34 UTC,"As a note, I managed working around it on Debian stretch (9.5) by choosing custom installation and then not selecting support for QT4 but support for QT5."
1785603,2020-07-08 11:04:02 UTC,PS. Sorry it's quite long- I just copied and pasted it straight from my terminal.
1785603,2020-07-08 11:03:04 UTC,Same for me- I get:
1785603,2019-07-03 18:38:46 UTC,That didn't change anything. Still the same error.
1785603,2018-09-13 18:58:33 UTC,"Hello, Thanks Ingo for the tipes.
It was not obvious this option was available
Yes it works"
1785603,2018-08-21 21:51:05 UTC,Also it seems to be a recurring problem of
1785603,2018-08-21 21:54:02 UTC,And also same story here https://bugs.launchpad.net/hplip/+bug/1719202
1785603,2018-08-10 15:31:51 UTC,"Frédéric - some feedback on how you are progressing with this issue would be useful. It seems a shame to have a nice, new printer and not have it working."
1785603,2018-08-06 13:24:23 UTC,"Hi Fred,"
1785603,2018-08-07 16:30:21 UTC,"Hi Frédéric,"
1785603,2018-08-07 12:38:19 UTC,"Hi,"
1785603,2018-08-07 10:42:35 UTC,"Hi Brian,"
1785603,2018-08-07 10:30:36 UTC,"Hi Srinivas,"
1785603,2018-08-06 17:23:08 UTC,One of the languages your printer deals in is PDF emulation. This makes it an ideal candidate for driverless printing on stretch. The question is - are you wedded to using HPLIP or do you just want to print?
1785603,2018-08-21 21:45:45 UTC,"Hello,"
1785608,2019-09-19 10:13:38 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1785608,2019-05-31 12:06:07 UTC,"Reviewed:  https://review.opendev.org/586252
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b4243ad3f72b3dc7ef5f291a85a3dd084d6c1c00
Submitter: Zuul
Branch:    master"
1785608,2019-01-31 23:31:51 UTC,"The spec for this RFE was merged recently, as can be seen in note #4 above. So marking the rfe as approved for consistency"
1785608,2019-01-19 00:04:33 UTC,"Reviewed:  https://review.openstack.org/619920
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=33d4d845f130ccb391f72d75b22906e9b6b38d75
Submitter: Zuul
Branch:    master"
1785608,2018-08-06 21:00:12 UTC,"@Miguel,"
1785608,2018-08-06 20:30:12 UTC,"@Moshe,"
1785608,2018-11-25 09:47:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619920"
1785614,2020-04-09 20:18:49 UTC,Can you provide an example file that triggers the crash?
1785615,2018-08-06 20:38:19 UTC,Is the action item for Neutron to make sure we use eventlet with the merged fix?
1785615,2018-08-07 06:52:58 UTC,"@Miguel yes. I requested a tag for eventlet and 0.24.1 contains the fix. I'll send a patch to test it out.
Thanks!"
1785615,2018-08-07 07:24:28 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/589385"
1785615,2020-06-24 10:36:29 UTC,Related patch: https://review.opendev.org/#/c/737651/
1785615,2019-04-16 08:51:43 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/589385
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1785619,2019-06-14 18:50:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785622,2019-01-27 09:41:29 UTC,"I've seen a couple of other applications which produce the message: Failed to load module ""topmenu-gtk-module"""
1785622,2018-08-07 19:22:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785622,2018-08-22 04:36:43 UTC,"I can confirm this issue. I also upgraded from 16.04 to 18.04 and instead of Dropbox icon I have now question mark without dropbox menu. I also can't start dropbox from application menu using command dbus-launch caja-dropbox start -i. It only starts with ~/bin/dropbox.py start command, which I found in another web page.
It is especially nasty because dropbox sent notification that only Ext4 will be supported starting with November and I have dropbox files on Ntfs partition and there is no way to  change settings without GUI. I  would be very thankful for recommendation on how to change dropbox settings in this situation."
1785622,2018-10-29 15:27:18 UTC,The problem is that 16.04 was on gtk 2 and 18.04.x is on gtk 3. I will mark this as invalid because there is no proper fix beside removing and reinstalling the dropbox applet.
1785622,2018-10-29 15:30:46 UTC,https://ubuntu-mate.community/t/problems-with-the-dropbox-icon-in-the-panel-um-18-04-1/17495/11?u=apolihronhere you will find a workaround.
1785625,2020-03-19 17:22:10 UTC,Closing because INVALID.
1785626,2018-08-08 18:03:40 UTC,"I decided to try to get more information. When plasmashell crashes, I can run Alt+F2 and start a Ksonsole session. During that session, I've tried to restart plasmashell at the prompt (it crashes again) and here is the output:"
1785626,2019-04-15 17:49:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785626,2018-08-08 17:34:26 UTC,Hello? Does anybody has any hint about this problem? Is there anything that I can do to help out?
1785629,2018-08-13 18:37:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785629,2018-10-25 09:29:01 UTC,"* -doc package: I think we should promote it as well in main, if the -dev is promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first is lynx, in universe, www-browser is a virtual package not fullfiled?). In addition, it ships the doc in devhelp format (despite symlink from doc/ to gtk-doc/).
I don't think anyway that those are needed, we don't tend to have -doc dep on a browser implementation.
* Same remark than for the other MIR: let's look at enabling the testsuite during build + autopkgtests
* Same kind of lintian warnings than for gupnp-dlna worths fixing or override + comments IMHO (gir-missing-typelib-dependency and typelib-package-name-does-not-match)"
1785629,2018-10-25 12:51:01 UTC,"Tests are actually ran during package build. So, good in that regard. Should it ran as autopkgtests though?"
1785629,2019-04-09 13:15:06 UTC,Let's turn those as incomplete to get off the list until we get over them again (probably next cycle).
1785629,2019-06-09 04:17:26 UTC,[Expired for gupnp-av (Ubuntu) because there has been no activity for 60 days.]
1785629,2019-09-11 15:14:36 UTC,+1 on the MIR side
1785633,2018-10-05 06:41:54 UTC,"This seems to have bit me again on Hyper-V, I can't see any output from the VM and it never seems to complete booting (which might be due to missing virtualized hardware support, TBD)."
1785633,2018-08-06 15:26:10 UTC,"Hey Saviq,"
1785633,2018-08-08 11:26:23 UTC,"FWIW the grub config has ""console=tty1"" instead of ""console=tty0"" - changing that gives me GRUB at least on the default console."
1785633,2018-08-08 11:43:08 UTC,"Just realized CONFIG_VT is disabled in the minimal kernel, so we won't get far with Mir on it :/"
1785634,2019-11-04 07:17:13 UTC,"Hello Ali,"
1785639,2019-04-09 14:04:59 UTC,This is happening to me aswell . PabloAB possible workaround worked for me.
1785639,2020-10-03 14:30:59 UTC,I have several debian 9 and 10 systems.  The debian 9 systems do not exhibit this problem however all of the debian 10 systems are affected.  The problem is specific to using non-numeric session names and a change at some point in tmux.  Numeric session names are properly culled when starting a new session however if the sessions are renamed to use non-numeric characters then the cull_zombies function no longer matches the zombies.
1785639,2019-03-14 01:59:04 UTC,To reproduce the bug:
1785639,2020-10-03 14:56:51 UTC,"There is another solution to this that prevents byobu from creating the temp sessions in the first place.  This solution has a behavior change for byobu that some users may not like.  Effectively this causes byobu to reattach to the exact same tmux session each time.  If you run one terminal session where you connect, do some work, disconnect, later reconnect, do some more work; then this change will work very well for you.  If you like to start byobu from multiple ""simultaneous"" terminal sessions and attach to the same byobu/tmux session then your terminal sessions will be mirrored; probably not what you wanted. My solution to this new behavior is to ensure that I always select ""create new session"" when starting byobu simultaneously from an additional terminal session."
1785639,2018-08-20 15:19:14 UTC,I am able to reproduce this using the steps described above.
1785639,2018-08-10 15:47:02 UTC,"> This is not the case on freshly created sessions, only after a while.
"
1785639,2019-03-11 18:22:31 UTC,Probably [this is the related AskUbuntu question][1]
1785639,2018-08-17 14:17:31 UTC,I'm getting the same issue.
1785639,2018-08-12 13:14:54 UTC,"Hmm, I'm not able to reproduce this..."
1785642,2018-08-06 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1785642,2018-08-06 15:07:30 UTC,"No logs are applicable, this is a packaging bug not a kernel bug. https://packages.ubuntu.com/cosmic/all/linux-tools-common/filelist may be used to confirm the report."
1785644,2019-07-23 07:24:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785644,2019-07-23 07:31:56 UTC,Good morning
1785647,2018-09-10 18:20:10 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1096.104
1785649,2019-06-09 04:17:27 UTC,[Expired for gupnp-dlna (Ubuntu) because there has been no activity for 60 days.]
1785649,2019-04-09 13:15:20 UTC,Let's turn those as incomplete to get off the list until we get over them again (probably next cycle).
1785649,2019-09-11 15:14:27 UTC,+1 on the MIR side
1785649,2018-10-25 12:50:49 UTC,"Tests are actually ran during package build (but one is skipped, as it needs a more complex setup). So, good in that regard. Should it ran as autopkgtests though?"
1785649,2018-11-27 16:34:21 UTC,"Thanks for the review, some of the fixes are commited now, also some tweaks still needed before upload (see question bellow)
https://salsa.debian.org/gnome-team/gupnp-dlna/commit/b161b805"
1785649,2018-08-13 18:35:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785649,2019-04-09 13:16:40 UTC,"on the autopkgtests question, I guess some for each components will be good to have a finer grained migration prevention. (even if those are testing the same thing, duplicated between packages)."
1785649,2018-10-24 15:07:41 UTC,"* -doc package: I think we should promote it as well in main, if the -dev is promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first is lynx, in universe, www-browser is a virtual package not fullfiled?). In addition, it ships the doc in devhelp format (despite symlink from doc/ to gtk-doc/).
I don't think anyway that those are needed, we don't tend to have -doc dep on a browser implementation.
* NEWS file has: 0.9.2 - Remove the old gupnp-dlna-1.1.pc.in file. / Remove gupnp and gstreamer-* dependencies from VAPI file generation. I think the build-dep on libgupnp-1.0-dev may thus be optional (only used for VAPI file, see ""Note to self"" below). Do you mind checking?
* Any progress on getting the usptream testsuite running during package build and autopkgtests?
* debian/copyright has some missing copyright notices:
Copyright: 2012-2013 Intel Corporation for instance in * as GPL-2.0+
I think that's the only missing one, but better to double check
* 2 of the 4 lintian warning worth fixing IMHO:
W: libgupnp-dlna-2.0-dev: gir-missing-typelib-dependency usr/share/gir-1.0/GUPnPDLNAGst-2.0.gir gir1.2-gupnpdlnagst-2.0 -> dep from the -dev on the gir*
W: gir1.2-gupnpdlna-2.0: typelib-package-name-does-not-match usr/lib/x86_64-linux-gnu/girepository-1.0/GUPnPDLNAGst-2.0.typelib gir1.2-gupnpdlnagst-2.0 <- this one worth only an override IMHO + an explanation."
1785653,2018-09-10 18:20:30 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1100.105
1785656,2018-08-06 18:11:32 UTC,From looking at the logs for the other dns test file:
1785656,2018-08-06 18:44:07 UTC,Proposed fix: https://review.openstack.org/#/c/589247
1785656,2018-08-06 18:46:42 UTC,Second fix proposed: https://review.openstack.org/#/c/589255
1785656,2018-08-06 18:48:50 UTC,"both fixes may work, ! we can verify both independently and landing both would be safer."
1785656,2018-08-07 04:35:38 UTC,"Change abandoned by Mike Kolesnik (<email address hidden>) on branch: master
Review: https://review.openstack.org/589202
Reason: Abandoned in favor of https://review.openstack.org/#/c/589247"
1785656,2018-08-07 04:58:07 UTC,"Reviewed:  https://review.openstack.org/589247
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=ff3bb29bc5b482639b721a93921149eb0c2baa2c
Submitter: Zuul
Branch:    master"
1785658,2018-08-06 16:21:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1785668,2018-10-12 21:25:08 UTC,"Indeed, I can see that the image verification code only executes when an image is downloaded from glance:"
1785668,2018-10-13 00:36:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/610189"
1785671,2018-08-16 20:38:24 UTC,Please report this issue on bugzilla.kernel.org and add <email address hidden> to the bug.
1785685,2018-08-07 06:11:48 UTC,Forcing users to select a file in a library directory would also limit the dialog to selecting only one library at a time.
1785685,2018-08-07 11:40:21 UTC,"Keep in mind, footprint libraries can be either a single file or a directory of files depending on the plugin type so any solution has to handle both conditions.  One option could be to have the plugin know it's file access type and use that to open either the native file dialog or the native folder dialog."
1785685,2018-08-06 21:23:12 UTC,"The selection idea would be possible, but then we'd just get bug reports that they selected the folder and Open was still disabled."
1785685,2018-08-06 19:52:57 UTC,This is unfortunate but it is because wxWidgets doesn't have a dialog that lets you select both directories (current library format) and files (legacy file formats).
1785685,2018-08-06 20:09:13 UTC,"It's rather the difference of implementation between the symbol library browser and the schematic library browser that's surprising, but I get the limitation...
Would it be possible to let the user select a file within that folder, and work back the folder path to include the complete library?
Alternatively, an ""Import Legacy Libraries..."" button would allow the user to select a file for that specific case."
1785686,2018-08-07 10:02:20 UTC,"I managed to create successful compressed dumps with trusty makedumpfile Version: 1.5.5-2ubuntu1.6, with both a linux-3.13.0-137 and a linux-3.13.0-85. That was on an amd64 kvm system."
1785686,2018-08-07 10:04:34 UTC,Can you try using the makedumpfile on trusty-backports?
1785686,2018-08-07 13:58:56 UTC,"For the record, Guilherme and I concluded that when dumping a kexec kernel, there may be leftover memory from the previous kernel which causes the dump to be corrupted. That was after I ran some tests that showed that when booting a 3.13.0-137, kexecing a 3.13.0-85, then dumping, the dump would contain 3.13.0-137 versions. And Guilherme confirmed that kexec was used to boot kernels once in a while during the tests."
1785686,2019-08-23 23:46:59 UTC,"Marking ""Won't Fix"" as trusty is ESM only now. Could as well be Invalid, though it's possible there is a bug dumping a kexeced kernel."
1785687,2018-08-14 02:46:11 UTC,"Hello,"
1785687,2019-09-17 09:37:17 UTC,"Hi,"
1785687,2019-11-17 04:17:34 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1785688,2018-08-06 19:54:27 UTC,not help https://download-installer.cdn.mozilla.net/pub/firefox/releases/61.0.1/win32/xpi/ru.xpi
1785711,2020-06-20 04:17:22 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1785711,2020-04-20 07:45:15 UTC,please update to .3 version
1785715,2018-08-07 10:40:25 UTC,Download them into same directory and run `sudo dpkg -i *deb`.
1785715,2018-08-07 11:49:21 UTC,"I did that and rebooted.
After i selected ubuntu in grub menu as usual i got the normal login screen. After logging in i only see a violet background and a mouse pointer. Hitting keys and moving mouse does nothing, but when i switch to TTY4 via ALT+f4 i can see a warning:
[ 368.068010] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:61]"
1785715,2018-08-08 20:24:40 UTC,"update: Even with the new kernel the problem still occurs (but it feels like they became more rare).
Today it appeared three times. Twice when closing the lid (in fact every time i closed it, if i remember correctly) and once while working (programming python)."
1785715,2018-08-07 11:57:04 UTC,"I just found out i can log into the graphical interface when i enter recovery mode root shell, then exit and resume normal boot. A weird but probably irrelevant thing is that the magnifying settings of text and icons seem to have resetted (but maybe that is because of the changes in your kernel)"
1785715,2018-08-23 08:47:20 UTC,Can you attach `lspci -vvnn`? I'd like to check the ASPM settings.
1785715,2018-10-26 16:27:33 UTC,"Just a few days ago i tried windows10 on the machine (more like a test run).
And strangely i encountered a similar (maybe the same) problem.
This time i noticed that i can provoke the problem by moving the laptop in some angles.
So i suspect that it might be a hardware problem (at least in part).
I just sent my Laptop to DELL for them to take a look."
1785715,2018-08-23 15:45:46 UTC,"Some of these show ""<access denied>"".
I dont see an edit option here, so i will just write another comment.
If i call this with sudo i get the full report here:"
1785715,2018-09-06 18:51:11 UTC,"Unfortunately i still couldnt get rid of the problem. Im still in the state where everything works fine as long as i do not close the lid or plug in AC adapter. Whenever i do that it reliably hangs and i cant do anything anymore (not change to another TTY or do any keyboard input, so i have to 7sec power-button-push to kill it). And still i cannot boot via my currently installed default kernel (hangs at login-screen), but have to enter root shell, exit it and then resume boot."
1785715,2018-10-25 07:54:13 UTC,Sorry for the late reply.
1785715,2018-08-07 07:16:29 UTC,Thank you Kai-Heng Feng for the quick response!
1785715,2019-05-10 15:26:59 UTC,Do you still see this bug?
1785715,2018-08-23 15:41:34 UTC,"Thank you for dedicating some of your time to this matter! :)
Here is the requested output:
revisor@revisor-XPS-15-9560:~$ lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
 Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1028:07be]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort+ <MAbort+ >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>"
1785715,2018-08-07 05:01:41 UTC,"Please test this kernel, it disables common clock on the NVMe."
1785715,2018-08-06 22:38:35 UTC,apport information
1785715,2018-08-06 22:38:42 UTC,apport information
1785715,2018-08-06 22:38:39 UTC,apport information
1785715,2018-08-06 22:38:37 UTC,apport information
1785715,2018-08-06 22:38:37 UTC,apport information
1785715,2018-08-06 22:38:34 UTC,apport information
1785715,2018-08-06 22:38:33 UTC,apport information
1785715,2018-08-06 22:38:32 UTC,apport information
1785715,2018-08-06 22:38:31 UTC,apport information
1785715,2018-08-06 22:38:29 UTC,apport information
1785715,2018-08-06 22:38:28 UTC,apport information
1785715,2018-08-06 22:38:26 UTC,apport information
1785715,2018-08-06 22:38:24 UTC,apport information
1785715,2018-08-06 22:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1785715,2018-08-06 22:38:44 UTC,apport information
1785715,2019-05-10 18:39:32 UTC,"Sorry, i forgot to report back. Thank you for asking."
1785718,2018-08-06 23:31:57 UTC,Interesting bug report.  Thanks.  I hadn't realized postfix didn't require HELO/EHLO by default:
1785718,2018-08-07 10:00:47 UTC,"Even if helo is set to required in postfix config, it is incorrect to rely only on helo entry.
Here an example: I manage a mail server at domain.com users received email with From:<email address hidden> and spammer entered test.com in helo (test.com do not have SPF DNS). Your perl script processed test.com from helo and seen no SPF record - neutral so it allows email from my domain.
If you check the from: header too this would not be possible."
1785720,2018-11-15 18:29:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785720,2018-11-15 18:36:26 UTC,Same problem on
1785723,2018-08-27 15:59:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785723,2018-08-30 15:44:56 UTC,"$ systemctl status systemd-journald
   Memory: 37.4M"
1785723,2020-05-05 11:43:26 UTC,"There was a recent fix which is eoan and later:
https://github.com/systemd/systemd/issues/11502"
1785723,2020-08-18 17:03:50 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1785724,2019-09-19 14:47:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1785731,2018-08-08 00:34:38 UTC,kernel-fixed-upstream
1785731,2018-08-07 01:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1785731,2018-08-07 15:03:32 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1785731,2018-08-07 15:31:52 UTC,"ok, I try that wen I go home from work and let you know.
tnx."
1785734,2018-08-07 20:26:34 UTC,"This is a part of a class of related problems for qemu linux-user, in that any non-atomic store is not validated before initiating a partial write."
1785735,2018-08-07 22:13:43 UTC,"Just to add some items that might be useful for someone, but please correct me if I'm wrong on any of this."
1785735,2020-09-14 20:29:12 UTC,"@Eric Miller
Hi,"
1785758,2019-09-16 13:58:40 UTC,Migrated to https://github.com/widelands/widelands/issues/2109
1785758,2018-08-08 08:44:23 UTC,"I'm not against switchable features, as long as their default value is intuitive."
1785758,2018-08-10 08:07:28 UTC,"I would not be against #5, but we're still having to many filesystem bugs around saving on Windows, so I'd be hesitant to touch it any more than needed at this point."
1785758,2018-08-08 06:23:20 UTC,Skipping autosave is also a good idea :-)
1785758,2018-08-07 16:06:24 UTC,"Although I understand the problem it tries to solve, I am against this feature in its current form. After the set amount of minutes without click, I would rather skip autosave instead of going to Pause."
1785758,2018-08-08 08:42:03 UTC,"@ypopezios:
the autopause feature should be a switchable option in the game options. If it is switchable would you still mind if this feature would be implemented? If so why?"
1785758,2018-08-08 18:58:11 UTC,"I'm basically in favor of ypopezios's suggestion, with an exception: only skip autosave when all autosave slots have been filled since the last named save for that scenario.  In other words, if it's (real clock time) 15 minutes per autosave and there are 4 autosave slots, the player plays for 20 active minutes after the last named save (one autosave already performed), the next 3 autosaves are made (at 10, 25 and 40 minutes of inactivity). After that point the game continues without autosaving."
1785761,2018-08-07 08:04:33 UTC,"I managed to activate NVIDIA driver instead of nouveau by adding ""blacklist=nouveau rdblacklist=nouveau"" to my kernel parameters."
1785761,2019-08-02 16:22:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785768,2018-09-20 07:46:34 UTC,I have encountered a similar issue with the Ubuntu installer.
1785768,2018-12-01 17:50:08 UTC,"I'm definitely seeing this bug at the moment, my issue arises when i have multiple router options , for example in isc-dhcp."
1785768,2019-03-25 12:13:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785768,2019-03-25 12:38:18 UTC,"This happens to me too - most of the time but not always. I can't identify why dhclient does DHCPDECLINE, the F4 log during installation doesn't have the reason. It is worth noting that my isc-dhcp-server log has warnings like these:"
1785780,2018-08-08 10:36:59 UTC,Please try the kernel in https://people.canonical.com/~khfeng/r8152-tb16-lp1785780/
1785780,2018-08-09 06:54:17 UTC,That fixed the issue. Thanks for help :]
1785780,2018-08-09 07:13:56 UTC,Is there a way to do the checksum turn off to be delivered f.e. through a kernel module which is able to check if it is necessary the change?
1785780,2018-08-10 13:50:23 UTC,`dmesg | grep TB16`
1785780,2018-08-17 12:13:39 UTC,Will this patch go in upstream Ubuntu Kernel or into Linux Kernel?
1785780,2018-08-08 09:00:01 UTC,"Ok, I think that's because the r8152's serial number on your TB16 is different:
E: ID_SERIAL=Realtek_USB_10_100_1000_LAN_000002000000"
1785780,2018-09-14 17:03:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1785780,2018-09-27 12:35:20 UTC,"Hi @ondrej-kolin,"
1785780,2018-10-01 17:15:35 UTC,This bug was fixed in the package linux - 4.15.0-36.39
1785780,2018-10-01 18:20:13 UTC,This bug was fixed in the package linux - 4.18.0-8.9
1785780,2019-02-14 16:44:52 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1785780,2018-08-20 04:44:33 UTC,Yes.
1785780,2018-08-08 08:35:39 UTC,apport information
1785780,2018-08-08 08:35:28 UTC,apport information
1785780,2018-08-08 08:35:37 UTC,apport information
1785780,2018-08-07 18:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1785780,2018-08-08 08:35:25 UTC,apport information
1785780,2018-08-08 08:35:26 UTC,apport information
1785780,2018-08-08 08:35:38 UTC,apport information
1785780,2018-08-08 08:35:29 UTC,apport information
1785780,2018-08-08 08:35:27 UTC,apport information
1785780,2018-08-08 08:35:32 UTC,apport information
1785780,2018-08-08 08:35:33 UTC,apport information
1785780,2018-08-08 08:35:34 UTC,apport information
1785780,2018-08-08 08:35:35 UTC,apport information
1785780,2018-08-08 08:35:36 UTC,apport information
1785780,2018-08-08 08:35:31 UTC,apport information
1785784,2018-08-07 09:27:02 UTC,"Review in progress for https://review.opencontrail.org/45341
Submitter: Parth Sarupria (<email address hidden>)"
1785784,2018-08-07 09:41:32 UTC,"Review in progress for https://review.opencontrail.org/45342
Submitter: Parth Sarupria (<email address hidden>)"
1785784,2018-08-10 19:43:34 UTC,"Reviewed:  https://review.opencontrail.org/45342
Committed: http://github.com/Juniper/contrail-controller/commit/bfe07a193df43ddbb4affced65c04e50b11252e2
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1785788,2018-08-21 12:04:37 UTC,"Hello,"
1785788,2018-08-07 15:30:27 UTC,"Hello,"
1785788,2018-08-21 09:08:31 UTC,"I've also just run into this bug - I hope to be able to test the upstream kernel on the client over the weekend, although the difficulty of triggering the bug on demand makes conclusive statements a bit tricky"
1785788,2018-08-07 15:32:06 UTC,"""current kernel"" -> ""latest bionic kernel"""
1785788,2018-08-07 11:05:32 UTC,"Hello,"
1785788,2018-08-07 10:30:07 UTC,This change was made by a bot.
1785788,2018-08-07 15:02:34 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1785791,2018-08-08 13:41:27 UTC,"my dpkg is stuck on the same or related problem. Sorry my clumsiness, never posted anything here before. In the attachment are infos of what I think is relevant. Hope you can get some info out of it."
1785791,2018-08-08 14:29:17 UTC,"sorry, these I forgot"
1785791,2018-08-11 20:18:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785791,2018-10-09 13:33:25 UTC,"Processing triggers for linux-image-4.15.0-30-generic (4.15.0-30.32) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-30-generic
/usr/sbin/mkinitramfs: 165: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/mkinitramfs: 65: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/mkinitramfs: 181: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/update-initramfs: 165: /usr/sbin/update-initramfs: Cannot fork
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
dpkg: error processing package linux-image-4.15.0-30-generic (--configure):
 installed linux-image-4.15.0-30-generic package post-installation script subprocess returned error exit status 1"
1785799,2018-08-07 11:16:50 UTC,"We have the upstream-centos-7 label defined in both the rdo-cloud and rdo-cloud-tripleo tenants [1]. I think this should not be the case, and proposed [2] with a fix."
1785799,2018-08-07 11:29:42 UTC,"This should be fixed, not limited to a single provider. As we plan for public openstack clouds (eg: vexxhost / ovh) we need to make sure these jobs are generic enough to be run on any cloud provider."
1785799,2018-08-07 11:30:23 UTC,"Based on pabelanger's comment in https://softwarefactory-project.io/r/13329, we should make it the other way around, and make sure we can run the job in different clouds (rdo-cloud and rdo-cloud-tripleo for now, others in the future)."
1785799,2018-08-08 12:15:46 UTC,Thanks Paul and Javier.
1785801,2019-09-05 09:57:18 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1785801,2019-11-05 04:17:34 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1785807,2018-08-07 11:33:59 UTC,KDE bug: https://bugs.kde.org/show_bug.cgi?id=351637
1785812,2020-04-27 23:00:25 UTC,"Next versions will not try to open luks, will just suggest user to decrypt."
1785812,2018-08-07 12:41:38 UTC,boot-info.log
1785812,2018-08-07 12:38:15 UTC,log with raids option
1785812,2018-08-25 21:50:01 UTC,"Thx Bougon for the report about LUKS.
Concerning the fact that boot-info should not use LVM in certain conditions, please can you open a new ticket ?"
1785813,2018-08-07 12:16:28 UTC,"The error message I get:
BadMatch (invalid parameter attributes)
Vim: Got X error
Vim: Finished."
1785819,2018-08-07 13:26:26 UTC,"StacktraceTop:
 g_assertion_message (domain=0x0, file=0x560f03dd569b ""../src/nautilus-directory.c"", line=841, func=0x560f03dd5ed0 <__func__.65580> ""add_to_hash_table"", message=0x7f8be8012910 ""assertion failed: (g_hash_table_lookup (directory->details->file_hash, name) == NULL)"") at ../../../../glib/gtestutils.c:2574
 g_assertion_message_expr () at ../../../../glib/gtestutils.c:2597
 add_to_hash_table (directory=0x560f0490b320, file=<optimized out>, node=0x560f0428e2c0) at ../src/nautilus-directory.c:840
 nautilus_directory_add_file (directory=0x560f0490b320, file=0x560f049693c0) at ../src/nautilus-directory.c:881
 nautilus_file_get_internal (location=location@entry=0x560f0426d260, create=create@entry=1) at ../src/nautilus-file.c:783"
1785819,2018-09-28 20:11:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785821,2019-07-06 23:46:06 UTC,"Howdy,"
1785826,2018-08-07 14:11:22 UTC,"StacktraceTop:
 dixLookupResourceByClass (result=result@entry=0x7ffcae75c5a0, id=id@entry=2097366, rclass=rclass@entry=4294967295, client=0x5568c5686850, mode=mode@entry=16) at ../../../../dix/resource.c:1240
 LegalNewID (id=2097366, client=client@entry=0x5568c6305a50) at ../../../../dix/resource.c:1183
 ProcCreatePixmap (client=0x5568c6305a50) at ../../../../dix/dispatch.c:1405
 Dispatch () at ../../../../dix/dispatch.c:479
 dix_main (argc=12, argv=0x7ffcae75c7b8, envp=<optimized out>) at ../../../../dix/main.c:287"
1785826,2018-09-17 14:07:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785826,2018-09-17 14:08:13 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/5406c377e8298f8db45325c279e7f40b0be7b891"
1785831,2018-08-07 14:26:43 UTC,"Note that this potentially a security issue, as I have found security sensitive screenshots in my Pictures folder.  Screenshots that I did not mean to take but are hanging around on my computer."
1785831,2018-08-07 14:27:07 UTC,"Also, I have a Debian desktop which does seem to implement the longer-keypress suggestion above."
1785831,2018-08-07 14:39:14 UTC,"I'm not convinced on making the prt-scr key have a delay on it, yet."
1785831,2018-08-07 15:15:47 UTC,e.g. the attached screenshot
1785839,2019-01-07 11:51:03 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: master
Review: https://review.openstack.org/589830
Reason: Marking this review as abandoned due to lack of activity in the past 6 months."
1785839,2018-08-08 11:51:46 UTC,"Change abandoned by Pedro Guimarães (<email address hidden>) on branch: master
Review: https://review.openstack.org/589853"
1785839,2018-08-08 07:35:31 UTC,"I can reproduce this issue by executing:
juju deploy <NEUTRON-API-CHARM> --series=bionic --config openstack-origin=""cloud:bionic-rocky"""
1785839,2018-08-08 10:12:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589830"
1785839,2018-08-07 15:19:26 UTC,"Thanks for reporting this bug Pedro. The problem is that the neutron.conf template hasn't been rendered yet, as can be seen by the database connection config:"
1785839,2018-08-08 11:43:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589853"
1785841,2018-08-08 02:30:20 UTC,"I imagine one of the purposes of cleaning time BP is resolving this issue.  The first usecase of the new feature comes from Ironic usecase, but basically it fixes this issue, too."
1785841,2018-08-08 02:32:05 UTC,"Oops, I mean we've already fixed the bug and don't need to care it."
1785841,2018-08-08 13:36:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589899"
1785841,2018-08-08 14:00:29 UTC,"Cleaning time would help, but it's not enabled by default. Please check my patch instead: it fixes other issues, such as running before_end_lease after start_lease has completed."
1785841,2018-09-10 21:02:31 UTC,I will push an updated patch.
1785845,2020-11-26 18:26:33 UTC,Thanks again @Norbert for saving the day! Confirmed it works in 20.20
1785845,2020-11-26 06:14:39 UTC,For 20.10 the solution is a bit longer
1785845,2020-05-01 14:11:51 UTC,@Norbert Thanks so much - looked everywhere for this.
1785845,2020-05-01 07:44:30 UTC,Issue on github - https://github.com/pixelb/fslint/issues/168
1785845,2020-04-30 20:34:35 UTC,Why isn't this available in Ubuntu 20.04? Is there a way I can install it?
1785845,2020-11-26 02:40:43 UTC,Is there a way to install this in Ubuntu 20.10? The method above for 20.04 does not work in 20.20.
1785851,2018-08-08 08:37:44 UTC,"Confirmed. This works with the deb package of libreoffice and thunderbird, but not with the snap.
It also works with the snap and evolution, so not sure this is a confinement problem (at least not one that cannot be overcome)."
1785853,2019-03-21 06:01:36 UTC,"As for me , I just remove the container named ""kubernetes-api"", and restack."
1785853,2021-02-03 09:29:22 UTC,This got fixed.
1785860,2018-08-07 20:22:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1785860,2018-11-04 18:03:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785860,2018-12-12 12:47:27 UTC,Thank you for your bug report. What session are you using? Could you make a screenshot of the sound settings screen you get?
1785860,2018-12-29 14:24:27 UTC,"Sorry for late response. Unfortunately I can't make a screenshot for you, because I've moved to  18.10 which doesn't have such problem."
1785860,2018-12-29 14:28:37 UTC,Just remembered that I've made the screenshot for this https://answers.launchpad.net/ubuntu/+question/668679 question! So there it is https://image.ibb.co/jD1UDn/over_amplification_problem.png
1785875,2018-08-07 21:12:54 UTC,"Fields are direct-edited in a grid in 5.1, which should largely alleviate this issue."
1785875,2019-01-09 20:50:00 UTC,"I think this bug been misunderstood.
What I ask it that all the software at least for eeschema, and pcbnew use the ""accelerate"" key to reduce move movement. And it still have not been apply on Version: (6.0.0-rc1-dev-1455-g4b7ef22ec), release build."
1785877,2018-08-07 23:14:40 UTC,"The modern toolset supports this in PCBNew, so it should be easy to add once we move EEschema to the new toolset."
1785881,2018-08-30 16:04:31 UTC,"I think fast grid by hot keys also better than nothing :-). But if the hot key for fast grid work ""faster"" if it work like holding a Ctrl, or Shift or whatever key to switch to that finer grid, and switch back to normal grid when key got released...."
1785881,2019-08-16 18:06:28 UTC,"@Seth
Alt key has side effects but AltGr acts as Alt key on wxWidgets and I did not see side effects."
1785881,2019-08-16 12:20:22 UTC,I think we need two wishlist items then:
1785881,2019-08-16 11:51:58 UTC,"@Jeff, the original report description mostly mentioned PCB items, but also some schematic items, so I changed the summary to be editor-agnostic (i.e. removed ""eeschema:""). Also, see the duplicates."
1785881,2019-08-16 11:23:05 UTC,"Don't knowing this bug I have written like the same bug (#1839342) but only about schematic.
I think that having automatically changed grids depending on moved object will be much more comfortable in use than having a grid modifying key.
After placing for example 10 symbols I have to move their values and references. So I will probably 20 times press 'M' key. If I would not to have to move my left hand also 20 times to press Ctrl+Shift and 20 times back to 'M' it would be much easier. May be others have it in their fingers, but for me move from 'M' to ""Ctrl+Shift"" or back means to have also a fast look at keyboard and then searching at screen where I was a moment before.
What is needed from my point of view is only to have an automatic separate grid (or no grid - like with Ctrl+Shift) for symbol values and references. Any other is so sporadic than can be done by modifying grid with context-menu.
The maximum needed I can imagine:
1. grid for symbols and wires and buses (I will use 50)
2. grid for references and values (I will use 1..5)
3. grid for other things (like texts) (I will use 50 for texts not directly connected with anything and probably 10 for texts like info about signals to be connected to socket pins - to be positioned at place I wont and to have easily them evenly spaced).
But I think spending a time to implement the point 3. is waste of time."
1785881,2019-08-15 18:52:15 UTC,@JP-
1785881,2019-08-15 18:08:39 UTC,"The Bug report is mainly related to placement items.
Perhaps the OP does not know the fact pressing alt key when moving the item disables the grid.
So no need to have alt grid for placement."
1785881,2018-08-30 14:23:34 UTC,I'm not sure tying a grid size to a schematic object type is a feature many users would use let alone the manpower required to implement.  Would a fast grid switching hotkey like we use in pcbnew be an acceptable alternative?  I find this to pretty handy when laying out boards and it sounds like a better solution for what you are requesting.
1785881,2019-08-15 15:16:13 UTC,"IIRC Altium only differentiates between components and non-components, but they have an interesting priority based system [1]."
1785881,2019-08-15 15:10:17 UTC,"Heres a screenshot from Mentor Graphics Xpedition, showing:
 - Part (footprints): Primary and secondary, accessible through a modifier key, mounting type or pin count threshold etc.
 - Route: can be split up between tracks and vias.
 - Other: Drawing (graphics, zones?), jumpers and test points."
1785881,2019-08-15 14:38:07 UTC,"I'm with Wayne here (from comment #1): I can't imagine people making use of something that complicated?  Do other packages really have this feature?  If so, I guess people must use it...."
1785881,2019-08-15 14:12:22 UTC,"I don't agree with that. Fast grid switching in Eeschema was a proposed work-around, which is not equivalent. Other EDA packages have multiple grids depending on what is being moved/what tool you're using, so I think this bug should be left as a Wishlist item for the original purpose (the heat is not insignificant after all)."
1785881,2019-04-15 16:21:16 UTC,"Hotkey switching between two pre-defined grid setting would do to me. I always and only use
- 50 mil for placing symbols and wires, and
- 5 mil to place/arrange texts (refs,values, footprints...)"
1785881,2019-08-15 15:41:01 UTC,"... but those are all for the PCB, not the schematic...."
1785882,2018-08-30 19:07:58 UTC,"Anyhow, with ${KIPPRJMOD} can be use to solve my current template issue in KiCad 5.0. And yes, I agreed that using relative paths is not a perfect solution for template. I had the ticket write in the knowledge of KiCad 4.0.7 not 5.0, and that is why I though relative path was a simplest solution for fixing the .pro files. Giving that, we still have problem with following case:"
1785882,2018-08-30 16:58:48 UTC,"Templates should include all custom libraries required so they get
copied to the newly created project folder.  You should not be just
creating project symbol and/or footprint library tables for templates
that point somewhere outside of the project.  This will never be
reliable.  If you are creating templates with custom libraries then you
should be using ${KIPRJMOD}/some_library.  ${KIPRJMOD} is always set to
the currently open project so as long as the libraries are somewhere in
the project path, this should work."
1785882,2018-08-30 16:10:12 UTC,"No, environment variable is nice to have, but it require user to set if correct for finding files where relative path is flexible, and not require/assuming the correctness of setting from environment. Again, if the template using global libraries everything fine without relative path, but if the template having it's own addition library files, or simulation files, or whatever file. Not of the environment setting going to be work except relative path."
1785882,2018-08-30 16:11:31 UTC,Please check #2 comment too.
1785882,2018-08-08 16:56:33 UTC,"Hi Jeff, I think your comment is belong to https://bugs.launchpad.net/kicad/+bug/1785879.
The new colum you mention meaning the checkbox for URL right? I think that also not bad to me."
1785882,2018-08-08 15:43:43 UTC,"I think that may solve part of my problem if I include library in template folder. But, I have a customize library that share across templates. Now copy into new project folder, without copy these customize global libraries would be much more sense? And most of the time, these customize global library location relative to the templates not the project going to be created. So using KICAD_USER_TEMPLATE_DIR may work too."
1785882,2018-08-07 20:55:43 UTC,"The `sym-lib-table`/`fp-lib-table` has some nice feature which could replace relative paths. If you place a library file inside the project folder you can use KIPRJMOD variable as a path. This special variable is always redefined to the current project path. So, it's easy to link project specific libraries regardless of the path where the project is located at the moment."
1785882,2018-08-30 14:27:53 UTC,"@NhatKhai, did Kerusey's suggestion resolve your issue?  It is the proper way to solve your problem."
1785882,2018-08-08 15:55:20 UTC,"I don't think my original idea of ""sniffing"" the field value is going to cut it."
1785885,2018-08-26 19:25:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785885,2018-08-26 19:26:34 UTC,+1
1785885,2018-10-09 11:16:55 UTC,"This seems to break Tilix's ""Save and restore window state"" preference - I have to set up my terminals after each login/reboot. Very annoying. I was under the impression this package was patched to fix the missing VTE PCRE2 functionality?"
1785888,2019-05-06 18:48:33 UTC,"Please ignore my previous comment.  I see I have confused prediction patterns with prediction pattern templates.  A prediction pattern template can be deleted in the above scenario, but a prediction pattern itself cannot.  Sorry for that mix-up."
1785888,2018-08-08 22:33:43 UTC,I was having this issue and brought to the attention of Equinox thinking there was a new permission I needed to access certain serial actions in the web client. Confirmed in 3.0.5.
1785888,2018-08-10 20:17:25 UTC,"I'll start a new bug for this if I can't find it elsewhere, but I found another serials-related permission that is not transferring to the web client. I cannot edit volume/item info for an issuance in the web client, but I can in xul. Most of the fields for the item (owning library, volume, classification, prefix, call number, suffix, copies, and part) are all grayed out. The only fields I can edit are Barcode and Copy #."
1785888,2018-08-13 17:12:20 UTC,"In the web client, prediction patterns can only be deleted if all the issues attached are in the ""expected"" state. Once an issue is received, the delete button becomes greyed out. I personally see it as a welcomed change. In the XUL client, deleting the prediction pattern also deleted attached issues/items. Removing the ability to delete the prediction pattern gives me less chance of accidently deleting my issues."
1785888,2018-08-30 20:32:52 UTC,"Holly,"
1785888,2019-05-06 16:37:01 UTC,"I am able to delete a prediction pattern from Serials Administration even if items generated from that pattern have been received.  This is contrary to what John noted above.  I've only recently been working with serials in the Web client, so I am not sure if this behavior has changed."
1785902,2018-08-08 05:39:53 UTC,Turned out that security_model=mapped can't cope with symlinks in the host file system.
1785912,2019-04-23 07:41:05 UTC,"(In reply to Mazin from comment #96)

> Nothing changed, I assume that work will be done here before the fix is
> pushed.
>
> @Marteen I also tried to build the kernel with ""constant_n = true;"" and the
> flickering is still there. I do know that a laptop with the same display
> panel (Dell xps 9370) works perfectly fine under Linux. The panel is
> manufactured by AUO and is the B133ZAN01.1.
"
1785912,2019-04-19 13:02:57 UTC,"Nothing changed, I assume that work will be done here before the fix is pushed."
1785912,2019-04-19 04:57:01 UTC,Did anyone check with the new kernel(5) in ubuntu 19.04?
1785912,2019-03-06 11:58:10 UTC,"@Maarten, any further help here?"
1785912,2019-03-03 08:21:29 UTC,i have the same problem - thinkpad x1 carbon model 16 gb
1785912,2019-03-01 12:15:55 UTC,@Maintainers
1785912,2019-02-05 11:40:57 UTC,"No, this is still an ongoing issue. Some people had luck with upgrading their BIOS, but me and many more still have the issue unfortunately."
1785912,2019-01-18 14:46:33 UTC,I've this very same problem. I'm using Ubuntu 18.04.
1785912,2019-01-22 01:41:34 UTC,"Sorry!
False alarm..."
1785912,2019-01-22 00:51:19 UTC,Hello All!
1785912,2018-12-04 18:23:30 UTC,"I have the same problem. Using Lenovo Ideapad 720s 4k screen, i7-8550U; Intel UHD Graphics 620
I have tried to install:
- Ubuntu 18.04.1
- Ubuntu 18.10
- Elementary OS 5.0
- Fedora (latest version)"
1785912,2018-11-29 02:50:30 UTC,Yup! me too. I have been running UEFI too and therefore do not think it is related to this!
1785912,2018-11-29 02:45:02 UTC,Dromichet I've been running UEFI only the whole time. I don't think this is related since turning on legacy support also breaks windows for me and linux doesn't get fixed on either UEFI/Legacy. Plus even the symptoms you were having are different.
1785912,2018-11-29 00:52:56 UTC,Hello again.
1785912,2018-11-27 08:50:38 UTC,"Boot kubuntu 18.10 from legacy mode (MBR) - screen flicker, boot from EFI - no screen fliker."
1785912,2019-02-05 10:58:57 UTC,"Hi,
Was this issue resolved for anyone. I moved to kernel `Linux 4.20.6-042006-generic` and use `i915.fastboot=1` in my grub options but ubuntu 18.04 still flickers when it wakes up after lock or sleep.
The above options do prevent it from flickering from the start but only after it has once gone to sleep (display turned off).
Any help with this would be greatly appreciated."
1785912,2019-05-05 21:37:22 UTC,"Ignore what I said earlier, the xps 13 model that uses the same panel is the xps 13 9380, and it seems to exhibit the same sort of flicker issue according to Bug 110511. Sorry!"
1785912,2019-05-28 08:04:15 UTC,"Working (fastset at boot):
[    3.494890] [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m: 6213395, gmch_n: 8388608, link_m: 517782, link_n: 524288, tu: 64"
1785912,2019-05-28 06:33:58 UTC,"@Stan/Maarten, can you help here? Any further suggestions?"
1785912,2019-11-29 17:54:45 UTC,-- GitLab Migration Automatic Message --
1785912,2019-10-23 14:05:41 UTC,"Another idea
https://github.com/vsyrjala/linux/commit/9bfe76d15704a680559d573d00d074a47eea764d"
1785912,2019-10-23 12:31:26 UTC,"Same issue with Ideapad 720s tested with the latest Ubuntu 19.10. I don't get flashing on boot, but when the computer wakes up from sleep mode it starts flashing and after 1 min or 2 the computer hangs."
1785912,2019-10-22 20:26:33 UTC,"I tried kernel 5.3.7, screen still exhibits the same issue with flickering on lenovo ideapad 720s 13ikb."
1785912,2019-10-22 19:05:43 UTC,"commit f0521558a2a8 (""drm/i915: Don't clobber M/N values during fastset check"") may have helped here."
1785912,2019-10-22 18:48:18 UTC,"(In reply to Lakshmi from comment #107)

> (In reply to Ashish Maknikar from comment #106)
> > I am having the same flickering problem with my Asus.Kernel is Kernel Linux
> > 5.0.0-29-generic x86_64. I have a dual boot with windows where the problem
> > is occurring as well. The flickering in windows lowers down (but does not
> > stop) from insane levels if I disable the Intel graphics in display adapters
> > option in Device manager. Any comments?
>
> Can you verify the issue with drmtip (https://cgit.freedesktop.org/drm-tip)
> and attach the dmesg from boot with kernel parameters drm.debug=0x1e
> log_buf_len=4M?
"
1785912,2019-10-02 07:47:44 UTC,"(In reply to Ashish Maknikar from comment #106)

> I am having the same flickering problem with my Asus.Kernel is Kernel Linux
> 5.0.0-29-generic x86_64. I have a dual boot with windows where the problem
> is occurring as well. The flickering in windows lowers down (but does not
> stop) from insane levels if I disable the Intel graphics in display adapters
> option in Device manager. Any comments?
"
1785912,2019-10-02 01:35:39 UTC,I am having the same flickering problem with my Asus.Kernel is Kernel Linux 5.0.0-29-generic x86_64. I have a dual boot with windows where the problem is occurring as well. The flickering in windows lowers down (but does not stop) from insane levels if I disable the Intel graphics in display adapters option in Device manager. Any comments?
1785912,2019-09-29 11:41:52 UTC,"Hey guys ,
Ive got the same flickering issue in both windows and ubuntu. Disabling the Intel UHD grapics in windows slows down the flickering from insane to a lot. Meanwhile the flickering is there in ubuntu as well but it suddenly stops after around 3-5 minutes of usage. Laptop is ASUS K501UW-ab78."
1785912,2019-09-05 17:37:48 UTC,Hi All
1785912,2019-08-27 09:13:10 UTC,"Maarten, what are the next steps?"
1785912,2019-08-15 04:47:59 UTC,"Does kernel parameter ""i915.enable_psr=0"" help?"
1785912,2019-08-14 14:44:17 UTC,"I am using ASUS GL704GW laptop(intel UHD 630/RTX 2070) with ubuntu 18.04/Elementary OS 5/Mint 19.2/MX Linux 18.3.
Same flickering problem.
I noticed that the bug has been confirmed almost a year now. Will it be fixed or not?"
1785912,2019-05-29 08:48:29 UTC,"Oh well, worth a shot."
1785912,2019-05-28 18:22:47 UTC,"Same thing happens to me, drops to the exact same wrong modeset after changing the bool value."
1785912,2019-05-28 17:57:48 UTC,"Created attachment 144365
dmesg with constant_n forced true"
1785912,2018-11-27 07:43:00 UTC,"(In reply to Yugge from comment #83)

> (In reply to Dmitry from comment #81)
> > Lenovo 720s-13IKS 81A8000SRK. Update to latest BIOS (5SSCN34WW to 5SCN38WW)
> > fix the problem for me. Ubuntu 18.10.
>
> Was interested to see if it was indeed a bios issue for my Lenovo 720s-13IKB
> 81BV so I updated the bios to 6MCN28WW. The issue still remained,
> unfortunately. Just to confirmed, that model is the UHD version right?
"
1785912,2019-05-28 05:59:06 UTC,"Created attachment 144358
dmesg from 5.1.4-arch1-1-ARCH with drm.debug=14"
1785912,2018-11-26 22:55:05 UTC,"(In reply to Dmitry from comment #81)

> Lenovo 720s-13IKS 81A8000SRK. Update to latest BIOS (5SSCN34WW to 5SCN38WW)
> fix the problem for me. Ubuntu 18.10.
"
1785912,2018-11-22 23:24:39 UTC,"This is a display DP bug then, probably needs some quirk to work correctly. :)"
1785912,2018-11-25 08:13:56 UTC,Lenovo 720s-13IKS 81A8000SRK. Update to latest BIOS (5SSCN34WW to 5SCN38WW) fix the problem for me. Ubuntu 18.10.
1785912,2018-10-04 10:38:21 UTC,This is also happening on the 8250U version of the ideapad 720s. I can attach logs if you would find them helpful.
1785912,2018-10-04 07:11:25 UTC,"(In reply to Joe from comment #6)

> Ok apparently I'm a noob, I can't get drm-tip to install and I have no clue
> where to add the config statements. Any help would be appreciated.
>
> Joe
"
1785912,2018-10-04 04:33:59 UTC,Ok so the only thing I couldn't figure out is install drm-tip. So unfortunately I was not able to get the dmesg after drm-tip.
1785912,2018-10-04 04:31:29 UTC,"Created attachment 141868
dmesg after drm changes"
1785912,2018-10-04 04:17:38 UTC,"Created attachment 141867
cat /sys/kernel/debug/dri/0/i915_edp_psr_status"
1785912,2018-10-04 04:05:03 UTC,"Ok apparently I'm a noob, I can't get drm-tip to install and I have no clue where to add the config statements. Any help would be appreciated."
1785912,2018-10-03 12:53:56 UTC,"Jani & Lakshmi,"
1785912,2018-10-04 11:16:36 UTC,"Mazin,Can you also elaborate the issue, to ensure its the same bug.
Have you verified with latest drm-tip?
You can attach the dmesg with kernel parameters drm.debug=0x1e log_buf_len=4M from boot."
1785912,2018-10-03 12:02:50 UTC,"For starters, full dmesg with drm.debug=14 on whichever kernel you're running will be helpful, but be prepared to try drm-tip too."
1785912,2018-10-03 07:04:12 UTC,"Joe, In order to debug the issue, following information will be useful
cat /sys/kernel/debug/dri/0/i915_edp_psr_status"
1785912,2018-10-03 06:48:47 UTC,"Joe, Can you please try to reproduce the issue using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot."
1785912,2018-10-02 15:43:17 UTC,"Created attachment 141835
Glitch."
1785912,2018-09-07 05:30:14 UTC,This change was made by a bot.
1785912,2018-09-07 05:03:20 UTC,"you may try drm-next or drm-intel-next from the mainline kernels ppa, but if those won't help then you'd better file a bug upstream at bugs.freedesktop.org (DRI -- drm/intel)"
1785912,2018-08-13 17:43:32 UTC,Tried mainline kernel 4.18 and it didn't help: the flickering looks the same to me.
1785912,2018-08-07 23:05:42 UTC,The machine is newly installed so I can try things out without too much stress if it helps.
1785912,2018-10-03 07:18:45 UTC,*** Bug 108138 has been marked as a duplicate of this bug. ***
1785912,2018-11-25 10:08:58 UTC,"(In reply to Mridul from comment #80)

> (In reply to Yugge from comment #78)
> > @Maarten Lankhorst - Verified, forcing constant_n to true does solve the
> > issue and let me restore from suspend without flickering!
>
> Will I have to build the drivers from source? Is this documented somewhere
> (how to build it from source)?
>
> Also, is this the final fix? forcing it to true?
"
1785912,2018-10-04 19:52:13 UTC,"(In reply to Lakshmi from comment #10)

> (In reply to Joe from comment #6)
> > Ok apparently I'm a noob, I can't get drm-tip to install and I have no clue
> > where to add the config statements. Any help would be appreciated.
> >
> > Joe
>
> Joe, go to grub file under /etc/default and edit like below
> Grub-cmdline-linux-default = “quiet splash drm.debug=0x1e log_buf_len=4M”
"
1785912,2018-10-04 20:15:28 UTC,"Team,"
1785912,2018-11-23 21:48:48 UTC,"(In reply to Yugge from comment #78)

> @Maarten Lankhorst - Verified, forcing constant_n to true does solve the
> issue and let me restore from suspend without flickering!
"
1785912,2018-11-17 11:16:55 UTC,"Same here.
Ubuntu 18.04, just installed on Razer Blade Stealth. With this flicker it's just impossible to use it. Crap..."
1785912,2018-11-10 21:42:38 UTC,"Similar bug, simlar hardware, in the freedesktop.org system here:
https://bugs.freedesktop.org/show_bug.cgi?id=108132"
1785912,2018-11-06 07:44:53 UTC,Sadly not!  The slightly older model (also 4k but older rev) worked fine with the standard install so my intention is to use that (long story but it has windows only at the moment).  Really I wanted the newer 4-core one running linux but I couldn't justify the time investigating.
1785912,2018-11-06 06:09:06 UTC,"I have Lenovo Ideapad 720s 4k screen, i7-8550U; UHD Graphics 620 (Kabylake GT2) and I am facing the exact same issue in it. The issue is deep rooted, as I have tried fedora, Mint, etc and there is simply no escape. But it works perfectly on a windows machine."
1785912,2018-10-09 12:04:32 UTC,"Lakshmi,"
1785912,2018-10-09 03:34:39 UTC,"Created attachment 141947
dmesg4.txt"
1785912,2018-10-04 19:52:42 UTC,"Created attachment 141902
dmesg2.txt"
1785912,2018-10-09 03:32:11 UTC,"(In reply to Lakshmi from comment #22)

>
> > What would you like me to try?
> Try to reproduce the issue with latest kernel with kernel parameters
> drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full
> dmesg from boot.
"
1785912,2018-10-08 22:07:08 UTC,"Created attachment 141943
Kernel 4.19 before flickering stops"
1785912,2018-10-08 20:00:07 UTC,"> What would you like me to try?
Try to reproduce the issue with latest kernel with kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot.
"
1785912,2018-10-08 14:55:49 UTC,"(In reply to Lakshmi from comment #20)

> Joe, if not with latest drm-tip, can you try with latest mainline kernel.
"
1785912,2018-10-08 13:42:49 UTC,"Joe, if not with latest drm-tip, can you try with latest mainline kernel."
1785912,2018-10-08 02:02:19 UTC,Any Luck Team?
1785912,2018-10-05 03:41:19 UTC,"Created attachment 141906
grub"
1785912,2018-10-05 03:40:19 UTC,"Created attachment 141905
dmesg3.txt"
1785912,2018-10-08 22:07:58 UTC,"Created attachment 141944
flickering stopped"
1785912,2018-10-05 03:39:42 UTC,Looks like my changes did not take I reviewed the dmesg and noticed it loaded the i915. I attached dmesg3.txt with the changes. Also note that I change the grub and still the changed didn't take. I have attached the grub file as well so you can see my changes.
1785927,2018-08-08 04:01:54 UTC,Could this new policy for obtaining tokens to enable posting to Facebook be relevant?
1785937,2018-08-08 16:13:33 UTC,Please see https://bugs.launchpad.net/bugs/1687404.
1785941,2018-08-08 04:22:16 UTC,You can place text fields in the symbol editor with horizontal/vertical orientation.
1785941,2019-09-26 11:27:32 UTC,"It's just ridiculous that someone is seriously discussing if name and number rotation is required or not.. Common,  this is just a BASIC editor functionality, this is must be in kicad."
1785941,2019-09-05 03:39:14 UTC,As per Wayne this horizontal text on vertical pins featur is already part of the new file format.
1785941,2018-08-08 12:07:15 UTC,"On 08/07/2018 11:23 PM, Bob Cousins wrote:

> ** Attachment added: ""Capture.PNG""
>     https://bugs.launchpad.net/kicad/+bug/1785941/+attachment/5172828/+files/Capture.PNG
>


You're right, that already does what I need to do, thanks!"
1785941,2018-08-14 14:16:49 UTC,"On 08/14/2018 08:56 AM, Maciej Suminski wrote:

> I realize you are asking for something else, but you should be able to
> edit properties of a symbol text field and toggle its ""Common to all
> units"" property.
>


I didn't realize I could do that, and you're right, it /can/ be used as
a workaround for my multipart issue."
1785941,2018-08-14 13:56:57 UTC,"I realize you are asking for something else, but you should be able to edit properties of a symbol text field and toggle its ""Common to all units"" property."
1785941,2018-08-14 12:51:23 UTC,"It turns out that the the workaround of using simple text for the pin names, rather than displaying the pin names themselves, works only for some cases of interest, and not for all of them."
1785941,2019-09-04 14:44:39 UTC,Another user asked for this in the forum: https://forum.kicad.info/t/rotate-pin-number-and-pin-description/17990. Maybe this could be considered for the new file format?
1785943,2018-11-28 01:26:16 UTC,https://bugs.launchpad.net/python-zvm-sdk/+bug/1792518
1785946,2019-08-13 20:23:13 UTC,should be good now!
1785946,2019-10-13 04:26:28 UTC,[Expired for scons (Ubuntu) because there has been no activity for 60 days.]
1785947,2018-08-08 11:20:34 UTC,"I'm not sure what exactly the author intended to do with ""get_default"" function in the drivers.
I think maybe we should change the code where the driver's function is called."
1785947,2018-08-08 07:17:57 UTC,"Hi Deepak, if it is indeed a bug, then we have to fix it and add some tests for the code  I think :)
Or maybe we can just remove this part if is really usless."
1785947,2018-08-08 10:10:52 UTC,I believe updating it to parent_id would be sufficient. What do you think?
1785947,2018-08-08 06:47:14 UTC,"Hi Yang, So do you want to write a test for this also or just change in the get_default method.?"
1785949,2018-08-08 21:20:51 UTC,Both ways should work. The context menu as well as the slow double click.
1785952,2018-08-08 17:28:41 UTC,"This is actually just a bug in the +members page.  It isn't a security bug because its overall effect is to forbid access to some information that ought to be permitted, rather than the other way round."
1785952,2018-08-08 21:11:27 UTC,"Huh, I've clearly paged a lot out, since private teams in public teams isn't making sense to my head now.
Teams with private membership in public teams - sure. But an invisible way to grant access to bugs etc... hmmm"
1785952,2018-08-08 21:43:05 UTC,"That was my initial reaction, but since the LimitedView security adapter for teams arranges that members of superteams can see that the subteams exist, I think it's not quite as bad as all that."
1785962,2018-08-08 14:10:35 UTC,This issue was fixed in the openstack/watcher 1.12.0 release.
1785964,2019-01-15 12:07:36 UTC,"I have integrated graphics Intel HD4600 (Haswell) and discrete Nvidia GTX750M as well, which is managed by the Nvidia binary blob (the nouveau module is blacklisted) but usually disabled. I also have an external monitor always plugged in while at home, and nothing elsewhere. Unfortunately the bug happens in every situation. I have to say, though, that the frequency has been going down, I haven't experienced it in the last ~10 days and I am not sure why, as my usage pattern (physical places, networks, monitors, etc...) is always the same."
1785964,2019-02-07 04:31:27 UTC,"Hi all,
can you cross check if you have any of these Gnome Shell plug-ins installed ?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813248/comments/10"
1785964,2019-02-07 04:32:42 UTC,Also I did a lot of docking and unlocking (I've got 3 screen setup - built-in and two external monitors)
1785964,2019-02-16 19:37:05 UTC,Had this with nvidia graphics drivers after installing and then removing proprietary drivers downloaded from nvidia website. I could not log in at all at first boot.
1785964,2019-02-16 19:41:32 UTC,nvidia-xconfig -generated xorg.conf looked like this https://paste.ubuntu.com/p/4hRVzHmbJV/
1785964,2019-05-20 15:47:29 UTC,"Dell Precision 5520 freeze cuz of Nvidia confirmed.
`sudo apt purge 'nvidia*'` solved it. Let's see what happens after I install it again."
1785964,2019-05-20 15:56:50 UTC,"`sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bckp`
`sudo apt install nvidia-driver-<version>` (check in GUI ""Additional Drivers"", mine is `430`)
everything works. Even the screen layout wasn't broken."
1785964,2019-07-03 22:04:51 UTC,Have the same issue for quite some time. Couldn't find any pattern yet. Also have the impression gdm is waiting for something. It happens for me when I am on Ethnernet as well when on wifi.
1785964,2019-07-05 13:42:20 UTC,It seems it's the Gnome extension GSConnect (https://extensions.gnome.org/extension/1319/gsconnect/) in my case. Removed that and had no freezes since. Will examine further.
1785964,2019-07-06 16:58:19 UTC,"Ok, very weird. Removing just GSConnect (**) didn't help after all. I also had to remove:
gnome-shell-extension-multi-monitors (*)
No topleft hot corner (**)"
1785964,2019-07-08 08:20:22 UTC,Still weird. The only Gnome extensions active are the follwoing ones from the Ubuntu repository:
1785964,2019-07-13 23:32:45 UTC,S2 instead of S3 didn't resolve the freezing too - took some time for the freezing to occur again. I stumbled across autofs and quick tests suggest with autofs turned off the freezing is gone.
1785964,2019-07-15 10:23:35 UTC,"I added a systemd unit to stop autofs before going into suspend and start autofs again after resume. I haven't had any freezes with gdm3 anymore. But there is still a difference between Ethernet and Wifi. When connected to Wifi, it takes some seconds longer to unlock the user session. It seems gdm3 is waiting for an active network sonnection."
1785964,2019-01-15 08:24:41 UTC,"        *-display
             description: VGA compatible controller
             produit: Skylake GT2 [HD Graphics 520]
             fabriquant: Intel Corporation
             identifiant matériel: 2
             information bus: pci@0000:00:02.0
             version: 07
             bits: 64 bits
             horloge: 33MHz
             fonctionnalités: pciexpress msi pm vga_controller bus_master cap_list rom
             configuration: driver=i915 latency=0
             ressources: irq:125 mémoire:de000000-deffffff mémoire:c0000000-cfffffff portE/S:f000(ta
ille=64) mémoire:c0000-dffff"
1785964,2019-07-04 17:46:53 UTC,"I had the following gnome extensions installed:
GSConnect
gnome-shell-extension-multi-monitors
gnome-shell-extension-system-monitor
gnome-shell-extension-caffeine
gnome-shell-extension-disconnect-wifi
gnome-shell-extension-shortcuts
gnome-shell-extension-top-icons-plus
gnome-shell-extension-ubuntu-dock
gnome-shell-extension-weather"
1785964,2019-01-15 05:02:11 UTC,Intel HD Graphics 520 - Internal
1785964,2019-01-04 13:03:05 UTC,"I have some new information: the bug is still happening as before, today I resumed my session and the login screen got stuck as usual; I left it there for a couple of minutes, then I unplugged and replugged the ethernet cable and, as soon as the network was up again, the session was unlocked! Maybe this can be helpful to understand the bug..."
1785964,2019-01-06 21:45:53 UTC,"Thanks Diego. A similar situation here today. The whole Christmas season at home no issues at all - many suspends (lid close), with and without power supply. Coming today to the office, boom, unlock screen freeze after providing the password."
1785964,2018-08-08 11:15:01 UTC,"This just happened again, with the same HW config."
1785964,2018-08-08 11:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1785964,2018-08-09 16:51:54 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1785964,2018-08-10 07:00:40 UTC,"I tried to reproduce this today on 4.15 with only one successful attempt,
however I haven't figure what's the correct combination to make this fail."
1785964,2018-09-20 19:54:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785964,2018-09-21 08:52:05 UTC,"This bug happened to me a number of times as well, on a fresh install of Ubuntu 18.04.1 on a Clevo W230ST (Intel Haswell, nvidia Optimus); it never happened after a lock screen but only after a suspend/resume; the nvidia proprietary drivers 396 are installed but not loaded, as I am using the Intel integrated graphics; the nouveau module is blacklisted. I attach the relevant syslog."
1785964,2018-10-23 08:33:59 UTC,"Hi all,"
1785964,2018-10-25 14:11:57 UTC,"I have the same bug here, and it's been quite a long time. It comes from time to time. After a while logins happens, but sometimes it's after a really long time !"
1785964,2018-10-28 10:30:17 UTC,"Hello again all,"
1785964,2018-10-28 20:20:58 UTC,"@grzesiekc thanks for the comment, on my side I have no such specific content."
1785964,2018-10-31 23:53:20 UTC,"Well you can disregard #14, happened again."
1785964,2018-11-01 17:43:22 UTC,"@grzesiekC, on my side, I quite frequently do the same (connecting / reconnecting), I will try to pay attention, to see if it's correlated."
1785964,2018-11-27 09:42:39 UTC,"I got the issue, today while using sudo (to use bindfs), just after I typed my password, whole gnome got blocked (the mouse cursor moving but without changing shape and being unable to type, neither have any action on any window or program), but I could log in a new tty console. Note also that this was during an internet downtime."
1785964,2018-08-08 06:43:34 UTC,"I think 13:69 is /dev/input/event5, which is your:"
1785964,2019-01-04 14:14:17 UTC,"Thanks Diego for the information, I also got the feeling that the bug is linked to logind waiting for something from the network or usb (not sure)."
1785964,2018-08-08 08:14:22 UTC,"Hello Daniel,"
1785964,2019-01-15 04:55:33 UTC,Is all the affected one's have external graphics card and made any switch from external to integrated or from external to integrated then back or any kind of switch between external and integrated Graphics Cards?
1785969,2020-02-11 10:47:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785969,2018-08-08 06:42:11 UTC,"StacktraceTop:
 ?? ()
 getX11InputMethodData (env=0x7fb5f44b6a00, imInstance=0x0) at ./src/java.desktop/unix/native/libawt_xawt/awt/awt_InputMethod.c:314
 _XimServerDestroy (im_2_destroy=<optimized out>) at ../../../../modules/im/ximcp/imInt.c:106
 _XimFilterServerDestroy (d=<optimized out>, w=<optimized out>, ev=<optimized out>, client_data=<optimized out>) at ../../../../modules/im/ximcp/imDefFlt.c:374
 Java_sun_awt_X11_XlibWrapper_XFilterEvent (env=<optimized out>, clazz=<optimized out>, ptr=<optimized out>, window=<optimized out>) at ./src/java.desktop/unix/native/libawt_xawt/xawt/XlibWrapper.c:673"
1785980,2018-08-09 07:02:11 UTC,"Hi,"
1785980,2018-08-10 08:19:47 UTC,"Hi, this is not a duplicate. in # 1771021 we are talking about aliases and several IPs. I wrote about the lack of possibility to change the IP source in the route."
1785980,2018-08-10 08:39:22 UTC,"Oh ok, I have unmarked it."
1785982,2018-08-15 14:11:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1785985,2019-10-09 00:34:36 UTC,"Reviewed:  https://reviews.mahara.org/10280
Committed: https://git.mahara.org/mahara/mahara/commit/8e7a3135a1c866ce6856b95da19f9355d331c0ef
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1785985,2019-10-09 00:34:37 UTC,"Reviewed:  https://reviews.mahara.org/9401
Committed: https://git.mahara.org/mahara/mahara/commit/00d4372518ae2e7b8e97d9cecce13526a9294f37
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1785985,2019-10-09 00:34:36 UTC,"Reviewed:  https://reviews.mahara.org/9710
Committed: https://git.mahara.org/mahara/mahara/commit/68b575088d834216157918d57f192e90da62beff
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1785985,2019-10-31 00:58:19 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10545"
1785985,2019-10-31 01:30:44 UTC,"Reviewed:  https://reviews.mahara.org/10546
Committed: https://git.mahara.org/mahara/mahara/commit/62cda412d0d72d92bd7786d401d51ac897a37029
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1785985,2019-10-31 01:30:36 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10546"
1785985,2019-10-31 03:00:37 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10547"
1785985,2019-10-31 03:02:23 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10548"
1785985,2019-10-31 03:02:32 UTC,"Reviewed:  https://reviews.mahara.org/10548
Committed: https://git.mahara.org/mahara/mahara/commit/098699bc57f1aa1c925c5f25dee1c142c63eda9e
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1785985,2019-10-31 01:30:30 UTC,"Reviewed:  https://reviews.mahara.org/10545
Committed: https://git.mahara.org/mahara/mahara/commit/9be8c499a0a373e8742ae5dbcea177a088596715
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1785985,2019-08-30 02:02:25 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10280"
1785985,2019-10-31 03:02:38 UTC,"Reviewed:  https://reviews.mahara.org/10547
Committed: https://git.mahara.org/mahara/mahara/commit/fabcf2bd29a38aecd49965766bfe1fd21c6b7d17
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1785985,2019-06-21 01:11:13 UTC,"Reviewed:  https://reviews.mahara.org/10023
Committed: https://git.mahara.org/mahara/mahara/commit/6c6bbc2526e4cde55c4dfab0f2eaa5411105c0e5
Submitter: Robert Lyon (<email address hidden>)
Branch:    18.10_STABLE"
1785985,2018-12-12 08:42:36 UTC,I'd certainly be in favour of removing triggers.  We run Mahara on MySQL and have experienced a number of issues over the years with the DB layer.  Transactions were disabled in MySQL (see https://bugs.launchpad.net/mahara/+bug/1514608) to help alleviate the issues.
1785985,2019-02-23 20:03:57 UTC,See https://reviews.mahara.org/#/c/9401/ for the patch for Elasticsearch
1785985,2019-04-05 00:59:38 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9710"
1785985,2018-12-12 01:32:50 UTC,"Hi all,
These triggers are causing db dumps to fail (in progresql) due to triggers being constantly deleted and created."
1785985,2019-05-15 21:49:16 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10018"
1785985,2019-06-21 01:15:41 UTC,"Reviewed:  https://reviews.mahara.org/10022
Committed: https://git.mahara.org/mahara/mahara/commit/a2f72b46ae62d107f2db9af3ddb55f9ea028f0c3
Submitter: Robert Lyon (<email address hidden>)
Branch:    18.04_STABLE"
1785985,2019-05-16 20:22:51 UTC,"Patch for ""18.04_STABLE"" branch: https://reviews.mahara.org/10022"
1785985,2019-05-16 20:25:48 UTC,"Patch for ""18.10_STABLE"" branch: https://reviews.mahara.org/10023"
1785985,2019-05-16 20:34:16 UTC,"Patch for ""19.04_STABLE"" branch: https://reviews.mahara.org/10024"
1785985,2019-06-04 00:01:36 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10065"
1785985,2019-06-21 01:07:38 UTC,"Reviewed:  https://reviews.mahara.org/10024
Committed: https://git.mahara.org/mahara/mahara/commit/4c620d4d4a93771ddf4932c1a8b34d9aa26fcdad
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.04_STABLE"
1785985,2019-05-16 20:14:24 UTC,"Reviewed:  https://reviews.mahara.org/10018
Committed: https://git.mahara.org/mahara/mahara/commit/1dbbbd9fa15f5f9d9769320e17c50cc51b29abf5
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1785989,2019-05-13 16:38:45 UTC,"Marking as duplicate of the ""Lock component in Eeschema"" wishlist item as 6.0 uses the new greedy/stingy selection model. This should help when selecting symbols placed on top of images."
1786000,2018-08-09 20:36:17 UTC,Why have you missed so many stations?
1786004,2018-08-08 12:24:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1786010,2019-09-16 13:59:07 UTC,Migrated to https://github.com/widelands/widelands/issues/2110
1786011,2020-09-08 09:22:55 UTC,"If I'm not wrong ZFS on root support has been introduced officially from 19.10 (eoan). I'm not sure if this one is still relevant, but with 20.04 I can't reproduce any errors/issues using ZFS as root and zfs-import-cache.service is working just fine."
1786013,2021-01-08 17:13:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786013,2020-10-26 14:38:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed-groovy'."
1786013,2020-07-16 01:14:26 UTC,"All autopkgtests for the newly accepted linux-signed-azure-5.4 (5.4.0-1022.22~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1786013,2020-07-14 02:58:18 UTC,"All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1786013,2020-07-12 19:15:03 UTC,"All autopkgtests for the newly accepted linux-hwe-5.0 (5.0.0-57.61~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1786013,2020-06-30 23:14:23 UTC,"All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1786013,2020-03-17 17:33:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1786013,2020-03-12 10:52:18 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'."
1786013,2019-02-14 16:54:54 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1786013,2019-11-12 20:04:58 UTC,"All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1786013,2019-07-25 16:04:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1786013,2019-05-14 22:53:52 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1786013,2019-02-04 14:46:37 UTC,This bug was fixed in the package linux - 4.19.0-12.13
1786013,2020-07-15 22:09:42 UTC,"All autopkgtests for the newly accepted linux-aws-5.4 (5.4.0-1020.20~18.04.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1786013,2018-12-20 05:31:53 UTC,This bug was fixed in the package linux-azure-edge - 4.18.0-1007.7~18.04.1
1786013,2018-12-20 05:30:01 UTC,This bug was fixed in the package linux-azure - 4.15.0-1036.38
1786013,2018-12-20 05:22:23 UTC,This bug was fixed in the package linux-azure - 4.15.0-1036.38~16.04.1
1786013,2018-12-20 05:21:00 UTC,This bug was fixed in the package linux-azure - 4.15.0-1036.38~14.04.2
1786013,2018-12-10 14:41:12 UTC,This bug was fixed in the package linux-azure - 4.18.0-1006.6
1786013,2018-12-10 08:38:11 UTC,This bug was fixed in the package linux-azure-edge - 4.18.0-1006.6~16.04.2
1786013,2018-12-03 14:59:47 UTC,This bug was fixed in the package linux - 4.4.0-140.166
1786013,2018-12-03 14:01:15 UTC,This bug was fixed in the package linux - 4.15.0-42.45
1786013,2018-12-03 08:49:32 UTC,This bug was fixed in the package linux - 4.18.0-12.13
1786013,2018-12-03 08:46:31 UTC,This bug was fixed in the package linux - 3.13.0-163.213
1786013,2018-11-15 11:04:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1786013,2018-11-16 16:38:27 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1786013,2018-11-16 16:36:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1786013,2018-11-15 11:34:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1786013,2018-12-20 05:43:11 UTC,This bug was fixed in the package linux-azure - 4.18.0-1007.7
1786014,2018-09-17 15:55:24 UTC,"I could not reproduce this bug (master branch) but still I agree that some work is needed e.g. by adding more test cases, improving/drafting missing documentation on both server and client sides"
1786014,2018-09-10 20:26:22 UTC,"This might be resolved by the fix implemented for #1786007, need to test. We should write a Tempest test for this."
1786023,2018-08-08 11:56:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589855"
1786028,2020-08-09 23:59:06 UTC,gimp (2.10.4+om-0ubu18.04.3~ppa)
1786031,2019-02-05 18:29:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/635005"
1786034,2021-02-17 17:08:59 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1786035,2019-05-16 23:03:38 UTC,This issue was fixed in the openstack/puppet-glance 11.6.0 release.
1786035,2018-08-20 15:16:07 UTC,This issue was fixed in the openstack/puppet-glare 2.3.0 release.
1786035,2018-08-20 15:15:59 UTC,This issue was fixed in the openstack/puppet-glance 13.3.0 release.
1786035,2018-08-20 04:01:42 UTC,"Reviewed:  https://review.openstack.org/592890
Committed: https://git.openstack.org/cgit/openstack/puppet-glance/commit/?id=48cd8b34d001d322e371741ba72d9c4621e470c4
Submitter: Zuul
Branch:    stable/pike"
1786035,2018-08-20 04:01:32 UTC,"Reviewed:  https://review.openstack.org/592889
Committed: https://git.openstack.org/cgit/openstack/puppet-glance/commit/?id=2602c0bb91b5181502dd84d0b4f9e66036b14a3b
Submitter: Zuul
Branch:    stable/queens"
1786035,2018-08-20 03:09:58 UTC,"Reviewed:  https://review.openstack.org/592891
Committed: https://git.openstack.org/cgit/openstack/puppet-glare/commit/?id=c9d780a1222fe0198aeaf07115d794a9cef04932
Submitter: Zuul
Branch:    stable/queens"
1786035,2018-08-08 15:26:25 UTC,"Reviewed:  https://review.openstack.org/589887
Committed: https://git.openstack.org/cgit/openstack/puppet-glare/commit/?id=efc14de4aaead7be4686fa2c0675f55693a8b8e9
Submitter: Zuul
Branch:    master"
1786035,2018-08-17 07:26:17 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/592890"
1786035,2018-08-17 07:25:51 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/592889"
1786035,2018-08-16 15:51:52 UTC,"Reviewed:  https://review.openstack.org/589886
Committed: https://git.openstack.org/cgit/openstack/puppet-glance/commit/?id=5af9d8765cbf87b049e9ecad60762b4c7ce4dae0
Submitter: Zuul
Branch:    master"
1786035,2018-08-08 13:15:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589887"
1786035,2018-08-08 13:11:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/589886"
1786035,2018-08-17 07:26:31 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/592891"
1786046,2019-07-17 20:38:13 UTC,"> /usr/local/lib/libssl.so.1.1: version `OPENSSL_1_1_1' not found
"
1786046,2019-07-17 17:25:38 UTC,That's on Ubuntu 18.04.2 LTS
1786046,2019-07-17 16:43:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786046,2019-07-17 17:24:28 UTC,"I think my problem is related to this one. I couldn't include my `ubuntu-bug` debug info, because of a
`
ERROR: Could not import module, is a package upgrade in progress? Error: /usr/local/lib/libssl.so.1.1: version `OPENSSL_1_1_1' not found (required by /usr/lib/python3.6/lib-dynload/_ssl.cpython-36m-x86_64-linux-gnu.so)
`
bug that didn't go away even after installing a brand new openssl 3.0 from github. Quite ironic."
1786046,2018-08-13 12:03:49 UTC,apport information
1786046,2018-08-13 02:03:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1786046,2018-08-08 14:23:35 UTC,"When testing again, after the reboot I was able to bypass the login screen by just disconnecting both external monitor and had full access of the computer and input device."
1786046,2018-08-13 12:03:50 UTC,apport information
1786046,2019-07-17 21:08:55 UTC,"Well, it was v1.1.0e which is the latest one per Apt. The stuff that's in conflict seems to also be stock, not custom."
1786049,2018-08-22 14:07:09 UTC,Maybe hit again: http://10.125.0.203:8080/job/RunUnittests-arm64/749/console
1786049,2019-08-26 01:49:08 UTC,It looks like this has been fixed as I cannot reproduce it locally under stress running the develop (heading into 2.7).
1786049,2018-08-22 14:14:22 UTC,http://10.125.0.203:8080/job/RunUnittests-race-amd64/645/console
1786050,2019-02-12 07:05:52 UTC,"Change abandoned by Jose Castro Leon (<email address hidden>) on branch: master
Review: https://review.openstack.org/589925
Reason: There is another patch in nova that allows this extend_volume action"
1786056,2018-08-08 15:23:03 UTC,Note on this line:
1786058,2018-09-12 21:56:32 UTC,"Reviewed:  https://review.openstack.org/599419
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7ee5499e5507c45249945fa5baf7665bc2f1cc02
Submitter: Zuul
Branch:    stable/rocky"
1786058,2018-09-03 14:51:47 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599419"
1786058,2019-03-22 03:48:22 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1786058,2018-10-08 21:50:49 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1786058,2018-10-05 11:02:31 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/603740
Reason: Apologies, finally getting around to looking at this now and as Icdcf681c1d71a09b88b029f80d13cd5015dacd56 landed in stable/queens we can't use it prior to this in Nova. Closing this out."
1786058,2018-10-05 11:02:05 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/603738
Reason: Apologies, finally getting around to looking at this now and as Icdcf681c1d71a09b88b029f80d13cd5015dacd56 landed in stable/queens we can't use it prior to this in Nova. Closing this out."
1786058,2018-08-22 17:16:43 UTC,"Reviewed:  https://review.openstack.org/589548
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8b019d6f1e7893a7e308bd79c879e94d3400e007
Submitter: Zuul
Branch:    master"
1786058,2018-09-24 14:46:58 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1786058,2018-09-19 12:44:32 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/603740"
1786058,2018-09-19 12:43:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/603738"
1786058,2018-09-19 12:43:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/603737"
1786058,2018-09-28 20:46:40 UTC,"Reviewed:  https://review.openstack.org/603737
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=551a7a459c6503158cb4512fec8b2dc9c0641abe
Submitter: Zuul
Branch:    stable/queens"
1786064,2018-10-26 04:27:30 UTC,149 GB. Feel free to contact me directly: mailto: tomreyn a7 megaglest d0t org.
1786064,2018-10-25 19:21:32 UTC,"So, how much space does your mirror use in gigabytes?"
1786064,2018-10-25 17:49:05 UTC,"Today, the server archive.getdeb.net points to became available again (after 2.5 months of not responding), but this Hetzner server now seems to be operated by someone else, hosting a different project."
1786064,2018-08-29 08:28:15 UTC,https://launchpad.net/~getdeb-package-managers/+members#active
1786064,2018-08-29 01:56:51 UTC,Who originally ran GetDeb/PlayDeb? Maybe he/she can be contacted to see if/why the project was abandoned?
1786064,2018-08-29 02:02:24 UTC,"Sorry for double posting, but, it looks like João Pinto ran the repo's. It does not look like he has been active for several years(though I haven't checked GitHub or IRC).
AFAIK PlayDeb and GetDeb was abandoned several years ago, but someone else took over the project and continued it, it is possible that João was the old maintainer. And the owner as of 2017 is someone else. I will check archive.org to see if I can find any leads."
1786064,2018-08-21 23:11:01 UTC,"Any way to get a package listing from getdeb and playdeb?
Also, a way to get an older version of the sites source code?"
1786064,2018-08-20 08:31:21 UTC,The repos haven't been updated since September 2017.
1786064,2018-08-15 17:51:06 UTC,"As of 2018-08-15, it's still down..."
1786064,2018-08-11 15:23:30 UTC,I'm not sure when it was last updated but there is a mirror available at http://mirrors.dotsrc.org/getdeb/ubuntu that's currently up.
1786064,2018-08-08 15:49:45 UTC,"http://archive.getdeb.net is also unreachable.
http://getdeb.megaglest.org mirrors it."
1786064,2018-08-25 21:13:00 UTC,Anyone interested in forking the project should have a look at ~c-korn 's Git repositories at https://github.com/ckorn
1786064,2018-08-25 20:36:11 UTC,Setting status to 'confirmed' since this bug affects multiple users.
1786072,2018-08-08 16:21:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1786076,2018-08-08 16:29:18 UTC,"Note, I filed this via Questions.LP on behalf of Sergey Egorov (subscribed)."
1786076,2019-01-07 14:21:05 UTC,"Same problem here. he disks sda and sdb are shown in reverse order - sdb shown a top of sda.
No bootable device, after restart fresh install from USB."
1786079,2018-08-08 21:29:59 UTC,"Noting that bug 1746566 adds code for larger view options in Item Status, among other places.  It's been merged for 3.2 and I've added a comment requesting a backport for 3.0 and 3.1."
1786079,2018-08-08 18:00:59 UTC,"It seems to me that the correct way to fix this is to add batch importing into copy (or rather, *all*) buckets. As it is this sounds a lot like making the item status window (intended to be ephemeral; just a quick place to check on some things) into a pseudo-bucket interface already. buckets already have an All display option and you can have multiples with names vs having to re-load file(s) any time you navigate away."
1786079,2018-08-08 18:38:50 UTC,I heartily second Jason's suggestion.
1786079,2018-08-08 18:52:38 UTC,+1 Jason Boyer this is an excellent idea
1786079,2018-08-08 19:50:38 UTC,+1 for Jason's idea and +1 for Christine's idea to add a way to upload a file directly into a bucket.
1786084,2018-11-02 06:47:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786084,2018-08-09 14:42:41 UTC,I also have this problem.
1786084,2018-10-04 22:07:12 UTC,me too
1786086,2019-07-06 09:56:05 UTC,Very sorry for my mistake in your name. I would not notice it myself.
1786086,2019-07-06 01:46:55 UTC,"Dude, my name is Leandro, not Leonardo.
I am proposing a way to test your idea, with the current version."
1786086,2019-07-05 17:14:51 UTC,"Leonardo,"
1786086,2019-07-05 16:15:14 UTC,"Piotr, I am trying to create such a thing."
1786086,2019-07-05 15:12:43 UTC,"Hi Leonardo,
Last time I used any script was a .bat files under DOS.
I don't know what is simple to do in scripts and what not."
1786086,2019-07-05 14:11:39 UTC,"Ah, the issue here is that the label 'Value' is not editable right now."
1786086,2019-07-04 07:23:18 UTC,I just got into that trap - when imported netlist to PCB I noticed all my power symbols are connected to one net.
1786086,2019-01-08 18:52:13 UTC,Just to make sure you have all the necessary information of the current implementation.
1786086,2018-08-24 01:56:58 UTC,Cool. That sounds good Wayne.
1786086,2018-08-23 18:06:57 UTC,This will be addressed with the new symbol file format which is going to be part of the 6.0 development.  There is limitation with the current symbol file format when defining power symbols.  No changes to the current symbol file format are allowed as it will become obsolete.
1786086,2019-07-05 14:03:29 UTC,Cool Piotr awesome idea.
1786086,2018-08-21 00:25:45 UTC,Someone has any ideas here?
1786089,2018-08-28 20:23:42 UTC,Confirmed in 3.0.9 and master.
1786090,2019-02-05 09:27:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786090,2018-08-11 17:22:58 UTC,"Ok, with a compliant EFI implementation, there's no reason that warm vs cold boot should be a factor either, but it's interesting to know and gives us a starting point."
1786090,2018-08-11 00:08:20 UTC,"Can you attach the output of the 'dmesg' command when this happens?  This really shouldn't happen at all, but maybe we can get some more verbose information from the kernel about what's failing."
1786090,2018-08-08 18:45:20 UTC,Shim-signed failed to install. Here's the terminal output:
1786090,2018-08-11 08:50:00 UTC,"Hi Steve, thanks for the response."
1786090,2018-08-08 18:41:23 UTC,I've just rebooted the system and it dropped into a GRUB prompt.
1786092,2018-10-27 15:11:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786093,2018-08-24 15:44:19 UTC,"Thanks Clemens, that saved me some head scratching. One minor correction to your first solution - the second change of ""importDir[]"" to ""importDir"" is on line 173, not 172."
1786093,2018-08-24 15:41:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786100,2018-11-16 21:07:01 UTC,Confirmed also in EG 3-2-0
1786100,2019-02-20 18:35:16 UTC,Still an issue in EG 3-2-3
1786100,2019-08-19 14:30:39 UTC,I recently had a chance to test this out on my own system and pull log info.  We are running 3.2.3 at the moment.
1786100,2019-10-10 13:29:21 UTC,Still an issue in 3.3.3
1786100,2020-02-11 16:47:13 UTC,"Geoff, can you paste the output of"
1786100,2020-08-05 22:22:50 UTC,"I've tracked down the problem: under certain upgrade scenarios, the asset.copy_tag_copy_map table can end up with two instances of the fake FK trigger, including one that still fires on DELETE:"
1786100,2020-09-23 15:57:42 UTC,A patch is available in working/user/gmcharlt/lp1786100_fix_actcm_inh_fkey / https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp1786100_fix_actcm_inh_fkey
1786100,2020-09-23 18:12:42 UTC,"I've tested the second part of the test plan, a system without the DELETE trigger part and sign off is here:  user/rogan/lp1786100_fix_actcm_inh_fkey"
1786100,2021-02-09 16:46:58 UTC,"Pushed to master and rel_3_6. Thanks for testing, Rogan!"
1786100,2018-11-05 16:39:34 UTC,E.G. Web Client 3-0-9
1786100,2019-02-22 14:43:14 UTC,Can any of the affected locations pull the evergreen / postgresql logs from a failed attempt at removing a copy tag? I'm wondering if it's possible that a change to some database triggers may have been missed that prevents these tags from being deleted.
1786104,2018-08-16 17:17:12 UTC,"John - You may have already tried this, but when we implemented the patch for the incorrect transit slips, we had to ask staff to clear browser cache if they were still seeing the problem. We haven't had any reports of problems after cache clearing."
1786104,2018-08-15 19:35:07 UTC,"Thanks, John.  This is certainly useful info.  There should only ever be one active transit on a copy at a time and the user interface (and all of the other code) assumes as much.  Any time multiple active transits exist, the behavior is undefined.  Any insights into how the multiples are happening is appreciated."
1786104,2018-08-15 20:34:20 UTC,Opened a new bug regarding active transits in the web client: https://bugs.launchpad.net/evergreen/+bug/1787274
1786104,2019-04-27 13:44:33 UTC,Browser full refresh is almost always the issue with this. We are no longer seeing this issue in 3.1.10. It might be time to close this bug.
1786104,2018-08-15 18:55:03 UTC,We are seeing way more items with multiple active transits in the web client. I was working on pinpointing why and I discovered a scenario that produced the wrong information on the transit dialog/slip even after the fix for bug 1740537.
1786109,2021-02-17 17:09:02 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1786109,2019-01-12 23:38:59 UTC,"I also got this error running the below command :
./tripleo-quickstart/quickstart.sh --clean --release master --teardown all --tags all -e undercloud_undercloud_ntp_servers=147.117.251.28 -e @/home/toor/deploy-config.yaml 127.0.0.2"
1786109,2018-08-09 02:33:37 UTC,https://logs.rdoproject.org/36/590036/1/openstack-check/legacy-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-master/0d2eae7/logs/undercloud/home/zuul/flavor_list.log.txt.gz
1786109,2018-08-20 19:26:51 UTC,"Reviewed:  https://review.openstack.org/590036
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=9ea6018d3b776b625c948afab8e2c264e67ddbe8
Submitter: Zuul
Branch:    master"
1786109,2018-08-08 20:43:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/590036"
1786110,2018-08-09 12:44:02 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-August/094644.html
1786110,2018-08-09 13:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1786110,2018-08-28 17:01:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1786110,2018-09-10 17:53:06 UTC,This bug was fixed in the package linux - 4.15.0-34.37
1786110,2019-02-14 16:55:10 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1786114,2018-08-13 18:59:01 UTC,"Hi Dmitrii,"
1786114,2019-09-19 12:06:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1786114,2019-09-20 13:00:56 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1786114,2019-09-20 13:30:47 UTC,https://discourse.maas.io/t/nvme-namespace-crud-and-discovery-support/998 - done
1786116,2019-08-30 13:04:12 UTC,I agree that a program-wide facility for visually distinguishing overridden properties would be of value.
1786116,2019-08-04 22:24:47 UTC,This is similar to having zone connections overridden at some level: there's not much we can do to indicate that the default value has been overridden (other than better documentation/training/etc.).
1786116,2018-08-08 20:53:27 UTC,Here is the demo sallen_key filter circuit showing this behavior.
1786116,2019-08-27 19:57:38 UTC,@Jeff
1786117,2019-09-15 17:09:55 UTC,Migrated to https://github.com/widelands/widelands/issues/1076
1786121,2018-08-14 02:49:41 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1786125,2018-08-10 14:34:42 UTC,Could you add the contents of /var/log/dist-upgrade/main.log to this bug report? Thanks in advance. I suspect this is a duplicate of bug 1315559.
1786125,2018-08-10 14:50:44 UTC,Ahh.. That's what it checks. No need. My problem then is I haven't been using do-release-upgrade to do updates for a long time.
1786128,2019-06-04 21:35:46 UTC,What is the spice commandline you use?
1786128,2019-08-05 05:54:11 UTC,Running spice from the export netlist dialog is no longer supported.
1786129,2021-02-17 17:09:05 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1786129,2018-08-08 22:10:41 UTC,https://github.com/openstack/tripleo-heat-templates/blob/master/ci/environments/ovb-ha.yaml doesn't include:
1786129,2019-07-31 19:16:31 UTC,It looks like the change mentioned in comment #2 is merged.  Can this bug be closed now?
1786129,2018-08-08 22:19:28 UTC,"ovb-ha.yaml is included by default for newer versions, https://github.com/openstack/tripleo-quickstart/blob/127d388a1594d5c6b621e995a6d9e53a33e05548/config/general_config/minimal.yml#L72-L75"
1786131,2020-02-06 22:22:52 UTC,"@ Frederic Roussel,"
1786131,2020-02-06 23:07:11 UTC,"Thank you for testing! I didn't expect anything less: it is a GOOD
practice. Thanks for being thorough."
1786131,2020-02-12 13:44:06 UTC,A bug-fix is uploaded to the unstable PPA (together with some other bugfixes and some added features. See
1786146,2018-09-23 04:33:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786146,2018-12-19 15:16:07 UTC,"Paul, thanks for reporting this. I've added upstream ceilometer as a target as well. For canonical bootstack I believe this affects deployments prior to queens, which is the point when charm deployments switched from mongodb to gnocchi."
1786146,2020-07-14 22:24:24 UTC,"After Queens, ceilometer has dropped support to MongoDB and removed the options mentioned in this bug. So we can now mark this bug as invalid."
1786146,2020-07-14 22:26:12 UTC,https://review.opendev.org/#/c/512700/
1786147,2019-09-19 12:06:14 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1786150,2019-07-19 17:15:08 UTC,"Hi,"
1786150,2019-09-18 04:17:28 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1786172,2018-09-12 08:55:21 UTC,upstream release is now 3.17.1. any chance to update it ?
1786179,2018-08-18 14:29:18 UTC,This bug was fixed in the package libvirt - 4.6.0-2ubuntu1
1786179,2018-08-15 12:38:18 UTC,Also made available to Debian via: https://salsa.debian.org/libvirt-team/libvirt/merge_requests/5
1786179,2018-08-13 09:09:28 UTC,"If pre cosmic release there is a nice other way we can still pick it up as a fix, but that would make it releasable for now."
1786179,2018-08-13 09:08:44 UTC,"Discussion with Debian systemd folks went great.
It seems mid/long term we will get dh_installsystemd to do the right thing."
1786179,2018-08-10 11:26:53 UTC,"Fix V:
 - drop virtlogd sysV script (to fix the original issue) and drop the dh_systemd__start call to
   libvirtd (to avoid the secondary issue)
 - Intention: libvirtd (re)start is taken care of by dh_installinit anyway, avoid the bad restarts
   on virtlogd with this tweak
 - with that it seems to work, but it might have other implications that I missed
   - the new virtlogd-admin.socket is down (as it would need to restart the service)
   - service itself is up and still has the old PID so all is good
   - installation works, no more breaking the upgrade."
1786179,2018-08-10 10:30:12 UTC,Was incomplete - once more
1786179,2018-08-10 10:28:28 UTC,"Trying an interim TL;DR:
- Service A - --no-stop-on-upgrade
  A Requires A1.socket
  A Requires A2.socket
- Service B - --restart-after-upgrade
  B Requires=A1.socket
- A and B have also sysV scripts.
- d/rules calls dh_installinit and dh_systemd_start
- maintscripts get"
1786179,2018-08-10 06:08:21 UTC,In general Debian wants to support non-systemd systems more than we do - so dropping sysV might not only be an issue due to the systemd based start pulling off a restart of virtlogd - but also that this might be a derive that is more than we want.
1786179,2018-08-10 11:32:32 UTC,Submitted my updated findings to Debian
1786179,2018-08-09 12:48:36 UTC,"It turns out it will do this in postinst now:
 if [ -n $2 ]
  deb-systemd-invoke restart virtlogd.socket"
1786179,2018-08-09 12:16:34 UTC,Note to myself - command to trigger on fresh cosmic container:
1786179,2018-08-09 12:00:11 UTC,Test with the new (~ppa4) version LGTM:
1786179,2018-08-09 11:57:01 UTC,"The POC removes the sysV scripts which is probably a good idea anyway.
Backports only go back as far as Bionic for us which is fully systemd."
1786179,2018-08-09 10:18:42 UTC,Reported to Debian
1786179,2018-08-09 09:37:35 UTC,"This is in Debian since April, that would have shown up there.
Why would it only hit us thou?"
1786179,2018-08-09 09:16:55 UTC,It seems absolutely reproducible - so I added a bit more verbose output in cae one searches for this.
1786179,2018-08-09 09:12:01 UTC,"Post Upgrade:
root@c2:~# systemctl status virtlogd.service virtlogd.socket virtlogd-admin.socket  virtlockd.service virtlockd.socket virtlockd-admin.socket --no-pager --lines 2
● virtlogd.service - Virtual machine log manager
   Loaded: loaded (/lib/systemd/system/virtlogd.service; indirect; vendor preset: enabled)
   Active: active (running) since Thu 2018-08-09 05:26:07 UTC; 3h 45min ago
     Docs: man:virtlogd(8)
           https://libvirt.org
 Main PID: 4059 (virtlogd)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/virtlogd.service
           └─4059 /usr/sbin/virtlogd"
1786179,2018-08-09 09:11:54 UTC,"The Upgrade
# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  libjansson4
The following packages will be upgraded:
  libvirt-clients libvirt-daemon libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt0
5 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 3790 kB of archives.
After this operation, 1225 kB disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libjansson4 amd64 2.11-1 [29.3 kB]
Get:2 http://ppa.launchpad.net/ci-train-ppa-service/3349/ubuntu cosmic/main amd64 libvirt-daemon-driver-storage-rbd amd64 4.6.0-1ubuntu1~ppa3 [34.3 kB]
Get:3 http://ppa.launchpad.net/ci-train-ppa-service/3349/ubuntu cosmic/main amd64 libvirt-daemon-system amd64 4.6.0-1ubuntu1~ppa3 [77.0 kB]
Get:4 http://ppa.launchpad.net/ci-train-ppa-service/3349/ubuntu cosmic/main amd64 libvirt-daemon amd64 4.6.0-1ubuntu1~ppa3 [1712 kB]
Get:5 http://ppa.launchpad.net/ci-train-ppa-service/3349/ubuntu cosmic/main amd64 libvirt-clients amd64 4.6.0-1ubuntu1~ppa3 [615 kB]
Get:6 http://ppa.launchpad.net/ci-train-ppa-service/3349/ubuntu cosmic/main amd64 libvirt0 amd64 4.6.0-1ubuntu1~ppa3 [1322 kB]
Fetched 3790 kB in 1s (3161 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libjansson4:amd64.
(Reading database ... 44954 files and directories currently installed.)
Preparing to unpack .../0-libjansson4_2.11-1_amd64.deb ...
Unpacking libjansson4:amd64 (2.11-1) ...
Preparing to unpack .../1-libvirt-daemon-driver-storage-rbd_4.6.0-1ubuntu1~ppa3_amd64.deb ...
Unpacking libvirt-daemon-driver-storage-rbd (4.6.0-1ubuntu1~ppa3) over (4.0.0-1ubuntu13) ...
Preparing to unpack .../2-libvirt-daemon-system_4.6.0-1ubuntu1~ppa3_amd64.deb ...
Unpacking libvirt-daemon-system (4.6.0-1ubuntu1~ppa3) over (4.0.0-1ubuntu13) ...
Preparing to unpack .../3-libvirt-daemon_4.6.0-1ubuntu1~ppa3_amd64.deb ...
Unpacking libvirt-daemon (4.6.0-1ubuntu1~ppa3) over (4.0.0-1ubuntu13) ...
Preparing to unpack .../4-libvirt-clients_4.6.0-1ubuntu1~ppa3_amd64.deb ...
Unpacking libvirt-clients (4.6.0-1ubuntu1~ppa3) over (4.0.0-1ubuntu13) ...
Preparing to unpack .../5-libvirt0_4.6.0-1ubuntu1~ppa3_amd64.deb ...
Unpacking libvirt0:amd64 (4.6.0-1ubuntu1~ppa3) over (4.0.0-1ubuntu13) ...
Processing triggers for ureadahead (0.100.0-20) ...
Setting up libjansson4:amd64 (2.11-1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.4-2) ...
Setting up libvirt0:amd64 (4.6.0-1ubuntu1~ppa3) ...
Setting up libvirt-daemon (4.6.0-1ubuntu1~ppa3) ...
Setting up libvirt-clients (4.6.0-1ubuntu1~ppa3) ...
Setting up libvirt-daemon-system (4.6.0-1ubuntu1~ppa3) ...
Installing new version of config file /etc/apparmor.d/abstractions/libvirt-qemu ...
Installing new version of config file /etc/apparmor.d/usr.sbin.libvirtd ...
Installing new version of config file /etc/default/libvirt-guests ...
Installing new version of config file /etc/libvirt/libvirtd.conf ...
Installing new version of config file /etc/..."
1786179,2018-08-09 12:54:12 UTC,"As long as it had a sysV init script that is prefered from starting the systemd service.
This is why it is active now."
1786179,2018-08-09 09:11:32 UTC,Pre Upgrade
1786185,2018-08-12 13:28:33 UTC,Please file an upstream bug report.
1786186,2019-05-08 15:39:45 UTC,Also: https://github.com/juju/charm-helpers/pull/316 and https://github.com/juju/charm-helpers/pull/318
1786186,2018-09-26 13:43:16 UTC,I think it makes sense to have one unified template fragment for keystone auth token which works for all openstack releases. To achieve this the template will need to know which release is being deployed hence: https://github.com/juju/charm-helpers/pull/224
1786186,2018-12-07 14:51:17 UTC,Marking this as High as Stein is in development so this work must be done for 19.04 charm release.
1786186,2019-05-06 08:59:39 UTC,"Pull request: https://github.com/juju/charm-helpers/pull/315
Charm-glance review request: https://review.opendev.org/#/c/656956/"
1786191,2018-08-09 09:10:28 UTC,we need handle this to 409 error
1786191,2018-11-26 11:31:24 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/434783
1786195,2018-09-10 04:45:43 UTC,"Having what I believe is the same issue. Internal Intel HDA audio is distorted at normal maximum volume on Xubuntu, at 100% and not above. Seems to be distorted at lower volume levels as well. System sounds are distorted as well as sounds from media applications. This is recent to me as it seems to have been working fine less than a month ago."
1786195,2018-09-10 07:26:25 UTC,The bug was not gone when using kernel 4.4
1786195,2018-09-10 05:55:48 UTC,"Dominic: Can you please rephrase that? Was the bug gone when using kernel 4.4? And yes Ubuntu 18.04 ships with kernel 4.15, which is why we need you to test downgrading the kernel to an older version."
1786195,2018-08-09 10:53:56 UTC,"""16.04 used kernel 4.4 and you are presently using kernel 4.15"""
1786195,2018-09-10 17:10:00 UTC,"My issue seems to be localized to only the right speaker on a Thinkpad x270, and the issue happens in Windows as well, so it may be due to a blown speaker on my laptop."
1786195,2018-08-09 09:57:14 UTC,Thanks. If the sound worked fine in Ubuntu 16.04 then that's useful information. 16.04 used kernel 4.4 and you are presently using kernel 4.15
1786195,2018-08-09 09:42:49 UTC,"Over-Amplification is set to ""OFF"""
1786195,2018-08-09 09:15:31 UTC,"Next, if sound used to work on this machine in an older version of Ubuntu then please tell us what that version was."
1786195,2018-08-09 09:12:06 UTC,"Also, while in Settings > Sound, click on ""Test Speakers"". Does the speaker test play cleanly?"
1786195,2018-08-09 10:39:59 UTC,"uname -a
Linux novgorod-LinuxBook 4.4.146-0404146-generic #201808061143 SMP Mon Aug 6 15:51:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1786195,2018-08-09 09:05:49 UTC,Thanks for the bug report.
1786197,2019-10-13 11:42:00 UTC,Had the same problem. This worked
1786197,2019-04-28 18:26:19 UTC,"I have the same problem with Ubuntu 18.04, lts-13.17. (Linux Subsystem on Windows 10)."
1786197,2019-04-25 10:53:00 UTC,"Still have it, same problem too."
1786197,2019-01-06 21:47:07 UTC,Just ran into this issue. Are there any updates on this?
1786197,2019-01-09 09:04:35 UTC,"Exact same problem in Ubuntu 18.04 - except it was for lts-13.2. No issues for Windows version though.
Look like the bug lives through the versions."
1786197,2018-09-21 19:00:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786197,2019-04-19 00:39:40 UTC,"Same problem. Ubuntu 18.04, LTS-13.16"
1786197,2019-01-01 17:21:01 UTC,Any update? This bug still exists.
1786204,2019-08-30 01:37:04 UTC,"Reviewed:  https://review.opendev.org/587405
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=0521f0a5d728a6f16eaaf9c929b6f2e3999c5dc7
Submitter: Zuul
Branch:    master"
1786204,2019-09-18 19:27:52 UTC,This issue was fixed in the openstack/python-tripleoclient 12.2.0 release.
1786204,2018-08-13 16:03:12 UTC,Fix proposed: https://review.openstack.org/#/c/587405
1786205,2018-08-09 12:24:39 UTC,"The attachment ""Upstream commit a409cc5473d186500fdafcfada40a154b8786957 ""Fix #246 - apcu_entry hangs"""" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1786205,2018-12-30 11:10:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786211,2018-08-09 23:39:07 UTC,"I like the idea of a combined Mixer pane. It definitely simplifies finding certain Mixxx preferences if they grouped in pref panes like they are in skins. We already have Waveforms, Decks, Effects and Library, so it makes sense to combine EQ, QuickEffect & Crossfader in a Mixer pane."
1786211,2018-09-21 00:19:21 UTC,+1 to this.
1786211,2018-09-21 00:35:02 UTC,"I am afraid this may not be so easy because the code for DlgPrefEQ is messy. I did work in https://github.com/mixxxdj/mixxx/pull/1705 to start cleaning it up, but there is still more to do."
1786224,2018-08-20 11:31:59 UTC,I've checked and PyQt5 and sip.cpython-36m-x86_64-linux-gnu.so are correctly installed in /usr/lib/python3/dist-packages/
1786224,2018-08-19 16:00:42 UTC,"python3
Python 3.6.5 (default, Apr  1 2018, 05:46:30)
[GCC 7.3.0] on linux
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> import sip
>>> print(sip, sip.SIP_VERSION_STR)
<module 'sip' from '/home/arnaud/.local/lib/python3.6/site-packages/sip.so'> 4.19.3"
1786224,2018-08-19 16:22:09 UTC,"If PyQt5 and sip.cpython-36m-x86_64-linux-gnu.so are not in /usr/lib/python3/dist-packages/
they are not installed with apt-get and that's the possible reason if they are not the 18.04 versions."
1786224,2018-08-19 15:17:27 UTC,"liboqapy-iproc0 is already installed.
I've tried to reinstall it (apt install --reinstall liboqapy-iproc0) and get always the issue…"
1786224,2018-08-19 15:01:49 UTC,"So, I've made my upgrade from 16.04 to 18.04 and I can reproduce the issue."
1786224,2018-08-17 12:23:39 UTC,It has been installed automatically.
1786224,2018-08-17 12:01:02 UTC,In this changelog [0] the API v12.3 was implemented in python3-sip v4.19.5.
1786224,2018-08-19 15:45:56 UTC,What is the return of
1786225,2018-08-09 11:40:04 UTC,"I don't know too much about Ceilometer, but it can be the code that cause problem.
https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/pollsters/__init__.py#L107-L116"
1786225,2018-09-03 12:36:15 UTC,"Same thing for me on queens with ceilometer version 10.0.1. Every instance, that does not have image fails polling it's metrics."
1786225,2020-04-12 23:46:49 UTC,cpu_l3_cache statistic in not available for instance 27247d9a-a183-4778-94fd-43a4ad7f0ab4: ceilometer.compute.pollsters.NoVolumeException
1786225,2020-12-01 09:38:21 UTC,cpu_util was removed in stein. Closing this.
1786226,2018-08-09 11:27:16 UTC,I compared rally results from Your patch and some other neutron patch (https://review.openstack.org/#/c/589885/). Looks for me that improvement is really impressive :)
1786226,2018-08-09 13:20:00 UTC,Awesome!!!!!!
1786227,2018-10-13 00:49:12 UTC,Sorry I didn't stumble across this bug a month ago.
1786227,2018-10-12 22:28:21 UTC,casper is also in the 'live' seed for Ubuntu and its flavors so it would still be installed by default in the live environment.
1786227,2018-10-12 23:09:10 UTC,"I made a custom ISO - or better a completely new one. Its whole size is 122 MB. It has e.g. no GUI, but fullfiles one specific target (network/VPN/firewall area)."
1786227,2018-10-12 22:56:16 UTC,This question was also asked a few months ago:
1786227,2018-10-13 00:45:27 UTC,"Unfortunately, we are in Final Freeze now in preparation for Ubuntu 18.10's release next week so I don't removing the direct dependency from casper is something we are going to be able to do until 19.04."
1786230,2018-08-09 11:33:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786230,2018-08-09 11:36:06 UTC,See also the bug report at Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902504
1786233,2018-08-10 07:50:17 UTC,apport information
1786233,2018-08-10 07:50:18 UTC,apport information
1786233,2018-08-10 07:50:20 UTC,apport information
1786233,2018-08-10 07:50:20 UTC,apport information
1786233,2018-08-20 02:29:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786233,2018-08-10 02:38:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1786238,2019-11-11 15:39:28 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1786238,2019-10-09 20:23:55 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/687669"
1786238,2019-09-24 16:05:45 UTC,"Reviewed:  https://review.opendev.org/683367
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=cc555c41966e53aa43d96e0d66a169720c3c98a4
Submitter: Zuul
Branch:    master"
1786238,2020-01-30 10:25:10 UTC,This issue was fixed in the openstack/kolla-ansible 8.1.0 release.
1786238,2019-09-20 11:33:09 UTC,"Thanks for posting the fix Eduardo, I proposed it to kolla-ansible."
1786238,2019-09-20 11:33:31 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/683367"
1786238,2018-08-10 05:17:35 UTC,kuryr-libnetwork does not support install_type==binary . but it supports install_type=source.
1786238,2019-10-10 09:50:18 UTC,"Reviewed:  https://review.opendev.org/687669
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d82439a41e98aba92f7440820fd1837a87343880
Submitter: Zuul
Branch:    stable/stein"
1786238,2018-08-15 07:17:41 UTC,"Just checked RDO kuryr packages, and there is not any for libnetwork, there are kuryr-lib (common library) and kuryr-kubernetes."
1786238,2019-09-20 08:59:18 UTC,"Little change to kolla-ansible to get kolla/centos-binary-kuryr-libnetwork without changing the whole kolla-install-type.
sed '/{{ kolla_install_type }}/i kuryr_install_type: ""{{ kolla_install_type }}""' -i /usr/share/kolla-ansible/ansible/roles/kuryr/defaults/main.yml
sed 's/{{ kolla_install_type }}/{{ kuryr_install_type }}/g' -i /usr/share/kolla-ansible/ansible/roles/kuryr/defaults/main.yml"
1786238,2018-08-15 07:11:08 UTC,"In centos repos there are few kuryr packages, need to find if any of those is for the libnetwork part."
1786241,2018-08-10 10:57:41 UTC,"Good day, All.
New bug report had been sent to Acer Support with request to fix ACPI in BIOS # 180810-001559
I hope to get a reaction from ACER Support:("
1786241,2018-08-09 19:08:52 UTC,"Testing of mainline kernel
romkuz@Nitro-5:~/Downloads$ ls -l linux-*
-rw-rw-r-- 1 romkuz romkuz 10323364 сер  9 21:29 linux-headers-4.18.0-041800rc8_4.18.0-041800rc8.201808052031_all.deb
-rw-rw-r-- 1 romkuz romkuz  1120436 сер  9 21:29 linux-headers-4.18.0-041800rc8-generic_4.18.0-041800rc8.201808052031_amd64.deb
-rw-rw-r-- 1 romkuz romkuz  8155044 сер  9 21:30 linux-image-unsigned-4.18.0-041800rc8-generic_4.18.0-041800rc8.201808052031_amd64.deb
-rw-rw-r-- 1 romkuz romkuz 44991028 сер  9 21:30 linux-modules-4.18.0-041800rc8-generic_4.18.0-041800rc8.201808052031_amd64.deb"
1786241,2018-08-09 15:41:48 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1786241,2018-08-09 14:02:16 UTC,apport information
1786241,2018-08-09 14:02:15 UTC,apport information
1786241,2018-08-09 14:02:13 UTC,apport information
1786241,2018-08-09 14:02:12 UTC,apport information
1786241,2018-08-09 14:02:09 UTC,apport information
1786241,2018-08-09 14:02:08 UTC,apport information
1786241,2018-08-09 14:02:04 UTC,apport information
1786241,2018-08-09 14:02:03 UTC,apport information
1786241,2018-08-09 14:02:01 UTC,apport information
1786241,2018-08-09 14:02:00 UTC,apport information
1786241,2018-08-09 14:01:59 UTC,apport information
1786241,2018-08-09 14:01:57 UTC,apport information
1786241,2018-08-09 13:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1786241,2018-08-09 14:02:07 UTC,apport information
1786241,2018-08-09 14:02:05 UTC,apport information
1786241,2018-08-09 14:02:11 UTC,apport information
1786243,2020-11-16 11:10:14 UTC,it should be ok with newer releases
1786243,2020-08-19 22:45:41 UTC,"This featured worked for me on 18.04, but there's a similar issue on 20.04: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1873922"
1786243,2021-01-16 04:17:32 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1786246,2019-04-25 14:30:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786246,2020-08-05 01:10:21 UTC,This still seems to be a problem. Tried installing clonezilla using Synaptic and got partially installed / failure errors on 20.04. Will post new bug so it attaches my system info.
1786248,2018-09-01 16:29:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786249,2018-09-10 20:15:02 UTC,The best option would be to extend the event model to keep track of the number of retries of each event.
1786258,2018-08-13 04:46:18 UTC,"We do pool connections. If the pool is in active use, we allow it to grow.
Likely lots of agents were doing concurrent activity and we don't put hard
caps on the pool."
1786258,2018-08-13 04:51:57 UTC,"Default pool limit, is in the gopkg.in/mgo.v2 code base is 4096 per
controller. You can set a value in agent.conf:
if limitStr := agentConfig.Value(""MONGO_SOCKET_POOL_LIMIT""); limitStr != """"
{"
1786258,2018-08-13 05:12:42 UTC,"I should also mention that I don't think the Pool is gardened. So it grows
to a max size, and then stays there. I would guess that without a policy of
""allow a request to not be satisfied for X ms"", you'll run into workers
restarting because hitting the limits of the pool will just cause the query
to be considered failed and the worker thread (and possibly agent) will
bounce."
1786258,2018-08-13 07:10:56 UTC,"So apparently I read in the code that you can change the max pool size in the agent config, correct ?"
1786258,2018-08-13 09:00:38 UTC,"I believe the config is only read at startup. But otherwise you would be
able to set a max pool size. However, if you hit it, it will just fail the
query, triggering an error, which is probably only handled by restarting
the worker."
1786269,2018-08-09 15:20:16 UTC,"reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1786269,2018-11-11 12:02:22 UTC,Bug should now be fixed: https://gitlab.com/inkscape/inkscape/merge_requests/323
1786283,2018-11-21 12:27:50 UTC,"Change abandoned by Alvaro Uría (<email address hidden>) on branch: stable/18.05
Review: https://review.openstack.org/590737
Reason: see https://review.openstack.org/619225"
1786283,2018-11-21 12:27:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619225"
1786283,2018-08-10 10:19:38 UTC,"Fix proposed to branch: stable/18.05
Review: https://review.openstack.org/590737"
1786286,2018-10-20 02:07:11 UTC,"Reviewed:  https://review.openstack.org/583984
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=1c6cfa1e4669d107d76e58b9cfdca3437add8dc6
Submitter: Zuul
Branch:    master"
1786286,2018-12-20 05:25:00 UTC,"Reviewed:  https://review.openstack.org/582163
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=681ff01f8b810dc3e9f63de8e5ee9b2101849309
Submitter: Zuul
Branch:    master"
1786286,2019-10-18 09:31:19 UTC,Marking invalid because this is an ongoing effort that does not need a bug. Otherwise it will be forever open.
1786298,2019-11-21 14:05:18 UTC,"Reviewed:  https://review.opendev.org/684658
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7aeec0e501816b8b74e5422d81d9628c2e71af16
Submitter: Zuul
Branch:    stable/pike"
1786298,2019-09-25 09:23:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/684658"
1786298,2019-07-10 21:40:19 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1786298,2019-04-10 21:42:22 UTC,"FYI, if you haven't purged your archived records, you can get away with this:"
1786298,2019-04-05 14:38:35 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/650309"
1786298,2019-03-22 03:48:42 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1786298,2018-10-08 20:53:38 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1786298,2019-04-05 21:24:07 UTC,"Reviewed:  https://review.openstack.org/650309
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b6f48354b7eacecd7a146fc05a12537b4f22e18
Submitter: Zuul
Branch:    stable/queens"
1786298,2018-09-21 14:18:45 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604373"
1786298,2018-09-21 13:00:12 UTC,"Reviewed:  https://review.openstack.org/591558
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8a6b57cf741e17d3de54ed8c85d9fb69c43e7432
Submitter: Zuul
Branch:    master"
1786298,2018-08-13 11:56:47 UTC,"What is ""delete_archive_logs""? Do you mean ""archive_deleted_rows""?"
1786298,2018-08-14 05:45:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/591558"
1786298,2018-08-13 12:51:21 UTC,I've attached a patch for the problem. I'm having some problems uploading changes to gerrit at the moment.
1786298,2018-08-13 12:16:20 UTC,"I guess you don't have to be using the ec2api, the DB API instance_create() method always creates an instance_id_mappings record but instance_destroy() does not remove it."
1786298,2018-08-13 12:01:07 UTC,"I believe the issue is that when the instances table record is deleted (instances.deleted != 0), we don't also delete the instance_id_mappings table record so the archive command never moves those records to shadow tables because they aren't actually marked as deleted != 0. This is a latent bug as far as I know."
1786298,2018-08-13 11:57:37 UTC,"Are you using the ec2api for this? As far as I know, instance_id_mappings is only used for ec2 instances."
1786298,2018-10-03 00:56:09 UTC,"Reviewed:  https://review.openstack.org/604373
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6186996c8093e723bdaa0e06664143685050312d
Submitter: Zuul
Branch:    stable/rocky"
1786305,2020-02-02 13:06:39 UTC,otherwise
1786305,2020-02-02 13:01:08 UTC,"Hi, currrent version is 4.7"
1786305,2020-02-02 12:34:58 UTC,"Thanks, it did the trick. I had to install it with the deb package on your website, the ppa on debian only has the 4.6 version. Is it normal? I don't know well how ppa works."
1786305,2020-01-26 15:52:21 UTC,The same bug affects me with 4.6. I do not remember the last time I used Qarte so I do not know for how log it occurs.
1786305,2020-01-26 16:25:00 UTC,"@ Gilgamesh, update to 4.7.0"
1786305,2018-08-16 15:14:09 UTC,"Thank you a lot.
If I may help, please tell me.
Not very good at computer stuff except as basic hacker, but...
Regards and thank you for your useful software.
FF."
1786305,2018-08-16 07:33:06 UTC,Fixed.
1786305,2018-08-13 10:59:14 UTC,"It indeed seems arte changed their codeline.
I deeply suspect they changed their way of showing video too."
1786305,2018-08-12 17:35:34 UTC,"same problem as above. No such videos. The window don't load anything.
It was also the same problem last summer. I think Arte change the codeline during that time."
1786305,2018-08-11 21:10:30 UTC,"confirmed, deb stretch as well, and marked another bug report as duplicate of this one"
1786305,2018-08-10 17:37:11 UTC,confirming this bug on Debian Strech
1786305,2018-08-23 21:09:14 UTC,"Fixed indeed
Thanks ever so much
Regards"
1786307,2018-08-14 09:20:30 UTC,hint:
1786307,2018-08-14 09:30:38 UTC,The addess in kubeconfig differs from the one which `curl` command tries to access:
1786312,2020-10-19 21:25:29 UTC,Here's a fix:
1786312,2019-02-07 17:56:54 UTC,Confirmed
1786312,2018-08-10 14:10:33 UTC,IRC discussion for reference:
1786312,2020-10-19 20:52:10 UTC,Just ran into this today as a result of a lot of COVID-related manual due date adjustments.  Should be a simple thing to retain the current logic while also reporting the correct amount billed so far by the patron.
1786318,2019-03-22 03:48:52 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1786318,2018-08-24 17:24:44 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc3 release candidate.
1786318,2018-09-24 14:46:37 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1786318,2018-08-23 20:17:47 UTC,"Reviewed:  https://review.openstack.org/590803
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=838ecb33830e58dabd5e7116a164b7ef792e6fdb
Submitter: Zuul
Branch:    stable/queens"
1786318,2018-09-24 14:46:59 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1786318,2018-08-10 15:39:39 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/590804"
1786318,2018-08-09 17:22:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/590439"
1786318,2018-08-23 20:17:36 UTC,"Reviewed:  https://review.openstack.org/590801
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a890c3403653ddea5f5639fc783b93f9e8e39265
Submitter: Zuul
Branch:    stable/rocky"
1786318,2018-08-10 15:35:40 UTC,"Reviewed:  https://review.openstack.org/590439
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3a4b4b91b0bee514d47a67f6a5f9c4ab9ae7f7d8
Submitter: Zuul
Branch:    master"
1786318,2018-08-25 05:45:28 UTC,"Reviewed:  https://review.openstack.org/590804
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6864804e61171aa3effa80642f47a7ccd040dd31
Submitter: Zuul
Branch:    stable/pike"
1786318,2018-08-10 15:38:51 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/590803"
1786318,2018-08-10 15:37:35 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/590801"
1786321,2018-08-09 19:37:43 UTC,"it was resolved, the problem resolved remove teamviewer package, that package blocks after that update (and teamviewer update also)."
1786324,2018-09-14 16:01:27 UTC,This command can download agents but it seems that all OS releases (for the same version and arch) are identical. I checked this with the Ubuntu ones. This seems to coincide with the single Ubuntu binary available here for instance:
1786333,2018-08-11 19:05:21 UTC,Replicated from: https://bugs.launchpad.net/kicad/+bug/1781277 (where we can found example for implementation)
1786333,2018-10-05 04:29:11 UTC,Related lp:1598912
1786333,2019-05-28 10:26:45 UTC,Has this request been satisfied now that the measure tool is available in the footprint viewer for the assignment tool in 5.1.2?
1786333,2018-08-10 21:31:01 UTC,I'm currently add using draw layer for adding dimension info for my customized lib.
1786336,2020-08-16 13:12:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786336,2020-08-16 13:48:47 UTC,On groovy here and I can't update https://releases.ubuntu.com/20.04/ubuntu-20.04.1-live-server-amd64.iso.zsync using zsync. Had to change it to: http://releases.ubuntu.com/20.04/ubuntu-20.04.1-live-server-amd64.iso.zsync.
1786336,2020-10-23 22:01:01 UTC,"Oct 23, on an ubuntu 18.04 system, the Ubuntu 20.10 zsync download displays the above errors when an https download is attempted.  Using http succeeds."
1786337,2018-12-11 15:43:51 UTC,"The verification of the Stable Release Update for python-phabricator has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1786337,2018-12-11 15:43:44 UTC,This bug was fixed in the package python-phabricator - 0.7.0-1ubuntu0.1
1786337,2018-12-09 23:33:10 UTC,I have tested the bionic proposed update in the bionic docker container and can confirm the fix:
1786337,2018-11-13 18:47:25 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1786337,2018-08-10 22:53:13 UTC,"Hello Simon, or anyone else affected,"
1786337,2018-08-09 21:05:59 UTC,This bug was fixed in the package python-phabricator - 0.7.0-1ubuntu1
1786337,2018-08-09 20:06:25 UTC,https://launchpad.net/ubuntu/+source/python-phabricator/0.7.0-1ubuntu1
1786337,2018-12-06 15:08:57 UTC,"$ python -c 'from phabricator import Phabricator; phab = Phabricator(host=""https://phab.lubuntu.me/api/"", token=""API KEY""); phab.diffusion.commit.search(constraints={""query"": ""a34837de8224""})'
Traceback (most recent call last):
  File ""<string>"", line 1, in <module>
  File ""/usr/lib/python2.7/dist-packages/phabricator/__init__.py"", line 248, in __call__
    return self._request(**kwargs)
  File ""/usr/lib/python2.7/dist-packages/phabricator/__init__.py"", line 323, in _request
    data = self._parse_response(response)
  File ""/usr/lib/python2.7/dist-packages/phabricator/__init__.py"", line 333, in _parse_response
    raise APIError(parsed['error_code'], parsed['error_info'])
phabricator.APIError: ERR-CONDUIT-CALL: Conduit API method ""commit.search"" does not exist.
$ python3 -c 'from phabricator import Phabricator; phab = Phabricator(host=""https://phab.lubuntu.me/api/"", token=""API KEY""); phab.diffusion.commit.search(constraints={""query"": ""a34837de8224""})'
Traceback (most recent call last):
  File ""<string>"", line 1, in <module>
  File ""/usr/lib/python3/dist-packages/phabricator/__init__.py"", line 248, in __call__
    return self._request(**kwargs)
  File ""/usr/lib/python3/dist-packages/phabricator/__init__.py"", line 323, in _request
    data = self._parse_response(response)
  File ""/usr/lib/python3/dist-packages/phabricator/__init__.py"", line 333, in _parse_response
    raise APIError(parsed['error_code'], parsed['error_info'])
phabricator.APIError: ERR-CONDUIT-CALL: Conduit API method ""commit.search"" does not exist.
$ sudo apt install python3-phabricator python-phabricator
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  python-phabricator python3-phabricator
2 upgraded, 0 newly installed, 0 to remove and 45 not upgraded.
Need to get 32.8 kB of archives.
After this operation, 5120 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 python-phabricator all 0.7.0-1ubuntu0.1 [16.1 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 python3-phabricator all 0.7.0-1ubuntu0.1 [16.7 kB]
Fetched 32.8 kB in 1s (45.4 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 23490 files and directories currently installed.)
Preparing to unpack .../python-phabricator_0.7.0-1ubuntu0.1_all.deb ...
Unpacking python-phabricator (0.7.0-1ubuntu0.1) over (0.7.0-1) ...
Preparing to unpack .../python3-phabricator_0.7.0-1ubuntu0.1_all.deb ...
Unpacking python3-phabricator (0.7.0-1ubuntu0.1) over (0.7.0-1) ...
Setting up python-phabricator (0.7.0-1ubuntu0.1) ...
Setting up python3-phabricator (0.7.0-1ubuntu0.1) ...
$ python -c 'from phabricator import Phabricator; phab = Phabricator(host=""https://phab.lubuntu.me/api/"", token=""API KEY""); phab.diffusion.commit.search(constraints={""query"": ""a34837de8224""})'
Traceback (most recent call last):
  File ""<string>"", line 1, in <module>
  File ""/usr/lib/python2.7/dist-packages/phabricator/__init__.py"", line 248, in __call__
    return self._request(**kwargs)
  File ""/usr/lib/python2.7/dist-packages/phabricat..."
1786344,2019-06-21 09:47:45 UTC,"I have tested the daily build ISO from this morning UTC. If I enter Ubiquity's welcome screen, select zh_CN from there and ""Try Ubuntu"", ""Intelligent Pinyin"" is now - unlike before - active in the resulting session, and I can select it via the input source indicator or <Super>+<Space> and start inputting Chinese instantly. Also tried ja_JP, also with a positive result."
1786344,2019-07-02 17:25:24 UTC,"Hello Ping-Wu, or anyone else affected,"
1786344,2019-07-02 18:42:09 UTC,Verified the test case using gnome-settings-daemon 3.28.1-0ubuntu1.3 from bionic-proposed.
1786344,2019-07-03 00:16:53 UTC,"How do I test it?  I'm interested in seeing Chinese input method being able
to be activated and behaving the way it is expected in a LiveUSB,
preferably in Ubuntu 18.04.3 iso.  Is there any pre-release version of the
18.04.3 iso available?"
1786344,2019-07-03 01:20:30 UTC,"On 2019-07-03 02:16, Ping-Wu wrote:

> How do I test it?  I'm interested in seeing Chinese input method
> being able to be activated and behaving the way it is expected in a
> LiveUSB, preferably in Ubuntu 18.04.3 iso.  Is there any pre-release
> version of the 18.04.3 iso available?
"
1786344,2019-07-03 06:31:58 UTC,"I have tried today's daily built iso of 18.04.  I selected simplified
Chinese during boot. Still couldn't input Chinese."
1786344,2019-07-03 06:49:07 UTC,"Tried 19.10 by selecting simplified Chinese during booting the daily build
iso.  Was able to toggle (shift-key) between Chinese and English inputs.
This is good!"
1786344,2019-07-03 09:58:27 UTC,"On 2019-07-03 08:31, Ping-Wu wrote:

> I have tried today's daily built iso of 18.04.
"
1786344,2019-07-05 16:37:49 UTC,Another good idea!  English (US).
1786344,2019-07-03 18:41:54 UTC,"On 2019-07-03 18:15, Ping-Wu wrote:

> On Wed, Jul 3, 2019 at 12:05 AM Gunnar Hjalmarsson
> <email address hidden> wrote:
>> On 2019-07-03 08:31, Ping-Wu wrote:
>>> I have tried today's daily built iso of 18.04.
>>
>> Where did you find that ISO?
>
> http://cdimage.ubuntu.com/bionic/daily-live/
"
1786344,2019-07-03 22:53:40 UTC,">
>
> we should be able to
> confirm it the day after version 3.28.1-0ubuntu1.3 has been moved to
> bionic-updates.
>
>
I am seeing that this package has already been moved to the daily build
that I tested.  😓  Please see the attached manifest.
"
1786344,2019-07-03 23:14:01 UTC,"Oops.  False alarm.  The Chinese input frame seems to be working OK in
190703 daily build.  👍  However, the first entry of the input method is
labeled as ""汉语“ （Chinese）。  Either that should be changed to ""英语”
（English），because it is indeed an English keyboard.  Or assign
ibus-libpinyin as the input method for ""汉语"" and remove the ibus-libpinyin
（""智能拼音""）entry.  The latter is, of course, preferred.  Please see attached
screenshot."
1786344,2019-07-05 02:09:02 UTC,"So not only are there daily builds of stable releases, they are taking packages in -proposed into account. I had no idea of either. Thanks for letting me know."
1786344,2019-07-05 07:29:06 UTC,"On Thu, Jul 4, 2019 at 4:15 PM Gunnar Hjalmarsson <
<email address hidden>> wrote:"
1786344,2019-07-05 12:39:08 UTC,"On 2019-07-05 09:29, Ping-Wu wrote:

> On Thu, Jul 4, 2019 at 4:15 PM Gunnar Hjalmarsson
> <email address hidden> wrote:
>> Replacing ""cn"" with ""en"" makes sense to me.
>
> This is a good idea!
"
1786344,2019-06-20 12:34:27 UTC,This bug was fixed in the package gnome-settings-daemon - 3.32.1-1ubuntu2
1786344,2019-07-11 09:17:06 UTC,"The verification of the Stable Release Update for gnome-settings-daemon has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1786344,2019-07-03 16:15:32 UTC,http://cdimage.ubuntu.com/bionic/daily-live/
1786344,2019-06-11 15:14:42 UTC,"Ok, noted Sebastien. I do plan to SRU it myself, so I re-added a bionic task and assigned it to me."
1786344,2018-08-29 14:24:17 UTC,"ubiquity doesn't do anything in the live session, it's the installer app that starts if you click the corresponding icon once in the live session, reassigning to gnome-settings-daemon which is a more likely starting point to investigate the issue"
1786344,2019-06-07 03:44:08 UTC,"Unlike what we have believed up to now, the issue is present on the 18.04.2 ISO as well, so I added a bionic bug task."
1786344,2018-08-10 00:22:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1786344,2018-08-10 02:44:46 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1786344,2018-08-10 06:32:00 UTC,@Ping-Wu: Please describe the issue in English too. It's hard to understand what the problem is.
1786344,2018-08-17 17:45:32 UTC,"Title:
  18.10 镜像无法输入中文"
1786344,2018-08-25 01:55:47 UTC,"I tested the 2018.08.24 iso, when booted into simplified Chinese locale, I can now select 智能拼音 (smart pinyin) to input Chinese characters.  However, this should be the DEFAULT, i.e., a Chinese user should be able to input Chinese characters when selecting the Chinese locale, WITHOUT any additional step."
1786344,2018-08-25 19:05:48 UTC,Thanks for clarifying.
1786344,2018-08-26 01:19:30 UTC,"Yes, something very similar to bug #1756205.  However, if I remember it
correctly, in bug #1756205, sunpinyin was selected as the default Chinese
input engine but was not included in the iso.  Once you change the default
Chinese input engine to ibus-libpinyin (which was included in the iso),
problem solved."
1786344,2018-08-26 01:48:27 UTC,"I need to point out that although I mentioned that ""the pinyin input engine has been deprecated"", this is inaccurate.  Indeed, ibus-pinyin, with some simple tweaking, is robust and fast and works very well in 18.04 (I think I should thank you, Gunnar!)  Actually ibus-pinyin is my preferred Chinese input engine, more so than ibus-libpinyin. As far as I am concerned, this is what makes Ubuntu stands out relative to Fedora/RedHat, etc."
1786344,2018-08-26 07:11:24 UTC,"On 2018-08-26 03:19, Ping-Wu wrote:

> 2.  The input method dialog window is also seriously flawed.  It has
> improved somewhat from my initial post, but very awkward to use, if
> at all.  It is difficult to explain & you should try it yourself to
> see how bad the problem is.
"
1786344,2018-08-28 18:07:14 UTC,"I downgraded gnome-control-center in my Cosmic installation to version 1:3.28.2-0ubuntu0.18.04.2, and then Intelligent Pinyin was shown as one of the Chinese input source options as expected. So item 2 above is most likely a gnome-control-center issue."
1786344,2018-08-28 20:02:24 UTC,"I am most interested in the LiveUSB (iso image).  This is the only way I
can interest my friends to try Ubuntu.  I will try to install the 18.10
daily built probably over this weekend, but, again, the iso image is the
only marketing tool, as I can never induce anyone to try to do the actual
installation on their machine."
1786344,2019-07-11 09:27:06 UTC,This bug was fixed in the package gnome-settings-daemon - 3.28.1-0ubuntu1.3
1786344,2018-09-04 14:18:03 UTC,"Andy, could you have a look?"
1786344,2018-09-24 17:31:14 UTC,"Tested 0923 daily built. When booted under the ""简体中文"" （simplified Chinese） locale, ""汉语“ (Chinese) was shown as the default input method, but still cannot input Chinese."
1786344,2018-09-25 14:05:40 UTC,"not marking as a release blocker, but andrea is still working on this as assigned"
1786344,2018-10-14 20:16:40 UTC,"@Andrea: When you get at this bug, please note bug #1796722 which was marked as a duplicate of this one. The duplicate does include details in the bug description which may be valuable to understand the nature of the issue."
1786344,2018-12-13 18:41:37 UTC,"Ubuntu 18.10. Initial install in en_US.  When I tried to create a new user with zh_CN environment, I only had the option of choosing 中国（香港）“China (Hong Kong)"".  This should be corrected to allow users to choose ""China""."
1786344,2019-06-11 13:55:40 UTC,"@Gunnar, we discussed it in the meeting and decided it was not important to rls track, that doesn't mean it can't be fixed/SRUed though (also in the futur, please don't do direct nomination without assignement, either you plan to fix it yourself and then you can assign the bug to you or use rls-nn-incoming tagging)"
1786344,2018-08-27 21:52:01 UTC,"I checked out the 2018-08-27 ISO, and made these observations:"
1786344,2018-08-29 14:56:46 UTC,The g-c-c task moved to separate bug report (bug #1789665).
1786346,2018-08-24 04:06:58 UTC,"Folks,"
1786346,2018-09-24 14:46:36 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1786346,2018-09-21 16:16:41 UTC,"This should be fixed in the GA of Rocky AFAIK, and is being backported to the other branches (releases pending in the next day or so)."
1786346,2018-09-21 15:01:51 UTC,Has this bug been resolved? And in what version of nova?
1786346,2018-09-18 22:49:54 UTC,"Reviewed:  https://review.openstack.org/590814
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=79a74d8185ed99be0e5041724f32af82ad8fe8d9
Submitter: Zuul
Branch:    master"
1786346,2018-09-14 05:27:20 UTC,"Reviewed:  https://review.openstack.org/591735
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bfe89fec4669df6f4ac48dbb56fde3db0a24cbac
Submitter: Zuul
Branch:    stable/queens"
1786346,2019-03-22 03:48:49 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1786346,2018-08-23 22:18:12 UTC,This is interesting I have two host compute-06 & compute-07
1786346,2018-08-23 20:37:06 UTC,"Today i have upgraded my nova to fix this patch but look like still i am seeing same issue, my live migration running slow, what else i should look for?"
1786346,2018-08-22 14:28:34 UTC,"For the record,"
1786346,2018-08-21 11:59:58 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc2 release candidate.
1786346,2018-08-15 23:16:59 UTC,"Reviewed:  https://review.openstack.org/591762
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b1b5a5eb96ec8f222e5bad9055ec7baeed9767cd
Submitter: Zuul
Branch:    stable/pike"
1786346,2018-08-15 17:32:12 UTC,"Reviewed:  https://review.openstack.org/591761
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dee99b1ed03de4b6ded94f3cf6d2ea7214bca93b
Submitter: Zuul
Branch:    stable/queens"
1786346,2018-08-14 18:19:23 UTC,"Reviewed:  https://review.openstack.org/591275
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=afd1c1e6e152b6337d6e71af1c908c73c847b6f3
Submitter: Zuul
Branch:    stable/rocky"
1786346,2018-08-14 15:32:12 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/591762"
1786346,2018-08-14 15:30:45 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/591761"
1786346,2018-08-13 15:52:49 UTC,"The bug is reported on Pike, why that has been reverted from master without to have clearly identified the root cause? Crying everywhere it's ""racy"" without any explanation does not really make sense, sorry."
1786346,2018-08-13 06:20:17 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/591275"
1786346,2018-08-13 03:58:37 UTC,"Reviewed:  https://review.openstack.org/590538
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=411c45842f6b4bef21710b4d7fa2f473976bc566
Submitter: Zuul
Branch:    master"
1786346,2018-08-10 16:23:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/590814"
1786346,2018-08-09 22:28:10 UTC,"Just adding a note here that given the poor user experience with live migrations running at 1MiB/s because of the racing, we've decided we need to remove the slow => fast live migration functionality for the release and are targeting the removal for RC2."
1786346,2018-08-09 21:56:07 UTC,Just some further clarification:
1786346,2018-08-09 21:43:28 UTC,"> By default we don't actually wait. That wait option was made False by default for backward
> compatibility with the todo to make it True by default in Stein.
"
1786346,2018-08-09 21:40:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/590538"
1786346,2018-08-09 21:35:50 UTC,This is the new option in rocky:
1786346,2018-08-09 21:33:12 UTC,"> On Rocky, we now always listen for that event a level up in the compute manager:
"
1786346,2018-08-09 21:29:36 UTC,I've got a test patch here:
1786346,2018-08-09 21:27:41 UTC,"This appears to be now fundamentally broken on Rocky, and racy on Queens and Pike. Below is the current thinking from live conversation and debugging of this with the reporter."
1786346,2018-09-24 14:46:56 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1786346,2018-10-17 09:42:40 UTC,How long does it usually take when those updates are available in the standard bionic apt repository?
1786352,2018-09-10 17:53:06 UTC,This bug was fixed in the package linux - 4.15.0-34.37
1786353,2018-08-25 16:30:24 UTC,"There are some additional settings in widelands.h, with a not for packagers to take care of it. The PPA will install the application into usr/share/applications and the data into usr/share/games/widelands"
1786353,2018-08-25 20:17:51 UTC,"There are extra settings in CMakeLists.txt with notes for packagers, I assume that's the file you meant and not widelands.h. These include WL_INSTALL_BASEDIR and WL_INSTALL_DATADIR. The DATADIR is respected properly as best I can tell, and WL_INSTALL_BASEDIR will set the location of the installation of files such as COPYING, CREDITS, ChangeLog as well as the doc folder for documentation. However, the binaries widelands, wl_map_info, wl_map_object_info and wl_render_richtext do not get installed in WL_INSTALL_BASEDIR. This is because the function ""wl_binary"", as defined in cmake/WlFunctions.cmake, makes no reference to WL_INSTALL_BASEDIR, and instead says ""install into CMAKE_INSTALL_PREFIX""."
1786353,2019-09-17 09:41:31 UTC,Migrated to https://github.com/widelands/widelands/issues/1710
1786359,2018-08-10 00:23:20 UTC,"The ""/"" character is reserved in KiCad for hierarchy separation.  Using it currently will cause many issues if used with hierarchical schematics."
1786359,2018-08-14 14:16:47 UTC,Please note that a tilde can be used to overline text to indicate active low signals.
1786359,2018-11-13 17:19:13 UTC,"Fix was deemed too risky for 5.1, but it's in my 6.0 tree."
1786361,2020-10-02 19:08:10 UTC,https://github.com/mixxxdj/mixxx/pull/3146
1786378,2018-08-10 07:39:13 UTC,"The cause has been found, the main reasons are as follows:
Nova and cinder use two different users when configuring rbd users. This problem is only caused by registering a key on libvirt."
1786381,2018-08-10 02:18:56 UTC,"This refers to Ubuntu 18.04.1 LTS. See attached screenshot, displaying this new requirement."
1786381,2019-08-13 11:24:46 UTC,https://github.com/CanonicalLtd/subiquity/pull/521
1786383,2018-08-10 07:58:56 UTC,"Could you add more information? What does ""multiple times"" mean - twice? 5 times? 100 times? Is it consistent - e.g., does it always happen on the Nth try? Are you running bootstrap in rapid succession?"
1786383,2018-08-10 02:40:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/590606"
1786384,2018-08-10 02:40:47 UTC,Complex example - partitions are configured as seen on the attached screenshot.
1786384,2018-08-10 02:54:15 UTC,"A less complex example, doing the same on Virtualbox with two virtual storages:"
1786384,2019-02-11 10:27:27 UTC,"You can just swap sata slots in VirtualBox for your two storages, so os will be booted normally."
1786384,2019-02-12 14:37:50 UTC,"Thanks for suggesting a workaround, Andrew."
1786384,2019-02-15 02:05:27 UTC,"Reproduced today on 18.04.2, with this configuration (within VirtualBox):"
1786384,2020-05-07 22:50:59 UTC,I think this stuff should be fixed now but am not completely sure...
1786384,2020-05-08 05:39:23 UTC,For the symmetric setup that we tested it works as expected. I.e. two disks have the same layout:
1786384,2020-06-17 09:43:50 UTC,Tentatively marking fix released. Please re-open if you disagree :)
1786386,2019-11-07 21:14:57 UTC,This is fixed in commit 8ddbb7156043b2c7e6e7abf2a92fd43d3a866dcd (Be more specific about which files are copied). Confirmed not able to reproduce now.
1786389,2018-12-22 12:53:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786391,2019-01-24 03:10:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786391,2019-01-24 05:29:23 UTC,"Still a problem in Ubuntu 18.10, mp3gain version 1.5.2-r2-6"
1786391,2019-01-24 05:37:40 UTC,"er, libasan0 Version: 4.8.5-4ubuntu9"
1786391,2020-10-09 03:11:03 UTC,this ppa has a working version of mp3gain for 20.04
1786395,2018-08-11 00:13:05 UTC,apport information
1786395,2018-08-11 00:13:03 UTC,apport information
1786395,2018-08-11 00:13:02 UTC,apport information
1786395,2018-08-11 00:13:01 UTC,apport information
1786395,2018-08-11 00:12:58 UTC,apport information
1786395,2018-08-11 00:12:56 UTC,apport information
1786395,2018-08-11 00:13:00 UTC,apport information
1786395,2018-08-11 00:12:54 UTC,apport information
1786395,2018-08-11 00:12:52 UTC,apport information
1786395,2018-08-11 00:12:51 UTC,apport information
1786395,2018-08-11 00:12:50 UTC,apport information
1786395,2018-08-10 04:08:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1786395,2018-08-11 00:12:55 UTC,apport information
1786399,2018-08-10 04:47:43 UTC,This may be applicable to the output from other commands. Worth a check when we come to do this work.
1786419,2018-08-10 08:51:27 UTC,apport information
1786419,2018-08-10 08:51:25 UTC,apport information
1786419,2018-08-10 08:51:24 UTC,apport information
1786419,2018-08-10 08:51:23 UTC,apport information
1786419,2018-08-10 08:51:06 UTC,apport information
1786419,2018-08-10 08:51:05 UTC,apport information
1786419,2018-08-10 08:51:04 UTC,apport information
1786419,2018-08-10 08:50:59 UTC,apport information
1786419,2018-08-10 08:51:02 UTC,apport information
1786419,2018-08-10 08:51:01 UTC,apport information
1786419,2018-08-10 08:50:59 UTC,apport information
1786419,2018-08-10 08:50:57 UTC,apport information
1786419,2018-08-10 08:50:56 UTC,apport information
1786419,2018-08-10 07:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1786419,2018-08-10 08:51:29 UTC,apport information
1786419,2018-08-10 08:51:03 UTC,apport information
1786419,2018-08-10 08:51:30 UTC,apport information
1786419,2018-08-10 08:51:31 UTC,apport information
1786419,2018-08-10 08:51:32 UTC,apport information
1786419,2018-08-10 08:51:33 UTC,apport information
1786419,2018-08-10 08:51:34 UTC,apport information
1786419,2018-08-10 08:51:35 UTC,apport information
1786419,2018-08-10 08:51:38 UTC,apport information
1786419,2018-08-10 08:51:40 UTC,apport information
1786419,2018-08-13 16:55:01 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1786425,2018-08-16 09:08:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786430,2018-10-30 06:51:36 UTC,I guess a file extension check would be a start.
1786430,2019-09-16 08:33:02 UTC,Migrated to https://github.com/widelands/widelands/issues/3302
1786430,2018-10-29 17:04:45 UTC,"While i generally agree, we should have some checks to prevent unwanted files. As far i remember SirVer talked about a map on the server which contained an unwanted file (text file or a script?)."
1786439,2018-09-01 01:44:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786439,2019-07-04 22:26:53 UTC,This will resolve the issue.  Ignore all error messages.
1786439,2019-07-04 22:29:46 UTC,Still better way
1786455,2018-08-10 10:48:13 UTC,"Looks like there may be something weird with the controller, given that other commands are failing:"
1786467,2019-11-05 22:09:41 UTC,"Mine was a false alarm. The printk() did not come from the kernel itself, but from a proprietary kernel module."
1786467,2019-11-05 20:03:50 UTC,This is still an issue in 2019.
1786467,2019-11-05 20:02:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786469,2018-08-10 13:17:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/590767"
1786469,2018-10-02 06:35:17 UTC,"Change abandoned by Xianjin Shao (<email address hidden>) on branch: master
Review: https://review.openstack.org/590767
Reason: No modifications are required here"
1786472,2018-08-10 13:06:15 UTC,Fix proposed: https://review.openstack.org/#/c/590763/
1786472,2018-08-22 13:33:43 UTC,This issue was fixed in the openstack/neutron-tempest-plugin 0.2.0 release.
1786476,2018-08-10 16:20:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1786476,2019-10-04 12:23:47 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1786476,2019-10-04 16:36:12 UTC,"Yes, it solved for me. Thank you!"
1786476,2019-10-04 16:52:11 UTC,Thanks for your reply. Closing as fixed.
1786479,2018-11-05 22:08:15 UTC,Problem resolved in openstack client version 3.16.1
1786479,2018-09-06 05:01:05 UTC,do you know if this backported to rocky ?
1786479,2018-09-05 21:07:20 UTC,this is fixed by commit 3e5a2d227c813937ad7ea23d334f7d23c1f8a2cc
1786479,2018-09-02 07:30:34 UTC,im using rocky and master deploying cloud with tripleo and have same issue
1786479,2018-08-22 20:26:06 UTC,"+1, reproduces on openstack client v3.14.0 & python-cinderclient-4.0.1:"
1786479,2018-09-05 12:22:54 UTC,"+1 same problem, fixed after reverting the mentioned commit"
1786489,2019-08-20 13:32:10 UTC,Actually I completely mis-understood NOENT - it does the exact opposite of what I thought it does ...
1786489,2019-09-11 15:14:16 UTC,+1 on the MIR side
1786489,2019-08-29 17:01:32 UTC,"Sorry, it was a leftover recommends on gstreamer libav, downgraded to a suggests now"
1786489,2019-08-28 17:00:27 UTC,"see https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
rygel tries to pull in 30+ other packages into main."
1786489,2019-08-28 07:14:49 UTC,"Now that all remarks have been addressed, I'm happy to give an official +1 from the MIR team side."
1786489,2019-08-22 16:01:58 UTC,"The Rygel recommends on gst-plugins-ugly has been lowered to a suggest, the review problems have been upstreamed and upstream acked the NOENT issue here. Sending back to the MIR team, we will backport the NOENT fix but otherwise I think it should be good to be acked on the MIR side now"
1786489,2019-08-20 13:01:07 UTC,"Current state appears to be that Desktop Team should look into the Recommends (gstreamer plugins-ugly), and someone have a review of the XML parser options (as pointed out in the security review, specifically for NOENT and RECOVER... maybe NONET should be added?)."
1786489,2019-08-14 11:52:09 UTC,"@Jens, yes I plan to do that (thanks for keeping an eye on launchpad btw ;-)"
1786489,2019-08-14 10:55:22 UTC,"I reviewed rygel 0.36.2-5ubuntu1 as checked in to eoan. This isn't a full security audit, but rather a quick gauge of maintainability."
1786489,2019-03-05 15:41:58 UTC,The multi-arching is done now (and synced to disco)
1786489,2018-12-07 08:01:04 UTC,"Ok, so to sum up, remaining work to do:
- Add multi-arch to the libs
- (optional) Run as autopkgtests to ensure vala doesn't break this build"
1786489,2018-12-04 00:10:26 UTC,This bug was fixed in the package rygel - 0.36.2-2
1786489,2018-12-03 16:04:17 UTC,"> * There are a lot of crash reports in launchpad. Those are several years old and shouldn't apply anymore.
> Maybe a little bit of cleanup of really old one, and looking at more recent ones will help once supported
> to review real new crashes (between launchpad and errors.ubuntu.com)?
"
1786489,2018-10-25 14:52:11 UTC,"* There are a lot of crash reports in launchpad. Those are several years old and shouldn't apply anymore. Maybe a little bit of cleanup of really old one, and looking at more recent ones will help once supported to review real new crashes (between launchpad and errors.ubuntu.com)?
* What is going to pull rygel on the iso: directly seeded or a recommends/deps somewhere? Note that there is as well rygel-tracker which shouldn't be promoted until tracker situation is deciphered.
* Some lintian warnings would be great to looked at, namely:
- W: rygel-2.6-dev: pkg-config-unavailable-for-cross-compilation (multiple of thm)
- W: rygel: uses-implicit-await-trigger interest /usr/lib/rygel-2.6 (line 1)
- W: rygel: uses-implicit-await-trigger interest rygel-restart (line 2)
* I guess rygel-preferences isn't going to be promoted, correct? (maybe we should list exactly the packages that are going to be promoted). It has a dep as linking on libgssdp-1.0-3, which is in universe.
* However rygel binary package has some dep issues as well:
 - dep on libgssdp-1.0-3 (gssdp source in universe) and libgupnp-1.0-4 (gupnp source in universe), which are not listed in the current MIR for the stack.
 - 2 recommends with its source in universe and not listed to be MIRed. They should be downgraded to Suggests, if possible: gstreamer1.0-libav and gstreamer1.0-plugins-ugly
* If we want to promote rygel-2.6-dev to main, there is again the libgupnp-1.0-dev dep as well which needs to be sorted out.
* librygel-server-2.6-2 is a dep of rygel, and depends as well on libgssdp-1.0-3 and libgupnp-1.0-4
* librygel-renderer-2.6-2 is a dep of rygel, and depends as well on libgupnp-1.0-4
* librygel-core-2.6-2 is a dep of rygel, and depends as well on libgssdp-1.0-3 and libgupnp-1.0-4
* some copyright are missing:
  - 2008-2009 Florian Brosch
  - 2012 Choe Hwanjin <email address hidden>
  - 2013 Cable Television Laboratories, Inc.
  - 2014 Jens Georg <email address hidden>
  - 2014 Atlantic PuffinPack AB.
  - 2017 Samuel CUELLA]
  - Intel Corporation copyright should be extended to 2013
  - Jens Georg copyright should be extended to 2016
I may have missed others but that should be about it."
1786489,2018-08-13 18:36:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786489,2019-08-14 11:40:47 UTC,Are you going to file upstream tickets for the relevant findings?
1786495,2019-03-30 19:21:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786495,2020-02-13 11:35:10 UTC,"Seems that it still breaks:
https://www.reddit.com/r/linuxhardware/comments/f37ypz/audio_stopped_working_after_upgrade_from_50037/"
1786495,2019-06-02 13:41:31 UTC,"I have the same problem on Ubuntu 19.10.
The fix of nic30 doesn't work for me."
1786495,2019-04-14 13:45:31 UTC,I found the fix. It seems funny but it is really fault of nvidia-driver-xxx. It somehow modifies power settings of the system. I am using latest Ubuntu 19.04 with 5.0.0-11-generic kernel but exactly same problem did happen wit any previous Ubuntu version and also with recent versions of Fedora.
1786495,2019-03-30 20:08:32 UTC,"I just found the ultimate debug tool for Intel HDA, https://git.alsa-project.org/?p=alsa.git;a=tree;f=hda-analyzer;hb=HEAD and alsa-tools-gui maybe it will help someone"
1786495,2018-08-13 04:11:57 UTC,"Try alsamixer, press F6 select HDA Intel PCH, then disable Auto-Mute. I attached my configuration on my M4800"
1786495,2019-03-30 19:27:21 UTC,"Same problem there, also Dell M4800, I am using latest ubuntu 18.10 and it was working until I installed latest nvidia-driver-418. I do not why. There is suspicious message in dmesg.
(If I uninstall the nvidia driver it is still not working and reinstalling of alsa-driver also did not help.)"
1786495,2019-02-17 18:07:07 UTC,"I have this same issue with Dell M6800. It works sometimes and after reboot, it stop working."
1786495,2020-10-31 07:45:03 UTC,"I have the same problem on Ubuntu 20.10.
nic30 solution works for me."
1786495,2020-12-25 13:23:37 UTC,I have a similar problem since today :
1786498,2018-08-21 13:29:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/594172"
1786498,2018-08-15 00:43:50 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/591872"
1786498,2019-03-22 03:48:51 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1786498,2018-08-21 17:37:15 UTC,"Reviewed:  https://review.openstack.org/594172
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2b46354d5ab6d59790e69c44bc36a17074155774
Submitter: Zuul
Branch:    master"
1786498,2018-08-21 11:59:57 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc2 release candidate.
1786498,2018-08-10 15:29:01 UTC,started in: https://review.openstack.org/#/c/590445/
1786498,2018-08-14 09:19:31 UTC,"Reviewed:  https://review.openstack.org/590445
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94617a71761710544cf9505ffda5b6403a645a7e
Submitter: Zuul
Branch:    master"
1786498,2018-08-16 05:16:18 UTC,"Reviewed:  https://review.openstack.org/591872
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97e7087ac329c5b6fc77ddd76d2007e03866e00f
Submitter: Zuul
Branch:    stable/rocky"
1786501,2018-10-26 20:51:45 UTC,This may be a duplicate of bug 1790169.
1786501,2020-03-31 20:43:17 UTC,Column sort for Pending Patrons is still broken in 3.5beta.  Columns don't sort on click or by using the sort priority.
1786509,2018-08-22 00:02:28 UTC,"I'm also having this issue on Ubuntu Mate 18.04.1
Plank Version: 0.11.4
Window Manager: Compiz
Desktop Environment: Mate 1.20.1"
1786509,2018-08-24 01:51:53 UTC,The bug also seems to happen when the dock is placed at the top also. Checked right side and bottom again and they're the only sides that seem to work correctly.
1786516,2019-11-05 07:51:01 UTC,Seems had issue with particular update. After updating Ubuntu to new version solved the issue.
1786516,2019-11-05 04:17:27 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1786516,2019-09-05 09:18:57 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Do you still see a problem related to the one that you reported when using currently supported versions of Ubuntu and Firefox?
1786516,2019-11-05 07:49:09 UTC,Hi
1786524,2020-12-03 15:32:36 UTC,Added a small tweak to add a guardian to the list of columns.
1786524,2020-08-14 21:25:43 UTC,I've been working with a few of our libraries who need to do periodic bulk loading and updating.  I have a generic script in the Equinox migration tools repo that has worked for several libraries already and covers a number of use cases.  I want to kick the tires on it more but intend to submit it for consideration for this.
1786524,2020-11-11 17:05:20 UTC,patch at :
1786524,2020-06-09 20:26:23 UTC,"Chris Sharp, Terran McCanna, and Tiffany Little presented on this topic at the 2020 Evergreen Online Conference.  Here is Chris' script: https://git.gapines.org/csharp/student-cards"
1786524,2020-10-01 12:43:03 UTC,Thinking about this some more as an Evergreen feature there is some reworking to do for a proper 3.6+ patch version.  The biggest is the in database logging.  The current script assumes no native Evergreen tracking of events and creates a logging table in schema patron_loader to log events such as when a match point can not be found for an account and so on.
1786524,2020-09-14 15:35:11 UTC,"I'm not putting a pull request on this yet because I'd like feedback on use cases, utility, etc... I have used it for three libraries at this point and am pretty happy with it."
1786524,2020-11-04 21:22:50 UTC,"This was discussed during the Hack-A-Way and the indication was that people would want to use the reporter to access logs.  So, I will be updating the branch soon with new features I've already put into place in migration-tools and making adding the tracking log to the actor schema and appropriate entries to fm_IDL.xml with a (cross fingers) target of inclusion in 3.7"
1786524,2020-06-09 21:01:23 UTC,It would be really handy to have a user interface for this so that the burden of setting up each school's info and connection data wasn't solely on the system admin.
1786528,2018-12-07 22:45:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786532,2018-12-12 11:02:18 UTC,"The settings is not a service and not involved in restoring configs after boot, it's just an interface to change the options. Removing g-c-c since the problem is not here"
1786543,2018-10-18 19:32:56 UTC,I have removed the LZ4 symbols in 1.9.1+dfsg-6 (in Debian unstable). So this should be fixed in the next Ubuntu version.
1786543,2018-10-10 14:52:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786543,2018-10-10 15:04:07 UTC,I believe this is affecting compilation of PCL's kdtree flann. So basically flann has it's own copy of lz4.h and it collides with the system package lz4.h?
1786545,2018-09-12 17:43:46 UTC,"Evergreen Release 3.0.11
Browser Chrome"
1786548,2018-08-10 20:44:37 UTC,Confirmed in Evergreen version 3.0 and 3.1. Affects Web Client and XUL.
1786548,2021-02-12 21:13:06 UTC,Confirmed in Evergreen 3-4-5.
1786552,2019-06-21 23:26:13 UTC,Release notes pushed to working branch.  This is ready for review.
1786552,2019-09-06 21:43:47 UTC,"Pushed to master for inclusion in the 3.4 beta. Thanks, Jeff!"
1786552,2019-02-09 00:11:49 UTC,"I've pushed an additional commit to the same branch, adding a new ""restrict_by_home_ou"" setting to auth_proxy config.  When enabled, if the login request includes an org param, the authenticator will refuse to authenticate a user unless their home OU matches or is a descendant of that org; login fails and auth_proxy proceeds to the next configured authenticator."
1786552,2019-01-10 23:18:26 UTC,Force-pushed a small change (scoping issue with $ldap_search var) to the same branch.  Works for me in testing.
1786552,2018-10-30 22:12:11 UTC,Working branch user/jeffdavis/lp1786552-ldap-bind-user has an untested first pass at implementing this feature:
1786552,2019-06-21 06:54:21 UTC,"I've pushed one more update to the working branch related to the restrict_by_home_ou setting.  Previously the setting was based on the login org param.  But it makes more sense to base it on the authenticator's org units, since that is what tells us which libraries the authenticator is valid for."
1786566,2019-09-19 14:47:29 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1786568,2018-09-21 08:07:29 UTC,"In #5 there was a question regarding potential reasons of different performance in debug and build releases. You are right regarding the primary cause, anything rendered on TARGET_OVERLAY redraws everything."
1786568,2018-09-21 12:17:46 UTC,"It keeps both - each target is rendered to a separate framebuffer and then compositor combines the their contents. If a target has not been touched, then it is not refreshed but displayed using the framebuffer contents from the previous frame."
1786568,2018-09-21 11:51:47 UTC,"Does the video card keep the last frame, or _only_ cached vertices?"
1786568,2018-09-20 10:16:26 UTC,I'm not sure it has anything to do with debug/release.  It's much slower because LAYER_SELECT_OVERLAY is not cached (so we draw it every time).
1786568,2018-09-21 12:44:17 UTC,Cool; I'll leave this open then.  (I might even try to get my head around OpenGL at some point and give it a whack.)
1786568,2018-09-19 23:14:49 UTC,"I don't really know, at least I see no logs in console output.
Initially I though some code was better optimized in release build."
1786568,2018-09-19 21:46:19 UTC,Interesting.  Anyone know why this would be slower in debug?  (Are we spitting out a bunch of log statements or something?)
1786568,2018-08-27 17:19:32 UTC,"I've checked the current master in release build and it works fine.
The slowness is still noticeable in a debug build."
1786568,2018-08-24 17:45:52 UTC,"The zooming does seem to be slower in modern canvas when the entire board is selected.  As soon as I deselect everything, the zooming is faster.  This is on my Debian testing build."
1786568,2018-08-24 16:56:16 UTC,Is this still an issue with current nightlies?
1786568,2018-09-20 06:28:51 UTC,"I would point at optimization and wxASSERTs. There is also a bunch of wxTRACE, but I *hope* they do not decrease performance until enabled."
1786568,2018-08-11 18:50:03 UTC,"Confirmed on Linux 16.04 since release of 2018-07-27 (I didn't remember before).
Also this happens when appended new board (summarizing, every that a large number of elements are selected)."
1786572,2018-08-11 01:13:24 UTC,"StacktraceTop:
 __libc_read (fd=12, buf=buf@entry=0x5573feb1e1b0, nbytes=nbytes@entry=1024) at ../sysdeps/unix/sysv/linux/read.c:27
 read (__nbytes=1024, __buf=0x5573feb1e1b0, __fd=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
 g_io_unix_read (channel=0x5573feb1d120, buf=0x5573feb1e1b0 """", count=1024, bytes_read=0x7ffe2ef55f80, err=0x7ffe2ef56060) at ../../../../glib/giounix.c:192
 g_io_channel_fill_buffer (channel=channel@entry=0x5573feb1d120, err=err@entry=0x7ffe2ef56060) at ../../../../glib/giochannel.c:1477
 g_io_channel_read_chars (channel=0x5573feb1d120, buf=0x7f1fc400fed0 ""\300\221\277\376sU"", count=8, bytes_read=bytes_read@entry=0x7ffe2ef56058, error=error@entry=0x7ffe2ef56060) at ../../../../glib/giochannel.c:2026"
1786574,2019-04-16 07:36:57 UTC,"Nope, I need to re-modprobe the psmouse again to make my touchpad work again"
1786574,2019-04-16 04:39:59 UTC,"@fenris
Adding back i2c_i801 to blacklist can make the touchpad work again? Is this what you mean?"
1786574,2019-04-14 20:10:31 UTC,"@aaronMa,"
1786574,2019-03-01 03:23:26 UTC,"Confirmed with three users who had regressions (bug 1802689 and bug 1802135) through email, and confirmed that our latest kernels no longer manifest the regressions even after i2c_i801 has been removed from blacklist."
1786574,2019-04-17 04:25:28 UTC,@Khairul
1786574,2019-02-27 10:32:59 UTC,"@midnightflash
Please provide more details on the issues you see so that we can help you. As Aaron said, please upload the dmesg from both your X11e and X250."
1786574,2019-02-20 15:25:49 UTC,@midnightflash
1786574,2019-04-11 03:05:32 UTC,verification-done-disco
1786574,2019-04-17 12:56:08 UTC,"@AaronMa,
after recent updates and new kernel 5.0.0-13-generic , I can't reproduce the issue again."
1786574,2019-05-09 14:21:34 UTC,"Hi, Khairul,
Could you try the attached patch?"
1786574,2019-05-09 14:05:53 UTC,Hi Khairul:
1786574,2019-05-09 16:37:50 UTC,"Hi Aaron,
Thanks for your prompt replied."
1786574,2019-05-10 12:49:00 UTC,"Hi Khairul,
Could you install attached dkms deb?"
1786574,2019-05-10 15:35:38 UTC,"Khairul,"
1786574,2019-05-14 02:35:11 UTC,"Hi @Aaron & @Kai-Heng,
I've installed the package and reboot + tried suspend 1 time."
1786574,2019-10-04 17:43:33 UTC,This bug is present in Ubuntu 19.10
1786574,2019-10-09 15:59:28 UTC,"Julian, what exactly is the problem you see in 19.10?"
1786574,2019-10-13 09:01:36 UTC,"i'm having the issue again, i run the evtest and the output as attached"
1786574,2019-10-13 14:22:31 UTC,Hi Khairul and Julian:
1786574,2019-05-09 12:38:10 UTC,Im still having this issue when booting from hibernate :(
1786574,2019-02-20 15:10:29 UTC,I'm also affected on two machines. (X11e and X250)
1786574,2019-04-08 23:45:42 UTC,This bug was fixed in the package kmod - 25-1ubuntu3
1786574,2018-12-03 02:27:31 UTC,This bug was fixed in the package kmod - 25-1ubuntu2
1786574,2019-02-20 14:33:48 UTC,"#1802135 is fixed in kernel patch:
https://lists.ubuntu.com/archives/kernel-team/2018-November/096852.html"
1786574,2018-08-11 06:09:51 UTC,"The real bug should not be bug #10306, but is bug #16602."
1786574,2018-08-22 03:51:06 UTC,Is there anything I should do to move this bug forward? Thanks.
1786574,2018-08-28 15:02:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786574,2018-08-28 15:18:26 UTC,@Anthony - should someone on the kernel team review your proposed merge/change rather than the server team?
1786574,2018-08-28 15:40:11 UTC,"Yes, probably, I actually have pinged apw about this bug, so shouldn't hurt to add him as reviewer. I may also try to find someone to upload a package later."
1786574,2018-08-29 02:38:42 UTC,LP: #1722478 should be the earliest report about this issue.
1786574,2018-09-17 15:50:58 UTC,I did prepare some slightly modified proposal for this and will try to get things progressing tomorrow.
1786574,2018-09-19 13:48:03 UTC,"Hi,
first of all this package seems to have quite some issues in the merges that are done - it doesn't list all remaining changes and the i2c blacklist is one of them.
It comes from like back in 2005 and I agree, it might or is safe to be removed."
1786574,2018-09-19 15:01:40 UTC,Resume issue should be fixed by kernel driver or other WA than blacklist a kernel module.
1786574,2018-10-04 04:16:59 UTC,"On Wed, 19 Sep 2018 at 22:01,  Christian Ehrhardt  <
<email address hidden>> wrote:"
1786574,2018-11-11 00:29:24 UTC,Another regression: bug 1802689
1786574,2018-10-29 08:45:13 UTC,"Hello AaronMa, or anyone else affected,"
1786574,2018-11-08 15:22:08 UTC,This seems to have caused a regression see bug 1802135.
1786574,2018-11-05 21:56:25 UTC,This bug was fixed in the package kmod - 24-1ubuntu3.1
1786574,2018-11-05 21:56:05 UTC,"The verification of the Stable Release Update for kmod has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1786574,2018-11-05 21:55:58 UTC,This bug was fixed in the package kmod - 25-1ubuntu1.1
1786574,2018-11-05 21:56:41 UTC,This bug was fixed in the package kmod - 22-1ubuntu5.1
1786574,2018-10-30 13:46:05 UTC,@AaronMa - Could you please add some verification details to the bug report?
1786574,2018-10-29 08:48:04 UTC,"Hello AaronMa, or anyone else affected,"
1786574,2018-10-29 08:47:11 UTC,"Hello AaronMa, or anyone else affected,"
1786574,2018-10-30 14:22:47 UTC,After update to new kmod in proposed and reboot:
1786574,2018-10-24 00:10:20 UTC,"Oh somehow I failed to notice the merge proposal on here, sorry about that. It's all fairly trivial though..."
1786576,2018-08-29 22:54:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786581,2018-08-11 03:22:26 UTC,I'm using OR x4168.
1786591,2018-08-11 07:25:01 UTC,"Additional info: this bug appeared early this year (2018). Before that, there was no trouble saving without a certificate."
1786591,2018-08-13 13:59:37 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1786596,2018-10-29 10:44:48 UTC,"Hi,"
1786596,2020-02-06 22:56:35 UTC,"Hi Mauro,"
1786599,2018-08-13 09:08:43 UTC,"#************************************************************
#*                     MadGraph5_aMC@NLO                    *
#*                                                          *
#*                *                       *                 *
#*                  *        * *        *                   *
#*                    * * * * 5 * * * *                     *
#*                  *        * *        *                   *
#*                *                       *                 *
#*                                                          *
#*                                                          *
#*         VERSION 2.6.2.beta            2018-04-02         *
#*                                                          *
#*    The MadGraph5_aMC@NLO Development Team - Find us at   *
#*    https://server06.fynu.ucl.ac.be/projects/madgraph     *
#*                                                          *
#************************************************************
#*                                                          *
#*               Command File for MadGraph5_aMC@NLO         *
#*                                                          *
#*     run as ./bin/mg5_aMC  filename                       *
#*                                                          *
#************************************************************
set default_unset_couplings 99
set group_subprocesses Auto
set ignore_six_quark_processes False
set loop_optimized_output True
set loop_color_flows False
set gauge unitary
set complex_mass_scheme False
set max_npoint_for_channel 0
import model sm
define p = g u c d s u~ c~ d~ s~
define j = g u c d s u~ c~ d~ s~
define l+ = e+ mu+
define l- = e- mu-
define vl = ve vm vt
define vl~ = ve~ vm~ vt~
install PPPC4DMID
launch
launch
launch
launch
launch dark1
Traceback (most recent call last):
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/extended_cmd.py"", line 1501, in onecmd
    return self.onecmd_orig(line, **opt)
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/extended_cmd.py"", line 1450, in onecmd_orig
    return func(arg, **opt)
  File ""/home/ygh/program/MadDM_v3.0.beta/PLUGIN/maddm/maddm_interface.py"", line 717, in do_launch
    self._MDM.exec_cmd('launch ' + line.replace(args[1], ''))
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/extended_cmd.py"", line 1528, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/extended_cmd.py"", line 1450, in onecmd_orig
    return func(arg, **opt)
  File ""/home/ygh/program/MadDM_v3.0.beta/PLUGIN/maddm/maddm_run_interface.py"", line 838, in do_launch
    self.save_remove_output(scan = True) ## this is to remove or save spectra, not the scan summary file!
  File ""/home/ygh/program/MadDM_v3.0.beta/PLUGIN/maddm/maddm_run_interface.py"", line 1837, in save_remove_output
    shutil.rmtree(out_dir)
  File ""/usr/lib/python2.7/shutil.py"", line 239, in rmtree
    onerror(os.listdir, path, sys.exc_info())
  File ""/usr/lib/python2.7/shutil.py"", line 237, in rmtree
    names = os.listdir(path)
OSError: [Errno 2] No such file or directory: '/home/ygh/program/MadDM_v3...."
1786599,2018-08-13 09:21:57 UTC,"ygh@ygh:~/program/MG5_aMC_v3_0_0$ ./bin/maddm.py
Plugin PLUGIN.maddm has marked as NOT being validated with this version.
It has been validated for the last time with version: 2.6.3
            ====================================================
            |                    MadDM v3.0                     |
            ===================================================="
1786599,2018-10-04 10:02:49 UTC,"Hi,"
1786600,2018-08-13 07:56:39 UTC,"Hi, do you really want to use host ntp during bootstrap?"
1786601,2019-05-19 04:18:06 UTC,[Expired for OpenLP because there has been no activity for 60 days.]
1786601,2018-08-11 09:48:13 UTC,The relevant part in the settings looks like this
1786601,2019-03-19 23:07:39 UTC,I'm not sure if I can replicate it and I don't have any complete settings. I shared what my settings looked like...
1786601,2019-03-16 08:04:08 UTC,"Simon, I cannot replicate this. I don't suppose you can share an old copy of the settings file could you? You can find backed up versions in ~/.local/share/openlp/{time/date}.config"
1786607,2018-11-28 14:43:12 UTC,"Thank you for your bug report, that's similar to what is described on https://bugzilla.gnome.org/show_bug.cgi?id=792442"
1786608,2018-08-27 07:47:59 UTC,"The verification of the Stable Release Update for gnome-shell-extension-system-monitor has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1786608,2018-08-27 07:47:36 UTC,"Ah indeed, missed the mention that it's fixed in master. Anyway, all good."
1786608,2018-08-20 20:06:32 UTC,35-1ubuntu0.18.04.1 fixes the issue.
1786608,2018-08-27 07:47:55 UTC,This bug was fixed in the package gnome-shell-extension-system-monitor - 35-1ubuntu0.18.04.1
1786608,2018-08-20 15:29:24 UTC,"Seeing that upstream isn't really much active nowadays, not blocking on this getting approved upstream. Accepting."
1786608,2018-08-11 12:35:38 UTC,This bug was fixed in the package gnome-shell-extension-system-monitor - 35-1ubuntu1
1786608,2018-08-11 12:11:21 UTC,Uploaded to bionic-proposed.
1786608,2018-08-11 12:03:32 UTC,Uploaded to cosmic.
1786608,2018-08-20 17:18:39 UTC,"To be clear, the patch is from upstream master."
1786608,2018-08-20 15:29:43 UTC,"Hello Jamie, or anyone else affected,"
1786609,2018-08-14 17:02:18 UTC,"This is a feature request. I wonder if it could be accomplished with an extension, rather than a direct code change in caja."
1786610,2018-08-11 12:17:06 UTC,Please change title to:  Cloudy/Murky
1786610,2018-08-11 12:19:52 UTC,one screen shot added here
1786610,2018-08-11 12:49:57 UTC,added missing letters in subject line; It might be my keyboard; I'm still investigating.
1786611,2018-08-11 16:11:58 UTC,https://github.com/retext-project/retext/issues/381
1786611,2021-02-11 18:19:14 UTC,This is now fixed in retext 7.2.0-1 in Hirsute:
1786623,2018-08-27 15:00:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786631,2018-10-06 12:55:40 UTC,"I get the same error message when attempting to start anki 2.1.0+dfsg-1 on Ubuntu Cosmic. Since python3-distutils is now a required dependency, that is installed."
1786631,2019-04-06 13:16:34 UTC,Same issue here - still no fix ?
1786631,2018-08-17 17:53:19 UTC,Do you have the python3-distutils package installed?
1786631,2018-12-11 07:30:34 UTC,"I could build, install, and use anki 2.1.6+dfsg~beta2-1 from Debian Sid without issue. ""Use"" refers to text-based flashcards (including Japanese characters) only, I didn't test other features (e.g. sync). I hope the update can be imported into Ubuntu soon."
1786634,2018-08-11 18:26:54 UTC,"StacktraceTop:
 pixman_rasterize_edges (image=image@entry=0x55bbb91b0190, l=l@entry=0x7ffc13cfefa0, r=r@entry=0x7ffc13cfefd0, t=t@entry=2185, b=b@entry=718711) at ../../pixman/pixman-edge.c:376
 pixman_rasterize_trapezoid (image=image@entry=0x55bbb91b0190, trap=trap@entry=0x55bbb90977c8, x_off=0, y_off=0) at ../../pixman/pixman-trap.c:386
 wfbRasterizeTrapezoid (pPicture=0x55bbb8974f40, trap=0x55bbb90977c8, x_off=0, y_off=0) at ../../../../fb/fbtrap.c:60
 ?? () from /tmp/apport_sandbox_wkejof0b/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so
 ?? ()"
1786639,2020-11-09 19:24:24 UTC,I got the following repeating pattern which occupies most of the syslog (probably 99%) Found syslog = 11.6 GB and syslog.1 =61.1 GB. It loooks like every 5 seconds i get a grouping of 4 messages.
1786639,2020-11-09 19:25:03 UTC,Previous comment I have Ubuntu 20.04 running on a dell XPS
1786639,2018-08-11 19:19:32 UTC,Some related info I found online:
1786644,2018-09-26 10:44:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786650,2018-08-11 23:13:11 UTC,"StacktraceTop:
 tcache_get (tc_idx=0) at malloc.c:2943
 __GI___libc_malloc (bytes=bytes@entry=1) at malloc.c:3050
 g_malloc (n_bytes=n_bytes@entry=1) at ../../../../glib/gmem.c:99
 g_strdup (str=str@entry=0x55c52579e7a9 """") at ../../../../glib/gstrfuncs.c:363
 g_strsplit (string=string@entry=0x55c52579e770 ""standard::is-hidden,standard::is-backup,access::can-read,"", delimiter=delimiter@entry=0x7f66ac512cab "","", max_tokens=<optimized out>, max_tokens@entry=-1) at ../../../../glib/gstrfuncs.c:2361"
1786650,2018-08-28 11:05:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786651,2018-10-28 17:51:17 UTC,"No, the GUI works just right."
1786653,2018-08-12 08:20:10 UTC,Think that is Intel graphics... is it?
1786653,2018-08-12 08:24:15 UTC,This blog though talks about lodpi vs hidpi and notifications
1786654,2018-09-12 11:34:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786654,2019-12-04 12:22:36 UTC,"My impression here is that radioclk was not functional in the first place, most likely because it was not configured or lacked the required hardware:"
1786654,2020-02-03 04:17:30 UTC,[Expired for radioclk (Ubuntu) because there has been no activity for 60 days.]
1786655,2019-05-30 03:16:29 UTC,We don't have any code in place that would specifically create these files. Can you let me know what desktop you're running so I can look further?
1786655,2020-06-21 11:20:39 UTC,"Hi, I just tested this again. I'm using Xubuntu 20.04, menulibre 2.2.1-1."
1786660,2019-09-12 13:58:38 UTC,"This is new functionality, and as mentioned quite a big code change - please raise a blueprint."
1786664,2018-08-13 20:50:41 UTC,"I have installed the v4.18.rc8-generic kernel (uname: 4.18.0-041800rc8-generic)
Unfortunately the problem remains.
Although the driver reports itself as the exact same version as in the Ubuntu kernel (info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p154) it produced a slightly different dmesg output which might be of help here.
I do not know how to set tags here, I would ask you to set 'kernel-bug-exists-upstream'."
1786664,2018-08-12 07:00:05 UTC,This change was made by a bot.
1786664,2018-08-12 07:01:30 UTC,"Is it possible that the idle power state of the driver is broken?
Referring to this output in the dmesg:
...
[  753.636901] mwifiex_pcie 0000:01:00.0: Firmware wakeup failed
..."
1786664,2018-08-13 16:52:36 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1786673,2018-08-12 08:39:49 UTC,"StacktraceTop:
 rtsFatalInternalErrorFn ()
 barf ()
 evacuate1 ()
 scavenge_loop1 ()
 scavenge_until_all_done ()"
1786676,2018-08-12 10:30:03 UTC,This change was made by a bot.
1786685,2018-08-13 02:29:04 UTC,Can you please attach (at least some of) the system log with the messages you describe?
1786685,2018-08-15 01:30:38 UTC,Thanks.
1786688,2019-01-26 15:39:13 UTC,"The first step is fixed in cryptsetup, would be nice if second part about partprobe was also built-in"
1786689,2018-11-16 17:21:08 UTC,"Windows 7 Enterprise (SP1)
Inkscape 0.92.3 (2405546, 2018-03-11
LaserJet Pro M402dne"
1786699,2021-01-14 20:30:47 UTC,"The attachment ""This patch is against the vmdb2-0.19 upstream tag"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1786699,2021-01-14 20:16:59 UTC,I've sent a patch to https://gitlab.com/larswirzenius/vmdb2/-/issues/36#note_485816538 which enables support for Ubuntu and Debian
1786699,2020-07-21 17:01:41 UTC,"This also keeps me from using vmdb2 to build a custom Ubuntu image. FWIW I opened https://gitlab.com/larswirzenius/vmdb2/-/issues/36 to discuss fixing this from the vmdb2 side instead, which might be an alternative solution."
1786699,2020-05-06 15:51:31 UTC,"Hello,"
1786699,2019-12-08 12:23:38 UTC,"(To be clear, I disagree with Mathieu and agree with Antonio.)"
1786699,2019-12-08 17:27:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786699,2019-12-08 20:31:35 UTC,Thanks.
1786699,2018-10-03 14:36:05 UTC,"I disagree. This needs to be fixed in Debian as well -- none of the options are crazy hacks, they are taken as explicit decisions meant to fix actual problems that people are having."
1786699,2019-12-08 12:23:14 UTC,"As the Debian maintainer, I entirely disagree.  Even though it's now the default behaviour, --force-extra-removable should be kept as a no-op, because it's used by other software.  Interfaces matter."
1786699,2019-12-08 16:57:12 UTC,"I have an issue with leaving cruft around instead of actively fixing whatever depends on old behavior; months from now, or even years, we'll still have this switch around that does nothing -- that's more confusing for users than actively moving forward."
1786701,2018-08-13 13:09:31 UTC,I've added a small note on the release notes to mention the xorg case.  If someone can answer the other questions I will add that information as well if appropriate.
1786701,2020-06-05 19:30:05 UTC,"Will: Thanks! I can't seem to find this change you made anymore, though. Maybe it was reverted since? I was looking for the string 'xorg' (case insensitive) on all of
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/18.04
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/ChangeSummary/18.04.1
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/ChangeSummary/18.04.2
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/ChangeSummary/18.04.3
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/ChangeSummary/18.04.4"
1786702,2018-08-12 16:32:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786702,2018-08-27 14:34:07 UTC,Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-characters/issues/36
1786702,2020-03-10 14:00:20 UTC,Confirming fixed with gnome-characters 3.34.0-1 in Ubuntu 20.04.
1786705,2019-04-02 07:21:26 UTC,"Hello,"
1786705,2019-06-02 04:17:22 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1786713,2018-08-15 05:35:44 UTC,"ohh sorry, 4.15.18"
1786713,2018-08-14 16:16:38 UTC,@Tim-
1786713,2018-08-13 20:02:34 UTC,"btw making initramfs is the problem, not the kernel itself."
1786713,2018-08-13 16:51:24 UTC,Can you expand upon why it is not working?  Was it once working and now it is not?  Are you seeing specific errors?
1786713,2018-08-12 21:20:11 UTC,there are no logs.
1786713,2018-08-13 17:19:44 UTC,"I don't know, why this is not working.
With kernel source 4.15.17 there was no problem.
I didn't see errors while compiling 4.15.18."
1786713,2018-08-12 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1786719,2018-08-14 14:49:12 UTC,Thank you for reporting this. Could you please tell us the exact two versions you installed (and in what particular order) ?
1786730,2018-08-13 16:55:50 UTC,I wonder if this might be sufficiently covered by recommending that the delay_reaping setting be sufficiently large that container replication will have settled... though the advent of deep containers makes that even harder to reason about.
1786752,2018-08-13 09:30:05 UTC,This change was made by a bot.
1786752,2019-03-20 04:16:47 UTC,"We have upgraded to kernel v4.20.15 and its going to be more than a week, we are not seeing any more call traces in this kernel logs. We will watch for few more days and i will report back here."
1786752,2019-03-06 09:31:21 UTC,"Seems like it's fixed by this commit:
commit 542fbda0f08f1cbbc250f9e59f7537649651d0c8
Author: Florian Westphal <email address hidden>
Date:   Tue Dec 11 07:45:29 2018 +0100"
1786752,2019-03-04 08:16:34 UTC,"# lspci
00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 (rev 01)
00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01)
00:02.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01)
00:02.2 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01)
00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01)
00:04.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 0 (rev 01)
00:04.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 1 (rev 01)
00:04.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 2 (rev 01)
00:04.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 3 (rev 01)
00:04.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 4 (rev 01)
00:04.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 5 (rev 01)
00:04.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 6 (rev 01)
00:04.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Crystal Beach DMA Channel 7 (rev 01)
00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management (rev 01)
00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug (rev 01)
00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01)
00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC (rev 01)
00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05)
00:11.1 SMBus: Intel Corporation C610/X99 series chipset MS SMBus 0 (rev 05)
00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05)
00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05)
00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #1 (rev 05)
00:16.1 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #2 (rev 05)
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 (rev 05)
00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 (rev d5)
00:1c.3 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #4 (rev d5)
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation C610/X99 serie..."
1786752,2020-03-06 12:58:57 UTC,"Hi, sorry to ask non related questions. But could youe please teach how did you identity there is a negative refcnts from the dmesg? thanks..."
1786752,2019-01-08 04:58:55 UTC,"Just to follow up , on behalf of Juergen. Do we have any progress with this bug ?"
1786752,2018-12-09 08:48:50 UTC,"Hi
Do you find fix for this bug
I use latest kernel 4.19.8 and have same problem see down
i use pppoe with 1k+ users if i activate shaper with hfsc and imq machine crash and reboot
after stop shaper for test mashine only send in dmesg bug error mesg."
1786752,2018-08-13 20:05:13 UTC,The issue still is visible with the latest mainline kernel; see attached.
1786752,2018-08-13 16:56:24 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1786752,2019-03-04 07:49:10 UTC,"We have upgraded the latest kernel and even occasionally we facing this call traces and CPU tainted,"
1786756,2019-10-03 19:14:33 UTC,"Fixed in Ubuntu 18.04 LTS bionic, so I propose to close this."
1786757,2018-08-14 05:32:16 UTC,Thanks.
1786757,2019-01-07 03:54:24 UTC,"Any work on this bug will occur upstream, so you should ask there instead:"
1786757,2019-01-07 03:41:28 UTC,Any update on this bug?
1786757,2018-10-01 07:31:02 UTC,Do we have an update on this issue?
1786757,2018-08-14 06:50:22 UTC,"Got it, thanks:
https://gitlab.gnome.org/GNOME/mutter/issues/263"
1786757,2018-08-14 05:32:33 UTC,and then tell us the ID of the new bug.
1786757,2018-08-14 04:53:16 UTC,See attached glxinfo
1786757,2018-08-14 03:50:46 UTC,apport information
1786757,2018-08-14 04:23:20 UTC,I'm using the built-in screencast by pressing CTRL+ALT+SHIFT+R
1786757,2018-08-14 04:06:20 UTC,Please also run these commands and send us the output:
1786757,2018-08-14 04:04:10 UTC,"When you say ""screencast"" what tool are you using there?"
1786757,2018-08-14 03:58:48 UTC,"Monitor 1 1600 x 900 VGA
Monitor 2 1600 x 900 VGA
Monitor 3 1680 x 1050 DVI"
1786757,2018-08-14 03:50:44 UTC,apport information
1786757,2018-08-14 02:15:51 UTC,1. What is the resolution of your monitors?
1786757,2018-08-14 04:52:42 UTC,See attached xrandr output
1786779,2018-10-01 16:24:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786792,2019-01-30 10:12:43 UTC,"Indeed, reported upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/860"
1786793,2018-08-13 15:00:55 UTC,"If there's any more info I can provide, please let me know."
1786793,2018-08-13 15:10:25 UTC,"StacktraceTop:
 decode_mcu_fast (MCU_data=0x7f2b1401ecd8, cinfo=0x7f2b2561c8d0) at jdhuff.c:715
 decode_mcu (cinfo=0x7f2b2561c8d0, MCU_data=0x7f2b1401ecd8) at jdhuff.c:779
 decompress_onepass (cinfo=0x7f2b2561c8d0, output_buf=0x7f2b1401ee20) at jdcoefct.c:106
 process_data_simple_main (cinfo=0x7f2b2561c8d0, output_buf=0x7f2b2561c758, out_row_ctr=0x7f2b2561c6c4, out_rows_avail=1) at jdmainct.c:298
 jpeg_read_scanlines (cinfo=cinfo@entry=0x7f2b2561c8d0, scanlines=scanlines@entry=0x7f2b2561c758, max_lines=max_lines@entry=1) at jdapistd.c:282"
1786799,2020-06-25 15:54:19 UTC,"After upgrading to 2.8.0 and re-applying this patch to our installation, I found this bug got automatically closed. Are you still intending to solve this in a future version of MAAS?"
1786799,2019-09-19 14:47:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1786799,2018-09-10 16:56:43 UTC,"If spaces aren't being used, it's easy to start using them. So I don't think that's a big concern. I think starting out with a spaces-based selection will get us 80-90% there. The (non-mutually-exclusive) alternatives to using spaces, which could be used for the other 10-20% of use cases, would be:"
1786799,2018-09-10 15:47:56 UTC,"@Mike, that sounds perfect! We are deploying our nodes through Juju with bindings on network spaces to constraint to machines with the right networks attached and to configure the applications with the correct networks. Hence, one preferred DNS space would work for us."
1786799,2018-09-10 16:35:39 UTC,"Using spaces doesn’t solve the issue in environments where spaces ar not
being used. This needs to be solved for configurations that doesn’t depend
on them."
1786799,2018-09-06 00:09:10 UTC,Thanks Niels; I think we have all the information we need to further discuss this issue.
1786799,2018-08-24 08:31:20 UTC,"Given the status is still set to incomplete, can I provide more info to confirm the problem?"
1786799,2018-08-14 14:23:57 UTC,"Hi Andres,"
1786799,2018-08-13 15:59:02 UTC,"Hi Niels,"
1786799,2018-09-07 21:36:42 UTC,"@Neils, I wanted to run an idea by you."
1786822,2020-06-17 11:42:21 UTC,updating mono fixed it for me too :)
1786822,2020-12-08 17:52:16 UTC,I updated mono
1786822,2020-08-05 19:34:29 UTC,I'm on 20.04 and the steps in #4 did not fix the problem for me.
1786822,2020-07-19 11:49:32 UTC,I can confirm steps in #4 fixes a problem in Ubuntu 18.04. Thanks.
1786822,2020-07-14 12:54:02 UTC,This happens in 20.04 too. I'll try #4 and see if it helps.
1786822,2020-06-25 12:25:57 UTC,"for the record, the default mono version that comes with MX 19 is:"
1786822,2020-06-25 12:22:56 UTC,#4 rocks! Thanks Jason.
1786822,2020-05-07 06:45:31 UTC,Also reported here:
1786822,2020-08-05 20:00:58 UTC,"Ok, I ran some other pending upgrades (`sudo apt upgrade`), restarted my computer, and Pinta has stopped crashing."
1786822,2020-04-13 00:39:18 UTC,"Thanks for confirming, this seems to be an issue with the default Mono version in 18.04"
1786822,2020-04-09 21:59:21 UTC,"#4 applied OK.
Running Pinta from terminal shows multiple GTK warning messages:"
1786822,2020-01-29 17:44:51 UTC,The solution in #4 worked for me. Thanks!
1786822,2019-07-26 14:15:34 UTC,The solution in #4 worked for me. Thanks!
1786822,2019-02-20 02:54:32 UTC,The issue seems to be with the Mono libs. See here for instructions to install a PPA with more recent packages: https://www.mono-project.com/download/stable/#download-lin
1786822,2018-12-29 16:56:31 UTC,Same with me Tom.
1786822,2020-05-07 06:44:55 UTC,"Still crashes on 20.04, even with the latest version of Mono."
1786822,2018-11-09 21:34:18 UTC,"I can confirm this too, new install, constantly crashes trying to do any simple tasks with an image. Doesn't seem to matter what the size of an image is."
1786822,2018-09-29 20:21:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786823,2018-08-15 11:47:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786837,2020-06-07 04:17:17 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1786837,2019-03-19 13:40:21 UTC,Is this still an issue?
1786842,2018-09-12 15:56:46 UTC,A link to the purchase order would be useful in the EDI Message list view as well.
1786862,2018-08-13 23:16:15 UTC,"show-credential was designed to be used on the controllers only - on a local system, you can look up credentials.yaml. It says so fairly explicitly in the command help."
1786862,2019-07-05 02:04:50 UTC,PR against develop: https://github.com/juju/juju/pull/10426
1786863,2018-08-13 23:56:58 UTC,"I just had this happen again, and *one* of the window icons on the taskbar can no longer be selected - clicking on it has no effect, while clicking on other window icons does bring them into the foreground. I am not sure if this always happens, just sometimes with a window I haven't tried to bring into the foreground, or if it is intermittent. But in any case, this isn't purely cosmetic after all."
1786863,2018-08-14 13:44:32 UTC,"I've had a variant on this problem occur just now; the taskbar is now permanently corrupt (it looks like some icon has been stuck half-dragged, not that I was trying to drag anything). I've attached two screenshots; corrupt-taskbar-1.png is when I first noticed this, corrupt-taskbar-2.png is after experimentally dragging some icons on the taskbar to see if it resolved things."
1786874,2018-08-28 08:25:21 UTC,Charm-helpers patch - https://github.com/juju/charm-helpers/pull/204
1786874,2018-08-21 10:45:58 UTC,glance charm patch - https://review.openstack.org/#/c/594082
1786874,2018-08-21 08:40:04 UTC,we can add below two lines to ceph.conf to enable this
1786881,2018-08-14 12:10:58 UTC,Patch attached to bug #1786880 fixes this too.
1786881,2018-08-14 12:16:50 UTC,"Or maybe not... The language names are shown using the effective session language, which has been the case for a long time AFAIK. Not sure that using the native language would be an improvement."
1786881,2018-08-14 15:42:09 UTC,@Robert: Probably this is not fixed at all.
1786881,2018-08-15 02:11:31 UTC,This appears to be due to libc using the LANGUAGE environment variable over the value set in setlocale ().
1786881,2018-08-15 04:01:53 UTC,The design [1] is that they should show in the native language. That is what I've seen on other systems too (e.g. Android). It makes sense to me - if I only speak Mandarin then there's no reason why I would recognise the english word for that.
1786881,2018-08-15 04:02:45 UTC,"Fixed with:
https://gitlab.gnome.org/GNOME/gnome-desktop/merge_requests/15"
1786881,2019-04-20 18:00:35 UTC,Unsubscribing the sponsors team because there is nothing to sponsor.
1786881,2019-05-09 02:23:58 UTC,"@Robert: I saw that upstream turned down the proposal to unset LANGUAGE for this purpose. Considering that the issue is kind of Ubuntu specific, do you think that it should be done as an Ubuntu patch for now? Or is any of the methods, which are discussed on the merge request document, within reach?"
1786889,2018-11-15 08:55:44 UTC,"Thanks for the bugreport. We fixed issues here and this should work with the snapd 2.36.x version which is available in the ""candidate"" channel and will be available as a deb soon."
1786889,2018-09-19 23:59:16 UTC,Comment #7 did not fix for me
1786889,2018-08-26 05:32:18 UTC,Comment #7 also fixed this for me on 4.18.1-041801-generic
1786889,2018-08-25 10:27:31 UTC,Comment #7 fixed this for me on 4.18.5-041805-generic #201808241320
1786889,2018-08-24 11:47:55 UTC,I can confirm same issue with 4.18.4-041804-generic.
1786889,2018-08-20 10:44:09 UTC,"comment #7 fixed it for me, on
Linux version 4.18.3-041803-generic (kernel@gloin) (gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1)) #201808180530 SMP Sat Aug 18 09:32:58 UTC 2018"
1786889,2018-08-15 12:02:30 UTC,By the way 4.17.14 works OK for me; only 4.18 doesn't.
1786889,2018-08-17 09:18:44 UTC,When I want to launch the calculator (gnome-calculator in the console) I get the same error message and the calculator does not start.
1786889,2018-08-15 11:56:11 UTC,Same issue with 4.18 from ~kernel-ppa/mainline and LXD 3.3 from snap.
1786889,2018-08-14 21:22:38 UTC,I can confirm same issue with 4.18
1786889,2018-08-14 13:51:57 UTC,Also confirming on 4.18
1786889,2018-08-14 05:26:46 UTC,"If I go back to Ubuntu 18.04 LTS kernel, this error goes away. So I think it is related to Linux kernel 4.17.xx and 4.18 from http://kernel.ubuntu.com/~kernel-ppa/mainline . I tested both kernel and getting same error. I need 4.17 or 4.18 kernel to deal with AMD CPU issue. Thanks!"
1786889,2018-08-17 18:50:08 UTC,"Hi guys, this appears to be a snap bug and is fixed in the beta channel, try the following:
sudo snap refresh core --beta"
1786892,2018-08-14 08:20:38 UTC,Please add version information as well.
1786892,2018-12-11 19:26:12 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1786894,2019-08-05 11:18:27 UTC,"I can confirm that this issue has no longer exist on P-3.13
Thank you Steve."
1786894,2019-08-02 22:10:15 UTC,"Sorry for the delay in addressing this, I've fixed up QRT to expect CONFIG_RETPOLINE for 3.13 kernels on precise, and not fail if earlier kernels have it enabled where we don't expect it. https://git.launchpad.net/qa-regression-testing/commit/?id=e01c4c81828765b3c66870cf4567cd83705b7b0f and https://git.launchpad.net/qa-regression-testing/commit/?id=aa614248beb08d904efb5b3a0f0773525a85c6cb ."
1786894,2018-11-02 11:30:03 UTC,"Put this on hold, asking juergh about the recent change for the spectre/meltdown mitigations"
1786894,2018-11-07 10:32:06 UTC,"I talked to the security team. There is no reason to check for CONFIG_RETPOLINE != 'y' in Precise. CONFIG_RETPOLINE should always be set to 'y', even if the toolchain doesn't support it. There are minimal mitigations that we get even without toolchain support but for that we need CONFIG_RETPOLINE enabled."
1786894,2018-11-20 03:49:54 UTC,"Hi Juerg,
Thanks for the feedback, so I think this should be fixed in the qa-regression-testing test suite now."
1786894,2018-08-14 07:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1786916,2019-02-01 10:56:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786922,2018-08-15 20:41:55 UTC,"After searching on the web, I've found the information that this may have been caused by compiz deactivating plugins. So I suspect that it has deactivated: 'desktop wall' and 'grid'."
1786934,2018-08-15 01:11:14 UTC,I can confirm this in stable/queens neutron.
1786935,2018-08-14 18:24:49 UTC,"This requires a python snap, as upstream only provides source tarball releases."
1786941,2018-08-15 05:20:38 UTC,"After some investigation, bug seems to be related with the displaylink driver. It works as expected (program starts on first try) without installed displaylink driver."
1786943,2018-12-27 02:46:30 UTC,"See this SO post for more details about the SVG spec, and the inkscape implementation.
https://stackoverflow.com/questions/5451135/embed-svg-in-svg"
1786943,2019-09-05 15:42:32 UTC,Here's my post on the same.
1786943,2020-03-27 18:33:06 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1786948,2018-09-25 15:33:08 UTC,https://launchpad.net/ubuntu/+source/gnome-shell-extension-multi-monitors/0.00~git20180920.1.0ca053f-1
1786948,2018-08-30 17:21:28 UTC,https://launchpad.net/ubuntu/+source/gnome-shell-extension-caffeine/0~git20171229-3
1786948,2018-08-30 17:20:58 UTC,https://launchpad.net/ubuntu/+source/gnome-shell-extension-autohidetopbar/20180511-2
1786948,2018-08-30 17:20:16 UTC,https://launchpad.net/ubuntu/+source/gnome-shell-extension-top-icons-plus/21-4
1786948,2018-08-30 17:18:32 UTC,This bug was fixed in the package gnome-shell-extension-workspaces-to-dock - 47-1
1786948,2018-08-30 17:17:30 UTC,https://launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/64-1 has GNOME 3.30 support
1786948,2018-08-30 17:17:13 UTC,This bug was fixed in the package gnome-shell-extension-pixelsaver - 1.10+git20180804-d97c6e4-1
1786948,2018-08-14 15:13:15 UTC,Someone will probably need to file bugs against individual extensions that don't work with GNOME Shell 3.29.90.
1786948,2018-08-15 09:24:47 UTC,"https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=shell-3.30&user=pkg-gnome-maintainers%40lists.alioth.debian.org <- that's Simon's list of bugs filed in Debian, which is probably more or less the same in Ubuntu."
1786948,2018-08-15 01:37:55 UTC,I don't *think* that gnome-shell promises to maintain a stable API (?). I've added some extension-specific tasks here and am closing the gnome-shell task. Please add tasks for any other extensions that were installed from the archive.
1786948,2018-08-14 14:06:27 UTC,Can you get a journalctl log?
1786948,2018-08-14 13:59:14 UTC,apport information
1786948,2018-08-14 13:59:13 UTC,apport information
1786948,2018-08-14 13:59:10 UTC,apport information
1786948,2018-08-21 10:46:53 UTC,"workspace grid is another one, though it's not packaged"
1786948,2018-08-14 14:05:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786959,2018-08-15 11:40:51 UTC,Thanks for highlighting this issue. I've fixed it upstream and will pull in the changes to xubuntu-artwork shorty:  https://github.com/shimmerproject/elementary-xfce/commit/358ce868986dca0186500269cdac276c6a2c644f
1786959,2018-08-15 21:31:58 UTC,"Checked and moka-icon-theme is ok - the ""new"" name is already catered for in the icon-theme."
1786959,2019-10-26 13:36:41 UTC,Fixed in elementary-xfce 0.13
1786963,2018-12-06 11:45:07 UTC,Could you confirm the first run was not run with sudo?
1786963,2018-12-06 17:27:44 UTC,"Hi Sylvain, no, I never run using sudo.  And we configure nodes to use NOPASSWD for sudo so we don't get prompted when running tests that DO use sudo."
1786963,2018-12-06 17:30:20 UTC,"ubuntu@xinyi:~$ certify-advanced
=========================[ Resume Incomplete Session ]==========================
There are 0 incomplete sessions that might be resumed
Preparing...
============[ Bootstrap com.canonical.certification::device (1/3) ]=============
==========[ Bootstrap com.canonical.certification::executable (2/3) ]===========
=============[ Bootstrap com.canonical.certification::fwts (3/3) ]==============
<<<Here is where the suite selection and test selection screens had appeared, and I CTRL-C'd out at Test Selection>>>>
ubuntu@xinyi:~$ certify-advanced
=========================[ Resume Incomplete Session ]==========================
There is 1 incomplete session that might be resumed
Do you want to resume session 'certify-advanced-2018-12-06T17.22.45'?
  r => resume this session
  n => next session
  c => create new session
  d => delete old sessions
[rncd]: r
Previous session run tried to execute job: com.canonical.certification::fwts
What do you want to do with that job?
  s => skip that job
  p => mark it as passed and continue
  f => mark it as failed and continue
  r => run it again
[spfr]: r
Reports will be saved to: /home/ubuntu/.local/share/checkbox-ng
--------------[ Running job 1 / 96. Estimated time left: unknown ]--------------
----------[ Collect information about system memory (/proc/meminfo) ]-----------
ID: com.canonical.certification::meminfo
Category: com.canonical.plainbox::uncategorised
... 8< -------------------------------------------------------------------------
swap: 4294963200
total: 16690040832
------------------------------------------------------------------------- >8 ---
Outcome: job passed
--------------[ Running job 2 / 96. Estimated time left: unknown ]--------------
--------------[ Collect information about the EFI configuration ]---------------
ID: com.canonical.certification::efi
Category: com.canonical.plainbox::uncategorised
... 8< -------------------------------------------------------------------------
path: /sys/class/dmi/id/bios_version
category: EFI
product: EFI v2.40
vendor: American Megatrends"
1786963,2018-12-06 17:31:41 UTC,"Package Versions.  Also, I updated the summary, this was running on 16.04, not 18.04."
1786963,2018-12-06 17:32:55 UTC,"Also, a more accurate recreation would be to do an install on dgx1 including all the dgx1 provider stuff listed in the initial post and re-test this.  I just tried it locally for expediency."
1786964,2018-08-14 23:08:00 UTC,It would appear from the DpkgHistoryLog.txt that possibly you were using a graphical or non-cli environment to install the packages.
1786964,2020-05-25 04:17:23 UTC,[Expired for php7.2 (Ubuntu) because there has been no activity for 60 days.]
1786965,2018-08-14 15:19:40 UTC,machine 24 did finally clear out of the model.
1786968,2018-12-17 16:06:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1786971,2018-08-15 17:23:57 UTC,"This patch fixes it for us. After thinking about it, I don't think it is necessary to check the global config flag I put in my pseudo code?"
1786973,2018-08-21 05:00:34 UTC,"For the time being, can this be alleviated through manually adjusting the `nova-compute` charm `sysctl` configuration option?"
1786977,2019-09-05 21:52:00 UTC,Thank you for your report. I am sorry it has been rotting for some time and gone unnoticed far too long.
1786980,2018-08-17 22:06:28 UTC,Here is the Traceback:
1786981,2018-08-14 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1786981,2018-08-28 17:01:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1786981,2018-09-05 16:36:05 UTC,-- proposed testing --
1786981,2018-09-10 17:53:06 UTC,This bug was fixed in the package linux - 4.15.0-34.37
1786985,2018-08-14 16:52:48 UTC,I uploaded logs form the bootstrap node here: https://private-fileshare.canonical.com/~jacek/lp1786985.tgz
1786985,2018-10-09 11:55:46 UTC,"It looks like the cause - inability to destroy application - maybe related to bug # 1779336.
I think once we figure out why this failed, model destruction will no longer fail. More importantly, we should be able to help you fix you environment."
1786985,2019-05-07 02:55:43 UTC,A lot of rework of destruction and removal operations went into 2.6. Is this a production environment or can you easily try a 2.6-rc2 to see if your issue has been addressed?
1786985,2019-07-06 04:17:31 UTC,[Expired for juju because there has been no activity for 60 days.]
1786989,2018-08-14 20:59:02 UTC,"Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it."
1786989,2019-11-01 08:57:37 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1786989,2020-01-01 04:17:17 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1786992,2018-08-14 17:33:32 UTC,"To clarify, if Ubuntu is booted in EFI mode, os-prober will currently assume that grub will continue to boot in EFI mode and so refuse to add a bios Windows chainloader stanza to the menu since it will not work.  It will only add a windows entry if it finds the windows efi loader in the ESP.  It may be able to come up with sufficient logic to have a bios chainloader entry that is only displayed by grub-pc and hidden in grub-efi, and a corresponding EFI mode that is hidden vice versa."
1787002,2020-11-13 15:45:37 UTC,Looking through old bug tickets ... This sounds like it was rather a bug in your toolchain ... is it still reproducible with a newer version of your Linux distro and the latest version of QEMU?
1787002,2021-01-13 04:17:15 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1787004,2018-08-14 18:30:07 UTC,This change was made by a bot.
1787004,2018-08-14 19:37:14 UTC,"Do you have a way to reproduce this bug, or was it a one time event?"
1787004,2018-08-14 22:21:12 UTC,"So far it's only been a one time event, will update if it happens again."
1787007,2018-08-25 20:38:29 UTC,Σχετικό άρθρο: https://www.phoronix.com/scan.php?page=news_item&px=Global-Switch-Skip-Spectre-Melt
1787007,2019-05-06 15:55:29 UTC,Αναμένεται νέο option για την απενεργοποίηση όλων των mitigations:
1787007,2019-05-25 08:35:21 UTC,"Πλέον υποστηρίζεται μια πιο εύκολη επιλογή, mitigations=off
https://www.phoronix.com/scan.php?page=news_item&px=Spectre-Meltdown-Easy-Switch-52"
1787007,2020-07-14 05:54:20 UTC,"Αυτό μπορεί να γίνει εύκολα με KERNEL_PARAMETERS=""mitigations=off"" στο ltsp.conf.
Ας μην είναι προεπιλεγμένο δεν νομίζω ότι είναι τόσο σημαντικό πια."
1787008,2018-12-06 09:36:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787014,2018-08-15 07:01:13 UTC,"Hi, this issue was fixed in master by https://github.com/openstack/cloudkitty-dashboard/commit/15e65aec62067a0a7f40a5ed3c8804418e0e0ece"
1787014,2018-09-20 21:37:36 UTC,Any workarounds for queens?
1787014,2019-01-14 09:38:43 UTC,https://review.openstack.org/#/c/630604/
1787014,2019-01-14 13:34:43 UTC,@klimber
1787021,2018-08-17 20:00:48 UTC,"Removing ubuntu-security-sponsors from the subscriber list, as there are no more actionable items here. If anyone makes the effort to provide and test a xenial debdiff for this issue, please resubscribe the ubuntu-security-sponsors team. Thanks!"
1787021,2018-08-15 23:24:55 UTC,"Hi,"
1787021,2018-08-14 20:23:29 UTC,"I've attached two versions of this patch, one is based off the Bionic upload, the other backports the minimal NMU that cosmic has.  I personally prefer the latter."
1787021,2018-08-16 18:25:41 UTC,This bug was fixed in the package cgit - 1.1+git2.10.2-3ubuntu0.1
1787024,2018-09-08 09:00:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787037,2018-08-14 22:07:04 UTC,Please add version info and screenshots
1787037,2018-08-15 10:33:35 UTC,"Hello,"
1787037,2018-08-15 11:13:43 UTC,Please add exact version info.
1787037,2018-08-15 11:15:59 UTC,I don't see why it is so hard to use. To me it simple goes south-east 100 mil every time. That does not make it hard to place them.
1787037,2018-08-17 08:28:41 UTC,"@Nick
I see really no arguing on the fact that the mouse pointer can and must reflects the tool selected. The same way you pick and place a GND, a +5v, the same way thousands of software have done with the mouse pointer since windows 2.0"
1787040,2020-06-04 08:50:59 UTC,"Kolla pins versions of direct dependencies in images. If karbor-dashboard did not create a release on the stable/rocky branch including this fix, we will not pick it up."
1787040,2020-06-03 15:02:06 UTC,"This is still present in the kolla/centos-source-horizon:rocky image, 65c00f5af1ca, from 8 weeks ago.  This defect was fixed in the dashboard ~70 weeks ago.  Why is the fix not in the centos/source image?"
1787040,2019-01-14 01:11:48 UTC,"Reviewed:  https://review.openstack.org/591923
Committed: https://git.openstack.org/cgit/openstack/karbor-dashboard/commit/?id=8d2e52f72ee00676119e065d6b4e688983d3689a
Submitter: Zuul
Branch:    master"
1787040,2018-08-15 06:42:10 UTC,"Hi, as I understand this bug, is a bug in karbor-dashboard requirements. They need to add icalendar into their requirements.txt file."
1787040,2019-01-23 22:38:29 UTC,This issue was fixed in the openstack/karbor-dashboard 1.2.0 release.
1787049,2018-08-14 22:59:39 UTC,"StacktraceTop:
 meta_window_unmaximize (window=window@entry=0x55e4e71818a0, directions=directions@entry=META_MAXIMIZE_BOTH) at core/window.c:3250
 update_move (window=window@entry=0x55e4e71818a0, snap=snap@entry=0, x=<optimized out>, y=954) at core/window.c:6056
 meta_window_handle_mouse_grab_op_event (window=window@entry=0x55e4e71818a0, event=event@entry=0x55e4e7e04570) at core/window.c:6420
 meta_display_handle_event (event=0x55e4e7e04570, display=0x55e4e5bfb600) at core/events.c:299
 event_callback (event=0x55e4e7e04570, data=0x55e4e5bfb600) at core/events.c:423"
1787049,2018-08-15 01:44:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787049,2018-08-15 01:44:42 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c"
1787049,2020-11-16 08:20:03 UTC,This is strange. No crashes in focal but a few in groovy(?)
1787051,2018-08-14 23:40:52 UTC,You still have the vim-common package installed which is causing a failure too.
1787067,2018-08-15 04:51:08 UTC,"This appears to be a bug in the Freezer client v1 here:
https://github.com/openstack/python-freezerclient/blob/master/freezerclient/v1/client.py#L33"
1787067,2018-08-15 06:34:55 UTC,"Hi, thanks for reporting this issue, i've already seen this. Any new info is appreciate."
1787067,2019-02-14 12:43:43 UTC,"hi，i've already seen this, i think the beat way is to set OPENSTACK_KEYSTONE_URL=auth_url/version in horizon local_settings,then it will not return ""provide valid keystone auth url"".after this ,will get a 404 ERROR,this ERROR because the file path is wrong, it is a bug of horizon or freezer_web_ui, and then when you get jobs-list will retrun 400 wrong,this is because the elasticsearch lib has remove filterd option. should we need repair this problem in kolla-ansible part ?"
1787070,2020-11-13 15:46:12 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1787070,2018-08-16 13:11:15 UTC,"QEMU version I'm using now is v3.0.0-65-g1d746ee95d-dirty and has the problem, the first version I observed the problem was 2.11 from Ubuntu's repositories."
1787070,2021-01-13 04:17:16 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1787070,2018-08-15 13:44:10 UTC,"I have run the openSUSE guest again, the output of the gdb command can be seen at https://paste.ubuntu.com/p/mCRMvkNWYq/"
1787070,2018-08-16 10:11:31 UTC,"Hmm, nothing obvious in the stack trace.
Also doesn't reproduce here.
What qemu version is this?
If older than 3.0:  Does it still happen for you with qemu 3.0?"
1787070,2018-08-15 06:43:01 UTC,"Can you attach gdb to qemu when the guest hangs, then run ""thread apply all bt""?"
1787073,2019-06-21 10:44:25 UTC,All inner layers are now available for hotkey assignment.
1787073,2019-06-25 11:27:09 UTC,"Fixed in revision f70ab6203b9a3fc44ce994eb4419317971c7d51a
https://git.launchpad.net/kicad/patch/?id=f70ab6203b9a3fc44ce994eb4419317971c7d51a"
1787090,2018-09-10 16:18:30 UTC,Commit 286e87718103acdf85f4ed323a37e4839a8a7c05 is now in the 18.10 kernel version: Ubuntu-4.18.0-8.9
1787090,2018-08-29 02:16:05 UTC,Fixed in v4.19-rc1
1787090,2018-08-15 04:40:27 UTC,"This bug is related CLX platform which is not PVed, keep it private until CLX platform is ready. Thanks for your understanding"
1787090,2018-08-29 02:16:17 UTC,need backporting for 18.10
1787097,2018-08-15 06:29:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/591914"
1787097,2018-08-15 10:37:46 UTC,"Reviewed:  https://review.openstack.org/591914
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=9ae2ca63237f41589492e951258b680c9477b17e
Submitter: Zuul
Branch:    master"
1787098,2018-08-17 13:45:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787098,2018-08-24 14:54:30 UTC,"I removed some broken package, founded from:"
1787098,2018-08-25 19:57:22 UTC,"Cool. Thank you, it worked!"
1787110,2019-09-24 20:37:37 UTC,"Hello Robbert, or anyone else affected,"
1787110,2019-10-03 08:56:53 UTC,This bug was fixed in the package nagios-plugins-rabbitmq - 1:1.2.0-2.2ubuntu0.18.04.1
1787110,2019-10-03 08:05:45 UTC,"The verification of the Stable Release Update for nagios-plugins-rabbitmq has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1787110,2019-10-03 08:05:39 UTC,This bug was fixed in the package nagios-plugins-rabbitmq - 1:1.2.0-2.2ubuntu0.19.04.1
1787110,2019-09-25 07:15:27 UTC,In ensured pre-upgrade the systems were affected and then:
1787110,2019-09-25 07:12:47 UTC,"Upgrading worked as expected:
# apt install nagios-plugins-rabbitmq
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  nagios-plugins-rabbitmq
1 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
Need to get 12.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu disco-proposed/universe amd64 nagios-plugins-rabbitmq all 1:1.2.0-2.2ubuntu0.19.04.1 [12.0 kB]
Fetched 12.0 kB in 0s (257 kB/s)
(Reading database ... 68294 files and directories currently installed.)
Preparing to unpack .../nagios-plugins-rabbitmq_1%3a1.2.0-2.2ubuntu0.19.04.1_all.deb ...
Unpacking nagios-plugins-rabbitmq (1:1.2.0-2.2ubuntu0.19.04.1) over (1:1.2.0-2.2) ...
Setting up nagios-plugins-rabbitmq (1:1.2.0-2.2ubuntu0.19.04.1) ..."
1787110,2019-09-24 20:07:19 UTC,"Hello Robbert, or anyone else affected,"
1787110,2019-10-03 08:58:49 UTC,This bug was fixed in the package nagios-plugins-rabbitmq - 1:1.2.0-2.1ubuntu0.1
1787110,2019-09-24 14:53:10 UTC,"The fix in Eoan works as expected.
Uploaded the same fix (as tested in containers already) to X/B/D for SRU review."
1787110,2019-09-24 13:52:41 UTC,This bug was fixed in the package nagios-plugins-rabbitmq - 1:1.2.0-2.2ubuntu1
1787110,2019-09-24 08:25:54 UTC,"This is a fix that does not touch the current Freeze being active in Eoan, lets prepare a fix for this and verify it."
1787110,2019-09-24 08:24:48 UTC,"In fact on Xenial the default setup as one can check via:
$ rabbitmqctl add_user full_access secret
Creating user ""full_access""
$ rabbitmqctl set_user_tags full_access administrator
Setting tags for user ""full_access"" to [administrator]
# web browse to <IP>:15672 then and we will find 1 socket on the xenial install used, but 0 on the other releases"
1787110,2019-09-24 07:22:42 UTC,Per the test above Bionic/Disco/Eoan are affected.
1787110,2019-09-24 07:20:32 UTC,"Optional checks if something isn't working
Note: some of the commands only exist in newer versions of rabbitmq
# Check that rabbit is up and ""happy""
# rabbitmqctl -n rabbit@$(hostname -s) node_health_check
Timeout: 70 seconds ...
Checking health of node rabbit@e ...
Health check passed"
1787110,2019-09-24 07:20:18 UTC,After some debugging I came up with a simple Testcase for this issue:
1787110,2018-08-15 12:25:04 UTC,"The attachment ""Fixes issue"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1787110,2019-09-24 18:47:02 UTC,"Hello Robbert, or anyone else affected,"
1787110,2019-09-24 06:10:55 UTC,"The actual upstream issue is:
https://github.com/nagios-plugins-rabbitmq/nagios-plugins-rabbitmq/issues/57
With the fix being:
https://github.com/nagios-plugins-rabbitmq/nagios-plugins-rabbitmq/commit/caabebdf4e1d820c19b7d7fa8e682848f22834e9"
1787128,2018-11-14 13:46:49 UTC,This is fixed with https://github.com/snapcore/snapd/pull/6122 and part of 2.36.1 which is in candidate and will be released soon.
1787130,2018-08-15 15:44:18 UTC,You may need to run the following from a terminal:
1787130,2018-08-15 09:00:08 UTC,This change was made by a bot.
1787142,2018-08-15 10:06:40 UTC,"Further Info
If user selects Local Folder, then Choose Folder, the Option ""Other Locations"" does not show File Manager mounted Shares in Kubuntu. In Ubuntu Mate 18.04 is does!
So Ubuntu Mate has a workaround. Kubuntu 17.10 not."
1787150,2019-11-14 02:02:37 UTC,Should be fixed in 19.10 by having Deja Dup depend on duplicity again.
1787160,2018-08-15 12:24:06 UTC,It should be possible to provide `hgrc.d` file for enabling the extension.
1787160,2018-08-15 12:42:46 UTC,Can not enable it even manually.
1787160,2018-08-16 12:55:31 UTC,I could install it by casting my Python-fu over https://packages.ubuntu.com/bionic/all/mercurial-git/filelist and not everybody possess such great skills as me. I wonder how many people could not install the extension because of missing instructions.
1787161,2018-08-23 07:27:12 UTC,ADT doesn't run on -meta only packages.
1787161,2018-08-23 12:41:23 UTC,"xenial/linux-azure-edge is -meta only and the binaries are provided by bug 1787161, which showed no regressions."
1787161,2018-08-28 12:08:57 UTC,Xenial/linux-azure already released to -updates. Setting Stakeholder-signoff to 'Fix Released'.
1787161,2018-08-29 14:32:29 UTC,The package has been published and the bug is being set to Fix Released
1787166,2018-08-23 14:04:42 UTC,The package has been published and the bug is being set to Fix Released
1787166,2018-08-21 10:56:55 UTC,"4.15.0-33.36~16.04.1 - lowlatency
Regression test CMPL, RTB."
1787166,2018-08-22 14:36:22 UTC,"According to the following comment made by Seth, the execveat03 issue is not critical and could be fixed in a upcoming release."
1787166,2018-08-22 10:57:20 UTC,"Throw it back to Incomplete due to execveat03 failure in
ubuntu_ltp_syscalls (bug 1786729)"
1787166,2018-08-23 07:17:59 UTC,ADT doesn't run on -meta only packages.
1787174,2019-09-10 05:37:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787176,2018-08-16 04:14:05 UTC,"Hi Ben Hu,"
1787185,2018-08-15 11:13:25 UTC,Please add exact version info.
1787188,2018-08-17 22:23:54 UTC,"Regression update, needs a USN."
1787188,2018-08-17 22:35:58 UTC,"The ESM upload seems to have a lot of configuration changes that weren't in the master upload, they're also not mentioned in the changelog (the changelog seems to be similar to what was in master). Could someone take a look and see if that's all wanted?"
1787188,2018-08-20 23:03:57 UTC,The package has been published and the bug is being set to Fix Released
1787190,2018-08-16 17:53:01 UTC,"@Seth,"
1787190,2018-08-16 18:04:51 UTC,JP-
1787190,2018-08-16 18:43:51 UTC,"Your thinking  is good.
The attached case shows a track segment that could be removed.
However, do not remove this small useless track segment does not create DRC issues."
1787190,2018-08-16 18:43:58 UTC,v4 add not any problems removing all those small pieces of nothing. Unless I'm completly dumb as suggested.
1787190,2019-06-01 17:05:25 UTC,"Fixed in revision 3fb896353604870b471309d8f573abf8fbdaf6a6
https://git.launchpad.net/kicad/patch/?id=3fb896353604870b471309d8f573abf8fbdaf6a6"
1787190,2018-08-16 19:54:21 UTC,"@cb3rob, have you tried a track starting in the middle of nowhere in 5.0?  I'm pretty sure I fixed that so that it gets no net.  (It's possible my memory is shot and it's in 5.1....)"
1787190,2018-08-16 19:57:31 UTC,I also fixed the path-chaining algorithm in 5.0 to continue chaining through stubs found inside a pad as long as the stubs continue to approach the pad centre.  Whether or not that affects under what conditions we *create* the stubs I can't say.
1787190,2018-08-16 17:37:34 UTC,"i think the 'desired behaviour' would at the very least include all the tiny little stubby dots under pads and sticking out the wrong end of vias to be gone. it does clean up all the large bits, sometimes it takes a few goes, but the tiny leftover of traces hidden under pads and (less often) at vias remain. the cnc mill won't give a crap about it (after all metal is metal and it doesn't care wether it's metal due to it being an ic socket pad or an ic socket pad with a trace under it) but sometimes they're visible as they do stick out a bit, and they affect the way in which the trace drawing chooses it's path."
1787190,2018-08-16 19:24:44 UTC,"@JP, where is the corner case in your design ?"
1787190,2018-08-16 17:32:41 UTC,new traces and vias started in the middle of nowhere appear not to be 'unasssigned' but have their own 'net' so you can't just draw the bus first and then connect things to it. one would think that the desired behaviour for drawing a line or via in the middle of nowhere is for it to have -no- net at first and then join any net that connects to it first. not refuse being connected to anything else.
1787190,2018-08-16 10:14:01 UTC,"Something changed between v4 & v5 simply because I used this cleanup function numerous times, to the point of resolving an annoying segfault."
1787190,2018-08-16 17:26:03 UTC,"the part where it 'forgets' little stubby things partially or wholy hidden under pads, in turn, seems to affect the 'assisted routing' ai in that it seems to try to steer around those remaining trace stubs sometimes, taking sharper corners at ic sockets, causing issues with routing another trace between 2 pins in doing so. also the 'leftover' stubby parts are still considered endpoints by the ratsnest, resulting in 'not very straight' ratsnest lines in some cases. only way to see those little leftovers is to either select the whole area a DIP socket is in and then they show up 'under it' or just move the whole thing and delete them one by one by hand. it's very annoying."
1787190,2018-08-15 22:32:42 UTC,This may be due to the fact that someone decided that keeping the net set for orphaned traces.  I suspect this change is causing the issue here.  The question is do we want this behavior or the old behavior where the net was set to zero and removed when clean up tracks was run.  I personally liked the previous behavior but I'm guessing if we change it there will be unhappy users.  Anyone of the devs have an opinion on this?  Should the priority of this bug report be wishlist or low?
1787190,2018-08-15 22:56:10 UTC,"Personally I don't like keeping the net set for orphaned traces.  I often find myself re-using an existing path through the board for something else, and keeping the net keeps other tracks from connecting to it when I re-jigger things."
1787190,2018-08-15 23:13:35 UTC,Perhaps an option is in order here unless a way can be figured out that solves both problems.
1787190,2018-08-15 23:27:24 UTC,"ah ah, I don't understand any point of view (Wayne, Jeff)."
1787190,2018-08-16 17:28:37 UTC,"it's actually visible that the merging doesn't work well, as the signal names on the traces are not aligned in the same way for overlapping/joined traces as they are for traces that were drawn in one go. if they were indeed merged, they should all look the same and have the net-names on the same place on the screen."
1787190,2018-08-15 11:48:15 UTC,the file producing the bad tracks
1787190,2018-08-16 16:38:20 UTC,@JP- Which tracks are you referring to?  I /think/ the ones in the middle are dangling and should be deleted but maybe I missed what you are seeing?
1787190,2018-08-16 16:45:16 UTC,"Wait, sorry JP, I understand now.  You are right."
1787190,2018-08-16 05:57:47 UTC,"A dangling track is a track with a end point connected to nothing, regardless its net."
1787190,2018-08-16 17:22:30 UTC,"quite often 5.0.0 'forgets' to delete little stubby parts of traces left under pads or just barely sticking out from under the pads, the same applies when a via is placed 'near the end' of a slightly longer trace... cleanup dangling traces simply 'forgets' those."
1787192,2019-11-29 07:51:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/696653"
1787192,2019-12-09 16:19:56 UTC,"Reviewed:  https://review.opendev.org/696653
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=919d760dc03343d1f2c90ff087ee11af105569a0
Submitter: Zuul
Branch:    master"
1787196,2019-03-05 14:11:36 UTC,Hello Jeff
1787196,2019-03-05 13:50:16 UTC,"""This is worsened by having an action selectively apply"" could also apply with a setting/hotkey."
1787196,2018-08-15 17:02:29 UTC,"""this is not a bug, this is a feature"" ;-) Sometimes the proverb verifies."
1787196,2018-08-15 14:40:21 UTC,This is intentional in order to support simple line removal (place a resistor over a wire) but we should probably only remove existing wires for two pin components or make it optional.
1787196,2018-08-20 16:24:44 UTC,"Looking at this more, I think a preference setting/hotkey is the way to go here.  Removing shorted wires is a common action for schematic capture software and of those that provide it, I haven't found any that make a distinction at the pin count.  The argument can be made that we accidentally mess up the schematic by shorting wires as well.  The common denominator is that we mess up our schematic when we are not paying attention/unfamiliar with the software.  This is worsened by having an action selectively apply."
1787201,2018-08-15 13:08:14 UTC,"We now have `qt5` abstraction, that should deal with this deny:
https://gitlab.com/apparmor/apparmor/blob/b1967c892a7b63e8b0f5e1d09d0027a4e04bb6b4/profiles/apparmor.d/abstractions/qt5#L6"
1787201,2018-09-30 10:09:34 UTC,https://gitlab.com/apparmor/apparmor/merge_requests/209
1787201,2018-08-15 13:35:09 UTC,"Vincas Dargis:

> We now have `qt5` abstraction, that should deal with this deny:
> https://gitlab.com/apparmor/apparmor/blob/b1967c892a7b63e8b0f5e1d09d0027a4e04bb6b4/profiles/apparmor.d/abstractions/qt5#L6
"
1787218,2019-08-04 13:32:03 UTC,"I'm having a similar issue on Ubuntu Budgie. The Restore Files text is very large, and the feature doesn't seem to work when trying to click on either a file or on the Restore Files text."
1787219,2018-08-15 14:41:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/592065"
1787219,2018-08-17 09:37:43 UTC,"Reviewed:  https://review.openstack.org/592065
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d64062e34349b1f784037e808d8ae835801bbdcc
Submitter: Zuul
Branch:    stable/queens"
1787219,2018-10-09 19:53:54 UTC,This issue was fixed in the openstack/cinder 12.0.4 release.
1787224,2018-08-16 12:45:42 UTC,"Another test:
3) Adding Windows 10 machine via MaaS
Similar to test 2 above, however the Windows 10 image is based on Windows 10 Pro Version 1709 Build 16299.248. Prior to upgrading to Windows 10 Pro 1803 17134.228, the windows machine was successfully added and it was in ""started"" state within JuJu environment. However, after the upgrade, the machine's state changed to ""down"". Check the following cloudbase-init logs [Prior to upgrade]: archive/1709/cloudbase-init.txt && archive/1709/cloudbase-init-unattend.txt . And the post upgrade cloudbase-init log: archive/1803/cloudbase-init.txt .
After attempting to manually start the ""juju"" service, error 1069 occurs; Check the corresponding screenshot: [archive/Upgrade Win10 1709 to 1803.bmp] .
Cloudbase-Init version is 0.9.12.dev26."
1787224,2018-08-17 14:28:54 UTC,"One observed difference between the ""started"" state in Test-3 (Before upgrading to 1803) and the ""pending"" state in Test-2, is that the ""jujud"" user does have its own home folder created under ""C:\Users"" in Test-3 while such a folder isn't created in Test-2, although both tests create ""jujud"" as a user account and a member of the Administrators group.
Thereafter, the following steps were applied within the machine of Test-2:
a) Deleted the existing ""juju"" service
b) Removed Registry entries created by JuJu's udata.ps1 powershell script
c) Deleted ""C:\Juju""
d) Removed the ""jujud"" user
e) Rebooted the machine
f) Edited the user data script created by JuJu (under ""C:\Users\cloudbase-init\AppData\Local\Temp\juju\udata.ps1"") and added the following code segment:"
1787224,2019-09-20 10:10:27 UTC,"I believe most of the charms that we've had were not targeting Windows 10, so probably the infrastructure there has not been polished as much. (Windows Server 2012, IIRC was the most tested windows platform.)"
1787224,2019-09-23 14:27:16 UTC,Thanks for the reply. Looking forward for further progress on this.
1787224,2019-11-23 04:17:22 UTC,[Expired for juju because there has been no activity for 60 days.]
1787225,2020-07-01 19:37:48 UTC,Closing as expired.
1787225,2019-07-17 19:40:56 UTC,Thanks for filing this bug in Ubuntu.
1787225,2019-07-17 19:41:46 UTC,"You can also check ""sudo systemctl cat apache2.service"", that will show if any overrides are in place."
1787225,2019-07-15 11:03:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787231,2018-08-15 15:52:38 UTC,"Hi Cheryl,"
1787233,2019-11-27 12:30:27 UTC,https://salsa.debian.org/phpmyadmin-team/phpmyadmin/issues/31
1787234,2018-08-15 15:58:03 UTC,"Also, with closed shapes, division should be used instead."
1787234,2020-03-20 15:58:50 UTC,Closing because INVALID.
1787240,2018-08-15 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787240,2018-08-28 17:01:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1787240,2018-09-05 22:48:41 UTC,-- proposed verification --
1787240,2018-09-10 17:53:06 UTC,This bug was fixed in the package linux - 4.15.0-34.37
1787241,2020-03-17 08:01:19 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787241,2020-05-17 04:17:27 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1787242,2019-05-22 13:31:52 UTC,I have now marked this as 'fix-released' as Ubuntu Mate 19.04 contains the upgraded files and I can confirm that this works for me.
1787242,2018-12-18 17:22:44 UTC,"@drstevebrule  & others,"
1787242,2018-11-20 11:20:48 UTC,I confirm this bug.
1787242,2018-10-24 10:58:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787242,2018-10-28 05:42:12 UTC,"Same problem after ""safely remove drive"""
1787242,2018-10-21 17:06:14 UTC,Paste from [ https://github.com/mate-desktop/caja/issues/1046#issuecomment-431685452 ]
1787242,2018-09-25 17:22:33 UTC,"Just a note, I get the same results on two different laptops; ASUS G1Sn with single Nvidia GPU and a Dell Precision M4600 with Intel/Nvidia. It many be possible that new users coming from Windows to MATE Mint & MATE Ubuntu might be thing this is normal behaviour for a Linux distro when they see the file manager drop out or they might find it confusing to figure out why and how to report such an issue. I find it hard to believe we are the only individuals with this issue give that I've manage to repeat the problem so easily on these two computers with Mint, Ubuntu and Manjaro but not on Fedoria or Debian. You could be right about gvfs but most of my testing was with live boots without updating anything.
                      Extra Panel	    Extra Panel	    Kernel	Kernel & Caja
                 Caja        blank info	    loc.bar focus   Version	“sigfault at 4”
Linux Mint 18.3 Mate	1.18.5	    n	            n	            4.10.0-38	n
Linux Mint 19.2 Mate	1.20.2	    y	            y	            4.15.0-20	n
Linux Mint 19.2 Mate	1.20.2	    y	            y	            4.15.0-33	y
Ubuntu 18.04 Mate	1.20.2	    n	            y	            4.15.0-29	y
Manjaro 17.1.12 Mate	1.20.2	    y	            n	            4.14.65-1	y
Debian 9.5 Mate	        1.16.6	    n	            n	            4.9.0-7	n
Fedora-MATE...28-1.1	1.20.2	    n	            n	            4.16.3-301	n"
1787242,2018-09-27 21:17:38 UTC,Woo! Not at my desktop but good work. Thanks.
1787242,2018-09-27 17:59:49 UTC,@drstevebrule much thanks for looking at this. Agree with your comments about new users.
1787242,2018-09-25 03:57:28 UTC,I am away from my desktop at present but recall that I found the original 18.04 live didn't have the problems.
1787242,2018-09-24 23:34:06 UTC,"I have spent many days looking at this problem on and off with several distros. At first I thought it was an upstream problem with MATE's caja but after seeing for myself that Fedora's live does not have this issue (newer kernel and the same caja 1.20.2), I'm more inclined to think this is a downstream issue affecting Ubuntu, Linux Mint and Manjaro. You can view my comments on the upstream report."
1787242,2018-08-17 11:34:17 UTC,"Of note, I can't duplicate this issue by using the 18.04 live ISO."
1787242,2018-08-16 10:09:03 UTC,I have done a bit more research:
1787242,2018-10-17 07:23:56 UTC,":(  Just did the upgrade with libmount1, mount, libblkid1, uuid-runtime, fdisk and others.  Even after a machine restart, the problem is still present."
1787247,2020-03-19 21:48:09 UTC,Closing because INVALID.
1787254,2018-09-05 16:02:40 UTC,"I can confirm that in core18 we also don't have fwupdate. The system-image seed is used during ubuntu-base builds that are used as the base of core18, but fwupdate is not part of it - and it is not installed separately either."
1787254,2019-10-16 06:12:20 UTC,I'm closing the snapd task because it looks like we don't need fwupdate for uc20. If it turns out I was wrong this needs to be reopened.
1787254,2019-04-17 20:45:30 UTC,"I have swapped fwupdate for fwupd in the system-image seeds so that fwupdate can be demoted to universe for disco.  Since it does not appear that either fwupd or fwupdate are actually used as part of the core18 build today, we should at least be referring to the *right* unused implementation."
1787254,2018-08-16 08:45:27 UTC,"I don't know much about this, but I'm asking different people and I'll answer here as I find out."
1787254,2018-08-15 21:01:21 UTC,Thanks Steve.  I've made the matching change in packaging so any future fwupdate uploads to Debian that sync won't try to make signed packages again.
1787254,2018-08-15 22:32:39 UTC,"Removing packages from cosmic:
 fwupdate-signed 1.18 in cosmic
  fwupdate-amd64-signed 1.18+10-3 in cosmic amd64
  fwupdate-arm64-signed 1.18+10-3 in cosmic arm64
  fwupdate-armhf-signed 1.18+10-3 in cosmic armhf
  fwupdate-i386-signed 1.18+10-3 in cosmic i386
  fwupdate-signed 1.18+10-3 in cosmic amd64
  fwupdate-signed 1.18+10-3 in cosmic arm64
  fwupdate-signed 1.18+10-3 in cosmic armhf
  fwupdate-signed 1.18+10-3 in cosmic i386
Comment: Superseded by fwupdx64.efi from fwupd source; LP: #1787254
1 package successfully removed.
Removing packages from cosmic-proposed:
 fwupdate-signed 1.20 in cosmic
  fwupdate-armhf-signed 1.20+12-3 in cosmic armhf
  fwupdate-signed 1.20+12-3 in cosmic armhf
Comment: Superseded by fwupdx64.efi from fwupd source; LP: #1787254
1 package successfully removed."
1787254,2018-08-15 17:50:34 UTC,Here is the IRC transcript that prompted this bug:
1787254,2018-08-15 20:48:24 UTC,"Based on the analysis in the previous comment, I'm going to go ahead and delete fwupdate-signed now from cosmic (and blacklist it).  If at a later date it is determined that Ubuntu Core does need fwupdate in Ubuntu 20.04 we can reintroduce it, but in the meantime we shouldn't carry on producing and signing EFI executables in the archive that we don't expect to be used."
1787254,2018-08-15 20:16:36 UTC,"As an archive admin I've said that we should not be signing two parallel streams of EFI binaries implementing this functionality. If fwupd is considered the preferred implementation upstream and Ubuntu is going to adopt this, then we should remove fwupdate-signed entirely from the archive and stop producing artifacts from fwupdate source package for EFI signing."
1787254,2018-08-16 03:44:21 UTC,"As also found by this, the signing source packages from debian need to be blocked too.  That's filed here: https://bugs.launchpad.net/ubuntu/+source/fwupdate-amd64-signed/+bug/1787315"
1787256,2018-08-24 18:32:28 UTC,Hi Joseph
1787256,2018-08-28 01:15:53 UTC,"I built a test kernel with commit 6927868e7ae929f037eea973c582b870808880b6.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1787256"
1787256,2019-08-29 18:02:01 UTC,Sorry I mistakenly changed from confirmed to Fix Released. Can someone please modify this? I'm wondering whether this fix was releases in any Linux kernel versions.
1787260,2018-09-15 04:54:38 UTC,"# cat /proc/version
Linux version 4.15.0-34-generic (buildd@lgw01-amd64-047) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018"
1787260,2018-09-15 04:51:22 UTC,"This may have been a BIOS bug, does not occur after BIOS upgrade (BIOS P4.70 04/17/2018 -> BIOS L4.81 08/16/2018):"
1787260,2018-08-17 19:01:32 UTC,"Could ""[PATCH V2 2/2] efi/fb: Convert PCI bus address to resource if translated by the bridge"" https://lkml.org/lkml/2018/5/18/729 be related?"
1787260,2018-08-17 18:14:22 UTC,"Please ignore the MWAIT comment, this is present ever since I set BIOS option
  Advanced > AMD CBS > Zen Common Options > Power Supply Idle Control
to the necessary (for system stability on any Ryzen CPU) non-standard value of 'Typical current' (#1690085)."
1787260,2018-08-17 18:04:42 UTC,Still present on 4.18:
1787260,2018-08-17 17:50:10 UTC,This issue started happening on 16.04.5 with HWE kernel:
1787260,2018-08-16 17:04:27 UTC,I have tried to reproduce the same behavior that you got but with no luck.
1787260,2018-08-16 15:45:00 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1787260,2018-08-15 18:30:11 UTC,This change was made by a bot.
1787272,2020-05-21 14:19:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1787272,2020-07-21 04:17:18 UTC,[Expired for accountsservice (Ubuntu) because there has been no activity for 60 days.]
1787289,2020-12-31 08:29:12 UTC,"It happens in ubuntu 20.04 with hplip 3.20.11 with a printer laserjet m1132 mfp. I have updated the patch above as it was failing, but it is the same thing: Removed references to imageprocessor. In order to use it:
hplip-3.20.11.run --noexec
cd hplip-3.20.11
patch -p1 < «path to patch»/evitar_usar_imageprocessor.patch
./hplip-install?field.comment=It happens in ubuntu 20.04 with hplip 3.20.11 I have updated the patch above as it was failing, but it is the same thing: Removed references to imageprocessor. In order to use it:
hplip-3.20.11.run --noexec
cd hplip-3.20.11
patch -p1 < «path to patch»/evitar_usar_imageprocessor.patch
./hplip-install"
1787289,2019-12-19 21:37:56 UTC,I have a similar error on Ubuntu 19.10 with HPLIP 3.19.12 as well while attempting to an HP Laserjet P1102w.
1787289,2019-12-09 10:09:00 UTC,"I have the same problem on Ubuntu 19.10, with HPLIP 3.19.11 using HP-Laserjet-CP-1025 pritner."
1787289,2018-10-30 01:58:26 UTC,"Arch may be unsupported, but I have the identical problem on Ubuntu 18.04.1 with hplip 3.17.10 from the repos, or the download tar.gz that installs 3.18.10.  So the problem appears to be generic regardless of the distro."
1787289,2018-08-16 04:31:16 UTC,"Hi Colin,"
1787289,2018-08-16 19:59:06 UTC,Downgrading hp-plugin only works if I also downgrade hplip. The whole point is that the current version of hplip uses the new libImageProcessor and it doesn't work with the matching version of hplip-plugin on Arch Linux.
1787289,2018-08-16 19:46:24 UTC,"Just now I ran hp-doctor because I figured having the old version of the plugin would be detected as an error, and it was. I let hp-doctor download and install the matching plugin version, which got me back to where I started. It still won't print. I will now re-install the patched version of hplip with use of libImageProcessor removed."
1787289,2018-08-16 19:42:37 UTC,"I have tried the older version of the plugin, but I still get the same error. Only by reverting the new libImageProcessor by applying the attached patch when building can I print using this latest version of hplip."
1787289,2018-08-16 19:17:54 UTC,Your problem appears to arise from the non-free plugin. Try installing the *files* from its previous version (the one which worked for you).
1787289,2018-08-16 04:55:45 UTC,"I am using Arch Linux, which is not a supported distribution. I install it using their pacman package manager. The forum and bug report I linked show that it's many Arch Linux users running into this issue. The user that came up with the patch is not experiencing this issue which is why he didn't submit the bug report himself. The patch fixes the issue for me and some others using Arch Linux. We were hoping you would use the patch to fix the issue."
1787289,2018-08-16 21:31:13 UTC,"> With the updated package imageProcessor is now being used but is failing.
> Unfortunately ImageProcessor is a binary blob and the hplip.plugin is another
> binary blob.
> Some interaction between these two black boxes results in the issue. Raise
"
1787294,2018-08-17 22:41:42 UTC,Upstream moved the bug to gtk-pixbuf as they knew of some problems with ico's in gdk-pixbuf
1787294,2018-08-17 22:08:04 UTC,Here is the Upstream Bug report
1787294,2018-08-16 01:38:17 UTC,I'm not sure what the right component to assign this bug is. To progress this issue please open a bug with the GTK developers here:
1787294,2018-08-15 22:55:42 UTC,Here is a PNG of the icon so you can see what it looks like if you are also on 18.04 with this bug.
1787294,2018-08-15 22:36:57 UTC,And interestingly enough. Nautilus also displays the preview of the file as noise.
1787294,2018-08-15 22:35:22 UTC,And here is the actual .ico file
1787294,2018-08-15 22:34:11 UTC,Here is a screenshot of the icon in gnome-hell
1787294,2018-08-16 01:35:02 UTC,"If nautilus also shows noise then this is a lower level bug, not in gnome-shell. Reassigning to GTK to start with..."
1787297,2018-08-16 09:28:15 UTC,For me it works though.
1787297,2018-08-16 09:40:18 UTC,"Ah I forgot, For your own custom time format, you need to first set `time-format` from 'locale-default' to 'custom'."
1787297,2018-08-16 11:10:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787297,2018-08-16 11:19:25 UTC,hello !
1787297,2018-08-16 11:37:46 UTC,"Ah, i am not under Unity:"
1787297,2018-08-16 21:23:16 UTC,"coeurnoir-1804@ASGARD:~$ locale
LANG=fr_FR.UTF-8
LANGUAGE=fr_FR:fr_CA:en
LC_CTYPE=""fr_FR.UTF-8""
LC_NUMERIC=fr_FR.UTF-8
LC_TIME=fr_FR.UTF-8
LC_COLLATE=""fr_FR.UTF-8""
LC_MONETARY=fr_FR.UTF-8
LC_MESSAGES=""fr_FR.UTF-8""
LC_PAPER=fr_FR.UTF-8
LC_NAME=fr_FR.UTF-8
LC_ADDRESS=fr_FR.UTF-8
LC_TELEPHONE=fr_FR.UTF-8
LC_MEASUREMENT=fr_FR.UTF-8
LC_IDENTIFICATION=fr_FR.UTF-8
LC_ALL=
coeurnoir-1804@ASGARD:~$"
1787297,2018-08-16 22:03:39 UTC,Thank you Khurshid Alam that's exactly what I was looking for !
1787297,2018-08-16 22:06:31 UTC,@kikito you're not under Unity neither under Bionic 18.04 ;-)
1787297,2018-08-17 13:09:35 UTC,@Coeur Noir: I know.
1787297,2018-08-21 08:52:26 UTC,Since it is happening in other sessions it could be bug in language-pack or some other package.
1787297,2019-12-01 15:13:57 UTC,Just a reminder.
1787297,2019-12-12 18:48:56 UTC,"The format you are complaining about is American NOT English. I have noticed the same problem, running Gnome Flashback under Ubuntu 18.04, today. System settings show the correct English regional format (eg Thu 12 Dec 2019 18:29:30) but, in the indicator, I get Thu Dec 12 2019 18:29:30. Extremely annoying."
1787298,2020-05-26 09:22:55 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/600269
Reason: This patch is old with negative review comments. I'm abandoning it but feel free to restore it or ping me (gibi) on IRC to restore it for you if you want to continue working on it."
1787298,2018-09-05 22:31:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/600269"
1787302,2018-08-16 01:19:42 UTC,Please un-nominate bionic. That's a mistake.
1787302,2019-01-15 17:20:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787302,2018-08-16 01:18:36 UTC,Fix Released. There were zero reports of this crash after Ubuntu 17.04.
1787304,2018-08-16 19:44:13 UTC,apport information
1787304,2018-08-16 19:44:11 UTC,apport information
1787304,2018-08-16 19:44:09 UTC,apport information
1787304,2018-08-16 19:44:07 UTC,apport information
1787304,2018-08-16 19:44:05 UTC,apport information
1787304,2018-08-16 19:44:04 UTC,apport information
1787304,2018-08-16 19:44:02 UTC,apport information
1787304,2018-08-16 19:43:58 UTC,apport information
1787304,2018-08-16 19:43:59 UTC,apport information
1787304,2018-08-16 01:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787304,2018-08-16 16:02:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1787304,2018-08-16 19:28:28 UTC,"Thanks @Joseph, this issue started happening after an upgrade 16.04 -> 18.04 via CLI.  Prior to upgrade I was on the latest 16.04 kernel as I had applied automatic updates constantly and restarted recently.  Sorry, as I don't recall the kernel version."
1787304,2018-08-16 19:44:01 UTC,apport information
1787304,2018-08-16 19:43:53 UTC,apport information
1787304,2018-08-16 19:43:55 UTC,apport information
1787304,2018-08-16 19:43:56 UTC,apport information
1787304,2018-08-16 19:43:52 UTC,apport information
1787307,2020-04-28 05:26:46 UTC,This bug was fixed in the package opendkim - 2.11.0~beta2-2
1787309,2018-09-08 23:50:52 UTC,"The 7.5 and 4.15 kernel was causing a crash under load when only zfs io was happening and then
did something to cause ext4 root file system i/o. The system locked up so hard that the console
keyboard cap lock did not even work."
1787309,2020-09-02 14:13:16 UTC,"I double checked this out with Xenial and it's working fine, so I will close this issue as it was confirmed in comment #2 the the email was not sent because a lockup and not zed not working correctly."
1787328,2018-08-16 06:30:07 UTC,This change was made by a bot.
1787328,2018-08-16 06:06:55 UTC,"I can only umount with force+lazy, but not remount.
The remount hangs (no crash) in D+ state:"
1787328,2018-08-16 06:04:42 UTC,apport information
1787328,2018-08-16 06:04:41 UTC,apport information
1787328,2018-08-16 06:04:40 UTC,apport information
1787328,2018-08-16 06:04:39 UTC,apport information
1787328,2018-08-16 06:04:38 UTC,apport information
1787328,2018-08-16 06:04:36 UTC,apport information
1787328,2018-08-16 06:04:35 UTC,apport information
1787328,2018-08-16 06:04:33 UTC,apport information
1787328,2018-08-16 06:04:32 UTC,apport information
1787328,2018-08-16 06:04:31 UTC,apport information
1787328,2018-08-16 06:04:30 UTC,apport information
1787328,2018-08-16 06:04:29 UTC,apport information
1787328,2018-08-16 06:04:37 UTC,apport information
1787328,2018-08-16 06:04:34 UTC,apport information
1787329,2018-09-25 18:51:17 UTC,You still need to fix your coding policy violations of which there are too many to list.  The easiest solution would be to use uncrustify or clang-format with the formatting config files provided in the kicad source root folder to fix the file build_BOM_from_board_properties.h.  build_BOM_from_board_properties.cpp should be fixed by hand to prevent unnecessarily large change set.
1787329,2018-10-31 17:27:56 UTC,"Hi Martin,"
1787329,2018-10-25 08:23:07 UTC,Hi Wayne
1787329,2018-09-25 12:01:38 UTC,"@ Wayne, you are right there was a bug in List 2 (as I only use list 1 for my purposes)"
1787329,2018-09-20 07:39:02 UTC,I changed the GPL2 to GPL3
1787329,2018-09-20 07:18:38 UTC,@Wayne
1787329,2018-08-31 13:19:43 UTC,"@Martin, some comments on your patch."
1787329,2018-08-31 08:10:11 UTC,Ich changed the patch so now It contains only the patch without my git history.
1787329,2018-09-24 17:33:40 UTC,"@Martin, I tested your patch but AFAICT it does not sort items alphabetically by reference.  It does some sorting but not what I expected.  What is the end goal with this patch?  There are still have a lot coding policy violations in your patch that need to resolved before it can be merged."
1787332,2018-08-16 06:40:20 UTC,"StacktraceTop:
 OsAbort () at ../../../../os/utils.c:1361
 AbortServer () at ../../../../os/log.c:877
 FatalError (f=f@entry=0x55ea826ed5d1 ""EnterVT failed for screen %d\n"") at ../../../../os/log.c:1015
 xf86VTEnter () at ../../../../../../hw/xfree86/common/xf86Events.c:524
 systemd_logind_vtenter () at ../../../../../../../hw/xfree86/os-support/linux/systemd-logind.c:255"
1787332,2018-08-16 06:50:33 UTC,"Looks similar to bug 1421808, but now slightly different."
1787332,2018-08-29 09:56:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787332,2018-11-29 17:30:09 UTC,I've been informed that this is a duplicate of 1805873 and that further communication about this bug should happen in this thread. I am able to reproduce this bug with a specific series of steps. Here's what I know:
1787332,2018-11-29 22:34:24 UTC,Please let me know what I can do to help with testing/debugging/fixing/etc. I have a reliable way to reproduce the condition and am willing to participate in the process.
1787332,2018-11-30 02:14:27 UTC,"This bug appears to be a little related to bug 1787337, but I can't find the official error tracker page for this one yet."
1787332,2019-04-25 21:17:03 UTC,This bug seems to have stopped for me a couple of months back. Now I get black screens that have to be toggled off and back on with xrandr before they display again after undocking/redocking.
1787332,2020-05-22 04:20:45 UTC,Maybe fixed in bug 1879893?
1787337,2018-09-17 14:04:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787337,2018-11-30 02:13:52 UTC,This looks closely related to bug 1787332.
1787337,2020-05-22 04:21:03 UTC,Maybe fixed in bug 1879893?
1787338,2020-05-22 04:21:16 UTC,Maybe fixed in bug 1879893?
1787338,2019-05-15 06:55:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787345,2019-12-18 14:38:57 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/592304"
1787347,2018-08-16 09:52:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787354,2018-08-16 08:55:04 UTC,Patch for evdev.xml
1787354,2018-08-16 12:25:09 UTC,"The attachment ""Patch for german keyboard layout file"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1787364,2018-08-20 01:49:03 UTC,"This time I got my blender window back but nother else. Gnome is dead, no windows, nothing. I used :
DISPLAY=:1.0 compiz --replace &
to restart compiz but it looks like it was not the true culprit here :-("
1787364,2018-08-20 02:03:48 UTC,"If I close Blender, I have the desktop. Nautilus is ok. I can right-click and open a terminal too. The terminal and Nautilus windows have headers, I can move them."
1787364,2020-03-15 15:02:40 UTC,I've this problem aleatory in my XPS L502x
1787364,2020-03-15 15:02:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787368,2018-08-16 22:29:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787368,2019-04-07 16:16:26 UTC,"Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected."
1787368,2019-04-12 16:20:30 UTC,It should be reported to GNOME/GTK upstream on gitlab
1787371,2019-01-03 04:05:41 UTC,"Reviewed:  https://review.opencontrail.org/48378
Committed: http://github.com/Juniper/contrail-controller/commit/d9cb298b7531dcb4723bfd8f062067811bfd2d0e
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1787371,2019-01-03 20:13:04 UTC,"Reviewed:  https://review.opencontrail.org/48379
Committed: http://github.com/Juniper/contrail-controller/commit/5fd37ce9c5876b15330a625cd7ab869c8da8efe2
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    R5.0"
1787371,2019-01-03 01:54:54 UTC,"Reviewed:  https://review.opencontrail.org/48380
Committed: http://github.com/Juniper/contrail-controller/commit/f19873501967a293d2a8719771fcd5153a17002c
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1787371,2019-02-20 07:23:15 UTC,"Reviewed:  https://review.opencontrail.org/49393
Committed: http://github.com/Juniper/contrail-controller/commit/77df3b58265b3fab414dfbc00e1ff39d19f0a99c
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    R6.0-WIP"
1787371,2018-12-27 10:12:05 UTC,"Review in progress for https://review.opencontrail.org/48379
Submitter: Édouard Thuleau (<email address hidden>)"
1787371,2018-12-27 10:11:48 UTC,"Review in progress for https://review.opencontrail.org/48378
Submitter: Édouard Thuleau (<email address hidden>)"
1787371,2018-12-19 23:26:51 UTC,"Reviewed:  https://review.opencontrail.org/45596
Committed: http://github.com/Juniper/contrail-controller/commit/182f70500ca104b50b26bc27906939eba49e0109
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1787371,2018-12-27 10:12:16 UTC,"Review in progress for https://review.opencontrail.org/48380
Submitter: Édouard Thuleau (<email address hidden>)"
1787371,2018-08-16 10:18:38 UTC,"Review in progress for https://review.opencontrail.org/45596
Submitter: Bruno Fernando (<email address hidden>)"
1787372,2018-08-20 17:09:27 UTC,Those issues are new as I have been running Diodon 18.04 without any problems.
1787372,2018-08-20 18:19:06 UTC,As far as I remember I installed from the repository. When I run apt install diodon I get the message diodon is already the newest version (1.8.0-1).
1787372,2018-08-20 19:48:22 UTC,How many items do you allow in your history? Seems to be fairly long ;).
1787372,2018-08-21 11:27:32 UTC,I configured diodon for 100 items in the history.
1787372,2018-08-21 21:13:05 UTC,Seems that the application indicator support doesn't support scrolling so the number of history items would need to be lower than the screen size as a workaround.
1787372,2020-04-05 18:05:48 UTC,You can try executing diodon from Terminal or gnome Alt + F2.
1787374,2019-03-15 12:42:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787385,2018-08-17 09:46:08 UTC,"Hello Tobias, thank you for your update, I will raise that within team. Cheers, Paweł"
1787396,2018-08-16 14:19:58 UTC,"I've replicated the problem and the way I see it, all you need is --no-header and a filter with no matches. Filters with matches (found connections) won't cause a segfault."
1787396,2018-08-16 14:20:55 UTC,This also happens on Cosmic that has the same version of ss/iproute2:
1787396,2018-08-16 21:55:25 UTC,This is fixed in Debian since 4.16.0-4 at least.
1787396,2018-11-30 10:13:14 UTC,I confirm this on Ubuntu 18.04 (bionic) with 4.15.0-2ubuntu1. It is fixed in 18.10 (cosmic) with  4.18.0-1ubuntu2.
1787396,2018-08-16 14:16:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787402,2019-09-17 20:25:25 UTC,bump.  me too.
1787402,2018-08-16 16:21:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1787402,2014-11-18 15:43:16 UTC,Perhaps something similar to 8f89ae4bb60fe6b15e0a8eb5b31135fbdd6ca182 in xfdesktop is needed here - Eric?
1787402,2014-11-18 16:44:31 UTC,"Oh yeah, makes sense. I don't have time to write a patch today."
1787402,2012-06-11 16:33:14 UTC,I've symlinked a .desktop file into ~/.config/autostart.
1787402,2014-11-18 17:09:57 UTC,"xfce_spawn_command_line_on_screen() is used there, and it doesn't allow a working directory passed to that function. There are some others in libxfce4ui/libxfce4ui/xfce-spawn.c that look plausible to use here, but I'm going to defer this one to someone more experienced. Thanks, Eric! :-)"
1787404,2018-08-16 23:08:39 UTC,"And actually, the workaround I mentioned wouldn't work anyway, since doing a block paste like that resets all of the reference designators.  I haven't actually been able to think of any other workarounds, other than editing the .sch file directly in a text editor."
1787409,2018-08-16 13:40:38 UTC,"This was my simple test config:
squidguard.conf:
#
# CONFIG FILE FOR SQUIDGUARD
#
# Caution: do NOT use comments inside { }
#"
1787409,2018-09-11 03:55:46 UTC,Do these settings really need to be in the squid Apparmour profile?
1787409,2018-09-11 12:32:11 UTC,I was wondering that too. I left that investigation for when I would tackle this bug.
1787411,2018-08-16 17:43:40 UTC,apport information
1787411,2018-08-16 17:49:09 UTC,"Yes, i had to fiddle around quite a lot with the package manager to get everything going again and it all works now (the apport information above is from after the upgrade)."
1787411,2018-08-16 17:43:47 UTC,apport information
1787411,2018-08-16 17:43:46 UTC,apport information
1787411,2018-08-16 17:43:43 UTC,apport information
1787411,2018-08-16 17:43:42 UTC,apport information
1787411,2018-08-16 17:43:41 UTC,apport information
1787411,2018-08-16 17:43:39 UTC,apport information
1787411,2018-08-16 17:43:35 UTC,apport information
1787411,2018-08-16 17:43:38 UTC,apport information
1787411,2018-08-16 14:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787411,2018-08-16 15:51:35 UTC,You may need to run the following from a terminal:
1787411,2018-08-16 17:43:32 UTC,apport information
1787411,2018-08-16 17:43:39 UTC,apport information
1787411,2018-08-16 17:43:34 UTC,apport information
1787411,2018-08-16 17:43:36 UTC,apport information
1787411,2018-08-16 17:43:37 UTC,apport information
1787411,2018-08-16 17:43:33 UTC,apport information
1787415,2018-08-16 14:20:40 UTC,Second promised attachment!
1787415,2019-08-07 17:24:54 UTC,Marking Confirmed.
1787415,2019-08-09 19:54:39 UTC,Just adding a pdf with some screen shots from before and after the patch.
1787415,2020-02-18 16:27:51 UTC,"I have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>."
1787415,2020-02-21 16:02:16 UTC,"Pushed to master, 3.3 and 3.4.  Thanks Michele and Dawn!"
1787415,2019-08-08 18:17:22 UTC,Fix available at:
1787417,2019-09-19 11:51:23 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1787418,2018-08-16 14:54:03 UTC,"this is the journalctl-a  (with all lines before last ""-- Reboot --"" removed (so as to shrink file)"
1787418,2019-08-20 01:52:43 UTC,"Thank you for reporting this bug. Since this was reported against a version of gimp included in a now end-of-life version of Ubuntu, please try to reproduce this bug using a more recent version of Ubuntu, and comment on this bug as to whether or not this bug still occurs."
1787418,2019-10-19 04:17:45 UTC,[Expired for gimp (Ubuntu) because there has been no activity for 60 days.]
1787418,2019-10-19 06:23:34 UTC,I missed Erich's 18.10 is EOL; please re-test - so this is belated sorry.
1787420,2018-09-06 18:39:32 UTC,"Hey Pawel,"
1787420,2018-08-17 09:58:57 UTC,"Hello Boden,"
1787420,2018-09-04 11:46:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599572"
1787423,2018-08-16 15:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787423,2018-08-27 13:55:48 UTC,Maybe keep this in mind: Before I upgraded to the Kernel 4.18.5 I have created a snapshot. So maybe if someone wants me to do some further testing I am able to revert the changes and do so.
1787423,2018-08-27 13:49:46 UTC,"I really was not expecting that this will work but today I was able to successfully update the Kernel to 4.18.5. And furthermore for the first time this machine exist, I was able to reboot and shutdown the system without killing my hypervisor and rebooting the host."
1787423,2018-08-16 15:19:16 UTC,apport information
1787423,2018-08-16 15:19:15 UTC,apport information
1787423,2018-08-16 15:50:45 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1787423,2018-08-16 15:19:13 UTC,apport information
1787423,2018-08-16 15:19:12 UTC,apport information
1787423,2018-08-16 15:19:11 UTC,apport information
1787423,2018-08-16 15:19:10 UTC,apport information
1787423,2018-08-16 15:19:09 UTC,apport information
1787423,2018-08-16 15:19:08 UTC,apport information
1787423,2018-08-16 15:19:14 UTC,apport information
1787424,2020-01-30 16:17:14 UTC,"Kyle,"
1787426,2018-09-21 11:43:09 UTC,The socat approach needs to stay I guess: LP: #1538174. Looking for ways to do it better instead of sleeping 1 second - otherwise I'll just bump the delay.
1787429,2018-08-16 18:26:20 UTC,From the logs the kernel bug seems to be affecting JAVA rather than tomcat7 itself.
1787429,2018-08-16 17:28:08 UTC,Bug is reproduceable here - affected all of our tomcat7 instances running on trusty...
1787429,2018-08-16 17:30:40 UTC,Restarted rolling back to 3.13.0-153-generic and tomcat7 starts fine
1787429,2018-08-16 16:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787429,2018-08-16 17:48:15 UTC,"I have completed the apport-collect, and attached some kernel logs, changing status to confirmed."
1787430,2018-08-16 15:48:02 UTC,Seems like it is a jenkins bug https://issues.jenkins-ci.org/browse/JENKINS-49644 not returning currentExecutable
1787431,2019-05-17 16:35:59 UTC,"yes, It can be removed; it pretty weak indeed as you say."
1787431,2019-05-17 09:29:35 UTC,"Hi Valentin,"
1787436,2020-03-26 03:01:37 UTC,"Based on autopkgtest history, this must have gotten fixed somehow."
1787438,2018-11-26 12:41:53 UTC,"Hello Seth, or anyone else affected,"
1787438,2018-12-03 12:57:46 UTC,Tested that it builds with 4.15 and 4.18 kernels after installing the package from bionic-proposed.
1787438,2018-12-03 15:23:34 UTC,This bug was fixed in the package openafs - 1.8.0~pre5-1ubuntu1
1787438,2018-12-03 15:23:43 UTC,"The verification of the Stable Release Update for openafs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1787439,2019-10-07 00:42:24 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1787439,2019-10-07 12:03:24 UTC,Tests look to be passing now with 4.18 kernels.
1787440,2019-02-14 12:10:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1787443,2018-11-26 12:53:12 UTC,"Hello Seth, or anyone else affected,"
1787443,2018-12-03 12:26:33 UTC,Tested -proposed package with 4.15 and 4.18 kernels.
1787443,2018-12-03 15:23:13 UTC,This bug was fixed in the package xtables-addons - 3.0-0.1ubuntu1
1787443,2018-12-03 15:23:18 UTC,"The verification of the Stable Release Update for xtables-addons has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1787455,2018-08-19 22:59:28 UTC,"On Sun, Aug 19, 2018 at 09:53:04PM -0000, Simon Déziel wrote:

>       But, the Applied-Upstream field can also refer to an upstream
> version incorporating/superseeding the said patch.
"
1787455,2018-08-20 05:08:54 UTC,"On Sun, Aug 19, 2018, 4:05 PM Robie Basak <email address hidden>
wrote:"
1787455,2018-08-17 10:31:28 UTC,"On Thu, Aug 16, 2018 at 09:10:13PM -0000, Nish Aravamudan wrote:

> I was thinking that, at a minimum, git-ubuntu (e.g., in lint) could
> check if the merge target is past the Applied-Upstream of any patch and
> if so, emit a warning?
"
1787455,2018-08-17 00:25:11 UTC,"On 2018-08-16 05:10 PM, Nish Aravamudan wrote:

> I was thinking that, at a minimum, git-ubuntu (e.g., in lint) could
> check if the merge target is past the Applied-Upstream of any patch and
> if so, emit a warning?
"
1787455,2018-08-16 21:10:13 UTC,"I was thinking that, at a minimum, git-ubuntu (e.g., in lint) could check if the merge target is past the Applied-Upstream of any patch and if so, emit a warning?"
1787455,2018-08-16 20:32:59 UTC,Thank you for the suggestion.
1787455,2018-08-19 21:53:04 UTC,"Granted, if the Applied-Upstream is a URL/commit ID, git-ubuntu won't be able to do much about it unless it learns about the upstream remote as well. But, the Applied-Upstream field can also refer to an upstream version incorporating/superseeding the said patch. In such case, it would be a simple version string comparison."
1787460,2019-01-31 09:08:15 UTC,This bug was fixed in the package apt - 1.6.8
1787460,2019-03-05 22:26:54 UTC,"Hello Dean, or anyone else affected,"
1787460,2019-03-05 22:35:19 UTC,"Hello Dean, or anyone else affected,"
1787460,2019-03-14 12:15:12 UTC,"Hello Dean, or anyone else affected,"
1787460,2019-03-14 12:21:50 UTC,"Hello Dean, or anyone else affected,"
1787460,2019-03-15 11:03:51 UTC,"So, unattended-upgrades refused to treat linux-image-generic as autoremovable in xenial and trusty; so let's look at apt itself:"
1787460,2019-03-21 11:05:31 UTC,This bug was fixed in the package apt - 1.0.1ubuntu2.22
1787460,2019-03-22 04:58:39 UTC,Are we still going to change the section of the metapackages? Those tasks are still open.
1787460,2020-03-07 21:21:53 UTC,"Hi,"
1787460,2020-07-02 19:25:59 UTC,"Ubuntu 19.04 reached end of life on January 23, 2020.  I am therefore marking this bug 'wontfix' for that release."
1787460,2020-07-05 07:10:15 UTC,The issues with virtualbox and hwe can be tracked in bug 1866518 or bug 1874309
1787460,2019-01-31 09:08:04 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1787460,2019-03-21 11:00:26 UTC,This bug was fixed in the package apt - 1.2.31
1787460,2019-01-31 09:07:56 UTC,This bug was fixed in the package apt - 1.7.2
1787460,2018-10-30 09:15:34 UTC,apt-side fix in
1787460,2019-01-30 16:14:31 UTC,bionic:
1787460,2019-01-31 09:07:38 UTC,"As per our discussion, releasing this before the 7-day aging period."
1787460,2018-08-17 11:44:04 UTC,"So, this might partially be a linux-meta/overrides bug.  The top-level metas (linux-$flavour) should be in the metapackages section so that if they're removed (for instance, by someone who doesn't want headers, but kinda likes kernels), the manually installed bit is transferred down one level to linux-image-$flavour and linux-headers-$flavour."
1787460,2018-08-17 11:47:17 UTC,"It does appear, however, that despite the above comment (which I think highlights ways we can make this foot a smaller target), this definitely began with human error:"
1787460,2018-09-26 14:18:55 UTC,"As Adam mentioned, the top-level kernel meta packages should change their section to metapackages, so we don't mark linux-image-generic for autoremoval if linux-generic is removed."
1787460,2018-09-27 13:23:01 UTC,"They both sound awfully ""generic"" (pun intended), but I can't really come up with an example for a bad match, so lets just try it I guess."
1787460,2018-08-16 22:31:28 UTC,Looking some more at the apt history log file we can see mutter version 3.28.3-2~ubuntu18.04.1 being installed. This package only exists in the -proposed version of the repository.
1787460,2018-08-16 20:12:31 UTC,Looking at .var.apt.history.log.txt we can see that in a previous package operation linux-generic was removed.
1787460,2019-01-15 20:20:35 UTC,"Hello Dean, or anyone else affected,"
1787460,2019-01-15 20:31:56 UTC,"Hello Dean, or anyone else affected,"
1787460,2019-01-28 16:24:40 UTC,"Hello Dean, or anyone else affected,"
1787460,2019-01-28 16:28:17 UTC,"Hello Dean, or anyone else affected,"
1787460,2019-01-30 16:08:21 UTC,cosmic:
1787460,2019-01-30 16:09:38 UTC,"(in practice the headers do not matter - if you have dkms installed, it will keep the headers alive)"
1787460,2018-11-15 17:25:39 UTC,This bug was fixed in the package apt - 1.8.0~alpha2ubuntu1
1787467,2018-08-16 19:40:08 UTC,An example on how to addres sthis would be the UbuntuForm.
1787467,2019-09-19 11:51:26 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1787469,2018-09-10 17:53:06 UTC,This bug was fixed in the package linux - 4.15.0-34.37
1787469,2018-08-28 17:01:35 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1787469,2018-08-16 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787469,2018-09-05 16:04:58 UTC,-- proposed verification for bionic --
1787471,2018-08-17 15:14:33 UTC,Thanks for reporting.
1787471,2018-08-18 14:08:50 UTC,">I took the liberty of moving this report over to the yubioath-desktop package.
"
1787478,2018-08-28 13:15:15 UTC,This is something that needs to be fixed either in the msxpertsuite metadata (preferably in Debian) or upstream needs to enable https
1787480,2018-08-16 20:49:51 UTC,"11:19 < bdmurray> psusi: How could I recreate the bug? It
                  might be best to test it in a live cd
                  environment.
12:38 < psusi> bdmurray: take an existing hard disk with at
               least one partition on it but no ESP, boot the
               installer in UEFI mode and it will crash when
               it tries to install grub
13:08 < psusi> bdmurray: ohh, and don't do the auto use whole
               disk install or it will make an esp... manual
               partitioning, and don't make an ESP"
1787480,2018-08-16 20:51:08 UTC,It's unknown whether this affects bug pattern checking from all systems or just those running Live CDs.
1787483,2018-11-02 21:32:31 UTC,Even though Tina has both barcodes showing in the working copies tab I wonder if this bug is somehow related to bug #1769678 where you couldn't create two copies at the same time. That bug has a fix released.
1787495,2019-01-30 23:50:09 UTC,This bug was fixed in the package networkd-dispatcher - 2.0-2
1787495,2018-09-19 12:24:20 UTC,Fixed in
1787495,2018-08-31 10:06:31 UTC,Forwarded to https://gitlab.com/craftyguy/networkd-dispatcher/issues/44
1787495,2018-08-31 10:15:53 UTC,systemd: https://github.com/systemd/systemd/issues/575
1787495,2018-08-31 10:12:10 UTC,"systemd also does not document the states itself, only in the source code. it should be in networkctl(1) IMO."
1787495,2018-08-31 10:04:30 UTC,From systemd:
1787495,2018-09-07 09:03:04 UTC,systemd pull request: https://github.com/systemd/systemd/pull/10033
1787499,2018-08-21 17:00:59 UTC,"I looked into this.  The holes are drawn on a separate layer which is then composited to the canvas.  The pads themselves are drawn ""full"" (that is, without regard to their holes)."
1787499,2018-08-21 20:55:50 UTC,And dragging a simplified (no text) footprint in transparent mode ?
1787499,2018-08-21 21:25:31 UTC,"Actually text is easy because it's stroked.  Same for silk and courtyard outlines.  It's the pads that are hard because they're filled shapes (ie: a circle, not a ring)."
1787499,2018-08-25 11:57:42 UTC,"@Jeff,
I learned it the hard way : don't trust grep to locate a piece of code (legacy/accelerated tools)."
1787499,2018-08-25 17:16:27 UTC,"@Jeff,"
1787499,2018-08-25 19:58:31 UTC,"@Franck, the Legacy code won't work with hardware acceleration on graphics cards, so it's a non starter."
1787499,2018-08-26 10:22:04 UTC,"I looked into this some more and I think a ""Use sketch mode when dragging"" option in the PcbNew preferences might be a good compromise."
1787508,2018-08-23 18:35:54 UTC,"Fixed in latest Ubuntu releases, let release managers decide if it can go into Xenial.
Thanks for the offer BTW! :-)"
1787512,2018-03-04 00:56:00 UTC,Similar problem has been detected:
1787512,2018-03-04 08:56:08 UTC,"I can reliably crash GNOME shell by typing ""sc"" in the search bar."
1787512,2018-04-05 19:50:06 UTC,*** Bug 1564261 has been marked as a duplicate of this bug. ***
1787512,2018-03-18 13:21:52 UTC,"Created attachment 1409471
GDB session"
1787512,2018-03-21 19:55:52 UTC,I notified gtk
1787512,2018-03-04 08:58:31 UTC,"By exclusion, I can also tell you that the search provider causing the crash is Files. If I disable it everything seems fine."
1787512,2018-04-17 16:40:27 UTC,*** Bug 1568518 has been marked as a duplicate of this bug. ***
1787512,2019-09-17 09:43:58 UTC,"@vanvugt hi! Nice triage, appreciated."
1787512,2018-11-27 16:09:46 UTC,"This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'."
1787512,2018-11-30 21:03:06 UTC,"Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1787512,2019-09-17 09:11:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787512,2019-09-17 09:54:55 UTC,"Nope, it didn't work."
1787512,2019-09-17 13:12:58 UTC,Found it.
1787512,2019-09-17 15:30:37 UTC,Hey Daniel! I hope you'll take a look here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354
1787512,2018-08-17 02:44:08 UTC,Looks like the new form of old bug 1722599.
1787512,2018-03-02 07:17:22 UTC,*** Bug 1550839 has been marked as a duplicate of this bug. ***
1787512,2018-03-18 13:20:28 UTC,"This is a very annoying bug, so I will help fixing it. I managed to gdb into the crashing gnome-shell with the help of https://fedoraproject.org/wiki/How_to_debug_Wayland_problems ."
1787512,2018-02-06 20:31:46 UTC,Had this twice already. Tried opening Gnome Software from the Dash and then my session crashed.
1787512,2018-02-24 15:27:41 UTC,Similar problem has been detected:
1787512,2017-12-01 22:40:50 UTC,"Description of problem:
Opening pgAdmin III reliably crashes gnome shell"
1787512,2017-12-01 22:40:57 UTC,"Created attachment 1361853
File: backtrace"
1787512,2017-12-01 22:40:59 UTC,"Created attachment 1361854
File: cgroup"
1787512,2017-12-01 22:41:01 UTC,"Created attachment 1361855
File: core_backtrace"
1787512,2017-12-01 22:41:08 UTC,"Created attachment 1361857
File: dso_list"
1787512,2017-12-01 22:41:10 UTC,"Created attachment 1361858
File: environ"
1787512,2017-12-01 22:41:12 UTC,"Created attachment 1361859
File: limits"
1787512,2017-12-01 22:41:06 UTC,"Created attachment 1361856
File: cpuinfo"
1787512,2017-12-01 22:41:18 UTC,"Created attachment 1361861
File: mountinfo"
1787512,2018-02-06 20:30:48 UTC,*** Bug 1542698 has been marked as a duplicate of this bug. ***
1787512,2018-01-31 14:03:46 UTC,*** Bug 1540602 has been marked as a duplicate of this bug. ***
1787512,2018-01-18 15:16:20 UTC,*** Bug 1536076 has been marked as a duplicate of this bug. ***
1787512,2017-12-01 22:41:15 UTC,"Created attachment 1361860
File: maps"
1787512,2017-12-01 22:41:23 UTC,"Created attachment 1361864
File: var_log_messages"
1787512,2017-12-01 22:41:21 UTC,"Created attachment 1361863
File: proc_pid_status"
1787512,2017-12-06 19:55:38 UTC,*** Bug 1522958 has been marked as a duplicate of this bug. ***
1787512,2017-12-01 22:41:20 UTC,"Created attachment 1361862
File: open_fds"
1787517,2018-08-17 04:05:49 UTC,"After digging more in logs look like its happening every days, randomly, i am not seeing any packet loss in network too"
1787517,2018-08-17 04:06:51 UTC,Found related issue here https://bugs.launchpad.net/tripleo/+bug/1691951
1787517,2018-08-17 04:25:36 UTC,This is very similar and interesting: https://bugs.launchpad.net/oslo.db/+bug/1774544
1787517,2018-08-20 15:03:47 UTC,"Found issue is related to F5 (We are not using haproxy), I am investigating issue for documentation and will keep updating this ticket."
1787517,2018-08-21 14:17:29 UTC,Resolved:
1787517,2018-08-21 15:16:47 UTC,It would be great if we make notes in Documentation that if you planning to use F5 load-balancer please make these setting accountable.
1787518,2018-08-20 03:13:39 UTC,I confirmed this.
1787518,2018-08-20 03:47:59 UTC,"Hi Motoki,
Thank you very much!"
1787520,2018-08-20 04:50:29 UTC,"Review in progress for https://review.opencontrail.org/45649
Submitter: Parth Sarupria (<email address hidden>)"
1787520,2018-08-17 09:20:47 UTC,"Review in progress for https://review.opencontrail.org/45631
Submitter: Parth Sarupria (<email address hidden>)"
1787520,2018-08-21 19:26:45 UTC,"Reviewed:  https://review.opencontrail.org/45649
Committed: http://github.com/Juniper/contrail-controller/commit/511964db169182a00953a7ee37382f504973e27d
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1787534,2018-08-21 14:00:38 UTC,I do not have Designate.
1787534,2021-01-24 04:32:23 UTC,Adding following in /etc/neutron/neutron.conf fix my designate error. now sure why do we need this setting if i am not using any l3-agent or tenant based networking. I am using vlan based provider where my Physical router is my gateway.
1787534,2018-08-20 07:28:48 UTC,"Hello,"
1787537,2018-09-19 05:43:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787549,2018-08-20 05:08:17 UTC,"Hi,"
1787549,2018-08-20 05:54:03 UTC,"  Hi,"
1787583,2020-04-01 12:59:47 UTC,"We have the same Problem.....
we can only use a standalone redis server ..btw works in moodle perfect"
1787588,2018-08-17 12:02:40 UTC,Added Trace
1787588,2020-05-28 16:31:09 UTC,Moving between computes with different [libvirt]/images_types settings using live migration like this isn't supported. Additionally I don't believe cold migration between such computes would work either.
1787589,2019-05-16 00:55:52 UTC,Per this page: https://wiki.ubuntu.com/Kernel/Livepatch
1787589,2019-08-11 07:24:08 UTC,We need it for 18.04 too
1787596,2018-08-17 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787596,2018-08-17 13:44:30 UTC,"Just manually giving acpi_rsdp parameter to kexec will make it work, so it should be automatically given despite the xloadflags not being present in bzImage."
1787596,2018-08-17 13:47:42 UTC,"926172d46038d7610b6b8d84e40db727cefb482d (""efi: Export EFI runtime memory mapping to sysfs"") might fix it on the linux side."
1787596,2018-08-17 13:48:13 UTC,"Ideally, kexec-tools should be the package fixed, as this allows it to work on older kernels as well."
1787600,2018-11-12 18:45:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787600,2018-08-18 03:30:58 UTC,"Thank you so much John, I'm trying your solution.
Based on your answer, it seems like this problem is not because of something special in my computer. Does that mean this problem occurs on every other computers running Ubuntu with gnome (Ubuntu 18.01) ?
(I'm new to Ubuntu, so may have some silly questions :-)"
1787600,2018-08-18 02:39:57 UTC,"Thanks John for your answer.
So do you know what cause this bunch of audit messages, and how could I fix that?"
1787600,2018-08-18 01:19:53 UTC,"Sadly yes. AppArmor currently doesn't do audit message deduping, leaving it entirely to the audit infrastructure. Which means denial messages can fill the logs."
1787600,2018-08-18 03:02:16 UTC,Its being caused by the gnome system-monitor snap. Its author is missing some permissions required to use it properly on your system. It looks like the system monitor is running and it keeps polling the file causing this denial.
1787601,2018-09-30 16:08:26 UTC,https://gitlab.com/inkscape/inkscape/commit/c01f30416277ab3b8eeaeebd0c1d9e3fcdf4fd42
1787601,2018-09-26 00:25:10 UTC,Fixed on 9688e38580
1787601,2018-09-25 09:15:42 UTC,"Ohh, yes thanks for notice me!"
1787601,2018-09-26 05:32:43 UTC,Thanks Jabier for fixing this!
1787601,2018-09-25 07:43:52 UTC,"Hi Jabier - changing ""/options/transform/stroke"" doesn't make a difference in my tests."
1787601,2018-09-13 12:38:01 UTC,"As starting point of fix, the bug only happends when scale stroke on transform is check, is a preference option so you can search when is checked as root investigations."
1787601,2018-09-09 09:39:52 UTC,problem not observed if removing viewBox attribute first
1787601,2018-08-17 14:52:36 UTC,Confirmed on Windows 10 with the same version of Inkscape (not reproduced in 0.92.3).
1787601,2018-09-25 09:10:20 UTC,problem not observed if drawing inside a transformed group
1787602,2020-09-29 08:05:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787604,2018-08-17 16:09:24 UTC,I believe this was fixed in a later release of magnum. You can try the following workaround in magnum.conf:
1787604,2018-08-18 14:57:47 UTC,"Hi Rick, Thanks for your reply! Do you know where it was fixed? Might be a bug number or a commit message. Thanks you!"
1787604,2018-08-29 07:51:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787604,2018-11-21 14:12:11 UTC,I can confirm that this is listed as a known issue in the release notes for magnum 6.0.1
1787606,2019-07-04 13:47:50 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.opendev.org/593074"
1787606,2018-08-17 15:14:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/593073"
1787606,2018-08-17 15:14:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/593074"
1787606,2019-07-04 13:47:20 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.opendev.org/593073"
1787609,2018-08-17 15:25:37 UTC,attached Testroute
1787609,2018-08-29 08:50:24 UTC,"Rob Roeterdink has set my by PN this informations:
it looks to me that the problem is in method UpdateInputs() in module Orts.Simulation\Simulation\RollingStocks\SubSystems\TrainControlSystem.cs :"
1787617,2019-09-19 11:58:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1787617,2018-11-30 15:16:25 UTC,"Hello,"
1787622,2018-08-18 07:15:20 UTC,Disabling the proxy in /etc/apt/apt.conf.d/01proxy  (by commenting it with //) fixes the issue for me; I'm proceeding with the upgrade.
1787622,2018-08-22 08:44:57 UTC,I should probably add that apt-cacher-ng was running on a version 14.04 LTS server.
1787629,2018-08-30 13:31:34 UTC,Let's triage it for next cycle.
1787631,2020-03-31 09:01:44 UTC,"This has been fixed already. Not sure when, though."
1787636,2020-05-01 17:53:51 UTC,"Pushed to master, 3.3, 3.4, and 3.5.  Thanks Jason, Dan, and all who tested!"
1787636,2020-03-20 18:20:40 UTC,I rebased the branch on master and added a commit to address Janet's concern in comment #3. I believe the branch is now doing everything that was requested. I have pushed to a collab branch for others to test:
1787636,2020-02-18 18:20:34 UTC,"I tested this today and can confirm that at the consortium level when Show empty volumes, Show empty libraries, Show copy details, and Show volume details are all checked, the list of libraries is in alpha order regardless if a branch has an item or not. Empty libraries remain in alpha order as items are added to branches. Adding an item to BR4, BR4 remains at the bottom of the list."
1787636,2019-06-10 19:03:03 UTC,Gonna take it for a test spin and then assign targets if it works.
1787636,2019-06-10 17:34:49 UTC,This seems to work on Concerto data:
1787636,2020-02-19 15:21:51 UTC,Removing pull request pending developer feedback on the last comment or a new patch.
1787638,2018-08-17 19:02:40 UTC,Please add version info.
1787638,2018-08-17 19:12:23 UTC,"Sorry, I originally included it but then removed it as it wasn't a bug but a feature request.
I'm on 5.0.0 from the Ubuntu stable ppa."
1787643,2018-08-21 13:25:28 UTC,Hmm - are those items transiting for a hold or transiting to return to their home location?
1787643,2018-08-21 18:43:24 UTC,"Yeah, weird. I looked at my own branch's transits for the past 21 days.
There are 425, half were returning home/half were holds, and none show a
patron barcode."
1787643,2018-08-18 21:20:58 UTC,"When I add Patron Name and Patron Barcode to the columns, the columns are
empty. Why is that? The picture is XUL but Webby has the same empty columns."
1787643,2018-08-17 19:52:19 UTC,Went ahead and updated the title of this one to reflect making the option available from the transit list.
1787643,2018-08-17 19:55:54 UTC,Eureka! You're an angel! It worked!
1787643,2018-08-17 19:50:36 UTC,"Also adding a note that if you're viewing the Transit List interface, there's not a way to edit the pickup location from there - you have to go to the patron's account, go to the holds screen, and then use the Actions button to edit the pickup location from there."
1787643,2018-08-17 19:42:52 UTC,"There is a setting in the User Permission Editor for UPDATE_PICKUP_LIB_FROM_TRANSIT which will allow changing the pickup location while an item is in transit. When it arrives wherever it was originally going, it will print out a new transit slip to the location that you've changed it to."
1787643,2018-08-17 20:02:26 UTC,Thanks!
1787644,2020-10-22 08:18:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787646,2018-08-17 20:06:42 UTC,The bug report in the description is incorrect.
1787654,2018-08-20 13:53:01 UTC,"This is a problem with the applications mentioned. Adwaita-dark is the dark variant of the default GTK+ theme, so if the problem exists there, the application must be addressed."
1787656,2019-06-08 08:02:05 UTC,With the advent of ngspice-30 there is a ngspice solution available.
1787656,2019-06-11 15:14:59 UTC,I tried to make the testbox in the sallen_key demos as follows on linux with ngspice 30.
1787656,2019-06-10 16:09:45 UTC,"@Holger, so this is a configuration issue rather than a KiCad bug correct?"
1787656,2019-06-04 21:23:06 UTC,"This windows build should include ngspice 30:
https://kicad-downloads.s3.cern.ch/windows/testing/patched/kicad-patched-372-eb1faebf1-x86_64.exe"
1787656,2019-06-23 21:09:14 UTC,command rusage (without arguments) will yield
1787656,2019-01-01 10:23:22 UTC,ngspice-30 is available with a patch (variable 'controlswait') to allow executing 'rusage' after the simulation.
1787656,2019-06-04 21:21:17 UTC,"@Holder, is any change required anywhere to kicad to make this work if it is already using ngspice 30?"
1787656,2018-08-19 10:20:23 UTC,"The ngspice command
rusage time
will print the total analysis time"
1787656,2018-08-20 20:07:22 UTC,"I tried adding a line with ""rusage time"" as well as "".option rusage time"" in the Simulation settings / Custom tab of the KiCAD GUI, but the behaviour is unchanged.  Having the simulation time read out correctly is not a big deal, but I just wanted to note the bug.  Perhaps it only occurs when ""cheating"" by using NGspice 28 instead of the included version 26 with KiCAD5.0.0."
1787656,2019-06-11 15:06:40 UTC,Where is this elapsed time visible in the GUI?
1787656,2018-10-17 22:29:58 UTC,"@ Holger
Now that I'm non longer in Debug mode, I tried ""rusage time"" between "".control"" and "".endc"", but the KiCAD GUI always shows:"
1787656,2018-08-22 22:48:19 UTC,"I had ""set ngdebug"" in my .spiceinit.  I have removed this line, and now I see
""
 Reference value :  0.00000e+00
 Reference value :  2.03435e-02
 Reference value :  4.55745e-02
 .
 .
 .
""
This does indicate the time correctly.  It seems the bug is only applicable to NGspice debug mode, where the time elapsed reads as a percentage (correctly) and a time (incorrect starting point)."
1787656,2018-12-07 13:17:24 UTC,The same reason as we have in https://bugs.launchpad.net/kicad/+bug/1788676:
1787663,2018-08-19 05:16:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787665,2018-08-17 22:15:35 UTC,tnx in advance...
1787676,2018-08-17 23:11:28 UTC,"Working branch user/jeffdavis/lp1787676-z3950-sort-local-catalog has a commit which reverts the previous fix and sorts Z39.50 sources in JS instead, allowing us to keep Local Catalog at the top of the list."
1787676,2018-12-07 03:21:32 UTC,"Works well for me.  Thanks, Jeff!  I created a rebased signoff branch called user/sandbergja/lp1787676-z3950-sort-local-catalog-signedoff"
1787676,2019-08-05 14:46:49 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jeff and Jane!"
1787690,2018-08-27 00:16:05 UTC,Possibly the message does not have a text/html part. Have you tried the following in pass_mime_types:
1787690,2018-08-27 04:24:58 UTC,Hi Mark -
1787690,2018-08-28 23:15:26 UTC,This is the correct tracker for Mailman 2.1 issues.
1787691,2018-08-23 03:56:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787691,2019-04-15 03:29:10 UTC,I was able to work around this bug by manually downloading the libcdt5 package and installing it with dpkg.
1787692,2018-09-01 22:39:35 UTC,It claims that a Firewall may be preventing me from getting email.
1787692,2018-09-16 21:17:12 UTC,"Resolved my boot issue, I think. Errors on FAT32 ESP, my sda1."
1787692,2018-08-23 21:13:33 UTC,"May be related to this bug.
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518"
1787692,2018-08-24 20:02:50 UTC,"I have been booting with the same version of UEFI from Asus since April.
But now either UEFI or Ubuntu is deleting all UEFI entries and creating multiple new UEFI entries from boot device."
1787692,2018-08-20 05:28:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787696,2018-08-18 06:41:43 UTC,apport information
1787696,2018-08-18 06:41:44 UTC,apport information
1787696,2018-08-18 06:41:45 UTC,apport information
1787696,2018-09-21 22:27:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787701,2020-07-01 00:24:26 UTC,Fixed in version python-simpy3/3.0.10-3
1787710,2018-08-18 12:22:31 UTC,"The attachment ""shrabon bangla keyboard layout code"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1787710,2018-08-18 09:38:26 UTC,Thanks for your proposed layout!
1787712,2018-08-18 09:58:36 UTC,Installed packages attached. Sources.list.d is empty.
1787712,2018-08-19 20:24:20 UTC,"Replacing sources.list with the following fixed it
deb http://us.archive.ubuntu.com/ubuntu/ bionic main universe restricted multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ bionic main universe restricted multiverse"
1787712,2018-08-19 20:25:35 UTC,correction: replace bionic with xenial
1787712,2019-01-25 14:27:42 UTC,"I had same problem, replaced sources.list with suggested one (xenial instead of bionic) but still unable to upgrade"
1787712,2019-01-25 14:28:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787712,2019-02-10 16:55:23 UTC,In my case I am trying to update from Ubuntu 18.04 to 18.10 and get the same behaviour (apart from the distribution name):
1787712,2019-10-15 07:20:10 UTC,I've had this issue:
1787712,2019-09-20 05:03:27 UTC,I am trying to upgrade from 16.04 to 18.04
1787715,2018-10-02 18:25:19 UTC,"A workaround covering some of the more common cases is found in githash 596dcd6c097864f70f5231069733e6f747046301, improving upon earlier 92d6e37f62a54361be4b87e37cd64d8c4cfea5a1."
1787717,2018-08-18 15:52:30 UTC,"currently apparmor can not use the cache for stdin because the cache file names are based on the policy file names, not the profiles in the file. As the profiles within the file are kept together as a single load unit."
1787717,2018-08-18 15:53:55 UTC,oh and (null) is not the cache file name it is the null pointer to the cache file name. The parser should not be reporting that it wrote that.
1787717,2018-08-18 17:59:56 UTC,"""(null)"" _is_ the cache file name, so the parser is correct in reporting that it wrote that cache file ;-)"
1787722,2018-08-18 13:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787722,2018-08-18 14:10:26 UTC,I don't think logs can help since this is a specific issue with a set of packages; changing to Confirmed.
1787722,2018-08-21 22:08:34 UTC,"If you need further logs to understand the issue, you haven't read the text of the report."
1787726,2018-08-19 16:26:52 UTC,Same for me except my Gtk-WARNING lines alternate between -11 and -1.  It draws a window that almost looks usable but the window is unresponsive and just there until apport is done and then it disappears.
1787726,2018-08-18 13:57:24 UTC,"When i run dmesg command, with each unsucessful launch of slic3r appears row like this:"
1787726,2019-05-15 20:06:33 UTC,"I'm also experiencing this bug after upgrading from 16.04 to 18.04.
Removing and reinstalling the package and .Slic3r dir does not fix it."
1787726,2018-08-19 16:27:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787726,2018-10-25 15:36:43 UTC,Same Problem...
1787737,2018-08-18 15:53:27 UTC,Updated the PC. Bug occured
1787740,2018-08-21 18:34:18 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1787742,2019-01-24 13:46:23 UTC,"Mainly, this one seems really helpful:
commit adf26a356f132e35093585521ea3e36cd185af83
Author: Stanislaw Gruszka <email address hidden>
Date:   Wed Sep 26 12:24:56 2018 +0200"
1787742,2019-01-24 13:45:09 UTC,There are fixes in kernel > 4.18. Please try latest mainline kernel.
1787742,2019-01-21 17:04:26 UTC,I can confirm this is still an issue on Ubuntu 18.10 (AMD64) running Linux Kernel 4.18.0-13-lowlatency (x86_64)
1787742,2019-01-03 11:52:06 UTC,"How can it see the 2.4GHz if it's a 5GHz adapter?
Is there some way I can get it to connect to 2.4GHz signals as well? 😊"
1787742,2019-01-03 00:21:57 UTC,"I can confirm that after upgrading to Kernel 4.18.0-13 , and moving up to ubuntu 18.10
BCM4360 802.11ac Wireless Network Adaptor (rev 03)
Still not able to view 5Ghz networks .
Wifi Radar only see's G Networks."
1787742,2018-08-21 21:13:26 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1787742,2018-08-30 16:55:11 UTC,"@jsalisbury, okay, I just tried it on the latest RC1 build as of 08/30/2018, and the T1U Archer wifi chip still doesn't activate."
1787742,2018-08-30 15:08:41 UTC,"@jsalisbury, which Upstream Kernel would you like me to attempt?"
1787742,2018-08-30 13:39:33 UTC,"Hey Joseph,
Sorry for the late response.
I'll try this today and get back to you."
1787742,2019-02-08 04:32:33 UTC,Still no fix on my end that works :-(
1787742,2018-10-19 15:24:45 UTC,Update: System upgraded to public release of Ubuntu 18.10 'Cosmic.' Wifi driver still not present for T1U Archer.
1787743,2019-04-04 16:47:56 UTC,"I installed Ubuntu Studio and experienced same with amd64 platform, vmlinuz-5.0.0-8-lowlatency.  After installing generic kernel, usb mouse performance returned to normal. I had this also with the live version 18.xx last fall, and never installed."
1787743,2019-04-04 17:19:03 UTC,"Mine is Ubuntu Studio 19.04 beta, attaching dmesg with vmlinuz-5.0.0-8-lowlatency."
1787743,2019-03-31 15:11:34 UTC,"Yep, same issue here on Ubuntu 18.10, 4.18.0-16-lowlatency kernel."
1787743,2019-04-03 18:00:14 UTC,Thank you
1787743,2019-05-03 00:03:33 UTC,"Today I installed Ubuntu Studio 18.10 64bit, after install I updated 4.18.0-18-lowlatency and now instead of what I observed in 4.15 kernels, see that IRQ16 nobody cares does not occur and my mouse is OK.  A780gm-a motherboard , SB700.
Happier that I have progress but note I have IRQ18 nobody cares event and an IRQ18 disabled occurring.  Moving my mouse to the front panel exhibits same laggy behavior.
$ cat /proc/interrupts
           CPU0       CPU1       CPU2       CPU3
  0:        116          0          0          0   IO-APIC   2-edge      timer
  1:          0          0        775          0   IO-APIC   1-edge      i8042
  8:          0          0          0          1   IO-APIC   8-edge      rtc0
  9:          0          0          0          0   IO-APIC   9-fasteoi   acpi
 14:          0          0          0          0   IO-APIC  14-edge      pata_atiixp
 15:          0          0       1476          0   IO-APIC  15-edge      pata_atiixp
 16:        571          0        107          0   IO-APIC  16-fasteoi   ohci_hcd:usb3, ohci_hcd:usb4, snd_hda_intel:card0
 17:          0          0          0          0   IO-APIC  17-fasteoi   ehci_hcd:usb1
 18:          0      51217          0          0   IO-APIC  18-fasteoi   ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7, radeon
 19:         59          0          0         32   IO-APIC  19-fasteoi   ehci_hcd:usb2, snd_hda_intel:card1
 22:       9134      36093          0          0   IO-APIC  22-fasteoi   ahci[0000:00:11.0]
 24:          0          0          0      17924   PCI-MSI 1048576-edge      enp2s0"
1787743,2019-04-01 04:33:58 UTC,"Jaap, please attach dmesg, thanks!"
1787743,2018-08-21 21:13:04 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1787743,2019-03-03 19:22:18 UTC,"Bug still occurs on my systems as well, all up-to-date using the standard
upgrade channels on 18.10."
1787743,2019-01-23 18:46:47 UTC,"Bug still exists on package named linux-image-4.18.0-13-lowlatency.
Can´t use it at all, bug exists on ubuntu studio distro as well."
1787743,2018-10-21 04:18:04 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1787747,2018-09-11 07:54:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787747,2020-08-09 22:42:33 UTC,"store-url: https://snapcraft.io/slack
contact:   https://get.slack.help/hc/en-us"
1787755,2018-08-18 19:10:24 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f056b6e0b9a ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f056b6e23f0 ""malloc_consolidate(): invalid chunk size"") at malloc.c:5350
 malloc_consolidate (av=av@entry=0x7f056b915c40 <main_arena>) at malloc.c:4441
 _int_malloc (av=av@entry=0x7f056b915c40 <main_arena>, bytes=bytes@entry=8192) at malloc.c:3703
 __libc_calloc (n=n@entry=1, elem_size=elem_size@entry=8192) at malloc.c:3436"
1787758,2018-08-20 19:24:47 UTC,"Ok, I removed the OpenuRL call to Firefox."
1787758,2018-08-20 15:07:17 UTC,"I don't think it believe it is considered a bug, it was intentionally removed from what I can tell."
1787758,2018-08-20 12:27:54 UTC,"Apparently this is a ""bug"" in Firefox,
  https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1425972
but I have no idea what is being considered the ""bug"" and how they are fixing it."
1787758,2018-08-20 07:57:39 UTC,"I see only the first call.  And when I try the command from the command line, it does indeed not give any error message or status code; it fails silently.  From your paths I suspect you are running on Windows.  I'm running on Linux; maybe there is a small difference in the start scripts."
1787758,2018-08-20 07:12:03 UTC,I take that back. I see two invocations in the *Messages* buffer:
1787758,2018-08-20 07:03:13 UTC,"Ok, the reason it is failing for you is independent of the ""-remote"" call, because VM tries it both ways, with and without ""-remote""."
1787758,2018-08-20 06:20:27 UTC,"Actually, the ""-remote OpenURL"" invocation failed and VM fell back to the standard call. So, perhaps the ""-remote"" stuff should be removed. Is there a man page for Firefox somewhere?"
1787758,2018-08-19 20:24:55 UTC,It works for you?  Now I'm getting confused.
1787758,2018-08-19 20:02:27 UTC,"The current settings work fine for me, using Firefox Quantum 61.0.2. And, it is working irrespective of whether there is a Firefox window already open or not."
1787759,2018-08-26 14:29:51 UTC,"@Ron, not sure which setting you're talking about."
1787759,2018-08-26 17:47:33 UTC,"On 08/26/2018 09:29 AM, Jeff Young wrote:

> @Ron, not sure which setting you're talking about.
>
> Eeschema has wire and bus thickness settings for display.  Not sure if
> they're used for print/plot or not.  They are *not* project-specific.
>
> The print and plot dialogs have default pen size and default line width.
> I think those are only used when no other line width is specified, but
> they might also be enforced as minimums.  Those are also *not* project-
> specific.
>


Yes, that was my whole point. /Sometimes/ these settings to be
project-specific, and right now they're not."
1787759,2018-08-26 18:55:58 UTC,"Of course, what I meant to write was that ""/Sometimes/ these settings need to be project-specific ...""."
1787760,2020-08-21 15:54:54 UTC,"Will this issue be fixed in Rocky?  As of 6/15/20, this was still failing in Rocky per https://bugs.launchpad.net/kolla-ansible/+bug/1883604"
1787760,2020-08-21 16:34:25 UTC,It's in https://review.opendev.org/737198
1787760,2020-09-01 17:54:12 UTC,When is the CI expected to be happy again?
1787760,2019-01-07 14:39:24 UTC,This issue was fixed in the openstack/kolla 8.0.0.0b1 development milestone.
1787760,2021-02-14 20:46:51 UTC,"Also, it appears that the releases specified in the timeline, https://launchpad.net/kolla-ansible/+series, do not correspond to what is available in pip, e.g."
1787760,2018-10-07 11:07:11 UTC,"This should fix it:
add in kolla/docker/zun/zun-base/Dockerfile.j2
the line:
sed -i 's|^exec_dirs.*|exec_dirs=/var/lib/kolla/venv/bin,/sbin,/usr/sbin,/bin,/usr/bin,/usr/local/bin,/usr/local/sbin|g' /etc/zun/rootwrap.conf
after line (and don't forget the ""\""):
&& chown -R zun: /etc/zun /var/www/cgi-bin/zun \"
1787760,2018-10-07 10:59:17 UTC,"When I compare the rootwrap.conf from nova, then the execution path in the venv is missing."
1787760,2018-08-18 20:02:55 UTC,"Note: Starting from Rocky, Zun has switched to privsep to execute privilege commands: https://bugs.launchpad.net/zun/+bug/1749342"
1787760,2020-09-02 17:00:08 UTC,"We have been hit by lots of issues we didn't have control over. We are slowly recovering. EM (Extended Maintenance) branches are not the main focus, hence why it takes the longest. External help is appreciated."
1787760,2018-10-07 14:42:56 UTC,"Yes, this is fixed by: https://review.openstack.org/#/c/606854/"
1787760,2020-09-04 09:34:12 UTC,It's getting merged.
1787760,2018-10-22 12:53:29 UTC,This issue was fixed in the openstack/kolla 7.0.0.0rc3 release candidate.
1787760,2021-02-14 20:01:30 UTC,"What is the kolla-ansible's EM branch support policy?  Ocata and Pike are still in EM, e.g. https://releases.openstack.org/ocata/, but kolla-ansible has both releases marked as 'Obsolete.'"
1787760,2021-02-15 09:38:07 UTC,Hi. Typically what we aim for is to have one release in EM at any time. Currently that is Stein. In that phase we will accept patches but will not actively maintain the code.
1787760,2021-02-15 16:31:32 UTC,"Per the timeline, https://launchpad.net/kolla-ansible/+series, Queens' status is 'Current Stable Release' and Rocky's status is 'Supported.'  Also, Ussari's status is ' Pre-release Freeze' Is this information correct?"
1787760,2021-02-16 09:16:31 UTC,I will update the status of the releases.
1787760,2021-02-16 18:20:20 UTC,"I realize our conversation is off-topic of the original issue but this may be as good of a place as any to have it. Firstly, I want to complement the kolla-ansible team on responding to these issues and I do understand your statements above."
1787760,2021-02-17 09:03:51 UTC,"Per the linked document, EM is provided ""While there are community members maintaining it."" All I can say is, if you want to come and maintain these older branches upstream, we will be happy to assist."
1787765,2018-08-20 05:16:09 UTC,"Hi,"
1787765,2018-08-20 06:06:28 UTC,No! didn't work out.
1787765,2018-08-18 20:36:34 UTC,Following is the hp-check -t output file
1787769,2020-08-23 04:17:21 UTC,[Expired for lvm2 (Ubuntu) because there has been no activity for 60 days.]
1787770,2018-08-20 07:24:51 UTC,"File tsection.dat may be opened with any text editor, like notepad, notepad++ and so on. From the logfile it seems that your tsection.dat hasn't a correct format. If your route doesn't require a special tsection.dat, reload an updated tsection.dat e.g. from trainsim.com."
1787771,2018-08-19 01:10:47 UTC,"crash confirmed on Windows 10, Inkscape 0.92+devel (14d07e6, 2018-08-17)"
1787771,2018-08-19 13:30:15 UTC,"Thank you, Alvin!!!"
1787771,2019-05-22 13:45:46 UTC,Closing  because it seems to be fixed
1787771,2018-08-19 01:24:23 UTC,"backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x0106cf67 in libinkscape_base!_ZNK7SPCurve4copyEv () from c:\app\temp\inkscape_devel\libinkscape_base.dll
(gdb)
(gdb) bt
#0  0x0106cf67 in libinkscape_base!_ZNK7SPCurve4copyEv () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#1  0x01316498 in libinkscape_base!_ZN9SPUsePath14refresh_sourceEv () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#2  0x01313e3e in libinkscape_base!_Z23refresh_textpath_sourceP10SPTextPath ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#3  0x0131490d in libinkscape_base!_ZN10SPTextPath6updateEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#4  0x012e571e in libinkscape_base!_ZN8SPObject13updateDisplayEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#5  0x013111ff in libinkscape_base!_ZN6SPText6updateEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#6  0x012e571e in libinkscape_base!_ZN8SPObject13updateDisplayEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#7  0x012bad87 in libinkscape_base!_ZN7SPGroup6updateEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#8  0x012e571e in libinkscape_base!_ZN8SPObject13updateDisplayEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#9  0x012bad87 in libinkscape_base!_ZN7SPGroup6updateEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#10 0x012e571e in libinkscape_base!_ZN8SPObject13updateDisplayEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#11 0x012bad87 in libinkscape_base!_ZN7SPGroup6updateEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#12 0x012f9aeb in libinkscape_base!_ZN6SPRoot6updateEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#13 0x012e571e in libinkscape_base!_ZN8SPObject13updateDisplayEP5SPCtxj () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#14 0x0171dcec in libinkscape_base!_ZN10SPDocument14ensureUpToDateEv () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#15 0x0172792b in libinkscape_base!_Z12sp_file_openRKN4Glib7ustringEPN8Inkscape9Extension9ExtensionEbb ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#16 0x0172c65a in libinkscape_base!_Z19sp_file_open_dialogRN3Gtk6WindowEPvS2_ ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#17 0x01802476 in libinkscape_base!_ZN8Inkscape8FileVerb7performEP8SPActionPv ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#18 0x01a1b877 in libinkscape_base!_ZN4sigc8internal9slot_callINS_12bind_functorILin1ENS2_ILin1ENS_16pointer_functor2IP8SPActionPvvEES6_NS_3nilES8_S8_S8_S8_S8_EES5_S8_S8_S8_S8_S8_S8_EEvJEE7call_itEPNS0_8slot_repE ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#19 0x0117a2c9 in libinkscape_base!_Z17sp_action_performP8SPActionPv () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#20 0x63c45f03 in ?? () from c:\app\temp\inkscape_devel\libgobject-2.0-0.dll
#21 0x63c5836d in ?? () from c:\app\temp\inkscape_devel\libgobject-2.0-0.dll
#22 0x63c60007 in ?? () from c:\app\temp\inkscape_devel\libgobject-2.0-0.dll
#23 0x63c60857 in ?? () from c:\app\temp\inkscape_devel\libgobject-2.0-0.dll
#24 0x668fe539 in ?? ()..."
1787775,2018-12-16 14:29:58 UTC,"As I said, I can't boot without recovery mode."
1787775,2018-12-09 23:01:38 UTC,Tried it today. Couldn't load the kernel with ubuntu-16.04.4 on Yoga 530-14arr.
1787775,2018-12-12 09:01:38 UTC,"Hey Kai-Heng Feng, thank you so much. This just works nice! I would like to buy you a beer!"
1787775,2018-12-12 06:25:38 UTC,I can confirm kernel in #34 works for Latitude 5495 which also uses AMDI0011. Please try the kernel out so I can update the driver.
1787775,2018-12-10 03:46:47 UTC,"Please attach dmesg, thanks!"
1787775,2019-01-23 19:36:37 UTC,"Can confirm that kernel from #34 works with touchpad and touchscreen on the flex-6-14arr, but will only boot from recovery mode."
1787775,2018-12-06 16:06:24 UTC,Thank you very much.
1787775,2018-12-06 10:45:20 UTC,"Please test this kernel out:
https://people.canonical.com/~khfeng/lp1787775/"
1787775,2018-12-06 05:19:11 UTC,No you don't need to do anything. I'll update the driver in Ubuntu's kernel.
1787775,2018-12-16 16:57:35 UTC,@hookedbehemoth: Not 100% sure but it looks like you booted the old kernel (where the driver was builtin) with the new modules.
1787775,2018-12-04 19:06:46 UTC,Is there anything i may try to get this working or is there any information that i can give to make diagnosis more easy? I already tried building the kernel from linux-source package matching my version and installing the dkms stuff but had no luck so far. Any guesses?
1787775,2018-12-06 18:57:44 UTC,Only touchpad.
1787775,2018-12-16 17:13:02 UTC,I tried installing the kernel with a fresh install of ubuntu-16.04.4 because it was the only version with a kernel lower then 4.15xx that I had on my system.
1787775,2019-04-02 17:32:31 UTC,tested on cosmic without mp2 dmks module and tochpad and screen are working fine :)
1787775,2018-12-16 17:44:09 UTC,"> Kai is waiting for the driver to be accepted by Linux's maintainers before applying it to Ubuntu's kernel.
"
1787775,2019-03-28 16:41:44 UTC,"I'm using a Ideapad 530s-14ARR, Linux version 5.0.3-050003-generic, Ubuntu 18.04."
1787775,2019-03-29 03:56:47 UTC,"The driver has landed to upstream, I'll build a test kernel to let everyone verify."
1787775,2019-03-29 15:12:34 UTC,"I built kernels for Bionic, Cosmic and Disco, please test:
https://people.canonical.com/~khfeng/lp1787775/"
1787775,2019-03-29 15:13:21 UTC,And please remove the MP2 DKMS to really test the kernel.
1787775,2018-11-24 16:07:50 UTC,I am just compiling na fresh vanilla kernel (4.20) and will then try this: https://github.com/Syniurge/i2c-amd-mp2
1787775,2019-04-02 19:25:15 UTC,I can also confirm the fix is working great for touchpad and touchscreen on my YOGA-530-14ARR (AMD® Ryzen 3 2200u with radeon vega mobile gfx × 4 ).
1787775,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1787775,2019-05-13 19:28:27 UTC,Just as a usage report after a while:
1787775,2019-05-16 15:03:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1787775,2019-05-20 14:01:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1787775,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1787775,2018-12-16 17:41:19 UTC,"That's strange then, maybe the old driver is still builtin in https://people.canonical.com/~khfeng/lp1787775/."
1787775,2018-11-12 07:32:23 UTC,Similar to LP: #1795292?
1787775,2018-10-09 09:10:22 UTC,Wifi works with using rtl8821ce drivers found here: https://github.com/tomaspinho/rtl8821ce
1787775,2018-11-11 21:10:18 UTC,@Syniurge: Wifi and Bluetooth do work on the 530-15IKB no matter if ideapad-laptop is loaded or not. Try `rfkill` to see the current hard- and softlock state.
1787775,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1787775,2018-08-19 00:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787775,2018-08-19 11:24:16 UTC,apport information
1787775,2018-08-19 11:24:17 UTC,apport information
1787775,2018-08-21 21:12:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1787775,2018-08-22 20:32:39 UTC,Tried both v4.18.3 and v4.18.4 using UKUU. Nothing changed.
1787775,2018-09-21 15:20:47 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  simon      1095 F.... pulseaudio
 /dev/snd/controlC0:  simon      1095 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-09-21 (0 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS ""Bionic Beaver"" - Release amd64 (20180725)
IwConfig:
 enx0050b61b278f  no wireless extensions."
1787775,2018-09-21 15:20:47 UTC,apport information
1787775,2018-09-21 15:20:48 UTC,apport information
1787775,2018-09-21 15:20:49 UTC,apport information
1787775,2018-09-21 15:20:50 UTC,apport information
1787775,2018-09-21 15:20:51 UTC,apport information
1787775,2018-11-11 21:24:12 UTC,"Sorry, this was for the Yoga 530-14ARR, I should have specified. And by ""Wifi works with this driver"", I meant https://github.com/tomaspinho/rtl8821ce"
1787775,2018-09-21 15:20:52 UTC,apport information
1787775,2018-09-21 15:20:54 UTC,apport information
1787775,2018-09-21 15:20:54 UTC,apport information
1787775,2018-09-21 15:20:55 UTC,apport information
1787775,2018-09-21 15:20:56 UTC,apport information
1787775,2018-09-21 15:20:57 UTC,apport information
1787775,2018-09-21 15:20:58 UTC,apport information
1787775,2018-09-21 15:21:00 UTC,apport information
1787775,2018-10-09 09:26:28 UTC,"Wifi does work on Yoga 530-15, but sometimes doesn't after reboot and only another reboot (off/on) helps."
1787775,2018-11-01 06:23:01 UTC,"Found this patch, that will hopefully solve this problem: https://<email address hidden>/msg1793230.html"
1787775,2018-11-01 09:27:26 UTC,"Found this patch, that will hopefully solve this problem: https://<email address hidden>/msg1793230.html"
1787775,2018-11-11 10:46:54 UTC,My model is a Yoga 530-14arr
1787775,2018-11-11 19:14:22 UTC,(Reposting the workaround for the WiFi I mentioned on Github)
1787775,2018-09-21 15:20:53 UTC,apport information
1787775,2018-12-16 19:44:43 UTC,Thanks a lot. Works like a charm.
1787775,2018-12-17 05:10:42 UTC,[    0.000000] Linux version 4.15.0-42-generic (buildd@lgw01-amd64-023)
1787778,2018-08-21 18:30:19 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1787785,2018-08-20 23:54:10 UTC,Binnmus scheduled for raspbian stretch and buster.
1787792,2018-11-21 10:46:06 UTC,"Both in LB and OVS, you have QoS support in both directions (egress and ingress). Of course, the QoS rule is applied at L2 (no IP classification). The QoS policies are applied in the compute node, relieving the network node from applying those QoS policies and reducing the network traffic in the OpenStack cluster."
1787792,2018-08-20 08:09:12 UTC,"That would IMO require to implement classful bandwidth limits but as for now I don't think we have resources to implement that.
If You would like to work on that - it would be great. I can of course help You with that as much as it will be possible.
We have Neutron QoS meetings on IRC every second Tuesday (http://eavesdrop.openstack.org/#Neutron_QoS_Meeting) - if You have any questions or You wants to discuss that, You are welcome :)"
1787792,2018-08-23 22:26:55 UTC,Let's discuss first in the QoS meeting of next week. After that we can bring it up to the drivers meeting
1787792,2018-08-28 04:06:13 UTC,"Ha, I ask yulong, he has no plan to support this, ;-(. So I think we should treat it as a total new feature. ;-). Gogogo, fight for neutron. ;-)"
1787792,2018-08-28 04:08:47 UTC,"@Slawek Kaplonski, totally agree with you, the current qos bw should be more classified. As I think the current tc-wrapper is too specific for very limite use cases. We should refact it, I think."
1787792,2018-08-28 08:58:36 UTC,"@zhaobo: yes, I agree that it will have to be changed. Also in case of QoS for vpnaas it will require some changes and support for classful rules in tc. So that should help :)"
1787792,2018-08-29 08:30:11 UTC,"During the qos meeting, ipv6 traffic control need some validation.
So here is my testing, the following rules can be successfully installed to the host:
tc filter add dev bond1 parent 1: protocol ipv6 prio 1 u32 match ip6 src fe80::fc16:3eff:fe2a:d740 flowid 1:10
tc filter add dev bond1 parent 1: protocol ipv6 prio 1 u32 match ip6 src fe80::fc16:3eff:fe57:d2c5 flowid 1:11"
1787792,2018-08-30 23:19:46 UTC,This topic has been scheduled for discussion during the Denver PTG on Friday 14th at 10:45: https://etherpad.openstack.org/p/neutron-stein-ptg
1787792,2018-09-14 16:12:46 UTC,"As discussed on PTG next steps can be:
1. Investigate how we can use Common Classifier Framework to associate QoS rules with some classifiers and apply it then only for specific class of traffic - then it will be able to use it for BW limit on FIP and on L2 port levels as well as for e.g. DSCP marking rules and other things,
2. Make some PoC of such solution or maybe find if there are other ways to do something like that,
3. In case of VPN QoS we will also have to implement some support for classful bw limits in tc driver so it may be reused in case of this RFE also."
1787793,2018-08-30 23:20:39 UTC,This topic has been scheduled for discussion during the Denver PTG on Friday 14th at 10:45: https://etherpad.openstack.org/p/neutron-stein-ptg
1787793,2018-08-29 05:40:04 UTC,"After the discussing during qos meeting last day [1], I think we have some work needs further study.
For the floating IPs bandwidth share, let me state some limitation of neutron first:
1. DVR scenario, floating IPs are hosting in different physical host, the bandwidth sharing now seems hard to achieve.
2. For one project, centralized floating IPs are located in the different router may still has no way to share the bandwidth. The router may schedule to different physical hosts too.
3. If you have mutiple external networks (floating IP networks), and each has its own NIC, then the share can not achieve. (p.s., neutron does not allow set mutiple gateway for router, so this seems not hurts so much.)
   Share floating IP bandwidth cross such external networks is not available.
4. So, the last one available scenario is floating IPs bandwidth hosted by one single centralized router."
1787793,2018-08-28 10:48:09 UTC,"@Slawek Kaplonski, bandwidth quota can be introduced to the neutron, since users can not use it unrestrainedly. But user may complain why pay for a large bandwith quota but not acctually use it."
1787793,2018-08-27 07:57:10 UTC,"It's maybe not very good idea but what if we could treat bandwidth as any other resource and give users some quota of bandwidth which they can use as they want. Then user could be able to use bandwidth which he pays for in the way he wants to use.
Maybe it should be then divided for ""FIP BW Quota"" and ""Port BW Quota"" in separate as it's different kind of traffic.
What You think about such idea?"
1787793,2018-08-28 04:02:30 UTC,"@yulong, currently, vpnaas not support DVR topology, there is still so much work to be done. ;-( . How to share one bandwith? The way to make it work, is introduce a new tc wraper with new qos model, as we can easy to share the bandwidth with tc, right? I already introduce a new tc-wrapper in the draft patch. Also, I have to say that I'm disagree that we do the limit outside of openstack, as that doesn't sound like a cloud. ;-) ."
1787793,2018-08-26 19:56:55 UTC,"VPN QoS is going to be implemented by Zhaobo during Stein https://review.openstack.org/#/c/558986/. But beyond this fact, if I understand correctly, the essence of this RFE is sharing a QoS bandwidth limit per tenant. Let's say the tenant has two floating IPs. The questions is how these floating IPs can share a tenant level QoS bandwidth limit. Some thoughts:"
1787793,2018-08-23 22:28:03 UTC,Let's discuss in the QoS meeting next week as a first step
1787793,2018-08-20 08:05:18 UTC,"First of all, QoS for VPN traffic is not implemented yet so we can't ""share"" bandwidth between FIP and VPN traffic for now :)"
1787793,2018-09-14 15:59:48 UTC,"Now that we have a potential technical solution at the TC level, we will work on a spec that address other issues around this proposal, like API design, testing, etc"
1787793,2018-08-27 04:04:17 UTC,"AFAIK, the vpnaas are using the centralized router (namespace) to connect the ipsec VPN traffic.  How to share the bandwidth for distributed floating IP and centralized VPN? For neutron scope, I don't think the distributed floating IP traffic and the centralized VPN traffic can share one bandwith. Maybe it can be limit under a high level physical device, maybe the TOR, core switch or a physical firewall."
1787793,2018-09-14 16:04:05 UTC,"Another approach to solve this is the one proposed in these two patches: https://review.openstack.org/#/c/568526/ and https://review.openstack.org/#/c/424468. By handling QoS in the router gateway, the limits will be shared by the tenaant"
1787801,2018-08-20 05:39:35 UTC,"Ok, thanks for the tip I didn't know that. If this is then coming from upstream I guess a bug report is warranted there as well."
1787801,2018-08-21 19:20:01 UTC,"I believe that since you changed the location of the config file, changing the systemd service file is just a continuation of your local configuration. Simon's tip in comment #1 was spot on, as was your investigation of the config setting that needed changing."
1787801,2018-08-19 16:25:34 UTC,"Since upstream uses ProtectHome=true, I'd tend to think that having the config files in home directories is not that common even if it's certainly a valid use case. IMHO, this is a perfect case for using drop-in snippets:"
1787805,2018-10-24 20:33:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787814,2018-08-31 11:18:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787816,2018-09-29 13:52:45 UTC,"I have this identical issue.  I can't paste a file into a cifs share with Caja, and if I right click and choose ""Properties"" Caja crashes."
1787816,2018-09-29 13:52:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787816,2018-10-10 16:24:44 UTC,"Updated 18.04.1
Linux mate-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1787819,2018-08-19 17:41:45 UTC,UPDATE: Seems to have been due to a hold on the following modules:  nvidia-opencl-icd-304 nvidia-current nvidia-304 nvidia-304-dev nvidia-304-updates  nvidia-304-updates-dev libcuda1-304
1787820,2018-08-19 22:30:14 UTC,"At least it as confusing enough to file this bug ..
Can we print the effected name?"
1787820,2018-08-20 18:19:33 UTC,"I would advise rebuilding when you update your OS, yes. IIRC when I update Fedora Mixxx will not run until I rebuild it."
1787820,2018-08-20 14:51:18 UTC,"I'd agree more debug is needed, as I was totally stuck here with no idea how to continue."
1787820,2018-08-19 22:00:57 UTC,"No, this is not necessary. Leading/trailing whitespaces in the database are unexpected, but don't cause any issues as far as I know. Moreover at this point we don't have enough context information for generating meaningful error messages."
1787820,2018-08-20 15:07:23 UTC,"FWIW, I did find a crate with trailing whitespace, but it has been there for several weeks, so the crash may be 100% unrelated to the debug assert which you probably already assumed. I'm guessing since I run from source when I update my OS, I need to rebuild mixxx. Is this a correct assumption?"
1787820,2018-08-19 17:20:34 UTC,Your database seems to contain crate names with leading or trailing white spaces. Mixxx should prevent that entries with invalid names are created.
1787820,2018-08-19 16:11:01 UTC,"I have seen this same error in the past, and it was after I updated my OS (Arch Linux), and it required a rebuild of mixx from source.Why would/should an OS update break an app?"
1787820,2018-08-19 16:00:31 UTC,Here is the relevant portion of the same sequence with mixxx --developer:
1787820,2018-08-19 21:08:38 UTC,"Shouldn’t we give here a more explicit error message, that the user has the chance to fix this via a db tool? What do you think?"
1787822,2020-07-06 21:44:34 UTC,"Thank you Daniel, hopefully by sometime next month 20.04.1LTS will be released and I'll upgrade."
1787822,2018-08-22 00:28:24 UTC,I'd like to note that I went here - https://bitbucket.org/eloy_garcia_pca/wallpaperdownloader/issues/34/ubuntu-1804-object-metabackground and opened an issue on the current version of the WallpaperDownloader snap.
1787822,2020-07-06 02:10:31 UTC,It appears the fix is in Ubuntu 20.04 but not 18.04. So I will mark this to request a fix in 18.04.
1787822,2020-07-03 21:43:06 UTC,"Ref bug #1886110, I submitted this because after almost 2yrs this issue is still valid, at least on my Ubuntu 18.04LTS. I'm commenting here because I was asked to on my other report. According to comments made here - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/501, the last one by  Marco Trevisan a commit was made a year ago to fix this issue - https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/a9234f7631f2228184d027419cab1350666ffdc1 therefore I'm wondering why it's not been fixed, at least in my case."
1787822,2018-09-03 02:21:43 UTC,Will do Daniel.
1787822,2018-09-03 02:09:25 UTC,No the issue is not fixed yet. Please put any relevant comments in the upstream bug where the developers will see them:
1787822,2018-08-31 22:13:45 UTC,Additional note. When I maximize then minimize the WallPaperDownloader snap this is written to syslog
1787822,2018-08-23 22:27:54 UTC,I forgot to mention that I also did a system restart because of a new kernel install so gnome-shell was completely restarted.
1787822,2018-08-23 15:49:48 UTC,There was a large software update this morning including Gnome-Shell and others. Gnome-Shell was updated to
1787822,2018-08-22 02:11:05 UTC,"Thanks, but I don't think that bug report will help. You can probably close that one."
1787822,2018-08-21 12:00:53 UTC,"Yes, I run a Snap called 'Wallpaperdownloader' that besides downloading wallpapers will also cycle them within a set time limit. I stopped it running at 6:38 this morning and have yet to see the issue resurface."
1787822,2018-08-20 02:47:20 UTC,apport information
1787822,2018-08-21 02:24:11 UTC,"On Tue, 2018-08-21 at 01:55 +0000, Daniel van Vugt wrote:

> Thanks.
>
> Is anything obviously broken or are you just reporting the error
> message?
>
> ** Changed in: gnome-shell (Ubuntu)
>        Status: New => Incomplete
>


No, nothing is obviously broken, at least to me, but something isn't
right. However it's an annoyance to have my syslog filled up with these
being written every 10 minutes."
1787822,2018-08-21 01:55:12 UTC,Thanks.
1787822,2018-08-20 12:03:49 UTC,Completely removed the extensions in /usr/share/gnome-shell/extensions and restarted. Output still present:
1787822,2018-08-20 03:15:09 UTC,Please also try removing the other extensions. There's more than two:
1787822,2018-08-20 02:50:41 UTC,"I reinstalled two of the Gnome Extensions, Freon and Window List since removing all extensions had no effect."
1787822,2018-08-21 02:57:40 UTC,It appears I can reproduce the message by changing wallpapers.
1787822,2018-08-20 02:47:19 UTC,apport information
1787822,2018-08-20 02:47:17 UTC,apport information
1787822,2018-08-20 02:27:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1787825,2019-11-06 20:58:06 UTC,This is still an issue.  If new events are added you are unable to add a new member as a contact individual.  The same applies to an event that is taken over by a new member.  We are only permitted to choose an individual from the list (many of whom are no longer active) to be the contact individual.
1787825,2020-11-16 18:22:24 UTC,"This bug still exists.  As new members take over events, there names cannot be inserted and we are left with an old and in some cases very outdated name."
1787833,2019-05-05 13:24:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787838,2018-12-07 17:40:17 UTC,"Press two gears near the lens model. If you see two gears then ufraw will crush, if one - it will work."
1787845,2018-08-24 16:55:00 UTC,I can confirm this.  I had this exact same issue (with an intel HD530 card).  The fix mentioned above worked.
1787845,2018-08-24 18:22:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787845,2020-04-24 03:52:18 UTC,How can i solve this problem?
1787845,2020-04-24 08:24:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu."
1787846,2018-12-17 12:20:10 UTC,same my problem :
1787846,2020-09-16 10:13:09 UTC,"Does your storage configured as local storage or as cinder backend?
Do you try to boot from volume?
What is the backend of the instance directory (i.e. [DEFAULT]/instances_path) on your compute?"
1787846,2020-09-18 23:35:59 UTC,"Hello, i use cinder backend."
1787848,2019-12-10 19:59:06 UTC,Migrated to:  https://gitlab.com/inkscape/inbox/issues/1342
1787857,2019-08-02 14:22:31 UTC,Does your system use AMD CPU? Looks like it only happens to AMD systems.
1787857,2019-08-02 19:13:40 UTC,yes. Output from lscpu if that helps:
1787857,2019-08-03 07:56:48 UTC,So it's specific to AMD systems.
1787857,2019-08-03 09:04:37 UTC,"I just tested 5.0.0-23-lowlatency kernel with the mouse plugged into a USB3 port, and everything seems to be okay. So it does seem to be USB2 specific (I dont have any USB1 ports to test it on, sorry)"
1787857,2019-08-04 18:22:35 UTC,Can you please attach `lspci -nn` so I can see its vid:pid?
1787857,2019-08-05 07:39:46 UTC,"00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge [1022:9600]
00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0) [1022:9603]
00:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 3) [1022:9607]
00:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) [1022:9609]
00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390]
00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
00:12.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller [1002:4398]
00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
00:13.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller [1002:4398]
00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 3c)
00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c]
00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383]
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d]
00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge [1002:4384]
00:14.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 [1022:1600]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 [1022:1601]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 [1022:1602]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 [1022:1603]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 [1022:1604]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 [1022:1605]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation GP107GL High Definition Audio Controller [10de:0fb9] (rev a1)
02:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller [1b21:1142]
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)"
1787857,2019-08-05 09:40:44 UTC,"Ok, I can't see the issue on AMD Stoney Ridge EHCI, 1022:7908.
Can you please attach full dmesg when this issue happens?"
1787857,2019-08-02 12:57:04 UTC,"Okay. Just burned that to USB and booted from USB live image (didn't install).
Issue is still present :-("
1787857,2019-10-10 13:45:53 UTC,"I also found this issue recent days, my cpu is also AMD, but I can not solve the problem by put mouse in usb3 port, whatever usb3.0 or usb2.0 the issue happens."
1787857,2019-10-12 05:51:17 UTC,I encountered this recently under Ubuntu 16.04.5 with Linux 4.15.0-65-lowlatency with an AMD A8-3870k APU. In the most recent case the machine was fine for nearly a week until I was reading a large amount of data off a usb stick. By moving my mouse receiver to a USB 3.0 port I was able to make the mouse work normally again without having to reboot.
1787857,2019-11-03 18:04:37 UTC,"I'm seeing this as well with Ubuntu 19.10, uname -a:"
1787857,2019-11-21 17:36:15 UTC,"I also have this issue.
Plugging it in to a USB3 port solves the issue, but I don't want to waste my precious USB3 ports for a mouse."
1787857,2019-11-21 17:44:41 UTC,"Please let me know if you need anything else to investigate the issue.
It looks like my keyboard is also lagging. I have to type very slowly so the keys are not skipped.
Both are Logitech devices."
1787857,2020-01-13 20:28:26 UTC,"My PC had this issue. It was an Intel chip and a Logitech mouse, keyboard. Over Christmas, I upgraded my desktop. The issue has gone away now. I'm still using my Logitech keyboard and an Intel chip."
1787857,2019-08-02 10:44:53 UTC,It's already in Ubuntu Studio daily image.
1787857,2019-08-08 05:39:44 UTC,"OK, so I booted up with the mouse in USB3 port. All good.
Put mouse in USB2 port. Problem appears (as expected).
output from dmesg attached"
1787857,2019-08-02 08:02:01 UTC,"@kaihengfeng - How do I find and install that Kernel? Sorry, I'm used to just using the gui and command line tools to upgrade, not sure how I find and install that kernel manually. I am used to using apt for installing general packages, just this scenario is new to me and I can't find any instructions on google."
1787857,2019-02-22 13:55:51 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1787857,2019-07-24 16:23:57 UTC,"Note that this became 100% consistent. As in every time I booted I got the issue, rather than just most of the time.
Also, that it's now in release 5.0.0.20-lowlatency, 64 bit version."
1787857,2019-07-15 15:42:53 UTC,Subscribing kernel team.
1787857,2019-07-29 18:32:22 UTC,"I just tried Ubuntu Studio 19.10 which uses kernel 5.2.0-8-lowlatency, seems like the issue doesn't happen there."
1787857,2019-07-15 12:22:13 UTC,"I tried now with 'linux-generic' package (provides currently linux-image-5.0.0-20-generic). I did not  experience any mouse lag issues, upon any successful* boot. So in that sense this is 0/10 reproducible with 'generic' kernel variant."
1787857,2019-07-15 10:18:45 UTC,I just saw this right at boot. The mouse was lagging already at the login screen. And the login screen took around 10 seconds to show up after the first two lines of kernel boot messages. (Usually takes around 2 seconds).
1787857,2019-07-07 18:39:43 UTC,"In that case I'm keeping this as incomplete, especially since OP (ronso0) has failed to verify with suggestions given by kaihengfeng. I feel like there is some hardware commonality here, and would like to see some hardware specifics as previously requested to better triage this bug."
1787857,2019-07-07 16:57:45 UTC,"Actually, happened also with lowlatency-5.0.0-20 on a subsequent boot. But again, after one reboot this did not reproduce. So it is not 10/10 systematical."
1787857,2019-07-07 15:42:42 UTC,"Lassi, thanks for the comment. If that's the case, I'm going to go ahead and mark this bug as ""Invalid"" for rtirq and ""Fix Released"" for linux, but I'd love to see more comments first to confirm this."
1787857,2019-07-07 14:41:17 UTC,"I saw this issue with fresh install of Ubuntu Studio 19.04, lowlatency-5.0.0-13 kernel."
1787857,2019-06-27 05:08:00 UTC,Can you guys try -generic kernel? I wonder this bug is -lowlantency specific.
1787857,2019-06-24 15:16:22 UTC,I have the same issue.
1787857,2018-08-19 21:58:54 UTC,"Please post this in the forums at ubuntuforums.com or at askubuntu.com. Also, please check to see if this is happening with any of the other flavors, especially Xubuntu. For now, I have to mark this bug as incomplete since further information may be required, such as your specific hardware information.  Moreover, the bug has to be targeted at a specific package and not the Ubuntu flavor in general, so until there is further information this bug is incomplete."
1787857,2019-02-03 20:37:22 UTC,Also subscribing rtirq since this may be related.
1787857,2019-02-03 20:35:07 UTC,"Still need to know hardware specifics. I, for one, have AMD Graphics which exhibits this behavior without some AMD-specific kernel parameters in the command line in grub. Either way, subscribing the kernel package to this as well."
1787857,2019-02-03 09:27:22 UTC,"It does not do this on xubuntu 18.04, only Ubuntu Studio 18.04. After be logged, wait about ten seconds an you'll see the speed mouse changing."
1787857,2018-09-12 21:01:47 UTC,"It is an kernel issue.
I tested with all 4.15.* kernels available in the ubuntu repo, but only upgrading the kernel to 4.16.0-041600-lowlatency from [1] solved all issues."
1787859,2018-10-01 08:22:11 UTC,Will it be fixed?
1787867,2019-10-20 23:20:28 UTC,This is a serious security issue and it's fixed in Gnome upstream. Probably should be backported.
1787867,2018-09-13 12:42:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787867,2018-09-13 12:45:22 UTC,Can confirm this bug. After activating Bluetooth via Setting menu in Ubuntu 18.04.1 the computer stay in a permanent bluetooth discoverable mode and is connectable by external bluetooth devices until the next system reboot.
1787867,2018-11-09 20:27:21 UTC,Can confirm this bug as well. Bluetooth remains discoverable from other devices when Bluetooth is On. - Thinkpad X220
1787867,2019-01-02 09:19:32 UTC,I can't believe that such a basic security/privacy issue has not been fixed yet.
1787867,2019-01-02 09:26:44 UTC,"Probably, lot of clues there:"
1787867,2019-07-19 17:35:02 UTC,"Also,  not only is ""Discoverable"" left on,  ""Discovery"" is left on.  If someone goes to Bluetooth Settings, Discovery is turned on (started) and can only be turned off (stopped) by disconnecting BT adapter or reseting bluetooth.service.   This leads to hundreds of detected devices per minute in a public space or office building."
1787867,2019-10-06 17:50:55 UTC,I can confirm the behavior. At least its possible to deactivate 'discoverable' and 'discovery' on the command line:
1787867,2020-05-20 14:56:16 UTC,sudo hciconfig hci0 noscan will turn discovery off but leave bluetooth on.  I added the line to the /etc/rc.local file so that it will start at every reboot without the sudo.  So the line will read hciconfig hci0 noscan.  This is a temporary workaround until this is fixed.  This bug persists in 20.04.
1787867,2020-05-20 16:50:51 UTC,"Just checked in 20.04, with a connected Bluetooth device, and my system is no more automatically discoverable. It's discoverable only when the Bluetooth Settings panel is opened."
1787867,2020-06-09 20:58:35 UTC,I can confirm this bug still exists on 20.04 after testing my desktop and laptop.
1787867,2020-06-20 20:54:02 UTC,"Over time and several reboots later, the issue has reappeared, so the workaround above is definitely not a permanent solution."
1787867,2020-10-10 15:48:53 UTC,"Can confirm the bug still exists in 20.04.1 and just like Stephan T mentioned, the workaround only works for a few reboots, then goes back to visibility being on by default and becoming a security issue."
1787872,2020-06-05 05:28:03 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/733745"
1787872,2020-06-20 05:57:30 UTC,"Reviewed:  https://review.opendev.org/733745
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=316d826d88dc7a4565ee2add7c07d3304629960e
Submitter: Zuul
Branch:    master"
1787872,2020-06-09 23:06:20 UTC,"Hi Pavani,
Thank you very much for fixing the issue and attaching the screenshot.
It looks good now."
1787872,2020-06-09 11:35:20 UTC,"Hi Yuko Katabami, I can reproduce this bug and have solved it. I have provided screenshot of it in attachment, please check."
1787872,2019-05-22 00:14:25 UTC,This happens only when a browser window width is narrow. Changing the priority to low.
1787872,2019-05-21 19:34:55 UTC,"It seems to depend on a screen width. If the width of the browser window is not wide enough, this seems to happen."
1787872,2019-01-25 10:45:07 UTC,"Hi,
Thank you for following this up.
I saw your screenshot and looks good for English.
It is not truncated even with non-English locale? (e.g. Japanese)
-- I am sorry, I currently don't have any environment I can quickly check. It would be great if you could check it for me."
1787872,2019-01-25 06:59:51 UTC,"Hi Yuko Katabami,I can't reproduce this bug.This bug is fixed in current release as you can see in attachment. Can we mark it as invalid?"
1787872,2019-05-21 22:28:28 UTC,Thank you @amotoki.
1787873,2018-08-29 18:36:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787879,2018-08-21 09:18:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787879,2019-05-01 14:34:17 UTC,Same just happened to me on Ubuntu 18.10 after console-setup-linux was updated.
1787880,2020-03-09 15:49:39 UTC,"Is this still relevant? For now, I'll mark it as Incomplete based on the fact it was filled long time ago and it might be fixed already."
1787880,2020-05-09 04:17:27 UTC,[Expired for tempest because there has been no activity for 60 days.]
1787886,2018-08-28 14:38:15 UTC,"The php release upgrade is a bit odd indeed, or so I think. If you have the versioned packages installed only (like php7.0-curl without php-curl), then the release upgrade might not update those packages, and even remove some. One should always pay close attention to what the release upgrade tool is telling you when it gives a summary of the actions it is going to take."
1787886,2018-08-27 20:44:23 UTC,Logs are attached
1787886,2018-08-27 15:00:30 UTC,Are the log files from the upgrade available? If you used do-release-upgrade they'd be found in /var/log/dist-upgrade/.
1787886,2018-08-21 06:39:10 UTC,php7.x-curl is also missing and needs to be manually installed after the upgrade
1787886,2018-08-28 14:21:21 UTC,Resseting to new as logs were provided.
1787886,2018-08-20 08:21:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1787886,2018-08-20 06:36:08 UTC,Something else I just noticed. The first server (the one I manually installed the php packages needed for Apache2) is on PHP 7.0.30.
1787886,2018-08-20 14:57:14 UTC,"Before the upgrade I collected the following
-----------------------------------------------------------
llist@dc1:~$ sudo apache2ctl -M
[sudo] password for llist:
Loaded Modules:
 core_module (static)
 so_module (static)
 watchdog_module (static)
 http_module (static)
 log_config_module (static)
 logio_module (static)
 version_module (static)
 unixd_module (static)
 access_compat_module (shared)
 alias_module (shared)
 auth_basic_module (shared)
 authn_core_module (shared)
 authn_file_module (shared)
 authz_core_module (shared)
 authz_host_module (shared)
 authz_user_module (shared)
 autoindex_module (shared)
 deflate_module (shared)
 dir_module (shared)
 env_module (shared)
 filter_module (shared)
 headers_module (shared)
 mime_module (shared)
 mpm_prefork_module (shared)
 negotiation_module (shared)
 php7_module (shared)
 rewrite_module (shared)
 security2_module (shared)
 setenvif_module (shared)
 socache_shmcb_module (shared)
 ssl_module (shared)
 status_module (shared)
 unique_id_module (shared)
llist@dc1:~$ ls -lsa /etc/apache2/mods-enabled/
total 8
4 drwxr-xr-x 2 root root 4096 Jun  5 02:38 .
4 drwxr-xr-x 9 root root 4096 Jul 31 23:11 ..
0 lrwxrwxrwx 1 root root   36 Nov 17  2016 access_compat.load -> ../mods-available/access_compat.load
0 lrwxrwxrwx 1 root root   28 Nov 17  2016 alias.conf -> ../mods-available/alias.conf
0 lrwxrwxrwx 1 root root   28 Nov 17  2016 alias.load -> ../mods-available/alias.load
0 lrwxrwxrwx 1 root root   33 Nov 17  2016 auth_basic.load -> ../mods-available/auth_basic.load
0 lrwxrwxrwx 1 root root   33 Nov 17  2016 authn_core.load -> ../mods-available/authn_core.load
0 lrwxrwxrwx 1 root root   33 Nov 17  2016 authn_file.load -> ../mods-available/authn_file.load
0 lrwxrwxrwx 1 root root   33 Nov 17  2016 authz_core.load -> ../mods-available/authz_core.load
0 lrwxrwxrwx 1 root root   33 Nov 17  2016 authz_host.load -> ../mods-available/authz_host.load
0 lrwxrwxrwx 1 root root   33 Nov 17  2016 authz_user.load -> ../mods-available/authz_user.load
0 lrwxrwxrwx 1 root root   32 Nov 17  2016 autoindex.conf -> ../mods-available/autoindex.conf
0 lrwxrwxrwx 1 root root   32 Nov 17  2016 autoindex.load -> ../mods-available/autoindex.load
0 lrwxrwxrwx 1 root root   30 Nov 17  2016 deflate.conf -> ../mods-available/deflate.conf
0 lrwxrwxrwx 1 root root   30 Nov 17  2016 deflate.load -> ../mods-available/deflate.load
0 lrwxrwxrwx 1 root root   26 Nov 17  2016 dir.conf -> ../mods-available/dir.conf
0 lrwxrwxrwx 1 root root   26 Nov 17  2016 dir.load -> ../mods-available/dir.load
0 lrwxrwxrwx 1 root root   26 Nov 17  2016 env.load -> ../mods-available/env.load
0 lrwxrwxrwx 1 root root   29 Nov 17  2016 filter.load -> ../mods-available/filter.load
0 lrwxrwxrwx 1 root root   30 Jun  5 02:38 headers.load -> ../mods-available/headers.load
0 lrwxrwxrwx 1 root root   27 Nov 17  2016 mime.conf -> ../mods-available/mime.conf
0 lrwxrwxrwx 1 root root   27 Nov 17  2016 mime.load -> ../mods-available/mime.load
0 lrwxrwxrwx 1 root root   34 Nov 17  2016 mpm_prefork.conf -> ../mods-available/mpm_prefork.conf
0 lrwxrwxrwx 1 root root   34 Nov 17  2016 mpm_prefork.load -> ../mods-available/mpm_prefork.load
0 lrwxrwxrwx 1 root root   34..."
1787894,2020-03-19 13:05:26 UTC,Closing because INVALID: Support request.
1787901,2018-10-29 17:58:53 UTC,Happens shortly after login.
1787901,2018-10-10 18:10:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787901,2018-08-20 08:35:28 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fc9cecb62fa ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7fc9cecb441a ""corrupted double-linked list"") at malloc.c:5350
 _int_malloc (av=av@entry=0x7fc9cecebc40 <main_arena>, bytes=bytes@entry=4152) at malloc.c:3926
 __libc_calloc (n=n@entry=1, elem_size=elem_size@entry=4152) at malloc.c:3436
 g_malloc0 (n_bytes=4152) at ../../../../glib/gmem.c:129"
1787903,2019-03-19 10:39:18 UTC,We probably want to rely on xdg-desktop-portal for this.
1787906,2019-03-15 06:39:41 UTC,"------- Comment From <email address hidden> 2019-03-15 02:31 EDT-------
Any updates on this?"
1787906,2018-08-20 09:08:57 UTC,"This bug has been mirrored as a Power issue, but the architecture in the bug report appears to show the issue has occurred on ""x86_64""."
1787906,2018-08-20 09:29:18 UTC,"------- Comment From <email address hidden> 2018-08-20 05:29 EDT-------
(In reply to comment #4)

> This bug has been mirrored as a Power issue, but the architecture in the bug
> report appears to show the issue has occurred on ""x86_64"".
>
> Could you clarify the hardware and architecture where this issue was seen?
"
1787906,2018-09-19 07:09:26 UTC,"------- Comment From <email address hidden> 2018-09-19 03:05 EDT-------
Any update on this"
1787906,2020-06-18 09:10:08 UTC,"------- Comment From <email address hidden> 2020-06-18 05:00 EDT-------
Hello Canonical,"
1787910,2018-08-28 12:47:43 UTC,"Reviewed:  https://review.openstack.org/596502
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=243ba8513097ca715af738422a9e1249c6a7a1f0
Submitter: Zuul
Branch:    master"
1787910,2018-08-30 13:32:17 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/598167"
1787910,2018-09-06 08:55:41 UTC,"FWIW i hit this issue locally, haven't been able to work around it yet. Yatin's patch is present in my environment, yet nova-placement still prints this:"
1787910,2018-09-06 11:36:20 UTC,"Reviewed:  https://review.openstack.org/598167
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=49916c09216479a8dd54e55b4c6e86dae8246fa3
Submitter: Zuul
Branch:    stable/rocky"
1787910,2018-10-09 09:19:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/608894"
1787910,2018-10-11 15:55:26 UTC,"Reviewed:  https://review.openstack.org/608894
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=0ec9a3db94a6a0e09387f7d86860d93708c524db
Submitter: Zuul
Branch:    master"
1787910,2018-10-17 10:26:04 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611286"
1787910,2018-10-22 13:03:31 UTC,Backporting the tripleo change as far as pike as that's where the nova defaults dropped these filters.
1787910,2018-10-23 17:39:13 UTC,Adding a note here because I was looking to understand why we didn't catch the ResourceProviderSyncFailed bug [1] where we weren't sending the needed microversion 1.26 in update_from_provider_tree.
1787910,2018-11-18 07:42:33 UTC,"Reviewed:  https://review.openstack.org/611286
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=1d736b7e675176fa7170f82e0545ff156fea6f76
Submitter: Zuul
Branch:    stable/rocky"
1787910,2018-12-18 18:24:18 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/625983"
1787910,2018-12-31 18:29:14 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.openstack.org/596610"
1787910,2019-03-22 03:48:33 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1787910,2019-05-20 06:05:17 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/660023"
1787910,2019-05-20 16:21:10 UTC,"Reviewed:  https://review.opendev.org/660023
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=306412539a92c03ac06c0bad38d6d14f2ea2f4f3
Submitter: Zuul
Branch:    stable/queens"
1787910,2019-06-11 08:31:13 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/664524"
1787910,2019-06-11 18:17:31 UTC,"Reviewed:  https://review.opendev.org/664524
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=89b09d3ed18f07f571b58d6a8049f08c9216e12e
Submitter: Zuul
Branch:    stable/queens"
1787910,2020-08-06 21:54:43 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/625983
Reason: This review is > 180 days without comment and WIP -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewers. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1787910,2018-08-26 16:52:59 UTC,https://review.openstack.org/596610 <--- is required to run the ovb ooo reproduce tooling.
1787910,2018-08-26 16:52:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/596610"
1787910,2018-08-28 17:51:39 UTC,"Reviewed:  https://review.openstack.org/596093
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=04b235652b44701b8703f63aee10fac6fad13ced
Submitter: Zuul
Branch:    master"
1787910,2018-08-24 22:28:21 UTC,So tl;dr https://review.openstack.org/#/c/565841 meant that ironic compute nodes no longer report vcpu/ram/disk to the scheduler so the core/ram/disk filters thought the node (via the HostState object) didn't have any inventory and filtered out that host. We definitely need to update the documentation on the nova core/ram/disk filters to mention they are no longer needed when using the filter_scheduler driver.
1787910,2018-08-20 11:37:21 UTC,"the only place i can find reference of CUSTOM_BAREMETAL is in this [1] undercloud post config bash which is called for the heat deployed undercloud. However its the overcloud deploy which fails with ""ResourceInError: resources.Controller: Went to status ERROR due to ""Message: No valid host was found. There are not enough hosts available., Code: 500"" like [2] (and same for all the node types as you can see in [2])."
1787910,2018-08-20 13:02:16 UTC,"For the record: the same problem broke ironic-inspector CI upstream. Rocky does not seem affected, nor does ironic itself."
1787910,2018-08-20 13:23:23 UTC,it seems that this call needs to be updated to use microversion 1.26 as well https://github.com/openstack/nova/blob/7e09641f849c323fd38006451256690ed66de80d/nova/scheduler/client/report.py#L1098
1787910,2018-08-20 14:02:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/593628"
1787910,2018-08-24 23:28:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/596502"
1787910,2018-08-20 15:52:53 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/593678"
1787910,2018-08-20 19:44:14 UTC,"Reviewed:  https://review.openstack.org/593628
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=55fb7efe3110e26a993be291cd2cfac1df8c4679
Submitter: Zuul
Branch:    master"
1787910,2018-08-20 23:53:24 UTC,"Reviewed:  https://review.openstack.org/593678
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aebb29ed710fb4b5b92a6efa99f1d3dbdcc48a0c
Submitter: Zuul
Branch:    stable/rocky"
1787910,2018-08-21 11:59:56 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc2 release candidate.
1787910,2018-08-20 15:22:12 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Invalid%20inventory%20for%20'CUSTOM_BAREMETAL'%20on%20resource%20provider%5C%22%20AND%20message%3A%5C%22The%20reserved%20value%20is%20greater%20than%20or%20equal%20to%20total%5C%22%20AND%20build_status%3A%5C%22FAILURE%5C%22%20AND%20voting%3A1&from=7d
1787910,2018-08-22 09:51:20 UTC,"o/ yatin I suspect it is because we don't have the fix in the job yet... looking at one of the ones you posted, nova is like:"
1787910,2018-08-22 09:53:51 UTC,"forgot to add ykarel you're right both of the logs you pointed at in comment #10 above have the bug still... quick thing to check (incase useful for anyone else looking here) is the overcloud deploy logs [1][2] with the ""no valid hosts was found"""
1787910,2018-08-23 12:18:46 UTC,"So checked further and found https://review.openstack.org/#/c/565841 to be possible cause. Just to confirm this i hacked nova/virt/ironic/driver a little and overcloud deployment completed.
So i can say that either this patch missed something, or it needs to be fixed at some place(resource_classes are not used correctly as the commit message says)."
1787910,2018-08-23 12:35:55 UTC,Seems like the flavors in these jobs still require some amount of RAM - they should only require the resource class.
1787910,2018-08-23 13:01:34 UTC,The flavor override code in nova is here:
1787910,2018-08-23 15:10:41 UTC,"So we have flavor created with properties:- properties                 | capabilities:boot_option='local', capabilities:profile='control', resources:CUSTOM_BAREMETAL='1', resources:DISK_GB='0', resources:MEMORY_MB='0', resources:VCPU='0' which is correct, jroll confirmed it."
1787910,2018-08-21 14:20:42 UTC,"Still i can see the ovb jobs failing with No Valid Host Found, thought there are different errors."
1787910,2018-08-23 20:59:16 UTC,folks..  tripleo promotion jobs use the latest merged code from non-tripleo projects that have been promoted from current ->  consistent .
1787910,2018-08-24 06:12:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/596093"
1787911,2018-08-20 13:55:23 UTC,I tried to reproduce on a hetzner cloud 18.04 instance and landscape-client detected virt as expected.
1787912,2018-12-17 15:45:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625632"
1787912,2019-07-05 09:25:27 UTC,"Reviewed:  https://review.opendev.org/617118
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=d3ecde97750eb0dd8c231702fc44a1038e4d5a15
Submitter: Zuul
Branch:    master"
1787912,2019-06-28 09:47:15 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.opendev.org/645351"
1787912,2019-04-03 13:01:14 UTC,"Reviewed:  https://review.openstack.org/645166
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=b8c93b903eef4732e60627c018c70a4c7393977c
Submitter: Zuul
Branch:    master"
1787912,2020-01-22 10:52:52 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.opendev.org/595576"
1787912,2019-03-15 15:48:25 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/599594
Reason: failed to quorum"
1787912,2019-01-24 14:48:32 UTC,"Reviewed:  https://review.openstack.org/625632
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=74e8e614f6c3e51bdf0351db99083db7eda61b49
Submitter: Zuul
Branch:    master"
1787912,2019-01-04 02:42:42 UTC,"Reviewed:  https://review.openstack.org/600403
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=55f3bfecac5e480a20bbdd48b462f6de1ca9466e
Submitter: Zuul
Branch:    master"
1787912,2018-12-27 14:02:52 UTC,"Reviewed:  https://review.openstack.org/625621
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=0c532f715b2a25f072bfa308709fdb784873500e
Submitter: Zuul
Branch:    master"
1787912,2020-01-12 17:10:37 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.opendev.org/600039"
1787912,2018-12-17 15:23:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625621"
1787912,2019-03-21 21:06:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645351"
1787912,2018-12-06 12:20:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623199"
1787912,2018-08-23 10:33:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/595576"
1787912,2018-09-05 13:10:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/600039"
1787912,2018-09-06 10:15:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/600403"
1787912,2018-09-06 13:17:01 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/590748
Reason: Abandoning since I added these variables to tripleoci repository and at least on Jenkins they work well."
1787912,2018-12-10 19:01:32 UTC,"Reviewed:  https://review.openstack.org/623199
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=9c196b00391e5ed5fb0d85913433efc1a2b010c3
Submitter: Zuul
Branch:    master"
1787912,2018-10-01 10:16:47 UTC,"Reviewed:  https://review.openstack.org/599358
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=4bd7ad3187a11f46cf1c80966e6a9a3408fd866c
Submitter: Zuul
Branch:    master"
1787912,2018-11-10 14:40:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617118"
1787912,2018-11-12 17:05:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617363"
1787912,2018-11-15 04:49:15 UTC,"Reviewed:  https://review.openstack.org/617363
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=cc9d7247b62d291a209746859c785408146e0445
Submitter: Zuul
Branch:    master"
1787912,2018-09-25 12:51:31 UTC,"Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master
Review: https://review.openstack.org/599358
Reason: Purging the gate to free up resources and address the timeout issues"
1787926,2018-10-11 03:46:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787934,2018-08-20 11:25:48 UTC,"Curiously, if I view the image via display(1) command of ImageMagick or via the eog viewer used by GNOME file manager, then it displays with the checked background. But if I view it via file:/// protocol in Chrome, then the background shown is correct."
1787934,2018-08-20 11:16:01 UTC,"I forgot to mention that this is on Ubuntu 18.04, kernel 4.15.0-32 and all packages up to date."
1787943,2018-10-25 16:06:44 UTC,This issue was fixed in the openstack/horizon 15.0.0.0b1 development milestone.
1787943,2018-10-17 16:28:30 UTC,So...think about this:
1787943,2018-09-06 00:16:32 UTC,"Reviewed:  https://review.openstack.org/593650
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=16c4f4c3a294040bb87386156dab49f2b782ce21
Submitter: Zuul
Branch:    master"
1787943,2018-10-17 17:44:07 UTC,"There are public endpoints, and those can be exposed, and there are private endpoints, and those should not."
1787943,2018-08-20 12:34:30 UTC,"The code responsible for this is here:
https://github.com/openstack/django_openstack_auth/blob/stable/ocata/openstack_auth/views.py#L108-L109"
1787943,2018-08-20 12:35:43 UTC,Also https://github.com/openstack/horizon/blob/master/openstack_auth/views.py#L125-L126
1787948,2019-09-05 21:35:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787948,2019-09-05 21:42:44 UTC,"I hit this in testing using vagrant to spin up virtual machines.  I start with the vagrant box bento/ubuntu-18.04 from app.vagrantup.com/boxes.  After I install environment-modules, I can't list any modules because of the above problem.  It works after I explicitly install the tcl package."
1787948,2020-05-18 09:39:54 UTC,This bug seems to be fixed in Debian Bullseye (environment-modules >= 4.5.0-1)
1787955,2018-08-20 13:42:54 UTC,"$ gnome-software --verbose
(gnome-software:2341): Gs-DEBUG: compatible-project: GNOME
(gnome-software:2341): Gs-DEBUG: compatible-project: KDE
(gnome-software:2341): Gs-DEBUG: compatible-project: XFCE
(gnome-software:2341): As-DEBUG: run GsPlugin::setup
(gnome-software:2341): Gs-DEBUG: searching for plugins in /usr/lib/gs-plugins-9
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_appstream.so: appstream
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_dpkg.so: dpkg
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_ubuntu-reviews.so: ubuntu-reviews
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_hardcoded-featured.so: hardcoded-featured
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_epiphany.so: epiphany
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_menu-spec-categories.so: menu-spec-categories
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_provenance.so: provenance
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_snap.so: snap
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_dummy.so: dummy
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_menu-spec-refine.so: menu-spec-refine
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_apt.so: apt
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_icons.so: icons
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_hardcoded-blacklist.so: hardcoded-blacklist
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_fwupd.so: fwupd
(gnome-software:2341): Gs-DEBUG: opened plugin /usr/lib/gs-plugins-9/libgs_plugin_moduleset.so: moduleset
(gnome-software:2341): Gs-DEBUG: appstream [0.0] to be ordered after menu-spec-categories [0.0] so promoting to [1.0]
(gnome-software:2341): Gs-DEBUG: ubuntu-reviews [0.0] to be ordered after appstream [1.0] so promoting to [2.0]
(gnome-software:2341): Gs-DEBUG: epiphany [0.0] to be ordered after appstream [1.0] so promoting to [2.0]
(gnome-software:2341): Gs-DEBUG: provenance [0.0] to be ordered after apt [0.0] so promoting to [1.0]
(gnome-software:2341): Gs-DEBUG: cannot find plugin 'packagekit-refine'
(gnome-software:2341): Gs-DEBUG: snap [0.0] to be ordered after appstream [1.0] so promoting to [2.0]
(gnome-software:2341): Gs-DEBUG: cannot find plugin 'packagekit-refine'
(gnome-software:2341): Gs-DEBUG: menu-spec-refine [0.0] to be ordered after appstream [1.0] so promoting to [2.0]
(gnome-software:2341): Gs-DEBUG: cannot find plugin 'packagekit-refine'
(gnome-software:2341): Gs-DEBUG: apt [0.0] to be ordered after appstream [1.0] so promoting to [2.0]
(gnome-software:2341): Gs-DEBUG: provenance [1.0] to be ordered after apt [2.0] so promoting to [3.0]
(gnome-software:2341): Gs-DEBUG: cannot find plugin 'packagekit-refine'
(gnome-software:2341): Gs-DEBUG: icons [0.0] to be ordered after appstream [1.0] so promoting to [2.0]
..."
1787956,2019-04-08 11:56:59 UTC,Related upstream bug: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/12
1787956,2019-03-21 10:01:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787960,2019-09-19 12:06:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1787967,2018-11-14 13:40:21 UTC,To reproduce run (ensure strace-static is not installed):
1787968,2018-08-20 14:53:17 UTC,"Thinking especially about things like kits, equipment, and local history rarities with this recommendation since they're unlikely to ever be available on Open Library or as part of a 3rd party enhancement (NoveList, Chilifresh, Content Cafe, etc.).  And for systems that rely exclusively on Open Library, the ability to add covers for media (dvds, music cds, audiobooks, etc.) would also be appreciated."
1787968,2020-07-06 19:45:51 UTC,"I wonder if, with the advent of the staff catalog, now would be the perfect time to pursue this addition.  The modal behavior in OL seems fairly straight forward."
1787969,2019-07-05 10:00:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787970,2018-08-20 15:06:54 UTC,Searching the web finds a few hits:
1787974,2019-04-05 10:44:35 UTC,Note that the feature is included by default since 18.10
1787974,2018-08-20 15:42:45 UTC,"Installing the package ""fprintd"" solves the issue."
1787974,2019-04-05 09:16:22 UTC,"to correct myself, the required package is libpam-fprintd"
1787974,2019-07-14 17:12:25 UTC,"i tried on Ubuntu 18.04.2 > ""sudo apt install -y fprintd libpam-fprintd"" and ""sudo pam-auth-update"" on my ThinkPad T400 (a bit old laptop) device info: Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810  but it doesnt work. in Users>Settings when i try to enable and choose finger to enroll it gets freeze and causes fingerprint reader get extremely hot. i had to quit the setting when it happened and remove ""fprintd"" and ""libpam-fprintd"""
1787974,2019-07-14 17:14:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787974,2019-07-14 17:16:25 UTC,"just to clarify i tested on ThinkPad T400, and fingerprint reader device ID: Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810"
1787974,2019-07-14 17:43:16 UTC,Note that the URL
1787977,2019-03-22 03:48:10 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1787977,2018-08-20 16:26:45 UTC,"The only argument against backporting is that we identified this as a potential situation at PTG in Denver (the first one), and said we would deal with it if/when it came up. At the time we had the most information from CERN, which is mostly immune to this situation."
1787977,2018-08-25 17:54:05 UTC,"Reviewed:  https://review.openstack.org/592698
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0a88916911e2b02055a2a707bda026c975f4472c
Submitter: Zuul
Branch:    master"
1787977,2018-08-28 04:55:25 UTC,"Reviewed:  https://review.openstack.org/593131
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c3a77f80b1863e114109af9c32ea01b205c1a735
Submitter: Zuul
Branch:    master"
1787983,2018-08-24 03:25:13 UTC,"3.13.0-157.207~precise1 - generic
Regression test CMPL, RTB."
1787983,2018-08-27 07:31:57 UTC,The package has been published and the bug is being set to Fix Released
1787985,2018-08-30 09:31:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787989,2020-05-08 16:34:11 UTC,"hi all,
I finally manage to get all icons on kphotoalbum on xfce.
there's 2 solutions and i don't know which one is the good one."
1787989,2020-05-05 20:27:45 UTC,"I'm definitly lost and not able to find a correect configuration of thene in order to have all icons in kde apps on xfce...
Anyone...any idea ?"
1787989,2020-05-05 20:25:53 UTC,The following 2 pictures show kphotoalbum with fusion ou breeze theme choosed by qt5ct
1787989,2020-04-22 17:27:30 UTC,Should the capitalization of Adwaita not also be fixed for Ubuntu 18.04 (bionic) in package xubuntu-icon-theme file /usr/share/icons/elementary-xfce/index.theme which still says
1787989,2019-03-31 21:07:25 UTC,This bug was fixed in the package elementary-xfce - 0.13.1-1ubuntu1
1787989,2019-02-02 19:01:32 UTC,This was fixed upstream.
1787989,2019-02-02 17:28:27 UTC,"I agree, that the issue is about small ""a"" and capital ""A"". This fixes the problem for me:

>sudo ln -s /usr/share/icons/Adwaita /usr/share/icons/adwaita
"
1787989,2020-05-05 20:13:13 UTC,"I'm still looking for the right solution.
It seams that playing with this"
1787989,2018-11-30 19:47:39 UTC,"Hi all,
I finally found a part of the problem.
In the file /usr/share/icons/elementary-xfce/index.theme
There's the line :
Inherits=adwaita,gnome,hicolor"
1787989,2018-11-30 20:37:15 UTC,"If the Inherits line in index.theme is changed to
Inherits=Adwaita,gnome,hicolor,breeze"
1787989,2018-08-24 12:36:25 UTC,"Likewise, I get"
1787989,2018-08-24 16:19:33 UTC,"yep, i'm sure it's not application related but something wrong in xubuntu. that's why i originally set it to Ubuntu... But Paul change it."
1787989,2018-09-07 14:10:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1787989,2020-04-22 19:21:20 UTC,Yes it is required on 18.04 but the better way should be to change the adwaita package so that it is lowercase like all other font package.
1787989,2018-10-31 17:02:33 UTC,It's not only `kphotoalbum` and `okular`. It's all KDE apps in XFCE that suffer the problem.
1787989,2018-10-31 21:19:50 UTC,"Change to adwaita-icon-theme because it affect all KDE apps on latest LTS xubuntu.
Please provide help"
1787993,2018-08-20 17:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1787993,2018-09-14 17:03:13 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1787993,2018-09-17 15:52:46 UTC,-- SRU verification --
1787993,2018-09-17 16:25:14 UTC,"-- SRU Verification --
Enabled SSBD v4 in firmware and booted the -proposed kernel, no regressions were found on boot."
1787993,2018-10-01 17:15:35 UTC,This bug was fixed in the package linux - 4.15.0-36.39
1787993,2018-08-22 13:46:48 UTC,"Tyler Hicks pointed out that Cortex-A57, Cortex-A72, Cortex-A73, and Cortex-A75 all just receive
firmware updates that disabled memory disambiguation at boot time to mitigate SSB. The following page indicates that the patches are only relevant for Cortex-A76. https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability"
1788004,2018-09-10 18:40:43 UTC,"Based on inspecting the ZFS source code, this looks like a ZFS inode where there is a mismatch between the claimed size of the inode's (ZFS) ACL and how it's stored. If you're willing to do some work, it might be possible to narrow this down to identify a specific inode and what's wrong with it, which could help fixing this (in Ubuntu and upstream). Unfortunately this will be a somewhat involved process involving zdb, because you need to dump on-disk structures. If you're interested and willing to tackle this, your best approach is probably to ask for help on the ZFS on Linux mailing list, because it will be easier to give the details there."
1788004,2018-09-12 13:21:59 UTC,Thanks for taking a look at this Chris.  I've started a thread on the ZoL mailing list here:
1788004,2018-09-15 17:38:40 UTC,"ZoL bug has also been opened for this with more information:
https://github.com/zfsonlinux/zfs/issues/7910"
1788004,2020-09-02 15:33:01 UTC,This looks like the upstream bug report has been closed because it is stale from no more activity. I'm going to close this bug. If it requires more attention please feel free to re-open this issue.
1788005,2019-01-16 22:05:14 UTC,"Thanks, that has been now reported upstream on https://gitlab.gnome.org/GNOME/rhythmbox/issues/1688"
1788012,2018-11-07 19:35:23 UTC,"In the case of ovs, Neutron show the bridge in vif details:"
1788012,2018-08-20 18:38:43 UTC,not that if i create the a br-int linux bridge on the destination the migration succeeds but the vm has no network connectivity because the tap is connected to the br-int bridge not the linux bridge associated with the neutron network. so if the correct bridge name was used live migration would would.
1788012,2018-08-26 19:37:30 UTC,"To clarify, the error happened in nova side."
1788014,2020-02-06 12:40:31 UTC,This issue was fixed in the openstack/nova 20.1.0 release.
1788014,2020-03-04 13:39:52 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/711233"
1788014,2020-02-06 12:45:04 UTC,This issue was fixed in the openstack/nova 19.1.0 release.
1788014,2020-01-22 18:14:19 UTC,"Reviewed:  https://review.opendev.org/700774
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6310e693039cc3b6d2808915a3b4daf7bbffb9a8
Submitter: Zuul
Branch:    stable/stein"
1788014,2019-12-30 14:35:59 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/700774"
1788014,2019-12-29 20:02:49 UTC,"Reviewed:  https://review.opendev.org/695900
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=27bfd0bc6233c25114504bb363402807752a7ece
Submitter: Zuul
Branch:    stable/train"
1788014,2019-11-23 15:55:39 UTC,"Reviewed:  https://review.opendev.org/594527
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aa87b9c288d316b85079e681e0df24354ec1912c
Submitter: Zuul
Branch:    master"
1788014,2019-11-21 16:46:02 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/594139
Reason: Let's just assume that https://review.opendev.org/#/c/594527/ fixes the bug since if we fix the root cause then we don't need to hack around cleaning up the busted port bindings."
1788014,2019-11-25 13:40:23 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/695900"
1788014,2019-11-05 16:38:12 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/693045"
1788014,2018-10-24 23:54:34 UTC,Here's a link to the partial fix that merged on 2018-08-23:
1788014,2018-08-21 19:36:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/594527"
1788014,2018-08-21 16:01:47 UTC,The fix I proposed initially is the wrong one.
1788014,2018-08-21 11:53:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/594139"
1788014,2018-08-21 10:11:50 UTC,"Do you see ""Binding ports to destination host"" in the logs on the source host when this failure occurs? That would happen when we enter post-copy mode and activate the destination host port bindings."
1788014,2018-08-21 09:57:49 UTC,What clears out the vif binding host_id and vif_type during the live migration? I would expect those to always be set. Is it something to do with rolling back (deleting) the destination host port binding but not activating the source host port binding?
1788014,2019-11-20 12:46:46 UTC,"Change abandoned by Artom Lifshitz (<email address hidden>) on branch: master
Review: https://review.opendev.org/693045
Reason: Doesn't seem to be a way to make this work..."
1788018,2018-08-21 06:00:07 UTC,This change was made by a bot.
1788018,2018-09-13 05:50:19 UTC,I also observed in my Dell laptop similar to Szymon that it relates to Touchpad.
1788018,2018-08-27 18:22:30 UTC,the bug started at upstream kernel commit 1455cf8dbfd06aa7651dcfccbadb7a093944ca65
1788018,2018-08-23 15:22:32 UTC,"I use ubuntu 18.04 with 4.15 kernel
I have hit the same problem, but with synaptics touchpad."
1788018,2018-08-21 06:17:23 UTC,I got a workaround by removing /lib/udev/rules.d/97-hid2hci.rules as was mentioned in a comment at https://askubuntu.com/questions/1028883/ubuntu-18-04-systemd-udevd-uses-high-cpu-conflict-with-wifi
1788018,2018-06-14 00:33:52 UTC,"Created attachment 276537
revert-bind_unbind-uevents.patch"
1788018,2018-10-18 17:53:33 UTC,(In reply to Y S Gupta from comment #8)
1788018,2018-06-13 16:50:40 UTC,As per https://patchwork.kernel.org/patch/10384111/ editing 97-hid2hci.rules as follows works around the new uevents added to the kernel in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
1788018,2018-05-20 07:57:41 UTC,"I observed the high cpu usage after upgrading from udev-233 to udev-236/udev-238 on Gentoo Linux. Downgrading back to udev-233 lets me use newer kernels (currently running 4.15.18) without any problems.
Using DELL Latitude E6400 from 2009, with same Broadcom Bluetooth module as mentioned above."
1788018,2018-05-09 23:02:06 UTC,"Bus 001 Device 009: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c:0000 Broadcom Corp."
1788018,2018-05-04 05:57:10 UTC,"I have the very same problem using the same distro (Ubuntu 18.04, 64-bit) on Dell Latitude E5400 laptop. Disabling BT from BIOS or removing the aforementioned rule solves the problem but leaves BT unusable."
1788018,2018-03-06 21:09:45 UTC,"Created attachment 274593
dmesg"
1788018,2018-06-14 00:32:13 UTC,"Scratch that last comment, on further testing found I was booted into incorrect kernel :/"
1788018,2018-12-22 17:54:47 UTC,"Command from Y S Gupta fixed to high cpu load for me.
As this is just a workaround. I suppose this bug should remain open.
Thanks for this, i can now reuse my bluetooth card."
1788018,2019-01-08 18:42:34 UTC,"When I boot up every day without exception, my machine starts up with one of the CPU cores running at 100%. I see lots of posts on other forums (Unbuntu  etc) going back over a year or more blaming touchpads or nvidia or WiFi. Some even say they can't use their thumb drive if it isn't plugged in when they boot. The problem also mimics a defective thumb drive where you plug it in and Ubuntu doesn't see it (because systemd-udevd doesn't have the cycles to process the newly plugged in USB device). Losing one core makes my machine slower but not too noticeably so. I do see much longer boot times and sometime it will hang entirely during boot. I assume a single core or dual core machine will be drastically slowed down or even unusable. When I search I find other non-ubuntu os's complaining about similar problems."
1788018,2019-01-08 19:38:50 UTC,"BTW, add to my previous comment an additional symptom:  sometimes my system will ""appear to hang"" entirely during boot (but it will power down normally by briefly touching the power off button when it ""looks like"" it is stuck)."
1788018,2019-02-05 20:16:54 UTC,"Marko Muehlberg (markom2), would you be able to confirm the commit from https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65 is the root cause for your issue by testing a revert of it following https://wiki.ubuntu.com/Kernel/KernelBisection ?"
1788018,2019-04-13 14:02:46 UTC,"I have the same problem, that John related."
1788018,2019-04-13 17:23:25 UTC,An update: The problem I reported in January went away on its own after a few weeks of having the problem every single day when I booted each morning. I was installing Ubuntu software updates when they became available during that time. There is something going on during boot that causes this problem.
1788018,2019-04-13 17:34:37 UTC,I fix the problem with this approach:
1788018,2019-04-13 18:30:30 UTC,These nerd-level suggestions all work but the root cause (the real problem) is not solved and will pop up again. How is the non-nerd supposed to do this? ...would you want your neighbor editing your system files????  Someone needs to fix this permanently!
1788018,2019-04-13 23:27:55 UTC,"I agree with you, its not the best solution. This bug impact many users! At next release of this softwares this bug has to be fixed."
1788018,2019-04-14 14:22:24 UTC,"This problem has been around for a long time and a lot of people have struggled with it. You can find examples such as the following on quite a few help sites, for example"
1788021,2018-10-01 16:00:27 UTC,"Same problem on an Asus UX331U. In Ubuntu 18.04 setting kbd backlight worked, it's broken in Ubuntu 18.10."
1788021,2018-11-13 22:29:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788021,2018-11-14 06:35:05 UTC,"Using Mainline Kernel 4.19.0 or above, it works. So it's a bug in the Ubuntu 18.10 Kernel Version."
1788023,2018-08-27 18:54:45 UTC,"As I mentioned in comment #1, if l2 population is enable, tunnels should be setup correctly across linuxbridge and OVS so we won't have this bug."
1788023,2018-08-27 02:41:20 UTC,"Hi @sean mooney,"
1788024,2019-04-17 06:04:39 UTC,"Hello,
do you still have this issue with the latest 4.15 HWE kernel on Xenial?"
1788024,2019-06-17 04:17:24 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1788028,2019-06-13 23:39:13 UTC,set status to traige and importance to low.
1788030,2018-08-21 02:10:44 UTC,Does the situation change at all when choosing to log in to 'Ubuntu on Wayland' or 'Ubuntu'?
1788030,2018-08-28 15:10:25 UTC,"I tried wayland and the session just failed and went right back to the low resolution login screen, which is Xorg.  I tried wayland a second time and just get a permanent busy cursor."
1788035,2018-10-17 18:26:38 UTC,We did not have a series of steps to reproduce this. Just left a server running without much happening and boom.
1788035,2019-10-03 07:34:27 UTC,"Fix can be found in Eoan, mark this as fix-released."
1788035,2019-01-23 11:10:47 UTC,"Some updates here: the patch was released in the -proposed pocket, and is available in the kernel 4.4.0-1075-aws - to enable the proposed repository please see this https://wiki.ubuntu.com/Testing/EnableProposed. The plan is to have this kernel released in the first week of February, after all tests/validations finish in the proposed package."
1788035,2018-12-04 21:15:25 UTC,"I'm investigating this issue, and built a kernel with the following two patches:"
1788035,2018-10-31 22:28:34 UTC,"We encountered an instance that had a nvme failure very early on in boot today. I've updated our internal Canonical case as well as our Amazon case on this, but posting relevant details here as well for consistency:"
1788035,2018-10-24 19:22:15 UTC,As this issue seems far from being solved and I dont see any progess coming from canonical neither aws which I find quite annoying considering the impact for them today we switched back our instances to m4
1788035,2018-10-18 18:36:13 UTC,We can confirm that this patch does not solve the issue as we are still seeing the same dmesg pattern with the 4.4.0-1069-aws kernel.
1788035,2018-10-17 10:09:26 UTC,I didn't find so far  way to reproduce the issue systematically.
1788035,2018-09-26 09:34:21 UTC,"Hello, it seems that this issue or a similar one still occurs despite the fix."
1788035,2018-10-12 15:54:27 UTC,I have the same.
1788035,2018-10-12 13:32:03 UTC,"We were reproducing this multiple times a day on multiple of our EC2 M5 instances. Interesting anecdote, our least loaded instances produced the bug more often than our heavily loaded instances."
1788035,2018-10-12 13:14:22 UTC,I am trying to reproduce it.
1788035,2018-09-26 15:36:56 UTC,i am also still seeing this bug after the fix.
1788035,2018-09-10 17:54:50 UTC,This bug was fixed in the package linux - 4.4.0-135.161
1788035,2018-08-29 11:04:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1788035,2018-10-12 16:04:28 UTC,So far the best I could reach is get the kernel call trace but not crashing the node yet.
1788040,2018-09-12 13:43:39 UTC,"Ok, going to close the nova-compute-lxd task then as it sounds like from a packaging point of view we're good, it's external integration (charms) that may run into problems."
1788040,2018-09-17 10:59:14 UTC,This bug was fixed in the package lxd - 1:0.3
1788040,2018-09-17 10:46:12 UTC,"As planned, releasing this to the release pocket by removing the blocker tag."
1788040,2018-09-16 00:18:02 UTC,"All autopkgtest failures have been dealt with, we're now all green and only held by this bug's tag."
1788040,2018-09-12 22:08:30 UTC,And package has now been uploaded to cosmic-proposed.
1788040,2018-09-12 20:06:46 UTC,Marking bug as block-proposed so we keep the transitional package in proposed for now.
1788040,2018-09-12 10:23:55 UTC,"From the perspective of nova-lxd, there isn't a problem with the snap version (as pylxd already works with a snap version of lxd).  However, the lxd charm will need to be altered to ensure that it installs / otherwise manages the fact that lxd is supplied in snap form."
1788040,2018-09-12 04:27:08 UTC,I've confirmed that adapt from the cosmic archive works just as well with the snap as it does the deb.
1788040,2018-09-12 04:08:20 UTC,"So looks like we're in good shape with removal of ""lxd-client"" and ""lxd-tools"" as only Suggests remains and that's autopkgtest which will be switched over to ""lxd"" soon enough."
1788040,2018-08-22 13:50:52 UTC,Thanks Martin!
1788040,2018-08-22 06:43:56 UTC,"Ah, it used to be useful for running the containers on a remote servers. I. e. what we used to do for armhf testing, they were running on remote arm64 OpenStack instances."
1788040,2018-08-22 06:27:09 UTC,"The only binary package left post-transition will be ""lxd"". The ""lxc-client"" and ""lxd-tools"" binary packages will be removed from the archive."
1788040,2018-08-22 06:15:29 UTC,"autopkgtest *only* uses the `lxc` CLI and documents the `lxd` setup CLI from $PATH. The package has a ""Suggests: lxd-client"". You mention that the ""lxd"" deb will remain around, does that apply to ""lxd-client"" as well?"
1788040,2018-09-12 04:31:17 UTC,And confirmed that snapcraft (cleanbuild) similarly works just fine.
1788044,2019-04-03 21:30:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788044,2018-08-20 21:17:14 UTC,Possible duplicate of #1723250 and/or #1723245
1788044,2018-08-20 21:30:07 UTC,This change was made by a bot.
1788044,2018-08-22 15:59:28 UTC,"Do you have a way to reproduce this bug, or was it a one time event?"
1788045,2018-08-21 19:21:45 UTC,"Hi @James,"
1788045,2018-08-21 19:24:56 UTC,"I am going to mark this bug as ""invalid"" since it doesn't seem to be a neutron bug."
1788045,2018-08-21 19:33:29 UTC,"FYI, this bug is forwarded to openstacksdk: https://storyboard.openstack.org/#!/story/2003517"
1788045,2018-08-21 20:29:13 UTC,"Ah, you're right. Thank you, and sorry for the confusion."
1788048,2019-05-21 11:07:05 UTC,"It seems like the upstream commits to fix this may have made journalctl --flush flaky and/or introduced other regressions:
https://github.com/systemd/systemd/pull/12230#issuecomment-491593897"
1788048,2019-05-29 18:11:31 UTC,Does installing finalrd package help?
1788048,2018-09-25 16:41:31 UTC,"C de-Avillez,"
1788048,2020-08-18 16:57:04 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1788048,2019-11-25 17:18:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788048,2019-05-15 19:57:03 UTC,@Dan Streetman
1788048,2018-09-04 21:42:48 UTC,"Guys, I think it's a critical problem!
All because I created an exclusive disk for / var"
1788048,2018-09-23 21:58:24 UTC,"Updated with upstream bug #; this seems to be an on-going concern, and depends on some not-yet-available interfaces between kernel and systemd."
1788048,2018-08-20 23:59:48 UTC,"I ended up using another solution, just do not know if it is the most correct.
Edit
sudo vim /lib/systemd/system/systemd-journald.service"
1788048,2018-08-20 22:01:41 UTC,"One more discussion about systemctl does not work correctly with the separate / var partition
https://bbs.archlinux.org/viewtopic.php?pid=1204644#p1204644"
1788048,2019-05-14 21:39:12 UTC,"Just to clarify, this does not hang shutdown/reboot for anyone, right?  It only fails to cleanly unmount /var, right?"
1788063,2018-08-21 13:19:59 UTC,I think delete is the best term.
1788063,2018-09-13 21:17:58 UTC,I think the proposed solution for bug 1735816 (if it is committed) should inform how this bug is resolved.
1788065,2018-08-21 13:45:27 UTC,"I did recreate the issue sort of and was able to add more the bucket; however, when I clicked back on the bucket from record query there is a message No Bucket Selected. The bucket is deleted."
1788065,2019-02-25 19:20:33 UTC,"I see the same thing Jane describes, including being able to add a new title to the supposedly deleted bucket. I never get the No Bucket Selected message that Elaine describes."
1788065,2019-02-25 20:11:40 UTC,I am able to delete recrd buckets in 3.2.2 with no problems
1788068,2018-09-06 18:23:15 UTC,"The bug is valid, the steps to reproduce are not - it might be a QSS-Bug - so yes, the widht of the clock wrong under certain circumstances - unfortunately we are not able to reproduce/fix it reliable upstream right now :)"
1788068,2018-09-06 17:53:55 UTC,"Well, let's ask this: does it work with sddm? Because if it does, sddm
ships with Lubuntu, i.e. Lubuntu implies the use of sddm. So, yes, weird
use case, regardless of whether or not it's common for you. I use
awesome with Lubuntu, but that's frankly pretty weird and I'm capable of
admitting as much."
1788068,2018-09-06 18:35:55 UTC,"Manjaro-lxqt:
Name            : lxqt-panel
Version         : 0.13.0-2
Description     : The LXQt desktop panel
Architecture    : x86_64"
1788068,2018-09-06 17:37:53 UTC,"Its not a really strange case. Its used on many distros, and documented many times as well.
 The point is why it doesn't work on Lubuntu, and only Lubuntu."
1788068,2018-09-06 23:50:22 UTC,It woks fine on Xubuntu on xfce-panel. I haven't tried lxqt on Xubuntu
1788068,2018-09-07 00:06:42 UTC,"That's kind of apples and oranges then, unfortunately. I have a sneaking
suspicion this might be some XDG sort of things. Can you collect all the
XDG variables on your Lubuntu, as well as Xubuntu and Manjaro?"
1788068,2018-09-06 18:50:19 UTC,"@agaida tsimonq2 said the bug is known upstream. Is there a bug report
for this? Why is this only a problem in some distributions?"
1788068,2018-09-06 15:12:55 UTC,"Here's how you can reproduce it:
(1) Remove or disable sddm
(2) Install getty autologin: https://wiki.archlinux.org/index.php/getty
(3) Reboot."
1788068,2018-09-06 15:29:15 UTC,Well now that's a really strange use case. Why not just use autologin in SDDM?
1788068,2018-08-21 13:56:37 UTC,"BTW marking as Incomplete regardless of whether or not we've heard other people having the problem. If we can't reproduce it, we don't have enough information to provide a fix."
1788068,2018-08-21 13:55:48 UTC,"I'm struggling to reproduce this. I do see you've shown me the problem, vmc, but I don't know how to make my system have the same problem. In other words, it is not that way on a fresh install. I suspect there is something about the settings you have that result in this change. What LXQt theme are you using? What about the font settings?"
1788068,2018-08-21 04:54:28 UTC,"Notice the ""clipped"" ""9"" on my attachment."
1788068,2018-08-21 04:32:46 UTC,"I've personally confirmed this a few times, it's known upstream."
1788068,2018-08-21 03:58:37 UTC,Here it is with no padding and set to an hour greater than 9.
1788068,2018-08-21 01:55:15 UTC,"Walter, that's because you ""pad"" with a zeo. Try without padding."
1788068,2018-08-21 00:09:25 UTC,"I cannot confirm this in a daily image with lxqt-panel 0.13.0-0ubuntu3, as you can see in the attached. Clear steps to reproduce, perhaps with particular screen sizes, along with images of the bug, would be very helpful."
1788070,2019-11-28 09:16:12 UTC,See dup (#1788070) - be able to assign a schematic symbol to a sheet.
1788070,2019-08-15 13:40:03 UTC,(a) has been implemented.
1788070,2018-09-01 12:10:30 UTC,"@Jeff, never mind. The learning was it worth for sure. :)"
1788070,2018-08-26 00:05:11 UTC,"@Ronnie, I do think it will be a lot easier to get this working in the new toolset.  Look at the bright side: you learned a lot about Kicad!"
1788070,2018-08-24 11:39:41 UTC,Another crack at a summary:
1788070,2018-08-23 17:45:04 UTC,This should be filed as a separate bug report.
1788070,2018-08-23 17:00:30 UTC,"Also, including here, is it possible to improve the navigator window? It would be nice to have some option to dock it in the EEschema window, or, at least, an option to keep it always on top."
1788070,2018-08-23 16:55:27 UTC,Perfect.
1788070,2018-08-25 23:23:01 UTC,"I've done a bit of work here: https://bugs.launchpad.net/kicad/+bug/593886/comments/2
But now seeing this bug, seems I've worked the wrong direction. :("
1788070,2018-08-23 14:16:51 UTC,Summary:
1788070,2018-08-22 11:47:31 UTC,@Jeff
1788070,2018-08-22 11:25:09 UTC,"@JP, well that wrecks my solution for (4). ;)"
1788070,2018-08-22 06:24:35 UTC,"The sheet name is used to prefix the local labels inside a sheet. It is mandatory.
(It is similar to a component reference.)
And needed by the hierarchy navigator."
1788070,2018-08-21 19:20:48 UTC,"For (4) I'd just as soon let the user decide what the title is.  If they want ""Sheet: "" in it then they can type that themselves."
1788070,2018-08-21 19:03:29 UTC,(3) has been requested at least once - https://bugs.launchpad.net/kicad/+bug/1784841
1788070,2018-08-21 10:46:37 UTC,"(1) and (2) should be addressed by the ""modern toolset for eeschema"" slated for 6.0."
1788070,2018-08-23 16:28:23 UTC,"On 8/23/2018 10:16 AM, Jeff Young wrote:

> Summary:
>
> (a) Implement 4-corner resize with new toolset for eeschema
> (b) Implement background fill and title parameter with new file format
> (c) Implement user-defined fields with new file format
> (d) Display title above sheet instead of sheetname
> (e) Display sheetname and filepath only in status bar
>


(f) Allow custom position, visibility, and font for sheet and file name
(g) Allow custom fill colors (new file format required)."
1788071,2018-08-21 00:36:32 UTC,"Here is an example file. It works in Firefox, it doesn’t neither in Chromium nor in Inkscape."
1788071,2018-08-21 00:40:41 UTC,"Here is a file with a workaround: the path which has the two texts on it is defined twice, with one definition going in the opposite direction, so that the two directions can be followed. This works in Firefox, in Chromium and in (the most important) Inkscape."
1788071,2020-03-19 13:09:22 UTC,Closing because Can't replicate; works in Inkscape.
1788077,2018-08-21 12:37:13 UTC,Got it.  What key does it in the main Kicad window?
1788077,2018-08-21 11:52:10 UTC,"Yes. It closes when I click on it. But it should work with keyboard also.
The tree view on the main kicad window works as expected."
1788077,2018-08-21 10:55:02 UTC,"@Leandro, did you try clicking on the little turn-down arrow next to the folder?"
1788077,2018-08-21 13:28:23 UTC,"Right-Arrow - Open folders and also move to the next item
Left-Arrow - Move to the parent folder
Spacebar (and Enter) - Toggles Open/Close a folder
Up-Arrow - Move the selection to the previous item
Down-Arrow - Move the selection to the next item
Home - Move the selection to the start
End - Move the selection to the end"
1788081,2018-08-21 01:57:46 UTC,"BTW, I forgot to mention a few things:"
1788081,2018-11-12 00:58:33 UTC,Hi Guys
1788081,2018-11-12 00:58:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788081,2018-11-12 03:49:47 UTC,@ajkan001:
1788082,2018-08-21 03:48:35 UTC,The issue appears to be the the upgrade-juju command correctly processes the requested agent-stream argument and finds the agent binaries in the right place and handles the controller upgrade.
1788082,2018-08-21 04:28:23 UTC,"Maybe I'm wrong because if the controller can get the agent binaries initially, they should then be cached and subsequent lookups from agents will find the cached copy, even though the agents may specify just the released stream."
1788086,2018-09-02 21:41:48 UTC,https://github.com/mixxxdj/mixxx/pull/1798
1788088,2019-05-29 00:41:58 UTC,I was able to add grub2-efi-x64 and shim-x64 to a CentOS image and successfully deploy using MAAS 2.6.0-rc1. I confirmed that the signed boot loaders were used post deployment. I've been unable to test this in a secure boot enabled environment as turning on secure boot with the machines in our CI requires physical access[1].
1788088,2019-12-11 00:12:44 UTC,This should be fixed with the attached branch.
1788088,2020-01-09 17:42:45 UTC,"This bug is fixed with commit 1be1cd71 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=1be1cd71"
1788088,2018-08-27 22:14:42 UTC,Not super happy about this.  Shim-x64 is installed and provides the efi file.
1788088,2018-08-23 02:51:38 UTC,"By installing the shim.x64 package in the image /boot/efi/EFI/BOOT/BOOTX64.EFI, /boot/efi/EFI/centos/shim.efi, and /boot/efi/EFI/centos/shimx64.efi are all created. Curtin only needs to ensure shim.x64 is installed and it configures the nvram with efibootmgr to fall back on /boot/efi/EFI/centos/shimx64.efi"
1788088,2018-08-27 19:03:43 UTC,"Do you happen to know what the fallback entry should look like or what the call to efibootmgr should be to specify shim as the fallback in case no other entries work (ie, the pxe entry fails when maas is offline)?"
1788095,2018-08-21 15:53:42 UTC,I agree I can't read the urls provided. In the docs it looks like
1788095,2018-08-21 23:46:10 UTC,"""juju-core"" is only used for Juju 1.x. Moving this over to ""juju"" which tracks Juju 2.x"
1788095,2019-02-05 13:49:44 UTC,The streams are now using the correct endpoints:
1788098,2019-04-10 08:21:11 UTC,"------- Comment From <email address hidden> 2019-04-10 04:10 EDT-------
(In reply to comment #66)

> Stefan NACK'ed the series. For some unknown reason that email did make it
> into the archive so here is ist content:
>
> > Since commit fb1522e099f0 (""KVM: update to new mmu_notifier semantic
> > v2"", 2017-08-31), the MMU notifier code in KVM no longer calls the
> > kvm_unmap_hva callback.  This removes the PPC implementations of
> > kvm_unmap_hva().
>
> This is not really the way SRUs should be done. We cannot remove support for
> interfaces after release. Also the amount of change as a requisite should be
> kept as minimal as possible. This just feels like too many changes without a
> strong argument on why this must be done that way.
>
> -Stefan
"
1788098,2019-04-09 05:42:08 UTC,Stefan NACK'ed the series. For some unknown reason that email did make it into the archive so here is ist content:
1788098,2019-04-08 14:42:18 UTC,"------- Comment From <email address hidden> 2019-04-08 10:37 EDT-------
This (In reply to comment #64)

> Hi Leonardo,
> unfortunately there was an issue with the SRU request and Juerg NACK-ed it,
> please have a look here:
> https://lists.ubuntu.com/archives/kernel-team/2019-March/099128.html
> Please re-submit the SRU request with the requested corrections.
"
1788098,2019-04-08 14:17:46 UTC,"Hi Leonardo,
unfortunately there was an issue with the SRU request and Juerg NACK-ed it, please have a look here:
https://lists.ubuntu.com/archives/kernel-team/2019-March/099128.html
Please re-submit the SRU request with the requested corrections."
1788098,2019-03-26 17:20:56 UTC,"------- Comment From <email address hidden> 2019-03-26 13:12 EDT-------
Updating:"
1788098,2019-03-14 19:50:57 UTC,"------- Comment From <email address hidden> 2019-03-14 15:47 EDT-------
Patchset SRU"
1788098,2019-03-12 19:00:51 UTC,"------- Comment From <email address hidden> 2019-03-12 14:52 EDT-------
(In reply to comment #60)
The patches were sent to Ubuntu kernel-team mailing list."
1788098,2019-02-26 14:50:19 UTC,apport information
1788098,2019-02-26 17:40:41 UTC,"------- Comment From <email address hidden> 2019-02-26 12:36 EDT-------
(In reply to comment #41)

> ...or perhaps I've misunderstood. Are the patches listed in comment #23 the
> complete set required to resolve the issue (with no complex backporting
> required)?
"
1788098,2019-02-26 14:50:17 UTC,apport information
1788098,2019-02-26 14:50:13 UTC,apport information
1788098,2019-02-26 14:50:12 UTC,apport information
1788098,2019-02-26 14:50:09 UTC,apport information
1788098,2019-02-26 14:50:08 UTC,apport information
1788098,2019-04-10 13:44:59 UTC,"In comment #22 above, it states that ""In a meeting with lagarcia, I was informed this patch is very important, and that it is already on kernel 4.18-15 onwards."""
1788098,2019-02-26 18:00:37 UTC,"------- Comment From <email address hidden> 2019-02-26 12:58 EDT-------
Here are the patches:"
1788098,2019-04-10 16:11:04 UTC,"------- Comment From <email address hidden> 2019-04-10 12:08 EDT-------
(In reply to comment #68)

> In comment #22 above, it states that ""In a meeting with lagarcia, I was
> informed this patch is very important, and that it is already on kernel
> 4.18-15 onwards.""
>
> So, I assume that the required patchset(s) are already applied to the 18.04
> HWE kernel, and this bug requests a backport to the bionic 4.15 kernel.
>
> Next step is for the Canonical kernel team to analyse this backport request,
> dropping the commit fb1522e099f0 (""KVM: update to new mmu_notifier semantic
> v2"", 2017-08-31), to assess whether it can be SRU'ed into the bionic 4.15
> kernel.
"
1788098,2019-02-26 14:50:06 UTC,apport information
1788098,2019-04-29 23:00:41 UTC,"------- Comment From <email address hidden> 2019-04-29 18:50 EDT-------
(In reply to comment #70)

> Leonardo, since you seem to have a reliable reproducer now, could you give
> this test kernel [1] a try? It just contains commit c066fafc595e (""KVM: PPC:
> Book3S HV: Use correct pagesize in kvm_unmap_radix()"") and is basically what
> Joe gave you (comment #5) but at that time you weren't able to reproduce the
> issue.
>
> [1] https://kernel.ubuntu.com/~juergh/lp1788098/
"
1788098,2019-11-15 06:43:45 UTC,"Hi Leonardo, yes that's correct.
Focus was changed in the way to make sure that everything is in 19.10, to be well prepared for 20.04 - and 18.04 (GA kernel 4.15) is not targeted (nevertheless 18.04 HWE kernel incl. the patches).
(All according to LP comment #66.)"
1788098,2019-11-14 21:07:48 UTC,"I know it's an old bug, but I just want to confirm if my understanding is correct:"
1788098,2019-09-30 13:23:13 UTC,"That was abs. correct, Rafael - thx (I just haven't had the permission to add D)."
1788098,2019-09-30 13:08:17 UTC,"Frank, based on your previous comment I'm also flagging disco as Fix Released. Please fix this if it makes no sense (just to be accurate). Thx!"
1788098,2019-09-27 09:08:17 UTC,I just double-checked all the commits that are mentioned in comment #67.
1788098,2019-09-27 06:01:09 UTC,"------- Comment From <email address hidden> 2019-09-27 01:51 EDT-------
(In reply to comment #73)

> Leonardo, can you elaborate on the 'other possible issues'? We're hesitant
> to pull 18 patches into a stable kernel under the assumption that they
> *might* fix some *potential* issues, without clear evidence. If you can test
> the single-patch kernel and report back that there are still issues then
> that's a much stronger case for the other patches.
>
> Commit 'KVM: PPC: Book3S HV: Avoid crash from THP collapse during radix page
> fault' that you're asking for requires all these additional backports to
> apply cleanly. Which makes me wonder if we're not actually introducing a
> problem with these backports just to fix it again later. Not saying that's
> the case, just wondering...
>
> Also, the following seem to be totally unrelated and unnecessary:
> - KVM: PPC: Remove unused kvm_unmap_hva callback
> - powerpc/mm/radix: Remove unused code
>
> While looking through the patches I also noticed that the following is the
> second patch of a series of 11 but it's the only one from the series that
> you're backporting.
> - powerpc/kvm: Switch kvm pmd allocator to custom allocator
> Its commit message mentions subsequent patches of that series so I'm
> wondering why we need/want only this single patch??
>
> Remember that we have to support this kernel for years and years to come so
> we only want to backport the absolute necessary.
>
> Lastly and FYI, the following is the minimal subset of your patches that all
> cherry-pick cleanly:
> - KVM: PPC: Book3S HV: Avoid crash from THP collapse during radix page fault
> - KVM: PPC: Book3S HV: Don't use compound_order to determine host mapping
> size
> - KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()
> - KVM: PPC: Book3S HV: radix: Refine IO region partition scope attributes
> - KVM: PPC: Book3S HV: Use __gfn_to_pfn_memslot() in page fault handler
> - KVM: PPC: Book3S HV: Handle 1GB pages in radix page fault handler
> - KVM: PPC: Book3S HV: Streamline setting of reference and change bits
> - KVM: PPC: Book3S HV: Radix page fault handler optimizations
>
> Please provide some context why we need all the above (and potentially more).
"
1788098,2019-09-26 19:51:19 UTC,"------- Comment From <email address hidden> 2019-09-26 15:42 EDT-------
Re-opening on our side to test in 19.10.  Everything should be there for that, but it would be good to confirm this in time to get any needed fixes to 20.04, too.  Just being clear at this point we don't need to target bionic - but validate on 19.10."
1788098,2019-09-26 17:59:21 UTC,"These patches are still needed to solve the bug, so this bug need to be reopened.
We are waiting for Paul's reply."
1788098,2019-07-22 14:24:10 UTC,"This bug has expired, marking it as invalid, please reopen if this is still a valid issue."
1788098,2019-07-13 04:18:13 UTC,[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.]
1788098,2019-07-13 04:18:09 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1788098,2019-05-13 21:11:39 UTC,"------- Comment From <email address hidden> 2019-05-13 17:04 EDT-------
Adding Paul Mackerras - can you help with the context for the patches - beyond the potential performance impact?   We were picking up this series because it fixes the migration problem, which appeared after adding a patch for bug 169712 for performance.  Thanks!"
1788098,2019-05-11 00:00:44 UTC,"------- Comment From <email address hidden> 2019-05-10 19:54 EDT-------
Hello Juerg,"
1788098,2019-05-10 12:25:05 UTC,"Leonardo, can you elaborate on the 'other possible issues'? We're hesitant to pull 18 patches into a stable kernel under the assumption that they *might* fix some *potential* issues, without clear evidence. If you can test the single-patch kernel and report back that there are still issues then that's a much stronger case for the other patches."
1788098,2019-05-06 14:52:34 UTC,"Leonardo, we're evaluating the patch series for inclusion."
1788098,2019-04-11 11:42:30 UTC,"Leonardo, since you seem to have a reliable reproducer now, could you give this test kernel [1] a try? It just contains commit c066fafc595e (""KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()"") and is basically what Joe gave you (comment #5) but at that time you weren't able to reproduce the issue."
1788098,2019-02-26 14:50:02 UTC,apport information
1788098,2018-08-21 05:05:09 UTC,"Oh, I just realized while initially reported against qemu in bug 1781526 that this is a kernel, and not a qemu patch."
1788098,2019-02-26 14:49:59 UTC,apport information
1788098,2019-01-24 14:29:57 UTC,"------- Comment From <email address hidden> 2019-01-24 09:26 EDT-------
By suggestion of Michael Ranweiler, I did some concurrent migration tests.
In fact, I just repeated the procedure used before, but did it twice at roughly the same time (in parallel)."
1788098,2019-01-07 11:17:03 UTC,"Hi Leonardo,
thanks for your efforts trying to verify that.
Given that you couldn't trigger it I wonder what to do.
Currently it is incomplete waiting for such a test, but as it seems to elude you I'd suggest we call the bug invalid until we would know otherwise."
1788098,2019-01-04 19:39:34 UTC,------- Comment (attachment only) From <email address hidden> 2019-01-04 14:32 EDT-------
1788098,2019-01-04 19:39:32 UTC,"------- Comment From <email address hidden> 2019-01-04 14:29 EDT-------
Test: Verify all memory after migration"
1788098,2019-01-04 11:19:26 UTC,"------- Comment From <email address hidden> 2019-01-04 06:12 EDT-------
I have tried the following test in order to reproduce the bug:"
1788098,2018-12-21 17:20:08 UTC,"------- Comment From <email address hidden> 2018-12-21 12:10 EDT-------
Hello,"
1788098,2019-01-24 14:29:58 UTC,------- Comment (attachment only) From <email address hidden> 2019-01-24 09:28 EDT-------
1788098,2018-11-29 13:43:24 UTC,"Nothing yet happened here.
I also declared the related qemu fix that is blocked by this as incomplete.
@manoj/jfh - maybe time for triage-r here?"
1788098,2018-08-30 20:19:44 UTC,"------- Comment From <email address hidden> 2018-08-30 10:29 EDT-------
Thanks, I've asked for some testing assistance from our KVM team but will note here some of the details from the original report of this problem.."
1788098,2018-08-22 16:04:57 UTC,"I built a test kernel with the following patch:
KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()"
1788098,2018-08-21 06:05:29 UTC,"FYI: this is essentially an IBM request, reverse mirroring will happen at some point, but I wanted to make you aware right now"
1788098,2018-08-21 06:02:53 UTC,"For this particular case the log files are not needed and/or applicable.
After discussing in #stable-kernel I set it to confirmed."
1788098,2018-08-21 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788098,2019-02-26 14:50:01 UTC,apport information
1788098,2018-11-12 14:38:54 UTC,Marking as incomplete while awaiting the IBM testing assistance described in comment #6.
1788098,2019-01-24 14:39:54 UTC,"------- Comment From <email address hidden> 2019-01-24 09:34 EDT-------
By the test results, the problem doesn't seem to reproduce."
1788098,2018-12-06 14:15:13 UTC,"After discussions with IBM, reducing the priority."
1788098,2019-01-24 14:39:58 UTC,------- Comment (attachment only) From <email address hidden> 2019-01-24 09:30 EDT-------
1788098,2019-01-24 14:39:56 UTC,------- Comment (attachment only) From <email address hidden> 2019-01-24 09:29 EDT-------
1788098,2019-02-26 14:49:57 UTC,apport information
1788098,2019-02-26 14:49:56 UTC,apport information
1788098,2019-02-26 14:49:51 UTC,apport information
1788098,2019-02-26 14:49:49 UTC,"ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116,  1 Feb 26 08:00 seq
 crw-rw---- 1 root audio 116, 33 Feb 26 08:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=/dev/mapper/rhel_zzfp368h-swap
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
PciMultimedia:"
1788098,2019-02-26 09:55:25 UTC,...or perhaps I've misunderstood. Are the patches listed in comment #23 the complete set required to resolve the issue (with no complex backporting required)?
1788098,2019-02-26 08:27:38 UTC,"In comment #22, you mentioned working on a backport of these patches to the Ubuntu 4.15 kernel. Was this successful? Is it possible to attach the backported patchsets to this bug?"
1788098,2019-02-26 14:49:54 UTC,apport information
1788098,2019-02-26 06:33:00 UTC,"Thanks for all your effort Leonardo,
that seems to make the bug valid again, but I'll leave that to JFH/Manoj to resurrect it and make it a proper kernel bug as it seems there now is a way to test it (at least you can do so) and a set of patches. I can not speak for the ack/nack of those back-ports but that the kernel Team will do then."
1788098,2019-02-25 23:39:39 UTC,"------- Comment From <email address hidden> 2019-02-25 18:35 EDT-------
I cherry-picked all patches on top of ubuntu-bionic (Ubuntu-4.15.0-45.48)."
1788098,2019-02-20 01:59:42 UTC,"------- Comment From <email address hidden> 2019-02-19 20:52 EDT-------
(In reply to comment #34)

> In a meeting with lagarcia, I was informed this patch is very important, and
> that it is already on kernel 4.18-15 onwards.
>
> In fact, including this one. there are two important patches on this subject:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/
> ?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
> https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/
> ?h=kvm-ppc-next&id=6579804c431712d56956a63b1a01509441cc6800
"
1788098,2019-02-08 19:09:57 UTC,"------- Comment From <email address hidden> 2019-02-08 14:05 EDT-------
In a meeting with lagarcia, I was informed this patch is very important, and that it is already on kernel 4.18-15 onwards."
1788098,2019-01-24 15:21:02 UTC,"Thanks for your continuous efforts on this Leonardo, I have no further suggestion.
I think to stay on the safe side we will keep everything as-is for now."
1788098,2019-01-24 14:39:59 UTC,------- Comment (attachment only) From <email address hidden> 2019-01-24 09:33 EDT-------
1788098,2019-02-26 08:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788101,2018-08-21 11:25:31 UTC,"Thanks, I can see the need to be able to help with that over time. It feels like something we need to bring to the current discussions around improving config for the roadmap."
1788104,2018-08-21 09:36:16 UTC,"Hello @krichter722, thank you for the time spent testing UPnP Router Control."
1788104,2018-08-21 20:00:09 UTC,"Hello Daniele,"
1788104,2021-02-05 14:56:14 UTC,"Hi Karlk, seems more a problem on the libgupnp because there is no device detected."
1788111,2018-10-17 04:11:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788112,2018-08-21 16:13:31 UTC,"@jbicha: Those changes will *never* affect a released Debian or Ubuntu version, only in-development stuff.
The earliest point I actually would consider making such a change is after the Debian Buster release and at least one release before the next Ubuntu LTS. Also, the amount of packages with issues should be really low at that point, ideally be zero."
1788112,2018-08-21 13:27:15 UTC,"Ubuntu Software uses appstream data to list available applications, as opposed to synaptic which is a plain package management GUI (it doesn't make a distinction between applications and other types of packages)."
1788112,2018-08-21 13:48:18 UTC,It would be neat though if font-manager fixed at least the issues listed at https://appstream.debian.org/sid/main/issues/font-manager.html with its metadata.
1788112,2018-08-21 15:40:00 UTC,"Matthias, if you make any changes to be stricter, please ensure it will not affect Ubuntu 16.04 LTS or 18.04 LTS (or Debian Stretch), as long as those releases are still supported."
1788115,2018-08-24 17:24:42 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc3 release candidate.
1788115,2018-09-14 14:10:04 UTC,"Reviewed:  https://review.openstack.org/594185
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=059c2d4a8a9967403755c40beda667c9463848a8
Submitter: Zuul
Branch:    stable/queens"
1788115,2018-09-24 14:46:55 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1788115,2018-09-24 14:46:35 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1788115,2019-03-22 03:48:28 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1788115,2018-08-24 08:45:55 UTC,"Reviewed:  https://review.openstack.org/594178
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad14e428f82f02d71e0b33ec6d20e7810a978e3b
Submitter: Zuul
Branch:    stable/rocky"
1788115,2018-09-21 00:21:29 UTC,"Reviewed:  https://review.openstack.org/594184
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=62464883e1c2ba98e1fddb1284171ca5bef4d8e1
Submitter: Zuul
Branch:    stable/pike"
1788115,2018-08-22 22:54:04 UTC,"Reviewed:  https://review.openstack.org/594050
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=690f91b5c7f7e84a4e6d351b27c05818d947cce1
Submitter: Zuul
Branch:    master"
1788115,2018-08-21 10:27:17 UTC,Indeed that's the case - instance.host is NULL and get_instance_availability_zone returned NULL AZ.
1788115,2018-08-21 13:58:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/594184"
1788115,2018-08-21 13:51:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/594178"
1788115,2018-08-21 08:24:16 UTC,That's quite possible (deleted before being scheduling). I'm gonna test it
1788115,2018-08-21 08:03:06 UTC,"While it is true that populate_missing_availability_zone does not check for deleted instances; I don't see how it can go into infinite loop unless there is no CONF.default_availability_zone set (https://github.com/openstack/nova/blob/722d5b477219f0a2435a9f4ad4d54c61b83219f1/nova/availability_zones.py#L99) which is the last resort; meaning CONF.default_availability_zone is set to None, which by default is ""nova""."
1788115,2018-08-21 07:13:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/594050"
1788115,2018-08-21 14:00:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/594185"
1788119,2018-08-22 01:13:43 UTC,"Yes, I found the related code in oslo.log and expected maybe there was historical reason for the code. :)"
1788119,2018-08-22 13:38:48 UTC,Adding in Doug who has more context on the oslo.log change.
1788119,2018-08-21 18:16:11 UTC,Your observations are correct.
1788121,2019-10-02 13:45:47 UTC,"Similar issue, though manifests on my system by a double beep every time it happens. May be linked to playing music through GooglePlayMusicDesktopPlayer, and only through the internal soundcard jack, not with USB headphones."
1788121,2019-10-02 13:56:33 UTC,"Nope, didn't work. Will carry on watching this thread..."
1788121,2019-10-02 13:57:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788121,2019-10-03 10:19:51 UTC,":( Pretty sure mine was caused by intermittent power on a laptop docking station. Easy fix - make sure your power lead is properly seated. Happy the beeps are gone, not sure that helps anyone else watching."
1788122,2018-08-21 08:09:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/594068"
1788122,2018-08-21 12:06:18 UTC,The lack of a uuidsentinel module in oslotest isn't a bug.
1788122,2019-05-25 01:20:05 UTC,"This uuidsentinel module had been added in oslo-utils [1], so I think we should not add it into oslotest again."
1788125,2020-01-23 20:28:42 UTC,dpkg terminal log looks corrupted.  Might be an instance of LP: #1809579 or LP: #1791515
1788129,2018-08-29 06:11:14 UTC,"Change abandoned by zhufl (<email address hidden>) on branch: master
Review: https://review.openstack.org/595399
Reason: not basic function, so test it on nova side"
1788129,2018-08-21 09:49:56 UTC,I believe during review we intentionally did not add support for server tags when creating a server with cells v1 because cells v1 is deprecated:
1788129,2018-08-21 09:53:27 UTC,"I've commented in the tempest patch, but I don't see why we need a tempest test for this, the functionality is already tested in the nova repo using functional tests and all we really need to test this is the nova API and DB. There are no other services involved."
1788137,2018-08-22 09:54:55 UTC,"Furthermore if a version of Inkscape is already installed, it should be listed first IMHO."
1788138,2019-02-04 17:02:51 UTC,"ok, so while looking into that list, we should keep in mind the ""valid cases"" as it's described in https://bugs.launchpad.net/tripleo/+bug/1788138/comments/2"
1788138,2021-02-17 17:09:08 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1788138,2019-02-06 16:21:28 UTC,"I think one thing can simplify templates a lot a merging all configs under var/lib/config-data/foo and removing *any* use of /var/lib/config-data/puppet-generated/foo, but for debug purposes only (there is a comment that explains that a copy of files modified during puppet run is useful for debugging). I'm not sure when we started referencing those debugging purposes only files residing in the puppet-generated paths, but that had been apparently a wrong move, that creates this subject issue in the first place."
1788138,2019-02-04 16:52:10 UTC,"So looking into that http://paste.openstack.org/show/eFwIo5kcp40DUiYYSA9Y/, yet another example is lines #203 vs #215 and #228. My gut feeling is that the latter must be with puppet-generated in it as well."
1788138,2019-02-01 15:03:09 UTC,"But that's not sure, cuz that all used to be ran on the host, not in a config containers, and there is *nothing* to pick from /var/lib/..."
1788138,2019-02-01 14:25:06 UTC,Related bug 1766178
1788138,2019-02-04 16:41:33 UTC,"thinking more of the fixes like in https://review.openstack.org/#/c/634649/2..3/docker/services/database/mysql.yaml@224 in the context of this issue, I came to a filter http://paste.openstack.org/show/eFwIo5kcp40DUiYYSA9Y/ that shows possible mismatches (look into ""config-data"" of the bind-mount paths used for docker_puppet_tasks vs docker_config's step_X sections). That is something we might want to align and probably could as well automate for the YAML checker."
1788138,2018-11-29 10:36:36 UTC,Related partial fix https://review.openstack.org/#/c/620868
1788138,2018-09-10 09:30:21 UTC,I'm fine with limiting this bug to identifying 2) and making sure they're consistent about directly mounting /var/lib/config-data/<service>/... vs /var/lib/config-data/puppet-generated/<service>/
1788138,2018-08-27 22:55:34 UTC,Its not quite as simple as doing a tht grep for /var/lib/config-data. Here are some things to consider:
1788138,2018-08-21 11:48:55 UTC,The solution is for each of the listed cases (there is a 4 possible ways to bind-mount things):
1788138,2019-02-01 14:17:50 UTC,It seems we have /etc/pki/ca-trust/source/anchors:/etc/pki/ca-trust/source/anchors defined globally and failing to catch up puppet config changes for Keystone IdM from the /var/lib/config-data/puppet-generated/keystone/etc/pki/ca-trust/source/anchors/ directory.
1788147,2019-05-28 02:47:10 UTC,Does someone have some idea about this bug?
1788147,2018-08-21 10:53:51 UTC,https://review.openstack.org/#/c/594124/
1788149,2020-05-19 11:04:11 UTC,@Dilip: Looking at the logs form comment #8 I don't see the long running GET operation. Neither any indication for HTTP 504 that you also mentioned in your comment. Could you please provide a bit more specific data about your fault?
1788149,2020-05-22 05:03:32 UTC,I am also experiencing this problem
1788149,2020-07-28 04:17:22 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1788149,2019-04-07 16:32:49 UTC,Me too experiencing the same issue. sometimes it gives us 504 also.
1788149,2020-05-28 09:43:04 UTC,@hulina: eventlet 0.20.1 known to be broken[1]. Follow the suggestions in https://bugs.launchpad.net/nova/+bug/1788149/comments/2
1788149,2018-10-22 04:18:32 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1788149,2018-08-22 08:36:33 UTC,"@Matt @s10
thanks for help, I upgrade the eventlet to 0.24.1, now it works fine. I will keep checking the new version of eventlet don't break the existing component."
1788149,2018-08-22 10:46:47 UTC,"@cnskyhigh
eventlet 0.24.1 will break neutron-metadata-api if you don't have a fix from https://review.openstack.org/#/c/576638/, see related bug https://bugs.launchpad.net/neutron/+bug/1777640"
1788149,2018-08-23 02:34:58 UTC,"@s10
thanks for your reminding.
will update the fix into neutron"
1788149,2018-08-21 14:51:49 UTC,"Also, are you running nova-api in uwsgi or mod_wsgi? Because we aren't monkey-patching eventlet in that case, see: https://review.openstack.org/#/c/592285/"
1788149,2018-08-21 14:46:49 UTC,"This bug might be related to eventlet DNS resolution issue. It was introduced in eventlet 0.20.0. The same bug exists in neutron: https://bugs.launchpad.net/neutron/+bug/1785615
Possible solution is to upgrade to eventlet 0.24.1 (isn't possible for pike) or downgrade eventlet to 0.19.0."
1788149,2018-08-21 14:38:42 UTC,"From your nova-api log snippet, I don't see the ""get_or_set_cached_cell_and_set_connections"" lock being held for 30 seconds. Can you attach the nova-api log where you're seeing that happen?"
1788150,2018-12-04 16:40:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1788150,2018-12-04 16:58:29 UTC,Looking a bit the issue seems fixed in 18.10
1788150,2018-12-06 14:17:40 UTC,"Unsure how to reproduce the issue there, ""python"" default to 2.7 on bionic when that one is installed (which is the case when using duplicate since it's a depends). Did you manually change your default python version and if so how did you do it?"
1788154,2021-01-21 12:48:25 UTC,"Possible workaround for this bug is to create this link:
 ln -rsf /usr/lib/jvm/default-java/lib/ /usr/lib/jvm/default-java/lib/amd64"
1788154,2021-01-21 12:33:34 UTC,I've prepared jsvc 1.2 packages because I needed urgently for some uat and production machines
1788154,2019-01-25 17:58:04 UTC,"I've published PPA packages of 1.1.0 at https://launchpad.net/~epkugelmass/+archive/ubuntu/jsvc for trusty and xenial. Will do bionic soon, as well. Perhaps a good starting point for the package maintainers."
1788154,2020-09-14 14:16:55 UTC,"Still old version in the archive for Ubuntu 20.04.
Any plans to solve this?"
1788154,2018-11-02 16:55:06 UTC,"I would really like to see this package updated to 1.1.0 as well. I tried to build my own executable from source, but couldn't get past the first two steps from the official site..."
1788154,2018-11-02 16:52:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788154,2019-01-11 01:29:35 UTC,https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
1788155,2018-08-21 12:24:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1788156,2018-08-28 18:19:52 UTC,I think this is a dup of #1747966
1788161,2018-08-21 12:38:22 UTC,"On Ubuntu 18.04 the odb package still contains the db pragma bug.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889664"
1788162,2018-08-21 12:33:11 UTC,"Errors were encountered while processing:
 /var/cache/apt/archives/texlive-fonts-extra-doc_2017.20180305-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)"
1788162,2018-08-24 06:39:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788165,2018-08-22 15:14:58 UTC,"Agreed we need to provide staff-facing settings for this, but in the meantime I just wanted to remind everyone it's possible for admins to disable individual sounds globally on the server.  See the example in bug 1691860.  In essence, you put a null audio file in just the right spot on the server.  The browser console (or Apache logs) will show you what audio file the browser is trying to load for each situation."
1788168,2018-08-21 12:57:18 UTC,"StacktraceTop:
 _dl_fixup (l=0x556b156c5790, reloc_arg=<optimized out>) at ../elf/dl-runtime.c:84
 _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125
 create_linear_gradient_image (gradient=<optimized out>) at ../../../../fb/fbpict.c:251
 image_from_pict_internal (pict=pict@entry=0x556b1634ce10, has_clip=has_clip@entry=0, xoff=xoff@entry=0x7ffd7cc0b650, yoff=yoff@entry=0x7ffd7cc0b654, is_alpha_map=is_alpha_map@entry=0) at ../../../../fb/fbpict.c:469
 wfb_image_from_pict (pict=pict@entry=0x556b1634ce10, has_clip=has_clip@entry=0, xoff=xoff@entry=0x7ffd7cc0b650, yoff=yoff@entry=0x7ffd7cc0b654) at ../../../../fb/fbpict.c:487"
1788170,2018-08-22 16:59:03 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1788170,2018-08-21 13:00:08 UTC,This change was made by a bot.
1788170,2018-08-21 13:03:32 UTC,Output of dmesg | grep Blu when I try to activate Bluetooth
1788170,2018-08-23 12:10:12 UTC,I've installed the kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.3 and the problem was resolved!
1788173,2018-08-28 21:22:28 UTC,"Hi Peter,"
1788173,2021-02-08 22:28:26 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11543"
1788173,2021-02-08 23:08:27 UTC,"To test:
1. Log in as Admin, navigate to Administration menu -> Extensions -> Plugins -> Configuration for module mobileapi (in the Plugin type: module section for mobileapi)
2. Observe the headings/ labels on the screen
Expected:
All headings are spelled correctly
Actual:
The ""Configuration item"" is misspelled."
1788176,2018-08-21 13:29:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/594172"
1788176,2018-08-21 15:58:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/594334"
1788176,2018-08-21 17:37:14 UTC,"Reviewed:  https://review.openstack.org/594172
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2b46354d5ab6d59790e69c44bc36a17074155774
Submitter: Zuul
Branch:    master"
1788176,2018-08-21 17:39:50 UTC,"Reviewed:  https://review.openstack.org/594334
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f7c5aca3b2b57547c9f95b8432da60b59d66fadf
Submitter: Zuul
Branch:    master"
1788176,2019-03-22 03:48:25 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1788180,2019-02-04 21:31:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/634814"
1788180,2019-03-24 23:39:38 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1788180,2019-03-22 03:44:42 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1788180,2019-02-07 02:20:40 UTC,"Reviewed:  https://review.openstack.org/634814
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=218c0f5f974d5ffd646b6b816bfb3fc494829e7b
Submitter: Zuul
Branch:    stable/rocky"
1788180,2019-01-16 00:35:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/631103"
1788180,2019-01-22 23:12:19 UTC,"Reviewed:  https://review.openstack.org/631103
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=890e2d320e8e8e7b501af8e21cc6b751fb204d04
Submitter: Zuul
Branch:    master"
1788180,2019-01-16 00:04:09 UTC,Seems like it would be reasonable to add handling of X-Forwarded-Proto and prefer it over Origin if it's present. I can try proposing a patch and see what people think about it.
1788181,2018-12-13 05:15:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788181,2019-01-03 15:47:04 UTC,This description for the backend package says:
1788184,2018-08-23 12:52:30 UTC,"host on compute is set here
https://github.com/openstack-dev/devstack/blob/5da7e4a22ede5f3049e7607a54a0f5ca2b413a29/lib/nova#L943-L949"
1788184,2018-08-21 18:19:10 UTC,"Hi @tikitavi,"
1788184,2018-08-22 11:28:50 UTC,"Hi, the local.conf and other logs are in attachment, if you need more you can find it here:
http://logs.openstack.org/77/589177/1/experimental/ec2-api-rally-fakevirt/2b60cc7/logs/"
1788184,2018-08-22 22:26:11 UTC,A few observations from your provided neutron log [1]:
1788184,2018-08-22 22:27:45 UTC,"I am going to mark this bug as ""invalid"" because it doesn't seem to be a neutron bug."
1788186,2018-08-23 20:26:46 UTC,Also hit in: nw-network-health-maas-2-2.  Please update the discourse ci test posts when resolved.
1788188,2018-09-13 13:30:51 UTC,Note to self.
1788188,2018-09-05 13:59:19 UTC,"I've hit that 'retrigger' button 2 more times and have not seen failures.
I just did again. Don't know what to do. :-("
1788188,2018-09-13 13:56:40 UTC,"@xnox,
Are you suggesting the /media/root-ro entry in /etc/fstab line for
/media/root-ro should have x-systemd.DefaultDependencies=no ?"
1788188,2018-08-23 08:53:23 UTC,"I was pushing this through autopkgtesting on LP-Infra where we see issues with that sometimes.
Unfortunately when you need an issue it does not show up, I only have 4 good cases:"
1788188,2018-09-06 20:12:35 UTC,"I uploaded open-iscsi_2.0.874-5ubuntu8 which has the debug code
that we were toying with included.  It also includes a fix for
FTBFS bug 1791154."
1788188,2018-08-22 15:08:51 UTC,"I pushed a branch up to
 https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/bug/1788188-debug
that Christian and I are trying to get some additional debug information out of a failure."
1788188,2018-08-21 14:25:12 UTC,"While it might seem unimportant ""only"" hitting some open-iscsi tests we can't be sure how many cases and how many people are hit by this every now and then."
1788188,2018-08-22 16:31:42 UTC,"here is a pastebin of boot with systemd debugging.
 http://paste.ubuntu.com/p/vGTRh6WB3B/"
1788190,2018-09-10 18:53:19 UTC,"The conclusion I've reached is that something like C#5 is good for 18.04, but for 16.04 and earlier we should still use apt-key."
1788190,2018-08-21 20:34:36 UTC,"If you have to, better do"
1788190,2018-08-21 16:07:12 UTC,Or if you are using sudo apt-key instead of gpg directly:
1788190,2018-08-28 00:44:54 UTC,@juliank Should C#5 work on 16.04?  Trying it via multipass and it doesn't get the keys added to apt-key list.
1788190,2018-08-21 15:39:38 UTC,"Okay, it looks like issues have been created upstream (https://dev.gnupg.org/T3065#111023). But it appears that the gpg devs don't really get how to implement a standards compliant HTTP client:"
1788190,2018-08-21 16:00:36 UTC,The workaround for now is to use curl to fetch the keys instead:
1788201,2018-08-30 09:28:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788221,2018-09-03 16:03:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788222,2018-09-11 17:59:22 UTC,Xenial has an earlier version of the patches that have introduced the issue and it will require a custom fix.
1788222,2018-10-22 16:31:21 UTC,This bug was fixed in the package linux - 4.4.0-138.164
1788222,2018-10-12 00:25:39 UTC,"I was able to verify that the fix in Xenial 4.4.0-138.164 works. The procedure was the same as in comment #4 [1], but with less run time."
1788222,2018-10-04 10:05:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1788222,2018-09-11 20:11:08 UTC,I added all debian to a tarball to simplify the download:
1788222,2018-09-11 19:53:01 UTC,The fix for xenial was submitted for review:
1788222,2018-09-10 18:15:29 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1019.20
1788222,2018-08-28 17:01:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1788222,2018-09-06 17:31:04 UTC,The 4.4 xenial kernel is not affected by the problem.
1788222,2018-09-06 12:04:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788222,2018-08-31 00:07:09 UTC,"Applied the patch from -proposed:
root@Ubuntu1804:~# echo ""deb http://archive.ubuntu.com/ubuntu/ bionic-proposed restricted main multiverse universe"" | tee -a /etc/apt/sources.list
root@Ubuntu1804:~# apt-get update
root@Ubuntu1804:~# apt-get dist-upgrade
root@Ubuntu1804:~# shutdown -r 0"
1788222,2018-08-22 07:25:11 UTC,"This fix will included on the main kernels, so no need to track the linux-gcp derivatives."
1788222,2018-08-21 16:09:26 UTC,"SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-August/094767.html"
1788222,2018-09-10 17:53:06 UTC,This bug was fixed in the package linux - 4.15.0-34.37
1788224,2018-08-21 21:14:21 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1788224,2018-08-21 19:45:45 UTC,"not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1788224,2018-08-21 20:25:00 UTC,"Originally on 0.92.2, now on 0.92.3 on Windows 10."
1788224,2020-03-29 12:10:51 UTC,Closing because INVALID: Can't replicate. See following explanation.
1788228,2018-10-04 22:33:09 UTC,This issue was fixed in the openstack/networking-ovn 5.0.1 release.
1788228,2018-08-31 22:16:33 UTC,"Reviewed:  https://review.openstack.org/594328
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=cffac6d8bd244c29ba5fe0c3cd41523bbba47638
Submitter: Zuul
Branch:    stable/rocky"
1788239,2018-08-21 16:39:40 UTC,"Demoting packages to cosmic-proposed:
 thepeg 1.8.0-3build1 in cosmic
 herwig++ 2.6.0-1.1build2 in cosmic
Comment: LP: #1788239: remove lhapdf (ftbfs), and demote rdeps
2 packages successfully demoted."
1788239,2018-08-21 16:40:32 UTC,"Removing packages from cosmic:
 lhapdf 5.9.1-6 in cosmic
  lhapdf-ccwrap-doc 5.9.1-6 in cosmic amd64
  lhapdf-ccwrap-doc 5.9.1-6 in cosmic arm64
  lhapdf-ccwrap-doc 5.9.1-6 in cosmic armhf
  lhapdf-ccwrap-doc 5.9.1-6 in cosmic i386
  lhapdf-ccwrap-doc 5.9.1-6 in cosmic ppc64el
  lhapdf-ccwrap-doc 5.9.1-6 in cosmic s390x
  lhapdf-pdfsets-minimal 5.9.1-6 in cosmic amd64
  lhapdf-pdfsets-minimal 5.9.1-6 in cosmic arm64
  lhapdf-pdfsets-minimal 5.9.1-6 in cosmic armhf
  lhapdf-pdfsets-minimal 5.9.1-6 in cosmic i386
  lhapdf-pdfsets-minimal 5.9.1-6 in cosmic ppc64el
  lhapdf-pdfsets-minimal 5.9.1-6 in cosmic s390x
  liblhapdf-dev 5.9.1-6 in cosmic amd64
  liblhapdf-dev 5.9.1-6 in cosmic arm64
  liblhapdf-dev 5.9.1-6 in cosmic armhf
  liblhapdf-dev 5.9.1-6 in cosmic i386
  liblhapdf-dev 5.9.1-6 in cosmic ppc64el
  liblhapdf-dev 5.9.1-6 in cosmic s390x
  liblhapdf0v5 5.9.1-6 in cosmic amd64
  liblhapdf0v5 5.9.1-6 in cosmic arm64
  liblhapdf0v5 5.9.1-6 in cosmic armhf
  liblhapdf0v5 5.9.1-6 in cosmic i386
  liblhapdf0v5 5.9.1-6 in cosmic ppc64el
  liblhapdf0v5 5.9.1-6 in cosmic s390x
  octave-lhapdf 5.9.1-6 in cosmic amd64
  octave-lhapdf 5.9.1-6 in cosmic arm64
  octave-lhapdf 5.9.1-6 in cosmic armhf
  octave-lhapdf 5.9.1-6 in cosmic i386
  octave-lhapdf 5.9.1-6 in cosmic ppc64el
  octave-lhapdf 5.9.1-6 in cosmic s390x
  python-lhapdf 5.9.1-6 in cosmic amd64
  python-lhapdf 5.9.1-6 in cosmic arm64
  python-lhapdf 5.9.1-6 in cosmic armhf
  python-lhapdf 5.9.1-6 in cosmic i386
  python-lhapdf 5.9.1-6 in cosmic ppc64el
  python-lhapdf 5.9.1-6 in cosmic s390x
Comment: LP: #1788239: remove lhapdf (ftbfs), and demote rdeps
1 package successfully removed."
1788242,2018-08-22 09:43:59 UTC,"I have tested the repo locally, and I have not found any issue. Can you check again? It was probably a transient network error, or a CentOS mirror issue."
1788242,2018-08-22 11:48:02 UTC,"Bonjour,
I found the solution. I disabled the epel-release repository. The conflict comes from epel with centos-release-openstack-queens."
1788250,2018-09-05 11:53:14 UTC,"the bug is in openjdk-lts and going to be fixed there, closing the java-atk-wrapper item since there is nothing to do for this one"
1788250,2018-09-16 01:03:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788250,2018-09-12 22:05:21 UTC,This bug was fixed in the package openjdk-lts - 10.0.2+13-1ubuntu0.18.04.2
1788250,2018-09-12 20:52:18 UTC,"On Wed, Sep 12, 2018 at 08:21:52PM -0000, Norbert wrote:

> I have spent long time adding all affected software to the bug list.
"
1788250,2018-09-12 20:25:48 UTC,Moreover we have 1074 views of related Q&A on AskUbuntu ( https://askubuntu.com/q/1067569/66509 ).
1788250,2018-09-12 20:21:52 UTC,@Steve Langasek (vorlon)
1788250,2018-09-12 20:18:05 UTC,"@Steve Langasek (vorlon)
Could you please fix the bug?"
1788250,2018-09-12 19:53:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788250,2018-09-05 12:00:46 UTC,jMeter fails to start with the error message: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper
1788250,2018-08-27 09:44:33 UTC,"Google found the workaround in #4 from 2015, and it has worked for me, running SQL Workbench/J."
1788250,2018-09-05 08:03:29 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug is being tracked and a fix has been proposed to the openjdk-lts package.
1788250,2018-08-26 11:07:32 UTC,Switching to the Official Oracle Java 8 Package was the workaround that worked for me.
1788250,2018-08-26 11:01:01 UTC,The workaround to comment out the accessibility.properties does not work on Ubuntu 18.04.1 using the Unity desktop
1788250,2018-08-23 02:13:57 UTC,"Workaround from Freeplane bug-tracker
https://sourceforge.net/p/freeplane/bugs/2605/"
1788250,2018-08-23 02:05:51 UTC,Also breaks freeplane
1788250,2018-08-21 21:55:22 UTC,It seems this regression has been introduced through https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900912
1788250,2018-08-21 18:10:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788260,2020-09-21 15:15:37 UTC,signoff at user/rogan/lp1788260_non_cat_in_house_use_aacct
1788260,2020-09-21 15:16:39 UTC,I'm going to take off the needs-release notes tag.  I know this was tagged as wishlist but I suspect that was a misclick.  This was a bug since it was the mislabeling and not addition of a new feature.
1788260,2019-08-21 20:55:10 UTC,Not sure why this is wishlist. It's a bug with existing code. Maybe it was flagged wishlist before the original code was committed to master?
1788260,2020-09-21 15:53:38 UTC,"Agreed, this is a bugfix, although it probably is worth a special announcement in the 3.4.x and 3.5.x release notes. Pushed to master, rel_3_5, and rel_3_4. Thanks, Chris and Rogan!"
1788260,2018-11-04 20:57:58 UTC,"Better later than never, here's the branch:"
1788260,2019-08-21 02:51:11 UTC,"Chris, since this is a wishlist bug, could you please add some brief release notes?"
1788263,2018-08-28 22:29:35 UTC,"Reviewed:  https://review.opencontrail.org/45688
Committed: http://github.com/Juniper/contrail-kolla-ansible/commit/78f1f1a71de4dd55a4269d7a5ba545ee438dfd51
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    contrail/queens"
1788263,2018-08-28 22:29:33 UTC,"Review in progress for https://review.opencontrail.org/45828
Submitter: Sahana Sekhar Palagrahara Chandrashekar (<email address hidden>)"
1788263,2018-08-29 01:17:54 UTC,"Reviewed:  https://review.opencontrail.org/45828
Committed: http://github.com/Juniper/contrail-kolla-ansible/commit/2f8721e45eae9c1e1323eb7c887e0c7a1981d5ac
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    contrail/ocata"
1788263,2018-08-21 18:32:13 UTC,"Review in progress for https://review.opencontrail.org/45688
Submitter: Sahana Sekhar Palagrahara Chandrashekar (<email address hidden>)"
1788275,2020-11-13 15:46:28 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1788275,2021-01-13 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1788286,2018-08-22 02:00:19 UTC,This change was made by a bot.
1788286,2018-08-22 16:53:38 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1788286,2018-08-24 06:46:41 UTC,"This is a fresh installation of Ubuntu 18.04.1
In Ubuntu 16.04.5 with the kernel linux-generic-hwe-16.04 on this equipment problems were not observed."
1788286,2018-10-24 04:17:14 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1788286,2018-10-24 19:43:33 UTC,Linux M51SE 4.18.0-8-generic #9~18.04.1-Ubuntu SMP Mon Sep 17 12:49:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
1788297,2018-12-07 17:09:47 UTC,"I agree with this. Even though I know better, I always click ""Manage"" in Item Status when wanting to add an alert before remembering I can't do it there."
1788299,2020-12-21 18:07:22 UTC,We recently had a library express a desire to view item alerts on the In-House Use page.
1788299,2018-08-29 20:34:28 UTC,"Thanks, Garry and Remington!"
1788299,2018-08-28 19:33:58 UTC,I was not able to duplicate this in current master or in 3.0.9.
1788299,2018-08-28 23:54:46 UTC,Thanks Jane for the added info.  I was indeed testing on an item that had an alert message not a copy alert.  Sorry for the confusion.
1788299,2018-08-28 22:16:08 UTC,"Thanks for digging in to this, Garry.  I'm not surprised that you aren't duplicating this in 3.0.9, since the big copy alerts change was released in 3.1 (https://bugs.launchpad.net/evergreen/+bug/1676608).  Not being able to duplicate this in current master surprises me, though."
1788299,2018-08-29 18:17:29 UTC,We've done some work related to this (and overlapping with bug #1779222). We'll try to share some code soon.
1788315,2018-09-07 16:00:02 UTC,I've added the subiquity project which is the installer for 18.04.
1788315,2018-09-07 15:14:42 UTC,"P.S. Hi. I know I am not the only one affected by this bug, since google-ing it shows otherwise. And I found a work-around solution:"
1788315,2019-02-21 15:01:09 UTC,"I'm going to close this bug on the grounds that there were fixes that _may_ have helped in the latest point releases. If not, please open new bugs."
1788315,2018-08-22 21:52:12 UTC,"More info:
The installer started fine.
One i enter all the info on the GUI (username etc.) it pop up to report the bug.
The only option i did have was to view log (which i typed here) and to reboot the machine (vm)."
1788315,2018-08-22 21:24:25 UTC,"Yes i did a install of ubuntu server installer inside a KVM running on RouterOS.
After I start the installer again from scratch everything did work fine."
1788315,2018-08-22 14:23:38 UTC,"Hi,"
1788315,2018-08-22 09:31:17 UTC,"I'm sure smosre/rharper will know better what to ask for, but aren't there more logs associated that should be added to the report?"
1788315,2018-08-25 14:57:13 UTC,"The installation process for ubuntu server 18.04 gives me error. ""curtin block meta customer"". curtin command block meta. remove previous storage devices."
1788321,2018-09-30 00:14:59 UTC,My perspective suggests that this bug might have came from upsteam.
1788321,2020-09-14 08:03:06 UTC,Good News!
1788321,2020-08-12 08:50:31 UTC,"Hello,"
1788321,2020-04-28 03:33:26 UTC,Fixed my problem.
1788321,2020-04-24 04:23:17 UTC,"Just did a fresh install of 20.04 as a Proxmox VM and see this ""invalid argument"" in the start up messages and syslog. Trying to start it manually also fails. Tried recreating it, also failed."
1788321,2020-03-12 16:07:52 UTC,Getting the same error on old bare metal:
1788321,2019-02-27 02:23:14 UTC,"ubuntu 16.04, hit the same issue as this. swapon -v shows these:"
1788321,2018-10-26 13:29:25 UTC,"Like John Shipp, we are on Debian 9.4 32-bit (on VMware) and still have this issue on the latest kernel: 4.9.0-8-686-pae #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08)"
1788321,2018-10-04 08:01:00 UTC,Seems fixed for
1788321,2018-10-03 08:04:11 UTC,"fixed for me as well, thanks
Linux svn-desktop16 4.15.0-36-generic #39~16.04.1-Ubuntu SMP Tue Sep 25 09:00:45 UTC 2018 i686 i686 i686 GNU/Linux
$ free
              total        used        free      shared  buff/cache   available
Mem:        1022124      244104      112896       14520      665124      594404
Swap:       1047548        4616     1042932"
1788321,2018-09-28 08:17:12 UTC,I am running
1788321,2018-10-02 13:07:46 UTC,"Last kernel 4.15.0-36-generic #39-Ubuntu i686 fixes the issue for me.
Could you try, please?"
1788321,2018-09-17 12:51:15 UTC,"On Xenial, update to ""linux-image-4.4.0-135-generic 4.4.0-135.161"" did not fix the problem, but I noticed a message, that might be related to the issue:"
1788321,2018-09-05 11:01:16 UTC,Swapon is not working with swap file or swap partion. Mkswap with Kernel 4.15.0-30-gernic and swapon with Kernel 4.15.0-33-gernic is even not working.
1788321,2018-08-22 04:23:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1788321,2018-09-03 09:06:01 UTC,"This is the failing ""swapon"" sequence from updated Xenial i386 on vmware:"
1788321,2018-08-31 21:56:58 UTC,">> Do you also have to re-run mkswap when switching back to the older, working kernel, or does simply using the other kernel let you run swapon on the same file that doesn't work with the newer kernel?
"
1788321,2018-08-31 19:36:28 UTC,Also what does getconf PAGESIZE say under the broken kernel?
1788321,2018-08-31 19:31:40 UTC,"This doesn't happen on amd64.  Do you also have to re-run mkswap when switching back to the older, working kernel, or does simply using the other kernel let you run swapon on the same file that doesn't work with the newer kernel?"
1788321,2018-08-24 13:27:02 UTC,"Charlie,
as regards me:"
1788321,2018-08-24 12:36:13 UTC,the changes that broke this seem to be related to the L1 terminal patches.  i've linked the CVE numbers.  maybe that will get us some help.
1788321,2018-08-24 12:32:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788321,2018-08-24 12:22:18 UTC,i'm running debian.
1788321,2018-08-24 06:57:19 UTC,"Hi charlie,
thank you for your answer.
I confirm I'm using VMware me too.
Last kernel 4.15.0-33 doesn't fix the issue.
Last kernel not affected is 4.15.0-30."
1788321,2018-08-23 17:19:06 UTC,are you running under vmware?  i am hitting this with vmware workstation.
1788321,2018-09-17 12:57:01 UTC,"Maybe this is the fix:
x86/speculation/l1tf: fix overflow on l1tf_pfn_limit() on 32bit
https://lkml.org/lkml/2018/8/20/222"
1788322,2020-04-10 01:34:56 UTC,"@cpollock: I don't think this is invalid. This is a very poor error message which gives no pointers about why, and causes logspam.  It was only because of your last update that I realised that I had incorrect file permissions also."
1788322,2018-08-29 22:28:10 UTC,Please mark this bug as invalid. After several replies to a question at LinuxQuestions.org on this I discovered that the permissions for /var/log/cron.log were incorrect. I corrected that problem this afternoon and the reported issue has been corrected.
1788322,2018-08-25 13:30:12 UTC,apport information
1788322,2018-08-25 13:30:11 UTC,apport information
1788322,2018-08-29 01:57:30 UTC,I've updated to version
1788323,2018-08-22 02:26:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/594769"
1788323,2018-09-18 07:58:42 UTC,"Reviewed:  https://review.openstack.org/594769
Committed: https://git.openstack.org/cgit/openstack/python-glanceclient/commit/?id=8fd7e8c664e82d805dc4a12534b3d7e3fcaac606
Submitter: Zuul
Branch:    master"
1788323,2018-10-25 15:05:28 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/613350"
1788323,2018-10-31 17:58:47 UTC,"Reviewed:  https://review.openstack.org/613350
Committed: https://git.openstack.org/cgit/openstack/python-glanceclient/commit/?id=395d0f157bed9dbc4e6e125f21e8b1879c26ccdb
Submitter: Zuul
Branch:    stable/rocky"
1788323,2018-10-31 21:57:38 UTC,This issue was fixed in the openstack/python-glanceclient 2.13.0 release.
1788323,2018-11-01 13:29:13 UTC,This issue was fixed in the openstack/python-glanceclient 2.14.0 release.
1788324,2018-08-22 04:52:51 UTC,This is a question for the user forum http://forum.kicad.info
1788324,2018-08-22 12:16:44 UTC,"Ok. But, actually it is an issue."
1788324,2018-08-22 15:39:38 UTC,"OK, I've edited the question to a wishlist for creating automatically hatched fills.  Note that in KLC, they just draw the lines."
1788324,2018-09-01 22:57:30 UTC,This is probably a duplicate of https://bugs.launchpad.net/kicad/+bug/594023
1788332,2018-08-22 05:00:08 UTC,"I'm beginning to wonder if this is really a bug, or I just don't 'get' (comprehend) what the icons for vertical & horizontal change are supposed to represent (which could still be the bug?!)."
1788336,2020-12-22 14:47:00 UTC,"I think this is the issue I have run into as well with a Focal VM. Installing nfs-kernel-server works (although it shows some ""Dependency failed"" messages) and then the service does not work, it is not an ideal experience having to find an explanation for why online. The linux-image-kvm package provides wireguard-modules and zfs-modules, why does it not work the same way for NFS so that the missing support in linux-image-kvm is detected by apt when installing?"
1788336,2019-07-30 07:44:56 UTC,"Package removed from the test, the config won't be enabled unless we got customer request for this"
1788336,2018-11-05 12:23:58 UTC,Aug 22 04:15:58 zeppo mount[3580]: mount: unknown filesystem type 'nfsd'
1788336,2018-11-29 07:45:28 UTC,"As we have this package removed from the ramfs / vfat test:
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=19f9ddeffdaec1cd491921872827f3c0b0d67711"
1788336,2018-11-29 07:38:02 UTC,For the Xenial generic kernel:
1788336,2018-12-05 07:18:17 UTC,"Re-open the task in ubuntu-kernel-test, as this is still affecting the kernel SRU."
1788349,2018-09-05 22:12:48 UTC,I'm running 18.04.1LTS updated from 16.04.5LTS. Saw this today while updating
1788349,2018-09-06 07:52:31 UTC,same again for me whilst sudo apt upgrade today 6 Sep 2018
1788349,2020-12-08 17:23:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788353,2020-02-21 16:34:16 UTC,Are you still facing this issue?
1788353,2020-03-09 16:00:19 UTC,based on the date the bug was filled (1.5 years ago) this could have been already fixed already or not occurring anymore. Therefore I'll mark this as Incomplete until the reporter confirms it's still relevant.
1788353,2020-05-09 04:17:32 UTC,[Expired for tempest because there has been no activity for 60 days.]
1788358,2018-12-09 04:17:58 UTC,hi bruh
1788358,2018-12-09 10:28:35 UTC,"Unfortunately I switched to sassc meanwhile, so I can't investigate it
further, but I never directly issued any ""gem update"" though - I
(naively) assumed gems would automatically update with the rest of the
system - Doh!
Thanks anyway and merry Christmas!"
1788359,2018-09-15 08:21:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788359,2019-02-07 11:08:38 UTC,I also see this when start Chrome/Chromium in the Kubuntu 18.04
1788364,2018-09-24 17:51:53 UTC,"Hi there,"
1788364,2018-09-23 19:09:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788364,2018-08-23 08:07:18 UTC,"Hello again, some updates on this issue."
1788367,2018-08-22 09:28:12 UTC,Comment from a Nova dev:
1788367,2018-08-22 09:28:28 UTC,Original bug: https://bugzilla.redhat.com/show_bug.cgi?id=1429457
1788367,2020-01-07 16:42:06 UTC,"Change abandoned by Radomir Dopieralski (<email address hidden>) on branch: master
Review: https://review.opendev.org/666394
Reason: Since there is no way to get a consistent behavior, I'm abandoning this."
1788370,2018-08-22 10:08:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1788375,2018-08-22 12:16:34 UTC,VaultKeyManager.delete() and VaultKeyManager.list() also needs fixing.
1788375,2018-10-11 19:18:01 UTC,This bug was fixed in the package python-castellan - 0.19.0-0ubuntu2
1788377,2019-07-22 04:02:06 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1788377,2018-08-23 08:13:09 UTC,Sounds a little like bug 1783363 (was).
1788377,2018-08-23 05:13:17 UTC,apport information
1788377,2018-08-23 05:13:19 UTC,apport information
1788377,2018-08-23 05:13:18 UTC,apport information
1788377,2018-08-23 01:45:11 UTC,"I think that's called the ""Activities Overview""."
1788377,2018-08-23 05:13:20 UTC,apport information
1788378,2018-08-22 10:29:43 UTC,I do like Ubuntu Mate and I have installed the 'mutiny desktop but if I cannot get my scanner working it is no good for me. Maybe there is a better scanning apt I can install but easy scan is the only one I can find in the software downloads.
1788378,2019-12-05 23:02:32 UTC,"The issue was resolved with ticket:
https://gitlab.gnome.org/GNOME/simple-scan/issues/130"
1788381,2020-03-19 11:49:00 UTC,Closing because NOT A BUG.
1788387,2018-10-15 03:36:27 UTC,Find the first bad/good -rc kernel to minimize the bisect range.
1788387,2018-08-22 12:12:25 UTC,apport information
1788387,2018-10-14 04:36:07 UTC,"I have seemingly similar problem on Intel NUC DE3815TYKHE (ntel Atom CPU E3815). On 4.15.*, it takes more than 5 minutes to unpack the initramfs (below is an example on 4.15.0-36). With the acpi=noirq, the kernel boots as usual."
1788387,2018-09-06 02:54:13 UTC,"Hi, yes I can try."
1788387,2018-08-30 02:04:00 UTC,Would it be possible for you to do a kernel bisection?
1788387,2018-08-23 04:15:17 UTC,I've tested the kernel 4.18.3
1788387,2018-08-22 16:23:35 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].
1788387,2018-08-22 12:12:23 UTC,apport information
1788387,2018-08-22 12:12:10 UTC,apport information
1788387,2018-08-22 12:12:18 UTC,apport information
1788387,2018-08-22 12:12:21 UTC,apport information
1788387,2018-08-22 12:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788387,2018-08-22 12:12:08 UTC,apport information
1788387,2018-08-22 12:12:11 UTC,apport information
1788387,2018-08-22 12:12:07 UTC,apport information
1788387,2018-08-22 12:12:14 UTC,apport information
1788387,2018-08-22 12:12:15 UTC,apport information
1788387,2018-08-22 12:12:12 UTC,apport information
1788387,2018-08-22 12:12:16 UTC,apport information
1788389,2018-09-17 14:35:45 UTC,I'd also say it's worse then mildly annoying. If you give someone a link to a particular section (a more or less daily occurrence on IRC/ask.openstack) then the exact information you want them to look at will be hidden by the banner.
1788389,2018-08-31 17:14:13 UTC,"The banner is actually harmful for projects that use cycle-with-intermediary releases. For example, today, right after the rocky release, the banner is mildly inconvenient. However, as soon as a new release it tagged, it becomes incorrect and refers people to older releases. I would like a way to disable the banner via a setting in conf.py so that I can control it on a per-project basis."
1788389,2018-08-31 07:58:33 UTC,"I consider this more than just mildly annoying. It may be slightly helpful for newcomers, but it just takes away valuable screen space for regular users."
1788389,2018-09-04 11:52:04 UTC,"Not sure whether something has changed, but I cannot remove the banner by clicking on the top right ""x"" anymore now."
1788401,2018-08-24 01:48:25 UTC,I just saw this again: http://ci.jujucharms.com/job/github-merge-juju/985/testReport/
1788401,2018-08-31 07:42:46 UTC,trialing fix against develop: https://github.com/juju/juju/pull/9146
1788401,2018-09-10 04:43:41 UTC,"Added local charm archive size check to ensure that we have a valid charm setup before we start the test.
PR against develop: https://github.com/juju/juju/pull/9175"
1788401,2018-09-17 09:37:27 UTC,Still seems to be happening as per http://ci.jujucharms.com/job/github-merge-juju/1146/consoleFull
1788401,2018-10-23 13:05:31 UTC,http://ci.jujucharms.com/job/make-check-juju/869/consoleFull
1788401,2019-10-31 03:59:18 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1788401,2018-09-06 03:54:45 UTC,Seen again: http://ci.jujucharms.com/job/github-merge-juju/1087/testReport/junit/github/com_juju_juju_api/TestAll/
1788405,2018-08-22 14:06:23 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1788407,2018-08-22 14:17:26 UTC,"Thanks! I wonder if we can make this broader to ignore any RFC822-style ""headers"" at the end of the commit message."
1788416,2020-04-15 13:09:02 UTC,"Here are the message mentioned above in a nicer format, I also reordered the values so that it's easily comparable:"
1788416,2020-12-17 12:54:07 UTC,This issue was fixed in the openstack/tempest 25.0.1 release.
1788416,2020-05-28 14:39:15 UTC,"Reviewed:  https://review.opendev.org/704293
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=f4b5df6d1dd5e562caa672a67106be2e29ab4cf6
Submitter: Zuul
Branch:    master"
1788416,2020-01-27 10:11:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/704293"
1788420,2019-08-21 07:20:51 UTC,"That was discussed on IRC #debian-gnome, the update is currently only in experimental because review of copyright/non free files included needs to be done before uploading to unstable"
1788420,2019-01-11 04:33:08 UTC,"netpbm-10.84.03-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report."
1788420,2019-01-11 02:58:50 UTC,"netpbm-10.84.03-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report."
1788420,2018-11-27 05:42:40 UTC,"netpbm-10.84.03-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-e58b5856ca"
1788420,2018-09-29 11:05:20 UTC,New versions uploaded on SourceForge. Please update!
1788420,2018-11-27 04:27:33 UTC,"netpbm-10.84.03-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-59216298b2"
1788420,2018-11-26 07:16:10 UTC,netpbm-10.84.03-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-59216298b2
1788420,2018-11-26 07:16:01 UTC,netpbm-10.84.03-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8069447986
1788420,2018-11-26 07:15:53 UTC,netpbm-10.84.03-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-e58b5856ca
1788420,2018-11-27 05:13:39 UTC,"netpbm-10.84.03-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-8069447986"
1788429,2019-06-19 01:57:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788429,2020-03-19 06:38:30 UTC,The number of reports of this bug are very low still. And none after 3.34 so let's remove 'focal' from the list.
1788429,2020-05-12 07:06:38 UTC,Maybe we should track https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2757 instead...
1788431,2018-08-23 01:53:25 UTC,This is a very different stack trace to bug 1723615. Not a duplicate.
1788431,2020-11-16 08:41:46 UTC,Zero crashes after 18.04 so consider it fixed.
1788438,2018-08-24 23:32:17 UTC,"It actually defaults to zoom-to-fit but as there's only the Reference and Value texts on creation, that's pretty zoomed in."
1788439,2018-08-22 16:36:55 UTC,"GIMP 2.10 isn't included in Ubuntu 18.04 and is therefore unsupported. However, by the output from the bug report, you're using 18.10 (for testing purposes, I'm guessing)? If so, I recommend editing your bug description."
1788439,2018-08-22 18:40:29 UTC,"Sorry, I error'ed and have corrected the bug description to read 18.10"
1788439,2019-08-20 01:51:26 UTC,"Thank you for reporting this bug. Since this was reported against a version of gimp included in a now end-of-life version of Ubuntu, please try to reproduce this bug using a more recent version of Ubuntu, and comment on this bug as to whether or not this bug still occurs."
1788439,2019-10-19 04:17:43 UTC,[Expired for gimp (Ubuntu) because there has been no activity for 60 days.]
1788440,2018-08-28 07:31:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788440,2018-08-27 18:46:46 UTC,Received the following response from A Raghuram (araghuramindia) to the question (#672572) that I posed:
1788444,2019-10-05 18:51:43 UTC,"The similar approach (universal type of copy alert) would be also needed when creating copy alert at checkin or checkout, renewal screen etc."
1788444,2018-08-22 17:09:50 UTC,Here is the gif
1788456,2019-01-11 12:07:55 UTC,"$ glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVS 3100M/PCIe/SSE2
OpenGL version string: 3.3.0 NVIDIA 340.107
OpenGL shading language version string: 3.30 NVIDIA via Cg compiler"
1788456,2019-05-19 04:17:30 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1788456,2019-03-19 08:54:53 UTC,"@sethh sorry for the delay.
i have tested today with version
5.1.0-unknown-0943c17~94~ubuntu18.10.1"
1788456,2019-02-28 14:38:17 UTC,@Stefan-  Would you try this again with the latest nightly build?  We may have addressed this issue with some new shader commits.
1788456,2019-01-10 19:02:40 UTC,Which nvidia driver version are you using?
1788456,2019-03-19 12:27:00 UTC,Thank you for the update.  We'll have to think on this some more.
1788456,2019-01-10 05:58:00 UTC,@Stefan- Does this still happen for you?  I know that there were some shader updates since the report.
1788456,2018-10-01 08:12:31 UTC,added the full output as file (was to long for message content)
1788456,2018-10-03 19:41:14 UTC,"When we can't load the shader, we should disable the menu options"
1788456,2019-01-10 18:49:26 UTC,i have updated my system in the meantime to Kubuntu 18.10.
1788456,2018-10-03 19:42:22 UTC,@stefan-
1788456,2018-10-03 20:06:17 UTC,"i would love to test the nouveau - but last time i tried switching to it i got 600x800pixel and 'software emulated rendering' or something like this... no way to switch options - so there seems to be something off with the my system in this regard...
(so no way to really test this)"
1788456,2018-10-01 03:06:10 UTC,Can you please attach the output of the command
1788459,2018-09-06 18:50:56 UTC,"Can you simplify the configuration needed to reproduce this bug? For example, does it happen when using gssapi authentication with apache, without the NFSv4 bit?"
1788459,2018-09-06 18:51:56 UTC,Or can you elaborate a bit more how you have this setup?
1788470,2019-03-22 03:46:52 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1788470,2018-11-06 06:01:12 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1788470,2018-10-27 18:51:04 UTC,"Just to let you know...when installing openstack on top of Ubuntu 18.10 it's no longer necessary (nor allowed) to add the cloud-archive:rocky (it's only supported for bionic)
Openstack install proceeds with no issues using the repositories included in the opsys...until we stunble on the issue of the need for nova-console-auth
When using the cloud-archive it was easy to bypass the issue just installing the nova-console-auth but on 18.10 using the repositories included with the opsys this package is not available and therefore there's no clear workarround until de fix for not needing nova-console-auth is released.
I guess the number of people stumbling on this will grow as they try ubuntu 18.10
Best regards."
1788470,2018-10-23 03:03:14 UTC,"Reviewed:  https://review.openstack.org/610673
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c69c1fdef4c868fb7b3775285d44d4c54358af4
Submitter: Zuul
Branch:    stable/rocky"
1788470,2018-10-15 23:54:51 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/607037
Reason: Instead of un-deprecating, we fixed the code to actually make nova-consoleauth optional:"
1788470,2018-10-15 17:41:59 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: master
Review: https://review.openstack.org/605250
Reason: Instead of un-deprecating, we fixed the code to actually make nova-consoleauth optional:"
1788470,2018-10-01 20:08:25 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/607037"
1788470,2018-08-24 17:24:41 UTC,This issue was fixed in the openstack/nova 18.0.0.0rc3 release candidate.
1788470,2018-08-24 16:18:30 UTC,"Reviewed:  https://review.openstack.org/595890
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=212a2c5fee389b413b69050d93a06831326b9192
Submitter: Zuul
Branch:    stable/rocky"
1788470,2018-08-24 07:57:33 UTC,"Reviewed:  https://review.openstack.org/595455
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f01f4ff88de571218a36ba7c4e998296a7b52a4
Submitter: Zuul
Branch:    master"
1788470,2018-08-23 20:55:27 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/595890"
1788470,2018-08-23 04:57:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/595455"
1788470,2018-10-15 17:38:49 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/610673"
1788470,2018-10-15 17:36:36 UTC,"Reviewed:  https://review.openstack.org/607068
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b49209cc29f5ccd529b8074b68be074c5a2f742f
Submitter: Zuul
Branch:    master"
1788473,2019-01-29 16:33:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788474,2018-11-09 17:27:38 UTC,"As per bug 1228378 - add ""Add to List"" functionality to bucket actions menu on the search results screen rather than requiring user to open the bucket first."
1788474,2020-10-07 20:32:27 UTC,Bumping as the steps to add basket contents to an existing list are still cumbersome and confusing.
1788479,2018-08-26 21:02:45 UTC,"I have looked into the issue, and I think we should not fix it."
1788481,2020-01-04 02:43:00 UTC,"see Bug #1826209, seems same issue."
1788481,2020-01-03 22:29:06 UTC,"Thinking perhaps my minimal packageset might be excluding something, i just installed lubuntu-desktop.  i start the container, launch a bare vncserver, then ""lxsession -s Lubuntu"", then gnucash.  Preferences still cannot be changed."
1788481,2019-12-31 23:00:31 UTC,"i am running gnucash(2.6.12) in a xenial container.  gnucash works by and large, but preferences cannot be changed.  i just found this, and just installed dbus-x11.  it installed alone, didn't pull in anything additional.  i stopped and started the container and fired up gnucash.  preferences still cannot be changed."
1788481,2019-12-31 23:00:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788485,2018-08-30 22:03:20 UTC,A patch is available at the tip of the user/gmcharlt/lp1788485_improve_basket_action_redirects branch:
1788485,2018-09-20 14:56:15 UTC,Thank you Galen! Add to existing list is working as expected now. I am also able to perform multiple actions in the basket and then remove the titles without the strange behavior I previously reported.
1788485,2020-02-10 16:15:52 UTC,"Kathy's feedback indicates this needs a little more work so that there isn't a ""Return"" button that goes nowhere, so I'm removing the pull request."
1788487,2018-08-28 15:41:46 UTC,"You should be able to specifically set the datasource in /etc/cloud/cloud.cfg.d/*.cfg
with:
 datasource_list: ['OpenStack', 'None']"
1788487,2018-08-28 19:47:22 UTC,"Let me try to clarify the original issue. Commit https://git.launchpad.net/cloud-init/commit/?id=1efa8a0a030794cec68197100f31a856d0d264ab introduced a mechanism where, for performance reasons, the OpenStack metadata service is never queried if the host platform does not _look like_ OpenStack from a DMI information check. This check happens even when `datasource_list` explicitly contains `OpenStack`."
1788487,2018-08-29 20:49:51 UTC,"@Mark,"
1788487,2018-09-02 20:51:10 UTC,"From our experiments, doing 'b' is currently not possible. The first thing the OpenStack datasource does is check the DMI data [1] and if it does not match an expected platform, the metadata service is never probed. This leaves cloud-init without any valid data source."
1788487,2018-09-06 20:55:05 UTC,"@Mark,"
1788487,2018-11-26 19:05:45 UTC,I appear to be running into the same issue described by Mark. Platform is OpenStack using VMware (VC + ESXi). I first noticed this after upgrading a template from Ubuntu 16.04.2 to 16.04.5 which bumped cloud-init from 17.2-35 to 18.4-0. I got the EC2 warning as well :)
1788487,2018-11-27 15:53:21 UTC,"@Scott,"
1788487,2019-03-12 16:54:46 UTC,FYI still seeing this on 18.5-21-g8ee294d5-0ubuntu1~16.04.1. Does anyone have this working with just OpenStack and None datasources?
1788487,2019-10-01 14:39:30 UTC,Is this not the same issue worked around in the fix for https://bugs.launchpad.net/cloud-init/+bug/1669875 ?
1788488,2019-09-18 20:56:41 UTC,"One possible solution is to reset the select after ""Add Basket to Bucket"" is triggered:"
1788488,2019-09-18 20:39:55 UTC,We were testing this on 3.3.  Basically you have to stay away from the Go button after using this feature.  Even if you successfully add the basket to a bucket the Go button generates an error.
1788495,2019-02-08 20:19:47 UTC,@Jeff-
1788495,2019-02-15 06:15:06 UTC,Hmm... That footprint properties looks new.  But that's a good opportunity to track down what went wrong.  I think it's fixed now.
1788495,2019-02-15 04:22:27 UTC,"This FootprintProperties dialog is also MUCH better.   There is still a glitch in the 1st column however.  Two issues:
a) The initial width is wrong as you can see.
b) The column sizing works until you release the drag, then it snaps back to this width."
1788495,2019-02-15 04:16:48 UTC,"@Seth:  things are looking BETTER!  Thank you so much.  See this
dialog by comparison, is wonderful.  I can actually pick a footprint now.  (I literally could not choose a footprint before.)"
1788495,2019-02-13 06:04:49 UTC,And one more fix in this series.  This time for the library columns.  But leaving the bug open to address the remaining abstractions for WX_GRID
1788495,2019-02-13 05:59:21 UTC,"Fixed in revision a74aa3850a394d5bdd18bf4d4b26a8681bb09702
https://git.launchpad.net/kicad/patch/?id=a74aa3850a394d5bdd18bf4d4b26a8681bb09702"
1788495,2019-02-10 17:04:18 UTC,"@Seth, no problem pushing this to v6.  I wonder if this problem still exists on wx3.1.  It may have already been addressed."
1788495,2019-02-09 23:38:07 UTC,"@Wayne-  That's the correct way although I don't think that there's a good method for automatic sizing yet.  I've pushed an abstraction up to WX_GRID that allows us to extract the actual visible information from the grid and use that a developer can then use set the widths.  It doesn't work correctly for grids that have non-textual information in them (checkboxes, drop-downs, etc), so there's still some work to be done to abstract a full method for these, maybe with an overloaded routine for cells.  But I think that that is better suited to 6.0 development atm."
1788495,2019-02-09 20:07:24 UTC,"@Seth, I took a quick look at this patch.  Is there any way we could unify this in our GRID_TRICKS object or some other base object derived from wxGrid?  The problem is if we us wxGrid in yet another window or dialog, the developer have to know that the title column sizing is broken or we will get yet another bug report for that wxGrid.  If this is fixed in an object derived from wxGrid, we get this fix everywhere we use the derived object."
1788495,2019-02-09 04:04:02 UTC,"Fixed in revision 76600e343616ba016eefef5ab859bd7301effdf1
https://git.launchpad.net/kicad/patch/?id=76600e343616ba016eefef5ab859bd7301effdf1"
1788495,2019-02-08 19:37:40 UTC,Ahh... we're talking about different columns.  Seth and Dick are talking about the column *within* the tree; I was talking about the column that *holds* the tree.
1788495,2019-02-09 04:13:52 UTC,"@Dick-  I've added some logic to re-space the columns based on the actual data and/or headers in a few of the grids.  I'll have a look around for others that might be broken in an accessibility view.  However, your help in this would be appreciated as you run with large fonts on a regular basis."
1788495,2019-02-08 14:24:11 UTC,@Jeff-
1788495,2019-02-08 16:03:27 UTC,"@Seth.  Thanks, you have a nice touch.  Yes very frustrating, since I spent time on everyone of the original dialogs, if not outright wrote them completely, and now that investment is poof, and the software is not friggin' useable.  So you got that right my friend."
1788495,2018-08-24 10:58:49 UTC,"Fixed in revision 8957008c2a3262ee5ea16e7e303d474e5bb2cbe5
https://git.launchpad.net/kicad/patch/?id=8957008c2a3262ee5ea16e7e303d474e5bb2cbe5"
1788495,2018-09-13 20:28:04 UTC,"Application: kicad
Version: (6.0.0-rc1-dev-541-ge7a0b3d5d-dirty), release build
Libraries:
    wxWidgets 3.1.1
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-23-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.1.1 (wchar_t,STL containers) GTK+ 2.24
    Boost: 1.65.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011"
1788495,2019-02-07 18:49:19 UTC,"This would not be so bad, except that I spent a lot of time
making the original dialogs functional."
1788495,2019-02-07 19:16:12 UTC,"Just so you know, these are not improvements."
1788495,2019-02-07 22:42:30 UTC,"The left-most column is resized by dragging the splitter bar.  (Although in your screen-shot it's wider than the default, so you must have already figured that out?)"
1788495,2019-02-07 22:24:26 UTC,There are 3 things wrong here:
1788495,2019-02-07 23:12:20 UTC,"@Jeff-  On linux, there is no splitter, fyi.  I assume it shows up on the Mac?"
1788495,2019-02-07 23:28:39 UTC,"@Seth, interesting.  Is the same true in the Symbol Editor (ie: no splitter on GTK)?"
1788495,2018-08-23 11:46:06 UTC,"Hi Dick, could you try out the attached patch?  Thanks!"
1788495,2019-02-08 00:27:05 UTC,"@Jeff-  Yes, same look.  Without the heads in the columns, we cannot resize them.  There is a splitter between the panel and the main sheet but nothing to drag between the columns."
1788495,2019-02-08 11:59:27 UTC,"@Seth, I tried out the patch and it is (marginally) more confusing/cluttered with the header so I think we should conditionally compile it."
1788495,2019-02-07 22:45:41 UTC,Hi Dick-
1788497,2019-11-28 14:05:00 UTC,tests work as designed for some time now
1788499,2018-09-05 08:42:19 UTC,4.15.0-30-generic #32-Ubuntu SMP
1788499,2018-08-31 09:16:27 UTC,"Hi,"
1788499,2018-08-30 15:02:14 UTC,"I am going to mark this incomplete and ask the reporter to please try the older kernel as described in comment 3. Once you try that please respond back here and move the bug back to ""New""."
1788499,2018-08-29 08:03:13 UTC,"@Andreas, well the 4.15.0-32 kernel was the security update to handle Foreshadow/L1TF. To mitigate that CPU bug there had been substantial changes to how non-present pages are represented in the page tables. For suspend/resume many parts have to play together. With Xen, there is the hypervisor which is a kernel on its own (and I would guess it also hooks into some BIOS functions visible to guests). The hypervisor loads and runs the kernel for the dom0 guest. This is the linux kernel and dom0 is a paravirtualized guest with special privileges."
1788499,2018-08-28 18:25:48 UTC,"@smb, do you have any idea about this?"
1788499,2018-08-23 00:23:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1788503,2018-08-22 22:00:03 UTC,This change was made by a bot.
1788505,2020-10-17 21:37:32 UTC,Is there any update to this?  This also affects rocky.
1788505,2020-10-18 00:51:01 UTC,"Also, I notice that there is a new var in globals.yml in rocky that was not present in queens, 'enable_neutron_provider_networks'."
1788505,2020-10-19 10:04:08 UTC,"If you want to use provider (flat or VLAN) networks for direct attachment of instances, you will need to enable enable_neutron_provider_networks."
1788505,2020-10-19 22:26:38 UTC,What about the issue itself?  Is there any update?
1788505,2020-10-20 08:12:32 UTC,"I don't know why the bridges are not being reconfigured. I have done this myself, and I can't see any relevant code changes between queens and master."
1788518,2019-11-13 00:08:20 UTC,This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.7
1788518,2019-09-09 09:35:28 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu7.1
1788518,2019-09-09 09:28:04 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu3.4
1788518,2019-09-09 09:25:31 UTC,"The verification of the Stable Release Update for landscape-client has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1788518,2019-09-05 21:05:58 UTC,"I verified the pacakges in xenial-proposed and the logs indicated scattered start delays, as expected."
1788518,2019-08-13 20:24:35 UTC,"Hello Ryan, or anyone else affected,"
1788518,2019-03-06 09:14:51 UTC,"Hi Junien,"
1788518,2019-07-19 18:53:07 UTC,"Hello Ryan, or anyone else affected,"
1788518,2019-07-09 16:43:06 UTC,"Hello Ryan, or anyone else affected,"
1788518,2019-03-06 06:30:43 UTC,"Hi, what's the progress here ? Maintaining our own landscape-client package is painful."
1788518,2018-11-01 23:55:41 UTC,"Sorry, I should clarify this patch does NOT solve the problem over time, since the +/- 10% theoretically averages out to zero over time.  What solved our synchronized load spikes was pushing out the patched landscape-client via landscape, so the units updated themselves over an N-hour window and spread out the initial timers."
1788518,2018-11-01 23:49:00 UTC,"The attached patch spreads out the various reactor calls +/- 10% and was used as a cowboy in our use case.  It's not production ready in that it should be a configurable option (and would also need to do the initial stagger which I couldn't figure out how to do -- mine works over time, not immediately), but should be a good starting point."
1788518,2018-08-23 16:19:18 UTC,"In addition to (or instead of) spreading the initial schedule, it would be beneficial to +/- a random percentage (e.g. between -10% and +10%) to the next interval on each run. This means that instead of running at hard intervals, the runs become skewed but remain at the given interval on average. This avoids synchronisation and consistent load spikes if the initial offset results in it matching another fixed processing schedule (e.g. from a cronjob). The same applies with load distribution on the server side (if applicable)."
1788518,2019-07-25 23:13:47 UTC,"Verified bionic and disco proposed, by setting launching a couple of instances and verifying the monitors are scattered in the logs."
1788520,2018-12-08 09:37:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788521,2018-08-23 00:46:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/595380"
1788521,2018-08-23 12:49:20 UTC,Could you describe how this would be used? Why would we want to disable this behavior?
1788521,2018-08-23 23:32:37 UTC,Basically want to limit the available options to the user to make it simpler. Having arguments that are the default I'd like to not show.
1788521,2019-06-24 09:57:40 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/595380
Reason: I'm not sure if you're planning to work on this anymore or not and if so, I'm happy to help. However, for now I'm going to abandon this since it seems stalled and I'd like to clean up my review queue."
1788527,2019-12-17 21:08:47 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/674770
Reason: Let's just drop this."
1788527,2019-09-27 09:02:41 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1788527,2019-08-12 20:41:57 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1788527,2019-08-06 10:33:04 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/674770"
1788527,2019-06-18 11:17:06 UTC,Removing https://github.com/openstack/nova/blob/c7e9e667426a6d88d396a59cb40d30763a3265f9/nova/scheduler/utils.py#L944-L950 does not effect functional and unit test results. So I guess Matt is right.
1788527,2019-06-25 11:25:01 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/667334"
1788527,2019-06-24 13:33:53 UTC,"Reviewed:  https://review.opendev.org/665954
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f108d7967636ec1afceff0be386da15d70e2ca37
Submitter: Zuul
Branch:    master"
1788527,2019-06-18 11:22:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665954"
1788527,2019-05-23 15:07:22 UTC,I've reported bug 1830234 for some other inefficiencies in the InstanceGroup.get_hosts() query code.
1788527,2019-05-23 14:22:40 UTC,"Looking at this again, this statement in the description is not accurate:"
1788527,2019-07-24 17:03:56 UTC,"Reviewed:  https://review.opendev.org/667334
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0313d8143309157067aa85f7333d0d177a5b6609
Submitter: Zuul
Branch:    stable/stein"
1788528,2018-08-23 02:14:27 UTC,"StacktraceTop:
 tcache_get (tc_idx=0) at malloc.c:2943
 __GI___libc_malloc (bytes=24) at malloc.c:3050
 QArrayData::allocate (objectSize=objectSize@entry=1, alignment=alignment@entry=8, capacity=capacity@entry=0, options=..., options@entry=...) at tools/qarraydata.cpp:118
 QTypedArrayData<char>::allocate (options=..., capacity=0) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:218
 QTypedArrayData<char>::fromRawData (options=..., n=15, data=0x7f1eb1d23151 ""checkIfFinished()"") at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:244"
1788535,2020-04-06 02:27:29 UTC,"I think this happens on systems with nearby frequency options in xrandr, like 59.96 and 59.97. It looks like mutter gets confused when multiple similar frequencies are available."
1788535,2018-08-23 03:17:32 UTC,"Upstream:
https://gitlab.gnome.org/GNOME/mutter/issues/275"
1788535,2018-12-13 03:14:23 UTC,"Maybe, maybe not. I haven't verified that yet since gnome-control-center is presently the only thing reporting bogus numbers."
1788535,2018-12-12 10:59:08 UTC,seems the issue is in the backend and not the settings?
1788538,2020-02-12 01:49:50 UTC,I've re-tested this and it no longer seems to be an issue.
1788538,2020-04-12 04:17:34 UTC,[Expired for Mahara because there has been no activity for 60 days.]
1788542,2018-09-02 10:27:09 UTC,"I guess fixing the mimetypes would solve that. So it is not a problem in featherpad, it's a general problem in application handling."
1788542,2018-09-03 23:53:53 UTC,"I had some suspicions it might be something like mimetypes, So what should this bug be filed against?"
1788542,2018-09-04 00:49:20 UTC,Talked with wxl about yesterday - maybe against the Lubuntu settings/branding package
1788542,2018-09-04 02:48:39 UTC,"Sun02Sep2018 1515 < wxl:#lxqt-dev> agaida: excuse me if this is the wrong forum for this, but are you saying that https://bugs.launchpad.net/bugs/1788542 is a general lxqt bug?
Sun02Sep2018 1516 <+agaida:#lxqt-dev> it's a general problem in application and mime handling
Sun02Sep2018 1516 < wxl:#lxqt-dev> so a more system-wide problem is what you're suggesting?
Sun02Sep2018 1516 <+agaida:#lxqt-dev> not limited to LXQt - heck, you can even notice that in Windows
Sun02Sep2018 1517 < wxl:#lxqt-dev> siiiiiiiigh
Sun02Sep2018 1517 <+agaida:#lxqt-dev> :P
Sun02Sep2018 1517 <+agaida:#lxqt-dev> it's a bit complicated
Sun02Sep2018 1518 <+agaida:#lxqt-dev> some applications provide 'hints' for the applications they handle
Sun02Sep2018 1518 <+agaida:#lxqt-dev> the last installed application for a mimetype wins
Sun02Sep2018 1518 < wxl:#lxqt-dev> oh wow jeez
Sun02Sep2018 1519 <+agaida:#lxqt-dev> maybe you remember the funny bug if audacious handle nodes
Sun02Sep2018 1519 <+agaida:#lxqt-dev> and try to play a directory :D
Sun02Sep2018 1519 < wxl:#lxqt-dev> do you think it
Sun02Sep2018 1520 <+agaida:#lxqt-dev> thats a shortcoming in the freedesktop definiton for mime-types - one cant provide priorities in desktop files
Sun02Sep2018 1520 < wxl:#lxqt-dev> s something we could do through default-settings?
Sun02Sep2018 1520 < wxl:#lxqt-dev> or does that run the risk of it being overwritten by something else?
Sun02Sep2018 1520 <+agaida:#lxqt-dev> erm - dunno, where and in which order the things are read
Sun02Sep2018 1521 < wxl:#lxqt-dev> alright i'll play with it and see what i can figure out. thanks for the hints
Sun02Sep2018 1521 <+agaida:#lxqt-dev> strace xdg-open might give a clue
Sun02Sep2018 1521 < wxl:#lxqt-dev> btw has anyone ever filed a bug against freedesktop to get priorities added?
Sun02Sep2018 1522 <+agaida:#lxqt-dev> and ofcourse - ir there is a mimetype list in ~/.config - that would help too, no program will override it
Sun02Sep2018 1522 <+agaida:#lxqt-dev> best bet is to talk with tsujan, palinek or luis about
Sun02Sep2018 1522 < wxl:#lxqt-dev> ok
Sun02Sep2018 1522 < wxl:#lxqt-dev> thanks again
Sun02Sep2018 1523 <+agaida:#lxqt-dev> and i guess there was more than one rant about - i know this dumbfuck sind 2009 - was some of the first things i encountered in linux
Sun02Sep2018 1524 < wxl:#lxqt-dev> that's what i feared :)
Sun02Sep2018 1525 <+agaida:#lxqt-dev> if you think about it more - it isn't easy to solve, best would be a kind of alternatives like for applications - and even this alternatives system is only in debian and derivatives
Sun02Sep2018 1525 < wxl:#lxqt-dev> yeah
Sun02Sep2018 1526 <+agaida:#lxqt-dev> and nobody really knows it or is able to create a alternative by hand :D
Sun02Sep2018 1527 <+agaida:#lxqt-dev> nice thing about: if this follows the normal xdg handling there should be a place inbetween the upstream and user stage distributions could use
Sun02Sep2018 1528 <+agaida:#lxqt-dev> should be traceble with strace - and maybe gio documentation too
Sun02Sep2018 1530 -!- Irssi: You are now talking in #lxqt-dev
Sun02Sep2018 1530 < wxl:#lxqt-dev> well i guess that will tell me which application wins
Sun02Sep2018 1530 < wxl:#lxqt-dev>..."
1788542,2018-09-04 02:58:27 UTC,"tl;dr it's kind of a freedesktop problem because there are no priorities for mime-types, but that wouldn't be easy to fix, just like alternatives aren't (this is a debian only thing)."
1788542,2018-09-04 05:11:19 UTC,"Actually, it's falkon's fault. It flips out for whatever reason. Firefox has no such problem."
1788542,2018-09-04 05:18:03 UTC,"FWIW the chrome-error://chromewebdata/ thing also occurs with qutebrowser, another QtWebEngine browser, but it does not go to 100% usage, though it does fail to load the mail client."
1788542,2018-09-04 05:24:46 UTC,"Upstream bug report:
https://bugs.kde.org/show_bug.cgi?id=398222"
1788542,2018-09-04 19:19:41 UTC,I also get this with url that involve tel: and sftp: the same problem for falkon.
1788542,2018-09-14 18:20:18 UTC,Upstream says they can't reproduce anymore. Curious.
1788542,2018-09-14 19:12:20 UTC,Confirmed it's working fine in master if you have an email client installed. Otherwise it goes into a loop.
1788542,2018-09-14 19:21:49 UTC,"The loop makes sense: xdg-open mailto:<email address hidden> opens falkon, which then opens xdg-open mailto:<email address hidden> which opens falkon, etc."
1788546,2019-07-22 03:57:11 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1788550,2018-08-27 05:27:28 UTC,"Is running under '--race' useful at all? I'm just curious if the problem is
actually that we have a small race condition in the test. Though probably
it isn't a variable race as much as general concurrency issues. ('--race'
tells you if you're looking at a variable from 2 goroutines without
synchronization, but it won't tell you that you assume X changes before you
look at it, when actually it changes at a later time.)"
1788550,2019-07-22 07:13:11 UTC,I cannot reproduce this at all - we must have fixed it as part of other work.
1788550,2018-08-23 11:58:46 UTC,This and its relatives below are stubborn heisenbugs.
1788550,2018-08-23 12:00:10 UTC,And you are right. Something isn't playing ball in the clock implementation.
1788551,2018-08-23 07:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788551,2019-05-13 06:18:53 UTC,Build passed on non-amd64 Bionic.
1788555,2020-08-31 05:54:39 UTC,"The current code simply checks for presence of a unit with a given source charm name. So, a check for nrpe will pick up nrpe-container and nrpe-physical.
I think with this in mind, a neater way to handle this would be able to check charm configuration, regardless of how the charm was placed on a machine (via an nrpe-physical or nrpe-container charm), conditional to whether or not the machine being checked is a container or physical host."
1788556,2019-04-16 08:46:50 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/632568
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1788556,2019-03-10 17:19:16 UTC,"Reviewed:  https://review.openstack.org/632563
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bb3dbf371ca127918355524120c080a9c4bafc1f
Submitter: Zuul
Branch:    stable/ocata"
1788556,2019-01-22 22:09:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632568"
1788556,2018-09-26 14:39:16 UTC,"Reviewed:  https://review.openstack.org/604320
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ffcb22f6338ae62c56b2f6e0d531b61f33349167
Submitter: Zuul
Branch:    stable/rocky"
1788556,2019-01-22 21:44:57 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/632563"
1788556,2018-09-25 14:11:48 UTC,"Reviewed:  https://review.openstack.org/604321
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=04b7f80f999c0fec456f5e905ce9407ab9ec5261
Submitter: Zuul
Branch:    stable/pike"
1788556,2018-09-21 09:57:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/604319"
1788556,2018-09-21 09:58:14 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/604321"
1788556,2018-09-21 09:57:46 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604320"
1788556,2018-09-21 09:20:48 UTC,"Reviewed:  https://review.openstack.org/595235
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8a3ff8a19ec39630d24b71cec86740b6b9f16bbe
Submitter: Zuul
Branch:    master"
1788556,2018-08-31 06:48:32 UTC,"The problem is that the bigger the size of the file the more chances to hit this bug and I'm afraid the situation can be worse if we start to retry and have more ""incomplete entries"".
From the top of my head, the only solution is to guarantee the atomicity in the file operations( dnsmasq writing and dhcp agent reading) on the same file is the main problem."
1788556,2018-08-30 20:59:59 UTC,"Yes, it could be that there are items missed, I don't think it's fatal for the dhcp-agent.  The only change I could think of to get past this is to trigger the retry code when we encounter a lease that's invalid.  For example:"
1788556,2018-09-25 03:33:02 UTC,"Reviewed:  https://review.openstack.org/604319
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=011d0fbf7c085f9f9f24bac67cf74b05ed91bdda
Submitter: Zuul
Branch:    stable/queens"
1788556,2018-08-29 11:21:51 UTC,"@brian-haley Although we are ignoring lines with an incorrect number of fields with the partial fix proposed, we are also likely to miss the entire trailing section of the file or to have truncated entries in the client_id field."
1788560,2018-08-23 13:12:33 UTC,Moving to the appropriate project
1788560,2020-08-18 05:27:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1773859, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1788561,2018-08-23 08:53:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/595548"
1788561,2019-07-13 22:49:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670707"
1788561,2019-07-24 07:05:19 UTC,"Reviewed:  https://review.opendev.org/670707
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=bd5be763cac31fee87a1b47e83a23d7674666595
Submitter: Zuul
Branch:    master"
1788561,2019-10-07 14:24:11 UTC,This issue was fixed in the openstack/tempest 22.0.0 release.
1788562,2018-08-23 08:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788563,2018-10-01 16:02:51 UTC,This bug was fixed in the package linux - 3.13.0-160.210
1788563,2018-10-01 16:02:04 UTC,This bug was fixed in the package linux - 4.4.0-137.163
1788563,2018-09-21 06:47:36 UTC,"On 2018-09-20 15:38:55, alex wrote:

> Do you have any ETA for Xenial fixed release ?
"
1788563,2018-09-20 15:38:55 UTC,Do you have any ETA for Xenial fixed release ?
1788563,2018-09-17 14:44:31 UTC,I just tried on Bionic with proposed kernel. It is working too!
1788563,2018-09-14 08:56:35 UTC,proposed kernel for trusty still resolves this like test-kernel from #7
1788563,2018-09-14 14:58:02 UTC,I've changed the tag from verification-needed-trusty to verified-done-trusty based on comment 15. Thanks for the testing!
1788563,2018-10-01 17:15:35 UTC,This bug was fixed in the package linux - 4.15.0-36.39
1788563,2018-09-14 06:06:04 UTC,"I don't have a trusty install to test, but #10 confirms that the test kernel from #7 resolved it for trusty."
1788563,2018-09-14 17:03:19 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1788563,2018-09-12 15:31:04 UTC,"It is solved with proposed kernel on Xenial, tag updated"
1788563,2018-08-24 01:00:06 UTC,This change was made by a bot.
1788563,2018-09-06 19:00:54 UTC,It's possible this issue may have been addressed by upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4
1788563,2018-09-06 19:10:16 UTC,"Also, there was an off-by-one error in the calculation, that was addressed upstream in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0a182f875689647b014bc01d36b340217792852 ."
1788563,2018-09-07 08:11:34 UTC,"Same problem here on my Xenial system with intel-microcode 3.20180807a.0ubuntu0.16.04.1 and linux-image-4.4.0-134-generic 4.4.0-134.160, with an Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz.
L1TF: System has more than MAX_PA/2 memory. L1TF mitigation not effective."
1788563,2018-09-07 18:01:32 UTC,"I built a Bionic test kernel with commits 9df9516, b0a182f8 and cc51e542. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788563/bionic"
1788563,2018-09-13 11:03:30 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1788563,2018-09-09 04:49:15 UTC,"Yes, the bionic test kernel resolves this issue. Verified by looking at dmesg as well as https://github.com/speed47/spectre-meltdown-checker"
1788563,2018-09-10 16:03:15 UTC,"Bionic SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095319.html"
1788563,2018-09-11 08:28:21 UTC,kernel from #7 resolves this on trusty as well (according to sysfs)
1788563,2018-09-07 22:34:27 UTC,I built Xenial and Trusty test kernels with those commits backported:
1788563,2018-09-12 11:01:34 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1788570,2018-08-23 08:45:56 UTC,Add new patch for correct offset.
1788570,2018-08-23 08:47:51 UTC,New patch
1788570,2018-08-23 08:49:06 UTC,Good patch
1788570,2018-08-23 08:50:30 UTC,Bug for download patch file
1788572,2018-08-23 08:18:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788578,2018-08-23 09:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788580,2018-08-23 09:00:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788580,2019-08-30 10:11:21 UTC,The failure on Bionic has been replaced by bug 1839912.
1788586,2018-08-27 07:00:50 UTC,This bug was fixed in the package linux-meta-gcp - 4.15.0.1018.32
1788593,2018-09-16 12:56:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788594,2018-09-16 12:54:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788594,2018-09-16 13:01:50 UTC,"I have this problem in Chromium and Firefox, but not on Chrome."
1788598,2018-08-24 07:45:13 UTC,"Thanks for getting back on this so fast.
I followed the proposed steps:"
1788598,2018-08-24 02:04:47 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1788600,2018-08-23 23:55:08 UTC,*** This is an automated message ***
1788603,2018-09-13 08:10:33 UTC,This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.5
1788603,2018-09-13 08:00:29 UTC,"The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1788603,2018-09-12 11:03:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788603,2018-09-10 10:15:28 UTC,"Started a guest with Bionic and Kernel 4.18 - working due to the updated apparmor profile.
We already had general regression tests on the identical PPA content, not redoing the same."
1788603,2018-09-06 15:57:30 UTC,"Hello Thadeu, or anyone else affected,"
1788603,2018-09-05 14:12:08 UTC,"Had another set of regression tests as I bundled another fix.
All good still."
1788603,2018-09-05 05:26:06 UTC,"Ok, glibc was unblocked and we can take a look at pushing this for Bionic as well."
1788603,2018-08-27 10:23:44 UTC,"Tested from PPA, also passed through some more checks and all look fine - but that was expected given the change being ""just"" opening up apparmor a little bit."
1788603,2018-08-28 05:29:06 UTC,"PPA for the Bionic SRU at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3386
Note: This not only waits for Cosmic to complete, but also for the former SRU to complete as well."
1788603,2018-08-28 05:23:06 UTC,"FYI cosmic is slightly stalled by glibc migration, other than that it looks good to me at the moment."
1788603,2018-08-27 10:23:02 UTC,"Tested against Kernel 4.18 from mainline builds:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18/linux-image-unsigned-4.18.0-041800-generic_4.18.0-041800.201808122131_amd64.deb"
1788603,2018-08-27 09:56:47 UTC,Prepared in PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3381
1788603,2018-08-27 08:49:41 UTC,Upstream accepted: https://libvirt.org/git/?p=libvirt.git;a=commit;h=8741b9435108b1f0d87670e44e1ed75f806b7791
1788603,2018-08-24 06:14:38 UTC,"Tested, confirmed wrapped in a libvirt upstream patch and submitted at https://www.redhat.com/archives/libvir-list/2018-August/msg01532.html"
1788603,2018-08-23 18:22:07 UTC,"ago 23 14:40:18 calabresa audit[5997]: AVC apparmor=""DENIED"" operation=""ptrace"" profile=""/usr/sbin/libvirtd"" pid=5997 comm=""libvirtd"" requested_mask=""read"" denied_mask=""read"" peer=""unconfined""
ago 22 18:00:12 calabresa audit[4409]: AVC apparmor=""DENIED"" operation=""ptrace"" profile=""/usr/sbin/libvirtd"" pid=4409 comm=""libvirtd"" requested_mask=""read"" denied_mask=""read"" peer=""libvirt-14e92a75-7668-4b97-8f92-322fc1b9c78a""
ago 23 09:18:06 calabresa audit[2507]: AVC apparmor=""DENIED"" operation=""ptrace"" profile=""/usr/sbin/libvirtd"" pid=2507 comm=""libvirtd"" requested_mask=""read"" denied_mask=""read"" peer=""unconfined"""
1788603,2018-08-23 17:52:43 UTC,"So, investigated this into an apparmor difference between 4.17 and 4.18. This is due to commit 338d0be437ef10e247a35aed83dbab182cf406a2 (""apparmor: fix ptrace read check"")."
1788603,2018-09-04 18:57:37 UTC,This bug was fixed in the package libvirt - 4.6.0-2ubuntu3
1788623,2018-08-28 18:53:43 UTC,"The following commit introduced the exception table in v4.15-rc1:
35732d01fe31 ipv6: introduce a hash table to store dst cache"
1788623,2018-08-28 20:59:10 UTC,I ran the test case on the 4.19.0-041900rc1-generic kernel and it also has the bug.
1788623,2018-08-29 17:26:11 UTC,"To confirm this regression is due to commit 35732d01fe31, I built a mainline test kernel with that commits as the tip."
1788623,2018-08-29 21:28:21 UTC,"Yes, kernel 4.14.0-041400rc3-generic resolves the bug. The test case in #1 succeeds with that kernel."
1788623,2018-08-31 14:17:37 UTC,Thanks for testing.  That implies that commit 35732d01fe31 is not the specific commit that introduced the regression.  I built a second test kernel up to the commit f5bbe7ee79c2.
1788623,2018-10-31 22:46:07 UTC,"Sorry for the long delay. I have tested the following version now, and the test (pmtu-sadr.sh) reports failure."
1788623,2018-09-05 12:27:12 UTC,"Thanks for testing.  There are quite a few ipv6 commits added in v4.15-rc1, so we may have to bisect through them.  Can you first confirm that v4.15-rc1 exhibits the bug?  It can be downloaded from:"
1788623,2018-09-13 15:42:17 UTC,"Yes, 4.15.0-041500rc1-generic exhibits the bug."
1788623,2018-09-13 20:13:22 UTC,I started a kernel bisect between commit v4.14 final and v4.15-rc1. The kernel bisect will require testing of about 13 test kernels.
1788623,2018-11-01 15:07:51 UTC,"You mention in comment #2 that your patch resolves this bug.  Is that still the case, and have you sent it upstream for inclusion in mainline?"
1788623,2019-12-22 15:03:54 UTC,"This bug was fixed by upstream in v5.2 (commit 510e2ceda031eed97a7a0f9aad65d271a58b460d). It's also fixed in v5.0.19, i.e. the fix is available in Disco-updates/security since version 5.0.0-26.27 of the linux package, and in Eoan and Focal."
1788623,2018-09-01 20:16:50 UTC,"Yes, the following kernels also resolves this bug:"
1788623,2018-08-24 18:43:39 UTC,I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the last kernel that did not have this issue.
1788623,2018-08-24 20:10:28 UTC,I have tested all kernels in the list (except 4.6 which link leads to 404) and the first kernel with the bug is v4.15 Final.
1788623,2018-08-23 16:28:32 UTC,I added logs from a Virtual Machine I did some testing on. But I doubt they are very interesting.
1788623,2018-08-23 20:00:07 UTC,This change was made by a bot.
1788623,2018-08-23 14:24:41 UTC,Patch which fixes the bug for me.
1788623,2018-08-23 14:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788623,2018-08-23 16:26:06 UTC,apport information
1788623,2018-08-23 16:26:07 UTC,apport information
1788623,2018-08-23 16:26:10 UTC,apport information
1788623,2018-08-23 16:26:11 UTC,apport information
1788623,2018-08-23 16:26:09 UTC,apport information
1788623,2018-08-23 16:26:14 UTC,apport information
1788623,2018-08-23 16:26:14 UTC,apport information
1788623,2018-08-23 16:26:16 UTC,apport information
1788623,2018-08-23 16:26:17 UTC,apport information
1788623,2018-08-23 16:26:18 UTC,apport information
1788623,2018-08-23 16:26:19 UTC,apport information
1788623,2018-08-23 16:26:12 UTC,apport information
1788624,2020-02-09 22:19:55 UTC,"Is this still an issue? I've just tried it and it works for me, tempest ended up with ModuleNotFoundError: No module named 'numpy' exception."
1788634,2018-09-06 08:31:28 UTC,"The problem seems to be there in stable/queens, too. (e.g. more than 1000 occurrences in http://logs.openstack.org/01/600101/1/check/tempest-full/25c9d13/controller/logs/screen-n-cpu.txt.gz )"
1788634,2019-03-22 03:48:17 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1788634,2018-09-24 14:46:48 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1788634,2018-09-21 12:02:43 UTC,"Reviewed:  https://review.openstack.org/600372
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ece888c790475e529163810a8f01b5ffa65c8ea
Submitter: Zuul
Branch:    stable/queens"
1788634,2018-09-06 08:29:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/600372"
1788634,2018-09-24 14:47:08 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1788634,2018-08-24 09:41:49 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/596264"
1788634,2018-08-24 08:45:40 UTC,"Reviewed:  https://review.openstack.org/595810
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=375632cbc9019f0e4e887afb5d6e48978f2a1a26
Submitter: Zuul
Branch:    master"
1788634,2018-08-23 15:10:03 UTC,"Taking http://logs.openstack.org/97/579897/4/check/tempest-full/53d05dc/controller/logs/screen-n-cpu.txt.gz as a sample, the ""Defaulting the value of the field"" DEBUG log shows up over 1000 times."
1788634,2018-08-23 15:04:08 UTC,@Matthew: because the implementation stalled halfway:
1788634,2018-08-23 15:02:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/595810"
1788634,2018-08-23 14:52:13 UTC,"As near as I can tell, numa_membw_values is never set. Maybe in some out-of-tree monitor? But it's certainly not set in https://github.com/openstack/nova/blob/cccba02be8dda0350a215de78b0acde3dbf19716/nova/compute/monitors/cpu/virt_driver.py#L42 which is where I'd expect it."
1788634,2018-09-05 10:39:15 UTC,"Reviewed:  https://review.openstack.org/596264
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3724280716703bad54d6dc434b4b1679243113d9
Submitter: Zuul
Branch:    stable/rocky"
1788645,2019-06-07 20:24:30 UTC,We no longer use the overcloud container image prepare command. Feel free to reopen if this is still an issue.
1788645,2021-02-17 17:09:11 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1788651,2018-09-07 18:58:04 UTC,"https://bugzilla.gnome.org/show_bug.cgi?id=795997 is fixed in evolution-data-server 3.28.3.
If your distribution does not ship 3.28.3 or higher you need to ask your distribution for backporting the fix."
1788651,2018-09-07 19:28:30 UTC,"Andre, Ubuntu 16.04 LTS included evolution-dats-server 3.18. 3.20 introduced a major overhaul of Google oauth2 integration. So a fix in 3.28.3 is probably not going to be easy to apply to 16.04 LTS."
1788655,2018-08-23 19:52:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788656,2018-08-24 11:07:36 UTC,Uploaded to cosmic-proposed.
1788657,2019-07-02 04:03:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788659,2018-10-23 11:27:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788659,2018-10-23 11:31:51 UTC,"I have seen this for quite some time as well. Usually connected to both wifi and cabled network at work (while laptop is docked), which is quite handy for when I go to meetings and undock my laptop, but will stay online since I am also on wifi."
1788659,2018-10-23 14:31:00 UTC,This is working as designed.
1788659,2018-10-23 14:31:34 UTC,"Marking Incomplete for now, in case there's more to it than a connectivity checking issue."
1788659,2018-10-23 14:46:10 UTC,"I eventually figured out that's what was happening. However, the connectivity check is not working correctly. In my case, there is indeed ethernet connectivity, despite it thinking that there isn't. It will assign the network ""penalty"" metric even when ethernet has been connected for 30+ minutes, so something is causing it to incorrectly fail the connectivity check. If I override the metric manually, it works and uses ethernet, so there is not a problem with the connection."
1788659,2018-10-23 15:17:11 UTC,"Whether it's been running for 30 minutes or not doesn't change much though; the connection *can* fail, and the connectivity checking is a pretty simple HTTP check."
1788660,2019-05-14 13:32:34 UTC,"I wonder if https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1828458 is related. (Has a similar ""invalid token"" error, but it is on a newer release of Openstack.)"
1788660,2018-11-09 09:09:06 UTC,"Looking at the original bug description closer, we can see that in fact the original web page (the SPICE client) was loaded as https, but the websocket was definitely insecure."
1788660,2018-11-05 07:31:09 UTC,This was Queens on Xenial.
1788660,2018-10-18 14:57:43 UTC,spice-html5 should be switching to wss mode automatically based on the fact that the connection is a https secure connection - please can you confirm which release of openstack you see this issue with.
1788660,2018-11-09 04:50:32 UTC,"I reproduced this issue, the problem is specifically when first configuring SSL (or disabling SSL) for the console. In my case I was using VNC and not SPICE.."
1788664,2018-09-25 11:45:25 UTC,"You are very right on that, the wording is confusing here and simply wrong.  Will get changed in the future."
1788665,2018-08-24 08:16:15 UTC,"QEMU is already capable of exposing the new CPU features to guests, so possibly a mis-configuration. Please provide the full QEMU command line args you are using for this guest too."
1788665,2018-09-14 17:27:07 UTC,"I did a git-bisect between 4.14.18(bad) and 4.14.10(good). Unsurprisingly, this is the first ""bad"" commit:"
1788665,2018-09-14 17:42:35 UTC,George: Can you confirm how your graphics is setup; the original reporter had an Nvidia card with PCI passthrough; is yours the same?
1788665,2018-09-14 20:02:44 UTC,"Yes, it's an Nvidia GTX 1060 6GB with PCI passthrough to a Windows 1803 KVM guest. As far as I can tell my setup is very similar to Heiko's, only I am using libvirt, not qemu directly."
1788665,2018-09-18 00:06:33 UTC,"It seems that this ""bug"" affects only 2D-performance mediated through GDI in Windows (CPU-, not GPU-driven). There have been reports that GDI switches a lot between user/kernel space."
1788665,2018-09-18 10:49:39 UTC,I don't think we should see a vmexit on a guest user<->kernel switch.
1788665,2018-09-19 01:24:12 UTC,"snapshot_2 showing the pattern of vmentries/vmexits from the previous comment (""zoom-in"")."
1788665,2018-09-19 18:53:42 UTC,"Just to be sure, I repeated it, with the same result. I have the impression that it might be the time spent between a vmentry and a vmexit that matters in the CPU performance of the guest. I am no expert though."
1788665,2018-09-11 18:56:43 UTC,"Hello All,"
1788665,2018-09-19 18:58:32 UTC,"I also tried to give ESXi a try. VMware lets me download only 6.7 from their site. Although I have a workstation motherboard (Supermicro X9SRA), it won't let me start a VM with IOMMU enabled, it complains about failing to register the passthrough GPU."
1788665,2018-09-19 19:20:14 UTC,It doesn't surprise me too much that the time spent on the host between exit&entry is higher on a host dealing with spec-ctrl;  but I wouldn't really expect it to change depending on the guests settings.
1788665,2020-11-12 18:24:08 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1788665,2020-11-19 20:23:43 UTC,I've switched hosts so I would have to run a series of tests to compare.
1788665,2021-01-22 04:17:15 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1788665,2018-09-19 09:57:59 UTC,"Have we got this the right way around????
So you're saying the one with spec-ctrl disabled is faster, but has a lot more kvm-exits?"
1788665,2018-09-05 20:01:21 UTC,"I won’t be able to run any tests for the next 16 days at the very least, as I’m traveling."
1788665,2018-09-19 01:23:15 UTC,"David, your suggestion seemed helpful, at least there is a difference in the pattern of vmentries and vmexits. See the snapshot attached."
1788665,2018-09-05 06:12:28 UTC,"Here is another person confirming the bug, with a little more details:"
1788665,2018-09-05 10:21:46 UTC,I don't have the nvidia for pass through to try this with; but I suggest that you try the following:
1788665,2018-08-24 16:47:54 UTC,"Thanks for the reply. I understand that the CPU features are exposed. However, is the host-side Intel microcode exposed to the guest?"
1788665,2018-08-24 17:11:12 UTC,"You're mis-understanding how microcode works a little. Microcode is loaded into physical CPUs in the host. This affects everything that runs on these CPUs thereafter. A KVM guest is merely a process running on the host CPUs, so it is affected by the updated microcode. There is no notion of the virtual CPUs having a different microcode."
1788665,2018-08-24 21:43:37 UTC,Thanks for your explanations - I thought so too.
1788665,2018-08-25 15:20:05 UTC,"Daniel Berrange: ...Essentially if your guest kernel shows ""pti ssbd ibrs ibpb stibp"" features as present, then thanks to your ""-cpu host"" usage, the guest should see them too."
1788665,2018-08-25 15:27:22 UTC,"For comparison, here the Linux/host cat /proc/cpuinfo (partial):"
1788665,2018-08-28 17:20:56 UTC,"Thanks, I will do that tomorrow and report back."
1788665,2018-08-28 16:07:18 UTC,"I'm not convinced we can trust the output from cygwin wrt CPU flags.  A better test would be to install a modern Linux guest which has the mitigations, and see if that reports the flags."
1788665,2018-08-30 11:08:41 UTC,Downloaded and ran the spectre-meltdown-checker.sh
1788665,2018-08-30 11:53:39 UTC,"> Whew, after some hurdles I managed to install a Linux Mint 19 guest (Ubuntu 18.04). After all updates, here the output:
>
> $ dmesg | grep microcode
> [ 0.036780] core: PEBS disabled due to CPU errata, please upgrade microcode
>
> So the microcode in the guest is not loaded! But see below:
"
1788665,2018-08-30 15:21:26 UTC,">The possibilities left are that either your Windows guest is lacking software updates that could perhaps improve its performance, or that 2D graphics really is that awful in combination with spectre/meltdown fixes.
"
1788665,2018-08-30 16:11:13 UTC,There is always a performance differential between bare metal & VMs. The actual amount varies depending on alot of different factors and meltdown/spectre have had an effect here - the actual perf hit depends on the CPU models & virtual hardware and more besides - ranging anywhere from 0% to 40% perf hit
1788665,2018-08-30 20:21:41 UTC,"> If you disable Spectre protection in the Windows VM, then it is not protected from Spectre. The hypervisor protects itself, and exposes the CPU feature(s) that enable the guest to activate its own protection. The hypervisor won't protect the guest directly - it just gives it the tools needed to protect itself.
"
1788665,2018-08-31 09:45:38 UTC,I find it interesting this is a slow down with PCI passthrough - that's pretty much the case you'd expect there to be least change; it shouldn't be generating lots of vm exit's for example which you'd expect could have been made slower by the recent security changes.
1788665,2018-08-30 10:40:41 UTC,"Whew, after some hurdles I managed to install a Linux Mint 19 guest (Ubuntu 18.04). After all updates, here the output:"
1788676,2018-12-17 14:20:18 UTC,"@Holger, thank you for efforts in supporting KiCad.  Thanks to ng-spice, we can offer spice simulation support to our users."
1788676,2019-06-08 08:03:50 UTC,With the advent of ngspice-30 there is a ngspice solution available.
1788676,2019-01-01 10:21:57 UTC,ngspice-30 is available with the above cited patch (variable 'controlswait'
1788676,2018-12-15 11:09:23 UTC,The text box in the eeschema window (e.g. for the laser driver demo) may look like this:
1788676,2018-10-18 20:38:01 UTC,"What appears to be happening is that when a simulation is started through the KiCAD GUI, the .raw file from the previous simulation gets written.  Thus, a simulation must be run twice after any changes if you want to update the .raw output.  I've updated my installation:"
1788676,2018-12-07 14:18:48 UTC,"Sounds great, thank you for the offer! Let me know if there is anything we should do on our side. If the change is not backward compatible, then I would be grateful for giving us a way to recognize whether the ngspice library used by KiCad contains the change, e.g. by bumping the shared library version."
1788676,2018-12-07 13:21:04 UTC,I propose to add some code to ngspice to allow handling of the .control section after the simulation has finished. A extra thread and some synchronization with the background thread that hosts the simulation are required. As of now using a .control section is without value.
1788676,2018-08-23 19:09:59 UTC,Please remember to add version information.
1788676,2018-12-15 11:04:51 UTC,"There is now a code enhancement available on the ngspice git pre-master branch to allow all ngspice .control section commands (e.g. rusage, write etc.) to be executed after the simulation has finished.
To enable this, one has to set a flag right before the command in the simulator window text box (then valid for all commands following) or in spice.rc or .spiceinit for every command with"
1788679,2018-08-24 07:04:01 UTC,"- auto-internal backup: https://bugzilla.gnome.org/show_bug.cgi?id=716151
- Jpg-raw images: https://gitlab.gnome.org/GNOME/shotwell/issues/21"
1788679,2018-08-24 07:17:51 UTC,Thanks Jens for the upstream pointers
1788679,2018-08-24 08:21:57 UTC,"Please subscribe yourself to those upstream bugs, this is out of Ubuntu's scope"
1788680,2018-08-23 19:37:46 UTC,"Testing the fix is a little cumbersome. Here's a contrived example; adjust as needed for your environment, or try it with an existing copy template that has null statcat values but a non-null statcat_filter value."
1788680,2019-03-19 14:00:07 UTC,SCLENDS has signed a contract with Equinox to address this bug.
1788680,2019-05-14 17:26:53 UTC,"We suddenly began running into this regularly.  The offered branch is a very simple change, and it works, so pushed to master through rel_3_1.  Thanks, Jeff!"
1788681,2018-10-04 20:29:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788681,2018-10-07 04:48:42 UTC,"Fix has only been released for Cosmic.  Given the package is basically non-functional on Bionic, is there a plan to backport the fix?  There doesn't seem much point in keeping it in the repository otherwise."
1788681,2018-08-23 20:56:19 UTC,"Hi Wladimir,"
1788681,2018-08-23 19:23:37 UTC,"same is reproduced when you run 'dc', enter into it some expression ending with 'p q', and examining its exit code with 'echo $?' afterwards"
1788681,2018-08-24 06:22:16 UTC,This bug was fixed in the package dphys-swapfile - 20100506-5
1788683,2018-09-04 16:06:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788686,2018-09-11 15:27:53 UTC,"Joseph Salisbury (jsalisbury),"
1788686,2018-09-11 15:09:09 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1788686,2018-09-06 17:51:09 UTC,"Since the laptop cannot be booted, apport cannot be run."
1788686,2018-10-08 18:35:18 UTC,"bellajohsan (bellajohsan),"
1788686,2018-08-23 19:41:00 UTC,Ubuntu 18.04.1 LTS gives the same boot failure.
1788686,2018-08-23 19:35:34 UTC,screen photo 2 is attached
1788686,2018-08-23 19:34:57 UTC,Acer laptop model is A315-41-R001
1788686,2018-09-06 17:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788701,2018-08-24 05:31:35 UTC,"virtio-vga will adapt the guest display to the window size (once the guest drivers are loaded).
Therefore it is not needed to auto-resize the window (to avoid display scaling)."
1788701,2018-08-24 09:44:32 UTC,"Well, then something isn't right here."
1788701,2020-11-13 15:47:14 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1788701,2021-01-13 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1788702,2018-08-24 15:56:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788706,2019-01-23 15:45:51 UTC,"I have same problem. 18.04 LTS, HPLIP hplip-3.18.12."
1788706,2019-08-10 22:39:31 UTC,"I just solved a problem very similar to this in Debian. To solve it, I added ""oldstable"" to my Debian sources.list and then I was able to downgrade several packages. I downgraded:"
1788706,2019-06-17 12:20:56 UTC,I've got Ubuntu 19.04 and HPLIP 3.19.5 and have the exact same error:
1788706,2018-10-21 21:17:03 UTC,"My distro is Ubuntu 18.04.1 LTS
My printer is a Laserjet Professional P 1102w
hplip 3.18.9 did not work for me, with error:
prnt/hpcups/HPCupsFilter.cpp 647: DEBUG: imageProcessorStartPage failed result = 2"
1788706,2018-09-17 12:06:43 UTC,"Hi,
Can you mention which distro you are facing this issue? We were not able to see this issue in Ubuntu 18.04 with hplip driver version of 3.18.7."
1788706,2018-09-24 17:28:12 UTC,Many thanks. Installed version 3.18.6 and it all worked the first time.
1788706,2018-09-17 12:33:07 UTC,"FWIW, at least another user seemed to be having the same (or a similar) problem with hplip 3.18.7 that went away using v. 3.18.6: https://askubuntu.com/questions/1070450/hplip-hp-device-manager-print-job-has-completed-but-nothing-happens-hp-la/1072536#1072536"
1788706,2018-08-29 22:42:13 UTC,Installing hplip 3.18.6 solves the problem.
1788706,2018-08-29 21:28:41 UTC,I have the same problem: the printer is installed but no job leaves the print queue.
1788706,2018-09-24 17:30:19 UTC,Hi!
1788707,2020-11-20 04:17:31 UTC,[Expired for mate-system-monitor (Ubuntu) because there has been no activity for 60 days.]
1788715,2019-02-09 18:23:31 UTC,Good idea.
1788718,2019-05-30 21:08:24 UTC,This option was looked at and it was decided that we would go the route of background steps for adding blocks to a page function
1788725,2018-08-24 08:07:42 UTC,apport information
1788725,2018-08-24 08:14:46 UTC,"somehow this bug was filed against linux, changed it to cheese (the webcam software) and added missing logfiles, marked as confirmed."
1788725,2018-08-24 08:07:49 UTC,apport information
1788725,2018-08-24 08:07:48 UTC,apport information
1788725,2018-08-24 08:07:47 UTC,apport information
1788725,2018-08-24 08:07:45 UTC,apport information
1788725,2018-08-24 08:07:43 UTC,apport information
1788725,2018-08-24 08:07:41 UTC,apport information
1788725,2018-08-23 23:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788725,2018-08-24 08:07:39 UTC,apport information
1788725,2018-08-24 08:07:38 UTC,apport information
1788725,2018-08-24 08:07:37 UTC,apport information
1788725,2018-08-24 08:07:35 UTC,apport information
1788725,2018-08-24 08:07:34 UTC,apport information
1788725,2018-08-24 08:07:33 UTC,apport information
1788725,2018-08-24 08:07:32 UTC,apport information
1788725,2018-08-24 08:07:40 UTC,apport information
1788734,2018-11-16 08:07:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788737,2019-03-29 01:16:35 UTC,This issue was fixed in the openstack/magnum-ui 5.1.0 release.
1788737,2018-09-10 05:18:10 UTC,This issue was fixed in the openstack/magnum-ui 4.0.1 release.
1788737,2018-09-05 19:23:04 UTC,This issue was fixed in the openstack/magnum-ui 5.0.1 release.
1788739,2018-08-30 02:44:15 UTC,"Those log messages are normal and not a bug. Although it's slightly unusual they would appear late like that. And no the logs are not separate any more, so that part is expected..."
1788739,2018-08-30 11:11:03 UTC,As far as I can tell Evolution is the only cause of those I usually have running.
1788739,2018-08-30 12:27:51 UTC,Also note it doesn't just happen when starting Evolution:
1788739,2018-08-31 01:35:33 UTC,If the EDID and mode info is being logged repeatedly that would usually mean the monitor is getting disconnected and reconnected. So please try:
1788739,2018-08-31 02:03:26 UTC,"Done, even blew out the connectors. Don't have another cable at the moment. As far as I can tell it's only Evo that causes this. There are only 3 that I use almost constantly. Ubuntu Firefox, Evo and Xfe file manager. Of those 3 only Evo causes this."
1788739,2018-08-31 02:13:38 UTC,Thanks. It's a Xorg server issue because they are X11 apps and the messages are coming from Xorg.
1788739,2018-08-31 02:28:48 UTC,Curious as to why nothing else causes it and why even after Evo is running it will periodically write to syslog. Any other kind of testing I can do?
1788739,2018-09-16 17:46:19 UTC,I have found that starting and stopping Xfe also causes this output.
1788739,2018-11-18 15:11:14 UTC,"This is still on-going. New VGA cable. May happen when I start Evo, XFE, Firefox and so on but not every time. I'm attaching /var/lib/gdm3/.local/share/xorg/Xorg.0.log possibly a clue is there. I realize all these are informational (II) notations to syslog however prior to my upgrade to 18.04.1LTS it was not happening."
1788747,2018-09-03 10:41:20 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.15.0-1022.24/raspi2-4.15-proposed-published.html"
1788747,2018-09-11 08:58:05 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1022.24
1788747,2018-08-30 10:26:52 UTC,Hardware Certification have begun testing this -proposed kernel.
1788747,2018-09-10 18:20:50 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1022.24
1788747,2018-09-10 18:33:11 UTC,The package has been published and the bug is being set to Fix Released
1788748,2018-09-11 08:50:29 UTC,This bug was fixed in the package linux-oem - 4.15.0-1018.21
1788748,2018-09-11 09:01:28 UTC,The package has been published and the bug is being set to Fix Released
1788748,2018-09-24 10:56:02 UTC,This bug was fixed in the package linux-oem - 4.15.0-1018.21
1788748,2018-08-28 15:04:56 UTC,Note: there was a conflict while rebasing the oem-next branch on top of Ubuntu-4.15.0-34.37. I skipped the following commit
1788750,2018-09-03 03:25:47 UTC,"4.15.0-1021.21 - aws
Regression test CMPL, RTB."
1788750,2018-09-10 18:14:22 UTC,This bug was fixed in the package linux-aws - 4.15.0-1021.21
1788750,2018-09-10 18:33:50 UTC,The package has been published and the bug is being set to Fix Released
1788750,2018-09-11 08:57:57 UTC,This bug was fixed in the package linux-aws - 4.15.0-1021.21
1788751,2018-09-10 18:34:21 UTC,The package has been published and the bug is being set to Fix Released
1788751,2018-09-10 18:15:53 UTC,This bug was fixed in the package linux-azure - 4.15.0-1023.24~16.04.1
1788751,2018-09-10 16:23:20 UTC,Testing looks good
1788751,2018-09-06 09:18:10 UTC,"4.15.0-1023.24 - azure
Regression test CMPL, RTB."
1788751,2018-09-10 18:15:19 UTC,This bug was fixed in the package linux-azure - 4.15.0-1023.24
1788752,2018-08-31 02:16:10 UTC,"4.15.0-1019.20 - gcp
Regression test CMPL, RTB."
1788752,2018-09-10 18:15:29 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1019.20
1788752,2018-09-10 18:32:07 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1019.20~16.04.1
1788752,2018-09-10 18:34:49 UTC,The package has been published and the bug is being set to Fix Released
1788753,2018-09-03 09:10:02 UTC,"4.15.0-1021.21 - kvm
Regression test CMPL, RTB."
1788753,2018-09-10 18:15:40 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1021.21
1788753,2018-09-10 18:35:10 UTC,The package has been published and the bug is being set to Fix Released
1788753,2018-09-11 08:57:59 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1021.21
1788754,2018-10-11 20:03:53 UTC,The package has been published and the bug is being set to Fix Released
1788754,2018-10-11 19:32:12 UTC,This bug was fixed in the package linux-azure - 4.15.0-1023.24~14.04.1
1788754,2018-09-10 20:41:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788754,2018-10-11 19:00:16 UTC,Testing complete.
1788754,2018-08-27 08:40:46 UTC,After discussion with SMB/Kleber accepting the Trusty nomination for now having that kernel in Trusty as well.
1788755,2018-09-06 09:54:16 UTC,"4.15.0-1023.24~16.04.1 - azure
Regression test CMPL, RTB."
1788755,2018-09-10 16:23:47 UTC,Testing looks good
1788755,2018-09-10 18:15:53 UTC,This bug was fixed in the package linux-azure - 4.15.0-1023.24~16.04.1
1788755,2018-09-10 18:35:54 UTC,The package has been published and the bug is being set to Fix Released
1788757,2018-09-03 14:48:33 UTC,ADT tests are not reported for -meta only packages.
1788757,2018-09-06 09:53:57 UTC,"4.15.0-1023.24~16.04.1 - azure
Regression test CMPL, RTB."
1788757,2018-09-11 08:33:45 UTC,xenial/linux-azure 4.15.0-1023.24~16.04.1 already released to -updates/-security.
1788757,2018-09-11 09:02:10 UTC,The package has been published and the bug is being set to Fix Released
1788758,2018-09-06 03:15:06 UTC,"4.15.0-1019.20~16.04.1 - gcp
Regression test CMPL, RTB."
1788758,2018-09-10 18:32:07 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1019.20~16.04.1
1788758,2018-09-10 20:30:58 UTC,The package has been published and the bug is being set to Fix Released
1788760,2018-09-10 20:10:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788760,2018-09-10 20:06:51 UTC,"Upon trying to upgrade to 4.15.0-34, it tells me I have broken packages but when I start Package Manager I have zero broken. My system is LM18.3 running kernel 4.15.0-33"
1788760,2018-09-10 18:36:52 UTC,The package has been published and the bug is being set to Fix Released
1788760,2018-09-06 10:48:27 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.15.0-34.37~16.04.1/xenial-4.15-proposed-published.html"
1788760,2018-09-10 10:01:37 UTC,"4.15.0-34.37~16.04.1 - lowlatency
Regression test CMPL, RTB."
1788760,2018-09-10 18:06:40 UTC,This bug was fixed in the package linux-hwe - 4.15.0-34.37~16.04.1
1788760,2018-08-30 10:27:35 UTC,Hardware Certification have begun testing this -proposed kernel.
1788761,2018-09-03 14:49:07 UTC,ADT tests are not reported for -meta only packages.
1788761,2018-09-10 10:26:25 UTC,"4.15.0-34.37~16.04.1 - lowlatency
Regression test CMPL, RTB."
1788761,2018-09-10 18:37:14 UTC,The package has been published and the bug is being set to Fix Released
1788762,2018-09-10 18:05:54 UTC,The package has been published and the bug is being set to Fix Released
1788762,2018-09-04 07:15:17 UTC,"3.2.0-135.181 - generic
Regression test CMPL, RTB."
1788762,2018-09-04 09:32:23 UTC,Verification tests not needed for this release.
1788763,2018-11-09 12:55:19 UTC,"Please don't randomly switch bugs to private, especially without any comment explaining why."
1788763,2018-08-24 06:49:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/596179"
1788765,2018-08-30 10:22:15 UTC,"3.13.0-158.208~precise2 - generic
Regression test CMPL, RTB."
1788765,2018-09-11 09:37:13 UTC,The package has been published and the bug is being set to Fix Released
1788767,2018-09-04 09:49:02 UTC,"4.4.0-1028.31 - aws
Regression test CMPL, RTB."
1788767,2018-09-10 16:09:33 UTC,No USN needed
1788767,2018-09-10 18:16:12 UTC,This bug was fixed in the package linux-aws - 4.4.0-1029.32
1788767,2018-09-10 18:39:47 UTC,The package has been published and the bug is being set to Fix Released
1788768,2018-08-30 10:27:15 UTC,Hardware Certification have begun testing this -proposed kernel.
1788768,2018-09-03 09:30:37 UTC,"4.4.0-135.161~14.04.1 - generic
Regression test CMPL, RTB."
1788768,2018-09-07 12:15:52 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/4.4.0-135.161~14.04.1/trusty-4.4-proposed-published.html"
1788768,2018-09-10 16:09:54 UTC,No USN needed
1788768,2018-09-10 18:09:26 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-135.161~14.04.1
1788768,2018-09-10 18:40:27 UTC,The package has been published and the bug is being set to Fix Released
1788769,2018-09-10 20:34:07 UTC,The package has been published and the bug is being set to Fix Released
1788769,2018-09-10 18:29:45 UTC,This bug was fixed in the package linux-aws - 4.4.0-1067.77
1788769,2018-09-05 07:31:43 UTC,"4.4.0-1067.77 - aws
Regression test CMPL, RTB."
1788769,2018-09-10 16:11:30 UTC,No USN needed
1788771,2018-08-31 02:58:56 UTC,"4.4.0-1033.39 - kvm
Regression test CMPL, RTB."
1788771,2018-09-10 16:11:57 UTC,No USN needed
1788771,2018-09-10 18:29:59 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1033.39
1788771,2018-09-10 20:34:30 UTC,The package has been published and the bug is being set to Fix Released
1788772,2018-08-30 01:11:26 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/VaVJ6L1K/360-pi2-kernel-440-1096104-68"
1788772,2018-09-03 10:41:00 UTC,Hardware Certification have begun testing this -proposed kernel.
1788772,2018-09-03 10:41:40 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1096.104/raspi2-4.4-proposed-published.html"
1788772,2018-09-10 16:13:21 UTC,No USN needed
1788772,2018-09-10 18:20:10 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1096.104
1788772,2018-09-11 08:03:45 UTC,The package has been published and the bug is being set to Fix Released
1788773,2018-09-11 08:04:02 UTC,The package has been published and the bug is being set to Fix Released
1788773,2018-09-10 18:20:30 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1100.105
1788773,2018-08-30 10:27:02 UTC,Hardware Certification have begun testing this -proposed kernel.
1788773,2018-09-06 10:18:28 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1100.105/snapdragon-4.4-proposed-published.html"
1788773,2018-08-29 16:36:26 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/8vk0CTzE/361-dragonboard-kernel-440-1100105-63"
1788773,2018-09-10 16:14:19 UTC,No USN needed
1788775,2018-08-24 12:32:24 UTC,"Well, we do use loop devices and do expect them to be listed for building the images. I'm not sure if there'll be a way to differentiate between the image build case and normal case to be able to pass some parameter (--skip-loopback, whatever) as appropriate. Let's look into that."
1788775,2018-08-26 07:44:12 UTC,Hmm that's a fair point.
1788775,2018-09-06 20:02:10 UTC,"How is this something relied on for building images?  As it stands, such a boot entry is non functional since it doesn't tell grub to set up a loop mapping to the underlying file so the ""disk"" won't be found.  If you are building an image and later transferring that image to bare metal, then it would work ( who does this? ), but does that use case only need to get the running system set up, or does it also need to be able to have os-prober add entries for other installations too?"
1788776,2018-08-24 22:54:03 UTC,"Also, just to clarify, the benefit of this package is that Samba would be able to provide proper Windows ACL/Permission Sets for ZFS. Since ZFS uses NFSv4 permission types."
1788776,2018-08-28 18:04:35 UTC,Marking as wishlist since it's a new feature for a stable release.
1788776,2019-02-14 13:32:06 UTC,"ZFS does not, as of this comment, have nfs4acl support under Linux.  It is REALLY close.  https://github.com/zfsonlinux/zfs/pull/7728  This pull request is mature and just missing test cases for the zfsonlinux build bots."
1788779,2018-09-13 11:52:15 UTC,You can find yours in ~/.config/indicator-stickynotes
1788781,2018-08-25 19:07:07 UTC,"@Steve Langasek oops, secure boot doesn't explain why I was able to run persistent live usb's. I also repaired grub  afterwards as the grub console kept appearing everytime I ran ubuntu.
Unable to access the desktop"
1788781,2018-08-25 19:02:20 UTC,apport information
1788781,2018-08-25 19:02:19 UTC,apport information
1788781,2018-08-25 18:08:57 UTC,@Steve Langasek disabling secure boot fixed my problem
1788781,2018-08-24 06:58:12 UTC,"You mention BIOS, but you have filed this bug report against shim which is a UEFI bootloader.  Is your system running UEFI?  How does your boot menu look?  Can you post the output of 'efibootmgr -v' when booted from the live CD?"
1788781,2018-08-25 19:02:18 UTC,apport information
1788790,2018-11-14 13:43:26 UTC,Thanks for the bugreport. What is your host lxd distro version and lxd version? I would like to reproduce and this info will help with that.
1788790,2018-11-15 03:23:25 UTC,"I just reproduced this. Host system is stock Ubuntu 18.04 (bionic), using the stable lxd snap (3.7)."
1788790,2019-09-20 10:10:28 UTC,Container created with 'lxc launch ubuntu:trusty -c security.privileged=true'
1788795,2018-08-24 07:32:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/596204"
1788806,2018-08-24 11:42:52 UTC,apport information
1788806,2018-08-24 11:42:51 UTC,apport information
1788806,2018-08-24 11:05:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1788806"
1788808,2018-08-24 19:07:36 UTC,Hi Thomas thanks for the report!
1788808,2019-03-08 07:51:31 UTC,"As much as Debian is concerned, I don't mind anymore, because Buster has version 2.6.0, which isn't conflicting anymore."
1788808,2019-03-11 23:42:38 UTC,"Got it thanks for the update, Thomas!"
1788814,2018-12-29 20:44:56 UTC,Thanks for the bug report. Resolved with the below commit.
1788814,2019-12-15 19:08:05 UTC,The commit was 2019.05.31. It's 2019.12.15...
1788814,2019-12-15 19:29:18 UTC,"To confirm i is just looking at/for an Exec Key, I added one:"
1788814,2019-12-15 19:38:30 UTC,*** Correction/Edit on #3: ***
1788817,2018-09-13 11:03:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1788817,2018-10-01 16:02:51 UTC,This bug was fixed in the package linux - 3.13.0-160.210
1788817,2018-08-24 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788817,2018-08-24 09:30:51 UTC,"Per git bisect, the fix for this should be:"
1788822,2019-09-20 13:22:38 UTC,This was fixed in MAAS 2.6.0:
1788833,2019-03-22 03:48:03 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1788833,2018-10-09 18:22:22 UTC,"This bug was fixed in the package nova - 2:18.0.1-0ubuntu1~cloud0
---------------"
1788833,2018-10-08 14:56:00 UTC,This bug was fixed in the package nova - 2:18.0.1-0ubuntu1
1788833,2018-10-04 14:14:31 UTC,Ubuntu Rocky py3.7 is tripping over the async keyword issue. Since we have python-oslo.db 4.40.0 in Ubuntu Rocky I'm planning to cherry-pick the following patch to the nova rocky package:
1788833,2018-09-24 14:46:59 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1788833,2018-08-29 08:09:04 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/597421"
1788833,2018-08-28 23:34:48 UTC,"Reviewed:  https://review.openstack.org/597174
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=964832d37dd244f4f4ebc0dba46e4316241a2120
Submitter: Zuul
Branch:    master"
1788833,2018-08-28 23:34:39 UTC,"Reviewed:  https://review.openstack.org/597173
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bd7d991309ea2bea5d175cb1f2710519936fd0c2
Submitter: Zuul
Branch:    master"
1788833,2018-08-28 16:12:32 UTC,I will upgrade oslo db to min 4.40 and come back
1788833,2018-08-28 16:05:06 UTC,"(10:56:34 AM) diliprenkila: <mriedem> diliprenkila oslo.db==4.40.0 ,oslo.messaging==8.1.0 on the compute nodes and oslo.db==4.38.0, oslo.messaging==6.4.1 on the nova controller node"
1788833,2018-09-06 04:56:51 UTC,"Reviewed:  https://review.openstack.org/597421
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=40e18681bc26c1e8f51aa280f600d72ad0846588
Submitter: Zuul
Branch:    stable/rocky"
1788836,2018-08-24 16:22:35 UTC,"Looking at https://launchpad.net/ubuntu/+source/jscoverage/+publishinghistory and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747401 it seems like the project was abandoned upstream and then removed from Debian, and in turn Ubuntu."
1788838,2018-08-24 10:56:35 UTC,"StacktraceTop:
 CheckPassiveGrab (tempGrab=0x564b3eb14330, checkCore=0, event=0x564b3e808890, grab=0x564b3ec9de90, device=0x564b3e936770) at ../../../../dix/events.c:3834
 CheckPassiveGrabsOnWindow (pWin=<optimized out>, device=device@entry=0x564b3e936770, event=event@entry=0x564b3e808890, checkCore=checkCore@entry=0 '\000', activate=activate@entry=1 '\001') at ../../../../dix/events.c:3955
 CheckDeviceGrabs (device=device@entry=0x564b3e936770, event=event@entry=0x564b3e808890, ancestor=ancestor@entry=0x0) at ../../../../dix/events.c:4040
 ProcessDeviceEvent (ev=ev@entry=0x564b3e808890, device=device@entry=0x564b3e936770) at ../../../../Xi/exevents.c:1783
 ProcessOtherEvent (ev=0x564b3e808890, device=0x564b3e936770) at ../../../../Xi/exevents.c:1873"
1788841,2018-08-24 11:03:17 UTC,`terraform apply -parallelism=1` seems to be a valid workaround.
1788841,2018-08-27 10:53:34 UTC,"Hi Sebastian,
the log only contains #2 ""reason why this is a libvirt issue"" when you know where to look exactly in your opinion or give it some pointers where others should look. So you could help next time by pointing to it with a few more words :-)"
1788841,2018-08-28 14:16:59 UTC,Marking the libvirt task as incomplete given the information request from the above comment.
1788841,2018-08-29 07:43:38 UTC,I'm working on it.
1788841,2018-08-29 08:06:07 UTC,"> Hi Sebastian,
> So you could help next time by pointing to it with a few more words :-)
"
1788841,2018-08-29 09:19:07 UTC,"I think you are good on the files of dnsmasq, I missed that those are the complete files indeed.
I beg your pardon for doing too much things at once."
1788841,2018-08-29 09:32:43 UTC,they have the same machine-id:
1788841,2018-08-29 10:17:49 UTC,"Ok, then this is the issue.
I'll mark the libvirt task invalid."
1788841,2018-08-29 10:39:23 UTC,Thanks very much!
1788843,2019-02-05 00:35:04 UTC,Perhaps you could leave this as a workaround as well(took me a while to figure out so maybe it will save someone else's time):
1788853,2018-12-09 04:17:31 UTC,[Expired for juju because there has been no activity for 60 days.]
1788853,2018-08-24 12:36:57 UTC,"This goes into a deeper nest as any existing entities (models, etc) and who owns then turns into different user accounts. There's no mechanism to tie existing Juju users in the DB to matching ones from the external identify service and so this is much deeper than changing the url which is locked for this very reason."
1788857,2018-09-04 13:49:46 UTC,Here is an object created in /usr/lib/python2.7/site-packages/keystoneauth1/identity/generic/base.py in get_auth_ref method:
1788859,2018-09-18 18:32:00 UTC,I have a similar issue: I can confirm that the output generated alternates between the two images attached at the system monitor update interval.
1788859,2018-10-18 13:36:16 UTC,"It's a common issue with RAM and swap. There are not enough memory. With Ubuntu 18.04  both memories should be greater than 1 GB . The load is often more than 90 % respectively.
With a bit of luck you  can check it  with
 System Load Indicator
(First I have removed Firefox in the graphical surface and then
 sudo apt install firefox  in the Terminal)"
1788859,2018-10-18 21:54:35 UTC,@fusi1939 in my case the problem was resolved by installing Unity desktop.
1788862,2019-09-19 12:06:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1788862,2019-09-20 13:20:33 UTC,"I think this is something that curtin should be able to determine on the fly, if could check that that device is an SSD (or supports TRIM) and enable discard."
1788862,2020-05-01 20:11:05 UTC,"there's no reason for curtin to determine on the fly; MAAS inventories the node, it knows which disks are rotational or ssd/nvme."
1788870,2018-09-17 11:53:20 UTC,"Hi,
The 'canberra-gtk-module' package not installed will not stop the print to happen in the device. Did the installation process got aborted after it failed to install this package?"
1788870,2018-09-18 04:55:34 UTC,"Hi Nestor,"
1788870,2018-09-18 11:26:09 UTC,Hello !!!
1788870,2018-09-18 11:43:24 UTC,Good to know that the issue is solved. Can you close this ticket as solved?
1788875,2018-11-14 06:34:35 UTC,"Is this limited to Quickstart? I'm getting this as of the latest version on a full triple-o deployment using oVirt nodes. I'm unable to specify a flavor or use scheduler hints. Seems regardless what I try, I'm getting the illusive No valid hosts. on overcloud deployment and also hitting this error:"
1788875,2018-09-12 15:33:53 UTC,"https://review.openstack.org/#/c/579406 fixed some errors (especially on baremetal/OVB) deployments with nodes not being recognized as suitable hosts, but it does not solve the issue of mismatch control and oooq_control etc. flavors."
1788875,2018-09-11 16:06:44 UTC,Does https://review.openstack.org/#/c/579406 also fix this?..
1788875,2018-09-12 15:12:41 UTC,"https://bugs.launchpad.net/tripleo/+bug/1790622 looks related, not sure if a dup"
1788880,2018-08-24 20:15:09 UTC,Jeff: please note the main bug report is about having a file browser opened by the edit icon. Permanent icons are a separated item.
1788880,2018-08-25 15:48:15 UTC,Initial patchset which adds a cell editor for directories to the path dialog:
1788880,2018-08-25 17:11:39 UTC,"Apologies, Thomas, I thought I had annotated this bug report."
1788880,2018-08-24 16:49:55 UTC,"Sadly it's rather difficult to get wxWidgets to agree to the ""show always"" part.  But I'll make another attempt at it when I have some spare time if someone else doesn't get there first."
1788890,2018-08-24 17:09:04 UTC,ceph is not currently supported with the standalone but this is a good thing to know that is an outstanding issue when we get to checking out ceph support.
1788890,2021-02-17 17:09:14 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1788894,2018-08-24 16:31:24 UTC,"This is not an issue in appstream, but likely the Ubuntu archive.
But it could also be snapcraft doing something weird (that cache path is odd!)."
1788894,2018-08-24 17:25:23 UTC,"Not sure what's going on, adding snapcragt and launchpad tasks for those folks to chime in"
1788894,2018-08-25 06:03:38 UTC,@ximion I tried to delete the cache directory manually (`rm -rf ~/.cache/snapcraft/`) and then run `snapcraft` again. Nothing changed.
1788897,2018-10-01 17:15:35 UTC,This bug was fixed in the package linux - 4.15.0-36.39
1788904,2018-09-18 23:20:31 UTC,Thank you!
1788904,2018-09-18 11:52:02 UTC,"Ok, I think this is good enough, thanks. I approve of the FFe for the listed changes in the description. Green light!"
1788904,2018-09-06 10:05:45 UTC,Could you update the bug for it to state the features that will be handled by the FFe?
1788904,2018-08-29 10:24:27 UTC,"I would be reluctant to approve a blanket FFe for this purpose, even for a non-LTS. We had some bad experiences in the past with blanket FFe's. What I would be willing to consider is a wider-range FFe for a selected set of features (which should be more or less similar). Would that be good enough?"
1788904,2018-08-30 00:29:10 UTC,"> I would be reluctant to approve a blanket FFe for this purpose, even for
> a non-LTS. We had some bad experiences in the past with blanket FFe's.
> What I would be willing to consider is a wider-range FFe for a selected
> set of features (which should be more or less similar). Would that be
> good enough?
"
1788905,2020-05-14 13:59:32 UTC,Here's a use case that would be helped by a setting that prevents or warns when a patron has had an item for too little time.
1788905,2020-05-14 14:47:02 UTC,"Another way to address this issue would be to provide an optional prompt in the Renew Items function. A sticky checkbox could enable a prompt to pop up when an item is scanned for renewal. The prompt could display the checkout (or last renewal) date and the due date of the item, and give the staff user a Yes/No option to proceed. This would allow the staff user to make an informed decision about proceeding with the renewal."
1788909,2018-11-21 15:55:43 UTC,Dupe of https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1786710?
1788915,2020-08-26 12:42:35 UTC,"I also hit this bug. We have late 2020 and I wonder, why this bug still is open?"
1788915,2020-11-05 08:38:08 UTC,Same here
1788915,2020-11-05 08:56:37 UTC,I think this is fixed https://github.com/canonical/cloud-init/commit/8439b191ec2f336d544cab86dba2860f969cd5b8
1788915,2020-11-05 14:14:25 UTC,"This just missed 20.3, but is included in upstream/master and will be included in 20.4."
1788915,2020-11-24 17:58:37 UTC,"This bug is believed to be fixed in cloud-init in version 20.4. If this is still a problem for you, please make a comment and set the state back to New"
1788919,2019-01-18 13:14:08 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/596428
Reason: Abandoning because this was not the correct way to fix this. What user is used depends on the qemu configuration of the host and the environment variables."
1788919,2019-03-15 15:11:47 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/611353"
1788919,2018-10-17 15:15:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611353"
1788919,2021-02-19 15:52:43 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1788919,2018-10-04 08:51:52 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/605021"
1788919,2018-08-24 19:10:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/596428"
1788919,2018-10-17 15:05:11 UTC,Progress on this got stuck on https://review.openstack.org/#/c/596428/ please join there in order to find-out a working solution.
1788919,2018-09-07 08:25:27 UTC,"just marked https://bugs.launchpad.net/tripleo/+bug/1790932 as duplicate of this, but I'm copy/pasting the description as it includes a trace which is missing here thanks"
1788920,2018-10-09 13:31:26 UTC,"Processing triggers for linux-image-4.15.0-33-generic (4.15.0-33.36) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-33-generic
mv: cannot stat '/boot/initrd.img-4.15.0-33-generic.new': No such file or directory
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.15.0-33-generic (--configure):
 installed linux-image-4.15.0-33-generic package post-installation script subprocess returned error exit status 1"
1788923,2018-08-24 19:22:31 UTC,"Interestingly, many of the mypaint packages point to http://mypaint.info/ which is expired."
1788923,2018-08-24 20:43:13 UTC,The MyPaint version is 1.2.0-4.1 if that is any help.
1788923,2018-08-25 22:57:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788929,2019-06-19 19:50:42 UTC,This bug was fixed in the package evince - 3.28.4-0ubuntu1.2
1788929,2019-06-19 19:40:36 UTC,This bug was fixed in the package evince - 3.18.2-1ubuntu4.5
1788929,2019-06-18 18:46:03 UTC,Ubuntu 14.04 LTS is now out of standard support and evince is not included in ESM.
1788929,2018-10-04 18:44:10 UTC,This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.10
1788929,2018-10-04 18:34:04 UTC,This bug was fixed in the package apparmor - 2.12-4ubuntu5.1
1788929,2018-10-04 18:23:50 UTC,This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.6~14.04.4
1788929,2018-10-02 14:52:49 UTC,"I referenced the wrong bug in the evince upload so it didn't auto-close, but 3.30.0-3ubuntu1 should address this."
1788929,2018-10-02 14:06:33 UTC,"Jamie, can you confirm whether cosmic is fixed for evince now with https://launchpad.net/ubuntu/+source/evince/3.30.0-3ubuntu1 ?"
1788929,2018-09-30 19:57:58 UTC,This bug was fixed in the package apparmor - 2.12-4ubuntu8
1788929,2018-09-27 17:51:32 UTC,https://gitlab.com/apparmor/apparmor/merge_requests/203/ was committed upstream.
1788929,2018-09-27 16:57:32 UTC,Adding apparmor task since the private-files abstraction should block this too.
1788929,2018-09-07 21:16:07 UTC,"I wonder whether it would make sense for you to amend https://wiki.ubuntu.com/Security/Features#AppArmor and add a little bit of information on what the various policies are supposed to achieve - in particular, replace the ""yes"" entries with something like ""best-effort""/""strong"" to signal whether the policy is supposed to provide meaningful confinement against a determined attacker.
Without that information, I believe that that table isn't very helpful to someone who is trying to reason about the security posture of a Ubuntu installation."
1788929,2018-09-05 18:46:59 UTC,Thank you for the report.
1788929,2018-08-24 23:16:23 UTC,"Hello Jann, thanks for the excellent report."
1788929,2018-10-02 14:36:53 UTC,"Since it was discussed here, the bug for enabling bubblewrap for gnome-desktop3 for bionic is LP: #1795668"
1788932,2020-04-03 23:51:50 UTC,This is resolved in 3.5 with the new angular interface.
1788935,2018-08-26 09:56:05 UTC,"Hello,"
1788935,2018-08-26 17:17:24 UTC,Hi.
1788936,2019-03-05 16:54:54 UTC,"You can see the bug at
Neutron's documentation [1]
  -> OpenStack Networking Guide
  -> Introduction
  -> Network address translation [2]
  -> ""SNAT"""
1788936,2018-12-21 16:22:21 UTC,This issue was fixed in the openstack/neutron 14.0.0.0b1 development milestone.
1788936,2019-03-05 07:24:02 UTC,"André Luis Penteado, why do you think openstack-manuals is affected as well?"
1788936,2018-08-24 22:04:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/596495"
1788936,2018-08-24 21:13:50 UTC,Tried to submit a patch via gerrit but kept getting
1788936,2018-08-28 16:46:39 UTC,"Reviewed:  https://review.openstack.org/596495
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3e1512873ad1fa7ad60a295ef86cefd3ac8c25f8
Submitter: Zuul
Branch:    master"
1788938,2018-08-24 20:57:20 UTC,I recommend looking at the date delta code that is in swift-storage charm for check_swift_replication_lag
1788938,2020-01-30 15:18:57 UTC,This was fixed in https://git.launchpad.net/nrpe-charm/commit/?id=2ac9b4d
1788940,2018-08-24 20:39:13 UTC,"FTR, a workaround for this that bypasses GRUB would be:"
1788940,2018-08-27 22:53:27 UTC,"This is now supported upstream, and I was able to backport the necessary fixes to the GRUB in Debian/unstable (test builds at ppa:dannf/test). However, I haven't been able to get them working on top of the Ubuntu patches - that build just loops with the error:"
1788946,2020-03-19 11:40:59 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1788946,2018-08-25 13:25:31 UTC,"Maybe (as a workaround), this extension will be useful to you:
https://gitlab.com/Moini/inkscape-realscale-extension"
1788946,2018-08-24 22:40:39 UTC,Hi tebi.
1788946,2018-08-25 00:25:15 UTC,thanks for the Tip Jabier.
1788951,2019-05-14 11:30:57 UTC,"It looks like the vault charm has been updated, and now configures the root CA, by default as 1 year - 1 hour. Additionally, there is a TTL option in the CA generation code now."
1788958,2018-08-24 23:11:36 UTC,Reported upstream at https://bugs.astron.com/view.php?id=32
1788960,2019-07-19 17:11:26 UTC,Thanks for filing the bug.  I believe this issue has been resolved in this commit:
1788967,2019-07-18 23:21:25 UTC,"HI,"
1788967,2019-09-17 04:17:44 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1788971,2018-08-26 14:18:40 UTC,None that I'm aware of.  What's the use-case that would require this?  (Or greatly benefit from it?)
1788971,2018-08-27 16:38:59 UTC,This was been discussed long ago.  There may have even been a bug report file for it on the old SourceForge bug tracker.  I can see this being useful for symbol and footprint library creators.  It's just that it is so low on the priority list that it is almost non-existent.  I can gladly make this a wish list but don't hold your breath.
1788971,2018-08-27 17:12:48 UTC,I was answering Jeff about it yesterday but I couldn't find a solid reason anymore.
1788972,2019-07-18 23:20:37 UTC,"Hi,"
1788974,2020-03-19 13:17:09 UTC,Closing because Fix Released.
1788976,2018-08-26 14:17:49 UTC,"Clarified title to not confuse with unmatched symbol fields (value, datasheet, footprint) between subsheets."
1788977,2019-04-22 11:30:16 UTC,Closing as a fix has been committed in 1.0alpha
1788977,2018-10-08 14:38:36 UTC,Able to reproduce in Fedora 28.  The following is the error in the console when it happens:
1788977,2018-08-25 13:02:10 UTC,"(here's a list of the others:
https://bugs.launchpad.net/inkscape/+bugs?field.searchtext=fedora%20crash&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=&orderby=-date_last_updated&start=0)"
1788977,2018-08-25 13:01:09 UTC,This is a known issue in Fedora... :-/
1788978,2019-01-08 15:53:54 UTC,"I also met the similar issue, vm with dpdk port just receives packets but cannot transmit packets out when restart openvswitch unless reboot the vm. And we found kernel version <= 3.10.0-327.el7.x86_64 does not have the problem, but the root causes haven't been found yet."
1788978,2018-10-25 01:22:43 UTC,I have not solved this problem yet.It’s really hard to get into the DPDK problem.
1788978,2018-08-28 00:27:32 UTC,I'm not sure that it's a bug releated neutron. Did you see any errors in neutron-openvswitch-agent log?
1788978,2018-10-22 03:42:04 UTC,"I also meet this problem, ovs+dpdk's vxlan can't success for more than 1500byte packets, and also meet this problem.do you solve it?"
1788978,2018-08-28 01:22:20 UTC,"This is the log in openvswitch.log, not in neutron-agent.log"
1788978,2018-10-22 12:14:38 UTC,"I also met the same issue, in my case it works sometimes after reboot and deleting/recreating DHCP agents"
1788982,2018-10-12 02:36:25 UTC,May be the reason below:
1788984,2018-08-25 06:29:57 UTC,"StacktraceTop:
 memset (__len=128, __ch=0, __dest=0xffff0009) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:71
 set_default_segmentation_info (parser=0x7f6a60013340) at gstvp9parser.c:565
 setup_past_independence (frame_hdr=0x556111809030, parser=0x7f6a60013340) at gstvp9parser.c:575
 gst_vp9_parser_update (frame_hdr=0x556111809030, parser=0x7f6a60013340) at gstvp9parser.c:603
 gst_vp9_parser_parse_frame_header (parser=<optimized out>, frame_hdr=frame_hdr@entry=0x556111809030, data=data@entry=0x7f6a6008f448 ""\202I\203B"", size=size@entry=74375) at gstvp9parser.c:812"
1788986,2018-08-28 17:58:02 UTC,Thanks for filing this bug in Ubuntu.
1788986,2018-08-29 19:10:27 UTC,"Earlier releases were able to use integrated configuration, meaning the rc-script tested if either the respective daemon configuration files existed, or if the integrated file Quagga.conf existed. If the daemon configuration file, zebra.conf for instance, or the Quagga.conf, either existed then the daemon was able to start. In the new systemd startup file it seems as if it only tests whether the respective daemon configuration files exist, not the integrated file."
1788986,2018-09-06 19:04:48 UTC,"The version of quagga in bionic is 1.2.4-1, which is the same as in Debian. Looks like Debian later on reverted the sysv script removal:
quagga (1.2.4-2) unstable; urgency=low"
1788986,2018-09-06 19:44:16 UTC,"Ok, I think I understand it now."
1788986,2018-09-06 19:48:53 UTC,"The sysv script checked for a Quagga.conf file, and if it's there, ignores the need for the other config files:
        # If the integrated config file is used the others are not checked.
        if [ -r ""$C_PATH/Quagga.conf"" ]; then
          return 0
        fi
...
          # check for config file
          if [ ! -r ""$C_PATH/$1.conf"" ]; then
            echo -n "" (not started without config file)""
            return 1"
1788988,2018-08-25 10:08:23 UTC,"News.  Multiple efforts using ARandR GUI failed;   however, this morning, by chance, an attempt to put the HDMI-2 on desktop extension underneath the primary DisplayPort DP-1 is successful.  It will take a while for my reflexes to pull or lift data from below the main menu bar, dragging with the mouse up or toward my knees, but it does work.  On the actual HDMI screen (to my right) there is the extended desktop and, as before, if I place a science database there using another application, using the window maximise +, it does go full screen on the local screen.  So, back to work! using a Workaround."
1788988,2018-08-25 08:45:40 UTC,"I think it's this /var/log/dist-upgrades apt.log; there are others.
Not sure why it's 4Mega;  hope the attachment works. . . .
The PC still does!"
1788989,2018-08-25 13:06:41 UTC,PC with problem froze soon after bug was reported.  It had been up for nearly 2 hours with fir4efox active most or that time.   After rebooting system was left alone for nearly 6 hours.  It has not frozen.
1788991,2018-08-31 22:31:06 UTC,Now it works again. Had switched off external screen in display devices settings after bug appeared. Switching it on again today did the job.
1788997,2019-03-08 16:44:15 UTC,"Sorry, I didn't bump the version number of the test kernel I built. I'll send a patch to revert the patch."
1788997,2019-03-08 16:02:07 UTC,"hmm, well...I'm not sure what happened..."
1788997,2019-03-08 08:11:23 UTC," kernel 4.15.0-46 works as good as -4.15.0-32, i.e. with the same setting (ant_sel=2 only)"
1788997,2019-03-08 06:50:59 UTC,"For me ant_sel=0  ""zero!"" was the magic key. Took me a week of messing around until I realized one cannot only select 1 or 2 but also 0. Try out with these:"
1788997,2019-03-08 06:01:09 UTC,"So for Bionic, the commit should be reverted."
1788997,2019-03-07 23:40:29 UTC,"I guess folk like myself who upgraded to Cosmic and 4.18 have a working wifi with ant_sel=1. Bionic has the problem, ironically given that it is LTS."
1788997,2019-03-07 21:51:51 UTC,"well, I have not seen any ""officially released"" kernel beyond 4.15.0-32, that works ."
1788997,2018-11-03 13:36:06 UTC,I can confirm comment #65 :-)
1788997,2019-03-07 11:15:49 UTC,"well...this bug has been unresolved for more than 6 month meanwhile, which is pretty hard for me to understand. I think it is common understanding that the Linux community is fixing bugs more or less instantaneously, as opposed to Microsoft Windows. Reverting a code change is a no brainer, which leave the question why this bug is not fixed with a  kernel update. Quite a few contributers, as well as myself, have tested kernels that fix the bug, let alone, that no ""official"" fix has been released meanwhile. This is pretty much frustrating."
1788997,2019-03-07 04:20:22 UTC,Does reverting the simple commit help? If it helps then we should simply revert it.
1788997,2019-02-03 11:57:20 UTC,This problem still exists for me on debian testing with 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1
1788997,2018-12-20 07:51:33 UTC,Still doesn't work in 4.15.0-42 either.
1788997,2018-11-05 08:51:25 UTC,Works on 4.15.0-36 but not on 4.15.0-38...
1788997,2019-03-14 11:51:55 UTC,"hmm, well, I had the test kernel as of #75 installed , which was overridden by a regular update today...and guess what, that kernel , as already mentioned in #78, does NOT work. So manual intervention is required to revert to the test kernel again. This is NOT very handy :-(("
1788997,2018-11-01 20:14:31 UTC,"I also tested last kernel from mainline (following #25 & #26 ,just for confirmation...)
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19
modinfo rtl8723be says:
filename:       /lib/modules/4.19.0-041900-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko
firmware:       rtlwifi/rtl8723befw_36.bin
firmware:       rtlwifi/rtl8723befw.bin
srcversion:     CF0CBB2F4446A615D0ABCBE"
1788997,2018-11-01 17:09:03 UTC,"I tested last proposed kernel 4.15.0-39, but the issue is still there, no signal with either no ant_sel, ant_sel=0, ant_sel=1 or ant_sel=2.
In my environment the last working kernel is 4.15.0-32 with ant_sel=2."
1788997,2019-03-07 16:25:44 UTC,"AFAIU, mainline kernel works, but with different ant_sel value.
On currently Ubuntu kernel, it doesn't work at all, correct?"
1788997,2019-03-14 16:46:38 UTC,It'll be included in next kernel release.
1788997,2019-04-06 12:56:30 UTC,"I'm downloading from archive.canonical.com/ubuntu ...but NOT from a mirror. The test kernel as of #77  is already at version 49 !, so how can a kernel in proposed be at version # 48."
1788997,2019-04-04 20:53:30 UTC,The Kernel modules as shown when -proposed is enabled DOES NOT solve the problem at all. The wifi signal is still extremely weak. Only the test kernel mention in #77 and #78 solves the problem.
1788997,2019-09-20 23:08:44 UTC,apport-collect 1788997
1788997,2019-07-28 12:29:44 UTC,"sorry,reinstalling the kernel package helped"
1788997,2019-07-28 11:45:40 UTC,"sudo modprobe -rvf rtl8723be
rmmod rtl8723be
rmmod rtl_pci
rmmod rtl8723_common
rmmod btcoexist
rmmod rtlwifi
rmmod mac80211
rmmod cfg80211"
1788997,2019-07-28 11:38:54 UTC,doesn't work on 4.15.0-55
1788997,2019-07-28 11:29:28 UTC,doesn't work on 4.15.0-55
1788997,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1788997,2019-04-19 06:55:34 UTC,"I installed the proposed kernel and the fix works in principle, but in the manual selection the numbering seems swapped. On my HP 250 the antenna cable is connected to connector #1 (label printed on the WiFi module) but in the kernel module I have to select antenna #2 for a good signal.
Anyhow, this is juts a cosmetic issue for me, thanks for the fix :)"
1788997,2019-04-10 11:55:03 UTC,"Well, I have to stand corrected !"
1788997,2019-04-10 10:35:07 UTC,Just to avoid confusion:
1788997,2019-04-10 10:25:52 UTC,Suffering from weak rtl8723be wifi signal and new to proposed updates.
1788997,2018-10-23 18:33:12 UTC,"Sorry, but it seems the kernels 4.15.0-38 in bionic-updates and in bionic-proposed are the same. I have tested it already (#57), the bug is in place. I would be happy to help test other kernels."
1788997,2019-04-09 19:56:41 UTC,To repeat again: I have the kernel as of # 75 installed.
1788997,2019-04-09 05:44:11 UTC,What's the output of `dpkg -l | grep linux-image` and `apt show linux-image-generic`?
1788997,2019-04-06 07:41:18 UTC,Maybe the mirror is not in-sync? Please give another mirror a try.
1788997,2019-04-05 19:22:04 UTC,"well,
this is what software updater reports:"
1788997,2019-04-05 16:31:21 UTC,What's the version of the proposed kernel? It should be -48.
1788997,2019-04-05 14:08:02 UTC,"oh well, ....it seems to me that kernel versioning is pretty much messed up. The (test) kernel I had installed, as of #77 reports version 4.15.0-46 ( linux-unsigned, modules, modoles-extra). Software  Updater reports the very same version numbers for those modules to be updated, independent from whether -proposed under the development tab in Software Updater is enabled or not !!"
1788997,2019-04-04 18:04:00 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1788997,2019-04-10 04:43:13 UTC,"On my system:
$ rmadison linux | grep bionic-proposed
 linux | 4.15.0-48.51   | bionic-proposed  | source"
1788997,2018-10-04 10:28:22 UTC,"I meant to type ""-34"" and of course it was -36 that was released recently."
1788997,2018-10-04 10:21:15 UTC,""" Can you test -proposed or newer than -33 to see if this bug is fixed?"""
1788997,2018-08-25 12:04:13 UTC,"The above diagnosis was performed having started the computer with 4.15.0-33.36 amd64; as a result there was no network connection. To obtain network connection for submitting the data, a Gigaset USB Adapter 108 has been plugged in prior to running apport-collect 1788997."
1788997,2018-08-25 11:56:04 UTC,apport information
1788997,2018-08-25 11:56:02 UTC,apport information
1788997,2018-08-25 11:55:59 UTC,apport information
1788997,2018-08-25 11:55:58 UTC,apport information
1788997,2018-08-25 11:55:57 UTC,apport information
1788997,2018-10-23 17:52:58 UTC,Tested bionic-proposed kernel 4.15.0-38.41.
1788997,2018-08-25 11:55:55 UTC,apport information
1788997,2018-08-25 11:55:54 UTC,apport information
1788997,2018-08-25 11:55:54 UTC,apport information
1788997,2018-08-25 11:55:52 UTC,apport information
1788997,2018-08-25 11:55:51 UTC,apport information
1788997,2018-08-25 11:55:50 UTC,apport information
1788997,2018-08-25 11:55:49 UTC,apport information
1788997,2018-08-25 11:55:48 UTC,apport information
1788997,2018-08-25 11:55:47 UTC,apport information
1788997,2018-08-25 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1788997,2018-08-27 10:00:31 UTC,"Please revert https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/net/wireless/realtek/rtlwifi?id=af8a41cccf8f469165c6debc8fe07c5fd2ca501a
It is the only change from -32 that could affect the rtl8723be"
1788997,2018-08-27 21:00:48 UTC,I have hp-15-ac167nf with wireless chip rtl8723be and ubuntu xenial 16.04 LTS and HWE.
1788997,2018-08-25 11:55:56 UTC,apport information
1788997,2018-08-28 18:08:19 UTC,"I built a test kernel with a revert of commit af8a41cccf8f469165c6debc8fe07c5fd2ca501a.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997"
1788997,2018-10-03 20:41:38 UTC,"I think this commit should fix the bug:
af8a41cccf8f rtlwifi: cleanup 8723be ant_sel definition"
1788997,2018-10-03 20:31:43 UTC,"Just to confirm, v4.17-rc4 works?  I'll start a ""Reverse"" bisect between v4.17-rc3 and v4.17-rc4."
1788997,2018-10-03 18:40:17 UTC,neither rc2 or rc3 work at all...very low signal ...
1788997,2018-10-02 12:52:11 UTC,"@Stephane Potier,  once we identify the fix, I will SRU it to the Ubuntu kernel.  At that point, the fix will be applied for the following round of updates."
1788997,2018-10-02 12:51:31 UTC,Can you next test v4.17-rc2 and v4.17-rc3:
1788997,2018-09-23 14:19:11 UTC,"I do not know Linux kernel process, but i would like to know if and when this fix will appear by defautl into Ubuntu doing a sudo apt upgrade ?
Thanks and sorry for such basic question."
1788997,2018-09-21 12:40:53 UTC,"v4.17-rc4 just works fine.
v4.17-rc1 doesn't work at all (yields no , or a very, very weak signal)."
1788997,2018-09-21 09:23:12 UTC,We next need to identify which 4.17 release candidate introduced the fix.  Can you next test the following kernels:
1788997,2018-09-20 14:54:32 UTC,"4.16 does not work at all.
4.17 and 4.18 work just fine.
Haven't tested 4.19-rc1 though anymore, as suggested."
1788997,2018-09-19 08:37:44 UTC,"We can perform a ""Reverse"" bisect to identify the commit that fixes this bug in v4.19.  We first need to identify the last bad kernel version and the first good kernel version."
1788997,2018-09-16 12:57:53 UTC,found how to set the tag and marked status as confirmed.
1788997,2018-09-15 10:34:42 UTC,I don't know how to add a tag to or mark this bug track. :-;
1788997,2018-09-15 10:21:35 UTC,"I've tested with the kernel as recommended and suggest in #25. Wifi with rtl8723b3 works again (like a charm). However, ant_sel must be set to 1 (ant_sel=1) as opposed to kernel 4.15.0-32, which required ant_sel to be set to 2 (ant_sel=2). (e.g sudo modprobe rtl8723be ant_sel=1 vs. sudo modprobe rtl8723be ant_sel=2)."
1788997,2018-09-13 20:00:09 UTC,"I'll ping upstream and the author of the patch that was reverted.  However, before doing so, we should test the latest mainline kernel to see if the bug is already fixed upstream."
1788997,2018-09-13 19:18:48 UTC,A new kernel update 4.15.0.34 has been provided recently. This kernel doesn't work with / support rtl8723be either. It seems the fix has not been committed so far.
1788997,2018-08-29 13:12:11 UTC,"Hello,
I have difficulties trying your test kernel.
maybe because I use signed kernel with secure boot ?"
1788997,2018-08-28 20:36:12 UTC,Thx! With the test kernel from http://kernel.ubuntu.com/~jsalisbury/lp1788997 according to #21 wifi of the laptop HP 1S-af023ngof works again. So reverting  commit af8a41cccf8f469165c6debc8fe07c5fd2ca501a seems to fix the bug.
1788997,2018-08-28 11:57:08 UTC,"Same story here with HP 17-y009ng, 16.04 worked like a charm, with ant_sel=2 ( after having had a hard time to find  out that this option was a must)."
1788998,2019-03-11 17:54:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1788998,2018-08-25 11:11:25 UTC,Do you have any examples of apps that use this?
1788998,2018-08-25 11:33:57 UTC,"No, not that I know of."
1789005,2020-01-23 08:35:40 UTC,"Hi, this bug has been reported to GitLab: https://gitlab.com/inkscape/inbox/issues/1327"
1789007,2018-11-09 14:11:54 UTC,"Somewhat related - resetting to defaults, which is a special case of this: https://bugs.launchpad.net/kicad/+bug/1502656"
1789007,2019-04-17 19:41:27 UTC,"It should be useful also to be able to save/load the visibility settings for layers with the colors.
Example:
In my usual workflow, after routing a board I have to correct the silk screen re-positioning a lot of text. Usually I hide anything like routes and bottom layer, showing only the  top pads, the silk screen and the vias in order to place the reference designators correctly.
Being able to load a color combination with the visibility settings would speed-up the process."
1789007,2019-04-17 20:13:00 UTC,"I agree, I'm working on that for 6.0"
1789008,2018-08-30 07:44:08 UTC,I opened a new bug for problem 1 (confirmation needed before overwriting a template).
1789008,2018-08-30 12:12:27 UTC,Thank you (and sorry for not having done that right away...)!
1789008,2020-06-19 13:53:47 UTC,"Closing because I can't reproduce this on Inkscape 1.0 (4035a4fb49, 2020-05-01).
Saving files always seems to correctly save the zoom scale and position, even when overwriting existing files."
1789009,2018-09-29 13:31:01 UTC,looks like the core functionality of pcbnew is not about tracks and segments of track !?
1789009,2018-09-29 13:36:38 UTC,here (video4) the 'Z' is unwanted.
1789012,2018-12-22 08:37:11 UTC,"Using Grsync to perform a remote to local backup works OK (grsync 1.2.6/ubuntu 18.04 LTS), just run on the local server ssh-keygen then ssh-copy-id to the remote server and grsync will complete sync not asking for the password."
1789012,2019-01-27 00:05:15 UTC,This might be related to the issues with ssh-askpass which I reported in bug #1812247
1789012,2020-01-02 18:05:18 UTC,One of my users is also affected.
1789012,2020-01-02 18:05:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789012,2020-03-09 04:25:10 UTC,"I experience the same issue, but can provide more details than those above.  Do I describe the same situation?"
1789014,2019-05-13 14:35:36 UTC,"@Nirmal
thanks for the feedback."
1789014,2019-05-13 09:03:30 UTC,"Dear RaiMan,"
1789014,2019-05-13 11:56:51 UTC,"@Nirmal
As stated on sikulix.com: no setup needed any more, just download and use it.
So what is the problem?"
1789014,2019-05-13 13:42:45 UTC,"@RaiMan,"
1789015,2019-05-21 12:11:19 UTC,"Thank you, Qantas94Heavy!"
1789015,2019-05-21 11:42:09 UTC,There was previously code for Gtk::AccelMap::load to load the file and use that for menu keyboard shortcuts. This has long since been removed and presumably replaced with some other way of handling this: https://gitlab.com/inkscape/inkscape/commit/222304de408e85f01ace7b5ec9f965440ff1079e
1789022,2018-12-22 09:50:15 UTC,"This forgotten issue still exists, also in Disco."
1789022,2019-01-25 08:36:45 UTC,The version 0.99.beta19-2ubuntu1 does not take this into account.
1789022,2019-01-25 15:27:26 UTC,The bug was fixed with the 0.99.beta19-2ubuntu2 update.
1789023,2018-08-25 17:02:50 UTC,The widelands package/metadata needs fixing for it to appear. See http://appstream.ubuntu.com/cosmic/universe/issues/widelands.html
1789023,2018-08-25 18:58:37 UTC,This bug was fixed in the package widelands - 1:19+repack-4ubuntu1
1789023,2018-09-06 20:13:57 UTC,"Hello GunChleoc, or anyone else affected,"
1789023,2018-09-07 19:42:11 UTC,Tested 1:19-ppa0-bzr8809-201809071017~ubuntu18.04.1
1789023,2018-09-13 07:47:51 UTC,This bug was fixed in the package widelands - 1:19+repack-4ubuntu0.18.04.1
1789023,2018-09-13 07:47:56 UTC,"The verification of the Stable Release Update for widelands has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1789023,2019-04-22 07:47:56 UTC,Fixed in build20-rc1
1789027,2018-10-21 22:41:53 UTC,"Hi, sorry I thought that was clear already. I'm seeing two keyboard shortcuts where the cursor isn't captured: Shift+PrtScr and Alt+PrtScr. I filed this issue because I wanted to be able to capture the cursor in selection captures and not have to crop images afterward."
1789027,2018-09-13 06:53:07 UTC,Is the problem only appearing when using (some) keyboard shortcuts for screen capture?
1789029,2018-08-29 14:44:07 UTC,I can confirm. The version of Libreoffice in Ubuntu 16.04 (5.1.6) is not affected.
1789029,2018-08-29 14:46:11 UTC,This also affects the snap package.
1789029,2018-12-13 09:24:44 UTC,"I have version 6.1.3.2 and on both Cosmic and Disco distributions, a Presentation with an Inserted video ignores video page size of the projection Screen.  For example, a 16:9 video is displayed in 4:3 on the projection screen,ie full screen.  Also, the contolling screen for advancing the presentation is similarly overwritten by the video image.  Even when a 4:3 video image is shown it totally occupies the 16:9 contolling screen."
1789029,2019-02-04 23:43:36 UTC,I have found a solution to this problem that works for me at: https://ask.libreoffice.org/en/question/157815/impress-6-in-ubuntu-1804-video-playback-only-as-full-screen/
1789035,2019-03-06 23:19:30 UTC,Same problem on an old HP NX7010 Laptop with i386 and forcepae install.
1789035,2019-03-06 23:19:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789036,2018-08-27 02:21:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789036,2018-08-27 02:22:47 UTC,"The login screen is mostly driven by 'gnome-shell' code still, so that might be where a fix will go."
1789046,2019-07-20 18:29:40 UTC,"Reviewed:  https://review.opendev.org/671045
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=6f4742457fae755e465315f17f39c3977c833d0e
Submitter: Zuul
Branch:    master"
1789046,2018-11-04 19:23:10 UTC,"Change abandoned by Akihiro Motoki (<email address hidden>) on branch: master
Review: https://review.openstack.org/596612
Reason: I have no plan to work on Django 2.1 support in Stein timeframe."
1789046,2018-09-06 09:18:33 UTC,"Reviewed:  https://review.openstack.org/596611
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=00c5814313d8af8ff71ed3e8ea9c0883eb3947f4
Submitter: Zuul
Branch:    master"
1789046,2018-09-06 07:45:25 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/596611
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1789046,2018-09-06 07:45:19 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/596612
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1789046,2018-08-26 16:58:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/596611"
1789046,2018-08-26 16:57:18 UTC,"I am not sure the horizon team has enough development resources to catch up with every Django releases. IMHO, considering the current situation, only Django LTS support might be a candidate."
1789046,2018-08-25 20:20:32 UTC,"Hi. While submitting this bug, I understood the problem. As I'm building for Debian Experimental, django 2.1 is being taken from there, instead of Django 1.11 from Sid. And that's the issue: Horizon current has a problem with Django 2.1, not with Python 3.7. So it's still a problem, but not as urgent as I once thought (Buster will be released with Django 1.11). I renamed the title of this bug accordingly."
1789046,2018-08-26 16:58:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/596612"
1789058,2018-08-27 10:57:53 UTC,+ Turn Silk rendering on/off
1789058,2018-08-27 17:20:53 UTC,"Oh, that is good, Tim."
1789071,2018-08-26 07:41:50 UTC,"On Lubuntu 18.10 daily build 08-26 the bug is the same, attached photo with proof."
1789071,2018-08-26 07:55:32 UTC,"Forget the kernel panic - I dd the stick again and left it for some time in the USB port.
18.04.1 from lubuntu.me works very well."
1789071,2018-08-26 17:01:12 UTC,"Since you had problems with the verified torrent, perhaps you should
ensure that you have no such problems with with the daily build. Make
sure you have verified the download, make sure you `dd` it, and make
sure you run ""Check disc for defects"" at the boot menu."
1789071,2018-08-27 17:43:09 UTC,"Downloading ISO's:
wget -c http://cdimage.ubuntu.com/lubuntu/daily-live/20180827/cosmic-desktop-i386.iso
mv cosmic-desktop-i386.iso cosmic-desktop-i386-lubuntu-0827.iso
wget -c http://cdimage.ubuntu.com/xubuntu/daily-live/20180827/cosmic-desktop-i386.iso
mv cosmic-desktop-i386.iso cosmic-desktop-i386-xubuntu-0827.iso
mkdir lubuntu
mkdir xubuntu"
1789071,2018-08-27 17:44:41 UTC,Lubuntu 18.10 0827 /var/log/syslog
1789071,2018-08-27 17:46:00 UTC,Lubuntu 18.10 0827 /var/log/Xorg.0.log
1789071,2018-08-27 18:07:39 UTC,Xubuntu 18.10 0827 /var/log/syslog
1789071,2018-08-27 18:08:41 UTC,Xubuntu 18.10 0827 /var/log/Xorg.0.log
1789071,2018-08-27 18:09:26 UTC,Xubuntu 18.10 0827 lsmod
1789071,2018-08-27 18:36:22 UTC,On phone proof picture see [ ->| ] mouse cursor at invisible right edge of invisible terminal window.
1789071,2018-08-27 18:25:17 UTC,Lubuntu 18.10 0827 lsmod
1789071,2018-08-27 18:48:48 UTC,"Initially the lxqt-powermanagement message does not appear. After I press CTRL+ALT+T in Lubuntu 18.10, the entire desktop flickers and the lxqt-powermanagement message appears and the mouse cursor dissapears, when I move the mouse cursor it reappears at the edges of the desktop and dissapears to the center of the desktop. Tested in virtualbox on another computer with settings 512 MB RAM and PAE enabled and works very well there."
1789071,2018-08-27 18:51:00 UTC,"Use ScreenGrab to take the screenshot in Lubuntu 18.10. Screenshooter in
Xubuntu. Grainy phone pics and YouTube videos are really not helping."
1789071,2018-08-27 18:57:29 UTC,"I can let you ssh into the Lubuntu 18.10 live cd at a specified UTC time if the ram can accomodate installing openssh-server, can install additional 256MB ram but it's at 333Mhz not 400 Mhz. I tested port forwarding on router ssh working from another location."
1789071,2018-08-27 19:00:46 UTC,Tommorow I will post the screenshots if I discover how to do them.
1789071,2018-08-27 22:34:51 UTC,"-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
"
1789071,2018-08-27 23:57:41 UTC,"One more thing. The corrected version is actually in proposed:
https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati/1:18.0.1-2"
1789071,2018-08-26 05:59:26 UTC,"Do you have the same problem with other flavors of Ubuntu? What about
other versions of Lubuntu?"
1789071,2018-08-27 18:11:09 UTC,"I need a screenshot from both the system that works and the one that
doesn't with a clear indication of what's wrong."
1789071,2018-08-26 07:41:18 UTC,"On Lubuntu 18.04.1 i386 from lubuntu.me I have kernel panic on try and install, verified torrent, attached photo.
On Lubuntu 18.04 i386 from lubuntu.net it works very well.
On Xubuntu 18.10 i386 daily build 08-26 it works very well."
1789071,2018-08-26 06:36:03 UTC,"i386 Ubuntu CD's are fewer.
I will try today from http://iso.qa.ubuntu.com/qatracker/milestones/390/builds
and report back on the other i386's I see there:"
1789071,2018-08-26 06:46:48 UTC,"and make sure to try already released versions of Lubuntu rather than
just dailies."
1789074,2018-08-30 15:44:38 UTC,"Okay, on IRC today, stephenfin reminded me that upstream, the configurable RX/TX Queue Size code is new in Rocky, but that OSP backported it all the way back to Newton. That's why Moshe is seeing the feature code in OSP10-OSP13."
1789074,2018-08-30 16:29:30 UTC,"If the regression is also in OSP13, can you backport to queens aswell?"
1789074,2019-03-22 03:48:05 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1789074,2018-09-24 14:46:57 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1789074,2018-09-14 05:54:47 UTC,"Reviewed:  https://review.openstack.org/599506
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e7ac7a1e03b9d703c42a3eea45594ab5980e4b7f
Submitter: Zuul
Branch:    stable/rocky"
1789074,2018-09-04 07:09:42 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599506"
1789074,2018-08-29 23:17:28 UTC,Patch is proposed here: https://review.openstack.org/595592
1789074,2018-08-30 20:59:13 UTC,"Noam, this bug is for tracking upstream only. The OSP teams will take care of backporting fixes to OSP, separately, after this fix is reviewed and merged on master."
1789074,2018-08-30 16:39:27 UTC,Let first get it merged in master :)
1789074,2018-08-30 03:59:02 UTC,Sorry I meant backport to ocata not queens
1789074,2018-08-30 03:58:20 UTC,"from the github I see that we need to backport to queens, but I may introduce in earlier openstack releases"
1789074,2018-08-29 23:23:50 UTC,"Previous discussion about this bug thought this is a regression in Rocky, but the bug report says it was seen in OSP13 (which is Queens). The bug report also says it could go back as far as Newton. Can anyone confirm how far back this will need to be backported?"
1789074,2018-09-03 18:41:11 UTC,"Reviewed:  https://review.openstack.org/595592
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=622ebf2fab0a9bf75ee12437bef28f60e083f849
Submitter: Zuul
Branch:    master"
1789080,2018-08-27 14:09:45 UTC,should work with latest build.
1789089,2018-08-27 02:35:28 UTC,Please report this bug to the PulseAudio developers here:
1789089,2018-08-27 07:16:12 UTC,Bug reported to PulseAudio GitLab. ID: 568
1789089,2018-08-27 07:41:04 UTC,Thanks
1789089,2018-10-24 01:52:15 UTC,"Fix committed upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/commit/fa2a7534772"
1789091,2019-08-13 11:00:21 UTC,"I can confirm this, it seems a re-run of apt upgrade makes it pass again?"
1789092,2020-04-06 21:02:42 UTC,Could you try if the current version fixes the issue for you?
1789092,2019-02-14 15:01:58 UTC,"That's known upstream, https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/4"
1789092,2018-10-16 06:11:02 UTC,"The same problem occures when the path contains characters like ""é""."
1789092,2019-02-14 15:16:20 UTC,"Could also be https://bugzilla.gnome.org/show_bug.cgi?id=795601 , does https://launchpad.net/ubuntu/+source/network-manager-applet/1.8.10-2ubuntu2 fixes the issue?"
1789095,2018-08-27 02:37:36 UTC,"When you say ""locks"", does that mean you can unlock it with a password?"
1789095,2018-08-27 07:40:41 UTC,"It's not a crash or a hang. It locks in terms of the screen being blank and the login password being required to unlock the screen. Also, I put this glitch down to the xorg package but I could be wrong."
1789097,2018-09-10 16:54:17 UTC,"As a workaround, could you try creating this file: /usr/lib/networkd-dispatcher/routable.d/10-winbind"
1789097,2018-12-16 13:12:47 UTC,So glad I took the time to report this.
1789097,2018-10-15 15:02:04 UTC,Upstream seems silent; bug remains in NEW state and no follow-up.
1789097,2018-09-10 19:06:50 UTC,Sure.
1789097,2018-09-10 18:06:07 UTC,"Actually, no, that doesn't work for me. Was expecting it would given the comments on the samba bug, but, well, no. It *does* work to send HUP once booted:"
1789097,2018-09-07 15:18:00 UTC,"As to the reply you got on https://bugzilla.samba.org/show_bug.cgi?id=13607, I can deny a ""net cache flush"" doing anything to get WINS name resolving going for me when booted with the original service file:"
1789097,2018-08-29 11:14:11 UTC,"Just to add: the issue's the same and fully constant on an Intel Xeon E5606 @2,13GHz with 8GiB running Mint 19 Cinnamon 64-bit, and an Intel Core 2 Duo E8400 @ 3GHz withj 4GiB running Mint 19 Xfce 64-bit."
1789097,2018-09-06 18:02:20 UTC,"basically if the interface is available when winbind starts, winbind keeps working if it's brought down and up again. But if winbind starts when the interface isn't available, then it won't recover without a restart. That's my finding so far."
1789097,2018-09-06 17:48:41 UTC,"> This is to say that I do not in fact have a WINS server specified; that judging by the logs
> my winbind is relying on broadcasts, and bombing out in that case if started before
> network-online.target.
"
1789097,2018-09-05 21:19:58 UTC,"Oh, and the mentioned vanilla smb.conf..."
1789097,2018-09-05 21:14:29 UTC,"Thanks much for checking. I see; I was expecting this to be an ""immediately obvious"" sort of thing to someone with unlike me an actual clue about samba/winbind, but I have with the above guidance nos supplied more information."
1789097,2018-09-05 19:34:19 UTC,"I'm trying to check why winbind won't recover from the network being down, so I setup a lxd container where I installed just winbind and the nss module."
1789097,2018-08-28 19:07:37 UTC,"Yes, the network itself comes up fine. ""Does not work"" simply means that NetBIOS name resolution is unavailable even after it does; that e.g. ""ping NAS"" for ""NAS"" the NetBIOS name of my, well, NAS, tells me the name cannot be resolved."
1789097,2018-08-28 18:12:53 UTC,Thanks for filing this bug in Ubuntu.
1789097,2018-09-06 18:02:36 UTC,"Ah, and that's only in the ""no wins specified"" case, otherwise it recovers just fine."
1789101,2018-08-26 14:15:18 UTC,"Solution found. Whilst playing the mp4 file in vlc: in Settings->Sound->Applications, check that 'VLC Media Player' is shown as 'On' and that the level is 'above zero' (i.e. somewhere on th right)"". As soon as I modified the level to be 'above zero' sound played. This also corrected no sound in Totem. What's confusing is that the volume shown by clicking the sound icon on the top right of the screen is shown  as being to the level you set it at but there is no indication for
an app (e.g. vlc) which is playing. Ubuntu remember the sound setting for vlc if you quit vlc (when the Applications line for vlc is no longer displayed) and start it again. This makes it even more confusing."
1789101,2018-08-27 09:35:04 UTC,"Seems like a bug in the gnome part controlling pulseaudio, but not like a vlc issue. Re-assigning to gnome since I don't know a better place for this bug."
1789109,2018-11-07 02:20:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789114,2018-09-15 18:42:57 UTC,Any update on this bug?
1789114,2018-08-27 02:02:03 UTC,Please send us:
1789114,2018-08-28 02:04:48 UTC,Thanks.
1789114,2018-08-28 02:14:44 UTC,Hello Daniel
1789114,2018-08-27 15:34:53 UTC,Hello Daniel
1789125,2018-08-26 20:21:34 UTC,I just found out that if you right click and select open in another tab the Netflix plank item gets a dot under it and clicking on it takes you to the new tab but clicking on the chromium logo still takes you to Netflix.
1789126,2018-08-26 20:11:50 UTC,Request also added for symbol libraries here: https://bugs.launchpad.net/kicad/+bug/1789127
1789126,2018-08-29 23:53:48 UTC,Realized that I forgot to include my version information. Here it is:
1789126,2019-10-09 13:14:08 UTC,I think it would be good to use a grid which has built-in sorting when clicking on the headers.
1789127,2018-08-26 20:11:53 UTC,Request also added for footprint libraries here: https://bugs.launchpad.net/kicad/+bug/1789126
1789127,2018-08-29 23:53:55 UTC,Realized that I forgot to include my version information. Here it is:
1789130,2018-08-28 02:01:31 UTC,"I just tried again on a fresh install, and noted this in syslog:"
1789135,2018-08-26 21:30:04 UTC,This change was made by a bot.
1789135,2018-08-26 21:30:14 UTC,"   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-100-generic)
   dpkg: error processing package linux-image-3.13.0-100-generic (--configure):
    subprocess installed post-installation script returned error exit status 2"
1789135,2018-08-27 18:12:19 UTC,You may need to run the following from a terminal:
1789139,2019-06-16 06:18:12 UTC,Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918623
1789143,2018-09-14 07:06:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789157,2020-01-20 22:00:53 UTC,"Change abandoned by Maciej Józefczyk (<email address hidden>) on branch: master
Review: https://review.opendev.org/671293
Reason: It will go to dedicated repository."
1789157,2020-01-15 16:47:05 UTC,"Reviewed:  https://review.opendev.org/701932
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=c6e5339d3d392342d643d777263064f4a7f7a9aa
Submitter: Zuul
Branch:    stable/train"
1789157,2018-10-26 15:16:07 UTC,"Reviewed:  https://review.openstack.org/608252
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=032872d93bfbac451f2b983e242f03a77d16d5c9
Submitter: Zuul
Branch:    master"
1789157,2018-11-14 10:56:55 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/608203"
1789157,2018-10-05 10:23:46 UTC,Marking it as in progress because it still lacks tests and documentation.
1789157,2018-08-27 05:41:30 UTC,https://review.openstack.org/#/c/577395/
1789157,2020-01-10 11:08:49 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/701932"
1789162,2018-08-27 06:37:09 UTC,"This only happens when I try to play a file live from the media manager, or add a media file to a service. However, if I open a service with media files in it, I can play those media files. I just can't add any new ones."
1789162,2018-10-21 14:25:32 UTC,try installing (or updating) VLC Player
1789164,2018-08-31 19:20:26 UTC,That's really weird.  I didn't even think grub showed up on a second monitor at all.  What if you press C to go to the command line and type a few characters?  As you type do they show up differently?
1789164,2018-09-11 12:46:24 UTC,"I press e and edit the boot command, then there is an instant reaction to the keyboard on all monitors, only the indicator in the main and sub-menu of grub seem to be affected."
1789168,2018-08-27 08:20:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1789169,2018-08-27 08:20:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1789169,2018-08-27 08:45:42 UTC,"There is a workaround. Don't use startx at all.
Use under root following:
xinit /usr/bin/blackbox
After that X starts.
Under root. And it's possible to sudo su - to
user and then root programs under it.
However under common user command:
xinit /usr/bin/blackbox
won't start."
1789170,2018-08-27 08:20:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1789176,2019-03-03 06:15:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789184,2018-10-04 09:49:06 UTC,This bug was fixed in the package hplip - 3.18.7+dfsg1-2ubuntu1
1789184,2018-10-03 14:27:37 UTC,"I have looked into the source code and it does not look much like a distro incompatibility, but seeing all what got commented out it looks like a half-hearted removal of some of the available actions to apply on a device (""Actions"" tab)."
1789184,2018-09-05 07:43:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789184,2018-09-18 11:42:37 UTC,Ubuntu 18.10 is not yet supported in hplip as the stable version of 18.10 is not yet released. We will enable the Ubuntu 18.10 support in hplip once the stable version is released.
1789184,2018-09-17 12:04:45 UTC,This bug is reported for 18.10. I don't have an 18.04 system to confirm if it exists or not on this release.
1789184,2018-09-17 11:55:35 UTC,"Hi,
Can you confirm on the distro version? We are yet to support the Ubuntu 18.10 in hplip driver. The latest Ubuntu version been supported in hplip is 18.04. Do you see any issues in Ubuntu 18.04?"
1789184,2018-10-03 07:12:07 UTC,"If the policy is to wait for the release to be stable to update hplip, it means that hplip will always be one release off and won't work on the latest release until the changes are SRUed.
Besides SRUing large set of changes is huge and much more work than releasing a new version to the development release. Which changes also have to be approved by the SRU team.
Finally, hplip is on Ubuntu and several flavors's ISO which won't be recreated after the release and will include a broken version of hplip."
1789185,2018-08-28 07:40:38 UTC,"I am using heat from July 2018. This is the SHA: 9e463f4af77513980b1fd215d5d2ad3bf7b979f9
I am using Tacker from July 2018. This is the SHA: 7d0c22524ac8352a50af2e017eed4b5be28d4c31"
1789185,2018-09-03 13:45:17 UTC,I am sorry because I can not produce that error in devstack.
1789185,2018-09-21 06:46:14 UTC,"Sorry, I don't see any heat logs to tell what's the issue where. I'm not sure why the signature would be missing for ec2 auth at the first place."
1789185,2018-08-28 05:31:23 UTC,"Can you give me tacker and heat version, and VNF descriptor too? I will check it asap. Thanks."
1789187,2018-08-27 12:57:21 UTC,Looks like related to https://bugs.launchpad.net/gdb-linaro/+bug/711375
1789187,2018-09-12 11:03:03 UTC,"Hi,"
1789194,2018-08-27 10:48:21 UTC,"in 2.4 it looks like we added API version 2 which allows you to pass >1 backup to remove.
However, it seems the 2.4 client always assumes a 2.4 server:
The client side code calls Remove, doesn't pay attention to the facade version and assumes len(results) == len(ids):
func (c *Client) Remove(ids ...string) ([]params.ErrorResult, error) {
 if len(ids) == 0 {
  return []params.ErrorResult{}, nil
 }
 args := params.BackupsRemoveArgs{IDs: ids}
 results := params.ErrorResults{}
 err := c.facade.FacadeCall(""Remove"", args, &results)
 if len(results.Results) != len(ids) {
  return nil, errors.Errorf(
   ""expected %d result(s), got %d"",
   len(ids), len(results.Results),
  )
 }
 return results.Results, errors.Trace(err)
}"
1789194,2018-08-27 10:49:33 UTC,"This is a regression, as 2.4 is now passing the object to remove as a list in IDs, but the 2.3 server expects it as a single value in the ID field. So its fairly import to fix."
1789196,2020-07-24 10:42:40 UTC,"OBE: liberty is no longer supported, so bug does not need addressing."
1789197,2019-06-02 05:14:52 UTC,"Yes I'd still like to see this happen,
mostly to help customers deploy with it."
1789197,2019-02-12 13:23:20 UTC,Is this something you still would want?
1789198,2018-11-21 12:13:24 UTC,Change proposal at https://review.openstack.org/#/c/596694/
1789200,2019-07-18 10:39:01 UTC,Zoom out should be equal or greater than the biggest of either the PCB's largest dimension fitting into smallest viewport dimension or the PCB's real size taking monitor DPI into account to be able to represent a PCB's true size.
1789200,2020-03-12 09:42:06 UTC,"The bug for me shows itself on and off when I add/remove footprints to my board.
It seems to be an issue with the code that estimates the board size."
1789200,2020-04-07 15:26:51 UTC,"KiCad has migrated to Gitlab, this issue is available here: https://gitlab.com/kicad/code/kicad/-/issues/2231"
1789204,2018-08-28 02:07:43 UTC,I can see that you have installed an 'NVIDIA Corporation GK208 [GeForce GT 710B]' and it is using the default driver called 'nouveau'.
1789204,2018-10-27 04:17:45 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1789204,2018-10-29 09:40:11 UTC,The problem is solved with last update!
1789205,2019-05-14 11:46:55 UTC,There has been a lot of effort to improve designate and designate-bind communication over the last release. I'm going to mark this as incomplete pending further reproduction.
1789205,2019-07-14 04:17:35 UTC,[Expired for OpenStack Designate-Bind Charm because there has been no activity for 60 days.]
1789214,2018-08-27 18:08:10 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1789214,2018-08-27 18:44:39 UTC,"> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
"
1789214,2018-08-28 18:59:06 UTC,Good evening!
1789214,2018-11-24 12:08:38 UTC,"Just for information, that trying out Ubuntu 18.10 kernel 4.18.0-10-generic booting from USB pen, the problem remains (and the intel_idle.max_cstate=1 workaround still works)."
1789214,2018-08-27 14:00:06 UTC,This change was made by a bot.
1789215,2018-10-01 16:02:51 UTC,This bug was fixed in the package linux - 3.13.0-160.210
1789215,2018-09-13 11:03:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1789215,2018-09-17 09:41:22 UTC,Boot tested on relevant HW.
1789215,2018-08-27 14:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1789239,2019-02-26 02:55:56 UTC,murano master branch fixed this bug in: https://review.openstack.org/#/c/637346/
1789239,2019-02-27 03:55:53 UTC,"Reviewed:  https://review.openstack.org/639244
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=69b6bf358693e44f20fd5f8f7d07fdabaa2cc647
Submitter: Zuul
Branch:    stable/rocky"
1789241,2018-11-01 01:21:05 UTC,Should we have bugs here or in https://github.com/juju-solutions/layer-filebeat/issues/new ?
1789241,2018-11-01 14:38:44 UTC,"The issue may not be in the filebeat layer itself, so I think it's fine to have bugs here - and in layer-filebeat if that layer is the one that is actually buggy"
1789241,2019-05-14 13:03:48 UTC,This PR to beats-base fixes the issue: https://github.com/juju-solutions/layer-beats-base/pull/35
1789241,2019-07-31 19:45:57 UTC,"With juju 2.6 environments not running config-changed on reboot, filebeat is not starting on reboots of new/updated clouds due to this issue."
1789241,2019-07-31 20:25:08 UTC,PR has been committed.
1789241,2019-07-31 21:02:23 UTC,This has been released to candidate as rev 26:
1789241,2018-12-28 10:39:26 UTC,"Looked into this issue, it seems the issue is actually in layer:beats-base (https://github.com/juju-solutions/layer-beats-base) in the function 'enable_beat_on_boot'"
1789242,2018-09-17 11:58:50 UTC,"Hi,
Linux Mint 19 support is yet to be added in hplip driver and this distro version support in hplip driver will be available in the September month release. Please check for the latest release information in hplip developer portal by this month end for Linux Mint 19 support in hplip driver."
1789244,2019-12-28 12:55:13 UTC,"Hello,"
1789244,2018-08-29 08:27:34 UTC,"As requested,"
1789244,2018-08-28 17:16:41 UTC,Thank you for getting back to me and for your suggestion and I did run the following command in the terminal;
1789244,2018-08-28 02:11:44 UTC,"With Ubuntu and Linux you don't usually need to install any drivers. It does however look like pulseaudio is failing on the machine, which will cause loss of sound:"
1789244,2018-08-29 01:55:53 UTC,It sounds like /etc/pulse/daemon.conf might still need fixing. Can you please attach yours here?
1789247,2020-04-06 01:31:46 UTC,"Ouch! This just seems to be some (default) theme problem. Menu entries hard-to-read light-gray text on lighter-light-gray background, but they work! Please feel free to close this bug. Or should this be moved over to 'themes department' (which package would that be)?"
1789251,2018-08-27 19:29:44 UTC,"Hi Sebastian,"
1789251,2018-08-28 08:29:39 UTC,"Hey Jeff,"
1789251,2018-08-29 20:46:18 UTC,"Got it.  Yes, those would be useful."
1789251,2019-08-21 19:46:24 UTC,"Also move the column order by draging-drop the actual column.
This should also affect (after) the order that the field will appear in each component."
1789251,2019-08-21 19:51:36 UTC,"Delete/rename should not be allowed to: Reference, Footprint, Value, Datasheet and other KiCad (ngspice) specific field."
1789252,2018-12-29 19:45:24 UTC,I have the same problem with the touchpad of my lenovo v130-15ikb
1789252,2018-12-18 11:28:57 UTC,"Same problem:
Ubuntu 18.04.1 x64 with standard kernel doesn't recognize the touchpad.
No touchpad functionality."
1789252,2018-12-07 14:29:33 UTC,"I had the same problem with the Lenovo V130-14IGM: No touchpad functionality.
I tried with Ubuntu 18.10, compiling the kernel with mm's one-line-modification. Kernel 4.18... current one - I don't remember.
But back on 18.04, with my own kernel, it succeeded. Kernel 4.15.0-42.45."
1789252,2018-10-21 20:17:36 UTC,"Please include the touchpad of Lenovo V130-14IGM in the kernel.
I hope for a quick solution, as this should not be a big thing."
1789252,2018-11-12 09:51:12 UTC,I'm also affected and installing the latest mainline kernels somehow does not fix this issue. Can somebody please upload a self-compiled kernel? Thanks in advance.
1789252,2018-11-06 20:52:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789252,2018-10-08 06:25:44 UTC,I have a brand new Lenovo 130-15IKB and have discovered the touchpad is ELAN0620:01.  Seems like this whole line of touchpads needs to have support added in the kernel.
1789252,2018-11-17 13:12:41 UTC,"I habe the same problem. Bought a new laptop yesterday and can't use it good because of this bug. It is such a small change :( I tried to build a kernel on my one without success. My laptop shows me ELAN0618 when i type in ""dmesg | grep -i elan""."
1789252,2019-05-10 09:42:30 UTC,"According to commit on github, the elan0615 might be supported in kernel 5.1"
1789252,2019-05-11 15:43:29 UTC,"The 5.1 mainline kernel basically works for me - ""ELAN0615 was added, touchpad is working."
1789252,2019-05-23 07:12:32 UTC,On my Lenovo V130-14IGM with xubuntu 18.04 with custom kernel I CAN suspend.
1789252,2019-05-17 12:52:26 UTC,"Same issue here, v130-14IGM and Ubuntu 19.04, the touchpad is not recognized and doesn't work."
1789252,2019-05-20 14:04:32 UTC,"Hi, I actualized my kernel to 5.1.3 and now the touchpad works! But still have problems with the suspend mode. I have a Lenovo v130-15IGM, Ubuntu 19.04 x64"
1789256,2019-05-31 14:41:36 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Kyle and Garry!"
1789256,2019-05-24 21:58:50 UTC,Thanks Kyle.  It works as advertised.  A signed off branch is at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1789256-monograph-part-in-check-out-signoff
1789256,2019-05-24 19:57:42 UTC,I've pushed a branch for this here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1789256-monograph-part-in-check-out
1789257,2019-05-31 14:34:33 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Kyle and Garry!"
1789257,2019-05-24 17:18:59 UTC,I've pushed a branch here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1789257-items-out-monograph-part
1789257,2019-05-24 18:40:37 UTC,Works perfectly.  Signed-off at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1789257-items-out-monograph-part-signoff
1789263,2018-09-12 14:58:55 UTC,Evergreen release 3.0.11
1789263,2019-04-26 16:06:01 UTC,Still an issue in Evergreen 3.2. I'm also adding a reference to bug 1130389. Any fix to allow unsetting a stat cat should not reintroduce the blank stat cat entry issue reported in 1130389.
1789263,2019-11-12 22:44:33 UTC,This bug is still an issue in Evergreen version 3.3.4 for PAILS SPARK group libraries.
1789263,2021-02-12 01:02:11 UTC,Continues to be an issue in 3.5 and 3.6.
1789267,2018-08-27 18:55:00 UTC,"A little correction to the above note: in bug #911426, the problem with seahorse keyring not being updated was observed when gnome-control-center was used. In this present case, the problem is observed when ""passwd"" is used."
1789288,2019-06-25 01:51:09 UTC,I cannot reproduce this on current 2.6.4. I must have been fixed as part of other work in the area.
1789292,2020-02-17 19:41:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789296,2018-08-27 20:48:01 UTC,"For future reference, I'm referring to the ""open-ils.circ.hold.cancel"" API."
1789296,2018-08-29 01:17:57 UTC,+1 to this proposal
1789296,2019-03-25 17:45:38 UTC,Related bug: #1780315
1789296,2019-03-25 17:46:24 UTC,https://bugs.launchpad.net/evergreen/+bug/1780315
1789298,2019-04-12 03:02:29 UTC,"On Thu, 11 Apr 2019, Kasia Gauza wrote:

>   info missing help docs ""info info"" and ""H"" command return error
>   The info command in Ubuntu 18.04 lacks it's own info page. This means
"
1789298,2019-04-11 15:09:27 UTC,"Confirmed, 'info info' and 'h' from within 'info' doesn't work on Ubuntu 18.04.2, Info ver: 6.5.0.dfsg.1-2"
1789298,2019-03-25 20:19:32 UTC,"""info info"" doesn't work: info: No menu item 'info-stnd' in node '(dir)Top'"
1789298,2019-04-11 15:07:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789314,2018-08-27 23:25:39 UTC,ubuntu_nbd_smoke_test failed.
1789317,2018-08-28 03:38:01 UTC,same problem as with #1713889
1789317,2018-09-05 08:23:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789317,2018-09-05 08:23:55 UTC,still happens on 18.04
1789321,2019-06-18 13:54:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789332,2018-08-28 04:18:40 UTC,There's a dashboard for Grafana already written for this: https://grafana.com/dashboards/2842
1789332,2019-12-15 06:41:25 UTC,"The design goal with the manager's Prometheus exporter is that it gains high availability directly via the Ceph cluster, so probably should pass all monitor IPs to Prometheus"
1789332,2020-04-09 08:57:12 UTC,"Reviewed:  https://review.opendev.org/716299
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=425c078299b6e177fc160ab44c55ca814c92dc75
Submitter: Zuul
Branch:    master"
1789333,2018-08-29 05:48:51 UTC,"The bug is indeed fixed in the latest v4.15 stable kernel:
$ uname -a
Linux apol1 4.15.18-041518-generic #201804190330 SMP Thu Apr 19 07:34:21 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1789333,2018-08-28 04:00:07 UTC,This change was made by a bot.
1789333,2018-08-28 15:44:12 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 stable kernel[0].
1789333,2018-08-28 15:57:44 UTC,"Okay, I will test this when I get back at home later this evening (EST time). The WiFi at my workplace works fine. Not sure why it selectively fails to work with my home WiFi. If you want to gather any additional info about what differences could be involved please let me know."
1789336,2019-05-14 08:00:50 UTC,"Hello Robert, or anyone else affected,"
1789336,2019-05-30 10:03:31 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.12
1789336,2019-05-14 21:54:29 UTC,Tested gnome-software 3.20.5-0ubuntu0.16.04.12 it shows the Skype publisher name with the appropriate tick icon.
1789336,2019-04-25 13:57:18 UTC,"An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: ""Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.""."
1789336,2018-09-21 08:01:11 UTC,"Hello Robert, or anyone else affected,"
1789336,2018-10-17 19:43:05 UTC,"The verification of the Stable Release Update for snapd-glib has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1789336,2018-10-22 08:33:35 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.4
1789336,2018-09-06 12:30:38 UTC,"Hello Robert, or anyone else affected,"
1789336,2018-09-21 13:14:18 UTC,Updated Bionic to proposed:
1789336,2018-10-17 19:42:50 UTC,This bug was fixed in the package snapd-glib - 1.43-0ubuntu0.18.04.1
1789338,2018-09-05 01:23:41 UTC,This bug was fixed in the package gnome-software - 3.30.0-0ubuntu1
1789338,2018-09-06 12:30:48 UTC,"Hello Robert, or anyone else affected,"
1789338,2018-09-21 08:01:18 UTC,"Hello Robert, or anyone else affected,"
1789338,2018-09-21 13:07:37 UTC,Installed on Bionic from proposed:
1789338,2018-09-21 13:13:28 UTC,"Hmm. Marking as verification-needed again, because the wide scope searches seems to be returning some strange results."
1789338,2018-10-16 03:34:55 UTC,"Will, are you still seeing this issue? I don't think it is related to this change (this only adds an additional flag to be sent to snapd and may cause more results to be returned than before)."
1789338,2018-10-16 08:30:08 UTC,"I'm trying to remember how the ""strange results"" manifest themselves.  Today, when I search in G-S for ""Stellar"" I get good results.  From what I can remember in BRU, we were getting additional non-matching results.  I dont see anything wrong today."
1789338,2018-10-17 19:42:50 UTC,This bug was fixed in the package snapd-glib - 1.43-0ubuntu0.18.04.1
1789338,2018-10-17 19:43:08 UTC,"The verification of the Stable Release Update for snapd-glib has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1789338,2018-10-22 08:33:35 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.4
1789340,2019-11-21 06:06:24 UTC,Issue is still seen with Openstack Stein branch.
1789340,2018-08-28 04:43:27 UTC,"Attaching nova compute logs,"
1789347,2018-08-28 07:05:51 UTC,Nevermind- it works with qemu 3.0.0 :)
1789351,2018-08-28 13:21:57 UTC,"I suspect that != line should be changed to ""is not"" for an object identity comparison instead of equality comparison."
1789351,2018-08-30 06:07:35 UTC,"As commented by Doug in comment #1 changing != to ""is not"" is fixing the issue, but I wonder why it occurs only for python3."
1789351,2018-09-04 12:03:16 UTC,"In a recent oslo.config change[1] , it will call ""versionutils.report_deprecated_feature"" if the option is deprecated when getting the option."
1789351,2018-09-04 16:14:27 UTC,"Applications should not need to worry about registering options used by libraries, so don't make that change, please."
1789351,2018-09-05 02:20:26 UTC,"Compare the contents is not very needed. After thinking again, I'm OK with ""if not"" now. It won't break the logic IMO."
1789351,2018-09-05 06:51:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599936"
1789351,2018-09-05 07:02:57 UTC,Fixed in keystonemiddleware.
1789351,2018-09-05 07:48:13 UTC,@Abhishek good to track the issue(mentioned in the report and setting registry_host in glance api v2) found in glance in a separate bug so those are worked upon :)
1789351,2018-09-07 06:22:21 UTC,"Reviewed:  https://review.openstack.org/599936
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=4fb7fef1eab2a981b8e366091073b6ee2d80ee6a
Submitter: Zuul
Branch:    master"
1789351,2018-09-07 15:59:15 UTC,This bug was fixed in the package python-keystonemiddleware - 5.2.0-0ubuntu2
1789351,2018-10-24 17:18:51 UTC,This issue was fixed in the openstack/keystonemiddleware 5.3.0 release.
1789352,2018-08-28 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1789352,2018-08-28 08:20:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1789352,2018-09-05 13:35:42 UTC,new nvidia p2000 lspci info
1789353,2019-05-29 03:00:20 UTC,"Hi Steve,"
1789353,2019-05-24 22:36:33 UTC,"Hi Po-Hsu,"
1789353,2018-08-28 06:28:42 UTC,"On this ARM64 node (4.4.0-134-generic #160~14.04.1-Ubuntu):
$  grep STACKPRO config-4.4.0-134-generic
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
CONFIG_CC_STACKPROTECTOR_REGULAR=y
# CONFIG_CC_STACKPROTECTOR_STRONG is not set"
1789353,2018-08-28 08:59:47 UTC,"Just from my memory: I believe that config option (at least on the x86) side required support in the compiler which is not available back in the Trusty user-space. And the Trusty/lts-backport-xenial (not called HWE, yet to really make things confusing) is build in the Trusty user-space environment. The config options for stack protector (there was something available with a different option name) get automatically converted using the backport script.
If its left set for arm64, its probably a mistake, but somehow seems to have no visible effect. Maybe its ignored on that arch or the arm64 gcc was already including that option.
If that option is really actively enabled on arm64, then the test should probably be changed to expect this. If its a false positive, the test also needs to be adapted, but ... differently."
1789353,2019-05-15 06:29:19 UTC,"It looks like I can use ""-fsstack-protector"" flag on an ARM64 node with T-LTS-X (works with cc as well)"
1789353,2018-08-28 07:27:27 UTC,It looks like this part in qrt is the cause:
1789356,2018-10-16 13:43:42 UTC,Not a rls bug.  Can be fixed later.
1789356,2019-01-24 07:20:16 UTC,This is getting confusing because the Yaru theme is changing faster than we can release fixes to correct the related transitions.
1789356,2019-01-16 01:18:07 UTC,Now disco is using a solid purple background (decided by upstream Yaru). So gnome-shell in disco needs changing to remove the above gnome-shell fix.
1789356,2018-12-12 18:55:40 UTC,This bug was fixed in the package gnome-shell - 3.30.1-2ubuntu1.18.10.1
1789356,2018-12-12 18:55:08 UTC,"On Wed, Dec 12, 2018 at 08:06:53AM -0000, Daniel van Vugt wrote:

> The proposed version of gnome-shell only makes this bug a little worse,
> to the extent that I expect other people will start reporting the bug
> and not just me. I don't mind if the gnome-shell fix goes into cosmic
> first and we live with that briefly - it would be no worse than disco is
> right now. However if the mutter fix was to be released first then we
> would avoid a perceived secondary (more visible) regression.
"
1789356,2018-12-12 18:54:06 UTC,"On Wed, Dec 12, 2018 at 07:48:37AM -0000, Didier Roche wrote:

> I think Daniel was clear by changing to verification-done that this can go in.
> We are talking about a less than a second flash, while blocking a bunch of fixes for GNOME Shell in cosmic. Note that this second flash already existed before the fix, and that the fix is correct, it will only be correctly applied once mutter is in.
"
1789356,2018-12-12 08:06:53 UTC,"The proposed version of gnome-shell only makes this bug a little worse, to the extent that I expect other people will start reporting the bug and not just me. I don't mind if the gnome-shell fix goes into cosmic first and we live with that briefly - it would be no worse than disco is right now. However if the mutter fix was to be released first then we would avoid a perceived secondary (more visible) regression."
1789356,2018-12-12 07:48:37 UTC,"I think Daniel was clear by changing to verification-done that this can go in.
We are talking about a less than a second flash, while blocking a bunch of fixes for GNOME Shell in cosmic. Note that this second flash already existed before the fix, and that the fix is correct, it will only be correctly applied once mutter is in."
1789356,2018-12-11 18:10:33 UTC,"I gather from Daniel's testing that this makes things worse for users of Cosmic. If that is correct, even if a fix for mutter is coming, I don't think releasing gnome-shell to -updates is the right idea."
1789356,2018-11-15 09:54:47 UTC,I now think the proposed gnome-shell version 3.30.1-2ubuntu1.18.10.1 is fine. It doesn't need fixing in itself but it does hit a mutter bug which needs fixing per the above link.
1789356,2018-11-14 10:30:43 UTC,"Fix proposed to mutter here:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/308"
1789356,2018-08-31 02:19:40 UTC,"Maybe ignore this bug for a little while. It is presently masked by a much bigger issue of the login screen and shell using the wrong VTs (and flickering, and failing) in cosmic. So transitioning doesn't presently work because of that too. Wait for the fix for bug 1786872 and bug 1786883 to be released first."
1789356,2018-11-14 05:16:43 UTC,I found the problem yesterday.
1789356,2018-08-30 15:25:47 UTC,"That is very strange indeed. There is no specific styling for the second screen though. I thought that this was fixed with https://github.com/ubuntu/yaru/issues/583
But obviously not. I will look into this."
1789356,2018-11-13 07:33:26 UTC,"I don't have the time to do a testround again, but I can give pointers for whoever has time to have a look:"
1789356,2018-11-13 01:27:56 UTC,"It does make this bug worse. The original bug was barely noticeable, but with that fix it's really a bright and obvious glitch."
1789356,2018-11-12 11:06:10 UTC,"Daniel, ok you consider the fix here as problematic. Do we believe it's worth unvalidating the SRU over it though? We have enough difficulties landing gnome-shell SRUs fixing at the moment and the touch event one included in the same update is important to oem.
If the background change is not perfect but not worth than we had perhaps we can mark it verified, get that SRU in on the principle that it's not really making things worth and have another go later at fixing it more correctly?"
1789356,2018-11-12 08:49:17 UTC,"Yes, I have now tested the proposed fix on two separate fresh installations of cosmic. One HP and one Lenovo laptop. In both cases they show a weird multi-stop gradient after the fix is installed. Looks like the colour goes up-down-up-down instead of just down."
1789356,2018-11-12 07:17:52 UTC,"Are you sure it's differently? Look at the diff, it's supposively exactly the same values than Yaru. Please check it and revert the status as needed."
1789356,2018-11-12 02:02:55 UTC,"The proposed fix 3.30.1-2ubuntu1.18.10.1 certainly changes things, but is equally broken as the original bug. Using the proposed fix a weird gradient flashes up briefly that doesn't match the login screen background and is more visually distracting than the original bug."
1789356,2018-11-09 10:14:48 UTC,"Hello Daniel, or anyone else affected,"
1789356,2018-11-09 04:18:04 UTC,This bug was fixed in the package gnome-shell - 3.30.1-2ubuntu2
1789356,2018-10-17 13:05:23 UTC,Fixed in https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb
1789356,2018-10-17 13:03:46 UTC,Fixed in gnome-shell as this is a separate parameter. Nice catch!
1789356,2018-11-13 10:06:57 UTC,I was wrong. I can see the same bug in git builds. It's just not obvious when you're not coming from the login screen.
1789356,2018-11-13 09:05:45 UTC,Thanks. I have confirmed on a third cosmic machine the same bug in 3.30.1-2ubuntu1.18.10.1 :(
1789362,2020-02-16 21:47:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789363,2018-09-03 07:20:51 UTC,"Yes, not only silkscreen, but more importantly a 3D model. Very useful for interference checks. Another use case like this:
A while ago I built a vacuum gripper for a climbing robot. A control PCB was directly mounted on top of the gripper cone and had a pressure and distance sensor and surrounding gasket to seal the assembly. For obvious reasons it was very handy to include the seal 3D model to make sure I wouldn't accidentally place a via in the vacuum area. Exporting back and forth to MCAD would've cost a lot more time."
1789363,2018-09-01 11:57:36 UTC,"@Jeff, I'm not sure this makes sense.  I plan on adding support for
adding symbols that do not get added to the netlist when updating the
board so users can create BOMs that have parts that are not required for
laying out the board.  I've never seen this done from the board side."
1789363,2018-09-01 12:46:57 UTC,"@Wayne, in Stefan's example he mentions wanting a silkscreen, so it would be on the board."
1789363,2018-08-31 23:30:58 UTC,"This would be a board file format change, so will have to wait until next time we update the format."
1789373,2019-07-31 21:07:11 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1789373,2018-08-28 07:46:53 UTC,https://review.openstack.org/#/c/587064/
1789373,2019-07-31 21:07:45 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/587064
Reason: This review is > 180 days without comment and WIP -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewers. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1789375,2018-08-28 07:40:42 UTC,"Logs:
=============="
1789378,2018-08-28 08:02:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597011"
1789378,2018-08-30 06:11:39 UTC,Do you want to add other quota driver?
1789378,2020-03-24 21:56:48 UTC,"Due to lack of any activity in this RFE since more than 1 year, I'm going to close it for now. If You would be still interested in implementing this and would like to continue discussion on that, feel free to reopen it and ping me (slaweq) on irc."
1789378,2020-05-21 02:17:41 UTC,"Change abandoned by junbo (<email address hidden>) on branch: master
Review: https://review.opendev.org/597011"
1789387,2018-08-28 09:07:54 UTC,"The Line tool allows you to draw lines using Shift at specified angles. But, to the point of view, these corners can not be changed. It would be desirable, that the angle could be set including 26.5 degrees (one or two characters after the decimal point)
Very convenient for drawing game isometry."
1789391,2018-09-12 20:45:20 UTC,This RFE was discussed during the Denver PTG. The team agreed to move ahead to write a spec.
1789394,2020-07-25 20:09:55 UTC,"Can you please provide exact step by step instruction how to reproduce a problem, if possible."
1789395,2018-08-28 10:48:11 UTC,Note that this shortcoming also troubles a lot of people that use the alternative none-eabi compiler available from arm directly: https://bugs.launchpad.net/gcc-arm-embedded/+bug/1698539 but they show exceptional do-not-care attitude.
1789401,2018-08-28 12:23:16 UTC,It seems this happens for grouped objects only.
1789401,2018-08-28 13:59:24 UTC,"The following change in svg2xaml.xsl seems to work for me:
It's somewhere around line 231."
1789407,2020-02-22 18:47:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789410,2018-08-28 13:15:52 UTC,"I looked at the svg2xaml.xsl file which is located in my installation directory. I could not find a <xsl:decimal-format> element, which seems to be needed for format-number() function to work correctly."
1789410,2020-04-08 17:16:36 UTC,Closing as part of bug migration to GitLab (https://alpha.inkscape.org/bug-migration/)
1789411,2018-08-28 18:28:57 UTC,"Hi Chris, thank you for your report."
1789411,2018-09-04 07:23:30 UTC,thank you!
1789411,2018-09-18 20:37:19 UTC,"Chris,
may I ask you to check that 'Europe/Vienna' timezone is present?"
1789411,2018-09-19 05:49:28 UTC,Hi!
1789411,2018-09-19 13:17:14 UTC,"Ok, last thing so I can try reproduce this.
Can you give me the version you where upgrading from?
Are you dist-upgrading (from ubuntu 16.10)?"
1789411,2018-09-19 14:15:00 UTC,"the old version should be 10.1.29-6 - here is the specific part of the logfile:
Upgrade: mariadb-common:amd64 (1:10.1.29-6, 1:10.1.34-0ubuntu0.18.04.1)
Upgrade: mariadb-client-core-10.1:amd64 (1:10.1.29-6, 1:10.1.34-0ubuntu0.18.04.1)
Upgrade: mariadb-client-10.1:amd64 (1:10.1.29-6, 1:10.1.34-0ubuntu0.18.04.1)
Upgrade: mariadb-server-core-10.1:amd64 (1:10.1.29-6, 1:10.1.34-0ubuntu0.18.04.1), mariadb-server-10.1:amd64 (1:10.1.29-6, 1:10.1.34-0ubuntu0.18.04.1)
Upgrade: mariadb-server:amd64 (1:10.1.29-6, 1:10.1.34-0ubuntu0.18.04.1)"
1789411,2018-09-24 19:50:59 UTC,"Chris,
thank you again for your help!"
1789411,2018-09-27 07:14:35 UTC,thanks for your help!
1789423,2018-11-21 22:00:25 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/619366"
1789423,2018-11-21 20:19:14 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/619349"
1789423,2018-11-21 20:28:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/619351"
1789423,2018-11-02 11:23:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615134"
1789423,2018-11-21 20:36:45 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/619352"
1789423,2018-11-21 21:20:12 UTC,"Reviewed:  https://review.openstack.org/615134
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c4f6b0bf6cc903cf52c4b238c3771604dda174b8
Submitter: Zuul
Branch:    master"
1789423,2018-11-26 22:14:24 UTC,"Reviewed:  https://review.openstack.org/619349
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c689c09996c4a3da9e05ccd5178a4b5060949889
Submitter: Zuul
Branch:    stable/rocky"
1789423,2018-11-30 03:26:34 UTC,"Reviewed:  https://review.openstack.org/619351
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=61bf7ae5795a3dfac7afc57bed9b4195cfdb6042
Submitter: Zuul
Branch:    stable/queens"
1789423,2018-12-19 10:01:24 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1789423,2018-12-19 20:48:08 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1789423,2019-01-30 02:17:10 UTC,"Reviewed:  https://review.openstack.org/619352
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a0d338c6775803516c5fdb99f0581e40957cb0c
Submitter: Zuul
Branch:    stable/pike"
1789423,2019-02-08 05:09:58 UTC,"Reviewed:  https://review.openstack.org/619366
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b8702ded74aad826432dcedaf65535af52835aa5
Submitter: Zuul
Branch:    stable/ocata"
1789423,2019-03-22 03:46:21 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1789423,2019-04-26 17:16:29 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1789425,2018-10-31 17:32:37 UTC,"An upload of magnum to bionic-proposed has been rejected from the upload queue for the following reason: ""Cleaning up the queue as https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1789425/comments/5 remains unanswered.""."
1789425,2018-09-07 21:18:01 UTC,"This is evidently an openstack package, but the upstream point release is not covered by https://wiki.ubuntu.com/OpenStackUpdates (magnum is not on the list of packages).  What is the expectation here?  Is magnum covered by the QA process listed on that exception page?"
1789425,2018-08-28 18:23:48 UTC,I've uploaded a new version of magnum 6.1.1 that also provides a fix for https://bugs.launchpad.net/cloud-archive/+bug/1789475.
1789425,2018-08-28 15:23:38 UTC,I've uploaded magnum 6.1.1 to the bionic unapproved queue where it is awaiting review by the SRU team. Note I accidentally uploaded 3 exact copies (2 failed attempts to upload to my own PPA).
1789425,2018-08-28 14:17:13 UTC,So essentially the latest upstream stable release of queens should fix this. Correct?
1789425,2018-08-28 14:16:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789426,2018-08-28 13:49:31 UTC,"Also noticed that after various attempts, other racks and region/rack started disconnecting from MAAS>"
1789426,2018-08-28 14:07:02 UTC,I think having MAAS regions know which rack controller to use based on power management tools is the wrong approach. We should require the same power management tools across all rack controllers. If we allow divergence we're asking for confusion and a debugging nightmare down the road. Even if MAAS is smart enough to just use the right one - what happens when that rack controller dies and now the remaining one can't do its job because we didn't enforce consistency?
1789426,2018-08-28 18:35:20 UTC,MAAS doesn't know which rack controller to use based on power management tools. MAAS has a mechanism in which it finds a rack controller that can communicate to the machine via the address of the BMC (e.g. checks that MAAS can reach to the machine via IP).
1789426,2018-08-28 20:24:51 UTC,Actually the mechanism to determine when rack controllers can communicate to a machine is only for Layer 3 communication. If maas determines that the BMC is located on the same Layer 2 as other rack controllers it will just pick one of those are random to power control that machine.
1789426,2018-08-28 20:37:19 UTC,"AFter further investigation, seems that the actual issue wasn't the fact that amt related decencies weren't installed (they were)."
1789426,2018-08-28 20:40:17 UTC,"I tried releasing 5 machines for which power management wasn't working (e.g. MAAS just couldn't contact the BMC's). 1 machine failed to release immediately, while the other 4 got stuck in 'Releasing':"
1789426,2018-08-28 20:41:38 UTC,"After a while, the other machines were marked failed releasing, because they timed out. That means that power management failure/traceback may be blocking other operations from continuing to be able to perform:"
1789426,2018-10-09 21:26:45 UTC,I think this is the same issue as this: https://bugs.launchpad.net/maas/+bug/1771777
1789426,2019-09-19 11:51:28 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1789428,2018-09-07 18:53:20 UTC,This has been fixed in version 3.30.1: https://gitlab.gnome.org/GNOME/evolution/issues/108
1789428,2018-09-07 20:36:07 UTC,"Thanks Andre for now I'll just do the work around which is to expunge, CTRL-E, within the folder I've deleted the messages from instead of doing it from the trash folder."
1789428,2018-08-28 13:57:52 UTC,Note: When saving this bug report it insisted that it was for Update Manager even though when I started writing it I selected 'Evolution' and the package. I had to go back in manually and change it back to evolution.
1789429,2018-11-02 06:18:40 UTC,New image import method web-download is added which might be a solution for this. Please add additional information if you still think this needs to be addressed.
1789429,2018-11-02 10:12:58 UTC,That is actually what I did mean.
1789433,2018-12-07 16:18:56 UTC,As this charm is deprecated marking low - if a group of people step up to own it at some point this will need fixing!
1789434,2019-02-21 15:57:02 UTC,This issue should be resolved with patch https://review.openstack.org/#/c/636710/2 as it looks that it is caused by bugs in rootwrap filters.
1789434,2019-04-03 00:30:02 UTC,"Reviewed:  https://review.openstack.org/645282
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8b7955dade3e388ad030ce2291651cef72d55108
Submitter: Zuul
Branch:    stable/rocky"
1789434,2019-03-27 03:50:47 UTC,"Reviewed:  https://review.openstack.org/645283
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6f3620aa88feef9527f8c9599dec049a831b49fa
Submitter: Zuul
Branch:    stable/queens"
1789434,2019-03-25 10:10:59 UTC,"Reviewed:  https://review.openstack.org/644931
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=0e8b686d84427532ffd8da842d4e4d2017995cbe
Submitter: Zuul
Branch:    master"
1789434,2019-03-21 17:50:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/645283"
1789434,2019-03-21 17:50:15 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/645282"
1789434,2019-03-20 15:49:39 UTC,"Change abandoned by Miguel Lavalle (<email address hidden>) on branch: master
Review: https://review.openstack.org/611461"
1789434,2019-03-13 21:00:37 UTC,"Reviewed:  https://review.openstack.org/636710
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=25c432a05a57f794dcbb4f17ce224d914c65e071
Submitter: Zuul
Branch:    master"
1789434,2019-04-05 10:39:05 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/650255"
1789434,2018-10-25 15:10:52 UTC,Proposed fix is here: https://review.openstack.org/#/c/611461/
1789434,2018-09-26 05:25:59 UTC,"Reviewed:  https://review.openstack.org/605057
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=e137cd003b93d641189ba4d2c0dd1effe4795ba4
Submitter: Zuul
Branch:    master"
1789434,2018-09-25 12:30:36 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/605057"
1789434,2018-09-12 20:38:56 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/602161"
1789434,2018-09-06 21:15:08 UTC,"def _update_ports(self, context, router_id):
    objs = l3_obj.RouterPort.get_objects(
         context, router_id=[router_id])
    for obj in objs:
        port_id = obj.port_id
        self._core_plugin.update_port(
            context, port_id, {'port': {'status': 'DOWN'}})"
1789434,2018-09-06 20:19:54 UTC,comment2 --continued
1789434,2018-09-06 20:17:06 UTC,"I tried this on a 3 node setup, DVR (1 allinone, 2. compute 3.network ) using miguel's vagrant scripts dvrvagrant and below is my observation which is exactly same as Brian's"
1789434,2018-09-04 16:57:29 UTC,So I did a little debugging here.
1789434,2018-10-17 23:15:47 UTC,"Change abandoned by Manjeet Singh Bhatia (<email address hidden>) on branch: master
Review: https://review.openstack.org/602161"
1789434,2019-04-06 05:39:37 UTC,"Reviewed:  https://review.openstack.org/650255
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=672a4328a97d6dae98cec208851198040530bd35
Submitter: Zuul
Branch:    stable/pike"
1789443,2018-08-29 04:47:01 UTC,"I agree, unregister exists to say ""don't try to clean anything up, just
record that everything is gone"". While ""kill-controller"" assumes there
should be something to clean up."
1789443,2018-08-29 13:37:37 UTC,"Can we update the unregister help?  Given that the controller wasn't registered, using unregister never came to mind."
1789443,2018-08-28 23:33:16 UTC,I'm with Rick on this one. This is why we created the unregister command.
1789443,2018-08-28 18:17:02 UTC,The node and controller machines are gone. I can't ping the cloud api ip.
1789443,2018-08-28 20:01:40 UTC,"My concern is having kill-controller make a decision when it cannot tell the cloud api is unreachable vs gone. It's up to the user to know that it's gone and use unregister in that case using current tooling. I personally am -1 on making the code JFDI something there that could lead to users thinking things are done and gone when their wifi was down, or a vpn wasn't up, or other issue that the user should be directed to look into vs just removing the local cache right away."
1789443,2018-08-28 15:19:22 UTC,"This was my controller, not one registered.   If it can't be reached, I expect kill-controller to clean up the local info."
1789443,2018-08-28 14:52:38 UTC,"Is the controller still there at all? If it's gone then the unregister command is meant to remove local cache data about a controller. Typically it's built to remove a controller you were granted access to that might have gone away and you need to clean your own record of it, but it might be the right fix for this as well."
1789443,2018-08-28 15:33:01 UTC,"I understand, but is there anything running on the provider? kill-controller is for avoiding the controller API and going straight to the cloud provider to clean up resources/etc. If there's nothing on the API there's nothing that distinguishes issues with the cloud API vs ""it's gone, let's clean up local stuff"". I'm wondering the state of the remote cloud API endpoint to help on what the best path is in this case."
1789445,2019-09-08 22:33:24 UTC,"dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  libglib2.0-0:amd64 -> libglib2.0-0:i386
 packages' pending triggers which are or may be unresolvable:
  man-db: /usr/share/man
  libglib2.0-0:i386: /usr/share/glib-2.0/schemas
  libglib2.0-0:amd64: /usr/share/glib-2.0/schemas"
1789445,2018-09-02 21:20:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789447,2019-09-30 21:50:10 UTC,pr: https://github.com/juju/charm/pull/293
1789447,2019-09-30 15:10:27 UTC,So the kind of stacktrace is the following:
1789447,2019-09-30 08:41:46 UTC,"Yes, i could recreate the error. if you deploy from a folder which not contains a `.git` folder, this error occurs. So ` nam:~ $ juju deploy ./Workspace/charms/postgresql-charm` leads to it, while
`nam:/home/nam/charm-folder/pogresgit $.... deploy` does not."
1789447,2018-08-29 01:09:18 UTC,"The issue here is that we now run ""git describe --dirty"" to pick up the sha of the latest commit and include that in a version file in the charm archive. This is reported in juju status."
1789447,2019-01-11 10:50:21 UTC,"This is still a problem in 2.5-rc1. I believe this could be due to the fact that the ""git"" command is not run in the appropriate directory."
1789454,2019-11-05 11:35:19 UTC,"As of Nov 2019, I'm getting the same crash bug, ran it through gdb and it crashes in the same place."
1789454,2020-02-07 21:28:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789454,2020-02-07 21:31:53 UTC,It was working fine for me a couple of months ago. Not it crashes with a segmentation fault.
1789455,2020-08-06 09:53:10 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/598482
Reason: This is an old change with negative review and merge conflict. I'm abandoning it. Please feel free to restore it (or ask me, gibi, on IRC to restore it for you) if you want to continue working on this."
1789455,2019-12-24 15:08:55 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/700520"
1789455,2018-08-31 07:56:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/598482"
1789455,2018-08-29 10:40:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597443"
1789455,2018-08-29 10:51:53 UTC,"Change abandoned by huanhongda (<email address hidden>) on branch: master
Review: https://review.openstack.org/597434
Reason: https://review.openstack.org/#/c/597443/
This patch is a better way."
1789455,2018-08-29 07:30:22 UTC,I am not so sure why this is happening actually. It also might be that soft_deleted filter is not passed properly.
1789455,2018-08-28 15:52:35 UTC,"The problem seems to be that soft-deleted instance's ""DELETED"" field is set to ""True"" whereas ""nova list --status SOFT_DELETED"" queries with search_opts's 'deleted' filter set to ""False""."
1789455,2018-08-29 09:31:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597434"
1789456,2018-08-28 17:57:03 UTC,"In this context, the AutoDj # can also be useful. Can this also fit in this new coloumn?"
1789456,2018-08-28 19:32:36 UTC,Who is adressed with this - me or devs? (Sorry :) )
1789457,2018-09-07 15:12:23 UTC,Just an update: this bug seems to still be present in 4.15.0.34.56.
1789475,2018-10-31 17:32:38 UTC,"An upload of magnum to bionic-proposed has been rejected from the upload queue for the following reason: ""Cleaning up the queue as https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1789425/comments/5 remains unanswered.""."
1789477,2020-03-04 14:11:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789484,2018-09-08 06:47:43 UTC,"Reviewed:  https://review.openstack.org/599064
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3987f597823c8760e953717d0a7d9ab64a913435
Submitter: Zuul
Branch:    stable/rocky"
1789484,2018-09-19 16:21:12 UTC,"Reviewed:  https://review.openstack.org/599200
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8ca3b075644109795d2c2f277f0bf857c1bd6b88
Submitter: Zuul
Branch:    stable/queens"
1789484,2018-08-29 00:45:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597330"
1789484,2018-09-24 14:47:01 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1789484,2018-09-01 21:25:38 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/599200"
1789484,2019-03-22 03:47:53 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1789484,2018-09-24 14:46:52 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1789484,2018-09-01 00:37:50 UTC,"Reviewed:  https://review.openstack.org/598353
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=df058720434cdca2726eb8c16f323a98bfc73ce3
Submitter: Zuul
Branch:    master"
1789484,2018-08-28 19:51:17 UTC,Better logstash query - http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22_determine_version_cap%5C%22%20AND%20tags:%5C%22screen-n-cpu.txt%5C%22&from=7d
1789484,2018-08-30 22:15:38 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/597330
Reason: https://review.openstack.org/#/c/598353/ is what we want, I just didn't know we had that conductor wait_until_ready thing."
1789484,2018-08-30 21:19:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/598353"
1789484,2018-08-28 20:15:59 UTC,"Correction on comment 2, we call post_start_hook before joining the service group:"
1789484,2018-08-28 20:14:47 UTC,"(2:38:34 PM) mriedem: 2018-08-27 14:30:31.159 | + functions-common:_run_under_systemd:1482 :   sudo systemctl start <email address hidden>
(2:38:54 PM) mriedem: 2018-08-27 14:30:32.414 | + functions-common:_run_under_systemd:1482 :   sudo systemctl start <email address hidden>"
1789484,2018-08-31 20:22:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599064"
1789485,2018-11-27 15:42:09 UTC,"Isn't there a distinction between ""previously marked destination"" and ""previously marked library""? In Item Status it seems you have to mark a ""library"", not a bib record for transfer. If you change this label to ""destination"" will the code still work if you select a bib and not a library?"
1789486,2020-11-09 08:38:55 UTC,"Hello,
do you still have this issue with the latest kernel? (4.15.0-122-generic)
Thanks"
1789486,2021-01-09 04:17:24 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1789491,2018-12-11 20:02:10 UTC,Confirmed in Evergreen version 3.2.1
1789491,2020-01-22 22:59:56 UTC,I pushed a branch with a color adjustment:
1789491,2020-02-19 21:46:30 UTC,Much easier to read!
1789491,2020-02-27 18:17:39 UTC,"Works well for me, too.  Thanks, Mike and Jessica.  I've pushed to master and rel_3_4."
1789492,2018-08-29 00:57:58 UTC,apport information
1789492,2018-08-29 00:57:57 UTC,apport information
1789492,2018-08-29 00:58:00 UTC,apport information
1789492,2018-08-29 00:58:11 UTC,apport information
1789492,2018-08-29 00:58:03 UTC,apport information
1789492,2018-08-29 00:57:55 UTC,apport information
1789492,2018-08-29 00:58:02 UTC,apport information
1789492,2018-08-29 00:57:54 UTC,apport information
1789492,2018-08-29 00:58:06 UTC,apport information
1789492,2018-08-29 00:57:50 UTC,apport information
1789492,2018-08-29 00:57:48 UTC,apport information
1789492,2018-08-29 00:57:47 UTC,apport information
1789492,2018-08-29 00:57:44 UTC,apport information
1789492,2018-08-29 00:57:40 UTC,apport information
1789492,2018-08-29 00:57:39 UTC,apport information
1789492,2018-08-29 00:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1789492,2018-08-29 00:57:52 UTC,apport information
1789494,2018-10-05 01:27:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789499,2019-04-16 08:50:22 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/601270
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1789499,2018-10-05 09:49:46 UTC,"Thanks Slawek, I will continue with the WIP patch."
1789499,2019-04-16 08:50:01 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1789499,2018-10-25 19:01:02 UTC,"Some interesting things during my ""research"" (NOTE: all the commands/API calls below were executed after source openrc demo demo)"
1789499,2018-10-05 09:28:07 UTC,"IMO this is valid bug. If some call is in general forbidden for user, it should returns 403 instead of empty list with 200."
1789499,2018-09-10 13:19:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/601270"
1789499,2018-09-10 13:21:59 UTC,"I uploaded a WIP patch (https://review.openstack.org/601270), check if it is something you miss please.
I would wait for the cores to have their opinion on this topic."
1789499,2018-09-10 08:58:22 UTC,I read some code for this problem:
1789499,2018-09-07 21:09:24 UTC,Yup. I think this is a defect because there is no error returned at all. I think either a 403 forbidden or a 404 not found would be appropriate. GET requests for a single resource return 404 when the user doesn't have permission to view that resource.
1789499,2018-09-07 07:16:29 UTC,"The issues really there (I tried in devstack, everything is on master)."
1789511,2018-09-03 16:24:46 UTC,probably related to https://bugs.launchpad.net/designate/+bug/1755788
1789512,2018-09-08 16:51:39 UTC,DNS zone panel is provided by designate-dashboard. Forwarding the bug to designate-dashboard.
1789516,2019-05-17 22:36:17 UTC,This bug was fixed in the package apport-symptoms - 0.22
1789519,2018-08-29 00:30:11 UTC,This change was made by a bot.
1789519,2018-08-29 01:10:51 UTC,Further Details on Problem:
1789519,2018-08-29 14:26:35 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1789519,2018-08-29 19:45:46 UTC,"Tested the 4.19-rc1 upstream kernel (4.19.0-041900rc1)
and the issue still exists!"
1789519,2018-09-05 19:01:09 UTC,"Since I reported this issue I have tried to debug this problem and found
that the function call to 'i8k_get_fn_status' in the kernel module 'dell-smm-hwmon'
(code at https://github.com/torvalds/linux/blob/master/drivers/hwmon/dell-smm-hwmon.c)
is what causes low memory corruption on Dell Inspiron 3847."
1789519,2018-10-30 19:43:31 UTC,"Hello there,"
1789519,2019-01-03 07:06:04 UTC,L1TF was introduced between these two versions.
1789523,2019-01-27 00:43:32 UTC,"It appears it's still there, but only accessible to project members. Which also excludes me."
1789523,2019-01-18 05:12:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789523,2018-08-29 08:42:10 UTC,Freedesktop tells me it's a downstream Debian script file.
1789523,2019-01-26 20:45:52 UTC,@kode54 Re: comment #5
1789523,2018-08-29 02:22:16 UTC,Thanks for the patch. We require all Ubuntu changes to be proposed to upstream first.
1789523,2018-08-29 04:22:01 UTC,"The attachment ""Patch to fix ssh-agent startup script"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1789527,2020-04-08 22:03:04 UTC,I have added the block-proposed-xenial tag so I can do multiple fixes in a single SRU for xenial.
1789527,2020-04-08 22:00:59 UTC,"commit 16dee87e24ee1a0d6e37b5fa7b91c303f7c912db
Author: Ralf Haferkamp <email address hidden>
Date:   Tue Aug 22 15:47:47 2017 +0200"
1789527,2019-11-11 13:54:48 UTC,I'm assigning myself to check this next time I touch the cleanup for resource-agents.
1789527,2019-05-14 18:04:59 UTC,"Workaround -> Importance: Medium, and back to Triaged since this isn't being actively worked on (it's in our backlog)."
1789527,2018-11-12 17:37:41 UTC,Can you test using this configuration of Pacemaker ? :
1789527,2018-11-12 17:22:34 UTC,Related: https://bugs.launchpad.net/charm-percona-cluster/+bug/1744393
1789527,2018-11-12 16:49:44 UTC,"By doing graceful shutdowns I can get in a state where the last node to die will have ""safe_to_bootstrap:1"" in its grastate.dat file. But I couldn't get that node back running, which was odd, as it should be the *only* one that can be started. I had to use one of the other initscript targets, restart-bootstrap, instead of just restart, or else it would timeout trying to reach the ""juju cluster"":"
1789527,2019-05-14 18:05:37 UTC,"(if anyone can contribute a fix in terms of a debdiff that is ready to apply, please do and I'll make sure it gets looked at promptly)"
1789527,2018-11-09 11:48:39 UTC,This wasn't enough to trigger the bug:
1789527,2018-11-09 11:17:34 UTC,"Sure, I just need to get the test case in order. I'll try that today."
1789527,2018-11-09 03:35:56 UTC,"Hi Andreas,"
1789527,2018-11-08 16:42:57 UTC,I have patched packages in this ppa if someone wants to try them: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3506/
1789527,2018-11-05 16:55:12 UTC,Currently blocking https://review.openstack.org/#/c/597969/
1789527,2018-09-05 18:54:03 UTC,Thanks for bringing this up together with an upstream patch.
1789527,2018-11-09 13:20:04 UTC,"Yes you are right Andreas, you need active database writes when you shutdown them. The resource agent automatically detect which instance has the last commit and start it as master and resume the replication to the other instances."
1789528,2020-03-07 14:14:52 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1789547,2018-08-29 05:47:45 UTC,"There is a workaround when you switch to ""playback"" tab on left side. But when you want to switch channel you have to witch the tabs."
1789547,2018-08-29 05:46:06 UTC,Here is a screenshot with the situation.
1789570,2018-08-29 08:33:41 UTC,Thanks for the bug report and feature idea/suggestion!
1789570,2019-04-10 09:55:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789575,2018-08-29 20:08:15 UTC,"Very good idea. Now that this idea is in I really will is that feature ;-)
+1 from my side"
1789575,2018-08-30 17:01:04 UTC,+1
1789575,2018-08-31 19:09:37 UTC,"+1 from my side as well :)
However should the button really go to the main menu or to the single player menu?
Implementation should be fairly easy, so if we decide to do so, this could make its way into build20"
1789575,2018-08-31 19:42:11 UTC,"Main menu imho. I believe that most of the time, players immediately load the newest savegame after starting Widelands. Together with the splash screen option it´ll then be possible to start playing with really just one click after starting WL :)"
1789575,2019-09-16 13:59:35 UTC,Migrated to https://github.com/widelands/widelands/issues/2111
1789588,2021-01-09 04:17:37 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1789588,2020-11-09 08:34:30 UTC,"Hello,
as this issue is a bit old, do you still have this problem with the latest kernel?
Thanks."
1789588,2020-11-09 09:25:19 UTC,"I guess so but dunno, we added ""8.046.00-1"" from bionic to our internal repo and are happy with it."
1789588,2021-01-09 04:17:36 UTC,[Expired for r8168 (Ubuntu) because there has been no activity for 60 days.]
1789589,2018-09-13 11:50:11 UTC,apport information
1789589,2018-09-13 11:50:12 UTC,apport information
1789589,2018-09-13 11:50:14 UTC,apport information
1789589,2018-09-13 11:50:16 UTC,apport information
1789589,2018-09-13 11:50:22 UTC,apport information
1789589,2020-01-26 15:28:54 UTC,From the original report:
1789589,2020-02-04 09:09:49 UTC,"Hans,"
1789589,2018-09-13 11:50:09 UTC,apport information
1789589,2019-01-03 07:01:26 UTC,Have you tried other quirks?
1789589,2018-09-13 11:50:06 UTC,apport information
1789589,2018-09-13 11:50:19 UTC,apport information
1789589,2018-09-13 11:50:03 UTC,apport information
1789589,2018-09-13 11:50:04 UTC,apport information
1789589,2018-08-29 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1789589,2018-08-30 21:59:31 UTC,"Dear all,
Tested with upstream kernel, same result.
Kernel version:
Linux version 4.19.0-041900rc1-generic (kernel@kathleen) (gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1))
kernel-bug-exists-upstream"
1789589,2018-09-13 11:49:53 UTC,apport information
1789589,2018-08-29 14:24:42 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1789589,2018-09-13 11:49:58 UTC,apport information
1789589,2018-09-13 11:50:00 UTC,apport information
1789589,2018-09-13 11:50:01 UTC,apport information
1789589,2018-09-13 11:49:56 UTC,apport information
1789592,2020-09-25 15:42:19 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/735201
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1789592,2020-09-25 15:41:17 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1789592,2018-12-06 10:11:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623179"
1789592,2020-06-11 17:24:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/735201"
1789592,2019-04-16 08:46:24 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/612400
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1789592,2019-04-16 08:45:58 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1789592,2018-12-10 16:15:49 UTC,"Reviewed:  https://review.openstack.org/623179
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f999970755571244f1133dc74e43fbbd62ecf380
Submitter: Zuul
Branch:    master"
1789592,2018-12-10 15:44:40 UTC,"Reviewed:  https://review.openstack.org/612153
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=22c9cf3d95c3d14351045bac2920b4e0994ec42f
Submitter: Zuul
Branch:    master"
1789592,2018-11-14 08:26:26 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/617780
Reason: Wrong change-id"
1789592,2018-10-15 09:51:15 UTC,"Recapping IRC discussion, I plan to work on it, but probably not soon."
1789592,2018-10-22 14:05:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612400"
1789592,2018-10-21 09:43:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612153"
1789592,2018-10-18 14:25:37 UTC,I asked Bernard and I'm going to start working on this one.
1789592,2018-10-05 14:37:22 UTC,This RFE was discussed and approved on October 5th.
1789592,2018-10-02 08:00:08 UTC,"Indeed I suggested it as a migration option, but just moving to API calls directly works too of course"
1789592,2018-09-28 07:47:48 UTC,One note: ovsdb_interface is already deprecated and should be removed in the future
1789592,2018-09-28 00:32:05 UTC,Sounds reasonable to me. Let's see what the drivers have to say
1789592,2018-11-13 18:36:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617780"
1789634,2018-08-31 12:31:01 UTC,"Do you have swap?
Is the resume device correct?"
1789634,2018-08-30 05:00:08 UTC,This change was made by a bot.
1789634,2018-09-02 04:30:00 UTC,I ran the commands as suggested and got no return on both.
1789635,2019-05-30 03:21:46 UTC,I believe this commit should resolve the issue. Can you check and confirm?
1789636,2018-08-29 14:20:09 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1789636,2018-08-29 12:00:13 UTC,This change was made by a bot.
1789638,2018-10-18 19:26:17 UTC,This bug was fixed in the package linux-azure - 4.15.0-1025.26~16.04.1
1789638,2018-08-31 12:54:40 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-August/095100.html
1789638,2018-08-29 15:19:33 UTC,Workaround fix attached. I suspect there may be a more elegant solution.
1789638,2018-08-29 14:04:47 UTC,Same issue with rbi->ring_buffer on write_avail_show() too.
1789638,2018-10-18 19:27:09 UTC,This bug was fixed in the package linux-azure - 4.15.0-1025.26
1789638,2018-08-29 12:40:47 UTC,"In read_avail_show, rbi->ring_buffer is NULL, causing the OOPS."
1789638,2018-08-29 12:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1789638,2018-08-31 09:01:04 UTC,The above patch fixes the issue for me. Thanks
1789638,2018-08-29 12:58:15 UTC,"Tested with today's linux tip, 4.19.0-rc1 @ commit 3f16503b7d2274ac8cbab11163047ac0b4c66cfe, issue still occurs."
1789638,2018-08-30 16:23:06 UTC,This has been submitted to 4.19 and stable:
1789639,2020-02-10 12:06:12 UTC,"Based on this comment, it seems, it's intended to run scenario tests regardless run_validation value:"
1789640,2019-11-12 04:18:01 UTC,[Expired for kolla because there has been no activity for 60 days.]
1789640,2019-09-12 13:59:35 UTC,Please deliver logs (/var/log/kolla/gnocchi/* and docker logs gnocchi_*) - marking as incomplete.
1789649,2019-04-11 20:18:07 UTC,Looks like this should be fixed now: https://review.openstack.org/#/c/650093/
1789649,2018-08-29 13:47:06 UTC,"Hmm, maybe osc-placement hasn't gone through the PTI changes yet for docs."
1789650,2020-08-03 19:37:29 UTC,"Yes, the procedure you've outlined seems sensible."
1789650,2018-08-29 14:26:57 UTC,"On Wed, Aug 29, 2018 at 9:01 AM Rod Smith <email address hidden> wrote:

>
> Public bug reported:
>
> This bug appears to be a regression of bug #1311827 and/or bug #1642298,
> but it seems to affect only some servers. Upon deployment via MAAS, the
> server is set to boot from the ""ubuntu"" EFI boot order entry -- that is,
> it boots directly from disk, bypassing the PXE-boot option. Immediately
> after deployment, the boot order looks like this:
>
> $ sudo efibootmgr
> BootCurrent: 0000
> BootOrder: 0000,0002,0001,0003,0004,0005,0006,0007,0008
> Boot0000* ubuntu
> Boot0001* Hard Disk 0
> Boot0002* PXE Network
> Boot0003  Enter Setup
> Boot0004  Boot Devices
> Boot0005  Boot Manager
> Boot0006  Setup
> Boot0007  Diagnostics
> Boot0008  Firmware Log
>
> This bug is affecting two Lenovo servers (drapion and jolteon), when
> deployed with either Ubuntu 18.04 or 16.04. These servers seemed OK in
> tests in late April. Other servers we've recently tested are NOT
> affected. Changes to the boot order after installation do ""stick,"" and
> it's possible to entirely delete the ""ubuntu"" entry without it being re-
> created, so I doubt if the firmware is creating the entry or making it
> the default; it appears that the bug is somewhere in Ubuntu. I'm
> reporting this against curtin, but it could be GRUB or something else is
> the true cause.
"
1789650,2020-07-01 14:12:59 UTC,"well, no joy.  I went into the EFI boot settings in firmware and re-ordered all the EFI boot options so that the Network device was first."
1789650,2020-07-01 14:34:20 UTC,"@rharper,"
1789650,2020-07-01 15:00:50 UTC,@Rod
1789650,2020-07-21 12:46:58 UTC,"Adding ""MAAS"" as an impacted project, as it appears there are questions about the curtin preseed that MAAS uses."
1789650,2020-07-22 07:50:15 UTC,Ryan's link is the correct one.
1789650,2020-07-22 16:33:18 UTC,"I've tried adding Ryan Harper's suggested workaround[1] to the MAAS curtin preseed file (/etc/maas/preseeds/curtin), to no effect; the node (I was using drapion for testing) still deploys with the system set to boot from hard disk (via the ""ubuntu"" entry in the EFI boot order). I also tried putting those lines in /etc/maas/preseeds/curtin_userdata, which we modify in our certification MAAS server for other purposes. (We do not create a ""grub"" entry by default, so there's no conflict over this detail.)"
1789650,2020-07-22 19:00:20 UTC,@Rod
1789650,2020-07-22 21:06:36 UTC,"@Ryan,"
1789650,2020-07-22 21:51:12 UTC,"> @Ryan,
>
> Is it the /var/log/maas/rsyslog/{nodename}/{date}/messages file you want? If
> so, I've appended it. Note that it includes several deployments from today.
> The final one is definitely with the GRUB config lines in
> /etc/maas/preseeds/curtin. If it's another file, can you please tell me
> where to find it?
"
1789650,2020-07-23 18:14:24 UTC,"AFAIK, BootCurrent is the only way to know how the system booted. OTOH, I suppose that, in theory, you could have MAAS's GRUB write a file somewhere that indicates a MAAS/PXE boot. You could then look for that file (checking its time stamp to be sure it was recent) -- but if BootCurrent is missing for GRUB in the EFI environment as well as for the kernel, that wouldn't help you figure out which of the Boot#### entries was used."
1789650,2020-07-23 18:32:51 UTC,I've got a branch of curtin if you can test:
1789650,2020-07-24 15:45:23 UTC,"Ryan,"
1789650,2020-07-24 18:02:25 UTC,"Thanks Rod,"
1789650,2020-07-24 20:08:17 UTC,"Ryan, I'm attaching what I can, which is the output from the ""maas {profile} machine get-curtin-config {system_id}"" command and the log file I provided earlier. The ""maas {profile} node-results read system_id={system_id} name=/tmp/curtin-logs.tar | jq -r .[0].data | base64 -d > curtin-logs.tar"" command from https://discourse.maas.io/t/getting-curtin-debug-logs/169 did not work; that produced 3-byte files. (Yes, I changed {profile} and {system_id} appropriately.) I suspect the documentation needs to be updated; or perhaps it's TOO up-to-date (we're running MAAS 2.6.2)."
1789650,2020-07-24 22:01:33 UTC,"Rod,"
1789650,2020-07-27 18:53:44 UTC,I've run a new series of tests with the latest version. Here are the results:
1789650,2020-08-03 14:54:41 UTC,"Rod,"
1789650,2020-08-03 17:47:46 UTC,"I've pushed  curtin - 20.1-246-g738de054-0ubuntu1  to the PPA, I'll copy the groovy build into the other releases when it's been published."
1789650,2020-08-05 01:37:18 UTC,"Not sure about where or how far to push ubuntu down the list, especially when a system has 2 or more potential bootable network devices."
1789650,2020-08-05 02:41:41 UTC,"On Tue, Aug 4, 2020 at 8:50 PM Greg McNutt <email address hidden>
wrote:"
1789650,2020-08-18 22:10:45 UTC,"Rod,"
1789650,2020-08-19 17:45:10 UTC,"Ryan,"
1789650,2020-08-19 18:23:43 UTC,"On Wed, Aug 19, 2020 at 12:50 PM Rod Smith <email address hidden>
wrote:"
1789650,2020-08-21 16:42:12 UTC,"This bug is fixed with commit 7a48737e to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=7a48737e"
1789650,2020-09-04 15:45:35 UTC,The bug I just issued (bug #1894217) seems very related to this. The deployment is failing due to an error being caused when trying to set the EFI boot order.
1789650,2020-09-04 18:24:27 UTC,"Thanks for the pointer David.  I've commented there; that bug is different, but related to curtin's manipulation of efi entries."
1789650,2020-08-03 19:03:18 UTC,"> Yes, #1, #3, and #4 were successful from the perspective of forcing a PXE boot; however, putting the ubuntu entry at the end of the boot list likely breaks the reason for creating the ubuntu entry at all (namely, enabling the node to boot if the MAAS server is down), since chances are an entry to boot to the firmware setup utility, EFI shell, or something else that would prevent an automated boot when the ubuntu entry is last in the list.
"
1789650,2020-06-29 21:34:41 UTC,@Jeff
1789650,2020-06-29 21:26:48 UTC,"Hrmmm... htat said, after messing about in the EFI boot settings a bit, I may have fixed it by forcing it to boot via PXE as it should have been all along...  Need to try this on some other machines to verify it's more likely misconfiguration for my hardware."
1789650,2020-08-03 18:23:16 UTC,"Ryan,"
1789650,2018-09-20 17:31:56 UTC,My tests of different kernels and Ubuntu versions yielded no clues; everything back to 14.04 with its GA kernel appears to be affected; however...
1789650,2020-06-29 20:49:31 UTC,"This is still an ongoing problem.  Currently, It is preventing me from runnign regression testing on some systems because, it appears, I must first log into each and delete all but the PXE option from the EFI boot menu before I can get them to re-deploy from MAAS."
1789650,2018-08-29 14:34:46 UTC,"I assume you mean the /root/curtin-install.log file, which I'm attaching. If you mean another file, please clarify."
1789650,2018-08-29 15:12:45 UTC,"On Wed, Aug 29, 2018 at 9:40 AM Rod Smith <email address hidden> wrote:

>
> I assume you mean the /root/curtin-install.log file, which I'm
> attaching. If you mean another file, please clarify.
"
1789650,2018-08-29 16:38:02 UTC,"I'm attaching a tarball with both the curtin-install-cfg.yaml and curtin-install.log files after a fresh installation, with the debugging feature you wanted activated."
1789650,2018-09-08 02:22:40 UTC,"Ryan, have you looked at the debugging output? Do you have any clues about what's going on?"
1789650,2018-09-10 14:45:50 UTC,"On Fri, Sep 7, 2018 at 9:30 PM Rod Smith <email address hidden> wrote:

>
> Ryan, have you looked at the debugging output? Do you have any clues
> about what's going on?
"
1789650,2018-09-12 14:45:27 UTC,Could you collect the same info (efibootmgr -v output before/after and the curtin-* from /root) from machines that work as you expect for further comparison?
1789650,2018-09-12 21:12:52 UTC,"Actually, this would seem like a regression in curtin. As per the comment #6 from Blake's branch:"
1789650,2018-09-12 21:19:15 UTC,"@Rod, so to clarify I would like to know:"
1789650,2018-09-12 21:24:03 UTC,and when was the last time the firmware of this system updated?
1789650,2018-09-12 21:53:19 UTC,"No change to curtin here, it will use update-nvram, remove old loaders and reorder."
1789650,2018-09-13 18:40:06 UTC,"Ryan and Andres, here are some things you've requested...."
1789650,2018-09-13 18:46:30 UTC,"Oh, I missed one question: The servers are all set to ""EFI Boot"" under ""Power Configuration."""
1789650,2018-09-13 19:16:08 UTC,"Rod,"
1789650,2018-09-12 14:29:22 UTC,"After MAAS deploys a node, the node *SHOULD* be set to PXE-boot. This is, in fact, what happens on most computers (or does recently; the behavior of booting from disk was a bug several months ago). In recent tests (for 16.04.5 regression testing), I've seen this misbehavior of having the disk-boot option first in the boot list only on two Lenovo computers, so it looks like there's some new interaction going on."
1789650,2018-09-13 20:39:35 UTC,"I've never dug into the efibootmgr source code, so I don't know offhand where it's getting the BootCurrent variable, but /sys/firmware/efi/efivars/BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c is a plausible source. FWIW, on the deployed problem machine, /sys/firmware/efi/efivars/BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c does exist and contains plausible data. If you've got a custom deployment config you want me to run, I can do that; or I can give you access to our MAAS server and the trouble systems."
1789650,2018-09-19 15:52:55 UTC,"That was weird. After the previous attempt, the system looked OK when it was fully deployed -- BootOrder was set correctly. I therefore tried replicating the login while deploying, and this time the /sys/class/firmware directory looked more normal, but both it and efibootmgr (once installed) showed no BootCurrent variable:"
1789650,2018-09-13 19:45:01 UTC,Looks like this comes from reading:
1789650,2018-09-14 20:12:04 UTC,If you can ssh in during deployment you can see if bootcurrent is available.
1789650,2018-09-14 19:34:43 UTC,"It can't be a simple matter of BootCurrent not existing when PXE-booted, since after adjusting BootOrder manually and rebooting, it is present:"
1789650,2018-09-14 18:54:21 UTC,"Related:
   https://bugzilla.redhat.com/show_bug.cgi?id=1031876"
1789650,2018-09-14 18:00:03 UTC,"Rod,"
1789650,2018-09-19 15:24:44 UTC,During deployment:
1789650,2018-09-14 17:10:12 UTC,Here are the install files using your modified MAAS preseed.
1789650,2018-09-14 16:34:28 UTC,Here's an updated late_command to deploy with.
1789650,2018-09-14 16:08:00 UTC,"On Fri, Sep 14, 2018 at 9:51 AM Ryan Harper <email address hidden> wrote:

>
> On Thu, Sep 13, 2018 at 6:35 PM Rod Smith <email address hidden> wrote:
> >
> > I'm afraid the node is failing to deploy with those changes to
> > /etc/maas/preseeds/curtin_userdata (I assume that's where you wanted
> > them):
> >
> >         Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmpzfw22u7e/target', 'sh', '-c', 'ls -al /sys/firmware/efi\nbcurrent=$(ls /sys/firmware/efi/efivars/BootCurrent*)\n[ -e ""${bcurrent}"" ] && hexdump $bcurrent\n'] with allowed return codes [0] (capture=False)
> >         total 0
> >         drwxr-xr-x  5 root root    0 Sep 13 23:10 .
> >         drwxr-xr-x  6 root root    0 Sep 13 23:08 ..
> >         -r--r--r--  1 root root 4096 Sep 13 23:10 config_table
> >         dr-xr-xr-x  2 root root    0 Sep 13 23:08 efivars
> >         -r--r--r--  1 root root 4096 Sep 13 23:10 fw_platform_size
> >         -r--r--r--  1 root root 4096 Sep 13 23:10 fw_vendor
> >         -r--r--r--  1 root root 4096 Sep 13 23:10 runtime
> >         drwxr-xr-x  9 root root    0 Sep 13 23:10 runtime-map
> >         -r--------  1 root root 4096 Sep 13 23:09 systab
> >         drwxr-xr-x 70 root root    0 Sep 13 23:10 vars
> >         ls: cannot access '/sys/firmware/efi/efivars/BootCurrent*': No such file or directory
>
> Yuck, I was seeing the same thing in my VM, but I was sure it was an
> issue with the VM.
>
> I cannot fathom why that sys path is not accessible.  Let me look more
> into my VM and see what's going on.
"
1789650,2018-09-14 14:51:55 UTC,"On Thu, Sep 13, 2018 at 6:35 PM Rod Smith <email address hidden> wrote:

>
> I'm afraid the node is failing to deploy with those changes to
> /etc/maas/preseeds/curtin_userdata (I assume that's where you wanted
> them):
>
>         Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmpzfw22u7e/target', 'sh', '-c', 'ls -al /sys/firmware/efi\nbcurrent=$(ls /sys/firmware/efi/efivars/BootCurrent*)\n[ -e ""${bcurrent}"" ] && hexdump $bcurrent\n'] with allowed return codes [0] (capture=False)
>         total 0
>         drwxr-xr-x  5 root root    0 Sep 13 23:10 .
>         drwxr-xr-x  6 root root    0 Sep 13 23:08 ..
>         -r--r--r--  1 root root 4096 Sep 13 23:10 config_table
>         dr-xr-xr-x  2 root root    0 Sep 13 23:08 efivars
>         -r--r--r--  1 root root 4096 Sep 13 23:10 fw_platform_size
>         -r--r--r--  1 root root 4096 Sep 13 23:10 fw_vendor
>         -r--r--r--  1 root root 4096 Sep 13 23:10 runtime
>         drwxr-xr-x  9 root root    0 Sep 13 23:10 runtime-map
>         -r--------  1 root root 4096 Sep 13 23:09 systab
>         drwxr-xr-x 70 root root    0 Sep 13 23:10 vars
>         ls: cannot access '/sys/firmware/efi/efivars/BootCurrent*': No such file or directory
"
1789650,2018-09-13 23:23:52 UTC,I'm afraid the node is failing to deploy with those changes to /etc/maas/preseeds/curtin_userdata (I assume that's where you wanted them):
1789650,2018-09-13 21:29:50 UTC,"On Thu, Sep 13, 2018 at 3:50 PM Rod Smith <email address hidden> wrote:

>
> I've never dug into the efibootmgr source code, so I don't know offhand
> where it's getting the BootCurrent variable, but
> /sys/firmware/efi/efivars/BootCurrent-8be4df61-93ca-11d2-aa0d-
> 00e098032b8c is a plausible source. FWIW, on the deployed problem
> machine, /sys/firmware/efi/efivars/BootCurrent-8be4df61-93ca-11d2-aa0d-
> 00e098032b8c does exist and contains plausible data. If you've got a
> custom deployment config you want me to run, I can do that; or I can
> give you access to our MAAS server and the trouble systems.
"
1789652,2018-08-29 13:51:56 UTC,"2018-08-29 12:18:32 Error executing autopkgtest:ubuntu-18.10-amd64:tests/main/dirs-not-shared-with-host:alternatives :
-----
+ . /home/gopath/src/github.com/snapcore/snapd/tests/lib/dirs.sh
++ export SNAP_MOUNT_DIR=/snap
++ SNAP_MOUNT_DIR=/snap
++ export LIBEXECDIR=/usr/lib
++ LIBEXECDIR=/usr/lib
++ export MEDIA_DIR=/media
++ MEDIA_DIR=/media
++ case ""$SPREAD_SYSTEM"" in
+ echo 'We can check the inode number of /etc/alternatives'
We can check the inode number of /etc/alternatives
++ stat -c %i /etc/alternatives
+ host_inode=312
+ '[' -e /snap/core/current ']'
++ stat -c %i /snap/core/current//etc/alternatives
stat: cannot stat '/snap/core/current//etc/alternatives': No such file or directory
+ core_inode="
1789652,2019-10-07 00:44:21 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1789652,2019-10-07 12:03:51 UTC,Tests look to be passing now with 4.18 kernels.
1789654,2018-09-05 18:22:31 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/597560"
1789654,2018-09-06 16:05:35 UTC,This was fixed by https://review.openstack.org/#/c/598365/
1789654,2018-09-14 10:51:02 UTC,"Reviewed:  https://review.openstack.org/599672
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=01265b98c4cd2b1377e891a06ce748fc6f8f3425
Submitter: Zuul
Branch:    stable/rocky"
1789654,2018-09-21 09:20:58 UTC,"Reviewed:  https://review.openstack.org/599673
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a039f8397702d15718ebcec0fdb9cfeb6155f6a1
Submitter: Zuul
Branch:    stable/rocky"
1789654,2018-10-22 16:21:05 UTC,"Reviewed:  https://review.openstack.org/597553
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9c842d1aa68d67383114f783c946492282832e5b
Submitter: Zuul
Branch:    master"
1789654,2018-10-24 22:14:40 UTC,"Reviewed:  https://review.openstack.org/597560
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ade240b392563914c1bddc228a3eb00585177d4c
Submitter: Zuul
Branch:    master"
1789654,2019-03-26 07:55:17 UTC,"Reviewed:  https://review.openstack.org/647291
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7a3b072442db74418fa7fe626c637627d219c71f
Submitter: Zuul
Branch:    stable/queens"
1789654,2019-03-25 05:36:00 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/647291"
1789654,2019-03-25 05:46:29 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/647292"
1789654,2018-09-05 11:50:33 UTC,"Reviewed:  https://review.openstack.org/599670
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c45adaca5dd241408f1e29b657fe6ed42c908b8b
Submitter: Zuul
Branch:    master"
1789654,2019-03-28 03:19:43 UTC,"Reviewed:  https://review.openstack.org/647292
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f8c0c4671c0b4967d9ccf9d84df575475fe3dddc
Submitter: Zuul
Branch:    stable/pike"
1789654,2019-03-28 03:33:05 UTC,"Reviewed:  https://review.openstack.org/613271
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=705284e18c3a9f2c93ecb15bd1bfee5d7710b684
Submitter: Zuul
Branch:    stable/queens"
1789654,2019-04-18 17:45:37 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/613263
Reason: Abandoning per rado."
1789654,2018-10-25 10:48:17 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/613263"
1789654,2018-09-05 11:50:22 UTC,"Reviewed:  https://review.openstack.org/598365
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2588af87c862cfd02d860f6b860381e907b279ff
Submitter: Zuul
Branch:    master"
1789654,2018-10-25 11:02:13 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/613271"
1789654,2018-09-04 16:22:03 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599672"
1789654,2018-08-29 14:36:54 UTC,Logs for the failed debian rocky run:
1789654,2018-09-04 16:22:18 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599673"
1789654,2018-08-29 14:43:51 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/597553"
1789654,2018-08-29 14:56:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/597560"
1789654,2018-08-29 17:56:57 UTC,https://review.openstack.org/#/c/597613/ should get the nova debug log patch into the xen CI testing.
1789654,2018-08-30 13:33:04 UTC,Got some debug logs from a failed xen CI run:
1789654,2018-08-30 14:03:25 UTC,My working theory is that the ResourceTracker._copy_resources method is setting the ComputeNode.cpu_allocation_ratio (and other alloc ratios) to 0.0 based on config here:
1789654,2018-08-30 14:19:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/598176"
1789654,2018-08-31 15:17:37 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/598176
Reason: Let's hope this works:"
1789654,2018-08-30 20:52:25 UTC,"We have a new xen CI run with the more detailed debug logs now and it's basically confirming what I think the problem was, but apparently this is a race because this time the xen CI job passed."
1789654,2018-09-04 16:14:48 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/599670"
1789654,2018-09-01 23:22:09 UTC,"BTW, if xenserver, powervm and vmware CI are all failing on this, it's not only intermittent but seems to also be isolated to virt drivers that don't implement the update_provider_tree method for whatever reason. Must be something in that alternative flow through the scheduler report client to report inventory updates to placement, likely because in the case of the libvirt driver, which does implement update_provider_tree, we're passing the same provider tree that the driver worked on to the scheduler report client, and in the non-libvirt case, we're passing an inventory dict to scheduler report client and the scheduler report client is updating its own view of the provider tree, which might be stale somehow."
1789654,2018-09-01 23:10:12 UTC,According to Rado in https://review.openstack.org/#/c/270116/ this also impacts the vmware CI.
1789654,2018-08-30 20:07:34 UTC,I also wonder if this is somehow contributing to the problem: https://review.openstack.org/#/c/518294/ - but that was in Queens. But maybe that combined with https://review.openstack.org/#/c/520024/ is causing a side effect.
1789654,2018-08-30 22:05:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/598365"
1789654,2018-08-31 20:57:48 UTC,"Anecdotal reports say we were failing PowerVM CI 90% of the time. I'm going to run https://review.openstack.org/#/c/598365/ through a couple of times, but initial results look positive."
1789656,2018-08-31 10:49:45 UTC,Does it happen if you start chromium with a new temporary profile?
1789656,2019-12-24 02:10:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789656,2019-11-28 09:36:25 UTC,"Hello,"
1789656,2019-11-28 08:47:15 UTC,Could you try if a wayland session behaves differently from an xorg one? Do you have anything printed in the journal log at the time that happens?
1789656,2019-12-12 12:36:31 UTC,This is the journal just before freeze. It does not seem to be referred to Chrome
1789656,2019-11-26 12:50:51 UTC,It happens to me too. Same problem. Related to Chrome or Chromium.
1789656,2019-05-31 07:00:17 UTC,"The issue was solved from my side by switching back to firefox. Before I had complete freezes but only the browser, this problem seems to be solved.
Since not using chromium there was no machine freeze at all."
1789656,2018-09-06 15:17:35 UTC,Thanks for the feedback Sam. I updated the title of the bug because it's very unlikely that that specific error message in the logs has anything to do with the actual cause of the freeze.
1789656,2018-08-31 12:48:02 UTC,"Thanks for taking the time, regarding q1, no, I have a second profile without starting 20 tabs and it never caused a system freeze.
Regarding q2, yes adblock plus and ip-domain-flag, but adblock is turned off anyway on this specific profile with 20 tabs open on start.
The crux is it occurs sporadic, I have this profile open five days a week at least five hours, but the system freeze occurs every two to three days."
1789656,2019-11-27 13:55:16 UTC,"UPDATE: it seems just to freeze mouse and keyboard input, since I am able to see desktop notifications and other stuff going on."
1789659,2018-09-06 15:57:41 UTC,"Hello Silvio, or anyone else affected,"
1789659,2018-10-09 10:30:41 UTC,"@Govinda - the remaining issue you mention is unrelated to the one we discussed and fixed here.
For everybody else that wants to follow, Govinda file bug 1794997 about that (Thanks)."
1789659,2018-09-28 14:01:42 UTC,"Christian,"
1789659,2018-09-28 06:44:36 UTC,"@Anish - it fixes the first of your messages in comment #8
The second is yet unknown/undebugged to me - in case you hit that still regularly I'd need an extra bug with much more information. The info in this bug here was about the hash issue that is now fixed."
1789659,2018-09-27 22:07:16 UTC,Does this also fix comment#8 ?
1789659,2018-09-27 20:12:06 UTC,Will this be back ported to xenial libvirt 3.6.x?
1789659,2018-09-13 08:10:33 UTC,This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.5
1789659,2020-07-22 14:22:41 UTC,"Apologies, pike is EOL and this is fixed in bionic."
1789659,2018-09-13 08:00:34 UTC,"The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1789659,2018-09-10 10:22:45 UTC,"Pre update test:
$ sudo ./test-lp1789659.sh
+ concurrency=40
+ duration=60
+ guests=4
+ uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
+ date +%F %T
+ starttime=2018-09-10 10:16:58
+ set +x
+ sleep 60s
uvt-kvm: error: libvirt: storage volume 'b1.qcow' exists already
+ date +%F %T
+ endtime=2018-09-10 10:17:58
+ pkill -P 5261
+ seq 1 4
+ uvt-kvm destroy b1
+ uvt-kvm destroy b2
+ uvt-kvm destroy b3
+ /bin/true
+ uvt-kvm destroy b4
+ /bin/true
+ journalctl -u libvirtd --since 2018-09-10 10:16:58 --until 2018-09-10 10:17:58
+ grep Hash operation
Sep 10 10:16:58 node-horsea libvirtd[3115]: 2018-09-10 10:16:58.914+0000: 3277: error : virHashForEach:597 : Hash operation not allowed during iteration
Sep 10 10:16:59 node-horsea libvirtd[3115]: 2018-09-10 10:16:59.326+0000: 3278: error : virHashForEach:597 : Hash operation not allowed during iteration
[...] ~80 of them"
1789659,2018-09-28 14:25:18 UTC,@Christian
1789659,2018-09-05 14:12:03 UTC,"I ran a set of regression tests - all looking good.
Summary of the x86 test (others the same):
stage0-prep: Pass    4 Failed    0 Skip    0 + 0    - RC 0    in 13 minutes
stage1-migrate: Pass  276 Failed    0 Skip    0 + 0    - RC 0    in 95 minutes
stage2-cross: Pass   22 Failed    0 Skip    0 + 1    - RC 0    in 35 minutes
stage3-misc: Pass  103 Failed    0 Skip    0 + 0    - RC 0    in 45 minutes
stage4-qemu: Pass    1 Failed    0 Skip    0 + 0    - RC 0    in 41 minutes"
1789659,2018-09-05 09:23:54 UTC,"Can appear in two forms (maybe more):
  virHashSearch:727 : Hash operation not allowed during iteration
  virHashForEach:597 : Hash operation not allowed during iteration"
1789659,2018-09-05 09:58:13 UTC,PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3404
1789659,2018-08-29 14:40:01 UTC,"This is upstram since 4.3 and thereby fixed in Cosmic.
Haven't had the time to look in depth and consider an SRU for Bionic ..."
1789659,2018-08-29 14:48:04 UTC,"It essentially removes a check for concurrency.
At the time it was added it was considered safe, but never the less in 4.0 (Bionic) there could be races left - just as much as there could be races not yet detected upstream.
I'd think this has a higher than usual regression risk."
1789659,2018-08-29 14:48:44 UTC,Incomplete for now waiting for help on repro steps for latter SRU process.
1789659,2018-09-04 07:05:09 UTC,I have just verified that the reproducer for Red Hat Enterprise Linux is valid for Bionic:
1789659,2018-09-05 07:16:14 UTC,"I had some more reports on this on IRC and per mail, so I set prio high."
1789659,2018-09-04 08:00:05 UTC,The reproduce is all I needed - thanks a lot!
1789659,2018-09-04 21:52:39 UTC,"Christian,"
1789659,2018-09-05 08:12:26 UTC,I did a code review to check for potential changes between 4.0 (what we have in Bionic) and 4.3 (when upstream created the fix) but found none that would make this change non-backportable (I was afraid of unrelated commits being required to make this safe - therefore the extra dive into the src).
1789659,2018-09-04 07:05:45 UTC,JFI: SUSE Linux Enterprise and openSUSE variants also added this patch to respective packages.
1789659,2018-09-05 08:21:55 UTC,"Extended the regression considerations by some content from the commit and discussions I found.
It is safe IMHO, but I need to explain the SRU team why."
1789660,2020-01-17 09:06:14 UTC,"It's a soname transition which Debian is going to start, we will follow once they do"
1789669,2018-08-29 19:22:21 UTC,">  /c/Windows/WinSxS/amd64_microsoft-windows-l..b-onecore....
"
1789679,2019-05-23 18:34:40 UTC,"I like the idea, but I think there needs to be a bit of additional work so that users can signal in the template and/or when creating a report that they want this behavior. Otherwise, somebody who uses a given template for statistics that they generate reports from periodically may be in for an unwelcome surprise."
1789679,2019-09-17 19:49:26 UTC,"Note that Postgres 9.6+ is now required for EG 3.4 (bug 1830749), so GROUP BY ROLLUP should be supportable in EG 3.4+."
1789679,2020-02-21 21:00:18 UTC,"I've force-pushed a rebased and updated branch that makes this feature optional, via the report definition interface and a new ""Calculate grouping subtotals"" checkbox.  As a side note, using this new feature with a pivot column is handy -- it provides a leading subtotal column for each combination of non-pivot columns."
1789679,2020-02-26 20:56:48 UTC,I signed off on Mike's fix and added a commit tweaking whitespace (tabs over spaces to match the file formatting) and uncheck the new checkbox by default so people don't see things change unexpectedly.
1789679,2020-08-19 19:07:11 UTC,This may need a rebase since it was signed off back in February.
1789679,2020-08-19 19:32:16 UTC,"Rebased branch available at the same location, with release notes.  Needs a signoff on my second commit, at least."
1789679,2020-08-19 19:34:57 UTC,"I signoff of this commit.
Lynn Floyd
<email address hidden>"
1789679,2020-08-24 16:11:38 UTC,"Pushed to master for inclusion in 3.6, along with a follow-up that adds an illustrative example to the release notes. Thanks, Mike, Chris, and Lynn!"
1789679,2018-08-29 15:42:18 UTC,Branch coordinates: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1789679-report-rollup
1789679,2019-05-23 18:35:06 UTC,"Also, I'm going to take this bug as an opportunity to start a discussion on whether we want to bump up the minimum required Pg version for 3.4."
1789682,2018-08-29 17:26:35 UTC,"backtrace:
[New Thread 1360.0x2594]"
1789682,2018-08-29 17:22:31 UTC,"- reproduced on Windows 10, Inkscape 0.92+devel (d890608, 2018-08-21) using the attached file."
1789682,2020-08-18 14:44:53 UTC,"Fixed for 1.0, was reported on GitLab https://gitlab.com/inkscape/inbox/-/issues/134 , fixed by abf707b5bc033615b24f7048fcccaa3a9a5148c6"
1789689,2018-08-29 16:13:05 UTC,The initial error reported above is due to a change in ovs 2.10. Upper-constraints is at 2.9.2 so this doesn't yet officially affect upstream code.
1789689,2019-09-04 07:56:02 UTC,Thanks Corey
1789689,2018-08-29 18:28:01 UTC,I'm attaching the patch that we'll carry in Ubuntu.
1789689,2019-09-03 08:03:42 UTC,"Hi Corey, if I understand well this bug can be closed in networking-l2gw, am I right?"
1789689,2019-09-03 11:57:34 UTC,"Hi Lajos, I think it needs to be fixed upstream once ovs 2.10 is supported."
1789692,2018-08-29 19:18:28 UTC,This might help... sounds more like a problem in your preseed.
1789692,2018-08-29 20:52:00 UTC,"One other suggestion.  Can you install the machine manually by pxebooting the installer WITHOUT that preseed, and manually performing the install?"
1789692,2018-08-29 20:52:24 UTC,"And finally, does any of this work via MAAS?"
1789692,2018-09-09 13:05:43 UTC,This is the  comments passed by  internal team.
1789692,2018-09-13 13:20:12 UTC,"OK... so how exactly are you PXE booting and what image are you using, exactly?"
1789692,2018-09-13 17:30:31 UTC,I am unable to recreate this myself in VMs... Michael may have other ideas too.
1789692,2018-09-13 17:31:41 UTC,"From your comments so far, it sounds like a driver issue in the initrd.gz image for netbooting.  What hardware is this?"
1789692,2018-09-13 18:38:43 UTC,I see this in my environment with UCS blade servers as well. I believe we are probably using the same server iso as BP that I downloaded from Canonical and copied to our repo. I am using the same procedure and preseed file that we use for xenial and trusty releases which work. This is being tested with Cisco UCS B200M4 currently.
1789710,2019-09-19 11:58:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1789712,2019-09-16 14:41:05 UTC,Migrated to https://github.com/widelands/widelands/issues/3307
1789712,2018-09-02 08:42:14 UTC,"I wouldn't consider the workarea as a big problem, if some parts are behind the buildhelp. In the past GunChleoc had also the idea to have a blended color with outlined border: https://wl.widelands.org/forum/topic/1884/?page=1#post-15793 We shouldn't forget that the buildhelp can easily be disabled."
1789712,2018-09-02 09:51:15 UTC,"I wasn´t aware that the workarea had been discussed so extensively before. I dislike the floating images in the settlers screenshot, it looks very strange to me.
I think the fact that the buildhelp obscures the work area is a bug and should be fixed. I always turn buildhelp on when looking for a good space for a farm, claypit etc, then I have to turn it off to see whether there´s enough space around, then on again to find a better place, and so on. That´s annoying. So either the buildhelp icons should be more transparent, but that makes them hard to see. Or the workarea icons could be replaced with blended colour and border (which I also find more aesthetically pleasing). Secondary influence areas could have a different blend&border colour."
1789712,2018-09-02 12:45:44 UTC,"The ones with intense colors fit best with the other buildhelp icons, imho. So blueish (2.row/1.colummn and 2.r/2.c), light orange (1.r/4.c), green (3.r/4.c), pink (4.r/4.c) or ocre (3.r/3.c)."
1789712,2018-09-02 13:42:52 UTC,"Here are the six you named with all mountain terrains as background :)
I think we can forget ocre and orange, they´re invisible on desert mountains. Pink and electric blue are poor as well against wasteland resp. winter. In my opinion, green is the best with dark blue a close second."
1789712,2018-09-02 16:15:48 UTC,"Tested them in-game. Here dark blue looks best in my opinion, so I vote for that."
1789712,2018-09-03 07:39:29 UTC,I think no amount of fiddling with the colors of that mining icon will make it look good. It needs to be redone completely.
1789712,2019-03-10 20:11:46 UTC,Purely experimental approach at the moment…
1789712,2019-03-11 07:51:41 UTC,Yes yes yes - I have wanted this for a long time!
1789712,2019-03-11 14:46:55 UTC,Now using a shader instead…
1789712,2018-09-01 18:53:55 UTC,"I gave the buildhelp icons for houses some transparency to let the work area shine through (screenshot: old above, new below). The secondary work area is still hard to see, but making the buildhelp even more transparent makes it almost invisible. So I´d suggest to change the work area overlays as well and give them a stronger colour."
1789712,2018-09-01 19:41:05 UTC,"Another suggestion: for the work area, we could replace the circles on each node with something like in this mockup"
1789713,2018-08-30 12:09:39 UTC,"Have you tried the first solution here:
https://askubuntu.com/questions/1062031/screen-flickering-in-ubuntu-18-04-1-lts
if that doesn't fix the issue, can you please post the issue on the support forum:
https://forum.peppermintos.com
where we'll try our best to get to the bottom of the issue."
1789713,2018-08-30 14:01:39 UTC,Thanks for the reply.
1789749,2018-08-30 15:20:26 UTC,It seems I didn't do a good explanation.
1789749,2018-08-31 02:30:47 UTC,"Oh wow. Thanks, I can reproduce the bug now."
1789749,2018-08-31 09:45:03 UTC,Thanks a lot! 👍
1789749,2018-09-03 02:18:54 UTC,"Discussion continues upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/517"
1789749,2020-07-30 02:15:01 UTC,This was fixed in 3.31.90.
1789749,2018-08-30 02:32:43 UTC,Please report this bug to the Gnome developers here:
1789758,2020-11-06 04:17:20 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1789758,2018-08-30 02:37:43 UTC,"Reassigned to pulseaudio. Bluetooth audio is a software feature implemented in pulseaudio, not in bluez."
1789758,2019-01-23 02:41:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789758,2020-09-07 02:24:27 UTC,There are two problems in your logs that might be relevant:
1789760,2018-08-29 23:32:26 UTC,"And this isn't a bug, but I cannot tolerate the button being on the left when new tabs open on the right. Is there an easy way for me to to modify the source myself to have a text new tab button on the right?"
1789760,2018-08-29 23:37:16 UTC,"It's also really silly that the forward button says ""Next or Forward,"" but I can change that to whatever I want by editing the .po/.mo locale files so I don't care."
1789766,2019-01-20 08:52:41 UTC,This bug was fixed in the package snapcraft - 2.43.1+18.10
1789766,2018-09-13 08:10:58 UTC,This bug was fixed in the package snapcraft - 2.43.1+18.04
1789766,2018-09-13 08:01:06 UTC,This bug was fixed in the package snapcraft - 2.43.1
1789766,2018-09-13 08:00:58 UTC,"The verification of the Stable Release Update for snapcraft has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1789766,2018-09-06 13:41:28 UTC,"Hello Sergio, or anyone else affected,"
1789766,2018-09-13 03:15:09 UTC,upgrade testing on xenial good
1789766,2018-09-06 13:35:49 UTC,"Hello Sergio, or anyone else affected,"
1789766,2018-09-06 13:35:29 UTC,Hope the issues with the disabled tests have been reported somewhere for tracking. Wouldn't want disabled tests to stay around for too long.
1789766,2018-09-05 16:47:08 UTC,"failed https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-snapcraft-daily/xenial/amd64/s/snapcraft/20180905_141633_8c584@/log.gz
we disabled the failing tests given that they are too slow now after the patchset and not as representative anymore"
1789766,2018-09-13 03:26:40 UTC,upgrade testing on bionic good
1789766,2018-09-05 16:25:23 UTC,bionic amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-snappy-dev-snapcraft-daily/bionic/amd64/s/snapcraft/20180905_080851_8c584@/log.gz
1789769,2018-08-31 01:33:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789771,2018-08-30 02:37:48 UTC,Looks like if iscsi-initiator-utils is installed on the undercloud it can prevent the container from starting properly
1789771,2018-08-30 17:52:02 UTC,I couldn't reproduce the bug on centos7 with libiscsi-1.9.0-7.el7.x86_64 and centos-binary-iscsid:9ad93affedba8870315dd72c714770875ce24759_b72f0c42.
1789771,2018-08-30 17:52:52 UTC,"Also, note that on a fresh undercloud deployed by hand from a clean centos7 image, iscsi-initiator-utils  wasn't installed."
1789774,2018-09-11 10:05:30 UTC,"<cjwatson> At that time there was a problem with the backend
<cjwatson> 2018-09-10 02:25:29+0000 [Uninitialized] Backend connection failed
<cjwatson>         Traceback (most recent call last):
<cjwatson>         Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused."
1789774,2018-09-11 09:37:13 UTC,Maybe https://paste.ubuntu.com/p/QJXJyYQZCF/ has better formatting.
1789774,2018-09-07 11:28:19 UTC,"so debug traces were added, and now they all pass (with and without traces). le sigh."
1789774,2018-08-30 02:51:28 UTC,It doesn't seem likely that this has anything to do with Launchpad. You'll need to try to reproduce it outside an autopkgtest and ideally get logs with GIT_CURL_VERBOSE=1 GIT_TRACE=1.
1789774,2018-08-30 03:39:48 UTC,"what confuses me is why ""https://"" protocol is used here, instead of git:// protocol."
1789774,2018-08-30 03:22:47 UTC,https://bileto.ubuntu.com/#/ticket/3394 should end up with autopkgtests detailing what's happening.
1789774,2018-08-30 02:34:38 UTC,Similarly:
1789774,2018-08-31 06:00:30 UTC,"git clone should work with these:
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic
git+ssh://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic"
1789774,2018-08-30 02:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1789775,2018-08-30 02:57:48 UTC,Please include your KiCad version
1789775,2018-08-30 13:00:21 UTC,Here it is.
1789775,2019-08-03 03:06:15 UTC,"Fixed in revision b8a03be8698db69ba02c7a9f4eec461fe02f9372
https://git.launchpad.net/kicad/patch/?id=b8a03be8698db69ba02c7a9f4eec461fe02f9372"
1789800,2019-03-22 03:47:52 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1789800,2018-09-24 14:46:53 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1789800,2018-09-06 06:10:35 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/600336"
1789800,2018-09-06 00:50:09 UTC,"Reviewed:  https://review.openstack.org/597986
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad1d9bd66e6a1c3538b426021962470599e480c5
Submitter: Zuul
Branch:    master"
1789800,2018-09-07 03:01:33 UTC,"Reviewed:  https://review.openstack.org/600336
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd0a0ef0e2810349a5bd645a9723c20aa2bab990
Submitter: Zuul
Branch:    stable/rocky"
1789800,2018-08-30 05:09:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/597986"
1789828,2018-09-14 16:23:31 UTC,"Fix proposed to branch: stable/18.08
Review: https://review.openstack.org/602676"
1789828,2018-09-14 16:19:22 UTC,"Reviewed:  https://review.openstack.org/600048
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=b04b5f3b5f00f67eef2b76fbb5b64aba2b80719d
Submitter: Zuul
Branch:    master"
1789828,2018-09-05 13:57:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/600048"
1789828,2018-09-17 07:05:56 UTC,"Reviewed:  https://review.openstack.org/602676
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=3fb70295afadec26dc2d0fdae822bc0184b87e87
Submitter: Zuul
Branch:    stable/18.08"
1789828,2018-09-04 07:11:47 UTC,"@hopem, yeah, I think you're totally right, all the places calling RBDVolumeProxy should have the same problem. This is a problem caused by the mix of green thread and local thread, the race between _get_usage_info and delete_volume is just one of them, so thank you very much to amend my previous title from 'racy between _get_usage_info and delete_volume' to 'race between threaded rbd operations' to react more closely to practical problem."
1789828,2018-09-03 19:58:06 UTC,@gorka that patch fixed a separate instance of this issue i.e. it catches ImageNotFound if it is raised at [0] but not if it is raised at [1] which is where this issue is still occurring.
1789828,2018-09-03 12:20:41 UTC,This looks like a duplicate of https://bugs.launchpad.net/cinder/+bug/1765845 which has already been fixed.
1789828,2018-08-30 09:01:32 UTC,So this is mostly correct but what I've seen is that the green thread that is waiting on the native thread never gets re-scheduled in the case where the threaded operation raises an exception and doesn't explicitly handle it. In other words the green threads calling the native threads gets stuck but other green threads still operate as normal. This simple test script seems to demonstrate the same behaviour - https://pastebin.ubuntu.com/p/JXgzhppKwr/
1789828,2018-09-04 15:04:30 UTC,"Ok I think I have a more accurate picture of what is going on here. For context I should say that we have observed this issue in an environment where a very large number (several thousand) of volumes where deleted at once and this manifested as all rpc threads consumed by the tasks that ensue. The *real* problem here is simply that when deleting an RBD volume, each rpc threads servicing the request will (by default) list and query *every* volume. This has two fallouts, the first being that the get_usage_info loop [0] is racing with deletes because each time it gets a list of volumes, by the time it queries each entry in the list that volume may have been deleted. The second issue is simply that is it doing this query of all volumes for every query all the time which simply doesn't scale. The first (images not found) has been fixed as previously mentioned but the second issue is not resolved. There is a way to stop this behaviour from happening which is to enable rbd_exclusive_cinder_pool [1] such that provisioned_capacity_gb stats are not queried and updated on deletes (or in the periodic task for that matter). Apart from the caveat described in the config desc I don't see any pitfall since, so long as the pool is only used by cinder, the allocated_capacity_gb should not get out of sync with provisioned_capacity_gb although probably worth keeping an eye on this."
1789828,2018-09-03 20:02:52 UTC,"@zhhuabj see my above comment. I believe that the error you saw has actually been resolved and backported to ocata (i.e. the bug ref'd by @gorka) but there is still a related bug in the rbd driver which is not yet fixed. I am able to 100% repro this issue by deploying Queens, creating 100 volumes then deleting them all at once. The error in the logs is https://pastebin.ubuntu.com/p/zBFHPffzgh/ which is the same exception that you mentioned but is raised in a different place."
1789830,2018-10-09 13:30:44 UTC,"Processing triggers for linux-image-4.15.0-33-generic (4.15.0-33.36) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-33-generic
/usr/share/initramfs-tools/hooks/framebuffer: 146: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
/usr/share/initramfs-tools/hooks/framebuffer: 65: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
E: /usr/share/initramfs-tools/hooks/framebuffer failed with return 2.
/usr/sbin/mkinitramfs: 181: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/update-initramfs: 165: /usr/sbin/update-initramfs: Cannot fork
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
dpkg: error processing package linux-image-4.15.0-33-generic (--configure):
 installed linux-image-4.15.0-33-generic package post-installation script subprocess returned error exit status 1"
1789836,2018-09-03 09:23:56 UTC,I tried to update the undercloud and overcloud. But when trying to add the new node I still get the error...
1789836,2018-09-03 10:59:40 UTC,The paunch configuration for stage3 is here (it seems to contain the :shared for all bind of /var/lib/nova):
1789836,2018-09-04 08:10:16 UTC,"Does not work on the new compute node:
[root@lab-compute-3 heat-admin]# mount -t xfs
/dev/vda3 on / type xfs (rw,relatime,seclabel,attr2,inode64,noquota)"
1789836,2018-09-04 08:19:47 UTC,"""docker info"" has some suspect things:
[root@lab-compute-3 heat-admin]# docker info
Containers: 4
 Running: 1
 Paused: 0
 Stopped: 3
Images: 7
Server Version: 1.12.6
Storage Driver: overlay2
 Backing Filesystem: xfs
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
 Volume: local
 Network: overlay null host bridge
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Security Options: seccomp
Kernel Version: 3.10.0-693.2.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 6
Total Memory: 23.39 GiB
Name: lab-compute-3
ID: CVHV:HFK5:WV6P:N2BV:AUTW:TDBW:JLKX:AEJN:XR5T:SARL:5ZVC:2XMO
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
 127.0.0.0/8
Registries: docker.io (secure)"
1789836,2018-09-04 08:31:24 UTC,So apparently I needed to update the deployment images because de deployment process of a new node does NOT execute yum update... I will try again with deployment images updated...
1789836,2018-09-06 07:50:50 UTC,Ok. After updating the deployment images. I finally managed to insert the new node into the cluster.
1789837,2019-09-16 14:00:03 UTC,Migrated to https://github.com/widelands/widelands/issues/2112
1789837,2018-09-30 16:09:24 UTC,I will gladly do so (although I do not know at the moment when I'll find some time again). And of course code review is obligatory the next time :).
1789837,2018-09-30 14:43:52 UTC,Shit happens - I hope you'll still want to take up this bug when you're less busy?
1789837,2018-08-31 17:28:16 UTC,"I agree with you as well... and as I created the sunset graphic shown on the splash screen, I thought it was more or less my task to give you an option for hiding the splash screen anyways ;)."
1789837,2018-08-31 18:00:10 UTC,"I think there was a discussion about removing the splash screen some time ago, and an argument for keeping it was that it gives new players a nice first impression about Widelands. I agree with that; when I was new to Widelands I liked that I was greeted with this beautiful image and not just the main menu. It´s only after a while that one gets used to it and the effect lessens.
So I´d vote for showing it by default and either disabling it optionally or automatically fading into the main menu; of the two, I find an option somewhat more comfortable, as the gameloading time is already quite long and we don´t need another 3 seconds here ;)"
1789837,2018-09-18 18:59:45 UTC,Fix committed in bzr rev 8841
1789837,2018-08-30 17:00:01 UTC,I agree that this screen is annoying...
1789837,2018-09-30 09:14:34 UTC,"I am very sorry for the unneeded trouble I made! :(
Life got busy again over here and I understood your change from ""opinion"" to ""confirmed"" as a ""go""... I've simply been away from widelands too long and did not have all rules for code commits in mind - sorry!
Please just uncommit the change, reimplementation should be fairly easy after Build20."
1789837,2018-09-24 08:53:47 UTC,"> Solution: Make the checkbox initially checked.
"
1789837,2018-09-24 06:08:08 UTC,"I have reviewed the code now, looks OK. Needs testing (I'm still waiting for the compiler)"
1789837,2018-09-24 06:06:34 UTC,"We are in feature freeze. Please do not merge branches that introduce new features, especially wishlist features."
1789837,2018-09-24 06:37:38 UTC,"This works not correct: The Checkbox is initially unchecked, but the splashscreen is shown. I guess thats because the option isn't initially in the config file. Solution: Make the checkbox initially checked."
1789838,2018-08-31 07:31:34 UTC,https://gitlab.com/inkscape/inkscape/merge_requests/319
1789838,2019-03-06 11:44:39 UTC,Fix committed in master as 4deaa8e1.
1789839,2018-08-31 19:06:07 UTC,"I agree.
However other players might have some other menus they would prefer. Therefore the idea brings up another thought I already had for quite some time: we could provide an option menu similiar to other games that shows all available hot keys and gives the player the chance to change hot keys."
1789839,2018-08-31 19:36:39 UTC,"Nearly every in-game window already has its own hotkey, except the general stats, the economy stats, and most editor tools. I think the ideal would be for every unique window to have one."
1789839,2018-09-01 10:07:51 UTC,"I did take a stab at configurable hotkeys once, but never finished it because other issues took priority https://code.launchpad.net/~widelands-dev/widelands/configurable_hotkeys"
1789839,2019-09-17 10:35:12 UTC,Migrated to https://github.com/widelands/widelands/issues/2113
1789840,2018-12-05 04:06:04 UTC,"Various non-chunks sections of the database, in case they help (Canonical-only links, sorry):"
1789840,2018-12-05 03:58:37 UTC,"I stumbled across this again today, on the very same controller (based on the result of db.backups.files.find()) although this time the backups database only had 8GB in it.  Per thumper and rick_h, I dropped the backups database to release the space. The controller was running 2.4.5 this time."
1789840,2018-09-06 12:18:15 UTC,"This feels like something started creating backup files, and then we removed the *reference* to the backups, but didn't actually remove the backup content."
1789850,2018-09-12 16:16:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789850,2020-12-15 10:29:22 UTC,doesn't seem like a bug to me - it works as expected
1789850,2018-08-30 18:08:30 UTC,Thank you for your feedback.  Taking your comments one-by-one:
1789854,2018-08-30 10:43:28 UTC,Query plan from staging:
1789856,2018-08-30 08:57:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/598090"
1789856,2019-04-01 02:05:13 UTC,"Change abandoned by Yong Huang (<email address hidden>) on branch: master
Review: https://review.openstack.org/598090
Reason: Abandon it, will create one on Train if needed."
1789858,2018-09-01 01:16:23 UTC,"I just do some tweaks to inkscape with a MR:
I hope soon is fixed and improve HiDPI usage.
By the way you can get similar results but with baddest icons setting this enviroment variables in windows previously to run Inkscape."
1789858,2018-10-07 11:49:50 UTC,This should be fixed by the use of gtk3 in master ?
1789858,2018-12-01 01:21:09 UTC,Is there a fix for this? I have the same problem with my new Spectre.
1789858,2018-09-01 01:16:55 UTC,https://gitlab.com/inkscape/inkscape/merge_requests/320
1789858,2019-06-05 15:09:42 UTC,Still have same problem my system is Macbook 15 retina with Ubuntu 19.04 and Inkscape 92.4. The Icons still very small also if I have setup larger and also the bar for choose the colors it's so much small. In the picture you can see the size of the font it's OK but icons and colors bar isn't.
1789858,2018-08-30 13:33:23 UTC,Use larger not large
1789858,2019-06-30 17:58:33 UTC,(screenshot attached in previous comment)
1789858,2019-12-10 08:03:29 UTC,Hello all. I can confirm that 1.0beta2 fixes this on my Dell XPS w/ 4K monitor! I've installed the fancy AppImage version and that worked out of the box. The previous issue was that changing the icon size did absolutely nothing in the UI.
1789858,2020-01-22 16:44:48 UTC,"As above, I've also installed the AppImage from https://inkscape.org/release/inkscape-1.0beta2/
and it works amazing! I have a 4k Dell XPS, and so far I haven't noticed any bugs."
1789858,2018-08-31 17:15:45 UTC,"No, I was wrong... I run always the same file, sorry. In ""inkscape-0.92+devel_2018-08-21_d890608-x64"" icon are again normal... but settings has some problems. (Some options aren't visibled)"
1789858,2019-06-30 17:57:43 UTC,"Can confirm this problem in 0.92.4, and the mouse pointer and (especially) the vector handles are also way too small. It's almost impossible to actually grab the handles to edit them, no matter how much you zoom in."
1789858,2018-08-31 10:30:42 UTC,"You need to find a saccessful build from the list, use master branch.
Regards."
1789858,2018-08-30 09:15:52 UTC,here
1789858,2018-08-31 07:31:59 UTC,thanks @maren!
1789858,2018-08-30 23:05:49 UTC,"@jabiertxof : you can also use this link when you direct users to the development builds, it's going to be kept up-to-date, and it's for all systems:
https://inkscape.org/releases/master/"
1789858,2018-08-30 20:28:39 UTC,"Ok, thanks anyway. You were very polite!
(I'll try unstable version :) -> better than don't use)"
1789858,2018-08-30 19:27:04 UTC,is inestable please save frecuently
1789858,2018-08-30 19:26:37 UTC,":( couldent help more, maybe you can test the development version.
http://www.inkscapeforum.com/viewtopic.php?t=32932
Regards."
1789858,2018-08-30 15:58:34 UTC,"(I'm wrong to write. Icon size change, but they are still small xD Sorry)"
1789858,2018-08-30 15:57:53 UTC,I've tried every option but NOTHING change
1789858,2018-08-30 10:53:12 UTC,"Hi, I've tried to set ""Large"" but nothing change... I use Inkscape on Windows from Microsoft Store (maybe should I use installer?)"
1789858,2020-06-19 19:43:09 UTC,Also the color selection tool is to small. The largest icon size is just large enough.
1789858,2018-08-30 09:14:03 UTC,"Hi thansd for fill the bug, could you try to increase size of icons in preferences dialog?"
1789858,2018-08-31 08:44:18 UTC,"@Jabiertxof I go to link you send me, but I cannot download nothing https://ci.appveyor.com/project/inkscape/inkscape/build/job/s2sjl5u60nf6qx41/artifacts ""The build job does not contain any artifacts"""
1789862,2018-08-30 14:41:53 UTC,"I am using a script with networkd-dispatcher now:
/sbin/ip route add table 200 172.16.4.0/24 dev ens192
This correctly adds the route to the table 200."
1789862,2018-08-31 07:45:28 UTC,"Hi,"
1789862,2018-08-30 09:09:18 UTC,"Also when using scope: link the ""table"" option is ignored."
1789862,2018-08-30 13:46:26 UTC,"Hi Fabian,"
1789868,2018-08-30 10:03:32 UTC,"For Windows, IIUC, these are the Virtio drivers:drivers:"
1789868,2020-01-23 18:03:30 UTC,"Reviewed:  https://review.opendev.org/616603
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=de512f2c025429b72ade5a5ec38a6f1bde60af3c
Submitter: Zuul
Branch:    master"
1789868,2018-11-08 16:27:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616603"
1789868,2018-09-19 08:15:45 UTC,"Hmm, looking at Nova's Git history, we _had_ a default (/dev/random) by default:"
1789873,2018-08-30 13:09:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/598154"
1789873,2018-08-30 13:12:12 UTC,I'm guessing this was found after testing based on this question?
1789873,2018-08-30 13:13:17 UTC,"Hmm, our API documentation doesn't mention that you can specify vm_state multiple times:"
1789873,2018-08-31 01:45:21 UTC,"@Matt: Yes, I was playing with vm_state and status filters when I noticed that ""GET servers/detail?status=ACTIVE&status=shutoff"" gave me both active and shutoff VMs as expected, but the counterpart by vm_state filters only returned stopped/shutoff VMs."
1789885,2019-09-19 10:09:44 UTC,This issue was fixed in the openstack/networking-ovn 7.0.0.0b1 development milestone.
1789885,2018-10-23 06:08:43 UTC,https://review.openstack.org/#/c/601948/ is the patch working on this
1789885,2019-07-01 09:58:56 UTC,"Change abandoned by Reedip (<email address hidden>) on branch: master
Review: https://review.opendev.org/601948
Reason: Abandoning in favor of the new patch"
1789885,2019-07-09 12:15:36 UTC,"Reviewed:  https://review.opendev.org/668396
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=48cac11283b32e829d34f57c9f87bc207d184347
Submitter: Zuul
Branch:    master"
1789885,2019-07-25 07:21:34 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/672642"
1789885,2019-07-30 17:32:17 UTC,"Reviewed:  https://review.opendev.org/672642
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=6e8986ab210f7af7af4fb20335c2f6f13330790d
Submitter: Zuul
Branch:    stable/stein"
1789885,2020-02-18 14:09:29 UTC,This issue was fixed in the openstack/networking-ovn 6.0.1 release.
1789888,2018-09-02 20:26:43 UTC,"Your logfile reports some problems:
- the Cajon Pass route seems not to be installed correctly (.w files corrupted); I'd suggest to install it again
- there is a bunch of messages warning that sound files are missing, e.g.
Warning: File x_Airblast1.wav missing from C:\MSTS\trains\trainset\BNSF_ES44DC_7312_H3\sound\..\..\Audio_Shack_Sounds\FDL12_OpenRails ; check that and try to install the missing files
- there is a warning about OpenRailsLog.txt not being accessible at a certain moment: maybe you had a preceding instance of OR that didn't exit correctly?"
1789897,2018-10-01 17:20:33 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1024.26
1789897,2019-03-22 17:28:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789899,2018-09-01 07:19:10 UTC,"The solution is to permit linebreaks at - in any string, unless the element before the - is too short - let's say 3 letters minimum?"
1789899,2019-09-15 17:03:24 UTC,Migrated to https://github.com/widelands/widelands/issues/1077
1789910,2018-08-30 16:22:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1789912,2018-08-30 14:15:25 UTC,I re-ran 'sudo apt-get upgrade' in the proper way and it worked fine.
1789919,2019-05-14 11:48:03 UTC,"@Jason have you seen this again since? If it's happened again, please mark this bug as new again!"
1789919,2019-07-14 04:17:36 UTC,[Expired for OpenStack percona-cluster charm because there has been no activity for 60 days.]
1789921,2018-10-24 23:56:15 UTC,"Reviewed:  https://review.openstack.org/611672
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=03dc5ae1c3208ddf68d0afe5f1b29a04d65a2135
Submitter: Zuul
Branch:    stable/rocky"
1789921,2019-10-28 14:45:32 UTC,This issue was fixed in the openstack/networking-ovn 4.0.4 release.
1789921,2020-02-28 15:27:38 UTC,This issue was fixed in the openstack/networking-ovn 5.1.0 release.
1789921,2019-09-20 22:15:28 UTC,"Reviewed:  https://review.opendev.org/681565
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=1016280a92f89e5d6fa981529494544b0c11bc91
Submitter: Zuul
Branch:    stable/queens"
1789921,2018-10-18 16:19:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611672"
1789921,2019-03-11 14:45:11 UTC,This issue was fixed in the openstack/networking-ovn 6.0.0.0b1 development milestone.
1789921,2019-09-11 18:16:40 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/681565"
1789922,2018-08-30 15:33:41 UTC,"Actually it looks like it's gnome-disk-utility that does the unmount and throws the error.  I can't for the life of me figure out this rat nest of code though.  In gduresizedialog.c, resize() calls gdu_utils_ensure_unused() and passes it unmount_cb(), which appears to be what is throwing that error message after the unmount fails.  What I can't see is where the actual unmount is done.  gdu_utils_ensure_unused() appears to call g_task_new to set up a task to invoke that callback after the task itself as run, but I see no call to g_task_run_in_thread() which would actually specify the task function to run, and make it run."
1789922,2018-09-10 17:03:15 UTC,"So I ran it under gdb and set a breakpoint to find how unmount_cb() is being called and traced the problem back up to unuse_data_iterate().  It calls gdu_utils_is_in_use_full(), which incorrectly identifies the mount point of the filesystem as ""/"".  So it looks like either it is finding the wrong mount point for the filesystem and trying to unmount the root ( which you obviously can't do ), or unuse_data_iterate() is actually being called on the root filesystem instead of the one you are trying to resize.  Unfortunately I can't tell which since almost all of the data this code is working with gdb tells me has an incomplete type."
1789922,2018-09-10 17:52:04 UTC,Man this cold must really be messing with my head.  I had the wrong drive selected and actually was trying to resize the root partition.
1789922,2018-09-10 18:17:15 UTC,"Nevermind, it still doesn't work on the right disk.  While the disk is not mounted initially, by the time unuse_data_iterate() is called, it has been mounted for some reason.  I'm thinking there is a race condition where something mounts the fs temporarily and unmounts it, and during the time it is mounted is when unuse_data_iterate() is called, which sees it is mounted, and tries to unmount it, but by the time the unmount request goes through, it has already been unmounted."
1789922,2018-09-10 19:43:00 UTC,"It turns out that just trying to unmount an fs is broken.  Apparently resize mounts the fs first for some reason, then when it tries to unmount, it can't."
1789922,2018-09-11 16:58:38 UTC,Upstream concluded that the bug lies in udisks.  It needs a similar fix to one it got before to wait for the changes to propagate before returning from resize. Unmount needs a similar waiter.
1789926,2018-10-07 15:53:26 UTC,Crash fixed in https://gitlab.com/inkscape/inkscape/commit/e9de1bbc21ec394add5e241f6624573ec436cbfa
1789926,2018-10-07 12:25:50 UTC,"crash is provoked by the <image y=""0"" x=""-nan"" ..."
1789926,2018-08-30 15:20:28 UTC,"- crash confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- crash also reproduced on Inkscape 0.92+devel (d890608, 2018-08-21)"
1789932,2018-09-07 20:23:17 UTC,The puzzling thing about this issue is the fact that MAAS always tries to reload the service when it writes out the config (if I'm reading the code correctly in maasserver/proxyconfig.py).
1789932,2018-09-08 00:37:01 UTC,Let's check if the code in this proposal fixes it:
1789933,2019-07-22 03:52:37 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1789933,2018-08-30 15:49:05 UTC,"StacktraceTop:
 shell_app_dispose (object=0x5654b1c61840) at ../src/shell-app.c:1485
 g_object_unref (_object=0x5654b1c61840) at ../../../../gobject/gobject.c:3309
 g_hash_table_remove_node (hash_table=0x5654a9a39360, i=<optimized out>, notify=<optimized out>) at ../../../../glib/ghash.c:459
 g_hash_table_remove_internal (hash_table=0x5654a9a39360, key=0x5654b1c61840, notify=1) at ../../../../glib/ghash.c:1376
 _shell_app_system_notify_app_state_changed (self=0x5654a977e120, app=app@entry=0x5654b1c61840) at ../src/shell-app-system.c:375"
1789933,2018-08-31 02:27:14 UTC,I can't find any other reports of this crash yet.
1789933,2018-08-31 11:13:10 UTC,"> Please try removing all of them and see if that fixes the problem.
"
1789939,2018-08-30 16:10:04 UTC,This is fixed on master. Thanks for the report.
1789949,2018-09-12 20:01:43 UTC,apport information
1789949,2018-09-12 20:01:42 UTC,apport information
1789949,2018-09-12 20:01:58 UTC,apport information
1789949,2019-04-22 13:40:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789949,2018-09-12 20:02:31 UTC,apport information
1789949,2018-09-12 20:02:29 UTC,apport information
1789949,2018-09-12 20:02:25 UTC,apport information
1789949,2018-09-12 20:02:14 UTC,apport information
1789949,2018-09-12 20:02:09 UTC,apport information
1789949,2018-09-12 20:02:06 UTC,apport information
1789949,2018-09-12 20:02:02 UTC,apport information
1789949,2018-09-12 20:01:59 UTC,apport information
1789949,2018-09-12 20:01:57 UTC,apport information
1789949,2018-09-12 20:01:55 UTC,apport information
1789949,2018-09-12 20:01:52 UTC,apport information
1789949,2018-09-12 20:01:50 UTC,apport information
1789949,2018-09-12 20:01:49 UTC,apport information
1789949,2018-09-12 20:01:47 UTC,apport information
1789949,2018-09-12 20:01:46 UTC,apport information
1789949,2018-09-12 20:01:44 UTC,apport information
1789949,2018-08-31 10:00:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1789949,2018-09-12 20:01:38 UTC,apport information
1789949,2018-09-12 20:01:39 UTC,apport information
1789949,2018-09-12 20:01:41 UTC,apport information
1789949,2018-09-12 20:01:53 UTC,apport information
1789950,2018-09-14 16:39:18 UTC,"This has been happening randomly; yesterday, the speaker worked again."
1789953,2018-08-31 13:20:36 UTC,"The Debian DSO patch is adding a bunch of -l<library> options to the linker command line, and it's doing that *before* existing *.la files in the same command line:"
1789953,2018-08-30 21:17:51 UTC,"This fixes the build on all arches except armhf:
https://code.launchpad.net/~ahasenack/ubuntu/+source/snapper/+git/snapper/+ref/cosmic-ftbfs-1789953"
1789971,2019-07-14 23:17:51 UTC,"I tested in 18.04.2, an upgraded 18.04 from 16.04 and 16.04 and I had the same results. That I said, I must be doing something wrong. Here's what I did:"
1789971,2019-02-28 18:16:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1789971,2019-07-14 11:10:30 UTC,Installing `at-spi2-core` does not help. The problem persists still after the upgrade to 18.04.2.
1789971,2019-09-13 04:17:23 UTC,[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1789971,2019-07-14 01:41:03 UTC,"Is this still a problem in 18.04.2? Do you also find the same issues in other flavors of Ubuntu? There are some suggestions in the link you provided, most notably installing `at-spi2-core`. Did they work to resolve the issue?"
1789982,2018-08-30 21:41:44 UTC,"From our cataloger: ""if you left the price blank [in the XUL client], it just went to ""unset"", in the [Web client] it makes the price 0.00"""
1789982,2018-08-31 13:25:28 UTC,This is also true in Web client 3.0.9
1789982,2018-08-31 14:12:01 UTC,"Thanks for confirming, Beth.  I believe that the behavior that our cataloger was seeing the saves-but-with-$0.00 behavior when applying item templates ported over from the XUL client."
1789982,2018-09-03 01:27:11 UTC,Possibly related issue: https://bugs.launchpad.net/evergreen/+bug/1740527
1789982,2018-10-19 15:12:14 UTC,"This is because of a combination of things, beginning with the fact that the type attribute for these fields is number rather than text. Deposit and acq cost can cause the same issues, even though cost initially appears blank. (If you enter anything into the cost field and then empty it the save will fail for the same reason.) The real fix for this is to just stop using number and make all of these fields text with a validator to only allow entries that look like prices. Branch on the way. Something else that needs to be addressed sometime: there's obviously a part of the save process that assumes nothing can ever fail and blindly charges ahead with closing the window and losing your work."
1789982,2018-10-19 17:16:51 UTC,"To be more clear, the issue with nullable numeric values is that if we don't use something like str-to-float to convert the values between numeric and string values we get empty values on edit, and if we do use these directives we're not able to save an empty value because it's translated to the string ""null"" which causes the insert/update to fail. This branch just tells Angular that the nullable currency fields are just strings. The pattern directive requires that they be either empty, just numbers, or numbers + '.' + 2 more digits. (If there are i18n reasons to allow for more than 2 decimal places, the committer may want to change the patterns to accommodate.)"
1789982,2019-03-11 13:55:40 UTC,"I have tested this code and consent to signing off on it with my name, Elaine Hardy and my email address, <email address hidden>."
1789982,2019-05-24 15:40:41 UTC,"I tested, and while this solves the very specific problem of adding a new copy with empty prices (and costs and deposit amounts), it doesn't go far enough. Specifically, if you add a copy, touch the price field and then clear it in the editing session, or if you edit an existing copy and try to empty the price, saving the results will still fail silently as it tries set the price to the string ""null""."
1790002,2018-08-30 21:29:58 UTC,"I don't believe the problem is with identity-provider: it's honoring the user's request to send things over to an http site (which as you noted, the browser correctly warns about - it is the user's choice to proceed in this case.) So I believe (and I've moved the bug to the appropriate project for that) that paste.ubuntu.com should redirect to https *before* authenticating."
1790010,2018-09-07 10:51:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790010,2018-09-07 12:21:36 UTC,"I'm having almost the same issue, I'm using a custom mouse theme and a custom size and the mouse cursor resets to default theme and size when:
- hovering over desktop
- hovering over a window top bar
- hovering over ""core"" applications like nautilus or settings"
1790010,2018-10-04 02:09:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1700085, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1790010,2018-11-21 06:47:43 UTC,"I believe it's incorrect to mark this bug as a duplicate of bug #1700085.
In fact, in bug #1700085, the user puts a lot of effort to get hidpi scaling and, even if he succeds in that, he is not able to make the cursor scale as well. So, the cursor doesn't scale at all."
1790023,2018-09-02 05:51:40 UTC,Can you try to run with LANG=en_US.UTF-8 temporally?
1790023,2018-09-04 02:09:44 UTC,"On english Centos instance start without error, but Cirros image work without interface.
When try to add interface manually see this:
2018-09-04 04:57:34.121 12568 WARNING nova.network.neutronv2.api [req-078cc9dd-6429-474f-8bb5-913ded1dd841 f868a5047b76448abe8e16e8c248d285 197530af151d40fb89e8743435b2ef6b - default default] [instance: c6106b22-6dee-408d-86a3-820225bbf4f2] 70e78c09-d763-4251-a562-bfd5fc1bfeb3 already exists in list: networks containing: [u'70e78c09-d763-4251-a562-bfd5fc1bfeb3']. ignoring it
2018-09-04 04:57:34.612 12568 ERROR compute_hyperv.nova.vmops [req-19bf38ca-4684-4943-8387-e8ee35dba56c bec61bd30a3b4472bb74b452a7253a83 2b5f5900fb9e4381926dbb8553b6068e - default default] [instance: c6106b22-6dee-408d-86a3-820225bbf4f2] Cannot hot plug vNIC to a first generation VM.
2018-09-04 04:57:34.617 12568 WARNING nova.compute.manager [req-19bf38ca-4684-4943-8387-e8ee35dba56c bec61bd30a3b4472bb74b452a7253a83 2b5f5900fb9e4381926dbb8553b6068e - default default] [instance: c6106b22-6dee-408d-86a3-820225bbf4f2] attach interface failed , try to deallocate port 094e4c32-f87a-4d1a-bdae-1504f9daddc9, reason: Failed to attach network adapter device to c6106b22-6dee-408d-86a3-820225bbf4f2: InterfaceAttachFailed: Failed to attach network adapter device to c6106b22-6dee-408d-86a3-820225bbf4f2
2018-09-04 04:57:35.895 12568 INFO nova.network.neutronv2.api [req-19bf38ca-4684-4943-8387-e8ee35dba56c bec61bd30a3b4472bb74b452a7253a83 2b5f5900fb9e4381926dbb8553b6068e - default default] [instance: c6106b22-6dee-408d-86a3-820225bbf4f2] Port 094e4c32-f87a-4d1a-bdae-1504f9daddc9 from network info_cache is no longer associated with instance in Neutron. Removing from network info_cache.
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server [req-19bf38ca-4684-4943-8387-e8ee35dba56c bec61bd30a3b4472bb74b452a7253a83 2b5f5900fb9e4381926dbb8553b6068e - default default] Exception during message handling: InterfaceAttachFailed: Failed to attach network adapter device to c6106b22-6dee-408d-86a3-820225bbf4f2
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server   File ""C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\oslo_messaging\rpc\server.py"", line 163, in _process_incoming
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server     res = self.dispatcher.dispatch(message)
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server   File ""C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\oslo_messaging\rpc\dispatcher.py"", line 220, in dispatch
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server     return self._do_dispatch(endpoint, method, ctxt, args)
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server   File ""C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\oslo_messaging\rpc\dispatcher.py"", line 190, in _do_dispatch
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server     result = func(ctxt, **new_args)
2018-09-04 04:57:36.019 12568 ERROR oslo_messaging.rpc.server   File ""C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Pyt..."
1790023,2018-08-31 15:04:44 UTC,"Hi!
Neutron server log is clear. Hyper-V and CentOS controller node - russian lang OS."
1790023,2018-08-31 14:05:57 UTC,Hi.
1790038,2018-09-02 08:15:23 UTC,Can you please provide the neutron log?
1790038,2018-09-04 11:42:26 UTC,"The ""BadRequestException: Unknown error"" error is a generic one as neutron-server rejects the request (proper error is displayed in Rocky, you may have more info with debug enabled)."
1790038,2018-09-04 15:51:40 UTC,"For reference, fix to get actual error is https://review.openstack.org/#/c/571101/ (Rocky and newer)"
1790043,2018-09-05 05:22:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/599915"
1790043,2019-05-24 04:28:05 UTC,"Change abandoned by Tony Breeds (<email address hidden>) on branch: master
Review: https://review.opendev.org/599915
Reason: There isn't a good fix for this.  The right thing is for the ceph container to be built on ppc64le but currently there aren't builders available for that :("
1790043,2021-02-17 17:09:17 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1790046,2019-05-30 06:58:12 UTC,led/microphone-mute not in https://git.launchpad.net/plainbox-provider-checkbox/commit/?id=7999ea12bd71075f5d57075c543d43ad2abcd869
1790046,2019-05-30 13:38:39 UTC,@Betty please see the explanation on the MR and the linked bug:
1790055,2018-09-04 15:43:52 UTC,Thanks for the feedback; this sounds like it could be a valuable enhancement to MAAS. We should discuss separately from this bug if it can be put on the roadmap.
1790055,2018-09-04 16:11:36 UTC,"Hi Trent,"
1790055,2018-09-04 17:34:15 UTC,"When I read ""hardware-assisted software raid"" I understood that it would actually improve performance, but talking to others, I understood that this is a metadata-only assistance. If that's the case, why would you want to do this? Wouldn't it be better to have the metadata on-disk instead of in the BIOS, in case you need to swap out the motherboard? In other words, the disks would be usable on any machine that supports `mdadm` if the metadata is on-disk and not managed by a [Fake]RAID controller."
1790055,2018-09-05 01:09:13 UTC,"The metadata is in fact stored on the disks, though in a different format to that of mdadm traditionally. The BIOS assists in letting you setup that metadata from the BIOS, though, you can also write to it with mdadm (you can do either)."
1790055,2018-09-05 19:12:12 UTC,Thanks for the clarification on the reasons for this requirement. Sounds like this would be nice-to-have.
1790055,2019-09-19 12:06:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1790055,2020-08-31 20:01:22 UTC,"It would be interesting, I'll try to ""borrow"" a VROC-enabled server for some days. I think it will be not too hard to add this to curtin. I'll have questions about the preferred method how to present this to the user, e.g. maybe an external_metadata: xxxx, where xxxx could be imsm for now could execute this 2 stage raid array creation.
About the MaaS part: I would leave it to MaaS developers, I'm not sure what should be done there. I think it will need a detection method in the commissioning phase at least."
1790055,2020-08-31 20:03:18 UTC,"Added the comment to the wrong report, sorry..."
1790076,2018-09-03 22:29:53 UTC,This is one of those bugs that needs to be fixed in the apiserver code.
1790076,2018-11-03 04:17:43 UTC,[Expired for juju because there has been no activity for 60 days.]
1790076,2019-04-01 11:57:23 UTC,"happened again
http://ci.jujucharms.com/job/make-check-juju/4064/testReport/junit/github/com_juju_juju_api_watcher/TestAll/"
1790076,2019-06-01 04:17:31 UTC,[Expired for juju because there has been no activity for 60 days.]
1790095,2019-09-16 13:55:51 UTC,Migrated to https://github.com/widelands/widelands/issues/2114
1790096,2018-09-05 13:23:50 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1790096,2018-08-31 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790096,2018-08-31 10:04:47 UTC,apport report
1790096,2018-09-05 14:00:35 UTC,"-34 tested a few minutes ago. Same problem.
I'm back with -32 for now."
1790096,2018-09-11 14:29:38 UTC,"Looking a the code, igb driver is untouched between -32 and -34.
looking network, timekeeping and x86 timer code is needed."
1790096,2018-09-13 20:44:54 UTC,I built a 4.15.0-35 test kernel.
1790096,2018-09-14 13:30:59 UTC,"Le 13/09/2018 à 22:44, Joseph Salisbury a écrit :

> I built a 4.15.0-35 test kernel.
>
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1792100
>
> Can you test this kernel and see if it resolves this bug?
>
> Note about installing test kernels:
> • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages.
> • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
>
> Thanks in advance!
>


Yes pblm fixed !
Do you have a precise idea of the source of the bug ?"
1790096,2018-09-17 09:32:39 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.compo/Testing/EnableProposed for documentation how to enable and use -proposed."
1790096,2018-09-17 12:39:52 UTC,"Hello,
Yes, bug fixed in the latest -proposed kernel."
1790098,2020-02-11 10:00:59 UTC,"------- Comment From <email address hidden> 2020-02-11 04:54 EDT-------
IBM Bugzilla status -> closed, Fix Released with bionic"
1790098,2018-08-31 17:06:20 UTC,"This output shows that you are using nmcli to manage network connections.  Network-manager is not part of the Ubuntu Server platform, it is not included in the images Ubuntu provides for s390x, and it is not the recommended tool for configuring vlans and bonds in Ubuntu."
1790098,2018-09-07 09:49:18 UTC,"------- Comment From <email address hidden> 2018-09-07 05:39 EDT-------
I agree that we need to switch to netplan, but that is currently not feasible approach for us.
We will keep you updated once we have anything concrete on it."
1790098,2018-09-07 22:16:22 UTC,The description for reproducing this says:
1790098,2018-09-08 00:20:57 UTC,Here is an example netplan yaml that emulates this configuration in a test container.
1790098,2018-09-08 00:33:04 UTC,"Note that the above test was with Ubuntu 18.04 on x86.  With a preliminary test of Ubuntu 18.10 on s390x, the eth0 interface fails to configure at all.  I will investigate further on Monday."
1790098,2018-09-08 06:04:31 UTC,"sorry, that was with Ubuntu 18.10 host kernel by mistake."
1790098,2018-09-08 06:20:11 UTC,"# uname -a
Linux rare-stork 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux
# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
3: bond0.100@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 10.132.106.86/24 brd 10.132.106.255 scope global bond0.100
       valid_lft forever preferred_lft forever
# ip link set dev bond0 down
# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
# ip link set dev bond0 up
# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
3: bond0.100@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 10.132.106.86/24 brd 10.132.106.255 scope global bond0.100
       valid_lft forever preferred_lft forever
#"
1790098,2018-09-11 00:16:20 UTC,"On Mon, Sep 10, 2018 at 09:19:41AM -0000, bugproxy wrote:

> So either i suspect one of the two issues here
"
1790098,2018-09-12 09:09:46 UTC,"------- Comment From <email address hidden> 2018-09-12 05:05 EDT-------
Vorlon,"
1790098,2018-12-18 16:33:35 UTC,The issue looks like it could be what is fixed by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680 (the change is included in 1.10.8 which is currently not yet in bionic but being SRUed)
1790098,2019-06-17 14:16:36 UTC,"Since our focus is on netplan only, I'm changing the status to Won't Fix."
1790098,2019-06-19 07:49:29 UTC,"------- Comment From <email address hidden> 2019-06-19 03:47 EDT-------
IBM Bugzilla status -> closed, Will not be fixed by Canonical"
1790098,2019-10-25 10:34:14 UTC,"Hello bugproxy, or anyone else affected,"
1790098,2019-10-25 12:24:41 UTC,"All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1790098,2019-10-29 08:09:37 UTC,"------- Comment From <email address hidden> 2019-10-29 03:59 EDT-------
Tested below scenario:"
1790098,2019-11-04 14:07:48 UTC,This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.2
1790098,2019-11-04 14:08:05 UTC,"The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1790098,2018-09-08 06:03:50 UTC,Test repeated on an Ubuntu 18.04 s390x container (Ubuntu 18.04 host):
1790098,2018-09-10 09:19:41 UTC,"------- Comment From <email address hidden> 2018-09-10 05:16 EDT-------
Vorlon,"
1790099,2018-09-11 21:07:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790100,2018-11-09 12:24:24 UTC,"@Egmont: thank you for your input. I just added ""gnome-terminal"" package in Ubuntu. I hope it is alright for you."
1790100,2018-11-16 21:01:45 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-10-25 (387 days ago)
InstallationMedia: Ubuntu 17.10 ""Artful Aardvark"" - Release amd64 (20171018)
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Tags:  bionic wayland-session
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-10-13 (34 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True"
1790100,2018-11-05 23:13:19 UTC,"I still have the problem in gnome terminal, it didn't go away..."
1790100,2018-11-06 09:05:24 UTC,"@giannione: may you create a new bug report? I guess you don't have the same configuration as me, maybe not the same bug then."
1790100,2018-11-07 21:41:00 UTC,"synaptic works
remmina works"
1790100,2018-11-07 21:41:52 UTC,gedit works
1790100,2018-11-09 09:13:20 UTC,"@giannione: that's interesting, that maybe means that the bug is not in vte2.91. May you give this information to gnome-terminal devs?"
1790100,2018-11-09 09:57:30 UTC,They don't want to hear about it and say that it's Ubuntu's fault....
1790100,2018-11-09 10:23:43 UTC,Please understand: It's not that we (vte and gnome-terminal developers) don't want to hear about it. We've heard about it and we are pretty certain that this is a bug somewhere elsewhere. Vte's and gnome-terminal's source code has absolutely no sign of treating ^ or any other similar simple character specially.
1790100,2018-11-04 15:42:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790100,2018-11-16 21:01:46 UTC,apport information
1790100,2018-11-16 21:01:47 UTC,apport information
1790100,2018-11-16 21:01:48 UTC,apport information
1790100,2018-11-16 21:03:27 UTC,"hello, I run that command
""ubuntu-bug -u 1790100"""
1790100,2018-11-16 21:04:24 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-10-25 (387 days ago)
InstallationMedia: Ubuntu 17.10 ""Artful Aardvark"" - Release amd64 (20171018)
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Tags:  bionic wayland-session
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-10-13 (34 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True"
1790100,2018-11-16 21:04:25 UTC,apport information
1790100,2018-11-16 21:04:27 UTC,apport information
1790100,2019-05-11 08:30:13 UTC,"still can't type ^
... :-("
1790100,2018-11-04 15:47:14 UTC,"gnome says that it's not their problem
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/48"
1790100,2018-11-04 15:45:26 UTC,I have the same problem on ubuntu 18.10 on gnome terminal (the problem appeared after upgrading from an 17.04ubuntu).
1790100,2018-11-05 15:35:10 UTC,"@giannione: as it is fixed for me, I propose to close this bug report. Feel free to re-open it or a new one if you have this bug again after a restart of your session."
1790100,2018-11-05 15:32:27 UTC,"> gnome says that it's not their problem
"
1790108,2018-09-03 15:14:17 UTC,"Depending on the selected user session type, the logout problem also occurs with pam_kwallet.so and pam_gnome_keyring.so (strange, how can the user session type affect what the pam modules and/or lightdm do). Maybe this is not a bug in the pam modules, but in lightdm?"
1790108,2018-09-04 15:21:16 UTC,"Well, somehow today I had different results from yesterday: All user session types had the same result and only pam_kwallet.so and pam_kwallet5.so caused problems. I guess that yesterday I mixed up several things when trying different lightdm versions and different pam configurations."
1790110,2019-04-30 09:03:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790110,2020-07-29 09:54:57 UTC,Same problem on Ubuntu 18.04.  Xscreen ignores Caffeine
1790110,2018-09-03 05:44:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790110,2019-01-16 10:48:24 UTC,"tested both on Xorg & Wayland, bug persists"
1790110,2018-09-03 04:59:33 UTC,"I have a same experience with ESPN from Firefox playing the video (in full screen) of Miami-LSU football game. Screensaver came on once too many times. It shouldn't be happening as it's 18.04 version! It felt like some developer took out the ""fix"" code out."
1790110,2019-02-04 11:13:45 UTC,"just tested & have this issue in 19.04 (LXQt desktop & vlc)
in `vlc` i had 'disable screensaver' ticked, but xscreensaver still hid vlc (both when vlc was playing in a window, or was fullscreen)"
1790110,2019-11-26 17:54:33 UTC,still affected in 20.04 development branch @ 26/11/2019
1790114,2018-08-31 09:56:19 UTC,"Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> search_opts.get(""vm_state"") == ['deleted']
Traceback (most recent call last):
  File ""<stdin>"", line 1, in <module>
NameError: name 'search_opts' is not defined
>>> search_opts = {'vm_state': 'deleted'}
>>> search_opts.get(""vm_state"") == ['deleted']
False

>>>
"
1790114,2018-08-31 10:00:17 UTC,"seems we both allow vm_state from REST API layer and internally we might transfer it to a dict
so it's a little bit weird ,need dig more"
1790114,2018-09-04 03:49:31 UTC,"jichen@kolla:~$ env | grep OS_
OS_REGION_NAME=RegionOne
OS_AUTH_PLUGIN=password
OS_USER_DOMAIN_NAME=Default
OS_PROJECT_NAME=demo
OS_IDENTITY_API_VERSION=3
OS_PASSWORD=demo2
OS_USERNAME=demo2
OS_TENANT_NAME=demo"
1790114,2018-09-04 04:17:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599492"
1790114,2019-10-07 13:48:15 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/599492"
1790114,2020-01-14 15:46:24 UTC,"Looks like you found a potentially issue and are digging into it (thanks!), but for this to be a valid bug report, it would be very helpful to follow the template of ""I did X, I expected Y, instead I got Z"", with details of the steps you did, what was the expected behaviour, and what you actually saw for X, Y and Z."
1790114,2020-03-15 04:17:29 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1790134,2018-08-31 13:31:30 UTC,"Here’s the icon in the layout code:
<https://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/view/head:/data/gtkbuilder/UpdateManager.ui#L182>"
1790134,2019-05-30 15:17:43 UTC,"The problem is fixed in Cosmic/Disco/Eoan, probably because yaru provides an icon with the correct geometry, it might still be a problem with other themes though."
1790134,2019-09-25 03:52:43 UTC,This bug was fixed in the package update-manager - 1:19.04.8
1790135,2018-09-03 02:34:48 UTC,That's a kernel error so reassigning...
1790135,2018-09-03 03:00:07 UTC,This change was made by a bot.
1790135,2018-09-05 14:18:18 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1790150,2018-10-04 10:18:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790151,2021-01-27 10:49:34 UTC,I think I'm seeing this as well.
1790151,2018-09-07 08:49:55 UTC,There are a few things that might be at play here.
1790153,2019-10-09 10:11:08 UTC,"Thanks for reporting this, and sorry for the delay in getting back to you."
1790167,2018-09-03 08:36:05 UTC,"Random results (we are speaking of ""yade -j1"" right?) usually come from using null pointers or uninitialized variables.
Running yade with valgrind (and debug symbols) would probably tell more.
In the case neverErase=true, I would double-check what happens if the interaction becomes active again.
Bruno"
1790167,2018-08-31 19:33:11 UTC,"«neverErase» is only ok if another functor is taking care of erasing. It
doesn't seem to be the case here, so it should just be «false».
Bruno"
1790167,2018-09-01 07:50:08 UTC,OK... We need neverErase=True for DFNFlow so what should we do? Create a functor to erase the interactions?
1790167,2018-09-03 08:52:44 UTC,"Hi guys,"
1790167,2018-09-03 19:13:02 UTC,">>
I always get the same curve when running the simulation with the same packing (with either neverErase=True or neverErase=False). I don't face the problem you mentioned Robert...
>>
"
1790167,2018-09-05 10:29:01 UTC,"> OK... We need neverErase=True for DFNFlow so what should we do? Create a functor to erase the interactions?
"
1790167,2018-09-05 12:24:28 UTC,"""Also, my curves do not match yours exactly (they are close though), why?"""
1790167,2018-09-05 14:45:52 UTC,">Can we have 2 interactions (in the interaction container"") which concerns the same particles pair?
"
1790167,2019-02-05 19:56:29 UTC,moved from https://bugs.launchpad.net/yade/+bug/1790167 to https://gitlab.com/yade-dev/trunk/issues/43
1790167,2018-09-01 11:05:48 UTC,"> I noticed that running the exact same simulation (with same initial packing) gives different behaviors
"
1790167,2018-09-02 08:49:19 UTC,"I am also curious as to why we see changes in these curves between replicates (even for neverErase=False), despite our use of a constant sphere packing..."
1790169,2018-09-07 20:07:15 UTC,I tested this extensively in 3.1.5 with spot checks in 3.1.4 and 3.0.9.
1790169,2018-09-07 21:16:05 UTC,Patch that addresses the saving of the sort priority in 3.1.x is available here: collab/gmcharlt/lp1790169_eggrid_column_sort_wip. The branch remains WIP since the sort settings are not honored.
1790169,2018-09-12 13:18:02 UTC,Some more information about this in comments #3-#5 of bug 996744 (which I've marked duplicate)
1790169,2018-12-03 20:53:59 UTC,"We see this behavior in SCLENDS, and I will just add a little heat with this example of why sort is useful (from a reference librarian):"
1790169,2019-05-01 15:43:01 UTC,Equinox is looking at this as part of a consultation for PaILS.
1790169,2019-07-30 14:46:13 UTC,"I've confirmed that the eg2 grid seems to need the same fixes.  It looks like Galen already fixed the saving issue in eg2, so it only needs the equivalent of Jason's compileSort fix."
1790169,2019-07-30 15:46:27 UTC,"And I've tested the AngularJS portions of this patch, and they work as described.  Here's my signoff branch:"
1790169,2019-09-01 13:11:46 UTC,"Pushed to master, rel_3_3, and rel_3_2.  Thanks, Galen, Jason, and Remington!"
1790169,2019-09-18 13:24:05 UTC,"Since this bug is committed and partially released, I have opened #1844532 as a follow-up to address the eg2 problems Remington identified in comment #8."
1790169,2019-10-18 22:14:04 UTC,The fix for this bug may be the cause of bug 1846038.
1790169,2019-06-27 22:20:54 UTC,"So what I'm seeing (with Galen's patch in place), is that the Sort Priority only takes effect upon page load or if Manage Column Width is invoked."
1790169,2019-05-01 15:24:37 UTC,"In CW MARS, this problem is most apparent when viewing the Holds Pull List. Some of our libraries use the ""Print Full Grid"" option since it has access to more columns, (like Pickup Library), than the print template does."
1790181,2018-08-31 17:18:13 UTC,apport information
1790181,2018-08-31 17:18:24 UTC,apport information
1790181,2018-11-12 17:56:26 UTC,Here is my patch for munin diskstats:
1790181,2018-11-12 06:23:29 UTC,iostat is showing the same thing btw.
1790181,2018-11-12 05:40:20 UTC,https://www.redhat.com/archives/dm-devel/2015-June/msg00042.html
1790181,2018-11-12 05:35:13 UTC,drivers/md/dm-stats.c:
1790181,2018-11-12 04:39:43 UTC,"It looks like partitions are being reported correctly, just not the main device"
1790181,2018-09-18 21:02:48 UTC,"On my laptop with a SATA ssd I also have higher reported times than process real time, albeit not by such a huge margin. Only a factor of 2-4 too high."
1790181,2018-09-18 20:55:31 UTC,Testing with http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2/ shows:
1790181,2018-09-05 16:23:38 UTC,I noticed the bug only after I installed munin recently. I don't know how long it may have existed before.
1790181,2018-09-05 14:25:59 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1790181,2018-08-31 17:18:22 UTC,apport information
1790181,2018-08-31 17:18:21 UTC,apport information
1790181,2018-11-13 23:18:41 UTC,https://forums.fedoraforum.org/showthread.php?318580-iostat-svctm-and-busy-numbers-are-wrong-for-NVME-drives
1790181,2018-08-31 17:18:19 UTC,apport information
1790181,2018-08-31 17:18:16 UTC,apport information
1790181,2018-08-31 17:18:15 UTC,apport information
1790181,2018-08-31 17:18:14 UTC,apport information
1790181,2018-08-31 17:18:11 UTC,apport information
1790181,2018-08-31 17:18:10 UTC,apport information
1790181,2018-08-31 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790181,2018-08-31 17:18:17 UTC,apport information
1790181,2019-01-03 17:02:57 UTC,"After rebooting, the values are < 2^31 and utilization is reporting fine. I feel this is a 31/32 bit overflow issue."
1790185,2020-04-14 08:36:06 UTC,"I think the original bug here is resolved - the vsphere provider supports the zones constraint, and that can be used to specify a particular cluster or any resource pool inside the cluster."
1790185,2018-12-18 23:52:28 UTC,Hi - can you explain how you would want Juju to behave?
1790185,2018-12-19 07:00:12 UTC,"Hi Christian,"
1790185,2020-04-13 22:31:27 UTC,"Is there any update on this feature? This impacts every deployment on VMWare. Being able to point to a cluster/resource pool with the ""zone"" is essential."
1790185,2020-04-13 22:37:16 UTC,#cpe-onsite
1790188,2018-10-01 17:15:35 UTC,This bug was fixed in the package linux - 4.15.0-36.39
1790198,2018-09-10 20:48:49 UTC,Still taking too long
1790200,2018-09-02 03:11:25 UTC,I'm reopening the bug because it doesn't do us much good if rollup still isn't usable. :(
1790200,2018-09-02 03:10:45 UTC,"Ok, now I get https://bugs.debian.org/892133 when I try to rebuild rollup."
1790200,2018-09-02 02:25:25 UTC,This bug was fixed in the package node-rollup - 0.50.0-1build1
1790200,2018-09-02 07:26:28 UTC,"On 09/02/2018 05:11 AM, Jeremy Bicha wrote:

> I'm reopening the bug because it doesn't do us much good if rollup still
> isn't usable. :(
>


Thanks Jeremy. I didn't see this problem with my build. I will look into
it further during the week."
1790200,2018-09-01 23:25:56 UTC,"Uploaded. I used a ""build1"" number since I consider this to be temporary and we want the next Debian update to auto-sync here. I will probably do a ""build2"" to revert to the distro packaging anyway once this version is accepted from the NEW queue and published."
1790202,2020-12-07 15:53:31 UTC,"On Fri, Dec 04, 2020 at 11:36:05PM -0000, Hayden Barnes wrote:

> /usr/lib/ubuntu-release-upgrader/check-new-release appears to lack any
> architecture-awareness.
"
1790202,2020-12-04 23:36:05 UTC,/usr/lib/ubuntu-release-upgrader/check-new-release appears to lack any architecture-awareness.
1790202,2018-09-18 20:48:06 UTC,"I'll have to say ""goodbye"" to ubuntu and debian and ""Hello, cent os"""
1790202,2018-09-18 12:09:34 UTC,"Big-endian PowerPC support was dropped after 16.10. There is no upgrade path from 16.04.5, however it will be supported for another ~3 years."
1790202,2018-09-07 16:59:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790203,2018-08-31 21:30:51 UTC,Better patch with correct some bugs
1790203,2018-08-31 19:26:13 UTC,File picture_frames_4.py
1790203,2018-08-31 19:24:23 UTC,file picture_frames_4.xml
1790203,2018-09-01 09:31:05 UTC,I think is the last patch :-)
1790204,2018-12-20 23:29:46 UTC,"Looking back over the history on this, it's my fault it looks like:"
1790204,2018-12-20 23:47:46 UTC,"Also, the hack idea I had in comment 1:"
1790204,2018-12-20 23:54:29 UTC,"Another idea is simply don't keep any allocations on the migration record if we know we're doing same host resize, leave the max allocations on the instance record. That would have implications for how the allocations are cleaned up on revert or failure in the same host resize case, and older computes wouldn't have that logic..."
1790204,2018-12-21 15:08:11 UTC,Another tricky thing to keep in mind is the new flavor is used to update the instance.vcpus and instance.memory_mb values:
1790204,2018-12-21 17:13:14 UTC,"I was starting to hack up a solution where conductor would detect the possibility of doing a same-host resize and *not* swap the source node old_flavor allocations to the migration record, which I thought would then get us to the point where the scheduler calls the _move_operation_alloc_request method during claim_resources. However, we don't even get that far because the GET /allocation_candidates request to placement filters out the only host (in this case the provider has DISK_GB=1028 and that's also what is currently allocated to the server with the old_flavor, and even though the new_flavor disk size doesn't change, the scheduler is requesting 1028 more)."
1790204,2019-01-03 07:54:00 UTC,"Reviewed:  https://review.openstack.org/619123
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0ce581369838dbe6909bdd8847aefac2aff1177e
Submitter: Zuul
Branch:    master"
1790204,2019-01-26 23:14:18 UTC,"@Jay, that's not a bad idea. While working through the various scenarios, possible solutions and issues with them, I thought about something like that as well, but for whatever reason figured that would be too big of a change since historically same-host resize has been pushed off as a test-only thing and not something people should be using in production, but clearly there are production cases for it as noted (resize to same host for affinity server groups and edge scenarios)."
1790204,2019-10-29 15:40:30 UTC,"Per comment 12, this is a latent issue and a duplicate of bug 1609193 which goes back to at least Newton but I'm sure was always an issue for resize on the same host."
1790204,2019-02-18 15:32:04 UTC,"For my own notes, I was wondering how the ResourceTracker claims code in the nova-compute service handles a same-host resize (before placement) and this is the code that calculates the usage for same-host resize during the resize_claim on the host:"
1790204,2019-02-22 16:21:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638700"
1790204,2019-02-22 16:44:53 UTC,Another issue with the approach in comment 9 is that we need to get alternative hosts from the scheduler in case the resize to the same host fails (assuming there would be alternative hosts).
1790204,2019-02-22 20:42:34 UTC,"Oh another thing, the new flavor could have new required traits which might not fit with the current host, so bypassing GET /allocation_candidates could mean we resize to the same host and violate the required traits on the new flavor..."
1790204,2019-02-22 23:44:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638791"
1790204,2019-08-20 21:35:13 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/645954
Reason: I'm not actively working on this. There are ideas in here and comments along with https://review.opendev.org/#/c/638791/ which could probably be formed into a solution."
1790204,2019-01-02 15:01:25 UTC,Why don't we just change the whole resize logic to always try resizing to the same host first (without ever touching the scheduler) and then only call the scheduler if the resize-on-same-host failed?
1790204,2018-11-21 00:07:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619123"
1790204,2019-02-24 00:27:05 UTC,"Reviewed:  https://review.openstack.org/638700
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4363b10f5b9eaa7be2df36a94b6bbad5f4674c57
Submitter: Zuul
Branch:    master"
1790204,2018-08-31 20:13:05 UTC,"One hacky way we could handle this is in conductor, after we've moved the instance allocations for the old_flavor to the migration record, if the selected host is the same host the instance is already one, we just fix the allocations so they are the max of the two flavors - but we'd need to sort out if we still use 2 consumers or only 1 - it might make sense to only have the instance consumer for the same-host resize case, but there is logic in the nova-compute service since queens that expects the source node allocations to be tracked by the migration record consumer, so those would have to be audited so they don't blow up now depending on what conductor does."
1790204,2019-03-22 22:49:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645954"
1790204,2019-08-20 21:35:22 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/638791
Reason: I'm not actively working on this. There are ideas in here and comments along with https://review.opendev.org/#/c/645954/ which could probably be formed into a solution."
1790204,2018-11-19 09:40:07 UTC,"Same host migration is important in another case:
Big VM with large root disk (1000GB or more, 50% or more of the total available disk) can't be resized to the same host, leading to the unnecessary cold migration of a large amount of disk data to another host, even if we increase only memory/vcpu count for this instance."
1790205,2018-10-06 13:55:24 UTC,"Same problem, I find myself 4.4GB of occupied space"
1790205,2018-10-06 15:13:37 UTC,"A month before the release of 18.04, a change was released to make systemd journals persistent, but the setting SystemMaxUse was left unset in /etc/systemd/journald.conf"
1790205,2019-01-07 13:41:38 UTC,"$ journalctl --list-boots 2>/dev/null | head -n1 && journalctl --disk-usage 2>/dev/null
-37 64975ef449c34cdc828feb0197d7a2f5 Mon 2018-09-10 02:00:47 CEST—Mon 2018-09-10 08:05:57 CEST
Archived and active journals take up 1.8G in the file system."
1790205,2019-03-21 15:36:44 UTC,I disagree with the title and description of the bug report.
1790205,2019-03-21 17:26:03 UTC,Not breached here:
1790205,2019-03-21 17:38:47 UTC,"So I wasn't aware of this size hard limit on persistent storage - I just noticed that it is 'already' allocating 1.8GB, but this is indeed less than the 10% of the file system the man page says it will consume. So from my personal point of view this is a non-issue then (ideally Benjamin will also provide feedback, though) - but the new behavior may be worth discussing in release notes."
1790205,2019-03-22 00:04:34 UTC,I have filed the usability issue of --disk-usage upstream at https://github.com/systemd/systemd/issues/12063
1790205,2020-07-16 23:13:16 UTC,"For reference, another example : https://discourse.ubuntubudgie.org/t/journalctl-takes-much-storage-has-no-config/3927"
1790205,2020-07-17 05:53:34 UTC,"Same issue on Bionic, installed May 15 (2 months ago):"
1790205,2020-07-17 12:31:14 UTC,"So, as has been previously stated here, and as is documented in section 5 of the journald.conf man page (install man-db, run 'man 5 journald.conf'), journald will, by default, limit the journals' disk allocation to either a maximum of 10% of available disk space, or to the absolute size of 4GB, whichever is lower."
1790205,2020-08-19 02:19:23 UTC,"disk space is cheap → this becomes an infuriating answer. Is cheap where ? For who ?
Whatever price it is, one might want to use it for something else than log ( on a desktop pc )."
1790205,2019-03-21 21:36:05 UTC,Everything ok for me too
1790205,2018-10-06 13:51:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790206,2018-08-31 20:32:00 UTC,It appears to only happen if you're running under screen. switching to tmux doesn't have TERMCAP set
1790219,2018-09-07 09:17:56 UTC,"@Carla, On that machine, did you ever successfully install other version of Nvidia proprietary driver with Ubuntu ? If yes, can you provide the version of ubuntu and Nvidia driver ?"
1790219,2018-09-03 08:11:49 UTC,Thanks for your report.
1790219,2018-09-03 19:15:48 UTC,"Hello Jean-Baptiste,
I am attaching the three boots I have detected with journalctl --list-boots."
1790219,2018-09-07 16:08:49 UTC,"@Yuan-Chen, no I have not installed other versions of Nvidia proprietary drivers with Ubuntu on this PC.
If you want I can try to install on a partition of my hard drive previous versions of Nvidia drivers on Ubuntu 18.10 (now I have a partition with Ubuntu 18.10 newly installed). If needed I can install another version on Ubuntu and Nvidia drivers.
I had installed Nvidia drivers just for a call for testing as I had the graphic card."
1790219,2018-10-21 15:24:56 UTC,I have had some freezing issues at login when enabling nvidia drivers on Ubuntu 18.04 with a custom driver config. It ended up being that nouveau was never successfully blacklisted due to this: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1784598 .
1790221,2018-10-03 01:09:22 UTC,"Reviewed:  https://review.openstack.org/606086
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b3060a9d3103fb8ade6ebeaa53cb4dd39308f8af
Submitter: Zuul
Branch:    stable/rocky"
1790221,2018-09-28 18:12:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/606155"
1790221,2018-09-28 18:26:11 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/606161"
1790221,2018-08-31 22:20:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599087"
1790221,2018-10-08 20:53:20 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1790221,2019-02-09 03:01:01 UTC,"Reviewed:  https://review.openstack.org/606155
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=437211bf37aacb6bc9490e2443984a4428c70779
Submitter: Zuul
Branch:    stable/queens"
1790221,2019-03-24 23:04:50 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1790221,2018-09-28 14:01:08 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/606086"
1790221,2019-03-26 06:19:17 UTC,"Reviewed:  https://review.openstack.org/606161
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=de7e5ae4e4786d3275e2ada688032a4a1cbc055a
Submitter: Zuul
Branch:    stable/pike"
1790221,2019-04-26 17:16:34 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1790221,2018-08-31 21:28:29 UTC,The easy fix is to null out the instance.availability_zone here:
1790221,2019-03-22 03:47:17 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1790221,2018-09-28 08:24:35 UTC,"Reviewed:  https://review.openstack.org/599087
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=771b9eaa71742b7a158c2e7759a3046ea5a6fc3a
Submitter: Zuul
Branch:    master"
1790226,2018-09-02 21:50:47 UTC,That is indeed very weird.
1790230,2018-09-18 21:13:25 UTC,"Review in progress for https://review.opencontrail.org/46292
Submitter: Nagendra Prasath (<email address hidden>)"
1790230,2018-09-21 00:08:09 UTC,"Reviewed:  https://review.opencontrail.org/46292
Committed: http://github.com/Juniper/contrail-provisioning/commit/27b38b16d3d6388de8adeb66e3dc6604373fe7e4
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1790231,2018-09-11 18:33:31 UTC,"Working branch user/jeffdavis/lp1790231-subject-heading-link-exact-match-search adds ""contains=>'exact'"" to the query params for subject heading links, forcing an exact-match search when a heading is clicked."
1790231,2018-09-12 20:30:36 UTC,"I tested using Jeff's strategy and lots more musical terms in the test database.  The patch works perfectly.  The number of records associated with a subject heading in the facets from a top level search, seemed to coincide with the number of records that you pulled up from clicking on a subject link in a record."
1790231,2019-05-10 17:41:14 UTC,"Thanks for this patch, Jeff, and for the testing, Garry.  The only problem I see is with the genre heading links.  Those are in a slightly different format (they're written as facets), which don't need and don't play well with contains=>'exact'.  With your patch applied, clicking on any genre heading link returns 0 results.  I'm adding the needsrepatch tag for this reason."
1790231,2019-05-15 18:55:25 UTC,"I've pushed two additional commits to working branch user/jeffdavis/lp1790231-subject-heading-link-exact-match-search.  The first new commit accommodates genre and other facet-based subjects where we don't want exact match.  The second new commmit applies the fix when display fields are not in use, e.g. when you access the record directly without search terms.  All three commits should probably be squashed before merging to master."
1790231,2019-07-23 19:51:30 UTC,"Thanks for this patch and the testing all, however this doesn't seem to be working as expected after rebasing to current master."
1790232,2018-08-31 23:25:55 UTC,"StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f39db3f8c40 <main_arena>) at malloc.c:4456
 _int_malloc (av=av@entry=0x7f39db3f8c40 <main_arena>, bytes=bytes@entry=3340) at malloc.c:3703
 __GI___libc_malloc (bytes=3340) at malloc.c:3065
 read_packet (c=0x55d253560a30) at ../../src/xcb_in.c:259
 _xcb_in_read (c=c@entry=0x55d253560a30) at ../../src/xcb_in.c:1018"
1790235,2018-08-31 23:45:12 UTC,"I unpinned these, and installed the upgrades which broke them.
I was able to get past the problem by this post:
https://askubuntu.com/questions/873565/broken-libperl5-package-when-trying-to-install-updates/993620"
1790235,2018-08-31 23:45:37 UTC,Now my upgrade-dist is not failing at the calculation.
1790235,2018-08-31 23:20:20 UTC,I have libperl5.22 and libperl5.22:I368 pinned at 5.22.1-9ubuntu0.3 because updates broke them.
1790236,2018-11-01 16:52:22 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1790242,2019-01-22 13:34:10 UTC,"Thank you for your bug report, that's probably an upstream bug and should be reported to them on https://gitlab.freedesktop.org/cairo/cairo"
1790244,2018-09-03 03:00:15 UTC,This change was made by a bot.
1790244,2018-09-03 02:41:04 UTC,Can you please take a photo or video of the problem and attach it here?
1790244,2018-09-03 02:41:33 UTC,"Also, please make sure each separate issue has a separate bug report."
1790251,2020-07-03 01:45:24 UTC,16.04 Xenial is still in the maintenance phase (see https://ubuntu.com/about/release-cycle) so that fix ought to be back-ported.
1790251,2018-09-02 01:38:04 UTC,"I am the one supporting the Martha so, yes, this bug affects me."
1790251,2020-07-29 08:42:01 UTC,It is now close to two (2) years and nobody seems to care.
1790251,2018-09-01 01:37:31 UTC,maybe connected to #1790249?
1790251,2020-08-01 02:59:09 UTC,thank you Sebastien for being a kind person
1790251,2018-09-02 01:36:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790251,2020-07-29 09:09:55 UTC,"Thank you for your bug report, could you give some details on the server you are connecting to. What protocol and settings do you use? What error do you get?
Could you add your 'journalctl -b 0' log after getting the issue?"
1790253,2018-09-01 02:00:07 UTC,This change was made by a bot.
1790256,2018-10-16 19:58:44 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1790266,2018-09-19 04:10:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790280,2018-09-01 13:31:28 UTC,Do You have gtk3 installed?
1790280,2018-09-10 07:37:48 UTC,"@Eduards Yes, of course Ubuntu 14.04 LTS contains libgtk-3 version 3.10.8-0ubuntu1.6
You can simply test from Ubuntu-Baltix 14.04.3 live USB, download image from http://download.vikis.lt/baltix/Baltix-Ubuntu-Linux-14.04.3-desktop-2015-09-amd64.iso"
1790280,2019-01-14 19:37:53 UTC,"Eduards Bezverhijs, how I can help you to fix this issue?"
1790280,2019-04-08 22:05:02 UTC,"Hi, do Baltix plan to move to at least 16.04? Timekpr-nExT is released, but only 16.04+ is supported.
I have encountered segmentation faults during new development for no apparent reason, is this still a cruciial problem?"
1790285,2018-09-11 08:08:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790294,2018-09-01 14:30:18 UTC,"Thanks Paul. Apport says ""Package libreoffice not installed and no hook available, ignoring"""
1790294,2018-09-01 13:15:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1790294,2018-09-06 13:38:22 UTC,"I can reliably reproduce the issue on an up-to-date cosmic with the default install (libreoffice-writer 1:6.1.0-0ubuntu2 installed, libreoffice-base not installed)."
1790294,2018-09-06 13:43:15 UTC,"And searching for ""libreoffice-base"" in gnome-software finds the package."
1790294,2018-09-06 13:59:54 UTC,And I can reproduce by running the following command:
1790294,2018-09-06 14:03:57 UTC,"The D-Bus method org.freedesktop.PackageKit.Query.IsInstalled correctly reports that ""libreoffice-base"" is not installed, and that ""libreoffice-writer"" is installed. So it looks like packagekit is doing its job. This might be a problem in gnome-software."
1790294,2019-01-22 17:26:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790299,2018-09-14 15:14:03 UTC,"Fixed with the latest update.
Many thanks and very well done"
1790299,2018-10-06 22:29:42 UTC,"If you would like this to be fixed for Bionic, please update the bug description for an SRU: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template"
1790299,2018-09-30 20:20:45 UTC,"The attachment ""0001-Fix-bug-1790299-Launchpad-Quotes-author-shown-with-h.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1790299,2018-09-04 22:53:11 UTC,https://github.com/varietywalls/variety/pull/74
1790299,2018-09-30 20:35:17 UTC,This bug was fixed in the package variety - 0.7.0-1
1790301,2021-01-14 01:17:23 UTC,dpkg was unable to read/create /var/lib/dpkg/info/tmux.list-new
1790315,2019-03-29 18:44:51 UTC,"When the text needs to be edited, it is entered into the text field and line breaks are deleted. This is necessary so that if the size (width) of the text field is changed, then a new text block will be formed (it will become wider and shorter or, on the contrary, longer).
Formation of lists and headings in the primitive way:
           Header (using spaces)
1.
2.
3."
1790315,2018-09-20 14:21:41 UTC,"Understood.
At this point I am more interested in wrap propriety in Pcbnew."
1790315,2018-09-12 13:18:05 UTC,"@Hildo, it could be done but it would require some major rework to support full text properties.  This is primarily due to the fact that the only font supported by pcbnew is it's own internal stroke font which is necessary to ensure accurate board plots.  It's possible to replace this using freetype which can convert system fonts into stroke fonts but the amount of work to do this will not be trivial.  Eeschema can use the system font rendering (soon to be Cairo) so it's far easier to implement since there is no requirement for absolute accuracy like there is in pcbnew.  I would rather not add anything new to the v6 road map as it is already very ambitious.  We could add it to a later road map."
1790315,2018-09-12 12:13:11 UTC,"@wayne, could this format be extended also to Pcbnew? (at the road map plan)"
1790315,2018-09-12 12:11:22 UTC,Linked with https://bugs.launchpad.net/kicad/+bug/1490050
1790315,2019-03-29 18:35:35 UTC,"It is enough to insert a line break after each last word in the line. When you increase the width of the text field - more whole words fit - the text engine works. It only remains after the last character (it can be any character, including punctuation marks) to insert \n without any kind of advanced formatting. Leave the left alignment by default. Why such complex formatting?"
1790315,2018-09-04 13:06:35 UTC,The upcoming new schematic file format will address this.  All text objects will have the same formatting options so horizontal and vertical justification from the anchor point will be supported.
1790315,2018-09-01 17:25:47 UTC,"I didn't get this: ""Justification is implied by the orientation."""
1790315,2018-09-01 17:02:38 UTC,Justification is implied by the orientation.
1790315,2018-09-04 19:32:47 UTC,"Cool Wayne, thanks for the explanation.
Is it possible to share a draft of this new file format?"
1790317,2018-09-27 22:42:41 UTC,This bug was fixed in the package sakura - 3.6.0-3
1790317,2018-09-27 16:17:53 UTC,Debian report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909744.
1790317,2018-09-27 14:32:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790317,2018-09-27 14:26:33 UTC,Sorry for the delay. I've applied the patch to the main branch. Tests with vte 0.52 doesn't show any problems.
1790317,2018-09-26 13:55:58 UTC,"When you do have patches for Ubuntu, please subscribe ~ubuntu-sponsors so that the bug will automatically be added to http://reqorts.qa.ubuntu.com/reports/sponsoring/"
1790317,2018-09-26 13:54:48 UTC,"Egmont, thanks for testing sakura. Could you please forward this patch to Debian since sakura is maintained there? Debian has vte 0.54.0."
1790317,2018-09-26 08:19:58 UTC,"The attachment ""draft fix"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1790317,2018-09-16 13:31:16 UTC,"Here's a draft patch. Needs thorough testing, and checking with older VTEs (maybe ifdefs or so)."
1790317,2018-09-01 17:02:31 UTC,"Thanks for the report, Egmont. I’ll look it into it ASAP (unfortunately that means two weeks :-/)"
1790320,2018-09-27 05:00:06 UTC,This change was made by a bot.
1790331,2020-03-19 11:19:47 UTC,Closing because fixed in later versions (can't replicate in 0.92.4 nor 1beta02).
1790334,2018-09-02 05:01:12 UTC,Looks like Shutter is in your desktop session startup list. You can remove it from there using the GUI of gnome-session-properties.
1790334,2018-09-15 22:40:37 UTC,"I've checked and only have 3 applications/packages that are started on bootup, and none of them are the Shutter program. I do however have Shutter pinned to the launcher bar."
1790335,2018-10-24 19:17:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790335,2019-10-01 15:28:59 UTC,"Same issue here, bionic 18.04, nvidia optimus laptop, xorg (no wayland), super+space for layout switching."
1790338,2018-09-02 01:50:40 UTC,"After a bit more playing, it appears the policy.json file ""is"" being read, but my interpretation of what ""!"" means was wrong.  Apparently, this actually means ""anybody but users with the admin role"".  I interpreted ""nobody"" as inclusive of admin-level users, including domain admins."
1790339,2018-09-06 11:08:02 UTC,"This appears to be a packaging problem with vim. Package vim-common installs /usr/share/applications/vim.desktop, and its exec line points to ""vim"", which isn't necessarily installed."
1790343,2018-09-03 11:13:46 UTC,Test is missing a return statement. I think main is compiled more efficiently because it can see that the value in the ptr field is the same as the value being returned so it's happy to put ptr into r0. For test the return is missing so the compiler might be assuming that r0 should not be reused.
1790343,2018-09-03 17:37:18 UTC,You are correct that adding a return does make test() use R0.
1790343,2018-09-05 01:39:03 UTC,Reduced the example to the bare minimum. This shows R4 being pushed and popped needlessly: https://godbolt.org/z/Y5jzx2
1790343,2018-09-12 10:36:41 UTC,I can reproduce with trunk GCC as well using the same flags (-std=c++17 -O3 -mcpu=cortex-m4).
1790345,2018-11-30 21:18:57 UTC,Are you planning to support a bionic repo?
1790347,2018-09-02 08:45:15 UTC,"I have to say sorry, cause I am a newbie in Linux. I have scrolled another bug report and found the right solution - to reset PulseAudio."
1790348,2018-09-18 04:47:48 UTC,"Hi Peter,"
1790348,2018-09-17 12:01:48 UTC,"Hi,
We see the required dependency packages didn't get installed properly from the hp-check log. Make sure the network connection is good during the installation. Can you rty re-installing the 3.18.7 run file and update whether the installation process went through with no errors or not?"
1790348,2018-09-11 18:56:30 UTC,One wonders why some people post here. I suppose it is not to answer questions.
1790348,2018-09-03 18:28:42 UTC,Did the printer work before upgrading? Why install hplip 3.18.7.run? What is wrong with using the hplip packages from the new distribution?
1790350,2018-09-02 10:54:33 UTC,"When I try to run a partial upgrade,  I get ""Can't install ubuntu-desktop
It was impossible to install a required package. Please report this as a bug using 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.""
I don't propose to report this as a seperate bug since I'm guessing it's all part of the same problem I've got on this one"
1790350,2018-09-02 09:25:27 UTC,"Software updater reports ""Failed to download repository information  -- Check your internet connection""  but my internet connection otherwise appears to be working fine."
1790350,2018-09-02 09:42:51 UTC,Here are the reported details (which I struggle to understand) after witnessing several minutes of apparently successful cache updates:
1790350,2018-09-02 10:00:12 UTC,"I have tried to overcome this problem by changing ""Download from"" from Isle of Man Server (where I had been staying) to UK server (where I am now) and then to Main server,  but none of these changes have prevented Software updater from coming up with ""Failed to download repository information"" after running a cache update from each of them in turn."
1790350,2018-09-02 12:13:33 UTC,"Noticed some errors were being shown as coming from ftp.hk.debian.org, so tried an unconventional experiment of setting up VPN to a HongKong server, selecting ro-mirrors.evowise.com/ubuntu ftp.hk.debian.org/debian as the best mirror for my new location and attempting cache update from there.
Cache updating completed slowly but although there were one or two ""network isn't available"" notes, most packages achieved 100% after about an hour of downloading.
Experiment didn't work though;  At the end of the updating,  I got the same window saying ""Failed to download repository information  - - Check your Internet connection""
Now removing that VPN connection and restoring ""Download from"" to Main server."
1790352,2018-09-04 14:52:08 UTC,Victor
1790352,2018-09-04 15:08:23 UTC,"Ah, the double-click thing works too - nice! I might be able to figure out where in the code this happens. Thanks!"
1790352,2018-09-04 14:04:59 UTC,"Okay, I think I figured out part of the problem."
1790352,2018-09-03 03:16:13 UTC,I am opening from the menu bar item in Caja called Bookmarks.
1790352,2018-09-02 19:49:28 UTC,"There is list of the ""Bookmarks"" at the ""Places"" sidebar which is in the left side of Caja. I'm opening from there."
1790352,2018-09-02 18:27:05 UTC,"By middle button, did you mean the ""scrolling wheel"" of the mouse? It does work on my machine. I've looked at the code, the option is there; it should work."
1790352,2018-09-02 17:11:43 UTC,"I'm running 1.20.2 - and for me it doesn't work. And that is common over
3 different computers.  Strange."
1790352,2018-09-02 15:15:23 UTC,It works on Caja 1.20.2 version.
1790352,2018-09-02 18:51:05 UTC,"Abu Sakib,"
1790355,2018-10-20 05:18:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790355,2019-10-03 13:59:52 UTC,"I am having this same problem on Ubuntu 18.04 LTS
Trying to install package fnfxd 0.3-16ubuntu1 but fails, both on apt-install and in Synaptic Package Manager. Hope
I am removing it but it still fails to install.."
1790358,2019-02-25 13:52:53 UTC,it's happened in all openstack version not only queens
1790358,2019-02-25 13:51:58 UTC,I Have same issue and it seems no one know how to solve this issue
1790358,2019-02-26 15:26:48 UTC,Could you paste the command or answers file you are using?
1790358,2019-02-26 17:16:42 UTC,I've tried to reproduce it using rocky and worked fine. My steps in a clean centos7 (wihtout epel repo enabled):
1790367,2018-09-26 17:23:26 UTC,This bit seems to be the relevant error message. It's from the attached VarLogDistupgradeApttermlog.gz.
1790372,2020-06-19 13:40:52 UTC,Closing because I can't reproduce.
1790372,2018-10-07 13:55:10 UTC,I can't reproduce that behavior...
1790372,2018-10-07 14:24:07 UTC,Is there any info that would help you? It's still present for me.
1790372,2018-10-07 14:25:47 UTC,"apt-cache policy libgtk-3-0
libgtk-3-0:
  Installiert:           3.18.9-1ubuntu3.3"
1790373,2020-03-19 17:10:26 UTC,Closing because Fix Released.
1790373,2019-04-02 05:26:28 UTC,It seems like this is 'sort of' fixed in Inkscape master. It still looks somewhat weird with the long buttons on the right but the correct dialog does come up if you click on it.
1790373,2019-04-02 12:38:18 UTC,"There's a separate report for the vertical buttons on gitlab, so this one here only applies to 0.92.x."
1790373,2018-10-07 13:59:05 UTC,"> - Get dialog 1 instead of 2, and dialog 2 is a huge button with vertical text below it.
I always get the right dialogs (and the huge button) ?
"
1790373,2018-10-07 14:32:27 UTC,"Yes, it's the same for me now. I get the correct dialogs with an Inkscape master compiled today."
1790374,2019-03-04 12:08:43 UTC,Can reproduce with both 0.92.4 and master (061c42fe).
1790374,2019-03-04 16:05:12 UTC,Thanks for checking!
1790374,2020-01-25 11:44:35 UTC,"In your configuration, I can increase the size of the dialogs, but not decrease it. That's because the minHeight of the Align & Distribute dialog which is also in that region must not be undercut. For more info see https://gitlab.com/inkscape/inbox/issues/1352#note_271596770. If I misunderstood the issue, please reopen at Gitlab."
1790381,2018-09-03 10:24:14 UTC,"- problem not reproduced on Windows 10, Inkscape 0.92+devel (d890608, 2018-08-21).
- my user extensions folder is at:
C:\Users\username\AppData\Roaming\inkscape\extensions
- in this folder I have the files: multipledivision.inx and multipledivision.py
- these files are not in the normal inkscape installation folder, but they execute properly."
1790381,2018-09-03 11:01:49 UTC,"Alvin, thanks for testing!"
1790381,2018-09-03 11:35:15 UTC,"- confirmed on Windows 10, Inkscape 0.92+devel (d890608, 2018-08-21)
- I created a new subfolder:
C:\Users\username\AppData\Roaming\inkscape\extensions\testing\
- I moved the files multipledifference.py and .inx into this folder.
- then the extension 'Multiple Difference' no longer showed up in the Inkscape Extension menu
- and I get the DOS error messages:"
1790381,2018-10-07 12:07:10 UTC,"doctormon: can you take a look at this, if this still stands?"
1790381,2018-10-07 12:49:43 UTC,"Currently, none of my old third-party extensions show up - I don't know if that's due to incompatible inx formats, and is supposed to be like this, or if it's a bug."
1790388,2019-11-10 14:57:16 UTC,Addendum to my previous comment: removing .xinputrc and logging out and in again did actually work for me.
1790388,2019-11-10 14:54:02 UTC,"Still happens with GnuCash 3.7 in Ubuntu 19.10.
Relevant dmesg lines:
[  268.839500] gnucash[2767]: segfault at f8 ip 00007f70b26f8a96 sp 00007ffd4525bac8 error 4 in libgdk-3.so.0.2404.8[7f70b26d5000+80000]
[  268.839511] Code: 26 fe ff e9 57 fd ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 8b 87 f8 00 00 00 c3 0f 1f 40 00 f3 0f 1e fa 31 c0 <48> 39 bf f8 00 00 00 0f 94 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00"
1790388,2018-11-09 17:44:01 UTC,I experimented a bit and found that removing the user .xinputrc file solved the problem for me.
1790388,2018-10-15 10:29:28 UTC,Still happens in 1:3.3-2
1790388,2018-11-09 17:47:23 UTC,"The .xinputrc file was from January 2016, so this still is a regression introduced with the upgrade mentioned in the description."
1790388,2018-09-02 19:13:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790388,2018-09-02 19:06:02 UTC,Please notice the core file I have added.
1790388,2018-09-02 21:29:03 UTC,The problem does not occur on Debian buster in Version 3.2-1
1790397,2018-09-02 20:27:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599258"
1790397,2018-12-25 09:12:07 UTC,Please better explain what it all means and why the action heartbeat mechanism should care about asynchronous actions. A 3rd party that processes async actions can't send heartbeats to Mistral.
1790397,2019-12-19 16:14:13 UTC,"If there was a heartbeat endpoint, a 3rd party process could hit it periodically. In our application we have an external service tightly integrated with mistral and would leverage this. Might make sense for the actions to be configurable in that case, since a normal 3rd party with a http callback probably wouldn't use it."
1790397,2019-12-20 06:14:14 UTC,"Yes, ok. We've never thought of this heartbeat mechanism as of something visible in the API. But your reasoning makes sense. I think we can extend it for this use case. I'd prefer to have a new BP for this though."
1790409,2018-09-24 23:53:25 UTC,This sounds like a nemo issue since gnome-shell does not handle desktop icons.
1790409,2018-09-24 23:06:21 UTC,I can also mention that changing my theme from Ambiance to Adwaita removed the issue. All the other accounts use Ambiance so there must be user level settings that is triggering this.
1790409,2018-09-24 23:03:36 UTC,I'm no longer certain this is nemo related as I found one account with Nemo and without the problem.
1790409,2018-09-02 21:50:37 UTC,I also checked updating to a newer version (3.8.4-1~bionic0) of nemo using the cinnamon ppa mentioned in the link in my description and it had no effect.
1790427,2019-04-03 08:38:57 UTC,"@josh the FFe bug for desktop is bug 1819207, the only remaining bit we need is a release of ubiquity."
1790427,2018-12-10 09:26:34 UTC,"Desktop would be firmly in favour of adding this feature to the Ubiquity based installer.  We've had a look and other than seeding open-vm-tools and adding the change to d-i, everything else should just work."
1790427,2019-04-02 17:34:11 UTC,"Hi,"
1790427,2019-03-08 06:17:00 UTC,"Hi,
open-vm-tools already is in main and so is the source [1]
Therefore all you need to get open-vm-tools-desktop to main is to seed it (or add a dependency at the right place from your installer if that is better for you).
It is ready and the component mismatch can be fixed up by an AA then."
1790427,2019-03-07 08:02:57 UTC,"On a side note, on Disco (and probably previous release) to install drivers from vmware player's UI you have to manually install libncursesw5."
1790427,2019-03-07 07:55:11 UTC,VMware PR https://bugzilla.eng.vmware.com/show_bug.cgi?id=1316614 for tracking this issue.
1790427,2019-04-26 06:22:56 UTC,this issue is fixed in ubuntu 19.04 desktop
1790427,2018-12-05 18:26:39 UTC,I've marked the subiquity task as invalid given the updated information and added the debian-installer task
1790427,2019-03-07 07:44:55 UTC,"On Desktop we need open-vm-tools-desktop which has dependencies on ""open-vm-tools"" core package and X libraries and provides additional desktop specific features."
1790427,2018-12-05 03:29:03 UTC,"> From latest sync notes:
"
1790427,2018-12-05 03:26:22 UTC,">But It's not installed automatically when install guestOS ubuntu desktop in ESXi
"
1790427,2018-12-04 20:47:29 UTC,From latest sync notes:
1790427,2018-12-04 20:32:55 UTC,@yhzou
1790427,2018-12-04 18:45:18 UTC,+subiquity task
1790427,2018-09-03 07:12:08 UTC,I linked the Debian bug here in the bug taskss.
1790427,2018-09-03 03:05:08 UTC,"Currently open-vm-tools is installed automatically by default when install guestOS ubuntu server in ESXi. But It's not installed automatically when install guestOS ubuntu desktop in ESXi and we need to install it with command ""sudo apt-get install open-vm-tools"""
1790427,2018-12-05 06:26:01 UTC,@Josh hearing the above confirmed you might find someone in foundations who would consider my MP at least for our branch of D-I?
1790441,2019-09-13 16:05:46 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1790441,2018-09-03 06:11:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599288"
1790441,2019-07-18 11:23:57 UTC,"Reviewed:  https://review.opendev.org/599288
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=aed90bab7e5989b172c6fad373c0a50628a05a8f
Submitter: Zuul
Branch:    master"
1790442,2018-10-05 14:34:18 UTC,"Hi mashuting,"
1790454,2018-11-01 07:56:19 UTC,"I'm happy to report that everything seems stable now.
I'm now running the following config
 - kernel 4.19.0-041900rc7-generic
 - delay after reset set to 200ms (see #38)
 - unload iwlwifi on suspend/sleep
 - btusb.enable_autosuspend=0"
1790454,2018-10-11 17:00:30 UTC,"Ok, running a patched kernel now.  Let's see if I can still trigger the bug."
1790454,2018-10-12 06:39:12 UTC,"Sorry, bug is still occurring, even with the patch.  Dmesg is attached."
1790454,2018-10-14 17:12:48 UTC,"I've seen similar things recently, and seems like increase the delay after reset can alleviate the issue."
1790454,2018-10-15 07:52:26 UTC,"ok, will do"
1790454,2018-10-15 14:56:11 UTC,"I've changed the delay to 200ms, but now I get"
1790454,2018-10-16 08:01:17 UTC,"Hmm, can you try removing iwlwifi before suspend, not sure if there's an internal race happen inside the Intel wireless module."
1790454,2018-10-09 06:58:40 UTC,Problem still occurs.  Dmesg is attached.
1790454,2018-10-18 07:00:21 UTC,"Also doesn't seem to make any difference...
Dmesg (attached) shows that iwlwifi is loading after initial btusb initialization, but it still fails about 2/3 of the time."
1790454,2018-10-19 08:56:03 UTC,"Hmm, running the current setup (200ms sleep+iwlwifi unload-on-suspend), I must say that the bt loading has become more reliable.  It still doesn't work 100% of the time, but it definitely is working more often than before (maybe 75% of the time it works ok now)."
1790454,2018-10-25 05:29:13 UTC,"My bad, I didn't saw it works on 4.15 but fails since 4.17."
1790454,2018-10-09 07:34:49 UTC,"Is it possible for you to try this patch?
https://patchwork.kernel.org/patch/10624303/"
1790454,2018-11-11 15:28:21 UTC,Yes please.
1790454,2018-12-23 05:59:44 UTC,"Bas,"
1790454,2018-11-24 13:27:26 UTC,"I'm still planning to run a bisect to find the offending commit, but havne't found the time yet."
1790454,2018-12-21 23:42:11 UTC,"I am having a similar issue with Intel 8260. Wifi and BT works correctly after cold boot. Wifi works correctly after suspend, but BT was showing no adapters available in KDE plasma widget. dmesg would report ""[  150.064149] Bluetooth: hci0: Failed to send firmware data (-38)"" after each resume."
1790454,2018-12-22 13:54:33 UTC,"If the enable_autosuspend option doesn't fix your issue, I think you are encountering a different bug (with overlapping symptoms).  For clarity, it might be best to open a separate bug report for your issue."
1790454,2018-12-23 05:59:07 UTC,"DH, I think this can workaround your issue:"
1790454,2018-12-23 19:34:24 UTC,"Yeah, ""enable_autosuspend=0"" by itself fixes the issue."
1790454,2019-01-08 15:24:03 UTC,"Bas,"
1790454,2019-04-04 09:25:08 UTC,"""enable_autosuspend=0"" did not fix the issue for me."
1790454,2019-04-04 09:46:43 UTC,"Emiliano,"
1790454,2019-06-17 07:15:58 UTC,Please test this patch.
1790454,2019-10-09 19:03:15 UTC,I am running into exactly the same problem as Bas Zoetekouw. I added the enable_autosuspend=0 option:
1790454,2019-10-15 16:18:41 UTC,"Stan,
Please file a separate bug so logs can be collected."
1790454,2018-10-08 19:28:24 UTC,"Ah yes, cold boot seems to fix it for now.  I'll need to wait and see if the bug now occurs during normal operation."
1790454,2018-11-23 11:51:59 UTC,Same issue here.
1790454,2018-10-08 14:45:17 UTC,"Hmmm, do you still see this if you cold boot with the quirk?"
1790454,2018-09-28 07:08:38 UTC,I can confirm that the bug still occurs in 4.19.0-041900rc5-generic.
1790454,2018-10-08 10:32:38 UTC,"Ok, please use v4.19-rc6 or rc7, and boot with kernel parameter ""usbcore.quirks=8087:0a2b:k"" which disables LPM for the Bluetooth device, and see if this issue still persists."
1790454,2018-09-03 08:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790454,2018-09-03 08:36:44 UTC,apport information
1790454,2018-09-03 08:36:45 UTC,apport information
1790454,2018-09-03 08:36:49 UTC,apport information
1790454,2018-09-03 08:36:50 UTC,apport information
1790454,2018-09-03 08:36:51 UTC,apport information
1790454,2018-09-03 08:36:53 UTC,apport information
1790454,2018-10-08 12:25:35 UTC,"With kernel 4.19rc7 and the kernel parameter as you prescribed, the BT adapter won't work at all.  The timeouts that would only occur sporadically after resume, are now present from boot, and the previous unload-modules/suspend/resume/load-modules cycle no longer works to get BT back on.
Dmesg is attached."
1790454,2018-09-03 08:36:55 UTC,apport information
1790454,2018-09-03 08:36:57 UTC,apport information
1790454,2018-09-03 08:36:58 UTC,apport information
1790454,2018-09-03 08:37:00 UTC,apport information
1790454,2018-09-03 08:36:54 UTC,apport information
1790454,2018-09-03 08:37:03 UTC,apport information
1790454,2018-09-03 08:37:02 UTC,apport information
1790454,2018-10-08 08:00:09 UTC,Is it possible for you to attach full dmesg? i.e. everything from boot. I'd like to check if LPM is enabled for this device.
1790454,2018-10-08 07:11:20 UTC,"Hmm, I guess the dmesg above was mispasted."
1790454,2018-10-08 07:03:05 UTC,The bug triggered again this morning:
1790454,2018-09-28 10:32:35 UTC,When the bug is triggered.
1790454,2018-10-08 10:11:56 UTC,"Sure, here it is."
1790454,2018-09-28 07:29:16 UTC,Can you attach full dmesg with `usbcore.dyndbg=+p`?
1790454,2018-09-28 07:17:39 UTC,"Adding to that, there is a (somewhat) reliable way to get bluetooth back.  It involves goign to the following process _twice_: stopping the bluetooth service, unloading all relevant modules, suspending the laptop, resuming, reloading all modules, starting the bluetooth service.
Rather cumbersome, but it might help other experiencing this issue."
1790454,2018-09-05 14:17:41 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1790454,2018-09-03 08:37:06 UTC,apport information
1790454,2018-09-28 08:26:21 UTC,"Do you need a dmesg when the bug is triggered, or does a regular boot log suffice?   It's hard to trigger the bug manually (but it occurs every couple of days)."
1790460,2018-09-04 12:10:40 UTC,"This modification also fixes issue:
https://git.greensocs.com/qemu/qbox/commit/a8ed106032e375e715a531d6e93e4d9ec295dbdb
Although I tested it only on v2.12.0 and didn't noticed performance improvement."
1790460,2018-10-12 08:34:18 UTC,"Long-term testing showed that my trivial adaptation didn't fixed issue and I sticked to modification from QBox. It didn't failed yet.
And yes, issue still relevant to current master branch."
1790460,2019-08-02 17:51:40 UTC,"I think we fixed this bug in commit 013aabdc665e4256b38d which would have been in the 3.1.0 release (this is why we closed #1774677, which as you say is the same issue)."
1790461,2019-10-10 12:42:47 UTC,I think this is fixed by https://review.opendev.org/#/c/686489
1790461,2019-10-12 01:37:00 UTC,Yes it looks like working now :)
1790464,2018-09-03 15:01:42 UTC,There is no gimp-help 2.10 version yet released by the Gimp develoeprs:
1790465,2018-10-15 23:42:14 UTC,"An improvement for macOS when Homebrew is installed to /usr/local:
https://github.com/mixxxdj/mixxx/commit/acfd563211d00309f2a6542981f42161f835695e"
1790466,2018-09-03 09:28:29 UTC,Is my laptop at risk?
1790468,2018-09-08 16:14:28 UTC,"I installed Kubuntu 18.10 in a virtual vmware machine and activated lvm2.
After installing and rebooting I see again the wrong error message in recovery mode / system summary.
I guess this is the Package wants to do:"
1790468,2018-09-08 16:28:15 UTC,You can start the script /lib/recovery-mode/options/system-summary in a terminal to check this issue.
1790468,2018-10-26 03:14:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790478,2018-09-04 05:14:28 UTC,@Daniel: the latest gdm even in proposed that Dimitri and I can easily try is currently 3.29.91-1ubuntu2
1790478,2018-09-03 11:19:12 UTC,"I have found this to be locally reproducible with:
$ autopkgtest --shell-fail --apt-upgrade --no-built-binaries --testname=boot-and-services --apt-pocket=proposed=src:systemd,src:dbus,src:iproute2,src:glibc systemd_239-7ubuntu6.dsc -- qemu --qemu-options='-cpu host' --qemu-command=qemu-system-i386 --cpus 8 --ram-size=4096 ~/autopkgtest-cosmic-i386.img"
1790478,2018-09-03 11:27:23 UTC,"I just found that further calls to
  $ sudo systemctl restart gdm"
1790478,2018-09-04 02:46:33 UTC,"Try gdm version 3.29.92, which has a fix for some rather serious issues:"
1790478,2018-09-04 05:04:46 UTC,"...ubuntu7 completed tonight thanks!
I tested 2 times from proposed in the local tester and working as expected now."
1790478,2018-09-04 22:08:59 UTC,This bug was fixed in the package systemd - 239-7ubuntu7
1790487,2018-12-20 04:03:51 UTC,I also tryed many other ubuntu 18.04 flavours on the same laptops and none of them presented this issue.
1790487,2018-10-09 14:33:20 UTC,It affects Google Chrome from Google's repository as well.
1790487,2018-12-20 03:58:57 UTC,It affects me too on both of my laptops: one with intel hd graphics 5500 (i5 5300u) and the other with intel hd graphics 4400 (i5 4300u).
1790487,2018-10-09 14:45:22 UTC,I'm sure you have read recent reports (see omgubuntu) - Google are not (currently?) supporting accelerated graphics using the capabilities of graphics cards.  Hence why Google Chrome and Chromium before poorly on certain PC's.
1790487,2018-09-07 06:18:20 UTC,"I tested Chromium (default browser) and it is also affected with the lag/freeze issue.
After testing several players now i confirm that only firefox has no issue at all.
Let me know if any system output needed"
1790487,2018-09-03 12:35:03 UTC,Exactly the same issue found here: https://discourse.ubuntubudgie.org/t/video-freezing-on-dell-xps15/955/7
1790487,2018-09-04 07:13:27 UTC,"Is this browser specific? I.e. does it occur in chromium/chrome but is ok
in Firefox?"
1790487,2018-09-04 06:59:55 UTC,@fossfreedom Window previews applet is not added to panel. I also had the same issue with a fresh install of ubuntu-budgie. Let me know if any terminal output needed.
1790487,2018-09-03 13:02:34 UTC,Is the Window previews applet added to your panel or not?
1790487,2018-12-20 06:19:02 UTC,If you use chrome or chromium turn off acceleration in the about config options or use firefox.
1790487,2018-09-04 08:05:39 UTC,"I mainly use Firefox, but i didn't encounter issues in the browser. I
cannot say anything about
chrome/chromium (yet),but i will test it"
1790487,2018-12-20 22:27:34 UTC,I found a fix without any throwbacks!
1790488,2018-09-03 12:52:44 UTC,And here is a screen capture of pavucontrol. It shows the HDMI sound output.
1790489,2018-09-04 15:04:38 UTC,Moving milestone to Stein-1 as this is affecting ocata and not required for Rocky RC2.
1790489,2018-09-12 08:44:05 UTC,"It's not happening so often, moving to high"
1790489,2018-09-10 08:22:21 UTC,"Noop change is working fine https://review.openstack.org/#/c/560445, removing alert on this."
1790489,2018-09-03 15:17:38 UTC,The error on controller-0:
1790489,2018-09-03 15:19:44 UTC,And a bit earlier:
1790489,2018-09-04 07:22:18 UTC,"Mmmh weird. I see we've stopped (again) collecting /var/log/pcsd ?
Does this happen only in ocata? or is this more widespread?"
1790490,2018-09-07 20:31:41 UTC,"I totally agree, also check https://review.openstack.org/#/c/599594/"
1790490,2019-02-19 13:34:53 UTC,Is this still an issue?
1790490,2021-02-17 17:09:20 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1790492,2018-10-07 12:03:34 UTC,"If that's related to the 4k problems, it might be better in the GTK3 version ? Or is it unrelated ?"
1790492,2018-10-11 11:56:20 UTC,"I think it's related, but as a general (simple-sounding, even) feature request it stands on its own."
1790492,2020-03-26 14:53:25 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1790494,2018-09-04 18:30:08 UTC,This change was made by a bot.
1790495,2018-09-03 17:15:47 UTC,Swapped overlong summary with description
1790496,2018-09-05 07:17:42 UTC,@paelzer - from my experience with gpsd that looks pretty good regarding the file rules etc - hopefully someone else who is more intimately familiar with AppArmor can comment on the list of capabilities.
1790496,2020-01-31 05:06:58 UTC,Are there any additional AppArmor denials in dmesg?
1790496,2020-01-31 04:20:06 UTC,That does not seem to be it. There seems to be a leaky avstraction somewhere.
1790496,2020-01-31 03:13:28 UTC,I can reproduce this by running:
1790496,2020-01-30 21:55:07 UTC,I can not add /dev/ttyUSB0 to a running gpsd either automatically or manually (on prerelease 20.04) when the AppArmor profile is active. Disabling it allows manual controls to work.
1790496,2020-01-30 21:43:11 UTC,"Jan 30 13:28:49 Dell-2018 sudo[135379]:   jamesb : TTY=pts/1 ; PWD=/home/jamesb/ntpsec ; USER=root ; COMMAND=/usr/sbin/gpsdctl add /dev/ttyUSB0
Jan 30 13:28:49 Dell-2018 sudo[135379]: pam_unix(sudo:session): session opened for user root by jamesb(uid=0)
Jan 30 13:28:49 Dell-2018 gpsdctl[135380]: gpsd_control(action=add, arg=/dev/ttyUSB0)
Jan 30 13:28:49 Dell-2018 gpsdctl[135380]: reached a running gpsd
Jan 30 13:28:49 Dell-2018 audit[135224]: AVC apparmor=""DENIED"" operation=""file_perm"" profile=""/usr/sbin/gpsd"" name=""/run/gpsd.sock"" pid=135224 comm=""gpsd"" requested_mask=""r"" denied_mask=""r"" fsuid=124 ouid=0
Jan 30 13:28:49 Dell-2018 audit[135224]: AVC apparmor=""DENIED"" operation=""file_perm"" profile=""/usr/sbin/gpsd"" name=""/run/gpsd.sock"" pid=135224 comm=""gpsd"" requested_mask=""r"" denied_mask=""r"" fsuid=124 ouid=0
Jan 30 13:28:49 Dell-2018 sudo[135379]: pam_unix(sudo:session): session closed for user root"
1790496,2018-09-03 14:38:18 UTC,@ubuntu-security: it would be great if someone could give the profile a security POV pre-check
1790496,2018-10-09 09:10:53 UTC,"FYI - I'll work on this along with some other gpsd activities related to the planned MIR.
But that will be 19.04 material and not urgent right now.."
1790496,2018-09-17 15:40:55 UTC,"Looks good to me, thanks Christian."
1790496,2020-01-31 08:32:08 UTC,I tested the rule it works fine.
1790496,2020-02-01 08:24:50 UTC,This bug was fixed in the package gpsd - 3.20-4
1790496,2018-10-09 09:11:10 UTC,@Seth - thanks for the profile review
1790496,2020-01-31 08:38:42 UTC,"Prepped, Tested and submitted to Debian as https://salsa.debian.org/debian-gps-team/pkg-gpsd/merge_requests/3"
1790501,2018-09-19 09:53:17 UTC,"Hi,"
1790501,2018-09-11 02:46:59 UTC,"Hi - did you clear out the model records as noted above? Are there more logs we can look at? Logging from the undertaker worker for that model would be especially useful. You mention lots of transactions - were the transactions backed up, or were they being applied ok?"
1790501,2019-06-25 02:49:22 UTC,"We have done some work in the area both in 2.6 and 2.7 series and believe that this may have been resolved as part of it. I'll mark this as Incomplete for now. If you are seeing this on a newer Juju versions, please re-open and provide associated, recent logs."
1790501,2018-09-03 15:02:26 UTC,"Note that at some point we changed the credentials for the user of this model, so juju was no longer able to issue commands to OpenStack for this model. Said change was later reverted."
1790501,2019-08-24 04:17:27 UTC,[Expired for juju because there has been no activity for 60 days.]
1790501,2018-09-06 01:14:28 UTC,"I initially attempted to remove the model via our Service Manager Juju client. This didn't work and I got a ""ERROR cannot destroy model: failed to destroy model: state changing too quickly; try again soon""."
1790509,2020-01-15 16:02:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790509,2018-09-03 15:56:02 UTC,"-- Reboot --
Sep 03 09:48:42 ubuntu systemd-networkd[317]: Enumeration completed
Sep 03 09:48:42 ubuntu systemd[1]: Started Network Service.
Sep 03 09:48:42 ubuntu systemd-networkd[317]: eth0: Interface name change detected, eth0 has been renamed to mainif.
Sep 03 09:50:53 ubuntu systemd[1]: Stopping Network Service...
Sep 03 09:50:53 ubuntu systemd[1]: Stopped Network Service.
Sep 03 09:50:54 ubuntu systemd[1]: Starting Network Service...
Sep 03 09:50:54 ubuntu systemd-networkd[627]: Enumeration completed
Sep 03 09:50:54 ubuntu systemd[1]: Started Network Service.
Sep 03 09:50:54 ubuntu systemd-networkd[627]: lo: Link is not managed by us
Sep 03 09:50:54 ubuntu systemd-networkd[627]: vlan5: netdev ready
Sep 03 09:50:54 ubuntu systemd-networkd[627]: mainif: IPv6 successfully enabled
Sep 03 09:50:54 ubuntu systemd-networkd[627]: vlan5: Gained carrier
Sep 03 09:50:54 ubuntu systemd-networkd[627]: lo: Link is not managed by us
Sep 03 09:50:54 ubuntu systemd-networkd[627]: mainif: Gained carrier
Sep 03 09:50:54 ubuntu systemd-networkd[627]: vlan5: Gained IPv6LL
Sep 03 09:50:54 ubuntu systemd-networkd[627]: vlan5: Configured
Sep 03 09:50:56 ubuntu systemd-networkd[627]: mainif: Gained IPv6LL
Sep 03 09:50:56 ubuntu systemd-networkd[627]: mainif: Configured"
1790512,2018-09-27 22:42:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790513,2018-09-03 16:30:09 UTC,This change was made by a bot.
1790515,2018-09-08 08:08:20 UTC,please try the latest 396 from ubuntu graphics ppa
1790515,2020-07-05 21:31:52 UTC,"Could you try the fix from #1881701, please?"
1790516,2018-09-03 20:25:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1790520,2018-09-03 20:55:21 UTC,I've switched both services back to using the original CA.
1790520,2018-09-03 21:09:31 UTC,And my livepatch client ('canonical-livepatch enable <MYAPIKEY>') just registered fine.
1790520,2018-09-04 03:11:26 UTC,"Only livepatch.canonical.com relies on pinning, so I've switched auth.livepatch.canonical.com back to Let'sEncrypt."
1790520,2018-09-04 11:23:07 UTC,"Also confirmed as now working here, thank you!"
1790526,2018-09-03 19:39:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599450"
1790526,2019-07-31 21:00:55 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1790531,2018-09-05 20:09:24 UTC,Any assistance would really be appreciated
1790536,2018-09-03 21:10:51 UTC,"I helped troubleshoot this with him on IRC. Looking at their dmesg and syslog, it looks like nouveau is failing in some way, which is causing kscreen to fail in some way. Weird that it works with xrandr."
1790536,2018-09-05 05:23:34 UTC,Just as a side note - you also get booted back to a login screen when trying to scale with xrandr
1790536,2018-10-09 23:15:19 UTC,"> scake  with: xrandr --output DP-2 --scale 0.8x0.8' or 1.5x1.5
"
1790536,2020-12-17 04:04:41 UTC,Thank you for reporting this bug to Ubuntu.
1790536,2021-02-15 04:17:53 UTC,[Expired for lxqt-config (Ubuntu) because there has been no activity for 60 days.]
1790539,2020-03-19 09:19:58 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1790542,2019-04-26 09:16:45 UTC,"at least for lumberjack and ranger this should be an easy one.
Already found the right spot in worker_programs (missing unnotify_player instruction)"
1790542,2019-09-15 16:00:06 UTC,Migrated to https://github.com/widelands/widelands/issues/1078
1790555,2020-09-09 10:14:27 UTC,Closing because INVALID.
1790555,2018-09-29 00:17:38 UTC,"The issue is also reported with the author of the brew formula:
https://github.com/caskformula/homebrew-caskformula/issues/63"
1790555,2018-09-25 14:19:09 UTC,"Exactly the same error, can't install inkscape..."
1790555,2018-09-21 01:40:01 UTC,Got the same error:
1790555,2018-09-28 09:18:47 UTC,"Same error for me,"
1790555,2018-09-11 16:08:36 UTC,I got the exact same error here.
1790555,2018-09-04 14:38:27 UTC,I got the same error.
1790555,2018-09-17 19:56:09 UTC,"Same bug over here. ""brew install --force ..."" doesn't help, deleting files doesn't help. ""brew cleanup"" and ""brew doctor"" fail to illuminate any problems."
1790555,2018-09-04 00:32:31 UTC,I've tried deleting both files and trying again. Other suggestions for successfully running brew install?
1790556,2018-09-09 13:32:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790563,2020-01-16 00:40:21 UTC,gnome-software[2024]: json_object_get_string_member: assertion 'node != NULL' failed
1790563,2019-05-30 10:03:39 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1790563,2019-05-30 10:03:31 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.12
1790563,2019-05-14 21:56:09 UTC,Tested gnome-software 3.20.5-0ubuntu0.16.04.12 and it no longer shows the critical warnings.
1790563,2019-05-14 08:00:59 UTC,"Hello Robert, or anyone else affected,"
1790563,2019-04-25 13:57:21 UTC,"An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: ""Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.""."
1790569,2019-05-07 12:23:22 UTC,"All open patches have been abandoned so I'm marking this incomplete and removing the assignee. I don't doubt this is something that could happen to leak allocations, but we'd need a more specific recreate I think. As a workaround, the operator could use the osc-placement CLIs to cleanup the unwanted allocations, or delete all allocations for the instance and then run the 'nova-manage placement heal_allocations' command to correct the allocations for the instance in placement."
1790569,2019-05-07 12:20:59 UTC,Would probably need a set of logs for the failure described above regarding migration failing. I'm sure there are probably places in the conductor code where we're not handling those types of errors but would need some more specific details with a log traceback.
1790569,2019-05-07 12:18:35 UTC,"Which release are you using? Since Queens conductor should move the allocations for the source node held by the instance to the migration record, and then the scheduler will claim resources on the dest node using the instance consumer record. If the scheduler fails to reply to the call from conductor, the conductor task should cleanup the allocations in the rollback routine:"
1790569,2019-07-07 04:17:23 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1790569,2019-05-07 00:30:21 UTC,"Change abandoned by fupingxie (<email address hidden>) on branch: master
Review: https://review.opendev.org/582899"
1790569,2018-09-18 01:36:48 UTC,"Change abandoned by fupingxie (<email address hidden>) on branch: master
Review: https://review.openstack.org/602219"
1790569,2018-09-06 14:00:20 UTC,"From the trace, it looks like conductor was unable to even cast to compute to build the server on the first selected host? But we don't do reschedules/retries within conductor schedule_and_build_instances, unless you have your own patches that does that? Anyway, we need a more clear description of the actual problem."
1790569,2018-09-13 03:17:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/602219"
1790569,2018-09-12 03:28:29 UTC,"@Matt Riedemann, I am so sorry to say that, the LOG in #1 is not exact."
1790569,2018-09-06 13:58:24 UTC,"Can you provide more details on the scenario that's failing? Is this a build reschedule scenario where the first selected host fails to build the server, so it's rescheduled to a second host and is built successfully there, but the allocations are not cleaned up from the first node for some reason?"
1790569,2018-09-04 06:22:23 UTC,"2018-08-27 08:50:38.084 17745 ERROR oslo.messaging._drivers.impl_rabbit [req-7f47bb6e-0dae-4fb2-b8c1-594002df9260 4f2101a461a6470a867278c965b0cde4 2dd72e94503e4222b80ef789ed9b7f99 - default default] Failed to publish message to topic 'nova': 'NoneType' object has no attribute '__getitem__'
2018-08-27 08:50:38.085 17745 ERROR oslo.messaging._drivers.impl_rabbit [req-7f47bb6e-0dae-4fb2-b8c1-594002df9260 4f2101a461a6470a867278c965b0cde4 2dd72e94503e4222b80ef789ed9b7f99 - default default] Unable to connect to AMQP server on 10.127.3.64:5672 after None tries: 'NoneType' object has no attribute '__getitem__'
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server [req-7f47bb6e-0dae-4fb2-b8c1-594002df9260 4f2101a461a6470a867278c965b0cde4 2dd72e94503e4222b80ef789ed9b7f99 - default default] Exception during message handling: MessageDeliveryFailure: Unable to connect to AMQP server on 10.127.3.64:5672 after None tries: 'NoneType' object has no attribute '__getitem__'
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py"", line 163, in _process_incoming
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server     res = self.dispatcher.dispatch(message)
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py"", line 220, in dispatch
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server     return self._do_dispatch(endpoint, method, ctxt, args)
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py"", line 190, in _do_dispatch
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server     result = func(ctxt, **new_args)
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/nova/conductor/manager.py"", line 1200, in schedule_and_build_instances
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server     limits=host['limits'])
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/nova/compute/rpcapi.py"", line 1129, in build_and_run_instance
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server     limits=limits)
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py"", line 152, in cast
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server     self.transport._send(self.target, msg_ctxt, msg, retry=self.retry)
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/transport.py"", line 123, in _send
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server     timeout=timeout, retry=retry)
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 578, in send
2018-08-27 08:50:38.086 17745 ERROR oslo_messaging.rpc.server     retry=retry)
2018-08-27 08:50:38.086 17745..."
1790569,2018-09-13 03:19:31 UTC,"Change abandoned by fupingxie (<email address hidden>) on branch: master
Review: https://review.openstack.org/582899
Reason: refer to https://review.openstack.org/#/c/602219/"
1790581,2018-09-12 15:56:05 UTC,"There are both choosers (Choose Symbol & Choose Footprint) and browsers (Symbol Library Browser, Footprint Library Browser) in both apps."
1790582,2018-09-05 09:25:26 UTC,"Changed settings to ""none"" instead of ""ibus"". Now i'll wait to see if it is
working for a longer time or forever.. :)
I don't understand though why it's not an issue on standard ubuntu but on
budgie..."
1790582,2018-09-04 07:58:35 UTC,The other workaround in that thread is the ibus tweak. Did that work for you?
1790582,2018-09-04 10:43:42 UTC,"I will do a fresh install and i will post an update once i finished. :)
Thanks for the quick reply."
1790582,2018-09-10 10:51:02 UTC,"Since i use the ""none"" settings in the input method, i couldn't reproduce the issue.
If this is the solution, this should be set to ""none"" by default on the OS image, right?"
1790586,2018-10-03 14:54:27 UTC,Not a kernel bug.
1790586,2018-10-16 04:21:16 UTC,"Node lodygin is out-of-order now, need to check this later."
1790586,2018-10-03 14:53:56 UTC,"My guess is lodygin fails to boot from the network, and cycles all the way to booting from Hard drive (0004), in which case, since shim and everything really /are/ installed on disk, it gets run to recreate the missing ""ubuntu"" entry."
1790586,2018-09-19 22:35:26 UTC,"For the AMD node lodygin, I can see this issue again in this cycle with Bionic"
1790586,2019-09-18 08:40:12 UTC,"Didn't see this anymore, and as lodygin is dead, I am closing this bug."
1790586,2018-09-04 15:51:06 UTC,"In theory, you should *never* have an ""ubuntu"" entry in efibootmgr when MAAS-deployed. I'm guessing this is a dup of the following bug, for which a fix has not been backported to trusty:
  https://bugs.launchpad.net/maas/+bug/1642298"
1790586,2018-09-04 11:13:28 UTC,"More test on the AMD Naples amd64 server ""lodygin"" shows:
1. This issue DOES NOT exist with this node deployed with Trusty.
2. This issue DOES exist with this node deployed with Trusty + T-LTS 4.4 kernel.
3. This issue DOES NOT exist with Xenial (no grub package in -proposed)
4. This issue DOES NOT exist with Xenial + X-HWE 4.15 kernel (no grub package in -proposed)
5. This issue DOES exist with this node deployed with Bionic."
1790586,2018-09-04 11:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790586,2018-12-16 04:17:15 UTC,[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]
1790586,2018-09-05 04:05:04 UTC,"From this point I don't think this is a dup as I can see the ""ubuntu"" entry for both of the AMD Naples amd64 server and the TunderX arm64 server, with Bionic:"
1790592,2018-09-04 10:08:21 UTC,tested on Win10 Java 11: works
1790592,2018-09-04 08:21:06 UTC,... not yet tested on Windows with Java 11
1790593,2019-06-14 12:39:55 UTC,Please Please Bump to current Version.
1790594,2018-09-04 08:30:09 UTC,This change was made by a bot.
1790594,2018-09-06 14:15:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1790594,2018-09-08 09:26:52 UTC,"Thanks to owner of the repository we found the solution adding this to the drivers/platform/x86/silead_dmi.c:
First this section
but is optional if i understood right the important things is to have a DMI match:
static const struct property_entry mediacom_w700_props[] = {
 PROPERTY_ENTRY_U32(""touchscreen-size-x"", 884),
 PROPERTY_ENTRY_U32(""touchscreen-size-y"", 632),
 PROPERTY_ENTRY_STRING(""firmware-name"",
         ""gsl1686-surftab-wintron70-st70416-6.fw""),
 PROPERTY_ENTRY_U32(""silead,max-fingers"", 10),
 PROPERTY_ENTRY_BOOL(""silead,home-button""),
 { }
};
The the DMI_MARTCH section:
  {
  /* Mediacom WinPad 7.0 W700 */
  .driver_data = (void *)&surftab_wintron70_st70416_6_data,
  .matches = {
   DMI_MATCH(DMI_SYS_VENDOR, ""MEDIACOM""),
          DMI_MATCH(DMI_PRODUCT_NAME, ""WinPad 7 W10 - WPW700""),
  },
 },"
1790594,2018-09-08 09:31:00 UTC,And you must have the firmware in  /lib/firmware/silead/<your_custom_firmware_name>.fw.
1790594,2018-10-13 15:02:29 UTC,"Thanks to this project https://linuxiumcomau.blogspot.com/2017/06/customizing-ubuntu-isos-documentation.html
I reinstalled the OS with the upgrade kernel option the kernel is now: 4.19.0-041900rc7-generic"
1790595,2019-04-16 18:03:16 UTC,apport information
1790595,2019-04-27 15:16:09 UTC,apport information
1790595,2019-04-27 15:16:08 UTC,apport information
1790595,2019-04-27 15:16:07 UTC,apport information
1790595,2019-04-27 15:16:06 UTC,apport information
1790595,2019-04-27 15:16:05 UTC,apport information
1790595,2019-04-27 15:16:03 UTC,apport information
1790595,2019-04-27 15:16:02 UTC,apport information
1790595,2019-04-17 14:18:56 UTC,"It was
[ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found
[ 165.844742] usb 1-1: selecting invalid altsetting 1"
1790595,2019-04-16 18:04:50 UTC,Same messages with wrong altsetting. Audio device creates but all application freezing when play trough it. No sound on playback an recording.
1790595,2019-04-16 18:39:08 UTC,No the altsetting is correct now. Possible to try it bare metal?
1790595,2019-04-27 15:16:10 UTC,apport information
1790595,2019-04-16 18:03:26 UTC,apport information
1790595,2019-04-16 18:03:24 UTC,apport information
1790595,2019-04-16 18:03:21 UTC,apport information
1790595,2019-04-16 18:03:19 UTC,apport information
1790595,2019-04-16 18:03:18 UTC,apport information
1790595,2019-04-17 13:46:52 UTC,Maybe understanding how the configuration:interface:altsetting:endpoint is arranged on this usb device is helpful.
1790595,2019-04-27 15:16:11 UTC,apport information
1790595,2019-04-27 15:16:16 UTC,apport information
1790595,2019-04-27 15:16:14 UTC,apport information
1790595,2019-09-25 13:02:24 UTC,"The fix for this bug has been applied to Xenial as part of the update for 4.4.187 upstream stable release (bug #1840081), and therefore doesn't need to be verified with this series."
1790595,2019-09-06 13:03:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1790595,2019-09-02 12:26:03 UTC,This bug was fixed in the package linux - 4.15.0-60.67
1790595,2019-08-27 13:15:15 UTC,This bug was fixed in the package linux - 5.2.0-13.14
1790595,2019-08-22 16:15:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1790595,2019-08-15 15:27:18 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1790595,2019-07-18 09:54:23 UTC,"Let's fix the wrong altsetting first:
https://lkml.org/lkml/2019/7/18/227"
1790595,2019-04-27 15:24:35 UTC,"Sorry for late answer. Still no luck with driver even on bare metal. Warning ""config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64"" still present. Now this driver creates two audio interfaces. Try to play through both by pulseaudio and alsa, no system freezing like in previous times but, no sound playing through phones on hdpod, and no sound recorded on notebook."
1790595,2019-04-27 15:16:25 UTC,apport information
1790595,2019-04-27 15:16:23 UTC,apport information
1790595,2019-04-27 15:16:21 UTC,apport information
1790595,2019-04-27 15:16:20 UTC,apport information
1790595,2019-04-27 15:16:19 UTC,apport information
1790595,2019-04-27 15:16:18 UTC,apport information
1790595,2019-04-27 15:16:17 UTC,apport information
1790595,2019-04-16 18:03:15 UTC,apport information
1790595,2019-04-27 15:16:15 UTC,apport information
1790595,2019-04-27 15:16:13 UTC,apport information
1790595,2019-04-16 18:03:14 UTC,apport information
1790595,2018-09-10 16:40:45 UTC,apport information
1790595,2018-09-07 16:37:10 UTC,apport information
1790595,2018-09-06 14:17:05 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1790595,2018-09-04 16:19:28 UTC,apport information
1790595,2018-09-04 16:19:26 UTC,apport information
1790595,2018-09-04 16:19:25 UTC,apport information
1790595,2018-09-04 16:19:23 UTC,apport information
1790595,2018-09-04 16:19:22 UTC,apport information
1790595,2018-09-04 16:19:20 UTC,apport information
1790595,2018-09-10 16:40:46 UTC,apport information
1790595,2018-09-04 16:19:18 UTC,apport information
1790595,2018-09-04 16:19:15 UTC,apport information
1790595,2018-09-04 16:19:13 UTC,apport information
1790595,2018-09-04 16:19:11 UTC,apport information
1790595,2018-09-04 16:19:10 UTC,apport information
1790595,2018-09-04 16:19:08 UTC,apport information
1790595,2018-09-04 16:19:06 UTC,apport information
1790595,2018-09-04 16:19:04 UTC,apport information
1790595,2018-09-04 16:19:16 UTC,apport information
1790595,2018-09-07 16:37:11 UTC,apport information
1790595,2018-09-07 16:53:01 UTC,"Same error with v4.19-rc2. I run apport-collect with v4.19, it create only two posts after you."
1790595,2018-09-10 16:40:19 UTC,apport information
1790595,2018-09-10 16:40:43 UTC,apport information
1790595,2018-09-10 16:40:41 UTC,apport information
1790595,2018-09-10 16:40:40 UTC,apport information
1790595,2018-09-10 16:40:39 UTC,apport information
1790595,2018-09-10 16:40:38 UTC,apport information
1790595,2018-09-10 16:40:37 UTC,apport information
1790595,2018-09-10 16:40:35 UTC,apport information
1790595,2018-09-04 16:19:02 UTC,apport information
1790595,2018-09-10 16:40:33 UTC,apport information
1790595,2018-09-10 16:40:30 UTC,apport information
1790595,2018-09-10 16:40:27 UTC,apport information
1790595,2018-09-10 16:40:26 UTC,apport information
1790595,2018-09-10 16:40:25 UTC,apport information
1790595,2018-09-10 16:40:24 UTC,apport information
1790595,2018-09-10 16:40:22 UTC,apport information
1790595,2018-09-10 16:40:20 UTC,apport information
1790595,2018-09-10 16:40:31 UTC,apport information
1790595,2018-09-04 08:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790598,2018-11-19 15:55:33 UTC,"The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1790598,2019-01-17 06:42:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/631434"
1790598,2018-11-08 17:18:00 UTC,Regression testing was successful against xenial-proposed:
1790598,2018-11-08 17:18:56 UTC,Sorry the first set of testing above was against bionic-proposed not xenial-proposed.
1790598,2019-01-19 00:32:49 UTC,"Reviewed:  https://review.openstack.org/631434
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1685982a97f1bc82698724eb9a47e92416dc0aac
Submitter: Zuul
Branch:    master"
1790598,2018-11-06 20:52:03 UTC,"Hello James, or anyone else affected,"
1790598,2019-01-21 12:36:39 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/632076"
1790598,2019-01-23 07:14:48 UTC,"Reviewed:  https://review.openstack.org/632072
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9f003cf497fd4f4ffcdd5c633824531b465aa69c
Submitter: Zuul
Branch:    stable/rocky"
1790598,2019-06-15 02:56:06 UTC,"Reviewed:  https://review.opendev.org/599541
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ae542f685466dc65967c6d74d38d8935685256f5
Submitter: Zuul
Branch:    stable/queens"
1790598,2019-06-18 22:11:01 UTC,"Reviewed:  https://review.opendev.org/632076
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4091dc33d7172a7ae6333ae29c1f0620aa50c400
Submitter: Zuul
Branch:    stable/queens"
1790598,2019-07-04 10:23:40 UTC,This issue was fixed in the openstack/neutron 12.1.0 release.
1790598,2019-01-21 11:59:26 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/632072"
1790598,2018-11-06 06:08:55 UTC,This issue was fixed in the openstack/neutron 13.0.2 release.
1790598,2018-11-19 16:05:34 UTC,This bug was fixed in the package neutron - 2:12.0.5-0ubuntu1
1790598,2018-10-15 09:30:20 UTC,Looks like this bug is verified but not marked as verification-done-bionic. Is there any more testing you want to perform on this bug before release?
1790598,2018-10-10 15:40:51 UTC,Regression testing successful for queens-proposed (tempest results):
1790598,2018-10-10 14:01:19 UTC,Regression testing successful for bionic-proposed (tempest results):
1790598,2018-10-05 13:14:59 UTC,"Hello James, or anyone else affected,"
1790598,2018-10-03 13:58:21 UTC,Neutron 2:12.0.4-0ubuntu1 is now ready for review in the unapproved queue.
1790598,2018-10-02 22:38:45 UTC,"An upload of neutron to bionic-proposed has been rejected from the upload queue for the following reason: ""coreycb said he was going to add some more patches in #ubuntu-devel.""."
1790598,2018-10-02 22:37:30 UTC,"As an FYI the ""Regression Potential"" part of the SRU description is supposed to be about how things can go wrong not a statement regarding the chances of their being a regression."
1790598,2018-10-02 12:25:15 UTC,"The stable/queens fix has been included in neutron 2:12.0.4-0ubuntu1, currently in the bionic unapproved queue awaiting SRU team review."
1790598,2018-09-18 02:26:49 UTC,"Reviewed:  https://review.openstack.org/599537
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c28e4963b75414f093e432c9934f8658a4e56b98
Submitter: Zuul
Branch:    stable/rocky"
1790598,2018-09-05 09:30:29 UTC,This bug was fixed in the package neutron - 2:13.0.0-0ubuntu2
1790598,2018-09-04 09:27:00 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/599541"
1790598,2018-09-04 09:06:17 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599537"
1790598,2018-10-15 12:57:22 UTC,I checked with jamespage and he said regression is enough for verifying this. Tagged as verified.
1790608,2020-09-03 20:15:42 UTC,"@OlivierS 20.04 has .deb LibreOffice (6.4.5), so there's no need to worry just yet. You can install it directly with apt. No need to use an external PPA."
1790608,2020-09-03 20:03:53 UTC,"I installed Ubuntu 20.04 on my daughters laptop. She had no problems with the previous Ubuntu, but this bug is too hard for an ordinary user to fix. She opens a document from Firefox to Libreoffice, and the document doesn't exist. Since those two applications are most important to her, it makes the laptop unusable. This is such a big usability problem this should really not have become part of Ubuntu 20.04."
1790608,2019-12-29 15:29:13 UTC,"I had also the same problem. LibreOffice (6.3.4.2 snap1), installed by ""Ubuntu Software"" on Ubuntu 18.04 could not open documents attached to e-mails (Thunderbird) and even those on the web. It had also problems in linking with Zotero. I removed it completely and installed the one from the LibreOffice site (https://www.libreoffice.org/donate/dl/deb-x86_64/6.3.4/en-US/LibreOffice_6.3.4_Linux_x86-64_deb.tar.gz). LibreOffice now works without any problem, and it opens much faster."
1790608,2018-09-06 10:58:11 UTC,This is a known issue with no solution as of today: https://forum.snapcraft.io/t/sharing-files-via-tmp/1613
1790608,2018-09-26 11:19:57 UTC,"Sorry for just being a random barely technical user, but...
Is there any hope in the following?
https://forum.snapcraft.io/t/allowing-xdg-open-to-open-files/3789/6"
1790608,2019-11-02 17:17:35 UTC,"This is also happening to me, but I don't have a snap version installed, I don't even know what that is."
1790622,2018-09-12 15:10:44 UTC,"That's exactly the issue I've also describing in https://bugs.launchpad.net/tripleo/+bug/1788875, it seems! This is really confusing, especially for side users trying tripleo quickstart."
1790624,2019-01-16 22:07:37 UTC,"Thank you for your bug report. How is the sftp mounting done? Do you use the gvfs location or a fuse mount or similar? Can you access/Read from that mount using e.g nautilus when rhythmbox is blocking?
In any case that's probably an upstream issue and should be reported on https://gitlab.gnome.org/GNOME/rhythmbox/issues/new"
1790627,2018-09-14 17:37:08 UTC,Thanks for submitting the bug. ironic doesn't use launchpad anymore. I 'ported' this over to Storyboard: https://storyboard.openstack.org/#!/story/2003780.
1790627,2018-09-16 05:59:59 UTC,Thank Ruby
1790628,2018-09-12 12:29:46 UTC,Domain-less external/network lookups are not supported.
1790632,2019-09-19 12:06:24 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1790632,2018-09-04 18:03:01 UTC,I looked through the logs and (as you imply) it isn't totally clear what the issue might be.
1790632,2018-09-05 04:31:25 UTC,"Mike, thanks for the detailed look! I initially suspected duplicate MAC because we do see that from time to time on 2.3.x. It's been fixed in newer builds. However, this one didn't have any of the known signatures. Unfortunately, there isn't a lot to go on. Thankfully, this is a one of a kind failure so far. But, I think it speaks to the value of having console logging enabled for pod machines, which would help determine what was happening here and on other sporadic issues."
1790633,2018-09-06 06:27:05 UTC,"To resolve my issue, I created a new user, moved my ~/.kde/ ~/.config/ and ~/.cache/ out of the way, copied over the ~newuser/.kde/ and ~/newuser/.config/, and reconfigured the desktop by hand."
1790633,2018-09-05 16:41:31 UTC,"Update: a better workaround is running from VT2 `pkill -sigint screenlocker`, which make the password widget visible, and the screen unlock-able."
1790633,2018-09-05 15:49:10 UTC,"Update: a better workaround is running from VT2 `pkill -sigint screenlocker`, which make the password widget visible, and the screen unlock-able."
1790633,2018-09-05 15:29:03 UTC,I was able to reproduce this behavior with running manually /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
1790633,2018-09-05 15:39:46 UTC,Update: sending sigint to the kscreenlock_greet made it trhow a message on screen that instructed me to run `loginctl unlock-session 3` which did unlocked the my screen.
1790635,2018-09-04 13:51:51 UTC,The apache error logs on the keystone units are likely important:
1790635,2018-09-04 13:52:23 UTC,"The BadStatusLine error in the pastebin is because of a broken socket, and if something is causing apache to constantly restart then this would be expected."
1790635,2018-09-04 14:01:06 UTC,rally output
1790637,2018-09-04 13:57:17 UTC,It appears the problem is when using --provide
1790637,2019-06-07 20:26:39 UTC,Should be fixed here - https://review.opendev.org/#/c/640803/
1790639,2018-11-24 17:17:40 UTC,"Hello.
I had the same problem as you. Then i found that qpdfview has another default shortcut to go to the next occurence: Ctrl+G. In Edit> Settings> Shortcuts you can see the shortcuts list. And you can customize them."
1790647,2018-09-06 10:22:11 UTC,"PR: https://github.com/juju/juju/pull/9172
Discourse Post: https://discourse.jujucharms.com/t/ec2-instance-types/223"
1790647,2018-10-01 14:41:31 UTC,"We should consider re-looking at this for 2.5, as the instances that we currently use for default controllers (et al) are being phased out and we should really consider using the new aws instance types."
1790647,2019-03-22 01:33:27 UTC,I am pretty sure that this has been forward ported to develop and 2.6
1790651,2019-08-05 13:12:55 UTC,Potential fix PR @ https://github.com/snapcore/snapcraft/pull/2653
1790664,2018-09-04 15:09:16 UTC,"Please include the *.network, *.netdev, *.link files from /etc/systemd/network or /run/systemd/network as well for the configuration, after making sure you sanitized them if there are any information (IPs?) that you don't want public."
1790664,2018-09-04 15:35:35 UTC,"Hi,"
1790672,2019-08-09 13:39:33 UTC,Duplicate of https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1768369
1790672,2019-08-09 13:39:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790686,2018-09-04 17:23:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599701"
1790686,2018-09-05 11:01:55 UTC,"Change abandoned by Victor Palma (<email address hidden>) on branch: master
Review: https://review.openstack.org/599701
Reason: According to documentation DNS is still available if needed I can provide another patch that add dns domain ports."
1790686,2020-11-03 16:35:05 UTC,"Fix released and backported to Rocky.
https://review.opendev.org/#/c/624097/"
1790688,2018-10-19 16:06:36 UTC,"Hello. I would like to note, that ""Meltdown"" mitigation - for i386 architecture - among others improvements, is already available in OpenBSD 6.4 release (see ""Security improvements"" section [in:] https://www.openbsd.org/64.html)."
1790688,2018-09-04 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790688,2018-09-04 17:40:37 UTC,Hello.
1790688,2019-06-17 15:57:08 UTC,"PTI makes my 2 32 bit laptops unstable. I have lubuntu 18.04 installed on both and they both started having trouble after the linux-image upgrade from 4.15.0-46/47 to 4.15.0-50/51. They either fail to boot without locking up or fail to shut down cleanly. I rarely get any useful logs or messages on the screen, although if the machines do boot without locking up, I have seen messages like this when they fail to shut down:
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
1790688,2019-07-23 16:59:41 UTC,Hello H Buus.
1790695,2019-03-22 03:47:50 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1790695,2018-09-07 05:39:05 UTC,"Reviewed:  https://review.openstack.org/599861
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a4f1274f40513d0a350a38c6e389c9a76c272379
Submitter: Zuul
Branch:    master"
1790695,2018-09-04 22:30:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599861"
1790701,2018-09-21 09:20:40 UTC,"Reviewed:  https://review.openstack.org/600464
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7f25c3e6072c2f892de740038e7d076b24fc09f7
Submitter: Zuul
Branch:    stable/rocky"
1790701,2018-09-05 14:41:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/600085"
1790701,2018-09-07 13:15:34 UTC,"Reviewed:  https://review.openstack.org/599744
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=63c10d2d536c3ffed68ccfb6bd393f317111d903
Submitter: Zuul
Branch:    master"
1790701,2018-09-06 15:08:11 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/600464"
1790701,2018-09-04 20:06:03 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/599822
Reason: Squashed into https://review.openstack.org/#/c/599744/"
1790701,2018-09-04 20:00:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599822"
1790701,2018-09-04 18:58:56 UTC,Note that this also points out that there's a placement db online migration in the nova online migrations (using code from nova/api/openstack/placement/objects ) which we're going to need address at some point soonish.
1790701,2018-09-04 18:55:30 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/599744"
1790701,2018-09-04 18:52:13 UTC,Looks like this was the regression:
1790701,2018-09-04 18:45:05 UTC,still exits 0 though
1790701,2018-09-24 14:46:51 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1790701,2019-03-22 03:47:46 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1790701,2018-10-05 14:02:25 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/600085
Reason: https://review.openstack.org/#/c/608091/"
1790705,2018-09-04 18:55:44 UTC,"Ultimately, this creates a check_haproxy UNKNOWN result in nagios."
1790709,2020-11-30 09:55:20 UTC,The version of syslinux in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1790709,2019-07-23 19:29:21 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1790709,2019-04-23 09:27:32 UTC,This bug was fixed in the package syslinux - 3:6.04~git20171011.af7e95c3+dfsg1-4ubuntu1.18.10.2
1790709,2019-04-16 18:46:54 UTC,syslinux 3:6.04~git20171011.af7e95c3+dfsg1-4ubuntu1.18.10.2 verification-done in cosmic:
1790709,2019-02-18 15:43:13 UTC,"Hello Mathieu, or anyone else affected,"
1790709,2019-02-18 15:42:16 UTC,"Hello Mathieu, or anyone else affected,"
1790709,2019-01-15 18:56:09 UTC,"Hello Mathieu, or anyone else affected,"
1790709,2019-01-09 15:41:19 UTC,"Fixing is required in cosmic as well since the issue is with the patch used for gnu-efi 3.0.8 support. Disco is ""unaffected""; I've synced with Debian which has already fixed the issue."
1790709,2018-12-04 16:02:55 UTC,Looks like there are some cases where syslinux will fail to load modules with the proposed rebuild patch with the new gnu-efi. This is a regression in syslinux; marking as verification-failed.
1790709,2018-10-22 08:09:03 UTC,The verification-done-bionic tag has not been re-set after the syslinux package has been accepted. Did all the validation steps have been performed for the package after it has been re-built? I see the test-case defines some functionality tests - are those also required in this case?
1790709,2018-10-12 20:51:18 UTC,"Hello Mathieu, or anyone else affected,"
1790709,2018-09-05 06:21:37 UTC,"Hello Mathieu, or anyone else affected,"
1790709,2018-09-13 08:22:33 UTC,This bug was fixed in the package gnu-efi - 3.0.8-0ubuntu1~16.04.1
1790709,2018-09-12 21:10:26 UTC,shouldn't syslinux also get a versioned build-dependency on gnu-efi for this?
1790709,2018-09-12 21:09:13 UTC,This bug was fixed in the package gnu-efi - 3.0.8-0ubuntu1~18.04.1
1790709,2018-09-12 21:08:53 UTC,"The verification of the Stable Release Update for gnu-efi has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1790709,2018-09-11 21:11:40 UTC,"Rebuilds in PPA have all passed -- the failures for efitools are exactly the same as they previously were and due to EFI not being available (or sbsigntool, efivar, etc.) on those architectures:"
1790709,2018-09-07 21:21:33 UTC,This bug was fixed in the package syslinux - 3:6.04~git20171011.af7e95c3+dfsg1-4ubuntu1
1790709,2018-09-05 06:25:33 UTC,"Hello Mathieu, or anyone else affected,"
1790709,2018-09-05 06:18:53 UTC,"Hello Mathieu, or anyone else affected,"
1790709,2018-09-04 19:25:03 UTC,syslinux in bionic and newer need a small fix to avoid FTBFS now that gnu-efi provides memset() and memcpy().
1790709,2018-09-13 08:23:30 UTC,This bug was fixed in the package gnu-efi - 3.0.8-0ubuntu1~14.04.1
1790711,2018-09-05 13:47:15 UTC,https://status.snapcraft.io/
1790711,2019-07-03 20:49:44 UTC,Moved to 1835305.
1790713,2020-01-29 19:57:59 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/704876"
1790713,2020-02-03 20:54:13 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/705553"
1790713,2020-01-29 20:14:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/704877"
1790713,2020-02-03 20:55:41 UTC,"Change abandoned by Sofia Enriquez (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/704876
Reason: Abandon because the Change-Id is wrong. Continue here https://review.opendev.org/705553/"
1790713,2020-04-03 14:51:52 UTC,This issue was fixed in the openstack/cinder 14.0.4 release.
1790713,2020-02-04 14:56:16 UTC,"Change abandoned by Sofia Enriquez (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/704877
Reason: Wrong change-id continue in https://review.opendev.org/#/c/705703/"
1790713,2020-02-12 16:32:32 UTC,"Reviewed:  https://review.opendev.org/705553
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=bef90868971118dcced47a64f3bbffc7f2732db7
Submitter: Zuul
Branch:    stable/stein"
1790713,2020-02-22 03:44:11 UTC,"Reviewed:  https://review.opendev.org/705703
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=bce6d01e153100681540d29496d2332c45b53eb3
Submitter: Zuul
Branch:    stable/rocky"
1790713,2020-03-04 02:14:48 UTC,This issue was fixed in the openstack/cinder 13.0.9 release.
1790713,2020-02-04 14:54:52 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705703"
1790713,2019-12-10 13:19:32 UTC,"Hi Giuseppe, Since this patch was considered a new feature and has a release note, I think a backport to queens won't be accepted."
1790713,2019-09-06 16:26:05 UTC,"Reviewed:  https://review.opendev.org/627941
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=5018727f8e18992e64c55b84f0d5b39ae7c70b32
Submitter: Zuul
Branch:    master"
1790713,2019-09-27 09:03:20 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1790713,2019-08-20 18:56:20 UTC,"Any updates on this issue? Still not fixed in 14.0.0.
It makes it impossible to rotate backups and have any sane backup policy."
1790713,2019-06-05 08:00:38 UTC,Any news here?
1790713,2019-03-21 17:22:22 UTC,This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.
1790713,2019-01-16 18:34:47 UTC,"Change abandoned by Sofia Enriquez (<email address hidden>) on branch: master
Review: https://review.openstack.org/628066
Reason: As @Rajat Dhasmana said, I close this patch to merge with @wanghao [1]."
1790713,2019-01-02 23:00:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/628066"
1790713,2018-12-11 14:56:27 UTC,The above change was reverted here:
1790713,2018-12-07 07:45:10 UTC,"Reviewed:  https://review.openstack.org/612503
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=797c5aa78574a29a9a0bf7dd1b8adb47554b42c2
Submitter: Zuul
Branch:    master"
1790713,2018-10-22 20:56:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612503"
1790713,2019-12-10 12:05:05 UTC,This bug is affecting a customer in Canonical Bootstack.
1790721,2018-09-07 13:15:30 UTC,"Reviewed:  https://review.openstack.org/599744
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=63c10d2d536c3ffed68ccfb6bd393f317111d903
Submitter: Zuul
Branch:    master"
1790721,2018-09-20 15:18:57 UTC,"Reviewed:  https://review.openstack.org/600098
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f588a0b6c337368596bc8732141e864f56f72212
Submitter: Zuul
Branch:    stable/rocky"
1790721,2018-09-21 09:20:37 UTC,"Reviewed:  https://review.openstack.org/600464
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7f25c3e6072c2f892de740038e7d076b24fc09f7
Submitter: Zuul
Branch:    stable/rocky"
1790721,2019-03-22 03:47:47 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1790721,2018-09-26 01:23:47 UTC,"Reviewed:  https://review.openstack.org/600101
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6a806de71b945509c8c5d3de53ff7ba5aa75bf87
Submitter: Zuul
Branch:    stable/queens"
1790721,2018-10-02 10:32:59 UTC,"Reviewed:  https://review.openstack.org/600113
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3f562226112b99d2044dd05a2e15b9752d5c9c1d
Submitter: Zuul
Branch:    stable/pike"
1790721,2018-09-06 15:08:07 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/600464"
1790721,2018-09-24 14:46:52 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1790721,2018-09-05 16:51:14 UTC,"Reviewed:  https://review.openstack.org/599875
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dcd421ae9e6f0391fea06c9d20949267354c3b3c
Submitter: Zuul
Branch:    master"
1790721,2018-10-02 21:30:34 UTC,"Reviewed:  https://review.openstack.org/600119
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ff8cb33283bbce474426f20f21675ecc1449b4d7
Submitter: Zuul
Branch:    stable/ocata"
1790721,2018-09-05 16:15:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/600113"
1790721,2018-09-05 15:42:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/600101"
1790721,2018-09-05 15:38:03 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/600098"
1790721,2018-09-05 01:00:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599875"
1790721,2018-09-05 00:37:11 UTC,"Ah I think I know what's happening, the else block on this for loop is busted:"
1790721,2018-09-05 00:15:12 UTC,The devstack change didn't fail because when nova-status upgrade check runs it's not seeing any compute nodes in the cell databases:
1790721,2018-09-04 20:58:40 UTC,Here is a devstack patch that runs nova-status upgrade check which should show this same warning and actually make devstack fail:
1790721,2018-09-04 20:36:42 UTC,"I suspect this is a similar regression as bug 1790701 in that the count for resource providers is using the placement DB API context manager from https://review.openstack.org/#/c/541435/ but the placement DB API context manager is not properly configured for the API DB, so it's likely just hitting the cell0 DB where there are no resource providers."
1790721,2018-09-05 16:23:42 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/600119"
1790722,2018-09-05 12:27:00 UTC,Hi Rowan!
1790724,2018-10-09 19:30:12 UTC,Verification-done with shim 15+1533136590.3beb971-0ubuntu1 / shim-signed 1.37~18.04.2:
1790724,2019-01-14 08:48:11 UTC,Hey! Is this a typo that the version number of shim-signed is 1.33.1~16.04.2+15+1533136590.3beb971-0ubuntu1 ? I'd expect it to be 16.04.3 instead of 16.04.2. Could you just please confirm that the right version was tested?
1790724,2019-01-09 14:52:22 UTC,Verification done on xenial:
1790724,2018-12-11 22:55:34 UTC,"Hello Mathieu, or anyone else affected,"
1790724,2018-11-01 20:31:52 UTC,The blocking bug is LP: #1792575.
1790724,2018-11-01 20:29:13 UTC,this has been temporarily rolled back from xenial because of the need for a matching grub update first.
1790724,2018-11-01 19:02:00 UTC,This bug was fixed in the package shim-signed - 1.33.1~16.04.2
1790724,2018-11-01 18:48:53 UTC,Verification done on xenial:
1790724,2019-01-21 15:56:31 UTC,This bug was fixed in the package shim-signed - 1.33.1~16.04.3
1790724,2018-10-11 07:34:08 UTC,This bug was fixed in the package shim-signed - 1.37~18.04.2
1790724,2019-01-17 14:39:17 UTC,"It is indeed a typo, I copy-pasted the previous comment about verification (since it was the exact same thing, but indeed verified with 1.33.1~16.04.3+15+1533136590.3beb971-0ubuntu1 which includes the added depends for grub2."
1790724,2018-10-01 16:33:08 UTC,"Hello Mathieu, or anyone else affected,"
1790724,2018-09-14 19:45:10 UTC,Regression reported: https://bugs.launchpad.net/maas/+bug/1711203
1790724,2018-09-18 07:58:40 UTC,"Not a regression in shim -- shim is doing what it should, but exposes an actual latent bug in the grub2 EFI patchset. This is still in progress."
1790724,2018-09-14 19:46:57 UTC,"sorry, https://bugs.launchpad.net/maas/+bug/1711203 is not the right bug for this regression."
1790724,2018-09-14 19:43:25 UTC,This SRU has been rolled back due to functional regressions that have been reported when chainloading from shim 15 to shim 13 in MAAS.  Investigation is ongoing.
1790724,2018-09-12 21:09:19 UTC,This bug was fixed in the package shim-signed - 1.37~18.04.1
1790724,2018-09-12 21:09:16 UTC,"The verification of the Stable Release Update for shim-signed has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1790724,2018-09-11 22:47:23 UTC,"Hello Mathieu, or anyone else affected,"
1790724,2018-09-11 18:34:08 UTC,"Verification-done for shim, shim-signed on bionic:"
1790724,2018-09-06 22:21:07 UTC,"Hello Mathieu, or anyone else affected,"
1790724,2018-09-04 22:02:26 UTC,shim and shim-signed 15 / 1.37 are already in Cosmic.
1790724,2018-09-25 20:00:50 UTC,Re-release of this SRU is currently blocked on resolution of LP: #1792575 in grub2.
1790727,2019-04-24 23:38:13 UTC,"Removing pullrequest tag here -- I've got a screen in the booking refresh that is really similar to this view.  The booking refresh is in modern Angular, rather than AngularJS, too, so it would be better to simply improve the booking refresh screen."
1790727,2019-02-06 21:31:32 UTC,Just a note that I pushed a small commit to that branch to catch some reservations that weren't previously appearing in this view.
1790727,2019-02-20 16:59:28 UTC,"I have tested this code and consent to signing off on it with my name, Christine Burns and my email address, <email address hidden>"
1790727,2018-10-23 20:30:14 UTC,Just a note that I pushed another small commit to the branch to make sure that canceled reservations aren't included.
1790727,2019-02-20 19:18:11 UTC,"Thanks for your testing, Christine!  I added a new working branch that squashes my commits, rebases against master, and includes Christine's sign off: user/sandbergja/lp1790727_booking_daily_schedule_final"
1790727,2018-09-27 04:49:22 UTC,"Here's a rebased branch, with two small fixes: user/sandbergja/lp1790727_booking_daily_schedule_for_feedback_rebased"
1790727,2018-09-04 22:36:47 UTC,The branch is called lp1790727_booking_daily_schedule_for_feedback
1790727,2018-10-09 21:42:02 UTC,"The Student Success Working Group took a look at this today, and were pretty positive about it!  I think that this branch is now ready for testing."
1790733,2018-09-04 23:27:39 UTC,"Could you provide some more info please? Distro, release, etc."
1790733,2018-09-05 14:58:04 UTC,"Wild guess based on looking at the code in aa.py set_logfile(): Either you don't have /etc/apparmor/logprof.conf, or the file doesn't have ""logfiles = ..."" in the ""[settings]"" section."
1790739,2018-09-06 18:00:47 UTC,"I tested with 3.13.0-158-generic (from proposed updates) and the problem persists, like for 13.0-157-generic .
It does not happen with 3.13.0-155."
1790739,2018-09-06 15:45:05 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1790739,2018-09-05 00:32:26 UTC,"The problem seems to happen only if the ext2 block size is 1024, which seems to be the default for a filesystem smaller than 537 MB."
1790739,2018-09-04 23:23:44 UTC,I was able to reproduce this issue on multiple hosts.
1790739,2018-09-04 23:30:06 UTC,This change was made by a bot.
1790746,2019-02-12 13:27:06 UTC,Are you still having this issue? We would need the relevant mistral logs in order to be able to debug this.
1790746,2019-05-19 04:17:36 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1790747,2018-09-06 12:48:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790750,2018-09-19 16:20:45 UTC,"Reviewed:  https://review.openstack.org/599882
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c6960e8acc6892c75811625091ce4cdf4024c464
Submitter: Zuul
Branch:    stable/queens"
1790750,2018-10-08 21:49:19 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1790750,2018-10-02 22:16:21 UTC,"Reviewed:  https://review.openstack.org/599885
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c59453bf84cb49f8bb2c7d08af2c8355bb5b8ad2
Submitter: Zuul
Branch:    stable/ocata"
1790750,2018-09-24 14:46:56 UTC,This issue was fixed in the openstack/nova 18.0.1 release.
1790750,2018-09-24 14:46:50 UTC,This issue was fixed in the openstack/nova 17.0.6 release.
1790750,2018-09-24 14:46:33 UTC,This issue was fixed in the openstack/nova 16.1.5 release.
1790750,2019-03-22 03:47:49 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1790750,2018-09-13 23:35:57 UTC,"Reviewed:  https://review.openstack.org/599881
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c09190996923449f4a64905d696c5b7e92841d3b
Submitter: Zuul
Branch:    stable/rocky"
1790750,2018-09-20 19:14:10 UTC,"Reviewed:  https://review.openstack.org/599883
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=37722c7f4f6df433489a62a19c318dceb4739d08
Submitter: Zuul
Branch:    stable/pike"
1790750,2018-09-05 01:27:52 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/599885"
1790750,2018-09-05 01:26:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/599883"
1790750,2018-09-05 01:25:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/599882"
1790750,2018-09-05 01:24:10 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/599881"
1790750,2018-09-05 01:13:15 UTC,No sqlalchamy expert but using table.name produced the correct name and worked.
1790750,2018-09-05 01:09:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599878"
1790750,2018-09-05 16:51:27 UTC,"Reviewed:  https://review.openstack.org/599878
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d0657f4acf30f77ae978bf95a9d7ce76fe97a56c
Submitter: Zuul
Branch:    master"
1790751,2021-02-17 17:09:26 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1790751,2019-07-31 18:16:10 UTC,"Is this bug still an issue/concern?  The following is a list I get on an undercloud installation on a single VM, and the only similarly named image is ""tempest"":"
1790751,2018-09-05 22:35:08 UTC,I'm not sure they are unnecessary as they could be used if a person enables the configs.  These are technically services that can be enabled on the undercloud so I'm not sure this is any worse than what we used to do on the overcloud images by pre-installing all of the rpms.  They likely share a bunch of common layers so I'm not sure the actual size is an issue either
1790751,2018-09-06 19:42:55 UTC,Yes I don't think this really impacts end users. I think it is still worth fixing just for CI speed reasons.
1790756,2018-09-05 13:46:44 UTC,We need to allow the 'rhel' os_variant into the case statement for centos and redhat during grub install.
1790756,2018-09-06 06:29:26 UTC,I've verified the latest branch fixes RHEL. Feel free to close.
1790762,2018-10-20 14:47:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790771,2018-09-05 05:23:49 UTC,"I am sorry I forget to tell that I use ubuntu 18.04,"
1790771,2018-09-10 18:53:09 UTC,This bug was fixed upstream in libmongoc 1.10.0. See the discussion here:
1790771,2018-09-13 12:43:16 UTC,Thanks for the update.
1790788,2019-06-25 07:53:05 UTC,With the changed focus from xenial to bionic - the xenial entry is now set to Won't Fix.
1790788,2019-03-08 13:55:25 UTC,SRU justification added - see bug description
1790788,2019-05-20 09:21:33 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.1
1790788,2019-05-20 08:46:37 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.10.1
1790788,2019-04-30 10:07:52 UTC,"Adjusting the bionic-verification tag, since I was able to successfully verify the package from bionic-proposed, too."
1790788,2019-04-30 10:06:53 UTC,"Adjusting the cosmic-verification tag, since I was able to successfully verify the package from cosmic-proposed."
1790788,2019-04-29 16:20:21 UTC,"Hello Frank, or anyone else affected,"
1790788,2019-04-29 16:09:13 UTC,"Hello Frank, or anyone else affected,"
1790788,2019-03-28 18:46:48 UTC,"Our makedumpfile updates are waiting for us to get approval for micro release updates. I am working on the justification so we can get exceptions for this and future updates, as makedumpfile is closely tied to the kernel version."
1790788,2019-03-08 09:31:26 UTC,"needs SRU template, test case etc"
1790788,2019-05-20 08:46:49 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1790788,2018-12-18 13:30:48 UTC,I am working on the merge of Debian and Ubuntu changes to Disco.
1790788,2019-01-18 18:21:25 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1
1790788,2018-09-05 07:13:57 UTC,For your testing here the default content of zipl.conf on a cloud-img KVM guest
1790788,2018-09-05 07:14:20 UTC,This is also the reason for all the fails in [1] which actually flags a real issue as reported in this bug
1790788,2018-09-05 07:13:03 UTC,"Ack to the report.
While I had some systems (lpar) which worked I was trivially able to confirm that it doesn't work on KVM guests based on cloud images."
1790788,2018-09-05 07:27:05 UTC,Assigned the task on request by JFH
1790788,2018-09-05 12:59:32 UTC,Adding a sample zipl.conf of an LPAR installation - just for reference:
1790788,2018-10-17 12:12:50 UTC,"This fix has been uploaded to Debian, and will be synced to 19.04 when it opens. After that, it will be backported to cosmic, bionic and xenial."
1790788,2018-09-05 07:17:13 UTC,Note: this also affects the makedumpfile autopkgtest
1790790,2018-10-12 22:25:51 UTC,I can confirm this.
1790790,2018-11-02 06:30:31 UTC,"Could anyone of you provide the environment details you are using like,
which OS (other than mentioned), which python version these tests are failing?"
1790790,2018-11-02 12:17:31 UTC,"Hi Abhishek Kekane,"
1790798,2018-09-05 07:58:04 UTC,Bug #1790803 is a duplicate that contains another set of logs from when I reproduced the problem.
1790798,2018-09-05 22:04:32 UTC,I was able to work around this by manually copying .efi files into /boot/efi/EFI/ubuntu and setting up a grub.cfg in there.
1790799,2018-09-05 16:21:48 UTC,"Exception during installation:
Sep  5 10:36:21 custom plugininstall.py: Traceback (most recent call last):
Sep  5 10:36:21 custom plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 1730, in <module>
Sep  5 10:36:21 custom plugininstall.py:     install.run()
Sep  5 10:36:21 custom plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 55, in wrapper
Sep  5 10:36:21 custom plugininstall.py:     func(self)
Sep  5 10:36:21 custom plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 200, in run
Sep  5 10:36:21 custom plugininstall.py:     self.install_extras()
Sep  5 10:36:21 custom plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 1257, in install_extras
Sep  5 10:36:21 custom plugininstall.py:     self.do_install(install_misc.query_recorded_installed())
Sep  5 10:36:21 custom plugininstall.py:   File ""/usr/lib/ubiquity/ubiquity/install_misc.py"", line 856, in do_install
Sep  5 10:36:21 custom plugininstall.py:     with Cache() as cache:
Sep  5 10:36:21 custom plugininstall.py: AttributeError: __exit__
Sep  5 10:36:21 custom plugininstall.py:"
1790801,2018-09-10 06:36:42 UTC,"Hello,
Thanks for your reply."
1790801,2019-04-10 09:28:57 UTC,Does this still happen to your system?
1790801,2018-09-06 15:43:16 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1790801,2018-09-10 06:39:37 UTC,"status:	 Confirmed
tags:	'kernel-bug-exists-upstream'."
1790801,2018-09-05 08:12:07 UTC,apport information
1790801,2018-09-05 08:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790801,2018-09-05 08:12:08 UTC,apport information
1790809,2018-12-21 07:27:55 UTC,"Change abandoned by Kuo-tung Kao (<email address hidden>) on branch: master
Review: https://review.openstack.org/599970
Reason: The patch already was commited by the other one."
1790809,2018-12-21 07:31:38 UTC,"The bug have been fixed by the other one.
https://github.com/openstack/kolla/blob/master/docker/zun/zun-base/Dockerfile.j2#L58"
1790809,2020-06-22 00:24:36 UTC,Will this be fixed in Rocky?
1790812,2018-09-05 09:44:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/599984"
1790814,2020-06-14 20:17:45 UTC,It's a bug because app-store are used by less-techy user who then don't notice what kind of package they have just installed. Or don't know why they should prefer one over the other.
1790814,2020-06-14 11:39:38 UTC,"*well, more a limitation than a bug."
1790814,2020-06-14 11:39:25 UTC,Launchpad Bug Watch Updater translated 'Closed' in GitLab to mean 'Fix Released' when it actually means 'Invalid' in this case. That would be a bug with Launchpad Bug Watch Updater.
1790814,2020-03-31 12:59:45 UTC,Can someone post a link to the released fix reported 30. march? I can't find it.
1790814,2019-04-22 00:08:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790814,2019-04-22 13:48:40 UTC,Issue reported to GNOME / gnome-software too:
1790814,2019-04-23 11:13:14 UTC,"> This is a downstream bug. The Ubuntu snap needs to add some extra metadata if it wants to be combined with the other entry.
"
1790816,2019-02-27 22:20:27 UTC,"It's a shot in the dark, but in my case, pulse sound server (atop of alsa) seems to have gotten into a mess with an upgrade between 16.04 and 18.04. Post login, removing old / session start user config fixed my dodgy channel mappings (but not quite the same as crackling, etc):"
1790816,2019-03-02 13:51:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790816,2019-03-07 04:43:06 UTC,"Thanks to your reply to my problems with 18.04 and sound. Just now saw it,
so I am only now replying."
1790821,2019-10-23 18:31:06 UTC,Bumping this to deal with the import failure in 5.1.5.
1790821,2019-10-23 18:30:34 UTC,"Fixed in revision df3fabfa21c1488c2ce9c2505de9663489d677df
https://git.launchpad.net/kicad/patch/?id=df3fabfa21c1488c2ce9c2505de9663489d677df"
1790821,2019-10-22 23:11:32 UTC,"Oops, sorry.  Disregard that.  I see the issue."
1790821,2019-10-22 22:43:23 UTC,What is this report actually requesting? It isn't clear from the previous discussion.
1790821,2019-01-18 09:10:11 UTC,"a similar issue, with the file not imported correctly when those entities are inside (they don't get just skipped)
https://forum.kicad.info/t/problems-importing-autocad-dxf-into-pcbnew/14722/9
https://kicad-info.s3.dualstack.us-west-2.amazonaws.com/original/2X/5/56ee40a3a5a442845df2026097198da367cb6719.dxf"
1790821,2019-10-22 22:59:13 UTC,"@Maurice, the file imports correctly for me."
1790821,2018-09-22 12:53:54 UTC,"Pcbnew is not a MCAD tool, so many dxf entities cannot be managed, and are just ignored.
Now a warning message (as requested by many users) is displayed for ignored dxf entities."
1790821,2018-09-22 07:19:35 UTC,"But then it's a difference.
Now it aborts."
1790821,2018-09-22 03:11:56 UTC,We've never handled solid objects.  Previous DXF import silently skipped them.
1790821,2018-09-12 20:43:32 UTC,Marking as High at least until we find out if it's a regression or not.
1790821,2018-09-22 13:20:36 UTC,"Ok.
Maybe I misinterpreted that part.
My memory was that it was also not imported.
However this was some time
ago so can't remember the details."
1790825,2018-09-05 09:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790825,2018-09-06 02:59:02 UTC,These two tests will be skipped with QEMU 3.0.0 built from source.
1790825,2018-11-09 10:38:25 UTC,"On Cosmic, these test cases will be skipped:
    qemu-system-aarch64: Userspace GICv3 is not supported with KVM"
1790825,2019-05-07 11:37:33 UTC,"For X-hwe, this gicv3-ipi is still failing but gicv3-active will pass on Moonshots node (skipped on ThunderX)"
1790825,2019-11-25 17:21:53 UTC,"So after running into bug# 1828165   I now stumbled across this one,  This test is invalid, as gicv3 is only supported on arm64 hardware Thunderx and newer.  the HP Moonshot cartridges are NOT to be used for this test.  This needs to be blacklisted somehow, will touch base with SAM on doing so."
1790825,2019-11-25 17:22:53 UTC,Marking the linux bug invalid as this test is not properly targeted to run on the correct hardware
1790826,2018-09-06 13:12:50 UTC,"Change abandoned by Carlos Camacho (<email address hidden>) on branch: master
Review: https://review.openstack.org/595817"
1790826,2019-05-13 07:22:07 UTC,"Change abandoned by Carlos Camacho (<email address hidden>) on branch: master
Review: https://review.opendev.org/595817
Reason: not needed"
1790827,2018-11-28 20:42:11 UTC,"This depends on Django feature. The bug itself looks valid, but considering the current horizon development human resource, what we can do is to wait for some improvement in Django."
1790827,2018-10-05 14:23:49 UTC,"Hi mashuting,"
1790839,2018-09-06 12:17:34 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: master
Review: https://review.openstack.org/599999"
1790842,2018-09-14 16:18:05 UTC,"@Wayne, that has all the information, but using that from a script would require parsing the string, which may contain an arbitrary number of dashes in the base tag name and then splits off the number of commits and the git commit ID with more dashes, so I'd think this would be too difficult to use reliably."
1790842,2018-09-05 10:57:27 UTC,I did some initial work to implement such an abstraction layer:
1790842,2018-09-08 20:31:44 UTC,We should try to make this happen during v6 development.  I suspect a lot of folks are going to want input on this.
1790842,2018-09-09 18:33:49 UTC,"I had hoped to get something like that in 5.1 already — that's why I limited the scope to ""get the version information"" in order to make this the only API that we need to commit on for now."
1790842,2018-09-14 15:06:33 UTC,"@Simon, is the function GetBuildVersion() adequate or do you need something different?  This is the function used throughout KiCad to fetch the version string."
1790842,2018-09-14 19:55:34 UTC,"If git is unavailable, the user needs to set a CMake variable, unless they are building from a release tarball. That should work for everyone, the only downside is that it requires that whoever prepares the release to give a default to that variable (as well as adjusting KICAD_VERSION)."
1790842,2018-09-14 16:37:47 UTC,"@Simon, I was thinking something cheap and dirty like exposing GetBuildVersion() but your assertion is correct that there may be some issues using the KiCad build string.  The issue I see with your solution that git is not always available for builds so using the `git rev-list --count` cannot be ensured.  The only way I know is to have a header that we manually update whenever we change any of the exposed pcbnew api but that is  probably not going to be any more reliable because it depends on devs remembering to increment the python api counter.  I'm open to suggestion on this one."
1790847,2018-10-04 18:05:44 UTC,I'm hitting some additional py3.7 unit tests errors. Please see: https://paste.ubuntu.com/p/cZb4zG4XWT/
1790852,2018-09-05 11:27:40 UTC,"Thanks for the report. These are known problems that are unfortunately
very difficult to solve:
https://github.com/jendrikseipp/rednotebook/issues/369"
1790855,2019-01-24 10:49:02 UTC,"Over the last years, the gpsd upstream usually did a very good job on ABI/API changes. This time its ... sad."
1790855,2019-01-24 10:50:11 UTC,I've subscribed Eric S. Raymond on this bug so he can see whats going on...
1790855,2019-03-05 09:11:46 UTC,While I'll continue to work with Bernd to get the newer GPSD in (post Buster) which will make it qualify for MAIN inclusion I wanted to share that I just realized that it was already in main in precise - I thought it is worth to share that nugget of information.
1790855,2019-10-17 08:44:21 UTC,"3.19-2 is now in Debian/unstable and will soon sync to Ubuntu.
That means the changes in 3.18 to resolve the packaging issues are in too.
Thanks Bernd for all the work."
1790855,2019-12-11 16:36:07 UTC,I helped to get the lib transition done and 3.19-3 is not only on proposed but in focal-release for real.
1790855,2019-01-24 07:32:36 UTC,"I further found potential changes that need adaptations in:
- Savannah issue #53671: policy_t -> gps_policy_t. [7]
- ATT: centralize clearing of the attitude data. [8]"
1790855,2020-01-10 04:09:00 UTC,"I reviewed gpsd 3.20-1 as checked into focal.  This shouldn't be considered
a full audit but rather a quick gauge of maintainability. As noted in the
MIR description, this review only covers code and binaries which are
contained in the gpsd and libgps25 packages."
1790855,2020-01-10 07:18:23 UTC,"Great, thanks Alex.
This is ready from MIR+Security POV now.
=> Set in progress according to our state chart"
1790855,2020-01-10 08:24:58 UTC,"On 2020-01-10 08:18, Christian Ehrhardt  wrote:

> Great, thanks Alex.
> This is ready from MIR+Security POV now.
> => Set in progress according to our state chart
>
> The latest version is in Focal already:
>  gpsd | 3.20-1         | focal/universe   | source, amd64, arm64,
> armhf, ppc64el, s390x
"
1790855,2020-01-29 13:24:33 UTC,"This had too many dependencies yesterday.
But when I was looking for that today I found that Steve already added"
1790855,2019-12-12 07:09:46 UTC,"FYI - server team now is already subscribed to this, that way we see ahead of time how much traffic is on this package and we can't forget it later on :-) Thanks Josh."
1790855,2019-01-24 07:24:29 UTC,"Yeah I formerly checked only libgps.h, but the list is somewhat bigger but still seems manageable:"
1790855,2020-01-29 13:25:02 UTC,"root@f:~# apt-cache policy libgps-dev gpsd
libgps-dev:
  Installed: (none)
  Candidate: 3.20-3
  Version table:
     3.20-3 500
        500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
gpsd:
  Installed: (none)
  Candidate: 3.20-3
  Version table:
     3.20-3 500
        500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages"
1790855,2019-01-23 15:19:17 UTC,"I didn't realize (or I forgot over Christmas?) that was the reason to make the transition harder than usual :-/
Thanks for the Info Bernd!"
1790855,2019-01-24 02:17:16 UTC,"Wow, that diff is really gross. (And the ""bump on incompatible changes"" define is even sitting there in the context.) Are we sure this is the best tool for the job?"
1790855,2018-09-05 13:35:20 UTC,+1 for server team ownership of gpsd
1790855,2018-09-13 18:20:06 UTC,"Since you're only Suggesting from chrony, this does not actually require
a MIR -- it's place in universe is fine for Suggests, and the package
will be available for installation."
1790855,2018-10-23 14:54:35 UTC,"You misunderstand, I think. Why put it in main at all, if you're not going to be installing it by default? There's just about no use; it's still only Suggested to install. People can install it from universe when they want a hardware time source."
1790855,2018-10-23 15:05:29 UTC,"On Tue, Oct 23, 2018 at 5:02 PM Mathieu Trudel-Lapierre <
<email address hidden>> wrote:"
1790855,2018-09-19 06:01:02 UTC,"Hi,
I wanted to give an update on the current status.
First of all thanks Mathieu for the reivew."
1790855,2018-12-03 00:00:38 UTC,@cyphermox - this is assigned to the security team for security review but is still marked Incomplete from your questions earlier - plus looks like you also NAK'd it above - is this now ACK'd from your side or is it still blocked - and hence should I un-assign it from the security team?
1790855,2018-12-03 06:45:54 UTC,"Hi Alex, it was NAK'd from packaging issues.
Those are already split in the Debian repository [1][2] and only wait for an upload to happen."
1790855,2019-01-23 10:17:09 UTC,"Hi,
all packaging quality issues are adressed in 3.18.1-1 which is in Debian experimental.
The maintainer wants to wait to do the transition until Buster is released."
1790855,2019-01-23 14:38:19 UTC,"Actually I do not want to wait, but given the fact that most reverse dependencies do not build due to an undocumented API/ABI change, I just did not have the time to figure out what the correct way to fix this for each reverse dependency is.
The new main gpsd upstream developer was not willing to fix the manpages and documentation after being asked if he could do it. He said he doesn't care about distributions and that the documentation is the code..."
1790855,2018-10-23 15:12:50 UTC,That isn't necessary. You should just be clear that you just want to seed it in the 'supported' seed.
1790856,2020-01-28 07:33:43 UTC,"bug 1853506 and bug 1790856 are ready (process-wise) when you are @ahasenack.
As checked on IRC, let me know when all is ready to add the dependency pulling it in."
1790856,2020-01-20 18:28:17 UTC,"I reviewed pmdk 1.7-1ubuntu1 as checked into focal.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1790856,2020-01-21 11:31:01 UTC,"Thanks for your review.  There's next release coming probably this week; -rc1 is already out.  The changes relevant for MIR are:
 * vmem and vmmalloc are dropped (moved to another source, but it's not main material).
   These were the only parts doing custom memory management in DRAM.
 * ppc64el support has been added"
1790856,2020-01-21 12:44:44 UTC,"The split is doable. What hurts, though, is having these kind of changes (like vmem and vmalloc moving to another source) still happening. We don't expect a package in main to still be going through these types of big changes. Has this stabilized?"
1790856,2020-01-31 18:32:38 UTC,"Splitting will serve another purpose too. rpmemd also links with libfabric, which is in universe. By moving rpmemd out of pmdk-tools, and into a new universe package, we won't have to MIR libfabric."
1790856,2020-02-04 08:19:36 UTC,"Thanks for explaining more details and backgrounds Adam!
But promotion to main isn't really done per-architecture."
1790856,2020-02-02 14:25:44 UTC,"This seems to auto-inclue way too much:
From
https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html"
1790856,2020-02-02 18:43:03 UTC,"@Andreas - take a look at these and ack+push if you are ok with that:
=> https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/ubuntu/+merge/378435"
1790856,2020-02-03 01:28:33 UTC,"Sorry if I was unclear: libpmemobj and friends are well-tested on amd64, it's only the ppc64el port of those that's very new (mostly because of many hardcoded x86 assumptions, like page and especially cacheline size, that are untrue on ppc).  The library has gone through six years of development already, thus can be considered pretty solid."
1790856,2019-10-14 05:35:51 UTC,"Since nothing happened for a while here an interim update, atm this seems to be on track for security review on time to make it into Ubuntu 20.04."
1790856,2020-02-06 14:39:32 UTC,"$ ./change-override -c main -t pmdk
Override component to main
pmdk 1.7-1ubuntu1 in focal: universe/libs -> main
Override [y|N]? y
1 publication overridden."
1790856,2020-01-31 18:57:58 UTC,"Version 1.8 has just been released.  As I mentioned before, besides splitting out deprecated and out of scope for PMDK libvmem and libvmmalloc, support for ppc64el has been added, thanks to Lucas Magalhães of IBM."
1790856,2019-02-19 08:46:58 UTC,"Just hit a snag with the new 1.5 upstream version, which I now realize Adam mentioned earlier."
1790856,2019-11-18 14:07:38 UTC,"The hardware is commercially available for more than half a year, thus proper support is more urgent than it was when this bug was initially filed.  At this time, the DIMMs work only with large servery machines, for which large numbers of qemu VMs is one of most widespread uses.  Thus, it's important that qemu can use NVDIMMs in non-volatile modes."
1790856,2019-02-13 14:25:51 UTC,"I'm working on syncing with debian's 1.5. I might first update ours to 1.5, and then merge."
1790856,2019-01-29 16:40:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790856,2019-01-09 11:55:45 UTC,"PMDK is since recently in Debian, maintained by me.  Version 1.5 (Ubuntu still has only 1.4)."
1790856,2018-09-25 08:54:45 UTC,"The feedback so far was answered and seems ok:
- ABIs experimental -> only pmemcto which will not get into MAIN
- amd64-only -> clarified with upstream really is only amd64 only atm
- bundled jemalloc -> explained by upstream  has to stay bundled
- package subscription -> done by powersj in comment #8"
1790856,2018-09-19 11:32:15 UTC,ubuntu-server is now subscribed to the bugs for pmdk
1790856,2018-09-19 08:55:26 UTC,"ok, then pmemcto should stay in universe."
1790856,2018-09-19 06:49:12 UTC,"I got confirmation from upstream @intel that pmdk is amd64 only, and there is some experimental arm64 code:
""""""
There's no official support for architectures other than x86_64, because PMDK requires per-architecture code (see src/libpmem/$(ARCH)/)."
1790856,2018-09-17 09:16:45 UTC,"On Fri, Sep 14, 2018 at 4:21 PM Andreas Hasenack <email address hidden>
wrote:"
1790856,2018-09-14 14:15:35 UTC,Only pmemcto is flagged as experimental: http://pmem.io/pmdk/libpmemcto/
1790856,2018-09-14 14:12:28 UTC,"Regarding jemalloc, I asked about that point exactly before submitting this package for archive inclusion:"
1790856,2018-09-13 10:46:02 UTC,some comments:
1790856,2018-09-05 15:35:12 UTC,"To add one more reason to do this like ""now"" (=early 19.04) from my personal POV.
While rare today, looking into the future I'd think the availability of nvdimms will rise."
1790856,2019-02-13 14:26:45 UTC,The pmdk 1.5 update is needed to unblock https://launchpad.net/ubuntu/+source/libpmemobj-cpp in disco-proposed
1790860,2018-12-11 12:05:31 UTC,I also have the same error on 18.04 and kernel 4.15.0-42-generic...
1790860,2018-10-18 11:00:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790860,2018-10-18 11:00:03 UTC,"I have exactly the same problem on 18.04 and kernel 4.15.0-36-generic. Reinstalling manpages and man-db did not help.
Did you find a solution?"
1790861,2019-08-11 22:52:41 UTC,With amdgpu.dc=0 I get random mouse lag after moving my mouse quickly. The cursor will just stop moving. I turned amdgpu.dc=1 and it went away.
1790861,2018-09-05 12:13:00 UTC,apport information
1790861,2018-09-05 12:13:01 UTC,apport information
1790861,2018-09-05 12:13:02 UTC,apport information
1790861,2018-09-05 12:13:04 UTC,apport information
1790861,2018-09-05 12:13:05 UTC,apport information
1790861,2018-09-06 16:00:03 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1790861,2018-09-06 16:39:21 UTC,"Did the test on 4.19.0-041900rc2-generic, issue is still there."
1790861,2019-01-08 00:15:16 UTC,"I'm using an RX 480 and also have the same problem on kernels 4.18 and 4.20 (tested using 4.20.0-042000 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20/). Adding ""amdgpu.dc=0"" to GRUB fixes the problem in both cases."
1790861,2019-01-08 01:09:47 UTC,I've since tested Linux v5.0-rc1 (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc1/) and the issue still hasn't been fixed.
1790861,2019-01-08 02:32:11 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu"
1790861,2019-01-08 05:11:45 UTC,I've filed a bug report. (https://bugs.freedesktop.org/show_bug.cgi?id=109246)
1790861,2019-08-10 18:29:47 UTC,"I am having the same issue on my rx570, I am on kernel 5.1.21"
1790861,2019-08-10 18:31:42 UTC,"I am using one displayport 4k monitor, and one hdmi 1080p monitor. They keep waking each other up. When I used an adapter to make the 1080p monitor connect via a displayport > hdmi adapter, they both just output black when trying to sleep and cannot be woken up. They are still outputting black, they did not go to sleep."
1790861,2018-10-27 21:52:03 UTC,"Same problem here with kernel 4.19 and 4.18, rx580 and vega 8 (ryzen 2200G)."
1790861,2018-09-05 12:12:57 UTC,apport information
1790861,2018-09-05 12:12:59 UTC,apport information
1790861,2018-09-05 12:12:55 UTC,apport information
1790861,2018-09-05 12:12:56 UTC,apport information
1790861,2018-09-05 12:12:41 UTC,apport information
1790861,2018-09-05 12:12:43 UTC,apport information
1790861,2018-09-05 12:12:44 UTC,apport information
1790861,2018-09-05 12:12:45 UTC,apport information
1790861,2018-09-05 12:12:46 UTC,apport information
1790861,2018-09-05 12:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790861,2018-09-05 12:12:49 UTC,apport information
1790861,2018-09-05 12:12:50 UTC,apport information
1790861,2018-09-05 12:12:51 UTC,apport information
1790861,2018-09-05 12:12:52 UTC,apport information
1790861,2018-09-05 12:12:53 UTC,apport information
1790861,2018-09-05 12:12:54 UTC,apport information
1790861,2018-09-05 12:12:47 UTC,apport information
1790864,2018-11-26 11:30:50 UTC,The review introduced by Attila has fixed my issue.
1790864,2018-11-21 20:59:49 UTC,"Reviewed:  https://review.openstack.org/615425
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=3588bb3f5ef546a0ef4d4ad621fd1be381b5fdaf
Submitter: Zuul
Branch:    master"
1790864,2018-11-04 11:46:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/615425"
1790865,2020-08-10 10:26:57 UTC,2.17 is now incoming in groovy
1790875,2018-12-04 01:21:42 UTC,"I ran into this consistently on a JAAS controller we were preparing to upgrade to 2.4.7, apparently always while backing up statueshistory.  So perhaps it's also a function of busyness as well as or instead of size?"
1790875,2018-12-12 16:20:12 UTC,"On Tue, 2018-12-04 at 01:21 +0000, Paul Collins wrote:

> I ran into this consistently on a JAAS controller we were preparing
> to
> upgrade to 2.4.7, apparently always while backing up
> statueshistory.  So
> perhaps it's also a function of busyness as well as or instead of
> size?
"
1790875,2018-12-12 16:30:06 UTC,"tune it, or get the backup from the PRIMARY  as it was agreed."
1790875,2019-10-31 03:33:50 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1790879,2018-09-11 16:00:10 UTC,"gmann is supposed to have an etherpad which the nova API subteam is using to track generic low-hanging-fruit cleanup actions in the API, for things like this (error codes, schema validation, etc)."
1790879,2018-09-11 15:40:48 UTC,"FYI this was discussed/brainstormed in general, ""REST API Error Consistency"" at the last Vancouver Summit Forum:"
1790879,2018-09-12 14:34:45 UTC,added this item in Nova API cleanup etherpad
1790880,2018-09-06 19:17:07 UTC,That did not clear my problem.
1790880,2018-11-23 07:54:49 UTC,Same trying follow https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel on Ubuntu 18.04.1
1790880,2018-09-06 16:01:16 UTC,You may need to run the following from a terminal:
1790888,2018-09-06 16:35:44 UTC,"Hi,"
1790888,2018-09-05 15:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1790888,2018-09-05 15:04:20 UTC,thanks for registration
1790888,2018-09-05 15:13:39 UTC,apport information
1790888,2018-09-05 15:13:40 UTC,apport information
1790888,2018-09-05 15:15:47 UTC,"status of the bug  'Confirmed"""
1790888,2018-09-06 15:59:40 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1790888,2018-09-06 16:34:15 UTC,"Hi,"
1790888,2018-09-14 15:46:34 UTC,docs attached
1790896,2019-03-10 22:25:10 UTC,I can confirm that I also see this issue on 3.2.3.
1790896,2019-02-07 18:54:43 UTC,http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1790896_receipt_email / working/user/jboyer/lp1790896_receipt_email will take care of this. I got a little overzealous when it came to letting the result of a string match() be coerced into a Boolean and accidentally broke it.
1790896,2019-05-23 21:27:06 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jason and Josh!"
1790896,2019-02-07 17:23:33 UTC,"This silent fail also happens when an invalid string is in the patron email field. It's 100% reproducible in v.3.0.13 if you just put any non-email value in the email field for any patron account, then attempt to print receipts for checkouts, items out, or bills. Oddly enough, printing the Open Hold Requests list did work."
1790904,2019-11-05 15:15:03 UTC,New MR for Bionic:
1790904,2019-12-02 16:30:35 UTC,"Awesome,"
1790904,2019-12-09 08:29:58 UTC,This bug was fixed in the package simplestreams - 0.1.0~bzr460-0ubuntu1.1
1790904,2019-12-02 15:58:05 UTC,"Timo,"
1790904,2019-11-29 12:27:40 UTC,"Hello David, or anyone else affected,"
1790904,2019-01-15 07:26:20 UTC,Thanks for the correction :)
1790904,2018-09-05 23:32:16 UTC,First attempt at a fix:
1790904,2019-01-11 12:26:32 UTC,"Hi,"
1790904,2018-11-13 18:20:17 UTC,This bug was fixed in the package simplestreams - 0.1.0-17-g693795b-0ubuntu1
1790904,2018-10-31 14:07:35 UTC,"This bug is fixed with commit efb19f32 to simplestreams on branch master.
To view that commit see the following URL:
https://git.launchpad.net/simplestreams/commit/?id=efb19f32"
1790904,2018-10-25 20:48:13 UTC,"The MP has been updated.
https://code.launchpad.net/~thedac/simplestreams/+git/simplestreams/+merge/354369"
1790904,2019-12-09 08:30:06 UTC,"The verification of the Stable Release Update for simplestreams has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1790904,2019-01-14 18:17:39 UTC,"This does need to be SRU'd to Bionic.
But not Xenial. Rocky is only supported on Bionic."
1790920,2018-09-11 15:25:29 UTC,"Effectively when using mongodb 3.2 you need to restart the service (see https://docs.mongodb.com/v3.2/tutorial/change-oplog-size/ ), in 3.6 it's no longer needed (see https://docs.mongodb.com/v3.6/tutorial/change-oplog-size/ ), so juju would need to check which version of mongodb is running and if it's >=3.6 accept the change, otherwise return an error indicating why it's not possible to change it"
1790920,2018-09-11 13:43:34 UTC,"We do already have agent.conf ""MONGO_OPLOG_SIZE"", which I thought we
exposed in controller config. IIRC, we don't let you change it after
bootstrap, as there are some sort of issue around it with mongo (I think
the issue is that you can't change it without restarting mongo, I don't
remember all the details)."
1790924,2018-09-06 10:24:11 UTC,"Hi, in Desktop Preferences > Desktop Icons have ""Show connected volumes on the desktop"" you see left panel in pcmanfm doesn't apppers cifs volumes. Still believe it to be a regression bug."
1790924,2018-09-10 17:31:11 UTC,I mount using smb://20.20.0.1/publico volumes in desktop works! Problem using the cifs!
1790924,2018-09-05 21:47:48 UTC,"Hi, I've never seen the CIFS partition in the desktop, in pcmanfm neither I've always (in 16.04 too) created a favorite to have ""quick access"".
However, I alwasy mounted with /etc/fstab with this:"
1790924,2018-11-21 02:23:38 UTC,try mounting it in /media instead of /Public folder tell us what happens
1790924,2018-09-05 19:13:39 UTC,Try test!
1790924,2018-09-05 19:15:48 UTC,Still test
1790924,2019-04-12 11:59:56 UTC,"Well, i wait for ubuntu 18.04.2 and now work cifs and show me Desktop Volume Mounted Icons."
1790924,2018-11-19 18:13:38 UTC,UP!
1790926,2018-09-05 19:51:22 UTC,run term
1790926,2018-09-06 11:55:08 UTC,"Bug error occurs only when running and used xfce desktop
If the gnome environment is used
Bedbug does not occur
The system does not report an error when the gnome graphics environment is used"
1790926,2020-03-13 13:25:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790931,2019-03-20 20:49:07 UTC,"Change abandoned by Lance Bragstad (<email address hidden>) on branch: master
Review: https://review.openstack.org/600266
Reason: Putting this on the back burner until we discuss it further at the PTG/forum. We can restore if we decide this is still the direction we'd like to go."
1790933,2018-11-29 19:52:04 UTC,Notes to self: Clustering seems to be doable in OVS > 2.9 (>2.10 preferred). A working example can be seen here:
1790942,2018-09-06 21:54:21 UTC,"The log out button is incidental, really. Every time you open the SongSelect wizard you have to log in anyway."
1790943,2018-09-06 09:02:55 UTC,"Reviewed:  https://review.openstack.org/599351
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=c4c16bcf497ef77119509f6ab63a3b769e41e9be
Submitter: Zuul
Branch:    master"
1790943,2020-07-23 06:21:03 UTC,Project is no longer maintained.
1790943,2018-09-06 09:26:52 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/600391"
1790943,2019-01-07 14:42:04 UTC,Note that https://review.openstack.org/#/c/626187/ may also solve the same problem using locks instead.
1790943,2019-08-09 15:23:45 UTC,"Change abandoned by Alex Kavanagh (tinwood) (<email address hidden>) on branch: master
Review: https://review.opendev.org/602037
Reason: The project is now archived."
1790943,2018-09-06 14:29:35 UTC,"Reviewed:  https://review.openstack.org/600391
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=4b935f860cb4299f846aec8d503d979efd7646ba
Submitter: Zuul
Branch:    stable/rocky"
1790954,2018-09-24 14:15:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604795"
1790954,2018-09-28 07:58:17 UTC,"Change abandoned by Vishakha Agarwal (<email address hidden>) on branch: master
Review: https://review.openstack.org/604795
Reason: The bug is already Fixed."
1790954,2019-07-01 08:28:23 UTC,"Change abandoned by wangxiyuan (<email address hidden>) on branch: master
Review: https://review.opendev.org/600357"
1790955,2019-12-08 20:34:19 UTC,"Hi Hermann,"
1790955,2019-12-12 13:37:38 UTC,This is fixed in 4:19.08.3-2ubuntu1
1790956,2018-10-04 16:02:12 UTC,In Ubuntu this fix is available in nova-lxd 18.0.0-0ubuntu1.
1790956,2018-09-06 14:29:32 UTC,"Reviewed:  https://review.openstack.org/600391
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=4b935f860cb4299f846aec8d503d979efd7646ba
Submitter: Zuul
Branch:    stable/rocky"
1790956,2018-09-06 09:26:51 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/600391"
1790956,2018-09-06 09:02:53 UTC,"Reviewed:  https://review.openstack.org/599351
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=c4c16bcf497ef77119509f6ab63a3b769e41e9be
Submitter: Zuul
Branch:    master"
1790956,2018-09-05 21:03:52 UTC,"2018-09-05 20:16:31 DEBUG install Reading package lists...
2018-09-05 20:16:31 DEBUG install Building dependency tree...
2018-09-05 20:16:31 DEBUG install Reading state information...
2018-09-05 20:16:31 DEBUG install genisoimage is already the newest version (9:1.1.11-3ubuntu2).
2018-09-05 20:16:31 DEBUG install python-six is already the newest version (1.11.0-2).
2018-09-05 20:16:31 DEBUG install xfsprogs is already the newest version (4.9.0+nmu1ubuntu2).
2018-09-05 20:16:31 DEBUG install librbd1 is already the newest version (13.2.1+dfsg1-0ubuntu2~cloud0).
2018-09-05 20:16:31 DEBUG install nova-compute is already the newest version (2:18.0.0-0ubuntu3~cloud0).
2018-09-05 20:16:31 DEBUG install nova-compute-lxd is already the newest version (18.0.0~rc1-0ubuntu1~cloud0).
2018-09-05 20:16:31 DEBUG install python-psutil is already the newest version (5.4.6-1build1~cloud0).
2018-09-05 20:16:31 DEBUG install The following package was automatically installed and is no longer required:
2018-09-05 20:16:31 DEBUG install   grub-pc-bin
2018-09-05 20:16:31 DEBUG install Use 'apt autoremove' to remove it.
2018-09-05 20:16:31 DEBUG install 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
2018-09-05 20:16:31 DEBUG install 3 not fully installed or removed.
2018-09-05 20:16:31 DEBUG install After this operation, 0 B of additional disk space will be used.
2018-09-05 20:16:31 DEBUG install Setting up python-nova-lxd (18.0.0~rc1-0ubuntu1~cloud0) ...
2018-09-05 20:16:32 DEBUG install   File ""/usr/lib/python2.7/dist-packages/nova_lxd_tempest_plugin/tests/scenario/manager.py"", line 569
2018-09-05 20:16:32 DEBUG install     result = test_utils.call_until_true(ping, timeout, 1)
2018-09-05 20:16:32 DEBUG install          ^
2018-09-05 20:16:32 DEBUG install SyntaxError: invalid syntax
2018-09-05 20:16:32 DEBUG install
2018-09-05 20:16:32 DEBUG install dpkg: error processing package python-nova-lxd (--configure):
2018-09-05 20:16:32 DEBUG install  installed python-nova-lxd package post-installation script subprocess returned error exit status 101
2018-09-05 20:16:32 DEBUG install dpkg: dependency problems prevent configuration of nova-compute-lxd:
2018-09-05 20:16:32 DEBUG install  nova-compute-lxd depends on python-nova-lxd (= 18.0.0~rc1-0ubuntu1~cloud0) | python3-nova-lxd (= 18.0.0~rc1-0ubuntu1~cloud0); however:
2018-09-05 20:16:32 DEBUG install   Package python-nova-lxd is not configured yet.
2018-09-05 20:16:32 DEBUG install   Package python3-nova-lxd is not installed.
2018-09-05 20:16:32 DEBUG install
2018-09-05 20:16:32 DEBUG install dpkg: error processing package nova-compute-lxd (--configure):
2018-09-05 20:16:32 DEBUG install  dependency problems - leaving unconfigured
2018-09-05 20:16:32 DEBUG install No apport report written because the error message indicates its a followup error from a previous failure.
2018-09-05 20:16:32 DEBUG install dpkg: dependency problems prevent configuration of nova-compute:
2018-09-05 20:16:32 DEBUG install  nova-compute depends on nova-compute-kvm | nova-compute-hypervisor; however:
2018-09-05 20:16:32 DEBUG install   Package nova-compute-kvm is not installed.
2018-09-05 20:16:32 DEBUG install   Package nova-compu..."
1790963,2018-11-15 16:29:05 UTC,This bug was fixed in the package openssh - 1:7.9p1-1
1790963,2018-10-31 12:55:48 UTC,"Indeed, there is fix [1] in latest OpenSSH 7.9p1 so updating the clients to the latest version should resolve the issue. But it does not change that there is a bug in RHEL7 too."
1790963,2018-10-31 12:17:01 UTC,I think something happend within openssh 7.9 if my interpretation of this is correct: https://www.spinics.net/lists/openssh-unix-dev/msg05371.html
1790963,2018-09-07 16:14:28 UTC,"This [1] appears to be the source of the problem, specifically ""Add new RSA certificate types that that can be used in the above options and on the wire to require the use of RSA/SHA2 signatures."" - unfortunately, those new certificate types don't exist/work in openssh <7.8, breaking backwards compatibility with 7.8 clients."
1790963,2018-09-07 15:31:43 UTC,"Hi all,"
1790963,2018-09-07 10:57:05 UTC,"Thanks Scott for the report, we don't have 7.8 yet (Cosmic will be released with 7.7).
But as I read the issue this already is an issue for all older SSH servers as soon as somebodies client is new."
1790963,2018-11-12 17:42:00 UTC,Am I right in understanding that there is no proposed action for Ubuntu to take on this right now?
1790963,2018-09-05 21:38:23 UTC,"Updated the description - specifically, this appears to affect certificate authentication and be related to <email address hidden> and <email address hidden> which are present in 7.8 server, but not earlier versions (nor are valid to add to the configuration manually)."
1790963,2018-09-05 20:45:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790963,2018-09-05 11:36:43 UTC,"Please, open a customer case if you have this issue with your RHEL installation."
1790963,2018-09-05 11:07:44 UTC,"Hi,"
1790963,2018-08-30 13:22:47 UTC,"Description of problem:
The OpenSSH server in RHEL7.6 does not send complete list of signature algorithms in SHA2 extension."
1790963,2018-09-04 17:33:06 UTC,"If you want to use certificates, you need to list also the SHA2 variants of certificates:"
1790963,2018-09-04 16:46:16 UTC,"Hi,"
1790963,2018-09-06 17:21:31 UTC,"Hi all,"
1790964,2020-12-29 21:13:32 UTC,"I'm ""using"" the latest snapd (just checked for update before writing this).
The issue persists.
`snap install <package>` does not resume downloads, nor does `snap refresh` (including auto-refresh).
`snap download <package>` does resume downloads, but as far as I know, it won't download delta updates (sad).
I'm on a remote area and my internet connection is very unstable and slow (~64kB/s down, ~20ish kB/s up).
`apt` works fine, though.
Unfortunately, until this issue is fixed, I can't really use snaps."
1790964,2020-02-23 09:48:49 UTC,"Just to follow up on my comments in the thread that @roadmr linked to, I can confirm that with 2.43.3, downloads resumption *is* possible using snap download, but does *not* currently appear to be implemented for snap refreshes (either automatic ones, or those triggered manually)."
1790964,2019-08-13 18:08:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790964,2019-08-14 08:57:30 UTC,"Dan, if the download you are referring to is a refresh, note you can rate limit *auto*-refreshes (that is, non-interactive refreshes) via `snap system set refresh.rate-limit <some limit>`. For interactive refreshes and installs, you can replace them with a `snap download` followed by a `snap ack` and a `snap install`, and `snap download` will leave a .partial file if you interrupt it."
1790964,2020-02-20 20:49:10 UTC,"See https://forum.snapcraft.io/t/refreshing-downloading-a-snap-over-a-poor-connection/15350/5, looks like snapd is still not resuming downloads in situations where it should (unexpected connection interruptions)."
1790964,2019-08-13 18:10:39 UTC,"Yep, I'm hitting a similar problem.  I'm trying to install the spotify snap on a library wifi connection that only gives me ~250kB/s and it's going to take about a quarter hour.  That makes using the connection for _anything else_ painful, but I can't interrupt the snap download without losing all the progress I've made."
1790973,2019-10-17 10:07:49 UTC,I also have this issue with an identical setup.
1790973,2020-09-21 03:07:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1790973,2018-09-06 21:43:37 UTC,"After talking to wxl in irc.freenode.net\lubuntu, it seems like this is more related to openbox"
1790973,2018-09-06 21:44:32 UTC,"wxl changed their mind, lxpanel it is"
1790973,2018-09-05 21:46:34 UTC,"I think I might have posted this in the wrong place, sorry about that. Is there an LXDE launchpad?"
1790979,2018-10-23 20:27:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790979,2019-06-12 12:25:53 UTC,"This bug occurred for me with a fresh installation of Ubuntu 19.04.
I created a new installation of Ubuntu 19.04 on a empty disk and checked the box to encrypt the installation. After the installation I tried to change the password and got locked out."
1790994,2018-09-22 19:31:38 UTC,Update: I fixed my problem by updating the BIOS.
1790994,2018-09-18 09:30:10 UTC,"Après  démarrage de l'ordinateur une fenêtre apparait : ""problème logiciel détecté"" heureusement ceci n'empêche pas l,ordinateur de fonctionner correctement. J'espère qu'avec ubuntu 18/10 ce bug va disparaitre.
Google translation : After starting the computer a window appears: ""problem detected software"" fortunately this does not prevent the computer from working properly. I hope that with ubuntu 18/10 this bug will disappear."
1790994,2018-09-07 03:49:16 UTC,I am also facing same issue.
1790994,2018-09-06 04:27:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1790994,2018-09-21 08:56:31 UTC,Some more information when trying to fix this.
1791006,2018-09-06 15:09:10 UTC,Can we confirm which version of curtin you have installed?
1791006,2018-09-06 20:50:38 UTC,"Assuming you mean on the MAAS machines, here's the cluster controller (same on the region controller):"
1791006,2019-09-19 12:06:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1791006,2018-09-06 05:01:51 UTC,I think the issue is quite simple actually.
1791008,2018-11-21 15:55:26 UTC,"Would need the redis log of this failure, alas."
1791017,2018-09-06 09:07:31 UTC,"Credential without any roles/types setting should be recognize as primary, right?"
1791018,2019-03-12 13:47:42 UTC,Do we still want to have other arches failing the build if tests do not pass?
1791018,2018-09-11 14:29:13 UTC,"I did a test at https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mysql-5.7/+packages by enforcing the test suite on all architectures, and it's actually green. Was going to suggest we enable it for arm64, but maybe we should consider the rest as well."
1791018,2018-09-07 10:28:42 UTC,"During build, passing the mtr suite is only enforced for i386 and amd64 architectures, because upstream has limited support for others, so the test suites tended to be unstable or failing ""reliably"" (particularly due to floating point differences as in this case)."
1791018,2018-09-06 07:18:05 UTC,Reference: wondered while debugging for bug 1791010
1791018,2018-09-07 17:53:10 UTC,"Christian, as Lars writes, Oracle only supports amd64 and i386.
https://salsa.debian.org/mariadb-team/mysql/commit/5d6a44b949d1014332720fb30768047e5b1d3007"
1791019,2019-07-22 04:12:09 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1791019,2018-09-06 11:23:07 UTC,Here's the bug report in GNOME Gitlab: https://gitlab.gnome.org/GNOME/gdm/issues/420
1791019,2018-09-06 11:12:03 UTC,"More testing when using a DisplayPort connected to a 2k monitor:
I am able to do user switching flawlessly, but when I do a VT switch to the console and switch between the ttys for a while and login to one of them and then logout; if I go back to CTRL+f1 and I see the a cursor blinking and a black screen, that's my signal that my user sessions might already have died.  After a while the gdm screen will show up and I am able to login to an account, but it will be a fresh one and the apps that were loaded before are gone. It's like the user session's where killed. Maybe when gdm restarted.  Sometimes it works though, and I am able to relogin to my GUI session, especially if I don't see that cursor blinking with a black background."
1791019,2018-09-06 07:45:47 UTC,This would be related to both:
1791019,2018-09-06 07:54:05 UTC,Please report the issue to the Gnome developers here:
1791019,2018-09-06 07:51:18 UTC,* I had hoped these issues would be fixed with bug 1786872 and bug 1786883.
1791019,2018-09-06 07:49:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791019,2018-09-06 07:56:31 UTC,This might be my old friend; bug 1775764 again.
1791026,2018-09-10 06:23:51 UTC,Thanks for the answer.
1791026,2018-09-07 13:52:41 UTC,"as far as I know, the short answer is no. Inkscape was developed primarily by Linux developers, not Windows."
1791026,2018-09-07 13:18:16 UTC,"Ок. Let's wait.
I've got one more question.
Is there a possibility in this program to manage the application using VBA scripts, as it is done, for example, in the MS Office?
Is it possible to work with this program as a Com-object, i.e. to manage it from another application?"
1791026,2018-09-07 12:59:55 UTC,"thanks for the info.
I do not know how to configure my computer to view this file correctly in MS Paint, so we will have to wait for someone else to look at this."
1791026,2018-09-07 12:05:59 UTC,"I'm working with the Russian version of Windows 7.
I view the file in MS Paint.
Version of Inkscape is 0.92"
1791026,2018-09-07 11:16:59 UTC,"yes, I suspected that the display was probably wrong. The problem is that this is not specifically an Inkscape issue. It is an issue that is shared by all the software on my computers. I do not have any programs on my Windows 10, or Windows XP, machines that are capable of displaying this text correctly."
1791026,2018-09-07 11:00:18 UTC,"All right. In the picture, the Russian text is shown in the wrong format. The Russian text is located just below the top line and on the left side of the sheet."
1791026,2018-09-07 10:36:34 UTC,"thanks for the file.
I am not able to reproduce the problem on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1791026,2018-09-07 09:47:00 UTC,I sent the file.
1791026,2018-09-06 16:27:41 UTC,"again, that link does not work. If I try to download it, I get a Windows error message saying it could not be downloaded. could you provide an attachment in the form of a wmf file? I am attaching a sample file."
1791026,2018-09-06 13:24:10 UTC,">Четверг,  6 сентября 2018, 15:21 +03:00 от Alvin Penner <email address hidden>:
>
>sorry, that link does not work
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1791026
>
>Title:
>  The Russian font is not correctly displayed after downloading the wmf
>  file
>
>Status in Inkscape:
>  New
>
>Bug description:
>  After downloading the wmf file the Russian font is not correctly
>  displayed.
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/inkscape/+bug/1791026/+subscriptions
"
1791026,2018-09-06 12:14:15 UTC,"sorry, that link does not work"
1791026,2018-09-06 09:41:48 UTC,">Четверг,  6 сентября 2018, 12:30 +03:00 от Alvin Penner <email address hidden>:
>
>could you attach the wmf file?
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1791026
>
>Title:
>  The Russian font is not correctly displayed after downloading the wmf
>  file
>
>Status in Inkscape:
>  New
>
>Bug description:
>  After downloading the wmf file the Russian font is not correctly
>  displayed.
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/inkscape/+bug/1791026/+subscriptions
"
1791026,2018-09-06 09:16:57 UTC,could you attach the wmf file?
1791037,2019-01-04 06:08:18 UTC,"Perviously I used LXDE on Lubuntu, now I use 18.04 with Gnome. And the problem is the same.
Here is the Pastebin-side:
https://paste.ubuntu.com/p/gQ6C8hNzpT/"
1791040,2018-09-06 10:04:32 UTC,Seems similar to https://bugs.launchpad.net/juju/+bug/1783983
1791040,2018-09-10 12:05:04 UTC,"Agreed on the related link. The thing is we allow upgrading the same charm mysql->mysql using different charms but not changing from one charm ""ubuntu-basenode"" to another charm ""juju-ingest""."
1791040,2018-09-06 09:52:44 UTC,"(in this case, the source charm contains no configuration at all and the only relation being participated in is juju-info with its subordinate units, so all documented criteria are met)"
1791049,2018-09-06 10:03:06 UTC,Proposed fix: https://github.com/CanonicalLtd/ubuntu-image/pull/162
1791058,2018-09-11 08:09:46 UTC,Further on this bug:
1791058,2018-12-22 00:41:04 UTC,Doesn't seem like a gvfs bug.  Network Manager?
1791060,2018-09-06 12:27:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1791061,2018-09-27 11:41:45 UTC,please solve above problem as soon as possible
1791075,2019-03-24 23:39:15 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1791075,2019-03-22 22:09:45 UTC,"Reviewed:  https://review.openstack.org/643219
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3bd7293dacad1eb1bc6476c6e9875618271cf7f8
Submitter: Zuul
Branch:    stable/queens"
1791075,2019-03-22 03:47:40 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1791075,2019-03-24 23:03:57 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1791075,2019-03-05 11:24:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640982"
1791075,2018-10-30 22:44:43 UTC,"Reviewed:  https://review.openstack.org/600425
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d8f7638d02f7354cea7283bde626d05fb11ae3db
Submitter: Zuul
Branch:    master"
1791075,2018-09-06 12:15:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/600425"
1791075,2019-03-13 20:48:54 UTC,"Reviewed:  https://review.openstack.org/640982
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b09f2e58e9ee38b90e8f84615e0445cc831444be
Submitter: Zuul
Branch:    stable/rocky"
1791075,2019-03-14 02:32:03 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/643219"
1791078,2018-09-06 20:26:28 UTC,I'm wondering how much of this is fallout from the API servers panicing due to the bug around determining collection sizes for the db log pruning.
1791078,2018-09-06 20:27:00 UTC,At a minimum we need to evaluate why these panics occurred.
1791078,2018-09-07 06:32:00 UTC,"> Did the machines recover from the panics? Are they running again?
"
1791078,2018-09-18 10:49:56 UTC,"Looking at the stack trace it is code that is calling NewUserTag without
validating it has a valid username in there. and, in fact, it appears to
have an empty string instead of a username."
1791078,2019-10-31 04:08:24 UTC,Removing from a milestone as this work will not be done in 2.3 series.
1791081,2018-09-06 12:42:01 UTC,My machine was effectively incapacitated during upgrade because removal of packages made my software unuseable. I thought I could fix this with a clean install. My computer is now dead.
1791101,2019-01-07 13:29:51 UTC,"The default MTU on a veth is 1500 - so the moment we assign one to the bridge, the bridge goes down to 1500, rather than the veth taking the higher MTU from the bridge"
1791101,2018-10-18 11:05:23 UTC,"Note that bridge adopts the lowest MTU of all connected devices, so does not need to be set."
1791111,2018-09-07 20:30:18 UTC,"Hi Paul,"
1791111,2020-01-23 11:24:02 UTC,This issue was fixed in the openstack/horizon 16.1.0 release.
1791111,2019-12-16 19:10:17 UTC,This issue was fixed in the openstack/horizon 17.1.0 release.
1791111,2019-12-09 13:00:08 UTC,"Reviewed:  https://review.opendev.org/697630
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=1229bd4bb43882d681937ad799a3a2c8a37193e6
Submitter: Zuul
Branch:    stable/train"
1791111,2019-12-06 08:24:20 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/697630"
1791111,2019-12-06 00:55:05 UTC,"Reviewed:  https://review.opendev.org/692945
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=c0cc0433c645181a9031b99d23954ae9bece9542
Submitter: Zuul
Branch:    master"
1791111,2019-07-30 17:32:44 UTC,"Since this is for new users only, the admin will need to provide the user with enough information to be able to change their password before first login, like some kind of onboarding packet. This would have to include their user ID. There's no way that keystone could supply the user's ID without the user first authenticating. Re-marking this as invalid for keystone."
1791111,2019-07-23 14:48:26 UTC,"I'm working on implementing this for Horizon, and I have a working view where the user can change their password (https://review.opendev.org/672289). However, for this to be actually usable, the user has to know their user_id somehow. As far as I can tell, there is no way to determine the user_id from username without first authenticating, so the users still can't change their expired passwords."
1791111,2018-09-10 09:54:01 UTC,"Hi Lance,"
1791111,2019-06-03 07:26:15 UTC,"Yes, i believe it is forced already. A user that has password expired has only access to the /v3/users/password API. And cannot change anything else."
1791111,2019-06-08 07:42:51 UTC,So this might be a huge change.
1791111,2018-10-10 18:47:48 UTC,"I have added horizon to the bug, as they would need to implement this feature directly."
1791111,2018-10-10 18:48:58 UTC,"Horizon needs to implement a ""change password form"" (or a user must use the /v3/users/password API directly) that does not require direct (normal token) login first. * [in addendum to comment #3]"
1791111,2018-10-10 18:47:21 UTC,"Keystone does not allow ""login"" for locked passwords, which includes ones marked for ""change before first use"". Horizon needs to implement a ""change password form"" (or a user must use the /v3/users/password API directly)."
1791111,2018-10-11 07:22:42 UTC,"Thanks for clarifying Lance and Morgan, we have a lot of customers who only uses horizon or openstackclient so forcing a password change via API is something we cannot do. But I agree this is more a rfe for horizon/openstackclient than for keystone."
1791111,2019-06-03 02:42:43 UTC,"Should this be forced? For example, one user has to change the password when first use, otherwise he cannot do anything."
1791111,2018-10-10 19:06:15 UTC,"I was able to verify this feature works, but more importantly why this was failing for Paul. I did the following"
1791115,2018-09-07 16:46:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/600816"
1791115,2018-09-19 06:39:11 UTC,"Change abandoned by Jose Luis Franco (<email address hidden>) on branch: master
Review: https://review.openstack.org/600816
Reason: multinode-rdocloud takes precedence"
1791115,2018-09-19 12:17:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/603709"
1791115,2018-09-20 15:10:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/604120"
1791115,2018-10-16 06:58:06 UTC,"Change abandoned by Jose Luis Franco (<email address hidden>) on branch: master
Review: https://review.openstack.org/603709
Reason: in favor of https://review.openstack.org/#/c/604120"
1791115,2020-09-18 16:40:10 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.opendev.org/604120
Reason: https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1791115,2018-09-07 08:53:19 UTC,"Affects non voting jobs, remove the critical."
1791115,2018-09-07 09:09:00 UTC,"Looks like the ovs version that is installed at vxlan is very old in RDO, but it's working in reproducer."
1791117,2018-09-07 02:20:37 UTC,"My understanding is that Synaptic is running as root, not as your user, so it only has access to system-wide themes, not themes only in your user directory."
1791125,2018-09-10 18:14:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/601349"
1791125,2018-09-10 23:24:00 UTC,"Reviewed:  https://review.openstack.org/601349
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=b5a4a47977700cb9780c94629b48645612acadb1
Submitter: Zuul
Branch:    master"
1791125,2018-09-11 06:27:37 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/601499"
1791125,2018-09-12 07:59:17 UTC,"Reviewed:  https://review.openstack.org/601499
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=d553b3abcf5434e21df79fc8659fed503f3f8d90
Submitter: Zuul
Branch:    stable/rocky"
1791125,2018-10-24 17:34:17 UTC,This issue was fixed in the openstack/python-novaclient 11.1.0 release.
1791125,2019-11-12 11:35:19 UTC,This issue was fixed in the openstack/python-novaclient 11.0.1 release.
1791128,2019-06-07 20:23:31 UTC,Is this still an issue?
1791134,2018-09-20 06:52:38 UTC,"StacktraceTop:
 g_settings_schema_get_value (schema=0x2f98f20, key=0x30b3ec0 ""launch-count"") at ../../../../gio/gsettingsschema.c:973
 g_settings_schema_key_init (key=key@entry=0x7fff523479c0, schema=0x2f98f20, name=name@entry=0x30b3ec0 ""launch-count"") at ../../../../gio/gsettingsschema.c:1252
 g_settings_get_value (settings=0x2f9b480, key=0x30b3ec0 ""launch-count"") at ../../../../gio/gsettings.c:1203
 g_settings_get_int (settings=<optimized out>, key=<optimized out>) at ../../../../gio/gsettings.c:1843
 ffi_call_unix64 () at ../src/x86/unix64.S:76"
1791138,2018-09-09 10:38:30 UTC,"For 'buntu 18.04
liblensfun1 0.3.2-4 located in: /usr/lib/x86_64-linux-gnu"
1791138,2018-09-09 06:37:52 UTC,Additional insformation.
1791138,2018-09-09 06:59:27 UTC,"From Logs:-
07:45:17 kernel: ufraw[2203]: segfault at 38 ip 00007fde0755db64 sp 00007ffdd844b840 error 4 in liblensfun.so.0.3.2[7fde0754a000+1a000]"
1791138,2019-01-31 16:10:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791138,2019-01-31 16:03:22 UTC,"Thanks to @launch-faygate's analysis in this bug, I came to a workaround on Ubuntu 18.04, and nufraw."
1791140,2018-09-06 18:24:42 UTC,I see.  The in-image hooks called curthooks.handle_cloudconfig() for us.  That's not something that we've done in the ubuntu-curthooks path as maas passes it's datasource config in vai debconf set_selections.
1791140,2018-09-06 18:57:07 UTC,"I believe I've got a fix for this.  Please test the experimental PPA, I've uploaded a new bionic curtin build curtin_18.1-137-gfc8c22fb-0ubuntu1"
1791140,2018-09-06 19:42:44 UTC,The updated Curtin works with no hooks. One thing I noticed is that internal Curtin is creating /etc/cloud/cloud.cfg.d/50-cloudconfig-maas-reporting.cfg while the current hooks create /etc/cloud/cloud.cfg.d/90_datasource.cfg. Do you think we should update the hooks to not create 90_datasource.cfg if CENTOS_CURTHOOK_SUPPORT is in features?
1791140,2018-09-06 23:06:07 UTC,As discussed on IRC 90_datasource.cfg is coming from the finalize hook. I've opened LP:1791189 to handle that separately.
1791141,2018-09-25 21:35:41 UTC,Issued resolved. Fix committed through this review
1791143,2020-09-07 15:25:18 UTC,I'll put this on the wish-list agenda for 21.04
1791143,2018-09-06 19:50:35 UTC,"My main reason for suggesting this is that it seems Canonical is easier on snaps wrt. having rolling upgrades. I don't see a reason debs can't do it, but I notice over and over again Canonical is very conservative upgrading major software versions on debs (which is no criticism, just a constatation)."
1791143,2018-09-06 19:29:09 UTC,"Is there something inherent in snaps that makes this easier or better than debs? For example, do snaps support multiple installable versions of the same package name?"
1791143,2019-08-27 20:00:48 UTC,"As kernels 5.2.0-x will bring zfs 0.8.x to Bionic LTS, I'd like to draw some attention to this request. People will get the 0.8.x zfs module via HWE but won't be able to do much with the major new features without the userland tools."
1791156,2018-09-06 19:29:13 UTC,Here's the Traceback:
1791157,2018-09-10 05:02:36 UTC,"Tried exporting $PYTHONHOME to a couple different ideas, my $PATH looks good. I have no ideas. Every other related bug's remedy does nothing. Gonna reinstall with 18.10 out of frustration if nobody comments tomorrow (Monday)."
1791159,2018-10-12 15:57:54 UTC,"Hi William,"
1791159,2018-10-12 22:09:11 UTC,Is it really RFE? For me it sounds like (valid) bug that get_port_from_device_mac always assume that there is only one unique port to return.
1791159,2018-10-18 22:56:26 UTC,"Yes, I agree with Slawek,. Let's process this as a normal bug. I'll assign it to myself and propose a fix soon."
1791159,2018-10-25 17:30:50 UTC,"Hi, I'm not sure why case 2 works..I didn't spend a lot of time analyzing it as it worked!"
1791159,2019-05-20 08:28:00 UTC,"The different networks are isolated from each other, so it's ip address and mac information can be reused."
1791159,2020-02-15 23:10:02 UTC,"I think we've run into the same bug, however - what we want to achieve differs from the original poster.  We want to be able to bond two interfaces on our guests."
1791159,2020-02-16 12:07:41 UTC,"I found a second, less ugly workaround:"
1791160,2018-09-10 09:06:01 UTC,Further fix in x.4202.
1791160,2018-09-06 19:43:46 UTC,First fix in x.4194.
1791161,2018-10-25 18:06:31 UTC," > Because you do not say what the printers are it is not
 > possible to trace the filter conversions as described
 > in the previous link."
1791161,2019-12-21 14:41:03 UTC,"Thanks for handling this brian_p! Marking as incomplete as we need further information, i.e. does using ""lp"" directly work and if not what options are passed by qpdfview."
1791161,2018-10-25 15:28:02 UTC,"Hello Ben,"
1791162,2018-11-26 20:39:09 UTC,I agree with Jason's suggestion. Bumping this to 3.3-beta1.
1791162,2018-10-24 23:36:37 UTC,I bumped the target to 3.2.2 even though this should probably be targeted at 3.next as a new feature at this point.
1791162,2018-09-06 19:51:17 UTC,"Note the branch linked sits atop the Angular6 branch, since it includes code related to that.  Only the tip commit is for this bug."
1791162,2018-09-06 22:22:40 UTC,Initial results of testing: I think this needs a little more time to bake and should not hold up the beta (though it makes sense to keep this in mind for the release candidate).
1791162,2018-09-07 14:34:07 UTC,"On Thu, Sep 6, 2018 at 6:31 PM Galen Charlton <email address hidden>
wrote:"
1791162,2018-09-06 19:49:09 UTC,http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/berick/lp1791162-makefile-browser-client-build
1791168,2018-09-07 08:13:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791185,2018-09-06 23:53:50 UTC,"images.maas.io gets its images from cloud-images.ubuntu.com/daily so this effects all cloud-image users, not just MAAS. I think we should have a larger discussion with foundations as to whether the image should include the apt list cache."
1791185,2018-09-07 00:07:10 UTC,"I think that if users are using a local
Mirror and, at the same time are updating their images constantly, they
should ensure the local mirror updated as frequently as the images."
1791185,2018-09-07 00:07:30 UTC,"I actually testing forcing an apt-get update with cloud-init, but doesn't solve the issue (presumably because apt doesn't overwrite the more current lists on-disk with the less recent files on the mirror)."
1791185,2018-09-07 00:28:53 UTC,"I agree with the concept that a mirror should not be more than a few days out-of-date, and if so,it should be a red flag. I disagree with the concept that it's okay for that condition to cause intermittent errors elsewhere in the stack, such as in MAAS or LXD. (In other words, this should be a warning, not an error.)"
1791185,2018-09-07 01:14:37 UTC,can you run 'cloud-init collect-logs' and attach output?
1791185,2018-09-07 18:19:50 UTC,"@smoser, sure I'll try to gather that the next time I hit this. Though as I said, it's an intermittent problem in my environment."
1791185,2019-09-19 11:58:54 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1791188,2018-09-08 23:42:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791192,2018-10-06 13:51:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791195,2018-09-11 15:07:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1791195,2018-09-07 01:08:04 UTC,had to blacklist 'ideapad_laptop' to send
1791195,2018-09-07 01:07:04 UTC,apport information
1791195,2018-09-07 01:07:02 UTC,apport information
1791195,2018-09-07 01:07:00 UTC,apport information
1791195,2018-09-07 01:06:56 UTC,apport information
1791195,2018-09-07 01:06:57 UTC,apport information
1791195,2018-10-09 09:14:20 UTC,"I have the same laptop, just different name (Yoga530), and touchpad and touchscreen are still not working on 4.19-rc7."
1791195,2018-09-07 01:06:58 UTC,apport information
1791195,2018-09-07 01:06:52 UTC,apport information
1791195,2018-09-07 01:06:53 UTC,apport information
1791195,2018-09-07 01:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791195,2018-09-07 01:06:42 UTC,apport information
1791195,2018-09-07 01:06:44 UTC,apport information
1791195,2018-09-07 01:06:55 UTC,apport information
1791195,2018-09-07 01:06:47 UTC,apport information
1791195,2018-09-07 01:06:49 UTC,apport information
1791195,2018-09-07 01:06:50 UTC,apport information
1791195,2018-09-07 01:06:46 UTC,apport information
1791196,2019-01-13 14:00:00 UTC,"Hi guys, I managed to have this working (on lubuntu) following https://linuxmusicians.com/viewtopic.php?t=16711"
1791198,2018-09-10 13:10:44 UTC,"Hmm, interesting."
1791198,2018-09-12 05:45:49 UTC,"Hi Daniel,"
1791198,2020-12-22 14:08:49 UTC,same problem for me config provided by ovh
1791199,2018-12-11 19:04:28 UTC,Unassigned; I have added a nicer test runner so the tests can be more easily controlled; they can be retrieved directly from the netplan source.
1791200,2018-09-07 04:23:04 UTC,"The attachment ""patch against version 2.02-2ubuntu8.4 of grub-pc"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1791200,2018-10-03 14:56:32 UTC,"A patch is attached, and it's a well-defined problem. Just needs that I take the patch and test that it behaves correctly to land it."
1791204,2018-10-24 19:49:25 UTC,What does the server create request look like? Is there a block_device_mapping_v2 parameter? Does the flavor have swap specified?
1791204,2020-05-19 10:53:44 UTC,Marking the bug Incomplete. Please but the bug back to New state after you answered Matt's question above.
1791219,2018-09-26 14:49:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791219,2018-11-01 14:51:23 UTC,"Workaround:
```
cd /usr/lib/jvm/java-11-openjdk-amd64
sudo rm src.zip
sudo ln -s ../openjdk-11/lib/src.zip src.zip
```"
1791219,2018-11-01 14:57:46 UTC,Workaround taken from https://github.com/redhat-developer/vscode-java/issues/689#issuecomment-434046529  (solves issue under VSCode unable to show Java JDK source code)
1791219,2018-11-25 18:06:00 UTC,"openjdk-11-source package is completely useless currently.
Please fix the symbolic link, that's really easy to do!"
1791219,2019-05-12 21:54:46 UTC,the same bug in openjdk-10 and openjdk-12
1791219,2019-05-14 15:22:47 UTC,still present on disco-dingo
1791219,2019-05-14 16:54:12 UTC,"Hi,"
1791219,2019-05-14 17:01:39 UTC,"Workaround 2 (alternative for #2):
```
cd /usr/lib/jvm/openjdk-*/lib
sudo bash -c 'mv src.zip ..; ln -s ../src.zip src.zip'
```"
1791221,2018-09-29 19:40:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791224,2020-04-23 19:03:17 UTC,"Closing, as per comment #3."
1791224,2018-09-09 16:37:48 UTC,Does it work if the config drive format is vfat?
1791224,2018-09-10 00:55:36 UTC,I haven't tested it when the config drive format is vfat.
1791224,2018-09-13 01:35:41 UTC,"I saw the latest Pike stable have fixed this issue in https://github.com/openstack/nova/blob/3da97201757c81574e3b03108c95cb29e7d7eba3/nova/virt/libvirt/guest.py#L662, so we can close this bug."
1791233,2020-10-23 12:10:42 UTC,"Hi Rodolfo,"
1791233,2020-10-23 09:48:57 UTC,Hello Sebastian:
1791233,2020-10-22 16:40:22 UTC,"We have the same problem. We are running neutron queens, but the affected code is also present in current neutron master:"
1791241,2018-09-07 21:13:50 UTC,It is reasonable to request that these hooks use -e instead of -x for maximum compatibility.  However:
1791241,2018-09-09 16:57:13 UTC,I now understand you viewpoint. Thanks a lot.
1791245,2018-09-07 07:43:54 UTC,A workaround is to set manually a different MAC address in bond0.netdev:
1791245,2018-09-07 13:15:41 UTC,Problem solved: root cause wa the same id on the 2 machines in /etc/machine-id
1791251,2018-09-07 09:18:35 UTC,Capture some logs from query-engine:
1791251,2018-10-24 09:33:59 UTC,"Build with contrail 4.1 ,also nothing found."
1791253,2019-12-06 10:55:21 UTC,"Hello.
I make error in vlan intarface name.
vlans:
    enp1s01.100:  #error here
            id: 100
            link: enp1s0
            addresses: [ 10.15.1.1/29 ]
    enp1s0.110:
            id: 110
            link: enp1s0
            addresses: [ 10.15.1.11/29 ]
    enp1s0.120:
            id: 120
            link: enp1s0
            addresses: [ 10.15.1.21/29 ]
Than edit config and try to netplan generate & netplan apply, but nothing change.
DEBUG:Skipping non-physical interface: enp1s01.100"
1791253,2019-07-02 16:37:54 UTC,"This is not related just to vlans, it's general configuration that doesn't get applied."
1791256,2018-09-07 12:55:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/600731"
1791256,2018-09-12 13:54:27 UTC,"Reviewed:  https://review.openstack.org/600731
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=8c226961a1e2976c1122610541369ce3386078a1
Submitter: Zuul
Branch:    master"
1791258,2018-09-07 09:14:09 UTC,"The code is also diverged, and the version in ansible-config_template is broken for json format files."
1791258,2019-02-07 15:06:11 UTC,I've put together an etherpad for this to help with execution co-ordination: https://etherpad.openstack.org/p/osa-config-template-migration
1791258,2019-02-08 13:32:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/635838"
1791258,2019-02-08 13:46:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/635841"
1791258,2019-02-11 17:33:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/636182"
1791258,2019-02-12 14:28:34 UTC,"Reviewed:  https://review.openstack.org/635841
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-tests/commit/?id=2462fa482031190474a98764d27675c7bcb8b753
Submitter: Zuul
Branch:    master"
1791258,2019-02-12 15:36:46 UTC,"Reviewed:  https://review.openstack.org/635838
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-plugins/commit/?id=b28590f5bd683d71446f30d0994db839e289cafe
Submitter: Zuul
Branch:    master"
1791258,2019-02-12 18:38:58 UTC,"Reviewed:  https://review.openstack.org/636182
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=0ee07525ed2b9bd07024487ef78c1fae2a432a69
Submitter: Zuul
Branch:    master"
1791258,2020-04-02 12:17:43 UTC,"Change abandoned by Chandan Kumar (raukadah) (<email address hidden>) on branch: master
Review: https://review.opendev.org/632726"
1791261,2018-09-08 11:53:47 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1791265,2018-09-07 09:54:06 UTC,Separated out: bug #1791269
1791265,2019-05-22 17:35:33 UTC,Fixed in stable r18967 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18967>.
1791267,2018-09-07 10:01:18 UTC,Further diagnostic suggestions were to try:
1791267,2018-09-07 10:23:33 UTC,"I got another automated crash prompt to come up.  This generated +bug1791278 (which is marked as private right now, but I shall try to change that when appropriate)."
1791268,2018-09-07 10:05:24 UTC,"I think the VM can arp the internal gateway IP locally, since the ARP request never goes out to the physical world. But in this scenario, the ARP is coming from the outside. So the potential solution maybe:
add some flows or rules to allow only the SNAT node to process internal gateway IP ARP request."
1791275,2018-09-07 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791276,2019-07-05 13:40:23 UTC,I get the same issue when pasting images using the Edit >> Paste Into New Image option. Today I got this error:
1791283,2018-12-05 02:58:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791283,2019-01-23 20:13:20 UTC,"That's still an issue and ""gio open"" does the sale"
1791290,2019-06-03 10:39:24 UTC,Well. it looks like the autopkgtests have become stable since cosmic.
1791290,2019-05-31 02:22:08 UTC,"So I think what's happening here is that finalrd.sh is getting killed because it's running for more than 90s and so the hooks don't get to copy all needed libraries to /run/initramfs (maybe this was obvious, but it wasn't to me). The open-iscsi tests boot an image in system emulation without any kvm acceleration so it's not surprising that things are extremely slow."
1791290,2018-09-13 14:12:32 UTC,"Logging out of session [sid: 1, target: tgt-boot-test-34LfbG, portal: 10.1.1.2,3260]
[  591.782918] sd-execu[1804]: /usr/lib/systemd/system-shutdown/open-iscsi.finalrd failed with exit status 141.
[  591.828276] reboot: Power down"
1791290,2018-11-26 07:28:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791295,2018-09-07 12:53:09 UTC,I believe
1791295,2018-09-07 13:15:18 UTC,"actually no, that's a red herring, this is entirely due to dependencies...."
1791305,2020-08-13 15:43:22 UTC,Ubuntu 18.04 LTS is also affected.
1791307,2019-10-14 09:29:11 UTC,"This appears to be mostly fixed now.
There are still a few minor discrepancies in the file open/save dialogs, but at least colours are correct."
1791307,2020-04-07 12:25:07 UTC,"That last comment was already reported as bug #1868162, no need to derail other bug reports with an unrelated topic."
1791307,2020-04-06 18:04:49 UTC,also the custom dpi setting for the desktop is somehow not passed on (in my case xfce). chromium-browser on a 4k display is readable only by setting the fonts to ridiculous sizes which makes font rendering broken in many web pages.
1791307,2019-10-15 08:19:33 UTC,"Right, this doesn't help with themes that aren't present in gtk-common-themes.
Which is partly why I'm leaving this bug open."
1791307,2019-10-14 19:30:18 UTC,Not fixed for me.  I'm using the Materia Dark theme which still isn't in gtk-common-themes.  Chromium / snap apps don't even pick up on the gtk-prefer-dark-theme setting to at least default to Adwaita Dark.  Chromium opens up super bright and glaring.
1791307,2019-08-07 15:18:08 UTC,"I confirm bwat47's observation (comment #9). The chrome part of the bug is fixed (except for bug #1800260), but open/save dialogs still don't look good."
1791307,2019-03-07 18:52:07 UTC,"Oh, pardon my misunderstanding. Seems like my problem lies in snap itself and is not related to this bug."
1791307,2018-09-07 15:22:44 UTC,"Updated the title and description as I realized this is affecting both versions of the snap (build from the debs, and built from source)."
1791307,2019-03-03 18:16:13 UTC,"Some system themes don’t get styled at all on the snap version. In the attachment there’s a comparison of the Adapta theme on the deb & snap versions of Chromium 72.0.3626.119, running on Xubuntu 18.04."
1791307,2019-02-16 12:57:40 UTC,"The chromium snap is core18 now, and if anything the theming is even worse now. It seems to only partially respect the system theme, and has bugs like white text on white background, instead of properly respecting yaru's theming. I attached a screenshot"
1791307,2018-10-09 14:45:38 UTC,"The chromium snap is built on xenial (16.04), and not against the gnome-3-26 backports PPA (https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/gnome-3-26/+packages)."
1791307,2018-09-11 20:49:56 UTC,"Tested the updated gtk-common-themes from the candidate channel (that includes yaru) in a cosmic VM, and no difference, still seeing a default-looking, adwaita-style theme."
1791307,2018-09-07 16:16:00 UTC,"It could also be that there are incompatibilities in the theming engines between the version of GTK3 that is used to build the snap (from the xenial repositories) and the one on the host system, maybe?"
1791307,2018-09-07 16:14:20 UTC,"For cosmic, this is a relevant issue: https://github.com/snapcrafters/gtk-common-themes/issues/7 (lack of Yaru in the gtk-common-themes snap)."
1791307,2019-03-06 12:29:01 UTC,That's because the Adapta theme is not part of gtk-common-themes.
1791307,2018-09-07 16:00:22 UTC,"In a xenial VM (with Unity and Ambiance as theme), there is indeed a difference between the snap built from the debs, and the snap built from source: the snap built from the debs displays the expected colours and theming for GTK dialogs, whereas the snap built from source displays different colours and theming (Adwaita?)."
1791312,2019-06-13 11:14:17 UTC,"Please test kernel here:
https://people.canonical.com/~khfeng/lp1791312/"
1791312,2019-06-12 16:35:23 UTC,"The patch is included in:
Linux 4.14.125
Linux 4.19.50
Linux 5.1.9
I don't have access to the laptop on which I investigated this problem anymore."
1791312,2019-06-12 16:27:14 UTC,"The patch is included in:
Linux 4.14.125
Linux 4.19.50
Linux 5.1.9"
1791312,2019-05-15 06:36:47 UTC,Whatsapp is well known messenger app.It is used worldwide for messaging when we download status from it we can face problem. By the use of this site https://downloadstatus.xyz we can download it for free.
1791312,2019-05-10 17:56:55 UTC,Being fixed in upstream https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.2&id=2e26ccb119bde03584be53406bbd22e711b0d6e6
1791312,2019-05-06 14:18:23 UTC,"Is there any chance to get the patch implemented into 18.04 LTS?
The flickering screen is really annoying ..."
1791312,2019-02-07 23:02:30 UTC,"Created attachment 143334
output of sudo dmidecode > dmidecode.txr"
1791312,2019-02-12 21:43:08 UTC,"I have done a git bisect:
client@client-LIFEBOOK-AH531 ~/mylinux $ git bisect good
f8a2645ecede4eaf90b3d785f2805c8ecb76d43e is the first bad commit
commit f8a2645ecede4eaf90b3d785f2805c8ecb76d43e
Author: Christian König <email address hidden>
Date:   Wed Apr 16 11:54:21 2014 +0200"
1791312,2019-02-14 22:22:10 UTC,"Created attachment 143381
.config file specifically for Compaq NX9420 on linux 4.19.21"
1791312,2019-02-14 21:36:55 UTC,"The following patch seems to work for me:
client@client-LIFEBOOK-AH531 ~/Téléchargements $ diff -u old/linux-4.19.21/drivers/gpu/drm/radeon/radeon_display.c linux-4.19.21/drivers/gpu/drm/radeon/radeon_display.c
--- old/linux-4.19.21/drivers/gpu/drm/radeon/radeon_display.c	2019-02-12 13:47:27.000000000 -0500
+++ linux-4.19.21/drivers/gpu/drm/radeon/radeon_display.c	2019-02-14 15:29:37.743229474 -0500
@@ -921,12 +921,14 @@
  ref_div_max = max(min(100 / post_div, ref_div_max), 1u);"
1791312,2019-02-12 22:10:32 UTC,"Same problem here: Laptop is a HP 255 G6 based on AMD E2-9000e, Ubuntu is 18.04 64 bits, kernel 4.15.0-45-generic, wide monitor is LG LG 25UM58-P, 2560x1080."
1791312,2019-02-12 21:49:48 UTC,"Created attachment 143368
git show of firt bad commit"
1791312,2019-02-12 21:43:58 UTC,"client@client-LIFEBOOK-AH531 ~/mylinux $ git bisect log
# bad: [a798c10faf62a505d24e5f6213fbaf904a39623f] Linux 3.15-rc2
# good: [c9eaa447e77efe77b7fa4c953bd62de8297fd6c5] Linux 3.15-rc1
git bisect start 'v3.15-rc2' 'v3.15-rc1' '--' 'drivers/gpu/drm/radeon'
# good: [681941c1790b92207334d08ee017007685f35438] drm/radeon: fix VCE fence command
git bisect good 681941c1790b92207334d08ee017007685f35438
# skip: [8902e6f2b832e00e10c6f9e9532f6f63feb4972f] drm/radeon: Improve vramlimit module param documentation
git bisect skip 8902e6f2b832e00e10c6f9e9532f6f63feb4972f
# bad: [bcddee29b0b87af3aeda953840f97b356b24dc5e] drm/radeon/ci: make sure mc ucode is loaded before checking the size
git bisect bad bcddee29b0b87af3aeda953840f97b356b24dc5e
# bad: [f8a2645ecede4eaf90b3d785f2805c8ecb76d43e] drm/radeon: improve PLL params if we don't match exactly v2
git bisect bad f8a2645ecede4eaf90b3d785f2805c8ecb76d43e
# good: [74073c9dd29905645feb6dee03c144657a9844cd] drm/radeon: memory leak on bo reservation failure. v2
git bisect good 74073c9dd29905645feb6dee03c144657a9844cd
# first bad commit: [f8a2645ecede4eaf90b3d785f2805c8ecb76d43e] drm/radeon: improve PLL params if we don't match exactly v2
client@client-LIFEBOOK-AH531 ~/mylinux $"
1791312,2019-06-16 09:26:32 UTC,"I've tested the kernel 4.15.0-52 (from khfeng) on my laptop and found: THE FLICKERING IS GONE!
Screen is O.K. in text and graphic - mode. Console switching works too.
So, Paul's bugfix seems to work! Many thanks!
I found one small thing:
the new radeon.ko - module identifies itself still as
""... Initialized radeon 2.50.0 20080528"";
same like the buggy version.
So it is difficult to distinguish the ""good"" from the ""buggy"" - module."
1791312,2019-02-09 21:13:58 UTC,"Same laptop, same problem.
Thanks for workaround using commands: xrandr ..; sleep 2; xrandr ...;"
1791312,2019-02-07 23:05:29 UTC,"Created attachment 143335
sudo lspci -nnvvk > lspci_while_flickering.txt"
1791312,2019-02-22 13:58:48 UTC,"Paul,"
1791312,2019-07-01 10:41:11 UTC,"today I've updated the kernel to the current version 4.15.0-54 and ... the screen flickers again (!!!)
while the version from https://launchpad.net/~kaihengfeng is working perfectly!!!
The differences:
current kernel 4.15.0-54: radeon.ko version: 2.50.0; module-size: 2342342
kaihengfeng kernel 4.15.0-52 unsigned: radeon.ko version: 2.50.0; module-size: 2343086
So the module in 4.15.0-54 seems NOT to be the same as that one corrected by Paul Dufresne / Kai-Heng Feng.
And: wouldn't it be a good idea to change the radeon.ko version-number too to identify the different versions?"
1791312,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1791312,2019-07-01 14:58:27 UTC,"instead of ""In Progress"" I better set the Status to ""Confirmed"""
1791312,2020-08-25 17:35:06 UTC,https://lkml.org/lkml/2020/8/25/934
1791312,2020-08-18 14:07:05 UTC,"Hello,
... good news! ""lp1861554-2/"" seems to work!
I got: linux-image-5.9.0-rc1+
giving:
- Linux version 5.9.0-rc1+ (khfeng@ubuntu)
- /lib/modules/5.9.0-rc1+/kernel/drivers/gpu/drm/radeon/radeon.ko
  size: 2244937 date: Aug 17 11:19
- radeon driver still tells: 2.50.0 20080528 (see: dmesg)
  (shouldn't it be better to modify it's version / date ??)"
1791312,2020-08-18 06:19:09 UTC,"Ok, can you please test this one:
https://people.canonical.com/~khfeng/lp1861554-2/"
1791312,2020-08-14 10:45:19 UTC,"Hello,
I've tested your kernel  Linux version 5.8.0+ (khfeng@ubuntu) and
unfortunately the screen  on my system flickers again!"
1791312,2020-08-14 10:31:20 UTC,"Hello,
I've tested the khfeng-kernel  Linux version 5.8.0+ (khfeng@ubuntu) and unfortunately the screen  on my system flickers again!"
1791312,2020-08-12 15:40:38 UTC,"Werner,
Can you please test the kernel here:
https://people.canonical.com/~khfeng/lp1861554/"
1791312,2020-06-08 15:36:32 UTC,"I still have flickering problems with the X1300, kernel 5.4, Ubuntu 20.04."
1791312,2020-02-18 18:40:56 UTC,"The patch 2e26ccb119bde03584be53406bbd22e711b0d6e6 created for this bug brokes the ATI Radeon HD3450/70 RV620 card. Please take a look at bug #1861554 and freedesktop issue here:
https://gitlab.freedesktop.org/drm/amd/issues/1045"
1791312,2019-11-23 02:28:32 UTC,"thank you for your tip, we can face a problem. Can I use free this"
1791312,2019-08-27 06:43:12 UTC,"I did the verification with 18.04 ""Bionic"" and it was o.k; see Comment# 72.
But I don't have a 16.04 ""Xenial"" installation, so I can't verify this version."
1791312,2019-08-22 16:17:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1791312,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1791312,2019-07-07 08:58:11 UTC,"I've tested the kernel from
http://at.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
 linux-headers-4.15.0-55-generic   Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
 linux-image-4.15.0-55-generic   Signed kernel image generic
 linux-modules-4.15.0-55-generic   Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
 linux-modules-extra-4.15.0-55-generic   Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
and: NO flickering screen! So the problem seems to be solved!"
1791312,2019-07-03 13:06:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1791312,2019-07-03 13:02:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1791312,2019-07-03 11:03:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1791312,2019-07-02 12:37:58 UTC,"Hi Werner,"
1791312,2019-07-01 14:29:26 UTC,Fix in Bionic does NOT work; see comment #65
1791312,2019-02-07 22:54:34 UTC,"Created attachment 143333
dufrp's dmesg for kernel 5.0rc5 (xstarted as root) with no flickering"
1791312,2019-04-15 13:07:31 UTC,"Thanks to Paul Dufresne a patch in ""radeon_display.c"" seems to fix the bug.
So the radeon maintainers should work on an upstream fix."
1791312,2019-02-07 22:04:37 UTC,"Created attachment 143331
Xorg.0.log for kernel 50rc5 with flickering"
1791312,2018-11-04 14:48:47 UTC,"(In reply to Alex Deucher from comment #1)

> Any chance you can narrow down when the regression occurred and bisect it
> using git?  Please attach your dmesg output and xorg log (if using X).
"
1791312,2018-11-04 14:43:28 UTC,"(In reply to Alex Deucher from comment #1)

> Any chance you can narrow down when the regression occurred and bisect it
> using git?  Please attach your dmesg output and xorg log (if using X).
"
1791312,2018-11-04 14:41:20 UTC,more tests with flickering screen:
1791312,2018-10-30 15:54:54 UTC,some more tests with different systems give the following table:
1791312,2018-10-24 13:29:58 UTC,Additional Information:
1791312,2018-10-23 17:07:33 UTC,"Created attachment 142156
dmesg Ubuntu14.04, Kernel4.4.0-133, radeon 2.43.0, screen flickering"
1791312,2018-10-23 16:45:12 UTC,"- I attached 2 dmesg-listings;
  booting Ubuntu14.04, Kernel3.13 -> screen is o.k.; no flickering
  booting Ubuntu18.04, Kernel4.15 -> screen flickers.
- no Xorg log since the flickering happens already in text-mode
- I did the following test (on Ubuntu18.04):
  . boot with radeon.modeset=0 (thus: disable radeon driver)
    -> screen o.k.; NO flickering
  . then sudo modprobe -v radeon modeset=1
    -> and the flickering starts ..."
1791312,2018-10-23 16:34:59 UTC,"Created attachment 142155
dmesg Ubuntu18.04, Kernel4.15.0-36, radeon 2.50.0, screen flickering"
1791312,2018-12-04 14:39:31 UTC,"(In reply to Werner Lueckel from comment #8)

>
> - BUT: what can I do when support for ""14.04 trusty"" ends?
"
1791312,2018-10-23 16:31:25 UTC,"Created attachment 142154
dmesg Ubuntu14.04, Kernel3.13.0-160, radeon 2.36.0, screen O.K."
1791312,2018-10-22 16:07:16 UTC,"my laptop: HP Compaq nx9420
my grafic card:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])
screen resolution: 1680x1050@60.1"
1791312,2018-09-17 07:38:35 UTC,"Sorry, but it turned out that the flickering-issue is NOT really fixed with the upstream-kernel.
Sometimes a boot again ends in a flickering screen as before.
Now I have the following scenario:
- boot 14.04.5 LTS with kernel 3.13.0-157
  -> screen is ALWAYS o.k.; NO flickering
- boot 18.04.1 LTS with upstream-kernel 4.19.0-041900rc3
  -> USUALLY the screen is o.k; BUT SOMETIMES the screen flickers as before
  I found no special reason that may cause/avoid the flickering; just reboot and watch ...
  and if the screen flickers, reboot again and the screen may be o.k. ..."
1791312,2018-09-15 09:20:40 UTC,"I tested the flickering-issue with the upstream-kernel
 ""linux-image-unsigned-4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832_amd64.deb""
and it seemed to be fixed!
No more flickering.
So I added the tag ""kernel-fixed-upstream"" to this report."
1791312,2018-09-11 15:06:27 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1791312,2018-09-09 15:57:25 UTC,I attached a short video-clip (MOV03422.MPG) showing the flickering screen; that flickering continues in grafic-mode too ...
1791312,2018-09-08 16:18:21 UTC,"you can find the missing logfile as attachment:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+attachment/5186052/+files/apport.linux-image-4.15.0-33-generic.s5j_wb2y.apport"
1791312,2018-09-07 15:00:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791312,2019-02-07 22:53:04 UTC,"Created attachment 143332
dufrp's Xorg.0.log for kernel 5.0rc5 (xstart as root) with no flickering"
1791312,2018-10-22 18:14:39 UTC,Any chance you can narrow down when the regression occurred and bisect it using git?  Please attach your dmesg output and xorg log (if using X).
1791312,2018-12-07 16:40:37 UTC,"thank you for your tip, but radeon.new_pll=0 gives me
... radeon: unknown parameter 'new_pll' ignored
And: I cannot find 'new_pll' in 'modinfo -p radeon';
So new_pll seems to be (no longer?) a radeon parameter."
1791312,2019-02-19 21:25:11 UTC,"Created attachment 143413
patch radeon-display.c for latest kernel (5.0.0-rc7)"
1791312,2019-02-01 01:55:35 UTC,"I guess I would rather add the two option lines (with same indentation) to:
file:///usr/share/X11/xorg.conf.d/10-radeon.conf"
1791312,2019-02-01 01:41:51 UTC,"The bug have been reported upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=108514"
1791312,2019-02-07 21:36:20 UTC,"Created attachment 143329
dufresnep's xorg log for kernel 4.15.0 with drm.debug=0 strangely without flickering"
1791312,2019-02-07 21:34:51 UTC,"Created attachment 143328
dufresnep's dmesg for kernel 4.15.0-45-generic with drm.debug=0 with strangely no flickering"
1791312,2019-02-07 19:54:39 UTC,"Created attachment 143327
dufresnep's Xorg.0.log for kernel 4.15.0-45 (Mint 19) with drm.debug=4 lots of flickering"
1791312,2019-02-07 19:53:01 UTC,"Created attachment 143326
dufresnep's dmesg for kernel 4.15.0-45-generic (Linux Mint) with drm.debug=4 with a lot of flickering"
1791312,2019-02-07 19:40:15 UTC,"Created attachment 143325
Paul Dufresne's Xorg.0.log for k3.14.79 no_flickering"
1791312,2019-02-07 19:38:14 UTC,"Created attachment 143324
Paul's dmesg with drm.debug=4 on kernel 3.14_79 (No flickering)"
1791312,2019-02-06 22:42:55 UTC,"I had determined that 3.15-rc2 was the first version where flickering appears.
I guess it could be related to:
https://lists.freedesktop.org/archives/dri-devel/2014-April/057800.html"
1791312,2019-02-06 19:34:48 UTC,"I am comparing PLL values for a not flickering kernel:
Linux version 3.14.79-031479-generic
and version 4.15 (recent one):"
1791312,2019-02-07 21:58:28 UTC,"Created attachment 143330
dmesg for kernel 5.0rc5 with flickering and debug=4"
1791312,2019-02-05 02:35:06 UTC,"Indeed, the two radeon parameters for PLL mention in previous message
does not seems to appear anymore in modinfo radeon."
1791312,2019-02-04 22:38:01 UTC,"From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/CHANGES
I see the folowing changes for radeon:"
1791312,2019-02-04 21:04:30 UTC,"Ok, I have access at ""work"" on a Compaq nx9420, for a few days."
1791312,2019-02-02 15:43:48 UTC,".. as recommended I tried 3.14.79-031479-generic;
giving me radeon.ko version  2.37.0 and the screen is o.k. No flickering.
btw. I had the same result e.g. with ""puppy_tahr 6.0.5 boot CD"" which has the same radeon-version (2.37.0).
My guess: the flickering-problem starts with radeon 2.39.0 upward. See my table above (a little messed-up due to lacking blanks)."
1791312,2019-02-01 17:46:21 UTC,"I just retried by installing headers, then reinstall kernel-generic.
This time wifi works.
Note that these packages won't show in Synaptic.
Will show in dpkg -l|grep kernel. Use dpkg -r to remove them."
1791312,2019-02-01 16:45:40 UTC,"Well, I tested on my laptop with:
paul@paul-NC210-NC110:~$ cat /proc/version
Linux version 3.14.79-031479-generic (kernel@gloin) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #20160910530 SMP Sun Sep 11 09:41:06 UTC 2016"
1791312,2019-02-01 15:42:38 UTC,"Thanks for trying the tearfree option! (ok, it don't work)"
1791312,2019-02-01 10:50:30 UTC,"I tried the glamor / tearfree - advice, but: with NO success; still flickering.
And, btw.: I don't think the flickering is an Xorg-issue;
it starts in ""textmode"" (!!) as soon as the radeon-kernel-driver loads. I think the kernel-driver
does NOT read Xorg-configurations."
1791312,2019-02-01 02:10:38 UTC,"Someone said:
""I tried this with a Ubuntu 17.10 and could not boot. I had to use a rescue boot and remove the lines again to get it up and running.""
from:https://askubuntu.com/questions/794865/16-04-ati-mobility-radeon-x1600-full-resolution-flickering
So, try with care!"
1791312,2019-02-06 03:11:33 UTC,"Well, It seems to take more than 12 hours ( I did stopped it ) to compile a
kernel (many features deactivated) on my atom based laptop. Will retry."
1791320,2019-04-05 09:02:45 UTC,I solved this by limiting the number of mounts in one of my docker containers.
1791320,2019-04-05 06:02:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791320,2018-09-07 15:13:46 UTC,apport information
1791320,2018-09-07 15:13:42 UTC,apport information
1791320,2018-09-07 15:13:40 UTC,apport information
1791320,2018-09-07 15:13:39 UTC,apport information
1791320,2018-09-07 15:13:38 UTC,apport information
1791320,2018-09-07 15:13:36 UTC,apport information
1791320,2018-09-07 15:13:37 UTC,apport information
1791320,2018-09-07 15:00:24 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791320,2018-09-07 15:13:27 UTC,apport information
1791320,2018-09-07 15:13:28 UTC,apport information
1791320,2018-09-07 15:13:30 UTC,apport information
1791320,2018-09-07 15:13:31 UTC,apport information
1791320,2018-09-07 15:13:33 UTC,apport information
1791320,2018-09-07 15:13:34 UTC,apport information
1791321,2018-09-19 08:40:05 UTC,I'll ping upstream for feedback if v4.19-rc4 still exhibits the bug.
1791321,2018-09-19 08:39:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1791321,2018-09-11 18:33:35 UTC,"Yes, the test kernel you uploaded works fine.  Thanks."
1791321,2018-09-11 17:52:10 UTC,"I built a test kernel with a revert of commit 3cd091a773936c54344a519f7ee1379ccb620bee.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1791321"
1791321,2018-09-11 15:13:51 UTC,Forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=201091.
1791321,2018-09-10 22:07:31 UTC,"3cd091a773936c54344a519f7ee1379ccb620bee is the first bad commit
commit 3cd091a773936c54344a519f7ee1379ccb620bee
Author: Rafael J. Wysocki <email address hidden>
Date:   Fri Feb 9 22:55:28 2018 +0100"
1791321,2018-09-10 22:04:23 UTC,apport information
1791321,2018-09-10 22:04:22 UTC,apport information
1791321,2018-09-20 19:14:05 UTC,"v4.19-rc4 works, v4.18.8 still has the bug."
1791321,2018-09-10 22:04:18 UTC,apport information
1791321,2018-09-10 22:04:16 UTC,apport information
1791321,2018-09-10 22:04:20 UTC,apport information
1791321,2018-09-10 22:04:04 UTC,apport information
1791321,2018-09-10 22:04:06 UTC,apport information
1791321,2018-09-10 22:04:07 UTC,apport information
1791321,2018-09-07 15:00:29 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791321,2018-09-10 22:04:10 UTC,apport information
1791321,2018-09-10 22:04:11 UTC,apport information
1791321,2018-09-10 22:04:12 UTC,apport information
1791321,2018-09-10 22:04:14 UTC,apport information
1791321,2018-09-10 22:04:09 UTC,apport information
1791323,2018-09-07 15:41:15 UTC,apport information
1791323,2018-09-12 23:23:30 UTC,Confirmed in the latest RC kernel:
1791323,2018-09-12 19:47:19 UTC,"Hi Joseph,"
1791323,2018-09-12 19:24:12 UTC,"Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced.   If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem."
1791323,2018-09-12 19:23:36 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1791323,2018-09-07 15:41:21 UTC,apport information
1791323,2018-09-07 15:41:19 UTC,apport information
1791323,2018-09-07 15:41:17 UTC,apport information
1791323,2018-09-07 15:41:14 UTC,apport information
1791323,2018-09-07 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791323,2018-09-07 15:41:10 UTC,apport information
1791323,2018-09-07 15:41:09 UTC,apport information
1791323,2018-09-07 15:41:06 UTC,apport information
1791323,2018-09-07 15:41:05 UTC,apport information
1791323,2018-09-07 15:41:03 UTC,apport information
1791323,2018-09-07 15:41:01 UTC,apport information
1791323,2018-09-07 15:41:00 UTC,apport information
1791323,2018-09-07 15:40:58 UTC,apport information
1791323,2018-09-07 15:40:56 UTC,apport information
1791323,2018-09-07 15:41:12 UTC,apport information
1791333,2018-09-10 19:09:27 UTC,"As stated before, we need to find the root cause before we submit a fix. Your description doesn't mention what version of snapcraft you used."
1791333,2018-09-11 07:10:10 UTC,"@Tony, different snaps increase their size in different quantities. For some reason NM is especially affected, with 5 additional MB. But MM snap increases only in 1 MB. The easiest way to check if something is affected by this bug is by running the 'file' command on a binary. If you see"
1791334,2020-05-12 14:59:22 UTC,"From the dupe, the reword/redesign should consider ""The terms ""identity provider"" and ""service provider"" are not mentioned at all. Ideally the page contains some status text, e.g. ""Signing in to Ubuntu Etherpad…""."""
1791334,2020-05-13 11:29:38 UTC,"Progress toward being signed in. I had in mind an indeterminate progress bar, but a spinner would work just as well."
1791345,2018-10-08 08:22:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791355,2019-05-31 10:15:47 UTC,Fixed by: https://review.opendev.org/#/c/582612/
1791355,2019-05-22 08:19:33 UTC,We now install Docker CE using the new repos - fixed in Stein and Rocky.
1791355,2019-05-21 16:00:06 UTC,We should install 'docker.io' from Ubuntu repository instead of external one ;D
1791355,2019-01-08 19:05:53 UTC,"I get the same problem
The kolla-ansible script change my apt-docker repo automatically
How can i prevent that ?"
1791355,2018-10-29 15:51:49 UTC,You can install docker before running bootstrap servers and then remove the docker install step from /kolla-ansible/ansible/roles/baremetal/defaults/main.yaml.  You could also update the docker install step to install docker on 18.04.
1791355,2018-10-29 14:19:31 UTC,Is there a known workaround that allows Ubuntu 18.04 installations despite this issue?
1791355,2018-09-13 03:45:06 UTC,"Change abandoned by Chason Chan (<email address hidden>) on branch: master
Review: https://review.openstack.org/601975
Reason: OK, abandon this one."
1791355,2018-10-30 08:25:54 UTC,Thanks for the hint!
1791355,2018-09-12 11:09:21 UTC,fix in https://review.openstack.org/601975
1791363,2019-05-24 14:24:03 UTC,@daxtens What if I want to force MTU to 1400 for all my cloned systems?
1791363,2018-09-10 06:49:02 UTC,"Hi,"
1791363,2018-09-10 07:24:03 UTC,We do actually have a bolded note in the docs for this! But it isn't in the version in Bionic.
1791370,2019-06-28 12:16:58 UTC,Patch for review
1791370,2019-07-03 21:55:37 UTC,Patch lgtm.
1791370,2019-07-08 16:29:45 UTC,This bug was fixed in the package secureboot-db - 1.5
1791370,2019-07-15 16:11:56 UTC,This is a low-priority bug and I had no expectation that this change needed to be SRUed into stable releases.  Introducing a systemd unit is relatively high risk for an SRU because of its potential impact on boot speed/timing/ordering.  I am declining this as an SRU.
1791370,2019-07-15 16:12:32 UTC,"An upload of secureboot-db to disco-proposed has been rejected from the upload queue for the following reason: ""Not necessary or appropriate to SRU""."
1791370,2019-07-15 16:13:17 UTC,"An upload of secureboot-db to bionic-proposed has been rejected from the upload queue for the following reason: ""Not necessary or appropriate to SRU""."
1791370,2019-07-15 16:13:48 UTC,"An upload of secureboot-db to xenial-proposed has been rejected from the upload queue for the following reason: ""Not necessary or appropriate to SRU""."
1791370,2019-06-28 12:19:16 UTC,Actual patch.
1791374,2018-09-07 20:59:34 UTC,I've managed to build with this patch.
1791374,2018-09-07 21:01:52 UTC,"Also, please, remove commas and add libboost-serialization-dev in INSTALL file:
 sudo apt-get install debhelper, cmake, libindicate-qt-dev, libmpd-dev, libqt4-dev, libboost-dev"
1791380,2018-10-09 13:16:39 UTC,"Processing triggers for initramfs-tools (0.122ubuntu8.1) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-1017-raspi2
WARNING: missing /lib/modules/4.4.0-1017-raspi2
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.4.0-1017-raspi2: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
cryptsetup: WARNING: could not determine root device from /etc/fstab
Warning: root device  does not exist"
1791387,2018-09-21 19:08:59 UTC,"Btw, I suppose its already supported in SM. Isnt that enough to validate? Customer is not going to use any of our provisioning anyways.. Correct me if i'm wrong."
1791389,2018-09-07 11:39:30 UTC,"Created attachment 278363
dmesg 4.18.5-gnu"
1791389,2018-09-07 11:45:28 UTC,"Created attachment 278365
# lspci -vvnn"
1791389,2018-09-07 11:51:34 UTC,"On Fri, Sep 07, 2018 at 11:39:30AM +0000, <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=201037
>
>             Bug ID: 201037
>            Summary: usb 3-1: device descriptor read/64, error -110
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 4.18.5-gnu
"
1791389,2018-09-07 15:30:23 UTC,"Hello Greg Kroah-Hartman,"
1791389,2018-09-07 23:46:59 UTC,"Hello,"
1791389,2018-09-08 00:00:07 UTC,This change was made by a bot.
1791406,2018-09-17 14:51:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1791414,2018-09-17 14:50:40 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1791421,2018-11-13 07:17:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791422,2018-09-17 12:03:09 UTC,"Hi,
Did you see any issues in hplip driver installation or any functionality issues? Were you able to use the driver functionalities after closing this warning message?"
1791422,2018-10-11 05:52:41 UTC,Errors during driver diagnostics:
1791425,2019-11-14 07:53:04 UTC,"The GCC 7 branch is being closed, re-targeting to GCC 8.4."
1791425,2020-03-04 09:34:23 UTC,"GCC 8.4.0 has been released, adjusting target milestone."
1791425,2018-08-14 16:46:52 UTC,Confirmed.  G++ 5 compiles it fine.
1791425,2019-04-16 19:07:14 UTC,"Author: jakub
Date: Tue Apr 16 19:06:41 2019
New Revision: 270396"
1791425,2018-08-14 16:38:22 UTC,"Created attachment 44539
Small test case"
1791425,2019-04-16 13:42:38 UTC,It seems to be fixed on the last version available on wandbox.org (gcc HEAD 9.0.1 201904): https://wandbox.org/permlink/Tu4T8jEXDDtDw0OS
1791425,2018-08-14 17:42:03 UTC,"struct B {
  double x;
  bool isfreex;
  bool isfreey;"
1791425,2018-10-26 10:13:46 UTC,GCC 6 branch is being closed
1791425,2018-08-14 16:36:54 UTC,"Created attachment 44538
preprocessed file of a small test case for the constexpr crash"
1791425,2018-08-14 17:46:05 UTC,Started with r230365 -- Merge C++ delayed folding branch..
1791425,2019-02-21 23:12:21 UTC,The patch for 89285 seems to have fixed this on trunk.
1791425,2018-08-24 15:25:55 UTC,"Another reason why we badly need to finish PR81601.
The constexpr evaluator really can't cope well with these BIT_FIELD_REFs, they read multiple fields at once, or could also read some uninitialized bits in between and mask them off, etc.
So at minimum we'd need to disable these optimizations while folding constexpr declared functions and if the fields don't have INTEGRAL_TYPE or the bit field reference covers more than one field."
1791425,2018-09-26 16:17:16 UTC,"Reassigned to gcc-7, which is the source package of the actual compiler, while gcc-defaults only provides metapackages."
1791427,2019-11-16 13:58:01 UTC,Hi guys! I've change BIOS settings bellow and the bug disappear.
1791427,2019-11-19 17:56:39 UTC,"Yes, but now your battery will die in like 4 hours in sleep mode, because you're not getting S3 mode."
1791427,2019-11-19 15:57:28 UTC,"Guys, try to set sleep state from Linux to Windows in BIOS settings. It seems worked for me."
1791427,2019-11-19 11:20:19 UTC,"@thorstenr-42: Also have a nfc model so still facing the same dead touchpad issues.
I've never built a custom kernel before, just loaded a kernel module for a wifi nic that didn't have drivers in the kernel. How do you go about building and running this?"
1791427,2019-11-18 22:28:28 UTC,"@sssss: Yes, I have a model with nfc typ: 20KGS03900"
1791427,2019-11-18 05:36:18 UTC,Does the nosleep workaround work for everyone?
1791427,2019-11-17 18:33:58 UTC,@thorsten Do you have a model with NFC?
1791427,2019-11-17 17:37:29 UTC,How to reproduce this bug on Lenovo X1 Carbon 6th
1791427,2019-11-17 16:26:10 UTC,"I do not just claim that, I am just sharing what helped me... With older kernels my touchpad hardly survived 5 suspends. With 5.3 it just works (4 weeks without a dead touchpad with at least 50 suspends). Okay the trackpoint issue is still there but i give a ..."
1791427,2019-11-26 20:11:10 UTC,@thorstenr-42: Very good to hear that it works for you since kernel 5.3! Could you tell us whether you have a certain configuration in the following files?
1791427,2019-11-17 15:11:28 UTC,I'm on 5.3 and it doesn't work:
1791427,2019-11-17 14:25:03 UTC,"People claim repeatedly that the problem is fixed when it is not. I will believe it only when I see it and indeed I will test it only with further reason to believe it. Sad, but reasonable."
1791427,2019-11-17 11:25:25 UTC,"The touchpad problem seems to be solved (for me) using linux 5.3. The trackpoint sometimes still dies but the touchpad keeps working. Luckily, i don't care about the trackpoint..."
1791427,2019-11-16 16:18:38 UTC,I was happy early because the bug appeared again :(
1791427,2019-11-16 15:58:46 UTC,@pavel just tried it on the model with NFC and it didn't help or change anything. (20KH006HRT)
1791427,2019-11-16 14:23:17 UTC,@Pavel
1791427,2019-11-01 13:47:30 UTC,What is the most effortless way of running the Windows firmware updates on a Linux machine? Are there live CD images I could use for this?
1791427,2019-11-17 15:17:07 UTC,"Same here, I have Ubuntu with 5.3.11 kernel and the issue is still there"
1791427,2018-09-08 12:30:08 UTC,This change was made by a bot.
1791427,2019-12-09 17:47:01 UTC,"Hi guys, I also suffer from this problem on my X1 6th gen on Ubuntu as well as Fedora."
1791427,2020-10-28 02:13:40 UTC,"I spoke too soon. Deep sleep works now, and the touchpad keeps working, but only - even with the new motherboard - if I keep the NFC *enabled* in the BIOS. And the trackpoint does not work under Linux. At all. At any time (at least on my distro) and even with a very recent kernel."
1791427,2020-10-16 02:37:59 UTC,"Somewhere in this long thread, I think, an engineer suggested the following."
1791427,2020-09-20 08:09:02 UTC,"The problem is still there for me too. Quite often the track point is dead after wake up from sleep (there is never a problem with the track pad) and I have to fix the track point with
echo -n ""none"" | sudo tee /sys/bus/serio/devices/serio1/drvctl
echo -n ""reconnect"" | sudo tee /sys/bus/serio/devices/serio1/drvctl
The problem has been around for a couple of years and is quite annoying."
1791427,2020-09-20 01:53:14 UTC,"any news on the patch?
I still have this issue"
1791427,2020-07-29 04:45:58 UTC,@Kai-Heng
1791427,2020-07-29 03:39:23 UTC,"Yea they need to come from the same system.
I guess just stick to s2idle then."
1791427,2020-07-29 02:59:09 UTC,@Kai-Heng
1791427,2019-12-03 22:12:57 UTC,@jnns
1791427,2020-07-29 02:31:56 UTC,Can someone attach dmesg when it uses S2Idle and when it uses S3?
1791427,2020-07-28 16:36:42 UTC,Anyone know what happened to Aaron's patch? The discussion at https://patchwork.kernel.org/patch/10822515/ ends on November last year with this question from Kai-Heng:
1791427,2020-07-17 04:34:54 UTC,@ssss
1791427,2019-12-30 09:34:55 UTC,Here is another screenshot that shows that I have Linux sleep enabled.
1791427,2019-12-30 09:33:32 UTC,I just did a little experiment and I think now I have trackpad waking up after s3 sleep:
1791427,2019-12-26 17:47:05 UTC,"attached devices , xinput and Xorg log"
1791427,2019-12-26 17:24:54 UTC,even worse it didn't detect/worked since booting up my laptop. removing from modprobe and adding it back still did not work :(
1791427,2019-12-26 17:22:28 UTC,"I'm having this issue with my Lenovo x240 , running ubuntu 19.10 with kernel 5.3.0-26-generic"
1791427,2020-07-28 17:38:03 UTC,"'Anyone tried a very recent kernel and can confirm the issue is still there [..]?' I tried 5.6.19, I think it was (so, moderately recently) and I can confirm the problem is there. Also, I've looked at the release notes for various 5.7 kernels and not seen a sign of the patch."
1791427,2019-12-03 20:41:15 UTC,"My X1 Carbon 6 Gen still suffers from the problem, no doubt about it. I'm currently using Linux 5.3.0-24-generic.
But I was able to migitate the rate of occurence by a large degree using the following configuration. Please not that I have no idea if anything of this is actually relevant or just me being a superstitious pidgeon. Hope it helps someone."
1791427,2019-10-16 18:15:54 UTC,dr_strangehate:
1791427,2018-11-22 18:09:22 UTC,"C'mon guys, this stuff is hopeless. As I said, I'm using Linux Mint. It lacks the /etc/gdm3 folder - perhaps because (I don't know) it uses a different 'greeter'. Nor does Mint use Wayland."
1791427,2018-11-05 23:59:12 UTC,Is the patch described on the following webpage - a patch has arrived on my system - relevant?
1791427,2018-11-04 14:37:59 UTC,@rriemann
1791427,2018-11-02 18:35:00 UTC,"For reference, this is the link to the Redhat/Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1442699 (no solution there as for now)"
1791427,2018-10-23 18:45:10 UTC,"This same thing happens to all distros - I've seen a bug report like this on Redhat's bug tracker (Fedora), and tried other distros, such as Manjaro. So it's not just Debian or Ubuntu I guess. I assume developers that take care of individual distros can make changes to the kernel and then send them up to the mainline version to be available for everyone. It's just that nobody cares enough, since it's not a super popular model I guess."
1791427,2018-10-23 18:32:42 UTC,@dr-strangehate
1791427,2018-10-23 09:14:10 UTC,@NJ
1791427,2018-10-22 23:25:29 UTC,@dr-strangehate
1791427,2019-10-15 21:08:45 UTC,"I'm just a user. I can only say it worked for me and all the people I asked and who listened, which was very few. So I cannot give you any guarantees if that is what you want :). Most people don't want to try it because it's either too much hassle (windows install) or think that for some reason an update through windows will break the laptop."
1791427,2018-10-18 11:20:09 UTC,"Here's some more dmesg output that I get after the first or second suspend (sometimes third, it's very random). Once I get this, it's impossible to reconnect the trackpad and trackpoint by any means:"
1791427,2018-10-17 06:58:24 UTC,"I also hit this problem in my x220t + ubuntu 18.04, I successfully fix it by using the following workaround:"
1791427,2018-09-15 23:20:45 UTC,I am on Mint 19 with kernel 20KHCTO1WW on a X1 model 20KHCTO1WW. I would be happy to contribute to any necessary testing. I use the synaptic touchpad driver.
1791427,2018-09-12 14:44:59 UTC,"Hi, i did a complete new installation with the ubuntu 18.04.1 iso and the touchpad was always working after suspend/resume only the trackpoints gets lost. Does it make a difference if s3 is available during installation?"
1791427,2018-09-12 07:23:48 UTC,"AaronMa, does your model have NFC? You can tell by a symbol printed on the touchpad just below the middle physical button of the trackpoint, looks like this one: https://i.redd.it/el9qai4evu811.jpg"
1791427,2018-09-12 01:53:18 UTC,Thanks for the detail test.
1791427,2018-09-11 08:52:33 UTC,"a small update: the tlp settings have no effect and are thus not necessary... Even with the settings the trackpoint is sometimes not working after resume. However, an additional suspend/resume does activate the trackpoint again!"
1791427,2018-09-10 12:23:59 UTC,"Hi, for me the following combination for ubuntu 18.04 using x1c6 with nfc (20KG) seems to be working:"
1791427,2018-10-17 16:50:12 UTC,@Hua Zhang
1791427,2018-11-08 15:46:38 UTC,Root cause should be broke communication via PS/2 bus.
1791427,2018-11-06 13:23:20 UTC,"To answer my own question: that update removed a blacklisting in blacklist.conf. The result of that removal, on my system, was that the touchpad stopped working after suspend, even when S3 was not enabled. A few hacks get the touchpad working again, but not properly - edge-scrolling, and I suspect some other functions, are lost."
1791427,2018-11-10 04:55:25 UTC,Hi all:
1791427,2018-11-22 17:53:09 UTC,"Try this:
1. Edit /etc/gdm3/custom.conf as root/with sudo
2. Uncomment the line WaylandEnable=false so it looks like below:
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false
3. Reboot and see if the issue still occurs."
1791427,2018-11-22 11:33:11 UTC,"Thanks for that. The ls reveals 1f.*4* on my system, but using that in the file does *not* work for my system, at least not after a long sleep."
1791427,2018-11-22 10:19:30 UTC,ALinuxUser
1791427,2018-11-22 00:05:12 UTC,"The above fix has a chance of working only if one's blacklisf.conf (/etc/modprobe.d/blacklist.conf, on my Linux Mint system) does *not* to blacklist 'i2c_i801'. Debian did recently remove that blacklisting."
1791427,2018-11-21 17:30:17 UTC,mr_tron
1791427,2018-11-21 08:52:46 UTC,"I have same bug on thinkpad t440s.
And that fix works for me:
```
# /etc/systemd/system/touchpad-sleep.service
# restore touchpad on suspend"
1791427,2018-11-08 17:02:10 UTC,"That is informative. Thank you. However: Lenovo support tends to be
clueless with Linux, so finding out from Lenovo when this fix will ever
appear is hard. Might you or someone else be able to advise on that?"
1791427,2018-11-19 23:33:43 UTC,"So, I've decided to check the new firmware. I installed Windows 10 (wiping out my Ubuntu install in the process), installed Lenovo Vantage and installed all firmware updates that it allowed me to, including touchpad and trackpoint firmware."
1791427,2018-11-20 01:37:09 UTC,"@dr_strangehate, thanks for test details."
1791427,2018-11-13 00:50:07 UTC,Cf. perhaps the following.
1791427,2018-11-13 00:49:01 UTC,"Thanks. It was hard even to run 'SynReflash.exe /Q': I had to install a touchpad driver/update, or two and then locate the relevant folder. (All this on a Windows PreBoot Environment. I tried to use a WindowsToGo installation, but after hours of creation and booting it errored out. When the command did run, it showed 'version 0.0' (*sic*)."
1791427,2018-11-12 14:02:47 UTC,Could you confirm the following info?
1791427,2018-11-10 13:33:46 UTC,"Next, more important result: no, *the touchpad still doesn't work* after (a fairly long) suspend."
1791427,2018-11-10 13:03:16 UTC,"First results: a recent update from Debian removed (on my Mint system) a blacklisting in blacklist.conf for '12c_i801'. I find that, unless I reactivate that blacklisting, touchpad edge scrolling does not work - from boot and before any sleep. So that is a problem that this update from Lenovo (presuming it installed properly) does not fix."
1791427,2018-11-10 12:53:13 UTC,"The install does has the aforementioned prerequisite, namely the Synaptics 'ultraNav' driver-cum-firmware."
1791427,2018-11-10 09:47:02 UTC,"That release note is so poorly written that I thought it meant: this update will not install on computers with the NFC model. Still, after a while I released that this update is meant to *fix* that problem with Linux. Hurrah!"
1791427,2018-11-13 23:47:20 UTC,"I wasted a (further) day trying to install this stuff in a way I should not even have to, namely via WindowsToGo, which doesn't work properly, at least on my hardware. (I tried three USB sticks, multiple burners, endured endless Windows setup screens and hangs.) And the fixes did not work anyway. Or perhaps they did not install in the first place - it was hard to tell."
1791427,2019-10-15 20:52:48 UTC,"> what you can do is update your touchpad/trackpoint firmware under Windows (unfortunately it's not supported in fwupdmgr), which fixes the issue completely for Linux, at least it did in my X1 Gen6 and a few others I know.
"
1791431,2019-08-26 00:43:40 UTC,"I don't really want to complicate the GUI here, but I think we could get 90% of the way there by saving the checkbox settings in the project file."
1791431,2019-08-26 17:28:38 UTC,"Fixed in revision 8d31c9a6c10312995fbd2be8542980f703d331e4
https://git.launchpad.net/kicad/patch/?id=8d31c9a6c10312995fbd2be8542980f703d331e4"
1791438,2018-09-17 14:44:52 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1791438,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1791443,2018-09-08 20:05:45 UTC,I have a multimonitor setup and my display manager/window manager have always trouble with it :-D
1791443,2018-09-09 08:52:39 UTC,"I don´t think it only depends on the graphic driver and window manager. The default behavior on my system is that a fullscreen window is placed on the monitor it was located on before maximizing. Widelands already has a different behavior, so I´d take a wild guess that the SDL can have some influence here.
Other programs have other handling methods. For example, OpenTTD allows me to choose a resolution equal to the combined size of both monitors, and when entering fullscreen mode at that res, the game uses both monitors. That´s what I would love to have for Widelands.
I don´t know the SDL very well, but it might be worth to check whether it allows to implement such a behavior."
1791443,2018-09-09 10:00:48 UTC,"SDL does have some functions for listing the monitors, so we should be able to take it from there and at least improve the situation - staying on the same monitor while switching the mode would be good."
1791443,2019-09-15 18:41:15 UTC,Migrated to https://github.com/widelands/widelands/issues/1079
1791443,2018-09-08 17:01:44 UTC,"I don't have a multi-monitor setup, but since we don't have any code to handle this, I'm setting the bug to confirmed."
1791446,2018-09-25 22:46:56 UTC,"Thank you for your detailed report, Michael. I've repeated the steps exactly as you described, but was not able to reproduce the behaviour."
1791446,2018-09-25 22:49:27 UTC,Do you use any symbolic links that could generate cyclic file paths?
1791446,2018-09-30 12:31:41 UTC,"Hi Uwe,"
1791446,2018-11-30 04:17:23 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1791449,2019-12-13 17:31:18 UTC,This issue was fixed in the openstack/mistral 10.0.0.0b1 development milestone.
1791449,2019-10-02 11:06:53 UTC,"Change abandoned by ali (<email address hidden>) on branch: master
Review: https://review.opendev.org/686138"
1791449,2019-10-02 11:06:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686138"
1791449,2019-11-12 09:45:26 UTC,"Reviewed:  https://review.opendev.org/684711
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=c7a54d22df990795141dc990300ab76704aa5d30
Submitter: Zuul
Branch:    master"
1791452,2018-09-10 02:48:34 UTC,"Screen tearing with 2 or more monitors in Xorg is a known problem, unlikely to be fixed."
1791452,2018-09-11 20:51:30 UTC,Try the following:
1791454,2019-11-18 20:29:45 UTC,"Could you describe your system? Is there anything non standard in the type of disks, user accounts, ...?"
1791454,2019-11-21 22:45:42 UTC,"Note, these accesses were added in 22d37f834b6f4605faa3887bae3cf4d0e1673278"
1791454,2019-11-18 02:01:54 UTC,My new machine (one week old) is receiving these as well:
1791454,2018-09-17 15:59:00 UTC,If this bug is about a snap package you should probably open a report with the snap author.
1791454,2018-11-11 23:13:48 UTC,iotop is showing systemd-journal writing to disk at around 1MBs while system-monitor is running.  420 entries per seconds.
1791454,2018-09-15 18:33:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791454,2018-11-28 14:52:46 UTC,"That's not an issue on a new/stock installation, maybe having to do with the context but unsure in which cases it's an issue"
1791454,2018-10-11 21:06:31 UTC,I have it on 18.04 as well with System-Monitor installed as an app.
1791463,2018-09-10 02:42:01 UTC,"Neverming - it is fixed now and no pinger ip patch is needed at all.
It was missing BINF that i just added to code. I think it works fine."
1791463,2018-09-10 18:56:07 UTC,The full version and build info is added to both the DE and VE fields which is I think unnecessary and not much useful. None of the ADC hubs and clients do this. Possible fix attached.
1791463,2018-09-11 01:06:22 UTC,"ADCH++ sents full build info in client INF as well.
This can be fixed in access.lua  so it sends just soft. version instead of f.b info."
1791463,2018-09-11 07:37:11 UTC,"Having full build info in DE is pretty much OK; that looks to be the correct field for such data. Uptime and usercount, among other data is/should be sent in the respective fields defined by the ADC extension <https://adc.sourceforge.io/ADC-EXT.html#_ping_pinger_extension>
Whether those are fully implemented in ADCH++ or not I'm not sure but if not then it is a topic of another bug report."
1791463,2018-09-12 00:16:33 UTC,"Yes. It's not pinger related. More like future request.
I meant: show hubs uptime and usercount when new user connects. Something like that:"
1791463,2018-09-13 19:06:31 UTC,"TL/DR: I suggest a new field is created with a ""unique version"" tag or dumping the hash/time altogether."
1791463,2018-09-13 19:08:18 UTC,"By the way, it important to distinguish from the information in PING and what a normal user (client) should get. A normal user may not really care about a bunch of things in provided in the INF, such as the user count -- because the client will automatically anyway show that."
1791463,2018-09-18 23:46:26 UTC,"the dev build number indeed matters - as is, I can agree with removing it from ""final"" builds (where the version number has been increased) only."
1791463,2018-09-08 19:50:54 UTC,"Its not a big deal but looks nasty in hublist stats.
Much bigger issue is that it disconnects all pingers (if ip is different that that outdated one patched into code a while ago)."
1791467,2018-09-08 22:02:50 UTC,"I completely agree, which is why I mentioned a ""reasonable list"" should be created."
1791467,2018-09-08 21:47:38 UTC,"Hi, while I see most of the points of this bug, is hardly almost impossible to detect every possible issue in CI most for failures and restarting things."
1791471,2018-09-08 22:25:44 UTC,This might be related to this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847659
1791474,2018-09-16 00:10:49 UTC,Reproduced also on 0.92.2 2405546 (MacPorts on macOS 10.13.6).
1791474,2018-10-06 19:06:10 UTC,I think this is fixed in master.
1791479,2018-09-09 03:13:02 UTC,further debugging in the namespace
1791483,2018-09-09 09:28:11 UTC,"Works in version 2.0.0, which is available from ubuntu software center."
1791491,2018-09-10 00:55:44 UTC,Note that the device description is shown correctly in all other tabs.
1791492,2018-10-13 13:11:26 UTC,"In the meanwhile, I found a workaround.
In the folder /usr/share/icons/youricontheme/cursors/
change the file ""cross"" with the one in /usr/share/icons/DMZ-White/cursors.
You can use any ""cross"" file that you like found in your favourite cursors theme."
1791492,2018-10-13 12:45:42 UTC,"I'm having the same problem. The crosshair is very dark as the selection's overlay.
I don't want to change the mouse theme just for this problem.
A solution to have either a standard white crosshair could be perfect. I'm fine with the dark background, it helps to focus on what you are screenshotting.
Having a white crosshair somehow in Shutter could be perfect."
1791492,2018-09-09 12:06:05 UTC,"Yes, I meant the system's theme. Breeze Snow seems to have a white cross symbol, I am surprised that it is still invisible! I tried ""DMZ (white)"" and it is quite well visible on the dark background."
1791492,2018-09-09 12:28:55 UTC,With DMZ (white) it works very well indeed.
1791492,2018-09-09 11:25:49 UTC,Thank you for your reply.
1791492,2018-09-09 13:06:37 UTC,"Well, since Shutter is not being developed for several years already, the wishlist status is rather of cosmetic nature. I wouldn't expect it to get implemented any time soon, unless a new developer takes on Shutter's development."
1791492,2018-09-09 09:58:17 UTC,"The visibility of the cursor depends on the cursor theme which is in use. In my case the cursor is rather dark as well, so I usually just draw a rectangle without seeing the cursor and then adjust it afterwards. You can also specify a default selection rectangle position and size, such that you then only need to adjust it to the position and size which is actually necessary. But the easiest solution would probably be to change the cursor theme which is lighter."
1791494,2018-09-09 14:40:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791496,2018-09-09 16:35:40 UTC,"So, you want to see something in the guide that says, ""warning: auth_uri is a thing but don't use it""? Because it's not a typo in the config, it's a deprecated config option for keystone."
1791496,2018-09-09 17:16:10 UTC,"Hi Matt,"
1791504,2018-09-09 16:48:58 UTC,"Thanks for the report and offer to contribute! We would love your help, if you have the time and energy. Please check out the wiki [1] for development resources and join Zulip [2] to chat with other developers."
1791504,2018-09-15 10:00:44 UTC,"Since this doesn't seem easy enough for someone with no experience in C++, I'd like to get started on an easy bug first. But the easy bug list is filled with bugs that are multiple years old an don't seem to be relevant anymore. Could you look into that and clean up a bit? Otherwise it is hard for me to get started in development :/
Also, a short introduction into what the .h files in relation to the C++ files do in the development section of the repo or wiki would be appreciated :)"
1791504,2018-09-15 10:47:22 UTC,"About the hashes, it could be an option you can turn on and off. It doesn't need to be done all the time."
1791504,2018-09-16 14:04:10 UTC,Very similar to my request a couple of years ago.
1791504,2019-12-30 03:46:14 UTC,"> We used to have code that tried to detect renames by recording the file contents hash, but having to hash every file during library scanning led to a significant slowdown in library scanner performance, so we removed it long ago (IIRC around Mixxx 1.9.x?).
"
1791504,2019-12-30 10:38:45 UTC,"Yeah, I approve. Although that still creates problems if you modify tags and move a song at the same time.
By the way, I have now written a tool for adapting the database on file movements, maybe someone finds that helpful (please backup though!): https://github.com/Xerus2000/mixxxdb-kt"
1791507,2018-10-22 04:40:42 UTC,"Hello,"
1791512,2018-11-05 13:01:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791512,2018-11-05 13:03:42 UTC,"I think there might be a race condition involved here, i.e., I think this behavior only happens if you start typing your password at the ""wrong time"" while the computer is in the process of waking up from sleep."
1791515,2018-12-16 15:30:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791515,2020-01-23 20:26:01 UTC,Looks more like a gdk-pixbuf bug?
1791517,2020-07-27 01:35:37 UTC,"I can't reproduce it either, so this seems to have been fixed."
1791517,2020-07-25 20:08:06 UTC,"I tried to test problem, but can't reproduce it in 1.7-development daily PPA on Ubuntu 18.04. This problem was most probably fixed. I clearly remember having problems with canvas resize and copping in the past."
1791520,2020-07-16 17:16:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal:"
1791526,2018-09-09 15:49:48 UTC,Add file with picture support.
1791526,2018-09-09 15:51:32 UTC,add patch from original file blender_listview.py with picture load support
1791534,2018-09-09 16:43:00 UTC,"it says that architecture amd64, but i am sure that i have intel processor"
1791540,2018-11-30 09:00:36 UTC,Nice idea. Very Useful. Thumps Up
1791540,2019-01-26 20:42:17 UTC,Nice idea!
1791546,2021-02-03 19:50:52 UTC,spam reported to https://answers.launchpad.net/launchpad/+question/695354
1791546,2021-02-02 14:36:51 UTC,Can someone delete the spam posts above?? (that is if launchpad has this provision for moderators)
1791546,2018-09-11 21:59:12 UTC,"Fixed in
  https://gitlab.com/inkscape/inkscape/commit/c918151606d7910619bba2fce6bd5bcf698fa419
and
  https://gitlab.com/inkscape/inkscape/commit/414e974ae35c3649db8426147efec31215a5c45a"
1791546,2018-09-10 07:23:28 UTC,"Confirmed, I see that, too, on my machine"
1791546,2018-09-10 19:19:16 UTC,"I just confirmed this is caused by
https://gitlab.gnome.org/GNOME/gtk/commit/359df028be7b1dae76a1ab"
1791546,2018-09-10 16:52:48 UTC,can confirm that it works if current master is compiled with gtk3-3.22.30.
1791546,2018-09-10 15:57:57 UTC,"Potential cause for future reference:
https://gitlab.gnome.org/GNOME/gtk/commit/359df028be7b1dae76a1ab"
1791546,2018-09-11 09:28:03 UTC,"Found the cause, fixing it now. :-)"
1791546,2018-09-10 08:13:48 UTC,The regression is caused by a gtk3 update (3.22.30->3.24.0).
1791547,2018-09-09 20:55:06 UTC,"file with picture, audio and movie file load"
1791547,2018-09-09 20:58:13 UTC,"Patch file for blender_listview with picture, audio and video load files"
1791571,2018-09-10 13:34:05 UTC,"Do you happen to have two instances of Brisk Menu running? Since Brisk looks at the global event queue for the <Super> key press, it would make sense that having two instances running would cause all sorts of undefined behavior issues. Is it possible that's what's happening here?"
1791571,2020-06-09 04:17:30 UTC,[Expired for brisk-menu (Ubuntu) because there has been no activity for 60 days.]
1791574,2020-04-06 04:37:53 UTC,Still happening in focal. Please use bug 1870822 from now on.
1791574,2019-10-11 10:46:21 UTC,"Test case works here with 3.28.4-0ubuntu18.04.2, e.u.c is not much helpful though since it tracks gnome-shell version only (bionic doesn't provide such infos to us yet)"
1791574,2019-09-17 03:28:47 UTC,"Hello Rocko, or anyone else affected,"
1791574,2019-08-05 08:03:29 UTC,This bug was fixed in the package mutter - 3.32.2+git20190711-2ubuntu1~19.04.1
1791574,2019-08-05 07:53:28 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1791574,2019-07-30 00:34:16 UTC,"marco@ubuntu-vmware:~:✗ $ apt-cache policy mutter
mutter:
  Installed: 3.32.2+git20190711-2ubuntu1~19.04.1
  Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1
  Version table:
 *** 3.32.2+git20190711-2ubuntu1~19.04.1 500
        500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages
        100 /var/lib/dpkg/status"
1791574,2019-10-14 10:05:16 UTC,This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.2
1791574,2019-06-27 17:15:10 UTC,This bug was fixed in the package mutter - 3.32.2+git20190626-1ubuntu1
1791574,2019-07-02 17:53:41 UTC,"Hello Rocko, or anyone else affected,"
1791574,2018-09-10 05:12:55 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f3f72b4b050 <__func__.114921> ""meta_window_unmanage"", message=<optimized out>) at ../../../../glib/gtestutils.c:2596
 g_assertion_message_expr (domain=domain@entry=0x7f3f72b3fb30 ""mutter"", file=file@entry=0x7f3f72b48dbd ""core/window.c"", line=line@entry=1498, func=func@entry=0x7f3f72b4b050 <__func__.114921> ""meta_window_unmanage"", expr=expr@entry=0x7f3f72b49de8 ""window->display->focus_window != window"") at ../../../../glib/gtestutils.c:2619
 meta_window_unmanage (window=window@entry=0x5631b320e140, timestamp=timestamp@entry=92923) at core/window.c:1498"
1791574,2018-09-10 06:55:16 UTC,Looks like bug 1422253 is back.
1791574,2019-07-29 15:47:11 UTC,"Hello Rocko, or anyone else affected,"
1791574,2018-10-16 13:42:31 UTC,Not a release blocker.  Will be SRUd
1791574,2019-03-07 09:06:42 UTC,See related bug 1759161
1791574,2018-09-10 06:57:51 UTC,"And still tracking in:
https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5"
1791574,2019-06-25 08:47:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791576,2018-10-09 13:14:20 UTC,"Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-33-generic
cp: failed to restore the default file creation context: Invalid argument
E: /usr/share/initramfs-tools/hooks/kmod failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-33-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1"
1791578,2019-11-11 13:20:10 UTC,My workaround solution (could be better):
1791578,2020-11-30 21:49:42 UTC,Is the AWS bug resolved? or is there any other update?
1791578,2018-12-17 16:47:28 UTC,"As an update, we've determined this is a bug with Amazon's DHCP implementation. We have filed a bug with them and will update this bug once the issue is resolved."
1791578,2018-10-02 20:52:37 UTC,Cool. Thank you @codeshepherd.
1791578,2018-10-02 20:33:59 UTC,"Reproduced with 18.04 standard AMI; confirmed bug not present in 16.04.
This file is written out by systemd-resolved, which was introduced between 16.04 and 18.04, which explains the change in behavior."
1791578,2018-12-18 08:48:33 UTC,Is there a public link where this is being discussed?
1791586,2018-09-10 19:17:16 UTC,I forgot to post the list of unit test with problems. Here it is:
1791587,2018-09-10 12:54:27 UTC,Thanks for your bugreport.
1791587,2018-12-05 21:47:18 UTC,Added snapd package to track the SRU work.
1791587,2018-10-11 23:02:27 UTC,Looks like there is still a problem even with the new core snap.
1791587,2018-10-13 16:07:20 UTC,"This bug was previously logged and supposed to be fixed, but still exists: https://bugs.launchpad.net/juju/+bug/1737332"
1791587,2018-10-19 23:10:47 UTC,Tried 2.35.4+18.04.
1791587,2018-10-29 12:51:55 UTC,"Built 2.36 from source, installed it in a LXD container and performed another test (http proxy is on a host to which there is a route in the routing table while there is no default gateway). Still getting the same behavior."
1791587,2018-10-29 13:10:55 UTC,Based on some experimentation I confirmed the following:
1791587,2018-10-30 12:57:25 UTC,"Thanks @dmitriis - while we had a test for this it was not good enough, i.e. we did not test that this also works with an empty state. The test is added in https://github.com/snapcore/snapd/pull/6062 and the test highlights that there are indeed problems with some store code that uses http requests without going through the proxy. This is fixed in 6062 and we plan to cherry-pick this in 2.36.1 which will be released soon."
1791587,2018-11-09 06:29:08 UTC,"# Seems to work with snapd built from source, 7bb38874f3bc8bbcac951cd51055579fc2c54473"
1791587,2018-11-14 16:47:00 UTC,Thanks for the report and for testing master. This should now work in 2.36.1 which is currently in the candiate channel and will be SRUed shortly.
1791587,2018-09-10 13:25:45 UTC,"Hi Michael,"
1791587,2018-10-03 08:53:26 UTC,Maybe the bug status should be updated
1791588,2018-09-10 08:13:26 UTC,For now I will be hinting this.
1791588,2020-07-21 12:58:58 UTC,The issue isn't there in the current version and serie
1791591,2018-10-08 13:35:37 UTC,"- reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- using the file freehand3.svg"
1791591,2018-10-07 14:14:29 UTC,Which inkscape version ? Can't reproduce on master
1791591,2018-10-07 16:02:11 UTC,"Must have been inkscape-0.92.3, since that's what I had installed at the time I reported."
1791591,2018-10-08 10:04:22 UTC,"could you attach the svg file that is associated with your screenshot.
I cannot reproduce this bug, but I've seen some strange behavior when drawing at very high zoom levels, which I have reported separately as:
https://bugs.launchpad.net/inkscape/+bug/1796650"
1791591,2018-10-08 11:53:53 UTC,"I'm not sure why I'm not getting such extreme deviations as before, but the three black lines in the attached .svg were drawn exactly within the bounds of the cyan curve (starting at the top), and somehow ended up ending a bit too far to the left (seemingly by about the same amount each time)."
1791591,2018-10-08 12:13:11 UTC,"I tried changing the units from px to cm and changing it to 0.001 user units per cm, and got a much more extreme result, attached."
1791591,2018-10-08 13:50:24 UTC,"problem is probably caused by accumulated roundoff error. Attached is a typical excerpt from a line. The precision of the individual points is extremely poor, in some cases no better than about 20% accuracy. If you take hundreds of these, as there typically are, and if you accumulate them, you will get a noticeable amount of error. And the error seems to be an underestimation, so the data are probably being consistently rounded down, which is not a good idea. (I have no idea why the speed should matter.) here is some data:"
1791591,2019-05-17 08:36:53 UTC,"Hi there, we're migrating bugs over to our new GitLab bug tracker. Please follow there for future updates."
1791594,2019-08-27 21:47:33 UTC,"In the first sentence, you mention concurrent deletion of multiple Consistency Group Snapshots
Was this done in a high availability active/active environment with multiple SolidFire-cinder drivers running against the same ElementOS/SolidFire cluster?"
1791594,2019-10-28 03:19:39 UTC,"It seems that def _issue_api_request
is already retryable. https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/solidfire.py#L584"
1791603,2018-09-12 14:34:38 UTC,"The image's min_disk property is set to 10GB, so trying to create a 1GB volume from the image is expected to fail."
1791603,2018-09-13 10:34:02 UTC,"hi Eric, I was not attempt to create 1 GB volume for image whose min_disk property is 10GB."
1791638,2019-03-08 16:21:01 UTC,Can you describe the steps and configurations that are needed to reproduce this problem please?
1791643,2018-09-17 14:44:09 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1791644,2019-10-26 07:33:59 UTC,Now fixed: https://review.opendev.org/#/q/I2a2363c71430a7173bb5253662412ae5dba09654
1791648,2020-11-30 21:10:12 UTC,"I expect this is well past being useful for you, but, try now? The newest version of this package removes the libgee dependency, and also adds support for running as a flatpak:"
1791648,2020-12-01 07:59:54 UTC,"Thanks. I forked and cloned, but I don't know now how build the project."
1791648,2020-12-03 23:30:00 UTC,"Yeah, the resulting executables there are going to end up in the build directory, like `./build/src/settings/gnome-break-timer-settings`. But they rely on various things being installed to particular system directories, so you'll probably want to install it with:"
1791662,2019-10-23 15:28:50 UTC,"Related bug 1750025, may be a duplicate.
Josh"
1791662,2020-11-12 14:47:34 UTC,I agree with Jonathan. As a patron searching for a title and not aware of the series name I'd think the series had no other titles attached to it. Very misleading. Please fix quickly.
1791662,2021-02-24 19:48:06 UTC,Just adding some heat to this.
1791662,2019-07-01 19:30:02 UTC,"We are also experiencing this in 3.1. It affects both users and catalogers-- the latter are frustrated that they take the time to code the relevant MARC fields correctly, but their work doesn't ""show"" (in the sense that it doesn't work as expected at present)."
1791662,2020-11-11 19:06:34 UTC,"This is disappointing.  When our patrons are viewing one book out of a series, they need a quick way to see all other books in that series.  Need this fixed."
1791662,2018-10-02 21:06:00 UTC,"I've looked into this and confirmed the behavior.  When a record is displayed after a search, the series text is taken from the display field based on the series|seriestitle metabib field, which (to oversimplify) grabs /just/ the title from the 800 field if the 490 has first indicator 1 (and from the 490 if the first indicator is 0)."
1791662,2018-09-10 16:38:41 UTC,"I'll also note that for patrons in the OPAC, there is no way to get the series stuff to come back.  Turning off highlighting does not reload the full record correctly and patrons are not going to know how to strip the search info from the URL and be able to see the numeration (which is SUPER important for our series readers). Only staff can see the full series entries on the refresh."
1791662,2018-10-23 14:10:10 UTC,"This is disappointing. We need a way to display the same fields that previously displayed in the catalog without disabling the highlighting, which is a feature that Evergreen libraries have been requesting for years. See also bug 1767416 and bug 1770453, which highlight other field displays that were broken in 3.1."
1791665,2020-01-19 11:06:18 UTC,This has been reported on GitLab; see https://gitlab.com/inkscape/inbox/issues/942.
1791672,2018-09-10 13:38:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/601272"
1791672,2018-11-08 14:57:48 UTC,"Reviewed:  https://review.openstack.org/601272
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=ad2d48fa52de9fdb0b667e193051d93dde07e343
Submitter: Zuul
Branch:    master"
1791674,2018-09-10 14:21:20 UTC,"This is essentially happening in the following bug too:
https://bugs.launchpad.net/tripleo/+bug/1791077"
1791674,2018-09-10 15:23:50 UTC,"Spoke with Martin André about this bug and the potential for others like it. The bug is not particular serious and it would be good to open discussion about this and other potential bugs. Therefore I have set it to a ""public security"" bug."
1791674,2018-09-10 17:24:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/601322"
1791674,2018-09-11 03:46:25 UTC,"Reviewed:  https://review.openstack.org/601322
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=27bab79096584b50947f0d81d41ad2e143c1041e
Submitter: Zuul
Branch:    master"
1791675,2020-10-10 20:11:22 UTC,I am also interested in a resolution.
1791675,2019-10-31 20:15:52 UTC,Any updates on this?
1791675,2018-11-08 10:49:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791676,2018-09-11 16:12:12 UTC,"This is something that could certainly be discussed. The actions API in Heat is set up in such a way that it should be comparatively easy to add new actions. However, there is a fair amount of implementation involved, since each resource type that needs to do something on stop/start would need to have the correct actions implemented."
1791677,2018-09-11 16:00:55 UTC,"You can set the deletion_policy for a resource to 'retain'. (If you forgot to do that at the start, you can update the stack to include that in the template and as long as there are no other changes it won't affect anything.) For any resources with a deletion_policy of 'retain', the physical resource will be left in place but unmanaged by Heat when the resource (or indeed the entire stack) is deleted."
1791677,2018-09-12 14:20:04 UTC,"Excellent to know, thanks Zane! (I'm the one who put this issue into Tobias' Denver luggage. :) )"
1791682,2018-09-11 15:42:19 UTC,This would arguably require a microversion since it would be an API change to allow live migrating suspended VMs:
1791684,2018-09-11 15:22:26 UTC,There is an instance live resize spec proposed:
1791688,2018-09-16 16:22:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791689,2018-09-20 09:47:59 UTC,"looking at the code, the same bug should affect OpenContrail 3.x as well"
1791691,2018-09-13 13:22:56 UTC,"Removing block-promote tag as this is fixed in 2.35.2+18.10 now (well, ""fixed"" it will do nothing if there is no PATH)."
1791691,2018-09-12 12:53:24 UTC,This is reported fixed under bug 1786438 in snapd 2.35.2+18.10 which is currently in cosmic-proposed.
1791691,2018-09-11 19:41:07 UTC,"Summary: environment-generators inherit environment that /sbin/init
started with, but no other systemd defaults.  Therefore, there is no
easy way to append to an environment variable that is not set as snapd
was hoping to do.  The only solution currently is to copy the expected
""default path"" into the snapd environment-generator."
1791691,2018-09-11 17:59:28 UTC,https://github.com/snapcore/snapd/pull/5808
1791691,2018-09-10 15:25:46 UTC,This is a security issue too.
1791691,2018-09-10 14:53:25 UTC,"http://cloud-images.ubuntu.com/cosmic/20180906/unpacked/cosmic-daily.changelog outlines the changed packages between the two images.  I strongly suspect that the root cause of this is the systemd environment generator added in the latest version of snapd, so I've added snapd to this bug."
1791691,2018-09-10 14:46:35 UTC,I can replicate
1791691,2018-09-10 14:44:22 UTC,This regressed between 5ee1af40be67 (serial: 20180905) and 20180906.
1791691,2018-09-10 15:18:34 UTC,"#!/bin/sh
if [ -z ""$PATH"" ]
then
 echo PATH=/snap/bin
else
 echo PATH=$PATH:/snap/bin
fi"
1791708,2018-09-14 17:17:42 UTC,"Error: System.IO.IOException: The process cannot access the file 'C:\Users\Bhavya\AppData\Local\Temp\tmpA2B7.tmp' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at Microsoft.Xna.Framework.Graphics.Texture.FromFile(GraphicsDevice graphicsDevice, Stream textureStream, Int32 numberBytes)
   at Microsoft.Xna.Framework.Graphics.Texture2D.FromFile(GraphicsDevice graphicsDevice, Stream textureStream)
   at Orts.Viewer3D.SharedTextureManager.Get(GraphicsDevice graphicsDevice, String path) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Materials.cs:line 128
   at Orts.Viewer3D.PopupWindowShader..ctor(Viewer viewer, GraphicsDevice graphicsDevice) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Shaders.cs:line 577
   at Orts.Viewer3D.SharedMaterialManager..ctor(Viewer viewer) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Materials.cs:line 202
   at Orts.Viewer3D.Viewer.Initialize() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Viewer.cs:line 363
   at Orts.Viewer3D.Viewer..ctor(Simulator simulator, Game game) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Viewer.cs:line 288
   at Orts.Viewer3D.Processes.GameStateRunActivity.Start(UserSettings settings, String acttype, String[] args) in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\GameStateRunActivity.cs:line 275
   at Orts.Viewer3D.Processes.GameStateRunActivity.<>c__DisplayClass8.<Load>b__3() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\GameStateRunActivity.cs:line 149
   at Orts.Viewer3D.Processes.GameStateRunActivity.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\GameStateRunActivity.cs:line 190
   at Orts.Viewer3D.Processes.LoaderProcess.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\LoaderProcess.cs:line 158
   at Orts.Viewer3D.Processes.LoaderProcess.DoLoad() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\LoaderProcess.cs:line 138
   at Orts.Viewer3D.Processes.LoaderProcess.LoaderThread() in e:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\RunActivity\Viewer3D\Processes\LoaderProcess.cs:line 109
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()"
1791709,2018-09-10 15:48:00 UTC,"If there is any question about the systemd version being an in house version. We only backported a bug fix from upstream. That being said it might be a cause of the issue however we only had issues with auditd and no other services, therefore we still think this bug is relevant."
1791709,2018-12-21 00:20:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791711,2019-10-15 23:44:04 UTC,I took another look at this for hardening the snap-confine profile and reconfirmed that even adding a rule like so:
1791711,2018-09-10 15:51:44 UTC,[explicitly adding people from the related email thread]
1791711,2018-09-10 16:02:24 UTC,"(The reason why SELinux doesn't have such issues is that SELinux works with filesystem-root-relative paths instead of namespace-root-relative ones, so the mount hierarchy has no effect on security controls, apart from security labels that are set via mount options.)"
1791711,2018-09-11 03:51:42 UTC,Indeed currently if pivot root is allowed it can be used to subvert apparmor policy. This is a known issue to apparmor upstream. There are plans to fix this in apparmor upstream. At the moment there is nothing snappy can do except maybe move from pivot_root to chroot which is currently better handled by apparmor.
1791711,2018-09-11 11:27:18 UTC,"Alright, if it's a known issue, this bug report can be changed to ""Public"" type, right?"
1791711,2018-09-11 15:44:38 UTC,"yes, thanks for the reminder"
1791711,2018-09-20 05:50:56 UTC,"Reassigning to apparmor. When fixes are available there, we'll take a look at updating snap-confine's policy."
1791711,2019-10-15 21:28:03 UTC,Hello
1791711,2019-10-15 23:27:39 UTC,The plans have been discussed several places. There isn't a canonical reference atm. But the basics are below
1791757,2018-09-27 12:41:22 UTC,No verification needed for this kernel.
1791757,2018-10-02 07:01:24 UTC,"3.2.0-136.182 - generic
Regression test CMPL, RTB."
1791757,2018-10-02 08:03:15 UTC,The package has been published and the bug is being set to Fix Released
1791761,2020-07-29 12:03:10 UTC,@mpaq: sorry for the lack of feedback when you originally reported the problem. Are you still seeing it with the latest thunderbird update on a supported release of Ubuntu?
1791761,2020-07-10 01:49:46 UTC,I had a problem much like this.
1791761,2020-07-10 13:08:40 UTC,Oops:
1791761,2020-09-28 04:17:19 UTC,[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.]
1791763,2020-11-13 16:00:10 UTC,"A quick eyeball of the patch and the current QEMU tree indicates that at least some of the bugs it's trying to fix still exist (notably a lot of use of ""long"" in various target_* structures, which should not be using types with a width dependent on the host system.)"
1791763,2020-11-13 15:48:38 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1791783,2018-11-04 05:10:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791786,2020-11-12 15:27:39 UTC,Confirmed on Xubuntu 20.04
1791786,2020-07-18 23:02:50 UTC,"Also reported on askubuntu.
https://askubuntu.com/questions/854668/shares-admin-crashes-when-trying-to-add-a-share
https://askubuntu.com/questions/1177302/how-to-fix-segmentation-failed-on-shares-admin"
1791786,2020-07-18 22:22:04 UTC,This is what gdb showed.
1791786,2018-10-07 13:49:10 UTC,"I'm still new to bug reporting, bare with me !"
1791786,2019-01-09 12:24:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791788,2019-04-20 14:14:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791788,2019-09-01 07:39:00 UTC,"It seems like whether lshift + rshift changes the layout depends on the other set combination. For example, changing keyboard layout on Left Alt would disable lshift + rshift as well as removing all switch combinations."
1791788,2019-09-01 07:40:22 UTC,"Also, Alt + Shift would enable LShift + RShift whereas Left Alt + Left Shift would not."
1791791,2019-09-13 18:09:11 UTC,Still an issue on 3.3.3.
1791791,2019-05-20 15:40:00 UTC,I have also noticed that line 63 in Open-ILS/src/templates/opac/parts/js.tt2):
1791791,2018-09-10 22:20:47 UTC,"I see this behaivour on both 3.0.4 and 3.1.4. Google Preview shows up if you search by record id, does not show up if searching by title and other bib info."
1791791,2018-09-14 16:29:07 UTC,"Still present in 3.2 beta 1. The same problem exists in the web client except that when you reload the page, the Google Preview button appears. Reloading the page in the public catalog, however, does not restore the button."
1791791,2018-09-18 15:28:10 UTC,"Additional observance from our production catalog (3.1.4). When a search is performed using just advanced search filters, e.g., by language and bibliographic level, the Google Preview buttons shows up in the record. For example:
https://spok.jabok.cuni.cz/eg/opac/record/30492?detail_record_view=0;fi%3Aitem_lang=eng;fi%3Abib_level=m;locg=1;pubdate=is"
1791791,2018-09-27 08:18:06 UTC,"It seems to me that it is the query part of the URL (e.g., ""query=mentální postižení valenta;"") that prevents the previews from showing up."
1791791,2018-11-02 11:16:51 UTC,It appears that Google Books previews are displayed via ac_google_books.js which is linked from  templates/opac/parts/js.tt2:
1791791,2019-05-21 11:15:23 UTC,I have also noticed that in:
1791793,2018-09-18 23:35:25 UTC,"builds again now with MinGW (links in the expert guide doc), SCons 2.5.0, boost 1.68, OpenSSL 1.1.1."
1791794,2018-09-10 20:13:18 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-September/095356.html
1791794,2018-10-29 22:25:21 UTC,This bug was fixed in the package linux-azure - 4.15.0-1028.29
1791794,2020-11-30 15:46:41 UTC,This bug was fixed in the package linux-azure - 5.4.0-1032.33
1791794,2020-12-01 17:45:06 UTC,This bug was fixed in the package linux-azure - 5.8.0-1013.14
1791794,2020-12-02 05:55:05 UTC,This bug was fixed in the package linux-azure-4.15 - 4.15.0-1100.111
1791794,2020-12-02 06:01:58 UTC,This bug was fixed in the package linux-azure - 4.15.0-1100.111~16.04.1
1791796,2021-01-13 04:17:18 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1791796,2018-10-01 09:05:05 UTC,Philippe Mathieu-Daudé <email address hidden> writes:
1791796,2018-09-30 23:22:41 UTC,"Hi Alex,"
1791796,2018-09-30 22:15:46 UTC,"Hi Alex,"
1791796,2018-09-12 10:19:05 UTC,Marek Vasut <email address hidden> writes:
1791796,2018-09-11 19:03:50 UTC,Sandra Loosemore <email address hidden> writes:
1791796,2018-09-11 15:34:27 UTC,"If you need a Nios II GNU/Linux toolchain, I think the most recent CodeBench Lite release will work:"
1791796,2018-09-11 15:08:13 UTC,Marek Vasut <email address hidden> writes:
1791796,2018-09-11 14:46:14 UTC,"Le 11/09/2018 à 16:40, Alex Bennée a écrit :

>
> Laurent Vivier <email address hidden> writes:
>
>> Le 11/09/2018 à 16:06, Alex Bennée a écrit:
>>> This is to work around the limitations of the buildroot
>>> qemu_nios2_10m50_defconfig which sets the base kernel version for
>>> glibc.
>>>
>>> Signed-off-by: Alex Bennée <email address hidden>
>>> ---
>>>  linux-user/nios2/target_syscall.h | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/linux-user/nios2/target_syscall.h b/linux-user/nios2/target_syscall.h
>>> index ca6b7e69f6..905b80d112 100644
>>> --- a/linux-user/nios2/target_syscall.h
>>> +++ b/linux-user/nios2/target_syscall.h
>>> @@ -2,7 +2,7 @@
>>>  #define TARGET_SYSCALL_H
>>>
>>>  #define UNAME_MACHINE ""nios2""
>>> -#define UNAME_MINIMUM_RELEASE ""3.19.0""
>>> +#define UNAME_MINIMUM_RELEASE ""4.16.0""
>>>
>>>  struct target_pt_regs {
>>>      unsigned long  r8;    /* r8-r15 Caller-saved GP registers */
>>>
>>
>> I have no objection. Perhaps you could ask NiosII Maintainers (cc).
>
> Doh.. I had cccmd = scripts/get_maintainer.pl --nogit-fallback but of
> course as I didn't actually touch an nios2 files it didn't include them.
"
1791796,2020-11-13 15:53:53 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1791796,2018-09-11 14:14:29 UTC,"Le 11/09/2018 à 16:06, Alex Bennée a écrit :

> This is to work around the limitations of the buildroot
> qemu_nios2_10m50_defconfig which sets the base kernel version for
> glibc.
>
> Signed-off-by: Alex Bennée <email address hidden>
> ---
>  linux-user/nios2/target_syscall.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/linux-user/nios2/target_syscall.h b/linux-user/nios2/target_syscall.h
> index ca6b7e69f6..905b80d112 100644
> --- a/linux-user/nios2/target_syscall.h
> +++ b/linux-user/nios2/target_syscall.h
> @@ -2,7 +2,7 @@
>  #define TARGET_SYSCALL_H
>
>  #define UNAME_MACHINE ""nios2""
> -#define UNAME_MINIMUM_RELEASE ""3.19.0""
> +#define UNAME_MINIMUM_RELEASE ""4.16.0""
>
>  struct target_pt_regs {
>      unsigned long  r8;    /* r8-r15 Caller-saved GP registers */
>
"
1791796,2018-09-11 14:06:31 UTC,"Now we have a docker image with a nios2 compiler we can add the bits
to build our TCG tests."
1791796,2018-09-11 14:06:30 UTC,"This is to work around the limitations of the buildroot
qemu_nios2_10m50_defconfig which sets the base kernel version for
glibc."
1791796,2018-09-11 14:06:29 UTC,Build a buildroot toolchain for the nios2 target.
1791796,2018-09-11 14:06:28 UTC,"We can build some more cross-compilers using buildroot. This base
system contains simply the minimum number of tools required for
buildroot to work. We also download and unpack the buildroot source
tree as that will be common for all system deriving from it."
1791796,2018-09-11 14:06:27 UTC,"Hi,"
1791796,2018-09-11 09:57:40 UTC,Thomas Huth <email address hidden> writes:
1791796,2018-09-11 14:40:14 UTC,Laurent Vivier <email address hidden> writes:
1791796,2018-09-11 08:49:36 UTC,Sandra Loosemore <email address hidden> writes:
1791797,2018-12-12 19:06:36 UTC,"sanjay@Swayam:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED
  fusiondirectory
The following packages have been kept back:
  cl-pgloader postgis postgis-gui postgresql postgresql-10-pgrouting postgresql-all
  postgresql-client postgresql-client-common postgresql-common postgresql-contrib
  postgresql-server-dev-all
The following packages will be upgraded:
  libfreerdp-client2-2 libfreerdp2-2 libwinpr2-2
3 to upgrade, 0 to newly install, 1 to remove and 11 not to upgrade.
1 not fully installed or removed.
Need to get 988 kB of archives.
After this operation, 8,785 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://archive.linux.duke.edu/ubuntu bionic-updates/main amd64 libwinpr2-2 amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 [287 kB]
Get:2 http://archive.linux.duke.edu/ubuntu bionic-updates/main amd64 libfreerdp2-2 amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 [448 kB]
Get:3 http://archive.linux.duke.edu/ubuntu bionic-updates/main amd64 libfreerdp-client2-2 amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 [252 kB]
Fetched 988 kB in 6s (158 kB/s)
(Reading database ... 880120 files and directories currently installed.)
Removing fusiondirectory (1.0.19-1ubuntu0.18.04.1) ...
apache2_invoke fusiondirectory postrm: No action required
apache2.service is not active, cannot reload.
invoke-rc.d: initscript apache2, action ""reload"" failed.
dpkg: error processing package fusiondirectory (--remove):
 installed fusiondirectory package post-removal script subprocess returned error exit status 1
Errors were encountered while processing:
 fusiondirectory
E: Sub-process /usr/bin/dpkg returned an error code (1)"
1791799,2019-09-03 01:05:31 UTC,Renamed the title since it was only done for Stein.
1791799,2019-04-28 19:03:41 UTC,This was implemented for stein.
1791799,2019-08-30 17:43:32 UTC,"Based on the comment above, those commits and neutron-fwaas-dashboard (that there is no installation process and it will be displayed if FWaaSv2 is available) I believe we can mark this as Fix-Released."
1791803,2018-09-17 17:58:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791806,2018-10-04 11:39:58 UTC,"Update: as per request from my laptop vendor, I updated the BIOS firmware of my computer(Clevo P650HP), then reinstalled Ubuntu 18.04.1."
1791806,2018-09-13 04:35:43 UTC,"Another person affected, the harware is an older issue of the same OEM manufacturer:"
1791806,2018-09-13 04:24:53 UTC,Hi
1791806,2018-09-26 13:50:40 UTC,"Here is another user affected by the same issue. Running Ubuntu 18.04.1, kernel 4.15.0-34-generic."
1791806,2018-09-30 16:14:45 UTC,"Similar configuration, same problem:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1731940"
1791806,2018-09-30 16:15:11 UTC,"Yet another affected user:
https://bbs.archlinux.org/viewtopic.php?id=147242"
1791806,2018-10-04 11:44:20 UTC,Additonal comment:
1791806,2018-11-15 01:20:07 UTC,"Hello Lehel,"
1791806,2018-10-16 18:24:51 UTC,"No, headphones are not detected in my case:"
1791806,2018-10-16 18:32:31 UTC,"S/PDIF is on, like in the case of Felipe, but headphones never worked."
1791806,2018-10-28 10:05:57 UTC,"This week I got updates for several packages apparently related with sound management, as well as a new kernel. After update and reboot, the headphones jack started to work again. Connection/disconnection was correctly managed in PulseAudio, and audio quality was very good."
1791806,2018-10-28 21:23:59 UTC,Hi Felipe
1791806,2018-10-28 21:25:32 UTC,"Missed one difference, so it should read:"
1791806,2020-05-13 20:38:20 UTC,I am also facing the same issue.
1791806,2018-09-12 19:10:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1791806,2018-10-08 05:55:34 UTC,"Does kernel parameter ""snd-hda-intel.model=clevo-p950"" help?"
1791806,2018-09-11 17:04:32 UTC,apport information
1791806,2018-09-30 16:15:30 UTC,"And another one:
https://bbs.archlinux.org/viewtopic.php?id=229296"
1791806,2018-09-11 17:04:26 UTC,apport information
1791806,2018-09-10 19:56:20 UTC,"Affects Ubuntu 18.04, 17.10, 17.04"
1791806,2018-09-10 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791806,2018-09-11 17:04:05 UTC,apport information
1791806,2018-09-11 17:04:07 UTC,apport information
1791806,2018-09-11 17:04:09 UTC,apport information
1791806,2018-09-11 17:04:10 UTC,apport information
1791806,2018-09-11 17:04:12 UTC,apport information
1791806,2018-09-10 19:58:08 UTC,"upload=true&script=true&cardinfo=
!!################################
!!ALSA Information Script v 0.4.64
!!################################"
1791806,2018-09-11 17:04:18 UTC,apport information
1791806,2018-09-11 17:04:15 UTC,apport information
1791806,2018-09-11 17:04:25 UTC,apport information
1791806,2018-09-11 17:04:24 UTC,apport information
1791806,2018-09-11 17:04:31 UTC,apport information
1791806,2018-09-11 17:04:21 UTC,apport information
1791806,2018-09-11 17:04:23 UTC,apport information
1791806,2018-09-11 17:04:19 UTC,apport information
1791809,2018-09-10 19:59:54 UTC,I'll have to go to another distro until this is fixed.
1791811,2021-01-30 11:37:19 UTC,"Fixed in igerman98 20161207-1, which is available in all distributions since bionic (but not in xenial)"
1791811,2018-09-11 15:51:42 UTC,"Thank you Roland.  So this was just an issue with Ubuntu not updating
the package..."
1791811,2018-09-11 15:24:04 UTC,This was already reported against the Debian package in https://bugs.debian.org/839628 and is fixed since version 20161207-1.
1791820,2018-09-10 20:38:50 UTC,Here's the Traceback:
1791822,2018-09-10 21:00:06 UTC,This change was made by a bot.
1791822,2018-09-12 19:10:13 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1791822,2018-09-13 19:45:18 UTC,kernel-bug-exists-upstream
1791822,2018-09-26 19:47:08 UTC,Regression still exists with 4.19-rc5.  Keyboard and touchpad are working with that version.
1791822,2018-09-10 20:46:14 UTC,I can confirm that this is caused by the kernel update.  When booting 4.17.0-9-generic the screen works correctly.
1791824,2018-09-10 23:11:35 UTC,ML thread on this to socialize the request:
1791828,2018-09-11 13:42:53 UTC,"If the list is implemented, perhaps the number of transits displayed could be determined by a library setting similar to [GUI] ""Maximum previous checkouts displayed"", which controls the Circ History List tab."
1791830,2019-10-26 07:29:12 UTC,Swift recon supported in the Train release. https://docs.openstack.org/kolla-ansible/latest/reference/storage/swift-guide.html#swift-recon
1791838,2019-06-10 18:33:11 UTC,"There are significant changes required to support Distributed Cloud in stx due to the containerized environment. Based on discussion with the Distributed Cloud PL, Dariush Eslimi, we agreed to close old Distributed Cloud bugs as Won't Fix. A full test cycle will be needed to verify the new implementation and new bugs can be opened for the issues reported then."
1791838,2018-09-14 21:23:40 UTC,There is no end user impact for this bug. Low priority. No targeted for any release.
1791861,2018-09-11 01:06:00 UTC,After upgrade.
1791861,2018-09-20 13:56:31 UTC,"Review in progress for https://review.opencontrail.org/46357
Submitter: alexey-mr (<email address hidden>)"
1791861,2018-09-20 13:56:35 UTC,"Review in progress for https://review.opencontrail.org/46358
Submitter: alexey-mr (<email address hidden>)"
1791861,2018-09-20 14:47:13 UTC,"Reviewed:  https://review.opencontrail.org/46357
Committed: http://github.com/Juniper/contrail-tripleo-puppet/commit/3622f2f142d9114d2e0737cc1c057e37ef2d59b7
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    stable/ocata"
1791861,2018-09-20 15:37:30 UTC,it is not applicable to master and 5.x
1791861,2018-09-20 15:57:53 UTC,"Reviewed:  https://review.opencontrail.org/46358
Committed: http://github.com/Juniper/contrail-tripleo-puppet/commit/169cf39ea92e534304445fdc67b47753774e76bd
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    stable/newton"
1791865,2018-10-03 17:46:54 UTC,gonna have a go at fixing this
1791865,2018-10-06 17:48:37 UTC,Created https://review.openstack.org/608245
1791865,2019-02-28 13:41:09 UTC,could you fix the bug also in the queens version?
1791865,2019-03-01 13:22:25 UTC,"I would like to but don't know the process, I just found the bug and provided a patch. I tried asking on freenode #openstack-dns but got no response."
1791865,2019-03-20 04:40:59 UTC,This issue was fixed in the openstack/designate-dashboard 8.0.0.0rc1 release candidate.
1791874,2018-10-09 13:15:33 UTC,"Processing triggers for linux-image-4.15.0-34-generic (4.15.0-34.37) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic
W: initramfs-tools configuration sets RESUME=UUID=e5ce10c3-4a95-4ddb-82b3-57c1f449995b
W: but no matching swap device is available.
cp: cannot stat '/etc/lvm/': No such file or directory
E: /usr/share/initramfs-tools/hooks/lvm2 failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-34-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.15.0-34-generic (--configure):
 installed linux-image-4.15.0-34-generic package post-installation script subprocess returned error exit status 1"
1791874,2018-09-16 08:25:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791883,2018-09-11 08:18:54 UTC,"The attachment ""bumblebee-git-develop.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1791891,2019-09-15 15:33:46 UTC,Migrated to https://github.com/widelands/widelands/issues/2115
1791892,2018-11-29 22:52:43 UTC,The original error is back again if I bypass pip error via workaround:-
1791892,2018-10-09 00:41:44 UTC,I have seen this error few weeks ago while automating devstack installation.
1791892,2020-08-24 23:37:50 UTC,This Ticket can probably be closed now.
1791892,2020-08-18 00:31:27 UTC,Even with DEST=/opt/stack/ I encountered this error on Ussuri and Ubuntu 18.04
1791892,2020-02-28 08:59:28 UTC,"Evgeny: This is obviously a different error, please create a dedicated bug report for it. Also it seems like this happens when using a desktop installation, please use Ubuntu Server instead."
1791892,2020-02-28 05:20:55 UTC,Try to install on VM with Ubuntu 18.04. Got an error:
1791892,2020-02-02 21:52:57 UTC,"Hi, do we have any temporary fix for this issue? I tried on Ubuntu 16.04 LTS and 18.04 LTS with Python3.5, Python3.6, and Python3.7 versions, still the issue persists."
1791892,2019-02-06 11:00:38 UTC,"I got the same error on a fresh install of CentOS 7 with devstack master, however, I have no local.conf. Finally, when I try to create the virtualenv manually it results in an error:"
1791892,2018-12-07 13:33:16 UTC,"Indeed there seems to be an issue in that the setting of DEST isn't honored in some locations, I'll try to debug that further. As a workaround I think it should work to just run with the default DEST=/opt/stack setting."
1791892,2018-12-07 12:06:21 UTC,"Hi guys,"
1791892,2018-12-01 22:02:34 UTC,See also https://www.dangtrinh.com/2018/07/got-optstackrequirementsvenvbinpip-no.html
1791892,2018-12-01 17:11:27 UTC,I cannot replicate (on Ubuntu) with custom DEST environment variable. This issue can be closed.
1791892,2018-09-24 04:19:31 UTC,"As I cannot reproduce this with the default settings, please provide more information like your local.conf file and possibly a complete log from the stack.sh run."
1791892,2018-11-30 12:33:47 UTC,"Doing a full chown is not without issues in some environments, see also https://review.openstack.org/203698 ."
1791892,2018-11-29 15:22:49 UTC,I see the issue again past few days.
1791892,2018-11-29 15:26:09 UTC,I would like OS supplied pip package is always used - can I configure that via ENV variable?
1791892,2018-11-29 16:34:46 UTC,Can you give us a complete series of steps to reproduce the issue? It doesn't seem to happen in our gate setup and I also failed to reproduce it locally.
1791892,2018-11-29 20:05:30 UTC,"Thanks for reply - Actually I found cause of /opt/stack/requirements/.venv/bin/pip"" not exists."
1791892,2018-11-30 20:55:44 UTC,"Its vagrant. I destroyed and recreated host (""ubuntu/bionic64"") and successfully installed  devstack (using salt + https://github.com/saltstack-formulas/devstack-formula) - logs are good. Basically this is installation of devstack using defaults:"
1791892,2018-11-29 21:22:11 UTC,One question - is stackrc used by stack.sh even if local.conf exists?
1791892,2018-11-29 21:26:53 UTC,And should stackrc use DEST=${DEST:-/opt/stack} instead of hardcoded value?
1791892,2018-11-29 21:46:37 UTC,I'm stuck on this pip permissions issue . (and stackrc is used with local.conf).
1791892,2018-11-29 20:12:08 UTC,Running this command before stack.sh did not help.  Let me attach logs.
1791908,2018-09-12 11:00:44 UTC,"still with a new install from Ubuntu 18.10 ""Cosmic Cuttlefish"" - Alpha amd64 (20180911)"
1791908,2018-09-12 19:08:24 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1791908,2018-09-13 07:05:58 UTC,"yes, this issue start happening after an upgrade, the problem was not present with installation from some old ISO and happen with all installations from recent ISO.
see also a similar bug for a different distribution: https://bugs.archlinux.org/task/59175.
will try to test the latest upstream kernel but i'm not an expert..."
1791908,2018-09-13 07:28:44 UTC,"following instructions in https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds
i downloaded files from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3/
but i have an error:
corrado@corrado-HP-p7-cc-0911:~$ cd Downloads
corrado@corrado-HP-p7-cc-0911:~/Downloads$ ls
linux-headers-4.19.0-041900rc3_4.19.0-041900rc3.201809120832_all.deb
linux-headers-4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832_amd64.deb
linux-image-unsigned-4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832_amd64.deb
corrado@corrado-HP-p7-cc-0911:~/Downloads$ sudo dpkg -i linux-headers-4.19.0-041900rc3_4.19.0-041900rc3.201809120832_all.deb
[sudo] password for corrado:
Selecting previously unselected package linux-headers-4.19.0-041900rc3.
(Reading database ... 140343 files and directories currently installed.)
Preparing to unpack linux-headers-4.19.0-041900rc3_4.19.0-041900rc3.201809120832_all.deb ...
Unpacking linux-headers-4.19.0-041900rc3 (4.19.0-041900rc3.201809120832) ...
Setting up linux-headers-4.19.0-041900rc3 (4.19.0-041900rc3.201809120832) ...
corrado@corrado-HP-p7-cc-0911:~/Downloads$ sudo dpkg -i linux-headers-4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832_amd64.deb
Selecting previously unselected package linux-headers-4.19.0-041900rc3-generic.
(Reading database ... 157391 files and directories currently installed.)
Preparing to unpack linux-headers-4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832_amd64.deb ...
Unpacking linux-headers-4.19.0-041900rc3-generic (4.19.0-041900rc3.201809120832) ...
Setting up linux-headers-4.19.0-041900rc3-generic (4.19.0-041900rc3.201809120832) ...
corrado@corrado-HP-p7-cc-0911:~/Downloads$ sudo dpkg -i linux-image-unsigned-4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832_amd64.deb
Selecting previously unselected package linux-image-unsigned-4.19.0-041900rc3-generic.
(Reading database ... 168928 files and directories currently installed.)
Preparing to unpack linux-image-unsigned-4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832_amd64.deb ...
Unpacking linux-image-unsigned-4.19.0-041900rc3-generic (4.19.0-041900rc3.201809120832) ...
dpkg: dependency problems prevent configuration of linux-image-unsigned-4.19.0-041900rc3-generic:
 linux-image-unsigned-4.19.0-041900rc3-generic depends on linux-modules-4.19.0-041900rc3-generic; however:
  Package linux-modules-4.19.0-041900rc3-generic is not installed."
1791908,2018-09-13 10:27:05 UTC,"found an usb pen with an old ISO: Ubuntu 18.10 ""Cosmic Cuttlefish"" - Alpha amd64 (20180729)
installed on a partition of same disk disconnected from internet to have an old kernel, problem does not occur. let me know if i can send syslog or other info."
1791908,2018-12-30 22:36:42 UTC,"I get this too on a 5th gen Lenovo X1 Carbon and mainline kernel. 4.20.0-042000rc7-generic at he moment, but it's been happening for some time not just this exact kernel."
1791908,2018-09-14 08:13:56 UTC,Please raise the issue to mailing list <email address hidden>.
1791908,2018-09-11 10:29:21 UTC,apport information
1791908,2018-12-30 22:54:53 UTC,Problem is intermittent for me.
1791908,2020-05-18 13:43:57 UTC,Old problem about Ubuntu 18.10. Changed status to invalid.
1791908,2018-09-13 15:34:46 UTC,"installed new kernel
corrado@corrado-HP-p7-cc-0911:~$ uname -a
Linux corrado-HP-p7-cc-0911 4.19.0-041900rc3-generic #201809120832 SMP Wed Sep 12 12:35:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
corrado@corrado-HP-p7-cc-0911:~$
problem not fixed"
1791908,2018-09-11 10:29:18 UTC,apport information
1791908,2018-09-12 14:42:09 UTC,"Problem DOES NOT OCCUR on a different hardware Ubuntu 18.10 ""Cosmic Cuttlefish"" - Alpha amd64 (20180911)"
1791908,2018-09-11 10:29:13 UTC,apport information
1791908,2018-09-11 10:29:16 UTC,apport information
1791908,2018-09-11 10:28:58 UTC,apport information
1791908,2018-09-11 10:28:59 UTC,apport information
1791908,2018-09-11 10:29:01 UTC,apport information
1791908,2018-09-11 10:29:03 UTC,apport information
1791908,2018-09-11 10:29:04 UTC,apport information
1791908,2018-09-11 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791908,2018-09-11 10:29:07 UTC,apport information
1791908,2018-09-11 10:29:09 UTC,apport information
1791908,2018-09-11 10:29:10 UTC,apport information
1791908,2018-09-11 10:29:11 UTC,apport information
1791908,2018-09-11 10:29:06 UTC,apport information
1791916,2020-07-21 00:46:45 UTC,This sounds very similar to the crashes caused by bug 1786822
1791917,2018-09-20 13:09:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791920,2018-10-07 14:59:18 UTC,Woah. Complex. Merci beaucoup!
1791920,2018-10-07 14:45:06 UTC,"for the record : resizing the page changed the position of the grid, which triggered an update of the ""widgets"" controlling the grid in the document properties panel, but since that panel was not opened before (the crash did not trigger if it was), the widgets were uninitalized -> crash"
1791920,2018-10-07 14:43:10 UTC,Fixed in https://gitlab.com/inkscape/inkscape/commit/6b230be186a6cdbf140ab439195f003d7e614413
1791920,2018-09-11 10:55:01 UTC,"backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x015a918c in libinkscape_base!_ZN8Inkscape2UI6Widget21RegisteredCheckButton9setActiveEb ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
(gdb) bt
#0  0x015a918c in libinkscape_base!_ZN8Inkscape2UI6Widget21RegisteredCheckButton9setActiveEb ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#1  0x00fd70a1 in libinkscape_base!_ZN8Inkscape12CanvasXYGrid13updateWidgetsEv ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#2  0x01640679 in libinkscape_base!_ZN8Inkscape2UI14ToolboxFactory14showAuxToolboxEP10_GtkWidget ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#3  0x01640baf in libinkscape_base!_ZN8Inkscape3XML21CompositeNodeObserver22notifyAttributeChangedERNS0_4NodeEjNS_4Util10ptr_sharedES5_ () from c:\app\temp\inkscape_devel\libinkscape_base.dll
#4  0x0ca32f48 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) c
Continuing."
1791920,2018-09-11 10:50:35 UTC,"reproduced on Windows 10, Inkscape 0.92+devel (c3d27b9, 2018-09-10)
DOS output is:"
1791920,2018-09-11 12:08:29 UTC,"Thanks a lot, Alvin!!! :)"
1791923,2018-09-30 12:23:07 UTC,"Arc package is ~12MB, from my link is only 1.3MB."
1791923,2018-09-21 17:17:00 UTC,Which version of Lubuntu are you using?
1791923,2018-09-27 09:13:45 UTC,18.04.1 LTS
1791923,2018-09-29 13:59:03 UTC,"I believe lubuntu 18.04 come with adwaita, it has a dark themes. Not sure if it comes with arc, arc has also a dark theme (arc dark)
sudo apt install arc-theme"
1791923,2018-09-30 12:26:27 UTC,Here are all preinstalled themes.
1791929,2018-09-12 06:23:11 UTC,You can already manipulate your game a bit by deleting individual packets ;)
1791929,2018-09-11 21:16:25 UTC,A save game is a saved game. Why should it be possible to tweak the saved game?
1791929,2018-09-12 06:14:21 UTC,"I had been thinking about this too, to get rid of the Profile class and make everything Lua."
1791929,2018-09-12 06:50:41 UTC,"OK valid point about map compatibility. So when implementing this, we´d have to keep the current loader and the s2-maploader around (though we could get rid of the current savers).
Just a brief question, we frequently break savegame compatibility, so why not break map compatibility as well once? After this change, we could put an announcement on the website: ""Save your old maps anew please, compatibility for the old map format will be removed for Build 22"", and a warning on the map-select screen so everyone will notice."
1791929,2018-09-13 05:12:09 UTC,"We only break savegame compatibility when we absolutely have to, and we have never, ever broken map compatibility. Map compatibility has always been a feature, and we might have a rebellion on our hands if we remove it."
1791929,2019-05-04 05:40:30 UTC,"Another argument against: Lua Tables need a lot of memory, and loading savegames will become a lot slower too."
1791929,2019-09-16 08:34:33 UTC,Migrated to https://github.com/widelands/widelands/issues/3316
1791930,2018-09-27 18:45:31 UTC,Thanks this is definitely something we need to keep up with as MAAS scales that Juju is working well with it.
1791930,2019-02-21 16:24:30 UTC,Also found this https://bugs.launchpad.net/juju/+bug/1600061
1791935,2018-09-26 06:24:08 UTC,"Hello,
many thanks for your input, very much appreciated.
The Oracle Virtual VM got installed smoothly after upgrading the Kernal to latest one 4.19."
1791935,2018-09-25 16:14:50 UTC,"BACKGROUND:
Ubuntu 4.15.0-34.37-generic 4.15.18 Ubuntu 18.04.1 LTS 64-bit running on VMWare Workstation 12 with VT-X enabled. VirtualBox 5.2 worked prior to kernel upgrade."
1791935,2018-09-25 17:21:37 UTC,"Tried the upstream header kernel `linux-headers-4.19.0-041900rc5`, which wasn't being displayed as an option in grub's advanced menu. There was no error after installing with `$ sudo dpkg -i lin...deb`, so assumed upstream was installed."
1791935,2018-09-11 12:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791935,2018-09-12 19:04:57 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1791936,2018-11-05 23:27:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791936,2018-11-05 23:29:38 UTC,Still affects current version 18.04.1 LTS.  Colors do not persist on exit and do not affect graph.
1791936,2018-11-07 15:15:58 UTC,I can't confirm those problems. Do you get any warning/error on the command line or in journalctl? Here the colors are restored and changed dynamically using the deb or the snap
1791936,2018-11-07 15:41:29 UTC,Try changing the CPU colours from right to left in one go where most of them are custom colours.
1791936,2018-11-07 15:52:36 UTC,the colors match the legend so you are basically saying that it's working for you?
1791936,2018-11-07 16:05:31 UTC,"Yes, it currently is working for me now after a while. It is likely if I fool around with the colours again that they won't stick. Shall I try?"
1791936,2018-11-24 07:27:45 UTC,"When assigning in reverse using only custom colors as you suggested (32 down to 1), it somewhat works, although not really (there are stray colors that are not changed at all)."
1791936,2018-12-30 17:37:22 UTC,"I'm experiencing the same issue and would like to contribute, how can I do so? Regards,"
1791936,2019-06-05 21:06:24 UTC,"Ok, this is enervating. The only current way to change colors is to follow this algo:
- Open System Monitor
- Select the wanted single cpu color and change it to a new custom one
- Close System Monitor
- Repeat
I had to do that 10 times, but nvm it worked..."
1791936,2019-07-13 15:22:17 UTC,"Not only can I not change the colours (also in Ubuntu 18.04), it seems many other elements of the settings are broken.  The stacked area chart button, and the smooth graph button result in unpredictable behavior."
1791941,2019-08-25 11:08:17 UTC,"Change abandoned by Sagi Shnaidman (<email address hidden>) on branch: master
Review: https://review.opendev.org/601601
Reason: because long time passed since last update"
1791941,2018-09-13 06:12:02 UTC,"Is working now, let's lower it and work it out as a improvement."
1791941,2018-09-11 14:57:54 UTC,http://logs.openstack.org/80/587380/1/gate/tripleo-ci-centos-7-scenario001-multinode-oooq-container/450d037/job-output.txt.gz
1791941,2018-09-11 15:00:04 UTC,similar issue found here http://logs.openstack.org/44/601244/1/gate/tripleo-ci-centos-7-undercloud-oooq/da91c72/job-output.txt.gz#_2018-09-11_14_24_28_480912
1791946,2018-09-11 13:31:14 UTC,We should either keep default CFLAGS when adding our own or provide our own set of defaults applied to all projects
1791946,2019-08-29 19:37:46 UTC,"@sergio: I heard this is implemented already, should this be fix committed or even fix released?"
1791946,2019-12-05 13:08:22 UTC,"@sergiusens, so, what has been the solution for this?"
1791946,2020-01-16 07:51:35 UTC,"I think the solution here would be to append the ""-I <folder>"" directives to CFLAGS instead of overriding it."
1791947,2020-11-12 18:24:53 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1791947,2021-01-12 04:17:33 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1791947,2018-09-25 16:24:33 UTC,"Oh sorry...
I am not subscribed to Qemu-devel yet."
1791947,2018-09-25 10:06:12 UTC,"I have already posted a reply on Qemu-devel since everything posted here is automatically forwarded to Qemu-devel, however, the opposite is not true. So duplicating my reply on Qemu-devel:"
1791947,2018-09-21 09:38:03 UTC,"How to reproduce:
1. download windows 10 iso april 2018 from here:
  https://www.microsoft.com/en-us/software-download/windows10ISO?NavToggle=True
2. create a VM with virtmanager with q35 chipset and configure two usb redirect devices
(3. modify xml to use an xhci controller)
4. Install windows
5. redirect a usb soundcard or a usb headset into the VM
5. play some video and observe that it freezes after some time (1-20 mins)"
1791947,2018-09-18 14:31:27 UTC,The same bug also occurs with Windows 7 Enterprise SP1.
1791947,2018-09-17 09:15:04 UTC,"I tried it again today with qemu master: 19b599f7664b2ebfd0f405fb79c14dd241557452
Unfortunately it did not work better than with qemu 2.11.2"
1791957,2019-09-24 13:57:09 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1791957,2019-09-24 14:37:47 UTC,https://discourse.maas.io/t/support-setting-target-session-attrs-postgres-option-by-passing-additional-options-to-a-django-database-backend/1020
1791957,2018-09-11 15:33:28 UTC,"> any contemporary version will do
"
1791957,2018-09-11 15:30:49 UTC,"Hi Andres,"
1791957,2018-09-11 14:35:10 UTC,"Hi Dmitrii,"
1791958,2018-09-12 06:19:52 UTC,Seems like the point release would be a reasonable SRU.
1791958,2018-09-12 15:54:48 UTC,1.6.2 in 18.04 would be a life saver as I have hit this issue and the only resolution is to compile iptables myself.  I can verify that 1.6.2 resolves this issue and I havn't had any other problems on 18.04 as far as other tools calling 1.6.2
1791967,2018-09-12 16:18:18 UTC,Will this also be patched in 3.28 so that it is available in 18.04?
1791967,2018-09-11 15:46:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791967,2018-09-11 15:46:42 UTC,Thanks for the report! I've forwarded it upstream: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/33.
1791967,2018-09-12 15:50:16 UTC,This will be fixed in 3.30.1 which will likely be available in Ubuntu 18.10 which will be released later next month. (Note that 18.10 will not be an LTS release.)
1791973,2018-09-20 16:35:28 UTC,"Based on consensus above, I've switched the bug to public and triaged it as a class D report, tagging it as a potential hardening opportunity or security-related improvement."
1791973,2018-09-20 15:49:41 UTC,"I concur, class D."
1791973,2018-10-26 16:53:46 UTC,Looking at the policy check:
1791973,2018-09-11 23:44:48 UTC,It seems like a class D according to the VMT's taxonomy ( https://security.openstack.org/vmt-process.html#incident-report-taxonomy ). I agree this can be fixed in the open.
1791973,2018-09-11 17:23:29 UTC,"While I've temporarily triaged this as a potential vulnerability under embargo, it sounds more like something we could discuss and fix in the open as a security-related improvement instead. I'm eager to get more input from Adam, the Keystone core security reviewers and other VMT members on whether they agree."
1791973,2018-09-11 20:42:27 UTC,"This is something I think can be done in the public. This is more ""not enough information is given"" vs. ""too much"" or ultimately something exploitable."
1791973,2018-09-11 17:21:08 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1791973,2018-09-11 22:05:25 UTC,Public is fine.  Just wanted it flagged as a security issue to get appropriate attention and priority.  An attacker is already thinking along these lines.
1791976,2020-03-21 19:20:58 UTC,Closing because CAN'T REPLICATE.
1791976,2018-09-11 20:41:49 UTC,"problem not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1791976,2018-09-11 21:36:26 UTC,"I am try open this file on Linux Fedora.
And instead of opening this file Inkscape showing message ""UniConvertor failed:"""
1791976,2018-09-11 21:54:46 UTC,"# dnf install uniconvertor --nogpgcheck
Last metadata expiration check: 0:21:15 ago on Wed 12 Sep 2018 02:32:37 AM +05.
Package uniconvertor-2.0-0.16.svn362.fc29.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!"
1791976,2018-09-11 22:06:28 UTC,$ uniconvertor -verbose /home/mikhail/Documents/slim2.cdr /home/mikhail/Documents/slim2.svg
1791976,2018-09-12 11:42:06 UTC,"If you are on Linux then you will probably see two entries for opening cdr files:
- Corel DRAW 7-X4 files (*.cdr)
- Corel DRAW 7-X4 files (UC) (*.cdr)"
1791976,2018-09-12 19:59:14 UTC,"For unknown reasons item ""Corel DRAW 7-X4 files"" without (UC) is not present in my file picker window."
1791976,2018-09-13 00:59:13 UTC,"which OS?
which version of Inkscape?"
1791976,2018-09-13 02:57:19 UTC,"$ cat /etc/os-release
NAME=Fedora
VERSION=""29 (Workstation Edition)""
ID=fedora
VERSION_ID=29
PLATFORM_ID=""platform:f29""
PRETTY_NAME=""Fedora 29 (Workstation Edition)""
ANSI_COLOR=""0;34""
CPE_NAME=""cpe:/o:fedoraproject:fedora:29""
HOME_URL=""https://fedoraproject.org/""
SUPPORT_URL=""https://fedoraproject.org/wiki/Communicating_and_getting_help""
BUG_REPORT_URL=""https://bugzilla.redhat.com/""
REDHAT_BUGZILLA_PRODUCT=""Fedora""
REDHAT_BUGZILLA_PRODUCT_VERSION=rawhide
REDHAT_SUPPORT_PRODUCT=""Fedora""
REDHAT_SUPPORT_PRODUCT_VERSION=rawhide
PRIVACY_POLICY_URL=""https://fedoraproject.org/wiki/Legal:PrivacyPolicy""
VARIANT=""Workstation Edition""
VARIANT_ID=workstation"
1791979,2018-09-12 19:24:34 UTC,apport information
1791979,2018-09-12 19:50:39 UTC,"I've checked behaviour of generic armhf kernel 4.18.7 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.7/
and the bug I report is not visible there - I can connect / disconnect USB device from host and is is properly enumerated, also can unload/load ci_hdrc_imx module and keep USB host working as usual"
1791979,2018-09-12 19:24:32 UTC,apport information
1791979,2018-09-12 19:24:38 UTC,apport information
1791979,2018-09-12 19:24:37 UTC,apport information
1791979,2018-09-12 19:24:31 UTC,apport information
1791979,2018-09-12 19:24:35 UTC,apport information
1791979,2018-09-12 19:24:28 UTC,apport information
1791979,2018-09-12 19:24:27 UTC,apport information
1791979,2018-09-12 19:04:35 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1791979,2018-09-11 16:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1791979,2018-09-12 19:24:30 UTC,apport information
1791981,2020-10-28 02:44:59 UTC,It looks like bug 1897530 might cover this but it's unclear. The fix for that is only in Ubuntu 20.10 so far.
1791981,2020-05-25 20:26:51 UTC,"Changing the frame rate to 60Hz isn't an option for me.  The only available frame rates are 119.99Hz, 119.97Hz, 59.96Hz and 59.95Hz."
1791981,2020-04-03 01:18:57 UTC,"And apparently I solved the mystery. As a desperate attempt I changed the refresh rate of the from 59.xx Hz to 60 Hz, and Xorg stopped crashing coming out of suspend. I suggest giving it a try. Note: I do not know why the screen was initially set to 59.xx Hz."
1791981,2019-11-20 21:20:46 UTC,"exactly the same issue as for Ben Echols on a Debian system with recent nvidia drivers. Initially I suspected some racing within systemd, thus filed (and later closed for now) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945158 which has supporting documentation.  Did not find a workaround yet, besides making sure that laptop is fully suspended before closing the lid."
1791981,2019-11-07 16:24:06 UTC,"This is happening to me right now (On Ubuntu 19.10, kernel 5.3.0 and 5.3.9, nvidia drivers version 435 and 440)"
1791981,2019-11-30 04:14:07 UTC,Filed a question within nvidia forum: https://devtalk.nvidia.com/default/topic/1066963/linux/if-laptop-lid-is-closed-during-suspend-quot-failed-to-set-mode-no-space-left-on-device-quot-upon-resume/post/5406357/  so far no closure
1791981,2018-09-16 20:25:54 UTC,"The bug is still occurring, it is a severe bug as it makes suspend functionality totally unusable!
Do you need any further information?"
1791981,2018-09-12 12:31:46 UTC,"By the way, I also did check my HDD and can confirm it is not full."
1791981,2018-09-12 11:05:30 UTC,"I found the file _usr_bin_nautilus.1000.crash in the directory /var/crash.
Running ubuntu-bug on that file only shows a popup and then exits, but there's an older bug I already submitted a few weeks ago: it's https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1788512"
1791981,2018-09-12 01:57:24 UTC,"""No space left on device"" usually means your disk is full, so check that. It can also mean that the process (X server or shell) has just leaked and exhausted some particular resource."
1791981,2019-02-12 19:32:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1791983,2018-11-15 07:42:10 UTC,Another month has passed without a hint.
1791983,2018-10-13 12:34:01 UTC,No update on this bug within a month.
1791983,2018-09-11 21:41:54 UTC,I have moved it over to procps. Thank you for confirming.
1791983,2018-09-11 18:25:05 UTC,"Hello Guido,"
1791983,2018-09-11 20:46:41 UTC,The man pages do not work in later docker images for ubuntu but the apt-file search does show that it is always procps.
1791986,2018-09-11 17:33:09 UTC,"Slightly different wishlist request, but see also: https://bugs.launchpad.net/evergreen/+bug/1765525"
1791991,2018-11-30 14:29:59 UTC,The ppa is maintained by Ubuntu GNOME and not an official Ubuntu archive
1791991,2018-11-30 13:43:50 UTC,Does the thumnailer still work on 32 bit with nautilus 3.30 from this ppa: https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/nautilus330/
1791991,2018-09-30 06:33:32 UTC,"One more thing about the bubblewrap.
Now that gnome-desktop3 (libgnome-desktop-3-17_3.30.1-1ubuntu1) is build against bubblewrap and depends on it, thumbnailer is working correctly on my system."
1791991,2018-09-13 09:53:21 UTC,"thumbnailers are working fine for me, both tiff and jpg, perhaps there is still a missing dependency, that is normally otherwise pulled in by vanilla-gnome-desktop. I generally only test gnome3-staging on systems with that meta package."
1791991,2018-09-12 15:22:43 UTC,"OK, I looked at the file default.rule file.
And I found out that it belongs to the package tracker.
However, that package is in universe now.
I did not have it installed."
1791991,2018-09-12 08:06:34 UTC,"I did get the default.rule error (starting from terminal) when I had installed both the nautilus_3.30.0-0ubuntu1~cosmic1 and the tracker_2.1.3-1~cosmic1 packeges.
As I mentioned, at that time nautilus did not start, the small wheel on the screen just kept on turning."
1791991,2018-09-12 07:38:02 UTC,"Hi Harry,
    Thank you for your bug report."
1791991,2018-09-11 18:02:52 UTC,"After trying with the official cosmic tracker version 2.0.3-3, I found out that Nautilus will start.
However the bubblewrap won't work and I get no thumbnails (tiff, jpg)."
1791991,2018-09-12 08:28:21 UTC,"can you try reinstall tracker 2.1.3 and see if that file exists on your
filesystem? If it doesnt please run apport-collect <bugno> which should
colllect your dpkg/apt logs."
1791995,2018-09-27 19:58:04 UTC,What version of Ubuntu MATE are you using?
1791995,2018-09-27 20:13:21 UTC,18.04
1791995,2018-10-10 12:12:30 UTC,In the feature please take a look at https://ubuntu-mate.community/t/how-to-report-problems-in-ubuntu-mate/17943
1791996,2019-01-31 11:31:15 UTC,That has been fixed in https://launchpad.net/ubuntu/+source/network-manager-fortisslvpn/1.2.8-2
1791996,2019-02-25 12:06:14 UTC,"Hello Paul, or anyone else affected,"
1791996,2019-05-27 19:29:18 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1791996,2019-05-29 08:52:06 UTC,"I don't have a VPN to test that plugin but things keep working fine with 1.2.8-1ubuntu1 installed, the change is a trivial packaging one, no regression was reported and the plugin was not working before, marking as verified"
1791996,2019-05-30 09:53:35 UTC,This bug was fixed in the package network-manager-fortisslvpn - 1.2.8-1ubuntu1
1791996,2019-05-30 09:53:39 UTC,"The verification of the Stable Release Update for network-manager-fortisslvpn has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1792000,2020-06-17 20:51:01 UTC,"Confirmed on focal, it's also not an issue with a GNOME session in the 'overview screen launcher' so seems specific to dashtodock"
1792000,2020-06-16 06:49:07 UTC,"Sebastien, it's fully reproducible.
In focal - just ""sudo apt install virtualbox-qt"" from standard repo.
Create any virtual machine and run it. Issue immediately visible."
1792000,2020-05-18 07:15:02 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1792000,2020-05-18 06:57:24 UTC,"Reproducible in focal fossa on all my installations (to PCs and laptop). Used virtualbox from repository (6.1.6_Ubuntu r137129). Show empty icon for running VM, until I disable/enable dock using ""Extensions""."
1792000,2018-09-14 06:12:18 UTC,"No desktop files installed: everything running out of the build directory, and the only thing installed outside is the kernel modules and a udev rule."
1792000,2018-09-14 05:55:44 UTC,"Mh, I can't reproduce this with standard builds, in your setup is any .desktop file for that installed or just running the binary with no setup in well known paths?"
1792000,2020-05-18 06:47:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792004,2019-05-16 10:09:22 UTC,This bug was fixed in the package bash - 4.3-14ubuntu1.3
1792004,2019-05-16 09:36:07 UTC,This bug was fixed in the package bash - 4.4.18-2ubuntu1.1
1792004,2019-05-16 07:49:49 UTC,"The verification of the Stable Release Update for bash has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1792004,2019-05-09 22:24:31 UTC,"(disco-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(disco-amd64)root@ottawa:~# dpkg-query -W bash
bash	5.0-3ubuntu1.1"
1792004,2019-05-09 20:15:39 UTC,"Hello Dimitri, or anyone else affected,"
1792004,2019-05-09 20:12:56 UTC,"Hello Dimitri, or anyone else affected,"
1792004,2019-05-09 22:26:27 UTC,"(bionic-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(bionic-amd64)root@ottawa:~# dpkg-query -W bash
bash	4.4.18-2ubuntu1.1"
1792004,2019-04-30 15:03:31 UTC,"We don't want to change dpkg's default path, the change in apt should be sufficient, as dpkg should not really be used on its own."
1792004,2019-04-30 15:02:55 UTC,"APT sets ""/usr/sbin:/usr/bin:/sbin:/bin"" as its PATH since disco. We explicitly do not add /snap/bin to the path as discussed internally, because we do not want deb maintainer scripts to be affected implicitly by snaps (they can still specify /snap/bin/<name>)."
1792004,2018-09-13 05:44:33 UTC,This bug was fixed in the package bash - 4.4.18-2ubuntu3
1792004,2018-09-12 16:45:06 UTC,"Bash regression appears to have been introduced in:
https://git.launchpad.net/ubuntu/+source/bash/diff/debian/patches/deb-bash-config.diff?id=c2fee82da8f6caa77764ac65bb7fc237314915f8"
1792004,2019-05-16 07:49:40 UTC,This bug was fixed in the package bash - 5.0-3ubuntu1.1
1792004,2019-05-09 12:01:03 UTC,"Hello Dimitri, or anyone else affected,"
1792004,2019-05-09 22:28:15 UTC,"(xenial-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(xenial-amd64)root@ottawa:~# dpkg-query -W bash
bash	4.3-14ubuntu1.3"
1792008,2020-04-24 00:32:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792017,2019-04-13 19:45:08 UTC,"Takeshi Abe committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1792017,2019-04-13 13:00:32 UTC,"Takeshi Abe committed a patch related to this issue.
It has been pushed to ""master"":"
1792017,2019-02-13 09:03:45 UTC,"Takeshi Abe committed a patch related to this issue.
It has been pushed to ""master"":"
1792017,2019-02-12 17:07:34 UTC,Patch in gerrit: https://gerrit.libreoffice.org/#/c/67741/
1792017,2018-10-09 15:52:34 UTC,NEW as already confirmed.
1792017,2019-02-13 10:33:09 UTC,"Takeshi Abe committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1792017,2018-09-14 21:19:31 UTC,"Description:
Original posted and confirmed here: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1792017
libreoffice 1:6.0.3-0ubuntu1
Ubuntu 18.04. LTS"
1792017,2018-09-14 20:51:04 UTC,"I have tweak the title again, because it is not a solution to make the directory a translatable string."
1792017,2018-09-14 11:49:15 UTC,"@Daniel, would you mind filing an upstream bug at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and share the link to it here? Thanks!"
1792017,2018-09-13 15:14:44 UTC,"Can you please elaborate by what you mean by ""the default working dir""?"
1792017,2018-09-14 11:42:01 UTC,Can you share the contents of ~/.config/user-dirs.dirs ?
1792017,2018-09-13 21:55:11 UTC,"I have testes with LibreOffice 4.2.8.2. It also fails to read ""Dokumente"" but this version falls back to the ""/home/username"" even if ""Documents"" exists."
1792017,2018-09-13 21:48:12 UTC,"I have a German installation and it is the
Optionen -> Pfade -> Arbeitsverzeichnis -> Standard"
1792017,2018-09-14 21:21:18 UTC,https://bugs.documentfoundation.org/show_bug.cgi?id=119890
1792024,2018-09-11 20:15:13 UTC,"Do you have some hints for the ""more reliable"" part of this bug. If yes, please file anew bug for it.
This way this one can be used for tracking the checkbox."
1792024,2018-09-11 20:21:44 UTC,I'm wondering if we need an option for this. What would a use case be for adjusting the waveform zoom level outside of the preferences?
1792024,2019-11-10 15:02:46 UTC,I think this would be a nice addition.
1792027,2019-12-19 20:31:30 UTC,This bug was fixed in the package apparmor - 2.13.3-7ubuntu1
1792027,2019-06-24 08:32:03 UTC,I get this upstream on Debian Stretch.
1792028,2019-01-18 14:31:40 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/601687"
1792028,2019-01-23 15:52:41 UTC,"Reviewed:  https://review.openstack.org/580469
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=0c8de3eb4c2b9bd1828c1e052f4f28e9f4dcd09f
Submitter: Zuul
Branch:    master"
1792028,2018-09-11 20:32:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/601687"
1792032,2020-08-24 13:16:04 UTC,Thanks for the report. We have moved on to a new plugin architecture for future development
1792033,2018-09-11 22:12:15 UTC,Drive was partitioned btrfs.
1792036,2018-11-08 23:44:57 UTC,if the system is in 192.0.2.x network please use this series ip address in undercloud.conf
1792038,2019-09-19 11:58:57 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1792039,2018-10-17 16:39:01 UTC,"exiftran is now running on JPG files instead of PNG ones, but it still doesn't rotate the file. Perhaps it needs to be applied before cropping instead of afterwards."
1792039,2018-10-17 16:27:16 UTC,The problem in my fix is that I applied it to PNG files instead of JPEG.
1792039,2018-10-05 22:15:55 UTC,Here's the output of:
1792039,2018-09-11 22:21:40 UTC,"Actually the problem comes before jpegoptim enters the picture. The images served out of /uploaded/ are not rotated properly on the ""Crop photo"" page and the browser will only apply the EXIF rotation if the image is navigated to directly."
1792039,2018-09-11 22:08:49 UTC,I suspect the problem is that the includes a mandatory rotation in the Exif data and that jpegoptim strips it out:
1792039,2018-10-08 04:54:32 UTC,"I committed a fix:
https://git.launchpad.net/~libravatar/libravatar/commit/?id=55a9a9b8a36137bde7e0aae2b17dd96f59d05aff"
1792040,2018-09-11 21:47:50 UTC,Branch available at: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1792040-hold-alias-column-on-shelf
1792040,2018-09-12 13:29:30 UTC,"I've pushed a followup commit to this branch that disables the (unnecessary) server-side sorting in the UI, since clientsort /always/ sorts in the browser for display.  This has the effect of never providing a broken sort clause to the server, which would be possible in some instances if we leave server-side sorting in use in these two UIs."
1792040,2019-01-22 18:26:08 UTC,"Tested and worked for me. I consent to signing off on this patch with my name and email: John Yorio, <email address hidden>"
1792040,2020-07-15 01:13:20 UTC,"Works well for me.  Thanks, Mike and John!  Added to master, rel_3_5, and rel_3_4."
1792052,2019-09-26 03:06:31 UTC,"A year later and this is still an obstacle.  I resorted to ph,err = io.popen(""curl "" .. URL , ""r"")"
1792054,2018-09-18 19:37:54 UTC,"This is one seen on Trusty, the solution is to add the Mitaka cloud archive and update python3-requests to the latest version."
1792054,2018-09-25 19:52:30 UTC,Recommend solving with more unit and functional tests
1792077,2019-04-23 04:16:34 UTC,"Reviewed:  https://review.opendev.org/653511
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8703282508954596e1d041340878c636693d8f5f
Submitter: Zuul
Branch:    stable/rocky"
1792077,2019-04-17 19:05:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/653514"
1792077,2019-04-18 17:32:49 UTC,"Reviewed:  https://review.openstack.org/611974
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=48fd81648a7cadf2d147a6beabac067c28b288b0
Submitter: Zuul
Branch:    master"
1792077,2019-04-21 19:24:46 UTC,"Reviewed:  https://review.opendev.org/653510
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7500c1910cf1cbe16ee48028b67aa919160f44da
Submitter: Zuul
Branch:    stable/stein"
1792077,2019-04-24 07:05:24 UTC,"Reviewed:  https://review.opendev.org/653512
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8ad9f4e1949ce6fdada565cc6660fbac7f75d6c
Submitter: Zuul
Branch:    stable/queens"
1792077,2019-04-17 19:00:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/653512"
1792077,2019-04-26 17:15:39 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1792077,2019-06-06 06:24:26 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1792077,2019-06-18 03:41:14 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1792077,2019-07-10 21:40:09 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1792077,2019-09-27 09:04:29 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1792077,2019-04-24 16:45:49 UTC,"Reviewed:  https://review.opendev.org/653514
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b50b70a18286b20afa0dbf68bc4833ce5a6235ca
Submitter: Zuul
Branch:    stable/pike"
1792077,2019-04-17 19:00:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/653511"
1792077,2018-10-18 16:36:26 UTC,"Indeed, we only set the initial disk_mapping['unit'] values if the image meta scsi_controller.model is 'virtio-scsi':"
1792077,2018-10-19 22:18:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611974"
1792077,2018-10-19 18:57:04 UTC,"Thanks for confirming that, Ben. I'll cook up a patch for this."
1792077,2018-10-19 16:12:51 UTC,FWIW the above patch (from comment 11) does work for the situation I care about. I would like to see it or something like it merged to Stein and backported to Rocky.
1792077,2018-10-18 22:55:15 UTC,If you push a patch I'll be happy to test it. Maybe we can get a fix in Stein and a backport to Rocky and then I can have a happy customer.
1792077,2018-10-18 21:22:53 UTC,"Ah, I think you're right."
1792077,2018-10-18 20:20:30 UTC,https://github.com/openstack/nova/commit/c25629f85feb53b5be0347f68c43b3b55fb9f137
1792077,2018-10-18 18:36:16 UTC,"Thanks Ben, that's helpful."
1792077,2018-10-18 18:14:08 UTC,"Ben: in reply to your earlier request, I don't have that image around anymore.  But it sounds like you might have a handle on the problem."
1792077,2018-10-18 17:50:37 UTC,If there's a workaround that would work with OpenStack Rocky I'd like to know about it though.
1792077,2018-10-18 17:41:16 UTC,"@melanie, I think the fix for this bug would be to always add the unit to the disk mapping if it is present."
1792077,2018-10-18 17:33:39 UTC,"@melanie: what happens is the the generated XML lacks the unit (for the disk address) altogether. If you omit the address tag, libvirt will autogenerate it, but if you send it and omit the unit field, it assumes zero, and that's where the conflict comes in."
1792077,2018-10-18 17:27:46 UTC,"Hm, but we only add 'unit' to the disk_mapping if image meta has scsi controller model 'virtio-scsi' and we only increment the 'unit' number if 'unit' is found in the disk_mapping. So it would seem like we're safely only setting and incrementing 'unit' if we have image meta. So I don't get how the duplicate address is happening."
1792077,2018-10-18 15:42:01 UTC,"This issue seems to be that nova only handles ""scsi"" block device mappings correctly if you boot from an image that has image metadata ""hw_scsi_model"" = ""virtio-scsi"". If you boot from disk rather than booting from an image I'm not sure if there is a workaround."
1792077,2019-04-17 18:53:10 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/653510"
1792077,2018-10-18 00:42:43 UTC,"I'm seeing the same behavior with Rocky and CentOS 7.5. I've also tried specifying a different device
name for the second disk, but that has no effect."
1792078,2019-01-16 14:19:47 UTC,Somewhat related: #1812003
1792078,2019-01-16 14:39:26 UTC,"The error is probably from 'snap check', which snapcraft calls to perform static analysis.
snapd is picky about what you put in the hooks directory, and this is unlikely to change. Having said that, we could have it ignore non-executable README* files. We should discuss this."
1792079,2019-09-15 18:37:59 UTC,Migrated to https://github.com/widelands/widelands/issues/1080
1792085,2019-12-25 09:00:25 UTC,"Hello, on Ubuntu 18.04 and USB 3 try diferent android devices and MTP it's extremely slow!"
1792085,2020-01-06 04:10:43 UTC,"I was able to fix this on Ubuntu 18.04 (bionic), which comes with libmtp-common=1.1.13 by installing a newer version of libmtp 1.1.16.  Now Ubuntu transfers huge numbers of songs between my phone and laptop by simply drag-and-drop in Nautilus."
1792085,2020-01-22 09:36:00 UTC,"I use ubuntu 19.10 and a lg d855. The version of libmtp is 1.1.16-2.
Transfers do not work on USB3 but work on USB2 (My motherboard has both types of USB ports)."
1792085,2020-01-23 09:42:50 UTC,"@jeff - for me it does not work your solution, maybe it is related to isparnid's comment? I only have USB3 on my Toshiba Satellite P50."
1792085,2020-02-03 10:08:59 UTC,"Latest release upgrade of ""libmtp"" solved for the issue:"
1792085,2020-01-29 09:31:53 UTC,"It is odd that this slowness happens with some directories, but not with others. For example it happens on a directory with 7 files; file names consist of letters, '-', digits and '.'. ls command on that directory takes about 5 minutes. But there are other directories (where there are more or less files) with which there is no such delay. Do you have any clue why is this?"
1792085,2020-01-29 09:59:37 UTC,"Sebastien Bacher, I attach the output of 'LC_ALL=C journalctl -b'. I issued ls command
on 11.39.34 and it took about 5 minutes to complete."
1792085,2020-01-29 10:02:37 UTC,The previous was on Xubuntu 19.10
1792085,2019-12-22 20:44:21 UTC,Same problem on Ubuntu 19.10 and galaxy S9 plus. I tried to play some videos via usb cable and during the transfer Ubuntu froze the screen. I was forced to remove the usb cable without ejecting the smartphone. = /
1792085,2020-02-03 16:31:56 UTC,"@lancillotto Sorry for the noob question, I am trying to install it, but don't make it."
1792085,2020-04-12 07:17:49 UTC,"I have a similar problem in 18.04, extremely slow mpt access to a Huawei P20. Installation of libmtp9_1.1.17-2, libmtp-common_1.1.17-2 and libmtp-runtime_1.1.17-2 did not result in any improvement."
1792085,2020-02-23 19:48:14 UTC,"I am also affected by this bug, on Ubuntu 18.04. I can't get the list of files from a folder on the phone (""could not get object handles""). No brackets in file names, just a folder named ""Camera"" and default Android names for pictures."
1792085,2020-02-23 19:54:14 UTC,"If that can be of interest, the ""unlistable"" folder has 124 files."
1792085,2020-02-26 22:16:51 UTC,"I have just tried installing libmtp-1.1.17-2 on 18.04 from here:
https://launchpad.net/ubuntu/+source/libmtp/1.1.17-2/+build/18694144
files:
libmtp-common_1.1.17-2_all.deb
libmtp-runtime_1.1.17-2_amd64.deb
libmtp9_1.1.17-2_amd64.deb
(disconnect phone and after installation log out and log in back to the system or reboot for new libraries to be loaded)
Now listing files is quick and I can actually transfer files."
1792085,2020-03-24 05:50:37 UTC,"Also have this problem - on Linux Mint 19.3, XFCE with a Samsung S7.  This worked fine under Mint 17.1 - listing 3500 jpeg files took 20 seconds; usually less.  Now when trying to read the same directory which is now only 2500 jpeg files, both Thunar and PCMANFM take > 20 MINUTES to generate a file listing - a slowdown by a factor of 60 for a thousand fewer files.  But once the listing shows up, I can scroll and do file transfers just fine.  Directories of only a few hundred jpegs on the phone come up almost instantly.  I can't get a more recent version of the libmtp than 1.1.13 from the repository, and I get errors that state ""Dependency is not satisfiable: libmpt9(=1.1.17-2)"" when I try the other solutions mentioned previously."
1792085,2020-03-24 06:08:03 UTC,@allenbt42 probably beta version of Ubuntu 20.04 could help if it has never version of libmpt
1792085,2020-03-26 17:29:08 UTC,Had the same issue - fixed it today by installing the libmtp 1.1.17 packages from the ubuntu-focal repositories. Seems to work OK now.
1792085,2020-04-19 13:57:50 UTC,I have the same Problem on Ubuntu 19.10 with a Samsung Galaxy S10 (SM-G973F)
1792085,2020-05-22 17:05:22 UTC,"Hi, I came back after a while and I found a nice link to deb packages at post #47 (thanks!).
I installed them and speed is improved, but file copies are still crashing randomly. The most common error message is ""libmtp error: Could not send object."" (it's an mp3)."
1792085,2020-05-22 18:20:07 UTC,And again folders with more than 124 items become unreadable and transfer of files crash at the 124th. So I can confirm that 1.1.17 brought not fix at all and mtp under Ubuntu 18 is still below usable levels.
1792085,2020-05-23 09:58:18 UTC,"I have the same issue, and recommend those who haven't tried it out yet, to look at post #10 ( https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1792085/comments/10 ) and use this application in the meantime. It works reliably for me."
1792085,2020-10-25 15:00:19 UTC,"Hi,
I'm on Linux Mint Tricia 19.3, Nemo 4.4.3. samsung J3 phone.
Worked good for me following Jeff suggestion (post #36). Install libmtp 1.1.16. Before, Nemo would take forever building dir of DCIM (if even returning), now it is ok. I can transfer files, delete, whatever, NO root needed. I confirm that : USB debuging have NOTHING to do with speed or access. Works, either way. Phone is almost as fast as a USB key(little slow with huge folders > 500 entries)
Thanks to all, it was so frustrating. I noticed that sometimes there is a ""ghost"" entry in
/run/user/1000/gvfs$ ls
'mtp:host=%5Busb%3A003%2C015%5D' >>That is a correct entry."
1792085,2019-11-05 20:20:28 UTC,As a temporary workaround ADB push/pull can be used. Mine worked with speed around 20 Mb/s.
1792085,2020-02-03 21:23:37 UTC,"Hi I suggest you to give to configure the execution rights by ""chmod +x configure""."
1792085,2019-11-05 10:23:33 UTC,"I just had this problem yesterday with Ubuntu 18.04 with all the updates and with a brand new Xiaomi Mi A3.
Copying from the phone (Xiaomi Mi A2) wasn't that bad, I was with speeds around 20mb/s but copying the data back to the other phone was unreasonably slow. It would start at around 5mb/s and then quickly drop to around 60kb/s."
1792085,2019-09-07 01:07:14 UTC,How is this not fixed a year later?  Whatever people are working on for the next release that they feel is sexy I hate it.  Instead please fix bugs which make the existing system unusable.  Then you will be my hero.
1792085,2019-10-20 20:34:32 UTC,Same problem on Ubuntu 18.04.3 LTS. ls hangs in /run/user/1000/gvfs/mtp:host=... .
1792085,2019-10-27 03:36:53 UTC,For those experiencing the slowness problem:
1792085,2018-09-19 08:27:37 UTC,The hang occurs when file names contain '('. The workaround is to rename that files by the Android file manager.
1792085,2018-09-24 19:17:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792085,2018-09-24 19:24:23 UTC,"I just switched to Ubuntu 18.04 and I have the same problem. Unable to list files on my android phone, specifically pictures from camera. It just hangs after clicking the DCIM dir - there are no '(' file names. It works without problem on Ubuntu 16.04."
1792085,2018-12-02 04:48:59 UTC,I literally waited an HOUR to get to my Camera directory on my Samsung S7 (Android 9) and FINALLY got to the files. I did not have any parenthesis error as mentioned above.
1792085,2019-01-19 22:34:15 UTC,Exactly the same happens to me. It's a huge issue to me because I need constantly copy files from android to ubuntu.
1792085,2019-01-20 11:35:09 UTC,I've tried a live ubuntu 16.04.5 LTS desktop 64 and works perfectly. The results of dpkg -s gvfs on the working ubuntu is:
1792085,2019-01-22 10:54:29 UTC,"Thank you for your bug report. Seems like there are different issues described there
- slowness
- filenames with a '('
- hang"
1792085,2019-01-25 18:28:36 UTC,Hi everyone.
1792085,2019-01-29 05:47:35 UTC,"Same/similar issue here.
Ubuntu 16.04 + Samsung Galaxy Note 8 - works
Ubuntu 18.04 + Samsung Galaxy Note 8 - doesn't: very slow, lost devices. Completely impossible to move photos via MTP
KDE Neon 18.04 - doesn't works as well"
1792085,2019-01-29 09:53:27 UTC,Could those having that issue maybe try for a 18.10 liveCD to see if the issue is resolved there?
1792085,2019-01-29 16:53:50 UTC,"I can confirm, the bug exists in Ubuntu 18.10"
1792085,2019-08-04 09:16:53 UTC,I have the same problem on Ubuntu 18.04 and Samsung Galaxy S9 (Android 9).
1792085,2019-03-27 02:26:07 UTC,"Same problem, was not reliable on 14.04 but work with a bad integration.
Integration is better on 18.04 but very very slow, and crash when opening folder with many files (like music or dcim folder).
Unusable actually..."
1792085,2019-10-20 09:32:36 UTC,Same problem on Ubuntu 18.04 LTS with all updates and Samsung Galaxy S8. Why did Google have to implement MTP instead of good old fashioned media access over USB like we used to have ? The good old days where the storage would show up just like a USB stick ? What is the benefit of MTP ?:-(
1792085,2019-10-14 12:24:54 UTC,Same problem with Samsung Galaxy S6 on Ubuntu 19.04 and 19.10.
1792085,2019-09-29 20:04:00 UTC,"Like others reported here, I observe the same problem (slowness) with my Samsung Galaxy A5 and ubuntu-18.04."
1792085,2019-09-08 12:02:26 UTC,"I had this problem, too, but it suddenly started to work in the middle of session. I don't know, if installing package android-tools-adb and pcmanfm had anything to do with it."
1792085,2019-09-07 08:45:41 UTC,"It's not the first bug who is not fixed in one or more years, the problem is, when you invite new users to discover ubuntu, at a time, they will need to connect their phone on their computer, and they will say: This doesn't work, and the fix (via mtpfs-go) is complicated for basic users."
1792085,2019-03-05 20:29:42 UTC,"any hacker can estimate when patch will be released ?

>Cheers,


tk"
1792085,2019-08-18 21:55:55 UTC,I checked again but this time with Cantata. It can't access my Samsung Galaxy J6 device. Must be a privilege problem or maybe I'm wrong.
1792085,2019-08-18 14:08:23 UTC,"Also couldn't solve with ""go-mtpfs"""
1792085,2019-08-18 14:05:36 UTC,"I have this exact problem with Calibre and Kindle PaperWhite (10th Gen).
I checked every part over here )https://www.mobileread.com/forums/showthread.php?t=118560) but I think it's an OS problem."
1792085,2019-06-01 11:27:16 UTC,"I see this problem when I am running Calibre and connect a Kindle Fire.  The Fire shows up as a mounted device in Nautilus, but has nothing on it (which is wrong).  Errors from both dmesg and Calibre imply that the problem may be related to libusb_claim_interface()"
1792085,2019-08-19 09:33:27 UTC,"I did something else today.
Calibre on Flathub detected both my phone and my Kindle perfectly but Calibre on Bionic official repo couldn't do that. Well, official repo is version 3.21 and Flathub version is 3.46. I don't know if that's the problem.
Anyone knows what is that mean?"
1792085,2019-04-18 14:55:38 UTC,"I have the same problem, as I moved from Ubuntu 16.04 to 18.04 I experienced a tremendous slowness when opening folders containing lots of files.
While I did not find any actual solution, I put together a workaround that I wanted to share here as I think someone might find it useful. I'll appreciate any comment or suggestion."
1792093,2018-09-12 14:41:40 UTC,"Prototype for the Alternative approach:
https://code.launchpad.net/~aluria/charm-policy-routing/+git/charm-policy-routing"
1792093,2020-03-20 08:19:57 UTC,This charm has been deprecated. Marking #wontfix
1792094,2019-09-19 12:06:31 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1792100,2018-11-19 15:47:04 UTC,"That is good news, that might indicate this bug is now fixed.  Can you apply all the latest updates and the latest kernel to see if the bug still exists?"
1792100,2018-11-19 10:27:42 UTC,The 4.15.0-33-generic #36-Ubuntu kernel works.
1792100,2018-11-16 15:08:46 UTC,"That was using a stock 4.15.0-33.36 tree that I built.  Can you test the official build from the ppa, which is available here:"
1792100,2018-11-12 10:37:55 UTC,The 4.15.0-33-generic #37~lp1792100v2 kernel works.
1792100,2018-10-31 15:26:36 UTC,"Does it hang at the same point as prior kernels, or does it seem different?"
1792100,2018-10-31 15:43:27 UTC,"It looks (superficially) the same...
   the purple screen says ""loading initial ramdisk..."" indefinitely."
1792100,2018-11-19 16:11:08 UTC,Neither the 4.18.0-10 nor the 4.15.0-39 kernel will boot.
1792100,2018-10-31 09:28:43 UTC,The 4.15.0-39-generic_4.15.0-39.43~lp1792100MasterNext kernel HANGS.
1792100,2018-10-30 13:09:46 UTC,I built a test kernel using the master-next repo.
1792100,2018-11-01 22:56:11 UTC,"What's interesting is the test kernel in comment #28 was tested as good.  That was built with commit 19e56be2af5 as the tip of the tree.  That commit is only one commit behind 22df1539aed9, which is the version tag.  However, the bug exists when commit 22df1539aed9 is the tip."
1792100,2018-11-19 16:30:59 UTC,"Hmm, OK, thanks for the feedback.  Let me review the bisect results and see if we went astray at some point."
1792100,2018-11-22 13:16:58 UTC,Those kernels are OK.
1792100,2018-11-20 12:20:45 UTC,The 4.20.0-042000rc3-generic kernel works.
1792100,2018-11-20 15:33:00 UTC,"If that is the case, we are better off performing a ""Reverse"" bisect to identify the fix in mainline versus investigating what went wrong in the first regular bisect."
1792100,2018-11-26 15:53:13 UTC,"Can you test 4.18 final:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18/"
1792100,2018-11-26 16:36:26 UTC,The 4.18.0-041800-generic kernel works.
1792100,2018-10-25 15:15:47 UTC,The 4.15.0-33-generic #37~lp1792100Commit19e56be2af5a kernel works.
1792100,2018-11-26 21:05:48 UTC,"Also, just to confirm to test this kernel you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages in that order."
1792100,2018-11-26 21:07:55 UTC,Can you also test the following mainline kernels to confirm if this is due to a SAUCE patch or not:
1792100,2019-01-08 12:08:17 UTC,The 4.15.0-34-generic downloaded from https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15307305 works.
1792100,2019-01-08 12:16:24 UTC,The 4.15.18-041518-generic kernel works.
1792100,2019-01-08 12:19:14 UTC,The 4.16.0-041600-generic kernel works.
1792100,2019-01-22 15:25:33 UTC,Upgrading to 18.10 works.
1792100,2018-11-19 20:49:42 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1792100,2018-11-26 21:05:00 UTC,"Can you test the following kernel?  It appears this bug may have been introduced by a SAUCE patch:
-34:"
1792100,2018-10-25 14:33:21 UTC,Sorry about that.  The .debs are there now.
1792100,2018-10-24 16:25:00 UTC,"I built the next test kernel, up to the following commit:
19e56be2af5ad5333a32da9595f60ec5045d1ca4"
1792100,2018-09-12 09:00:06 UTC,This change was made by a bot.
1792100,2018-09-12 19:50:40 UTC,I built a 4.15.0-35 test kernel.
1792100,2018-09-13 09:51:29 UTC,I get error messages when installing linux-headers:
1792100,2018-09-13 13:21:54 UTC,"The linux-headers package shouldn't be needed to test for this bug.  You should only need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages."
1792100,2018-10-24 16:47:38 UTC,The kernel is missing at http://kernel.ubuntu.com/~jsalisbury/lp1792100.
1792100,2018-09-17 13:04:24 UTC,I started a kernel bisect between Ubuntu-4.15.--32 and Ubuntu-4.15.0-33. The kernel bisect will require testing of about 7-10 test kernels.
1792100,2018-09-17 13:47:31 UTC,I'll test this tomorrow.
1792100,2018-09-18 10:48:29 UTC,The kernel 4.15.0-32-generic #35~lp1792100Commit77a24c313d2 works.
1792100,2018-09-18 12:40:06 UTC,"I built the next test kernel, up to the following commit:
7f36a83df6d4fabe39ba597a4eef5ca1f5bbda99"
1792100,2018-09-18 15:45:10 UTC,The 4.15.0-33-generic #37~lp1792100Commit7f36a83df6d kernel works.
1792100,2018-09-19 07:44:09 UTC,"I built the next test kernel, up to the following commit:
9627b5742a8e8d87f62d29a8ee04ae867ecd3768"
1792100,2018-09-19 09:04:09 UTC,The 4.15.0-33-generic #37~lp1792100Commit9627b5742a8e kernel works.
1792100,2018-09-14 08:29:00 UTC,"The 4.15.0-35 test kernel also hangs at ""loading initial ramdisk...""."
1792100,2018-09-19 11:50:14 UTC,The directory http://kernel.ubuntu.com/~jsalisbury/lp1792100 is empty!
1792100,2018-09-19 10:07:02 UTC,"I built the next test kernel, up to the following commit:
00c3aa70c712c5f7758370e0cd719ac5e401305e"
1792100,2018-10-24 09:08:53 UTC,The 4.15.0-33-generic #37~lp1792100Commit3dfa1c904fcf138 kernel works.
1792100,2018-10-23 18:11:04 UTC,"I built the next test kernel, up to the following commit:
3dfa1c904fcf138e64658c03f054ef102f52c6ec"
1792100,2018-10-22 12:00:44 UTC,The 4.15.0-33-generic #37~lp1792100Commitf03220fb0122 kernel works.
1792100,2018-10-02 14:34:09 UTC,"I built the next test kernel, up to the following commit:
f03220fb0122a5aced32a57bcb14dde045fc462c"
1792100,2018-09-21 11:41:38 UTC,"I built the next test kernel, up to the following commit:
d86a0bd64457a4373623713e93fe8848a9e75ce7"
1792100,2018-09-21 12:07:11 UTC,The 4.15.0-33-generic #37~lp1792100Commitd86a0bd644 kernel works.
1792100,2018-09-20 14:24:03 UTC,"I built the next test kernel, up to the following commit:
d4be7ce8e6324691737b45f336d770245ba07310"
1792100,2018-09-20 10:00:17 UTC,The 4.15.0-33-generic #37~lp1792100Commit84d28cc43f2 kernel works.
1792100,2018-09-20 07:37:49 UTC,"I built the next test kernel, up to the following commit:
84d28cc43f2d9820bd97e8dc428b00483322f660"
1792100,2018-09-19 15:37:50 UTC,The 4.15.0-33-generic #37~lp1792100Commit00c3aa70c71 kernel works.
1792100,2018-09-21 08:32:24 UTC,The 4.15.0-33-generic #37~lp1792100Commitd4be7ce8e632 kernel works.
1792100,2018-09-19 13:12:16 UTC,"Sorry, my upload failed.  The .debs are there now."
1792109,2018-10-22 16:31:21 UTC,This bug was fixed in the package linux - 4.4.0-138.164
1792109,2018-09-12 09:38:41 UTC,"Skipped ""ext4: fix false negatives *and* false positives in ext4_check_descriptors()"" because it was already applied for bug #1792109."
1792118,2019-03-05 12:23:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792118,2019-03-05 08:41:07 UTC,I have a the same systemd version and DNS resolution sometimes fails due to cache issues.
1792132,2019-10-31 03:34:18 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1792135,2018-09-17 14:43:07 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1792135,2019-03-31 06:07:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792135,2018-09-12 11:39:54 UTC,"StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()"
1792141,2018-09-12 13:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1792141,2018-09-12 19:47:08 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1792141,2018-09-12 21:33:36 UTC,"Hello everybody, thank you for your messages. This is my first bug message. Therefore I ask for a little patience. Which logs are needed? I'll upload it as soon as I know which logs it should be."
1792141,2018-09-12 23:45:42 UTC,Hey Joseph Salisbury (jsalisbury) ;)
1792141,2018-09-13 08:43:18 UTC,"For better understanding.
In a system with two monitors operating side-by-side, the system behaves almost normally. (Only users who have installed Concky, for example, will notice that the monitor management is faulty.) If Concky runs two desklets on different monitors, a desklet will be hidden.)"
1792141,2018-09-13 08:58:21 UTC,I'm uploading the Xorg.0.log file now. Active Kernel: 4.15.0-34 (screen management with error)
1792144,2018-11-20 05:15:11 UTC,"I have the same bug on a similar motherboard - Asrock j4105-itx (j4105 CPU, asmedia asm1061, realtek rtl8111h)
After the boot sequence
KUbuntu 18.04 fully updated to Nov-19-2018
Bios 4.0.0.1245    Intel GOP  13.0.1011"
1792144,2018-09-12 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1792144,2018-09-12 15:36:45 UTC,"apport-collect ignores local proxy and hangs.
apport-bug doesn't show any relevant information and does not find any crash-reports (because there's noc crash, but only a dark screen)"
1792144,2018-09-12 19:45:41 UTC,The upstream bug states that the following commit resolves this bug:
1792144,2018-09-12 20:06:22 UTC,"yes, unfortunately we still see this bug (else we haven't filed it here)."
1792144,2018-09-14 16:54:32 UTC,we've just re-opened above mentioned bug at freedesktop
1792147,2019-12-19 15:33:26 UTC,Is this even still valid?
1792147,2019-12-20 14:21:18 UTC,@Julia - I'm guessing no. Even if it were I don't think there is enough info here to go on. I'm going to mark as invalid
1792159,2019-07-07 21:32:34 UTC,"Fixed in revision b029e4e44a066e8e225504042dcebe42d0d114dc
https://git.launchpad.net/kicad/patch/?id=b029e4e44a066e8e225504042dcebe42d0d114dc"
1792159,2019-07-07 02:07:32 UTC,All yours!
1792159,2019-07-06 22:21:40 UTC,"Hi Seth,"
1792159,2019-06-28 09:37:02 UTC,This should be easy to automate with the new ACTION framework (all info necessary is in the ACTION).
1792159,2018-12-11 19:26:43 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1792159,2018-09-12 15:42:59 UTC,This is a really good idea.  Thanks!
1792162,2018-09-12 14:55:22 UTC,"Hi, can just use custom configs and override the service plug-ins with all the plugins needed. Trunk is not in the current list so cannot be enabled with native kolla-ansible co fig.
 A file will look like.
Etc/kolla/config/neutron/<filename>"
1792162,2018-09-12 15:12:17 UTC,"HI
i try to so it and the reconfigure
[DEFAULT]
core_plugin = ml2
service_plugins = router,lbaasv2,trunk
this is not work :)"
1792162,2019-04-01 04:15:57 UTC,Hi.
1792162,2019-04-01 05:16:20 UTC,Hi i als try this this is not oveeride the config
1792162,2019-04-03 08:00:23 UTC,Could you show exactly what you're doing to override this config? You need to put a file in /etc/kolla/config/neutron.conf containing this:
1792162,2019-11-14 16:14:51 UTC,This needs more info from reporter
1792162,2020-01-14 04:17:32 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1792164,2019-06-18 04:17:40 UTC,[Expired for python2.7 (Ubuntu) because there has been no activity for 60 days.]
1792164,2019-04-19 01:00:22 UTC,we don't configure with --with-fpectl anymore. what do you expect?
1792164,2019-04-18 18:49:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792164,2019-04-18 22:02:30 UTC,This bug affects far more than 2 users.
1792166,2018-09-12 15:00:12 UTC,The work around is to disable MAAS' internal proxy.
1792166,2019-09-19 11:58:59 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1792176,2018-09-17 14:32:05 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1792183,2018-09-12 19:38:56 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1792183,2018-09-12 16:30:15 UTC,This change was made by a bot.
1792183,2018-09-12 22:11:15 UTC,"Resolved in v4.19 rc3. (though the laptop wont wake up from other ACPI wakeup event, such as LID0, even if enabled)"
1792184,2021-02-10 17:51:04 UTC,"Looking at our test server on 3.6.1, the EDI Messages grid now shows the label of the EDI account and not the ID."
1792184,2021-02-10 18:33:03 UTC,Marking Won't Fix as it's working in current master now
1792187,2018-09-17 16:30:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792187,2018-10-04 15:02:19 UTC,Please update the Software to its latest stable release!
1792187,2020-07-03 22:54:44 UTC,This was fixed in Ubuntu 19.10.
1792188,2018-09-12 18:10:19 UTC,Confirmed in 3.0.2
1792188,2018-09-12 19:10:10 UTC,This should have been fixed back in 3.0-alpha on bug 1672421.  I am not seeing this on 3.1.5 or on 3.2 beta (test server bugsquash.missourievergreen.org).
1792188,2018-09-13 17:43:08 UTC,Here's the commit for bug 1672421:
1792188,2018-09-13 20:50:57 UTC,"Thanks for the additional info, Michele.  I'm not sure why I wasn't seeing it on Missouri's test environment, but I checked on a local ""master-ish"" and now I am seeing what you reported."
1792188,2018-09-14 13:56:19 UTC,Here's a branch bringing back the hold refresh when paging between records:
1792188,2019-01-22 19:28:28 UTC,"Tested and worked for me. I consent to signing off on this patch with my name and email: John Yorio, <email address hidden>"
1792188,2019-05-07 15:53:13 UTC,"Pushed to master, rel_3_3, and rel_3_2. This doesn't affect 3.1.x as far as I can tell. Thanks, Mike and John!"
1792189,2019-06-07 23:43:59 UTC,I.e. instead of the current
1792189,2019-06-07 23:41:48 UTC,"Normally, postinst should only hint a trigger to run initramfs update. And not force creation of an initrd."
1792189,2018-09-19 07:57:18 UTC,"This isn't a bug in linux-firmware, it shouldn't depend on initramfs-tools, but initrafms-tools shouldn't fail miserably when called in this fashion either."
1792189,2018-09-12 17:02:43 UTC,script output from bionic with a linux-firmware deb with the above patch applied performing the installation without issue
1792189,2018-09-12 17:01:42 UTC,Patch to add the dependency
1792189,2018-09-19 08:19:38 UTC,"The attachment ""linux-firmware_1.173.1ubuntu1_source.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1792189,2018-09-12 17:00:54 UTC,script output from a recreate on bionic demonstrating the failure
1792193,2018-09-13 09:37:25 UTC,"Hi Kirill,
  That's a bit tricky to debug; could you build qemu from git and try and bisect between 2.12.0 and 3.0 to see which commit broke it?"
1792193,2018-09-14 10:09:22 UTC,"Yes I could, but it rebuilds too long. I will report results later, when find broke commit."
1792193,2018-09-14 18:02:18 UTC,"I try to bisect git version. When I run git bisect bad v3.0.0 it says:
Bisecting: 1298 revisions left to test after this (roughly 10 steps)
error: Your local changes to the following files would be overwritten by checkout:
        configure
        po/bg.po
        po/de_DE.po
        po/fr_FR.po
        po/hu.po
        po/it.po
        po/messages.po
        po/tr.po
        po/zh_CN.po
Please commit your changes or stash them before you switch branches.
Aborting
Something is wrong, isn't it?"
1792193,2018-09-15 14:23:24 UTC,"I can't do bisect, but I have installed qemu version 3.0.50 (v3.0.0-614-g19b599f766-dirty) from git and this works fine."
1792193,2020-11-12 18:25:38 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1792193,2021-01-12 04:17:34 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1792202,2018-11-21 01:30:27 UTC,grep reveals several references to obsolete URLs
1792202,2018-11-21 03:30:08 UTC,https://github.com/juju/juju/pull/9489
1792205,2018-09-13 19:46:11 UTC,"This option is selected as a result of having CONFIG_MTD_DOCG3. This seems to be very old hardware which only had experimental support, so I doubt there's any harm in disabling it. I agree that CONFIG_BCH_CONST_PARAMS looks to only make sense when the hardware is known. It seems it should be safe to disable these options."
1792229,2018-09-19 14:27:42 UTC,"I don't see a handle_snapshot() method implemented in StackResource even in master, so it looks like this was just never implemented for nested stacks."
1792230,2018-09-19 14:25:51 UTC,"I believe this was intentional. From memory it's because snapshots get deleted if the volume is deleted, but backups do not. So even though it makes the naming a little weird, there are circumstances where you wouldn't be able to restore the stack snapshot if it relied on volume snapshots."
1792231,2018-09-13 13:53:20 UTC,"Xenial and Bionic are not affected, only Trusty"
1792231,2018-09-13 13:49:36 UTC,"Ok, some magic affects containers int hat case (even ssh to the LXD and then re-ssh to itelf would not work).
But in a KVM guest I could recreate it."
1792231,2018-09-13 13:31:05 UTC,"Broken since security update on Thu, 05 May 2016
Fixed in Debian in openssh/1:6.7p1-5+deb8u7
Per the Debian bug they were affected as well re-using our CVE fixes in Debian."
1792231,2018-09-13 13:43:39 UTC,"I wanted to check if other releases are affected as well, but it was interesting as it didn't show up even on a Trusty container ssh'ing to itself."
1792233,2018-09-12 20:55:03 UTC,Syslog attachment.
1792240,2021-02-17 17:09:31 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1792248,2019-05-13 12:04:13 UTC,Would it be possible to get a lsblk from one of the impacted units? I'd like to see the partition layouts.
1792248,2019-07-13 04:18:04 UTC,[Expired for OpenStack ceph-osd charm because there has been no activity for 60 days.]
1792248,2018-10-16 00:27:26 UTC,"Additionally, on a cloud where the upgrade happened with all OSDs online, but when one crashed with the charm default of bluestore=true left enabled:"
1792255,2019-10-15 08:51:48 UTC,"Looks like it's fixed by that commit
https://gitlab.gnome.org/GNOME/network-manager-applet/commit/9ef81a0820"
1792270,2018-09-26 08:17:50 UTC,"Eric, I've proposed a change [1] to revert Eduardo's change [2] in kolla that removed ceilometer from upper-constraints, which should work now that [3] has merged. However, it is my understanding that ceilometer builds were fixed by that workaround."
1792270,2018-10-11 16:01:21 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/605351"
1792270,2018-09-27 21:03:06 UTC,Thanks Mark!  I learned a bit more about packages and how to install the development version from git (using setup.py) and was able to get the latest stable/rocky build installed (Kolla and Kolla-Ansible).
1792270,2018-09-26 09:27:09 UTC,"It's not a release, it's a git branch. You can clone it from here:
https://github.com/openstack/kolla/tree/stable/rocky"
1792270,2018-09-26 09:09:43 UTC,"It doesn't look like Kolla has a stable/rocky version?
https://releases.openstack.org/teams/kolla.html"
1792270,2018-09-26 08:58:17 UTC,"Yes, Eduardo's change was merged after 7.0.0.0rc1. I'd recommend trying the
stable/rocky branch."
1792270,2018-09-26 08:36:12 UTC,"Thanks Mark!  I had uninstalled, re-installed, and run kolla-build with the source option very recent and the problem still remained.  However, it looks like the changes Eduardo made (and you reverted) were to master?  Does that mean these changes were backported to the kolla 7.0.0.0rc1 build?  or only available in master?  Maybe that's my problem - using 7.0.0.0rc?"
1792270,2018-09-26 08:13:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/605351"
1792270,2018-09-15 16:49:42 UTC,"Hi, is an issue in openstack globals requirements. A patch is under review, once merged build will succeed. Affect both master and rocky branch."
1792270,2018-09-15 23:51:31 UTC,"Having a binary Package depends on the work of external project, while the pip packages are created during openstack releases"
1792270,2018-09-15 23:50:06 UTC,Binaries are the rpms or deb files created by Ubuntu and RDO. Sources are the installation of pip packages directly without any modifications or downstream work specific to a distro.
1792270,2018-09-15 23:40:03 UTC,"Aren't the binaries just builds using the source options and pushed to the Docker repository?  I don't know when/where this happens, so maybe I'm missing a piece as to why some binaries are created for CentOS (for example) and others are not."
1792270,2018-09-15 23:28:08 UTC,Probably there is no binary available for the distro used.
1792270,2018-09-15 23:19:09 UTC,"Thanks for the explanation!  I'm still learning, so this helps put the pieces together."
1792270,2018-09-15 22:33:06 UTC,Related parts of the issue:
1792270,2018-09-15 22:19:45 UTC,"Hi, this wasn't catched at CI because was a change outside kolla and after rocky branch was created.
A pip package was created for ceilometer which wasn't before, this affect any project installing ceilometer."
1792270,2018-09-15 21:59:05 UTC,"Thanks Eduardo!  Due to ignorance of the process, can you help me understand how something like this gets past all of the Ci/CD build processes?  Again, I don't know much about this process, but this seems like a pretty significant issue that should have been caught before it affected everyone from deploying OpenStack (at least with Kolla)?"
1792270,2018-09-25 23:49:16 UTC,"Hi Eduardo,"
1792276,2018-09-13 03:31:21 UTC,It's good to support it IMO.
1792279,2019-09-21 10:06:51 UTC,"done
+ warning message to remind move the old file when you change path into preference"
1792280,2018-10-05 04:13:48 UTC,Looking into this:
1792280,2018-10-08 16:33:06 UTC,A notification would be good so that they know why the person dropped off their list and they can go for another try if they wanted to.
1792285,2019-02-12 13:28:55 UTC,Is it still an issue?
1792285,2019-05-19 04:17:37 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1792294,2019-08-21 02:51:22 UTC,"I mean the kernel is bootable is you install 0.131ubuntu15 and regenerate the initramfs. They have a later version now, hopefully it fixes the issues as well."
1792294,2019-08-16 07:59:08 UTC,"Hi Kai-Chuang Yan,"
1792294,2018-10-19 07:08:31 UTC,This bug seems to be fixed in the latest release (0.131ubuntu15).
1792294,2019-08-16 08:16:14 UTC,Add: this problem only happens in new kernel version. I can boot system with the old kernel version.
1792298,2018-12-06 00:32:05 UTC,That patch is applied upstream in the package shipped in bionic and later
1792298,2018-12-06 00:29:10 UTC,Thanks for the patch and testing instructions
1792298,2018-12-03 12:32:18 UTC,"Confirmed.
Without the following patch, wrong exit status code would be reported."
1792298,2018-11-30 08:09:14 UTC,"Sorry for being late to reply.
My co-worker found another related problem and we needed to fix that alongside."
1792298,2018-09-13 06:34:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792298,2018-09-14 07:58:47 UTC,"> b) a summary of steps to reproduce it to verify and evaluate for the SRU team.
"
1792298,2018-09-14 07:25:17 UTC,"On our environment (Xenial), I will verify the fix."
1792298,2018-09-14 07:15:56 UTC,@Christian
1792298,2018-11-29 13:37:32 UTC,"Missing feedback, any chance you get to that Takuya?"
1792298,2018-09-14 06:46:41 UTC,"Patch included since keepalived-1.3.2, due to that only Xenial is affected as reported."
1792300,2019-08-29 20:00:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792300,2019-10-07 14:55:16 UTC,"Sorry for the lack of timely feedback. Is this still an issue with the latest chromium version in Ubuntu 16.04 ? Does it work on 18.04 or newer Ubuntu releases, by any chance?"
1792300,2019-10-07 15:58:01 UTC,I can confirm that this does not work in any version of Ubuntu.
1792300,2019-10-08 10:23:49 UTC,"I can confirm this doesn't work in chromium, neither snap (tested in 19.10) nor deb (tested in 18.04)."
1792300,2019-10-08 15:43:57 UTC,You don't need to go to any web page in particular to test this.
1792300,2020-07-26 08:49:08 UTC,"User activation has been added to my trick for Chromium:
http://www.lonniebest.com/CardTrick/"
1792300,2020-07-27 04:33:03 UTC,"I was able to get Speech Synthesis working in Kubuntu via Firefox:
https://askubuntu.com/a/1262310/256054"
1792300,2020-09-19 17:07:27 UTC,Speech synthesis processing is not shipped in Chromium source code.
1792300,2020-09-19 17:35:16 UTC,Current broken state of speechSynthesis at Chromium https://bugs.chromium.org/p/chromium/issues/detail?id=1130231
1792304,2019-04-17 21:04:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792312,2018-09-17 14:31:14 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1792329,2019-04-25 15:58:44 UTC,"It happens with more than one open card, especially with Facebook.
I have the swap configured, with Ubuntu it can be about 300 Mb in swap.
It seems to me that random happens without apparent similarities between the cases, and since February it has never happened again."
1792329,2019-04-25 13:13:02 UTC,"Stefano, can you elaborate on the exact problem you're seeing now?
Is there a series of steps that can reliably reproduce the problem?"
1792329,2019-02-09 16:18:11 UTC,"Now the PC is no longer blocked, sometimes the pages present the problem of not loading."
1792329,2019-07-03 04:17:28 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1792329,2019-02-09 13:35:05 UTC,Is this still an issue now that Firefox 65.0 is the currently supported version?
1792329,2018-11-16 18:28:49 UTC,Could it be that your system is running out of memory? Do you have swap configured?
1792329,2018-11-10 11:45:08 UTC,This is a picture of the screen. I had to restart Firefox.
1792329,2018-11-12 19:17:00 UTC,"When I made the report it happened more often, and I seem to remember (but I'm not sure) that it did it even without extensions.
Now it happens much less.
It happens randomly, but sometimes it blocks the PC."
1792329,2018-11-12 08:52:33 UTC,"Thanks for the additional information Stefano.
It appears you're using a number of extensions. Does the problem occur if you disable all extensions?"
1792329,2019-05-03 08:55:28 UTC,"Thanks for the feedback Stefano. I'll mark the bug incomplete, which will make it expire in about 60 days. If in the meantime you're seeing the problem again, please comment, and we can re-assess."
1792329,2018-11-10 11:01:21 UTC,apport information
1792329,2018-11-10 11:01:12 UTC,apport information
1792329,2018-11-10 11:01:17 UTC,apport information
1792329,2018-11-10 10:50:07 UTC,"Stefano,"
1792329,2018-11-10 11:01:04 UTC,apport information
1792329,2018-11-10 11:01:18 UTC,apport information
1792329,2018-11-10 11:01:07 UTC,apport information
1792329,2018-11-10 11:01:08 UTC,apport information
1792329,2018-11-10 11:01:05 UTC,apport information
1792329,2018-11-10 11:01:11 UTC,apport information
1792329,2018-11-10 11:01:13 UTC,apport information
1792329,2018-11-10 11:01:14 UTC,apport information
1792329,2018-11-10 11:01:16 UTC,apport information
1792329,2018-11-10 11:01:10 UTC,apport information
1792329,2018-11-10 11:01:09 UTC,apport information
1792336,2018-10-22 16:31:21 UTC,This bug was fixed in the package linux - 4.4.0-138.164
1792338,2019-08-18 14:16:04 UTC,"I'm running official Ubuntu 18.04 and this bug is still there.
I should manually generate fa_IR and change the /etc/default/locale to the right value."
1792338,2020-03-21 06:38:08 UTC,"I'm using Ubuntu 18.04 too and also I have a laptop with Ubuntu Mate 19.10 and another with Xubuntu 20.04 beta, none of them correctly recognize the true locale.
I think the problem is caused by auto-recognition of locale from the Internet."
1792338,2020-03-21 06:39:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792344,2018-09-20 15:24:24 UTC,"Change abandoned by Ian Y. Choi (<email address hidden>) on branch: master
Review: https://review.openstack.org/602356
Reason: Thanks a lot for interacting with Contributhon (Contribution + Hackathon) in Korea. No need to merge - let's abandon it"
1792348,2019-09-16 10:31:02 UTC,"Test split into 3:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=a5fc2f32e2bb988449f61c8c9210d07ee82e52c6"
1792349,2018-09-13 10:00:06 UTC,This change was made by a bot.
1792349,2018-09-13 13:17:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1792349,2018-09-13 17:40:56 UTC,I re-ran on 4.19.0-041900rc3-generic #201809120832 SMP Wed Sep 12 12:35:08 UTC 2018 and am still seeing the leak.
1792349,2018-09-17 09:17:57 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1792349,2018-09-19 10:00:04 UTC,"Bug reported - link to email is here ->
https://www.spinics.net/lists/cgroups/msg20593.html"
1792349,2018-10-11 08:51:09 UTC,"Hi, as per this update -> https://www.spinics.net/lists/cgroups/msg20660.html"
1792349,2018-10-23 10:21:30 UTC,"Hi, any update on what needs to happen to get these patches backported to a 4.15 Kernel build for Ubuntu 18?"
1792349,2018-10-24 19:24:38 UTC,"Because there are a few and they affect the memory management layer, it might be best to submit these patches to the Ubuntu Kernel Team mailing list for feedback."
1792349,2018-10-31 19:34:10 UTC,This issue also exists on the Linux-azure kernel series.
1792349,2018-11-02 05:34:39 UTC,"More patches are required: https://lkml.org/lkml/2018/11/2/182
It looks we'll have to wait for some time, before the kernel stabilizes..."
1792353,2018-10-09 13:09:42 UTC,"Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-29-generic
cryptsetup: WARNING: failed to detect canonical device of overlay
cryptsetup: WARNING: could not determine root device from /etc/fstab
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=41df2b38-d40b-4dcc-a7f8-378892ae25a3)
I: Set the RESUME variable to override this.
cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file or directory
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1"
1792357,2018-10-05 17:44:02 UTC,"Reviewed:  https://review.openstack.org/597357
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=a71f447ce72c7408033ffd622270d8ffd9a588cd
Submitter: Zuul
Branch:    stable/queens"
1792361,2018-11-21 16:43:52 UTC,"Also Win 7 64
Could be very useful while putting an other audio source or standalone tool for sound processing in the stream in auto DJ mode.
While using virtual audiocable etc."
1792361,2018-11-21 16:58:05 UTC,That's exactly what I was trying to do when I reported this bug.
1792361,2019-05-22 09:45:07 UTC,"I just want to bump this with:
https://www.mixxx.org/forums/viewtopic.php?f=3&t=12537"
1792361,2019-05-22 09:56:48 UTC,"Add to my last comment:
Version of mixxx is the current nightly:
2.3.0~alpha~pre-0ubuntu1~master~git6789~bionic"
1792364,2018-10-05 17:44:05 UTC,"Reviewed:  https://review.openstack.org/597357
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=a71f447ce72c7408033ffd622270d8ffd9a588cd
Submitter: Zuul
Branch:    stable/queens"
1792369,2019-10-11 10:50:30 UTC,"any news regarding this?
we are experiencing high memory usage on ubuntu 18.04 too.
machine has about 256G ram, with ubuntu 18.04 bionic
after 1.5day glusterfs mount uses about 40% of available memory."
1792373,2018-10-23 19:40:24 UTC,"Posted as https://github.com/testing-cabal/subunit/pull/32, but I am probably missing something and getting https://github.com/testing-cabal/testtools/issues/121"
1792373,2018-09-13 12:40:33 UTC,"Or is it completely useless, because apparently https://src.fedoraproject.org/rpms/python-subunit/blob/master/f/dead.package the Python package has been replaced by the large subunit package, wasn't it?"
1792373,2018-09-13 11:52:30 UTC,"That seems reasonable to me; can you propose it on GitHub, and maybe we can get lifeless to have a quick look at it as well?"
1792373,2018-09-13 15:10:03 UTC,"Please, ignore the previous comment, it is nonsense."
1792383,2018-09-13 13:15:08 UTC,"Skipped ""x86/mm/pat: Fix L1TF stable backport for CPA"" because that would only be required if we had reverted ""86/mm/pat: Ensure cpa->pfn only contains page frame numbers"" which upstream stable did in 4.4.104 but we did not. By sheer luck this failed to apply because of incorrect use of tabs and spaces in our version. Not sure what the issues were which led to the revert but if we ever have to we also need to pick up this one."
1792383,2018-10-22 16:31:21 UTC,This bug was fixed in the package linux - 4.4.0-138.164
1792386,2019-09-10 15:38:05 UTC,cod-tools 2.2+dfsg-3 was sync'd into Ubuntu 19.04.
1792386,2019-09-10 15:58:04 UTC,"On 2019-09-10 18:38, Graham Inggs wrote:

> cod-tools 2.2+dfsg-3 was sync'd into Ubuntu 19.04.
>
> For future reference, this can be done using the requestsync tool, see:
> https://wiki.ubuntu.com/SyncRequestProcess
"
1792387,2018-09-13 14:02:55 UTC,Patch: https://lists.ubuntu.com/archives/kernel-team/2018-September/095430.html
1792417,2018-09-13 21:50:36 UTC,"Presuming this is using the Text and Font dialog, not replicated on Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1 64bit."
1792417,2018-10-07 11:40:43 UTC,confirmed on .92.3 but looks fixed in master
1792421,2018-09-13 20:38:13 UTC,What's the difference with evenly spacing baselines ?
1792421,2018-09-13 21:51:18 UTC,"When you space evenly baselines for text objects of different sizes, they
may overlap or just produce uneven white spaces between lines."
1792421,2020-03-21 19:09:16 UTC,Closing because INVALID: NOT A BUG.
1792423,2018-09-14 07:25:24 UTC,"Hi,"
1792424,2020-06-15 21:23:34 UTC,Could you try on a newer Ubuntu version if you can confirm it's resolved?
1792424,2020-06-15 14:30:58 UTC,I think this was fixed upstream like four years ago:
1792424,2020-06-09 17:47:44 UTC,"> Reporting upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ would be more useful than arguing over bug settings on this ticket...
"
1792424,2020-06-09 17:46:18 UTC,"When this happens, it often also happens that a process whose name I can't remember right now but that has the word ""trash"" in it, consumes an awful lot of CPU during the time the flickering is observed (which is sometimes several minutes)."
1792424,2020-02-17 08:51:51 UTC,Reporting upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ would be more useful than arguing over bug settings on this ticket...
1792424,2020-02-13 15:44:30 UTC,Please fix the importance.
1792424,2019-09-28 15:39:48 UTC,Why the f*** has nothing been done on this for over a year?
1792424,2020-06-16 16:01:37 UTC,No I can't.
1792424,2019-04-26 16:37:43 UTC,"> This is a huge usability issue.
"
1792424,2019-04-26 16:33:36 UTC,How is this importance low???
1792424,2019-04-25 23:19:20 UTC,"I believe that I found a ""solution"", I don't know what caused it. After suffering with the problem for 2 weeks I discovered that emptying the trash the terminal way solved it. It seems Nautilus was having issues with something in the rubbish bin via the below command."
1792424,2019-04-23 00:55:14 UTC,"I am also suffering from this problem when deleting images (I delete around 2k and I can reproduce it immediately also). Occurs from network part of sidebar down. I have a video to show the effect.
https://youtu.be/lxMjDEEEKX4"
1792424,2019-04-04 18:27:11 UTC,Affects me too.
1792424,2019-04-01 04:17:49 UTC,[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]
1792424,2019-01-29 23:37:45 UTC,Do you still see that problem in newer Ubuntu versions?
1792424,2019-01-30 15:38:43 UTC,"> Do you still see that problem in newer Ubuntu versions?
"
1792424,2019-04-29 07:19:53 UTC,Could someone having the issue record a screencast showing the bug?
1792429,2018-09-13 21:52:20 UTC,"Issue and fix confirmed.  Thanks, Galen.  Merged to master."
1792429,2018-09-13 18:09:39 UTC,A patch is available in the user/gmcharlt/lp1792429_point_queue_position_in_right_direction branch:
1792429,2019-01-14 16:37:23 UTC,Adding a 3.1.x target since bug 1712854 is set to be backported.
1792442,2018-09-13 18:58:28 UTC,I try to install libxp6 for IDL and get crashes all the time.  Firefox brings this up.
1792452,2018-09-14 18:08:28 UTC,Thanks for reporting.
1792459,2018-09-14 20:01:49 UTC,"In the public cloud operators session in Denver 2018, we discussed the potential for at least coalescing the direct-to-database ownership transfer operations into a single place where we could collaborate on the safest possible option."
1792464,2018-10-09 13:03:15 UTC,"Processing triggers for linux-image-4.15.0-1017-oem (4.15.0-1017.20) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-1017-oem
/usr/share/initramfs-tools/hooks/udev: 190: /usr/share/initramfs-tools/hooks/udev: Cannot fork
E: /usr/share/initramfs-tools/hooks/udev failed with return 2.
/usr/sbin/mkinitramfs: 181: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/update-initramfs: 165: /usr/sbin/update-initramfs: Cannot fork
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
dpkg: error processing package linux-image-4.15.0-1017-oem (--configure):
 installed linux-image-4.15.0-1017-oem package post-installation script subprocess returned error exit status 1"
1792473,2018-09-14 11:54:48 UTC,"I found two upstream bugs that look related, but they seems to imply that the problem has existed for a long time, not a regression introduced by chromium 69:"
1792473,2018-09-14 15:22:21 UTC,"Yes, the problem existed in Google Chrome for quite a long time, but Chromium was not affected until the latest update."
1792473,2018-09-14 15:23:58 UTC,"At least not Ubuntu build of Chromium. Maybe there was a patch that was dropped, I don't know. But I am working with IPv6 all the time and instantly noticed the change of behavior."
1792473,2018-09-14 15:42:22 UTC,"No distro-patch related to IPv6 was dropped/added in chromium, so it must be an upstream change that triggered the change in behaviour.
Can you comment on one of the upstream bugs to try and get attention from the developers at Google?"
1792473,2018-09-14 16:06:41 UTC,"https://bugs.chromium.org/p/chromium/issues/detail?id=216388 is not related to the issue I am reporting.
https://bugs.chromium.org/p/chromium/issues/detail?id=516305 - left a comment here, but I am sure Google will not care. Looks like Chromium needs a patch disabling Async DNS feature."
1792493,2019-02-18 15:29:20 UTC,"According to Rodolfo's explanation, so we can close this bug."
1792493,2019-02-14 15:32:42 UTC,Hello:
1792493,2018-09-27 19:44:46 UTC,"It is only an issue with respect to the external bridge configuration, which includes ext-net for floating IPs.  If there are multiple bridges defined, such as ext-net, br-prov001, br-prov001, etc., all associated with VLANs on the same physical interface, or a team/bond interface, the same MAC address is given to all of these physical interfaces, and this appears to be where the problem lies.  Once the MAC address was forcefully changed to unique MAC addresses per VLAN on a physical interface, then external bridges have worked perfectly."
1792493,2018-09-27 14:59:14 UTC,"The unique MAC address is only used for the DVR host MAC.
We always have the same MAC for the router ports that are distributed and not sure why this should be an issue..
So I am assuming that it is with respect to your external bridge configuration that you are having this problem.
Can you confirm."
1792493,2018-09-17 11:13:55 UTC,"It appears my theory was correct.  I wrote some code to change the ifcfg files so the MAC addresses of all VLAN interfaces was unique, and after a re-deploy, floating IPs work as expected, even with a provider network defined."
1792493,2018-09-17 07:18:50 UTC,I think I may have found the issue.
1792493,2018-09-15 20:46:12 UTC,"Just a quick note that kernel version doesn't appear to matter.  My latest deploy was with no yum updates, so the kernel was:
Kernel: Linux 3.10.0-862.el7.x86_64"
1792493,2018-09-16 23:00:48 UTC,I believe I have narrowed it down to adding a provider network in the globals.yml file such as:
1792493,2018-09-17 06:31:13 UTC,I have done additional testing and the provider network configuration is the cause:
1792493,2018-09-14 04:15:52 UTC,It is interesting that OVS reports br-int's port for fg-ba492724-bd as down:
1792493,2018-09-14 21:35:39 UTC,"I have a Queens environment that works, so I am comparing everything possible between it and the Rocky deployment."
1792493,2018-09-14 22:51:36 UTC,"I looked at the openvswitch log file here (from inside the openvswitch-vswitchd container):
/var/log/kolla/openvswitch/ovs-vswitchd.log"
1792493,2018-09-15 02:25:05 UTC,Rocky has been re-deployed with only br-ex and prov001 external bridges and the same problem is occurring.
1792493,2018-09-16 07:02:28 UTC,"Ok, after simplifying the deployment (as I mentioned in the previous message), DVR is working as expected with floating IPs."
1792493,2018-09-14 22:29:08 UTC,One significant difference I see is the OVS flows created on the br-ex bridge:
1792497,2018-10-16 15:40:04 UTC,"The logs here are missing, but I think the likely cause is this:"
1792497,2018-09-14 19:26:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792497,2018-10-25 23:28:20 UTC,"The verification of the Stable Release Update for shim-signed has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1792497,2018-09-30 09:16:58 UTC,In my case I have installed ubuntu 14.0.5 instead of windows 10 and got this error
1792497,2018-10-25 23:24:16 UTC,"With the correct sources.list settings, I see:"
1792497,2018-10-25 20:08:05 UTC,"Hi, we encountered this error during installations of the SecureDrop application, which uses Ubuntu 14.0.4.5 for its server-side OS. We put out an advisory which you can find here: https://securedrop.org/news/advisory-server-installation-failure-uefi-boot-mode/ -but basically we're seeing the same error as described above."
1792497,2018-10-25 23:28:16 UTC,This bug was fixed in the package shim-signed - 1.33.1~14.04.3
1792497,2018-10-16 16:59:57 UTC,"And in fact, I see that trusty-updates currently has shim 13-0ubuntu2, but the newest version in cosmic/bionic is 15+1533136590.3beb971-0ubuntu1 which has not yet been SRUed to trusty because there are updates needed for other packages before it can land."
1792497,2018-10-16 16:14:52 UTC,"I see; the version of dpkg in trusty-updates does support control.tar.xz (dpkg 1.17.5ubuntu5.8; LP: #1730627), but the version of dpkg in the trusty release pocket does not.  So testing on an up-to-date trusty environment would not hit this bug."
1792497,2018-10-16 16:10:49 UTC,"It's correct that the shim binary that gets published to trusty is built on bionic; we only have one shim binary that's current at any given time (each must be signed separately by microsoft, we don't have separate binaries per series).  But obviously the .deb published to trusty needs to be installable with trusty dpkg."
1792497,2018-10-16 15:42:55 UTC,"Łukasz, looks like you binary published Trusty's shim built on Bionic. Please could you take a look?"
1792497,2018-10-25 15:35:45 UTC,"Hello PRATIK, or anyone else affected,"
1792497,2018-10-25 23:20:22 UTC,shim 13-0ubuntu2 is present in the trusty-updates repository.  Did you remove trusty-updates from your sources.list when enabling trusty-proposed?
1792499,2019-02-20 09:38:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792499,2019-02-20 09:39:51 UTC,Confirming for 18.04.2
1792500,2018-09-17 14:30:31 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1792503,2018-10-22 12:32:16 UTC,"This bug has been already fixed on placement/master
The backport to nova/stable/rocky is under review.
This bug will be ported to nova/master unless extraction is completed in Stein cycle."
1792503,2019-02-21 16:31:07 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/607454
Reason: Abandoning since https://review.openstack.org/#/c/608903/ is abandoned (until someone expresses a need for it)."
1792503,2019-02-21 16:30:43 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/608903
Reason: I'm going to abandon this since as far as I'm aware nothing is using nested providers in stable/rocky (nova isn't) so I think until this is needed by someone we don't need to backport it. I'm abandoning to clean up the nova stable/rocky review queue."
1792503,2018-10-09 10:03:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/608903"
1792503,2018-10-03 02:36:31 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/607454"
1792503,2018-10-03 04:48:50 UTC,This bug has been fixed on the master of the placement repository. (https://review.openstack.org/#/c/602638/ and https://review.openstack.org/#/c/602639/)
1792503,2018-09-14 22:58:31 UTC,member_of$N (granular request group) is *not* affected by this bug.
1792503,2018-09-14 20:44:37 UTC,"https://review.openstack.org/#/c/602638/
https://review.openstack.org/#/c/602639/"
1792508,2018-09-29 11:09:51 UTC,"Alright, it is not that black and white, so here're the reproduction steps:
Assumption: no byobu, tmux, nor screen processes are running
$ ps -ef |grep byobu
And if they do, kill them."
1792508,2018-11-01 11:23:01 UTC,"To fix this, change the shebang line in
/usr/local/lib/byobu/include/select-session.py
(or /usr/local/Cellar/byobu/5.127/lib/byobu/include/select-session.py)"
1792508,2018-12-29 00:49:33 UTC,"Hi @Ben, your fix works great! Thanks for it"
1792508,2018-09-29 10:40:04 UTC,"I have exactly same issue, but I use MacPort to install Byobu."
1792510,2018-10-31 13:31:25 UTC,"I am also getting this error message, and I am also on 1.0.18."
1792511,2018-09-14 10:22:09 UTC,I am not sure if issue is caused by network-manager or netplan or gnome-shell or two/all of them combined.
1792511,2019-01-08 16:26:41 UTC,"Thank you for your bug report, that has been reported upstream also on
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/216#note_345395"
1792512,2018-09-14 06:13:54 UTC,"Observed on Arch Linux with Inkscape 0.92+devel (8b8e0a6670, 2018-09-13)"
1792512,2020-03-21 18:59:43 UTC,Closing because DUPLICATE ISSUE.
1792514,2018-09-21 18:20:54 UTC,https://gitlab.com/inkscape/inkscape/commit/ec7a928bacad3df202e92b552f50af4dc9e275cb
1792514,2018-09-14 06:13:46 UTC,"Observed on Arch Linux with Inkscape 0.92+devel (8b8e0a6670, 2018-09-13)"
1792518,2018-11-28 01:26:50 UTC,"https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/434132/
https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/434310/"
1792520,2018-10-24 12:29:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792521,2018-09-28 06:30:58 UTC,"Hmm, there is another aspect of sending this to the Homedir:

> Log output will be written to: C:\Users\klaus\.widelands\stdout.txt
"
1792521,2018-09-28 06:50:47 UTC,"If there is no stdout.txt in those directories, you can't. Please open a separate bug for it and target it to Build 20, because tis bug is about the rerouting of stderr, and your bug is about stdout."
1792521,2019-09-15 17:08:11 UTC,Migrated to https://github.com/widelands/widelands/issues/1081
1792523,2018-09-14 15:48:55 UTC,"To clarify, are the problematic USB passthrough devices these:"
1792523,2019-10-22 04:45:46 UTC,"I tested this again on the latest Qemu and Linux kernel and cannot reproduce it anymore, so this can be closed now.."
1792523,2018-09-14 18:26:21 UTC,The usb-host devices have the problem.
1792535,2018-09-14 08:38:27 UTC,The attached patch simply removes the two include lines
1792535,2018-09-14 12:23:08 UTC,"The attachment ""Quilt patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1792536,2019-05-07 07:04:38 UTC,KBL will use another bug.
1792536,2018-09-17 09:47:47 UTC,"this commit only fix DNV, instead of KBL-NUC. Our engineer is contacting upstream for confirmation. The commit will be soon for KBL-NUC. I will input the commit here."
1792536,2019-05-07 07:06:19 UTC,"for KBL, it will old watchdog driver. Not a kernel issue."
1792536,2018-09-17 08:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1792536,2018-09-14 08:22:56 UTC,"if needed, it can also cherry picked to 18.10 or 16.04.x. Dawson Canyon is supported by Canonical with OEM image."
1792536,2018-09-17 09:17:01 UTC,"@Quanxian, by the way, can you share with us how exactly we can verify this feature in Dawson Canyon after we add this commit please?"
1792536,2018-09-17 04:21:52 UTC,"@Quanxian, Dawson Canyon has already been migrated to 16.04.5. We will get the Canonical kernel team to review this patch and see if it can be back ported to Xenial."
1792543,2018-09-17 07:57:30 UTC,adding myself as a subscriber
1792543,2019-01-02 14:42:27 UTC,Any update on this?
1792543,2019-02-01 23:26:25 UTC,According to the Terraform registry [1] the Terraform AWS EKS module is now provisioned over 44 000 times since it's inception in June 2018. It build a community around it with 46 contributors and many more users [2]. In total there are 14 releases of the module [3] and it is actively maintained by two core maintainers.
1792543,2020-10-09 19:42:46 UTC,"Hi,"
1792544,2019-01-23 23:49:49 UTC,This bug was fixed in the package clamav - 0.100.2+dfsg-2ubuntu1
1792544,2019-01-23 17:24:29 UTC,This bug was fixed in the package libpam-mount - 2.16-9ubuntu2
1792544,2018-11-09 17:24:25 UTC,systemd uses pcre2 for a useful journal feature that we can't enable until pcre2 is in main LP: #1751006
1792544,2018-10-18 01:39:37 UTC,libpam-mount 2.16-9 uses pcre2 (for real this time)
1792544,2018-09-28 08:35:54 UTC,"FYI
NMAP
Started to consider pcre2 due to the bug, but they have zillions of regrex use cases and it would be a major effort that doesn't seem to happen anytime soon."
1792544,2018-10-14 22:55:20 UTC,https://launchpad.net/debian/+source/libpam-mount/2.16-8
1792544,2018-09-26 11:46:05 UTC,Summarizing the Server Team related task status for a better overview.
1792544,2019-01-24 00:00:20 UTC,quagga was another false Build-Depends so I filed a Debian bug requesting they drop the pcre3 Build-Depends.
1792544,2018-10-14 23:02:53 UTC,libpam-mount wasn't actually switched to pcre2. I filed a Debian bug to let its maintainer know.
1792544,2019-01-24 00:03:40 UTC,libslang2-modules is in universe although it's built from the slang2 source. I guess that means we can mark it invalid here?
1792544,2019-05-01 20:17:30 UTC,The situation with apache2 is what I documented in https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:
1792544,2019-01-30 06:44:12 UTC,This bug was fixed in the package git - 1:2.20.1-2ubuntu1
1792544,2019-03-14 14:37:36 UTC,"Please do not forget to remove the pcre patch from Tilix, see https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1818991 - thanks!"
1792544,2019-04-29 23:07:41 UTC,This bug was fixed in the package zsh - 5.7.1-1ubuntu1
1792544,2019-05-01 18:37:28 UTC,"Regarding apache2, https://bz.apache.org/bugzilla/show_bug.cgi?id=57471 is still open, and I just tried a 2.4.38 build with pcre2, and it doesn't work. Switching the task back to incomplete according to the bug instructions."
1792544,2018-09-18 16:00:24 UTC,NGINX has technically said this is won't fix:
1792544,2019-05-01 20:33:32 UTC,"Thanks for the update, I missed that comment (again). I guess it can be moved back to ""triaged"" then."
1792544,2019-05-01 20:54:01 UTC,zsh is not really fixed. Please see the changelog entry of 5.6.2-3 which states:
1792544,2019-05-07 23:09:20 UTC,This bug was fixed in the package libselinux - 2.9-1
1792544,2019-07-31 14:32:26 UTC,sssd master has pcre2 support via https://github.com/SSSD/sssd/pull/677#issuecomment-508238642
1792544,2019-01-24 04:49:41 UTC,This bug was fixed in the package wget - 1.20.1-1ubuntu3
1792544,2018-09-18 13:26:39 UTC,This bug was fixed in the package apr-util - 1.6.1-2ubuntu1
1792544,2019-05-02 12:47:39 UTC,"Switching zsh back to incomplete, according to previous comment. Thanks for noticing that."
1792544,2018-09-18 12:10:04 UTC,"Nice find, I looked in trac but must have missed that..."
1792544,2018-09-14 13:13:35 UTC,Debian's git has already switched
1792544,2018-09-14 13:14:00 UTC,Debian's php7.3 has already switched
1792544,2018-09-14 13:14:54 UTC,Debian's clamav has already switched.
1792544,2018-09-14 14:25:11 UTC,Nginx properly builds with pcre2
1792544,2018-09-15 20:30:06 UTC,zsh in Debian Unstable (5.6.2-1) seems to build fine if I exchange libpcre3-dev by libpcre2-dev in Build-Depends and Build-Using (via debian/rules).
1792544,2018-09-17 10:45:56 UTC,wget builds and works with pcre2 in Debian (uploaded). I cannot change the Status to Triaged. Maybe somebody with higher privileges can change the wget status of this bug to Triaged. thx.
1792544,2018-09-18 06:30:57 UTC,"I've seen the wget debian change, but just switching builddeps from pcre3-dev to pcre2-dev and rebuilding isn't enough. The package ends up not finding pcre and doesn't enable it:
checking for PCRE... no
checking pcre.h usability... no
checking pcre.h presence... no
checking for pcre.h... no
...
  Libs:              -luuid -lidn2 -lnettle -lgnutls -lz -lpsl"
1792544,2018-09-18 07:37:38 UTC,"Andreas: No, it’s not a bug.  PCRE2 is a new project that’s not intended to be compatible with the older PCRE (i.e. what Debian misnamed “pcre3”).  The API is completely different and this is expected.  See bug 1636666 for context, and specifically the PCRE2 release announcement linked in the bug description:"
1792544,2018-09-18 07:41:37 UTC,apr-util has a false Build-Depends on libpcre3-dev; it should simply be dropped.  A corresponding Depends was already dropped in https://bugs.debian.org/757140.
1792544,2018-09-14 10:58:05 UTC,sssd builds fine with libpcre2-dev
1792544,2018-09-18 07:56:35 UTC,"Copying from https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1636666/comments/20, HAProxy and SELinux upstream support PCRE2."
1792544,2018-09-18 08:17:30 UTC,"• Aide: no PCRE2 support
• Exim: no PCRE2 support, upstream bug: https://bugs.exim.org/show_bug.cgi?id=1878
• FreeRADIUS: no PCRE2 support, mentioned in passing: https://github.com/FreeRADIUS/freeradius-server/issues/1865
• GLib: no PCRE2 support
• grep: no PCRE2 support"
1792544,2018-09-18 08:26:37 UTC,"• pam_mount: no PCRE2 support
• nmap: no PCRE2 support
• postfix: no PCRE2 support, http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
• pyScss: no PCRE2 support"
1792544,2018-09-18 08:31:38 UTC,"• Quagga: no PCRE2 support
• Rasqal: no PCRE2 support
• S-Lang: no PCRE2 support"
1792544,2018-09-18 08:35:39 UTC,reported upstream: https://savannah.gnu.org/bugs/index.php?54677
1792544,2018-09-18 08:37:58 UTC,"Actually, sssd build would still pull libpcre3-dev because of some dependency, and then use that... and upstream config phase doesn't support pcre2. I've filed a bug upstream."
1792544,2018-09-18 08:45:10 UTC,"I think that completes the analysis of the current state of things.  Although it seems infeasible to demote PCRE at this time, there’s no reason that should block the promotion of PCRE2, especially seeing as a bundled copy of PCRE2 is already in main (18.04 and 18.10) via libqt5core5a."
1792544,2018-09-18 08:54:29 UTC,Note to those filing upstream bugs: probably don’t call the old library “pcre3” since that’s not a thing outside Debian/Ubuntu.
1792544,2018-09-18 08:56:47 UTC,sssd: https://pagure.io/SSSD/sssd/issue/3833
1792544,2018-09-18 09:43:07 UTC,"Hi,"
1792544,2018-09-18 10:22:26 UTC,"Likewise, nginx does not support PCRE2: https://trac.nginx.org/nginx/ticket/720"
1792544,2018-09-18 08:04:15 UTC,apr-util: filed a Debian bug.
1792544,2018-09-18 12:27:08 UTC,glib is filed upstream as https://gitlab.gnome.org/GNOME/glib/issues/1085
1792549,2018-09-14 10:11:12 UTC,I forgot to mention that the pod has the right notation:
1792550,2018-09-14 10:25:53 UTC,SOLVED:
1792550,2018-09-14 11:02:59 UTC,...AND my changed
1792562,2018-11-02 02:27:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792563,2019-07-29 15:31:08 UTC,"The bug was in stestr and it is fixed:
https://github.com/mtreinish/stestr/commit/09cc5d2a41ec04b808770ef4b41f1087b5c7e8cb#diff-c6629310ffaaf8e44b83fea266c89480"
1792573,2018-09-14 12:48:30 UTC,"StacktraceTop:
 __assert_fail_base (fmt=0x7f6078627622 <error: Cannot access memory at address 0x7f6078627622>, assertion=0x7f6080918903 ""first"", file=0x7f60809187c4 ""../src/evdev-mt-touchpad.c"", line=1541, function=<optimized out>) at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f6080918903 ""first"", file=file@entry=0x7f60809187c4 ""../src/evdev-mt-touchpad.c"", line=line@entry=1541, function=function@entry=0x7f60809191a0 <__PRETTY_FUNCTION__.12316> ""tp_detect_thumb_while_moving"") at assert.c:101
 tp_detect_thumb_while_moving (tp=<optimized out>) at ../src/evdev-mt-touchpad.c:1541
 tp_process_state (time=1461748714, tp=0x561162eb6e10) at ../src/evdev-mt-touchpad.c:1792
 tp_handle_state (tp=0x561162eb6e10, time=time@entry=1461748714) at ../src/evdev-mt-touchpad.c:1876"
1792573,2018-09-17 08:46:16 UTC,Can you please report the crash to the libinput developers here?
1792573,2018-09-23 10:48:57 UTC,"Daniel, sure, but which one stacktrace I should upload to libinput developers? Should I link back to this bugreport? If yes, then how to make this bugreport public?"
1792573,2018-10-02 08:11:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792573,2018-10-26 07:09:33 UTC,Bug reported upstream: https://gitlab.freedesktop.org/libinput/libinput/issues/170
1792573,2019-07-22 03:53:24 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1792574,2018-09-17 04:59:46 UTC,I think the serial is the same as LP: #1785780.
1792574,2018-09-19 21:09:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792574,2018-11-14 13:51:29 UTC,Looks like this bug was fixed with kernel version 4.15.0-36.39.
1792578,2018-09-14 13:09:56 UTC,"StacktraceTop:
 pcache1PinPage (pPage=0x55d2e33a9048) at sqlite3.c:48209
 pcache1FetchNoMutex (createFlag=<optimized out>, iKey=1504, p=0x55d2e32bacc8) at sqlite3.c:48637
 pcache1Fetch (p=0x55d2e32bacc8, iKey=1504, createFlag=<optimized out>) at sqlite3.c:48685
 sqlite3PcacheFetch (pCache=<optimized out>, pCache=<optimized out>, createFlag=3, pgno=1504) at sqlite3.c:47150
 getPageNormal (pPager=0x55d2e338c908, pgno=1504, ppPage=0x7ff7a27fb8e0, flags=2) at sqlite3.c:55008"
1792579,2019-07-23 10:26:22 UTC,Please provide us with logs of Network Manager in debug mode. See
1792579,2019-09-22 04:17:28 UTC,[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]
1792583,2018-11-09 08:04:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792583,2019-09-07 17:32:42 UTC,This bug was fixed in the package man-db - 2.8.7-3
1792594,2018-09-14 14:58:31 UTC,"To work around this give tecoc the following command at any time
before saving. This works also on files that have previously been
saved with different end-of-line  character sequences."
1792595,2018-09-14 19:32:21 UTC,yep thats a problem if they are expecting that to work. That being said people are using it this way so we are going to have to request a CVE.
1792595,2018-09-18 08:18:56 UTC,After investigating this issue further we have determined this is a high priority issue that is also trivial to exploit with the change_profile api
1792595,2018-09-19 06:55:36 UTC,"After discussing with ubuntu, suse, and debian representatives we are going to make this bug public. The threat model that they are currently most concerned with is the behavior of the confined application, it is expected that the unconfined user could do things to bypass some apparmor security, as long as it doesn't elevate the users privileges beyond what a linux system using capabilities and dac would allow."
1792596,2018-09-14 15:06:28 UTC,"First, get tecoc of the hanger with"
1792596,2018-09-14 15:07:36 UTC,"Second, avoid and work around this, for now."
1792596,2018-09-14 15:09:08 UTC,"Of course, your configuration files might work. Tell, please."
1792599,2018-09-14 15:21:00 UTC,"In this image, I'm hovering my mouse over the sound applet no volume level indicator is popping out, unlike in Lubuntu 16.04."
1792600,2018-09-20 14:12:42 UTC,"right, now using that and checking in an autopkg test, so migration of kernels with a changed build system will block."
1792600,2018-09-17 08:57:27 UTC,It looks like building the binary-arch-headers target should limit the build to the linux-libc-dev package.
1792600,2018-09-16 10:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1792600,2018-09-14 16:39:30 UTC,"the ""native"" build fails like:"
1792600,2018-09-16 09:55:48 UTC,The better solution for this would be a build profile in the linux source that just builds the linux-libc-dev package.  That way the cross-toolchain-base packaging would be independent from the linux build system.
1792600,2018-09-14 16:38:28 UTC,"that's how the ""cross"" build fails:"
1792604,2018-09-14 15:36:49 UTC,"This would need to happen on new installs of yaru-theme-gtk only, not updates."
1792604,2018-09-14 15:53:40 UTC,"lxd has some logic in the deb package to install the snap in its preinst script (sort of the opposite of what we're trying to achieve here), this can be interesting: https://github.com/lxc/lxd-pkg-ubuntu/blob/dpm-cosmic/debian/lxd.preinst"
1792604,2018-09-14 16:12:02 UTC,The following should do the trick (will require thorough testing):
1792604,2018-09-17 09:15:26 UTC,"Tested this in a PPA, and it works as expected. One minor issue is that when uninstalling the communitheme snap while the theme is in use, icons in the dock change on the fly, and that doesn't look great. That would happen only during upgrade from bionic and to users actually using the communitheme session, so that's probably acceptable, but we can reduce the impact further by having the snap removed in the dist-upgrader code at the very end of the upgrade process (when unused debs are being removed)."
1792604,2018-09-24 07:36:37 UTC,"As we discussed, I'm working on the immediate issue: moving to a separate binary package.
This is done on https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1794024"
1792605,2018-09-14 19:39:07 UTC,"You mean it breaks the existing OpenStack services/container?  I have the whole bunch of instances are running there, some of them are considered as production instances."
1792605,2020-07-10 14:26:05 UTC,Summary: using different passwords will not work with an existing cluster. It applies to most password-protected resources.
1792605,2018-09-14 16:43:09 UTC,"Yes, will deploy new computes with different passwords,you can find what passwords are used on the config files for each service in the hosts at /etc/kolla/(service_name)"
1792615,2018-09-28 08:24:57 UTC,"Reviewed:  https://review.openstack.org/602526
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=050f8799ca82f121f9d33c7e773b982b9763f074
Submitter: Zuul
Branch:    master"
1792621,2019-01-14 16:41:23 UTC,Adding 3.1.x target since bug 1712854 is to be backported.
1792621,2018-11-19 02:50:02 UTC,"Pushed to master and backported to rel_3_2.  It did not backport cleanly to rel_3_1, not sure if this is something that can be easily pushed back (or is even necessary?)"
1792621,2018-09-20 15:01:46 UTC,I've pushed a second commit to the above branch that addresses a think-o in the hold shelf delay YAOUS test.
1792621,2018-09-17 14:22:47 UTC,I have a branch here that fixes this issue.  It also addresses an adjacent hold status calculation issue.
1792621,2018-09-14 18:05:28 UTC,I should add that this is in the web client. eg/staff/circ/holds/shelf
1792621,2018-11-05 21:12:30 UTC,Signoff pushed to :
1792624,2019-09-16 14:27:05 UTC,Migrated to https://github.com/widelands/widelands/issues/1712
1792624,2018-09-30 13:12:16 UTC,There should be a discussion on what convention to follow. Maybe list some candidate schemes and comment on them.
1792629,2018-09-17 12:50:25 UTC,"Hello all,"
1792629,2018-09-17 12:54:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792629,2018-09-17 16:23:29 UTC,"Hi,"
1792629,2018-09-17 16:53:18 UTC,The best place seems to be the Orca mailing list. I've sent a message about your issue on it: https://mail.gnome.org/archives/orca-list/2018-September/msg00105.html
1792629,2018-10-04 08:04:40 UTC,This issue has been fixed in the development branch of Orca that will be available on Ubuntu 18.10 or 19.04.
1792642,2018-09-19 12:38:28 UTC,"Thanks for the report Henning.
Would you mind testing libreoffice 1:6.0.6-0ubuntu0.18.04.1 from bionic-proposed (see https://wiki.ubuntu.com/Testing/EnableProposed)? Please comment here to let me know whether the issue is still there."
1792643,2018-09-19 14:47:42 UTC,Tried examining bug locally and getting symbols with apport:
1792643,2018-09-19 14:35:57 UTC,From /var/log/apport.log
1792643,2019-07-18 16:47:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792643,2019-07-18 17:11:24 UTC,"This issue seems to have occurred to me today (and several times previously) - when I returned to my computer after a while (the screen had entered power saving mode), the gnome-shell process (on XWayland) failed."
1792649,2018-09-27 18:41:24 UTC,Thanks for the bug report. You're correct in that we don't currently list RHEL in the known series as we don't have images that we can test/rely on as being suitable for the expectations of Juju and the charms that are used. We don't list out things that we're not sure will function.
1792652,2018-09-15 04:17:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1792659,2020-11-12 18:26:24 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1792659,2020-11-12 20:44:39 UTC,I can follow the logic here and agree there's a bug.
1792662,2019-07-17 14:52:15 UTC,See https://github.com/libhangul/ibus-hangul/issues/70
1792663,2018-12-18 09:49:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792663,2018-12-18 11:06:10 UTC,"I have fixed this bug, please review:
https://review.openstack.org/#/c/602283/"
1792668,2020-07-08 04:17:32 UTC,[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.]
1792668,2020-05-09 02:14:25 UTC,"I have avoided using the calendar application as it has been too buggy to be usable, I will need to see if this issue still occurs."
1792668,2020-05-05 15:44:09 UTC,Thank you for your bug report. Do you still have those issues? Could you report them to the software writter directly on https://gitlab.gnome.org/GNOME/gnome-calendar/issues ?
1792668,2019-03-02 12:14:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792668,2019-11-25 23:42:57 UTC,"18.04, for me, the native Calendar app synced in Online Accounts > Nextcloud after syncing it does not removed deleted events that were part of a recurring series."
1792668,2018-09-17 04:27:46 UTC,"I am renaming all ""evolution"" folders in ~.config ~.cache and ~.local/share to see if that fixes the behavior."
1792668,2018-09-17 04:23:11 UTC,Experiencing similar issues/behavior in other gnome office apps: contacts and todo list.
1792668,2018-09-15 06:03:31 UTC,"1. Renamed ""calendar"" folder under ~/.cache/evolution, and also the ~/.config/evolution and .local/share/evolution folders
2. rebooted. Then I
3. de-activated and re-activated ""calendar"" under each separate online account.
4. then I restarted Calendar app."
1792668,2018-09-19 06:00:30 UTC,Renaming folders does not appear to resolve the issues. See bug 1793256 for potentially-related information.
1792672,2018-09-15 06:30:06 UTC,This change was made by a bot.
1792672,2018-09-15 14:12:04 UTC,"Gioele Barabucci, thank you for reporting this and helping make Ubuntu better."
1792672,2018-11-15 04:17:36 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1792672,2018-11-15 06:43:21 UTC,The problem is still present in the kernel version 4.15.0-38-generic.
1792672,2018-11-15 07:00:07 UTC,This change was made by a bot.
1792672,2018-11-15 08:38:53 UTC,Please try latest mainline kernel which may already fix the regression.
1792672,2019-05-08 15:00:11 UTC,This change was made by a bot.
1792672,2019-05-09 02:09:29 UTC,"Gioele Barabucci, instructions for testing the latest mainline kernel are available via https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792672/comments/18 ."
1792672,2019-07-08 04:17:33 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1792672,2020-01-15 18:51:49 UTC,This problem is still present in the kernel version 4.15.0-72-generic (current HWE kernel for 16.04 LTS).
1792672,2020-01-17 06:25:09 UTC,Would it be possible for you to do a kernel bisection?
1792672,2020-12-17 04:17:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1792672,2018-09-15 06:10:36 UTC,apport information
1792672,2019-05-08 14:36:34 UTC,This problem is still present in the kernel version 4.15.0-48-generic (current HWE kernel for 16.04 LTS).
1792672,2018-09-15 06:10:34 UTC,apport information
1792672,2019-02-22 04:18:29 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1792672,2018-09-15 06:10:31 UTC,apport information
1792672,2018-09-15 06:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1792672,2018-09-15 06:10:19 UTC,apport information
1792672,2018-09-15 06:10:20 UTC,apport information
1792672,2018-09-15 06:10:21 UTC,apport information
1792672,2018-09-15 06:10:22 UTC,apport information
1792672,2018-09-15 06:10:18 UTC,apport information
1792672,2018-09-15 06:10:32 UTC,apport information
1792672,2018-09-15 06:10:24 UTC,apport information
1792672,2018-09-15 06:10:26 UTC,apport information
1792672,2018-09-15 06:10:27 UTC,apport information
1792672,2018-09-15 06:10:29 UTC,apport information
1792672,2018-09-15 06:10:30 UTC,apport information
1792672,2018-09-15 06:10:23 UTC,apport information
1792679,2018-10-09 13:26:55 UTC,"I also noticed, that the isue is hard to observe on lightdm, but reproduces easily when using gdm."
1792679,2018-09-15 08:49:41 UTC,It happens with mainline kernl builds and stock ubuntu kernels regrdless of stable branches that those kernels come from.
1792683,2019-01-30 13:37:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792684,2020-10-22 22:07:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792684,2020-10-22 22:19:08 UTC,"I have to reboot tu make the error 10 dissapear (i hope), refresh the partition table, and make a fresh install"
1792687,2018-09-16 13:43:06 UTC,"> Thanks launchpad for being a bug-reporting service that doesn't even support code markup... How does this still exist?
"
1792687,2018-09-17 19:15:33 UTC,"Maybe a spinner or something? Anything that indicates that mixxx is actually shutting down and not just stuck.
@Be what do you mean with audio interface? I use whatever comes with KDE Plasma and have devices on Kubuntu 18.04 and KDE Neon, with similar experience."
1792687,2018-09-17 08:10:35 UTC,"...I suppose a progress bar wouldn't help here, because it would just get stuck at this point without displaying any helpful feedback."
1792687,2018-09-17 08:08:59 UTC,I would consider this issue a duplicate of https://bugs.launchpad.net/mixxx/+bug/1778310
1792687,2018-09-17 19:52:26 UTC,"Your audio interface is the hardware that gets audio signals in/out of your computer. The older term is ""sound card"", but few of them look like cards nowadays."
1792687,2018-09-18 19:18:13 UTC,"Ah okay. Well, it happens on all of my devices, so I'm not sure about the root of the issue.
I ran lspci -v | grep -i audio on my pc and got this:"
1792687,2018-09-16 13:38:23 UTC,"> However, when I run mixxx plainly from the commandline, it shuts down in under one second. So the delay seems to be related to the suspension of pulseaudio.
"
1792687,2018-09-16 12:35:41 UTC,Thanks launchpad for being a bug-reporting service that doesn't even support code markup... How does this still exist?
1792687,2018-09-16 12:32:10 UTC,"Aha, I found the root of the issue: The mixxx.desktop file uses the following command: `sh -c ""pasuspender -- mixxx || mixxx""`"
1792687,2018-09-15 23:08:55 UTC,"Mixxx should not take so much time to shut down. You can watch the console output when running with the ""--logLevel debug"" command line argument to see what is taking so long. Are you using any of the 64 sampler skins?"
1792687,2018-09-16 12:36:35 UTC,"By the way, I use Deere."
1792688,2018-09-15 23:06:32 UTC,I presume this is using ALSA? I think the problem is with ALSA or PortAudio.
1792688,2018-09-16 12:38:01 UTC,"I use KDE Plasma as my desktop everywhere, and as far as I know it uses ALSA, yes."
1792688,2018-12-16 16:34:29 UTC,"I now start mixxx without ""pasuspend"", and it starts up and shuts down a LOT faster and is quicker when interacting with audio devices."
1792690,2018-09-15 10:53:10 UTC,"This seems pretty easy, and I would actually start working on it myself. I will try to find the relevant files, but a pointer to where to start would be helpful :)"
1792690,2018-09-15 15:59:34 UTC,https://github.com/mixxxdj/mixxx/pull/1342
1792691,2018-09-17 10:05:18 UTC,In general you should not start a batch analysis while performing live. Running batch analysis tasks is supposed to be done offline. I remember that Serato entirely disabled batch analysis while a controller was connected.
1792693,2018-09-25 22:33:40 UTC,Mixxx has no concept of multiple formats/files per track. It would be difficult to extend the current design. And before adding new features the scalability issues between the database backend and the frontend should to be solved.
1792698,2018-09-16 07:55:23 UTC,If it crashes you should have core dump. Please provide a back trace with all debugging symbols installed. See https://wiki.ubuntu.com/DebuggingProgramCrash for details.
1792698,2018-09-16 10:22:19 UTC,There is no apport response and something in /var/crash for vlc. But i can provide a deeper report from vlc itself.
1792698,2018-09-16 10:25:38 UTC,"Sorry for malformed file, here it is again."
1792698,2018-09-18 07:25:22 UTC,"The log looks like vlc exiting normally, so I don't see a crash here. Do you have ""Quit at the end of the playlist"" enabled?"
1792698,2018-09-18 17:54:54 UTC,"Checking, YES this option was switched on. Switching it off restores the normal behaviour."
1792704,2018-10-03 08:00:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792710,2020-11-20 14:37:00 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/763570"
1792710,2020-11-20 14:29:55 UTC,"Reviewed:  https://review.opendev.org/762498
Committed: https://opendev.org/openstack/glance_store/commit/ca0c58b52756058b6d51bf6a47aeac3d525c1e16
Submitter: Zuul
Branch:    stable/ussuri"
1792710,2020-11-12 10:53:18 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/762498"
1792710,2020-08-21 09:08:49 UTC,"Reviewed:  https://review.opendev.org/746579
Committed: https://git.openstack.org/cgit/openstack/glance_store/commit/?id=c43f19e8456b9e20f03709773fb2ffdb94807a0a
Submitter: Zuul
Branch:    master"
1792710,2020-08-17 18:01:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/746579"
1792710,2019-05-05 02:46:42 UTC,"Thanks Jokke. I know ceph support shrink, but not sure if other storage backend support shrink or not. It's a good idea, but may need to check if backends support shrink when doing resize. if not support shrink, then may need to keep current way - resize in a small step."
1792710,2019-05-02 16:52:30 UTC,PTG May 2nd Cinder/Glance session:
1792710,2018-10-12 10:17:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/609997"
1792710,2018-10-12 10:10:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/609994"
1792710,2018-09-17 06:58:54 UTC,"@Sean, more information provided in ""Bug Description"", thanks"
1792710,2018-09-16 15:56:55 UTC,Glance and glanceclient take an optional size as input. What is the bug there? This needs better detail.
1792710,2018-09-15 15:53:49 UTC,cinder need to get the image size and send the size to glance at the beginning of the uploading. I will point the review to this bug soon.
1792710,2018-09-15 15:32:11 UTC,What is the Cinder issue here?
1792711,2018-09-17 14:57:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792724,2019-04-15 13:01:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792731,2018-10-13 01:17:45 UTC,We also experience the same i/o error but with Python version 3.6.6 final 0
1792732,2018-09-16 16:35:11 UTC,"Thinking about this a bit more, I guess a simple way to do that would be to just issue the following SQL:"
1792732,2018-09-17 19:15:36 UTC,"Hello Jane, here are my scripts/notes on purging authority records."
1792734,2020-07-03 04:23:03 UTC,libjpeg8:amd64 (8d1-2)
1792735,2019-08-26 15:32:54 UTC,"Could you please add the -f option to the strace command you used and post the resulting trace?  (Assuming it's still happening, since I've fixed various things since then.)"
1792735,2019-10-26 04:17:27 UTC,[Expired for man-db (Ubuntu) because there has been no activity for 60 days.]
1792736,2020-04-25 13:40:13 UTC,tor seems to be happy in focal
1792737,2018-09-15 19:43:03 UTC,I use Debian 9.5
1792737,2018-09-15 19:15:25 UTC,"Help-me please with solution, I build a distro named Aioulinux in sourceforge and for build it, I use Systemback."
1792739,2019-09-10 23:35:37 UTC,"Fixed, see also https://gitlab.com/inkscape/lib2geom/issues/16"
1792741,2019-05-22 20:02:46 UTC,I get this:
1792747,2018-09-18 23:26:14 UTC,"Bugs that will become obsolete if we fix this ;)
Bug #1196833
Bug #1736971
Bug #1774639"
1792747,2018-09-18 23:26:26 UTC,https://github.com/mixxxdj/mixxx/pull/1808
1792747,2018-09-20 02:56:32 UTC,https://github.com/mixxxdj/mixxx/pull/1814
1792749,2019-04-20 17:42:09 UTC,"I make the widget consistent, which mean Other is visible when it should be and hidden instead of disabled when it should not."
1792749,2018-11-30 09:06:17 UTC,Nice idea. Very Useful. Thumps Up
1792749,2018-11-30 09:11:47 UTC,Nice idea. Thumps up
1792749,2018-09-16 11:58:32 UTC,"Looking at the Balance report ""Other"" is also disabled but it appears as a selection when the date range is selected. In the drop down it is still disabled."
1792749,2018-09-28 20:42:12 UTC,This widget is especially only devoted to select a dare range.
1792752,2018-09-17 06:16:09 UTC,The error in your log shows:
1792752,2018-09-24 06:25:48 UTC,Thanks. it worked.
1792752,2018-09-27 03:35:51 UTC,Thanks. It worked.
1792760,2019-07-29 22:23:03 UTC,eog
1792762,2020-03-07 11:36:38 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1792770,2018-09-16 07:10:22 UTC,"yep i just literally installed it and did bit of updateing /upgrading
hopefully it wont pop again thanks for your prompt timing"
1792771,2019-10-13 09:51:53 UTC,"The last update in bionic (0.6.2-2ubuntu0.18.04.1) also included that change, so I'm marking this bug as fixed."
1792771,2018-09-16 08:19:44 UTC,"The attachment ""Upstream fix"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1792774,2018-09-24 08:03:45 UTC,+1 for #3
1792774,2019-04-25 08:12:15 UTC,"Unless I´m confusing stuff here, this was assigned to that branch by mistake and the issue is still unsolved"
1792774,2018-09-18 20:07:02 UTC,"The bug report is actually about the priority buttons, not about the new branch with the amount buttons. But it affects the new branch as well.
I decided to use Ctrl back when the ""set all priorities"" feature was implemented since it is kind like a ""strong"" order to set the priority, similar to the function of, e.g., the ""Dismantle"" button."
1792774,2019-09-16 08:37:22 UTC,Migrated to https://github.com/widelands/widelands/issues/3320
1792774,2018-09-16 13:10:46 UTC,As the branch for CTRL-CLicking the ware priority buttons I won't consider this a bug more a development review comment to be fixed for the relevant branch. so at least we should link this to the new branch
1792774,2018-09-17 09:05:59 UTC,"Why not use another key like ""Shift"" that is not used currently?"
1792779,2018-09-16 09:10:14 UTC,"I have added 8.8.8.8 to /etc/resolvconf/resolv.conf.d/tail as I read in some suggested workaround, that is why it's present /etc/resolve.conf I think."
1792783,2021-02-23 17:07:47 UTC,"Triaged to medium; there should be a fix for the openstack-dashboard charm to setup horizon to do this, but it can be done from the CLI as a workaround."
1792783,2020-12-18 21:44:37 UTC,"Perhaps I am dense, but this problem seems to affect me as well.  I am using a brand-spanking new openstack-dashboard install out of JAAS.ai, and I cannot add roles using the admin user account provisioned during ""juju deploy""."
1792783,2020-09-08 14:14:27 UTC,"On the other hand, charm-openstack-dashboard does not correctly setup REST_API_REQUIRED_SETTINGS for the change at Rocky: https://opendev.org/openstack/charm-openstack-dashboard/src/branch/master/templates/ocata/local_settings.py#L893"
1792783,2018-12-23 17:23:16 UTC,Has OPENSTACK_KEYSTONE_BACKEND been added to REST_API_REQUIRED_SETTINGS?
1792783,2018-12-21 21:38:20 UTC,"I did a little more digging and I'm still not sure what the problem is. I can create/delete users, groups, projects, domains, but not roles as there are no buttons."
1792783,2020-09-08 14:13:27 UTC,"The Ubuntu package installs the local_settings.py from ""openstack_dashboard/local/local_settings.py.example"" so I think that, as Albert noted, the package is doing the right thing."
1792783,2018-11-25 22:32:24 UTC,I cannot reproduce this either.
1792783,2018-10-10 15:04:08 UTC,"Corey, could you please confirm that it's reproducible on upstream horizon?"
1792783,2018-09-16 09:40:44 UTC,Rocky screenshot
1792783,2018-09-16 09:40:16 UTC,Queens screenshot
1792783,2018-12-18 16:21:31 UTC,This is possibly explained by the following comments from LP:1775227:
1792789,2018-10-11 09:17:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792793,2018-09-16 16:47:11 UTC,Please only one request per bug report. Otherwise it's difficult to handle them.
1792793,2018-09-17 11:33:24 UTC,"thank you very much,Mr AlexB
1) Internal Error encountered ,Maybe my code is wrong,Let me check again
2）Hope the update will come soon
3）Good luck"
1792797,2019-05-01 14:45:11 UTC,https://github.com/mixxxdj/mixxx/pull/2095
1792798,2018-09-17 10:09:10 UTC,screenshot of how it looks like right after powering it on from suspend/sleep mode. (tty2)
1792798,2018-09-18 19:40:18 UTC,https://askubuntu.com/questions/896971/problem-with-display-after-suspending
1792802,2018-09-16 16:49:31 UTC,IT IS A BUG...
1792802,2018-09-16 16:58:40 UTC,"Thank you Gunnar.. but the rotation occurred while I was watching a
video streaming program.  I had not touched the keyboard.  Then
following the instructions to change the rotation, the actual screen
allowing me to do so would not open... never did after 5 or more tries.
It just looped back to instructions."
1792802,2018-09-16 17:08:27 UTC,"Ok, if you say so. But it's still not a desktop guide bug."
1792802,2018-09-16 15:58:41 UTC,"You have filed a bug against the desktop documentation, but what you write has nothing to do with that. Apparently you are seeking support, so I recommend you to try at e.g. <https://askubuntu.com>."
1792802,2018-09-16 15:29:25 UTC,"I note importance undecided... well it is extremely important to me.. this is a computer used for business.  It backs up my other laptop which is running windows 10.. which I also detest.  I love Linux/Ubuntu except for these hazards.  I should never be an early adopter.
L R Bellmore Jr"
1792802,2018-09-16 15:35:09 UTC,Rebooted a 3rd time and it restored to normal orientation.  I am leaving this page open to see how long it takes before it rotates again.. I had rebooted twice before and it maintained the clockwise rotation.  I am going to go back to the same website I was on before .. it is a video streaming of a live program.  It took about an hour before it rotated.  So I saw most of the live program before the screen rotated.
1792802,2018-09-16 15:30:22 UTC,"OH, and the cursor doesn't like the rotation either.. very difficult to control it."
1792802,2018-09-16 15:49:23 UTC,I am communicating from my W10 HP i7 laptop which is my main laptop because we have one software program that must and only runs on Windows.  It is critical to our licensing/business.  The HP g7 laptop is a backup running Ubuntu.  I would prefer to have all my office computer systems on Ubuntu but I have one program that will only run on Windows.  I have not tried it in a virtual machine yet.  That is next step for trying to transition to Ubuntu completely.  I have 3 desktops and 1 laptop running W10 and this laptop on W10 because of the one software program that I need for business production.  I can't run it on the Ubuntu laptop. There are major suppliers who run the specific software on virtual machines but you must be a high volume user of the software to afford their virtual systems running this sofware... so I am stuck with Windows.
1792806,2018-09-17 18:02:46 UTC,"Hi,
Maybe you can share an example file by using a service like dropbox. Then, we can test with it and help find a solution."
1792806,2018-09-18 20:10:36 UTC,"Hi,
Thank you for your quick feedback. You think I should provide an Inkscape (*svg) file with these problems?"
1792806,2020-03-29 17:14:52 UTC,Closing because INVALID: issue resolved.
1792811,2018-09-17 13:33:24 UTC,I can't run gdb with that crash (it can't be loaded)
1792811,2018-09-19 08:43:32 UTC,"After opening with apport the crash dump, I can see a crash in the above mentioned
Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987"
1792811,2018-09-16 18:20:59 UTC,"please run
apport-collect 1792811"
1792812,2018-10-09 14:47:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792817,2018-09-23 17:46:20 UTC,"I installed pluma on a different machine (clean install) and it runs very fast. However, if I ssh -X to that machine and run pluma, I get the lag (other apps are fine, so it's not the connection)."
1792817,2018-09-17 15:30:30 UTC,"The problem does not seem to happen in gedit, it's quite fast, although I greatly dislike that editor in general. MATE first captured my interest because they had retained the gtk2 version of gedit, which was renamed to pluma. At the time gedit had already started changing the UI and I had been keeping pinned versions of the old gedit package, which was no longer necessary with MATE."
1792817,2018-09-16 20:31:43 UTC,"Have you tried any other app that uses GtkSourceView like Gedit, Meld or Mousepad?"
1792817,2018-09-16 22:28:14 UTC,"Might have found it! Ran pluma on Ubuntu MATE live (18.04) and it didn't have the problem. So, I straced pluma to see what files were being loaded from my home directory and started methodically renaming things one at a time. Renaming ~/.fonts.conf seems to have done the trick for me. The contents of that file were:"
1792817,2018-09-16 22:34:47 UTC,Never mind.. I guess it was just being nice for a minute there. Lag remains :(
1792817,2018-09-16 22:45:46 UTC,"I do not use Gedit, Meld, or Mousepad."
1792817,2018-09-17 01:29:43 UTC,"If you install one or more of them, you can see if the issue is with Pluma or the GtkSourceView library they all use."
1792817,2018-09-17 10:58:33 UTC,"I don,t have this problem. I have a question : your 18.04 is a fresh install or a update from 16.04?"
1792817,2018-09-18 12:33:58 UTC,what if you delete and then reinstall Pluma? You have some old configs store in the .home dir that it's doing this.
1792818,2019-07-17 13:29:23 UTC,Can you add the attachment or reproduce this with latest version of stretch -> buster?
1792827,2018-10-19 21:03:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792835,2018-09-18 10:21:03 UTC,Fix committed in git.
1792835,2018-09-18 18:37:50 UTC,"jackd, ufw, cowbuilder, dpatch_edit_patch, and axi-cache should maybe also be fixed."
1792835,2018-09-20 12:46:20 UTC,"Fix committed in git:
https://salsa.debian.org/pbuilder-team/cowdancer/commit/bbac66ca568e00ff6f54e0b38d77556f44b7b03d"
1792835,2018-10-09 10:49:15 UTC,This bug was fixed in the package inkscape - 0.92.3-4
1792835,2018-12-14 15:33:32 UTC,The ufw bug is being tracking in bug 1775043. Removing that task.
1792835,2019-01-08 00:45:39 UTC,This bug was fixed in the package cowdancer - 0.88
1792841,2020-01-29 10:20:55 UTC,The requested functionality is not a charmed way of connecting nagios and nrpe units.
1792841,2020-01-29 20:40:38 UTC,What do you mean? Any charms using charmhelper.contrib.charmsupport.nrpe drops files in /var/lib/nagios/export for a nagios host to collect.
1792841,2020-05-10 21:42:46 UTC,"The functionality referred to here is the 'other' way of getting NRPE checks to Nagios, via rsync rather than relation.  Although it's an older method, there are use cases still for it, and we need to continue to support it."
1792843,2018-12-29 21:13:45 UTC,"I have almost the same issue.
Using gdm3, when I lock my session (e.g. with <super>+<L>) the lock screen doesn't accept keyboard and mouse events at all."
1792843,2018-12-29 21:06:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792843,2018-11-01 17:52:02 UTC,I can work around by using ctrl-alt-f1 to change to the user switcher and re-authenticatie into the session that way.
1792843,2018-11-01 17:51:36 UTC,This also happens to me on bionic on a dell xps 9370 (intel video)
1792843,2018-09-17 15:25:57 UTC,Note: for now I have worked around this by preventing my console from being locked when the display sleep kicks in. Not ideal but at least I don't have to reboot after every sleep.
1792843,2018-09-17 15:22:51 UTC,apport information
1792843,2018-09-17 15:22:50 UTC,apport information
1792843,2018-09-17 07:44:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1792843"
1792843,2018-09-17 15:22:52 UTC,apport information
1792856,2018-09-19 08:08:37 UTC,This might be a quick fix:
1792856,2020-03-10 06:53:58 UTC,Juju 1 series is no longer supported / in use
1792859,2018-12-02 21:13:08 UTC,"Change abandoned by Ian Y. Choi (<email address hidden>) on branch: master
Review: https://review.openstack.org/603032
Reason: Setting this as abandoned since there is no response from the author - please change the status if someone wants to make changes from this patch"
1792859,2018-09-17 07:17:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/603032"
1792860,2018-09-17 19:39:33 UTC,There is 02proxy
1792860,2019-08-01 15:09:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792860,2019-08-01 15:15:34 UTC,Ubuntu now uses https to connect to changelogs.ubuntu.com (LP: #1744318)
1792860,2020-05-03 09:23:42 UTC,It seems to have been fixed in Ubuntu 20.04:
1792866,2020-02-13 11:42:01 UTC,"Is this still reproducible?
I checked the code and I don't see anything which could cause such an issue. The test list extensions available and then iterates over them while it takes the alias of the extension, requests details through that alias and checks if the name in the details is the same as was listed at the beginning of the test.
Let us know, if you still experience the issue. I'm gonna mark this as incomplete as I'm gonna need more info to debug it further."
1792866,2020-04-14 04:17:33 UTC,[Expired for tempest because there has been no activity for 60 days.]
1792866,2018-09-17 06:53:25 UTC,"took a look into the code. The problem is *not* the order of ext, its the ""name""-field of the tag-ext extension."
1792875,2020-03-02 14:51:45 UTC,This issue was fixed in the openstack/mistral 10.0.0.0b2 development milestone.
1792875,2019-12-19 08:08:29 UTC,"Reviewed:  https://review.opendev.org/695212
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=6948e50de80559f78988ff34d92969aab61bf012
Submitter: Zuul
Branch:    master"
1792875,2019-11-20 09:16:04 UTC,workflow_execution_id is of type UUID (ie. 6c07a453-c5e1-4bbe-97ed-3cb77b4f55ff) but the given value to the API is eq:6c07a453-c5e1-4bbe-97ed-3cb77b4f55ff.
1792875,2019-09-17 08:00:20 UTC,"Ali, please verify and investigate, if needed."
1792877,2020-11-23 05:16:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1792880,2019-02-13 00:25:24 UTC,subscribed ~field-medium
1792880,2018-10-04 15:28:48 UTC,"Hi ByungYeol,"
1792880,2018-10-04 15:33:41 UTC,"Hi ByungYeol,"
1792880,2020-05-29 21:05:44 UTC,"FYI Circling back to this, it looks like the upstream issues are still pending:"
1792883,2018-10-23 14:38:55 UTC,"Please run 'sudo grub-install -v"" from the live image; we should have a look at the full debug output to see why md126,1 isn't found."
1792883,2019-04-02 00:37:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792891,2018-09-17 11:49:23 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-September/095498.html
1792896,2020-05-03 04:17:35 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1792896,2020-03-03 13:34:58 UTC,"very old, letting expire unless someone has any current news"
1792896,2018-10-02 03:54:06 UTC,Has anyone else run into this issue?
1792896,2018-10-22 12:10:19 UTC,Seems to same as 'https://bugs.launchpad.net/neutron/+bug/1788978'
1792901,2018-10-08 03:24:36 UTC,Agree with ”allow to delete a prefix if it is not consumed“. That is just what I want.
1792901,2019-02-08 18:05:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/635907"
1792901,2019-02-08 17:34:20 UTC,"I would suggest taking a look at the implementation of subnet onboard as an example of what the API should look like. In fact, I would like to see prefix additions handled with a similar API. What exists today is not very friendly, it processes updates to the prefix list on simple PUT to the subnetpools resource. It's very difficult to parse intent from that (ie should we remove or add a prefix?). I would like to see an add_prefix and remove_prefix in the ACTION_MAP similar to how we have onboard_network_subnets for subnet onboard."
1792901,2019-02-27 23:40:33 UTC,"Reviewed:  https://review.openstack.org/635907
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=a6438f427916b01957ff09bc11e959f1ae23ab50
Submitter: Zuul
Branch:    master"
1792901,2019-07-24 13:16:23 UTC,"Reviewed:  https://review.opendev.org/662253
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=b7238bd91b6ca17b612b0fe05e12c4fff05b3d33
Submitter: Zuul
Branch:    master"
1792901,2019-05-30 15:55:13 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/662253"
1792901,2019-07-05 01:17:19 UTC,"Reviewed:  https://review.opendev.org/648197
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7eb74d2c4aa9bf1db0f165bee64fdf856fc94a2a
Submitter: Zuul
Branch:    master"
1792901,2018-10-05 15:11:33 UTC,Drivers team discussed and approved feature 2 as described in note #11 in this RFE on October 5th
1792901,2019-03-27 17:50:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/648197"
1792901,2018-10-04 23:22:55 UTC,Let's discuss with the drivers team
1792901,2018-09-28 13:59:14 UTC,"@Wenran Xiaao,"
1792901,2018-09-28 01:59:32 UTC,@Miguel Lavalle
1792901,2018-10-04 23:22:40 UTC,"@Ryan,"
1792901,2018-09-17 11:32:41 UTC,"Indeed subnet pools do not support deleting prefixes, the only possible operation is to update them (and only if existing prefixes are a subset of the new prefixes)"
1792901,2018-09-18 01:51:46 UTC,"The actual situation is as you described， but If I create a wrong prefixes by mistake, what should I do?
Why does subnet pool not support deleting prefiexs？ Is this some reasons?"
1792901,2018-09-27 02:36:48 UTC,Fix proposed:
1792901,2018-09-28 16:31:46 UTC,"This is actually all working as designed, which is the unfortunate part of this! I think pursuing an RFE is worthwhile, and I would be happy to help with the effort. There are some things we can clean up here. It sounds like there are 2 discrete use cases here, both of which can be pursued independently:"
1792901,2018-09-27 16:25:28 UTC,Thanks Ryan for your comment. Here's the patchset that implemented the functionality: https://review.openstack.org/#/c/148698
1792901,2018-09-27 16:29:58 UTC,"Based on comment #4 above, this is not a bug. This is how the functionality was implemented. I'll tag it as a RFE and, if the submitter decides so, we can continue processing this in the RFE process"
1792901,2018-09-28 00:43:51 UTC,"@Wenran Xiaao,"
1792901,2018-09-27 16:12:38 UTC,"This was a while ago, so my memory is a little fuzzy. I recall there being a bit of contention about the semantics of a PUT on the API to update the prefix list, specifically around how to express removal of a prefix without forcing all PUT's to send the entire list of prefixes. This was not implemented well from the start. In retrospect I would implement a specific subresource (add_prefix or something of the sort) to operate against for prefix updates. Maybe adding this resource and a collorary remove_prefix resource to the API extension would have the benefit of both enabling prefix removal AND a more explicit API. It may be infeasible, but that would leave open the possibility of deprecating PUT support on the prefix_list, making it a read-only attribute. Thoughts?"
1792903,2018-09-17 10:22:53 UTC,this sounds like a kernel bug - or do you think there is something for autopkgtest / autopkgtest-cloud to do?
1792903,2018-09-21 11:49:53 UTC,The kernel itself is fine on retry or when the cloud is quiet. Thus it requires logs from the nova to check that the host/vm was stable at the time. It feels like an over-commit issue with cloud itself faulting the kernel in the VM.
1792915,2018-09-17 11:26:40 UTC,What now?
1792917,2021-02-17 17:09:34 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1792917,2018-09-19 16:40:00 UTC,"@Emilien - With the new command I still have to run the command twice. Once with no environment files passed to get the default container set, and another time with the environment file, to get the additional containers (like OVN)."
1792917,2018-09-17 12:19:54 UTC,Have you tried with `openstack tripleo container image prepare` ? It's the new command in Rocky.
1792920,2018-10-12 09:01:56 UTC,This is due to a single worker getting ENOMEM in response to all mmap syscalls even though there is no clear reason why that should be the case (plenty of memory and not an unreasonable number of current maps).  We don't yet know why this is happening.
1792920,2018-11-22 10:13:07 UTC,"I'm hoping that https://code.launchpad.net/~cjwatson/launchpad/optimise-git-ref-scan/+merge/359171 may improve the situation here.  We're also considering no longer scanning refs/changes/*, since it's very large for some repositories and not super-useful to have in the LP database (as opposed to in git)."
1792925,2018-09-17 13:16:06 UTC,Perhaps [1] need to be backported to Rocky?
1792925,2018-09-17 13:17:16 UTC,Looks like the backport was proposed here: https://review.openstack.org/#/c/603041/
1792925,2018-09-17 17:33:16 UTC,"Boden, I don't get your point. Why does the backport related to pylint affect q-dhcp failure?"
1792925,2018-09-17 18:21:36 UTC,"Akihiro please disregard my ref to the other patches.
I thought we had went with a different patch that changed agent code."
1792929,2018-09-17 13:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1792929,2018-09-17 13:17:00 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1792929,2018-09-17 14:50:50 UTC,I've tested the latest upstream kernels at http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc4 and have the same problem.
1792929,2018-09-17 14:54:02 UTC,"In response to the previous question - this occurred after upgrading xubuntu 17.10 to 18.04, previously the touchpad worked perfectly (and therefore must've have been detected). I am afraid I do not know which kernel version I was previously on."
1792932,2018-10-03 09:33:44 UTC,"the bug should be fixed with that upload (currently in proposed), https://launchpad.net/ubuntu/+source/xorg-server/2:1.20.1-3ubuntu2"
1792932,2018-10-01 02:45:01 UTC,Also tracking in:
1792932,2018-10-01 02:42:59 UTC,Judging by the duplicates it looks like this isn't specific to virtualbox. It's been happening for a few years.
1792932,2018-09-27 18:31:23 UTC,"was filed upstream already, linked here"
1792932,2018-09-21 12:12:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1432137, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1792932,2018-09-27 11:43:07 UTC,"that mesa is now on the latest ISOs, and apparently doesn't fix it after all"
1792932,2018-09-26 15:07:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1792932,2018-10-03 10:29:17 UTC,This bug was fixed in the package xorg-server - 2:1.20.1-3ubuntu2
1792932,2018-09-18 06:37:27 UTC,"could be a mesa bug which is fixed in 18.1.7/18.2.0-rc5+, please test the latter from"
1792932,2018-09-27 17:53:57 UTC,"right, not this case which is a bit weird one"
1792932,2018-11-10 21:22:52 UTC,"I am using Xubuntu 16.04.3 LTS, my current Linux kernel is 4.4.0-116-generic x86_64."
1792932,2019-10-30 16:34:22 UTC,This needs Regression Potential SRU information completed please.
1792932,2019-10-16 05:07:20 UTC,Any fixes/updates for bionic?
1792932,2019-10-21 14:52:02 UTC,please test if the package on https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging works (once it's built)
1792932,2018-09-17 13:22:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792932,2019-11-02 08:51:12 UTC,"Can't reproduce bug at Bionic, may be after some packege updates it's gone."
1792932,2019-11-14 18:16:46 UTC,"Hello Jean-Baptiste, or anyone else affected,"
1792932,2019-11-15 04:27:38 UTC,"All autopkgtests for the newly accepted xorg-server (2:1.19.6-1ubuntu4.4) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1792932,2019-12-14 11:04:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792932,2020-02-14 08:42:45 UTC,In bionic I couldn't verify the original bug because the HWE packages in 18.04.4 don't seem to be affected by this bug.
1792932,2020-02-14 08:57:03 UTC,I also tried the packages from proposed on top of 18.04.0 on which I could reproduce the original issue and the packages from proposed fixed it. double verification done.
1792932,2020-02-14 09:21:54 UTC,thanks for testing!
1792932,2020-02-17 16:53:53 UTC,This bug was fixed in the package xorg-server - 2:1.19.6-1ubuntu4.4
1792932,2020-02-17 16:54:02 UTC,"The verification of the Stable Release Update for xorg-server has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1792932,2018-12-13 18:11:34 UTC,-- GitLab Migration Automatic Message --
1792932,2018-04-02 20:57:24 UTC,"Created attachment 138508
naive assert fix"
1792932,2018-09-26 14:49:46 UTC,ubiquity-dm then the session start with mesa from the canonical-x/x-staging PPA.
1792932,2018-04-02 20:44:16 UTC,"Created attachment 138507
backtrace with debug symbols"
1792932,2016-08-12 00:16:35 UTC,"This is semi-related to another bug: https://bugzilla.kernel.org/show_bug.cgi?id=150731
And by semi, I mean it's either completely related or completely not related, and I don't know which yet."
1792932,2016-08-12 13:52:38 UTC,Please attach your dmesg output from after you load the amdgpu driver.
1792932,2016-08-12 20:04:19 UTC,"Created attachment 125758
dmesg log"
1792932,2016-08-15 03:41:44 UTC,"Since the Xorg log file ends abruptly, we'd probably need to see the Xorg stderr output. It should be captured in a display manager log file / the systemd  journal / ..."
1792932,2018-04-02 20:50:34 UTC,"I'm afraid I won't be able to help out with this anymore for I have no idea how long. I'm currently dealing with another bug in which DRI3 refuses to turn on for my NVidia GT 740, even though there's nothing wrong with DRI3, my hardware and conf files haven't changed, and downgrading my entire system back to a time before that other bug started happening does not make it go away. Because magic or something. Other nouveau users don't seem to have the issue besides one guy on reddit who's using a 730. Consequently, it's been months and I still haven't been able to find the cause. Until it's fixed, I can't test the entire premise that this bug report is based on--adding my AMD card to the current X server."
1792932,2016-08-15 04:27:56 UTC,"Created attachment 125786
x-0.log"
1792932,2016-08-15 04:28:12 UTC,"Created attachment 125787
x-0.log.old"
1792932,2016-08-16 09:46:07 UTC,Can you:
1792932,2016-08-16 20:54:19 UTC,"It looks like in Arch Linux, I'd have to recompile those packages myself to get debug symbols. At that point, I think it'd be easier to just do this in a LiveUSB of debian. If I have the same issue with this card in debian, would that debug info be as good as if I had done it in Arch?"
1792932,2016-08-17 00:48:46 UTC,"(In reply to jimijames.bove from comment #8)

> If I have the same issue with this card in debian,
> would that debug info be as good as if I had done it in Arch?
"
1792932,2016-08-17 23:14:59 UTC,"Alright, new problem. I have debian all set up to debug this. I even tested the whole debugging process without amdgpu running and it went swimmingly. But, as soon as I put in my 20-amdgpu.conf file, X crashes, because it can't grab my card from pci-stub, but in order to test this bug, I *need* to boot up the machine with the card bound to pci-stub. It's because for some reason, in Arch Linux, X is OK with loading amdgpu without finding a usable card, but in debian, not finding a card makes it freak out, even though Ignore is set to true. Here's the amdgpu part of the crash log from debian:"
1792932,2016-08-18 00:35:51 UTC,"(In reply to jimijames.bove from comment #10)

> Section ""Device""
>     Identifier ""Radeon""
>     Driver ""amdgpu""
>     Option ""DRI"" ""3""
>     Option ""Ignore"" ""true""
> EndSection
"
1792932,2016-08-18 00:45:37 UTC,"I forgot to mention, the reason I need that conf file is I need to test this on DRI3, because on the default of DRI2, the crash did not occur, meaning it's either a problem with Arch and not debian, or a problem with DRI3. Is there a section besides ""Device"" that doesn't disable fallback but still enables DRI3?"
1792932,2016-08-15 04:14:18 UTC,"That's interesting. Turning AutoAddGPU off completely fixed the problem, and didn't work the way I expected. With it off, my computer still automatically binds the card to amdgpu as soon as I rescan, so I guess that's a quirk of the kernel or amdgpu, but X takes the card in with no crash. It works as seamlessly as it's supposed to, and I can once again use DRI_PRIME to access the card. I'll turn it back off to get the error output (because there is none when I'm using this perfectly fine workaround), which I figured out is not in my Xorg logs (https://bugs.launchpad.net/lightdm/+bug/1322277), and upload that now."
1792932,2016-08-18 00:51:33 UTC,"Oh. I didn't know that. In that case, this got easier to test."
1792932,2016-08-18 00:49:00 UTC,"DRI3 needs to be enabled for the primary GPU. The secondary GPU doesn't matter for that; in fact, as I mentioned in comment 3, Xorg doesn't need to use the secondary GPU directly at all with DRI3. It's all handled by Mesa."
1792932,2018-04-02 15:00:40 UTC,"Hi there! Same issue, same use case, same distro."
1792932,2016-09-05 02:29:25 UTC,"OK, nevermind on that second debug report. Even though pacman tells me /lib64/ld-linux-x86-64.so.2 comes from glibc, reinstalling glibc with debug symbols (which DID make objdump --sym return plenty of symbols for /lib64/ld-linux-x86-64.so.2) did not change the output in any way. So, I don't know how to make gdb able to find debug symbols for /lib64/ld-linux-x86-64.so.2."
1792932,2016-09-05 00:18:31 UTC,"The ""Cannot access memory at address errors"" are weird, because yes, they popped up as soon as I ran gdb, but they didn't happen again until the moment of the crash, and there was a good 10 minutes between when I opened gdb and actually ran the test."
1792932,2016-09-05 00:01:36 UTC,"Created attachment 126211
debug-without-glibc"
1792932,2018-09-26 14:09:12 UTC,I deduplicated this bug because it happens without the X crash.
1792932,2016-08-18 02:03:39 UTC,"Sorry, I think I'm just confusing myself from not having a full grasp of the terminology."
1792932,2016-08-18 01:30:02 UTC,"(In reply to jimijames.bove from comment #17)

> But a crash happening anyway with DRI3 and Xorg not using the GPU directly
> is exactly the original issue I posted this bug report trying to fix.
"
1792932,2016-08-18 01:24:11 UTC,"But a crash happening anyway with DRI3 and Xorg not using the GPU directly is exactly the original issue I posted this bug report trying to fix. And I just finished testing without any of my own explicit options for amdgpu: no DRI3, no Ignore (and it the DRI_PRIME stuff I was doing still works fine, so you were right that those options had no point), and it's still crashing unless AutoAddGPU is turned off. So, I'll be grabbing that debug output in debian now."
1792932,2016-08-18 01:03:27 UTC,"Note that since the crash happens when Xorg tries to use the GPU, testing with DRI3 and Xorg not using the GPU directly cannot trigger the crash."
1792932,2016-08-18 01:00:48 UTC,"According to the xorg.conf manpage and the xserver code, Option ""Ignore"" only has an effect in ""InputClass"" and ""Monitor"" sections."
1792932,2016-08-18 02:29:46 UTC,"Argh. I finally got X configured and running in debian, and now I can't get the card to bind to amdgpu no matter what I do. The normal method--a rescan--results in it going straight back to pci-stub. If I unbind, then rmmod pci-stub, then rescan, it still refuses to bind to amdgpu. I think I'll just have to compile X and amdgpu in Arch after all."
1792933,2018-11-14 19:51:31 UTC,This was fixed by John recently in https://github.com/snapcore/snapd/pull/6093
1792933,2018-11-14 22:02:25 UTC,Thanks for fixing this!
1792934,2020-02-17 21:39:14 UTC,I inspected perl code in /usr/bin/debsums...
1792934,2020-02-17 20:50:51 UTC,"It is debsums bug. Uninstalling module-init-tools lets debsums pass first error, but it throws same error on another package:"
1792934,2020-02-17 20:51:46 UTC,"Not a problem with mentioned package, but with the tool ""debsums"""
1792934,2019-04-17 13:39:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1792934,2019-12-01 13:17:01 UTC,strace -f debsums module-init-tools:
1792934,2018-09-17 13:16:40 UTC,"(TBH I've no idea what debsums is nattering about, /usr/share/doc/module-init-tools/changelog.Debian.gz is a regular file, and no parent directory is a symlink.)"
1792936,2018-09-24 07:46:19 UTC,"I cannot reproduce this, looks like something is wrong with your host. Is this a physical machine or a VM? How did you install the host? Are you using a local package mirror? Please show the output of ""apt policy graphviz""."
1792936,2018-09-24 17:24:49 UTC,"Oh, wait, I can reproduce this by building a machine from a server ISO instead of running a pre-built cloud image. Will dig further."
1792936,2018-09-25 10:27:30 UTC,"O.k., so the reason for this behaviour seems to be that the failing packages are living in the ""universe"" repository. And the installation ISO only contains packages from ""main"" and ""restricted"", so this is what gets enabled by default, see also [1]. As a workaround, you can edit the /etc/apt/sources.list file and add ""universe"" after ""main"" on each line. Maybe we can have devstack do this automatically, otherwise there should at least be some warning in the documentation."
1792936,2018-10-01 10:07:39 UTC,"Yes, you are right. Everything works fine, after adding the ""universe"" repository as you recommend."
1792936,2018-11-22 13:20:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619562"
1792936,2019-07-03 16:38:29 UTC,"Reviewed:  https://review.opendev.org/619562
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=8d1b20b4c2334dc3045cea93441568657869f6d1
Submitter: Zuul
Branch:    master"
1792939,2019-06-06 11:52:56 UTC,"Is this a case where application 'A' is listening on port 8081, but then you add HA, and so haproxy becomes the one to listen on port 8081 ?"
1792939,2019-06-06 12:21:12 UTC,"@Junien,
haproxy should be the one. but there is a race when application receives event and closes port AFTER haproxy will try to open the same port."
1792940,2019-09-17 10:14:38 UTC,Migrated to https://github.com/widelands/widelands/issues/2116
1792943,2019-08-16 15:08:22 UTC,We've just hit the need for this feature :-
1792943,2019-08-16 17:38:59 UTC,"Thanks, we've got it in the roadmap ideas list and will see if we can get some movement on it in the future."
1792943,2018-09-18 10:47:08 UTC,"If we modeled them as part of Credentials then they would already be model
wide. However, I'd want to be sure that you wouldn't want to use 2
different pools for 2 different applications in the same model.
With CMR we can be a little bit more restrictive as you *could* create a
second model for the applications that you want. However, it still means
you wouldn't see them in the same fashion for ""juju status"", etc."
1792943,2018-09-18 11:58:43 UTC,"jameinel,"
1792943,2018-09-18 06:00:03 UTC,"Thanks this is helpful. As you noted projects are a different cloud typically and so we want to make sure we're looking to model the resource pools correctly across Juju ideas. Given your examples 1,2,3 it would seem that they might work more like regions, but I thought we already did a form of regions in MAAS so we'll have to investigate some more."
1792943,2018-09-17 14:46:42 UTC,How do resource pools typically work in production? Is this typically used to pool resources such as storage nodes or ceph targets? Using this as a model-config I worry is too wide a default. The docs on resource-pools doesn't seem to really speak to which level.
1792943,2018-09-17 15:12:05 UTC,"rharding,"
1792943,2018-09-18 06:59:48 UTC,I think it's important to distinguish them from regions as regions of a cloud are roughly sets of endpoints providing independent control planes (and data planes in most cases).
1792943,2018-09-17 16:25:40 UTC,One additional note: in case of OpenStack and projects Juju has to use different cloudspecs to actually provision machines in different projects.
1792946,2018-09-17 19:51:32 UTC,Will do - thanks Georg.
1792946,2018-09-17 16:06:15 UTC,"The bug has been already reported on Github and will be discussed there. And yes, for further reports (on other issues) please go to Github."
1792946,2018-09-17 14:05:15 UTC,Here are 2 screen shots from my colleague
1792946,2018-09-17 14:34:43 UTC,"Duplicate of
https://github.com/Stellarium/stellarium/issues/252"
1792946,2018-09-17 14:05:46 UTC,with Q pressed to remove cardinal points
1792946,2018-09-17 15:17:20 UTC,Am I logging any issues in the correct place here... or should I be using github?
1792959,2018-11-15 09:17:09 UTC,Thanks for your bugreport.
1792959,2020-01-07 10:59:01 UTC,We fixed on over agressive progress bar which resulted in much less of these calls AFAICT. Moving to medium for this reason.
1792977,2020-07-01 13:35:37 UTC,I think it's fair to say at this point that this isn't happening.
1792977,2018-09-17 16:18:29 UTC,Be sure to test exception propagation from server to client!
1792978,2019-01-26 09:31:21 UTC,"In the previous package removal, we are seeing:"
1792978,2019-02-04 10:58:58 UTC,Can you please give me more information about the environments this is failing in?
1792978,2019-03-20 18:56:16 UTC,"1) Testing
2) No, it's in baremetal
3) Attached.
4) The machine was deployed with maas - it's a bionic cloud image. We then install/configure maas, run some tests, and remove maas via purge, and repeat. This shows up sometimes on deployments after the initial one - avahi-daemon, or at least its pid file, is left in /var/run/avahi-daemon from a previous run. There are LOTS of commands run. The important ones seem like:"
1792978,2020-10-30 18:56:31 UTC,"Avahi is not covered by field sla, so unsubscribing field-high"
1792978,2019-01-28 14:06:49 UTC,Subscribed to field-high as this is causing a lot of failures lately.
1792986,2018-10-13 14:54:04 UTC,Good morning
1792990,2018-09-17 17:49:00 UTC,"This is already available under the ""Items"" tab of the layers manager.  You can select on/off references and values independently of the silkscreen layer"
1792990,2018-09-17 17:50:51 UTC,"Whoops, I just saw that you were referring in your title to the 3d display."
1792990,2018-09-17 19:05:18 UTC,"Sorry, Seth, I will try hard have to improve the way I report issues!
Most of the time I am in the middle of the work when I found the issue (or
when I have an idea)."
1792990,2018-09-17 19:49:36 UTC,"No worries.  Version information is always available when you are running KiCad under the Help->About KiCad menu.  Just click the ""Copy Version Information"" and paste it to the end of your report."
1792990,2018-09-18 00:37:30 UTC,"Sure, I know that. Sometimes I am just really busy.
Well, here is the version to make te report complete."
1792993,2018-09-17 17:42:00 UTC,Here is the gif
1792995,2020-02-04 22:49:00 UTC,I pushed a branch with a fix.  Now the full details will show for the row being clicked on. If no row is clicked on the UI shows the first selected row's details.
1792995,2020-02-17 21:59:03 UTC,"Works like a charm! Thanks, Mike!"
1792995,2020-02-21 15:52:45 UTC,"Pushed to master, 3.3 and 3.4.  Thanks Mike and Terran!"
1792995,2019-12-19 20:58:51 UTC,Confirmed on version 3.3
1792996,2018-09-18 06:41:31 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1792997,2019-03-24 15:49:43 UTC,Tom is this a doc update that needs to be done for hpe?
1792997,2019-03-25 13:38:24 UTC,"Jason, yes it is: the doc for hpe 3par driver was written before they added support for DHSS=True and it has not been updated to reflect that support."
1792997,2020-08-07 00:22:59 UTC,"The HPE driver maintainers are no longer active in the manila community; and so we've marked this bug as ""Wishlist"". It can be expired at the end of the Victoria cycle if there is no interest in this driver/documentation."
1792999,2020-04-30 15:33:31 UTC,Closing the nova side of the bug as it is originate from starlingx but they cannot reproduce it any more.
1792999,2019-12-06 14:48:27 UTC,"Closing. As per notes above, the issue is no longer reproduced with openstack train."
1792999,2019-12-04 11:35:50 UTC,"After doing live migration with uefi mode instance in NOVA on train,
Issue didn't happened."
1792999,2019-12-04 08:43:12 UTC,"@chengde, you mentioned this issue was not observed in recent StarlingX with OS Train.
Please post your update here."
1792999,2019-11-29 20:20:32 UTC,"@Yong Hu, Is it possible this was addressed in nova train? The associated nova bug seems to still be open."
1792999,2019-11-29 18:22:30 UTC,Test Result for: testcases/functional/nova/test_migrate_vms.py::test_migrate_vm_various_guest[ge_edge-1-1024-shared-image] - Test Passed
1792999,2019-08-23 17:42:49 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1792999,2019-08-08 16:02:20 UTC,"seeing @Yao is working on a nova patch https://review.opendev.org/#/c/621646/ for https://bugs.launchpad.net/nova/+bug/1785123, which is a duplication of this current LP."
1792999,2019-07-16 13:38:52 UTC,"The default plan is to rebase stein before RC1 or cherry pick to Stx-Nova.
Chris is the owner of that patch."
1792999,2019-03-05 19:02:40 UTC,This is an OpenStack nova issue tracked by https://bugs.launchpad.net/nova/+bug/1785123
1792999,2018-09-24 17:38:54 UTC,"Targeting stx.2019.03 as this is not a common guest use-case.
Note: this is a nova upstream bug. A nova bug needs to be opened and the fix proposed there.
Once that is done, the fix can be pushed to stx-staging until we rebase to a new version of openstack which includes the nova fix."
1792999,2019-11-13 01:47:56 UTC,"@chengde, please help check whether this issue still exists in Nova with ""Train"" version"
1793005,2018-09-17 19:15:17 UTC,1. Hatch extension patch to allow access to /eg2/*/staff/:
1793005,2018-09-17 19:18:03 UTC,"In 3.2, only a limited number of (acq) admin interfaces are using Angular6, so this may not be urgent for 3.2.  I suspect admin grids are printed infrequently."
1793005,2019-04-12 20:30:05 UTC,"Note if/when bug #1824391 is merged, this will need some updates."
1793005,2019-04-17 19:29:14 UTC,Rebased to master.
1793005,2019-04-24 18:10:14 UTC,"Hatch signoff
https://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/blake/lp1793005-hatch-eg2-access"
1793005,2019-04-24 19:48:16 UTC,"Evergreen signoff:
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/blake/lp1793005-ang6-hatch-rebase"
1793005,2019-04-24 20:03:41 UTC,"Both sign-off branches merged to master and 3.3.  thanks, Blake!"
1793007,2020-06-03 20:54:59 UTC,Could someone having the issue report it upstream on https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues ?
1793007,2020-06-02 15:03:49 UTC,This bug is still valid in Ubuntu 20.04.
1793007,2019-08-05 16:40:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793013,2018-10-19 21:07:44 UTC,"I did some more tests today.
Note: this is a mechanical MicroSATA laptop drive."
1793013,2019-01-04 22:25:48 UTC,"Hello,"
1793016,2018-09-18 11:39:08 UTC,"Found a work around by removing the option ""-f vmd""
Still a bug though."
1793016,2018-09-18 11:39:32 UTC,"meant ""vmdk"" of course."
1793016,2018-09-18 14:35:39 UTC,"Hi,"
1793016,2020-11-12 18:41:18 UTC,"I'm closing this ticket since it was likely just a wrong file extension ... if you disagree, feel free to open the ticket again."
1793022,2018-09-17 21:37:53 UTC,apport information
1793022,2018-09-17 21:37:55 UTC,apport information
1793022,2018-09-17 21:37:57 UTC,apport information
1793022,2018-10-03 07:08:32 UTC,This bug seems fixed after the latest 4.15 update (4.15.0-36-generic).
1793022,2018-09-18 06:28:59 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1793022,2018-09-19 08:13:16 UTC,"I checked (both laptops) and the bug seems to be fixed in the upstrem kernel (4.19-rc4). In the meantime I'll stick with 4.15.0-29. At the moment I edited /etc/default/grub with: GRUB_DEFAULT=""1>4"" to load it by default. Is it the correct way to do that? Thanks."
1793022,2018-09-17 21:37:51 UTC,apport information
1793022,2018-09-17 21:51:27 UTC,Please find the required apport information. Trying to send the information with the -34 kernel loaded I also realized the following:
1793022,2018-09-17 21:37:50 UTC,apport information
1793022,2018-09-17 21:37:48 UTC,apport information
1793022,2018-09-17 21:37:46 UTC,apport information
1793022,2018-09-17 21:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1793022,2018-09-17 21:37:36 UTC,apport information
1793022,2018-09-17 21:37:37 UTC,apport information
1793022,2018-09-17 21:37:39 UTC,apport information
1793022,2018-09-17 21:06:51 UTC,"AFAIR, this bug happened to me in Lenovo Thinkpad T430."
1793022,2018-09-17 21:37:42 UTC,apport information
1793022,2018-09-17 21:37:43 UTC,apport information
1793022,2018-09-17 21:37:45 UTC,apport information
1793022,2018-09-17 21:37:40 UTC,apport information
1793028,2018-11-09 07:40:39 UTC,"I should have read it more carefully, 2nd pass of reading makes it better.
The CVE is obviously fixed but it introduced a regression."
1793028,2020-07-02 21:15:20 UTC,"ipsec-tools and racoon are still being maintained by Debian (despite of some concerns), NetBSD and Apple. NetBSD has published the fix for this bug already in 2018 and since then published further improvements for setkey command. A subset of the upstream changes and some minor Debian changes have been packaged into a new version of PPA https://launchpad.net/~rdratlos/+archive/ubuntu/racoon (see changelog there) and published for the current Ubuntu LTS releases.
The related source code is now maintained on Github (https://github.com/rdratlos/racoon-ipsec-tools/tree/develop)."
1793028,2019-09-19 13:28:58 UTC,Summary:
1793028,2019-09-19 13:14:44 UTC,"See http://ipsec-tools.sourceforge.net/ for the abandonment, the supported ipsec solution is strongswan and I highly recommend to look into this instead."
1793028,2019-09-19 13:12:44 UTC," ipsec-tools | 1:0.8.2+20140711-5         | xenial/universe          | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 ipsec-tools | 1:0.8.2+20140711-10build1  | bionic/universe          | source, amd64, arm64, armhf, i386, ppc64el, s390x"
1793028,2018-11-13 06:53:31 UTC,"Thanks for the clarification Marc, it is on our list and tagged to be sooner, but atm I see no one with a few cycles left so it might be a few days more."
1793028,2018-11-09 12:25:28 UTC,"It looks like we inherited the bad patch from debian, as we haven't fixed this CVE ourselves. This isn't a post-release security update regression."
1793028,2018-11-09 07:30:15 UTC,"The security team lists that [1] CVE as fixed already.
I don't see it in [2] that is supposed to fix it thou."
1793028,2018-10-01 17:24:22 UTC,Upstream bug report: http://gnats.netbsd.org/51682
1793028,2018-10-03 15:14:48 UTC,Upstream NetBSD has reviewed the proposed code fix and proposed a slight modification which is now committed in their repository as add-on patch.
1793028,2018-10-09 19:21:07 UTC,Upstream bug report: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=53646
1793028,2018-10-01 17:30:14 UTC,"From the commit history at https://github.com/NetBSD/src/commits/trunk/crypto/dist/ipsec-tools/src/racoon/isakmp_frag.c it looks like debian (and ubuntu) has the latest changes. It's also not clear to me if SuSE reworked that patch, or also just took the latest version."
1793028,2018-10-01 23:26:59 UTC,Quote from upstream bug report discussion:
1793028,2018-09-18 06:20:27 UTC,"I've stored a ""patched"" package in Ubuntu launchpad that fixes this issue but again contains vulnerability CVE-2016-10396."
1793028,2018-10-02 09:09:36 UTC,"I performed some analysis and debugging of the isakmp fragmentaion error. The root cause seems to be a logical error in upstream CVE-2016-10396 patch. When applying this patch, racoon server prevents from DoS but does not recognize a completed reassembly of a isakmp fragemnt chain. This forces racoon clients like Apple iPhones that fragment isakmp messages to retransmit fragemnts which leads to a similar behaviour than the DoS attack, that developers wanted racoon servers to be protect from. So in turn, after a couple of retransmissions racoon server terminates pahse 1 negotiation. This prevents the fragmenting client from accessing the VPN."
1793028,2018-10-02 12:24:02 UTC,"The attachment ""0001-Fix-isakmp-fragmentation-bug-in-CVE-2016-10396-patch.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1793028,2018-10-01 23:31:58 UTC,"I would offer some support to better analyse the bug. The new log messages plus debug in racoon do not help much. Maybe dumping network traffic with wireshark could help, but traffic is encrypted."
1793029,2019-07-03 14:32:20 UTC,This issue was fixed in the openstack/neutron-lib 1.28.0 release.
1793029,2018-09-18 15:56:55 UTC,"I didn't try to reproduce this yet but I think that what happened here is:
1. By default in security group there is rule to accept ingress traffic from all other ports which uses same security group,
2. When You added this allowed_address_pair, security group rules (allowed source IPs) where updated for all other ports which use same SG - and because of that You had such bad rule in iptables."
1793029,2018-09-18 16:16:04 UTC,From #6:
1793029,2018-09-20 04:45:00 UTC,"I confirmed what is reported here with linuxbridge mechanism driver.
http://paste.openstack.org/show/730395/"
1793029,2018-09-20 04:45:08 UTC,[analysis of what happens]
1793029,2018-09-20 04:53:09 UTC,"For problem 2 in #10, I don't have a good solution directly.
What I can suggest is not to use ""remote group"" in security group rules and ""allowed-address-pair"" (with a wider IP address range) together. It is recommended to use ""IP address"" rather than ""remote group"" in security group rules if you use ""allowed-address-pair""."
1793029,2018-09-20 08:06:51 UTC,I agree with Akihiro's proposal here. IMO best thing we can do here is add warnings to documentation to make operators aware of this kind of risk.
1793029,2018-09-20 13:16:51 UTC,Thanks everyone for the prompt analysis. I've triaged this as a class B2 port per the OpenStack VMT taxonomy: https://security.openstack.org/vmt-process.html#incident-report-taxonomy
1793029,2018-09-20 17:21:32 UTC,"Thanks Akihiro, your description makes perfect sense and I see now why it did what it did. Definitely worth a note in the doc."
1793029,2018-09-24 12:29:33 UTC,Based on previous comments it appears we plan to doc this in the neutron api-ref.
1793029,2019-05-27 13:30:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661594"
1793029,2019-05-29 16:32:37 UTC,"Reviewed:  https://review.opendev.org/661594
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=e02c4b214b6762823c5e1ae5719f08f5f51910e8
Submitter: Zuul
Branch:    master"
1793029,2018-09-18 15:34:36 UTC,I just wanted to clarify a few things.
1793029,2018-09-18 14:23:17 UTC,@Alex:
1793029,2018-09-18 14:59:41 UTC,"Slawek, I'm not 100% sure as those are the one and the same in this environment. You might be right and it impacted all instances using the default security group."
1793029,2018-09-18 00:13:49 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1793029,2018-09-18 00:16:05 UTC,"Alex, are you saying an account for one tenant/project inserting this rule can bypass filtering for the instances/ports belonging to others? Or only for their own? If the latter, I think the sooner we switch this to a public workflow the better so that users will know to avoid doing this even before it gets patched."
1793029,2018-09-18 01:11:58 UTC,"Jeremey, yes, the latter. The only security risk here is that a user who can modify a port on a single instance can bypass security groups on all other instances within the same network (so does not cross tenants / networks). Not sure if that qualifies or not, but thought it better safe then sorry, so please feel free to open publicly if you are comfortable with it."
1793034,2019-01-17 15:38:00 UTC,"Reviewed:  https://review.openstack.org/622835
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=442c7c68c2c074591e96988059a63dd3c01e1ecd
Submitter: Zuul
Branch:    master"
1793034,2019-03-26 08:24:30 UTC,"Reviewed:  https://review.openstack.org/627282
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d078b95b59e08dc35903f2d93417c3c50dca9a00
Submitter: Zuul
Branch:    master"
1793034,2019-02-01 14:33:25 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/626778"
1793034,2018-12-21 01:10:54 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626778"
1793034,2018-12-25 09:31:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627282"
1793034,2018-12-05 04:41:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/622835"
1793034,2018-09-27 09:17:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605628"
1793034,2018-12-15 14:12:11 UTC,"Reviewed:  https://review.openstack.org/605628
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2a3e7affea8d0abeb5a9735695b967053088be42
Submitter: Zuul
Branch:    master"
1793035,2018-09-18 18:35:25 UTC,"I ended up finding a solution to this - there is still an issue with Sikuli out of the box, but here is my workaround:"
1793035,2018-09-19 06:14:35 UTC,Thanks for finding.
1793035,2018-09-19 07:00:05 UTC,Please test with the build from today.
1793035,2018-09-19 18:36:00 UTC,"Deleted the entire Sikuli folder in AppData, the JAR file of the previous build and also uninstalled RF through pip."
1793035,2018-09-20 08:14:18 UTC,Thanks for the confirmation.
1793040,2018-09-19 10:39:30 UTC,"Hi,"
1793049,2019-10-27 09:41:46 UTC,Was later synced automatically along with newer versions. Ubuntu 19.04 for instance shipped with i2p 0.9.38-3.
1793049,2018-09-18 23:17:05 UTC,Hi Masayuki!
1793060,2018-09-20 15:02:36 UTC,"(initramfs) configure_networking
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/"
1793060,2018-09-19 16:47:16 UTC,This types of errors appear when running configure_networking.
1793060,2018-09-20 09:53:13 UTC,Well the missing chown is not going to be a problem because there is only one user in the initramfs (root!). The chmod failing might be a problem but it seems a bit unlikely.
1793060,2018-09-18 06:04:51 UTC,"Thanks for the report. I'm a bit confused though, because although you're right that the call to chown will probably fail, I can't see how that failure will result in networking not being configured. Can you post the console log of networking failing to be configured?"
1793060,2018-09-18 23:57:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793074,2019-09-20 10:11:11 UTC,"I think we need assistance to work out what the deb should look like, but it is one of the items that we have on our list of todos."
1793077,2019-04-08 16:09:53 UTC,Is this still an issue? I cannot recreate it.
1793077,2020-02-25 08:18:56 UTC,Is this still a problem in MAAS 2.7?
1793077,2020-04-26 04:17:18 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1793079,2018-09-19 20:54:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793083,2018-09-18 07:58:43 UTC,As it was asked in several other bug reports: python3-distutils (v3.6.5-3) is installed.
1793083,2018-11-13 05:32:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793096,2018-10-15 21:07:14 UTC,"Thanks for your input, Michael."
1793096,2018-10-15 20:08:06 UTC,"To be honest, I think this bug may be mistargeted given what you say -- the store exposes the information I want, but it's not available via the snapd API. Currently subiquity only talks to the snapd API and I'd generally prefer to keep it that way..."
1793096,2018-09-18 09:15:27 UTC,"The update on this seems to be that the v2/ store api supports this data, but subiquity talks to the v2 _snapd_ api and that does not."
1793096,2018-10-12 12:25:08 UTC,"Michael,"
1793106,2018-09-18 10:10:50 UTC,apport information
1793106,2018-09-18 10:10:48 UTC,apport information
1793106,2018-09-18 09:54:20 UTC,apport information
1793106,2018-09-18 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1793106,2018-09-18 10:10:43 UTC,apport information
1793106,2018-09-18 10:10:44 UTC,apport information
1793106,2018-09-18 10:10:45 UTC,apport information
1793106,2018-09-18 10:10:46 UTC,apport information
1793106,2018-09-18 10:10:47 UTC,apport information
1793106,2018-09-18 10:10:49 UTC,apport information
1793108,2019-04-09 12:25:44 UTC,"Interestingly, I also can't reproduce it anymore (neither with 0.92.4 not 1.0~alpha)."
1793108,2018-09-19 16:07:18 UTC,"Hmm, we use glibmm for fetching the RSS feed, specifically
- Gio::File::create_for_uri()
- Gio::File::load_contents_async()"
1793108,2019-04-09 11:33:33 UTC,Closing because I can't reproduce this on Inkscape 1.0alpha on Ubuntu. Importing cliparts worked for me.
1793108,2018-09-18 16:07:57 UTC,Could this have been an intermittent problem (i.e. server problems or similar on openclipart.org's side)?
1793108,2018-09-19 13:46:21 UTC,"Not quite, it seems to be pretty consistent to me here."
1793111,2018-10-01 09:21:46 UTC,"@kaihengfeng, do those new projects find the problem is better when AC power is unplugged?"
1793111,2018-09-27 22:55:52 UTC,"Same thing happened to me in 4.19.0. Switched to Mint with kernel versions 4.19 and 4.18.3 and the same problem persists. Laggy and TouchPad does not work at all, except in the login screen. After initial install of Ubuntu it worked fine for about a day, then stopped after a reboot."
1793111,2018-10-08 05:04:11 UTC,"Not really.
So I think what I am working on and what you've been seeing are two different bugs."
1793111,2018-09-18 12:00:08 UTC,This change was made by a bot.
1793111,2018-09-18 11:30:45 UTC,Same bug in 4.19.0-041900rc4-generic
1793111,2018-09-18 10:26:58 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1793111,2018-09-18 10:12:22 UTC,Workaround:
1793111,2018-09-19 05:04:45 UTC,"Daniel,"
1793113,2018-09-18 12:22:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1793120,2019-11-19 16:24:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793120,2019-02-25 12:46:17 UTC,Tried with ubuntu-18.04.2-desktop-amd64. Same error.
1793122,2018-09-18 11:36:06 UTC,The translation is broken
1793122,2018-09-18 11:36:37 UTC,"I submitted a fixed translation for cosmic, changing"
1793124,2019-01-15 11:58:54 UTC,"I landed on this page from one of the duplicates. I would like to extend the issue to ""Cell with large dimensions make LibreOffice Calc impossible/unpleasant to work with""."
1793124,2012-08-14 14:20:20 UTC,Reproducable on v3.5.5.3 - view still jumps horribly.
1793124,2018-11-10 10:36:01 UTC,"(In reply to lupurus from comment #17)

> Sadly this behaviour is really annoying. Smooth scrolling would be nice.
>
> Unfortunately the docs for developers are not very good, I would really like
> to improve some stuff for LO :( Maybe someone can contact and help me (I use
> a Mac).
"
1793124,2018-12-13 23:14:32 UTC,"I checked all the pages, but developing for Mac is so badly documentated. I gave up, because it was too frustrating. Couldn't find out how to create the Xcode-project."
1793124,2019-01-18 19:25:17 UTC,"An obvious workaround is to zoom out on the sheet.  If that reduces legibility too far, then use assorted text function to split the text into different cells nearby, or reformat the cells using wrap etc. as appropriate."
1793124,2021-01-14 13:49:27 UTC,what does it take to fix it? will a donation make a difference?
1793124,2019-12-19 13:31:32 UTC,"(In reply to Mehrad Mahmoudian from comment #20)

> Suggestion:
> It would be wise to have an option in the preferences to let user choose
> between ""smooth scrolling"" and ""legacy scrolling"".
"
1793124,2020-03-06 09:35:19 UTC,It's still a problem in LibreOffice-6.4.11.
1793124,2020-06-07 15:38:54 UTC,"Set back to ""Inherited by OOo""."
1793124,2020-10-24 15:31:09 UTC,"Made an account to say, I'd really like this bug solved / feature added"
1793124,2020-10-24 15:49:34 UTC,"(In reply to Ethan from comment #27)

> Made an account to say, I'd really like this bug solved / feature added
"
1793124,2018-11-10 10:21:57 UTC,Sadly this behaviour is really annoying. Smooth scrolling would be nice.
1793124,2021-02-18 02:44:20 UTC,"Related meta: Bug 98754
Current ticket will celebrate 10th anniversary in a week"
1793124,2019-01-19 01:57:21 UTC,"(In reply to Libomark from comment #21)

> An obvious workaround is to zoom out on the sheet.  If that reduces
> legibility too far, then use assorted text function to split the text into
> different cells nearby, or reformat the cells using wrap etc. as appropriate.
"
1793124,2018-09-18 12:52:06 UTC,*** Bug 70525 has been marked as a duplicate of this bug. ***
1793124,2011-11-30 14:16:50 UTC,Noel is currently looking into the new input bar.
1793124,2018-01-29 17:23:53 UTC,*** Bug 114849 has been marked as a duplicate of this bug. ***
1793124,2012-08-15 09:34:09 UTC,"I agree - it's a ""showstopper"" only in the - admittedly rare - situation where the cell exceeds the window-size."
1793124,2012-08-15 08:29:33 UTC,"(In reply to comment #11)

>
> A real showstopper this one.


'showstopper' really? especially since you say Excel or Google docs do the same thing, its been like this forever etc. etc.
I think your scenario is not that common, this hardly this qualifies as a showstopper. Further more as Kohei explained this is by design ( admittedly there is room for improvement ) therefore I am making this an enhancement.
Anyway since the new inputbar does allow you to view and edit text that would normally be hidden in this scenario the situation has been improved somewhat."
1793124,2012-03-20 05:47:17 UTC,*** Bug 46505 has been marked as a duplicate of this bug. ***
1793124,2011-09-24 00:44:25 UTC,*** Bug 41139 has been marked as a duplicate of this bug. ***
1793124,2011-09-21 06:39:19 UTC,"BTW this is what Anurag Jain's GSOC work - support multi-line formula input bar - aims to resolve.  There was a bug filed for that (can't remember the number), and I would say it's more appropriate to mark this as a duplicate of that bug."
1793124,2011-09-21 06:37:41 UTC,"(In reply to comment #5)

> ""Bug 40917 - UI: scrolling only by full row height"" is not exactly the same
> issue, but I believe a common solution would be fine.
"
1793124,2011-09-21 01:48:51 UTC,"""Bug 40917 - UI: scrolling only by full row height"" is not exactly the same issue, but I believe a common solution would be fine."
1793124,2011-03-08 05:26:28 UTC,"(In reply to comment #3)

> Actually google docs (and, I think, Excell) has the same frustrating problem
> too.
>
> It's interesting that since Microsoft started this trend ""everybody"" has
> mimicked it without questioning wether it's good - or - more likely - bad.
"
1793124,2011-03-08 01:45:38 UTC,"Actually google docs (and, I think, Excell) has the same frustrating problem too."
1793124,2011-03-08 00:27:12 UTC,"Assigning to Kohei; as always, feel free to assign back to list if you feel having this on your list is not useful. Please add a comment if you have insight in how hard it would be to fix this."
1793124,2011-02-26 01:22:52 UTC,"[Reproducible] with ""LibreOffice 3.3.1  – WIN7  Home Premium  (64bit) German UI [OOO330m19 (build 8 / tag 3.3.1.2)]""."
1793124,2011-02-24 19:10:33 UTC,"Created attachment 43775
Spreadsheet with large row heights showing that scrolling is broken."
1793124,2018-08-28 22:03:49 UTC,*** Bug 84099 has been marked as a duplicate of this bug. ***
1793126,2018-09-18 16:56:33 UTC,"Created attachment 144989
Screenshot of a Calc sheet which shows wrong default alignment"
1793126,2018-09-18 16:56:53 UTC,I submitted an upstream report at https://bugs.documentfoundation.org/show_bug.cgi?id=119961
1793126,2018-09-18 14:49:02 UTC,"I can reliably reproduce the issue with libreoffice 6.0.3.2 on bionic, and with the 6.1.1.2 snap on cosmic."
1793126,2018-09-18 16:55:42 UTC,"Description:
Calc seems to assign the alignment of any particular text cell based on the contents of the cell: if the first character is a LTR character, the cell is aligned to the left, and if the first character is RTL, the cell is aligned to the right. This is desirable behavior but it breaks when the first character is neutral, i.e. a character that behaves as RTL in an RTL context and as LTR in a LTR context."
1793126,2018-10-12 17:11:19 UTC,"Apparently this feature was not yet in 3.3.0, but I can already repro in 3.6.7"
1793126,2018-09-18 11:38:25 UTC,I submitted a separate report for the font metrics problem at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1793127
1793126,2019-10-16 09:05:42 UTC,Still reproducible on
1793126,2019-10-13 02:34:14 UTC,"Dear vaaydayaasra,"
1793127,2018-09-18 14:41:58 UTC,"I can reliably reproduce the issue with libreoffice 6.0.3.2 on bionic, and with the 6.1.1.2 snap on cosmic. The issue can be observed in calc, not in writer."
1793127,2018-09-18 16:45:56 UTC,"Description:
In the attached screenshot, I’ve written an English sentence with an Arabic word in the middle on the first row of a Calc sheet. On the second row, I’ve written the same Arabic word (العربية) by itself. The second row looks as it should but on the first row, some of the characters overlap. The same problem occurs if I surround the isolated Arabic word with parentheses, in which case the cell is automatically aligned to the left. I’m using the default font settings, which in my environment are Liberation Sans for Latin text and DejaVu Sans for Arabic. The problem only occurs in Calc, not Writer."
1793127,2018-09-18 16:47:07 UTC,"Created attachment 144988
Screenshot of an Arabic RTL inset in the middle of LTR text"
1793127,2018-09-18 16:47:40 UTC,I filed an upstream report at https://bugs.documentfoundation.org/show_bug.cgi?id=119960
1793127,2018-10-12 17:40:38 UTC,Did some testing and looks like it appeared with the HarfBuzz implementation in 5.3.
1793127,2018-10-12 20:45:01 UTC,Can you also reproduce with 6.1.x or master ?
1793127,2018-10-13 06:21:03 UTC,"(In reply to Lior Kaplan from comment #3)

> Can you also reproduce with 6.1.x or master ?
"
1793127,2019-10-14 02:27:39 UTC,"Dear vaaydayaasra,"
1793127,2019-10-16 08:56:04 UTC,"I tested this again with LO 6.3.2.2 installed on Ubuntu as a snap. Now font metrics are still mixed up in the main view while I am typing and permanently on the formula line. When I finish typing and press Enter, the main display shows the characters correctly. So part of the problem is fixed, part is remaining."
1793127,2019-10-16 08:58:42 UTC,"Created attachment 155033
Screenshot on LO 6.3.2.2"
1793128,2020-11-17 10:10:07 UTC,I need this as well to connect lxd containers to a vlan:
1793130,2019-09-18 02:53:39 UTC,"Dear Muhammad Bashir Al-Noimi,"
1793130,2018-09-18 14:54:50 UTC,"I can reliably reproduce the issue with libreoffice 6.0.3.2 on bionic, and with the 6.1.1.2 snap on cosmic."
1793130,2018-09-17 17:24:18 UTC,"(In reply to Eike Rathke from comment #14)
That change seems like an easy fix for a developer who knows her/his way around the ""EditEngine"" - or am I wrong?"
1793130,2017-11-03 19:26:06 UTC,Still happens in:
1793130,2017-10-13 14:03:58 UTC,"That analysis is not quite correct. The default cell alignment is *non-aligned*, how content is displayed horizontally aligned depends on the actual content. When editing cell content the EditEngine is used that seems to default to left-aligned (didn't check). Setting a hard alignment attribute at the cell is not correct and will break other things. Instead, the algorithm that decides how to align for display must also be used to set the default alignment for the EditEngine when in edit mode."
1793130,2017-10-13 11:02:03 UTC,"So the problem is that though RTL is enabled on a cell, the 'Default' value set to horizontal text alignment is always putting it as left aligned rather than right aligned."
1793130,2017-10-12 10:47:49 UTC,Still happens in LibreOffice 5.4.1.
1793130,2015-03-20 09:29:08 UTC,"Still happens in 4.3.3 when layout isn't explicitly set, but hinted by direction (LTR,RTL). This happens regardless of sheet direction."
1793130,2016-04-16 07:26:44 UTC,** Please read this message in its entirety before responding **
1793130,2013-06-09 17:10:24 UTC,"Not a duplicate, verified on master (where the other bugs were closed)."
1793130,2015-03-17 00:03:46 UTC,** Please read this message in its entirety before responding **
1793130,2013-06-09 06:55:03 UTC,All the Arabic text with Right To Left layout appears in Left To Right layout during input process then back to the right layout after finishing editing process.
1793130,2013-06-09 06:55:41 UTC,"Created attachment 80554
Wrong layout during editing the cell"
1793130,2013-06-09 06:56:38 UTC,"Created attachment 80555
Wrong layout during editing the cell"
1793130,2013-06-09 07:49:13 UTC,"Sorry, duplicate of 63546"
1793130,2013-06-09 07:25:24 UTC,confirm in 4.1 beta 1
1793130,2013-06-09 07:44:54 UTC,"Fixed in LO4.1 Beta
http://www.libreoffice.org/download/pre-releases/"
1793130,2013-06-09 08:03:00 UTC,"(In reply to comment #6)

> Sorry, duplicate of 63546
>
> *** This bug has been marked as a duplicate of bug 63546 ***
"
1793130,2013-06-09 06:57:09 UTC,"Created attachment 80556
After finish editing the cell"
1793132,2018-09-20 21:45:45 UTC,"Reviewed:  https://review.openstack.org/603333
Committed: https://git.openstack.org/cgit/openstack/ovsdbapp/commit/?id=31a476435373a8c6581ad66d96fbe314711e7f36
Submitter: Zuul
Branch:    master"
1793132,2018-09-25 21:07:53 UTC,This issue was fixed in the openstack/ovsdbapp 0.13.0 release.
1793133,2019-06-11 11:06:49 UTC,"Now we have ubuntu_ltp_syscalls printing summary:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=0aa562bd0cdc80e1427a67cb13cf8a6f76fd47d1"
1793134,2018-11-08 15:24:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616585"
1793134,2018-11-21 12:13:00 UTC,"Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master
Review: https://review.openstack.org/616585
Reason: clearing the gate"
1793134,2018-11-22 21:49:22 UTC,"Reviewed:  https://review.openstack.org/616585
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=e3a410f699efb3fbdc34f95299c68c75bbc2de0a
Submitter: Zuul
Branch:    master"
1793137,2018-09-19 08:18:06 UTC,"Reviewed:  https://review.openstack.org/583499
Committed: https://git.openstack.org/cgit/openstack/charm-lxd/commit/?id=4d7b3e924008af878b0c369c1bd3e92238d51a93
Submitter: Zuul
Branch:    master"
1793137,2018-09-20 09:10:35 UTC,Note that the LXD charm change is a workaround to the nova-lxd bug.  The nova-lxd bug still needs to be fixed so that the LXD pool name can be different to the ZFS pool name.
1793147,2019-03-22 02:20:29 UTC,I had a closer look at both commands' help.
1793147,2019-03-22 02:23:20 UTC,"As this is a usability bug, just a correction in command help, it was mis-triaged as High (a category usually reserved for functional changes). Also we are not likely to backport it to previous Juju versions. So, I have re-targeted this correction to go into current development branch that is heading into 2.6."
1793148,2019-08-21 19:35:26 UTC,"Fixed in revision a6b7d4f7f6cc51d5ba2aed76227d2e530e4532a5
https://git.launchpad.net/kicad/patch/?id=a6b7d4f7f6cc51d5ba2aed76227d2e530e4532a5"
1793148,2019-08-22 17:15:43 UTC,Hi Jeff-
1793148,2019-08-22 23:26:58 UTC,"@Seth, I think we should fix up the python test cases.  Where do I find them?"
1793148,2019-08-22 23:36:54 UTC,Sounds good.  They are in qa/test.py
1793148,2019-08-22 23:57:13 UTC,"I've pushed what I think should fix them, though the test framework won't run on my machine so I can't be 100% sure."
1793151,2020-09-21 15:36:16 UTC,"Marking Confirmed, this can be very confusing for staff when assisting patrons and managing holds. The issue is that on the title side, metarecord holds only display on the master record of the metarecord group, not the individual metarecord member titles."
1793151,2020-09-21 15:50:59 UTC,We encountered a problem with a metarecord hold last week that was made substantially more difficult to troubleshoot because of this.
1793152,2019-02-01 11:07:42 UTC,"Indeed, that's still an issue in disco"
1793152,2019-02-01 12:17:55 UTC,That's known upstream as https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/70
1793154,2018-09-18 20:35:20 UTC,"Adding a note that the fix I just posted was only applied to the holds shelf, not the record holds interface. I did a quick test on a master system, and I am seeing this problem. I'll target the bug to 3.2 for now since I'm pretty sure it's a result of code from bug 1712854."
1793154,2018-09-18 20:20:15 UTC,I'm unable to replicate this on the community demo server running 3.1.4. I can try upgrading it to 3.1.5 later this week to see if something was added during this time period to make it break.
1793154,2018-11-20 16:59:15 UTC,The action handler name was a bit wobbly and so the grid couldn't find the function to call. This branch puts it back on the map:
1793154,2018-11-20 17:35:58 UTC,Works like a charm! My signoff branch is at:
1793154,2018-11-20 18:00:47 UTC,"Pushed to master and rel_3_2.  Thanks, Jason and Michele!"
1793160,2018-09-18 14:45:49 UTC,"More info: my OS is Ubuntu 18.04. The version of HPLIP is 3.18.7.
After reinstalling hplip so that i can actually print, hp-doctor returns
errors about its being unable to read a couple of files in /etc/cups/ppd,
but those are the only errors.  I set those files to be readable, and that
removed them."
1793160,2018-09-19 10:58:58 UTC,"Hi Jds,"
1793160,2018-09-19 13:02:32 UTC,"Yes, they are on the same network."
1793161,2020-04-05 06:36:09 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1793163,2019-06-23 23:00:39 UTC,I think this was fixed some time ago.  Footprints no longer include their text in the selection boundingbox -- whether the text is visible or not.
1793163,2018-09-18 16:43:57 UTC,"Seems like I suck at trouble-shooting. When creating a completely new project, the selection works as expected. So, I've emailed you a project where it doesn't behave correctly (your ucdavis email)."
1793163,2018-09-18 16:10:35 UTC,Not selecting an object when fully encompassed is certainly an error.  I cannot recreate this on my machine.
1793163,2018-09-18 16:51:16 UTC,I received your project.
1793163,2018-09-18 14:55:34 UTC,This is intentional.  One is a touching selection one is an included selection.  Note that the selection box is also colored differently.
1793163,2018-09-18 15:42:39 UTC,"Ok, but that's not how it behaves. Starting in the top-left corner, dragging the box so that it completely encompasses all vias in the array (with margin), it still selects none of them. It seems like the box is drawn in one place, but the selection is done with an offset to it."
1793166,2018-10-03 15:11:52 UTC,"It's not wrong, because it really should have that dependency since it's using sbsigntool, but you shouldn't be hitting this bug in the first place: shim-signed should always be installed on UEFI systems, and does pull in sbsigntool."
1793167,2018-09-19 07:51:23 UTC,Please find same picture of eclipse JDialog issue with problem encircled
1793167,2018-09-19 07:13:50 UTC,"Sorry, I can't see the problem in those screenshots. Can you circle it?"
1793167,2018-09-18 15:33:41 UTC,Here the correct context menu behavior when screens have their left edges aligned
1793167,2018-09-19 07:50:17 UTC,"Hello,
Please find same picture of context menu issue with problem encircled"
1793167,2018-09-18 15:28:33 UTC,Problem with context menu
1793167,2018-09-18 15:32:11 UTC,Here the correct behavior with eclipse JDialog when screens have their left edges aligned
1793172,2018-09-18 16:30:06 UTC,This change was made by a bot.
1793172,2018-09-19 06:52:30 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1793172,2018-09-19 15:23:34 UTC,Hi Joseph
1793172,2018-09-20 06:31:40 UTC,"worked it out, see TAG below"
1793172,2018-10-14 21:33:02 UTC,"Still taking a very long time to boot up. gives a different acpi error messag.
THEN error message saying
lvmetad missing and scans system to find suitable.
any suggestions gratefully received."
1793177,2019-04-26 17:16:02 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1793177,2019-03-13 14:57:26 UTC,"Reviewed:  https://review.openstack.org/603439
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=76f937b50a50dd43b97d62ebab8459bc98cfe554
Submitter: Zuul
Branch:    stable/pike"
1793177,2018-09-24 08:54:31 UTC,"Hey Matt, it was set to auto."
1793177,2018-09-23 22:40:37 UTC,What is the value of [upgrade_levels]/compute in nova.conf? It should be Ocata for compatibility while you're doing rolling upgrades (or 'auto' might work too).
1793177,2018-09-18 16:42:10 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/603439"
1793178,2018-09-18 17:00:06 UTC,This change was made by a bot.
1793178,2018-09-19 06:51:48 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1793178,2018-09-19 14:22:09 UTC,"Thank you a lot that was a good advise, with the mainline kernel 4.19-rc4 everything is working now. Even System Suspend and the backlight keys, now the laptop is just perfect."
1793181,2018-10-10 23:58:59 UTC,"Thanks, I'm glad that you find errors.ubuntu.com useful! The bug you've referenced contains information about why we don't retrace crashes from PPAs specifically:"
1793184,2018-09-18 18:30:19 UTC,Pushed this change to master
1793185,2018-09-18 17:31:37 UTC,Fixed in b5fd4c6befb44fdfc5dd2c095e82590b1e587f21.
1793202,2018-09-19 14:16:49 UTC,"If we enforce SSE2 in our own init code, people without SSE2 couldn't build Mixxx without hacking it. So I second having our Ubuntu package depend on the sse2-support package. Or if there are many non-SSE2 users, should we be building our x86 package without it?"
1793202,2018-09-19 06:21:23 UTC,The same issue may effect our other 32 bit targets. Do we reach main() with sse2 enabled and msvc?
1793202,2018-09-19 06:04:43 UTC,"Sounds like a good solution.
How does this work on none x86 architectures?"
1793202,2018-09-18 23:06:08 UTC,"What would be the best way to do that? Since this crash is in static initialization, we don't have the chance to add a check in main(). If we had a wrapper script that runs mixxx we could do it there, but I'm not sure that's the best way?"
1793202,2018-09-19 16:04:20 UTC,"With sse2 support I am able to use Mixxx on my old Netbook. If we remove it, we have a regression for these devices in favour of older devices which may not be usable anyway."
1793202,2020-05-10 10:00:24 UTC,Won't fix because almost all Devices have sse2 now.
1793202,2018-09-18 21:54:43 UTC,"Instead of crashing, we can warn the user and suggest to build Mixxx build on their own."
1793202,2018-09-18 19:05:51 UTC,This has been reported 75 times in the last year according to errors.ubuntu.com.
1793205,2018-09-27 08:55:00 UTC,"I have tried reproducing the issue https://bugs.launchpad.net/cinder/+bug/1536248 on next environment:
MOS7.0 + MU8 updates
Cinder host:
Ubuntu 14.04
cinder-volume                        1:2015.1.1-1~u14.04+mos3062
python-cinderclient                  1:1.1.2-1~u14.04+mos323
python-rtslib-fb                     2.1.45-4~u14.04+mos2
python2.7                            2.7.6-8ubuntu0.4
linux-image-generic                  3.13.0.158.168"
1793205,2018-09-21 14:41:00 UTC,"Fix proposed to branch: openstack-ci/fuel-7.0/2015.1.0
Change author: Eric Harney <email address hidden>
Review: https://review.fuel-infra.org/39315"
1793205,2018-09-24 16:15:35 UTC,"Reviewed: https://review.fuel-infra.org/39315
Submitter: Denis V. Meltsaykin <email address hidden>
Branch: openstack-ci/fuel-7.0/2015.1.0"
1793205,2018-09-21 15:43:06 UTC,https://review.fuel-infra.org/#/c/39305/
1793206,2019-02-17 03:43:43 UTC,any comments ?
1793207,2018-09-18 19:51:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/603485"
1793207,2018-09-19 20:03:25 UTC,"Hi Brian,"
1793207,2018-10-18 17:12:15 UTC,Sorry for super late.
1793207,2019-11-26 19:26:59 UTC,"Was just going through old bugs and patches and noticed this one, updating based on information I received."
1793207,2019-11-26 19:30:03 UTC,"Change abandoned by Brian Haley (<email address hidden>) on branch: master
Review: https://review.opendev.org/603485
Reason: It was intentional to make this admin-only, see the bug for more information."
1793212,2019-01-09 12:51:34 UTC,This KB resolved my issue https://kb.juniper.net/InfoCenter/index?page=content&id=KB30500
1793213,2018-09-18 22:01:51 UTC,The problem was due to MariaDB not functioning after a test.
1793216,2018-09-19 02:10:11 UTC,"another useful function of such a feature is that you almost never want to move your board outlines, but when selecting a large portion of the layout you may inadvertently tweak them. this would help avoid moving board outlines inadvertently as well."
1793216,2018-09-19 02:26:58 UTC,found a picture of the mentioned preemptive selection filter context menu
1793216,2018-09-22 13:36:58 UTC,To extend that problem :
1793216,2018-09-22 14:11:23 UTC,"Franck,"
1793216,2018-09-25 21:28:07 UTC,It will be implemented as a selection filter panel.
1793216,2018-12-13 13:07:14 UTC,Isn't #1670428 a dublicate of this wish?
1793216,2019-05-05 16:15:20 UTC,+1 https://bugs.launchpad.net/kicad/+bug/1827781 :-)
1793216,2019-07-08 13:36:06 UTC,+1 on this feature request:
1793218,2018-09-27 20:59:13 UTC,I have tested this with the latest stable/rocky build of Kolla and Kolla-Ansible with no change in behavior - it appears that the configuration is broken.  I don't know enough about Kibana and ElasticSearch to diagnose the problem.
1793218,2018-10-02 08:58:33 UTC,"Just a quick note that this is still an issue with the latest built-from-source Kolla and Kolla-Ansible today (October 1, 2018), so 7.0.0.0rc2-devXX (I think dev24 and dev17 versions, respectively)."
1793218,2019-10-12 14:12:18 UTC,I don't believe it's broken per say. I just had the same behavior on a Stein/Centos7 with pip Kolla 8.0.2 deployment.
1793218,2019-10-12 14:30:01 UTC,It looks like there is a ES index at  :
1793222,2020-01-06 09:13:25 UTC,After Ubuntu 19.10 I couldn't reproduce on any system.
1793222,2018-10-01 22:46:05 UTC,Indeed. I took some hours to try it myself on a fresh installation. The bug didn't appear. I will try to find out more about the environment and post infos as soon as I have them. Maybe it's something that only happens through the upgrade...
1793222,2018-09-26 10:41:57 UTC,"I have tried to reproduce it in the live session of Xubuntu 18.04.1 and 18.10 (dev release), but I did not encounter the issue."
1793222,2018-09-26 04:28:09 UTC,Sorry for the doublepost.
1793222,2018-09-26 04:24:54 UTC,I was trying to make the bug better reproducable. I now think it's a bug in ibus-anthy. Firefox will btw. have the same behavior.
1793222,2018-09-21 14:28:52 UTC,Works fine here.
1793222,2018-09-26 07:14:00 UTC,"aw. And yes, I'm also able to trigger this with another user account."
1793229,2018-09-19 07:09:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1735995, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1793229,2018-11-05 01:48:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793231,2018-09-19 00:19:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1793231,2018-09-19 02:07:16 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1793231,2018-10-10 06:56:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793231,2019-10-04 13:17:27 UTC,Has this issue been seen with any later Lubuntu release?
1793231,2019-12-04 04:17:32 UTC,[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1793242,2020-06-30 11:33:59 UTC,Same issue here on Kubuntu 20.04
1793242,2020-01-07 20:33:28 UTC,"This is pretty much how it has always been, but I never had the time to properly analyse it and report it to the KDE devs (just found this report here while searching for it, because I got annoyed again)."
1793242,2019-01-03 14:43:47 UTC,"Same issue on Fedora29 KDE spin listed above. I located the session file ~/.config/ksmserverrc and  firefox et al are all present, and are restored correctly when I boot-up again (this is using automatic previous session restore). Chrome however, is not restored."
1793242,2019-01-03 14:40:08 UTC,"OS: Fedora 29 Twenty Nine
Kernel: x86_64 Linux 4.19.10-300.fc29.x86_64
Uptime: 23m
Packages: 2057
Shell: bash 4.4.23
Resolution: 5120x1440
DE: KDE 5.53.0 / Plasma 5.14.4"
1793242,2018-09-19 02:28:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793244,2018-09-19 04:26:09 UTC,UDP egress should always be allowed unless you have modified them.  Are you sure you have the ingress rules set correctly for all the ports iperf might be using?
1793244,2018-09-19 04:55:32 UTC,"1. Default security group, which I use for now, has the following rules:"
1793244,2018-09-19 06:04:01 UTC,"2. I've changed firewall_driver from 'openvswitch' to 'iptables_hybrid' on compute nodes, and udp works fine.
It seems there is some kind of bug with ovs fw?"
1793244,2018-09-19 07:23:16 UTC,"Hi,"
1793244,2018-09-19 08:00:57 UTC,"Slawek,
thanks for being envolved!"
1793244,2018-09-19 13:11:18 UTC,"Just a follow-on to Slawek's comment.  If you changed the firewall driver and started new VMs, then they should be plugged differently and be using iptables, and not possibly bypassing rules."
1793244,2018-09-20 21:39:02 UTC,"Guys,"
1793244,2018-09-21 15:49:09 UTC,"@Annie: if Your vm was created when ovs fw driver was used and has ovs_hybrid_plug=False then if You switch to iptables firewall driver, this vm will not have security groups at all. That will be the only impact of such vm later."
1793244,2018-10-05 22:15:19 UTC,"Hi, I tried to reproduce this issue on master branch on single node devstack. All worked fine for me.
Can You check exactly where traffic is blocked in Your case? Is it really on some openflow rules on destination host?
Also another question - does both Your vms using same security group rule? If so, all traffic should be accepted between them by default so adding other security group rules for upd traffic shouldn't be necessary at all."
1793252,2018-09-19 05:25:30 UTC,examples
1793253,2018-10-17 08:16:14 UTC,"Did you report this on cairo? I'm unable to found appropriate entry nor on old nor new cairo bugzilla. If so, can you paste link to it?"
1793253,2018-10-07 15:20:51 UTC,"I would report this bug to cairo.
Since they use a sigabrt, I could not catch it with a try/catch, and listening for the ABRT signal() is what we already do for the emergency save."
1793253,2018-09-19 17:52:20 UTC,"Confirmed on Windows 10 with
- Inkscape 0.92.3 (98b32c4a03, 2018-09-15)
- Inkscape 0.92+devel (05291f649e, 2018-09-15)
in an MSYS2 environment (which handles the conversion from POSIX-style paths)."
1793253,2018-09-19 12:24:11 UTC,"My inkscape open this z.svg file. You can try chrome(ium) or firefox.
But contents of this file is rather irrelevant. This file only must have some path element, id=""top"" and no ""width & height"" in svg element."
1793253,2018-09-19 10:30:08 UTC,"not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1793253,2018-09-21 05:46:51 UTC,"Little update, crash didn't occur when angle in transformation rotation is 90 degrees multiplier. Ie:"
1793254,2018-09-23 06:41:23 UTC,I ran 18.04 off a USB (I did not install) and the applications mentioned above looked fine.  Just thought I would let you all know.
1793254,2018-11-26 05:18:15 UTC,Sorry for the late reply here but did you see the same behavior with the original installation media before you installed? I assume you used some other media than USB?
1793255,2018-11-28 20:07:52 UTC,I have restored https://review.openstack.org/#/c/605154/ and updated it.
1793255,2019-03-24 23:39:53 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1793255,2019-03-22 03:45:52 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1793255,2019-01-31 13:44:19 UTC,"Reviewed:  https://review.openstack.org/630997
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7a0203c9ad1b10596f5de0d0954ee3ccb356d685
Submitter: Zuul
Branch:    stable/rocky"
1793255,2019-01-15 14:42:56 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/630997"
1793255,2018-12-17 16:36:52 UTC,"Reviewed:  https://review.openstack.org/605154
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=983e6ea5518dee956d8054cd67dddbe98eab9f78
Submitter: Zuul
Branch:    master"
1793255,2018-11-28 20:54:28 UTC,"Since https://review.openstack.org/610673 merged, it should not be required to install nova-consoleauth unless the [workarounds]enable_consoleauth config option has been set to True by the operator."
1793255,2018-11-28 19:44:31 UTC,Also see related bug 1798188. I'm not sure if this should be duplicated against that or not.
1793255,2018-10-15 17:42:06 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: master
Review: https://review.openstack.org/605255
Reason: Instead of un-deprecating, we fixed the code to actually make nova-consoleauth optional:"
1793255,2018-10-15 23:54:57 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/607038
Reason: Instead of un-deprecating, we fixed the code to actually make nova-consoleauth optional:"
1793255,2018-09-23 22:51:41 UTC,Installing nova-consoleauth was removed from the docs in Rocky as part of this change:
1793255,2018-10-01 20:08:45 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/607038"
1793255,2018-09-25 22:45:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/605255"
1793255,2018-09-25 22:25:56 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: master
Review: https://review.openstack.org/605154
Reason: We need to do more than this and un-deprecate nova-consoleauth, so the revert is here:"
1793255,2018-09-25 22:20:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605250"
1793255,2018-09-25 17:16:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605154"
1793255,2018-09-23 22:57:06 UTC,Should have been fixed as part of this:
1793255,2018-11-28 18:21:02 UTC,We continue to get bugs in triage for the rocky install docs not saying that nova-consoleauth should be installed (duplicated to this bug). So I think we need to say *something* in the install guide about the nova-consoleauth service install (which was removed in https://review.openstack.org/#/c/565367/) - maybe it would be as simple as adding a note and linking to the workaround config option for more details:
1793256,2019-01-26 14:20:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793259,2020-07-30 21:51:49 UTC,"Reviewed:  https://review.opendev.org/742784
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=fc6ca22bdb955137d97cb9bcfc84104426e53842
Submitter: Zuul
Branch:    master"
1793259,2020-07-24 05:54:46 UTC,uploaded a patch: https://review.opendev.org/#/c/742784/
1793266,2019-05-09 12:53:39 UTC,"I tried it on two repositories that I couldn't delete.
Both were imports of external repositories."
1793266,2019-08-06 17:32:04 UTC,"It sounds like the indexes did the trick.  If we come across new cases where deletion performance is a problem, please file a new bug and we can look into it there."
1793266,2019-05-09 13:04:58 UTC,I can also confirm this working on a previously failing repo: https://code.launchpad.net/~pymor/pymor/+git/pymor
1793266,2019-05-09 12:26:42 UTC,"It fixed the issue for me, thanks!"
1793266,2019-03-25 13:34:14 UTC,r14049 in db-stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-stable/revision/14049) is part of this bug's fix.
1793266,2019-04-02 09:30:38 UTC,r18920 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18920) is part of this bug's fix.
1793266,2019-03-25 13:35:56 UTC,"2019-03-22 18:02:54,291 INFO    2210-01-0 applied just now in 0.1 seconds"
1793266,2019-01-30 12:36:20 UTC,"It's odd that the delete from Job is so slow, since selecting from it is quite quick on staging.  Perhaps there are some badly organised indexes or something."
1793266,2018-11-20 20:49:47 UTC,"Hi, I tried again today, still the same issue, that repository isn't deleteable and needs to be removed manually by some administrator."
1793266,2019-05-09 11:42:15 UTC,"Could you please give this another try?  We may still need the asynchronous deletion, but in the meantime we added some more database indexes yesterday (https://code.launchpad.net/~cjwatson/launchpad/more-job-indexes/+merge/367063) which may well have helped."
1793270,2018-11-14 06:39:47 UTC,"As described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907539 , installing gimp-python solves the problem."
1793270,2019-07-22 13:38:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793270,2019-08-01 10:49:41 UTC,"The gimp-python needs to be a dependency, please fix it."
1793272,2019-04-06 01:18:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793272,2019-04-06 01:21:33 UTC,This isn't just ARM. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907308
1793280,2018-10-10 15:34:43 UTC,"Those are the expected versions, I'm not sure what's going on that makes update-alternatives want to write to /usr/local/var/log/alternatives.log."
1793280,2018-10-05 20:33:46 UTC,"david@Vbox:~$ update-alternatives --version
Debian update-alternatives versie  1.19.0.5."
1793280,2018-09-21 15:30:23 UTC,Translated error message:
1793280,2018-09-21 21:54:50 UTC,"the package came pre installed with ubuntu bionic.
I didn't change anything to the setup.
Because of this error i can't install any package using software manager
or apt-get."
1793280,2018-09-21 15:34:21 UTC,It is weird that update-alternatives would want to write to /usr/local/var/log/alternatives.log. It should write to /var/log/alternatives.log.
1793280,2018-10-04 07:00:49 UTC,Can you please share the output of the following commands?
1793282,2018-09-19 10:20:38 UTC,Can you be more specific about the steps to reproduce this?
1793282,2018-09-19 10:22:35 UTC,"For reference, bug #1704501 actually added the ability to move VLANs to a different fabric. Previously, we had recommended simply recreating the VLAN with the given VID in the target fabric, rather than moving it (which may be problematic in some cases, especially when you have already-deployed machines)."
1793282,2018-09-19 11:02:35 UTC,"Hmm. Testing this again, I can see that MAAS does move it to a different fabric after all."
1793286,2019-10-31 03:34:43 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1793286,2018-12-12 15:05:17 UTC,"Thanks, we're searching through the codebase trying to find where such an error is thrown and it's a bit tough without more of the context. Next time you hit a report that has it if you could help post it it'll help us make sure we're doing the right thing in the right place."
1793286,2018-12-10 13:12:42 UTC,"Hi Junien Fridrick,"
1793286,2018-12-12 14:05:47 UTC,"Hey Junien,"
1793286,2018-12-12 14:50:05 UTC,"If I remember correctly, the state of the api-server worker was literally ""shutting down"". thumper suggested that the reason of the shutdown should be added to the ""report"" field, and so I filed this bug."
1793286,2018-12-10 13:53:04 UTC,"Hi,"
1793297,2020-11-12 18:42:00 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1793297,2021-01-12 04:17:34 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1793301,2019-01-13 00:55:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793301,2019-01-23 13:58:05 UTC,"Here is a one-line to work around the issue:
    sed -i 's#export KEY_CONFIG.*#export KEY_CONFIG=""$EASY_RSA/openssl-1.0.0.cnf""#' /home/ubuntu/openvpn-ca/vars"
1793301,2019-02-05 14:23:06 UTC,"Same problem, using the command below as workaround:
   ln -s openssl-1.0.0.cnf openssl.cnf"
1793305,2020-03-18 20:47:10 UTC,"Forget it, please. Sorry."
1793305,2020-03-18 20:45:24 UTC,"Hi, Grey."
1793305,2020-03-18 19:20:46 UTC,Closing because CAN'T REPLICATE; INVALID: may be a support request.
1793305,2018-10-07 11:30:08 UTC,"I can't reproduce that bug, it looks like your shape is rasterized somehow..."
1793305,2018-09-26 21:06:21 UTC,Anyone can give a hand on it?
1793305,2018-10-08 12:29:54 UTC,"Thank, MC! Will try to remove it and install Inkscape once again, never . see that before."
1793307,2020-05-01 20:16:28 UTC,"I accidentally found a solution. I opened konqueror and I right-click on the folder that appears on the top-left corner. I selected ""More Actions"">""Special Application Settings"", then OK to the popup, click on the ""Desktop"" and select ""Do Not Affect""."
1793310,2018-09-19 14:51:24 UTC,"Hi Andrea,"
1793310,2019-09-19 12:06:34 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1793310,2019-09-19 15:50:16 UTC,Reopening as I believe this would still be a useful improvement for MAAS
1793310,2019-09-20 13:26:15 UTC,"This is very much a useful improvement to MAAS. We have been discussions about it for some time. We are moving all feature discussion to discourse (https://discourse.maas.io/c/features). Marking this bug as invalid being that its a feature request, do not worry its not being ignored and currently being discussed."
1793322,2018-12-24 18:21:42 UTC,Reported at https://gitlab.gnome.org/GNOME/gnome-control-center/issues/325
1793322,2018-12-12 12:46:23 UTC,Thank you for your bug report. That is similar to bug #1778596. Could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues
1793323,2018-09-19 14:21:10 UTC,"I wrote a simple test program , it runs fine, I don't know why above error log happened."
1793323,2018-09-20 02:21:03 UTC,"I query MariaDB Database and find nova user has select privilege, and I only changed the password, not privilege."
1793323,2018-09-20 07:44:53 UTC,I have a way you can try:
1793323,2018-09-20 08:09:17 UTC,"I enabled pymysql debug switch and rebooted the control node, the error still is existed."
1793323,2018-09-20 14:21:45 UTC,"I solved my issue and found it was caused by nova cell. after nova cell mapped , the transport url and connection string has been fixed though you changed the nova database password, so we need to change cell's configuration"
1793323,2018-09-21 09:13:42 UTC,It would be good for kolla-ansible to provide some documentation for day 2 operations tasks such as changing passwords.
1793323,2018-09-24 16:49:07 UTC,"Mark, we should have documentation for this but I think you also may want to know about the manual installation. It's easy to change the database password."
1793323,2018-09-25 00:18:36 UTC,"No,  In fact I want to change the password on production evionment,  the
setup in this case is only my test bed for this task."
1793326,2019-09-17 09:52:00 UTC,Migrated to https://github.com/widelands/widelands/issues/1713
1793326,2018-09-28 09:53:54 UTC,"Since WL states it supports S2 maps, I would suggest the solution that a port can be built in any case if it is a port space, regardless of the size of the plot. If it is only medium-sized, there can be built only up to medium-sized buildings and a port, but no other big-sized buildings. This would give compatibility."
1793326,2018-09-28 06:01:34 UTC,"The problem is that the plots for the port spaces are only medium-size plots, but we need big plots to fit a port space."
1793328,2018-09-19 14:41:13 UTC,"This could be very noisy on a cloud if enabled by default.  Suggest we might want to make it a disabled option by default, but allow for it to be enabled as needed on smaller deploys of the charm, such as nrpe-lxd-service-checks that could get related to something like landscape, nagios, graylog.  Or perhaps this could be builtin to the nagios charm itself."
1793328,2018-09-19 14:55:09 UTC,"This is already part of openstack-service-checks.  May be invalid for these charms, but should be considered for future nagios charm, as openstack-service-checks should be upstreamed into each individual service's checks eventually."
1793329,2019-07-25 21:46:57 UTC,"If this yielded a tangible benefit, it might be interesting.  But I don't see the inherent upside (I may just be slow here)"
1793329,2019-07-25 19:51:57 UTC,"PLD linux carries a patch which uses a ""naked"" function instead of a toplevel asm function to allow the compiler to properly track the function."
1793329,2019-07-25 19:18:06 UTC,Sounds good.  Patch pushed to master and 5.1.  Thank you Stefan!
1793329,2019-07-25 19:17:40 UTC,"Fixed in revision e58d9606ddceb3cfd757fd3e203b2f974d566bd0
https://git.launchpad.net/kicad/patch/?id=e58d9606ddceb3cfd757fd3e203b2f974d566bd0"
1793329,2019-07-25 17:53:18 UTC,Thanks JP!
1793329,2019-07-25 17:40:58 UTC,"No problem to compile on W7 32 bits / mingw.
I made a fast test, and did not found issues."
1793329,2019-07-25 15:56:52 UTC,"Thanks.  This compiles without error under Ubuntu 16.04, 18.04 and Debian Buster using both clang and gcc."
1793329,2019-07-25 13:22:42 UTC,Sure! Here's a patch that applies to the current head.
1793329,2019-07-25 18:38:33 UTC,"@Seth, I just completed a 64 bit build and quick test on windows without any issues so I don't see any reason not to merge this patch.  We probably should cherry-pick this to the 5.1 branch."
1793329,2018-09-19 20:06:14 UTC,I updated the formatting to match the rest of the file and added a comment with a short explanation for why the code is there.
1793329,2018-09-19 15:35:24 UTC,"While this makes sense, I've never seen an error while compiling this.  Is it system-specific?"
1793329,2018-09-19 15:43:41 UTC,Please add more info about the reasoning behind this. To me to looks like a hack.
1793329,2018-09-19 15:52:04 UTC,"FYI, I think this is suggested here:
https://gcc.gnu.org/wiki/LinkTimeOptimizationFAQ"
1793329,2018-09-19 15:55:40 UTC,"I would rather not add optimization flags to our configuration and leave that up to the person building KiCad.  I'm guessing most linux package devs would agree with this.  It should be easy enough to pass this compiler flag on the command line.  As it is, this compiler flag is gcc specific and may cause issues with other compilers."
1793329,2019-07-24 18:39:30 UTC,@Stefan can you rebase this patch?  It no longer applies cleanly to master.
1793329,2018-09-19 16:34:14 UTC,My rebuild without the patch just came to a halt at the error message related to this. Several similar instances follow.
1793329,2018-09-19 16:43:30 UTC,Some further background / results:
1793329,2018-09-19 17:06:43 UTC,"I would be willing to accept your second patch as long as we do some due diligence and thoroughly test this on every build platform we support to make sure it doesn't cause grief elsewhere.  Also, please note the coding style of the cmake file you are modifying.  While we do not have an official cmake coding policy, our cmake files try to follow the c coding policy as closely as possible."
1793329,2018-09-19 16:17:48 UTC,GCC and Clang: https://llvm.org/docs/LinkTimeOptimization.html
1793330,2018-09-19 23:55:05 UTC,*** This is an automated message ***
1793334,2020-11-12 08:51:35 UTC,"I wonder whether this might be an upstream bug. Would you be able to test with chrome (get it from https://www.google.com/chrome/) and see if it's similarly affected? If it is, could you please file a bug at https://bugs.chromium.org/p/chromium/issues/list and share the link to it here?"
1793334,2020-12-16 14:46:42 UTC,I just tested it with this version of Chrome on Ubuntu 20.04.1 LTS
1793334,2019-07-13 00:07:57 UTC,"Even worse, using Ubuntu 18.04, there is no option to change the sink per application in the audio control panel anymore."
1793334,2020-11-10 19:59:03 UTC,"I've got the same bug on Ubuntu 20.04 with Chromium 86.0.4240.183 when using Teams. Every time I call someone or someone calls me it switches source and sink to my internal laptop microphone and speakers. Then I have to go to the sound settings where it still shows my headphones as source and sink, and I need to switch to internal sink/source and back to headphones to make it work. It's really annoying.
Why is chromium even allowed to change my pulseaudio settings?"
1793334,2018-09-20 15:43:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793336,2018-09-19 15:51:06 UTC,"Hi Konrad, thanks for the bug report."
1793337,2018-09-19 15:52:19 UTC,"Hi Konrad - I think this should be a heat bug and not heat-translator.  Heat-translator can only generate the HOT template, it is not responsible for implementing the template itself."
1793339,2018-09-19 17:08:48 UTC,Checked on BusyBox 1.1.2 which DOES allow fractional sleep durations. Please ignore this report.
1793341,2019-02-23 10:13:10 UTC,"Major issues appearing when importing qif files have been solved recently
https://bugs.kde.org/show_bug.cgi?id=397824
https://bugs.kde.org/show_bug.cgi?id=403565"
1793341,2020-03-15 07:55:11 UTC,"I've just come across this bug whilst hunting for assistance with the scheduled transaction bug. Having failed to find the build anywhere and with dependency issues for the usual suspects I've built it on a PPA using the Debian stable code with no changes. Just noting here in case it is of use to anyone given the ""no rolling release"" policy.
https://launchpad.net/~bellalistair/+archive/ubuntu/kmymoney/"
1793341,2019-02-23 10:00:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793347,2019-03-13 02:27:58 UTC,"This just hit me today too, fortunately this came up quickly on Google. :)
I definitely do think it's up to Keystone to fix this in their rocky requirements..."
1793347,2019-04-04 14:19:09 UTC,This issue was fixed in the openstack/keystone 14.1.0 release.
1793347,2019-03-19 15:29:56 UTC,"Reviewed:  https://review.openstack.org/599447
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=64c6c481ef45df1633535fbf9ece404a4f5d0dd1
Submitter: Zuul
Branch:    stable/rocky"
1793347,2019-03-18 13:41:35 UTC,"Change abandoned by Colleen Murphy (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/643021
Reason: I just noticed we already have https://review.openstack.org/599447 - we should fix up that one instead."
1793347,2019-03-13 11:48:51 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/643021"
1793347,2019-03-13 02:34:16 UTC,"Actually, I'd also like to point out that ROCKY isn't present until 3.38.0, which I think the packagers above figured out and used 3.39.0 instead."
1793347,2018-10-25 13:57:37 UTC,"Morgan, that's not true, we've switched to managing our own requirements:"
1793347,2018-10-10 13:10:41 UTC,"Hi sunguangning,"
1793347,2018-10-10 12:15:54 UTC,There are the same question in centos7.4 when use kolla-ansible to deploy openstack rocky
1793347,2018-09-26 20:44:31 UTC,"This bug was fixed in the package keystone - 2:14.0.0-0ubuntu2~cloud0
---------------"
1793347,2018-09-20 20:41:34 UTC,This bug was fixed in the package keystone - 2:14.0.0-0ubuntu2
1793347,2018-09-20 09:23:32 UTC,Thanks very much for reporting this Tobias. I will have a fix coming for the Ubuntu package. We use apt dist-upgrade in our upgrade tests which won't uncover this.
1793347,2018-10-24 18:04:05 UTC,"This isn't something Keystone directly has control over, what is in our requirements/g-r is what we ship with. Marking as invalid for keystone server."
1793350,2020-02-14 17:15:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793351,2018-09-19 17:37:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/603855"
1793351,2018-09-24 06:21:30 UTC,"Change abandoned by David Rabel (<email address hidden>) on branch: master
Review: https://review.openstack.org/603855"
1793354,2018-09-20 01:02:14 UTC,I'll have a look to see if it can be dealt with.
1793354,2018-09-20 07:10:28 UTC,"ovs friendly clears up flows when a controller is set up.
See ovs/ofproto/connmgr.c:connmgr_set_controllers."
1793354,2018-09-20 21:13:28 UTC,"I can confirm that packet loss occurred by following the reproducing steps, but not sure if neutron should deal with it as @IWAMOTO Toshihiro mentioned."
1793354,2018-09-20 21:54:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/604228"
1793354,2019-12-04 08:33:07 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/604228
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns."
1793355,2019-11-15 17:32:00 UTC,Moved:
1793358,2019-04-18 18:41:40 UTC,I am facing same issue. Anybody has any updates on this issue about how to fix it?
1793360,2018-09-19 19:14:18 UTC,"I see this quite often and it worsens if you have more than one building, cause the upgraded soldier will knock on the door of each of the military buildings where you have cahnged the settings to prefer rookies."
1793360,2018-09-19 20:25:25 UTC,Thats true and could prevent soldiers going fast to the frontier where the enemy is nearby.
1793360,2018-09-21 20:24:14 UTC,"I think this observation might be related:
Assume you have no soldiers in warehouses, but all militarysites are occupied. You destroy a militarysite, thus freeing a soldier. He starts going to a warehouse. While he´s on the way, a new militarysite is finished and needs a soldier.
Expected behaviour: The soldier should go to the new militarysite.
What I get: He walks to the warehouse, enters, comes straight out again and then goes to the militarysite."
1793360,2018-09-24 08:10:08 UTC,"I guess what happens here is that the economy request for the soldier never gets canceled. Only after reaching the destination, the old request is canceled and the already waiting, new request is fulfilled."
1793360,2018-10-05 08:53:00 UTC,Was done this way to keep it simple. Old requests remain in order.
1793360,2019-09-17 07:59:37 UTC,Migrated to https://github.com/widelands/widelands/issues/1082
1793363,2018-09-19 18:23:20 UTC,"Sono curioso, puoi allegare uno screenshot?"
1793363,2018-09-19 18:38:49 UTC,Eccolo! Ciao vale 😁
1793363,2019-11-12 17:25:37 UTC,Moved:
1793364,2018-09-19 18:39:51 UTC,"The IndexError looks like the killer, and that's probably coming from one of the eventlet parts of the stacktrace where it's reading from a buffer."
1793364,2018-09-19 18:47:28 UTC,We are getting some deprecation warnings for old test fixture usage:
1793364,2018-09-19 18:57:37 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22%20%20connection.scalar(select(%5B1%5D))'%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d
1793364,2018-09-19 18:56:24 UTC,My guess is the IndexError is coming from the this:
1793364,2018-09-20 23:42:16 UTC,"Latching on, we had a similar failure on the manila gate today: http://paste.openstack.org/show/730492/"
1793364,2019-02-08 21:42:43 UTC,I'm seeing something slightly different here:
1793364,2019-03-12 15:22:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642788"
1793364,2019-03-12 16:57:48 UTC,"Reviewed:  https://review.openstack.org/642788
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=79c12f5930ecdbacf33fabcba7dce1f4cb8f72ba
Submitter: Zuul
Branch:    master"
1793364,2019-04-04 20:08:16 UTC,Potentially related bug 1823251 although that bug just started spiking in nova since April 1 2019.
1793368,2018-10-01 13:32:37 UTC,This *looks* like a HA setup where the particular controller machine being communicated with cannot reach MongoDB on another controller machine.
1793370,2018-09-19 19:23:29 UTC,"(2:12:32 PM) mriedem: clarkb: is this a known issue? http://logs.openstack.org/17/595317/1/gate/build-openstack-sphinx-docs/b8849f2/job-output.txt.gz#_2018-09-18_18_33_45_353493
(2:12:42 PM) mriedem: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22rsync%20error%3A%20unexplained%20error%20(code%20255)%20at%5C%22&from=7d
(2:13:40 PM) clarkb: mriedem: I think that is a limestone node (based on ipv6 usage) and I think logan- said he was fixing some stuff there?
(2:13:43 PM) openstackgerrit: Andreas Jaeger proposed openstack-infra/elastic-recheck master: convert docs to PTI  https://review.openstack.org/559396
(2:13:49 PM) clarkb: mriedem: it is odd that it timed out then failed to reconnect
(2:13:50 PM) clarkb: logan-: ^"
1793370,2018-09-28 17:11:16 UTC,Reading through a lot of these cases they are actually failing very early in the pre steps due to broken networking. We then also fail later in the post steps when trying to copy logs as explained in this bug. I think the impact of this issue is actually lower than e-r may imply because failing in pre playbooks like this will cause the job to be retried. There is a cost associated with the retry but it is lower than the cost of failing entirely.
1793370,2018-09-28 20:57:45 UTC,"If we're retrying the job run on this then we could just mark the fingerprint / query in elastic-recheck so it doesn't show up in the graph, i.e. if it's just going to be persistent but not really a problem that needs a lot of attention."
1793377,2018-09-21 13:34:19 UTC,"I would say a better approach, would be to select 2 pads and tell you the trace distance between them, for stuff like DDR memory routing this is more important, and there have been many times I have had to delete segments to isolate a trace to accomplish this so far."
1793377,2018-09-20 22:55:49 UTC,"+1, but what should happen if a T-shaped track (or worse) is selected? Total length for all branches?"
1793377,2018-09-20 23:35:04 UTC,"I think the correct response is that the display shows the length of selected track.  If you have a T, then it is the user's responsibility to only select the section that they care about."
1793377,2018-09-21 14:26:26 UTC,That's a fine idea as well and could be implemented although I think it would need a separate approach.
1793381,2019-12-21 02:11:17 UTC,"Reviewed:  https://review.opendev.org/699420
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=bcba626d3b868457d34aa418eca6b3cf4792356a
Submitter: Zuul
Branch:    stable/queens"
1793381,2019-01-11 16:18:58 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.3.0 release.
1793381,2019-12-17 13:57:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/699420"
1793381,2018-10-01 14:06:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/606958"
1793381,2019-01-03 07:48:03 UTC,"Reviewed:  https://review.openstack.org/606958
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a425a6f1ff1833da0ec5f42c7ca3f9ad952b54bf
Submitter: Zuul
Branch:    master"
1793389,2018-10-25 13:20:06 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/613325"
1793389,2018-11-02 09:30:47 UTC,"Reviewed:  https://review.openstack.org/613321
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=ce0df5355f837dc406e0a94e6fcc6e4c8f1b37e0
Submitter: Zuul
Branch:    stable/rocky"
1793389,2018-10-26 12:45:11 UTC,"Reviewed:  https://review.openstack.org/613325
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=b8798d89f8b5537c58a7d3636c47b3513f06bc64
Submitter: Zuul
Branch:    stable/ocata"
1793389,2018-10-26 13:06:52 UTC,"Reviewed:  https://review.openstack.org/613323
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=0b4eb4162a34d2f9947aca2f9e7f42504b5ba010
Submitter: Zuul
Branch:    stable/pike"
1793389,2018-10-26 20:15:21 UTC,"Reviewed:  https://review.openstack.org/612482
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=03e3e83953218ad3a99c7c239037a94b60313ee7
Submitter: Zuul
Branch:    stable/queens"
1793389,2018-11-01 06:56:40 UTC,https://review.openstack.org/#/c/612686/
1793389,2018-12-12 17:08:36 UTC,We (Keystone) will add the db schema version ID / Number to the cache key generator so that we do an implicit cache pop on schema upgrades.
1793389,2018-10-22 19:07:55 UTC,"Reviewed:  https://review.openstack.org/608066
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=afc0e5b1ce660224593f2f9d1886d45f1c69f174
Submitter: Zuul
Branch:    master"
1793389,2019-03-20 20:47:06 UTC,"Change abandoned by Lance Bragstad (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/612686
Reason: Removing from my work queue for now. If someone has the time to pick this up, please feel free to do so."
1793389,2019-04-12 23:31:23 UTC,This issue was fixed in the openstack/openstack-ansible-os_keystone ocata-em release.
1793389,2019-04-26 17:14:39 UTC,This issue was fixed in the openstack/openstack-ansible-os_keystone 16.0.29 release.
1793389,2019-04-29 06:37:49 UTC,"Change abandoned by Jesse Pretorius (odyssey4me) (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/604845
Reason: This has been replaced by a better solution"
1793389,2019-04-29 06:38:06 UTC,"Change abandoned by Jesse Pretorius (odyssey4me) (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/604846
Reason: This has been replaced by a better solution"
1793389,2019-04-29 06:38:31 UTC,"Change abandoned by Jesse Pretorius (odyssey4me) (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/605148
Reason: This has been replaced by a better solution"
1793389,2018-10-25 13:16:33 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/613323"
1793389,2019-01-28 17:29:37 UTC,Removing myself in case others have more time to pick this up [0].
1793389,2018-10-25 13:13:32 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/613321"
1793389,2018-09-25 16:59:04 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605148"
1793389,2018-10-23 13:02:43 UTC,I proposed a patch to keystone's stable/ocata branch that should help with this.
1793389,2018-09-24 14:36:07 UTC,"Noticing that even on successfull upgrades there are usually a few failed attempts at running the ""Ensure service tenant"" play.  Simply adding more retires should greatly mitigate upgrade failures going forward."
1793389,2018-09-24 14:46:06 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/604804"
1793389,2018-09-24 17:00:46 UTC,"Change abandoned by Alex Redinger (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/604147
Reason: Abandoning for upstream changed here https://review.openstack.org/#/c/604804/"
1793389,2018-09-24 17:00:53 UTC,"Change abandoned by Alex Redinger (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/604144
Reason: Abandoning for upstream changed here https://review.openstack.org/#/c/604804/"
1793389,2018-09-24 17:02:39 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/604845"
1793389,2018-10-25 12:32:50 UTC,"Reviewed:  https://review.openstack.org/613256
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=280f3e062a30ebffdc2986d0b3c20e323486e3da
Submitter: Zuul
Branch:    master"
1793389,2018-09-25 16:58:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605146"
1793389,2018-09-24 17:02:51 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/604846"
1793389,2018-10-04 19:44:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608066"
1793389,2018-10-04 19:48:53 UTC,"Change abandoned by Alex Redinger (<email address hidden>) on branch: master
Review: https://review.openstack.org/605146
Reason: Abandoning in favor of https://review.openstack.org/#/c/608066/"
1793389,2018-10-05 12:48:56 UTC,"Change abandoned by Alex Redinger (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/604804"
1793389,2018-10-22 19:31:35 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/612482"
1793390,2018-09-19 21:09:33 UTC,"second install , trying to get cuda 9.2 install working"
1793400,2019-06-18 18:26:35 UTC,"Thanks for testing, marking as verified then."
1793400,2019-06-25 22:10:46 UTC,Screenshot is attached
1793400,2019-06-25 20:16:36 UTC,The SRU team needs some more information about the verification process before we feel comfortable releasing it. A screenshot showing the translations and the version of the package installed would help.
1793400,2019-06-25 22:54:28 UTC,This bug was fixed in the package kazam - 1.4.5-2.1ubuntu0.1
1793400,2019-06-18 18:08:59 UTC,It works
1793400,2019-06-18 16:58:36 UTC,"Hello Mikhail, or anyone else affected,"
1793400,2019-06-08 18:38:54 UTC,This bug was fixed in the package kazam - 1.4.5-3
1793400,2019-06-01 20:21:58 UTC,"The attachment ""kazam-1.4.5-setlocale.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1793400,2018-09-19 21:52:51 UTC,This is a screenshot of Kazam in Russian before and after the patch.
1793400,2019-06-25 22:54:32 UTC,"The verification of the Stable Release Update for kazam has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1793406,2018-11-03 07:27:19 UTC,Same under tranditional Chinese language.
1793406,2018-09-26 14:07:42 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1793406,2018-09-23 00:33:06 UTC,"I've just looked at many launchers in MenuLibre and I can confirm what tehkos wrote, seems like this problem occurs specifically when there's a ""Polish specific"" (in my case) letter with diacritic mark in the name and/or description, so ""ę, ó, ą, ś, ł, ż, ź, ć, ń""."
1793406,2018-09-22 23:07:44 UTC,"Same in russian localization
Look at screenshot.
Instead of ""Веб-браузер"" there is only ""Веб-бр"".
And instead of ""Смотреть в интернете"" there is only ""Смотреть в"".
All applications with non-latin characters have such reduced titles."
1793408,2018-09-19 23:09:15 UTC,"Digging through the Answers backlog, I found a question that was solved back in 2016:"
1793408,2018-09-20 07:27:10 UTC,"If you run this script in an undefined tab (not yet saved), you first get the script-save dialog."
1793408,2018-09-20 16:45:53 UTC,"Hi RaiMan,"
1793408,2018-09-21 15:06:18 UTC,thanks for testing. I will look into it again.
1793408,2018-09-21 17:33:50 UTC,please test with the latest build from today
1793408,2018-09-21 21:28:06 UTC,Tested against 1.1.4(2018-09-21-17:33)
1793410,2020-04-20 09:33:16 UTC,The same issue on Acer Swift 5F314-56 model N17W7 with Realtek ALC256 chip (HDA-Intel - HDA Intel PCH sound card).
1793410,2019-10-22 18:04:46 UTC,The response was “The MIC is bulit into the in mainboard of the unit.” Does that help? Happy to ask again if that still doesn’t answer your question.
1793410,2019-10-16 22:04:55 UTC,"not asking if the codec directly connects to DSP, please ask if internal mic connects to DSP or codec?"
1793410,2019-10-16 11:52:30 UTC,"The response from Acer was that ""the realtek codec is directly connected to the DSP"". Is there anything else I should ask them?"
1793410,2019-10-13 03:02:27 UTC,Could you ask the Acer what is the hardware design for the internal mic on this machine? Does the internal mic connect to the realtek codec or directly connect to the DSP in the PCH?
1793410,2019-10-12 22:48:50 UTC,"Hello there, this bug also affected me even though the Product model is a bit different.
My laptop model is Acer Swift 3 SF314-56G which also use Realtek ALC256 (HDA-Intel - HDA Intel PCH)
I use the fresh install of Ubuntu 19.04 with 5.0.0-31-generic kernel version. Is there any solutions or steps I need to take to make the microphone works?
Both internal and external microphone is not working at all."
1793410,2018-12-17 14:07:28 UTC,"Sorry you are right. I'm not really familiar with alsa much but triaged a few similar issues recently and tried to help a bit. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/sound/pci/hda/patch_realtek.c has mention of hacks with the ALC256 but for asus configs, unsure they would adapt well."
1793410,2018-12-07 14:43:44 UTC,Could be that it requires an hack similar to https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=b72f936f with your ids being 1025:1269
1793410,2018-12-09 15:23:45 UTC,It's just adding that line in the right place in your patch_realtek.c and rebuilding
1793410,2018-12-08 13:30:00 UTC,"Hi Sebastien,"
1793410,2019-10-29 10:45:11 UTC,"the same issue here with
Swift 314-54"
1793410,2018-09-24 23:09:53 UTC,Hello I have the same issue. I tried for a couple days to fix it without any results. I have the latest drivers installed (https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS). I then tried to set all configurations to default and ran alsa-info. The ouput is located at the following url and in the attached text document. I hope this is helpful.
1793410,2018-09-24 22:50:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793410,2018-12-16 23:59:19 UTC,"Hi Sebastien,"
1793411,2019-10-27 10:28:42 UTC,"hi @deshipu,"
1793411,2018-09-25 04:11:25 UTC,"I just did a quick bit of testing to see what functions don't have any weakrefs and therefore can't be cleaned up:
http://paste.openstack.org/show/730680/"
1793411,2019-03-21 08:30:38 UTC,This should be fixed by https://review.openstack.org/c/614893/
1793416,2018-09-20 13:48:25 UTC,"Thinking about a little more, when we have multi-cells, we should have nova-novncproxy service instance for each cell, and have each instance has its own endpoint (novncproxy_base_url). I think it might be an issue how Devstack deploys this use case, this report maybe should be against devstack project."
1793418,2019-01-03 08:10:09 UTC,"I'm using Magnum rocky release (installed from source code https://github.com/openstack/magnum/tree/stable/rocky) and Fedora Atomic 27, my k8s cluster has exactly the same problem. Please help suggest a solution to this problem other than manually creating a ""/etc/kubernetes/cloud-config"" file or adding the ""--cloud-config=/etc/kubernetes/kube_openstack_config --cloud-provider=openstack"" parameters to processes of kube-controller-manager and kube-apiserver. Or did I miss any configuration for Magnum or my k8s cluster?
Thanks!"
1793418,2019-01-10 01:32:38 UTC,"Btw, the version of Magnum I'm using is 7.0.3.dev1 (from source code https://github.com/openstack/magnum/tree/stable/rocky)."
1793418,2019-01-14 08:03:42 UTC,"More update:
I met this issue in the testing of following scenarios:
* Magnum Rocky 7.0.3.dev1 + Fedora-Atomic-27-20180419.0
* Magnum Rocky 7.0.2 + Fedora-Atomic-27-20180419.0
* Magnum Rocky 7.0.2 + Fedora-Atomic-28-20180806.0"
1793418,2019-01-22 13:15:15 UTC,"We are running this version of magnum:
# /openstack/venvs/magnum-18.1.0/bin/pip show magnum
Name: magnum
Version: 7.0.2.dev21"
1793419,2019-03-22 03:47:05 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1793419,2018-11-30 22:27:32 UTC,"Reviewed:  https://review.openstack.org/610974
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=164b1ba301f580edbfa5a52a80b51f49f2a28fea
Submitter: Zuul
Branch:    stable/queens"
1793419,2018-11-06 06:01:16 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1793419,2018-10-17 14:52:28 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/611343"
1793419,2018-10-16 13:42:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/610974"
1793419,2018-10-16 08:13:45 UTC,"Reviewed:  https://review.openstack.org/608572
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=57b46754ff67c52c49e10d3ae176515cdcda30e3
Submitter: Zuul
Branch:    stable/rocky"
1793419,2018-10-08 05:38:34 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/608572"
1793419,2018-09-22 16:52:40 UTC,"BTW, this is the change that started deleting request_specs when archiving deleted instances:"
1793419,2018-09-25 18:16:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605164"
1793419,2018-12-19 20:48:20 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1793419,2018-09-22 16:48:58 UTC,"OK I think I see, _get_marker_for_migrate_instances returns the marker because there is still a request_specs table entry with the marker instance_uuid (because we didn't used to clean up request specs on db archive/purge - but now we do). So when listing instances we passed a marker to an instance which wasn't found, and that raised MarkerNotFound and failed."
1793419,2018-09-22 16:47:01 UTC,"Do you have more details from the failure? If the marker instance was deleted, I'd expect the migration to just start over from the beginning."
1793419,2018-09-22 16:45:28 UTC,"> In our upgrade test, we hit a scenario where the marker instance from the online migration that was run during the Mitaka->Newton upgrade had been deleted and purged from the db
"
1793419,2019-04-26 17:16:31 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1793419,2018-10-05 03:14:19 UTC,"Reviewed:  https://review.openstack.org/605164
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ff03b157b930de23e5912802cbfbc86889c869c2
Submitter: Zuul
Branch:    master"
1793419,2019-03-15 23:53:00 UTC,"Reviewed:  https://review.openstack.org/611343
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=456e5439f58967fc03c7c13e11fe0e15bea84486
Submitter: Zuul
Branch:    stable/pike"
1793427,2019-01-30 15:57:45 UTC,I've had this happen to me with Ubuntu 18.10 as well.
1793427,2020-03-18 19:48:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793427,2020-03-18 19:45:28 UTC,I've the same problem with a L2TP VPN.  This still happens on Ubuntu 19.10.
1793427,2019-01-30 15:16:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793427,2018-12-13 23:08:59 UTC,This might be a duplicate of: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946
1793427,2018-12-13 22:42:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793427,2018-12-13 22:42:27 UTC,I have a very similar problem when using a PPTP VPN.
1793432,2018-10-09 12:59:42 UTC,"Processing triggers for linux-image-4.15.0-33-generic (4.15.0-33.36) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-33-generic
cp: failed to restore the default file creation context: Invalid argument
E: /usr/share/initramfs-tools/hooks/kmod failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-33-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.15.0-33-generic (--configure):
 installed linux-image-4.15.0-33-generic package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for linux-image-4.15.0-34-generic (4.15.0-34.37) ...
/etc/kernel/postinst.d/dkms:
Error! Your kernel headers for kernel 4.15.0-34-generic cannot be found.
Please install the linux-headers-4.15.0-34-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic
cp: failed to restore the default file creation context: Invalid argument
E: /usr/share/initramfs-tools/hooks/kmod failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-34-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.15.0-34-generic (--configure):
 installed linux-image-4.15.0-34-generic package post-installation script subprocess returned error exit status 1
Processing triggers for initramfs-tools (0.130ubuntu3.3) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-32-generic
cp: failed to restore the default file creation context: Invalid argument
E: /usr/share/initramfs-tools/hooks/kmod failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-32-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1"
1793433,2018-10-09 12:39:54 UTC,"Processing triggers for linux-image-4.15.0-33-generic (4.15.0-33.36) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-33-generic
cp: failed to restore the default file creation context: Invalid argument
E: /usr/share/initramfs-tools/hooks/kmod failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-33-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-4.15.0-33-generic (--configure):
 installed linux-image-4.15.0-33-generic package post-installation script subprocess returned error exit status 1"
1793433,2018-12-05 13:59:41 UTC,"I was able to workaround this problem by following Mauricio Grueso's suggestion in bug #1776652:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1776652"
1793437,2018-09-20 09:39:20 UTC,"This behaviour is caused by the ""apt"" program, not by RedNotebook."
1793437,2018-09-20 11:05:38 UTC,"We do not care about the case of the expression, so both y and Y do work. Are you sure there has not been any other input before the Y like a space?"
1793437,2018-09-20 11:46:45 UTC,I've edited the question. Thanks @juliank for the comment. It was possibly a white space character there!
1793444,2018-10-03 08:59:46 UTC,"Hi Stephane,"
1793444,2021-01-17 15:11:09 UTC,"@brian-murray,"
1793444,2021-01-11 08:20:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793444,2018-09-21 03:25:54 UTC,Given mdadm as Recommends in debian/control
1793444,2019-01-18 16:18:49 UTC,This is just a friendly reminder that the 18.04.2 point release is coming up shortly if you want to get this in for that.
1793444,2018-09-20 07:19:55 UTC,"Please also make casper depend on or recommend mdadm for this issue.
This issue is after LP: #1779685."
1793444,2018-09-20 08:58:19 UTC,"The attachment ""add-md-support.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1793450,2018-09-20 06:53:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/603999"
1793450,2018-11-11 07:20:46 UTC,"Reviewed:  https://review.openstack.org/603999
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=e304ca37710e8b382954d1594e7bae52df9f414f
Submitter: Zuul
Branch:    master"
1793454,2018-09-20 07:03:24 UTC,https://github.com/mixxxdj/mixxx/pull/1812
1793459,2018-10-10 08:16:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793460,2018-09-20 11:47:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604067"
1793461,2018-10-22 16:31:21 UTC,This bug was fixed in the package linux - 4.4.0-138.164
1793461,2018-10-22 15:58:43 UTC,This bug was fixed in the package linux - 4.15.0-38.41
1793461,2018-10-22 15:58:04 UTC,This bug was fixed in the package linux - 3.13.0-161.211
1793461,2018-10-12 13:48:54 UTC,This bug was fixed in the package linux - 4.18.0-9.10
1793461,2018-10-12 13:30:44 UTC,"New 'startnewrelease' target used for all Trusty, Xenial and Bionic backports this cycle. Worked as expected."
1793461,2018-10-03 17:33:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1793461,2018-10-04 10:05:20 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1793461,2018-09-20 07:30:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1793461,2018-10-04 11:02:11 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1793465,2018-12-03 19:11:37 UTC,"I also have this problem on the Fedora 28 Mate Spin (I hope it's okay to put that here). I routinely set the clock to show the seconds and that really uses up the memory. Note that with absolutely nothing ""refreshing"" the screen there is still some leakage. I have been using Fedora since version 3 and I have never seen this before. For example, I have a Fedora 27 Mate laptop that has been running for 381 days, no leaks of any kind."
1793465,2020-08-17 18:30:35 UTC,Fixed via mate-panel 1.24.1-0ubuntu1 in Ubuntu Groovy.
1793465,2020-08-31 11:45:24 UTC,"I can also confirm that on my Ubuntu MATE 20.04, if the system is not rebooted for days then there is an astronomical amount of usage of the CPU, RAM as well as the SWAP memory."
1793465,2019-04-26 15:08:48 UTC,"Not sure if this helps anyone here but thought I should follow up. This memory leak issue appears to have been fixed* on the Fedora 30 Mate Spin Beta (mate-panel-1.22.0-3.fc30.x86_64). It's only been up for 4 days, however, mate-panel started at 0.5 memory usage and has not changed at all.
I am running the clock with seconds, the System Monitor, and everything else I can think of to try and see the leak again and it's not happening. I expect to see uptimes of 400+ days again, yay!"
1793465,2018-10-25 12:18:32 UTC,I'll try to verify this
1793465,2020-08-29 04:38:20 UTC,"This is appreciated, Martin."
1793465,2018-10-24 08:05:33 UTC,"I can confirm, in 18.04"
1793465,2018-10-24 07:58:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793465,2018-10-25 11:56:03 UTC,"I've found what causes this bug in my case - mate-netspeed-applet. If I remove it from panel, this issue does not occur."
1793468,2018-09-20 08:16:36 UTC,It's intermintent issue
1793468,2018-09-20 08:23:32 UTC,"http://logs.openstack.org/45/560445/144/check/tripleo-ci-centos-7-containers-multinode-queens/dcb313c/logs/undercloud/home/zuul/overcloud_prep_containers.log.txt.gz#_2018-09-19_23_07_47
2018-09-19 23:07:47 | 2018-09-19 23:07:47,010 INFO:
2018-09-19 23:07:47 | 2018-09-19 23:07:47,010 ERROR: Failed running yum update for 192.168.24.1:8787/tripleoqueens/centos-binary-horizon:current-tripleo; try number 2
2018-09-19 23:07:47 | 2018-09-19 23:07:47,010 ERROR: /usr/bin/docker-current: Error response from daemon: grpc: the connection is unavailable.
2018-09-19 23:07:47 | time=""2018-09-19T23:07:47Z"" level=error msg=""error getting events from daemon: net/http: request canceled"""
1793469,2018-09-27 12:37:01 UTC,From VarLogDistupgradeMainlog.txt:
1793472,2021-01-20 09:15:13 UTC,Intel VROC (Intel Virtual RAID on CPU) needs mdadm to install on it per OEM test result.
1793473,2020-07-08 12:28:45 UTC,"Haven't pin-pointed exactly when the change was synced/merged from Debian, but in newer Ubuntu releases (at least 19.10 and later), xdg-desktop-portal-kde is indeed providing xdg-desktop-portal. (https://packages.ubuntu.com/eoan/xdg-desktop-portal-backend) Based on this, I'm marking this fix released."
1793473,2018-09-20 20:51:41 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1793473,2018-09-22 14:44:42 UTC,"Looks like there's already a request in Debian for this package to provide xdg-desktop-portal-backend, see the attached bug watch."
1793473,2018-09-22 16:27:59 UTC,"@hjd, Thanks for pointing this out, I hadn't spotted this."
1793473,2018-09-22 18:07:22 UTC,"As this affects xdg-desktop-portal-kde, I'm going to mark flatpak as invalid."
1793486,2018-09-27 12:52:12 UTC,Hook execution should be shown in the status output as they're triggered.
1793488,2020-01-10 15:03:03 UTC,Fixed with https://review.opendev.org/#/c/677580/3
1793488,2020-01-10 15:04:26 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.opendev.org/663603"
1793503,2018-09-23 12:19:53 UTC,"Hi,
We had installed the 3.18.7 build in Ubuntu 18.04 and didn't see this error. Python Imaging is Optional package for hplip installation and hence the installation continued. Did you see any issues in print/scan using hplip after installation?"
1793503,2018-09-24 09:38:00 UTC,"It's true, python-imaging package is optional, and installation completes fine once you skip the  installation of this package."
1793504,2018-09-24 05:25:41 UTC,"Hi,"
1793504,2018-09-24 09:33:39 UTC,"thanks for your answer,
The printer is connected to our network, and I can't connect it via USB at the moment, since it's used by others."
1793504,2018-09-24 09:39:57 UTC,Here's the output from hp-check command:
1793511,2018-09-27 12:50:57 UTC,"Thanks, updating to ping wallyworld on the plans/expectations there."
1793513,2018-09-21 17:40:13 UTC,"OK, reproduced (I only tought of re-testing after closing...)"
1793513,2018-09-21 17:49:06 UTC,This seems to be https://gitlab.com/gitlab-org/gitlab-ce/issues/45697
1793513,2019-06-16 16:36:45 UTC,As https://gitlab.com/gitlab-org/gitlab-ce/issues/45697 is not really our issue and I wouldn't know how to work around it I'll close this for now.
1793513,2018-09-21 18:55:33 UTC,"Thanks for investigating and also fixing the depth, Patrick!"
1793513,2018-09-21 17:37:43 UTC,">  Getting merge conflicts in inkscape-web-i18n
"
1793513,2018-09-20 15:39:40 UTC,"Hmm, can you open the link manually from within a browser?"
1793513,2018-09-20 20:33:16 UTC,Mmh. Getting merge conflicts in inkscape-web-i18n... meh.
1793513,2018-09-20 20:20:58 UTC,"Yes, seems to work again in the browser (it didn't previously) - now I'm running make, to try out your fixes for the other issue :)"
1793513,2018-09-20 20:47:34 UTC,"Deleted the old website-i18n repo, and ran make again (thanks for cloning the git repos automatically now!) - worked!"
1793514,2019-01-31 21:16:25 UTC,"Per #4, he was trying to upgrade using the selected ""controller"" model."
1793514,2019-01-31 14:19:55 UTC,"I think the issue is that you have to upgrade the controller first, which
is currently ""juju upgrade-juju -m controller"", and *then* you can upgrade
individual model agents (juju upgrade-model)."
1793514,2019-01-31 03:40:53 UTC,"It doesn't seem obvious from earlier updates to this ticket, but this occurs when the streams.canonical.com metadata differs from the cache in the local OpenStack cloud.  This bug occurs when the local cloud's syncing is broken but the controller can reach streams.c.c and see that there is an update available.  What appears to be happening is that juju status is using only the presence of new versions in streams.c.c as a flag, whereas juju upgrade-juju is using streams.c.c plus the local cache."
1793514,2019-01-28 04:17:38 UTC,[Expired for juju because there has been no activity for 60 days.]
1793514,2018-11-15 16:30:41 UTC,I am unable to reproduce with 2.4.1.  I tried 2.4.4 as well.
1793514,2018-09-28 08:57:10 UTC,"So to clarify - this happened for the _controller_ model. Juju status says:
$ juju status
Model Controller Cloud/Region Version SLA Timestamp Notes
controller canonistack-lcy01 canonistack/lcy01 2.4.1 unsupported"
1793514,2018-09-27 13:57:42 UTC,"Ok, at the start then I would update so that we don't output that a model can be upgraded unless the controller is at that version as well."
1793514,2018-09-27 13:26:53 UTC,"This looks like something where we know there is an upgrade available, but
you have to upgrade the controller model before you can upgrade another
model.
 $ juju upgrade-model -m controller
then you can
 $ juju upgrade-model
In the other models."
1793514,2018-09-27 12:49:32 UTC,Can you provide more details on the setup.
1793516,2018-09-21 08:23:06 UTC,"hey,bonden"
1793516,2018-09-21 18:58:46 UTC,"As already mentioned in comment #7, this is reproducible with queens."
1793516,2018-09-21 01:41:55 UTC,"cat create_delete_network.sh
--------------------------------
#!/usr/bin/bash"
1793516,2018-09-21 01:37:21 UTC,"check the DB logs, to see whether there are some DB deadlock info.and check the conf of DB about deadlock."
1793516,2018-09-20 17:10:49 UTC,"I have not been able to reproduce this with devstack master/queens using the suggestions in comment #3. I've tried both approaches multiple times, but can't find any deadlock errors."
1793516,2018-09-21 20:57:37 UTC,"I've been trying to reproduce on stable/rocky, but am running into other issues."
1793516,2018-09-20 12:24:30 UTC,"Is this issue easy enough to reproduce?
If so can you please provide the steps used to create the error?"
1793516,2018-09-20 12:22:10 UTC,"I switch the order ,delete ipamsubnet first, delete subnet later.it seems to solve the issue.
but there's another deadlock between standardattributes and ml2_port_bindings when delete network."
1793516,2018-09-20 13:03:57 UTC,it is easy to reproduce.
1793530,2018-09-20 16:31:17 UTC,"not sure what is meant by the phrase:
"" DXF file containing many thousands of tiny entities"""
1793530,2018-09-20 21:52:27 UTC,Inkscape extension bugs should now be reported to the Inkscape-extensions repository issues tracker. This is to make it easier to fix issues for each of the parts of Inkscape (plus we've been rewriting a lot of code and could do with more eyes on the new code)
1793530,2018-09-21 10:51:27 UTC,Alright; I've reported it over at https://gitlab.com/inkscape/extensions/issues/12
1793533,2019-03-22 03:47:35 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1793533,2018-10-08 21:50:46 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1793533,2018-10-08 21:49:13 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1793533,2018-10-08 21:45:33 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1793533,2018-10-08 20:53:40 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1793533,2018-10-02 21:30:23 UTC,"Reviewed:  https://review.openstack.org/604451
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=81fe10ffbce67977577e04c72cd48bdf9b0e498c
Submitter: Zuul
Branch:    stable/ocata"
1793533,2018-10-02 03:22:25 UTC,"Reviewed:  https://review.openstack.org/604449
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=976e52a49c7b43a5bb9ba86bf7970bf7185ef285
Submitter: Zuul
Branch:    stable/pike"
1793533,2018-09-25 09:35:42 UTC,"Reviewed:  https://review.openstack.org/604448
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d01336a332a4080f26ac70d131ecf3ed66e129a9
Submitter: Zuul
Branch:    stable/queens"
1793533,2018-09-22 01:19:13 UTC,"Reviewed:  https://review.openstack.org/604367
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=518fdc7a22dd3dabbc9dd032e816e0aecdd75150
Submitter: Zuul
Branch:    stable/rocky"
1793533,2018-09-21 18:52:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/604451"
1793533,2018-09-21 13:48:18 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604367"
1793533,2018-09-21 18:47:23 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/604448"
1793533,2018-09-21 12:59:51 UTC,"Reviewed:  https://review.openstack.org/604108
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=37f3444c32ccb72076a1a6549c183f40c33fe684
Submitter: Zuul
Branch:    master"
1793533,2018-09-20 14:37:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604108"
1793533,2018-09-20 13:47:45 UTC,The related issue is that the scheduler was not filtering out deleted compute node records when pulling them from the cell DB:
1793533,2018-09-20 13:44:43 UTC,Sounds like this was a duplicate of bug 1756179.
1793533,2018-09-20 13:34:13 UTC,Are you sure you're stopping the nova-compute service before deleting the actual service record via the API?
1793533,2018-09-21 18:48:13 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/604449"
1793539,2020-08-10 18:37:46 UTC,As you can see in the build log the package builds sucessfully.
1793539,2020-08-10 15:25:13 UTC,"Actually more likely https://github.com/vivier/qemu-m68k/issues/33, in which case it's also fixed.."
1793539,2020-08-10 15:23:11 UTC,"Possibly duplicate of bug #1594394, in which case it would be worth testing with 5.0.0 or above.."
1793540,2019-09-04 12:18:41 UTC,"3.2.1 Wed, Sep  4, 2019
 * Add support for setting timeout for convenience methods in DNS.lazy
 * Fixed DNS.req resulttype error format (LP: #1842423)
 * Use errno.EADDRINUSE instead of the hard coded Linux value for improved
   portability (LP: #1793540)
 * Update test suite to correct for use of no longer existing DNS records
 * Set timeout=1 for tests so testing with a non-responsive nameserver will
   finish in a reasonable time"
1793542,2018-09-20 22:55:57 UTC,"> all the FX outputs are routed directly to the master output
"
1793542,2018-09-21 12:36:19 UTC,"Yes, I quite agree that option B would be a better way to go, but maybe A is easier and quicker to implement. Or maybe not."
1793555,2018-09-20 15:42:37 UTC,Seems to be related to https://github.com/systemd/systemd/pull/7403 which isn't merged still.
1793555,2018-09-26 14:38:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793555,2018-11-30 07:36:56 UTC,This issue has been fixed upstream: https://github.com/systemd/systemd/pull/10597
1793555,2020-04-14 10:18:13 UTC,This appears to be fixed in the latest version of systemd for Bionic and later.
1793556,2019-03-13 00:42:09 UTC,"Reviewed:  https://review.openstack.org/640771
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4ede35281160b8d988ef5b775b97d81950d0c6e1
Submitter: Zuul
Branch:    stable/rocky"
1793556,2018-09-21 17:24:54 UTC,"Reviewed:  https://review.openstack.org/602127
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9d5fb1b58e908ccacbbbf29341918d0b0588a36f
Submitter: Zuul
Branch:    master"
1793556,2019-03-04 14:24:57 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640771"
1793556,2019-03-24 23:39:18 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1793556,2019-03-22 03:47:33 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1793561,2018-09-20 16:20:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604151"
1793561,2019-03-11 09:13:55 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.openstack.org/604151"
1793569,2018-09-20 17:23:20 UTC,"Somewhat related to this, some folks @vmware are making a script that talks to the database directly for some ""placement audit"" needs. Mostly because that's SOP for them and doesn't require dealing with tokens and such. I include it here as an example in case it is useful. This version is oriented towards a pre-nested world, mostly ocata, but sometimes queens."
1793569,2018-09-20 17:10:57 UTC,Updated iteration that deletes allocations from RPs that has been deleted.
1793569,2020-06-23 21:18:43 UTC,"Change abandoned by Artom Lifshitz (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/723751"
1793569,2020-06-23 21:18:13 UTC,"Change abandoned by Artom Lifshitz (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/720842"
1793569,2020-06-23 21:18:00 UTC,"Change abandoned by Artom Lifshitz (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/720839"
1793569,2020-06-23 21:17:50 UTC,"Change abandoned by Artom Lifshitz (<email address hidden>) on branch: stable/train
Review: https://review.opendev.org/720838"
1793569,2020-04-27 23:15:22 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/723751"
1793569,2020-04-17 21:22:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/720842"
1793569,2020-04-17 21:11:07 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/720839"
1793569,2020-04-17 21:08:07 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/720838"
1793569,2018-09-20 17:06:30 UTC,Related tooling for cleaning up orphaned resources and fixing incorrect allocations:
1793569,2020-03-30 12:02:08 UTC,"Reviewed:  https://review.opendev.org/670112
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c03716be1f3e9fd5a5e9adf95860c7ce4bfe211f
Submitter: Zuul
Branch:    master"
1793569,2020-03-30 07:22:40 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/715797"
1793569,2019-07-12 13:52:26 UTC,Bug 1836369 gives another scenario where allocations can be leaked and not tracked correctly when compute crashes during a resize.
1793569,2019-07-10 16:14:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670112"
1793569,2019-06-26 15:15:05 UTC,"(10:07:47 AM) mriedem: bauzas: i think what i was thinking of was an audit command could detect that you have orphaned allocations tied to a not-in-progress migration, e.g. a migration that failed but we failed to cleanup the allocations,
(10:08:20 AM) mriedem: bauzas: and then that information could be provided to the admin to then determine what to do, e.g. delete the allocations for the migration record consumer and potentially the related instance,
(10:08:33 AM) bauzas: mriedem: yeah ok
(10:08:35 AM) mriedem: and if they delete the allocations for the instance, then they could run heal_allocations on the instance to fix things up
(10:08:49 AM) mriedem: we could also eventually build on that to make it automatic with options
(10:08:57 AM) mriedem: e.g. nova-manage placement audit --heal
(10:09:00 AM) mriedem: something like that"
1793569,2019-06-26 14:59:15 UTC,"Per comment 5, I think I meant to say:"
1793569,2019-06-19 15:14:43 UTC,"I think one thing that larsks' and mnaser's audit scripts probably aren't handling are allocations held by migration records which never got cleaned up when a migration completed, likely failed for some reason and weren't cleaned up, e.g. we have several bugs related to failed migrations not cleaning up allocations properly:"
1793569,2020-04-02 23:08:19 UTC,"Reviewed:  https://review.opendev.org/715797
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=35ec5a0bd1d82d4d973bdfe1e62dc5a795eb533a
Submitter: Zuul
Branch:    master"
1793569,2018-11-05 15:13:21 UTC,Paste of mnaser's script: http://paste.openstack.org/show/734146/
1793572,2018-09-20 20:21:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1793581,2019-09-18 19:29:53 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.2.0 release.
1793581,2019-07-30 03:16:20 UTC,"Reviewed:  https://review.opendev.org/644662
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=9e265a209df9799f9ed80b82f078d26cd3141fe3
Submitter: Zuul
Branch:    master"
1793581,2019-03-19 20:02:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/644662"
1793581,2019-02-12 13:30:59 UTC,Is it still an issue?
1793588,2018-09-20 19:46:41 UTC,I'm Sorry for the German Text but otherwise I would need to reboot and I dont't know if I can recreate this problem.
1793593,2019-10-26 07:30:20 UTC,This is how ansible precedence works. Just remove from globals.yml.
1793595,2019-05-27 02:10:52 UTC,This bug is closed.
1793595,2019-05-25 06:39:23 UTC,"I can confirm this bug is an upstream bug.
I moved from Ubuntu to Fedora for this reason but it's still present even on the latest Fedora 30 with kernel 5.0.17.
Gnome shell (xorg or wayland) freezes mostly when using Chrome, I can't get Sys info during the freeze because keyboard and mouse aren't responding.
No issues on KDE Plasma desktop.
Tested on my work laptop (above 8 hours daily activity), Gnome freezes 4/5 times a day."
1793595,2019-05-17 04:17:25 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1793595,2019-05-17 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1793595,2019-03-18 02:43:59 UTC,Can you please try some newer kernels?
1793595,2019-03-18 02:43:11 UTC,"I just noticed you said ""Cannot access the system remotely as well."", which suggests a kernel problem."
1793595,2018-12-01 04:17:31 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1793595,2018-12-03 14:46:36 UTC,Here are the journalctl logs. Thanks for looking into it.
1793595,2019-03-17 15:41:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793595,2018-09-21 15:04:08 UTC,"everything freezes, only the mouse pointer works for a while. Can not do Alt+F1 sometimes."
1793595,2018-09-21 17:17:46 UTC,"Hi,"
1793595,2018-09-21 07:29:55 UTC,Does anything else freeze at the same time or is it just those apps?
1793595,2018-10-01 14:50:41 UTC,"Hi,"
1793595,2018-12-03 12:57:23 UTC,Could you add your journalctl log after getting the issue?
1793595,2018-10-01 07:57:08 UTC,If the mouse cursor still moves then the shell isn't completely frozen. gnome-shell actually uses a lot of CPU and processing to move the cursor so if it does then gnome-shell itself is fairly awake.
1793601,2018-09-21 02:13:36 UTC,Nice coincident that I just made a feature request for mirroring: https://bugs.launchpad.net/kicad/+bug/1793493. Would that work for you?
1793601,2018-09-21 14:41:13 UTC,Thanks for the note.
1793601,2018-10-20 10:17:50 UTC,As a comment and work-around:
1793606,2020-09-16 12:03:04 UTC,I was not able to reproduce this issue on the latest master. So I'm setting this Invalid. If you can still see the issue then please set this back to New.
1793608,2018-09-22 13:53:13 UTC,Small clarification to the bug description above.
1793608,2020-11-12 07:57:15 UTC,"A patch has been posted here:
https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg02218.html
(""ppc/translate: Implement lxvwsx opcode"")"
1793608,2020-12-10 08:45:39 UTC,Released with QEMU v5.2.0.
1793613,2021-01-10 23:50:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1584298, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1793623,2018-09-24 08:16:10 UTC,"Your logfile is full of warnings of type:
Warning: Signal not found : JJHSWSTANDHIA1R.S n .
This means that OR isn't able to find the Shape files of the signals. I assume you haven't correctly installed the route."
1793626,2018-09-21 02:56:53 UTC,https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/426301/
1793629,2019-09-01 15:26:09 UTC,"There are multiple duplicates and various suggested patches both on here and other forums but I can't see that any have been accepted. There are large ranges of values which can be returned by `Gdk.get_display().partition('.')[0]` which results in negative hash values, the most common probably being all display values between `:1000` and `:9999`, particularly on systems which might be configured to start display numbers at 1000 or 1001."
1793633,2018-11-08 14:03:56 UTC,"Reviewed:  https://review.openstack.org/604273
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=00ae68453867da38727aae0b48463d7133e53160
Submitter: Zuul
Branch:    master"
1793633,2018-09-21 06:30:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604273"
1793635,2020-11-12 18:43:08 UTC,How did you run QEMU? Is this still an issue with the latest version?
1793640,2019-06-21 11:04:34 UTC,I have tested on Kubuntu 19.04:
1793640,2019-06-21 11:13:32 UTC,Sending email to <email address hidden> bounces because the bug is archived and cannot be modified.
1793640,2019-06-21 11:51:08 UTC,"I confirm that timidity works after removing the timidity user. So instead of removing timidity all together, another workaround for this bug is to remove the timidity user and make sure the audio group is empty."
1793640,2019-06-21 21:17:34 UTC,"I removed timidity (without even purging) and my sound satarted working normally, even though my audio group still contains two users: pulse and timidity.  This group is supposed to be empty?"
1793640,2019-06-22 00:05:31 UTC,I have unarchived / reopened and commented debian bug.
1793640,2020-03-03 09:05:46 UTC,I upgraded from 18.04 to focal and had the same problem.  Purging timidity got audio back for me as well.
1793640,2020-03-09 16:59:07 UTC,Started happening to me on upgrade from 18.04 LTS to 19.10.
1793640,2020-06-03 05:30:51 UTC,Hit this issue when upgrading from Kubuntu 18.04 to 20.04.
1793640,2019-06-21 10:48:44 UTC,"A user in that bug already verified that it works. What I'm pointing out is that the user/group fix is not implemented in the Debian or Ubuntu package, and as long as that bug is closed it's not likely become implemented."
1793640,2020-09-20 04:51:23 UTC,Managed to make TiMidity++ work together with PulseAudio just fine on Focal 20.04.1. The idea is just to start both pulseaudio and timidity under the same user. One-liner for the current desktop user:
1793640,2020-09-22 05:57:49 UTC,TL;DR: It is enough to update the config of the timidity daemon instead of purging the timidity-daemon package in order to make pulseaudio work together with timidity daemon.
1793640,2020-09-22 19:42:03 UTC,@h1bymask
1793640,2020-10-21 09:01:04 UTC,sudo setfacl -m u:user:rw /dev/snd/*
1793640,2020-03-04 12:29:41 UTC,"In case this helps anybody:
I solved the MIDI issue by installing fluidsynth instead of timidity according to this guide:
https://blog.geierb.de/debian-fluidsynth-als-systemd-service/"
1793640,2020-08-03 09:14:40 UTC,On 20.04 at least it seems sufficient to only purge timidity-daemon and still timidity could be used to play midi files.
1793640,2019-06-21 09:18:41 UTC,Try the user/group fix mentioned there first:
1793640,2019-06-21 02:45:00 UTC,"I think that ""Fix Released"" status is misleading. Even the Debian bug mentions the problem is in 2.14.0-8 and that's the latest version in Ubuntu and Debian."
1793640,2018-10-03 05:21:43 UTC,I've changed the title because according to lspci the audio device is actually  Intel Corporation Sunrise Point-LP HD Audio (rev 21)
1793640,2018-10-19 21:12:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793640,2018-10-24 09:05:04 UTC,Can you please run this command:
1793640,2019-06-21 09:02:01 UTC,"Can the Debian bug be reopened? Otherwise, I'm afraid, we'll never see it fixed."
1793640,2018-10-25 02:35:44 UTC,Thanks! The problem is:
1793640,2019-03-30 16:13:33 UTC,"Same thing on a Lenovo L520 with Intel chipset,  attaching some info just in case it helps."
1793640,2019-04-16 12:09:54 UTC,I still have this problem in Ubuntu 19.04 develpment version. Here is a Debian bug about this:
1793640,2018-10-24 13:57:22 UTC,"Result of:
dpkg -l > dpkgl.txt"
1793640,2019-04-17 06:07:59 UTC,"I do use it, to play midi files and to convert them to other formats. But if it is an abandoned project, I will have to look for alternatives."
1793640,2019-04-17 06:11:49 UTC,"Daniel, why do you say it is unmaintained? I see an active Debian maintainer:"
1793640,2019-04-17 06:33:38 UTC,"OK, maybe just not with many releases or much active development. The latest version was released August 2018 and the latest commit was October 2018:"
1793640,2019-04-17 08:27:37 UTC,"From the discussion in bug 210472 and in the Debian bug, it looks more like a configuration or intergration issue in timidity packages rather than a genuine upstream bug."
1793640,2019-06-20 16:02:10 UTC,"Does ""fix release"" mean this bug has been fixed?"
1793640,2019-06-20 16:55:01 UTC,It does not seem to have landed in ubuntu yet : https://changelogs.ubuntu.com/changelogs/pool/universe/t/timidity/timidity_2.14.0-8/changelog
1793640,2019-04-17 01:56:27 UTC,"It doesn't appear Timidity is being maintained upstream anymore. If you can, please just uninstall it."
1793641,2018-10-02 00:53:13 UTC,"Installed zsh with oh my zsh and bug disappears.
Still don't know the cause, but too lazy to go back and deal with hunting it down."
1793667,2018-09-21 14:05:43 UTC,"Reviewed:  https://review.openstack.org/604288
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=78001f06a79d3bdd52fb7e2702fa4f124b453343
Submitter: Zuul
Branch:    master"
1793667,2018-09-21 14:06:27 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/604369"
1793667,2018-09-23 05:36:06 UTC,"Reviewed:  https://review.openstack.org/604369
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=02856c9d8483c549619a8e6c16bb7ad5a5001c5d
Submitter: Zuul
Branch:    stable/rocky"
1793667,2018-10-02 12:43:41 UTC,This issue was fixed in the openstack/kolla 7.0.0.0rc2 release candidate.
1793667,2019-01-07 14:39:20 UTC,This issue was fixed in the openstack/kolla 8.0.0.0b1 development milestone.
1793676,2018-10-23 14:47:17 UTC,"@Chhavi
Yeah, the only thing is that just having it configured doesn't mean it's actually set up properly and working.  A driver would be smart if it actually verifies it has connectivity and the connection settings work properly."
1793676,2018-10-15 13:50:36 UTC,"Hi chhavi, thanks for filing this.  There's a catch with that check actually, in particular with replication.  The problem is we didn't want to do the replication checks until *after* we were certain that all services were up and had reported their capabilities (including replication).  Note this also ties in the cluster replication/HA initialization as well IIRC."
1793676,2018-10-23 08:33:47 UTC,"Thanks John for the response, Agree to the point that for replication check we need all the services to be up.
What I am trying to propose, that for just getting the replication status do we really need to make get_volume_stats() call as this call fetches the complete volume stats. Rather if we can have a new method get_replication_status() which can be used to fetch the replication capabilities."
1793676,2018-10-23 08:35:35 UTC,"Or we can have replication_enabled as a driver property, which we currently do have in most of the storage drivers, to get the replication capabilities."
1793693,2018-09-21 09:43:07 UTC,"FWIW, the `autoload-credentials` command appears to generate a client certificate and key."
1793693,2020-03-12 03:11:02 UTC,"Due to current priorities, I am not currently working on this bug, so I am un-assigning myself from it."
1793694,2020-03-23 17:26:11 UTC,This issue was fixed in the openstack/horizon 18.1.0 release.
1793694,2020-01-31 10:45:15 UTC,"Reviewed:  https://review.opendev.org/704727
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=42d9a8d2e8736c5a8e94eaf7074755a1add3922b
Submitter: Zuul
Branch:    stable/stein"
1793694,2020-01-31 10:45:04 UTC,"Reviewed:  https://review.opendev.org/704728
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=e058e381607e93439a59f47c36e6a9b7cf61cc71
Submitter: Zuul
Branch:    stable/train"
1793694,2020-01-29 05:11:01 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/704728"
1793694,2020-01-29 05:11:30 UTC,"Change abandoned by Rikimaru Honjo (<email address hidden>) on branch: stable/train
Review: https://review.opendev.org/704503
Reason: Hello Akihiro,"
1793694,2020-01-29 05:07:17 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/704727"
1793694,2020-01-28 07:52:40 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/704505"
1793694,2020-01-28 07:50:15 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/704503"
1793694,2020-01-18 06:21:43 UTC,"Reviewed:  https://review.opendev.org/702642
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f9e0f8a976b82088ef095a69cd1fa892cddde3ba
Submitter: Zuul
Branch:    master"
1793694,2020-01-15 10:48:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/702642"
1793694,2020-01-29 05:09:25 UTC,"Change abandoned by Rikimaru Honjo (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/704505
Reason: I fixed Change-id in the following patch."
1793726,2018-09-21 12:43:55 UTC,apport information
1793726,2018-10-01 08:00:05 UTC,This change was made by a bot.
1793726,2018-09-21 12:43:59 UTC,apport information
1793726,2018-09-21 12:43:58 UTC,apport information
1793726,2018-09-21 12:43:57 UTC,apport information
1793726,2018-09-21 12:43:56 UTC,apport information
1793726,2018-09-21 12:43:54 UTC,apport information
1793726,2018-09-21 12:43:53 UTC,apport information
1793726,2018-09-21 12:43:53 UTC,apport information
1793726,2018-09-21 12:43:52 UTC,apport information
1793726,2018-09-21 12:43:51 UTC,apport information
1793726,2018-09-21 12:43:49 UTC,apport information
1793726,2018-09-21 12:43:48 UTC,apport information
1793726,2018-09-21 12:43:47 UTC,apport information
1793726,2018-09-21 11:47:16 UTC,Please:
1793729,2019-07-02 08:43:52 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/668635"
1793729,2019-07-02 16:22:35 UTC,"Reviewed:  https://review.opendev.org/668635
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=bd354841d5422f5d936c9f031228c3d5889368df
Submitter: Zuul
Branch:    stable/19.04"
1793729,2019-06-24 09:17:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/667046"
1793729,2019-06-06 04:16:04 UTC,Note we can whitelist the devices that OVS will probe which will improve this problem.
1793729,2019-06-24 13:59:14 UTC,"Reviewed:  https://review.opendev.org/667046
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=3c66c48bbd11922aa4740e752dfdb5e4f35a959d
Submitter: Zuul
Branch:    master"
1793731,2018-09-21 11:39:35 UTC,Crash report attached.
1793731,2018-09-21 12:22:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1793731,2018-09-21 14:26:51 UTC,See attachment re ls -l /home/dlf/.local/lib/python2.7/site-packages/six.py
1793737,2018-09-21 12:05:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793747,2018-10-08 20:53:31 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1793747,2019-03-22 03:47:22 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1793747,2018-12-19 10:04:52 UTC,This issue was fixed in the openstack/nova 16.1.7 release.
1793747,2018-10-08 21:50:44 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1793747,2018-10-01 21:44:19 UTC,"Reviewed:  https://review.openstack.org/605266
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=329780eb9282b05959e9c6159869ef1b4538030d
Submitter: Zuul
Branch:    stable/queens"
1793747,2018-10-24 22:35:43 UTC,"Reviewed:  https://review.openstack.org/605268
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c5cae2f63448c145c80b7f82ddccc7a9e672d534
Submitter: Zuul
Branch:    stable/pike"
1793747,2018-09-27 04:12:12 UTC,"Reviewed:  https://review.openstack.org/604898
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c9448cbdbf96e7436b13ac5c3a92addfc0f2f5a2
Submitter: Zuul
Branch:    master"
1793747,2018-09-25 23:25:17 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/605268"
1793747,2018-09-25 23:21:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/605266"
1793747,2018-09-25 23:09:40 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605260"
1793747,2018-09-24 20:31:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604898"
1793747,2018-09-24 20:27:03 UTC,https://review.openstack.org/#/q/Iee4b9bbf412adfdc6fdc62ea3429fb960d6ac2a2 was just released in pike and queens as well.
1793747,2018-09-29 01:51:39 UTC,"Reviewed:  https://review.openstack.org/605260
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8ea8ed4662a045f4121df688b85471e410593ec
Submitter: Zuul
Branch:    stable/rocky"
1793748,2018-09-21 12:47:48 UTC,"On Fri, Sep 21, 2018 at 12:16:42PM -0000, Aleksandr Bogdanov wrote:

> $ snapcraft
> Pulling deps
> Downloading 'node-v6.14.2-linux-x64.tar.gz'[============================================================================================================================================] 100%
> Sorry, an error occurred in Snapcraft:
> Traceback (most recent call last):
> [... snip ...]
>   File ""/usr/lib/python3.5/_compression.py"", line 68, in readinto
>     data = self.read(len(byte_view))
>   File ""/usr/lib/python3.5/gzip.py"", line 469, in read
>     uncompress = self._decompressor.decompress(buf, size)
> zlib.error: Error -3 while decompressing data: invalid block type
"
1793748,2018-09-25 10:51:57 UTC,"The file was broken indeed.
After manually deleting it, snapcraft command succeeded, since it was able to re-download it."
1793754,2018-09-21 16:18:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1793754,2018-09-21 20:05:57 UTC,"in the extracted files to the temp directory
root@:/tmp/tmp.TTeBq4nyWA# vim DistUpgradeAptCdrom.py"
1793754,2020-11-09 23:19:45 UTC,With ubuntu-release-upgrader version 21.04.2 which will be used by users upgrading to Ubuntu 21.04 the option to use cdromupgrade has been removed as it broken (as this bug indicates) and was no longer accessible by running any upgrade options.
1793755,2018-09-24 08:39:33 UTC,"I see it does have some reverse-depends (ubuntu-app-launch, libsdl2 etc), but none of them are seeded (or even in main) so it seems safe to release (indeed if no ABI/API has been broken). The package is in 'supported' so please be sure it doesn't introduce any visible regressions."
1793755,2018-09-24 09:58:55 UTC,"I thought sdl2 dropped the Mir dependency back in 18.04? It hasn't worked since the ""Mir EGL"" patch was dropped from mesa."
1793755,2019-01-14 14:38:38 UTC,Should that bug be closed or do you want to turn it into a SRU request?
1793758,2020-03-19 09:05:40 UTC,Closing because INVALID: Support request.
1793761,2019-08-03 03:06:13 UTC,"Fixed in revision 01e78b04c6bcc918ff67fedf585f31a5a03f6a5c
https://git.launchpad.net/kicad/patch/?id=01e78b04c6bcc918ff67fedf585f31a5a03f6a5c"
1793761,2019-08-03 02:47:37 UTC,"Also export VRML, IDF, GenCAD, and Specctra DSN."
1793763,2018-09-21 16:51:07 UTC,Can you please file a bug on the upstream project tracker:
1793763,2019-05-03 21:10:04 UTC,Probably bug 1826403 is related. It got reported upstream as
1793764,2019-08-26 09:31:30 UTC,Outputting the stuff in what appears (to the user) to be a random order strikes me as more of a bug....
1793764,2019-08-26 17:28:33 UTC,"Fixed in revision 92330b9c93feaed6d58ea03f9859c3c543bb8399
https://git.launchpad.net/kicad/patch/?id=92330b9c93feaed6d58ea03f9859c3c543bb8399"
1793765,2018-09-21 16:18:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1793766,2019-05-18 01:35:30 UTC,I do have this error looping every minute or so.
1793766,2019-06-18 16:26:40 UTC,I see this error too
1793767,2018-09-21 14:46:24 UTC,"You are right.  The middle-alignment, center-alignment issue was a quick-fix in the last days of 5.0-rc.  I recall the decision at the time was to make it deterministic (left-most and center-most) instead of picking the middle of the group.  But the plan is to eventually update that to align to the element you right-click on.  In the case of keyboard shortcut, we would use the first element selected."
1793768,2018-12-14 05:17:39 UTC,"Reviewed:  https://review.openstack.org/607730
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0163783382c4825a6f18e346d17b9e67e98ed1a2
Submitter: Zuul
Branch:    stable/queens"
1793768,2019-03-22 03:47:28 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1793768,2018-12-19 20:48:24 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1793768,2018-10-08 20:53:26 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1793768,2018-09-21 14:49:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/604376"
1793768,2018-10-03 14:37:54 UTC,"Reviewed:  https://review.openstack.org/605533
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=220796807396ad6aa8cc8f1fc9ff905253681896
Submitter: Zuul
Branch:    stable/rocky"
1793768,2018-09-26 20:59:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605533"
1793768,2018-09-26 20:52:03 UTC,"Reviewed:  https://review.openstack.org/604376
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6eb32bc40340fed631b9fce1245326e0ebc1c540
Submitter: Zuul
Branch:    master"
1793768,2018-10-03 22:08:06 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/607730"
1793773,2019-01-15 23:34:36 UTC,"Confirmed by SCLENDS (3.1.8, Google Chrome).  Here is how one SCLENDS cataloger describes the web client change versus XUL:"
1793773,2019-01-17 18:37:31 UTC,"Meg,"
1793773,2019-01-17 18:38:30 UTC,"While I see the dangers inherent in having the entire subfield focused, I would like to have text wrapping in the MARC editor"
1793775,2020-08-19 09:53:11 UTC,Issue not reproduced in openstack stein release. Issue seems to be fixed now.
1793791,2021-01-12 04:17:37 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1793791,2020-11-12 18:43:53 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1793791,2018-09-25 22:37:11 UTC,"Okay, this is probably a race condition bug.  If remove:"
1793791,2018-09-24 19:53:07 UTC,"I'm back to trying to figure this out.  I can't use migrate and copy storage until this bug is fixed, so I'm pretty motivated.  Today I configured libvirt/qemu to dump the core, and I compiled qemu with debugging symbols.  Here is the backtrace.  I'm not sure it says anything we don't already know."
1793791,2018-09-21 23:34:43 UTC,"Hi Eric,"
1793791,2018-09-21 22:36:28 UTC,"On 9/21/18 11:42 AM, Matthew Schumacher wrote:

> Public bug reported:
>
> Qemu version on both sides: 2.12.1
> Host A Linux: 4.9.76
> Host B Linux: 4.14.67
>
> While calling from Host A:
> virsh migrate virtualmachine qemu+ssh://hostB/system --live --undefinesource --persistent --verbose --copy-storage-all
"
1793791,2018-09-21 19:07:53 UTC,Tested with Qemu 3.0.0 and this still happens.
1793791,2018-09-24 20:23:33 UTC,From the core:
1793802,2019-09-06 21:40:12 UTC,"Pushed to master for inclusion in 3.4. Thanks, Bill and Chris!"
1793802,2018-09-26 21:25:36 UTC,Patch to address the two above TODO items pushed.
1793802,2018-10-19 22:33:03 UTC,"I installed this branch on my 3.0.2(-ish) database and the migration went well.  However, when I attempted a purge of circulations, I got this:"
1793802,2018-10-20 12:14:17 UTC,"Chris, the action.age_circ_on_delete() trigger function needs to delete payments before it deletes billings.  (Swap the last 2 lines of the function).  I fixed this in the migration script, but forgot about the circ aging function...  I've pushed a commit to the working branch to change the function (and add a minor efficiency improvement to the migration)."
1793802,2018-12-03 20:00:24 UTC,Signoff branch at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/csharp/lp1793802-aged-billing-payment
1793802,2018-12-04 15:40:34 UTC,"Beware, if this code is deployed to a 3.0 system, an extra SQL step is required during the 3.1 upgrade to add create_date, period_start, and period_end fields to money.aged_billing."
1793802,2018-12-04 16:23:30 UTC,Continuing from my previous comment...  The new money.aged_billing columns can be created during the 3.0 -> 3.1 upgrade as NULL-able so admins may back-fill the data and re-synchronize the columns at their leisure (i.e. not during an upgrade outage).
1793802,2019-05-21 10:37:56 UTC,"After applying this to PINES production and running it since January 2019, all has been well overall, but I did discover an issue with the Combined Aged and Active Circulations view(s) where they are not linked to these new sources, causing us to undercount bills/payments.  I will rebase and update my signoff branch accordingly shortly."
1793802,2019-08-12 12:16:11 UTC,"Okay, here's my branch. Sorry for the delay:"
1793802,2019-08-12 12:17:04 UTC,Removed signoff so others can review the full branch including my changes.
1793802,2018-09-21 20:35:13 UTC,"I have some interest in data cleanup prior to upgrading to 3.1, so I put together a patch to implement the above for feedback, minus the purge-interval setting.  May revisit that later via another LP."
1793802,2018-09-26 14:37:33 UTC,TODO:
1793809,2019-07-19 09:53:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793809,2019-07-19 09:57:14 UTC,"Why use a package manager if the packages are not updated in a regular manner?
Fast developing stuff like golang should receive quick updates."
1793809,2019-07-26 13:34:04 UTC,Installing go using `snap install go --classic` installs go version 1.12.7
1793809,2020-05-01 20:12:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu."
1793812,2018-09-25 22:08:39 UTC,...and/or recommend to try Fedora on ARM?
1793812,2020-12-16 00:08:37 UTC,I have just enabled the ARM ARMv7 Hard Float (armhf) for 2.3 and 2.4
1793813,2018-10-15 12:47:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793813,2018-10-22 01:21:49 UTC,"This is affecting queens as well
ii  magnum-api                           6.1.0-0ubuntu1~cloud0                      all          OpenStack containers as a service
ii  magnum-common                        6.1.0-0ubuntu1~cloud0                      all          OpenStack containers as a service - API server
ii  magnum-conductor                     6.1.0-0ubuntu1~cloud0                      all          OpenStack containers as a service - conductor
ii  python-magnum                        6.1.0-0ubuntu1~cloud0                      all          OpenStack containers as a service - Python library"
1793813,2018-11-07 09:03:27 UTC,The upstream fix to this has just landed in master: https://review.openstack.org/#/c/614082/
1793817,2018-09-21 20:42:18 UTC,"Noting that checkin_handle_backdate() in Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Circulate.pm will need to be updated to accept the time passed in, among other things."
1793826,2018-09-24 12:37:41 UTC,Hello.
1793826,2018-09-24 20:33:36 UTC,"I wish that link came up higher on the Google results!
Thanks."
1793831,2018-09-27 18:53:51 UTC,Have you tried:
1793831,2018-09-27 20:54:51 UTC,"Blake,"
1793831,2018-09-27 20:56:43 UTC,Would it make sense to have a global option for this?
1793837,2018-10-01 19:15:02 UTC,"No better luck with 4.19.0-041900rc6-generic.
Upon reboot, running at 1920x1080 *interlaced*. No good - I am getting the shakes just watching the screen. And it is slightly blurred.
Thanks for all the help and hard work!
pj"
1793837,2018-10-01 19:03:44 UTC,"No change with kernel 4.19.0-041900rc5-generic, alas."
1793837,2018-10-01 09:28:35 UTC,Thank you.
1793837,2018-10-01 07:53:58 UTC,"The hardware brochure says ""HDMI 2.0 (3840x2160 @ 60Hz), HDCP compliant"" on
http://hkftp.zotac.com/External/ZBOX/C-series/CI547nano/Brochure/ZBOX-CI547NANO_Brochure.pdf"
1793837,2018-09-26 18:53:28 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1793837,2018-09-24 07:36:11 UTC,You probably need to file it upstream at bugs.freedesktop.org (DRI; DRM/Intel)
1793837,2018-09-26 20:07:33 UTC,"I will do so with great pleasure on Tuesday (happen to be on a business
trip at this moment)."
1793837,2018-09-24 08:06:25 UTC,"I hear you.
It happens both with the intel driver and with the standard 'modesetting' driver.
Quite a few people appear to have this problem from what I could glean out there.
I understand the reluctance at this layer to look into this, but it is a fairly common problem, and I get the impression wherever I see this reported that there is no-one even trying."
1793844,2020-04-04 15:13:17 UTC,"I was unable to reproduce your error on a system with gfortran-6.4.0.
Note that you seem to have hit upon an internal compiler error, not on an error in xmlf90 itself."
1793844,2020-04-04 15:13:31 UTC,Development of xmlf90 has moved to Gitlab:
1793845,2018-10-08 10:00:01 UTC,"You should not need to add the `saml2 = ...` line, as saml2 is already configured as an entrypoint for the Mapped plugin: http://git.openstack.org/cgit/openstack/keystone/tree/setup.cfg?h=14.0.0#n97"
1793845,2018-10-24 18:03:15 UTC,"Do we want to revert the change or continue forward with this plan? Marking as incomplete waiting for Colleen or the reporter to follow up. If this expires, my assumption is we will roll with the changes we have and not move forward on a revert."
1793845,2018-10-24 18:18:05 UTC,I think its up to y'all. My vote is to let it work like it did before because that wasnt hurting anything from my point of view but I dont know what kind of overhead it is to maintain code wise.
1793845,2018-10-25 13:47:22 UTC,"I think we should revert for another cycle, because the way it is we don't have a workaround for this anymore: https://bugs.launchpad.net/keystone/+bug/1724645 (hoping to get an outreachy intern to work on that pretty soon)"
1793846,2018-10-04 03:52:45 UTC,"Use kernel parameter ""usbhid.quirks=0x0079:0x0006:0x100000""."
1793846,2018-10-11 07:59:25 UTC,https://lkml.org/lkml/2018/10/11/331
1793846,2018-10-04 04:25:09 UTC,Thank you for this option. Using it the controller is working properly again.
1793846,2018-09-27 03:54:28 UTC,Have you tried HID_QUIRK_INCREMENT_USAGE_ON_DUPLICATE?
1793846,2018-09-26 20:48:16 UTC,"Unfortunately the gamepad is still with the problem. The right stick does not work properly, its up/down movement does the left/right action and left/right movement do nothing."
1793846,2018-09-26 19:48:33 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1793846,2018-09-22 04:30:05 UTC,This change was made by a bot.
1793846,2018-09-27 04:37:28 UTC,"No, because I don't know where I should apply HID_QUIRK_INCREMENT_USAGE_ON_DUPLICATE, as all search results are the commit message."
1793852,2018-09-23 05:31:34 UTC,Quoting RainMan from https://bugs.launchpad.net/sikuli/+bug/1793854
1793852,2018-11-22 16:39:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793852,2018-11-22 16:40:39 UTC,Still actual for freshly upgraded 18.04 LTS. All output is below:
1793852,2019-06-05 19:46:07 UTC,"latest report:
[error] RunTimeINIT: Java version not detected (using 7): 11.0.3+7-Ubuntu-1ubuntu218.04.1
java ?7?-64 version 11.0.3+7-Ubuntu-1ubuntu218.04.1 vm 11.0.3+7-Ubuntu-1ubuntu218.04.1 class 55.0 arch amd64
*** system properties dump
awt.toolkit                   = sun.awt.X11.XToolkit
file.encoding                 = UTF-8
file.separator                = /
java.awt.graphicsenv          = sun.awt.X11GraphicsEnvironment
java.awt.printerjob           = sun.print.PSPrinterJob
java.class.path               = /usr/share/sikulix/sikulix.jar
java.class.version            = 55.0
java.home                     = /usr/lib/jvm/java-11-openjdk-amd64
java.io.tmpdir                = /tmp
java.library.path             = /usr/lib/jni:/usr/lib/alpha-linux-gnu/jni:/usr/lib/x86_64-linux-gnu/jni:/usr/lib/aarch64-linux-gnu/jni:/usr/lib/x86_64-kfreebsd-gnu/jni:/usr/lib/powerpc64-linux-gnu/jni:/usr/lib/powerpc64le-linux-gnu/jni:/usr/lib/s390x-linux-gnu/jni:/usr/lib/sparc64-linux-gnu/jni
java.runtime.name             = OpenJDK Runtime Environment
java.runtime.version          = 11.0.3+7-Ubuntu-1ubuntu218.04.1
java.specification.name       = Java Platform API Specification
java.specification.vendor     = Oracle Corporation
java.specification.version    = 11
java.vendor                   = Oracle Corporation
java.vendor.url               = http://java.oracle.com/
java.vendor.url.bug           = http://bugreport.java.com/bugreport/
java.version                  = 11.0.3
java.version.date             = 2019-04-16
java.vm.compressedOopsMode    = 32-bit
java.vm.info                  = mixed mode, sharing
java.vm.name                  = OpenJDK 64-Bit Server VM
java.vm.specification.name    = Java Virtual Machine Specification
java.vm.specification.vendor  = Oracle Corporation
java.vm.specification.version = 11
java.vm.vendor                = Oracle Corporation
java.vm.version               = 11.0.3+7-Ubuntu-1ubuntu218.04.1
jdk.debug                     = release
line.separator                ="
1793859,2018-10-25 13:35:25 UTC,"Hi, I have a hack for this issue."
1793859,2018-11-06 08:45:34 UTC,"Hi there,"
1793859,2018-11-26 21:53:26 UTC,"Chen, have you seen the following bug report? https://bugs.launchpad.net/qemu/+bug/1592351
See my comment there, with recent git build of 3.1.0 I don't have a pointer offset issue."
1793859,2020-02-14 23:54:04 UTC,Perhaps this is due to this issue https://github.com/intel/gvt-linux/issues/71
1793860,2019-10-10 22:53:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793865,2018-10-04 04:59:35 UTC,Ok
1793865,2018-10-03 18:43:16 UTC,An open pull request does not change the state of this issue.
1793865,2018-10-03 17:16:48 UTC,Link to pull request https://github.com/mixxxdj/mixxx/pull/1831
1793865,2018-09-28 16:55:44 UTC,"Hm, I personally find ""from File"" and ""from Audio File"" equally ambiguous."
1793865,2018-09-23 11:00:37 UTC,"""audio file"""
1793865,2018-09-22 08:44:36 UTC,"Or ""Re-Import from file"" ""Import from file again"""
1793867,2018-09-22 10:22:41 UTC,-
1793879,2018-09-23 08:50:43 UTC,"Salut,"
1793879,2018-09-28 17:58:20 UTC,"Je peux répliquer sans même faire une recherche filtre
Je ne suis pas un pro des ''locales''"
1793879,2018-09-28 18:58:47 UTC,"Les histoires de locales
il y a aussi
https://bugs.launchpad.net/qarte/+bug/1666829"
1793880,2018-09-24 19:38:58 UTC,"Submitted https://bugs.launchpad.net/keystonemiddleware/+bug/1794179 but we should fix up proxy_logging to handle unicode headers on py2 regardless, if only to make third-party middleware authors' lives easier."
1793880,2018-09-24 21:08:53 UTC,"Change abandoned by Bulat Gaifullin (<email address hidden>) on branch: master
Review: https://review.openstack.org/604519"
1793880,2020-01-13 15:42:37 UTC,I got a simillar error in Train version (python 3)
1793886,2018-10-02 20:02:12 UTC,"In Peppermint9, I can get the Font Size and Background Image to work (if I put the .png file in /boot/grub), but the Font Colours steadfastly refuse to change."
1793886,2018-10-02 20:25:55 UTC,But the only way I could revert the background was to delete my image file. Nothing I can do makes the font colours change.
1793894,2020-09-16 16:38:43 UTC,We do not support 32-bit UEFI.
1793894,2019-07-18 08:12:51 UTC,"Debian 10 Buster now has proper signed bootloader for 64bit UEFI and 32bit UEFI.
so next step should be that ubuntu will upgrade to properly signed bootloader as well."
1793894,2019-02-16 14:53:32 UTC,see the answer i got https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909718
1793894,2018-10-31 22:17:14 UTC,"today i tried Fedora 29 Workstation Live (64bit).
there is a bootia32.efi that is correctly Microsoft UEFI CA signed.
with that version i can boot and use Fedora 29
on all my UEFI32 + SecureBoot enabled devices successfully.
i hope it will be fixed for Ubuntu as well soon..."
1793894,2019-02-15 16:46:10 UTC,"Sorry, I was wrong: Debian now has IA32 package (not sure about ISOs though).
https://packages.debian.org/buster/grub-efi-ia32-signed"
1793894,2019-02-15 15:04:10 UTC,"I can confirm that Ubuntu, Debian and OpenSuse have only X86_64 signed EFI bootloader. From what I know, only Fedora has IA32 signed bootloader."
1793894,2019-02-16 14:40:38 UTC,"the Debian one is only ""Debian UEFI CA"" signed and not ""Microsoft Corporate UEFI CA"" signed.
that means, as far as i know, it is only usable then you manually add that ""Debian UEFI CA"" certificate/key to your UEFI certificate/key store, before you are able to boot with SecureBoot enabled."
1793902,2018-09-22 17:35:50 UTC,"Whoops, sorry, just noticed that it was related to Padoka's PPA, might be a few days old (I'm currently testing stuff to identify an issue with Mesa). I assume it's an issue with the PPA, bug report can likely be closed."
1793903,2018-11-16 15:09:41 UTC,"Yes, this is a known, long-standing issue, tracked in Debian at https://bugs.debian.org/509100 (and some more duplicates of that bug report)."
1793904,2018-09-26 11:02:54 UTC,Update: I do have changed all important vms to a fuserfs image mount.
1793904,2018-09-26 20:27:59 UTC,"Looks like you've narrowed it down to QEMU's usage of gluster, but some additional details might still be nice just to be sure:"
1793904,2018-09-26 22:07:48 UTC,"Hi John,"
1793904,2019-04-21 11:05:30 UTC,I will have to put more efford into that: The bug applies to oVirt 4.3 too which seems to use a fuse filesystem.
1793904,2019-04-23 05:31:29 UTC,I did some undocumented testing to circle the issue down: It seems to affect Files that are stored as sparsed files either raw or qcow2.
1793904,2019-04-29 19:58:21 UTC,Please note the updates on:
1793918,2020-11-05 09:52:54 UTC,"> (untested) patch
"
1793918,2020-11-05 09:40:45 UTC,Comment from the new duplicate
1793918,2018-11-01 21:50:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793925,2018-10-06 00:06:18 UTC,submitted PR https://gitlab.gnome.org/GNOME/caribou/merge_requests/1
1793928,2020-03-07 11:35:42 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1793932,2018-09-23 05:13:21 UTC,Further investigation showed error was due to deprecated TLS options in settings files.
1793932,2018-09-25 07:19:08 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1793934,2019-04-14 13:53:04 UTC,"I created an account to chime in here and say I'm having basically the exact same issue. I can't boot into the live USB without setting a nomodeset flag. I can then install, but I can't boot into the actual OS without setting nomodeset. I've tried several workarounds, but nothing has been successful."
1793934,2018-10-06 12:05:39 UTC,"I found this ArchWiki page which has a section about my GPU: https://wiki.archlinux.org/index.php/AMDGPU#R9_390_series_Poor_Performance_and.2For_Instability
After setting ""radeon.cik_support=0 amdgpu.cik_support=1 amdgpu.dpm=1 amdgpu.dc=1"" as kernel parameters, I did not get a black screen (yet).
So it seems, I am having the same issue as in this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=91880"
1793934,2018-10-03 09:27:24 UTC,A couple lines in kern.log stood out to me:
1793934,2018-09-27 18:26:42 UTC,Thank you for looking into this.
1793934,2018-09-26 19:45:18 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1793934,2018-09-23 07:00:06 UTC,This change was made by a bot.
1793934,2018-10-03 09:17:20 UTC,I just did a reinstall using nomodeset. Afterwards I gathered some log files out of /var/log/ in the hopes that they may be of some help.
1793940,2018-09-23 10:29:00 UTC,"I think I falsely blamed the bug 1654034 fix, I'm sorry. Reverting the fix doesn't help, and I can reproduce it also with ""Inkscape 0.92.2 2405546, 2018-03-11"" (from Arch Linux repo)."
1793940,2018-09-23 13:16:03 UTC,Is the relative directory a parent directory or a child directory for you?
1793940,2018-09-23 14:00:47 UTC,"Thanks for testing, Patrick!"
1793940,2018-09-23 14:06:07 UTC,"might be useful to look at
https://gitlab.com/inkscape/inkscape/blob/master/src/xml/rebase-hrefs.cpp"
1793940,2018-09-24 07:10:54 UTC,"Patch:
https://gitlab.com/inkscape/inkscape/merge_requests/333"
1793946,2018-09-24 08:18:32 UTC,I think the difficulty could also be selected in on the campaign or campaign scenario selection screens rather than in-game.
1793946,2019-09-16 13:56:22 UTC,Migrated to https://github.com/widelands/widelands/issues/2117
1793946,2018-09-23 13:58:58 UTC,I have missed this also :-) Especially some sort of option box...
1793946,2018-09-23 14:29:08 UTC,"For the text dialogue: I´d like to ask the player his name once when he starts the first mission and then address him by name throughout the campaign, to integrate him into the storyline like one of the characters. For example, if you then play the frisian campaign, the chieftain will be called not Reebaud but kaputtnik ;)
I also want to give players the chance to choose between several difficulties (like easy/medium/hard) when they begin a campaign. Spinners could be used to allow players to set advanced settings for the scenario difficulty if they like, such as the number of wares demanded in fri02."
1793953,2018-11-10 15:29:16 UTC,apport information
1793953,2018-11-25 20:41:13 UTC,"Hi, I've just tried kernel v.4.4.164 and I'm writing this after a resume from standby successfully: the keyboard is active and it works."
1793953,2018-11-22 08:14:07 UTC,Can you try kernel v4.4? It's a regression if it works under old kernel.
1793953,2018-11-15 21:10:00 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1793953,2018-11-10 15:29:25 UTC,apport information
1793953,2018-11-10 15:29:22 UTC,apport information
1793953,2018-11-10 15:29:19 UTC,apport information
1793953,2018-11-10 15:29:18 UTC,apport information
1793953,2018-11-10 15:29:15 UTC,apport information
1793953,2018-11-10 15:29:20 UTC,apport information
1793953,2018-11-10 15:29:14 UTC,apport information
1793953,2018-11-10 15:29:13 UTC,apport information
1793953,2018-11-10 15:29:11 UTC,apport information
1793953,2018-11-10 15:29:10 UTC,apport information
1793953,2018-11-10 15:29:09 UTC,apport information
1793953,2018-11-10 15:29:07 UTC,apport information
1793953,2018-11-10 15:29:06 UTC,apport information
1793953,2018-11-10 13:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1793953,2018-09-23 18:43:01 UTC,On Ubuntu 16.04 LTS resume from suspend worked well with the same laptop.
1793953,2018-11-10 15:29:14 UTC,apport information
1793954,2018-09-23 12:36:19 UTC,"Maybe we can tweak the environment variables using the slider in:
https://github.com/mixxxdj/mixxx/pull/1741"
1793954,2018-12-25 09:06:09 UTC,"Zulip:
https://mixxx.zulipchat.com/#narrow/stream/109695-_support/topic/v2.2E2.2E0.20scaling
https://mixxx.zulipchat.com/#narrow/stream/109171-development/subject/2.2E2.2E0.20release.20progress/near/152504828"
1793954,2019-04-07 19:34:50 UTC,"It looks like this is a relay annoying one. I will put it to the 2.3 milestone to express this.
Maybe one find time to fix it without using a batch file."
1793954,2019-04-07 19:39:38 UTC,An other effected user: https://www.mixxx.org/forums/viewtopic.php?f=1&t=12585
1793954,2019-04-07 19:54:09 UTC,That's the reason why I always recommended not to enable this legacy option by default.
1793954,2019-04-16 11:11:26 UTC,"one more
https://mixxx.zulipchat.com/#narrow/stream/109695-_support/topic/help"
1793955,2018-09-23 12:49:10 UTC,"Reported here:
https://mixxx.zulipchat.com/#narrow/stream/109695-_support/subject/saving.20h.2Fw.20config"
1793956,2019-05-09 09:46:08 UTC,Could you add the journalctl log from the machine after a failing login?
1793956,2019-05-09 09:50:25 UTC,Please also run:
1793956,2019-07-09 04:17:19 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1793956,2019-05-09 08:39:39 UTC,given it's incomplete and not activity for quite a while. remove from oem-priority.
1793956,2019-05-09 09:01:40 UTC,Sorry I will post more info from the client
1793960,2019-09-11 10:41:37 UTC,"Similar problems with Acer TravelMate B118-M that has ElanTech touchpad ELAN0502.
My distro is Lubuntu 16.04.6 LTS 64 bit with 4.15.0-60-generic kernel (up-to-date).
Tried to upgrade the kernel to latest releases, but it claims for libssl1.1 (used in 18.04) and 16.04 uses libssl1.0
I tested the laptop with Lubuntu 18.04.3 64bit (USB installation stick) that it comes with 5.0.0-23-generic kernel and it works!"
1793960,2019-06-21 13:00:45 UTC,using 5.2.0-050200rc3-generic worked for me.
1793960,2019-06-11 02:45:45 UTC,Does anyone know which kernel DOES have this fix so I can upgrade ? This is an annoyance.
1793960,2019-02-20 15:08:17 UTC,"No, it's not in 5.0-rc* yet."
1793960,2019-02-20 14:49:35 UTC,Would 5.0.0-rc* work?
1793960,2019-02-20 13:00:47 UTC,Please test the kernel in -proposed. It should solve this issue.
1793960,2019-02-15 20:48:47 UTC,"Doing
sudo rmmod i2c_hid
sudo rmmod hid
worked for me."
1793960,2019-02-06 21:59:00 UTC,"This error happens, but even when I am not touching anything, I do ctrl alt f5 and it spams the shell. I can’t even put a command in. The only things I can do are shut down and exit shell."
1793960,2019-02-06 22:07:21 UTC,"Also, my syslog file took up 1.1 Gb. My computer only has 16. (Chromebook, soooo...) Even if I delete it, it comes back."
1793960,2018-11-11 15:50:00 UTC,"I did post the issue to the mailing list but did not receive any answer for the past 14 days. I know that other users are affected too, for example at reddit. This is really bad, because it essentially means that this laptop can not be used with linux at all without external mouse."
1793960,2018-09-23 14:00:06 UTC,This change was made by a bot.
1793960,2018-11-24 19:49:44 UTC,The same problem to me with the same model of computer.
1793960,2018-09-23 19:48:56 UTC,"modprobe -r elan_i2c
modprobe elan_i2c"
1793960,2018-09-26 19:44:20 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1793960,2018-09-23 19:45:02 UTC,After some time the Touchpad now stops working and is not usable. External Mouse works fine.
1793960,2018-10-01 06:58:31 UTC,Both elan_i2c and hid_i2c want to use the device. Can you blacklist either one of these to see which one really works?
1793960,2018-10-03 10:50:41 UTC,"modprobe -r elan_i2c disables the touchpad.
modprobe -r i2c_hid doesn't seem to have any effect."
1793960,2018-10-03 10:58:58 UTC,"Also did
depmod -a
update-initramfs -u"
1793960,2018-10-04 14:35:40 UTC,"Please report the issue to <email address hidden> and cc the Elan driver author, <email address hidden>."
1793960,2018-09-28 18:54:22 UTC,"Thanks for your reply.
This is a new laptop, so I am not able to say anything about prior kernel versions.
With upstream kernel v4.19 the issue persists."
1793965,2019-01-18 00:54:12 UTC,Like this:
1793965,2019-10-26 23:51:29 UTC,Fixed in 1.3.2-5 in focal.
1793965,2019-09-24 14:52:21 UTC,The fix actually has been re-directed to the 1.3 series; IE 1.3.1 has it.
1793965,2019-08-28 13:52:45 UTC,So from upstream fwupd we've decided to drop the support for probing Dell MST hubs at fwupd init.  They'll only show up in fwupd now if a monitor is plugged in.
1793965,2019-05-24 15:54:38 UTC,Wow I'm not alone!  Happens with the same hardware.  Dell 5520 with a TB16 dock.  After login it now goes through up to 6 cycles of blank to normal screens before it stabilizes after 30-60 seconds.  It's connected to a Dell 4k monitor via displayport.  The TB16 side is using a normal DP connector and the monitor side is using a mDP connector.  I mention this because previously I had the cable connected the other way (mDP connector on TB16) and it would flicker a little less (up to 4 times max).
1793965,2019-02-21 14:05:37 UTC,"Getting the same issue on Precision 5520, Ubuntu 18.04.1, kernel 4.18.0-15 (HWE) with a Dell TB16 dock and it only happens when daisy-chaining DP monitors."
1793965,2019-01-17 05:04:53 UTC,"#10 ""After disabling ""dell"" plugin, it doesn't blank out my screens any-more."" How did you do that?"
1793965,2018-09-24 13:57:19 UTC,"My suspicion around this is that it's not actually the dock being reset, but rather an MST hub being placed into ""high"" power mode.  The TB16 contains two MST hubs.
The current configuration of monitors you have plugged in probably doesn't exercise both MST hubs, so one of them is operating in ""low"" power mode."
1793965,2018-09-29 10:03:05 UTC,"After disabling ""dell"" plugin, it doesn't blank out my screens any-more."
1793965,2018-09-29 10:01:12 UTC,4) (after disabling dell plugin and reboot)
1793965,2018-09-29 09:57:01 UTC,"1.
fwupdmgr get-devices
Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock
  DeviceId:             7b3cbc344094ace839263dd4711c84ea99bb6dc3
  ParentDeviceId:       84edf044a6b53037732cfc7591b65a8d36384cc9
  Guid:                 152a9833-41e6-5c21-9dde-0ff8984f3e20
  Guid:                 0a52c8c7-26d5-59a0-ae44-6b00e276d775
  Guid:                 51000744-2de6-5a52-8a86-d5f69fd73d34
  Summary:              Multi-Stream Transport Device
  Plugin:               synapticsmst
  Flags:                updatable|registered
  Vendor:               Synaptics
  Version:              3.12.002
  Icon:                 computer
  Created:              2018-09-29"
1793965,2018-09-28 12:44:27 UTC,"Dell Precision 5520. Running Intel graphics. Nvidia card is turned off (unused).
I'll try that and I'll let you know. Thanks for help."
1793965,2018-09-23 22:19:28 UTC,Can you please add --verbose to the ExecStart line of the systemd unit and share journal output?
1793965,2018-09-23 14:54:35 UTC,"BTW: The problem existed also on Ubuntu 18.04, so this is not a new thing.
Kernel version seem to not have any influence. Tried many kernels ranging from recent 4.15.x, 4.17.19, through 4.18.8, to the newest 4.19.rc4."
1793965,2018-09-23 14:52:11 UTC,Removing fwupd package completely fixes the problem.
1793965,2018-09-29 10:07:05 UTC,After unplugging displays from the dock and rebooting:
1793972,2018-09-23 17:44:28 UTC,Logging out and logging back in again made them appear. Bug resolved.
1793972,2019-03-20 21:59:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793973,2018-09-24 01:50:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1793975,2018-09-23 19:26:32 UTC,"StacktraceTop:
 ?? ()
 vnc_connection_raw_update (conn=conn@entry=0x55be0f00dd40, x=x@entry=112, y=y@entry=0, width=<optimized out>, height=height@entry=16) at ../../../src/vncconnection.c:2190
 vnc_connection_hextile_rect (bg=0x7ff9d1200e90 """", fg=0x7ff9d1200e50 ""\252\252\252"", height=<optimized out>, width=<optimized out>, y=<optimized out>, x=112, flags=9 '\t', conn=0x55be0f00dd40) at ../../../src/vncconnection.c:2225
 vnc_connection_hextile_update (height=<optimized out>, width=<optimized out>, y=<optimized out>, x=<optimized out>, conn=<optimized out>) at ../../../src/vncconnection.c:2280
 vnc_connection_framebuffer_update (height=384, width=640, y=0, x=0, etype=<optimized out>, conn=0x55be0f00dd40) at ../../../src/vncconnection.c:3136"
1793985,2019-05-30 16:14:39 UTC,I am having the same issue on Ubuntu 19.04. Which is too bad as I use this feature a lot when I want to change from the gui to the command line.
1793985,2019-01-26 18:52:26 UTC,I am still experiencing issues with this.
1793986,2018-09-23 21:13:57 UTC,This looks like it automaticity added 8 files to the report. Thanks for your attention. Hot mail me.
1793987,2018-09-23 22:48:00 UTC,"There's a typo in the ""Re-associate footprints by reference"" code which makes a pretty big mess."
1793987,2018-09-23 22:52:17 UTC,"Fixed in revision 9eb574015c7eee1e6a2feb5769de7fcc0fa34d9b
https://git.launchpad.net/kicad/patch/?id=9eb574015c7eee1e6a2feb5769de7fcc0fa34d9b"
1793987,2018-09-23 22:54:17 UTC,"Setting back to ""New"" as my fix only addresses 1/2 of the bug."
1793993,2019-01-18 10:00:11 UTC,"Hi,"
1793993,2019-01-19 16:18:52 UTC,"I ticked the box ""Request to merge"" on the branch page.  Will try to get it into 0.8 soon."
1793997,2018-10-12 10:07:28 UTC,"lspci no longer shows ""Intel Corporation Wireless 7260"" entry on my system. So I guess it is a hardware problem. Funny thing that bluetooth which is located on the same chip still works."
1793997,2018-10-08 20:20:37 UTC,"Haven't asked for a new wifi card yet, as I don't think it's the hardware. But I might get annoyed enough to try."
1793997,2018-10-08 05:19:44 UTC,Joseph do you need any more information? Any ideas to try?
1793997,2018-10-08 05:08:44 UTC,"In my case crash can happen on freshly booted system as well. And it is more likely to happen when I'm using Wi-Fi actively, although it sometimes happens even if I barely use Wi-Fi (eg. I'm connected via ethernet cable and Wi-Fi at the same time and routing is configured to use the cable)."
1793997,2018-10-08 01:38:38 UTC,"Another crash, without any temperature message."
1793997,2018-10-05 03:04:12 UTC,"I've grepped through dmesg and journalctl there is zero messages about temperature from iwlwifi in my case. I've some from CPU, but they are probably not related."
1793997,2018-10-04 20:01:21 UTC,"I have been working with the manufacturer, System 76, and they asked me for a ""dmesg | grep iwlwifi""."
1793997,2018-09-27 19:33:35 UTC,Started happen to me few days ago as well. Happens with 4.15.0-34-generic and 4.15.0-34-generic.
1793997,2018-09-30 03:50:58 UTC,"I've tested with mainline kernel and it is crashes as well. Also I've tried booting previous Ubuntu releases (4.15.0-20-generic, 4.15.0-29-generic, 4.15.0-32-generic, 4.15.0-33-generic) and bug happens with all of them. This is strange because I've used these kernels without any problems for months. Wi-Fi worked extremely stable until problem recently appeared. So looks like bug was present for long time, however it have not manifested itself. But some non-kernel update uncovered it."
1793997,2018-09-28 05:14:40 UTC,"Although I could boot the mainline kernel, I can't use it, as it doesn't have zfs. Any tips how I can get zfs working? I assume I can't just copy the zfs module?"
1793997,2018-09-27 19:42:49 UTC,I've meant with 33 and 34.
1793997,2018-09-26 21:05:59 UTC,I think I may have seen it in 17.10.
1793997,2018-09-26 19:41:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1793997,2018-09-25 11:36:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1793997,2018-09-24 04:20:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1793997,2018-10-02 21:31:30 UTC,Latest Ubuntu kernel 4.15.0-36 is even more unstable. Can last only 24 hours before it crashes. Here is the latest log:
1793997,2018-09-24 00:03:24 UTC,"lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic"
1793998,2018-09-26 19:42:42 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1793998,2018-09-24 00:30:05 UTC,This change was made by a bot.
1793998,2018-09-26 20:30:31 UTC,I have confirmed that the latest mainline kernel does indeed fix the SD card and it reads just fine again with 4.19-rc5.
1793999,2019-04-26 17:48:46 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/604669
Reason: we no longer use repo_build!"
1794000,2018-09-24 01:35:26 UTC,I've attached a screenshot example from our production dashboard.
1794000,2019-12-25 09:19:58 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/700554"
1794000,2019-12-25 09:20:35 UTC,"Change abandoned by Ziyu Bai (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/700554"
1794000,2019-12-25 09:32:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/700557"
1794000,2020-01-07 02:52:43 UTC,"Reviewed:  https://review.opendev.org/700557
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=6d149b0e8138611516b652cf6b8157725f717048
Submitter: Zuul
Branch:    master"
1794000,2020-01-09 18:46:50 UTC,This issue was fixed in the openstack/horizon 18.0.0 release.
1794001,2018-09-24 01:39:32 UTC,"StacktraceTop:
 search_provider_solve_equation_co (_data_=0x55b94eb6e120) at search-provider/search-provider@@gnome-calculator-search-provider@exe/search-provider.c:2025
 g_task_return_now (task=0x55b94eb70a80) at ../../../../gio/gtask.c:1148
 g_task_return (task=0x55b94eb70a80, type=<optimized out>) at ../../../../gio/gtask.c:1206
 g_subprocess_communicate_made_progress (source_object=0x55b94eb725b0, result=0x55b94eb70dc0, user_data=0x55b94eb70a80) at ../../../../gio/gsubprocess.c:1523
 g_task_return_now (task=0x55b94eb70dc0) at ../../../../gio/gtask.c:1148"
1794001,2018-10-02 14:24:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794003,2018-09-30 15:01:38 UTC,^symbols^footprints^
1794003,2018-09-30 15:01:22 UTC,Or just support rectangles.  They're pretty common in symbols too.
1794003,2018-09-24 12:23:14 UTC,"Agree that a plugin could even add more shapes such ""polygon"" (definition the number of sides).
But the square is the most common shape used to PCBs by the KiCad users. This could add a little improvement in UX."
1794003,2018-09-24 02:44:06 UTC,Hmm... I think your idea is better handled by a script that generates a rectangle.  Special cases for general tools end up being very confusing.
1794006,2019-05-28 20:43:59 UTC,"When there is no network connection, error message should mention about network connection problem."
1794006,2019-06-28 20:10:22 UTC,That is the pull request of this issue.
1794013,2018-09-24 10:05:05 UTC,"Are you sure Kicad crashes?
It looks to me this is a wxWidgets assert info (shown in debug mode), and not a crash."
1794013,2018-09-24 10:23:32 UTC,"You are correct, this is not a crash-inducing bug. Attempting to exit the
wxWidgets failed assertion dialogue closes KiCAD as it should."
1794013,2018-09-24 10:27:02 UTC,"I have corrected the bug's title. Since this is an error relatively deep in the interface, it probably should not be marked Critical."
1794013,2018-09-24 18:13:03 UTC,It's a wxWidgets bug (https://trac.wxwidgets.org/ticket/18186).
1794013,2018-09-24 18:15:06 UTC,"What do we usually do with these?  Mark them ""Won't Fix"" or ""Invalid"", or leave them open till we upgrade to the relevant version of wxWidgets?"
1794013,2018-09-24 19:04:04 UTC,"@Jeff, we don't really have a policy but I guess it should stay open until we make the minimum wxWidgets version 3.1.2 or greater."
1794015,2019-09-02 19:20:45 UTC,"Can you confirm that an autostart file was correctly created at ~/.config/autostart/variety.desktop and that it's enabled in your session settings? The CalledProcessError bit is fixed in 0.7.2-1 (as well as in the nightly builds), but shouldn't actually be related to this because it doesn't cause Variety to exit."
1794017,2018-09-24 07:46:22 UTC,"Hi Adam,
the new dispatcher must restart the session with the same name of the dispatcher that saved the session in the first computer.
Anyhow, if you want help, you need to provide the full OpenRailsLog.txt file and not only the .png file."
1794028,2019-12-16 19:10:20 UTC,This issue was fixed in the openstack/horizon 17.1.0 release.
1794028,2019-11-28 13:31:12 UTC,"Reviewed:  https://review.opendev.org/693148
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8a984300eb71317109717b7fbcb9c388d336e764
Submitter: Zuul
Branch:    master"
1794032,2018-10-03 11:12:56 UTC,"Hi,"
1794032,2018-10-03 12:14:48 UTC,">share the screenshot of hp logo in ubuntu 18.04
What do you mean about screenshot? I send you a screenshot from when I click on the logo, nothing appears just a little white part :)
"
1794032,2018-10-03 15:37:06 UTC,"I did a new screenshot on Mate, you can see better."
1794033,2019-03-12 05:27:16 UTC,"(In reply to Yoshinori Gento from comment #18)

> I saw this once.


This occurred in our product."
1794033,2019-03-12 15:18:29 UTC,"Yoshinori: Mesa i965 team is seeking a way to reproduce this bug, so we can analyze and fix it."
1794033,2019-03-13 03:17:16 UTC,"(In reply to Mark Janes from comment #20)

> Yoshinori: Mesa i965 team is seeking a way to reproduce this bug, so we can
> analyze and fix it.
>
> How often does this occur in your product?  If it is reproducible, then
> perhaps we can use an apitrace to investigate the root cause.
"
1794033,2019-03-13 15:38:22 UTC,Hmm...`cp` in xterm is a pretty clear indicator that this issue is random and not triggered by a specific workload.
1794033,2019-03-14 11:36:34 UTC,"(In reply to Mark Janes from comment #22)

> Hmm...`cp` in xterm is a pretty clear indicator that this issue is random
> and not triggered by a specific workload.
>
> Lionel suggested that it would be good to have a feedback from the kernel
> about what didn't pass validation.
>
> There is a kernel option to generate debug traces for that but you have to
> recompile your kernel with that option.  Lionel, can you provide some
> details?
>
> It would be a good data point to see if a much older kernel produces this
> error (eg 4.9, 4.4).  I can't deploy those kernels in Mesa i965 CI because
> they lack features needed to run our Vulkan test suites.
"
1794033,2019-03-14 12:19:18 UTC,I haven't encountered this issue at all since moving away from modesetting and back to the intel DDX driver.  So whatever extra exercises GLAMOR was doing may be triggering the bug.  I'm sure that doesn't help actually fix it but it might at least help people experiencing it to have a more stable desktop.
1794033,2019-03-15 11:01:08 UTC,"I saw this problem three times from yesterday.
All of them occurred during file sync over LAN with rsync.
I think this problem might be related to load by disk i/o or network i/o.
But unfortunately I have not re-compiled kernel with CONFIG_DRM_I915_DEBUG_GEM yet.
I will try to it next week."
1794033,2019-03-25 06:41:32 UTC,"Created attachment 143768
Debug trace."
1794033,2019-09-25 19:07:58 UTC,-- GitLab Migration Automatic Message --
1794033,2019-08-29 11:55:03 UTC,"(In reply to Denis from comment #28)

> Hello Yoshinori Gento
>
> >I got how to reproduce.
> Does this mean that you could provide an apitrace or somekind of reproducer?
> It would be really helpful.
"
1794033,2019-11-28 07:26:34 UTC,"TFA above suggests that the change is related to 4.19, but the above shows that 4.15 was also affected.  Does this matter?"
1794033,2020-01-01 00:22:46 UTC,I'm encountering this about once/day on my Lenovo X1 carbon laptop with kernel 5.3.0-24-generic.
1794033,2020-01-02 11:20:46 UTC,Just got this on 19.10 on a thinkpad t470s.
1794033,2020-03-06 11:54:18 UTC,Also encountered this:
1794033,2020-05-08 10:33:55 UTC,"Also facing this issue persistently, always when working with little memory available (as #32)."
1794033,2020-05-08 10:58:49 UTC,Previous issue (https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680) was closed as duplicated of this one.
1794033,2019-03-12 05:21:30 UTC,I saw this once.
1794033,2019-05-07 03:24:19 UTC,I got how to reproduce.
1794033,2019-03-08 11:53:16 UTC,The CI Bug Log issue associated to this bug has been archived.
1794033,2019-08-08 15:26:22 UTC,Hello Yoshinori Gento
1794033,2019-02-16 00:53:52 UTC,Mesa CI reproduce these test failures immediately:
1794033,2019-03-08 11:53:07 UTC,"(In reply to Mark Janes from comment #15)

> Mesa CI reproduce these test failures immediately:
>
> https://mesa-ci.01.org/mesa_master/builds/15252/group/
> 63a9f0ea7bb98050796b649e85481845
>
> Builds have fairly recent kernels:
>
> Linux otc-gfxtest-sklgt2-01 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1
> (2018-12-22) x86_64 GNU/Linux
"
1794033,2018-01-31 14:59:20 UTC,"Do we know what kernel version is running on the machines with failures?  We do slightly different things on v4.13 and later.  Wondering if it's only happening on machines with older kernels, or newer ones, or both."
1794033,2018-01-31 16:42:44 UTC,Unfortunately I saw this recently on 4.14 and 4.11
1794033,2018-03-23 10:51:40 UTC,"Running piglit.shaders.glsl-fs-raytrace-bug27060, I found this valgrind warning : https://patchwork.freedesktop.org/patch/212413/"
1794033,2018-03-23 13:42:29 UTC,"The Broadwell failure is interesting as it's clearly a memory corruption issue.
Running the dEQP-GLES31.functional.debug.* tests under valgrind, I can see a few errors from the CTS suite :"
1794033,2018-04-15 02:12:18 UTC,"I just had my Gnome desktop crash and the only info in the log was:
i965: Failed to submit batchbuffer: Bad address"
1794033,2018-05-03 18:33:38 UTC,I've also encountered some desktop crashes lately with
1794033,2018-05-23 05:36:21 UTC,*** Bug 106621 has been marked as a duplicate of this bug. ***
1794033,2018-01-24 22:47:15 UTC,"Mesa CI reports a low error rate (2/700k), however the number of intermittent failures is consistently nonzero.  This is worse than our historical results."
1794033,2018-04-15 17:23:08 UTC,"It's clear to me that this bug is not simply ""CI ghosts"".  We have a bug in Mesa which is hard to trigger, and we hit it very occasionally with the exhaustive CI infrastructure."
1794033,2018-10-25 15:58:44 UTC,also happened with
1794033,2018-10-29 15:42:48 UTC,One of the tests that seems to reproduce this more often than others:
1794033,2018-11-01 15:12:22 UTC,"We hit this bug twice in a week, and then nothing since then (5 months and 1 week). I wonder if newer kernels fixed this issue. What is the most up to date kernel that has shown this issue?"
1794033,2019-02-14 21:55:16 UTC,"The problematic tests have been disabled in mesa ci since June 2018.  If you think this is fixed, than I can re-enable them."
1794033,2018-11-01 15:43:52 UTC,"4.18.  If you have a suggestion for what to run, I'll update."
1794033,2018-11-01 16:19:17 UTC,"(In reply to Mark Janes from comment #11)

> 4.18.  If you have a suggestion for what to run, I'll update.
"
1794033,2018-12-17 21:16:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794033,2018-12-17 21:18:05 UTC,"Just hit me, kernel 4.19.8-liquorix-amd64, Ubuntu 18.10.   I was running with modesetting, but decided to change to intel driver (freshly compiled from git) to see if I run into it again (it seems pretty rare though so will probably be tough to hit).  Has anyone definitely hit it on xf86-video-intel or only modesetting?"
1794033,2019-02-14 09:37:14 UTC,"Last seen this issue on our CI system is 8 months, 3 weeks / 4968 runs ago.
Can we close this issue?"
1794033,2018-10-03 06:35:18 UTC,I just had this exact problem. Was watching a facebook video on chrome when everything crashed.
1794036,2020-02-18 23:45:21 UTC,"Unfortunately the repo for repcached looks to be unmaintained, and there's no supported package for this software.  In light of that, I'll mark this as wontfix."
1794040,2018-09-25 10:03:35 UTC,Its a mainline ppa problem...
1794040,2018-09-24 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794041,2018-12-18 00:14:54 UTC,"On Mon, Dec 17, 2018 at 08:31:22PM -0000, Richard Elkins wrote:

> Any work-around/patch in 18.04.1 LTS?
"
1794041,2019-12-17 18:56:00 UTC,"I tried to do ""twine upload dist/*"" in terminal and also came upon the error ""ModuleNotFoundError: No module named 'keyring.util.escape'"" (which also led to another exception call...)"
1794041,2019-11-23 00:41:46 UTC,"I landed here from searching ""ModuleNotFoundError: No module named 'keyring.util.escape'"""
1794041,2019-11-01 21:35:42 UTC,"I landed a change relating to this.  I think the original issue was worked around in the snap package (c.f. comment #7) by pinning the version, however the issue appears to be resolved upstream.  In any case, our snaps are pulling a newer version of keyring.util, which pip3 check flagged as inconsistent.  I've updated the requirement to exclude the keyring.util package version with this bug, but allow any newer versions."
1794041,2019-09-19 18:04:10 UTC,The following was the fix that I found at https://github.com/jrnl-org/jrnl/issues/558:
1794041,2018-12-17 20:31:22 UTC,Any work-around/patch in 18.04.1 LTS?
1794041,2018-09-26 15:12:58 UTC,Simpler reproducer:
1794041,2018-09-27 12:08:09 UTC,"keyring 15.0.0 removed keyring.util.escape; keyrings.alt started using its own version in keyrings.alt 3.1. setup.py specifies keyrings.alt 2.3 but doesn't require anything about keyring. So we're now building with a newer version of keyring but an older version of keyrings.alt. I guess Python modules can't declare the equivalent of ""Breaks"", so that's what's caused the breakage."
1794041,2018-09-24 17:41:18 UTC,"I can also confirm that 433 v 434, the following path disappears:"
1794041,2018-09-24 17:17:01 UTC,I think we pick up the keyring package from either LP or pypi. Possibly something changed/broke there and it should be pinned into our source (by version) like keyrings.alt is.
1794041,2018-09-24 17:09:26 UTC,r433 does not have this problem:
1794041,2018-09-24 16:52:39 UTC,"nacc@pitfall:~$ snap run --shell git-ubuntu
nacc@pitfall:~$ cd $SNAP
nacc@pitfall:/snap/git-ubuntu/434/lib/python3.6$ which python3
/snap/git-ubuntu/434/usr/bin/python3
nacc@pitfall:/snap/git-ubuntu/434/lib/python3.6$ python3
Python 3.6.3 (default, Sep 19 2018, 23:13:33)
[GCC 5.4.0 20160609] on linux
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> import keyring.util.escape
Error initializing plugin EntryPoint('Windows (alt)', 'keyrings.alt.Windows', None, Distribution('keyrings.alt', '2.2')).
Traceback (most recent call last):
  File ""/snap/git-ubuntu/434/lib/python3.6/site-packages/keyring/backend.py"", line 163, in _load_plugins
    init_func = ep.load()
  File ""/snap/git-ubuntu/434/lib/python3.6/site-packages/entrypoints.py"", line 77, in load
    mod = import_module(self.module_name)
  File ""/snap/git-ubuntu/434/usr/lib/python3.6/importlib/__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File ""<frozen importlib._bootstrap>"", line 994, in _gcd_import
  File ""<frozen importlib._bootstrap>"", line 971, in _find_and_load
  File ""<frozen importlib._bootstrap>"", line 955, in _find_and_load_unlocked
  File ""<frozen importlib._bootstrap>"", line 665, in _load_unlocked
  File ""<frozen importlib._bootstrap_external>"", line 678, in exec_module
  File ""<frozen importlib._bootstrap>"", line 219, in _call_with_frames_removed
  File ""/snap/git-ubuntu/434/lib/python3.6/site-packages/keyrings/alt/Windows.py"", line 9, in <module>
    from . import file_base
  File ""/snap/git-ubuntu/434/lib/python3.6/site-packages/keyrings/alt/file_base.py"", line 12, in <module>
    from keyring.util.escape import escape as escape_for_ini
ModuleNotFoundError: No module named 'keyring.util.escape'
Error initializing plugin EntryPoint('file', 'keyrings.alt.file', None, Distribution('keyrings.alt', '2.2')).
Traceback (most recent call last):
  File ""/snap/git-ubuntu/434/lib/python3.6/site-packages/keyring/backend.py"", line 163, in _load_plugins
    init_func = ep.load()
  File ""/snap/git-ubuntu/434/lib/python3.6/site-packages/entrypoints.py"", line 77, in load
    mod = import_module(self.module_name)
  File ""/snap/git-ubuntu/434/usr/lib/python3.6/importlib/__init__.py"", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File ""<frozen importlib._bootstrap>"", line 994, in _gcd_import
  File ""<frozen importlib._bootstrap>"", line 971, in _find_and_load
  File ""<frozen importlib._bootstrap>"", line 955, in _find_and_load_unlocked
  File ""<frozen importlib._bootstrap>"", line 665, in _load_unlocked
  File ""<frozen importlib._bootstrap_external>"", line 678, in exec_module
  File ""<frozen importlib._bootstrap>"", line 219, in _call_with_frames_removed
  File ""/snap/git-ubuntu/434/lib/python3.6/site-packages/keyrings/alt/file.py"", line 11, in <module>
    from keyring.util.escape import escape as escape_for_ini
ModuleNotFoundError: No module named 'keyring.util.escape'
Error initializing plugin EntryPoint('pyfs', 'keyrings.alt.pyfs', None, Distribution('keyrings.alt', '2.2')).
Traceback (most recent call last):
  File ""/snap/git-ubuntu/434/lib/python3.6/site-packages..."
1794041,2018-10-11 12:13:17 UTC,This should be in edge now - r436.
1794042,2018-09-24 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794053,2018-10-25 15:29:32 UTC,This bug was fixed in the package apt - 1.2.29
1794053,2018-10-25 15:21:10 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1794053,2018-10-25 15:20:52 UTC,This bug was fixed in the package apt - 1.6.6
1794053,2018-10-18 12:18:26 UTC,"xenial
======"
1794053,2018-10-17 22:26:33 UTC,"Hello Julian, or anyone else affected,"
1794053,2018-10-17 22:34:35 UTC,"Hello Julian, or anyone else affected,"
1794053,2018-10-01 18:35:37 UTC,"Hello Julian, or anyone else affected,"
1794053,2018-10-01 17:12:49 UTC,"Hello Julian, or anyone else affected,"
1794053,2018-09-25 11:33:33 UTC,This bug was fixed in the package apt - 1.7.0~rc2ubuntu1
1794053,2018-10-18 12:11:38 UTC,bionic (1.6.3ubuntu0.1 -> 1.6.6):
1794059,2018-12-04 08:44:36 UTC,"Whatever it was is resolved now, the recent strongswan builds worked fine"
1794059,2018-12-04 15:50:32 UTC,"Ha I spoke too soon, i386 it is
Still hit by this issue ..."
1794059,2018-12-04 15:30:12 UTC,Working fine now for ruby as well https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3552/+build/15737990
1794059,2018-09-25 20:54:38 UTC,retried ruby2.5 build 4 times in the archive now.
1794059,2018-09-25 05:56:17 UTC,Strongswan hit a rather similar issue with a build time test timing out that was always fine in the past and now seems flaky (worked on retry).
1794059,2018-09-25 05:16:46 UTC,I didn't want to retrigger your upload since I don't own it.
1794059,2018-09-25 05:14:52 UTC,"I reported the same a few hours before, duping mine to your bug ..."
1794059,2018-09-24 12:44:49 UTC,[FAILEDTOBUILD] Failed to build on lgw01-amd64-033 Retry this build
1794059,2018-09-25 05:15:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794061,2018-09-30 13:03:31 UTC,"This should also get a tool-tip stating ""No current objectives""."
1794061,2019-09-16 13:56:48 UTC,Migrated to https://github.com/widelands/widelands/issues/2118
1794064,2018-09-24 10:38:50 UTC,"Note that this works with the evince snap, only the deb package is affected."
1794064,2018-09-24 11:00:38 UTC,"I can ""fix"" the issue if I add the following two lines to /etc/apparmor.d/abstractions/ubuntu-browsers and reload the evince profile:"
1794064,2018-09-25 13:44:25 UTC,I went through this the other day with a personal profile. We probably can do something along the lines of:
1794064,2018-10-04 07:35:10 UTC,"@Jamie, given your recent work on the evince apparmor profile, should that be assigned to you?"
1794064,2019-10-31 21:01:06 UTC,After transition to snap the Chromium is not usable for me. I have a lot of PDFs with hyperlinks and they stopped working. Is there any workaround other then migrating to deb Chrome?
1794067,2018-10-11 19:17:17 UTC,"Can you next test 4.15.0-18:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+build/14779251"
1794067,2018-10-12 06:35:16 UTC, 4.15.0-18 does not work
1794067,2018-10-12 11:38:54 UTC,"There is no -16 kernel, so the last one to test before bisecting would be 4.15.0-17:"
1794067,2018-10-12 13:00:01 UTC,4.15.0-17 does also not work
1794067,2019-05-16 10:50:58 UTC,"Suffering from this as well, making kernel upgrades on serveral machines quite hard (need to boot with selinux=0).
I can reproduce the failure with the steps above on 4.15.18-38, while Debian buster/sid with 4.19.28-2 doesn't show the problem."
1794067,2018-10-16 05:13:46 UTC,"no, does not"
1794067,2018-12-07 05:00:41 UTC,"This also affects me on Ubuntu 18.04, kernel 4.15.0-39."
1794067,2018-10-11 09:18:19 UTC,"the last working version is 4.15.0-15,
the version 4.15.0-20 has the bug"
1794067,2018-10-15 15:28:38 UTC,There are a bunch of LSM stacking changes in 4.15.0-16 that may be the cause.
1794067,2018-10-10 13:27:57 UTC,Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:
1794067,2018-09-24 11:05:38 UTC,It does not occur on a mainline kernel
1794067,2018-10-09 18:31:53 UTC,"We may have to test some prior kernel to have a starting version for a bisect.  Before starting a bisect, would it be possible for you to test the proposed kernel and post back if it resolves this bug?"
1794067,2018-10-08 09:30:31 UTC,I've no clue in which kernel version it started...
1794067,2018-10-04 15:35:14 UTC,"Commit 36788bfe15f1 was applied to Bionic in kernel version: Ubuntu-4.15.0-16.  Do you happen to know the last kernel version that did not exhibit this bug?  If not, we can try a kernel bisect to identify the commit that caused this."
1794067,2018-10-03 13:46:17 UTC,the problem does not exist on the mainline kernel
1794067,2018-10-01 19:02:06 UTC,"The test kernel I posted is built on top of upstream 4.15.18.  To confirm this is an Ubuntu specific bug, can you test 4.15.18?  It can be downloaded from:"
1794067,2018-09-27 10:45:24 UTC,"no, does not solve the issue"
1794067,2018-09-26 22:50:43 UTC,"I built a test kernel with a revert of commit 36788bfe15f16b2eba.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794067"
1794067,2018-09-26 20:59:52 UTC,I'll build a test kernel with the commit posted in #4 reverted so see if that is the cause.
1794067,2018-09-24 11:17:45 UTC,FYI:
1794067,2018-09-24 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794067,2018-10-10 07:15:55 UTC,the linux-image-4.15.0-37-generic kernel from proposed has also the same problem
1794072,2020-03-29 08:06:33 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1794072,2018-09-25 12:28:06 UTC,"> Just a copy-paste of my answer posted in the mailing list:
"
1794072,2018-09-25 09:12:48 UTC,"Hi Jürgen.
This is not posible on this kind of files but I undertand he want a reference of the file location used on import, not autoupdate on file change. I added this also for embebed files like images that can easy be marked his original location."
1794072,2018-09-25 07:34:42 UTC,"When importing a PNG file, I can chose between (*) embed or ( ) link.
Selecting (*) link allows editing the original image and then have it automatically updated in inkscape, by e.g. restarting or re-opening."
1794072,2018-09-24 15:37:40 UTC,How to handle this and another embeded files? we need to ask to the user if want to include a description tag to the imported root element with the origin of the file?
1794072,2018-09-25 10:37:56 UTC,Just a copy-paste of my answer posted in the mailing list:
1794074,2018-10-19 19:33:02 UTC,"There is another bug like this, to which I added some more info:"
1794074,2018-10-09 18:00:09 UTC,This change was made by a bot.
1794074,2018-10-02 22:50:34 UTC,"[16205.365224] perf: interrupt took too long (3736 > 2500), lowering kernel.perf_event_max_sample_rate to 53500
[18209.636450] xhci_hcd 0000:10:00.0: ERROR unknown event type 15
[18214.741280] xhci_hcd 0000:10:00.0: xHCI host not responding to stop endpoint command.
[18214.774794] xhci_hcd 0000:10:00.0: Host halt failed, -110
[18214.774796] xhci_hcd 0000:10:00.0: xHCI host controller not responding, assume dead
[18214.774823] xhci_hcd 0000:10:00.0: HC died; cleaning up"
1794074,2018-10-02 22:49:11 UTC,I am having the same problem
1794074,2018-09-27 12:12:35 UTC,apport information
1794074,2018-09-27 12:12:39 UTC,apport information
1794074,2018-09-27 12:12:38 UTC,apport information
1794074,2018-09-27 12:12:36 UTC,apport information
1794074,2018-09-27 12:12:34 UTC,apport information
1794074,2018-09-27 12:12:41 UTC,apport information
1794074,2018-09-27 12:12:31 UTC,apport information
1794074,2018-09-24 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794074,2018-09-26 20:50:34 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1794074,2018-09-27 12:12:23 UTC,apport information
1794074,2018-09-27 12:12:25 UTC,apport information
1794074,2018-09-27 12:12:33 UTC,apport information
1794074,2018-09-27 12:12:27 UTC,apport information
1794074,2018-09-27 12:12:28 UTC,apport information
1794074,2018-09-27 12:12:29 UTC,apport information
1794074,2018-09-27 12:12:30 UTC,apport information
1794074,2018-09-27 12:12:26 UTC,apport information
1794075,2019-02-15 08:48:11 UTC,I ran into the same problem. From what I gathered the problem is the bootstrap of mariadb
1794075,2019-03-04 07:32:12 UTC,"So, I thought I'd post my workaround for everybody else who runs into that problem:"
1794075,2018-12-25 13:59:23 UTC,"Hi,"
1794080,2018-09-28 23:22:21 UTC,We should consider allowing users to upload and store cloud-init user-data in addition to supplying it at deployment time.
1794080,2019-03-22 19:39:00 UTC,The process described at https://docs.maas.io/2.5/en/nodes-custom#cloud-init needs a GUI solution.
1794080,2019-09-19 14:47:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1794080,2019-10-07 18:24:49 UTC,"Thanks for the suggestion. We've recently moved discussion of all new
features to https://discourse.maas.io/c/features Could you please post
there?"
1794080,2019-10-07 18:35:29 UTC,https://discourse.maas.io/t/allow-passing-cloud-init-user-data-on-deployment-and-power-on-via-ui/1061
1794084,2018-11-06 22:13:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794085,2018-10-06 13:47:14 UTC,"TY for your time and attention, updating Ubuntu some days after solved this."
1794085,2018-09-24 15:06:32 UTC, Can't reproduce this. Please try with a fresh install.
1794086,2020-11-12 06:26:07 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1794088,2018-09-24 13:30:06 UTC,This change was made by a bot.
1794088,2018-09-26 20:49:44 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.compo/Testing/EnableProposed for documentation how to enable and use -proposed."
1794088,2018-09-27 12:26:18 UTC,"Yes, sure."
1794088,2018-09-27 12:26:38 UTC,https://wiki.ubuntu.com/Testing/EnableProposed is the correct link.
1794088,2018-10-02 15:36:40 UTC,Sorry for the typo.
1794092,2018-09-24 13:26:39 UTC,"In case the code changes, the latest version of this patch can also be found there:
https://github.com/fgouget/hplip/commits/fixes"
1794092,2018-10-03 11:10:19 UTC,"Hi,"
1794095,2018-10-03 11:10:06 UTC,"Hi,"
1794096,2018-10-03 11:09:50 UTC,"Hi,"
1794097,2018-10-03 11:09:37 UTC,"Hi,"
1794098,2018-10-03 11:09:15 UTC,"Hi,"
1794099,2018-10-03 11:09:04 UTC,"Hi,"
1794100,2018-10-03 11:08:53 UTC,"Hi,"
1794101,2018-10-03 11:08:39 UTC,"Hi,"
1794106,2018-10-03 11:08:18 UTC,"Hi,"
1794108,2018-10-03 11:07:37 UTC,"Hi,"
1794110,2020-04-06 14:25:54 UTC,Both of these patches are in Focal so I am going to close this bug
1794110,2018-10-10 13:36:08 UTC,"Thanks for the feedback.  If you can get a list of additional commits that are needed in Bionic, that would be great.  An alternative would be for us to perform a reverse bisect, but that would require a lot of testing and be time consuming."
1794110,2018-10-09 18:32:49 UTC,Do you happen to know which commits are also needed in Bionic?
1794110,2018-10-10 05:37:28 UTC,"@jsalisbury -
Unfortunately we do not have that info in hand. I'll check if we can try getting it."
1794110,2018-10-09 12:44:57 UTC,"The cosmic test-kernel based on v4.18 is a Pass.
Please include them in planned HWE kernels of 18.04.2 that is based on v4.18."
1794110,2018-10-01 17:58:10 UTC,"The test kernel posted in comment #2 is for cosmic.  Bionic needs some backporting, so I'll post that test kernel shortly."
1794110,2018-10-02 00:22:27 UTC,A bionic test kernel is also available with commits 3dbe97efe8bf and 9f0e89359775 applied.
1794110,2018-10-01 17:59:22 UTC,"Also, cosmic already has commit 3dbe97efe8bf applied, so the test kernel just needed commit 9f0e89359775."
1794110,2018-10-01 17:57:40 UTC,"I built a test kernel with the two requested commits.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794110/cosmic"
1794110,2018-09-24 14:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794110,2018-10-02 11:59:35 UTC,"Thank you for sharing a test-kernel.
We will test it and revert back here with test-results."
1794126,2018-10-08 21:50:39 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1794126,2018-10-04 03:11:55 UTC,"Reviewed:  https://review.openstack.org/604817
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0c9bd9ce6e0fe9eb6e8e2a16fe04615662a4f0f0
Submitter: Zuul
Branch:    stable/queens"
1794126,2018-09-24 15:22:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/604817"
1794133,2018-10-07 09:53:41 UTC,"Hi Petr, I'm not active on this project, but I do like it and use it sometimes, just a couple comments below to help you out with this contribution. :)"
1794139,2019-02-27 09:53:14 UTC,Upstream reopened it
1794140,2018-09-24 17:05:55 UTC,I think this is a duplicate of bug 1789263
1794140,2019-04-26 11:51:47 UTC,Setting the stat cat to an empty entry results in an actual row for that patron in the table actor.stat_cat_entry_usr_map. This might not be desired. The ability to delete the existing entry completely for the given patron account is what I am hoping this bug addresses.
1794142,2018-09-25 18:07:48 UTC,"This may be a false alarm, when going through the yaml file in /etc/netplan on the MAAS VM and I noticed that the nameserver for the internal network was configured for an external network. I had Cisco remove those settings from the 172.x.x.x network entry.  I should have confirmation tomorrow if this was in fact the issue.  It now makes sense to me as to why the traffic was not resolved through the maas server once it was NAT'ed regardless of the hack. The yaml file now resembles the following:"
1794142,2020-05-11 20:08:45 UTC,"Is this still an issue, or was this resolved by updates to MAAS or Maniacs-setup?"
1794142,2018-09-24 19:49:29 UTC,Some additional information
1794142,2018-09-24 17:26:14 UTC,The following lines in startnat.sh SHOULD be setting the values correctly:
1794142,2018-09-24 18:31:08 UTC,"Michael, can you get with Cisco and re-verify this, or verify the behaviour we think we saw today."
1794142,2018-09-24 16:49:35 UTC,"Before running modified maniacs-setup
ubuntu@ubuntu-s-2vcpu-4gb-nyc3-01:~$ cat /usr/sbin/startnat.sh
#!/bin/sh"
1794142,2018-09-24 19:10:26 UTC,"I will verify this issue on the Cisco set up tomorrow.  I have seen this issue in the past using VM's  and typically changing the the values of INTERNAL_NET and EXTERNAL_NET in /usr/sbin/startnat.sh has worked to get the from the SUT, to the outside world, via the MAAS VM.  Typically I have had to make this change and re-run the script after power interruptions or rebooting the MAAS VM."
1794145,2018-09-24 16:41:29 UTC,"StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x55dc25d151a0 <__func__.66233> ""nautilus_directory_finalize"", message=<optimized out>) at ../../../../glib/gtestutils.c:2596
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x55dc25d146ed ""../src/nautilus-directory.c"", line=line@entry=201, func=func@entry=0x55dc25d151a0 <__func__.66233> ""nautilus_directory_finalize"", expr=expr@entry=0x55dc25d149c8 ""directory->details->file_list == NULL"") at ../../../../glib/gtestutils.c:2619
 nautilus_directory_finalize (object=0x7f2cdc010630) at ../src/nautilus-directory.c:201
 g_object_unref (_object=0x7f2cdc010630) at ../../../../gobject/gobject.c:3346
 nautilus_directory_unref (directory=<optimized out>) at ../src/nautilus-directory.c:360"
1794145,2019-01-25 14:19:30 UTC,Similar fedora report on 3.30 https://bugzilla.redhat.com/show_bug.cgi?id=1634432
1794145,2019-01-25 14:19:49 UTC,The issue should be reported upstream on https://gitlab.gnome.org/GNOME/nautilus/issues
1794159,2018-09-24 18:47:24 UTC,"I wonder if this could be configurable behavior.  We really prefer the current behavior, because it prevents our staff from doing more manual work.  The EDI Invoices come in, correct the prices without our staff having to worry about them, and then we don't have a process of Saving or Closing invoices."
1794159,2018-09-24 19:08:34 UTC,"Jane, I'm okay with the invoices having the corrected amount--that's definitely okay! I don't want to increase work in that way. I'm thinking more that the fund debit itself shouldn't be modified until the invoice is saved and/or closed for the first time. When you say you don't have a process of saving or closing invoices--do your staff not close invoices?"
1794159,2018-09-25 00:12:03 UTC,"Correct, we don't close invoices.  We only use EDI invoices to correct the fund debits themselves; we're not actually very concerned with viewing or working with the invoices in Evergreen.  So, kind of the exact opposite of your use case, I think. :-)"
1794159,2018-09-25 11:48:09 UTC,"So do your funds stay encumbered forever? Are you just not looking at encumbered vs spent? (Hopefully not veering too off topic, but I'm interested. I literally never thought of not closing invoices!)"
1794159,2018-09-26 16:21:42 UTC,"Yeah, I guess the funds never stop being encumbered for us.  It is nice that the encumbrance gradually gets more and more correct as EDI invoices come in, I guess. :-D"
1794162,2018-10-03 09:28:12 UTC,"Hi,"
1794169,2018-09-25 22:50:15 UTC,Not sure whether the issue is a poor interaction with sd-pam and the kernel or strictly a kernel issue.
1794169,2018-09-26 16:43:03 UTC,information attached and status changed.
1794169,2018-09-26 16:36:18 UTC,apport information
1794169,2018-09-26 16:36:17 UTC,apport information
1794169,2018-09-26 16:36:15 UTC,apport information
1794169,2018-09-26 16:36:14 UTC,apport information
1794169,2018-09-25 23:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794169,2018-09-26 16:36:11 UTC,apport information
1794169,2018-09-26 16:36:10 UTC,apport information
1794169,2018-09-26 16:36:08 UTC,apport information
1794169,2018-09-26 16:36:07 UTC,apport information
1794169,2018-09-26 16:36:05 UTC,apport information
1794169,2018-09-26 16:36:12 UTC,apport information
1794175,2018-10-22 17:22:19 UTC,This bug was fixed in the package linux-aws - 4.15.0-1025.25
1794179,2018-10-26 20:06:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613681"
1794179,2019-09-24 16:02:30 UTC,"Change abandoned by Morgan Fainberg (<email address hidden>) on branch: master
Review: https://review.opendev.org/613681"
1794179,2018-10-24 18:14:17 UTC,This looks great and we totally would like to have this fix in keystonemiddleware. Can you submit the patch to our gerrit: review.openstack.org ? Thanks!
1794186,2019-07-20 08:30:31 UTC,This is fixed in Debian unstable:
1794186,2019-07-20 08:27:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794187,2019-03-28 10:22:26 UTC,I've submitted a patch to the list: http://patchwork.ozlabs.org/patch/1067963/
1794187,2019-07-08 15:19:39 UTC,Improved diagnostic message is now in master and will be in QEMU 4.1.
1794187,2019-08-16 04:56:50 UTC,"Fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=ff3dcf28c0b7a3ac261"
1794191,2018-09-25 13:15:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794191,2018-09-25 14:40:58 UTC,That's the upstream behavior of gnome-software.  You have the click on back button up top.  If we want to consider changing that we'll need some design work and review.
1794191,2018-09-26 02:05:06 UTC,"The back button on top doesn't respond, but the snap store reverts back to the main page after reboot and did work properly for one installation before getting stuck on the application installation page again."
1794194,2020-06-08 20:52:41 UTC,"Thanks, there is a similar request in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962363"
1794194,2020-05-30 22:49:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794194,2020-06-06 18:51:29 UTC,"This is a debdiff for bionic. I built this in pbuilder and it builds successfully. I verified that the static library is in the libopenjp2-7-dev deb with ""dpkg --listfiles""."
1794194,2020-06-06 20:24:30 UTC,"The attachment ""1-20.18.04.ubuntu1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1794201,2020-12-29 22:23:54 UTC,"Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted."
1794213,2019-02-27 13:09:31 UTC,"I forgot to mention: of course, network connectivity is given.
And the system is up-to-date."
1794213,2019-02-27 13:13:48 UTC,"OK, so /var/cache/app-info/ exists before and after software-updater runs. But it does not exist in between while it prepáres the upgrade."
1794213,2018-09-26 03:06:30 UTC,"I ran sudo apt-get autoclean, and other command line clean up tools and
tried again."
1794213,2019-02-27 12:52:37 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-02-12 (380 days ago)
InstallationMedia: Ubuntu 17.10 ""Artful Aardvark"" - Release amd64 (20180105.1)
Package: appstream 0.12.0-3
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Tags: bionic third-party-packages
Uname: Linux 4.15.0-32-generic x86_64
UpgradeStatus: Upgraded to bionic on 2019-02-27 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf
_MarkForUpload: True"
1794213,2019-02-27 12:48:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794213,2020-01-18 19:12:00 UTC,"This is resolved in `appstream >= 0.12.7` (since the code doesn't exist there anymore). The original issue was likely caused by AppStream not handling broken metadata correctly, which is an area that has also been improved greatly."
1794213,2019-02-27 12:52:37 UTC,apport information
1794213,2019-02-27 12:48:30 UTC,"I can confirm, experiencing the same."
1794213,2019-02-27 12:52:38 UTC,apport information
1794225,2018-10-09 06:20:01 UTC,Patch submitted against master: https://review.openstack.org/#/c/604971/
1794225,2019-09-12 18:55:42 UTC,"Reviewed:  https://review.opendev.org/604971
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=915ac7ea172688e508e5087ecaa781dc92632e02
Submitter: Zuul
Branch:    master"
1794225,2019-09-18 15:36:28 UTC,This issue was fixed in the openstack/glance 19.0.0.0b1 development milestone.
1794229,2018-09-25 05:40:37 UTC,It appears these packages are in main but mainly pulled in (at least on my system) by 'devscripts'. This affects cosmic.
1794229,2018-09-25 05:53:52 UTC,"Looks like the recent astroid rebuild/changes removed the file, but it's still present in alembic"
1794230,2018-09-25 07:20:01 UTC,I get the same on my 16.04 test server.
1794230,2018-09-25 07:16:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794232,2019-07-22 15:39:27 UTC,Verified on Xenial
1794232,2019-07-03 11:05:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1794232,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1794232,2019-06-26 09:04:40 UTC,"As the test kernel with the backported Xenial fix
has been up for almost 2 months now, I'm submitting
the SRU for Xenial, although I have not received
feedback from original reporter or others."
1794232,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1794232,2019-07-24 20:29:02 UTC,This bug was fixed in the package linux - 4.4.0-157.185
1794232,2019-05-21 07:32:55 UTC,"Bionic, Cosmic kernels successfully tested.
I've updated the tags."
1794232,2019-05-09 06:11:15 UTC,A 4.4 test kernel with the fix backported is available at:
1794232,2019-05-16 15:03:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1794232,2019-05-08 01:19:00 UTC,"Resubmitted SRU for B,C for this kernel cycle."
1794232,2019-04-17 14:34:38 UTC,"Submitted SRU request for Bionic, Cosmic."
1794232,2019-04-16 10:47:21 UTC,"We had tested a patch discussed above and tested internally,
with success - although we have limited testing (opening up
a geneve tunnel between 2 kvm guests)."
1794232,2018-09-25 07:24:38 UTC,"Logs not necessary at this time, will attach patches and other
information as needed."
1794232,2018-09-25 06:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794232,2019-05-20 14:02:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1794232,2019-04-17 05:03:32 UTC,"I tested a fully up to date cosmic VM using the reproducer steps in the description, and found that I could not create a geneve tunnel when ipv6 is disabled."
1794238,2018-09-27 12:47:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605678"
1794238,2018-09-29 00:23:57 UTC,"Reviewed:  https://review.openstack.org/605678
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=22126f701075c6dacce646c663b8e23551e0c8d8
Submitter: Zuul
Branch:    master"
1794243,2018-09-25 21:02:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794245,2019-01-23 14:45:22 UTC,the upstream commit is https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f9ffcb0a21e1fa8e64d09ed613d884e054ae8191
1794245,2019-01-24 05:43:32 UTC,So the fix lands in kernel >= v4.18.
1794245,2020-06-08 18:08:14 UTC,"I'm getting a possibly similar bug.
Lately, during the first couple of minutes after login, I'm getting terrible mouse freezes every two seconds:
Here is a truncated sample:
juin 08 10:01:57 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) XINPUT: Adding extended input device ""SEMICCHIP Usb Mouse"" (type: MOUSE, id 14)
juin 08 10:01:57 hostn /usr/lib/gdm3/gdm-x-session[3092]: (**) Option ""AccelerationScheme"" ""none""
juin 08 10:01:57 hostn /usr/lib/gdm3/gdm-x-session[3092]: (**) SEMICCHIP Usb Mouse: (accel) selected scheme none/0
juin 08 10:01:57 hostn /usr/lib/gdm3/gdm-x-session[3092]: (**) SEMICCHIP Usb Mouse: (accel) acceleration factor: 2.000
juin 08 10:01:57 hostn /usr/lib/gdm3/gdm-x-session[3092]: (**) SEMICCHIP Usb Mouse: (accel) acceleration threshold: 4
juin 08 10:01:57 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) event17 - SEMICCHIP Usb Mouse: is tagged by udev as: Mouse
juin 08 10:01:57 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) event17 - SEMICCHIP Usb Mouse: device is a pointer
juin 08 10:01:59 hostn kernel: usb 1-1: USB disconnect, device number 125
juin 08 10:01:59 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) config/udev: removing device SEMICCHIP Usb Mouse
juin 08 10:01:59 hostn /usr/lib/gdm3/gdm-x-session[3092]: (**) Option ""fd"" ""82""
juin 08 10:01:59 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) event17 - SEMICCHIP Usb Mouse: device removed
juin 08 10:01:59 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) UnloadModule: ""libinput""
juin 08 10:01:59 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) systemd-logind: releasing fd for 13:81
juin 08 10:01:59 hostn kernel: usb 1-1: new low-speed USB device number 126 using xhci_hcd
juin 08 10:02:00 hostn kernel: usb 1-1: New USB device found, idVendor=1a2c, idProduct=0042, bcdDevice= 1.10
juin 08 10:02:00 hostn kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
juin 08 10:02:00 hostn kernel: usb 1-1: Product: Usb Mouse
juin 08 10:02:00 hostn kernel: usb 1-1: Manufacturer: SEMICCHIP
juin 08 10:02:00 hostn kernel: input: SEMICCHIP Usb Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:1A2C:0042.007A/input/input147
juin 08 10:02:00 hostn kernel: hid-generic 0003:1A2C:0042.007A: input,hidraw0: USB HID v1.10 Mouse [SEMICCHIP Usb Mouse] on usb-0000:00:14.0-1/input0
juin 08 10:02:00 hostn mtp-probe[7409]: checking bus 1, device 126: ""/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1""
juin 08 10:02:00 hostn mtp-probe[7409]: bus: 1, device: 126 was not an MTP device
juin 08 10:02:00 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) config/udev: Adding input device SEMICCHIP Usb Mouse (/dev/input/mouse0)
juin 08 10:02:00 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) No input driver specified, ignoring this device.
juin 08 10:02:00 hostn /usr/lib/gdm3/gdm-x-session[3092]: (II) This device may have been added with another device file.
juin 08 10:02:00 hostn /usr/lib/gdm3/gdm-x-session[1617]: (II) config/udev: Adding input device SEMICCHIP Usb Mouse (/dev/input/mouse0)
juin 08 10:02:00 hostn /usr/lib/gdm3/gdm-x-session[1617]: (II) No input driver specified, ignoring this device.
juin 08 10:02:00 hostn /usr/lib/gdm3/gdm-x-session[1617]: (II) This device may have been added with a..."
1794245,2020-11-08 18:48:22 UTC,"This issue, especially comment #7 looks very much like the issues I've been having since I installed Ubuntu on my desktop for the first time."
1794245,2019-01-23 14:44:26 UTC,"Reassigning to the kernel, the redhat bug states the issue is there and it has been marked as fixed in a kernel update"
1794245,2019-01-23 13:57:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794247,2019-05-12 08:51:00 UTC,"""some strings"" isn't specific enough - I don't understand what I need to do here."
1794247,2019-05-12 12:35:03 UTC,"you already fixed that as it was the reminder for the ""works at"" topic ;-)"
1794247,2019-09-15 15:51:35 UTC,Migrated to https://github.com/widelands/widelands/issues/1715
1794250,2018-09-25 13:38:24 UTC,"This is only true for strings that don't contain explicit numbers, like e.g. headings."
1794250,2019-09-15 15:24:13 UTC,Migrated to https://github.com/widelands/widelands/issues/3323
1794252,2019-06-13 16:44:59 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/605011
Reason: Already fixed with Iadbf8ec935565a6d4ccf6f36ef630ab6bf1bea5d."
1794252,2018-09-25 08:57:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605011"
1794252,2018-10-09 02:48:13 UTC,"Hi melanie, we use version 9.1.1 of nova."
1794252,2018-10-09 00:09:41 UTC,"We had a commit in the past ""Don't persist RequestSpec.retry"" [1] which was supposed to take care of avoiding the persist of retry information to the database. The patch was backported to Queens, Pike, and Ocata."
1794260,2018-09-26 05:16:58 UTC,"As per the discussion with Numan yesterday, an ideal way to handle the above issue might be to track the changes in a router."
1794260,2018-09-29 13:31:11 UTC,"This can be tricky at scale. Imagine an scenario where we have a Logical Router with a large number of networks connected to it. One of that networks has an LB which is main use case is that Members, VIPS and user are in the same subnet. Still, because we don't know that this is the use case, we're going to add the load balancer to *all* of the networks connected to that router. Not sure how this can impact at scale but I'd say it's something to keep in mind."
1794260,2018-10-03 10:46:33 UTC,So the idea is to tackle this by applying the LB to all LS connected to the LR and if this is a problem at scale we'll look at how to enhance it in core OVN so that the LB is only applied to the LR.
1794260,2018-10-03 10:56:17 UTC,Plan is to monitor the Logical_Router table and on every update/delete event:
1794260,2018-10-04 09:59:14 UTC,You can also monitor the LSP/LRP tables to find out when a router port on a network is created.
1794260,2019-06-27 14:17:42 UTC,"Change abandoned by Maciej Józefczyk (<email address hidden>) on branch: master
Review: https://review.opendev.org/667642"
1794260,2019-07-01 10:00:25 UTC,"Change abandoned by Reedip (<email address hidden>) on branch: master
Review: https://review.opendev.org/608862
Reason: Abandoning in favor of the new patch"
1794260,2019-07-15 18:23:52 UTC,"Reviewed:  https://review.opendev.org/668397
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=aa4268a09470aea28f4a8c9f1062f32f057cb151
Submitter: Zuul
Branch:    master"
1794260,2019-07-25 07:22:08 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/672645"
1794260,2019-08-06 12:06:28 UTC,"Reviewed:  https://review.opendev.org/672645
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=c5169327ec13e7fb02ee2346a70f8666c725ab2a
Submitter: Zuul
Branch:    stable/stein"
1794260,2019-09-19 10:09:43 UTC,This issue was fixed in the openstack/networking-ovn 7.0.0.0b1 development milestone.
1794260,2019-12-05 19:48:51 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/697558"
1794260,2019-12-05 19:54:16 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/697559"
1794260,2019-12-07 00:56:57 UTC,"Reviewed:  https://review.opendev.org/697559
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=eef8fa3933b46c7c0cfe40539c5f1d12db14139f
Submitter: Zuul
Branch:    stable/queens"
1794260,2019-12-13 14:52:48 UTC,"Reviewed:  https://review.opendev.org/697558
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=5fae8f68a033d66838fbecec3796e37d0ccdd60d
Submitter: Zuul
Branch:    stable/rocky"
1794260,2020-02-18 14:09:25 UTC,This issue was fixed in the openstack/networking-ovn 6.0.1 release.
1794260,2019-06-26 14:58:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/667642"
1794269,2018-11-15 08:37:17 UTC,Thanks for your suggestion. It makes sense to allow this to be customized. You could do some trickery today by mounting /var/lib/snapd/snaps from a different place but of course that is relatively complicated.
1794269,2018-11-15 11:19:34 UTC,Thanks for your response! It would be nice if this functionality could be implemented.
1794270,2018-09-26 21:24:47 UTC,"I've tried again in the dev env I have available right now with me, which is not queens, but pre-rocky with exabgp 4.0.6, and the feature works as designed in this context."
1794270,2018-09-26 13:35:37 UTC,"> I think the way of exabgp logger is kind of weird though, maybe we networking-bagpipe should follow it.
"
1794270,2018-09-26 08:20:38 UTC,"The log level is supposed to be forced here:
https://github.com/openstack/networking-bagpipe/blob/master/networking_bagpipe/bagpipe_bgp/engine/exabgp_peer_worker.py#L102"
1794270,2018-09-26 10:25:51 UTC,"4.0.5 for exabagp, stable/queens for networking-bagpipe."
1794273,2018-09-25 13:51:01 UTC,I have removed all packages cited as foreign or obsolete in /var/log/dist-upgrade/main.log below:
1794281,2018-09-25 12:11:55 UTC,async became a keyword in python 3.7. This looks like the upstream fix:
1794283,2019-01-30 10:00:13 UTC,"Thank you for your bug report. Does it happen on any share/file or only on specific ones? Can you copy using ""gio copy ..."" or does that hit the same issue?"
1794283,2019-01-30 10:01:14 UTC,"Could you also do 'GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd -r', try the copy and copy any output you get there?"
1794283,2019-01-31 08:19:41 UTC,"This happens when copying files using nautilus. I can copy files using a terminal (e.g. gio copy) and another file manager, e.g. double commander. Earlier I observed that this happens when copying photos and documents, and the error appeared after copying 1 MB of data (smaller files were copied), but now I looked at it again and trying to copy a 350 MB zip file, I received an error at the very end. It looks as if the file was copied in full, but with an error at the very end, so I can't say if the contents are correct."
1794283,2019-01-31 09:39:09 UTC,"> Using 'GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd -r' unfortunately does not return any output
"
1794283,2019-03-21 19:36:12 UTC,This is output when I was mounting samba resources and trying to copy a file:
1794283,2019-05-21 04:17:26 UTC,[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]
1794285,2020-11-12 06:27:44 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1794285,2021-01-12 04:17:13 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1794288,2018-10-26 14:51:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794289,2018-09-27 18:34:34 UTC,Removing you as an assignee as this is not (yet) targeted for fixing.
1794289,2019-09-19 12:06:39 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1794289,2018-09-27 17:36:13 UTC,We already have the commissioning tag which selects which tests are run by default during commissioning. Originally when I implemented commissioning during enlistment I actually added any test tagged commissioning. That was removed during review but I could add it back.
1794293,2018-09-25 13:45:00 UTC,"This is a feature request, not a bug report. Therefore, no log files are required for this issue, and now changing to ""confirmed""."
1794293,2018-09-25 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794295,2021-02-18 19:16:04 UTC,Confirmed same behavior in 3.6.1
1794295,2018-09-25 13:35:12 UTC,"Confirming, but I'm also adding a note that if you press the Ctrl key while selecting the action, the correct interface will load in a new tab. I'm not sure why one works when the other doesn't."
1794295,2018-09-25 13:54:35 UTC,"Kathy,
   CTRL+Left-Click is indeed a viable workaround until it is fixed. Thank you! Scott"
1794295,2018-10-04 12:52:03 UTC,It seems like this workaround stopped working in 3.1.5. CTRL+Left Click now simply overwrites the open tab instead of opening a new one. Can someone verify this? I tried it in both Chrome and Firefox.
1794295,2018-10-04 14:21:23 UTC,"I just updated my test system to 3.1.6 and am still able to use CTRL-Left Click on the check in screen to open an action in a new tab. I also updated Chrome to 69.0.3497.100 in case it was a change in browser behavior, but it's still working for me."
1794295,2018-10-04 15:40:11 UTC,I have the same version of Chrome. I tried it on our 3.1.5 and 3.1.2 test servers as well. It doesn't work. Can someone else try it on a pre-3.1.6 system? I am not sure what is going on.
1794295,2018-10-04 16:18:44 UTC,Adding a note that I also tried it on 3.1.4 before I upgraded the test system this morning. But it would be good to get confirmation from somebody else.
1794295,2018-10-18 19:43:16 UTC,"3.1.5 test system, no new-tab options from checkin are working -- right click, scrollwheel-click, or ctrl-left click.  Will look at an earlier 3.1 later if I get to it."
1794295,2018-10-18 19:44:15 UTC,Forgot to add this was on Chrome ^^
1794295,2018-10-18 20:07:45 UTC,"I just tried again on the community demo server. If I CTRL-click Retrieve Last Patron Who Circulated Item, I see the behavior Scott and Andrea described. If I CTRL-click Show Record Holds or Show Last Few Circs, I get the expected behavior of opening it in a new tab."
1794295,2018-11-06 17:07:50 UTC,"Kathy, belatedly confirming what you see (on a 3.1.6 test server).  Ctrl+click works for Show Record Holds and Show Last Few Circs, it's just Retrieve Last Patron that's broken."
1794298,2018-09-26 06:47:48 UTC,https://gitlab.com/inkscape/inkscape/commit/5d6b743493293644cd1006c18fb974cde353dee3
1794298,2018-09-25 13:38:00 UTC,"Thomas thanks for disect the bug, I couldent add you as asigned, but I add you to the notiffied to do it."
1794298,2018-09-25 13:32:30 UTC,File with the bug
1794299,2018-10-13 13:49:44 UTC,"Re: use of OpenGL, I have ""UI Render: default"""
1794299,2019-05-08 18:25:37 UTC,"Dear Stephen_Hamer_UK,"
1794299,2018-10-13 19:36:54 UTC,"Im not the Ubuntu maintainer anymore, please file downstream. (Self-removal of CC)"
1794299,2018-10-13 16:25:27 UTC,@Stephen: thanks for checking.
1794299,2019-06-08 03:05:20 UTC,"Dear Stephen_Hamer_UK,"
1794299,2018-10-11 18:12:48 UTC,I cannot reproduce the problem on Ubuntu 16.04 LTS with the TDF LibreOffice build 6.0.6.2.
1794299,2018-10-11 14:42:20 UTC,"Description:
Working in Ubuntu Bionic with the std LibreOffice pkg."
1794299,2018-10-11 15:18:13 UTC,"reporter: could you give a try to a more recent LO version by using LO ppa?
Indeed, last one is 6.1.2."
1794299,2018-10-04 16:12:35 UTC,"Thanks for responding, Oliver"
1794299,2018-10-04 07:27:40 UTC,"Just tested in an up-to-date virtual machine running bionic (18.04) and libreoffice 6.0.6.2, and the script runs fine. See attached screenshot."
1794299,2018-09-25 13:42:52 UTC,This was the script mentioned in my report:
1794299,2018-10-11 14:48:09 UTC,Find my bugzilla bug-report here:
1794299,2018-10-10 14:23:00 UTC,"Would you mind filing an upstream bug report at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided, and share the link to it here? Thanks!"
1794300,2018-10-29 04:39:31 UTC,"Reviewed:  https://review.openstack.org/612546
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=37ce11ade95c41e884a868801e4186a207d1dcde
Submitter: Zuul
Branch:    master"
1794300,2018-10-23 02:07:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612546"
1794300,2018-11-19 20:38:59 UTC,This issue was fixed in the openstack/puppet-nova 14.1.0 release.
1794301,2018-10-17 05:52:46 UTC,"Reviewed:  https://review.openstack.org/610438
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=581d5dcb98344d8934d0a7e1f6c34e5ed9195b5c
Submitter: Zuul
Branch:    master"
1794301,2018-10-30 11:05:08 UTC,"Reviewed:  https://review.openstack.org/613834
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=a4be0712cee63edeafa9039b496f5b3e6ba4e3e8
Submitter: Zuul
Branch:    stable/rocky"
1794301,2018-11-19 20:39:08 UTC,This issue was fixed in the openstack/puppet-nova 14.1.0 release.
1794301,2018-10-29 05:02:27 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/613834"
1794314,2019-10-20 12:48:43 UTC,This bug was fixed in the package devscripts - 2.19.7ubuntu2
1794317,2018-09-25 20:35:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794318,2018-09-27 12:05:17 UTC,"sudo dmidecode
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
76 structures occupying 2828 bytes.
Table at 0xCBD62018."
1794318,2018-09-25 15:38:11 UTC,View attachment for more info.
1794318,2018-09-27 11:40:17 UTC,"sudo mdadm --examine /dev/sd[a-z]
/dev/sda:
          Magic : Intel Raid ISM Cfg Sig.
        Version : 1.2.06
    Orig Family : b64dd376
         Family : b64de296
     Generation : 00000806
     Attributes : All supported
           UUID : fe813c51:b5e27074:8e458e63:fd55063a
       Checksum : d3a21665 correct
    MPB Sectors : 1
          Disks : 2
   RAID Devices : 1"
1794318,2018-09-27 11:39:30 UTC,"sudo mdadm --assemble --scan
returns nothing"
1794318,2018-09-27 11:34:18 UTC,"sudo  mdadm --detail-platform
[sudo] password for jeroen:
       Platform : Intel(R) Rapid Storage Technology
        Version : 12.9.0.2006
    RAID Levels : raid0
    Chunk Sizes : 4k 8k 16k 32k 64k 128k
    2TB volumes : supported
      2TB disks : supported
      Max Disks : 6
    Max Volumes : 2 per array, 4 per controller
 I/O Controller : /sys/devices/pci0000:00/0000:00:1f.2 (SATA)
          Port5 : /dev/sdd (S33HNX0J200966L)
          Port1 : /dev/sdb (S33HNX0J200852F)
          Port4 : /dev/sdc (WDZ29M4J)
          Port0 : /dev/sda (S33HNX0HA01515T)
          Port2 : - no device attached -
          Port3 : - no device attached -"
1794318,2018-09-26 10:44:45 UTC,"TL;DR: probably mdadm commit from April 2018; see end.
Today's IRC logs of debugging session with reporter:"
1794318,2018-09-27 12:11:49 UTC,bios screenshots
1794318,2018-09-26 09:00:24 UTC,"sudo cat /proc/mounts
[sudo] password for jeroen:
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=8140992k,nr_inodes=2035248,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=1634112k,mode=755 0 0
/dev/mapper/isw_dafiffhfja_Volume1p2 / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/unified cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/rdma cgroup rw,nosuid,nodev,noexec,relatime,rdma 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15340 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
sunrpc /run/rpc_pipefs rpc_pipefs rw,relatime 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
/dev/mapper/isw_dafiffhfja_Volume1p1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /run/user/119 tmpfs rw,nosuid,nodev,relatime,size=1634108k,mode=700,uid=119,gid=124 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1634108k,mode=700,uid=1000,gid=1000 0 0"
1794318,2018-09-26 08:50:55 UTC,after a purge remove vagrant I get raid problems.
1794318,2018-09-26 09:20:56 UTC,"find /etc/initramfs-tools/ -ls
 14417979      4 drwxr-xr-x   5 root     root         4096 sep 26 08:25 /etc/initramfs-tools/
 14419131      4 -rw-r--r--   1 root     root          378 jan  5  2018 /etc/initramfs-tools/update-initramfs.conf
 14419128      4 drwxr-xr-x  12 root     root         4096 jul 25 05:03 /etc/initramfs-tools/scripts
 14419136      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/local-premount
 14419135      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/local-bottom
 14419137      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/local-top
 14419139      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/nfs-premount
 14419133      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/init-premount
 14419134      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/init-top
 14419140      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/nfs-top
 14419141      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/panic
 14419138      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/nfs-bottom
 14419132      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/scripts/init-bottom
 14419126      4 drwxr-xr-x   2 root     root         4096 jul 25 05:17 /etc/initramfs-tools/conf.d
 14419130      4 -rw-r--r--   1 root     root          246 jul 25 05:03 /etc/initramfs-tools/modules
 14419129      4 -rw-r--r--   1 root     root         1646 jan  5  2018 /etc/initramfs-tools/initramfs.conf
 14419127      4 drwxr-xr-x   2 root     root         4096 feb 20  2018 /etc/initramfs-tools/hooks"
1794318,2018-09-26 08:11:07 UTC,"After installing vagrant it did a update-initramfs, which I presume, broke booting from kernel 4.15.0-34-generic when I switched back, using the grub menu, to a previous kernel  4.15.0-29-generic I could still boot without problems"
1794318,2018-09-26 07:34:21 UTC,I've added my logs after a failed boot (using a usb live disk).
1794318,2018-09-26 06:33:32 UTC,full*
1794318,2018-09-26 06:33:16 UTC,I reinstalled my system again and did a fool update and a reboot. It looks like something else is causing the problem.
1794318,2018-09-25 15:50:53 UTC,So which kernel is good and which one is bad?
1794318,2018-09-25 15:49:58 UTC,Per the earlier conversation:
1794318,2018-09-26 08:23:35 UTC,initramfs
1794318,2018-09-27 12:47:59 UTC,  https://irclogs.ubuntu.com/2018/09/27/%23ubuntu-devel.html#t11:31
1794328,2018-09-26 17:46:59 UTC,"hmm, I see I think I miss understood your comment and wrote comment #2.
at first I thought FactoryOwners.Forbidden works this way
""If has any factory built by a FactoryOwners.Forbidden country, the tag will not be satisfied.""
If you read #2 again with this notion you will understand my point."
1794328,2018-09-26 16:45:06 UTC,"conclusion flowchart:
https://i.imgur.com/Qwa8LeD.jpg"
1794328,2018-09-26 16:00:00 UTC,"case1: ""Only if all factories are owned by forbidden owners should [tank1] become unavailable.""
I don't see the point of having 2 tags If it works like that."
1794328,2018-09-26 12:26:54 UTC,case 1: yes I did own at least one.
1794328,2018-09-25 18:49:08 UTC,"Did you own a single factory that was owned by USSR? Or did you own more than one, and one owned by USSR was among them? In the first case the [tank1] shouldn't be buildable, in the second case it should. Only if all factories are owned by forbidden owners should [tank1] become unavailable. I'll look into it if it's the former."
1794334,2018-09-25 20:48:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794334,2018-11-14 01:23:45 UTC,I have the same problem when trying to install android studio on ubuntu 18.04. My version of the package is 16.11.1ubuntu1
1794334,2018-11-14 01:26:26 UTC,ERROR: Download page changed its syntax or is not parsable (url missing)
1794334,2018-11-14 01:56:17 UTC,I downloaded the version in the repository and see that it's working. So it would probably just backporting the fix to the 18.04 release.
1794340,2018-09-25 18:30:13 UTC,This change was made by a bot.
1794340,2018-09-26 20:25:58 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1794340,2018-09-27 17:58:19 UTC,"---Update on 27th September 2018
As requested tested with mainline kernel v4.19-rc5, the bug still exists. The PC gets stuck at the reboot or the shutdown stage. Hence adding the additional tag."
1794340,2019-05-06 14:22:22 UTC," This bug affected me too! Ubuntu-Budgie 19.04 64-bit dual boot with windows 10 kernel 5.0.0.14 stuck ad reboot/shutdown. Only reset button work! Trying with install latest nvidia-drivers, but no reason still resist the problem!"
1794348,2020-08-17 21:14:32 UTC,Fixed via mate-sensors-applets 1.24.1-0ubuntu1 in Ubuntu Groovy.
1794354,2020-08-26 05:02:46 UTC,Here's a quick fix:
1794354,2020-08-25 06:40:30 UTC,"I have issue with this on ubuntu 20.04 focal, I have setup the color emoji for chromium and another program for using.
Once I update to 20.04 and it using snap version of chromium, It turn back to black and white emoji which is quiet annoy me for spending time to debugging it and find out that is snap version causing it."
1794354,2018-10-04 07:47:51 UTC,"Indeed the snap links against and contain libfontconfig.so.1.9.0, from xenial."
1794354,2018-09-25 19:21:05 UTC,What distro version are you building the Snap from? Maybe you need fontconfig from bionic?
1794354,2019-08-07 15:29:00 UTC,"The snap is now being built on bionic. However the issue can still be observed. What's more, it's not snap-specific. The deb is similarly affected."
1794358,2018-09-25 20:20:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1794364,2018-10-08 21:45:29 UTC,This issue was fixed in the openstack/nova 16.1.6 release.
1794364,2019-03-22 03:47:19 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1794364,2019-03-21 17:22:50 UTC,This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.
1794364,2018-12-03 16:29:04 UTC,This issue was fixed in the openstack/cinder 13.0.2 release.
1794364,2018-10-31 19:09:16 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614617"
1794364,2018-10-31 01:30:38 UTC,"Reviewed:  https://review.openstack.org/611463
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d47486d317e8cdb1cdab50d73f6484289ab082d4
Submitter: Zuul
Branch:    master"
1794364,2018-10-26 19:32:43 UTC,"Reviewed:  https://review.openstack.org/605836
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c86f309c564f4a394285068bbdb4f138cfff1651
Submitter: Zuul
Branch:    master"
1794364,2018-10-17 23:15:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611463"
1794364,2018-10-08 21:50:41 UTC,This issue was fixed in the openstack/nova 17.0.7 release.
1794364,2018-10-08 21:49:11 UTC,This issue was fixed in the openstack/nova 15.1.5 release.
1794364,2018-10-08 20:53:22 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1794364,2018-11-26 21:56:32 UTC,"Reviewed:  https://review.openstack.org/614617
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=74fd810ad1a8561ba150925d19feb8cbe598fe84
Submitter: Zuul
Branch:    stable/rocky"
1794364,2018-10-03 17:59:38 UTC,"Reviewed:  https://review.openstack.org/605840
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=25e73d5cbf66984f69deb0e808a25f97772bd9dd
Submitter: Zuul
Branch:    stable/pike"
1794364,2018-10-02 21:20:34 UTC,"Reviewed:  https://review.openstack.org/605839
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d8b99f05abb2fa8964a326958804f47daf95da64
Submitter: Zuul
Branch:    stable/queens"
1794364,2018-10-02 03:22:00 UTC,"Reviewed:  https://review.openstack.org/605828
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fc9c8772012b528176c3f58d99a58491bb1aedb4
Submitter: Zuul
Branch:    stable/rocky"
1794364,2018-09-28 21:14:50 UTC,"Reviewed:  https://review.openstack.org/605329
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c4c6dc736e084f2d919b9bcf93d26df87e0341c9
Submitter: Zuul
Branch:    master"
1794364,2018-09-27 19:06:35 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/605842"
1794364,2018-09-27 19:00:41 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/605840"
1794364,2018-09-27 18:57:40 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/605839"
1794364,2018-09-27 18:54:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/605836"
1794364,2018-09-27 18:24:08 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605828"
1794364,2018-09-26 04:33:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605329"
1794364,2018-09-25 20:44:45 UTC,"(3:05:42 PM) mriedem: that populate_uuids migration was added in queens, and looking at a grenade run from queens, we should see bdms getting migrated to have a uuid, and i'm not seeing any results in the table for a grenade run on queens
(3:05:42 PM) mriedem: http://logs.openstack.org/48/604448/1/check/neutron-grenade/19d8166/logs/grenade.sh.txt.gz
(3:05:46 PM) mriedem: so yeah, likely busted"
1794364,2018-10-04 17:14:32 UTC,"Reviewed:  https://review.openstack.org/605842
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5d33e554e4c96cec85274e8f46f3a7fa2b040b17
Submitter: Zuul
Branch:    stable/ocata"
1794369,2018-11-23 19:47:33 UTC,Fix: https://github.com/kassoulet/soundconverter/commit/2c5d70af16ed8e9c66fbf2c48daff24d858cdefb
1794380,2020-08-26 18:18:09 UTC,"Thanks for the report, do you have any interest in moving to bases https://snapcraft.io/docs/base-snaps ?"
1794380,2020-08-27 17:35:11 UTC,This should be fixed in current snapcraft when using a `base`.  Legacy builds do not have supported extensions.
1794382,2018-09-25 22:15:24 UTC,"This is a log file for Open Rails. Please include this file in bug reports.
--------------------------------------------------------------------------------
Date/time  = 9/26/2018 12:13:38 AM (2018-09-25 22:13:38Z)
BIOS       = X751LB.402 (American Megatrends Inc.)
Processor  = Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (4 threads, 2 cores, 2.2 GHz) (L1 Cache 32 KB) (L1 Cache 32 KB) (L2 Cache 256 KB) (L3 Cache 3072 KB)
Memory     = 11.9 GB
Video      = NVIDIA GeForce 940M              (2.0 GB RAM) (nvlddmkm 10.18.13.5946)
Video      = Intel(R) HD Graphics 5500 (1.0 GB RAM) (igdkmd64 20.19.15.4549)
Display    = \\.\DISPLAY2 (1360 x 768, 32-bit, 1600 x 0)
Display    = \\.\DISPLAY1 (1600 x 900, 32-bit, primary, 0 x 0)
Sound      = Bluetooth Audio Device (btath_a2dp 8.0.1.316)
Sound      = Realtek High Definition Audio (rtkvhd64 6.0.1.7224)
Sound      = NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (nvvad64v 1.2.30.0)
Disk       = C: (Local Fixed Disk, NTFS, 237.9 GB, 107.1 GB free)
Disk       = D: (CD-ROM Disc, )
Disk       = E: (Local Fixed Disk, NTFS, 117.2 GB, 69.5 GB free)
Disk       = H: (Local Fixed Disk, NTFS, 814.2 GB, 339.3 GB free)
OS         = Microsoft Windows 10 Home 64-bit (10.0.17134)
Runtimes   = 2.0.50727 SP2  3.0 SP2  3.5 SP1  4 Client  4 Full  4.0 Client
Runtime    = 4.0.30319.42000 (32bit)
--------------------------------------------------------------------------------
Version    = <none>
Build      = 0.0.6527.40026 (2017-11-14 22:14:12Z)
Logfile    = C:\Users\Robert Chalcak\Desktop\OpenRailsLog.txt
Executable = RunActivity.exe
Argument   = -resume
Argument   = C:\Users\Robert Chalcak\AppData\Roaming\Open Rails\Trat ZSR 191-193 Vlaky 2018-09-26 00.09.17.save
--------------------------------------------------------------------------------
ActRandomizationLevel          =                0
ActWeatherRandomizationLevel   =                0
AdhesionFactor                 = (user set)     200
AdhesionFactorChange           = (user set)     0
AdhesionMovingAverageFilterSize =                10
AdhesionProportionalToWeather  =                False
Alerter                        = (user set)     True
AlerterDisableExternal         = (user set)     False
Autopilot                      =                False
AuxActionEnabled               =                False
AvatarURL                      =                http://openrails.org/images/support-logos.jpg
BrakePipeChargingRate          =                21
BreakCouplers                  =                False
Cab2DStretch                   =                0
CarVibratingLevel              = (user set)     1
CircularSpeedGauge             =                False
ConditionalLoadOfDayOrNightTextures =                False
CorrectQuestionableBrakingParams =                False
CurveResistanceSpeedDependent  =                False
CurveSpeedDependent            =                False
DataLogger                     =                False
DataLoggerSeparator            =                comma
DataLogMisc                    =                False
DataLogPerformance             =                True
DataLogPhysics                 =                False
DataLogSpeedUnits              =         ..."
1794382,2018-09-26 09:23:48 UTC,"Can you explain in which situation the activity and the player train were, when you saved the game?"
1794385,2018-11-07 18:54:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794387,2019-08-13 11:27:47 UTC,This bug was fixed in the package linux - 4.15.0-58.64
1794387,2019-08-07 08:34:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1794387,2019-02-14 12:12:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1794387,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1794387,2019-01-15 11:19:45 UTC,Using kernel 4.18.0-14-generic from cosmic-proposed fixes the issue. Thanks!
1794387,2018-09-27 18:55:11 UTC,"I installed kernel v4.19-rc5, but the system hangs due to an ""ACPI BIOS Error"".
Should I try rc4?"
1794387,2019-01-15 10:33:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1794387,2018-10-02 15:29:36 UTC,https://lkml.org/lkml/2018/10/2/1237
1794387,2018-09-28 17:14:36 UTC,"Using the kernel provided by Kai-Heng Feng solves the issue, now colour banding is gone.
Thank you very much!"
1794387,2018-09-28 08:15:12 UTC,"Please try this kernel:
https://people.canonical.com/~khfeng/lp1794387/"
1794387,2018-09-27 18:31:34 UTC,apport information
1794387,2018-09-27 18:31:25 UTC,apport information
1794387,2018-09-27 18:31:32 UTC,apport information
1794387,2018-09-27 18:31:30 UTC,apport information
1794387,2018-09-27 18:31:29 UTC,apport information
1794387,2018-09-27 18:31:28 UTC,apport information
1794387,2018-09-27 18:31:27 UTC,apport information
1794387,2018-09-27 18:31:26 UTC,apport information
1794387,2018-09-27 18:31:24 UTC,apport information
1794387,2018-09-27 18:31:23 UTC,apport information
1794387,2018-09-27 18:31:22 UTC,apport information
1794387,2018-09-26 20:23:45 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1794387,2018-09-25 23:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794387,2018-09-27 18:31:33 UTC,apport information
1794393,2020-08-22 22:14:03 UTC,"Unable to reproduce. If you can reproduce the problem, please reopen and provide instructions."
1794397,2018-09-26 00:00:06 UTC,This change was made by a bot.
1794397,2019-04-30 10:23:57 UTC,There is a similar warning/error in the description of bug #1826025 (though that's not what the report is about)
1794399,2019-01-15 21:37:21 UTC,"This bug is fixed with commit fdadcb5f to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=fdadcb5f"
1794399,2019-05-10 18:07:27 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1794401,2018-11-28 18:52:38 UTC,This looks like a translation bug. Forwarding to openstack-i18n.
1794401,2018-11-28 18:54:12 UTC,"translation should be fixed in the translation platform (translate.openstack.org).[1]
Horizon is not related. Removing horizon from the affected project."
1794403,2018-09-27 01:33:11 UTC,For others with the same problem:
1794419,2019-10-30 14:19:09 UTC,This issue was fixed in the openstack/python-novaclient 10.1.1 release.
1794419,2019-03-28 23:02:24 UTC,"Reviewed:  https://review.openstack.org/613090
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=154b29b7a34ee3e1938574de2a69255b879979e5
Submitter: Zuul
Branch:    stable/queens"
1794419,2019-01-08 23:40:40 UTC,"Reviewed:  https://review.openstack.org/613057
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=5610ebd10d18ac6db204d31e8b4341a33a31e327
Submitter: Zuul
Branch:    stable/rocky"
1794419,2018-10-24 17:34:14 UTC,This issue was fixed in the openstack/python-novaclient 11.1.0 release.
1794419,2018-10-24 15:57:50 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/613090"
1794419,2019-11-12 11:35:17 UTC,This issue was fixed in the openstack/python-novaclient 11.0.1 release.
1794419,2018-10-24 14:42:51 UTC,The bug was introduced in Queens so we should backport the fix.
1794419,2018-10-03 06:47:16 UTC,"Reviewed:  https://review.openstack.org/605341
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=cac7351b0ee9716f1be01e8711d6ed3a237362ca
Submitter: Zuul
Branch:    master"
1794419,2018-10-24 14:44:32 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/613057"
1794419,2018-09-26 06:49:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605341"
1794421,2018-10-06 17:48:59 UTC,policy_rules for allowed_address_pairs is correct [1] and the corresponding policy.json from neutron is correct too [2].
1794421,2019-10-22 20:08:09 UTC,This issue was fixed in the openstack/horizon 15.1.1 release.
1794421,2019-10-22 20:07:34 UTC,This issue was fixed in the openstack/horizon 14.0.4 release.
1794421,2019-10-22 20:06:47 UTC,This issue was fixed in the openstack/horizon 13.0.3 release.
1794421,2019-10-09 11:11:58 UTC,"Reviewed:  https://review.opendev.org/684862
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=78574736a52656c6d9fba92634bf58e0ad03915a
Submitter: Zuul
Branch:    stable/stein"
1794421,2019-10-09 10:20:16 UTC,"Reviewed:  https://review.opendev.org/684922
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=83855762fb6af0f560de9432512aa488377e9e21
Submitter: Zuul
Branch:    stable/rocky"
1794421,2019-10-09 10:25:21 UTC,"Reviewed:  https://review.opendev.org/685045
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d8ae1d05920f144531fe16a70e80f9871c37675f
Submitter: Zuul
Branch:    stable/queens"
1794421,2019-09-26 11:30:29 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/685045"
1794421,2019-09-26 04:03:25 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/684922"
1794421,2019-09-26 01:17:15 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/684862"
1794421,2019-09-25 19:33:50 UTC,"Reviewed:  https://review.opendev.org/679967
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=87b57dfe7113da09715d5613ab9c91c15a75c189
Submitter: Zuul
Branch:    master"
1794421,2019-09-04 11:16:41 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/679967"
1794421,2019-03-01 12:05:59 UTC,Would this be looked in to soon? :-)
1794421,2019-01-07 10:44:15 UTC,Temporarily assigning me as I cannot work on this soon
1794421,2019-09-27 08:57:27 UTC,This issue was fixed in the openstack/horizon 16.0.0.0rc1 release candidate.
1794422,2019-06-26 19:21:06 UTC,In this case kolla-ansible tries to use `database_password` as root password to create the `keystone` user by itself. If keystone user is to be precreated then the database must be too and the variable value needs to be changed.
1794425,2019-03-29 10:16:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794425,2019-05-23 16:55:39 UTC,I added an explanation of this issue on https://gitlab.gnome.org/GNOME/gnome-screenshot/issues/14#note_517056
1794426,2018-10-02 08:06:01 UTC,The package has been published and the bug is being set to Fix Released
1794426,2018-10-01 14:16:36 UTC,"Two bugs fixed by bionic kernel in -proposed have not been verified. Given that they have low regression potential, I'm setting verification-testing to 'Fix Released'."
1794426,2018-09-27 09:09:43 UTC,Hardware Certification have begun testing this -proposed kernel.
1794426,2018-09-28 13:16:09 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-36.39/bionic-proposed-published.html"
1794426,2018-10-01 14:37:30 UTC,regression-testing not running for this release.
1794427,2018-09-27 09:09:04 UTC,Hardware Certification have begun testing this -proposed kernel.
1794427,2018-09-28 13:47:15 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.15.0-1024.26/raspi2-4.15-proposed-published.html"
1794427,2018-10-02 08:34:55 UTC,The package has been published and the bug is being set to Fix Released
1794428,2018-10-01 18:06:50 UTC,The package has been published and the bug is being set to Fix Released
1794428,2018-10-01 14:42:30 UTC,regression-testing not running with this release.
1794430,2018-10-02 08:06:22 UTC,The package has been published and the bug is being set to Fix Released
1794430,2018-10-01 14:41:21 UTC,regression-testing completed with aws kernel 4.15.0-1022.22 (bug 1791725).
1794431,2018-10-01 14:40:39 UTC,regression-testing not running for this release.
1794431,2018-10-18 16:29:52 UTC,Tests look good
1794431,2018-10-18 19:37:26 UTC,The package has been published and the bug is being set to Fix Released
1794432,2018-10-01 08:38:16 UTC,"4.15.0-1021.22 - gcp
Regression test CMPL, RTB."
1794432,2018-10-02 08:00:32 UTC,The package has been published and the bug is being set to Fix Released
1794433,2018-10-01 14:40:11 UTC,regression-testing not running for this release.
1794433,2018-10-01 18:00:53 UTC,The package has been published and the bug is being set to Fix Released
1794436,2018-10-18 20:01:07 UTC,The package has been published and the bug is being set to Fix Released
1794436,2018-10-18 16:30:05 UTC,Tests look good
1794436,2018-10-01 14:38:20 UTC,regression-testing not running for this release.
1794438,2018-10-19 18:01:10 UTC,The package has been published and the bug is being set to Fix Released
1794438,2018-10-01 14:38:42 UTC,regression-testing not running for this release.
1794439,2018-10-02 09:01:10 UTC,The package has been published and the bug is being set to Fix Released
1794439,2018-10-01 04:30:51 UTC,"4.15.0-1021.22~16.04.1 - gcp
Regression test CMPL, RTB."
1794441,2018-09-26 19:04:54 UTC,The following packages ended up in the wrong component in the -proposed pocket:
1794441,2018-09-26 23:11:11 UTC,"Binary component overrides done.Override component to main
linux-headers-oem 4.15.0.36.59 in xenial amd64: universe/kernel/optional/100% -> main
linux-image-oem 4.15.0.36.59 in xenial amd64: universe/kernel/optional/100% -> main
linux-signed-image-oem 4.15.0.36.59 in xenial amd64: universe/kernel/optional/100% -> main
linux-signed-oem 4.15.0.36.59 in xenial amd64: universe/kernel/optional/100% -> main
linux-tools-oem 4.15.0.36.59 in xenial amd64: universe/kernel/optional/100% -> main
Override [y|N]? y
5 publications overridden."
1794441,2018-09-26 23:12:05 UTC,"Override component to main
linux-oem 4.15.0.36.59 in xenial amd64: universe/kernel/optional/100% -> main
1 publication overridden."
1794441,2018-09-27 09:09:32 UTC,Hardware Certification have begun testing this -proposed kernel.
1794441,2018-09-28 13:22:41 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.15.0-36.39~16.04.1/xenial-4.15-proposed-published.html"
1794441,2018-10-01 14:39:15 UTC,regression-testing not running for this release.
1794441,2018-10-01 18:05:16 UTC,The package has been published and the bug is being set to Fix Released
1794442,2018-10-01 14:39:35 UTC,regression-testing not running for this release.
1794442,2018-10-01 18:01:52 UTC,The package has been published and the bug is being set to Fix Released
1794444,2018-09-27 14:43:03 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/KHSd9yVB/394-pc-kernel-440-137163-159"
1794444,2018-09-27 09:09:38 UTC,Hardware Certification have begun testing this -proposed kernel.
1794444,2018-09-27 11:15:28 UTC,Verification tests completed for xenial-proposed.
1794444,2018-10-01 14:32:06 UTC,regression-testing not running for this release.
1794444,2018-09-28 13:59:37 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-137.163/xenial-proposed-published.html"
1794444,2018-10-02 08:32:02 UTC,The package has been published and the bug is being set to Fix Released
1794445,2018-10-01 14:32:37 UTC,regression-testing not running for this release.
1794445,2018-10-01 16:33:16 UTC,The package has been published and the bug is being set to Fix Released
1794446,2018-09-27 09:09:22 UTC,Hardware Certification have begun testing this -proposed kernel.
1794446,2018-09-28 13:38:58 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/4.4.0-137.163~14.04.1/trusty-4.4-proposed-published.html"
1794446,2018-10-01 14:33:24 UTC,regression-testing not running for this release.
1794446,2018-10-01 16:32:53 UTC,The package has been published and the bug is being set to Fix Released
1794447,2018-10-01 09:42:52 UTC,"4.4.0-1069.79 - aws
Regression test CMPL, RTB."
1794447,2018-10-02 08:03:40 UTC,The package has been published and the bug is being set to Fix Released
1794449,2018-10-01 14:34:39 UTC,regression-testing completed with kvm kernel 4.4.0-1034.40 (bug 1791751).
1794449,2018-10-01 16:33:41 UTC,The package has been published and the bug is being set to Fix Released
1794451,2019-02-19 13:20:36 UTC,Is this still an issue?
1794451,2019-03-03 09:29:55 UTC,"no but I had to redeploy the overcloud, which fixed the problem"
1794452,2018-10-01 19:57:58 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/JrgCh0Ns/393-pi2-kernel-440-1098106-73"
1794452,2018-09-28 13:46:54 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1098.106/raspi2-4.4-proposed-published.html"
1794452,2018-10-02 08:32:30 UTC,The package has been published and the bug is being set to Fix Released
1794452,2018-09-27 09:09:11 UTC,Hardware Certification have begun testing this -proposed kernel.
1794453,2018-09-27 09:09:17 UTC,Hardware Certification have begun testing this -proposed kernel.
1794453,2018-09-27 13:23:14 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/jhnqo1Ro/395-dragonboard-kernel-440-1102107-68"
1794453,2018-09-28 13:47:39 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1102.107/snapdragon-4.4-proposed-published.html"
1794453,2018-10-02 08:32:48 UTC,The package has been published and the bug is being set to Fix Released
1794454,2018-09-27 09:09:28 UTC,Hardware Certification have begun testing this -proposed kernel.
1794454,2018-09-28 13:40:46 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-160.210/trusty-proposed-published.html"
1794454,2018-09-28 15:26:29 UTC,Verification tests completed for trusty-proposed.
1794454,2018-10-01 14:23:15 UTC,Not running regression-tests for this release.
1794454,2018-10-01 16:35:29 UTC,The package has been published and the bug is being set to Fix Released
1794455,2018-10-01 14:25:58 UTC,Regression tests completed successfully with 3.13.0-159.209~precise1 (bug 1791756).
1794455,2018-10-01 16:36:05 UTC,The package has been published and the bug is being set to Fix Released
1794461,2018-10-22 22:16:36 UTC,"If I find the time I will test spinning it off into a PPA, incrementing the build number (and of course changing the build suffex to RuedII-PPA)."
1794461,2018-10-22 22:09:40 UTC,"As a note, it might just need to be recompiled against a newer DRI/Mesa version."
1794461,2018-09-26 23:08:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794478,2019-12-11 15:22:41 UTC,"Setting 'bionic' from ""Fix Released"" to ""Confirmed"" since 2 different persons stated the problem still exist (supported with reproducer testing)"
1794478,2019-12-10 15:40:29 UTC,"------- Comment From <email address hidden> 2019-12-10 10:31 EDT-------
Re-opened bugzilla, problem still not fixed"
1794478,2019-12-09 17:23:41 UTC,"Changed the status to New, since I was still able to reproduce the issue on Bionic, using the ""patched"" network-manager version."
1794478,2019-11-29 21:15:11 UTC,"Hi, all.  I'm afraid I'll need to reopen this bug."
1794478,2019-05-14 15:20:01 UTC,"------- Comment From <email address hidden> 2019-05-14 11:09 EDT-------
IBM bugzilla status -> closed, Fix Released with Bionic.."
1794478,2019-04-23 08:24:26 UTC,Adjusting tags according to comments #9 and #10.
1794478,2018-10-04 09:09:28 UTC,"------- Comment From <email address hidden> 2018-10-04 05:03 EDT-------
Vorlon,"
1794478,2019-04-04 13:09:33 UTC,"------- Comment From <email address hidden> 2019-04-04 09:01 EDT-------
Basic testing is done on the image and it looks good."
1794478,2019-02-15 13:56:19 UTC,"> The new stable version indicate the fix mentioned by seb128 is there but no indication has been made in
> the debian/changelog to automatically change the status, which breaks the SRU machinery for this
> particular bug.
"
1794478,2019-02-06 20:41:54 UTC,"The new stable version indicate the fix mentioned by seb128 is there but no indication has been made in the debian/changelog to automatically change the status, which breaks the SRU machinery for this particular bug."
1794478,2018-12-18 16:34:46 UTC,The issue looks like it could be what is fixed by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/34ca1680 (the change is included in 1.10.8 which is currently not yet in bionic but being SRUed)
1794478,2018-10-05 19:46:05 UTC,"Indeed, sorry about that, I overlooked that this was on a bond and tested with a bridge instead."
1794478,2018-10-02 00:25:59 UTC,This is not reproducible with netplan in an Ubuntu 18.04 container (on an Ubuntu cosmic host).  With the following netplan config:
1794478,2018-10-01 09:10:03 UTC,"------- Comment From <email address hidden> 2018-10-01 04:59 EDT-------
dhcp client package details:"
1794478,2018-09-26 14:01:00 UTC,"Which dhcp client is used? (affected package)
Notice that network-manager is not supported on Ubuntu Server 18.04,
please consider to move to netplan and networkd.
For now assuming that this is related to DHCP rather than nw mgr."
1794478,2019-04-23 08:09:39 UTC,"------- Comment From <email address hidden> 2019-04-23 04:08 EDT-------
The fix has worked , tested and we did not notice any other issues during the test."
1794478,2020-02-14 18:00:06 UTC,"------- Comment From <email address hidden> 2020-02-14 12:51 EDT-------
Eric,"
1794478,2020-02-12 14:41:09 UTC,"This look like a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1575944
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35"
1794478,2020-02-19 06:11:21 UTC,I uploaded patch for bionic sru. but I didn't subscribe sru-sponsors yet because I'm still confirming reproducer.
1794478,2020-02-14 19:51:37 UTC,Thanks for reporting the outcome of your test.
1794478,2020-03-12 10:10:36 UTC,"------- Comment From <email address hidden> 2020-03-12 06:07 EDT-------
IBM Bugzilla status-> closed, delivered by the distro"
1794478,2020-03-11 21:13:37 UTC,"The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1794478,2020-03-11 21:13:18 UTC,This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4
1794478,2020-03-04 15:29:02 UTC,Thx '<email address hidden>' for verification - the tags are set to done.
1794478,2020-03-04 14:02:03 UTC,"------- Comment From <email address hidden> 2020-03-04 08:55 EDT-------
The network manager fix provided is working fine."
1794478,2020-02-26 19:06:45 UTC,Sponsored by dgadomski. Unsubscribing sts-sponsor team.
1794478,2020-03-03 14:00:35 UTC,"All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1794478,2020-02-20 01:02:06 UTC,Default Comment by Bridge
1794478,2020-02-21 08:28:39 UTC,Default Comment by Bridge
1794478,2020-03-04 07:36:18 UTC,Hello
1794478,2020-02-24 13:07:08 UTC,"@xtrusia,"
1794478,2020-03-03 10:09:27 UTC,"Hello bugproxy, or anyone else affected,"
1794478,2020-02-21 08:37:00 UTC,why bugproxy keep attaching old debdiff I've changed
1794484,2019-02-12 13:33:19 UTC,Is that still an issue?
1794484,2019-05-19 04:17:39 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1794493,2018-09-26 11:28:43 UTC,"This is similar to https://bugs.launchpad.net/nova/+bug/1793423 but for cell0 and it had a review https://review.openstack.org/#/c/603998 submitted and it was abandoned because this behavior of update_cell taking options from the config file is designed on purpose. See the comments. It would be expected that the corresponding config file of that cell conductor (default nova.conf for cell0) would be used for the update of that cell. However since cell0 is a special case and it doesn't have a transport url, the update_cell command should check for this and not update the cell0's transport_url when using the default nova.conf (like in the default devstack setup), just like we don't allow disabling cell0."
1794493,2018-09-26 13:05:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605414"
1794508,2019-01-07 11:07:33 UTC,"This could be a feature rather than a bug: imagine a user named their lease badly, and later they want to rename it to reflect what it was used for?"
1794512,2018-12-14 11:13:54 UTC,Same error with bundle-bionic-rocky.yaml
1794516,2018-09-26 12:23:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794517,2018-09-26 12:43:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794522,2018-09-26 13:35:09 UTC,"suggestions how could it be done for mouse:
- if mouse is in the lower half, place split below. if mouse is in the upper half, when I right-click and split, split above
- if shift or ctrl is held when clicking split, invert split placement
- additional split items in the menu"
1794523,2020-03-26 08:47:01 UTC,Hello.
1794523,2020-05-26 04:17:17 UTC,[Expired for lxc (Ubuntu) because there has been no activity for 60 days.]
1794523,2020-05-26 12:19:07 UTC,There is still a problem :-/
1794523,2020-03-26 03:03:18 UTC,"Hmm, no, that would be wrong."
1794525,2018-10-02 16:22:35 UTC,Related patch: https://review.openstack.org/#/c/561218/
1794528,2018-10-05 15:06:33 UTC,This bug will be fix at
1794535,2018-09-26 14:19:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605434"
1794535,2018-09-27 04:10:10 UTC,"Can you explain your use case here for a subnet with two routers.
As per the initial design if the VM is deleted a port delete event should be sent to neutron and neutron server will send an rpc message to the agent to remove the ARP entry for invalid entries or for deleted VMs."
1794535,2018-10-01 07:59:35 UTC,"We have multiple external networks and since multiple interfaces on one VM are a bit hard to handle we have one subnet with multiple routers. This works quite well, the only problem is that ARP entries may persist. The l3 agent gets a delete request but only for one router, so the other routers keep their ARP entries."
1794537,2018-09-27 12:44:51 UTC,Subscribing Andreas FYI. Looks like a trivial patch that will look obviously correct when reviewed.
1794537,2018-09-27 14:38:45 UTC,"Hi,"
1794537,2018-09-27 15:17:54 UTC,Forget about the users problem on cosmic. I found the problem and I can confirm I have no issue at all. Only the dns update problem... but I have this problem with all server joined with samba (ok with sssd) since at least ubuntu 16.04.
1794537,2018-10-18 18:43:33 UTC,"Can you elaborate a bit on how you are joining the domain, and the output you are getting? The upstream bug and this one are not showing that particular detail, they only say that ""net ads join fails""."
1794537,2018-10-18 19:32:14 UTC,"I don't have the exact output, but the binary segfault at the end when I try it on my servers."
1794537,2018-10-18 19:43:03 UTC,"Could you share your smb.conf, sanitized if needed?"
1794537,2018-09-27 12:44:09 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1794541,2018-09-26 16:28:47 UTC,How did you share the song with the other user as there should be functionality to support this in the code.
1794541,2018-09-27 13:18:37 UTC,"Tim, you are right. I just realized that importing a song, will also import the tags."
1794543,2018-10-01 13:56:38 UTC,"Hi Olivier,"
1794543,2018-09-28 07:11:31 UTC,"Hi,"
1794543,2018-09-27 08:26:11 UTC,"Hi Olivier,"
1794543,2018-09-26 18:36:09 UTC,"Hi Pablo,"
1794543,2018-09-27 09:11:44 UTC,"P.S: forget about the ickkw = 1 option in the run_card for the MLM scheme. I just realised this is only available when importing a LO model, but not when importing the corresponding NLO model and running at LO+PS"
1794553,2018-10-10 00:32:01 UTC,This bug was fixed in the package squid - 4.1-1ubuntu3
1794553,2018-10-08 13:28:23 UTC,Upstream PR got some activity: https://github.com/squid-cache/squid/pull/257
1794553,2018-10-08 12:31:57 UTC,Disabling the pinger also works around the problem:
1794553,2018-10-04 20:53:44 UTC,"If squid.conf has a cache_dir setting, then the crash doesn't happen. For example:
cache_dir aufs /var/cache/squid-deb-proxy 40000 16 256"
1794553,2018-10-04 17:14:47 UTC,apparently so
1794553,2018-10-04 20:18:33 UTC,"I also just managed to get this in debian's 4.2-2:
Oct  4 20:17:00 sid-squid4 squid[582]: assertion failed: comm.cc:428: ""!isOpen(conn->fd)"""
1794553,2018-10-04 19:21:55 UTC,This looks very much like https://bugs.squid-cache.org/show_bug.cgi?id=4796
1794553,2018-10-04 19:07:53 UTC,"/usr/sbin/squid -k rotate is enough to crash it on adconrad's machine, even with the apparmor profile disabled."
1794553,2018-10-04 17:00:31 UTC,"@jibel and @adconrad, are you guys running squid with its apparmor profile enabled? Can you check with ps faxwZ or aa-status?"
1794553,2018-10-04 20:38:18 UTC,"Turns out it's easier than I thought, both in debian and ubuntu:"
1794553,2018-10-04 13:02:54 UTC,Here is the journal with records from September 23rd. The crash happened again yesterday.
1794553,2018-10-04 14:00:42 UTC,Thanks!
1794553,2018-09-26 15:40:05 UTC,"StacktraceTop:
 xassert (msg=msg@entry=0x555e7628ad6f ""!isOpen(conn->fd)"", file=file@entry=0x555e7628ad3c ""comm.cc"", line=line@entry=428) at debug.cc:618
 comm_init_opened (conn=..., note=note@entry=0x555e7629a065 ""Pinger Socket"", AI=0x555e76fe78a0) at comm.cc:428
 comm_openex (sock_type=<optimized out>, proto=<optimized out>, addr=..., flags=2, note=0x555e7629a065 ""Pinger Socket"") at comm.cc:403
 ipcCreate (type=type@entry=2, prog=0x555e76fe8d20 ""/usr/lib/squid/pinger"", args=args@entry=0x7ffc18daf380, name=name@entry=0x555e7629a065 ""Pinger Socket"", local_addr=..., rfd=rfd@entry=0x7ffc18daf378, wfd=0x7ffc18daf37c, hIpc=0x555e764f2c28 <_ZL4hIpc>) at ipc.cc:111
 IcmpSquid::Open (this=0x555e764f0ba0 <icmpEngine>) at IcmpSquid.cc:212"
1794553,2018-09-27 13:07:22 UTC,Thank you for the report.
1794553,2018-09-28 18:57:22 UTC,Getting this crash regularly here too.
1794553,2018-09-28 18:57:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794553,2018-10-04 18:38:42 UTC,"Ok, this seems to be pointing at a problem with the apparmor profile. I'll prepare an update for that."
1794553,2018-10-02 14:42:28 UTC,I'll work on an ubuntu update
1794553,2018-10-04 12:24:11 UTC,"Do you still have /var/log/syslog (maybe rotated) from the time of the crash, september 23rd? If yes, please attach it. Maybe I can correlate it with something else going on in the system."
1794553,2018-10-04 04:36:36 UTC,I'm also running squid-deb-proxy but it's the main squid that crashed. Here is the cache.log from the time of the crash. The access file for the same time is empty (I don't use squid on this machine at the moment)
1794553,2018-09-30 09:48:20 UTC,IIRC this may be the result of a bug found in the src/ipc/TypedMsgHeader.* GCC-8 patch for 4.1. Debian received the fix for that in the GCC-8 changes formally accepted into 4.2.
1794553,2018-10-03 20:05:37 UTC,"@jibel, are you running squid-deb-proxy too by any chance?"
1794553,2018-10-02 20:20:53 UTC,"Here are squid 4.2 packages for cosmic, merged from debian:"
1794559,2019-05-14 13:35:21 UTC,"Sounds like a race, or a bad assumption about a hook reliably getting triggered."
1794563,2021-02-17 17:09:37 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1794575,2018-09-26 18:22:45 UTC,Confirmed - I saw this exact bug late yesterday and had been puzzling over how to phrase the report. Evergreen version 3.0.2
1794575,2019-06-26 13:38:15 UTC,Related: Bug 1819542
1794592,2018-10-16 19:21:08 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1794599,2018-09-26 19:54:35 UTC,"In https://review.openstack.org/587586 we removed molteniron from the integrated build, but we didn't add anything to remove /etc/ansible/roles/os_molteniron when doing a major upgrade. We should add something to do that, otherwise the py_pkgs lookup will try to build the wheel from git, but the git repo won't be there and repo_build will fail."
1794599,2018-09-26 20:22:20 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605522"
1794599,2018-10-10 02:41:02 UTC,"Reviewed:  https://review.openstack.org/605522
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=e94c56ebe56559a2b2940cd2ef5378378905ac5e
Submitter: Zuul
Branch:    stable/rocky"
1794599,2018-10-15 20:05:49 UTC,This issue was fixed in the openstack/openstack-ansible 18.0.0.0rc4 release candidate.
1794599,2019-03-28 14:32:22 UTC,"Hello,"
1794599,2019-04-24 00:17:54 UTC,"Hello,
I have the same issue but in a different process.
I am building from the begin a cloud using the OpenStack Ansible ""Rocky version"" and this issue appears on my first clean installation, I need to run the phase ""openstack-ansible setup-infrastructure.yml"" twice to works."
1794599,2019-04-24 00:20:17 UTC,https://bugs.launchpad.net/openstack-ansible/+bug/1794599/comments/6
1794599,2020-10-28 15:41:24 UTC,Please resubmit your bugs separately if you are still facing issues. It is unlikely we will produce any patches for releases in Extended Maintenance / EOL.
1794601,2019-10-03 15:11:23 UTC,"Yeah, I think the tempurl work at https://github.com/openstack/swift/commit/5a4d3bdfc will be a really good guide. This is nice and self-contained; good first-contribution material. The main points we'd look for in a patch would be:"
1794605,2018-12-30 12:06:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794605,2020-02-26 16:56:01 UTC,"Could that possibly be due to changes in OpenSSL leading crashes? If so, find a fix at: https://github.com/proftpd/proftpd/issues/674"
1794613,2018-09-27 09:23:26 UTC,So I managed to create the container correctly but I had to add the old legacy configs manually for config and eth1.
1794613,2018-10-10 12:11:26 UTC,"On a fresh Ubuntu Xenial host, I tried the following and was unable to replicate the issue:"
1794613,2019-04-03 07:27:10 UTC,"I found out why was happening. The container cache was too old and i guess wasn't prepared for the new configuration layout.
I fixed it by deleting /var/cache/lxc/download."
1794616,2018-09-28 11:57:51 UTC,"I have dpkg files in /usr/local/bin/
I think there is an installation of dpkg under /usr/local/ but I'm not sure."
1794616,2018-09-28 16:37:37 UTC,"> I have dpkg files in /usr/local/bin/
> I think there is an installation of dpkg under /usr/local/ but I'm not sure.
"
1794616,2018-09-26 22:52:40 UTC,The error in your log is:
1794621,2018-09-28 21:00:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/606202"
1794621,2018-10-04 19:59:31 UTC,Subscribed field-medium
1794621,2018-12-06 19:50:27 UTC,Please see the reviews in gerrit.  But to bring over the outstanding question to this bug:
1794621,2018-12-07 16:34:47 UTC,"TBH in the context of OpenStack this change makes no difference - the OS charms all use the shared-db relation, not the db relation which this change impacts."
1794621,2018-12-07 16:35:32 UTC,@woutervb which charms are making use of the db relation and have this particular issue?
1794623,2019-09-09 16:02:14 UTC,"Fixed in revision 2b387f4b4d472fa90f9ea548a56334eaec035f42
https://git.launchpad.net/kicad/patch/?id=2b387f4b4d472fa90f9ea548a56334eaec035f42"
1794623,2019-09-09 16:02:49 UTC,Looks good Ian.  Thanks!
1794623,2019-09-07 17:08:05 UTC,"Looks like this is being caused by the unit binder in the text controls. When it parses the text, it will update the text in the control with the result. This causes the selection to be lost."
1794623,2019-09-07 10:06:58 UTC,"Whoops, spoke to soon. It looks like this is only a problem if the string is only numbers, and works if there is text in it."
1794623,2019-09-07 10:04:36 UTC,"This looks to have been fixed at some point, since I can't reproduce the original test case in either 5.1.4 or master."
1794623,2019-09-07 21:31:45 UTC,"The UNIT_BINDER does more than just parsing.  It will also evaluate (for instance, 3 + 4 will become 7)."
1794623,2019-09-07 23:10:05 UTC,"I found another alternative, we can load the primary selection clipboard with our own data and not rely on GTK to do it for us."
1794628,2019-04-01 20:37:45 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9688"
1794628,2019-08-12 20:38:16 UTC,"Reviewed:  https://reviews.mahara.org/9688
Committed: https://git.mahara.org/mahara/mahara/commit/fe195ddc4b8c095f38f1e832d99e58830c328f81
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1794628,2019-08-15 00:55:59 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10262"
1794628,2019-08-16 05:25:36 UTC,"Reviewed:  https://reviews.mahara.org/10262
Committed: https://git.mahara.org/mahara/mahara/commit/a38ddad4f44fdd84fdc801ac4934bcf9700f9af6
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1794630,2019-04-01 11:12:17 UTC,I am running into the same problem. For testing/evaluation I deployed a single graylog instance
1794630,2019-05-16 08:06:01 UTC,This has been released in cs:graylog-28. Please test and let us know if we can mark this bug as fix released.
1794630,2019-06-24 11:09:18 UTC,the fix still doesn't allow removing and re-adding mongodb and/or elasticsearch relations. Attached is a patch that correctly handles this
1794631,2018-09-26 23:34:09 UTC,Proposed fix here: https://code.launchpad.net/~cmars/graylog-charm/+git/graylog-charm/+merge/355742
1794631,2020-03-04 14:02:25 UTC,https://code.launchpad.net/~npochet/charm-graylog/+git/graylog-charm/+merge/368200 has been fix-released.
1794640,2019-10-30 12:33:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794641,2018-09-27 15:13:15 UTC,apport information
1794641,2018-09-27 15:13:17 UTC,apport information
1794641,2018-09-27 03:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794641,2018-09-27 15:12:06 UTC,apport information
1794641,2018-09-27 15:12:05 UTC,apport information
1794641,2018-09-27 15:12:04 UTC,apport information
1794641,2018-09-27 15:12:03 UTC,apport information
1794641,2018-09-27 15:12:01 UTC,apport information
1794641,2018-09-27 15:12:00 UTC,apport information
1794641,2018-09-27 15:13:16 UTC,apport information
1794641,2018-09-27 15:11:59 UTC,apport information
1794641,2018-09-27 15:11:57 UTC,apport information
1794641,2018-09-27 15:11:55 UTC,apport information
1794641,2018-09-27 15:11:54 UTC,apport information
1794641,2018-09-27 15:11:53 UTC,apport information
1794641,2018-09-27 15:11:51 UTC,apport information
1794641,2018-09-27 15:11:50 UTC,apport information
1794641,2018-09-27 15:11:58 UTC,apport information
1794641,2018-09-27 15:13:13 UTC,apport information
1794641,2018-09-27 15:13:14 UTC,apport information
1794641,2018-09-27 15:13:26 UTC,apport information
1794641,2018-09-27 15:13:18 UTC,apport information
1794641,2018-09-27 15:13:19 UTC,apport information
1794641,2018-09-27 15:13:20 UTC,apport information
1794641,2018-09-27 15:13:21 UTC,apport information
1794641,2018-09-27 15:13:23 UTC,apport information
1794641,2018-09-27 15:13:24 UTC,apport information
1794641,2018-09-27 15:13:25 UTC,apport information
1794641,2018-09-27 15:13:27 UTC,apport information
1794641,2018-10-02 15:03:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1794641,2018-10-22 15:00:50 UTC,Seems like there are some UEFI magic happens under the scene. Have you tried using the default macOS boot loader instead?
1794641,2018-10-31 23:17:54 UTC,"Yes, I have tried both mac and grub. Admittedly, I have blessed my refind installation and from their used refind to load grub. (My preferred method, given the number of boot options refind can handle). I haven't tried using the macOs bootloader to boot into linux directly."
1794647,2018-10-10 23:09:37 UTC,"> This wll trigger errors when live-migration to the source host.
"
1794647,2019-06-27 14:44:44 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/605590
Reason: I have a feeling this might already be fixed by now but would need to dig into it or try to recreate the bug on master. Either way it looks like this change is abandoned."
1794647,2019-06-27 14:50:38 UTC,I think this may have been fixed with https://review.opendev.org/#/c/566367/.
1794647,2018-09-27 05:43:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605590"
1794656,2018-09-27 05:23:37 UTC,Can not reproduce it on gnome-settings-daemon(3.30.0-0ubuntu1).
1794660,2019-05-28 15:48:31 UTC,same thing is happening to me  is there not a fix for this/
1794661,2018-09-27 06:24:41 UTC,"More info please see https://bugs.launchpad.net/cinder/+bug/1791213 .
Expected results:
Horizon should be able to list volume attachment and allow users to delete."
1794661,2018-11-25 22:59:07 UTC,There are questions to fix the bug. Can you clarify them?
1794683,2018-09-27 07:25:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605602"
1794683,2020-05-26 09:24:54 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/605602
Reason: This is an old patch with negative code review. I'm abandoning it."
1794683,2020-05-26 09:29:07 UTC,I don't think this is a bug per se. Soft delete means you might or might not want to restore the instance that is being deleted. If the instance is end up being really deleted then the port will be freed anyhow. But if the instance will be restored then the port is still need to be present so your instance is restored to the state from where it was soft deleted.
1794686,2018-09-27 14:03:49 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1794700,2020-03-07 16:08:35 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1794706,2020-08-06 09:56:38 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/608500
Reason: This is an old patch in merge conflict  connected an already expired bug. So I'm abandoning it. Feel free to restore it if you want to continue working on it."
1794706,2019-08-06 04:17:24 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1794706,2019-06-07 00:31:54 UTC,"Unfortunately, we will not be able to simply delete the instance if MessageDeliveryFailure is raised, because for the end user, they will have received 202 ACCEPTED from the API and then their instance never appears (or they see it, and then it disappears with no explanation). So, at best we could catch the exception and set the instance into the ERROR state with a fault message explaining the reason."
1794706,2019-06-07 01:44:24 UTC,"this might also be related to
https://bugs.launchpad.net/oslo.messaging/+bug/1661510"
1794708,2020-01-09 18:50:52 UTC,This issue was fixed in the openstack/oslo.service 1.38.1 release.
1794708,2019-08-30 11:52:04 UTC,"Reviewed:  https://review.opendev.org/641907
Committed: https://git.openstack.org/cgit/openstack/oslo.service/commit/?id=e7dd2916893157854ca0fa5f4215d536151abbb3
Submitter: Zuul
Branch:    master"
1794708,2019-09-23 15:08:17 UTC,"Reviewed:  https://review.opendev.org/680505
Committed: https://git.openstack.org/cgit/openstack/oslo.service/commit/?id=abfec6a48a01c80b861ebe7e151b8df23ff6b398
Submitter: Zuul
Branch:    stable/stein"
1794708,2019-09-06 02:57:49 UTC,"Reviewed:  https://review.opendev.org/679465
Committed: https://git.openstack.org/cgit/openstack/oslo.service/commit/?id=a7621c8c46378fb456f306dcf5f8cc7836b110d2
Submitter: Zuul
Branch:    master"
1794708,2019-09-03 19:05:48 UTC,This issue was fixed in the openstack/oslo.service 1.40.1 release.
1794708,2019-08-30 14:54:19 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/679465"
1794708,2019-03-08 16:20:52 UTC,"Change abandoned by Dan Smith (<email address hidden>) on branch: master
Review: https://review.openstack.org/641793
Reason: I still think the is-daemon check (and original justification) is wrong, but it's not the acute problem right now so I don't care enough to push on this."
1794708,2019-09-05 20:17:55 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/680505"
1794708,2019-03-07 20:32:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641793"
1794708,2018-09-28 12:53:26 UTC,FYI this bug report comes from https://bugs.launchpad.net/tripleo/+bug/1789680 if I understood correctly.
1794708,2018-09-27 16:56:41 UTC,Possibly linked to this problem https://bugs.launchpad.net/oslo.service/+bug/1793830 ?
1794708,2019-03-08 03:14:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641907"
1794708,2018-09-27 14:29:36 UTC,"This comment try to describe the ""wait"" method main changes timeline concerning this bug."
1794708,2018-09-27 12:17:29 UTC,If you look at this line https://github.com/openstack/oslo.service/blob/master/oslo_service/service.py#L668 you can see that a break are realised on SIGHUP so we don't make another shutdown.
1794712,2019-01-04 13:48:25 UTC,this is in progress at https://review.openstack.org/624705
1794712,2019-03-20 20:47:20 UTC,This issue was fixed in the openstack/placement 1.0.0.0rc1 release candidate.
1794726,2019-06-30 12:32:51 UTC,sorry my last comment was for #1648580
1794726,2018-09-28 23:00:40 UTC,"There was a bug in Lasso that caused the SIGNATURE_NOT_FOUND result with ECP. Having the namespace declarations on the soap envelope was not the root cause. However, that does not mean you shouldn't fix the location of the SAML namespace declarations, just that it wasn't the primary culprit."
1794726,2018-10-25 14:00:59 UTC,"FYI, there was a bug in Lasso which I fixed and supplied a test build to the reporter to verify the fixed worked. That was several weeks ago. I will follow-up to see what transpired."
1794726,2018-10-25 14:06:42 UTC,"Ah, now I remember. The fix was tested and this specific problem was resolved. However, they were encountering other problems once that issue went away and I was waiting for diagnostic information on the new issue (likely a configuration issue with ECP)."
1794726,2019-05-04 00:29:44 UTC,"It appears that the other issue was because we currently default to setting ""relay_state_prefix"" to ""ss:mem:"". That is what Shibboleth generally uses to prefix the relay state that it sends."
1794727,2019-10-10 15:10:17 UTC,I'm seeing the same issue:
1794732,2019-01-11 08:19:21 UTC,"When is tunneling coming? Missing it creates lots of extra work to add workarounds which might be unsupported once ""the solution"" is released."
1794745,2019-07-03 22:06:14 UTC,"According to https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13594 this has been fixed in:
v2.9.0rc0-1153-g536e26c55e
v2.6.2rc0-130-gc1fb20adc7"
1794745,2018-07-03 10:35:22 UTC,"Fixed the crashes in:
v2.9.0rc0-1153-g536e26c55e
v2.6.2rc0-130-gc1fb20adc7"
1794745,2018-07-03 10:32:56 UTC,"Change 28578 merged by Peter Wu:
Qt: fix crash on opening a capture file while loading/saving another"
1794745,2018-07-03 10:30:17 UTC,"Change 28578 had a related patch set uploaded by Peter Wu:
Qt: fix crash on opening a capture file while loading/saving another"
1794745,2018-06-30 19:44:02 UTC,"Change 28541 had a related patch set uploaded by Peter Wu:
Qt: fix crash on changing capture file while loading a previous one"
1794745,2018-07-03 07:58:04 UTC,"Change 28541 merged by Anders Broman:
Qt: fix crash on opening a capture file while loading/saving another"
1794745,2018-06-30 10:54:53 UTC,*** Bug 14351 has been marked as a duplicate of this bug. ***
1794745,2018-06-28 23:18:26 UTC,Confirmed case 2 with v2.9.0rc0-1112-g1108791d29. Quick reproducer:
1794745,2017-04-13 09:10:13 UTC,"Build Information:
Wireshark 2.3.0 (v2.3.0rc0-3070-g7c3c15a)"
1794745,2018-06-30 11:00:13 UTC,"The ""Crash #2"" scenario is caused by handling the ""startCapture"" action while the original file is still being read:
#4  0x00005555565c16ce in cf_close file.c:361
#5  0x000055555686e564 in MainWindow::startCapture ui/qt/main_window_slots.cpp:848
#6  0x00005555568be177 in MainWindow::on_actionCaptureStart_triggered ui/qt/main_window_slots.cpp:3582
...
#23 0x00005555569cb97d in update_progress_dlg ui/qt/progress_frame.cpp:77
#24 0x00005555565c567b in cf_read file.c:609
#25 0x000055555683ec10 in MainWindow::openCaptureFile ui/qt/main_window_slots.cpp:246
#26 0x000055555668064e in main ui/qt/main.cpp:831"
1794749,2018-10-08 19:16:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794750,2020-03-27 21:31:57 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1794750,2020-03-27 21:06:30 UTC,"Mr Raynsford,"
1794750,2020-03-27 19:49:41 UTC,I hadn't been back because Inkscape is an excellent program that works amazingly well. I haven't encountered any other bugs or things that I felt would be useful features :)
1794750,2020-03-27 19:25:05 UTC,"I deliberated on that issue for five days before deciding to close it, hence the ""If you feel this issue has been injustly closed...""."
1794750,2020-03-27 14:14:48 UTC,Reopening until this has been clarified.
1794750,2020-03-27 14:14:31 UTC,? Why has this been closed exactly? Has it been moved?
1794750,2020-03-27 13:46:05 UTC,Closing because INVALID: bug-migration.
1794750,2018-09-29 23:27:31 UTC,"You don't need a layer to apply a filter/blend mode (blend modes are filters) (see Object > Objects) or create a custom filter for it (you can put that custom filter into your default template, or add it to the filters file, to have it readily available)."
1794750,2018-09-29 22:46:32 UTC,"Sadly not, things imported from dxf do not have layers so having to break everything up into layers to apply a blend mode (especially if the dxf lines are disconnected) would be a lot more work."
1794750,2018-09-29 22:01:38 UTC,"I understand now, thank you, Martin."
1794750,2018-09-29 20:36:29 UTC,"You are right, in normal mode the zooming in and out essentially changes the line thickness on the display, it makes it hard to find the nodes on lines etc."
1794750,2018-09-29 00:21:40 UTC,Why don't you just set the line thickness in normal mode? Is it because of zooming that interferes?
1794750,2020-03-27 23:34:55 UTC,"Ha, I just wrote the same in the chat, @msraynsford ... :
https://chat.inkscape.org/channel/bug_migration?msg=2CT5wiqK6Bh4kfsSR"
1794750,2018-09-30 07:41:27 UTC,That's really useful to know. I've had a quick play with it but none of this gets past the zoom able problems first mentioned.
1794755,2019-04-28 15:52:18 UTC,"yes, that would be helpful.
Not sure if we need GUI buttons, but we could definitely create a keyboard shortcut for this."
1794757,2019-08-11 07:50:32 UTC,XML schema validation is not implemented in lxml but in libxml2.
1794759,2018-09-30 18:40:54 UTC,"Hi,"
1794759,2018-10-03 22:16:34 UTC,"Thanks for the answer, the problem is related to variety when the latter is active.
However, it is not the change of wallpaper that makes the image jump. I checked.
At a regular time interval or not, I observe the image of the browser (firefox) that jumps (for example I was watching a video and suddenly I see appear for 1s the window of my mail client open behind the window of my browser but the sound is not cut off)
When I leave variety manually this phenomenon does not appear anymore.
My graphics card is a Nvidia GEforce 840M.
Cordially."
1794763,2018-10-03 12:17:15 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1794763,2018-09-27 14:00:05 UTC,This change was made by a bot.
1794763,2018-10-02 15:02:21 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1794763,2018-10-03 06:44:21 UTC,"Joseph, thanks for your answer."
1794766,2018-09-27 14:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794766,2018-09-27 14:26:41 UTC,"Unable to send logs as this host is ipv6 only, and bugs.launchpad.net does not have a quad A record published (ERROR: connecting to Launchpad failed: [Errno 101] Network is unreachable)."
1794766,2018-09-27 15:26:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794766,2018-10-02 15:01:13 UTC,Bionic already has commit 639812a1ed9b since it was added to mainline as of v4.14-rc6:
1794766,2018-10-03 07:56:14 UTC,"On Tue, Oct 02, 2018 at 03:01:13PM -0000, Joseph Salisbury wrote:

> Bionic already has commit 639812a1ed9b since it was added to mainline as
> of v4.14-rc6:
>
> 639812a1ed9b nbd: don't set the device size until we're connected
>
> Can you confirm Bionic has this bug after applying all the latest
> updates?  If it does, we can perform a ""Reverse"" bisect, since you
> confirm this bug is fixed in 4.19-rc5.
"
1794771,2019-08-20 02:06:40 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/677327"
1794771,2019-12-04 08:48:11 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1794771,2019-06-14 20:33:57 UTC,https://review.opendev.org/#/c/665467/
1794771,2019-12-04 08:48:22 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/677327
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1794771,2018-10-05 14:26:01 UTC,This RFE was discussed and approved for implementation on October 5th
1794771,2019-09-04 19:52:25 UTC,"so another thing here is trunk creation would not be allowed after vms are created with sriov ports because api doesn't allow trunk creation for bound ports, could be an issue for sriov"
1794771,2018-09-28 15:04:33 UTC,"mlavalle,
1)  I don't see any changes to API as of now, We need to see if trunk port has any limitation to do it for SRIOV ports, which i don't think has any issues, will check again.
2) Yes work should be in sr-iov agent from neutron perspective."
1794771,2018-09-28 07:49:59 UTC,"You said that it is supported only by some vendors, so do You plan to add some discovery of this feature and validation on API level if it can be used or just documenting it properly will be enough?"
1794771,2018-09-28 00:38:47 UTC,Let me understand what is entailed in this change:
1794771,2018-10-04 22:58:51 UTC,"ok, let's bring this up to the drivers team"
1794773,2019-03-24 23:39:27 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1794773,2019-03-24 23:04:07 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1794773,2019-03-22 03:47:16 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1794773,2019-02-22 05:42:16 UTC,"Reviewed:  https://review.openstack.org/608573
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0794345ecd1d61efb7a0d321eb32844d2dd684d0
Submitter: Zuul
Branch:    stable/rocky"
1794773,2019-02-21 15:39:44 UTC,"The comment in the bug report description linking to [1] https://review.openstack.org/#/c/565841/ was merged in Stein, not Rocky."
1794773,2019-03-13 04:08:22 UTC,"Reviewed:  https://review.openstack.org/608611
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e46019a6e52452554b85f5c40a6e4b069172cd9a
Submitter: Zuul
Branch:    stable/queens"
1794773,2018-10-08 05:41:15 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/608573"
1794773,2018-10-04 22:05:42 UTC,"Reviewed:  https://review.openstack.org/605754
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=63b9c88386998bc584786ecb8ea7a2aae971a384
Submitter: Zuul
Branch:    master"
1794773,2018-09-27 14:39:00 UTC,Fix proposed: https://review.openstack.org/#/c/605754/
1794773,2018-10-08 09:02:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/608611"
1794811,2018-09-27 14:59:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/605765"
1794811,2018-09-27 15:07:16 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/605771"
1794811,2018-09-30 20:50:12 UTC,"Reviewed:  https://review.openstack.org/605765
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a5203536520578f016c6e0f849264039ff146f14
Submitter: Zuul
Branch:    master"
1794811,2018-10-01 11:28:42 UTC,"Reviewed:  https://review.openstack.org/605771
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=18cc479316e872ecf320136e160bdee5eb3f7469
Submitter: Zuul
Branch:    stable/rocky"
1794811,2018-10-08 20:53:25 UTC,This issue was fixed in the openstack/nova 18.0.2 release.
1794811,2019-03-22 03:47:14 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1794814,2018-10-01 06:40:28 UTC,"Just for the record, the snap application needs to have `daemon` set, you can use simple, forking, oneshot, notify etc.  If `watchdog-timeout` is not supported by snapcraft, then you can add it as `passthrough` option. On top of this, you also need to use `daemon-notify` plug to gain access to the notification socket and connect it manually once the snap is installed."
1794814,2018-09-27 18:54:02 UTC,"In the meantime, I am using the following as a workaround, not sure if there is a better way but this seems to work:"
1794814,2018-10-01 14:00:45 UTC,"Awesome, thank you very much! The minimal example works great."
1794820,2018-09-27 17:42:26 UTC,I'm tracking the private-files-strict and user-files portion of this bug in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794848
1794820,2018-09-27 19:23:16 UTC,"'And for ""audit deny @{HOME}/.config/autostart/**"", you'll probably have to block write access to ~/.config, if that's possible without breaking things? Otherwise someone could move the whole ~/.config directory as a bypass.'"
1794820,2018-09-27 16:46:24 UTC,"Thinking on this, more users clearly don't understand and there is a partial fix we could roll out before the inode labeling lands"
1794820,2018-09-27 16:23:13 UTC,I'll take a look at fixing that.
1794820,2018-09-27 16:30:02 UTC,I should add that apparmor's solution for this is planned but has not landed. It is a case where inode labeling will be used.
1794820,2018-09-27 16:41:02 UTC,"And for ""audit deny @{HOME}/.config/autostart/**"", you'll probably have to block write access to ~/.config, if that's possible without breaking things? Otherwise someone could move the whole ~/.config directory as a bypass."
1794820,2018-09-27 16:04:07 UTC,"yep, this should be well known."
1794820,2018-09-27 16:20:05 UTC,"It is well known, but there is a problem in out private-files-strict policy that we can address. We currently have:"
1794833,2019-02-14 12:43:50 UTC,"Openvswitch is not run in containers yet AFAIK. Even when it is, this bug is still valid because we cannot bounce the openvswitch services without potentially breaking data and control planes."
1794833,2019-02-12 13:33:58 UTC,Is it still an issue? Isn't ovs in containers now?
1794836,2018-09-28 06:46:09 UTC,apport information
1794836,2018-09-28 06:46:09 UTC,apport information
1794836,2019-01-08 09:52:20 UTC,It solved the problem!!! Million thanks
1794836,2018-09-27 16:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794836,2018-12-18 18:32:19 UTC,Still not working and no solution given :-(
1794836,2018-10-02 14:54:21 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1794836,2018-09-28 06:46:22 UTC,apport information
1794836,2018-09-28 06:46:21 UTC,apport information
1794836,2018-09-28 06:46:19 UTC,apport information
1794836,2019-01-08 02:25:03 UTC,"That's because ""nomodeset"" is in your kernel parameter."
1794836,2018-09-28 06:46:17 UTC,apport information
1794836,2018-09-28 06:46:17 UTC,apport information
1794836,2018-09-28 06:46:15 UTC,apport information
1794836,2018-09-28 06:46:14 UTC,apport information
1794836,2018-09-28 06:46:13 UTC,apport information
1794836,2018-09-28 06:46:12 UTC,apport information
1794836,2018-09-28 06:46:10 UTC,apport information
1794836,2018-09-28 06:46:18 UTC,apport information
1794839,2018-09-27 17:10:51 UTC,We do not support 'alignment-baseline'. We do support 'dominant-baseline' and 'baseline-shift'.
1794841,2019-05-16 13:45:36 UTC,"Sorry, we'll be sticking with u-boot for the foreseeable future. Partly this is because it keeps things (somewhat) consistent between the core and classic images, but also keeps things consistent between RPi and Ubuntu images for other embedded platforms. Were we to remove u-boot from the RPi images, it would make them a special case among all such images (it's also worth noting we may start inheriting u-boot configuration from Debian upstream in future; Debian also uses u-boot although we currently override their configuration for RPi)."
1794842,2018-10-03 14:03:42 UTC,I noticed that there is a new release labeled 3.18.9. Does this have the CDS feature included in it?
1794842,2018-10-08 15:28:30 UTC,"> What does ""CDS"" stand for and what is it intended to do?
"
1794842,2018-10-03 09:24:56 UTC,"Hi,"
1794842,2018-10-10 11:26:02 UTC,"The only place I can find any mention of ""cds"" is in installer/text_install.py:"
1794842,2018-10-03 11:06:55 UTC,"> We have added CDS feature as part of HPLIP 3.18.7 version.
"
1794842,2018-10-09 21:57:17 UTC,"> > What does ""CDS"" stand for and what is it intended to do?
>
> I thought that was a really easy question for someone to answer; maybe someone at HP?
"
1794845,2018-11-04 20:53:25 UTC,"This seems to be a problem specific to armhf architecture (and maybe all other special architectures that are only available at the http://ports.ubuntu.com repository server).
For i386 and amd64 architecture the download page does provide links, e.g. https://packages.ubuntu.com/trusty/amd64/ethtool/download"
1794845,2018-11-04 20:57:59 UTC,Probably a duplicate of Bug #1712523
1794845,2018-11-04 20:59:48 UTC,or a duplicate of Bug #1660938
1794853,2018-09-27 18:28:24 UTC,I don’t think we have intended to support this in KVM pods so decreasing priority to low!
1794853,2018-09-27 18:28:46 UTC,And this could potentially be an option for the pod.
1794853,2018-09-27 19:43:01 UTC,I filed this as a bug because we are setting <cpu mode='host-passthrough'/> on ARM64 and PPC64EL. Its just missing on AMD64 and S390X. Whatever we do I think we should be consistent across architectures.
1794853,2018-10-25 23:15:55 UTC,Upstream is now enabling KVM by default starting with kernel 4.20.
1794853,2019-09-19 12:00:25 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1794853,2019-11-24 19:26:23 UTC,ran into this issue as well. It does not seem consistent to apply host-passthrough as a default for ARM64 and PPC64 but not for AMD64.
1794860,2018-10-23 13:10:12 UTC,Here's a screenshot from Jeanette Lundgren.
1794860,2018-12-17 22:35:35 UTC,"Jason,
The boxes to increase the number of call numbers and number of items do not need to be that big, these boxes have room for at least a 1,000 digit number, way more than enough to add even 100 items at a time. And then there's the item# box. Are other networks adding copy numbers, i.e. c.1, c.2, etc.?  We gave up using copy numbers when items have specific barcodes for identification.  Even if networks do use it, it's bigger than needed. Is it possible to reduce the size of these three boxes to give room to the prefix/suffix boxes?"
1794860,2018-12-17 21:05:58 UTC,"Looking at this today, all of the width is taken up by the current controls. Simply making the prefix and suffix controls wider causes the view to wrap and makes the interface less usable, not more usable. (See screenshot.)"
1794860,2018-12-18 00:27:35 UTC,"Bootstrap (the CSS kit that is used in the staff client) is limited in what it can do to size the boxes. What you see in the screen shot is what happens when I ask it to make them the same size as the other boxes. By the way, that is only a size increase of 1 step, i.e. from 1 to 2. We don't actually have the ability to set the sizes to percentages or to fixed pixel widths with the tools that we're using. That is, unless we want to break the tools that we're using."
1794860,2019-07-05 15:01:22 UTC,"Jason, any further progress on this? I have a valid complete from one library that the size of the box is a showstopper for moving to the web client cataloging. Since the xul client will no longer be an option next year this is a real problem for them.
Janet"
1794865,2018-12-17 16:29:53 UTC,"Change abandoned by Hongbin Lu (<email address hidden>) on branch: master
Review: https://review.openstack.org/605265
Reason: Will be addressed by: https://review.openstack.org/#/c/625395/"
1794870,2018-09-27 20:41:04 UTC,"(3:18:02 PM) slaweq: mriedem: it's not a race
(3:18:30 PM) slaweq: mriedem: I saw it already before, it's some issue with neutron that it process request very slow, see: http://logs.openstack.org/70/605270/1/gate/tempest-full-py3/f18bf28/controller/logs/screen-q-svc.txt.gz?level=INFO#_Sep_27_01_11_47_552844
(3:19:12 PM) slaweq: so first request is processed very long, and tempest client has http timeout, so client retries same request but then network is already removed
(3:19:14 PM) mriedem: time: 66.6156189
(3:19:19 PM) mriedem: wow
(3:19:19 PM) slaweq: exacly :/
(3:19:26 PM) slaweq: *exactly"
1794876,2018-09-27 21:30:07 UTC,This change was made by a bot.
1794876,2018-10-02 14:52:48 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1794876,2018-10-02 15:54:21 UTC,"With the mainline kernel, the psmouse.synaptics_intertouch=1 kernel option does not appear to be necessary any longer, but I still need to un-blacklist the i2c_i801 module in /etc/modprobe.d/blacklist.conf and rebuild my initramfs."
1794876,2019-08-21 21:24:59 UTC,"This impacted me as well (X1 Carbon Gen 6, 5.0.0-25-generic #26~18.04.1-Ubuntu) . Un-blacklisting the module (and update-initramfs'ing) seems to have worked. Previously my touchpad was *highly* inconsistent and the Trackpoint either didn't work as well or I just never noticed it working; now both seem fine."
1794876,2020-01-25 08:26:50 UTC,"I was also facing with my touchpad on Ubuntu 18.04 + KDE plasma, so removed i2c_i801 from blacklist & updating initramfs worked for me."
1794876,2020-01-25 08:28:00 UTC,I am using DELL XPS 7590 model & removing from blacklist worked for me.
1794876,2020-02-12 18:19:03 UTC,"I'm using a new ThinkPad E495 laptop with a ""SynPS/2 Synaptics TouchPad"" and Xubuntu 18.04.4 with the current HWE kernel ""5.3.0-28-generic"" and I had a similar issue.  In my particular case, installing xserver-xorg-input-synaptics-hwe-18.04 returned normal function to the TouchPad."
1794877,2020-07-14 15:35:32 UTC,"We couldn't reproduce the bug and reporter cannot help in providing data, so we're marking as invalid. If anybody ever reproduces that, please ping here and reopen.
Thanks,"
1794877,2018-09-27 21:48:09 UTC,"I was reading assembly and comparing with the code to evaluate the accuracy of the registers during the dump, and also some points in which it could has failed."
1794877,2018-09-27 21:43:08 UTC,"A preliminary analysis of the problem, based in a crash dump collected."
1794883,2019-06-21 17:19:27 UTC,Committed to 5.1 in commit d80759efb8bc1ab9bf62f0319fd2b6b15259a023.
1794884,2018-10-02 21:36:45 UTC,Working branch user/jeffdavis/lp1609556-sru-z3950-opac-visible-copies has a fix that only includes OPAC-visible holdings in SRU/Z39.50 holdings output.
1794884,2019-07-29 14:54:15 UTC,"I have tested this code and consent to signing off on it with my name, Kyle Huckins, and my email address, <email address hidden>."
1794884,2019-10-03 22:07:19 UTC,"Pushed all the way to rel_3_1. Thanks, Jeff and Kyle!"
1794889,2018-10-22 15:58:43 UTC,This bug was fixed in the package linux - 4.15.0-38.41
1794891,2018-09-28 17:13:03 UTC,"Thanks, this is tough as folks tend to think of locked when the disable all is there. I agree that allowing an opening of things from there for actions is appropriate."
1794891,2019-01-17 02:24:12 UTC,"I'd like to point out, this isn't just how a user would expect it to work. This is also how it's documented to work: https://docs.jujucharms.com/2.4/en/juju-block"
1794891,2019-01-17 05:32:08 UTC,"@Chris Sanders (chris.sanders),"
1794891,2019-01-21 11:31:12 UTC,"Hi Anastasia, in the command groups table[0] there is no mention of ""run-action"", which would imply that actions can always be run. This is however not the case."
1794891,2019-04-29 01:28:38 UTC,juju run-action is being modified to bypass blocking[0]. We're aiming to have this landed in a release candidate shortly.
1794900,2018-11-28 07:49:41 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/432403
1794900,2018-09-28 03:50:15 UTC,"has this been tested in our FVT and documented in our doc as well?
also, please try detach as well..."
1794900,2018-11-28 07:10:43 UTC,I have fixed this in recent volume feature code.
1794900,2018-11-28 07:23:43 UTC,I suggest you add the patch link into bug so that we know where to find fix if any problem related occurs
1794906,2020-03-07 14:10:25 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1794911,2018-09-28 07:43:33 UTC,This had been fixed in Debian some weeks ago with the 2.40.1-4 package version. Ubuntu needs to sync it to its archives for solving your bug report.
1794922,2018-10-22 09:15:50 UTC,"More testing, this time also with Xubuntu 18.10, 32 bit."
1794922,2018-09-28 07:07:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1794922,2018-10-22 07:31:17 UTC,I *think* that this bug affects me too:
1794922,2019-07-24 20:42:44 UTC,18.10 is no longer supported.
1794922,2019-04-03 21:52:16 UTC,"Thanks Chris for your reply, but my machine is x86 :-(
I will try with other distro. :-("
1794922,2019-04-02 02:59:09 UTC,@chmp/@chmp99
1794922,2019-04-02 01:42:57 UTC,"Hi,
I'm with the same error and I don't understand the solution. Will be fixed only in the next release? There is some steps to run the live image (in my physical notebook, not emulated)?"
1794922,2018-10-25 07:30:46 UTC,installed lubuntu 18.04.1 on dell 755 without updates
1794922,2018-10-22 12:25:43 UTC,"More testing, this time also with Xubuntu 18.10, 32 bit."
1794922,2018-10-21 23:03:18 UTC,And did the virtual machine test fail?
1794922,2018-10-21 23:02:51 UTC,"Sorry to repeat myself if I'm doing so but there's a lot to scroll through here (feel free to summarize your findings by editing the description), but does this occur with a 64 bit image?"
1794922,2018-10-21 05:03:14 UTC,"I found a $HOME with 10gb space, so finally a virtual machine test"
1794922,2018-10-09 02:26:56 UTC,"did a test on a hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1794922,2018-10-22 02:45:04 UTC,"So you have EHCI enabled on the virtual machines? Without it, they're not testing similar conditions"
1794922,2018-10-08 05:19:15 UTC,Maybe installing in a virtual machine might be good idea?
1794922,2018-09-29 03:29:50 UTC,Downloaded http://archive.ubuntu.com/ubuntu/dists/cosmic/main/installer-i386/current/images/netboot/mini.iso
1794922,2018-09-29 01:47:03 UTC,Lubuntu 18.10 (today's daily image) on dc7700
1794922,2018-09-29 01:33:06 UTC,I've re-run zsync for latest image; no 'ehci-pci' messages on either dc7700 or 755 for Xubuntu x86  (but both drop to BusyBox/initramfs)
1794922,2018-09-28 22:38:24 UTC,"another update on xubuntu 18.10 (x86) iso
the same thumb-drive image runs fine on d610 (dell latitude laptop)
(no zsync yet)"
1794922,2018-09-28 22:17:28 UTC,"update on xubuntu 18.10 (x86) iso
both systems get to busybox; the dc7700 (other box) didn't show hundreds of those ehci-pci messages..."
1794922,2018-09-28 22:05:15 UTC,"Reply to ""Ubuntu Kernel Bot"""
1794922,2018-09-28 15:42:30 UTC,"Also let's check Xubuntu and netboot, too. They both have i386 images."
1794922,2018-09-28 15:40:25 UTC,"I note the linked report is 32 bit as well. Can you confirm this does NOT occur on a 64 bit machine? Be very careful if you're using a 64 bit machine that it's more likely to not have an EHCI controller. Roughly speaking, EHCI is 2.0-level USB while xHCI is 3.0 (UHCI being 1.0, which requires some additional memory hardware to support 64 bit FWIW). Since the errors relate to EHCI, this is going to be crucial. `lspci | grep HCI` should help out in that regard. It also might be good to check a 32 bit kernel on a 64 bit machine if you can get that test out of the way."
1794922,2018-09-28 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1794922,2018-10-08 06:58:22 UTC,"Sorry Walter, I should have updated with info from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795092"
1794926,2018-09-28 17:32:53 UTC,this sounds more like an issue with the firmware on that system.  calling it as described above works across the board on everything.  This is the only instance of failure I've ever heard of.
1794926,2018-09-28 17:31:33 UTC,"We don't check the channel... the call that checks the user list is this:
ipmitool user list"
1794926,2018-09-28 17:33:17 UTC,I take that back... grrr... but it won't block the cert.
1794931,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1794935,2018-10-02 21:55:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794936,2018-10-09 23:56:46 UTC,"Hello Samuele, or anyone else affected,"
1794936,2018-11-28 13:38:52 UTC,"The verification of the Stable Release Update for dh-golang has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1794936,2018-11-28 13:38:44 UTC,This bug was fixed in the package dh-golang - 1.34.2
1794936,2018-11-20 22:20:46 UTC,That worked better:
1794936,2018-10-14 23:46:03 UTC,Ahh silly me 1.34.1 added the fix to debian/patches but it's a native package.
1794936,2018-10-09 23:48:22 UTC,"> The dh-golang SRU needs a proper Regression Potential section please.
"
1794936,2018-11-20 19:38:18 UTC,"Hello Samuele, or anyone else affected,"
1794936,2018-10-02 23:44:35 UTC,"On Mon, Oct 01, 2018 at 07:39:32AM -0000, Michael Vogt wrote:

> I am much in favour of stop supporting powerpc in snapd. If we can make
> that official in the SRU page we have one worry less (in practical terms
> powerpc was never really fully supported because we don't build a core
> snap for powerpc).
"
1794936,2018-09-28 10:03:20 UTC,"Should SRU the new dh_golang I guess. Although why do you care about
buildability with gccgo?"
1794936,2018-10-03 21:29:33 UTC,The dh-golang SRU needs a proper Regression Potential section please.
1794936,2018-09-28 10:56:03 UTC,"that's a question for mvo, but afair is because some platforms we ""support"" have only that?"
1794936,2018-09-28 16:41:00 UTC,"On Fri, Sep 28, 2018 at 10:56:03AM -0000, Samuele Pedroni wrote:

> that's a question for mvo, but afair is because some platforms we
> ""support"" have only that?
"
1794936,2018-10-02 23:18:42 UTC,"While I entirely support the idea of snapd no longer caring about gccgo, this report does indicate a clear bug so I've uploaded a fix for dh-golang to the SRU queue."
1794936,2018-10-02 06:50:46 UTC,"marking as invalid for gcc-8. Awaiting reply now from the snapd team, if it should be ignored, or fixed."
1794936,2018-10-01 07:39:32 UTC,I am much in favour of stop supporting powerpc in snapd. If we can make that official in the SRU page we have one worry less (in practical terms powerpc was never really fully supported because we don't build a core snap for powerpc).
1794936,2018-10-02 08:51:18 UTC,Thanks for your reply @doko.
1794950,2020-11-12 07:11:10 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1794950,2021-01-12 04:17:15 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1794953,2018-09-28 14:14:34 UTC,In a cosmic live session there are permission denied errors mounting the content interfaces for gtk-common-themes.  Here's the output:
1794953,2018-09-28 14:24:08 UTC,And the apparmor denials:
1794953,2018-09-28 14:48:37 UTC,/proc/self/mountinfo:
1794953,2018-10-03 14:09:39 UTC,"I have reproduced, debugged and fixed this. The PR with the fix is at https://github.com/snapcore/snapd/pull/5912"
1794956,2020-03-30 21:10:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/716081"
1794956,2020-04-30 22:20:21 UTC,"Reviewed:  https://review.opendev.org/718586
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=63ed20b7e9d9a3856c7f2444473504ae6e634e4c
Submitter: Zuul
Branch:    stable/queens"
1794956,2020-04-14 18:48:33 UTC,A fix to ceph:pybind/rbd was merged: https://tracker.ceph.com/issues/44610
1794956,2020-04-09 01:03:39 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/718586"
1794956,2020-04-08 23:01:49 UTC,"Reviewed:  https://review.opendev.org/716081
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=5d62c72d3545ed59b4cb3300b5c2b75d0a443a99
Submitter: Zuul
Branch:    stable/rocky"
1794956,2020-04-03 14:51:40 UTC,This issue was fixed in the openstack/cinder 14.0.4 release.
1794956,2020-04-03 14:47:02 UTC,This issue was fixed in the openstack/cinder 15.1.0 release.
1794956,2020-03-30 15:33:48 UTC,"Reviewed:  https://review.opendev.org/715574
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=47caae4cbbcacf1d81554af4ea2bfec01a0f7c54
Submitter: Zuul
Branch:    stable/stein"
1794956,2018-12-21 14:20:55 UTC,Is there a corresponding bug elsewhere against librbd for this?
1794956,2020-03-27 21:25:47 UTC,"Reviewed:  https://review.opendev.org/714151
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=7bfd3c4dcf528ba900d6179ff06c227ea1016176
Submitter: Zuul
Branch:    stable/train"
1794956,2020-03-20 15:37:24 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/714151"
1794956,2020-03-13 20:07:55 UTC,"Reviewed:  https://review.opendev.org/606038
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=394fbd7e20dbd8fb8cc58510657753432c43fa9b
Submitter: Zuul
Branch:    master"
1794956,2018-10-24 03:57:05 UTC,"Do with python interactive model:
[root@dev ~]# python
Python 2.7.5 (default, Jul 13 2018, 13:06:57)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] on linux2
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> import rbd
>>> import rados
>>> cluster = rados.Rados(conffile='/etc/ceph/ceph.conf')
>>> cluster.connect()
>>> ioctx = cluster.open_ioctx('volumes001')
>>> image = rbd.Image(ioctx, 'vol01')
>>> image
rbd.Image(ioctx, 'vol01')
>>> image.close()
>>> image
rbd.Image(ioctx, 'vol01')
>>> image.unprotect_snap('snap01')
Segmentation fault"
1794956,2018-10-24 03:48:25 UTC,"hi Jon, I think that if you can do as followed, you will reproduce the issue.
- First of all, you must have integrated openstack with ceph.
- Change the config 'rbd_max_clone_depth' as '2' in cinder.conf, then restart the cinder_volume service.
- Create the first volume(named as vol01)
- Create the second volume(named as vol02) and the volume vol01 as the source volume
- Create the third volume(named as vol03) and the volume vol02 as the source volume. Now for vol01, the depth of vol03 is 2 which equals the 'rbd_max_clone_depth' in cinder.conf
- At this time, when we create the fourth volume(named as vol04) and the volume vol03 as the source volume. The cinder-volume service was crashed and the service was restarted."
1794956,2018-10-08 17:51:35 UTC,"Not reproducible here, need additional information."
1794956,2018-10-05 14:21:04 UTC,"""Child 28221 killed by signal 11"" indicates some kind of nasty bug here.  That probably requires a fix outside of just Cinder itself.  Is 28221 the cinder volume pid?"
1794956,2018-09-28 11:26:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/606038"
1794956,2020-03-27 23:35:27 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/715574"
1794956,2018-10-09 01:17:22 UTC,"hi Eric, more info about ceph packages are as followed:
On ceph cluster
ceph-common-12.2.5-0.el7.x86_64
ceph-selinux-12.2.5-0.el7.x86_64
ceph-mon-12.2.5-0.el7.x86_64
ceph-osd-12.2.5-0.el7.x86_64
ceph-radosgw-12.2.5-0.el7.x86_64
centos-release-ceph-jewel-1.0-1.el7.centos.noarch
libcephfs2-12.2.5-0.el7.x86_64
python-cephfs-12.2.5-0.el7.x86_64
ceph-base-12.2.5-0.el7.x86_64
ceph-mgr-12.2.5-0.el7.x86_64
ceph-mds-12.2.5-0.el7.x86_64
ceph-12.2.5-0.el7.x86_64
ceph-fuse-12.2.5-0.el7.x86_64"
1794959,2018-09-29 18:03:31 UTC,But it would interfere with current team stuff.
1794959,2018-09-28 11:45:23 UTC,This was discussed some time ago - perhaps putting the players into teams would do the trick... Might be available via LUA interface...
1794959,2018-09-28 12:18:54 UTC,"I´ve been using teams as a workaround in fri02, but they can´t work as desired there. It is necessary there that two players are enemies (different teams or teamless) while still unable to attack each other, and that p3 can attack p2 but p2 can´t attack p3. This can´t be implemented with the current team system."
1794959,2018-09-28 12:45:00 UTC,Well if you look at:
1794959,2018-09-28 12:49:17 UTC,Well I can imagine new variable for Player class like: std::set no_attack_players and then AI (and UI for human player) could read and follow this... should not be complicated on AI's side
1794959,2018-09-29 05:35:27 UTC,"We could have 3 states: enemy, ally, neutral. Neutral won't attack, but also not share the other player's vision."
1794959,2018-09-29 18:06:19 UTC,Why would it interfere with the current team stuff? team = ally. What I'm proposing is that we keep teams and enemies as they are and add a 3rd state.
1794959,2018-09-29 20:12:17 UTC,In the scenario i am working on i have implemented a prevent_attack function. This uses just the field_action window and checks if the attack button is there. Whenever a player clicks on an attackable building a warning is shown:
1794959,2018-09-30 06:16:10 UTC,"So, you want the player to be able to attack the enemy, and the enemy can never retaliate, because the settings forbid it? Or would the other player automatically change their state after being attacked? The latter case sounds like a war declaration, in which case we would not need individual states, but some diplomacy UI instead."
1794959,2018-09-30 08:06:40 UTC,"@kaputtnik: That´s an elegant fix! Unfortunately it works only for human player, right? Since AI doesn´t use UI elements.
@GunChleoc: Yes, I want the Barbarians to be able to attack the Empire, but the Empire must be helpless unless I explicitly allow them to strike back, which would be the case if and only of the barbarians have conquered a sizeable number of buildings. (Checking that is as easy as checking for the number of ""empire_*"" militarysites the barbarians own.). I want to allow the Empire to reconquer buildings they have lost, but not much more than that; especially they must not defeat the barbarians."
1794959,2018-09-30 12:32:05 UTC,The tested (in other strategy games) solution is to have an independent stance from every tribe to every other tribe. Everything else is suboptimal.
1794959,2018-09-30 14:46:02 UTC,"OK, independent stance it is, those are valid reasons :)"
1794959,2019-09-15 15:32:59 UTC,Migrated to https://github.com/widelands/widelands/issues/2119
1794959,2018-09-29 18:42:41 UTC,"Implementing this as a third state would go both ways, wouldn´t it? If the ""neutral"" state was set so p2 can´t attack p3, then p3 won´t be able to attack p2.
IMHO the best way to solve this would be to have for each player individually a list of players he mustn´t attack. p1 can then attack p2 if and only if they are on different teams (or teamless) AND p2 is not on p1´s ban list.
So, all team-related stuff would be unchanged and the new feature is merely a way to override the ''attackable==true'' state between enemies.
Also, this would provide a way to account for every imaginable constellation of player relations, so there won´t be need to implement something again for other very special cases…"
1794960,2019-09-15 17:02:53 UTC,Migrated to https://github.com/widelands/widelands/issues/1083
1794960,2019-05-09 14:07:55 UTC,The problem is worse in peaceful mode. I was able to push the ai back to its headquarter just by placing military buildings close to the border and waiting for it to dismantle its buildings.
1794960,2018-09-28 13:58:24 UTC,OK
1794960,2018-09-28 12:21:27 UTC,"I don´t think that´s the cause here. The AI starts with a lot of soldiers, and I could see that it still had several of them left in the HQ and no vacant positions at all…"
1794960,2018-09-28 13:16:03 UTC,"Yes, it seems not reasonable."
1794960,2018-09-28 13:33:55 UTC,"I have seen this many times now. Best to be seen while watching a 4 players AI only game on several maps. (normally I use full moon for that).
The behaviour is not related to whether the AI has contact with the enemy or not.
Even after having been in fight it dismantles strong military buildings with no obvious reason."
1794960,2018-09-28 11:55:57 UTC,I ques this is probably because of shortage of soldiers and too much vacant soldier positions....
1794960,2018-09-28 13:00:28 UTC,"Here´s a screenshot: The AI (red) just dismantled the Sentry, losing some territory that is now held by my Outpost. It also dismantles the Tower a few minutes later, which will not lose any territory but is also an obvious mistake."
1794960,2018-09-28 12:39:18 UTC,"I see. This behavior is controlled fully by genetic algorithm, so there is not much that can be done in the code, maybe do some C++ debug to see why AI decided to do it. BTW can you estimate the distance from dismantled militarysite to nearest enemy military site?"
1794962,2018-09-28 11:54:48 UTC,"Obviously this is hardcoded into AI logic - do not go on until construction of a lumberjack an/or a forester starts...
By my opinion this is very corner case.... it would need specific workaround for the case the buildings are prohibited..."
1794962,2019-09-15 15:22:04 UTC,Migrated to https://github.com/widelands/widelands/issues/3324
1794962,2019-05-15 07:40:45 UTC,I think this bug is fixed with the Ai-fixes branch. You just need to take care that if you make a second suplly chain (e.g. for logs) you need to tell the Ai about (adding an output line to a tribe specific building)
1794962,2019-05-02 06:41:12 UTC,For the expansion part I have opened a separate bug. There is already a fix described in.
1794962,2018-10-05 10:46:45 UTC,"I don´t see a reason why it should behave much different, except that it gets different starting wares and workers, and most importantly: no lumberjacks, foresters, mines, quarries, hunters can be built. That might cause conflicts with basic economy, so it could have some impact."
1794962,2018-10-05 10:18:52 UTC,"Um okay… well in that case you can just delete everything inside the scripting folder, then it´ll certainly work, though you´ll have to restore it later if you want to check how the AI behaves under scenario conditions…"
1794962,2018-10-05 09:34:18 UTC,I renamed init.lua but I still get:
1794962,2018-10-05 11:07:26 UTC,"Well, at least size of territory and territorial growth will be reflected to the training score...."
1794962,2018-10-04 19:17:28 UTC,"I looked at fri03 map, I have some issues due to some strange LUA errors and loadgame crashes. What should I strip to get ""pure"" map?"
1794962,2018-09-28 13:38:05 UTC,I guess that might have to do with basic-economy achieved but this could be workarounded in a scripting scenario. I can have a look into this after we have build 20 out.
1794962,2018-10-05 07:15:09 UTC,"What lua errors are you getting? The loadgame crashes are probably bug 1795871 I guess.
To play without scripting, just rename the fri03.wmf/scripting/init.lua to any other name"
1794962,2018-09-28 13:58:59 UTC,Might be
1794962,2018-10-04 11:30:37 UTC,"Perhaps this is not related to the basic economy after all… I now allowed the AI all buildings for testing, and it still refuses to expand, although there´s no apparent reason for it…"
1794962,2018-10-05 10:32:20 UTC,"Why, is there a reason for AI to behave differently if in scenario?"
1794962,2018-10-04 12:16:56 UTC,"It´s in my branch:
lp:~widelands-dev/widelands/fri03
data/campaigns/fri03.wmf
The AI takes players 2 (emp) and 4 (bar), player 1 is human player, slot 3 is empty."
1794962,2018-10-04 12:31:32 UTC,And could you have a look fri04 (same branch) please? Red player (atl) is performing very poorly there.
1794962,2018-10-04 11:44:46 UTC,"What map is it? If it has 4 similar positions, I can include it into pool of testing maps"
1794964,2018-11-29 14:05:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794982,2019-01-30 16:00:26 UTC,"Can we get this in for 19.04? This should be relatively low-risk to roll out there, and if we get regression reports, we can roll it back later."
1794982,2019-05-10 18:07:29 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1794982,2019-02-27 03:11:01 UTC,"This bug is fixed with commit f2f530e5 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=f2f530e5"
1794982,2018-09-28 14:15:37 UTC,We really should have had like a host-scoped option for that.
1794982,2018-09-28 14:12:40 UTC,"I don't have a broken mirror or proxy. We have tests in apt >= 1.2 (or 1.1) that check pipeline fixup. The test case we use there is packages a, b, c, d. Then we map the responses like this:"
1794982,2018-09-28 13:42:52 UTC,I can confirm that for AWS the S3-based mirrors are no longer in place.  You are correct that a caching proxy is used instead.
1794982,2018-09-28 13:35:18 UTC,Is that something you can do?
1794982,2018-11-28 04:17:47 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1794982,2018-09-28 13:34:50 UTC,"@Julian,"
1794986,2019-05-19 04:17:41 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1794986,2018-10-16 13:45:50 UTC,"No I tried many things like reinstalling the OS, trying with Ubuntu and CentOS. It always crash unfortunately."
1794986,2019-02-12 13:47:20 UTC,Is this still an issue? Can you try using CentOS 7.6?
1794986,2018-10-16 04:09:34 UTC,Hi. Do you find the solution for this?
1794988,2018-10-02 11:24:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1794996,2019-11-21 16:48:43 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/639357"
1794996,2019-04-26 17:16:27 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1794996,2019-03-24 23:04:47 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1794996,2019-03-22 03:45:54 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1794996,2019-02-26 14:48:55 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/639357"
1794996,2019-02-12 16:37:19 UTC,"Reviewed:  https://review.openstack.org/623359
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb61e864b98dde4955ab29f7a39c9935fbd5ffd0
Submitter: Zuul
Branch:    stable/pike"
1794996,2019-02-12 16:37:04 UTC,"Reviewed:  https://review.openstack.org/623358
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91455a522738572def003dfe5e4f0bec08255074
Submitter: Zuul
Branch:    stable/pike"
1794996,2019-02-12 08:43:03 UTC,"Reviewed:  https://review.openstack.org/623355
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6c7e53e21059f80325d728cf7dee2766da7a9471
Submitter: Zuul
Branch:    stable/queens"
1794996,2018-12-19 10:01:21 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1794996,2018-12-08 03:38:52 UTC,"Reviewed:  https://review.openstack.org/623349
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0208d64397731afa829bc08cd7b3b6494f0f05d5
Submitter: Zuul
Branch:    stable/rocky"
1794996,2019-02-11 21:53:39 UTC,"Reviewed:  https://review.openstack.org/623354
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c3fd5e5061b837a78a95705074239c3d2e41e644
Submitter: Zuul
Branch:    stable/queens"
1794996,2018-12-07 00:40:46 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/623358"
1794996,2018-09-28 14:15:24 UTC,This goes back to Pike because that's when the resource provider allocation cleanup code was added to the _destroy_evacuated_instances method.
1794996,2018-12-08 03:38:40 UTC,"Reviewed:  https://review.openstack.org/623348
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=83d74dbbb6b45bfeada0c0b9ac13385b126709bb
Submitter: Zuul
Branch:    stable/rocky"
1794996,2018-09-28 15:48:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/606122"
1794996,2018-10-29 11:47:38 UTC,"Reviewed:  https://review.openstack.org/606106
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d252f81573cdfe7a0966f134608bb85d17311e33
Submitter: Zuul
Branch:    master"
1794996,2018-12-04 03:34:49 UTC,"Reviewed:  https://review.openstack.org/606122
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=05cd8d128211adbbfb3cf5d626034ccd0f75a452
Submitter: Zuul
Branch:    master"
1794996,2018-09-28 15:00:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/606106"
1794996,2018-12-06 23:23:29 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623348"
1794996,2018-12-06 23:23:52 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623349"
1794996,2018-12-06 23:59:24 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/623354"
1794996,2018-12-06 23:59:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/623355"
1794996,2018-12-05 10:56:46 UTC,"Reviewed:  https://review.openstack.org/575190
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=604819b29c0bd43969747d32f6e3d818b3cbece7
Submitter: Zuul
Branch:    master"
1794996,2018-12-07 00:41:03 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/623359"
1794999,2018-09-28 16:19:45 UTC,"The attachment ""Fix wrong null pointer check"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1794999,2018-10-18 13:34:46 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better.
I took a look at your patch and I don't think it is the best solution. As far as I can tell, the problem is actually caused because of toolchain (gcc) version in bionic. I've tried to build the same version of pam-python on Xenial and it worked. So changing the logic, like your patch does, will probably break something else during execution or bring up other problems.
Also checking the build of pam-python with gcc8 brings up more errors during build, besides the one you mentioned. So the project needs an update.
Have you tried to contact upstream maintainer?
http://pam-python.sourceforge.net/
It seems like the project is not being developed anymore, so it might be difficult to get an answer, but worth a try.
Let me know if you have problems in contacting upstream maintainer."
1794999,2018-10-19 13:10:37 UTC,"So I took another look at the patch and the current code and maybe I was too hard in my response.
The current code is wrong as it will still make the string comparison even if dot is null. So the patch fixes this problem and should be proposed to upstream."
1794999,2018-10-30 14:02:49 UTC,"So I've talked to upstream and Russel mentioned that a new version is coming next year.
For more information:
https://sourceforge.net/p/pam-python/tickets/5/"
1795006,2018-10-16 19:01:31 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1795008,2018-09-28 16:20:03 UTC,"The attachment ""This is an example/hint how we solved it, might not be sufficient for the final solution."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1795010,2018-10-01 15:02:50 UTC,"Thanks - If I can help in any way to resolve the problem please feel
free to contact me"
1795010,2018-10-01 14:32:33 UTC,Thanks for filing this bug in Ubuntu.
1795012,2018-09-28 15:00:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/606104"
1795012,2020-02-20 11:17:54 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/606104"
1795015,2018-09-28 17:34:22 UTC,Confirmed : EG 3.2-beta1
1795015,2020-05-27 20:35:10 UTC,"I'm seeing the same thing in 3.4 and 3.5 when downloading the full CSV from Item Status, Check Out, and Items Out.  In my tests it's always been 6 spaces but one of our libraries downloaded a CSV from Item Status that had 34 spaces ahead of the title."
1795021,2019-09-12 14:37:03 UTC,"I'm having the same problem on Ubuntu 18.04.3 LTS.
gsd-xsettings is the reason my system is even fully filling the SWAP. Is there any possibility to debug this?"
1795021,2018-09-28 15:54:55 UTC,"top -bn1
top - 18:53:10 up 19:16,  1 user,  load average: 0,45, 0,99, 1,17
Tasks: 386 total,   1 running, 313 sleeping,   0 stopped,   0 zombie
%Cpu(s):  3,9 us,  1,1 sy,  0,0 ni, 93,7 id,  1,2 wa,  0,0 hi,  0,1 si,  0,0 st
KiB Mem :  8048180 total,   240784 free,  5832756 used,  1974640 buff/cache
KiB Swap:  8191996 total,  8191996 free,        0 used.  1807524 avail Mem"
1795021,2018-12-23 21:12:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795021,2019-03-26 07:38:27 UTC,"Hi Team,
I have the same problem on old and on a brand new installation:"
1795021,2019-09-12 14:38:38 UTC,"…and could this issue be related to this one?
https://bugzilla.redhat.com/show_bug.cgi?id=1668808"
1795021,2019-11-29 13:45:26 UTC,"Same here. The memory usage grows and grows. Currently it's at 1,4 GB but yesterday I had about 3,4 GB."
1795021,2020-08-10 01:22:55 UTC,This makes my Ubuntu installation hard to use after a day of use.
1795023,2018-10-04 21:34:51 UTC,"I have some tracks with a wrong key like ""c minor"" imported from the metadata.
I kike to reset it with the context menu,in the same way I can reset the beat grid."
1795023,2018-10-03 21:03:33 UTC,"Could you reproduce the bug?
To fix this, use ""find in files"" to find the existing menu entries than add the missing."
1795023,2018-10-04 21:11:16 UTC,"Actually I am not able to understand what that last line says ``But not ""key""``"
1795023,2019-02-07 22:30:01 UTC,https://github.com/mixxxdj/mixxx/pull/2007
1795023,2018-10-03 17:10:34 UTC,Can you please share more details?
1795030,2019-05-14 14:37:39 UTC,This issue was fixed in the openstack/os-collect-config 7.2.3 release.
1795030,2019-03-14 10:38:41 UTC,This issue was fixed in the openstack/os-collect-config 9.2.1 release.
1795030,2019-03-18 00:34:58 UTC,This issue was fixed in the openstack/os-collect-config 8.3.1 release.
1795030,2018-10-08 18:13:29 UTC,This issue was fixed in the openstack/os-collect-config 10.0.0 release.
1795039,2018-10-16 17:04:50 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1795045,2020-02-12 18:46:22 UTC,This problem still exists in Ubuntu 19.10.
1795057,2019-08-13 17:05:56 UTC,"The nets are assigned to the pads, so if you edit a footprint it will then push the nets out to connected tracks, zones, etc.  It just that the connectivity isn't getting updated or something."
1795057,2019-10-17 17:03:27 UTC,"@Art's use-case is panelization, which we don't really support."
1795057,2019-10-17 19:18:30 UTC,"Fixed in revision 09954336014fa43e947f413b2d441df15b8ccdd3
https://git.launchpad.net/kicad/patch/?id=09954336014fa43e947f413b2d441df15b8ccdd3"
1795059,2018-10-02 19:54:37 UTC,Remote parts are going away when using bases per LP: #1794805
1795062,2018-09-28 20:52:40 UTC,Confirm that your patch works.
1795062,2018-09-28 20:34:56 UTC,untested patch that might work...
1795062,2018-09-28 20:28:30 UTC,"The cleaner approach is to use the is_valid_name function to also check for length, which should resolve the issue."
1795064,2018-12-19 10:01:41 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1795064,2019-03-24 23:04:21 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1795064,2019-03-22 03:47:08 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1795064,2019-02-12 14:26:33 UTC,"Reviewed:  https://review.openstack.org/635921
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8049e9595bfcf041cd81a4dd353f6285a9806100
Submitter: Zuul
Branch:    stable/pike"
1795064,2019-02-11 21:53:28 UTC,"Reviewed:  https://review.openstack.org/635897
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8369a78af07b224f109586de398c702db342b49d
Submitter: Zuul
Branch:    stable/queens"
1795064,2019-02-08 19:29:42 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/635921"
1795064,2019-02-08 17:35:53 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/635897"
1795064,2019-04-26 17:16:06 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1795064,2018-12-07 18:12:21 UTC,"Reviewed:  https://review.openstack.org/610163
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dfbcf5e40bb51813f56f983e4f75e29a6034a830
Submitter: Zuul
Branch:    stable/rocky"
1795064,2018-10-03 16:56:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/607650"
1795064,2018-10-11 22:10:12 UTC,"Reviewed:  https://review.openstack.org/607650
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=035708c37d587e4c5ede7fe80270bdbff98016ac
Submitter: Zuul
Branch:    master"
1795064,2018-10-04 16:00:48 UTC,"Matt,"
1795064,2018-10-03 17:02:22 UTC,If we can sort out why the devices weren't showing up properly on the host (was the pci passthrough whitelist configuration correct? Or is it a known issue with the version of the kernel you were using with the types of devices?) then we could document something as a known issue...
1795064,2018-10-03 17:00:48 UTC,This has been around since Juno: https://review.openstack.org/#/c/98828/
1795064,2018-10-12 20:59:31 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/610163"
1795064,2018-10-03 15:51:58 UTC,Well the code itself is clearly fragile because it's blindly pop'ing a result from what could be an empty list:
1795064,2018-09-29 02:56:34 UTC,"This is what i found, I was running kernel 4.18.9 as soon as i have downgrade kernel to 3.10.0-862.11.6.el7.x86_64 it resolved my issue."
1795067,2018-09-28 20:46:12 UTC,https://review.openstack.org/#/c/606197/
1795069,2018-09-28 20:52:42 UTC,https://review.openstack.org/#/c/606197/
1795074,2019-02-02 06:25:12 UTC,Had some cool data in there but the fact is turning of SVIDEO speeded up the boot time to where it is not annoying and or reasonable.
1795075,2018-09-29 04:18:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1795075,2018-10-01 16:32:31 UTC,Can you please check / post your journal (journalctl -b 0; remove any private information). I suspect this is a duplicate of bug #1792932 - i.e. X crashes when starting the live session and restarts successfully.
1795075,2018-10-07 09:32:53 UTC,"I only get login screen when selecting ""Try Ubuntu without installing"" from boot menu. If I boot without selecting any options - I land on installer where I choose ""Try Ubuntu"" and it goes straight to desktop, without displaying login.
Yes, it was actually https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1792932 - got same error messages in log."
1795079,2018-09-28 23:13:31 UTC,"Ok, I over-interpreted some of the tickets - it doesn't get far enough to run into the permissions problems, because it doesn't deal with `virtio` being builtin instead of a module (which is what the error is from, the `writerKernelModules` function in `fakemachine/machine.go`. Still in the ""why is this in ubuntu if there's no way for it to actually work"" category, though."
1795079,2019-04-06 09:00:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795092,2018-10-05 04:52:58 UTC,"The x201's native OS is Ubuntu 16.04 LTS (x86_64), the native OS for dc7700 is Ubuntu 14.04 LTS (x86_64), but whilst we haven't proven the debian issue is the problem, it relates to i686 only (not amd64).  I can add the kernel to the x201 (if it had HWE enabled, it'd almost be there anyway), but I don't expect issues on amd64."
1795092,2018-10-18 03:27:14 UTC,SORRY
1795092,2018-10-08 14:59:20 UTC,"Thanks for all the testing, Chris. It leaves me a little baffled."
1795092,2018-10-05 11:34:41 UTC,"found my xubuntu 18.10 daily image iso (updated this morning 2018-10-04 is date found in zsync)
xubuntu plymouth screen, ctrl-alt-f2 & scrolling"
1795092,2018-10-05 11:03:24 UTC,"installed lubuntu 18.04.1 on dell 755 without updates, format of /, but used my old /home (from fedora). rebooted post install, pointed sources to my ISP's ubuntu mirror (bandwidth free updates) & dist-upgrade. I added xubuntu-desktop & some of the apps missing from my modified xfce desktop."
1795092,2018-10-05 05:44:53 UTC,"your second link opened to i386/686 kernels, so I'm guessing yes (to i686/i386)"
1795092,2018-10-25 07:32:34 UTC,-- i re-did test from comment #13 (oct 5) hopefully correctly using lubuntu
1795092,2018-10-04 18:18:34 UTC,"If possible, maybe you could install an older release such as Bionic?  There are older iso images here:
http://releases.ubuntu.com/"
1795092,2018-10-03 22:21:56 UTC,changed to confirm as system won't boot; I can't run ubuntu-bug using that image.
1795092,2018-10-03 22:30:45 UTC,"It is my suspicion that the change occurred at switch to 4.18; but only because of timeline, and Walter (WXL) discussion providing a link to a possible cause that was introduced shortly after what I recall as being my last successful test on those machines (755, dc7700 anyway)"
1795092,2018-10-03 22:19:40 UTC,I no longer have a 4.17 image; and my requests for if anyone who knows where one is (on irc) got no answer.
1795092,2018-10-02 15:32:04 UTC,"Are you able to boot with older releases on these systems that are failing?  If so, we can test out the cosmic kernels and try to narrow down the commit that introduced this regression."
1795092,2018-10-01 16:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1795092,2018-09-29 05:10:20 UTC,"same issue on lenovo thinkpad x201  (i5, 4gb, i915)"
1795092,2018-09-29 04:18:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1795108,2018-09-29 13:19:33 UTC,apport information
1795108,2018-09-29 13:19:34 UTC,apport information
1795108,2018-09-29 13:19:35 UTC,apport information
1795108,2020-11-16 08:48:49 UTC,I can't reproduce this in 20.04 or 20.10 so please let us know if it's still a problem.
1795108,2021-01-16 04:17:23 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1795108,2018-09-29 13:19:35 UTC,apport information
1795109,2018-09-29 13:20:59 UTC,apport information
1795109,2020-04-15 22:28:33 UTC,"In my system, this started with ..."
1795109,2018-11-19 09:39:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795109,2018-09-29 13:20:56 UTC,apport information
1795109,2018-09-29 13:20:55 UTC,apport information
1795109,2018-09-29 13:20:57 UTC,apport information
1795114,2018-11-08 01:53:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795115,2018-10-04 17:07:56 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1795124,2018-10-04 17:05:00 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1795124,2018-10-08 13:00:11 UTC,"Checking the github repo of fail2ban, I can see that a newer version of the logwatch script is available (revision 1.6) at `https://github.com/fail2ban/fail2ban/blob/master/files/logwatch/fail2ban`. Logwatch 7.4.2 comes with the 1.5 revision of said script, which is apparently not equipped to handle the new log messages. So I guess it's not really a bug, more like a version incompatibility."
1795135,2018-10-24 20:23:30 UTC,Not sure it's helpful to add all panel-like applications that are affected by this problem to the bugreport - unless of course you want to track which applications implemented the same workaround (which seems to be the only known workaround anyway - if you don't want to intercept X11's signals manually).
1795135,2018-10-23 21:52:39 UTC,I have written a patch that employs the only known/reasonable workaround so far for the issue within xorg: https://git.xfce.org/xfce/xfce4-panel/commit/?id=e56e8699e271cea209f5b283421952d9035ad2b5
1795135,2018-10-24 02:09:27 UTC,If there is still a Xorg bug here then please log it upstream here:
1795135,2018-10-24 02:10:29 UTC,"Sorry, I see you already did that on bugs.freedesktop.org."
1795135,2018-10-24 14:20:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795135,2018-10-24 15:08:58 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1795135,2018-12-17 17:27:26 UTC,-- GitLab Migration Automatic Message --
1795135,2020-07-03 08:10:29 UTC,"It's ""Won't fix"" only for the component xorg, because it won't/can't be fixed in that component."
1795135,2019-03-03 12:42:18 UTC,This issue is resolved with greybird 3.22.10-1 and xfce4-panel 4.13.4-1
1795135,2019-03-05 14:48:38 UTC,"(Those tags just make the bug drop off our desktop team report, don't worry about it)"
1795135,2019-04-20 12:26:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795135,2020-04-26 03:27:02 UTC,"This bug was fixed in Xubuntu 19.04, if I remember correctly. But on later releases it became reproducible again."
1795135,2020-04-26 17:40:49 UTC,"Confirmed in 20.04 with screenshot, weather applets, and notification area applets
whiskers menu, clock, and show desktop are unaffected"
1795135,2020-07-03 01:52:29 UTC,"Reason for ""Won't Fix""?"
1795135,2018-10-23 17:42:23 UTC,So obviously this is a known bug and literally every panel-like application is affected. It also seems there is no good solution so far apart from the aforementioned workaround of switching away from xinput2 via the environment variable.
1795135,2019-03-03 12:30:01 UTC,The new upstream url for the Xorg bug is https://gitlab.freedesktop.org/xorg/xserver/issues/577
1795135,2018-10-22 20:10:28 UTC,"Ok, so a bit further down the debugging road I know that this issue is related to libxinput2.
I noticed that the enter/leave-notify events were firing because the panel's extents start at 0x0 but moving the pointer towards the top of the screen in combination with the sub-pixel handling of xinput2 produces negative coordinates, e.g. -0.6185, so a leave-notify event is fired, even though the panel should not have lost focus."
1795135,2018-01-26 14:13:15 UTC,"Created attachment 136974
effect of the bug on menu in MATE desktop"
1795135,2018-10-18 13:14:09 UTC,"I guess you noticed this already but the problem only occurs at 0x0, so with a panel on the left or a panel on the top of the screen.
The behavior is fine with panel on the right or lower side of the screen."
1795135,2020-07-03 12:34:20 UTC,"Awesome!
Any idea when it will land in the ubuntu groovy repos?
Just pulled it into my 20.04 install and it seems to not be there yet
$ xfce4-panel --version
xfce4-panel 4.14.4 (Xfce 4.14)"
1795135,2015-10-26 17:29:03 UTC,"On gnome-shell, if I run xinput test-xi2, side-maximize it on the left by dragging the window to the left edge, the window will end up aligned to the left screen edge. However, moving the pointer towards that edge will sometimes issue events like:"
1795135,2017-03-22 02:56:56 UTC,"It has been reported that it affects windows placed to the left and top of the screen. I just want to add that it's affecting panels (maybe it's the same thing. Is it?) The wingpanel of elementary OS doesn't always recognize the pointer passing over and clicking, same with Budgie's top panel and MATE's. Unity works fine, and so does Cinnamon and Gnome."
1795135,2017-07-02 18:51:16 UTC,"This bug will die with Xorg. No activity. No reports elsewhere. No way to set a bounty on it. Wayland is not affected, it seems."
1795135,2018-01-24 17:20:41 UTC,Xfce4-panel 4.13 and higher - the new version relying on gtk3 - is hit by this too. Really annoying.
1795135,2018-01-24 17:25:45 UTC,"Created attachment 136946
app with button in the top left corner"
1795135,2018-10-18 13:17:23 UTC,In fact if you debug the panel a bit you'll see that the enter-notify and leave-notify events are constantly firing with a panel at 0x0 and behaving correctly on the other screen edges.
1795135,2018-01-27 01:10:10 UTC,(In reply to Douglas from comment #1)
1795135,2018-01-27 15:46:14 UTC,"Thank you very much Egmont for your time. Just testing the patch against 1.19.6 (it is also applicable to current git version). So far so good. I will try to post a short memo of this bug at xorg-devel, hopefully it will get some notice."
1795135,2018-01-28 18:09:09 UTC,"Testing a bit more, I found it is not necessary to substitute trunc with floor; the patch works when only the part setting root_x_frac and root_y_frac to zero is left in."
1795135,2018-01-29 17:11:24 UTC,"Gave this a quick test in the hopes that it might fix (or at least improve) bug 92186. Unfortunately, it looks like all this does is just result in the loss of fractional coordinate data, causing errors to increase slightly across the board. E.g., the first row of the table in the linked bug would now report a root coordinate of ""164.00"" making the delta from expected ""-3.70"" instead of ""-3.00""."
1795135,2018-01-29 19:49:22 UTC,"Jason, I'm sorry to hear that my patch makes another bug a bit worse. My patch consists of two parts, either one is sufficient to fix this bug here. Could you please maybe try which of its two parts cause that regression?"
1795135,2018-01-31 11:29:52 UTC,A few suggestions.
1795135,2018-03-21 20:13:34 UTC,Any news about this?
1795135,2018-09-30 20:31:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795135,2018-01-27 01:22:36 UTC,"Created attachment 136979
Fix"
1795138,2018-12-16 12:11:40 UTC,"I get normal Icons back, but I do not know the context."
1795138,2018-12-12 10:35:16 UTC,similar in bionic on Lenovo ThinkPad T430.
1795138,2018-12-12 10:43:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795138,2018-10-10 20:41:43 UTC,Does the upower command report the correct status?
1795139,2018-09-29 18:42:16 UTC,"Multi-line rule are supported in some places (dbus, signal, etc). However this is dependent on how the rule is parsed."
1795141,2018-10-01 15:26:16 UTC,"Hhm, it is not easy to understand the problem. Could you please tell me the software used to make the server so I can try reproducing it?"
1795144,2018-11-27 01:41:24 UTC,0.9.1 actually
1795144,2018-11-07 21:48:47 UTC,@alexxcons thank you!
1795144,2018-11-07 21:13:01 UTC,Alexander Schwinn referenced this bugreport in commit 608dd1d0ae60e58080d18d423ca6024354bc24f8
1795144,2018-11-07 21:05:07 UTC,"Created attachment 8093
fix"
1795144,2018-11-07 21:27:25 UTC,"fixed, will be released in thunar-volman 0.10.0"
1795144,2018-11-07 16:47:39 UTC,"The bug happens when in the thunar-volman GUI, ""Browse removable media when inserted"" is enabled."
1795144,2018-11-07 16:12:25 UTC,"isn't there an ""xfce4-volman"" app? That would be the right solution"
1795144,2012-11-23 19:36:15 UTC,(XFCE 4.10 on Xubuntu 12.10)
1795144,2018-11-07 20:40:47 UTC,"Hah, interesting configuration, so you are running a thunar daemon in the background, featuring thunar-volman, just to open some other file-manager :P"
1795150,2018-09-29 16:00:56 UTC,"Once the turnaround applied, 'lpstat -v' returns ""matériel pour Maison-Canon_MG4250 : cnijnet:/00-BB-C1-90-A8-B4"".
The computer is a HP Laptop 14-cf0013nf."
1795150,2018-09-30 07:18:54 UTC,"I also had the same problems (and same solution) with a Dell laptop Latitude E6430s, with the same system (fresh install, as upgrade from 16.04 did not work)."
1795150,2018-09-30 07:21:48 UTC,"I left a message on Canon site, in a survey, about the obsolete dependencies in their Debian package."
1795152,2018-09-29 16:17:39 UTC,Ich mache nix mit der Kommandozeile. Das ist Eure Sache.
1795159,2018-10-17 05:32:38 UTC,Definitely been changed somewhen.
1795159,2019-12-26 11:06:35 UTC,Can i help? if Yes pls point me in the right direction!
1795180,2018-10-15 12:43:55 UTC,"Thx Eric, So I will remove neutron from affected projects then."
1795180,2018-10-11 08:54:17 UTC,"Thanks Slawek, sounds like I need to address this with the openstackclient project, which I couldn't find on launchpad (and forgot about storyboard)."
1795180,2018-09-30 01:07:34 UTC,"Hi Eric,
I guess openstackclient project would be a good place to start with. I cannot simply tell whether neutron is affected or not since it needs further triage."
1795180,2018-10-11 08:37:53 UTC,"I don't think that neutron can filter things based on domain. From api-ref: https://developer.openstack.org/api-ref/network/v2/#filtering-and-column-selection it looks that it can filter on fields which belongs to specific project as this is field in Neutron's db.
We don't know anything about domain in neutron.
Isn't it more ""global"" issue then?"
1795187,2018-09-30 01:25:24 UTC,"That's unfortunately true, most of the guide reflects vanilla GNOME. The simple reason is a lack of manpower; we'd need more contributors for the desktop guide."
1795187,2018-09-30 01:37:05 UTC,how would one go about contributing ubuntu specific changes?
1795187,2018-09-30 17:27:43 UTC,You'd get involved in the docs team to start with. :)
1795202,2018-09-30 07:06:54 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1795202,2019-07-07 04:26:33 UTC,I'm marking this invalid as it was a hardware issue.
1795206,2018-09-30 07:22:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/606789"
1795206,2018-10-01 11:24:51 UTC,I think we want to move into the other direction and change other services to work similar the way keystone already does instead of continuing to have people rely on the legacy setup.
1795206,2018-10-03 07:09:47 UTC,"I agree with Harbott, let's move to new way than supporting legacy port usage."
1795207,2018-10-12 14:29:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795207,2020-05-25 15:43:17 UTC,Still affecting me upgrating from 18.04 LTS to 20.04 LTS
1795207,2020-10-01 12:44:11 UTC,Confirmed affecting me upgrating from 18.04.5 LTS to 20.04.1 LTS
1795207,2020-11-10 09:30:25 UTC,Confirmed for upgrading 18.04.5 LTS to 20.04 LTS
1795212,2018-12-18 08:40:59 UTC,"Ok, one more question. Imagine the case when:
1. Agent starts and is doing full sync - so it gets list of ports and networks from server and starts configuring it one by one, right?
2. During this time, processing of incoming RPC messages is blocked, right?
3. Now (still during initial full sync) someone deleted ports so port-delete-end message is send to DHCP agent but this agent refuse to process this message, right?
4. Full sync is end and agent is still handling port which was deleted in 3. - am I right? Or will it be cleaned somehow?"
1795212,2018-12-18 00:48:00 UTC,"@slaweq
Thanks for the comments.
From our point of view, it does not matter how long the full sync takes. Processing any RPC messages, even ones that are not stale, before the initial full sync completes is not guaranteed to provide consistent results.
For example, if a port-update-end arrives before that port is received as part of the initial sync it will unnecessarily result in a full resync on that port’s network. Similarly, if a port-delete-end arrives before that port is received as part of the initial sync then it will be added to the “deleted_ports” list but that list is not referenced during the full sync so the information for that port will remain in the DHCP configuration for that network even though the port no longer exists. That will cause issues later when a new port is created and uses the IP address of that deleted port.
We were opting the agent delay approach in the spirit of avoiding compatibility changes and changes that would impact running against an unmodified server. We agree that timestamp is a good approach but that will come with backward compatibility constraints and additional complexity.
Let us know if any further question or concern. Thanks!"
1795212,2018-12-19 02:19:24 UTC,"@slaweq
The RPC handlers (e.g., port_update_end) are all wrapped with “_wait_if_syncing” so they don’t actually start processing until after sync has completed. We are only trying to prevent messages from being processed between the start of the process lifetime and the beginning of the initial sync. That window is what leads to the issues we have noted."
1795212,2018-11-07 20:57:13 UTC,"Moving this RFE to the confirmed stage. We are waiting for submitter to update his proposal before moving the RFE to triaged state, where we will discuss it again in the drivers meeting"
1795212,2018-12-21 09:58:05 UTC,"@Miguel
The RPC handlers (e.g., port_update_end) are all wrapped with ""_wait_if_syncing"" (https://review.openstack.org/#/c/609463/10/neutron/agent/dhcp/agent.py@491).
When that initial ""sync_state()"" is running, it will acquire a write lock to block all operations for a global sync call (https://review.openstack.org/#/c/609463/10/neutron/agent/dhcp/agent.py@491). During this time, if a RPC message is sent to the DHCP agent, it will wait if any sync operations/writers are in progress due to the ""_wait_if_syncing"" decorator mentioned above. And it will start processing after the sync (""sync_state()"") has completed.
So, IMO the corner case described by Slawek will not happen since the message received during that sync process will not be dropped and will be handled later."
1795212,2020-04-21 09:06:19 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.opendev.org/609463
Reason: Please, feel free to retake this patch if needed."
1795212,2018-12-21 01:33:58 UTC,"Looking at the proposed code (https://review.openstack.org/#/c/609463/10/neutron/agent/dhcp/agent.py@168), while that initial sync_state() is running, the corner case described by Slawek can still happen, right? Because at that point self._block_rpc == True if conf.initial_state_delay > 0"
1795212,2018-12-16 08:51:37 UTC,"I understand problem which You described here and I can imagine how it can happen in some corner cases.
I'm however afraid that approach with some configurable delay isn't good approach because You can't know how much time agent will need to do full sync after restart.
IMO if You want to solve this problem, You should try to do something based on timestamps and discard messages which came before agent was started."
1795212,2018-10-24 03:10:25 UTC,"Dear drivers team,
Since the patch is pretty much in a good shape, can we have this RFE triaged/discussed during this week's drivers meeting on October 26th? Thanks!"
1795212,2018-10-26 15:19:29 UTC,"Questions to follow up based on the discussions during drivers meeting on October 26th:
1. amotoki: what kind of corner cases and negative behaviors could happen (even with full sync)?
2. slaweq: in some (very) old releases rpc queues which agent's registered had some random id, so when agent was e.g. restarted it created new queue and would not consume messages from this old one.
AR: To double check slaweq's statement and clarify failure modes in question, i.e., what actually happens, together w/ Q1.
3. haleyb: doing it without a config option somehow? e.g. Resource queue with ExclusiveResourceProcessor used in L3 agent"
1795212,2018-11-21 04:34:08 UTC,Some answers to the questions raised in the last driver meeting.
1795212,2018-10-10 15:57:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/609463"
1795212,2018-10-08 06:17:43 UTC,"Hi Miguel,
It is not a replacement for the cited spec related with agent load re-balancing.
This one targets to address another issue about stale RPC messages processed by DHCP agents when they restart up, which is usually seen in a rescheduling scenario.
Let me know if any further question, thanks!"
1795212,2018-10-04 23:31:20 UTC,"Hi Kailun Qin,"
1795212,2018-09-30 08:54:33 UTC,"Two solutions are considered to tackle with this issue:
1) Introduce a new configurable startup delay to the DHCP agent. Within that delay, no stale RPC messages should be allowed to be processed. We'll wait for the RPC messages to be synced during this startup delay.
2) Introduce a timestamp/sequence number in the RPC messages sent between the server and DHCP agents. In this way, we may define a dead time/limit for the stale RPC messages so that they could be discarded."
1795221,2018-09-30 10:18:39 UTC,Changing the code above so that it uses the code in the except: clause unconditionally produces the desired result.
1795223,2019-01-09 10:22:29 UTC,In fact it's a known bug and has been fixed upstream in https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/267
1795223,2019-01-09 10:23:48 UTC,the fix is https://gitlab.gnome.org/GNOME/gnome-control-center/commit/8b8b49e9 and has been commited to gnome-3-30 after 3.30.2 was out
1795223,2018-12-12 10:52:45 UTC,Thank you for your bug report. Does it do every time? Could you take a screenshot showing the issue?
1795225,2019-07-27 17:59:21 UTC,"XPath is implemented in libxml2, not in lxml."
1795226,2018-10-03 11:47:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795227,2018-10-01 12:09:16 UTC,"For clarity, I've attached a patch that reverts the removal of the globals."
1795230,2018-10-01 14:11:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795230,2018-10-01 14:34:23 UTC,"Marco, you did that SRU. Did you see/hear about other similar problems? Any idea what the issue could be?"
1795230,2018-10-01 14:33:49 UTC,"The bug is not easy to work on without a reproducer or a debug backtrace. Can you share the binary you are using which is hitting the issue? If not could you at least get a debug backtrace (install the debug symbols for libappindicator and libglib2.0-0, see https://wiki.ubuntu.com/DebuggingProgramCrash for detailled instructions on how to do that)"
1795230,2018-10-01 14:19:43 UTC,Thanks a lot Vishnu!
1795230,2018-10-01 15:17:09 UTC,"Mh, not that I'm aware of, but also not having a full stacktrace doesn't help."
1795230,2018-10-01 13:58:49 UTC,"We tried with the package which was given above (AMD64 - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3389-deletedppa/+build/15310024) , and still we facing the same issue and same gdb back trace as well."
1795230,2018-10-01 11:29:19 UTC,"Can you reproduce the issue in a previous version, such as 2.56.2-0ubuntu0.18.04.1?
Also, is there any POC/test in how to reproduce this?"
1795230,2018-10-01 13:40:00 UTC,"Here is the back trace when running using GDB,"
1795230,2018-10-01 11:50:06 UTC,"When we tried to install glib 2.56.2-0ubuntu0.18.04.1 it was giving an error like this,
E: Version '2.56.2-0ubuntu0.18.04.1' for 'libglib2.0-0' was not found."
1795230,2018-10-01 11:13:41 UTC,"Here is the stack view of the time of crash happened ,"
1795230,2018-10-01 10:53:46 UTC,"Hi Amit,"
1795230,2018-10-01 08:47:42 UTC,"Could you give details on the segfault, maybe a backtrace from gdb? Did you try downgrading the glib package to verify if that resolves the issue?"
1795230,2018-10-01 13:41:25 UTC,"By the changelog, glib2.0 was update to a new upstream release from 2.56.1-2 to 2.56.2 and so a security update was done over it."
1795231,2020-08-09 23:51:51 UTC,openbve 1.5.3.8
1795232,2020-03-07 16:07:01 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1795232,2020-05-07 04:17:25 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1795238,2018-10-01 09:21:39 UTC,"while trying to figure out what the Path Effect does, I got the following unexpected output:"
1795238,2020-03-18 16:15:10 UTC,Closing because LPE Text Label has been removed (checked against 0.92.4 and 1beta02).
1795238,2020-03-18 16:22:46 UTC,:-/ It has only been disabled.
1795241,2018-09-30 21:16:21 UTC,"@Gioele,"
1795241,2018-09-30 20:01:46 UTC,It id possible to get this with the microwave tools. Please examplify your exact use case.
1795241,2018-10-01 08:57:32 UTC,"I could see it being useful when running a trace (say) of width 2mm horizontally into an SMD pad of height 2mm and width 1mm - currently you get a bit of trace poking out of the other side of the pad, which decreases clearances, looks untidy and generally gets in the way."
1795241,2018-09-30 17:56:49 UTC,The same issue applies to the graphical lines used in silk screen as well.
1795241,2018-09-30 19:55:03 UTC,"Disclaimer: I'm not a developer, just interested."
1795241,2018-10-01 08:58:06 UTC,....a lower bound on the sharpness of corners anyway.
1795241,2018-10-01 11:28:29 UTC,"At the moment its a legacy thing from when gerbers would be traced out by a light based system, the beam of light is round, and so the traces where round, the real way you can get around this for now is to neck down to a smaller trace or use zones,"
1795241,2018-10-01 11:58:29 UTC,"""At the moment its a legacy thing from when gerbers would be traced out by a light based system, the beam of light is round, and so the traces where round"""
1795241,2018-10-01 16:23:00 UTC,"Here you can find some screenshots showing why round edges are problematic, especially when connecting thick track to square pads:"
1795241,2018-10-02 18:18:34 UTC,Just make that request a variation of Teardrops.
1795241,2019-08-21 18:22:34 UTC,See also: https://bugs.launchpad.net/kicad/+bug/1833688.
1795242,2018-10-09 08:57:26 UTC,"@seth-arnold more and more intermediate certificates are also included in Chrome/Firefox, because a lot of website admins forget to include them in their .pem file of their domain certificate.  To prevent showing an ugly error message, browsers are integrate all the intermediates too. thats what i saw the last year."
1795242,2018-10-03 18:43:56 UTC,"On Wed, Oct 03, 2018 at 05:55:59AM -0000, Stan Janssen wrote:

> (I wonder why DigiCert has not been able to convice Mozilla to include
> this certificate, yet they still sign certificates that are intended for
"
1795242,2018-10-02 23:16:00 UTC,Aha! https://s.marktplaats.com/ indeed gives different results on Qualys:
1795242,2018-10-03 05:55:59 UTC,"I have reported this to Marktplaats.nl, suggesting they include the certificate in the chain that is being sent out by the server."
1795242,2018-10-02 20:21:10 UTC,"Thanks, Seth, for looking into this. You're right; that certificate is
indeed installed by default."
1795242,2018-10-01 23:20:14 UTC,This certificate does appear to be installed by default in the ca-certificates package:
1795242,2018-10-02 20:32:37 UTC,"This is on ElementaryOS 0.4.1, which is based on Ubuntu 16.04:"
1795248,2018-09-30 18:47:58 UTC,"You hit the nail on the head: at this point there is no clear, clean pathway to upgrade. It will likely be something that comes in the form of documentation, though."
1795248,2018-10-01 16:40:03 UTC,Didn't even notice the duplicate power icon!
1795248,2018-10-01 19:29:06 UTC,I have put this in the outline for the Lubuntu manual and will mark as in progress once I start writing it.
1795249,2018-10-14 18:25:49 UTC,"1. Samsung monitor problem overcome by Software & Updates -> additional drivers tab -> check NVIDIA driver instead of open source driver.
2. NVIDIA driver also corrects the permanent blobs problem noted above so ""quiet splash"" can be put back into the grub file.
3. Note also ""acpi=off"" stops the computer powering off when shutting down (manually use the front panel button when all activity has stopped) but this is a small price to pay for allowing the computer to boot up!"
1795249,2018-10-30 19:54:39 UTC,It looks like the necessity for acpi=off in my grub file has now been removed presumably by a recent update. My computer now boots up and powers off on shutdown correctly. I am happy now. (I even got my scanner working again!)
1795250,2018-11-16 02:03:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795252,2018-10-08 16:21:38 UTC,"The lack of multicore processing is dependent on `locale-gen`. See here for more info and a potential fix:
https://bugs.gentoo.org/show_bug.cgi?id=592300"
1795259,2018-10-01 23:27:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1795260,2018-10-27 22:41:43 UTC,"Not sure exactly when Variety started doing it, probably last update....but now it's displaying bigger than the screen i.e. it cuts off about 20% ish from top and bottom....can't see any relevant settings to tinker with?"
1795260,2018-11-05 17:39:36 UTC,"my bad!!! 'twasn't variety at all....seems setting under dekstop had changed itself to zoom, somehow.....that was really doing my nut! :-("
1795267,2018-10-01 13:14:25 UTC,"A nice addition would be to highlight the matching songs we you go to one of the highlighted playlists/crates. Any previous search query in that playlist would have to be reset then. Or that ""fuzzy"" match string automatically becomes the search query for that playlist so that you'll see only the matching tracks"
1795274,2018-10-01 23:30:30 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1795276,2018-10-07 08:35:06 UTC,"broke with commit
https://gitlab.com/inkscape/inkscape/commit/95b1c7b549"
1795276,2018-10-12 11:22:39 UTC,https://gitlab.com/inkscape/inkscape/merge_requests/352
1795278,2021-02-03 20:04:43 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1795278,2021-02-03 19:49:05 UTC,P.S. added Hirsute and Groovy tags since the latest dupe shows it affects Hirsute and thus should affect Groovy.
1795278,2021-02-03 19:48:11 UTC,"Michal, that's not how patching works, unfortunately. You can put all that in a file and use the `patch` command. The easy way is to go to the folder containing the file and run `sudo patch < /path/to/diff`."
1795278,2020-03-08 05:54:31 UTC,"# diff --git a/softwareproperties/qt/SoftwarePropertiesQt.py b/softwareproperties/qt/SoftwarePropertiesQt.p
diff: unrecognized option '--git'
diff: Try 'diff --help' for more information."
1795278,2020-03-04 16:32:16 UTC,"According to the dupe, this affects more recent versions, too. And not just Kubuntu."
1795278,2020-03-04 17:06:00 UTC,"There are no PyKDE imports anymore, only PyQt. That said, replacing `KUrl.fromPath` with just `QUrl` should resolve that."
1795278,2018-12-07 10:54:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795278,2018-09-30 21:01:00 UTC,This came from this Ask Ubuntu post:
1795278,2020-03-05 01:29:33 UTC,this should be the diff to be tested:
1795280,2018-10-01 18:27:24 UTC,"Hi!  I don't have a system with that kernel version handy at the moment, so I cannot confirm that I see the issue as well.  But I am looking for a subject matter expert at Red Hat."
1795280,2018-10-02 07:26:27 UTC,"Thanks for your replies. I'm not running Neutron in a container.
I tried to see if I could execute the netns deletion using neutron-rootwrap (we are using the rootwrap-daemon) but I don't remember if it worked."
1795280,2018-10-01 18:11:15 UTC,"It does look related to the pyroute2 bug linked in #1, I'll follow that as well to see if there is a fix released soon.  I haven't seen the failure locally, but don't think I'm running with this kernel version either."
1795280,2018-10-01 09:44:25 UTC,"[root@controller ~]# rpm -qa | grep pyroute2
python2-pyroute2-0.4.21-1.el7.noarch"
1795280,2018-10-01 09:49:27 UTC,should note that running `ip netns delete <namespace>` using the root user or with pyroute2 script running as root the namespace can be deleted.
1795280,2018-10-01 09:43:37 UTC,possibly https://github.com/svinota/pyroute2/issues/535
1795282,2018-10-13 10:28:38 UTC,cron /etc/cron.daily/couriergrey is also broken:
1795292,2019-05-21 22:55:05 UTC,same Ideapad 330s amd ryzen2500u.
1795292,2019-04-28 21:28:18 UTC,"I have an Ideapad 330s 15ARR and can confirm this bug in Ubuntu 19.04. The parameter ivrs_ioapic[32]=00:14.0 fix the problem. If any help is needed to investigate and test this, I'm glad to do so."
1795292,2019-03-29 15:14:14 UTC,"I just updated the BIOS to the latest 7VCN46WW (Jan 2019).
Tried to boot without the `ivrs_ioapic[32]=00:14.0` kernel parameter, and the stock 4.18.0-16-generic kernel just wouldn't boot at all.
Added the parameter back and it works."
1795292,2019-03-29 08:04:01 UTC,"Hey everyone. I was directed here from askubuntu. Having the same issue. No wifi or touchpad. Although I updated to the latest BIOS through windows before making the switch to ubuntu. Before looking around, I was able to update to kernel v5.0.4-50004 (using ethernet to usb converter). and still no touchpad or wifi. Have there been any updates reguarding getting at least the touchpad working without having to compile the kernel?"
1795292,2019-03-07 07:13:07 UTC,"Is parameter ""ivrs_ioapic="" still needed?"
1795292,2019-01-09 15:23:25 UTC,"Dont have anything much to add, but just wanted to mention:"
1795292,2018-11-10 19:31:03 UTC,:)
1795292,2018-11-11 02:11:00 UTC,Glad to hear :) Feels nice to be able to use this at 100% capacity. Can use this as my main OS now!
1795292,2018-11-11 01:06:46 UTC,"Yes, that works for me too!  Thanks Kenji!  Stock 4.18.0-10 kernel with `noapic` removed and `ivrs_ioapic[32]=00:14.0` added to the kernel command line makes the touch pad work.  It seems the `i2c_designware` timeout error has disappeared from dmesg."
1795292,2018-11-10 21:22:50 UTC,"Happy to confirm that I am typing this from the laptop running a fresh Ubuntu 18.10 installation. The only snag I had was after the installer completes, it doesn't want to pop up the grub menu (goes straight into booting Ubuntu), which would prompt a crash due to the grub cmd not being in place. You have to hit ESC right before the Lenovo boot logo disappears for this to pop up. After that you can edit the boot line to get booted up and edit /etc/default/grub."
1795292,2018-11-10 19:59:49 UTC,"My USB install stick had 18.04 on it, can confirm editing the installer line enabled keyboard/touchpad no issues in the installer; however, I am shooting for 18.10 for this laptop. Just adding the confirm here that it works for 18.04 kernel as well. Will update shortly on 18.10 fresh install."
1795292,2018-11-10 19:50:37 UTC,"Okay, just went back over some things to confirm in case anyone else is encountering this issue. First, here's my setup:"
1795292,2019-06-15 16:02:09 UTC,"I don't have words to convey my thanks to this forum (specially Kenji (dude2k5) ). I have Lenovo 330s 15ARR Laptop. Until read this forum I used NOAPIC parameter to start Ubuntu. Otherwise it is stuck on black screen. Even though  I was able to start Ubuntu, touch pad doesn't work (not identified by Ubuntu), Suspend(sleep) option does not work (led light doesn't flash, screen goes black, no response after that, only thing has to do - force shut down ) and keyboard doesn't work time to time on each boot. Finally, everything started to worked correctly after substituting NOAPIC by ivrs_ioapic[32]=00:14.0."
1795292,2018-12-01 12:15:37 UTC,"Hi all)
Thanks for the good work, but same problem here. The model is ideapad 330-15arr (the same ryzen but without the S prefix)"
1795292,2019-08-07 05:48:21 UTC,"Please test this kernel without ""ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2"":
https://people.canonical.com/~khfeng/lp1795292/"
1795292,2019-08-08 10:20:57 UTC,https://lkml.org/lkml/2019/8/8/286
1795292,2019-08-10 16:10:39 UTC,"Hi Kai-Heng Feng,"
1795292,2019-08-13 04:39:28 UTC,"Sorry because I mistakenly used ""ivrs_ioapic[4]=00:14.0"" in my patch. I've updated it as ""ivrs_ioapic[32]=00:14.0"" in my patch sent to upstream:"
1795292,2019-08-13 21:20:20 UTC,"Ah I see, I can test again once it's updated. Will the new updated files be in here (same place as last time)? Im guessing it hasn't been updated yet since it's still shows Aug 7 as the last modified date?"
1795292,2019-08-16 13:11:18 UTC,"I've uploaded new kernel to the same address, please give it a try."
1795292,2019-08-16 21:33:10 UTC,Success! I am typing from kernel 5.3.0-6 without the ivrs_ioapic edit in grub. That did it.
1795292,2019-08-17 07:20:09 UTC,https://lkml.org/lkml/2019/8/17/26
1795292,2019-08-26 19:07:21 UTC,"Per https://bugs.freedesktop.org/show_bug.cgi?id=111122#c25 it seems that Lenovo released a BIOS update (1.54 / R0UET74W) to fix IVRS tables on E485. As the Ideapad 330S-14ARR and 530S-14ARR use the same mobo, I guess it is also fixed there (or going to be fixed soon)."
1795292,2019-10-22 15:02:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1795292,2019-10-24 16:02:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1795292,2019-11-06 21:15:21 UTC,"From the bug history, this looks like an old bug that was fixed in Ubuntu (Bionic or cosmic?) a while ago, then upstreamed to linux-stable, then brought back to disco and eoan."
1795292,2019-11-12 20:04:58 UTC,"All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1795292,2019-11-12 22:18:04 UTC,This bug was fixed in the package linux - 5.3.0-22.24
1795292,2019-07-30 12:40:47 UTC,"Thanks to the whole community, but especially to Kenji. I had been trying to resolve the conflicts my laptop gave me for days. I have an Ideapad 330s-15ARR and I can say that replacing ""noapic"" with ""ivrs_ioapic [32] = 00: 14.0"" solves the touchpad problem (at least in my case it was the last thing to fix).
I will try later to try this type of solution in other distro linux, soon I will be giving a return of the tests. regards"
1795292,2018-11-10 19:29:19 UTC,"Hi Kenji,"
1795292,2018-10-26 04:08:05 UTC,"I have an oscilloscope, so I might be able to find out.  A 133MHz clock though?  That seems awfully high for a touch pad.  Where's the reference you found?"
1795292,2018-11-10 19:06:16 UTC,"Hi Kenji,"
1795292,2018-10-16 02:27:34 UTC,Here's the full output of acpidump.
1795292,2018-10-16 07:24:37 UTC,"Please also try the latest BIOS for your laptop, those settings are provided by BIOS."
1795292,2018-10-18 04:44:09 UTC,"Latest BIOS makes no difference, behavior is the same."
1795292,2018-10-23 04:33:21 UTC,All that seems to happen here is that you make me try new BIOSes and kernels as they come out.  Disappointing.
1795292,2018-10-23 05:13:55 UTC,That's pretty much all you can do unless you're capable of writing drivers or reading ACPI tables yourself.
1795292,2018-10-24 04:34:17 UTC,If I could do that I'd fix my problem myself.  I thought reporting a bug was so people who know how to do these things could take a crack at it.  But it seems there's no one at Canonical who knows about these things either.
1795292,2018-10-24 04:47:45 UTC,Someone's probably working on it. I personally am. But have nothing to show yet. Most likely the same with whoever else is working on it currently
1795292,2018-10-25 08:51:08 UTC,"Please boot with kernel parameter ""i2c_designware_core.dyndbg=+p"" and attach dmesg."
1795292,2018-10-25 14:45:57 UTC,Here you go.  I did it on kernel 4.19 since you were going to ask me to do that next.
1795292,2018-10-25 15:53:30 UTC,"Does anyone have the technical sheet on this touchpad?
I've seen reference to it's clock being 133mhz, but can't confirm it as I don't own an oscilloscope."
1795292,2020-04-07 09:28:39 UTC,"Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
Kernel Version: 5.4.0-21-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.4 GiB of RAM"
1795292,2018-10-28 02:00:49 UTC,"I would like to add that I am encountering the same issue with ELAN469D. Tried with kernel v4.19 with no changes, not seeing it in dmesg. Please let me know if there is any way I can assist with testing."
1795292,2018-10-29 08:16:55 UTC,"The SDA hold time on your system is 72, but it's is 48 on a working RR system I tested."
1795292,2018-10-30 00:01:23 UTC,"Hi kaihengfeng,"
1795292,2018-10-30 04:16:45 UTC,"Tried the 4.19.0-4 you provided Kai-Heng, still doesn't work.  dmesg output attached."
1795292,2018-10-31 02:01:07 UTC,"Unlike FF8Jake, I do have touchpad references in the output.
Is this the same laptop FF8Jake?  Or what model laptop do you have?"
1795292,2018-10-31 02:30:09 UTC,"Hi Patrick,"
1795292,2018-11-02 03:15:36 UTC,"Also on  v4.19.0, same touchpad and Laptop, Lenovo 330s-15ARR, I can test if anyone has a new build. I'd love to get this laptop working with Ubuntu :)"
1795292,2018-11-03 11:09:12 UTC,Please try this kernel out:
1795292,2018-11-03 20:46:30 UTC,"Hello,"
1795292,2018-11-05 03:10:27 UTC,Hmm I am out of any idea. Would it be possible to ask support from Lenovo?
1795292,2018-11-07 04:35:54 UTC,"I tried the 4.15.0-39 kernel.  It still doesn't work but there's a difference in the dmesg output, which I attached.  This message is new / different:"
1795292,2018-11-07 14:11:58 UTC,"Look at what this guy did:
https://forums.lenovo.com/t5/Lenovo-IdeaPad-1xx-3xx-5xx-7xx/Lenovo-Ideapad-330-15ARR-ryzen-5-bios-doesn-t-support-linux/m-p/4251437/highlight/true#M61640"
1795292,2018-11-08 14:46:45 UTC,"Hi Kenji,"
1795292,2018-11-08 16:23:07 UTC,"Indeed I tried as well, did not work either. I may make an account and ask the user which kernel version they used. Also seeing they keyboard issue, very strange. And my wifi says ""disabled by button/airplane mode on"" but there is no button the laptop, and my BIOS has wifi ""enabled"", so not sure why that doesn't work either."
1795292,2018-11-08 16:42:36 UTC,"So far, my wifi has worked consistently, but maybe I am just lucky. Considering the random nature of the keyboard, it makes me wonder if some of us seeing ELAN in dmesg and some not is also pure luck of the draw on that bootup as well."
1795292,2018-11-08 20:45:05 UTC,"Figured out my wifi issue. Can't get it working with Linux Mint, not sure why. Ubuntu works fine. I had to disable some options in my bios to get wifi (AMD security off, boot mode legacy support, boot priorty legacy first and OS optimized defaults enabled). Once I had those set, I was able to go to the grub setup and do ""nomodeset"" and ""noapic"" which makes it install and work with wifi. I tried the same options in Linux Mint but it would not get past the initial boot/setup/grub, kept getting kernel panics or ACIP errors. I can with ""apci=off"" but then wifi will not enable and show it ""disabled by hardware"", and no FN keys re-enable it. So I'll stick to Ubuntu for now, since wifi works at least. Still no idea on the touchpad, I tried a few kernels (4.17, 4.18, 4.19), tried to email someone from ELAN but got nothing so far :/"
1795292,2018-11-10 18:10:50 UTC,Can you guys check your BIOS version? I think that might be part of an issue. Im on 7WCN27WW
1795292,2018-11-10 18:58:28 UTC,SUCCESS!!!
1795292,2018-11-10 19:14:34 UTC,"Hm, yea that sounds almost hardware at this point. I had issues initially but they cleared up (and even my FN keys work now, idk how). I think I almost have everything working at this point, on the newest BIOS, on ubuntu 18.04 and custom 4.19."
1795292,2018-10-13 00:53:25 UTC,"https://bugzilla.kernel.org/show_bug.cgi?id=201393
--
Cristian Aravena Romero (caravena)"
1795292,2018-10-15 03:43:56 UTC,Can you provide acpidump? Maybe the frequency provided by ACPI was wrong.
1795292,2018-10-11 01:18:56 UTC,@nikola is this the same laptop?  Here are the same pieces of data from my Lenovo Ideapad 330S-15ARR:
1795292,2018-10-11 05:36:40 UTC,"Kernel 4.19.0-rc7
Laptop is a Lenovo IdeaPad 330S-15ARR. Same issue as everyone else."
1795292,2018-10-09 20:05:57 UTC,"Same here, touchpad not working in Ubuntu 18.04... on every kernel i tried"
1795292,2018-10-08 05:03:15 UTC,"Upstream kernel 4.19.0-rc7 doesn't help either.
Anyone working on this?"
1795292,2018-10-04 17:47:10 UTC,"Not sure if this will be helpful, but I attached the output log of ""fwts""."
1795292,2018-10-04 16:21:58 UTC,"I updated the BIOS.  This allowed me to remove the ""pcie_aspm=off"" and ""pci=noaer"" kernel parameters.  The others are still necessary though.  Removing ""noapic"" makes the system hang on boot (after the initial RAM disk message I think, so I don't know how to get any data on what that's all about)."
1795292,2018-10-13 00:31:08 UTC,"acpidump:
    5B10: 39 5F 48 49 44 00 A0 13 93 54 43 50 44 0A 02 A4  9_HID....TCPD...
    5B20: 0D 53 59 4E 41 33 32 35 35 00 A0 13 93 54 43 50  .SYNA3255....TCP
    5B30: 44 0A 03 A4 0D 41 4C 50 53 31 32 31 45 00 A4 0D  D....ALPS121E...
    5B40: 45 4C 41 4E 34 36 39 44 00 08 45 49 43 30 11 21  ELAN469D..EIC0.!
    5B50: 0A 1E 8E 19 00 01 00 01 02 00 00 01 06 00 80 1A  ................
    5B60: 06 00 15 00 5C 5F 53 42 2E 49 32 43 44 00 79 00  ....\_SB.I2CD.y.
    5B70: 08 53 49 43 30 11 21 0A 1E 8E 19 00 01 00 01 02  .SIC0.!........."
1795292,2018-10-04 13:41:40 UTC,"Does removing `noapic` help? Also I found that there's new BIOS version for the laptop, please try it."
1795292,2018-10-03 14:42:14 UTC,apport information
1795292,2018-10-03 14:40:22 UTC,Still doesn't work with this kernel.  Did you make any changes to the i2c_designware?  This error still exists and I wonder if it's related since this is a I2C touchpad.
1795292,2018-10-03 05:02:36 UTC,"Hi Patrick, I have made some changes to the Elan driver and compiled a new kernel. Can you try the kernel in https://people.canonical.com/~ypwong/lp1795292/ and see if your touchpad works? If not, please post dmesg. Thanks."
1795292,2018-10-02 16:43:51 UTC,"This has not worked with any kernel I've tried, from 4.15 to 4.18 to the upstream 4.19 you linked to."
1795292,2018-10-02 14:43:18 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1795292,2018-10-01 05:30:05 UTC,This change was made by a bot.
1795292,2018-10-03 14:47:52 UTC,Well that didn't work.  apport-collect complains I am running a mainline kernel and should report it upstream.  So here's just the output of dmesg.
1795292,2018-10-13 00:52:18 UTC,"Hello,"
1795296,2018-10-01 06:32:20 UTC,"Seems my guess about rp_filter is wrong, setting it to 0 has no effect, for whatever reason the outbound traffic does not transmit. So removing that from the description."
1795296,2018-11-20 13:29:09 UTC,"On Mon, 2018-10-01 at 06:12 +0000, Trent Lloyd wrote:

> I would argue in some ways this is a bug in juju, as other things may
> rely on interfaces.d and it probably should rewrite 50-cloud-init.cfg
> or otherwise not remove the interfaces.d include (or it could leave
> the include there but remove the 50-cloud-init.cfg)
"
1795296,2018-12-11 08:30:24 UTC,"Though it is not material to the bug itself, Jay was able to determine *why* the traffic fails when both the interface and the bridge has the same IP address. I originally incorrectly suspected this was related to rp_filter."
1795296,2018-12-11 08:35:47 UTC,Additionally on juju 2.3.8 at least I suspect the interface file updates are racing between juju (setting up multiple container bridges over time) and the charm updating the file. juju 2.4 may be better but I did not conclusively test that.
1795305,2018-10-10 20:05:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795307,2018-10-01 23:47:06 UTC,"Hello, it looks like your torque-scheduler isn't happy. I hope this helps you address your issue."
1795307,2018-10-01 23:46:48 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1795309,2018-11-25 23:06:46 UTC,I think the original bug description is unclear because only the bug title explain the most important thing. I will update the bug description.
1795309,2018-11-25 23:09:13 UTC,"When a server group quota exceeds Nova API returns 403.
I guess 403 is not handled properly."
1795309,2019-12-03 19:44:48 UTC,It is already fixed in https://review.opendev.org/#/c/677580/.
1795309,2018-10-15 07:50:49 UTC,I found simmilar bug report from octavia-dashboard that user will be logout from horizon if create new entity which is met quota.
1795309,2018-10-03 13:18:44 UTC,ByungYeol could you please provide horizon and keystone logs?
1795309,2018-10-05 09:12:13 UTC,"------------
number of instances => number of server groups
------------"
1795310,2018-10-01 14:04:33 UTC,"Sounds good :)
The plan is to transition Ubuntu to 8.0 for 19.04, so hopefully this will propagate down before then."
1795310,2018-10-01 13:20:31 UTC,Fixes committed in v3.0.x:
1795314,2020-02-13 16:34:37 UTC,This bug was fixed in the package isc-kea - 1.6.1-0ubuntu1
1795314,2020-02-10 18:53:18 UTC,"This was fixed upstream, but the fix clashes with Ubuntu's reintroduction of my_bool as a bool."
1795321,2020-02-17 18:18:50 UTC,This was fixed in 0.9.0-6ubuntu2
1795327,2020-09-23 23:30:04 UTC,"Removed in lighttpd 1.4.52, released Nov 2018"
1795328,2021-02-05 02:45:29 UTC,This was addressed/fixed in 0.7.2-1ubuntu1.
1795329,2019-08-15 08:14:09 UTC,"FYI filing a removal request, will link the bug here or actually since it is meant to resolve the transition I'll make this a dup then."
1795330,2018-10-01 09:22:31 UTC,"Found a FIX for this issue here:
https://askubuntu.com/questions/976187/dpkg-error-message-with-libsane-while-installing-winehq-stable"
1795336,2018-10-01 11:41:32 UTC,"Hm, but I see it's referenced as causing a build failure with MariaDB without also checking the MariaDB flag, so maybe there are issues with the older versions (I tested briefly with 5.7)"
1795336,2018-10-01 11:04:54 UTC,"Actually, it should be backwards compatible.
In 5.x, my_bool is typedef'ed to char, but functions using it will still happily accept int or bool (and most of the code I see in Ubuntu assigns it as one of those)."
1795336,2018-10-01 09:50:04 UTC,As discovered upstream this is not entirely backwards compatible with older MySQL or current MariaDB. https://github.com/PowerDNS/pdns/pull/6842 fixed this upstream.
1795338,2018-11-21 15:55:33 UTC,Dupe of https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1786710?
1795342,2019-06-04 04:17:38 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1795342,2019-06-04 04:17:37 UTC,[Expired for The Ubuntu Power Consumption Project because there has been no activity for 60 days.]
1795342,2019-01-18 01:31:46 UTC,Cool. What are the approximate power usage numbers you see in watts?
1795342,2019-01-18 18:26:00 UTC,gjs version is 1.54.3.
1795342,2019-01-18 07:46:39 UTC,"Also, can you please confirm what version of package 'gjs' you have installed?"
1795342,2019-01-11 02:00:36 UTC,Some notable CPU users from that file:
1795342,2019-01-10 16:52:43 UTC,"Ok. here's another file. Left the laptop idle for few hours, still high power usage."
1795342,2019-01-21 01:56:53 UTC,What are the approximate power usage numbers you see in watts? (Gnome Shell vs Unity)
1795342,2018-10-01 14:08:39 UTC,"Out of interest, do you have an Nvidia Prime setup?"
1795342,2018-12-04 05:32:57 UTC,"Thanks, that's a nice report."
1795342,2018-12-04 05:37:24 UTC,Please also try shrinking the Firefox window so that it is not touching the screen edges (not touching the Gnome panel and Ubuntu dock). Does that improve things?
1795342,2018-12-04 12:47:55 UTC,"1. Closed firefox and left the laptop idle for an hour and the battery is almost fast drained again.
2. removeaccesibity extension is important for me because I have a HiDpi display and normally the screen looks tiny and enabling Universal access helps and at the same time I don't like the icon present always there, makes me feel sick, sorry about that!"
1795342,2018-12-05 01:52:40 UTC,"It looks like you're also running skypeforlinux, slack and more. Please try with all apps closed (just log out and log in again). Is the power usage still high with zero apps?"
1795342,2018-12-08 04:15:53 UTC,Thanks and I tested it many times. Kept the system idle with zero apps running and the power usage was still high.
1795342,2018-12-10 02:07:46 UTC,OK. Next we need to figure out what system component is to blame.
1795342,2018-12-10 11:52:00 UTC,"Thank you.
Attached is the output of top -d60"
1795342,2018-12-10 12:05:18 UTC,"Please ignore the previous one, I took that screenshot sooner. Consider this one."
1795342,2019-01-17 18:00:16 UTC,"I installed a new kernel 4.20 on Gnome-shell and the power consumption was almost same/high.
Then, I removed the kernel and switched back to 4.18 that comes with 18.10 base and installed unity-session and I noticed a sudden decrease in power consumption. I don't know, if the problem is Gnome-shell but this is what seems by switching to unity."
1795342,2018-12-14 17:42:59 UTC,"Disabled snapd service and left the laptop idle, almost same power usage."
1795342,2018-12-17 01:47:41 UTC,OK. There's one more thing to check before we can blame the kernel...
1795342,2019-01-06 16:45:22 UTC,"Hi, please confirm the attached output of `ps auxw`."
1795342,2019-01-07 03:44:51 UTC,Thanks. That only shows a few seconds of CPU usage. How long was the machine running when you collected that?
1795342,2019-01-07 17:58:34 UTC,"Please ignore the previous output file, took that too soon after system boot."
1795342,2019-01-08 01:53:56 UTC,Did you confirm the power usage is still too high before sending allprocs.txt?
1795342,2018-12-04 05:09:52 UTC,"Hey thanks,"
1795342,2018-10-01 09:28:28 UTC,Please run this command to send us more system info:
1795342,2018-12-11 02:21:27 UTC,"Thanks. Although gnome-shell, snapd and deja-dup-monitor are the top users for the previous 60 seconds, it also shows that snapd has used an accumulated 4m40s which is way above everything else."
1795342,2018-10-02 02:22:25 UTC,That question would be answered by attaching output from:
1795342,2018-12-04 02:05:54 UTC,Thanks. Please try installing 'powertop' and then run 'sudo powertop'. You may find a reason for the high power consumption there.
1795342,2018-12-03 18:11:28 UTC,apport information
1795342,2018-12-03 18:11:26 UTC,apport information
1795342,2018-12-03 18:11:24 UTC,apport information
1795342,2018-12-03 18:11:22 UTC,apport information
1795342,2018-12-03 05:07:59 UTC,This bug is now closed. If you would like to reopen it then please answer comment #1.
1795342,2018-12-03 04:17:42 UTC,[Expired for The Ubuntu Power Consumption Project because there has been no activity for 60 days.]
1795342,2018-12-03 04:17:41 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1795342,2018-10-04 02:19:00 UTC,Thanks. So it's Intel-only graphics:
1795342,2018-10-03 12:15:29 UTC,This is the hardware info:
1795343,2018-10-04 20:32:10 UTC,Tested 0.40.1 from -proposed; things look good here.
1795343,2018-10-04 18:26:39 UTC,"Hello EOLE, or anyone else affected,"
1795343,2018-10-01 15:39:16 UTC,I can reproduce the failure as well after upgrading to netplan.io in proposed and touching /etc/netplan/99-empty.yaml
1795343,2018-10-24 15:03:56 UTC,It's working fine with version 0.40.1~18.04.1.
1795343,2018-10-09 03:58:07 UTC,This bug was fixed in the package netplan.io - 0.40.2
1795343,2018-11-06 18:13:46 UTC,This bug was fixed in the package netplan.io - 0.40.1~18.04.2
1795343,2018-12-05 18:47:48 UTC,This bug was fixed in the package netplan.io - 0.40.1~18.04.3
1795343,2018-11-27 13:06:10 UTC,OK with 0.40.1~18.04.3
1795343,2018-11-26 19:25:59 UTC,"Hello EOLE, or anyone else affected,"
1795343,2018-11-06 18:15:24 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1795343,2018-10-23 22:02:01 UTC,"Hello EOLE, or anyone else affected,"
1795343,2018-10-09 14:54:50 UTC,Marking verification-done based on Ryan's verification.
1795345,2018-10-04 08:49:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/607849"
1795349,2018-10-02 02:43:27 UTC,"I think we should just get rid of this `--partial` option, since this can be achieved with `--format`."
1795358,2019-06-08 07:28:56 UTC,"Ubuntu 19.04 release has Qt 5.12, so marking this as fixed."
1795358,2018-10-02 13:43:18 UTC,"This has been fixed in https://code.qt.io/cgit/qt/qtbase.git/commit/?id=818ab021f5fbeedd, which will be part of Qt 5.12."
1795365,2021-01-08 03:41:47 UTC,Andreas Hasenack addressed this in 1.4.4-3ubuntu2.
1795365,2020-02-06 14:14:42 UTC,"I just tried this in an Ubuntu 19.10 in a VM and I've not been able to reproduce it. Looking at /usr/include/mysql/mysql.h, it seems at some point the my_bool transitions has been given more time:"
1795365,2020-01-23 16:22:06 UTC,"The attachment ""fix-mysql-bool.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1795365,2020-01-23 14:00:43 UTC,I will try to spin up a new Ubuntu machine to fix this at some point. In the mean time I have a mostly untested patch.
1795368,2018-10-01 11:40:34 UTC,"Please now and in the feature when reporting a problem please add the os version, video card, video drivers, kernel, what is the normal resolution and what resolution you get in this case and how to reproduce this problem."
1795368,2018-10-02 20:35:01 UTC,What if you open the monitor after you login ? What happens?
1795368,2018-10-01 22:31:56 UTC,"First of all, thank you for such a quick response!"
1795368,2018-10-01 22:37:51 UTC,About the way to reproduce the BUG. It happens when I start the system with the monitor turned OFF and only turn it ON almost at login screen. I could reproduce it twice on this computer.
1795368,2018-10-02 13:51:39 UTC,"Please can you test with both cases (turn on the monitor in the same time with the laptop and the second case turn on the monitor after the ""almost at login screen"" )
We need the find the precise way that the problem appears.
Thanks"
1795368,2018-10-02 15:00:26 UTC,"Sorry, I think I explained it wrong. Thank you for your patience, it is my first BUG report."
1795368,2018-10-02 15:19:34 UTC,What happens if you open first the monitor and then the laptop/pc?
1795368,2018-10-03 08:42:18 UTC,Remember the problem is at my desktop and not at my laptop.
1795368,2018-10-02 20:49:26 UTC,"In that situation, I had to turn the monitor ON before to put the pass. It is the same than the situation of ""just before/during login screen""."
1795368,2018-10-02 15:35:47 UTC,"That way, the BUG won't happen."
1795369,2018-10-01 10:52:46 UTC,Applying recent patches from http://lists.nongnu.org/archive/html/qemu-devel/2018-09/msg04038.html doesn't fix any of issues.
1795369,2020-11-12 07:12:11 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1795369,2021-01-12 04:17:16 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1795377,2018-10-01 21:38:02 UTC,Related to https://github.com/mixxxdj/mixxx/pull/1747 ?
1795377,2019-08-19 20:39:28 UTC,"I cannot confirm this using Mixxx 2.2.2 or Mixxx 2.3.0 alpha.
Can you still confirm? Maybe this was fixed in the meanwhile?"
1795377,2019-08-19 21:21:10 UTC,"This was confirmed for 2.2.2 as well here:
https://github.com/mixxxdj/mixxx/pull/1801#issuecomment-522758051"
1795377,2020-11-30 10:38:58 UTC,Fixed in 2.3
1795385,2018-10-01 12:37:01 UTC,"Application: pcbnew
Version: 5.0.1-dev-unknown-9837d16~66~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-34-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011"
1795385,2019-08-26 17:28:30 UTC,"Fixed in revision 67db6c49b5c0517a0cd191de7d62c0a75ce146cd
https://git.launchpad.net/kicad/patch/?id=67db6c49b5c0517a0cd191de7d62c0a75ce146cd"
1795385,2019-08-26 10:08:29 UTC,"This appears to have gotten fixed at some point, although I did notice that the button was missing the ""..."" so I fixed that."
1795395,2018-10-01 13:09:52 UTC,"StacktraceTop:
 ?? ()
 ply_keyboard_stop_watching_for_renderer_input (keyboard=0x561ce4852380) at ply-keyboard.c:406
 ply_keyboard_stop_watching_for_input (keyboard=keyboard@entry=0x561ce4852380) at ply-keyboard.c:406
 ply_device_manager_deactivate_keyboards (manager=0x561ce4843a60) at ply-device-manager.c:976
 on_quit (state=0x7fffe68b3630, retain_splash=<optimized out>, quit_trigger=0x561ce483f390) at main.c:1435"
1795395,2018-10-16 18:36:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1795396,2018-11-16 13:03:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795398,2018-10-04 11:57:03 UTC,"Git commit 3394a564ec62a40ed99c185324993205f9a72641 by Rik Mills.
Committed on 04/10/2018 at 11:56.
Pushed by rikmills into branch 'Applications/18.08'."
1795398,2018-02-17 09:31:39 UTC,"With PackageKit 1.0.x, this is not an acceptable version during configure, so features are disabled and lost."
1795398,2018-03-01 02:08:04 UTC,"Would you be able to propose a fix? openSUSE Tumbleweed still uses PackageKit-Qt 0.9.6, so I cannot investigate locally."
1795398,2018-10-01 14:28:51 UTC,"(In reply to Christoph Feck from comment #1)

> Would you be able to propose a fix? openSUSE Tumbleweed still uses
> PackageKit-Qt 0.9.6, so I cannot investigate locally.
"
1795398,2018-10-01 18:20:37 UTC,This bug was fixed in the package kdenetwork-filesharing - 4:18.04.3-0ubuntu2
1795398,2018-10-04 11:54:59 UTC,"Git commit 1895a88670e6bef79fa07fe13335373956eedf9c by Rik Mills.
Committed on 04/10/2018 at 11:54.
Pushed by rikmills into branch 'master'."
1795407,2019-04-29 11:28:00 UTC,"@sil2100 I think there is a regression in the other locking fixes, as reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 - but that said, we have that in every other release too, and I'll upload SRUs for that later."
1795407,2019-04-29 11:38:51 UTC,Tracking the regression in bug 1826870
1795407,2019-05-06 11:16:01 UTC,"Hello Julian, or anyone else affected,"
1795407,2019-05-09 09:08:07 UTC,This was for xenial 1.1.0~beta1ubuntu0.16.04.4
1795407,2019-05-16 10:22:34 UTC,This bug was fixed in the package python-apt - 1.1.0~beta1ubuntu0.16.04.4
1795407,2019-04-29 11:11:33 UTC,"@juliank is this upload still relevant and good for release? Last time it was 'blocked' on the unattended-upgrades SRU - and that one has landed in xenial-updates already. Can we release it now, or does it need a re-upload?"
1795407,2019-05-09 09:04:44 UTC,without SystemLock being held works fine:
1795407,2018-10-31 12:16:39 UTC,"We don't plan to. Trusty does not run unattended-upgrades by default, so there's no strong need for frontend locking in there."
1795407,2018-10-31 17:22:05 UTC,Got it. Thanks for the info.
1795407,2018-10-29 10:34:39 UTC,This bug was fixed in the package python-apt - 1.6.3
1795407,2018-10-29 10:24:25 UTC,"The verification of the Stable Release Update for python-apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1795407,2018-10-19 11:16:29 UTC,Same for xenial (1.1.0~beta1ubuntu0.16.04.3).
1795407,2018-10-19 11:10:16 UTC,"FTR, with the locking with statement, without the SRU, it fails, as expected (both in bionic and xenial), e.g.:"
1795407,2018-10-19 11:07:45 UTC,bionic 1.6.3:
1795407,2018-10-01 18:42:44 UTC,"Hello Julian, or anyone else affected,"
1795407,2018-10-01 17:52:29 UTC,"Hello Julian, or anyone else affected,"
1795407,2018-10-31 10:56:42 UTC,Hello! Is there any change this fix will be backported to ubuntu/trusty?
1795412,2018-10-06 21:04:55 UTC,"When subscribing the Ubuntu Sponsors Team, please attach a debdiff with a changelog entry that can be sponsored."
1795412,2018-10-01 14:28:39 UTC,telepathy-haze-fix.patch
1795416,2018-10-04 14:21:12 UTC,https://github.com/snapcore/snapcraft/pull/2316
1795416,2018-10-02 08:42:34 UTC,"Different error message, but seems related."
1795416,2018-10-01 15:56:39 UTC,This seems to be a problem with the /dev/api/snaps/(snap_id)/metadata endpoint.
1795416,2018-10-01 15:28:10 UTC,"Thank you for taking the time to report this bug and helping to make snapcraft better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1795416,2018-10-01 16:04:19 UTC,Luke's reproducer is in Sentry as SNAPCRAFT-DASHBOARD-ZN
1795420,2019-06-06 01:46:40 UTC,Aforementioned patch was included in 2018-04-09 Release 1.4.3
1795420,2018-10-02 12:45:15 UTC,"Thanks for filing this bug in Ubuntu, and providing a link to a patch. This will need some backporting, but it's an excellent start."
1795420,2019-04-01 13:29:02 UTC,"This wan't touched for quite a while :_/
I realized it missed a tag to get in the common list that is re-iterated - it didn't seem we wait on something right Andreas?"
1795420,2019-06-04 12:29:10 UTC,Still in the queue.
1795420,2019-12-04 19:30:27 UTC,"Cosmic is out of service, so canceling that task.  The bug is otherwise still valid for sru for xenial/bionic if/when someone has time to package it and finish the SRU form.  Meanwhile, if anyone is interested in helping push this issue towards a fix, the SRU process is documented at https://wiki.ubuntu.com/StableReleaseUpdates."
1795421,2019-10-03 06:05:25 UTC,Is this still a problem? This seems to have been reported against only cosmic so far.
1795421,2019-12-03 04:17:18 UTC,[Expired for yaru-theme (Ubuntu) because there has been no activity for 60 days.]
1795421,2019-03-01 01:59:34 UTC,Fixed for scale 1.0 maybe. I don't think it is fixed for 2.0.
1795421,2019-12-03 04:17:21 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1795421,2018-10-02 14:03:26 UTC,"This is being marked as notfixing for Cosmic.  It's a nice to have, but not a release blocker."
1795421,2018-10-02 08:06:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795421,2019-02-28 10:48:34 UTC,Was fixed https://launchpad.net/ubuntu/+source/gnome-control-center/1:3.30.2-4ubuntu2
1795430,2018-10-01 15:28:11 UTC,"you want ""gcc-arm-linux-gnueabihf:amd64"" here"
1795433,2018-10-02 19:24:19 UTC,Old upstream report:
1795433,2018-10-02 19:20:38 UTC,https://git.launchpad.net/xubuntu-default-settings/commit/etc/xdg/xdg-xubuntu/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml?id=ae651957905725b57cc7de5c1daf35c6ca5a5ac8
1795433,2018-10-02 19:21:47 UTC,Did you install xubuntu-desktop or xubuntu-default-settings?
1795453,2018-10-22 16:03:16 UTC,I see the disks going offline during stress in mainline 4.19.0-041900rc7-generic as well.
1795453,2018-10-22 15:57:50 UTC,"With the 4.18.0-8-generic kernel, I see AMD IOMMU IO_PAGE_FAULTs for invalid addresses
AMD-Vi: Event logged [IO_PAGE_FAULT device=e1:00.0 domain=0x0000 address=0xfffffffffffd14c0 flags=0x0030]"
1795453,2018-10-22 15:56:05 UTC,"With latest 4.15 LTS kernels, I see the vdbench process crash and the PERC controller and the related disks go offline.."
1795453,2018-10-16 12:05:23 UTC,Yes below 4.18 kernel (which is 4.15) fixes only with increased memory
1795453,2018-10-16 03:00:24 UTC,"@sasikumarpc - Ok. So when you say below v4.18 kernel fixes it, does it mean with increased memory or is it with the same setup where the issue was originally seen?"
1795453,2018-10-15 18:35:58 UTC,"> Also another version (other than default version of Ubuntu 18.04.01) of 4.15 kernel fixes the issue
"
1795453,2018-10-15 17:28:59 UTC,apport information
1795453,2018-10-15 17:29:01 UTC,apport information
1795453,2018-10-22 16:41:02 UTC,"Yes , It seems that bug is still not fixed"
1795453,2018-10-15 17:28:58 UTC,apport information
1795453,2018-10-15 17:28:56 UTC,apport information
1795453,2018-10-15 17:28:55 UTC,apport information
1795453,2018-10-15 17:28:53 UTC,apport information
1795453,2018-10-15 17:28:51 UTC,apport information
1795453,2018-10-15 17:29:03 UTC,apport information
1795453,2018-10-29 11:08:15 UTC,"@sasikumarpc -
We observed this scenario where the PERC goes offline:
sgl_ptr->Address = fffffffffffff000
sgl_ptr->Length = 1000"
1795453,2018-11-05 15:45:26 UTC,63 bit masking will cause double buffering of data ?
1795453,2018-11-02 05:47:56 UTC,"The 63bit dma_mask was just a test to understand the adress-wraparound by the fw. Nothing specific.
PERC didn't go offline. Always ended up with OOM btw."
1795453,2019-03-06 10:49:37 UTC,This bug was fixed in the package linux - 4.18.0-16.17
1795453,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1795453,2019-03-01 05:02:03 UTC,This is the final reminder to please verify that the kernel in -proposed resolves the issue for which you've filed this bug report.   Canonical is planning to release these kernels early next week.   Thank you in advance!
1795453,2019-02-13 08:53:44 UTC,"Hi,"
1795453,2019-02-11 16:51:59 UTC,"How long does it take for content to show up in proposed?
As of today it does not appear to be available yet."
1795453,2019-02-11 11:06:18 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1795453,2019-02-08 15:47:17 UTC,This landed in the 4.15 kernel so it should picked up in 16.04.5
1795453,2019-02-08 07:03:15 UTC,"Can we also get the above fixes in Xenial HWE kernels?
I suppose Xenial HWE kernel is a fork of bionic LTS kernels.."
1795453,2018-10-15 17:28:50 UTC,apport information
1795453,2019-01-30 17:45:59 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-January/098154.html
1795453,2019-01-28 14:54:04 UTC,"Testing Status Update:
4.18 kernel has run for 72+ hours without failure."
1795453,2019-01-22 18:47:30 UTC,"Testing Status Update:
Testing ongoing since last week.
4.15 kernel ran for 72 hours without failure.
Will update tomorrow on status of the 4.18 kernel (so far 24+ hours without failure)."
1795453,2019-01-17 20:11:24 UTC,I built test kernels for bionic and cosmic with the fix applied. Please can you test it and check if the problem is solved?
1795453,2019-01-09 22:06:03 UTC,How to Recreate
1795453,2018-12-20 05:18:28 UTC,"Broadcom submitted the fix upstream:
https://marc.info/?l=linux-scsi&m=154514161019901&w=2
https://marc.info/?l=linux-scsi&m=154514161319908&w=2
https://marc.info/?l=linux-scsi&m=154514161619911&w=2"
1795453,2018-10-31 21:08:44 UTC,Just would like to understand more about the system behavior when we change the DMA Mask from 64 bit to 63 bit
1795453,2018-10-15 17:28:48 UTC,apport information
1795453,2018-10-11 14:31:52 UTC,we are in the process of collecting logs
1795453,2018-10-15 17:27:35 UTC,apport information
1795453,2018-10-15 17:25:41 UTC,"> Also another version (other than default version of Ubuntu 18.04.01) of 4.15 kernel fixes the issue
"
1795453,2018-10-15 17:10:15 UTC,"Issue reported Kernel Version
-----------------------------"
1795453,2018-10-15 15:35:01 UTC,"sasikumarpc -
Can you share the specific kernel versions that you are using, where the issue is fixed?
Can you also share the logs of pass & failure cases?"
1795453,2018-10-12 20:25:06 UTC,It will be good if you could provide us the exact commit (Patch) which fixes the issue
1795453,2018-10-12 15:24:00 UTC,Also another version (other than default version of Ubuntu 18.04.01) of 4.15 kernel fixes the issue
1795453,2018-10-12 15:07:56 UTC,"Could you also test the latest upstream 4.15 stable kernel?  It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/"
1795453,2018-10-12 14:07:58 UTC,"Looks like the issue is not seen with 4.18 kernel , please let me know still Ubuntu requires the log with 4.15 kernel ?"
1795453,2018-10-10 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1795453,2018-10-10 14:36:32 UTC,moving to kernel itself rather than the hwe package
1795453,2018-10-10 14:36:09 UTC,Can any of you recreate this using the mainline kernel?
1795453,2018-10-05 19:59:27 UTC,"No, we own only the mega raid Linux driver , you may have to reach out to AMD iommu driver team"
1795453,2018-10-05 19:07:46 UTC,@mreed8855 This issue may be related to the amd_iommu driver. There are patches upstream that are not in the 4.15 kernel. How can we get a list of those patches. Is there an amd_iommu expert out there?
1795453,2018-10-04 19:19:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795453,2018-10-03 18:02:43 UTC,uname -r:
1795453,2018-10-03 16:26:34 UTC,"Can you provide more information, such as the driver version, uname -a, logs, and how to recreate the issue?"
1795453,2018-10-15 17:28:46 UTC,apport information
1795453,2018-10-15 17:26:46 UTC,apport information
1795453,2018-10-15 17:26:45 UTC,apport information
1795453,2018-10-15 17:26:49 UTC,apport information
1795453,2018-10-15 17:27:33 UTC,apport information
1795453,2018-10-15 17:27:31 UTC,apport information
1795453,2018-10-15 17:27:29 UTC,apport information
1795453,2018-10-15 17:27:28 UTC,apport information
1795453,2018-10-15 17:27:27 UTC,apport information
1795453,2018-10-15 17:26:48 UTC,apport information
1795453,2018-10-15 17:27:25 UTC,apport information
1795453,2018-10-15 17:27:26 UTC,apport information
1795453,2018-10-15 17:27:21 UTC,apport information
1795453,2018-10-15 17:26:57 UTC,apport information
1795453,2018-10-15 17:26:56 UTC,apport information
1795453,2018-10-15 17:26:54 UTC,apport information
1795453,2018-10-15 17:26:53 UTC,apport information
1795453,2018-10-15 17:26:51 UTC,apport information
1795453,2018-10-15 17:26:50 UTC,apport information
1795453,2018-10-15 17:27:22 UTC,apport information
1795458,2018-10-01 16:28:23 UTC,"Thanks for raising this Elise. Is this something you or your team plan on addressing, or does this need an owner to follow it through?"
1795458,2018-10-01 18:06:56 UTC,"I'll give it a go, with the above caveat."
1795458,2018-10-01 18:39:36 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/607022"
1795458,2018-12-07 20:48:42 UTC,"Change abandoned by Sofia Enriquez (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/623343
Reason: Unproperly cherry-picked. Sorry, this was my first cherrypick."
1795458,2018-12-06 22:45:30 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/623343"
1795458,2019-01-29 16:30:45 UTC,"Change abandoned by Eric Harney (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/607022"
1795458,2019-01-25 23:34:16 UTC,"Backport proposed to branch: stable/pike
Review: https://review.openstack.org/#/c/625041/"
1795463,2018-10-05 07:23:26 UTC,"Hi Goutham, yes, I think your referenced solution is better."
1795463,2020-03-24 07:41:23 UTC,"Hi Dmitry, your issue is being worked on in https://bugs.launchpad.net/manila/+bug/1860061 via https://review.opendev.org/#/c/703025"
1795463,2019-11-12 11:39:35 UTC,This issue was fixed in the openstack/manila 7.4.0 release.
1795463,2019-11-12 11:32:48 UTC,This issue was fixed in the openstack/manila 8.1.0 release.
1795463,2019-11-11 12:48:49 UTC,"Hi All,"
1795463,2019-10-25 12:53:31 UTC,This issue was fixed in the openstack/manila 6.3.2 release.
1795463,2018-10-04 21:07:13 UTC,Thanks for this bug report Maurice.
1795463,2019-10-18 02:04:39 UTC,"Reviewed:  https://review.opendev.org/688542
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=bad03feea9a8470c9fe55f1a925d83e026353989
Submitter: Zuul
Branch:    stable/rocky"
1795463,2019-10-14 19:22:50 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/688542"
1795463,2019-10-21 20:12:16 UTC,"Reviewed:  https://review.opendev.org/689604
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=8263f911beaef26865d30c2cfee760c594175e5e
Submitter: Zuul
Branch:    stable/queens"
1795463,2019-09-26 19:50:07 UTC,This issue was fixed in the openstack/manila 9.0.0.0rc1 release candidate.
1795463,2019-09-26 17:23:19 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/685135"
1795463,2019-09-26 16:51:05 UTC,"Reviewed:  https://review.opendev.org/650986
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=57edcbd1da4b61ce1a61db3be0d69755d968c36c
Submitter: Zuul
Branch:    master"
1795463,2019-06-24 19:07:14 UTC,"Hi, Chuan! We can plan a implementation to the offset in another bug fix in the future."
1795463,2019-06-18 17:36:55 UTC,"current patch takes parameter `limit`, and disregards `offset`. Do you plan to implement the offset in another bug fix?"
1795463,2019-05-03 17:12:35 UTC,Review is here: https://review.opendev.org/#/c/650986/
1795463,2019-01-16 12:59:26 UTC,"Sadly I won't have time this year, feel free to pick this."
1795463,2019-10-14 19:21:53 UTC,"Reviewed:  https://review.opendev.org/685135
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=462b0e7461cdd00d51f15aacaa43854aeb0689f4
Submitter: Zuul
Branch:    stable/stein"
1795463,2019-10-18 23:22:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/689604"
1795469,2018-10-03 16:14:12 UTC,I just created a branch for this called user/sandbergja/lp1795469_add_cn_suffix_to_opac_holdings_order
1795469,2019-03-11 00:52:26 UTC,"This worked for me, remember to restart apache when testing to apply the change on a running system, took me a few minutes to remember that."
1795469,2020-07-28 14:14:34 UTC,"Pushed to master, rel_3_5, and rel_3_4. Thanks, Jane and Josh!"
1795470,2019-10-05 18:19:01 UTC,It would be great to have an indicator of missing barcodes (the current state is a frequent reason for confusion among staff in our consortium).
1795475,2018-10-01 17:29:34 UTC,Here's the Traceback:
1795479,2019-07-02 16:14:11 UTC,"Thank you for your bug report, the issue there seems to be with the ark software though, reassigning"
1795481,2018-10-01 18:05:10 UTC,I was able to confirm/validate the failure on a set of LXC containers:
1795481,2018-10-01 19:55:00 UTC,"This is resolved in Cosmic:
bladernr@cosmic:~$ iperf3 -c 10.148.80.151 -n 1500G -i 60
Connecting to host 10.148.80.151, port 5201
[  5] local 10.148.80.5 port 58834 connected to 10.148.80.151 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-60.00  sec   447 GBytes  64.0 Gbits/sec  845   1.04 MBytes
[  5]  60.00-120.00 sec   435 GBytes  62.3 Gbits/sec  653    898 KBytes
[  5] 120.00-180.00 sec   444 GBytes  63.5 Gbits/sec   47   3.01 MBytes
[  5] 180.00-203.80 sec   174 GBytes  62.8 Gbits/sec    0   3.01 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-203.80 sec  1.46 TBytes  63.2 Gbits/sec  1545             sender
[  5]   0.00-203.80 sec  1.46 TBytes  63.2 Gbits/sec                  receiver"
1795481,2018-10-01 19:00:16 UTC,"This also affects bionic:
bladernr@xenial:/etc/apt/preferences.d$ iperf3 -c 10.148.80.151 -i 60 -n 1500G
Connecting to host 10.148.80.151, port 5201
[  4] local 10.148.80.13 port 44836 connected to 10.148.80.151 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-60.00  sec   457 GBytes  65.4 Gbits/sec  2546   1.77 MBytes
[  4]  60.00-120.00 sec   482 GBytes  69.1 Gbits/sec   89   3.04 MBytes
[  4] 120.00-180.00 sec   478 GBytes  68.4 Gbits/sec   25   3.01 MBytes
[  4] 180.00-193.22 sec  82.7 GBytes  53.7 Gbits/sec  1091   1.60 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-193.22 sec  0.00 (null)s  66.7 Gbits/sec  3751             sender
[  4]   0.00-193.22 sec  0.00 (null)s  66.7 Gbits/sec                  receiver"
1795483,2018-10-01 18:53:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795483,2018-10-03 11:03:53 UTC,"I see the same behavior on a display with the same dimensions on a different laptop:
Asus ZenBook Flip 15 UX561UD
15.6 inch 16:9, 3840 x 2160 pixel, 282 PPI"
1795483,2020-04-10 10:37:32 UTC,"Still reproducible with Ubuntu 20.04 beta with gnome-control-center 1:3.36.1-1ubuntu4 and gnome-3.36.1, where the option to enable fractional scaling is exposed in the GUI"
1795487,2018-10-25 13:59:31 UTC,"Morgan, what do you propose we do about this? AFAIK this is just how openstackclient works. Obviously 'RegionOne' is an invalid uuid, so the log isn't wrong."
1795488,2018-10-01 18:27:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/607019"
1795488,2018-10-18 15:44:23 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611658"
1795488,2018-10-18 15:44:32 UTC,"Change abandoned by James Slagle (<email address hidden>) on branch: master
Review: https://review.openstack.org/607019
Reason: this is no longer relevant on master due to:"
1795488,2018-10-18 19:22:43 UTC,"Think we also see that here, checking to see if the latest tht is on the box"
1795488,2018-10-18 19:39:25 UTC,"wes, it's a different error. The CI log you posted shows:"
1795488,2018-10-22 21:16:21 UTC,"Reviewed:  https://review.openstack.org/611658
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7efe1087df1bd04e57afc67e1c6cb1ec96d161df
Submitter: Zuul
Branch:    stable/rocky"
1795488,2018-12-18 23:40:42 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.1.0 release.
1795488,2021-02-19 15:52:46 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1795502,2019-05-24 20:03:24 UTC,Was this fixed with https://review.opendev.org/#/c/626952/ ?
1795508,2019-05-10 18:07:32 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1795508,2019-01-31 03:52:17 UTC,"This bug is fixed with commit 48955354 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=48955354"
1795509,2018-10-01 21:30:09 UTC,This change was made by a bot.
1795509,2018-10-02 15:29:41 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1795509,2018-10-02 19:20:19 UTC,"This driver is in the kernel since 4.17 [1]. Before I used the media-tree backports[2], but had some issues (inkluding the reported bug) that I was hoping to get rid of. Though I can't say for sure wheter is was exactly the same. I just remember that a kernel bug showed up in dmesg."
1795510,2018-10-02 07:23:03 UTC,"What command are you issuing to achieve ""3. Destroy model""?"
1795510,2018-10-02 13:27:31 UTC,"Sorry, step 3 should have been ""remove application""."
1795510,2018-10-03 08:12:50 UTC,This looks like what we expect.
1795515,2019-04-07 16:53:56 UTC,A demo video would help to understand the problem.
1795515,2019-05-01 12:48:15 UTC,"This area is due to be looked at in v6, so I am tentatively setting the milestone."
1795523,2018-10-01 23:09:31 UTC,"This is a log file for Open Rails. Please include this file in bug reports.
--------------------------------------------------------------------------------
Date/time  = 10/2/2018 1:05:45 AM (2018-10-01 23:05:45Z)
BIOS       = X751LB.402 (American Megatrends Inc.)
Processor  = Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (4 threads, 2 cores, 2.2 GHz) (L1 Cache 32 KB) (L1 Cache 32 KB) (L2 Cache 256 KB) (L3 Cache 3072 KB)
Memory     = 11.9 GB
Video      = NVIDIA GeForce 940M              (2.0 GB RAM) (nvlddmkm 10.18.13.5946)
Video      = Intel(R) HD Graphics 5500 (1.0 GB RAM) (igdkmd64 20.19.15.4549)
Display    = \\.\DISPLAY1 (1600 x 900, 32-bit, primary, 0 x 0)
Display    = \\.\DISPLAY2 (1360 x 768, 32-bit, 1600 x 0)
Sound      = Bluetooth Audio Device (btath_a2dp 8.0.1.316)
Sound      = Realtek High Definition Audio (rtkvhd64 6.0.1.7224)
Sound      = NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (nvvad64v 1.2.30.0)
Disk       = C: (Local Fixed Disk, NTFS, 237.9 GB, 132.3 GB free)
Disk       = D: (CD-ROM Disc, )
Disk       = E: (Local Fixed Disk, NTFS, 117.2 GB, 69.7 GB free)
Disk       = H: (Local Fixed Disk, NTFS, 814.2 GB, 339.3 GB free)
OS         = Microsoft Windows 10 Home 64-bit (10.0.17134)
Runtimes   = 2.0.50727 SP2  3.0 SP2  3.5 SP1  4 Client  4 Full  4.0 Client
Runtime    = 2.0.50727.8935 (32bit)
\\.\DISPLAY1 = NVIDIA GeForce 940M              (nvd3dum.dll 10.18.13.5946)
    Anisotropy     = 16
    Render Targets = 4
    Streams        = 16 (stride 255)
    Textures       = 8 (16384 x 16384, repeat 8192, ratio 16384)
    Points         = 8192^2
    Volumes        = 2048^3
    Primitives     = 16777215
    Vertexes       = 16777215
    Vertex Shader  = 3.0 (4096 slots, 256 constants)
    Pixel Shader   = 3.0 (4096 slots)
    Clip Planes    = 8
\\.\DISPLAY2 = NVIDIA GeForce 940M              (nvd3dum.dll 10.18.13.5946)
    Anisotropy     = 16
    Render Targets = 4
    Streams        = 16 (stride 255)
    Textures       = 8 (16384 x 16384, repeat 8192, ratio 16384)
    Points         = 8192^2
    Volumes        = 2048^3
    Primitives     = 16777215
    Vertexes       = 16777215
    Vertex Shader  = 3.0 (4096 slots, 256 constants)
    Pixel Shader   = 3.0 (4096 slots)
    Clip Planes    = 8
--------------------------------------------------------------------------------
Version    = X4234
Build      = 0.0.6847.35965 (2018-09-30 19:58:50Z)
Logfile    = C:\Users\Robert Chalcak\Desktop\OpenRailsLog.txt
Executable = RunActivityLAA.exe
Argument   = -resume
Argument   = C:\Users\Robert Chalcak\AppData\Roaming\Open Rails\Trat ZSR 191-193 Vlaky  2018-10-02 00.47.11.save
--------------------------------------------------------------------------------
ActRandomizationLevel          =                0
ActWeatherRandomizationLevel   =                0
AdhesionFactor                 = (user set)     200
AdhesionFactorChange           = (user set)     0
AdhesionMovingAverageFilterSize =                10
AdhesionProportionalToWeather  =                False
Alerter                        = (user set)     True
AlerterDisableExternal         = (user set)     False
Autopilot                      =                False
AuxActionEnabled              ..."
1795523,2018-10-01 23:11:30 UTC,"In Open rails are long activites unless, because in case, the user needs to make a pause and save the game and turn off the game with returning later, because Open rails cannot load the sceene. This case is in both version like MONO and Ordinary version."
1795534,2018-10-02 02:32:17 UTC,"(updated box; rebooted since last comment; x86 (32bit))
Opening LXQt Appearance  (assuming theme is NOT Light [at login])"
1795534,2018-10-02 02:10:53 UTC,"I tried to replicate this bug; but only had issues with ""Light"" theme where last digit of seconds was obscured; hh:mm:ss is my chosen format.  I noticed updates available, so updated.  ""Light"" now selected as my default, so I logged out to let updates effect my LXQt desktop."
1795534,2018-12-02 04:17:31 UTC,[Expired for lxqt-themes (Ubuntu) because there has been no activity for 60 days.]
1795534,2018-10-02 07:42:15 UTC,In getting the screenshots - i changed from HH:MM to HH:MM:SS and noted the clock corrected itself!
1795534,2018-10-02 07:36:29 UTC,edited to indicate the issue is appreciable in system and light themes
1795534,2018-10-02 06:16:03 UTC,One other thing: lxqt-themes and lxqt-system-theme are both from the source package lxqt-themes.
1795534,2018-10-02 05:49:23 UTC,"Yep - I had no issues with ambience, dark, frost or kde-plasma (or lubuntu-arc)."
1795534,2018-10-02 04:43:34 UTC,"Ok, default's good. Yay. So now the blame isn't really on Lubuntu Artwork, but on the themes that are problematic. Do I understand that the two problematic themes are ""System"" and ""Light"" LXQt themes but there is no problem with ""Ambience,"" ""Dark,"" ""Frost,"" or ""Kde-plasma?"""
1795534,2018-10-02 04:18:51 UTC,"On a 'live' system (x86, current daily image) by changing theme I can make part of clock disappear off bottom right of screen.  I tried this on four machines (t43 [4:3], d610 [4:3], sl510 [ws] & dx6120 [4:3] being models referred to in my QA-testing; but note all have similar (low-med) resolution screens)."
1795534,2018-10-02 06:13:19 UTC,Well and it's remarkable that the problems are not permanent.
1795534,2018-10-02 02:43:41 UTC,I assume that by default there are no problems?
1795543,2020-11-09 08:39:33 UTC,"Hello,
do you still have this issue with the latest 4.15 kernel on Xenial?
Thanks"
1795543,2021-01-09 04:17:25 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1795545,2018-10-22 23:56:16 UTC,"On 10/19/18 2:38 PM, Frank Ch. Eigler wrote:

> Hi -
>
> This commit appears to fix this problem.
>
> https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=8bc64034509474bee3fb7996b2a9e74c8bc27281
>
"
1795545,2018-10-19 21:38:23 UTC,Hi -
1795545,2018-10-23 00:04:45 UTC,"On 10/19/18 2:38 PM, Frank Ch. Eigler wrote:

> Hi -
>
> This commit appears to fix this problem.
>
> https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=8bc64034509474bee3fb7996b2a9e74c8bc27281
>
"
1795555,2018-10-02 06:00:03 UTC,This change was made by a bot.
1795555,2018-10-03 08:17:14 UTC,"""apt-get install -f"" want delete package ""linux-image-4.15.0-33-generic""
and... I see same error"
1795555,2018-10-03 11:40:17 UTC,and this:
1795555,2018-10-06 23:39:17 UTC,"Watch this??? On every apt action (upgrade, install)"
1795555,2019-02-07 13:59:46 UTC,"i have got the same error, pls solve this because i can't install any package"
1795555,2018-10-02 15:28:30 UTC,You may need to run the following from a terminal:
1795557,2018-10-11 14:07:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795557,2018-10-11 14:09:11 UTC,i think i hit the same issue:
1795559,2018-10-02 18:25:20 UTC,Most likely there is one AI train station stop defined in .srv or .trf file which does not exist.
1795559,2018-10-03 12:14:07 UTC,"Respected developers.
       I am very thankful for your reply. But I am unable to identify the
error. so please if possible provide details about error elimination
process."
1795562,2019-03-18 04:30:27 UTC,This code has been removed in master: https://gitlab.com/inkscape/extensions/commit/c1cc229abaf16a76f13fabae85ed2c6560d63fed
1795562,2018-10-02 09:06:00 UTC,Hi & thanks for the report!
1795562,2019-03-20 09:06:40 UTC,Backported to 0.92.x here: https://gitlab.com/inkscape/inkscape/merge_requests/589
1795583,2018-10-22 06:27:28 UTC,"4.4.0-1032.35 aws
Regression test CMPL, RTB."
1795583,2018-10-22 16:28:26 UTC,This bug was fixed in the package linux-aws - 4.4.0-1032.35
1795583,2018-10-22 17:11:06 UTC,The package has been published and the bug is being set to Fix Released
1795584,2018-10-15 07:32:01 UTC,Hardware Certification have begun testing this -proposed kernel.
1795584,2018-10-19 06:53:55 UTC,"4.4.0-138.164~14.04.1 - generic
Regression test CMPL, RTB."
1795584,2018-10-19 15:49:00 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/4.4.0-138.164~14.04.1/trusty-4.4-proposed-published.html"
1795584,2018-10-22 16:29:15 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-138.164~14.04.1
1795584,2018-10-22 17:01:03 UTC,The package has been published and the bug is being set to Fix Released
1795585,2018-10-22 16:32:50 UTC,This bug was fixed in the package linux-aws - 4.4.0-1070.80
1795585,2018-10-19 10:21:26 UTC,"4.4.0-1070.80 - aws
Regression test CMPL, RTB."
1795585,2018-10-22 17:01:31 UTC,The package has been published and the bug is being set to Fix Released
1795587,2018-10-04 11:20:27 UTC,"We are using the 4.15 HWE kernel on Xenial, and the i40e driver is working, the only problem that the kernel driver version is not matching the minimum requirement for 6.01 Firmware, what is required for latest dpdk / sriov features and upgrades."
1795587,2018-10-04 11:06:56 UTC,"Does this have any connection to the bug ""i40e driver does not work with kernel 4.15"" described on https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1779756 ?"
1795587,2018-10-04 11:03:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795587,2018-10-02 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1795587,2018-10-02 09:31:31 UTC,"It is rather a feature request than a bug, but affects the supportability of NIC firmware, and the performance of SRIOV and DPDK."
1795589,2018-10-22 17:02:05 UTC,The package has been published and the bug is being set to Fix Released
1795589,2018-10-11 11:06:19 UTC,"4.4.0-1036.42 - kvm
Regression test CMPL, RTB."
1795589,2018-10-22 16:32:57 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1036.42
1795591,2018-10-17 01:38:59 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1099.107/raspi2-4.4-proposed-published.html"
1795591,2018-10-15 07:31:50 UTC,Hardware Certification have begun testing this -proposed kernel.
1795591,2018-10-23 06:30:47 UTC,The package has been published and the bug is being set to Fix Released
1795591,2018-10-22 16:33:24 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1099.107
1795591,2018-10-09 13:13:56 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/mqbmjQzP/418-pi2-kernel-440-1099107-74"
1795593,2018-10-09 13:06:24 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/yLrw7DTa/419-dragonboard-kernel-440-1103108-70"
1795593,2018-10-15 07:31:56 UTC,Hardware Certification have begun testing this -proposed kernel.
1795593,2018-10-17 01:35:36 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1103.108/snapdragon-4.4-proposed-published.html"
1795593,2018-10-22 16:34:04 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1103.108
1795593,2018-10-23 06:31:13 UTC,The package has been published and the bug is being set to Fix Released
1795596,2018-10-09 10:45:45 UTC,"3.13.0-161.211~precise1 - generic
Regression test CMPL, RTB."
1795596,2018-10-22 16:34:35 UTC,The package has been published and the bug is being set to Fix Released
1795602,2018-10-02 09:14:15 UTC,"I didn't see that swift3 is now s3api and that the proxy-server.conf-sample file has a sample for enabling this.  s3api is discussed here:
https://docs.openstack.org/swift/latest/middleware.html#module-swift.common.middleware.s3api.s3api"
1795602,2019-10-26 07:31:01 UTC,Supported in the Train release: https://docs.openstack.org/kolla-ansible/latest/reference/storage/swift-guide.html#s3-api.
1795603,2019-10-02 05:35:31 UTC,Verified the bug passed with:
1795609,2018-10-02 09:52:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/607138"
1795609,2018-10-02 09:52:28 UTC,https://review.openstack.org/607138
1795611,2019-06-09 16:37:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795615,2018-11-04 04:51:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795615,2018-11-04 04:53:44 UTC,"Happened during a reboot after an update that requested a reboot. I did not do the reboot for several days after the update. Even with the error, the system appeared to come up normally."
1795628,2019-07-18 23:16:25 UTC,Thanks for filing a bug.  It's definitely a file cloud-init generates and it could clean it up if requested.
1795629,2019-04-20 21:23:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795630,2018-10-02 23:08:41 UTC,"We've had the idea of revamping this page (and similar ones, e.g. group member invitations) to make them more accessible and perform bulk options so you can see more user details. Possibilities of what to show is the"
1795642,2018-10-02 19:15:04 UTC,We still need to figure out and brainstorm how we want to solve this.
1795645,2018-11-24 18:12:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795646,2019-02-12 13:41:02 UTC,Is it still an issue?
1795646,2019-02-12 13:57:58 UTC,"Yes, this is still the case. It's not bothering me that much so never went to fixing it as I had other things to get working in priority."
1795650,2018-10-02 23:01:05 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1795651,2018-10-02 17:42:35 UTC,"Hi. ICU tz data is kept available such as https://github.com/unicode-org/icu-data/tree/master/tzdata/icunew/2018e/44 ( look in the le / be / ee for different endianness, ee is ebcdic ) . It could be rebuilt into an updated icu package.  Or, it could be side loaded (as a separate data file loaded at runtime)."
1795651,2018-10-02 20:53:26 UTC,"Yes, I'm well aware it could be rebuilt. Do you suggest me taking over the maintenance and rebuild it for you?"
1795651,2020-03-25 22:45:05 UTC,@anrdaemon not sure what you mean. ICU itself doesn't cut a release every time there's a timezone update.
1795659,2020-01-30 14:19:02 UTC,"The new patch merge is being work on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856949 (thanks Juergh and Marcelo for this work). So in case you face this issue in the future, please use the LP #1856949 for reporting."
1795659,2019-12-30 12:49:20 UTC,"Hi Guillaume and all involved, it seems this bug still can occur even with the backported fix [0]. I found an upstream new fix that is quite promising, it addresses this specific oops. In the past it was thought by maintainers that other fix [0] could reduce the likelihood of those crashes in smb2_push_mandatory_locks (and it may worked, reducing the occurrence), but the fact is a proper fix was never worked until kernel 5.5."
1795659,2019-11-04 16:53:08 UTC,"Hi Guillaume, thanks for your report! Do you have more details on how did you reproduce it? It was ""organic"", or can you trigger that using some workload or test pattern? Also, based on the log output that you pasted, seems it took about 30 hours to reproduce, correct? Let me know if possible the topology of the cifs volumes in your system (how many mount points you have, how many targets - and where are they -, etc)."
1795659,2019-11-04 16:09:22 UTC,"Hi,"
1795659,2019-08-13 11:27:47 UTC,This bug was fixed in the package linux - 4.15.0-58.64
1795659,2019-07-31 14:27:36 UTC,"I've validated the -proposed kernel for Bionic (4.15.0-56) using the xfstests suite mentioned in the description. Interestingly, the patch seems to fix the test generic/504, which failed both in smb2 and smb3 only in kernel 4.15.0-55. Other than that, the same amount of tests failed in both cases, and no significant performance impact was noticed."
1795659,2019-07-29 06:58:31 UTC,This bug was fixed in the package linux-azure - 4.15.0-1052.57
1795659,2019-08-07 08:34:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1795659,2019-07-17 20:04:25 UTC,SRU request sent to kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2019-July/102354.html
1795659,2019-05-06 18:18:32 UTC,"Hi, have some news in this one. I've emailed Microsoft CIFS maintainers, they recommended the following patch as a potential fix:
b98749cac4a6 (""CIFS: keep FileInfo handle live during oplock break"")."
1795659,2019-04-10 14:06:22 UTC,"Thanks for reporting that Stefan! There's a Debian bug report (although the kernel
version is different, seems the same issue): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830771 ."
1795659,2018-12-02 04:17:54 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1795659,2018-10-02 17:52:16 UTC,I'm unable to fully test the upstream bugs as I can't install linux-headers-4.19.0-041900rc6-generic due to libssl1.1 not being available for 4.15. System does boot without the generic package on the new version though.
1795659,2018-10-02 15:14:37 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1795659,2019-07-25 18:32:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1795673,2020-08-18 17:04:24 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1795675,2018-10-05 14:21:08 UTC,"Turns out that it is the cpu hotplug kernel selftest that crashes the kernel. Simply run:
$ bash tools/testing/selftests/cpu-hotplug/on-off-test.sh
from the Trusty 3.13 tree and the machine will fall over a couple of minutes later."
1795675,2018-10-05 14:21:40 UTC,Works fine in a VM.
1795675,2018-10-02 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1795676,2018-10-02 14:50:00 UTC,this is an example of how sportcar was exported if I wanted a 400x400 image. There is no way to keep the proportions today.
1795676,2018-10-02 14:51:32 UTC,"here is the original svg I used (found on google search) found here:
http://tuxpaint.org/stamps/stamps/vehicles/auto/sportscar3.svg"
1795676,2019-03-12 00:20:51 UTC,This is a good suggestion to export the png and preserve the aspect ratio.
1795676,2020-03-27 09:27:58 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1795677,2018-10-25 23:50:43 UTC,">>> What's the impact to users in practice please?
We had a special use case (and we patched locally), so the impact of that is not so high for the users, but we want to report it. I think it is okay if it will be fixed in the upstream."
1795677,2018-11-05 07:25:48 UTC,Subscribing Andreas to track this with the next Samba merge that contains the fix.
1795677,2018-10-25 13:13:25 UTC,What's the impact to users in practice please? Did you detect the leak using some leak detection tool or because it was causing you a practical problem?
1795677,2018-10-24 08:41:58 UTC,">>> Do you have a pointer to an upstream bug, or somewhere where this was reported or fixed?
No, I do not have. We found the bug in the code and I reported it only here."
1795677,2018-10-18 19:27:40 UTC,Thanks for filing this bug in Ubuntu and providing a patch.
1795677,2018-10-02 16:23:32 UTC,"The attachment ""f0e88410bd2528517910f780d71e63f8effb91ef.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1795678,2018-10-02 18:30:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795678,2018-10-09 12:56:34 UTC,"Processing triggers for initramfs-tools (0.130ubuntu3.3) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic
W: initramfs-tools configuration sets RESUME=UUID=8690dd17-8c64-490e-9c50-d6099db9e1e4
W: but no matching swap device is available.
cp: -r not specified; omitting directory '/etc/udev/rules.d/79-udev-epson.rules'
E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-34-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1"
1795678,2018-11-14 23:46:56 UTC,"I think the following may be associated with this problem.
My system will not resume from suspend
Hard rebooting causes a Kernel panic and inability to mount the file system
From Grub using advanced options I can eventually ""resume"" through 4.15.0-34-generic
 (but not 4.15.0-36 or 4.15.0-38!) - but it does not resume the previous session"
1795694,2018-10-02 17:03:11 UTC,further to this:
1795694,2018-10-08 15:41:13 UTC,"For anyone else deploying with SSL terminated at HA proxy, kolla-ansible does not configure the services config files correctly for this scenario, how a service detects the public URL when configured in reverse proxy is implemented in different ways, services configured with the wrong scheme use version.py and build with host_url, so while the keystone catalog may have the correct scheme, the actual endpoint is wrong."
1795694,2018-10-02 16:27:21 UTC,"how does this even happen?, for services using the internalURL the links should be that of the 'kolla_internal_fqdn' why then are they using the external_fqdn with the internal scheme? i.e. the links that  the http services are purporting to use 'internalURL' do not exist in the openstack catalog."
1795697,2018-10-07 07:05:55 UTC,The Danish translation for gnome-font-viewer was incomplete upstream for 3.30.0. You can ask upstream to make a 3.30.1 release if you want the latest translations.
1795697,2018-10-07 07:12:28 UTC,"Seb, it looks like there is a very large number of translation files in needs review status."
1795697,2018-10-08 16:06:43 UTC,"the evolution-data-server/evolution issues have been fixed now (it was another of those cases where template sharing was enabled on launchpad leading to not have source files imported), I wouldn't be susprised if we still have buggy components in that case in cosmic..."
1795697,2018-10-04 14:57:01 UTC,"This appears to have affected gtk+-properties as well, but that translation is up to date now.  Probably was fixed at the same time as for the main gtk+ package."
1795697,2018-10-04 07:50:58 UTC,"Thanks for the report, that's fixed in launchpad now and will be fixed in cosmic before it's out with a languagepack export"
1795697,2018-10-03 12:00:05 UTC,"Looks like the gnome-software bug mentioned above was a false alarm.  But the Gtk module has indeed not imported those translations that were present upstream at the time of the GNOME release deadline.  It is essential that these imports are triggered correctly, else we will either get duplicate work on the part of translators or ship a distribution which is not fully translated."
1795697,2018-10-04 14:52:59 UTC,Thank you very much.  I will open this in a few more projects that seem to be affected as well.
1795703,2020-03-24 15:57:34 UTC,This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 67ubuntu20.04.3
1795703,2019-09-30 09:19:06 UTC,"Have same issue with same error message.
For now every time it happens, I run `Alt+f2` and run `r` command."
1795703,2019-01-17 14:00:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795703,2020-01-05 15:37:40 UTC,"I get this quite regularly, thanks to the participants of this for the work around, very useful. But this is definitely still a problem."
1795703,2019-11-21 00:14:55 UTC,"This seems to only happen to me after a period of inactivity, as i've only seen the dock disappear after logging back in from the lock screen. I can't reproduce it, other than to say it happens about once every week or two."
1795703,2019-09-30 09:37:07 UTC,"It's happening very frequently for me again. I decided to wait for 20.04 basically, meanwhile the ""fix"" i've found is to go to https://extensions.gnome.org/extension/307/dash-to-dock/ and uninstall-install the extension, it would bring the dock back without a need to reboot."
1795703,2019-03-10 18:58:47 UTC,"Ok, happened again :( After such a long time, I was hoping it's gone. Sorry for spamming."
1795703,2019-01-16 04:17:40 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1795703,2019-01-18 10:22:51 UTC,"Yeah. Also, once again, this didn't happen in quite some time and with big uptimes. I wouldn't bother until many more people confirm."
1795703,2019-01-29 22:29:46 UTC,Same problem here (I think).
1795703,2019-01-18 10:15:08 UTC,"the log has this warning, unsure if that's what makes the dock unload though?"
1795703,2018-11-07 13:21:22 UTC,"I think this doesn't happen anymore, didn't check logs but the dock is there for more than 7 days now. Yay! :)"
1795703,2019-01-16 04:17:38 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1795703,2018-11-16 09:36:45 UTC,"Ok, so it happened again, but it took 15 days this time :)"
1795703,2018-11-07 15:07:47 UTC,"Thanks for the update, it's weird if it got away without a real fix, maybe it's transient. Setting as incomplete for now, please provide the informations if you hit the issue again, thx"
1795703,2018-11-07 13:22:38 UTC,"I don't see a button to close it, so anyone who does -- feel free to."
1795716,2020-04-07 13:01:01 UTC,"Change abandoned by Brian Haley (<email address hidden>) on branch: master
Review: https://review.opendev.org/607341
Reason: No longer needed"
1795716,2018-10-31 15:07:36 UTC,"Andreas - yes, I guess it wasn't clear to me, I will take a look at the downstream bug again."
1795716,2018-10-05 20:27:11 UTC,"I dug into this further. I discovered this issue in RH OSP 10, but it's fixed in RH OSP 13 and upstream master."
1795716,2018-10-02 18:49:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/607341"
1795716,2018-10-31 14:30:42 UTC,"Hi,"
1795716,2018-10-02 18:34:26 UTC,This should fix it:
1795720,2020-06-22 22:20:52 UTC,"Jane, I wanted to clarify the work.  By navbar, are you referring to the dark green top nav on all pages?  (See attached screenshot)"
1795720,2020-06-22 23:54:28 UTC,"Oh, good clarification, Mike!  Once you open up one of the navbar menus, it's all the little icons on each of the entries.  For example, if you open up the Cataloging menu, there are icons next to the entries for ""Search the catalog"", ""Item status"", etc."
1795720,2020-06-23 23:36:47 UTC,"I applied aria-hidden=""true"" to  69 icons in the navbar.  I intentionally didn't apply it to the far left and far right icons (home and list) because there is no other text associated with them."
1795720,2020-06-25 13:39:26 UTC,"> Re-reading the original description, there is a reference to an Angular
> JS navbar. I'm thinking that's something that was around in 2018 but not
> currently?  If I'm missing anything, please let me know and I'm happy to
> address it.
"
1795720,2020-08-24 15:36:50 UTC,"Tested and pushed to master, rel_3_5, and rel_3_4. Thanks, Mike and Terran!"
1795720,2020-06-25 22:13:32 UTC,"Thanks for that, Galen.  I went in and made the same changes to the Angular JS navbar. 82 icons were modified.  The branch is the same as before:"
1795720,2020-08-14 20:45:27 UTC,Hi Mike - I am getting a conflict error when I try to cherry-pick this to current master. Can you take a look?
1795720,2020-08-14 21:30:35 UTC,"I cherry picked this and pushed a branch with the latest code.
Looks like the conflicts were due to some minor changes on the navigation.  For example, on the latest master there are 2 different options  ""Search the Catalog"" and ""Search the Catalog (Traditional)"""
1795720,2020-08-18 18:27:56 UTC,"I went to test this and discovered that MacOS voice over actually doesn't read the menus at all, which is unfortunate so I can't test this.  Another screen reader like JAWS or MS's Narrator may still be useful for testing."
1795720,2020-08-20 18:28:49 UTC,re: screen readers for testing.
1795720,2020-08-20 20:21:21 UTC,Here are improved testing instructions:
1795720,2020-08-20 21:10:08 UTC,I think more accessibility reviews are in order and the tools above are an excellent place to start - a quick look at the new Firefox Accessibility Inspector identified some focusability issues with the navigation menus that should be addressed.
1795725,2019-07-01 00:58:29 UTC,"Hi Jeremy,"
1795725,2019-07-04 15:31:36 UTC,I got help with my personal bionic issue. It was a missing package:
1795745,2020-10-20 09:16:00 UTC,"I am not sure if this is really fixable with CSS
Any gtk theme that has this right?"
1795745,2018-10-03 03:03:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795745,2019-11-28 12:23:23 UTC,"In current version the alignment is still slightly off by few pixels, however the same misalignment is present upstream (at least on Adwaita GTK 3.32), so the fix should be made there first."
1795747,2020-09-04 11:46:07 UTC,I think this one is partially invalid/duplicate/fixed in release.
1795757,2018-10-02 22:18:48 UTC,"pardon je ne comprends pas trop je laisse a plus tard, j'espere que ca se resoud intuitivement
peut etre je ne sais trop merci cordialement"
1795757,2018-12-22 09:36:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795762,2018-10-05 20:13:17 UTC,FWIW the bsg-mailx package also supplies a compatible mail command and pulls in far fewer dependencies.
1795763,2019-09-17 20:06:15 UTC,"hapening to me with ubuntu 19.04, pci card 3.1 usb box 10 drives."
1795763,2018-10-27 08:11:29 UTC,I use:
1795763,2018-10-26 23:59:36 UTC,unbind and bind gets the usb enumeration back
1795763,2018-10-26 23:56:43 UTC,apport information
1795763,2018-10-26 23:45:53 UTC,kernel-bug-exists-upstream
1795763,2018-10-03 14:15:35 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1795763,2018-10-02 23:02:49 UTC,apport information
1795763,2018-10-02 23:02:46 UTC,apport information
1795763,2018-10-02 23:02:44 UTC,apport information
1795763,2018-10-19 19:31:16 UTC,I'm also running into this problem:
1795763,2018-10-02 23:02:41 UTC,apport information
1795763,2018-10-02 23:02:40 UTC,apport information
1795763,2018-10-02 23:02:39 UTC,apport information
1795763,2018-10-02 23:02:38 UTC,apport information
1795763,2018-10-02 23:02:37 UTC,apport information
1795763,2018-10-02 23:02:36 UTC,apport information
1795763,2018-10-02 23:02:34 UTC,apport information
1795763,2018-10-02 23:02:33 UTC,apport information
1795763,2018-10-02 23:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1795763,2018-10-02 23:02:43 UTC,apport information
1795786,2019-01-09 14:43:55 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/629515"
1795786,2019-01-10 12:04:49 UTC,"Change abandoned by Serhii Rusin (<email address hidden>) on branch: master
Review: https://review.openstack.org/627983
Reason: This is no need to remove because it's gonna be re added in glance for v2[1] as image cache will play a big role for Edge computing."
1795786,2019-06-14 15:58:50 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/629515
Reason: Patch to master was abandoned."
1795788,2018-10-03 06:08:22 UTC,Patch for version https://git.openstack.org/cgit/openstack/openstack-ansible-os_horizon/commit/?h=stable/queens&id=0654b3847f7e74f817dfb64a9ac9a5b0ee3f3bb9
1795788,2020-04-10 22:25:26 UTC,"Reviewed:  https://review.opendev.org/607474
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_horizon/commit/?id=d86285b377221fb5522207a9da6cbfbdea4dd1e9
Submitter: Zuul
Branch:    master"
1795788,2020-04-14 12:36:46 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/719934"
1795788,2020-05-12 18:35:43 UTC,"Reviewed:  https://review.opendev.org/719934
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_horizon/commit/?id=e3326b77086b3865202cff9bce95377937aa6f07
Submitter: Zuul
Branch:    stable/train"
1795788,2020-06-10 13:20:30 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/734834"
1795788,2020-06-11 17:17:52 UTC,"Reviewed:  https://review.opendev.org/734834
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_horizon/commit/?id=198fbf664636a1ce8340537bec0da30bf99b4248
Submitter: Zuul
Branch:    stable/stein"
1795789,2018-10-03 17:57:02 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1795799,2018-10-03 09:26:21 UTC,Here's what Suse62 does.
1795799,2020-11-12 07:12:59 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1795799,2021-01-12 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1795800,2020-03-18 14:43:01 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.opendev.org/634826"
1795800,2019-03-25 19:24:57 UTC,"Still working on this, I've gotten a flask hook setup to catch any unauthorized, allowing us to delay the Unauthorized exception until the very end, however I'm still not seeing identical times. Local testing is showing .480 seconds for an existing user while it's gone from ~0.022 to ~0.033 for invalid users with delaying the exception."
1795800,2019-02-14 17:26:39 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.openstack.org/625699
Reason: Replaced by https://review.openstack.org/#/c/634826/"
1795800,2019-01-03 01:20:56 UTC,Have requested MITRE to review this thread again and updated the CVE dispute info.
1795800,2018-12-17 22:57:36 UTC,"Change abandoned by Gage Hugo (<email address hidden>) on branch: master
Review: https://review.openstack.org/625700"
1795800,2018-12-17 19:54:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625700"
1795800,2018-12-17 19:53:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625699"
1795800,2018-12-17 14:22:33 UTC,"Note that, unlike what the CVE dispute info suggests, the Keystone team has not concluded performance degradation would result from possible methods of reducing the efficacy of this particular oracle. They in fact indicated that fixes for this hardening opportunity would be welcome (""wishlist"" importance, please see Colleen's comment #9)."
1795800,2018-12-17 14:13:54 UTC,"I've updated the bug title to more accurately indicate this is a timing oracle in Keystone's core auth plugin, and so is still mitigated by the usual account brute-forcing defenses (e.g., enforcing strong authentication secrets, temporarily rejecting failing authentication attempts per source IP address, throttling calls to relevant API methods, et cetera)."
1795800,2018-12-17 08:10:27 UTC,CVE-2018-20170 assigned
1795800,2019-02-04 22:43:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634826"
1795800,2018-12-10 00:11:08 UTC,"Regardless of the ""to fix or not to fix"" question, can we please start the process of filing this bug with MITRE and get a CVE assigned for tracking?"
1795800,2018-12-10 02:19:21 UTC,"The OpenStack Vulnerability Management Team only requests CVE assignments to track vulnerabilities corresponding to fixes they're announcing via OpenStack Security Advisory publications, but anyone can request a CVE assignment from MITRE for any issue they'd like to track (or assign one themselves directly if they're a CNA). Please don't let the ongoing conversation stop you from obtaining a CVE for this particular bug if you want one, but please note within the bug report if you do so in order that we might avoid future duplication."
1795800,2018-10-03 12:20:26 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1795800,2018-10-03 15:23:00 UTC,I tested this in a test env we have here in our company on Identity 3.8. The POST payload was from the API https://developer.openstack.org/api-ref/identity/v3/#password-authentication-with-unscoped-authorization
1795800,2018-10-03 16:11:11 UTC,There are a number of things here that make it difficult to solve:
1795800,2018-10-03 14:57:52 UTC,"I can attempt to recreate this, what environment did you use to test this?  Looks like devstack?"
1795800,2018-10-03 17:58:51 UTC,"Test this with a containerized OpenStack deployment that runs pretty fast, both authenticating successfully and by providing a non-existent username produced a difference of ~0.020 seconds."
1795800,2018-10-03 18:15:33 UTC,"Thanks, I've gone ahead and triaged this as a hardening opportunity for now."
1795800,2018-10-24 18:00:36 UTC,"I don't know how we'll address this. Realistically, I think this is going to have to be marked as invalid/wont fix/opinion. I'm going to mark it as wont fix, we can circle back on it if there is more discussion to be had."
1795800,2018-10-25 14:19:50 UTC,I disagree that this is too hard to fix. In fact I'm fairly sure I found it already:
1795800,2018-10-03 17:33:22 UTC,"My opinions mirror those expressed by Damien Miller in his oss-security ML followup[*] about CVE-2018-15473 for a similar report in OpenSSH. To summarize, it isn't actually a user enumeration bug, it's a timing oracle which can lead to user enumeration via brute-force mechanisms, and there's a wide gulf of criticality between the two. The usual mitigations against brute-force attacks apply here."
1795808,2018-10-28 00:16:18 UTC,"Uncommenting ""WaylandEnable=false "" worked for me as well. And, the GPU is back and working for SETI."
1795808,2019-08-05 22:28:05 UTC,"thank you. uncommenting ""WaylandEnable=false "" worked for me as well. now I can use android studio emulator with hardware accelerator."
1795808,2018-11-26 08:07:48 UTC,"CTRL-ALT-F2 followed by CTRL-ALT-F1 bypassed the issue for me. However I have now uncommented the WaylandEnable in gdm3 config, and that allows the boot sequence to complete and display the login screen."
1795808,2018-11-14 00:51:20 UTC,"Uncommenting ""WaylandEnable=false"" line on /etc/gdm3/custom.conf left my computer without booting the UI, it got stuck with the message ""A start job is running for Hold until boot process finishes up (Xmin Xs/no limit)"", I was not even able to switch to terminals using CTRL+ALT+FX. To fix it I had to boot on ""safe mode"" and comment out that line again to at least boot using Wayland."
1795808,2018-11-08 21:11:11 UTC,I have KUbuntu installed with sddm and have same problem with my GT630M on 390 and 396 drivers.
1795808,2018-10-25 08:57:26 UTC,"That makes sense. Lightdm was never there, which probably means there was no other display manager."
1795808,2018-10-25 04:38:18 UTC,This worked for me as well.
1795808,2018-10-25 05:55:24 UTC,"Uncommenting ""WaylandEnable=false "" worked for me as well."
1795808,2018-10-24 23:30:04 UTC,Solution is
1795808,2018-10-24 20:19:35 UTC,Problem is in GDM3. I removed it and installed lightdm. OS booted normally.
1795808,2018-10-24 19:31:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795808,2018-10-24 19:00:05 UTC,"Ubuntu 18.10. No login screen after Nvidia-410 drivers installation.
System accessible via ssh.
Only after purge nvidia drivers login screen back and system works fine"
1795808,2018-10-25 08:37:08 UTC,"Coz u need install another display manager instead of removed gdm3, lightdm for example.
But uncomment WaylandEnable in gdm3 config is much easir solution of coz"
1795809,2018-10-03 07:30:51 UTC,More details can be found here: https://github.com/wavexx/screenkey/issues/82#issuecomment-426457927
1795809,2020-05-18 09:35:12 UTC,"The new package (0.10~rc1-1) is based on Pythn3 and Gtk3, so python-appindicator dependency is no longer relevant. I close this bug report."
1795816,2020-02-21 16:38:48 UTC,This issue was fixed in the openstack/neutron-dynamic-routing 16.0.0.0b1 development milestone.
1795816,2019-11-13 22:31:39 UTC,"Reviewed:  https://review.opendev.org/665328
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=4780fe548b86eba7f64a57ccf2d000958c238253
Submitter: Zuul
Branch:    master"
1795816,2019-06-14 08:30:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665328"
1795816,2018-10-15 15:18:48 UTC,"I spoke too soon, I was able to reproduce this on master. This occurs when a VM with an associated FIP is destroyed before the FIP is disassociated. The FIP is disassociated here [1], which results in a following notification payload that does not contain last_known_router_id [2]. In practice this shouldn't affect BGP announcements, but it isn't very clean. This can be fixed as described in the report by simply being more defensive in the plugin, or the notification from the L3 plugin could use a more well-defined payload."
1795816,2018-10-15 07:14:20 UTC,"python-neutron-12.0.3-1
openstack-neutron-bgp-dragent-12.0.1-1
openstack-neutron-dynamic-routing-common-12.0.1-1
python2-neutron-lib-1.13.0-1"
1795816,2018-10-15 13:57:06 UTC,"I think we can definitely be more defensive about this sort of thing. This is causing me to want to look at little deeper at the notifications neutron-dynamic-routing consumes. Is this blocking you? I assume new and updated FIP announcements would end up delayed because of this, but within 30 seconds the new route should be announced. Are you seeing any other behavior that is problematic, or is this just noise in the logs for you?"
1795816,2018-10-14 08:44:01 UTC,"Can You provide exact versions of: neutron, neutron-dynamic-routing and neutron-lib used when this issue happens to You?"
1795816,2018-10-12 07:49:11 UTC,"Unfortunately no, I don't run CI jobs. Tempest is generating this problem in production environment."
1795816,2018-10-11 08:08:08 UTC,Do You have link to any CI job results with such error?
1795816,2018-10-15 14:46:36 UTC,"I'm unable to reproduce this behavior on master. This would be encountered whenever a new floating IP that has no previous router association is associated, disassociated, or migrated. I am surprised that last_known_router_id isn't included in the notification payload https://github.com/openstack/neutron/blame/f88cb5276dc8d31b484772f31160fc1071a28541/neutron/db/l3_db.py#L1294. I'll keep digging and go back to something older than master."
1795818,2018-12-18 22:04:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795827,2018-10-03 08:51:13 UTC,Also 'is set:' should probably be 'is not set:'?
1795828,2018-10-11 15:50:30 UTC,May I have access to setup?
1795828,2018-10-10 05:29:28 UTC,"@Vinod:  why ifup/down should touch agent container? To down vhost0 interface it is enough to just stop dkdp container and bind back to system NICs, ifup bind NICs to dpdk again and init vhost0."
1795828,2018-11-27 14:20:36 UTC,Issue was in manually patched /etc/sysconfig/network-scripts-vrouter-dpdk-env file. There were names of containers commented that is why ifdown script was not able to stop dkdk container and rebind scripts hangs because of opened descriptors.
1795828,2018-10-08 22:37:31 UTC,"Michael - If this  is the model we want to follow for osp13, then the ifdown should stop the vrouter container first and bind the interfaces back to kernel and the reverse on ifup."
1795828,2018-10-03 17:04:23 UTC,"From Michael Henkel:
ifdown stops dpdk pmd container and attaches interfaces back to kernel. ifup attaches interfaces to dpdk and starts pmd container .
dpdk pmd container should not be restarted manually."
1795828,2018-10-03 16:25:56 UTC,Hi Bernhard
1795828,2018-10-09 11:08:32 UTC,The changes to fix this bug needs to be part of provisioning or part of if-up/down scripts. Hence removing the vrouter tag.
1795829,2019-08-20 01:48:32 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1795831,2018-10-03 09:27:53 UTC,There was a separate variable vm-mime-alternative-yank-method. Added a default (of nil) so that it uses the same setting as vm-mime-alternative-show-method.
1795840,2018-11-22 14:03:34 UTC,"The highlight points to the channel being tracked, fwiw"
1795840,2018-11-22 14:15:29 UTC,"Right, but since it's a local install, it isn't really/actively tracking it, is it?"
1795844,2018-12-07 16:29:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795852,2019-01-11 07:46:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795852,2020-01-10 10:33:56 UTC,"This happened to me when I upgraded from 16.04 LTS to 18.04 LTS, I noticed error dialog boxes during the install but unsure if they are related."
1795861,2018-10-24 00:41:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795866,2019-12-10 12:43:01 UTC,"Here is a net on which the problem can be reproduced. The issues is in using the GCD optimization which causes the shortest trace to be 30 time units, but with this technique disabled the shortest trace is only 28 time units."
1795869,2018-10-03 16:32:40 UTC,Yes I wrote the instructions on the raspberry pi wiki about how to boot arm64.  But I'm not talking about that here.
1795869,2018-10-03 15:33:42 UTC,"We have a kernel dedicated to the RaspberryPi boards (linux-raspi2), why do you want to use the generic-lpae kernel instead?"
1795869,2018-10-04 08:06:54 UTC,"This https://ubuntu-mate.community/t/aarch64-on-raspberry-pi-2-rev-1-2-3b-3b/16853/37 is currently what you have to do to use the armhf netboot installer on a pi 2/3B/3B+.  The debian-installer has no knowledge of the raspi2 kernel (you can't force it to install it), nor does raspi2 have any udebs."
1795870,2019-04-16 08:45:27 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/639375
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1795870,2019-04-06 05:39:34 UTC,"Reviewed:  https://review.openstack.org/650255
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=672a4328a97d6dae98cec208851198040530bd35
Submitter: Zuul
Branch:    stable/pike"
1795870,2019-04-05 10:39:02 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/650255"
1795870,2019-04-03 00:29:59 UTC,"Reviewed:  https://review.openstack.org/645282
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8b7955dade3e388ad030ce2291651cef72d55108
Submitter: Zuul
Branch:    stable/rocky"
1795870,2019-03-27 03:50:44 UTC,"Reviewed:  https://review.openstack.org/645283
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6f3620aa88feef9527f8c9599dec049a831b49fa
Submitter: Zuul
Branch:    stable/queens"
1795870,2019-03-21 17:50:47 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/645283"
1795870,2019-03-21 17:50:12 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/645282"
1795870,2019-03-14 14:37:30 UTC,"Change abandoned by Miguel Lavalle (<email address hidden>) on branch: master
Review: https://review.openstack.org/624271
Reason: Fix to bug was released in Neutron: https://review.openstack.org/#/c/636710/"
1795870,2019-03-14 14:33:27 UTC,"Change abandoned by Miguel Lavalle (<email address hidden>) on branch: master
Review: https://review.openstack.org/630778"
1795870,2019-03-13 21:00:35 UTC,"Reviewed:  https://review.openstack.org/636710
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=25c432a05a57f794dcbb4f17ce224d914c65e071
Submitter: Zuul
Branch:    master"
1795870,2019-02-26 15:59:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639375"
1795870,2019-01-28 01:39:39 UTC,Neutron server is losing contact with the L3 agent running in the controller node. One example is:
1795870,2019-01-14 22:02:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630778"
1795870,2019-01-07 20:36:41 UTC,Analyzing the failure of test_trunk_subport_lifecycle in http://logs.openstack.org/90/627990/1/check/neutron-tempest-plugin-dvr-multinode-scenario/c760de2/testr_results.html.gz i find the following:
1795870,2018-12-11 03:59:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624271"
1795870,2018-11-07 23:08:56 UTC,This is a successful recent execution: http://logs.openstack.org/93/615893/1/check/neutron-tempest-plugin-dvr-multinode-scenario/87e6767/job-output.txt.gz#_2018-11-07_14_22_29_545589
1795870,2018-10-30 16:16:28 UTC,"Removing the code line number from the query in the original filing and #4, so code changes don't render the query useless:"
1795870,2018-10-29 20:23:00 UTC,Using this slightly improved query to cover the 7 previous days:
1795870,2018-10-29 20:18:43 UTC,"As of October 29th, 0 hits over the past 7 days. I'll continue checking it"
1795870,2018-10-18 14:57:17 UTC,"For the time being, adding it also to the dvr backlog as well"
1795870,2018-10-16 21:13:51 UTC,"We got 33 hits over the past 7 days, out of which 29 are with job neutron-tempest-plugin-dvr-multinode-scenario. So it seems that we should focus on isolating the problem in that job."
1795870,2019-02-13 18:30:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636710"
1795875,2019-04-09 11:34:59 UTC,The error with wrong capitalization (wifiobj instead of wifiObj) in ui5/wifisetupdialog.py line 573 is still there in HPLIP 3.19.3.
1795875,2019-04-15 08:59:24 UTC,"Hi Manfred,"
1795875,2019-01-11 11:21:51 UTC,The error with wrong capitalization (wifiobj instead of wifiObj) in ui5/wifisetupdialog.py line 573 is still there in HPLIP 3.18.12.
1795875,2018-10-04 07:48:57 UTC,Please compare line 566 in hplip/ui4/wifisetupdialog.py and line 573 in hplip/ui5/wifisetupdialog.py
1795875,2018-10-19 10:24:37 UTC,"Tried to run hpli 3.18.9 and got:
[erik@Erik-PC Hplip]$ ./hplip-3.18.9.run
Creating directory hplip-3.18.9
Verifying archive integrity...Error in MD5 checksums: fc13708a58081673b8cfba6c573c9ad0 is different from 67be478c26ce5190f806f498b41204f3"
1795875,2018-10-04 06:47:44 UTC,"Hi,
We checked the wifisetupdialog.py file and it is ""wifiObj.getwifiotherdetails"" only. Please try on latest HPLIP driver 3.18.9.
We have verified wifi option with hp printers in 3.18.9 and it worked fine."
1795875,2018-10-19 14:12:45 UTC,"@Erik P. Olsen:
The message that you see has nothing to do with the problem that is covered by this bug message.
You should try re-downloading the hplip-3.18.9.run file."
1795886,2018-10-03 12:48:19 UTC,"*sigh* it must be duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/tp-smapi/+bug/1606447 :|"
1795888,2018-10-06 21:05:37 UTC,"I'm confused, what exactly is it that needs sponsoring?"
1795888,2019-02-12 08:48:19 UTC,"Unsure the glib behaviour change can be described as 'regression' and that they plan to change the behaviour, the test here should be adapted rather than commented out"
1795888,2018-10-08 09:47:41 UTC,"Ah, sorry, I am supposed to propose a merge, but there are some issues. Can you ask Trevinho to look at this?"
1795889,2019-09-03 19:12:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/679845"
1795889,2019-09-20 08:19:26 UTC,"Reviewed:  https://review.opendev.org/679845
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=db5e5a6829f30bc38defbd358c068aa5f4d9cae3
Submitter: Zuul
Branch:    master"
1795889,2018-10-12 19:52:40 UTC,Marking as Low; not gating for any release. Code cleanup only; no system impact
1795897,2018-10-16 22:11:14 UTC,I am ceasing to support searching for a solution to this probem.
1795897,2018-10-12 19:01:52 UTC,"> printer Hp laserjet M1132 MFP does not work
"
1795897,2018-10-08 16:27:55 UTC,I expect you just want to print and do not care how you get there?
1795897,2018-10-04 18:31:33 UTC,"Hi,"
1795897,2018-10-14 17:44:01 UTC,"Hello,"
1795897,2018-10-03 16:10:54 UTC,Can't you see it in the hp-doctor file
1795897,2018-10-03 15:59:59 UTC,"Hello
what is this plugin?
There where 2 files
hplip-3.18.9.run and plip-3.18.9-plugin.run in Xenal workt everything fine"
1795897,2018-10-03 15:57:15 UTC,Hello
1795897,2018-10-03 15:35:59 UTC,Did you install the proprietary plugin?
1795897,2018-10-04 06:53:19 UTC,"Hi,
The plugin files are installed properly as seen in the hp-doctor log file.
Can you share the hp-check command output for further analysis of this issue?"
1795903,2018-10-03 14:35:57 UTC,"This could be that debug logging was enabled and that was causing increased memory usage, otherwise, something is leaking memory."
1795903,2018-10-03 20:33:13 UTC,"Debug does leak memory, its documented in Django that enabling debug will store all the queries made in the DebugCursor."
1795903,2018-10-10 23:37:03 UTC,"Maybe we should consider a separate debugging option for logging all queries, so we can get MAAS debug logs without the potential clutter."
1795903,2018-10-10 23:37:17 UTC,(and memory leaks)
1795903,2019-09-20 07:39:06 UTC,I believe this issue is fixed in 2.6.
1795906,2018-10-25 13:51:39 UTC,"From a management perspective, we would prefer a Library Setting wherein we could choose a Pickup Library or Consortial queue position per org unit."
1795906,2019-01-22 16:54:08 UTC,"I've pushed a branch that converts Galen's global flag into a YAOUS to allow some more control over what ""resource sharing"" means for patron-visible hold queue position calculation.  From the commit message:"
1795906,2018-10-23 17:45:10 UTC,"We are testing this one of our test servers. In My Account, the queue position is indeed the Pickup Library position and not the consortial position. This is peferable. However, the number of copies is consortial."
1795906,2019-11-12 16:23:58 UTC,"I had a possible default-behavior thought for this bug.  If we lack a setting value, we could default to using the selection depth of the hold in question, which would take into account any soft or hard boundaries in play for the hold.  The drawback is that soft boundaries could make the queue position seem higher that it actually is, because it would further restrict the set of holds we consider peers in the situation where there was an extant copy at, say, a branch when the hold was placed, but that can be overridden by the proposed setting."
1795906,2018-10-09 12:38:31 UTC,"From our perspective, here are the options from least desirable to most desirable:"
1795906,2018-10-05 19:47:40 UTC,"Another caveat: restricting the hold queue position set to holds that match the pickup library can produce misleading results. For example, consider a library with two branches, A and B, whose patrons mostly use branch A for hold pickup.  Suppose a title has 100 holds, with the first 99 placed to be picked up at branch A and the last one to be picked up at branch B."
1795906,2018-10-03 15:19:00 UTC,"Even with the caveats, this is something we really need. The big issue for us right now is in the My Account portion of the OPAC where the only choice to display the consortial queue position. Since we do not yet resource share across the consortium, Pickup Library queue position would be preferable."
1795906,2018-10-03 14:23:55 UTC,Here be the branch: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1795906-queue-position-calculation-parity
1795906,2018-10-09 13:53:04 UTC,"Galen,"
1795911,2018-10-03 14:46:50 UTC,"Actually I did:
unset JAVA_CMD; find_java_runtime java8; echo $JAVA_CMD"
1795911,2018-10-03 14:47:56 UTC,because once set JAVA_CMD will be used regardless what java you'll want!
1795918,2018-11-08 17:17:14 UTC,"Reviewed:  https://review.openstack.org/608346
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=f0ee6692792a7a2ad7dafa7f9914251b9ba4f338
Submitter: Zuul
Branch:    master"
1795918,2019-03-13 18:00:46 UTC,"I've targeted some of the charms that I know are affected by this bug, but this bug needs a full audit of charms to determine which ones are definitely affected."
1795918,2018-10-04 20:48:43 UTC,We should look at all os-charms and evaluate for this impact.
1795918,2018-10-05 19:54:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608346"
1795919,2018-11-27 20:52:25 UTC,I've added the SRU Bug Template. Could you take it from here?
1795919,2020-05-22 05:53:06 UTC,"I'll add that the identified patch still applies to bionic's dovecot, so it doesn't appear that dovecot itself has already been fixed; if the issue is resolved the fix could be in the kernel or elsewhere."
1795919,2020-05-22 05:45:59 UTC,"This issue is not reproducing on bionic for me.  I've fleshed out the test case in the bug description with a more precise series of steps to set things up in a multipass VM, but the quota values I'm seeing appear to be correct.  I'm guessing there's either some additional configuration step, or the issue has been fixed elsewhere (maybe in the kernel?)"
1795919,2019-02-25 08:19:18 UTC,"Thank you - we have just upgraded our mail system from xenial to bionic, and unexpectedly hit this."
1795919,2019-02-19 20:59:46 UTC,"Yes, it's on our list to do soon."
1795919,2019-02-19 20:46:33 UTC,But should still be backported to bionic IMHO.
1795919,2019-02-19 17:52:10 UTC,https://github.com/dovecot/core/commit/39eefc53d06cf9790c6e3180a67b68e89eb71313#diff-e72982e5f369f46babc0f4b79df68878 is the upstream commit corresponding to the attached patch.
1795919,2018-11-27 15:26:04 UTC,Sorry I missed your previous comment. Please could you see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure and handle as much of that as you can? I'll be happy to help with with the rest. Please could you also verify that this bug is fixed in Ubuntu 18.10 (Cosmic)?
1795919,2018-10-08 18:06:56 UTC,"Are you able to test the attached patch?
I wasn't able to build the package on my current system.
Or I just don't know how to do it. With apt source dovecot-core I got the sources for dovecot 2.2.22, but the installed version is 2.2.33.2"
1795919,2018-10-30 21:25:49 UTC,"I was away for a while, but in the meantime the patched dovecot was running all the time without any issues.
I tried to replicate the service quota-status on a freshly installed ubuntu 16.04.5. I get the same result of DUNNO instead of Mailbox full. So no regression here."
1795919,2018-10-09 18:48:14 UTC,"The patch seems to work. Dovecot now displays the correct quota.
Also the command doveadm quota get -u user shows correct values.
What I'm unable to verify is the quota-status-service for postfix."
1795919,2018-10-08 20:21:48 UTC,"The attachment ""quota-fs.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1795919,2018-10-08 18:28:14 UTC,I uploaded a build to my experimental PPA at: https://launchpad.net/~racb/+archive/ubuntu/experimental/
1795919,2018-10-07 21:09:43 UTC,"On Sun, Oct 07, 2018 at 08:50:21PM -0000, Thomas Sommer wrote:

> Any chance the package is upgraded to version 2.3.3?
"
1795919,2018-10-07 20:50:21 UTC,"I think I found the problem when looking at the source which is related to glibc.
The fs quota plugin is not compatible with the shipped glibc."
1795919,2018-10-04 21:04:49 UTC,"Somebody already reported it to the dovecot mailing list:
https://www.dovecot.org/list/dovecot/2017-June/108423.html"
1795919,2018-10-04 15:05:41 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1795919,2018-11-26 21:06:46 UTC,~racb what do you think? Could you release a new version with the patch included?
1795919,2020-06-30 20:36:50 UTC,"I'm still unable to reproduce the originally reported problem on bionic, with a fresh container, following the steps I outlined in [Test Case]."
1795920,2019-12-13 00:25:51 UTC,"Reviewed:  https://review.opendev.org/674072
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8c7224172641c6194582ca4cf7ce11e907df50aa
Submitter: Zuul
Branch:    master"
1795920,2018-10-03 17:23:09 UTC,"looking at the code i belive this is because the feature was not fully implmetned
i will work with the core team to see if this can be reproposed for the stein release."
1795920,2018-10-04 16:49:12 UTC,Can we backport this feature in queens or pike release once it get successfully implemented on stein release?
1795920,2019-08-08 19:17:25 UTC,note that as this bug is actually a feature request we will tack its completion as part of this blueprint https://blueprints.launchpad.net/nova/+spec/sriov-numa-affinity-policy-via-flavor-and-image
1795920,2019-10-02 17:24:59 UTC,I had exact same issue last year when i was building openstack cloud with SR-IOV and this is what i did for workaround:
1795920,2019-10-02 17:38:16 UTC,"i am currenlty proposing https://blueprints.launchpad.net/nova/+spec/vm-scoped-sriov-numa-affinity
which is adressed by this spec https://review.opendev.org/#/c/683174/ and this code https://review.opendev.org/#/c/674072/ to adress this issue for Ussuri"
1795937,2019-08-03 16:40:35 UTC,"I've pushed this to master for inclusion in 3.4, along with a follow-up that makes the Angular client use it. Thanks, Geoff and Rogan!"
1795937,2018-10-03 16:35:31 UTC,"Adding a note that it would also be nice to update the logo used for the LP project, but I don't think I have the power to do so."
1795937,2019-04-25 22:24:31 UTC,"I've got a working branch here with the updated icon here:
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gsams/LP1795937_favicon_update"
1795937,2019-07-29 15:43:44 UTC,Signoff pushed to user/rogan/lp1795937_favicon
1795942,2018-10-03 20:51:34 UTC,https://gitlab.com/inkscape/inkscape/merge_requests/344
1795947,2019-10-01 23:12:06 UTC,This feels like a papercut but it also needs UX design. I'll relay this issue to my colleague who is looking into snap service management now.
1795947,2019-10-01 23:15:48 UTC,"We will be working on some UX changes to `snap services`, namely the changes mentioned at https://forum.snapcraft.io/t/how-to-manage-services-with-sockets-timers/7904/8?u=ijohnson"
1795950,2020-09-23 08:24:56 UTC,"Reviewed:  https://review.opendev.org/607680
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=922c2ed5adbfedba17324174369cfa2329e999ab
Submitter: Zuul
Branch:    master"
1795955,2018-10-04 04:40:12 UTC,Thanks for your report.
1795955,2018-10-04 07:50:08 UTC,"Yeah, Laney dropped in to IRC last night and said that it was probably the
same issue as he has a fix for.  Waiting for that to land."
1795957,2019-07-01 05:53:09 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/668353"
1795957,2019-07-11 09:25:07 UTC,This issue was fixed in the openstack/cinder 14.0.1 release.
1795957,2019-07-12 02:08:20 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/670428"
1795957,2019-07-19 10:24:39 UTC,"Reviewed:  https://review.opendev.org/670428
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9a1953a3bb78d85d6991b04ade68cb24e0c091b3
Submitter: Zuul
Branch:    stable/pike"
1795957,2019-07-08 15:52:07 UTC,"Reviewed:  https://review.opendev.org/668353
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=f55d3a6f61b3be3df4597504d26385ddb72f6b6b
Submitter: Zuul
Branch:    stable/queens"
1795957,2019-07-26 16:52:36 UTC,This issue was fixed in the openstack/cinder 12.0.8 release.
1795957,2019-09-27 09:04:16 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1795957,2019-06-18 16:05:54 UTC,"Reviewed:  https://review.opendev.org/665046
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=4fd1cdcf62bf83b57d7685d19fa06daa522c9a98
Submitter: Zuul
Branch:    stable/rocky"
1795957,2019-07-26 10:08:20 UTC,This issue was fixed in the openstack/cinder 13.0.6 release.
1795957,2019-06-06 23:11:38 UTC,"Reviewed:  https://review.opendev.org/662669
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=053c33cbfc2b4b72d9ca20f617e542452f98944f
Submitter: Zuul
Branch:    stable/stein"
1795957,2019-06-13 02:35:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/665046"
1795957,2019-05-29 16:20:00 UTC,"Reviewed:  https://review.opendev.org/659701
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=18fbbd1afe2b9151fe521d200b280ae4a0ef6202
Submitter: Zuul
Branch:    master"
1795957,2019-05-17 02:48:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659701"
1795957,2019-05-16 12:51:49 UTC,"Root caused, will submit fixes soon."
1795957,2019-05-16 10:59:59 UTC,I'm looking into the VNX failure cases.
1795957,2019-05-15 16:10:55 UTC,"Here's the patch that was merged to get py37 in as a non-voting job:
https://review.opendev.org/#/c/655612/"
1795957,2019-05-03 16:46:45 UTC,Here's the related gerrit review to get py37 unit tests enabled: https://review.opendev.org/#/c/617840/
1795957,2019-05-03 16:44:57 UTC,The taskflow bug received some feedback from Ben Nemec [1] and he thinks this is not a taskflow isue.
1795957,2018-11-14 13:36:20 UTC,May be an issue in taskflow: https://bugs.launchpad.net/taskflow/+bug/1780823
1795957,2019-06-03 02:42:56 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/662669"
1795961,2019-04-01 14:50:44 UTC,I've made the Save/Update Board command context-sensitive.
1795961,2019-04-03 10:22:31 UTC,"Fixed in revision ca25f352ce2c215cabf481c0d3720ab8388f0a37
https://git.launchpad.net/kicad/patch/?id=ca25f352ce2c215cabf481c0d3720ab8388f0a37"
1795961,2018-10-08 12:27:42 UTC,"BTW, I went ahead and implemented the title change.  I tried out a bunch of different formats, and ended up with basically an inversion of Seth's proposal:"
1795961,2018-10-03 23:03:43 UTC,@Jeff-
1795961,2018-10-03 20:09:31 UTC,"Hi Seth,"
1795967,2018-10-03 21:55:26 UTC,Cause by
1795967,2019-04-09 15:29:08 UTC,Another example:
1795967,2019-08-07 20:24:15 UTC,Another example:
1795967,2020-02-12 16:53:52 UTC,"These all appear to be working now.  However, there are still type failures from rtp testing.  I will open a separate ticket."
1795972,2019-05-20 19:11:46 UTC,I have created a branch for this:
1795972,2019-07-02 21:05:14 UTC,"Testing on the latest master, this works, though I'm wondering if the upgrade script should use oils_i18n_gettext() so it's nice and translatable."
1795972,2019-07-02 21:16:47 UTC,"I've pushed a sign-off branch here, making that recommended change: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1795972-apply-workstation-setting-desc-signoff"
1795972,2019-07-30 14:22:32 UTC,"Pushed to master for inclusion in 3.4. Thanks, Chris and Kyle!"
1795978,2018-11-01 18:56:17 UTC,+1
1795978,2018-11-01 17:53:42 UTC,I agree it would be more useful to have just the publisher name in that column.
1795978,2018-11-12 20:30:16 UTC,We are not seeing this behavior in 3.0.2 or 3.2. Just the publisher displays in both item status and record buckets
1795978,2018-11-01 15:53:02 UTC,Screen shots attached
1795978,2019-01-17 02:38:19 UTC,"Adding a follow up note here that may help troubleshooting. As Elaine said, here at PINES we were correctly only seeing the Publisher's name in this column. However we were also running into an issue where the Title and Author columns were coming in as all lower-case. When we applied this to fix that: https://bugs.launchpad.net/evergreen/+bug/1811689 our title and author are now capitalized correctly, but we're now getting the entire 260/264 field as reported by others above."
1795983,2018-10-15 19:54:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795985,2018-10-04 06:42:39 UTC,"Thank you, fix committed in https://git.launchpad.net/ltsp/commit/?id=a554125b16a08527390c90ab281c085c1ee334f0."
1795987,2018-10-06 09:12:17 UTC,Thanks for reporting.
1795987,2018-10-05 19:15:30 UTC,Spoke too soon. Now getting the following error with the attached image.
1795987,2018-10-05 17:17:17 UTC,I haven't ran into any errors so far in my tests today. Looks like it's all fixed.
1795987,2018-10-05 07:47:55 UTC,fixed - a test would be appreciated.
1795987,2018-10-04 19:01:48 UTC,"Ok, thanks
I guess I will have fixed it tomorrow"
1795987,2018-10-04 17:32:31 UTC,... and if I convert the .png image to .jpg it also does not work.
1795987,2018-10-04 17:23:45 UTC,The png-image you sent me is a gray image (only 1 color layer) opposed to rgb-png-images which have 3 color layers.
1795987,2018-10-04 15:59:44 UTC,"Yes, of course. Thank you for your quick response!"
1795987,2018-10-04 07:49:03 UTC,my mail: sikulix---at---outlook---dot---com
1795987,2018-10-04 07:47:31 UTC,Could you send me one of the offending .png files?
1795987,2018-10-04 17:47:28 UTC,I should have been more clear about the image conversion. I converted it via image software ImageMagick. Same can be done simply using Microsoft paint. Changing the extension type directly doesn't fix the issue. I attached the jpg variant of the above image.
1795989,2018-10-03 23:03:25 UTC,Thanks for this bug report.
1795989,2019-08-16 09:56:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795991,2018-12-11 18:02:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1795991,2019-07-22 04:14:50 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1795992,2019-03-22 03:45:59 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1795992,2018-12-19 10:01:23 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1795992,2018-12-09 05:07:57 UTC,"Reviewed:  https://review.openstack.org/620121
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4b5a21b4ebcd3272ffdf6b42937acf348c5b045f
Submitter: Zuul
Branch:    stable/rocky"
1795992,2018-11-21 23:51:23 UTC,"Reviewed:  https://review.openstack.org/607735
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5af632e9cab670cc25c2f627bb0d4c0a02258277
Submitter: Zuul
Branch:    master"
1795992,2018-10-03 23:07:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/607735"
1795992,2018-11-26 17:53:45 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620121"
1795997,2019-01-15 00:41:03 UTC,You should add domain config in keystone_authtoken section of cinder.conf like：
1795998,2018-10-07 00:07:10 UTC,"Added the output of `strace qterminal --drop`, followed by 19 repeated Ctrl+Alt+Z keystrokes, a Ctrl+C, and an exit. The 19th one was the failure. It should have hidden the dropdown, but did not."
1795998,2019-04-13 23:51:44 UTC,"I can confirm this behavior on a Dell Inspiron 7720.
Package: qterminal
Version: 0.9.0-3ubuntu3
Linux 4.18.0-17-generic x86_64"
1795999,2018-10-04 08:30:17 UTC,"It's true that ScalingStack hosts are slower now, but I'm not convinced that running python's tests on a bigger VM is a solution. This to me feels like the tests are buggy and/or racy, and they should probably better be fixed to deal with running in resource-constrained environments - you'd want to know that Python works well there anyway."
1796000,2020-04-09 10:21:33 UTC,"This got fixed 1y+ ago, so marking it accordingly."
1796003,2018-10-04 02:58:38 UTC,I put the bug and not the enhancement part in bug # 1796007
1796003,2018-10-04 02:32:01 UTC,"I undestand if there are no plans for adding a Containers tab,, I was just requesting this since I saw the new Pods tab.. but you know best regarding where containers should be displayed"
1796003,2019-09-19 12:06:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1796003,2018-10-04 02:27:53 UTC,"When I click on the DNS link for a Container, even though internally the container is a device (before it was renamed to Container), why is it these ""Containers"" are hidden from the devices tab?  I mean if it could be just shown there with a column (for all devices - parent) that would make it relatively easy to implement (I dont know the details, sorry for the assumption)"
1796003,2018-10-04 02:23:59 UTC,"Hi Luis,"
1796003,2018-10-04 02:29:17 UTC,I tried downloading the source code and trying to look into this.. but I have no idea where to look for this model/view to display the extra parent column and to disable the filter that doesn't show the container devices in the Devices tab page
1796004,2018-12-31 14:07:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796006,2018-10-04 21:23:04 UTC,"Yes, it would be nice to have this better represented in MAAS. I feel it's a risky change for this late in the 2.5 cycle."
1796025,2018-10-04 22:21:07 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1796025,2018-10-04 22:21:27 UTC,"Hello, I spotted this in your logs, I hope this helps you solve your issue:"
1796033,2020-05-04 09:06:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796034,2018-10-04 07:47:10 UTC,$ sudo lshw -C video
1796034,2018-10-04 07:53:40 UTC,"StacktraceTop:
 __GI_____strtoul_l_internal (nptr=0x8028f260 ""0"", endptr=0x8028f120, base=10, group=0, loc=0xb7f5bc40 <_nl_global_locale>) at strtol_l.c:252
 __GI___strtoul_internal (nptr=0x8028f260 ""0"", endptr=0x8028f120, base=10, group=0) at strtol.c:98
 _IO_vfscanf_internal (s=<optimized out>, format=<optimized out>, argptr=<optimized out>, errp=<optimized out>) at vfscanf.c:1864
 _IO_vsscanf (string=0x90a456b ""0"", format=0xb7f00e1b ""%hu%n:%hu%n:%hu%n"", args=0x8028f7c8 ""\362\367(\200\370\367(\200\364\367(\200\370\367(\200\366\367(\200\370\367(\200@\037o\266\001\325\250\200"") at iovsscanf.c:41
 __sscanf (s=0x90a456b ""0"", format=0xb7f00e1b ""%hu%n:%hu%n:%hu%n"") at sscanf.c:32"
1796034,2018-10-07 12:44:42 UTC,"This is very likely https://bugs.debian.org/910317 (""QtWebEngine in unstable is constantly crashing"")."
1796034,2021-01-31 06:30:42 UTC,"I assume that since https://bugs.debian.org/910317 is fixed for a long time, this issue is no more present either."
1796035,2018-10-04 22:23:02 UTC,"Hello, based on the following it looks a little like you've selected an EFI install but don't have the correct EFI partitioning. I hope this helps:"
1796035,2018-10-04 22:22:38 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1796042,2019-09-16 13:57:14 UTC,Migrated to https://github.com/widelands/widelands/issues/2120
1796043,2018-10-05 13:27:40 UTC,I can't reproduce this.  Are you sure it's not because your connectors are through-hole components?  (The .pos file only lists SMD components.)
1796043,2018-10-06 07:51:36 UTC,"Yeah, I checked that. It solved a few of the components. But the rest still
did not show up."
1796043,2018-10-06 13:13:34 UTC,"@Kristoffer, the fabrication attributes can be set in the footprint properties dialog."
1796043,2018-10-06 13:44:02 UTC,"I am well aware that the SMD, Virtual and through hole can be set there,
but what is the INSERT attribute... It does not show up in the properties
dialog."
1796043,2018-10-06 13:54:10 UTC,The documentation on this could potentially be improved.
1796043,2018-10-06 13:56:41 UTC,"It probably makes sense to include a few more optional outputs as well as more fabricators are asking for x/y for through hole components as well (Advanced Assembly, Screaming Circuits in US at least)"
1796043,2018-12-11 19:27:12 UTC,Version 5.1 is in feature freeze.  Moving to 6.0.0 milestone.
1796046,2018-10-09 10:49:15 UTC,This bug was fixed in the package inkscape - 0.92.3-4
1796046,2018-10-05 16:16:25 UTC,"committed to https://gitlab.com/inkscape/lib2geom/commit/f86669bdd13d467665c1b62104df7e66467ef37e , has yet to be pushed into inkscape repo"
1796046,2018-10-08 11:21:39 UTC,Andrej: why?  That bug link to Debian was perfectly fine.  It is synced up periodically by a cronjob that syncs the external bug trackers.
1796046,2018-10-08 11:32:32 UTC,"@mapreri: Hmm, it didn’t seem like it worked, that’s why I changed it to manual. Changing it back now."
1796046,2018-10-08 12:22:33 UTC,"Yes, It takes a while.  Several hours usually."
1796046,2019-03-06 12:09:07 UTC,I can't see this in Inkscape master. Does the fix still need to be pushed to Inkscape repo?
1796046,2019-03-15 08:07:14 UTC,Still an issue with 0.92.4.
1796046,2019-04-30 12:01:28 UTC,Fix committed to Inkscape master: https://gitlab.com/inkscape/inkscape/commit/4ebf9a1c96d7484529f3ed38fa1b4220e484a2c5
1796046,2019-05-01 00:17:25 UTC,Fix pushed to 0.92.x branch: https://gitlab.com/inkscape/inkscape/commit/5095c1b47bf125394c941e7db76aac445e3da993
1796047,2018-10-31 23:51:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796047,2018-10-31 23:52:49 UTC,http://standards.ieee.org/develop/regauth/oui28/mam.txt and http://standards.ieee.org/develop/regauth/oui36/oui36.txt both redirect to the new location.
1796047,2018-11-01 00:11:38 UTC,also need http://standards.ieee.org/regauth/oui/iab.txt replaced by http://standards-oui.ieee.org/iab/iab.txt
1796047,2018-11-01 00:14:24 UTC,"so new settings in the script should be:
ouiurl=""http://standards-oui.ieee.org/oui/oui.txt""
oui28url=""http://standards-oui.ieee.org/oui28/mam.txt""
oui36url=""http://standards-oui.ieee.org/oui36/oui36.txt""
iaburl=""http://standards-oui.ieee.org/iab/iab.txt"""
1796047,2018-11-01 04:19:18 UTC,"The attachment ""patch containing new urls for oui files"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1796047,2018-11-26 14:10:44 UTC,"the fix is in the 20180508.1 version of ths package which is only available in cosmic and folowing version.
why ?"
1796047,2019-04-08 15:33:09 UTC,Still an issue with ieee-data 20170531.1 in xenial.  Also generates an error from cron.monthly:
1796047,2019-05-01 08:52:40 UTC,Still an issue with ieee-data 20150531.1 in xenial.
1796047,2020-01-06 17:25:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796048,2019-01-08 15:46:32 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.openstack.org/608234"
1796048,2018-10-05 11:20:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608234"
1796048,2018-10-04 17:11:11 UTC,"Please investigate, but I'm pretty sure this is jenkins not quickstart."
1796052,2018-10-06 06:57:51 UTC,After HW restart the printer prints second page in duplex mode correctly.
1796052,2018-10-08 10:01:54 UTC,"Hi,"
1796055,2018-10-07 00:33:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796055,2018-10-07 00:37:32 UTC,Recent kernels that weren't booting:
1796056,2018-10-04 10:55:15 UTC,"StacktraceTop:
 glamor_egl_init (scrn=scrn@entry=0x55ba1510f610, fd=<optimized out>) at ../../../../../../glamor/glamor_egl.c:992
 try_enable_glamor (pScrn=0x55ba1510f610) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:769
 PreInit (pScrn=0x55ba1510f610, flags=<optimized out>) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:996
 InitOutput (pScreenInfo=pScreenInfo@entry=0x55ba131ee9c0 <screenInfo>, argc=argc@entry=12, argv=argv@entry=0x7ffc057d30e8) at ../../../../../../hw/xfree86/common/xf86Init.c:557
 dix_main (argc=12, argv=0x7ffc057d30e8, envp=<optimized out>) at ../../../../dix/main.c:193"
1796056,2018-10-04 16:51:26 UTC,"So this is the result of the new patch, but the bug is in either mesa or libglvnd. eglMakeCurrent doesn't seem to work if the server crashes like this."
1796056,2018-10-09 07:55:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796056,2018-10-10 02:22:59 UTC,Note that Xorg catches its own crashes. So the real crash (signo=11) starts at frame #7:
1796056,2018-10-10 02:24:58 UTC,Also tracking in https://errors.ubuntu.com/problem/80a261d57f137287204ff4f0f865866de3742560
1796056,2018-10-10 06:38:20 UTC,upstream has a patch to fail more gracefully in this case
1796056,2019-07-22 04:20:16 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1796057,2018-10-04 11:55:37 UTC,"Sorry, my name is not Linus :-)
I still believe in the ability of future mankind (O.-M.-G.! There is MAN in that! Must be wrong.) to deal with views and arguments they don't share in other ways than trying to ban them. Maybe they even learn again to have a laugh at them !!1! (well, I am an optimist).
I have enjoyed writing my report the way it is, otherwise there may not be a report at all. If you didn't find anything humorous in it you are probably a GNOME- and/or systemd developer. :-P
I apologize for the digress. Cheer up :-)"
1796057,2018-10-04 11:23:06 UTC,Can we have a less sarcastic tone? Thanks
1796071,2018-10-04 14:36:51 UTC,"I also get this error when I directly click on the last visible entry, so apparently missing entries are not correctly skipped…"
1796071,2018-10-05 07:15:45 UTC,"I don't exoect that this is new, so I'm retargeting the bug. It might autofix itself https://code.launchpad.net/~widelands-dev/widelands/campaignselect_box because the design will be changed from visible scenarios to completed scenarios."
1796071,2019-09-16 08:27:20 UTC,Migrated to https://github.com/widelands/widelands/issues/3329
1796074,2019-04-26 17:16:10 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1796074,2019-03-22 03:47:03 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1796074,2019-02-22 03:35:22 UTC,"Reviewed:  https://review.openstack.org/632480
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2c464b084006866cb31a289971a36b55eada2355
Submitter: Zuul
Branch:    stable/pike"
1796074,2019-01-22 14:44:17 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/632480"
1796074,2018-12-19 20:48:12 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1796074,2018-12-19 10:01:44 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1796074,2018-11-21 18:45:39 UTC,"Reviewed:  https://review.openstack.org/616551
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=346c8feb5837b33b3759c7faaba486715e32b685
Submitter: Zuul
Branch:    stable/queens"
1796074,2018-11-08 14:18:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/616551"
1796074,2018-11-01 17:58:51 UTC,"Reviewed:  https://review.openstack.org/608336
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=057a05dbbd7e4b9aea0aaa52f4bf6c1089f079be
Submitter: Zuul
Branch:    stable/rocky"
1796074,2018-10-05 15:38:45 UTC,"It helps with the immediate issue, but it also avoids wastefully sending duplicated IDs for neutron to filter upon. If/when we add chunking, we wouldn't want to be chunking duplicated IDs anyway."
1796074,2018-10-05 18:33:04 UTC,"Reviewed:  https://review.openstack.org/608040
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ab5fc6870260d3b3c3bce90a7123c17816bf0093
Submitter: Zuul
Branch:    master"
1796074,2018-10-05 15:21:29 UTC,"Relaying what I said in the nova change review, nova could chunk the requests to neutron if there are more than some limit of subnet IDs, we do that elsewhere:"
1796074,2018-10-05 14:17:30 UTC,"Thanks for confirming the result, Evgeny. According to the output of your 'nova-manage --version' command, you're running nova version 14.0.0 newton, which unfortunately has been EOL since 2017-10-25. So we won't be able to release the fix for newton. At best, we can backport it to 15.0.0 Ocata."
1796074,2018-10-05 12:00:22 UTC,"I made changes at /usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py and made restart services nova-api, nova-compute, nova-conductor, nova-scheduler and all works fine. New ip address successfully attach to instance. Thanks a lot for help, Melanie!!!"
1796074,2018-10-05 07:39:32 UTC,"Thanks for your prompt response. I describe this bug at python-neutronclient (https://bugs.launchpad.net/python-neutronclient/+bug/1794528), but unfortunately it stay without answers. At instance attached two different subnets. I will try to fix at nova/network/neutronv2/api.py and describe result here."
1796074,2018-10-04 17:43:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608040"
1796074,2018-10-04 17:37:46 UTC,"This issue can only be addressed in nova, so marking as Invalid for python-novaclient."
1796074,2018-10-04 16:14:02 UTC,"Thanks for providing a detailed bug report complete with log excerpts. From the log, we can see that the error you're hitting is coming from the python-neutronclient code:"
1796074,2018-10-05 18:47:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/608336"
1796097,2018-10-04 15:01:28 UTC,"[I am a developer of kdev-python, and a user and occasional committer to kdevelop]"
1796102,2018-10-04 15:17:37 UTC,It loads for me without error.
1796102,2018-10-08 15:56:33 UTC,As requested.
1796102,2018-10-08 16:52:50 UTC,Same versions I tested and found no issue. :/
1796102,2019-10-10 03:26:00 UTC,I have the exact same issue:
1796102,2019-10-17 18:28:28 UTC,"So I had Logged back out and then logged back in and then tried again to load the widget on the desktop, and now it is WORKING."
1796104,2019-07-04 16:04:36 UTC,"There is no fix here. This is not reproducible. We use the ""Invalid"" state for this case."
1796104,2019-07-03 13:24:37 UTC,Have not seen this issue for a while
1796104,2019-07-03 08:48:35 UTC,"I deploy image 20190623T233000Z and 20190626T013000Z for 10 times.
and don't find degraded status while unlocking controller-0."
1796104,2019-07-03 08:57:57 UTC,"thanks Long, I will mark it as ""fix released""."
1796104,2018-10-10 17:54:46 UTC,Marking as Low priority with no target release as there is no system impact.
1796104,2018-10-05 19:05:48 UTC,Setting importance to Low as there is no end system impact. The coredump will be reviewed to see if there is something obvious.
1796104,2019-03-19 07:58:17 UTC,"I deploy image 2018.10.10. on cengn
http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/bootimage.iso"
1796106,2018-10-11 13:14:05 UTC,Landed in edge (2.5) with the merge from 2.4 under https://github.com/juju/juju/pull/9299
1796106,2018-10-04 15:05:52 UTC,Thanks for the bug. Is this 2.4.3?
1796106,2018-10-04 15:23:26 UTC,"Ugh, yes indeed 2.4.3 on xenial"
1796106,2018-10-05 10:19:42 UTC,Did you do any manual initialisation of LXD on the new host?
1796106,2018-10-05 10:27:23 UTC,"Also, are there any firewalls in play here?"
1796106,2018-10-05 11:18:17 UTC,"Haven't performed any manual initialisation, no - besides installing the lxd/lxd-client packages.
The iptables rules present are those from lxd and libvirt:"
1796106,2018-10-05 13:28:31 UTC,I have managed to reproduce this.
1796106,2018-10-08 16:02:15 UTC,I have proposed https://github.com/juju/juju/pull/9287 to address this.
1796106,2018-10-09 13:50:53 UTC,Patch for 2.3: https://github.com/juju/juju/pull/9292
1796118,2019-01-10 10:25:10 UTC,"Hmm... the previous comment relates to the original question (about visibility locig), not to the changed subject line."
1796118,2018-10-06 20:16:32 UTC,(Sorry the previous post had a typo;
1796118,2019-02-09 18:32:38 UTC,I agree with @eelik regarding having zones in the items visibility list.  It is mostly a convenience thing since you can turn the zone visibility on and off on the other side of the window.
1796118,2019-01-10 10:19:05 UTC,Possible solution which doesn't break existing workflows or behavior:
1796118,2019-01-11 22:30:59 UTC,Looking like https://bugs.launchpad.net/kicad/+bug/1811355 also relative to this.
1796118,2018-10-07 20:23:42 UTC,I think that's an excellent summary for the first issue (showing/hiding zones).
1796118,2018-10-06 20:13:42 UTC,"Dear Seth,"
1796118,2018-10-07 01:20:34 UTC,It doesn't quite help; that only puts them in outline mode; I can't seem to hide them completely.
1796118,2018-10-06 20:49:02 UTC,You can change the zone display on the left hand side so that you don't see the copper fill.
1796118,2018-10-04 15:52:59 UTC,Attaching an image to show options.
1796118,2018-10-04 15:44:28 UTC,"Does unchecking the ""Tracks"" item not give you what you want?"
1796118,2018-10-07 03:30:15 UTC,"OK, that makes sense.  I think that this is a wishlist item for two separate things:"
1796119,2019-01-24 10:40:53 UTC,"just found another solution using pass (apt-get install pass (and some dependencies I'd rather not want to have installed, but still better than having to install gnome-keyring...) ). this will not store plain text credentials in your ~/.docker/config.json."
1796119,2019-01-24 09:33:57 UTC,"my workaround for now is renaming /usr/bin/docker-credential-secretservice - login works again, but I did not test what else it might break."
1796119,2019-01-09 20:01:35 UTC,FWIW.
1796119,2018-10-11 18:45:23 UTC,"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910822
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910823"
1796119,2019-01-09 20:54:10 UTC,"The whole idea that avoiding deb packaging fixes the problem is a serious problem. The culture of docker (containers, pip, snap, etc) seems to encourage abandoning sane packaging because it's too difficult, apparently."
1796119,2018-10-08 16:46:51 UTC,Should be golang-docker-credential-helpers?
1796119,2018-10-04 17:22:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796119,2018-10-04 15:37:30 UTC,https://github.com/docker/compose/issues/6023
1796119,2018-10-08 16:49:57 UTC,"Also, it is brought it due to python3-dockerpycreds"
1796124,2018-10-05 19:02:02 UTC,Assigning to Kevin Smith to triage
1796124,2018-10-10 17:52:13 UTC,Targeting stx.2019.03 as the issue is intermittent
1796124,2019-03-12 23:50:46 UTC,I will try to reproduce by setting a duplex system and perform a host-swact.
1796124,2019-05-08 13:00:10 UTC,"@peng, can you retest and see if this is still repro in latest build?"
1796124,2019-05-22 13:32:14 UTC,"just report see the bug in the latest ISO again, please reopen it."
1796124,2019-05-27 13:42:42 UTC,Issue was not able to reproduced.
1796127,2018-10-04 16:09:47 UTC,Here is the output of juju config nova-compute app
1796127,2018-10-04 16:01:44 UTC,I also attached a more than minimal version of the bundle to show the relation between the nova-compute charm and contrail-agent.
1796128,2019-07-13 00:36:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796130,2019-02-22 11:23:05 UTC,I took a look into these patches and noticed the following:
1796130,2018-10-09 15:53:40 UTC,"Description:
These missing patches are basically to improve Ubuntu kernel support for NVMe Surprise Removel/hot-plug of NVMe disks.
The patch list shared and formed above is from comparing the 4.18 HWE kernel that is already present in the -proposed apt repo.
We would like to have these included into the HWE kernel 4.18 of 18.04.2"
1796130,2020-04-06 14:37:09 UTC,4 of the 5 patches are in Focal.  The final patch is not
1796130,2018-10-04 19:56:58 UTC,Can we make this bug public?
1796130,2018-10-04 23:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1796135,2018-10-04 21:09:10 UTC,"Hi Seth,"
1796137,2020-06-18 14:44:50 UTC,I just used the focal cloud images on systems with no internet connectivity and snapd is adding at least 20 seconds of delay:
1796137,2018-10-04 16:50:23 UTC,"# ls -lh /var/lib/snapd/seed/snaps/
total 154M
-rw------- 1 root root 88M Oct  3 03:55 core_5548.snap
-rw------- 1 root root 67M Oct  3 03:55 lxd_8959.snap"
1796137,2020-06-01 16:30:58 UTC,"@stgraber,
The bug subject says ""Huge and slow"".  Shame on me to make 1 bug for 2 issues."
1796137,2020-06-01 16:01:01 UTC,I believe work in snapd was done to improve seeding so that this wouldn't be such an issue anymore.
1796137,2019-10-09 20:32:02 UTC,"I'm assign Pawel here as he has been working on some first-boot speed improvements for cloud images specifically. Also, since this was reported we now have `snap debug timings` command, which would be really useful to look at for slow first boot. For a first-boot, the first snap change is always seeding, so the output of `snap debug timings 1` would be useful in understanding what's still slow here."
1796137,2018-10-15 16:50:54 UTC,Subscribed the LXD team directly as we are obviously interested in this issue.
1796137,2018-10-11 09:38:57 UTC,Some work has been done to make connections after in https://github.com/snapcore/snapd/pull/5469 - this will be part of the upcoming 2.36 release which will most likely not be ready before cosmic though :/
1796137,2018-10-11 09:12:38 UTC,Thanks Dan! Thats really helpful. So from the log you provided it looks like the follow happend:
1796137,2018-10-10 14:10:37 UTC,"From a pre-LXD-seeding instance, the plot is at http://people.canonical.com/~dwatkins/1796137-before.svg and the `snap change` output is:"
1796137,2018-10-10 08:24:09 UTC,@Dan could we get the same data (plot + output of snap changes/tasks) for the image *before* lxd was seeded as well? This way we can more easily compare.
1796137,2018-10-09 21:18:14 UTC,Some more details about what's happening inside snapd:
1796137,2018-10-09 20:54:44 UTC,http://people.canonical.com/~dwatkins/1796137.svg is a `systemd-analyze plot` run on the instance with lxd.
1796137,2018-10-09 20:48:56 UTC,As requested on IRC:
1796137,2018-10-09 20:43:15 UTC,This is from a cosmic GCE instance _before_ the lxd snap was seeded (i.e. with just the google-cloud-sdk snap seeded):
1796137,2018-10-09 20:39:58 UTC,This is from a cosmic GCE instance _after_ the lxd snap has been seeded:
1796137,2018-10-09 20:29:10 UTC,"I've heard that even cloud images that were shipping snaps before the LXD inclusion are seeing a ~10s slowdown. If that's indeed the case, can we get a before/after for those with:"
1796137,2018-10-09 13:59:16 UTC,"Just as a point of reference, a single container booted on the same system I
showed the 38 second boot time before, seems to be down to 25 or so now.
Much better, but still not 10 seconds as it was."
1796137,2018-10-06 20:58:03 UTC,snapd has now migrated to the release pocket
1796137,2018-10-06 02:36:48 UTC,"The updated LXD snap should be available now in the stable channel.
The updated snapd is in cosmic-proposed and will hopefully migrate over the weekend."
1796137,2018-10-04 21:23:36 UTC,"is that blocking on NSS user lookup on gaining network connectivity? Also on a classic system i would have expected for /var/lib/extrausers/passwd to not be used, as the user should be either systemd's DynamicUser or system pre-allocated one."
1796137,2018-10-04 21:39:06 UTC,"I was able to SSH in before the service completed, so I don't think it's just a lack of network connectivity."
1796137,2018-10-04 21:46:51 UTC,Attaching the 'journalctl --boot' output after first boot of an AWS AMI from today (ubuntu/images-testing/hvm-ssd/ubuntu-cosmic-daily-amd64-server-20181002 - ami-03a19e7ba42cf1f55 in us-west-2) on an m5.large instance
1796137,2018-10-04 21:49:34 UTC,No output was returned for:
1796137,2018-10-04 22:19:00 UTC,Can you paste the content of /etc/nsswitch.conf from an affected instanced?
1796137,2018-10-05 00:15:07 UTC,"repeat boots could I guess be slow as a result of bug 1786165.
The snaps that are seeded are never removed. perhaps snapd doesn't realize (or has to re-check) to verify that they are not new."
1796137,2018-10-05 00:18:21 UTC,"@Stgraber,
I'm not sure why you wouldnt' have just done this yourself, so maybe I'm
missing your request."
1796137,2018-10-05 00:50:08 UTC,"To get the extrausers in the log above, you need this ""grep -q ""^passwd.*extrausers"" /etc/nsswitch.conf"" to be true, so I'm wondering what else may be different in this image's nsswitch and also how we ended up with extrausers in nsswitch but no extrausers file on disk."
1796137,2018-10-05 00:58:56 UTC,@stgraber:
1796137,2018-10-05 01:03:40 UTC,"As Scott showed in comment #9, /etc/nsswitch.conf in the images do not contain extrausers, but the core snap does."
1796137,2018-10-05 01:55:18 UTC,"Oh, I see what's going on, this piece of code used to be running AFTER we setup our custom /etc for the snap (which includes the real host nsswitch.conf) but now that it's moved over when we setup socket activation, this isn't true anymore."
1796137,2018-10-05 15:41:49 UTC,"I've updated the LXD snap, note that there's also a snapd issue which may be in play here as it's been known to needlessly delay boot with snaps using socket activation."
1796137,2018-10-05 16:10:56 UTC,"Bah. my comment 8 above is wrong.
I meant to reference bug 1796165 (seeded snaps never cleaned up.)
That could affect boot time of subsequent boots, if snapd is re-reading those preseed snaps."
1796137,2018-10-05 00:48:15 UTC,Because I suspect the GCE image may have a different looking one.
1796137,2018-10-04 21:17:23 UTC,"Our testing suggests that we're now seeing ~22s of first boot slowdown across all the cloud platforms.  We would expect to see some slowdown in when introducing a new pre-seeded snap (as there is more work for the system to do on first-boot), but that is excessive.  Furthermore, we are _also_ seeing slowdown on subsequent boots (when the cost of an extra snap should be negligible)."
1796140,2020-04-27 10:08:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796140,2020-04-27 10:13:57 UTC,"Same happens to me plus that I want to install a local(USB) printer but ubuntu only shows network printers which are added automatically and doesn't show usb printers connected locally..
Ubuntu use to be very good before with printing. but it's all messed up since the last 3 upgrades I'm having this same problem wich doesn't seem to be given attention."
1796147,2020-10-22 20:04:05 UTC,closing since the package has been removed from Ubuntu
1796147,2018-10-04 17:11:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796158,2019-05-14 12:35:40 UTC,"Fixed in revision 041c52c36959ba06b959a96a4153636e3c812a38
https://git.launchpad.net/kicad/patch/?id=041c52c36959ba06b959a96a4153636e3c812a38"
1796160,2019-09-19 14:47:42 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1796161,2018-10-12 14:02:30 UTC,"==> /var/log/maas/maas.log <==
2018-10-12T14:01:55.492322+00:00 autopkgtest maas.api: [info] lenovo-RD230-01-jenkins-master: Added new device"
1796162,2019-12-09 22:22:27 UTC,I remove the milestone and let it expire
1796162,2019-08-20 18:28:28 UTC,I will try and take another look when I get a chance.
1796162,2019-08-19 20:35:41 UTC,"I cannot confirm this using Mixxx 2.2.2 or Mixxx 2.3.0 alpha.
Can you? Maybe this was fixed in the meanwhile?"
1796162,2020-02-08 04:17:35 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1796162,2018-11-03 06:49:30 UTC,Do you have a mixxx log file from when this has happened? We print debugging info about why we decide to re-analyze a track.
1796162,2018-10-08 20:33:09 UTC,"That's alright, it hasn't really caused any lasting damage. I just went into the database directly and set the bpm_lock field to 1 for my whole library to prevent any changes. It makes sense to have it on anyway."
1796162,2018-10-06 06:32:48 UTC,"Yikes, that's not good! Sorry about this."
1796162,2018-11-03 18:29:31 UTC,"> If the BPM is 0.0 or the first beat is at position 0.0 then we override the preference setting and re-analyze anyway. If the first beat is 0.0 then the code is supposed to only change the grid offset.
"
1796165,2018-10-08 12:56:31 UTC,"Yes, somewhat by design. The seed directory was cooked to be read-only so that factory-resets can bring the device back into a pristine state."
1796168,2018-10-04 19:25:09 UTC,"I see Debian's up to 2.1.2 in Buster for what it's worth:
https://packages.debian.org/search?keywords=vagrant"
1796168,2018-11-05 17:16:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796168,2018-11-05 17:18:09 UTC,https://github.com/dotless-de/vagrant-vbguest/issues/292
1796168,2018-11-05 17:26:40 UTC,"I was able to resolve the issue installing ""vagrant plugin install vagrant-fsnotify"""
1796175,2018-10-04 19:40:46 UTC,Please also see:
1796175,2019-09-19 15:00:58 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1796177,2020-11-07 10:12:30 UTC,"I very much support this very important feature request.
Mixxx 2.3 can already import Rekordbox databases.
If Mixxx will also able to export to Rekordbox databases a single shared library between Mixxx and Rekordbox is possible which will be a big step forward by allowing to easily switch and sync between both programs."
1796180,2018-10-09 12:57:52 UTC,"Processing triggers for linux-image-4.15.0-36-generic (4.15.0-36.39) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-36-generic
/usr/share/initramfs-tools/hooks/framebuffer: 84: /usr/share/initramfs-tools/hooks/framebuffer: Cannot fork
/usr/sbin/mkinitramfs: 777: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/mkinitramfs: 181: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/update-initramfs: 165: /usr/sbin/update-initramfs: Cannot fork
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
dpkg: error processing package linux-image-4.15.0-36-generic (--configure):
 installed linux-image-4.15.0-36-generic package post-installation script subprocess returned error exit status 1"
1796183,2018-10-05 08:52:19 UTC,https://github.com/shimmerproject/elementary-xfce/issues/104
1796183,2018-10-05 14:32:55 UTC,I placed missing icons but still same result. Lock symbol is appearing when VPN is in connecting state.  BTW I don't have package network-manager-applet installed(E: Unable to locate package network-manager-applet).
1796183,2018-10-05 16:44:22 UTC,"The package name is network-manager-gnome, but it listed under network-manager-applet here on launchpad."
1796183,2018-10-05 17:12:16 UTC,Installing xubuntu-artwork package fixed the problem. Thanks :)
1796183,2019-02-20 18:19:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796185,2018-11-04 21:39:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796185,2018-11-04 21:42:04 UTC,"(evolution:29032): GLib-CRITICAL **: 22:29:26.663: g_strsplit: assertion 'string != NULL' failed
Speicherzugriffsfehler (Speicherabzug geschrieben)"
1796185,2019-01-24 19:39:41 UTC,"Please provide a full stacktrace in gdb via ""thread apply all bt full"" and make sure to have all debug packages installed."
1796185,2019-04-30 07:56:31 UTC,"The backtrace symbol suggests it's similar to bug #1730241 and have to do with the nvidia driver, are you using those as well? are they correctly installed/enabled?"
1796185,2019-04-30 11:50:45 UTC,Yes I'm using nvidia propritary driver but unlike bug #1730241 I have not disabled it. I only have one graphics card so it is very much in use and installed correctly.
1796185,2019-06-30 04:17:32 UTC,[Expired for evolution (Ubuntu) because there has been no activity for 60 days.]
1796187,2021-02-19 16:17:42 UTC,After the fix it takes
1796187,2021-02-19 16:24:11 UTC,*** Bug 139211 has been marked as a duplicate of this bug. ***
1796187,2018-10-05 11:41:49 UTC,"Note that I also tested libreoffice 6.0.6 that's installed by default in Ubuntu 18.04 (the deb packages, not the snap), and it took over 20 minutes to load the same document, so it's not a snap-specific problem."
1796187,2021-02-19 19:16:45 UTC,*** Bug 137938 has been marked as a duplicate of this bug. ***
1796187,2021-02-18 12:32:20 UTC,"László Németh committed a patch related to this issue.
It has been pushed to ""master"":"
1796187,2018-11-19 09:09:53 UTC,Cold be a duplicate of Bug 76260. Please compare console errors.
1796187,2018-10-05 18:47:43 UTC,"Description:
Trying to load the attached DOCX results in a hang. I force-quit after 20 minutes. The DOCX was created in MS Word (2013 I think), and is about 450 pages, thousands of footnotes, but no graphics AFAIK."
1796187,2018-10-05 18:50:15 UTC,"Thank you very much for the quick triage, Mr. Tilloy!  Much appreciated."
1796187,2018-10-05 11:40:32 UTC,"I can observe the issue in an up-to-date bionic amd64 VM. Opening the attached document and rendering it completely took 32 minutes. This is an insane amount of time to load a 516 pages document (153316 words, 927209 characters), but it eventually completed and once done the document can be navigated and edited just fine, as far as I can tell."
1796187,2018-10-05 19:22:05 UTC,"Confirmed on windows 7 x64 with Version: 6.0.6.2 (x64)
Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
CPU threads: 3; OS: Windows 6.1; UI render: default"
1796187,2018-10-05 18:49:36 UTC,"See also:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1796187"
1796187,2018-10-05 18:49:02 UTC,"Created attachment 145419
the docx that hangs Writer on opening."
1796194,2018-10-09 14:40:13 UTC,"Reviewed:  https://review.openstack.org/608277
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=b18b6a6d1d7dbf499563b728658f89fcb5c9b02c
Submitter: Zuul
Branch:    master"
1796194,2018-10-14 07:25:12 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/610342"
1796194,2018-11-26 18:59:53 UTC,"Reviewed:  https://review.openstack.org/610342
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=30b474787275e4e0a291e717f70ba700cc6fb812
Submitter: Zuul
Branch:    stable/rocky"
1796194,2019-01-07 14:39:19 UTC,This issue was fixed in the openstack/kolla 8.0.0.0b1 development milestone.
1796194,2019-01-07 14:47:30 UTC,This issue was fixed in the openstack/kolla 7.0.1 release.
1796195,2019-11-08 13:22:09 UTC,This is OBE as the heat tests have been migrated to zaza.  This was on amulet.
1796199,2019-02-01 19:24:42 UTC,Let's wait for core16 to be a thing first.
1796207,2019-04-03 22:31:52 UTC,This issue was fixed in the openstack/cinder-tempest-plugin 0.2.0 release.
1796207,2018-10-04 23:50:04 UTC,Patch is posted here: https://review.openstack.org/608103
1796210,2018-10-05 01:13:25 UTC,"StacktraceTop:
 g_settings_schema_get_value (schema=0x562733c9aed0, key=0x562733cfb940 ""disabled-plugins"") at ../../../../gio/gsettingsschema.c:973
 g_settings_schema_key_init (key=key@entry=0x7ffcac0adea0, schema=0x562733c9aed0, name=name@entry=0x562733cfb940 ""disabled-plugins"") at ../../../../gio/gsettingsschema.c:1252
 g_settings_get_value (settings=0x562733ce6f00, key=0x562733cfb940 ""disabled-plugins"") at ../../../../gio/gsettings.c:1203
 g_settings_get_strv (settings=<optimized out>, key=<optimized out>) at ../../../../gio/gsettings.c:2183
 ffi_call_unix64 () at ../src/x86/unix64.S:76"
1796210,2019-10-26 06:42:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796211,2018-10-05 01:42:39 UTC,"StacktraceTop:
 g_themed_icon_equal (icon1=0x7fa59408e520, icon2=0x55e27dde3950) at ../../../../gio/gthemedicon.c:549
 st_icon_set_gicon (icon=0x55e27d58a190, gicon=0x55e27dde3950) at ../src/st/st-icon.c:549
 object_set_property (nqueue=0x55e27bdd4090, value=0x7ffe28e9b768, pspec=0x55e27afcab40, object=0x55e27d58a190) at ../../../../gobject/gobject.c:1447
 g_object_setv (object=0x55e27d58a190, n_properties=<optimized out>, names=<optimized out>, values=<optimized out>) at ../../../../gobject/gobject.c:2253
 g_object_set_property (object=<optimized out>, property_name=<optimized out>, value=<optimized out>) at ../../../../gobject/gobject.c:2537"
1796211,2018-10-05 02:40:21 UTC,I can't find any other reports of this crash. Can you please try disabling your extensions:
1796211,2018-10-05 02:42:10 UTC,"Your JournalErrors.txt file seems to show a very large number of crashes in the ""gsconnect"" extension. But still, please try disabling all the extensions."
1796211,2018-10-06 13:53:26 UTC,"i disabling all extensions and see ""journalctl -ex"" log. It seems to be solved...
I do not see an error at all"
1796211,2018-10-08 02:02:18 UTC,OK. Please try re-enabling all extensions EXCEPT for gsconnect.
1796211,2018-10-09 01:59:39 UTC,ok. i re-enablin all extension except for gsconnect. everything look good.
1796212,2019-07-03 01:11:18 UTC,This was fixed with the following upload:
1796228,2018-10-30 17:19:18 UTC,"Created attachment 279255
iwlwifi scheduling while atomic, dmesg output"
1796228,2018-10-13 06:33:40 UTC,*** Bug 201355 has been marked as a duplicate of this bug. ***
1796228,2018-10-13 06:33:19 UTC,*** Bug 201297 has been marked as a duplicate of this bug. ***
1796228,2018-10-13 06:19:38 UTC,"Thanks, Johannes! I'll pull your fix into our core release soon, during my next round of merging back from upstream."
1796228,2018-10-12 11:03:29 UTC,"(In reply to Haochen Tong from comment #4)

> As a side note, the scripts/uninstall.sh in backport-iwlwifi does not
> support xz compression for kernel modules.
"
1796228,2018-10-12 11:00:48 UTC,"Thanks for the initial analysis, we'll try to find if there's any patch that fixes it in core39."
1796228,2018-10-13 15:38:39 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=200991#c7
1796228,2018-10-08 15:34:18 UTC,Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
1796228,2018-10-05 03:30:10 UTC,This change was made by a bot.
1796228,2018-10-01 12:37:45 UTC,"As a side note, the scripts/uninstall.sh in backport-iwlwifi does not support xz compression for kernel modules."
1796228,2018-10-01 12:32:24 UTC,Here's some test result:
1796228,2018-09-28 13:23:20 UTC,"No idea, but I'll give a try with LTS 4.14.72."
1796228,2018-09-28 10:49:04 UTC,Do you have any idea if this was happening before 4.18?
1796228,2018-09-01 18:03:15 UTC,"Created attachment 278231
relevant lines from journalctl -b"
1796228,2018-10-09 17:55:53 UTC,"https://bugzilla.kernel.org/show_bug.cgi?id=201297
--
Cristian Aravena Romero (caravena)"
1796229,2018-10-05 04:29:05 UTC,"Modify user and password，Then the installation is normal：
 /usr/share/kolla-ansible/ansible/roles/grafana/tasks/post_config.yml"
1796237,2018-10-07 15:06:40 UTC,rm -rf ~/.cache/font-manager
1796237,2018-10-08 05:31:01 UTC,Worked!
1796237,2018-10-09 21:31:13 UTC,Your welcome.
1796240,2020-11-16 08:42:08 UTC,Zero crashes after 18.10 so consider it fixed.
1796252,2019-07-22 04:03:23 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1796252,2019-05-19 16:54:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796252,2019-05-19 16:56:06 UTC,"Also affects Gnome on Ubuntu 19.04, at least under Wayland. Line number is a bit different (269 instead of 253), but the rest is the same. Crashes the session."
1796252,2019-07-22 04:03:15 UTC,The error report for this bug:
1796260,2018-10-16 15:11:16 UTC,"and when it doesn't like HD(5,MBR...) entry and has no other entries it tries to ""autogenerate"" the entry and injects it into bootorder.... and then boot loops.... and then the entries pile up"
1796260,2020-06-03 02:04:16 UTC,This bug was fixed in the package ubiquity - 20.10.2
1796260,2020-05-28 18:12:25 UTC,This bug was fixed in the package partman-partitioning - 120ubuntu3
1796260,2020-05-28 16:42:38 UTC,"well, maybe in bios mode we should install as gpt by default, on fresh disks."
1796260,2019-07-18 02:56:49 UTC,"So subiquity/curtin sort of tiptoe around this bug currently. Curtin's data model uses the same field (""flag"") to indicate that a partition is an ESP (set flag to ""boot"") and that a partition is a logical partition (set flag to ""logical"")."
1796260,2018-10-16 19:21:08 UTC,This bug was fixed in the package partman-auto - 134ubuntu10
1796260,2018-10-16 17:51:27 UTC,"This is an efivar bug, that's what will generate file paths for efibootmgr, specifically in efi_va_generate_file_device_path_from_esp() and the code it calls."
1796260,2018-10-16 15:17:30 UTC,"So.... i don't think efibootmgr generates ""right"" entries for ESP on extended mbr partition."
1796260,2018-10-16 14:42:24 UTC,"So we have zeroed these out. And we have now done bios-mbr install, and then side-by-side install in uefi mode with mok util."
1796260,2018-10-11 05:02:01 UTC,On this machine there is a boot setting to select the boot mode UEFI or Legacy
1796260,2018-10-15 18:05:58 UTC,"@Dimitri, what do you mean by ""Clearing all the boot entries"" ? I didn't do anything but installing this machine with ubuntu."
1796260,2018-10-11 05:01:26 UTC,"This is on bare metal, DELL Inspiron 13"
1796260,2018-10-10 19:54:06 UTC,"Is this running on real hardware or in a virtual machine? If it's on metal, what kind of hardware?"
1796260,2018-10-11 06:14:32 UTC,"I have tried and failed to reproduce this in a VM.  After installing the second Ubuntu in UEFI mode, I wind up without any settings persisting in the nvram store at all, so I just get dropped to the ovmf shell.  That is a bug in my KVM setup, but it makes it rather difficult to reproduce the problem."
1796260,2018-10-15 20:40:33 UTC,"Jean-Baptiste, your efibootmgr -v output shows no fewer than 18 boot entries for Ubuntu.  That didn't happen as a result of a single install of Ubuntu (.... I hope).  I think Dimitri's suggestion is that you zero these out, either with efibootmgr or from the firmware UI, to see if the system is less confused then and able to boot after install."
1796260,2018-10-15 08:07:27 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1796260,2018-10-15 16:33:12 UTC,@jibel
1796260,2018-10-15 17:10:10 UTC,"with persistent uefi vars, it rebooted into uefi system fine."
1796260,2018-10-11 09:03:07 UTC,output of efibootmgr -v:
1796262,2020-09-16 01:33:15 UTC,A button in the BPM tab of the file Properties dialog to round the detected or tapped BPM would be handy.
1796262,2019-01-20 17:18:51 UTC,Somewhat-related PR: https://github.com/mixxxdj/mixxx/pull/2001
1796262,2018-12-16 20:45:02 UTC,There's some discussion about bpm sorting/rounding on the Mixxx Zulip: https://mixxx.zulipchat.com/#narrow/stream/109122-general/topic/BPM.20sorting
1796262,2018-12-16 20:17:26 UTC,"Is it really a point to have BPM counted in a non integer number ?
In order to mix we will use the waveforms or our ears. We only need to know how many bits per minute the track is, just to find compatible tracks easily. A number with 4 decimal digits makes it difficult. I have a huge database of about 80000 tracks and only one out of fifteen (or even more than 15) has an integer BPM. I think it is pointless.
I have to agree with xerus for an option to round them if I would like. A checkbox in preferences ""Integer BPM"" or something similar would be the best solution for me."
1796262,2018-12-16 19:31:39 UTC,"Yeah, I think there's value in implementing this. I am still getting to grips with C++ and Qt so I can't say I'll personally be working on it, but it deserves attention."
1796262,2018-12-16 16:33:22 UTC,"Maybe I did have fast analysis on when scanning this. But regardless, could this be implemented as an option?"
1796262,2018-10-22 19:22:15 UTC,I get 90.036 if I enable the Fast Analysis option with the (QM) Tempo and Beat Tracker.
1796262,2018-10-21 19:11:14 UTC,I'm on Mac/OS X for the record.
1796262,2018-10-21 19:10:24 UTC,"Weird, if I run build 2.2-r6566 and analyze that track it just comes out as 180 (as in exactly 180). Same on the current release or most recent master build."
1796262,2018-10-20 20:45:02 UTC,"Which version of Mixxx are you running, and what OS? The Pegboard Nerds and Rootkit tracks are both coming out at exact BPMs for me."
1796262,2018-10-20 13:04:21 UTC,"I have attached a zip containing 3 examples. I ran them through the scanner multiple times and the result was always a broken number, but very very close to the actual one, which is simply the value rounded to the nearest whole."
1796262,2018-10-19 19:58:06 UTC,"I used to have issues with the bpm detection always being ever so slightly out. It happened a lot when I had a collection that was mostly vinyl rips, though I think it would sometimes get things wrong that were genuinely at a whole bpm too. I very rarely encounter it these days, but I reckon I could easily run some bits through the analyzer again and provide some example tracks from the results."
1796262,2018-10-06 16:45:43 UTC,"Do you have a significant sample song?
A YouTube link would be nice."
1796262,2018-10-06 14:35:26 UTC,"That's why it should be an option. Even when the BPM is not a whole number, the analyser probably gets them wrong with its weird 4-digit number, and a lot more often the nearest whole number is simply correct.
This is not a ""visual and usability issue"", it is only about the scanner."
1796262,2018-10-05 16:20:31 UTC,Thank you for the bug.
1796262,2018-10-21 14:48:36 UTC,"I'm currently running 2.2.0-beta (build 2.2 r6578) on Kubuntu. Have you tried removing the BPMs and re-scanning them? The Pegboard Nerds one always results in 90,02829268 for me, btw I have set the BPM range between 90 to 180."
1796262,2018-10-20 22:39:52 UTC,"A while back when my library contained a lot of vinyl rips I went through and checked that the BPM values were right to around 1/1,000th of a BPM - ie accurate enough that over a long transition between two tracks I could rely purely on bpm sync. I checked around 400 tracks this way."
1796263,2020-10-14 06:58:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796269,2018-10-05 11:56:21 UTC,What happens if you set a binding to coordinator-memcached relation like coordinator-memcached=internal-space?
1796274,2018-10-05 12:17:00 UTC,"Odd, it crashes in std::stringstream::str()"
1796277,2019-01-16 09:32:42 UTC,"I discussed this with Michał in person and have some better understanding. Based on their goal, the generic kernel may be the best choice and not the linux-azure kernel."
1796284,2018-10-05 19:56:05 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1796292,2019-08-27 13:15:15 UTC,This bug was fixed in the package linux - 5.2.0-13.14
1796292,2019-06-03 18:58:17 UTC,Is there an estimate on getting this package in bionic-updates please?
1796292,2019-06-03 19:23:03 UTC,"On Mon, Jun 3, 2019 at 2:05 PM Andrey Grebennikov <
<email address hidden>> wrote:"
1796292,2019-07-01 15:43:17 UTC,Canonical kernel team has this item queued in the hotlist to work on.  I am assigning to myself to accelerate work
1796292,2019-07-03 16:01:03 UTC,From a kernel perspective this big slowness on shutting down a bcache volume might be caused by a locking / race condition issue. If I read correctly this problem has been reproduced in bionic (and in xenial we even got a kernel oops - it looks like caused by a NULL pointer dereference). I would try to address these issues separately.
1796292,2019-07-03 17:26:36 UTC,"This is difficult for us to test in our lab because we are using MAAS, and
we hit this during MAAS deployments of nodes, so we would need MAAS images
built with these kernels. Additionally, this doesn't reproduce every time,
it is maybe 1/4 test runs. It may be best to find a way to reproduce this
outside of MAAS."
1796292,2019-07-03 23:52:32 UTC,I've setup our integration test that runs the the CDO-QA bcache/ceph setup.
1796292,2019-07-03 23:53:55 UTC,"Without the patch, I can reproduce the hang fairly frequently, in one or two loops, which fails in this way:"
1796292,2019-07-04 12:53:35 UTC,"Thanks tons for the tests Ryan! Well, at least the hung task timeout trace is different, so we're making some progress."
1796292,2019-07-05 08:45:14 UTC,"Good news! I've been able to reproduce the hung task in bch_bucket_alloc() issue locally, using the test case from bug 1784665. I think we're hitting the same problem now. I'll do more tests and will keep you updated."
1796292,2019-07-05 08:45:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796292,2019-07-10 09:49:37 UTC,"Hi Ryan, I've uploaded a new test kernel:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-54.58+lp1796292/"
1796292,2019-07-10 14:07:11 UTC,"... and, just in case, I've uploaded also a test kernel based on the latest bionic's master-next + a bunch of extra bcache fixes:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-55.60+lp1796292+1/"
1796292,2019-07-10 22:27:31 UTC,"Andrea,  thanks for the updated kernels."
1796292,2019-07-10 23:58:47 UTC,The newer kernel went about 16 runs and then popped this:
1796292,2019-07-29 19:11:36 UTC,Escalated to Field Critical as it now happens often enough to block our ability to test proposed product releases. We are unable to test openstack-next at the moment because our test runs fail behind this bug.
1796292,2019-08-01 09:04:42 UTC,"I've uploaded a new test kernel based on the latest bionic kernel from master-next:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292/"
1796292,2019-08-01 12:12:27 UTC,"ubuntu@ubuntu:~$ uname -r
4.15.0-56-generic
ubuntu@ubuntu:~$ cat /proc/version
Linux version 4.15.0-56-generic (arighi@kathleen) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #62~lp1796292 SMP Thu Aug 1 07:45:21 UTC 2019"
1796292,2019-08-15 20:16:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1796292,2019-08-15 15:27:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1796292,2019-08-06 00:30:20 UTC,"On Mon, Aug 5, 2019 at 1:19 PM Ryan Harper <email address hidden>
wrote:"
1796292,2019-08-05 18:19:32 UTC,"On Mon, Aug 5, 2019 at 8:01 AM Andrea Righi <email address hidden>
wrote:"
1796292,2019-08-05 12:51:02 UTC,"Ryan, I've uploaded a new test kernel with the fix mentioned in the comment before:"
1796292,2019-08-05 08:48:51 UTC,Some additional info about the deadlock:
1796292,2019-09-02 12:26:03 UTC,This bug was fixed in the package linux - 4.15.0-60.67
1796292,2019-08-02 17:26:15 UTC,After some help from Ryan (on IRC) I've been able to run the last reproducer script and trigger the same trace. Now I should be able to collect all the information that I need and hopefully post a new test kernel (fixed for real...) soon.
1796292,2019-08-02 17:14:34 UTC,Trying the first kernel without the change event sauce also fails:
1796292,2019-08-02 14:35:33 UTC,"I tried the +3 kernel first, and I got 3 installs and then this hang:"
1796292,2019-08-02 13:50:17 UTC,"Ryan, unfortunately the last reproducer script is giving me a lot of errors and I'm still trying to figure out how to make it run to the end (or at least to a point where it's start to run some bcache commands)."
1796292,2019-08-01 15:17:13 UTC,Reproducer script
1796292,2019-08-01 14:52:42 UTC,"On Thu, Aug 1, 2019 at 10:15 AM Andrea Righi <email address hidden>
wrote:"
1796292,2019-08-01 14:10:24 UTC,"Thanks Ryan, this is very interesting:"
1796292,2019-05-22 14:21:47 UTC,"This bug is believed to be fixed in curtin in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1796292,2019-05-14 14:04:39 UTC,"This script *should* trigger the issue on Bionic GA: https://pastebin.ubuntu.com/p/WdKGbMWnM6/
Try it with both GA and HWE bionic, the commit on HWE should trigger up."
1796292,2019-01-23 12:35:32 UTC,"sub'd to field high as we've hit this 4 times in CI, and it seems related to bug 1808231 and bug 1811117, and we don't have a workaround."
1796292,2019-05-13 15:50:33 UTC,@jhobbs
1796292,2019-03-06 00:40:04 UTC,"Hi,"
1796292,2019-02-12 16:29:20 UTC,We hit another failure that could possibly be this. http://paste.ubuntu.com/p/pvDmP2B8Q2/
1796292,2019-01-28 16:41:59 UTC,"We've had a number of successful test runs with this now, and no more failures, so I think it's fixed."
1796292,2019-01-24 18:54:32 UTC,@jhobbs
1796292,2019-01-24 06:35:11 UTC,"Yes, we do turn on curtin_verbose"
1796292,2019-01-23 16:19:07 UTC,"Do you turn on curtin_verbose during the QA runs?  If not, can we ensure we get a reproduce with the curtin_verbose enabled?"
1796292,2019-03-15 16:04:15 UTC,I've attached curtin-logs from a failure. This was with curtin from proposed - 18.2-10-g7afd77fa-0ubuntu1~18.04.1
1796292,2019-01-17 19:01:22 UTC,"On Thu, Jan 17, 2019 at 12:15 PM John George <email address hidden>
wrote:"
1796292,2018-12-18 15:21:15 UTC,Thank you for the config and an install log.
1796292,2018-12-18 08:14:27 UTC,"Hi Ryan,"
1796292,2018-12-17 15:24:54 UTC,"Thank for the log.  If it's reproducible, can you re-run the deployment
with curtin verbosity set ?"
1796292,2018-12-14 22:47:50 UTC,It looks like we have this reproduced:
1796292,2018-12-12 23:11:33 UTC,"Yeah, I think it make sense for shutdown_bcache to adjust.  Currently it does this:"
1796292,2018-11-26 16:18:33 UTC,Can we get a console output of a failure ? or a curtin log.
1796292,2019-01-17 18:03:50 UTC,"@Ryan we're hitting this issue during solutions QA test runs. The latest recreate is here:
https://solutions.qa.canonical.com/#/qa/testRun/4b4c04da-0178-4bcd-8a4b-7da81f3ed6bc"
1796292,2019-03-15 16:23:02 UTC,Thanks.
1796292,2019-01-23 09:50:27 UTC,Here is another reproduction:
1796292,2019-03-21 20:26:12 UTC,"I've seen this failure in another scenario, tracked in this private bug (LP: #1815018); so I'm copying in the portion that's relevant here."
1796292,2019-03-15 16:48:12 UTC,There are logs of that creation here:
1796292,2019-05-09 14:02:43 UTC,Xenial GA kernel bcache unregister oops:
1796292,2019-05-09 13:59:11 UTC,"On Wed, May 8, 2019 at 11:55 PM Trent Lloyd <email address hidden>
wrote:"
1796292,2019-05-09 04:45:35 UTC,I have been running into this (curtin 18.1-17-gae48e86f-0ubuntu1~16.04.1)
1796292,2019-05-06 22:23:27 UTC,This occurrs on a target machine during maas install. Apport is not collected in this case.
1796292,2019-05-01 18:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1796292,2019-05-01 17:58:57 UTC,Adding affects linux package
1796292,2019-04-26 17:10:45 UTC,Ryan Harper <email address hidden> writes:
1796292,2019-05-14 12:16:09 UTC,I was looking into kernel commits and I came across this: https://github.com/torvalds/linux/commit/fadd94e05c02afec7b70b0b14915624f1782f578
1796292,2019-04-25 15:38:58 UTC,"err, ./10.244.40.32/var/log/maas/rsyslog/spearow/2019-04-25/messages"
1796292,2019-04-25 15:36:58 UTC,"In comment 24, the failure was on spearow; unpack the logs for 10.244.40.32 and it's at:"
1796292,2019-04-25 15:11:54 UTC,we hit this issue with the version from the curtin-dev ppa - so it is apparently not yet resolved:
1796292,2019-04-09 14:21:21 UTC,I've copied what's in disco into this ppa; so it won't change on you while testing.
1796292,2019-04-08 20:32:50 UTC,"Jason,"
1796292,2019-04-03 18:15:51 UTC,"This bug is fixed with commit 36351dea to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=36351dea"
1796292,2019-04-25 20:26:29 UTC,"After looking at the logs, I believe curtin is doing all that it can to shut down the bcache device."
1796304,2018-10-05 14:08:10 UTC,"Yes, support for Octavia is on the roadmap."
1796304,2018-10-15 16:16:55 UTC,timeline?
1796304,2018-12-06 15:36:03 UTC,"The charm and its dependencies are commited to the master branch and is previewable at the following links:
https://jujucharms.com/u/openstack-charmers-next/octavia/7
https://github.com/openstack-charmers/openstack-bundles/pull/108/
https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-octavia.html"
1796316,2020-03-18 15:12:14 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1796316,2018-10-09 18:12:10 UTC,Support for color emoji requires recent libraries. See:
1796316,2018-10-09 10:51:57 UTC,"Here's the result of running the pango-view command — it's not a Ü, it's just a very long empty space, which is still weird."
1796316,2018-10-06 07:31:07 UTC,"The ""❌"" looks correct in the .svg file (attached)."
1796316,2018-10-05 21:44:49 UTC,"This actually renders properly for me in Inkscape 0.92.3 (2405546, 2018-03-11) on Windows 10, see attached screenshot."
1796316,2018-10-05 14:35:03 UTC,Not sure how well we are supposed to handle color emojis ?
1796316,2018-10-08 17:07:05 UTC,I can confirm the characters in the SVG file are properly UTF-8 encoded and render properly on my system.
1796317,2018-10-05 19:56:57 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1796324,2017-11-17 22:58:40 UTC,"Forwarded from #882029. This function is found in format.h but it not exported in map-file and thus unavailable on most (all?) linux systems. I don't know if the function is supposed to be exported, or maybe it should be private instead."
1796324,2017-12-12 04:16:52 UTC,"I'm 99.3% certain that it's supposed to be exported. It's documented, and internally it's only used in format.c, so if it isn't meant to be exported, then the declaration should be removed from format.h since it's not needed."
1796324,2017-12-12 05:03:09 UTC,The patch is now in master.
1796324,2018-10-08 02:07:52 UTC,"Thanks for the detailed bug report. It looks like the fix first appeared in PulseAudio version 12.0. So ""Fix Released"" for Ubuntu 18.10 and nominated 18.04 to receive a fix."
1796324,2019-09-17 20:14:34 UTC,I am still experiencing this on latest Bionic. So apparently the fix is not really released?
1796344,2018-10-24 16:49:20 UTC,This has been fixed and merged into develop.
1796344,2018-10-05 15:33:08 UTC,"@knguyen93 This demonstrates the issue: https://pastebin.canonical.com/p/yKPnVmrXh8/. Instead of ""ERROR ""redis/0"" is not a local charm"", we'd want Juju to fire the collect-metrics hook."
1796344,2018-10-05 15:10:41 UTC,Need to remove the restriction that collect-metrics only works on a locally-deployed charm.
1796350,2018-10-15 12:38:24 UTC,This bug was fixed in the package linux-azure - 4.18.0-1003.3
1796350,2018-10-15 12:54:57 UTC,The package has been published and the bug is being set to Fix Released
1796354,2018-10-05 15:28:27 UTC,"This was the same issue that was discussed in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/78584 and it was fixed in the following versions of Evince, but now it has reappeard (at least to me)"
1796354,2020-07-01 20:27:12 UTC,"Thank you for your bug report, that's an upstream choice and you should rather open a ticket on gitlab.gnome.org to discuss changing the behaviour with the people writting the software"
1796362,2019-03-25 10:58:50 UTC,Without apparmor snapd will work correctly but snaps will be mostly unconfined. I'm not sure if people should be using such an environment but perhaps that's what they want.
1796362,2018-10-16 09:54:20 UTC,"Passing the kernel argument apparmor=0 in the boot loader,
did allowed me to launch them."
1796362,2018-10-16 09:38:13 UTC,"gnome-calculator, gnome-system-monitor and gnome-logs_gnome-logs are also affected and impossible to launch on the livecd."
1796362,2018-10-09 18:05:38 UTC,The apparmor unit is intentionally not active on the live cd because most profiles need to be changed to operate in that state. This has been the case ever since apparmor was introduced in the distribution.
1796362,2018-10-09 17:55:39 UTC,"Ah, interesting! You can show the definition of unit with ""systemctl cat apparmor.service"" but I think what is happening is that on the live CD apparmor is not being started. It seems that /rofs/etc/apparmor.d is present and thus apparmor is _not_ started."
1796362,2018-10-09 17:37:42 UTC,"ubuntu@ubuntu:~$ notepad-plus-plus
snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks"
1796362,2018-10-16 09:58:56 UTC,"What are side effect of booting without apparmor? Should this argument be included by default on a persistent livecd, should we inform the author of https://help.ubuntu.com/community/mkusb about the need of changes?"
1796362,2018-10-09 11:03:31 UTC,"Tried with lots of variations either with sudo and without, didn't help out."
1796362,2018-10-09 10:38:55 UTC,Hey
1796362,2018-10-05 18:33:53 UTC,"It's live-CD environment that uses casper-rw partition to save all the progress.
I used mkusb to get it all work.
https://help.ubuntu.com/community/mkusb#Quick_start_manual_and_mkusb_PPA"
1796362,2018-10-05 17:28:53 UTC,"When you say persistent, does that imply a live-CD environment or a regular ""boot and install to HDD/SSD"" mode? The error is not about interface connections but about a special profile for the confinement tool itself. Normally snapd installs this profile automatically but on your system, for some reason it does not happen. Today is a little bit late but perhaps you can provide the logs of the snapd system service? You can collect them with:"
1796362,2018-10-05 16:51:26 UTC,"So, this is a loop. I'm able to make it to work, but it won't launch after restart of the operating system."
1796362,2018-10-05 16:28:33 UTC,Hello!
1796362,2018-10-05 16:49:24 UTC,"Okey, I have newly installed persistent Ubuntu 18.04.1"
1796362,2018-10-09 17:14:06 UTC,Can you inspect the status of apparmor.service?
1796379,2018-10-05 21:43:09 UTC,This is almost certainly fixed via this patch:
1796379,2018-10-05 20:00:25 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1796379,2018-10-05 18:24:24 UTC,"StacktraceTop:
 e2p_is_null_uuid (uu=uu@entry=0x7ffcdb8f3000) at ../../../../lib/e2p/uuid.c:32
 e2p_uuid2str (uu=uu@entry=0x7ffcdb8f3000) at ../../../../lib/e2p/uuid.c:80
 e2p_list_journal_super (f=0x7fa1b95de760 <_IO_2_1_stdout_>, journal_sb_buf=0x7ffcdb8f1db0 ""\300;9\230"", exp_block_size=4096, flags=<optimized out>) at ../../../../lib/e2p/ljs.c:105
 print_inline_journal_information (fs=0x555fb1e382d0) at ../../../misc/dumpe2fs.c:395
 main (argc=<optimized out>, argv=<optimized out>) at ../../../misc/dumpe2fs.c:733"
1796384,2018-10-05 23:19:09 UTC,On dirait que c’est relié au fait que Google maintenant veut que tout le monde utilise des clés API pour utiliser Google MAPS.
1796385,2019-01-28 11:47:42 UTC,"Message from syslogd@amer at Jan 27 19:26:19 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [swapper/5:0]"
1796385,2019-01-28 11:36:30 UTC,"Message from syslogd@amer at Jan 27 19:26:19 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [swapper/5:0]"
1796385,2019-05-18 07:40:39 UTC,"[root@localhost network-scripts]# systemctl status network -l
? network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2019-01-19 03:47:01 EST; 21s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 86319 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS)
  Process: 86591 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
    Tasks: 0"
1796385,2020-02-18 17:19:25 UTC,I'm seeing the same here.
1796385,2020-02-18 19:39:36 UTC,I had the same problem with OSP on RHEL 7.6
1796385,2020-02-24 17:39:17 UTC,Thanks ... I reviewed log files this morning and had a look at output from journalclt.  Appears the system is good to go.  I guess going through and blowing out the machine and re-seating everything into their slots helped.  Thanks you for your assistance!
1796385,2020-02-21 23:42:28 UTC,I opened up the server and reset cards and vacuumed it out a couple of days ago.  I'll know if things are okay next week.
1796385,2020-02-22 04:09:31 UTC,"Hi,"
1796385,2020-02-22 05:49:34 UTC,"Hi,"
1796385,2018-10-16 04:50:15 UTC,"Hello,"
1796385,2020-02-18 20:34:02 UTC,"you can also check RAID card as it's common to be defect and causes problems on servers, and disk I/O latency if there is a disk problem it will affect the performance, I had this on HDD also for some services that needed an SSD to be installed and recommended by some Vendor to me."
1796385,2018-10-12 23:36:15 UTC,"Hello,"
1796385,2018-10-11 18:09:02 UTC,"This issue started with the upgrade to 18.10 beta. I was not having it before.
I installed the V4.19-rc7 and still have the issue though it seems to be happening less frequently."
1796385,2018-10-12 17:21:58 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=201379#c6
1796385,2018-10-12 17:12:33 UTC,Unfortunately we do not have information to determine 'Product' and 'Component'.
1796385,2018-10-12 14:14:04 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3
1796385,2018-10-12 12:15:48 UTC,"@Guenter,"
1796385,2018-10-12 11:59:53 UTC,"Also, I don't think I have permission to change any of the bug status fields."
1796385,2018-10-12 11:57:40 UTC,"The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either."
1796385,2018-10-12 11:49:55 UTC,"@Guenter,"
1796385,2018-10-12 11:41:09 UTC,"Talk about shooting the messenger. The kernel's watchdog (kernel/watchdog.c) reports a stalled CPU. This is not a problem with the kernel's watchdog. The kernel watchdog just reports the problem. It is also not a problem with the watchdog subsystem, which is not even involved."
1796385,2018-10-11 19:44:56 UTC,"https://bugzilla.kernel.org/show_bug.cgi?id=201379
--
Cristian Aravena Romero (caravena)"
1796385,2018-10-11 18:32:59 UTC,"Hello,"
1796385,2018-10-08 15:18:59 UTC,Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
1796385,2018-10-05 19:00:06 UTC,This change was made by a bot.
1796385,2018-10-12 18:02:38 UTC,@Bounty
1796395,2018-10-18 10:07:08 UTC,"I think we discussed this last week (or the one before); The approach the charms take to HA in non-shared l2 deployments is to use DNS-HA for the deployment; MAAS could take the same approach, providing a single managed DNS entry based on availability for clients to connect to."
1796395,2019-09-19 12:06:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1796395,2019-09-24 07:59:52 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1796395,2019-09-24 08:15:30 UTC,https://discourse.maas.io/t/support-multiple-regiond-endpoints-in-maas-client/1014
1796397,2020-02-05 04:33:10 UTC,This bug was fixed in the package firefox - 73.0+build1-0ubuntu1
1796397,2020-01-20 12:02:51 UTC,Fixed with https://bazaar.launchpad.net/~mozillateam/firefox/firefox.focal/revision/1349.
1796397,2020-01-20 11:31:01 UTC,"Not an upstream bug after all. I downloaded the latest release build, unpacked it in a clean VM and observed that the icon for DDG in the new tab page is reasonably high resolution, unlike the one in the Ubuntu builds."
1796397,2020-01-17 02:08:55 UTC,Hey it’s been two years I’m wondering if anyone knows the solution to this
1796397,2018-11-29 06:23:04 UTC,@osomon are you sure ?
1796397,2018-11-19 15:12:23 UTC,The firefox snap is also affected by this issue. It appears to be an upstream bug. Would you mind filing a bug at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and sharing the link to that bug here?
1796397,2018-10-30 18:29:36 UTC,"@osomon Since Quantum, FF has an icon in the source tree - https://hg.mozilla.org/mozilla-central/file/default/browser/components/newtab/data/content/tippytop/images/duckduckgo-com@2x.png"
1796397,2018-10-10 15:48:08 UTC,"It did, after removing the cached search data from my profile directory (~/.mozilla/firefox/XXXXXXXX.default/search.json.mozlz4)."
1796397,2018-10-10 15:30:39 UTC,"I tried replacing the Image entry in /usr/lib/firefox/distribution/searchplugins/locale/*/ddg.xml with a higher resolution icon, but this didn't seem to make a difference."
1796397,2018-10-10 15:15:22 UTC,The icon is the 16×16 base64-encoded image provided by DuckDuckGo themselves at https://duckduckgo.com/opensearch.xml.
1796397,2018-10-05 20:15:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796399,2018-12-24 11:47:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796400,2019-06-06 02:17:23 UTC,"Reviewed:  https://review.opendev.org/658825
Committed: https://git.openstack.org/cgit/openstack/charm-hacluster/commit/?id=4d391e8107f63eefbc143624d78100389fd12a92
Submitter: Zuul
Branch:    master"
1796400,2019-05-13 14:28:01 UTC,@Chris:
1796400,2019-05-13 11:50:22 UTC,"Reviewed:  https://review.opendev.org/615965
Committed: https://git.openstack.org/cgit/openstack/charm-hacluster/commit/?id=9483383555c181e7efa99619fad6f7641020bc5a
Submitter: Zuul
Branch:    master"
1796400,2019-05-13 08:57:14 UTC,Chris:
1796400,2018-11-06 18:14:03 UTC,"check_crm v0.7 already supports specifying a threshold for failcounts, and in any case the plugin never sends a CRITICAL for failed actions, only a WARNING.
The problem is actually that check_crm sends a CRITICAL for failed actions, and that takes precedence over the warnings for failcounts."
1796400,2019-05-13 07:39:41 UTC,Andrea:
1796400,2018-12-10 16:45:56 UTC,Subscribed field-medium
1796400,2018-11-08 13:40:07 UTC,"Actually... I marked my commit as 'closes-bug' but that's wrong: it only allows check_crm to be configured to ignore failed actions, but does not change anything in the way the charm configures it.
Now we should set --failedactions=ignore and either expose the --failcount option, or set it a sane default. I think something like 5 would make sense (monitor actions for openstack services are set to once every 5s)."
1796400,2019-05-13 11:41:07 UTC,"I've just merged https://review.opendev.org/#/c/615965. Andrea: if you want to continue working on this change, that would be great, otherwise, I believe that the field-medium subscription should be removed."
1796402,2018-10-05 22:36:08 UTC,"Hello Jann, thanks for contacting us. Excellent discovery."
1796402,2018-10-05 22:52:02 UTC,"No, I have not allocated a CVE number for this."
1796402,2018-10-19 01:40:32 UTC,"Hello,"
1796402,2018-10-20 02:41:23 UTC,"CVE-2018-15686 has been assigned to this issue.
Thanks"
1796402,2018-10-22 16:31:49 UTC,Thanks for the update! That looks like a very thorough cleanup. :)
1796407,2018-10-19 08:38:03 UTC,"I'll revise the patch when I have time... may have an hour /two this weekend.
But I have never done anything  using the test thing though.. there'd
be quite a learning curve to do that, I think.
On Thu, 18 Oct 2018 at 12:55, Robie Basak <email address hidden> wrote:

>
> Thanks Martin!
>
> @D J Gardner I hope that gives you a clear path forward?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1796407
>
> Title:
>   pg_wrapper doesn't work when -p is used
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1796407/+subscriptions
"
1796407,2018-10-18 09:37:53 UTC,"@Robie: It's been a while since I dabbled with this, but to me this is not really ""wishlist"", it's an actual bug. Surely pg_wrapper doesn't document that it looks at the explicitly specified port, but it certainly ought to. This case was just plain forgotten."
1796407,2018-10-11 12:44:50 UTC,"> From that perspective, I'm not sure this is suitable for SRU, so it will need to go to the development release first.
"
1796407,2018-10-18 09:48:50 UTC,Thanks Martin!
1796407,2018-10-10 08:17:29 UTC,"There is a mismatch in behaviour of a library function (returns cluster on
default port) and what the program expects (null value for port if no
cluster was selected)"
1796407,2018-10-09 11:45:37 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1796407,2018-10-06 04:19:35 UTC,"The attachment ""port-based-pgversion.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1796407,2018-10-11 12:42:48 UTC,"OK, thanks."
1796408,2018-10-18 07:45:17 UTC,"I'm checking the route.
First thing I noticed (which has nothing to do with the crash, which I also have) is that the logfile has many warning lines of type:
Warning: Cannot parse the constant number nan in J:\Program Files\Train Simulator\ROUTES\Campania2018_352gts\Campania2018.rdb:line 18500
In fact if you check line 18500 of the .rdb file it is as follows
   UiD ( -5633 14367 12031 3 -5633 14367 nan nan nan 0 1.5402702 0 )
This is clearly a faulty line. The route author should check such faulty lines and correct them."
1796408,2018-10-18 11:49:28 UTC,"I've found the cause of the error. I'm sorry, but there is a mess in the signal data of the route, which causes the problem. In file w-005626+014367.w there is this block
 Signal (
  UiD ( 12919 )
  FileName ( FSSignal_1C_2VQ.s )
  Position ( -841.867 0.994007 143.205 )
  QDirection ( 0 0.505806 0 0.862647 )
  VDbId ( 4294967295 )
  SignalSubObj ( 00004013 )
  SignalUnits ( 2
   SignalUnit ( 0
    TrItemId ( 0 938 )
   )
   SignalUnit ( 1
    TrItemId ( 0 939 )
   )
  )
 )"
1796408,2018-10-17 17:26:47 UTC,"http://www.mediafire.com/file/yzewa3dhgsbv1rd/Campania_2018.rar/file this
is the link for the download..Thank you for the work you are doing!!"
1796408,2018-10-16 16:27:51 UTC,Where can I download that route?
1796408,2018-10-13 20:01:16 UTC,If I have time I'll download the route and check why it fails in MP.
1796408,2018-10-13 13:58:28 UTC,"sorry, I express myself better: when I use the scenario in question in Single Player it works correctly, when in MP crasha giving me the error that I sent in the picture .. I would like to understand what is due. Thanks for the support."
1796408,2018-10-06 06:52:25 UTC,"Providing the full logfile is always better. This crash seems be caused by the particular route tdb file, and concerns signals. Can you tell me in which route this occurs, and if possible can you attach the full logfile?"
1796410,2018-11-06 15:02:28 UTC,i am rather conflicted on how to triage this bug.
1796410,2018-11-07 11:37:57 UTC,"I had looked at Neutron QoS policies, but it looked like these were network policies, not per-flavor policies.  We need the ability for flavors to define the policy since our users will create their own projects, create their own networks, and launch their own VMs, and should not have the ability to affect the QoS policy on their own infrastructure."
1796412,2018-10-05 23:02:38 UTC,SOLVED!!!!
1796412,2018-12-05 14:11:15 UTC,"Hi I fixed this by telling XQUartz preferences to emulate 3 button mouse and then in Inkscape:
Edit->Input Devices and in the settings pane revealed select Core pointer and Disable it then select xquartz virtual pointer and enable it. (crashed when I tried to enable the virtual pointer without disabling the Core pointer but didn't duplicate this to check whether the crash was random - also didn't check if 3-button emulation was essential)"
1796412,2018-12-05 14:25:47 UTC,"Hm, Now it crashes every time I use the calligraphy pen.
3-button emulation in XQuartz is not essential to get mouse working on inkscape canvas
Inkscape forgets configuration between re-starts so edit-Input Device is required at every start up"
1796416,2019-09-19 12:06:49 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1796418,2019-09-19 12:06:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1796429,2019-09-06 02:17:54 UTC,is this unit test still randomly failing?
1796429,2020-01-24 16:40:31 UTC,"Based on the comments, marking for now as Incomplete."
1796429,2020-02-28 08:40:28 UTC,"Due to a long inactivity, I am moving this bug to Invalid.
If you still experience the issue, feel free to reopen it."
1796430,2019-01-10 12:29:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/629843"
1796434,2018-10-06 01:03:45 UTC,@Steve
1796434,2018-10-06 00:42:16 UTC,That would be a failed verification but not a regression.  Removing the tag.
1796434,2018-10-06 00:48:49 UTC,"To add more information to my previous report, I've recently installed Ubuntu 18.04.1 on two machines, one of which is pretty old, and the other is about a year and a half old."
1796435,2018-10-06 01:28:22 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1796435,2018-10-09 17:01:58 UTC,"I will read the link you gave me, but i do not promise anything.
I also wonder why you don't have for the field ""importance"" a value for critical security vulnerabilities:
https://wiki.ubuntu.com/Bugs/Importance"
1796437,2020-01-18 18:21:31 UTC,"I found the real reason for the crashes. The problematic package is the `gstreamer1.0-vaapi` (see https://packages.ubuntu.com/focal/gstreamer1.0-vaapi).
It is a dependency of `ubuntu-restricted-addons` (see https://packages.ubuntu.com/focal/ubuntu-restricted-addons)."
1796437,2020-04-04 13:51:30 UTC,Seeing this on Ubuntu MATE 20.04 LTS beta 20200402:
1796437,2020-03-19 13:55:13 UTC,This is still happening in Ubuntu Budgie 20.04 on virt-maneger VM on latest daily.
1796437,2020-03-14 17:31:35 UTC,Still happens with Ubuntu MATE 20.04 LTS (20200313) using VirtualBox 5.1.
1796437,2020-02-17 19:44:53 UTC,"Unable to log in to Xorg session.  I got dumped back to the login screen.
I was able to log in using Wayland.
I did a full update in CLI but was still unable to successfully log in to Xorg.
Running on KVM/virt-manager"
1796437,2020-02-07 09:30:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796437,2020-01-20 22:55:40 UTC,I run into this on Ubuntu Budgie 20.04 when trying to open GNOME Settings. It dumps me to to the login screen. I just tried to use About and it did the same thing. This is in a VirtualBox virtual machine if that is relevant. Happy to provide additional detail if needed. Thanks for looking into this.
1796437,2020-01-19 13:05:32 UTC,"The issue is more generic - Yelp and Cheese crash in the VirtualBox on MATE, Xfce, Budgie and GNOME FlashBack (metacity) sessions."
1796437,2020-01-18 17:30:11 UTC,This change was made by a bot.
1796437,2020-01-10 17:59:27 UTC,"Got this bug on clean installation of Ubuntu MATE 20.04 LTS (http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/ , SHA256 = db76f02f944bad2b713f49bc5d8f15f1e4a4da819e11053de99175d849c4b6a6 ) inside Oracle VM VirtualBox 5.1.38 (Ubuntu 16.04.6 LTS MATE as host)."
1796437,2020-01-16 21:33:12 UTC,Still reproducible on 20200115 and 20200116 builds.
1796437,2020-01-14 23:15:00 UTC,@Norbert I am not seeing this with the 20200114 build. I'm running this in VirtualBox 5.2.34
1796437,2020-01-13 18:11:57 UTC,@Daniel van Vugt (vanvugt)
1796437,2020-01-13 17:53:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796437,2020-01-13 02:09:12 UTC,"Norbert,"
1796437,2020-01-10 19:00:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1796437,2020-01-10 18:10:42 UTC,The Xorg crash is fixable by preventing the start of Ubuntu MATE Welcome (I did it by removing whole Snap functionality with `sudo apt purge snapd`).
1796437,2019-07-22 04:20:50 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1796437,2018-10-06 01:56:18 UTC,"StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 __assert_fail_base (fmt=0x7f29afb85858 ""%s%s%s:%u: %s%sAssertion `%s' failed.\n%n"", assertion=0x55c50dca64bb ""key->initialized"", file=0x55c50dcaa9b0 ""../../../../../../include/privates.h"", line=121, function=<optimized out>) at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x55c50dca64bb ""key->initialized"", file=file@entry=0x55c50dcaa9b0 ""../../../../../../include/privates.h"", line=line@entry=121, function=function@entry=0x55c50dccc0c0 <__PRETTY_FUNCTION__.13800> ""dixGetPrivateAddr"") at assert.c:101
 dixGetPrivateAddr (key=<optimized out>, key=<optimized out>, privates=0x55c50f7ba1d0) at ../../../../../../include/privates.h:121"
1796437,2020-01-18 17:04:51 UTC,"With virt-manager the crashes occur with Cirrus, QXL, VGA video drivers.
But does not occur with VMVGA video driver.
Possibly kernel (drm) issue."
1796438,2019-05-31 05:50:26 UTC,Note : Still getting this message on ubuntu-19.04-live-server
1796438,2019-09-27 06:17:33 UTC,"No this issue in ubuntu-19.10-live-server-amd64.iso daily build Aug-2019 with initrd.img-5.2.0-10-generic.
kernel: 5.2.0-10-generic"
1796438,2019-03-12 12:16:02 UTC,Note : Still getting this message on sudo apt upgrade
1796438,2019-06-21 01:29:15 UTC,Confirmed this is still happening in 5.0.0-17
1796438,2019-01-15 13:47:03 UTC,"NO.
The issue is still there in 18.10."
1796438,2018-10-11 17:14:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796438,2018-10-25 02:55:13 UTC,"This issue disappear in ubuntu-18.10-server-amd64.iso and ubuntu-18.10-desktop-amd64.iso,
but it still exists in ubuntu-18.10-live-server-amd64.iso"
1796438,2019-01-15 14:02:05 UTC,"NOTE that mlst of the problem is the use of ""may not"", which means ""is not allowed to""."
1796441,2018-10-06 02:36:42 UTC,Bug exists in 16.04...18.04
1796443,2019-08-13 11:27:47 UTC,This bug was fixed in the package linux - 4.15.0-58.64
1796443,2019-08-07 08:34:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1796443,2019-07-25 18:33:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1796443,2019-07-16 10:36:02 UTC,"Please note that all commits requested for Disco have already been applied as part of LP: #1836614 (""Disco update: 5.0.18 upstream stable release"")."
1796443,2019-07-02 20:50:31 UTC,All 3 test kernels look good.  Tested on internal ryzen development boards that were showing this symptom previously.
1796443,2019-06-20 17:36:29 UTC,Thank you! Will do.
1796443,2019-06-04 17:55:03 UTC,Adding dmesg/serial from failing system (AMD test board) as another example of failing system besides the original reporter.
1796443,2019-05-31 15:45:14 UTC,Just ran across this bug in LP.
1796443,2018-12-05 20:50:01 UTC,"Fix became part of the following releases:
1) 4.20-rc5 (commit 60c8144afc28)
2) 4.19.7 (commit 00f91adf52af)
3) 4.14.86 (commit 855eefd9124a)"
1796443,2018-11-30 23:10:16 UTC,"Fixed in Linus's tree with commit 60c8144afc28 (""x86/MCE/AMD: Fix the thresholding machinery initialization order"")."
1796443,2018-11-28 11:43:35 UTC,A proper fix has been provided by Borislav:
1796443,2019-06-14 05:07:49 UTC,"Jon,"
1796443,2018-10-12 12:38:28 UTC,*** Bug 201213 has been marked as a duplicate of this bug. ***
1796443,2018-10-11 07:18:57 UTC,I think it's better to mail to the patch author and cc x86 mailing list.
1796443,2018-10-10 04:11:52 UTC,Changing as requested.
1796443,2018-10-10 04:10:34 UTC,Kernel
1796443,2018-10-09 16:10:57 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1796443,2018-10-08 15:00:42 UTC,"Hello,"
1796443,2018-10-06 04:00:07 UTC,This change was made by a bot.
1796443,2018-10-06 03:43:32 UTC,"Note: bug also effect 18.04. Debian stable works, as it's based on 4.9."
1796443,2018-09-30 04:07:25 UTC,"Created attachment 278849
dmesg from normal debian 4.9 boot"
1796443,2018-09-30 04:01:15 UTC,"Created attachment 278847
dmesg from booting from last good commit"
1796443,2018-09-30 03:50:49 UTC,"Created attachment 278845
ACPI dump"
1796443,2018-11-27 10:21:43 UTC,https://marc.info/?l=linux-edac&m=154331383121359&w=2
1796444,2018-10-06 18:19:09 UTC,"Yes, you are right.  There is something odd there."
1796444,2018-10-06 04:16:16 UTC,"It looks like your track is off-grid.  There are a few snap points that get set when you start off-grid.  The first is the track's original grid origin, next is the end point of the joint and last is the original grid.  As you drag, it will look for increments of the track's grid, increments of your board grid and last snap points."
1796444,2018-10-06 17:49:32 UTC,Hi Seth
1796446,2019-02-03 07:38:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796451,2018-10-06 05:42:30 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x55c5e6894d50, fundamental_type=fundamental_type@entry=76) at ../../../../gobject/gtype.c:4026
 g_param_spec_unref (pspec=0x55c5e6894d50) at ../../../../gobject/gparam.c:230
 std::unique_ptr<_GParamSpec, void (*)(_GParamSpec*)>::~unique_ptr (this=0x55c5e6883a50, __in_chrg=<optimized out>) at /usr/include/c++/8/bits/unique_ptr.h:347
 GjsAutoParam::~GjsAutoParam (this=0x55c5e6883a50, __in_chrg=<optimized out>) at ./gjs/jsapi-util.h:86
 js::HashMapEntry<JS::Heap<JSString*>, GjsAutoParam>::~HashMapEntry (this=0x55c5e6883a48, __in_chrg=<optimized out>) at /usr/include/mozjs-60/js/HashTable.h:732"
1796451,2020-03-12 04:00:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796453,2018-10-06 07:00:04 UTC,This change was made by a bot.
1796454,2018-11-24 20:15:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796457,2018-10-06 11:48:06 UTC,Looks like a graphics bug. Downgrade mesa. OR try in fresh install.
1796457,2018-10-07 15:34:00 UTC,Thanks. Fresh install: same problems. I'm not an experienced user and I don't know how to downgrade mesa in a safe manner. I think it could make my system unusable if I get it wrong. How do I safely downgrade it?
1796457,2019-01-14 13:32:57 UTC,"We had this same problem on ~100 PCs, all these computers had Ati Radeon X1200 graphic card and stopped working (Compiz Crash) on mid/later 2018."
1796458,2019-11-26 19:55:44 UTC,"Could you please run simple-scan with command:
  $ simple-scan --debug"
1796458,2019-11-26 19:56:12 UTC,What kind of scanner are you using?
1796464,2020-02-26 17:46:22 UTC,"I think I have found what caused the missing ""Steam Installer"" issue. See my comment in #1864635."
1796464,2020-02-23 20:10:32 UTC,This bug was fixed in the package steam - 1:1.0.0.61-2ubuntu1
1796464,2020-02-25 10:44:28 UTC,"This issue was still not completely fixed. ""Steam Installer"" disappeared from GNOME Software after latest Steam update, see: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1864635"
1796464,2020-01-28 14:08:16 UTC,"The steam/steam-devices packages are still outdated in Ubuntu, including latest Ubuntu Focal. They were last updated two years ago. The outdated version (1.0.0.54) does not contain proper udev rules for Steam Controller and VR, does not have conflicts with the official Valve package solved, and has many other issues that the latest (1.0.0.61-2) Debian package has already solved."
1796464,2020-02-20 19:06:08 UTC,"Steam is still in the outdated, broken version on latest Ubuntu Focal. Is there anything we could do to help Canonical with updating the Steam packages?"
1796464,2020-01-28 14:05:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796469,2018-10-12 09:45:11 UTC,Does anyone have any more information about this?
1796469,2018-10-12 15:17:09 UTC,Not sure if it's related but I'll leave this here.
1796469,2018-10-15 07:24:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796469,2018-10-15 17:11:07 UTC,For anyone using ansible this is how I rolled back to version 21
1796469,2018-10-19 11:49:27 UTC,The problem affects also transfers from RDS instances - it prevents for example creating an export file using pg_dump from an RDS Postgres database.
1796469,2018-10-23 23:46:07 UTC,"We ran into the exact same issue with pg_dump after upgrading to Bionic (4.15.0-1023-aws kernel) on r5.xlarge (a next-gen Nitro instance). After 16-80 MB of data is received, tcpdump shows the receive window collapsing to 1 (not quite suddenly, but quickly), and it never recovers. We have engaged with AWS support on this issue, and they referred us to this bug."
1796469,2018-10-24 19:21:50 UTC,"Trying it again with the newly posted 4.15.0-1025-aws kernel, we can no longer reproduce the issue with pg_dump."
1796469,2018-10-25 12:06:03 UTC,Can also confirm that the 4.15.0-1025-aws kernel appears to have solved the timeout issues we were seeing with `git clone` processes.
1796478,2018-10-15 19:17:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796479,2020-08-28 15:09:25 UTC,"Unfortunately this is still not working even with wxPython 4.1.0, though it is closer."
1796481,2020-04-27 17:27:40 UTC,Fixed in 2.1.0: APFS mounting is now supported on macOS 10.12 and higher.
1796481,2020-04-17 14:55:36 UTC,Fixed in upcoming version 2.1.0
1796482,2019-12-03 17:04:03 UTC,"Fixed, will be available in 2.1.0"
1796482,2020-04-27 17:28:15 UTC,Fixed in 2.1.0 with improvements to output file mounting code
1796483,2020-04-08 18:21:01 UTC,Fixed in upcoming version 2.1.0
1796485,2019-02-16 16:15:27 UTC,"In my case, I do get back, but it can take minutes.  How could one help debugging what the issue is?  Got local account and while I am waiting for the login screen to get away, the hard disk light is off; there is no IO.  I suspect some kind of timeout is happening."
1796485,2020-02-29 22:17:03 UTC,"I moved to Ubuntu 19.10, Gnome 3.34 and the problem does not happens anymore.  I believe that it has been fixed in the later version of the OS."
1796485,2020-03-01 00:05:45 UTC,I solved this by switching to lightdm
1796490,2020-06-02 22:56:37 UTC,"Unfortunately, there's not enough information to determine what went
wrong here. Moreover, the Ardour developers have released version 6.0
and don't appear to have any interest in fixing bugs in versions prior."
1796492,2018-10-06 21:55:34 UTC,"Subscribing kubuntu-bugs, since this appears to be a Kubuntu matter rather than a translation issue."
1796494,2018-10-06 15:50:36 UTC,"Currently, the only procedure to change an application password I found is as follows:"
1796494,2018-10-09 15:20:47 UTC,"The procedure mentioned in #1 does not take into account that grants are not created if they already exist so even if a password is changed in a service config file and leader settings of the percona application, it is not changed in the DB itself:"
1796495,2018-10-10 15:43:08 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1796500,2018-10-07 16:34:38 UTC,"Graphic items on copper are never a good idea.
For instance you cannot define a clearance for these items
Therefore I am not sure making them easy to draw on copper layers is a good idea."
1796500,2019-04-03 10:22:29 UTC,"Fixed in revision 920d9e3d46f89dd60ed52553ab635a697227e21b
https://git.launchpad.net/kicad/patch/?id=920d9e3d46f89dd60ed52553ab635a697227e21b"
1796500,2019-04-03 12:37:29 UTC,"@Jeff
I reopen this bug, because the fix creates *serious issues*:
Dimensions and polygons are now allowed on copper layers, but they are ignored by DRC and can create broken boards (short circuits)."
1796500,2019-04-03 16:41:12 UTC,The reason we haven't enabled this in the past is because the DRC doesn't handle it.  I recommend we revert this change until the DRC is capable of handling dimensions and polygons on copper layers.
1796500,2019-04-03 18:17:09 UTC,"Fixed in revision 77284e82c821682cbd8bb9c9ac812664c4f60dfa
https://git.launchpad.net/kicad/patch/?id=77284e82c821682cbd8bb9c9ac812664c4f60dfa"
1796501,2019-11-09 01:02:42 UTC,"Hello jrb0001, or anyone else affected,"
1796501,2019-11-09 05:30:46 UTC,"All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1796501,2019-11-14 15:00:27 UTC,"Hello jrb0001, or anyone else affected,"
1796501,2019-11-14 19:08:45 UTC,"Verified in disco with, ii  systemd                                    240-6ubuntu5.8"
1796501,2019-11-14 21:50:16 UTC,Verified in bionic with 237-3ubuntu10.32
1796501,2019-11-15 00:55:07 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1796501,2019-11-25 11:18:51 UTC,This bug was fixed in the package systemd - 240-6ubuntu5.8
1796501,2019-10-10 23:29:50 UTC,This bug was fixed in the package systemd - 242-7ubuntu2
1796501,2019-11-16 02:55:53 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1796501,2019-11-25 11:19:19 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1796501,2019-11-26 03:46:45 UTC,"ubuntu@lp1796501-b:~$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3"
1796501,2019-11-26 17:37:57 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.33
1796501,2020-11-15 20:56:01 UTC,i fixed the issue simply but changing the link from the stub resolver to just point at resolv.conf with just nameserver lines...
1796501,2019-11-15 16:41:09 UTC,"Hello jrb0001, or anyone else affected,"
1796501,2019-10-04 19:55:18 UTC,I'm adding this patch to the next upload I'm preparing in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3797/+packages .
1796501,2019-06-13 23:36:00 UTC,"I grabbed the top 500 hosts in an Eaon LXD container with DNS=1.1.1.1
wget -O top500.csv https://moz.com/top-500/download/?table=top500Domains
cut -d, -f2 < top500.csv | cut -d\"" -f2 > top500"
1796501,2019-09-20 09:41:59 UTC,@bryanquigley are you going to SRU that?
1796501,2018-10-23 00:48:45 UTC,Can this bug make the complete failure of DNS (like https://github.com/systemd/systemd/issues/6490) more likely?
1796501,2018-10-23 17:41:38 UTC,I think the downgrade behaviour of systemd-resolved is the same as in that upstream bug although it is triggered differently. Except that it only breaks that single NXDOMAIN query in my case while it sounds like a permanent failure in the upstream bug.
1796501,2019-01-23 15:42:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796501,2019-02-19 15:19:29 UTC,https://github.com/systemd/systemd/issues/9384
1796501,2019-06-12 21:09:11 UTC,"A simple case on Disco+ that I believe is related to the DVE workaround is:
resolvectl query www.engadget.com"
1796501,2019-07-09 23:26:04 UTC,"I've confirmed, that #9 is is not reproducible with systemd from Debian.   The runs from there with our without DNSSEC=yes are the same.  They differ on Ubuntu."
1796501,2019-04-08 15:56:44 UTC,"Has there been any progress so far? systemd-resolved would be nice in theory, but not if it breaks half of the websites like it did before I stopped using it."
1796501,2019-08-14 01:16:48 UTC,"I've confirmed the fix causes other issues (above), and is still needed for wifi to work at Starbucks (In Toronto) - although DNS failed after accepting to east.datavalet.io."
1796501,2019-09-11 22:38:49 UTC,@xnox Your updated patch (https://github.com/systemd/systemd/commit/50b9974aee29efb8118a20360b0d521f58110afd) on the GH issue fixes this issue AFAICT.  Can we have the patch updated in Ubuntu?
1796501,2019-09-12 23:20:36 UTC,Built a eoan package with xnox's updated patch in my ppa: https://launchpad.net/~bryanquigley/+archive/ubuntu/1796501/+packages
1796501,2019-09-13 00:23:23 UTC,"The attachment ""eoan debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1796501,2019-09-19 22:10:18 UTC,I've confirmed that with this update patch my issue in C#9 is indeed fixed.   It also should be more performant for non-DNSSEC=yes users.
1796501,2019-07-19 04:49:49 UTC,I just built a package that just reverts it for Bionic and Disco : https://launchpad.net/~bryanquigley/+archive/ubuntu/1796501
1796501,2019-09-20 15:23:45 UTC,"Yes, if we can get it into dev, I'd happily make debdiffs to SRU it to bionic/disco."
1796504,2018-10-08 17:12:21 UTC,The behaviour seen in GParted is because GParted is unable to read the used/unused information from the F2FS file system.  Hence it warns that some operations may be unavailable.  This is due to limitations in the file system tools for F2FS.
1796504,2019-03-05 18:06:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796506,2018-10-10 13:38:50 UTC,Speaking only about the projector -
1796514,2018-10-07 20:37:48 UTC,"I suggest that it should be initially unbound (as per ALLOCATE-INSTANCE protocol, and as it is now), but DESCRIBE should not signal an error. CLHS states that DESCRIBE isn't supposed to signal errors."
1796514,2018-10-07 20:28:27 UTC,"Are you suggesting that NAME should not be initially unbound, or that describe should print 'unbound'? As is, this seems at worst a minor inconvenience, not an actual bug.  There a zillion ways to create objects whose state is incomplete for some other operation."
1796517,2018-10-11 06:55:05 UTC,"This happens because CMake doesn't like libraries that include only header files. We have added a dummy .cc file to all of those, which makes all compilers except for Clang on Mac happy. Clang on Linux does not have any issues with it."
1796517,2019-09-17 07:28:09 UTC,Migrated to https://github.com/widelands/widelands/issues/3331
1796520,2018-12-14 12:29:38 UTC,This is still reproducible on git master:
1796520,2020-11-26 23:53:36 UTC,"Bug is still pending on git master. Have not pinged the SuperH crew yet. Will try to do that tomorrow, I'll also ping glibc upstream."
1796520,2020-11-23 09:03:34 UTC,Did you ever ask the glibc or SuperH experts? Is this bug still pending in the latest version of QEMU?
1796520,2019-08-18 18:07:17 UTC,We can ask both glibc upstream and some SuperH experts. I'll ask.
1796520,2021-01-26 04:17:25 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1796520,2019-08-12 14:36:58 UTC,"On that hardware, at least, the user-space visible FPSCR value is indeed 0x000800000. Execution of the 'frchg' insn either doesn't trap, or the trap is caught by the kernel and emulated. I think it is not being emulated because CONFIG_SH_FPU_EMU is not set."
1796520,2019-08-09 14:18:03 UTC,I can provide access to a machine connected to the internet so you can test it yourself. I'll send you an email.
1796520,2019-08-09 14:00:14 UTC,"I can reproduce this bug, but I'm not sure what QEMU is doing wrong. Looking at the ""SH4 Software Manual"", it definitely says that if the FPSCR.PR bit is 0 then the 'frchg' and 'fschg' instructions should both trap."
1796520,2019-08-12 14:48:55 UTC,"(Edit to note that ""that hardware"" is an SH7785LCR with an SH7785 CPU.)"
1796528,2018-10-08 09:09:13 UTC,"Xorg without external monitor:
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
LVDS-1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1280x800      59.98 +  59.97*   59.81    59.91
   1280x720      60.00    59.99    59.86    59.74
   1024x768      60.04    60.00
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   800x512       60.17
   700x525       59.98
   800x450       59.95    59.82
   640x512       60.02
   720x450       59.89
   700x450       59.96    59.88
   640x480       60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   680x384       59.80    59.96
   640x400       59.88    59.98
   576x432       60.06
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
VGA-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
SVIDEO-1 disconnected (normal left inverted right x axis y axis)"
1796528,2018-12-09 04:17:25 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1796528,2018-12-09 04:17:23 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1796528,2018-12-09 04:17:19 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1796528,2018-10-09 07:20:47 UTC,Many thanks for your help!
1796528,2018-10-09 01:49:15 UTC,"If your gear icon vanishes then that indicates some bug has happened and the system is unable to offer you more than one option. Usually the system will just remember the last option you chose in the gear icon, so future logins should all be Wayland."
1796528,2018-10-09 00:07:33 UTC,"Sorry, I'm still a noob y many things. I've edited /etc/gdm3/custom.conf and I minded I was enabling wayland with this...
I've disabled automatic login and rebooted, then make login by clicking on the gear to select wayland -before I tryed to make this by closing session, but then the gear didn't appeared, only the login button.
Then, when I run xrandr in terminal Igot this:
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
XWAYLAND0 connected 1280x800+0+0 (normal left inverted right x axis y axis) 330mm x 210mm
   1280x800      59.81*+"
1796528,2018-10-08 09:04:46 UTC,"Next, please:"
1796528,2018-10-08 08:12:47 UTC,Thanks. Unfortunately that did not collect all the info I was hoping.
1796528,2018-10-08 08:52:14 UTC,"All of those seem to be from Xorg, not Wayland."
1796528,2018-10-08 08:51:01 UTC,"xorg, without external monitor"
1796528,2018-10-08 08:40:00 UTC,With external connected. Both Wayland
1796528,2018-10-08 08:34:59 UTC,"Without external
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
LVDS-1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1280x800      59.98 +  59.97*   59.81    59.91
   1280x720      60.00    59.99    59.86    59.74
   1024x768      60.04    60.00
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   800x512       60.17
   700x525       59.98
   800x450       59.95    59.82
   640x512       60.02
   720x450       59.89
   700x450       59.96    59.88
   640x480       60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   680x384       59.80    59.96
   640x400       59.88    59.98
   576x432       60.06
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
VGA-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
SVIDEO-1 disconnected (normal left inverted right x axis y axis)"
1796528,2018-10-08 02:11:05 UTC,Please run this command to send us more information about the system:
1796528,2018-10-08 07:43:08 UTC,apport information
1796528,2018-10-08 07:43:06 UTC,apport information
1796528,2018-10-08 07:43:05 UTC,apport information
1796528,2018-10-08 08:52:29 UTC,"xorg, external monitor attached"
1796535,2019-03-13 21:37:31 UTC,Retargeted to the hw-health charm.
1796535,2019-05-10 16:50:49 UTC,"Megaraid checks were added into the charm, however, the megaraid software is not detecting all smart errors on the disks."
1796535,2020-01-27 13:24:04 UTC,"This requires smartctl to be fully integrated to the charm, and given a config option for the controller number."
1796539,2019-01-02 15:39:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796544,2018-10-10 02:40:43 UTC,In the cosmic live session:
1796544,2018-10-10 02:29:43 UTC,"""Restricted Add-ons"" can't install because there is no internet access to get them. There is no internet access because of this bug. :)"
1796544,2018-10-07 09:06:49 UTC,WORKAROUND:
1796544,2018-10-09 12:02:39 UTC,This file is in /pool/restricted/b/bcmwl/bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu4_amd64.deb
1796549,2018-10-07 09:32:44 UTC,Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/334
1796549,2019-03-07 08:48:05 UTC,Please don't test for this bug while bug 1818972 is open. Or at least use the workaround mentioned in bug 1818972.
1796549,2019-10-03 02:56:30 UTC,Fix released in mutter 3.34
1796553,2019-06-17 07:16:25 UTC,Please test this patch.
1796553,2019-02-06 17:45:30 UTC,"Now I'm on
linux-image-4.18.0-14-generic                 4.18.0-14.15
(without btusb.enable_autosuspend=0) and it's broken again."
1796553,2018-10-17 19:34:15 UTC,"Hello Ralf,"
1796553,2019-01-17 22:24:14 UTC,"Testing the kernel from  https://people.canonical.com/~khfeng/lp1796553/
without btusb.enable_autosuspend=0"
1796553,2019-01-04 02:16:29 UTC,Sorry for the belated response.
1796553,2018-10-23 20:18:59 UTC,btusb.enable_autosuspend=0  definitely made the issue go away.
1796553,2018-10-22 21:39:51 UTC,btusb.enable_autosuspend=0 seems to have worked (so far)...
1796553,2018-10-18 04:12:43 UTC,"Please try kernel parameter ""btusb.enable_autosuspend=0""."
1796553,2018-10-17 19:45:35 UTC,"hildeb@humbaba:~$ ls -lihsa /lib/firmware/intel/
total 16M
3801225  12K drwxr-xr-x  2 root root  12K Sep 29 20:24 .
3801094  40K drwxr-xr-x 85 root root  36K Sep 29 20:25 ..
3817159    0 lrwxrwxrwx  1 root root   21 Aug  6 20:26 dsp_fw_bxtn.bin -> dsp_fw_bxtn_v3366.bin
3814817 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_bxtn_v2219.bin
3814818 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_bxtn_v3366.bin
3817161    0 lrwxrwxrwx  1 root root   20 Aug  6 20:26 dsp_fw_cnl.bin -> dsp_fw_cnl_v1191.bin
3814819 572K -rw-r--r--  1 root root 571K Aug  6 20:26 dsp_fw_cnl_v1191.bin
3817163    0 lrwxrwxrwx  1 root root   20 Aug  6 20:26 dsp_fw_glk.bin -> dsp_fw_glk_v3366.bin
3814820 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_glk_v1814.bin
3814821 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_glk_v2768.bin
3814822 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_glk_v2880.bin
3814823 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_glk_v3366.bin
3817166    0 lrwxrwxrwx  1 root root   20 Aug  6 20:26 dsp_fw_kbl.bin -> dsp_fw_kbl_v3402.bin
3814824 236K -rw-r--r--  1 root root 234K Nov 17  2017 dsp_fw_kbl_v1037.bin
3814825 236K -rw-r--r--  1 root root 234K Aug  6 20:26 dsp_fw_kbl_v2042.bin
3814826 240K -rw-r--r--  1 root root 238K Aug  6 20:26 dsp_fw_kbl_v2630.bin
3814827 240K -rw-r--r--  1 root root 238K Aug  6 20:26 dsp_fw_kbl_v3266.bin
3814828 244K -rw-r--r--  1 root root 242K Aug  6 20:26 dsp_fw_kbl_v3402.bin
3814829 240K -rw-r--r--  1 root root 238K Aug  6 20:26 dsp_fw_kbl_v3420.bin
3814830 236K -rw-r--r--  1 root root 234K Nov 17  2017 dsp_fw_kbl_v701.bin
3817169    0 lrwxrwxrwx  1 root root   24 Aug  6 20:26 dsp_fw_release.bin -> dsp_fw_release_v3402.bin
3814831 244K -rw-r--r--  1 root root 242K Aug  6 20:26 dsp_fw_release_v3402.bin
3814832 216K -rw-r--r--  1 root root 216K Aug  6 20:26 dsp_fw_release_v969.bin
3814833 688K -rw-r--r--  1 root root 686K Aug  6 20:26 fw_sst_0f28.bin
3814834 260K -rw-r--r--  1 root root 260K Mär 30  2017 fw_sst_0f28.bin-48kHz_i2s_master
3814835 688K -rw-r--r--  1 root root 686K Aug  6 20:26 fw_sst_0f28_ssp0.bin
3814836 688K -rw-r--r--  1 root root 686K Aug  6 20:26 fw_sst_22a8.bin
3814837 4,0K -rw-r--r--  1 root root   18 Mär  5  2018 ibt-11-5.ddc
3814838 584K -rw-r--r--  1 root root 581K Aug 30 21:57 ibt-11-5.sfi
3814839 4,0K -rw-r--r--  1 root root   14 Aug  6 20:26 ibt-12-16.ddc
3814840 580K -rw-r--r--  1 root root 579K Aug 30 21:57 ibt-12-16.sfi
3814841 4,0K -rw-r--r--  1 root root   14 Apr 24 16:28 ibt-17-0-1.ddc
3814842 612K -rw-r--r--  1 root root 611K Aug  6 20:26 ibt-17-0-1.sfi
3814903 4,0K -rw-r--r--  1 root root   29 Aug 30 21:57 ibt-17-16-1.ddc
3814904 616K -rw-r--r--  1 root root 614K Aug 30 21:57 ibt-17-16-1.sfi
3814843 4,0K -rw-r--r--  1 root root   14 Apr 24 16:28 ibt-17-1.ddc
3814844 612K -rw-r--r--  1 root root 611K Aug  6 20:26 ibt-17-1.sfi
3814905 4,0K -rw-r--r--  1 root root   29 Aug 30 21:57 ibt-17-2.ddc
3814906 616K -rw-r--r--  1 root root 614K Aug 30 21:57 ibt-17-2.sfi
3814907 4,0K -rw-r--r--  1 root root   14 Apr 24 16:28 ibt-18-0-1.ddc
3814908 612K -rw-r--r--  1 root root 611K Aug  6 20:26 ibt-18-0-1.sfi
3814911 4,0K -rw-r--r--  1 root root   29 Aug 30..."
1796553,2018-10-17 19:02:59 UTC,Still the same issue.
1796553,2019-01-21 19:29:53 UTC,"After a few days of testing (work, suspend, resume, work) it seem to work OK with the new kernel."
1796553,2018-10-11 02:25:00 UTC,"There's a new firmware for Intel 7260:
commit 70353356f8a01b6593ea94fd6ed6e9593fd0da1f
Author: Amit K Bag <email address hidden>
Date:   Wed May 16 10:52:14 2018 +0530"
1796553,2018-10-08 02:19:49 UTC,"Also, according to your kernel log (CurrentDmesg.txt) the message happens along with a bunch of other messages relating to the system suspending/resuming. Maybe it is trying to suspend and just failed to do so?..."
1796553,2018-10-08 02:30:05 UTC,This change was made by a bot.
1796553,2018-10-08 11:23:17 UTC,Bluetooth adapter is builtin. so I can't change the port.
1796553,2018-10-08 11:24:11 UTC,"It's definitely NOT happening while supending/resuming.
It happens while I'm using the machine, literally while moving the mouse."
1796553,2018-10-08 02:14:43 UTC,It sounds more like a kernel issue (or hardware) if your Bluetooth dongle is getting reset:
1796553,2018-10-09 12:32:42 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0].
1796553,2018-10-09 12:35:13 UTC,"Hello,"
1796553,2018-10-10 22:29:23 UTC,Tested:
1796553,2018-10-09 09:47:47 UTC,"My next step is to test the upstream kernels, I guess?"
1796553,2018-10-11 09:13:20 UTC,I cloned the repo and copied the new firmware to the appropriate place. Testing now.
1796554,2018-10-07 10:56:16 UTC,"StacktraceTop:
 g_variant_unref (value=0xffffffff983a3ed0) at ../../../../glib/gvariant-core.c:625
 ___lambda21_ (_data3_=0x55a163ac5aa0, _data3_=0x55a163ac5aa0, obj=<optimized out>, res=<optimized out>) at gkr/gkr@@seahorse-gkr@sta/gkr-keyring.c:1073
 ____lambda21__gasync_ready_callback (source_object=<optimized out>, res=<optimized out>, self=0x55a163ac5aa0) at gkr/gkr@@seahorse-gkr@sta/gkr-keyring.c:1115
 g_simple_async_result_complete (simple=0x55a163de1170) at ../../../../gio/gsimpleasyncresult.c:802
 on_real_prompt_completed (source=0x55a163afde20, result=0x55a163de11e0, user_data=<optimized out>) at libsecret/secret-service.c:322"
1796554,2018-10-10 16:29:53 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1796554,2019-10-09 19:30:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1796554,2019-12-09 04:17:32 UTC,[Expired for seahorse (Ubuntu) because there has been no activity for 60 days.]
1796562,2019-11-28 12:37:59 UTC,Fixed in 19.10
1796563,2018-10-22 09:18:14 UTC,img2pdf seem to do the job for the reverse operation nicely...
1796563,2020-10-20 19:36:36 UTC,"As a workaround, you can type this command :"
1796563,2019-02-11 13:55:37 UTC,"Hello,"
1796563,2018-11-01 16:13:41 UTC,"For what it's worth, we ran into this issue today as well. It looks like the related Ghostscript vulnerability is detailed here: https://www.kb.cert.org/vuls/id/332928"
1796563,2018-10-22 09:05:28 UTC,Here is an alternative to `convert document.pdf image.jpg`:
1796563,2018-10-19 16:32:09 UTC,I guess this shows that I suffer from the same issue when trying to convert image file(s) to pdf:
1796563,2018-10-08 08:18:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796563,2018-10-07 17:35:47 UTC,"Yeah, but it's not immediately obvious if you're not familiar with imagemagick internals (I certainly didn't know what policy.xml was), and it's part of 70 lines of changes."
1796563,2018-10-07 16:06:35 UTC,The package changelog mentions this:
1796563,2018-10-19 16:58:05 UTC,"Sadi, if you're willing to take the risk, you can comment the appropriate line in /etc/ImageMagick-6/policy.xml .."
1796566,2019-03-08 14:45:09 UTC,"As for options 1 or 2, 1 is fine, as it goes along with the main program, and thus is quite logical.
I wouldn't complain about 2, either, though. So, slight tendency to 1."
1796566,2019-03-05 16:49:53 UTC,"I'm not sure yet, basically there are two possibilities:
1. Create ""master"" branch and fork branch for Inkscape 1.0
   once Inkscape itself branches.
2. Create branch for 1.0 and fork ""master"" branch at some
   point in the future."
1796566,2019-06-16 15:03:31 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape-docs/documentation/issues/1 (where we can also set an appropriate milestone)
1796566,2018-10-07 22:21:20 UTC,Thank you!
1796566,2018-10-07 21:49:16 UTC,I'll try to get it done next week.
1796566,2019-03-04 22:36:14 UTC,"Patrick, what name should the new branch get?"
1796568,2018-10-07 15:51:15 UTC,Further investigation shows that SB-MOP:METHOD-LAMBDA-LIST returns an erroneous value.
1796568,2018-10-07 17:29:08 UTC,Bug pinpointed.
1796568,2018-10-07 17:30:42 UTC,"Clarification: the above fix needs to be applied to ADD-READER-METHOD (L1299), ADD-WRITER-METHOD (L1316) and ADD-BOUNDP-METHOD (L1330)."
1796568,2018-10-07 17:35:21 UTC,"Can confirm that, after making the above fix in the above methods and redefining them in a live SBCL image, SETF CLASS-NAME works as intended."
1796573,2019-08-28 02:01:43 UTC,"Pander, please open a new bug by running:"
1796573,2019-08-28 02:00:19 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1796573,2019-08-27 20:53:52 UTC,I have tried that on 19.04 with kernel 5.0.0-25-generic but it did not work. What are ways to debug this?
1796573,2019-01-31 05:43:14 UTC,Try: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/comments/34 ?
1796573,2019-01-15 09:50:17 UTC,There are two 'versions' of this issue. One for users with /sys/class/leds/*::kbd_backlight* and one for users missing /sys/class/leds/*::kbd_backlight*
1796573,2019-01-15 09:58:45 UTC,"Pander,"
1796573,2018-10-13 15:11:00 UTC,"Hello Nadav,"
1796573,2018-10-13 09:53:47 UTC,"I managed to sign vmlinuz myself and the backlight is back :)
When the official release will be?"
1796573,2018-10-09 12:39:06 UTC,"I can't upgrade my kernel because every time I do when I'm trying to boot after kernel upgrade it's giving me ""invalid signature"" error on vmlinuz (Maybe because I have dual boot?)"
1796573,2018-10-09 12:27:41 UTC,"Hello,"
1796573,2018-10-09 12:23:09 UTC,Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
1796573,2018-10-07 16:30:07 UTC,This change was made by a bot.
1796573,2018-11-06 04:22:02 UTC,"Sounds like bug 1797862, if not bug 1796550."
1796576,2018-10-07 17:25:30 UTC,Attaching dmesg output
1796576,2018-10-07 17:30:07 UTC,This change was made by a bot.
1796576,2018-10-09 17:34:13 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1796576,2018-10-14 15:17:30 UTC,"Hello,
sorry for the delay, I've tested kernel 4.15.0-38-generic, but the problem is not solved.
Wifi seems, connect, but I cannot ping my domestic router...it seems that there are some problem sending packet on the Wifi connection, rather than establishing the connection with the Wifi router...
Is there any other test I can perform?"
1796576,2018-11-02 13:56:18 UTC,"Hello,
just a quick update: using Kernel version 4.15.0-39-generic I was able to connect to wifi, but after switching on and off some times the Wifi...so the problem is partially solved, but there is still something not working fine."
1796581,2018-10-08 13:42:30 UTC,git rev-parse HEAD: ebfa7d1f7dac036d50760e0d4527f5c165d33a28
1796581,2018-10-08 09:40:00 UTC,"mmm, what commit did you test against?"
1796581,2018-10-08 10:56:08 UTC,I tried to find in the source code eeschema a place where you can create a grid in the form of lines or at least bold dots. And accidentally checked the code during the build.
1796581,2018-10-08 12:55:49 UTC,@Ivan-  Thank you for submitting this.  It is a potentially interesting and useful group of things to check.  Can you post the output of the command
1796582,2019-05-19 09:32:21 UTC,"No, I have the AMD R6xx HDMI sound chip. So I think the problem has been solved for my sound chip but not yours."
1796582,2019-05-14 01:11:00 UTC,"Doesn't work for me.  I have sound chip Realtek ALC236, is that the same as yours?"
1796582,2019-05-07 16:26:30 UTC,"For me, the problem has been resolved on Kubuntu 19.04 and the Ideapad 330-15ARR. I have the kernel 5.0.0-13-generic. I just needed to block front-right microphone in pavucontrol and it works fine."
1796582,2019-04-23 19:27:13 UTC,"Last time, I tried to boot Kubuntu 18.10 with kernel 4.15: black screen and no system init. So I don't know if it works or not."
1796582,2019-04-22 05:27:54 UTC,"Ok, please test if microphone works under v4.15."
1796582,2019-04-20 12:47:15 UTC,"No, I have the Ideapad 330 (Not S)-15ARR. But I think the microphone is the same for both."
1796582,2019-04-20 09:41:44 UTC,Do you use the same laptop as the original bug reporter?
1796582,2019-04-20 09:15:33 UTC,Bug isn't corrected in Kubuntu 19.04 in kernel 5.0.0-13-generic.
1796582,2019-03-30 08:38:07 UTC,"If v4.15 kernel works 100% of the time, then a kernel bisection can find the regression point easily."
1796582,2019-04-04 16:02:52 UTC,Not working also on 4.18.0-17-generic kernel.
1796582,2019-03-29 15:18:22 UTC,The dumb thing is: it was working!  For a while.
1796582,2019-03-07 07:13:18 UTC,Does this still happen on an up-to-date system?
1796582,2019-01-28 03:37:02 UTC,Facing similar issue in lenevo ideapad 330.
1796582,2018-10-09 17:15:12 UTC,Confirmed on kernel 4.19-rc7.
1796582,2018-10-09 12:17:26 UTC,"Hello,"
1796582,2018-10-08 14:53:52 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19-rc7 kernel[0]."
1796582,2018-10-07 18:30:07 UTC,This change was made by a bot.
1796582,2019-04-10 17:32:22 UTC,"I searched a bit about the changes in the kernel. I've found that :
https://lore.kernel.org/patchwork/patch/1030491/"
1796584,2018-10-10 10:41:01 UTC,"Hi Nikolay,"
1796584,2018-10-09 17:57:13 UTC,I did as you wrote. After command
1796584,2018-10-08 15:34:07 UTC,"> You need to install (or update) the plugin.
"
1796584,2018-10-08 15:24:30 UTC,"> MISSING - Missing Dependency or Permission or Plug-in
> INCOMPAT - Incompatible dependency-version or Plugin-version
"
1796584,2018-10-08 16:03:31 UTC,I expect you just want to print and do not care how you get there?
1796587,2019-03-14 00:38:27 UTC,"When thinking about a solution, please take bug #1564117 into consideration."
1796591,2018-10-16 18:04:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796592,2018-10-07 21:38:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608469"
1796595,2018-11-27 01:58:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796599,2018-10-08 00:25:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608474"
1796599,2019-06-13 16:20:04 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/608474
Reason: Seems as though we can't agree on a path forward here, I'm assuming Sam's head exploded long ago and just pulled this down for his cloud anyway."
1796602,2020-01-27 10:24:05 UTC,"This issue has been fixed in 0.44.12-2. The problem was, that on SIGTERM the dwarf-fortress wrapper script tried to unmount the temporary unionfs-fuse mount point and then recursively delete it. When the unmounting step failed the script would still try to delete the directory afterwards and the unionfs-fuse mount propagated all deletes into the user run directory. The new version doesn't use unionfs-fuse anymore, so the problem doesn't occur anymore."
1796606,2018-10-22 14:33:51 UTC,"Anyone affected, please share your"
1796606,2018-10-08 08:32:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796606,2019-06-06 09:33:42 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1796606,2019-06-01 02:31:41 UTC,"No errors.ubuntu.com report for 3.28.4 and 3.32.0 (where the same patch is applied), plus this fix is part of the upstream release, and so marking as verified as per the GNOME SRU release exception."
1796606,2019-05-28 21:39:50 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1796606,2019-03-27 15:03:39 UTC,This has been fixed for disco in gnome-shell 3.32.0-1ubuntu1
1796606,2019-03-11 11:35:32 UTC,"Daniel, while the fix¹ didn't landed yet it will land on 3.32.1²."
1796606,2019-03-11 01:53:42 UTC,"Are you sure it's ""fixed-upstream""? Both the upstream bugs in comment #10 are still open."
1796606,2019-06-06 09:33:24 UTC,This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.1
1796606,2019-02-18 09:28:29 UTC,"Chris,"
1796606,2019-02-06 04:54:11 UTC,"This (gnome-shell seg fault) happens to me every few times I close and reopen my laptop (though not every time).  I've uploaded them almost every time, no idea how to link it to this (or any other) bug report."
1796606,2018-12-11 07:55:17 UTC,Upstream bug (?) https://gitlab.gnome.org/GNOME/gnome-shell/issues/804
1796606,2018-11-21 01:45:03 UTC,"When I first started getting these crashes, they were triggered by attaching an external monitor, but that problem seems to have been fixed. Now, I am getting crashes when I put my laptop to sleep and then wake it up. It also destroys screen and tmux sessions somehow, so these crashes have about the same effect on the user as a kernel panic. Yet another way that systemd is broken, I guess?"
1796606,2018-10-22 17:09:21 UTC,I cannot reproduce it repeatedly. Currently gnome-tweaks opens without crashing gnome-shell.
1796606,2018-10-22 16:27:07 UTC,"Great, thanks for this.
Can you reproduce this repeatedly? If so, you've also a /var/crash file for this?"
1796606,2018-10-22 15:05:45 UTC,"Managed to reproduce the crash by launching gnome-tweaks.
Here is the log from just before the crash to after logging back in."
1796606,2019-03-07 08:55:08 UTC,Upstream(s):
1796607,2018-11-09 13:16:05 UTC,It is really super hideous that restarting the shell is crashing the entire session.
1796607,2018-12-05 21:16:01 UTC,"As the reporter of the duplicate bug 1799787, I thought that I would see if I could reproduce this problem with the latest disco daily (20181205). Unfortunately I can by taking the following steps:"
1796607,2018-12-05 22:08:24 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1796607,2018-12-13 22:07:25 UTC,I can also confirm this problem which is easily reproduced on Fedora 29 by moving an application to workspace 4 and restarting gnome-shell from workspace 4. I can restart gnome-shell from workspace 1 with no other workspaces in use which is why I thought that Fedora 29 didn't have this issue which I have seen in both Ubuntu 18.10 and Ubuntu 19.04 (the current development version).
1796607,2018-12-13 22:09:10 UTC,Also reproducible on Fedora 29
1796607,2019-03-13 10:38:18 UTC,FYI: for me this seems to be fixed in Disco with gnome-shell 3.32.0-1ubuntu1 but another problem has surfaced when restarting gnome-shell: bug 1819890
1796607,2018-12-14 23:15:52 UTC,"Reported upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/853"
1796607,2019-01-10 15:02:31 UTC,Similar problem has been detected:
1796607,2019-03-18 22:54:05 UTC,"Seems upstream diagnosed and fixed this bug in their master branch two weeks ago, and the fix indeed got included in 3.32 (first in 3.31.92, though it seems to have been omitted from their changelog/NEWS file)."
1796607,2018-11-09 13:10:05 UTC,Similar problem has been detected:
1796607,2018-12-14 23:10:30 UTC,*** Bug 1659662 has been marked as a duplicate of this bug. ***
1796607,2018-11-06 14:10:49 UTC,"Created attachment 1502490
File: var_log_messages"
1796607,2018-12-14 23:14:21 UTC,I've also reported the issue to GNOME - https://gitlab.gnome.org/GNOME/gnome-shell/issues/853
1796607,2018-11-06 14:10:46 UTC,"Created attachment 1502488
File: open_fds"
1796607,2018-11-06 14:10:28 UTC,"Description of problem:
alt-f2, r to restart the shell"
1796607,2018-11-06 14:10:34 UTC,"Created attachment 1502478
File: backtrace"
1796607,2018-11-06 14:10:47 UTC,"Created attachment 1502489
File: proc_pid_status"
1796607,2018-11-06 14:10:37 UTC,"Created attachment 1502480
File: core_backtrace"
1796607,2018-10-29 08:28:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796607,2018-11-06 14:10:38 UTC,"Created attachment 1502481
File: cpuinfo"
1796607,2018-11-06 14:10:35 UTC,"Created attachment 1502479
File: cgroup"
1796607,2018-11-06 14:10:40 UTC,"Created attachment 1502483
File: environ"
1796607,2018-11-06 14:10:41 UTC,"Created attachment 1502484
File: exploitable"
1796607,2018-11-06 14:10:42 UTC,"Created attachment 1502485
File: limits"
1796607,2018-11-06 14:10:44 UTC,"Created attachment 1502486
File: maps"
1796607,2018-11-06 14:10:45 UTC,"Created attachment 1502487
File: mountinfo"
1796607,2018-11-06 14:10:39 UTC,"Created attachment 1502482
File: dso_list"
1796610,2018-10-08 07:21:24 UTC,I found part of the issue - related to the MongoDB ReplicaSet not being initialized properly.
1796614,2019-07-22 04:12:29 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1796614,2019-02-21 23:32:13 UTC,"I had the same problem, and also solved it with uncommenting WaylandEnable=false in /etc/gdm3/custom.conf."
1796614,2018-11-21 02:06:04 UTC,The same workaround seems to be working for bug 1798790. Although that is about the proprietary Nvidia driver and this one is about nouveau (which also means Jeffery seems to be commenting on the wrong bug). Not sure if we can or should merge the two bugs.
1796614,2018-11-20 17:04:42 UTC,Caveat:
1796614,2018-11-20 16:56:52 UTC,I also have this problem.
1796614,2018-10-18 07:27:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796614,2018-10-22 00:19:10 UTC,Hi guys! (Daniel? Since you seem to be the only one reading this :)
1796614,2018-10-17 01:39:41 UTC,It appears to be just us right now :)
1796614,2018-10-16 21:28:34 UTC,"I don't know if anyone's tuned into this bug anymore, but are there any other verbose / debug logs I could attach to help move this one closer to resolution?"
1796614,2018-10-15 02:11:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796614,2018-10-15 02:09:30 UTC,I think the right answer is to reopen bug 1795637. Unless you can convince people to move the remaining discussion into this bug.
1796614,2018-10-14 18:51:45 UTC,Not sure if there's a way to mark this bug as duplicated by the upstream Gnome one.
1796614,2018-10-14 18:50:12 UTC,Hi there. Thanks for the triage. As per https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/comments/25 this bug isn't a duplicate of the bug you mention. I've removed the duplicate notation.
1796614,2018-10-08 03:22:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1795637, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1796614,2018-10-17 20:00:04 UTC,Done!
1796622,2020-03-17 15:35:55 UTC,SRUing the newer version failed since it changed behaviour in some configuration which created issue for existing users.
1796622,2019-02-24 20:39:46 UTC,"The bionic fix is included in the upstream 1.10.14 release:
https://launchpad.net/ubuntu/+source/network-manager/1.10.14-0ubuntu1"
1796622,2019-02-24 20:34:15 UTC,This is fixed in Disco; I opened Bionic and Cosmic tasks since the bug needs to be open in some way for it to be tracked.
1796622,2018-12-11 09:31:44 UTC,"The issue was fixed in 1.12.6 which has been uploaded to disco, https://launchpad.net/ubuntu/+source/network-manager/1.12.6-0ubuntu1"
1796622,2018-10-12 07:59:42 UTC,"It should be yes, but I'd like to look at the changes needed before going any further.  Looking at the diff, it doesnt look too bad for the current version on n-m.  With some luck it will be backported by upstream, if not we'll take a look."
1796622,2018-10-11 13:36:20 UTC,Investigation found that DAD timeout for IPv6 seems to be not implemented for network manager [1]. And only support up to IPv4. It looks like a limitation but couldn't find any writing confirmation for this limitation.
1796622,2018-10-11 13:27:13 UTC,Upstream fix:  https://github.com/NetworkManager/NetworkManager/pull/228
1796622,2018-10-11 13:23:44 UTC,Upstream issue reported:
1796622,2018-10-11 11:00:01 UTC,Spoke to upstream.  They will look in to this and get it fixed.  I've asked David to log it upstream and we can link to that here.
1796622,2018-10-11 06:13:42 UTC,"Hi Bryan,"
1796622,2018-10-10 18:58:18 UTC,"Hi David,"
1796622,2018-10-12 06:48:41 UTC,"Thank you Will!
We are running Ubuntu 16.04 with network-manager version 1.2.6, that will be fixed too?"
1796627,2019-11-18 09:55:54 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/694737"
1796627,2020-02-14 22:39:18 UTC,This issue was fixed in the openstack/python-mistralclient 4.0.0 release.
1796627,2019-12-13 17:31:18 UTC,This issue was fixed in the openstack/mistral 10.0.0.0b1 development milestone.
1796627,2019-12-03 11:31:55 UTC,"Reviewed:  https://review.opendev.org/694737
Committed: https://git.openstack.org/cgit/openstack/python-mistralclient/commit/?id=7cea381bfe6a5bd7213d2cd990ffbc34a8ba2273
Submitter: Zuul
Branch:    master"
1796627,2019-11-12 11:31:47 UTC,"Reviewed:  https://review.opendev.org/686929
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=6b862e625e0b59cb7d3806a119fdd223227c06c2
Submitter: Zuul
Branch:    master"
1796627,2019-10-06 09:07:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686929"
1796627,2019-08-28 06:27:18 UTC,Your last suggestion looks good to me.
1796627,2018-11-20 14:57:43 UTC,Thinking about it again i realized it's maybe better to improve existing tools rather than creating new once. So with this in mind i think the following should be done here:
1796627,2018-11-19 16:13:49 UTC,Maybe we should expand the expiration policy. Giving the option to not delete workflows in an error state (or maybe having a longer expiration for error state etc.)
1796627,2018-10-22 14:45:26 UTC,we currently do not use execution expiration policies as we can not filter the executions which are supposed to be deleted. so far we only automatically delete successful workflows and keep the once with error for further manual investigation.
1796627,2018-10-08 15:04:41 UTC,Do you use the execution expiration policy? https://docs.openstack.org/mistral/latest/main_features.html#execution-expiration-policy
1796628,2020-03-10 06:56:50 UTC,Could you please let us know if the problem still happens with all the changes that have been made to the charm recently?
1796628,2020-06-14 04:17:32 UTC,[Expired for Grafana Charm because there has been no activity for 60 days.]
1796628,2020-10-13 07:21:59 UTC,Getting the same both on ussuri and rocky UCA of ceph.
1796634,2018-11-19 14:09:14 UTC,This bug was fixed in the package linux-firmware - 1.157.21
1796634,2018-11-19 12:15:00 UTC,This bug was fixed in the package linux-firmware - 1.173.2
1796634,2018-11-19 11:55:21 UTC,This bug was fixed in the package linux-firmware - 1.175.1
1796634,2018-11-19 11:45:21 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1796634,2018-11-09 10:46:25 UTC,"Hello AceLan, or anyone else affected,"
1796634,2018-11-09 10:46:59 UTC,"Hello AceLan, or anyone else affected,"
1796634,2018-11-09 10:45:37 UTC,"Hello AceLan, or anyone else affected,"
1796634,2018-10-08 07:55:45 UTC,"commit 534daf431c88b24236d23572039cdd79223b246a
Author: Balakrishna Godavarthi <email address hidden>
Date:   Mon Sep 17 15:29:33 2018 +0530"
1796634,2018-11-13 05:15:36 UTC,Verified by Delivery Team's Ethan Hsieh.
1796642,2018-10-08 09:03:58 UTC,"Note, with the matching versions, a command 'podman ps' works. Except that then my test container crashes, see https://github.com/containers/libpod/issues/1602"
1796642,2018-10-08 14:37:22 UTC,"To w/a that we could bind mount podman and conmon into containers that want to use podman CLI.
But the very thing to do so is no go, see https://github.com/containers/libpod/issues/1602#issuecomment-427820978 :"
1796642,2018-10-31 10:31:53 UTC,Marking that invalid as the current approach is using nsenter and enter the host mounts namespace
1796642,2018-11-05 10:59:08 UTC,"I think the issue is still valid, as we install podman via kolla overrides. The way to go may be a side car container, see http://lists.openstack.org/pipermail/openstack-dev/2018-November/136272.html"
1796645,2019-01-09 09:17:29 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1796645,2019-10-14 08:16:36 UTC,Superceeded by later ceph release.
1796645,2019-02-05 08:23:29 UTC,Thanks for updating Ceph on Bionic and Xenial/Queens.
1796645,2019-01-09 09:17:31 UTC,"This bug was fixed in the package ceph - 12.2.8-0ubuntu0.18.04.1~cloud0
---------------"
1796645,2019-01-08 17:26:19 UTC,"The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1796645,2019-01-08 17:26:05 UTC,This bug was fixed in the package ceph - 12.2.8-0ubuntu0.18.04.1
1796645,2018-12-03 23:53:58 UTC,What are the plans for cosmic here? Comment #2 seems valid.
1796645,2018-12-03 13:55:58 UTC,xenial-queens/proposed testing:
1796645,2018-12-03 11:57:50 UTC,bionic-proposed testing:
1796645,2018-11-02 12:00:57 UTC,"Hello James, or anyone else affected,"
1796645,2018-10-31 00:11:05 UTC,I think this needs to get pushed to cosmic as well. Cosmic has 12.2.4 which created a bit of a mess on upgrade from bionic.
1796645,2018-10-19 19:22:48 UTC,"Hello James, or anyone else affected,"
1796645,2018-12-04 08:25:21 UTC,See bug 1805355 - which re-introduced ceph 13.2.1 back into cosmic (as it sat in proposed for most of the cycle waiting for a MIR to complete).
1796647,2018-10-09 17:23:37 UTC,apport information
1796647,2018-10-09 18:16:38 UTC,"My understanding of the issue after an IRC conversation with sforshee is that the modules were intentionally dropped from the kernel packages, but the corresponding Provides of virtualbox-guest-modules was _not_ dropped from the kernel packaging.  This means that when we install virtualbox-guest-utils during image build, it sees the modules as already available so does nothing.  (Instead, it should have to fulfil the dependency some other way, probably by installing the DKMS packages which build the drivers)."
1796647,2018-10-09 20:58:43 UTC,"So I just go ""vagrant init ubuntu/cosmic64 && vagrant up""... which works for all other vagrant I'm wanting to use."
1796647,2018-10-09 21:26:03 UTC,The box certainly needs to be fixed.
1796647,2018-10-10 08:06:03 UTC,"As I saw cosmic64 box available so I thought test it out. Using my standard vagrant examples to see if they all still work or no on cosmic. I'm in the process of setting up jenkins instance to check for available box updates for the examples I've setup, then rebuild and see if the examples still work."
1796647,2019-02-14 13:11:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1796647,2018-10-16 12:20:21 UTC,"Cheers all,
Just updated myself and picked up '20181015.0.0' and vagrant up works cleanly.
John"
1796647,2018-10-16 13:46:05 UTC,"On Tue, Oct 16, 2018 at 12:20:21PM -0000, John Patrick wrote:

> Cheers all,
> Just updated myself and picked up '20181015.0.0' and vagrant up works cleanly.
> John
"
1796647,2019-02-14 16:54:41 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1796647,2018-10-15 17:46:59 UTC,"Hi John,"
1796647,2018-10-09 17:23:36 UTC,apport information
1796647,2018-10-09 17:23:35 UTC,apport information
1796647,2018-10-09 17:23:33 UTC,apport information
1796647,2018-10-09 17:23:32 UTC,apport information
1796647,2018-10-09 17:23:30 UTC,apport information
1796647,2018-10-09 17:23:29 UTC,apport information
1796647,2018-10-09 17:23:27 UTC,apport information
1796647,2018-10-09 17:23:26 UTC,apport information
1796647,2018-10-09 17:23:24 UTC,"ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116,  1 Oct  9 16:18 seq
 crw-rw---- 1 root audio 116, 33 Oct  9 16:18 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.10
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcEnviron:
 LC_CTYPE=C.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:"
1796647,2018-10-09 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1796647,2018-10-09 16:31:21 UTC,It looks like the appropriate modules are no longer shipped in the linux-modules-...-generic package (which is where they were in bionic); I'm following up with the kernel team to check if there's an existing bug to track this or if I need to file a new one (or repurpose this one).
1796647,2018-10-09 16:21:10 UTC,"Hi John,"
1796647,2018-10-09 09:29:10 UTC,"Just tried latest version and still has same error;
ubuntu/cosmic64    (virtualbox, 20181008.0.0)"
1796649,2018-10-09 21:39:36 UTC,"kernel-bug-exists-upstream
Last time when there was no problem:
Sun Sep 16 23:37:50 2018 CST"
1796652,2018-10-08 10:13:45 UTC,"""/home/username/T%C3%A9l%C3%A9chargements/"" is the default download directory in french so it's  can be a problem for some french speaking users."
1796652,2019-02-14 14:51:36 UTC,That looks similar to https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/4
1796653,2019-06-18 21:40:03 UTC,"Note, it's possible to edit the constraints on a deployed application - e.g. juju set-constraints cinder spaces=ceph-access-space.  This doesn't affect the bindings at all, but can at least mean that the unit has an interface in the needed space."
1796653,2019-10-10 13:06:48 UTC,"We have hit this bug in a different customer were barbican-vault didn't have a correct binding for the secrets-storage relation to vault. When sending the secrets_relation_request to vault it used the incorrect IP (i.e. an IP it is not using to communicate with the vault unit). The barbican-vault charm, in turn, assigned the incorrect IP to the cidr bounds for the role and secret ID."
1796653,2019-06-05 22:21:09 UTC,For further references the mentioned issue with the memcached binding has been documented here: https://docs.openstack.org/charm-guide/latest/1904.html#adding-nova-cloud-controller-memcached-relation
1796653,2019-11-01 21:14:51 UTC,This is in 2.7-rc1 so marking fix-committed as part of the networking improvements in the 2.7 series.
1796653,2019-10-10 13:35:58 UTC,Thanks for the update. We're actively working on this and have it going into the 2.7 release. We're glad that this will be useful/helpful.
1796653,2019-05-03 14:34:24 UTC,"This bug is also related to bug 1827397. After an upgrade to OS Charms 19.04, nova-cloud-controller could not connect to the memcached application. ""Connection refused"" errors were not reported by charm-nova-cloud-controller nor the Nova API logs. In the end, we had to redeploy the memcached application with a matching binding, but it would have been less disruptive to update the ""cache"" binding."
1796653,2019-05-16 07:58:00 UTC,"As a follow-up to comment #8, we also had gnocchi and designate related to memcached, but their bindings was different that nova-cloud-controller. That sounds like a mistake, but the only ways forward to fix the problem were:
1) redeploy gnocchi and designate to match the same nova-cloud-controller binding, or
2) deploy a new memcached application (ie. memcached-internal) to work with gnocchi and designate (while leaving the memcached application related to n-c-c)"
1796653,2019-04-17 14:51:02 UTC,"For an actual use case, please see bug:"
1796653,2019-04-14 12:41:28 UTC,"Note that if you have a default binding ("""": foo) I believe that all new
endpoints currently inherit the default binding. So often it isn't there is
*no* binding, but certainly it could be the *wrong* binding."
1796653,2019-04-12 20:32:57 UTC,After a conversation there's two potential use cases/issues at play here.
1796653,2019-04-12 20:06:01 UTC,Thanks for the updated information.
1796653,2019-04-12 20:00:12 UTC,"We have a scenario which has surfaced as a release blocker for OpenStack Charms, with this bug at its core."
1796653,2019-04-17 14:52:12 UTC,"This will become an more urgent issue as many production clouds today leverage network space bindings, and will need to be able to transform applications in those clouds, including new relations on previously-undeclared bindings."
1796653,2018-10-08 11:47:37 UTC,"Thanks, this is definitely something on our roadmap todo list and we could use field requests for this during planning sprints."
1796657,2018-10-08 10:44:39 UTC,"I've added as an attachment a .desktop file that, once saved in /usr/share/applications, enables umlet to be listed in Ubuntu's launcher."
1796661,2019-05-13 11:34:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796661,2020-01-02 22:56:13 UTC,I'm hopeful this (ie the end-user-facing issue; we've not changed what temp dir is used) would be fixed on current nightlies ( https://nightly.mozilla.org/ ) based on bug 1555644 being fixed on Linux/macOS now. Would it be possible for you to verify if your issue is resolved on nightly?
1796661,2019-05-19 08:35:56 UTC,Confirming that the patch described here [0] has fixed the issue (tested today running Ubuntu 19.04 with mainline kernel 5.1.3.
1796661,2019-05-13 12:23:15 UTC,"Just adding this for others who are looking for help.
Following Troels' suggestion, this can be overcome with by binding /tmp/ to a directory in your home directory:"
1796661,2019-05-06 13:35:30 UTC,(In reply to Troels Liebe Bentsen from comment #4)
1796661,2019-01-27 20:20:19 UTC,There is also a bit of discussion on changing the behaviour of fscrypt to use EXDEV instead:
1796661,2019-01-22 07:35:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796661,2019-01-21 23:48:13 UTC,"The issue is because firefox does a rename from the /tmp folder to the encrypted home folder, right now fscrypt returns EPERM instead of EXDEV that would be normal when the operation can not complete because of crossing a mount point or in this case unencrypted to an encrypted folder."
1796661,2019-01-21 23:36:53 UTC,Don't really know if this is the right location:
1796661,2019-01-21 23:26:53 UTC,It seems Firefox downloads the file to a folder under /tmp and then tries to rename the file to the final location:
1796661,2019-01-19 14:59:21 UTC,I can confirm this bug and will create a bug report on bugzilla :)
1796661,2019-01-18 10:51:47 UTC,User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0
1796661,2018-10-10 16:02:10 UTC,That sounds like an upstream issue. Would you mind filing a bug report at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and sharing the link to it here?
1796661,2019-01-23 16:20:35 UTC,(In reply to Troels Liebe Bentsen from comment #2)
1796662,2019-02-18 14:07:43 UTC,"Can you post here a code snipped to integrate in the documentation?
As far as I remember, you wrote some."
1796662,2019-05-21 04:17:17 UTC,[Expired for Dr. Geo II because there has been no activity for 60 days.]
1796670,2018-10-08 11:55:46 UTC,"see also
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725284"
1796684,2018-10-09 15:22:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1796688,2018-10-08 14:18:58 UTC,"https://jtacworkbench.juniper.net/api/download-manager/download?caseId=2018-1005-0336&attId=2018-1005-03360007151705 (cz296-ncctrl1m.tar.gz)
https://jtacworkbench.juniper.net/api/download-manager/download?caseId=2018-1005-0336&attId=2018-1005-03360007151704 (cz296-ncctrl2m.tar.gz)
https://jtacworkbench.juniper.net/api/download-manager/download?caseId=2018-1005-0336&attId=2018-1005-03360007151703 (cz296-ncctrl0m.tar.gz)
https://jtacworkbench.juniper.net/api/download-manager/download?caseId=2018-1005-0336&attId=2018-1005-03360007151701 (vrouter)"
1796689,2020-02-24 20:00:44 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/709603"
1796689,2020-08-18 02:36:42 UTC,"Reviewed:  https://review.opendev.org/709600
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f8a721ae85cab44754b8e64434e90f4c2afa89aa
Submitter: Zuul
Branch:    stable/pike"
1796689,2020-02-24 19:48:53 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/709600"
1796689,2019-03-24 23:04:29 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1796689,2019-03-22 03:46:27 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1796689,2019-02-22 03:54:36 UTC,"Reviewed:  https://review.openstack.org/632516
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=70b4cdce68f9b1543c032aa700e4f0f4289d90a6
Submitter: Zuul
Branch:    stable/queens"
1796689,2018-12-19 10:01:35 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1796689,2018-11-12 18:18:35 UTC,"Reviewed:  https://review.openstack.org/613853
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=133b194ba079abe84900d09a5c3c74ef9f464bab
Submitter: Zuul
Branch:    stable/rocky"
1796689,2018-10-29 08:16:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/613853"
1796689,2018-10-27 08:58:03 UTC,"Reviewed:  https://review.openstack.org/608685
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=afc3a16ce3364c233e6e1cffc9f38987d1d65318
Submitter: Zuul
Branch:    master"
1796689,2018-10-08 14:17:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608685"
1796689,2019-01-22 17:23:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/632516"
1796690,2019-01-07 15:56:46 UTC,btw the menu bar is displayed correctly with current master (2.3)
1796690,2020-06-22 14:15:30 UTC,Cannot be fixed until someone is able to find out why this happens on Ubuntu/.
1796690,2020-06-22 14:10:54 UTC,Visibility issues on Ubuntu/Mint have also been reported in the forums for both 2.2 and 2.3:
1796690,2019-01-07 15:56:16 UTC,"@ronso0 @dj_segfault
I guess you both ignored my ;) Of course it's a bug.
""feature"" because with this bug I got rid of another distraction = information in my visual range that I rarely need."
1796690,2018-10-08 14:52:04 UTC,2md screen shot
1796690,2019-01-07 07:18:39 UTC,I don't see how you can consider it a feature that saves space when the space is still taken up by the menu; it's just not visible.
1796690,2018-10-09 13:03:37 UTC,"btw: right now I consider this a feature rather than a bug ;)
The menu bar is still stealing vertical space but at least it's 'invisble' which is fine regarding I use it once or twice (at most) a session, and it can't be styled by the OS theme."
1796690,2018-10-08 22:32:58 UTC,"This also happpens with 18.04 and xfce desktop
* start in windowed mode = black text on grey
* switch to fullscreen = black text on almost black
* switch back to window mode = black background remains"
1796690,2019-01-07 07:57:41 UTC,"@ronso0: I agree with dj_segfault that this is not a feature for me as it makes using the menu difficult. If I can choose to turn this on or off, maybe, but not a default choice."
1796698,2019-12-31 15:55:30 UTC,"Mike Kaganski committed a patch related to this issue.
It has been pushed to ""master"":"
1796698,2019-12-31 15:13:37 UTC,https://gerrit.libreoffice.org/c/core/+/86046
1796698,2020-01-05 02:14:27 UTC,Mike Kaganski: Thanks for the fix. Any plan to backport this to libreoffice-6-3 and libreoffice-6-4 branch?
1796698,2019-09-25 13:25:01 UTC,Synchronising bug status with upstream.
1796698,2020-01-08 15:07:49 UTC,"Mike Kaganski committed a patch related to this issue.
It has been pushed to ""libreoffice-6-4"":"
1796698,2020-01-09 09:01:49 UTC,"Mike Kaganski committed a patch related to this issue.
It has been pushed to ""libreoffice-6-3"":"
1796698,2020-01-08 13:20:02 UTC,"(In reply to Kevin Suo from comment #8)

> Mike Kaganski: Thanks for the fix. Any plan to backport this to
> libreoffice-6-3 and libreoffice-6-4 branch?
"
1796698,2019-12-31 12:29:45 UTC,"Actually, although the problem actually doesn't manifest now for majority of cases, it still is reproducible like this:"
1796698,2018-10-11 07:40:42 UTC,"Ok, upstream report filled at https://bugs.documentfoundation.org/show_bug.cgi?id=120502"
1796698,2019-12-10 04:08:59 UTC,"Dear Aidas Kasparas,"
1796698,2018-11-22 19:13:30 UTC,Repro.
1796698,2018-10-11 07:58:26 UTC,Thanks!
1796698,2018-10-11 07:40:11 UTC,"Created attachment 145586
Example file"
1796698,2018-10-11 07:38:59 UTC,"Description:
LibreOffice Calc can handle only 1024 columns, but default style says it apply style to column 1025 too. If such .xlsx document is processed with PhpOffice and single cell value is written, <col> nodes gets expanded, including for <col min=""1025"" max=""1025""/>. This column cannot be processed by LibreOffice Calc and produces warnings that some information is lost."
1796698,2018-10-10 16:07:51 UTC,Thanks for the report. Could you please file an upstream bug report at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and share the link to it here?
1796698,2019-12-30 08:36:47 UTC,fixed after https://git.libreoffice.org/core/+/071d72cc3662168c58358ce53a77ceacbf80f545%5E%21
1796701,2018-10-08 23:55:06 UTC,*** This is an automated message ***
1796701,2018-11-22 04:54:46 UTC,Dear Ubuntu developers.
1796703,2018-10-23 04:00:04 UTC,"Thanks Slawek for information. I'll try to debug this script and provide more info.
About 11.0.2.dev2 version, we deployed OpenStack more than several moth ago when Pike 16.0.1 was latest release. Currently we can't perform update to not affect important services running on VMs."
1796703,2018-10-11 15:34:41 UTC,So your version is 11.0.2.dev2 - is that from a vendor?  It doesn't correspond to an upstream tag.  The latest tagged version of Pike is 11.0.5 so perhaps you can try with a later version?
1796703,2018-10-11 07:41:50 UTC,"Thx Andrii for reporting this issue.
In fact it's hard to say why it happened like that.
About Your question where keepalived.conf is prepared, it's in https://github.com/openstack/neutron/blob/master/neutron/agent/linux/keepalived.py which is used later by this class: https://github.com/openstack/neutron/blob/master/neutron/agent/l3/ha_router.py#L60"
1796708,2019-01-29 16:33:46 UTC,Just hit this again: http://logs.openstack.org/66/633566/1/check/tempest-full-pike/4719f27/controller/logs/screen-c-vol.txt.gz?level=TRACE#_Jan_29_14_55_55_994454
1796713,2018-10-09 12:41:52 UTC,I'm wondering about the source of these symbols... there are viewbox attributes to symbols in the file that are not found in other symbol files.
1796713,2018-10-09 12:57:25 UTC,"Hi,"
1796713,2018-10-10 19:42:10 UTC,"I can't say that *everything* will work, but the scale and position seem to work properly when the viewbox attributes are removed."
1796713,2018-10-13 08:28:01 UTC,Thank you. This seems to fix my issues. I opened a PR at https://github.com/Xaviju/inkscape-open-symbols/pull/100 for the removal of the viewBox.
1796720,2018-10-09 13:47:44 UTC,@Daniel:
1796720,2018-10-09 18:23:11 UTC,Help Joseph!
1796720,2018-10-09 18:03:46 UTC,@Cristian
1796720,2018-10-09 13:58:03 UTC,"Report in kernel.org
""Power consumption RX560 idle raised from 7 W to 13 W""
--
Cristian Aravena Romero (caravena)"
1796720,2018-10-09 11:36:43 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0].
1796720,2018-10-09 18:29:04 UTC,"Hello,"
1796720,2018-10-08 20:58:38 UTC,"Created attachment 278965
git diff -p 93b100ddda3be284be160e9ccba28c7f8f21ab73..93b100ddda3be284be160e9ccba28c7f8f21ab73^1"
1796720,2018-10-08 19:59:04 UTC,"(In reply to quirin.blaeser from comment #27)

> I can´t find ""c3df50abc84b"" from https://lkml.org/lkml/2018/9/15/172
> but ""drm/amd/pp: Convert clock unit to KHz as defined"" is
> 23ec3d1479fd79658cd52c47618d8ddd2f32550b
"
1796720,2018-10-08 19:49:14 UTC,"I can´t find ""c3df50abc84b"" from https://lkml.org/lkml/2018/9/15/172
but ""drm/amd/pp: Convert clock unit to KHz as defined"" is 23ec3d1479fd79658cd52c47618d8ddd2f32550b"
1796720,2018-10-08 19:42:16 UTC,"(In reply to quirin.blaeser from comment #25)

> (In reply to Alex Deucher from comment #24)
> > This patch shouldn't have been applied to 4.18.  It looks like it was
> > autoselected:
> > https://lkml.org/lkml/2018/9/15/172
> > It should be reverted.
>
> So ""[...]the display component was requesting minimum clocks[...]"" isn´t an
> issue with Polaris?
> Is there any QA left?
> Avoiding unusual units is a good idea generally, but it should happen very
> early in development.
"
1796720,2018-10-08 20:59:36 UTC,"(In reply to Alex Deucher from comment #28)

> (In reply to quirin.blaeser from comment #27)
> > I can´t find ""c3df50abc84b"" from https://lkml.org/lkml/2018/9/15/172
> > but ""drm/amd/pp: Convert clock unit to KHz as defined"" is
> > 23ec3d1479fd79658cd52c47618d8ddd2f32550b
>
> That was the commit id in our amd-staging-drm-next branch:
> https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-
> next&id=c3df50abc84b289be8e7b96968d7d7e006576880
"
1796720,2018-10-10 11:26:01 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18.13 kernel[0].
1796720,2018-10-08 19:34:55 UTC,"(In reply to Alex Deucher from comment #24)

> This patch shouldn't have been applied to 4.18.  It looks like it was
> autoselected:
> https://lkml.org/lkml/2018/9/15/172
> It should be reverted.
"
1796720,2018-10-10 13:42:12 UTC,"Yes, it should. GregKH reverted the offending commit in  4.18.13."
1796720,2018-10-10 18:48:13 UTC,I can confirm that the problem is fixed in 4.18.13:
1796720,2018-10-14 20:53:42 UTC,"Excelent! Thanks You...
--
Cristian Aravena Romero (caravena)"
1796720,2018-10-16 16:44:46 UTC,I have tried the latest Ubuntu 18.10 kernel (4.18.0-10.11) available here:
1796720,2018-10-16 17:11:08 UTC,"Hello Daniel,"
1796720,2018-10-24 16:39:39 UTC,today received update to kernel version 4.18.0-11.12 and the problem is not fixed yet...
1796720,2018-10-24 17:19:24 UTC,"Help Joseph!
--
Cristian"
1796720,2018-11-06 17:07:47 UTC,"Daniel,"
1796720,2018-11-06 18:16:19 UTC,"Hi Cristian,"
1796720,2018-11-15 18:02:14 UTC,This kernel update didn't fix the the high power consumption on my Radeon RX580 GPU.
1796720,2018-11-15 21:37:27 UTC,"Thanks a lot.
This worked OK. I used kernel 4.19.1, but now I have removed it and I have also removed the ""proposed package"" setting.
The power draw from the wall outlet at idle is now back to the normal 63W-65W."
1796720,2018-10-10 11:39:14 UTC,"Hello,"
1796720,2018-10-08 17:30:07 UTC,This change was made by a bot.
1796720,2018-11-15 18:25:25 UTC,"Dear Per-Inge,"
1796720,2018-10-08 14:26:57 UTC,"This patch shouldn't have been applied to 4.18.  It looks like it was autoselected:
https://lkml.org/lkml/2018/9/15/172
It should be reverted."
1796720,2018-09-28 16:51:31 UTC,"Created attachment 278829
lsusb lspci cpuinfo config url sensors"
1796720,2018-09-28 17:11:57 UTC,Can you bisect?
1796720,2018-09-28 18:14:20 UTC,"Git bisect howto:
https://www.kernel.org/doc/html/v4.18/admin-guide/bug-bisect.html"
1796720,2018-09-28 21:51:16 UTC,"Am 28.09.18 um 20:14 schrieb <email address hidden>:

> https://bugzilla.kernel.org/show_bug.cgi?id=201275
>
> --- Comment #2 from Alex Deucher (<email address hidden>) ---
> Git bisect howto:
> https://www.kernel.org/doc/html/v4.18/admin-guide/bug-bisect.html
>


Sounds prakticable, but may take 1-2 days."
1796720,2018-09-29 02:44:41 UTC,I can second that for RX580 (Polaris20)
1796720,2018-09-29 21:20:33 UTC,"Created attachment 278841
bisect result"
1796720,2018-09-29 21:28:30 UTC,"RX560 is Polaris11, so Bug may be ported from Polaris20"
1796720,2018-09-30 14:07:38 UTC,For now i have resolved this problem by simply removing patch for 4.18.11
1796720,2018-10-04 17:56:53 UTC,"4.18.12
Bug still present, removing 93b100ddda3be284be160e9ccba28c7f8f21ab73 solves this problem for now."
1796720,2018-10-04 20:21:41 UTC,"I don't think this is a bug.  The problem is, prior to that patch, the display component was requesting minimum clocks that were 10x too low.  This saved power, but led to display problems on some systems because the clocks were too low to sustain the display requirements."
1796720,2018-10-04 22:48:47 UTC,"(In reply to Alex Deucher from comment #9)

> I don't think this is a bug.  The problem is, prior to that patch, the
> display component was requesting minimum clocks that were 10x too low.  This
> saved power, but led to display problems on some systems because the clocks
> were too low to sustain the display requirements.
"
1796720,2018-10-05 02:37:12 UTC,Can you attach the output of `cat /sys/kernel/debug/dri/0/amdgpu_pm_info` before and after the patch?
1796720,2018-10-08 17:25:31 UTC,this report is from running lm-sensor when system is idle:
1796720,2018-10-05 03:41:47 UTC,amd-staging-drm-next (with broken SDDM and then 'init 3')
1796720,2018-10-07 09:20:01 UTC,"drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_services.c (v4.18.12)
There is a lot of work to do:"
1796720,2018-10-07 00:34:38 UTC,"Created attachment 278939
bisect"
1796720,2018-10-06 10:43:21 UTC,I can confirm that only 4.18.x (x > 9) is affected. 4.19-rc6 reports the same clock and power values as with 4.18.9. At least that's the case for my RX 560.
1796720,2018-10-05 22:18:46 UTC,"(In reply to Michel Dänzer from comment #19)

> People on the Phoronix forum mentioned that this doesn't seem to happen with
> 4.19-rc kernels. If people here can confirm that, maybe there are other
> corresponding changes that need to be backported as well.
"
1796720,2018-10-05 14:44:38 UTC,"People on the Phoronix forum mentioned that this doesn't seem to happen with 4.19-rc kernels. If people here can confirm that, maybe there are other corresponding changes that need to be backported as well."
1796720,2018-10-05 03:04:04 UTC,openSUSE Tumbleweed Kernel:stable 4.18.12-2.ga880bd8-default
1796720,2018-10-05 11:52:39 UTC,I can confirm the issue with Polaris10. Power consumption is roughly 30 Watts higher in idle compared to what it used to be and compared to Windows. DPM are stuck in highest power modes for both s and m.
1796720,2018-10-05 08:25:45 UTC,"Created attachment 278933
amdgpu_pm_info"
1796720,2018-10-05 03:52:06 UTC,"(In reply to Dieter Nützel from comment #14)

> Diff !!!
>
> BAD
> Host Data Path Light Sleep: Off
"
1796720,2018-10-05 03:43:19 UTC,Diff !!!
1796720,2018-10-05 13:50:25 UTC,"(In reply to Alex Deucher from comment #9)

> I don't think this is a bug.  The problem is, prior to that patch, the
> display component was requesting minimum clocks that were 10x too low.  This
> saved power, but led to display problems on some systems because the clocks
> were too low to sustain the display requirements.
"
1796737,2018-10-31 19:02:37 UTC,"Reviewed:  https://review.openstack.org/608777
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a99722bb854d2ba99c3abc2d2738ba281148fde4
Submitter: Zuul
Branch:    master"
1796737,2018-12-19 10:01:32 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1796737,2018-12-07 18:11:43 UTC,"Reviewed:  https://review.openstack.org/614588
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=980013d7008aff3f83d9de646417f387b29dc1df
Submitter: Zuul
Branch:    stable/rocky"
1796737,2018-12-07 18:11:31 UTC,"Reviewed:  https://review.openstack.org/614587
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d4ec96611c76128d0b8e0c7066ddda0490209565
Submitter: Zuul
Branch:    stable/rocky"
1796737,2018-10-31 18:39:50 UTC,"Reviewed:  https://review.openstack.org/608771
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cb36ca76df788d45d70059b074691f7f3453b8fa
Submitter: Zuul
Branch:    master"
1796737,2019-03-22 03:47:00 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1796737,2018-10-31 16:48:29 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614587"
1796737,2018-10-08 21:38:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/608777"
1796737,2018-10-08 21:06:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/608771"
1796737,2018-10-08 18:22:32 UTC,Marked as medium severity since this is mostly only a problem if you're using the DiskFilter which is deprecated.
1796737,2018-10-31 16:48:47 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614588"
1796743,2018-10-17 01:00:29 UTC,Fixed in 4.19-rc7.
1796743,2018-10-09 20:09:24 UTC,"Excellent! Thank you...
--
Cristian Aravena Romero (caravena)"
1796743,2018-10-09 19:56:03 UTC,Yay this is in fact fixed in 4.19-rc7! Thanks very much this was a real show stopper :)
1796743,2020-02-11 16:11:03 UTC,Hi! This is definitely fixed in Ubuntu 20.04 - my laptop now sleeps like a champ with no issues or crashes.
1796743,2018-10-09 11:17:30 UTC,Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
1796743,2018-10-08 18:30:08 UTC,This change was made by a bot.
1796743,2018-10-09 11:58:56 UTC,"Hello,"
1796746,2018-10-10 16:23:21 UTC,"Could it be that you're using the chromium snap, and not the deb package? If so that would be bug #1738164. If unsure, you can browse to chrome://version and share the output here."
1796746,2018-10-10 22:28:03 UTC,Definitely not snap:
1796746,2018-10-10 22:31:33 UTC,"The point is: It works with plain u2f tokens such as yubikey (blue), hypersecu, plugup. So it's not a general usb problem."
1796746,2018-10-11 05:28:51 UTC,Thanks for the confirmation. I have ordered a Yubikey 4 so I can test and investigate the issue.
1796746,2018-10-25 09:14:38 UTC,"Just tested with a brand new yubikey 4 in chromium-browser 70.0.3538.67-0ubuntu0.18.10.1 (Ubuntu 18.10), and U2F works as expected (tested with https://demo.yubico.com/u2f)."
1796746,2018-11-01 11:09:55 UTC,"I'm currently travelling, and my resources (time, things) are limited, but it still does not work (my yubikey 4 sticks not new, around 1 year old)"
1796746,2018-11-19 15:38:41 UTC,Sorry for the lack of feedback. It looks like this could possibly be a 18.04-specific issue (given that I was not able to observe it on 18.10).
1796746,2019-04-18 09:05:41 UTC,"Since the problem still exists and I need to use the device, I've done some further debugging."
1796746,2019-04-18 09:11:02 UTC,"Strangely, the apparmor state for chromium was in complain mode, not enable mode."
1796755,2019-05-13 21:25:44 UTC,"Fixed in revision 76a915d472b78fe1d42952f3e963b501d9a3a024
https://git.launchpad.net/kicad/patch/?id=76a915d472b78fe1d42952f3e963b501d9a3a024"
1796757,2018-10-15 08:37:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796758,2018-10-09 09:08:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796765,2019-03-28 07:05:31 UTC,"I encountered the same problem and after disabling the preview column the gui works fine (thank you!).
I'm using a current KDE Plasma desktop (nothing exotic), so I think more users will be impacted by this."
1796765,2019-03-31 09:15:26 UTC,Maybe this is already fixed in the 2.2 branch and master.
1796765,2019-04-23 21:34:11 UTC,Is this fixed now with the 2.2.1 release?
1796765,2019-11-26 14:59:14 UTC,works great with 2.2.2!
1796767,2018-10-09 12:26:22 UTC,"https://www.ee.iitb.ac.in/~spilab/Tips/ansii_graphic_symbols_for_electrical_and_electronics_daigrams_1993.pdf, starting on page 213."
1796767,2019-11-26 17:28:20 UTC,"@Seth, this seems like it is opening a can of worms... specifically what reference designator list should we use? There is the IEEE one that Jeff linked, but it appears that the KiCad library doesn't follow that itself and deviates in some instances (see [1], [2], [3])."
1796767,2019-11-26 18:01:39 UTC,"As a card-carrying IEEE member, I'm biased. :)"
1796774,2019-08-26 17:28:26 UTC,"Fixed in revision 6b6e9eddee891b6cf8522e0770505b353a94dc9c
https://git.launchpad.net/kicad/patch/?id=6b6e9eddee891b6cf8522e0770505b353a94dc9c"
1796777,2019-02-09 17:32:27 UTC,It did the first time I moved the folder.
1796777,2019-02-09 16:46:19 UTC,Walt does this also fail for you?
1796777,2018-11-16 14:26:41 UTC,User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0
1796777,2018-11-16 14:27:42 UTC,"Confirmed using Ubuntu 19.04 (dev) and Thunderbird 60.2.1
Reported Upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1507804"
1796777,2018-11-16 14:27:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796779,2018-10-29 21:36:06 UTC,"As a workaround, I just grabbed and installed the 1.3.0-2 package from sid https://packages.debian.org/sid/amd64/isync/download"
1796779,2018-10-25 18:21:07 UTC,This looks to have been patched upstream: https://sourceforge.net/p/isync/isync/merge-requests/2/
1796779,2018-10-09 02:20:19 UTC,This is the certificate returned by gmail:
1796779,2018-10-25 18:20:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796788,2018-10-09 15:25:13 UTC,"Yep, I can reproduce the problem.  It bisected to:"
1796788,2018-10-10 01:00:27 UTC,"Hi Theodore,"
1796788,2018-10-10 15:25:30 UTC,Note a file system which is significantly shrunk --- which tends to be the case with resize2fs -M --- is going to have files fragmented which will have performance implications.   It's not clear to me what you are trying to optimize for --- I assume you're just wanting to save on download bandwidth so you want a highly compressed image?
1796815,2018-10-09 08:14:36 UTC,I tried removing things from gnus.svg to find a minimal example that makes imagemagick coredump.
1796815,2018-11-13 08:42:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796816,2021-01-12 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1796816,2018-10-10 07:44:35 UTC,"I have configured a matching PowerPC virtual machine under an OpenSUSE Tumbleweed x86_64 host with qemu-ppc64 for that platform, and the keyboard mapping is correct for all keys. So the bug I have come across is presumably a bug with the WIndows port of QEMU."
1796816,2020-11-12 07:13:32 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1796820,2019-12-23 06:45:20 UTC,"Cron triggers won't be supported as part of core mistral functionality in the long run. Most likely, they won't be copied to another place (e.g. mistral-extra) in a different form and deprecated in Mistral."
1796820,2019-09-17 08:16:41 UTC,Closing this bug for now since it seems to duplicate https://bugs.launchpad.net/mistral/+bug/1788174
1796820,2019-01-05 21:42:39 UTC,will be fixed when https://review.openstack.org/#/c/594187 is merged and auth_uri is no longer supported in stein release
1796822,2018-10-14 04:16:40 UTC,I can still reproduce this bug with the Ubuntu cosmic 20181014 iso on VirtualBox (my host is also running cosmic and I use the distro-packaged VirtualBox). The workaround mentioned in the bug description works well.
1796822,2018-10-16 21:27:49 UTC,"Personally I can't reproduce that, so please check if the fix for bug #1794280 also works here."
1796822,2018-10-15 14:25:29 UTC,I have a similar case. Let me know if you want me to file a new bug and where to file it.
1796822,2018-10-14 15:24:40 UTC,Never mind. I think I somehow managed to boot an older iso. I zsynced just before so I don't know how that happened. I can't reproduce this bug any more.
1796822,2018-10-23 14:21:51 UTC,Untargetting the xorg part from cosmic since the initramfs was enough to workaround the problem there
1796822,2018-10-14 01:07:29 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1796822,2018-10-09 08:43:17 UTC,From IRC:
1796822,2018-10-10 13:40:32 UTC,This bug was fixed in the package initramfs-tools - 0.131ubuntu14
1796822,2018-10-09 13:50:30 UTC,it's a fringe case for devs who use other distributions
1796822,2018-10-09 11:05:06 UTC,What is the fringe case here?
1796822,2018-10-09 10:12:56 UTC,"adding vboxvideo to initrd seems to load it at 1.2s instead of 6.6s on my instance, giving it plenty of time for X to not cause issues"
1796822,2018-10-24 02:15:29 UTC,"FYI, similar skewed stride bugs on:"
1796822,2018-10-11 11:01:54 UTC,Confirming that todays pending ISO boots correctly on Vbox.
1796822,2018-10-09 09:24:22 UTC,"After installation vboxvideo is loaded much earlier (no rootfs to unpack) and getting userspace up and running takes a few seconds, so once X is started the native driver is ready and everything works as it should."
1796822,2018-10-09 08:42:38 UTC,"Logs from the live session show that xorg started before the vbox video driver was ready
dmesg attached"
1796822,2018-10-09 08:42:51 UTC,xorg log
1796828,2018-10-12 07:28:38 UTC,@Corey: Sadly I fear that we cannot accept patches via Launchpad. Would it be possible for you to submit your patch following this guideline? https://docs.openstack.org/infra/manual/developers.html
1796828,2018-10-12 13:10:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/610030"
1796828,2018-10-15 15:05:37 UTC,"I am not sure about this bug - the entire API is documented publicly, which makes the ""remediation"" seemingly worthless."
1796830,2018-11-27 16:58:54 UTC,"Reviewed:  https://review.openstack.org/620023
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=11cf61ba11041aad60b3fb5c4d949aa491fabcb5
Submitter: Zuul
Branch:    stable/18.11"
1796830,2018-11-27 16:34:45 UTC,"Reviewed:  https://review.openstack.org/620021
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=b7f5d9c95493de81119cdcf4f015bb5047d13068
Submitter: Zuul
Branch:    stable/18.11"
1796830,2018-11-27 16:32:27 UTC,"Reviewed:  https://review.openstack.org/620016
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=00642244587dc79f30ab31b8e56de0591a7976e5
Submitter: Zuul
Branch:    stable/18.11"
1796830,2018-11-27 16:31:00 UTC,"Reviewed:  https://review.openstack.org/620022
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=cd915ee6f822af152379059a22ffbe1bdcc43313
Submitter: Zuul
Branch:    stable/18.11"
1796830,2018-11-26 23:29:15 UTC,"Reviewed:  https://review.openstack.org/619752
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=b77bc9cd1ed04df3a99e6324d82a91cd5ee535f5
Submitter: Zuul
Branch:    master"
1796830,2018-11-26 23:28:55 UTC,"Reviewed:  https://review.openstack.org/619758
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=ce389711da998ae44c90c31db96b7a466af9d400
Submitter: Zuul
Branch:    master"
1796830,2018-11-26 23:28:14 UTC,"Reviewed:  https://review.openstack.org/619773
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=96741629b4d22d7102fe9a3fe6e3de3e45ab9df1
Submitter: Zuul
Branch:    master"
1796830,2018-11-26 11:50:10 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/620023"
1796830,2018-11-26 11:49:31 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/620022"
1796830,2018-11-26 11:49:01 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/620021"
1796830,2018-11-26 23:28:33 UTC,"Reviewed:  https://review.openstack.org/619762
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=882e78c5ad76df9232dfd4b741031c4b36341b9c
Submitter: Zuul
Branch:    master"
1796830,2018-11-23 17:11:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619773"
1796830,2018-11-23 16:11:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619762"
1796830,2018-11-23 16:01:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619758"
1796830,2018-11-23 15:32:21 UTC,Charm-helpers change at: https://github.com/juju/charm-helpers/pull/247
1796830,2018-11-26 11:36:39 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/620016"
1796830,2018-11-22 18:19:47 UTC,"After the (coming change) to charm-helpers, keystone, nova-cc and openstack-dashboard will require charm-helper syncs."
1796830,2018-11-22 18:17:15 UTC,"The problem is in charm-helpers, specifically in charmhelpers.contrib.charmsupport.nrpe.copy_nrpe_checks().  It assumes that the charmhelpers directory will always be in hooks, which (probably) was a good assumption until the PY3 work makes it very hard in some charms to not root the python path in the charmdir."
1796830,2018-11-22 14:40:51 UTC,"This bug also affects keystone, nova-cloud-controller and openstack-dashboard:
https://github.com/openstack/charm-keystone/blob/stable/18.11/hooks/keystone_hooks.py#L748
https://github.com/openstack/charm-nova-cloud-controller/blob/stable/18.11/hooks/nova_cc_hooks.py#L1014
https://github.com/openstack/charm-openstack-dashboard/blob/stable/18.11/hooks/horizon_hooks.py#L311"
1796830,2018-11-19 11:35:47 UTC,"Reviewed:  https://review.openstack.org/608904
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=65c90e7c272e984ecc9cee7c936484fbe087fa1b
Submitter: Zuul
Branch:    master"
1796830,2018-10-09 10:20:42 UTC,Change proposed: https://review.openstack.org/#/c/608904/
1796838,2018-11-11 23:24:14 UTC,The page source has:
1796840,2018-10-19 07:48:49 UTC,Isn't that a known problem with Python?
1796841,2018-10-09 09:42:11 UTC,Great idea!
1796842,2018-10-09 09:42:11 UTC,test comment
1796853,2018-10-31 09:50:26 UTC,Is someone following the bug reports?
1796853,2018-10-31 09:59:53 UTC,"I think https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1770173 might be related as well.
The installation hangs at the exact same point: 66% while running the ""dmsetup create -r osprober-linux-something"" command."
1796853,2019-03-12 10:14:26 UTC,"Hi,"
1796853,2019-03-14 13:23:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796853,2021-01-04 09:13:16 UTC,This also happens during installs of 18.04 and it causes the installation to hang at Installing grub 66%
1796857,2018-10-09 15:12:37 UTC,"I can confirm those are the properties that the ImagePropertiesFilter are looking at and are aliased for the legacy names, however, the image properties documentation in glance still refers to the ""legacy"" property names, so if we're going to change the docs, they should be consistent:"
1796864,2018-10-12 18:59:44 UTC,Checked out now? How did it go?
1796864,2018-10-12 19:15:30 UTC,"I haven't had the time to do that by now, probably Sunday :) Thanks for
asking :)"
1796864,2018-10-13 08:45:16 UTC,It works now :) I ended up using the CUPS webinterface. Thanks!
1796864,2018-10-10 15:27:26 UTC,"Thanks, I'll check it out."
1796864,2018-10-10 06:41:04 UTC,I have a HP Officejet 5230
1796864,2018-10-10 06:40:19 UTC,I have a HP Officejet 5230
1796864,2018-10-09 18:02:31 UTC,What is your printer?
1796864,2018-10-10 08:40:12 UTC,"This printer has AirPrint, so it is a candidate for driverless printing:"
1796871,2018-10-12 08:04:53 UTC,"Hi Gulyas,
I understand your problem. I already have a new version of OR that lets you re-enter the game where you were at save time, even if your consist has changed. However in this moment I can't upload the new version, because changes cannot be performed until OR 1.3 is published, which should occur this week."
1796871,2018-10-12 08:49:19 UTC,"For the moment your player can generate a .con file with the new consist he had at the moment the save was done, and he can re-enter the game with such new .con file. This way he will re-enter the game where he was when the save was done."
1796873,2018-10-10 17:58:31 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1796874,2018-10-09 12:18:41 UTC,I have created an issue on transifex as well
1796874,2018-10-10 07:04:36 UTC,"""crammed together"" would work"
1796874,2019-09-15 15:50:54 UTC,Migrated to https://github.com/widelands/widelands/issues/1717
1796876,2018-10-10 13:11:21 UTC,"Sorry for missunderstanding you.
No, in Control Center -> Keyboard -> Layout -> add the right keyboard is added.
What it does not affect from Control Center is the file /etc/default/keyboard which I do not know if it should."
1796876,2018-10-10 12:04:43 UTC,"So there are 2 bugs :
1 ""Yes it is when using Ubiquity"" ""when selecting Switzerland, all keyboard layouts are the same and therefore wrong."""
1796876,2018-10-10 11:39:17 UTC,"Yes it is when using Ubiquity. Tried with Ubuntu 18.04.1 installation and there is the same problem. So in all Ubuntu Forks should be this ""bug""."
1796876,2018-10-10 09:23:57 UTC,"""Also while installing, the swissgerman keyboard is not right and must be choosen with autorecognition."""
1796876,2018-10-10 07:26:06 UTC,"Thanks for the adwice, i will do so next time."
1796876,2018-10-09 19:47:11 UTC,In the feature please have a look at https://ubuntu-mate.community/t/how-to-report-problems-in-ubuntu-mate/17943 when reporting a problem.
1796882,2018-10-09 13:17:39 UTC,"This patch got merged on October the 3rd touching that test:
https://review.openstack.org/#/c/600046/"
1796882,2018-10-09 14:22:31 UTC,"Logstash also shows [0][1] that after the patch [2] got merged this error became more common. It doesn't seem to affect only networking-ovn. From what I could see in the logs networking-odl, dragonflow and potential others have also been affected."
1796882,2018-10-09 15:19:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/609032"
1796882,2018-10-10 13:18:56 UTC,"The fix should go to tempest, here's a patch in networking-ovn testing the tempest change: https://review.openstack.org/#/c/609033/ (works)"
1796882,2018-10-14 13:40:15 UTC,"Reviewed:  https://review.openstack.org/609032
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=692422babfb76ff2cea216877185a86eecf946e2
Submitter: Zuul
Branch:    master"
1796882,2018-11-08 09:51:43 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/609732
Reason: Not needed anymore"
1796882,2020-02-10 14:18:26 UTC,"Seems it's fixed, related reviews were merged and the test is not failing in any tempest gate."
1796883,2019-02-05 19:49:59 UTC,moved from https://bugs.launchpad.net/yade/+bug/1796883 to https://gitlab.com/yade-dev/trunk/issues/44
1796883,2018-10-12 13:05:07 UTC,"Hi Alex,
It sounds relevant indeed, however the possible ""push_back"" would have to be done inside boost serialization, and I doubt we need to dig that deep to understand the problem."
1796883,2018-10-12 12:39:26 UTC,In the Facet.cpp I found the following comment. Maybe this rings a bell for somebody?
1796886,2020-07-21 07:26:43 UTC,Due to the wide impacting nature of the fix for this issue this will not be stable backported but will be included in the upcoming 20.08 charm release.
1796886,2020-06-18 16:22:58 UTC,Just tested next charms in bionic-stein and confirm that i hit the error by simply going from single unit to 3 unit (cluster_count: 3).
1796886,2020-07-08 12:41:29 UTC,"To close the loop, all patches landed have resolved the issue for me. As long as I set min-cluster-size to be the targeted size prior to adding units, i do not hit the problem anymore."
1796886,2020-06-30 10:01:50 UTC,This review should address #22: https://review.opendev.org/#/c/738219/
1796886,2020-06-26 11:41:57 UTC,Having now tested with the updated clients I think I have found another issue. On my nova-compute host I see that the client config does not contain the address of the new unit (rabbitmq-server/4):
1796886,2020-06-26 10:38:20 UTC,"My bad, i missed that the client-side patches have not landed yet. I will re-test with those included."
1796886,2020-06-26 10:28:28 UTC,I'm afraid this is still not fixing the problem for me. I did the following:
1796886,2020-06-25 10:18:45 UTC,"Reviewed:  https://review.opendev.org/737717
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=20f865c19fb1ca296dd6b574da110d9d2c1be91c
Submitter: Zuul
Branch:    master"
1796886,2020-06-25 05:13:13 UTC,"https://review.opendev.org/737717
https://github.com/juju/charm-helpers/pull/482"
1796886,2020-06-22 15:35:56 UTC,"I've tried testing this with different settings for min-cluster-size and seem to have noticed that if I increase the config to n+1, and then add a new node, I don't have any issues with the service going down."
1796886,2020-06-18 18:37:46 UTC,Can confirm with focal/ussuri. Adding a 4th rabbitmq-server breaks nova-compute.
1796886,2020-06-17 16:54:36 UTC,"It appears that a restart is issued to rabbit and then the client connects - in the situations where it fails, the login failure is occuring between issueing the restart command and before the server has actually stopped"
1796886,2019-02-14 15:13:22 UTC,"I think the interesting part of the bug is: ""the clients get an authentication failure and never retry thus they sit there unusable until they are manually restarted."""
1796886,2020-06-17 16:49:47 UTC,I tried waiting for more things:
1796886,2019-02-15 04:52:17 UTC,Agreed @ajkavanagh.
1796886,2019-02-14 08:55:57 UTC,"It appears that the root cause of this behaviour might be elsewhere. Even before the rabbitmq cluster is formed, the amqp-relation-changed hook fires on the clients of rabbitmq-server:amqp as this relation already exists. This causes the newly added rmq node's IP to propagate to the client's configuration, triggering errors of the form:"
1796886,2018-11-27 19:23:24 UTC,Let's add more gates in rabbit_utils.client_node_is_ready() to make sure the node has joined the cluster and there is a reasonable expectation it has its data.
1796886,2019-02-07 10:51:46 UTC,"Alok, I was probably too hasty in suggesting this was incomplete as David has indicated where to probably do the fix.  It's possibly best if a fix is done and then Ed might be able to test it on his setup?"
1796886,2019-02-07 16:11:02 UTC,I had been trying to reproduce this with openstack-on-LXD. hopem suggested that kvm might be a better bet to reproduce. From IRC:
1796886,2019-02-07 09:47:24 UTC,Cannot reproduce. My test setup of course does not have much load so I simulate some AMQP traffic by invoking openstack compute service list repeatedly in parallel but there is no sign of the reported problem.
1796886,2019-02-15 06:28:34 UTC,"On bionic-rocky, the behaviour is different. After expanding the rmq cluster, spawning instances fails with the error:"
1796886,2020-04-10 22:41:59 UTC,"I'm subscribing ~field-high as this appears to have slipped several releases and this is going to impact a major re-architecture/migration event we have planned in the near future. If this is in 20.05 we'll be fine, if it's later it could be problematic."
1796886,2020-06-08 16:25:53 UTC,I have been asked to rule out this bug https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1818260 as a possible culprit.
1796886,2020-06-17 12:16:33 UTC,"After bug in #11 was fix merged, I have retested and the problem still exists. Continuing to traige."
1796886,2019-02-09 15:52:54 UTC,"@alephnull-b here is a bundle, as requested, that you can use to reproduce this issue - https://paste.ubuntu.com/p/VvGVfGh8PQ/"
1796895,2018-10-09 19:08:12 UTC,"Tested the first bisected version, on commit 003ae88ae88d48643e71dc69c18d4eda598339d5, problem still present."
1796895,2018-10-09 22:57:14 UTC,Ok - for anyone that isn't used to installing kernels from proposed.  It helps to install linux-image-generic and not linux-image-XXXXX-generic in order to pull in the modules package.
1796895,2018-10-09 22:48:00 UTC,"For whatever reason, after installing linux-image-4.15.0-37-generic the system boots up fine but doesn't appear to initialize the motherboard's built in realtek network adapter so there is no network connectivity to test."
1796895,2018-10-09 20:46:59 UTC,I installed the proposed kernel on a remote host and rebooted but of course the host didn't come back online for who only knows what reason.  I'll post an update in a few hours once I have a chance to get my hands on it.
1796895,2018-10-09 19:11:53 UTC,"Thanks for all the testing.  If this bug is fixed in -proposed, then the fix is already applied to the Ubuntu kernel and will be released in the next round of updates on November 12th."
1796895,2018-10-09 18:33:09 UTC,"Just tested with the proposed build, the problem is fixed with the proposed kernel 4.15.0-37 on my server."
1796895,2018-10-09 15:13:38 UTC,I can't use apport-collect since it requires IPv4 connection to internet.
1796895,2018-10-09 17:23:52 UTC,I'm seeing similar behavior on multiple physical hosts running 4.15.0-36-generic.  The TCP window size only appears to grow very slightly (from initial of 224 to around 1400) during the entire length of the transfer.
1796895,2018-10-09 17:19:37 UTC,"It might also be good to test the latest mainline kernel to see if this issue also exists upstream, if it is fixed upstream and/or if this regression is Ubuntu specific."
1796895,2018-10-09 17:17:36 UTC,"I can perform a kernel bisect to identify the commit that introduced this regression.  Before starting the bisect, can you test the -proposed kernel:"
1796895,2018-10-09 15:16:02 UTC,Also want to add that once we downgraded back to 4.15.0-33 the problem went away. Rebooting back to 4.15.0-36 the problem reappears.
1796895,2018-10-09 15:04:18 UTC,"We had a similar issue with our MySQL server farm (seven dedicated MySQL servers). Replication was very slow, falling behind for no apparent reason. We were reaching 24 hours of lag! We never had that kind of lag before. A couple of minutes at the most."
1796895,2018-10-09 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1796895,2018-10-09 18:26:58 UTC,I started a kernel bisect between 4.15.0-34 and 4.15.0-36. The kernel bisect will require testing of about 7-10 test kernels.
1796895,2018-10-21 21:28:07 UTC,Sorry for the accidental status change. I can't revert. Not sure why I was able to do that. Verified fix in -37.
1796895,2018-10-18 03:18:06 UTC,For the record:
1796899,2018-10-24 19:22:23 UTC,"Tests are explicitly using random values to ensure there are no hardcoded explicit ""did we get a value we expected""."
1796900,2019-05-29 16:55:41 UTC,"This has been fixed upstream and is part of the 1.32 version of tar, which is not yet in Ubuntu or Debian."
1796903,2018-10-09 15:05:00 UTC,"The branch is called: user/sandbergja/lp1796903_accessible_calendar_button
Here is a link: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/sandbergja/lp1796903_accessible_calendar_button"
1796903,2019-05-24 18:10:04 UTC,I've pushed a signoff of Jane's patch along with a suggested followup to
1796903,2019-07-18 21:46:19 UTC,"Thanks, Galen.  Signoff branch here: user/sandbergja/lp1796903_angularjs_datepicker_a11y_signedoff"
1796903,2019-07-30 14:32:02 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jane!"
1796904,2018-10-29 17:13:18 UTC,-- -proposed kernel testing --
1796904,2018-10-09 15:11:04 UTC,"ubuntu@starbuck:~$ sudo perf stat -e l1d_cache_refill_rd,l1d_cache_refill_wr,armv8_pmuv3_0/l1d_cache_refill/ stress-ng -c 2 -i 1 -m 1 --vm-bytes 128M -t 10s
stress-ng: info:  [4198] dispatching hogs: 2 cpu, 1 io, 1 vm
stress-ng: info:  [4198] successful run completed in 10.01s"
1796904,2018-10-09 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1796904,2018-10-24 13:35:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1796904,2018-11-13 18:51:26 UTC,This bug was fixed in the package linux - 4.15.0-39.42
1796904,2018-10-09 15:13:10 UTC,"ubuntu@starbuck:~$ sudo perf stat -e unaligned_ld_spec,unaligned_st_spec,unaligned_ldst_spec,mem_access_rd,mem_access_wr,armv8_pmuv3_0/mem_access/  stress-ng -c 2 -i 1 -m 1 --vm-bytes 128M -t 10s
stress-ng: info:  [4212] dispatching hogs: 2 cpu, 1 io, 1 vm
stress-ng: info:  [4212] successful run completed in 10.02s"
1796904,2018-10-09 15:16:37 UTC,A test kernel and tool packages are available in ppa:yarmouth-team/lp1794838
1796905,2018-10-09 14:51:06 UTC,"Affected file:
https://git.launchpad.net/kicad/tree/3d-viewer/3d_plugin_dir.h.in"
1796910,2018-10-18 10:00:25 UTC,From the interface:
1796911,2018-10-22 12:40:30 UTC,I see very similar errors with strongSwan when the daemon charon is run as non-root:
1796911,2020-04-07 23:37:55 UTC,This bug was fixed in the package apparmor - 2.13.3-7ubuntu4
1796911,2019-04-24 10:36:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796914,2018-10-09 15:46:57 UTC,"That type of menu is commonly referred to as a ""Hamburger Menu."""
1796914,2018-12-13 20:34:19 UTC,Fix pushed to: user/slink/lp1796974_top_right_menu_aria_label
1796914,2018-12-13 20:43:22 UTC,"Oops! The W3C standard expressly prohibits using both. I chose to use the title attribute alone, both as it provides a tooltip, and to maintain consistency with the Angular7 version of the menu. A corrected commit has been pushed to the aforementioned branch."
1796914,2019-05-24 20:06:54 UTC,I pushed a signoff to
1796914,2019-06-13 14:24:37 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1.  Thanks, Sam and Galen!"
1796915,2018-10-22 09:12:16 UTC,"OK, I am still with Ubuntu18.04, installed xubuntu-desktop package, and it solved all bugs. No more in games crashes, no more full screen moving/resizing when changing sound volume, no more volume notifications bugs, and no more PC hanging when changing sound volume in games. Hope someday GNOME improve."
1796915,2018-10-10 05:39:40 UTC,"Daniel my problem starts by a different way (had no problems with Alt+Tab, maybe  because I play different games), but I have the same problem with the screen, and yeah it just looks like that https://imgur.com/a/3stwv
In my case the screen restores back to normal when volume popup hides back. It is just annoying when I change volume."
1796915,2018-10-10 02:47:48 UTC,"Sounds related to bug 1725649, but that's closed. I think I've heard of another similar Nvidia bug, somewhere."
1796916,2018-10-10 07:00:19 UTC,"I wonder if this is related to the change that stopped creating an
status-history record for when update-status was triggered."
1796916,2018-10-15 18:42:13 UTC,Is this in the status output or the debug-log output?
1796916,2018-10-15 18:51:45 UTC,It's in the unit log.
1796916,2018-10-23 21:17:28 UTC,"With current 2.4 branch this is what I see:
unit-ul-0: 17:12:40 DEBUG juju.worker.uniter.operation running operation
run install hook
unit-ul-0: 17:12:40 DEBUG juju.worker.uniter.operation preparing operation
""run install hook""
unit-ul-0: 17:12:40 DEBUG juju.worker.uniter.operation executing operation
""run install hook""
unit-ul-0: 17:12:40 DEBUG juju.worker.uniter [AGENT-STATUS] executing:
running install hook
unit-ul-0: 17:12:40 INFO juju.worker.uniter.operation skipped ""install""
hook (missing)
unit-ul-0: 17:12:40 DEBUG juju.worker.uniter.operation committing operation
""run install hook""
un"
1796916,2018-11-06 22:47:40 UTC,"I don't think we've changed logging-config. What would turn those on or
off? We have DEBUG level messages."
1796916,2019-04-01 22:41:30 UTC,I just checked with 2.5.3 and definitely have both the lines mentioned:
1796916,2019-07-14 04:17:18 UTC,[Expired for juju 2.4 because there has been no activity for 60 days.]
1796916,2019-07-14 04:17:21 UTC,[Expired for juju because there has been no activity for 60 days.]
1796917,2018-12-03 09:17:02 UTC,"The Ubuntu 18.04 minimal cloud image from 22-Nov-2018 20:29 (https://cloud-images.ubuntu.com/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img)
is still affected from this issue:"
1796917,2018-10-09 17:31:37 UTC,"This bug is fixed with commit 00e36d3d to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=00e36d3d"
1796917,2018-10-09 15:45:57 UTC,cloud-init collect-logs would harvest a tarfile of all cloud-init artifacts.
1796917,2018-10-09 15:31:50 UTC,"It's not clear to me whether this is a cloud-init bug or a kernel bug, so I've filed it in cloud-images for triage for now."
1796917,2018-10-09 15:44:32 UTC,Can we get the network configuration passed to this instance or the cloud-init.logs.tar it might shed more light on a configuration that we need to take into account in cloud-init. We can certainly attempt to ignore duplicate mac checks in cloud-init if macs are returned as 6-tuple of 00. But we probably want to make sure we are also understanding the full network config in this case too.
1796920,2018-10-09 15:43:45 UTC,The code in the ironic virt driver to report VCPU/MEMORY_MB/DISK_GB inventory was removed in Stein:
1796920,2018-10-09 16:08:55 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/609043"
1796920,2018-11-26 17:12:00 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/620111"
1796920,2018-11-26 17:31:20 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/620113"
1796920,2018-12-19 10:01:42 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1796920,2019-10-22 14:28:40 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/620111
Reason: I'm not actively working on this."
1796920,2019-10-22 14:28:49 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/620113
Reason: I'm not actively working on this."
1796920,2018-11-24 17:00:54 UTC,"Reviewed:  https://review.openstack.org/609043
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f7d0a7671fb73983a1853b0d2f3ce7552d752c31
Submitter: Zuul
Branch:    stable/rocky"
1796923,2019-05-14 13:40:38 UTC,"Per Liam's comment, this should be fixed by the latest charm release. Please reopen if the problem recurs."
1796923,2018-10-31 17:48:30 UTC,Tagged cdo-release-blocker since this appears to be a regression. We have only seen this with the 'next' charms.
1796923,2018-12-11 12:33:37 UTC,"I think we need to be a bit careful about attributing deployment failures to this bug as there are many reasons why a charm may not have got the full relation data from a charm it is related to. I think the latest crashdump is yet another bug (3rd distinct bug attributed this bug). Anyway, <tl;dr> The latest crash dump looks like a duplicate of Bug #1794850 </tl;dr>."
1796923,2018-12-03 15:48:32 UTC,Hit is on Nov 15...logs attached above
1796923,2018-11-10 21:40:30 UTC,"Setting as incomplete rather than new.  If, after the keystone goal state fixes, this specific issue is observed again, please attach new logs and reset the bug state to new."
1796923,2018-11-05 17:07:15 UTC,"Liam,"
1796923,2018-11-05 16:20:57 UTC,"I've created a new bug, https://bugs.launchpad.net/charm-keystone/+bug/1801754 , for the keystone goal state issue for clarity."
1796923,2018-12-11 09:47:51 UTC,"Looking at the logs from Chris Gregan, the latest 'since' time in the juju_status.yaml is 11:01, with most of the 'since' times occuring between 10:50 and 10:55 - if the juju_status.yaml was captured at the same time crashdump was run (as is usually the case), it would indicate a controller problem - multiple units were still running update-status well beyond 11:01, e.g."
1796923,2018-11-05 12:51:54 UTC,"Yep, on it's way..."
1796923,2018-11-05 12:37:38 UTC,"Ed, the existing crash dump provided for this bug is pretty clear that the missing data was missing because the db clustering hadn't finished. That is not to say you are not hitting a closely related bug or that the deploy already referenced in this bug wouldn't have moved on to seeing the issue you're seeing eventually."
1796923,2018-11-05 12:32:26 UTC,"I'm seeing this a lot with the next charms i.e. I deploy openstack non-HA but with Keystone deployed as HA and i regularly have at least one service that does not get its relation set from keystone. It appears that keystone was waiting for hacluster to finish which took a while (slow env) and it never goes back and updates (all) relations that need updating thus leaving then with ""incomplete relations: identity""."
1796923,2018-11-01 10:21:38 UTC,I'm not sure why but the nova-cloud-controller log entries stop on or before 2018-10-08 13:53:18:
1796923,2018-10-31 18:00:12 UTC,It seems this is nova-cloud-controller not completing its relationships:
1796923,2018-11-05 13:11:57 UTC,"bundle - https://pastebin.ubuntu.com/p/9mcN5JyjDj/
overlay - https://pastebin.ubuntu.com/p/s7NKY2Pn98/"
1796926,2018-10-10 07:57:01 UTC,"I guess this bug belongs to charms.openstack, keeping both tasks until it is clear what needs to be done."
1796928,2018-10-10 15:18:22 UTC,apport information
1796928,2020-01-02 16:38:35 UTC,should be fixed since 19.04
1796928,2020-01-01 11:56:10 UTC,"Have this fix been backported to Ubuntu libinput packages? I'm asking, because they're typically ancient there, so I don't think that because it's been fixed upstream, it was fixed in Ubuntu as well."
1796928,2018-10-11 01:30:37 UTC,"Excellent, thanks!"
1796928,2018-10-10 15:19:13 UTC,1. 'apport-collect 1796928' run on affected machine.
1796928,2018-10-10 15:18:26 UTC,apport information
1796928,2018-10-10 15:18:25 UTC,apport information
1796928,2018-10-10 15:18:24 UTC,apport information
1796928,2018-10-10 15:18:20 UTC,apport information
1796928,2018-10-10 15:18:13 UTC,apport information
1796928,2018-10-10 15:18:16 UTC,apport information
1796928,2018-10-10 15:18:15 UTC,apport information
1796928,2018-10-10 15:18:11 UTC,apport information
1796928,2018-10-10 15:18:10 UTC,apport information
1796928,2018-10-10 15:18:07 UTC,apport information
1796928,2018-10-10 15:18:01 UTC,apport information
1796928,2018-10-10 03:02:51 UTC,Please:
1796928,2018-10-10 15:18:18 UTC,apport information
1796930,2020-01-10 09:33:56 UTC,Interesting idea with that ProxySQL.
1796936,2018-12-17 18:43:50 UTC,"Actually, it seems like this is a bit more complex than I thought at first.  When the row is already selected, this checkbox should actually be labeled as ""Un-select row"" (or something similar) in both Angular and AngularJS.  The AngularJS client currently isn't toggling that title attribute between ""Select row"" and ""Un-select row""."
1796936,2019-04-12 20:26:04 UTC,I created a branch for this called user/sandbergja/lp1796936_label_grid_checkboxes
1796936,2019-08-01 16:07:08 UTC,"Works for me. Pushed to master and rel_3_3. Thanks, Jane!"
1796942,2019-05-23 17:11:42 UTC,"Looks good, thanks Jeff, Galen.  Merged to 3.1 and above."
1796942,2018-10-09 20:52:05 UTC,working branch at user/jeff/lp1796942_sip_payment_type_01_visa
1796942,2019-05-23 15:40:22 UTC,Signed off:
1796943,2020-06-10 18:52:06 UTC,"According to the documentation, the section should be [profiler]."
1796943,2018-10-09 19:46:25 UTC,"Yes, I have them enabled. Here's the related section from /etc/cinder/cinder.conf:"
1796943,2020-06-10 18:26:41 UTC,"Hopefully you figured this out, but your section is called [profiler], but the setting to enable this is under [osprofiler]."
1796943,2018-10-09 19:21:22 UTC,OSProfiler is disabled by default with Cinder. Make sure you have the section:
1796945,2019-08-14 21:27:26 UTC,"I think I have a simple fix for this, but running late for something.  Will post in the morning!"
1796945,2019-08-22 18:25:14 UTC,I should have looked at the calendar to get this into yesterday's releases but that didn't work out.
1796945,2019-08-16 19:22:21 UTC,I've tried out Dan's updated branch above and it works great. Signoff is here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1796945_signoff / working/user/jboyer/lp1796945_signoff
1796945,2019-08-15 14:31:32 UTC,"Okay, small change now pushed:"
1796945,2019-07-31 19:25:26 UTC,"Thanks Dan, your branch is a great improvement. I think I can also see what's going on in Tina's examples too. The Source Path separator is different between the XUL and web clients: The XUL Client uses both '->' and '::' depending on how many layers down the tree you go, while the Web Client instead only uses '->' regardless of the number of links traversed. So when you clone a simple XUL report that results in this SQL:"
1796945,2019-06-27 22:46:03 UTC,"I encountered an issue when adding a displayed or filter field from a linked table, I got the missing FROM clause error."
1796945,2019-06-07 19:35:06 UTC,We deployed the fix on a 3.1.7 test server. I picked some XUL templates to test all the listed scenarios. They worked for me. For
1796945,2019-05-03 17:53:26 UTC,A variety of improvements to the webstaff reporter interface are now available here:
1796945,2019-03-19 21:27:37 UTC,"I think the branch posted has the right idea, but as noted, is not going to be right in some cases.  Even 'has_a' doesn't necessarily mean an inner join if the data allows the link to be null.  (has_a only determines ""direction"" of the link)"
1796945,2019-02-15 00:04:31 UTC,We observed two types of issues with templates cloned from XUL:
1796945,2019-02-13 18:03:04 UTC,"We have applied this code and haven't seen any issues, but we haven't identified any particular reports we had been having problems cloning yet, so not comfortable signing off. Tina, are you able to apply Jason's code to see if it fixes the problems with your reports?"
1796945,2019-01-28 15:57:45 UTC,"That should have read ""in my limited testing..."" Anyone that's interested please test thoroughly in case I've missed some glaring issue."
1796945,2019-01-28 14:55:39 UTC,This branch tries to address this by choosing left joins for any relationship types other than has_a (which is supposed to be inner anyway). In my testing it allowed correct XUL->Web report conversion and also helped correct an issue I was having (related to might_have links and field names != 'id').
1796945,2018-10-25 15:49:14 UTC,I can confirm we're seeing the same problems with any join that wasn't an INNER for cloned templates.
1796945,2018-10-09 18:14:37 UTC,another example
1796945,2018-10-09 18:14:17 UTC,"Attached are two examples templates in 3 states: before being clone, cloned without editing, cloned with replaced fields from linked tables (following the same path)."
1796945,2019-02-22 19:58:22 UTC,An example that a right join in XUL template was changed to inner join during the cloning.
1796948,2020-03-03 20:24:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796951,2020-03-07 16:00:02 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1796967,2019-02-28 18:03:45 UTC,"This also affects origin=""ppa:landscape/19.01"", when deployed in Xenial."
1796967,2018-11-23 15:20:55 UTC,"The issue here is that ppa:landscape/18.03 installs python3 libs whereas Juju uses Python 2.7 to execute its charms. So, we can see errors like:"
1796977,2019-01-17 00:57:05 UTC,Bueller?
1796977,2019-03-06 01:03:17 UTC,This looks like an issue with the installer.  I've added the package to this bug.
1796981,2018-10-10 17:28:53 UTC,Do you see one of those log messages in the compute log before the NoneType failure?
1796981,2019-03-22 03:46:51 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1796981,2018-12-19 20:48:13 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1796981,2018-12-19 10:04:49 UTC,This issue was fixed in the openstack/nova 16.1.7 release.
1796981,2018-12-19 10:01:40 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1796981,2018-11-30 03:25:54 UTC,"Reviewed:  https://review.openstack.org/614872
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d004b0ecfa6f20ceefd029f4ed09de191f0d76b3
Submitter: Zuul
Branch:    stable/pike"
1796981,2018-11-26 23:04:12 UTC,"Reviewed:  https://review.openstack.org/614868
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=62fbfdfa8f2dda1a5d9c3733b2f3da3a9d00c93a
Submitter: Zuul
Branch:    stable/queens"
1796981,2018-11-03 15:26:29 UTC,"Reviewed:  https://review.openstack.org/611326
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=940034c27c611b8b344f8371eb0458b16fb58f1d
Submitter: Zuul
Branch:    stable/rocky"
1796981,2018-10-10 21:21:40 UTC,based on the calls to Log.info in
1796981,2018-11-01 21:11:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/614868"
1796981,2018-10-18 18:24:07 UTC,"Re-reading the commit message of the fix, indeed it's probably that the method will return None if the guest is gone during the evacuate."
1796981,2018-10-18 18:18:23 UTC,"Chris, yes those are the correct text to look for in the log files. But you said you had none of those entries, so that means there was no error encountered while the libvirt driver was getting block stats. It implies that the domain.blockStats() libvirt python binding returned None, but I don't know why it would do that. This is the method that's called at the lower level:"
1796981,2018-10-17 14:08:26 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611326"
1796981,2018-10-17 13:54:48 UTC,"Reviewed:  https://review.openstack.org/609518
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4da54c07861a1542a8e30a768d4506d3e81b5598
Submitter: Zuul
Branch:    master"
1796981,2018-10-10 17:28:27 UTC,"Looks like the libvirt driver is the only driver that implements the block_stats() method, and it that method encounters an error it logs it and returns None:"
1796981,2018-10-10 17:26:33 UTC,Looking at what fails:
1796981,2018-10-16 13:35:37 UTC,"bump.. Is this the correct text to be looking for in the log files ?
""Updating volume usage cache with totals""
""Getting block stats failed""
""Could not find domain in libvirt"""
1796981,2018-11-01 21:30:26 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/614872"
1796981,2018-10-10 19:08:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/609518"
1796986,2019-10-18 23:26:44 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/689605"
1796986,2019-02-21 19:49:10 UTC,"hi! i want to work on this bug. But am preoccupied with university exams for 3 more days, ie till 25th feb. can i start working on this issue please?"
1796986,2019-11-12 11:39:34 UTC,This issue was fixed in the openstack/manila 7.4.0 release.
1796986,2019-10-25 12:53:28 UTC,This issue was fixed in the openstack/manila 6.3.2 release.
1796986,2019-10-23 14:58:18 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/690599"
1796986,2019-10-23 14:53:43 UTC,"Reviewed:  https://review.opendev.org/689605
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=c6e2e4ec7334ef0161d7ada9859f9e7ca6b06659
Submitter: Zuul
Branch:    stable/rocky"
1796986,2018-10-11 16:23:16 UTC,"Yikes, we really need to get these docs added as soon as we can. Marking the bugs on manila and python-manilaclient as triaged and will query for volunteers in the next upstream meeting."
1796986,2019-09-26 19:50:20 UTC,This issue was fixed in the openstack/manila 9.0.0.0rc1 release candidate.
1796986,2019-07-22 21:29:01 UTC,This issue was fixed in the openstack/manila 8.0.1 release.
1796986,2019-10-23 17:23:18 UTC,"Reviewed:  https://review.opendev.org/690599
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=b72b45d10a578c0a95d3c46ef7faa158375962f0
Submitter: Zuul
Branch:    stable/queens"
1796986,2019-06-27 01:11:44 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/667764"
1796986,2019-06-26 12:33:30 UTC,"Reviewed:  https://review.opendev.org/645010
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=84e7f4e5426fcee5941b8e4cb6d53040be8cd0ee
Submitter: Zuul
Branch:    master"
1796986,2019-06-11 19:02:51 UTC,"Jason Yes!, here: https://review.opendev.org/#/c/645010/
I'm going to update it ASAP"
1796986,2019-06-11 16:38:14 UTC,Soledad where you able to upload the changes again?
1796986,2019-03-21 20:53:26 UTC,"Change abandoned by Soledad Kuczala (<email address hidden>) on branch: master
Review: https://review.openstack.org/645010
Reason: I'm going to upload it again"
1796986,2019-06-27 02:42:24 UTC,"Reviewed:  https://review.opendev.org/667764
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=bf829be9999c97acd260bbc16aa4e6a921637886
Submitter: Zuul
Branch:    stable/stein"
1796986,2019-03-20 21:14:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/645010"
1796986,2019-02-21 21:27:39 UTC,"Sure thing, please assign the bug to yourself, and thanks for the help."
1796987,2019-01-23 15:27:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1796987,2020-03-10 15:21:58 UTC,@Dan: This is an interesting observation.. I'll bring it up with the team. Thank you.
1796987,2018-10-09 21:55:01 UTC,"Further to this, I believe snapd drops its record of old changes at some point, with no way of understanding what happened before its oldest recorded change.  If these changes were logged, regular log rotation/retention would retain this information."
1797000,2019-04-21 21:03:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797002,2018-10-12 01:59:57 UTC,"That's strange. Your Bluetooth chip looks like a common one that any Linux kernel version should support:
  https://ark.intel.com/products/66889/Intel-Centrino-Wireless-N-2230-Single-Band"
1797002,2020-12-15 18:03:20 UTC,"Hello,"
1797002,2020-12-15 09:31:33 UTC,Yeah OK... Anyone experiencing this bug please also report it to BlueZ upstream:
1797002,2020-12-15 09:19:06 UTC,"Unsure if that's something settings could change though, it's probably due to the panel triggering bluetooth discovery automatically"
1797002,2020-12-15 09:04:20 UTC,Can anyone experiencing this bug please report it upstream?
1797002,2020-01-08 09:18:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797002,2018-10-12 22:28:34 UTC,"hi,
FINALLY, i was able to localize problem :)"
1797002,2018-10-12 20:48:06 UTC,"Hi,
it was a great idea to test by running without installation,
and i test it on:
ubuntu-16.04.1-desktop-amd64 -  don't see my Bluetooth headset
ubuntu-17.10.1-desktop-amd64 - same problems with skipping as with current version
ubuntu-18.04-desktop-amd64 - same problems with skipping as with current version"
1797002,2018-10-12 01:44:24 UTC,"After downgrading core bluetooth device disappeared, and installing most recent one didn't help to bring it back.
I am just not enough familiar with linux to be able reinstall it manually.
had to reinstall whole ubuntu from scratch - still have same problems."
1797002,2018-10-10 02:59:03 UTC,"The last bluez update was 3 months ago, so whatever changed for you recently it's not bluez. It's also not pulseaudio (4 months ago)."
1797002,2018-10-11 04:15:30 UTC,"The change could also be a coincidence and environmental, like:"
1797002,2018-10-11 03:39:34 UTC,"Thanks Ivan. It appears your bluez and pulseaudio packages last updated on 2018-07-25, so they won't be the cause of any recent regressions."
1797002,2018-10-11 03:13:01 UTC,and dpkg.log
1797002,2018-10-11 03:11:19 UTC,"Here they are, bu today I've tried to update with check box pre-release updates"
1797002,2018-10-11 01:39:35 UTC,Ivan:
1797002,2018-10-10 14:06:57 UTC,"I'm experiencing this as well. After rebooting today for the first time since September 25, I noticed somewhat choppy audio over bluetooth, first with mp3s on disk, then tried Youtube and it was significantly worse. Same audio content over laptop speakers seems to play without problems. Attaching a pulseaudio verbose log in case that helps."
1797002,2018-10-10 03:00:05 UTC,This change was made by a bot.
1797002,2018-10-09 22:58:49 UTC,"Also side comment:
`Architecture: amd64` - though i am using: Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz"
1797002,2018-10-11 23:48:03 UTC,Thanks for you help.
1797013,2018-11-01 03:19:20 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1797018,2020-07-17 18:25:32 UTC,"Hi qiaomin032,"
1797018,2020-09-16 04:17:25 UTC,[Expired for octavia (Ubuntu) because there has been no activity for 60 days.]
1797025,2018-10-15 20:26:30 UTC,+1
1797025,2018-10-10 14:06:17 UTC,+1
1797030,2018-10-10 04:39:31 UTC,3. Does the problem only occur when using multiple monitors? Does it go away when you unplug all external monitors and just use the built-in display?
1797030,2018-10-10 05:12:18 UTC,"I am reminded of https://bugs.freedesktop.org/show_bug.cgi?id=98876, but that is about the modesetting driver which you are not using."
1797030,2018-10-10 04:37:49 UTC,"1. Do you mean fullscreen video playback only, or does the flicker happen with video in a window too?"
1797031,2018-10-10 05:00:07 UTC,This change was made by a bot.
1797031,2018-10-10 13:55:38 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1797031,2018-10-10 21:45:24 UTC,The bug still exists in 4.19rc7.
1797031,2018-10-10 21:48:22 UTC,"Forget to answer, this bug has existed on every kernel I've tried, which is limited to Ubuntu 18.04."
1797031,2018-10-11 02:26:32 UTC,Please upstream your patch so we can backport it to Ubuntu's kernel.
1797031,2018-10-11 03:28:15 UTC,"I've posted it to the linux-input list a few times but was ignored, so I tried here."
1797031,2018-10-11 03:55:04 UTC,"Upstream maintainers are busy, so it's quite normal. Please be patient."
1797031,2018-10-11 08:46:54 UTC,I'll try again someday.
1797032,2018-10-13 12:15:25 UTC,The conclusion seems to be that having light-locker or xscreensaver enabled is a way to prevent this glitch from occurring.
1797032,2018-10-12 04:51:46 UTC,"Xubuntu 18.10 daily image, last resume from suspend took 59 seconds before mouse-pointer returned.  In this case I was mostly just watching the clock (not waving it around; I started waving it around furiously at 56 seconds...)"
1797032,2018-10-12 03:45:30 UTC,"with Xubuntu 18.10 (yes X) booted (installed image on dx6120); dist-upgrade, 3x suspends using terminal & 3x suspends via menu with mouse-pointer, then noticed I'd not logged out since upgrade. I logged out, back in & repeat 3x suspends using term & 3x menu suspends and mouse-pointer was there each time."
1797032,2018-10-12 02:35:40 UTC,"NOTE:  my last comment relates to LUBUNTU - which is not XUBUNTU..
I've been testing the 'live' image & only just worked out why there were so many app changes!
Sorry my mistake !"
1797032,2018-10-12 01:09:43 UTC,I had my (installed) 18.10 system on dx6120 running (for testing lximage-qt elsewhere) so decided to try that (instead of 'live').
1797032,2018-10-11 10:19:47 UTC,"Does it change anything if you disable light-locker in 18.04, or enable it in 18.10? Also, can you restore the mouse pointer by switching to another VT and back?"
1797032,2018-10-10 22:03:39 UTC,Thanks Theo.
1797032,2018-10-11 02:32:20 UTC,"i booted lubuntu 18.10 (9-Oct-2018 iso); it has `xserver-xorg-video-nouveau` & started suspending (suspend, few secs, wake, look for pointer, repeat) but couldn't recreate.  Lubuntu uses xscreensaver so I was using mouse to wake up screensaver - so `killall xscreensaver`then repeated testing. I get an error on wake (""Error occurred starting screensaver. Action 'activate' failed. Ensure you have xscreensaver installed and running"") which I hit <enter> to bypass."
1797032,2018-10-10 22:46:59 UTC,In this case I suggest that you test with 18.04.1 also.
1797032,2018-10-10 21:35:19 UTC,This is a new issue in 18.10?
1797032,2018-10-10 06:42:53 UTC,"I've re-ran this test on another system (different video card) & no issue.
re-tested (daily-iso) trying to cause bug on same machine -- yes re-created briefly, but within 30 seconds mouse-pointer appeared (before I worked out where mouse-pointer was)"
1797032,2018-10-11 04:11:25 UTC,booted 18.04.1 x86 iso
1797038,2019-01-15 01:23:06 UTC,"I'm busy preparing a paper for an upcoming deadline, but I'll be back at circuit design in about a month. I'd be more than happy to help work on this feature beyond my little script then. Cheers, Sam"
1797038,2019-01-14 16:16:58 UTC,"It is, indeed, the same idea"
1797038,2018-10-23 12:04:40 UTC,"I put my script on GitHub, as I feel it works reasonably well: https://github.com/s-bear/expand_netlist"
1797038,2018-10-17 11:55:12 UTC,"I've played around with this concept using the Python interface for generating BoMs. For whatever reason my script doesn't run when it's added as a ""Netlist plugin"", but that's not particularly relevant. I prefer the BoM interface because it shows the docstring and script output."
1797038,2019-01-14 13:32:18 UTC,This sounds very similar to https://bugs.launchpad.net/kicad/+bug/1747397
1797039,2018-10-10 18:01:41 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1797039,2019-02-03 23:05:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797041,2018-10-10 10:46:47 UTC,puppet-pacemaker part of the fix: https://review.openstack.org/609351
1797041,2018-10-10 12:08:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/609367"
1797041,2018-11-21 19:01:34 UTC,"Change abandoned by Michele Baldessari (<email address hidden>) on branch: master
Review: https://review.openstack.org/609367"
1797047,2020-03-18 13:54:37 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1797054,2019-05-02 02:48:10 UTC,There have been a bit of renovations done in the destruction area since this bug was filed and this failure was observed.
1797055,2018-10-27 15:21:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797062,2018-10-22 18:00:52 UTC,The package has been published and the bug is being set to Fix Released
1797062,2018-10-22 17:33:31 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1023.24
1797062,2018-10-22 09:28:59 UTC,"4.15.0-1023.24 - gcp
Regression test CMPL, RTB."
1797062,2018-10-22 15:01:58 UTC,Does not need to go to the security pocket.
1797063,2018-11-06 10:52:17 UTC,The disco cycle is starting so that's unblocked now
1797063,2020-05-01 20:11:39 UTC,https://bugs.launchpad.net/ubuntu/+source/cron/3.0pl1-136ubuntu1
1797064,2020-05-01 20:11:19 UTC,https://bugs.launchpad.net/ubuntu/+source/libxml2/2.9.10+dfsg-5
1797065,2018-10-22 16:34:38 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1025.25
1797065,2018-10-22 17:08:43 UTC,The package has been published and the bug is being set to Fix Released
1797065,2018-10-16 11:20:53 UTC,"4.15.0-1025.25 - kvm
Regression test CMPL, RTB."
1797066,2018-10-22 17:22:19 UTC,This bug was fixed in the package linux-aws - 4.15.0-1025.25
1797066,2018-10-22 17:31:35 UTC,The package has been published and the bug is being set to Fix Released
1797066,2018-10-19 09:25:47 UTC,"4.15.0-1025.25 - aws
Regression test CMPL, RTB."
1797066,2018-10-22 15:04:20 UTC,Does not need to go to the security pocket.
1797073,2018-10-22 17:32:21 UTC,The package has been published and the bug is being set to Fix Released
1797073,2018-10-22 17:23:55 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1026.28
1797073,2018-10-17 01:39:15 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.15.0-1026.28/raspi2-4.15-proposed-published.html"
1797073,2018-10-15 07:31:45 UTC,Hardware Certification have begun testing this -proposed kernel.
1797076,2018-10-15 07:32:11 UTC,Hardware Certification have begun testing this -proposed kernel.
1797076,2018-10-18 09:58:09 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.15.0-38.41~16.04.1/xenial-4.15-proposed-published.html"
1797076,2018-10-18 11:13:51 UTC,"4.15.0-38.41~16.04.1 - lowlatency
Regression test CMPL, RTB."
1797076,2018-10-22 17:19:34 UTC,This bug was fixed in the package linux-hwe - 4.15.0-38.41~16.04.1
1797076,2018-10-22 17:33:09 UTC,The package has been published and the bug is being set to Fix Released
1797077,2018-10-12 08:37:45 UTC,"First of all there is a minor problem at line 1956 of sigcfg.dat: you have two lines with the signal aspect STOP_AND_PROCEED. However I don't think you solve the crash problem, which is probably due to an inconsistency of your .tdb file or between the .tdb file and other files. I have no other suggestions than restarting from an older of your route. The other way is to use the Open Rails source code and to use the debugger to find out where is your problem, however this requires knowledge of the C# language."
1797080,2018-10-22 08:11:45 UTC,"4.15.0-1023.24~16.04.1 - gcp
Regression test CMPL, RTB."
1797080,2018-10-22 17:28:47 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1023.24~16.04.1
1797080,2018-10-22 17:33:42 UTC,The package has been published and the bug is being set to Fix Released
1797081,2018-10-22 17:34:09 UTC,The package has been published and the bug is being set to Fix Released
1797081,2018-10-18 11:13:57 UTC,"4.15.0-38.41~16.04.1 - lowlatency
Regression test CMPL, RTB."
1797084,2018-10-10 08:33:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/609324"
1797084,2018-10-12 05:54:37 UTC,"Reviewed:  https://review.openstack.org/609324
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8e60531d11401c2c509a1255b49f89bc2bf81a74
Submitter: Zuul
Branch:    master"
1797084,2018-12-21 16:21:41 UTC,This issue was fixed in the openstack/neutron 14.0.0.0b1 development milestone.
1797088,2018-11-07 15:08:26 UTC,"I never noticed this before but you are correct.  When the hole size is the same as the pad size, no selection highlighting happens."
1797088,2019-01-17 03:49:22 UTC,"Not critical for 5.1, moving to 6"
1797094,2019-03-01 15:20:13 UTC,see https://bugs.launchpad.net/kolla-ansible/+bug/1816907
1797094,2019-04-12 21:08:45 UTC,Additional info:
1797094,2019-09-12 14:02:23 UTC,Is this still an issue with the latest code? If yes - please upload new logs.
1797094,2019-11-12 04:18:10 UTC,[Expired for kolla because there has been no activity for 60 days.]
1797097,2018-10-10 21:35:54 UTC,I added a simple python app in the hope that is sufficient for reproducing it.
1797097,2018-10-10 17:47:51 UTC,"Mh, I don't see this in evince... Where can i reproduce this?"
1797097,2018-10-10 12:26:25 UTC,"Thank you for your bug report, is that a regression from the recent SRU?"
1797097,2018-10-10 13:05:34 UTC,Hi i sadly can not comment on that. I noticed the bug while trying out an application on ubuntu 18.04 with all updates installed and it already had the same behavior. There where other problems too but they all seem to be fixed with ubuntu-themes_16.10+18.10.20181005.
1797100,2018-10-11 08:37:01 UTC,"Hi,"
1797100,2018-10-11 08:57:15 UTC,"Hi,"
1797100,2018-11-06 15:05:18 UTC,"Hi,"
1797101,2021-01-07 16:51:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797101,2021-01-14 13:51:17 UTC,See https://bugs.openjdk.java.net/browse/JDK-8259535
1797113,2018-10-10 13:07:35 UTC,I can't reproduce this cosmic. Can you try reproduce this on cosmic? Also specify how to reproduce? IS it specific to a particular app ?
1797113,2018-10-10 15:47:50 UTC,"On Wed, Oct 10, 2018 at 9:20 AM Khurshid Alam
<email address hidden> wrote:

>
> I can't reproduce this cosmic. Can you try reproduce this on cosmic?
> Also specify how to reproduce? IS it specific to a particular app ?
"
1797113,2018-10-10 23:55:28 UTC,I can't reproduce this on bionic either. The error something related to compiz/unity is broken. Do try installing ubuntu-unity-desktop to see if any package is missing. If you have upgraded from 16.04 then it could be the issue with compiz profile broken. Check askubuntu answer how to reset compiz.
1797113,2019-02-04 15:35:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797113,2019-02-04 15:36:18 UTC,"I have the same message, and in my case it is ""indicator-power-service"". The messages only appear when on battery, and stop if I kill the indicator."
1797113,2019-02-05 16:47:05 UTC,@Antonio Cunei
1797122,2018-10-10 13:33:57 UTC,"#************************************************************
#*                     MadGraph5_aMC@NLO                    *
#*                                                          *
#*                *                       *                 *
#*                  *        * *        *                   *
#*                    * * * * 5 * * * *                     *
#*                  *        * *        *                   *
#*                *                       *                 *
#*                                                          *
#*                                                          *
#*         VERSION 2.6.2.beta            2018-04-02         *
#*                                                          *
#*    The MadGraph5_aMC@NLO Development Team - Find us at   *
#*    https://server06.fynu.ucl.ac.be/projects/madgraph     *
#*                                                          *
#************************************************************
#*                                                          *
#*               Command File for MadGraph5_aMC@NLO         *
#*                                                          *
#*     run as ./bin/mg5_aMC  filename                       *
#*                                                          *
#************************************************************
set default_unset_couplings 99
set group_subprocesses Auto
set ignore_six_quark_processes False
set loop_optimized_output True
set loop_color_flows False
set gauge unitary
set complex_mass_scheme False
set max_npoint_for_channel 0
import model sm
define p = g u c d s u~ c~ d~ s~
define j = g u c d s u~ c~ d~ s~
define l+ = e+ mu+
define l- = e- mu-
define vl = ve vm vt
define vl~ = ve~ vm~ vt~
import model /home/ygh/program/MadDM_v3.0.beta/models/InertDoublet_UFO
generate relic_density
Traceback (most recent call last):
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/extended_cmd.py"", line 1501, in onecmd
    return self.onecmd_orig(line, **opt)
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/extended_cmd.py"", line 1450, in onecmd_orig
    return func(arg, **opt)
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/master_interface.py"", line 271, in do_generate
    return self.cmd.do_generate(self, line, *args, **opts)
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/madgraph_interface.py"", line 4474, in do_generate
    self.do_add("" "".join(args))
  File ""/home/ygh/program/MadDM_v3.0.beta/PLUGIN/maddm/maddm_interface.py"", line 500, in do_add
    return self.generate_relic([])
  File ""/home/ygh/program/MadDM_v3.0.beta/PLUGIN/maddm/maddm_interface.py"", line 768, in generate_relic
    self.search_dm_candidate(excluded_particles)
  File ""/home/ygh/program/MadDM_v3.0.beta/PLUGIN/maddm/maddm_interface.py"", line 322, in search_dm_candidate
    self.update_model_with_EFT()
  File ""/home/ygh/program/MadDM_v3.0.beta/PLUGIN/maddm/maddm_interface.py"", line 1078, in update_model_with_EFT
    self.exec_cmd(mg5_command, postcmd=False)
  File ""/home/ygh/program/MadDM_v3.0.beta/madgraph/interface/extended_cmd.py"", line 1528, in exec_cmd
    stop = Cmd.onecmd_orig(current_inter..."
1797122,2020-03-09 12:33:03 UTC,"Hi,"
1797123,2018-10-10 18:32:32 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1797129,2018-10-10 17:41:45 UTC,Add a retry interval: https://review.openstack.org/609494
1797129,2018-10-10 16:47:47 UTC,A similar effect happens for operations that are in the 'monitoring' state - every SDN journal thread will query the job status of every operation that is in the maintenance state. With many processes this could place quite a heavy load on the NEO API.
1797129,2018-10-10 13:59:29 UTC,"A retry interval would also make the retry mechanism more sane, ensuring that it is possible to retry over a long enough period of time that an error can be determined to be permanent rather than transient."
1797131,2018-10-10 14:27:07 UTC,The error tracker isn't part of Launchpad.  I'm reassigning this over in their direction.
1797131,2018-10-11 00:05:57 UTC,We currently don't have fine grained access controls for crashes at the Ubuntu Error Tracker and since it is possible for retraced crash reports to contain sensitive information we only grant access to software developers. I'm sorry if this wasn't clear when you filled out the form.
1797132,2019-03-21 22:30:06 UTC,We welcome merge proposals to fix this :-)
1797137,2018-10-10 15:07:18 UTC,In the feature please have a look at https://ubuntu-mate.community/t/how-to-report-problems-in-ubuntu-mate/17943 when reporting a problem.
1797137,2018-10-10 20:32:38 UTC,"I'm sorry but you missed the first part of the message, which is :"
1797138,2018-12-07 17:32:35 UTC,"Reviewed:  https://review.openstack.org/620953
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=8cead22781c50bc9b3767c5fe9d6ba196e3f5db3
Submitter: Zuul
Branch:    stable/rocky"
1797138,2018-12-06 15:06:13 UTC,"Reviewed:  https://review.openstack.org/610493
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=030442d07d7931d016044f150314a921167a31af
Submitter: Zuul
Branch:    master"
1797138,2018-11-29 16:21:52 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620953"
1797138,2018-10-23 13:38:48 UTC,"Reviewed:  https://review.openstack.org/611858
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=6e021da2e350db6548e216648ad5e14c4f6ab3c7
Submitter: Zuul
Branch:    stable/pike"
1797138,2018-10-23 12:57:36 UTC,"Reviewed:  https://review.openstack.org/611857
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=521744b5476111f584302f7f9f11399624030eb3
Submitter: Zuul
Branch:    stable/pike"
1797138,2018-10-19 12:40:45 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/611858"
1797138,2018-10-19 12:40:32 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/611857"
1797138,2018-10-17 17:54:34 UTC,"Reviewed:  https://review.openstack.org/609457
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=18987fbe32316e3ed8c7afcc3bf6199a10d0ee8b
Submitter: Zuul
Branch:    stable/queens"
1797138,2018-10-17 17:54:26 UTC,"Reviewed:  https://review.openstack.org/609456
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=91746c290be5fc374ad2389694779a7b57351c81
Submitter: Zuul
Branch:    stable/queens"
1797138,2019-01-24 15:33:12 UTC,"Change abandoned by Jose Luis Franco (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/611879"
1797138,2018-10-11 01:26:54 UTC,"Reviewed:  https://review.openstack.org/609422
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=610193f7fbefe325bf64ac52b176c8ef21342171
Submitter: Zuul
Branch:    stable/pike"
1797138,2018-10-10 15:37:18 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/609457"
1797138,2018-10-10 15:37:05 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/609456"
1797138,2018-10-10 14:34:25 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/609422"
1797138,2018-10-15 12:13:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/610493"
1797146,2019-08-12 21:11:29 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1797146,2018-10-10 15:48:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/609460"
1797146,2019-08-12 20:41:42 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1797146,2019-09-27 09:02:39 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1797146,2019-07-08 17:36:04 UTC,"Reviewed:  https://review.opendev.org/667355
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0142cc840f6680e5011381c6793173ebd0c9ee1e
Submitter: Zuul
Branch:    stable/rocky"
1797146,2018-10-10 14:58:08 UTC,"The obvious fix would be to only retrieve the vif type from the image if the VIF is not a direct passthrough. However, there might be more complications to it than this (some SR-IOV NICs provide a virtio interface, I'm told)."
1797146,2019-06-25 12:47:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/667355"
1797146,2019-06-25 12:46:24 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/667354"
1797146,2019-06-24 15:45:41 UTC,"Reviewed:  https://review.opendev.org/609460
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a235451578ad7af25268e82500dff5ba6a64ea4e
Submitter: Zuul
Branch:    master"
1797146,2019-07-05 01:01:13 UTC,"Reviewed:  https://review.opendev.org/667354
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d78310e67a8fcf59465907eddecba4f5145a0a6f
Submitter: Zuul
Branch:    stable/stein"
1797154,2018-10-10 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797154,2018-10-24 13:35:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1797154,2018-11-13 18:51:26 UTC,This bug was fixed in the package linux - 4.15.0-39.42
1797158,2018-12-06 16:29:16 UTC,"thank you for your bug report, the issue looks similar to bug #1802675"
1797161,2018-10-10 23:36:49 UTC,"Thanks Martin, I've filed https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/95 with upstream developers."
1797161,2018-10-12 06:22:17 UTC,Thanks!
1797161,2018-10-18 20:28:56 UTC,Ping: Is there any progress?
1797161,2018-10-24 18:21:33 UTC,"Since there is no progress, the bug will be published soonish..."
1797168,2018-10-15 12:11:48 UTC,"Can you provide the Juju version that you are using, the command you used to set the config value initially, and the command you used to change it?"
1797168,2018-11-13 17:02:17 UTC,"I am using juju version 2.4.5 and i am defining
container-image-metadata-url to private repository. After deployment of model i wanted to switch to different repository and wanted to update this metadata repo on deployed nodes as well. I can confirm online the nodes where lxd container was not created only uses the new repo. But if lxd container is already deployed and if i create new container it still refers to old repository."
1797168,2019-10-31 03:35:01 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1797169,2018-10-10 16:22:54 UTC,"The tempest test should handle this, either by being less precise for this field or just ignoring it."
1797174,2019-05-14 19:38:09 UTC,"I cannot reproduce this anymore on Ubuntu 19.04, gnome-shell 3.32"
1797174,2019-07-22 04:03:52 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1797174,2018-11-26 18:30:35 UTC,"I'll try to test on an X session in a bit.  One thing I have noticed is that while I still get the log messages, the unrotate behavior seems much better when setting the `dc=0` amdgpu module parameter (was also behaving better with the module blacklisted, but not sure about log messages), as per comments in https://gitlab.gnome.org/GNOME/mutter/issues/357 and https://gitlab.gnome.org/GNOME/mutter/issues/365"
1797174,2019-05-14 19:54:18 UTC,"(I still get the ""Failed to apply DRM plane"", but the immediate unrotation does not happen anymore. This is at least in Wayland, could not check X)"
1797174,2018-10-19 17:41:47 UTC,Thank you. I had written bug #1792813 about the sensors not being found with kernel 4.18. This is fixed in the mainline 4.19 (see the other report).
1797174,2018-10-19 17:27:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797174,2018-11-25 20:34:31 UTC,"@Joe: Can you confirm that you see the unrotation behavior and the log entry,
""gnome-shell[5422]: Failed to apply DRM plane transform 1: Invalid argument""
only in a Wayland session?"
1797178,2018-10-11 01:48:13 UTC,Please start by disabling your extensions:
1797178,2018-10-11 14:18:27 UTC,"Disabling extensions in the same session still shows the same behavior.  Logging out and back in again with them still disabled shows the same behavior on the ""Activities"" button, but app launchers respond to touch events appropriately.  Re-enabling them in the same session keeps the same state (""Activities"" button bad, app launchers good)"
1797178,2018-10-12 01:52:19 UTC,There might be some relation to bug 1725384.
1797178,2018-10-19 17:21:24 UTC,"maybe, although I'm using the vanilla gnome session, so the ubuntu-dock extension shouldn't be involved."
1797178,2018-11-03 11:10:03 UTC,"FWIW and FYI, I cannot repro this on Cosmic with Dell XPS 15 9575"
1797178,2018-11-07 16:18:32 UTC,"Doing a little more testing, it looks like everything works fine under Xorg, but am still seeing the activities button behavior under Wayland."
1797178,2018-11-08 18:21:55 UTC,"And with more testing, it seems like the activities button target is smaller and/or lower under Wayland than it is in Xorg.  I can get it to work if i aim for the bottom of the black top bar, vs the middle of it (while aiming for the middle results in the flash, but not activation of the Activites text)."
1797178,2018-11-25 21:26:21 UTC,"@Joe, at least in Wayland (did not test in X yet) the touch does not register when I touch anywhere right at the edge of the display. That goes for the whole perimeter of the display. E.g., srollbars of maximized windows on the right, dock launchers on the left, and the Gnome panel menu top right are not triggered in this case."
1797178,2019-07-22 04:04:17 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1797179,2019-10-08 13:10:06 UTC,Most errors are gone in version 3.34. Thanks!
1797179,2019-02-13 23:27:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797179,2018-10-11 17:47:57 UTC,"Could you report the crash to the upstream developers?
https://gitlab.gnome.org/GNOME/gnome-sound-recorder/issues"
1797179,2018-11-19 15:26:49 UTC,"> Could you report the crash to the upstream developers?
> https://gitlab.gnome.org/GNOME/gnome-sound-recorder/issues
"
1797181,2018-11-01 09:37:06 UTC,"It's the expected behavior of in-used volume migration, and there already was a ""_migrate_volume_completion"" [1] since [2], you need call it to complete the migrations. The tmp volume will be deleted."
1797181,2018-11-01 09:51:27 UTC,"""The interesting part is that retype with migration of an attached volume works fine."""
1797181,2018-11-01 10:13:58 UTC,But I found a other unexptected
1797181,2018-11-20 06:45:37 UTC,"Ignore #1, and it is the same bug mentioned in: https://bugs.launchpad.net/nova/+bug/1803961"
1797181,2018-11-20 15:28:48 UTC,"Hey Yikun, I think migrate_volume_completion won't be called by nova because the Cinder manager never updates the volume status as ""migrating."". It works when you attempt a retype because the manager updates the volume status as ""retyping"", thus calling the migrate_volume_completion module"
1797181,2019-02-25 10:05:43 UTC,"Hi there. I tried to solve it by adding a missing status ""migrating"" (https://review.openstack.org/#/c/638995/). I think it's logical to have an additional status for migrating like it realized for retyping. After that, Nova has no problem to run Cinder's migrate_volume_completion callback. Fell free to review my bugfix."
1797181,2019-03-22 13:02:27 UTC,https://bugs.launchpad.net/nova/+bug/1803961 is a duplicate of this and attempts to resolve the issue by using the migration_status of the volume within Nova.
1797187,2019-07-19 02:46:14 UTC,"A clarification on the following test steps:
1.	reduce 512 from the number of 2M-page
2.	add 1 1G-page
Expect the changes are accepted without any errors."
1797187,2019-08-13 20:46:18 UTC,Verified on 2019-08-12_20-59-00
1797187,2019-07-23 14:44:45 UTC,"Reviewed:  https://review.opendev.org/671553
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=16eb0ce4e0492a56458537d8d5205227e79e80c5
Submitter: Zuul
Branch:    master"
1797187,2019-07-18 19:15:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671553"
1797187,2019-05-30 18:04:23 UTC,"The ""Steps To Reproduce"" has been executed in a Bare Metal Dedicated Storage 2+3+2 having both, the same error message as reported and without the error message, depending on the value and CPU core. The system used to initially test was used for CEPH validation, another system is being installed to repeat the steps and give more clarity in the process followed and the results obtained."
1797187,2019-06-07 13:20:06 UTC,This was tested again in a brand new deployment:
1797187,2018-12-12 14:22:36 UTC,Thanks for the report.
1797187,2018-10-12 19:14:48 UTC,Targeting stx.2019.03 as this is not a common use-case
1797187,2019-07-18 01:49:38 UTC,Most of the reported error messages have been eliminated by my patch which was integrated to https://review.opendev.org/#/c/667811/.
1797190,2018-10-10 18:00:07 UTC,This change was made by a bot.
1797190,2018-10-10 18:23:26 UTC,"https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104
--
Cristian Aravena Romero (caravena)"
1797190,2018-10-10 18:34:55 UTC,"Hello,"
1797190,2018-10-10 18:44:22 UTC,List: linux-usb
1797190,2018-10-10 19:14:47 UTC,"On Wed, Oct 10, 2018 at 06:34:55PM +0000, <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=201371
>
>             Bug ID: 201371
>            Summary: It can not be formatted with 'gnome-disk-utility' the
>                     pendrive
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: Ubuntu 4.18.0-9.10-generic 4.18.12
"
1797194,2019-06-10 10:18:09 UTC,"I have taken a shot at this one. The root reason for the denials is not really calling ptrace, but accessing the /proc/<pid>/stat file from the process that calls NM using the DBus interface (see [1] for more information). This apparmor denial is triggered only when the caller process uid is root, for instance 'sudo nmcli' triggers the denial while 'nmcli' does not."
1797194,2018-10-17 14:54:42 UTC,"The ptrace denials are a known issue, and were in fact noted as harmless in bug #1602383. We've done a code inspection of NetworkManager itself, and found no usage of ptrace. Likewise an informal review of all NM dependencies was done, and the offending code wasn't located. This was also re-visited recently during development of the NM 1.10 snap, and the only usage of ptrace found in any of NM's dependencies was in libc6 itself, so ptrace may being called indirectly via libc6."
1797194,2018-10-17 15:15:18 UTC,"Unfortunately, while they are harmless from a system perspective, they do cause nuisance log messages."
1797195,2019-05-23 14:14:45 UTC,"Following the steps noted above, I was not able to recreate this on our 3.1.8 production or 3.2.4 test systems. I tested with line items in an on-order and received status."
1797207,2019-04-09 19:33:46 UTC,"We are on web client 3.2.4.
The Record summary date is pulling from the 260 correctly with the trailing - after the date.
In a record with a 264 instead, it is pulling from the fixed field Date1, with no trailing - after the date.
I confirmed where it was coming from by changing the fixed field to an incorrect date and reloading the record in a new tab."
1797214,2018-10-13 08:06:41 UTC,I wish there was the option to exclude liability accounts from being displayed in top spending and statistics reports
1797214,2018-10-13 16:44:22 UTC,"I'm going to create another fictional file and upload it as an example. In this example, there is the current account with the opening balance of 10K and a mortgage loan for 100k (balance -100K)"
1797214,2020-05-10 04:12:31 UTC,"The issue described here causes me to turn off the ""Top spending"" view."
1797214,2020-10-22 19:59:43 UTC,"yes, or just configure this accoutn to be out of report:
account dialog > behaviour
exclude from any report"
1797222,2018-11-06 10:52:28 UTC,The disco cycle is starting so that's unblocked now
1797222,2019-08-14 18:29:37 UTC,https://bugs.launchpad.net/ubuntu/+source/fontconfig/2.13.1-2ubuntu1
1797223,2019-09-19 11:59:02 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1797237,2019-03-24 23:39:25 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1797237,2019-03-24 23:04:04 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1797237,2019-03-22 18:05:51 UTC,"Reviewed:  https://review.openstack.org/640116
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8f7b778f82cb4f7e8b3655d8b51bb4c6b94da1d0
Submitter: Zuul
Branch:    stable/queens"
1797237,2019-03-05 01:01:33 UTC,"Reviewed:  https://review.openstack.org/640110
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=35a050a520683c104b8ba170cdca49ee0f9c9088
Submitter: Zuul
Branch:    stable/rocky"
1797237,2019-03-22 03:44:09 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1797237,2019-02-28 17:10:22 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640110"
1797237,2019-02-27 05:13:30 UTC,"Reviewed:  https://review.openstack.org/581453
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5bef746c9b50537dde47278a208c4457b42896d0
Submitter: Zuul
Branch:    master"
1797237,2019-02-11 20:04:25 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/609547
Reason: Dropped for https://review.openstack.org/#/c/581453/."
1797237,2018-10-10 21:14:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/609547"
1797237,2019-02-28 17:17:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/640116"
1797242,2018-10-10 21:28:13 UTC,"You can see the sad, sad, history, in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800"
1797242,2019-12-17 19:11:35 UTC,These were only needed for bionic and we can drop in focal.
1797242,2019-12-19 20:31:30 UTC,This bug was fixed in the package apparmor - 2.13.3-7ubuntu1
1797258,2019-01-12 09:03:27 UTC,Hi
1797258,2019-07-10 21:58:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797258,2019-07-10 22:03:45 UTC,"Hi Gudjon,"
1797262,2020-11-04 13:59:40 UTC,Should be now fixed by commits 74de7145fd6..83ad4695478 (CPRMAN model added).
1797262,2019-07-08 16:48:28 UTC,"latest series posted:
https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg00191.html"
1797262,2020-12-10 09:21:02 UTC,Released with QEMU v5.2.0.
1797262,2018-10-19 11:59:26 UTC,Isn't this likely due to the newer kernel accessing hardware we are not emulating properly?
1797262,2018-10-19 12:26:14 UTC,"On 19 October 2018 at 12:59, Alex Bennée <email address hidden> wrote:

> Isn't this likely due to the newer kernel accessing hardware we are not
> emulating properly?
"
1797270,2019-01-15 17:54:40 UTC,Fixed in https://review.openstack.org/#/c/620716/
1797270,2019-02-28 14:17:55 UTC,This issue was fixed in the openstack/senlin-tempest-plugin 0.2.0 release.
1797287,2018-11-21 04:05:35 UTC,"This should go in via Debian, not via Ubuntu. Please submit it there."
1797287,2019-03-22 18:56:12 UTC,I no longer waste my time by contributing to Debian
1797289,2018-10-11 16:43:05 UTC,"To give an overview over the changes:
https://web.ics.purdue.edu/~gblack/Trace%20Temp%20Study.pdf"
1797289,2018-10-13 07:28:43 UTC,"OK,I will upload the IPC-2152-2009 standard tomorrow."
1797289,2018-10-13 13:56:23 UTC,Please do not upload IPC documents to the bug tracker.
1797289,2018-10-13 14:27:38 UTC,Is there a copyright risk?
1797289,2018-10-13 15:34:40 UTC,"AFAIK, IPC standards are copyrighted material and cannot be freely
distributed so please do not post them on any KiCad website."
1797289,2018-10-14 02:45:03 UTC,OK
1797289,2019-04-20 22:19:48 UTC,"Just to comment on this. Typically the IPC-2221 is more conservative than IPC-2152 but that isn't always the case nor is it right.
SaturnPCB includes IPC-2152 with/without modifiers BUT how it does it or validation is not included."
1797290,2018-10-29 21:28:04 UTC,"python3-argcomplete does seem quite useful for complex pythonic autocompletion, but it seems to have downside as well - users will need to run a script to set it up first:
https://pypi.org/project/argcomplete/#activating-global-completion"
1797290,2018-10-15 15:34:26 UTC,"This has bugged me too, unless someone else gets to this first I'll take a look at adding it."
1797290,2018-10-15 19:36:09 UTC,I recommend you look at python3-argcomplete for this :)
1797296,2018-10-11 03:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797296,2019-01-07 22:48:57 UTC,"Jan  7 02:41:41 ceo1homenx kernel: [40698.439354] WARNING: CPU: 6 PID: 24218 at drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau]
Jan  7 02:41:41 ceo1homenx kernel: [40698.439355] Modules linked in: vfio_pci vfio_virqfd vfio_iommu_type1 vfio rfcomm ebtable_filter ebtables ip6table_filter devlink ip6_tables iptable_filter bpfilter cmac bnep bridge stp llc dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm wmi_bmof dell_smbios dell_wmi_descriptor irqbypass uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common crct10dif_pclmul crc32_pclmul videodev ghash_clmulni_intel pcbc media joydev aesni_intel dcdbas snd_hda_codec_hdmi input_leds snd_hda_codec_realtek snd_hda_codec_generic aes_x86_64 nouveau snd_usb_audio snd_hda_intel snd_usbmidi_lib snd_hda_codec crypto_simd cryptd snd_hda_core snd_hwdep glue_helper snd_pcm i915 snd_seq_midi snd_seq_midi_event intel_cstate intel_rapl_perf snd_rawmidi mxm_wmi ttm
Jan  7 02:41:41 ceo1homenx kernel: [40698.439378]  snd_seq 8250_dw btusb btrtl btbcm btintel bluetooth ecdh_generic drm_kms_helper snd_seq_device snd_timer snd idma64 soundcore drm i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt mac_hid virt_dma mei_me mei video wmi acpi_pad sch_fq_codel parport_pc ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx ahci i2c_i801 intel_lpss_pci mdio libahci intel_lpss pinctrl_sunrisepoint pinctrl_intel
Jan  7 02:41:41 ceo1homenx kernel: [40698.439399] CPU: 6 PID: 24218 Comm: kworker/6:1 Tainted: G        W         4.18.0-13-generic #14-Ubuntu
Jan  7 02:41:41 ceo1homenx kernel: [40698.439400] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018
Jan  7 02:41:41 ceo1homenx kernel: [40698.439423] Workqueue: events nouveau_cli_work [nouveau]
Jan  7 02:41:41 ceo1homenx kernel: [40698.439436] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau]
Jan  7 02:41:41 ceo1homenx kernel: [40698.439436] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 7a a9 b7 f9 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
Jan  7 02:41:41 ceo1homenx kernel: [40698.439454] RSP: 0018:ffffb8f8486ffdb8 EFLAGS: 00010282
Jan  7 02:41:41 ceo1homenx kernel: [40698.439455] RAX: 00000000fffffffe RBX: ffffb8f8486ffde8 RCX: 0000000000000000
Jan  7 02:41:41 ceo1homenx kernel: [40698.439455] RDX: 0000000000000010 RSI: ffffb8f8486ffd28 RDI: ffffb8f8486ffdc8
Jan  7 02:41:41 ceo1homenx kernel: [40698.439456] RBP: ffffb8f8486ffdd8 R08: ffffffffc0970b40 R09: 0000000000000000
Jan  7 02:41:41 ceo1homenx kernel: [40698.439456] R10: ffff8af646b1d300 R11: 0000000000000030 R12: ffffb8f8486ffe20
Jan  7 02:41:41 ceo1homenx kernel: [40698.439457] R13: dead000000000200 R14: dead000000000100 R15: ffff8af646b1dde0
Jan  7 02:41:41 ceo1homenx kernel: [40698.439458] FS:  0000000000000000(0000) GS:ffff8af73ed80000(0000) knlGS:0000000000000000
Jan  7 02:41:41 ceo1homenx kernel: [40698.439459] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan  7 02:41:41 ceo1homenx kernel: [40698.439459] CR2: 00007f2b0f778..."
1797296,2019-01-07 22:52:17 UTC,"an  7 06:39:01 ceo1homenx CRON[29352]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Jan  7 06:47:12 ceo1homenx kernel: [55429.029596] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Jan  7 06:47:12 ceo1homenx kernel: [55429.029607] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
Jan  7 06:47:12 ceo1homenx kernel: [55429.029615] nouveau 0000:01:00.0: fifo: channel 12: killed
Jan  7 06:47:12 ceo1homenx kernel: [55429.029622] nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery
Jan  7 06:47:12 ceo1homenx kernel: [55429.029951] nouveau 0000:01:00.0: Xorg[1901]: channel 12 killed!
Jan  7 06:47:37 ceo1homenx libvirtd[1522]: 2019-01-07 12:47:37.719+0000: 1522: error : virKeepAliveTimerInternal:140 : internal error: connection closed due to keepalive timeo
ut
Jan  7 06:49:46 ceo1homenx kernel: [55582.936599] INFO: task kworker/u16:12:28366 blocked for more than 120 seconds.
Jan  7 06:49:46 ceo1homenx kernel: [55582.936602]       Tainted: G        W         4.18.0-13-generic #14-Ubuntu
Jan  7 06:49:46 ceo1homenx kernel: [55582.936603] ""echo 0 > /proc/sys/kernel/hung_task_timeout_secs"" disables this message.
Jan  7 06:49:46 ceo1homenx kernel: [55582.936604] kworker/u16:12  D    0 28366      2 0x80000000
Jan  7 06:49:46 ceo1homenx kernel: [55582.936636] Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau]
Jan  7 06:49:46 ceo1homenx kernel: [55582.936637] Call Trace:
Jan  7 06:49:46 ceo1homenx kernel: [55582.936642]  __schedule+0x29e/0x840
Jan  7 06:49:46 ceo1homenx kernel: [55582.936644]  schedule+0x2c/0x80
Jan  7 06:49:46 ceo1homenx kernel: [55582.936646]  schedule_timeout+0x258/0x360
Jan  7 06:49:46 ceo1homenx kernel: [55582.936674]  ? nv50_wndw_atomic_destroy_state+0x1d/0x20 [nouveau]
Jan  7 06:49:46 ceo1homenx kernel: [55582.936676]  dma_fence_default_wait+0x1fc/0x260
Jan  7 06:49:46 ceo1homenx kernel: [55582.936678]  ? dma_fence_release+0xa0/0xa0
Jan  7 06:49:46 ceo1homenx kernel: [55582.936679]  dma_fence_wait_timeout+0x3e/0xf0
Jan  7 06:49:46 ceo1homenx kernel: [55582.936685]  drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
Jan  7 06:49:46 ceo1homenx kernel: [55582.936704]  nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
Jan  7 06:49:46 ceo1homenx kernel: [55582.936705]  ? __switch_to_asm+0x40/0x70
Jan  7 06:49:46 ceo1homenx kernel: [55582.936706]  ? __switch_to_asm+0x34/0x70
Jan  7 06:49:46 ceo1homenx kernel: [55582.936725]  nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
Jan  7 06:49:46 ceo1homenx kernel: [55582.936727]  process_one_work+0x20f/0x3c0
Jan  7 06:49:46 ceo1homenx kernel: [55582.936728]  worker_thread+0x34/0x400
Jan  7 06:49:46 ceo1homenx kernel: [55582.936730]  kthread+0x120/0x140
Jan  7 06:49:46 ceo1homenx kernel: [55582.936731]  ? pwq_unbound_release_workfn+0xd0/0xd0
Jan  7 06:49:46 ceo1homenx kernel: [55582.936732]  ? kthread_bind+0x40/0x40
Jan  7 06:49:46 ceo1homenx kernel: [55582.936733]  ret_from_fork+0x35/0x40
Jan  7 06:49:46 ceo1homenx kernel: [55582.936736] INFO: task kworker/u16:1:28944 blocked for more than 120 seconds.
Jan  7 06:49:46 ceo1homenx kernel: [55582.936737]       Tainted: G   ..."
1797296,2019-06-26 18:45:10 UTC,"Apparently this is happening across the distro world.  Thought the link below is fedora, notice it includes debug detail from ubuntu, debian, etc."
1797296,2019-06-26 18:52:18 UTC,"This is against disco, crashed not an hour ago.  Detail:"
1797296,2019-06-26 18:54:33 UTC,"The above:
uname -a
Linux ceo1homenx 5.0.0-19-generic #20-Ubuntu SMP Wed Jun 19 17:04:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1797297,2021-01-08 01:33:56 UTC,See also LP:1909569
1797297,2020-12-28 23:57:04 UTC,See also LP:1723184
1797297,2020-12-18 04:19:52 UTC,To add:
1797297,2020-11-05 08:00:17 UTC,Also LP:1673325
1797297,2018-10-11 09:02:11 UTC,"Updating this leader setting more aggressively will help, and a quick fix so can be done."
1797297,2018-10-11 09:06:27 UTC,"Ideally, the only thing the lead unit does is to select which of the unit is primary. We don't want the primary unit in an ubuntu-repository-cache deployment to flap every time there is a netspit (which will trigger Juju leadership elections and flapping)"
1797305,2019-09-16 19:51:26 UTC,"Reviewed:  https://review.opendev.org/609843
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=1ded0d6c8793ca3eca573c098cef78b5ae41f080
Submitter: Zuul
Branch:    master"
1797305,2019-10-03 16:34:51 UTC,This issue was fixed in the openstack/swift 2.23.0 release.
1797305,2019-10-05 04:04:33 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/686864"
1797305,2019-10-05 05:38:39 UTC,"Reviewed:  https://review.opendev.org/686864
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=bfa8e9feb51f2b10adfec3a741661a76fcf73216
Submitter: Zuul
Branch:    feature/losf"
1797306,2018-11-21 08:56:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797322,2018-10-23 15:11:35 UTC,uploaded to the bionic SRU queue now
1797322,2018-11-05 22:09:01 UTC,This bug was fixed in the package gnome-settings-daemon - 3.28.1-0ubuntu1.1
1797322,2018-10-30 05:00:56 UTC,"@Brian
The issue is gone after upgrading gnome-settings-daemon to 3.28.1-0ubuntu1.1."
1797322,2018-10-29 19:21:11 UTC,"Hello ethan.hsieh, or anyone else affected,"
1797322,2018-10-17 09:36:34 UTC,@Sebastien
1797322,2018-11-05 21:59:02 UTC,"The verification of the Stable Release Update for gnome-settings-daemon has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1797322,2018-10-11 17:47:45 UTC,This bug was fixed in the package gnome-settings-daemon - 3.30.1.2-1ubuntu2
1797322,2018-10-11 14:33:02 UTC,"Upload to cosmic, it would probably be a good candidate for a bionic SRU which I guess the oem team is going to want? If so could someone adapt the description to be SRU compliant (https://wiki.ubuntu.com/StableReleaseUpdates) with impact/test case/regression potential sections.
The description has details but lack an user visible description of the error (is it that e.g bluetooth or wifi fails to be restored after resume?)"
1797322,2018-10-11 14:28:03 UTC,Thanks for your work
1797322,2018-10-11 08:13:05 UTC,"Thanks, don't forget to subscribe ubuntu-sponsors when you have a patch that needs to be reviewed/sponsored, I'm subscribing that team for you now"
1797322,2018-10-11 07:44:55 UTC,"Have sent a merge request to GitLab and wait for approval.
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/57"
1797322,2018-10-12 02:41:53 UTC,Thanks for your reminder. Bug description has been updated.
1797330,2020-04-20 10:44:22 UTC,Passed with 4.4.0-1070.77 - kvm
1797331,2020-04-20 10:43:49 UTC,Passed with 4.4.0-1070.77 - kvm
1797333,2020-05-19 10:49:24 UTC,This is more a libvirt / nfs question than a nova question. I suggest to reach out to the libvirt community: https://libvirt.org/bugs.html
1797335,2020-11-02 18:40:35 UTC,This bug was fixed in the package glibc - 2.27-3ubuntu1.3
1797335,2020-11-02 18:30:37 UTC,"The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1797335,2020-10-09 18:10:37 UTC,Verified 2.27-3ubuntu1.3 on Bionic:
1797335,2020-09-13 01:42:45 UTC,"All autopkgtests for the newly accepted glibc (2.27-3ubuntu1.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1797335,2020-09-10 23:04:10 UTC,"Hello Paul, or anyone else affected,"
1797335,2020-05-22 22:53:37 UTC,"Fixed in glibc 2.29 and later, included in Ubuntu 19.04 and later."
1797335,2018-11-30 00:34:12 UTC,"The bug has been opened on glibc and being (or already) fixed :
https://sourceware.org/bugzilla/show_bug.cgi?id=23709"
1797335,2018-11-29 22:50:45 UTC,"I notice that your cpu flags list avx2; this suggests the possibility that the code path being used is one that's specific to avx2, not just sse2.  I have attempted to reproduce this on CPUs both with and without avx2 and I cannot.  I get no statistically-significant difference in runtime, on either the avx2 system or the non-avx2 system, with glibc from Ubuntu 16.04 vs. glibc from Ubuntu 18.04."
1797335,2018-11-29 22:43:07 UTC,"I can't reproduce this here.  I'll note that I'm testing on a Broadwell and you're on a Haswell, but I'd hope that doesn't make a huge difference, unless H.J. Lu's latest round of CPU detection stuff has gone amok."
1797335,2018-10-11 11:06:25 UTC,"$ file strstr
strstr: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=f09b9ae65046d6650a9b7007a9aa5d6d472a2d06, not stripped"
1797335,2018-10-11 10:29:38 UTC,"Yes, but to be absolutely certain, the `strstr` binary you created is a 64-bit binary?"
1797335,2018-10-11 09:45:22 UTC,"I'm running on amd64, i7 cpu :"
1797335,2018-10-11 09:24:29 UTC,Regarding:
1797335,2018-11-29 23:03:49 UTC,"On my system, I can clearly see it selecting the sse2 implementation (there is no AVX implementation of strstr)"
1797343,2018-10-11 20:13:59 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1797343,2019-05-15 13:57:44 UTC,"Does Ubuntu have the ability to remove unmaintained and vulnerable community packages? If so, please remove tinc, as it looks like in several months, fixes present in Debian have not made their way here, putting users at unnecessary risk."
1797343,2019-05-15 13:58:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797345,2018-10-12 05:58:41 UTC,"As you said, the issue you report has been fixed on Modules v4.1.2. Other special character escaping issues are also fixed on this bugfix release:"
1797345,2018-10-11 12:20:48 UTC,And here is the upstream commit that fixes this bug (part of v4.1.2 release):
1797345,2019-02-07 14:16:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797346,2018-10-11 09:47:57 UTC,"The clients were inconsistent with their database requests, with only one unit requesting the 'citext' extension. This unit never considered the database available, because the server had not installed the requested extension yet, because the server only looks at an arbitrary unit and trusts that they will converge (a common assumption)."
1797348,2019-10-14 11:55:54 UTC,"Found on Disco KVM (5.0.0-1020.21 - kvm) as well:
msgstress04 1 TBROK : msgstress04.c:365: Kill failed to kill child 3"
1797350,2018-12-02 21:57:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797351,2018-10-12 01:54:04 UTC,fixed by this patch: https://review.openstack.org/#/c/609902/
1797352,2018-10-11 10:16:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797352,2018-10-11 10:34:29 UTC,"You should report problem upstream, or is this Ubuntu specific bug?"
1797352,2018-10-11 11:55:45 UTC,I`ve created issue on https://gitlab.gnome.org/GNOME/gnome-flashback/issues/12
1797352,2018-10-11 12:23:29 UTC,"The attachment ""add-support-modifiers-only.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1797357,2018-10-15 21:53:49 UTC,"Aahh, well that makes another extra step for me.  Because until we can configure the snap notification (make it smaller or more transparent or further away or change the distance in which the mouse triggers it) I keep mine turned off because it blocks my view too much.  Once in a while I need to see it, if I can't be sure where the snap happens, but otherwise I just watch for the visible snap.  So I would have to first turn the notification on, before I could see it."
1797357,2019-12-10 20:13:24 UTC,Migrated to:  https://gitlab.com/inkscape/inbox/issues/1343
1797357,2018-10-11 11:18:27 UTC,"I just had an extra thought.  If the purpose of this handle is merely to drag the object (without switching to Selection tool), maybe the X doesn't need to be in the center of the object??"
1797357,2018-10-15 17:26:10 UTC,"Actually you *can* draw new objects from the center despite the center handle:
If you move the mouse cursor within ""snapping distance"" of the center you'll see the corresponding tooltip (i.e. ""Handle to object midpoint"" or ""Handle to object rotation center"") and can draw the shape you want."
1797358,2018-10-11 14:08:20 UTC,We saw that VRCNTR_WIRE_DROP_INVALID_VIF gets incremented for packets arriving over the wire. The source side seems to be operating as expected. It is on the destination side where the packets are dropped.
1797358,2018-10-12 09:55:32 UTC,I am seeing this behaviour when using nfp_p1 port and not nfp_p0.
1797358,2018-10-23 08:24:55 UTC,"With nfp_p0 interface, the issue was not reproduced."
1797359,2018-10-11 11:09:40 UTC,"Hello,"
1797359,2018-10-11 11:27:30 UTC,"Created attachment 278991
dmesg_4.19.0-041900rc7-generic"
1797359,2018-10-11 11:31:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797359,2018-10-11 11:50:07 UTC,"Hello,"
1797361,2018-11-01 19:00:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797362,2019-09-17 04:17:43 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1797362,2019-07-18 23:15:03 UTC,Thanks for filing a bug.
1797366,2019-06-10 10:08:50 UTC,"Bug 1832212 is slightly related, although not a dependency."
1797366,2019-07-02 10:20:36 UTC,Fixed in stable r18993 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18993>.
1797366,2018-10-12 13:44:54 UTC,Thanks for debugging and confirming.  At least for now I'll swap that file to be a real file rather than symlink to get this working again.
1797366,2018-10-12 23:56:12 UTC,We could just see if it looks like a path and resolve it ourselves.
1797370,2018-10-12 13:21:27 UTC,We are on 3.1.5 and are affected by this bug.  What follows is a cataloger's description of encountering the bug:
1797370,2020-04-06 20:51:33 UTC,"In 3.4 the option is to ""Export non-imported records"" and it does download an *.mrc file."
1797370,2020-04-06 20:52:28 UTC,"Noting, because I didn't make this totally clear, that 3.4 uses the new Angular Import/Export interface."
1797373,2020-02-10 23:38:37 UTC,I just tested this on 20.04 with the 6.4.0-0ubuntu3 deb as well as the 6.4.0.3 snap.
1797373,2019-12-14 20:32:23 UTC,"Same here on Dell XPS 13 (9333) / Xubuntu 19.10 / LO 6.3.3. 3D slide transitions don't work at all, but **only** when I use the **default distro packages**. OpenGL 3D transitions are broken within Debian / Deepin / Ubuntu, Fedora and even Manjaro/Arch Linux (see https://www.reddit.com/r/libreoffice/comments/9g4ets/libreoffice_impress_61_doesnt_show_3d_transitions for example)."
1797373,2019-11-22 09:43:11 UTC,Please accept my apologies. The issues I saw had to do with broken 3D acceleration in the VMs I used to test this. I can confirm this is in fact working in the 6.3.3 deb from:
1797373,2019-11-21 13:13:52 UTC,"(In reply to Marcus Tomlinson from comment #8)

> Also, reproducible against latest 6.4.0.0.alpha1-1 deb from:
>
> http://dev-builds.libreoffice.org/daily/master/
"
1797373,2019-10-18 07:40:36 UTC,"Also, reproducible against latest 6.4.0.0.alpha1-1 deb from:"
1797373,2019-10-18 07:32:05 UTC,"Reproducible (as in, 3D transitions don't work) on both Ubuntu 19.10 and Debian Stretch against latest 6.3.2 deb from:"
1797373,2019-10-17 19:30:46 UTC,Turning use opengl for all rendering off and on again fixed 2d animations but 3d still don't work.
1797373,2019-10-17 19:27:17 UTC,I'm running kubuntu 19.10 with all latest updates. No transitions work. Option for 3d accel is greyed out.
1797373,2019-05-17 01:36:09 UTC,Related bug on MacOS: bug 57128
1797373,2019-04-05 13:51:44 UTC,"I can confirm with 6.2, although I've got a couple extras that didn't work:"
1797373,2019-01-08 15:56:39 UTC,"Thank you for reporting the bug.
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build"
1797373,2018-12-08 23:03:26 UTC,"While the problem might be gone by the time we get to 6.3.0.0., for now I can *confirm* that Olivier's observations. 3D-transitions do not work for me, regardless if hardware acceleration and OpenGL are activated or deactivated."
1797373,2018-11-29 09:50:09 UTC,Bug not reproducible in version
1797373,2018-11-16 12:51:30 UTC,I reported the bug upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=121463
1797373,2018-11-16 12:51:07 UTC,"Description:
(initially reported on ubuntu: https://launchpad.net/bugs/1797373)"
1797373,2018-11-16 11:22:59 UTC,"yes, hardware acceleration is checked."
1797373,2018-11-16 10:04:36 UTC,"Can you confirm that the option to use hardware acceleration is checked under ""Tools > Options > LibreOffice > View"" ?"
1797373,2019-05-11 15:04:18 UTC,Tested 6.3.0.0.alpha0+ and can confirm that 3D transitions are now working as expected. But 6.2.3 shows only black screen while any 3d transition is running.
1797375,2018-10-15 21:38:11 UTC,"You may want to think about something that can be run via the inputs.exec plugin, that's super trivial to do, I knocked out some for the retracers in an hour or so a while back.  The telegraf plugin story (i.e. plugins requiring compilation) seems kind of unfortunate but it looks like you may be able to dump a config into /etc/telegraf/telegraf.d/whatever.conf with your inputs.exec config and have it work sanely, I'll have to test that out."
1797381,2018-12-11 14:48:04 UTC,"Would be nice to fix but it was decided to not be important enough at the moment to rls target, tagging -notfixing"
1797381,2018-12-05 01:49:43 UTC,Maybe merge with bug 1760399?
1797381,2019-07-22 03:49:26 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1797381,2018-10-16 08:19:50 UTC,"It might be a gnome-shell/OSK issue, sound similar to some of the issues Andrea was looking at where ... Andy, could you have a look once you are done with helping Marco with the boot issues?"
1797381,2018-10-16 10:05:45 UTC,That's a known regression from commit https://gitlab.gnome.org/GNOME/gnome-shell/commit/fc5ab4470445992b1ad4338290deb24e6b1c5ce2
1797387,2018-10-11 14:04:22 UTC,"Doesn't occur on 18.04, CentOS 6 or CentOS 7"
1797387,2018-10-11 14:02:10 UTC,Reproduced on Ubuntu 14.04 and 16.04
1797387,2018-10-12 11:50:46 UTC,Reproduced on debian 8 but not debian 9. I will log a bug through debian also.
1797388,2018-10-15 12:38:34 UTC,This is unfortunately difficult to make smoother. I agree with you but this is the best for the limitations we've got at the moment.
1797389,2018-10-11 14:09:08 UTC,Hi! I have this problem too! Canonical please fixed it!
1797389,2018-10-11 14:14:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797389,2019-02-19 10:47:12 UTC,Have this critical bug too.
1797389,2020-04-17 08:25:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797389,2020-04-17 08:26:30 UTC,ubuntu 20.04 have this critical bug too.
1797390,2019-08-27 07:47:16 UTC,"We didn't update this cycle and it's late now, tagging as blocked by ff again"
1797390,2021-01-20 19:46:48 UTC,Debian just updated to 8.12.16 and its bug was closed
1797390,2021-01-21 19:44:44 UTC,https://bugs.launchpad.net/ubuntu/+source/libphonenumber/8.12.16-3
1797394,2018-10-27 20:36:59 UTC,"This may help pinpoint the cause: I did a virgin install of 18.04 on the same machine, and now hplip works, printer is found, printing (and scanning as well) is OK. Therefore the problem must be with the distribution upgrade process."
1797394,2018-10-27 16:45:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797397,2019-04-13 14:59:03 UTC,"No promises on how quickly this gets done, but now that the python3 port is released, this is the next major feature on my list."
1797397,2019-10-30 19:25:55 UTC,Git master now has a (at least for me) functioning implementation for SigningTable and KeyTable.
1797397,2020-01-03 23:30:27 UTC,"1.2.0 2020-01-03
 - Add support for SigningTable, KeyTable, and KeyTableEd25519 (LP: #1797397)
 - Add support for specifying MinimumKeyBits for RSA signatures
 - Add support for SignHeaders feature, thanks to Ralph Seichter for the patch
 - Add support for specifying DNSTimeout (bumps required dkimpy version to 1.0)
 - Add information on message content conversion to README
 - Add new expand option to setup.py so various file system locations can be
   specified at build/install time rather than being hard coded
 - Install openrc init file for Gentoo and other openrc users
 - Add support for passing PID file name on command line to make it easier to
   keep system init and daemon configuration in sync
 - Add support for storing DKIM failed mails in a specified
   DiagnosticDirectory
 - Fix startup logging so it provides information at a useful time
 - Fix verify processing so missing (optional) i= tag doesn't cause the milter
   to fail  (LP: #1842250)
 - Fix message extraction so that signing in the same pass through the milter
   as verifying works correctly
 - Add debug logging for content type to assist troubleshooting MIME
   conversion issues
 - Fix variable initialization so mailformed mails missing body From do not
   cause a traceback (LP: #1844161)
 - Catch more ascii encoding errors to improve resilience against bad data
   (LP: #1844189)
 - Fix sysv init so it works (LP: #1839487)
 - Make error logging more explicit to aid debugging
 - Remove SigningTableEd25519 from documentation - it was never implemented
   and a per algorithm signing table turns out not to be needed
 - Delete own_socketfile to resolve race condition where the permissions
   change fails on a Unix socket because it hasn't been created yet (libmilter
   will do this correctly on its own based on umask, the milter doesn't need
   to do it) (LP: #1849712)"
1797398,2018-10-15 12:57:18 UTC,"Thanks, I've added this to the 19.04 planning doc as a field request."
1797400,2018-11-06 09:52:27 UTC,I confirm for 32 bit FC13.
1797400,2018-11-06 09:54:16 UTC,https://bugs.launchpad.net/pcb/+bug/1074268
1797406,2018-10-26 14:31:13 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1027.29
1797406,2018-10-24 13:35:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1797406,2018-11-13 18:51:26 UTC,This bug was fixed in the package linux - 4.15.0-39.42
1797406,2018-10-12 07:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797406,2018-10-24 08:34:45 UTC,We are re-spinning bionic/linux-raspi2 based on previous SRU cycle to fix this issue.
1797406,2018-10-12 07:28:51 UTC,"@Paolo, since the patch is targeted at bionic/master I added the respective task and nomination. I let you handle how you want to set status of linux-raspi2 tasks."
1797411,2019-02-12 02:35:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797417,2019-09-23 13:11:02 UTC,"By the way, mate-panel works in my configuration. And it uses 32-bit visuals for systray and icons."
1797417,2019-09-23 13:10:02 UTC,"(In reply to Ivan A. Melnikov from comment #36)

> I'm attaching the patch with these two simple changes. Applying it to
> xfce4-panel 4.14.0 fixed the issue on my machine.
"
1797417,2019-09-23 12:52:25 UTC,"Created attachment 9050
patch that fixes the problem on my machine"
1797417,2019-09-19 14:25:54 UTC,I tested MATE in VirtualBox with compositing disabled and couldn't reproduce the panel icon problem.
1797417,2019-09-19 11:48:25 UTC,"Has anyone tested if mate-panel exposes this bug too? If not, their code base is fairly similar, so the fix may be there..."
1797417,2019-09-19 11:27:52 UTC,"I also tried a few things. First, as far as I understood, parent-relative background is not set with NULL, there is a special pattern that should be used instead:"
1797417,2020-07-31 21:44:24 UTC,I continue to have this problem with a machine updated to 20.04.1 with xfce-panel 4.14.3.  Am I supposed to delete some old configuration files to reset something?
1797417,2019-09-18 19:59:59 UTC,"(In reply to Simon Steinbeiss from comment #29)

> Created attachment 9037 [details]
> Always set parent-relative background
>
> I'm not sure it's helpful to not set a parent-relative background when
> compositing is disabled, so I went for always enabling it.
> This fixes the problem for me.
>
> Please test the attached patch! Thanks
"
1797417,2019-09-18 19:42:52 UTC,*** Bug 13948 has been marked as a duplicate of this bug. ***
1797417,2019-09-18 19:39:39 UTC,"Created attachment 9037
Always set parent-relative background"
1797417,2019-09-18 19:03:17 UTC,"Hi Ivan, thanks for debugging - that sounds like a most likely cause.
I'm not sure I understand why yet, but at least that's a good direction to start searching."
1797417,2019-09-05 10:50:00 UTC,"I'm also affected by the problem, with gtk+3 3.24.11 and xfce4 panel 4.14.0."
1797417,2019-09-03 14:42:46 UTC,Good news. Linux Mint team are developing a cross platform/cross desktop panel tray technology.
1797417,2019-09-23 16:15:52 UTC,It works here too on Gentoo and xfce4-panel-4.14.0. Thanks a lot Ivan!
1797417,2019-09-18 20:50:16 UTC,"Ok, no need to test the patch. Unfortunately I was only looking at apps with 16x16 opaque icons, which looked fine.
So no, it doesn't work."
1797417,2019-09-23 20:02:30 UTC,Patch 9050 fixed the problem for me. Tested with volumeicon-alsa on ubuntu 19.04.
1797417,2019-09-23 22:11:16 UTC,Ivan A. Melnikov referenced this bugreport in commit 820de57c44c381e47091d3a7e214852bf8fafb53
1797417,2019-09-23 22:12:06 UTC,"@Ivan: I reviewed and tested the patch, makes a lot of sense! Thanks a bunch for taking a look at this!"
1797417,2019-09-24 07:45:13 UTC,"Simon, thank you for reviewing and merging."
1797417,2019-12-20 08:07:10 UTC,"I built Xfce-panel 4.14.1 for LinuxMint 19.3 'Tricia' (which has Xfce 4.14 by default) GTK 3.0-3.22.30 , as I had the same issue. But it still did not work out of the box. On checking bug #16106, I enabled compositing, brought the Enter and Leave opacity to 100, disabled Compositing, and restarted the panel and only then did this fix work for me."
1797417,2019-12-20 09:48:30 UTC,"@bpr95: Could you please try to reproduce with an empty, newly-created panel?"
1797417,2019-12-20 10:32:08 UTC,"Created attachment 9319
Exported panel config"
1797417,2019-12-20 10:34:33 UTC,"(In reply to bpr_95 from comment #47)

> Created attachment 9319 [details]
> Exported panel config
"
1797417,2020-01-10 17:44:42 UTC,"Confirming.
Affected icons of: Golden dict, claws-mail, KDE Connect, Pidgin, Pasystray, EasyStroke.
So, that's all kde applicatons or applications which icon can show any status information. Can attach screenshot (if it can help somehow and if someone can explain me how to do it here) or resend it somethere or try to gather some information to debug.
Fedora 30, xmonad, nvidia composition pipeline (without transparenty), xfce4-panel version 4.14.1."
1797417,2020-01-10 22:48:14 UTC,Simon Steinbeiss referenced this bugreport in commit 536272e869ea5472a319a7368009f3b4f4051095
1797417,2020-01-10 22:48:48 UTC,Simon Steinbeiss referenced this bugreport in commit f6e855143571530b452ae40bc3b01a4fcb82256d
1797417,2020-01-10 22:50:03 UTC,"@bpr_95: Thanks for the instructions, I was able to reproduce and fix the bug."
1797417,2020-04-05 07:18:47 UTC,This is still a problem on Xubuntu 19.10 with xfce4-panel 4.14.1-0ubuntu1.?????
1797417,2020-04-07 23:54:20 UTC,Fixed in xfce4-panel 4.14.2. Focal is currently shipping 4.14.3.
1797417,2019-08-27 23:21:02 UTC,"Please don't take this personally but ""it affects me too"" comments aren't helpful anymore at this point."
1797417,2019-08-27 17:07:54 UTC,Also experiencing this bug on Arch Linux with xfce4-panel 4.14.0-1 and gtk3 1:3.24.10-1.
1797417,2019-09-23 22:10:36 UTC,Ivan A. Melnikov referenced this bugreport in commit f6f70cce417fd2982c2ce6f01016ed01deb6a9ae
1797417,2019-08-14 14:54:41 UTC,*** Bug 15821 has been marked as a duplicate of this bug. ***
1797417,2018-08-03 21:19:26 UTC,"Created attachment 7858
Screenshot"
1797417,2018-08-07 01:47:07 UTC,"I'm almost certain it's a dup of Bug 14438, but let's keep this open for now, I would like to be sure that people working on panel (Simon, Sean?) are aware of your analysis."
1797417,2018-09-24 18:09:46 UTC,Found interesting GNOME stories:
1797417,2018-10-09 19:33:19 UTC,I would like to confirm downgrading to gtk3-3.22 and the icon problem isn't present. Tested on a few workstations that have had this problem since the gtk3 package update on ArchLinux.
1797417,2018-10-11 16:54:09 UTC,Does this happen regardless of having compositing enabled or disabled?
1797417,2018-10-11 17:08:46 UTC,"Compositing was disabled. When I enabled it, the problem was fixed instantly. I have not seen any more signs of the problem with compositing enabled. Thank you."
1797417,2018-10-11 17:37:56 UTC,"My main computer with GeForce 8600 GT and driver 340.107-0ubuntu2 had Compton compositor running via Application Autostart in Session and Startup. Disabling that, logging out and logging back in brings up some corruption there as well."
1797417,2018-10-11 20:24:12 UTC,This issue has been reported upstream also:
1797417,2018-10-17 20:34:35 UTC,"@Andreas: Your analysis seems sound, but to be honest this seems to be an issue within Gtk+3, I'm not sure how we can properly work around this in the panel reliably and without introducing ugly hacks."
1797417,2018-10-17 20:35:26 UTC,*** Bug 14438 has been marked as a duplicate of this bug. ***
1797417,2018-10-17 21:02:38 UTC,*** Bug 14397 has been marked as a duplicate of this bug. ***
1797417,2018-12-12 15:02:52 UTC,"Should be fixed in GTK+ 3 (gtk-3-24 branch, will be in 3.24.2) and in Arch with gtk3-3.24.1+155+g4c8fcd6a6f-1."
1797417,2018-12-13 00:47:24 UTC,Just to note that the above fix caused serious breakage in some applications when using a compositor. [1] I reverted it in Arch for now. :\
1797417,2019-08-18 16:15:20 UTC,"I'm also experiencing this issue on Arch Linux with xfce4-panel 4.14.0-1 and gtk3 1:3.24.10-1. I'm able to fix the issue by enabling compositing, which I prefer to have switched off. I've uploaded screenshots here: https://imgur.com/a/5KvhHA3"
1797417,2018-12-13 20:54:42 UTC,"@Evangelos: Is this one related? https://bugzilla.xfce.org/show_bug.cgi?id=14186
(Note that compositing is enabled there)"
1797417,2018-12-13 22:19:16 UTC,Bug 14936 is almost certainly a duplicate of this one.
1797417,2019-08-12 14:30:30 UTC,"I noticed this issue resurfaced again after updating gtk3 and xfce4 on ArchLinux. Enabling compositing and it goes away immediately. Turn it off and redrawing of icons turns into a strange mixture / mess of icons. Initially, all icons in the notification area had black background, regardless of theme setting."
1797417,2019-07-06 18:58:08 UTC,"(In reply to Denis Dupeyron from comment #19)

> Anyway, I would have agreed with you about the issue being limited to
> nm-applet, until I found out that after a few back-and-forth of the
> compositing on/off setting I could make all the other icons in my panel go
> dark background and messed up. So, if all you see is a messed up nm-applet
> icon I want to say: try harder ;-)


I didn't mean ""this is a nm-applet bug"", I meant that this is still an issue that I can reproduce with nm-applet."
1797417,2019-07-05 00:11:59 UTC,"(In reply to Andre Miranda from comment #16)

> Created attachment 8663 [details]
> screenshot
>
> gtk3.24.8+177+gae2ef1472c-1 here on Arch, only network-manager-applet is
> weird when compositing is disabled.
"
1797417,2019-06-22 12:17:35 UTC,Although I'll try to stay with compositing enabled and all settings off. Probably that won't stress much or at all this old hardware (pentium e2160 and via s3 graphics) and could be the solution if this takes time to be fixed.
1797417,2019-06-22 12:11:25 UTC,"I just installed gtk3.24.9 in fedora but the issues remains.
No matter which apps, the issues aren't consistent but it's either a black background or redraw issues (either the icon moved to the side for a new one or by changing icon themes and the old icon still partially visible underneath) or both.
Compositing disabled, but that's a basic feature as compositing do take a toll on old hardware."
1797417,2018-12-13 20:55:05 UTC,And this one seems to be a duplicate too... https://bugzilla.xfce.org/show_bug.cgi?id=14936
1797417,2019-06-22 11:08:28 UTC,"Created attachment 8663
screenshot"
1797417,2019-05-19 09:22:52 UTC,Ditto on upgrade to 19.04 from 18.10.  Same issue....
1797417,2019-04-20 07:53:14 UTC,I just upgraded to 19.04 (Disco) and still see this behaviour (black background to system tray icons in XFCE).
1797417,2019-01-16 13:54:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797417,2018-12-21 01:18:35 UTC,"(In reply to Denis Dupeyron from comment #13)

> TL;DR Downgrading to gtk+ 3.22 doesn't fix this issue for me.
>
> I just had time to try downgrading gtk+ to test if this was fixing this
> issue here. I first downgraded gtk+ to 3.22.30, then to 3.22.19 (the oldest
> gtk+ 3 in Gentoo), then tried rebuilding all core XFCE packages against gtk+
> 3.22.19, rebooted every time I tested, and none of that fixed it. Am I
> missing something?
"
1797417,2018-12-21 00:15:48 UTC,TL;DR Downgrading to gtk+ 3.22 doesn't fix this issue for me.
1797417,2018-12-13 22:58:32 UTC,*** Bug 14936 has been marked as a duplicate of this bug. ***
1797417,2019-06-22 09:45:20 UTC,i'm on gtk3-3.24.8-1.fc30.x86_6 on fedora and still the distorted images.
1797418,2019-10-04 18:20:49 UTC,We have been unable to reproduce this bug under testing in 3.2 and 3.3 (with the caveat that it is a hard one to test) - have any of the earlier reporters of this bug had it occur in 3.2 or later?
1797418,2019-01-16 17:59:27 UTC,"CWNARS also has this in 3.0.13. It is not in every template and doesn't happen every time or it would be more noticeable. Although, I have one cataloger that had it in every template that moved from xul to the web client and in several new templates created in the web client. That cataloger has deleted and made a new template for periodicals items 4 times. We wonder if there's a caching issue with that field."
1797418,2019-03-19 14:00:01 UTC,SCLENDS has signed a contract with Equinox to address this bug.
1797418,2019-01-16 17:12:25 UTC,Elaine or Lynn -- in which version(s) of EG do you see this bug?
1797418,2019-01-16 17:48:52 UTC,3.0.2 for me. We will be migrating to 3.2 this weekend
1797426,2020-03-19 08:46:50 UTC,"Closing because ""Not a bug, works as intended""."
1797435,2018-10-11 17:33:48 UTC,"Application: kicad
Version: 5.0.1-unknown-7573c6a~66~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-36-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011"
1797435,2018-10-12 13:00:37 UTC,"Does the Preferences->Reset to Default Settings menu entry not reset the color to their defaults?  This is in 5.0.0.  If not, there are two separate bug reports.  One is a bug because reset defaults should restore the default colors.  The other is a wish list for color saving which would be this bug report."
1797435,2018-10-12 13:21:05 UTC,"I didn't know about that. I guess that this seetings should come near the
entry to change the board colors."
1797435,2019-11-10 16:19:20 UTC,"In v6 there is now the ability to specify the silkscreen and soldermask colors inside the board stackup manager, so ideally we should auto populate the 3D color settings using that information and allow the user to override it if desired (see duplicate report lp:1851990 pointing this out)."
1797435,2018-10-12 14:06:52 UTC,This resets all of the 3D viewer settings not just the colors so it seems it is in the correct place to me.
1797441,2019-09-24 17:42:41 UTC,"Bug 1845238 may help with this -- it adds a link from holds to the hold copy map, which appears to be required to implement your SQL query via the reporter."
1797441,2019-09-25 13:22:55 UTC,"Thanks, Jeff, I'll take a look at your branch."
1797445,2018-10-14 06:57:06 UTC,"I don't know what exactly ""python_d.exe"" is. Does it just contain additional debug symbols or is it a dedicated debug build of CPython, with all the additional debug checks? If the latter, then you also need a corresponding build of lxml for it. We don't provide that on PyPI, because as this ticket seems to suggest, it would almost never be used."
1797445,2018-10-16 12:33:57 UTC,"Yes it is the latter, python_d is a debug build of Python.
We use it extensively when debugging across language boundaries (e.g.
python bindings around C++ code) in which case we have to match ABI between
the two builds.
We had a similar issue with Numpy which has since been resolved:
https://github.com/numpy/numpy/issues/11508"
1797445,2018-10-16 18:34:36 UTC,lxml's wheel names on PyPI are completely qualified. How do you install lxml in the two interpreters?
1797445,2019-07-27 18:03:56 UTC,"This should be resolved in Py3.8, which allows to import normally built extension modules in debug builds."
1797446,2018-10-12 00:20:18 UTC,"I think we can split apart the bits in KSM to have ""process environment"" and ""get environment data"". If we do this split, keystone can use the ""process environment"" code and supply the environment directly from flask.request.environ instead of assuming the data will come from a webob request object. This means that keystone benefits from all the work KSM does, but can push AuthContext down to a simple ""pre-request"" function that populates the sane bits of the environment used further down the stack."
1797446,2018-10-12 00:27:30 UTC,Hmm. The more I look at it the more I think the change can be super small:
1797446,2018-10-12 00:06:02 UTC,"Keystone shouldn't need to import webob is the point. Keystone should be able to say ""hey, get a token like X and validate a token like Y"" and that's it. There should be no ""import this thing, subclass it and lean on webob to make my subclassing work""."
1797446,2018-10-11 22:29:25 UTC,"I understand the wishlish nature of this, so just a comment."
1797448,2019-09-18 13:49:12 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/682900"
1797448,2019-09-18 13:54:54 UTC,(note copied from review)
1797448,2019-09-18 13:55:38 UTC,At least iSCSI works out-of-the-box.
1797448,2019-09-19 22:09:57 UTC,"Reviewed:  https://review.opendev.org/682437
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=ed29cb61b808187288479a050053ca8604b9a123
Submitter: Zuul
Branch:    master"
1797448,2020-01-30 10:22:27 UTC,This issue was fixed in the openstack/kolla-ansible 7.2.0 release.
1797448,2019-10-16 14:41:15 UTC,Looks like this one is fixed now?
1797448,2019-10-16 15:30:25 UTC,I will handle this.
1797448,2019-10-20 16:39:39 UTC,"iSCSI refactored to:
https://bugs.launchpad.net/kolla-ansible/+bug/1848933"
1797448,2019-10-20 16:56:41 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/689654"
1797448,2019-10-21 11:06:18 UTC,"Reviewed:  https://review.opendev.org/689654
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=832791e6017167cee79631e026d07511a77d5dc0
Submitter: Zuul
Branch:    stable/rocky"
1797448,2019-10-22 12:56:54 UTC,"Reviewed:  https://review.opendev.org/682900
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=2447c161b8887e130ff2586dee2413c2850572a6
Submitter: Zuul
Branch:    master"
1797448,2019-10-23 15:45:45 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/690614"
1797448,2019-10-24 08:42:26 UTC,"Reviewed:  https://review.opendev.org/690614
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=01135e0f4d330c3bb7829fb1f1ccfee00fa0a973
Submitter: Zuul
Branch:    master"
1797448,2020-01-19 03:09:24 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/703274"
1797448,2019-10-20 16:48:21 UTC,kolla patches (missing pciutils): https://review.opendev.org/#/q/Iebc1f2c05c1f57c2b6f98ca9772f1ae9d9a420fa
1797448,2019-09-17 08:55:18 UTC,"Reviewed:  https://review.opendev.org/682436
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=8b6a7845f331a39e6eaef899b0d2a3ccc7336379
Submitter: Zuul
Branch:    stable/rocky"
1797448,2019-09-16 17:22:08 UTC,"Zun reports ""ceph-common package is not installed"" when using ceph volumes - bug triaged."
1797448,2019-09-16 17:37:50 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/682437"
1797448,2019-09-16 19:22:07 UTC,after ceph-common in zun-compute:
1797448,2018-10-13 08:54:52 UTC,"I got now zun-compute quite good running, but it needs following adjustments in kolla:
Packages in the container:
pciutils
ceph-common"
1797448,2018-10-13 08:55:20 UTC,Info: I will add the kolla-ansible fixes later.
1797448,2018-10-13 08:57:40 UTC,Release with the issues is: rocky
1797448,2018-10-13 09:10:56 UTC,"With this changes I got zun up and running under kolla-rocky. Only thing I'm a bit disappointed is the zun-ui. It covers everything, but the information presentation is quite bad compared to nova."
1797448,2018-10-13 22:01:50 UTC,"@Andreas,"
1797448,2018-10-13 09:06:38 UTC,"kolla-ansible missing things (not all have solution yet):
We require a similar configuration like nova-compute. Please add following lines in ""ansible/roles/zun/defaults/main.yml"":
zun_services:
  zun-compute:
    volumes:
      - ""/lib/modules:/lib/modules:ro""
      - ""/dev:/dev""
      - ""{% if enable_iscsid | bool %}iscsi_info:/etc/iscsi{% endif %}""
Last line is not tested yet. But could be required if another storage than ceph is used.
Further we need in the container under /etc/ceph:
ceph.conf
ceph.client.cinder.keyring"
1797448,2018-11-09 01:42:51 UTC,"Made a typo above, replace:
       - ""/var/lib/zun:/var/lib/zun:rw""
By:
       - ""/var/lib/zun:/var/lib/zun:shared"""
1797448,2019-09-12 14:11:46 UTC,"zun-compute now contains pciutils, but not ceph-common."
1797448,2019-09-15 18:52:00 UTC,"there seem to be multiple issues reported in this bug report, need to test storage in zun for sure then; adding myself to the bug loop"
1797448,2019-09-16 17:29:53 UTC,Backported pciutils addition to Rocky for completeness.
1797448,2019-09-16 17:29:57 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/682436"
1797448,2019-09-16 17:30:25 UTC,https://review.opendev.org/682436
1797448,2018-11-09 00:53:38 UTC,"Just a quick addition, /var/lib/zun needs to be created on the host and mounted inside zun_compute container."
1797449,2018-10-12 18:45:05 UTC,"I'm not sure why there is a unicode double quote in report files instead of an ascii double quote but report files are for humans to read which entails different languages so ascii is not adequate.  Board, schematic, project, etc. files on the other hand are for computers to read so they always have to be in the same other than embedded strings which are utf8 encoded."
1797449,2019-11-13 23:15:25 UTC,"Yes, I'm running 5.1.4 and I still see UTF-8 characters used for double quotes."
1797449,2019-11-11 13:24:18 UTC,Does this still affect the 5.1.x packages?
1797449,2018-10-15 17:12:25 UTC,"After doing some digging around, I found that this only effects the 5.0.0 package.  My development builds (including the 5.0 branch) create files with ascii double quote characters.  It looks as though the problem has to do with how our package builders are building KiCad.  Any ideas?  I'm going to leave the double quotes until we understand why there is a difference here."
1797449,2018-10-15 14:00:11 UTC,I'm fine with going to single quotes if that resolves the issue.  What I don't understand is why double quotes would not be output as ascii unless it has something to do with escaped characters in strings.  I'll go ahead and make the change but technically it will still not make the report file ascii.  Hopefully devs will see this and avoid using escaped characters in report output strings in the future.
1797449,2018-10-12 21:11:57 UTC,"Hi Wayne, probably because they're exported from a HTML view (WX_HTML_REPORT_PANEL). I also agree that these files are intended to be human-readable, not necessarily machine-readable. We might also remove the quotes from these report files, I don't believe they are absolutely necessary around component designators/values in the report file."
1797449,2018-10-12 18:04:01 UTC,"Thanks for the explanation, it finally prompted me to actually get Vim working with unicode (set encoding=utf-8).  However, it's the inconsistency that I don't understand.  Looking at the other files Kicad produces (schematic, layout, project) they all use only ASCII characters, even for the quotation mark (22), which I've verified with a hex editor.  If I had the same problem with every other Kicad file, I would have figured it out before now, but since report.txt is the only file I've had this problem with, that's why I opened the bug report.  And according to Fabian, the Linux version uses ASCII for the quotation mark.  I don't know what makes this file special on Windows that it is treated differently."
1797449,2018-10-12 06:30:59 UTC,"Kicad uses Unicode.
But a text file is not necessary a ASCII7 text file. It is just not a binary file."
1797449,2018-10-11 23:48:04 UTC,"If the report messages are translated, ascii would cause a loss of information in translated report files."
1797449,2018-10-11 23:12:26 UTC,"Sorry, I should have said that I'm using Kicad 5.0 on Windows."
1797449,2018-10-11 22:39:40 UTC,"The file Robert attached doesn't use the ASCII quotation mark (checked using an hex editor) but I'm still able to read it using geany, gedit, nano, micro and vi."
1797449,2018-10-11 21:13:04 UTC,It most definitely is not completely readable with Vim and other text editors.
1797449,2018-10-11 20:36:21 UTC,I don't see the problem
1797449,2018-10-11 20:17:53 UTC,"When the log window is open, none of the other Kicad windows work, so to fix the errors listed, I have to close the window, in which case I can't see the list of errors.  So the first thing I do is save the file and open it so that I can fix schematic errors.  Also, I find myself swapping pins in the layout often, and to sync up the schematic and layout, I have to open the report.txt file.  Because that file has everything listed in it instead of just the mismatches, I have to search for pin changes, and readability makes this easier.  I can't recall exactly the problem I had, but I was doing some copying and pasting."
1797449,2018-10-11 20:01:26 UTC,Please add version information.
1797449,2018-10-12 00:09:56 UTC,"I'm not familiar with unicode nor translating files, so I don't understand why making this text file at least partly incompatible with text editors is worth it.  I would think that translating ascii is something that can be done.  I'm not 100% sure why the schematic and pcb files are also not held to the same standard.  Shouldn't they also move to unicode then (not that I actually want that)?  And finally, the Linux version appears to use ascii, so the differing standards also seems strange."
1797454,2018-10-11 20:25:15 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f373b3b4c00 ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f373b3b6490 ""malloc_consolidate(): invalid chunk size"") at malloc.c:5336
 malloc_consolidate (av=av@entry=0x7f373b3ebc40 <main_arena>) at malloc.c:4427
 _int_malloc (av=av@entry=0x7f373b3ebc40 <main_arena>, bytes=bytes@entry=2048) at malloc.c:3687
 __libc_calloc (n=n@entry=1, elem_size=elem_size@entry=2048) at malloc.c:3420"
1797460,2020-08-30 05:36:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1797460,2018-10-12 11:28:14 UTC,"A Minimal Working Example. In other words, could you please provide steps how to reproduce this bug?"
1797460,2018-10-12 09:28:47 UTC,what is MWE ?
1797460,2018-10-12 05:26:53 UTC,Could you please provide steps a MWE to reproduce this bug?
1797462,2019-05-10 18:59:12 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658453"
1797462,2019-06-14 21:44:21 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665479"
1797462,2019-06-14 21:48:15 UTC,"Change abandoned by Genevieve Nantel (<email address hidden>) on branch: master
Review: https://review.opendev.org/665479
Reason: duplicate review"
1797462,2019-07-12 01:47:38 UTC,"Reviewed:  https://review.opendev.org/658453
Committed: https://git.openstack.org/cgit/openstack/karbor/commit/?id=e96ec2726caabef7d6e1b064f8dcc2cb0c00d938
Submitter: Zuul
Branch:    master"
1797462,2019-09-15 19:06:32 UTC,This issue was fixed in the openstack/karbor 1.4.0 release.
1797472,2019-03-14 00:55:20 UTC,"This may also differ between the Backpack, the Open Badge Passport and Badgr. All three need to be looked at."
1797482,2019-01-14 13:29:22 UTC,I am not so sure this would be so clear cut. How would you for example handle generic symbols like a resistor where the value is different than the value once placed? This would definetly need some thought.
1797482,2019-04-11 18:13:08 UTC,When changing a reference if the value equalled the old reference then it should be updated to the new reference.  Otherwise it should be left.
1797482,2019-08-15 16:02:22 UTC,"Fixed in revision a6b36adb32cc1da2e2a0e4e3b4ef30e31e59ad32
https://git.launchpad.net/kicad/patch/?id=a6b36adb32cc1da2e2a0e4e3b4ef30e31e59ad32"
1797487,2019-12-13 17:58:35 UTC,The workaround doesn't seem to work for me with the 0.92.4 Snap:
1797487,2020-04-26 19:12:38 UTC,"The solution also doesn't work for me with Ubuntu 19.10, Inkacape 0.92.4 and snap snap    2.44.3:"
1797487,2018-12-15 17:52:11 UTC,"Not reproduced at my end, after connecting the `cups-control` security confinement interface the printers should appear in the printing dialog."
1797487,2018-10-15 17:58:11 UTC,"The problem is only in the snap program,  It is in Ubuntu 18.04.01 the
printer It is a Epson l200"
1797487,2018-10-15 17:41:24 UTC,"Sorry, but we'll need a lot more information than that (e.g. OS, installed printers, printers visible in Inkscape print dialog - potentially backed by screenshots, etc.)."
1797487,2018-10-16 17:57:51 UTC,"OK, thanks."
1797489,2018-10-29 14:59:36 UTC,This is tricky because:
1797492,2018-10-12 10:55:50 UTC,apport information
1797492,2018-10-12 10:55:54 UTC,apport information
1797492,2018-10-12 10:55:53 UTC,apport information
1797492,2018-10-12 10:55:51 UTC,apport information
1797492,2018-10-12 10:55:49 UTC,apport information
1797492,2018-10-12 10:55:47 UTC,apport information
1797492,2018-10-12 10:55:45 UTC,apport information
1797492,2018-10-12 10:55:44 UTC,apport information
1797492,2018-10-12 10:55:43 UTC,apport information
1797492,2018-10-12 10:55:42 UTC,apport information
1797492,2018-10-12 10:55:41 UTC,apport information
1797492,2018-10-12 10:55:39 UTC,apport information
1797492,2018-10-12 10:55:38 UTC,apport information
1797492,2018-10-12 01:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797492,2018-10-12 10:55:55 UTC,apport information
1797492,2018-10-12 14:59:16 UTC,The commit in the description is the the Cosmic Ubuntu-4.18.0-9 kernel.
1797498,2018-10-12 02:39:41 UTC,/var/cache/apt/archives/libumfpack5_1%3a5.1.2-2_i386.deb
1797501,2019-04-16 16:09:54 UTC,"To reduce the amount of typing for me, I will reference Message #5 at"
1797501,2019-04-09 23:22:34 UTC,Regarding the M281fdw LaserJet:
1797501,2019-02-18 20:10:36 UTC,A new entry for the Hall of Fame:
1797501,2019-03-28 19:19:25 UTC,Losing track: have we had the HP LaserJet Pro MFP M28-M31?
1797501,2019-02-20 15:10:52 UTC,There is a patch at
1797501,2019-02-19 20:30:03 UTC,"Let's start with Jeremy Kerr's first message in this report. I have no understanding of python but, from observation and a bit of testing, it has all the hallmarks of being a correct analysis. And then there are quite a number of bug reports that appear to arise from the change in mdns.c which occured in HPLIP 3.17.10."
1797501,2020-06-30 22:06:28 UTC,io/hpmud/model.c 532: no tosmart_prem_c410_series attributes found in /usr/share/hplip/data/models/models.dat
1797501,2019-02-03 19:02:23 UTC,Almost certainly another one. An HP Laserjet PRO MFP M280nw. See
1797501,2018-10-15 11:14:28 UTC,"Hi Jeremy,"
1797501,2018-11-12 23:46:33 UTC,Three more affected devices apparently. Two Officejets and a Deskjet:
1797501,2018-11-08 14:10:21 UTC,I can now reproduce the behaviour described in Jeremy's first post.
1797501,2018-10-30 00:46:13 UTC,"Hi Brian,"
1797501,2018-10-29 16:40:31 UTC,"Hi Jeremy,"
1797501,2018-10-22 10:41:47 UTC,"Hi Brian,"
1797501,2018-10-14 11:05:24 UTC,"Hi Brian,"
1797501,2018-10-12 18:19:40 UTC,Why is my ENVY4500 not affected by this?
1797501,2018-11-25 23:37:22 UTC,Another affected device:
1797505,2020-06-04 08:08:11 UTC,"Just adding the missing DLL files did not help on my Server 2012 R2 machine but installing the ""Media Foundation"" Package from the server control panel did the job. Thanks everyone!"
1797505,2019-03-20 21:36:50 UTC,Also with Java 8 64-bit....build 202
1797505,2019-04-05 15:11:13 UTC,Another update:
1797505,2019-03-20 21:35:04 UTC,"Update to say that I reinstalled Windows RedStone 4 (fresh Windows, but didn't format the drive).  The issue still persisted - so it wasn't the Red Stone update to blame."
1797505,2020-03-13 08:38:55 UTC,"I was having the same problem on my machine -
Sikulix - 1.1.4
Windows 10 Enterprise  N LTSC"
1797505,2020-04-23 23:50:21 UTC,"Hello, to solve this problem in Windows you only have to go to the path:"
1797505,2020-02-13 11:33:43 UTC,I had this problem on Windows Server 2012 R2 and solved it by installing Desktop Experience from Control Panel.
1797505,2019-03-19 23:43:16 UTC,"Oh, I forgot to mention, I am using Sikuli SNAPSHOT from 2019-03-15."
1797505,2019-04-04 19:59:57 UTC,"Same problem: Windows 10 Pro N version 1809, OS build 17763.379 (64 bit)
Fresh install, only the java jdk 11 and chrome installed and same error:"
1797505,2019-01-08 10:14:45 UTC,"Installing the win update KB2670838 solved this issue for me, found here: https://www.microsoft.com/en-nz/download/details.aspx?id=36805"
1797505,2018-10-12 15:43:15 UTC,"I guess, there is some ""Visual C++ Redistributable …"" missing on your system."
1797505,2018-10-14 03:42:38 UTC,I am seeing this issue on Windows Server 2012 and Windows 7. I have Redistributable 2017 installed on both machines as well as the latest JRE.
1797505,2018-10-16 13:15:08 UTC,"I tested with a Windows 7 64Bit Service Pack 1 with latest updates but nothing else (no Net Framework, no Redistributable or other packages):
It works."
1797505,2019-03-19 23:41:00 UTC,"I am adding a comment because I have the same issue on one of my test Win10 machines.  I tried the solutions here and found elsewhere on the web, but nothing has helped so far."
1797505,2018-10-17 17:50:55 UTC,As mentioned in comment #3: IMHO a Redistributable seems not to be needed
1797505,2018-11-18 13:39:17 UTC,"I solved this issue copying the (missing) file ""api-ms-win-downlevel-shlwapi-l1-1-0.dll"" from another computer where sikulix was working"
1797505,2018-10-17 15:20:42 UTC,"I have this issue on windows 7 with latest JRE and Redistributable 2017 but without latest updates of windows (a lot of windows updates was missing in fact).
I updated window, tested it again and it work now."
1797512,2018-10-13 03:38:03 UTC,"Reviewed:  https://review.openstack.org/609832
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=a07c51e8b01074d8ee8bb936a31ad4c1654c4e73
Submitter: Zuul
Branch:    master"
1797512,2019-03-21 20:41:00 UTC,"since the job is non-voting, reviewers may take a call to ignore coverage failure"
1797516,2018-10-12 07:05:25 UTC,"The bug is concerning, at least, all 3.18 HPLIP version"
1797517,2020-06-30 08:21:12 UTC,We recently added support for stopping and uninstalling the host chrony service when the chrony container is enabled.
1797517,2018-10-12 07:58:38 UTC,This definitely fixed the issue.  Clock skew was horribly bad (300ms+ from NTP) and now servers are within 0.1ms down to 0.01ms from NTP.
1797518,2018-10-24 03:33:53 UTC,"This morning was the next time.
Here the screenshot"
1797518,2018-10-26 18:32:03 UTC,done
1797518,2018-10-26 03:46:55 UTC,Please also change the bug description in the same way.
1797518,2018-11-14 17:36:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797518,2018-10-26 01:46:32 UTC,"Please change the bug title and description to cover just one problem, because it sounds like two unrelated issues at the moment."
1797518,2018-10-26 01:44:43 UTC,Oooh... that was the login screen's Xorg shutting down. So Xorg exiting was not an error:
1797518,2018-10-26 01:36:41 UTC,It seems everything started to fail after resume because the X server went away:
1797518,2018-10-25 16:15:12 UTC,here the file
1797518,2018-10-25 04:09:23 UTC,Thanks.
1797518,2018-10-25 03:51:59 UTC,"On the first wake up, the system was hanging. Worse then before with the nvidia driver, see screenshopt for options.
Should I go back to the nuveau driver?"
1797518,2018-10-24 17:16:23 UTC,"I did not have ""Proprietary drivers for devices (restricted)"" checked.
After that I was able to install the nvidia-driver-390
I rebooted
If the hang happens again, I will report it."
1797518,2018-10-24 04:51:51 UTC,"It appears that either your mirror.switch.ch server is missing the required files, or you don't have the required channel enabled."
1797518,2018-10-26 03:38:33 UTC,"My main issue is ""on resume from suspend"" which I never had with 16.04. I probably had 30-50 resumes before I rebooted after a kernel update.
In the mean time I am on 4.15.0-38.
I assume I removed the gnome-shell, also I switched from nouveau to nvidia-driver-390
I had several (5) resumes after my last reboot and no issue yet. It does not happen all the time.
I did change the subject as suggested."
1797518,2018-10-18 15:25:20 UTC,"Yes it does.
Today is the 10-18 and it froze again. About 5-10 Standby's.
When I installed 18.04, it mentioned something about the nouveau driver.
But everything worked. This freezing is very recent, so I would think it has to do with one of the recent kernel version, maybe the 4.15.0-36 ?"
1797518,2018-10-17 05:07:43 UTC,"Good. Now the extensions are disabled, reboot and retest. Does the problem reoccur?"
1797518,2018-10-22 02:21:18 UTC,"Next please try installing the nvidia driver, using these commands:"
1797518,2018-10-12 07:55:24 UTC,"Also, next time the problem happens and you need to reboot, please collect the log of the previous boot where the bug occurred:"
1797518,2018-10-12 12:03:24 UTC,"Here the crash files, they are not uploading via ubuntu-bug"
1797518,2018-10-12 12:14:10 UTC,"Since 1. failed
2:
https://errors.ubuntu.com/user/230b4c65c3987a78cc956c8f58273b870218dcc359f8b69389d8186574ccdf290a72652c83f6032d2bb69a8b8a42cb904555b3bd931d85829dccb84aec250996"
1797518,2018-10-15 02:23:55 UTC,Thanks. I have opened bug 1797820 for your most recent desktop crash. But that's likely not the freeze we're talking about here.
1797518,2018-10-12 07:53:39 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1797518,2018-10-17 04:05:05 UTC,"Next freeze happened.
I woke system up, logged in and started Thunderbird. Thunderbird was not open yet but froze. Funny thing is that it seemed to ru in the background, because when I get a new msg, it will play a wave file and it played it."
1797518,2018-10-17 04:14:19 UTC,1. Gnome shell extensions need to be disabled from the Gnome Tweaks app.
1797518,2018-10-17 04:32:54 UTC,"In the tweak app there is nothing under shell, see screenshot (its grayed out)"
1797518,2018-10-17 04:59:53 UTC,"I think you meant disable all gnome-shell extensions. I think I did now
see screenshot"
1797518,2018-10-17 05:00:08 UTC,"Click on ""Extensions"" in the Gnome Tweaks app."
1797518,2018-10-15 04:06:09 UTC,"to 1)
sudo apt-get remove --auto-remove snapd"
1797525,2018-10-17 13:21:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/611312"
1797525,2018-10-17 14:18:41 UTC,"So that we have now and for future work (to optimize long running ps calls, like caching):"
1797525,2018-10-19 16:06:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/611911"
1797525,2018-10-25 13:03:35 UTC,The related fixes for bug 1799902 should also help with debugging of the original issues
1797525,2018-10-25 16:05:23 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/611911
Reason: The podman performance seems addressed for the podman 0.10.2-dev so we can let this poor thing go now"
1797525,2018-10-25 16:04:47 UTC,The podman performance seems addressed for the podman 0.10.2-dev
1797525,2018-10-30 15:26:49 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/611312
Reason: it fails my local testing see https://pastebin.com/eYKhKwYA"
1797525,2018-11-02 17:05:22 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/609963
Reason: https://review.openstack.org/#/c/614537/"
1797525,2018-11-05 09:51:25 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/609941"
1797525,2018-10-25 13:04:54 UTC,"A 'podman ps' caching (WIP) patch https://review.openstack.org/611911 addresses some of the proposals listed in https://bugs.launchpad.net/tripleo/+bug/1797525/comments/14 as well, but it's not there yet!"
1797525,2018-10-17 08:52:58 UTC,"As benchmarking shows (see https://github.com/containers/libpod/issues/1656) ``podman ps`` is a bottleneck as it locks for seconds/tens of seconds, while containers being operated in a concurrent fashion. And paunch does rely a lot on the ps results. Perhaps, to speed up things we should avoid using ps as much as possible, for podman, and instead just use try/except with retries or something."
1797525,2018-10-16 08:45:09 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/609963
Reason: This does not make the tripleo-ci-centos-7-undercloud-containers job timing out, so no need to revert it"
1797525,2018-10-16 08:28:36 UTC,"Given that we see no timeouts for all jobs cuz of these podman and remaining skopeo layers issues, that probably allows us to reduce the priority to high. When we're back to switch all jobs to podman, let's re-iterate if that still blocks us."
1797525,2018-10-12 08:28:08 UTC,"Note, that issue also seems like a major show stopper for other multi node CI jobs now hitting timeouts for mistral workflows and more places (see also https://bugs.launchpad.net/tripleo/+bug/1789680 )"
1797525,2018-10-12 08:32:09 UTC,"Small thing regarding skopeo: it will be more than probably dropped due to several bugs we had, especially when running skopeo from within mistral containers.
The following patch drop skopeo, and re-implement its basic functions in plain python:
https://review.openstack.org/609586"
1797525,2018-10-12 08:32:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/609963"
1797525,2018-10-12 08:36:19 UTC,The skopeo switch revert https://review.openstack.org/#/c/609941/
1797525,2018-10-16 16:33:04 UTC,The upstream podman issue with benchmarking results https://github.com/containers/libpod/issues/1656
1797525,2018-10-13 07:12:45 UTC,"Hi,"
1797525,2018-10-16 04:33:28 UTC,"BTW, the skopeo uploader has landed but is not yet used until https://review.openstack.org/#/c/590087/ has landed. It should not land yet because it will be really slow."
1797525,2018-10-16 08:23:28 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/609941
Reason: we have https://review.openstack.org/#/c/609586/ merged and hopefully need no more to revert"
1797525,2018-10-12 09:09:34 UTC,"seems no need to revert the skopeo switch, but an alternative fix https://review.openstack.org/#/c/609586/"
1797532,2018-10-12 09:03:30 UTC,This bug report is too general to be actionable on its own.  This comment is an attempt to make it actionable.
1797538,2018-12-22 04:22:06 UTC,apport information
1797538,2018-12-22 04:22:09 UTC,apport information
1797538,2018-12-22 04:22:10 UTC,apport information
1797538,2018-12-22 04:22:11 UTC,apport information
1797538,2018-12-22 04:22:13 UTC,apport information
1797538,2018-12-22 04:22:17 UTC,apport information
1797538,2018-12-22 04:22:15 UTC,apport information
1797538,2018-12-22 04:22:18 UTC,apport information
1797538,2018-12-22 04:22:20 UTC,apport information
1797538,2018-12-22 04:22:05 UTC,apport information
1797538,2018-12-22 04:22:25 UTC,apport information
1797538,2018-12-22 04:22:14 UTC,apport information
1797538,2018-12-22 04:22:22 UTC,apport information
1797538,2018-12-22 04:22:04 UTC,"ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  typer      2994 F.... pulseaudio
 /dev/snd/pcmC0D0p:   typer      2994 F...m pulseaudio
CurrentDesktop: LXQt
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-20 (2 days ago)
InstallationMedia: Lubuntu 18.10 ""Cosmic Cuttlefish"" - Release amd64 (20181017.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
 Bus 001 Device 002: ID 046d:c083 Logitech, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B360M-D3H
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=ba2e86e4-48ce-47f3-a413-98536fe6febd ro quiet splash resume=UUID=5b571422-2d63-4044-88be-ecd5e66732d8 vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-12-generic N/A
 linux-backports-modules-4.18.0-12-generic  N/A
 linux-firmware                             1.175.1
RfKill:"
1797538,2018-12-02 05:06:55 UTC,Still happening on 4.20.0-042000rc4 as well.
1797538,2018-12-22 04:15:33 UTC,"For me the issue is happening on ubuntu 16.04, 18.04 and 18.10 I also tried kernel 4.19, no success"
1797538,2018-10-12 10:00:06 UTC,This change was made by a bot.
1797538,2018-10-12 14:52:50 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1797538,2018-10-20 13:09:11 UTC,I have the same issue after upgrading it from 18.04.1 and also after a clean install. I can't do mutch with the computer because it is freezing after the login. The trackpad also freezes about 10s after the login.
1797538,2018-10-20 14:05:53 UTC,"Joseph, do you have any suggestion on how I can I apply the upstream kernel once the system freezes right after the login? Is it possible to apply it from the live USB?"
1797538,2018-10-12 20:28:40 UTC,This occurred right after I upgraded to 18.10 from 18.04.1.
1797538,2018-10-21 18:26:39 UTC,"@Joseph, I was able to install a new kernel. I didn't test the rc7 because I found a rc8 there."
1797538,2018-10-27 20:56:00 UTC,"Just to add a note, I the kernel I was using is 4.18.0-10."
1797538,2018-10-27 20:59:16 UTC,Tested and working with Kernel 0.19.0-041900rc8
1797538,2018-12-02 04:42:57 UTC,Still happening on 4.19.6-041906.
1797538,2018-10-20 14:06:58 UTC,I also could't see grub or the recover mode to test something from there.
1797540,2018-10-14 19:30:56 UTC,"Currently, the description field is a full text field where you can use formatting and also add images. This is due to historical reasons because before we had flexible page layouts, people used the description field to add a top banner to their page."
1797550,2018-12-05 12:43:18 UTC,"Version 18.04.1 LTS (Bionic Beaver) 64-bit
Kernel Linux 4.15.0-42-generic x86_64
MATE 1.20.1
Caja 1.20.2"
1797550,2019-03-25 17:49:50 UTC,"Bug (annoying) and still exists in Ubuntu MATE 18.10 / (same) Caja 1.20.2.
Can't confirm the previous statement

> On 16.04 it was still working properly.


Was already broken in 16.04"
1797550,2019-03-27 06:35:09 UTC,"Yes, bug annoying and still exists, but I keep confirming on my machine with 16.04 CAJA was behaving properly without that bug. Is a bit strange."
1797557,2019-03-08 03:43:26 UTC,How exactly do I fix this mess? My cross-build VM is basically fucked after upgrading to Bionic.
1797557,2019-03-12 15:46:56 UTC,The work around listed doesn't work and I'm completely unable to use apt in order to install packages.
1797557,2018-11-22 19:16:17 UTC,"to understand how annoying this has become,
when I try to install Synaptic Package Manager
error while installing package: unqble to open
'/usr/arm-linux-gnueabihf/lib/Mcrt1.odpkg-new"
1797557,2019-08-26 22:11:54 UTC,Ive had this same problem for awhile now and I still can't get this fixed nor can i install anything because the everything is broken over this. and kyle i tried yous here in a last hope and i get
1797557,2019-08-26 22:22:27 UTC,i'm considering backing up all my data and reinstalling ubuntu completely as this appears to be the last and only option
1797557,2019-04-11 16:56:13 UTC,"I had the exact same symptoms as sboylan above, and brute-force fixed this issue by running"
1797557,2018-11-22 17:49:51 UTC,"I would just like to remove, but have not found a way.
Please could you help?"
1797557,2018-10-15 11:00:34 UTC,"Iam also facing the same issue, My desktop got freezed after log-in. I went to recovery mode and tried to install all the dependencies I came across the same issue after upgrade to 18.04"
1797557,2018-10-18 15:02:41 UTC,I'm not sure I understand how people are supposed to deal with this situation. Are they supposed to uninstall libc6-armhf-cross before upgrading? How would they know to uninstall it?
1797557,2018-10-18 06:37:53 UTC,"""it has the potential to make quite a mess"""
1797557,2018-10-17 14:27:19 UTC,Removing the package causes a lot of churn even on a minimal cross-build install:
1797557,2018-10-16 06:59:07 UTC,"yes, and I'm unsure that I want to fix that.  You can work around that by uninstalling libc6-armhf-corss, and re-installing the armhf cross compilers. Is this a feasible option for such a development package?"
1797557,2018-10-19 09:24:37 UTC,"> I'm not sure I understand how people are supposed to deal
> with this situation. Are they supposed to uninstall
> libc6-armhf-cross before upgrading? How would they know
> to uninstall it?
"
1797557,2018-10-12 17:54:19 UTC,"I confirm this locally, the package is not upgradeable due to (I think) the switch of ./usr/arm-linux-gnueabi/libhf/ from a symlink to a directory not being managed correctly."
1797562,2018-11-11 20:04:47 UTC,This only seems to be an issue when building with the DEBUG flag is set.
1797562,2018-11-11 19:51:49 UTC,"Hi, Doesn't crash for me - but the asserts are only enabled during debug builds."
1797566,2019-10-28 04:17:28 UTC,[Expired for juju because there has been no activity for 60 days.]
1797566,2018-11-21 02:11:39 UTC,"note that we did see 10s queries on Prodstack yesterday. We don't know if
that was strictly due to load or some other contention. I'm hoping to have
some time today to play with the sanitized backup and see if there is
anything interesting in the data."
1797566,2018-10-18 12:02:57 UTC,Moved to field-high from field-critical.
1797566,2018-10-14 16:14:53 UTC,On the SSD RAID1 it takes about 30 seconds to destroy a model:
1797566,2018-10-14 16:02:29 UTC,Took a look at the environment again with John this morning:
1797566,2018-10-14 11:05:40 UTC,The qcow2 image for the juju VM is located at /srv/libvirt/storage/.
1797566,2018-10-14 10:09:19 UTC,"> I do see a lot more noise in query logs when doing a destroy-model than a deploy
"
1797566,2018-11-20 22:25:34 UTC,"Based on the underlying disk issues here, I'm marking it incomplete."
1797566,2018-10-14 08:47:08 UTC,juju debug-log --date --utc -m base1 --replay | zstd > debug-log-base1.zst
1797566,2018-10-14 08:45:18 UTC,openstack model logs (zstd)
1797566,2018-10-14 08:26:26 UTC,"The openstack model was redeployed several times, and openstack-base a couple of times."
1797566,2018-10-14 06:28:46 UTC,"To get some context, is this with 10 models running, or is this just that a model was deployed, destroyed, repeat and after 10 times of doing this it started to slow down?"
1797566,2018-10-13 16:27:24 UTC,"Looks to me like we are not doing sufficient performance analysis and correction, and probably not doing it as part of the landing test suites. We should not be making hundreds of writes to the database per second for a single bundle deployment."
1797566,2018-10-12 18:56:00 UTC,Marking as ~field-critical due to the fact that the core functionality was critically impacted and resulted in customer-facing implications.
1797566,2018-10-14 08:50:01 UTC,I do agree that we should be tracking it more closely. I do wonder if some of the overhead is related to destroying an earlier model. I do see a lot more noise in query logs when doing a destroy-model than a deploy.
1797568,2018-10-12 18:00:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1797570,2019-08-29 17:53:45 UTC,See also https://forum.kicad.info/t/pcbnew-how-to-set-user-grid-size/18725 (the user had problems finding the grid settings because there weren't in Preferences).
1797570,2019-05-15 12:28:53 UTC,"@Michael, your latest patch does not apply cleanly.  It looks like there were some changes in eeschema/menubar.cpp that conflict with your patch.  Please rebase and resubmit it when you get a chance.  There are few minor coding policy[1] errors.  Most of them are exceeding the 100 character line limit.  Also, please follow the commit message policy[2] maximum character limit of 72."
1797570,2019-05-10 13:07:34 UTC,Well this grew bigger than expected... Updated patch attached for review.
1797570,2019-05-02 13:03:37 UTC,"@Michael, you probably should coordinate with Jeff to prevent merge conflicts."
1797570,2019-05-02 12:37:29 UTC,"@Wayne, thanks for reviewing this. I will rebase it, but should I wait until the eemodern branch (or anything else) is merged to avoid duplicating effort again?"
1797570,2019-05-02 12:23:00 UTC,"@Michael, I finally got around to taking a look at your patch and it no longer applies due to Jeff's grid refactor work.  I'm fine with your concept and agree with your rationalization for moving the grid settings out of the view menu.  If you are still interest in getting this merged, please rebase your patch and I will take a look at it.  If not, then we should close out this bug report."
1797570,2019-01-28 09:56:38 UTC,"I'm already used to Grid Settings being in the View menu, but it still feels like out of place there. Logically grid settings are more than just viewing, they actually affect behavior and board editing, unlike all (most?) other items in the View menu."
1797570,2018-11-07 14:35:26 UTC,"I had some spare time so I took a look at this, and hacked together a proof of concept patch set."
1797570,2018-10-13 16:48:12 UTC,"Upon further investigation I see that for Pcbnew and Modedit the User Defined Grid and Fast Switching grids are stored in the pcbnew settings file, so I believe these should go in the app preferences."
1797570,2018-10-12 14:21:15 UTC,"Also a useful feature would be to have different grids for placement, routing, drawing polygons etc. that are set up and stored in the Board Setup dialog."
1797570,2019-03-12 22:53:42 UTC,"I've rebased and updated the patch a bit for review. I have tested it on macOS. I ran it through the clang-format so hopefully that'll have picked up style errors, but it seems the wxFormBuilder files aren't compliant."
1797580,2018-11-08 17:07:32 UTC,"Reviewed:  https://review.openstack.org/611938
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cb9c96f0a8287a3261432c75f9178275780cec38
Submitter: Zuul
Branch:    stable/rocky"
1797580,2019-03-24 23:04:44 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1797580,2019-03-22 03:46:48 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1797580,2019-03-21 15:22:32 UTC,"Reviewed:  https://review.openstack.org/611945
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a29a3c9cb16ee0b42f125f8e9b047f22d05c47c4
Submitter: Zuul
Branch:    stable/queens"
1797580,2018-12-19 10:01:37 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1797580,2018-12-14 05:17:18 UTC,"Reviewed:  https://review.openstack.org/611944
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fbf729d61b608bf8b19157bf699f6c0b5f43f10d
Submitter: Zuul
Branch:    stable/queens"
1797580,2018-11-08 18:22:32 UTC,"Reviewed:  https://review.openstack.org/611939
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=954b2004a1daa43d4dff0694e6e5cdb9630a441b
Submitter: Zuul
Branch:    stable/rocky"
1797580,2018-10-19 20:03:55 UTC,"Reviewed:  https://review.openstack.org/610098
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ce3af5e33ae6843411e611e81c6ca1c21e0f1e09
Submitter: Zuul
Branch:    master"
1797580,2018-10-19 19:56:23 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/611944"
1797580,2018-10-19 19:55:35 UTC,"Reviewed:  https://review.openstack.org/610088
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bfc8d1052ba6f1011fcdb882a825694acf98dd39
Submitter: Zuul
Branch:    master"
1797580,2018-10-19 19:43:48 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611939"
1797580,2018-10-19 19:43:28 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611938"
1797580,2018-10-12 16:07:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/610098"
1797580,2018-10-12 15:39:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/610088"
1797580,2018-10-12 15:10:37 UTC,"By the way, this is where the changes to the request_spec get persisted during the cold migrate:"
1797580,2018-10-19 19:56:44 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/611945"
1797581,2018-12-17 08:25:19 UTC,"Again it seems to break on initramfs being bad:
[    0.840153] Initramfs unpacking failed: no cpio magic"
1797581,2019-04-19 15:39:57 UTC,"The kernel code path mentioned in #55 is only executed if there is no ""early userspace init"" - in other words, if there is no /init on initrd:"
1797581,2019-04-19 15:04:04 UTC,"echo -n 'BOOT_IMAGE=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs ip=::::maas-vhost6:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc cloud-config-url=http://10.10.101.2:5248/MAAS/metadata/latest/by-id/xeqrrw/?op=get_preseed apparmor=0 log_host=10.10.101.2 log_port=5247 --- console=ttyS0,115200 initrd=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/boot-initrd BOOTIF=01-52-54-00-3f-ae-46' | wc -c
576"
1797581,2019-04-19 13:50:53 UTC,Just reproduced it on my env (where things used to work) after updating from MAAS 2.5.0~rc2 to 2.5.2.
1797581,2019-03-21 16:37:24 UTC,"Ok, thanks Jason.
That is great info, but about as much as we had so far :-/"
1797581,2019-03-21 16:15:01 UTC,@Christian
1797581,2019-03-21 06:51:11 UTC,"Jason,
thanks for chiming in - so far this was non-reproducible every time we looked at it. We had plenty of approaches with the MAAS team to this and later on with Thiago, but still miss the right data to continue."
1797581,2019-01-14 16:59:38 UTC,"@Thiago,
Can you attach your guest XML that's working successfully with 2048MB?"
1797581,2019-01-15 15:45:09 UTC,"Ryan,"
1797581,2019-01-14 20:34:31 UTC,"On Mon, Jan 14, 2019 at 1:55 PM Thiago Martins <email address hidden>
wrote:"
1797581,2019-04-19 15:56:05 UTC,I cannot reproduce the same with a xenial (GA kernel) image with 2048 MiB of RAM allocated to a VM.
1797581,2019-01-14 16:41:26 UTC,I'm also facing this problem.
1797581,2019-01-05 03:01:50 UTC,Reproduced today on MAAS 2.5 latest bionic
1797581,2018-12-17 16:07:15 UTC,@Ryan - the resource and other bits being different is because in the bad case the domain was up and in the good case down. That in itself is not a problem.
1797581,2018-12-17 15:16:39 UTC,"One other oddity in the xml is the cgroup construction in the ""bad"" case."
1797581,2019-03-20 21:27:14 UTC,Bumped to field-high as we ran into this again in testing.
1797581,2019-04-19 16:18:55 UTC,Found something interesting.
1797581,2019-04-23 11:55:57 UTC,"Fro experimenting with sizes things can easily be padded with zeros:
$ truncate -s 80000000 bug-1797581-bad-initrd-extended
$ truncate -s 9000000 bug-1797581-xenial-base-extended"
1797581,2019-04-23 10:57:25 UTC,"@Dmitrii - we were at the ""junk in ..."" in comment #21 already.
The ""broken padding"" is interesting but might be the same issue with a different message as the newer kernel understands slightly more about it."
1797581,2020-02-28 08:39:08 UTC,"Setting this to incomplete for maas as weel, since we couldn't reproduce the issue with maas 2.7."
1797581,2020-02-28 00:45:36 UTC,As this is subscribed to field-high and field-medium I am unsubscribing field-high. There has been no update for 9 months to this bug. If folks are still seeing this then additional logs and help reproducing would be much appreciated.
1797581,2019-09-18 13:58:41 UTC,"It was already clear on the bug that for qemu I can't do much more as-is.
So I had a discussion with the Maas Team today.
To core issue for me stays that it seems it is unreproducible outside of Maas."
1797581,2019-06-24 09:34:22 UTC,"Thanks Kellen,
I took your kernel/initrd and IPXE booted it fine via http from qemu's IPXE on a 2G guest.
In the past we tried more (use squash, use tftp instead of http, use the same parmlines as maas, ...), but it all comes down to the same thing every time - only occurs inside Maas."
1797581,2019-06-23 00:31:29 UTC,"Ran into this today, attaching the information requested in #51."
1797581,2019-06-17 11:16:08 UTC,"Yeah, it seems to only occur with the TFTP setup that maas creates - and in all former cases it resolved a few days later - most likely by size of images changing.
That is the reason we need the files from an affected case."
1797581,2019-04-19 18:06:58 UTC,Tested bionic-hwe - the issue does not occur with 2048 MiB.
1797581,2019-06-14 11:49:30 UTC,"I can also confirm the reported issue. I've tried with Juju and plain MAAS to create a VM with just 2048MB and it fails in both cases. Creating, registering and commissioning the machine works, but it cannot be deployed."
1797581,2019-05-09 05:10:41 UTC,@sfeole Thanks for the Dup hit that as well now - as all others I ask you to please help to catch the data needed to finally recreate and debug this.
1797581,2019-04-23 13:18:59 UTC,"After a longer session on IRC this is now also for Dmitrii un-reproducible.
Lets summarize the current status for the next oen coming by:"
1797581,2019-04-23 12:33:16 UTC,Tried using direct kernel boot with QEMU and couldn't reproduce it:
1797581,2019-04-23 12:15:44 UTC,The bionic/ga files from #63 need to be placed into both dirs:
1797581,2019-04-23 12:03:10 UTC,"tar -czvf boot-resources-20190419-115735-amd64-generic-bionic.tar.gz boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/squashfs
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-kernel
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-initrd"
1797581,2019-04-23 11:40:00 UTC,"Ran with:
- the cloud-image of Xenial of 20190419 [1]
- XML with a memory definition of:
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
- kernel&initrd are from the host
   <kernel>/var/lib/libvirt/images/bug-1797581-bionic-base</kernel>
   <initrd>/var/lib/libvirt/images/bug-1797581-bad-initrd</initrd>
- The attached broken initrd of comment #56
- Otherwise it is a uvtool kvm guest as it is created on Bionic
- Host is Bionic
- different kernels:
  - xenial
  - xenial hwe
  - bionic
  - bionic-hwe"
1797581,2019-05-09 05:16:04 UTC,Added to the description what we need from anyone affected.
1797581,2018-12-14 13:11:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797581,2019-01-14 19:47:45 UTC,"@Ryan,"
1797581,2018-12-14 13:05:56 UTC,"Subscribing field-medium as workaround (e.g not to use 2048mb ram VMs) exists, but solution still need to be found."
1797581,2018-10-15 10:53:01 UTC,As Ryan I can not reproduce locally - hrm.
1797581,2018-10-13 00:56:59 UTC,Here's a full console log from the failure.
1797581,2018-10-12 22:05:27 UTC,It's an empty image - MAAS PXE boots the VM.
1797581,2018-10-12 20:49:20 UTC,I'm unable to recreate with a daily bionic cloud-image on a bionic host with the same versions.
1797581,2018-10-12 20:46:54 UTC,The backing image:
1797581,2018-10-12 20:03:14 UTC,And /var/log/libvirt/qemu/<guestname>.log ?
1797581,2018-10-15 11:00:15 UTC,After DHCP is up it works just fine.
1797581,2018-10-12 19:55:04 UTC,Here's the version information.
1797581,2018-10-12 19:24:03 UTC,Can you attach the guest xml and host kernel/qemu/libvirt packages?
1797581,2018-10-12 19:08:27 UTC,"We can't run apport-collect since the machine doesn't boot, but this was seen with a non-tainted 4.15.0.36-generic kernel in my environment."
1797581,2018-10-12 19:01:22 UTC,"To be clear, the kernel panic is seen when a VM is composed in MAAS with exactly 2048 MB of RAM. Composing with 2047 or 2049 MB RAM results in a working VM."
1797581,2018-10-12 18:56:15 UTC,Adding the linux package; we should narrow down the issue to see if it's in kernel space or user space.
1797581,2018-10-12 17:31:15 UTC,I can't reproduce this crash. Does the kernel panic happen at commissioning time or later?
1797581,2018-10-12 17:09:39 UTC,"This doesn't appear to be a UI issue. Steve, has taken a look into the templates but it all seems to be displaying correctly."
1797581,2018-10-12 19:50:51 UTC,Here's an example of working XML (with 2047 MB RAM) that MAAS generated:
1797581,2018-10-15 12:07:43 UTC,"Working on this I found by accident that I actually can reproduce:
  VFS: Cannot open root device ""squash:http://192.168.122.1:80/squashfs"" or unknown-block(0,0): error -6"
1797581,2018-10-12 20:33:49 UTC,Here's the log from the failing VM. Doesn't look too unusual to me...
1797581,2018-10-16 07:26:27 UTC,"Since it is reproducible maybe not a networking hiccup.
But maybe a hiccup of the PXE setup (thats why I asked for it).
Or a hiccup of the quite complex shim loading if signed kernels are used."
1797581,2018-10-15 16:39:58 UTC,"[    0.943808] Unpacking initramfs...
[   20.690329] Initramfs unpacking failed: junk in compressed archive
[   20.703673] Freeing initrd memory: 56612K"
1797581,2018-10-18 05:02:49 UTC,"Hi,
thanks for your feedback.
We are at least much closer to what happened and thereby should be faster if it reoccurs.
I don't think it is an interaction of the Kernel and Squashfs as we found that already initramfs unpack was broken. That is before Squash comes into play."
1797581,2018-10-17 16:54:17 UTC,"Looking again at the date stamps, I don't see any squashfs filesystems older than October 15th. The kernels are all from ~September 25th. So I feel like this must have been an interaction between the kernel September 25th and whatever the previous squashfs was."
1797581,2018-10-17 16:51:03 UTC,"After triaging this again on a call with Andres (who originally reported this) this morning, we determined that this issue is no longer reproducible with MAAS. The only way for me to explain it at this point was that there was something wrong with the daily image MAAS was using last week, and a subsequent update fixed it. (It looks like the images were updated yesterday.)"
1797581,2018-10-17 11:28:11 UTC,There actually is no need to debug further on my non-maas PXE setup.
1797581,2018-10-17 11:10:18 UTC,"Taking the x86 pxelinux.0 from /usr/lib/PXELINUX/pxelinux.0 and otherwise doing the same tftp setup as in [1] and switching from the ""maas"" to the ""default"" network where I have set up dhcp to netboot by libvirt as in [1]. I can see netboot happening."
1797581,2018-10-17 08:36:55 UTC,"I didn't see any guests crashing, instead they all just hang finding nothing to boot."
1797581,2018-12-14 13:02:49 UTC,Reproduced today on MAAS 2.5 / latest Bionic.
1797581,2018-12-14 13:06:51 UTC,"Setting this back to incomplete for MAAS because there is not enough information to determine this is a MAAS Bug. That said, given that this work with any VM other than one with 2048 of RAM, the issue may appear to be the kernel or libvirt."
1797581,2018-10-17 07:19:21 UTC,"I must admit, compared to you just sharing your kernel/initrd/squash asking to install an own dev maas in comment #23 consumes quite some time :-/
Waiting for a sync here, setting up users there, sorting out how to make us provide PXE and such on the ""maas"" virtual network, ... - it just isn't one click and ready."
1797581,2018-10-16 23:56:52 UTC,... it's interesting that [practically?] the same kernel version that fails consistently with Bionic works just fine with Xenial.
1797581,2018-10-16 23:54:42 UTC,I just tried Xenial with the HWE kernel - same result (success). FYI.
1797581,2018-10-16 23:46:20 UTC,"Good idea @rharper. It's easy for MAAS to attempt commissioning on Xenial or Bionic, so I gave Xenial a try. It works fine![1]"
1797581,2018-10-16 22:19:37 UTC,Does this fail with other releases? like trusty?  I was wondering if initrd size plays a factor here:
1797581,2018-10-16 21:48:35 UTC,"I agree that this doesn't look like a QEMU issue, and I agree that it doesn't look like a [general] networking hiccup."
1797581,2018-10-17 08:32:21 UTC,I didn't let me calm down - I found in the doc [1] that the switch might be on the VLAN and not the subnet (Hrm why?)
1797582,2018-11-30 21:43:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797587,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1797587,2019-01-15 21:42:43 UTC,"Brad, Sujith is on vacation until 1/22/2019. We will try to find someone to verify. But if we are not able to locate, What is the plan to mitigate waiting for Sujith to return?
--jerry"
1797587,2019-01-15 10:37:52 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1797587,2019-01-08 19:58:34 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2019-January/097553.html"
1797587,2018-12-14 17:19:51 UTC,"Can I now changed this bug to Public?  That will allow me to submit the SRU request.  If we need, we can removed any sensitive information."
1797587,2018-12-10 14:48:28 UTC,"@jsalisbury -
Inclusion of the above patch is enough from the kernel side. Rest aspects will be taken care by the userspace tools.
Please include the requested patch."
1797587,2018-10-29 16:08:24 UTC,"@jsalisbury -
Update -
Since there was no difference in the output with and without the patch, we are approaching Intel for more details on the fix.
Will keep you guys updated once we get a response."
1797587,2018-10-12 21:50:34 UTC,"I built a test kernel with commit 62843c2e42.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1797587"
1797587,2018-12-18 06:12:49 UTC,"@Joseph - Yes, You can open this to public."
1797588,2018-10-12 17:10:27 UTC,"https://bugs.freedesktop.org/show_bug.cgi?id=108346
--
Cristian Aravena Romero (caravena)"
1797588,2018-10-12 17:26:51 UTC,"Hello David,"
1797588,2018-10-15 02:28:55 UTC,"David,"
1797588,2018-10-15 02:29:49 UTC,"Cristian,"
1797588,2018-10-15 02:31:37 UTC,"David,"
1797597,2018-10-22 18:10:38 UTC,"I am confused it on the bug. It seems that the size of 117082529792 is correct for the storage pool. The used/available is what MAAS knows about, meaning MAAS uses the block devices in MAAS to calculate the used/available. MAAS does not store the used in the model, that is calculated based on the block devices created in the pool in MAAS."
1797597,2018-10-29 14:54:08 UTC,The problem with that is that MAAS doesn't really know what an available storage pool size is.
1797597,2019-09-19 14:47:44 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1797599,2018-10-30 22:51:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797599,2019-01-13 14:29:02 UTC,"I have this same issue, but only with one set of FLAC files.  They are (I believe) 96 kHz files ripped from a Blu-Ray audio disc.  My FLACs of CD rips are fine."
1797599,2020-01-21 03:34:26 UTC,I see this as well.
1797599,2020-01-21 03:39:47 UTC,Looks like this is coming from ffmpeg: https://github.com/FFmpeg/FFmpeg/blob/06f6857b54a7fbbd087b0803f75bed44abed50d9/libavcodec/decode.c#L824
1797604,2020-05-11 10:50:06 UTC,Could you try if that's still an issue with the current hwe updated stack?
1797604,2019-01-21 06:25:02 UTC,Finally I have fixed the problem by compiling and installing latest git xf86-video-intel driver. Now everything works fine. Thanks.
1797604,2019-01-21 06:24:20 UTC,Finally I have fixed the problem by compiling and installed latest git xf86-video-intel driver. Now everything works fine. Thanks.
1797604,2019-01-21 05:32:09 UTC,Hello
1797604,2018-10-30 14:44:20 UTC,"Marking as bb-notfixing.  This means the bug is not considered a release blocker, but can still be worked on and fixed."
1797604,2018-10-12 19:45:19 UTC,"Hello Dmitry,"
1797604,2018-10-12 20:09:55 UTC,Before 18.04 I tried  linux-image-4.18.13-041813 kernel on 16.04 with HWE Xserver but the same. If you want I can try any newest kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline that already have this patch.
1797604,2018-10-12 19:39:18 UTC,"commit e7bfc9065345085f767235eea8b148c356e5bd2b
Author: Liwei Song <email address hidden>
Date:   Thu Mar 15 23:14:18 2018 -0400"
1797604,2018-10-12 18:58:03 UTC,Also I found than glxgears has some artifacts (see attached pic) if running without vsync with Awesome WM in DRI2 mode/ Intel driver. In full screen mode or with vsync no artifacts. Also no artifacts if running without awesome WM.
1797604,2018-10-12 17:41:14 UTC,"Hello,"
1797604,2018-10-12 23:28:20 UTC,"@Dimitry,"
1797605,2020-03-10 06:59:40 UTC,This appears more as a system issue then something the charm has done
1797626,2019-05-22 13:19:23 UTC,Ovidiu comments that this is expected behavior.
1797626,2019-05-22 20:03:55 UTC,"Changing the priority to Low as this is no longer considered gating based on Cindy's comment above.
If this is expected behavior, I suggest to update the status to Invalid so that the bug is considered closed. Is there a reason to continue to keep this open?"
1797626,2019-05-08 18:55:33 UTC,"Maria please retest this bug, verify that it is still an issue and if so, provide detailed repro steps.  Thanks!"
1797626,2018-11-08 06:24:16 UTC,"Please ""Maria Yousaf"" feedback above questions."
1797626,2018-11-08 06:19:02 UTC,1. How to set up the test environment? Please give detail documents about hardware requirement and the running software.
1797626,2018-10-15 17:38:52 UTC,Targeting stx.2019.03 as this is a corner case during disk replacement
1797626,2018-11-09 01:12:01 UTC,"Hi Maria Yousaf,
   Could you give the feedback?
   This problem is reported on 2018-10-13, what's the latest status?"
1797628,2018-10-15 03:00:05 UTC,This change was made by a bot.
1797628,2018-10-15 17:28:43 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1797628,2018-10-15 19:53:53 UTC,This started happening after the distribution upgrade from Bionic 18.04 which I did in the first few days of October 2018. (Sorry for lack of specificity here.)
1797628,2018-10-16 06:31:39 UTC,Seems like it worked on older kernels. Can you find out which on works?
1797628,2018-10-16 15:56:03 UTC,I would like to but I have a correction to report: this system never had 18.04 LTS (or any prior versions) on it. I had remembered upgrading a different machine to Cosmic at the same time as I had done a fresh install on this machine.
1797635,2019-06-10 18:38:05 UTC,"There are significant changes required to support Distributed Cloud in stx due to the containerized environment. Based on discussion with the Distributed Cloud PL, Dariush Eslimi, we agreed to close old Distributed Cloud bugs as Won't Fix. A full test cycle will be needed to verify the new implementation and new bugs can be opened for the issues reported then."
1797635,2019-06-11 19:12:39 UTC,closing per wont fix decision above
1797635,2018-10-15 17:35:53 UTC,Targeting stx.2019.03 - horizon issue with distributed cloud. Doesn't gate stx.2018.10 as it's not a common config
1797636,2018-10-12 21:56:06 UTC,"Maybe we should set the dpkg options --force-confdef,confnew"
1797636,2018-10-18 14:12:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797636,2018-10-18 20:29:36 UTC,I think that will work. I tried enabling these settings and it completed this time
1797637,2018-10-15 17:34:25 UTC,Targeting stx.2019.03 - horizon issue with distributed cloud. Doesn't gate stx.2018.10 as it's not a common config
1797637,2019-06-10 18:38:44 UTC,"There are significant changes required to support Distributed Cloud in stx due to the containerized environment. Based on discussion with the Distributed Cloud PL, Dariush Eslimi, we agreed to close old Distributed Cloud bugs as Won't Fix. A full test cycle will be needed to verify the new implementation and new bugs can be opened for the issues reported then."
1797637,2019-06-11 19:12:12 UTC,closing per wont fix decision above
1797647,2019-06-25 11:21:16 UTC,This bug was fixed in the package imagemagick - 8:6.9.7.4+dfsg-16ubuntu6.7
1797651,2020-06-23 12:55:18 UTC,codeblocks-common 16.01~ubuntu16.04.1
1797662,2018-10-14 09:05:02 UTC,Thank you for reporting this issue and help making Ubuntu better.
1797665,2019-03-13 21:53:52 UTC,"I was also able to reproduce this in cosmic with 0.7-0ubuntu2. For me, the segfault happened when there were 15 messages or more."
1797665,2019-03-11 20:36:30 UTC,I intend to close this ticket soon if no confirmation of this still being a problem comes forward.
1797665,2019-03-13 23:34:09 UTC,My last comment was on live in a VM. I redid it in an installed VM with 2G memory allocated and needed to up it to 20 messages before I could get it to die. Somehow it seems there there's some sort of proportional relationship between the number (or size as many of mine were small) of messages and the amount of memory. Similar results with latest git (b94f4307).
1797665,2019-03-13 23:27:27 UTC,I neglected to mention in my previous comment that I was testing on a Dell Inspiron 7720 laptop with an Intel i5-3210 processor and 8 Gb of RAM.
1797665,2019-02-11 16:24:53 UTC,I was unable to reproduce this with a self-compiled trojita 0.7-0ubuntu2 on bionic.  Is this still an issue?
1797665,2019-03-13 20:59:57 UTC,"So with 10 emails, I can easily reproduce this in dingo with 0.7-0ubuntu2. With less emails, it doesn't work."
1797665,2018-10-16 03:17:28 UTC,"STEPS TO REPRODUCE
 1. Click on a folder
 2. Click a column header to sort by that column
 3. Repeat #2 several times (can be a different header)"
1797665,2018-10-13 15:14:30 UTC,"Unfortunately, I can't reproduce this. I do have a fairly empty inbox, though. How many messages and what size are you dealing with?"
1797665,2018-10-13 17:56:27 UTC,"Good point. I've just tried it again, and sorting works fine in my smaller imap folders. The main inbox has 78 messages."
1797665,2018-11-12 12:48:21 UTC,I was able to get a backtrace after a long series of random clicking. This is with a random and pretty old snapshot of Qt.
1797665,2018-10-16 02:59:28 UTC,"I actually got this to fail in as little as about 10 messages. It's also that way in the latest git master, so it looks like it's an unsolved issue. Pushing upstream."
1797665,2018-10-13 18:08:08 UTC,"The size of the messages ranges from 2KB to 300KB, with the vast majority between 4KB and 10KB."
1797669,2018-10-15 17:32:17 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1797669,2018-10-16 01:18:00 UTC,"yes, I upgrade from ubuntu 4.4.0-116-generic, and it works fine.
I tested upstream latest v4.19 kernel first and it is fine, then find out that upstream has this issue between 4.15.x-4.16.2."
1797675,2018-10-14 02:46:22 UTC,#4260 - corrected a problem with car count identified in this thread - https://bugs.launchpad.net/or/+bug/1797675
1797675,2018-10-14 06:43:04 UTC,#4261 - fixed problem due to poorly defined ENG file loading - http://www.elvastower.com/forums/index.php?/topic/32401-fpm-pacific-surfliner-problem/page__st__10__gopid__241899#entry241899
1797678,2018-10-13 08:20:18 UTC,I forgot to say that the printer is a networked Samsung SCX-4729FD.
1797678,2018-10-13 11:18:45 UTC,"Solution found in Ask Ubuntu site at:
https://askubuntu.com/questions/1081885/printer-stopped-working-after-upgrade-16-04-to-18-04
Solution is:
sudo rmdir /usr/share/ghostscript/9.25/iccprofiles
sudo apt-get install --reinstall libgs9-common"
1797678,2020-03-03 20:33:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797680,2019-03-27 08:53:17 UTC,Note: This still happens on GTK+3.
1797680,2018-11-01 17:01:46 UTC,May be related with https://bugs.launchpad.net/kicad/+bug/1779854 ?
1797681,2018-10-13 09:08:59 UTC,https://review.openstack.org/#/c/610177/
1797682,2019-09-17 10:21:55 UTC,Migrated to https://github.com/widelands/widelands/issues/2121
1797683,2018-10-16 13:44:27 UTC,"One software that I already used
https://www.youtube.com/watch?v=9ZPok7dK5g0&t=33s"
1797683,2018-10-13 15:38:51 UTC,"I am currently working on a solution for this because it has to be
solved for legacy schematics which we will always have to support.  I
don't expect this to be easy to resolve but I'm pretty confident it can
be solved.  My goal is to have it done for 5.1."
1797683,2018-10-13 14:01:34 UTC,I would say this feature can be implemented in a safe way when the new schematic file format is in place.
1797683,2019-07-28 11:53:42 UTC,Hello
1797683,2018-10-13 12:47:47 UTC,"from what I found out, there pops up a warning when Design Rules differ and you can change it to the board defaults."
1797683,2018-10-13 11:08:56 UTC,"Importing a sheet is already supported by Eeschema.
This kind of feature is really *complex* (although useful)."
1797683,2018-10-13 13:37:51 UTC,"Adding (importing) hierarchical sheets is easy, and should not create duplicated net issues as long as no global label is used (this is the interest of hierarchies and local labels)."
1797686,2018-10-14 06:57:33 UTC,This looks like a problem with your graphics driver. See
1797686,2019-09-17 07:27:10 UTC,Migrated to https://github.com/widelands/widelands/issues/3336
1797686,2018-10-13 16:40:59 UTC,Can you provide some information of the installed packages related to graphics?
1797697,2018-10-13 14:45:45 UTC,Thank you for your bug report.
1797697,2020-04-22 23:01:21 UTC,"we no longer publish hungarian, only U.S. English."
1797702,2019-09-16 08:28:04 UTC,Migrated to https://github.com/widelands/widelands/issues/3337
1797707,2018-10-15 15:14:57 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1797711,2020-03-07 11:29:43 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1797717,2020-01-26 22:12:37 UTC,"Right now in 19.10, /lib/systemd/system/fstrim.service runs /sbin/fstrim --fstab --verbose --quiet , which doesn't cause the service to report these errors. According to the fstrim man page, for the --fstab option: ""Errors from filesystems that do not support the  discard  operation,  read-only  devices  and read-only filesystems are silently ignored."""
1797717,2018-10-22 19:11:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797717,2018-10-22 19:14:15 UTC,I see the same warnings in systemd log.
1797718,2018-10-15 15:18:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1797718,2019-08-03 04:17:18 UTC,[Expired for gnome-disk-utility (Ubuntu) because there has been no activity for 60 days.]
1797725,2018-10-16 08:51:11 UTC,In build 20181015 problem disappeared.
1797725,2020-03-07 11:32:14 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1797734,2020-03-15 08:58:03 UTC,Last month some of Canonical engineering met up for a regular conference. There a couple of talks were given about what's being done to speed up snap launch times. I was surprised and encouraged there were a couple of efforts in progress. So better performance is coming...
1797734,2020-03-15 14:36:10 UTC,"It is not physically possible to ever get a snap to start as fast as a native application.  The entire purpose of a snap is that it uses its own set of dependencies, which means that by definition it cannot share those dependencies with other applications on the system, which means that they must be loaded separately, which will take longer, use more system resources, etc."
1797734,2020-03-14 13:59:12 UTC,"I'm not sure why the ""is 2s too slow to start"" is the question being asked.  Who starts and stops their calculator multiple times in a row?  That's not a realistic use-case for the vast majority."
1797734,2020-03-16 01:29:57 UTC,That's a good case for keeping this bug logged here under gnome-calculator. Maybe we should just drop the snap and default to the deb. I'll assign this bug to ubuntu-meta for that...
1797734,2020-02-25 14:37:07 UTC,"untagging, that's being worked but not specific enough to be rls tracked"
1797734,2020-11-11 17:36:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797734,2020-11-12 02:09:45 UTC,ubuntu-meta (1.444) focal; urgency=medium
1797734,2020-11-12 02:10:36 UTC,"^^^
The issue was resolved in Ubuntu 20.04. If you need a fix for Ubuntu 18.04 then please see comment #4."
1797734,2020-03-16 18:18:41 UTC,"Hey, if my assertion incentivizes someone to figure out how to do that, I'm more than willing to admit I was wrong :)."
1797734,2020-02-23 05:58:07 UTC,This problem persists on Ubuntu 20.04. See this proposal to remove the snap version of the package: https://discourse.ubuntu.com/t/proposal-for-ubuntu-20-04lts/12969/92
1797734,2019-10-10 15:46:56 UTC,"Hi, Ubuntu 18.04.3 LTS running on SSD laptop with 16GB ram and i7 cpu here, i can confirm that startup was very slow and was solved doing:"
1797734,2019-06-11 11:08:38 UTC,"Hello,
Try to remove the snap package:"
1797734,2019-05-22 13:11:24 UTC,"We can further improve this now that we have layouts.  Once the snapcraft gnome extension lands, I'll look into adding that to the extension."
1797734,2019-05-22 09:46:54 UTC,2 seconds it way to slow for simple application like this on a system installed 6 days ago on a quite good machine. Firefox opens way faster.
1797734,2019-05-22 09:27:07 UTC,"On many keyboards there is a dedicated Calculator button so you may expect a fast launch. I use the deb version of gnome-calculator for this reason, and it launches apparently instantly. So I understand if a few seconds seems too long by comparison."
1797734,2019-05-22 09:21:10 UTC,"Thanks, the first use is still probablematic indeed. Do you consider 2 seconds as too slow?"
1797734,2019-05-22 09:05:04 UTC,Here's my trace. You can see the first launch takes around 2 seconds. Second run takes significantly less time. In both cases `/snap/gnome-calculator/406/bin/desktop-launch` is what takes most of the time during startup.
1797734,2019-05-22 08:25:47 UTC,"Could those having the issue copy the output of this command in the bug?
$ snap run --trace-exec gnome-calculator"
1797734,2019-05-21 23:33:39 UTC,"At least on Ubuntu 18.04, I found that the version from the apt package starts up much faster than the snap version. I ended up swapping them using `sudo snap remove gnome-calculator && sudo apt install gnome-calculator`"
1797734,2019-03-04 10:57:07 UTC,"This is a problem on 18.10 Cosmic Cuttlefish, as well. Embarrassingly slow for a simple application like this."
1797734,2018-11-12 14:02:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797739,2018-10-15 13:26:38 UTC,"Going to add a flag to make it possible to override the : check.  I don't want to remove that check completely, as that would break people's score cards by evaluating things like is_admin and other common checks that the : check was skipping."
1797739,2020-05-19 17:10:15 UTC,"Change abandoned by ayoung (<email address hidden>) on branch: master
Review: https://review.opendev.org/610402"
1797739,2018-10-15 01:34:28 UTC,"Turns out the checker looks for a : in the rules, as most of the other services are formatted like identity:create_user, but glance has no namespace."
1797741,2019-08-20 01:48:09 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1797743,2018-10-15 16:44:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797745,2019-10-15 10:54:06 UTC,Hello
1797748,2019-03-03 17:57:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797748,2019-04-25 19:05:25 UTC,"Similar problem here, although the GNOME Integration extension works in Chromium for me. In Firefox, it remains broken."
1797752,2018-11-19 12:54:29 UTC,what exact version of Windows?
1797752,2018-11-19 22:00:23 UTC,"Hi!
Windows 10 Version 1803  (Build:17134.407)"
1797752,2018-11-20 09:26:27 UTC,"ok, thanks."
1797752,2019-01-06 09:46:38 UTC,"For your information, my workaround on the PC where clicks don't work anymore, is to start SIKULIX via that .bat script: that works fine in all the cases."
1797752,2019-01-06 10:05:03 UTC,interesting - thanks a lot.
1797753,2019-10-11 01:30:04 UTC,"Given that bug 1740231 covers the wifi issue, can we reword this bug to be about just the touchpad?"
1797753,2019-12-10 04:17:35 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1797753,2019-10-07 12:08:07 UTC,"projects on github seems to work, maybe concider integrating into ubuntu / kernel if possible, so that we don't have to reinstall module with each new kernel update."
1797753,2018-10-14 12:23:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1797753,2019-01-03 17:36:10 UTC,No upstream support yet. Please refer to LP: #1740231 for more information.
1797753,2019-03-11 01:19:17 UTC,"Please add driver for wireless RTL8821CE to Ubuntu 18.04, 18.09, and Ubuntu 19.04 (HP Notebook - 14-df0010nr)"
1797754,2020-03-25 17:04:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797755,2018-10-29 10:46:17 UTC,"Hi Eric,"
1797755,2020-03-03 13:33:40 UTC,oopsie; this is confusing
1797757,2018-10-14 20:26:12 UTC,It seems that the reason for this failure was that there was no EFI partition. Probably this can be detected and reported with a more informative error message.
1797761,2019-04-16 16:43:14 UTC,This bug was fixed in the package gradle - 4.4.1-5ubuntu2~18.10
1797761,2019-04-16 16:23:22 UTC,This bug was fixed in the package gradle - 4.4.1-5ubuntu2~18.04
1797761,2019-03-21 03:14:31 UTC,This bug was fixed in the package gradle - 4.4.1-5ubuntu2
1797761,2019-03-21 18:45:18 UTC,"Cool, thanks! Works well so far (both Bionic and Cosmic)."
1797761,2019-03-20 18:35:30 UTC,I tested all my projects in the Gradle 4.4.1 / OpenJDK 8 combination and I can say it's compatible. So there is no reason to not allow an alternative dependency to OpenJDK 8.
1797761,2018-11-11 11:45:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797761,2019-03-20 18:35:47 UTC,#1820389
1797765,2019-07-14 11:48:07 UTC,"Change abandoned by zhulingjie (<email address hidden>) on branch: master
Review: https://review.opendev.org/610364"
1797765,2020-07-25 15:47:00 UTC,This is now supported in release 8.0.0
1797766,2019-04-13 02:16:49 UTC,"Change abandoned by zhulingjie (<email address hidden>) on branch: master
Review: https://review.openstack.org/610350"
1797767,2019-04-12 14:54:17 UTC,"Change abandoned by zhulingjie (<email address hidden>) on branch: master
Review: https://review.openstack.org/610352"
1797769,2018-11-13 22:30:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797772,2019-07-22 06:43:08 UTC,"forevertheuni,
Please try https://people.canonical.com/~khfeng/lp1833630/"
1797772,2019-07-18 18:53:30 UTC,"I have the same problem in lenovo y540, can you help me get it working there? I lose the acpi from this module :("
1797772,2019-07-20 04:16:32 UTC,"By the way. I went to linux kernel 5.2.1 ideapad_laptop.c and now there's no no_hw_rfkill_list. It's the opposite, now it has to be specified if there is a hw-rfkill. So that new laptops don't get this problem."
1797772,2019-07-18 23:44:32 UTC,"I solved it in my Y540 by compiling a new ideapad_laptop with dkms adding ""legion Y54015IRH"" to the no_hw_rfkill_list."
1797772,2019-08-01 20:44:30 UTC,Also happens on the c930
1797772,2019-01-18 08:32:44 UTC,"Hi TJ, do you still have the machine? Can it be fixed with the similar approach as you did in bug 1811815?"
1797772,2018-10-15 17:30:49 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1797772,2018-10-14 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797772,2018-10-20 17:57:02 UTC,It was a clean install of 18.10. The mainline module doesn't have support for this device as yet. Since the blacklist the user has gone quite so additional testing is not possible
1797774,2018-10-14 14:07:15 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1797775,2019-06-16 15:53:40 UTC,"Reviewed:  https://review.opendev.org/610376
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=7db3e3b005470df345ffc624ec9cea6527abb849
Submitter: Zuul
Branch:    master"
1797777,2019-04-09 09:05:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797777,2019-11-25 15:13:27 UTC,"I am new to launch pad, but I would like the maintainers merge this patch.
How can I help you?"
1797779,2019-02-28 14:21:41 UTC,The iso-codes issue got resolved with https://gitlab.gnome.org/GNOME/gedit/commit/0b3c018d
1797787,2018-12-08 14:37:49 UTC,I don’t think it’s quite correct to say we’re breaking existing boards.  The user has to do something to trigger a zone re-fill to get the change.
1797787,2018-12-08 13:57:12 UTC,"We have an non-written policy about not breaking (aka changing without
the users knowledge) existing boards so I'm going to side with JP on
this one.  We should wait and implement this in v6 as a new feature."
1797787,2018-12-08 10:33:55 UTC,"I agree with Seth: this change can create issues with existing boards.
The best way is to revert it."
1797787,2018-12-07 20:39:16 UTC,The problem is that people have made boards in v5 using this work-around.  Removing it changes the board output and may invalidate existing designs as copper now extends closer to the edge.
1797787,2018-10-16 15:19:54 UTC,A lot of board vendors have a different required margin from the board edge for internal and external layers (see e.g item 6 in the [copper layer design rules of Eurocircuit](https://www.eurocircuits.com/pcb-design-guidelines/#copperlayers))
1797787,2018-12-07 19:34:58 UTC,@Jeff- This disabled the only way to set the clearance to the board edge.
1797787,2018-11-14 23:46:49 UTC,"Fixed in revision bcc8c642562ee9013e5b76a696e6c3faa6b907ef
https://git.launchpad.net/kicad/patch/?id=bcc8c642562ee9013e5b76a696e6c3faa6b907ef"
1797787,2018-12-08 16:25:38 UTC,"@Feff, this case is subtle.  I use this trick as well to ensure the board edge clearance is greater than the zone fill clearance.  I have a few boards where I need a low zone fill clearance (<= 10 mils) to ensure I end up with a continuous fill.  Doing this puts the zone fill dangerous close to the board edge so the board edge line thickness trick ensures that I don't end up with exposed copper.  I know this is not ideal and that the bug submitter is correct that the clearance should be determined from the center of the board outline layer line.  Unfortunately we have users who have used this trick so changing it would change the board edge clearance should they ever need to revise their board layout that requires a zone refill.  We need to create a new board edge clearance feature to implement this in a way that wont bite someone who isn't expecting their board edge clearance to change.  This should be part of our new constraint management system."
1797787,2018-12-07 20:28:31 UTC,"Well, it comes down to bug vs. missing-feature work-around.  I'm sure you'd find people to come down on either side of the argument."
1797787,2019-04-05 21:19:30 UTC,"Fixed in revision 1ae47b6069e54da89fa43896ab25a18f68e985b3
https://git.launchpad.net/kicad/patch/?id=1ae47b6069e54da89fa43896ab25a18f68e985b3"
1797790,2020-03-21 15:48:32 UTC,Closing because INVALID: support request.
1797790,2018-10-15 01:47:09 UTC,could you attach a sample svg file?
1797791,2018-10-15 23:06:54 UTC,"I believe that I have identified why the newer nvidia drivers which depend on the new nvidia_drm kernel module fail on Mac hardware. That new module depends on the ipmi modules. On Mac hardware, unsurprisingly, the ipmi_si module fails to load and the ipmi device is not created. Motherboards with issues supporting on the PC probably explain the similar errors reported at..."
1797791,2018-10-26 10:21:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797791,2020-04-04 18:43:57 UTC,"I can confirm, on a 2008 MacPro with Apple ROMed GTX680, that the nvidia 440 drivers bundled with the 20.04 beta release show the same behavior. The Apple Cinema HD display LED comes on (indicating that the driver loses contact with the display) as nvidia drivers are loaded and nvidia-modeset executes."
1797791,2020-04-11 02:00:17 UTC,I can also confirm that the nvidia-340 package in 20.04 builds usable kernel modules and works fine on the same 2008 MacPro with Mac rom'd GTX680.
1797795,2018-10-20 13:38:02 UTC,FileNotFoundError: [Errno 2] No such file or directory: '/home/popalex/mysnaps/hello/prime/bin/hello'
1797798,2018-10-22 21:05:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797799,2019-03-01 00:14:09 UTC,"@Pointhi that's pretty cool
Do you know if the C-PCB autorouter is usable (at all) for more complex boards?"
1797799,2018-10-14 20:16:39 UTC,See also lp:1290022
1797799,2019-02-23 18:39:09 UTC,"As some experiment, I made a prototype integration of https://github.com/vygr/C-PCB into KiCad:"
1797799,2019-03-01 00:23:06 UTC,I can easily benchmark it against frerouting if somebody uploads some sample spectra DSN.
1797801,2018-11-22 11:46:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797802,2018-10-21 13:10:33 UTC,I collected some perf data for further analysis.
1797802,2018-10-21 13:11:36 UTC,Perf data collected for the run above.
1797802,2018-10-21 13:16:54 UTC,"Temperatures:
Before the performance drop: up to 97 C
After performance drop: 52-55 C"
1797802,2019-01-18 11:21:45 UTC,"dimahetman (dimahetman),
please also try as described in #18."
1797802,2018-10-21 19:38:15 UTC,"Can you reassign this bug to thermald package?
Or should I create a new one?
Thanks"
1797802,2018-11-15 21:19:12 UTC,"This is of course ridiculous, but I have an inverse problem I have a big problem with thermal throttling In topic #1598394."
1797802,2018-10-21 13:04:07 UTC,More observations:
1797802,2018-10-21 18:58:51 UTC,Disabling thermald with:
1797802,2018-10-15 07:42:08 UTC,"And as soon as I hit ""rebuild project"" in the IDE, the frequencies go immediately down from 2.8 GHz to about 1.2-1.5 GHz now."
1797802,2019-01-18 11:18:20 UTC,"try running thermald in a window from command line.
systemctl stop thermald
#thermald --no-daemon --loglevel=info"
1797802,2018-10-15 07:35:24 UTC,The problem exists in 4.19.rc7 I just tried.
1797802,2018-10-15 07:04:54 UTC,"Is it normal that C-states percentages reported by i7z don't sum up to 100%, but exceed it?
Under load, I frequently get C0% close to 99%, but at the same time Halt is at about 40-60%.
Also when C0 is >90, the frequency of cores goes DOWN. This looks totally reversed to me."
1797802,2018-10-15 06:31:34 UTC,"Update: I got the ""package temperature above threshold"" again (still using 4.18.0-10 kernel), but it did not cause visible performance loss and i7z still shows the CPU freq can go up to ~3.8 GHz easily. So maybe these messages are not related."
1797802,2018-10-15 06:25:11 UTC,"> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
"
1797802,2018-10-14 20:31:58 UTC,"Aaaah, I can see plenty of this in syslog:"
1797802,2018-10-14 20:30:41 UTC,"BTW, when the system is in this weird state, CPU fans are running at the lowest speed (but running) and never go to their max speed, even under heavy CPU load like compiling stuff."
1797802,2018-10-14 20:29:53 UTC,Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
1797802,2018-10-15 07:40:15 UTC,"Huh, another surprise. After running my infinte loop for the time I wrote the previous post, suddenly it ""magically"" fixed itself and now one core reports 100% C0 and ~6% C1, temperature 57, voltage 0.94. The frequency did not go above 2.8 GHz, though."
1797809,2018-10-24 14:05:16 UTC,This is really a bug in the somewhat old version of the Haskell HTTP library present in xenial's version of cabal-install:
1797809,2018-10-24 16:31:46 UTC,"Hmm, it doesn't actually seem to be just that, although the symptoms are extremely similar.  xenial's haskell-cabal-install was built against libghc-http-dev 1:4000.2.20-3, and the bug above was fixed in HTTP 4000.2.11.  The current issue is in fact:"
1797809,2018-10-25 05:11:59 UTC,I tried a number of workarounds:
1797811,2019-10-30 12:47:09 UTC,"@James - Apologies for the delayed response, it took me a while to track this down. I believe that the fix was https://review.opendev.org/#/q/I0f699c9869effc5ccc0d3f79422935975f698134 in OSA. If you're using an older environment than one with that present, you could implement that patch. IIRC it was not applicable to anything Queens and before - it was only a Rocky bug which was fixed in 18.0.3/Rocky and pre-release for Stein."
1797811,2019-04-15 19:14:19 UTC,could we please have some direction as to where and what the bug and the fix is? is it something that can be applied in place to an working older environment?
1797811,2019-03-02 12:47:54 UTC,"@James For OSA, this was fixed in release 18.1.3 - so you can use that or anything later."
1797811,2019-03-02 08:38:11 UTC,"sorry, but I would have the very same ""naive question"" ... Thx Harry"
1797811,2019-02-14 18:21:24 UTC,"sorry for the naive question. if the last comment says ""fix released"" does that mean there is a fix I can find somewhere? I would like to test this in my environment. thanks!"
1797811,2018-12-05 20:27:47 UTC,codylab suggested i might have a very similar issue.
1797811,2019-02-12 11:34:26 UTC,Fixed in OSA and release in 18.1.3
1797814,2019-11-27 13:30:20 UTC,"Hi Mark, I would recommend removing the control codes, it will break anytime you pipe stdout or stderr to from_json to get the changed status."
1797814,2019-12-09 11:27:18 UTC,Raised a separate bug for the control code issue: https://bugs.launchpad.net/kolla-ansible/+bug/1855701
1797814,2019-11-25 13:23:33 UTC,"That's good information Rowan, we do see some odd failures during this task. I did a little googling and ^]]00m is an escape character for terminal colour control that should reset the attributes to normal. Perhaps we need to remove the control codes from the output?"
1797814,2019-11-25 12:00:08 UTC,"Sorry - minor correction to my previous statement, it's an escape character (^[) not a NULL character.
I tested piping the same file.txt through a tr command to remove non-printable characters:"
1797814,2019-11-25 11:43:33 UTC,"Hi, we have hit this issue using kolla-ansible 8.0.1 (installed from pip) as well as the `stable/stein` branch when deploying using the git repository."
1797814,2019-11-11 15:40:07 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1797814,2019-09-09 09:18:05 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.2 release.
1797814,2019-09-09 09:17:12 UTC,This issue was fixed in the openstack/kolla-ansible 6.2.2 release.
1797814,2019-08-02 13:29:31 UTC,"Reviewed:  https://review.opendev.org/670548
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=441c5a03f7e788336f3a7c1cb15dcec207073b07
Submitter: Zuul
Branch:    stable/rocky"
1797814,2019-08-02 09:55:40 UTC,"Reviewed:  https://review.opendev.org/670549
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=8e219a91738048ff16f2caed4c24f85832211aad
Submitter: Zuul
Branch:    stable/queens"
1797814,2019-07-18 00:37:21 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc2 release candidate.
1797814,2019-07-16 14:10:15 UTC,"Reviewed:  https://review.opendev.org/670546
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d62e927dacfa42822296e7a0720cb85019c08a9b
Submitter: Zuul
Branch:    stable/stein"
1797814,2019-07-12 13:10:23 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/670546"
1797814,2019-07-12 13:11:26 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/670548"
1797814,2019-07-12 11:57:32 UTC,"Reviewed:  https://review.opendev.org/650962
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d5e5e885d11e338806425839a361d868c1f4ff10
Submitter: Zuul
Branch:    master"
1797814,2019-07-01 14:01:28 UTC,"A manual workaround (truncated in post above) is to run the db_sync manually for the failed service, eg:"
1797814,2019-07-01 13:15:00 UTC,The problem is this:
1797814,2019-07-01 13:05:31 UTC,"I see something very similar to this on a three node deploy, in stein and in master."
1797814,2018-11-23 07:38:55 UTC,"Any news on that?
I'm seeing the same when tying to deploy rocky."
1797814,2018-10-15 00:58:45 UTC,I ran the docker command directly on the host so I could get clean output and it looks like this (the first few lines out of hundreds):
1797814,2018-10-15 00:38:47 UTC,"After reviewing a bit more - the SQL error above is ""expected"", indicating that the role already exists.  And thus the ""failed"" return value, in the JSON response, should be ""true""."
1797814,2018-10-15 00:18:34 UTC,It looks like the failure is caused by this SQL statement error (please forgive the lack of spaces - due to a JSON formatter):
1797814,2018-10-14 23:57:39 UTC,"I missed that the ""failed_when"" line was referring to the ""register"" variable in this task - so it is NOT related to the bootstrap.yml file I mentioned."
1797814,2019-07-12 13:23:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/670549"
1797820,2019-06-10 15:58:06 UTC,Maybe this update corriga this error:
1797820,2019-01-16 04:53:19 UTC,Setting to Medium importance due to the low/moderate number of crash reports on errors.ubuntu.com
1797820,2019-01-16 04:48:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797829,2020-04-28 16:31:34 UTC,This bug was fixed in the package kdocker - 5.3-1
1797833,2018-10-15 16:35:58 UTC,Thanks for reporting.
1797836,2019-08-14 01:20:35 UTC,This bug was fixed in the package logwatch - 7.4.3+git20161207-2ubuntu1.1
1797836,2019-08-13 19:13:50 UTC,My current version is as shown below and so far I have not seen the false positive with it
1797836,2019-08-13 13:10:45 UTC,Thanks for the feedback @fomember! Could you please update the bug tags according to the instructions in comment #9? It would also be appreciated if you could be explicit about the package that you have been testing. An apt-cache policy <package> output should be enough.
1797836,2019-08-12 10:37:22 UTC,I am running the proposed package for about a week now and so far I did not see any problems and the false kernel error warning is gone.
1797836,2019-08-14 01:20:40 UTC,"The verification of the Stable Release Update for logwatch has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1797836,2019-07-30 20:52:15 UTC,"Hello latimerio, or anyone else affected,"
1797836,2019-07-30 03:08:42 UTC,"Package is merged and uploaded, next step will be SRU team verification."
1797836,2019-08-01 11:41:54 UTC,"I did enable the proposed package and did an   apt update
apt search logwatch   doesn't show any proposed package yet though.
P.S. I am on a headless system."
1797836,2019-07-24 20:57:46 UTC,"Merge proposal for review:
- bionic: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/370585"
1797836,2019-07-18 17:58:29 UTC,Dropping cosmic task since cosmic reached end of support this month.
1797836,2019-06-18 19:24:33 UTC,"Looks like it needs this patch, from 1 Jun 2018.  Looks like it is included in 7.5.0 (which disco and eoan are shipping) but not in 7.4.3+git20161207, which bionic and cosmic have."
1797836,2018-12-09 08:15:13 UTC,"It is really annoying when you see error messages which are in fact no errors.
Either the name of the service should be changed or logwatch should filter this false positive.
A tool which should make the admin aware of things must do every effort to avoid obfuscating real errors."
1797836,2018-10-17 20:00:28 UTC,Thanks for filing this bug in Ubuntu.
1797836,2019-07-29 09:27:22 UTC,"Since it is in >=Disco I set the main task to ""Fix Released"""
1797840,2018-10-15 09:41:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1797840,2018-12-03 13:10:16 UTC,How long is the event? Is it only 10 minutes? If so that's a known upstream issue than short event are not well displayed on the week view
1797840,2018-12-07 16:02:42 UTC,"Yes, even 15 minutes"
1797840,2018-12-07 16:20:57 UTC,"Thx, It's the same as https://gitlab.gnome.org/GNOME/gnome-calendar/issues/180"
1797842,2019-02-28 16:12:19 UTC,"Yes, nova-lxd doesn't delete the images that were fetched to the compute-node when no instances are using those images.  It would be necessary to hook into the clean-up function when an instance is deleted to find out of the image is being used by any other instance and then remove it; we'd probably need to take a lock early in the deletion process to prevent a race with another instance being created with the same instance."
1797848,2020-01-13 03:14:57 UTC,https://github.com/juju/juju/pull/11096
1797848,2020-01-09 03:36:26 UTC,"@thumper - yes, having the healthcheck off the same port is fine (if not beneficial) - this way we're testing the same TCP socket, the same TLS connection, etc. The main thing is that this end point does not require authentication (or if it does, it is simple, like a shared secret)."
1797848,2019-12-13 01:43:18 UTC,"There seems to be some misunderstanding around the requirements for this - this specific bug is about providing a healthcheck end point that indicates whether or not a particular Juju controller can receive and process API requests. In the case where Juju controllers are fronted with a load balancer (e.g. haproxy), we need the ability to determine if the load balancer should send traffic to a controller."
1797848,2019-12-18 02:49:40 UTC,"@jsing, does it make sense to hang the health check off the same port?"
1797848,2019-12-11 14:25:29 UTC,See duplicates for details like
1797848,2018-10-15 12:55:45 UTC,"Thanks, I've added this to the field doc for planning ideas for 19.04."
1797848,2019-12-11 18:27:04 UTC,"From an ops perspective, without an endpoint like this we have no means to know if Mongo is healthy which can lead to split-brain later on (and resulting data loss), if the replicaset is out of sync."
1797857,2018-10-15 09:07:11 UTC,"Sorry, this is actually a bug in python3-tzlocal."
1797857,2018-11-10 11:09:43 UTC,I submitted a pull request to fix this bug: https://github.com/regebro/tzlocal/pull/68
1797857,2019-06-20 14:38:05 UTC,This is fixed in 2.0.0b2
1797859,2018-10-17 07:29:50 UTC,"any idea to get it fixed?
I'm afraid I'm not the only one user with this BS issues after the upgrade..."
1797859,2018-10-17 16:37:08 UTC,Soved! :
1797859,2018-10-17 17:12:06 UTC,"Unbelievable Jörg :))
I think it has helped really.
The printer has printed again after a break of ca. 3days!!!
I thank you so much!
Going to wait for the upgrade to current 18.9 - for now never change a running system LOL
Have a nice evening from Germany!"
1797859,2018-10-17 17:31:51 UTC,Fine!
1797859,2018-10-17 18:50:47 UTC,"> Unbelievable Jörg :))
"
1797859,2018-10-18 07:14:25 UTC,"Hi Brain and Jörg
from my perspective all of activities are valuable for the community many thanks again to you Brian as my first guide ;)
Apart from that it could be helpful to include a shortened final solution in the knowledge base and probably link the current defect to the topic. It could avoid redundant defects and could help other users with similar issues."
1797859,2018-10-18 04:02:32 UTC,Apologies. I was a little grumpy. And you did indeed help.
1797859,2018-10-18 08:21:46 UTC,"@Brian
after your #15-comment I thought you're done with this defect as you wrote:"
1797859,2018-10-18 19:04:22 UTC,"@Kourosh
Again, I apologise for my grumpiness and add that you, of course, were entitled to take the view you did. My view would be that the log might have helped Srinivas even if I had dropped out of the conversation."
1797859,2018-10-17 07:14:18 UTC,"many thx Brian
as Srinivas have changed the status of the defect to ""In Progress"" I guess he is going to follow up.
Have never had such strange issues for a simple matter with Linux/Ubuntu... sad :("
1797859,2018-10-17 20:37:05 UTC,"Hi Brian,"
1797859,2018-10-16 22:15:39 UTC,I am ceasing to support searching for a solution to this probem.
1797859,2018-10-15 13:50:07 UTC,"> Hey Brian
"
1797859,2018-10-16 18:16:57 UTC,"Hi,
I had installed HPLIP-3.18.9.
I'm processing its uninstall during the installation of your suggested version 18.6."
1797859,2018-10-16 12:16:25 UTC,"Hi,"
1797859,2018-10-16 08:34:34 UTC,A filter has failed and the last 5 jobs have been held in a queue. An error_log will tell you which filter failed or you could do (as root)
1797859,2018-10-15 18:30:32 UTC,"lpstat -t
Zeitplandienst läuft
systemvoreingestelltes Ziel: test
Gerät für Epson_Stylus_Office_BX630FW: ipp://EPSON620832.local:631/Epson_IPP_Printer
Gerät für HP_Color_LaserJet_CP1215: hp:/usb/HP_Color_LaserJet_CP1215?serial=LJ20TGN
Gerät für test: hp:/usb/HP_Color_LaserJet_CP1215?serial=LJ20TGN
Epson_Stylus_Office_BX630FW akzeptiert anfragen seit Mo 15 Okt 2018 13:51:38 CEST
HP_Color_LaserJet_CP1215 akzeptiert anfragen seit Mo 15 Okt 2018 17:04:25 CEST
test akzeptiert anfragen seit Mo 15 Okt 2018 17:11:48 CEST
Drucker Epson_Stylus_Office_BX630FW ist im Leerlauf.  Aktiviert seit Mo 15 Okt 2018 13:51:38 CEST
Drucker HP_Color_LaserJet_CP1215 ist im Leerlauf.  Aktiviert seit Mo 15 Okt 2018 17:04:25 CEST
Drucker test ist im Leerlauf.  Aktiviert seit Mo 15 Okt 2018 17:11:48 CEST
 Filter failed
test-2047               kourosh          19456   Mo 15 Okt 2018 17:06:24 CEST
test-2048               kourosh           1024   Mo 15 Okt 2018 17:09:02 CEST
test-2049               kourosh           1024   Mo 15 Okt 2018 17:10:15 CEST
test-2050               kourosh           1024   Mo 15 Okt 2018 17:11:13 CEST
test-2051               kourosh           1024   Mo 15 Okt 2018 17:11:48 CEST"
1797859,2018-10-15 15:47:06 UTC,This sounds more and more like a CUPS problem.
1797859,2018-10-15 15:12:45 UTC,"ok, have tried:"
1797859,2018-10-15 14:17:20 UTC,You have
1797859,2018-10-15 14:03:10 UTC,"additional hint:
Scanning with ""Epson BX630FW"" works without any issues"
1797859,2018-10-15 11:39:32 UTC,"Your error_log doesn't show any job arriving at the CUPS server. You also say you cannot print to a Epson BX630FW. At first sight, this looks like a CUPS problem, not an HPLIP problem. Try this:"
1797859,2018-10-16 18:32:26 UTC,unfortunately without any changes :( s. attach
1797860,2018-10-22 09:19:38 UTC,"Yeah, sorry that we had different terms for the same things :) Ok, I understand now as well. I'm trying to look at this whole thing globally and not from the technical split (which is a little bit artificial) that we did."
1797860,2018-12-03 08:58:04 UTC,"Hey Gunnar,"
1797860,2018-10-22 19:46:29 UTC,"On 2018-10-22 11:19, Didier Roche wrote:> Gunnar Hjalmarsson wrote:

>> Please note that the language-options script serves the purpose of
>> providing a list of languages only, i.e. it let's the user select
>> the display language. That should be distinguished from selecting
>> the locale for regional formats. For the latter purpose the user is
>> offered an option list consisting of all the generated UTF-8
>> locales.
>
> I'm unsure to understand this split; but that's probably due to my
> inexperience.
"
1797860,2018-10-17 06:14:51 UTC,"When you are telling that you select French, or English, and so, all dialects should be installed for them, why do we have that separation in different packages though? Shouldn't we only have one ""English"", ""French"", … package?"
1797860,2018-10-20 21:26:52 UTC,"On 2018-10-17 08:14, Didier Roche wrote:

> When you are telling that you select French, or English, and so, all
> dialects should be installed for them, why do we have that separation
> in different packages though? Shouldn't we only have one ""English"",
> ""French"", … package?
"
1797860,2018-10-16 07:43:54 UTC,I think we should answer some questions first in term of fundamentals.
1797860,2018-10-15 15:55:35 UTC,"Hey Didier,"
1797860,2018-10-17 00:42:33 UTC,I think we need to distinguish between what's installed and what the language-options script outputs.
1797861,2018-10-15 12:50:33 UTC,"ok, then I'm sorry but I guess we're seeing different things"
1797861,2018-10-15 10:07:20 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1797861,2018-10-15 12:08:03 UTC,It seems to be due to it being root here; can you confirm that? e.g. 'sudo gedit' also is not read.
1797861,2018-10-15 12:35:05 UTC,I verified in Bionic and this is a new problem in Cosmic.
1797861,2018-10-15 12:45:41 UTC,"""sudo gedit"" works fine and the screen reader reads the UI and what I type."
1797861,2018-10-15 13:53:52 UTC,additionally I just tried with a UEFI system booting from today's ISO to a live session and it seems to work OK; comment #3 happened in an ISO that I booted from maybe-ubiquity in virt-manager/kvm.
1797861,2018-10-16 13:26:18 UTC,"Confirm what Iain is seeing, in maybe-ubiquity mode with kvm, if you select then the live session."
1797861,2020-10-13 10:38:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797861,2020-10-13 10:42:33 UTC,Confirming this bug with today's groovy (20.10) daily image (20201013.1).
1797862,2018-10-16 14:30:54 UTC,if you try to tweak it through upower/desktop controls it could be bug #1796550
1797862,2018-10-16 14:50:29 UTC,"No,I don't have any /sys/class/leds/*::kbd_backlight* folder."
1797862,2018-11-24 13:24:44 UTC,Bug #1791372 was fixed by update in Bug #1796550
1797862,2018-10-15 17:27:25 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1797862,2018-11-06 04:23:27 UTC,Maybe merge with bug 1791372?
1797862,2018-10-15 10:22:46 UTC,"No,it's not useful.And I tried acpi_listen,still no output when i press Fn+Down"
1797862,2018-10-15 10:10:16 UTC,"^^^
You also need to reboot after changing that."
1797862,2018-10-15 10:09:35 UTC,Does changing your upower.service file fix the problem?
1797862,2018-10-15 09:53:55 UTC,"Yes,maybe these are two bug.Fn keys doesn't work and unable to control keyboard backlight.
But I can control the screen brightness via the top-reight control panel."
1797862,2018-10-15 09:44:10 UTC,Although if /sys/class/leds/*kbd* is missing then that's certainly a separate bug to the screen backlight problem.
1797862,2018-10-15 09:41:28 UTC,Oh. Actually they might be the same bug if the problem is broken kernel support for your Asus control keys.
1797862,2018-10-15 09:40:17 UTC,"These would be two different bugs:
  * Cannot turn off keyboard backlight.
  * Unable to control screen brightness via fn keys"
1797866,2018-10-15 09:46:03 UTC,oui installation neuve
1797867,2018-10-15 10:12:00 UTC,apport information
1797867,2018-10-15 10:10:08 UTC,apport information
1797867,2018-10-15 10:10:11 UTC,apport information
1797867,2018-10-15 10:10:14 UTC,apport information
1797867,2018-10-15 10:11:52 UTC,apport information
1797867,2018-10-15 10:11:53 UTC,apport information
1797867,2018-10-15 10:11:56 UTC,apport information
1797867,2018-10-15 10:11:58 UTC,apport information
1797867,2018-10-15 10:10:07 UTC,apport information
1797867,2018-10-15 10:12:01 UTC,apport information
1797867,2018-10-15 10:10:05 UTC,apport information
1797867,2018-10-15 10:12:04 UTC,apport information
1797867,2018-10-15 10:12:05 UTC,apport information
1797867,2018-10-15 10:12:08 UTC,apport information
1797867,2018-10-15 10:12:10 UTC,apport information
1797867,2018-10-15 10:12:11 UTC,apport information
1797867,2018-10-15 10:12:15 UTC,apport information
1797867,2018-10-15 10:12:17 UTC,apport information
1797867,2018-10-15 17:26:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1797867,2018-10-16 12:34:00 UTC,"ok,upgraded
acpi_listen outputs nothing.
And my nvidia doesn't work now,uh."
1797867,2019-04-11 07:59:28 UTC,Does this issue still happen?
1797867,2018-10-15 10:12:03 UTC,apport information
1797867,2018-10-15 10:10:03 UTC,apport information
1797867,2018-10-15 10:09:57 UTC,apport information
1797867,2018-10-15 10:10:00 UTC,apport information
1797867,2018-10-15 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797867,2018-10-15 10:07:13 UTC,apport information
1797867,2018-10-15 10:07:16 UTC,apport information
1797867,2018-10-15 10:07:18 UTC,apport information
1797867,2018-10-15 10:07:20 UTC,apport information
1797867,2018-10-15 10:07:21 UTC,apport information
1797867,2018-10-15 10:07:23 UTC,apport information
1797867,2018-10-15 10:07:24 UTC,apport information
1797867,2018-10-15 10:07:26 UTC,apport information
1797867,2018-10-15 10:07:27 UTC,apport information
1797867,2018-10-15 10:10:02 UTC,apport information
1797867,2018-10-15 10:07:31 UTC,apport information
1797867,2018-10-15 10:07:32 UTC,apport information
1797867,2018-10-15 10:07:36 UTC,apport information
1797867,2018-10-15 10:07:40 UTC,apport information
1797867,2018-10-15 10:09:49 UTC,apport information
1797867,2018-10-15 10:09:50 UTC,apport information
1797867,2018-10-15 10:09:54 UTC,apport information
1797867,2018-10-15 10:09:55 UTC,apport information
1797867,2018-10-15 10:09:59 UTC,apport information
1797867,2018-10-15 10:07:29 UTC,apport information
1797868,2018-10-15 11:07:30 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1797878,2020-06-07 22:56:50 UTC,"Solution #4 https://bugs.launchpad.net/kazam/+bug/1500083 work for me!!!!, on debian 10.
DEBUG Kazam - Starting ...
DEBUG Kazam - Running on: debian 10.4
DEBUG Kazam - Kazam version: 1.4.5 NCC-80102
DEBUG Prefs - XDG_PICTURES is a directory and accessible
DEBUG Prefs-HW - Getting hardware specs
DEBUG Prefs-HW - Getting Video sources.
DEBUG Prefs-HW - Found 1 monitor(s).
DEBUG Prefs-HW -   Monitor 0 - X: 0, Y: 0, W: 1366, H: 768
DEBUG Instant - Setting variables./usr/share/kazam/
DEBUG Grabber - Starting Grabber.
DEBUG Grabber - Grabber source: 0, 0, 1366, 768
DEBUG Instant - Grabbing screen
Failed to play sound: Sound disabled
DEBUG Grabber - Coordinates     X 0  Y 0  W 1366  H 768
DEBUG Grabber - Adding cursor.
DEBUG Grabber - Cursor coords: 546 303"
1797878,2020-02-07 13:40:50 UTC,These two workarounds enabled a build & install from kazam 1.4.5 tarball on Fedora
1797878,2020-02-05 20:07:49 UTC,"Ditto comments #1 & #2
=="
1797878,2020-05-07 10:21:01 UTC,Solution #4 https://bugs.launchpad.net/kazam/+bug/1500083 does not work for me on a fresh Ubuntu Focal 20.04 install with Kazam version (1.5.3-0ubuntu3) installed.
1797878,2020-01-13 01:53:50 UTC,i have also the same bug under fedora 32 (rawhide)
1797878,2020-01-13 02:01:07 UTC,but downloaded and installed with kazam-1.4.5.tar.gz
1797880,2018-10-15 11:32:07 UTC,"I had also sent bug report to Debian, but it's still not processed yet."
1797881,2018-11-02 09:31:48 UTC,The commits are headed upstream and tagged with appropriate tags to be backported to stable kernels. Please let us know if the fixes don't show up in v4.18 in a few weeks.
1797881,2018-10-16 07:21:45 UTC,Is it possible for you to find the first bad 4.19-rc* kernel in [1]?
1797881,2018-10-20 19:37:42 UTC,I think the same applies for the upcoming 4.19 as well.
1797881,2018-10-20 19:35:42 UTC,this is actually an issue on the 4.18.8 and newer.
1797881,2018-10-17 11:01:31 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=108083
1797881,2018-10-17 10:44:43 UTC,"it seems this commit is causing the problem
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/intel_dp.c?id=399334708b4f07b107094e5db4a390f0f25d2d4f"
1797881,2018-10-17 09:07:25 UTC,"rc2 is fine, rc3 has the problem"
1797881,2018-10-23 11:28:57 UTC,"(In reply to Karol Herbst from comment #4)

> this is actually an issue on the 4.18.8 and newer.
>
> Those commits need to be applied to 4.18 to fix this regression:
>
> 9ebd8202393dde9d3678c9ec162c1aa63ba17eac
"
1797881,2018-10-15 18:41:02 UTC,same problem with linux-image-unsigned-4.19.0-041900rc8-generic
1797881,2018-10-15 14:38:11 UTC,Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
1797881,2018-10-15 11:30:06 UTC,This change was made by a bot.
1797881,2018-10-03 07:12:12 UTC,Thankyou for your feedback. I will resolve this bug as worksforme.
1797881,2018-10-02 16:30:23 UTC,"I re-tested on latest drm/drm-intel (without patch), this issue is not exist."
1797881,2018-10-02 05:58:02 UTC,"Shun, Can you apply following path and test if the issue is still existing?
(https://bugs.freedesktop.org/attachment.cgi?id=141229)."
1797881,2018-09-27 07:36:16 UTC,"Created attachment 141757
full dmesg"
1797881,2018-10-15 15:04:46 UTC,"linux-image-4.18.0-7-generic has no problem
linux-image-4.18.0-10-generic has problem"
1797882,2019-09-18 19:41:27 UTC,-- GitLab Migration Automatic Message --
1797882,2019-07-28 22:18:49 UTC,"Unfortunatelu no new flavor of Ubuntu is supporting 32 bits anymore.
Therefore I had to install Debian 10 (Buster)."
1797882,2019-07-22 04:04:36 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1797882,2019-02-19 23:46:01 UTC,"Created attachment 143415
libdrm_ignore_deadlock"
1797882,2019-02-19 23:43:09 UTC,"Created attachment 143414
fix intel_blit.c"
1797882,2019-02-19 23:39:44 UTC,"Some more investigation, understanding and adding 2 other possible fixes for the problem.
The problem occurs at Ubuntu 18.10 only at gdm3 with wayland using dual monitor.
It is not occuring with wayland at single monitor.
It totally doesnot occur if gdm3 is not using wayland.
At ubuntu 18.04 the same problem exists with wayland, but is not occurring so often."
1797882,2019-01-26 10:52:47 UTC,"Created attachment 143231
libdrm-patch"
1797882,2019-01-26 10:50:53 UTC,"I am using intel i915 gen 3 with 16 fence registers.
When displaying the variable total_fences
at function drm_intel_gem_check_aperture_space at libdrm-2.4.95/intel/intel_bufmgr_gem.c,
it is seen that the deadlock-abort is occurring at total_fences == 16,
where the previous display shows total_fences == 14,
so there is an increment of 2 fences in stead of the usual increment of 1.
Apparently the deadlock occurs at the ""freeing fences phase"", that is started if total_fences is too high.
I decided to lower the available_fences from 14 to 13 (see proposed patch).
This solved the problem.
After this patch I still saw sometimes total_fences == 16,
where the previous display shows total_fences == 13, so there is an increment of 3 fences. This did not cause a deadlock at the ""freeing fences phase""."
1797882,2019-07-28 22:43:01 UTC,"I am currently using Debian 10 Buster with Wayland.
This problem is not existing anymore at this release.
Wayland no longer uses an extra fence register if dual monitor is used."
1797882,2018-12-19 14:34:18 UTC,"Mesa-bug:
https://bugs.freedesktop.org/show_bug.cgi?id=109102"
1797882,2018-12-19 14:31:37 UTC,"Created attachment 142856
ubuntu-cogl-patch"
1797882,2018-12-19 14:29:06 UTC,"Created attachment 142855
stacktrace"
1797882,2018-12-19 01:31:57 UTC,"Gert,"
1797882,2018-12-18 20:22:05 UTC,"The attachment ""dirty_patch.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1797882,2018-12-18 16:25:16 UTC,Trace
1797882,2018-12-18 16:20:39 UTC,"Without solving this problem, wayland cannot be used after logon, when using dual monitor. The sesssion stops very easy and often. Work is lost; you have to logon again. E.g. the simple switching between 2 overlapping windows causes the end of the session."
1797882,2018-12-19 14:35:07 UTC,-EDEADLOCK = userspace tried to use more fence registers than the HW supports.
1797883,2018-10-16 14:06:14 UTC,"Thanks for your report. Could you share what version of Ubuntu you're using (or, if you're not using Ubuntu, what distribution/version), the version of indicator-stickynotes, and a screenshot, if possible?"
1797883,2018-10-17 12:10:26 UTC,"Yes, sure. I'm using Ubuntu 16.04 LTS and indicator-stickynotes' is 1.0.0. I cannot show the issue in a screenshot 'cause it doesn't appear. sorry."
1797883,2019-04-02 06:14:07 UTC,"I am facing similar issue on Ubuntu 16.04 LTS 1.0.0. Is there any workaround available ?
Thanks"
1797883,2019-04-23 14:52:41 UTC,Can confirm. I am also having this issue on:
1797886,2018-12-11 18:51:11 UTC,Confirmed that currently (master) you can only associate one request per line item.  This would be a good enhancement for this feature.
1797888,2018-10-15 16:22:51 UTC,"It's not just the icon that's missing, the menu entries don't do anything. But in this regard the deb package seems to be affected too, so it's not snap-specific."
1797888,2018-10-15 16:23:54 UTC,See also bug #1769736.
1797897,2018-10-15 18:31:17 UTC,I realized in IRC I failed to explain properly what happens here.
1797897,2018-10-15 18:33:24 UTC,"This sounds like a good idea to me. I can understand that nginx upstream might not want this as a default because it sounds like it'll burn memory in structures, but it sounds wonderful for a general purpose distribution with a variety of users who all want something slightly different out of their webserver."
1797897,2018-10-15 18:33:59 UTC,"Note that for Ubuntu, this will not be done for Cosmic - we are too late in the dev cycle to do this for Cosmic, so any changes to this which would add this to the Ubuntu packages will be for D-series (whatever it is named).  This needs discussed first, however, before it gets included in the Ubuntu Repositories' versions of NGINX."
1797897,2018-10-16 11:20:35 UTC,"> ...as to whether we want users to be able to dynamically compile and include extra modules outside of the binaries we ship already.
"
1797897,2018-10-16 13:44:56 UTC,We are too close to Cosmic release to get this into Cosmic (Won't Fix'd for Cosmic).  This will be included in the D-series cycle for Ubuntu.
1797897,2018-10-17 13:31:47 UTC,"Mainline PPA packages are building with --with-compat in the staging PPA, if all goes well I'll copy it over to the actual Mainline PPA."
1797897,2018-10-17 13:43:37 UTC,"Stable PPA packages are now building with --with-compat in the staging PPA, they'll be copied over if all goes well to the main Stable PPA as well."
1797897,2018-10-17 14:05:18 UTC,PPAs now have --with-compat enabled.  Updated packages are copying in from the staging PPAs now.
1797897,2018-11-13 15:20:36 UTC,"A packaging change containing the --with-compat change has been committed to disco-proposed, along with security patch fixes via the newer nginx version for bugs #1801982 and #1801983."
1797897,2018-11-15 07:12:48 UTC,This bug was fixed in the package nginx - 1.15.6-0ubuntu1
1797915,2019-11-28 14:49:23 UTC,did it fix by itself in the meantime?
1797915,2020-01-28 04:17:22 UTC,[Expired for sssd (Ubuntu) because there has been no activity for 60 days.]
1797920,2018-12-17 12:22:43 UTC,Cannot run the app:
1797920,2019-04-03 14:17:23 UTC,The Linux version from their website http://www.sweethome3d.com https://sourceforge.net/projects/sweethome3d is basically a Java application and ofcourse that is running without any (c/c++) errors.
1797920,2019-03-01 16:36:07 UTC,Is there a workaround (with apt-get) to start sweethome3d on 18.10?
1797920,2018-12-13 01:29:25 UTC,The sweethome3e you get from the snap is version 5.7.
1797920,2019-02-13 09:22:26 UTC,Same here:
1797920,2018-10-20 01:56:53 UTC,Specs:
1797920,2018-10-20 01:09:44 UTC,Caused by recent upgrade of the openjdk-lts source. Numerous (100+) undefined symbol errors
1797920,2018-10-15 16:34:05 UTC,"Problem seems due to some recent update. as you can see from the attached terminal output sweethome start ok before updates, then i run apt update+upgrade and after upgrades sweethome does not start."
1797920,2018-11-03 08:19:14 UTC,"After installing the newest snap, sweethome3d runs again.
Used sudo snap install sweethome3d-homedesign to install it."
1797921,2018-10-15 16:03:47 UTC,Have a proposed pull-request upstream that needs verifying and known issues resolving
1797932,2018-10-15 17:13:34 UTC,"@adconrad - ack. Just a comment -  This time there was less than a month between installing this bionic instance, doing the sru test and then reverting - so I had at least some recollection of what went on. If it had been 3 years - I'd have no chance and would wonder what was going on. I guess I'd always assumed that reverting uninstalled - I knew it didn't remove the package(s) though."
1797932,2018-10-15 16:47:10 UTC,"To be clear, nvidia was never removed, as far as I can tell, but it was installed and then nouveau selected as the default.  So, the upgrade upgraded nvidia (which is fine), but then the default became nvidia again."
1797932,2018-10-15 16:41:31 UTC,Attaching logs from /var/log/dist-upgrade
1797941,2018-10-21 13:57:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797942,2019-10-16 19:55:39 UTC,I've just tested this with a PostgreSQL db and looks good to me! Candidate snap promoted to stable.
1797942,2018-11-28 17:17:20 UTC,Is there any progress on the inclusion of postgress DB drivers to be in the snap?
1797942,2018-12-10 19:20:28 UTC,I think it is important to add postgresql drivers.
1797942,2019-10-13 04:05:21 UTC,I've just installed the LO snap (6.3.2.2-snap1).
1797942,2019-10-15 15:45:38 UTC,"Hi John (or anyone else affected by this), could you please install the candidate LibreOffice snap and let me know if PostgreSQL connections work now?"
1797942,2019-10-16 08:20:38 UTC,Hallo Marcus
1797943,2018-12-02 13:59:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797945,2018-10-18 12:26:24 UTC,Where do I put the .xpi file to be recognized by Thunderbird?
1797945,2018-10-18 17:22:05 UTC,@Adrian Limmi:
1797945,2018-10-18 19:15:39 UTC,It worked like a charme. Thank you!
1797945,2018-10-19 07:53:54 UTC,"As defined it is not invalid, because it _is_ a Bug.
It will be resolved later, when a compatible Version of Lightning will be made available at Thunderbird-Add-On-Search.
(I could not chose ""Won't fix"")
So i changed its Status to ""In Progress"""
1797945,2018-10-19 08:02:50 UTC,"It's a bug but not in Ubuntu, which is what this bug tracker is about"
1797945,2018-10-19 08:08:20 UTC,"It _is_ a Bug in Ubuntu, because they do not deliver the Standard-Thunderbird-Version with Lightning includes.
It _is_ a Bug in Ubuntu, because Ubuntus xul-ext-lightning is english-only and not international (localized).
A compatibel Release-Version of Lightning is already available, it is just, that Ubuntu does not include it or offer it."
1797945,2018-10-19 08:17:57 UTC,"I have to correct myself:
I think, this is a Bug, Ubuntu should care about immediately, because it breaks Peoples already installed Calendar by an Ubuntu-Update."
1797945,2018-10-19 08:31:01 UTC,"I found it really hard to find good answers to this problem - It was such a shock, and so important, that I was surprised this site was not no.1 in a Google search."
1797945,2018-12-04 10:21:08 UTC,"Hey, Thunderbird maintainer here."
1797945,2018-10-19 09:59:06 UTC,"Note: This may be fixed in some Weeks, Months, or Years, so maybe you can try first:
 > Thunderbird > Add-Ons > Extensions > Search for: Lightning > Install.
If you use Ubuntu-Linux or a Derivative, Lightning is not included in Thunderbird 60+ and the Update will break your Calendar (incompatible, not compatible). xul-ext-lightning is not international. Search for Add-On leads to incompatible Version. Someone told, the Beta is not recommended."
1797945,2018-10-22 06:31:11 UTC,I'm affected too and thanks to the users here - especially piraten-kris - we got an overview about the workarounds.
1797945,2018-10-23 14:58:17 UTC,"I believe that this should be set back to Confirmed, but the tracker's not letting me do that.  Or did someone actually start working on the issues in #25?"
1797945,2019-10-10 12:59:45 UTC,Comments #17 and #24 closed this bug report as being invalid but it was reopened as many users required a version of Lightning in a language other than English which could at the time of reporting only be obtained from the Thunderbird web-site.
1797945,2018-10-24 22:36:42 UTC,It was broken for me also and comments from #3 and #4 helped. Calendar is very important functionality and sudden disappearance was very problematic. May be work with Mozilla and ask them to update documentation for Ubuntu so that others facing this problem will have a quick solution.
1797945,2018-10-26 10:17:21 UTC,"When I tried installing  xul-ext-lightning , I got blocked, whether via the Synaptic Package manager or Software Center or using  apt from the command-line. The essence of the error message was:"
1797945,2018-10-26 17:42:44 UTC,Did anyone manage to synchronize NextCloud (DAV) calendar with any of workaround mentioned in this thread?
1797945,2018-11-10 19:23:26 UTC,"EN:Correction (DE:Korrektur)
----------------------------
EN: Note:
This may be fixed in some Weeks, Months, or Years, so maybe you can try first:
 > Thunderbird > Add-Ons > Extensions > Search for: Lightning > Install.
Problem:
If you use Ubuntu-Linux or another Debian-Derivative, Lightning is not included in Thunderbird 60+ and the Update will break your Calendar (incompatible, not compatible). xul-ext-lightning is not international. There is no Language-Pack for Lightning available. The normal Search for Add-On leads to an incompatible Version. Someone told me, the Beta was not recommended.
---
Workaround:
 1.> Lookup your Version of Thunderbird:
   > =Menu > Help > About Mozilla Thunderbird
 2.> Download the same Version of Thunderbird fitting for you from here:
https://ftp.mozilla.org/pub/thunderbird/releases/
 3.> Open File with an Archive-Program(Unzipper)
   > (Usually just > Double-Click or > Right-Click > open ..)
 4.> Goto > thunderbird > distribution > extensions >
 5.> {e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi (=Lightning) > Extract
 6.> Open your installed Thunderbird > Add-Ons > Extensions
 7.> (Remove unwanted english Version of Lightning: )
   > (Terminal > sudo apt remove xul-ext-lightning)
 8.> Gear-Wheel-Button next to the Search-Box
 9.> Install Add-on From File
 10.> Select Download-Folder and the .XPI-File > Install
=> All your Calendar-Data should be back. :-)
---------------------------------------------
DE: Hinweis:
Dies mag in einigen Wochen, Monaten oder Jahren behoben sein. Probiere zuerst
 > Thunderbird > Add-Ons > Erweiterungen > Suche nach: Lightning > Installieren.
Problem:
Wenn du Ubuntu-Linux oder einen anderen Debian-Abkömmling benutzt, ist Lightning nicht in Thunderbird 60+ enthalten und ein Update wird den Kalender abschalten  (inkompatibel, nicht kompatibel). xul-ext-lightning ist nicht international. Es ist kein Sprach-Paket für Lightning verfügbar. Die normale Suche nach Add-On führt zu einer inkompatiblen Version. Jemand sagte mir, die Beta sei nicht empfohlen.
---
Hilfs-Lösung:
 1.> Sieh nach, welche Version von Thunderbird du hast:
   > =Menü > Hilfe > Über Mozilla Thunderbird
 2.> Lade die selbe Version von Thunderbird passend für dich von dort:
https://ftp.mozilla.org/pub/thunderbird/releases/
 3.> Öffne die Datei mit einem Archiv-Programm(Unzipper)
   > (normalerweise nur > Doppelklick oder > Rechtsklick > öffnen ..)
 4.> Gehe dort zu > thunderbird > distribution > extensions >
 5.> {e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi (=Lightning) > Entpacken
 6.> Öffne dein installiertes Thunderbird > Add-Ons > Erweiterungen
 7.> (Entferne die unerwünschte englische Version von Lightning:)
   > (Terminal > sudo apt remove xul-ext-lightning)
 8.> Zahnrad-Knopf neben dem Suchfeld
 9.> Add-on aus Datei installieren
 10.> Wähle den Download-Ordner und die .XPI-Datei > Installieren
=> Alle deine Kalender-Daten sollten wieder da sein. :-)"
1797945,2018-10-21 18:40:44 UTC,"Got the same problem too, which I found very annoying.
I was very surprised to have such a blocking bug with regular Ubuntu updates."
1797945,2018-10-17 17:54:24 UTC,"This is ridiculous: If you go to https://bugs.launchpad.net
and search for: ""Lightning incompatible Thunderbird""
you will only find two many years old bugs, which have never been closed."
1797945,2018-10-23 20:11:36 UTC,"Hey, in my case the steps to fix it were as follows:
1. Download thunderbird tar.bz2 from https://www.thunderbird.net/
2. Extract it wherever you want
3. In extracted thunderbird folder you will find lightning xpi file compatible with TB 60.2.1: distribution/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi
4. Open your Thunderbird 60.2.1 installed from Ubuntu repo
5. Go to Addons -> Install addon from file and choose xpi file from point 3
6. Restart Thunderbird and enjoy Lightning once again :)"
1797945,2018-10-17 14:22:49 UTC,"There is an updated lightning package in the archive, but there isn't a compatible version of lightning on addons.thunderbird.net for users who have installed it from there as opposed to installing the one in the archive. There's not really anything we can do about that, other than advise you to install the one from the archive instead."
1797945,2018-10-17 17:23:22 UTC,"Hi Chris Coulson,"
1797945,2018-10-15 18:44:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797945,2018-10-15 19:39:27 UTC,"Hi all,"
1797945,2018-10-15 20:40:38 UTC,"Brain, thanks, installing xul-ext-lightning package from the package manager worked for me.  I may have needed to restart thunderbird as well."
1797945,2018-10-15 22:00:33 UTC,Brian's solutions works!
1797945,2018-10-16 00:27:49 UTC,"Same Problem today after ""sudo apt upgrade"" => from Thunderbird 52 to 60.2.1 (64-bit)
In all my 3 Profiles Lightning had stopped working / disappeared.
The First Profile had Lightning 5.4 installed as Add-On and now showed: incompatible .. deaktivated
Second and third Profile: In the Past, Lightning had been automatically integrated by clicking ""keep it"" and now it had disappeared.
Trying to install via search Add-Ons in Thunderbird only led to the incompatible 5.4."
1797945,2018-10-16 00:57:44 UTC,"Above is the direct Link to the German Version (DE).
Maybe you will have to chose your Language-Version from:
https://archive.mozilla.org/pub/calendar/lightning/candidates/6.2b6-candidates/build1/"
1797945,2018-10-16 06:34:56 UTC,"Solution in #6 worked for me. So thanks piraten-kris. I use swedish localization of thunderbird so it is not perfect since ""Termine und Aufgaben"" in the menu is definitively not Swedish but German."
1797945,2018-10-15 20:22:55 UTC,"I found switching from the add-on version to the xul-ext-lightning Ubuntu package worked, giving me the latest version."
1797945,2018-10-16 10:05:32 UTC,"One (temporary) option is also to downgrade Thunderbird back to the previous version (in my case 52.7).
I used 'Synaptic Package Manager' to downgrade and lock in the old version. I'll wait a while before updating."
1797945,2018-10-16 10:59:17 UTC,"The solution with installing the package xul-ext-lightning definitely works, having one issue: the only language it contains is English, which looks very uncool to have a mixed language Thunderbirds for users using that in other language than English."
1797945,2018-10-16 15:01:44 UTC,Recent versions of Thunderbird (at least the version packaged / distributed by Mozilla) has come pre-installed with Lightning; this is why the extension hasn't been updated on addons.mozilla.org.
1797945,2018-10-16 15:02:44 UTC,"The bug report for ""xul-ext-lightning is only available in English"" is at https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778 ."
1797945,2018-10-16 17:09:10 UTC,"Tested comment #12. Yes, it works! And it displays Lightning 6.2.2.1. I add it as attachment"
1797945,2018-10-16 21:05:26 UTC,"Instead of everyone having to download and extract their own .xpi file, I decided to do it myself and upload all the language/locale versions of the extension to here:"
1797945,2018-10-17 02:10:34 UTC,"I'm lucky enough to use english so installing xul-ext-lightning from the ubuntu software center worked as post #12 calls the ""correct"" solution.  I did however have to remove the old lightning addon using the thunderbird add-ons menu to get the new xul-ext-lightning one to show up.  Luckily the lightning tasks and events were preserved."
1797945,2018-10-16 06:40:52 UTC,"I update myself: I used #7 and used the swedish localization of instead. So now it says ""Händelser och uppgifter"" in the menu, which is correct Swedish. So problem solved!"
1797947,2019-08-23 01:43:44 UTC,"Retested before ceph -s returns and after.
Build info:
OS=""centos""
SW_VERSION=""19.09""
BUILD_TARGET=""Host Installer""
BUILD_TYPE=""Formal""
BUILD_ID=""20190821T053000Z"""
1797947,2019-08-15 17:27:00 UTC,"I retested this in a standard lab configuration (not a subcloud)
under the condition Tyler has noted above (ie. where labsetup is not complete and ceph -s does not return)"
1797947,2019-06-21 12:28:37 UTC,Assigned to Bruce for re-assignment.
1797947,2018-10-16 13:28:30 UTC,Targeting stx.2019.03 - horizon issue with distributed cloud. Doesn't gate stx.2018.10 as it's not a common config
1797947,2019-03-13 17:21:41 UTC,"I've seen this on a recent non-distributed cloud installation before.  It occurs during setup, before ceph has been brought up, as such the connection errors are expected.  It will occur whenever the 'ceph -s' command fails on the cli.  Think the action here is to suppress these exceptions and instead log a friendly message saying ceph isn't up yet.  Think this is a low priority issue though"
1797950,2019-09-19 11:59:04 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1797951,2018-10-17 11:19:33 UTC,If I ran this script from The URL: https://help.ubuntu.com/community/ManualFullSystemEncryption/DetailedProcessPrepareInstall
1797966,2019-06-19 20:59:39 UTC,"I've corrected the title of the bug since it doesn't cause a failure in tempest as far as I can tell, it's just a race which generates a confusing traceback in the logs which makes it hard to debug real failures."
1797966,2018-10-15 19:35:34 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22detaching%20network%20adapter%20failed.%3A%20libvirtError%3A%20internal%20error%3A%20End%20of%20file%20from%20qemu%20monitor%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d
1797966,2018-10-15 20:56:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/610727"
1797966,2020-03-09 18:45:12 UTC,"Reviewed:  https://review.opendev.org/610727
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6c3e8bc48e460c96f4fc8d975a63ef76e6f55694
Submitter: Zuul
Branch:    master"
1797967,2020-09-01 14:27:27 UTC,"No update for several. Weeks, will close. If this is still an issue, please re-open the bug."
1797967,2020-06-10 10:57:14 UTC,Apologies for taking so long to get around to triage this issue. If this is still an issue please attach the DKMS make.log file generated on the failed build.
1797967,2018-12-10 05:23:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1797973,2018-10-15 21:16:32 UTC,"Indeed, several UI's were updated as part of bug #1511742 (https://bugs.launchpad.net/evergreen/+bug/1511742/comments/40).  It looks like we missed one..."
1797973,2018-10-15 21:54:37 UTC,"Ah I see what you mean Bill, thanks."
1797973,2018-10-17 04:55:22 UTC,"Here's a branch for some OU selectors that I found needed to be contained a bit.
There may be more in places I didn't think to look however..."
1797973,2020-08-18 18:40:59 UTC,I'm getting a merge conflict when I try to cherry-pick this to current master.
1797973,2020-09-24 20:16:18 UTC,Apparently the issue shown in the screenshot has already been fixed at this point.
1797973,2020-12-14 20:08:03 UTC,No longer an issue in 3.5 and 3.6.
1797975,2018-10-15 21:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797975,2018-10-16 15:58:51 UTC,apport information
1797975,2018-10-16 15:58:53 UTC,apport information
1797975,2018-10-16 15:58:54 UTC,apport information
1797975,2018-10-16 15:58:55 UTC,apport information
1797975,2018-11-06 02:46:10 UTC,"Looks like same issue as reported in https://github.com/raspberrypi/linux/issues/2098. We have CONFIG_MMC_BCM2835=y defined but not in raspberry pi upstream (I'm looking at https://github.com/raspberrypi/linux/blob/rpi-4.14.y/arch/arm/configs/bcm2709_defconfig). Interestingly, both drivers/mmc/host/bcm2835.c and drivers/mmc/host/bcm2835-sdhost.c contains ""MODULE_ALIAS(""platform:sdhost-bcm2835"");"""
1797975,2018-10-16 15:58:59 UTC,apport information
1797975,2018-10-16 16:00:09 UTC,I also saw this on cosmic release candidate with rpi2. I ran apport-collect 1797975 as suggested but I'm not sure it really gathered anything new
1797975,2018-12-22 17:58:12 UTC,I reported this back in April (bug 1762835) and sent a patch to the mailing list.
1797975,2018-10-16 15:58:58 UTC,apport information
1797975,2018-10-16 15:58:50 UTC,apport information
1797975,2018-10-15 21:15:56 UTC,apport information
1797975,2018-10-15 21:15:57 UTC,apport information
1797975,2018-12-24 09:03:21 UTC,See Gentoo pull request https://github.com/sakaki-/bcmrpi3-kernel-bis/pull/3
1797975,2018-10-15 21:15:54 UTC,apport information
1797975,2018-10-15 21:15:53 UTC,apport information
1797975,2018-10-15 21:15:51 UTC,apport information
1797975,2018-10-15 21:15:50 UTC,apport information
1797975,2018-10-15 21:15:48 UTC,apport information
1797975,2018-10-15 21:15:46 UTC,apport information
1797975,2018-10-16 15:58:49 UTC,"ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw----+ 1 root audio 116,  1 Jun 22 11:11 seq
 crw-rw----+ 1 root audio 116, 33 Jun 22 11:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13
Architecture: armhf
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.10
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
 Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: linux (not installed)
PciMultimedia:"
1797975,2020-01-23 11:42:04 UTC,I've got this error message only and system won't boot. busybox shell is all I get.
1797985,2018-10-16 08:59:16 UTC,"Thanks for the pointer.
You are right: if it is there, it should return something useable ;-)"
1797986,2019-09-19 11:59:07 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1797986,2018-10-16 22:27:52 UTC,Currently generated maas config
1797986,2018-10-16 22:28:27 UTC,maas config if relay-only option/ability was provided.
1797986,2018-10-15 22:30:08 UTC,"Hi Kellen,"
1797986,2018-10-16 22:25:41 UTC,"Hi Andres,"
1797993,2018-10-20 00:23:31 UTC,This is most likely a lag in the refresh in the JS library.
1797997,2018-10-16 04:20:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1797997,2018-10-16 07:38:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797997,2018-10-16 08:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1797997,2018-10-16 08:45:27 UTC,"The bug on is
  BUG_ON(!(*sptep & PT_PRESENT_MASK));
In kvm_zap_rmapp"
1797997,2018-10-16 09:30:41 UTC,I found a similar bug in RedHat: https://access.redhat.com/solutions/2924271
1798001,2018-10-17 07:43:54 UTC,The only real way to fix this regardless of how EC2 behaviour might change underneath us is punt on assuming a NVMe block device link is valid for a newly attached machine volume even though it may not be. This is because we have to real way of querying how an attached volume will be exposed on a machine instance. This has no practical effect other than potentially printing an incorrect device link when printing storage volume information in YAML. The device name (eg xvdf) is accurate. To update the Juju model after the volume is recorded as attached is messy because we don't want to encode AWS specific behaviour at that layer.
1798001,2018-10-18 03:31:20 UTC,https://github.com/juju/juju/pull/9331
1798001,2018-10-16 02:14:37 UTC,"to replicate, using juju 2.4.4:"
1798001,2018-10-17 06:39:52 UTC,"Digging into the storage processing code, tt looks like the problem is that the EBS volumes are being exposed as NVMe block devices. This is relatively new behaviour that was previously confined to c5 and m5 instance types but now appears to have been more widely implemented. The issue is that the block device names become unpredictable which messes up how Juju determines whether a volume has become attached to a machine. This in turn blocks the initialisation of the unit agent since it waits for storage to become attached before installing the charm."
1798001,2018-10-16 01:44:20 UTC,Can we get an errors reported via the AWS console? What does juju debug-log indicate? Maybe the instance type has a limitation of how many volumes can be attached?
1798001,2018-10-16 02:11:29 UTC,@wallyworld `juju debug-log` does not contain log messages because the agent does not start it seems.
1798007,2018-10-18 06:46:00 UTC,Can't build this test on Xenial i386 as well.
1798007,2019-07-09 03:11:39 UTC,"Solution is here:
commit 29ff4881e498192118065dbc722e7302df740f6d
Author: Paolo Bonzini <email address hidden>
Date:   Tue Oct 25 15:26:43 2016 +0200"
1798007,2019-07-09 09:08:18 UTC,"Hmm, the commit above is quite old and we already have it."
1798021,2018-10-16 06:10:44 UTC,"Actually, I just noticed that the Ubuntu Studio testsuite on the ISO tracker is using the generic (Entire Disk) Install Test (1300). We should think about switching this to 1639, or at least adding a separate test for the ubiquity plugin stuff."
1798029,2019-09-12 07:34:29 UTC,"The package currently requires libzip5 1.5.0 or newer.  Is this request already adequately addressed, or is the request to downgrade the requirement to the older version?"
1798029,2020-03-25 22:20:47 UTC,I'm closing this at this time as the earlier question did not receive an answer.  Feel free to reopen and clarify the request if there is still an issue for you.
1798037,2018-12-19 17:38:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798040,2018-10-16 08:27:13 UTC,"Review in progress for https://review.opencontrail.org/47031
Submitter: Ankit Jain (<email address hidden>)"
1798041,2018-12-11 09:27:08 UTC,What can I do to get this bug fixed in bionic?
1798048,2019-10-01 17:06:12 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/686011"
1798048,2019-10-03 05:32:20 UTC,"Reviewed:  https://review.opendev.org/686011
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=5c284f228af2aafc2861f2035930e420991200dc
Submitter: Zuul
Branch:    stable/train"
1798048,2019-10-09 10:20:27 UTC,"Reviewed:  https://review.opendev.org/686005
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=be4d2301bb9654a772990d5d6f7bb2b126c7c127
Submitter: Zuul
Branch:    stable/stein"
1798048,2019-10-10 15:29:21 UTC,This issue was fixed in the openstack/horizon 16.0.0.0rc2 release candidate.
1798048,2019-10-01 16:36:05 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/686005"
1798048,2019-10-14 19:43:11 UTC,"Reviewed:  https://review.opendev.org/687956
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=93c4ded713c23832237f2c30974e0566574b8134
Submitter: Zuul
Branch:    stable/rocky"
1798048,2019-11-21 10:24:52 UTC,This issue was fixed in the openstack/horizon 17.0.0 release.
1798048,2019-10-22 20:08:05 UTC,This issue was fixed in the openstack/horizon 15.1.1 release.
1798048,2019-10-10 17:01:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/687956"
1798048,2019-10-01 06:57:35 UTC,"Reviewed:  https://review.opendev.org/679513
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=44987f02be671fd81b3dcd8d22f9fa1b219488c2
Submitter: Zuul
Branch:    master"
1798048,2019-10-22 20:07:26 UTC,This issue was fixed in the openstack/horizon 14.0.4 release.
1798048,2019-08-30 20:19:46 UTC,manila-ui bug https://bugs.launchpad.net/manila-ui/+bug/1842119
1798048,2019-08-30 17:56:23 UTC,"We have some customers complain about the issue. After a little bit digging, there are a couple of issues for manila-ui integration:"
1798048,2019-08-26 09:08:29 UTC,i am facing the same issue and it only appears when i manila-ui is enabled
1798048,2019-04-20 16:37:21 UTC,You seem to use manila-ui. Does it happen when manila-ui is enabled or does it still happen when only horizon is enabled?
1798048,2019-04-17 23:57:51 UTC,"FWIW, the line that is causing the TypeError is:"
1798048,2019-04-16 15:06:04 UTC,"I've got this in the config, of which the first 5 are shown in horizon and appear to be the initial defaults?"
1798048,2019-04-16 15:02:46 UTC,"Infact, on admin/defaults you can add the three missing values and edit, then it lists the new values on the page...click edit again and the 3 are missing"
1798048,2019-04-16 14:50:54 UTC,I still see this is rocky.
1798048,2019-08-30 21:00:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/679513"
1798049,2018-10-16 10:42:09 UTC,I've opened a bug report upstream https://bugzilla.mindrot.org/show_bug.cgi?id=2918 because friends not using Ubuntu confirmed the same erratic behavior even with newer OpenSSH versions (7.8)
1798049,2019-06-19 16:46:58 UTC,This bug was fixed in the package openssh - 1:8.0p1-2
1798052,2019-03-20 10:50:38 UTC,Found on P8 as well.
1798052,2019-03-20 10:35:20 UTC,But still failing with ARM64 / i386
1798052,2019-03-20 10:34:16 UTC,"Passed with T-AMD64:
tartup='Sat Mar 16 06:36:19 2019'
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted'
request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted'
request_key03.c:154: PASS: didn't crash while updating key of type 'trusted'
request_key03.c:168: PASS: didn't crash while requesting key of type 'trusted'
request_key03.c:154: PASS: didn't crash while updating key of type 'user'
request_key03.c:168: PASS: didn't crash while requesting key of type 'user'"
1798052,2018-11-28 11:43:50 UTC,"With 3.13.0-163-generic ARM64 this cycle:
request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM"
1798052,2018-10-25 07:45:42 UTC,"Tested again with 3.13.0-161 on a KVM node, it looks OK, need more check for the upcoming cycle."
1798052,2018-11-07 07:42:44 UTC,Still failing with generic Trusty kernel
1798052,2018-10-16 09:30:06 UTC,This change was made by a bot.
1798052,2018-11-07 08:30:58 UTC,"The failure in Trusty ARM64 is a bit different:
With 3.13.0-161-generic
request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM"
1798054,2019-06-03 18:08:52 UTC,This section of code will be deprecated when the solidfire template image for cloning is removed in favor of cinders image cloning
1798054,2019-06-25 20:51:35 UTC,"Here is the link for removing the depreciated value
https://review.opendev.org/#/c/664739/"
1798054,2020-06-15 15:15:56 UTC,"The patch https://review.opendev.org/664739 merged on Aug 21, 2019 and was first released in version 15.0.0.0rc1."
1798055,2018-10-17 16:06:29 UTC,"Yes it works !!!
Rsyslogd was already installed when I made the FreeBSD Openstack image."
1798055,2018-10-16 13:55:25 UTC,"@Carlo,
Can you verify that the module works on FreeBSD ?"
1798055,2018-10-17 12:08:37 UTC,"@Scott,
I've tried to test the single module but it didn't run because there are no rsyslog in configuration (The configuration is in the archive for the previous submission). I've also attached the dump from cloud-init analyze command."
1798055,2018-10-17 14:52:40 UTC,"I kind of suspect it will work, but before enablilng it by default in
freebsd i'd like to know that it does."
1798055,2020-10-29 07:08:18 UTC,"if we adapt the configuration location for rsyslog on BSD to /usr/local/etc instead of /etc, we can enable it by default."
1798057,2020-11-12 07:15:24 UTC,"I'm assuming that the right physbits setting fixed the bug? ... so I'm marking this ticket as ""Invalid"". If the problem still persists, then please open again."
1798057,2018-10-16 09:55:50 UTC,"Hi Alex,
  You should be able to fix this by passing the right cpu flags, e.g.:"
1798061,2018-10-16 10:30:07 UTC,This change was made by a bot.
1798061,2020-03-19 14:54:45 UTC,"As we're not supporting P8 on Trusty ESM anymore, I will close this bug."
1798072,2018-10-16 11:59:01 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/610936"
1798072,2018-11-09 08:59:06 UTC,"Change abandoned by Kamil Sambor (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/610936"
1798072,2019-03-19 13:36:28 UTC,is this still being worked on?
1798072,2019-06-03 20:29:48 UTC,I believe this was addressed in packaging for pike.
1798072,2021-02-17 17:09:44 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1798074,2018-12-15 23:41:28 UTC,"(In reply to Andras from comment #19)

> (In reply to Mike Kaganski from comment #17)
> Not the very similar result (not in console but simple GUI processes)  made
> her/him to report here? Yes, everyone should read rules before reporting
> however what made you think everyone should know what's going on below GUI?
> Actually I just got the very similar experience with LibreOffice and now I
> just start thinking where should I go, maybe to Office 365 instead. At least
> answer for a simple question what should miserable users do after your
> magnificent breathtaking awesome reprimand. God luck opensource with this
> attitude.
"
1798074,2019-05-09 13:19:21 UTC,"Reading related upstream reports, one possible cause of this may be LibreOffice's Common Print Dialog (CPD) integration. Could you please check if you have any cpd packages installed by running:"
1798074,2019-05-04 17:50:16 UTC,"Unfortunately I removed the archive version of LO and installed the snap version, which is not exhibiting the problem, because I need to be able to edit documents; I can therefore no longer replicate the bug. But pleasingly it looks as though Jani can, so I'll leave it in their hands."
1798074,2019-05-04 16:31:35 UTC,"Can't speak for Stuart, but I'm the other one affected, and still so:"
1798074,2018-12-16 01:08:29 UTC,"(In reply to Julien Nabet from comment #21)
Thanks for the prompt responses and I appreciate your contribution and your hard work. I'm only a stubborn hothead and it was nothing personal but a matter of math. Yes, you're right I use whatever software I wan't and opensources evolved and got the number of users today because users needed opensource and because given software was usable but don't forget it's vice versa. Obviously it'll not happen to LO tomorrow but I think a lot project aren't here today because rude users and angry contributors.
I already reported my issue here:
https://bugs.documentfoundation.org/show_bug.cgi?id=122116
so sorry for bothering here but yes currently I'm quite depending on LibreOffice and still searching over and over for solution that's why I landed here.
I don't know my issue is relevant to this particular bug however just in case I attached my similar result and please neglect it right after you recognize it isn't related, thank you."
1798074,2019-04-17 13:36:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798074,2019-07-03 13:35:28 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.0.7-0ubuntu0.18.04.7
1798074,2019-05-13 16:32:07 UTC,"@Marcus: yup, that seems to be it:"
1798074,2019-04-25 13:42:51 UTC,Sorry for the lack of feedback on that report Stuart.
1798074,2019-05-13 17:35:30 UTC,"Ok yeah, so you would still see this happening in 6.0.x as the issue was only later fixed in 6.2.0+ (see: https://bugs.documentfoundation.org/show_bug.cgi?id=122116#c35)"
1798074,2019-06-17 08:41:15 UTC,"The verification of the Stable Release Update for libreoffice has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1798074,2019-06-10 08:39:43 UTC,"Upgraded libreoffice from 1:6.1.6-0ubuntu0.18.10.2 to 1:6.1.6-0ubuntu0.18.10.3 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and verified that the crash is now resolved."
1798074,2019-06-17 08:40:58 UTC,This bug was fixed in the package libreoffice - 1:6.1.6-0ubuntu0.18.10.3
1798074,2019-07-02 16:24:44 UTC,This bug was fixed in the package libreoffice - 1:6.0.7-0ubuntu0.18.04.7
1798074,2019-06-17 08:41:19 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.1.6-0ubuntu0.18.10.3
1798074,2019-06-25 15:40:21 UTC,"Hello Stuart, or anyone else affected,"
1798074,2019-06-25 16:18:31 UTC,"Hello Stuart, or anyone else affected,"
1798074,2019-06-26 08:58:44 UTC,"Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.6 to 1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the crash is now resolved."
1798074,2019-06-26 12:32:09 UTC,Happy to report that the proposed packages did fix the issue for me also. Thanks everyone!
1798074,2019-06-07 21:35:20 UTC,"Hello Stuart, or anyone else affected,"
1798074,2018-12-15 23:26:21 UTC,"(In reply to howil from comment #18)

> (In reply to Mike from comment #17)
>
> ...
> How to proceed? Should I report a new bug or is it somehow related to this
> one. In any case it is annoying, because LO6 does not start under any
> circumstances.
"
1798074,2018-12-16 01:15:14 UTC,"Created attachment 147588
LibreOffice won't start because recovery issue, not even in safe-mode without restore"
1798074,2018-08-20 13:47:44 UTC,(In reply to Mike from comment #17)
1798074,2018-12-15 23:05:57 UTC,"(In reply to Mike Kaganski from comment #17)
Not the very similar result (not in console but simple GUI processes)  made her/him to report here? Yes, everyone should read rules before reporting however what made you think everyone should know what's going on below GUI? Actually I just got the very similar experience with LibreOffice and now I just start thinking where should I go, maybe to Office 365 instead. At least answer for a simple question what should miserable users do after your magnificent breathtaking awesome reprimand. God luck opensource with this attitude."
1798074,2016-10-13 06:02:57 UTC,"Description:
Libreoffice crashed after trying to open a *.docx-file. Now, when I start Libreoffice, it starts with „document resauration“ and when I click „ok“ there it crashes."
1798074,2016-10-13 09:17:36 UTC,Do you confirmed you renamed your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux)
1798074,2017-05-02 11:36:41 UTC,"Dear Bug Submitter,"
1798074,2018-03-11 21:08:09 UTC,"Created attachment 140569
File that reproduces the bug"
1798074,2018-03-11 21:14:12 UTC,"When opening the attached document using the following command I can reproduce this bug in both 5.1.4.2 and now with Ubuntu 17.10 and LibreOffice 5.4.5.1
Build ID: 1:5.4.5-0ubuntu0.17.10.5. I'm able to open the file in other progs, like Excel."
1798074,2018-03-11 22:08:08 UTC,"On pc Debian x86-64 with master sources updated today, I could also reproduce the crash but it seems cause is different.
Indeed, both bts you show Michael and you are different."
1798074,2018-03-11 23:08:14 UTC,"Yep, let's keep this one open!"
1798074,2018-03-12 07:09:55 UTC,https://gerrit.libreoffice.org/51096
1798074,2017-05-31 10:46:00 UTC,"Dear Bug Submitter,"
1798074,2018-03-12 09:28:25 UTC,"Wow Mike, that was really fast! Thanks a lot
I've just cherry-picked it to 6-0, 5-4 and 5-4-6"
1798074,2018-03-12 08:09:21 UTC,"Mike Kaganski committed a patch related to this issue.
It has been pushed to ""master"":"
1798074,2018-08-16 08:40:25 UTC,Still open on Ubuntu 18.04 in LibreOffice 6.0.6.2 00m0(Build:2) (from ppa).
1798074,2018-03-13 11:10:10 UTC,Let's simplify a bit targets.
1798074,2018-03-13 10:59:22 UTC,"Mike Kaganski committed a patch related to this issue.
It has been pushed to ""libreoffice-5-4-6"":"
1798074,2018-08-16 08:45:49 UTC,(In reply to howil from comment #16)
1798074,2018-03-13 10:39:07 UTC,"Mike Kaganski committed a patch related to this issue.
It has been pushed to ""libreoffice-6-0"":"
1798074,2018-03-13 10:38:56 UTC,"Mike Kaganski committed a patch related to this issue.
It has been pushed to ""libreoffice-5-4"":"
1798074,2018-03-13 10:37:04 UTC,Verified in
1798090,2018-10-16 14:06:00 UTC,Not the same problem here on 16.04 : my google calendars are still in sync using google agenda provider add-on.
1798090,2018-10-16 16:28:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798090,2018-10-16 16:43:55 UTC,"same here - on 16.04. the ""internal"" Lightning calendar disappearead since it is not longer compatible with TB60."
1798090,2018-10-18 07:32:21 UTC,I am not convinced this is a ducplicate of bug #1797945. If I read that report correctly it is about upgraded Thunderbird with the external add-ons used. I *do* have both lightning and gcal provider from the Ubuntu archive (repeating from the description):
1798090,2018-10-18 07:33:45 UTC,Above is from apt upgrade log. So both went from 1:52.9.* to 1:60.2*
1798090,2018-10-22 06:13:27 UTC,"Yes - my comment #4 is related to bug #1797945
Thanks to smb for the clarification"
1798090,2018-11-29 20:48:55 UTC,I believe I have the same problem: an Ubuntu upgrade has caused the Ubuntu-installed gdata provider to not be visible in the Thunderbird addons list. This results in all of my google calendars being greyed out in the Thunderbird calendar pane.
1798092,2018-10-19 07:22:56 UTC,There is no space left on the /boot partition. Maybe removing some old kernel packages would help. That can be done by running the following command in the terminal:
1798092,2020-11-09 08:39:50 UTC,"Hello,
do you still have this issue with the latest 4.15 kernel on Xenial?
Thanks"
1798092,2021-01-09 04:17:26 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1798103,2018-11-16 19:33:38 UTC,I can reliably reproduce the bug with the steps provided.
1798103,2018-11-17 13:14:32 UTC,"Thanks Olivier, I've now added the link to my upstream report."
1798109,2018-10-18 12:55:11 UTC,apport information
1798109,2018-10-18 12:55:12 UTC,apport information
1798109,2018-10-18 12:55:14 UTC,apport information
1798109,2018-10-18 12:55:15 UTC,apport information
1798109,2018-10-18 12:55:17 UTC,apport information
1798109,2018-10-18 12:55:19 UTC,apport information
1798109,2018-10-18 12:55:20 UTC,apport information
1798109,2018-10-18 12:55:23 UTC,apport information
1798109,2018-10-18 12:55:25 UTC,apport information
1798109,2018-10-18 12:55:27 UTC,apport information
1798109,2018-10-18 12:55:29 UTC,apport information
1798109,2018-10-18 12:55:35 UTC,apport information
1798109,2018-10-18 12:55:37 UTC,apport information
1798109,2018-10-18 12:55:38 UTC,apport information
1798109,2018-10-18 12:55:40 UTC,apport information
1798109,2018-10-18 12:59:52 UTC,apport information
1798109,2018-10-18 12:57:46 UTC,apport information
1798109,2018-10-18 12:57:51 UTC,apport information
1798109,2018-10-18 12:59:25 UTC,apport information
1798109,2018-10-18 12:59:27 UTC,apport information
1798109,2018-10-18 12:59:29 UTC,apport information
1798109,2018-10-18 12:59:31 UTC,apport information
1798109,2018-10-18 12:59:33 UTC,apport information
1798109,2018-10-18 12:59:35 UTC,apport information
1798109,2018-10-18 12:59:36 UTC,apport information
1798109,2018-10-18 12:59:38 UTC,apport information
1798109,2018-10-18 12:59:39 UTC,apport information
1798109,2018-10-18 12:59:41 UTC,apport information
1798109,2018-10-18 12:59:44 UTC,apport information
1798109,2018-10-18 12:59:45 UTC,apport information
1798109,2018-10-18 12:59:49 UTC,apport information
1798109,2018-10-18 12:57:48 UTC,apport information
1798109,2018-10-18 12:55:09 UTC,apport information
1798109,2018-10-16 15:54:09 UTC,"In 'WifiSyslog.txt' what's relevant about 'nvidia':
""10月 16 22:14:56 blurhy-FX503VD kernel: nvidia: loading out-of-tree module taints kernel.
10月 16 22:14:56 blurhy-FX503VD kernel: nvidia: module license 'NVIDIA' taints kernel..."""
1798109,2018-10-18 12:55:01 UTC,apport information
1798109,2018-10-16 14:46:44 UTC,"The card is GTX1050
Driver Version: 390.87"
1798109,2018-10-16 15:07:26 UTC,"Hello blurhy,"
1798109,2018-10-16 15:17:17 UTC,apport information
1798109,2018-10-16 15:17:19 UTC,apport information
1798109,2018-10-16 15:17:22 UTC,apport information
1798109,2018-10-16 15:17:23 UTC,apport information
1798109,2018-10-16 15:17:25 UTC,apport information
1798109,2018-10-16 15:17:27 UTC,apport information
1798109,2018-10-16 15:17:28 UTC,apport information
1798109,2018-10-16 15:17:30 UTC,apport information
1798109,2018-10-16 15:17:31 UTC,apport information
1798109,2018-10-16 15:17:33 UTC,apport information
1798109,2018-10-16 15:17:35 UTC,apport information
1798109,2018-10-18 12:55:02 UTC,apport information
1798109,2018-10-16 15:17:40 UTC,apport information
1798109,2018-10-16 15:17:36 UTC,apport information
1798109,2018-10-16 15:53:12 UTC,"blurhy,"
1798109,2018-10-18 12:54:59 UTC,apport information
1798109,2018-10-18 12:54:57 UTC,apport information
1798109,2018-10-18 12:54:00 UTC,apport information
1798109,2018-10-18 12:53:58 UTC,apport information
1798109,2018-10-16 15:18:53 UTC,apport information
1798109,2018-10-18 12:53:45 UTC,apport information
1798109,2018-10-18 12:53:47 UTC,apport information
1798109,2018-10-18 11:06:11 UTC,"Ok,fixed by disabling the nvidia indicator.
But I think there is still a bit not smooth"
1798109,2018-10-17 11:42:14 UTC,The gifs don't show the difference.
1798109,2018-10-17 09:50:43 UTC,Firefox says that it's using nvidia and opengl is enabled.
1798109,2018-10-17 09:44:41 UTC,"Compare intel and nvidia.
Using prime-select to switch card."
1798109,2018-10-17 09:31:37 UTC,"Bios isn't the latest version.I don't know whether or bios cause the 'i2c_hid'.Also I don't want to upgrade it,I afraid that my computer won't boot."
1798109,2018-10-18 12:53:43 UTC,apport information
1798110,2018-10-16 15:44:28 UTC,Patches posted to kernel-team mailing list [1].
1798110,2018-11-13 17:53:26 UTC,This bug was fixed in the package linux - 4.4.0-139.165
1798110,2018-10-25 14:07:05 UTC,"Verification successful with the kernel in xenial-proposed.
Updating verification tags."
1798110,2018-10-25 08:04:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1798110,2018-10-16 15:23:06 UTC,Organic Testcase:
1798110,2018-10-16 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798110,2018-10-16 15:11:06 UTC,"Synthetic Test Case
==================="
1798110,2018-10-16 14:44:52 UTC,"Problem Analysis
================"
1798110,2018-10-16 15:13:58 UTC,"Organic Testcase
================"
1798123,2018-10-16 16:27:36 UTC,By creating the leases container manually I don't get this error anymore.
1798125,2019-01-07 14:46:57 UTC,This issue was fixed in the openstack/kolla-ansible 7.0.1 release.
1798125,2018-11-30 17:05:07 UTC,"By changing the ""scheduling_strategy"" from ""multi-node"" to ""default"" I'm able to get a checkpoint triggered!"
1798125,2018-11-28 23:49:59 UTC,"After some checks, the code never enter in the loop for operations_ids because operations_ids is equal to: set([])"
1798125,2018-11-28 19:37:48 UTC,"Ok, I figured out why I got the ""KeyError: u'tenant_id'"" error, it is because Kolla creates the wrong endpoint. Karbor uses ""project_id"" and Kolla creates the endpoint using ""tenant_id"""
1798125,2019-01-07 14:37:57 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0b1 development milestone.
1798125,2018-11-23 19:49:21 UTC,"The error disappeared by itself :/
Now I don't have any more error but the checkpoint creation is not triggered, nothing happens."
1798125,2018-11-23 17:38:49 UTC,"region_id option was missing in [karbor_client] section.
Now I got a different error:"
1798125,2018-11-23 16:23:41 UTC,"Still getting the error, I though this change would help: https://review.openstack.org/#/c/616730/"
1798125,2018-11-28 18:14:57 UTC,The error came back after karbor-operationengine service restart.
1798127,2020-10-19 13:22:08 UTC,"Marked all tasks invalid.  It's been over 2 years and no further update from the tester who reported this initially.  One can only presume it's been resolved by some update to the kernel, or was not kernel related and resolved itself by other means.  If this appears again, we'll open a fresh bug."
1798127,2018-10-16 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798127,2018-10-16 18:36:55 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1798127,2018-10-22 23:23:51 UTC,'kernel-fixed-upstream'
1798127,2018-10-22 23:26:57 UTC,"Successfully upgraded to 4.19. Stress-ng memory test passed without lockup issue. New rebuild kernel 4.19  has fixed the issue. Refer to text below:
-------
ubuntu@fluent-orca:~$ uname -r
4.19.0-041900rc8-generic"
1798127,2018-10-30 19:55:13 UTC,"I added a nomination for Xenial, but that may not be the right way (I'm not sure how to add a Xenial task like the Bionic task already added."
1798127,2018-11-14 16:23:11 UTC,"Would it be possible for you to test the latest upstream stable 4.18?  It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.19/"
1798127,2018-11-15 01:45:28 UTC,"Why is Xenial marked invalid?  AFAIK this affects 4.15, but not 4.4, which means Xenial HWE also has this regression."
1798127,2018-11-15 15:54:19 UTC,"The Xenial bug task is for the base Xenial kernel version 4.4.  Any commits/fixes applied to Bionic flow down into Xenial HWE because Bionic is 4.15 based, which is the source for Xenial HWE."
1798127,2018-11-16 00:58:03 UTC,"Ahhh, ok. Thanks. That makes sense, then.
On Fri, Nov 16, 2018 at 12:01 AM Joseph Salisbury
<email address hidden> wrote:

>
> The Xenial bug task is for the base Xenial kernel version 4.4.  Any
> commits/fixes applied to Bionic flow down into Xenial HWE because Bionic
> is 4.15 based, which is the source for Xenial HWE.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1798127
>
> Title:
>   CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as
>   root FS
>
> Status in linux package in Ubuntu:
>   Triaged
> Status in linux source package in Xenial:
>   Invalid
> Status in linux source package in Bionic:
>   Triaged
> Status in linux source package in Cosmic:
>   Triaged
>
> Bug description:
>   This was reported by a hardware partner.  The system set up is a
>   server with 512GB RAM and an M.2 NVMe drive as the root
>   filesystem/boot device.
>
>   Per the customer, when running the certification Memory Stress test
>   (utilizing several stress-ng stressors run in sequence) the system
>   freezes with CPU Soft Lockup errors appearing on console whe the
>   ""stack"" stressor is run.
>
>   Tester has tried with 2.5” SATA (1TB), 2.5” NVMe (800GB), and M.2 NVMe
>   (1.9TB).
>
>   So far, this only seems to affect the 4.15 kernel.  The tester has
>   tried using the 2.5"" SATA SSD as the RootFS/Boot device and the tests
>   pass on all attempts.  It is ONLY when using the M.2 NVMe as the root
>   / boot device that the tests cause a lockup.  The tester is re-trying
>   now with the 2.5"" NVMe device to see if this only occurs with the M.2
>   NVMe.
>
>   The tester has tried this on the following while using the M.2 NVMe as the rootFS/Boot device:
>   Test run #1 – 16.04.5 at kernel 4.15; Result: Failed stress-ng memory on stack stressor
>   Test run #2 – 18.04.1 at kernel 4.15; Result: Failed stress-ng memory on stack stressor
>   Test run #3 – 16.04.5 at kernel 4.4; Result: Passed stress-ng memory test
>
>   The stress-ng command invoked at the time the soft lockups occur is
>   this:
>
>   'stress-ng -k --aggressive --verify --timeout 300 --stack 0'
>
>   This can be reproduced by running the memory_stress_ng test script
>   from the cert suite:
>
>   sudo /usr/lib/plainbox-provider-certification-
>   server/bin/memory_stress_ng
>
>   It may be more easily reproducible running the stack stressor alone,
>   or the whole memory stress script without dealing with Checkbox.
>
>   UPDATE: The tester also confirms that the 2.5"" NVMe drives also fail
>   with the 4.15 kernel and pass with the 4.4 kernel.  The SSD works on
>   all kernels.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798127/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; status=Triaged; importance=High; <email address hidden>;
> Launchpad-Bug: distribution=ubuntu; distroseries=xenial; sourcepackage=linux; component=main; status=Invalid; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic; s...
"
1798132,2019-09-19 14:47:47 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1798132,2018-10-16 15:44:18 UTC,What it would seem to me is that MAAS was starting up. Recent changes in the startup process don't seem to hanbdle these thigns correctly though.
1798132,2018-10-16 15:43:41 UTC,"2018-10-16 11:02:52 twisted.scripts: [info] twistd 17.9.0 (/usr/bin/python3 3.6.6) starting up.
2018-10-16 11:02:52 twisted.scripts: [info] reactor class: twisted.internet.asyncioreactor.AsyncioSelectorReactor.
2018-10-16 11:02:54 stderr: [error] --- Logging error ---
2018-10-16 11:02:54 stderr: [error] Traceback (most recent call last):
2018-10-16 11:02:54 stderr: [error]   File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 1386, in _inlineCallbacks
2018-10-16 11:02:54 stderr: [error]     result = g.send(result)
2018-10-16 11:02:54 stderr: [error] StopIteration: (3, '● maas-syslog.service - MAAS Syslog Service\n   Loaded: loaded (/lib/systemd/system/maas-syslog.service; enabled; vendor preset: enabled)\n   Active: inactive (dead) since Tue 2018-10-16 11:01:15 EDT; 1min 38s ago\n     Docs: man:rsyslogd(8)\n           http://docs.maas.io/\n Main PID: 636 (code=exited, status=0/SUCCESS)\n\nOct 16 11:00:39 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:00:51 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:00:53 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:00:55 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:00:55 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:01:14 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:01:15 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:01:15 bionic-maas-run systemd[1]: Stopping MAAS Syslog Service...\nOct 16 11:01:15 bionic-maas-run rsyslogd[636]:  [origin software=""rsyslogd"" swVersion=""8.32.0"" x-pid=""636"" x-info=""http://www.rsyslog.com""] exiting on signal 15.\nOct 16 11:01:15 bionic-maas-run systemd[1]: Stopped MAAS Syslog Service.\n', '')
2018-10-16 11:02:54 stderr: [error]
2018-10-16 11:02:54 stderr: [error] During handling of the above exception, another exception occurred:
2018-10-16 11:02:54 stderr: [error]
2018-10-16 11:02:54 stderr: [error] Traceback (most recent call last):
2018-10-16 11:02:54 stderr: [error]   File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 1386, in _inlineCallbacks
2018-10-16 11:02:54 stderr: [error]     result = g.send(result)
2018-10-16 11:02:54 stderr: [error]   File ""/usr/lib/python3/dist-packages/provisioningserver/utils/service_monitor.py"", line 560, in _loadSystemDServiceState
2018-10-16 11:02:54 stderr: [error]     returnValue((active_state_enum, process_state))
2018-10-16 11:02:54 stderr: [error]   File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 1363, in returnValue
2018-10-16 11:02:54 stderr: [error]     raise _DefGen_Return(val)
2018-10-16 11:02:54 stderr: [error] twisted.internet.defer._DefGen_Return: (<SERVICE_STATE.OFF: 'off'>, 'dead')
2018-10-16 11:02:54 stderr: [error]
2018-10-16 11:02:54 stderr: [error] During handling of the above exception, anoth..."
1798134,2019-02-13 15:58:14 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611065"
1798136,2019-02-17 03:52:08 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611063"
1798137,2018-12-10 15:13:11 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611043"
1798140,2019-02-17 03:51:50 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611060"
1798141,2019-02-17 03:52:19 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611046"
1798142,2019-01-04 19:45:11 UTC,"Change abandoned by Dan Prince (<email address hidden>) on branch: master
Review: https://review.openstack.org/611061
Reason: Just makes the line longer. Lets wait until there is actually something meaningful here before syncing these."
1798145,2018-12-10 15:13:23 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611042"
1798151,2018-12-07 02:15:20 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611041"
1798153,2019-02-03 12:58:45 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611037"
1798155,2019-03-06 13:40:33 UTC,"Change abandoned by weizj (<email address hidden>) on branch: master
Review: https://review.openstack.org/611030"
1798158,2018-10-16 17:00:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611094"
1798158,2018-10-17 13:05:09 UTC,"Reviewed:  https://review.openstack.org/611094
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=133d6b3bcc26bb2e66ef303011280e38add00702
Submitter: Zuul
Branch:    master"
1798158,2018-10-17 14:09:32 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611327"
1798158,2018-10-24 06:19:28 UTC,"Reviewed:  https://review.openstack.org/611327
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=44e12db8420da9cea8cb23f3b0fabed2d1e0278b
Submitter: Zuul
Branch:    stable/rocky"
1798158,2018-11-06 06:01:08 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1798158,2019-03-22 03:46:44 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1798161,2018-11-23 16:14:31 UTC,"Works for me now, I think this is related to this change https://review.openstack.org/#/c/618639/"
1798163,2018-10-18 00:43:00 UTC,"Reviewed:  https://review.openstack.org/611314
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=83396b325428332bd51c57f89599cf4cc074c7fb
Submitter: Zuul
Branch:    stable/rocky"
1798163,2019-03-22 03:46:45 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1798163,2018-11-06 06:01:10 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1798163,2018-10-19 03:34:21 UTC,"Reviewed:  https://review.openstack.org/611315
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6bd7e8a958f53e2288b41a27528a008e3cfb2802
Submitter: Zuul
Branch:    stable/rocky"
1798163,2018-10-17 13:25:31 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611315"
1798163,2018-10-17 10:38:52 UTC,"Reviewed:  https://review.openstack.org/611113
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=618b47627d8dc4f071032e3e63c530d3fe199b39
Submitter: Zuul
Branch:    master"
1798163,2018-10-17 12:18:28 UTC,"Reviewed:  https://review.openstack.org/611115
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=730936e535e67127c76d4f27649a16d8cf05efc9
Submitter: Zuul
Branch:    master"
1798163,2018-10-16 17:49:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/611113"
1798163,2018-10-17 13:25:13 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611314"
1798163,2018-10-16 17:55:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611115"
1798166,2020-12-09 08:23:34 UTC,"Follow-up to Comment #36: Although patching upower fixes the issue, gnome-settings-daemon is still broken, since disabling notifications won't disable all notifications."
1798166,2018-10-16 19:51:08 UTC,"https://marc.info/?l=linux-usb&m=153971734920554&w=2
--
Cristian Aravena Romero (caravena)"
1798166,2018-10-18 12:45:12 UTC,"the issue is rather on the GNOME side that on the kernel, there was a request to add those to the notifications panel in https://gitlab.gnome.org/GNOME/gnome-shell/issues/308"
1798166,2018-10-18 15:09:55 UTC,"https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108
--
Cristian Aravena Romero (caravena)"
1798166,2020-04-28 05:59:02 UTC,"I'm using Ubuntu 20.04 and every time I start typing on my keyboard, the ""Keyboard battery low"" alert pops up, obscuring a large part of the screen. This is becoming really annoying. I do not want to completely disable all power notifications as I'm using a laptop and need to know when the laptop will die."
1798166,2020-04-28 08:36:28 UTC,"Retitling, it's now possible to disable the power notification but that's still not a great solution"
1798166,2020-05-06 00:36:55 UTC,"> I'm using Ubuntu 20.04 and every time I start typing on my keyboard, the ""Keyboard battery low"" alert pops up, obscuring a large part of the screen. This is becoming really annoying. I do not want to completely disable all power notifications as I'm using a laptop and need to know when the laptop will die.
"
1798166,2020-05-06 08:23:43 UTC,Could you take a screenshot of the notification?
1798166,2020-06-12 20:40:03 UTC,"Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_0
  native-path:          hidpp_battery_0
  model:                MX Keys Wireless Keyboard
  serial:               408a-9b-b6-52-57
  power supply:         no
  updated:              Fr 12 Jun 2020 22:39:07 CEST (8 seconds ago)
  has history:          yes
  has statistics:       yes
  mouse
    present:             yes
    rechargeable:        yes
    state:               discharging
    warning-level:       low
    battery-level:       low
    percentage:          10% (should be ignored)
    icon-name:          'battery-caution-symbolic'"
1798166,2020-06-12 20:46:09 UTC,"Some background: rechargeable batteries have 1.2V nominal (compared to 1.5V nominal for regular battteries). Any mouse will report levels around 10%, although the batteries will run for *many* months."
1798166,2020-08-25 01:41:15 UTC,"Noooooooo, please don't mark this as invalid.  This is the most annoying notification on my wonderful Gnome desktop.  It is so premature.  First off, it thinks my MX Logitech keyboard is a mouse and secondly, it displays over and over long before the keyboard needs to be charged."
1798166,2020-09-25 06:17:45 UTC,"This bug is NOT invalid. This issue has remained unaddressed for years. Worse still, workarounds that used to mitigate the problem (dconf tweaks, etc) no longer seem effective."
1798166,2020-09-25 23:25:11 UTC,"If I understood correctly this bug was invalidated as a Linux bug only, not as a GNOME issue. As a GNOME (or more specifically as ""gnome-settings-daemon package"") it is not only valid, but its priority is set to high. It makes sense to me."
1798166,2020-09-26 06:18:39 UTC,"Clarification: this bug ist not about wrong battery Level measurements (Nobody reported that), it's about users being unable to disable notifications. The notification is shown even when in DND mode."
1798166,2020-10-17 13:04:46 UTC,"The battery warning stays on top window layer all the time and covers real important warnings and information, e.g. the task bar of a window."
1798166,2020-12-08 15:23:51 UTC,This needs a solution. Not being able to turn of the notifications is not acceptable. Thanks.
1798166,2020-12-09 08:21:28 UTC,"FYI, here's the corresponding bug in GNOME:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/108"
1798166,2018-10-16 19:14:08 UTC,"https://bugzilla.kernel.org/show_bug.cgi?id=201445
--
Cristian Aravena Romero (caravena)"
1798166,2020-07-07 02:27:58 UTC,Hope this one gets fixed soon. The notification is quite annoying.
1798166,2018-10-16 19:07:45 UTC,"Earlier I used rechargeable batteries, I just recharged them when this notification appeared."
1798166,2018-10-16 18:22:23 UTC,apport information
1798166,2018-10-16 18:15:42 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798166,2018-10-16 18:21:58 UTC,apport information
1798166,2018-10-16 18:22:00 UTC,apport information
1798166,2018-10-16 18:22:01 UTC,apport information
1798166,2018-10-16 18:22:03 UTC,apport information
1798166,2018-10-16 18:38:44 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1798166,2018-10-16 18:22:07 UTC,apport information
1798166,2018-10-16 18:22:06 UTC,apport information
1798166,2018-10-16 18:22:10 UTC,apport information
1798166,2018-10-16 18:22:11 UTC,apport information
1798166,2018-10-16 18:22:12 UTC,apport information
1798166,2018-10-16 18:22:13 UTC,apport information
1798166,2018-10-16 18:22:16 UTC,apport information
1798166,2018-10-16 18:22:18 UTC,apport information
1798166,2018-10-16 18:22:21 UTC,apport information
1798166,2018-10-16 18:22:08 UTC,apport information
1798167,2019-06-09 20:49:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798172,2018-10-19 03:04:14 UTC,"Reviewed:  https://review.openstack.org/611337
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=57566f4c8d2929c25e76564883369a7c6eda720a
Submitter: Zuul
Branch:    stable/rocky"
1798172,2019-03-22 03:46:42 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1798172,2018-11-06 06:01:06 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1798172,2018-10-17 23:20:16 UTC,"Reviewed:  https://review.openstack.org/611162
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=498413074d1f11688123b6b592d5c204dc7b5ef2
Submitter: Zuul
Branch:    master"
1798172,2018-10-16 19:14:15 UTC,It doesn't blow up on startup because the exception is caught and logged in ComputeManager._update_available_resource_for_node.
1798172,2018-10-16 20:27:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611162"
1798172,2018-10-17 14:27:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/611337"
1798172,2018-10-16 19:04:00 UTC,Confirmed in the ironic grenade job in a stable/rocky change:
1798177,2018-10-17 07:40:05 UTC,Upstream bug: http://bugs.debian.org/877279
1798178,2018-10-16 18:57:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798178,2018-10-16 23:55:06 UTC,*** This is an automated message ***
1798178,2019-08-18 12:33:38 UTC,"Meanwhile, version 1.0.5 has been released at https://github.com/PanderMusubi/klingon/tree/master/packages"
1798179,2018-10-16 18:57:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798179,2018-10-16 23:55:04 UTC,*** This is an automated message ***
1798179,2019-08-18 12:33:30 UTC,"Meanwhile, version 1.0.5 has been released at https://github.com/PanderMusubi/klingon/tree/master/packages"
1798179,2020-05-05 13:25:36 UTC,"As packaging for Debian will take a while to get into stable, please use the stable from our PPA https://launchpad.net/~nuspell/+archive/ubuntu/ppa"
1798179,2020-05-05 13:26:40 UTC,"Please ignore last remark, is for another bug."
1798185,2019-06-13 10:37:42 UTC,"I can see this in Disco too, mark this as Fix-released."
1798185,2018-10-29 22:25:21 UTC,This bug was fixed in the package linux-azure - 4.15.0-1028.29
1798185,2018-10-23 13:42:54 UTC,We are also setting CONFIG_INFINIBAND_IPOIB=y.
1798185,2018-10-16 19:37:45 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798185,2018-10-17 21:46:26 UTC,I'm assuming CONFIG_INFINIBAND_USER_MAD=m.
1798187,2019-03-05 15:40:39 UTC,New bug for the documentation piece here: https://bugs.launchpad.net/evergreen/+bug/1818692
1798187,2019-03-05 16:14:18 UTC,I'm in favor of documenting standards for barcodes in Evergreen.
1798187,2019-03-05 16:29:03 UTC,I agree with having white space characters stripped from barcodes before saving and entering.
1798187,2019-03-05 19:04:08 UTC,The XUL client took any whitespace/newline/comma characters to be separators between barcodes.
1798187,2019-03-08 20:20:56 UTC,"My vote would be for each barcode on a separate line, strip all whitespace."
1798187,2019-03-10 14:23:52 UTC,"Updated branch at user/stompro/lp1798187-item-status-barcode-import-crlf
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1798187-item-status-barcode-import-crlf"
1798187,2019-03-10 18:30:25 UTC,"It may also be useful to have a pop-out help link right next to the file upload, so a user can just click the ""?"" and get a quick description of the file format required.  That is faster than trying to find the information in the docs."
1798187,2019-03-10 18:58:08 UTC,+1 to having a pop-out help.  You should be able to add one with the following code in the tt2 file:
1798187,2019-03-11 12:11:37 UTC,"+1 to reporting back on the failed barcodes, and less intrusive than XUL."
1798187,2019-03-12 18:52:00 UTC,"I force updated my last branch with the help popup, thanks Jane.  I couldn't position it right where I wanted it because the input button for the file upload is wide to show filenames, but I think it works fine where it is."
1798187,2019-03-12 21:17:43 UTC,"I'm fine with keeping the alert as part of this bug, but would not mind if others determined it was best to separate it."
1798187,2019-05-24 17:19:04 UTC,I've tested and signed off on the current patch:
1798187,2019-07-30 16:00:07 UTC,"this an issue at Albany Public Library.
Lynn"
1798187,2019-03-11 12:00:00 UTC,"+1 to reporting back on the failed barcodes, and less intrusive than XUL."
1798187,2019-03-05 15:11:30 UTC,I think documenting the barcodes standards for both items and patrons is a good idea.
1798187,2019-07-30 23:38:48 UTC,"Thanks, all!  I've pushed this to master, rel_3_3, rel_3_2, and rel_3_1 -- this will be included in the 3.4, 3.3.3, 3.2.8, and 3.1.14 releases."
1798187,2019-03-05 14:19:08 UTC,I don't think there would be many recent barcode formats that would have spaces that are not stripped out when scanned. The barcode on the label might be  5 07230 1013677 4 but scans as  50723010136774.
1798187,2019-03-05 14:45:43 UTC,+1 for the XUL regular expression.
1798187,2018-10-16 19:42:42 UTC,Attaching file without spaces
1798187,2018-10-18 17:19:35 UTC,"Marking this confirmed. We've had reports of failed file uploads, and this could be a contributing factor as I was able to duplicate on my side."
1798187,2018-10-18 18:38:43 UTC,This happens also in 3.1.5.
1798187,2019-02-26 23:06:08 UTC,That's https://bugs.launchpad.net/evergreen/+bug/1813954
1798187,2019-02-27 15:13:04 UTC,"Ah, many thanks Elaine.  LP search foils me yet again!  I've confirmed bug 1813954."
1798187,2019-02-26 22:53:44 UTC,Still in recent-ish master; noting that blank hard-return lines at the end of the barcode list will also cause a failure.
1798187,2019-02-27 20:48:43 UTC,"It looks like for some reason, the regex that strips trailing spaces and commas, is also stripping off \r (carriage returns), but only for the barcodes that don't have trailing spaces.."
1798187,2019-02-27 20:57:39 UTC,Looks like the simple fix is for the split to look for both CRLF and LF.
1798187,2019-02-27 21:13:49 UTC,"Branch at user/stompro/lp1798187-item-status-barcode-import-crlf
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1798187-item-status-barcode-import-crlf"
1798187,2019-03-04 21:21:15 UTC,Tested in sandbox.
1798187,2019-03-04 21:27:38 UTC,Created a file with blank lines at end (using above barcodes) and the file loaded with no problems
1798187,2019-03-05 02:15:11 UTC,"I was looking at how the xul client handled the barcode import, and it handled it using a single split statement."
1798187,2019-02-27 15:22:55 UTC,"I often have more luck searching in Google rather than LP. For this one, I just pulled up bugs I reported"
1798188,2018-10-30 22:45:02 UTC,"Reviewed:  https://review.openstack.org/613174
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d362e4285137de63e14f0fe8e24fa874a975660b
Submitter: Zuul
Branch:    stable/rocky"
1798188,2018-12-17 16:36:48 UTC,"Reviewed:  https://review.openstack.org/605154
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=983e6ea5518dee956d8054cd67dddbe98eab9f78
Submitter: Zuul
Branch:    master"
1798188,2018-12-13 21:32:06 UTC,"This is considered fixed since https://review.openstack.org/611214 merged, since an update to the rocky release note went directly to the stable/rocky branch and not to master. The patch used ""Partial-Bug"" in the commit message because it was intended to go alongside a release note patch to close out the bug, but the release note patch was stable-only and went only to the stable/rocky branch."
1798188,2018-11-06 06:00:59 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1798188,2018-10-31 18:16:56 UTC,"Reviewed:  https://review.openstack.org/614302
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2147093a966864434ab90d9167324c561e260fb5
Submitter: Zuul
Branch:    stable/rocky"
1798188,2018-10-30 22:44:52 UTC,"Reviewed:  https://review.openstack.org/611214
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2535b0261205ed80e1731451496caff19ef3f63
Submitter: Zuul
Branch:    master"
1798188,2019-01-31 13:44:15 UTC,"Reviewed:  https://review.openstack.org/630997
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7a0203c9ad1b10596f5de0d0954ee3ccb356d685
Submitter: Zuul
Branch:    stable/rocky"
1798188,2018-10-26 18:53:36 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: master
Review: https://review.openstack.org/611218
Reason: This should go direct to the stable branch and that is proposed here:"
1798188,2018-10-25 00:18:41 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/613174"
1798188,2018-10-17 02:57:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611218"
1798188,2018-10-17 02:35:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611214"
1798188,2018-10-16 20:04:26 UTC,"One suggestion in IRC today was that we could add a ""nova-status upgrade check"" which iterates the cell DBs looking to see if there are any non-deleted/disabled nova-consoleauth services table records and if so, check to see if there are no console_auth_tokens entries in that DB and if [workarounds]/enable_consoleauth is False, fail (or warn?) the status check b/c it means that cell is using nova-consoleauth but doesn't have tokens in the DB so it needs to run the consoleauth service."
1798188,2019-01-15 14:42:51 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/630997"
1798188,2018-10-30 16:57:05 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614302"
1798192,2019-02-12 13:49:47 UTC,"We can see this patch seems to be related:
https://review.openstack.org/#/c/613082/"
1798192,2018-10-17 15:15:02 UTC,Hi Emilien:
1798192,2018-10-17 14:57:58 UTC,"Hey Carol, is it related to https://review.openstack.org/#/c/582626/ ?"
1798199,2018-10-29 10:53:39 UTC,"Hi Erik, I also thought about this. But actually, we're not usually change this key.
For the deployment time, we can easy to define the key name or image tag by custom configuration following:"
1798199,2020-05-07 16:35:02 UTC,we still dont do this correctly.
1798201,2018-10-16 23:08:36 UTC,The strace fragment seems to come from VTE's rewrap-on-resize code.
1798204,2018-10-17 00:30:18 UTC,I'm pretty sure this will be additional flags for backup being passed to an older mongo (probably 2.4 in trusty).
1798204,2018-10-17 12:06:22 UTC,"yep. Trusty runs mongo 2.4 which doesn't have the same flags as 3.2 on
Xenial."
1798204,2019-01-09 20:51:13 UTC,Subscribed field-medium as this affects production environments.
1798204,2019-10-31 04:01:47 UTC,Removing from a milestone as this work will not be done in 2.4 series.
1798204,2020-10-09 19:30:50 UTC,"This is still happening on 2.7.4 controllers, subscribing field high"
1798212,2019-04-25 09:06:55 UTC,On 18.04 with kernel 4.15.0-46-generic #49-Ubuntu we hit the hang:
1798212,2018-10-17 03:01:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798212,2018-12-11 22:40:57 UTC,"We just hit a similar issue on Ubuntu 18.04. From the crash dump, I'm able to see this stack:"
1798212,2019-01-26 08:35:34 UTC,4.15.0-43-generic #46~16.04.1-Ubuntu SMP x86_64
1798212,2019-01-29 18:01:21 UTC,"I think in my case it was this issue that made systemd go into D state:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021
I was yet to test the fix in that bug but will do it as soon as it's available on 4.15.+"
1798212,2019-04-25 09:23:57 UTC,"This bug looks similar/related to:
https://github.com/systemd/systemd/issues/10123
https://www.spinics.net/lists/linux-fsdevel/msg132837.html"
1798213,2019-12-04 16:23:40 UTC,the issue looks like a corruption rather than a package bug
1798216,2018-10-17 23:26:37 UTC,Could you please run 'apport-collect 1798216' as that will gather log files from your upgrade attempt? Alternatively please add /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log as attachments to your bug report.
1798216,2018-10-18 01:05:24 UTC,Here is main.log
1798216,2018-10-18 01:05:39 UTC,Here is apt.log
1798216,2018-10-18 01:10:50 UTC,"After reviewing main.log and some googling, I stumbled upon https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1769184 in which it was suggested that ""unity"" might be the issue. So I removed unity and retried, and at this point the upgrade seems to be running. I think my main issue at this point is exactly what is said in https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1769184/comments/9 (i.e. I really wish I had gotten an warning message about unity, rather than just ""aborting"") but I'm okay if you decide to close this as a duplicate of 1769184"
1798221,2018-10-18 11:12:41 UTC,I don't think that https://bugs.launchpad.net/kicad/+bug/1798500 is a duplicate of this.
1798221,2018-10-18 13:51:21 UTC,"Fixed in revision eea949ce0a0ec625d675e89546959f60f0962aae
https://git.launchpad.net/kicad/patch/?id=eea949ce0a0ec625d675e89546959f60f0962aae"
1798221,2018-10-19 12:04:24 UTC,Does this affect the stable 5 branch?
1798221,2018-10-19 15:40:01 UTC,I could not recreate in 5.0.x
1798237,2018-10-17 11:28:06 UTC,"Thanks for reporting this bug.
I see this affects Tango and LateNight where I placed beatgrid controls next to the waeforms: the right-click control is just missing."
1798237,2018-10-17 15:05:59 UTC,https://github.com/mixxxdj/mixxx/pull/1847
1798237,2018-10-21 02:09:27 UTC,Ronso0: I can confirm that this is correct (I usually use the LateNight skin):
1798242,2018-10-17 04:53:09 UTC,"Andres: While the button shouldn't be there, I feel that the error not being presented is likely also a bug in itself. Should that be a separate bug? Not sure if that's an issue with this specific action or a general issue with surfacing errors back to the client."
1798251,2018-10-17 06:37:22 UTC,"I just tried booting the USB drive of ubuntu-18.04-desktop-amd64.iso on a different workstation. The drive was picked up for the boot menu and the grub boot menu was displayed. I selected ""Try Ubuntu without installing"" and it seemed to start booting (flash screen appeared). Then after a while it dropped down to BusyBox. The message it gave might be of some help: ""(initramfs) Unable to find medium containing a live file system"". I then switched off the PC and booted again. This time I selected ""Install Ubuntu"" from the grub boot menu, but it dropped down to BusyBox again with the same message. If there is any way I can get more information from BusyBox, please let me know."
1798251,2018-10-17 08:20:30 UTC,I have been able to successfully create a USB drive that boots Ubuntu 18 ISO images. The web site that I used for information is https://www.splitbrain.org/blog/2012-12/22-the_ultimate_usb_stick_setup .
1798251,2018-10-17 06:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798253,2018-10-25 07:54:53 UTC,Not seen in the latest Netronome build 73.
1798253,2018-10-23 08:23:50 UTC,"Pieter seems to have fixed the issue. Need to use build 73 to test the same.
Will update after testing this."
1798259,2018-11-07 18:37:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798265,2018-10-17 07:34:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611254"
1798265,2019-06-05 02:40:55 UTC,"Change abandoned by Wenran Xiao (<email address hidden>) on branch: master
Review: https://review.opendev.org/611254"
1798293,2018-10-17 14:11:37 UTC,"The actions work in GNOME/cosmic, there is no change also in that update that concern the desktop entry"
1798293,2018-10-17 14:52:44 UTC,"I just found I manually patched my Thunderbird but this change got now overridden by a system update.
Does Ubuntu Gnome perhaps also accept ""Unity"" for OnlyShowIn? In any case, KDE should be added to the list."
1798307,2020-07-30 09:59:51 UTC,"Due to the age of the bug report it's possible it got already fixed as lots of changes have been merged since the bug report. I'll mark this as Invalid, but if you encounter the issue with the latest tempest codebase as well, feel free to reopen."
1798307,2018-10-17 09:00:05 UTC,Important lines are with my custom log outputs:
1798307,2020-03-03 14:50:00 UTC,Is this still reproducible? I'm wondering if there is any chance this could have resulted in https://bugs.launchpad.net/tempest/+bug/1860294 ?
1798307,2018-10-17 08:53:16 UTC,I am using tempest v18.0.0 with cirros-0.3.5. Openstack release Queens deployed with OSA 17.1.2
1798309,2018-10-17 09:07:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1798309,2018-10-17 09:56:50 UTC,Right unsure what ubiquity can do there out of restarting gnome-shell (or does reloading would be enough?) which would lead to flicker
1798313,2019-06-28 21:04:47 UTC,"The issue is fixed in the current version, a SRU has been uploaded to bionic now"
1798313,2019-07-10 08:19:41 UTC,I can confirm that the package linked to in #13 does indeed fix the problem.
1798313,2019-06-28 21:04:59 UTC,(the ppa build has been deleted since replaced by the SRU)
1798313,2019-07-10 19:51:06 UTC,"Hello Rami, or anyone else affected,"
1798313,2019-04-11 18:30:18 UTC,Yes I also ran into this same problem.
1798313,2019-07-11 06:26:29 UTC,I've tested the 3:20161105-1ubuntu3 version in proposed and it fixes the bug for me. I've changed the tag accordingly.
1798313,2019-07-18 08:09:14 UTC,"The verification of the Stable Release Update for iputils has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1798313,2019-07-18 08:19:14 UTC,This bug was fixed in the package iputils - 3:20161105-1ubuntu3
1798313,2019-06-28 11:59:07 UTC,Could those having the issue try if the deb on https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/10307594/+listing-archive-extra fixes their issue (I don't know enough ab out IPv6 to have those commands return something else than 'network unreachable')
1798313,2019-07-10 21:57:00 UTC,"All autopkgtests for the newly accepted iputils (3:20161105-1ubuntu3) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1798313,2019-04-24 13:38:47 UTC,Is there any plan to fix this bug in the 178.04 LTS version?
1798313,2019-04-11 16:51:56 UTC,"I have hit this issue too. via iputils-tracepath under ubuntu 18.04. There are actually 2 issues with this, one with ipv6 address and the other to an ipv6 hostname.
https://github.com/iputils/iputils/issues/68
https://github.com/iputils/iputils/issues/81"
1798313,2019-04-11 16:53:54 UTC,"and no, using the traceroute package does not fix the issue
dudek@test-box:~$ sudo apt-get install traceroute
[sudo] password for adudek:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  traceroute
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 45.4 kB of archives.
After this operation, 152 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 traceroute amd64 1:2.1.0-2 [45.4 kB]
Fetched 45.4 kB in 3s (14.3 kB/s)
Selecting previously unselected package traceroute.
(Reading database ... 103312 files and directories currently installed.)
Preparing to unpack .../traceroute_1%3a2.1.0-2_amd64.deb ...
Unpacking traceroute (1:2.1.0-2) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up traceroute (1:2.1.0-2) ...
update-alternatives: using /usr/bin/traceroute.db to provide /usr/bin/traceroute (traceroute) in auto mode
update-alternatives: using /usr/bin/lft.db to provide /usr/bin/lft (lft) in auto mode
update-alternatives: using /usr/bin/traceproto.db to provide /usr/bin/traceproto (traceproto) in auto mode
update-alternatives: using /usr/sbin/tcptraceroute.db to provide /usr/sbin/tcptraceroute (tcptraceroute) in auto mode
adudek@test-box:~$ traceroute6 -V
traceroute6 utility, iputils-s20161105
adudek@test-box:~$ traceroute -V
Modern traceroute for Linux, version 2.1.0
Copyright (c) 2016  Dmitry Butskoy,   License: GPL v2 or any later
adudek@test-box:~$ traceroute6 2001:4860:4860::8888
traceroute to 2001:4860:4860::8888 (2001:4860:4860::8888) from 2003:8:8:4:20c:29ff:fe59:583c, 30 hops max, 24 byte packets
sendto: Invalid argument
 1 traceroute: wrote 2001:4860:4860::8888 24 chars, ret=-1"
1798313,2018-11-21 17:04:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798313,2019-04-03 01:09:59 UTC,Hello!
1798313,2018-12-10 11:37:58 UTC,You can use the traceroute6 or traceroute from the package traceroute.
1798313,2018-12-09 10:42:52 UTC,"Is there a workaround to get this working in Ubuntu 18.04, until the bug is deemed important enough to actually fix?"
1798313,2018-12-04 14:38:32 UTC,"While reviewing the nominated bugs we decided it would be good to fix but not important enough to rls track it, so tagging rls-bb-notfixing"
1798313,2018-11-29 15:44:54 UTC,"The Debian bug referenced is fixed in the version your are using/bionic,
https://launchpad.net/ubuntu/+source/iputils/3:20161105-1ubuntu1"
1798313,2018-11-28 16:20:04 UTC,"This is fixed in Debian and upstream. As this binary is 100% useless, it really needs to be updated."
1798315,2018-10-17 09:30:08 UTC,This change was made by a bot.
1798318,2018-10-20 07:50:58 UTC,The following 2 files need to be fixed when a language is uninstalled:
1798322,2018-10-17 10:51:39 UTC,It seems to be a secure boot / UEFI issue. Retrying with the same bootentry and a minimal install also failed. I briefly saw something about grub not being able to write somewhere in the install console.
1798323,2019-01-24 16:30:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798326,2019-01-25 04:26:53 UTC,"Hi Martin, do you have any progress on this issue?"
1798326,2019-01-25 07:44:40 UTC,Fix proposed here - https://review.openstack.org/#/c/608704/.
1798326,2019-01-25 17:29:36 UTC,Fix Committed status is for when the patch is merged.
1798326,2019-06-17 22:10:39 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/608704
Reason: No response to comments since January and is now in merge conflict so I'm going to abandon this."
1798326,2019-06-19 08:44:18 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666245"
1798326,2019-06-19 08:45:32 UTC,"Change abandoned by Martin Midolesov (<email address hidden>) on branch: master
Review: https://review.opendev.org/608704
Reason: New branch is created for that change.
https://review.opendev.org/#/c/666245/"
1798326,2020-05-18 12:47:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/728860"
1798333,2020-06-02 02:23:29 UTC,Hi Rosika.
1798333,2019-10-11 11:30:03 UTC,"""Is there a way of stopping this behaviour?"""
1798333,2019-10-12 11:33:46 UTC,"Hi Moshe and thanks for your reply,"
1798333,2020-06-02 13:36:48 UTC,"Hi Takayuki Tokuyoshi (powtok),"
1798333,2019-10-12 06:41:37 UTC,"I hope that I understand your issue correctly, If I remember, I removed the volume control indicator, added the indicator applet and ticked/unticked the sound menu option. Might be something similar. My idea was that some indicators don't exactly fit the distro. I would try removing your systemload-indicator/indicator-multiload or other indicators."
1798333,2019-10-10 13:58:32 UTC,"Hi,"
1798333,2019-10-10 14:20:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798333,2019-10-11 11:54:35 UTC,"Hello Moshe,
thanks for your reply."
1798346,2018-10-17 13:05:46 UTC,What bug does this cause not having this a configurable option?
1798346,2018-10-25 13:02:39 UTC,In the case when volume can't be deleted immediately (active flattening for example) retry tries to do it again and again but always using backoff_rate = 2 that means that interval between attempts is growing. It can be inconvenient for Nova when it tries to clean up instances which are erroneously still running after having been deleted or for cloud operators who want to change the default behaviour. So actually it's not a bug but an improvement.
1798347,2018-10-17 19:11:17 UTC,">I read a popup when print start, but immediately another popup
> says to me that print is stopped.
"
1798347,2018-10-21 18:54:16 UTC,No further information from the OP. Progress is impossible.
1798349,2018-10-17 10:53:47 UTC,Both the exfat-fuse and exfat-utils packages are installed (version is 1.2.8-1)
1798349,2018-10-17 10:55:41 UTC,"Results of ""dumpexfat -s /dev/sdb1"""
1798349,2018-10-17 10:58:49 UTC,"Also the drive is a Sandisk USB Ultra Fit, may be relevant as this particular drive overheats a lot"
1798350,2018-10-17 11:07:33 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1798358,2018-11-09 09:35:42 UTC,"Tested with P8 ""modoc"" + Bionic 4.18 kernel"
1798358,2019-12-11 11:24:28 UTC,The error on Eoan 5.3 P8 (node modoc) is:
1798358,2019-12-11 11:27:38 UTC,BTW this test has passed on the P9 node baltar with the same Eoan kernel.
1798364,2019-10-25 21:06:28 UTC,"@wxl   I upgraded my debian-testing box last night (#lubuntu-dev) so it obtained the 3.9.0-1, copied to code to a NFS server and ran on my primary [Lubuntu] 20.04 box; it reports LXDE :("
1798364,2019-10-25 07:00:08 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1798364,2019-10-25 17:35:54 UTC,"With functioning fixes in upstream master, this assumedly will be fixed in the next version, i.e. >3.9.0."
1798364,2019-10-07 06:38:45 UTC,Response from upstream - hopefully fixed..
1798364,2019-10-25 06:52:11 UTC,"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
purpose of this test is to start looking for old bugs & confirm focal impacted; these bugs are old & upstream issues and will impact very few end-users (impact me thus why chased)
..
installed screenfetch; package hasn't been updated yet (or upstream fix didn't work) - https://bugs.launchpad.net/ubuntu/+source/screenfetch/+bug/1798364"
1798369,2019-06-03 21:44:29 UTC,This option is still present in Disco and it fails in the same way.
1798369,2020-08-20 17:27:44 UTC,Digging into this a bit further the apt-clone file which ubiquity has created in /target/ubiquity-apt-clone/apt-clone-state-ubuntu.tar.gz does not actually have the packages listed in it which I'd previous installed on my system.
1798369,2020-08-19 22:26:11 UTC,On Ubuntu 20.04 the error message I'm seeing when trying to manually run the apt-clone command from the Ubuntu 20.04 Live CD is:
1798369,2020-08-18 16:48:05 UTC,"eoan has reached end of life, so this bug will not be fixed for that release"
1798369,2019-06-03 21:53:13 UTC,"Actually I did not see an error message regarding the log file, nor can I find one on disk, but the packages I had installed before the reinstall are no longer installed."
1798369,2019-03-21 15:49:01 UTC,Is this option still presented in disco or has it been removed?
1798369,2020-09-16 19:51:45 UTC,This bug was fixed in the package ubiquity - 20.10.10
1798369,2018-10-17 15:01:02 UTC,"I installed cosmic in a KVM vm using virt-manager, then ran update-manager to update a few packages leaving the lock file behind, restarted to the installer, chose reinstall and the installer is stuck in systemd[1]: Started Cleanup of Temporary Directories."
1798369,2018-10-17 14:07:31 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1798369,2018-10-17 13:53:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798369,2018-10-17 13:53:33 UTC,Also seen running 'manual partitioning' test case.
1798369,2020-08-25 12:49:12 UTC,"OK.
Thanks!
RGMüller"
1798369,2018-10-17 16:28:37 UTC,"We decided this is not a release blocker as actually, what I missed mentioning earlier, this does not cause actually the installation to fail (the title was wrong). The install still finishes but at the end the user is presented with an error message that the refresh of installed applications failed. The message however does mention that everything is ok with the system just with the applications left in previous state and risk of them not working without a reinstall (or something similar). The system is bootable and still works."
1798369,2020-09-15 22:55:50 UTC,"This process which reinstalls your existing applications has been removed from ubiquity as it was broken and misleading in that it frequently would not reinstall many of the applications which were installed on the system. So in the interest of providing a better user experience, by not creating expectations that would not be met, we have removed that part of the ""Reinstall Ubuntu"" option."
1798370,2020-03-07 11:27:39 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1798378,2018-10-18 16:38:51 UTC,"I installed flashback and tested. The problem isn't that DESKTOP_SESSION is empty; it's set to ""gnome-flashback-compiz"", and it fails because compiz isn't installed."
1798378,2018-10-18 13:43:43 UTC,This is from a server that started with standard Ubuntu desktop (not MATE).
1798378,2018-10-17 13:46:24 UTC,What is the output of sudo ltsp-info?
1798378,2018-10-18 08:59:44 UTC,"Additionally to the output of `sudo ltsp-info`, please also provide the output of the following commands:
ls -l /etc/alternatives/x-session-manager
egrep -R '^Exec=|^DesktopNames=' /usr/share/xsessions/"
1798381,2019-05-21 04:17:22 UTC,[Expired for Dr. Geo II because there has been no activity for 60 days.]
1798385,2019-09-19 14:47:49 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1798400,2020-03-17 19:10:05 UTC,"The premise is that my ignorance on BT is complete. After some investigation, it is my understanding that RFCOMM channels are to RFCOMM communication a bit like ports in TCP and UDP, with the main difference that while there are really a lot of TCP/UDP ports and some of them are reserved as ""well known ports"", the number of channels in RFCOMM is extremely limited, so that there cannot be well known ports. Furthermore, I understand that no one should ""hardwire"" RFCOMM channels and that channels should be released whenever not strictly needed."
1798400,2019-09-04 10:18:27 UTC,Wonder if it could be useful to kindly ask Andrzej Hunt if he can look into the issue. If I am not wrong he is the author of the current bluez 5 code in Impress.
1798400,2020-02-20 18:19:10 UTC,Thanks for the analysis!
1798400,2020-02-20 18:08:27 UTC,"This issue was annoying me for a while too. So I sat down and debugged bluez to see why the bind fails: LO is using the default channel (3) for the RFCOMM protocol as it should be. However, the bind call fails, because another process has already bound that channel via DBUS. Changing the default RFCOMM channel in the bluez source temporaliy to 2 (UDP, unused) and recompiling bluez made remote impress work immediately!"
1798400,2019-12-27 03:12:29 UTC,Can confirm that my samsung galaxy running Android 9 and linux mint 19.3 are still not working appropriately with the impress remote. It refuses to connect via bluetooth no matter what I do.
1798400,2019-12-19 10:29:47 UTC,"Andrzej, I am CC-ing you on this, because I believe that you were one of the original corder of the BT code for the impress remote on linux. I hope that you may able to provide some advice on this. If I'm wrong, please take my apology for the noise."
1798400,2019-12-19 10:18:04 UTC,The bug is also confirmed in the ubuntu launchpad at https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400.
1798400,2019-12-10 13:53:39 UTC,@John Poole
1798400,2019-12-10 13:43:50 UTC,Issue still present in LibO 6.4.3.1.
1798400,2019-10-06 13:11:28 UTC,"Here is a link to the code (& log) regarding the impress remote project:
https://cgit.freedesktop.org/libreoffice/impress_remote/"
1798400,2019-06-11 03:01:43 UTC,[Automated Action] NeedInfo-To-Unconfirmed
1798400,2019-09-04 10:12:24 UTC,Issue persists with current LibO 6.3.1.2 and most likely due to the fact that the bluetooth stack on linux (bluez) has changed in the past years and impress has not cought up.
1798400,2019-06-10 15:40:43 UTC,"Thank you for reporting the bug.
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build"
1798400,2019-06-10 16:32:40 UTC,"Cannot test daily builds right now, but 6.3.0 beta 1 still has the issue.
Launching impress reports:
bluetoothd[1386]: RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98)
in the system logs and then the remote app cannot contact the host."
1798400,2019-05-04 16:40:31 UTC,Can confirm on Arch Linux with LO version 6.2.3.2
1798400,2018-12-21 21:44:15 UTC,Still present in 6.2.0 RC 1
1798400,2018-11-03 11:43:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798400,2018-10-18 01:59:19 UTC,"I agree this is most likely a LibO bug, as is:
https://bugzilla.redhat.com/show_bug.cgi?id=1581879"
1798400,2018-10-17 16:56:19 UTC,"I think that the issue can be either a bug in the bluetooth stack or merely something that has /changed/ in the bluetooth stack, that libreoffice has not tracked properly. Hence, I have also opened a bug upstream for LibO, mentioning this one."
1798400,2018-10-17 16:53:57 UTC,"I have stayed a long time without trying impress remote, so I do not know exactly when the issue started. However, I am sure that last year at this time (aka on 16.04) the issue did not exist."
1798400,2018-10-17 15:57:39 UTC,"Description:
The fault seems to be on the Libreoffice application running on the computer, not on the android impress remote app."
1798400,2018-10-17 15:24:35 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1798400,2018-10-17 15:12:44 UTC,See https://bugzilla.redhat.com/show_bug.cgi?id=1581879
1798404,2018-10-17 15:52:22 UTC,"I am maintaining ubuntu-packaging-guide packaging/infrastructure, but I don’t really have time for content. So merge proposals (in bzr :)) are welcome."
1798415,2018-10-17 17:10:15 UTC,This maybe expected behavior; assigning to the design prime to review/confirm.
1798415,2018-10-24 18:03:31 UTC,"From Paul-Emile:
I have reproduced the issue."
1798415,2018-10-24 18:03:55 UTC,Targeting stx.2019.03 as best effort; lower priority as this is just a log getting repeated.
1798415,2019-07-02 09:59:39 UTC,"I am using the 2019.06.26/06.23/06.20 version of the ISO, duplex mode, which does not reproduce the phenomenon you describe.
The operation is as follows:
0. Operate in controller-0 and controller-1 respectively.
1. sudo touch /home/sysadmin/TEMP
2. sudo chmod 755 /home/sysadmin /TEMP
3. Append content to monitored file
echo ""ls"" | sudo -S tee -a /home/sysadmin /TEMP
4. Execute created file
sudo /home/sysadmin /TEMP
5. sudo rm /home/sysadmin /TEMP"
1798415,2019-07-04 05:47:24 UTC,"I am using the 2018.10 version of the ISO, duplex mode and still have not reproduced this problem."
1798415,2019-07-04 09:04:21 UTC,"OK, let me mark it as ""fix released"" for now. And if bug reporter found it reproducible, please re-open it."
1798415,2019-07-04 15:53:17 UTC,"Cindy, we only use ""Fix Released"" if we definitively know that there is a code fix that addressed the issue. This doesn't seem to be the case here. The comments above only indicate that the issue is not reproducible. In this case, we have been using the ""Invalid"" status since there is ""no reproducible"" status in launchpad."
1798415,2019-08-20 13:41:00 UTC,Original issue only happens with extended security profile (as opposed to the default standard security) when IMA is enabled.
1798425,2018-10-17 23:28:18 UTC,The request to use apport-collect is unnecessary as I've confirmed that what you've said is true. Thanks for reporting a bug!
1798425,2018-10-17 18:10:01 UTC,"Hi Cristian,"
1798425,2018-10-17 17:38:45 UTC,"Hello P1h3r1e3d13,"
1798425,2018-10-17 17:33:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798429,2018-10-17 18:04:37 UTC,"Hello Efthimios,"
1798429,2018-10-17 18:07:37 UTC,"It seems that this is for GDM
--
Cristian"
1798429,2018-10-17 18:26:49 UTC,"It says package gdm is not installed. May I ask, what does the package do? Thank you."
1798429,2018-10-17 18:51:00 UTC,This is a feature request for gdm.
1798429,2018-10-17 18:51:46 UTC,"Efthimios, you don't need to worry about providing the apport information for this bug. We already have all the information we need for this bug."
1798433,2018-10-17 18:36:23 UTC,"See related bug 1794588. Depending on how that bug is resolved, it could be a duplicate of this one."
1798440,2019-10-09 19:30:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1798440,2019-12-09 04:17:31 UTC,[Expired for seahorse (Ubuntu) because there has been no activity for 60 days.]
1798444,2019-04-12 01:55:29 UTC,"This will come as part of porting Eeschema to the new tool framework (currently only the rendering code is ported to GAL, it is still not making use of the tool framework which is what is responsible for the nicer selection behavior in PcbNew)"
1798444,2018-10-31 15:58:16 UTC,"I see this in the current master. Left-right selection is a yellow-edged box, right-left is a blue-edged box. However, they both have the behaviour Fabian reports: selection of anything inside OR intersected by it. This should be the behaviour of only the blue-edged right-to-left action."
1798444,2018-10-19 08:12:33 UTC,"I think the direction aware selection is only implemented in GAL. (I didn't check it right now, so maybe you need to be sure to be in GAL)"
1798444,2018-10-22 19:22:53 UTC,Hi Nick
1798444,2018-10-18 13:49:17 UTC,"Do you mean a selection that is dragged from top-left to bottom-right vs. one that is dragged from bottom-right to top-left?  The borders are different colours, no?"
1798444,2018-10-18 17:15:27 UTC,"Yes, but it always selects anything that it's partially inside the selection box, no matter how the selection was started."
1798450,2018-11-16 19:10:58 UTC,"This also affects the libreoffice snap, and more generally all snaps using the desktop helpers (and it should be fixed there)."
1798450,2018-11-16 19:12:54 UTC,And I filed https://github.com/ubuntu/snapcraft-desktop-helpers/issues/167 to track the issue where it belongs.
1798450,2018-11-21 16:06:39 UTC,"This is a runtime thing, not build time"
1798450,2018-11-29 13:39:36 UTC,"I don't think we want (or can) change HOME in snapd (due to undesired consequences and breaking many snaps), it works as designed, i.e. gives snaps dedicated areas where they can freely write data to, including hidden files; access to real user $HOME may not even be allowed unless home interface is connected. I see an alternative approach that only affects file picker is already discussed in the snapcraft-desktop-helpers issue above, for now marking it invalid for snapd."
1798450,2020-02-18 21:28:27 UTC,"Just adding that this issue has recently affected my work flow trying to upload a file to social media site in hopes of generating actual deniro . . . but could not get my own files to show up in what I was hoping would be my /home directory . . . but was instead a ""snap"" ""virtual home"" directory, so that it showed as ""empty"" . . . ??  very disruptive to routine uses . . . ???  I posted to wxl that if this was to prevent me from uploading his files to my social media then that ""makes sense"" . . . but to prevent me from simply uploading my own files n the system I'm booted and logged into . . . non-sensical . . ."
1798450,2020-04-23 22:26:51 UTC,So the issue is somewhat still present with newest snap system. I'm on 20.04 LTS.
1798450,2020-04-23 22:31:39 UTC,Correction it seems that you can select an image from your Images folder but it doesn't actually get uploaded.
1798451,2018-10-23 23:11:48 UTC,"Considering the fact that both Ubuntu and Elementary require SSE to boot, I'd wait to get decoding fixed. I wrote a test kernel module that reliably reproduces your issue on qemu edu device. Whenever QEMU prints Unimplemented handler Instruction pointer only moves two bytes further, instead of the instruction length. That corrupts code execution as the next instruction after unimplemented handler is decoded from the wrong address."
1798451,2020-11-12 07:17:05 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1798451,2019-09-27 21:20:21 UTC,Adding a ditto to this.
1798451,2018-12-26 22:50:15 UTC,Still an issue on 3.1.0 and now Mojave
1798451,2018-10-22 18:49:57 UTC,"Thanks for helping Roman, so I take it my options at this point are wait for VMEXIT to be implemented or try to find a linux distro that doesn't require SSE?"
1798451,2018-10-20 10:20:20 UTC,I've had issues with multiple vcpus previously.
1798451,2018-10-20 20:09:04 UTC,Also seeing quite a few of these errors
1798451,2018-10-20 20:05:23 UTC,"Thanks for replying Roman, I switched to your tap but even before that I'm not struggling to get the machines to boot even without the smp/numa lines... vga std flashes a lot then hangs with a black screen and a blinking cursor whereas vga vmware quite unexpectedly."
1798451,2018-10-22 15:47:04 UTC,I have tried to run the OS and I can confirm that some instructions that require VMEXIT are not implemented. In your case that's 0F7F or MOVQ (mem from mmxreg) from MMX. In my case that's 0F11 or MOVUPS(xmmreg1 to mem) from SSE.
1798454,2018-10-17 19:44:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611423"
1798454,2021-02-19 15:06:53 UTC,This was fixed in https://review.opendev.org/c/openstack/cinder/+/597148
1798459,2019-06-27 18:06:14 UTC,This should be addressed through calling HPE support.
1798464,2018-11-02 21:13:26 UTC,Let's push it to 6 and see if we can come up with a solution.
1798464,2018-11-02 20:43:14 UTC,"I like ""won't fix"" better.  ""Triaged"" will show up in searches and reduce the signal-to-noise ratio, making it less likely that bugs that can be fixed will be found and dealt with."
1798464,2018-11-02 18:54:08 UTC,"Perhaps ""Triaged"" is better.
""wont fix"" looks like we do not want to fix it, but this is not the case."
1798464,2018-10-19 08:21:57 UTC,Negative objects are incorrectly shown in Cairo canvas (they are drawn on top of other items).
1798464,2018-11-02 18:26:39 UTC,"If we cannot fix this in Cairo, should the status of this bug report be wont fix since there is no can't fix?"
1798468,2020-04-10 19:49:43 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: driverfixes/newton
Review: https://review.opendev.org/687126
Reason: driverfixes branches are now EOL and going away."
1798468,2019-09-11 13:37:21 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/681477"
1798468,2019-10-07 18:08:06 UTC,"Fix proposed to branch: driverfixes/newton
Review: https://review.opendev.org/687126"
1798468,2019-10-07 15:04:15 UTC,"Reviewed:  https://review.opendev.org/681477
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=936a4aef6e02b6f8d96cb3510ca94c2b17eb73cd
Submitter: Zuul
Branch:    stable/ocata"
1798468,2019-10-04 13:01:04 UTC,This issue was fixed in the openstack/cinder 12.0.9 release.
1798468,2019-10-04 08:52:02 UTC,This issue was fixed in the openstack/cinder 14.0.2 release.
1798468,2019-09-27 09:03:22 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1798468,2019-09-10 23:34:53 UTC,"Reviewed:  https://review.opendev.org/680237
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=01d3d2ee242f265ce9639349a8353891284c8142
Submitter: Zuul
Branch:    stable/pike"
1798468,2019-10-04 13:00:19 UTC,This issue was fixed in the openstack/cinder 13.0.7 release.
1798468,2019-09-04 22:48:07 UTC,"Reviewed:  https://review.opendev.org/679863
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=f3639046cbdc5202340ffd7a691c21ce3b6cc1bf
Submitter: Zuul
Branch:    stable/queens"
1798468,2019-08-23 17:54:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678278"
1798468,2019-08-27 18:13:54 UTC,"Reviewed:  https://review.opendev.org/678278
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=33a3a4bf6fe72b093702922e2e5f102d06249375
Submitter: Zuul
Branch:    master"
1798468,2019-08-27 18:26:58 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/678936"
1798468,2019-09-05 00:10:09 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/680237"
1798468,2019-08-29 19:17:24 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/679322"
1798468,2019-09-03 21:25:28 UTC,"Reviewed:  https://review.opendev.org/679322
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=058700edc93a5815bedc8c7f53cccd672618019c
Submitter: Zuul
Branch:    stable/rocky"
1798468,2019-09-03 21:29:38 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/679863"
1798469,2020-07-19 08:44:05 UTC,"Just noticed this fix was in and wanted to say thanks! It was always a minor annoyance, but it's really nice to not have to mess with the settings on every start. Mixxx is now even more awesome :)"
1798471,2018-10-17 22:50:58 UTC,Some questions:
1798473,2020-02-24 07:00:23 UTC,This has since been addressed by adding extra bindings for checking against all endpoints in the Keystone catalog.
1798481,2018-11-06 19:19:59 UTC,"I really don't have much experience reporting bugs with large open projects. I tried asking in what I thought was the correct venue but didn't get a response. As long as people who were in my situation can discover the solution via finding this report or the answer I posted to the related question on askubuntu.com then I'm satisfied and I don't mind this report being closed (""invalid"" I guess, not sure what statuses are available). I'd close it myself but I can't find an affordance for doing that."
1798481,2018-11-05 18:42:18 UTC,"Steve, did you contact the Xfce developers?"
1798481,2018-10-18 21:08:11 UTC,Thanks for the investigation!
1798481,2018-10-18 21:07:56 UTC,"It seems the symptom is specific to xfce, where the values in xfconf seem to control the relevant behavior. The cursor blinking timeout for GTK applications can be controlled by adding a new integer key ""/Gtk/CursorBlinkTimeout"" to the ""xsettings"" channel."
1798481,2018-10-18 21:02:20 UTC,"Or perhaps such an addition wouldn't be appropriate because it only applies to GTK applications and the xfce team would only want to include such a control if it were universal? In any case, I'll try to bring this to the attention of the xfce maintainers (and add answers to askubuntu.com, etc)."
1798481,2018-10-18 20:58:15 UTC,"I grepped for 463 against everything in my home directory and this was at the top of the list:
.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml:
    <property name=""CursorBlinkTime"" type=""int"" value=""463""/>"
1798481,2018-10-18 18:03:58 UTC,"#2 Thanks for the comment. I'm accustomed to blinking following focus. The values I have in dconf are:
cursor-blink: true
cursor-blink-time: 1200
cursor-blink-timeout: 10000"
1798481,2018-10-18 18:32:48 UTC,"> cursor-blink-time: 1200
> cursor-blink-timeout: 10000
> time=463 timeout=10
"
1798481,2018-11-06 21:44:12 UTC,Your suggestion in comment #8 looks like something that is worth to forward to the Xfce bug tracker (Xfce Core -> Xfce4-settings).
1798481,2018-10-18 16:15:09 UTC,"VTE does have code in place to support these variables and they work for me. No need for reboot, not even to restart gnome-terminal, it should pick up the change immediately."
1798481,2018-10-18 12:44:11 UTC,"Those are VTE based terminal emulators, so I suggest that you forward this issue to the GNOME developers."
1798481,2018-10-18 19:48:12 UTC,The blink time does seem to be a bit less than a half second. If I count the seconds out loud it blinks twice each second with a little time to spare.
1798485,2018-10-18 09:18:13 UTC,Attached is a patch along with tests that check the assertion behavior.
1798485,2018-10-18 08:41:00 UTC,"Possible patch against mgo/txn:
$ git diff flusher.go
diff --git a/txn/flusher.go b/txn/flusher.go
index c0fc36d..012933f 100644
--- a/txn/flusher.go
+++ b/txn/flusher.go
@@ -895,6 +895,14 @@ func (f *flusher) apply(t *transaction, pull map[bson.ObjectId]*transaction) err
                        }
                case op.Assert != nil:
                        // Pure assertion. No changes to apply.
+                       if len(pullAll) >= 20 {
+                               var d bson.D
+                               if d, err = addToDoc(d, ""$pullAll"", bson.D{{""txn-queue"", pullAll}}); err != nil {
+                                       return err
+                               }
+                               chaos(""update asserted document"")
+                               err = c.Update(qdoc, d)
+                       }
                }"
1798485,2018-10-23 19:37:53 UTC,"https://github.com/juju/juju/pull/9340 was merging into 2.3
https://github.com/juju/juju/pull/9359 is merging 2.3 into 2.4"
1798485,2018-10-18 08:29:40 UTC,Thank you tremendously for the dump. This is what we noted:
1798489,2018-10-19 14:05:48 UTC,This issue was fixed in the openstack-infra/shade 1.30.0 release.
1798490,2018-10-18 17:10:26 UTC,"This is actually not an issue specific to tutorials but happens with every document if you have ""Save and restore window geometry for each document"" in Preferences -> Interface --> Windows enabled and the location stored in the document does not match your monitor set-up (specifically if the coordinate (0,0) is outside of the visible desktop area, which is the case for you (it's in the upper left corner of the combined screen area)."
1798490,2020-03-21 10:24:20 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1798492,2019-02-14 19:15:19 UTC,We do remember the last location of various windows and many don't check that their last location is still on the screen when they pop up again.  It should be a simple check to add this when creating a new window.
1798492,2019-02-14 18:59:25 UTC,"No, I don't believe that is the issue. This happens always, even when I go from a single laptop screen to a single external screen. All other programs work, including Kicad, it's just the Kicad popups that don't show up.  I don't have to restart any other programs but Kicad."
1798492,2019-02-14 08:57:35 UTC,Isn't this just a matter of your screen did't fallback to a single monitor?
1798492,2018-12-14 22:50:06 UTC,I can now confirm that this problem still exists in kicad 5.0.2.
1798492,2018-11-27 19:55:50 UTC,"I installed that version and it reports to be version 5.0.1-44-g50eedcf0b.  I then installed the patch kicad-patched-223-5.0.1-47-gf66ccfb64-x86_64.exe, but Kicad still reports version 5.0.1-44-g50eedcf0b.  My popup windows are still hidden, so these versions haven't solved the problem yet.  I hope I'm just not using the right version."
1798492,2019-02-13 04:17:33 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1798492,2018-11-26 17:24:41 UTC,"I haven't tried on any new versions, though I'd be happy to.  I found a file with those tags, but it's under the patch directory and is only a patch.  I don't know which version to install before installing this patch, so could use some guidance."
1798492,2018-11-26 16:44:26 UTC,Have you tried the latest stable release?  I cannot duplicate this with (5.0.1-47-gf66ccfb64) which will be tagged as 5.0.2.
1798492,2018-10-18 21:22:14 UTC,"Forgot to add, to fix this problem, I have to close down Kicad completely, then restart it.  Also, all popups are invisible in both layout and schematic capture."
1798492,2018-11-26 17:50:06 UTC,The latest stable build (which should become 5.0.2 in about two weeks) can be found at http://downloads.kicad-pcb.org/windows/testing/5.0/.
1798493,2018-10-18 00:44:02 UTC,https://review.openstack.org/#/c/611469/
1798493,2019-03-08 04:20:23 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1798508,2018-10-18 04:11:39 UTC,related
1798512,2019-06-21 11:43:28 UTC,"initramfs hooks of cryptsetup got ""smarter"" and generate dev-mapper name as seen in d-i as the source device...
... which has wrong X/-partX naming for multipath devices
... thus partman-multipath, should rename multipath devices ""for target"" once partman is finally done, as otherwise at update-initramfs an invalid crypttab is generated and included in the initramfs irrespective of what /target/etc/fstab says."
1798512,2018-10-18 04:58:35 UTC,"Filed in partman-crypto for now, I'm guessing that's what writes crypttab, and it might not be aware of multipath's special way of addressing devices?"
1798512,2018-10-18 05:29:01 UTC,"partman-crypto looks fine at first glance, but I'm starting to suspect multipath-tools might be addressing devices differently in d-i; possibly because of how we build the udeb, or what we have in multipath.conf?"
1798512,2018-10-18 06:07:30 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1798512,2018-12-18 04:17:19 UTC,[Expired for multipath-tools (Ubuntu) because there has been no activity for 60 days.]
1798524,2020-11-03 02:36:49 UTC,https://github.com/linux-test-project/ltp/commit/100e3fed3126e41ac7d44f932588f40f6bc096aa
1798524,2019-07-10 08:08:02 UTC,"Issue reported upstream:
https://github.com/linux-test-project/ltp/issues/542"
1798524,2019-07-10 07:26:43 UTC,This is caused by the e2fsprogs package on Xenial.
1798524,2018-11-15 10:52:50 UTC,Found on 4.15.0-1032.33~14.04.2 azure as well.
1798524,2019-01-30 08:15:58 UTC,Can be seen on AWS Xenial 4.15 as well (4.15.0-1032.34~16.04.1)
1798525,2018-10-22 20:51:32 UTC,"Looking at the traces after merge that show the errors and the ones in the change job that do not, here is an observation ..."
1798525,2018-10-22 16:45:02 UTC,"Ignore comment above - ...
 ""update_containers"": ""true"",
in the change job"
1798525,2018-10-22 16:38:24 UTC,"Possibly the change job is not failing in CI because update_containers is set to false.
Trying patch out"
1798525,2018-10-22 12:07:07 UTC,removed alert as it doesn't fail now
1798525,2018-10-19 01:53:27 UTC,"Reviewed:  https://review.openstack.org/611518
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3cbaadd09c034629fb20e3c663ad64b3b468f77b
Submitter: Zuul
Branch:    master"
1798525,2018-10-18 12:41:28 UTC,apparently also affecting overcloud deploy via irc just now
1798525,2018-10-22 15:28:36 UTC,This failure reproduced on the baremetal master jobs:
1798525,2018-10-18 07:55:21 UTC,Fix for CI https://review.openstack.org/#/c/611526/
1798525,2018-10-18 07:30:13 UTC,posted the revert ^^^ but not sure if we need it yet... the error is pretty clear but why did it not fail on the review?
1798525,2018-10-18 07:20:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/611518"
1798525,2018-10-18 07:17:54 UTC,"It was passing in the review, maybe something is broken with build-test-package so it didn't test the review ?
http://logs.openstack.org/30/605430/5/check/tripleo-ci-centos-7-containerized-undercloud-upgrades/3ac93a2/job-output.txt.gz"
1798525,2018-10-18 12:23:26 UTC,Please take a look at https://review.openstack.org/#/c/611356/
1798529,2018-10-18 07:02:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611515"
1798535,2018-10-18 08:19:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1798535,2018-10-20 09:10:24 UTC,"I think I found the reason here. Looking at https://launchpad.net/ubuntu/+source/language-pack-hy, the last Ubuntu release to include the Armenian language pack was Ubuntu 14.04. Based on https://launchpad.net/ubuntu/+source/language-pack-hy/+publishinghistory it looks like the language pack was removed for having less that 5% translations."
1798535,2018-10-20 12:14:47 UTC,"That's precisely the explanation, Hans. I also tried to explain it at <https://askubuntu.com/q/1084617>."
1798538,2018-10-18 10:30:15 UTC,hmmm it seems this only happened once so will keep an eye but may end up closing this one
1798538,2019-01-22 19:37:04 UTC,Reproduced in current master with using environments/monitoring-environment.yaml and podman deploy.
1798538,2021-02-17 17:09:48 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1798548,2019-06-03 17:20:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798550,2018-10-18 13:08:43 UTC,FWIW< i believe this was fixed on 2.3.3:
1798550,2018-10-18 13:07:19 UTC,"Hi There,"
1798550,2019-05-10 09:20:12 UTC,@alextu please double check if this is still an issue for OEM team.
1798550,2018-10-18 08:59:14 UTC,$dpkg -l '*maas*'|cat
1798552,2018-10-18 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798552,2018-11-15 11:04:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1798552,2018-11-15 11:34:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1798552,2018-11-16 07:45:04 UTC,"Verified on my XPS, keypress can wake the system up in s2idle."
1798552,2018-12-03 08:49:32 UTC,This bug was fixed in the package linux - 4.18.0-12.13
1798552,2018-12-03 14:01:15 UTC,This bug was fixed in the package linux - 4.15.0-42.45
1798553,2018-10-18 13:31:02 UTC,"It should be fixed only for Pike, thanks!"
1798553,2019-03-18 00:34:47 UTC,This issue was fixed in the openstack/instack-undercloud 8.4.7 release.
1798553,2018-12-05 18:57:40 UTC,"Reviewed:  https://review.openstack.org/611647
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=a1038f30366f95aef7cf0b1df8f695a638fc499e
Submitter: Zuul
Branch:    stable/queens"
1798553,2018-10-23 10:54:32 UTC,"Change abandoned by Athlan-Guyot sofer (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/611647
Reason: legit error"
1798553,2018-10-19 16:47:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/611919"
1798553,2018-10-18 15:05:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/611647"
1798553,2018-10-18 13:39:52 UTC,Actually we need queens as well as in pike we don't use stackrc during pike undercloud upgrade so it can be unoticed and then happen only in queens where we do use authentication to check the overcloud state.
1798553,2018-10-18 11:50:24 UTC,"Note this is won't fix for the master (Stein), nor Rocky (as it has containerized undercloud instead of instack) and should only be fixed as a backports."
1798553,2018-10-18 09:17:51 UTC,This is the likely change[1] that broke this upgrade path.
1798553,2018-10-18 09:17:16 UTC,I updated my stackrc to use auth_url v3 authentication and it is now working.
1798553,2018-10-18 09:14:55 UTC,"So, for the last error, it's as if we're using /v2 path[1] while we're using domain[2]"
1798553,2018-10-18 13:14:31 UTC,"Hi Bogdan,"
1798554,2018-10-18 10:07:44 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1798559,2019-09-16 13:57:50 UTC,Migrated to https://github.com/widelands/widelands/issues/2122
1798559,2018-10-19 07:34:59 UTC,"To avoid merge conflicts, we should merge https://code.launchpad.net/~widelands-dev/widelands/bug-794407-soldier-stats before working on this."
1798563,2018-10-18 10:35:06 UTC,"AS showed in the attached screenshot, even if the backupCount parameter is setted as integer at the BaseRotatingHandler class, on the emit method, the parameter self.backupCount is readed as str."
1798564,2018-10-18 12:13:52 UTC,"Mead:

> Mead is produced by mead breweries and used in drinking halls for producing meals. Soldiers drink mead during advanced training.


Incorrect, it´s used only by soldiers (meals need normal beer)."
1798564,2018-10-18 11:56:54 UTC,And for iron and iron ore as well
1798564,2019-09-15 15:50:07 UTC,Migrated to https://github.com/widelands/widelands/issues/1718
1798564,2018-10-24 19:17:46 UTC,Same as in #7 for the Mead Brewery
1798564,2018-10-18 10:50:10 UTC,"The gold helptext always refers to the ""smelting works"", which is called ""furnace"" for fri."
1798564,2018-10-18 10:35:08 UTC,"The felling ax refers only to the ""lumberjack"", though he is called ""woodcutter"" for atl and fri."
1798564,2018-10-18 10:42:37 UTC,"Fruit helptext:

> Fruit are berries gathered from berry bushes by a fruit collector. They are used for rations and meals.


""Meals"" is wrong, and aqua farms are missing."
1798564,2018-10-18 10:54:38 UTC,Same as in #4 for gold ore
1798564,2018-10-18 10:28:31 UTC,And the need for coal for bricks is missing from the helptexts both for coal and bricks.
1798571,2020-04-09 23:32:33 UTC,This was fixed via Brisk Menu 0.5.0-11ubuntu1 in Ubuntu 19.10.
1798574,2018-10-18 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798574,2018-10-18 11:02:10 UTC,"For the record, as we don't have this test enlisted for bare-metal testing (lp:1798575), the only way to catch this for other kernels will be the ADT testing for ppc."
1798574,2018-10-18 13:07:42 UTC,"It didn't fail with older kernels on ADT, only with 4.15.0-38. So there might be a environment variable to it as well (e.g. number of cpus). And since we ran this test on baremetal only with ppc64el, it might affect other arches as well."
1798574,2019-09-18 13:50:03 UTC,"I can reproduce this on 4.15.0-38 but not on a more recent kernel, e.g. 4.15.0-64, so I think this has been fixed.  I'll close this for now as fixed released, but feel free to re-open it if we see the same issue again."
1798577,2020-06-16 19:51:38 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/606007
Reason: As we are going to deprecate master branch in this project this patch is not needed anymore."
1798577,2018-10-19 00:15:58 UTC,Thanks for filing a bug.  Let me check this behavior again.
1798577,2018-10-18 11:32:27 UTC,"I have commit the solution in this patch:
https://review.openstack.org/#/c/606007/"
1798583,2018-12-08 20:54:42 UTC,I'm not going to make a recommendation one way or another.
1798583,2019-02-14 16:44:42 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1798583,2019-02-14 14:48:40 UTC,"I'm afraid I only have 18.10 to test, which it did solve. Don't see why it would be any different with 18.04 and absolutely should not just be dropped after five days."
1798583,2019-02-14 12:11:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1798583,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1798583,2019-01-15 12:33:10 UTC,Updated tags for Liam.  Thanks for testing.
1798583,2019-01-15 12:29:33 UTC,"I don't see anywhere to change/add tags by the way, I assume I don't have permissions?"
1798583,2019-01-15 12:23:57 UTC,"I enabled proposed updates, upgraded and removed my blacklist on hid_steam and rebooted."
1798583,2019-01-15 10:32:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1798583,2018-12-10 10:56:00 UTC,"As I understand it, while this currently works on Bionic with 4.15 it will _stop_ working on Bionic when the new 4.18 HWE kernel gets released, without this patch applied."
1798583,2018-12-10 09:39:15 UTC,Seems like it already works under Bionic as a generic HID device. It depends on how many new features hid-steam brings to justify whether backporting it is a good idea or not.
1798583,2018-12-10 09:12:51 UTC,"I would like to see this prepared for Bionic too.  While a lot of gamers go for the latest release, the LTS has a massive user base.  I'd like to see Steam controllers working in Bionic."
1798583,2018-12-10 08:13:14 UTC,"Ok, I'll ask Mr. Costa about the question."
1798583,2018-12-08 07:32:00 UTC,"kisak, in addition to the fix, do you think backport the hid-steam driver to Bionic's v4.15 kernel useful to the users?"
1798583,2018-11-26 13:24:29 UTC,There has been no change on the bugzilla report/patch it seems :-/
1798583,2018-12-06 19:28:54 UTC,"The issue should be fixed in that disco update, https://launchpad.net/ubuntu/+source/linux/4.19.0-8.9"
1798583,2018-12-05 05:33:52 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1806247/"
1798583,2018-12-04 17:04:07 UTC,Kernel team are addressing this in bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806247
1798583,2018-12-04 14:28:54 UTC,"it's in the stable git also, https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=385a4886"
1798583,2018-12-04 14:23:54 UTC,"Seems like it has been merged on linux-next
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=385a4886"
1798583,2018-11-21 14:01:15 UTC,Any updates on this? I still experience the problem on 4.19.3-041903-generic
1798583,2018-10-30 19:43:34 UTC,Hi.
1798583,2018-10-18 12:29:06 UTC,"there is a patch on lklm but it's not merged yet, the bug still exists in the current kernel version"
1798583,2018-10-18 12:09:32 UTC,"The issue is at stated, the hid steam driver in Kernel 4.18."
1798583,2018-10-18 12:05:22 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1798583,2018-10-18 12:00:06 UTC,This change was made by a bot.
1798583,2018-12-07 17:34:41 UTC,"Hello Kai-Heng Feng, on Ubuntu 18.04.1, I grabbed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.20/ and your build. With 4.18.20 mainline I can confirm Rocket League's main menu can not be navigated via the Steam Controller, and can be with your test build. No game play was tested and only one game was tested. Game was launched from Steam's Big Picture Mode."
1798596,2019-10-11 13:20:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798596,2019-11-04 20:35:57 UTC,Thanks for reporting.
1798600,2018-10-18 18:46:38 UTC,I would prefer something in the Library Settings Editor.
1798608,2018-10-19 01:33:17 UTC,"I am sorry, I am sooo new at this and have only tried to report one bug
before and was told it was not a bug. I promise I am not trying to be hard
to get along with. I flat don't understand what I am doing."
1798608,2018-10-18 19:04:51 UTC,"Just found software version, sorry."
1798608,2018-10-18 20:09:30 UTC,ubiquity is the installer app. In this case the app it's called mate-tweak again have a look at the how to report problems on the forum.
1798608,2018-10-18 15:26:26 UTC,"Have a look at https://ubuntu-mate.community/t/how-to-report-problems-in-ubuntu-mate/17943 before you are making a bug report.
Because this report it's incomplete i will mark this as incompletely intil we have a os version etc."
1798608,2018-10-18 18:54:51 UTC,Ubuntu Mate 18.04.1
1798621,2018-10-19 11:32:53 UTC,Here's a patch which escapes '/' characters in labels (and resulting netnames) and re-allows spaces (as they can come in through sheet names anyway).  It uses the escaping mechanism Wayne and I discussed over email (which prioritizes readability over verbosity).
1798621,2018-10-18 18:30:44 UTC,"I believe that's because we can't tell the difference between label ""PAR_AUX3/SELECT*"" and label ""SELECT*"" on sheet ""PAR_AUX3""."
1798621,2018-10-18 19:11:53 UTC,This regression breaks existing schematics in our demos folder.  It will certainly break other people's schematics as well.  We shouldn't be adding the limit now until we bump the schematic version.
1798621,2018-10-18 19:37:15 UTC,See https://bugs.launchpad.net/kicad/+bug/1749232.
1798621,2018-10-18 20:04:44 UTC,Huh.  Thanks!
1798621,2018-10-18 20:15:08 UTC,"I /think/ even in 4.0.7 we validated it in some places but not others.  I thought 5.0 was uniform, but it's possible it just validated in more places and 5.1 does it uniformly."
1798621,2018-10-18 20:56:13 UTC,"I see the difference.  In 5.0.x, we didn't allow input of the '/' character but you could still paste it and it wasn't checked on closing the dialog.  In 5.1, we check on closing the dialog."
1798621,2019-04-07 10:32:38 UTC,"Fixed in revision 684bb62fd8edb4785caee33b189d73e68921942f
https://git.launchpad.net/kicad/patch/?id=684bb62fd8edb4785caee33b189d73e68921942f"
1798624,2019-04-23 20:47:33 UTC,"Just got a new mail, this time it worked."
1798624,2019-04-23 16:46:43 UTC,"Hi,"
1798624,2019-04-23 20:36:57 UTC,"I get a link with two tokens again and clicking on the link, I see an empty page. No 404 this time. Just empty. The email does not get verified this way."
1798624,2019-04-23 17:04:59 UTC,"@dholbach: After looking at your validation link, it has this form:"
1798624,2019-04-23 16:25:10 UTC,"I'm seeing a similar issue. I used ""+"" in the email address. Is that an issue?"
1798624,2018-10-18 19:07:13 UTC,"We'd be seeing a deluge of similar requests if that were the case, and we haven't; but waiting a few days and retrying seems prudent."
1798624,2018-10-18 18:41:25 UTC,"I can't think of any, no.  Unless there was a huge queue of DB related locks or timeouts or something preventing the tokens and data from being properly populated."
1798624,2018-10-18 18:30:17 UTC,I can't reproduce with the provided steps.
1798628,2018-12-04 15:46:28 UTC,"I am seeing this, as well."
1798628,2019-01-17 18:44:30 UTC,Here's a branch that changes how the copy alerts are counted in the holdings view. This should prevent any confusion where the column claims there are X alerts but clicking the Manage button displays between 0 and X actual alerts.
1798628,2019-03-02 19:09:28 UTC,Tested and it works as advertised.  Sign-off branch at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=71f03426809afe73dd7f2e0dade84353f6492ec9
1798628,2019-03-08 19:36:19 UTC,"Pushed to master and rel_3_2.  Thanks, Jason and Garry!"
1798629,2018-10-21 13:12:47 UTC,I've filed this against Yaru too https://github.com/ubuntu/yaru/issues/913
1798629,2018-10-20 11:52:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798629,2018-10-19 18:53:18 UTC,Just want to add that this is observed with any snap application on Ubuntu 18.10. Not limited to System monitor or calculator.
1798650,2018-10-19 07:13:25 UTC,"""Laitteella ei ole tilaa jäljellä"" means ""No space left on device""."
1798652,2018-10-19 10:35:41 UTC,"probably duplicate of:
https://bugs.launchpad.net/inkscape/+bug/1768444"
1798652,2018-10-19 10:28:34 UTC,"probably caused by the following element:
    <linearGradient
       id=""linearGradient844""
       osb:paint=""solid""
       gradientTransform=""matrix(0,0,0,0,3973.0047,-18164.678)"">"
1798652,2019-06-21 13:23:05 UTC,Closing as duplicate of bug 1768444.
1798652,2018-10-19 10:17:04 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1798655,2018-10-18 19:11:54 UTC,"I just discovered that replacing the first ""return"" inside the while loop with ""break"" prevents the bug from being triggered."
1798655,2018-10-18 19:14:18 UTC,"Also, bug still occurs when the function is rewritten to use indices instead of iterators. Appears the control flow statements are the issue."
1798655,2020-03-02 11:21:27 UTC,"Hi,
I can't reproduce with latest toolchain release:"
1798657,2019-04-11 19:38:44 UTC,saw this again on upgrade from cosmic to disco.
1798658,2018-10-22 15:13:41 UTC,Does not need to go to the security pocket
1798658,2018-10-29 15:53:27 UTC,Testing complete. No new issues.
1798658,2018-10-29 22:25:21 UTC,This bug was fixed in the package linux-azure - 4.15.0-1028.29
1798658,2018-10-30 14:33:16 UTC,The package has been published and the bug is being set to Fix Released
1798661,2018-10-19 13:31:59 UTC,"The problem comes from openjdk-11-jdk-headless package.
In previous release it has needed java.xml.bind.jmod , but in 18.10 the file is missed."
1798661,2018-10-22 17:29:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798669,2019-01-29 00:03:36 UTC,"Edits and deletions of copy alerts also fail silently when the user doesn't have the needed permissions (UPDATE_COPY_ALERT and DELETE_COPY_ALERT) or has the permission but not at the needed depth.  (For example, if permissions are granted at the library level and Library A tries to delete Library B's alert it appears to succeed but doesn't actually delete.)"
1798669,2019-01-11 16:55:15 UTC,"I opened bug #1811442, which might address the lack of permission. But I agree that Evergreen should do something nicer whenever a case like this occurs."
1798671,2018-10-18 20:17:06 UTC,"The attached screen shot shows the MAAS UI reporting three completely different IP addresses that don't work, while the MAAS log instead shows two OTHER IP Addresses that DO work.  Basically, the IP addresses below in the maas.log snippet are the IP addresses MAAS assigned when I set those two interfaces to ""Auto Assign"".  When I entered Rescue Mode, MAAS UI tells me completely differetn IP addresses that do not work, while the 2.99 address DOES work."
1798671,2018-10-18 20:35:11 UTC,"A machine that failed to deploy still holds the IP addresses that were assigned to the machine. However, rescue mode and other ephemeral environments get network from the /dynamic/ range and not from the static network configuration because it could be the very same reason why it fails to deploy/configure/etc."
1798671,2019-09-19 14:49:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1798674,2018-10-29 22:53:24 UTC,This bug was fixed in the package linux-azure - 4.15.0-1028.29~16.04.1
1798674,2018-10-22 15:14:45 UTC,Does not need to go to the security pocket.
1798674,2018-10-29 15:54:06 UTC,Testing complete. No new issues.
1798674,2018-10-30 14:30:36 UTC,The package has been published and the bug is being set to Fix Released
1798676,2019-09-19 11:51:31 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1798676,2018-11-06 23:47:57 UTC,"I think this occurs because the IP address is decided dynamically, based on how the request was made."
1798690,2018-11-07 11:31:30 UTC,"Thanks Sean!  I will have to look at the hosts again, but it appears the OVS configuration does not get migrated from source to target host.  Instead, the OVS configuration remains on the source host.  I was able to migrate the VM ""back"" to the source and the internal network connectivity started to work again.  I was looking at the OVS rules, and the rules (flows) still exist in the vswitch on the source host."
1798690,2018-10-18 23:31:50 UTC,"Shortly after submitting this, I ran into the same situation, but when I had initially started a ping between the VMs.  So, the problem is more severe.  I will provide logs shortly after I have some time to review."
1798690,2018-10-18 23:47:33 UTC,"Looking at the OVS configurations (with ovs-vsctl show), the flows configured on the source host still exist, and there are ""no"" flows configured on the target host."
1798690,2018-10-19 07:57:09 UTC,"Just a quick note that I have confirmed that this issue happens on Ceph-backed volumes as well, so this is not iSCSI backend related."
1798690,2018-10-19 09:57:58 UTC,"I ran a few tests, trying to reproduce the problem - see below."
1798690,2018-10-28 22:38:42 UTC,"Added to Neutron group.  This is easily reproducible, but if more information is needed, please let me know."
1798690,2018-11-05 11:32:25 UTC,Just checking-in and to also see if anyone else has had success with live migrations?  I'm just trying to narrow down whether we have an environment issue here that may not happen to anyone else.
1798690,2018-11-06 15:14:29 UTC,"i have not looked into this closely but my guess is this could be related to the arp suppression rules
used in the dvr case not being updated correctly that said it is just a guess
so there may be something more going on here."
1798690,2020-04-28 11:04:19 UTC,"Hello, I have same issue migrating from queens to rocky.
Works fine on queens.
Does not work on rocky
Does non work on stein
Ignazio"
1798703,2018-10-19 05:44:59 UTC,There are some similar bug reports.
1798703,2018-11-28 07:33:27 UTC,This issue has been fixed in different bug- https://bugs.launchpad.net/nova/+bug/1741000
1798708,2018-10-19 02:34:21 UTC,apport information
1798708,2018-10-19 02:34:24 UTC,apport information
1798708,2018-10-19 02:34:19 UTC,apport information
1798708,2018-10-19 02:34:27 UTC,apport information
1798708,2018-10-19 02:34:10 UTC,apport information
1798708,2018-10-26 08:21:06 UTC,"After I removed the nvidia-kms.conf or change option ""nvidia-drm modeset=0"", then update initramfs, the external monitor will work fine."
1798708,2018-10-29 04:33:59 UTC,"Here is another workaround. When  in Nvidia mode, do below commands."
1798708,2019-03-19 05:00:23 UTC,The external monitor problem is probably a well-known gdm3 bug: gdm3 with nvidia modeset=1 stops the nvidia driver from detecting external monitors (possibly it invokes some wayland features when it shouldn't). It is not a problem with nvidia-prime or with the kernel. You can fix it by using lightdm instead of gdm3. This bug affects fedora as well.
1798708,2018-10-19 02:34:17 UTC,apport information
1798708,2019-08-22 05:38:55 UTC,"Talked to Bin and he no longer has this issue, so I'm closing this bug."
1798708,2018-10-26 08:13:51 UTC,"After the workaround in comment 2, I found the external monitor couldn't be used ThinkPad P1 and P72, it's a critical issue."
1798708,2018-10-19 02:34:14 UTC,apport information
1798708,2018-10-19 02:34:06 UTC,apport information
1798708,2018-10-19 02:34:11 UTC,apport information
1798708,2018-10-19 02:01:41 UTC,"Here is the workaround.
$ prime-select intel # It will generate /lib/moprobe.d/blacklist-nvidia.conf"
1798708,2018-10-19 02:33:58 UTC,apport information
1798708,2018-10-19 02:33:59 UTC,apport information
1798708,2018-10-19 02:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798708,2018-10-19 02:34:04 UTC,apport information
1798708,2018-10-19 02:34:13 UTC,apport information
1798708,2018-10-19 02:34:08 UTC,apport information
1798708,2018-10-19 02:34:02 UTC,apport information
1798709,2019-10-31 03:35:18 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1798720,2019-05-23 03:28:09 UTC,"Commit hash: 10fd48dc4585770be27a22e7aff7026f227b0d2f
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw | Default raw | Ocean | Modern | Primary school"
1798720,2018-12-05 02:58:47 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9356"
1798720,2018-12-10 00:43:08 UTC,"Environment tested: Master
Browser tested: Chrome"
1798720,2018-12-12 06:23:54 UTC,Items 7 and 9 needs to be dealt with separately. That is not part of this feature. There is already a bug report for that.
1798720,2018-12-20 00:24:50 UTC,"Any tags, i.e. usually prefixed by ""Tags"" should not be links anymore. Other links may still go to live sites. That is behavior that is not fixed here, but is a separate issue."
1798720,2019-06-25 01:14:09 UTC,"Reviewed:  https://reviews.mahara.org/9356
Committed: https://git.mahara.org/mahara/mahara/commit/0bd2fb3452ed19b62fef5f9e5e1d8805892df627
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1798721,2018-12-10 11:58:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798723,2018-10-19 18:50:37 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1798726,2018-11-15 06:48:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/618086"
1798726,2020-02-05 07:40:25 UTC,"Reviewed:  https://review.opendev.org/618086
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=938262073f11913169c79299941d9c5c4d4b0645
Submitter: Zuul
Branch:    master"
1798734,2018-10-19 05:33:17 UTC,"Please note, this *does* seem to have the desired effect on charm hooks, just not on the environment of the ubuntu user."
1798734,2020-07-21 18:28:44 UTC,"This is because the golang http client caches the environment proxy settings. If you bounce the jujud machine process on the controller or the juju machine you want to update, you'll see that the changed settings are honored.  This is not realistic for most configs."
1798738,2018-10-19 05:46:44 UTC,Here is a screenshot.
1798738,2019-01-23 16:29:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798738,2019-01-23 16:31:04 UTC,"Confirming this. After some experiments of installing various icons packs, I found the only solution to run under desktop-plasma session (as opposed or Unity or Ubuntu). Maybe someone can guess the cause better?"
1798738,2019-12-12 13:42:44 UTC,"Hi,"
1798738,2020-01-14 08:14:38 UTC,Icon doesn't show but is functional when hoovering over it.
1798740,2018-10-19 11:12:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798740,2018-10-19 08:15:56 UTC,Eventually I see no errors.
1798740,2018-10-19 07:30:16 UTC,Degraded systemctl is probably irrelevant. It was fixed with `dpkg-reconfigure postfix`.
1798744,2018-10-19 08:13:05 UTC,you can add this cli filter support in openstackclient
1798744,2018-10-19 08:43:38 UTC,https://review.openstack.org/#/c/611789/
1798744,2018-11-09 07:09:02 UTC,This issue was fixed in the openstack/python-openstackclient 3.17.0 release.
1798744,2019-03-08 04:20:22 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1798745,2018-10-19 08:07:24 UTC,hi! which version of tricircle do you use? and I think you should delete the port in the center region not in the local region.
1798745,2018-10-19 08:45:46 UTC,"Hi baisen, I am using Tricircle master version. Because Heat only works in 1 region at a time, when I delete a stack, only nova instances are deleted. Ports are different, they are in Central region, so Heat can not delete them."
1798762,2018-10-19 07:58:38 UTC,I have choosed wrong file in comment #2. Here is the correct one.
1798768,2018-10-19 18:50:12 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1798787,2018-10-19 19:25:58 UTC,"OK this is a rough translation, but I think the bug is saying that this step in the install guide shows the nova-consoleauth:"
1798787,2018-10-19 19:28:55 UTC,Yeah looking at this page in queens you see the nova-consoleauth service being installed and started:
1798787,2018-10-30 01:29:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614055"
1798788,2018-10-19 11:31:29 UTC,Many of you are trying to run checkbox over ssh via jenkins jobs. You need to take special care doing so.
1798788,2018-10-26 09:22:21 UTC,The comment#1 works for bucky CID 201807-26321. Thanks!
1798788,2018-11-05 06:57:29 UTC,"followed #2 result, we land that solution by job yaml, but get another error:"
1798788,2018-11-05 07:49:50 UTC,@alex
1798790,2019-04-29 15:41:53 UTC,I can reproduce this issue on my 19.04 system using GTX 650. If anyone needs debug information or to try a new package I'm happy to offer my help.
1798790,2019-06-05 13:38:17 UTC,"In case it helps. The bp_filter issue only affects me when booting without connected to power. In other words, the screen gets stuck on this only when booting with the battery alone."
1798790,2019-06-02 11:32:15 UTC,"The GDM side is committed for 3.33, but the way we've implemented this needs support from gnome-shell and a declaraion in the session file (which comes from gnome-session). WIP:"
1798790,2019-05-28 07:53:26 UTC,We probably don't need any more logs thanks. A fix is already being discussed here:
1798790,2019-05-28 07:45:29 UTC,"I experienced the same problem when I tried to install Ubuntu 19.04 with the initial option to install third party drivers.  After installation and the first reboot, the system will not start up. I will see if I can reproduce this and post the log report."
1798790,2019-05-18 12:25:16 UTC,Workaround in #19 working for me so far on Ubuntu 19.04. Have done a reboot test and a powerup test so far.
1798790,2019-04-30 06:06:15 UTC,I've opened a fresh bug since the one referenced above was closed. https://gitlab.gnome.org/GNOME/gdm/issues/483
1798790,2019-01-19 22:47:13 UTC,I also have the same problem.
1798790,2019-04-25 20:22:50 UTC,WaylandEnable=false workaround also works for 19.04
1798790,2019-01-21 02:15:10 UTC,"Vincent, you are commenting on the wrong bug. Please open a new one instead."
1798790,2019-06-05 19:09:22 UTC,"I have Dell 7530 with Nvidia Quadro P3200 (nvidia driver 418.74), running Ubuntu 18.04 (with all the latest updates) and I observe the same thing: with power cable it boots fine and without it gets stuck on ""bpfilter started""."
1798790,2019-01-10 04:57:15 UTC,Uncommenting this line worked for me. This bug occurred after a fresh install of 18.10.
1798790,2019-01-07 02:15:41 UTC,Then you are commenting on the wrong bug. Please open a new one instead.
1798790,2019-04-29 15:56:02 UTC,I've added some extra debugging information to an upstream bug https://gitlab.gnome.org/GNOME/gdm/issues/435#note_499818
1798790,2019-06-05 19:39:00 UTC,"With WaylandEnable=false active in /etc/gdm3/custom.conf, the system monitor does not launch."
1798790,2019-06-13 10:56:31 UTC,"Also, just a reminder: If anyone is using a multi-GPU desktop machine then please see bug 1705369 instead."
1798790,2019-06-07 03:11:54 UTC,"I had thought bug 1825544 was intentional, but I was wrong. I was confusing it with the absence of guest mode, which is intentional."
1798790,2019-06-07 14:07:31 UTC,When I do the setting WaylandEnable=false fix the system becomes unstable and I get constant lockups and freezes unfortunately.
1798790,2019-06-10 01:32:44 UTC,"Eli,"
1798790,2019-01-05 07:38:41 UTC,"The uncommenting this line doesn't work for me:
#WaylandEnable=false"
1798790,2019-06-28 06:29:19 UTC,"I also have this issue, but I discovered if I pressed Alt+F{N>2} then Alt+F1 gdm boots immediatly."
1798790,2019-07-10 10:13:27 UTC,I see   'Started bpfilter'   at shutdown or restart and it hangs when closing down.  I can just power off holding the power button but I know may be causing OS/ HDD issues in not closing down correctly.
1798790,2019-08-26 23:40:40 UTC,This bug was fixed in the package gdm3 - 3.33.90-1ubuntu1
1798790,2019-08-27 13:14:09 UTC,This bug was fixed in the package gnome-shell - 3.33.91-1ubuntu1
1798790,2019-08-27 13:14:19 UTC,This bug was fixed in the package gnome-session - 3.33.90-2ubuntu1
1798790,2019-09-10 13:38:10 UTC,"This happened to me after booting up on Sep 10 2019 after Ubuntu ran software updater on Sep 9. 2019. I update whenever there is an update reported by software updater.   Tried to restart several times with the same result. System went to text mode and stuck at ""starting bpfilter"" every time. 100%.  Luckily I had a 2nd computer to search for this issue. Uncommenting the Wayland option fix it. I update daily. Why did this happen ? This seems to be a recurring issue."
1798790,2019-09-10 13:56:21 UTC,"Ubuntu 19.04
Updates set ""for any new version""
Software updates: Just all the defaults
Linux 5.00.027-low latency #28-Ubuntu SMP PREMPT Aug 20 20:33:37 UTC 2019 x86_64 x86_64 GNU/Linux
Additional drivers:
Nvidia GF119, GeForce 610.
NVidia driver meta-package from Nvidia driver-390. proprietary tested).
Monitor Beng 2710BL 2560x1440 using DVD-DL."
1798790,2019-09-11 01:40:52 UTC,This bug is fixed in Ubuntu 19.10. We know it is not fixed in 19.04.
1798790,2019-10-02 13:51:41 UTC,"I will try the Wayland parameter option, but for what it's worth, the only way I've been able to recover so far is to boot off a USB thumb drive, mount my actual boot drive, download and run boot-repair. When I reboot, I finally get a grub menu and can institute the usual menu-driven repairs from there.  The full boot-repair report can be found at https://paste.ubuntu.com/p/34RRkD365G/."
1798790,2019-10-03 01:48:56 UTC,This bug is closed. If you have any ongoing issue then please open a new bug for it.
1798790,2019-06-06 12:26:25 UTC,For info only:
1798790,2018-12-29 11:32:30 UTC,"This is not a problem of Wayland or Ubuntu but of Gnome and the Nvidia driver.
In fact Fedora 29 has the same problem, only it has to come out a month later they deactivate the proprietary driver and force to use Noveau."
1798790,2019-04-22 18:43:13 UTC,"bug also in 19.04, just updated from 18.10"
1798790,2018-12-12 08:21:32 UTC,"Daniel, sorry, you're right, I'm not describing a problem on an nVidia-based system. Will open a new bug."
1798790,2018-10-19 14:20:46 UTC,Same issue. Going to recovery mode and then restarting seems to have solved it for now.
1798790,2018-10-19 14:22:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798790,2018-10-19 15:14:10 UTC,Simply going into recovery mode and then restarting didn't fix it for me. Continuing into normal boot also didn't fix the issue.
1798790,2018-10-21 14:19:49 UTC,"As mentioned in the above askubuntu posting, removing the nvidia driver got me past the problem."
1798790,2018-10-22 14:08:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1798790,2018-10-22 14:37:42 UTC,Can the importance also be higher? Gaming is impossible with the Nouveau drivers. Thank you. I might provide a video reproducing the problem later as well.
1798790,2018-12-29 02:06:19 UTC,"Wayland is not fully functional or compatible with Ubuntu 18.10 yet.
So why use wayland in a full new distribution, and cause problems?
It wasted 8 hours of my time to find the solution.
Just because of 1 line in a gdm3 conf file.
1 wrong line in a config line, and Ubuntu fails.
Ubuntu needs essential conf and system protection, so that 1 little change cannot derail the entire
OS, or deleting or installing cannot remove essential files necessary to run the OS.
After this many years Ubuntu is still incredibly easy to break.
Essential, necessary configs and system files that run the basic OS should be read only!"
1798790,2018-10-23 07:36:09 UTC,"Sorry but I don't understand the description, """"Started bpfilter"" is located just under ""Started Gnome Desktop Manager""."" what does that mean? Where is that displayed? Why is it an issue to have ""Started bpfilter"" displayed under ""Started Gnome Desktop Manager""?"
1798790,2018-10-23 07:56:04 UTC,Sounds like the real issue is that the login screen is not appearing.
1798790,2018-10-23 08:12:38 UTC,"These commands were run in a normal boot of Ubuntu, without the Nvidia drivers."
1798790,2018-10-23 08:17:12 UTC,@seb128 I'm just trying to explain where the two messages are in relation to each other in this command-like environment you are stuck in. Having one line before the other is not an issue.
1798790,2018-10-23 08:41:57 UTC,"Oops, sorry. That is the log from when it was working. We need a log from when it is broken, so please..."
1798790,2018-10-23 08:46:19 UTC,"@Efthimios, well, your description still doesn't make sense, it should start with a statement of the problem, like ""after installating the nvidia driver my computer doesn't reach the login screen but is stucked on a screen with those messages"" if that's what is happening?"
1798790,2018-10-23 09:20:42 UTC,"@seb128 Sorry, I will remove it."
1798790,2018-10-23 10:14:48 UTC,Thanks. I think I can see the problem now.
1798790,2018-10-22 15:19:09 UTC,"Part 1: https://youtu.be/Dq8l9PkFiyQ
Part 2: https://youtu.be/dqUOw13sUbo"
1798790,2018-10-23 10:30:34 UTC,The workaround worked.
1798790,2018-12-11 02:30:29 UTC,Please don't comment on this bug unless the workaround in comment #19 works for you. If it doesn't work for you then you need to log a new bug of your own.
1798790,2018-12-10 13:14:13 UTC,"I forgot to include introductory links to this complicated issue. My crude understanding is that systemd handles system initialization, calling bpfilter (replacing iptables) which is handled by the linux kernel."
1798790,2018-12-10 12:56:42 UTC,SOLVED (MAYBE)
1798790,2018-12-10 11:39:49 UTC,"GDM3 fails to start, stalled at 'started bpfilter' on my HP laptop (model hp15-ay016nr) which runs Intel graphics, no nVidia hardware or drivers. So, this is not strictly an nVidia issue, which began after a Sat 8 December upgrade."
1798790,2018-12-04 01:54:15 UTC,"The same workaround of commenting Wayland worked for me, also, before reading this, i got it to work doing this procedure:"
1798790,2018-11-21 02:04:28 UTC,The same workaround seems to be working for bug 1796614. Although that is about nouveau and this is about the proprietary Nvidia driver. Not sure if we can or should merge them.
1798790,2018-10-23 10:20:14 UTC,The bug ID is 435.
1798790,2018-11-15 11:21:10 UTC,I'm having the same issue. The login screen appears after I press ctrl+alt+f2 and then ctrl+alt+f1.
1798790,2018-11-06 16:01:15 UTC,Another workaround is adding `nvidia-drm.modeset=1` to the kernel command line.
1798790,2018-10-29 07:56:20 UTC,"Edit the file /etc/gdm3/custom.conf it also worked for me.
If someone had tried installing lighdm you can go back to gdm by doing
sudo service lightdm stop
sudo reboot"
1798790,2018-10-25 21:49:30 UTC,Just to say that I've tested the '#WaylandEnable=false' method (I was having the same problem with the nVidia drivers) and it works great!
1798790,2018-10-25 03:01:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798790,2018-11-15 17:04:53 UTC,"The following workaround worked for me, no problems now (140.107 - Ubuntu 18.10):"
1798794,2020-07-06 05:29:03 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/739402"
1798794,2020-08-06 21:02:28 UTC,"Reviewed:  https://review.opendev.org/739629
Committed: https://git.openstack.org/cgit/openstack/charm-guide/commit/?id=06f4cdaa65b38218511f6002c8b7ab02707acb85
Submitter: Zuul
Branch:    master"
1798794,2020-07-17 16:18:07 UTC,"Reviewed:  https://review.opendev.org/739402
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=08d56bb04064d4252b358f99aaeff7f024f8c6c0
Submitter: Zuul
Branch:    master"
1798794,2020-10-20 07:18:57 UTC,"It's worth noting that when this is removed we should add code to remove the /etc/sysctl.d files from the disk, reverting the actual running config values is more tricky as it's not entirely straight forward to reset them back to the 'default' as the sysctl tool won't reset values that no longer exist in /etc/sysctl.d and some of the options are calculated to different values on boot based on RAM size."
1798794,2020-06-12 07:32:13 UTC,"It keeps ""slipping"" because it is just updated to the next Milestone. It is not on a roadmap as it hasn't been given enough priority. It would probably make sense for the OpenStack Charm bugs to not be given a milestone until they are actually targeted to one but that is the general practice."
1798794,2019-09-03 20:13:19 UTC,"Given the marginal usefulness in operations, the potential for highly undesirable impact, and the idea that it is difficult, if not impossible, to autotune with a one-sized approach, I would be in favor of deprecating this charm config option."
1798794,2020-06-11 16:46:48 UTC,"Why does this keep slipping? Can we at least change the charm doc that says ""Enabling this option should generally be safe"" if we believe it's not safe?"
1798805,2018-10-19 15:31:18 UTC,"When you say ""Disable the nova-compute service on host compute001"" do you mean using the disable API for the compute service, or simply stopping the nova-compute process on the host? If the latter, are you waiting for it's status to e 'down' in the nova service-list output?"
1798805,2018-10-19 16:14:52 UTC,"Even if the API did check if the compute service was running, it wouldn't fix the problem since the compute service could die (or get taken down) right after sending the RPC cast."
1798805,2018-10-19 21:58:23 UTC,"@Matt - Since we are using Kolla-Ansible to deploy a container-based OpenStack, we stop the docker container that is running the nova-compute process(es), so it is effectively the same as stopping the nova-compute process (gracefully) on a non-containerized OpenStack."
1798807,2018-10-19 12:23:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1798813,2018-11-17 03:54:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798813,2019-04-20 08:01:03 UTC,The default initial NAT configuration on adapter 1 grants Internet access.
1798813,2019-11-12 13:55:14 UTC,"Can you please try again with 5.2.34 in bionic?
I think I fixed bug - Add suid bit to VBoxNetNat to make it work (LP: #1805651)"
1798813,2019-11-23 07:38:44 UTC,"I checked on Ubuntu 18.04 upgraded to 21/11/2019, that means virtualbox 5.2.32.  It works perfect now. Problem solved! Virtual machines with NatNetwork mode accesing internet."
1798813,2020-01-23 04:17:24 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1798818,2018-10-21 12:28:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798818,2018-12-12 21:40:27 UTC,"Approved after upgrading to 18.10.
Cannot access hostnames under vpn dns.
Connecting with same config file ""x.conf"" like on 18.04.
On 18.04 resolving was working."
1798818,2018-11-02 13:20:37 UTC,"Is there any planned activity on this?
Currently I need to keep several IPs in my hosts file, which is very fragile and anoying."
1798825,2018-10-19 14:41:20 UTC,"It will time out if not in use (as it should, for security). However, I haven't seen a problem with it losing the workstation. You might want to check your browser's Privacy and Security settings to make sure that cookies are allowed and saved for your domain."
1798828,2020-08-10 04:14:07 UTC,reported upstream at https://gitlab.gnome.org/GNOME/gvfs/-/issues/503
1798828,2020-08-01 05:33:39 UTC,gitlab closed the issue as not belonging there
1798828,2020-08-01 02:53:35 UTC,reported upstream at https://gitlab.com/gitlab-org/gitlab/-/issues/233169
1798828,2020-08-01 02:06:46 UTC,after reboot the Trash icon shows empty
1798828,2020-08-10 22:03:13 UTC,upstream replied
1798828,2020-08-01 00:43:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798828,2018-10-19 14:02:45 UTC,"Bug #1558768 can be related, but that bug is abotu high CPU usage"
1798828,2020-08-01 01:05:11 UTC,Ubuntu LTS 16.04.6
1798829,2018-11-28 16:17:50 UTC,I want to say that https://bugs.launchpad.net/tripleo/+bug/1799724 fixes this?
1798829,2019-08-22 15:13:28 UTC,"I did an undercloud deployment earlier with the following options:
local_ip=192.168.0.21/24
undercloud_public_host=undercloud.rdocloud"
1798831,2018-10-20 08:47:19 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1798831,2018-10-20 10:11:49 UTC,Thanks for the clarification.
1798833,2018-10-23 11:00:46 UTC,apport information
1798833,2018-10-23 11:00:43 UTC,apport information
1798833,2018-10-23 11:00:41 UTC,apport information
1798833,2018-10-23 11:00:40 UTC,apport information
1798833,2018-10-23 11:00:39 UTC,apport information
1798833,2018-10-23 11:00:38 UTC,apport information
1798833,2018-10-23 11:00:33 UTC,apport information
1798833,2018-10-23 11:00:35 UTC,apport information
1798833,2018-10-23 11:00:34 UTC,apport information
1798833,2018-10-23 11:06:38 UTC,"After coming back from the weekend, the issue is now also occurring on the 4.15.0-20 kernel. I am not sure what is up. I had tried the 4.15.0-22 and 4.15.0-36 kernels, prior to booting up 4.15.0-20 again. In this particular machine, I had tried resetting the power saving settings of the network card from a Windows install, per bug that could be related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171"
1798833,2018-10-23 11:00:31 UTC,apport information
1798833,2018-10-19 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798833,2018-10-23 11:00:37 UTC,apport information
1798834,2020-04-14 10:23:49 UTC,Fixed in - or before - initial releasee of Ubuntu MATE 20.04 Focal Fossa alpha release.  Can be closed.
1798834,2018-10-20 09:54:57 UTC,The problem is more widespread?  Appears to affect any setting in Compiz Config Settings Manager which addresses the Mouse settins!  Ie. has the mouse icon on left and the 3 buttons on the right (Current value / Edit / Clear) REGARDLESS of panel.
1798834,2018-10-20 09:51:49 UTC,WORKAROUND:  The regression bug appears to be in the entry process.  So to make those settings change you need to go to Preferences (on the entry page) and Export the current profile (probably 'mate').  Edit the resulting file to include - if not already present):
1798844,2020-05-15 14:53:02 UTC,I can easily reproduce this one.
1798845,2018-10-19 19:21:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/611937"
1798845,2019-01-07 19:59:20 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/611937
Reason: this patch has no activity, i'll just abandon it until I spend time again on the bug."
1798845,2021-02-19 15:52:50 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1798857,2020-07-31 11:31:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798858,2018-10-28 17:31:51 UTC,Thank you for clarifying.
1798858,2018-11-05 22:49:04 UTC,"The issue seems to effect more users, since QT has a blacklist of drivers.
So any system that is listed here will not have GL Waveforms:
https://github.com/qt/qtbase/blob/dev/src/plugins/platforms/windows/openglblacklists/default.json"
1798858,2018-10-28 21:39:29 UTC,I'm not comfortable making *any* change to the 2.2 build environments at this point unless it is needed to fix a critical bug.
1798858,2018-10-28 21:10:01 UTC,The fix won't be like for libEGL/etc. because Qt doesn't produce these DLLs.
1798858,2018-10-28 19:48:17 UTC,"Do you have a recipe to do it?
I just had a look how you add libEGL.dll butI have no clue."
1798858,2018-10-28 18:54:38 UTC,"I see no risk in doing it for 2.2 if someone's motivated to fix this, I'm
only talking about priority."
1798858,2018-10-28 17:05:08 UTC,"Notably it's a crash on startup, so not a ""party stopper"" per se. Adding
the OpenGLES DLLs mitigate the issue for real hardware and some VMs I
believe, so I think the only time this actually causes an issue is if the
user truly has no graphics card capable of OpenGL and software rendering is
needed. Because I don't think it affects anyone but us developers using
Mixxx in a VM that's why I put it as low priority :)."
1798858,2019-04-26 22:43:15 UTC,"If GL is blacklisted or < 2.1 Qt tries to use the angle driver for GL ES which translates direct 3 d.
It will currently crash, if this is blacklisted as well, because of the outdated GL detection code.
The cash will be fixed here:
https://bugs.launchpad.net/mixxx/+bug/1825461"
1798858,2018-10-28 15:20:41 UTC,This is a crasher? I don't see any reports of actual crashes in this bug. RJ's last comment in the old bug ( https://bugs.launchpad.net/mixxx/+bug/1786718/comments/20 ) said this remaining issue is not critical.
1798858,2018-10-28 11:12:49 UTC,Since this is a crasher fix it should be a requiment for a 2.2 release.
1798858,2018-10-28 17:56:36 UTC,"Isn't it only a matter of adding a dll to the installer?
What is the risk, not to do it in 2.2?"
1798858,2019-04-26 22:47:33 UTC,"We can find the required DLLs here:
http://download.qt.io/development_releases/prebuilt/llvmpipe/windows/"
1798859,2018-10-19 16:21:55 UTC,"When I build it directly from source, everything works fine."
1798864,2019-09-19 12:00:29 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1798864,2018-10-19 18:16:15 UTC,Should MAAS automatically import Xenial if CentOS 6 or Precise are selected and neither Xenial nor Trusty are imported?
1798868,2018-11-01 11:03:32 UTC,"I have the same problem, needed datas were given at https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/comments/68"
1798872,2018-10-31 11:25:48 UTC,"So, you want to execute python in a subprocess and read its output?"
1798872,2018-10-31 11:54:35 UTC,"On Wed, Oct 31, 2018, 7:41 AM Julian Andres Klode <
<email address hidden> wrote:"
1798872,2019-12-01 13:31:32 UTC,sys.version_info is a runtime check of the actual version of python running. This is what we care about not enforcing a setup.
1798872,2019-12-01 13:33:05 UTC,Sorry for repeating already sent information would you be open to a patch for this?
1798880,2019-11-19 07:04:54 UTC,Remove the last physical PC card you installed. Or replace it
1798880,2019-05-16 18:47:01 UTC,"Bug was gone (fixed, I think) in my PC today after installing new Kernel version ""linux-image-4.15.0-50-generic"" in Ubuntu 18.04.2 x86_64."
1798880,2018-10-20 12:20:21 UTC,"lenge@hp-15:~$ cat /proc/version
Linux version 4.19.0-041900rc8-generic (kernel@kathleen) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #201810150631 SMP Mon Oct 15 06:33:11 UTC 2018"
1798880,2019-03-03 16:27:28 UTC,"cat /proc/version
Linux version 4.19.0-13-generic (buildd@lcy01-amd64-027) (gcc version 8.2.1 20190204 (Ubuntu 8.2.0-17ubuntu6)) #14-Ubuntu SMP Thu Feb 7 21:51:25 UTC 2019"
1798880,2018-10-19 19:00:06 UTC,This change was made by a bot.
1798880,2018-10-19 19:07:40 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1798881,2019-04-17 21:31:36 UTC,I think it's using snapcraft snap because this is present in the logs:
1798881,2019-04-17 17:58:58 UTC,Can you reproduce this when using the snapcraft snap and setting base to either core or core18?
1798881,2019-04-17 19:27:05 UTC,with snapcraft snap (edge ​​channel) and core18 I get the same issue
1798881,2019-04-17 21:13:41 UTC,"El miércoles, 17 de abril de 2019 16:27:05 -03 usted escribió:

> with snapcraft snap (edge ​​channel) and core18 I get the same issue
>
> Here is the build log:
> https://launchpadlibrarian.net/419684583/buildlog_snap_ubuntu_xenial_i386_vs
> codium.snap_BUILDING.txt.gz
"
1798881,2019-04-17 21:29:37 UTC,I compile directly from launchpad
1798883,2018-11-24 13:27:16 UTC,I'm also having this issue on my file server running Ubuntu 18.10. My file server get multiple SFTP connections every second and when the load is high some connection fails with below error in logs.
1798887,2018-10-23 19:28:05 UTC,SCLENDS consortium libraries report that they would like to see each counted noncat on its own line.  One benefit of each item having its own line is that it assists circ staff in providing a quite and accurate tally of the number of items a patron is checking out.
1798896,2019-05-20 18:04:44 UTC,We have had numerous reports of double holds on items where we believe the problem to be double clicking on submit by either the patron or staff. I believe we can confirm this behavior.
1798898,2018-10-22 17:22:59 UTC,Targeting stx.2019.03 -- horizon issue w/ Distributed Cloud configuration. Issue is not very serious.
1798898,2019-06-10 18:39:14 UTC,"There are significant changes required to support Distributed Cloud in stx due to the containerized environment. Based on discussion with the Distributed Cloud PL, Dariush Eslimi, we agreed to close old Distributed Cloud bugs as Won't Fix. A full test cycle will be needed to verify the new implementation and new bugs can be opened for the issues reported then."
1798898,2019-06-11 19:11:25 UTC,closing per wont fix comment above
1798899,2019-06-10 18:33:26 UTC,"There are significant changes required to support Distributed Cloud in stx due to the containerized environment. Based on discussion with the Distributed Cloud PL, Dariush Eslimi, we agreed to close old Distributed Cloud bugs as Won't Fix. A full test cycle will be needed to verify the new implementation and new bugs can be opened for the issues reported then."
1798899,2018-10-19 21:18:10 UTC,Low priority issue; the issue is limited to the first time and the dialog opens eventually.
1798903,2018-10-24 12:39:51 UTC,Targeting stx.2019.03 - horizon issue with distributed cloud. Doesn't gate stx.2018.10 as it's not a common config
1798903,2018-10-29 17:31:13 UTC,"Based on additional input, this is a lower priority item as the proper procedure is to create the volumes from the subclouds, not from the System Controller."
1798903,2019-06-10 18:34:05 UTC,"There are significant changes required to support Distributed Cloud in stx due to the containerized environment. Based on discussion with the Distributed Cloud PL, Dariush Eslimi, we agreed to close old Distributed Cloud bugs as Won't Fix. A full test cycle will be needed to verify the new implementation and new bugs can be opened for the issues reported then."
1798910,2018-10-23 18:48:34 UTC,"Ran into this issue within the last week.  Thanks for filing this, Jeff.  I'd love to see this fixed somehow, as the current outcome is surprising."
1798910,2019-11-07 14:28:52 UTC,"EG 3.3.4, just upgraded from 2.10 about 2 weeks ago.  Just ran into this issue with ebook titles added since the upgrade."
1798910,2019-11-07 15:24:03 UTC,"That's a good idea, Josh.  I'll see if I can come up with a patch we're happy with, that hopefully only has to call the function once."
1798910,2019-11-07 16:19:23 UTC,Here's a branch to consider: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1798910-update_bib_vis_on_same_marc
1798910,2020-01-08 19:47:54 UTC,Tested against a fresh copy of master this is causing a failure to update the biblio.record_entry row when a bib record (at least with located URIs) is updated.
1798921,2019-03-15 20:04:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1798921,2019-03-28 15:21:02 UTC,"Hello,"
1798921,2019-03-20 21:23:21 UTC,"I can not check the kernel v5.0-rc8
because I have other errors regarding the nvidia graphics card and the system does not start"
1798921,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1798921,2019-03-14 09:16:18 UTC,"This actually came to Xenial via upstream stable 4.4.176. This went into v5.0-rc8 upstream, so it is by now released on devel/disco. I am adding additional nominations to act as reminders for those releases."
1798921,2019-04-08 10:50:49 UTC,"Hey there, I'm having this issue with a Mint 19 (bionic) installation and two Marvell 88E8053 NICs. Logged in, press the power button or the Suspend menu, computer goes to sleep. When awoken from the power button, ""Network cable is disconnected""."
1798921,2018-12-07 16:20:49 UTC,"Sorry, didn't realize what was meant. I don't use WoL, only suspend (manually or by closing the lid). Resume works for me with the 4.13 kernels Mint provided so far. All of the 4.15 kernels I tried so far didn't work."
1798921,2018-12-06 19:21:46 UTC,"For me, it works with any 4.13 kernel."
1798921,2018-12-05 05:33:39 UTC,So there are three different issue:
1798921,2018-12-01 23:43:04 UTC,Would this bug effect WoL functionality?
1798921,2018-12-03 20:46:53 UTC,I have the same problem.
1798921,2019-02-19 15:48:42 UTC,"Sorry for the late reply. Sent a patch:
https://lkml.org/lkml/2019/2/19/513"
1798921,2019-04-25 22:32:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1798921,2018-11-29 15:07:25 UTC,Please attach `sudo lspci -vvnn`.
1798921,2019-05-07 10:53:25 UTC,"Hi Podesta, Socratis and everyone affected,"
1798921,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1798921,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1798921,2019-06-01 08:03:57 UTC,"Sorry I couldn't test the pre-release version (out of order), but with my current version ""4.15.0-50-generic"", I still see the issue; the NICs aren't active upon wake up. I need the ""/lib/systemd/system-sleep/sky2-refresh"" workaround to make it happen:"
1798921,2019-06-01 08:26:33 UTC,"Socratis, this bug is platform dependent. Please file a new bug so we can find an in-kernel solution."
1798921,2019-06-04 21:45:53 UTC," ....this bug is platform dependent....
or maybe also from hardware?
I am helped by adding options in grub / kernel
GRUB_CMDLINE_LINUX_DEFAULT=""quiet splash pci=nomsi,noaer""
????"
1798921,2019-06-28 23:12:17 UTC,"Confirmed fix with:
    ""Linux 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64"""
1798921,2019-07-20 15:21:56 UTC,4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
1798921,2019-07-22 07:39:41 UTC,"kris (ski007), I think that I may have spoken too soon. I've been testing with the same ""4.15.0-53-generic"" kernel, and the issue seems that hasn't been resolved. Workaround is still:"
1798921,2019-08-06 01:09:05 UTC,"I'm new to the community, I wanted some guidance on how to report this bug. I have a Samsung RV510 Notebook, which uses this ""sky 2"" Driver to manage the Notebook's Lan network interface. Upon returning from sleep, the Lan interface stops working and only works when you completely restart the Notebook. I've read some comments here in the topic, including that the bugs were fixed in some kernel versions, but for me the version: 4.15.0-55.57 and 4.18.0-25.26 still have the same bug. I did some tests on other distros not based on Ubuntu and using newer Kernel, the problem also happens, very strange this problem. An interim solution I found in this topic was the ""quiet splash pci = nomsi, noaer"" which I believe has temporarily solved the problem. I appreciate the community response."
1798921,2019-08-06 06:28:02 UTC,"ricardovitor,"
1798921,2018-11-30 21:42:41 UTC,"Hello
I no longer use the suspend option
I replaced the HDD drive with SSD :-)
if you need a command result from a Samsung R780 laptop
I give it:
http://paste.ubuntu.com/p/9qfjpvSgd7/"
1798921,2019-09-13 07:55:15 UTC,"OK ,,,,,, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841304"
1798921,2019-04-29 16:03:34 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1798921,2018-11-29 14:56:29 UTC,"I wonder what performance penalty ""pci=nomsi,noaer"" would has?"
1798921,2018-11-15 20:35:37 UTC,I'm now using Debian - everything works OK ?
1798921,2018-11-04 17:39:10 UTC,"I just installed it .... it does not work
there is still an error:
""sky2 ethernet card do not work after returning from suspension""
regards"
1798921,2018-11-18 16:31:10 UTC,"I'm sorry but it's probably the fault of a particular laptop Samsung R780 :-(
I checked the recurring error on the internet :
[ 380.567633] do_IRQ: 3.34 No irq handler for vector
I applied fix to grub file : pci=nomsi,noaer"
1798921,2018-10-20 00:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1798921,2018-10-23 17:08:11 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1798921,2018-10-24 18:18:13 UTC,Please try the kernel in https://people.canonical.com/~khfeng/lp1798921/
1798921,2018-11-04 17:22:10 UTC,"4.19.0-041900-generic
kernel-bug-exists-upstream  :-("
1798921,2018-11-04 17:36:09 UTC,"kris,"
1798921,2018-11-04 17:46:28 UTC,"uname -a
Linux kris-R780 4.15.0-39-generic #42~lp1798921 SMP Wed Oct 24 05:59:26 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1798921,2018-11-06 02:39:15 UTC,"Please attach the dmesg when the issue happens, thanks!"
1798921,2018-11-06 16:45:38 UTC,my dmesg saved on pastebinit
1798921,2018-11-12 02:17:37 UTC,"I came in to apologize for not testing the posted kernel before and finally do it. Went on to use the ethernet only since yesterday, and couldn't get the bug anymore, while it happened 100% of the time before."
1798921,2018-11-12 18:54:57 UTC,"and which kernel is corrected :-)
Now I have :
Linux kris-R780 4.19.1-041901-generic #201811041431 SMP Sun Nov 4 14:33:06 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
the same error........"
1798921,2018-11-12 21:48:55 UTC,"I ran some tests today to try and pinpoint it a little better, and understand why I didn't encounter it when testing a couple days ago. For me, the case seems to be related to the user that suspends."
1798921,2018-11-12 06:07:12 UTC,Thanks. I'll upstream the change when you confirm it really fixes the issue.
1798921,2018-11-13 15:58:35 UTC,"I will say yes, I have three systems
Linux Mint / Xubuntu / Debian (stretch)
Debian (stretch) stable: kernel 4.9.XXX - sky2 / suspend - OK
Linux Mint 18.3 Sylvia: kernel 4.13. XX - sky2 / suspend - OK
Xubuntu 18.04.1 LTS: kernel 4.19.1 - sky2 / suspend - Error
sky2 works OK also on kernel 4.14.xxx
I think sky2 does not work correctly on kernels above 4.14 ....
but I am not a specialist, maybe others will speak :-)
for now I will still use this fix:"
1798921,2018-11-18 00:57:31 UTC,"I'm running Gentoo with a 4.19.1 kernel on a macbook 3.1. If you want me to revert that git, do bissects, etc, please just ask, I won't be able to run debian/ubuntu kernels."
1798921,2018-11-16 11:43:07 UTC,"what to do .... if no one can fix it :-)
I know the fix #15
it will be harder for other linux users :-("
1798921,2018-11-16 08:28:06 UTC,"Kris,
So your issue happens since commit bc976233a872. Once Debian starts using kernel > 4.14 then the issue will resurface again."
1798921,2018-11-15 19:59:43 UTC,":-) ....
I installed the kernel again from the link https://people.canonical.com/~khfeng/lp1798921/
the error with me is the same
dmesg : http://paste.ubuntu.com/p/CWBzNfHn98/
I'm not testing anymore
regards!"
1798921,2018-11-13 04:27:04 UTC,"> * Boot Computer -> login to BOB -> Suspend -> Wake -> login to BOB => NO PROBLEMS.
Then the issue is solve, from kernel's perspective.
"
1798921,2018-11-15 17:28:40 UTC,"maybe someone else will help with this error  ... :-(
regards!"
1798921,2018-11-15 18:06:43 UTC,"The head of your dmesg is ""Linux version 4.15.0-39-generic (buildd@lgw01-amd64-054)"" so it's not built by me."
1798921,2018-11-15 14:24:25 UTC,No it's not.
1798921,2018-11-15 12:53:22 UTC,Here you are #9  :-)
1798921,2018-11-15 06:13:07 UTC,"Please provide dmesg when the issue happens, under kernel in #7."
1798921,2018-11-14 17:29:45 UTC,And this is not the same as #7 ?
1798921,2018-11-14 14:38:13 UTC,"Kris, have you tried kernel in #3?"
1798945,2019-09-12 14:05:11 UTC,"Is this still an issue?
Are you using binary or source builds?
In the source builds gnocchi should be the latest version - in binary we are dependent on binary packages vendor."
1798945,2019-11-12 04:18:12 UTC,[Expired for kolla because there has been no activity for 60 days.]
1798946,2018-10-21 17:27:50 UTC,attaching logs from /var/log/dist-upgrade/
1798946,2018-10-21 18:13:17 UTC,"I managed to fix my system by booting a live system, chrooting into my installation and manually running `update-initramfs -u`. Still, this should be looked into."
1798946,2018-10-20 12:21:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1798954,2020-09-22 07:16:38 UTC,Marked this bug as invalid because Cosmic is not supported anymore. Thanks.
1798955,2018-11-21 09:24:45 UTC,Thank you for your bug report. Could you give the rational of why you think that new version should be backported to bionic (see https://wiki.ubuntu.com/StableReleaseUpdates about details of stable updates and why/when to do one)
1798955,2018-11-21 18:51:48 UTC,Hi Sebastien. Thanks for your help.
1798955,2019-04-20 18:19:44 UTC,"Hello Pedro, thank you for the bug report."
1798956,2018-10-22 04:52:08 UTC,The error in your logs is:
1798958,2018-11-25 20:09:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798961,2019-06-24 16:08:44 UTC,"ahci.mobile_lpm_policy=0 did not fix it, it hung in a few days.  I will downgrade to 18.04.  And small correction, this is an asrock deskmini h110m-stx system, not a NUC."
1798961,2019-06-21 16:12:16 UTC,"@karl-piccket try booting with ahci.mobile_lpm_policy=0, and then try comment #42 if it doesn't work."
1798961,2019-06-21 15:45:58 UTC,"I am using 19.04.  I have a Pentium G4600 desktop (Intel NUC, kaby lake, intel 630 HD graphics) and have gotten hard lockups on average every 24 hours, and always while playing video usually in chrome.  This system was rock solid with 18.04 :("
1798961,2019-05-31 22:03:12 UTC,"Sorry I thought this was a thread about Brave Browser and freezing, not just Ubuntu in general.  Well touch wood I only get freezes with Braze meaning I'll have to ditch Brave Browser."
1798961,2019-05-31 21:57:24 UTC,Hi All.
1798961,2019-05-25 10:05:46 UTC,"I was getting random freezes on a Dell Latitude E7450 with Intel HD Graphics 5500, with no hints as to the cause in logs that I could find. Freezes could happen multiple times a day when in heavy use, but often more like once a week. I followed the advice in #42 a month ago and have had no freezes since (fingers crossed!)."
1798961,2019-05-20 07:08:28 UTC,"The correct solution to the problem I've been facing was finally solved on comment #58, thanks @prasanth-s-cmi. I've contacted the kernel developer responsible for these patches introduced around Linux 4.16.1 on https://bugzilla.redhat.com/show_bug.cgi?id=1571330 , and he will blacklist my laptop model (Lenovo G40-80) for newer versions of Linux. Meanwhile, `ahci.mobile_lpm_policy=0` can workaround this problem."
1798961,2019-05-15 19:31:52 UTC,I also confirm that Paco Angulo (3rpako)'s suggestion (#42) worked for my laptop too. It's Asus with I7 core running Debian-10. Thanks Paco Angulo.
1798961,2019-05-14 00:51:58 UTC,"I've had these freeze issues for a while, and I've been following this thread for a while (comment #42 helped, though I still have occasional freezes)."
1798961,2019-04-23 23:31:24 UTC,"The workaround from #42 seems to make the hard lockup less frequent for me, but it's not completely gone. I still experience a complete freeze from time to time. It's completely aleatory, and it doesn't seem related to the workload, although I suspect that it's related to powersaving. From my experience, the probability of being hit by the freeze increases around a standby or resume event, or around plugging / unplugging the laptop."
1798961,2019-05-03 04:50:37 UTC,I haven't been bitten by this bug with an uptime of 9 days with workaround #42. But I had not the opportunity to test suspending my laptop during this time.
1798961,2019-05-02 08:04:59 UTC,"Unfortunately I have to confirm that the workaround from #42 only makes the hard freeze less frequent and doesn't solve it like I stated in #53.
I also have the impression that standby/resume increases the probability of a freeze, but I just had one about one hour after a fresh new start."
1798961,2019-04-23 16:28:28 UTC,"After uptime 15 days, 10:34 with countless standby/resume cycles, I think it is pretty safe to say that the solution from #42 works for me too."
1798961,2019-04-23 11:50:16 UTC,"This bug has become a catchall for any type of system unresponsiveness. I had hope the hard-lockup problem would be solved on Linux 5.0, Ubuntu 19.04, but it wasn't. I'll try the solution from #42 and report back. The probable root cause of the problem may be investigated on the diff from comment #23."
1798961,2019-04-18 01:31:13 UTC,"I have encountered this problem on Ubuntu Bionic (running in VMWare Fusion) with Chrome latest open. Chrome will start drawing the page randomly (I've seen that on really old versions of Chrome on Mac). When it starts doing that I can lock-up my OS by doing a `killall chrome` from terminal. When I do that, I can still move my mouse, but clicking doesn't register. I end up having to reboot my VM."
1798961,2019-04-12 17:42:50 UTC,Is it the same as https://askubuntu.com/questions/1133341/xubuntu-18-10-locking-weird-behavior ?
1798961,2019-04-12 16:24:44 UTC,"I have a freeze issue when it sits unused for about 15 minutes. The issue I found is that the Keychain is using a massive amount of system resources. I have launch a console session with alt+F# (which takes about 5 minutes to show), run top, and then kill the keychain process. Then the system responds like normal. This never happened with 18.04, only after upgrade to 18.10."
1798961,2019-05-07 13:52:40 UTC,"Seems like a kernel issue, marking invalid for intel but feel free to reopen if it proves out to be an issue with the driver (not that -intel is deprecated in favor of modesetting nowadays)"
1798961,2019-06-29 18:46:03 UTC,"I had been experiencing the freeze/lockup on 18.10. My main machine is a Lenovo ThinkPad laptop with switchable graphics (Intel & Nvidia), and Intel Xeon E-2176M CPU."
1798961,2019-04-02 08:01:34 UTC,"@teresaejunior Yes, currently trying it, will report back!"
1798961,2019-07-04 15:46:44 UTC,"I was also getting random freeze (multiple times a day), and using the ahci.mobile_lpm_policy=0 appears to solve the issue as well (didn't try another value).
BTW, I am using Debian (kernel  4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15))
Laptop: HP 15-ay005nf (core i3 5005U with Intel graphics 5500)
The bug happens with the original 1TB WD Blue (WD10JPVX) HDD and with a Samsung 860 EVO 250GB SSD."
1798961,2020-09-03 09:06:43 UTC,This bug is closed. Please use the 'ubuntu-bug' command to open a new one.
1798961,2019-04-01 20:58:17 UTC,@dode Have you tried #42?
1798961,2020-09-03 08:44:39 UTC,"This happens to me every week on Ubuntu 16.04. LTS with kernel 4.15.0-112-generic. It seems to be  a random complete system freeze. The mouse does not respond, caps lock and numlock do not change light on keyboard, ctrl alt f2/f3/etc does not work, and even Alt + SysRq REISUB does not respond. Only a hard reset works by pressing the power button will reboot the system."
1798961,2020-06-02 07:05:31 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1798961,2020-06-02 07:04:06 UTC,Everyone please report NEW bugs by running:
1798961,2020-05-19 01:50:37 UTC,I also experienced regular system freeze when playing youtube videos. The freeze would not occur after removing xserver-xorg-video-intel. I am on 20.04.
1798961,2020-04-29 00:12:52 UTC,UPDATE: freezes stopped occuring since I uninstalled xserver-xorg-video-intel.
1798961,2020-03-29 19:43:05 UTC,I am experiencing the freeze regularly since I attached an external display through HDMI.
1798961,2020-02-13 02:24:40 UTC,"I have the same issue but have not investigated further as yet.
I have recently upgraded however the issue was there before. I'm leaning toward a hardware issue."
1798961,2020-01-02 23:03:46 UTC,Addition: neither #42 nor #58 doesn't help. The problem persists in 19.10 too.
1798961,2019-12-28 16:43:34 UTC,I confirm Solution #58 (add `ahci.mobile_lpm_policy=0` to boot options works great). Thanks @prasanth-s-cmi!
1798961,2019-12-17 21:48:10 UTC,Happening to me too. Full details available on this issue: https://github.com/brave/brave-browser/issues/7439
1798961,2019-12-10 09:44:19 UTC,"Hey guys,"
1798961,2019-11-14 19:38:03 UTC,"This happens to me about three times a week on Ubuntu 18.04.3 LTS with kernel 4.15.0-70-generic. I have not been able to find a way to consistently reproduce it. It is a random complete system freeze. The mouse does not respond, caps lock and numlock do not change light on keyboard, ctrl alt f2/f3/etc does not work, and even Alt + SysRq REISUB does not respond. Only a hard reset works by pressing the power button will reboot the system. The first sign of it happening is the mouse begins to stutter for a couple seconds before the whole screen completely freezes. Here is some system info:"
1798961,2019-11-09 19:47:46 UTC,How to reproduce?
1798961,2019-11-03 22:45:38 UTC,"I have been a victim of the same behaviour on Debian* for about 6 months.
The computer, assembled with amd64 architecture, crashes with both Debian 9 and Debian 10, both with proprietary NVidia and Nouveau drivers."
1798961,2019-10-25 14:39:31 UTC,"I can confirm this bug also on a Dell XPS desktop system, which was running Ubuntu for several years and versions before without any issues. In my case the freeze happens with mostly Chrome browsers, usually within a minute or so. It renders the system practically unusable, so I would consider it as a high priority issue for 19.10. The recent kernel upgrades (official) were not solving the system."
1798961,2019-10-09 10:51:55 UTC,"Same issue, here, on Latitude 5547 with Intel Haswell i3 and Haswell-ULT integrated (HD 4400) graphics. This laptop has fully upgraded hardware - new SSD, new 16GB RAM, new battery, new Wifi/BT card - and performs like a monster, running Windows, Manjaro, and most Ubuntu flavors, including a touchscreen. However, my goto is Ubuntu Studio (xfce), and that OS is where I'm getting the random freezes. It just locks up under no repeatable conditions. Sometimes it happens while I'm working, sometimes while I'm away from my desk, sometimes with apps running, sometimes with no apps open, so workload is not a factor."
1798961,2019-08-25 18:26:37 UTC,I am having the same issue since 18.04. I monitored the memory usage in system monitor. The total RAM uses increases gradually after the boot. Even if no program is running it goes on increasing until it is 100% and then everything freezes. The memory uses by the processes doesn't add up to the total memory uses shown. Whichever program is eating the RAM is not listed in the processes. The issue remains in 19.04.
1798961,2019-06-29 18:47:36 UTC,kernel crash logs attached
1798961,2019-04-01 11:59:55 UTC,Unfortunately I have to revoke my comment #44 - had again two freezes with 4.18.0-16-generic in the last few days.
1798961,2019-03-27 10:36:22 UTC,"I think that I have similar issue:
On Kernel 4.18.0-16-generic I had:
 1) Two unrecoverable freezes (sound looped, unable to SSH)
 2) Random software crashes with segfault in dmesg
 3) Random Chrome tab crashes with ""trap invalid opcode"" in dmesg"
1798961,2019-03-19 21:10:54 UTC,For me on a DELL Latitude E5550 it seems the issue is solved since update to 4.18.0-16-generic (kubuntu). Running for a week now with several suspend/resume cycles - no more frost. Spring is coming  :-)
1798961,2018-11-27 07:41:18 UTC,Please perform a kernel bisection to find which commit introduces the regression.
1798961,2018-11-26 23:03:38 UTC,"After around two days of running with `pcie_aspm=off', it does not make any difference. I was just forced to do a hard reset of my laptop."
1798961,2018-11-25 10:02:19 UTC,"teresaejunior, could you try that:"
1798961,2018-11-25 06:59:05 UTC,Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283
1798961,2018-11-25 06:55:30 UTC,"I also have had random system freezes ever since I upgraded from 18.04 to 18.10, Linux 4.18.0-10-generic, solved by always booting into 4.15.0-36-generic. When the freezes happen, the screen simply stops, and no input is accepted, not even the usual REISUB."
1798961,2018-11-14 15:14:49 UTC,There are no noticeable error message. It can be hardware freeze. Can you try 4.20-rc2 and boot with kernel parameter `pcie_aspm=off`?
1798961,2018-11-13 14:14:46 UTC,"It happened again.
See the attachment of the output of journalctl -b -1 -k"
1798961,2018-11-12 13:24:06 UTC,I have the same freeze problem https://bugs.launchpad.net/ubuntu/+bug/1802902 and seemingly fixed it by deleting the folder .cache/thumbnails/fail
1798961,2018-11-12 10:20:42 UTC,"I have updated to A16 and so far no freezes, although it's still not uncommon for these to stop happening for a while and then return."
1798961,2018-11-12 06:23:01 UTC,"The bug in #4 is for Ryzen platforms, so it doesn't apply to Inspiron 5458, which seems to be a Broadwell platform."
1798961,2018-11-06 14:37:18 UTC,"The problem is, it could take days before the system freezes. I don't know how to reproduce, it simply happens. I don't even know where to start. Maybe 4.17-rc1 and so on. But that's a huge task and one needs a lot of patience to do it. I'm not sure I'll be able to."
1798961,2018-11-05 14:30:45 UTC,Would it be possible for you to do a kernel bisection?
1798961,2018-11-05 12:33:22 UTC,"Hey, have you found any solution? I have the same issue and changed the default kernel now to 4.15.0-36-generic. This is working, but it would be better with the new kernel."
1798961,2018-10-22 00:09:38 UTC,Affects the latest mainline build 4.19-rc8 as well.
1798961,2018-10-20 19:36:08 UTC,This is the bug report opened for Arch Linux [TASK FS#59483]:
1798961,2018-10-20 17:31:00 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1798961,2018-10-20 13:30:07 UTC,This change was made by a bot.
1798961,2018-12-18 16:50:19 UTC,I have the same problem very often during a day on a Lenovo ThinkCentre M900 (see specs below).
1798961,2018-12-22 05:17:47 UTC,I tried Kernel/MainlineBuilds (https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D) with my Dell XPS13 (9343).
1798961,2018-12-13 17:04:32 UTC,"I just would like to add that I have the same problem about once a day on a DELL Latitude E5550, usually a relatively short while after resuming from standby. It never happens when I boot into the older 4.15.0-39-generic kernel."
1798961,2019-01-02 11:19:42 UTC,This happens to me on a clean install with OS updates installed 19/01/01.
1798961,2019-03-18 16:37:56 UTC,"I confirmed that 3rpako's settings work for my env too.
My env is Dell XPS13 (9343) + Xubuntu 18.10."
1798961,2019-03-08 23:08:45 UTC,"Had same frozen display problem with Ubuntu, most times coincident with a very busy video adapter (MVP, Gimp, GMaps..)
Hardware: Laptop Acer Aspire 5735Z
Ubuntu 18.10
Linux 4.18.0-13-generic"
1798961,2019-03-06 21:01:16 UTC,"I'm using this same version of ubuntu. Before crash I've opened new terminal window Ctrl + Alt + F1 and then I 'saw NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [plymouthd:305]'.
In my case this do the trick:
https://askubuntu.com/questions/875173/nmi-watchdog-bug-soft-lockup-cpu2-stuck-for-23s-plymouthd305"
1798961,2019-02-28 15:50:09 UTC,"I have been using kernel 4.18.0-15-generic for 3 weeks now, and I haven't had this issue anymore."
1798961,2019-02-28 09:34:36 UTC,I have the Problem with Kerner 4.15.0-43.
1798961,2019-02-11 09:53:48 UTC,"Same freezing error.
Clean 18.10 install"
1798961,2019-02-08 10:33:13 UTC,"Same freezing error.
Clean 18.10 Ubuntu instal.
Processor: Ryzen
Nvidia drivers installed from nvidia homepage."
1798961,2018-12-28 19:32:51 UTC,"I am running Kubuntu 18.10 w kernel 4.18.0-11-generic with AMD Ryzen 2700x CPU, I initially believed I had a Ryzen soft lockup issue, and I had posted in AMD community forums:"
1798961,2019-01-31 14:38:01 UTC,"Ubuntu froze again. It happened after closing the lid. There were streaks on the screen after opening. I held the power button. The laptop would not turn on again. Even the welcome screen did not appear. Just a black screen. I had to turn on and off several times. Only after an hour I could enter the bios settings and start the system from the repair disk. The disk scan did not report any errors. I had this before and then I had to reinstall everything, because the bios did not detect the disk. It was only the format and reinstallation of Windows and Ubuntu that helped. Now it happened again, but fortunately Ubuntu is visible after the start. I will format disk again and install Ubuntu, but now without nvidia drivers"
1798961,2019-02-01 10:48:37 UTC,"It turns out that the installation without nvidia drivers and the secureboot option also causes errors. After some time using the laptop, the screen freezes and only holding down the power button allows you to turn off. Unfortunately, after switching on again, there was a problem with the grub welcome screen. I could not even enter the bios settings. There was only a black screen. I had to press the power button several times until I was able to do it after an hour.
I have been using ubuntu for several years and this has never happened to me. The problem appeared a week ago on January 23. Previously, everything was fine."
1798961,2019-01-11 23:50:55 UTC,"I found a solution to my particular issue.
DISCLAIMER: I'm not positive that I experienced the same issue as other commenters since the problem was more pronounced than others have been describing. Since this is a new system, this was the first time I tried to install Ubuntu. I'll try to describe what I found in some detail since this was thread seemed like the most pertinent to my issue it may help others."
1798961,2019-01-11 18:14:32 UTC,I am encountering a similar issue on a new Dell G5 5587. I've installed Ubuntu 18.10 (fresh download today) alongside Windows 10 on a 1TB nvme SSD.
1798961,2019-01-10 14:43:42 UTC,Also running into the same issue. It's been happening ever since I installed 18.10.
1798961,2019-01-07 18:49:10 UTC,"Today the problem presented itself, twice, with kernel 4.15.0-43-generic in Xubuntu 18.10."
1798961,2019-01-04 15:50:42 UTC,"Hello. I had been using Xubuntu 18.04 since May to November, with no problems. This problem began when I upgraded to Xubuntu 18.10, using the Upgrade GUI. I work with my laptop around 10 hours a day, sometimes more, and since I installed 18.10, it freezes between 3 to 7 times a day, sometimes more. I work mostly with Firefox, 5+ tabs open, mostly Google Drive. I also have Dropbox running in the background. It seems to happen more often when I upload an image to a Google Drive file, or while performing a screen capture. Some other times while scrolling on a file, and once while using Atom."
1798961,2019-01-04 11:58:55 UTC,"I have been using Linux 4.15 as a workaround too. I noticed I could reproduce the bug easily by watching YouTube on Chrome in fullscreen. I know it is related to the GPU, but in my case, the Intel drivers (Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) v: 4.5 Mesa 18.2.2)"
1798961,2019-01-04 11:42:26 UTC,"I tried kernel 4.20 and 4.15 and keep having freezes.
I have a clean install. I used to have 17.10 on this machine without problems."
1798961,2019-01-03 19:32:41 UTC,My latest posting on this bug issue posted in AMD communities copied here FYI:
1798961,2019-01-17 00:10:17 UTC,"I also faced this same bug. I was casting video from my laptop to chrome cast- for about one hour it worked fine and then suddenly video stopped and laptop did not respond at all. It did not take any input. So, I had to hit the power button and switch it off and start it again."
1798964,2018-10-22 15:50:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798967,2018-10-20 14:28:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798968,2019-01-12 16:06:49 UTC,"We could add a new wire to the schematic that doesn't respect user preferences but I'd prefer not to do that.  And this edges into new feature territory.  This is something that we can address in the new toolset during v6, not for 5.1"
1798968,2019-05-07 19:41:49 UTC,"Fixed in revision a40367ce178a5656d5e5c9a988a40a750f6270b4
https://git.launchpad.net/kicad/patch/?id=a40367ce178a5656d5e5c9a988a40a750f6270b4"
1798968,2019-05-07 16:01:04 UTC,"the new behaviour of eemodern is similar to the old one, but it looses connection of indirectly connected nets."
1798968,2019-01-12 15:27:15 UTC,I don't think thats rubberbanding what the bug report is about. It's more about simply keeping the connection (adding wires if required)
1798968,2019-01-12 15:02:23 UTC,"That's one way of looking at it.  But we don't support rubberbanding at the moment (lp: 594054), so the new requirement will need to wait for that to be implemented."
1798968,2019-01-12 14:06:19 UTC,"@sethh, this fix does not seem to work correctly."
1798968,2019-01-11 01:31:01 UTC,"Fixed in revision 353bda6792c5af26b98adf3ab3d040fc476c3777
https://git.launchpad.net/kicad/patch/?id=353bda6792c5af26b98adf3ab3d040fc476c3777"
1798970,2018-10-20 15:16:47 UTC,+ the installer crashed when I wanna go in with the testing.
1798970,2018-10-22 17:46:50 UTC,"The bug is solved. I had 2 Ubuntu EFI's when I restart Ubuntu. I think that this had to do when I putting on 14.04 with the WUB installer. So, I formatted the USB and set only the 18.04 and installer on it, and wallah..."
1798970,2020-03-07 15:58:48 UTC,"Further to comment #3 by reporter, closing as invalid."
1798972,2018-10-22 02:06:54 UTC,"From the log, looks like a bug in ess 17.11-3.
Ref: https://github.com/emacs-ess/ESS/issues/635"
1798973,2019-06-03 07:48:47 UTC,"This issue is also present in vlc 3.0.7, but not in the 4.0 branch."
1798974,2018-10-22 01:35:23 UTC,Actually i'm using the Super key for other propose; its 18.10 cosmic.
1798974,2018-10-20 15:41:21 UTC,Cannot reproduce your issue.  18.04 or 18.10?
1798976,2018-11-11 21:10:57 UTC,Una forma temporal de solucionarlo es escribir en la terminal:
1798977,2019-11-13 14:59:57 UTC,"Hi, this bug also affect my system.
Ubuntu mate 18.04 with kernel 5.0.0-32 hwe (I need this kernel for the realtek wi-fi card rtl8723be).
In my case I have two sudoers users on my system (but I found the same issue with one sudoers and one nosudoers), if  plug in a usb drive it is ready for use in the account logged in, if I change the account without unplugging the usb drive, it will not be usable in the new account, but nor in the previous account.
The drive appears to be unmounted, but unmountable because locked from other process.
The problem affects usb drive with both ext4 format and exfat format.
If I unplug the usb drive before changing account, everything works fine."
1798977,2018-10-20 19:19:16 UTC,Please tell us what version of Ubuntu Mate you have and if the os it's up to date. Until then i will mark this as incomplete.
1798977,2018-10-20 20:22:46 UTC,Edited OP to include os version.
1798977,2018-10-23 01:08:02 UTC,dmesg output during the attempted mount:
1798977,2018-10-23 01:10:51 UTC,After switching to my spouse's session the attached picture is the dialogue box which has appeared.
1798977,2019-10-12 18:55:22 UTC,"This is still present in 19.10, and is actually worse than the OP realises: because of the bug also triggering the mount dialog in the first place, unprivileged users can't mount external drives at all."
1798977,2019-10-12 19:31:04 UTC,"To clarify that last part: if two users, Sudoer and NonSudoer, are both logged in, and NonSudoer is the active user, then even if they happen to be the one that gets the prompt (from Sudoer cancelling the mount dialog, certainly; but I don't know what happens if the prompt chooses to show up on NonSudoer's screen first) it will be asking for Sudoer's password rather than theirs."
1798977,2019-10-13 05:06:05 UTC,"Interestingly, plugging in the same device just now while the Sudoer account had the seat mounted it correctly: that is, successfully and without a prompt."
1798977,2019-10-18 11:46:02 UTC,"Tweaked the title slightly to save confusion over it reading as ""multiple users trying to mount the device concurrently"" (though that's realistically what the bug amounts to since the automount is running for both)."
1798979,2018-10-23 05:01:43 UTC,Would it be possible for you to do a kernel bisection?
1798979,2018-10-20 17:33:04 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1798979,2018-10-20 18:11:08 UTC,"> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
"
1798979,2018-10-20 17:00:06 UTC,This change was made by a bot.
1798996,2018-10-20 19:04:20 UTC,looks like .deb is bad too.
1798996,2018-10-20 19:07:24 UTC,"the deb can be started as root, be previously it would work as non-root too."
1798996,2018-10-23 07:48:47 UTC,Thank you for your bug report. What Ubuntu version are you using? Do you have any apparmor denial or such in the journal log?
1798996,2018-10-24 13:38:10 UTC,"To launch the deb I use $ /usr/bin/gnome-system-monitor, from a gnome-terminal."
1798996,2018-10-24 14:13:01 UTC,What is the output of:
1798996,2018-10-24 14:42:41 UTC,"$ snap version
snap    2.35.5+18.10
snapd   2.35.5+18.10
series  16
ubuntu  18.10
kernel  4.18.0-10-generic"
1798996,2018-11-09 15:24:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798997,2020-08-04 16:41:06 UTC,I can reproduce this problem on Ubuntu 18.04 using latest PPA 1.7+r1134-202008032046~ubuntu18.04.1
1798998,2018-10-20 23:24:00 UTC,"I've attached a short screen recording of the bug. I open 3 seperate applications: VSCode, VLC and Chrome and non of them show up in Plank. Note that if I switch desktops to 2 and back to 1, Plank will update and pick up the applications."
1798998,2020-09-23 03:04:43 UTC,"I use Ubuntu 20.04 in ubuntu:gnome-session. With the gnome-shell extension named pixel-saver which integrates APP title-bar into the gnome-shell dock enabled, plank won't show up when some APP is started up. I have to switch to another APP to activate it."
1798998,2018-10-29 08:36:16 UTC,Interesting.  No idea if this is a bug with plank ... or if plank is expecting something specific from budgie-desktop that it isn't currently providing
1798998,2018-10-28 18:31:03 UTC,I have Restrict to Workspace enabled.
1798998,2018-10-28 15:56:21 UTC,"@00knight have you got ""Restrict to workspace"" ticked in plank preferences - behaviours?  What happens if you untick that option?"
1798998,2018-10-20 22:37:05 UTC,Sorry. Cannot reproduce. Do you have a video showing what are doing to reproduce this?
1798998,2018-10-28 12:46:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1798998,2018-10-20 23:43:08 UTC,"Here's some warnings from when I booted Plank, and then VSCode:"
1798998,2018-10-28 12:50:17 UTC,Ubuntu Budgie LTS 18.04.1
1799004,2020-08-16 05:53:05 UTC,Yes indeed. I am looking for that too.
1799005,2018-12-07 20:14:28 UTC,"Is this bug being ignored?
Please, let me know if developers need me to test or upload any logs"
1799007,2018-11-01 19:21:34 UTC,ahhh well like I said that crash dump was from after uninstalling the jack packages. things are still broken without jack installed. no sound in any app.
1799007,2018-11-01 03:17:02 UTC,There is no need to send more crash reports right now. Just uninstall the jack packages and see if that solves the problem.
1799007,2018-11-02 01:50:42 UTC,"1. Can you please confirm where you are looking when you say ""it no longer shows any of the audio output devices""? Are you looking in Settings > Sound > Output ?"
1799007,2018-11-01 01:07:32 UTC,Repeated the crash report after purging the jack audio packages: https://errors.ubuntu.com/oops/831e65ae-dd64-11e8-959d-fa163ee63de6
1799007,2018-10-30 01:52:30 UTC,"Tessa,"
1799007,2018-10-30 03:05:53 UTC,"@vanvugt:  actually, PoP! is just a light themeing a driver PPA on top of Ubuntu, it doesn't really change a lot. it also uses pulseaudio, I installed jackd after I started having issues just in an attempt to get usable sound on my system, but it didn't improve the situation. but pulseaudio was definitely broken before I installed jack."
1799007,2018-10-30 02:11:29 UTC,"More simply, please try this command and then reboot:"
1799007,2018-10-29 17:54:33 UTC,"@vanvugt: alright, it's been uploaded, it says it's at this URL but I don't have permissions to view that and verify:
https://errors.ubuntu.com/oops/ffc53e0c-dba2-11e8-9fcf-fa163e6cac46"
1799007,2018-10-30 03:11:07 UTC,"OK, that makes sense. In that case I was misled by apport automatically writing this in the bug report:"
1799007,2018-11-02 17:46:15 UTC,"yes, that's where I've been looking. nothing listed for input or output in the sound control panel."
1799007,2018-10-22 11:03:12 UTC,"Ok, in my case, |fuser -v| reveals that it's being blocked by timidity."
1799007,2018-11-05 01:38:55 UTC,Try looking in /dev/snd/ :)
1799007,2018-11-05 21:47:14 UTC,"Ahh yes, there everything is in /dev/snd, so really starting to feel like a pulseaudio bug."
1799007,2018-11-05 22:56:43 UTC,"Booting off USB, sound works fine, soundcards show up correctly. So... it's something that got messed up in the upgrade from 18.04, I guess?"
1799007,2018-11-06 02:03:39 UTC,"Yes, I suspected as much. System76 wouldn't ship a laptop without working audio on Ubuntu."
1799007,2018-11-06 04:10:27 UTC,"I've already tried reinstalling pulseaudio, and it doesn't do anything. I can't really afford to reinstall my work laptop right now, I really need it to just, you know, work. ;)"
1799007,2018-11-06 04:25:42 UTC,The PulseAudio developers should be able to help you with more advanced debugging. You can log a bug to get help from them at:
1799007,2018-11-22 01:30:13 UTC,"ok, I've figured some more out with the help of system76 support:"
1799007,2018-10-29 02:05:35 UTC,"Franck, that's very strange. If you would like to keep discussing your issue then please log a new bug."
1799007,2019-07-22 03:43:52 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1799007,2018-11-02 17:48:44 UTC,note that the sound devices seem to be correctly detected by the kernel:
1799007,2018-10-26 16:41:04 UTC,"for me the problem is solved with :
sudo apt remove pulseaudio
reboot"
1799007,2018-10-21 17:39:15 UTC,"Digging into the pulse config on 18.10, it looks like instead of using the daemon mode it's trying to setup up some sort of IPC socket, but this isn't getting run correctly:"
1799007,2018-10-26 01:55:13 UTC,"OK, the wording is confusing but we still call it a ""daemon"" even though it has ""--daemonize=no""."
1799007,2018-10-20 21:22:43 UTC,other report in the wild: https://askubuntu.com/questions/1085176/sound-device-lost-after-update-to-18-10
1799007,2018-10-21 14:36:51 UTC,"Same problem here.
Upgraded ubuntu from 18.04."
1799007,2018-10-21 14:48:46 UTC,I've manage to get sound working again running:
1799007,2018-10-21 16:58:27 UTC,"hmmm. I tried that, but no dice for me. pulse starts in a terminal, but nothing in my session sees a sound device still. for the one started in a terminal, it doesn't respond to kill signals, and needs to be kill -9d."
1799007,2018-10-22 02:38:52 UTC,Please run this command to send us more information about the system:
1799007,2018-10-22 10:37:54 UTC,"I'm also facing the same issue, and ""apport-collect 1799007"" does not accept to run for me, stating I'm not on the bug :/"
1799007,2018-10-22 18:10:26 UTC,"@lissyx: so you're probably just experiencing #1797714. can you give the exact fuser command you ran and the output you saw though, so others can repeat that test on this bug?"
1799007,2018-10-22 18:10:34 UTC,apport information
1799007,2018-10-26 01:57:00 UTC,I mean please run:
1799007,2018-10-22 18:10:36 UTC,apport information
1799007,2018-10-25 02:49:15 UTC,I think the main hint is in comment #15:
1799007,2018-10-24 09:02:53 UTC,"Per the bug description, this is not related to Timidity."
1799007,2018-10-23 01:46:59 UTC,"Tessa,"
1799007,2018-10-25 19:29:13 UTC,"@vanvugt:  there's nothing in /var/crash from pulseaudio, and as noted above, pulse is started in non-daemon mode by Ubuntu. so it's running, but apps can't seem to talk to it. probably because of the failure to start the socket service, as noted above. without the socket, and without it being a daemon, I don't think there's any way for apps to actually reach pulse."
1799007,2018-10-22 18:14:15 UTC,"```
tessa@viper:~$ fuser -v /dev/snd/pcmC*
                     USER        PID ACCESS COMMAND
/dev/snd/pcmC0D0c:   tessa     11703 F...m pulseaudio
/dev/snd/pcmC0D0p:   tessa     11703 F...m pulseaudio
tessa@viper:~$ pacmd list
Daemon not responding.
```"
1799007,2018-10-22 18:10:39 UTC,apport information
1799007,2018-10-22 18:10:38 UTC,apport information
1799007,2018-10-22 18:10:35 UTC,apport information
1799012,2019-01-21 20:35:20 UTC,This bug appears to be fixed in disco.
1799015,2018-10-22 09:30:04 UTC,could you provide detailed steps to reproduce?
1799015,2018-10-22 11:19:31 UTC,"Made a new install of Inkscape, then go open L-Systems.
Replace the default axiom with A. Change the left and right angles to 90
degrees.
Write in the rules ""A=B[+A][-A]"" and turn on live preview
Then, add ""B=BB"" and the tree should become a single segment"
1799015,2018-10-22 13:13:06 UTC,"thanks for the info.
unfortunately, I do not know enough about Lindenmayer to be able to judge what the correct behavior is, will have to wait for someone else to comment."
1799015,2018-10-22 13:29:28 UTC,"It is supposed to make a tree shape, with the branches coming off half the
length of the one they branched off from"
1799015,2020-02-09 20:46:02 UTC,"Hi Romaji, this is possible by separating the rules with a semicolon (i.e. ""A=B[+A][-A];B=BB"")."
1799023,2020-07-30 19:04:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799028,2018-10-21 08:10:37 UTC,Recently reported in Kubuntu as https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1799028
1799028,2016-08-10 18:32:10 UTC,Ack on fresh install and up to date Kubuntu 16.04 LTS.
1799028,2016-08-26 04:27:52 UTC,"Hi,"
1799028,2014-11-16 09:14:56 UTC,Using K3B 2.0.2 on debian Jessie (I'm up to date as of today).
1799032,2019-12-07 10:34:55 UTC,Thanks for reporting :)
1799033,2018-10-21 10:36:23 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1799037,2020-04-27 09:21:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799043,2018-11-01 16:49:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1799043,2020-03-07 11:23:40 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner
1799044,2019-01-14 13:03:01 UTC,"I've read https://github.com/yama-natuki/JD/issues/15 and now I understand it is a fork, and I'll submit RM request for this JD package to Debian ftpmasters."
1799044,2018-12-02 17:24:30 UTC,"Well, what's the relationship between https://github.com/yama-natuki/JD/tree/test
and current upstream? (Is it fork?)"
1799044,2019-03-26 13:26:21 UTC,"Thank you very much.
I'm sorry to late reply for your responses.
There is no excuse,I apologize to you."
1799050,2019-02-11 20:38:22 UTC,"Hi,"
1799050,2018-10-21 13:31:22 UTC,Ubuntu 18.10 indicator-stickynotes problems
1799054,2019-01-10 12:17:52 UTC,"The issue is known upstream, https://gitlab.gnome.org/GNOME/gnome-control-center/issues/191"
1799054,2018-10-22 14:07:49 UTC,It looks like something is eating/leaking file descriptors. I guess that's going away after a reboot? Any chance to use lsof to see which process is using your fds?
1799054,2018-10-22 15:09:42 UTC,The CPU usage drops after a while with Background > Desktop still open and the RAM usage drops when Settings is closed.
1799054,2018-12-12 10:14:11 UTC,What's the number of images you have in /home/adam/Pictures/?
1799054,2018-12-12 10:22:56 UTC,"1919, didn't realize it was quite that many xD Still, is it reasonable to expect this sort of delay or could GNOME process it better? Files is still functional when loading it whereas Settings isn't, apparently..."
1799054,2018-12-12 10:23:29 UTC,"(you should be able to reproduce the issue by taking 100 or so screenshots and then making lots of copies and doubling from there, perhaps)"
1799054,2018-12-12 10:25:43 UTC,"(when the delay is happening Settings becomes unresponsive so I can't exit from the Background > Desktop window and it slows down the rest of the computer too, which loading Pictures in Files doesn't do at all)"
1799059,2018-10-26 16:32:19 UTC,"yeah, it's a Budgie session (Ubuntu Budgie)."
1799059,2019-03-23 12:40:02 UTC,"On Cosmic, it's crash too. No Fixed yet."
1799059,2018-10-26 09:14:32 UTC,"""** Message: 18:25:28.743: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11."""
1799059,2018-10-24 16:27:35 UTC,Here you are.
1799059,2018-10-22 14:03:50 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1799061,2018-10-21 15:38:43 UTC,Also note that the screen jitters at the GDM login screen.
1799061,2018-10-22 03:00:06 UTC,This change was made by a bot.
1799061,2019-07-22 04:15:10 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1799064,2018-10-22 03:00:13 UTC,This change was made by a bot.
1799064,2018-10-22 03:03:25 UTC,Please try installing an older kernel like that which was in Ubuntu 18.04:
1799064,2018-11-05 20:25:27 UTC,"Works in 4.15.0, but fails in 4.16.18 and 4.17.19. I don't have time right now to try earlier point releases (plus this is an infuriatingly slow system), but hope this helps narrow it down a bit, at least."
1799064,2018-11-06 02:30:05 UTC,This change was made by a bot.
1799064,2018-11-06 02:32:38 UTC,"Can kernel parameter ""usbcore.enable_autosuspend=0"" workaround the issue?"
1799064,2018-12-16 14:50:05 UTC,Apologies for the belated response. Unfortunately that does not seem to work around the issue.
1799064,2018-12-17 07:02:56 UTC,"And apology from my side, it should be ""btusb.enable_autosuspend=0"" instead."
1799064,2018-12-18 20:21:42 UTC,"Many thanks for the pointer - that workaround did indeed work!
If there's any detail I can provide to help fix this properly, do let me know."
1799066,2019-12-18 06:11:10 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1799066,2018-10-24 06:04:54 UTC,Does [1] help?
1799066,2018-10-21 16:47:10 UTC,Cannot test other kernels on Live CD
1799066,2018-10-21 16:31:13 UTC,Issuing those two commands found on Arch wiki:
1799066,2018-10-21 16:36:18 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799066,2018-10-21 16:26:42 UTC,"After suspend, xinput claims both devices are still there:"
1799066,2018-10-21 16:25:47 UTC,"After suspend (S3 suspend enabled in BIOS since BIOS v1.30), trackpad and trackpoint are dead again. After some swiping for a few minutes, trackpad is working again. Trackpoint remains dead (along with its physical buttons). I attach the dmesg gathered after suspend."
1799066,2018-10-21 16:18:13 UTC,"Attached is dmesg output. It clearly indicates that the kernel tries to connect the device(s) a few times before it succeeds. Not ideal, but we can say it makes the distro installable if the user waits a few minutes for the reconnection."
1799066,2018-10-21 16:30:08 UTC,This change was made by a bot.
1799073,2020-04-16 02:11:27 UTC,This works great in 20.04
1799073,2020-02-12 02:00:26 UTC,"I think there is upstream work coming in Gnome Shell 3.36 related to this, but it doesn't seem to work in 20.04 right now. Which are you referring to?"
1799073,2020-02-11 16:13:15 UTC,This is fixed in Ubuntu 20.04
1799073,2018-10-22 08:01:29 UTC,"That work-around works perfectly, thank you *SO* much!"
1799073,2018-10-22 07:59:46 UTC,apport information
1799073,2018-10-22 07:59:47 UTC,apport information
1799073,2018-10-22 02:54:22 UTC,Please also run this command to send us more information about the system:
1799073,2018-10-22 02:53:51 UTC,"As a workaround, please try:"
1799073,2018-10-22 02:52:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799073,2018-10-22 02:56:08 UTC,"After applying the workaround in comment #2, the zoom keys seem to start working."
1799078,2018-10-31 10:11:23 UTC,The keepalived password will typically be generated via kolla-genpwd. Is there any reason not to use the generated password?
1799078,2018-10-31 10:30:54 UTC,"So far I tracked this issue down to this password generation script [1] which is run by Vagrant provisioner. Don't know why yet, but in my case after VM was provisioned and running, it ended up with blank /etc/kolla/passwords.yml. When I run the script manually it autofilled passwords, so I suspect something might overrode generated passwords or might be case with rights."
1799080,2020-05-10 09:47:08 UTC,IS this one now fixed?
1799080,2018-10-22 06:20:16 UTC,I think this is another aspect of the same bug: https://bugs.launchpad.net/mixxx/+bug/1405010
1799080,2018-10-28 11:09:32 UTC,"Is the situation improved with:
https://github.com/mixxxdj/mixxx/pull/1716"
1799080,2018-10-22 14:51:32 UTC,"yes, correct."
1799080,2018-10-22 01:10:56 UTC,"Alternatively, we can auto-generate an arbitrary number of beats (64?) off the beginning and the end of the track and then we don't need any code changes to fix this bug.  However all existing tracks will have this bug"
1799080,2019-12-15 21:57:21 UTC,That PR does appear to fix the issue!
1799080,2018-10-21 23:05:05 UTC,proposed solution:
1799080,2018-10-21 20:52:49 UTC,"hm, getbpmaround relies on findnthbeat returning -1 so it can know about invalid requests. I'll have to think more about how best to handle this case transparently.  (unless we don't want a workaround solution?)"
1799080,2018-10-21 20:12:23 UTC,"It is exactly this problem.  If the DJ pushes ""play"" before the first beat, findNthBeat gets called at a place where there is no data for beat -2."
1799080,2018-10-21 19:56:37 UTC,"This could be a symptom of the m_pBeats->findNthBeat(dThisPosition, -2) logic that a comment warns about..."
1799080,2018-10-21 23:05:40 UTC,"(therefore, getbpmaround can note if the position is artificial and know that the beat was out of range)"
1799081,2018-10-22 03:58:00 UTC,"It is interesting that this is not reproducible in Lubuntu. We've apparently got something Ubuntu doesn't, which is strange, because we're quite similar at the core. Maybe try installing lubuntu-core or the lxde (or maybe lxde-core) metapackage and see if you can't figure out what you're missing. My guess is that this comes down to a missing package."
1799081,2019-09-13 18:45:13 UTC,"This describes my problem too (since some time).
Cut and past don't work in PCManFM 1.2.5, but works on the very same file in the default file manager Filer 3.26.4.
That should rule out other stuff I think."
1799081,2019-11-05 17:37:57 UTC,"Same here (for a while now)
I am using ubuntu + Pcmanfm and installed the lxde package (with 18.04 I prefer lxde)"
1799085,2018-10-21 20:02:22 UTC,It does not sound related to applets at all... Anyway changed to mate-applets - MATE devevelopers probably will move to correct package if needed.
1799085,2018-10-21 19:57:42 UTC,I'm using ubuntu mate on virtual box on os x as host machine. I don't know whether this related to trackpad or not. When I use external wired mouse text selection works fine. I really don't understand why this happening. I tried other desktop environment like gnome budgie and it works fine. But I gnome classic so I want to fix this issue on mate.
1799085,2018-10-21 19:32:04 UTC,How is this related to gnome-applets?
1799085,2018-10-21 19:53:17 UTC,I'm new on linux. This problem is related to mate desktop environment. I'm unable to select text properly.
1799095,2019-03-13 08:38:11 UTC,"FTR, the default backend has been reverted to iptables in last uploads of firewalld"
1799095,2019-10-16 18:50:03 UTC,I did not tried but it seems to be the way to go ?
1799095,2019-10-16 18:50:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799095,2020-08-07 07:39:48 UTC,"This somehow does not affect Ubuntu 20.04 LTS, but it does affect the current ""groovy"" release again:"
1799098,2018-10-21 22:19:23 UTC,"/etc/init.d/isc-dhcp-server has a comment
                if test -n ""$INTERFACES"" -a -z ""$INTERFACESv4""; then
                        echo ""DHCPv4 interfaces are no longer set by the INTERFACES variable in"" >&2
                        echo ""/etc/default/isc-dhcp-server.  Please use INTERFACESv4 instead."" >&2
                        echo ""Migrating automatically for now, but this will go away in the future."" >&2"
1799099,2020-01-25 11:35:54 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1799099,2018-10-21 22:28:43 UTC,An EMF from the govdocs1 corpus - http://downloads.digitalcorpora.org/corpora/files/govdocs1/by_type/
1799099,2018-10-21 23:03:00 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1799101,2018-10-22 14:25:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799101,2020-01-25 19:50:51 UTC,"https://launchpad.net/ubuntu/+source/sway/
shows sway included in Ubuntu from the disco release"
1799102,2018-10-23 14:22:27 UTC,dmesg with 4.19.0-041900-generic is attached. 4.19-rc8 has the same WARNING on boot.
1799102,2018-10-22 00:12:17 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799102,2018-12-08 18:31:07 UTC,What causes this WARNING is the host kernel.
1799102,2018-10-21 23:00:06 UTC,This change was made by a bot.
1799102,2018-10-21 23:05:49 UTC,Host information:
1799103,2020-01-24 11:30:41 UTC,"thank you Daniel,"
1799103,2020-08-07 09:53:47 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020."
1799103,2019-09-21 23:35:54 UTC,"hi Daniel,"
1799103,2020-01-24 09:05:54 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1799103,2019-07-22 04:15:31 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1799103,2019-07-22 10:20:38 UTC,"hi Daniel,"
1799107,2019-09-10 14:02:04 UTC,Has it ever been resolved somehow? So far this is the only solution I could find.
1799107,2019-09-16 13:08:23 UTC,seein the same problem too
1799109,2018-10-30 04:03:39 UTC,I encountered this issue by using ubuntu/xenial queens configurations.
1799109,2018-10-31 10:25:50 UTC,"Perhaps a safer option for stable branchs would be to pin the openstacksdk library? We could bump the version of python-openstackclient in master, or just rely on upper-constraints."
1799109,2018-10-31 10:26:23 UTC,"Takashi Sogabe, is this something you are able to propose a fix for?"
1799109,2018-10-31 10:28:18 UTC,Fixed by https://review.openstack.org/#/c/612684/2.
1799109,2018-11-01 03:47:32 UTC,"Mark, Thank you for fixing the issue.
Pinning ofr openstacksdk<0.18 would be enough for my environments."
1799112,2019-06-05 08:43:37 UTC,"(sorry, commented on the wrong bug)"
1799113,2018-12-19 20:48:16 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1799113,2018-10-24 17:37:08 UTC,"Reviewed:  https://review.openstack.org/612561
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad3ed220e53dd7ad1ec7513193004191da99f8df
Submitter: Zuul
Branch:    stable/rocky"
1799113,2018-10-24 20:25:24 UTC,"Reviewed:  https://review.openstack.org/612562
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f3610bc755b3e56f0a6dfb63aaf8a7ffd1d4602
Submitter: Zuul
Branch:    stable/queens"
1799113,2018-10-24 04:00:57 UTC,"Reviewed:  https://review.openstack.org/612231
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=10d64b2c62c54f243e6fb05bc9c7b027d433aae1
Submitter: Zuul
Branch:    master"
1799113,2018-11-06 06:01:01 UTC,This issue was fixed in the openstack/nova 18.0.3 release.
1799113,2018-10-23 04:03:02 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/612561"
1799113,2018-10-22 04:18:25 UTC,This patch needs to be backported to queens
1799113,2018-10-22 04:17:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612231"
1799113,2019-03-22 03:46:34 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1799113,2018-10-23 04:03:52 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/612562"
1799121,2018-10-23 00:49:32 UTC,"Yes, it is. Thank you for the response!"
1799121,2018-10-22 08:42:55 UTC,Is this your issue?
1799124,2018-10-23 00:20:12 UTC,I will try and confirm this failure not using containers as it's probably not required.
1799127,2018-10-22 07:57:39 UTC,"actually, there are other issue with the CRD exampe, should be:
apiVersion: ""k8s.cni.cncf.io/v1""
kind: NetworkAttachmentDefinition
metadata:
  name: a-bridge-network
  annotations:
    openstack.org/kuryr-config: '{
      ""subnetId"": ""id_of_neutron_subnet_created_previously""
    }'
spec:
  config: '{}'"
1799132,2018-10-22 06:35:06 UTC,Review: https://review.openstack.org/#/c/612253/
1799132,2018-10-22 15:25:04 UTC,I wonder if this is limited to python 3.
1799132,2019-11-07 04:35:31 UTC,"In general, the error means that you attempted to index an object that doesn't have that functionality. You are trying to subscript an object which you think is a list or dict, but actually is None. NoneType is the type of the None object which represents a lack of value, for example, a function that does not explicitly return a value will return None. 'NoneType' object is not subscriptable is the one thrown by python when you use the square bracket notation object[key] where an object doesn't define the __getitem__ method . e.g.: http://net-informations.com/python/err/nonetype.htm"
1799132,2019-12-18 14:55:47 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/612253
Reason: This has had open comments for some time now and the fix doesn't seem correct. I'm going to abandon this in case someone else wants to take a stab at resolving this."
1799132,2020-06-24 12:17:36 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/612253
Reason: We're going to tackle this via https://review.opendev.org/#/c/736406/4 so I think this is safe to remvoe"
1799132,2020-07-02 19:27:04 UTC,"Ubuntu 19.04 reached end of life on January 23, 2020.  I am therefore marking this bug 'wontfix' for that release."
1799147,2018-10-22 08:36:03 UTC,"Shortly after replying, I saw this in the logs, so I thought I'd mention it in case it was a permissions issue, with ""<REDACTED>"" in place of any confidential information:"
1799147,2018-10-22 08:24:57 UTC,It does appear that this is the issue - missing container and object ring files.
1799149,2018-10-22 07:27:50 UTC,Suggestion patch attached.
1799149,2018-10-22 07:26:31 UTC,"Full backtrace with ""thread apply all bt full"""
1799152,2020-01-13 02:29:47 UTC,"I was refering to [1], when I said nova returns JobInfo(type=libvirt.VIR_DOMAIN_JOB_COMPLETED). The
key point I want to say is that in our case, we meet VIR_ERR_OPERATION_INVALID error when trying to
get job stats by self._domain.jobStats(). In [1], nova already returns JobInfo(type=libvirt.VIR_DOMAIN_JOB_COMPLETED), so post live migration is executing later."
1799152,2018-10-22 07:51:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612272"
1799152,2018-10-24 22:35:31 UTC,"This bug looks valid, marking as High as it involves data loss."
1799152,2020-01-06 14:41:29 UTC,i dont think i agree that we should retry as if the vm has been killed its unlikely that we woudl be able to recover.
1799152,2020-01-07 03:14:19 UTC,"In our case, we didn't permit post copy live migration, a pre copy migration was executing, and during migration process, vm, aka qemu process on the *source node* was killed due to host OOM. The domain status is SHUTOFF, then in get_job_info(), self._domain.jobStats() got a libvirt error 'VIR_ERR_OPERATION_INVALID'. In previous code, nova thinks the domain is shutdown or gone away, so it happily return JobInfo(type=libvirt.VIR_DOMAIN_JOB_COMPLETED), but it will eventually trigger post_live_migration() to delete source vm files. That's why I report this bug."
1799152,2020-01-08 18:27:47 UTC,"i think this is actully another example of https://bugs.launchpad.net/nova/+bug/1788014
in that we had a general problem where we tread all event as success."
1799153,2019-03-08 04:20:20 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1799153,2018-10-23 01:54:54 UTC,https://review.openstack.org/#/c/612283
1799154,2018-10-22 07:49:26 UTC,It somehow feels like maybe indeed there can be some cases that there is no fault info on ERROR?
1799157,2020-05-15 23:51:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799157,2020-05-18 07:16:01 UTC,"Thank you for your bug report, you might have better success enabling the nvidia drivers from software-properties-gtk"
1799159,2018-10-22 12:17:38 UTC,Can you give more contex to this?
1799159,2018-10-22 12:30:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612375"
1799159,2018-10-22 12:37:17 UTC,"As this bp https://blueprints.launchpad.net/cinder/+spec/summarymessage is completed, and we can add corresponding error logs so that users/admins can check what the problem is."
1799159,2018-10-29 05:21:21 UTC,"Reviewed:  https://review.openstack.org/612375
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=67b2159f2fa9299359ef5d409309390cf184595a
Submitter: Zuul
Branch:    master"
1799159,2018-11-05 02:57:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615466"
1799159,2018-11-05 06:52:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615480"
1799161,2018-10-22 16:29:27 UTC,"Hi Valdimir,"
1799161,2018-11-19 23:42:18 UTC,"Vladimir,"
1799161,2018-10-22 20:23:49 UTC,"Reproducer: https://pastebin.canonical.com/p/YVdYQr3tDg/ (after this command set execution node is not able to deploy; error like in bug description is shown; also ""maas %user% bcaches read %node_id% throws the same exception)"
1799161,2018-10-22 20:06:54 UTC,"No, we don't."
1799161,2018-10-22 19:46:59 UTC,"Vladimir,"
1799161,2018-10-22 13:21:52 UTC,Changed to field-high again since to this issue may become a blocker on customer env.
1799161,2018-10-22 17:13:21 UTC,"Hi Andres,"
1799161,2018-10-22 08:40:27 UTC,+ ~field-medium team subscription
1799161,2018-10-22 17:19:11 UTC,"Tried to put machine to ""Deploying"" state via GUI and tried ""get-curtin-config"" again, it failed with ""list index out of range"": https://pastebin.canonical.com/p/4PqJtthWnZ/"
1799167,2018-11-06 20:18:20 UTC,s/nova-novncproxy/nova-serialproxy/ ^^
1799167,2018-11-06 20:12:46 UTC,"Hi Mike,"
1799167,2018-11-06 20:17:15 UTC,Actually both nova-novncproxy and nova-spiceproxy are in universe due to [1]. We should be able to add python-websockify to the nova-novncproxy dependencies for now. Once we get the security issues fixed we can get it promoted to main where it will get security support.
1799173,2018-10-22 08:59:17 UTC,"This package is 7 years old, latest one is v18.10"
1799173,2018-10-22 08:57:10 UTC,RedHat Bugzilla entry https://bugzilla.redhat.com/show_bug.cgi?id=1580105
1799174,2018-10-26 19:30:39 UTC,not a bug.
1799174,2018-10-26 18:29:07 UTC,"what's wrong?
how it should work?
how I can reproduce?"
1799174,2018-10-26 19:31:24 UTC,there are no actual result (wrong behavior) and expected behavior
1799174,2018-10-26 11:34:02 UTC,"Openstack heat was used, so contrail specfic heat test cases not applicable."
1799174,2018-10-22 19:11:41 UTC,please add more information.
1799174,2018-10-26 11:22:19 UTC,Adding more info:
1799180,2018-10-22 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799180,2018-10-22 12:49:51 UTC,apport information
1799180,2018-10-22 15:33:34 UTC,Feel free to close this if it makes sense. I am researching how best to report this upstream. The documentation on reporting kernel bugs makes it clear you need to identify the affected subsystem or your bug will be bit-bucketed. More hard core log diving is called for :)
1799180,2018-10-27 21:15:50 UTC,I'll bet dollars for donuts this is the nouveau driver. I see a bunch of lines like this as the system slows to a crawl (Also there's a juddering/tearing band in the center of the screen)
1799180,2018-10-27 21:17:24 UTC,Also marked this for re-triage since I have some usable evidence and a smoking gun.
1799180,2018-10-27 21:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799180,2018-10-27 21:31:57 UTC,Also attaching nouveau driver info a-la modinfo.
1799180,2018-10-27 21:44:41 UTC,apport information
1799180,2018-10-31 22:45:46 UTC,"Interestingly, this ONLY happens with Gnome."
1799180,2020-02-11 16:12:41 UTC,This is fixed across all environments in Ubuntu 20.04
1799185,2019-11-07 13:50:02 UTC,This is the debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454595
1799185,2019-05-07 17:40:00 UTC,"No activity upstream yet, in the bug or in the svn repo."
1799185,2018-10-23 14:51:46 UTC,"This is confirmed for cosmic, btw, and the upcoming DD one too."
1799185,2018-10-22 09:50:38 UTC,"Hi,
I'm installin our new relay and as before I'm running spamd with --virtual-config-dir option enabled:
""spamd -d --pidfile=/var/run/spamd.pid -c -x --virtual-config-dir=/var/lib/spamassassin/vconfig/%u/ --allow-tell -u debian-spamd -g debian-spamd --max-children=5 --min-children=3 --max-spare=3"""
1799185,2018-10-23 14:51:09 UTC,Confirmed.
1799195,2018-10-22 10:33:54 UTC,"Review in progress for https://review.opencontrail.org/46909
Submitter: Bartosz Pankowski (<email address hidden>)"
1799195,2018-10-26 11:05:56 UTC,"Reviewed:  https://review.opencontrail.org/46909
Committed: http://github.com/Juniper/contrail-infra/commit/d7fadaec6e83c573d4877f2b94a3a8f723a7fc1c
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    production"
1799201,2018-10-22 12:24:09 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1799201,2018-10-22 13:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799201,2018-10-22 15:06:13 UTC,"I've moved to ubuntu 1810 in the meantime, can't file a bug from the system anymore"
1799204,2019-12-10 10:47:22 UTC,Bug #1799217 has been solved and this one as well
1799204,2018-10-22 13:52:06 UTC,resolving bug #1799217 would resolve that issue as well
1799204,2018-11-24 05:45:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799212,2020-04-07 22:55:45 UTC,Thank you zdohnal.
1799212,2020-04-07 09:32:58 UTC,I added keyserver.ubuntu.com into list of keyservers.
1799212,2018-11-14 14:31:38 UTC,"Actually, I tried to connect to pgp.mit.edu with gpg three times in the last two weeks, all without success. I think the issue is more urgent than expected - it blocks users for installing plugin."
1799212,2020-04-07 06:08:31 UTC,The following patch updates previous - now it uses list of keyservers and the script is able to try the next keyserver if previous key download failed.
1799213,2020-02-09 16:20:22 UTC,Posts twice about every 10 seconds.
1799213,2019-06-03 16:13:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799213,2019-05-06 04:15:59 UTC,As per https://wiki.ubuntu.com/DebuggingProgramCrash  I added the ddebs repositories
1799213,2019-05-03 07:57:08 UTC,"> quits on the first warning, no crash, no dump:
"
1799213,2019-05-03 02:55:05 UTC,"I've upgraded to 19.04 since, with network-manager-gnome 1.8.20-1ubuntu1 .  It bleats some error messages to stderr on startup, but not a constant stream like before:"
1799213,2019-05-03 03:00:48 UTC,"My mistake, stderr *is* getting a constant repeat of these error messages in version 1.8.20-1ubuntu1 , I didn't wait long enough.  The same six warning messages, every 60-120 seconds."
1799213,2019-05-02 18:04:24 UTC,"Since it’s not a crash, it’d be difficult to get traces. The issue is in the patch Ubuntu ships for the indicator menu; the warnings don’t appear when the indicator menu is not used."
1799213,2018-12-22 04:17:50 UTC,[Expired for network-manager-applet (Ubuntu) because there has been no activity for 60 days.]
1799213,2018-10-23 02:59:58 UTC,"The wiki page says to look in /var/crash but there's no files there.  it says to install the ""$name-dbg"" package, but there is no ""network-manager-gnome-dbg"" package."
1799213,2018-10-22 13:46:05 UTC,"The report is from XFCE, would be useful to get a gdb backtrace from the warning if you could (https://wiki.ubuntu.com/DebuggingProgramCrash)"
1799213,2019-05-02 21:56:44 UTC,You can get a backtrace of warnings either by using --g-fatal-warnings (but then it only works until the first warning since it exits) or by setting a break on g_log in gdb
1799215,2019-11-29 14:00:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799221,2019-01-29 01:44:39 UTC,This issue was fixed in the openstack/cinder 12.0.5 release.
1799221,2019-01-15 20:09:01 UTC,"I had this as affecting ""ossn"", but am thinking that was incorrect.  Anyway, this defect was introduced in Pike. See comment #2 for security implications. Not sure if this is worth a note or not."
1799221,2019-01-24 00:15:28 UTC,"Reviewed:  https://review.openstack.org/629463
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=937af5be0e7c17b34860e25cc434a219d7143387
Submitter: Zuul
Branch:    stable/queens"
1799221,2019-01-24 15:18:57 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/633015"
1799221,2019-02-06 21:59:09 UTC,This issue was fixed in the openstack/cinder 13.0.3 release.
1799221,2019-01-11 17:35:56 UTC,"Brian,"
1799221,2019-02-28 14:30:47 UTC,This issue was fixed in the openstack/cinder 11.2.0 release.
1799221,2019-03-21 17:21:51 UTC,This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.
1799221,2020-07-02 15:34:31 UTC,"I don't think this needs an OSSA.  It's kind of old, plus the outcome was a corrupt download, not a leakage of content or anything like that."
1799221,2021-01-21 16:35:51 UTC,"Per Brian's comment #23 this sounds like a security hardening opportunity, not an exploitable vulnerability."
1799221,2019-02-08 18:49:35 UTC,"Reviewed:  https://review.openstack.org/633015
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0551f0a9ff7b787fcb3e1b686b83e25f99cad874
Submitter: Zuul
Branch:    stable/pike"
1799221,2019-01-10 16:21:47 UTC,"I should add that even though there are 4 patches, we're talking a very few lines of code (it's just that a surprising number of bugs have been packed into a very small space)."
1799221,2018-12-14 05:40:26 UTC,"Reviewed:  https://review.openstack.org/625135
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=80fdc0a71b55659d92efdda826807d60d8bd4ab9
Submitter: Zuul
Branch:    master"
1799221,2019-01-09 12:38:40 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/629463"
1799221,2018-10-23 07:43:36 UTC,Fix proposed in https://review.openstack.org/#/c/612393/
1799221,2018-12-13 23:11:11 UTC,"This also causes checksum/hash verification failures to get missed, as glanceclient throws a IOError with EPIPE in that case, so you can get a volume with corrupted image content and not know it...."
1799221,2019-01-10 04:50:13 UTC,The backport to Queens is complicated by the fact that the exception used in this fix doesn't exist in Queens.
1799221,2018-12-14 05:49:42 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/625148"
1799221,2018-12-14 00:58:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625135"
1799221,2019-01-08 02:47:17 UTC,"Reviewed:  https://review.openstack.org/612393
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=864c074ff15db601c896dadc2842ae703861c0dd
Submitter: Zuul
Branch:    master"
1799221,2019-01-08 05:31:17 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/629091"
1799221,2019-01-08 14:18:48 UTC,Note to security team: this defect was introduced in Pike.  See comment #2 for security implications.  Not sure if this is worth a note or not.
1799221,2019-01-09 02:55:54 UTC,"Reviewed:  https://review.openstack.org/629091
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=bf89f76fb1b7a52299c17467106018eae01608e8
Submitter: Zuul
Branch:    stable/rocky"
1799221,2018-12-18 21:04:13 UTC,"Reviewed:  https://review.openstack.org/625148
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9c696ce29f63275ec229a943a9b9bcf63f688f0c
Submitter: Zuul
Branch:    stable/rocky"
1799227,2018-10-22 16:22:01 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1799228,2018-10-24 06:05:05 UTC,Thank you for the swift response.
1799228,2018-10-23 02:30:07 UTC,This change was made by a bot.
1799228,2018-10-23 19:05:03 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1799228,2018-10-31 14:10:09 UTC,"Dear Joseph,"
1799229,2019-05-03 18:18:54 UTC,"I'm having this same issue.
Just started out of no where, last week it worked perfectly. This week I'm getting this error.
Uninstalled win32diskimager from my PC. Rebooted, regcleaned/etc...
I can open the program. I select the source and the destinations. Give a file name and click Read. I then get this message."
1799229,2019-12-19 14:54:56 UTC,I can confirm this issue. I'm not able to create a backup of my SD card.
1799235,2018-10-26 05:28:29 UTC,"On your system, this is in kernel message:
[ 0.104005] ACPI: GPE 0x6F active on init"
1799235,2018-10-22 14:53:53 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799235,2018-10-22 15:49:28 UTC,"The issue began after a fresh system install on a new computer.  Admittedly, the first system I installed was Qubes, with Fedora (24 I believe).  When I decided Qubes wasn't adequate for my needs, I wiped the system (reformatted using gparted) and installed the latest Ubuntu (as of a month ago).  The kworker process was out of control in both Fedora and Ubuntu."
1799235,2018-10-23 14:34:49 UTC,"I've now tested with 4.19-rc8.  The kworker process remains at about 65% continuously.  Not quite sure how to mark this as confirmed, but will try."
1799235,2018-10-23 14:38:10 UTC,I should add that I issued the following last night:
1799235,2018-10-23 16:12:19 UTC,"There's a BIOS update for this system, it might solve the issue."
1799235,2018-10-24 15:23:28 UTC,I've updated the BIOS for my system.  It did not solve the issue.
1799235,2018-10-24 18:04:10 UTC,Can you try v4.13? There's a new commit introduced in v4.14:
1799235,2018-10-25 16:14:01 UTC,Thanks Kai-Heng.
1799235,2018-10-29 22:14:52 UTC,"Hmm, I think the main bios change is that I have safe mode turned off (at least in part because of that unsigned module).  I'll see what I can do the next time I restart the system."
1799235,2018-10-31 15:13:50 UTC,"Hi again:  So, I tried both with restored default bios settings and default factory setting.  The kworker process is still going at over 85%.  I can turn it off w/ echo ""disable"" > /sys/firmware/acpi/interrupts/gpe6F in both cases."
1799235,2019-10-06 07:45:13 UTC,This is also found on a Cannon Lake Intel SDP with Xeon E-2176G running v5.4-rc1 kernel.
1799235,2019-11-19 20:32:12 UTC,"PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
20684 root       20   0     0     0     0 I 59.9  0.0  2:52.66 kworker/0:0-kacpi_notify"
1799235,2019-11-20 05:11:50 UTC,"Daniel, can you please attach output of `grep . /sys/class/dmi/id/*`?"
1799246,2018-12-13 19:24:14 UTC,"Reviewed:  https://review.openstack.org/617297
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=74ed2fe69f15d86252b1c7779c916cb93ffc252d
Submitter: Zuul
Branch:    stable/rocky"
1799246,2018-11-12 11:30:58 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/617297"
1799246,2018-12-19 10:01:31 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1799246,2018-11-09 01:54:02 UTC,"Reviewed:  https://review.openstack.org/610034
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=00d08a3288f61268f8a823991fadf0d83c36c04d
Submitter: Zuul
Branch:    master"
1799246,2019-03-22 03:46:12 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1799251,2018-12-04 17:08:35 UTC,"Hello Dimitri, or anyone else affected,"
1799251,2018-12-05 13:17:39 UTC,This bug was fixed in the package systemd - 239-7ubuntu15
1799251,2018-10-22 15:49:05 UTC,"Hmmmm... not sure if /run should be limited to 10%, or if runtime journald should be limited to 1%."
1799253,2018-10-28 09:38:45 UTC,when software boutique gets to 'stocking software boutique' it hangs and then goes blank. I'm on intel pentium 3ghz. No gpu as far as I am aware. welcome screen loads normally. Fresh install of ubuntu mate 18.04 32 bit
1799260,2018-10-22 20:06:15 UTC,What OR version are you using? Can you attach a logfile?
1799260,2018-10-22 21:40:34 UTC,"X4264, now the log file it’s not available"
1799260,2018-10-23 07:13:14 UTC,"I have tested with x.4273, and it works here. I'm sorry, but if you don't provide me further data about how the problem occured, I can't help you."
1799260,2018-10-23 16:27:26 UTC,It works here. Can you test with another trainset and/or another route?
1799261,2018-10-23 16:04:55 UTC,"Also, xmlsec with pip3 with npm installed not is possible install."
1799261,2018-10-29 14:09:42 UTC,"After to do any tests, the problem are this packages:"
1799262,2018-10-30 12:33:27 UTC,Could you give some details on your VPN config and on the DNS server you expect to be used?
1799262,2019-08-18 19:42:10 UTC,"This is affecting users of dappnode.io platform when connecting from Ubuntu.
The DNS server pushed by OpenVPN server is not being added to clients.
A temporary fix can be applied, see https://askubuntu.com/questions/1032476/ubuntu-18-04-no-dns-resolution-when-connected-to-openvpn, but it's not very convenient for users."
1799262,2018-10-31 11:51:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799262,2018-10-31 09:09:15 UTC,The vpn connection config created by network-manager-openvpn in attachment. I changed some values such as remote host name.
1799262,2018-10-29 10:10:49 UTC,"Thank you for your bug report. What's the output of ""systemd-resolve --status""?"
1799262,2018-10-30 08:33:06 UTC,The output of systemd-resolve in attachment.
1799262,2018-10-29 08:53:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799263,2020-06-15 04:17:17 UTC,[Expired for Telegraf Charm because there has been no activity for 60 days.]
1799263,2018-12-13 15:32:18 UTC,"This can also carry over to locking dpkg for other charms.  Suggest adding update-status hook routine to check for need to configure telegraf dpkg and force a ""no"" response."
1799263,2018-12-13 17:40:39 UTC,Workaround:
1799263,2020-03-10 07:01:51 UTC,How can this situation replicated using charms to handle the deployment?
1799265,2019-09-25 12:55:02 UTC,"Also, startlingly, I seem to have thousands of ipv6 addresses assigned to enp0s8:"
1799265,2019-11-23 09:39:13 UTC,I'm seeing exactly the same issue on Ubuntu 19.04
1799265,2018-10-29 14:56:48 UTC,"Ok, ignore previous post. My laptop was sitting unused and suddenly I hear the fans spin up (which they almost never do). Sure enough, the avahi-daemon was running up a full cpu core. I've attached the logs."
1799265,2019-09-25 12:37:59 UTC,"Hi, I'm hitting this quite consistently on Pop!_OS 19.04 in Virtualbox (Windows 10 host) on Lenovo T460."
1799265,2019-11-23 09:42:03 UTC,That's with avahi-daemon 0.7-4ubuntu5
1799265,2019-08-27 12:55:40 UTC,"Same problem with high CPU, but I'm not able to disable ipv6 (ipv6 network). avahi-daemon is almost always at first place by CPU usage."
1799265,2018-10-29 14:56:34 UTC,"Ok, ignore previous post. My laptop was sitting unused and suddenly I hear the fans spin up (which they almost never do). Sure enough, the avahi-daemon was running up a full cpu core. I've attached the logs."
1799265,2018-10-29 14:57:01 UTC,"Ok, ignore previous post. My laptop was sitting unused and suddenly I hear the fans spin up (which they almost never do). Sure enough, the avahi-daemon was running up a full cpu core. I've attached the logs."
1799265,2018-10-27 06:58:21 UTC,"Ok, the issue seems gone! I cannot recreate it, and I'm not sure why."
1799265,2018-10-23 04:04:35 UTC,"Hi Matt,"
1799265,2019-05-12 11:58:04 UTC,A similar bug happened here on 2 different Ubuntu installs once they upgraded to Ubuntu 18.10.
1799266,2019-05-07 09:29:22 UTC,"Now tracking the required fixes here:
https://gitlab.gnome.org/GNOME/mutter/issues/590"
1799266,2019-03-11 03:27:14 UTC,"I think it's too early for this to be a release bug. A bunch of fixes are still awaiting upstream review, some require more upstream work by me, and the final one needs to be rewritten completely after so re-profiling. Lots of upstream work to do before considering this for distro."
1799266,2018-11-14 04:32:06 UTC,"The GJS fix is now in 19.04 here:
https://launchpad.net/ubuntu/+source/gjs/1.54.2-1"
1799266,2019-03-06 09:06:06 UTC,The gjs tasks are effectively tracked via bug 1803271.
1799266,2018-10-23 02:17:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799266,2018-10-23 02:17:47 UTC,Thanks for the bug report.
1799266,2018-10-23 09:07:46 UTC,"Thank you! After reading through the reference bugs, it seems like you have a bit of a handful here."
1799272,2019-05-24 17:08:00 UTC,"(I can see arguments either way: if the expiration time has passed, it is has passed; or, if the patron manages to beat the library staff to picking up the item from the holds shelf, it's still fair play.)"
1799272,2019-09-06 21:56:40 UTC,"Pushed to master for inclusion in 3.4. Thanks, Jason!"
1799272,2018-10-22 19:26:43 UTC,Pushed a fix branch to user/dyrcona/lp1799272-limit-sip2-hold-items-to-available in the working repository.
1799272,2018-10-22 20:32:07 UTC,"This comment is mostly for the benefit of Jeff Godin, who asked in IRC."
1799272,2018-11-02 13:43:59 UTC,I have pushed a better branch for this bug. It makes the change in behavior optional by adding an implementation option for the oils_sip.xml file: msg64_hold_items_available. I have also added release notes to this branch:
1799272,2019-05-14 14:48:16 UTC,"CW MARS has been using the branch mentioned in Comment #3 since we upgraded to Evergreen 3.2.4 on April 14, 2019.  The site that we implemented this feature for is happy with the change, and the other sites that don't use the setting don't know it's even there."
1799272,2019-05-24 17:06:30 UTC,"While reading the patch, a question occurred to me: would it be useful to also consider shelf_expire_time and not count a hold as available qua ""on the holds shelf"" if the shelf expiration time has passed?"
1799272,2019-07-01 17:35:30 UTC,"I can see arguments either way, and I prefer to leave the code unchanged.  I hesitate to add yet another option to handle hold shelf expire times."
1799273,2018-10-22 20:53:04 UTC,I found the issue - unrelated to the psycopg2 warning - rather the value of the notification_format as described here:  https://bugs.launchpad.net/ceilometer/+bug/1665449/comments/8
1799274,2020-03-11 03:39:44 UTC,"I know this has been a long time since the bug report, and details may no longer be available.  If this can be reproduced now, could you share a more full juju unit log from the Elastic unit, as well as any Elastic logs themselves and /var/syslog, and some details on the model itself?  We really need to understand the network spaces in use, as well as what's killing Elastic."
1799274,2020-06-15 04:17:19 UTC,[Expired for Elasticsearch Charm because there has been no activity for 60 days.]
1799279,2019-03-18 09:19:00 UTC,"Hello,"
1799279,2019-08-16 19:28:47 UTC,"@Radoslaw This bug is a duplicate of bug #1827697, and has been fixed in all releases."
1799279,2019-08-16 19:19:06 UTC,"This affects me as well.
Cannot install display link drivers because of that issue."
1799279,2019-05-18 16:38:52 UTC,This is being tracked in bug #1827697
1799279,2019-05-18 08:40:09 UTC,Still present in 19.04 (kubuntu in my case).
1799279,2018-12-20 15:35:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799279,2019-03-05 20:52:43 UTC,"I've had the very same issue for the first time with Kubuntu 16.04 LTS (that's not a typo, the issue is with both versions)."
1799279,2018-10-22 19:29:32 UTC,"Note that I got out of this by killing the update-secureboot-policy and whiptail processes, and I did not get an error message from dpkg or dkms after doing that, so the fact that the update-secureboot-policy and whiptail commands exited with non-zero statuses was not detected."
1799279,2018-10-22 19:23:53 UTC,"Sorry, I misspoke above. I'm on 18.04, not 18.10. I've updated the comment above to indicate this."
1799279,2019-03-05 20:54:04 UTC,"Sorry, that's Roger Wolff, with two f."
1799298,2020-11-07 11:14:20 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/761811"
1799298,2020-11-07 11:15:29 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/761812"
1799298,2020-11-07 11:16:16 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/761813"
1799298,2020-10-21 03:26:57 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/758928"
1799298,2021-02-03 01:50:22 UTC,https://review.opendev.org/c/openstack/nova/+/761809 has merged to stable/victoria
1799298,2021-02-04 11:22:19 UTC,This issue was fixed in the openstack/nova 22.1.0 release.
1799298,2020-11-07 11:13:19 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/761810"
1799298,2020-11-07 11:17:40 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/761814"
1799298,2020-11-07 11:11:39 UTC,"Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/761809"
1799298,2020-10-14 22:35:20 UTC,"Hi, a Red Hat customer is now seeing this issue with DoS as result. Reproduce by:
1.add 128 properties to an image
2.add 128 metadata
3.Max out the user_data"
1799298,2020-11-05 08:22:34 UTC,"Reviewed:  https://review.opendev.org/758928
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e728fe668a6de886455f2dbaf655c8a151462c8c
Submitter: Zuul
Branch:    master"
1799298,2020-10-15 13:30:36 UTC,"I'm inclined to classify this as a security hardening opportunity, since there are likely countless ways a server instance can hammer the metadata API and connecting networks, and the offending system can be readily identified and disabled by operators. The security impact also obviously only impacts environments which expose the metadata service, so is not a risk for those providing only configdrive."
1799298,2020-10-15 00:23:05 UTC,I have changed the information type on this bug to Public Security so it will show up on the Vulnerability Management Team's radar.
1799298,2018-12-17 23:09:17 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/624778
Reason: The join in security_groups should be trivial since the table should be empty in neutron cases, and when getting base metadata we also return the password which is stored in instance.system_metadata, so pre-joining instance_system_metadata is actually something we should be doing when we pull the instance from the cell database - it's used more than just vendordata v2 requests, which makes this change essentially not worthwhile."
1799298,2018-12-12 18:18:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624778"
1799298,2018-12-12 17:57:17 UTC,I think we can make a couple of simple enhancements by:
1799298,2020-11-05 18:24:16 UTC,"As there have been no objections to my proposal to treat this as security hardening, I'm switching our advisory task to won't fix status indicating we won't publish any formal security advisory about it. This decision can of course be reversed if people feel differently about the relative severity and practicality of exploits for it."
1799301,2019-10-22 22:04:23 UTC,"Switching to a different way to detect the distro as was done with https://github.com/cloud-init/cloud-init/commit/0948cdfbef2052cdf839f24d6a17d457aa9fd4d3#diff-b3309b48873bd17b3fc8f29bd84c50fa is part of the solution. However, for SUSE there is also lp#1849378 that needs addressing."
1799301,2018-11-01 11:25:57 UTC,Fedora 29 is presenting the same problem today with last release.
1799301,2019-07-18 22:15:36 UTC,Thanks for filing the issue.
1799301,2019-08-16 12:57:23 UTC,I would like to stress that this is still blocking the latest Fedora Rawhide (Fedora-Cloud-Rawhide-x86_64-20190812.n.0) as well as other cloud-init distros like Fedora-Cloud-30-1.2 or openSUSE-MicroOS.x86_64-16.0.0-Kubic.
1799301,2019-08-16 14:42:08 UTC,"@yct,"
1799301,2019-10-16 04:17:21 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1799305,2018-11-06 23:21:57 UTC,"Yes, looks like it and editing /etc/gdm3/custom.conf to set ""WaylandEnable=false"" fixed the issue for me too.  Thanks!"
1799305,2018-11-06 15:34:42 UTC,Possibly duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790
1799305,2019-02-16 08:42:59 UTC,I tried a few versions a few times but I can only use nouveau driver
1799305,2018-10-23 08:23:08 UTC,The issue persists after installing nvidia-410 from the “Graphics Drivers” team PPA.
1799305,2019-02-16 08:41:54 UTC,NVIDIA drivers don't work for me on 18.04 at all.
1799305,2018-10-26 09:26:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799307,2019-01-18 10:56:54 UTC,"Hi, I have problems with navigation system too in Meizu Mx4. When I start unav it shows a wrong place, sometimes a town far away from mine. I can get in my destination, but unav tells me, that it's waiting for GPS-Signal. I fond out, that route will be finding, when I put unav in the background and put it then back in the focus. When I start my trip, unav does not follow for a few minutes, but suddenly it starts to work exactly. I think, that this is not a error of unav, but the GPS-System of the smartphone, because also OSMScout and GoogleMaps do not find the position. Thank you in advance for your help."
1799307,2019-03-03 10:42:11 UTC,"Hi,
I would say it's a hardware issue. Could you reboot it and leave it in a window 1 hour?
Best regards."
1799307,2018-10-23 18:34:36 UTC,"Hi, reboot and leave the phone 1 hour in a window. Is the GPS enabled? And
tell me if it gets a position.
Best regards."
1799309,2020-05-19 10:45:58 UTC,I believe that the fix for bug [1] in oslo is fixing you problem.
1799309,2019-08-08 10:28:34 UTC,"In the IRC discussion linked in comment #5 the [1] weird piece of code was mentioned, which point to [2]. So I dig that code a bit to see why we really need that and come up with some answers see [3] and [2]. I'm not sure if this helps this bug so I left his here as a FYI."
1799309,2020-05-31 03:26:40 UTC,"Change abandoned by norman shen (<email address hidden>) on branch: master
Review: https://review.opendev.org/732003"
1799309,2018-10-24 19:36:21 UTC,Can you attach the nova-api logs? Kind of need a stacktrace to see where the ValueError is coming from.
1799309,2018-11-05 23:04:02 UTC,"Just a quick note that I tested the script with delays and looped it.  I ran it 576 times before stopping it - all successful ""cold"" migrations, whereas a cold migrate while the VM is powered on will create the error described above, which I have yet to find a way to recover from."
1799309,2019-08-06 01:59:11 UTC,"We are seeing the same issue in Rocky and talked to mriedem about it on IRC.
http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2019-08-02.log.html#t2019-08-02T18:37:47"
1799309,2018-10-26 08:47:59 UTC,Sorry for the delay - the nova-api log Traceback (as requested in a DM) is below.
1799309,2018-11-05 12:53:37 UTC,Please let me know if you need anything else to diagnose this issue.
1799318,2018-10-22 23:07:49 UTC,an incompatibility*
1799318,2019-02-15 19:19:02 UTC,I'm going to re-set this issue so that we don't lose track of the full fix.
1799318,2018-11-08 11:25:21 UTC,"@Alexis, your thoughts here would be great if you have a moment...."
1799318,2018-11-08 11:24:58 UTC,"> Funny, that's what I was thinking about your suggestion!
"
1799318,2018-11-08 01:12:32 UTC,">Trouble is its discoverability is pretty poor.
"
1799318,2018-11-08 00:20:12 UTC,"To be honest, it never occurred to me to put them in the schematic.  Doing so has other advantages, such as being specific to a pair of nets.  Trouble is its discoverability is pretty poor."
1799318,2018-11-07 23:40:16 UTC,Hmm... Maybe (can't check right now) but that's because I have it in the schematic.
1799318,2018-11-07 23:15:51 UTC,"@Seth, I think the difference is that your net-tie pad is already assigned the correct net.  Set it to no net (as if it just came from the library), and I think you'll find that it doesn't work."
1799318,2018-11-07 21:50:48 UTC,Hmm... I don't have any issues with the official library net ties and just #4.  Either in routing or DRC. (video attached)
1799318,2018-10-23 19:55:22 UTC,"Fixed in revision a96dbde7389a8f4d409aee38d42666a5821efc9a
https://git.launchpad.net/kicad/patch/?id=a96dbde7389a8f4d409aee38d42666a5821efc9a"
1799318,2018-11-07 20:41:51 UTC,@Jeff-
1799318,2018-11-07 21:18:15 UTC,"@Seth, the #4 commit only works when the pad is at least {clearance} larger than the connecting copper shape.  If it's not then the router won't let you route to the pads and DRC will complain."
1799318,2018-11-07 16:58:27 UTC,"@Jeff, I meant to comment on this sooner but it just got lost in the noise.  Your solution is a bit fragile.  I'm assuming you based your decision to search for ""net ties"" in the footprint description because all of the footprints in the KiCad NetTie library have ""net tie"" in the description.  The problem is this behavior will not work for users who have made their own net tie footprints and failed to add ""net tie"" to the description.  Even worse would be the case were ""net tie"" was in the footprint description but the footprint wasn't actually a net tie.  Granted the risk is low but not zero.  If we cannot find a better way to handle this, we may have to live with it until v6 when we can update the footprint file format to support net ties."
1799318,2018-11-07 16:31:12 UTC,Hi Jeff-
1799318,2018-11-07 14:24:41 UTC,"Fixed in revision 34395515437118f4eff0f04792aa04316f9232cf
https://git.launchpad.net/kicad/patch/?id=34395515437118f4eff0f04792aa04316f9232cf"
1799318,2018-11-03 17:34:22 UTC,"@Tom, I've attached a very simple fix which handles both DRC and PNS.  It isolates the workaround (net-tie footprints must contain ""net tie"" at the start of their keywords) to a single line.  Let me know what you think."
1799318,2018-10-24 15:55:11 UTC,"I take it back.  A bit more examining, José's net tie uses a segment instead of a polygon.  The polygon works fine.  The library netties also use polygons"
1799318,2018-10-24 15:45:53 UTC,I think this is the common case as this is what is included in the libraries.
1799318,2018-10-22 23:06:34 UTC,Version information
1799318,2018-10-23 23:28:49 UTC,"Yeah, this fix will only work if your net-tie pads are at least {clearance} larger than your connecting copper.  Since your pads are the same size as the width of your copper, it fails."
1799318,2018-10-23 23:08:14 UTC,"Gentlemen, let's discuss this before making any fixes. I would like to see what options we have before the P&S code becomes aware of any workarounds like the net ties one."
1799318,2018-10-23 22:36:52 UTC,Unfortunately this fix alone did not do it for my net ties. I have attached a minimal fragment that shows the issue. If you try routing towards the net tie in the PNS it will not let you reach it. If you try routing from the net tie you get a nag dialog saying you cant start from a keepout.
1799318,2018-11-07 20:21:13 UTC,"I completely agree with the comments.  However, we need some sort of work-around until we can change the file format."
1799318,2018-10-22 23:07:19 UTC,As this looks like a regressions stability wise for 5.1 I will mark the milsetone for it as well.
1799326,2020-03-27 08:36:13 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1799330,2018-10-23 16:32:03 UTC,"This is a larger request than might be first apparent.  We draw the zones with the line width first and then fill.  Since we cannot make a section smaller than the line width, we can't make spoke smaller than the line width (they wouldn't be drawn)."
1799330,2018-10-23 18:49:38 UTC,Actually we need to change it to what Seth says.  Right now (believe it or not) we draw thermal reliefs by knocking out the 4 pie-slices *around* the spokes.  This is why we can't handle spokes on custom pad shapes.
1799330,2019-08-15 16:44:28 UTC,Minimum zone width and minimum track width are not the same thing.  Minimum zone width is as much about peeling copper as it is about current-generated-heat.
1799332,2018-10-24 21:37:57 UTC,"I believe that this should be reopened, since the issue remains for the following reasons:"
1799332,2018-10-24 17:59:22 UTC,"It is recommended keystone NOT be deployed on non-http/https (80/443) ports. If you would like to use a Vhost on a different port it is up to the deployer/installation tools to make that decision. The provided wsgi file is intended to be opinionated on the best way to deploy keystone, port 80/443 (standard ports) under the identity-prefix."
1799332,2018-10-25 13:41:02 UTC,"This is valid IMO. It's hard to fix for exactly the reason you describe, we have to update all our documentation to stop referring to the port as well as every other projects' docs and also make sure the operator is aware of how to set it up without interfering with horizon. So far we've been sticking to referring to the port because there are fewer prerequisites to explain. But the long-term answer is to update the install guide to set up /identity and correct all instances of :5000 in ours and other projects' docs."
1799337,2018-10-24 18:06:52 UTC,Note: the redhat spec file needs the same change.
1799337,2018-10-24 19:51:02 UTC,"That may be, but I didn't test that distro and have no plans to do so. In the real world, any RHEL customer uses the RHEL back-patched version of 18.2 that they support; that version either never took 6ee8a2 and thus doesn't need this change, or did take that commit but had a similar patch applied there."
1799337,2018-10-29 20:46:49 UTC,"I appreciate the candor. Unfortunately, the real world also includes people like me who are not a RHEL customer (we use CentOS) and also need to build cloud-init from upstream. :-) I had that single-line diff in my tree already and was going to make my own bug report, but found this one first, so I thought I'd piggy-back off of it."
1799339,2019-01-28 09:27:05 UTC,"Since the package failed verification, I am removing it from cosmic-proposed."
1799339,2019-05-16 15:07:17 UTC,The new version with the change landed in Ubuntu since
1799339,2018-11-26 13:03:04 UTC,"K, so the issue there was probably not the one pointed in the description/that commit. Likely not going to be fixed in cosmic then"
1799339,2018-11-03 00:53:00 UTC,Please flesh out this SRU test case so that it can be clearly followed by someone unfamiliar with xfce and redshift.
1799339,2018-11-20 22:20:36 UTC,"Hello Olek, or anyone else affected,"
1799339,2018-10-25 09:07:15 UTC,"Thank you for your bug report, that seems a candidate for a fix backport but could you describe with some extra details what version of Ubuntu you are using, what you are doing and what problem you hit? (you mentioned redshift, where do you use it and how?)"
1799339,2018-11-25 03:07:32 UTC,Hello Brian.
1799339,2018-10-25 17:00:24 UTC,"Sebastien, I'm on Xubuntu 18.10 and I'm using the redshift package through redshift-gtk. As described in the upstream bug, the problem occurs on login when redshift attempts to start automatically and fails due to the geoclue timeout."
1799339,2018-11-20 20:26:15 UTC,done
1799340,2019-04-16 01:29:40 UTC,The current BUG is similar to https://bugs.launchpad.net/nova/+bug/1815476
1799340,2019-06-18 07:00:04 UTC,I can reproduce what the reported described.
1799341,2019-01-17 15:26:38 UTC,Python 3 support is very much needed. Just about every openstack package has py3 support. Note that py2.7 is almost end of life: https://pythonclock.org/.
1799341,2019-01-30 19:15:43 UTC,Fyi I can't package this for ubuntu without python3 support. We've moved to python3 only for stein+.
1799341,2019-01-31 01:45:55 UTC,"@Corey we will make this high priority
https://releases.openstack.org/stein/schedule.html is community schedule
what's your deadline to have this onboard? Thanks"
1799342,2018-10-23 06:49:33 UTC,It is the same thing if i close the window.
1799345,2019-11-04 13:10:40 UTC,"The verification of the Stable Release Update for sylpheed has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1799345,2019-11-04 13:10:33 UTC,This bug was fixed in the package sylpheed - 3.5.1-1ubuntu3.19.04.1
1799345,2019-10-29 08:58:08 UTC,"ubuntu@lp1799345:~$ dpkg -l|grep sylpheed
ii  sylpheed                       3.5.1-1ubuntu3                     amd64        Light weight e-mail client with GTK+
ii  sylpheed-i18n                  3.5.1-1ubuntu3                     all          Locale data for Sylpheed (i18n support)"
1799345,2019-10-25 16:42:25 UTC,I've tested 3.5.1-1ubuntu3.18.04.1. This package fixes the bug.
1799345,2019-10-24 13:42:09 UTC,"Hello Moses, or anyone else affected,"
1799345,2019-10-24 13:41:10 UTC,"Hello Moses, or anyone else affected,"
1799345,2019-09-28 15:27:12 UTC,Need help with Regression Potential section. I have no idea about possible regressions.
1799345,2019-10-08 21:14:41 UTC,"thanks @vofka!  I uploaded to Eoan, Disco, and Bionic so it's waiting for approval now."
1799345,2019-09-25 16:37:02 UTC,Hello.
1799345,2019-11-04 14:23:01 UTC,This bug was fixed in the package sylpheed - 3.5.1-1ubuntu3.18.04.1
1799345,2019-09-25 14:37:59 UTC,"This was fixed in Debian a year ago with a patch from #2 and is already in stable (buster).
This is a debdiff for Bionic applicable to 3.5.1-1ubuntu4. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended."
1799345,2019-06-16 13:23:33 UTC,"I'm on Lubuntu 18.04.2, and I'm having the same problem with Sylpheed and Gmail."
1799345,2018-11-02 06:43:26 UTC,"There is an upstream bug report with a patch, though it's not released yet:
https://sylpheed.sraoss.jp/redmine/issues/306"
1799345,2019-10-08 21:56:43 UTC,This bug was fixed in the package sylpheed - 3.5.1-1ubuntu5
1799345,2019-09-25 16:28:17 UTC,"The attachment ""1-3.5.1-1ubuntu5.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1799346,2018-12-11 00:21:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799358,2019-09-12 17:22:17 UTC,"Reviewed:  https://review.opendev.org/612617
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=f28c59df2b9be75a1b81133b0d9803078de87fe6
Submitter: Zuul
Branch:    master"
1799358,2019-09-19 10:10:48 UTC,This issue was fixed in the openstack/neutron-fwaas 15.0.0.0b1 development milestone.
1799358,2018-10-23 07:39:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/612617"
1799360,2018-10-24 19:52:17 UTC,I have a feeling that this could be more than just connection load. Is it possible to gather a few heap reports for a loaded controller over a few hours?
1799360,2018-10-25 21:04:19 UTC,@thumper here are the reports.
1799360,2018-10-26 08:21:19 UTC,"This bug is specifically about putting defenses in place so that whole classes of bugs and attacks don't take down the controllers, rather than diagnosing a particular trigger."
1799360,2018-10-26 15:52:44 UTC,"@stub I agree, and we are putting things into place, but I'm also just checking that we aren't leaking."
1799364,2019-07-05 08:21:58 UTC,The fix of LP: #1740894 can fix this issue.
1799364,2019-07-05 07:45:20 UTC,Cosmic has fixed this issue.
1799364,2019-04-20 18:10:40 UTC,"Unsubscribing sponsors, as there seems to be disagreement with respect to the patch's relevance."
1799364,2018-12-21 09:45:52 UTC,not seeing this at all on a dell m3800 precision running 4.18.0-13-generic
1799364,2018-12-06 07:06:49 UTC,"Sorry, I mean disco works fine without this problem.
Please ignore comment #12."
1799364,2018-12-06 07:05:51 UTC,cosmic works fine without this problem.
1799364,2018-12-06 06:13:45 UTC,"I have verified systemd/239-7ubuntu10.5 but it doesn't fix this problem alone.
It also needs to install xkb-data/2.23.1-1ubuntu1.18.10.1 to fix the problem."
1799364,2018-11-22 21:33:44 UTC,"the patch created issues (see the comments on bug #1740894 and https://github.com/systemd/systemd/issues/10704) and was reverted upstream in https://github.com/systemd/systemd/pull/10709 , please don't backport that change to older series but rather the revert/more recent upstream changes"
1799364,2018-12-01 02:54:06 UTC,This bug was fixed in the package systemd - 239-7ubuntu14
1799364,2018-11-22 22:14:07 UTC,@seb128
1799364,2018-11-22 17:22:41 UTC,In disco-proposed
1799364,2018-10-23 12:23:12 UTC,"The attachment ""0001-d-p-hwdb-Fix-wlan-keycode-for-all-Dell-Latitude-and-.patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1799364,2018-10-23 09:34:37 UTC,The patch has accepted by the upstream at https://github.com/systemd/systemd/commit/9e2629919f0cd4d48d179fa5ae5e46c3267c1cdc.
1799364,2018-10-23 09:29:12 UTC,The patch for https://code.launchpad.net/~ubuntu-core-dev/+git/systemd/+ref/ubuntu-cosmic
1799364,2018-10-23 07:44:00 UTC,Ubuntu 18.04 has the same problem.
1799364,2018-12-04 17:08:51 UTC,"Hello Shih-Yuan, or anyone else affected,"
1799365,2019-10-31 03:37:08 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1799365,2019-01-31 03:06:47 UTC,"Reopening - this is still an ongoing issue - if for some reason all clients end up connected to a single controller, then they will remain there until something causes the connections to drop (e.g. forcing agent restarts, firewalling off agent connections, bouncing the controller, etc)."
1799365,2019-02-01 02:36:31 UTC,Retargetting for 2.5.2 for some form of active load balancing.
1799365,2018-10-24 03:26:38 UTC,https://github.com/juju/juju/pull/9360 targets 2.4 with a couple changes that should help connections.
1799369,2018-10-23 08:27:53 UTC,I'm running Pocillo theme at scale 100% and no overlap when the top-panel is switched to left - then a window is maximised.
1799369,2018-10-23 08:48:02 UTC,"well in Ubuntu budgie 18.04 same settings was no problem. Now my panel width is 40px and if i increase the size overlap stays.
Tried to add new empty panel no applets same problem.
Tried to change scale to 100% and back to 200% have this bug on both scales."
1799369,2018-10-23 08:49:59 UTC,Have this bug on all themes standard Ubuntu budgie themes
1799375,2018-10-24 08:22:30 UTC,"How about using spam keywords, just like we do on the forum?"
1799375,2019-01-01 11:51:29 UTC,"Spam coming from legal notice are different than spam in the forums. E.g. they contain bitly links which can't be used as keywords, because they differ a lot."
1799375,2019-01-03 08:15:41 UTC,Of course we can use 'bit.ly' as a keyword for our spam filter... Trying to use the brain on the day after Sylvester may lead into errors :-D
1799375,2019-02-09 10:57:32 UTC,"We could also add a mandatory subject line - this will allow us to identify spam messages that got through to our inboxes more easily, because we can delete most of them without opening them."
1799375,2019-05-21 20:13:27 UTC,"I have created a new app 'quiz_captcha' which is like a quiz: A user has to answer a (widelands) specific question. If the answer didn't match the question, the validation fails. The questions and corresponding answers can be set through the admin interface. E.g. (Question | Answer):"
1799375,2019-06-18 19:04:59 UTC,"I think these are sufficient - we will have to come up with new ones when these get cracked, so it's better not to have too many."
1799375,2019-09-06 08:17:26 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/287
1799384,2020-06-16 16:24:29 UTC,Fixed with [1]
1799389,2018-10-23 09:26:52 UTC,apport information
1799389,2018-10-23 09:26:54 UTC,apport information
1799389,2018-10-23 09:26:56 UTC,apport information
1799389,2018-10-23 22:37:23 UTC,"Good observation. We need to update man page.
I am looking for volunteer for updating man page."
1799389,2018-10-24 02:43:48 UTC,"Hi srinivas-pandruvada,
It's a workaround to update man to avoid confusing, but not really help the case which user would like to correct the behavior without change in BIOS."
1799389,2019-11-10 12:39:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799389,2019-11-10 12:41:04 UTC,"Not sure is the same issue, but in boot logs as per `journalctl -b` I always have this error in Ubuntu 19.10:"
1799390,2019-08-22 09:40:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799390,2018-10-26 20:03:56 UTC,"Yes, I've set it via Gnome Tweak Tools - it just doesn't work.
I've found similar bug report for elementary OS: https://github.com/elementary/switchboard-plug-keyboard/issues/75"
1799390,2018-10-24 05:48:39 UTC,"I think you need to set these via the gnome config, otherwise g-s-d will reset the settings"
1799390,2018-10-23 19:05:05 UTC,"Tested with Fedora 29 liveusb - the same bug
KDE Neon 20181011 User  - no such bug. Looks like it's something in Gnome"
1799390,2018-10-23 16:06:45 UTC,Just tested liveusb with ubuntu 18.10 - bug can be reproduced there as well
1799392,2019-06-20 12:21:12 UTC,"I believe this can be marked ""fixed"""
1799392,2019-05-27 07:13:22 UTC,Also installed 19.04 and it also didn't happen there anymore.
1799392,2019-03-11 07:53:21 UTC,Just installed 18.04.2 and it didn't happen there.
1799392,2019-01-30 07:51:48 UTC,"A workaround for me was running ""sudo apt install cryptsetup && sudo apt install lvm2"" before running ""sudo apt autoremove"". This worked for 18.10 as well as 19.04. Both programs were already installed, but the first command makes sure the second command doesn remove them."
1799392,2019-01-23 21:17:18 UTC,"I have also just run into this issue. I manually partitioned my drive for LUKS. Started the system, did all updates, then ran autoremove. Could no longer boot. Had to select older entry in the boot menu. After manually reinstalling cryptsetup-initramfs as Victor suggested above it's now working."
1799392,2019-01-03 15:18:34 UTC,Just downloaded a fresh 19.04 iso (3 jan 2019) and the same happens.
1799392,2018-11-15 05:33:42 UTC,"On a fresh install, you can avoid this issue by just running `sudo apt install cryptsetup-initramfs` before any other running the autoremove. This marks the package as manually installed and so it won't be removed."
1799392,2018-11-15 04:03:13 UTC,"More updates: I was able to reproduce this using the full install using a freshly downloaded Ubuntu MATE 18.10 ISO. The full install has a shorter list of packages to autoremove after the fact:
cryptsetup
cryptsetup-bin
cryptsetup-initramfs
cryptsetup-run
dmeventd
libdevmapper-event1.02.1
liblvm2app2.2
liblvm2cmd2.02
libreadline5
lvm2"
1799392,2018-11-14 21:12:10 UTC,I wonder if there's a specific package in the desktop.minimal-remove file that makes cryptsetup-initramfs an orphan for some reason... that's the only thing I can think off. I will install a full version (non-minimal) and remove packages manually to see if I can spot the culprit.
1799392,2018-11-14 06:08:18 UTC,"Just checked and this does not happen on stock Ubuntu, after a fresh install, running `apt update && apt autoremove` does not try to remove any of the cryptsetup-* packages"
1799392,2018-11-14 05:04:19 UTC,Martin - is there a way to make `cryptsetup-initramfs` a required part of the system so that an `apt autoremove` doesn't remove it? I'll try to reproduce this with stock Ubuntu in case this should be handled upstream.
1799392,2018-11-14 04:57:24 UTC,"Okay, I've managed to solve it on my VM. Here's what I did:"
1799392,2018-11-14 03:55:35 UTC,"Okay, just found the offending package: cryptsetup-initramfs (which was a relief, since I started removing one by one from the top :)
When purging it, I got this from apt:"
1799392,2018-11-13 19:51:44 UTC,"I've been reproducing this consistently over the last two days on my XPS-15. It only happens if I install with LUKS encryption, the system is very stable (as long as I add acpi_rev_override=1 to grub kernel params). As soon as I do an apt autoremove, the next reboot drops into an initramfs shell."
1799392,2018-11-13 16:58:17 UTC,I can't reproduce this.
1799392,2018-10-26 12:07:31 UTC,Here are all the programs it wants to remove.
1799392,2018-10-24 11:19:30 UTC,"Hi, Autoremove removes all unused packages. I always do this after a full-upgrade. And till now it always worked well and it didn't delete any package it shouldn't."
1799392,2018-10-24 08:54:04 UTC,Hello. Why did you autoremove? What did you uninstall?
1799394,2018-12-17 08:54:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799398,2018-11-06 04:00:52 UTC,"3.2.0-137.183 - generic
Regression test CMPL, RTB."
1799398,2018-11-13 18:05:50 UTC,The package has been published and the bug is being set to Fix Released
1799398,2018-11-09 15:58:54 UTC,No verification needed for this release.
1799400,2018-11-02 02:59:20 UTC,"3.13.0-162.212~precise1 - generic
Regression test CMPL, RTB."
1799400,2018-11-13 18:08:26 UTC,The package has been published and the bug is being set to Fix Released
1799404,2018-11-05 09:49:16 UTC,Hardware Certification have begun testing this -proposed kernel.
1799404,2018-11-07 10:30:03 UTC,"4.4.0-138.164~14.04.1 - generic
Regression test CMPL, RTB."
1799404,2018-11-09 12:51:47 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/4.4.0-139.165~14.04.1/trusty-4.4-proposed-published.html"
1799404,2018-11-13 17:51:46 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-139.165~14.04.1
1799404,2018-11-13 18:15:40 UTC,The package has been published and the bug is being set to Fix Released
1799406,2018-11-02 09:03:15 UTC,"Reviewed:  https://review.openstack.org/613656
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=dbf6d2770dcd97d2ef2939ca735309e44b946c4d
Submitter: Zuul
Branch:    master"
1799406,2018-11-07 18:14:09 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/616263"
1799406,2018-11-08 14:02:47 UTC,Verified successfully on cosmic-proposed: https://paste.ubuntu.com/p/HsPFYHFsYr/
1799406,2018-11-09 04:17:58 UTC,This bug was fixed in the package aodh - 7.0.0-0ubuntu5
1799406,2018-11-13 15:40:16 UTC,"This bug was fixed in the package aodh - 7.0.0-0ubuntu4~cloud0
---------------"
1799406,2018-11-12 18:31:07 UTC,"The verification of the Stable Release Update for aodh has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1799406,2018-11-01 19:42:05 UTC,"Hello Liam, or anyone else affected,"
1799406,2018-11-28 18:31:30 UTC,I don't think this is invalid on oslo.i18n. It sounds like there's a problem with the Message class that caused this. The Aodh fix is only a workaround for that.
1799406,2019-02-28 14:40:56 UTC,"Change abandoned by Ryan Beisner (<email address hidden>) on branch: master
Review: https://review.openstack.org/614797"
1799406,2019-03-22 16:41:39 UTC,This issue was fixed in the openstack/aodh 8.0.0.0rc1 release candidate.
1799406,2018-11-12 18:31:02 UTC,This bug was fixed in the package aodh - 7.0.0-0ubuntu4
1799406,2018-10-26 18:08:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613656"
1799406,2018-11-07 18:45:36 UTC,Verified successfully on rocky-proposed: https://paste.ubuntu.com/p/z83B3DDHHW/
1799406,2018-10-25 18:26:57 UTC,Confirmed that changing:
1799406,2018-10-25 17:55:39 UTC,where:
1799406,2018-10-25 17:53:19 UTC,"Ok a little progress, value:"
1799406,2018-10-25 16:21:49 UTC,The failure is caused when _escape_unicode(value) [1] is called with the following (it expects a str for py3):
1799406,2018-10-24 14:42:07 UTC,"/usr/lib/python3/dist-packages/pymysql/connections.py (note translate in dir(obj) output)
-----------------------------------------------------------------------------------------
line 806, in escape"
1799406,2018-10-24 14:20:08 UTC,parameters= map to the Alarm class variables above
1799406,2018-10-24 14:18:47 UTC,"/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py
-----------------------------------------------------------
do_execute, line 508:  cursor.execute(statement, parameters)"
1799406,2018-10-24 13:01:20 UTC,A bit more details traceback: https://paste.ubuntu.com/p/PWhMqKM5Ht/
1799406,2018-10-24 12:01:12 UTC,Part of the reason why this only occurs on py3 is because the code path is different in pymysql for py2 vs py3 (see lines 68-102):
1799406,2018-10-23 19:28:07 UTC,"I'm having a hard time determining where the problem is. Adding upstream aodh, oslo.db, and oslo.messaging to see if anyone else can help."
1799406,2018-10-23 19:16:29 UTC,"# Sample for recreating
#
# py2 results: https://paste.ubuntu.com/p/JrDMDr9yMk/
# py3 results: https://paste.ubuntu.com/p/n2zt3Bw3VJ/"
1799406,2018-10-23 19:08:53 UTC,Please ignore comment #2 (hidden).
1799406,2018-10-23 17:29:40 UTC,"The problem looks to be that pymysql/converters.py is calling oslo_i18n's translate() method with a list argument (named _escape_table). translate expects desired_locale (string) to be passed in, not a list."
1799406,2018-10-25 19:47:49 UTC,Is this a problem with oslo.i18n? The oslo_i18n._message.Message class defines translate() as:
1799407,2018-11-13 19:31:33 UTC,The package has been published and the bug is being set to Fix Released
1799407,2018-11-13 17:56:29 UTC,This bug was fixed in the package linux-euclid - 4.4.0-9029.31
1799407,2018-11-01 07:13:31 UTC,CVE only update. No bug reports to be verified.
1799407,2018-11-05 09:48:44 UTC,Hardware Certification have begun testing this -proposed kernel.
1799407,2018-11-01 07:12:33 UTC,Automated testing is not meaningful. The euclid kernel only boots on very specific hardware which cannot be enforced within ADT.
1799407,2018-11-09 10:17:50 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/euclid/4.4.0-9029.31/euclid-4.4-proposed-published.html"
1799408,2018-10-29 08:59:11 UTC,"4.4.0-1037.43 - kvm
Regression test CMPL, RTB."
1799408,2018-11-13 18:44:48 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1037.43
1799408,2018-11-13 21:30:59 UTC,The package has been published and the bug is being set to Fix Released
1799409,2018-10-30 14:51:25 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/ynTblywB/459-pi2-kernel-440-1100108-78"
1799409,2018-11-05 09:49:05 UTC,Hardware Certification have begun testing this -proposed kernel.
1799409,2018-11-07 10:11:41 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1100.108/raspi2-4.4-proposed-published.html"
1799409,2018-11-13 18:45:46 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1100.108
1799409,2018-11-13 21:32:47 UTC,The package has been published and the bug is being set to Fix Released
1799410,2018-11-07 10:16:56 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1104.109/snapdragon-4.4-proposed-published.html"
1799410,2018-11-14 17:34:10 UTC,The package has been published and the bug is being set to Fix Released
1799410,2018-10-31 19:46:27 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/KMfvz8Rl/461-dragonboard-kernel-440-1104109-73"
1799410,2018-11-05 09:49:12 UTC,Hardware Certification have begun testing this -proposed kernel.
1799410,2018-11-13 18:48:38 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1104.109
1799412,2018-11-05 09:48:58 UTC,Hardware Certification have begun testing this -proposed kernel.
1799412,2018-11-13 19:08:54 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1028.30
1799412,2018-11-07 10:16:12 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.15.0-1028.30/raspi2-4.15-proposed-published.html"
1799412,2018-11-13 22:42:28 UTC,The package has been published and the bug is being set to Fix Released
1799416,2018-11-08 16:45:17 UTC,This kernel needs a nvidia specific blob to be released before it is releasable.
1799416,2018-11-12 05:10:56 UTC,"4.15.0-1024.25 - gcp
Regression test CMPL, RTB."
1799416,2018-11-12 06:26:14 UTC,The nvidia blobs are now released.
1799416,2018-11-13 17:57:53 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1024.25~16.04.2
1799416,2018-11-13 19:01:16 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1024.25
1799416,2018-11-13 22:39:54 UTC,The package has been published and the bug is being set to Fix Released
1799417,2018-11-01 07:08:09 UTC,"4.15.0-1026.26 - kvm
Regression test CMPL, RTB."
1799417,2018-11-13 19:07:52 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1026.26
1799417,2018-11-13 20:00:48 UTC,The package has been published and the bug is being set to Fix Released
1799424,2018-11-13 18:14:17 UTC,The package has been published and the bug is being set to Fix Released
1799424,2018-11-13 17:57:53 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1024.25~16.04.2
1799424,2018-11-12 06:09:20 UTC,"4.15.0-1024.25~16.04.2 - gcp
Regression test CMPL, RTB."
1799425,2018-10-25 16:21:50 UTC,Hardware Certification have begun testing this -proposed kernel.
1799425,2018-10-26 01:28:40 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.15.0-39.42~16.04.1/xenial-4.15-proposed-published.html"
1799425,2018-11-08 08:53:05 UTC,"4.15.0-39.42~16.04.1 - lowlatency
Regression test CMPL, RTB."
1799425,2018-11-13 17:59:20 UTC,This bug was fixed in the package linux-hwe - 4.15.0-39.42~16.04.1
1799425,2018-11-13 20:31:13 UTC,The package has been published and the bug is being set to Fix Released
1799426,2018-11-08 09:22:26 UTC,"4.15.0-39.42~16.04.1 - lowlatency
Regression test CMPL, RTB."
1799426,2018-11-13 21:53:31 UTC,The package has been published and the bug is being set to Fix Released
1799433,2018-10-23 11:19:06 UTC,Can you please attach the journal when this issue happens? Thanks.
1799433,2018-10-23 11:22:48 UTC,This may be the journal from that run..
1799435,2019-03-20 14:50:01 UTC,This issue was fixed in the openstack/watcher-tempest-plugin 1.1.0 release.
1799440,2020-07-26 18:44:23 UTC,"Using Ubuntu 20.04 I'm seeing high contrast icons for gnome-calculator, gnome-software and gnome-system-monitor so changing the status of those tasks to 'Fix Released'."
1799441,2018-10-23 15:31:48 UTC,"This is related:
https://bugs.launchpad.net/bugs/973136"
1799441,2019-12-09 12:58:48 UTC,"This is quite simple problem, just updating tags for WMP,MM,WINAMP. or just WMP.
which can be numbers 1-5."
1799441,2019-12-09 13:11:01 UTC,Please consider the fact that some files may already have one or more rating tags. Those ratings might be inconsistent and they might also differ from the internal Mixxx rating. Simply overwriting all ratings in the files with the Mixxx rating is not an option imho.
1799441,2019-12-12 10:14:01 UTC,"One solution is save mixxx rating tag to files.
I can very easily using mp3tag application to copy the rating tag what my other applications are using. and no need to care do mixxx overwrite other ratings."
1799441,2019-12-12 10:14:44 UTC,"I mean create an new tag ""MIXXXRATING"""
1799441,2019-12-12 13:21:09 UTC,"other solution is turn off , switch"
1799441,2020-05-22 08:38:01 UTC,I would love to have this feature. Having ratings fragmented between various applications is no fun. Would be great to be able to rate a song independently of the media player currently used. Then have ratings be updated and saved across the different players.
1799441,2020-06-08 07:32:48 UTC,For the record an unfinished attempt: https://github.com/mixxxdj/mixxx/pull/924
1799443,2018-10-23 12:15:32 UTC,Fedora now include the files https://<email address hidden>/thread/ZLO7EAYV7VRX3ZBWJ2IBSMPDQNOMKXPD/
1799443,2018-10-23 12:18:24 UTC,I believe Ubuntu's pi core images also include the files.
1799443,2019-03-01 20:22:53 UTC,WiFi files are now included but have different names https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=638a91ab5d066929d92c808e064c295a3ccab41d
1799444,2019-10-14 14:47:05 UTC,Niko Tyni from Debian pointed out the bug and the correct fix:
1799444,2019-10-13 06:34:01 UTC,I've bisected this issue and it is caused by this commit:
1799444,2018-12-20 12:10:23 UTC,"Seems definitely to be related to --jobs. I've had ""--jobs"" removed from my script for the last weeks and never seen it. Re-enabled it and sure enough, the error returned."
1799449,2018-11-13 19:13:16 UTC,This bug was fixed in the package linux-raspi2 - 4.18.0-1006.8
1799449,2018-11-13 21:52:23 UTC,The package has been published and the bug is being set to Fix Released
1799449,2019-02-14 12:10:56 UTC,This bug was fixed in the package linux-raspi2 - 4.18.0-1009.11
1799452,2018-11-08 16:45:31 UTC,This kernel needs a nvidia specific blob to be released before it is releasable.
1799452,2018-11-08 16:54:59 UTC,Certification tests not needed for cloud kernels.
1799452,2018-11-12 06:25:53 UTC,The nvidia blobs are now released.
1799452,2018-11-12 06:39:49 UTC,"4.18.0-1003.4 - gcp
Regression test CMPL, RTB."
1799452,2018-11-13 19:11:40 UTC,This bug was fixed in the package linux-gcp - 4.18.0-1003.4
1799452,2018-11-13 22:34:29 UTC,The package has been published and the bug is being set to Fix Released
1799452,2018-11-15 12:00:00 UTC,This bug was fixed in the package linux-gcp - 4.18.0-1003.4
1799453,2018-11-15 11:59:55 UTC,This bug was fixed in the package linux-kvm - 4.18.0-1004.4
1799453,2018-11-13 22:33:59 UTC,The package has been published and the bug is being set to Fix Released
1799453,2018-11-08 16:55:36 UTC,Certification tests not needed for cloud kernels.
1799453,2018-11-13 19:12:26 UTC,This bug was fixed in the package linux-kvm - 4.18.0-1004.4
1799453,2018-11-08 03:23:25 UTC,"4.18.0-1004.4 - kvm
Regression test CMPL, RTB."
1799458,2018-10-23 14:18:18 UTC,"Is this a resized installation, where you selected to install Ubuntu alongside Windows and let the installer resize partitions?"
1799462,2018-10-23 17:42:26 UTC,"I have been able to get around this by using the nouveau.modeset=0 to boot the liveusb and get Ubuntu 18.04 installed, however there is still the compatibility issue of nouveau to a GTX1050"
1799463,2018-10-23 13:32:16 UTC,It's not a charms bug. Charms do not configure NTP.
1799465,2018-10-23 15:50:23 UTC,"Agreed with the first.
Agreed with the second.
Agreed with the third (user level being .gitconfig git-ubuntu section?)"
1799465,2019-05-14 08:35:32 UTC,"BTW - I love that ~canonical-server is auto-added.
Could we have a local config file maybe in ~/.git-ubuntu where users can define their preferred default reviewers that will be added?"
1799465,2019-05-14 08:51:47 UTC,"I agree. I'd like a generic user configuration mechanism for various user preferences, which we'll need to put together first."
1799476,2019-10-15 06:31:57 UTC,"This looks great, thanks !"
1799476,2018-12-06 23:37:55 UTC,This errors come from the cloud calls made by a dependency engine.
1799476,2019-10-15 03:28:28 UTC,"While the messages aren't prefixed, they are now split out into different files and log collections."
1799488,2018-10-24 14:16:05 UTC,Anyone can help?
1799488,2018-10-25 06:16:12 UTC,"In the same env I can create centos and boot success.
export DIB_BLOCK_DEVICE_CONFIG='
- local_loop:
    name: image0"
1799488,2018-12-11 04:41:10 UTC,Have you tried updating kernel and kernel-firmware packages?
1799490,2018-10-23 15:06:26 UTC,"Please note, I'm not using this VM as DOM0."
1799490,2018-10-23 15:19:09 UTC,"Also, I misspoke, the server is running XenServer 7.0."
1799490,2018-10-23 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799490,2018-10-23 19:16:54 UTC,"In response to the kernel bot, I am not able to get to a point that I can gather logs."
1799490,2018-10-23 18:29:36 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1799497,2018-11-05 13:09:52 UTC,"Darn, would have been too good if it had only happened with zram. :( Sounds a bit like quickly catching all CPUs in a spin-dead-lock. And I am not sure right now which path to use for debugging. Try turning on lock debug in the kernel, though that often changes timing in ways that prevent the issue from happening again. Or hope its not a hardware driver and try to re-produce in a VM, but even if that is possible there were issues with the crash tools and kernels having certain address space randomization enabled. And that was even before Metldown/Spectre hit us."
1799497,2020-01-09 18:33:59 UTC,"Can reproduce this with stress-ng exercising high memory pressure scenario using:
stress-ng --brk 0 -v --aiol 0"
1799497,2018-12-19 06:32:54 UTC,"OK.. it is been quite a while with no locks I had it once after the zram config pacakge was removed,, but no other locks since then."
1799497,2019-10-31 01:37:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799497,2019-10-31 02:09:52 UTC,Other reports of similar issues with zram on kernel 4.15:
1799497,2020-01-09 17:38:30 UTC,"It would be useful to know if one has made any specific zram config changes, and if so, what your current config is just to help with the debugging of this issue."
1799497,2020-01-09 17:47:46 UTC,"I'm assuming the defaults are being used for the moment, this means 50% of total memory being used in total distributed across the number of CPUs, as defined in /usr/bin/init-zram-swapping"
1799497,2020-01-10 09:56:46 UTC,"Hi.. I had to remove zram config from my production servers long ago. ...
since then I don't have the issue.  I was using LXD containers a lot on the
hosts with different kind of usage,, But I don't have any other setup at
the moment"
1799497,2018-11-03 10:57:30 UTC,"Got a hot locked with no zram-config installed.. Same behaviour, no log information, can't even type in the console, no ssh, no ping.  ALso all the LXD containers don't ping either"
1799497,2020-01-16 18:17:13 UTC,It sounds like what I was getting.
1799497,2020-01-28 19:47:32 UTC,Captured the hard lock on the following
1799497,2020-01-30 14:47:28 UTC,Couple more notes:
1799497,2020-01-30 16:14:09 UTC,Running w/o swapfile and zswap and just stress-ng brk and stack stressors with NO file I/O can also lock the system.
1799497,2020-02-07 16:25:38 UTC,Cornered this to zswap and not an issue with mm or I/O.  Figured out that 3 hours soak testing on each bisect step is the only reliably way to do a bisect.  Bisected between 4.20 and 5.0 finally cornered the issue and hence the commits required to fix this.
1799497,2020-02-17 21:28:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1799497,2020-02-21 18:57:46 UTC,Soak tested the -proposed kernel for 2 hours with no hang occurring. Verified OK.
1799497,2020-03-16 10:53:57 UTC,This bug was fixed in the package linux - 4.15.0-91.92
1799497,2020-01-16 17:27:45 UTC,"After quite a bit of experimentation I found that I can reproduce the bug if I have zram *and* also swap on the filesystem enabled while exercising the brk stressors and aiol (to cause lots of I/O). Eventually the system grinds to a halt, we lose interactivity and we eventually get lockups as follows:
[ 2012.040006] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [stress-ng-brk:1632]
[ 2012.040922] Modules linked in: zram(E) kvm_intel(E) kvm(E) irqbypass(E) crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) pcbc(E) aesni_intel(E) aes_x86_64(E) crypto_simd(E) glue_helper(E) cryptd(E) psmouse(E) input_leds(E) floppy(E) virtio_scsi(E) serio_raw(E) i2c_piix4(E) mac_hid(E) pata_acpi(E) qemu_fw_cfg(E) 9pnet_virtio(E) 9p(E) 9pnet(E) fscache(E)
[ 2012.044655] CPU: 2 PID: 1632 Comm: stress-ng-brk Tainted: G            EL   4.15.18 #1
[ 2012.045581] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1 04/01/2014
[ 2012.046555] RIP: 0010:__raw_callee_save___pv_queued_spin_unlock+0x10/0x17
[ 2012.047340] RSP: 0018:ffffb73382083718 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff11
[ 2012.048238] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000002
[ 2012.049078] RDX: 0000000000000000 RSI: ffff9d327c2f6918 RDI: ffffffffa3269978
[ 2012.049909] RBP: ffffb73382083720 R08: ffff9d327c2f6918 R09: ffff9d327c0a5328
[ 2012.050746] R10: ffff9d327c1e2310 R11: ffff9d327c1e2328 R12: ffff9d327c2f6800
[ 2012.051574] R13: ffff9d327c1e2328 R14: ffff9d327c1e2310 R15: ffff9d327c1e2200
[ 2012.052436] FS:  00007f89f2ccd740(0000) GS:ffff9d327f280000(0000) knlGS:0000000000000000
[ 2012.053382] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2012.054058] CR2: 00007f1350a8dd90 CR3: 00000000311a4004 CR4: 0000000000160ee0
[ 2012.054889] Call Trace:
[ 2012.055192]  get_swap_pages+0x193/0x360
[ 2012.055652]  get_swap_page+0x13f/0x1e0
[ 2012.056123]  add_to_swap+0x14/0x70
[ 2012.056530]  shrink_page_list+0x81d/0xbc0
[ 2012.057013]  shrink_inactive_list+0x242/0x590
[ 2012.057523]  shrink_node_memcg+0x364/0x770
[ 2012.058012]  shrink_node+0xf7/0x300
[ 2012.058432]  ? shrink_node+0xf7/0x300
[ 2012.058863]  do_try_to_free_pages+0xc9/0x330
[ 2012.059368]  try_to_free_pages+0xee/0x1b0
[ 2012.059842]  __alloc_pages_slowpath+0x3fc/0xe00
[ 2012.060424]  __alloc_pages_nodemask+0x29a/0x2c0
[ 2012.060963]  alloc_pages_vma+0x88/0x1f0
[ 2012.061414]  __handle_mm_fault+0x8b7/0x12e0
[ 2012.061909]  handle_mm_fault+0xb1/0x210
[ 2012.062375]  __do_page_fault+0x281/0x4b0
[ 2012.062848]  do_page_fault+0x2e/0xe0
[ 2012.063274]  ? async_page_fault+0x2f/0x50
[ 2012.063751]  do_async_page_fault+0x51/0x80
[ 2012.064262]  async_page_fault+0x45/0x50
[ 2012.064719] RIP: 0033:0x55ec1997bd0a
[ 2012.065147] RSP: 002b:00007ffeacd21600 EFLAGS: 00010246
[ 2012.065754] RAX: 000055ec28601000 RBX: 0000000000000005 RCX: 00007f89f2de956b
[ 2012.066580] RDX: 000055ec28601000 RSI: 00007ffeacd216d0 RDI: 000055ec28602000
[ 2012.067410] RBP: 00007ffeacd216c0 R08: 0000000000000000 R09: 00007f89f3d0c2f0
[ 2012.068290] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
[ 2012.069129] R13: 0000000000000002 R14: 0000000000000001 R15: 00007ffeacd216d0
[ 2012.069965] Code: 50 41 51 41..."
1799497,2018-11-02 03:34:14 UTC,"Correct.. I ould like to give it some more time to see if it doesn't happen.  So far so good, no lockups.  I hadnt have to restart any server in a week and a half."
1799497,2018-11-01 01:34:58 UTC,"Just happened again, though the machine wouldn't reboot at all afterwards, leading to the hosting provider going for a motherboard replacement, so I guess better luck next week with debugging this."
1799497,2018-11-01 15:27:04 UTC,"Oh, I am also using zram-config on the affected machine."
1799497,2018-10-23 16:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799497,2018-10-23 16:30:49 UTC,Would you be able to test some kernels? A bisect can be done if we can identify what kernel version introduced this issue.
1799497,2018-10-23 17:59:14 UTC,"Well, kinda, this is a production server running a lot of publicly visible services, so I can run test kernels on it so long as they don't regress system security."
1799497,2018-11-01 18:02:44 UTC,"Darn, wanted to reply earlier. So maybe at least for Luis who sounds to have multiple servers in a test environment, it would be possible to run two otherwise identical servers and only remove zram-config on one. Then one locking up and the other not would be quite good proof."
1799497,2018-10-23 18:02:03 UTC,apport information
1799497,2018-10-23 18:02:04 UTC,apport information
1799497,2018-10-23 18:02:07 UTC,apport information
1799497,2018-10-23 18:02:08 UTC,apport information
1799497,2018-10-23 17:59:53 UTC,Oh and whatever kernel I boot needs to have support for ZFS 0.7 or I won't be able to read my drives.
1799497,2018-10-23 18:02:10 UTC,apport information
1799497,2018-10-23 18:02:13 UTC,apport information
1799497,2018-10-23 18:02:15 UTC,apport information
1799497,2018-10-23 18:04:06 UTC,Note that I've deleted the wifisyslog and currentdmesg as they're not relevant (current boot) and included information that I'd rather not have exposed publicly.
1799497,2018-10-24 06:07:38 UTC,"Hello, I sumbitted the report on LXD since that is the only thing I have installed on the server that is actively running as Stéphane mentioned on https://github.com/lxc/lxd/issues/5197"
1799497,2018-10-24 07:42:21 UTC,"To add a bit more detail (maybe unrelated but with so little evidence everything helps), when thos lockups happen, is the server at least pingable? Some other idea would be, as long as those servers are accessible enough to see whether sysrq combinations are still handled. Though I fear at least for Stéphane that server is somewhere else with probably only ssh (maybe ipmi) access. But if that was possible and working, maybe one could prepare kdump and enable the sysrq crashing combo."
1799497,2018-10-24 16:22:54 UTC,The server doesn't respond to pings when locked up.
1799497,2018-11-01 05:56:56 UTC,In my case it hasn't happen again.. Although I removed package zram-config from the host servers  ( I think this is the only difference in software from 16.04 to 18.04 that I added.  I would like to either discard or confirm that that it has an effect on the issue
1799497,2018-10-23 18:02:09 UTC,apport information
1799509,2019-07-31 13:17:23 UTC,The bug is now fixed in gnutls-3.6.4 (on Disco Dingo).
1799509,2018-10-23 20:21:31 UTC,"The attachment ""gnutls-3.6.4-fix-rehandshake.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1799511,2018-10-23 17:29:35 UTC,"I've extracted the events from cloud-init analyze dump and the hyperv kvp event handler is generating additional event_types we've not seen before, 'failed' and 'skip';  cloud-init will need to ignore these."
1799511,2018-10-23 17:58:33 UTC,"It doesn't look like the hyperv keystore daemon is running, it's supposed to create /var/lib/hyperv directory; that's not done here.  Cloud-init should handle creating that dir I think even if the daemon isn't running.  Lastly, since the directory wasn't present, the handler logged the errors which generated events which introduced the ""skip"" and ""failed"" events.  Cloud-init will need to find out how to log these errors to /var/log/could-init.log without invoking the HyperV handler so we don't get the failures in the event stream."
1799511,2018-10-23 20:28:45 UTC,"On Tue, Oct 23, 2018 at 05:58:33PM -0000, Ryan Harper wrote:

> It doesn't look like the hyperv keystore daemon is running, it's
> supposed to create /var/lib/hyperv directory; that's not done here.
> Cloud-init should handle creating that dir I think even if the daemon
> isn't running.  Lastly, since the directory wasn't present, the handler
> logged the errors which generated events which introduced the ""skip"" and
> ""failed"" events.  Cloud-init will need to find out how to log these
> errors to /var/log/could-init.log without invoking the HyperV handler so
> we don't get the failures in the event stream.
"
1799511,2018-10-24 11:31:53 UTC,In further testing I have confirmed that it was indeed the change to add cloud-init KVP telemetry that introduced this issue.
1799511,2018-10-24 11:42:21 UTC,"This issue is not present on the standard (non-minimal) image that is published to azure, `b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-18_10-amd64-server-20181018-en-us-30GB`. I was able to run `cloud-init analyze show`, `cloud-init analyze blame` and `cloud-init analyze dump` with no visible errors. The directory `/var/lib/hyperv` was also present with a timestamp indicating it was created during boot. KVP telemetry is enabled on this image."
1799511,2019-02-26 21:18:22 UTC,I suspect this is related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640
1799540,2019-01-28 17:07:01 UTC,"This bug is fixed with commit 3f12012e to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=3f12012e"
1799540,2019-05-10 18:07:36 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1799542,2019-10-15 13:52:25 UTC,The prompting mechanism is indeed on the roadmap but we don't have the required kernel components yet (apparmor prompting) so there's nothing we can do in snapd yet.
1799542,2018-10-24 20:26:50 UTC,"It works, thank you. But.."
1799542,2018-10-25 09:38:21 UTC,"i think the ""popup a permissions window"" thingie is on the roadmap, but it might still take a while ..."
1799542,2018-10-24 08:22:42 UTC,"you need to connect the removable-media interface (for security reasons this interface is not auto-connected), either by going to the software center, finding gimp in there and clicking the ""Permissions"" button where you then can allow access to ""removable storage devices"" or via the command line with:"
1799544,2018-10-25 17:42:30 UTC,"Hi,
Thank you for contributing to cloud-init."
1799546,2018-10-23 18:29:12 UTC,"This seems more difficult to reproduce than I originally thought.  It happened the first time I tried the failover, and then after a bunch more iterations it only happened one more time."
1799550,2018-10-24 18:12:21 UTC,Thanks for the answer but I'm not sure I fully understand.
1799550,2018-10-24 18:41:12 UTC,"You can create the partitioning to use /boot on a separate partition, and / on an encrypted disk with LVM (the installer gives you various options for what to use a partition with). It's the same story as that blog post, but using the graphical options."
1799550,2018-10-24 19:28:06 UTC,"Ok I missed that point.
You can close it if you want,except if you intend to support resizing *and* disk encryption.
Sorry for the noise."
1799550,2018-10-25 18:51:07 UTC,"Well actually I don't see how to achieve that with the *k*unbuntu installer.
I have created an encrypted partition
blkid /dev/sda7
/dev/sda7: UUID=""c9deed35-610e-4328-b8e7-079e95d43f76"" TYPE=""crypto_LUKS"" PARTLABEL=""Linux"" PARTUUID=""13aac430-9701-4323-810d-53231decca9c (on which I installed kubuntu as described in the blog link)."
1799550,2019-05-23 12:32:36 UTC,"Ok it is a feature request but I see it more as a security regression.
It used to be possible to encrypt /home in one click in the installer. This feature does not exist anymore and (I assume that) many users simply gave up and installed an unencrypted (k)Ubuntu.
It is possible to install an encrypted ""/"" but the howto is not given in the installer.
http://blog.botux.fr/en/2015/09/ubuntu-installation-manual-full-disk-encryption-lvm-on-luks/ is useful but needs to be adapted (no more swap) : it is far from obvious for a standard user."
1799550,2019-10-25 08:55:46 UTC,The issue remains the unchanged with 19.10.
1799550,2020-10-14 08:20:32 UTC,"No progress on this issue in 20.04 beta :(
There is still no way to install an encrypted kubuntu in dual boot without having to deal with the command line. That’s a no go for many users.
I’m  not even asking for full encryption.  The kubuntu installer should at least be able to install an encrypted kubuntu (even with a non encrypted /boot…) alongside windows on the same disk."
1799550,2020-10-14 08:21:27 UTC,"oups, no progress on *20.10 beta* (of course 20.04 wasn't better)."
1799550,2020-11-18 12:00:19 UTC,"No progress on this topic :(
It is still not possible to install kubuntu 20.10 encrypted in dual boot with windows without having to deal with the command line.
This is a security issue as it forces many beginners to go for a non encrypted installation."
1799550,2020-11-18 12:03:26 UTC,"I might work with the ubuntu installer 20.10 (to be confirmed) but it does not work with the kubuntu installer. By 'it does not work' I mean 'the option is not given'.
One has to create the LUKS, open it, then launch the installer and eventually use chroot to make it work."
1799550,2020-12-22 23:10:44 UTC,"I think the answer there is fscrypt - native encryption at the filesystem level supported by ext4 and some other day - but I'm not sure what the plans are. Partitioning is hard and the requirement to setup a separate /boot and crypt device are not always possible, though it is less of an issue these days with GPT devices."
1799550,2020-12-23 01:36:30 UTC,Thank you so much for the feedback!
1799550,2021-01-07 19:34:30 UTC,What's the meaning of this tag?
1799550,2018-10-24 16:45:29 UTC,It's a feature that was there before (encrypting /home) but is no longer supported.
1799552,2018-10-23 18:37:25 UTC,"Thinking a bit more I'm not sure unmonitor is ever the solution I would want for these templates. I'm trying to come up with a use case and can't do it. For now I've changes all ""unmonitor"" to ""alert"" in /etc/monit/templates/root*. I'll give that a try for a while."
1799554,2018-10-23 21:30:42 UTC,the issue is somewhat similar to bug #1720262
1799555,2020-04-16 05:47:08 UTC,"Reviewed:  https://review.opendev.org/718213
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f2298815a2c87b2539c16ea10cf86e9576e944f1
Submitter: Zuul
Branch:    stable/queens"
1799555,2020-04-16 05:47:00 UTC,"Reviewed:  https://review.opendev.org/718212
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=89f5193f4a5f0a707474eb604bcfbba120db0d45
Submitter: Zuul
Branch:    stable/rocky"
1799555,2020-04-15 03:10:24 UTC,"Reviewed:  https://review.opendev.org/718210
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=92f1521353aa3ef5d229029c9aa38c409a8850f0
Submitter: Zuul
Branch:    stable/train"
1799555,2020-04-07 20:19:46 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/718213"
1799555,2020-04-07 20:19:26 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/718212"
1799555,2020-04-07 20:19:09 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/718211"
1799555,2020-04-07 20:18:42 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/718210"
1799555,2019-11-07 17:39:02 UTC,"Reviewed:  https://review.opendev.org/689550
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d15ad2e481b9b888079d55ba46d73ca5b7253285
Submitter: Zuul
Branch:    master"
1799555,2019-10-18 17:06:46 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/689550"
1799555,2019-10-18 16:58:35 UTC,Found this problem again in [1].
1799555,2019-09-10 10:16:03 UTC,"Reviewed:  https://review.opendev.org/680657
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5b07cb21e3d8abe15c6322616b0b8976b54aef8d
Submitter: Zuul
Branch:    stable/stein"
1799555,2019-09-10 09:50:13 UTC,"Reviewed:  https://review.opendev.org/680658
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=68077a4cc9af638256a272cda42b44346d90589d
Submitter: Zuul
Branch:    stable/rocky"
1799555,2019-09-09 23:50:58 UTC,"Reviewed:  https://review.opendev.org/680659
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=57725fc7d4513c37de597a4b86f8d6878e2be034
Submitter: Zuul
Branch:    stable/queens"
1799555,2019-09-06 11:02:51 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/680659"
1799555,2020-04-16 06:34:14 UTC,"Reviewed:  https://review.opendev.org/718211
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5f8371357192b3e0cb2b6388fb17561bb1cd2212
Submitter: Zuul
Branch:    stable/stein"
1799555,2019-09-06 11:00:35 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/680657"
1799555,2019-09-06 10:55:22 UTC,Looks like we don't have those issues since https://review.opendev.org/665422 was merged. I will mark this bug as fixed now.
1799555,2019-09-06 11:02:35 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/680658"
1799555,2018-10-27 17:41:21 UTC,Looks intermittent.
1799555,2019-03-13 15:44:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/643079"
1799555,2019-03-28 10:47:14 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/643079"
1799555,2019-05-21 16:38:52 UTC,It happened again recently http://logs.openstack.org/87/658787/5/check/neutron-fullstack/7d35c49/testr_results.html.gz
1799555,2019-05-22 16:50:31 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/660785"
1799555,2019-05-30 17:47:02 UTC,"Reviewed:  https://review.opendev.org/660785
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b3404d900ef142637869e6e8999d29d712185e95
Submitter: Zuul
Branch:    master"
1799555,2019-03-02 14:30:08 UTC,It happens again. I saw it at least 3 times in last week.
1799555,2019-06-07 11:24:27 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/663903"
1799555,2019-06-09 02:13:42 UTC,"Reviewed:  https://review.opendev.org/663903
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d01a1deca9a9ccc8c396da6ca88839fa0862dd65
Submitter: Zuul
Branch:    master"
1799555,2019-06-14 15:28:37 UTC,Hello:
1799555,2019-06-14 16:05:32 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/665422"
1799555,2019-06-14 16:19:47 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/665426"
1799555,2019-06-19 01:37:50 UTC,"Reviewed:  https://review.opendev.org/665426
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b76321f1d8864b013d15b236b1868a21ffb8b875
Submitter: Zuul
Branch:    master"
1799555,2019-06-21 19:27:53 UTC,"Reviewed:  https://review.opendev.org/665422
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7c5ae8a0378fa50853e91241426b6470ffe7492
Submitter: Zuul
Branch:    master"
1799555,2019-06-07 11:03:21 UTC,Hello:
1799557,2018-10-23 19:35:26 UTC,Related: https://review.openstack.org/#/c/449155/10/specs/rocky/approved/ironic-instance-switchover.rst@207
1799560,2019-03-20 16:19:27 UTC,There is also this script which records the average time to retrace on a release and architecture basis.
1799560,2019-01-30 17:14:06 UTC,"While there are counters for cores retraced and cores uploaded these are from rabbitmq and not from the retracers directly, additionally looking at rabbitmq doesn't provide us information about whether or not the retrace was successful or not so there is definitely some room for improvement."
1799560,2019-02-08 06:51:11 UTC,"As far as I know, no. prometheus has its own format, see https://github.com/prometheus/client_python"
1799560,2019-02-07 20:37:04 UTC,"Is json ""prometheus scrapable""? I ask as the Error Tracker already produces json for its own use e.g. https://errors.ubuntu.com/api/1.0/retracers-average-processing-time/?limit=32767&format=json."
1799560,2019-03-18 23:01:23 UTC,I've gone ahead and added the following code to the server team metrics which is now populating the foundationsro data source with retrace results in the foundations_production_retracer_results table.
1799562,2018-11-20 11:19:13 UTC,Hello Sebastien Bacher
1799562,2018-11-21 15:00:50 UTC,"I can't confirm that, does it work on file? Could you try with a new user profile?"
1799562,2018-11-21 19:47:34 UTC,Hello Sebastien Bacher
1799562,2018-11-21 21:27:29 UTC,"Simply create any document, image or folder and play any document on the Ubuntu desktop and click ""move to"" or ""copy to"" to produce the ""error"" message. The result will be the same."
1799562,2018-11-23 07:03:12 UTC,"Is your userdir or desktop dir on a special location? There is a similar report upstream from non Ubuntu on https://bugzilla.gnome.org/show_bug.cgi?id=770836
Do you have any error in journalctl when you get the issue?"
1799562,2020-02-25 14:27:06 UTC,"Reproducible with new and existing profiles using nautilus 3.26.4
in Ubuntu 18.04. Only seen with user created files/folders and not
with system items such as 'Home' or 'Network Servers' as 'Move to'
and 'Copy to' are greyed out on right click menu."
1799562,2018-11-20 09:29:36 UTC,Thank you for your bug report. Does it happen only on the desktop? What version of Ubuntu/nautilus do you use?
1799568,2018-10-24 15:13:27 UTC,"That's fine, thanks for assigning it to me."
1799572,2019-05-14 14:50:53 UTC,"Based on Tingjie's reproduction attempt and Mitch's response, this bug can be marked ""Fix Released"" based on the ceph upgrade."
1799572,2019-05-16 02:38:15 UTC,"Hi Michel, there are several memory leak fixing in Ceph Mimic release as following, actually this Ceph upgrade is from 10 to 13.2.2, there are no more than the the 6 memory leak fixings.
---------------------------
common: common/dns_resolve: fix memory leak (pr#19649, Yao Zongyou)
common: fix potential memory leak in HTMLFormatter (pr#20699, Yao Zongyou)
common: test: fix unittest memory leak to silence valgrind (pr#19654, Yao Zongyou)
rbd-mirror: ImageMap memory leak fixes (pr#19163, Venky Shankar)
rbd,tests: test/librbd: fix valgrind memory leak warning (pr#17187, Mykola Golub)
rbd,tests: test/librbd: memory leak in recently added test (pr#18478, Mykola Golub)"
1799572,2019-05-14 01:56:22 UTC,I have setup storage dedicated multi-node deployment with ISO:20190509T013000Z to verify but cannot see obvious memory leak after unlock the first controller.
1799572,2019-05-08 14:01:39 UTC,"Vivian, Assuming your question is directed to me, I don't know if the issue is reproducible in the latest code base or not. I checked with the reporter and he no longer has an env to retest this. The developer who has this bug should be able to attempt to reproduce the issue and update accordingly. Cindy already confirmed that the issue was reproducible prior to the upgrade, so it should be straight-forward for the developer to verify the same scenario with the new version of ceph."
1799572,2018-10-24 17:37:22 UTC,Targeting stx.2019.03 for now until further investigation. This is not a very likely scenario where the user configures the 1st controller and doesn't proceed with the rest of the system configuration for an extended period.
1799572,2019-05-14 14:07:49 UTC,"Hi Tingjie,"
1799572,2019-05-07 23:23:47 UTC,"Khalil, Ghada <email address hidden> Since patches to upgrade ceph have been merged. is the issue reproduced on latest code base? Thanks!"
1799572,2019-01-23 14:42:07 UTC,issue reproduced. Vivian will handle this issue after Ceph upgrade is done.
1799572,2018-10-31 19:03:19 UTC,Cindy can you please get with Vivian and have her assign someone to this bug?  Thanks!
1799574,2020-09-23 15:18:19 UTC,Since I ran into this bug repeatedly I'll work on a fix for 2.3
1799574,2019-12-18 16:09:16 UTC,"Using samples from the start is problematic IMO as users probably don't expect it, and if the do the result is unprecitable because that range is not visible on the waveform."
1799574,2019-12-17 15:22:29 UTC,"ok, I misunderstood 'recursive'."
1799574,2018-12-23 21:54:27 UTC,"Ok, the current situation is odd."
1799574,2019-12-17 13:08:20 UTC,"that's just the play direction. use '[group],reverse' '1'"
1799574,2018-12-23 22:37:32 UTC,1) would be the winner :) because loop_end after track end would be a feature IMO
1799574,2019-12-17 14:08:58 UTC,"mevsme's idea is to build a loop that runs bejond the end of the track as if repeat was enabled, by jumping to the beginning and playing the missing samples from there."
1799574,2019-12-17 11:37:23 UTC,"Maybe also, as a variant, we can make recursive loop that starts at the end and finish at the start? D"
1799575,2018-10-26 19:01:26 UTC,Marking as stx.2019.03 for now. This should be investigated by the same person looking at: https://bugs.launchpad.net/starlingx/+bug/1799486
1799575,2019-06-13 13:27:01 UTC,"Given there is no infrastructure network anymore, I'm going to close this bug as this configuration is no longer valid. The cluster network doesn't have any traffic controls or rate-limiting."
1799575,2019-05-16 13:34:26 UTC,"@Yang, Are you still able to reproduce this issue? Based on Ran's investigation, she is unable to reproduce the issue."
1799575,2018-12-11 06:18:07 UTC,"based on system files provided above. the root reason of this bug is ""we band two 10G NIC to bond0 by mode=4, but kernel set the speed of bond0 20G instead of 10G""."
1799575,2018-12-06 19:41:05 UTC,Files under /sys/devices/net and /sys/devices/pci* attached.
1799575,2018-12-06 08:39:12 UTC,Thanks Yang~
1799575,2018-10-24 12:36:46 UTC,Low priority - this is a day one issue and will have no impact unless the system is in an overload condition. It is also specific to a very particular configuration. Not serious enough to gate stx.2018.10. TBD whether this should gate stx.2019.03 or not.
1799575,2018-12-05 19:05:59 UTC,"controller-0:~$ cat /sys/class/net/bond0.79/speed
20000
controller-0:~$ sudo ethtool bond0
Settings for bond0:
        Supported ports: [ ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 20000Mb/s
        Duplex: Full
        Port: Other
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Link detected: yes
controller-0:~$ sudo ethtool bond0.79
Settings for bond0.79:
        Supported ports: [ ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 20000Mb/s
        Duplex: Full
        Port: Other
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Link detected: yes"
1799575,2018-12-05 16:05:58 UTC,"Hi Ran, I will get back to you next week. That system is booked by others this week."
1799575,2018-12-05 06:16:32 UTC,"this bug can not be verified.
by deeply analyzing, the difference of physical network between two environment may be the key point. Could you provide files under ""sys/class/net"", so I can get more network information of your env.
Thanks"
1799575,2018-12-03 08:48:14 UTC,"Thank you Yang. Could you provide more information?
   1. results of cmds:
      $cat /sys/class/net/bond0.79/speed
      $ethtool bond0
      $ethtool bond0.79
   2. verify the switch support ""802.3ad""
   3. from logs provided, enp131s0f0 and enp131s0f1 are two 10G physical NIC, right?"
1799575,2018-11-29 16:40:51 UTC,It is indeed configured as no lag by system. I'm not sure if it is intentional.
1799575,2018-12-05 19:07:08 UTC,Got the system earlier than expected. See info from above comments.
1799575,2018-11-29 08:59:18 UTC,"from logs provided by the reporter,
  a) it is the system ""using speed 20000 for tc filtering on bond0.79""
  b) by reproducing and analyzing logs, infra interface is configured to ""no aggregation"". To confirm this, could you offer final configure file? (by the latest code, it is under /opt/platform/config/<version>/cgcs_config)"
1799576,2020-09-28 00:46:55 UTC,https://github.com/mixxxdj/mixxx/pull/3137
1799579,2019-09-19 14:49:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1799579,2018-11-14 19:18:47 UTC,"Attached below is the BMC configuration data that was written by MAAS.  In addition to the attached BMC configuration, other permutations were attempted such as setting Rmcpplus_Conf_Privilege:Maximum_Privilege_Cipher_Suite_Id_#'s to Administrator as outline in https://www.gnu.org/software/freeipmi/manpages/man5/ipmi-config.conf.5.html but I was still unable to login to the BMC's UI."
1799579,2018-11-05 22:36:25 UTC,I have tried multiple times to reproduce this by logging into the UI of the BMC for the MAAS CI's IPMI machines.  The only time I have had issues logging in is with:
1799579,2018-11-06 21:23:07 UTC,Some reasons why I think this is an issue with the firmware of the Tuleta:
1799579,2018-10-31 21:14:01 UTC,By adding this ~/.ssh/config (forgot to include in last comment above):
1799579,2018-10-31 21:13:12 UTC,By adding the below to ~/.ssh/config and restarting sshd I was able to ssh into machines that were giving me issues before (here is one example):
1799579,2018-10-31 21:00:36 UTC,Using the CI I found some machines would not let me ssh into the BMC:
1799579,2018-10-25 17:33:14 UTC,"Check one of the machines in the CI whether you can ssh to the BMC using the MAAS credentials. If not, you can always figureout what settings you need to be tweaked."
1799579,2018-10-31 21:14:59 UTC,Marking this as invalid as I do not think this is a MAAS bug due to what was found above.
1799579,2018-10-23 23:14:51 UTC,Do you have known IPMI hardware that MAAS doesn't create administrator privileges on?
1799580,2020-07-29 06:07:13 UTC,I noticed the same bug affecting me on 3 installs:
1799580,2020-07-13 15:52:18 UTC,I am using a stock Ubuntu Studio 20.04 on a Dell Optiplex 3020.
1799580,2020-07-13 15:50:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799580,2020-07-13 16:29:33 UTC,"I don't believe this is a bug with qastools since it simply tells alsa what to do. Also, the issue can be duplicated on alsamixer. qasmixer itself doesn't save anything, neither does alsamixer. Something somewhere isn't remembering between reboots, but it's definitely not qastools related."
1799588,2018-10-24 14:53:34 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1799588,2018-10-24 19:04:59 UTC,"This issue was posted to openstack-operators, where some responders said they were unable to duplicate the problem, and that's a big concern of mine. If it is a misconfiguration of my cluster, I still want to understand what went wrong and how to fix it, because this is a pretty serious problem.  To shed a little light on our installation procedure, what we do is we provision our bare metal using xCAT, after which we apply RPM packages from the CentOS Cloud repo (http://mirror.centos.org/centos/7/cloud/x86_64/openstack-queens/) and configure services strictly according to the openstack docs (e.g. https://docs.openstack.org/glance/queens/install/install-rdo.html).  We tweak the config files to use HTTPS and speak to our endpoints, etc, but there is really nothing exotic about our setup.  We were running glance under uwsgi, behind apache+mod_proxy, but as part of our troubleshooting we reverted to using the openstack-glance-api systemd unit file that launches the old python2 eventlet -- there was no change in the exhibited behavior though."
1799588,2018-10-26 17:48:22 UTC,"Okay, we believe we understand the problem now."
1799588,2018-10-26 19:17:28 UTC,"Since this bug is already public, related patches can be pushed directly to review.openstack.org (and it's a trivial enough patch that if someone wants to do that for Michael I don't think we need to worry about ICLA coverage for it, but make sure to git-am it so his authorship is correctly preserved)."
1799588,2018-10-26 19:18:47 UTC,@ Jeremey I have just figured out how to deal with gerrit and believe it's submitted.
1799588,2018-11-05 19:44:41 UTC,Change is still under review.
1799588,2018-11-05 19:53:34 UTC,Adjusted the bug title to reduce the freakout effect.
1799588,2018-11-05 20:14:30 UTC,"The problem is that the way a ""sample_default"" value is displayed (as opposed to an actual ""default"" value) is misleading.  This has been fixed in oslo.config master (fix not yet released):
https://review.openstack.org/#/c/607353/"
1799588,2018-11-05 20:17:33 UTC,The oslo.config bug for this is https://bugs.launchpad.net/oslo.config/+bug/1795729
1799588,2018-11-05 20:40:37 UTC,"We use sample_default for several config values, so regardless of what's decided about changing the default value for paste_deploy.flavor, part of the fix for this bug should be a patch to update requirements.txt and lower-constraints.txt in glance once oslo.config 6.6.3 is released and upper-constraints.txt has been updated in the requirements repo."
1799588,2018-11-06 15:32:34 UTC,"I was having serious deja vu yesterday when looking at this.  This is a duplicate of https://bugs.launchpad.net/glance/+bug/1711117 .  Will mark the old one as a duplicate of this (which is a bit weird, but looks like the discussion on this bug explains that it's actually sort of fixed now)."
1799588,2019-08-08 02:31:16 UTC,"Change abandoned by Michael Moore (<email address hidden>) on branch: master
Review: https://review.opendev.org/613671
Reason: as mentioned by Brian, resolved in https://review.openstack.org/#/c/607353/"
1799588,2018-10-26 18:36:35 UTC,correct patch file for https://github.com/openstack/glance/pull/9
1799595,2018-10-25 02:22:11 UTC,Here's one confusing log:
1799595,2020-09-15 00:14:48 UTC,This is still happening:
1799595,2018-10-23 22:41:58 UTC,"Here is an example of the link pointing to an invalid directory:
https://pastebin.canonical.com/p/BX6TvDdWmK/"
1799599,2018-10-25 08:30:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613239"
1799599,2018-10-26 11:39:02 UTC,by definition a flat network should not have a vlan tag and therefor should not have a vlan_tci bit to set. ml2/ovs does not support vlan transparency so the guest should not be allowed to send a vlan tagged packet outside of the use of vlan aware vms.
1799599,2018-11-07 11:27:33 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/613239
Reason: as per Sean's comments it shouldn't be done this way"
1799601,2018-11-22 16:47:48 UTC,@Evan-
1799601,2018-11-22 15:40:04 UTC,So... the discussion above doesn't boil down to a single solution for me. But maybe I'm missing it.
1799601,2018-10-29 19:32:03 UTC,https://bugs.launchpad.net/kicad/+bug/1799601/+attachment/5206860/+files/Bildschirmfoto_2018-10-29_12-07-05.png
1799601,2018-10-29 18:50:21 UTC,"FWIW, my vote would be to not include TH parts in the .POS file.  I am to even sure we are using any assembly house which still has TH pnp machines (It is all done hand placement).  But if you do want to include them, it needs to be a box-check option at time of .POS creation ...   including TH parts in in the .POS file which is primary SMT will cause extra unneeded work and potential for introducing errors as those are removed/ignored."
1799601,2018-10-29 19:08:05 UTC,"From my conversation with Advanced Circuits, they need the XY for THT for their axial assembly process as well as the many radial forms.  Similar to these processes: [1][2]"
1799601,2018-10-28 04:31:05 UTC,I'm pretty sure that that still only works for footprints that have SMD pads.  The comments in the code indicate it is to export positions for footprints that are mislabeled but have SMD pads.
1799601,2018-10-27 21:00:09 UTC,"@Seth, I thought that's what the checkbox to include footprints if they have SMT pads was for or is this only available in the dev branch?"
1799601,2018-10-26 15:39:08 UTC,"I think we should have some options in the export here for users to choose what to include in the pos file.  I've had board houses (Advanced Circuits, e.g.) complain that through-hole components were not included.  Adding a simple group of checkboxes to include different types (including virtual) might fix this report."
1799601,2018-10-26 12:20:03 UTC,"I don't think the behavior has changed:
Only footprints with attribute ""surface mount"" (previously ""normal+insert"") are in .pos files."
1799601,2018-10-25 19:14:25 UTC,"@shack
I assume this is only about board fiducials and not component fiducials (which should be part of the footprint). Just to be clear."
1799601,2018-10-23 23:06:21 UTC,"I believe this is a library issue
these are made as virtual footprints, but should be SMD if they should show up in the pos file."
1799601,2018-10-29 15:03:29 UTC,"I'm not sure if allowing THT footprints in the position file makes sense.  This may just be one of those cases where the user has to change the footprint type from virtual to SMT to make sure it shows up in the position file.  In the case of this bug report, fiducials typically are virtual because they don't have a component that gets populated at the fiducial position.   Maybe the user is using the position files for something other than component pick and place."
1799613,2018-10-25 15:38:17 UTC,"Hello,"
1799613,2019-01-16 22:17:34 UTC,"No further information provided by reporter, hence unfortunately closing as WORKSFORME."
1799613,2018-10-26 01:58:51 UTC,"Cristian, please stop creating upstream bugs for other people."
1799613,2018-10-25 15:51:56 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799613,2018-10-25 15:48:31 UTC,Please attach your xorg log and dmesg output.  Can you bisect?
1799613,2018-10-25 15:38:58 UTC,"https://bugzilla.freedesktop.org/show_bug.cgi?id=108554
--
Cristian Aravena Romero (caravena)"
1799613,2018-10-25 15:09:10 UTC,"Please file an upstream bug at [1], Product: DRI, Component: DRM/amdgpu."
1799613,2018-10-25 13:29:03 UTC,Attached apport
1799613,2018-10-25 14:28:50 UTC,Where is that configured?
1799613,2018-10-25 14:06:36 UTC,Does `amdgpu.dc=0` help?
1799613,2018-10-25 11:29:35 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799613,2018-10-24 22:39:01 UTC,Linux blackbox 4.19.0-041900-generic #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
1799613,2018-10-24 13:53:19 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799613,2018-10-24 01:30:07 UTC,This change was made by a bot.
1799613,2018-10-25 14:46:33 UTC,I think that fixed it.
1799613,2018-10-24 00:11:15 UTC,Monitors: L24q-20
1799614,2019-04-29 03:06:49 UTC,Tested in 18.04 LTS (gnome-software 3.28.1-0ubuntu4.18.04.10). Screenshots and icons continue to show using new API.
1799614,2019-04-29 03:28:42 UTC,Tested in 19.10 (gnome-software 3.30.2-0ubuntu11). Screenshots and icons continue to show using new API.
1799614,2019-05-06 08:28:40 UTC,This bug was fixed in the package gnome-software - 3.30.2-0ubuntu11
1799614,2019-05-14 21:57:18 UTC,Tested gnome-software 3.20.5-0ubuntu0.16.04.12. Screenshots and icons continue to show using new API.
1799614,2019-05-14 08:01:11 UTC,"Hello Robert, or anyone else affected,"
1799614,2019-05-30 10:03:31 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.12
1799614,2019-04-29 01:41:10 UTC,gnome-software 3.20 actually has it's own implementation of the snapd communication code (snapd-glib evolved from that) so it doesn't need a version bump. It's only using a trivial amount of the snapd-glib code.
1799614,2019-05-06 08:28:47 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1799614,2019-04-25 13:57:23 UTC,"An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: ""Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.""."
1799614,2019-05-06 08:43:15 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.10
1799614,2019-04-25 13:42:40 UTC,"Hello Robert, or anyone else affected,"
1799614,2018-10-24 03:14:19 UTC,"Bionic patch is in https://gitlab.gnome.org/robert.ancell/gnome-software/tree/media-api-3-30, will forward port that to 3.32 and master when we're happy with it."
1799614,2018-11-20 01:40:08 UTC,Support in snapd in version 2.36 [1] which is not currently in any Ubuntu release.
1799614,2019-01-18 04:08:44 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu2
1799614,2019-01-18 21:34:48 UTC,"Hello Robert, or anyone else affected,"
1799614,2019-01-18 21:41:44 UTC,The upload of snapd-glib is a new upstream version of the package yet only this bug report is referenced in the changelog for it. Is there a special exception for new versions of snapd-glib that I'm not aware of?
1799614,2019-04-25 13:48:53 UTC,"Hello Robert, or anyone else affected,"
1799614,2019-02-08 19:33:41 UTC,"An upload of snapd-glib to cosmic-proposed has been rejected from the upload queue for the following reason: ""contains changes unrelated to the bug listed in the changelog; currently no SRU exception is approved.  Can be reuploaded as-is after an SRU exception is approved, or can be uploaded with just the changes for the bug you're proposing to fix, but in the meantime rejecting the upload rather than leaving it stalled in the queue.""."
1799614,2019-03-01 18:44:26 UTC,"An upload of gnome-software to cosmic-proposed has been rejected from the upload queue for the following reason: ""reuploading with different -v option to avoid listing LP: #1799614 which is *un*fixed in this version""."
1799614,2019-04-02 03:51:28 UTC,The pending SRU page (http://people.canonical.com/~ubuntu-archive/pending-sru.html) still shows this bug as blocking the SRU.
1799614,2019-01-30 22:26:26 UTC,"@brian-murray - there isn't a special exception, so I have written a proposal:
https://wiki.ubuntu.com/SnapdGlibUpdates"
1799614,2019-04-02 15:52:07 UTC,This bug was fixed in the package gnome-software - 3.30.2-0ubuntu10
1799619,2019-06-20 04:41:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799619,2020-02-16 12:56:13 UTC,python3-googleapi was updated to 1.7.11-2 in Ubuntu 19.10.
1799624,2020-01-21 16:09:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799624,2020-01-21 16:22:03 UTC,Also having this same error when trying to mount a share with a comma in it.
1799625,2018-11-06 16:25:32 UTC,Please see the linked Debian bug for the latest status on this.
1799627,2018-10-24 04:50:23 UTC,"Not pointing to a serial port, as it is now.  I should submit bug reports after I have coffee."
1799629,2018-11-03 00:33:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799631,2018-11-01 16:52:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799632,2018-10-24 09:02:38 UTC,"ejabberd 18.06 needs erlang-p1-zlib 1.0.4, which fails to build with:"
1799632,2018-10-24 19:51:51 UTC,The patch in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911789 allows building erlang-p1-zlib and ejabberd.
1799632,2018-11-17 18:04:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799637,2018-10-25 13:13:40 UTC,That's interesting. Thank you for making the videos. I am marking this as Low priority considering that the workaround is easy.
1799637,2018-10-25 09:37:14 UTC,"Be, you are right, it must have to do with the rendering of the waveforms. Now i know a bit more!! In order your instructions i tested in r6594 it with different preferences."
1799637,2018-10-24 17:32:43 UTC,"I doubt this will make a difference, but could you test the different options for the waveform renderer in the Waveforms section of the preferences with your computer running Ubuntu 18.04? Does this bug happen with all of them?"
1799637,2018-10-24 13:02:25 UTC,"Are you compiling Mixxx yourself or are you using the packages from the PPA? What GPU (graphics card) are you using on each computer? If you use an nVidia GPU, are you using nVidia's proprietary driver?"
1799637,2018-10-24 16:34:36 UTC,I use(ed) the latest beta-releases (now: 2.2 r6590) from the PPA. But this behavior i watched since qt5 in my own compiled test-versions also.
1799639,2018-10-26 21:55:54 UTC,"Reviewed:  https://review.opencontrail.org/47247
Committed: http://github.com/Juniper/contrail-controller/commit/63bc506e1fddb52f7ad483ca563df48d7a929fea
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1799639,2018-10-24 07:27:41 UTC,"Review in progress for https://review.opencontrail.org/47244
Submitter: Parth Sarupria (<email address hidden>)"
1799639,2018-10-24 08:45:02 UTC,"Review in progress for https://review.opencontrail.org/47247
Submitter: Parth Sarupria (<email address hidden>)"
1799640,2018-10-24 07:31:04 UTC,I can confirm that updating to (a backport of) erlang-p1-tls 1.0.25-2 from Debian fixes the problem (erlang-p1-utils 1.0.13-1 is needed as a build dependency).
1799642,2018-12-19 12:15:19 UTC,"Reviewed:  https://review.openstack.org/621709
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=1dacd1944e285ef70f60c7e9982fa2ab180b144e
Submitter: Zuul
Branch:    stable/queens"
1799642,2018-12-18 14:39:34 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/625930"
1799642,2018-12-18 07:13:50 UTC,"Reviewed:  https://review.openstack.org/624967
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=6258a920fdf8432f39696815765f3320afe92fca
Submitter: Zuul
Branch:    master"
1799642,2020-05-27 07:52:12 UTC,This bug is marked incomplete for tripleo. Please remove the milestone to stop the spam with each RC :)
1799642,2018-12-03 21:53:26 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/621709"
1799642,2018-11-27 07:29:37 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620238"
1799642,2018-11-27 07:25:20 UTC,"Reviewed:  https://review.openstack.org/612887
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=b06d8387f50ac9c536941ffddb00c5bdb45753b6
Submitter: Zuul
Branch:    master"
1799642,2018-10-24 06:52:24 UTC,"Some experiment in kolla with https://review.openstack.org/#/c/612887/, not sure if it would actually fix the issue."
1799642,2018-12-12 11:05:13 UTC,"Reviewed:  https://review.openstack.org/620238
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=e11c541b3f291c13c6ed553ef115fd74468dfc64
Submitter: Zuul
Branch:    stable/rocky"
1799642,2018-12-18 23:12:14 UTC,"Reviewed:  https://review.openstack.org/625930
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=fe7ff62f68689362799cc9147cd456dd633255fe
Submitter: Zuul
Branch:    stable/rocky"
1799645,2018-11-08 07:38:18 UTC,"I didn't get to take a screenshot (because I forget that I wrote this bug report), but I might have figured out when these visual bugs appear, and I might know how to recreate them; though it must be said, that are a bit random."
1799645,2018-11-08 07:48:20 UTC,"Marked it in red, as it can be a bit hard to see, but if you look closely, you can see it's there."
1799647,2018-10-24 08:20:03 UTC,"The attachment ""Add configuration for german provider winSIM"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1799647,2018-11-29 18:09:43 UTC,"hey,"
1799647,2019-04-20 18:13:22 UTC,"Unsubscribing sponsors, please submit this upstream first."
1799647,2019-04-21 09:11:28 UTC,"Submitted upstream:
https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info/merge_requests/7"
1799647,2019-08-14 05:42:19 UTC,I believe this is fixed in version 20190618-2.
1799655,2018-10-26 14:34:14 UTC,The package has been published and the bug is being set to Fix Released
1799655,2018-10-26 14:31:13 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1027.29
1799655,2018-10-25 16:20:38 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.15.0-1027.29/raspi2-4.15-proposed-published.html"
1799655,2018-10-25 09:03:02 UTC,Hardware Certification have begun testing this -proposed kernel.
1799657,2020-05-14 08:58:31 UTC,Thank you for reporting this bug to Ubuntu.
1799659,2018-11-01 07:45:26 UTC,And I use `do-release-upgrade` tool without arguments
1799659,2018-10-24 10:38:48 UTC,"Thank you for your bug report, from what version did you try to update and using what tool?"
1799659,2018-10-24 13:18:11 UTC,Thank you. Now I use Ubuntu Server 16.04
1799660,2018-11-14 11:24:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799660,2019-01-10 17:05:38 UTC,"Hello, I think this bug should be reported upstream! can you please do it?"
1799663,2018-10-24 09:21:48 UTC,Can you please attach a screenshot of the problem?
1799663,2018-10-24 10:00:13 UTC,Before adding padding: 0;
1799663,2018-10-24 10:00:52 UTC,After adding padding: 0;
1799663,2018-10-24 14:29:41 UTC,Patch for padding
1799663,2018-10-24 16:21:35 UTC,"The attachment ""Patch for padding"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1799669,2019-12-15 20:04:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799674,2019-07-18 23:08:58 UTC,"I believe this commit should close this bug, correct?"
1799674,2019-07-19 09:03:08 UTC,This does indeed look good like a massive improvement.
1799674,2020-10-29 07:23:09 UTC,A fix of the comment is here: https://github.com/canonical/cloud-init/pull/635
1799674,2018-10-25 20:50:08 UTC,The standard way for FreeBSD folks to build packages is to:
1799674,2018-10-25 17:24:03 UTC,"Igor,
Thanks!"
1799675,2018-10-24 11:52:44 UTC,Upstream MP: https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/260
1799675,2018-11-12 14:46:32 UTC,"Upstream doesn't want to fix the obvious problem because they disagree g-c-c should be used outside out of GNOME, unassigning/setting back to triaged since we don't want to enter into arguing about that"
1799679,2019-02-22 06:03:11 UTC,"Yeah, it seems to be a general type of OpenGL application."
1799679,2020-11-13 05:47:33 UTC,"Possibly related: ""OpenGL yield behavior"" in http://us.download.nvidia.com/XFree86/Linux-x86_64/455.38/README/openglenvvariables.html"
1799679,2019-02-22 05:49:56 UTC,"I don't think it affects just glxgears, I experience it with pretty much any app that utilizes opengl, like Chromium or any Electron-based app like Slack or Discord."
1799679,2018-10-29 09:58:45 UTC,A video showing the lag.
1799679,2018-10-25 07:04:46 UTC,Workaround:
1799679,2018-10-24 11:21:13 UTC,Xorg profile of when I was just moving the glxgears window.
1799679,2018-10-24 11:17:09 UTC,Bug confirmed in two separate window managers so far:
1799679,2019-02-20 06:30:25 UTC,The bug is also in nvidia-410.93 and nvidia-418.30 :(
1799683,2019-04-30 08:48:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656469"
1799683,2019-04-30 08:49:15 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656470"
1799683,2019-05-10 16:16:32 UTC,This issue was fixed in the openstack/heat-translator 1.3.1 release.
1799683,2019-05-16 09:28:10 UTC,"Reviewed:  https://review.opendev.org/656469
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=1fe295ca88c73cd3eeec55cb671b1d5a99ac0701
Submitter: Zuul
Branch:    master"
1799683,2019-05-17 09:11:42 UTC,"Reviewed:  https://review.opendev.org/656470
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=aee46c86bbe87cbb8b6ebb3bd9b765aafd13df53
Submitter: Zuul
Branch:    stable/stein"
1799683,2019-06-14 20:22:02 UTC,This issue was fixed in the openstack/heat-translator 1.4.0 release.
1799683,2019-09-27 08:55:00 UTC,This issue was fixed in the openstack/tacker 2.0.0.0rc1 release candidate.
1799683,2020-02-14 22:49:15 UTC,This issue was fixed in the openstack/python-tackerclient 1.0.0 release.
1799684,2020-04-23 20:08:10 UTC,New installer is out.
1799684,2019-04-23 12:46:41 UTC,The project entry is still in status 'Fix Committed' and will be changed to 'Fix Released' once subiquity is the default installer (for s390x).
1799684,2019-04-23 12:48:25 UTC,"------- Comment From <email address hidden> 2019-04-23 08:44 EDT-------
The installer part will come with 19.10. Therefore changed target Release"
1799684,2019-04-23 12:21:14 UTC,"This is already done in subiquity installer (which itself is not out yet).
This is not done in the current d-i based installer (which is the default installer at the moment)."
1799684,2019-06-28 07:49:20 UTC,"------- Comment From <email address hidden> 2019-06-28 03:48 EDT-------
IBM Bugzlla status -> closed, Fix Released for Eoan"
1799686,2020-07-06 07:08:58 UTC,It's seems like there is a progress on getting Qualcomm Venus decoder works on Snapdragon-based laptops so this feature could be useful for these laptops too: https://github.com/bm16ton/yoga-c630-linux-kernel
1799686,2019-02-16 09:14:36 UTC,"I asked on the pi forum if they could help with the upstream bug report https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=233552 .  I like the pi, but the people that make it are obnoxious.  They are not going to help."
1799686,2019-01-13 07:21:26 UTC,Please also ensure there is an upstream bug report for this problem in:
1799686,2019-01-13 07:19:29 UTC,That's a good point. If a single component needs multiple different fixes like separate ones for desktop and Pi then separate bugs are really required.
1799686,2019-01-11 16:29:47 UTC,My concern is that v4l2 will be forgotten about on the other bug report.  Va-api won't work on the pi.
1799686,2019-01-10 13:44:02 UTC,"I believe, although bug #1424201 is assigned to *chromium-browser*, it is too general, as it also mentions and links to Mozilla bug reports. Therefore, that one should be closed or treated as a “tracking report” – if Launchpad allows that, and individual reports should be created for each browser."
1799686,2019-01-09 18:52:35 UTC,There is already a bug for vaapi - bug 1424201
1799686,2019-01-11 01:29:37 UTC,One of the benefits of Launchpad over other bug trackers is that we can spread a single bug over multiple components. And those different components have different Status values within a single bug. Bug 1424201 does that.
1799686,2019-01-09 09:14:34 UTC,"Vaapi is not the only mechanism that can be used for hardware decode.  V4l2 is an alternative, the one that will be used on the raspberry pi with the open source vc4 driver (see blog posts https://anholt.github.io/twivc4/2018/02/12/twiv/ ).  I believe there is some communication between chromium and the pi makers about implementing this, but I am doubtful this will make it upstream."
1799686,2019-01-09 11:42:41 UTC,"Daniel, should we fill separate bugreport regarding VA-API? Or, perhaps, if you understand situation better, you can fill it?"
1799686,2019-01-08 06:26:01 UTC,Fedora developers enabled video decoding in their builds. Is anyone from Canonical can comments on this?
1799686,2019-01-08 06:26:06 UTC,https://src.fedoraproject.org/rpms/chromium/c/278c62709d1dba5883c3b69047706837bb402bd7?branch=master
1799686,2019-01-08 06:26:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799686,2019-01-10 02:27:46 UTC,Thanks for the information all.
1799686,2019-01-09 03:56:21 UTC,"V4L2 doesn't have anything to do with video decoding that I know of, but maybe ARM is different..."
1799686,2019-01-08 08:42:05 UTC,"You meant VAAPI, not v4l2 , isn't it ?"
1799686,2019-01-09 04:10:37 UTC,"More information about VP9 and other decoding in V4L2:
https://linuxtv.org/downloads/v4l-dvb-apis/uapi/v4l/extended-controls.html"
1799686,2019-01-09 04:04:40 UTC,Seems both statements are true :)
1799689,2020-05-08 06:44:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/726289"
1799689,2020-05-23 13:38:25 UTC,"Reviewed:  https://review.opendev.org/726289
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=fbc47e60e1ce0f371c3f9e4350d5581c98d7b393
Submitter: Zuul
Branch:    master"
1799689,2020-05-23 13:43:29 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/730455"
1799689,2020-05-23 16:46:14 UTC,"Reviewed:  https://review.opendev.org/730455
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=aea9b4d23367d4d0d8094f49584b537f13b86c6c
Submitter: Zuul
Branch:    stable/ussuri"
1799689,2020-05-25 07:51:32 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/730568"
1799689,2020-05-25 18:30:14 UTC,"Reviewed:  https://review.opendev.org/730568
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=eccb6806cc9e8767e443ecb4faea4cdfbf06f633
Submitter: Zuul
Branch:    stable/train"
1799689,2020-06-12 17:04:20 UTC,"Hello, I was also experiencing this problem as well. I applied the patches listed here: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=eccb6806cc9e8767e443ecb4faea4cdfbf06f633 and it resolved the issue for my deployment. It also seems to have resolved another issue I was having with the Kibana dashboard was not displaying when I hit port 5601 on the external_vip_address. My deployment is stable/train on CentOS 8 and is an all-in-one deployment. If you have anything else you want me to check in regards to the patches, feel free to let me know. Thanks."
1799689,2020-06-16 09:38:43 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/735839"
1799689,2020-06-28 11:13:03 UTC,"Reviewed:  https://review.opendev.org/735839
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=f1ce8737025cee8a92b7efe00f8363833f8d6f1f
Submitter: Zuul
Branch:    stable/stein"
1799689,2020-05-08 06:16:49 UTC,i am facing the same problem and the log is https://raw.githubusercontent.com/albertjone/issue-attachments/master/kolla-ansible/issue-1799689/task_faile_log
1799690,2018-11-12 15:42:19 UTC,"https://review.openstack.org/#/c/613588/ fixed the dependency issues, and https://review.openstack.org/#/c/616677 will ensure that installing tripleo-quickstart would not pull in numpy, which is now an extra as it's only used for CLI cases to compare results."
1799690,2018-11-12 16:47:08 UTC,"Reviewed:  https://review.openstack.org/616677
Committed: https://git.openstack.org/cgit/openstack/browbeat/commit/?id=03be4251029281228f92d355bdb146be3d9ae048
Submitter: Zuul
Branch:    master"
1799694,2019-07-26 23:30:45 UTC,This is a confirmed bug waiting for a contributor. Are you able to jump in here?
1799694,2019-07-26 20:42:17 UTC,I wish this is not future in wishlist.
1799694,2018-10-24 16:16:38 UTC,"This civers the exporte side:
https://bugs.launchpad.net/bugs/1799441"
1799694,2018-10-24 17:25:46 UTC,"I couldn't understand what you mean by ""dj rate"" but I'm talking about my own ratings."
1799694,2018-10-24 16:17:54 UTC,Which rating do you express with the embedded rating? Is it you personal rate or the DJ rate?
1799694,2018-10-28 11:13:38 UTC,I would like to have a personal rating. If you mean  DJ rating is what audience like to hear.
1799697,2019-03-14 18:32:54 UTC,"ubuntu@lp1799697-c:~$ dpkg -l | grep knockd
ii  knockd                          0.7-1ubuntu1                        amd64        small port-knock daemon
ubuntu@lp1799697-c:~$ sudo systemctl enable knockd
Synchronizing state of knockd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable knockd
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl."
1799697,2019-03-21 10:29:32 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu1.18.04.1
1799697,2019-03-21 10:18:56 UTC,"The verification of the Stable Release Update for knockd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1799697,2019-03-21 10:18:56 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu1.18.10.1
1799697,2019-03-14 11:34:25 UTC,"Build armhf (knockd_0.7-1ubuntu1.18.04.1_armhf.deb) works without issue, thanks"
1799697,2019-03-13 20:12:01 UTC,"Hello Zeta, or anyone else affected,"
1799697,2019-03-12 17:23:16 UTC,"Many thanks!!!!!
Kind regards."
1799697,2019-03-12 16:16:39 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu2
1799697,2019-03-12 15:37:32 UTC,Sponsored in development release (disco).
1799697,2019-03-10 16:41:30 UTC,test pkgs at https://launchpad.net/~ddstreet/+archive/ubuntu/lp1799697
1799697,2019-03-10 15:06:58 UTC,"marked invalid for t/x since upstart is used in those releases, not systemd, and this affects only systemd-controlled knockd."
1799697,2018-10-24 13:17:37 UTC,Seems the same as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868015
1799697,2019-01-23 10:14:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799697,2019-03-13 20:10:24 UTC,"Hello Zeta, or anyone else affected,"
1799702,2018-10-24 14:53:35 UTC,"I discussed with slangasek, who said:"
1799705,2019-02-12 13:52:27 UTC,Is it still an issue?
1799711,2019-06-10 18:34:24 UTC,"There are significant changes required to support Distributed Cloud in stx due to the containerized environment. Based on discussion with the Distributed Cloud PL, Dariush Eslimi, we agreed to close old Distributed Cloud bugs as Won't Fix. A full test cycle will be needed to verify the new implementation and new bugs can be opened for the issues reported then."
1799711,2018-10-24 17:30:56 UTC,Low priority issue as the user is able to re-connect. Fix is best effort; no specific target release.
1799713,2019-03-07 19:10:36 UTC,See bug #1763100 for the solution.
1799713,2019-03-07 20:22:01 UTC,"The attachment ""console-setup-1.178ubuntu9-JNZ-1.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1799714,2020-11-16 08:06:30 UTC,Zero crashes after 19.04 so consider it fixed.
1799714,2018-11-16 01:49:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799718,2018-11-04 10:16:18 UTC,apport information
1799718,2018-11-04 10:24:33 UTC,"Seems to be crashed !
Something blocks apport information...."
1799718,2018-11-05 23:27:32 UTC,"It's an ACPI bug !
I make a bad thing about AMD While trying to correct colour resize
So, on recovery mode... Cleaning remove all files.
I try to install 18.10 on UEFI mode ... crash
I try to install Ub 17.10 UEFI mode.... Crash
I try to install 16.04.5 UEFI mode crash too ....
PC says error ACPI core...."
1799718,2018-11-05 23:52:05 UTC,"Propriétés de la table ACPI
Signature ACPI	APIC
Table de description	Multiple APIC Description Table
Adresse Mémoire	00000000-7A712800h
Longueur de la table	188 octets
OEM ID	_ASUS_
OEM Table ID	Notebook
OEM Revision	01072009h
Creator ID	AMI
Creator Revision	00010013h
Local APIC Address	FEE00000h"
1799718,2018-11-04 10:16:16 UTC,apport information
1799718,2018-11-06 18:04:29 UTC,"For info,"
1799718,2018-11-08 00:24:28 UTC,IT'S   A problem of
1799718,2018-11-15 10:10:33 UTC,"HIE,"
1799718,2018-11-15 10:14:22 UTC,"On forum, I saw that Bugs is on AMD with NVidia GEForce 1050 !!!!"
1799718,2018-11-05 23:56:04 UTC,"There is a problem here...
UEFI	Système compatible UEFI Microsoft
PNP0C02	Thermal Monitoring ACPI Device
PNP0C02	Thermal Monitoring ACPI Device
PNP0C02	Thermal Monitoring ACPI Device
PNP0C02	Thermal Monitoring ACPI Device
PNP0C02	Thermal Monitoring ACPI Device
PNP0C02	Thermal Monitoring ACPI Device
THERMALZONE	Zone thermique ACPI"
1799718,2018-11-04 10:16:12 UTC,apport information
1799718,2018-11-04 10:15:59 UTC,apport information
1799718,2018-11-04 10:16:10 UTC,apport information
1799718,2018-10-24 15:14:48 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799718,2018-11-04 10:16:11 UTC,apport information
1799718,2018-10-24 22:11:05 UTC,"Sorry,"
1799718,2018-11-04 10:14:14 UTC,"Hie, Too much bugs to restart pc. Finally after format hard disk, impossible to install Ubuntu 18.04...
My PC : ASUS ROG GL753VD. Notebook . Bios change version (307)... No possibility to put a bootable usb on CSM mode... Only EFI permiss. To restart, I put Ubuntu 16.04 EFI, then upgrade with ubuntu 18.04.1 and then bug !!! Black screen and problem with ACPI temp sensors... See attachment words.... To restart, Recovery start/ Clean and remove all fills proposed, Then dkpg repair. Then resume and black screen obtained !
Restart and Ubuntu 18.04 gone in bad quality.... Then, upgrade on Ubuntu 18.10.  Seems correct but many fonction don't work !  (colour of screen (fade and white cloud... no contrast, saturation can be used) Driver AMDNVidia correct (390), virtualbox (I am looking on forum to see more...)).
This way ubuntu 18.10 is correctly installed. He asked me a new password to bios enter...
I think that is a problem of EFI and secure boot management... And too bugs with sensors use. I don't find where is fan sensor..."
1799718,2018-11-04 10:16:01 UTC,apport information
1799718,2018-11-04 10:15:57 UTC,apport information
1799718,2018-11-04 10:16:04 UTC,apport information
1799718,2018-11-04 10:16:06 UTC,apport information
1799718,2018-11-04 10:16:08 UTC,apport information
1799718,2018-11-04 10:16:07 UTC,apport information
1799718,2018-11-04 10:16:02 UTC,apport information
1799719,2018-11-04 11:54:09 UTC,"Reduced to
(typep 10 '(or (cons (or fixnum vector (member a ""b"")))
               (cons (or (and (not vector) array) (and (not integer) number)) number)))"
1799727,2018-10-26 01:02:42 UTC,"Reviewed:  https://review.openstack.org/613115
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=45f36cebabdbaad10e69c1a99f5ad4f091885f82
Submitter: Zuul
Branch:    master"
1799727,2019-03-22 03:46:24 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1799727,2018-12-19 10:01:33 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1799727,2018-12-07 18:11:21 UTC,"Reviewed:  https://review.openstack.org/614564
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=26c5ee100fb7d75721355878ade9167ff88a70e6
Submitter: Zuul
Branch:    stable/rocky"
1799727,2018-12-07 18:11:09 UTC,"Reviewed:  https://review.openstack.org/614563
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=57ca9288ce33550b73deee22ca902cc35f2b4819
Submitter: Zuul
Branch:    stable/rocky"
1799727,2018-10-31 18:38:31 UTC,"Reviewed:  https://review.openstack.org/613991
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4e3616b562647ea140f6f67d1bf888f562b4b6d7
Submitter: Zuul
Branch:    master"
1799727,2018-10-31 18:32:57 UTC,"Reviewed:  https://review.openstack.org/613126
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ca279c68a54b054cb54d45ee9d2eed8ade9a6db5
Submitter: Zuul
Branch:    master"
1799727,2018-10-31 15:50:49 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614564"
1799727,2018-10-31 15:50:31 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614563"
1799727,2018-10-24 17:26:38 UTC,"I was looking at https://github.com/openstack/nova/blob/835faf3f40af6b0e07c585690982a997d6a2ac47/nova/compute/provider_tree.py#L128 incorrectly, that will return True from has_inventory_changed if the keys are different, meaning we don't need to check the values, which is correct."
1799727,2018-10-24 17:54:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613126"
1799727,2018-10-24 17:41:31 UTC,OK I think this is the regression:
1799727,2018-10-24 17:22:59 UTC,I guess this shouldn't be a problem in queens because the resource tracker didn't use that provider tree to report back the inventory changes:
1799727,2018-10-24 17:20:28 UTC,I believe the bug is right here:
1799727,2018-10-24 17:10:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/613115"
1799727,2018-10-24 17:08:21 UTC,"I have a recreate in a functional test, will push it up shortly."
1799727,2018-10-24 16:24:39 UTC,"Sorry, I'm using 18.0.1"
1799727,2018-10-24 16:02:05 UTC,"""OpenStack 14"" is a RHOSP vendor product version - what is the actual upstream release you're testing against? 18.0.0 (Rocky GA)? 18.0.2 (latest stable/rocky release)?"
1799727,2018-10-29 16:57:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/613991"
1799736,2018-12-10 19:57:36 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1799736,2018-12-10 19:57:25 UTC,This bug was fixed in the package livecd-rootfs - 2.408.41
1799736,2018-12-10 18:23:50 UTC,"I said, ""it should be a package dependency for livecd-rootfs based on this testing"" but now that I look at the traceback it's the case that python3-ubuntu-image is using 'sudo' but does not depend on it.  So I'd say that maybe this SRU can be marked verification-passed but ubuntu-image source needs a bug files to add 'sudo' to its dependencies."
1799736,2018-12-10 18:31:24 UTC,New bug #1807750 filed against ubuntu-image for the sudo dependency.  Marking this as verification-done to unblock other SRUs and because the change introduced by this SRU does allow for building of core16 images using the steps outlined in the test case (and in the buildds once ubuntu-image is fixed).
1799736,2018-10-31 12:00:00 UTC,"This is now uploaded to xenial. Please note that some of the changes have not yet been released into bionic - but that's intended. I would like to request that the xenial livecd-rootfs of this SRU land first, before we prepare bionic. The reason for that is that currently, thanks to bionic missing these changes, we can use this series to temporarily build core16 images. Otherwise we'd have no easy way of doing that before the xenial livecd-rootfs fully migrates into updates (and right now that's still needed)."
1799736,2018-12-10 18:12:23 UTC,I have tested on amd64 with livecd-rootfs 2.408.41 from -proposed following the test case in the description.  My testing diverged from the test plan in that I am driving livecd-rootfs with ubuntu-old-fashioned[1] which builds with launchpad-buildd tools in a lxd container to replicate the buildd environment.  In this environment the build fails due to the lack of 'sudo':
1799736,2018-10-25 11:21:44 UTC,"The xenial SRU will require an MIR for ubuntu-image, as it's still in universe in that suite."
1799736,2018-11-27 15:58:16 UTC,"Hello Łukasz, or anyone else affected,"
1799736,2018-10-26 07:07:33 UTC,"I wasn't able to find the bug report for python3-voluptuous, but I've promoted this now."
1799736,2018-10-26 17:53:39 UTC,I promoted both pyparted and ubuntu-image to main on xenial right now.
1799737,2018-10-24 22:49:25 UTC,I guess you upgraded from an original neutron 8 config to queens. In queens external_network_bridge has been deprecated and should not be used (Using this will result in incorrect port statuses).
1799737,2020-03-27 11:53:17 UTC,@hopem I think it got installed as Pike but with old charm config options used.
1799737,2020-03-27 11:18:35 UTC,@axino I assume the environment you have that is using external_network_bridge/external_network_id is quite old and was originally deployed with a version older than Queens? Using these option to configure external networks is really deprecated and since at least Juno we have used bridge_mappings for this purpose (and to allow > 1 external network). There is an annoying quirk here though (and perhaps this is why you have not switched) which is that with the old way the network will likely not have a provider name (in the db) and therefore migrating it as-is to a bridge_mappings type config will break the network (unless perhaps one can be set manually in the database).
1799737,2020-03-27 11:05:37 UTC,@slaweq the bug description says this issue was observed in Queens which is currently under Extended Maintenance so presumably still eligible for fixes if there is sufficient consensus on their criticality and enough people to review. We also need to consider upgrades from Q -> R -> S where people are still using this config.
1799737,2020-03-27 11:35:25 UTC,Does feel like the code change in https://review.opendev.org/#/c/564825/10/neutron/agent/l3/router_info.py could be reverted though since it only affects the legacy config and is also breaking it.
1799737,2019-07-09 05:11:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799737,2018-11-19 11:05:35 UTC,"The charm appears to do the right thing, it marks the feature as ""deprecated"" but properly configures it whenever asked."
1799737,2018-11-05 14:03:24 UTC,"Hi Junien,"
1799737,2018-10-26 17:40:41 UTC,"This cloud is indeed upgraded from pike, and using juju charms - said charms still offer the option to set external_network_bridge, although the option is clearly marked as ""deprecated""."
1799737,2019-07-09 07:15:08 UTC,"Hi,"
1799742,2020-04-15 13:34:49 UTC,More discussion on the #openstack-manila IRC channel on Freenode:
1799742,2020-04-15 14:13:38 UTC,Using: Netapp drive (vlan support) as dhss true!
1799742,2020-04-08 17:19:51 UTC,"I was able to reproduce the bug using the Netapp drive with multi-segmentation.  Enabling the segments extension in neutron.conf and creating the net, segments and subnets as described. Then, creating the 3 manila share-network with its shares. Showing the share-network the ""segmentaion_id"" is set as same value for all of them!"
1799742,2020-04-14 21:51:16 UTC,More discussion on the bug happened on the #openstack-manila channel on Freenode:
1799742,2019-12-02 09:01:25 UTC,"Jason, I am not sure what is the change required here. Should segmentation_id be a list so that all the segment IDs will be appended to it or any other modification is required. It will be helpful if I receive a suggestion on this."
1799742,2019-10-24 14:59:32 UTC,Sneha is there any update to this bug?
1799742,2020-03-05 15:44:36 UTC,Revisted see http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-03-05-15.00.log.html
1799742,2019-03-29 18:53:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648755"
1799742,2019-03-13 18:18:03 UTC,"I would like to work on this issue,  what is the expected change in the code?"
1799744,2018-10-24 16:15:32 UTC,Having a look at the corosync logs on the overcloud node [1]
1799749,2019-02-25 15:09:34 UTC,I have also seen this in a customer deployment.
1799749,2020-03-06 14:39:28 UTC,"FTR, forcing the units to restart should clear the status, when it gets stuck :"
1799766,2018-10-25 15:46:23 UTC,"Hi,"
1799766,2018-10-25 17:30:39 UTC,"Yes, I messed up with `-device`, because I initially tried to do it with `-device`, later rely only on automatically created device, and so had automatically created devices."
1799767,2018-11-01 21:41:16 UTC,"Since your dist-upgrade logs also show that you had shim-signed 1.34.9.2 installed since September 23 and the problem only occurred for you after the upgrade on October 11, I'm provisionally marking this as a regression-update due to the apparent connection to shim-signed 1.37~18.04.2+1533136590.3beb971-0ubuntu1."
1799767,2018-11-02 19:25:23 UTC,"Dear Steve,"
1799767,2018-11-01 21:27:27 UTC,"Ok.  Crucially, this shows that you have the 1.37~18.04.2+15+1533136590.3beb971-0ubuntu1 version of shim-signed installed, which was released on October 11 to bionic-updates; superseding version 1.34.9.2 which was there previously."
1799767,2018-11-03 19:24:48 UTC,"Oh my god, that is really a strange behavin. As you said, I entered that mokutil command and rebooted the system, entered BIOS. I enabled CSM, saved the config and rebooted. In the attachment you see the message from shim after BIOS splash screen. But what happened then?
Suddenly I saw the grub menu and after 10 secs ubuntu starts automagically in secure boot mode. I didn't believe that. Thought I had made a mistake. So I switched off verbosity and rebooted. But, and that's surprising, I did not saw any grub menu, just the black screen as before.
So I had to boot into BIOS, set CSM to ""auto"" and reboot. And I did it again, just to verify this. I switched verbosity on, rebooted, enabled CSM, rebooted again and I have seen the grub menu. Ubuntu starts automagically in secure boot mode."
1799767,2018-11-02 20:44:23 UTC,Could you please test the following:
1799767,2018-10-31 21:27:00 UTC,apport information
1799767,2018-11-02 20:45:14 UTC,"Advice from @cyphermox is to actually record the screen rather than taking a picture, in case the messages appear/disappear quickly."
1799767,2018-10-31 21:26:58 UTC,apport information
1799767,2018-10-31 21:26:57 UTC,apport information
1799767,2018-10-26 19:15:11 UTC,"Output of apport-collect now is
...
Package shim-signed not installed and no hook available, ignoring
Gtk-Message: 21:00:40.534: GtkDialog mapped without a transient parent. This is discouraged
..."
1799767,2018-10-26 15:58:16 UTC,"apologies, it looks like we may only have the hook for the shim-signed source package.  Could you please run apport-collect 1799767 once more?"
1799767,2018-10-26 15:11:06 UTC,apport information
1799767,2018-10-26 15:11:05 UTC,apport information
1799767,2018-10-26 05:17:20 UTC,"Please run apport-collect 1799767 on the affected system, so we can gather the information that is relevant to the shim package, rather than for ubuntu-release-upgrader."
1799767,2018-10-31 21:26:59 UTC,apport information
1799776,2020-09-04 08:13:37 UTC,"Somewhat more importantly, it looks like we should actually carry python-barbicanclient in the UCA for Rocky? The source package has 4.7.0 in the stable/rocky branch; however, the UCA doesn't seem to have any python-barbicanclient between mitaka and queens."
1799776,2020-09-04 12:49:35 UTC,"Seeing as we don't have python-barbicanclient in the rocky uca and rocky is EOL, I think we can close this."
1799779,2018-10-25 16:15:41 UTC,"marking this as 'fix-released' on xenial, it is not a problem there as there is a 'zfs' (virtual) package"
1799779,2019-05-10 18:07:40 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1799779,2019-01-17 17:52:21 UTC,Looking closer at Ubuntu releases:
1799779,2019-01-25 17:46:38 UTC,"This bug is fixed with commit c283321b to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=c283321b"
1799779,2019-01-18 23:05:23 UTC,Fix is awaiting approval in my branch.
1799779,2019-01-28 21:56:43 UTC,This bug was fixed in the package cloud-init - 18.5-17-gd1a2fe73-0ubuntu1
1799782,2018-10-24 20:39:44 UTC,"Looking in
http://docs.kicad-pcb.org/5.0.0/en/pcbnew.html#_left_hand_side_toolbar
is the  ""Display footprint rats nest dynamically as it is moved."" removed or just forgotten somehow?"
1799782,2018-10-24 20:59:27 UTC,It's always on in GAL.
1799788,2019-12-16 15:19:14 UTC,"I'm not sure i understand what you mean here, since /boot/config-* file is part of linux-modules-$ver-generic since Xenial (i didn't check before that): perhaps you wanted the kvm flavour to be an exception by shipping /boot/config has part of linux-image? And why in that case?"
1799788,2019-12-16 16:25:58 UTC,"Ok, disregard my previous comment: config file was  part of linux-image until kernel signing was implemented - nonetheless, nowadays linux-image generic doesn't ship the config file anymore - any reason why you don't install linux-modules? Is this issue still relevant?"
1799790,2018-10-25 15:55:31 UTC,"We can probably just re-open 1792472, but I am working on tracking down why this is still failing, associated port seems to still be in BUILD state."
1799791,2019-05-14 10:30:09 UTC,We are applying these changes on linux-kvm only for Cosmic and Disco for now. If they don't cause any problems (e.g. boot speed increase) we will apply later also for the older series.
1799791,2019-08-13 12:06:19 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1054.61
1799791,2019-06-09 16:54:50 UTC,This bug was fixed in the package linux-kvm - 5.0.0-1007.7
1799791,2019-06-04 11:26:15 UTC,This bug was fixed in the package linux-kvm - 4.18.0-1013.13
1799791,2019-06-04 11:15:51 UTC,This bug was fixed in the package linux-kvm - 5.0.0-1007.7
1799791,2019-08-13 11:37:53 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1042.42
1799791,2018-10-25 18:57:20 UTC,Could you re-apply the KEXEC config changes to the linux-kvm tree build?
1799791,2018-10-25 23:57:14 UTC,The CONFIG_KEXEC and CONFIG_KEXEC_FILE config options are already enabled for the linux-kvm repo.  Here is a grep of the config directory:
1799791,2018-10-24 22:32:31 UTC,I built a test kernel from the linux-kvm repo.  This repo already has those two options enabled:
1799791,2019-04-23 17:42:34 UTC,"At first glance it looked like these options were enabled for linux-kvm because they showed up as being set to ""yes"" under the ""debian.master/config/config.common.ubuntu"" file. However, my grepping was too narrow because grepping for ""CONFIG_KEXEC="" didn't show the following lines:"
1799791,2018-10-25 17:08:45 UTC,"Sure, I'll take a look and build a new kernel."
1799791,2018-10-25 16:39:19 UTC,"The virtio configuration in this new kernel build changed, can it get reverted to what the -kvm kernel currently has?"
1799791,2018-10-25 18:22:45 UTC,"I posted another test kernel built using the linux-kvm tree, with no changes made."
1799792,2019-10-31 23:22:38 UTC,Also happens on Ubuntu 19.10
1799792,2020-11-13 16:03:30 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1799792,2020-11-13 18:10:36 UTC,Still happening in QEMU 5.1.0
1799792,2020-11-18 15:32:58 UTC,"I have the same issue, but unfortunately I cannot work around it: gl=off doesn't work with vfio-display-dmabuf, and sdl segfaults when the guest OS tries to enter GUI."
1799792,2020-11-18 16:06:44 UTC,unset GDK_SCALE GDK_DPI_SCALE works for me. It was GDK_SCALE=2 GDK_DPI_SCALE=0.5 as KDE would have set.
1799795,2020-07-24 17:20:23 UTC,Has this been reported upstream to NetworkManager? We're experiencing this with one of our modems with NetworkManager 1.18.
1799795,2018-10-26 17:18:19 UTC,@alfonso
1799795,2018-10-26 16:54:05 UTC,I would say that in general the cellular connection MTU is negotiated:
1799795,2018-10-26 16:57:59 UTC,"Also, note that MTU is a read-only property in MM's bearer:"
1799796,2018-10-26 21:26:13 UTC,I started Java game and freeze. Mouse and Key board not responds.
1799796,2018-10-28 18:15:16 UTC,loading occurred for the third time.
1799796,2019-10-25 05:31:35 UTC,It sounds like you're reporting two problems:
1799796,2019-12-25 04:17:18 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1799796,2018-10-25 03:06:14 UTC,Please:
1799807,2018-10-24 21:54:49 UTC,"For whatever it's worth: I wouldn't mind spending a bit of time trying to set up https://python-apt.readthedocs.io/ based on the git repository at https://git.launchpad.net/ubuntu/+source/python-apt, although I can't tell if this plan will actually work without trying it (for example I don't know if the dependencies of the documentation build will be available in the RTD environment)."
1799811,2020-08-04 16:33:43 UTC,"I remember this was once a problem, but I am pretty sure this problem was fixed somewhere during 1.7-development. I tested it right now on Ubuntu 18.04 with Pinta-1.7-latest-development-build and this problem does not appear anymore, but I am sure in Pinta 1.6 this was unbearable slow."
1799832,2019-03-09 15:18:19 UTC,"douglas@godlike:/usr/bin$ sudo torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.9
https://github.com/micahflee/torbrowser-launcher
Refreshing local keyring...
Keyring refreshed successfully...
  No key updates for key: EF6E286DDA85EA2A4BA7DE684E2C6E8793298290
Downloading and installing Tor Browser for the first time.
Downloading https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
Latest version: 8.0.6
Downloading https://dist.torproject.org/torbrowser/8.0.6/tor-browser-linux64-8.0.6_en-US.tar.xz.asc
Downloading https://dist.torproject.org/torbrowser/8.0.6/tor-browser-linux64-8.0.6_en-US.tar.xz
Verifying Signature
Extracting tor-browser-linux64-8.0.6_en-US.tar.xz
Running /home/douglas/.local/share/torbrowser/tbb/x86_64/tor-browser_pt-PT/start-tor-browser.desktop
Unhandled Error
Traceback (most recent call last):
  File ""/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py"", line 964, in dispatcher
    return func(*args, **kwargs)
  File ""/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py"", line 1532, in _finishResponse_WAITING
    self._giveUp(Failure(reason))
  File ""/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py"", line 1585, in _giveUp
    self._disconnectParser(reason)
  File ""/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py"", line 1573, in _disconnectParser
    parser.connectionLost(reason)
--- <exception caught here> ---
  File ""/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py"", line 560, in connectionLost
    self.response._bodyDataFinished()
  File ""/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py"", line 964, in dispatcher
    return func(*args, **kwargs)
  File ""/usr/lib/python2.7/dist-packages/twisted/web/_newclient.py"", line 1220, in _bodyDataFinished_CONNECTED
    self._bodyProtocol.connectionLost(reason)
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 364, in connectionLost
    self.all_done(reason)
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 383, in response_finished
    self.run_task()
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 299, in run_task
    self.run_task()
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 305, in run_task
    self.verify()
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 563, in verify
    self.run_task()
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 309, in run_task
    self.extract()
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 600, in extract
    self.run_task()
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 313, in run_task
    self.run()
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 616, in run
    if not self.check_min_version():
  File ""/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py"", line 604, in check_min_version
    for line in open(self.common.paths['tbb']['changelog']).readlines():
exceptions.IOError: [Errno 2] Arquivo ou diretório inexistente: '/home/dougla..."
1799832,2019-03-09 15:16:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799834,2020-03-07 11:26:27 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1799843,2018-10-25 22:00:44 UTC,Looks like chassis* and sys* are a little wonky. This is an Intel NUC btw.
1799843,2018-10-29 23:07:23 UTC,PR for fix: https://github.com/CanonicalLtd/landscape-client/pull/58
1799843,2019-12-04 23:24:27 UTC,This bug was fixed in the package landscape-client - 19.12-0ubuntu1
1799843,2018-10-24 23:55:02 UTC,For reference:
1799843,2018-10-25 21:06:38 UTC,"Thanks for filing the bug, please can you attach files in /sys/class/dmi/id/ matching '*vendor' e.g. ""sys_vendor"", ""chassis_vendor"", ""bios_vendor"" - looks like there's something funny in one of those files which is tripping up the registration."
1799849,2019-10-04 11:55:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799853,2019-04-10 18:07:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799853,2019-04-16 06:44:32 UTC,"Something is strange in general with the localization stuff in Tomboy.
See the recording in the attachment:"
1799853,2020-07-23 15:40:43 UTC,This bug is still present in Tomboy 1.15.9-0ubuntu1 on Ubuntu 20.04.
1799853,2020-07-23 15:42:38 UTC,Upstream bug seems to be this one: https://github.com/tomboy-notes/tomboy/issues/101
1799854,2018-10-25 12:56:55 UTC,"Jane, what is the value of the checkin_time and checkin_scan_time fields? If they are null, then the bug is that your transaction got xact_finish set while it was still checked out. xact_finish is used as a surrogate for the checkin_time and to indicate that all bills have been paid, etc."
1799854,2018-10-25 13:47:10 UTC,"Jason, thanks for the troubleshooting advice!  You're right, the checkin_time and checkin_scan_time fields are both null.  I'm changing the name of this bug, and will try to figure out how reproduce this particular bug."
1799857,2018-10-30 17:04:41 UTC,"Yes, but the fix will need to be backported and tested in Bionic separately, if you want Bionic fixed. The final backported patch needs to be a ""debdiff"" or contain the equivalent information, including the changelog entry, etc. See https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for details."
1799857,2018-10-30 16:09:51 UTC,"Robie, it's already fixed see my earlier posts to this thread."
1799857,2018-10-30 14:25:05 UTC,Let's leave this open since the bug appears valid and somebody else might be able to volunteer the fix.
1799857,2018-10-25 09:35:56 UTC,Confirmed incorrect behavior in bionic. xenial and cosmic behave correctly.
1799857,2018-10-26 18:04:05 UTC,"This was fixed in sudo 1.8.22 by the following commit:
https://www.sudo.ws/repos/sudo/rev/93cc4f4761f3"
1799857,2018-10-25 19:06:10 UTC,"There must be something in the code that is causing this.  I confirm that neither the EV SUDO_PROMPT, nor passprompt_override in /etc/sudoers are set."
1799857,2018-10-25 17:16:48 UTC,I've unfortunately hit a wall investigating this :(
1799857,2018-10-27 12:56:26 UTC,I installed sudo 1.8.23-2 from the cosmic repository and can confirm that if fixes the problem
1799858,2018-10-25 15:11:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799859,2018-10-27 10:42:23 UTC,I found a workaround for this problem.
1799859,2018-11-09 08:00:15 UTC,"As Pete mentioned, the ""wrong"" version comes from the proposed version. We can see the list is here:"
1799859,2018-10-27 06:06:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799859,2018-10-27 06:28:12 UTC,"I've run into the same problem, although I'm using cowbuilder-dist instead of pbuilder-dist on Ubuntu 16.04. I've attached a log."
1799859,2018-10-27 21:53:56 UTC,"Well... the creation of the environment worked with ""--updates-only""."
1799859,2018-10-25 02:51:17 UTC,"Just in case, I tried again after commenting my .pbuilderrc and I also have a hook."
1799867,2019-02-14 06:10:30 UTC,This shows what prints.  Please note the lack of a blank line that the next image has.
1799867,2019-02-14 06:11:51 UTC,This shows the composing window of the previous label to show how it SHOULD print.
1799867,2019-02-14 06:05:15 UTC,Here is the problem as it prints the first time with this file.  Changing to another file results in the next file having the same issue.
1799871,2018-10-25 04:24:44 UTC,Further information i found:
1799871,2018-10-25 04:29:33 UTC,"Also, weird thing is that I can use MAAS over the API just fine."
1799871,2018-10-25 04:47:37 UTC,only other error i see is this:
1799871,2018-10-25 13:25:00 UTC,"database_host: localhost
database_name: maasdb
database_pass: *******
database_port: 5432
database_user: maas
maas_url: http://**.**.**.**:5240/MAAS"
1799871,2018-10-25 14:42:56 UTC,"$ ps auxf | grep 'maasdb 10.90.90.3' | wc -l
168"
1799871,2019-09-19 11:51:33 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1799892,2019-03-22 03:45:57 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1799892,2018-12-19 10:01:26 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1799892,2018-11-21 20:47:02 UTC,"Reviewed:  https://review.openstack.org/619076
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e90e89219410a771f9b6b0c4200edb0480360afe
Submitter: Zuul
Branch:    stable/rocky"
1799892,2018-11-21 19:15:20 UTC,"Reviewed:  https://review.openstack.org/619075
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2ddb689f8789f1e9e845f4103617f267d990bc2b
Submitter: Zuul
Branch:    stable/rocky"
1799892,2018-11-21 02:00:11 UTC,"Reviewed:  https://review.openstack.org/613305
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cdbedac920f407e102a6916f2d943e50a1b0943d
Submitter: Zuul
Branch:    master"
1799892,2018-11-09 20:41:44 UTC,There is an online data migration:
1799892,2018-11-20 19:39:58 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/619075"
1799892,2018-11-09 23:21:06 UTC,"Reviewed:  https://review.openstack.org/613304
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=95d0ebc3d896a1af95c369d5d12b413e36c1c8d9
Submitter: Zuul
Branch:    master"
1799892,2018-10-25 12:22:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/613305"
1799892,2018-10-25 12:22:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/613304"
1799892,2018-11-20 19:40:17 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/619076"
1799892,2018-11-09 20:34:23 UTC,"OK so it looks like the root_provider_uuid should always be set, and if the resource provider is created without a parent_provider_uuid, then it is itself the root. But this is a data migration problem because for any existing providers created before queens ( https://review.openstack.org/#/c/377138/ ) wouldn't have either of those fields, and we didn't have any kind of online data migration to set the root_provider_id for existing providers."
1799900,2019-06-09 12:51:21 UTC,"Hi Nikos,"
1799900,2019-08-09 04:17:18 UTC,[Expired for cmt (Ubuntu) because there has been no activity for 60 days.]
1799905,2019-09-23 03:58:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799905,2019-09-23 05:56:33 UTC,"Hi,
this package was buggy and unmaintained for quite a while already.
Due to that it was removed from the Archive after Bionic in Debain and Ubuntu."
1799905,2019-09-23 06:02:01 UTC,"For the sake of help and guidance, this particular error was rather trivial.
xmlrpc/client is missing (it was part of ruby but not is separated).
Due to that old dependencies are missing it."
1799912,2019-12-19 12:44:28 UTC,This bug is already fixed by commit aa4268a09470aea28f4a8c9f1062f32f057cb151
1799913,2019-11-03 19:13:08 UTC,"Same problem here, but then on Xubuntu 18.04.3 LTS computer and an old iPhone 4."
1799913,2019-03-24 16:23:07 UTC,same here
1799913,2019-02-26 21:05:36 UTC,"I have the same issue,  but I just double checked, it works on my machine with bionic, the problem only arises on my cosmic machine."
1799913,2019-02-23 17:11:02 UTC,Same here as described by Devon Stuper (vanish) on 2019-02-04. I used an iPhone SE with iOS 12.1.4 and Ubuntu Cosmic (18.10).
1799913,2019-11-03 19:37:41 UTC,"Ok I actually made it work. Not sure if this still belongs here, but might as well inform others how I fixed it. Maybe it will help you as well."
1799913,2019-02-04 11:43:48 UTC,"I have tested this on my Disco development machine, and here's what I found."
1799913,2019-02-04 01:52:55 UTC,Tried the above.
1799913,2019-01-30 16:22:51 UTC,"Coudl you restart the gvfs service with that command
$ GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd -r"
1799913,2019-01-30 15:47:52 UTC,"Same here, with 18.10 and iPhone on 12.1.3 with, iPhone 6s, SE and 7
When accessing ""Documents"" I get ""Unhandled Lockdown error (-2)
The other folder seems mounted ok,but when I go to the DCIM folder, I get this error:
""Unhandled error message: The name:1.2260 was not provided by any .services files"""
1799913,2018-11-04 20:06:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799913,2019-02-04 18:54:39 UTC,"When I plug in my iPhone I automatically get a pop up on my iPhone asking if I wish to trust my computer. I accept it and put in my pass code. In Nautilus I get two new sections ""Documents on iPhone"" and ""iPhone"". The section ""iPhone"" opens up just fine and I am able to look at my pictures. But when I click on ""Documents on iPhone"" I get the lockdown error."
1799913,2018-10-25 12:24:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1799919,2020-11-13 16:04:14 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1799919,2020-11-13 16:30:39 UTC,I tried the repro case five times and each time it ran OK to the point of asking for floppy 2. So that suggests we probably fixed whatever it was...
1799919,2020-11-14 06:31:10 UTC,"Thanks, Peter! Looking at the bug description again and at the point in time when it happened, this was maybe a bug that we also saw with FreeDOS, caused by the CONFIG_ATA_DMA setting in Seabios, which had been fixed here: https://patchwork.kernel<email address hidden>/
Anyway, let's mark this as fixed, if it happens again, then please re-open or file a new bug."
1799920,2019-07-22 10:17:08 UTC,"Hi,"
1799920,2018-10-25 10:38:55 UTC,"Just got the external screen in the same state again (ie, blank) after leaving the desk for 5-10 minutes."
1799920,2018-10-26 15:33:59 UTC,"Hi,"
1799920,2018-10-26 02:08:47 UTC,Please run this command to send us more information about the system:
1799920,2019-07-22 04:23:43 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1799921,2018-11-11 13:13:32 UTC,I am not the only one facing this - https://wiki.archlinux.org/index.php/Talk:MSI_GS65
1799921,2018-11-05 17:11:47 UTC,"I am unable to boot after waking my laptop from suspend when using v4.19 kernel.
I tried using the recently released v4.19.1 kernel, but I am unable to install it(dkms apport Error)."
1799921,2018-10-29 17:07:34 UTC,"Can you remove all kernel parameters and workarounds, reboot with v4.19 kernel, and attach dmesg when the issue happens?"
1799921,2018-10-25 14:05:12 UTC,"Remove all kernel parameter, and comment out ""blacklist i2c_i801"" in /etc/modprobe.d/blacklist.conf, see if this help."
1799921,2018-10-25 13:23:21 UTC,No this issue did not start happening after an update/upgrade. This was always present since I booted Ubuntu onto this laptop.
1799921,2018-10-25 10:50:21 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799921,2018-10-25 10:30:06 UTC,This change was made by a bot.
1799921,2018-10-25 14:10:51 UTC,I did that. Did not work.
1799925,2019-05-08 12:11:58 UTC,Is this still a problem?
1799925,2019-07-08 04:17:22 UTC,[Expired for Snapcraft because there has been no activity for 60 days.]
1799927,2018-11-25 15:04:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799927,2019-06-09 15:29:52 UTC,4.17 is both in Disco and Eoan so this can be closed.
1799946,2019-05-14 19:08:05 UTC,"Thank you pascal, herrsaalfeld and others! This solution worked also for me on Ubuntu 18.10 when using Mediathekview."
1799946,2019-06-12 20:01:11 UTC,I would like to add that the proposed workaround to downgrade the openjfx packages is NOT a solution because no security updates will be available.  The correct solution is to provide an openjfx-8 package as proposed by the TO or to roll back the openjfx package to version 8.  The current openjfx package breaks the openjdk-8 package for Java FX applications and is unnecessary because openjfx-11 is a jar only solution that does not require package management by Ubuntu but can be fetched via maven or alike.
1799946,2019-08-07 14:13:38 UTC,"@herrsaalfeld Instead of using apt-mark hold, I would recommend to rank the origin higher, so that in - the unlikely case - there will be an update published, it actually arrives."
1799946,2019-08-08 10:15:28 UTC,"> Although that works, its quite an hack. Can't we have something like openjdk-8-jfx,
> openjdk-8-jfx-source, openjdk-11-jfx, ...
"
1799946,2019-11-20 12:31:25 UTC,"I attempted to compile JFX 8 from source manually, but it errors out. Can somebody try this and see if you can get any further? (I'm on 19.10)."
1799946,2020-09-23 17:31:57 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
1799946,2020-05-13 23:07:09 UTC,"Is there anyway we could increase the priority of this issue? The workaround of pinning to 8u161-b12-1ubuntu2 because that package no longer exists. There are MANY codebases out there that are still stuck in Java 8 and so far it seems that the only way to get openJFX with OpenJDK 8 is to compile it from source, which is not trivial."
1799946,2020-05-15 13:11:29 UTC,"FYI, so far I have not found a way to compile openJFX 8 from source on Ubuntu 20.4. I've created this bug on openJFX to hopefully resolve that. https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8245065"
1799946,2020-05-15 13:27:26 UTC,"Personally, I have given up on that and moved to using sdkman (https://sdkman.io) for handling Java variants, this so far seems the best / most reliable way to get different Java versions (including 8.x series) to work on recent Linux distributions. Java packaging in Debian-based distributions always has been weird, and JavaFX and the changes related to the way it's supposed to be distributed don't make things easier here."
1799946,2019-05-12 15:41:41 UTC,ok. This works:
1799946,2020-02-28 10:21:08 UTC,see https://stackoverflow.com/a/56166582/1497139
1799946,2019-05-12 15:39:32 UTC,This bug also effects the greenfoot project.
1799946,2018-11-19 14:18:55 UTC,I was able to copy the files from the openjfx package in 18.04 into my 18.10 manually and was able to launch Oracle SQLDeveloper which is what I needed the package for.
1799946,2019-05-06 15:12:25 UTC,"Hmmm, ok, I am unsure how Oracle and OpenJDK/JFX relate to each other, and whether the Open* variants will continue to see any community updates. The whole post-Java8-world still is a difficult thing to handle."
1799946,2019-05-06 14:50:22 UTC,"I'm aware of this, I was merely pointing out that the lack of oracle updates for java 8 now removes one of the possible workarounds, making the only still-working workaround."
1799946,2019-05-06 10:08:33 UTC,"Yes, but the suggested approach (""Would it be possible to supply an openjfx-8 package, similar to the openjdk-{8,11}-{jdk,jre}?"") would both fix this problem and make versioning of the openjdk- and openjfx- packages (which, despite being separate packages, are pretty closely tied to each other) immensely more concise. ;)"
1799946,2019-05-06 09:29:33 UTC,"As of a few weeks ago, Oracle will no longer supply free updates (security or otherwise) to oracle-jdk/jre-8. So now the only way to get Java 8-only applications, which still constitute a large portion is to use pinning of the openjfx package."
1799946,2019-05-03 08:38:26 UTC,Stumbled into this problem here as well both with a couple of internal Java applications and some FLOSS apps such as mediathekview (https://mediathekview.de/) in Germany.
1799946,2019-05-02 16:08:56 UTC,"On bionic, you will also have to downgrade libopenjfx-jni
```
sudo apt install openjfx=8u161-b12-1ubuntu2 libopenjfx-java=8u161-b12-1ubuntu2 libopenjfx-jni=8u161-b12-1ubuntu2
```"
1799946,2018-12-24 08:39:12 UTC,"The problem with the ""get oracle java"" workaround is that oracle java is no longer free (as in beer):"
1799946,2018-11-20 13:13:37 UTC,Workaround: get Oracle Java from https://launchpad.net/~webupd8team/+archive/ubuntu/java
1799946,2018-11-19 14:22:43 UTC,workaround:
1799946,2018-10-29 15:06:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799946,2018-11-19 13:36:43 UTC,"I've hidden my last comment because it's wrong.
I confirmed the author of this bug is right."
1799946,2019-05-07 09:38:49 UTC,It looks like this isn't going to happen:
1799946,2018-11-19 13:35:17 UTC,Your app may be incompatible for other reasons.
1799947,2018-12-08 16:52:58 UTC,"I saw what looks like the same issue under Wayland today. It was slightly different than what I had seen before in that I had one window (Chrome) that wasn't black. All others were. The issue started when I clicked to upload a file to a web page. The Chrome window went subdued, which it normally will do when it's launching the file chooser to select a file to upload, but the file chooser came up all black, and Chrome remained subdued and unresponsive (at least in that tab). Other application windows were also all black, including newly launched ones (tried another Files and also a Terminal window)."
1799947,2018-11-26 02:07:06 UTC,Please log new bugs for those other issues.
1799947,2018-11-23 17:25:02 UTC,Took me a while to figure out how to enable Wayland. Apparently WaylandEnable needs to be set explicitly to true in custom.conf to appear in the login choices. Running with it now... One thing I can say is that it seems to have fixed a problem where my entire Gnome session would crash when I tried to open a 10MP JPG.
1799947,2018-11-23 19:45:05 UTC,"On the flip-side, I still have a corrupted lock screen, and, under Wayland, two-finger trackpad scrolling doesn't work anymore."
1799947,2018-11-15 14:37:22 UTC,"00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
 Subsystem: Hewlett-Packard Company Compaq 6910p
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:03.0 Communication controller: Intel Corporation Mobile PM965/GM965 MEI Controller (rev 0c)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: mei_me
 Kernel modules: mei_me
00:03.2 IDE interface: Intel Corporation Mobile PM965/GM965 PT IDER Controller (rev 0c)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: ata_generic
 Kernel modules: pata_acpi
00:03.3 Serial controller: Intel Corporation Mobile PM965/GM965 KT Controller (rev 0c)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: e1000e
 Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M-E) LPC Interface Controller (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: lpc_ich
 Kernel modules: lpc_ich
00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel drive..."
1799947,2018-10-26 02:11:02 UTC,Please run this command to send us more information about the system:
1799947,2018-11-07 01:31:28 UTC,"In that case, please manually attach the output from running each of these commands:"
1799947,2018-11-06 12:51:29 UTC,OK. I apparently had to chmod permissions on .cache/apport to allow it to write the credentials file.
1799947,2018-10-27 18:49:07 UTC,"I tried, but launchpad.net stays stuck at ""Almost finished"" and doesn't actually create the launchpad.credentials file, even though the web UI says that the system is authorized."
1799947,2018-11-16 01:28:29 UTC,"Please try logging into ""Ubuntu on Wayland"" instead of ""Ubuntu"" and tell us if that stopps the bug from happening."
1799949,2020-05-28 07:57:52 UTC,I don't think this is a bug. It is an effect of a bug in the RPC lib. I think the good place to fix such bug is in the RPC lib itself. I consider this as a possible improvement on nova side hence the Whislist priority.
1799953,2020-12-01 14:09:35 UTC,Growpart grows a partition (/dev/sda2) on a block device (/dev/sda).
1799953,2020-12-01 13:47:36 UTC,This is fix-released in 0.32.
1799953,2020-07-16 15:25:49 UTC,https://github.com/canonical/cloud-utils/pull/9
1799953,2020-07-10 14:30:26 UTC,"As a note... it seems like there is almost no fallout of doing this.
a.) subsequent calls to pvresize (possibly added to users' scripts to finish this) will still exit 0
b.) there is no way other way that i'm aware of to use the space on that pv. (you can't add a second VG on that pv or anything like that).   By growing the partition we're already stopping a user from using that space in any way *other* than to add it to the PV."
1799953,2020-07-10 14:25:48 UTC,It seems all we have to actually do is call 'pvresize' to make this all work.
1799953,2020-01-15 01:48:25 UTC,"If this is accurate, I suspect the bug is in the cloud-init call to growpart, as I am using 0.31 successfully on CentOS 7 appliances with a LVM. There obviously are further steps needed to extend the LVM PV and LVs, along with the filesystem, but 0.31 seems to work well at growing the raw disk partition (we had to use the project release of 0.31 because the EL7 bundled package includes a much older release that mangles 2TB > GPT disks due to Bug #1259703)."
1799953,2020-07-10 15:38:23 UTC,"It seems like to determine if the partition we grew is a lvm pv, we should probably just use 'pvs' with explicit input rather than grep. and probably should use 'lvm' command rather than 'pvs'."
1799958,2018-10-25 15:33:16 UTC,Thanks for the bug merlijn. This looks like it's a pretty old Juju at 2.3.3 and I'm curious if this behavior is true in more recent 2.3.9 or better yet 2.4.4?
1799958,2018-10-25 15:51:31 UTC,"Yes, the most recent release we tested it with is 2.5-beta1"
1799964,2019-01-30 13:30:29 UTC,"Sorry for the noise but, I am having the very same problem with an nvidia card. I am posting this here because it seems that this problem affecting AMD, intel an nvidia cards since the 18.10 update, so maybe this should be inspected as a general graphics bug, not just a bug in AMD. If that is not the case, my apologies for adding a bit of noise."
1799964,2018-10-29 02:17:17 UTC,It looks like you both indeed are hitting the same kernel crash in 'amdgpu'.
1799964,2018-11-14 02:08:25 UTC,"Similar problem with my Toshiba Satellite C650 (embedded Intel HD Graphics 3000) running Xubuntu 18.10.  Once the Screen has Blanked, it will not unblank with normal Keystrokes and Mouse Events.  My ""Work around"": Plugging an External Monitor into the Satellite C650's VGA Port, which will unblank the Toshiba's Screen!!!"
1799964,2018-10-26 22:39:28 UTC,"Adding my output with the same issue in case it helps in investigation.
Attached the output as requested by Daniel van Vugt."
1799964,2018-11-14 02:21:17 UTC,"Lawrence,"
1799964,2018-10-26 08:22:11 UTC,Thanks. That seems to show the 'amdgpu' kernel module crashing at the end so it sounds like a kernel bug.
1799964,2018-10-25 14:28:05 UTC,Similar to #1799965
1799964,2018-10-25 19:43:04 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799964,2018-10-26 08:30:05 UTC,This change was made by a bot.
1799964,2018-10-26 07:56:52 UTC,Attached the output as requested by Daniel van Vugt.
1799964,2018-10-26 02:15:10 UTC,"Please reproduce the problem, do a hard reset and then run this command:"
1799968,2018-10-25 15:36:01 UTC,related to lp:1741317
1799968,2018-10-25 18:59:15 UTC,I think this request is more complicated because it also implie the handling of complex constraint geometry.
1799968,2018-10-25 19:11:31 UTC,"Is this just a duplicate of lp:1654571 ?  If not, can you edit your wishlist to make the implied aspects more explicit?"
1799968,2018-10-26 10:19:32 UTC,Feel free to mark it as duplicate if the difference are not enough.
1799969,2018-12-18 11:06:50 UTC,"I'm pretty sure it was created by Anisim Kalugin, but I've since lost the correspondence. It just appeared in the commit log without any source material. Do you have his email? Otherwise you can just message me privately."
1799969,2018-10-31 17:11:03 UTC,"Erik, do you know who originally created the bitmap? Since we have multiple icon sizes I assume that there was a GIMP file or something that the icon was originally created from. If I can get my hands on that, I'm happy to create the SVG. If we can't find an actual source file, I could probably create an SVG from the highest-resolution bitmap we have available. Just let me know!"
1799969,2018-10-31 14:04:39 UTC,"I agree that SVG would be nice, however the source image is a bitmap. We would need to re-create it using vectors."
1799974,2018-10-26 13:45:27 UTC,"* -doc package: I think we should promote it as well in main, if the -dev is promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first is lynx, in universe, www-browser is a virtual package not fullfiled?). In addition, it ships the doc in devhelp format (despite symlink from doc/ to gtk-doc/).
I don't think anyway that those are needed, we don't tend to have -doc dep on a browser implementation."
1799974,2018-12-05 16:50:05 UTC,Thanks! Do you mind listing the exact binary package list which should then be promoted?
1799974,2018-12-05 21:17:46 UTC,The only binary we care about is 'libgupnp-1.0-4'.We can promote the documentation if that's standard practice but that's not needed.
1799974,2019-08-14 11:57:44 UTC,This one could do with a quick review from the security team.
1799974,2019-08-20 00:34:36 UTC,"I reviewed gupnp 1.2.1-1 as checked in to eoan. This isn't a full security audit, but rather a quick gauge of maintainability."
1799974,2018-12-04 15:55:49 UTC,"Same as gssdp, the doc/depends issue is fixed in 1.0.3-2 in Debian/going to be autosynced. The tests are not integration tests so unsure there is much value having them as autopkgtests?"
1799977,2019-09-18 12:21:46 UTC,"I can't find who promoted this package to main; but it is there right now, and it seems it also was in previous releases. Closing as Fix Released based on the ack from Seb128 thatit would be subscribed to by desktop-bugs."
1799977,2019-08-23 15:46:59 UTC,It has to answer unicast M-SEARCH. That's in the UPnP spec and validation test suite.
1799977,2019-08-16 19:01:49 UTC,"I reviewed gssdp 1.2.0-1 as checked in to eoan. This isn't a full security audit, but rather a quick gauge of maintainability."
1799977,2019-08-14 12:00:06 UTC,This one could do with a quick review from the security team.
1799977,2018-12-05 16:50:09 UTC,Thanks! Do you mind listing the exact binary package list which should then be promoted?
1799977,2018-12-04 15:47:57 UTC,@doc depend & vcs reference have been fixed in 1.0.2-3 which just got uploaded to Debian (and going to be autosynced to disco)
1799977,2018-10-26 13:45:25 UTC,"* -doc package: I think we should promote it as well in main, if the -dev is promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first is lynx, in universe, www-browser is a virtual package not fullfiled?). In addition, it ships the doc in devhelp format (despite symlink from doc/ to gtk-doc/).
I don't think anyway that those are needed, we don't tend to have -doc dep on a browser implementation."
1799977,2018-12-05 21:17:00 UTC,"Sure, the only binary we care about here is 'libgssdp-1.0-3'. We can promote the documentation if that's standard practice but that's not needed."
1799978,2018-10-31 20:10:23 UTC,Duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542 ?
1799978,2018-10-31 20:09:12 UTC,apport information
1799978,2018-10-31 20:09:09 UTC,apport information
1799978,2018-10-31 20:09:07 UTC,apport information
1799978,2018-10-31 20:09:10 UTC,apport information
1799978,2018-10-31 20:09:05 UTC,apport information
1799978,2018-10-31 20:09:04 UTC,apport information
1799978,2018-10-31 20:09:02 UTC,apport information
1799978,2018-10-31 20:09:01 UTC,apport information
1799978,2018-10-31 20:09:00 UTC,apport information
1799978,2018-10-31 20:09:06 UTC,apport information
1799981,2020-01-28 23:50:26 UTC,The fix has been merged.
1799981,2020-01-28 17:29:28 UTC,"Reviewed:  https://review.opendev.org/692375
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=1d500e79156ada6bc6fdb628ed1da0efd4121f6a
Submitter: Zuul
Branch:    master"
1799981,2020-01-28 15:17:09 UTC,"Change abandoned by Oleksii Butenko (<email address hidden>) on branch: master
Review: https://review.opendev.org/615558
Reason: https://review.opendev.org/#/c/692375/6"
1799981,2019-10-31 13:59:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/692375"
1799981,2019-09-29 21:55:34 UTC,Adding example traceback as it's missing in the bug description (Stein deployment with RadosGW):
1799981,2019-07-29 15:28:07 UTC,"How other swift clients solves this ?
Does the swift documentation suggest anything about how get the info url from the catalog url ?"
1799981,2018-11-05 13:21:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615558"
1799981,2020-01-15 19:43:15 UTC,This seems Tempest is not able to pickup the registered service catalog in keystone. In case of swift we are modifying it in a incorrect way.
1799982,2018-12-04 19:29:30 UTC,"We are testing on a 3.2.2 system. There is a permission called ""VIEW_COPY_ALERT"". Currently we have it set to the consortial level. This seems to allow staff members to view copy alerts whenever the Manage action/button is selected."
1799988,2019-02-28 20:00:00 UTC,Tried the kernel in #50 and seeing better stability.
1799988,2019-04-02 10:44:05 UTC,"Update: correction, I realise foolishly that I was accidentally was looking at the wrong sources, so I have *not* been running with the patch."
1799988,2019-04-02 10:32:50 UTC,"Hi there,"
1799988,2019-03-25 16:31:29 UTC,Kai-Heng Feng:
1799988,2019-03-21 06:49:43 UTC,Do you still have this issue?
1799988,2019-03-02 13:45:46 UTC,"I am also experiencing the same issue with on a Dell XPS 13 9370 that I upgraded to 18.04. I added mem_sleep_default=deep to my grub boot options to workaround the battery drainage when ""suspended"". Just like other people, I can't seem to figure out a pattern to reproduce the issue with 100% certainty. I checked and the BIOS is up to date, and my wifi firmware is WLAN.RM.4.4.1-00079-QCARMSWPZ-1."
1799988,2019-02-28 20:19:18 UTC,"I spoke too soon, back to ""question mark"" state and no connection."
1799988,2019-02-27 18:10:42 UTC,"I'll gladly try any patches, if that would be helpful to you. I do however not use ubuntu, so the kernel in #50 is not really an option."
1799988,2019-01-15 15:52:16 UTC,"Actually, it still happens:
[45130.159244] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[45130.159255] dpm_run_callback(): pci_pm_suspend+0x0/0x130 returns -16
[45130.159258] PM: Device 0000:00:14.0 failed to suspend async: error -16
[45130.696215] PM: Some devices failed to suspend, or early wake event detected"
1799988,2019-02-09 07:23:33 UTC,"I'm now running the patches against 4.20.7 with firmware=RM.4.4.1.c2-00057-QCARMSWP-1 and I'm seeing some issues in the log after resume, however the wifi does work fine."
1799988,2019-02-07 12:34:23 UTC,"I forgot to add, I'm currently using an older firmware version RM.4.4.1.c2-00057-QCARMSWP-1 (which is mostly a leftover of searching for one that doesn't result in crashes). If you'd like to get any logs or or want me to run any tests, I'll gladly help."
1799988,2019-02-07 12:30:49 UTC,I've been testing the patches you linked above on Fedora 29 against 4.19.15-302 for about two weeks and so far I haven't had wifi disappear. I'm reasonably certain that I've lost bluetooth at least once  so I'm not quite sure whether the results are just a conicidence.
1799988,2019-02-05 05:54:49 UTC,Please test this kernel:
1799988,2019-01-16 04:19:42 UTC,"Actually, I still have the issue with wifi/bluetooth. But it has so numerous options, so I'm kind of confused.
Now I can definitely state that updated ath10k fw (up to 132) didn't help.
It can be no signs of the issue for few days after update, but it eventually occurs."
1799988,2019-01-15 16:00:29 UTC,"FWIW, the ""firmware crashed"" seems to be solved once a delay is used before resume. But since you no longer see the issue..."
1799988,2019-04-10 08:59:13 UTC,"Please follow [1] and see if it helps:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730331/comments/25"
1799988,2019-02-20 10:15:38 UTC,Please try the kernel in #50.
1799988,2019-04-10 09:12:20 UTC,"For those who don't use Ubuntu, here are changes that _may_ help the situation:
1) Commit d7a6c0ce8d26412903c7981503bad9e1cc7c45d2 (""USB: Consolidate LPM checks to avoid enabling LPM twice"").
This can fix this error:
    [ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
    [ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)"
1799988,2019-05-08 18:25:28 UTC,Sorry I didn't answer before. The script by @rasch seems to have solved the issue for me. I didn't have any problem with WiFi since using it almost two weeks ago.
1799988,2019-04-12 12:26:42 UTC,"Kai-Heng Feng, I can confirm on my XPS 9370 that everything seems to be working on 5.10-rc3-mainline which includes that patches from #47, but does not seem to have patches from #65 and #66."
1799988,2019-12-10 20:07:27 UTC,I can confirm that the patch in #77 is working in a kernel 5.3.15 on Devuan Beowulf (https://devuan.org). The kernel is taken from a Devuan Ceres (equivalent for Sid) repository.
1799988,2019-08-26 06:53:57 UTC,Might I add - looking at the logs above it seems people with both iwl and ath10k are affected - which probably points to something upstream in the bus.
1799988,2019-08-26 06:41:54 UTC,"Not sure if this might help... looks like this Dell has some hardware design problems - we should be able to come up with a workaround nonetheless. I've had the stock Ubuntu kernels die on me several times - goes into what seems to be disk thrashing (on an SSD?!) and 50% of the time the OOM killer recued it - but only after 30-60 minutes, nobody can wait that long - with nothing in the logs to go on, so I compiled my own kernel to dig deeper."
1799988,2019-05-15 09:59:52 UTC,"No, it doesn't effect functionality AFAIK"
1799988,2019-05-15 09:40:11 UTC,That's just a warning which got fixed in later release. Does it affect network connection?
1799988,2019-05-15 09:18:35 UTC,The wifi looks functional after the fix but ath10k driver starts complaining
1799988,2019-05-15 09:07:24 UTC,"confirmed #35 build fix same issue on XPS13 9360 with wifi module QCA6174.
Tested 10 suspends on power pluged and unpluged"
1799988,2019-05-13 16:58:56 UTC,Comment #35.
1799988,2019-05-13 13:23:45 UTC,@Kai-Heng is there a patched kernel package I can test with?
1799988,2019-05-08 19:04:49 UTC,"FWIW this is the (not upstreamed yet) patch to solve the issue:
https://lkml.org/lkml/2019/4/30/213"
1799988,2019-01-08 17:27:35 UTC,"As soon as it seems that the issue has been resolved, something bad occurs again.
Right now my laptop woke up without bluetooth (but with wifi). No dpm_run_callback trail though."
1799988,2019-05-08 17:24:01 UTC,"THe script by @rasch did not help for the issue that I have on my XPS 9360 where the wifi adapter is gone after resuming from sleep. Not sure if it's supposed to. Putting the machine back to sleep and then waking it up again solves things. However, if it's plugged in while I put it to sleep, waking it up does not help, so I also have to make sure it's unplugged. I've had this since I got the machine last year, with every version of Ubuntu that's been available since then."
1799988,2019-04-27 18:55:02 UTC,"Yes, you're correct. Updated snippet:"
1799988,2019-04-27 14:48:28 UTC,"Thanks for the workaround @rasch, I'll try it.
One question, I don't have a ""/lib/systemd/systemd-sleep/"" folder. Maybe it is ""/lib/systemd/system-sleep/""?"
1799988,2019-04-26 19:44:55 UTC,"This is a workaround to make sure Wifi works on each and every resume, not just every other one (obviously this disables wake from Bluetooth) - after ""sudo -s""."
1799988,2019-04-26 18:31:43 UTC,Still experiencing similar issues with suspend/resume with https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc6/
1799988,2019-04-13 10:05:07 UTC,"No not yet. I am certain patch in #65 prevents the system get woken up by BLE events, I am not sure patch in #66 has any effect at all."
1799988,2019-04-11 02:49:11 UTC,Suffering from this bug in a Dell XPS 9360 with Killer WiFi. It happened in 18.10 and still happens in 19.04. :/
1799988,2019-01-08 09:05:43 UTC,No it means somehow it's fixed by the new firmware.
1799988,2019-10-18 16:24:51 UTC,"Since the link under #35 is dead, I assume the patch got merged into the kernel at some point?"
1799988,2019-01-08 07:32:47 UTC,"Is ""dpm_run_callback()"" still shown in dmesg?"
1799988,2018-10-26 03:07:26 UTC,apport information
1799988,2018-10-26 03:07:24 UTC,apport information
1799988,2018-10-26 03:07:23 UTC,apport information
1799988,2018-10-26 03:07:21 UTC,apport information
1799988,2018-10-26 03:07:20 UTC,apport information
1799988,2018-10-26 03:07:18 UTC,apport information
1799988,2018-10-26 03:07:17 UTC,apport information
1799988,2018-10-26 03:07:16 UTC,apport information
1799988,2018-10-26 03:07:28 UTC,apport information
1799988,2018-10-26 03:07:15 UTC,apport information
1799988,2018-10-26 03:07:12 UTC,apport information
1799988,2018-10-26 03:07:10 UTC,apport information
1799988,2018-10-25 19:41:26 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799988,2018-10-25 19:40:22 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799988,2018-10-25 16:48:48 UTC,I think I have same issue:
1799988,2018-10-25 16:00:55 UTC,Use latest firmware for wifi and bluetooth (from linux-firmware git)
1799988,2019-01-08 08:50:33 UTC,Cannot see such text. Should I enable some debug flags?
1799988,2018-10-25 15:55:30 UTC,apport-collect collected no additional data
1799988,2018-10-26 03:07:13 UTC,apport information
1799988,2018-10-26 03:07:45 UTC,"Cristian Aravena Romero,"
1799988,2018-10-26 03:07:22 UTC,apport information
1799988,2018-10-31 21:54:37 UTC,I've had some intermittent Wi-Fi issues after upgrading to 18.10.
1799988,2019-01-08 07:20:49 UTC,I didn't test it with disabled Bluetooth. So cannot provide correct information.
1799988,2019-01-07 15:03:49 UTC,Now it's a different issue.
1799988,2019-01-04 15:14:50 UTC,"Bt+wifi still disappear if laptop goes to sleep while bluetooth active.
In my case, steps to reproduce
1. Listen bluetooth headset
2. Close a lid
3. Wake laptop and watch missed bt+wifi"
1799988,2019-01-03 14:40:52 UTC,Just preliminary results. Done 2 cycles of sleep-wake. No signs of missing wifi+bluetooth. It seems encouraging.
1799988,2018-10-31 06:17:38 UTC,"Kao, I can see the issue on the XPS 9370 w/ Killer 1435. Let me see what I can do."
1799988,2019-01-02 16:47:23 UTC,"Kai Heng,"
1799988,2019-01-02 05:23:05 UTC,"Kao,"
1799988,2018-12-29 22:38:58 UTC,"Sorry for bloating up here, just wanted to state that I have the same bios version as aberry5555"
1799988,2018-12-29 22:37:07 UTC,"Hi, I just experienced this today, the only thing that was not usual was that I left my Bluetooth Headphones which were previously used on and the notebook fell asleep. Maybe this is a coincidence, but it happened to me in this exact combination and only once since ever."
1799988,2019-01-03 05:51:26 UTC,Please enable btusb autosuspend during test.
1799988,2018-12-20 09:03:46 UTC,"When I was seeing this issue before I made the bios config change, I did notice that when the wifi and/or bluetooth died it'd need a hard power down and start up rather than a reboot to get it properly working."
1799988,2018-12-20 02:49:29 UTC,"aberry5555,"
1799988,2018-12-19 15:07:45 UTC,"I am running fedora 28 with kernel 4.19.8-300 and see this issue too, but just any FYI it seems disabling the wireless switch for both bt & wifi (by default both wireless and bluetooth can be switched on/off with the fn+home buttons) in the BIOS resolves this issue, only mentioning as it might help track down the bug."
1799988,2018-12-13 08:55:27 UTC,"The issue is introduced by this commit:
commit a0085f2510e8976614ad8f766b209448b385492f
Author: Sukumar Ghorai <email address hidden>
Date:   Wed Aug 16 14:46:55 2017 -0700"
1799988,2018-11-06 07:54:43 UTC,Observed the issue on 4.15 but not on 4.4.
1799988,2018-11-01 05:02:08 UTC,"Chris,"
1799988,2018-11-02 07:08:26 UTC,Seems like this also happens to v4.19. Trying v4.15 to see if this is a regression...
1799988,2018-11-01 14:27:40 UTC,"This is my readout from running a wireless info report, a note I'm using docker for local development work, so there are a bunch of bridged connections in the iwconfig. I've tried removing docker and still the issue persists. If the information below isn't adequate let me know of a way to get the information you're needing."
1799988,2018-12-20 09:05:15 UTC,"As an FYI, here's info about my bios version:"
1799989,2019-10-31 03:37:29 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1799989,2018-11-05 11:40:26 UTC,"Reading through the links from Cory and Ian makes it clear that doing so is poking lots of holes in the security of containers. Specifically, the pool of loopback devices is shared on the host, and by default LXD isn't allowed to mount them (there is a security risk of mounting arbitrary filesystems, because you are passing untrusted data directly to the kernel.)"
1799989,2018-10-31 13:22:06 UTC,What is expected behaviour for the test charm in question?
1799989,2018-11-05 02:56:54 UTC,"for LXD block storage I'm pretty sure we want to be mounting storage from
the host so that we get the same properties of 'storage that can outlive
the instance'. Otherwise you'd just use somewhere on the instance's root
dir."
1799989,2018-10-29 16:12:54 UTC,"Interestingly, the command run in the container by the storage provisioner is:"
1799989,2018-10-29 14:28:58 UTC,"Machine log looks like this:
https://pastebin.ubuntu.com/p/vQCtphkh5k/"
1799989,2018-11-05 03:23:17 UTC,I misremembered the exact mechanism needed. Here's some (slightly old) doc
1799993,2018-11-19 16:27:37 UTC, .o0O0o.  apt list --installed  | grep firefox
1799993,2018-11-19 17:13:54 UTC,"Thanks Christopher, that's useful."
1799993,2018-11-19 16:29:38 UTC,attached backtrace as txt file for readability
1799993,2018-11-19 14:46:52 UTC,"@Christopher: can you install the firefox-dbg package, and reproduce the crash in gdb again to get a usable stack trace ?"
1799993,2018-10-25 16:50:28 UTC,"@aixguy, Firefox got an update recently so version 63 should be available. Would you mind checking if this new version also segfaults?"
1799993,2018-10-29 14:26:51 UTC," .o0O0o.  firefox -g
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""powerpc64le-linux-gnu"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word""...
Reading symbols from /usr/lib/firefox/firefox...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/lib/firefox/firefox
[Thread debugging using libthread_db enabled]
Using host libthread_db library ""/lib/powerpc64le-linux-gnu/libthread_db.so.1""."
1799993,2018-10-25 18:37:49 UTC,Uploading new apport report.
1799993,2018-10-25 18:09:46 UTC,Thanks for confirming with version 63. In the apport report from version 62.0.3 there was:
1799993,2018-10-25 17:37:36 UTC,OK I updated.  Problem still exists.
1799993,2018-10-29 14:29:47 UTC," .o0O0o.  firefox -g -d gdb
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""powerpc64le-linux-gnu"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word""...
Reading symbols from /usr/lib/firefox/firefox...(no debugging symbols found)...done.
(gdb) handle SIG33 noprint nostop
Signal        Stop      Print   Pass to program Description
SIG33         No        No      Yes             Real-time event 33
(gdb) run
Starting program: /usr/lib/firefox/firefox
[Thread debugging using libthread_db enabled]
Using host libthread_db library ""/lib/powerpc64le-linux-gnu/libthread_db.so.1""."
1799994,2018-10-26 17:43:34 UTC,"ok, I take that back. Rebooting to -36 after reinstalling nvidia gets a successful boot, but does NOT get working displays. Looks like this is an nvidia driver issue, and NOT a kernel issue."
1799994,2018-10-26 17:27:45 UTC,"reinstalled nvidia with:
# sudo ubuntu-drivers autoinstall
Reboot into -38 and same black screens.
Reboot into -36 and same previous working Xorg"
1799994,2018-10-26 16:34:24 UTC,sudo apt purge $(dpkg -l|awk '/nvidia/ {print $2}')
1799994,2018-10-26 16:01:16 UTC,$ sudo apt install --reinstall nvidia-driver-390 nvidia-dkms-390
1799994,2018-10-26 11:16:44 UTC,"Tim Riker,

Try this:"
1799994,2018-10-25 20:11:42 UTC,Last ones are from no-display -38 kernel
1799994,2018-10-25 19:59:04 UTC,apport information
1799994,2018-10-25 19:58:59 UTC,apport information
1799994,2018-10-25 19:59:01 UTC,apport information
1799994,2018-10-25 19:58:58 UTC,apport information
1799994,2018-10-25 19:58:56 UTC,apport information
1799994,2018-10-25 19:58:55 UTC,apport information
1799994,2018-10-25 19:58:53 UTC,apport information
1799994,2018-10-25 19:58:52 UTC,apport information
1799994,2018-10-25 19:58:50 UTC,apport information
1799994,2018-10-25 19:59:03 UTC,apport information
1799994,2018-10-26 19:07:17 UTC,"Tried ppa drivers 410, 390, same issue."
1799994,2018-10-30 15:19:00 UTC,"Sometimes it finds the displays, and sometimes it does not. Uploading two Xorg.0 log files from /var/lib/gdm3/.local/share/xorg/ One from before stopping gdm, running Xorg as root, stopping Xorg as root and then restarting gdm. The first one finds no displays:"
1799994,2018-10-31 16:18:07 UTC,"Switching to lightdm works around the issue:
# apt install lightdm-gtk-greeter lightdm"
1799994,2019-06-13 09:23:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1716857, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1799994,2018-11-09 21:52:51 UTC,"I uninstalled lightdm and lightdm-gtk-greeter to get the log. I reinstalled lightdm and lightdm=gtk-greeter, restarted display-manager, and I'm up and running again."
1799994,2018-11-09 21:03:32 UTC,"For the record, I have a Lenovo P50 running Ubuntu MATE (which uses lightdm), also in am Ultradock. It is running in ""Discrete"" (NVIDIA) mode using nvidia-396 from the graphics-driver ppa, and had been working well since at least -34."
1799994,2018-11-07 01:34:30 UTC,OK. Next we probably want to get an idea of what gdm is doing.
1799994,2018-11-06 17:15:20 UTC,"I'm already not running Wayland. When I was running Wayland, it started up on the internal display using the Intel driver. When docked, I don't use the internal display, so I disabled Wayland."
1799994,2018-11-06 05:28:47 UTC,Please try this:
1799994,2018-11-06 04:49:26 UTC,Adding nomodeset rebuilding initrd and rebooting does not fix it.
1799994,2018-11-06 04:09:21 UTC,Sounds like bug 1705369 or bug 1798790.
1799994,2018-11-06 03:40:18 UTC,"nvidia drivers build and install just fine. Starting gdm3 fails to detect displays, but Xorg does start. Stopping gdm3 and running a bare Xorg gets working displays. Restarting gdm3 and displays work."
1799994,2018-10-25 19:58:48 UTC,apport information
1799994,2018-11-06 03:35:57 UTC,"After completely removing the nvidia drivers, rebooting, and reinstalling the nvidia drivers, even the old kernel fails to boot. This appears to be an nvidia driver issue that shows up because of the gdm3 setup where it runs two different Xorg instances. Under lightdm+gnome the displays light up normally."
1799994,2018-11-06 02:30:13 UTC,This change was made by a bot.
1799994,2018-11-06 02:11:40 UTC,I'm not sure we should be looking in gdm here.
1799994,2018-11-05 22:01:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799994,2018-10-31 16:35:57 UTC,"After comment #107 I add gdm3
--
Cristian Aravena Romero (caravena)"
1799994,2018-10-29 15:55:52 UTC,"Any ideas what to try next? Starting gdm3 on boot results in black screen. Stopping display-manger, starting Xorg manually, stopping Xorg, restarting display-manager and I'm up. I need to do this every time I boot the machine."
1799994,2018-10-25 19:58:45 UTC,apport information
1799994,2018-10-25 17:00:36 UTC,apport information
1799994,2018-10-25 18:21:59 UTC,"Second log set it from running -38. Xorg running, all displays are black."
1799994,2018-10-25 17:00:44 UTC,apport information
1799994,2018-10-25 17:00:42 UTC,apport information
1799994,2018-10-25 17:00:40 UTC,apport information
1799994,2018-10-25 17:00:39 UTC,apport information
1799994,2018-10-25 17:00:38 UTC,apport information
1799994,2018-10-25 17:00:35 UTC,apport information
1799994,2018-10-25 17:00:33 UTC,apport information
1799994,2018-10-25 17:00:31 UTC,apport information
1799994,2018-10-25 17:00:29 UTC,apport information
1799994,2018-10-25 17:00:28 UTC,apport information
1799994,2018-10-25 17:00:27 UTC,apport information
1799994,2018-10-25 17:00:26 UTC,apport information
1799994,2018-10-25 17:00:23 UTC,apport information
1799994,2018-10-25 17:00:22 UTC,apport information
1799994,2018-10-25 16:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1799994,2018-10-25 17:09:25 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799994,2018-10-25 18:33:44 UTC,"There is a new version of the kernel '4.15.0-39.42', to install, you must follow [0]this guide
[0] https://wiki.ubuntu.com/Testing/EnableProposed"
1799994,2018-10-25 17:16:21 UTC,Yes. I upgraded yesterday. On booting today into -38 the displays did not light up. On reverting to -36 I get displays again. I'll test the mainline kernel and report back.
1799994,2018-10-25 17:36:20 UTC,"As this is with the nvidia driver, I think I need a kernel with modules-extra included. Any hint on how to find the last one of those?"
1799994,2018-10-25 18:20:50 UTC,apport information
1799994,2018-10-25 18:20:48 UTC,apport information
1799994,2018-10-25 18:20:46 UTC,apport information
1799994,2018-10-25 18:20:45 UTC,apport information
1799994,2018-10-25 18:20:43 UTC,apport information
1799994,2018-10-25 18:20:41 UTC,apport information
1799994,2018-10-25 18:20:39 UTC,apport information
1799994,2018-10-25 17:31:00 UTC,We already know that your linux '4.15.0-36' works well. You could try to boot with your kernel '4.15.0-38' and then start your system switch to terminal mode (CTRL + ALT + F3) and execute:
1799994,2018-10-25 18:20:38 UTC,apport information
1799994,2018-10-25 18:20:35 UTC,apport information
1799994,2018-10-25 18:20:33 UTC,apport information
1799994,2018-10-25 18:20:32 UTC,apport information
1799994,2018-10-25 18:20:30 UTC,apport information
1799994,2018-10-25 18:20:29 UTC,apport information
1799994,2018-10-25 18:20:27 UTC,apport information
1799994,2018-10-25 18:20:26 UTC,apport information
1799994,2018-10-25 18:20:36 UTC,apport information
1799995,2018-10-28 21:50:37 UTC,According to http://sane-project.org/sane-mfgs.html#Z-EPSON this should be supported by the SANE drivers. This will need to be solved in the driver in the SANE project. Note that connecting via USB using different protocols than network scanning which is why it works only over the network.
1799998,2018-10-26 10:24:44 UTC,"It does not.
Still no sound on <20%.
But over 100%, it did increase the volume output without distortions."
1799998,2018-10-30 03:36:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1799998,2018-10-25 21:13:56 UTC,"""Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?""
This is the first time I install Ubuntu/Linux on my laptop."
1799998,2018-10-26 02:21:29 UTC,Please try setting:
1799998,2018-10-25 19:38:55 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1799999,2019-09-19 12:06:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1799999,2018-10-30 18:13:12 UTC,The stress-ng-cpu-long test fully loads the system for the entire time it runs. Some hardware issues only surface after the system is loaded for a sustained period of time. One reason for this could be the issue is heat related. This could explain why the error isn't showing in stress-ng-cpu-short or doing a test deployment.
1799999,2018-10-25 17:18:46 UTC,"For what it's worth, I've seen this exact symptom on faulty hardware. ;-) Often the short tests will be fine, but the long tests will fail in that case. So personally, I would recommend further investigation!"
1800007,2018-10-25 20:20:45 UTC,The property label and string were changed due to the following report:
1800007,2018-11-05 18:51:11 UTC,Did you check the linked report?
1800007,2019-01-01 11:53:28 UTC,New upstream report:
1800012,2020-02-25 22:08:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800012,2020-02-25 22:10:09 UTC,This bug makes ogg files unusable and may destroy entire music collections. Fixing of this bug is highly neccessary
1800012,2020-02-26 00:22:16 UTC,"The attachment ""taglib-1.11.1-bug-864.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1800012,2020-08-18 17:03:53 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1800012,2020-09-02 18:19:35 UTC,"Is there a timeline for when the fix for Focal will be released? I have corrupted half my music collection due to this bug, good thing I had a backup."
1800014,2019-07-27 18:09:35 UTC,"I don't consider this an important use case. Just raise a new exception instead, of a type that you control."
1800014,2019-07-27 18:10:09 UTC,"(BTW, what you show is not exception chaining)"
1800016,2019-09-13 10:22:15 UTC,This is now fixed with znetconf from s390-tools v2.10 and higher - hence fixed in Eoan that comes with v2.11.
1800016,2019-09-13 09:59:42 UTC,"------- Comment From <email address hidden> 2019-09-13 05:55 EDT-------
@CAN. The problem is solved with Ubuntu 19.10, Please check if this is true from your perspective. Many thanks in advance"
1800024,2021-01-04 18:01:33 UTC,we're still seeing this behaviour
1800024,2018-11-09 04:51:39 UTC,"Also ran into this, it causes the nova-novncproxy service to fail to start (issue applies to both VNC and SPICE). See also related Bug #1788660"
1800024,2018-11-09 04:59:16 UTC,"I'm not sure that key= and cert= needs to be set for the normal nova-cloud-controller SSL deployment at all, at least in our case where we use apache2 for the SSL frontend."
1800037,2018-12-06 16:24:56 UTC,"Thank you for your bug report, that doesn't seem a nautilus issue though. Could you include a screenshot of the dialog? How did you trigger it?"
1800037,2018-12-06 21:35:28 UTC,"According to https://github.com/GNOME/nautilus/blob/8442b4e7dd45fe15ebafa4457e781e9e9c89d166/po/de.po#L4500 the original message is ""Unable to find the requested file. Please check the spelling and try again."""
1800040,2018-11-05 21:43:29 UTC,"Yes, looks to me like it's armhf build of bacula-fd that's the issue - 7.0.5 worked fine and bconsole provides a workaround so it's not a showstopper. FWIW, A-X-A on Karl's list works too."
1800040,2019-04-25 21:43:29 UTC,"GDB installed and it's now showing some more info.
Config:
  Selene (Bacula host) has just been upgraded to Disco, Bacula now version 9.4.2.
  Bat running from Selene via ssh tunnel (ssh -X userxxx@selene)
  Client -> Status Client causes FD to fail, Bat still reports new version of client and sometimes gets some data in header tab."
1800040,2019-01-12 10:28:08 UTC,"Thanks, unfortunate the traceback is not working properly for your environment:"
1800040,2019-01-09 19:33:31 UTC,"Sorry, just rediscovered this. Attached a whole bunch of tracebacks for you."
1800040,2018-11-09 11:42:50 UTC,"Hello, could someone attach a Bacula *.traceback generated by this sigsegv, please. Thanks."
1800040,2018-11-05 10:52:54 UTC,Thanks Richard!
1800040,2018-11-05 10:33:01 UTC,Thank you for your detailed investigations.
1800040,2018-11-04 15:53:29 UTC,Test 5 - Bat on armhf fails too.
1800040,2018-10-31 23:12:29 UTC,Hi Christian
1800040,2018-10-29 08:06:08 UTC,"Actually I guess ""mix of Windows & Linux 32 and 64bit"" implies that x86 client was tested."
1800040,2018-10-29 08:02:32 UTC,"Hi,
I tried to do the same from ""bat"" but it just happened to work for me. See attached screenshot (I waited a bit, no fail later)."
1800040,2018-11-05 10:34:08 UTC,"(if I'm wrong about the armhf thing, please let us know)"
1800041,2019-01-13 02:49:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800041,2019-01-13 02:54:29 UTC,"This bug prevents IKOS from being built for Bionic with Apron features enabled, and will be a hindrance to distributing IKOS as a package in the future."
1800043,2019-10-20 00:45:56 UTC,"Sorry for delay :
as of today :"
1800043,2019-06-18 11:52:37 UTC,"Hi, I have exactly the same issue.
Since the OP didn't provide the gio infos upstream requested, I just wanted to jump in and provide those infos."
1800043,2019-04-17 08:39:23 UTC,"Upstream asked for extra details
'Can you please provide gio info /media/feydreva/download and gio info -f /media/feydreva/download outputs?'"
1800043,2019-03-24 08:52:48 UTC,"I have exactly the same issue. Also with a synology NAS.
Mounted like this
192.168.1.43:/volume1/homes /home/files/syn nfs rw,relatime,user,noauto 0 0"
1800043,2019-02-06 16:34:18 UTC,"Hello,"
1800043,2019-01-02 18:21:49 UTC,"Do we work on the same problem? My nfs share is exported by an external file server (i.e. a synology disc station) and imported by Ubuntu 18.04.
Thus, the line in my /etc/fstab on my Ubuntu system reads
xxx.yyy.zzz:/volume1/homes/peter /media/peter/MyStorage nfs defaults,intr 0 0
This links the external disc to my Ubuntu system. The option ""intr"" seemed to be important for the synology station when I still was using 16.04. Now, the behaviour doesn't change if I omit it.
Once again: using nautilus I can only read from ""/media/peter/MyStorage"". Using command line tools I can read and write to the share.
Also, using nautilus I can read _and_ write to every subfolder of ""/media/peter/MyStorage""."
1800043,2019-01-26 23:55:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800043,2019-01-07 13:30:32 UTC,"I have the same problem, can't write to the 1st directory of nfs share in GUI.
Searched a day until found this thread here.
Coming from 14.04 to 16.04 and nemo 3.6.5 instead of nautilus (mint cinnamon 17.3->18.3). The same problem also consists with thunar.
So it should be a common bug.
Maybe a follow failure from another (gnome?)package, because with a fresh usb stick (in my case mint 18.03) it works!"
1800043,2019-01-02 16:51:53 UTC,"I exported a nfs share (rw,sync,no_subtree_check) on Ubuntu 18.04.1 LTS, used nfs-kernel-server: 1:1.3.4-2.1ubuntu5 and nfs-common: 1:1.3.4-2.1ubuntu5 nautilus: 1:3.26.4-0~ubuntu18.04.2 and could not reproduce the problem. Ensure the system is properly patched."
1800043,2019-01-02 16:14:24 UTC,"I exported a nfs share (rw,sync,no_subtree_check) on Ubuntu 18.04.1 LTS Release: 18.04
nautilus: 1:3.26.4-0~ubuntu18.04.2 and could not reproduce the problem. Nautilus works OK."
1800043,2018-12-31 17:02:34 UTC,"As for the command line: copying and deleting works with the usual cp/rm commands and also with the gio tool (gio copy/gio remove). However, it doesn't work with nautilus.
The nautilus UI simply doesn't let me place the icon of the desired file into the root window. It ""flies"" back to where it came from. Thus, it behaves exactly as you would expect from a read-only file system. BTW: copying _from_ the root system with nautilus also works correctly. And, again, once I go into one of my folders - everything works as usual.
For now I decided to mount my share with CIFS - which also works as desired."
1800043,2018-12-06 16:23:57 UTC,Thank you for your bug report. Can you write into that directory using the gio command line utility? Do you get any error in the journalctl log or in the nautilus UI when trying to copy to the base directory?
1800043,2019-02-06 11:57:10 UTC,Reported on https://gitlab.gnome.org/GNOME/nautilus/issues/884
1800044,2020-01-26 14:51:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800044,2018-11-06 23:43:52 UTC,"Thanks, that's the version of friendly-recovery from Ubuntu 18.04."
1800044,2018-11-06 22:41:34 UTC,"I'm not using Ubuntu.  This problem occurred with Linux Mint 19,
Friendly-Recovery software update 0.2.38ubuntu1.  I used Timeshift to
restore Linux Mint to an earlier date, which resolved the problem.  I then
tried installing the Friendly-Recovery update again, and experienced the
same issue when trying to use fsck."
1800044,2018-10-31 18:57:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800044,2018-11-06 21:28:37 UTC,Which release of Ubuntu are experiencing this issue on?
1800047,2019-04-29 17:55:02 UTC,https://github.com/mixxxdj/mixxx/pull/2092
1800051,2019-04-03 20:23:27 UTC,https://github.com/mixxxdj/mixxx/pull/2072
1800056,2018-10-28 23:58:44 UTC,"It is confusing indeed. However, due to a backward compatibility and current scripts that may potentially rely on current behavior, we cannot remove this redundant option unitl Juju 3."
1800056,2018-10-29 14:08:32 UTC,"I tried using the `--credential` option in 2.5-beta1, 2.4.4, and 2.3.9 and it's not supported:"
1800056,2019-03-22 03:45:08 UTC,"This PR against develop removes redundant, non-operational option https://github.com/juju/juju/pull/9943"
1800060,2018-10-26 01:47:32 UTC,Compile trunk (compatible with bamf3) but same crash.
1800066,2018-10-26 02:49:04 UTC,Can you attach the problematic board?
1800066,2018-10-26 13:00:57 UTC,"Seth, ok it is not a problem. It is attached here."
1800066,2018-10-26 15:32:59 UTC,Thanks.  The outline is not closed.  Here is the top left corner
1800066,2018-10-26 15:58:53 UTC,"Yes sure, the fix was easy."
1800067,2019-05-25 05:10:56 UTC,This is hard to handle as people can select the colors from a palette. An admin is expected to make a sensible choice.
1800077,2020-04-30 16:03:28 UTC,"Change abandoned by Lance Bragstad (<email address hidden>) on branch: master
Review: https://review.opendev.org/619336
Reason: Abandoning this since I haven't updated it in over a year. Someone is more than welcome to pick this up and carry  it forward."
1800077,2018-11-21 18:02:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619336"
1800077,2019-01-28 17:43:09 UTC,Unassigning myself for now in case anyone has time to pick up what's in review [0].
1800078,2018-11-10 08:42:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800078,2018-11-10 08:59:54 UTC,"From journalctl:
packagekitd[28511]: terminate called after throwing an instance of 'std::length_error'
packagekitd[28511]:   what():  basic_string::_M_replace
systemd[1]: packagekit.service: Main process exited, code=killed, status=6/ABRT
systemd[1]: packagekit.service: Failed with result 'signal'."
1800078,2019-01-07 20:58:44 UTC,https://bugs.kde.org/show_bug.cgi?id=400123 blames it on Packagekit malfunction in Kubuntu 18.10
1800078,2019-01-13 20:20:25 UTC,I did some cleanup and that fixed the problem.
1800079,2019-01-17 06:29:51 UTC,This issue seems to be environmental or devstack as backend may be down during installation.
1800079,2020-01-24 16:37:05 UTC,"No data has been provided per the previous comment's request in a year, so I assume the reporter's issue got resolved. If not and you still encounter the issue, please, provide more info and feel free to reopen it."
1800080,2019-09-15 17:08:45 UTC,Migrated to https://github.com/widelands/widelands/issues/1084
1800088,2021-01-13 04:17:19 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1800088,2020-11-13 16:04:28 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1800093,2019-08-20 01:47:33 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1800103,2018-10-26 08:20:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1800103,2018-11-14 12:22:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800103,2019-02-21 15:33:40 UTC,We should probably think about how better to allow entry of ip addresses. This isn't a but per se -- but it's certainly confusing.
1800105,2018-10-26 08:36:34 UTC,"Please see bugs #1799761 Pidgin fails to start after install in 18.10, and #1800071 Wireshark fails to start after installation on 18.10."
1800105,2018-10-26 12:23:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1800106,2018-11-29 10:41:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800115,2019-01-17 06:22:11 UTC,"Hi B ChandraShekhra,"
1800115,2020-01-24 16:34:40 UTC,"No steps for reproducing the issue has been provided in a year so I'm gonna mark this as Invalid. If you still encounter the problem and provide more information as requested in the previous comment, feel free to reopen the bug."
1800118,2018-10-26 09:53:31 UTC,Can you please describe the problem in a sentence or two?
1800118,2018-10-26 10:12:52 UTC,"Sure
Nvidia NVHDA Sound works only with a PATCH!
NVHDA does not persist after Suspend or Hibernating (my System Fully
Supports BOTH)"
1800118,2018-10-26 17:03:26 UTC,"And to help you Fix these ISSUES for not me but ALL Ubuntu enthusiasts,
especially for newbies, as these workarounds are really only for those like
me who try very hard to solve problems!"
1800127,2018-10-27 19:28:17 UTC,apport information
1800127,2018-10-27 19:28:16 UTC,apport information
1800127,2018-10-27 19:28:15 UTC,apport information
1800127,2018-10-27 19:28:14 UTC,apport information
1800127,2018-10-27 19:28:13 UTC,apport information
1800127,2018-10-27 19:28:12 UTC,apport information
1800127,2018-10-27 19:28:10 UTC,apport information
1800127,2018-10-27 19:28:09 UTC,apport information
1800127,2018-10-27 19:28:11 UTC,apport information
1800127,2018-10-27 19:28:07 UTC,apport information
1800127,2018-10-27 19:28:08 UTC,apport information
1800127,2018-10-27 19:28:00 UTC,apport information
1800127,2018-10-27 19:28:01 UTC,apport information
1800127,2018-10-27 19:28:02 UTC,apport information
1800127,2018-10-27 19:27:59 UTC,apport information
1800127,2018-10-27 19:28:04 UTC,apport information
1800127,2018-10-27 19:28:05 UTC,apport information
1800127,2018-10-27 19:28:03 UTC,apport information
1800127,2018-10-26 14:57:14 UTC,"DEDan,"
1800132,2020-01-30 10:24:18 UTC,This issue was fixed in the openstack/kolla-ansible 8.1.0 release.
1800132,2020-01-30 10:21:59 UTC,This issue was fixed in the openstack/kolla-ansible 7.2.0 release.
1800132,2019-12-12 10:04:22 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc2 release candidate.
1800132,2019-12-04 13:44:42 UTC,"Reviewed:  https://review.opendev.org/697255
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=8a3afd4ea53601ca24ad5f6e873c0552fb0dd139
Submitter: Zuul
Branch:    stable/train"
1800132,2019-12-04 13:30:14 UTC,"Reviewed:  https://review.opendev.org/697256
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=021f55b2fa7b66aa37d2859331e48b1383474da7
Submitter: Zuul
Branch:    stable/stein"
1800132,2019-12-04 10:22:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/697257"
1800132,2019-12-04 10:20:16 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/697255"
1800132,2019-12-04 10:16:19 UTC,"Reviewed:  https://review.opendev.org/696757
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=21488710d68450eac4ace21bea4c5f929e0189d4
Submitter: Zuul
Branch:    master"
1800132,2019-11-29 19:40:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/696757"
1800132,2019-11-29 18:11:32 UTC,See https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2291dab2c9d1880efd19469df2042e2277c8b7a4 for noop reason
1800132,2019-11-29 18:10:14 UTC,CentOS 8 only warns about it though.
1800132,2019-11-29 16:07:46 UTC,"Affects debian buster which is a supported platform (train), and will affect centos 8 (ussuri)."
1800132,2019-12-04 12:55:30 UTC,"Reviewed:  https://review.opendev.org/697257
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=bebb9bc72332b85a176e8529bbcf4fb24dc2d8fb
Submitter: Zuul
Branch:    stable/rocky"
1800135,2018-10-30 16:11:03 UTC,"On 30/10/2018 15:42, Harald Sitter wrote:

> Are you sure this is still incorrect in cosmic? It seems to me this is
> only broken in bionic.
"
1800135,2018-11-20 14:38:55 UTC,"It's not an user visible problem nor impacting our default desktop, rls-bb-notfixing from a desktop team perspective"
1800135,2018-10-26 12:46:21 UTC,In Bionic version 0.8.0~20170825.94fa1e38-1ubuntu0.1 the cnake files are not installed to anywhere.
1800135,2018-10-30 15:42:29 UTC,Are you sure this is still incorrect in cosmic? It seems to me this is only broken in bionic.
1800135,2018-10-26 12:25:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800139,2019-04-07 16:14:15 UTC,This was originally reported against deja-dup but I’m guessing this is more of a duplicity issue. Feel free to kick back to me if not.
1800149,2019-01-23 20:09:13 UTC,Reported upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/852
1800149,2018-12-06 16:20:44 UTC,"That's indeed suboptimal, ideally it should be reported upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/"
1800149,2019-01-23 21:26:24 UTC,Upstream closed the bug as duplicate of https://gitlab.gnome.org/GNOME/nautilus/issues/808 which has this comment
1800150,2018-10-26 14:08:36 UTC,"I was wrong, it's still not fixed. debconf allows you to configure the ""namecheap"" value for the setting, but then when the package is configured and /etc/ddclient.conf is created, it still says ""dyndns2"" for the protocol, i.e., the setting isn't being propagated properly into /etc/ddclient.conf."
1800150,2018-10-26 18:48:00 UTC,"Dang it, I put the comment above on the wrong bug. Please disregard the comment."
1800150,2020-07-13 16:00:55 UTC,A new version will be uploaded to Debian soon. After it is accepted in Debian it will automatically propagate to the next Ubuntu release.
1800156,2020-11-23 08:58:08 UTC,Does the mouse grabbing still does not work with the latest version of QEMU? Which binaries did you use?
1800156,2021-01-23 04:18:31 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1800159,2018-11-23 00:30:22 UTC,"I agree that the workaround isn't sufficient and this should really work out of the box, so I've added this to the server team's backlog. But since it is reported fixed in Bionic and a workaround is available for Xenial, I'm prioritising other work over this bug. If someone can figure out and provide a patch, we'll help you get it landed. Otherwise, I expect this bug to remain inactive for a while, but hopefully we can get to it the next time someone from the server team tries to clear out some of the bugs open against keepalived."
1800159,2018-11-22 18:34:26 UTC,"Great, thanks!"
1800159,2018-11-22 18:12:25 UTC,"# lsmod | grep ip_
  ip_vs_wlc              16384  3
  ip_vs                 151552  5 ip_vs_wlc
  nf_conntrack          131072  1 ip_vs
  libcrc32c              16384  3 nf_conntrack,xfs,ip_vs"
1800159,2018-11-22 18:08:37 UTC,It's also a workaround
1800159,2018-11-22 17:45:55 UTC,"Understood, but if you'd like this properly fixed in Xenial, it would be very helpful to us if you could tell us if the /etc/modules workaround works for you. This will help inform our work."
1800159,2018-11-20 11:16:04 UTC,"global_defs {
    notification_email {
        <email address hidden>
    }
    notification_email_from <email address hidden>
    smtp_server 127.0.0.1
    smtp_connect_timeout 15
    router_id lb2.domain.tld
}"
1800159,2018-11-22 16:28:07 UTC,"Reproduced with your keepalived.conf, thanks - specifically that what goes to syslog seems to be a problem on startup without ip_vs manually loaded, and after a manual modprobe there is less of an error (I get other errors presumably because I don't have your network set up)."
1800159,2018-11-19 18:52:30 UTC,Can you share your config /etc/keepalived/keepalived.conf ?
1800159,2018-11-14 11:38:57 UTC,"Hi Thorsten,"
1800159,2018-11-12 22:33:56 UTC,"This looks as though you are running keepalived from within a container. Due to the isolation of containers, applications running within the container cannot load kernel modules. Once you manually load the module, keepalived can use the module from within the container."
1800159,2018-10-26 14:19:41 UTC,Bionic is working
1800159,2018-11-22 17:27:04 UTC,"My work-a-round is that I'm knewing this problem and so I load it manually.
Bionic is working, I wrote it 2018-10-26.
We still use Debian 6-9 and  Ubuntu 12-18"
1800159,2018-11-16 10:00:16 UTC,@pqa It's not running in a container we want stable software
1800161,2018-10-26 20:25:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613682"
1800161,2020-04-30 16:02:53 UTC,"Change abandoned by Lance Bragstad (<email address hidden>) on branch: master
Review: https://review.opendev.org/613682
Reason: Abandoning this since I haven't updated it in over a year."
1800167,2019-09-05 11:16:24 UTC,Forwarded upstream: https://github.com/karelzak/util-linux/issues/857
1800167,2019-09-05 14:36:49 UTC,Fixed in upstream tree. Thanks for your report.
1800170,2018-10-30 15:59:18 UTC,Gracias por la respuesta.  Gabriel Pascual
1800170,2018-10-27 12:20:59 UTC,"Your logfile shows many errors of type
Warning: Expected end of file in C:\1-MSTS\ROUTES\sob\WORLD\w-005803+014705.w:line 20
and errors of type
Warning: Missing TrackShape in tsection.dat : 21566."
1800173,2018-12-03 22:53:16 UTC,"I think this was a disk space issue. I think it's fixed by removing the pod vms during clean, which is done now."
1800176,2019-05-13 08:18:04 UTC,Can you attach a bundle that shows this behavior? We have been using and testing glance-simplestreams-sync successfully for some time and have not seen this issue.
1800176,2019-07-13 04:17:59 UTC,[Expired for OpenStack glance-simplestreams-sync charm because there has been no activity for 60 days.]
1800185,2019-04-01 16:39:32 UTC,"For Stein, this was handles as part of https://review.openstack.org/624773 - we may wish to do a partial backport for the part that handles the env.d files."
1800185,2020-12-03 12:58:11 UTC,"Unfortunatelly we will not backport back this change since even Stein is now under extended maintenance.
If issue still takes place please - revive this bug report."
1800189,2018-10-30 06:27:28 UTC,"The way the Ubuntu Serverguide master code is done, it can not be in a separate page. It has to be added to the current content."
1800189,2018-10-29 16:20:24 UTC,Mr. Basak:
1800189,2018-10-29 13:46:35 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1800196,2019-05-09 14:23:01 UTC,I have the same issue.
1800196,2019-06-08 01:37:13 UTC,I am wondering if a JVM can be used to more reliably trigger the bug and thus help isolate it? Hopefully someone else reading this has an opinion...
1800196,2019-06-08 05:33:59 UTC,"Wish I had the ability to edit a post...
Scratch most of my last post. There is a problem with vdagent~, but I just refuted my previous post. I do have the error, but I am 99.9% certain that it does not cause the problems that I am experiencing which brought me to this bug report. Apologies if the previous post caused any inconvenience."
1800196,2019-06-09 20:17:45 UTC,"Hi all,
I have the same issue with a dell laptop Inspiron 15.
Step to reproduce:
Plug HDMI cable 4k ready, of course connected to 4k screen."
1800196,2019-06-10 07:08:07 UTC,"Hi all,
I have the same problems...
I just upgraded my system...
It freaks me out..."
1800196,2019-06-10 07:10:52 UTC,"Jun  9 23:57:05 ubuntu spice-vdagent[1306]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Jun  9 23:57:05 ubuntu dbus-daemon[670]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jun  9 23:57:05 ubuntu systemd[1]: Started PackageKit Daemon.
Jun  9 23:57:06 ubuntu gnome-session[1032]: gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Jun  9 23:57:06 ubuntu gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Jun  9 23:57:06 ubuntu gnome-shell[1077]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
Jun  9 23:57:06 ubuntu gnome-shell[1077]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1477]: reference to undefined property ""MetaWindowXwayland""
Jun  9 23:57:06 ubuntu ModemManager[779]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0': not supported by any plugin
Jun  9 23:57:06 ubuntu dbus-daemon[670]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.62' (uid=121 pid=1311 comm=""/usr/lib/gnome-settings-daemon/gsd-color "" label=""unconfined"")
Jun  9 23:57:06 ubuntu gnome-session-binary[1032]: Entering running state
Jun  9 23:57:06 ubuntu xbrlapi.desktop[1391]: openConnection: connect: 没有那个文件或目录
Jun  9 23:57:06 ubuntu xbrlapi.desktop[1391]: cannot connect to braille devices daemon brltty at :0
Jun  9 23:57:06 ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles...
Jun  9 23:57:06 ubuntu colord[1392]: failed to get edid data: EDID length is too small
Jun  9 23:57:06 ubuntu dbus-daemon[670]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Jun  9 23:57:06 ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles.
Jun  9 23:57:06 ubuntu gsd-color[1311]: failed to get edid: unable to get EDID for output
Jun  9 23:57:06 ubuntu gsd-color[1311]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
Jun  9 23:57:16 ubuntu systemd[1]: Created slice User Slice of hfu."
1800196,2019-10-17 14:24:33 UTC,Thanks Yas
1800196,2019-06-11 00:49:27 UTC,"Hi all,
We have found a workaround, for the display not usable.
I give it here for people like me who were stuck... with dell."
1800196,2019-09-15 15:09:25 UTC,"Hi all,
I've found this messages in systemd journal but in my case it was a bare metal install of Ubuntu 18.04, so I don't see the need to have spice-vdagent installed (that I understand is for virtual machine guest). Remove it is not an option because it will remove ubuntu-desktop.
I tried then to disable it with:
$ sudo systemctl disable spice-vdagent"
1800196,2019-09-15 17:15:44 UTC,"Thanks for sharing yas! That approach seems to take care of the problem, it doesn't show up in my log any longer."
1800196,2020-02-14 11:46:29 UTC,"Hi Yas and everyone on this page!
I'm totally 'rookie' in the world of Ubuntu LinuX.. I just some weeks ago arrived from ""Bill's World"" :D and firstly must to say a big sorry about my English. I have some important question about your ""bug solution"". Repeat: I'm really 'rookie' so please don't laugh on me."
1800196,2020-02-14 15:36:15 UTC,"I I did it!
1.) I opened the  /etc/xdg/autostart/spice-vdagent.desktop   file with ""sudo gedit"".
2.) I modified the file to:
[Desktop Entry]
Name=Spice vdagent
Comment=Agent for Spice guests
Exec=/usr/bin/spice-vdagent
Terminal=false
Type=Application
Categories=
X-GNOME-Autostart-Phase=Initialization
NoDisplay=false
X-GNOME-Autostart-enabled=false
3.) Saved
4.) After I did it same with the  /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop   file.
(Interesting: when I browsing this folder with ""Nautilus"", just a ""Spice vdagent"" named file was there... but when I opened this folder with ""sudo gedit"" there a ""spice-vdagent.desktop"", so I opened.)
5.) Saved
6.) Finally: $ sudo systemctl stop spice-vdagentd  and  $ sudo systemctl disable spice-vdagentd
7.) Reboot... and the ""Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0"" error message is gone!
P.S: How the heck can modified my comments? I can't find..
:)"
1800196,2019-06-10 07:19:57 UTC,"I have a suggestion that if the ubuntu can backup itself when upgrade ,when if it  crashed , I can restore it, now I have to rollback it to a very old version..."
1800196,2019-04-28 05:12:38 UTC,"I'm not a programmer/developer, but just a user. I can answer this question, however:"
1800196,2019-03-17 03:27:13 UTC,"I cant speak to other peoples issues - I trigger the message in the system journal, by booting my system.  I understand gdm3 starts the spice-vdagent program?  I have not noted any ill effects, and I've been simply ignoring it."
1800196,2019-04-03 00:25:26 UTC,"I have the problem every time I login, within ~30 seconds, without doing anything.
I get an error popup asking to ignore or report the problem. When I click on ""report problem"", the popup disappears and not sure if anything occurs."
1800196,2018-11-03 08:27:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800196,2018-11-08 22:30:29 UTC,Is there a related error happening with gnome-session-binary?
1800196,2018-11-19 19:19:43 UTC,"spice-vdagent
Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0"
1800196,2018-11-20 09:27:11 UTC,"Thank you for your bug report, do you have other problems or only that warning? https://bugzilla.redhat.com/show_bug.cgi?id=1497637 describes a similar warning"
1800196,2019-04-03 03:35:39 UTC,"Same problem here, on boot:"
1800196,2018-11-22 18:48:22 UTC,"Same error on Ubuntu 18.04 4.15.0-39-generic
I can't use virtualization because the system reboots when using it. Also I have short time random black screen and random reboots."
1800196,2018-11-23 03:41:20 UTC,I've extended my search in journalctl. Hope this helps:
1800196,2018-11-22 02:58:46 UTC,"I am getting these logs on boot:
1. Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
2. from gnome-session-be: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
3. systemd: Failed to start Service for snap application canonical-livepatch.canonical-livepatchd."
1800196,2018-12-07 11:22:04 UTC,"Same problem on 18.04 LTS:
11:26:56 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
11:26:38 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
11:25:53 gnome-session-b: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Fehler beim Aufruf von StartServiceByName für org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1"
1800196,2018-12-07 13:39:15 UTC,It's still unclear to me what's the problem is here? Is that only the warning in the log or is there a feature not working?
1800196,2018-12-07 15:11:09 UTC,In my case the system is slowing down very much and I search for the reason. Don't know whether this is one.
1800196,2019-02-24 14:11:03 UTC,Summary: a feature is not working: copy/paste works initially as expected but then fails.
1800196,2019-03-13 02:02:08 UTC,I am also getting this error in my Ubuntu 18.04 logs during boot. I tried disabling it under Startup Applications:
1800196,2019-03-14 20:47:38 UTC,Could people having the issue describe exactly what they are doing to trigger it and what's the visible impact? Is that only a warning in the journal log?
1800196,2018-12-03 21:24:21 UTC,"Hello,"
1800197,2018-12-17 10:09:13 UTC,This bug was fixed in the package gcc-6 - 6.5.0-2ubuntu1~18.04
1800197,2018-12-03 15:14:54 UTC,This bug was fixed in the package gcc-6-cross - 30ubuntu4.1
1800197,2018-12-17 09:59:20 UTC,This bug was fixed in the package gcc-6-cross-ports - 28ubuntu3.1
1800197,2018-12-17 09:59:17 UTC,This bug was fixed in the package gcc-6-cross - 30ubuntu3.1
1800197,2018-12-03 15:14:58 UTC,This bug was fixed in the package gcc-6-cross-ports - 28ubuntu5.1
1800197,2018-12-03 15:14:48 UTC,"The verification of the Stable Release Update for gcc-6 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1800197,2018-11-20 22:32:50 UTC,"Hello Matthias, or anyone else affected,"
1800197,2018-11-26 09:38:03 UTC,"the gcc-6 testsuite look good in both bionic and cosmic.  The autopkg tests look good, except for the linux autopkg test triggered by gcc-6 in cosmic.  The trigger is hard-coded in autopkg test, and can be ignored. The kernel doesn't use gcc-6 at all."
1800197,2018-11-20 22:27:14 UTC,"Hello Matthias, or anyone else affected,"
1800197,2018-11-20 22:32:04 UTC,"Hello Matthias, or anyone else affected,"
1800197,2018-12-03 15:14:35 UTC,This bug was fixed in the package gcc-6 - 6.5.0-2ubuntu1~18.10
1800197,2018-11-20 22:41:42 UTC,"Hello Matthias, or anyone else affected,"
1800197,2018-11-20 22:43:21 UTC,"Hello Matthias, or anyone else affected,"
1800197,2018-11-20 22:38:39 UTC,"Hello Matthias, or anyone else affected,"
1800202,2018-10-27 09:05:46 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1800202,2018-10-29 02:01:08 UTC,It's the clip again. Release it to get the export working.
1800202,2018-10-30 15:12:19 UTC,Thanks for the update.  This does not appear to work for either of the two platforms/versions I am using.
1800204,2020-04-23 18:51:18 UTC,"I'm going to say the same thing as bug 1801733 - this is super nifty and interesting, but realistically is not a concern and will most likely never get addressed."
1800219,2018-11-01 16:47:20 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1800220,2018-11-28 01:26:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800222,2018-11-11 09:14:30 UTC,"Hi Andrea,
I've checked on the code. The program seems to be frozen during the execution of this module
PIEHidDotNet.PIEDevice.WriteData(Byte[] wData)
which is called by following OR code line
            Device.WriteData(WriteBuffer);
within the SetLEDs module.
PIEHidDotNet.PIEDevice.WriteData(Byte[] wData) is a standard Raildriver module (not an OR module), which hasn't been written by OR people.
So I really can't help you. Maybe there is a hardware problem in your Raildriver or in your PC port, or some incompatibility problem of the hardware with that version of the Raildriver module."
1800222,2018-10-27 12:29:08 UTC,"""Thread hang"" means that the computer was too slow in computing OR code. Your computer is not a slow machine, so the problem is probably caused by the many log messages you get. If you look at the logfile, you will see many lines of the type
Warning: File ..\..\Suono_Italiano\XXVentilo.wav missing from D:\Programmi\Microsoft Games\Train Simulator\trains\trainset\FS_E464_CC\sound
This means that you haven't installed ""Suono_Italiano"".
I see also many warnings of type
Warning: Signal referenced in .w file -5672 14413 as TrItem 13792 not present in .tdb file
which means that there is incoherence between world files and the tdb file. This is a problem of the route, although probably it is not the cause of your crash."
1800222,2018-10-27 16:12:10 UTC,I've tested the RailDriver with differents Activity/Routes and I always have the same problem. Without RailDriver it works without crashes and lags.
1800224,2018-10-26 21:47:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/613695"
1800226,2018-12-07 15:27:51 UTC,I've push what I think is an appropriate fix to:
1800240,2018-10-26 22:29:56 UTC,"Work in progress in the working repo, branch user/jeffdavis/lp1800240-secure-ldap-wip"
1800240,2019-02-08 20:37:00 UTC,"On further testing, LDAPS appears to be at least minimally functional. I tried prefixing my LDAP hostname with ""ldaps://"" and it seems to work."
1800245,2018-11-21 14:14:01 UTC,"Thanks Lazer,"
1800250,2018-11-19 10:55:20 UTC,I'm still experiencing this issue with the following newer kernels too:
1800250,2018-12-12 18:39:57 UTC,Latest update has now made all kernels none bootable. Any update on this? I am more than willing to work with anyone to figure a solution out.
1800258,2018-10-27 12:54:34 UTC,Fair enough - did just that: https://github.com/KiCad/kicad-mac-builder/issues/227
1800258,2019-11-20 23:35:20 UTC,"According to the discussion in the mac packaging bug tracker, this bug is just a symptom of the Eeschema python path problem."
1800258,2018-10-27 12:39:15 UTC,"Actually, if you could file this over at https://github.com/KiCad/kicad-mac-builder, this is a macos packaging issue, and that's where I fix those. :)  Thanks!"
1800260,2019-07-19 15:36:05 UTC,"(and both are focused, of course)"
1800260,2019-10-11 13:51:54 UTC,"The gtk-common-theme snap in the candidate channel has now been promoted to stable, so I'm closing this bug."
1800260,2019-10-11 09:33:47 UTC,"I am not sure exactly which commit fixed the problem, but I suspect it's an update in Yaru itself.
Possibly one of those:"
1800260,2019-10-11 09:06:38 UTC,"As pointed out by Nicolás in https://forum.snapcraft.io/t/call-for-testing-chromium-browser-deb-to-snap-transition/11772/14, the gtk-common-themes snap in the candidate channel appears to fix the problem."
1800260,2019-07-19 15:35:04 UTC,"I'm attaching a screenshot demonstrating my claim above, showing gnome-calculator as a snap on the left, and from the deb on the right. This is in a clean and up-to-date disco VM, with Adwaita as the default theme. Colours clearly aren't right with the snap."
1800260,2019-07-19 15:14:30 UTC,"This doesn't appear to be chromium-specific, nor Yaru-specific. I initially thought that only Yaru was exhibiting an incorrect background color for the focused headerbar, but I am now seeing an incorrect color with the gnome-calculator snap when using Adwaita."
1800260,2018-11-12 09:03:19 UTC,"Thanks for the report Jeff. I can reliably observe the problem in a bionic VM.
I also tested the snap in the candidate channel (based on core18), and there are also issues with the custom rendering of the window title bar and borders, although they are different (only the close button is visible, minimize and maximize can be hovered and clicked but they are not rendered properly)."
1800260,2019-07-19 14:32:50 UTC,"I tested in an XFCE/XUbuntu session, and the focused headerbar color was correct, so there's something specific to the Ubuntu/GNOME session."
1800260,2019-06-20 16:53:33 UTC,Preliminary investigation: the code in chromium responsible for looking up the theme color for the header bar is there: https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/gtk_ui.cc?type=cs&l=864.
1800260,2019-06-26 13:20:12 UTC,I updated the title to reflect the fact that only Yaru (or communitheme on older releases) seems to be affected. All the other themes that I tested behave correctly.
1800260,2019-06-13 15:30:10 UTC,"Updated the bug title because all chromium snaps are based off core18, and the symptoms are slightly different to what was initially reported."
1800260,2019-06-28 09:28:43 UTC,"I modified Yaru in the gtk-common-themes snap with different, garish colors for the focused and unfocused headerbar. In other snaps such as gnome-calculator these new colors were picked up as expected. In chromium, only the unfocused color was applied, the focused one remained (242,242,242)."
1800260,2019-07-19 14:05:04 UTC,"I tested a few more things, unsuccessfully:"
1800260,2019-06-27 16:02:29 UTC,"This is not a confinement problem, as the same happens when the snap is installed in devmode."
1800261,2018-10-27 12:09:37 UTC,"What you want is already available in the next version of Inkscape:
* You can now add arbitrary directories to load fonts from
* There's preliminary support for the CSS @font-face rule
  (currently supported are TTF and OTF fonts on the local drive)"
1800261,2018-10-27 12:11:29 UTC,P.S. Development builds are available at https://inkscape.org/release/master/
1800264,2019-01-07 08:22:21 UTC,"The verification of the Stable Release Update for libtorrent-rasterbar has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1800264,2019-01-07 08:22:16 UTC,This bug was fixed in the package libtorrent-rasterbar - 1.1.9-1ubuntu0.1
1800264,2019-01-03 13:09:00 UTC,"Thanks Brian, weirdly missed receiving notification about this update so would have checked sooner!"
1800264,2018-12-11 18:27:47 UTC,"Hello stupid, or anyone else affected,"
1800264,2018-12-11 18:27:13 UTC,It doesn't seem worth fixing but the debdiff has an extraneous line removal in debian/changelog.
1800264,2018-12-05 12:04:27 UTC,This won't be fixed in upstream boost package so instead I have made an upstream request to fix the package that should propagate to Disco https://salsa.debian.org/debian/libtorrent-rasterbar/merge_requests/1
1800264,2018-12-05 11:58:26 UTC,Created a debdiff to fix the 1.1.9 package on Cosmic.
1800264,2018-11-16 12:34:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800264,2018-11-15 12:11:01 UTC,So the backward compatibility links were broken in libboost_python 1.67:
1800264,2018-11-15 10:47:54 UTC,The issue seems to be that in Cosmic the libboost-python lib naming convention has changed and that affects the debian rules scripts picking the correct lib python version.
1800264,2018-12-09 13:38:55 UTC,This bug was fixed in the package libtorrent-rasterbar - 1.1.11-2
1800264,2018-11-15 12:23:16 UTC,Upstream merge request created: https://salsa.debian.org/debian/boost/merge_requests/4
1800265,2018-11-12 08:43:35 UTC,"Hi,"
1800265,2018-10-31 19:40:29 UTC,"Hi,"
1800265,2018-10-31 10:00:39 UTC,"Hi,"
1800268,2019-07-18 08:34:31 UTC,Cosmic is now 'end of life'
1800273,2020-01-30 14:39:55 UTC,"An empty string being a synonym for ""disabled check"" seems to be used pretty consistently within the nrpe charm (e.g. zombies, load, swap, mem, etc.), although we could additionally allow 'False' to mean the same thing."
1800277,2018-10-29 10:01:05 UTC,"I can do that if really required, but this is not a bug with my system - it's just the way the system works right now, so I'm suggesting an idea for how we can make it better :)"
1800277,2018-10-29 02:28:33 UTC,Please run this command to send us more information about the system:
1800277,2018-10-29 11:12:59 UTC,apport info added.
1800277,2018-10-29 11:12:23 UTC,apport information
1800277,2018-10-30 11:53:41 UTC,Thanks for the info and reporting upstream!
1800277,2018-10-29 10:23:45 UTC,"it's better if bugs are opened with apport so they get proper tagging for the ubuntu version they are reported against, etc, but I don't think it's a requirement for that one"
1800277,2018-10-29 10:18:23 UTC,"Ideally that would be reported upstream (https://gitlab.gnome.org/GNOME/gdm/issues/), there is more chance to have one of the project contributors looking at the problem there"
1800277,2018-10-29 10:17:41 UTC,"Yes, in the least it helps us track the affected release and package versions."
1800277,2018-10-29 11:12:22 UTC,apport information
1800277,2018-10-29 11:19:22 UTC,Reported as https://gitlab.gnome.org/GNOME/gdm/issues/438.
1800278,2018-10-27 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1800278,2018-10-27 16:58:48 UTC,i´m unable to run this command due to the nature of this bug
1800278,2018-10-27 17:03:09 UTC,i´m unable to run this command due to the nature of this bug on my laptop
1800278,2018-10-29 18:52:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1800278,2018-10-30 09:03:12 UTC,"hello,"
1800278,2018-10-30 09:10:43 UTC,bug confirmed
1800278,2019-03-07 07:13:54 UTC,Does this still happen on an up-to-date system?
1800280,2019-05-19 19:52:29 UTC,"So, is there any progress on this?"
1800280,2019-02-15 13:32:22 UTC,"> > What do you exactly mean by ""setting ZSH as the default shell""?
>
> I just mean using chsh to set the default login shell. /bin/sh is left unchanged.
"
1800280,2020-01-05 09:42:32 UTC,"Maybe the snapd packagers should not rely on the assumption, that every user is using bash as login shell? More and more programs are only available as snaps, e.g. chromium-browser."
1800280,2018-11-03 15:26:25 UTC,"> What do you exactly mean by ""setting ZSH as the default shell""?
"
1800280,2018-11-03 13:31:14 UTC,"> Either Ubuntu's zsh package should do the same (or something similar), or Ubuntu must put important environment variable stuff somewhere else and have only bash-specific stuff in /etc/profile and /etc/profile.d.
"
1800280,2019-02-15 04:20:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800280,2018-11-03 15:13:50 UTC,"Hi Martin,"
1800284,2019-01-11 18:52:48 UTC,"Hi, thanks for your interest."
1800284,2019-01-14 10:02:49 UTC,Thanks!
1800284,2019-07-01 13:37:57 UTC,The bug has been fixed in the current version
1800284,2019-01-10 14:02:34 UTC,"Indeed, that's still an issue in the current version and seems an upstream one. Could you maybe report it to them as well on https://gitlab.gnome.org/GNOME/gnome-calculator/issues ?"
1800285,2018-10-27 16:37:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800285,2018-10-28 07:31:29 UTC,"I uploaded a huge file and that wouldn't copy or download back to my computer. Perhaps because it was a copyrighted file, or because it was so large. Error message screenshot included. Clicking retry multiple times got the same result."
1800285,2018-10-28 07:37:14 UTC,Trying with a smaller (still large; ~30 Mb) it worked perfectly!
1800285,2018-10-29 23:31:33 UTC,Tried today with a large textfile (#kde channel from ~2012 to now!) about 195 Mb with perfect success. Uploaded it from the Gdrive browser window from my computer. Opened Dolphin to Network > Gdrive and moved it back to my Downloads folder.
1800288,2018-10-30 19:49:32 UTC,"This is fixed, probably by an update."
1800288,2018-10-30 21:15:29 UTC,The issue only did not occur for a few hours. The reason for the change is unclear.
1800291,2019-05-12 19:50:11 UTC,I think it's reasonable to only update when the prior no longer exists
1800291,2019-05-12 14:52:10 UTC,"@Jon, I'm not sure the correct answer is always to change it.  Let's say you highlight ""Chassis GND"" and then see a connection that ought to go to ""Audio GND"".  If you correct the bad connection, you don't want the highlighting to change to ""Audio GND""; you probably want it to stay ""Chassis GND""."
1800291,2019-05-12 19:47:46 UTC,For now it keeps the named net but makes sure the highlighting is updated.
1800291,2019-05-12 14:02:21 UTC,"Jeff, FYI I haven't looked at this problem, but thinking about it very quickly, it seems possible that when you are extending a highlighted net with new wires, the highlighted net name could change (for example if the new wires connect to a higher-priority label) so that will need to be considered in the fix."
1800295,2018-10-27 16:24:09 UTC,Probably related: https://unix.stackexchange.com/questions/369097/mouse-left-click-stops-working
1800295,2018-10-27 17:01:28 UTC,Xorg.log
1800305,2018-11-25 14:54:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800305,2020-02-28 11:42:04 UTC,"Paramétrage de python3 (3.6.7-1~18.04) ...
E: py3compile:183: cannot create directory /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or directory')
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/aboutdialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/aboutdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/aligndialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/aligndialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/cleandialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/cleandialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/colorcaldialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/colorcaldialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/devicesetupdialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/devicesetupdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/deviceuricombobox.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr5.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr5_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr_ext.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabgrouptable.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabnametable.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabwindow.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabwindow_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/faxsetupdialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/faxsetupdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/filetable.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/firmwaredialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/firmwaredialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/infodialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/infodialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/linefeedcaldialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/linefeedcaldialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/loadpapergroupbox.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/makecopiesdialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/makecopiesdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/mimetypesdialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/mimetypesdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/nodevicesdialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/nodevicesdialog_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/plugindiagnose.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/plugindiagnose_base.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/plugindialog.py'
[Errno 2] No such file or directory: '/usr/share/hplip/ui5/plugindialog_base.py'
[Errno 2] No such file or ..."
1800310,2021-02-15 18:56:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800312,2018-12-23 00:25:12 UTC,Any updates on the current situation?
1800312,2019-06-23 23:36:31 UTC,Sorry but because this bug report is incomplete I need to mark it as invalid. If there are any updates please let me know.
1800312,2018-10-28 01:26:21 UTC,Thanks for the info. I will try when libgphoto2 is updated.
1800312,2018-10-27 23:57:01 UTC,"Hi,"
1800312,2018-10-28 00:32:35 UTC,"Thanks for the additional files. It looks like you are having many problems on your system, all related to device removal and file reading / writing. I suspect the root cause is a libgphoto2 bug, but I can't be sure. It's possible you are also seeing a hardware fault.  Recently another Nikon user reported a libgphoto2 problem so I'm inclined to suspect that. A latest version of libgphoto2 is 2.5.20, which is newer than on your system. I'd wait until that release is in Manjaro and test it again."
1800312,2018-10-27 23:44:45 UTC,"Hi, thank you for your bug report and for including the log file. Can you please attach your configuration file, which is ~/.config/Rapid Photo Downloader/Rapid Photo Downloader.conf. Also, please attach all the other log files."
1800319,2019-12-03 04:55:34 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10633"
1800319,2019-12-16 01:37:23 UTC,Robert's comment on the patch on reviews.mahara.org:
1800319,2019-12-29 22:54:22 UTC,"Cecilia and I discussed this. This change here is an ""interim"" solution until we have better collection permissions, which requires a major overhaul of the collection system though."
1800319,2020-02-03 03:33:56 UTC,"- Gerrit: https://reviews.mahara.org/#/c/10633/ Patch set 12
- Browser/s tested: desktop Chrome
- Theme: Raw"
1800319,2020-02-03 04:44:49 UTC,"Reviewed:  https://reviews.mahara.org/10633
Committed: https://git.mahara.org/mahara/mahara/commit/467c1163bafcf115e1c45dcb57067d621b39a846
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1800320,2018-11-01 16:44:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1800320,2018-11-15 15:54:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800323,2018-10-28 08:11:20 UTC,"I think what's happening is that ""alsa"" and ""pulseaudio"" both get the same description in gnome software, which is confusing. I don't know why it then doesn't toggle the right one."
1800323,2018-10-29 04:33:30 UTC,"Thanks for the reply, John. The ALSA + PA explanation makes sense (I have both).
Good point about superfluous permissions, I uninstalled for now and asked the developer why that is."
1800323,2018-10-31 11:03:50 UTC,"Hi @chipaca
Here is the developer's detailed response about extra permissions in the snap: https://github.com/lettier/gifcurry/issues/29#issuecomment-434128583
Cheers"
1800326,2018-10-28 14:18:43 UTC,"I don't understand what is occurring. First of all: is this a new bug or did this occur also to older versions of Open Rails?
From your words I understand this:
1) You are a client player and you exit the game.
2) Then I read: ""I'll go back to the server"": Do you mean that you re-enter the game?
3) Then I read: ""then connect the train"": Do you mean that you couple your player train to another player train?
4) Then I read: ""and become the one"". What do you mean?
5) Then I read: ""Trains are merged"". Do you mean that one train goes into the other instead of coupling?
6) Then I read: ""Sometimes it reverses the fitting 180 degrees"". So you mean that the consist is fully reversed? First car becomes the last one and so on?
Please answer all questions as clearly as possible."
1800326,2018-11-02 18:26:08 UTC,"Due to message transmission rate, that may be too low to recognize train coupling, in Multiplayer train coupling not always succeeds and trains enter one into the other.
An additional train coupling check has been introduced for Multiplayer with x.4288, which should fix this problem."
1800329,2018-11-01 06:26:47 UTC,I tried to find a reasonable solution and looks that there are different approaches.
1800329,2018-10-29 15:43:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800330,2019-09-19 08:55:14 UTC,I believe this is because the package acpica-tools uses alternatives and the commands provided by the package actually have different names.
1800330,2019-09-19 09:01:00 UTC,The acpica-tools package can make a change which will allow command-not-found to recognize acpidump and acpixtract as a command. From command-not-found-extractor's README.md:
1800332,2019-03-05 16:34:53 UTC,Was this fixed wehn moving to SVG icons?
1800340,2018-11-29 10:39:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800343,2018-10-28 23:22:49 UTC,2.2 ubuntu studio 18.04
1800343,2018-10-28 23:22:16 UTC,"I can reproduce with Reloop TerminalMix2 & TerminalMix4.
I can see the touch signals are sent to the script, but I need to cycle through
 engine.scratchEnable(deck, 800, 33+1/3, alpha, beta);
 engine.scratchDisable(deck);
once until the scratch ticks are registered by the engine."
1800343,2018-10-28 17:41:18 UTC,I just tried master and the latest 2.1 buildserver build on macOS 10.13.6 with a Hercules 4-Mx and can't reproduce. I'm using the built-in Hercules 4-Mx preset.
1800343,2018-10-28 16:27:17 UTC,I can confirm this on Linux (Debian) as well.
1800343,2018-10-28 17:58:30 UTC,Sean -- what controller are you able to repro with?
1800343,2018-10-28 15:24:26 UTC,I am surprised we have not had reports about this from other macOS users. Can you reproduce this on other Macs?
1800344,2018-10-28 12:23:42 UTC,"The attachment ""Patch to PyGIT.py"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1800344,2018-11-29 05:43:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800344,2018-11-29 05:45:37 UTC,Applied the changes to usr/lib/python2.7/dist-packages/tracopt/versioncontrol/git/PyGIT.py and source browsing now works correctly.
1800347,2018-10-28 21:26:36 UTC,dhcp-range for static ranges is
1800348,2018-11-01 19:11:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800355,2019-01-09 08:23:57 UTC,"Hi, please upgrade to Kile 2.9.92."
1800355,2019-07-07 10:15:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800355,2019-07-07 10:22:18 UTC,"This behaviour hits me recently, upgraded to bionic LTS from 16.04 LTS. Did not experience this before."
1800355,2020-03-08 11:49:46 UTC,Is there an upstream bug report for this since clearly nobody's reading this?
1800355,2019-01-09 08:14:35 UTC,SUMMARY
1800357,2018-11-01 16:42:32 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1800357,2019-05-22 18:48:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1830066, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1800367,2019-09-17 10:05:15 UTC,Migrated to https://github.com/widelands/widelands/issues/1720
1800367,2018-10-29 12:12:48 UTC,"you are right, Gun, let me update my wording: it was intended for local games..."
1800367,2018-10-28 19:45:27 UTC,"Okay makes sense. The description, though, is a little misleading:"
1800367,2018-10-28 19:59:00 UTC,"Oops, should be singleplayer.
Perhaps should be disabled in multiplayer altogether."
1800367,2018-10-28 19:32:46 UTC,"This feature was not intended for multiplayer, in fact it was intended for AI training..."
1800367,2018-10-29 06:35:20 UTC,I find it useful in multiplayer too for local testing
1800368,2018-12-23 16:56:44 UTC,new update at startup it show alott if words something about spectre fail to load something and more maybe il post a picture
1800368,2018-11-24 17:07:21 UTC,RE Walter Lapchynski & Ian Bruntlett:And 19.04 versions
1800368,2018-11-24 16:53:44 UTC,RE Ian Bruntlett:Ok i will check with memtest just to see if anything come up but doubt it because its with 18.10 versions only thanks
1800368,2018-11-24 16:46:41 UTC,"RE Walter Lapchynski:No its with 18.10 (ubuntu , lubuntu) versions the install issue(from usb) , hashes if you mean if it is from the official sites(lubuntu.me) then yes if it is something else i dont know what it is"
1800368,2018-11-23 18:37:45 UTC,"Hi All,"
1800368,2018-11-23 18:26:36 UTC,"If you can't install it, that's a completely different issue. What I'm seeing, though, is that you're having trouble installing ANY image, correct? Have you checked the hashes on the image?"
1800368,2018-11-23 16:50:08 UTC,"RE #5:One of the bug report(#1803827) is from a different computer but similar bug not the same, if is that what you mean {So you can't install 18.10...... but you've installed 18.10?}"
1800368,2018-11-23 16:30:12 UTC,RE #5:Assuming you've seen the other bug reports the cdrom/casper/filesystem. squashfs error bug is when trying to install from USB (it boots but cant install) even from windows virtualBox
1800368,2018-11-22 00:38:22 UTC,So you can't install 18.10...... but you've installed 18.10?
1800368,2018-11-21 22:56:48 UTC,RE #5 Post:
1800368,2018-11-21 05:49:26 UTC,"I'm not asking for you to do a bug report. Actually, this is a bug report. I'm asking for:"
1800368,2018-11-04 21:45:57 UTC,i cant do a a bug report i tried many ways in lubuntu because nothing is crashing its just doesn't shutdown reboot or sleep(wakes up 1 second after it sleeps) for the day a change cpu from  AMD Athlon 64 TF-20 to AMD Turion 64 X2 TL-68 for the Acer Aspire 5516
1800368,2018-11-02 05:39:12 UTC,"I'm sorry but there is not sufficient information here for me to reproduce this bug. Could you explain in more detail the steps to reproduce this bug, what the expected results are and what the actual results are?"
1800368,2018-11-23 16:58:14 UTC,RE Walter Lapchynski:By the way thanks for the support you're the only one responding
1800369,2019-11-26 14:51:52 UTC,I just set it to LOW instead of WISHLIST as it's not nice-to-have but seriously affects the GUI feedback as well as replay gain leveling of newly added tracks. See my first comment for more context.
1800369,2018-12-23 11:53:13 UTC,"PlayerManager uses a single analysis queue/scheduler for regular, preview, and sampler decks. This might be split into separate queues/schedulers that are suspended and resumed internally according to some prioritization strategy."
1800369,2018-10-30 18:11:00 UTC,"In the case I described the overlay text is just irritating (""what's happening in the background? Why that delay?"") because the reason for delay is not obvious, even less with hidden samplers."
1800369,2018-10-30 22:14:39 UTC,Please consider postponing any code changes until https://github.com/mixxxdj/mixxx/pull/1624 has been merged. I'm not willing to resolve more merge conflicts after I completed working on the multi-threaded analysis long ago.
1800369,2018-10-31 06:34:37 UTC,"Oh yes. I think a fix should be merged together with your changes.
do you like the proposed change here?"
1800369,2018-10-28 23:10:00 UTC,"this gave me some headaches, especially when I presented Mixxx during our open-decks sessions. usually, if waveforms were missing it was mostly an indicator my sound devices were unconfigured/broken."
1800369,2018-10-30 15:41:03 UTC,We have an overlay text on the waveform overwiew. Should we add something to the scrolling waveform as well?
1800375,2018-11-06 03:35:42 UTC,Fixed by: https://review.openstack.org/#/c/613807/
1800375,2019-01-25 03:24:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/633106"
1800375,2019-02-16 21:12:10 UTC,"Reviewed:  https://review.openstack.org/633106
Committed: https://git.openstack.org/cgit/openstack/zun-tempest-plugin/commit/?id=b2313233978525444baa7d8b7f3a7f9aa90f1182
Submitter: Zuul
Branch:    master"
1800378,2018-10-28 20:37:35 UTC,"Please tell us what version of Ubuntu Mate you use , what video drivers... Until then i will mark this as incomplete."
1800378,2018-11-12 17:32:54 UTC,"Hi there, have you abandoned me? Is there anything else I can do?"
1800378,2018-10-29 20:54:42 UTC,"Ubuntu Mate 18.04.1 LTS
Intel HD Graphics Intel V10149
Intel OS Tech Center 3.0 Mesa 18.0.5"
1800378,2018-10-30 20:21:06 UTC,THANKS for your time. syslog output as requested - Attempted to shutdown laptop at Oct 30 20:00:00
1800378,2018-10-30 17:16:33 UTC,"Ok let's pull some logs. Try to reproduce the problem and after that please open terminal and type sudo mate-system-log and then copy from the syslog the output , share it here and tell us what was the time when you tried to shutdown the laptop."
1800394,2020-10-22 15:34:42 UTC,Is now working in 2.3 r7650
1800394,2020-10-22 15:35:45 UTC,I was too quick..still broken
1800394,2020-10-22 16:26:31 UTC,https://github.com/mixxxdj/mixxx/pull/3203
1800397,2018-10-28 23:08:53 UTC,"Upon automatically re-running dpkg --configure -a, the system was able to sucessfully update.  A selection of warnings from the screen (running in `screen`, so I missed quite a few)"
1800398,2018-12-09 09:17:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800401,2018-10-29 00:40:09 UTC,The OVMF BIOS used can be downloaded from  https://dev.gentoo.org/~tamiko/distfiles/edk2-ovmf-2017_p20180211-bin.tar.xz
1800401,2020-11-13 16:05:23 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1800401,2021-01-13 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1800402,2019-06-20 00:31:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800406,2019-07-11 08:30:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800410,2018-11-03 17:23:10 UTC,"Should be fixed with 1.0.1-2, scheduled to be included in disco."
1800413,2018-11-05 01:37:38 UTC,set to high as the bug only happen to package in ppa (not in update channel).
1800415,2019-09-19 22:10:24 UTC,"Hello Kyra,"
1800415,2019-10-09 20:28:59 UTC,"I don’t think that would be a difference? Maybe this got fixed from the password handling rework after the passphrase problems we hit. If this can’t be reproduced, I’ll close for now. Please re-open if you still hit this bug on version 40 or above. Thanks!"
1800432,2018-10-29 09:13:25 UTC,When build package on lp， we should add ”export NO_PNG_PKG_MANGLE=1“ in debian/rules to avoid optimizing png pictures
1800432,2019-04-10 14:47:14 UTC,This bug was fixed in the package ubuntukylin-theme - 1.8.2.1
1800433,2019-12-15 04:17:27 UTC,[Expired for devstack because there has been no activity for 60 days.]
1800433,2019-10-15 08:29:33 UTC,Is this issue still happening or has it been fixed in CentOS repos?
1800433,2018-11-09 08:26:05 UTC,"Thanks for the reply,"
1800433,2018-11-09 08:10:46 UTC,"Thanks for the reply,"
1800433,2018-10-29 09:30:03 UTC,"I cannot find a reference to mirror.centos.org in stack.sh or in any other devstack code, can you please show where you are getting this error? Please include your local.conf file and a copy of the output from the stack.sh run."
1800433,2018-12-20 09:49:04 UTC,so it is modified repo side issue right. you can add the workaround in tools/fixup_stuff.sh as Jens mentioned till you get that pckg in centos mirror path.
1800442,2018-11-06 19:44:06 UTC,"Hmm, unfortunately the initial run would have been different I suspect.
It looks like the cleanup partly run once and now it's just getting stuck on some leftover mounts."
1800442,2018-11-08 09:16:29 UTC,"Hey Stéphane, thanks for replying! Sorry that this is producing a different result from the first time I did the upgrade. I had a look, and I found the output from that apt run in /var/log/apt which contains:"
1800442,2019-01-08 04:17:23 UTC,[Expired for lxd (Ubuntu) because there has been no activity for 60 days.]
1800446,2018-12-15 13:09:37 UTC,I have the same issue on an acer vn7-592g and Ubuntu 18.10. I temporarily fixed by editing thermald config in /etc/thermald/thermal-cpu-cdev-order.xml to deactivate most cooling methods (guess work as the documentation for it is almost none existent)
1800446,2021-01-20 17:04:56 UTC,I am experiencing this bug in 20.04
1800446,2019-03-25 16:40:55 UTC,Do we still have this issue?
1800446,2019-02-15 23:12:56 UTC,Also affected me after upgrading from 18.04 to 18.10.
1800446,2018-12-15 13:18:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800446,2018-11-01 13:54:41 UTC,I checked that there is no difference in configuration files between Ubuntu 18.04 and Ubuntu 18.10.
1800446,2019-03-25 18:21:18 UTC,Also can you attach acpi.out by issuing the following command
1800446,2018-10-30 14:14:34 UTC,I reinstalled thermald and tried with the 4.15 kernel and still got intense throttling. I noticed that with either kernel the dmesg output still dumps this:
1800446,2018-10-30 14:59:49 UTC,Here is what I did:
1800446,2018-10-29 11:30:06 UTC,This change was made by a bot.
1800446,2018-10-29 11:47:01 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1800446,2019-02-17 03:24:22 UTC,"I suggest, disable thermald service first.
#systemctl diable thermald"
1800446,2018-10-29 13:06:48 UTC,"I created a new Ubuntu 18.10 VM and tried to reproduce this, but couldn't. No `kidle_inject` processes were started at all. I'm not sure if they should start inside a VM, though."
1800446,2018-10-29 14:16:50 UTC,I have a Dell Precision 5520. I just updated my bios and updated Ubuntu to 18.10 from 18.04 and ran into hard CPU throttling. I uninstalled thermald and everything is fine. Not sure if it would be better to blacklist kidle_inject as suggested here instead though.
1800446,2018-10-29 11:57:57 UTC,"Hi @caravena ,"
1800446,2018-10-29 16:41:00 UTC,"Justin,"
1800447,2018-10-29 15:17:17 UTC,hi Matt!
1800447,2018-10-29 15:45:45 UTC,"Andrey,"
1800447,2018-10-29 16:02:07 UTC,Strange. Can you try more recent image? 1.3.0 tag for example or 'latest'
1800447,2018-10-29 16:26:05 UTC,I got the same problem with:
1800447,2018-10-29 16:46:50 UTC,"I do not know what it can be :( I tried to execute Dummy.dummy with constant_for_duration runner and everything works with recent images. If it works for me, it means that the issue not in code of rally itself or multiprocessing. The issue can be in input data. How you are running Rally? What and where volumes/directories/files are mounted? What is version of docker?"
1800447,2018-10-29 20:13:50 UTC,"Hum :(
Let me give you some background/context information.
But first, note that the ""constant"" runner works perfectly fine in my environment."
1800447,2018-10-31 10:38:02 UTC,Today I've tested outside docker. This unfortunately led to the same problem.
1800447,2018-10-31 16:09:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/614576"
1800447,2018-10-31 16:19:20 UTC,"Andrey,
I've submitted a patch that is related to this.
Any advice from any rally expert there would be really appreciated :)"
1800447,2018-11-06 10:50:00 UTC,"Reviewed:  https://review.openstack.org/614576
Committed: https://git.openstack.org/cgit/openstack/rally/commit/?id=cfde22978a8e06bb6d6606dd2641ae647a13dabd
Submitter: Zuul
Branch:    master"
1800449,2018-11-07 09:08:03 UTC,"Perhaps the same as:
- https://github.com/lxde/lxterminal/issues/61
- https://bugs.launchpad.net/sakura/+bug/1790317
- https://github.com/Tetralet/LilyTerm/issues/134"
1800460,2019-09-23 22:26:32 UTC,"I've came here from Google search. I think it was fixed in upstream
https://github.com/jiaqi/jmxterm/commit/55dca9f2ec82246e6d7c573010a55af874f39bc4"
1800465,2019-06-13 09:19:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1769857, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1800465,2018-11-16 13:24:17 UTC,I have the exact same bug. This one seems to be related: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1769857
1800465,2019-05-01 09:58:47 UTC,Same bug here on two different laptop.
1800465,2019-03-28 21:34:15 UTC,"In general nvidia-drm.modeset=1 is required to have Nvidia PRIME enabled, which reduces (or even removes) tearing of moving images on Optimus setups."
1800465,2019-03-14 23:40:05 UTC,I also had this same bug. Adding nvidia-drm.modeset workaround helped.
1800465,2018-11-27 12:39:49 UTC,"nvidia-drm.modeset=0 disables the vsync between the Intel and Nvidia card, called Prime SYNC."
1800465,2018-11-27 08:54:15 UTC,"""I solved this just putting nvidia-drm.modeset=0 option into my grub config."""
1800465,2018-11-08 10:03:59 UTC,"yes, Gdm has issues with nvidia and KMS. Switching to Lightdm should help."
1800465,2018-10-30 23:50:32 UTC,"Oh so it seems that Ubuntu 18.10 gdm and desktop defaults to Wayland, that has probably something to do with GDM and the wayland session..."
1800465,2018-11-07 11:07:33 UTC,So I think there is an issue regarding GDM and updated Nvidia drivers...?
1800465,2018-11-07 11:05:27 UTC,A temporary workaround is to switch gdm to another display manager
1800465,2018-11-07 10:46:47 UTC,"This bug affects me too.
Ubuntu 18.10.
GeForce GTX 960M
Driver Version: 410.73"
1800465,2018-11-06 06:51:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800465,2018-11-01 10:34:36 UTC,"So, happens in Ubuntu 18.04 when you update the graphics drivers through PPA, and ONLY when using GDM.
Happens in Ubuntu 18.10 without even upgrading graphics drivers. ALWAYS and ONLY when GDM is used. Opengl works fine, vulkan doesn't."
1800465,2018-10-31 00:35:35 UTC,"Oh actually no I don't know...It's really strange and frustrating when this happens, because I was able to reproduce the problem on an Ubuntu 18.04 based distro using GDM as display manager... A way to make it working is to run ""vulkaninfo"" as sudo once, it works, then also without sudo is back to work again once you reboot..."
1800465,2018-10-30 17:45:31 UTC,"This ONLY happens on Ubuntu 18.10, no issue in 18.04"
1800465,2018-10-29 13:18:08 UTC,Those were the update packages...
1800465,2018-11-07 18:03:23 UTC,I solved this just putting nvidia-drm.modeset=0 option into my grub config.
1800465,2018-10-29 13:37:52 UTC,"I was wrong, you don't need to update."
1800475,2018-10-29 13:57:38 UTC,journal from this session
1800475,2018-10-30 02:18:41 UTC,Sounds like it could be related to bug 1799293.
1800475,2018-10-30 02:21:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800475,2018-12-24 04:46:57 UTC,"Related and possible duplicates: #1809536, #1807265, #1799293"
1800475,2019-07-22 04:05:37 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1800484,2019-08-03 15:52:21 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jason and Rogan!"
1800484,2019-08-01 14:18:33 UTC,Worked for me.  Sign off at user/rogan/lp1800484_signoff
1800484,2018-10-29 14:57:39 UTC,Here it is:
1800487,2018-12-03 22:53:41 UTC,We're going to work on a change to juju-wait for this.
1800497,2018-10-29 17:40:59 UTC,"I want to have links to libs like this
${KIPRJMOD}/../libs
It is supported with manual entering this link"
1800497,2018-10-29 16:06:27 UTC,Now it is possible only manual edit of path or from script that no user friendly
1800497,2018-10-29 17:27:22 UTC,"@Eldar, are you asking to convert paths relative the current project path automatically to ${KIPRJMOD} in the table editor?  ${KIPRJMOD} is how you are supposed to define paths that are within the current project path.  If you are asking for paths relative to something else, that concept has been rejected by the project due to past issues."
1800500,2020-10-14 12:24:43 UTC,Still a problem in Shotwell 0.30.10 on Ubuntu 20.04.
1800501,2018-10-29 17:41:34 UTC,+1
1800501,2018-10-29 19:57:39 UTC,+1
1800503,2019-03-15 20:53:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800505,2018-10-29 18:03:26 UTC,"Hi,"
1800505,2018-10-29 18:22:09 UTC,why does the main page display: MediaWiki has been installed. instead of please go to HOSTname/mediawiki to configure media wiki?
1800511,2018-10-31 18:16:45 UTC,"Reviewed:  https://review.openstack.org/614041
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=66ec5b4334cd0e1fc65f21ab21b4b088dca87f2b
Submitter: Zuul
Branch:    stable/rocky"
1800511,2018-10-31 16:35:55 UTC,"Reviewed:  https://review.openstack.org/614040
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d28e7346ec1b3730d9bedf4a1b84223b89083635
Submitter: Zuul
Branch:    stable/rocky"
1800511,2018-10-30 22:48:24 UTC,"Reviewed:  https://review.openstack.org/614008
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=643f53f5e9544d6c98833b1ae3dd472602118a1f
Submitter: Zuul
Branch:    master"
1800511,2018-10-29 21:47:09 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614041"
1800511,2018-10-29 17:59:57 UTC,"(12:54:52 PM) cfriesen: mriedem: I think the issue is that the instance originally didn't have mtu in it
(12:54:59 PM) cfriesen: then we upgraded nova, and now it would have mtu
(12:55:53 PM) cfriesen: nova on the dest doesn't need to have the mtu, but the xml that we pass the live migration needs to match the xml that was used to start the running instance."
1800511,2018-10-29 21:46:49 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614040"
1800511,2018-10-29 18:52:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/614008"
1800511,2018-10-30 08:58:54 UTC,"Reviewed:  https://review.openstack.org/614004
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=29ee8011b4e1cf5371b1aa9c6c0f930eb49fe795
Submitter: Zuul
Branch:    master"
1800511,2018-10-29 17:56:22 UTC,"FWIW I don't think https://github.com/openstack/nova/commit/2b52cde565d542c03f004b48ee9c1a6a25f5b7cd really changed how https://github.com/openstack/nova/commit/f02b3800051234ecc14f3117d5987b1a8ef75877 could have broken anything. _update_vif_xml is called from the source host using migrate data from the dest host, but as far as I know that migrate data doesn't have any information about mtu from the dest to determine what to set in the source vif config. Before _update_vif_xml, we would have just sent the source guest xml vif config to the dest and if the dest didn't support mtu it would have failed also."
1800512,2018-10-29 17:49:22 UTC,I will check and fix asap.
1800514,2020-05-16 13:04:38 UTC,Also get the 'signal #6' crash when I delete a chunk of text in the Text Editor window.
1800515,2018-10-30 11:10:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/614190"
1800515,2019-10-02 20:26:09 UTC,"Reviewed:  https://review.opendev.org/614190
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b597f759f9133964fd580d9e0eefd4cd6eb819f
Submitter: Zuul
Branch:    master"
1800516,2018-11-28 10:57:38 UTC,"Quick addition for proof:
$ juju ssh openstack-dashboard/0 sudo -s
# dpkg -l | egrep ""(neutron|octavia)""
ii  python3-neutron-fwaas-dashboard  1.5.0-0ubuntu3~cloud0             all          OpenStack Firewall as a Service - dashboard plugin
ii  python3-neutronclient            1:6.7.0-0ubuntu1                  all          client API library for Neutron - Python 3.x
ii  python3-octavia-dashboard        2.0.0-0ubuntu1~cloud0             all          OpenStack Load Balance as a service - dashboard plugin"
1800516,2018-11-28 10:54:18 UTC,"I can confirm that the octavia-dashboard package works, see attached screen shot and steps provided below."
1800519,2018-11-19 20:03:17 UTC,This bug was fixed in the package octavia-dashboard - 2.0.0-2.1ubuntu1
1800520,2018-11-01 16:40:41 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1800523,2020-03-07 15:54:56 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1800527,2018-10-30 09:24:42 UTC,"I manually edited the header for now so this issue is resolved, but we need to modify cdimage to use a core header for all of its builds by default."
1800537,2018-12-03 14:01:15 UTC,This bug was fixed in the package linux - 4.15.0-42.45
1800538,2018-11-01 16:40:31 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1800538,2018-11-09 06:37:34 UTC,"Thanks Mark Deslauriers for your feed back. Although, this is happening everytime system updates.
Is there any way to ignore or delete this error?
Thankyou for your services,
   SirJams"
1800542,2019-04-06 04:28:00 UTC,"Following the debugging instructions at https://wiki.gnome.org/Projects/NetworkManager/Debugging#Debugging_NetworkManager-openvpn was not sufficient to get debug logs; NM still spawned a separate nm-openvpn-service process instead of using the one I was running from a terminal, despite supports-multiple-connections=false being set.  Does NM have to be restarted after making this change?"
1800542,2019-04-16 17:32:01 UTC,"Thanks, attached is a complete log of an nm-openvpn-service session, ending with exit 1."
1800542,2019-04-16 13:01:25 UTC,"@Steve, right, I just gave it a try and indeed n-m needs to be restarted ('sudo systemctl restart NetworkManager' is enough, no need of rebooting)"
1800542,2019-02-14 14:49:54 UTC,Could you get a debug log as described on https://wiki.gnome.org/Projects/NetworkManager/Debugging#Debugging_NetworkManager-openvpn ?
1800542,2018-10-29 21:33:11 UTC,apport information
1800542,2018-10-29 21:50:35 UTC,"Please reproduce the problem, do a hard reset and then run this command:"
1800542,2018-10-29 22:11:21 UTC,"> Please reproduce the problem, do a hard reset and then run this command:
"
1800542,2018-10-29 21:18:57 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1800542,2018-10-29 21:33:08 UTC,apport information
1800542,2018-10-29 21:33:09 UTC,apport information
1800542,2018-10-29 21:34:06 UTC,"attached, though aside from the package number there doesn't appear to be much of use here."
1800544,2018-10-29 21:17:12 UTC,Xenial nvme-cli doesn't provide any bash completion script; this is needed only in bionic/cosmic.
1800547,2018-10-31 17:13:47 UTC,"Reviewed:  https://review.opencontrail.org/47374
Committed: http://github.com/Juniper/puppet-contrail/commit/957cddf2048584cd9f53fa39e208c876fd70cf86
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1800547,2018-11-01 12:33:07 UTC,"Review in progress for https://review.opencontrail.org/47418
Submitter: alexey-mr (<email address hidden>)"
1800547,2018-11-02 17:20:08 UTC,"Reviewed:  https://review.opencontrail.org/47418
Committed: http://github.com/Juniper/puppet-contrail/commit/037f86e39f050b146c3586be634d873892ff79fa
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1800547,2018-10-30 19:49:20 UTC,"Review in progress for https://review.opencontrail.org/47374
Submitter: alexey-mr (<email address hidden>)"
1800547,2018-10-30 19:55:24 UTC,not applicable to master
1800554,2020-03-07 11:20:06 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1800555,2018-11-01 16:40:03 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1800555,2018-11-05 20:19:55 UTC,My system is running much better. Thank you.
1800555,2018-11-05 20:19:39 UTC,My system is running much better. Thank you.
1800558,2018-10-29 22:13:16 UTC,Workaround from https://ubuntuforums.org/showthread.php?t=2346196&page=2&p=13723151#post13723151 no longer applicable to 18.04.1: fails though online updates (even 3rd party) on during install
1800558,2018-10-29 22:19:43 UTC,"Conversely https://forums.linuxmint.com/viewtopic.php?t=241379#p1289326 recommends installing offline (as well as making /dev/sda1 FAT32, possibly 0C LBA rather than 0B these days)..."
1800558,2018-10-29 22:28:29 UTC,"Cf. https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767259/comments/10 re. ""required ~200MB FAT32-formatted, bootable partition with an esp flag"""
1800558,2018-10-29 23:35:15 UTC,"For the record, the installer crashes whether online or not,
and even after manually setting the /dev/sda1 partition type to 0C,
but the system in Legacy mode (UEFI-only fails to find media) does restart into a GRUB rescue prompt,
so /dev/sda itself is bootable: just the next-stage config obviously wrong."
1800558,2018-10-30 19:36:12 UTC,"So this ideapad Z510 came with FreeDOS, ran nicely since and under Ubuntu 12.04 (up to .5) LTS and never had Windows 7-10 on it."
1800558,2019-01-31 13:05:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800561,2018-11-11 07:13:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800562,2019-02-25 17:51:53 UTC,"Thanks for bringing that up, Cascardo. That was one scenario we didn't consider, and you're right about it causing problems for users with encrypted systems."
1800562,2019-02-19 12:24:11 UTC,"The attachment ""debdiff for disco"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1800562,2020-08-18 16:57:16 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1800562,2019-02-20 09:04:58 UTC,Have you seen this cause any issue when kdumping from bionic or any releases later than xenial?
1800562,2019-07-04 21:30:02 UTC,"This is the debdiff containing the proposed solution for this LP.
I'd like to thanks specially Cascardo and Heitor for the fruitful discussions with regards the direction we should take in this LP."
1800562,2019-04-20 20:08:55 UTC,Unsubscribing the Ubuntu Sponsors Team as there is nothing to sponsor.
1800562,2020-07-02 19:27:23 UTC,"Ubuntu 19.04 reached end of life on January 23, 2020.  I am therefore marking this bug 'wontfix' for that release."
1800565,2018-10-30 05:45:09 UTC,"As I understand it, the problem is that strings that are stored in savegames are saved localized.
Easier way to reproduce: Start a savegame, save it, change the language, load it, and the strings are messed up. Especially in scenarios (story messages and objectives are always in the language in which the game was first started)."
1800565,2018-10-30 06:47:31 UTC,"The problem here is that strings coming from the win conditions and from the scenarios get assembled via Lua freely. This means that not only the English string, but the complete algorithm on how it was assembled would need to be sent to C++ - I don't think that this is doable."
1800565,2018-10-30 07:50:37 UTC,"Instead of translating strings immediately on calling _(), they could be tagged as ""translatable"", stored in English with this tag all the time and only translated for displaying by the font renderer. This might be a very large change though, and I don´t know how the tagging should be handled. Perhaps as a new struct Translatable which encapsulates a const char* or std::string and replaces these as data type for strings that should be translated?"
1800565,2019-09-17 10:03:39 UTC,Migrated to https://github.com/widelands/widelands/issues/1721
1800565,2018-10-31 07:11:12 UTC,This will not work. We assemble complicated strings before sending them to C++.
1800566,2020-01-29 03:50:17 UTC,This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.2
1800566,2020-01-29 03:47:35 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.4
1800566,2020-01-29 03:38:31 UTC,This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu2
1800566,2020-01-29 03:37:14 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1800566,2020-01-15 16:57:55 UTC,"Sorry for the typo in last comment: ""package sin - proposed"" -> ""packages in -proposed"" !"
1800566,2020-01-15 16:55:02 UTC,"I've verified this LP in all 3 releases, by installing the package sin -proposed and checking the command-line of kdump kernel, which contains ""reset_devices"" for all the 3 versions tested:"
1800566,2020-01-14 14:18:21 UTC,"Hello Guilherme, or anyone else affected,"
1800566,2020-01-13 15:54:08 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.6-2ubuntu2) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1800566,2020-01-14 08:28:24 UTC,"Hello Guilherme, or anyone else affected,"
1800566,2019-02-19 09:32:26 UTC,Debdiffs for this bug were attached to LP#1800562
1800566,2019-07-04 21:05:36 UTC,"This is the debdiff with this LP's proposed modifications.
I'd like to specially thanks Cascardo and Heitor for the discussions and joint work in this issue."
1800566,2019-07-05 00:20:38 UTC,"The attachment ""lp1800566_eoan.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1800566,2020-01-14 09:55:45 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.4) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1800566,2020-01-07 20:45:37 UTC,This bug was fixed in the package makedumpfile - 1:1.6.6-4ubuntu1
1800566,2020-01-13 14:56:10 UTC,"Hello Guilherme, or anyone else affected,"
1800566,2019-12-20 18:02:37 UTC,"After some attempt to merge the work needed in LP #1816743 here, we decided to split the bugs and only work the 'reset_devices' addition here."
1800566,2020-01-09 19:10:12 UTC,"For this LP SRU submission, the following candidate packages were tested in amd64 arch:
* Xenial, candidate version 1.6.3-2~16.04.2;
* Bionic, candidate version 1.6.5-1ubuntu1~18.04.4;
* Disco, candidate version 1.6.5-1ubuntu1.4;
* Eoan, candidate version 1.6.6-2ubuntu2;"
1800572,2018-10-31 19:21:54 UTC,Minor gui issue; low priority / does not gate any release
1800573,2018-11-16 16:22:14 UTC,"I just installed MaaS 2.5 beta 4, I can deploy Ubuntu 18.04 Machines normally, but, when I click to deploy the machine ""As a KVM Host"", it fails and I can't easily find why."
1800573,2019-09-19 14:47:51 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1800573,2018-11-17 01:06:22 UTC,The cloud-init-output.log (failed deployment):
1800573,2018-11-17 01:05:44 UTC,The cloud-init.log with BOND (failed deployment):
1800573,2018-11-17 01:05:36 UTC,The cloud-init.log with BOND (failed deployment):
1800573,2018-11-17 01:05:23 UTC,The cloud-init.log with BOND (failed deployment):
1800573,2018-11-17 01:02:43 UTC,"It works with basic network topology (i.e., no BOND), however, when there is a BOND channel, the deployment fail again but, in a different stage."
1800573,2018-11-16 21:58:00 UTC,And the cloud-init-output.log.
1800573,2018-11-16 21:57:30 UTC,The cloud-init.log
1800573,2018-11-16 21:57:03 UTC,Netplan file
1800573,2018-11-16 21:22:52 UTC,I just found the problem!
1800573,2018-11-16 17:37:46 UTC,Debugging ifnormation should be available in:
1800573,2018-11-17 01:03:50 UTC,"New Netplan with BOND (works without KVM Host selected, as per first screenshot above):"
1800577,2020-09-08 14:15:28 UTC,"Its worrying that you cannot reproduce it but here is a screenshot showing the problem on a Macbook Pro Retina 15 inch screen using MacOS 10.15.6, and using Mixx 2.2.3 (build 2.2 r6750)."
1800577,2020-09-08 18:03:55 UTC,"I think as a band aid, we should add just an empty line at the end.
This will probably also fix the painting issue with the star rating and the last track in the list.
https://bugs.launchpad.net/mixxx/+bug/1278592"
1800577,2020-09-08 10:50:07 UTC,"strange, I'm sure I saw it but can't reproduce it anymore.."
1800577,2020-09-08 17:22:04 UTC,"Compared to my setup, with Ubuntu Bionic 18.04 and QT 5.9.5 the scrollbars are inside the content area and inside the borders changing colors when focused."
1800577,2018-10-31 03:38:13 UTC,">> Do you use any other Qt applications? Have you noticed the same issue with those?
Hm, I think RStudio uses Qt and while I didn't find the identical bug, I do observe a different scrolling bug in their file viewer.
"
1800577,2018-10-31 02:33:01 UTC,"Considering this happens with other scrollbars, I suspect this is a bug in Qt. Do you use any other Qt applications? Have you noticed the same issue with those? What version of Qt did you build with and how did you install it?"
1800577,2018-10-31 01:38:56 UTC,">> Which Mixxx version are you using?
Built from source on master
"
1800577,2018-10-30 12:31:25 UTC,Thanks for reporting this!
1800577,2018-10-30 02:50:49 UTC,"Actually, I see the same behavior for other scroll bars, not just the tracks display. I believe the reason is that I have scroll bars set to always show (a MacOS setting)."
1800577,2020-09-08 10:08:38 UTC,"Unfortunately I now also experience this
Ubuntu 20.04
Mixxx 2.3beta with Qt5.12.8"
1800578,2020-08-09 23:52:20 UTC,1.5.3.8
1800584,2018-10-30 04:16:43 UTC,I noticed it in Dell Inspiron 14-3467.
1800585,2018-10-30 11:57:25 UTC,"In 18.10 i don't have this problem. What if you will change the ""Type"" in the launcher properties to ""Application in terminal"" (if the app wont't start from the menu)
About the problem of not finding the new menu entry this will persists after a reboot\restart?"
1800585,2018-10-31 04:00:37 UTC,"Dear APolihron,"
1800585,2021-02-04 11:10:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800591,2019-09-16 08:29:01 UTC,Migrated to https://github.com/widelands/widelands/issues/3346
1800592,2019-07-30 14:13:38 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1800592,2018-11-19 10:43:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800596,2020-02-12 05:09:22 UTC,Is the same for me
1800596,2020-04-18 15:33:40 UTC,"yo I get this message in ubuntu when running ""make"" so I can't even get past the first step..."
1800596,2019-04-12 06:38:38 UTC,It shoult be:
1800599,2018-11-01 09:04:25 UTC,"This may be a new RFE for Neutron. But to be honest, I'm not familiar about your mentioned, we can discuss this in the weekly driver meeting."
1800599,2018-11-07 20:11:18 UTC,Per the conversation we had during the latest weekly meeting (http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-11-06-14.00.log.html#l-135) Neutron server can be executed with  apache WSGI integration. You mentioned during the meeting that you could verify such deployment. This is the documentation that we have: https://docs.openstack.org/neutron/latest/admin/config-wsgi.html. Are you going to try it?
1800599,2018-11-07 20:11:48 UTC,"Since  apache WSGI integration, let's treat this as a normal bug."
1800599,2018-11-07 20:12:40 UTC,You may also find this useful: https://review.openstack.org/#/c/580049/
1800599,2018-11-08 05:59:34 UTC,"Thanks much for the comments, will do the test with that configuration."
1800599,2018-12-06 04:49:39 UTC,"Miguel,
Thanks much for the instructions to enable new uwsgi based web server for neutron, Following the steps, it is verified that new uwsgi based web server can solve this issue."
1800605,2019-06-20 10:15:54 UTC,Sorry.. for the previous message.. please delete it. It was intended for lighttpd bug list :D
1800605,2019-06-20 10:14:46 UTC,1) I didn't write to ask for any help. I am perfectly capable of solving the problem in many ways.
1800605,2019-06-13 15:03:13 UTC,Still an issue in bionic after update today (2019-06-13).
1800605,2018-11-18 21:04:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800606,2018-10-30 11:11:16 UTC,2.1 beta? We are currently testing 2.2 beta. Does this still happen with 2.2 beta?
1800606,2018-10-30 12:44:52 UTC,"I assume that this bug was triggered by a teack. By luck, you have still the mixxx.log file from the crashing run.
It is stores as mixxx.log.x where x is the number of restarts since then.
https://www.mixxx.org/wiki/doku.php/finding_the_mixxx.log_file
This should contain the effected file as last entry."
1800606,2018-10-30 20:04:46 UTC,I cant repeat the problem and have not seen it before. I did not touch the pc in any way. The Mixxx program just shutdown and closed without any errors.
1800607,2018-10-31 14:50:06 UTC,"Hello Matthias, or anyone else affected,"
1800607,2018-10-31 16:55:17 UTC,"autopkg tests are fixed, for both python3-defaults and patsy triggers."
1800607,2018-11-07 22:05:37 UTC,"The verification of the Stable Release Update for patsy has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1800607,2018-11-07 22:05:55 UTC,This bug was fixed in the package patsy - 0.4.1+git34-ga5b54c2-1ubuntu0.1
1800608,2019-04-03 17:20:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800610,2019-01-25 08:01:21 UTC,This is blocked by bug 1801629
1800610,2019-03-18 10:53:40 UTC,Could this be related to bug #1806204?
1800610,2019-03-22 12:21:00 UTC,"Hello Julian, or anyone else affected,"
1800610,2019-04-05 14:28:38 UTC,I looked at today's xubuntu daily image:
1800610,2019-04-09 18:55:13 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1800610,2019-04-09 19:05:13 UTC,This bug was fixed in the package livecd-rootfs - 2.525.20
1800610,2019-05-04 21:02:22 UTC,"I initially marked this Won't Fix for xenial, as there will be no more desktop or server images produced for xenial, but if this also has benefit on cloud images, we might want to look into it for that."
1800617,2019-04-16 08:16:24 UTC,"Closing because not replicated in 1.0alpha (Linux Mint 19.1, Windows 10). The speed performance is slightly different but nowhere near as bad as in Inkscape 0.92.3 (ppa) or Inkscape 0.92.4 (flatpak) Linux Mint 19.1"
1800617,2020-05-10 13:11:35 UTC,Thank you very much to you and the entire Inkscape team!
1800621,2018-10-30 11:34:06 UTC,"running Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11), using the Internal Import of pdf.
It looks to me like the colors are correct. The problem is that the linewidths are too narrow. Attached is an edited version where I have edited Chart 4 to have linewidths of 0.5 px instead of the original 0.1 px."
1800621,2018-10-30 11:50:03 UTC,Thanks for looking into this. Why is the internal import of InkScape not reproducing with the same linewidths as in the case of POPPLER import?
1800621,2018-10-30 15:15:24 UTC,">> Why is the internal import of InkScape not reproducing with the same linewidths as in the case of POPPLER import?
"
1800621,2018-10-30 09:57:57 UTC,"Forgot to add.
InkScape version: 0.92.3
OS: Windows 10"
1800631,2018-10-30 11:46:54 UTC,"More info,
there isn't un upgrade but a reinstall of freeipa-server package on the same 4.3.1 version,
that was removed before from an"
1800631,2019-01-28 08:45:05 UTC,"I had a very similar problem (with bionic). I was able to upgrade to FreeIPA 4.3.1 by installing version 3.36.1 of the package libnss3, from the cosmic repositories. There is a bug in the version 3.35 distributed with bionic (see https://bugzilla.redhat.com/show_bug.cgi?id=1568271) which prevents upgrades (and not only... installing a replica IPA server was also failing for me)."
1800631,2019-01-28 08:51:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800644,2018-10-30 19:51:49 UTC,"I agree that (from upstream POV) keeping everything in sync is worth more than skipping Void Linux backup files, so if I see a merge request that comments out that section and adds a ""TODO: get parser and tools in sync, see lp#1800644 for details"", I'll probably accept it ;-)"
1800644,2018-10-30 12:39:25 UTC,parser/apparmor_parser.pod and the is_skippable_file function in utils/apparmor/aa.py also need to be updated for XBPS patterns to be fully implemented in a consistent manner.
1800644,2018-10-30 13:08:57 UTC,"> E.g. to make Debian/Ubuntu drop their own profiles loading code in favour of the upstream one (https://bugs.debian.org/870697) I need to start by cleaning up obsolete stuff, e.g. all the code in rc.apparmor.functions that now duplicates the parser's functionality, which includes skipping such special files. This would be easy if we had no code in rc.apparmor.functions that does almost, but not quite, the same thing as what the parser does.
"
1800655,2018-10-30 13:41:01 UTC,running haproxy in debug doesn't see the utility containers traffic reach the haproxy
1800655,2018-10-30 13:48:07 UTC,when running tcpdump on the container itself
1800655,2018-10-30 13:57:21 UTC,"flushing the iptables -F on the aio host fixes the problem.
so ansible is pushing some firewall rules in iptables that block the utility container for reaching the haproxy on the aio host"
1800655,2018-10-30 16:12:30 UTC,We actually don't install any firewall rules so it seems like these have been put in place by another utility.
1800655,2018-10-30 16:19:06 UTC,"We need to actually make sure that we document that firewalld should not be installed (or if it is, we need to make sure you have relaxed rules)"
1800662,2020-10-11 23:56:29 UTC,"Per upstream developers: ""Wontfix. no more support for that release"""
1800662,2019-03-07 18:44:32 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1800663,2019-03-24 23:04:00 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1800663,2019-03-22 03:46:03 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1800663,2019-03-13 00:42:21 UTC,"Reviewed:  https://review.openstack.org/619125
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fee13a41c77edebeaef0ed37b149d5b6ef86fe5b
Submitter: Zuul
Branch:    stable/queens"
1800663,2018-11-09 01:32:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616721"
1800663,2018-12-07 16:08:13 UTC,"Reviewed:  https://review.openstack.org/619122
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e54c5fbe2df7324a75612e01433356a6b7fc1d14
Submitter: Zuul
Branch:    stable/rocky"
1800663,2018-11-21 00:41:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/619125"
1800663,2018-11-20 23:44:24 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/619122"
1800663,2018-11-20 15:55:41 UTC,"Reviewed:  https://review.openstack.org/616721
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0e718ddb7a43230fa1ae9ee2d78c4375a964cd48
Submitter: Zuul
Branch:    master"
1800663,2018-12-19 10:01:22 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1800664,2018-11-15 11:03:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1800664,2018-11-16 08:33:09 UTC,Performance is much increased with cosmic-proposed kernel
1800664,2018-11-20 00:47:39 UTC,"Ike has since done some more extensive testing, and found that performance actually *drops* with longer iperf runs. With a 900s run, he's seeing it go down to ~200Mbps, while the kernel emits messages like these:"
1800664,2018-12-03 08:49:32 UTC,This bug was fixed in the package linux - 4.18.0-12.13
1800664,2019-02-04 14:46:37 UTC,This bug was fixed in the package linux - 4.19.0-12.13
1800664,2019-02-14 12:13:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1800666,2021-02-24 10:05:00 UTC,fixed with https://review.opendev.org/c/openstack/swift/+/776673
1800676,2018-11-05 13:35:40 UTC,"Hi Neil,"
1800676,2018-11-05 14:24:14 UTC,"For example proxy is LSB generated, not systemd native"
1800676,2018-11-05 18:35:09 UTC,"You are right, the packages do in fact lack systemd unit files. While the SysV scripts and generated files work as is, we should stil add systemd unit files and align with the rest of the openstack packages. Also we are overdue for dropping upstart scripts from the packages now that we are no longer backporting openstack releases to the cloud archive for trusty. Note that the upstart scripts shouldn't be causing any issues."
1800676,2020-06-26 16:37:06 UTC,This bug was fixed in the package swift - 2.25.0-0ubuntu3
1800681,2020-05-12 17:03:14 UTC,"The verification of the Stable Release Update for open-iscsi has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1800681,2020-05-12 17:03:03 UTC,This bug was fixed in the package open-iscsi - 2.0.874-5ubuntu2.9
1800681,2020-05-11 14:14:35 UTC,"I built a test bionic image with open-iscsi from proposed, uploaded to OCI, booted on a PV instance, then performed a reboot. That reboot worked as expected without any scsi-related delays."
1800681,2019-10-28 19:57:01 UTC,"All autopkgtests for the newly accepted open-iscsi (2.0.874-5ubuntu2.8) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1800681,2019-11-29 12:12:34 UTC,"Hello Dimitri, or anyone else affected,"
1800681,2020-04-27 16:47:25 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1800681,2018-12-10 09:11:37 UTC,This bug was fixed in the package open-iscsi - 2.0.874-5ubuntu13
1800681,2019-10-28 17:04:45 UTC,"Hello Dimitri, or anyone else affected,"
1800681,2019-04-22 17:50:52 UTC,"I tested this fix on disco, and it appears to be working as intended."
1800683,2018-11-01 11:44:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800684,2018-10-30 17:44:50 UTC,"Will this happen on driverfixes/newton currently, as well?"
1800684,2018-10-31 10:41:04 UTC,"Hi Eric,
No it does not.  The locking that occurs within _last_volume_delete_initiator_group in masking.py in stable/ocata line 2772 does not exist in driverfixes/newton."
1800684,2018-10-31 12:18:12 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/614485"
1800684,2018-11-22 16:07:32 UTC,"Reviewed:  https://review.openstack.org/614485
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b7490b7644e4ce93ce416a9080ea16760f0a66aa
Submitter: Zuul
Branch:    stable/ocata"
1800685,2018-10-30 16:55:19 UTC,"[root@overcloud63m-compdpdk-41 ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
47fbf34ad5f4 100.64.87.201:8787/contrail-vrouter-agent-dpdk:5.0.1-0.214-rhel-queens ""/entrypoint.sh /u..."" 32 minutes ago Up 26 minutes contrail-vrouter-agent-dpdk
d7c4ce970d51 100.64.87.201:8787/contrail-vrouter-agent:5.0.1-0.214-rhel-queens ""/entrypoint.sh /u..."" 4 weeks ago Up 25 minutes contrail_vrouter_agent
5a8e63dc4468 100.64.87.201:8787/contrail-nodemgr:5.0.1-0.214-rhel-queens ""/entrypoint.sh /b..."" 4 weeks ago Up 4 weeks contrail_vrouter_agent_nodemgr
bad7243091bb 100.64.87.201:8787/rhosp13/openstack-cron:13.0-59 ""kolla_start"" 4 weeks ago Up 4 weeks logrotate_crond
e5d7f07b9525 100.64.87.201:8787/rhosp13/openstack-nova-compute:13.0-60 ""kolla_start"" 4 weeks ago Up 4 weeks (healthy) nova_migration_target
749c9eb1f028 100.64.87.201:8787/rhosp13/openstack-nova-compute:13.0-60 ""kolla_start"" 4 weeks ago Up 4 weeks (healthy) nova_compute
5b1086983084 100.64.87.201:8787/rhosp13/openstack-nova-libvirt:13.0-62 ""kolla_start"" 4 weeks ago Up 4 weeks nova_libvirt
21e5fb27701d 100.64.87.201:8787/rhosp13/openstack-nova-libvirt:13.0-62 ""kolla_start"" 4 weeks ago Up 4 weeks nova_virtlogd
988268f33f10 100.64.87.201:8787/rhosp13/openstack-iscsid:13.0-53 ""kolla_start"" 5 weeks ago Up 5 weeks (healthy) iscsid
[root@overcloud63m-compdpdk-41 ~]#
[root@overcloud63m-compdpdk-41 ~]#
[root@overcloud63m-compdpdk-41 ~]#
[root@overcloud63m-compdpdk-41 ~]# contrail-status
Pod Service Original Name State Status
vrouter agent contrail-vrouter-agent running Up 25 minutes
vrouter agent-dpdk contrail-vrouter-agent-dpdk running Up 26 minutes
vrouter nodemgr contrail-nodemgr running Up 4 weeks"
1800685,2018-10-30 16:55:08 UTC,We are using the following build on the vrouter.
1800687,2018-10-30 17:41:37 UTC,The unit can even go into this state while actually failing on TLS certificate verification:
1800687,2019-05-27 20:07:12 UTC,"Proposed patch fixes
2) landscape-client charm does not do proper error reporting."
1800687,2020-06-19 15:47:34 UTC,may help someone resolve landscape-clinet stuck in maintenance mode
1800690,2018-12-12 10:32:54 UTC,"Thank you for your bug report, that's indeed an annoying user experience. A similar problem is discussed upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/247"
1800692,2018-11-02 16:04:51 UTC,The package has been published and the bug is being set to Fix Released
1800692,2018-11-01 18:50:25 UTC,Tests complete with no regression. Customer issue fix verified
1800692,2018-10-30 20:33:08 UTC,Awaiting test kernel
1800692,2018-11-01 19:34:35 UTC,This bug was fixed in the package linux-azure - 4.15.0-1030.31
1800692,2018-10-31 12:04:58 UTC,This kernel has 2 small but important fixes and is being fast-tracked to -updates. I am marking testing as Invalid.
1800693,2018-11-01 18:51:53 UTC,Tests complete with no regression.
1800693,2018-11-01 19:33:34 UTC,This bug was fixed in the package linux-azure - 4.15.0-1030.31~14.04.1
1800693,2018-11-01 20:05:35 UTC,The package has been published and the bug is being set to Fix Released
1800693,2018-10-31 12:02:21 UTC,This kernel has 2 minor but important fixes and is being fast tracked. I'm marking testing as invalid.
1800693,2018-10-30 20:32:22 UTC,Awaiting test kernel
1800694,2018-10-30 20:31:41 UTC,Awaiting test kernel
1800694,2018-10-31 12:03:44 UTC,This kernel has 2 small but important fixes and is being fast-tracked to updates. I'm marking the testing as invalid.
1800694,2018-11-01 18:48:14 UTC,Tests show no regressions and the changes correct the customer problem.
1800694,2018-11-01 19:36:41 UTC,This bug was fixed in the package linux-azure - 4.15.0-1030.31~16.04.1
1800694,2018-11-02 16:41:23 UTC,The package has been published and the bug is being set to Fix Released
1800698,2018-10-30 21:10:43 UTC,"Changed in two spots, and deleted the related note.
@noah: Please check the difference file for the branch push, and confirm you agree."
1800713,2018-11-02 03:18:05 UTC,Getting the metrics should be fast. I have a strong suspicion that this is related to gathering the mongo metrics.
1800713,2018-11-04 02:17:44 UTC,"We should consider what Stats we can get quickly and possibly skip some of
them if it takes too long. Certainly it is better to get timely incomplete
stats than no stats. Especially when trying to figure out why things are
slow/overloaded."
1800713,2019-01-11 02:37:16 UTC,"For Juju 2.4.7 and later, the slow part (which happens on big controllers) can be skipped by setting the following:"
1800713,2019-10-31 03:37:57 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1800719,2020-01-24 15:05:19 UTC,Upgraded from 16.04.5 to 18.04.3 and have noticed the same symptom
1800719,2020-02-06 03:48:34 UTC,I believe I also have this issue.
1800719,2019-05-05 19:35:37 UTC,"The files /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf and /etc/ld.so.conf.d/i386-linux-gnu_GL.conf are symlinks to /etc/alternatives/x86_64-linux-gnu_egl_conf /etc/alternatives/x86_64-linux-gnu_gl_conf, which are in turn the symlinks to /usr/lib/virtualbox/additions/00vboxvideo.conf (from VirtualBox package)."
1800719,2019-02-12 16:05:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800719,2019-10-11 07:24:17 UTC,"Same symptoms like Jerzy Luszawski @dr-agon wrote, except my links pointing on:"
1800719,2018-11-06 02:54:56 UTC,The easy fix was to move the two links out of the /etc/ld.so.conf.d directory.
1800720,2019-01-01 20:12:31 UTC,"I confirmed this on windows 10 with the development branch as well.  If I remember correctly, this is as wxWidgets issue due to the menu accelerator handling on windows.  Although it may have been corrected in the 3.1 branch."
1800720,2019-01-01 17:47:30 UTC,"This persists in KiCad 5.0.2 release on Windows 10. For now, exporting, editing, and importing the hotkeys file is a workaround."
1800720,2018-11-25 22:52:48 UTC,"Application: kicad
Version: (5.0.0), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011
Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON"
1800720,2018-11-25 22:54:34 UTC,"A search of the bug tracker for ""hotkey windows"" did not yield a similar report."
1800720,2018-11-25 22:01:21 UTC,Please include your KiCad version information.  I believe this issue is only on certain platforms and has already been reported.
1800720,2019-01-01 16:57:01 UTC,Anyone on MSW able to recreate this behavior?
1800723,2020-08-30 09:43:15 UTC,"$ python3.7 -m pip --version
pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.7)"
1800723,2019-05-14 17:55:03 UTC,"I would really like to see pip3 not pulling in dependencies for python3.6. It interferes with other dependencies. In my case, few packages, for instance cffi is causing issues with import when compiling with python 3.7"
1800723,2019-05-14 17:45:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800723,2018-11-02 18:04:22 UTC,"Ok, I see."
1800723,2019-05-14 17:44:42 UTC,"I arrived here researching this exact issue, in my case I'd really need not to install python 3.6 since it interferes with other dependencies and makes a docker image larger."
1800723,2018-10-31 19:35:36 UTC,"That (python3-pip) does install pip3, but it also installs all of python3.6. Also, the pip3 it installs is by default set up for python3.6 (/usr/bin/python3), sadly."
1800723,2018-10-31 18:46:59 UTC,"The python3 package is python 3.6. It does contain pip3 (for python 3.6 of course, so not useful in my case). The python3.7 package has no pip or pip3.
What I attempted to do:
  apt install python3.7
  pip3 --version
What is missing? pip/pip3
What did I expect? The python3.7 package, or perhaps a package ""python3.7-pip"" (which doesn't exist), should install a version of pip or pip3 which works with python 3.7."
1800723,2018-10-31 18:29:25 UTC,Thanks for reporting.
1800723,2018-10-31 00:21:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1800723,2018-10-31 19:41:05 UTC,"Also once python3-pip is installed, ""python3.7 -mpip --version"" works. So it's really not terrible, it's just that all of python3.6 is needlessly installed."
1800723,2018-10-31 19:02:18 UTC,"I'm sorry, I messed up above. The pip3 binary is part of the python3-pip package. In other words pip is package separately from python. (Or pip3/python3 as in this case)"
1800732,2018-10-31 18:34:08 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1800735,2020-04-26 17:50:28 UTC,Submitted as a pull request on Github:
1800736,2019-05-31 05:26:25 UTC,"Yes, I met this problem too.
As for me, the ""ceph health detail"" told me that there are about 640 pgs unknown.
I finally found that it was that kolla-ansible did not configure ceph correctly. It is to say that kolla-ansible cannot recognize the device label ""KOLLA_CEPH_OSD_CACHE_BOOTSTRAP"", and took it as the normal osd drives.
I solved this problem temporarily by manually correcting the crushmap:
1. Delete the cache osd from the default nodes, such as controller01, controller02, etc, and correct the weights in root default.
2. Add the cache configurations of nodes before root cache, such like the configurations above. Remember to use another id.
3. Add the cache items to the root cache with the right weight.
4. Refresh the crushmap.
However, it can only take effect until next restart of the related osds.
Hoping there could be a more effective approach."
1800740,2019-12-15 18:11:06 UTC,"This had affected me... I discovered this when starting menulibre, as a parse error."
1800740,2019-10-09 15:32:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800745,2019-09-10 20:23:05 UTC,Confirmed this on the 3.3.3 sandbox.
1800745,2018-10-31 20:59:28 UTC,"BTW: this is a huge annoyance for us and makes the ""Mark for Selector"" and ""Mark for Order"" processes extremely time consuming for us, because the selector and order person often find themselves wanting to change funds on items that their colleagues have sent over."
1800747,2019-01-30 02:00:27 UTC,nobody who can help? here my settings:
1800747,2018-12-06 14:41:20 UTC,"jl@2n1:~$ echo $XDG_CURRENT_DESKTOP
KDE
jl@2n1:~$ ls /usr/share/xsessions/
plasma.desktop"
1800747,2018-12-06 14:34:48 UTC,Onboard crashes the entire Desktop on the most recent release of Kubuntu.
1800749,2020-08-07 09:53:23 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020."
1800749,2020-01-25 14:46:27 UTC,"A ""renegade mouse pointer"" still flickers about once a second in the center of the screen in Sauerbraten full screen mode in Ubuntu 19.10 with updates thru 01-25-2020.  Game play is better, though."
1800749,2019-07-22 23:44:58 UTC,"The bug started Ubuntu 18.10 and continues in 19.04 with all updates applied as of the date of this comment.  Again, it seems like the Ubuntu Desktop, as of 18.10, is continuously(once a second) hijacking the mouse and keyboard from Sauerbraten when running in full-screen mode.  Thanks."
1800749,2019-07-22 04:06:05 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1800749,2020-01-24 09:06:12 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1800749,2018-11-29 01:18:15 UTC,"The issue described in Post #4 seems to also occur in DOSbox (package 0.74-2-1) - when running fullscreen and pressing two or more keys simultaneously, one of them stops being registered a while later."
1800749,2018-11-18 10:33:38 UTC,"Correction: not _epoll_, but _poll_.  Again, it was a hack at trouble-shooting and may be unrelated."
1800749,2018-11-18 09:30:23 UTC,"It appears that the xinput devices(keyboard/mouse) are being hijacked by desktop?  As long as there is user input(keyboard/mouse activity) at least once second within Sauerbraten, everything works as expected in Ubuntu 18.10.  Further bug info: I noticed that if you're moving forward with the 'w' key(with no mouse activity), and jump(press 'spacebar') while keeping the 'w' key pressed, the bug returns about a second later.  The forward movement stops and the rogue mouse pointer returns to flickering, as if there is no user activity, or as if the user input activity has been cleared/reset.  ***If you _don't_ jump while moving forward, the forward movement continues as expected and the rogue mouse pointer stays away.  When there is no user input/activity for about 1 second, the flickering mouse pointer returns.  Again, everything works as expected in Ubuntu 18.04.  Thanks!"
1800749,2018-11-10 08:04:19 UTC,A little more info:
1800749,2018-11-05 10:02:26 UTC,"I'm not sure if it's related, but graphic games under dosbox, such as Scorched Earth, fail to capture the mouse in Ubuntu 18.10.  They work fine(mouse is captured/functional) in Ubuntu 18.04*."
1800749,2018-11-29 01:19:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800752,2018-11-07 23:59:08 UTC,I've been looking (briefly) for some docs on the Intel GPU hardware layout.
1800752,2018-11-07 01:37:33 UTC,apport information
1800752,2018-11-07 01:37:34 UTC,apport information
1800752,2018-11-07 01:40:23 UTC,"OK. So I have to run as root *while logged in to desktop of the system*.  Just being logged in as root (on a system where I ""never"" user the console...) over the network isn't good enough."
1800752,2018-11-07 01:42:12 UTC,Only affect Cosmic. Bionic is OK.
1800752,2018-11-11 12:14:12 UTC,('invalid' = 'not beignet's bug' - I do agree it is *a* bug)
1800752,2020-10-26 00:59:49 UTC,This has been fixed....
1800752,2018-11-11 23:26:11 UTC,"Additional information (note in particular that Intel consider the graphics development branch at https://cgit.freedesktop.org/drm-tip, not the integration branch at kernel.org, to be the appropriate ""latest upstream"" to test against):"
1800752,2018-11-12 00:48:33 UTC,"Thanks.
I'll add relevant links (both ways) if I can as I report it on that site.
If the code hasn't changed in the graphics development branch I may submit a report now anyway..."
1800752,2018-11-12 02:05:13 UTC,"I've opened:
   https://bugs.freedesktop.org/show_bug.cgi?id=108712"
1800752,2018-11-13 04:48:21 UTC,Yes. The patch will land Cosmic and Disco.
1800752,2018-11-13 19:30:45 UTC,Good.
1800752,2018-11-07 01:37:31 UTC,apport information
1800752,2018-11-11 19:01:07 UTC,Or I could post a comment to the commit mentioned in #14 - see what the author (from Intel) thinks?
1800752,2018-11-07 01:27:40 UTC,">> I've installed it - it might now be collecting data...
"
1800752,2018-11-12 17:51:34 UTC,"They've found the bug!!
   https://bugs.freedesktop.org/attachment.cgi?id=142443"
1800752,2018-11-07 01:01:49 UTC,">> Further information may be available in the files (readable only by root,
>> the 0 may be different if you have more than one graphics device):
"
1800752,2018-11-04 22:53:58 UTC,">> Was this report sent from the affected system?
"
1800752,2018-11-04 23:03:33 UTC,If it's any help here is the info from the last BOINC startup log under Bionic and the first under Cosmic.
1800752,2018-11-07 01:03:39 UTC,Here's the Bionic kernel info (couldn't seem to be able to attach two files to one comment?).
1800752,2018-11-05 23:01:47 UTC,"Well spotted - BOINC ""GFLOPS peak"" is the theoretical 8 * compute units * max clock (not an actual speed measurement), and matches the 24 compute units clinfo reports, not the 48 compute units this GPU is supposed to have."
1800752,2018-11-04 22:39:48 UTC,"Was this report sent from the affected system?  as it says the CPU is an i5-2500K, which is too old for beignet.  (It shouldn't crash, but won't be running the computations, so the slowdown is probably from some other package.)"
1800752,2018-11-06 00:17:33 UTC,Looks like there's a bug in dpkg-buildpackage!?!
1800752,2018-11-06 01:21:32 UTC,The dh_auto_configure reports this:
1800752,2018-11-06 01:23:31 UTC,Built and installed beignet-opencl-icd_1.3.2-4_amd64.deb with the patch.
1800752,2018-11-04 23:05:54 UTC,"Just noticed that the logs in #4 show a difference in the reported GFLOPS peak.
Bioinc says 384, while Cosmic says 192."
1800752,2018-11-06 11:19:54 UTC,">> BOINC running - haven't had sufficient time to check relative processing speed yet.
"
1800752,2018-11-06 15:19:24 UTC,FYI: Boiled it down to a simple ioctl() call.
1800752,2018-11-06 15:23:37 UTC,"And, just for confirmation, with the older Bionic 4.15.0-38-generic kernel I get:"
1800752,2018-11-06 18:32:55 UTC,"Just guessing, but a possible candidate...
https://github.com/torvalds/linux/commit/8cc7669355136f8952779e6f60053c1284d59c4d"
1800752,2018-11-06 22:07:00 UTC,"Further information may be available in the files (readable only by root, the 0 may be different if you have more than one graphics device):"
1800752,2018-11-06 22:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1800752,2018-11-07 00:26:59 UTC,apport-collect 1800752
1800752,2018-11-06 07:46:35 UTC,"> I suppose the question now is why did teh code get 48 in Bionic, but only get 24 in Cosmic?
Agreed; I'll look into this later.
"
1800753,2020-11-06 18:44:25 UTC,Included in the 19.04 release of the charms
1800753,2019-03-25 00:24:35 UTC,"I see that this fix / change is now in master, any change that this can be backported? To a current field version?"
1800753,2018-11-08 07:42:03 UTC,submitted a draft patch just now - https://review.openstack.org/#/c/616436
1800753,2019-03-27 02:18:46 UTC,submitted a backported patch for stable/18.11 for review per wouter's comment - https://review.openstack.org/#/c/647977/
1800755,2018-11-01 14:40:39 UTC,"Sounds like bug 1632247 but that was ""fixed"" a couple of years ago with this change:"
1800755,2018-11-01 14:44:56 UTC,"I'm not sure why we don't provide some way to purge old faults. The API only shows the latest fault for a given instance. And we don't have any API or nova-manage CLI to list *all* faults for a given instance, so I guess they are just there in the database until the instance is deleted and archived/purged. Seems we could add a nova-manage CLI to allow purging old fault information as long as the latest fault is left intact."
1800755,2018-11-01 14:49:26 UTC,This is also likely poor for performance:
1800755,2018-11-01 15:30:05 UTC,Pretty sure that StarlingX purges instance_faults when purging instances.  It's in INSTANCES_CHILD_TABLES here:
1800756,2018-11-01 16:39:12 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1800761,2019-03-04 19:28:47 UTC,"Hello, I'd like to contribute to OpenLP so I figured I might take a look at this issue."
1800763,2020-03-31 16:23:52 UTC,"I know 18.10 is already unsupported, but I guess it applies to later versions as well."
1800763,2019-01-08 10:00:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800763,2018-11-15 16:31:34 UTC,"I've attached the boot log, so that it is easier to determine what the problem is."
1800763,2019-01-08 10:17:01 UTC,"I don't have the same final message (as I now booted the last one I got was ""Started Detect the available GPUs and deal with any system changes.""), but the result is the same. The system tries to start the graphical environment and usually fails (maybe one boot in 30 succeeds on the first try)."
1800779,2018-11-19 15:34:08 UTC,I can reliably reproduce the issue with the attached document in libreoffice 6.0.6 on Ubuntu 18.04 and with the libreoffice snap (version 6.1.3.2).
1800788,2018-11-05 09:48:52 UTC,Hardware Certification have begun testing this -proposed kernel.
1800788,2018-11-09 12:51:07 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/oem/4.15.0-1026.31/oem-4.15-proposed-published.html"
1800788,2018-11-14 04:30:50 UTC,"4.15.0-1026.31 - oem
Regression test CMPL, RTB."
1800788,2018-11-14 15:15:29 UTC,This bug was fixed in the package linux-oem - 4.15.0-1026.31
1800788,2018-11-14 15:34:09 UTC,The package has been published and the bug is being set to Fix Released
1800788,2018-11-15 11:16:17 UTC,This bug was fixed in the package linux-oem - 4.15.0-1026.31
1800794,2019-09-05 22:26:22 UTC,"@RussianNeuroMancer: Thanks for the additional info. From what you now say, and unlike how I understood comment #14, the newline fix *does* make a difference, i.e. it addresses the problem description in the bug summary: ""usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE"". Is that correct?"
1800794,2019-09-06 05:14:22 UTC,"> i.e. it addresses the problem description in the bug summary: ""usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE"". Is that correct?
"
1800794,2019-09-09 15:43:50 UTC,Just in case I want to clarify that I did mistake in #19 and #22 - I totally forgot that besides configuration file I also added couple of lines with modem id's to /lib/udev/rules.d/40-usb_modeswitch.rules:
1800794,2019-09-09 15:56:19 UTC,Log of usb-modeswitch 2.5.2+repack0-2ubuntu2~mtrudel1 and without /usr/share/usb_modeswitch/03f0:0857
1800794,2019-09-09 15:57:14 UTC,Log of usb-modeswitch 2.5.2+repack0-2ubuntu2~mtrudel1 and with /usr/share/usb_modeswitch/03f0:0857 (Configuration=3)
1800794,2019-09-09 15:59:24 UTC,Log of usb-modeswitch 2.5.2+repack0-2ubuntu1 from Ubuntu eoan repository and with /usr/share/usb_modeswitch/03f0:0857 (Configuration=3)
1800794,2019-09-09 16:04:05 UTC,"Shortly, 2.5.2+repack0-2ubuntu2~mtrudel1 version does not work with or without /usr/share/usb_modeswitch/03f0:0857"
1800794,2020-06-30 17:16:40 UTC,This bug was fixed in the package usb-modeswitch - 2.6.0-2ubuntu1
1800794,2019-09-10 06:13:43 UTC,"I referring to the variant with the TCL dispatcher in the first PPA. You described this version in #4 as ""dispatcher-c-rewrite.patch disabled"" so this is why I call it like this."
1800794,2019-09-16 12:08:23 UTC,"So with my PPA version, what do you have in /run/usb_modeswitch/current_cfg then?"
1800794,2019-09-23 06:36:42 UTC,"Currently I doesn't have access to hardware. I will try to check /run/usb_modeswitch/current_cfg content with latest build from PPA this Friday, or next week."
1800794,2020-11-03 22:32:26 UTC,"Issue is no longer reproducible on Linux 5.8, although on 5.9 there is regression: https://bugzilla.kernel.org/show_bug.cgi?id=209469"
1800794,2020-11-03 22:32:42 UTC,*on Ubuntu 20.10 with Linux 5.8
1800794,2020-11-03 23:16:54 UTC,"@RussianNeuroMancer: This bug is closed, so please file a new bug if you have found a new issue. OTOH, an issue with Linux 5.9 isn't reasonably an Ubuntu bug yet. If you think there is a need to modify usb-modeswitch to work with Linux 5.9, then I think it's best to start a new topic in the upstream forum."
1800794,2019-09-05 18:05:32 UTC,"So last time (#16) usb-modeswitch service failed for me because there was no configuration for this modem in usb-modeswitch-data - result log is in #20
It's possible to workaround this be creating configuration manually (#21) but version without dispatcher-c-rewrite.patch is more convenient - it configured modem even without configuration file (#19)."
1800794,2019-09-09 19:56:11 UTC,Thanks! I'll leave it to Mathieu to ask possible follow-up questions.
1800794,2019-09-05 18:02:28 UTC,Log of usb-modeswitch with fixed dispatcher-c-rewrite.patch and with /usr/share/usb_modeswitch/03f0:0857 (Configuration=0)
1800794,2019-09-09 13:56:41 UTC,"@RussianNeuroMancer: With your log files as guidance, Mathieu has made several modifications of dispatcher-c-rewrite.patch, which I put in the second PPA:"
1800794,2019-09-05 18:00:56 UTC,Log of usb-modeswitch with disabled dispatcher-c-rewrite.patch and without /usr/share/usb_modeswitch/03f0:0857
1800794,2019-08-26 14:36:47 UTC,"From my understating this issue boils down to not dropping new line symbol from kernel version string when function in C program check presence of cdc_mbim kernel module. It can’t find cdc_mbim kernel module because it looking in folder that doesn’t exist, so automatic changing LTE modem mode to MBIM doesn’t happen and it stays in Ethernet mode, which doesn’t work."
1800794,2019-08-26 14:42:21 UTC,"> Please include all the debugging information you can here
"
1800794,2019-08-26 21:42:29 UTC,"I built usb-modeswitch with tcl8.6-dev and dispatcher-c-rewrite.patch disabled, and mobile broadband still works with my old USB thing."
1800794,2019-08-27 02:04:34 UTC,"On 2019-08-26 23:42, Gunnar Hjalmarsson wrote:

> I built usb-modeswitch with tcl8.6-dev and
> dispatcher-c-rewrite.patch disabled, and mobile broadband still works
> with my old USB thing.
>
> No extra runtime depends.
"
1800794,2019-08-27 02:46:06 UTC,"As RussianNeuroMancer correctly pointed out the bug is in the concatenation of the strings
MODULES_PATH, kversion, and CDC_MBIM_DRIVER_PATH into cdc_mbim_module_path."
1800794,2019-08-27 10:30:17 UTC,"> Does this possibly address the issue you are having?
"
1800794,2019-08-27 11:03:01 UTC,@RussianNeuroMancer: Thanks for confirming.
1800794,2019-08-27 16:33:33 UTC,"Am 27. August 2019 04:04:34 GMT+02:00 schrieb Gunnar Hjalmarsson <email address hidden>:

>
> The upstream source has a jim/ folder with a lot of stuff, but that
> folder is excluded in the Debian/Ubuntu source.
"
1800794,2019-08-27 17:17:09 UTC,@Josua: Thanks for that explanation.
1800794,2019-09-05 18:01:33 UTC,Log of usb-modeswitch with fixed dispatcher-c-rewrite.patch and without /usr/share/usb_modeswitch/03f0:0857
1800794,2019-08-28 14:29:11 UTC,"There is no enthusiasm among the Ubuntu developers to go back to a TCL dispatcher, so I have made an alternative fix via the attached debdiff where I simply modified the C patch by removing the problematic newline. Built with the modified patch in this PPA:"
1800794,2019-08-28 14:35:37 UTC,@Josua: Thanks for your answer! (I didn't see it before posting the debdiff.)
1800794,2019-08-30 13:01:31 UTC,"> Any chance you can test this variant too, before I ask a sponsor to upload the patch?
"
1800794,2019-08-30 16:56:09 UTC,@RussianNeuroMancer: Thanks for testing! Is that the same error you get when you run the usb-modeswitch version in the Ubuntu archive?
1800794,2019-08-26 14:27:18 UTC,"Please describe the problem here, rather than in forum posts. It's not helpful to have to go through various pages and posts from different people, with information that is potentially irrelevant to the bug. To compound to the situation, pastebins have disappeared by now."
1800794,2019-09-01 11:34:33 UTC,"> Is that the same error you get when you run the usb-modeswitch version in the Ubuntu archive?
"
1800794,2019-09-03 11:39:55 UTC,"So to summarize you found the newline issue, but that proved to not be related to the error message you get, even if fixing it may be necessary as a partial solution. If I modify the test script by commenting the newline fix I get:"
1800794,2019-09-05 13:32:03 UTC,"Rather than pasting just a single error line, please include the full debug log for running usb-modeswitch. You can do that by modifying /etc/usb_modeswitch.conf:"
1800794,2019-08-28 12:39:53 UTC,"Am 27. August 2019 19:17:09 GMT+02:00 schrieb Gunnar Hjalmarsson <email address hidden>:

>@Josua: Thanks for that explanation.
>
>Since you are here, may I take the opportunity to ask a question. I
>think that Mathieu would prefer that TCL somehow is compiled into a
>binary, and that's what README indicates will happen with the
>installed-
>shared option. But Debian builds with installed-shared, and they still
>depend on libjim.
"
1800799,2018-10-31 09:38:14 UTC,How this is related to Neutron?
1800808,2018-10-31 12:24:46 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1800808,2018-10-31 14:02:18 UTC,Well thanks my bot but idk what the fuck is piping about lol
1800812,2019-09-16 13:52:06 UTC,Migrated to https://github.com/widelands/widelands/issues/2123
1800812,2019-05-31 17:31:21 UTC,I´ll implement that you can select additional wares and workers to take on the ship in the expedition tab.
1800812,2018-10-31 10:45:24 UTC,Not sure what you mean with hardcoded here. The cost for an expedition is the cost for a new port plus a builder and a ship. The port cost is in data/tribes/buildings/warehouses/<tribename>/port/init.lua
1800812,2019-06-02 05:00:29 UTC,I think that starting an expedition is already expensive enough and the additional wares should not be added by default.
1800813,2018-11-14 20:54:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800819,2019-05-13 10:34:28 UTC,"Reviewed:  https://review.opendev.org/614487
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=eb592162817184b1d8b3c9b3e576ebc0715ec350
Submitter: Zuul
Branch:    master"
1800819,2019-09-13 16:05:52 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1800820,2019-09-13 16:05:54 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1800820,2019-05-13 06:24:16 UTC,"Reviewed:  https://review.opendev.org/614488
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=7e0f4eeed351c66b0355605f917553adcd9f7cea
Submitter: Zuul
Branch:    master"
1800836,2020-12-15 13:37:35 UTC,"possibly needs upstream commit
https://github.com/systemd/systemd/commit/f02ba163891bab73a80332b4599a9d73083cb6c2"
1800836,2020-09-16 11:00:49 UTC,This is still happening with 237-3ubuntu10.42 in Bionic.  RA routes announced with lifetime of 0s are not removed.  It is the firewall which used to be the default router which (continously) announce these 0s lifetimes to make sure there are no issues with failover.
1800836,2020-02-02 04:17:32 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1800836,2019-12-03 21:26:19 UTC,"> After a failover
"
1800836,2019-11-05 17:18:09 UTC,fw01/02 have bond0.21 that is setup to have fe80::1 as the VIP used as the network gateway:
1800836,2019-09-27 18:19:46 UTC,"> For me it looks like the issue is fixed in this pull request:
> https://github.com/systemd/systemd/pull/3242
"
1800836,2019-05-27 07:22:43 UTC,We are also affected by this issue. networkd does not expire routes which causes issues with active-passive router configurations.
1800836,2019-03-13 12:39:19 UTC,I can confirm the same issues with `systemd-networkd` in Xenial (and Debian Stretch). Do you know if there is a patch from a modern `systemd` that can be used to backport a fix to older versions?
1800836,2019-03-13 11:59:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800836,2018-11-16 20:39:48 UTC,systemd from Cosmic is not affected by this bug:
1800836,2019-09-27 18:21:51 UTC,"@sdeziel can you provide more specific simplified steps to reproduce this?  Like, specific networkd (or netplan) config file(s), and steps to reproduce?"
1800838,2019-01-23 11:32:28 UTC,"Regarding the nvidia fan (right side of the case), it doesn't spin fast for me either. I tried to get the fan controls in nvidia-settings (390.77-0ubuntu0.18.04.1) by rebooting with ""Coolbits"" ""4"" (see: https://z-issue.com/wp/nvidia-linux-drivers-powermizer-coolbits-performance-levels-and-gpu-fan-settings/ or just google ""coolbits"") but the controls didn't appear on the app."
1800838,2019-01-23 11:24:28 UTC,"Thanks for the ""127 gives full speed"" trick. Until now I was using"
1800838,2019-01-23 10:32:44 UTC,Current update.
1800838,2019-01-22 15:00:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800838,2018-11-02 07:44:42 UTC,"First is sensors output. Here is only 1 pwm.
thinkpad-isa-0000
Adapter: ISA adapter
fan1:        2067 RPM"
1800838,2018-11-02 04:36:10 UTC,how do you know the 2nd fan is not working? let me check it in your way on my p52 too.
1800838,2018-11-01 08:00:38 UTC,"This is manual fan regulation what is not very handy to control fan speed manually all the time.
I found other issue, second fan is not wokring. It is repeating on 3 laptops, so can not be hardware malfunction."
1800838,2018-10-31 14:31:32 UTC,repeat on 4.19 kernel version
1800838,2018-10-31 13:50:54 UTC,1. This was from beginning
1800838,2018-10-31 13:45:10 UTC,apport information
1800838,2018-10-31 13:45:09 UTC,apport information
1800838,2018-10-31 13:31:59 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1800838,2018-11-01 03:40:16 UTC,create /etc/modprobe.d/thinkpad_acpi.conf with: options thinkpad_acpi fan_control=1
1800838,2018-10-31 13:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1800839,2019-04-09 16:45:22 UTC,"Got this back from the Sony dev Roderick Colenbrander,"
1800839,2019-04-09 13:30:40 UTC,"kaihengfeng, emailed Roderick Colenbrander the commit at Sony and we will see."
1800839,2019-04-09 11:33:46 UTC,"Thanks for pointing out the regression commit. The patch author is from Sony, so it's better to ask the patch author directly the justification behind blacklisting."
1800839,2019-04-10 05:29:42 UTC,Does it work out of the box under Wayland session?
1800839,2019-04-09 09:48:39 UTC,"Kai-Heng Feng, I replied to you several months ago via email but for completeness I want to leave a reply here too.
Yes, when the new sony_hid first came out there were two devices an analog sticks/triggers and buttons device and a second accelerometer/gyro device.  Splitting into two joysticks simply required remapping in the applications I was using.  Later (around last april-june)the gyro/accelerometer device is detected but is not registered as a joystick device.
this answer which I asked when I first reported this bug is at Ask Ubuntu, maybe it might help, I didn't get it to work and after loosing use of a second computer I prefer to leave hand repairs out of my everyday machine.
https://askubuntu.com/questions/1088925/ubuntu-18-04-no-longer-adds-second-joystick-device-for-sony-dualshock3s-gyro-ac"
1800839,2019-02-22 14:08:17 UTC,Does it use to work on previous Ubuntu releases?
1800839,2019-02-03 18:46:12 UTC,'kernel-bug-exists-upstream'
1800839,2018-10-31 13:55:25 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1800839,2019-04-09 09:55:10 UTC,"This looks like the change which blacklists the motion device.
https://github.com/torvalds/linux/commit/20ac95d52a28f55472a54cc751eeec49fd445cb1#diff-34c8d0c14a101d038ef2d2e7a1957559"
1800843,2018-10-31 14:00:41 UTC,Sorry that this is logged against 'Apport'. I am using a different laptop to report the problem as the affected laptop 'iOTA' cannot send emails! Have 500 ( tried restoring from Backup's but problem persists.
1800843,2019-10-04 13:14:26 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1800843,2019-12-04 04:17:31 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1800847,2018-11-02 18:15:06 UTC,"Erica, your examples both seem to involve going backwards across the Daylight Savings boundary, which strikes me as a possible cause for the initial bug of setting the date to the following day. I don't know a lot of the details, but it sounds like the difference between setting the due date to ""23:59:59"" (the end of a day) vs. mistakenly bumping it forward an hour, which becomes ""00:59:59"" on the next day."
1800847,2018-11-09 16:10:14 UTC,This may be the same Daylight Savings Time bug that was just committed at the Hack-a-way:
1800847,2020-02-13 17:54:38 UTC,"Just noticed it this morning with a book, dd not have the same issue with a DVD yesterday."
1800848,2019-06-05 13:56:10 UTC,"Hmmm, I am confused, I posted the log entry ""not a new instance""… so some part of cloud-init was running. So maybe the issue has been that I forgot to enable all of cloud-init services that would to the new instance check or either cloud-init 18.2-3.13 had a bug. I am quite sure I was not aware that there are four different services for cloud-init (cloud-init, cloud-final, cloud-config, cloud-init-local). I find it sometimes challenging to crasp the complexity behind cloud-init."
1800848,2019-06-05 19:06:18 UTC,"OK, good to know."
1800848,2019-06-05 14:47:51 UTC,Proxmox VE gets this right:
1800848,2019-06-05 14:25:32 UTC,"Hi Martin,"
1800848,2019-06-05 13:48:54 UTC,It might be difficult to get back the RPM package of the cloud-init version I used as I reported the bug. And the recent ones work.
1800848,2019-05-28 09:04:52 UTC,"Nope, this did not help. It appears that cloud-init is not even ran on startup. But this would be a different bug than this one."
1800848,2019-05-28 09:58:30 UTC,This appears to be fixed with both cloud-init from Public Cloud module in SLES 15 SP 1
1800848,2019-05-28 09:38:12 UTC,I resolved  Bug 1136532 - cloud-init-generator does not run cloud-init on SLES 15 SP 1 (mistake in my understanding it appears) and applying IP addresses works correctly with
1800848,2019-05-28 08:47:16 UTC,This does not yet appear to be fixed with:
1800848,2018-10-31 14:18:04 UTC,I bet this is related to this change:
1800848,2019-05-29 15:39:17 UTC,"Hi,"
1800848,2018-10-31 14:12:53 UTC,Reported upstream as: https://bugs.launchpad.net/cloud-init/+bug/1800848
1800854,2018-10-31 14:34:59 UTC,I will carry the following in the SUSE package for now:
1800854,2019-07-18 23:04:53 UTC,"Hi,"
1800854,2020-02-20 21:15:03 UTC,"This bug is believed to be fixed in cloud-init in version 20.1. If this is still a problem for you, please make a comment and set the state back to New"
1800857,2018-11-08 17:46:44 UTC,https://blueprints.launchpad.net/cinder/+spec/scaleio-glance-image-cache-support  - there is a blueprint for the same feature
1800861,2018-10-31 15:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1800870,2018-10-31 17:09:41 UTC,"I was just looking at https://git.launchpad.net/~neels/kicad/log/?h=neels/ratsnest_ and I'm torn on the ratsnest settings.  Technically, nets are already defined in the board file so I don't think adding additional tokens such as ""show"" and ""color(r,g,b,a)"" to the net definitions is a bad idea.  So in the board file a net would look like (where items in [] are optional and are the default setting if not specified):"
1800870,2018-10-31 16:46:41 UTC,Isn't the user preference file just the same as the project file?  Or am I missing an important piece here?
1800870,2018-10-31 16:21:08 UTC,I'm not opposed to the idea of custom views but I am opposed to saving them in the board file.  We've discussed the annoyances of having the board file modified for layer visibility setting changes.  This will only pile on top of that.  I would rather split out the view related information to a separate file so it doesn't dirty the board file.  This also keeps VCS users happy.
1800870,2018-10-31 16:42:50 UTC,"On 31/10/2018 17:21, Wayne Stambaugh wrote:

> I'm not opposed to the idea of custom views but I am opposed to saving
> them in the board file.  We've discussed the annoyances of having the
> board file modified for layer visibility setting changes.  This will
> only pile on top of that.  I would rather split out the view related
> information to a separate file so it doesn't dirty the board file.  This
> also keeps VCS users happy.
>
"
1800870,2018-10-31 16:34:13 UTC,"Yes, that makes sense to me, too. If we have a such a sidecar format, that's perfect. I just didn't think having board-wise ""views"" in the user config made sense."
1800870,2018-10-31 16:44:15 UTC,"This ""user preference"" file could also be used to store some other preferences like rats-nest colors by net/by netclass ..."
1800871,2021-01-07 21:55:41 UTC,Some testing notes:
1800871,2021-01-05 21:29:26 UTC,"I took the opportunity to rebase, sign off on Josh's commit, and add a follow-up commit to change the upgrade script to an UPDATE rather than INSERT statement: user/sandbergja/lp1800871_MADS_2.15_update"
1800871,2021-01-06 14:39:52 UTC,"Jane, thanks for reviving this, sorry I didn't see your earlier message about the update using an insert.  I think I must have been copying the update script that added the feature and didn't think about the fact that it was already there for upgrades.  I agree that it should be an update.
Josh"
1800871,2019-08-02 14:32:17 UTC,"Thanks, Josh and Linda, for figuring out such a gnarly issue, and for getting it fixed upstream!"
1800871,2019-08-02 15:35:07 UTC,It looks likely to me but it will surely be up to Josh to confirm it...
1800871,2019-02-28 14:57:46 UTC,"Hello, I've taken a stab at updating the evergreen files related to this."
1800871,2019-02-28 15:23:24 UTC,"Thank you, Josh!"
1800871,2018-11-14 08:43:35 UTC,The official file from the LC has already been updated accordingly:
1800872,2018-10-31 16:19:03 UTC,"I ran into the same issue with a different model, exact same symptoms and missing fields in mongodb."
1800872,2019-02-26 14:15:09 UTC,https://github.com/juju/juju/pull/9793 is a fix for 2.5
1800872,2019-02-26 12:44:22 UTC,I agree and believe that we should do both the upgrade step and the change to the query.
1800872,2019-03-01 11:53:23 UTC,https://github.com/juju/juju/pull/9819 merges this into develop
1800872,2019-02-26 11:11:09 UTC,"More data to debug : https://pastebin.canonical.com/p/vr6XVyvYtb/ (good and bad models creation date), https://pastebin.canonical.com/p/XzPRgBCJhT/ (db.upgradeInfo dump) - sorry, Canonical-only links"
1800872,2019-01-31 15:10:37 UTC,"@jam : we just ran into this bug again. Should we proactively add ""volumes"" and ""filesystems"" fields for all modelEntityRefs documents that don't have them ?"
1800872,2018-11-04 07:40:17 UTC,"My supposition was wrong. Even in Mongo 2.4 $size: 0 only matches if you have an array:

> db.t.insert({""a"": []})
> db.t.find()


{ ""_id"" : ObjectId(""5bdea1bb8952436077782726""), ""a"" : [ ] }

> db.t.find({""a"": {$size: 0}})


{ ""_id"" : ObjectId(""5bdea1bb8952436077782726""), ""a"" : [ ] }

> db.t.find({""b"": {$size: 0}})
> exit
"
1800872,2019-02-26 12:11:21 UTC,"Looking at the code, the description of the modelEntityRefs document is:
type modelEntityRefsDoc struct {
 UUID string `bson:""_id""`"
1800872,2019-02-26 17:07:43 UTC,"The patch against 2.5 has landed, but it only fixes the Query, it doesn't introduce an upgrade step.
It is also unclear whether this will end up in 2.5.2 or 2.5.3 as we won't block 2.5.2 for it, but it may be that we won't finish getting a clean report for 2.5.2 until after this patch is released."
1800873,2020-08-18 17:00:19 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1800879,2018-10-31 21:04:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/614637"
1800879,2018-10-31 23:43:19 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/614637
Reason: It will be fixed on Oslo.service side with https://review.openstack.org/#/c/614642/"
1800879,2018-11-02 09:13:50 UTC,Fixed on oslo.service side: https://review.openstack.org/#/c/614642/
1800879,2018-11-02 09:14:41 UTC,"Just for confirmation, periodic job is now passing: http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master/openstack-tox-py35-with-oslo-master/f7c6623/testr_results.html.gz"
1800879,2020-03-19 21:59:15 UTC,We don't have py35 job anymore so I will close this as Won't fix.
1800879,2020-03-19 21:59:42 UTC,"Argh, it's already fixed, sorry for my last comment :)"
1800881,2018-11-01 06:22:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800912,2019-06-18 04:17:33 UTC,[Expired for file-roller (Ubuntu) because there has been no activity for 60 days.]
1800912,2019-04-18 15:53:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1800912,2018-10-31 21:52:13 UTC,This computer was given to me through a program...do not have software to reload. would you please help I will be eternally grateful. :)
1800912,2019-04-18 15:53:29 UTC,In any case that doesn't seem likely to be an issue with the archive manager
1800915,2018-10-31 22:24:04 UTC,IMO this should be only well documented. Changing it in API may cause failures on clients so it should be discoverable as any other API change. I'm not sure if that is worth to do :)
1800915,2018-11-01 02:42:08 UTC,"I would agree with Slawek, making this change would break backwards-compatibility of the API, documenting it would be better."
1800918,2019-03-25 13:58:05 UTC,Seemed to encounter this in a docker 18.04 container without sudo package installed.
1800925,2021-01-15 15:55:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800925,2021-01-15 15:56:49 UTC,In 21.04 the printmenu from evince stops the whole programm and can only be killed.
1800935,2018-12-02 23:02:46 UTC,"Can see i posted this over a month ago, no comments from the development team?"
1800937,2018-11-01 08:49:26 UTC,Update from Biswajit
1800940,2019-10-31 02:50:23 UTC,2.6.7 release never went out. This fix was instead released in 2.6.8 - re-targeting this report.
1800940,2019-09-17 04:41:27 UTC,"Although this is likely a rare use-case, in a multiuser setup this will cause problems. So, having a user-unique location for temporary data is a must."
1800940,2019-09-16 12:57:10 UTC,"The directory ""/tmp/juju-juju-vsphere-bionic"" is used to guard against multiple bootstraps done simultaneously on a client from trying to access the image cache at the same time. ie I could have 2 client terminals open and run bootstrap in each."
1800940,2019-09-16 12:09:51 UTC,Hi Erik and Daniel - I've created a different bug to track work on this multiple-clashing-nics issue: https://bugs.launchpad.net/juju/+bug/1844125
1800940,2019-09-13 09:25:54 UTC,Another observation here is that the directory: /tmp/juju-juju-vsphere-bionic created on the client-side of juju as part of a bootstrap command will be left in place.
1800940,2019-09-13 08:12:55 UTC,UPDATE (on the issue of bootstrap creates 2 nics):
1800940,2019-09-12 18:01:15 UTC,I get the same behavour as Daniel Bidwell above.
1800940,2019-09-11 05:39:41 UTC,"Hi Daniel - I don't see multiple nics on the controller machine (or other machines) when I bootstrap. Is it possible you're using a different stream that has a customised OVA with multiple nics?
The vsphere provider isn't space-aware, so it seems that in that situation we'll only generate a mac for the first nic and then the second nic might be left with whatever was the default."
1800940,2019-09-10 19:04:50 UTC,"I am now testing bootstraping a controller on vmware with a
vsanDatastore and am getting unusual behavior that is causing trouble."
1800940,2019-09-03 20:26:34 UTC,"Fantastic, I knew it would be an easy configuration setting somewhere. We did look!"
1800940,2019-09-03 16:46:04 UTC,"Doing a little more verifying of my solution shows that the ""maybe-
ubiquity"" is not needed at all.  I just removed the ""console=tty1
console=ttyS0"" and it works fine."
1800940,2019-09-03 15:47:43 UTC,"I have found a solution.  The juju vsphere images load with
/etc/default/grub containing the following line which is causing the
problem."
1800940,2019-08-14 21:40:50 UTC,Good news. We've been able to land a change that enabled Juju to support vSAN volumes. I've added testing instructions for the curious in our forum: https://discourse.jujucharms.com/t/1929
1800940,2019-07-30 09:16:25 UTC,"I finally got our vSphere back up and running, and gave this a try, however I ran into some issues with it."
1800940,2019-07-24 07:30:30 UTC,"We tried updating the hardware version in the past, but the Ubuntu images
then failed to boot (kernel failure midway through the boot process). We
might have better success with the new code path, so it is probably worth
testing again."
1800940,2019-01-08 18:50:08 UTC,Is there any indication that this will actually make it into the 2.5.1 release?
1800940,2019-07-22 15:09:53 UTC,Fantastic! I'll give it a try tomorrow!
1800940,2019-07-23 13:21:53 UTC,"Unfortunately our VMware trial license has expired, so I have to get our IT department to help me, before I can test out the changes. :-("
1800940,2018-12-09 12:07:15 UTC,"same issue here, you are not alone"
1800940,2018-12-11 15:13:13 UTC,Blocking some customer deployments (https://bugs.launchpad.net/juju/+bug/1807953).
1800940,2018-12-20 14:14:55 UTC,"I'd love to assist with resolving this bug. I'm relatively new to juju, but this is blocking some of the work we're doing in the Dell EMC Customer Solution Centers. I have access to environments to assist in troubleshooting, but I'll need help. Please let me know what I can do."
1800940,2019-03-12 18:19:00 UTC,juju bootstrap downloads a *.vmdk file.  The cdrom points to an ovfenv-juju-*.iso but fails to boot from it and drops down to the vmware pxe boot which of course times out and failes.
1800940,2019-03-12 18:39:37 UTC,"upgrading the vmware hardware version to 11,13, or 14 does not make any difference in it's behaviour."
1800940,2018-11-08 19:34:57 UTC,Is there any more information I can provide to assist in this bug resolution?
1800940,2019-07-10 20:43:43 UTC,Adding kubernetes-master-charm as it is marked as affecting a duplicate bug report.
1800940,2019-07-10 21:12:43 UTC,"Agreed, don't see the kubernetes-master charm being relevant for this bug."
1800940,2019-07-11 08:43:05 UTC,Thanks for pointing me to the duplicate issue.
1800940,2019-07-16 03:57:03 UTC,Thanks for the offer of assistance Frederik. I missed the email notification when it came through and apologise for not updating this ticket sooner.
1800940,2019-07-16 07:46:41 UTC,"Brilliant, let me know if there's anything I can assist you with, testing maybe?"
1800940,2019-07-22 01:06:42 UTC,Good news. I was able to make some progress late last week and was able to bootstrap Juju onto a vSphere/ESXi instance backed by vSAN.
1800940,2019-07-22 01:31:49 UTC,"This is wonderful news.  Is there any chance that they can update the
vsphere images from hardware version 10 to 14?"
1800940,2019-07-10 20:57:02 UTC,"I'm marking this as invalid for kubernetes-master, since the issue occurs during Juju bootstrap or machine deployment, before kubernetes-master ever runs."
1800950,2018-10-31 23:01:17 UTC,"Oops almost forgot sorry, running *cups-filters* 1.20.2-0ubuntu3 on Ubuntu Mate 18.04 LTS (4.14.77-v7+)"
1800952,2019-11-23 06:10:10 UTC,"This was broken for me in the latest bionic 18.04-3, with or without backports."
1800952,2018-11-17 00:28:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800952,2018-11-09 15:30:43 UTC,FWIW
1800952,2018-11-01 22:07:59 UTC,I installed KHelp Center to see if that is similarly affected. It's NOT.
1800952,2018-12-13 02:18:46 UTC,"Yes, it would be really good if this could be fixed!"
1800953,2018-11-16 05:26:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800957,2019-01-28 18:22:38 UTC,I'm now able to reproduce the problem using the procedure described in comment #35.  I did have to bump up the thread count and lower the wait time - I'm running the rpc-client like this:
1800957,2019-01-28 08:08:59 UTC,+1
1800957,2019-01-25 23:03:27 UTC,Nice work Gabriele!
1800957,2019-01-25 12:30:28 UTC,"After a thorough analysis, we ended up  on the py-amqp socket read function [1]
and more in detail on the SSL Class implementation [2]
Using a ""big"" buffer the read function did not work correctly, by debbuging this code [3]:
```
frame_type, channel, size = unpack('>BHI', frame_header)
```
we saw data as:"
1800957,2019-01-19 23:05:42 UTC,"Can you try using a higher number of threads in the simulator client?
i.e. -p 10"
1800957,2019-01-16 21:30:34 UTC,"I haven't been able to replicate the error following the steps above either.
Only difference is that I used our existing rabbit server as opposed to the docker one."
1800957,2019-01-14 16:57:19 UTC,"Unfortunately I wasn't able to reproduce the problem either. With SSL, I get the following summary:"
1800957,2019-01-13 13:06:03 UTC,"@kgiusti I repeat the test in a fedora 28 x86_64 VM and a hit the same issue, after some time one of the queues starts to have unack messages."
1800957,2019-01-11 18:18:17 UTC,Thanks for doing this @itsuugo I appreciate it.
1800957,2019-01-11 13:13:02 UTC,@kgiusti I think that I'm able to reproduce the issue only with the tools/simulator.py script that's in the oslo.messaging repository.
1800957,2019-01-09 17:08:43 UTC,"We have the same issues with nova-compute, some messages get stuck in the queue when using SSL.
We've identified that this problem happen periodically, always in the same queue and with large messages (> 100k characters)"
1800957,2019-01-14 17:19:35 UTC,Here's a description of my environment and the results of a few test runs:
1800957,2019-01-30 23:44:25 UTC,"Great, this is excellent news. After doing some successful testing we have deployed this to prod and seems to be working well. We can move on with our lives once again :-)"
1800957,2019-02-26 00:03:43 UTC,This issue was fixed in the openstack/oslo.messaging 9.5.0 release.
1800957,2019-02-18 16:21:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637576"
1800957,2019-02-18 16:32:00 UTC,"Saw that amqp 2.4.1 has been released and as it contains the fix i took the liberty to send a patch proposal. Would you mind taking a look, Ken?"
1800957,2019-02-20 22:39:31 UTC,"Reviewed:  https://review.openstack.org/637576
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=64f74cd2cc17a9331f943f25c76dde6b4c604247
Submitter: Zuul
Branch:    master"
1800957,2019-02-21 14:55:39 UTC,Unfortunately we can't backport this fix to previous stable branches since it is a change to requirements which is technically a feature release.
1800957,2019-02-21 16:51:05 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/638461"
1800957,2019-02-22 17:47:20 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/638733"
1800957,2019-02-22 17:55:56 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/638735"
1800957,2019-02-25 03:42:53 UTC,"Reviewed:  https://review.openstack.org/638735
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=3113175443b975d72699b3bbe6fea488c414a3ef
Submitter: Zuul
Branch:    stable/pike"
1800957,2019-02-25 17:40:58 UTC,"Reviewed:  https://review.openstack.org/638461
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=693cd964e02002ab28366df08c5b75f396198492
Submitter: Zuul
Branch:    stable/rocky"
1800957,2019-03-04 19:35:29 UTC,"Reviewed:  https://review.openstack.org/638733
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=389dacdc6bda1cad890c786e2bc6f9594e86a191
Submitter: Zuul
Branch:    stable/queens"
1800957,2019-10-30 11:32:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800957,2018-12-07 00:46:43 UTC,Looks like this could also be an issue with the queens versions too. We upgraded ceilometer from ocata to queens and seeing similar issues with messages not being ack'd. We have downgraded back to ocata for now.
1800957,2019-01-31 15:00:32 UTC,"That fix for py-amqp (see comment #43) has landed on master today.
We'll need to bump the minimum version of amqp in oslo.messaging's requirements once the fix is released."
1800957,2018-11-28 22:49:08 UTC,OK I've done some more thorough testing with our nova install in production
1800957,2019-01-20 22:59:44 UTC,"OK yes tried with -p 10 and that did the trick, lots of timeouts now"
1800957,2018-11-26 14:29:21 UTC,Let us know if moving to the newer versions solve your SSL problems.   If that is the case I'll open a bug on Ubuntu cloud archive referencing this issue.
1800957,2018-11-01 00:35:54 UTC,OK I tried running the newer version of python-amqp with the older version of oslo.messaging and it works fine so I don't suspect python-amqp to be an issue.
1800957,2018-11-01 00:42:29 UTC,OK I have narrowed this down to olso.messaging itself.
1800957,2018-11-01 03:08:49 UTC,Can confirm 5.17.4 works and 5.18.0 doesn't work
1800957,2018-11-01 03:14:06 UTC,Running commentary....
1800957,2018-11-01 03:22:17 UTC,and then there was one. It's https://github.com/openstack/oslo.messaging/commit/7e71ac821f4103032afc8eff8007ad48afe49a2c
1800957,2018-11-05 16:36:58 UTC,"Hi Sam,"
1800957,2018-11-05 22:56:15 UTC,"The connections to the rabbit server are fine, I see them. The issue is the messages in the reply queue aren't acked."
1800957,2018-11-06 17:02:52 UTC,Gotcha.
1800957,2018-11-07 00:16:47 UTC,OK have given this a go
1800957,2018-11-07 21:29:53 UTC,"Ugh, so it looks like the test client worked."
1800957,2018-11-07 22:23:14 UTC,OK I have added this onto the client side (neutron-dhcp-agent)
1800957,2018-11-07 22:31:51 UTC,"Sorry my above paste was missing some stuff at the start, here is a complete one http://paste.openstack.org/show/734376/"
1800957,2018-11-07 22:43:16 UTC,Here's another go with same error http://paste.openstack.org/show/734378/
1800957,2018-11-07 23:05:13 UTC,Here is a message timeout with logs from server too
1800957,2018-11-26 21:32:21 UTC,We upgraded nova to pike last week and we have experienced similar issues but they seem slightly different and the downgrading of amqp and kombu hasn't helped in this case. We had to roll back to nova ocata and have spent the last few day trying to figure out what the problem is. Still unknown at this stage.
1800957,2018-11-08 21:55:17 UTC,Yes without ssl it works fine.
1800957,2018-11-12 05:40:34 UTC,On a possibly related note we see these errors when we upgraded nova to pike (and hence the olso-messaging upgrading too)
1800957,2018-11-12 05:59:50 UTC,And in RabbitMQ logs we start to see the following errors after upgrading too:
1800957,2018-11-12 23:48:03 UTC,"OK I have started again and done some more thorough testing, here's what I've found."
1800957,2018-10-31 23:53:20 UTC,I should also note that downgrading back to the ocata versions of everything fixes this.
1800957,2018-11-13 03:03:36 UTC,For reference we have packaged up oslo.messaging stable/pike branch with one patch to revert the use kombu 4 library.
1800957,2018-11-15 00:01:21 UTC,So with nova we have upgraded our conductors to pike and they now are getting these errors
1800957,2018-11-15 00:03:35 UTC,Should mention that changing conductor to not use ssl to connect to rabbit stopped getting these amqp reconnect errors
1800957,2018-11-15 07:55:05 UTC,"Hi Sam, I have got timeout errors at nova-compute side on my cloud. I used your oslo.messaging patch and changed amqp version to amqp==1.4.9 and kombu version to kombu==3.0.37 versions, it worked well. Now I don't get any timeout errors at nova-compute side. But I am using different library versions at nova-conductor side and it is working well. at nova-conductor side, I am using amqp (2.2.1) , kombu (4.1.0) and oslo.messaging (5.30.2)"
1800957,2018-11-15 22:10:29 UTC,@skylightcoder are you using SSL and also what version of RabbitMQ are you using?
1800957,2018-11-16 05:02:15 UTC,Yes I am using SSL and Rabbitmq version is 3.6.9. This my rabbitmqctl status output : http://paste.openstack.org/show/734900/
1800957,2018-11-21 16:57:06 UTC,"Hi Sam and Gokhan,"
1800957,2018-11-21 21:10:10 UTC,Hmm ok I'll look at using the newer versions. These are the versions that ship with the Ubuntu Pike Cloud Archive so anyone using this version of openstack would be affected.
1800957,2018-11-08 19:19:58 UTC,Thanks for gathering those logs.
1800959,2019-02-12 15:49:59 UTC,"Most likely, I did not try using a dash in the role name since I initially stumbled across this."
1800959,2019-02-12 13:57:26 UTC,Is this still an issue?
1800959,2021-02-17 17:09:51 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1800963,2018-11-01 15:37:41 UTC,apport information
1800963,2020-04-29 09:07:58 UTC,Looks like a fix is coming in bug 1866088 so let's use that.
1800963,2020-04-29 08:30:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800963,2018-11-01 23:11:05 UTC,This behavior is also encountered when using the nouveau display driver on a fresh install that hasn't had nvidia drivers installed.
1800963,2018-11-01 15:37:51 UTC,apport information
1800963,2018-11-01 15:37:50 UTC,apport information
1800963,2018-11-01 15:37:48 UTC,apport information
1800963,2018-11-01 15:37:46 UTC,apport information
1800963,2018-11-01 15:37:43 UTC,apport information
1800963,2018-11-01 15:37:39 UTC,apport information
1800963,2018-11-01 15:37:49 UTC,apport information
1800963,2018-11-01 15:37:37 UTC,apport information
1800963,2018-11-01 15:37:36 UTC,apport information
1800963,2018-11-01 15:37:35 UTC,apport information
1800963,2018-11-01 15:37:34 UTC,apport information
1800963,2018-11-01 15:37:32 UTC,apport information
1800963,2018-11-01 15:37:31 UTC,apport information
1800963,2018-11-01 15:37:29 UTC,apport information
1800963,2018-11-01 15:12:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1800963,2018-11-01 02:24:53 UTC,apport information
1800963,2018-11-01 02:24:52 UTC,apport information
1800963,2018-11-01 15:37:38 UTC,apport information
1800963,2018-11-01 01:40:41 UTC,This bug is missing log files that will aid in diagnosing the problem. Please enter the following command in a terminal window:
1800965,2020-04-13 16:31:50 UTC,"Closing the ""fontconfig (Ubuntu)"" task, since I have the experience that upstream is disinclined to change /etc/fonts/conf.avail/65-nonlatin.conf at the request of a distro, and carrying patches for the purpose is inconvenient."
1800965,2020-04-09 00:53:28 UTC,"I made an attempt to address this bug via another package. The language-selector-common package installs /etc/fonts/conf.avail/64-language-selector-prefer.conf, and I added ""Lohit Devanagari"" (installed by default) to that file."
1800965,2019-10-07 06:36:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800965,2020-04-13 13:14:12 UTC,This bug was fixed in the package language-selector - 0.204
1800965,2019-10-07 06:36:13 UTC,"+1 on this. Some ligatures are not rendered: eg, त्र is showing up as त् र (two letters) with the default Ubuntu, because of this ""Raghindi"" font setting.  Changing it to (in my case) Noto fixes the rendering. I made the change in my home directory (.config/fontconfig/conf.d/). Please change this system setting."
1800968,2019-07-19 13:26:06 UTC,"Please provide a log of network-manager in debug mode, following the instructions on"
1800968,2019-07-21 18:44:39 UTC,"I don't have that computer handy, but I have another one I use currently which is affected by the same issue. This computer is running Ubuntu MATE 19.04, network-manager-gnome version 1.8.20-1ubuntu1."
1800968,2019-09-20 04:18:10 UTC,[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]
1800973,2018-12-18 20:06:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1800973,2018-12-18 20:08:42 UTC,Without TLS enabled it works perfectly.
1800973,2019-03-13 10:02:01 UTC,"This issue can (at least partially) be resolved by upgrading golang-google-grpc to version 1.7.0. It includes a fix for https://github.com/etcd-io/etcd/issues/8627, which the author of this issue reported as the problem in https://github.com/etcd-io/etcd/issues/9956."
1800976,2018-11-01 03:49:57 UTC,"The commit ""c714676a1  proc: restrict kernel stack dumps to root"" (part of the update to linux-stable 4.4.160) has changed the permissions of /proc/self/stack to be root- and CAP_SYS_ADMIN-only which is causing test_095_kernel_symbols_missing_proc_self_stack to fail"
1800976,2018-11-01 04:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1800976,2018-11-07 08:24:14 UTC,"It looks like there is a nbd related failure in the test report.
I will split the kernel_security one first to nail them down one by one:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802069"
1800985,2018-12-18 22:44:05 UTC,"Reviewed:  https://review.openstack.org/617345
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=37091909c83d5504d159039b27937f44327fbe71
Submitter: Zuul
Branch:    master"
1800985,2018-11-13 13:09:57 UTC,I think the best option here would be to request requests to tag and move to that.  rolling back has caused problems in the past that I'd like to avoid.
1800985,2018-11-08 02:59:53 UTC,"Workaround the issue by
1. downgrading `requests` to the version before 2.20.0. Or
2. patch the fix from requests master branch before 2.20.1 is released."
1800985,2018-11-07 15:15:02 UTC,"running into the same issue with nagios-unity script.
https://github.com/thecodeteam/nagios-unity"
1800985,2018-11-12 11:26:34 UTC,"Hi,
submitted a patch to pump requests to 2.20.1
https://review.openstack.org/617296"
1800985,2018-11-01 10:02:25 UTC,can we pin 'requests!=2.20.0' in requirements/upper-constraints.txt
1800996,2019-01-22 13:20:02 UTC,"Another backup tool I am using is borg (https://www.borgbackup.org/); similar to restic, but with less options as destination."
1800996,2019-01-22 03:33:53 UTC,Heyo! Maintainer of Deja Dup here. We’ve never actually had another tool backend before. So this would be breaking new ground.
1800996,2019-01-14 07:37:50 UTC,"fwiw I hacked on this a little bit, and have a patch that copies deja's duplicity backend to a new ""restic"" and gets things building:"
1800996,2019-01-21 11:18:06 UTC,Checking the documentation it has a json output option
1800996,2019-01-07 14:48:02 UTC,Also interested in this.
1800998,2018-11-08 05:31:51 UTC,"Some corrections and additions to the message above (everything was checked on CentOS7 compute host, latest Rocky with all available updates installed):"
1800998,2018-11-02 13:50:34 UTC,Maybe this is the related bug in storyboard:
1800998,2018-11-06 12:01:28 UTC,Hello Matt.
1800998,2018-11-01 14:33:25 UTC,"Anyway, this isn't a nova bug, so I've invalidated it for nova, but if you're using openstackclient 3.16.1 then this should be fixed so I'll leave it open for OSC - although note they track bugs in storyboard now:"
1800998,2018-11-01 14:32:05 UTC,This is a CLI issue. You're using python-novaclient 11.0.0 and the corresponding remove_fixed_ip code in novaclient was removed in 10.0.0:
1800998,2018-11-01 08:12:10 UTC," affects nova
 importance high"
1800998,2018-11-02 06:37:19 UTC,"Matt, thank you for your response. But as I may see through patch you've mentioned, it is about floating IP addresses, not fixed ones."
1801000,2018-11-01 07:39:56 UTC,"I send a script and two files.
png file is a copy of pdf one which I prepared by the same inkscape in batch mode."
1801000,2018-11-02 16:58:00 UTC,"Hello,"
1801000,2018-11-02 19:08:54 UTC,thank you for the support files:
1801000,2018-11-03 10:05:48 UTC,"Tank you for quick answer,"
1801000,2018-11-03 10:32:02 UTC,I'm not sure I fully understand the issue but it seems to break down into the fact you're trying to embed a PDF file into an SVG file?
1801000,2018-11-03 12:54:44 UTC,"Thanks again for the quick answer,"
1801000,2018-11-03 13:22:01 UTC,"I think there's a fundamental misunderstanding on how Inkscape works on your side:
- If you drag&drop a .pdf file into an opened Inkscape instance,
  then the PDF is *imported*, that means converted from PDF to SVG
  on-the-fly and the resulting SVG code is added to the opened document
- There is *no* embedded PDF file in the file ""North.svg""
- If you manually create a line like
    <image xlink:href=""file.pdf""/>
  in an SVG file it is *invalid* and Inkscape won't be able to open it"
1801000,2020-03-18 19:08:57 UTC,"Closing because ""works as expected"". Request is beyond the scope of the project."
1801000,2018-11-01 10:26:13 UTC,"- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- using the command line:
inkscape \windows\temp\drawing.svg --export-pdf=\windows\temp\testex1.pdf >pdf.log 2>&1"
1801014,2019-06-18 07:52:16 UTC,"user space perf tools commit ids:
0ccdb8407a4660f6dbc5977bc060917d2c3e7986
acae8b36cded0ee62038dedd0a44d54d5d673a96
b74d8686a18b36adecc710597198d5ef2dd5ef14
db5742b6849ed7f01d764e6755b8ab2b422f29b2
e05a899718f094e2c87d99115c5b1191405a9fd0"
1801014,2019-05-06 06:30:34 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801014,2019-06-18 07:54:32 UTC,related kernel bug is LP#1791232
1801027,2018-11-09 00:49:15 UTC,"Removing packages from disco-proposed:
 eficas 6.4.0-1-2 in disco
  eficas 6.4.0-1-2 in disco amd64
  eficas 6.4.0-1-2 in disco arm64
  eficas 6.4.0-1-2 in disco armhf
  eficas 6.4.0-1-2 in disco i386
  eficas 6.4.0-1-2 in disco ppc64el
  eficas 6.4.0-1-2 in disco s390x
Comment: Depends on FTBFS openturns; LP: #1801027, Debian bug #902513
1 package successfully removed."
1801031,2019-02-06 19:44:27 UTC,"A rebuild of this package was triggered for the switch from python3.6 to python3.7, but it appears that this rebuild was not needed.  So this is not a blocker for the disco release; however, it's important that supported packages be buildable from source."
1801033,2018-11-01 10:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801033,2018-11-02 07:00:33 UTC,"Tested with 4.18.16 and 4.19.0-041900-generic mainline kernel, issue still exist"
1801033,2018-11-02 08:08:28 UTC,"Tried to run this test with upstream toolset, https://github.com/torvalds/linux.git with commit 8adcc59 on 4.18.0-11-generic s390x kernel."
1801037,2018-11-01 10:30:05 UTC,This change was made by a bot.
1801037,2018-11-02 12:58:51 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].
1801037,2018-11-14 07:14:51 UTC,"Hello
I had a few problem with this upstream kernel.
Somehow I could not boot anymore and often got at the bootup to error message :
Gnome display manager. Dispatcher service... tpacpi::kbd_backlight"
1801038,2019-03-26 10:07:44 UTC,"Fix merged to master, will land in Stein: https://review.openstack.org/645614"
1801038,2019-03-26 10:19:48 UTC,Backports:
1801046,2018-12-12 11:13:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801052,2018-11-01 11:48:47 UTC,apport information
1801052,2019-11-14 04:18:08 UTC,"Hi Andre,
Thanks for reporting this."
1801052,2018-11-01 11:48:50 UTC,apport information
1801052,2018-11-01 11:48:46 UTC,apport information
1801052,2018-11-01 11:48:49 UTC,apport information
1801052,2018-11-01 11:48:45 UTC,apport information
1801052,2018-11-01 11:48:44 UTC,apport information
1801052,2018-11-01 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801052,2018-11-01 11:48:43 UTC,apport information
1801052,2018-11-01 11:48:41 UTC,apport information
1801052,2018-11-01 11:40:18 UTC,I have also tested this on the ubuntu running on 96 core TX system. Fails with linux-image-4.15.0-20-generic but passes with an alllocalconfig build of 4.19.
1801052,2018-11-01 11:48:46 UTC,apport information
1801068,2019-01-17 01:06:33 UTC,"Reviewed:  https://review.openstack.org/612374
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=45a118b0f4798a2527baee85d6a6b8fb859b0206
Submitter: Zuul
Branch:    stable/rocky"
1801068,2019-01-17 00:55:01 UTC,"Reviewed:  https://review.openstack.org/612373
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=0e3afdce42ec1e42c6eebf7407fe9de8f036a4c4
Submitter: Zuul
Branch:    stable/rocky"
1801068,2019-01-17 00:54:20 UTC,"Reviewed:  https://review.openstack.org/612372
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=048131984769de3955562a78a8f3652d86f75f05
Submitter: Zuul
Branch:    stable/rocky"
1801068,2019-01-08 19:25:34 UTC,"Reviewed:  https://review.openstack.org/612371
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=6652aaa477812c6e2b4c4faad708fbe05049507e
Submitter: Zuul
Branch:    stable/rocky"
1801068,2019-01-08 19:25:24 UTC,"Reviewed:  https://review.openstack.org/612370
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=38e16618bce0068478c901ba8dd6dbb55eae3e06
Submitter: Zuul
Branch:    stable/rocky"
1801068,2018-12-19 05:29:59 UTC,"Reviewed:  https://review.openstack.org/612304
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=56690bc3caac894c3dfec05eed6f0c5c64261520
Submitter: Zuul
Branch:    stable/rocky"
1801068,2018-11-14 04:16:43 UTC,"Reviewed:  https://review.openstack.org/613893
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=181fb4a0dcaef3484a50376679d8d3258f912fa4
Submitter: Zuul
Branch:    stable/rocky"
1801068,2018-11-14 04:16:34 UTC,"Reviewed:  https://review.openstack.org/612303
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=03c67d9a45a16c257927196b43d775d27f297d11
Submitter: Zuul
Branch:    stable/rocky"
1801068,2018-11-02 13:23:13 UTC,"Reviewed:  https://review.openstack.org/612302
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=f25a2f35b7ac739e6b18af92d708b99697a0eaf4
Submitter: Zuul
Branch:    stable/rocky"
1801068,2018-11-02 08:10:36 UTC,"Change abandoned by Martin Mágr (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/612304
Reason: Abandoning for now as this patch will block other to merge."
1801068,2019-01-03 03:14:57 UTC,"Reviewed:  https://review.openstack.org/612369
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=cf3946e7cecb4756b4686deebc5b2cff058f619d
Submitter: Zuul
Branch:    stable/rocky"
1801072,2018-11-01 13:17:32 UTC,Example error:
1801072,2018-11-01 13:21:53 UTC,this error is causing exception to be thrown when using iptables firewall see
1801072,2018-12-07 13:33:44 UTC,"Reviewed:  https://review.openstack.org/602384
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=165ed325917e5deadb274ad9c122db157c0b55b2
Submitter: Zuul
Branch:    master"
1801072,2018-12-10 21:51:42 UTC,This issue was fixed in the openstack/os-vif 1.13.0 release.
1801072,2019-05-30 17:13:02 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/609851"
1801072,2019-05-30 17:13:14 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/609850"
1801075,2019-08-26 14:49:02 UTC,"A SPARK library asked if this were possible. It would be a great feature to add, especially if combined with Bug #1783642."
1801088,2018-11-01 16:38:22 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1801091,2018-11-19 20:03:17 UTC,This bug was fixed in the package octavia-dashboard - 2.0.0-2.1ubuntu1
1801092,2018-11-01 14:18:18 UTC,"Hmm my initial idea is wrong, we do have the tags, digging further..."
1801092,2018-11-01 14:42:00 UTC,This shows we do have the tags
1801093,2018-11-01 16:21:57 UTC,I have not been able to duplicate this on either 3.0.13 or 3.2.1.
1801093,2018-11-01 19:17:57 UTC,"I just retested, and *headdesk*. As it turns out, the library had Hold Shelf Slip content in the Hold Transit Slips template."
1801094,2020-07-17 14:22:00 UTC,python3-octavia-dashboard has been seeded
1801094,2020-07-27 06:09:07 UTC,"[Summary]
OpenStack dashboard extension for Octavia (Load balancer as a service)."
1801094,2020-09-24 05:38:19 UTC,"Override component to main
octavia-dashboard 6.0.0~b3~git2020091410.570c51b-0ubuntu1 in groovy: universe/misc -> main
python3-octavia-dashboard 6.0.0~b3~git2020091410.570c51b-0ubuntu1 in groovy amd64: universe/python/optional/100% -> main
python3-octavia-dashboard 6.0.0~b3~git2020091410.570c51b-0ubuntu1 in groovy arm64: universe/python/optional/100% -> main
python3-octavia-dashboard 6.0.0~b3~git2020091410.570c51b-0ubuntu1 in groovy armhf: universe/python/optional/100% -> main
python3-octavia-dashboard 6.0.0~b3~git2020091410.570c51b-0ubuntu1 in groovy i386: universe/python/optional/100% -> main
python3-octavia-dashboard 6.0.0~b3~git2020091410.570c51b-0ubuntu1 in groovy ppc64el: universe/python/optional/100% -> main
python3-octavia-dashboard 6.0.0~b3~git2020091410.570c51b-0ubuntu1 in groovy riscv64: universe/python/optional/100% -> main
python3-octavia-dashboard 6.0.0~b3~git2020091410.570c51b-0ubuntu1 in groovy s390x: universe/python/optional/100% -> main
8 publications overridden."
1801100,2020-08-31 05:36:13 UTC,Hopefully fixed by merge #383939 once complete
1801100,2020-09-21 23:30:13 UTC,"Re: standard-approach, meaning, nagios monitor_self=true."
1801100,2020-06-19 06:29:09 UTC,"Ah, sorry, it's still there. Disregard."
1801100,2020-06-19 06:26:38 UTC,This doesn't appear to be a problem any more.
1801100,2020-08-31 05:14:29 UTC,"When referring to the ""standard approach"" - is this being defined somewhere? Feel free to email me directly with more context if it pertains to customer deployments."
1801101,2018-11-02 01:18:13 UTC,it's referenced here: https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/identity/v3/__init__.py#L24
1801101,2018-11-02 10:10:00 UTC,"Yes, the reference is correct. There's excess colon on line 211 in https://git.openstack.org/cgit/openstack/keystoneauth/tree/doc/source/authentication-plugins.rst"
1801101,2018-11-05 06:31:04 UTC,"oh, yeah, the format is not correct."
1801101,2019-05-23 06:01:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660886"
1801101,2019-05-29 16:59:15 UTC,"Reviewed:  https://review.opendev.org/660886
Committed: https://git.openstack.org/cgit/openstack/keystoneauth/commit/?id=2bb7f120c343774c7e7d27816c3c5eda1e88ccf7
Submitter: Zuul
Branch:    master"
1801101,2019-07-15 14:53:25 UTC,This issue was fixed in the openstack/keystoneauth 3.15.0 release.
1801103,2018-11-01 15:28:33 UTC,"The driver manager simply installs the nvidia driver/meta package for the compatible selected driver. If prime should be a dependency of that, then is really an issue with that package."
1801103,2018-11-01 22:41:04 UTC,"It's not needed for everyone, just for laptops with hybrid nvidia graphics. With current behavior some perfectly reasonable user actions render system unusable without CLI knowledge. IMO it's exactly driver managers' problem and it should not just install a package but make sure drivers are correctly installed for this system."
1801107,2018-11-29 21:20:47 UTC,I'm afraid we can't take patches through launchpad due to licensing issues. Can you submit this as a patch to https://review.openstack.org/#/admin/projects/openstack/futurist ?
1801111,2018-11-06 07:39:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615760"
1801111,2020-04-01 17:18:41 UTC,The example is removed in [1]. Thus marking this invalid.
1801125,2018-11-02 18:41:56 UTC,"OK, yes, it is a *very* long standing local customization! Thanks!"
1801125,2018-11-02 17:51:58 UTC,I just tested this in XUL on the MassLNC community demo server and see the same behavior Terran described.The password is based on the last four digits of the phone number only after entering the phone number for a new patron.
1801125,2018-11-02 17:29:05 UTC,"Weird. Resetting a password has always pulled the day phone last four digits for us. In the XUL, 3.0.13, it still does."
1801125,2018-11-02 17:29:58 UTC,Here's a screen shot of what I see.
1801125,2018-11-02 14:30:23 UTC,I'm not able to confirm this.
1801125,2018-11-02 17:49:01 UTC,"How strange. I've changed  this back to ""New"" rather than incomplete, so perhaps someone more familiar with that part of the code can chime in."
1801130,2019-02-28 18:09:15 UTC,"For some background, this was originally intended as a disincentive for relying on the pre-cat functionality vs actually cataloging an item.  Whether it's a good idea or not..."
1801130,2019-02-28 19:11:57 UTC,"I think it is still a good idea and would not want a precat to continually be available. For ILL items, perhaps we need a different solution than precats?"
1801131,2018-11-01 16:58:09 UTC,Converted from Question https://answers.launchpad.net/kicad/+question/675809
1801136,2019-11-01 18:46:55 UTC,"I retested the issue on Ubuntu 19.10, with following version of Guake:"
1801136,2019-11-02 21:21:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1801136"
1801136,2020-01-02 04:17:35 UTC,[Expired for guake (Ubuntu) because there has been no activity for 60 days.]
1801137,2020-04-19 17:41:14 UTC,"Thanks, Kyle and Jennifer!  The rebasil'd pasta was delicious.  Pushed to master, rel_3_5, rel_3_4, and rel_3_3."
1801137,2020-04-10 16:55:42 UTC,"Thanks Jane! I've rebasil'd the copy/pasta, and removed the title column link for precats, as well as making some wording changes(""Dummy title"" to ""Precat title"") after some additional feedback, and updated the branch."
1801137,2020-04-16 19:54:43 UTC,"Tested on our 3.5beta server and the title, author, and ISBN are displaying in Item Status in the expected places.  I love that the pre-cat title isn't a link in Item Status to the -1 catalogue record."
1801137,2020-03-11 21:09:47 UTC,I've pushed a branch here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1801137-item-status-display-precat
1801137,2020-03-22 04:14:00 UTC,"Thanks for the branch, Kyle.  It looks like there is a copy/pasto in the t_list file (all three columns just show the dummy title, instead of dummy author and dummy isbn)."
1801137,2018-11-01 18:44:09 UTC,Confirmed that this is an issue in 3.1.7.  My preference is also to have the same behaviour as in the web client check out and items out and xul item status.
1801137,2019-06-27 20:09:14 UTC,Confirming this is still an issue in 3.3
1801137,2020-01-30 19:43:58 UTC,"This would be useful, as trying to figure out which item is the precat item in a large list without checking every title in the list."
1801138,2019-10-01 20:15:55 UTC,"CEPH was upversioned in stx.2.0.  There are no current plans to address this LP. If this issue is important to the reporter please re-test on a current load and if a similar issue exists with the new version of CEPH, please create a new LP."
1801138,2019-07-15 21:36:26 UTC,"move to ""stx.dist.other"" since Daniel is working in that sub-project.
And this is just a warning and could be an enhancement in future."
1801138,2018-11-02 13:33:01 UTC,"The developers' guess was correct, the condition was reproduced after waiting/idling the cluster for approximately 24hrs.  Attaching the ceph command output again."
1801138,2019-03-12 14:29:14 UTC,Ceph update is still in progress. Unless we update the formula to compute the number of PGs it will reproduce.
1801138,2019-03-12 13:28:46 UTC,"This is a Low priority bug, should it be release gating?  Does it reproduce on the new updated Ceph?"
1801138,2018-11-05 19:01:25 UTC,stx.2019.03 - issue confirmed by the developer; would be nice to fix
1801138,2019-05-28 13:43:13 UTC,Removing stx.2.0 tag since this is a Low Importance Bug.
1801140,2018-11-01 18:27:50 UTC,Forgot to say that playing on the external monitor seem different even with the same tearing.
1801143,2019-05-21 17:31:48 UTC,Confirmed in 3.2.5 and in current master.
1801146,2020-01-22 14:17:05 UTC,This is still an issue in Evergreen 3.4.
1801146,2021-02-09 17:30:53 UTC,Also still an issue in 3.6
1801148,2019-01-02 12:45:55 UTC,You should try to re-install the package.
1801150,2018-11-01 19:40:32 UTC,"One more thing here related to the datasheet field visibility.  Let's say that you entered a link in the datasheet field for a symbol and discovered that all of them are visible now throughout the whole schematic.  You go back and try to delete it utilizing the same tool, only to discover that when you delete a field and hit save nothing changes.  You actually have to enter something into the cell, even if it is just a space and then hit save for the new value to take."
1801150,2019-07-02 00:15:03 UTC,"@Art & @Ron, let me know if this meets your needs."
1801150,2018-11-02 20:53:49 UTC,"Having both a ""Show"" and a ""Visibility"" checkbox there will hopelessly confuse many users (perhaps even me)."
1801150,2019-07-01 21:17:16 UTC,"Fixed in revision ad26ece8d4687aef45c28a0440b58ec0ae8d5baa
https://git.launchpad.net/kicad/patch/?id=ad26ece8d4687aef45c28a0440b58ec0ae8d5baa"
1801151,2018-11-02 02:42:59 UTC,"1. I've noticed Firefox's scrollbar is narrower by a pixel or two than fully native GTK+ apps for most themes. This seems to be a bug with how Firefox interprets the GTK+ theme. When I've tried them, Arc (arc-theme) seems to be closer to the same, as does Adapta."
1801151,2018-12-12 16:46:59 UTC,Thanks for the report William.
1801151,2019-05-16 04:17:29 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1801153,2018-11-07 11:25:40 UTC,It's not an upstream Horizon bug
1801153,2020-01-04 23:06:27 UTC,"hey, the issue is real, the openstack-dashboard in openstack rocky on top of the iubuntu 18 is unable to be installed. any tries to remove and fully remove and fix and install never succeeded."
1801153,2020-01-06 14:09:29 UTC,"The traceback indicates someone's personal django source [1] is being used which we can't support. If you're able to recreate this issue with packages fully installed from Ubuntu archives, please reopen this bug."
1801161,2019-08-08 17:24:57 UTC,"I currently have it from time to time in Artix/ Arch Linux (libreoffice-still 6.1.6-2), only using lcalc. It is triggered when I do some action, but too seldomly that I can really test what in detail triggers it."
1801161,2019-04-11 09:33:30 UTC,"Also, the bug still happens, but apparently less frequently, when libreoffice is launched with env variable LIBGL_DRI3_DISABLE is true (i.e: LIBGL_DRI3_DISABLE=true /usr/bin/libreoffice) as advised in https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984"
1801161,2019-04-08 06:51:31 UTC,"If that helps, here are all gtk2 related packages installed:"
1801161,2019-04-07 20:30:07 UTC,"Oliver: there's a bug for pcmanfm (https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984) with the same end result. This seems to somehow related to GTK2, as there are several other applications that show the same behavior (https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710). There's a file manager called SpaceFM one user tried and it showed the problems with the GTK2 version but not with the GTK3 version. This, coupled with Ilya's suggestion, leads me to believe GTK2 is indeed the result. With pcmanfm, though there are specific behaviors that cause the bug, it's not 100% reproducible. Sometimes those behaviors cause the error and sometimes they do not."
1801161,2018-11-19 15:40:54 UTC,Thank you for the report Chris.
1801161,2019-03-20 16:38:13 UTC,I have a similar bug with LibreOffice Writer. Application freezes with following traces in .xsession-errors:
1801161,2019-02-15 21:04:53 UTC,Solution: remove libreoffice-gtk2 and install libreoffice-gtk3
1801161,2019-02-15 04:17:25 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1801161,2018-12-16 19:10:43 UTC,I have similar bug with several applications: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1808710
1801161,2019-03-20 16:40:51 UTC,"Sorry, forgot to tell in #6 that libreoffice-gtk2 is already removed and libreoffice-gtk3 already installed."
1801163,2020-01-23 12:51:27 UTC,"I've given this one last once-over and all of the silly unicode that I threw in my template ended up in my inbox. Pushed to master, rel_3_4, and rel_3_3."
1801163,2019-02-08 21:41:27 UTC,I have pushed a branch to the working repository that resolves this issue in my testing (see the commit message for a test procedure).
1801163,2020-01-03 23:02:35 UTC,I've tested and pushed a signoff to user/gmcharlt/lp1801163_email_mime_signoff.
1801163,2018-11-01 22:15:24 UTC,"OK, Galen, I see you point after reading through the Github issue."
1801163,2018-11-01 21:12:55 UTC,"I want to point out related bug 1466502, and bug 1362260 which took the approach of installing Email::Send from CPAN."
1801163,2018-11-01 23:02:02 UTC,"Thanks! It occurs to me that dealing with Email::Sender at or around the same would be a good idea; if we end up adding a dependency on Email::MIME or Email::Stuffer, we may as well stack up other dependency changes."
1801163,2018-11-01 21:18:00 UTC,"I think the issues are orthogonal, as at first glance Email::Sender still needs something like Email::MIME to generate a correctly formatted (and escaped) email to send."
1801164,2018-11-02 00:21:20 UTC,"The attachment ""fix the port=0 issue"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1801164,2018-11-25 18:33:50 UTC,This bug has been fixed in the new upstream release 1.1.11 [1].
1801168,2019-09-30 00:03:49 UTC,This fix was landed to master last year.
1801169,2018-12-04 03:32:50 UTC,"Dear Luiz,"
1801169,2018-12-04 09:38:07 UTC,"Hello Santhost,"
1801173,2018-11-02 14:41:10 UTC,This bug was fixed in the package mia - 2.4.6-3ubuntu2
1801173,2019-01-27 19:24:10 UTC,This bug was fixed in the package mia - 2.4.6-4ubuntu2
1801173,2019-01-27 20:01:13 UTC,"reopening, just a work around"
1801183,2018-11-01 22:38:53 UTC,"OK, looking in /var/log/syslog, I see these entries from this morning's boot:"
1801183,2018-12-26 21:14:25 UTC,"Thank you Christian. I tried chrony in the past, but found it less featureful. I may try one of the other ntp packages. Meanwhile, I guess let's leave this open in case there's a solution."
1801183,2018-12-03 11:37:22 UTC,"Hi Andrew,
Sorry I can't help you from the logs I see, but I wanted to let you know that NTP had accrued way too many issues over the time.
Therefore from Ubuntu 18.04 and onwards the recommended and primarily supported ntp components are:
- systemd-timesyncd (if you need NTP client only, default installed)
- chrony (for more advanced NTP client logic)
- chrony (NTP serving)"
1801184,2018-11-03 01:00:43 UTC,"Hello Michael, or anyone else affected,"
1801184,2019-05-01 19:55:02 UTC,Also quickly tried https://github.com/tornadoweb/tornado/commit/00675409071b41650a5cd6894cafd921d16085ae but that didn't help on its own.
1801184,2019-05-01 19:19:39 UTC,"Indeed, just export ASYNC_TEST_TIMEOUT=30 doesn't help with the bionic + proposed build."
1801184,2019-04-29 11:03:21 UTC,"I added some hints on
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/34
and
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/35
for a possible fix and reasons for the failures.
I hope this helps!"
1801184,2019-07-24 16:25:51 UTC,Dropping the Cosmic task since Cosmic is now EOL.  The bionic task is still viable if someone sorts out reproducibility.
1801184,2019-04-25 08:51:17 UTC,"Any movement on this? The package has been around in -proposed for quite a long time. I'd say if this doesn't get a follow up fix in the nearest weeks, I'll drop it from -proposed."
1801184,2018-11-08 20:16:11 UTC,Turns out the package in release ftbfs too. I guess I get to fix that too!
1801184,2018-11-05 23:05:12 UTC,"An upload of python-tornado to bionic-proposed has been rejected from the upload queue for the following reason: ""I'm rejecting this because the same changes failed to build for cosmic.""."
1801184,2018-11-05 23:04:21 UTC,"I was looking at the SRU of this for bionic and noticed that the cosmic SRU still fails to build, so accepting it in Bionic seems premature."
1801184,2019-04-26 02:08:33 UTC,"No, no progress on this. The package ftbfs in release in both bionic and cosmic, in ways that are not obviously the same. I'm not very inclined to fix cosmic but I guess fixing bionic should be slightly higher priority."
1801184,2019-07-23 05:38:39 UTC,The version of python-tornado in the proposed pocket of Cosmic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.
1801189,2018-11-02 00:21:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1801189,2018-11-02 10:11:10 UTC,"unfortunately I am not able to recognize what package is the bug related to...
it is probably one of dnsmasq, network-manager-openconnect-gnome, network-manager-openconnect, openconnect, resolvconf"
1801189,2019-01-07 14:39:22 UTC,I have the same error on 18.04.1 up to date @ 7/1/2019
1801189,2019-01-07 17:03:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801189,2019-04-19 07:12:12 UTC,"I have the same issue!
If you know how to fix it, let us know!"
1801201,2019-10-15 10:49:47 UTC,I believe that pixmap icons are not supported by snapd. I've added a snapcraft task to ensure that this is caught at snap build and validation time.
1801205,2018-11-06 00:34:19 UTC,I'm just trying the GUI way not the CLI way (which I'm not familiar with.)
1801205,2020-08-19 00:37:11 UTC,Ubuntu 20.04 one of the main feature was to mount Veracrypt volumes with Gnome disk... Mmm... 2 years later and noup.
1801205,2020-09-30 14:12:45 UTC,"Thank you for your bug report, it sounds similar to what is discussed on https://github.com/storaged-project/udisks/issues/589"
1801219,2019-05-06 08:30:29 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801219,2019-09-01 15:07:44 UTC,0c608dad2a771c0a11b6d12148d1a8b975e015d4 2f7726f955572e587d5f50fbe9b2deed5334bd90 68bc30bb9f33fc8d11e3d110d29e06490896a999 711486fd18596315d42cebaac3dba8c408f60a3d
1801222,2019-05-06 08:15:56 UTC,any mcelog update for 19.04?
1801225,2018-11-05 09:58:58 UTC,"LLVM is maintained by Debian, nothing is happening on the Ubuntu side. You should report this kind of bugs on the Debian side.
Thanks"
1801225,2018-11-07 01:48:35 UTC,"Sylvestre, you already closed the corresponding Debian bug report with fixes :)"
1801225,2018-11-07 07:09:09 UTC,"@doko if I prepare the patch, can you help with a SRU? Thanks"
1801232,2018-11-02 03:00:06 UTC,This change was made by a bot.
1801232,2018-11-02 13:02:56 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1801232,2018-11-03 15:19:47 UTC,"Dear Joseph,
Unfortunately I am a Linux newbie. This means that I do not even know what
you mean by ""upstream kernel"". I do know that when I tried Ubuntu MATE
18.10 that after three days of error messaged I went back to 18.04. I am
still trying to recover data from the initial 18.04 total meltdown (I was
not even able to boot). After installing different versions of Ubuntu three
times in one week, I am leery of trying some method I do not know to try an
""upstream kernel""."
1801241,2019-04-23 15:12:04 UTC,This update missed the feature freeze for 19.04. It will be updated in 19.10 first in this cycle.
1801241,2019-05-23 21:06:41 UTC,"In one of the last rebases, I forgot to include this bug number in the debian changelog file, so this bug wasn't automatically closed."
1801241,2019-04-18 07:31:12 UTC,This Issue blocked AEP testing on VM too，We are expecting a usable pmdk added into 19.04.
1801241,2019-04-04 07:51:07 UTC,it is a must package for AEP.  Would Canonical add this into 19.04? it will not affect other packages.
1801241,2019-04-18 13:38:48 UTC,Latest PMDK version released in PMDK1.6.
1801267,2021-01-13 17:35:59 UTC,"Hello Ben, or anyone else affected,"
1801267,2021-01-13 23:35:40 UTC,"Hi Robie, Logan - thanks for looking after this."
1801267,2021-01-20 10:45:42 UTC,"Hi - FYI, after rereading the docs, my understanding is that I should change verification-needed to verification-done also, since bionic was the only release that actually needed verifying (and this was done successfully). So I've just done this now. - Ben."
1801267,2021-01-21 16:41:55 UTC,This bug was fixed in the package regina-normal - 5.1-2build2
1801267,2021-01-21 16:42:00 UTC,"The verification of the Stable Release Update for regina-normal has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1801281,2020-02-11 06:02:40 UTC,"once it is reproduced, reopen it."
1801282,2020-02-11 06:10:52 UTC,"if reproduce, just reopen it."
1801295,2019-03-20 14:49:59 UTC,This issue was fixed in the openstack/watcher-tempest-plugin 1.1.0 release.
1801296,2018-11-15 16:48:04 UTC,"Reviewed:  https://review.opencontrail.org/47429
Committed: http://github.com/Juniper/contrail-controller/commit/6e7af514eee1f8089273f4c2913c90e9ee01351b
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1801296,2018-11-15 05:47:12 UTC,"Review in progress for https://review.opencontrail.org/47686
Submitter: Parth Sarupria (<email address hidden>)"
1801296,2018-11-02 06:45:07 UTC,"Review in progress for https://review.opencontrail.org/47429
Submitter: Parth Sarupria (<email address hidden>)"
1801296,2018-11-15 05:51:58 UTC,"Review in progress for https://review.opencontrail.org/47429
Submitter: Parth Sarupria (<email address hidden>)"
1801303,2019-03-15 18:58:18 UTC,can you provide more information on what neutron network backend you are using.
1801303,2019-05-15 04:17:43 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1801306,2018-11-02 07:31:11 UTC,I started fixing this problem here: https://review.openstack.org/#/c/612733/5
1801306,2018-11-06 10:57:33 UTC,There are two patches in progress to fix this bug:
1801306,2018-11-20 16:53:40 UTC,"Reviewed:  https://review.openstack.org/612733
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=6f9bb77d9872a1cac4e1815ce13d97b8a143b3a8
Submitter: Zuul
Branch:    master"
1801306,2019-04-16 08:39:07 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1801306,2019-04-16 08:39:17 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/615813
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1801309,2018-11-13 13:51:45 UTC,"I think this needs to be expanded upon and is really part of the future ""enhanced federation"" bits."
1801309,2018-11-13 13:52:02 UTC,Added as wishlist.
1801314,2018-11-06 01:48:53 UTC,Than you for your reply. I have open the issue on gnocchiclient project at https://github.com/gnocchixyz/python-gnocchiclient/issues/97.
1801314,2018-11-05 13:27:37 UTC,"Hello jun923.gu,"
1801315,2019-10-17 12:00:04 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1801316,2019-04-26 20:29:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/656010"
1801316,2019-07-26 16:52:46 UTC,This issue was fixed in the openstack/cinder 12.0.8 release.
1801316,2019-05-15 20:12:19 UTC,"Reviewed:  https://review.opendev.org/656010
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=66133741602924c4a6509277bcb33a2f2aa042d1
Submitter: Zuul
Branch:    stable/queens"
1801316,2019-04-23 14:32:52 UTC,"This issue is present in queens, and so the fix needs to be backported to
stable/queens. The problem happens when upgrading from pike to queens
*without* changing the backup_driver to the new (in queens) format that
specifies the class name instead of the module name."
1801316,2019-04-23 14:34:09 UTC,Edit: Support for loading a driver by module name was finally REMOVED in stein.
1801316,2018-11-26 22:14:39 UTC,"Reviewed:  https://review.openstack.org/615455
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b90a13d07dcf230a509cc93a4c864a20494cf5e7
Submitter: Zuul
Branch:    stable/rocky"
1801316,2018-11-05 00:33:36 UTC,"Change abandoned by Brin Zhang (<email address hidden>) on branch: master
Review: https://review.openstack.org/615117
Reason: As Sean said, this problem exists in rocky and its previous version, abandon this patch, move this to stable/rocky.
Link the rocky commit: https://review.openstack.org/#/c/615455/"
1801316,2018-11-05 00:28:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/615455"
1801316,2018-11-02 09:50:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615117"
1801316,2018-11-02 12:33:32 UTC,"This is no longer the case in master (stein) since the ability to configure the backup driver by module name was removed. Stable branches do still have this since although it was deprecated there, it was still allowed. So this would be one of the rare cases where the patch can be proposed directly against stable/rocky and cherry picked from there."
1801316,2018-12-03 16:29:02 UTC,This issue was fixed in the openstack/cinder 13.0.2 release.
1801317,2018-12-05 14:43:04 UTC,The issue seems similar to https://gitlab.gnome.org/GNOME/nautilus/issues/411 where upstream stated that the minimal width is 729 and more than half of the screen which is why it's can be set.
1801317,2018-12-06 16:18:08 UTC,not a nautilus bug but a gnome-shell limitation
1801317,2018-12-07 08:31:53 UTC,"Another stupid limitation from GNOME.
Should be fixed as 1366x768 resolution is used very often.
Writing from laptop with this resolution.
If GNOME can't support then I'll remove GNOME."
1801317,2018-12-07 09:23:06 UTC,Upstream says that it is yours fault ( https://gitlab.gnome.org/GNOME/nautilus/issues/411#note_380767 ):
1801319,2018-11-07 11:27:36 UTC,Sowmya Divvi could you please verify that it's still valid for the latest release? We don't change AngularJS version for a while but we need to check it
1801322,2018-11-02 14:19:05 UTC,"I've found that the correct key is `notify-discharge`, which solves the problem."
1801325,2018-11-02 12:29:20 UTC,"This is probably a systemd issue, but we can account for it and fix it in mate-session-manager."
1801325,2018-11-02 12:27:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801325,2018-11-02 14:44:18 UTC,"Note that I filed this under ubuntu-mate because I only verified this behaviour under MATE, so I assumed it could be a mate-session-manager issue. Of course, I suspect it's really a systemd-logind problem, but I thought it might be wise to give it the benefit of the doubt… ;)"
1801328,2018-11-02 10:36:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615129"
1801329,2019-01-31 10:19:31 UTC,When are packages normally upgraded in Ubuntu? Only when a new Ubuntu release comes out? When Ubuntu 19.04 is released Sia might already be on version 1.4.1. It would be great if you could ship a recent Sia in the next Ubuntu release.
1801329,2020-10-22 20:04:48 UTC,the package is coming directly from Debian
1801338,2020-05-30 02:57:18 UTC,I met the issue when installing packages from a private PPA of Launchpad. Hope this would be helpful to reproduce the issue.
1801338,2019-12-05 11:26:43 UTC,"FWIW, I've not seen this bug in over a year, I totally forgot about it."
1801338,2020-08-21 14:04:39 UTC,This may be fixed now even.
1801338,2020-08-04 08:13:18 UTC,"I can't reproduce this anymore, so closing it."
1801338,2019-12-05 09:20:35 UTC,"Yes, it seems to have something with pipelining, so I disabled it with the following configuration:"
1801338,2019-12-05 11:30:17 UTC,"I don't even know how I setup the reproducer last year. I think I mirrored main in a trusty container and put an apache in front of it, but not sure"
1801338,2019-10-18 21:52:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801338,2019-04-11 23:28:05 UTC,"This can be reproduced by hosting a mirror on S3. S3 has built in functionality that closes a connection after 100 requests. We were able to add comments to apt source that output every time a new connection was made and we confirmed every 100 requests that S3 did close the connection. Intermittently, we would get the Undetermined Error during one of the connection close events. Debug output confirmed there is a connection: close header. We also confirmed apt identified a 102 connection reset by peer event by printing the error."
1801338,2018-11-19 12:50:42 UTC,"Yes, exactly, that's why it was removed from disco-proposed and I quickly reverted it in the followup upload. Though, the problem only seems to happen with apache based servers, if you put a squid in front of them, you're fine."
1801338,2018-11-19 11:22:49 UTC,And it made multiple buildds hang for days :-(. I just only noticed it now.
1801338,2018-11-15 17:50:30 UTC,It actually did not fix the issue.
1801338,2018-11-15 17:25:39 UTC,This bug was fixed in the package apt - 1.8.0~alpha2ubuntu1
1801338,2018-11-02 11:09:58 UTC,"It's unclear if xenial's apt is affected or not, we did not get to testing that yet."
1801338,2019-12-04 23:56:02 UTC,"Affects me on Bionic, too."
1801339,2019-02-18 14:05:48 UTC,Can you make detailed a code proposal?
1801339,2019-05-21 04:17:21 UTC,[Expired for Dr. Geo II because there has been no activity for 60 days.]
1801341,2018-11-14 11:12:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801342,2018-11-02 11:50:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615141"
1801342,2020-05-27 19:48:31 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.opendev.org/615141"
1801345,2018-11-11 19:54:10 UTC,"sorry to disturb you also when I try ""sudo update && sudo apt upgrade -y"" I have this error
Atteint:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Atteint:2 http://fr.archive.ubuntu.com/ubuntu bionic InRelease
Atteint:3 http://archive.canonical.com/ubuntu bionic InRelease
Atteint:4 http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu bionic InRelease
Atteint:5 http://fr.archive.ubuntu.com/ubuntu bionic-updates InRelease
Atteint:6 http://archive.canonical.com bionic InRelease
Atteint:7 http://fr.archive.ubuntu.com/ubuntu bionic-backports InRelease
Ign:8 http://ppa.launchpad.net/kile/livepreview/ubuntu bionic InRelease
Atteint:9 http://ppa.launchpad.net/kile/master/ubuntu bionic InRelease
Err:10 http://ppa.launchpad.net/kile/livepreview/ubuntu bionic Release
  404  Not Found [IP : 91.189.95.83 80]
Lecture des listes de paquets... Fait
W: La cible Packages (partner/binary-amd64/Packages) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible Packages (partner/binary-i386/Packages) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible Packages (partner/binary-all/Packages) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible Translations (partner/i18n/Translation-fr_FR) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible Translations (partner/i18n/Translation-fr) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible Translations (partner/i18n/Translation-en) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible DEP-11 (partner/dep11/Components-amd64.yml) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible DEP-11 (partner/dep11/Components-all.yml) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible DEP-11-icons-small (partner/dep11/icons-48x48.tar) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible DEP-11-icons (partner/dep11/icons-64x64.tar) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible DEP-11-icons-hidpi (partner/dep11/icons-64x64@2.tar) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible DEP-11-icons-large (partner/dep11/icons-128x128.tar) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible CNF (partner/cnf/Commands-amd64) est spécifiée plusieurs fois dans /etc/apt/sources.list:45 et /etc/apt/sources.list.d/xenial-partner.list:4
W: La cible CNF (partner/cnf/Commands-all) est spécifiée plusieurs fois..."
1801345,2018-11-11 21:14:28 UTC,😄
1801345,2018-11-11 20:04:42 UTC,"And from the new version of downloader -
http://launchpadlibrarian.net/370382340/bgoffice-dict-downloader_0.10_all.deb
it works well thank you :)"
1801345,2018-11-11 19:41:31 UTC,"Thank you for your reply :) but when I try with ""sudo install"" I have this error  ""install: opérande de fichier manquant"""
1801345,2018-11-11 16:39:54 UTC,"Link is for manual download. Full path:
https://sourceforge.net/projects/bgoffice/files/Full%20Pack%20of%20Dictionaries/1.0/full-pack.tar.bz2
I have installed gbgoffice 1.4 [a GTK2 (gtkmm) vertion of kbgoffice] from
ubuntu repository. After that:
[image: image.png]
Sorry for my english, 😄"
1801345,2018-11-11 17:53:50 UTC,"No it not a problem and thank you for your reply.
In the fist step I did "" sudo make install"" and I have this message"
1801345,2018-11-11 14:20:45 UTC,I tried but I have this error
1801345,2018-11-11 13:48:51 UTC,"I suppose the problem is that the link is broken.
I found the dictionaries at:
https://sourceforge.net/projects/bgoffice/files/ .
That solved the problem for me.
Thank you!"
1801345,2018-11-10 16:35:07 UTC,thank you Launchpad Janitor for your replay but I can not find status in bgoffice-dict-downloader.
1801345,2018-11-06 16:17:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801345,2018-11-11 19:02:40 UTC,"[image: image.png] is the same step - ""sudo install"". Now you mast have all
dictionaries installed. Run gbgoffice and test. 😄
I found new version of downloader -
http://launchpadlibrarian.net/370382340/bgoffice-dict-downloader_0.10_all.deb
."
1801349,2018-11-08 16:10:35 UTC,"Colin, sorry, no; it's the bug that 'found' the issue; it's basically saying that we aren't enabling a particular gate test (i.e. it's staying dev-) due to this bug."
1801349,2018-11-13 16:41:03 UTC,Thanks Colin for tracking this done; very pleased it's not a kernel bug.  I'll now take this up with the snappy team.  Thank again for doing the detective work; much appreciated!
1801349,2018-11-13 11:35:37 UTC,After adding a lot of debug into the kernel I can see what is causing the issue:
1801349,2018-11-12 10:50:51 UTC,"Ryan, my bad -- I should have updated the bug; I've provided Colin with a serverstack bastion and some scripts to do testing, and Colin has been doing that.  Apologies that the bug didn't reflect this new information."
1801349,2018-11-12 10:48:50 UTC,"Hi Colin - We believe we've provided that in comment #3 above.  It is a fresh Cosmic instance, followed by reproducer commands.  Please let us know if this does not allow you to reproduce.  Thank you."
1801349,2018-11-08 16:43:23 UTC,"Hi Alex,"
1801349,2018-11-08 15:46:31 UTC,Is the above commit a fix to this issue?
1801349,2018-11-02 15:41:03 UTC,Further details of the vanilla nova instance:
1801349,2018-11-07 20:04:13 UTC,I added debug into the kernel and observed /dev/vdb is being mounted by systemd:
1801349,2018-11-07 16:59:38 UTC,"This is not a zfs related bug per se, it's more of a kernel related, so I'm re-assigned the bug"
1801349,2018-11-07 16:58:40 UTC,Some notes:
1801349,2018-11-07 14:58:10 UTC,"Can you supply me the commands required to reproduce this issue, I'm not familiar with the test environment you are using."
1801349,2018-11-05 19:24:33 UTC,"Additionally, after the umount, the jbd kernel thread is still running for the block device, which is why it can't be claimed."
1801349,2018-11-02 14:58:45 UTC,Also checking on a non-juju serverstack cosmic instance:
1801349,2018-11-02 14:13:27 UTC,Please provide a vanilla (non-charm) repro with a straightforward nova boot approach and confirm with those findings and logs here.
1801349,2018-11-08 11:06:28 UTC,"Reviewed:  https://review.openstack.org/609024
Committed: https://git.openstack.org/cgit/openstack/charm-lxd/commit/?id=ff0ee580b808102be534c3f6035bcc157799c325
Submitter: Zuul
Branch:    master"
1801349,2018-11-02 12:45:18 UTC,"An option, for the test, is to change the lxd storage to a ""dir"" and *avoid* zfs.  However, the underlying cause should be resolved."
1801352,2018-11-05 04:50:42 UTC,"hrm, when I duplicated this basic stuff into diskimage-builder, I had a couple of problems with the prompt getting all mixed up with the final output, which made me put a sleep in [1]"
1801352,2018-11-22 12:14:35 UTC,"There are no processes left running when I get into the error condition except for the ""tee"" process."
1801353,2020-01-22 08:07:40 UTC,Fixed by camitk-4.1.2-2
1801353,2019-11-06 05:59:04 UTC,"This bug was closed in debian. Everything looks fine now.
Should we close this bug?"
1801353,2020-01-22 08:06:34 UTC,Closing this bug as it was closed by version 4.1.2-2
1801353,2020-01-22 08:07:07 UTC,Fixed in 4.1.2-2
1801355,2019-01-11 13:01:38 UTC,InVesalius was already ported to Python3. The package from Debian Testing is already updated with this version.
1801359,2019-08-15 07:52:54 UTC,"I think there is issues in handling such case in gnome-shell/bionic itself. With an Intel card only platform, one may login via gdm displayed on the external monitor. But when logged in, the built-in display will have the content of a second one, and the external monitor will be blank. Then if you unplug HDMI and replug in, the external monitor will have the content of a second one, but the built-in display will be off."
1801359,2019-08-13 13:32:15 UTC,"* with nvidia proprietary driver 430 and Disco runtime/kernel-5.0.0-23-generic, one can login via the external monitor while the built-in one still remains off. Mainline kernel v5.2.8 has the same situation, but v5.3-rc4 gets worse as it can't even set the external monitor resolution right."
1801359,2019-05-31 16:51:09 UTC,I'll see if this also happens to the Precision 5520 in our lab.
1801359,2019-08-14 03:17:27 UTC,"* `edp_panel_vdd_on` related:
  good:
  ```
  [drm:edp_panel_vdd_on [i915]] Turning eDP port A VDD on
  [drm:edp_panel_vdd_on [i915]] PP_STATUS: 0x80000008 PP_CONTROL: 0x0000000f
  ```
  bad:
  ```
  [drm:edp_panel_vdd_on [i915]] Turning eDP port A VDD on
  [drm:wait_panel_power_cycle [i915]] Wait for panel power cycle
  [drm:wait_panel_status [i915]] mask b800000f value 00000000 status 00000000 control 00000002
  [drm:wait_panel_status [i915]] Wait complete
  [drm:edp_panel_vdd_on [i915]] PP_STATUS: 0x00000000 PP_CONTROL: 0x0000000a
  [drm:edp_panel_vdd_on [i915]] eDP port A panel power wasn't enabled
  ```"
1801359,2019-05-29 03:20:59 UTC,Does this issue still happen?
1801359,2018-11-02 13:30:06 UTC,This change was made by a bot.
1801359,2019-05-29 06:36:36 UTC,"Yes it still happens even with recent Ubuntu and Linux Kernel (5.1).
I guess it's neither a Ubuntu nor a Linux Kernel problem but a bios problem of the Dell Precision 5520 but unfortunately I have no Windows installed to verify."
1801359,2018-11-02 16:59:25 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1801359,2019-08-13 09:07:50 UTC,"I managed to reproduce this on a Precision 5520 with Bionic, kernel 5.0.0-23.24~18.04.1-generic:"
1801359,2018-11-15 20:22:48 UTC,"This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug."
1801359,2018-11-02 18:11:59 UTC,It always happend on this notebook (since one year on the last 3 Ubuntu releases)
1801362,2019-05-03 08:17:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801363,2018-11-02 18:17:53 UTC,"> But sometimes the indicators aren't visible even when they differ from the
> standard settings. I'm ok with that setup but it has to work :)
"
1801363,2018-11-02 17:15:20 UTC,"Did I implement that bug/feature for the exact scenario you discovered it? ;)
The indicators are visible only if the setting differs from standart 2-deck settings."
1801363,2019-05-10 12:36:49 UTC,https://github.com/mixxxdj/mixxx/pull/2075
1801363,2018-11-13 14:12:48 UTC,https://bugs.launchpad.net/mixxx/+bug/1803140
1801363,2018-11-04 01:09:38 UTC,We can add a control type or control parameter for this. Can you file a bug?
1801363,2018-11-03 23:58:03 UTC,that would make the control more predictable as there are no sudden jumps from left to right anymore.
1801363,2018-11-03 23:56:31 UTC,"maybe it would also improve the ux if the button states are toggled
0-1-2-1-0-1... instead of 0-1-2-0-1..."
1801363,2018-11-02 17:35:56 UTC,"But sometimes the indicators aren't visible even when they differ from the standard settings.  I'm ok with that setup but it has to work :).  And I'm not sure it's a good idea to make them disappear again when the user is changing the orientation, because maybe they need to go through the default setting to get to the setting they want."
1801363,2018-11-03 21:34:03 UTC,yeah this is a relatively low priority fix
1801363,2018-11-03 21:34:09 UTC,"sounds good, thanks!"
1801363,2018-11-03 18:39:58 UTC,"Your PR does fix the current behavior.  I still don't like how if the right deck is set to M, and I'm in two-deck mode, and single click makes the control just vanish (because now it's the default value).  I think it'd be better to just have the controls always be visible in 2-deck mode."
1801363,2018-11-02 18:23:13 UTC,"quick fix for current behaviour:
https://github.com/mixxxdj/mixxx/pull/1881"
1801363,2018-11-03 19:32:25 UTC,"Okay, I see your point and I can just remove the condition.
Otoh to avoid incosistency across skins, we'd have to squeeze the xfader buttons next to the xfader in Deere (that's the only reasonable place I can imagine without reworking the Deere mixer)."
1801363,2018-11-03 18:40:19 UTC,"""and single click"" -> ""a single click"""
1801364,2018-11-02 14:12:10 UTC,Example data for the case that triggered this issue:
1801364,2019-12-10 19:11:29 UTC,"> Just did a test and it *does* seem to persist with the latest commits
> on the master branch :).
... (emphasis added)
> So, what would be needed to consider this bug closed?
"
1801364,2019-12-10 16:34:29 UTC,"Alright, thanks folks."
1801364,2019-12-10 14:45:46 UTC,"> I can't figure it out; the commit where this was added was the same as the initial Openstack. Openstack documentation doesn't say if we should be injecting this somewhere either.
"
1801364,2019-12-10 14:30:00 UTC,"@Eric,
It should be fixed in that it will no longer stack trace as it did.
The path to failure was:
a.) openstack has 'random_seed' which (not surprisingly) had non-utf8 data in it
b.) cloud-init tries to persist data from the metadata service by storing json
c.) json can only serialize/store utf-8 data.
d.) stack trace on attempt to do so."
1801364,2019-12-10 13:42:01 UTC,"On 12/10/19 8:22 AM, Eric Lafontaine wrote:

> I'm trying to understand how this bug is considered fixed by the
> following commit; https://git.launchpad.net/cloud-
> init/commit/?id=067516d7
>
> We have resolved the issue by just not base64 decoding;
> -        if 'random_seed' in metadata:
> -            random_seed = metadata['random_seed']
> -            try:
> -                metadata['random_seed'] = base64.b64decode(random_seed)
> -            except (ValueError, TypeError) as e:
> -                raise BrokenMetadata(""Badly formatted metadata""
> -                                     "" random_seed entry: %s"" % e)
>
> Could somebody help me with some information about why we try to get the
> random_seed and interpret it?
"
1801364,2019-12-10 13:22:48 UTC,I'm trying to understand how this bug is considered fixed by the following commit; https://git.launchpad.net/cloud-init/commit/?id=067516d7
1801364,2019-12-19 23:00:18 UTC,"This bug is believed to be fixed in cloud-init in version 19.2-53. If this is still a problem for you, please make a comment and set the state back to New"
1801364,2019-05-16 22:35:48 UTC,The patch in https://bugs.launchpad.net/cloud-init/+bug/1801364/comments/2 fixes this issue for me using python2.7 on rhel7 and centos7.
1801364,2018-11-02 14:33:21 UTC,The patch is one possible implementation of avoiding the utf-8 error when persisting the metadata.
1801364,2019-09-27 20:46:04 UTC,"This bug is fixed with commit 067516d7 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=067516d7"
1801364,2018-11-02 18:14:15 UTC,"Robert,
Can you please attach logs?"
1801364,2018-11-02 18:30:11 UTC,"Yes, sorry, this is Python version dependent, fails with Python 2.7, works with Python 3."
1801364,2019-12-10 18:25:22 UTC,Just did a test and it does seem to persist with the latest commits on the master branch :).
1801364,2018-11-02 18:34:17 UTC,Log file that shows the failure.
1801364,2018-12-03 21:03:24 UTC,"I'm attaching a test case that shows the failure on python2.7.
The issue is in the way that we're serializing binary data into
json.  The implementation we have (using default=json_serialize_default)
just does not work in python2.7."
1801364,2019-03-27 14:07:17 UTC,If someone fixes this correctly/generically then they should probably remove the Azure specific fix at https://code.launchpad.net/~jasonzio/cloud-init/+git/cloud-init/+merge/365065 .
1801372,2018-11-02 14:45:17 UTC,See also bug 1648278
1801380,2018-11-08 14:48:36 UTC,"Happened again, this time when opening firefox right after gnome-terminal was opened and moved to the right side of the screen. The terminal window portion can be seen in the firefox window area."
1801382,2019-09-01 04:17:27 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1801382,2019-09-01 04:17:25 UTC,[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60 days.]
1801382,2019-07-02 16:22:23 UTC,Do you still get the issue in newer versions/series? What image exactly has the wrong color?
1801382,2018-11-13 13:35:41 UTC,Todays update of evince (3.30.1-1ubuntu1.2) did not change anything.
1801382,2018-11-02 16:17:54 UTC,"Checked by myself now. Opened the original file with evince, opened the print dialog and clicked the preview button. The preview already shows the problem. So the problem already occurs before the job gets to CUPS. It is a problem of evince and/or GTK. Moving ..."
1801382,2019-07-02 16:41:01 UTC,"Hi to all,"
1801382,2018-11-02 16:14:29 UTC,How did you print the file? Did you print it out of a PDF viewer? Which one? Could you try another PDF viewer or direct printing from the command line?
1801383,2019-09-17 09:20:40 UTC,"Hi Brian,"
1801383,2019-10-02 09:56:47 UTC,This bug was fixed in the package thunderbird - 1:68.1.1+build1-0ubuntu1
1801383,2019-09-17 12:20:25 UTC,"Marc, the version currently in eoan-proposed has the fix. I'm working on addressing autopkgtest issues in related packages that prevent thunderbird from migrating to the release pocket."
1801383,2019-09-17 09:21:42 UTC,"Olivier,"
1801383,2019-09-19 13:31:50 UTC,"WifiSyslog does contain SSID information. While this will be removed from the thunderbird and firefox packages, I don't think it would be appropriate to remove it from the linux kernel apport reports."
1801383,2018-12-20 16:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801383,2018-12-22 03:03:02 UTC,"`apport-bug linux` uploads WifiSyslog.txt, so this also affects apport hook for the linux package."
1801383,2018-11-05 11:32:54 UTC,"Thank you for your bug report, that indeed seems an issue"
1801383,2019-03-21 18:51:20 UTC,"The linux kernel apport hook is provided by apport directly, so needs to be fixed there:"
1801383,2018-11-28 19:15:22 UTC,"@osomon +1, thanks!"
1801383,2018-11-27 09:06:34 UTC,I removed the attach_wifi() call in the apport hook. This will make it to the next firefox stable update.
1801383,2018-12-05 15:57:31 UTC,This bug was fixed in the package firefox - 64.0+build1-0ubuntu1
1801386,2019-04-11 11:53:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801388,2019-02-19 13:08:06 UTC,Is this still an issue?
1801391,2018-11-02 20:45:21 UTC,Just a few notes on this bug:
1801391,2018-11-02 22:34:04 UTC,"Hi Heather,"
1801391,2018-11-06 14:20:05 UTC,"Those config items affect cloud-init script behaviour itself, but after reproducing this I see this when dumping APT config:"
1801391,2018-11-06 15:15:08 UTC,"I should note that plain --config doesn't apply to all models. You need to
use --model-default w bootstrap"
1801391,2018-11-06 20:45:59 UTC,"But apt-get has been previously run, when the custom image was built."
1801394,2018-12-18 08:09:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801420,2020-06-08 18:33:49 UTC,This still happens in MAAS 2.6.2
1801420,2019-09-30 12:05:53 UTC,Is this still an issue with MAAS 2.6.1?
1801420,2018-11-12 02:54:43 UTC,"Did more testing and it appears it's install_kvm that's broken in 2.5.0~beta4-7361-g401d6, both CLI and GUI.  Does not appear to have anything to do with passing user-data."
1801420,2019-11-30 04:17:40 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1801420,2018-11-06 05:18:56 UTC,"Hi Mike,"
1801420,2018-11-06 19:46:04 UTC,"With the information provided in this bug report, I can't narrow the cause of the failure down to the user-data blob. A week or two ago I hit bug #1800573, which had a symptom that exactly corresponds to the failure mode in your logs, but I subsequently can't reproduce it (with the latest code on the MAAS master branch)."
1801420,2018-11-02 22:09:48 UTC,Attachment also includes cloud-init.log and cloud-init-output.log from a failed host.
1801420,2018-11-15 16:09:48 UTC,"Hi Craig,"
1801420,2018-11-06 03:02:52 UTC,The vendor-data for installing KVM is complex[1]; depending on what your're doing I can see that you could easily cause a conflict between your custom user-data and this vendor-data.
1801420,2018-11-06 03:10:30 UTC,"Thanks for attaching the logs - I did find one thing that needs fixing[1], but I'm not certain it has anything to do with the user-data you provided."
1801420,2018-11-06 02:57:26 UTC,"Using install_kvm causes the cloud-init vendor-data to be preset by MAAS. If you are providing custom user-data, it will need to be provided in a specific way (documented by the cloud-init team[1]) so that it can be merged correctly."
1801421,2018-11-09 05:49:24 UTC,Does this fade to black occur if you don't make the changes?
1801421,2018-11-09 09:06:35 UTC,"I am unsure what do you mean by ""make the changes""? It only happens when I save a configuration and restart the pc. If I change the display resolution, but don't save it then it doesn't happen (neither immediately and neither after I restarting the PC). I hope this answers your question..."
1801421,2019-04-13 21:46:48 UTC,Are you sure this isn't xscreensaver kicking in?
1801421,2019-04-13 23:24:26 UTC,Also: how long does it stay black?
1801421,2019-06-08 12:25:44 UTC,"I disabled screensaver (Mode, select Disable Screen Saver)."
1801422,2020-03-07 11:17:03 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1801423,2019-12-16 04:17:27 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1801423,2019-12-16 04:17:26 UTC,[Expired for snapd because there has been no activity for 60 days.]
1801423,2019-10-16 06:18:59 UTC,"Snapd uses the standard way for this, i.e. it writes desktop files into XDG_DATA_DIRS. Maybe lxqt-panel is not monitoring all XDG_DATA_DIRS for changes ? Not sure what snapd can do about this."
1801423,2018-11-03 00:38:50 UTC,Lubuntu as a project and LXQt as a project do not support snaps.
1801423,2018-11-03 12:37:36 UTC,"I haven't tried restarting the LXQt panel, but I suppose it would work."
1801423,2018-11-03 03:23:41 UTC,"Have you tried restarting LXQt panel that should probably do the trick as a
better workaround."
1801427,2019-07-15 18:36:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801427,2019-07-15 20:05:49 UTC,"a dpkg --force-overwrite -i  /var/cache/apt/archives/texlive-latex-recommended-doc_2017.20180305-1_all.deb
got me a little further."
1801429,2018-11-05 10:53:31 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1801429,2018-12-03 15:04:16 UTC,"This affects me as of updating to 18.10. All Google Talk accounts complain that the connection is untrusted. The certificate details show a CN of ""invalid2.invalid"" and an OU of ""No SNI provided; please fix your client."""
1801434,2018-11-18 11:30:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801441,2018-12-10 01:14:50 UTC,>>> Surprise! <<<
1801441,2018-11-19 06:31:08 UTC,I find that a minimum of 1024x712 is necessary to show the entire window.
1801441,2020-02-09 22:17:04 UTC,Updating since this is released.
1801441,2019-04-15 03:50:54 UTC,So looking at the log I find:
1801441,2019-04-11 04:17:59 UTC,[Expired for calamares (Ubuntu) because there has been no activity for 60 days.]
1801441,2018-11-21 06:06:33 UTC,"I realize my previous message is a bit obtuse, if not completely incomprehensible. The question is that you seem to have a 1024x768 window which is larger than the 1024x712 minimum I found. So can you confirm that it indeed does not work with 1024x768 on a fresh boot of the live CD? If so, I'm really going to be surprised."
1801441,2019-02-08 19:36:25 UTC,What about the persistence thing?
1801441,2019-02-08 04:17:28 UTC,[Expired for calamares (Ubuntu) because there has been no activity for 60 days.]
1801441,2018-12-10 01:15:44 UTC,Here is the monitor settings window.
1801441,2019-02-09 02:39:59 UTC,Oops!  Sorry!
1801443,2018-11-03 01:58:03 UTC,My ISP's mirror is reported (https://launchpad.net/ubuntu/+archivemirrors) as two hours behind
1801443,2018-11-03 02:26:36 UTC,Maybe also useful (three bug reports that occurred & are possibly linked)
1801443,2018-11-22 08:12:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801443,2020-11-23 05:14:58 UTC,Thank you for reporting this bug to Ubuntu.
1801443,2021-01-23 04:17:40 UTC,[Expired for scowl (Ubuntu) because there has been no activity for 60 days.]
1801447,2018-11-03 02:23:23 UTC,Here is the second of the two screen images.
1801449,2020-11-23 05:00:40 UTC,Thank you for reporting this bug to Ubuntu.
1801449,2021-01-23 04:17:39 UTC,[Expired for scowl (Ubuntu) because there has been no activity for 60 days.]
1801455,2019-06-11 07:56:55 UTC,"Reviewed:  https://review.opendev.org/609003
Committed: https://git.openstack.org/cgit/x/python-scciclient/commit/?id=ae7bc81d103dfaf9414dbfca3d3a2a08d1d01b42
Submitter: Zuul
Branch:    master"
1801456,2018-12-12 10:41:38 UTC,This issue was fixed in the openstack/networking-generic-switch 1.3.0 release.
1801465,2018-12-05 16:21:40 UTC,"Reviewed:  https://review.openstack.org/614947
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=3ff0ba1f273d247307206608580e8a2df6a652df
Submitter: Zuul
Branch:    master"
1801465,2018-11-05 01:33:55 UTC,Could you please just post a single Bug for the whole fix list? I saw you have post multiple bugs for each project.
1801465,2018-11-27 10:38:28 UTC,https://review.openstack.org/#/c/614942/
1801465,2018-11-21 00:18:02 UTC,"Reviewed:  https://review.openstack.org/614956
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=5e3f3ce32afaf4e7eb853181dc334f3e386994bd
Submitter: Zuul
Branch:    master"
1801465,2018-11-29 19:03:27 UTC,"Reviewed:  https://review.openstack.org/614942
Committed: https://git.openstack.org/cgit/openstack/networking-sfc/commit/?id=6f171fee70feedf70be073ee7b08b8ead2cfe258
Submitter: Zuul
Branch:    master"
1801466,2019-09-03 08:01:40 UTC,"The fix was merged: https://review.opendev.org/614931, but the bug number was wrong in the commit msg."
1801477,2019-02-19 13:09:03 UTC,Please provide more information about what's expected here.
1801477,2019-03-21 17:27:26 UTC,This issue was fixed in the openstack/octavia 4.0.0.0rc1 release candidate.
1801477,2019-05-21 04:17:22 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1801478,2018-12-06 10:44:10 UTC,This issue already have been fixed in https://review.openstack.org/#/c/614963/
1801483,2018-11-15 05:04:25 UTC,"Change abandoned by Vieri (15050873171@163.com) on branch: master
Review: https://review.openstack.org/614937"
1801484,2019-10-30 14:57:29 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/615077"
1801494,2019-03-19 17:27:59 UTC,"I had this problem with a fresh install of Ubuntu Mate 18.10 on a 2008 white Macbook, 2.4 GHz. dual-booting with MacOS 10.6.8, using rEFInd. I have never seen the menu bar of Ubuntu Mate on this install, it was absent on the first boot."
1801494,2019-03-20 02:04:51 UTC,If you experience this problem then please run:
1801494,2019-05-19 04:18:07 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1801494,2019-05-20 17:33:20 UTC,This bug hasn't been addressed and is obviously still an issue. Why was it allowed to expire?
1801494,2019-05-21 02:05:57 UTC,"I can't see any reason for the dock going permanently missing in that log. It might be a good idea if anyone experiencing this problem opens a new bug with all the required attachments, by running:"
1801494,2019-05-20 20:01:57 UTC,it expired because no-one added the info requested in comment #18
1801494,2019-05-20 20:45:30 UTC,"OK, I've attached the requested info from my system. It goes back 4 days, so it should include the period when it stopped working. Unfortunately I can't tell you exactly when that was - having the dock autohide means it's pretty much hidden until I need it."
1801494,2019-07-20 04:17:30 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1801494,2019-02-17 10:09:01 UTC,"Could those having the issue give a description of how/when they get the dock missing and also attach their journalctl log after getting the problem? Also describe the extensions you are using and the session yoiu logged in (default, wayland, GNOME...)"
1801494,2019-05-20 17:53:08 UTC,"I can get the dock back with alt-f2-r to restart the gnome shell, so I have a workaround for now. But this is obviously an issue."
1801494,2019-02-16 16:25:00 UTC,"Also,  I have no customizations to the OS generally.  I am using the OS video driver for amd."
1801494,2018-11-17 15:12:58 UTC,"I havn't had this error again since I reported it, but what your saying makes sense. I'm pretty sure my screen was turned off as well and I have a AMD RX580, and had to reboot a bunch of times when the system locks up (not sure how related but hasnt happened in a while)."
1801494,2019-02-14 10:07:29 UTC,"Same here. Everytime I resume my session after lock, I lose the Dock. Reenabling the extension in Tweaks didn't do anything. Dock still is gone."
1801494,2019-02-16 16:00:56 UTC,"I'm now seeing this issue, after messing with my monitor cables.  I only have a single monitor.  I was trying to get my DVI to work on my AMD RX550 card - which will not display while logged in (but does at bios)."
1801494,2018-11-03 14:17:44 UTC,"@philrego, please can you expand on your points 4 and 5 in the bug description: dock is/is not there."
1801494,2018-11-04 02:52:41 UTC,I read through that thread. Not sure if there is much more I can add now. When I restart the computer it comes back but this has happened a few times before. Someone mentioned thunderbird i was using that. A screen dimming app. Ill post again if i notice anything.
1801494,2018-11-05 01:43:17 UTC,"Philip,"
1801494,2018-11-16 09:53:33 UTC,"Hi,"
1801494,2018-11-13 11:08:59 UTC,"I'm seeing this same issue. The dock disappears after the machine turns off the monitor after 5 minutes of inactivity. I don't have hibernate or suspend enabled. Per Daniel's suggestion, I ran gnome-tweaks and enabled the Ubuntu Dock extension..."
1801494,2018-11-19 02:53:18 UTC,That crash looks unrelated. And generally anything about your graphics driver is unrelated to this bug.
1801494,2018-11-19 03:32:25 UTC,No i mean i havnt got this bug again since i reported it. I installed gnometweaks and the extentions were already set to enabled.
1801494,2018-11-22 00:00:39 UTC,It happened again today. I put the computer to sleep. Turned off the TV. Started it next morning. Turned on TV. And the dock isn't here.
1801494,2018-11-17 15:02:38 UTC,"I havn't had this error again since I reported it, but what your saying
makes sense. I'm pretty sure my screen was turned off as well and I have a
AMD RX580, and had to reboot a bunch of times when the system locks up (not
sure how related but hasnt happened in a while)."
1801494,2019-01-21 14:48:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801496,2019-01-24 09:13:44 UTC,"Dear Till,"
1801496,2019-01-18 14:54:24 UTC,A problem I have observed in the logs is that foomatic-rip calls Ghostscript twice here. Once to convert the PDF input into PostrScript and then to convert the PostScript into PCL XL.
1801496,2019-01-18 13:55:37 UTC,"One thing you should test is to run Ghostscript separately. For this, take the Ghostscript command line from the error_log and feed your PDF file directly into it. How long does it take? Is it much faster than running as part of the print job? Or is it more or less the same?"
1801496,2019-01-17 14:25:21 UTC,"Sorry for the late reply, I had some other more urgent tasks to do."
1801496,2019-01-17 09:34:21 UTC,"Dear Till,"
1801496,2019-01-04 09:12:17 UTC,"Dear Till,
Happy new year!
I'am very sorry to bother you again."
1801496,2019-01-18 09:47:33 UTC,"Dear Till,"
1801496,2018-11-15 09:32:03 UTC,"Dear Till,
  Thanks for your investigation of this problem."
1801496,2018-12-05 01:02:55 UTC,"Dear Till,
      I'am very sorry to bother you again.
We are still working hard to looking for cause why Ubuntu 16.04 printing performance slowdown.
      We figure out that there are many cause may slowdown the print job.
The other cause than OS may slowdown the print job, and we are working on those cause’s investigation.
Here are some slowdown point about OS issues that we can't investigation deeper, we hope that you(or your team) can offer a help for the investigation."
1801496,2018-11-07 10:02:32 UTC,"We are reported that users(who are affect by this problem ) can't do their job normally. Such as, doctors' consulting speed are seriously delay by the medical diagnostic document printing speed."
1801496,2018-11-08 09:28:53 UTC,To find out about the slowing down I need some more information:
1801496,2018-12-27 09:41:08 UTC,"Dear Till,
      I'am very sorry to bother you again."
1801496,2018-11-12 10:10:20 UTC,"Dear,
Our user have huge printing job to do in the next week(November 20). So, they are eagerly want to know that can we offer them an workaround(an fixed solution would be best) for this slowdown problem."
1801496,2018-11-12 13:25:42 UTC,I have looked into the error_log files and the processing by the filters on 16.04 takes ~20 seconds and on 14.04 less time. The 326 seconds you observe on 16.04 is caused by the printer's processing of the PostScript it receives. The PostScript is generated by Ghostscript (you find the Ghostscript command lines used in the error_log files).
1801496,2018-11-09 09:47:40 UTC,Below are the information about this slowdown problem:
1801498,2018-11-03 23:13:07 UTC,"I booted x86 thumb-drive and there are 11 entries between ""American English"" and ""British English (United Kingdom)"" on x86/i686 installer, I didn't even see ""Australian English"" (which doesn't worry me anyway [i'm aussie])"
1801498,2019-03-04 21:22:02 UTC,"In the Calamares welcome screen, languages are sorted in the list by their ISO language name (e.g. Russian, Korean, Greek, etc.) but their native language name (e.g. русский, 한국어, ελληνικά, etc.) is displayed. Languages with different localized variants (look at Spanish/español) are grouped together. There is one exception to this: American English is always at the top. It seems there is a bit of reluctance in doing so, but it is certainly intentional:
https://github.com/calamares/calamares/commit/59537d86d65ffc190cd2f74587b2893161065c19
That said, it's certainly not random. The other Englishes are where they belong. It's just American English that's weird. Strange, but not terrible. If you don't need American English, it's not even strange."
1801498,2019-03-04 22:39:14 UTC,Upstream issue linked.
1801498,2019-07-13 19:24:24 UTC,This was resolved in the most recently updated version:
1801498,2019-03-04 22:38:30 UTC,"Ok, I changed my mind. After some discussion with the developers, there's some ideas on how to resolve this."
1801499,2019-01-14 11:31:18 UTC,"See above. xdg-screensaver (and hence caffeine{,-indicator}) does not use xscreensaver under GNOME."
1801499,2020-08-31 16:02:16 UTC,"Closing, as I won't be fixing for 18.04 any more."
1801499,2019-03-09 09:16:13 UTC,Report on Kubuntu 18.04.2
1801499,2019-01-18 02:38:14 UTC,"Tried alternative 'Brightside' to stop xscreensaver using corner 'hotspot'... hotspot seems to 'activate', but xscreensaver STILL activates...."
1801499,2019-01-14 06:40:38 UTC,"using Ubuntu 18.04LTS and caffeine/caffeine indicator will no longer prevent screensaver from activating - say - when playing full screen video - broken caffeine or broken Ubuntu (from latest update?)? Used to work fine - indicator will display on bar at top and allow 'activate' (steam comes out of 'cup'), but won't prevent Xscreensaver from running on full screen videos, etc. Any 'alternative'?"
1801499,2018-11-21 16:28:48 UTC,"I also confirm it doesn't work with 18.04.01 32bits, gnome 3.28.2:
caffeine and caffeine indicator are in processes list
caffeine indicator button is not visible
xscreensaver is not disabled when playing full screen video (firefox or VLC)"
1801499,2018-11-21 20:26:00 UTC,"In GNOME, xdg-screensaver (and hence Caffeine) will interact with GNOME's desktop idleness inhibition, not xscreensaver."
1801499,2018-11-03 19:04:21 UTC,"I'm not sure what you mean by ""the tool bar""."
1801499,2018-11-12 06:52:15 UTC,"caffeine-ng has built-in code to manage screensaver inhibition, whereas caffeine uses xdg-screensaver. All the evidence so far is that the problem is in xdg-screensaver."
1801499,2018-11-12 01:00:56 UTC,"i can confirm that on 18,10 does not work"
1801514,2018-11-07 09:58:25 UTC,UPDATE to Bug Description!
1801514,2018-11-29 11:53:42 UTC,"I think I found the problem for that bug. I switched to Ubuntu Budgie because that 'auto screen rotation' was very annoying and I found out that the new installed os had some screen glitches and flashes like in elementary, so I went to the BIOS and found out that my video drive memory was set tot „Auto”. I modified that value to 512mb and now everything works fine.
I didn't switch back to elementary os yet but I'm guessing that if that solved the glitches and screen flashes on Budgie it will solve the screen rotation from elementary os."
1801521,2019-06-11 19:55:19 UTC,This has been fixed since Disco was released.
1801533,2018-11-03 16:18:58 UTC,"Same problem: it does not matter if upgraded from 18.04 or installed new with 18.10. lightdm might not allways be capable initializing graphics leeding to some loop together with systemd turning on backlight, turning it off again, then restarting."
1801533,2018-11-03 16:22:32 UTC,"This schouldn't happen. lightdm should only be started about 10 times, then disabled."
1801533,2018-11-03 16:24:27 UTC,This bug exists since 16.10 – we are at 18.10 now it is now two years with this monitor killing bug.
1801535,2018-12-08 16:20:03 UTC,"On Sat, Dec 8, 2018 at 10:19 AM Alton Cedervall <email address hidden>
wrote:"
1801535,2018-12-08 16:19:06 UTC,"I realise you have a lot of work, but if you go to the software download
program and check out the software boutique you will see a notice saying
that the program is being reworked."
1801535,2018-12-08 12:51:09 UTC,"Seems to be the same bug as bug 1806459, https://bugs.launchpad.net/ubuntu-mate/+bug/1806459, software boutique broken on 32bit UM"
1801535,2018-11-12 18:35:56 UTC,"Still an issue and I have loaded Ubuntu Mate on three computers and same issue. I can load software from terminal so I can deal, but a pain in the rump never the less."
1801535,2018-11-05 18:16:43 UTC,"You are correct as I did not give you the full info necessary.  The
software version is Ubuntu mate version 18.04.1 32 bit version. I could not
find the software bboutique version as it won't load. Please help. Thank
you.."
1801535,2018-11-05 18:14:46 UTC,"You are correct as I did not give you the full info necessary.  The
software version is Ubuntu mate version 18.04.1 32 bit version. I could not
find the software bboutique version as it won't load. Please help. Thank
you.."
1801535,2018-11-03 16:36:57 UTC,I will mark this as incomplete because we don't have a Ubuntu Mate versio in the description and a software boutique one.
1801540,2019-08-26 22:42:23 UTC,Just chiming in: I applied the upstream patch[1] with success on my older-kernel system.
1801540,2019-08-22 04:44:55 UTC,"(In reply to Vinay Shastry from comment #261)

> Distortion/crackled sound in steam voice chat started with kernel 5.2.9.
> Differently distorted sound in discord web - parts of voice is chopped off
> every half second or so, and a large lag - 1 second or so.
>
> Everything works fine in 5.2.8.
>
>
> Board: ASUS PRIME X370-PRO.
> lspci -nn extract:
> 0c:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h
> (Models 00h-0fh) HD Audio Controller [1022:1457]
>
>
> Is there a way to disable this patch - with a bootparam perhaps?
"
1801540,2019-08-21 17:31:24 UTC,"(In reply to Vinay Shastry from comment #261)

> Everything works fine in 5.2.8.
"
1801540,2019-08-21 08:01:35 UTC,"Distortion/crackled sound in steam voice chat started with kernel 5.2.9.
Differently distorted sound in discord web - parts of voice is chopped off every half second or so, and a large lag - 1 second or so."
1801540,2019-08-20 19:31:14 UTC,"Asus A88X-Pro (Realtek 1150)
I join the problem in Discord"
1801540,2019-08-16 08:58:22 UTC,"(In reply to Khaled from comment #256)

> I have MSI A320m mobo with a Realtek ALC887 and got the same problem not
> sure if others are having another problem with this chip but if i connect a
> speakers to the rear panel and a headset to the front panel it only detects
> my front panel it even says ""unplugged"" in audio settings i have to unplug
> the headset to get audio from the speakers no hardware problems since it
> works just fine on Windows 10
"
1801540,2019-08-15 20:05:39 UTC,"(In reply to Ernst Sjöstrand from comment #257)

> (In reply to Khaled from comment #256)
> > I have MSI A320m mobo with a Realtek ALC887 and got the same problem not
> > sure if others are having another problem with this chip but if i connect a
> > speakers to the rear panel and a headset to the front panel it only detects
> > my front panel it even says ""unplugged"" in audio settings i have to unplug
> > the headset to get audio from the speakers no hardware problems since it
> > works just fine on Windows 10
>
> This is not related to crackled sound capture.
"
1801540,2019-08-09 23:45:40 UTC,No issues here with Steam Voice Chat with patch 7 on 1022:1457.
1801540,2019-08-15 10:33:35 UTC,"I have MSI A320m mobo with a Realtek ALC887 and got the same problem not sure if others are having another problem with this chip but if i connect a speakers to the rear panel and a headset to the front panel it only detects my front panel it even says ""unplugged"" in audio settings i have to unplug the headset to get audio from the speakers no hardware problems since it works just fine on Windows 10"
1801540,2019-08-11 16:24:40 UTC,"(In reply to Luca from comment #254)

> That's true, Steam Voice Chat has distortions/delays for 1 minute (but
> totally different than the usual like it was on Discord)
> Also, my voice has a much lower pitch too, and only for one minute.
>
> But I noticed this is happening on Discord too right when I join a channel
> (or do a voice self test) for 2 seconds.
"
1801540,2019-08-11 11:25:06 UTC,"That's true, Steam Voice Chat has distortions/delays for 1 minute (but totally different than the usual like it was on Discord)
Also, my voice has a much lower pitch too, and only for one minute."
1801540,2019-08-10 13:52:44 UTC,"(In reply to Marco from comment #251)

> (In reply to al from comment #250)
> > (In reply to Takashi Iwai from comment #249)
> > > (In reply to al from comment #248)
> > > > Thanks that did it works great now!
> > >
> > > OK, I'll add the entry for 1022:1487 in the upstream, too.
> >
> > Ok thanks, I tested with discord and load-module module-loopback and it
> > works perfectly.
> >
> > But with steam I tested my voice for the first minute of testing I sound
> > like a demon, and in valve games the mic is still distorted.
> >
> > Any info I can provide?
>
> That is unfortunately correct, in Steam Voice Chat the audio is still
> stuttering like crazy :S
"
1801540,2019-08-27 20:22:13 UTC,"(In reply to Takashi Iwai from comment #249)

> (In reply to al from comment #248)
> > Thanks that did it works great now!
>
> OK, I'll add the entry for 1022:1487 in the upstream, too.
"
1801540,2019-08-09 18:15:26 UTC,"(In reply to al from comment #250)

> (In reply to Takashi Iwai from comment #249)
> > (In reply to al from comment #248)
> > > Thanks that did it works great now!
> >
> > OK, I'll add the entry for 1022:1487 in the upstream, too.
>
> Ok thanks, I tested with discord and load-module module-loopback and it
> works perfectly.
>
> But with steam I tested my voice for the first minute of testing I sound
> like a demon, and in valve games the mic is still distorted.
>
> Any info I can provide?
"
1801540,2019-08-09 15:52:25 UTC,"(In reply to Takashi Iwai from comment #249)

> (In reply to al from comment #248)
> > Thanks that did it works great now!
>
> OK, I'll add the entry for 1022:1487 in the upstream, too.
"
1801540,2019-08-15 12:18:25 UTC,"(In reply to Khaled from comment #256)

> I have MSI A320m mobo with a Realtek ALC887 and got the same problem not
> sure if others are having another problem with this chip but if i connect a
> speakers to the rear panel and a headset to the front panel it only detects
> my front panel it even says ""unplugged"" in audio settings i have to unplug
> the headset to get audio from the speakers no hardware problems since it
> works just fine on Windows 10
"
1801540,2019-08-28 11:57:30 UTC,"ASRock Fatal1ty B450 Gaming K4
ALC892, [1022:1457] subsys [1849:9893]"
1801540,2019-09-01 10:54:10 UTC,"(In reply to Takashi Iwai from comment #271)

> And how is the application set up?  Does it run over PulseAudio backend or
> accesses directly ALSA devices?
"
1801540,2019-08-28 12:34:13 UTC,"(In reply to Ernst Sjöstrand from comment #267)

> So you can have different $THING ALC1220 vs ALC892 but still the same pciid
> 1022:1457 ...
"
1801540,2020-04-20 10:09:29 UTC,The problem still seems to affect Raven Ridge ([1022:15e3] in a HP ProBook 455R G6) using kernel version 5.6.4.
1801540,2019-11-26 07:21:23 UTC,"Why the issue is back?
i remember in Linux kernel 5.3 RC7 it was fixed but now it's back my audio codec is ALC887-VD"
1801540,2019-10-27 18:03:29 UTC,Confirming this for ALC887-VD Analog [ALC887-VD Analog]
1801540,2019-10-09 19:07:16 UTC,"(In reply to Marco from comment #276)

> Following my previous post, disabling the batch flag on both streams (patch
> 3 from comment 269), Steam is perfect, Discord is lagged again while
> acquiring.
>
> With the second patch from the comment 269, same identical problem without
> the patch (Discord perfect, Steam crackling for the first minute + audio
> slightly delayed). However when changing volume there was a little bit of
> distortion on the output audio (extremely small, but still audible,
> especially on high volumes), but it seems that using the workaround only on
> acquisition seems to have removed that small issue. If someone here had the
> same problem when changing volume, please try patch n.2 and report back.
>
> It seems that we can't have both working together simultaneously on my end.
> The default workaround is still the best option on my system, for now.
"
1801540,2019-09-20 11:19:58 UTC,"(In reply to Takashi Iwai from comment #280)

> Yours has a different controller chip, so the patch doesn't have any effect
> as is.
>
> Try a freshly submitted / merged patch on top of the previous fixes:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/
> ?id=d2c63b7dfd06788a466d5ec8a850491f084c5fc2
"
1801540,2019-09-20 07:36:06 UTC,"Yours has a different controller chip, so the patch doesn't have any effect as is."
1801540,2019-09-19 01:08:29 UTC,"This patch, as applied to the latest 5.3 kernel, is not working on my SO's desktop machine, running Arch Linux, still glitching in Discord voice chat."
1801540,2019-09-16 05:32:24 UTC,(In reply to Takashi Iwai from comment #271)
1801540,2019-09-14 12:57:35 UTC,"in the final release of Linux 5.3 are going to be these patches?
I ask because I am buying an amd laptop right now with ryzen 5 3550 H and want to know how was going this problem !
In an acer swift with AMD ryzen I had the problem"
1801540,2019-09-06 19:26:59 UTC,"Following my previous post, disabling the batch flag on both streams (patch 3 from comment 269), Steam is perfect, Discord is lagged again while acquiring."
1801540,2019-09-06 12:13:51 UTC,"(In reply to Takashi Iwai from comment #273)

> Hmm, would it be only about playback?  That is, restricting the workaround
> only to capture stream works better?
>
> --- a/sound/pci/hda/hda_controller.c
> +++ b/sound/pci/hda/hda_controller.c
> @@ -617,7 +617,8 @@ static int azx_pcm_open(struct snd_pcm_substream
> *substream)
>          * tsched=1 when a capture stream triggers.  Until we figure out the
>          * real cause, disable tsched mode by telling the PCM info flag.
>          */
> -       if (chip->driver_caps & AZX_DCAPS_AMD_WORKAROUND)
> +       if ((chip->driver_caps & AZX_DCAPS_AMD_WORKAROUND) &&
> +           substream->stream == SNDRV_PCM_STREAM_CAPTURE)
>                 runtime->hw.info |= SNDRV_PCM_INFO_BATCH;
>
>         if (chip->align_buffer_size)
>
>
> In anyway, we need to know this change makes sense at all.  IOW, people need
> to check whether this causes yet another regression on the devices that have
> worked with BATCH workaround.
"
1801540,2019-09-02 00:36:03 UTC,"(In reply to Takashi Iwai from comment #269)

> For all people who still see the problem: please test 5.3-rc6 or rc7 kernel
> and confirm that the problem persists.
"
1801540,2019-09-01 12:31:23 UTC,"Hmm, would it be only about playback?  That is, restricting the workaround only to capture stream works better?"
1801540,2019-08-09 09:26:12 UTC,"(In reply to al from comment #248)

> Thanks that did it works great now!
"
1801540,2019-09-01 08:28:49 UTC,"OK, that's good to know."
1801540,2019-09-01 07:30:28 UTC,"(In reply to Takashi Iwai from comment #269)

> For all people who still see the problem: please test 5.3-rc6 or rc7 kernel
> and confirm that the problem persists.
"
1801540,2019-08-29 12:55:29 UTC,For all people who still see the problem: please test 5.3-rc6 or rc7 kernel and confirm that the problem persists.
1801540,2019-08-28 12:27:15 UTC,So you can have different $THING ALC1220 vs ALC892 but still the same pciid 1022:1457 ...
1801540,2019-08-09 00:16:03 UTC,"(In reply to Takashi Iwai from comment #247)

> (In reply to al from comment #245)
> > I just picked up a new MSI MPG X570 GAMING EDGE WIFI with Realtek ALC1220.
> Judging from alsa-info.sh output, your device has a different PCI device ID,
> 1022:1487.  Replace the entry and retest.
"
1801540,2019-04-23 19:40:39 UTC,I have the same problem with MSI B450 Tomahawk Motherboard
1801540,2019-08-08 06:25:42 UTC,"(In reply to Ernst Sjöstrand from comment #244)

> So with patch 7, but tsched=1 (ie. not the part with |= BATCH included) I
> get the following:
>
> Only test idea 1: crackling
> 1+2: no crackling but playback skips when start/stop recording
> 2: no crackling but playback skips when start/stop recording
>
> I retested patch 2 and realized I also have that behavior there: no
> crackling but playback skips when start/stop recording.
"
1801540,2018-12-19 12:00:01 UTC,"@Luca,"
1801540,2018-12-19 11:09:00 UTC,Any updates on this?
1801540,2018-11-27 17:14:54 UTC,"Created attachment 279675
Recording showing the noise"
1801540,2018-11-27 17:14:05 UTC,"Tried all those values through HDAAnalyzer, but nothing relevant changed, the noise is still there."
1801540,2018-11-27 16:39:50 UTC,"So yes even with the module-echo-cancel enabled is still happening, I'll try modifying the realtek patch on the kernel"
1801540,2018-11-06 03:17:09 UTC,"Probably the FreeBSD is working as Windows, they use the software de-noise filter when users record sound."
1801540,2018-11-05 19:23:24 UTC,1) Happens with both Front mic and Rear mic.
1801540,2018-12-19 12:49:04 UTC,Yes I already did that but I may not understand how to add the required maintainers into the mailing list
1801540,2018-11-05 01:26:18 UTC,"Does this issue happen on Front Mic, Rear Mic or LineIn?"
1801540,2018-11-03 22:09:33 UTC,"https://help.ubuntu.com/community/ReportingBugs
--
Cristian Aravena Romero (caravena)"
1801540,2018-11-03 18:39:27 UTC,"I tried running it, I don't know honestly if that worked because when I clicked on that link a browser page just appeared showing nothing relevant"
1801540,2018-11-03 17:56:37 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801540,2018-11-03 17:36:51 UTC,"Created attachment 279301
alsa-info"
1801540,2017-06-18 18:52:22 UTC,To elaborate on this bug:
1801540,2017-06-18 18:46:14 UTC,"Created attachment 257067
alsa-info of offending hardware"
1801540,2017-04-09 18:55:48 UTC,"Audio playback seems to be fine, however audio capture results in crackling."
1801540,2018-11-03 22:21:07 UTC,"Uhm yes I know that, but apport-collect is just not working as I already said..."
1801540,2019-08-08 06:27:26 UTC,"(In reply to al from comment #245)

> I just picked up a new MSI MPG X570 GAMING EDGE WIFI with Realtek ALC1220.


Judging from alsa-info.sh output, your device has a different PCI device ID, 1022:1487.  Replace the entry and retest."
1801540,2018-12-19 13:05:23 UTC,I may confirm that recording without pulseaudio using ffmpeg -alsa produces the same disturbed sound
1801540,2018-12-20 01:36:25 UTC,"Done, for sending an email to them using that CC you mean without the bugzilla site?"
1801540,2019-06-28 16:26:07 UTC,"Most reports mention ALC1220, but the same bug occurs in older AMD systems also."
1801540,2019-06-28 16:04:38 UTC,Bug 195303 (ALC1220 snd_hda_intel Sound capture is crackled / distorted) is the most detailed and active of several open bug reports about this.
1801540,2019-06-08 12:58:57 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=195303
1801540,2019-06-08 12:57:39 UTC,"Some info regarding this, looks like a common problem with also other different codecs and the only thing in common is the AMD chipset."
1801540,2019-02-19 12:09:40 UTC,"Just for curiosity, how did you test if it works or not?"
1801540,2019-02-18 23:45:52 UTC,Got it fixed by in with my MIO-892:
1801540,2019-02-15 23:25:26 UTC,"i've the same Problem on Ubuntu 18.10.
I'm running a Asus P9D-X (no Onboard Sound) with a Asus MIO 892 (Realtek)-Card which is detected as Intel-HDA:
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)"
1801540,2018-12-20 00:27:24 UTC,you might have a try with adding <email address hidden> and <email address hidden> to the CC list.
1801540,2019-01-08 17:49:11 UTC,"Seems to be the same problem as https://bugzilla.kernel.org/show_bug.cgi?id=195303
With ALC1220 codecs"
1801540,2019-01-04 00:23:15 UTC,"Actually this workaround adds another problem, in games the sound is delayed..."
1801540,2019-01-03 23:18:24 UTC,A partial workaround which doesn't completely fix the issue but improves things is the following:
1801540,2018-12-25 23:07:42 UTC,There are other people having the same issue on the same motherboard model
1801540,2018-12-25 19:03:14 UTC,"I have exactly the same problem, and I also have an MSI B350 am4 motherboard..."
1801540,2018-12-21 01:50:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801540,2018-12-20 11:52:30 UTC,Motherboard model is an MSI B350M AM4 for Ryzen CPU's
1801540,2018-12-20 03:13:04 UTC,put the bugzilla link in the email.
1801540,2019-01-04 22:52:01 UTC,Following up that I'm experiencing the same issue on an MSI B450 AM4 motherboard with the same realtek chipset.
1801540,2019-02-19 00:20:25 UTC,"Tried that, it does not work for me"
1801544,2019-01-05 14:45:31 UTC,"Interesting. One workaround is to switch to icon-grid mode in Nautilus, rather than list mode. Then you have white space to click on."
1801544,2020-06-19 18:52:05 UTC,This is fixed upstream (development releases only so far) by simply removing the nautilus integration in favor of an in-app browser.
1801544,2020-06-19 02:01:01 UTC,This bug is still present in Ubuntu 18.04.3.
1801547,2019-11-06 03:01:04 UTC,There is no improvement for me as well. I had some time to look closer at it.
1801547,2019-11-08 04:15:42 UTC,winpthreads again.  Ugh.
1801547,2019-11-08 17:22:11 UTC,"Interesting.  I just thought I wasn't seeing this on my windows box
because it's a pretty fast system but now that I think about it, my
windows builds are using clang due to a gcc build issue with one of the
dependency libraries.  I think this gcc dependency build issue has since
been fixed but my build config is still using clang.  Maybe we should
convert our windows builds over to clang instead of gcc to see if that
resolves this issue.  Good catch Seth."
1801547,2019-11-08 18:06:42 UTC,Can someone provide a clang build? I’d like to see if it improves.
1801547,2019-11-20 15:22:20 UTC,"I'm experiencing same behavior in several stable versions and also in a recent nightly (5.99.0-393-gd4cea0f2b). Also running Windows 10 x64, with an i7-2600 3.4GHz CPU and middle of the road GFX card (Radeon HD 6700M). Waited some time for this to disappear (~ 1 year), expected it to be a temporary bug, but the problem seems pretty persistent."
1801547,2019-11-20 17:02:51 UTC,@Nick-  What do we need to generate a test clang build?
1801547,2019-11-20 19:15:22 UTC,"Possibly (not) related, after working on KiCAD stable for a while switched to nightly (5.99.0-393-gd4cea0f2b) yesterday."
1801547,2019-11-28 18:45:20 UTC,"@Seth, sorry, I forgot this. It should be possible, it looks like there is a clang toolchain for mingw in the msys2 repos. But last time I updated the build environment my patch job stopped working, and I am not quite sure why. But probably a PEBCAK because the nigthly builds using makepkg works fine."
1801547,2018-11-06 17:36:04 UTC,@Igor-
1801547,2019-11-29 16:08:06 UTC,@Wayne-
1801547,2019-11-29 17:24:33 UTC,"@Seth, it's not a build error.  Clang actually crashes.  Here is the output of the crash:"
1801547,2019-11-29 17:42:06 UTC,"@Wayne, what are your cmake args to make it use clang? I never tried it on my windows environment."
1801547,2019-11-29 18:00:39 UTC,"@Nick, all you need to do is set the environment variable CC=clang and CXX=clang++ and run cmake to create the build configuration as you normally would.  CMake picks up clang as the compiler and sets up the build environment accordingly.  I'm guessing you could also set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER as well but I never tried that."
1801547,2019-11-29 18:51:59 UTC,Grrrrrr!  I just tried a 64 bit build with the clang 8.0.1-3 package and I'm getting the same error.  Now I'm beginning to wonder how this ever built on clang.  Did we change libcontext.cpp recently?
1801547,2019-11-29 19:08:22 UTC,"Just to add insult to injury, clang 7.0.1-1 wont even run so I'm at the end of my rope here."
1801547,2019-11-29 19:21:04 UTC,I tried to build Kicad with clang on W7 32 bits.
1801547,2019-11-29 23:53:47 UTC,"Concerning the compiler crash, here's a patch that enables libcontext's winfiber API also for MSYS/MINGW (not tested as I don't have a Windows setup with MSYS here)."
1801547,2019-11-06 01:02:17 UTC,"Previously I was on ""Version: (5.1.4)-1, release build"", and I just tried the above ""Version: (5.1.5-rc1-4-g167d408b5)-1, release build"" - there doesn't seem to be any change in behavior (it's still choppy)."
1801547,2019-11-29 15:19:02 UTC,"I finally found some time to test this again and I do see the choppy move behavior with 5.1.5 downloaded from the KiCad website.  The downloaded version of the KiCad windows installer was build with gcc 9.2.0.  I tried to update my clang builds but apparently the latest version of clang (both 32 and 64 bit builds) crashes attempting to build libcontext.cpp so I cannot go back and confirm the clang behavior without doing a downgrade of clang.  This most likely explain why @Nick saw a build failure.  If someone else has an older version of clang (the latest is 9.0.0) and has the time to confirm this behavior, I would appreciate it."
1801547,2019-11-03 02:34:37 UTC,@gregoryfitz- Can you try with the 5.1.5RC1 nightly build from https://kicad-downloads.s3.cern.ch/windows/testing/5.1/kicad-5.1-jenkins-450-x86_64.exe ?  We have recently updated the packaging versions and would like to know if this affects the threading issues.
1801547,2019-04-01 15:04:53 UTC,"@Nick, the video is comparing two different versions of KiCad (5.0.0-rc2 and 5.1.0 IIRC, check the original bug report)"
1801547,2018-11-07 00:32:05 UTC,Thanks for the quick build. I installed the version you linked. Behavior is about the same.
1801547,2018-11-07 00:54:09 UTC,Can you post information about your graphics card?  Are the drivers up to date?
1801547,2018-11-07 02:52:12 UTC,"Sure,
The display graphics card info is below. I noticed that you mentioned 5.0.2-dev. Did I install the right release? The release info in my install says 5.0.1-39."
1801547,2018-11-07 08:35:27 UTC,"Seth,"
1801547,2018-11-07 17:32:30 UTC,@Igor-
1801547,2018-11-07 23:53:58 UTC,"Hi Seth,"
1801547,2018-11-08 00:13:49 UTC,Thanks.  Doesn't seem to be board-specific.  At least there is no lag that I can detect on Linux.  I'll try in my VM tomorrow.
1801547,2018-11-15 00:45:31 UTC,"Tried in a windows 10 VM (mac os host). Move was smooth but crashed shortly after, probably due to Bug #1798460."
1801547,2019-04-02 21:37:08 UTC,"Ahh ok, I missed that. Disregard the comments #19 and #17."
1801547,2018-12-16 21:50:09 UTC,"I am the author of Bug #1807610 and am also experiencing this behaviour. I am running a fairly powerful PC, with an i5-4430 and a GTX 1080 Graphics card so I am expecting system performance to not be a factor here."
1801547,2018-12-17 22:46:11 UTC,Good insight.
1801547,2019-01-04 22:40:08 UTC,I don't think so.  At least not in a way that will ensure other libraries are not loaded as I believe that this depends on your system settings (I could be mistaken in this)
1801547,2019-03-31 19:18:44 UTC,Can we statically link our version of winpthreads into the build?
1801547,2019-04-01 11:20:35 UTC,Maybe it is possible to use process explorer to check which dll it uses?
1801547,2019-04-01 13:20:36 UTC,<I'm a users who raised one of the duplicate bug reports>
1801547,2019-04-01 13:41:51 UTC,But I thunk I saw a bugreport where the user was on linux and he had two windows of pcbnew open at the same time. Only the one window showed laggy move of the footprint.
1801547,2019-04-01 14:13:33 UTC,"I recently formatted and re-installed Windows 10 and Kicad 5.1. I am still getting the same behavior.
Maybe it's a system/driver issue?"
1801547,2019-04-01 14:54:24 UTC,"Ok, I found the video I was talking about in #17."
1801547,2018-12-17 22:32:00 UTC,I suspect that this is an issue with your threading libraries.
1801555,2020-05-06 22:19:22 UTC,Also happens on Kubuntu 19.10!
1801555,2018-12-19 13:51:16 UTC,Confirmed on version 18.10 of Kubuntu amd64 as well.
1801555,2020-05-06 21:16:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801555,2018-11-04 15:16:23 UTC,"https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices
--
Cristian Aravena Romero (caravena)"
1801555,2018-11-05 17:50:33 UTC,"@caravena wrote:

> https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices
"
1801555,2018-11-04 00:30:25 UTC,I have reproduced this a third time and it seems was also able to confirm that the md device returns out of sync data:
1801555,2018-11-04 00:43:03 UTC,Package versions:
1801561,2020-04-20 07:45:47 UTC,Is it still an issue with 20.04?
1801561,2021-01-16 04:17:34 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1801561,2018-11-08 22:27:39 UTC,I also verified that this issue exists on Ubuntu-MATE 18.04 and the latest Elementary OS (based on 18.04)
1801567,2019-10-01 23:14:09 UTC,I'm marking this as triaged but can you double check that --extrausers is still missing. I recall reading that it has landed somewhere. Please respond if this is no longer a problem.
1801573,2018-11-04 08:00:07 UTC,This change was made by a bot.
1801573,2018-11-05 03:31:49 UTC,Look like this is an issue of graphic driver (amdgpu).
1801574,2019-05-13 10:34:36 UTC,"Hi,
After trying the steps that mentioned in #4 on 18.10, the issue doesn't reproduces with the suggested setting."
1801574,2019-04-28 08:57:59 UTC,"Hi
Sure i will try it and update."
1801574,2019-04-18 15:11:43 UTC,"Hello - Talat, could you please try the workaround that I mentioned in comment #4? It should be all you need to get back to the old threshold values."
1801574,2019-03-21 20:26:18 UTC,Hello Talat - You said that this test passes on the 18.04 LTS kernel so it is worth nothing that the commit you identified is also present in that kernel. It was released in 4.15.0-32.34:
1801574,2019-03-24 08:02:41 UTC,"Hi Tyler,"
1801574,2019-03-21 19:53:47 UTC,"Hi Talat,"
1801574,2018-11-04 08:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801574,2019-04-18 13:37:17 UTC,"Hi Tyler, do you have any update for this bug?"
1801574,2019-03-21 19:56:03 UTC,Err... nevermind 4.4 anyway. just 5.0 would be interesting to see if this persisted into Disco.
1801576,2018-11-04 12:26:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1801576,2018-11-05 09:33:27 UTC,"I don't know what specific package, installed or missing, is responsible for the missing GUI in the laptop, so I can't specify this information. (Presumably, if I new which package was to blame, I wouldn't be having this issue for over a week now.)"
1801576,2018-11-17 02:15:55 UTC,Does anyone have any updates or insights regarding this issue? I can't really use my laptop.
1801578,2019-01-30 08:56:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801579,2020-03-07 15:52:08 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1801579,2020-03-07 18:22:56 UTC,Dear Paul
1801579,2020-03-07 18:32:38 UTC,Thanks for the feedback Douglas.
1801582,2019-09-16 17:33:52 UTC,Migrated to https://github.com/widelands/widelands/issues/2124
1801584,2018-11-07 17:03:46 UTC,"can you elaborate a bit more?
it's normal for openflow rules disappearing on a restart."
1801584,2018-11-08 03:00:54 UTC,"Thank you for your prompt reply,The problem is as follows:
1.create a tap-service on a desination port
2.create a tap-flow on the mirrored on port
3.After the actions above,I can see br-tap, br-int,and br-tun have added some extra openflow rules related to mirrored port traffic forwarding.
for example,if I create a tap-service on host1, the br-int on host1 should add openflow rules as follows:"
1801588,2018-11-04 13:46:47 UTC,Here's the related bug reported at Pyzo GitHub: https://github.com/pyzo/pyzo/issues/529
1801588,2018-11-04 14:01:07 UTC,"I've just found out that this bug is fixed on March 5th, 2018, ie. from version 4.6.0.
https://github.com/pyzo/pyzo/pull/530"
1801598,2019-11-01 05:59:29 UTC,"@jeroldh,
May I know what keyboard layout which you selected when you setting the passphrase ""eeee"" ?"
1801598,2019-10-29 15:03:13 UTC,"Sure, but please you should still fix it for the users of the XPS 13 9370..."
1801598,2019-10-24 02:11:18 UTC,@anomalroil @jeroldh Please kindly create a new bug for XPS 13 7390.
1801598,2019-10-23 19:14:19 UTC,I was having the same issue on the new XPS 13 7390.
1801598,2019-10-18 19:36:12 UTC,Admittedly it's not clear but 1.63 is actually intended for 19.10+ later.  Can you please do it with 1.62 from release page?
1801598,2019-01-22 20:23:59 UTC,It seems so
1801598,2019-02-21 20:14:59 UTC,This bug is also present in the currently shipping image on the XPS 13 9380. The workaround worked with v1.62 from the release page which I think includes the fix for the package removal.
1801598,2019-01-16 00:46:32 UTC,I believe that's bug https://bugs.launchpad.net/ubuntu/bionic/+source/ubiquity/+bug/1801629
1801598,2019-01-15 21:16:52 UTC,"Following packages shall be declared as non removable : cryptsetup, cryptsetup-bin and lvm2"
1801598,2018-12-19 21:37:09 UTC,"Another issue found is that the sudo apt-get autoremove command shall be definitively avoided.
The result of the command is making Ubuntu not able to reboot anymore."
1801598,2018-12-05 21:24:29 UTC,Here is a workaround successfully tested:
1801598,2018-11-13 21:01:50 UTC,"Dell has confirmed there is a bug in Dell Recovery application.
They will have to respin the XPS 13 9370 factory image in the future."
1801598,2019-10-18 13:46:19 UTC,"Notice this bug is also present in the currently shipping image on the XPS 13 7390.
The proposed workaround did not fully work with v1.63, as it then boots in OEM configuration mode (?) which has a script ""Prepare for shipping to end user"", but it does not load Dell's PPA and drivers as it should."
1801602,2018-11-09 01:52:30 UTC,"Sounds like equal blame on the application, window manager (mutter) and the user :)"
1801602,2018-11-12 15:13:48 UTC,"""when a custom display mode (960x540) is active"" has been added to description but (as I mentioned before) it's not true for the Steam Way To Go game."
1801602,2018-11-07 20:21:37 UTC,Here you are the xwininfo test result.
1801602,2018-11-06 02:26:40 UTC,Please:
1801602,2018-11-07 20:28:14 UTC,Further investigation shows that the abe game fails fullscreen only when I have additional xrandr mode added. It's set within session startup script with commands:
1801602,2018-11-04 20:19:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1801606,2021-02-04 12:00:35 UTC,"This issue is fixed in recent upstream sources 0.1.1 which is in the archive now:
https://launchpad.net/ubuntu/+source/lxhotkey/0.1.1-1"
1801609,2018-11-21 17:33:28 UTC,"Indeed. The log file does not list intel_drv.so, so maybe Xorg has to be explicitly configured to do so."
1801609,2018-11-26 18:02:58 UTC,"Tested positive on: Intel Core i3 3rd generation, Intel HD graphics
                    Also with Intel Core i7 8700k & Intel Core M-5Y31"
1801609,2018-12-23 23:19:07 UTC,"Enabling the intel driver by creating /etc/X11/xorg.conf containing
    Section ""Device""
        Identifier ""intel""
        Driver ""intel""
    EndSection
still results in a blank screen (no backlight), but it comes on when moving the pointer, like it did in Xubuntu 18.04."
1801609,2019-02-17 19:01:39 UTC,"@bbethge, your solution worked for me. After creating xorg.conf and enabling intel driver screen wakes up after lock and behaviour is right. Xubuntu 18.10, Intel(R) HD Graphics 620 (Kaby Lake GT2)."
1801609,2019-02-17 20:18:38 UTC,"More info here, as well:"
1801609,2019-05-22 14:11:40 UTC,I would refrain from messing with the video drivers just to workaround a bug in the screen locker. Solution #27 doesn't work for me either.
1801609,2018-11-21 16:33:13 UTC,Attached is the Xorg.0.log without the xserver-xorg-video-intel driver installed?
1801609,2019-07-22 04:23:54 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1801609,2019-08-14 00:48:27 UTC,"I'm running Xubuntu 18.0.03, which hasn't reached end-of-life, and this bug is still present. It was introduced when I upgraded to kernel 5.0 with xorg 1.20.4-1ubuntu3~18.04.1. It can be circumvented using either of 2 methods:"
1801609,2019-08-14 00:50:33 UTC,"Ops, apologies for the typo, I'm running Xubuntu 18.04.03"
1801609,2019-03-24 21:10:43 UTC,A simple workaround (that worked for me at least):
1801609,2018-11-21 16:32:04 UTC,The Bug is present whether or not xserver-xorg-video-intel driver is installed.
1801609,2018-11-05 14:51:41 UTC,Soooo looking forward to Sean's xfce4-screensaver @ https://github.com/xfce-mirror/xfce4-screensaver !!
1801609,2018-11-21 04:21:37 UTC,"With my Toshiba Satellite C650 (Core i3-2350M 2.3 GHz, onboard Intel HD Graphics 3000):"
1801609,2018-11-21 12:14:12 UTC,The cause of this issue has to be in Xorg 1.20 then (18.04 comes with 1.19).
1801609,2018-11-06 13:03:43 UTC,"Does terminating light-locker and running ""dm-tool lock"" trigger the bug?"
1801609,2018-11-06 14:48:18 UTC,"Hi Theo, thanks for the follow-up. In answer to your question:"
1801609,2018-11-06 14:52:24 UTC,"Also, upon reflection, it would seem that the actual issue is _not_ a failure to switch to VT8, as I can blindly enter passwd and return to session. It would seem that the video driver is simply not coming out of +dpms mode. I will update the title to better reflect that."
1801609,2018-11-06 17:47:14 UTC,Are there any hints in the system or lightdm logs?
1801609,2018-11-05 14:45:07 UTC,Confirming that this problem exists on two different systems. Both systems(desktop and laptop) are using an Intel video card year 2009 or newer.
1801609,2018-11-07 15:44:24 UTC,"lightdm & syslog(relevant sections only), attached. I saw nothing
suspicious, although the lightdm.log seemed to have the most relevant
entries."
1801609,2018-11-07 15:19:56 UTC,"lightdm & syslog(relevant sections only), attached. I saw nothing suspicious, although the lightdm.log seemed to have the most relevant entries."
1801609,2018-11-19 19:58:24 UTC,"Confirming this problem exists with my Toshiba Satellite C650 (Core i3-2350M 2.3 GHz, onboard Intel HD Graphics 3000), with a fresh Xubuntu 18.10 Installation."
1801609,2018-11-20 18:01:22 UTC,Few more things:
1801609,2018-11-09 16:34:23 UTC,@Theo:  Thanks for your help.
1801609,2018-11-09 16:02:10 UTC,I did not spot anything relevant in your log files either.
1801620,2018-11-05 06:55:01 UTC,Thanks for your bug report.
1801620,2018-11-05 14:51:47 UTC,"Good google search and I spot a link:
https://developer.mozilla.org/en-US/docs/Archive/Mozilla/Persona/The_implementor_s_guide/Problems_integrating_with_CRSF_protection#The_problem_with_Persona"
1801620,2018-11-05 15:09:13 UTC,"Thanks for the link, which describes the problem very well :)"
1801620,2019-09-06 08:04:10 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/188
1801626,2020-06-30 03:24:30 UTC,"$ systemctl cat secureboot-db.service  | grep Condition
ConditionPathExists=/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f"
1801630,2020-08-10 01:50:50 UTC,gmic (2.4.1)
1801631,2019-04-23 05:56:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801632,2018-11-05 01:31:22 UTC,"t_doc_generator::sandesh_level::type t_doc_generator::get_sandesh_level(
    t_sandesh* tsandesh) {
    string content = get_doc_member(tsandesh, ""severity"");
    if (content != """")
 return string_to_sandesh_level(content);
    return sandesh_level::INVALID;
}"
1801642,2019-08-09 07:54:04 UTC,"/sys is huge, with many directories and files.
Can't find here bluetooth related config."
1801642,2019-08-09 08:25:28 UTC,Does kernel parameter `btusb.enable_autosuspend=0` help?
1801642,2021-01-18 05:40:52 UTC,To change parameters you need to:
1801642,2019-08-09 09:54:59 UTC,btusb.enable_autosuspend=0 is a magic! Yay!!!
1801642,2021-01-13 13:48:34 UTC,"Hello,"
1801642,2019-08-09 07:34:51 UTC,Such settings are in the /sys filesystem as text files you can read and write to. Writing to them is not remembered across boots though -- that's what software like powertop or tlp does.
1801642,2019-08-09 08:45:59 UTC,"Additional info:
sudo service bluetooth status:
.
.
.
Aug 09 11:05:47 boaz-desktop systemd[1]: Started Bluetooth service.
Aug 09 11:05:47 boaz-desktop bluetoothd[944]: Starting SDP server
Aug 09 11:05:47 boaz-desktop bluetoothd[944]: Bluetooth management interface 1.14 initia
Aug 09 11:05:51 boaz-desktop bluetoothd[944]: Endpoint registered: sender=:1.110 path=/M
Aug 09 11:05:51 boaz-desktop bluetoothd[944]: Endpoint registered: sender=:1.110 path=/M
Aug 09 11:06:20 boaz-desktop bluetoothd[944]: No cache for FF:FF:7D:BE:34:6F
Aug 09 11:06:22 boaz-desktop bluetoothd[944]: bt_uhid_send: Invalid argument (22)"
1801642,2019-08-09 07:17:51 UTC,"Exactly. But I can't figure our where this setting, for a permanent change..."
1801642,2018-11-09 01:57:33 UTC,First ensure you don't have 'tlp' installed.
1801642,2019-08-09 06:49:29 UTC,"After enabling the HWE stack on my Kubuntu 18.04.3 64bit and upgrade to Kernel 5.0, the bluetooth mouse sleeps after some inactivity.
An upgrade to Kubuntu 19.04, Kernel 5.0.0-23-generic, didn't solve the issue."
1801642,2018-11-09 02:00:06 UTC,This change was made by a bot.
1801642,2018-11-08 23:59:21 UTC,"Day 5: Issue comes back again (after suspend). Those two unknown devices switched back to ""Good"". This time I toggled one of them to ""Bad"" and the issue is resolved."
1801642,2018-11-06 07:02:45 UTC,"I see. There are two ""Good"" unknown autosuspend USB devices, not sure which one is my mouse. I can't find it in ""Bad"" either."
1801642,2018-11-06 02:32:08 UTC,I think you're looking at the wrong line there. The line you want is:
1801642,2018-11-06 00:18:46 UTC,"Ok, after another waking from suspend, the issue comes back again."
1801642,2018-11-05 06:57:52 UTC,"My apology, I found the issue is due to canonical-livepatch (which is LTS-only). Issue resolved after removing it."
1801642,2018-11-05 03:49:01 UTC,1. If you have 'tlp' installed then please try removing that.
1801642,2019-08-09 07:06:28 UTC,"""Good"" in PowerTop usually means it is set to sleep. It sounds like the setting you want is actually the one labelled ""Bad""."
1801642,2018-11-08 00:16:26 UTC,"Day 3: No issue after wake from suspend.
Day 4: Issue comes back again (after suspend). Resolved after toggling ""Autosuspend on"" for two unknown USB devices to ""Bad""."
1801648,2018-11-05 05:46:49 UTC,add precondition : use gnome (3.18.2)
1801648,2019-04-18 15:54:36 UTC,Thank you for your bug report. Could you add your journalctl log after getting the issue? Is there any chance you could also try newer Ubuntu series?
1801648,2019-06-18 04:17:34 UTC,[Expired for file-roller (Ubuntu) because there has been no activity for 60 days.]
1801651,2018-11-05 07:22:29 UTC,"Reviewed:  https://review.opencontrail.org/47464
Committed: http://github.com/Juniper/contrail-vcenter-plugin/commit/e2f361311b49d3cb5f3e36c7263254cc10da5a55
Submitter: Vinay Vithal Mahuli (<email address hidden>)
Branch:    R4.1"
1801651,2018-11-05 07:11:15 UTC,"Reviewed:  https://review.opencontrail.org/47465
Committed: http://github.com/Juniper/contrail-java-api/commit/3ad68d753e156dd9b16fef41826c60f15eac6a2f
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1801651,2018-11-05 06:08:53 UTC,"Review in progress for https://review.opencontrail.org/47464
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1801651,2018-11-05 06:11:04 UTC,"Review in progress for https://review.opencontrail.org/47465
Submitter: Sachchidanand Vaidya (<email address hidden>)"
1801655,2019-04-23 06:33:08 UTC,"I have add yours as a duspliacted one, so this this 1801655 heat rise up!"
1801655,2019-03-09 16:53:23 UTC,"I spent more time on this, and I finally fill a bug @GTK project.
https://gitlab.gnome.org/GNOME/gtk/issues/1733"
1801655,2019-03-02 11:41:31 UTC,"Well in fact things are a litlle bit complicated that users might expect.
Like said into this bug:  #1777250 Change of workflow in Import dialog
HomeBanks use a standard pre-coded GtkAssistant, as so have not full control about what is displayed."
1801655,2019-04-23 03:57:58 UTC,I'll note that I brought up a similar issue with the new file creation dialog bug #1663790
1801655,2018-11-11 12:19:22 UTC,2nd step
1801655,2018-11-11 12:18:59 UTC,1st step
1801655,2018-11-10 18:47:16 UTC,Microsoft Windows [Version 10.0.17134.345]
1801655,2018-11-10 07:50:57 UTC,what is your OS ?
1801655,2018-11-11 12:19:35 UTC,3rd step
1801664,2019-04-20 23:37:19 UTC,"If booted with systemd.unified_cgroup_hierarchy=1, all snaps apps break"
1801664,2019-09-30 11:31:07 UTC,This has been under development for some time and initial version should be (or is already) available for Fedora 31 release day. Ongoing work will extend that to bring more feature parity over (specifically: device cgroup replacement)
1801667,2018-11-06 05:57:03 UTC,Changing the component for this bug.
1801667,2019-01-22 15:24:37 UTC,I'm waiting for this feature.
1801681,2019-03-08 20:06:02 UTC,This issue was fixed in the openstack/python-mistralclient 3.8.0 release.
1801688,2018-11-05 13:00:04 UTC,This change was made by a bot.
1801688,2018-11-05 12:22:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware.  I recommend performing a back up and then investigating the situation.  Measures you might take include checking cable connections and using software tools to investigate the health of your hardware.  In the event that is is not in fact an error with your hardware please set the bug's status back to New.  Thanks and good luck!
1801688,2018-11-05 09:30:08 UTC,This change was made by a bot.
1801688,2018-11-05 12:56:29 UTC,i could not find any hardware problems
1801694,2018-11-05 12:05:31 UTC,"- confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1801694,2018-11-05 14:02:20 UTC,"This is a feature I find handy. It functions properly on Win 8.1 64, Inkscape 0.92.2 (5c3e80d, 2017-08-06)."
1801694,2018-11-05 14:54:12 UTC,"Also not working here on Inkscape 0.92.2 (5c3e80d, 2017-08-06)"
1801694,2018-11-06 04:23:15 UTC,Appears to work when the user has navigated into the containing group (via 2Xclick or Objects menu).
1801694,2018-11-14 17:59:19 UTC,Relevant MR: https://gitlab.com/inkscape/inkscape/merge_requests/419 (needs some discussion on how to actually fix this issue)
1801694,2020-04-06 18:41:42 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1801699,2018-11-17 14:11:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801699,2018-11-17 14:12:38 UTC,Same problem also on Ubuntu 19-04
1801701,2018-11-05 14:22:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/615570"
1801701,2018-11-19 15:25:05 UTC,"Reviewed:  https://review.openstack.org/615570
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=030df4e31005e28b71f549dbb888f3040e0a4457
Submitter: Zuul
Branch:    master"
1801702,2018-12-19 10:01:25 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1801702,2018-12-19 10:04:48 UTC,This issue was fixed in the openstack/nova 16.1.7 release.
1801702,2018-12-13 12:59:55 UTC,"Reviewed:  https://review.openstack.org/619254
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ba844f2a7c1d4602017bb0fc600a30b150c28dbc
Submitter: Zuul
Branch:    stable/pike"
1801702,2019-01-18 17:30:19 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/631843"
1801702,2019-04-06 09:56:12 UTC,"Reviewed:  https://review.openstack.org/631843
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c77c3eb61ca7a0da64eed62dea084ee3df1d0722
Submitter: Zuul
Branch:    stable/ocata"
1801702,2018-12-19 20:48:10 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1801702,2018-12-07 05:20:26 UTC,"Reviewed:  https://review.openstack.org/619220
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f8eb8a7bc52448ede25cb8ac67fcb1818d3fdd2e
Submitter: Zuul
Branch:    stable/queens"
1801702,2019-03-22 03:46:06 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1801702,2018-11-21 22:39:47 UTC,"Reviewed:  https://review.openstack.org/616580
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=14d98ef1b48ca7b2ea468a8f1ec967b954955a63
Submitter: Zuul
Branch:    master"
1801702,2018-11-21 14:18:49 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/619254"
1801702,2018-11-21 14:03:20 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/619251"
1801702,2018-11-21 12:02:03 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/619220"
1801702,2018-11-08 15:12:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616580"
1801702,2018-11-08 14:51:00 UTC,We are affected by this on stable/pike and stable/queens now after we had to enable preallocate_images=space in order to avoid some out-of-space issues. Have been running on nvme for local storage with block size 4096 for some time for performance reasons.
1801702,2018-11-08 15:01:11 UTC,"Maybe the check should try 8192, 4096 and then 512 and failing all three consider it not supported."
1801702,2018-11-08 14:56:10 UTC,"Erm, I meant to write ""... any disks with block size 8192 ..."" of course."
1801702,2018-11-27 11:52:11 UTC,"Reviewed:  https://review.openstack.org/619251
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=386e574f4ae6ead225edd65f2759e9aa14c4887b
Submitter: Zuul
Branch:    stable/rocky"
1801704,2018-11-07 10:49:47 UTC,The same happened to me with Atril (Mate desktop) and Evince (Gnome desktop) in Debian testing last month. Stop opening cbr files but still opening cbz files. It's a problem with mime types.
1801706,2019-10-15 16:59:19 UTC,"Another possible way could be ""downlighting"" the not connected pads to a less visible color (making an average between the background color and the pad color), just to see them ""at a glance""."
1801711,2019-05-19 04:17:49 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1801711,2018-11-05 12:08:25 UTC,"2018-11-05 12:02:29Z [standalone]: CREATE_COMPLETE  Stack CREATE completed successfully
** Downloading standalone ansible.. **
Generating default ansible config file /home/stack/ansible.cfg
** Running ansible deploy tasks **
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path."
1801711,2019-02-19 13:09:54 UTC,Is this still an issue?
1801714,2020-06-26 13:49:03 UTC,As we discussed on the nova weekly meeting I'm OK with the idea to introduce a service up check in the rebuild code path.
1801714,2020-08-26 13:44:41 UTC,@Akhil: I saw your ping on IRC. I the rebuild code paths is the following
1801714,2020-09-02 14:57:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/749531"
1801714,2020-05-19 09:25:47 UTC,I can reproduce the reported behavior on recent master in a devstack. I also waited after the compute service stop until the nova controller detected that the compute is down. Still rebuild is accepted and the the instance is stuck in REBUILD state even after I started the compute service back up.
1801714,2020-06-18 10:17:55 UTC,"I was also able to reproduce this bug in the latest version. I would like to add my views on this bug since the nova controller can detect that the compute node is down maybe we can add a method to check the status of the compute nodes, that get invoked for all the requests made related to compute services."
1801717,2018-11-05 13:11:07 UTC,i guess it will be ok once https://review.openstack.org/#/c/597563/ is merged
1801720,2018-11-06 03:23:13 UTC,"Ack, I don't think a given tarball can be decompressed by more than one of
these, but for determinism I'm fine with ordering it."
1801722,2019-04-30 14:00:40 UTC,Just saw you went on for implemtning this in c++ now. I will try to get the Normal AI tricked to work on this map tonight. I'll report back my experiences. I still think with the playercommands the normal AI should be capable doing what you want.
1801722,2019-05-12 12:52:24 UTC,"Hi Nordfriese,
branch with my AI changes is now under review I would like your opinion on this changes whether they could help you so you could try to test fri03 in this branch (AI-fixes), if your time allows. We won't add fri03 with this branch I just added it there to evaluate my changes. Therefore I would wait for your feedback before merging this to give you the chance to test before deleting all the stuff."
1801722,2019-05-01 22:37:13 UTC,At least this nis good for finding bugs in the AI. found a new bug regarding the economy. with that cured I really get close to the Ai working for this scenario.
1801722,2019-05-01 14:40:46 UTC,"ok the coal should be manged by building charcoal kiln probably, but by this the AI gets slowed down."
1801722,2019-05-01 14:38:03 UTC,Ok I did some tests now running your scenario with the normal AI.
1801722,2019-04-30 14:35:53 UTC,"I wasn't talking about training. From All I saw what has been implemented in fri03 so far, I believe the normal Ai should be able to handle the scenario well if brought out of basic economy mode which I believe I can manage by scripting.
If I will be successful with this you could evaluate the result and decide what to use."
1801722,2019-04-30 14:30:46 UTC,"I´m now writing this as a standalone C++ AI designed to closely interact with scenarios by providing a scripting interface. This gives better performance (I hope) and much higher flexibility for other scenarios, as my Lua AI was designed specifically for this one scenario."
1801722,2018-11-20 20:30:05 UTC,"The main difference between the C++-AI´s roadbuilding logic and mine is the way candidates for new roads are found. I´m not sure what the c++ AI does, but I check for flags that are physically close to each other but far apart for routing purposes. Other than that, the algorithms are similar (I think)."
1801722,2019-09-16 13:52:45 UTC,Migrated to https://github.com/widelands/widelands/issues/2125
1801722,2018-11-20 17:52:56 UTC,"1) It´s *much* more triggerhappy than in b19, which I frequently discover to my disadvantage in normal games :D But even so, it´s a bit reluctant at times and prefers to wait until it is almost certain of victory (or really desperate). But my AI player can afford to take chances, as he cannot be defeated (thanks to a ""guardian angle"" script that saves it from too-good players ;) )
2) It´ll be a waste of resources if they get a whole mining infrastructure for no purpose. Worst of all, no mines can be built on the whole map, which will necessarily make the AI very unhappy…
3) The AI already does get some nice cheats – if I give it more, there´s little difference to scripting my own ;)
4) Yep, it should definitely handle that better. Current situation is that it builds no militarysites whatsoever…"
1801722,2018-11-20 15:47:20 UTC,"Thanks for the explanation.
Some quick thoughts:
1. aggressiveness - current AI is already much more ""triggerhappy"" than the old(b19) one. In my opinion your design goal is exactly what we should aim for the normal AI, as it is easier to relive this for easy AI.
2. What about giving your scenario players the necessary buildings (as described in your scenario basic economy tables) by player command at start up. (placing the constructionsites probably) and afterwards declare basic economy reached by lua command. After that the AI will build according the normal neededness. Not needed buildings could forbidden for this player.
3. cheating could be done by scripting at regular intervals.
4. Last point I don't really understand. But again we should aim for the normal AI handling this situation better."
1801722,2018-11-20 12:21:05 UTC,"I pushed a fix now that makes the AI much much faster. The game runs fluently (with only one out of two AIs enabled, and slowed down to 300x slower for testing purpose…), and the garbage collector isn´t needed that often anymore. Performance will not be an issue :)"
1801722,2018-11-20 11:53:35 UTC,"Uploaded a new revision to fix the LP bug.
In my first attempt of creating a basic luaAI, it started to consume 8GB of RAM within one minute… Now I run the garbage collector after every run of the main loop, which is slower but fixes that problem. The main slowdown now is caused only by the necessity to search the entire map for road optimizing, but I already have an idea how to fix this. This will make my AI very fragile regarding human or script interfering, but as it´s only for this scenario, so well. I guess my micro-AI won´t be much worse than a long game on a huge map when it´s ready.
The reason why the default-AI *shouldn´t* be trained to behave properly in fri03 is:
· It should be super-aggressive, reckless though not to the point of foolishness
· Lots of normally important buildings are obsolete, therefore basic economy and mining is impossible
· It´s in ""cheating mode"" by getting free wares and soldiers
· The permanent nearness of unguarded enemy borders confuses it
· …
I´ll do my best to keep the performance up (e.g. by inserting short sleep statements into long loops, that makes the AI a bit slower but the game much faster), then the normal AI won´t be needed here…"
1801722,2018-11-20 07:48:40 UTC,"by the way the playercommands branch is empty due to a Launchpad bug probably. Perhaps uploading a new revision could solve this, if you would be so kind."
1801722,2018-11-20 07:47:30 UTC,"Hi Nordfriese,"
1801722,2018-11-19 11:19:19 UTC,"Since I want to continue scripting fri03 soon, I´ll just start implementing what I need"
1801722,2018-11-06 19:07:54 UTC,"Forgot to mention:
· Start/Stop building
· Enhance building
And for the future:
· All actions that can be applied to an expedition ship (change direction, build port, etc)"
1801722,2018-11-06 05:03:01 UTC,Please make a list of the commands that you'd like to use so that we can start with those.
1801722,2018-11-20 19:28:46 UTC,"Ok first of all if it is fun for you I didn't want to take this away from you.
Anyhow it might be the case you got me wrong. I just wanted to show you a way to achieve your goals with the normal AI if this might have worked for you.
So for the aggressiveness I think we agree about current Ai state. My thought was it shouldn't be far from your expectation.
for the economy I clearly see your problem my solution for current AI would have been to avoid unnecessary / unbuildable buildings by forbiddinng them. Script all basic buildings for this scenario (the ones the Ai does really need to survive and build other buildings) and set the Ai manually to basic economy reached mode. In this mode the Ai should theoretically only build the allowed buildings based on economical / military needs (of course with the current limitations). So mising mines should be no problem with this setup.
necessary cheating for the AI player coud be easily controlled via script in this modus. which leaves the weird military behaviour at unguarded borders as a real problem, and it is definitly one of my most important goals for b21 to improve that."
1801722,2018-11-06 19:04:38 UTC,"The features I´m missing most are:
· Attacking an enemy militarysite
· Dismantling a building
· Changing InputQueue capacities and priorities
· Changing SoldierControl capacity
· Sending individual soldiers away
· Kicking out a worker from a building
· Militarysite prefers heroes/rookies
And might be nice in the future
· Sending a geologist to a flag"
1801723,2019-09-16 13:53:21 UTC,Migrated to https://github.com/widelands/widelands/issues/2126
1801727,2019-02-18 14:29:21 UTC,"This issue tripped up phoe when he was producing a portable test suite for package local nicknames.   Perhaps it should be a warning, not a style warning."
1801727,2020-12-14 00:11:10 UTC,"There is set of users who would be disaffected - those who compile in a build infrastructure that escalate all warnings to build breakages. Introducing a new warning for something as innocuous as a perfectly ordinary call to defpackage that is nowise unstylish would kind of be a problem for them.
(And don't get me wrong - it is problematic to introduce _any_ new style warning)"
1801730,2019-12-06 10:32:33 UTC,This was fixed in 3.6.1-8ubuntu3.2.
1801733,2020-04-23 18:39:50 UTC,"This is definitely nifty and impressive, but realistically will never be addressed. We recommend folks deploy with TLS on all internal services, including the message queue used for RPC. TLS makes this kind of in-flight RPC hacking even less of a concern in practice - because let's face it, if someone has gained enough access to modify in-flight RPC this way, setting VCPUs to a wrong value is the least of your concerns."
1801735,2019-03-29 12:54:05 UTC,The fix is now published and this bug can be closed (https://docs.ubuntu.com/core/en/guides/manage-devices).
1801735,2019-03-26 12:07:30 UTC,"I've created a PR for this:
https://github.com/canonical-docs/ubuntu-core-docs/pull/83"
1801743,2018-12-15 12:54:07 UTC,"Thanks for this, nadi!"
1801743,2018-12-08 18:40:18 UTC,"Hei Magnus,
What do you mean ""which is stable""? can you put the computer in Sleep mode (S3) and it recovers?
Does it wakes when you open the lid, or do you have to press the button then it wakes?
Thanks"
1801743,2018-12-08 20:26:55 UTC,"Hei Nadi,"
1801743,2018-12-09 08:58:22 UTC,"I tried to change the swap size to 8 GB (I have 16GB RAM), and confirmed that my swap is 8GB:"
1801743,2018-12-09 09:29:05 UTC,"OK, I think I progressed a bit:"
1801743,2018-12-08 17:17:20 UTC,"This bug affects me as well, on a Dell Latitude E7440 (is this a Dell problem?). In my case, the bug started to appear with kernel 4.15.0-36 (and has been present in all later updates), both on 16.04 with the latest HWE and now with 18.04. For the time being I am using kernel 4.15.0-34, which is stable."
1801743,2018-12-14 05:21:14 UTC,I updated the BIOS but it did not help....
1801743,2018-12-16 16:10:44 UTC,I think I just found a solution! I just saw the following bug report over at Redhat (https://bugzilla.redhat.com/show_bug.cgi?id=1597481) and this kernel.org report (https://bugzilla.kernel.org/show_bug.cgi?id=200455).
1801743,2020-06-24 09:55:50 UTC,"I have the same issue.
Unfortunately it's now Ubuntu 20.04 and kernel 5.4.0 and it still happens.
My laptop is Lenovo Thinkpad T440p.
First issue that was happening all the time was that the touchpad didn't work after waking from suspend. But it was better known issue with some fixes with the help of some scripts.
This is harder as it's now happening always but only sometimes and I haven't figured out robust steps to reproduce this issue. It just happens sporadically but when it happens only hard reset helps.
My laptop has also Intel CPU and nVidia graphics card so that's something that is common I suppose.
If anything else is needed I could provide more information."
1801743,2018-12-22 16:07:21 UTC,"Everyone affected by this bug, please try 4.15.0-43. This fixes the issue completely for me (without needing to blacklist mei)."
1801743,2019-01-30 12:53:14 UTC,I am having this issue now with kernel 4.15.0-44-generic in a Dell Latitude E7440. Ubuntu 18.04
1801743,2019-01-30 13:54:30 UTC,"Felipe,
can you try to cancel the lid option? you do it with
sudo sh -c ""echo LID0 disabled > /proc/acpi/wakeup""
than check it is '*disabled' in the LID0 entry, by running
cat  /proc/acpi/wakeup
and check the output."
1801743,2019-01-30 20:08:11 UTC,I'm having the same issues today after upgrading to 4.15.0.44-generic on a Dell Latitude 5289 Ubuntu 18.04.1
1801743,2019-01-30 20:37:39 UTC,"@MaskedDriver: Does blacklisting the mei_me module (Intel Management Engine) fix the issue? That fixed the problem some weeks ago, perhaps the bug has re-appeared. I have not upgraded to .44 yet..."
1801743,2019-04-05 06:01:28 UTC,"I have the same problem. Suspend works fine with any kernel version4.14.x, does not work with any version from 4.15.x. I have blacklisted the mei modules, it did not solve the problem. Following are my lsmod."
1801743,2018-12-06 16:05:58 UTC,"Hei,
I have the same problem as Carsten Gräser (graeser), and in fact a similar laptop (Dell Latitude 7390).
I tried all the possible kernels since 4.14 to 4.19, and suspend (sleep S3) does not work. Same symptoms: It suspends when I close the lid, but cannot resume. When I open the lid and press the power button, it flushes ones but the screen is black. No response, no mouse, all dead. The only solution is to press again on the power button which performs hard reset."
1801743,2018-12-22 10:53:00 UTC,"Hei Magnus,
Yes it solved my problem as well. Using kernel 4.19.11, I blacklisted mei_me as you pointed out, now I have no crash when resuming from sleep S3, finally!!
Thanks a lot,
God Jul! :-)"
1801743,2018-11-08 16:31:27 UTC,Last entry in /var/log/kern.log for the incomplete shutdown seems to be
1801743,2018-11-05 16:17:14 UTC,apport information
1801743,2018-11-07 08:27:27 UTC,The mainline kernel indeed seems to fix the issue: Not a single failed suspend/resume cycle since using 4.19.1.
1801743,2018-11-05 16:17:07 UTC,apport information
1801743,2018-11-05 16:17:09 UTC,apport information
1801743,2018-11-05 16:17:10 UTC,apport information
1801743,2018-11-08 16:19:41 UTC,"Unfortunately, not for me. We have a bunch of (theoretically) identical computers in a new classroom, and on one of them this issue is present. Similarly as described by Carsten Gräser (graeser): last entry in kern.log, running fan and no reaction to either keyboard or power button, last message on screen being"
1801743,2018-11-05 16:17:12 UTC,apport information
1801743,2018-11-05 16:17:17 UTC,apport information
1801743,2018-11-05 16:17:20 UTC,apport information
1801743,2018-11-05 16:17:21 UTC,apport information
1801743,2018-11-05 16:17:11 UTC,apport information
1801743,2018-11-05 16:17:23 UTC,apport information
1801743,2018-11-05 16:17:22 UTC,apport information
1801743,2018-11-05 17:02:33 UTC,"Yes the issue did not happen prior to the update to 18.04. But I don't know if there was a prior kernel in 18.04 where the issue did not occur, because it's not happening 100% of the time. Still a successful resume is rare."
1801743,2018-11-05 16:19:26 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1801743,2018-11-05 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801743,2018-11-05 16:17:29 UTC,apport information
1801743,2018-11-05 16:17:26 UTC,apport information
1801743,2018-11-05 16:17:25 UTC,apport information
1801743,2018-11-05 16:17:30 UTC,apport information
1801744,2018-12-12 10:25:28 UTC,"This is caused by insufficient disk space on /boot partition where kernels are stored, excerpts from the attachments:"
1801748,2019-11-01 21:21:19 UTC,"Since nothing is currently using the tox.ini in the repo, I've cleaned that up via the following commit.  Sorry for the duplicate work, I didn't know about this branch."
1801749,2018-12-03 22:56:42 UTC,Is this still an issue?
1801751,2019-08-09 12:15:50 UTC,"hi, the bug relies in the wireless-tools package, wicd & python-wicd are just wrappers around them"
1801751,2019-08-09 12:26:07 UTC,p.s. le sigh! :/
1801751,2019-12-01 06:19:43 UTC,"Dear Guido,"
1801752,2019-09-19 14:47:55 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1801755,2021-02-25 02:33:07 UTC,You also need to configure the following in /etc/ceilometer/ceilometer.conf and restart the ceilometer service
1801755,2018-12-18 13:48:01 UTC,"Hello, I didn't test the `cluster_id` metadata yet, but `server_group` works fine for me with rocky release."
1801755,2018-12-18 08:58:35 UTC,I've tried to use this command:
1801755,2018-12-19 03:50:08 UTC,"If want to used clusetr_id,
here was my step:"
1801755,2018-11-13 07:33:09 UTC,@Duc Truong: is there any information about that?
1801757,2020-10-18 19:46:58 UTC,I face this issue in Ubuntu 20.04.  Just found the Alt-F2-r combination and it does work.
1801757,2020-03-11 19:35:24 UTC,"If I restart gnome shell, most of the app indicators remain, but the Google Chrome and Hangouts appindicators disappear."
1801757,2020-03-11 19:20:21 UTC,"This should have been fixed by appindicator 32-1, let me know if this is not the case"
1801757,2020-02-26 08:29:48 UTC,"Hello,"
1801757,2019-05-21 14:34:04 UTC,"Not certain, but I don't think I've seen this since upgrading to 19.04. I imagine it's unlikely to get fixed in 18.04 if it's fixed in 19.04 and people can upgrade, but I guess maybe it should be since 18.04 is supposedly supported until 2023?"
1801757,2019-05-20 22:54:27 UTC,"Same here in Ubuntu 18.04.
Monitor manager and other gnome extensions are disappearing from the top panel. Alt-F2 r, like other said, helps to get them back. Extensions are still running though when the bug appears."
1801757,2019-03-08 13:29:41 UTC,"With the last update today: Dropbox, Radiotray-NG and gEncFS Manager indicators came back working in the top panel."
1801757,2019-03-04 21:24:58 UTC,@valeryan-24 that sounds like the same problem as the one I reported.
1801757,2019-03-03 22:28:15 UTC,"I don't know if it is the same bug, but I have a similar problem since approx. 1 week in Dingo : Dropbox, Radio-tray NG, gEncFS Manager indicators are no more visible in the top bar, programs are still running."
1801757,2019-03-01 17:01:15 UTC,"The log has some warnings, including
[AppIndicatorSupport-WARN] while calling AboutToShow: Gio.IOErrorEnum: Method “com.canonical.dbusmenu.AboutToShow” returned type “()”, but expected “(b)”"
1801757,2019-03-01 15:46:50 UTC,"As described above, the indicators disappear intermittently and come back when I type Alt-F2 r RET. It seems to happen when the screen locks automatically and then I come back later and unlock it, though I don't know if it happens _every_ time the screen locks. I've attached my journalctl output for today with unrelated, private information removed. I've returned to my computer at least twice today and found the indicators missing, the most recent time being for the session I'm sitting in front of right now, i.e., if you can see in the journalctl when my screen locks and unlocks, then this problem manifested in the most recent iteration of that."
1801757,2019-03-01 14:09:16 UTC,"@jik, can you attach your journalctl log after getting the issue? is that transient or always?"
1801757,2018-11-10 14:37:53 UTC,"It works well... There are several bugs filed for this beavior. Maybe indicator-application package should be marked as conflicting for something newer or so, so that it gets removed upon dist upgrade."
1801757,2019-03-01 13:54:55 UTC,N.B. This is now happening to me in ** 19.04 ** (Disco).
1801757,2018-11-06 02:40:31 UTC,Can you please take a screenshot or photo of before and after?
1801757,2018-11-06 03:17:03 UTC,"Before, it looks like the attached (though there is also a Shutter indicator, which disappears while I'm taking the screen capture)."
1801757,2018-11-06 03:28:25 UTC,Thanks.
1801757,2018-11-06 09:45:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801757,2018-11-09 12:55:41 UTC,Also happening in 18.10.
1801757,2018-11-10 08:25:00 UTC,"Maybe, I've found a solution:"
1801757,2019-03-01 13:55:15 UTC,I believe it went away when I upgraded to 18.10 and came back when I upgraded from there to Disco.
1801757,2018-11-13 19:38:12 UTC,Just discovered the typing Alt-F2 r RET brings the app indicators back.
1801757,2018-11-14 09:41:13 UTC,looks similar to bug #1714504
1801757,2018-11-14 12:00:52 UTC,Not the same issue.
1801757,2019-01-07 23:25:15 UTC,"I have been living with this issue for some time now, finally annoyed me enough to Google and found this bug (thanks for reporting :)). Alt-f2 r also fixes for me which is a new workaround that I'm very grateful for. In my case it seems to be related to extensions which manipulate the top bar (e.g. todo.txt / system monitor). If I disable all extensions, and reboot the box, its fine. If I enable one of the extensions after rebooting and logging, it looks fine but after reboot, no application icons will be there. Previously I had just assumed they were broken extensions but seems to happen with quite a few of them and i have seen with many different combinations of extensions."
1801757,2018-11-11 00:04:20 UTC,1) I don't have /etc/xdg/autostart/indicator-application.desktop.
1801757,2019-01-31 13:03:43 UTC,I have the same issue. Alt-f2 r helps.
1801761,2018-11-05 17:15:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/615610"
1801761,2018-11-05 17:30:12 UTC,"For posterity, here's the gist of our IRC discussion about this:"
1801761,2018-11-05 17:53:09 UTC,"Email to the ops, sigs and dev lists:"
1801761,2018-11-05 19:30:44 UTC,"Reviewed:  https://review.openstack.org/615610
Committed: https://git.openstack.org/cgit/openstack/oslo.upgradecheck/commit/?id=c4283dd0ebbb2e64947b966e51b7f3f47233b7be
Submitter: Zuul
Branch:    master"
1801761,2018-11-05 21:50:18 UTC,This issue was fixed in the openstack/oslo.upgradecheck 0.1.1 release.
1801761,2018-12-20 15:36:57 UTC,I just noticed that we (Sahara) use it. Is there a suggested path for migrating out of it?
1801761,2018-12-20 16:24:17 UTC,You can stop using it today by just removing the enable_lazy call(s) from your code. That will cause oslo.i18n to use the regular translation code internally instead of the lazy framework.
1801762,2018-11-06 17:46:30 UTC,Julian - I hadn't realised there are two gpgv's!
1801762,2018-11-05 21:41:08 UTC,"I've created a shell wrapper than might be useful for this called ""gpgpv-multisig"" which is a multi-call executable. Given /usr/bin/gpgv-multisig"
1801762,2018-11-06 07:59:20 UTC,That wrapper is conceptually wrong. It should be using --status-fd.
1801781,2020-01-27 18:30:43 UTC,"Oh, and it seems that NTP settings in the kickstart configuration also do not propagate into the VM config. AFAIK, this stanza should configure the NTP server:"
1801781,2020-01-25 14:08:18 UTC,"Adding some information from my testing today with 18.04.3 server in a KVM-based VM. In my kickstart file, I have the following line:"
1801781,2020-04-18 02:51:25 UTC,"James, is there anyway we can get Kickstart updated to include automatic configuration of the DNS servers? I believe this is the only holdup I have from being able to leverage Kickstart to it's fullest since my network uses private DNS servers. Thanks and appreciate the follow-up in all of this!"
1801781,2019-09-10 22:20:18 UTC,"Hi Martin, the main functionality of Kickstart may work with Ubuntu 18.04, but the networking portion of Kickstart does not work at all and needs to be updated for SystemV. Please see my above bug description."
1801781,2019-09-10 13:39:45 UTC,Kickstart works with the non-GUI 18.04 installer (ubuntu-18.04.3-server-amd64.iso)
1801781,2018-12-30 15:46:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801781,2019-09-10 22:20:47 UTC,"Correction: SystemD, not Init-V"
1801781,2018-11-30 17:30:02 UTC,Please note: Preseeding is not an option for unattended network installations because network configuration only works for CD-ROM and USB. (Source: https://help.ubuntu.com/lts/installation-guide/arm64/apbs04.html#preseed-network)
1801790,2018-11-05 21:15:04 UTC,Quick fix on https://git.launchpad.net/cloud-init/tree/cloudinit/config/cc_disk_setup.py#n952
1801790,2019-07-18 23:03:06 UTC,"Hi,"
1801790,2019-09-17 04:17:43 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1801796,2018-11-07 15:57:54 UTC,That's known upstream and reported as https://gitlab.freedesktop.org/bolt/bolt/issues/92
1801796,2019-11-13 15:45:07 UTC,"I actually think that this might have been fixed. I suspect the main reason that bolt was started in the first place was fwupd (the firmware update daemon) starting it to force power the thunderbolt controller. It does so even if there is no controller to force power in the first place.
A small fix (https://github.com/fwupd/fwupd/commit/7e5c7b269a3b9182db58a201c24835177107ad41) to the fwupd daemon should prevent it from poking bolt if there is no hope of boltd succeeding in force powering the daemon. Thus on a system without any thunderbolt controller boltd should not be started anymore."
1801796,2019-11-14 19:30:22 UTC,That fix for fwupd to not use boltd on such systems is landed in fwupd 1.3.3 which is currently in focal-proposed.
1801796,2019-11-21 20:07:20 UTC,"1.3.3-3 promoted to focal release pocket today fixes this, marking fix released."
1801804,2018-11-08 23:14:33 UTC,I've the feeling this is also related to lp:1774587
1801805,2020-12-17 18:18:52 UTC,Does this issue still affect cups-pdf 3.0.1 packages?
1801805,2020-12-17 19:16:32 UTC,"Hallo,"
1801805,2021-02-14 09:56:17 UTC,Thanks. Let's close it then.
1801807,2018-11-05 23:02:52 UTC,"If I add a dll from http://download.qt.io/development_releases/prebuilt/llvmpipe/windows/
the non GL Waveforms and spinnies are back and moving. GL Waveforms are still empty."
1801809,2018-11-18 22:57:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801810,2018-11-06 05:47:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801814,2018-11-06 02:13:52 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1801814,2020-09-22 19:46:31 UTC,"Not sure why this bug has been marked as ""no longer affects Ubuntu Bionic"", it was only fixed in Focal and Groovy, I believe Bionic could still have the bug."
1801814,2020-08-12 06:01:04 UTC,This bug was fixed in the package flatpak - 1.6.5-0ubuntu0.1
1801814,2020-08-12 06:00:31 UTC,"The verification of the Stable Release Update for flatpak has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1801814,2020-08-05 21:24:09 UTC,"Awesome, thanks !"
1801814,2020-08-05 02:39:21 UTC,"Hello Sebastian, or anyone else affected,"
1801814,2020-07-07 20:30:03 UTC,@smcv Thanks for the info ! I'm going to look at backporting that change into 20.04 with the 1.6.5 SRU I'm currently doing.
1801814,2020-04-07 07:11:41 UTC,this is still happening on ubuntu 20.04
1801814,2019-10-04 19:13:53 UTC,"Confirming this bug. More distressingly, after removing flatpak from my system with apt, this change persisted; it left /etc/profile.d/flatpak.sh on my system which would automatically run on my main user, since it still had some leftover files in .local/share/flatpak, and would crash the desktop session upon logging in when it couldn't find relevant dependency."
1801814,2018-11-08 23:59:09 UTC,"Thanks for investigating further, yes [0] seems to be the issue upstream. I'll keep an eye on the pull request/issue and hopefully it will land into a release that can be SRU'd :-)"
1801814,2018-11-08 17:57:45 UTC,Should've mentioned that this happens when using GNOME session under Wayland.
1801814,2018-11-06 02:24:38 UTC,"I also wonder if /etc/profile.d/ are having an affect, as in there I have flatpak.sh and xdg_dirs_desktop_session.sh. [4] mentions how the order of loading these was incorrect at one point in time for Debian and GNOME systems (but this was for PATH which is more of a special case). Also I'm not super familiar with the sequence of how these are loaded, so might be wrong :-)"
1801814,2020-07-07 06:57:23 UTC,I've just run into this on 20.04 also. Installing flatpak broke all the snaps in my Wayland session because of the way flatpak overwrites the XDG_DATA_DIRS envar. It doesn't break snaps in xorg sessions.
1801814,2020-07-07 13:18:19 UTC,"This is believed to be fixed by version 1.8.1-1, which converts the gdm env.d fragment into an example file (moving it from usr/share/gdm/env.d to usr/share/doc/flatpak/examples/etc/gdm3/env.d). If Ubuntu developers want to backport that change to 20.04, please see commit b634ea2a in the Debian packaging."
1801825,2019-11-13 10:23:52 UTC,Do you have a list of projects some have this issue?
1801825,2020-07-27 15:28:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/743259"
1801830,2018-11-12 02:18:18 UTC,"Change abandoned by 98k (18552437190@163.com) on branch: master
Review: https://review.openstack.org/609126"
1801832,2018-11-08 16:11:10 UTC,What desktop environment/session are you using?
1801832,2018-11-08 16:30:29 UTC,Ubuntu 18.04 LTS
1801832,2018-11-14 02:33:38 UTC,IBus 1.5.17
1801832,2018-11-07 15:08:57 UTC,Thank you for your bug report. What key did you configure to switch input method in the control-center region settings?
1801832,2018-11-08 12:23:49 UTC,ctrl-space
1801839,2019-04-13 21:44:38 UTC,"I'm not sure that we can call this confirmed at least in how it's defined (""verified by someone other than the reporter""). What we need are clear steps to reproduce that. Without that, it's unclear how to fix it. It could, for example, be a hardware issue of some kind."
1801839,2019-06-13 04:17:22 UTC,[Expired for xscreensaver (Ubuntu) because there has been no activity for 60 days.]
1801839,2019-01-21 04:17:39 UTC,[Expired for xscreensaver (Ubuntu) because there has been no activity for 60 days.]
1801839,2018-11-21 15:50:06 UTC,"Original install was Ubuntu (3-4 years ago?), along the way I installed the XFCE meta package (forget if it was the xubuntu meta or what), and switched the DE to XFCE, but the core is base Ubuntu. That's why I use that nomenclature."
1801839,2018-11-21 05:53:51 UTC,"You're saying Ubuntu but you're using the XFCE desktop? Are you actually using Xubuntu? In any case, we'd need to have some understanding on how you have things set up so we can figure out what's controlling power management."
1801839,2019-01-21 13:43:46 UTC,"Um, this issue still persists..."
1801877,2018-11-22 10:29:35 UTC,Targeting linux-tools-common Precise package as it's where the perf tool came from.
1801877,2018-11-22 10:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801878,2019-05-16 11:32:43 UTC,"Patch 9e143793 has landed in D/E as well, mark this bug as fix-released."
1801878,2018-12-03 14:59:47 UTC,This bug was fixed in the package linux - 4.4.0-140.166
1801878,2018-12-03 14:01:15 UTC,This bug was fixed in the package linux - 4.15.0-42.45
1801878,2018-11-16 16:36:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1801878,2018-11-15 11:34:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1801878,2018-11-15 11:04:27 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1801878,2018-11-06 08:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801878,2018-12-03 08:49:32 UTC,This bug was fixed in the package linux - 4.18.0-12.13
1801879,2018-11-06 10:00:34 UTC,fixed in https://github.com/Juniper/contrail-charms/commit/1a15136c029d5e52d5966ad785cf88497ad505f3
1801884,2018-11-06 09:19:37 UTC,"Review in progress for https://review.opencontrail.org/47495
Submitter: Jan Gutter (<email address hidden>)"
1801897,2019-04-29 19:05:22 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656382"
1801897,2019-05-01 14:12:53 UTC,"Reviewed:  https://review.opendev.org/656510
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fa275544c27a5b428ad34b4c03be511607d15bf6
Submitter: Zuul
Branch:    stable/rocky"
1801897,2019-04-30 13:17:18 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/656510"
1801897,2019-04-29 04:52:08 UTC,"Reviewed:  https://review.opendev.org/636947
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=74cefe4266a613d4c2afbb0c791e16eb7789aef4
Submitter: Zuul
Branch:    master"
1801897,2019-04-30 11:26:57 UTC,"Reviewed:  https://review.opendev.org/656382
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c280d747fb23f1abaaf91eea7f6d11e716c6db42
Submitter: Zuul
Branch:    stable/stein"
1801897,2019-04-23 21:44:51 UTC,Looks like this could go back to pike:
1801897,2018-11-06 18:48:13 UTC,"Hmm, we do do a scatter/gather here when listing services:"
1801897,2019-02-14 13:05:14 UTC,"3) assumption is wrong, services are not fetched by one."
1801897,2019-02-14 12:48:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/636947"
1801897,2019-02-13 12:31:50 UTC,"There is a room for improvement:
1) service list is fetched twice
   https://github.com/openstack/nova/blob/master/nova/availability_zones.py#L127-L128
   https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/availability_zone.py#L63-L64
2) it's better to use set in
   https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/availability_zone.py#L74-L75
3) most important, from tcpdump I see services are fetched by one from
   some place, see (http://paste.openstack.org/show/745011/)"
1801897,2019-04-23 21:45:55 UTC,Note that the scatter/gather routine when fetching services from the HostAPI was already backported to pike:
1801901,2018-11-06 19:58:13 UTC,"Removing packages from disco:
 libextutils-parsexs-perl 3.350000-1 in disco
  libextutils-parsexs-perl 3.350000-1 in disco amd64
  libextutils-parsexs-perl 3.350000-1 in disco arm64
  libextutils-parsexs-perl 3.350000-1 in disco armhf
  libextutils-parsexs-perl 3.350000-1 in disco i386
  libextutils-parsexs-perl 3.350000-1 in disco ppc64el
  libextutils-parsexs-perl 3.350000-1 in disco s390x
Comment: Package version is obsolete with perl 5.28; LP: #1801901, Debian bug #912682
1 package successfully removed."
1801910,2018-11-26 06:44:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801910,2019-01-14 09:15:19 UTC,I have met same case with you also I'm using proxmox. Should like the image of Proxmox provided for us diffent a bit with normal OS. My laptop using Ubuntu 18.04 but no problem with the rsyslog. It still is version rsyslogd 8.32.0.
1801910,2019-01-14 12:01:20 UTC,"Il 14/01/2019 10:15, Phan Van Cuong ha scritto:

> I have met same case with you also I'm using proxmox. Should like the
> image of Proxmox provided for us diffent a bit with normal OS. My laptop
> using Ubuntu 18.04 but no problem with the rsyslog. It still is version
> rsyslogd 8.32.0.
>
> Rsyslog is included in all major distributions. So you do not
> necessarily need to take care of where packages can be found - they are
> “just there”. Unfortunately, the distros provide often rather old
> versions. This is especially the case for so-called enterprise
> distributions.
>
> So to fix this, I have still newest version of rsyslog then the issue
> has solved.
>
> sudo apt-get install -y software-properties-common # Provide add-apt-repository
> sudo add-apt-repository ppa:adiscon/v8-stable
> sudo apt-get update
> sudo apt-get install rsyslog
>
> Let's run again:
> # /etc/cron.daily/logrotate
"
1801910,2019-01-15 03:48:43 UTC,"Hi Marco,"
1801910,2019-01-22 22:54:02 UTC,"Il 15/01/2019 04:48, Phan Van Cuong ha scritto:

> Hi Marco,
>
> In my opinion, I think we should install rsyslog above on the container.
> You could create a new image for ubuntu 18.04 for never do it again.
>
> Like what I said, could be it happened on the image of Proxmox, so you
> should install the newest package of rsyslog on the container.
>
> By default, Ubuntu 18.04 rsyslogd version is rsyslogd 8.32.0.
>
> This is a result after upgrade:
>
> $ rsyslogd -version
> rsyslogd 8.40.0, compiled with:
> 	PLATFORM:				x86_64-pc-linux-gnu
> 	PLATFORM (lsb_release -d):
> 	FEATURE_REGEXP:				Yes
> 	GSSAPI Kerberos 5 support:		No
> 	FEATURE_DEBUG (debug build, slow code):	No
> 	32bit Atomic operations supported:	Yes
> 	64bit Atomic operations supported:	Yes
> 	memory allocator:			system default
> 	Runtime Instrumentation (slow code):	No
> 	uuid support:				Yes
> 	systemd support:			Yes
> 	Number of Bits in RainerScript integers: 64
>
> Seehttps://www.rsyslog.com  for more information.
"
1801911,2018-11-12 12:23:32 UTC,"The attachment ""99-kile3-filechange-refresh.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1801911,2018-11-06 11:01:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801911,2018-11-12 10:16:44 UTC,"As you can see here, the patch is relatively simple and it should be relatively safe to apply it."
1801919,2020-01-22 08:35:40 UTC,"Reviewed:  https://review.opendev.org/703234
Committed: https://git.openstack.org/cgit/openstack/os-ken/commit/?id=1f751b2d7d385a75d4255934694177d6fd6f012f
Submitter: Zuul
Branch:    master"
1801919,2020-01-18 12:18:56 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/703234"
1801919,2019-03-12 22:22:10 UTC,"Reviewed:  https://review.openstack.org/617354
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=56946cfc5f88d8df3b4b9a1a2530ce2cc9a68cde
Submitter: Zuul
Branch:    master"
1801919,2019-02-27 03:03:57 UTC,This issue was fixed in the openstack/os-vif 1.15.0 release.
1801919,2019-02-25 18:34:55 UTC,"its not released yet but ill be releaseing os-vif today.
it looks like teh rule for setting fix released are wrong.
it sould only be set when we release that commit in a tagged release on pypi/
tarballs.openstack.org."
1801919,2019-02-25 13:41:41 UTC,"Reviewed:  https://review.openstack.org/636822
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=1f6fed6a69e9fd386e421f3cacae97c11cdd7c75
Submitter: Zuul
Branch:    master"
1801919,2019-02-25 13:03:02 UTC,"Reviewed:  https://review.openstack.org/636821
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=5027ce833c6fccaa80b5ddc8544d262c0bf99dbd
Submitter: Zuul
Branch:    master"
1801919,2019-02-14 04:08:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636822"
1801919,2019-02-14 04:07:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636821"
1801919,2019-02-11 17:20:00 UTC,quick update.
1801919,2018-12-06 11:29:05 UTC,"Reviewed:  https://review.openstack.org/616995
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e92ecd3a428f7ac6ab2ecf613f796e22fa3f6199
Submitter: Zuul
Branch:    master"
1801919,2019-02-06 22:50:30 UTC,os-vif uses brctl in both its linuxbridge plugin and in the ovs plugin when hybrid_plug=true e.g. when the ip tables security group driver is used.
1801919,2019-02-07 14:58:03 UTC,Feb 28 is the non-client library freeze for the Stein release so yeah you're going to need to work on this pretty fast if you want to get it in and also have some buffer time for any regressions to get fixed.
1801919,2018-11-06 14:39:28 UTC,"We should just skip right over using 'ip' and use pyroute2 so this can all be done in privsep, it seems to have the support for it."
1801919,2018-11-07 07:29:12 UTC,"Adding nova, nova also using brctl for example in the NeutronLinuxBridgeInterfaceDriver ,"
1801919,2018-11-09 16:36:32 UTC,I don't see where NeutronLinuxBridgeInterfaceDriver is used in nova anymore...
1801919,2018-11-09 16:49:51 UTC,"LinuxBridgeInterfaceDriver is still using brctl but that's only used for nova-network which is itself deprecated, so I don't think we probably need to worry about removing that specifically since all of that code will be dropped when we drop nova-network, which should hopefully be in the Train release."
1801919,2018-11-13 02:08:07 UTC,Seeing the Fedora 28 and other releases don't seem to be supporting this I've bumped the priority so we get to this sooner.
1801919,2018-11-12 16:23:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617354"
1801919,2018-11-13 21:00:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617836"
1801919,2018-11-21 23:26:44 UTC,"Reviewed:  https://review.openstack.org/617836
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2572c158f5290ddc3bc2e4f06ecbd4768c82eee4
Submitter: Zuul
Branch:    master"
1801919,2018-11-09 16:54:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/616995"
1801919,2018-12-21 16:20:52 UTC,This issue was fixed in the openstack/neutron 14.0.0.0b1 development milestone.
1801921,2018-11-08 15:24:06 UTC,This occurs when the configuration contains invalid data.
1801933,2018-12-05 11:20:38 UTC,"IMHO, if achieving ease of use comparable to VirtualBox is your benchmark target, then launching QEMU directly is really the wrong way to approach things. QEMU is a very low level piece of infrastructure not a complete end user desktop solution. For that it is better to look at using an application such as virt-manager, or GNOME Boxes. These provide higher level solution over QEMU and do smart things during installation, using libosinfo to automatically determine the best memory, disk, network, etc settings for each particular guest OS rather than relying on some hardcoded defaults."
1801933,2018-12-05 13:03:44 UTC,"Hi Daniel,"
1801945,2018-11-06 14:42:10 UTC,"Demoting packages to disco-proposed:
 breezy-debian 2.8.13 in disco
Comment: LP: #1801945: remove breezy and demote its rdep breezy-debian
1 package successfully demoted."
1801945,2020-02-08 15:52:14 UTC,"Hi Matthias, Can this be marked fixed?"
1801946,2019-06-22 21:15:26 UTC,I run into this problem with locked tracks because of DRC violations quite frequently. This is one of the few situations where I have to switch to legacy canvas to escape from the locked situation. I am not sure how this would be solved when the legacy canvas is gone.
1801947,2020-08-18 20:31:16 UTC,"Thank you for adding that adjustment, Jane!"
1801947,2020-08-17 21:50:10 UTC,"Good catch, Jane!"
1801947,2020-08-17 21:00:17 UTC,"Thanks, Mike and Terran!  This is a good improvement.  I added it to master, rel_3_5, and rel_3_4."
1801947,2020-06-19 20:02:53 UTC,I pushed a branch with this change:
1801947,2020-08-17 19:39:56 UTC,"The functionality works well - I can use keyboard controls to tab to it and turn it off and on. The styling looks like a button (see attached) so could be improved, but I'm happy to sign off due to the accessibility improvement:"
1801947,2019-02-07 00:06:01 UTC,"Good catch, Galen.  Just a note for anybody who works on this: I am +1 to changing the styling a bit so that the look of the eg-help-popover remains consistent.  However, when the eg-help-popover receives focus, it should still have some type of border to indicate that it has focus."
1801949,2019-01-11 16:16:30 UTC,This issue was fixed in the openstack/paunch 4.2.0 release.
1801949,2018-11-06 23:13:02 UTC,Fixed by https://review.openstack.org/#/c/615909/
1801951,2019-10-17 18:56:26 UTC,Confirmed in the 3.4 release candidate.
1801954,2018-12-28 11:20:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1801954,2020-02-29 00:20:54 UTC,Same on Ubuntu 19.10 - It was working up until recently however. Error I'm given is: 'Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.'
1801964,2019-07-11 13:23:27 UTC,"The entire process for handling EDI, both pushing and fetching, could benefit from more robust error handling.  As it is, any errors with pushing are pretty much ignored and require manual intervention on the part of an administrator with access to the database and/or production servers.  This could be avoided with some sensible code in the EDI processes."
1801964,2019-11-13 20:34:06 UTC,We are running into this also.
1801970,2018-11-06 16:57:47 UTC,Sorry should have included these other versions.
1801970,2018-12-06 03:39:21 UTC,"Turns out, this affects more than just the port pair group command. It looks like the cmd_resource is not being set for port_pair, port_pair_group, and flow_classifier. As a result, these resource names are being used to build out the 'list_' commands and are failing since the methods were renamed."
1801970,2018-12-06 19:57:07 UTC,"That is strange, I suspect something changed around this helper function:
https://github.com/openstack/python-neutronclient/blob/master/neutronclient/osc/v2/sfc/sfc_port_pair_group.py#L307"
1801970,2018-12-05 03:58:08 UTC,"I, too, am having this issue. I believe I traced it back to the following commit:"
1801973,2018-11-06 17:01:24 UTC,https://github.com/snapcore/snapcraft/pull/2393
1801974,2018-11-12 13:48:18 UTC,Dear Valerio
1801974,2019-01-25 10:16:01 UTC,Dear Valerio
1801974,2018-11-12 14:05:44 UTC,"By the way, what I forgot to say is that in the FO_Analyse_card file, I had to remove LCINT from FO_EXTRALIBS since I'm using root6.14.04"
1801974,2018-11-12 13:56:33 UTC,"Dear Menziani,"
1801974,2018-11-12 13:40:55 UTC,Dear Frederix
1801974,2018-11-12 13:00:21 UTC,There is this error message:
1801974,2018-11-12 13:41:09 UTC,"Dear Meziani,"
1801974,2018-11-12 09:36:33 UTC,Dear Frederix
1801974,2018-11-12 07:43:54 UTC,"Dear Meziani,"
1801974,2018-11-12 09:56:54 UTC,What does the log file in /home/hep-ph/MG5_aMC_v2_6_3_2/amcfast2_test/SubProcesses/P0_udx_wp/all_G1/log.txt say?
1801974,2018-11-12 10:03:55 UTC,it says this
1801975,2019-08-05 10:17:10 UTC,This bug was fixed in the package dm-writeboost - 2.2.8-1ubuntu3~18.04.2
1801975,2019-08-05 10:07:09 UTC,"The verification of the Stable Release Update for dm-writeboost has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1801975,2019-08-05 09:37:27 UTC,dkms install -m dm-writeboost -v 2.2.8 -k 5.0.0-23-generic
1801975,2018-11-06 17:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1801975,2019-04-24 17:39:08 UTC,"Hello Thadeu, or anyone else affected,"
1801975,2018-11-09 02:26:35 UTC,This bug was fixed in the package dm-writeboost - 2.2.9-1ubuntu1
1801975,2019-07-24 19:29:12 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1801975,2018-11-06 17:44:10 UTC,Tested to build against 4.18 and 4.19.
1801980,2018-11-08 13:15:36 UTC,"See Bug #1796550.
--
Cristian Aravena Romero (caravena)"
1801980,2018-11-11 20:30:30 UTC,"Thanks for an answer.
I am actually user of Linux Mint 19 and not Cosmic user. I've installed package referenced in that topic, but I don't understand how to use it."
1801981,2020-02-18 01:29:29 UTC,Ubuntu 14.04 reached end of standard support in April 2019:
1801982,2019-08-07 16:32:29 UTC,"These were addressed in disco in 1.15.6-0ubuntu1, closing. Thanks!"
1801983,2019-08-07 17:27:16 UTC,"This was fixed in disco in nginx 1.15.6-0ubuntu1, closing. Thanks!"
1801990,2019-06-10 18:39:52 UTC,"There are significant changes required to support Distributed Cloud in stx due to the containerized environment. Based on discussion with the Distributed Cloud PL, Dariush Eslimi, we agreed to close old Distributed Cloud bugs as Won't Fix. A full test cycle will be needed to verify the new implementation and new bugs can be opened for the issues reported then."
1801990,2018-11-07 18:16:21 UTC,Targeting stx.2019.03 -- sync not working for a specific attribute; not urgent
1801999,2018-11-06 21:29:46 UTC,Patch available here:
1801999,2018-11-06 22:17:01 UTC,Force pushed some changes based on feedback.
1801999,2018-11-06 22:35:35 UTC,Added release notes.
1801999,2018-11-12 21:53:23 UTC,"I like the idea of this (and we do something similar as needed), but I think it would be *really* useful if it were in an org unit setting so that it could be managed by someone that doesn't have direct file access to the server and so that it could be set at consortium/system/branch levels."
1801999,2018-11-12 21:54:38 UTC,It would also be nice to have a staff-facing alert option on the web client home page that could be updated with an org unit setting.
1802001,2019-03-07 10:32:34 UTC,This issue was fixed in the openstack/python-zunclient 3.3.0 release.
1802001,2018-12-10 03:54:47 UTC,Done: https://docs.openstack.org/python-zunclient/latest/user/python-api.html
1802001,2018-11-24 19:30:23 UTC,The documentation will be online once this patch is merged: https://review.openstack.org/#/c/616069/
1802001,2018-11-06 22:31:16 UTC,"Hi Hongbin,"
1802001,2018-11-07 00:09:51 UTC,And I believe 'ContainerManager' is for internal use. 'Client' is the class for external.
1802001,2018-11-07 00:07:24 UTC,Below is the script I tried and it worked for me (I borrowed it from python-novaclient https://docs.openstack.org/python-novaclient/latest/reference/api/index.html):
1802001,2018-11-06 21:28:42 UTC,The request for documentation is valid. We will improve the documentation for python-zunclient although I have a question on the example above.
1802001,2018-11-07 02:17:25 UTC,"The only thing that was difficult was that in AUTH_URL, I changed /identity to :5000/v3"
1802005,2020-10-05 16:57:38 UTC,This bug was fixed in the package libvirt-dbus - 1.3.0-1ubuntu1
1802005,2020-10-05 14:41:21 UTC,Tested on Focal PPA
1802005,2020-10-05 12:25:25 UTC,"Confirmed, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4296 has valid Focal test builds now."
1802005,2020-10-05 12:12:00 UTC,"In Focal it is an FTFBS as well, but a different one"
1802005,2020-10-05 11:37:29 UTC,This bug was fixed in the package libvirt-dbus - 1.4.0-1ubuntu1
1802005,2020-10-05 10:53:01 UTC,"Uploaded to groovy.
I also linked another bug as duplicate which is about the same issue."
1802005,2020-10-05 10:51:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802005,2020-10-05 05:53:04 UTC,"Tested on two systems, one with one without the PPA - the fix seems to work just as planned.
This also will be used as SRU Template test steps."
1802005,2020-10-02 09:38:41 UTC,"The PPA build [1] is now complete if someone would want to give it a try.
That should add the libvirtdbus user to the group on install and therefore avoid the issues."
1802005,2020-09-30 05:46:39 UTC,FYI - this has issues to rebuild (independent to my changes) which stalls providing a test PPA a bit.
1802005,2020-09-30 05:00:06 UTC,"Sorry, meant that last reply for Christian."
1802005,2020-09-29 11:54:22 UTC,"libvirt can be configured in two ways, to use policykit for authentication, or to use traditional unix permissions. Ubuntu uses the traditional permissions configuration, not the policykit one."
1802005,2020-09-29 07:44:25 UTC,"Hi Chris,
thanks for your report, your workarounds are interesting."
1802005,2020-09-29 01:04:36 UTC,This bug affects me in Focal (20.04) and is not resolved.
1802005,2020-02-24 17:00:42 UTC,"@Christian: Wontfix WFM, I'm glad that the default works in focal (the next LTS). For the non-LTS ones it can be worked around (write a systemd unit drop-in or so), but apparently it's not such a big issue. Thanks!"
1802005,2020-02-24 15:46:41 UTC,The permissions of the sockets are usually controlled by libvirtd.conf
1802005,2020-02-24 15:40:51 UTC,"Nice, thanks Christian!"
1802005,2020-02-24 15:34:26 UTC,Eoan:
1802005,2020-02-24 15:29:24 UTC,Hi Martin o/
1802005,2020-02-18 07:59:49 UTC,The socket is actually owned by libvirt
1802005,2020-01-03 21:46:27 UTC,"I too am also affected,"
1802005,2019-12-29 09:00:11 UTC,Here as well: https://www.reddit.com/r/linuxquestions/comments/c7hcfe/whack_issues_with_cockpit_and_ubuntu_server_1904/
1802005,2019-12-29 08:58:59 UTC,Other users run into this as well: https://github.com/cockpit-project/cockpit/issues/13339
1802005,2020-09-30 01:25:10 UTC,"Mark,"
1802005,2020-09-29 01:06:57 UTC,I was able to manually workaround this on Ubuntu 20.04 with the file from here:
1802007,2019-10-31 03:30:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802008,2019-01-08 18:57:06 UTC,"Related bugs:
 - for hierarchical pins: https://bugs.launchpad.net/kicad/+bug/1781725
 - for power ports (power symbols): https://bugs.launchpad.net/kicad/+bug/1639400"
1802014,2018-11-07 09:09:48 UTC,"Oh, no, it's not. I missed this: ""Version: 0.98"""
1802014,2018-11-07 09:08:29 UTC,Looks like a duplicate of bug 1800449.
1802015,2018-11-07 00:22:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1802019,2018-11-07 06:35:55 UTC,"In the editor, we also need to be able to paint underneath a window even if it is focused, so that has to be taken into account too when doing any design changes."
1802019,2019-09-16 08:29:44 UTC,Migrated to https://github.com/widelands/widelands/issues/3351
1802021,2019-03-01 08:25:17 UTC,Do you know when a fix for linux-xenial will be available? Looks like that's the only one remaining.
1802021,2019-03-01 05:02:57 UTC,This is the final reminder to please verify that the kernel in -proposed resolves the issue for which you've filed this bug report.   Canonical is planning to release these kernels early next week.   Thank you in advance!
1802021,2019-02-25 10:23:32 UTC,This bug was fixed in the package linux-azure - 4.18.0-1011.11
1802021,2019-02-20 10:12:58 UTC,This bug was fixed in the package linux-azure - 4.18.0-1011.11~18.04.1
1802021,2019-02-14 20:53:09 UTC,"@lazamarius1: Just to clarify, the fix is scheduled to go in the 4.15 kernel in Bionic which is the same kernel as the Xenial HWE kernel. So there's no need to add anything to the Affects section. You will see a new linux-hwe 4.15 kernel in xenial-proposed once this is ready to test. Thanks!"
1802021,2019-03-04 05:08:55 UTC,"Andrei, I will discuss with engineering to confirm availability and get back to you"
1802021,2019-02-14 12:31:13 UTC,"Hi @lazamarius1,"
1802021,2019-02-14 12:28:53 UTC,"Hi @brad-figg,"
1802021,2019-02-14 12:12:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1802021,2019-02-20 10:12:27 UTC,This bug was fixed in the package linux-azure - 4.18.0-1011.11
1802021,2019-03-05 15:06:44 UTC,This bug was fixed in the package linux-azure - 4.15.0-1040.44
1802021,2019-02-08 13:18:26 UTC,"Hi Marcelo (@mhcerri),"
1802021,2019-03-16 07:37:27 UTC,"Hi Brad @brad-figg,"
1802021,2019-03-18 14:52:52 UTC,"Hi Marius @lazamarius1,"
1802021,2019-03-18 14:59:19 UTC,"@lazamarius1,"
1802021,2019-03-18 20:23:51 UTC,Thanks Mauricio! @mfo
1802021,2019-03-24 14:26:24 UTC,@mfo
1802021,2019-03-24 14:32:14 UTC,"As Marius mentioned we already deployed this patch on several instances and now we are monitoring them to see if this still happens. At least 2 of them were affected by the bug before patching so we had to reboot them.
If the above information (previous post) is correct and considering the time until this might reproduce or not, I think you might want to include this fix into existing release cycle."
1802021,2019-03-24 15:23:08 UTC,"I was experiencing a situation with moby dockerd entering a state similar to comment 0 here, running kubernetes and linux kernel 4.15.0-1037-azure. This was an 8 node cluster. Observed with combinations:"
1802021,2019-03-25 13:16:02 UTC,Updating bug tags to verification done.
1802021,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1802021,2019-04-02 10:29:42 UTC,This bug was fixed in the package linux - 4.18.0-17.18
1802021,2019-03-15 23:31:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1802021,2019-02-04 21:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802021,2019-01-29 21:58:27 UTC,The fix was picked up for upstream stable 4.19.15 and 4.20.2. I would expect the generic kernels to eventually pick up this fix.
1802021,2019-02-04 15:37:20 UTC,"Thanks David, that was my intention to patch the systems and wait for it to reproduce (usually we get the issue back in 3-8 days or so...)
Also thanks for the pointers for checking the release notes for certain releases.
Is there a connection between the changes listed in the second link and the code base for those changes? I mean to say maybe the LP bug does not appear in the changes because it was not tagged with a correct tag for it to show up but maybe the code fix is already there ? Does this make sense? I know the code fix it's already available starting with 4.19.16 but I don't know how the back-porting is handled."
1802021,2018-12-06 15:27:45 UTC,"Hi, Josh. Do you have an specific workload that triggers that issue?"
1802021,2019-02-04 17:39:31 UTC,You can clone the ubuntu-xenial kernel:
1802021,2018-12-06 17:08:52 UTC,"It's a heavy database workload from a online site, so it is difficult to make a simple repro for."
1802021,2018-12-09 20:08:29 UTC,I built a test kernel with commit eb4c2382272ae7 from linux-next.   This commit relies on commit d633198088bd9 for the definition of spin_lock_rcu_node and it's corresponding unlock.  That commit was added to mainline in v4.16-rc1
1802021,2018-12-11 20:51:20 UTC,"Joe, is your kernel different than the one Gavin Guo built for us here? https://launchpad.net/~mimi0213kimo/+archive/ubuntu/sf00204509-rcu-backport"
1802021,2018-12-12 08:55:00 UTC,"Hi Joshua,"
1802021,2018-12-12 12:25:15 UTC,"Hi Joshua,"
1802021,2019-01-16 11:12:15 UTC,"Hi, Josh."
1802021,2019-01-24 19:52:18 UTC,No new instances of the problem on the test cluster for many weeks. Let's move forward with this change.
1802021,2019-01-29 13:33:47 UTC,Using Ubuntu 16.04.5 LTS btw.
1802021,2019-01-31 15:43:07 UTC,"Hi, Josh. Should we apply the fixes for the 4.15 and 4.18 linux-azure kernel then?"
1802021,2019-01-29 12:47:06 UTC,"Will this fix be available for Linux 4.15.0-generic x86_64, or is it available already?"
1802021,2019-02-01 15:17:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802021,2019-02-04 15:14:00 UTC,"Mauricio @mfo, is there a way to reproduce the issue easily in order to test it? I was not able to find it.
The only way I can tell the issue is there or not is to apply the patch and wait for the servers to ""hit"" the problem (could take days or weeks...), and when that happens, in my case, docker tasks will end up in D state and load average will go to 100 very fast, then also a certain kworker will hit the D state and possibly in the end the init/systemd will go also in D state, and the only recovery action is to restart the box."
1802021,2019-01-31 17:15:59 UTC,"Yes, please, per comment #8"
1802021,2019-02-04 14:59:18 UTC,"Marcelo @mhcerri,"
1802021,2019-02-04 14:40:05 UTC,"Hi, @overlord."
1802021,2019-02-04 15:03:33 UTC,"Thanks Marcelo! However I still see the unassigned package is linux-hwe, and I can't add Xenial tag.
I also notices I received an update today from 4.15.0-43-generic to 4.15.0-45-generic but I cannot tell if this update has the fix from this bug.
Could you help me with some directions on this? Where could I check ?
Thanks!"
1802021,2019-02-04 07:30:47 UTC,"Hey guys, I am not sure how to do this but can you also make a patch for Xenial, 4.15.0-generic, for linux-hwe package? We have the same problem and we can't upgrade the boxes to a newer release so this would really help us."
1802021,2019-02-01 19:36:20 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-February/098264.html
1802021,2019-02-04 15:21:26 UTC,"@overlord: AFAIK, there is no simple reproducer test case for this issue. The ideal testing scenario for a bug and fix like this one would be for each user who reported this issue to use a test kernel with the fix in their environment and report back if the issue still manifests or not after some time has passed with that test kernel in your affected environment."
1802021,2019-02-01 19:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802021,2019-02-04 07:33:23 UTC,Can't run the logs collection tool since the system is stuck in D state and times out. (Also the tool is not installed on the systems). We just need this fix back-ported  on 4.15.0-generic for Xenial on linux-hwe package (we don't use linux-azure)
1802021,2019-02-04 15:18:18 UTC,"Hi overlord. An easy way to check the updates included in released kernels is to look at the ""-changes"" mailing list for your Ubuntu release."
1802023,2018-11-15 11:04:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1802023,2018-11-15 11:34:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1802023,2018-11-16 01:14:09 UTC,Smoke tested both bionic-proposed & cosmic-proposed.
1802023,2018-12-03 08:49:32 UTC,This bug was fixed in the package linux - 4.18.0-12.13
1802023,2018-12-03 14:01:15 UTC,This bug was fixed in the package linux - 4.15.0-42.45
1802025,2019-03-14 10:31:31 UTC,This issue was fixed in the openstack/murano-tempest-plugin 1.0.0 release.
1802036,2018-11-11 19:45:18 UTC,We've landed a change in mailman3-web-charm that avoids these parsing problems.
1802039,2018-08-12 14:33:17 UTC,"Created attachment 8999435
2 Window after re-maximizing"
1802039,2018-09-10 10:20:02 UTC,"I experience the same problem with gnome-flashback, see my comment here: https://bugzilla.mozilla.org/show_bug.cgi?id=1408360#c32"
1802039,2018-11-07 13:14:43 UTC,I've noticed this and reported it upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1482716
1802039,2018-11-25 02:12:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802039,2019-02-06 13:06:56 UTC,Can you try latest nightly please? Thanks.
1802039,2019-02-06 17:22:21 UTC,I just tried Nightly and I do still see the issue. I tried Ubuntu MATE 18.10 and a daily build of Disco (18.04).
1802039,2019-05-30 23:49:56 UTC,https://bugzilla.mozilla.org/show_bug.cgi?id=1552613
1802039,2019-06-23 20:30:25 UTC,Did this bug get fixed?
1802039,2021-02-02 12:44:12 UTC,This is still happening in Ubuntu Mate 20.04 with Firefox 85.0. Any updates?
1802039,2021-02-02 14:01:01 UTC,"I haven't used MATE for a couple years now, so I'm not sure myself."
1802039,2021-02-08 16:19:48 UTC,"Yeah I've been having trouble with it still in Ubuntu MATE 20.10.  Also
appears to be an issue in Vivaldi."
1802039,2018-08-12 14:30:32 UTC,"Testing with Ubuntu MATE 18.04(.1) using the default wm/compositor Marco. I've tried Nightly (downloaded from Mozilla), Firefox 61 (the version in the Ubuntu repo), and back to 60 (downloaded from Mozilla) (I think the first version with CSD?)."
1802039,2018-08-12 14:32:31 UTC,"Created attachment 8999434
1 Window after unmaximizing"
1802050,2019-02-11 23:27:06 UTC,"My OS details:
$ uname -a
Linux Ubuntu-PC 4.18.0-15-generic #16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1802050,2019-02-11 21:54:27 UTC,"Also, worth to note, I had similar crashes before upgrading to nVidia, by using Nouveau driver. See: https://bugs.freedesktop.org/show_bug.cgi?id=100567"
1802050,2018-11-07 06:31:30 UTC,Kernel module crash after dist-upgrade from 18.04 to 18.10. This happens after every boot. I rebuild dkms modules twice. Everything else runs smoothly :-)
1802050,2019-02-11 15:30:41 UTC,Still reproducible on 4.18.0-15-generic
1802050,2019-01-10 05:26:49 UTC,"redhat fixed it https://bugzilla.redhat.com/show_bug.cgi?id=1570493
debian followed also with the same patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919"
1802050,2018-11-07 15:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802050,2019-02-11 21:51:53 UTC,Related: https://forums.geforce.com/default/topic/1098094/geforce-drivers/kernel-crash-at-_nv009384rm-os_memcpy_to_user-bad-or-missing-usercopy-whitelist-/
1802052,2018-11-28 09:30:40 UTC,"I am not sure if the issue started happening after an update/upgrade. I noticed it the first time I tried.
No there was no prior kernel version where I was not having this problem.
I tried the latest upstream kernel - The issue still exists."
1802052,2018-11-15 21:26:09 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1802052,2018-11-07 07:00:07 UTC,This change was made by a bot.
1802052,2018-11-07 07:22:42 UTC,"Removing ""acpi_osi=! ""acpi_osi=Windows 2009"" "" from boot does not fix the issue."
1802052,2018-11-07 07:14:40 UTC,Issue persists in upstream kernel v4.19.
1802052,2018-11-07 11:38:35 UTC,I have attached the dsdt.dsl file.
1802056,2018-11-07 07:30:06 UTC,This change was made by a bot.
1802056,2018-11-07 07:44:34 UTC,"Similar issue bug 1765668
This is not a regression."
1802062,2020-03-07 17:31:49 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1802064,2019-07-18 22:33:46 UTC,"Hi,"
1802064,2019-09-17 04:17:42 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1802067,2018-11-08 20:24:43 UTC,It looks like the underlying error is this:
1802067,2018-11-09 06:18:50 UTC,"Tim, I wonder if it would be worth discussion potential reasons that the controller would randomly shut down - this wasn't on a long lived controller that might have undergone maintenance, it is on a controller in our CI environment that would have been, at most, one week old (and likely less than two days). We never intentionally shut them down except when we destroy and re-create them, and that never happens during a test run."
1802067,2018-11-11 20:11:34 UTC,"Sure, did you want the conversation on this bug or in person?"
1802067,2019-05-03 00:30:16 UTC,"Hi, I am facing this same issue. After application-version-set fails, jujud seems to shutdown and the unit is kept on ""waiting"" status."
1802068,2018-11-08 03:17:53 UTC,"    def resize_fs(self, mount_point):
        """"""Resize the filesystem on the specified device.""""""
        self._check_device_exists()
        # Some OS's will mount a file systems after it's attached if
        # an entry is put in the fstab file (like Trove does).
        # Thus it may be necessary to wait for the mount and then unmount
        # the fs again (since the volume was just attached).
        try:
            if self._wait_for_mount(mount_point, timeout=2):
                if CONF.volume_fstype == 'xfs':
                    utils.execute(""xfs_growfs"", self.device_path,
                                  run_as_root=True, root_helper=""sudo"")
                    LOG.debug(""Unmounting '%s' before resizing."" % mount_point)
                    self.unmount(mount_point)
                    return"
1802070,2020-09-26 06:40:05 UTC,"Change abandoned by Dmitriy Rabotyagov (noonedeadpunk) (<email address hidden>) on branch: master
Review: https://review.opendev.org/616113"
1802070,2019-06-18 20:27:01 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.opendev.org/629880"
1802070,2019-01-17 19:46:56 UTC,Fix merged for openstack-ansible here https://review.openstack.org/#/c/628197
1802070,2019-01-02 10:41:55 UTC,Ah sry
1802070,2019-01-02 10:26:32 UTC,"Hallo all,"
1802070,2019-01-10 15:22:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/629880"
1802070,2018-11-07 08:58:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616113"
1802077,2018-11-07 09:30:15 UTC,This change was made by a bot.
1802077,2018-11-07 10:49:02 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1802077,2018-11-07 12:44:18 UTC,"I didn't use bluetooth on this machine before, so this may or may not be relevant to update.
I also can't try a new kernel version."
1802078,2018-11-07 10:15:57 UTC,This is because the postgresql snap doesn't have any revisions published in the 'latest' track
1802078,2018-12-17 16:47:59 UTC,wgrant - please evaluate and determine scope of work to expand search for non-latest tracks.
1802078,2019-10-22 20:23:26 UTC,"$ snap info postgresql
error: no snap found for ""postgresql"""
1802084,2019-09-03 17:43:51 UTC,Committed: https://git.launchpad.net/upnp-router-control/commit/?id=0d436e4f78ccf2e224d3e0aabceeacb76012b56e
1802092,2018-11-07 12:28:11 UTC,"It's possible to switch on/off different outline modes and also adjust opacity of pads etc. Those features help when trying to find tracks. However, the suggested feature, if implemented for tracks which overlap any other copper (tracks, zones, other tracks) would help everywhere without any actions by the user. I can't find any drawbacks in the idea, either."
1802094,2018-11-11 20:10:06 UTC,"gdm3: didn't work when I tried a couple of days ago, wanted to test again now, but unable to do so, x11vnc doesn't want to play nice with gdm3."
1802094,2018-11-22 19:33:05 UTC,"Accessing the pc: remotely only if I have no other choice. LDAP always though, unless there are LDAP issues, then a local account."
1802094,2018-11-14 16:54:00 UTC,"LDAP, x11vnc... !?"
1802094,2018-11-11 20:53:06 UTC,"journalctl _COMM=gnome-flashback
-- Logs begin at Fri 2018-11-02 19:04:45 CET, end at Sun 2018-11-11 21:43:50 CET. --
Nov 06 17:47:31 R1 gnome-flashback[11436]: failed to commit changes to dconf: The connection is closed
Nov 06 17:47:31 R1 gnome-flashback[11436]: Error unregistering authentication agent: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: T
Nov 06 17:47:31 R1 gnome-flashback[11436]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/vo
Nov 06 17:47:31 R1 gnome-flashback[11436]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/vo
-- Reboot --
Nov 06 21:06:39 R1 gnome-flashback[7089]: g_object_notify: object class 'UpClient' has no property named 'g-name-owner'
Nov 06 21:06:39 R1 gnome-flashback[7089]: gnome-flashback: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
-- Reboot --
Nov 09 01:50:04 R1 gnome-flashback[3592]: g_object_notify: object class 'UpClient' has no property named 'g-name-owner'
Nov 09 01:50:04 R1 gnome-flashback[3592]: Couldn't upload new XKB keyboard description
Nov 09 01:50:04 R1 gnome-flashback[3592]: failed to commit changes to dconf: The connection is closed
Nov 09 01:50:04 R1 gnome-flashback[3592]: Error unregistering authentication agent: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: Th
Nov 09 01:50:04 R1 gnome-flashback[3592]: gnome-flashback: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
-- Reboot --
Nov 11 20:58:24 R1 gnome-flashback[30233]: The owner of /home/christian/.config/ibus/bus is not root!"
1802094,2018-11-11 20:09:34 UTC,"Unfortunately apport-collect did not attach any logs, only some information about versions."
1802094,2018-11-11 19:34:43 UTC,apport information
1802094,2018-11-11 19:34:44 UTC,apport information
1802094,2018-11-07 20:47:26 UTC,A newly created local user with command adduser was also unable to login.
1802094,2018-11-07 12:13:02 UTC,Well this starts sound like problem is somewhere else... Do I understand correctly that you can not login only in LDAP?
1802094,2018-11-11 19:34:42 UTC,apport information
1802094,2018-11-09 21:22:40 UTC,Can you please run “apport-collect 1802094” on the affected machine? This command will attach some logs to this bug.
1802105,2018-11-07 15:05:03 UTC,"Thank you for your bug report, that's known upstream as https://bugzilla.gnome.org/show_bug.cgi?id=786395"
1802105,2019-04-14 18:16:57 UTC,"Hello,"
1802105,2019-04-19 12:06:32 UTC,"Sorry, can't compile it. Where can I find the build instruction?"
1802107,2019-05-09 10:58:48 UTC,"I seem to have the same issue, though it seems to be triggered by the initial Docky instance crashing on startup. Details below:"
1802108,2019-02-22 11:08:27 UTC,https://bugs.launchpad.net/tripleo/+bug/1815204
1802108,2019-10-01 14:41:09 UTC,Fixed in https://bugs.launchpad.net/tripleo/+bug/1815204
1802108,2019-02-19 13:37:42 UTC,Is this stillan issue?
1802108,2019-02-20 09:04:38 UTC,"Yes, sadly. There is progress but also mixup of tracking LP issues. Ill try to make order in this today."
1802110,2018-11-07 15:17:21 UTC,It turns out that none of the migration scripts executes a backpropagation of neutron_nsx_network_mappings to add the dvs_id values of nsxv_tz_network_bindings.
1802110,2018-11-08 12:02:50 UTC,Turns out the vnic binding table was missing some entries. I assume it's another db migration issue.
1802111,2018-12-19 10:01:29 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1802111,2018-11-13 09:21:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/617535"
1802111,2019-03-22 03:46:09 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1802111,2018-11-09 16:33:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616991"
1802111,2018-11-09 16:29:29 UTC,The other workaround with the older AggregateMultiTenancyIsolation filter is to create as many aggregates for the same hosts as needed to cover the number of tenants needed. It's unfortunate but that's a workaround until you get to Rocky and can use the newer filtering mechanism.
1802111,2018-11-09 16:20:59 UTC,I'm just going to update the docs because we have a replacement for the old filter in Rocky.
1802111,2018-11-09 16:19:36 UTC,"Yup, this is a known limitation, and also that the AggregateMultiTenancyIsolation filter doesn't allow scoping to keystone domains. I think there is a Public Cloud SIG bug related to this as well."
1802111,2018-11-09 23:56:58 UTC,"Reviewed:  https://review.openstack.org/616991
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1fa09acf08dacf94a435fbdaddc50eabfada48ec
Submitter: Zuul
Branch:    master"
1802111,2018-12-07 16:08:24 UTC,"Reviewed:  https://review.openstack.org/617535
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4c0342bf1d86bca2bedf1118b341295998d2c7f6
Submitter: Zuul
Branch:    stable/rocky"
1802115,2019-05-14 07:22:43 UTC,"Unless we reproduce this elsewhere, I don't think this is worth digging into further"
1802116,2018-11-08 15:40:16 UTC,Workaround for this problem was adding
1802120,2020-03-07 11:15:39 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1802120,2020-05-07 04:17:21 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1802122,2018-11-07 15:21:30 UTC,"https://paste.ubuntu.com/p/RtMQjvfM9d/ <- JSON journal output, trimmed to get relevant info"
1802123,2020-01-16 17:11:17 UTC,This issue has now been solved. See:
1802123,2020-01-16 17:15:11 UTC,"Sorry, gave a link to a post instead of the main thread:"
1802128,2018-11-09 13:49:17 UTC,Confirmed in 3.2 on our test server. Only one edition statement appears in the OPAC view when the bib record has multiple ones.
1802128,2019-09-13 21:04:38 UTC,"Have added ""cataloging"" tag to help this item stand out to catalogers."
1802132,2018-11-27 16:41:16 UTC,Can you please share your user_varibles.yml and openstack_user_config.yml file?
1802132,2018-11-28 12:38:20 UTC,"Thank you very much for your email. My openstack_user_config.yml is as below. Right now, it's all in one setup. Later, we plan to add extra node and deploy it as a separate compute node."
1802132,2018-11-20 16:50:17 UTC,Can you please try running this again?
1802132,2018-11-20 21:45:28 UTC,"I have tried this. In fact, I have gone as far as destroying all containers using 'lxc-destroy' and setting everything up from scratch with"
1802133,2018-12-07 07:22:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802133,2020-09-16 02:54:45 UTC,"For now, on 20.04, this problem still happened."
1802133,2020-09-16 03:02:10 UTC,"But, basically, we may not use tpm 1.2 and its tool anymore due to likely transitioning to 2.0 for the general case."
1802137,2018-11-07 16:22:00 UTC,[0]: https://www.spinics.net/lists/linux-bluetooth/msg75267.html
1802138,2020-01-02 16:17:12 UTC,"Created attachment 9348
improved xflock4"
1802138,2020-01-01 23:04:34 UTC,"I do not see a problem in having even longer delay than a second. But, using ""sleep 1; xset dpms force off"" has still the problem that user may accidentally touch something so that display will become on again. Besides, it effectively disables Presentation mode user may have set using Power manager's panel item."
1802138,2020-01-01 17:12:31 UTC,Maybe some implementations of sleep do not allow non-integer number argument.
1802138,2019-05-01 14:35:01 UTC,"@Simon: apologies, if your previous comment is directed at me. I'm currently on Ubuntu 19.04(Gnome 3) without a proper XFCE4 installation to test this on."
1802138,2019-04-27 22:52:39 UTC,@Chris: Does a sleep of <1sec also work?
1802138,2018-11-07 20:23:11 UTC,"The attachment ""sleep added."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1802138,2018-11-07 20:12:31 UTC,Still happening in Xubuntu 18.10. I vote for adding the patch!
1802138,2015-02-24 04:05:05 UTC,Same problem with:
1802138,2015-02-12 02:20:22 UTC,"Ok, I've been a bit silly on that one. So, when having slock installed I reach this code path."
1802138,2015-02-12 10:47:11 UTC,"> With the patch: 1 second delay, then a black screen
> Without the patch: black screen immediately
"
1802138,2015-02-12 02:21:19 UTC,"Chris, thanks for writing the patch and bearing with me though. Of course if you can link to others complaining about the issue, and to more precise reasons why it is systematically happening for you, it'll increase the odds of people weighing in favour of your patch."
1802138,2015-02-08 21:15:53 UTC,"Can you try ""slock & sleep 1; xset dpms force off"""
1802138,2015-02-08 20:36:33 UTC,"Hi Chris,"
1802138,2015-02-08 20:27:28 UTC,"@Steve Yes the patch works for me using slock.
What exactly fails for you?
Does ""sleep 1; xset dpms force off"" successfully turn off the monitors on your system?
Do you have one of {xscreensaver-command,light-locker-command,gnome-screensaver-command} installed? If so, the xset dpms line in xflock4 is never executed."
1802138,2015-02-08 17:07:02 UTC,"I can reproduce the issue, but the patch does not work for me (Xfce 4.11, ArchLinux 64 bits, xscreensaver 5.32)."
1802138,2015-02-08 12:50:49 UTC,"Created attachment 5915
xflock4-sleep.patch"
1802138,2015-01-31 13:03:53 UTC,"As noted at http://www.shallowsky.com/linux/x-screen-blanking.html calls to ""xset dpms"" need to be prefixed with ""sleep 1"":"
1802138,2015-02-12 17:37:48 UTC,Also see:
1802138,2015-02-08 20:38:11 UTC,"Errata; after uninstalling xscreensaver, the patch still does not work."
1802143,2019-08-22 18:37:33 UTC,"Reviewed:  https://review.opendev.org/672805
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=2468ceaa724aa5c8c44fb87ae223eb6687ff85f2
Submitter: Zuul
Branch:    master"
1802143,2019-07-25 18:21:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672805"
1802146,2018-11-09 20:00:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802147,2018-11-07 17:49:34 UTC,This requirement is similar to https://bugs.launchpad.net/opencontrail/+bug/1801764
1802148,2020-08-09 23:08:15 UTC,grafana 5.2.1
1802154,2018-11-07 20:49:04 UTC,"Untested suggestion to yan0s in IRC
 http://paste.ubuntu.com/p/VSjZpMvtH6/"
1802154,2018-11-08 11:22:38 UTC,In MAAS 2.4.2:
1802154,2019-02-15 12:24:52 UTC,"I've overcommed this problem by forcing curtin to use the stretch and the buster repos. The both packages required for UEFI secure booting are being installed (as they are present in the buster repos), and once the target OS is booted for first time cloud-init takes the control and replaces the sources so the buster repos automagically dissapear."
1802154,2018-11-08 13:50:27 UTC,"An idea would be moving this decision (about which grub packages are needed) from the python code to the preseed file as ""early_commands"". And maybe create a preseed_examples directory for major distros. What do you think?"
1802156,2018-11-07 20:50:53 UTC,"Also related:
bug 1091885"
1802166,2020-07-27 14:59:06 UTC,Pushed all the way to rel_3_4.  I added a follow-up to the release notes to mention a way of clearing the preferred name and name keyword fields from already-purged records:
1802166,2020-01-09 14:47:32 UTC,"Works as advertised, signoff for keywords and names pushed to user/rogan/lp1802166_purge_preferred_names_and_keywords_signoff"
1802166,2019-07-01 17:30:30 UTC,"I already made a 3.2 backport branch that we're using at CW MARS in production, so I've gone ahead and pushed it: user/dyrcona/lp1802166-purge-preferred-names_rel_3_2"
1802166,2019-05-22 21:10:24 UTC,"As a (small) privacy issue, I do think it needs to be fixed in 3.2.x as well. I've added the target and will take responsibility for the backports."
1802166,2019-02-15 18:36:42 UTC,"I added another commit to set name_keywords to NULL, so you want the top two commits on the branch."
1802166,2019-02-15 17:41:30 UTC,I have pushed a branch that fixes this for master/3.3: user/dyrcona/lp1802166-purge-preferred-names in the working repository.
1802168,2018-11-07 20:06:02 UTC,apport information
1802168,2018-11-07 20:06:10 UTC,apport information
1802168,2018-11-07 20:06:11 UTC,apport information
1802168,2018-11-07 19:31:44 UTC,"Reloading the psmouse kernel module with ""elantech_smbus=0"", I get back the right-click, as documented in the upstream bug."
1802168,2018-11-08 13:34:04 UTC,"Add 'patch' in 'Tags'. For https://bugzilla.redhat.com/show_bug.cgi?id=1628715
--
Cristian Aravena Romero (caravena)"
1802168,2018-11-08 13:03:29 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1802168,2018-11-08 13:22:41 UTC,"Yes, as much as I can tell, it started after the upgrade. I did share a link to RedHat bugzilla that describe the exact same issue, documented to start with 4.18, provides a patch that has been confirmed on the very same laptop that I use: I don't see the point of testing mainline 4.19. I'd be happy to test a ubuntu 4.18 built with their patch."
1802168,2018-11-07 20:06:08 UTC,apport information
1802168,2018-11-07 20:06:13 UTC,apport information
1802168,2018-11-07 20:06:07 UTC,apport information
1802168,2018-11-07 20:06:03 UTC,apport information
1802168,2018-11-07 20:06:05 UTC,apport information
1802168,2018-11-07 20:06:04 UTC,apport information
1802168,2018-11-07 20:06:01 UTC,apport information
1802168,2018-11-07 20:05:56 UTC,apport information
1802168,2018-11-07 20:05:57 UTC,apport information
1802168,2018-11-07 20:05:59 UTC,apport information
1802168,2018-11-17 09:30:49 UTC,"Sorry to bother you again, but is there a branch for the kernel where one can checkout the progress? I noticed that nothing has been merged yet to 4.20-rc1/rc2."
1802168,2018-11-07 20:06:00 UTC,apport information
1802168,2018-11-07 20:06:06 UTC,apport information
1802168,2018-11-19 17:36:38 UTC,Patch series applies cleanly also on 4.19.2. New scratch build on koji https://koji.fedoraproject.org/koji/taskinfo?taskID=30991677
1802168,2019-01-02 14:52:38 UTC,"As mentioned, libinput 1.12.4 has a quirk for the t480s.
Regarding the kernel, I pushed a revert-like for the p52/p72, so now all those three machines should be fine. The patch has been backported to 4.19, so I guess if it's not already in F29, it will be in the next week or so."
1802168,2018-12-12 07:57:33 UTC,Patch series applies cleanly on 4.19.8. New scratch build on koji https://koji.fedoraproject.org/koji/taskinfo?taskID=31418467
1802168,2018-11-07 19:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802168,2019-08-21 22:56:27 UTC,"Was it already patched in kernel and merged?
If it was - which version of kernel was the first with this patch merged?
I'm having similar problems on other distro on kernel 5.2.9 with some HP Pavilion's touchpad and created libinput quirk which is basicly the same as quirks for this clickpad."
1802168,2019-07-22 07:36:59 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1802168,2019-04-18 14:01:23 UTC,"Just upgraded to Disco, it seems okay, not checked if it's really fixed or just a workaround in place."
1802168,2019-03-19 16:40:13 UTC,Can we backport to Cosmic?
1802168,2019-02-26 10:46:52 UTC,So there is a temporary fix in libinput (https://bit.ly/2ExTtIm) before Benjamin's kernel fix is accepted as discussed in https://gitlab.freedesktop.org/libinput/libinput/issues/177. That fix is already in Disco so only need to fix Cosmic.
1802168,2019-02-22 16:25:27 UTC,"> Affected by LP: #1802135?
"
1802168,2019-02-22 14:11:19 UTC,Affected by LP: #1802135?
1802168,2019-02-15 17:51:42 UTC,"What is currently blocking this from being merged into the Kernel? I have to keep reapplying this patch even on 4.20.8 -- the kernel bug linked in this thread appears to be a different issue, at least from the comments there. Does someone need to actually file a bug for the T480s (et al) touchpad issue to get this finally merged?"
1802168,2018-11-24 16:57:38 UTC,"Hi Benjamin,"
1802168,2019-02-05 17:38:24 UTC,"I should have mentionned that it's still affecting with uptodate 18.10, latest kernel etc."
1802168,2019-02-02 10:03:17 UTC,"Created attachment 1526247
libinput records for two versions of libinput"
1802168,2019-02-02 09:30:06 UTC,"(In reply to Benjamin Tissoires from comment #59)

> As mentioned, libinput 1.12.4 has a quirk for the t480s.
> Regarding the kernel, I pushed a revert-like for the p52/p72, so now all
> those three machines should be fine. The patch has been backported to 4.19,
> so I guess if it's not already in F29, it will be in the next week or so.
>
> The proper kernel support is still on its way, but I think we can close the
> Fedora bug right now.
"
1802168,2019-01-07 08:19:36 UTC,Can we get any news on that?
1802168,2019-01-04 06:44:56 UTC,I can confirm that with kernel-4.19.13-300.fc29.x86_64 TrackPoint & Touchpad including all 6 buttons work OOTB on my Lenovo P52.
1802168,2018-12-27 18:20:51 UTC,The workaround in libinput 1.12.4 solved the problems also on my side!
1802168,2018-12-27 17:41:32 UTC,"Was this fix officially resolved and pushed upstream? My T480s with Elan Touchpad suddenly regained right click with two fingers and bottom right corner, running 4.19.10-300.fc29.x86_64. However I have some coworkers with the same laptop who report the issue persists."
1802168,2018-12-14 14:48:56 UTC,Workaround for P52 works for me. New scratch build for F29: https://koji.fedoraproject.org/koji/taskinfo?taskID=31456822
1802168,2018-12-12 20:54:29 UTC,"> @Benjamin I just discovered your new patch series https://patchwork.kernel.org/project/linux-input/list/?series=55699. Is that workaround supposed to be to replace the original series https://patchwork.kernel.org/project/linux-input/list/?series=30187?
"
1802168,2018-12-12 19:24:50 UTC,"@Benjamin I just discovered your new patch series https://patchwork.kernel.org/project/linux-input/list/?series=55699. Is that workaround supposed to be to replace the original series https://patchwork.kernel.org/project/linux-input/list/?series=30187? It is marked for 4.18+ stable, i.e. will it make it to 4.19 and 4.20?"
1802168,2019-02-05 17:09:10 UTC,This is still affecting my system.
1802168,2018-11-05 10:12:18 UTC,"(In reply to barish from comment #45)

> Hey just piggybacking on Stefan as I've been unable to find time to until I
> got the email notification, but it's still very time consuming having to
> rebuild my kernel every time a new one is released. My device is managed by
> Chef so dnf update is run every 30 minutes in the background and I don't
> realize I have a new kernel until I reboot and lose right-click again.
"
1802168,2018-11-06 21:36:13 UTC,"(In reply to Stefan Becker from comment #46)

> The only thing that doesn't work is the middle button in the button row
> below the touchpad. I don't see anything in the evemu record when I press
> that button.
"
1802168,2018-11-02 20:57:37 UTC,"(In reply to Benjamin Tissoires from comment #41)

> (In reply to franciserol from comment #40)
> > Need some help.  I currently use a thinkpad P52 and have run into the issue
> > where touchpad completely stops working on any 4.18 kerenel to get around
> > the issue I had been using a 4.17 kernel.  This morning after updating I
> > know no longer have the 4.17 kernel and instead 3 4.18 kernels to choose
> > from.  The latest kernel 4.18.13.200.fc38.x86_64 this issue is still
> > present.  Touchpad not working at all.  I no longer have a 4.17 kernel to
> > revert back to.  Please any assistance would be greatly appreciated.
>
> Yep, this is a known issue. I submitted the series upstream this week
> (https://patchwork.kernel.org/project/linux-input/list/?series=30187) and I
> need to send a v2 based from the reviews. When this gets upstream, we will
> ask the fedora maintainers to take the patches in the v4.18 series, but we
> can't really backport patches that are not accepted upstream yet.
>
> Apologies for the inconvenience.
"
1802168,2018-10-09 07:06:47 UTC,"Peter mentioned that if you are on f28, which should be the case, you can replace the 2 recordings of evemu+libinput debug-event by a single call to ""sudo libinput record""."
1802168,2018-10-09 06:54:30 UTC,"barish, can you provide us some logs so we can actually debug the issue?
I would need:
- a dmesg from the boot on the 4.18 kernel,
- an evemu-record of the touchpad (package evemu) when you are actually using the right click (still on the v4.18 kernel)
- While you are capturing the evemu trace, it would be interesting to see the 'libinput debug-events' trace in parallel (beware to not capture the password of 'sudo' while libinput debug-event is running. We won't see the actual characters, but we will see the length)"
1802168,2018-10-04 16:39:18 UTC,"I compiled upstream 4.19-rc6 today. Right and middle-click with two, respectively three fingers does not work. So I guess this bug might still be open? Also the official kernel package from the fedora repository 4.18.10-200 did not fix the issue."
1802168,2018-09-26 20:16:58 UTC,"kernel-4.18.9-100.fc27, kernel-headers-4.18.9-100.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report."
1802168,2018-11-02 22:31:24 UTC,"Created attachment 1500694
Lenovo P52, 4.18.16-300.p52.1.fc29.x86_64 with elan patches included"
1802168,2018-09-24 00:15:50 UTC,(Adding myself to the CC list for visibility.)
1802168,2018-09-21 08:32:59 UTC,"kernel-4.18.9-100.fc27, kernel-headers-4.18.9-100.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-d77cc41f35"
1802168,2018-09-20 20:45:52 UTC,"Neither the latest stable update, nor the latest vanilla fedora knurd have resolved this issue. I am still running 4.17.19-200.fc28.x86_64 to maintain my touchpad function. Can this please be fixed? This model laptop had been working perfectly up until this point."
1802168,2018-09-20 19:12:54 UTC,"kernel-4.18.8-200.fc28, kernel-headers-4.18.8-200.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report."
1802168,2018-10-09 08:27:50 UTC,"Created attachment 1491990
dmesg output for kernel 4.18.10 on ThinkPad Yoga L380"
1802168,2018-09-20 15:56:29 UTC,kernel-headers-4.18.9-100.fc27 kernel-4.18.9-100.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-d77cc41f35
1802168,2018-09-18 18:49:24 UTC,"(In reply to Fedora Update System from comment #7)

> kernel-4.18.8-200.fc28, kernel-headers-4.18.8-200.fc28 has been pushed to
> the Fedora 28 testing repository. If problems still persist, please make
> note of it in this bug report.
> See https://fedoraproject.org/wiki/QA:Updates_Testing for
> instructions on how to install test updates.
> You can provide feedback for this update here:
> https://bodhi.fedoraproject.org/updates/FEDORA-2018-f93103ae20
"
1802168,2018-09-18 14:46:31 UTC,"(In reply to Fedora Update System from comment #7)

> kernel-4.18.8-200.fc28, kernel-headers-4.18.8-200.fc28 has been pushed to
> the Fedora 28 testing repository. If problems still persist, please make
> note of it in this bug report.
> See https://fedoraproject.org/wiki/QA:Updates_Testing for
> instructions on how to install test updates.
> You can provide feedback for this update here:
> https://bodhi.fedoraproject.org/updates/FEDORA-2018-f93103ae20
"
1802168,2018-09-17 19:24:47 UTC,"kernel-4.18.8-200.fc28, kernel-headers-4.18.8-200.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-f93103ae20"
1802168,2018-09-13 18:58:47 UTC,Description of problem:
1802168,2018-09-13 23:38:52 UTC,"This is https://bugzilla.kernel.org/show_bug.cgi?id=200899, we should pick up that patch for the fedora kernel"
1802168,2018-09-14 14:30:13 UTC,"(In reply to Peter Hutterer from comment #1)

> This is https://bugzilla.kernel.org/show_bug.cgi?id=200899, we should pick
> up that patch for the fedora kernel
"
1802168,2018-09-14 14:42:44 UTC,"(In reply to Peter Hutterer from comment #1)

> This is https://bugzilla.kernel.org/show_bug.cgi?id=200899, we should pick
> up that patch for the fedora kernel
"
1802168,2018-09-17 15:04:20 UTC,kernel-headers-4.18.8-200.fc28 kernel-4.18.8-200.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-f93103ae20
1802168,2018-09-17 15:05:42 UTC,kernel-headers-4.18.8-100.fc27 kernel-4.18.8-100.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-3b2c23b946
1802168,2018-09-18 22:03:41 UTC,You can see the fixes I picked up at https://src.fedoraproject.org/rpms/kernel/c/473a8aafe6eae66e8053b11aba38df07b285349e?branch=f28 . If there's another one please let me know
1802168,2018-10-09 08:31:46 UTC,"Created attachment 1491992
libinput record of right click, left click and trying to move a window"
1802168,2018-09-25 20:13:29 UTC,"(In reply to Peter Hutterer from comment #1)

> This is https://bugzilla.kernel.org/show_bug.cgi?id=200899, we should pick
> up that patch for the fedora kernel
"
1802168,2018-10-09 10:13:14 UTC,"Created attachment 1492024
libinput record of right click, left click and window drag"
1802168,2018-09-17 18:28:12 UTC,"kernel-4.18.8-100.fc27, kernel-headers-4.18.8-100.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-3b2c23b946"
1802168,2018-11-02 19:58:07 UTC,Got a brand-new P52 yesterday and of course installed the brand-new F29 on it. As F29 only has kernel 4.18 I ran into this issue :-(
1802168,2018-10-18 18:19:15 UTC,"(In reply to franciserol from comment #42)

> ok thx Benjamin will probably have to switch to using my old macbook pro
> till this is resolved.
"
1802168,2018-10-09 08:55:01 UTC,"so, we have:
    #   Event code 273 (BTN_RIGHT)
...
    # Properties:
    #    Property 0 (INPUT_PROP_POINTER)"
1802168,2018-10-18 14:01:54 UTC,"(In reply to franciserol from comment #40)

> Need some help.  I currently use a thinkpad P52 and have run into the issue
> where touchpad completely stops working on any 4.18 kerenel to get around
> the issue I had been using a 4.17 kernel.  This morning after updating I
> know no longer have the 4.17 kernel and instead 3 4.18 kernels to choose
> from.  The latest kernel 4.18.13.200.fc38.x86_64 this issue is still
> present.  Touchpad not working at all.  I no longer have a 4.17 kernel to
> revert back to.  Please any assistance would be greatly appreciated.
"
1802168,2018-10-18 13:57:35 UTC,"Hi,"
1802168,2018-10-12 23:01:58 UTC,"(In reply to Benjamin Tissoires from comment #36)

> Created attachment 1493337 [details]
> elan_i2c_v2.patch
>
> Here is the updated (hopefully final) patch that I am going to submit in a
> few minutes.
>
> There has not been much changes, some typos, doc and rename of some
> properties. I am confident it still works, but I'd be glad if someone could
> give it a try so I am sure it still fixes the T480s.
"
1802168,2018-10-12 22:17:28 UTC,"Created attachment 1493437
libinput record, T480s, logs from kernel-4.18.13-201 patched with elan_i2c_v2"
1802168,2018-10-12 20:14:22 UTC,Works fine :-)!
1802168,2018-10-12 13:56:31 UTC,"Created attachment 1493337
elan_i2c_v2.patch"
1802168,2018-10-18 14:10:42 UTC,ok thx Benjamin will probably have to switch to using my old macbook pro till this is resolved.
1802168,2018-10-09 18:39:38 UTC,"Glad to see this got worked out, Please let us know when there's a patch that's ready to apply to Fedora."
1802168,2018-10-09 17:49:57 UTC,"Created attachment 1492149
T480s, Logs from Kernel 4.19-rc7(patch+fix)"
1802168,2018-10-09 16:48:21 UTC,"(In reply to Michael from comment #31)

> Created attachment 1492144 [details]
> T480s, Logs from Kernel 4.19-rc7(patched)
>
> Here you are :)
"
1802168,2018-10-09 16:28:46 UTC,"Created attachment 1492144
T480s, Logs from Kernel 4.19-rc7(patched)"
1802168,2018-10-09 16:23:09 UTC,"Michael, do you have the evemu-record of the touchapd with the patched kernel?"
1802168,2018-10-09 15:42:30 UTC,"(In reply to Michael from comment #28)

> Created attachment 1492123 [details]
> T480s, Logs from Kernel 4.18.10-200
"
1802168,2018-10-09 15:40:51 UTC,"Created attachment 1492123
T480s, Logs from Kernel 4.18.10-200"
1802168,2018-10-09 15:03:28 UTC,https://koji.fedoraproject.org/koji/taskinfo?taskID=30148153
1802168,2018-10-09 14:31:15 UTC,"Created attachment 1492100
elan_i2c.patch"
1802168,2018-10-09 10:23:15 UTC,"(In reply to Pascal from comment #24)

> Created attachment 1492024 [details]
> libinput record of right click, left click and window drag
>
> Yes, it seems you are right. The touchpad is in fact a clickpad.
"
1802168,2018-10-10 06:28:33 UTC,"Hello Benjamin,"
1802169,2019-08-09 13:21:12 UTC,One of our libraries also requested a hover for the full column heading text. Marking this Confirmed.
1802169,2020-05-14 18:29:25 UTC,Related bug #1738266
1802174,2020-02-13 16:25:52 UTC,@barryprice - RHEL7 should be deployable with MAAS 2.3+ and Curtin-18.1-59+. Make sure you are using those versions or newer. Its possible MAAS commissioned the system using BIOS compatibility which is why the UEFI partition isn't being added correctly. Try recommissioning after making sure the power boot type is set to UEFI.
1802174,2020-02-13 10:08:52 UTC,This still exists in at least version 2.3.5 (6511-gf466fdb-0ubuntu1).
1802174,2019-09-19 14:47:58 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1802174,2018-11-07 22:50:51 UTC,The error message at the bottom is key:
1802174,2018-11-08 15:40:51 UTC,"How is this reproducible?
How was the configuration when this happened?
What did the user do to felony and have this failed?
Was the machine originally not EFI and the user then set it to EFI manually?
What were the porter control settings like?"
1802174,2018-11-08 09:00:25 UTC,My mistake I thought we had added the UEFI partition back. I'm moving this to a MAAS bug as MAAS should not allow deployments on UEFI systems if the UEFI partition is missing.
1802174,2018-11-08 17:10:59 UTC,"The machine was commissioned as a UEFI host and IPMI is configured to boot UEFI. The user created a custom storage layout which did not include /boot/efi. MAAS allowed the user to deploy the machine but deployment failed due to /boot/efi missing. This happens when deploying Ubuntu, CentOS, or RHEL."
1802177,2018-11-08 10:55:48 UTC,"Are you saying that this should be done in 18.04? Not going to happen, besides there are missing dependencies which don't have python3 version packaged yet, like talloc, ldb, samba etc..."
1802177,2019-11-28 14:06:10 UTC,"freeipa 4.8.x migrated to py3, available in 19.10 and up"
1802182,2018-12-07 09:00:01 UTC,"Reviewed:  https://review.openstack.org/623301
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=67c9cdf20474acbbe79ee3889bfc2d4d30bf519f
Submitter: Zuul
Branch:    stable/18.11"
1802182,2018-12-06 20:02:46 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/623301"
1802182,2018-11-29 12:31:06 UTC,"Reviewed:  https://review.openstack.org/620134
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=ef5e7a36a9a97b1ef49cc1fde9f7a689b229eebd
Submitter: Zuul
Branch:    stable/18.11"
1802182,2018-11-26 16:06:10 UTC,"Reviewed:  https://review.openstack.org/616696
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=25200b5a1611280d5f05854eaeb2d00816428a9f
Submitter: Zuul
Branch:    master"
1802182,2018-11-26 18:30:08 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/620134"
1802182,2018-11-08 09:06:54 UTC,"Reviewed:  https://review.openstack.org/616357
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=41a046ba82435cde2e3524b529e425bdd42ab52f
Submitter: Zuul
Branch:    master"
1802182,2018-11-07 21:47:03 UTC,"This commit[0] removed the symlink from ""hooks/charmhelpers""  to ""../charmhelpers"""
1802182,2018-11-08 21:37:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616696"
1802182,2018-11-07 21:57:59 UTC,I'm adding a new task for neutron-gateway where we are seeing the same root cause for a different stack trace:
1802182,2018-11-07 21:50:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616357"
1802183,2018-11-07 21:48:33 UTC,Script started on 2018-11-07 09:47:45-0800
1802186,2020-09-09 10:12:58 UTC,"Alternatively, indicators for windows on other workspaces could be styled differently, like another color and/or shape."
1802188,2019-02-06 21:22:41 UTC,"This bug is fixed with commit 3a897fbd to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=3a897fbd"
1802188,2019-05-10 18:07:43 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1802193,2019-01-13 17:03:38 UTC,"2.1.6 is not effected but master build.
However there are some related error handling issues that can be fixed in 2.1.6 as well."
1802194,2018-11-07 23:06:30 UTC,/var/log/dist-upgrade/apt-term.log does not contain all the (error) messages what was on the screen during do-release-upgrade.
1802194,2018-11-07 23:28:05 UTC,"While the do-release-upgrade was running, (in a separate window) I queried the current locale. It was:"
1802203,2018-11-08 16:03:49 UTC,So I think a selinux policy would not be bad for that specific case - I've opened an issue against libpod here: https://github.com/containers/libpod/issues/1782
1802203,2018-11-16 11:42:32 UTC,"So, apparently we'll need to add some upgrade task somewhere just before the podman containers are started. Either a ""chcon -R"", or, cleaner:
semanage fcontext -a -t container_share_t ""/var/lib/kolla/config_files(/.*)?""
restorecon -R -v /var/lib/kolla"
1802203,2018-11-08 09:19:25 UTC,"Hey,"
1802203,2018-11-08 10:51:19 UTC,"Funky... apparently it's not an isolated bug I hit by chance:
http://logs.openstack.org/56/615956/5/check/tripleo-ci-centos-7-containerized-undercloud-upgrades/3443e6f/logs/undercloud/home/zuul/undercloud_upgrade.log.txt.gz#_2018-11-08_08_27_44"
1802203,2018-11-12 12:21:47 UTC,Back on that one.
1802203,2018-11-08 05:33:28 UTC,"Hey,"
1802206,2018-11-08 01:01:42 UTC,attaching partman after initial bug created
1802206,2020-03-07 15:49:41 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1802208,2019-09-27 16:15:12 UTC,"Stephan Bergmann committed a patch related to this issue.
It has been pushed to ""master"":"
1802208,2019-09-27 09:56:51 UTC,"(In reply to Stephan Bergmann from comment #11)

> It would have been useful to document exactly what failed.  At least with
> java-latest-openjdk-headless-13.0.0.33-1.rolling.fc31.x86_64, the
> testurlcheck program in configure.ac reports ""false"", but (when you convert
> the corresponding AC_MSG_ERROR into a AC_MSG_RESULT to not make configure
> fail) a full `make check screenshot` works fine for me.
"
1802208,2019-09-26 18:38:09 UTC,"(In reply to Jan-Marek Glogowski from comment #0)

> When OpenJDK tried to enforce stricter class path URL checks without
> previous announcement, things started to break left and right. This included
> failing LibreOffice JUnitTest checks, since the dependency classpath in our
> generated Jars doesn't pass the stricter URL checks and therefore is ignored.
"
1802208,2018-12-11 21:09:04 UTC,"Jan-Marek Glogowski committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1802208,2019-06-12 08:48:08 UTC,"(In reply to Alex Thurgood from comment #8)

> Would this bug also affect use of Oracle OpenJDK 12 when trying to call an
> external hsqldb.jar, e.g. when a user has what is known as a split database
> (no embedded hsqldb) ? If so, then it would be a regression for those users.
"
1802208,2019-06-12 08:40:07 UTC,"Would this bug also affect use of Oracle OpenJDK 12 when trying to call an external hsqldb.jar, e.g. when a user has what is known as a split database (no embedded hsqldb) ? If so, then it would be a regression for those users."
1802208,2019-04-26 12:22:05 UTC,"(In reply to Andreas Säger from comment #6)

> Is this the reason why
> https://adoptopenjdk.net is not recognized as a valid JDK?
"
1802208,2019-04-26 12:15:27 UTC,"I don't understand the details of this issue. Is this the reason why https://adoptopenjdk.net is not recognized as a valid JDK?
Is it true that someone works on it?
No need to file another issue?"
1802208,2019-01-14 21:16:47 UTC,"This appears to have been fixed in an OpenJDK update.
Successfully tested on xenial, bionic and disco."
1802208,2018-12-11 21:12:37 UTC,"These patches are no fixes, but will detect the failing JDK setup during configure as an early warning! They should be reverted after a real fix is merged."
1802208,2019-06-12 13:08:29 UTC,(In reply to Stephan Bergmann from comment #9)
1802208,2018-12-11 15:12:38 UTC,"Jan-Marek Glogowski committed a patch related to this issue.
It has been pushed to ""master"":"
1802208,2018-12-06 10:08:16 UTC,"quoting my 2018-11-12 10:34 comment at <https://gerrit.libreoffice.org/#/c/63118> ""Simplify and fix Java UNO API test makefiles"":"
1802208,2018-12-05 15:14:05 UTC,"When OpenJDK tried to enforce stricter class path URL checks without previous announcement, things started to break left and right. This included failing LibreOffice JUnitTest checks, since the dependency classpath in our generated Jars doesn't pass the stricter URL checks and therefore is ignored."
1802208,2018-11-19 09:40:08 UTC,That's because OpenJDK 11 in 18.10 doesn't have S8195874 (Improve jar specification adherence) yet.
1802208,2018-11-18 15:27:37 UTC,"This problem affected me after upgrading to Ubuntu 18.10. However, setting the Java version to use to OpenJDK 11 fixed this issue for me."
1802208,2018-11-16 17:13:27 UTC,"I rebuilt libreoffice 6.0.7 for bionic with the debian patch that sets jdk.net.URLClassPath.disableClassPathURLCheck to true, and verified that this was built against a version of the JDK that has the patch to honour that flag, but this hasn't fixed the issue."
1802208,2018-11-15 16:42:51 UTC,"cosmic and disco are not (yet) affected, because S8195874 (Improve jar specification adherence) was not backported to openjdk there."
1802208,2018-11-15 15:16:46 UTC,debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913641
1802208,2018-11-15 14:20:30 UTC,"Copying over reportbuilder.jar AND reportbuilderwizard.jar from the upstream build or from the snap ""fixes"" the issue."
1802208,2018-11-14 11:24:30 UTC,Libreoffice 5.1.6.2 on xenial (1:5.1.6~rc2-0ubuntu1~xenial4) is also affected.
1802208,2018-11-14 10:52:50 UTC,Neither the debs from libreoffice.org nor the snap package seem to be affected. Only the packages in the ubuntu repositories.
1802208,2018-11-14 10:27:31 UTC,"I can reliably reproduce the issue when creating a new report, closing it and double-clicking it to open it again."
1802208,2018-11-09 11:13:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802208,2018-12-06 10:40:57 UTC,"From reading the current URLClassPath.java code, it seem you can set ""jdk.net.URLClassPath.disableClassPathURLCheck"" to ""debug"", and the loader will print the ignored class path entries, which can help debugging."
1802212,2018-11-11 19:45:59 UTC,"We're updating the mailman3-web-charm to manage uwsgi.ini and to use the correct ""processes"" directive."
1802212,2019-02-20 16:45:53 UTC,I've just published cs:~mailman3-charmers/mailman3-web-19
1802214,2019-09-19 14:49:50 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1802214,2018-12-12 18:47:12 UTC,I wrote a quick test to confirm this is an issue in the websocket handler (and/or form).
1802214,2018-12-12 14:33:50 UTC,"It looks like if we save a VLAN with no name, the params we send to the websocket have the name set as an empty string. When the data comes back from the backend, the name is set to what it was previously."
1802214,2018-12-12 17:02:42 UTC,I'll see if I can reproduce this in the websocket tests. Thanks for taking a look!
1802218,2019-06-14 00:25:21 UTC,"marking as invalid as this is likely an issue wiht the ssh client you are using ro the ssh server in the guest.
the fact it works on linux but not windows/android suggest to me it might be related to the authentication methods
or encryption algothims and key types supproted in the client/server and is likely not related to openstack/nova"
1802222,2019-03-18 09:24:08 UTC,@Heitor
1802222,2019-06-12 15:03:22 UTC,"@Laurent, please open a new bug report to enable us to verify, triage and track this issue."
1802222,2019-06-12 13:51:36 UTC,"For a better readability, results units should be adapted :"
1802222,2019-04-30 18:58:36 UTC,"Fixed in revision 9f189ca71a7243587d3e83e0171862d224ed56fd
https://git.launchpad.net/kicad/patch/?id=9f189ca71a7243587d3e83e0171862d224ed56fd"
1802222,2019-04-30 18:58:13 UTC,Looks good Nabeel!  Thank you for your contribution to KiCad
1802222,2019-04-29 08:47:15 UTC,The attached patch contains updated licensing information in the SVG file.
1802222,2019-04-21 15:15:20 UTC,"@Nabeel-  Sorry for the delay on my end.  Between the holiday and KiCon coming this week, I've been too swamped to give your patch a good test.  I'll have time to test/merge after the 28th."
1802222,2019-04-20 18:51:02 UTC,"@Seth, have you been able to test the patch?"
1802222,2019-04-10 10:27:52 UTC,This patch includes changes suggested by Seth and Heitor.
1802222,2019-04-09 17:39:27 UTC,"@Nabeel-  As soon as you can rebase your patch and address Wayne's comment in #14, we'll be able to push your changes to the master tree."
1802222,2019-04-09 16:49:44 UTC,"Master is now open for 6.0, so it'd be great to get this wrapped up, rebased, and merged."
1802222,2019-03-18 15:57:12 UTC,@Nabel
1802222,2019-03-13 00:10:11 UTC,"This looks very useful!
The screenshot from comment #11 shows it is very simple to use."
1802222,2018-12-09 07:25:59 UTC,The patch is based on this online calculator [1]. The only difference in functionality is that the temperature rise parameter has been made variable.
1802222,2019-03-11 14:47:56 UTC,"@Nabeel,  I prefer the layout from comment #11.  It has a much cleaner appearance than your proposed layout changes (#12)."
1802222,2019-03-11 13:37:42 UTC,Hi Nabeel-
1802222,2019-03-11 11:59:56 UTC,"I am attaching a proposed layout, which I think looks more polished. Please see if this design would be better. I have grouped inputs and outputs by category. Via dimensions affect all results, so they are kept separate. This layout also makes the length of the two columns almost equal."
1802222,2019-03-11 11:14:43 UTC,"An updated patch is attached. It changes the following things from the previous patch:
- Added diagram
- Added 3 tooltips
- Removed horizontal lines between parameters and results
- Updated comments and references about calculations in code"
1802222,2018-12-10 18:08:58 UTC,"Okay, noted."
1802222,2018-12-10 17:31:48 UTC,"Oh, OK I see.  That is the maximum temperature rise that you are willing to accept.  We should probably have some tooltips for the fields."
1802222,2018-12-10 16:56:37 UTC,@Seth
1802222,2018-12-10 15:01:34 UTC,Sure thing (Last paragraph of #4)
1802222,2018-12-10 14:12:16 UTC,"@Seth, please hold off on merging this patch until v6.  We are in feature freeze for 5.1 and this is a new feature."
1802222,2018-12-10 13:38:52 UTC,@Nabeel-
1802222,2018-12-09 17:28:58 UTC,"Hi Seth,"
1802222,2018-12-09 15:32:45 UTC,Hi Nabeel-
1802222,2019-03-12 06:16:21 UTC,"@Seth and Wayne
Thank you for the feedback. I will update the patch as suggested."
1802227,2020-03-31 19:55:50 UTC,"@Drew - yeah, that could work, and solves both problems."
1802227,2020-03-31 19:41:06 UTC,"For those environments where recursive and authoritative bind servers are one in the same, could we solve this by expanding the get_serial() method to provide a specific exception if the returned query is non-authoritative such that if the response is non-authoritative, we consider the zone to be missing from the designate backend bind servers?"
1802227,2019-01-30 02:28:02 UTC,@Shi Yan I'm using designate in a private cloud and I can decide the zone's ns name. The code will match the unique ns name and return number '0' when doing the 'delete' action. I haven't publish my code for it is not universal.
1802227,2019-01-29 14:46:00 UTC,"Unfortunately, we need to be able to query the zone on the configured Bind servers to see if they have actually been deleted (rndc is not perfect, and sometimes we need to retry)."
1802227,2019-01-29 07:25:17 UTC,"@ephem haha yes, unfortunately, it is a similar situation for other OpenStack projects."
1802227,2019-01-29 00:49:11 UTC,"Hi,@Shi Yan.I have taken some workaround like recognize the customized email address, and it works well. Btw, there are many bugs with designate, haha..."
1802227,2019-01-24 23:44:38 UTC,I think I am meeting with the same issue here.
1802233,2019-06-26 15:33:48 UTC,"@cypressyew that sounds reasonable, the only word of caution here is we should not dismiss future bugs detected on this system as ""expected to fail"", because the problem is in the 3rd party BMC firmware *and not* in the Pnor FW or Power9 hardware."
1802233,2019-06-26 11:02:53 UTC,"From my point of view,
I think we should leave the test case as-is, it helped us to identify this firmware issue. And it might be able to catch another FW issues on other platforms in the future."
1802233,2019-06-24 14:11:50 UTC,IBM indicated that they do not have an ETA for a GA release of the BMC firmware with this fix. Would the kernel team be ok with working around this issue in the testcase by adding a .5 delay?
1802233,2019-06-17 19:20:53 UTC,I upgraded the firmware on tiselius (boston p9) and ran the testcase and it works as expected.
1802233,2019-06-12 22:20:11 UTC,I tried some test fw for the boston:
1802233,2019-06-10 18:13:11 UTC,Opened issue 1423 on this - unfortunately the boston openpower is closed.
1802233,2019-06-06 22:21:29 UTC,"Sorry did not realize that all the comments were not correctly mirrored over. A launchpad bug was reported by the Ubuntu kernel team as a result of their testing in the lab. We were not sure if this was a BMC issue, a hardware issue or kernel bug, so there is no github report as of now. If you think this is related to the BMC I can open a github bug. Also please tell us how to open bugs for BMC on Bostons."
1802233,2019-06-06 17:30:16 UTC,"------- Comment From <email address hidden> 2019-06-06 13:19 EDT-------
bugproxy,  I did see the command.  However, it was not clear if that what trigger the failure.  The details of the problem isn't clear."
1802233,2019-06-05 14:17:32 UTC,@youhour are you able to see the comments in the launchpad bug?
1802233,2019-06-04 20:50:20 UTC,"------- Comment From <email address hidden> 2019-06-04 16:47 EDT-------
is there issue associate with this problem?
How does one recreate this problem?"
1802233,2019-06-03 13:58:45 UTC,"Michael,"
1802233,2019-05-29 16:40:48 UTC,"Changing owner to ""bugproxy"" as the next steps are with IBM on the Witherspoon and Boston firmware."
1802233,2019-06-07 18:10:58 UTC,"------- Comment From <email address hidden> 2019-06-07 14:04 EDT-------
I don't know if this is a BMC issue either.  With your latest note,  I still do not understand the problem on Boston.  Whether this is a HWCLOCK setting issue or HWCLOCK setting is working but have a long delay...  Can you help clarify that?"
1802233,2019-05-21 18:21:11 UTC,"------- Comment From <email address hidden> 2019-05-21 11:58 EDT-------
(In reply to comment #24)

> Would a similar BMC firmware release from AMI fix this issue for Bostons
> systems? and is there an ETA for when that will be available to us.
"
1802233,2019-05-20 14:07:21 UTC,Would a similar BMC firmware release from AMI fix this issue for Bostons systems? and is there an ETA for when that will be available to us.
1802233,2019-05-17 19:30:31 UTC,"------- Comment From <email address hidden> 2019-05-17 15:22 EDT-------
We had bugs reported in past also about hwclock not working on P9.
LTC 155321 is one of such bugs. Its likely openBMC issue here.
As per latest comment in bug  155321"
1802233,2019-05-15 15:12:51 UTC,"-- Witherspoon firmware --
Server: IBM-witherspoon-OP9-v2.2-9.56
BMC: ibm-v2.3-476-g2d622cb-r30-0-g862e40a"
1802233,2019-05-15 14:52:18 UTC,On the Witherspoon the hwclock does not seem to set at all.
1802233,2019-05-22 01:49:59 UTC,"------- Comment From <email address hidden> 2019-05-21 21:46 EDT-------
(In reply to comment #25)

> (In reply to comment #24)
> > Would a similar BMC firmware release from AMI fix this issue for Bostons
> > systems? and is there an ETA for when that will be available to us.
>
>
> Hi Stewart,
>
> Please let know if a BMC firmware release exists that fixes this issue on
> Boston ? This is similar issue reported in LTC bug 155321 for Witherspoon.
"
1802233,2019-05-14 04:12:46 UTC,"Tested with the latest mainline kernel on Baltar:
ubuntu@baltar:~$ uname -a
Linux baltar 5.1.1-050101-generic #201905110631 SMP Sat May 11 07:16:36 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux"
1802233,2019-05-13 15:26:41 UTC,So looks like it is slow to sync with RTC.
1802233,2019-05-13 15:14:53 UTC,If you use it in verbose mode it works. It could be that it is slow to read from the rtc and the verbose mode just enough time to sync?
1802233,2019-05-13 14:37:29 UTC,"Next step is for the kernel team to assess whether this is a test case issue, or a real kernel bug."
1802233,2019-05-10 08:34:15 UTC,"This issue could be found on node ""dradis"" as well."
1802233,2018-11-08 08:27:24 UTC,"Spotted on 4.15 Xenial, one of two power8 boxes failed with:
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock is 'Wed Oct 20 04:09:59 2004 .840175 seconds'"
1802233,2018-11-08 06:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802256,2019-08-21 17:19:18 UTC,Some discussion of this in https://forum.snapcraft.io/t/go-modules/7265/7
1802260,2019-01-11 14:46:31 UTC,Note the previous comment. This bug report will not automatically be updated because the deb-to-snap related code is no source package in Launchpad's mind.
1802260,2018-12-06 14:14:31 UTC,"https://lists.ubuntu.com/archives/kernel-team/2018-November/096856.html
https://lists.ubuntu.com/archives/kernel-team/2018-November/096857.html
https://lists.ubuntu.com/archives/kernel-team/2018-November/096858.html"
1802260,2018-11-09 06:03:21 UTC,applied this patch against lp:~ubuntu-kernel/ubuntu/+source/linux-snap/+git/bionic then the issue is gone.
1802260,2018-11-09 01:10:03 UTC,The fix would be similar with this bug #1794279
1802260,2018-11-08 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802264,2018-11-08 12:15:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802269,2020-12-01 05:55:04 UTC,"Try installing lua-posix, which is one of the prerequisites of Lmod, as shown in the documentation:
https://lmod.readthedocs.io/en/latest/030_installing.html"
1802275,2019-02-02 07:14:40 UTC,"In my opinion,there is no need to config 'port_forwarding' in 'service_plugins ',for ovn is the l3 plugin for neutron.
you can try it  and paste more log."
1802281,2018-11-08 10:48:35 UTC,apport information
1802281,2018-11-08 10:49:53 UTC,Seems to be related to this report: 1792167
1802281,2018-11-08 10:48:33 UTC,apport information
1802281,2018-11-08 10:47:23 UTC,Xrandr attached
1802281,2018-11-08 10:48:34 UTC,apport information
1802283,2018-11-23 09:47:22 UTC,"Another day, another freeze. Even with the new firmware installed. It ofen occurs during video chats. I wonder if CPU usage has something to do with it."
1802283,2018-11-24 15:45:09 UTC,It freezed again. This time without an external monitor connected. The system was running for quite some time with suspends/resumes in between and I ran a pytest test suite. Directly after the tests being finished the system didn't respond to any keyboard input whatsoever. Only a reboot via the power button helped.
1802283,2018-11-27 05:04:54 UTC,"Use ""journalctl -b -1"" to get log from last boot (the crashed one)."
1802283,2018-12-05 09:27:00 UTC,Today I resumed from suspend and five minutes later it froze again.
1802283,2018-12-07 12:52:14 UTC,"So far today, the laptop hasn't crashed completely but Firefox and Thundebird are crashing constantly making it impossible to get work done. As soon as I restore the crashed Firefox session the whole program crashes again."
1802283,2018-12-10 23:37:03 UTC,It happened again.
1802283,2018-12-11 06:50:08 UTC,"Please do the following:
- Memory test.
- Use a Ubuntu Live USB to run fsck on your rootfs."
1802283,2019-03-07 07:25:58 UTC,So seems like we can close this bug?
1802283,2018-11-22 11:09:36 UTC,I just ran `sudo fwupdmgr` to see if there have been firmware updates and – in deed – they released update 0.1.34 today:
1802283,2019-03-07 08:31:26 UTC,Yes
1802283,2019-03-22 10:44:33 UTC,After a long time of no system freeze it happened again a few minutes ago:
1802283,2019-03-22 11:00:07 UTC,This change was made by a bot.
1802283,2019-03-22 15:46:36 UTC,I think it's different. Seems to be a gnome-shell issue according to the very limited log.
1802283,2019-03-22 16:40:32 UTC,"Okay. Thanks for looking into it. Feel free to close the issue, please."
1802283,2020-02-18 12:18:50 UTC,"I also experience system freezes, usually after resume from suspend on X1 Carbon 6th. It happens on 4.18.0-15 and 5.3.0-40 kernels. I am running with no issues for many months on 4.15, currently 4.15.0-88-generic."
1802283,2019-01-23 08:25:01 UTC,I did a memory test with memtest86 that ran around 5h through the night and it passed 48/48 tests with 0 defective bits.
1802283,2018-11-22 10:59:26 UTC,Today it already crashed twice in a very short period:
1802283,2018-12-04 10:52:24 UTC,I have the feeling that chances are higher that the system freezes when I use suspend. When I shutdown and boot I can go a few days even without a system crash.
1802283,2018-11-19 08:45:45 UTC,"log showed that you are connected with a dock station (Intel light ridge), right?
No kernel panic info in log. It is hard to say what happened."
1802283,2018-11-08 11:15:30 UTC,Snippet of /var/log/syslog from when I started my laptop until the moment when it froze.
1802283,2018-11-08 11:30:07 UTC,This change was made by a bot.
1802283,2018-11-08 12:52:27 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1802283,2018-11-19 20:41:54 UTC,Thank you for taking your time with this issue.
1802283,2018-11-08 14:45:43 UTC,"Thank you for your help, Christian. I added the last boot log as you requested and will try the 4.19 kernel."
1802283,2018-11-08 15:29:05 UTC,"Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1802283,2018-11-09 08:57:41 UTC,1. There are no specific steps that I took. The last time the system froze I was just loading up a virtual machine in VirtualBox. A day before that I was doing a video chat over https://talky.io with Firefox 64.
1802283,2018-11-12 10:16:03 UTC,"After my laptop worked fine yesterday for the whole day, it crashed again a few minutes ago. I have been using it for about 1.5h and the open programs where gnome-shell, thunderbird, firefox and gnome-terminal. It froze while browsing gitlab.com. It didn't respond to MagicSysRq keys."
1802283,2018-11-08 13:06:25 UTC,"Please reproduce the problem, do a hard reset and then run this command:"
1802283,2018-11-13 04:55:21 UTC,Does the crash only happen after suspend (S3) the system?
1802283,2018-11-13 07:22:43 UTC,"No, it also happens after cold boot. But maybe the external monitor plays a
role. I think i have yet to experience a crash when no external monitor is
connected."
1802283,2018-11-13 14:17:36 UTC,"So far, no hard crash today. But I'm experiencing lots of crashing tabs in Firefox today. But not only the tabs; Thunderbird and Firefox crashed completely as well and needed a restart. And once, my gnome-session was killed and I was put back to gdm and needed to log in again."
1802283,2018-11-15 05:33:34 UTC,Does disabling zswap solve the issue in #13?
1802283,2018-11-19 07:10:04 UTC,Does the Firefox crashing only happens when the system is docked?
1802283,2018-11-15 10:51:28 UTC,A few minutes ago Firefox crashed again several times in a row. This is the tail of /var/log/kern.log right now (lots of times):
1802283,2018-11-17 15:16:19 UTC,Another system crash happend a few moments ago. This time I noticed that dmesg reports hardware errors:
1802283,2018-11-12 10:21:04 UTC,"The latest crash happened on the 4.19 mainline kernel by the way. When I worked on my laptop yesterday, it wasn't attached to the power adapter. When it crashed today it was charging."
1802285,2019-07-18 22:32:35 UTC,"HI,"
1802285,2019-09-17 04:17:41 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1802286,2018-11-09 05:57:40 UTC,"need to unlock the setup as it's sanity testbed.
logs are copied @/cs-shared/bugs/1802286"
1802292,2018-11-09 09:20:32 UTC,"A fixed version 3.2.7a-2 was just uploaded to the Debian archive, so it make it into Ubuntu soon."
1802292,2021-01-30 12:20:40 UTC,Fixed in 3.2.7a-2 (available since focal)
1802292,2018-11-08 13:00:56 UTC,I just forwarded the issue to the upstream tracker: https://sourceforge.net/p/mcj/tickets/35/
1802295,2020-02-21 01:14:10 UTC,Still reproducible on current git-ubuntu:
1802297,2018-11-08 13:17:29 UTC,"This my mistake. The full stop at the end of ""HEAD as commit 4af2db7da81fd12b958966faee2c2aff6605a4f9."" prevents double click and middle click paste. Let's drop that part."
1802298,2020-07-14 21:44:38 UTC,"Change abandoned by Sergii Golovatiuk (<email address hidden>) on branch: master
Review: https://review.opendev.org/681971"
1802298,2020-08-06 21:55:33 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/681930
Reason: This review is > 90 days without comment, and failed Zuul the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1802298,2020-08-06 21:55:07 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1802298,2019-09-13 06:42:41 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/681971"
1802298,2020-08-06 21:55:39 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/681934
Reason: This review is > 90 days without comment, and failed Zuul the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1802298,2019-09-12 21:11:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/681930"
1802298,2018-11-08 13:21:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616542"
1802298,2019-02-19 13:10:40 UTC,Still working on this?
1802298,2019-09-12 21:27:16 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/681934"
1802298,2019-06-03 20:31:45 UTC,This option was removed https://bugs.launchpad.net/tripleo/+bug/1824781 however this still impacts older versions (queens/rocky)
1802298,2019-04-23 00:32:41 UTC,"Change abandoned by Radoslaw Smigielski (<email address hidden>) on branch: master
Review: https://review.opendev.org/616542"
1802299,2019-08-15 19:03:46 UTC,"Change abandoned by Andrey Pavlov (<email address hidden>) on branch: master
Review: https://review.opendev.org/573781
Reason: too old"
1802300,2019-05-30 00:40:27 UTC,I take it this error message can be ignored when it comes up?  Or does it indicate an actual fault that the user needs to deal with?
1802300,2019-06-17 17:13:57 UTC,"I ran into this again and dug into it further.  Both for my previous run-in and again in this one, it was a bit of a red herring and the actual problem was something different."
1802301,2019-02-13 23:54:45 UTC,Enter year and year out and Ubuntu continues with startup errors.
1802303,2019-08-07 20:25:36 UTC,"Encountered this error as well. For my case, if no services (svc) is returned by list comprehension, the error is thrown. This is occurring when there's a host in a host aggregate but no corresponding OS service running on it."
1802305,2018-12-12 11:24:07 UTC,Looks like upstream used to store the password as plaintext but changed this a while ago to instead store it in the keyring - https://github.com/GNOME/gnome-boxes/commit/ac552985647ebb6d7ee924cd77f0b93df44b4ff0
1802305,2019-03-07 16:08:55 UTC,"Bug report has been added to Gnome's official ""Gitlab"" bug tracker for ""gnome-boxes.
https://gitlab.gnome.org/GNOME/gnome-boxes/issues/317"
1802305,2019-03-07 16:23:13 UTC,"""auto-csoriano <email address hidden>"" added to Launchpad bug report."
1802307,2018-11-15 17:03:54 UTC,"I agree with the hesitation around ""proceed with warnings""; if someone wants to deploy KVM on something other than Bionic, I would prefer an active mechanism, such as requiring the user to  acknowledge their choice of trying an unsupported release. (From the API we do this occasionally with a `force=true` parameter.) The use case is ""we are having an issue and we want to see if it happens on release X, but we don't want to change the MAAS code""."
1802307,2019-09-19 14:49:53 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1802307,2018-11-09 17:27:15 UTC,"More generally, we should consider each custom action on deployment (such as deploying a MAAS-managed KVM host or a rack controller) to be associated with a specific set of supported images."
1802307,2018-11-15 14:31:34 UTC,That's an excellent idea to generalise this.
1802310,2018-11-11 22:21:14 UTC,Agree.  I think failure-timeout as a new charm config option would make sense.  We should have more conversation though about the default value.
1802310,2018-12-12 14:58:07 UTC,Here is a patch for setting failure-timeout to 3 minutes by default: https://review.openstack.org/#/c/624720/
1802310,2019-06-03 08:26:18 UTC,"Reviewed:  https://review.opendev.org/624720
Committed: https://git.openstack.org/cgit/openstack/charm-hacluster/commit/?id=e28f8a9adc9f8ac1b3c1462d4f0724a4ddbc2257
Submitter: Zuul
Branch:    master"
1802316,2018-11-08 18:52:16 UTC,"> given a list of commands specified in a ""runcmd"" list, if a command fails
> i think it should prevent the next commands from running and mark the
> execution as failed
"
1802316,2018-11-19 08:46:50 UTC,"that's really a shame :(
isn't there a way to optionally have this behavior ? like with a boolean which would default to false for backward compatibility, but set to true, would behave like described above ?"
1802316,2019-07-18 22:31:15 UTC,"Hi,"
1802320,2018-12-03 15:02:48 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1101.109
1802321,2018-11-27 03:07:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802321,2018-12-18 06:15:53 UTC,This issue impacted me as well on a fresh Ubuntu 18.04 install. I encountered this when I attempted to install ubuntu-restricted-extras.
1802321,2019-01-31 22:24:05 UTC,"I was impacted with semi-new install 18.04.1
It was probably always there but I just now saw the error.
The workaround above has stopped the broken packages printout."
1802321,2019-05-08 14:01:58 UTC,Still present in 19.04
1802321,2019-08-13 21:11:17 UTC,"Recently noticed during a software update in 19.04. Like previous commenters, the work-around provided (sudo dpkg-reconfigure libdvd-pkg) corrected the issue. Thanks for this...broken packages do not inspire confidence."
1802327,2020-09-11 08:35:09 UTC,"Any update on this? In our case we use a separate store instead of a private snap. Same result, can't build snaps with ""build-snaps"" or ""stage-snaps"" requirements."
1802327,2018-11-20 16:10:13 UTC,"This bug is also affecting BootStack's operations. We want to share a set of tools via snaps (previously shared via a private ppa), but copying the snap around is not maintainable."
1802330,2018-11-08 16:22:33 UTC,"Note that I was able to successfully backport the Bionic 0.3.11 version into Xenial with one change to the build dependencies (a very minor change) in a PPA, and this works without issues (and is not affected by this bug)."
1802330,2018-11-08 16:24:09 UTC,"Correction, the backported version was using Disco as a base, however in this case the actual versions of partclone are still the same, the only difference is the version string (as the changes in Bionic, COsmic, and Disco are just no-change rebuilds as far as I can tell)"
1802330,2018-11-08 17:03:28 UTC,"For reference, current versions of partclone as reported by rmadison:"
1802334,2019-02-04 16:34:48 UTC,"Confirm that this needs doing, the beta version installed in Bionic (18.04) is flawed, for instance running for orientation (--psm 0) gives segmentation fault. Installing stable 4.0.0 (using ppa https://launchpad.net/~alex-p/+archive/ubuntu/tesseract-ocr) gets rid of this problem."
1802334,2019-10-03 17:04:30 UTC,This is done.
1802337,2018-11-15 17:28:52 UTC,I’ve been misled by that option for all these years.
1802337,2019-02-14 16:29:49 UTC,See also #1798992
1802345,2019-01-23 18:52:08 UTC,Here's the part recipe that fixes the problem:
1802345,2019-07-04 13:58:44 UTC,"Thanks, that's much nicer that having to export it outside of snapcraft!"
1802345,2019-01-10 12:39:50 UTC,"This is a bigger issue when building with VMs in snapcraft 3, as there's no way to export C_INCLUDE_PATH."
1802345,2019-01-23 17:49:46 UTC,"> This is a bigger issue when building with VMs in snapcraft 3, as there's no way to export C_INCLUDE_PATH.
"
1802355,2018-11-08 23:02:16 UTC,I've configured our test runs to turn debug logging on for networkd and resolvd.
1802363,2018-11-09 04:54:35 UTC,Have a look there: https://bugs.launchpad.net/kolla/+bug/1797448
1802363,2019-07-23 17:30:40 UTC,In my deploy whe I try to attach a volume to a contanier i get
1802363,2019-08-09 08:07:31 UTC,Do you have logs from cinder-volume?
1802369,2018-11-20 04:42:50 UTC,"Reviewed:  https://review.openstack.org/617119
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=593c04d10d9d67cc6f864ff37416951dd28584f5
Submitter: Zuul
Branch:    master"
1802369,2019-01-10 00:00:12 UTC,"Reviewed:  https://review.openstack.org/625332
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=14bc0d940841de31f055fa3170289e0fa671b7bb
Submitter: Zuul
Branch:    master"
1802369,2019-01-04 10:53:14 UTC,This patch https://review.openstack.org/#/c/625332/ to neutron-lib should fix such issues in proper way :)
1802369,2018-12-21 16:20:58 UTC,This issue was fixed in the openstack/neutron 14.0.0.0b1 development milestone.
1802369,2018-12-14 19:08:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625332"
1802369,2018-11-15 02:06:55 UTC,"Reviewed:  https://review.openstack.org/617979
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=e83edbc171a33fa5f495b5b9fe483988419f2bfd
Submitter: Zuul
Branch:    stable/rocky"
1802369,2018-11-08 18:51:22 UTC,Failures:
1802369,2018-11-13 23:40:48 UTC,"Reviewed:  https://review.openstack.org/617307
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=605ad27f053a1ef9ffb3601c6023987ddb6a22e1
Submitter: Zuul
Branch:    master"
1802369,2018-11-12 12:28:52 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: master
Review: https://review.openstack.org/616668
Reason: https://review.openstack.org/#/c/617307/"
1802369,2018-11-10 14:58:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617119"
1802369,2018-11-10 11:27:43 UTC,"Yes, this is what I did here for networking-ovn:  https://review.openstack.org/#/c/616668/"
1802369,2018-11-08 19:27:25 UTC,"When importing that module, these event listeners are created:"
1802369,2019-09-11 18:17:35 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/681568"
1802369,2018-11-14 15:11:36 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/617979"
1802369,2019-09-22 12:55:42 UTC,"Reviewed:  https://review.opendev.org/681568
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=49e6e141f254762f63ba8347ead84e28eefca838
Submitter: Zuul
Branch:    stable/queens"
1802369,2018-11-08 19:15:52 UTC,There's tons of errors like:
1802369,2018-11-09 23:28:13 UTC,"So maybe we should import neutron.db.api module in neutron/common/utils.py again (with ""noqa"" to make pep8 happy).
Or any other, better solutions?"
1802374,2019-05-16 18:36:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802375,2018-11-17 15:36:43 UTC,"Ok, I disabled systemd-resolved on my machine, following ..."
1802375,2018-11-17 15:01:48 UTC,"After more web searching I found https://wiki.archlinux.org/index.php/Avahi#Hostname_resolution, stating the systemd-resolved does interfere with avahi mDNS ...
So I turned off systemd-resolved for a test and a pending job got printed immediately."
1802378,2018-11-08 23:55:14 UTC,*** This is an automated message ***
1802379,2018-11-13 23:18:35 UTC,"After investigating this, I think this is a change in how the sudoers file works in Xenial vs. Bionic. Thus, we should backport this to MAAS 2.4 as well."
1802391,2018-11-09 19:53:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802398,2018-12-16 09:58:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802402,2018-11-13 08:30:14 UTC,"Yeah, I rather did it by my self, already installed everything back and then
I fixed the issue by myself."
1802402,2018-11-13 01:45:23 UTC,"Sorry, that suggestion was based on the package not being in Ubuntu 18.10. I did not realize it is a required package in 18.04."
1802402,2018-11-09 02:09:31 UTC,Please run this command:
1802402,2018-11-12 02:20:31 UTC,Please try this:
1802402,2018-11-09 09:40:17 UTC,"---------- Původní e-mail ----------
Od: Daniel van Vugt <email address hidden>
Komu: <email address hidden>
Datum: 9. 11. 2018 3:19:11
Předmět: [Bug 1802402] Re: [UX430UNR, Realtek ALC294, Black Headphone Out,
Left] No sound
""Please run this command:"
1802402,2018-11-12 19:31:08 UTC,"Hello,"
1802406,2018-11-12 19:51:43 UTC,"Patch for ""17.10_STABLE"" branch: https://reviews.mahara.org/9307"
1802406,2018-11-12 19:51:53 UTC,"Reviewed:  https://reviews.mahara.org/9307
Committed: https://git.mahara.org/mahara/mahara/commit/4ab3cf830e74d144511ad0c22939b04b6bd82fcb
Submitter: Robert Lyon (<email address hidden>)
Branch:    17.10_STABLE"
1802406,2018-11-12 19:51:38 UTC,"Reviewed:  https://reviews.mahara.org/9306
Committed: https://git.mahara.org/mahara/mahara/commit/1613c886aea4a3efb584290d9c264e3ee00813c8
Submitter: Robert Lyon (<email address hidden>)
Branch:    18.04_STABLE"
1802406,2018-11-12 19:51:29 UTC,"Patch for ""18.04_STABLE"" branch: https://reviews.mahara.org/9306"
1802406,2018-11-12 19:51:23 UTC,"Reviewed:  https://reviews.mahara.org/9305
Committed: https://git.mahara.org/mahara/mahara/commit/cea4ffe05334cd8e631750eaaa22ca755efc0d96
Submitter: Robert Lyon (<email address hidden>)
Branch:    18.10_STABLE"
1802406,2018-11-12 19:49:33 UTC,"Patch for ""18.10_STABLE"" branch: https://reviews.mahara.org/9305"
1802406,2018-11-12 18:28:55 UTC,"Reviewed:  https://reviews.mahara.org/9297
Committed: https://git.mahara.org/mahara/mahara/commit/e02653c34117ef71a908ef3191fe972cba426464
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1802406,2018-11-08 22:31:23 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9297"
1802417,2018-11-09 00:01:57 UTC,The workaround for using master python-senlinclient is to install openstacksdk 0.17.2
1802417,2019-01-15 17:53:12 UTC,Fixed in https://review.openstack.org/#/c/624528/
1802417,2019-02-28 14:17:41 UTC,This issue was fixed in the openstack/python-senlinclient 1.10.0 release.
1802421,2019-02-04 08:47:55 UTC,This bug was fixed in the package linux - 4.4.0-142.168
1802421,2019-01-23 03:20:42 UTC,The user has verified that the -proposed kernel resolves their issue.
1802421,2019-01-17 14:22:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1802424,2020-06-11 01:14:47 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/735026"
1802424,2020-06-09 22:06:25 UTC,"Reviewed:  https://review.opendev.org/733427
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=3cbceccc4061a8931d682285419c716eafafb6cd
Submitter: Zuul
Branch:    stable/ussuri"
1802424,2020-06-04 03:03:07 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/733427"
1802424,2020-05-31 22:43:56 UTC,"Reviewed:  https://review.opendev.org/726514
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=853d4fbceb1fffbe4fe4ae91846ac8531aa5d516
Submitter: Zuul
Branch:    master"
1802424,2020-05-09 10:38:21 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/726514"
1802424,2019-03-08 15:53:32 UTC,"There were some additional temporary files in the first commit. So I squashed
it with the next correct commit. The first 'Change' was abandoned, and I
deleted the entire branch to begin working from the scratch."
1802424,2019-03-08 02:51:54 UTC,"Change abandoned by Yajushi Srivastava (<email address hidden>) on branch: master
Review: https://review.openstack.org/641418
Reason: Failed to recover change and files. Refer to #641666 for a clean patch."
1802424,2019-03-06 17:47:18 UTC,"Change abandoned by Goutham Pacha Ravi (<email address hidden>) on branch: master
Review: https://review.openstack.org/641379
Reason: I'm assuming this change was submitted in error. Thank you for your contribution to OpenStack/Manila, I take it the real review should occur https://review.openstack.org/#/c/641418/"
1802424,2019-03-07 13:28:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641666"
1802424,2019-03-07 13:30:30 UTC,"Change abandoned by Yajushi Srivastava (<email address hidden>) on branch: master
Review: https://review.openstack.org/641418
Reason: Patch with new Change-Id submitted for review."
1802424,2018-11-09 01:23:21 UTC,Here are instructions on how to add a user message: https://docs.openstack.org/manila/latest/contributor/user_messages.html
1802424,2019-03-04 06:24:41 UTC,I am an Outreachy Applicant.
1802424,2019-03-06 12:07:11 UTC,"Looks good Yajushi, please submit a patch set following the contribution workflow [0] so other manila contributors can review your work. Thanks!"
1802424,2019-03-06 14:17:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641379"
1802424,2019-03-06 15:30:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641418"
1802424,2019-03-07 13:25:16 UTC,"I messed up my development environment a little. Will be submitting a patch with new Change-Id, as I can't seem to find a way to continue with the existing one."
1802428,2018-11-09 16:56:28 UTC,Sounds related to this:
1802431,2018-11-19 19:21:15 UTC,Tried a PID loop.
1802431,2019-06-02 07:53:26 UTC,"I pretty much fixed this in a recent revision, but I think it may still be possible to overflow sometimes.  I'm not sure; it still needs more testing on a super-overpowered hot-rod host.  But on almost every host I've tried so far, the new thermal code gets nearly-optimal results."
1802438,2019-03-22 01:24:14 UTC,This issue was fixed in the openstack/neutron-lbaas 14.0.0.0rc1 release candidate.
1802438,2018-11-21 23:52:58 UTC,"btw, i'm not necessarily against the change in question.
my claim is that it should be done differently.
that is, either:
1. avoid affecting the driver api
or
2. coordinate with driver maintainers, including out of tree ones."
1802438,2018-11-21 23:30:56 UTC,"Rodolfo,"
1802438,2018-11-21 09:57:45 UTC,Hello Yamamoto:
1802438,2018-11-12 03:41:06 UTC,Hello Yamamoto:
1802438,2018-11-12 17:34:56 UTC,"Rodolfo,"
1802438,2018-11-11 23:52:09 UTC,Hello Yamamoto:
1802438,2018-11-20 14:04:57 UTC,"Rodolfo,"
1802438,2018-11-09 13:22:19 UTC,https://review.openstack.org/#/c/616763/
1802439,2019-02-14 03:44:50 UTC,"As of now, I have just finish create my own script to all doing BOM back and forth from XML, or SCH to/from CSV BOM file. So this may not be a big of a deal for me. Here is the bom2csv and bom2sch scripts if some one have the need: https://github.com/nhatkhai/kicad_scripts/tree/master/bom_plugins"
1802439,2019-05-30 05:43:00 UTC,"The field editor in eeschema can be used as the target (or sorce) of copy paste operations. For example from any spredsheet program into the field editor. (Can even copy multiple cells at once. I tested copy paste of a full table to libre office calc, changed stuff including line ordering and then copied the changes back. So this could be an easy alternative to using scripting.)"
1802449,2018-11-10 00:49:59 UTC,contrail-flows also doesn't work.
1802454,2019-10-17 08:21:50 UTC,"Test result on Trusty:
 startup='Sat Oct 5 00:28:40 2019'
 tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0'
 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
 mke2fs 1.42.9 (4-Feb-2014)
 tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
 fanotify10.c:331: INFO: Test #0: ignore mount events created on a specific file
 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8205 fd=30
 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8205 fd=30
 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8205 fd=30
 fanotify10.c:398: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:331: INFO: Test #1: ignore exec mount events created on a specific file
 fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
 fanotify10.c:331: INFO: Test #2: don't ignore mount events created on another file
 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30
 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30
 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30
 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30
 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30
 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30
 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30
 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30
 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30
 fanotify10.c:331: INFO: Test #3: don't ignore exec mount events created on another file
 fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
 fanotify10.c:331: INFO: Test #4: ignore inode events created on a specific mount point
 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8207 fd=30
 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8207 fd=30
 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8207 fd=30
 fanotify10.c:392: FAIL: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
 fanotify10.c:392: FAIL: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
 fanotify10.c:392: FAIL: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
 fanotify10.c:392: FAIL: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
 fanotify10.c:392: FAIL: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
 fanotify10.c:392: FAIL: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
 fanotify10.c:331: INFO: Test #5: ignore exec inode events created on a specific mount point
 fanotify10...."
1802454,2019-01-22 03:58:12 UTC,Passed with Bionic SRU.
1802454,2020-11-17 04:34:08 UTC,Still visible in Xenial 4.4.0-1118.132 AWS c5.metal
1802454,2019-07-10 09:47:36 UTC,"For Xenial 4.4, if you run this test after a clean reboot you will get:
<<test_output>>>
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0'
incrementing stop
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.42.13 (17-May-2015)
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:331: INFO: Test #0: ignore mount events created on a specific file
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3049 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3049 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3049 fd=15
fanotify10.c:398: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:398: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:398: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:398: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:398: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:398: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:331: INFO: Test #1: ignore exec mount events created on a specific file
fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
fanotify10.c:331: INFO: Test #2: don't ignore mount events created on another file
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15
fanotify10.c:331: INFO: Test #3: don't ignore exec mount events created on another file
fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel?
fanotify10.c:331: INFO: Test #4: ignore inode events created on a specific mount point
fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3051 fd=15
fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3051 fd=15
fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3051 fd=15
fanotify10.c:392: FAIL: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
fanotify10.c:392: FAIL: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
fanotify10.c:392: FAIL: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
fanotify10.c:392: FAIL: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
fanotify10.c:392: FAIL: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
fanotify10.c:392: FAIL: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event
fanotify10.c:331: INFO: Test #5: ignore exec inode events created on a specific mount point
..."
1802454,2020-07-27 06:47:29 UTC,"For the failure of test case #16 on Focal, please check bug 1882717"
1802454,2019-03-27 06:44:39 UTC,"For Trusty-4.4 test timeouted.
 startup='Fri Mar 22 02:07:25 2019'
 tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0'
 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
 mke2fs 1.42.9 (4-Feb-2014)
 tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
 fanotify10.c:331: INFO: Test #0: ignore mount events created on a specific file
 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=10758 fd=30
 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=10758 fd=30
 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=10758 fd=30
 fanotify10.c:398: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 fanotify10.c:398: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Cannot kill test processes!
 Congratulation, likely test hit a kernel bug.
 Exitting uncleanly..."
1802454,2018-11-20 04:11:44 UTC,"For cosmic, it's been fixed in stable update, bug 1801931"
1802454,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1802454,2019-01-15 10:37:46 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1802454,2018-11-09 07:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802454,2018-11-09 06:50:13 UTC,Can be reproduced on different kernels.
1802454,2019-03-20 08:11:13 UTC,"For cosmic it's been fixed in stable updates:
9aa2a0a66f6f5f5b5d12e9cbd7caff7385cd6179"
1802457,2018-11-09 11:49:58 UTC,"not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1802457,2018-11-10 08:33:40 UTC,"Attached.
Ubuntu 18.04.1 LTS
When I double click an svg, this inkscape opens:
0.92.3 (2405546, 2018-03-11)"
1802457,2018-11-10 11:00:17 UTC,"thanks for the file.
On Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
and also Inkscape 0.92.3 (0612fd7, 2018-10-23)
I am unable to reproduce the crash. The printing marks are shown in the attached file."
1802457,2020-03-18 20:39:55 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1802465,2018-11-24 09:49:20 UTC,"In my case the problem is quite subtle.
Nearly every time we send the key strokes, the guest os keeps receiving space or tab or new line character. And ending part of the text is truncated, where the truncated part is fixed depending on the keystrokes we are sending.
Additionally, the keystrokes are mis-ordered at a higher frequency than 1 out of a few hundreds as you said."
1802466,2018-11-09 08:04:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/616847"
1802466,2019-07-29 20:40:19 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/616847
Reason: no longer relevant, we're using journald"
1802468,2020-02-28 03:23:37 UTC,"Change abandoned by Yong Huang (<email address hidden>) on branch: master
Review: https://review.opendev.org/616125"
1802469,2018-11-14 07:28:54 UTC,"Today it happened again and I have attached a screenshot here.
As said, after a ctrl-alt-delete the system booted ok and I can see no sign of the failed disk in the logs."
1802474,2019-05-10 13:36:38 UTC,"On Disco the result is a bit different:
  libbpf: Error loading ELF section .BTF: -22. Ignored and continue.
  libbpf: object file doesn't contain bpf program"
1802474,2018-11-09 11:46:05 UTC,Can be found on Cosmic 4.18 as well.
1802474,2019-05-09 10:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802479,2020-03-07 15:50:25 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1802480,2018-11-09 09:18:28 UTC,"Commit fdb06c787b34fd397f28f515105627307d615025 title is ""xfrm: reset transport header back to network header after all input transforms ahave been applied"""
1802480,2018-11-09 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802480,2018-11-09 09:32:59 UTC,"Sorry, currently, all hosts are running a mainline kernel (4.18.17)."
1802480,2018-11-10 09:54:17 UTC,"Nevermind, 4.18.17 is not enough to fix the crash. Currently testing with 4.19.1."
1802480,2018-11-16 19:21:23 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1802480,2018-11-17 05:52:19 UTC,This happens with 4.20-rc2. This is fixed by the patch referenced in this thread:
1802480,2019-03-27 15:26:16 UTC,"The fix is available in commit:
commit 0152eee6fc3b84298bb6a79961961734e8afa5b8
Author: Steffen Klassert <email address hidden>
Date:   Thu Nov 22 07:26:24 2018 +0100"
1802480,2019-03-28 06:27:56 UTC,"The commit is already in upstream stable tree, so it will be included to future Ubuntu kernel release."
1802481,2018-12-13 17:21:12 UTC,"I really don’t know what to suggest here. As you mentioned, this used to work. If you are only using LUKS for swap, maybe you could just remove it from crypttab and run the appropriate commands manually in rc.local or a custom systemd unit."
1802481,2018-12-10 18:06:56 UTC,"If the pool is on top of LUKS (a relatively common configuration when ZFS and cryptsetup are both being used), then you'd need cryptsetup first. My advice is that you should either stop encrypting swap or start encrypting the whole pool. Hopefully in another (Ubuntu) release or two, we'll have native ZFS encryption and this whole things Just Works."
1802481,2018-12-13 14:05:32 UTC,"Hey Richard,
OK I understand why this order has to be kept dunring boot amd I understand it is a personal problem and this bug can be closed."
1802481,2018-12-07 20:05:11 UTC,"Try adding initramfs as an option in /etc/crypttab. That's the approach I use when putting the whole pool on a LUKS device, and is necessary due to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1612906"
1802481,2018-11-29 08:37:31 UTC,"BTW... my /etc/crypttab contains:
cryptswap1 /dev/zvol/rpool/swap /dev/urandom swap,cipher=aes-xts-plain64:sha256,size=256"
1802481,2018-11-16 07:21:54 UTC,"Hi,"
1802481,2018-12-10 10:32:42 UTC,"Hi Richard,
thank you for your reply, but that didn't fix the problem."
1802483,2018-11-09 10:20:59 UTC,Libnotify fix for xenial
1802483,2018-11-09 10:27:17 UTC,Fix for bionic (and cosmic)
1802483,2018-11-09 10:30:56 UTC,Fix for disco (but could be used for bionic too) is at:
1802483,2018-11-09 12:24:27 UTC,"The attachment ""libnotify_0.7.7-3+snap-support.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1802483,2019-07-08 08:58:32 UTC,"The changes got reviews on https://gitlab.gnome.org/GNOME/libnotify/merge_requests/5 and some work is needed so unsubscribing sponsors for now, please subscribe them back once you get the upstream reviewers agreeing"
1802488,2019-08-20 03:20:10 UTC,https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=224b6c27432a755f26120166507cb3ba47d66d31
1802491,2019-09-15 19:13:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802491,2019-09-15 19:16:46 UTC,quel-est le probleme
1802495,2019-09-19 21:53:06 UTC,"Passed with 4.15 i386, marking this bug as Invalid."
1802495,2019-09-19 14:33:06 UTC,"Can't reproduce this on 5.0 i386.
Will check for 4.15 i386, if it's still OK I will just close this."
1802495,2019-09-19 12:47:35 UTC,"Trying to reproduce this on 5.0 i386 now, as 4.18 has reached EOL."
1802495,2019-05-21 14:05:57 UTC,I've reported this to the upstream lttng project: https://bugs.lttng.org/issues/1184
1802495,2019-05-21 03:14:49 UTC,"This is something that's failing for a while (was affected by bug 1802443, and then this one since 4.18.0-13.14~18.04.1)"
1802495,2019-05-20 12:34:24 UTC,And for amd64 bionic+ it fails to generate syscall info too.
1802495,2019-05-20 14:25:29 UTC,"Course bisect, this does not work with stock upstream kernels since at least 4.7-rc1.  For now I'm going to disabled this part of the lttng tests until I can get it to work again with stock 4.8+ kernels."
1802495,2019-05-20 11:57:26 UTC,"It appears that syscalls are not available on i386, got zero syscalls on bionic, cosmic, disco. It works OK on xenial."
1802495,2018-12-17 09:48:31 UTC,After the lttng module build issue solved (bug 1802443). This issue can be found on B-hwe (4.18.0-13.14~18.04.1) as well.
1802495,2018-11-09 12:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802495,2019-05-20 14:40:00 UTC,Disabling the kernel system call tracing for the moment: https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=b1654ce9e8d7d744af76787b6d4a5ff7bcec387d
1802498,2018-11-14 09:03:13 UTC,"Hey Edson,"
1802498,2018-11-18 11:42:44 UTC,"Thank you for the explanation I guess it's up to the user to fix that issues with AppArmor , or to wait for ESET to release an update that will make their AV work with AppArmor"
1802498,2018-11-13 12:09:11 UTC,"I don't know if Ubuntu can really help with this problem , it's not their problem , it's ESET's"
1802498,2018-11-09 21:40:23 UTC,Another Linux user with the same problem in AppArmor. Access the link.
1802498,2018-11-13 15:18:35 UTC,Hello Rami
1802498,2018-11-14 20:12:32 UTC,"On Wed, Nov 14, 2018 at 09:03:13AM -0000, Rami Hakim wrote:

> When ESET v4 was released , AppArmor wasn't available back in the time
> it wasn't developed yet.
"
1802500,2018-11-09 12:35:37 UTC,"By holding down the eSwitch on boot, the light will:"
1802500,2018-11-12 10:37:09 UTC,"Assigning to me, since a patch is available and waiting on me to test/merge it."
1802500,2018-11-12 12:29:37 UTC,Strange Idea:
1802500,2018-11-12 23:28:52 UTC,"I'm not sure anyone has the equipment or skill to implement that solution in a production environment, and it still doesn't resolve the issue of the attiny sensor being uncalibrated.  Due to communication and translation difficulties, it is difficult to get manufacturers to use the correct fuse values, much less get them to patch a hex file."
1802500,2018-11-19 18:08:23 UTC,This patch needs a small change. It currently passed the values ROOM_TEMP (20) and DEFAULT_THERM_CEIL (45) to the save function.
1802500,2019-01-21 07:22:44 UTC,That was odd.  Looks like a bot of some sort.
1802500,2019-01-21 07:24:37 UTC,"BTW, I gave this a quick try last month, hoping to get a reset function in time for the FW3A...  but things didn't go well.  I went back to a solid and well-tested build for that, and haven't really gotten back to the reset function yet.  But it should still happen."
1802500,2019-07-28 07:07:50 UTC,"I forgot to update this when I fixed it, but the new feature was released almost a month ago."
1802500,2018-11-12 10:35:55 UTC,"Oops, I didn't see this when I was on a bug-filing spree, and I made a duplicate.  Copying the description of that bug here:"
1802501,2018-11-09 12:54:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802501,2018-11-09 13:05:42 UTC,"Ah, here is probably the cause of it all, deprecated packages from 18.04 are not deinstalled... https://phab.lubuntu.me/w/bugs/"
1802505,2019-09-19 14:48:00 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1802505,2018-11-09 17:46:24 UTC,"I see the bug: when I create an A record in the UI and specify a TTL, it doesn't take effect."
1802505,2018-11-09 17:45:37 UTC,Unsubscribed ~field-high.
1802505,2018-11-09 17:43:46 UTC,1. Haven't tried CLI initially - UI and API only. The API part was also gated by the pacemaker resource agent operation - it looks like it did not try to apply TTL once the record was already in place.
1802505,2018-11-09 13:23:49 UTC,Subscribed ~field-high due to the fact that this bug affects high-availability in L3-oriented FCB deployments that cannot rely on VIPs.
1802505,2018-11-09 13:21:34 UTC,From the zone file:
1802505,2018-11-09 13:24:44 UTC,Please provide:
1802508,2018-11-09 13:30:04 UTC,This change was made by a bot.
1802518,2019-02-19 21:37:12 UTC,Tested on 3.2.2.  E-records show in the count in the basket in the search results but don't display in the actual basket under My Lists.
1802518,2019-12-11 21:21:19 UTC,Still present in 3.4.1.
1802518,2019-12-11 21:32:42 UTC,The problem does not manifest on the demo server with the Conifer dataset because the ebooks there (authored by Tolkien) all have their located URIs set to CONS.
1802518,2020-01-12 00:07:01 UTC,"I changed one of the Tolkien items to have a 856 $9 of SYS1, then started adding debug statements to see what was going on with an anonymous list containing all four Tolkien items."
1802518,2020-01-12 00:08:18 UTC,Oh and avoiding the sort does keep all four items and successfully shows them all on the mylist page.
1802518,2020-01-12 00:22:37 UTC,Confirmed that the id disappears after the call to open-ils.search.biblio.multiclass.query in bib_record_list_via_search() in OpenILS/Application/AppUtils.pm.
1802518,2020-01-12 21:28:36 UTC,Here's what goes in:
1802519,2019-04-15 19:12:00 UTC,Closing due to inactivity. Feel free to reopen if there is more information
1802519,2018-11-11 13:38:56 UTC,Following up on my previous comment. The initial errors are timeouts deploying nodes:
1802519,2018-11-09 14:19:15 UTC,Probably -> https://review.openstack.org/539981 is related here.
1802519,2019-02-19 13:38:05 UTC,Is this still an issue?
1802520,2019-02-27 21:53:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802520,2019-02-27 21:54:36 UTC,"I just upgraded to 18.10 and have the same problem. For me, the output when opening a single gnome-terminal is the following."
1802520,2019-05-08 12:18:21 UTC,Same issue. Output:
1802523,2018-11-09 16:14:35 UTC,"Note, even when I add a blank ""include"" on my test plan as was suggested, the tests still fail. This was AFTER adding a blank ""include"":"
1802529,2018-11-09 14:53:23 UTC,Discovered that the cause was because
1802529,2018-11-09 18:47:38 UTC,Yep - that was the problem - google caused apt to fail because they wanted explicit acceptance from someone with fingers. Once I did that update-manager worked fine. This needs to be fixed!
1802533,2020-09-28 20:25:19 UTC,Pipewire 0.3.12 landed in Debian testing.
1802533,2020-10-16 07:34:18 UTC,"> Reassigning so that necessary work is done to get pipewire updated, building and working
"
1802533,2020-11-10 08:33:13 UTC,@Liz Fong-Jones
1802533,2020-11-10 20:16:58 UTC,"https://launchpad.net/~lizthegrey/+archive/ubuntu/freedesktop -- I backported, rather than directly installing the Debian packages. You need to do a formal backport from source to force linking against Ubuntu's ABI."
1802533,2020-11-10 20:57:10 UTC,Thank you Liz. There are no installable packages on your PPA though.
1802533,2020-11-10 21:06:59 UTC,"That is correct, if you're on amd64. I built only for ARM because that's what I need for my device running Wayland (sorry!) but you should be able to clone my PPA and rebuild from source on amd64 if you like."
1802533,2020-11-11 07:33:01 UTC,"Thank you Liz! I'll see if I have the energy to do that, but with my company pushing bad remote meeting solutions I might have to :/ Now I at least know where things stand and what to do."
1802533,2020-11-30 09:06:57 UTC,GNOME Shell will start depending on it in the next release and this is what is going to pull it in main.
1802533,2020-11-26 15:20:33 UTC,"Hello, what is the status of this MIR? Getting screen sharing to work in Wayland would be a huge improvement in times like these and I'm weary of the ""Unassigned, importance low"" status that this currently have."
1802533,2020-11-26 15:44:34 UTC,"Hi Rasmus,
this looks soemwhat ready to me - it is on the Desktop team to now integrate and thereby trigger the component mismatch that will pull it into main.
I've last week pinged seb128 and didrocks about it - AFAIK they will take a look."
1802533,2020-11-27 15:28:30 UTC,"Thank you Christian, that sounds great!"
1802533,2020-12-10 21:42:42 UTC,@didrocks Any ETA for the 21.04 channel? I'd like to test this asap.
1802533,2021-02-01 10:15:45 UTC,"As Ubuntu 21.04 won't have Gnome 40, can this be enabled for the current version (in 21.04 ofc.)?"
1802533,2021-02-01 10:39:13 UTC,"On Mon, Feb 01, 2021 at 10:15:45AM -0000, Rasmus Eneman wrote:

> As Ubuntu 21.04 won't have Gnome 40, can this be enabled for the current
> version (in 21.04 ofc.)?
>
> It's explicitly disabled for Ubuntu here https://salsa.debian.org/gnome-
> team/mutter/-/blob/debian/master/debian/rules#L41-48
"
1802533,2020-11-18 16:27:09 UTC,This second review will only document the areas that some difference was found from the first review.
1802533,2020-09-14 08:55:24 UTC,https://tracker.debian.org/news/1175550/pipewire-0310-4-migrated-to-testing/
1802533,2021-02-09 18:03:02 UTC,"These were the ones component-mismatches-proposed said were required. If some of them aren't, they'll show for demotion and can be put back to universe then. Thanks!"
1802533,2020-08-17 22:15:12 UTC,"Reassigning so that necessary work is done to get pipewire updated, building and working in groovy."
1802533,2018-11-12 14:17:37 UTC,"Just comment from a desktop team perspective, that MIR is low priority for us at the moment."
1802533,2018-11-12 22:50:06 UTC,"Seb, I believe gnome-remote-desktop offers the same password option that vino does through the same UI in gnome-control-center's Sharing panel."
1802533,2018-11-20 09:26:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802533,2018-11-21 07:18:02 UTC,"@Jeremy, the MIR here is the pipewire one, not about gnome-remote-desktop vs vino, you maybe commented on the wrong ticket?
(If that was a reply to my comment, the problem with wayland/why we don't consider if for default is not the service enabling VNC, it's other things having your session closing when the shell it a bug, the lack of xrdp option, etc. And anyway, that bug is not the place to argue about wayland not being the default, that's just the fact today and leads to the comment about priority I was making)"
1802533,2020-09-04 11:17:10 UTC,"pipewire 0.3 is in NEW in Debian. Once it's cleared out there, we can request an FFe to hopefully get into groovy, and then assign back to the security team for review."
1802533,2019-02-01 19:25:36 UTC,"I certainly can't see this as a small and easy package to maintain in general. Fortunately, right now it is in sync with Debian, but it's a pretty big codebase. Any issues that might come up, especially security issues, might be effort-intensive, though at a quick glance I didn't notice anything sensitive popping up -- that said, I only did a quick review of the code -- there's some 260 files of source code."
1802533,2019-02-01 19:28:14 UTC,Please also make sure to set a bug subscriber...
1802533,2018-11-21 11:35:21 UTC,I agree remote VNC is not the only blocker for enabling Wayland by default for 20.04 LTS.
1802533,2020-02-01 13:01:26 UTC,Is this going to get done for Focal? It would be a shame to ship an LTS release without remote desktop support for Wayland. Aren't we at the point now where Wayland is supposed to people's first choice?
1802533,2020-03-10 10:37:07 UTC,"+1
It isn't possible to record a screencast with OBS on Wayland"
1802533,2020-07-01 20:20:15 UTC,"is there any chance of getting this in Groovy?
it would be nice to start migrating to Wayland-by-default in non-LTS versions, and being unable to screenshare is a blocker for a lot of users"
1802533,2020-07-02 06:05:51 UTC,"Thanks for the ping Vlad, The old FAQ declaring it not ready yet these days is (quote):
""Is PipeWire ready yet?
It is getting ready for broader testing.
The API in master is now declared stable and not expected to change anymore for the
0.3 release.
The protocol can support older 0.2 version clients transparently. This means that flatpaks
with older PipeWire libraries can connect to a newer daemon.""
=> https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ#is-pipewire-ready-yet"
1802533,2020-07-02 08:40:19 UTC,"@cpaelzer, thanks for checking with us. Pipewire is where GNOME is heading and is already required for e.g screen sharing to work on Wayland (which isn't our default session at the moment but we still want that working in Ubuntu). I don't think we are ready to switch the desktop this cycle but might aim for next cycle so getting reviews going again now makes sense. I'm reassigning to ubuntu-security as suggested"
1802533,2020-07-30 02:24:40 UTC,"I have Pipewire 0.3 working on Focal, with at least a few of its reverse-depends working correctly (gnome-remote-desktop, mutter, xdg-desktop-portal)"
1802533,2020-08-17 21:54:23 UTC,"Hi, security team is wanting to do a MIR audit on pipewire for groovy. Unfortunately, the current pipewire source downloaded from groovy does not appear to have been updated nor does it build."
1802533,2019-11-01 14:16:54 UTC,I reviewed pipewire 0.2.5-1 as checked into eoan.  This shouldn't be considered a full audit but rather a quick gauge of maintainability.
1802536,2018-11-09 16:48:09 UTC,Have you got both Budgie and Ubuntu sessions installed at the same time?  Or are you describing two different installations?
1802536,2018-11-10 01:49:52 UTC,"I have dedicated a laptop to solving this problem.  I have used 2 separate hard drives, one drive with Ubuntu Budgie 18.04.1 and one with Ubuntu 18.04.1.  I then installed Inkscape on each, separately."
1802536,2018-11-10 05:24:08 UTC,"My advice would be to also create a topic on ubuntuforums.org and raise a
question on askubuntu.com"
1802541,2018-11-09 17:36:26 UTC,"ATM we don't really know at the point where we decide to pull in the base whether the snap has hooks, they could be not listed in the snap.yaml. So this would need store support or changes around snapcraft output but then we could have issues with preexisting snaps if we are not careful."
1802541,2018-11-09 17:49:07 UTC,"I agree, while we could teach the store about it I think it is much easier to just have a special case value, like ""base: none"" that we can handle early on explicitly."
1802542,2018-11-27 15:10:53 UTC,https://review.openstack.org/#/c/617985/ looks related
1802542,2018-11-09 17:15:20 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=status%3AERROR%20and%20message%3A%5C%22ImportError%3A%20cannot%20import%20name%20deploy%5C%22
1802542,2018-11-09 17:12:57 UTC,http://logs.openstack.org/25/616125/5/check/devstack-plugin-ceph-tempest/28e36f4/job-output.txt.gz
1802542,2018-11-26 21:31:31 UTC,Still appearing here:
1802570,2020-04-26 22:20:21 UTC,"Just tried 20.04 and the behaviour has improved, but the core problem remains.
Now, at least the installer recognizes the issue and exits gracefully, but grub still fails to install."
1802570,2020-05-24 22:35:57 UTC,"I've done more extensive testing and it seems that when installing grub with the --no-nvram option, all goes well. Setting EFI vars is what mucks up."
1802572,2018-12-04 04:12:56 UTC,"4.15.0-42.45~16.04.1 - lowlatency
Regression test CMPL, RTB."
1802572,2018-12-04 07:02:39 UTC,The package has been published and the bug is being set to Fix Released
1802573,2018-11-20 15:05:18 UTC,No luck with 4.19.2 either -- kernel panic (recovery mode or normal boot).
1802573,2018-11-20 01:46:08 UTC,"I suggest trying a more stable newer version in that case, like:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.2/"
1802573,2018-11-19 22:31:27 UTC,"I installed vmlinuz-4.20.0-042000rc3-generic per your request. The machine won't boot, and just loops infinitely with the error message:"
1802573,2018-11-19 16:07:44 UTC,This machine is a fresh install so there have been no updates/upgrades. The initial install was 18.10 and whatever kernel came by default with that. I will test with the latest upstream kernel and report back.
1802573,2018-11-19 15:22:15 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1802573,2018-11-19 02:30:06 UTC,This change was made by a bot.
1802573,2019-07-22 04:15:52 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1802573,2018-11-13 01:47:29 UTC,"On the login screen, click on the gear (cog) icon :)"
1802573,2018-11-12 17:26:15 UTC,I'm having trouble finding a way to switch Ubuntu 18.10 to Wayland. I have Xwayland installed but don't see a way to switch the session. I did enable it in gdm3 custom.conf but it doesn't seem to be running. Can you point me to some directions?
1802573,2018-11-12 02:35:36 UTC,"Can you please try logging into ""Ubuntu on Wayland"" and tell us if that has the same problem?"
1802573,2018-11-19 02:15:23 UTC,If you get the same behaviour in Wayland sessions then it's probably not a Xorg bug. Maybe mutter or maybe the kernel.
1802573,2018-11-16 21:59:03 UTC,"I can't even get into the login screen when the DisplayPort device is attached. But I disconnected that, got to gdm login via the VGA device, then switched to Ubuntu on Wayland. Ubuntu on Wayland works fine for me generally, but I get the same behavior when connecting the DisplayPort device after logging in. I've included a video of the behavior here: https://photos.app.goo.gl/aJSx5stMMg7QZULH6"
1802574,2019-09-25 19:32:06 UTC,I'm having the same issue (mostly) with Ubuntu 19.04.
1802574,2019-09-25 19:38:08 UTC,"Forgot to mention, laptop is Thinkpad X1 Carbon 6th gen"
1802574,2019-07-28 08:52:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802574,2018-11-12 02:37:56 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1802574,2018-11-17 15:11:49 UTC,"OK, so, I've learned more about this."
1802574,2018-11-13 01:51:20 UTC,OK. This sounds related to bug 1723025 or one of:
1802574,2018-11-12 17:41:59 UTC,"I've already got apport configured to report everything (i.e., I've already done the workaround suggested in bug 994921), and there is no crash either in /var/crash or on https://errors.ubuntu.com. I don't think a crash is what's happening here."
1802574,2019-07-26 08:45:20 UTC,"Was there ever a resolution to this.  I am having much the same problem using my Dell Latitude 7480 running Ubuntu 18.04.2 LTS.  In my case the behaviour that causes problems is that I have the laptop docked and suspend it - and then undock the laptop.  When I attempt to restart the laptop (undocked) I get the same behaviour reported by the OP - i.e. laptop starts up and screen backlight comes on, but nothing is ever displayed.  I can switch to a virtual console and use that normally including rebooting. There is nothing in /var/crash or on http://errors.ubuntu.com/ .  I have tried killing a range of X related processes to see if I could get the GUI to restart - but without success."
1802578,2018-11-09 20:00:07 UTC,This change was made by a bot.
1802578,2018-11-10 15:15:55 UTC,"I am testing the latest mainline kernel now, version 4.19.0-041900-generic #201810221809."
1802578,2018-11-12 19:54:36 UTC,"Issue occurred again today, but I could not find the same error in the journal this time. Could perhaps be non-kernel related?"
1802578,2018-11-19 09:21:25 UTC,"Keeps happening, but it does appear to be docking station related. After getting some more errors today I got to Google and find that #1552040 might be the bug causing this with me. So perhaps a duplicate of that."
1802578,2018-11-23 09:09:13 UTC,I can confirm that this is happening less frequent after applying workaround from bug 1552040.
1802584,2018-11-13 01:55:07 UTC,"Sorry, but we can't support packages from PPAs here. You have installed:"
1802584,2018-11-12 14:35:44 UTC,apport information
1802584,2018-11-12 14:35:43 UTC,apport information
1802584,2018-11-12 13:27:06 UTC,It's done.
1802584,2018-11-12 14:35:41 UTC,apport information
1802584,2018-11-12 14:35:39 UTC,apport information
1802584,2018-11-12 02:45:39 UTC,Please run this command to send us more information about the system:
1802584,2018-11-12 14:35:42 UTC,apport information
1802585,2019-09-04 20:19:04 UTC,This was fixed in the latest 4.15 kernels (linux-hwe 4.15.0-60.67)
1802585,2019-08-27 17:48:56 UTC,"My reproducer for Disco+ is a different bug.  I get input/output errors very quickly once specifying nfs vers=4.0.  If you don't specify it, it works fine."
1802585,2019-08-27 16:57:40 UTC,I was also able to reproduce this on Eoan by specifying vers=4.0 - where I thought it should be fixed.
1802585,2019-01-25 20:51:56 UTC,Looks good to me!
1802585,2018-11-16 21:35:30 UTC,"I built a test kernel with commit be189f7e7f03.  The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1802585"
1802585,2018-11-09 21:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802585,2019-08-26 23:31:08 UTC,"I was able to reproduce this.  Minor note, that you need to specify vers=4.0 in the mount options, nfs 4.1+ appears to not be affected by this."
1802587,2018-11-15 05:02:12 UTC,Upstream Patch: https://review.openstack.org/617229
1802587,2018-11-16 20:50:50 UTC,"I was just discussing this with Iain in IRC:
http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2018-11-16.log.html#t2018-11-16T20:17:06"
1802587,2018-11-19 05:26:41 UTC,"Hi Brian,"
1802587,2018-11-23 21:42:02 UTC,"I proposed changes for (1) and (2). (3) can be done already, but it involves the user composing JSON. A --baskend option could be added."
1802587,2019-05-04 21:22:42 UTC,"I notice that with current implementation of nova snapshot, snapshoting VM with direct_snapshot enabled backend (exemple ceph backend) will always fail, as nova will always hit the ""400 invalid location error"", should this increase criticity of this bug ?"
1802587,2019-07-30 16:52:40 UTC,"I have run into this as well.
I have setup glance backends as described here:
https://docs.openstack.org/glance/latest/admin/multistores.html"
1802587,2019-07-30 17:09:16 UTC,Could you try the same using glance image-create command (i.e. using glanceclient). Openstack client is not compatible or up-to-date with current glance changes.
1802587,2019-07-30 21:23:29 UTC,I get the same error.
1802587,2019-07-30 21:37:30 UTC,"I also tried specifying either of my 2 defined backends 'fast' or 'reliable'
and got the same failure either way."
1802587,2019-07-31 04:37:51 UTC,"Hi Walt,"
1802587,2019-07-31 14:32:35 UTC,"Thank you, that worked.  I tried using both my backends and glance-api seems happy with that patch."
1802587,2019-09-25 14:23:26 UTC,"Reviewed:  https://review.opendev.org/617229
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=4e070fd6e0346948898b751516234ba62121e2a8
Submitter: Zuul
Branch:    master"
1802587,2019-10-02 10:05:59 UTC,This issue was fixed in the openstack/glance 19.0.0.0rc1 release candidate.
1802590,2019-04-09 12:04:30 UTC,http://ci.jujucharms.com/job/make-check-juju/4235/consoleFull
1802590,2019-01-28 22:17:21 UTC,And again: http://ci.jujucharms.com/job/make-check-juju/2518/console
1802590,2019-01-18 09:27:10 UTC,This just happened again. http://ci.jujucharms.com/job/make-check-juju/2346/consoleFull
1802593,2019-08-05 14:53:05 UTC,"I've gone ahead and pushed this to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jane and Sam!"
1802593,2019-08-01 15:51:00 UTC,I agree with using ctx.eg_locale. Jane's patch works for me; signoff pushed to user/gmcharlt/lp1802593_signoff.
1802593,2018-11-09 21:13:59 UTC,Adding the accessibility tag because of this explanation of this explanation of its accessibility ramifications: https://dequeuniversity.com/rules/axe/3.1/html-lang-valid
1802593,2019-03-01 15:23:12 UTC,Possible fix pushed to user/slink/LP1802593_angular_js_web_client_invalid_lang_attributes.
1802593,2019-07-29 19:11:57 UTC,"Thanks for the patch, Sam.  Your approach was good, but it seems like it broke the language picker in the Web staff client."
1802593,2019-03-01 15:05:03 UTC,Confirmed.
1802614,2020-03-12 05:00:22 UTC,"Hmm, I was under the impression that VNC and RDP were both supported in Gnome...  sorry about that."
1802614,2021-02-01 15:35:26 UTC,"[Summary]
MIR Team Ack
List of specific binary packages to be promoted to main: gnome-remote-desktop"
1802614,2021-02-01 15:32:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802614,2021-02-01 15:14:58 UTC,I'll do a quick re-review as the former checks didn't reach a final Ack/Nack
1802614,2021-02-01 10:21:54 UTC,"The pipewire MIR has been approved now, was that the only item blocking this one? Security team reviewed and gave an ack, is it fine from the MIR team side as well? We would like to switch the desktop default to wayland around now and that's needed to not regress screen sharing"
1802614,2021-02-01 09:44:59 UTC,Settings back to New which I think is needed for the MIR team to notice is still needs to be reviewed? (pipewire has been accepted now)
1802614,2020-10-25 11:38:36 UTC,"Hi,
Can someone confirm that this is still an issue in 20.10 or that vnc/rdp will not work in a wayland sesison ?"
1802614,2020-03-09 10:59:04 UTC,@Jonathan
1802614,2020-03-07 04:21:50 UTC,I'm another person who is definitely disappointed that this doesn't seem to be slated for inclusion in 20.04.
1802614,2020-01-31 15:22:17 UTC,"Are you REALLY going to ship your next LTS release without screen sharing in Wayland, when the code for supporting it is 100% implemented and the security team appears to have approved it?"
1802614,2020-01-07 02:00:18 UTC,This is a huge functional regression. I can't believe it isn't already fixed. Now it appears maybe it isn't even going to be fixed in 20.04. wtf?
1802614,2019-07-09 19:51:59 UTC,I would like to add an additional condition to the security team ACK. The pipewire MIR must also be ACK'd.
1802614,2019-07-09 19:38:54 UTC,I reviewed gnome-remote-desktop 0.1.7-1 as checked into eoan. This shouldn't be considered a full audit but rather a quick gauge of maintainability.
1802614,2019-02-07 19:20:03 UTC,"Thanks, I removed that sentence from the description."
1802614,2019-02-07 17:27:23 UTC,"> Once this MIR is approved, we should be able to demote vino to universe.
"
1802614,2019-02-07 17:06:23 UTC,"Yes, it's a VNC server."
1802614,2019-02-07 14:58:21 UTC,"So if I understand well, this is a server rather than a client? You should make that clearer when fixing MIRs, so it's absolutely unabiguous whether something is a client program or a server part of the desktop."
1802614,2018-11-20 09:28:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802617,2020-07-13 01:14:03 UTC,I got the same issue after upgrading from 18.04 to 20.04.  I followed the steps from #11 and then reversed them to fix the issue and re-enable swap encryption
1802617,2020-05-08 18:42:49 UTC,"First, besides the active swapfile, that caused the trouble, I found an additional uncommented line in my fstab, referencing /dev/mapper/yoga--vg-swap_1. Whether this was used before or is just a relict I cannot tell."
1802617,2019-12-11 09:53:26 UTC,"I've changed following tags:
removed 'wayland-session' - no connection to a display server, because the boot procedure fails, before any display manager is loaded (x or wayland) - FYI I always used X."
1802617,2019-10-18 00:31:04 UTC,"Sorry for the spam, this is how to fix this (note it will mean your swapfile isn't encrypted anymore and I'm  not sure how much of a security risk that poses)."
1802617,2019-10-18 00:21:12 UTC,"update-initramfs: Generating /boot/initrd.img-5.3.0-18-generic
cryptsetup: ERROR: Couldn't resolve device /swapfile
cryptsetup: WARNING: Resume target cryptswap1 uses a key file"
1802617,2019-10-18 00:16:59 UTC,"^ ignore that, it will further break cryptsetup.  the fix was that same as comment #11, except using a 19.10 recovery instead.  This will get you back into your system, but it will re-break every time the kernel is updated."
1802617,2019-10-17 23:56:14 UTC,"FYI to anyone who's going from 19.04 to 19.10, you need to remove the `size=256` part in /etc/crypttab or this issue comes back :)"
1802617,2019-01-03 08:08:06 UTC,"Used a clean instal for Ubuntu 18.10 without swap file.
After kernel update I get stuck in the ""cryptsetup: Waiting for encrypted source device /swapfile..."""
1802617,2019-02-22 05:07:21 UTC,"For those looking to solve this problem please note: removing the swap line from /etc/fstab and /etc/crypttab will fix the problem, but it'll also disable swap."
1802617,2019-01-18 20:48:24 UTC,"Not sure about the proposed workaround, because I don't know what would happen to the encrypted /home when we purge cryptsetup. Instead, I've done the following sequence:"
1802617,2018-11-14 17:52:25 UTC,"I am using a clean installation of Ubuntu 18.10. I have the same problem. With a kernel 4.18.0-10.11 it worked for me when I added option size to crypttab. After an update of the kernel to 4.18.0-11.12 the system gives me the same error: ""cryptsetup: Waiting for encrypted source device /swapfile..."""
1802617,2018-11-14 17:44:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802617,2018-11-12 16:24:59 UTC,The messages from aptermlog seem relevant:
1802617,2018-11-10 14:33:27 UTC,Candidate Work-around:
1802617,2018-11-10 02:33:47 UTC,A post on Ask Ubuntu seems relevant: https://askubuntu.com/questions/1087828/cant-unlock-cryptswap1
1802617,2019-03-21 09:05:22 UTC,"I've also hit this issue.  I go round it by loading up a 18.04 Live USB in live mode.  I then mounted my HDD onto the live OS (I only encrypted my home folder, so wasn't an issue).  I then cded into the mount directory and ran `chroot ./`.  Then added `size=256` to the end of the /swapfile line in /etc/crypttab and ran update-initramfs -u (hence the chroot)."
1802622,2019-10-17 22:06:27 UTC,We're considering disabling CONFIG_HARDENED_USERCOPY_FALLBACK in preparation for 20.04 LTS so getting this fixed soon would be necessary to keep the driver working.
1802622,2019-10-17 23:38:20 UTC,Thanks for pointing that out! I'm marking this bug as fixed for nvidia-graphics-drivers-340.
1802622,2019-06-07 09:55:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802622,2019-10-17 23:05:39 UTC,This patch was added to the nvidia-340 package in 340.107-0ubuntu5 as per http://changelogs.ubuntu.com/changelogs/pool/restricted/n/nvidia-graphics-drivers-340/nvidia-graphics-drivers-340_340.107-0ubuntu7/changelog so this bug can be marked as resolved.
1802622,2019-05-15 20:00:29 UTC,This is the patch from debian for this issue. The driver seems to compile fine with it.
1802622,2019-05-15 20:24:41 UTC,"The attachment ""kmem_cache_create_usercopy.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1802622,2018-12-02 07:03:27 UTC,"No problems in 18.04, but just installed 18.10 and immediately noticed:"
1802622,2018-11-11 16:11:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802625,2018-12-09 15:56:17 UTC,"Confirmed on Inkscape 0.92+devel, Debian 9"
1802625,2020-02-10 19:40:39 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1802628,2018-11-14 08:56:30 UTC,"The Debian bug is closed by accident, the root cause was not fixed, just an issue that came up while checking."
1802628,2019-01-15 13:17:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802628,2019-08-14 14:12:50 UTC,"One should disable the ""Microsoft Network Client"" filter on all unnecessary interfaces in Windows."
1802628,2020-02-26 13:14:57 UTC,Has anyone tried the more recent samba versions like 2:4.11.5+dfsg-1ubuntu2 in Focal in regard to this bug?
1802628,2020-05-01 11:08:00 UTC,I can confirm that this issue still exists in Focal:
1802631,2019-07-22 04:42:47 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1802631,2019-07-22 05:11:59 UTC,This behaviour is the same in 19.04 as well... Front jack is just not working
1802640,2020-01-31 13:37:12 UTC,"Reviewed:  https://review.opendev.org/703791
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cf36bd4ca52bec4a707c35df261b8a2630850e68
Submitter: Zuul
Branch:    master"
1802640,2020-01-22 13:35:32 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/703791"
1802640,2019-02-07 21:40:41 UTC,"Change abandoned by Terry Wilson (<email address hidden>) on branch: master
Review: https://review.openstack.org/621572
Reason: was just for testing."
1802640,2018-12-13 14:56:35 UTC,"Change abandoned by Hongbin Lu (<email address hidden>) on branch: master
Review: https://review.openstack.org/621318"
1802640,2018-12-13 08:40:28 UTC,@Terry: I modified this query a bit and it showed me a lot of hits in last few days:
1802640,2018-12-03 13:38:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621572"
1802640,2018-12-03 13:30:47 UTC,"The timeout always happens as we are waiting for the response from ovsdb-server incrementing next_cfg. The time between successfully calling OVSBridge.create() and set_secure_mode() (which fails) in one of the logs I looked at is 0.3 seconds and there is nothing weird in ovsdb-server.log (we just see the disconnect from the agent after the TimeoutException), so it seems unlikely that things slowed down by over 30x in that short time to cause an ovsdb timeout."
1802640,2018-11-30 23:56:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621318"
1802640,2018-11-29 16:56:36 UTC,"Yes, I saw it at least few times recently in neutron jobs, e.g.:"
1802640,2018-12-04 17:59:45 UTC,"According to logstash, it hasn't hit since Nov 30 for some reason."
1802640,2018-11-29 15:47:25 UTC,"Over the past few days, according to elasticsearch, this has occurred 15-25 times per every 3 hour window. Most recently observed it causing a grenade job to fail in a patch on ironic's gate. :("
1802646,2018-11-10 14:00:08 UTC,This change was made by a bot.
1802646,2018-11-16 19:12:25 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1802646,2018-11-17 13:00:49 UTC,kernel-bug-exists-upstream
1802652,2019-12-23 03:09:39 UTC,Confirming for newer model:
1802652,2019-12-23 03:18:40 UTC,"dmesg:
[   14.503395] asus_wmi: ASUS WMI generic driver loaded
[   14.505116] asus_wmi: Initialization: 0x1
[   14.505180] asus_wmi: BIOS WMI version: 9.0
[   14.505219] asus_wmi: SFUN value: 0x21
[   14.505221] asus-nb-wmi asus-nb-wmi: Detected ATK, not ASUSWMI, use DSTS
[   14.505223] asus-nb-wmi asus-nb-wmi: Detected ATK, enable event queue
[   14.507229] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input29
[   14.662354] asus_wmi: Number of fans: 0"
1802652,2020-02-05 19:55:01 UTC,"Another update. Keys do emit events, but appear to be incorrect?"
1802652,2020-04-20 01:31:50 UTC,I'm trying to break this down further:
1802652,2020-02-05 20:48:58 UTC,Wireshark capture data from each button individually in Windows.
1802652,2020-02-05 20:54:25 UTC,"Apologies, the last attachment is Linux capture data (as per filename)"
1802652,2020-04-19 04:51:47 UTC,"The key thing I've noticed here is that if I grab the device via libusb and capture data, then it's on  interface 0x83, and the bytes are a little different to the keys that do work (like vol+)."
1802652,2020-02-05 20:34:03 UTC,Wireshark capture data from each button individually in Windows.
1802652,2019-06-17 06:41:55 UTC,"Hi, same problem here, keyboard backlight and some Fn don't work:
- F5 (fan overboost, that's ok if it doesn't work)
- F6 (don't know what it is)
- F7 (screen brightness down)
- F8 (screen brightness up)
- F10 (disable touchpad)
- F11 (screen sleep)
- F12 (airplane mode)
- keyboard arrow up (brightness keyboard light up)
- keyboard arrow down (brightness keyboard light down)"
1802652,2019-01-15 09:35:11 UTC,see also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343
1802652,2019-01-31 18:05:31 UTC,"Tried it, no change"
1802652,2019-02-07 04:49:16 UTC,Different. I'm on an ASUS ROG GL502VM
1802652,2018-11-10 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802652,2018-11-10 15:35:49 UTC,"See Bug #1796550.
--
Cristian Aravena Romero (caravena)"
1802652,2018-11-10 19:17:26 UTC,"Ubuntu 18.10 does not work on this laptop, at least not the live version. It blocks on the GPU.
In linux mint it works smooth, apart from the keyboard backlight."
1802652,2018-11-11 09:54:42 UTC,"Fedora 29, same thing. Doesn't start in graphic mode. The only version that seems to work is Linux Mint 19 at the moment.
I've added an output of inxi:"
1802652,2018-11-16 19:06:54 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1802652,2018-11-16 19:40:46 UTC,"It is a fresh install never tried an older version.
I have tried the new kernel, same issue.
The asus-nb-wmi module is loaded but seems not to support this keyboard."
1802652,2019-01-15 09:51:02 UTC,and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796573
1802652,2019-01-31 05:43:06 UTC,Try: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/comments/34 ?
1802653,2018-12-04 18:46:32 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1802653,2019-07-22 04:43:01 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1802654,2020-03-18 14:43:23 UTC,Closing because Invalid: may be a support request.
1802659,2020-03-22 11:04:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802659,2020-04-22 18:07:51 UTC,Looks likie this was a was a problem 5 years ago as weel... with the same problem.
1802660,2019-05-04 21:33:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802661,2018-11-10 21:08:33 UTC,"deepl translation:
¿En qué sistema operativo se encuentra? ¿Por qué empiezas Mixxx nuevo? ¿Qué problema tiene antes de reiniciar?"
1802661,2020-07-10 04:17:24 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1802661,2018-11-10 21:07:33 UTC,On which OS are you? Why do you start Mixxx new? What issue do you have before restart?
1802665,2018-11-10 18:00:07 UTC,This change was made by a bot.
1802665,2018-11-16 19:04:56 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1802665,2018-11-17 13:22:54 UTC,kernel-bug-exists-upstream
1802674,2018-11-10 20:27:58 UTC,"pow is indeed part as well of the math library for the 'power of' function.
as well as roundf."
1802674,2018-11-11 11:38:00 UTC,"Well, I did find a working fix to apply in debian/rules."
1802674,2018-11-11 20:43:26 UTC,"Well, my Launchpad PPA is currently back to fully working."
1802675,2020-04-29 09:30:26 UTC,I too have the exact problem and would like to get this resolved ASAP. Thanks a lot.
1802675,2018-12-06 17:05:29 UTC,"Hello Sebastian,
Although I move back to Windows (*it was needed for my job).
I remember that I when was copying between local directories or from a directory to the my ext. HDD was behaving ok the problem appears when copying straight to the desktop (*not the folder).
If you see the video I attached I demonstrate well the problem.
Also the hdd was formatted as NTFS."
1802675,2018-12-06 16:15:14 UTC,Thank you for your bug report. Is that specific to some devices? Do you get it when copying between local directories or from other drives? What sort of disk/filesystem is it?
1802675,2019-04-22 12:10:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802677,2018-11-30 18:09:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802677,2018-11-30 18:18:32 UTC,Affecting Ubuntu 18 since updates on 11/27. Update log file attached.
1802677,2018-11-30 21:47:16 UTC,"If you reboot after receiving this error you will be unable to get back into the system. Boot up will hang at ""Started Update UTMP about System Runlevel Changes. Alt-F2 allows you to switch to login prompt. However, attempts to purge gnome and related dependencies or perform any updates fail."
1802677,2018-11-30 22:14:59 UTC,"Found the following two entries had been added to /etc/apt/sources.list following automatic updates.
deb [trusted=yes] http://ftp.us.debian.org/debian experimental main
deb [trusted=yes] http://ftp.us.debian.org/debian sid main"
1802677,2018-12-01 21:21:15 UTC,"Unfortunately I don't even have the entries that jtrupp mentioned in his post. My system is still broken. Funny thing is, it's a fresh install, therefore I have no software to work with..."
1802679,2018-11-10 21:14:55 UTC,This should be clearer
1802679,2018-11-15 08:12:22 UTC,I am seeing the exact same problem as described in the previous posts with screenshots.
1802679,2019-02-05 22:40:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802680,2018-12-07 17:03:40 UTC,Thank you for your bug report. What Ubuntu version do you use? There is a know issue in 18.10 which is resolved 3.30.2 (which isn't in Ubuntu yet)
1802680,2018-12-07 18:05:49 UTC,This was after updating to 18.04
1802680,2018-12-07 19:15:55 UTC,I mean to 18.10
1802682,2020-09-23 21:42:33 UTC,"Mike, you're right in that the ability to select from a dropdown is the fix but the root issue is that without this change staff just have to know that the correct values to enter into that setting are database ids (3 for No Access), not the textual names displayed in the dropdown. When you type the name of the setting the value is un-set in the user editor."
1802682,2020-09-23 20:49:53 UTC,Hi Mike - terran-master doesn't have that patch installed. It's on acorn.evergreencatalog.com
1802682,2020-09-23 20:27:33 UTC,I tried this out on the https://terran-master.gapines.org server. Here's the steps I went through for testing:
1802682,2020-09-23 21:13:42 UTC,"Aha!  Thank you for seeing my error, Terran.  I re-did the testing on the acorn.evergreencatalog.com server and I see the default net access level showing.  That part looks great. I have no objections to the sign off on this."
1802682,2020-09-14 20:58:51 UTC,"In yet further necrobranchy I offer up this code in the place of my earlier attempt:
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1802682_cnal_ous_type / working/user/jboyer/lp1802682_cnal_ous_type"
1802682,2019-07-30 15:32:47 UTC,"Jason, I'm unable to confirm this bug.  When I change the value, it's reflected in the Register New Patron interface after a refresh.  It looks like the value is getting applied in the set_new_patron_defaults() function."
1802682,2018-11-10 23:05:32 UTC,"Here it is, including an enhancement to the OUS Editor to use the correct type for that setting rather than making you use raw ID numbers (or as I have seen in our database, various permutations of the word ""filter"")."
1802682,2020-09-23 19:48:57 UTC,Works for me! My signoff is at:
1802691,2019-08-28 12:18:13 UTC,"I'm also experiencing this issue and I'm trying to fix this for days now. The send speed caps out at about 700 Mbps. I'm not seeing any hangs or connection losses though. I'm eager to find a solution for this, as I have to move 50 TB over that server."
1802691,2020-06-10 17:43:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1802691,2020-06-10 17:45:28 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1802691,2020-06-16 23:32:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'."
1802691,2020-06-30 23:14:23 UTC,"All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1802691,2020-07-01 10:25:25 UTC,This bug was fixed in the package linux - 5.4.0-40.44
1802691,2020-07-01 10:26:50 UTC,This bug was fixed in the package linux-oem-5.6 - 5.6.0-1018.18
1802691,2020-07-01 10:28:55 UTC,This bug was fixed in the package linux - 4.15.0-109.110
1802691,2020-07-01 10:33:31 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1063.68
1802691,2020-07-12 19:15:03 UTC,"All autopkgtests for the newly accepted linux-hwe-5.0 (5.0.0-57.61~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1802691,2020-07-28 00:57:35 UTC,This bug was fixed in the package linux-oem-5.6 - 5.6.0-1020.20
1802691,2020-07-28 00:57:39 UTC,This bug was fixed in the package linux - 5.4.0-42.46
1802691,2020-08-12 14:58:25 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1065.70
1802691,2019-03-28 07:18:38 UTC,"Please test this kernel, which disables TSO:
https://people.canonical.com/~khfeng/lp1785171/"
1802691,2020-07-01 10:27:39 UTC,This bug was fixed in the package linux - 5.3.0-62.56
1802691,2019-01-07 22:33:26 UTC,"I also encountered network performance degradation on my server, however I'm not running Ubuntu but Debian with a self-compiled kernel. With bisecting the kernel, I could track this issue down to this commit between 4.14.2 and 4.14.3:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0f478f25d50cb6464678284a13f514fefc16e271"
1802691,2018-11-16 13:38:02 UTC,apport information
1802691,2018-11-18 00:20:52 UTC,"I've just confirmed the problem again by trying to transfer a file between Windows 10 and Ubuntu 18.04.1 via samba. Upload speed from Windoes to Ubuntu is 110-115MB/S, while download from Ubuntu to Windows is only 88-90MB/S."
1802691,2018-11-11 01:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802691,2018-11-11 05:12:29 UTC,"Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?"
1802691,2018-11-30 18:14:59 UTC,"While I was waiting for a fix, I've just noticed a new problem.. Now the transfer speed became very inconsistent. For the first few seconds when I'm sending TO Ubuntu I get 110MBs (as expected), but then speed drops to 50, 30, 20 and keeps going up and down for the rest of the files transfer. Very disappointing."
1802691,2018-11-15 23:32:35 UTC,"I have to ckarify. The problem is NOT with receive/download speed, but with SEND. SEND speed on Ubuntu machine are too low. Iperf is a bit backwards, but I confirmed it by checking my windows pc traffic."
1802691,2018-11-16 13:37:53 UTC,apport information
1802691,2018-11-16 13:37:54 UTC,apport information
1802691,2018-11-16 13:37:55 UTC,apport information
1802691,2018-11-16 13:37:56 UTC,apport information
1802691,2018-11-15 20:57:22 UTC,I dis not upgrade. I did a clean install. Unfortumately I probbly won't be trying a mainline kernel because it seems that it's too complicated to remove.
1802691,2018-11-16 13:37:58 UTC,apport information
1802691,2018-11-16 13:37:58 UTC,apport information
1802691,2018-11-16 13:38:00 UTC,apport information
1802691,2018-11-16 13:38:01 UTC,apport information
1802691,2018-11-16 13:38:04 UTC,apport information
1802691,2018-11-16 13:38:03 UTC,apport information
1802691,2018-11-16 13:37:57 UTC,apport information
1802693,2019-01-28 12:28:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802705,2018-11-22 07:37:27 UTC,"""taas can create tap-service on a port down"" is an expected behavior.
""new rules not added even the port is up later"" is a bug."
1802706,2018-11-22 07:38:37 UTC,"""taas can create tap-flow on the source port down without any error info"" is an expected behavior.
""new rules not added even the port is up later"" is a bug."
1802707,2018-11-11 10:09:04 UTC,"#!/bin/bash
# tadaen sylvermane | jason gibson
# configure locales for ubuntu bionic ltsp chroot creation"
1802712,2018-12-18 07:43:41 UTC,See both:
1802712,2018-12-18 07:40:22 UTC,Also mentioned in bug 1807706.
1802712,2018-12-16 06:29:18 UTC,The touchpad works fine on linux kernel v4.18.19 and more
1802712,2018-11-11 11:18:44 UTC,apport information
1802712,2018-12-15 20:36:34 UTC,"Upstream kernel commit https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/input/mouse/elan_i2c_core.c?id=13c1c5e4d7f887cba36c5e3df3faa22071c1469f
Should fix this"
1802712,2018-11-15 21:08:41 UTC,Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 stable kernel[0].
1802712,2018-11-11 11:18:45 UTC,apport information
1802712,2019-01-10 07:50:33 UTC,Looks like at least one model is fixed in disco proposed:
1802712,2018-11-11 11:18:42 UTC,apport information
1802712,2018-11-11 11:18:33 UTC,apport information
1802712,2018-11-11 11:18:39 UTC,apport information
1802712,2018-11-11 11:18:38 UTC,apport information
1802712,2018-11-11 11:18:37 UTC,apport information
1802712,2018-11-11 11:18:35 UTC,apport information
1802712,2018-11-11 11:18:34 UTC,apport information
1802712,2018-11-11 11:18:32 UTC,apport information
1802712,2018-11-11 11:18:30 UTC,apport information
1802712,2018-11-11 11:18:29 UTC,apport information
1802712,2018-11-11 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802712,2018-11-11 11:18:41 UTC,apport information
1802718,2018-11-12 21:30:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802718,2020-07-25 02:34:43 UTC,"Just confirming the annoyance/source of bugs/misunderstanding of doing such:
sudo cp /etc/apt/sources.list /etc/apt/sources.list~
sudo sed -Ei 's/^# deb-src /deb-src /' /etc/apt/sources.list
sudo apt-get update"
1802718,2020-07-25 07:47:17 UTC,Should probably be
1802718,2020-07-25 07:49:00 UTC,Enabling by default does not make much sense and people usually use pull-lp-source instead which does not need sources.list entries and pulls directly from launchpad.
1802720,2019-01-20 15:52:20 UTC,"Fixed upstream 2018-11-25:
https://www.smartmontools.org/ticket/1131#comment:5
Included in smartmontools-7.0 and in 5.41-6.6 drivedb branches."
1802720,2018-11-14 09:01:39 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. I'm sure it'll be helpful to others experiencing the same issue.
1802720,2018-11-14 09:00:22 UTC,"That usually means the smartmontools DB isn't new enough for your new device.
Could you give the version 6.6 that is in the current Development release of Ubunut (19.04 Disco Dingo) a try if that has an updated device DB that would know yours?"
1802720,2018-11-14 19:19:31 UTC,"Ok, tested with 6.6, which didn't make much of a difference as I had already updated my drivedb.h to the version found in the 6.6 version. I suspect the issue is due to this line in the database:"
1802721,2018-11-12 15:57:18 UTC,"So, you're hitting two or three separate bugs. The extra one is if you try this on snapd and hit the ld-so absolute symlink one :)"
1802721,2019-11-26 10:06:35 UTC,"John, what is the status of this issue?"
1802721,2019-11-26 10:11:27 UTC,/me realises the issue talks about core18-based classically confined snap. Not strictly about a snap that runs on core18.
1802722,2018-11-11 16:38:28 UTC,"This is the underlying cause, it looks like the switch to python3 broke the script generating the list of plugins:"
1802722,2018-11-11 16:53:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617152"
1802722,2019-03-07 12:57:39 UTC,"Change abandoned by Matthew Treinish (<email address hidden>) on branch: master
Review: https://review.openstack.org/617152"
1802722,2020-02-10 14:36:40 UTC,"Seems like it got fixed by the following review:
https://review.opendev.org/#/c/615396/"
1802724,2019-02-19 01:18:18 UTC,@Nick ... and open a new one with an ugly diff pair routing bug causing difficulties drawing the pairs ;-) Thanks for a nice test case Nick!
1802724,2019-02-18 22:07:44 UTC,"I was trying to route those diff pairs, and because they were ""hard"" to connect and  it was not something I could reproduce consistently. I don't remember the pns settings. But I guess it was in walkaroud mode. Maybe it requires some more obstacles for the pns to get stuck. I guess we should close this bug for now."
1802724,2019-02-18 21:51:55 UTC,"@Nick,"
1802724,2019-02-18 21:19:23 UTC,"@Tomasz, sorry for the slow response. But I can't seem to make it get stuck here at the moment."
1802724,2019-02-08 15:06:06 UTC,"@Nick, I really appreciate that. If you manage to freeze Kicad, could you send me a full coredump instead of just the stack trace? I suspect the freeze happens somewhere in the shove algorithm (PathLength() always exits in finite time)."
1802724,2018-12-24 14:29:16 UTC,"@Nick, do you have any PCB where this bug ever occurred? Maybe I'll try fuzzing the router a bit with random mouse events to see if it fails after a while..."
1802724,2018-12-17 19:46:38 UTC,"@Tom, from a user perspective I not the difference is significant.  If the walkaround code can get stuck in a loop and there is no way to exit out of the loop, then I see this as an issue because the process will have to be kill possibly causing loss of changes."
1802724,2018-12-11 22:58:31 UTC,"Hi Wayne,"
1802724,2018-11-15 13:43:42 UTC,"@Tom, did you get a chance to take a look at this?  Is it possible that some condition puts the SHAPE_LINE_CHAIN code into an infinite loop?"
1802724,2018-11-11 12:38:56 UTC,I don't have a PCB where I can reliably reproduce this.
1802724,2019-02-05 08:21:17 UTC,"@Tom, I think this is the issue I mentioned at FOSDEM, I have the pcb file locally, and I will try to see if it still happens for master and report back."
1802725,2018-11-15 10:46:35 UTC,"As I can see, all containers are using jounald as logging driver. So far I've been able to identify that this problem is not related to journald rate limiting. Even though rate limiting was active on the controller nodes and some messages were being discarded because of that, it is not the root cause of that specific problem."
1802725,2018-11-16 15:27:53 UTC,"Just an idea that cause of this problem may be blocking delivery of logs from container to driver. By default logs are delivered from container to logging driver (journald in our case). This behaviour is controlled by --log-opt mode=non-blocking option. If application encounters when STDERR or STDOUT streams, it may fail or misbehave in unpredictable way. Need to test that somehow."
1802728,2018-11-13 05:50:41 UTC,Fixed in stable r18823 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18823>.
1802728,2018-11-15 17:38:09 UTC,"It's a bit hard to tell whether that patch has made much difference since staging is sufficiently much slower than production to obscure any gains, but it at least doesn't seem to have made matters any worse.  We'll see once it's on production."
1802728,2018-11-15 19:47:47 UTC,"Well, it's faster, but not fast enough: it's still timing out.  A current OOPS is OOPS-88ba1d4284215d4813e0f7e59c73983e.  In that, it takes rather more than five seconds between the query in the bugtask_set.getBugTaskPeople call in BugLinksListingView.buglinks and the next database query, which is an authentication check on a person.  It's hard to tell how much of that is the cost of materialising the list of Person rows and how much is other stuff in between.  (Also the authentication check may be a problem in itself, though I can't be sure about that.)"
1802729,2020-02-10 09:39:16 UTC,"fixed in 1.0beta2 (c38fd11e78, 2020-02-09)"
1802736,2018-11-17 19:17:56 UTC,"This seems to happen because of a tornado/eventlet bug. I reported it to eventlet, but they don't seem to agree with my observations so far.
https://github.com/eventlet/eventlet/issues/529"
1802736,2018-11-26 10:54:50 UTC,do you think there is anything we (neutron) can do to fix/workaround it?
1802738,2019-06-06 12:05:16 UTC,"Hello Kai-Heng,"
1802738,2018-12-01 00:19:28 UTC,"The patch was picked up in the stable kernel (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/), and added to 4.19.5, 4.14.84, 4.9.141, 4.4.165, and 4.20-rc4."
1802738,2018-11-20 13:33:22 UTC,My kernel patch was accepted this morning (very quick!!). Per the notification received:
1802738,2018-11-11 16:30:07 UTC,This change was made by a bot.
1802738,2018-11-16 18:44:35 UTC,"Thank you for providing a patch, and making Ubuntu better."
1802738,2018-11-11 16:32:10 UTC,The change I applied to cdc-acm.c is as follows:
1802738,2018-11-19 23:28:18 UTC,"Hello Joseph,"
1802739,2018-11-11 17:29:22 UTC,"Correct me if I'm wrong, but I don't think ltsp-live is part of ltsp.
I think it was part of edubuntu, which is no longer developed or maintained.
So I assigned the bug to edubuntu, but I don't think anyone will work on an unmaintained project."
1802739,2018-11-11 19:33:06 UTC,"You are right, thanks for bug reassigment and the reply."
1802739,2018-11-11 19:34:18 UTC,"You are right, thanks for bug reassigment and the reply"
1802754,2018-11-16 20:09:17 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1802771,2019-05-22 12:55:00 UTC,"Reviewed:  https://review.opendev.org/657319
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=58de96970940e336c3c4141a31226fbfe3b658a5
Submitter: Zuul
Branch:    master"
1802771,2019-05-06 06:17:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657319"
1802771,2019-04-17 04:04:33 UTC,"Checked this bug. I was able to install etcd without any problem, too. :)"
1802771,2019-04-16 14:00:19 UTC,"I spun up a clean image for Ubuntu 18.04, and I was able to install etcd without any problem."
1802771,2019-04-17 04:20:59 UTC,"It looks like issue has been resolved with the release of 18.04.1 and
18.04.2, also hilariously enough I was able to install openstack for the
first time tonight."
1802772,2018-12-03 09:04:21 UTC,The package has been published and the bug is being set to Fix Released
1802772,2018-11-20 02:54:52 UTC,"3.13.0-163.213~precise1 - generic
Regression test CMPL, RTB."
1802773,2020-03-24 14:55:49 UTC,"> yes, I think the fix would be to detect) if a request comes through the ""old"" assertions.ubuntu.com and in that case use max-format=0 if max-format is not set
"
1802773,2020-02-13 13:52:33 UTC,"> So, iiuc, defaulting to the old format on requests with no explicit ""max-format"" on ""assertions.ubuntu.com"" would fix the issue.
"
1802773,2020-02-07 22:00:09 UTC,"- Snapd 2.17 started sending ""max-format"" when retrieving assertions, released on Nov 2, 2016 [4]."
1802773,2020-02-07 21:51:22 UTC,"Some archaeology:
- Snapd 2.27 switched from ""assertions.ubuntu.com"" to ""api.snapcraft.io"", released on Aug 10 2017 [1][2].
- The assertions service switched json by default around Jan 15 2018 (it was committed on that date, not exactly sure when deployed to production but should be close enough)[3]."
1802773,2020-02-07 22:07:41 UTC,"So, iiuc, defaulting to the old format on requests with no explicit ""max-format"" on ""assertions.ubuntu.com"" would fix the issue."
1802773,2019-04-04 08:58:21 UTC,I'm marking the store side of the bug as confirmed since this prevents anyone from using the images from http://cdimage.ubuntu.com/ubuntu-snappy/16.04/current/
1802773,2018-12-19 15:04:06 UTC,"pedronis, can you complete your comment above? appears to have been cutoff."
1802773,2018-11-12 10:27:03 UTC,"To be clear we do want to keep the new behavior on the snapdevicegw own endpoints, the assertions.ubutnu.com behavior is stricly for backward compatibility but it's fairly confusing curl using"
1802773,2018-11-12 10:08:35 UTC,this is likely related to a configuration change in the store that stopped interpreting missing max-format query param as max-format=0 on assertions.ubuntu.com/v1/assertions/<type>/<primary-key> requests
1802773,2020-02-07 19:49:05 UTC,Not reproducible with the current ubuntu core 16 image from http://cdimage.ubuntu.com/ubuntu-core/16/stable/current/ (dated on 2019-08-06).
1802777,2018-11-22 10:33:01 UTC,"3.2.0-138.184 - generic
Regression test CMPL, RTB."
1802777,2018-11-26 11:52:37 UTC,No verification tests needed for this release.
1802777,2018-12-03 09:10:25 UTC,The package has been published and the bug is being set to Fix Released
1802784,2018-11-11 19:22:32 UTC,"My system is:
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic"
1802789,2018-11-11 23:55:07 UTC,*** This is an automated message ***
1802798,2018-12-11 11:41:13 UTC,"OK, so it wasn't just a dogfood-specific problem.  The new problem seems to be stuff like this:"
1802798,2018-12-11 11:48:27 UTC,"The first occurrence of the ""Exceeded 30 redirects"" failure in our logs was at 2018-06-26 17:05:17; before that updates seemed to be working fine.  Now, that does coincide with us deploying a refactoring of our external bug tracker code, so it could either be that we broke authentication to BMO somehow in the process of that, or else that BMO's authentication arrangements genuinely changed at some point between then and now but that the exact time of that was masked by the bug I fixed in r18836."
1802798,2018-12-07 14:40:32 UTC,Fixed in stable r18836 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18836>.
1802798,2018-11-11 23:26:23 UTC,"I'm seeing stuff like this in logs, which is probably relevant:"
1802798,2018-12-07 16:20:30 UTC,"This change seems to be an improvement as far as it goes and it gets past the previous failure, though authentication fails from our dogfood instance.  This may just be a problem with the configuration on dogfood, so we'll need to see how it behaves on production."
1802800,2018-11-15 13:40:28 UTC,I'm assuming you mean the board and/or footprint editors since you did specify.
1802800,2018-11-15 14:07:01 UTC,"Correct, I wrote this quickly after commenting on this one: https://bugs.launchpad.net/kicad/+bug/1792699 (so that selecting a snap point could replace selecting an item/origin in Position Relative dialog)."
1802806,2018-11-12 11:04:04 UTC,apport information
1802806,2018-11-12 11:04:01 UTC,apport information
1802806,2018-11-12 11:03:59 UTC,apport information
1802806,2018-11-12 11:03:58 UTC,apport information
1802806,2018-11-12 11:03:56 UTC,apport information
1802806,2018-11-12 11:03:55 UTC,apport information
1802806,2018-11-12 11:03:53 UTC,apport information
1802806,2018-11-12 10:57:00 UTC,apport information
1802806,2018-11-12 10:57:04 UTC,apport information
1802806,2018-11-12 10:56:56 UTC,apport information
1802806,2018-11-12 10:56:54 UTC,apport information
1802806,2018-11-12 10:56:52 UTC,apport information
1802806,2018-11-12 10:56:50 UTC,apport information
1802806,2018-11-12 10:56:46 UTC,apport information
1802806,2018-11-12 11:04:06 UTC,apport information
1802806,2018-11-12 10:57:06 UTC,apport information
1802806,2018-11-12 11:04:08 UTC,apport information
1802806,2018-11-12 11:04:27 UTC,apport information
1802806,2018-11-12 11:04:11 UTC,apport information
1802806,2019-03-14 07:05:43 UTC,"Please try rtw88:
https://github.com/lwfinger/rtlwifi_new/tree/rtw88"
1802806,2018-11-12 11:06:01 UTC,exeuted apport-collect 1802806 and report sent
1802806,2018-11-12 11:04:43 UTC,apport information
1802806,2018-11-12 11:04:40 UTC,apport information
1802806,2018-11-12 11:04:36 UTC,apport information
1802806,2018-11-12 11:04:31 UTC,apport information
1802806,2018-11-12 11:04:29 UTC,apport information
1802806,2018-11-12 10:56:45 UTC,apport information
1802806,2018-11-12 11:04:26 UTC,apport information
1802806,2018-11-12 11:04:24 UTC,apport information
1802806,2018-11-12 11:04:23 UTC,apport information
1802806,2018-11-12 11:04:22 UTC,apport information
1802806,2018-11-12 11:04:20 UTC,apport information
1802806,2018-11-12 11:04:17 UTC,apport information
1802806,2018-11-12 11:04:16 UTC,apport information
1802806,2018-11-12 11:04:15 UTC,apport information
1802806,2018-11-12 11:04:13 UTC,apport information
1802806,2018-11-12 11:04:09 UTC,apport information
1802806,2018-11-12 10:56:43 UTC,apport information
1802806,2018-11-12 10:56:49 UTC,apport information
1802806,2018-11-12 10:56:39 UTC,apport information
1802806,2018-11-12 10:40:33 UTC,apport information
1802806,2018-11-12 10:40:31 UTC,apport information
1802806,2018-11-12 10:40:29 UTC,apport information
1802806,2018-11-12 10:40:28 UTC,apport information
1802806,2018-11-12 10:40:26 UTC,apport information
1802806,2018-11-12 10:40:24 UTC,apport information
1802806,2018-11-12 10:40:22 UTC,apport information
1802806,2018-11-12 10:40:21 UTC,apport information
1802806,2018-11-12 10:40:18 UTC,apport information
1802806,2018-11-12 10:40:17 UTC,apport information
1802806,2018-11-12 10:40:13 UTC,apport information
1802806,2018-11-12 10:40:12 UTC,apport information
1802806,2018-11-12 10:40:10 UTC,apport information
1802806,2018-11-12 10:56:41 UTC,apport information
1802806,2018-11-12 10:40:06 UTC,apport information
1802806,2018-11-12 10:40:05 UTC,apport information
1802806,2018-11-12 06:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802806,2018-11-12 10:40:35 UTC,apport information
1802806,2018-11-12 10:40:36 UTC,apport information
1802806,2018-11-12 10:40:09 UTC,apport information
1802806,2018-11-12 10:40:39 UTC,apport information
1802806,2018-11-12 10:40:37 UTC,apport information
1802806,2018-11-12 10:56:37 UTC,apport information
1802806,2018-11-12 10:56:35 UTC,apport information
1802806,2018-11-12 10:56:31 UTC,apport information
1802806,2018-11-12 10:56:30 UTC,apport information
1802806,2018-11-12 10:56:28 UTC,apport information
1802806,2018-11-12 10:56:26 UTC,apport information
1802806,2018-11-12 10:56:22 UTC,apport information
1802806,2018-11-12 10:56:21 UTC,apport information
1802806,2018-11-12 10:56:48 UTC,apport information
1802806,2018-11-12 10:56:16 UTC,apport information
1802806,2018-11-12 10:40:41 UTC,apport information
1802806,2018-11-12 10:40:42 UTC,apport information
1802806,2018-11-12 10:40:45 UTC,apport information
1802806,2018-11-12 10:56:18 UTC,apport information
1802806,2018-11-12 10:40:55 UTC,apport information
1802806,2018-11-12 10:56:12 UTC,apport information
1802806,2018-11-12 10:56:14 UTC,apport information
1802806,2018-11-12 10:40:50 UTC,apport information
1802810,2020-08-18 00:01:41 UTC,"Same deal with Ubuntu 20.04
5.4.0-42-generic
Reader does not show up in lspci or lsusb.  Card works with external reader."
1802810,2019-03-18 13:57:17 UTC,Can confirm this is happening here too. Its the exact same problem
1802810,2019-03-14 07:18:21 UTC,Does this happen after suspend?
1802810,2018-11-13 02:44:04 UTC,apport information
1802810,2018-11-19 06:13:23 UTC,"Comic and Disco use the same linux and grub2 packages at this moment, so it's interesting to see which new package fixes the issue..."
1802810,2018-11-19 05:58:09 UTC,This bug seems to have been fixed when I upgraded to Ubuntu Budgie 19.04
1802810,2018-11-15 21:47:58 UTC,kernel-bug-exists-upstream
1802810,2018-11-15 21:44:42 UTC,"I updated to the latest mainstream kernel 4.20.0-042000rc2-generic  This did not fix the issue, The SD card reader only worked back in Ubuntu 18.04 with one of the 4.15 kernels."
1802810,2018-11-15 21:04:44 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1802810,2018-11-15 21:04:38 UTC,Does this issue go away if you boot back into the prior kernel?
1802810,2018-11-13 02:44:19 UTC,apport information
1802810,2018-11-19 21:28:51 UTC,"Wait, after I updated my system, the reader stopped working. It only seems to work with a clean install of Ubuntu without any reboots or updates."
1802810,2018-11-13 02:44:00 UTC,apport information
1802810,2018-11-13 02:43:58 UTC,apport information
1802810,2018-11-12 04:18:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1802810,2018-11-13 02:44:01 UTC,apport information
1802810,2018-11-13 02:43:45 UTC,apport information
1802810,2018-11-13 02:43:46 UTC,apport information
1802810,2018-11-13 02:43:49 UTC,apport information
1802810,2018-11-12 16:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802810,2018-11-13 02:43:53 UTC,apport information
1802810,2018-11-13 02:43:55 UTC,apport information
1802810,2018-11-13 02:43:56 UTC,apport information
1802810,2018-11-13 02:43:57 UTC,apport information
1802810,2018-11-13 02:43:51 UTC,apport information
1802810,2018-11-13 02:43:52 UTC,apport information
1802813,2018-11-12 03:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802813,2018-12-05 03:11:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1802813,2018-12-20 05:39:13 UTC,This bug was fixed in the package linux-oem - 4.15.0-1030.35
1802813,2018-12-21 18:08:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802813,2019-01-10 10:39:39 UTC,This fix has already been applied to Bionic as part of bug 1808399.
1802820,2018-11-12 16:21:36 UTC,Thank you! It was already helpful to know about libcec4-dev.
1802820,2018-11-12 05:05:18 UTC,This is caused by the raspberry pi foundation packages and needs to be fixed from their side.
1802821,2019-04-22 06:03:41 UTC,"For an adding kernel parameters how-to, please refer to this article:
https://wiki.ubuntu.com/Kernel/KernelBootParameters"
1802821,2018-12-23 21:50:00 UTC,I am a Linux newbie. How do I do what you asked?
1802821,2018-12-23 06:11:12 UTC,"Please try kernel parameter ""usb-storage.quirks=vid:pid:u"", replace vid and pid to the USB device ids."
1802821,2018-12-13 21:25:40 UTC,"After a month of waiting for confirmation of the bug, I have reformatted the partition as ext4. If this works (can copy 1.5TB in less than 2 days) the bug is in the NTFS support in Ubuntu. If it doesn't, I will return the drive (Seagate says it is in warranty but refuses to provide any support to Linux users) and chalk up another Ubuntu bug that is being ignored by the Ubuntu community."
1802821,2018-12-03 06:19:57 UTC,"The bug is in the upstream kernel and in Ubuntu MATE 18.10. Seagate refused to contact you to find out what the problem is. With no response from Ubuntu, I am returning the drive for a refund. Maybe some decade Ubuntu will support drives larger than 5TB (currently the largest from Seagate is 16TB)."
1802821,2018-11-12 05:00:07 UTC,This change was made by a bot.
1802821,2018-11-28 18:17:08 UTC,No! This problem did not start until after I had purchased the drive so any questions about behavior before I mounted the drive are not applicable.
1802821,2018-11-28 18:05:14 UTC,No this problem occurred when I purchased and mounted the 6TB drive.
1802821,2018-11-16 18:41:44 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1802821,2018-11-28 19:18:24 UTC,Am trying upstream kernel v4.20-rc4 (2e6e902d185027f8e3cb8b7305238f7e35d6a436).
1802834,2018-11-12 08:39:14 UTC,apport information
1802834,2018-11-12 08:39:13 UTC,apport information
1802834,2018-11-12 08:01:13 UTC,Here is the journalctl log.
1802834,2018-11-12 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1802834,2018-11-12 08:39:01 UTC,apport information
1802834,2018-11-12 08:39:03 UTC,apport information
1802834,2018-11-12 08:39:05 UTC,apport information
1802834,2018-11-12 08:39:07 UTC,apport information
1802834,2018-11-12 08:39:09 UTC,apport information
1802834,2018-11-12 08:39:11 UTC,apport information
1802834,2018-11-12 08:39:18 UTC,apport information
1802834,2018-11-12 08:39:17 UTC,apport information
1802834,2018-12-12 07:18:32 UTC,"After I resume from suspend, I found the backlight is normal, and here is the log."
1802834,2018-12-17 07:48:01 UTC,"This possibly means brightness value is 0 when systemd-backlight@amdgpu_bl0 saves the brightness, and it clamps its value to 5% of max_brightness which is 12."
1802834,2018-12-12 09:58:35 UTC,"Installed the 19.04 daily image, the kernel  is 4.18.0-11-generic. It works fine. And the brightness value is 255."
1802834,2018-12-12 09:48:02 UTC,"After you install the 18.04 image, it will show the dim screen.
After suspend, the backlight is normal."
1802834,2018-12-12 08:40:05 UTC,"When this issue happens, what's the output of ""grep . /var/lib/systemd/backlight/*""?"
1802834,2018-11-12 08:39:20 UTC,apport information
1802834,2018-11-12 08:39:22 UTC,apport information
1802834,2018-11-12 08:39:26 UTC,apport information
1802834,2018-11-12 08:39:23 UTC,apport information
1802834,2018-11-12 09:00:07 UTC,This change was made by a bot.
1802834,2018-11-16 19:46:25 UTC,Does this issue still happen after applying the latest updates?
1802834,2018-11-19 04:48:48 UTC,"Upgraded to 4.15.0-42 kernel from proposed. And this issue is still exist. And the default value is 12, but the max is 255."
1802834,2018-11-22 05:16:21 UTC,Do you also see the issue on 19.04 daily image?
1802834,2018-11-22 05:59:47 UTC,"No, I didn't, let me try it."
1802834,2018-12-12 07:13:03 UTC, backlight_level = amdgpu_atombios_encoder_get_backlight_level_from_reg(adev);
1802834,2018-11-12 08:39:28 UTC,apport information
1802834,2018-12-12 07:14:37 UTC,"So it looks like the initial brightness is got from atombios of graphic card, so it is atombios issue or the code can't correctly parse the atombios."
1802842,2018-11-12 09:27:07 UTC,"     _ _
    | (_)
  __| |_ ___  ___ ___
 / _` | / __|/ __/ _ \

| (_| | \__ \ (_| (_) |


 \__,_|_|___/\___\___/"
1802842,2018-11-12 09:23:03 UTC,more Disco
1802842,2018-11-12 09:06:55 UTC,works on my machine...
1802849,2018-11-12 10:53:18 UTC,"I know you not suppose to, but I'm commenting on myself"
1802854,2018-11-12 09:26:29 UTC,What about green hair ?
1802858,2018-11-12 09:24:58 UTC,Take the S3!
1802862,2019-06-02 07:55:15 UTC,Fixed in fsm branch rev 421.
1802865,2018-11-12 09:26:52 UTC,Yay!!!
1802865,2018-11-12 09:31:06 UTC,Yes!
1802869,2018-11-12 09:31:35 UTC,check the rabitmq credentials
1802869,2018-11-24 12:19:20 UTC,"hi install Openstack on ubuntu  18 LTS  and  Rokcy  Release
1:15 PM with kolla-ansible, but having problem with ""rabbitmq"":
1:15 PM rabbitmq docker container continously restarting
1:15 PM ""kolla/ubuntu-source-rabbitmq:rocky ""kolla_start"" 6 minutes ago Restarting (1) 47 seconds ago rabbitmq""
1:15 PM and in /var/lib/docker/volumes/kolla_logs/_data/rabbitmq/startup_err => "" Protocol 'inet_tcp': register/listen error:""
1:15 PM /var/lib/docker/volumes/kolla_logs/_data/rabbitmq/startup_log  => ""econnrefused""
1:15 PM als Workarround i doing: docker restart rabbitmq ; docker exec -it -u root rabbitmq  epmd &
1:15 PM and is working, but do you also these Problem ?"
1802870,2018-11-12 09:31:49 UTC,A comment :)
1802897,2018-11-12 11:15:32 UTC,Configs as an attachment since the tracker eats spaces and tabs.
1802901,2018-11-28 13:25:51 UTC,"In Ubuntu we decided to support libapache2-mod-auth-mellon for keystone federation (https://launchpad.net/bugs/1610286). This was based on input from the security team at Canonical that xml-security-c code quality was lacking and it (and Xerces) were not well maintained at the time, and flaws could affect shibboleth. This doesn't solve the problem for this bug but may provide a work-around by using libapache2-mod-auth-mellon instead."
1802901,2018-11-22 11:10:36 UTC,So it seems that this bug is the root cause https://bugs.launchpad.net/ubuntu/+source/xmltooling/+bug/1776489 but no progress or workaround available yet.
1802901,2018-11-20 13:50:24 UTC,"Looks like it's failing here [0]. I haven't seen anything like this recently, but I suppose we could patch that installation script to include other dependencies if needed."
1802901,2018-11-28 13:27:22 UTC,s/Not/Note
1802901,2018-11-28 13:27:14 UTC,Not that libapache2-mod-auth-mellon is in main and will get full security support as of 18.04 LTS.
1802910,2018-11-19 10:05:46 UTC,"Ah, cinder is indeed related to ceph-mon, amongst others:"
1802910,2018-11-12 13:13:10 UTC,"This is using the stable/18.02 versions of the charms, btw."
1802910,2018-11-19 09:25:20 UTC,Tracked this down to a cephx username mismatch. I've use bogus UUIDs here to illustrate.
1802910,2018-11-20 04:29:47 UTC,"Thanks, confirmed that removing the relation and starting again with a fresh volume/instance results in successful attach/detach."
1802910,2018-11-19 10:27:58 UTC,"remove relation should do the right thing - but I'd remove any volumes that
have already been created first"
1802910,2018-11-19 09:43:33 UTC,cinder should be providing the 'cinder-ceph' username as part of the block device setup - can you check that you don't have a direct relation between the cinder charm and ceph-mon as this might cause this problem
1802910,2018-11-27 10:40:17 UTC,Repurposing this bug to deal with dropping the ceph support in the cinder charm.
1802912,2020-01-18 00:25:32 UTC,This bug was fixed in the package s3fs-fuse - 1.85-1
1802912,2019-03-23 14:46:20 UTC,"Why do you say ""Please update s3fs package and dependencies to a newer version."" - do you know this particular case is fixed by something? When you wrote this message there wasn't a new upstream release of s3fs."
1802915,2018-12-15 14:50:05 UTC,"Instead of changing the value, I think there should be a function that determines the ideal ""GUI_REFRESH_INTERVAL_DEFAULT"" value, with the option to override it. That way, monitor greater than 60 Hz can also benefit."
1802915,2018-11-12 13:17:14 UTC,Slow motion clips for host/guest were uploaded as attachments.
1802918,2018-12-18 06:44:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625806"
1802918,2020-07-21 08:56:43 UTC,"Reviewed:  https://review.opendev.org/625806
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=71e50362de6481eb03154a26848903f788f44581
Submitter: Zuul
Branch:    master"
1802919,2018-11-20 06:46:48 UTC,Same bug 1797181
1802919,2018-11-19 10:01:02 UTC,This is Nova bug 1803961
1802923,2018-11-12 16:42:07 UTC,we will not fix this. the work around is to remove libc6-armel-cross and re-install the cross compiler packages.
1802925,2018-11-23 11:12:30 UTC,in progress with https://review.openstack.org/#/c/619049/
1802933,2018-11-12 14:31:27 UTC,"Removing packages from disco:
 spark 2012.0.deb-11build1 in disco
  spark 2012.0.deb-11build1 in disco amd64
  spark 2012.0.deb-11build1 in disco arm64
  spark 2012.0.deb-11build1 in disco armhf
  spark 2012.0.deb-11build1 in disco i386
  spark 2012.0.deb-11build1 in disco ppc64el
  spark 2012.0.deb-11build1 in disco s390x
Comment: LP: #1802933, remove spark and polyorb, not read for gnat 8
1 package successfully removed."
1802944,2019-04-25 12:58:55 UTC,"Hi Richud,"
1802944,2019-06-25 04:17:33 UTC,[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]
1802944,2019-04-25 12:33:26 UTC,"Hi Christian,"
1802944,2019-02-20 10:57:49 UTC,"Hi Christian,"
1802944,2019-03-20 08:13:37 UTC,"Hi Richud,
The upstream feedback sort of repeats our discussion.
Just as I have recommended to use in the meantime e.g. at comment #7 that we could use:
  virsh snapshot-revert <guestname> <snapshot>
  virsh edit <guestname> (set type)
  virsh start <guestname>"
1802944,2019-03-18 14:40:32 UTC,"Well I followed what was ""prior art"" for the option text.
And it is the same text for any edit that is in virsh."
1802944,2019-03-18 14:24:46 UTC,"Hi Christian,"
1802944,2019-03-06 13:26:24 UTC,"Coders usually think ""scripts/APIs first, manual edit maybe later"" therefore I haven't thought of the snapshot-edit yet."
1802944,2019-02-19 15:33:23 UTC,"> Unfortunately it is snapshot-edit that needs a --force to change the machine type , MAC, memory or other tangible item that won't break the snapshot.
> Afraid I don't understand what use that is on snapshot-create tbh., sorry.
"
1802944,2019-02-19 14:01:10 UTC,"Hi,"
1802944,2019-02-14 15:29:33 UTC,FYI - the change for now looks like this http://paste.ubuntu.com/p/bxr3zpQSsN/
1802944,2019-02-14 15:15:58 UTC,"Working for me:
$ virsh snapshot-dumpxml disco-mt-zesty 1550137482 > snapshot.xml
$ vim snapshot.xml
$ virsh snapshot-create disco-mt-zesty snapshot.xml --redefine
error: unsupported configuration: Target domain machine type pc-i440fx-disco does not match source pc-i440fx-zesty"
1802944,2019-02-14 14:18:24 UTC,"The PPA will be https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3651
For now it is still building, but later on we can hopefully try our luck from there."
1802944,2019-03-18 15:50:04 UTC,"Submitted upstream:
https://www.redhat.com/archives/libvir-list/2019-March/msg01170.html
https://www.redhat.com/archives/libvir-list/2019-March/msg01171.html"
1802944,2019-02-14 14:04:05 UTC,"TL;DR:
New option to snapshot-create ""--force""
New Flag: VIR_DOMAIN_SNAPSHOT_CREATE_NOCHECK
only meaningful on --redefine
--force to essentially ignore the same kind of incompatibility as on snapshot-restore (same wording for coherency)"
1802944,2019-02-14 10:36:00 UTC,"The breaking check is in virDomainDefCheckABIStabilityFlags which is meant to:
  This compares two configurations and looks for any differences
  which will affect the guest ABI. This is primarily to allow
  validation of custom XML config passed in during migration"
1802944,2019-02-14 10:23:34 UTC,I updated the description to de-confuse myself and others that might come by.
1802944,2019-02-14 10:20:30 UTC,"And yes - there is no way to ""permanently"" edit the snapshots as their metadata is meant to store the data of the time it was taken."
1802944,2018-11-26 16:09:09 UTC,"Hi Christian,"
1802944,2018-11-23 10:16:17 UTC,"Thanks for the commands btw - I'm just flooded by other higher prio things atm - sorry.
I'm also glad that you could help yourself for your case."
1802944,2018-11-22 13:45:38 UTC,"Hi Christian,"
1802944,2018-11-15 16:01:34 UTC,"Hi Christian,"
1802944,2018-11-14 10:39:38 UTC,"Hi Richud,
first I have to beg your pardon.
I replied to this but only today was made aware that my answer was eaten by the internet demons :-/"
1802944,2019-02-14 13:14:34 UTC,"tools/virsh-snapshot.c
  -> cmdSnapshotCreate collects arguments and sets flags
  -> virshSnapshotCreate does the handling then
     - gets the xml in const char *from
     - flags in unsigned int flags
  -> virDomainSnapshotCreateXML gets xml and flags
  -> impl callback conn->driver->domainSnapshotCreateXML(domain, xmlDesc, flags);
     from src/qemu/qemu_driver.c that is qemuDomainSnapshotCreateXML
  -> virDomainSnapshotRedefinePrep
  -> virDomainDefCheckABIStability <- here the breakage starts complaining about the mismatch"
1802944,2019-03-20 08:17:35 UTC,Status: Incomplete - waiting on Upstream discussion to resolve
1802944,2019-02-14 10:18:04 UTC,"Hi Richud,
finally I had some time to take a deeper look into this again - for too long it was teasing me being unread in my inbox :-)"
1802944,2019-03-18 16:02:07 UTC,"prior art, I like it! -  very diplomatic :)"
1802952,2019-07-26 15:42:26 UTC,"Confirming that with this patch, records with luris but no copies are showing up in the auto-suggestion box on Firefox. A recent Chrome update seems to have broken auto-suggest functionality, so I was unable to test on Chrome. I've pushed a rebased sign-off branch here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1802952_luri_auto_suggest_visibility_signoff"
1802952,2018-11-12 16:57:35 UTC,Branch here:
1802952,2019-10-21 18:11:57 UTC,"Pushed all the way to rel_3_1. Thanks, Dan and Kyle!"
1802953,2018-11-12 16:44:44 UTC,"Ich kann Ihre Nachricht nicht versteheh, das Ganze in Deutsch waere sehr hilfreich."
1802959,2018-12-11 20:52:10 UTC,"changed to low this is a config parameter, it can be updated in the config shipped with the snap but the user can add it to their own config if necessary"
1802959,2020-06-19 05:57:20 UTC,"Since this is now standard in FCE deployments, it should be added to the known charms of the canonical-openstack-rules.yaml."
1802959,2020-08-31 05:33:32 UTC,This should be addressed by 390003 once merged
1802961,2018-11-12 17:24:43 UTC,"StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
 QMessageLogger::fatal (this=this@entry=0x7ffe8f77b4c0, msg=msg@entry=0x55d5aacdcdf0 ""Display server failed to start. Exiting"") at global/qlogging.cpp:796
 SDDM::Display::start (this=this@entry=0x55d5ab686620) at ./src/daemon/Display.cpp:112
 SDDM::Seat::createDisplay (this=0x55d5ab6815b0, terminalId=2) at ./src/daemon/Seat.cpp:81
 SeatAdaptor::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./obj-x86_64-linux-gnu/src/daemon/seatadaptor.moc:116"
1802962,2018-11-15 11:14:02 UTC,"Umm, this also affects dovecot.
Both imported fine in the past."
1802962,2018-11-12 18:13:02 UTC,"I will need to check, but this is probably due to known issues with ""gbp
import-orig"" which causes it to sometimes not work."
1802962,2018-11-15 16:02:05 UTC,"On Thu, Nov 15, 2018 at 03:38:59PM -0000,  Christian Ehrhardt  wrote:

> Detail:
> We want to `git ubuntu export-orig` what is imported at the Debian
> import when doing a merge.
"
1802962,2018-11-15 16:27:13 UTC,"As we just talked about it:
1. fallback is not working
2. I want proper pristine tar if possible"
1802962,2019-06-04 13:00:01 UTC,"Hey,
qemu is also affected but I found something interesting at least for .xz archives.
The import will do soem re-compressions and checks.
That fails with .xz but not with .gz on qemu."
1802962,2018-11-15 15:38:59 UTC,"> What's your use case that is broken by the pristine tar data being
> missing?
"
1802962,2018-11-15 13:37:05 UTC,"What's your use case that is broken by the pristine tar data being
missing?"
1802963,2018-11-12 17:34:51 UTC,Maybe make the tolerance a netclass property? So that you can make your RAM DQ signals be their own netclass and inherit tolerance settings from that?
1802963,2018-11-12 21:15:20 UTC,AFIK the length of the vias are not considered in the length calculations. These should probably also be handled in some way.
1802963,2018-11-12 22:03:00 UTC,"Via length is not considered in the current length matching implementation, however adding that should probably be a separate issue. This issue is specifically for adding tolerance to the length, unrelated to how the length is calculated."
1802964,2018-11-13 09:12:08 UTC,"There is already a parameter to enter a difference in length in pad settings dialog:
""Pad to die length"""
1802964,2018-11-13 20:28:15 UTC,"Hmmm. If we're going to support that it would probably still be good to allow creating an offset in the middle of the board (say, between passives) as well."
1802968,2020-09-13 11:25:38 UTC,It also affects bond and bridge interfaces :
1802968,2019-03-25 22:34:07 UTC,"Running netplan apply a second time seems to fix this, at least in bionic with netplan.io 0.40.1~18.04.4."
1802971,2019-03-18 17:43:38 UTC,"no longer an upstream job, moved to standalone"
1802971,2018-11-13 22:49:36 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/617845"
1802971,2018-11-13 09:02:23 UTC,"From both the logs, after ssh into cirros image, it tries to find the instance-id of the data source but it failed:
checking http://169.254.169.254/2009-04-04/instance-id
2018-11-12 17:40:46 |     failed 1/20: up 188.34. request failed
2018-11-12 17:40:46 |     failed 2/20: up 190.71. request failed
2018-11-12 17:40:46 |     failed 3/20: up 192.88. request failed
2018-11-12 17:40:46 |     failed 4/20: up 195.14. request failed
2018-11-12 17:40:46 |     failed 5/20: up 197.43. request failed
2018-11-12 17:40:46 |     failed 6/20: up 199.58. request failed
2018-11-12 17:40:46 |     failed 7/20: up 201.87. request failed
2018-11-12 17:40:46 |     failed 8/20: up 203.99. request failed
2018-11-12 17:40:46 |     failed 9/20: up 206.25. request failed
2018-11-12 17:40:46 |     failed 10/20: up 208.38. request failed
2018-11-12 17:40:46 |     failed 11/20: up 210.69. request failed
2018-11-12 17:40:46 |     failed 12/20: up 212.93. request failed
2018-11-12 17:40:46 |     failed 13/20: up 215.10. request failed
2018-11-12 17:40:46 |     failed 14/20: up 217.41. request failed
2018-11-12 17:40:46 |     failed 15/20: up 219.55. request failed
2018-11-12 17:40:46 |     failed 16/20: up 221.85. request failed
2018-11-12 17:40:46 |     failed 17/20: up 223.98. request failed
2018-11-12 17:40:46 |     failed 18/20: up 226.26. request failed
2018-11-12 17:40:46 |     failed 19/20: up 228.43. request failed
2018-11-12 17:40:46 |     failed 20/20: up 230.67. request failed
2018-11-12 17:40:46 |     failed to read iid from metadata. tried 20
2018-11-12 17:40:46 |     no results found for mode=net. up 232.92. searched: nocloud configdrive ec2
2018-11-12 17:40:46 |     failed to get instance-id of datasource
2018-11-12 17:40:46 |     Top of dropbear init script
2018-11-12 17:40:46 |     Starting dropbear sshd: failed to get instance-id of datasource"
1802971,2018-11-13 09:34:42 UTC,"Based on discussion with slawq on #tripleo channel, http://logs.openstack.org/03/616203/9/gate/tripleo-ci-centos-7-standalone/75f1be5/logs/undercloud/home/zuul/tempest.log.txt.gz#_2018-11-12_17_40_46 ->  it don't even have fixed IP configured
The first instance works fine but the second instance fails."
1802971,2018-11-13 10:13:02 UTC,We need  dnsmasq logs from neutron_dhcp container in order to investigate and find out what is going wrong.
1802971,2018-11-13 10:57:11 UTC,"Probably relevant, I can see the following in the journal logs."
1802971,2018-11-13 11:30:19 UTC,"@Rabi: I don't think it's related as it is about different network.
Id of network used in failed test was: 783701e2-8acc-4cb8-ab8a-c7040f549475 and I found only logs like:"
1802971,2019-04-10 14:27:20 UTC,"Reviewed:  https://review.openstack.org/635478
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=ed1364ecbcf829c29fff708ee025bc09209e7faa
Submitter: Zuul
Branch:    master"
1802971,2018-11-13 20:05:11 UTC,hrm.. is it possible that this will fix the issue in tripleo? https://review.openstack.org/#/c/617022/
1802971,2018-11-13 22:13:06 UTC,https://review.openstack.org/#/c/617022/ isn't going to help as nothing uses this environment file.
1802971,2018-11-12 20:10:14 UTC,http://logs.openstack.org/22/617022/1/gate/tripleo-ci-centos-7-standalone/fad33fa/logs/stackviz/#/testrepository.subunit
1802971,2019-03-18 17:44:41 UTC,"disregard last statement, that was for another bug"
1802971,2018-11-21 01:00:02 UTC,"Reviewed:  https://review.openstack.org/617913
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=5102788c23e8984bd13e48377682d77f8d9065c6
Submitter: Zuul
Branch:    master"
1802971,2018-11-26 12:57:14 UTC,it seems Slawek is already looking at this.
1802971,2019-01-02 21:02:09 UTC,Any updates?
1802971,2019-01-28 15:26:02 UTC,"Do You have any link to logs with such issue? Originally reported logs are now not available anymore.
Or maybe You have log stash query to find such issues in current runs?"
1802971,2019-02-07 11:22:44 UTC,"from the latest run of standalone, http://logs.openstack.org/93/604293/128/check/tripleo-ci-centos-7-standalone/9e35890/logs/stackviz/#/testrepository.subunit/test-details/tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_port_security_macspoofing_port is passing."
1802971,2019-02-07 11:28:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/635478"
1802971,2019-02-07 11:28:45 UTC,https://review.openstack.org/635478 added review for unskipping bootvolume pattern to get some logs why it is failing.
1802971,2019-02-11 09:20:34 UTC,From patch https://review.openstack.org/635478 it looks for me that this test if now working fine.
1802971,2018-11-14 01:18:24 UTC,"Reviewed:  https://review.openstack.org/617845
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=a554bed7e00599f9fa32abe1d15eb2df0dd62aa8
Submitter: Ian Wienand (<email address hidden>)
Branch:    master"
1802973,2019-06-14 08:42:40 UTC,Thanks for letting me know.
1802973,2019-06-13 23:03:59 UTC,Nova does not currently have support for neutron ports without an ip.
1802976,2019-05-14 19:31:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802976,2019-08-26 12:19:51 UTC,"From the description it sound similar to my problem with a Ryzen5 2500U:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825554"
1802982,2018-11-13 09:23:06 UTC,Thank you for your bug report. Could you take a screenshot of the dialog you see and describe how you trigger it? The Ubuntu One account is only used for reviews I think?
1802982,2018-11-14 13:05:44 UTC,"After the system is restarted, the Ubuntu One account gets disconnected for no obvious reason."
1802982,2018-11-14 13:08:55 UTC,"And to add more information to this bug, there is no dialog informing me that the Ubuntu One account got disconnected, it just happens by itself. I have to keep logging in every time I start the system (I don't do it every time, because this has been happening for sometime now)."
1802982,2018-11-14 13:12:41 UTC,"Also, I don't know if this is important, but I have my Ubuntu Single Sign-On account connected to the system, I think that GNOME Software should use this to stay connected to Ubuntu One, instead of having to do that by itself."
1802982,2018-11-20 09:31:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802982,2018-11-25 23:41:54 UTC,"Bug does not effect disco. I checked. As a workaround, you can download all the related packages from disco and the login issue will be resolved. Maybe the devs can find out what changed and backport it?"
1802982,2018-11-27 19:37:46 UTC,Actually the bug does effect disco. Noticed it again after a few app openings.
1802982,2019-09-29 16:19:27 UTC,This still affects Ubuntu 19.04 and 19.10.
1802982,2018-11-14 12:53:35 UTC,"This is after getting logged in with the Ubuntu One account on Ubuntu Software. And yes, it is used for programs reviews."
1802983,2019-11-08 23:28:56 UTC,"I cannot find any image or text containing ""openstack service list"". Please advise."
1802984,2018-11-13 10:30:05 UTC,What are the steps to reproduce? Any error log?
1802987,2019-01-28 12:22:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802993,2018-11-13 08:55:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802993,2018-11-13 08:57:38 UTC,looks similar to bug #1794292
1802993,2018-11-13 09:39:46 UTC,Reported upstream https://gitlab.freedesktop.org/plymouth/plymouth/issues/70
1802994,2018-11-27 07:37:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1802994,2019-02-12 20:32:52 UTC,I have the same issue (crashes as soon as I press any key on the keyboard. I could use the mouse without any issue) ever since I switched to GnuCash 3.4 (from v2.6.19)
1802994,2018-11-12 22:29:00 UTC,apport information
1802994,2019-02-12 20:35:49 UTC,"If I ""sudo gnucash"" then it runs fine without crashing."
1802994,2019-03-09 17:37:55 UTC,"I'm too affected by this bug and a backtrace shows the crash occurs near im-xim.so, which is the X input method. After clearing the environment variable GTK_IM_MODULE (which was set to xim) the crash disappears, although now my keyboard is badly broken since I heavily rely on XCompose to input all sorts of letters."
1802994,2020-02-02 08:32:26 UTC,I experience the same problem in Linux Mint with gnuash version 3.8
1802994,2020-05-27 01:50:07 UTC,This crash just started happening to me in the past week. Ubuntu 18.04 with gnucash 3.8. Running as root solves the problem for me as well.
1802994,2018-11-12 22:29:02 UTC,apport information
1802994,2018-11-12 22:29:01 UTC,apport information
1803001,2019-06-02 07:46:15 UTC,"This was delayed for a long time, but I just published some revisions to the fsm branch which include a solution for this feature request."
1803001,2018-11-14 03:09:27 UTC,"Thanks, looks like you helped Texas_Ace quite a bit.  :)"
1803001,2019-06-02 07:48:53 UTC,"Oh, um, I didn't change the default to release-off.  I tried it, and it works...  but yuck.  It makes all multi-press actions awkward to use, and can easily confuse people who want to turn the light off and then turn it back on in a different mode...  because it can't be turned back on until a moment after it shuts off.  If they try to turn it back on too soon, it'll be interpreted as a multi-click event instead."
1803002,2019-10-08 09:33:02 UTC,SELinux policy for snapd has undergone substantial changes in the last ~year with all observed alerts fixed. Please re-check with latest Fedora and open a new bug if needed. Thank you.
1803003,2018-11-13 07:14:18 UTC,"Change abandoned by Jude Cross (<email address hidden>) on branch: master
Review: https://review.openstack.org/617394
Reason: looks like we already do this."
1803003,2018-11-13 18:29:40 UTC,"This may be caused by a nova bug in mitaka, will investigate further. My original assumption on the cause of this issue was incorrect."
1803003,2018-11-12 23:36:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/617394"
1803012,2018-11-22 11:45:36 UTC,"Similar to https://bugs.launchpad.net/juniperopenstack/+bug/1803537, this issue was probably caused by older version of virtio NIC drivers for Windows. Update of virtio-win drivers to a 0.1.141 version, newest at the moment, should resolve the issue."
1803013,2018-11-15 11:40:48 UTC,Not sure how selinux fail is related to windows
1803013,2018-12-06 10:16:59 UTC,"This bug was probably caused by this issue https://bugs.launchpad.net/juniperopenstack/+bug/1802380, which was unrelated to Windows."
1803016,2019-07-22 03:45:08 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1803016,2018-11-13 02:12:36 UTC,Please run this command to automatically send more system information:
1803016,2018-11-13 14:34:25 UTC,apport information
1803016,2018-11-13 14:34:28 UTC,apport information
1803016,2018-11-13 14:34:31 UTC,apport information
1803016,2018-11-13 14:34:33 UTC,apport information
1803016,2018-11-13 14:34:35 UTC,apport information
1803016,2018-11-23 21:05:59 UTC,Hello any update ?
1803016,2019-02-20 19:23:55 UTC,I have the same issue.  And progress on this bug?
1803016,2019-02-21 01:28:46 UTC,The next step would be to report the problem to the PulseAudio developers here:
1803016,2019-03-21 23:21:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803016,2018-11-13 14:34:29 UTC,apport information
1803021,2019-02-10 10:50:35 UTC,That's not easy to do.  Let me quote from my first reply:
1803021,2019-02-17 15:11:04 UTC,"Oh, that's handy, thank you Max."
1803021,2019-01-22 06:50:26 UTC,This issue is about error message. Not a support request.
1803021,2019-02-06 03:10:32 UTC,"Then let me change it to wontfix, which description is ""Doesn't fit with the project plans, sorry."" that literally matches my intentions."
1803021,2019-02-10 10:21:21 UTC,"Thanks! That's much better. =) As a minimal workaround, can you replace the text"
1803021,2019-02-10 12:35:36 UTC,I see that translations is the primary concern even though the spurious error message in English is much worse than friendly explanation in English.
1803021,2019-02-17 14:59:39 UTC,"fixed upstream for 1.0-alpha:
https://gitlab.com/inkscape/inkscape/commit/b928f75a6e40661f9e2dff482d738a536276764a"
1803021,2019-01-16 12:34:29 UTC,"They are in the separate inkscape-tutorials package, please install that and it will work.  See LP: #238276"
1803021,2019-02-17 15:32:03 UTC,I guess this makes also sense to back-port to 0.92.x for us. Would you mind crating an MR Max (or just commit directly; I think you have permissions)?
1803021,2019-02-17 15:48:21 UTC,"I know, but the thing is that I haven't heard of any real transition plan, I just know that the issue tracker is open on gitlab and you welcome bugs there."
1803021,2019-02-17 15:51:57 UTC,Committed the patch in debian.
1803021,2019-02-17 16:14:27 UTC,"> I know, but the thing is that I haven't heard of any real transition plan.
"
1803021,2019-02-17 18:18:56 UTC,Backported to 0.92.x (will be released as 0.92.5). https://gitlab.com/inkscape/inkscape/merge_requests/533/
1803021,2019-03-23 15:10:17 UTC,This bug was fixed in the package inkscape - 0.92.4-3
1803021,2019-05-31 13:53:25 UTC,"@Mattia Where would be the right place to report the underlying issue: ""Installing inkscape/gimp/... does not install the help, contrary to what most users expect"" ?"
1803021,2019-05-31 15:49:29 UTC,"But Inkscape never shipped the ""help"", that's online (at least here, clicking ""help"" → ""Inkscape manual"" opens a webpage).  For the tutorials, in my opinion not installing them by default is a feature, as I'm very happy to do without some extra 55 MB."
1803021,2019-07-04 10:11:38 UTC,"Thanks everyone for fixing the error message. It is better now. Although I would argue that adding 25% package size to help onboarding new users to Inkscape is nothing compared to the fact that many users will not be installing those docs, because they are not aware that these docs are not a plain text, but actual SVG files used to practice by doing. Anyway, this should be measured to draw any conclusions."
1803021,2019-02-05 17:51:21 UTC,"It is okay if you don't have time to patch the string, but closing this as invalid is like saying everybody else that they should not do this either. I can not appreciate such collaboration over UX. Sorry."
1803021,2019-01-22 08:28:56 UTC,"Right, and the error message goes away once you install that package."
1803028,2019-04-24 07:35:50 UTC,According to the link that you pasted here:
1803028,2019-04-24 07:37:34 UTC,"Can you still reproduce this with the latest HWE kernel?
It looks like we already have them in 4.18
Thanks."
1803028,2019-06-24 04:17:19 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1803029,2019-08-22 04:09:45 UTC,"Reviewed:  https://review.opendev.org/677675
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=25c9d10cdd06074786840bca2698239b6c9711c6
Submitter: Zuul
Branch:    stable/stein"
1803029,2019-11-06 01:14:32 UTC,This issue was fixed in the openstack/kolla 9.0.0.0rc1 release candidate.
1803029,2019-09-09 09:19:39 UTC,This issue was fixed in the openstack/kolla 8.0.1 release.
1803029,2019-09-09 09:19:09 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.1 release.
1803029,2019-09-09 09:18:35 UTC,This issue was fixed in the openstack/kolla 7.0.4 release.
1803029,2019-08-23 07:53:17 UTC,"Reviewed:  https://review.opendev.org/677680
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=f3331fcd2dca8baaab5afeaaa6d251304dba1dbc
Submitter: Zuul
Branch:    stable/rocky"
1803029,2019-08-22 10:27:41 UTC,"Reviewed:  https://review.opendev.org/677679
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=510c2d8f9583970a48fd1d66cfa4d00e0395a0c7
Submitter: Zuul
Branch:    stable/stein"
1803029,2019-08-21 09:04:54 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/677680"
1803029,2019-08-21 09:03:58 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/677679"
1803029,2019-08-21 09:00:16 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/677675"
1803029,2019-08-20 20:15:23 UTC,"Reviewed:  https://review.opendev.org/668410
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=120e8080ab57d79a7ae4b51d3215b98222aab29e
Submitter: Zuul
Branch:    master"
1803029,2019-08-19 15:50:35 UTC,"Reviewed:  https://review.opendev.org/668409
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=eb7c730e057082eadab5c01ef845f65bb5cf47c4
Submitter: Zuul
Branch:    master"
1803029,2019-07-01 10:26:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668410"
1803029,2019-07-01 10:20:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668409"
1803029,2019-11-11 15:39:47 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1803030,2018-12-03 16:14:08 UTC,"I think it's reasonable to inform the user about the issue, rather than crashing without an explanation."
1803030,2018-12-03 08:55:55 UTC,"I think it's good that Mojo chokes on these, it helps us identify charm bugs."
1803031,2019-02-01 15:07:55 UTC,"Indeed, but we should really be catching these errors earlier, when the installer is running and the user is partitioning."
1803031,2019-01-30 21:43:40 UTC,Here is the error message from UbiquitySyslog.txt:
1803031,2019-02-08 23:21:05 UTC,This bug was fixed in the package partman-efi - 71ubuntu5
1803031,2018-12-05 10:45:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803031,2019-02-05 09:28:23 UTC,Thanks for working on that one! Some questions
1803031,2019-02-05 16:50:56 UTC,"yes, you install using a recent daily. That should be enough, but otherwise you can upgrade to the new ubiquity from -proposed."
1803031,2019-02-05 17:00:40 UTC,"Thanks Mathieu, that's indeed an improvement (""go create an EFI"" doesn't seem like something obvious/that non technical users would figure out but it's already better than saying nothing and failing install later on)"
1803031,2019-02-05 19:49:18 UTC,Verification done with ubiquity 18.04.14.12 / partman-efi 71ubuntu2.2:
1803031,2019-02-08 21:50:38 UTC,This bug was fixed in the package partman-efi - 71ubuntu2.2
1803031,2019-02-08 21:50:44 UTC,"The verification of the Stable Release Update for partman-efi has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1803031,2019-02-01 20:51:58 UTC,I would like to see a more complete set of test cases here for SRU verification.
1803031,2019-02-05 07:51:50 UTC,"Hello Vinicius, or anyone else affected,"
1803031,2019-03-01 18:33:09 UTC,"Hello Vinicius, or anyone else affected,"
1803031,2019-04-23 09:26:48 UTC,This bug was fixed in the package partman-efi - 71ubuntu4.1
1803031,2019-11-10 10:00:51 UTC,"I have spent far too long trying to install kubuntu 18.04.3 on an old HP box that has a recent installation of Windows 10:  i7, 16 GB ram, 1TB HDD, SSD.  C: has been shrunk to ~500 GB and new partitions created for  /, swap and /home.  Installation fails while copying files at ~83%.  Sometimes 276 packages have been updated, although not by the installer.  Installation media both DVD (verified) and Rufus-USB."
1803031,2019-12-08 11:31:55 UTC,"Eventually I abandoned this.  The installer always made encouraging 'nearly there' comments before hard-crashing with around 85% files copied.  The check of install media found no problems, with either release or daily images, and I had tried shrinking the windows partitions by different amounts before reformatting /, swap and /home, and with or without a second efi partition and nomodeset."
1803031,2020-11-10 12:02:04 UTC,"same happend for me in groovy (bios mode/Disklabel type: dos).
) Even I verrified live-session was boot in bios mode."
1803031,2019-04-16 18:10:08 UTC,Verification-done on cosmic with partman-efi/71ubuntu4.1:
1803031,2019-02-01 20:57:06 UTC,"Hello Vinicius, or anyone else affected,"
1803043,2018-11-13 06:04:48 UTC,ps...version is Cosmic
1803043,2018-11-13 17:07:06 UTC,What desktop environment are you using? Could you please add a screenshot of the dialog to which you are referring? Thanks in advance.
1803043,2018-11-14 01:06:25 UTC,LXDE. Screenshot attached. It appears to actually append the current working directory. I was in /tmp when I ran the command.
1803045,2020-07-16 02:10:16 UTC,Fixed in version fs-uae/2.8.4+dfsg-2
1803045,2018-12-15 15:10:36 UTC,I am the maintainer of the original Debian package fs-uae and I have already fixed the bug in Debian. Someone on the Ubuntu side needs to trigger an update of the imported sources from Debian.
1803045,2020-07-16 02:09:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803078,2019-09-08 16:29:40 UTC,"It was worked around in totem, but ultimately was a bug in mutter, which I also fixed."
1803078,2018-11-14 06:20:43 UTC,"It may be considered a bug in Totem, actually. Is it OK for it to ask D-Bus to launch the Gnome screensaver in the first place, while not running in a Gnome session?"
1803078,2018-11-14 11:00:44 UTC,Should be fixed in https://gitlab.gnome.org/GNOME/totem/merge_requests/20
1803078,2019-09-02 18:37:46 UTC,"This seems only a totem issue (and now solved), or I'm wrong?"
1803078,2019-09-08 16:39:55 UTC,"Never mind, I confused this bug with another screensaver one."
1803078,2018-11-13 07:49:01 UTC,"This is where my technical knowledge is reaching its current boundaries. Based on what I saw in this Arch forum thread[1], it seems possible to block certain services from starting up in `/usr/share/glib-2.0/schemas/org.cinnamon.SessionManager.gschema.xml`. There is an `autostart-blacklist` key, but maybe there is also a way to block Totem from requesting `org.gnome.ScreenSaver` even at a later point?"
1803080,2018-11-13 09:43:12 UTC,Some more rule examples:
1803080,2018-11-13 09:46:12 UTC,"We do not tolerate any slandering or disrespect of ANY kind, in ANY context, towards ANYONE."
1803080,2018-11-14 20:18:41 UTC,"The rules should be as short as possible, otherwise they won't be read at all. They should also be understandable to non native english speakers, so simple english is wanted, at least by me :-D"
1803080,2018-11-14 21:28:58 UTC,"My 2 cents on this: I am a fan of a code of conduct and if we establish something, we should not limit it to the forum, but to all interactions related to Widelands. I personally think a CoC must contain both the rules and values, but also the action taken when it is violated. One of my favorite ones is the one from the Rust community, which I think we can in large parts just steal:"
1803080,2019-09-06 08:18:09 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/290
1803083,2018-11-23 04:21:53 UTC," yes, like ""10.1"",If we enter 10.1，The chart changes are not what we expected"
1803083,2018-12-29 13:01:44 UTC,The proposed review is https://review.openstack.org/#/c/617519/
1803083,2018-11-20 18:21:00 UTC,"Do you mean something like ""10.1""?"
1803121,2018-11-13 12:04:16 UTC,"Also, if a questionnaire starts, in the middle of it, it may stop working, giving an error that the token as been used."
1803121,2019-01-02 14:03:23 UTC,"Dear Adam,"
1803121,2018-11-15 01:19:55 UTC,Thanks for this report.
1803121,2019-01-16 04:21:09 UTC,I have fixed the warnings so it should work with php 7.2/7.3 now. A new session should not be created - but the existing one should be continued.
1803126,2018-11-16 08:59:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803126,2019-04-15 21:29:41 UTC,KDE neon also afected
1803127,2019-03-11 10:55:43 UTC,"Ubuntu Mate 18.04
1.2.0-rcgit-29 (git rcgit-29)"
1803127,2019-03-11 10:56:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803127,2019-04-11 18:00:21 UTC,Also affecting me on KDE Neon with Remmina 1.2
1803127,2019-05-17 05:37:45 UTC,*nudge* Need this security very badly.
1803127,2019-05-17 07:21:55 UTC,That should probably be reported upstream on https://github.com/FreeRDP/Remmina
1803132,2018-11-15 04:43:46 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1803132,2019-07-30 10:27:38 UTC,"Closing, fixed mostly everywhere"
1803135,2018-11-13 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803135,2018-11-13 14:11:55 UTC,apport information
1803135,2018-11-13 14:11:58 UTC,apport information
1803135,2018-11-15 02:20:45 UTC,"Pooja, you are using an unsupported mainline kernel 4.19.0-041900rc4-lowlatency. If you boot back to the official v4.15 kernel do you still have the problem?"
1803135,2018-11-15 07:09:43 UTC,"Thanks Anthony,
I could try doing that.
In case you have the instructions/help-page for installing v4.15, please let me know."
1803135,2018-11-21 08:30:17 UTC,"Hello,
thanks for the reply.
well, I had loads of issue in installing a stable working Ubuntu in Thinkpad and therefore also I went through series of problem fixing solutions. In short, there is a higher chance that I played around with Grub, but can not confirm. Besides, I am not much into Grub settings.
Please find the info of my Grub, and guide me further which one I have got and which one I should have [1].
Also, one more important requirement for me is that I am running my work-windows 10 in Oracle VM, that should also be compatible with the Grub."
1803135,2018-11-16 01:15:17 UTC,"Pooja, you don't really need to install that explicitly, since it is the default when you installed 16.04.5, unless you have accidentally removed it. Can you see that in the grub menu?"
1803136,2019-10-29 22:24:31 UTC,This looks like there's a bit more than only bugfixes in here.
1803136,2019-12-19 11:41:57 UTC,"Seems the SRU makes gnome-calculator fail to rebuild. The fix is
https://gitlab.gnome.org/GNOME/gnome-calculator/merge_requests/17
but it seems problematic that a SRU update leads to source no being rebuildable..."
1803136,2020-01-27 12:25:31 UTC,"The verification of the Stable Release Update for vala has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1803136,2020-01-27 12:25:22 UTC,This bug was fixed in the package vala - 0.40.17-0ubuntu1
1803136,2020-01-21 09:30:50 UTC,The gnome-calculator new SRU is including the fix needed to build with the new vala. It's a bit unfortunate that a stable vala update is leading to build failures but seems it's the wait it is and that one has been handled so the SRU seems fine to be released now
1803136,2020-01-20 16:58:45 UTC,"Ok, I see that there is a new gnome-calculator in the archive, so I assume the build failure was some red herring? The package aged sufficiently long for it to be releasable, but I'd like to know how we stand with the build failure situation before proceeding."
1803136,2020-01-16 18:31:55 UTC,"I have been running a few applications (simple-scan, gnome-calculator and plank) compiled with vala 0.40.17 from -proposed without issues for the last weeks."
1803136,2019-10-30 00:16:38 UTC,"Hello Rico, or anyone else affected,"
1803136,2019-12-20 13:59:14 UTC,@seb128 The build test went fine at the time: https://launchpad.net/~ricotz/+archive/ubuntu/vala-sru/+sourcepub/10687929/+listing-archive-extra
1803136,2019-10-14 14:09:59 UTC,vala - 0.40.17-0ubuntu1 package is available here
1803136,2019-09-19 07:13:58 UTC,vala - 0.40.16-0ubuntu1 package is available here
1803136,2019-04-20 18:53:37 UTC,Unsubscribing the Ubuntu Sponsors Team as there is nothing to sponsor; could you please attach a debdiff and resubscribe?
1803136,2019-04-18 14:52:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803136,2019-02-26 14:37:19 UTC,"Updating to current bugfix version is worth doing, that's not a rls goal/something the desktop team was to own though, tagging rls-bb-notfixing (it doesn't prevent the SRU to be worked on still)"
1803136,2019-10-29 22:43:17 UTC,"I have done mass-rebuild (with 0.40.11) as can be seen in the bug description. (I have deleted the dedicated PPA some time ago). Of course this was outdated given the age of this bug report. I can trigger another one, this will also show many unrelated build issues though."
1803138,2019-02-26 14:39:44 UTC,"Updating to current bugfix version is worth doing, that's not a rls goal/something the desktop team was to own though, tagging rls-bb-notfixing (it doesn't prevent the SRU to be worked on still)"
1803138,2019-04-20 18:53:44 UTC,Unsubscribing the Ubuntu Sponsors Team as there is nothing to sponsor; could you please attach a debdiff and resubscribe?
1803144,2019-12-30 23:58:27 UTC,"Have you tried to disable the UFW
sudo ufw disable
to check if the Firewall is interfering? You can enable it again with
sudo ufw enable
if the firewall it not the culprit."
1803145,2018-11-14 13:23:38 UTC,This may be a duplicate bug report.
1803145,2019-01-07 12:29:45 UTC,"I Think this is a great idea as well, and I have to say I would love to see something like the diptrace component editor added with how they do attached patterns. It would be nice to be able to take one symbol and use it for a family of parts, so that you actually end up linking a single symbol to all the packages it could come in under one family. It would be really helpful for the medium size cortexes where they have both a qfp and a bga package but they are still ~200 pins and no one wants to make multiple symbols for the two packages. Though this would mean you could have some pins that are not connected on all packages and that may be an issue."
1803155,2018-11-13 16:27:22 UTC,+1
1803167,2018-11-25 18:47:14 UTC,"Tried RLE and it looks a lot better, uploaded a build here:
https://zeroflow.at/flashlight/anduril_RLE_working.zip"
1803167,2018-11-14 03:47:45 UTC,"This is an interesting idea.  I wonder if it should use run-length encoding to decrease the size even more.  It's pretty simple to implement, and can compress any number of runs within each table."
1803168,2018-11-14 14:30:42 UTC,"Hi, your system appears to have an invalid init.d script which is causing boot ordering failures"
1803171,2018-11-13 18:30:07 UTC,This change was made by a bot.
1803171,2018-11-16 19:44:21 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1803171,2018-11-18 09:33:01 UTC,"It is on a new laptop (lenovo 300e winbook), not after an upgrade. I've had 18.04 and 18.10 installed. The HW is OK (problem is not there with windows 10). The touchpad is"
1803171,2019-05-21 16:37:47 UTC,Does the bug still exist?
1803171,2019-11-21 16:53:39 UTC,"Milan, can you please file a separate new bug? It's a different case for HP laptops."
1803171,2019-11-16 20:36:57 UTC,I can confirm the bug still exists. HP 15-db1041nm (AMD Ryzen 5 3500U).
1803173,2018-11-26 16:58:03 UTC,"Hi.
I added a 'linux' package task here.  It seems that in bug 1551419 patches were added
to the ubuntu kernel to do the right thing.  Possibly those patches were inadvertantly
dropped?  Either way, it seems like the [Ubuntu] kernel should promise this consistently
so that multiple consumers do not need to all know about this issue and handle it
themselves."
1803173,2018-11-22 03:49:15 UTC,Marking this New so we can re-look at it as this feels like case insensitivity in UUID matching is something we really should be handling.
1803173,2018-11-26 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803173,2018-11-26 17:02:11 UTC,"Hi Adrian,"
1803173,2018-11-26 19:53:53 UTC,"Hi,
I recreated the issue using the Ubuntu upstream kernel builds at
  http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/"
1803173,2018-11-29 20:37:22 UTC,Thanks All.
1803173,2018-11-21 19:36:51 UTC,"Hello,"
1803173,2018-11-13 20:22:26 UTC,"Hi,
Please attach the tarball created by running 'cloud-init collect-logs'.
Then set the status back to New."
1803174,2018-11-13 19:19:08 UTC,Also reported on gitlab here:
1803174,2020-01-07 20:43:58 UTC,"Upstream report closed 2018-11-29, no action taken.
Further to comment #2 by reporter, closing."
1803174,2018-11-29 15:37:47 UTC,New info...
1803179,2019-11-10 11:32:00 UTC,"(In reply to Kai-Heng Feng from comment #145)

> Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM
> will disable the power of the card.
> After nvidia.ko gets unloaded, make sure ""power/control"" is ""auto"" for its
> video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and its upstream
> bridge (use lspci -t to check).
>
> In addition to that, these two commits are also required for mainline kernel
> users:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
> ?id=52525b7a3cf82adec5c6cf0ecbd23ff228badc94
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
> ?id=bacd861452d2be86a4df341b12e32db7dac8021e
"
1803179,2019-11-11 16:22:42 UTC,on Which kernel (of the mainline) the patches are applied. Is it coming soon or I have to apply the patches myself.
1803179,2019-11-12 23:22:47 UTC,I've tryed the patches and can confirm that the issues with lockups are gone with just using bumblebee (unloading nvidia module).
1803179,2019-11-12 23:26:45 UTC,Of course I've set the power to auto for everything
1803179,2019-11-12 23:31:06 UTC,More infos:
1803179,2019-11-18 23:55:08 UTC,"Ok after I removed the patches and the normal Kernel-Update to 5.3.11 happend, I'm experiencing the same higher power consumption that happend during the test before."
1803179,2019-12-29 22:41:40 UTC,ok I've found out that this difference seems to be gone when using tlp instead of laptop-mode-tools.
1803179,2020-02-09 14:44:50 UTC,"Are these patches included in kernel 5.5.2? I blacklist nvidia modules on boot, and  ""echo 'OFF' | sudo tee /proc/acpi/bbswitch"" (which succeeds) followed by lspci also produces a freeze on my machine. Without the call to bbswitch, the freeze does not happen, but my idle power usage is at 25-30W, instead of the ~11 that occurs if I do invoke bbswitch."
1803179,2020-02-09 19:16:21 UTC,"Yep the actual arch kernel is working fine here, including these patches:
Linux omega 5.5.2-arch1-1 #1 SMP PREEMPT Tue, 04 Feb 2020 18:56:18 +0000 x86_64 GNU/Linux"
1803179,2020-02-09 20:08:17 UTC,"(In reply to Matthias Fulz from comment #157)

> Yep the actual arch kernel is working fine here, including these patches:
> Linux omega 5.5.2-arch1-1 #1 SMP PREEMPT Tue, 04 Feb 2020 18:56:18 +0000
> x86_64 GNU/Linux
>
> Best Powerconsumption so far 6-7W normal working (wlan, 25% display,
> browsing, etc.)
>
> No lockups anymore, using bumblebee (primusrun, optirun) just need to
> manually unload the nvidia modules afterwards, which I've included in simple
> scripts.
>
> Thanks at all for this :)
"
1803179,2020-02-09 20:23:52 UTC,"Yep the problem is bbswitch. Just deinstall it, make sure the power mode for nvidia gpu and hdmi sound are set to auto and unload the nvidia & nvidia_modeset modules."
1803179,2020-02-09 22:31:14 UTC,"(In reply to Matthias Fulz from comment #159)

> Yep the problem is bbswitch. Just deinstall it, make sure the power mode for
> nvidia gpu and hdmi sound are set to auto and unload the nvidia &
> nvidia_modeset modules.
>
> bbswitch will still lead to the lockups, if used.
"
1803179,2020-02-09 22:43:38 UTC,I'm just using bumblebee and do not blacklist nvidia modules.
1803179,2020-02-09 22:45:52 UTC,Additional information:
1803179,2020-02-09 23:17:38 UTC,"(In reply to Matthias Fulz from comment #161)

> I'm just using bumblebee and do not blacklist nvidia modules.
>
> This is my /etc/bumblebee/xorg.conf.nvidia
>
> Section ""ServerLayout""
>     Identifier  ""Layout0""
>     Option      ""AutoAddDevices"" ""true""
>     Option      ""AutoAddGPU"" ""false""
> EndSection
>
> Section ""Device""
>     Identifier  ""DiscreteNvidia""
>     Driver      ""nvidia""
>     VendorName  ""NVIDIA Corporation""
>
>
>     Option ""NoLogo"" ""true""
>     Option ""UseEDID"" ""false""
>     Option ""AllowEmptyInitialConfiguration""
> EndSection
>
> Section ""Screen""
>     Identifier ""Screen0""
>     Device ""DiscreteNvidia""
> EndSection
>
> And I'm just using an additional systemd service for powertop
> /etc/systemd/system/powertop.service:
>
> [Unit]
> Description=PowerTOP auto tune
>
> [Service]
> Type=idle
> Environment=""TERM=dumb""
> ExecStart=/usr/bin/bash -c ""sleep 30 && /usr/bin/powertop --auto-tune &&
> sleep 10 && echo 'on' > '/sys/bus/usb/devices/1-1/power/control'""
>
> [Install]
> WantedBy=multi-user.target
>
> Then I've everything ready and can use:
> primusrun
> optirum
>
> for nvidia GPU stuff. For the unloading of the modules after the use I'm
> using the following scripts:
>
> /usr/local/bin/primusrun
>
> #!/bin/bash
>
> trap unload 1 2 3 6
>
> unload() {
>     /usr/bin/lsmod | grep nvidia > /dev/null 2>&1
>     if [ $? -eq 0 ]
>     then
>         echo ""unloading nvidia modules ...""
>         sleep 2
>         /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
>         if [ $? -eq 0 ]
>         then
>             sudo /usr/bin/rmmod nvidia_modeset
>         fi
>         sudo /usr/bin/rmmod nvidia
>         echo ""finished.""
>     fi
> }
>
> primusrun $@
> unload
>
> /usr/local/bin/optirun
>
> #!/bin/bash
>
> trap unload 1 2 3 6
>
> unload() {
>     /usr/bin/lsmod | grep nvidia > /dev/null 2>&1
>     if [ $? -eq 0 ]
>     then
>         echo ""unloading nvidia modules ...""
>         sleep 2
>         /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
>         if [ $? -eq 0 ]
>         then
>             sudo /usr/bin/rmmod nvidia_modeset
>         fi
>         sudo /usr/bin/rmmod nvidia
>         echo ""finished.""
>     fi
> }
>
> optirun $@
> unload
>
> That's it for me.
>
> In addition for powersavings I'm using TLP with quite default settings.
>
> Offloading inside the nvidia drivers is just not really helpful afaik :)
>
> Hope that helps.
"
1803179,2020-04-14 19:49:59 UTC,"(In reply to Matthias Fulz from comment #161)

> I'm just using bumblebee and do not blacklist nvidia modules.
>
> This is my /etc/bumblebee/xorg.conf.nvidia
>
> Section ""ServerLayout""
>     Identifier  ""Layout0""
>     Option      ""AutoAddDevices"" ""true""
>     Option      ""AutoAddGPU"" ""false""
> EndSection
>
> Section ""Device""
>     Identifier  ""DiscreteNvidia""
>     Driver      ""nvidia""
>     VendorName  ""NVIDIA Corporation""
>
>
>     Option ""NoLogo"" ""true""
>     Option ""UseEDID"" ""false""
>     Option ""AllowEmptyInitialConfiguration""
> EndSection
>
> Section ""Screen""
>     Identifier ""Screen0""
>     Device ""DiscreteNvidia""
> EndSection
>
> And I'm just using an additional systemd service for powertop
> /etc/systemd/system/powertop.service:
>
> [Unit]
> Description=PowerTOP auto tune
>
> [Service]
> Type=idle
> Environment=""TERM=dumb""
> ExecStart=/usr/bin/bash -c ""sleep 30 && /usr/bin/powertop --auto-tune &&
> sleep 10 && echo 'on' > '/sys/bus/usb/devices/1-1/power/control'""
>
> [Install]
> WantedBy=multi-user.target
>
> Then I've everything ready and can use:
> primusrun
> optirum
>
> for nvidia GPU stuff. For the unloading of the modules after the use I'm
> using the following scripts:
>
> /usr/local/bin/primusrun
>
> #!/bin/bash
>
> trap unload 1 2 3 6
>
> unload() {
>     /usr/bin/lsmod | grep nvidia > /dev/null 2>&1
>     if [ $? -eq 0 ]
>     then
>         echo ""unloading nvidia modules ...""
>         sleep 2
>         /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
>         if [ $? -eq 0 ]
>         then
>             sudo /usr/bin/rmmod nvidia_modeset
>         fi
>         sudo /usr/bin/rmmod nvidia
>         echo ""finished.""
>     fi
> }
>
> primusrun $@
> unload
>
> /usr/local/bin/optirun
>
> #!/bin/bash
>
> trap unload 1 2 3 6
>
> unload() {
>     /usr/bin/lsmod | grep nvidia > /dev/null 2>&1
>     if [ $? -eq 0 ]
>     then
>         echo ""unloading nvidia modules ...""
>         sleep 2
>         /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
>         if [ $? -eq 0 ]
>         then
>             sudo /usr/bin/rmmod nvidia_modeset
>         fi
>         sudo /usr/bin/rmmod nvidia
>         echo ""finished.""
>     fi
> }
>
> optirun $@
> unload
>
> That's it for me.
>
> In addition for powersavings I'm using TLP with quite default settings.
>
> Offloading inside the nvidia drivers is just not really helpful afaik :)
>
> Hope that helps.
"
1803179,2020-04-14 20:35:26 UTC,"(In reply to Ranjith Hegde from comment #164)

> (In reply to Matthias Fulz from comment #161)
>
> Hello,
> Thank you for your patch and effort. I tried your primusrun patch. First I
> get an infinite repetitions of this
> /bin/bash: warning: shell level (1000) too high, resetting to 1
>


Ok this is NOT a patch :)
It's just a simple script to run optirun / primusrun encapsulated to load and unload the nvidia module."
1803179,2020-04-14 22:01:13 UTC,"(In reply to Matthias Fulz from comment #165)

> (In reply to Ranjith Hegde from comment #164)
> > (In reply to Matthias Fulz from comment #161)
> >
> > Hello,
> > Thank you for your patch and effort. I tried your primusrun patch. First I
> > get an infinite repetitions of this
> > /bin/bash: warning: shell level (1000) too high, resetting to 1
> >
> Ok this is NOT a patch :)
> It's just a simple script to run optirun / primusrun encapsulated to load
> and unload the nvidia module.
>
> > and when I stop (C-c) I get an infinite loop of this
> >
> > rmmod: ERROR: Module nvidia is not currently loaded
> > finished.
> > unloading nvidia modules ...
> > rmmod: ERROR: Module nvidia is not currently loaded
> > finished.
> >
> > nothing launches..
> >  Any ideas?
> >
> Yes: I'm quite sure you've got /usr/local/bin in your PATH and this before
> the /usr/bin entry, where optirun / primusrun should be placed in.
>
> Two possible solutions:
>
> 1.) Change the lines primusrun $@ and optirun $@ to use the full path a.e.
> /usr/bin/primusrun $@ instead of primusrun $@
>
> 2.) Rename the scripts to something like /usr/local/bin/primusrun.sh and
> /usr/local/bin/optirun.sh
>
> Second solution will avoid any naming clushes for sure.
>
> Hope that helps
>
> BR,
> Matthias
"
1803179,2020-04-16 11:43:59 UTC,"btw, this bug should be fixed with the nouveau river in 5.7 (and backports should follow soon for 5.4, 5.5 and 5.6)"
1803179,2020-05-29 16:08:25 UTC,"(In reply to Karol Herbst from comment #167)

> btw, this bug should be fixed with the nouveau river in 5.7 (and backports
> should follow soon for 5.4, 5.5 and 5.6)
"
1803179,2020-05-29 16:48:41 UTC,"(In reply to xxxaaa from comment #168)

> (In reply to Karol Herbst from comment #167)
> > btw, this bug should be fixed with the nouveau river in 5.7 (and backports
> > should follow soon for 5.4, 5.5 and 5.6)
>
> I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727 but
> I use NVIDIA PRIME driver. Will your bugfix work for that too or does it
> work only for nouveau drivers?
"
1803179,2020-05-30 11:46:06 UTC,"Karol Herbst,"
1803179,2020-05-30 12:20:07 UTC,"(In reply to Kai-Heng Feng from comment #170)

> Karol Herbst,
>
> Is it fixed by removing the OSI vendor strings?
"
1803179,2020-07-12 09:52:05 UTC,New problems in an old thread
1803179,2020-08-16 11:23:25 UTC,"(In reply to xxxaaa from comment #173)

> (In reply to Karol Herbst from comment #169)
> > (In reply to xxxaaa from comment #168)
> > > (In reply to Karol Herbst from comment #167)
> > > > btw, this bug should be fixed with the nouveau river in 5.7 (and
> > backports
> > > > should follow soon for 5.4, 5.5 and 5.6)
> > >
> > > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727
> but
> > > I use NVIDIA PRIME driver. Will your bugfix work for that too or does it
> > > work only for nouveau drivers?
> >
> > the fix is for Nouveau only, but I am actually in contact with Nvidia about
> > the same issue they have inside their driver as well.
> >
> > But the bug can be fixed from within the open source files inside the
> nvidia
> > driver as well I just hope that Nvidia will have a proper solution here as
> > the fix in Nouveau is also more of a workaround than a real fix.
>
> (Sorry for being impatient but this bug has been bugging me a lot.)
> Do you know if this has been fixed on Nvidia Drivers yet or not? And if it
> has not been fixed then whether it is on their roadmap or not?
"
1803179,2020-08-16 11:54:03 UTC,"(In reply to Karol Herbst from comment #174)

> (In reply to xxxaaa from comment #173)
> > (In reply to Karol Herbst from comment #169)
> > > (In reply to xxxaaa from comment #168)
> > > > (In reply to Karol Herbst from comment #167)
> > > > > btw, this bug should be fixed with the nouveau river in 5.7 (and
> > > backports
> > > > > should follow soon for 5.4, 5.5 and 5.6)
> > > >
> > > > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727
> > but
> > > > I use NVIDIA PRIME driver. Will your bugfix work for that too or does
> it
> > > > work only for nouveau drivers?
> > >
> > > the fix is for Nouveau only, but I am actually in contact with Nvidia
> about
> > > the same issue they have inside their driver as well.
> > >
> > > But the bug can be fixed from within the open source files inside the
> > nvidia
> > > driver as well I just hope that Nvidia will have a proper solution here
> as
> > > the fix in Nouveau is also more of a workaround than a real fix.
> >
> > (Sorry for being impatient but this bug has been bugging me a lot.)
> > Do you know if this has been fixed on Nvidia Drivers yet or not? And if it
> > has not been fixed then whether it is on their roadmap or not?
>
> Afaik they do not and my attempts to get them to even reproduce the issue
> failed...
>
> so I don't see it getting fixed any time soon and honestly, if I have to put
> more time into it I might even stop caring as the fix we have for Nouveau is
> good enough and appears to have resolved the issue for good.
>
> In case you are still plagued by it I suspect you might want to bring that
> up to Nvidia directly and see if they get more motivated fixing it if they
> get more reports.
"
1803179,2020-09-14 07:31:25 UTC,"(In reply to Ranjith Hegde from comment #172)

> New problems in an old thread
>
> After using @Matthias Fulz's method (bumblebee without bbswitch + pm with
> powertop+tlp) its quite simple to run any software requiring nvidia. with
> his patch.
>
> The problem is in preventing any other software from using nvidia when not
> run with optirun/primusrun. For example, any software that calls for EGL
> automatically turns on nvidia. Mpv is one of those.
>
> Is there any way to ensure EGL calls intel instead? There is solution in
> arch wiki with env-variable
> ""__EGL_VENDOR_LIBRARY_FILENAMES=""/usr/share/glvnd/egl_vendor.d/50_mesa.json""
> ""
>
> but it does not work. I have tried adding it in all possible places
> (/etc/environment, /etc/profile, bash-profile, zsh-profile-equivalent etc..)
"
1803179,2019-11-10 01:06:21 UTC,"I have hp-spectre x360
i7-9750h, nvidia gtx 1650"
1803179,2020-08-16 11:09:40 UTC,"(In reply to Karol Herbst from comment #169)

> (In reply to xxxaaa from comment #168)
> > (In reply to Karol Herbst from comment #167)
> > > btw, this bug should be fixed with the nouveau river in 5.7 (and
> backports
> > > should follow soon for 5.4, 5.5 and 5.6)
> >
> > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727 but
> > I use NVIDIA PRIME driver. Will your bugfix work for that too or does it
> > work only for nouveau drivers?
>
> the fix is for Nouveau only, but I am actually in contact with Nvidia about
> the same issue they have inside their driver as well.
>
> But the bug can be fixed from within the open source files inside the nvidia
> driver as well I just hope that Nvidia will have a proper solution here as
> the fix in Nouveau is also more of a workaround than a real fix.
"
1803179,2019-10-25 19:43:10 UTC,"(In reply to Kai-Heng Feng from comment #145)

> Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM
> will disable the power of the card.
> After nvidia.ko gets unloaded, make sure ""power/control"" is ""auto"" for its
> video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and its upstream
> bridge (use lspci -t to check).
>
> In addition to that, these two commits are also required for mainline kernel
> users:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
> ?id=52525b7a3cf82adec5c6cf0ecbd23ff228badc94
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
> ?id=bacd861452d2be86a4df341b12e32db7dac8021e
"
1803179,2019-10-25 18:45:17 UTC,"(In reply to Matthias Fulz from comment #144)

> Ok here are more tests:
>
> Disabling the audio part with your suggestion ist working.
> No NVIDIA audio in powertop nor in lspci.
>
> Your solution is basically loading / unloading the nvidia modul now, which
> indeed is working, but not the optimus part I think?
"
1803179,2016-11-16 21:49:18 UTC,"(In reply to Peter Wu from comment #18)

> (In reply to Rafael J. Wysocki from comment #15)
> > That PCIe ports PM appears to be different from what we're going to do in
> > 4.8+, though, which may be the source of the problem.
>
> This is not the source of the problem, the issue exists before with older
> kernels.
>
> The list of affected models keeps growing, there have been reports from
> additional HP, Dell and Asus laptops. All of these have in common a Skylake
> CPU (i7-6700HQ) and some NVIDIA GPU (Maxwell cards, GTX 950M/960M/965M/970M,
> Quadro M1000M). Some of the laptops are listed at the updated list in
> https://github.com/Bumblebee-Project/Bumblebee/issues/764#issuecomment-
> 234494238
>
> Any idea what to look into? Patches, documentation or other possible hints?
"
1803179,2016-11-03 12:55:50 UTC,"(In reply to Rafael J. Wysocki from comment #15)

> That PCIe ports PM appears to be different from what we're going to do in
> 4.8+, though, which may be the source of the problem.
"
1803179,2016-11-03 13:10:19 UTC,"Created attachment 243561
attachment-10037-0.html"
1803179,2016-09-08 10:25:10 UTC,"Created attachment 232611
dmesg for v4.7-rc5 (triggered runtime-resume via writing ""on"" to (nvidia device)/power/control)"
1803179,2016-09-12 10:51:42 UTC,"let's focus on one platform first.
For people who encounters this problem and can give quick response, please attach the acpidump of the platform."
1803179,2016-09-12 10:54:29 UTC,"Okay, let's focus on Clevo_P651RA first."
1803179,2016-09-12 10:55:33 UTC,"I don't see how to download the acpidump file at https://github.com/Lekensteyn/acpi-stuff/blob/master/dsl/Clevo_P651RA/acpidump.txt
can you please attach it here?"
1803179,2016-09-12 12:07:08 UTC,"Created attachment 233091
acpidump for Clevo P651RA (BIOS 1.05.07)"
1803179,2016-09-19 23:49:11 UTC,Does this still fail if you use the proprietary nvidia driver?
1803179,2016-09-20 02:36:24 UTC,"Peter:
Should you first try this: attachment 239241"
1803179,2016-09-20 08:31:09 UTC,"(In reply to Len Brown from comment #5)

> Does this still fail if you use the proprietary nvidia driver?
"
1803179,2016-09-21 05:53:35 UTC,"Do you mean it's already long enough (95.7ms) for this case, and waiting longer won't solve the issue?
I don't know, I just want to get rid of the possible bug causes."
1803179,2016-09-21 05:56:59 UTC,"It looks like AML code in PGON prior than this loop should always make the condition true. What the platform need to do is to wait.
So IMO, the code prior than this loop is more important for root causing this issue."
1803179,2016-09-21 12:23:08 UTC,"(In reply to Lv Zheng from comment #8)

> Do you mean it's already long enough (95.7ms) for this case, and waiting
> longer won't solve the issue?
"
1803179,2016-09-22 02:43:58 UTC,Let me re-assign it to Power-management category and reset the assignee to involve more developers.
1803179,2016-09-27 00:09:41 UTC,"Peter, one question: Why is this not regarded as a nouveau problem?"
1803179,2016-09-27 09:28:34 UTC,"(In reply to Rafael J. Wysocki from comment #12)

> Peter, one question: Why is this not regarded as a nouveau problem?
"
1803179,2016-09-28 00:31:04 UTC,"On Tuesday, September 27, 2016 09:28:34 AM <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=156341
>
> --- Comment #13 from Peter Wu <email address hidden> ---
> (In reply to Rafael J. Wysocki from comment #12)
> > Peter, one question: Why is this not regarded as a nouveau problem?
>
> Something changed in Windows 10 that made firmware authors write this
> specific
> DSDT workaround. If Linux advertises itself as Windows 7 for example, the
> problematic code is not triggered. (Some laptops also work when advertising
> ""non-Windows 10"", such as Windows 8).
>
> It could be a missing piece in the nouveau driver, but exactly how to tackle
> that is not known. In a minimal module that uses the new PCI port runtime PM
> (""PR3 support"") introduced with v4.8, I could also trigger the lockups.
>
> Are you aware of changes to the policies in Windows 10 that could explain the
> different methods of putting a device into D3? Timing-wise or other APIs
> changes?
"
1803179,2016-09-29 21:20:00 UTC,One difference between Windows 10 and Windows 7 I know about is that Windows 10 supports power management of PCIe ports and I bet the ASL in comment #7 is needed to cope with that.
1803179,2016-09-29 21:59:04 UTC,"(In reply to Rafael J. Wysocki from comment #15)

> One difference between Windows 10 and Windows 7 I know about is that Windows
> 10 supports power management of PCIe ports and I bet the ASL in comment #7
> is needed to cope with that.
>
> That PCIe ports PM appears to be different from what we're going to do in
> 4.8+, though, which may be the source of the problem.
"
1803179,2016-10-24 10:30:13 UTC,Tested against 4.9-RC2 on Fedora 25 and the problem still exists
1803179,2016-11-16 21:52:49 UTC,And what if we simply avoided using ACPI PM with the affected device on those systems?
1803179,2016-11-16 23:42:41 UTC,"> You said that acpi_osi=""!Windows 2015"" helped in some cases.  I guess the
> other cases (where it doesn't help) are Windows 10 only systems?
"
1803179,2019-10-25 18:56:42 UTC,(In reply to Kai-Heng Feng from comment #145)
1803179,2017-01-28 23:37:14 UTC,I just wanted to report that this issue is present on Lenovo W541 with 4.9.4-1. You can see my full bug report here for the symptoms: https://bugzilla.opensuse.org/show_bug.cgi?id=1022443
1803179,2019-10-25 18:00:33 UTC,"Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM will disable the power of the card.
After nvidia.ko gets unloaded, make sure ""power/control"" is ""auto"" for its video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and its upstream bridge (use lspci -t to check)."
1803179,2019-10-25 16:42:56 UTC,Ok here are more tests:
1803179,2017-02-15 04:56:21 UTC,"I would like to add that acpi_osi=""!Windows 2015"" does not solve the problem, while  acpi_osi=! acpi_osi=""Windows 2009"" does (it does disable the touchpad though)."
1803179,2019-10-25 16:17:25 UTC,"(In reply to arpie from comment #142)

> (In reply to Matthias Fulz from comment #141)
> > (In reply to arpie from comment #140)
> [snip]
> > > If I completely disable the audio card using :
> > > echo 1 | sudo tee /sys/bus/pci/devices/0000:01:00.1/remove
> > >
> > > Then the system hangs are completely cured
> >
> > Not working for me. Still freezing with this.
>
> Any chance of more details?  When and how is it freezing?  Is it any
> different from before?  What are your machine/card details (looks like you
> haven't posted these anywhere above)?
>
"
1803179,2019-10-25 13:38:19 UTC,"(In reply to Matthias Fulz from comment #141)

> (In reply to arpie from comment #140)


[snip]

> > If I completely disable the audio card using :
> > echo 1 | sudo tee /sys/bus/pci/devices/0000:01:00.1/remove
> >
> > Then the system hangs are completely cured
>
> Not working for me. Still freezing with this.
"
1803179,2019-10-24 22:09:04 UTC,"(In reply to arpie from comment #140)

> After hours of experimenting on this laptop :
>
> Computer : PC Specialist OptimusIX 15 (aka Clevo N8xxEP6)
> BIOS : American Megatrends 1.07.13
> OS : Arch Linux
> GPU : NVIDIA GTX 1060 Mobile
>
> Until recently, any attempt to use bumblebee or acpi commands to power down
> the GPU have resulted in a system freeze with lspci, suspend, power cable
> plug in, etc.  No kernel line parameters seem to have any effect.
>
> I have discovered that the system freeze is closely linked to the
> interaction between the nvidia graphics card on pci address 0000:01:00.0 and
> its associated sound card at pci address 0000:01:00.1  (I don't actually
> know what that sound card is doing - I presume it's for the HDMI port?)
>
> If I completely disable the audio card using :
> echo 1 | sudo tee /sys/bus/pci/devices/0000:01:00.1/remove
>
> Then the system hangs are completely cured - I can acpi _OFF or _ON or _PS3
> or _PS0 to my hearts content and the gfx card will power up and down
> perfectly, lspci behaves perfectly normally (without any lag), and
> suspend/resume and power cable plug/unplug all works.  Even better, kernel
> power management on the PCI bus seems to work perfectly too, but only kicks
> in when I rmmod nvidia.  So far, bumblebee and bbswitch also seem to be
> totally happy.
>
> Can anybody else confirm similar findings?
>
> Bear in mind that the audio card needs to be removed BEFORE the kernel loads
> any audio modules.  I do it like this :
>
> [Unit]
> Description=Nvidia Audio Card OnBoot Disabler
> Before=bumblebeed.service
>
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> ExecStart=/usr/bin/sh -c ""echo 1 > /sys/bus/pci/devices/0000:01:00.1/remove""
> ExecStop=/usr/bin/sh -c ""echo 1 > /sys/bus/pci/rescan""
>
> [Install]
> WantedBy=sysinit.target
"
1803179,2019-10-23 22:09:55 UTC,After hours of experimenting on this laptop :
1803179,2019-09-28 21:53:48 UTC,"If someone is interested in a workaround for using either nvidia or the intel card, I've worked out the following setup:"
1803179,2019-10-25 18:36:49 UTC,"(In reply to Matthias Fulz from comment #143)

> (In reply to arpie from comment #142)
> > (In reply to Matthias Fulz from comment #141)
> > > (In reply to arpie from comment #140)
> > [snip]
>
> Ah I see.
> Then I think this is basically somehow similar to my workaround using the
> snd_hda_intel modul parameter.
> The nvidia card will just be completely ""powered off"" by not using it in any
> way (no module loaded)
"
1803179,2018-11-28 21:11:41 UTC,"A workaround is adding the following boot patameters:
`acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep`"
1803179,2018-11-27 19:34:30 UTC,"Some added info. This bug is present in:
driver   : nvidia-driver-415 - third-party free recommended
driver   : nvidia-driver-410 - third-party free
driver   : nvidia-driver-390 - distro non-free"
1803179,2018-11-23 14:07:42 UTC,Seems like this is caused by nvidia drivers not liking s2idle or forcing the use of 'deep' leads to reliable suspend/resume cycles. Properly removing nvidia drivers leads to a working system.
1803179,2018-11-15 21:27:27 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1803179,2018-11-13 20:00:08 UTC,This change was made by a bot.
1803179,2017-02-21 01:26:08 UTC,"Created attachment 254843
Patch for XPS 9560"
1803179,2017-01-22 17:32:16 UTC,"Hi everyone, I'm hoping to provide some helpful information here. I'm affected by this bug, in that I can't login to gnome unless I either blacklist the nouveau module or add ""nouveau.runpm=0"" to my kernel parameters. I've got some files here that I hope are of use to you:"
1803179,2017-02-19 07:29:19 UTC,Is there anything else I can do to help debug this issue?
1803179,2017-02-15 21:11:46 UTC,"Created attachment 254777
acpidump for ASUS N552VW-FI056T SkyLake i7-6700HQ/GTX 960M BIOS 3.0.0"
1803179,2018-11-28 09:30:38 UTC,"Opened a forum thread on the Nvidia dev forum regarding this issue""
https://devtalk.nvidia.com/default/topic/1044633/linux/driver-does-not-wake-gpu-properly-after-suspend-ubuntu-18-10-with-branch-390-410-and-415-/"
1803179,2017-02-15 07:53:25 UTC,"Created attachment 254763
acpidump for Dell XPS15 9560 KabyLake i7-7700HQ/GTX1050M BIOS 1.0.3"
1803179,2017-02-15 06:30:53 UTC,"@Andrzej, please attach the acpidump output of your laptop."
1803179,2017-02-12 15:58:21 UTC,This issue is present on ASUS n552vw-fi056t (Core i7-6700HQ and NVIDIA GeForce GTX 960M) with kernel 4.9.9.
1803179,2017-02-15 04:54:57 UTC,"The issue is also present on KabyLake Dell XPS15 9560 with i7-7700HQ with NVidia GTX1050M. It manifests itself with complete freezes if the intel card is used for X and the NVidia card is disabled with bumblebee. Then, running nvidia-smi, lspci casuses freeze. The freezes do not happen if NVidia card is enabled using bbswitch."
1803188,2019-05-28 07:39:36 UTC,"When using MAAS 2.5.3, and composing a machine on a pod, it creates an alias for the first interface."
1803188,2018-12-11 15:14:40 UTC,The failure in comment #6 happened around 2018-12-11-11:38:26
1803188,2018-12-11 15:14:05 UTC,We are seeing this on 2.4.3 also:
1803188,2018-11-15 14:35:45 UTC,"Sure, that said, the fact that a single with 2 addresses results on a alias after commissioning is still an issue (regardless of what other issues may be happening in the commissioning environment)."
1803188,2018-11-14 00:04:35 UTC,"Yes, we should take a look at the handoff between the IP address the machine gets in the pre-boot environment and the next DHCP client that will be taking over the lease. I would be willing to bet that's part of the issue."
1803188,2018-11-13 22:55:51 UTC,"I've not explored why it would have gotten 2 different IP addresses, but it could also be the fact that during commissioning, we try to bring up other interfaces to see if we can discover networks. I wonder if this has regressed and it is trying to dhcp scan the interface used for PXE, which would cause it from potentially obtaining a new IP?"
1803188,2018-11-13 21:33:01 UTC,"Just thinking out loud here, but I'm wondering if this could be related to bug #1749019. I know we've had issues with DHCP IP addresses from the PXE environment not playing well with subsequently-acquired addresses from ISC DHCP, but that's the most recent thing that has changed in this area..."
1803189,2019-05-10 10:07:49 UTC,"Launchpad does not expire a bug if the bug is associated with multiple projects, so (as horizon upstream) I am removing 'horizon' from the affected projects. If this can be reproduced, please re-add 'horizon'."
1803189,2018-11-24 02:40:14 UTC,"This report is about ubuntu package, so I added it to the affected project."
1803189,2019-05-04 19:40:03 UTC,"Hello Dilip,"
1803189,2019-05-04 19:40:26 UTC,"Marking as incomplete now, but if this is still an issue please feel free to move back to New."
1803189,2019-07-10 04:17:25 UTC,[Expired for horizon (Ubuntu) because there has been no activity for 60 days.]
1803192,2019-07-22 03:45:31 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1803192,2018-12-04 18:28:58 UTC,"Hi alain.roger,
Your issue doesn't look like a security issue.
I saw you reported it upstream as asked by Daniel.
So can we make this issue Public and mark it as not Security?
I am asking because I am not sure why you marked it as Private Security.
Thanks"
1803192,2018-11-21 02:11:32 UTC,I can't see anything obviously broken so suggest reporting the bug to the PulseAudio developers here:
1803192,2018-11-20 18:08:40 UTC,Any news regarding this issue ?
1803192,2018-11-14 18:27:53 UTC,apport information
1803192,2018-11-14 18:27:52 UTC,apport information
1803192,2018-11-14 18:27:43 UTC,apport information
1803192,2018-11-14 18:27:49 UTC,apport information
1803192,2018-11-14 18:27:48 UTC,apport information
1803192,2019-03-07 18:34:15 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1803192,2018-11-14 01:46:48 UTC,Please run this command to send us more information about the system:
1803192,2018-11-14 18:27:50 UTC,apport information
1803192,2019-03-08 01:47:00 UTC,I can't seem to find the upstream bug. Can you share the link?
1803192,2018-11-14 18:28:42 UTC,Here they are
1803195,2019-09-19 12:06:59 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1803201,2019-09-19 14:48:03 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1803202,2018-12-05 14:13:58 UTC,"Did you mean ""./run_PY8.sh"" ?"
1803202,2018-11-23 18:18:03 UTC,"Hello,"
1803202,2018-12-04 02:25:02 UTC,"Hello,"
1803202,2018-12-04 02:41:00 UTC,"I would advise to contact directly Stephan Prestel and  Valentin Hirschi about this.
I can not do more than that."
1803202,2018-12-04 06:15:03 UTC,"The issue comes from the parallelisation of the Pythia8 shower, which unfortunately has to be managed by MadGraph since Pythia8 doesn't offer this functionality."
1803202,2018-12-04 13:59:53 UTC,"Just for information, I do not reproduce this behavior on Ubuntu 16.04.5 LTS (run on azure)
and on debian (run via singularity: https://www.singularity-hub.org/containers/5631)
and obviously on my mac."
1803202,2018-12-04 22:18:30 UTC,"Hello Valentin,"
1803202,2018-12-05 07:32:37 UTC,"Yes, this would be the log file, however it does not seem to indicate any
error.
Could you try to run it manually using script inside that ""split_0""
directory, with the command:"
1803202,2018-12-05 16:47:11 UTC,"Looking back into your original report I see that the following triggered a
crash:"
1803203,2020-08-04 08:00:58 UTC,"Thanks to Heitor's work, the pull request to support preferred_lft has been merged upstream: https://github.com/CanonicalLtd/netplan/pull/89"
1803203,2018-11-15 18:01:05 UTC,"Hi Andy,"
1803203,2018-11-15 18:47:21 UTC,"Andy, in the interest of full disclosure, I'm the other user that reported this through the paid support channel."
1803203,2018-11-16 08:25:08 UTC,"Hi Daniel,"
1803203,2018-11-17 23:39:40 UTC,"As a workaround, here is a networkd-dispatcher hook script which when called will set preferred_lft 0 for all IPv6 addresses on the system, apart from any exceptions you list."
1803203,2019-05-09 13:58:35 UTC,systemd back to bionic already supports the PreferredLifetime config param.  Only netplan needs a change to provide a param to set PreferredLifetime.
1803203,2019-05-27 19:00:02 UTC,Some notes for reference:
1803203,2019-05-29 09:45:47 UTC,"Currently, addresses is a ""sequence of scalars"" (aka a list). Here is the example from the Netplan reference you quoted:"
1803203,2019-06-07 20:03:25 UTC,"@rlaager
I've started a PR discussion on Netplan.io's Github with your proposed changes as they seemed the best way forward for now."
1803203,2020-09-22 11:41:00 UTC,This bug was fixed in the package netplan.io - 0.100-0ubuntu4
1803204,2020-01-18 20:52:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803207,2018-11-14 10:04:23 UTC,"The other solution would be to add eo.UTF-8 (& eo.ISO8859-3) to locale.dir & compose.dir.  This is probably the most correct way, because Esperanto is one of those languages which doesn't belong to any country, nor has national variants."
1803209,2018-11-15 13:19:53 UTC,I see this on windows as well but it's not very perceptible so maybe it's worse on linux.
1803209,2018-11-15 15:45:20 UTC,@Seth - I can't see a difference in this behaviour. The mouse pointer still moves a fraction before the crosshair and moved item do.
1803209,2019-07-08 20:10:46 UTC,"@Devs, does this still reproduce?  It appears instant on OSX, but maybe it was never a bug there."
1803209,2019-07-17 13:01:13 UTC,I'm not see much of a lag on windows but I'm using a fairly simple board.  Is this something that could be dependent on board complexity?
1803209,2018-11-15 15:13:53 UTC,@John-  I think this is related to lp:1801135  Can you see if the issue is better when exporting GTK_OVERLAY_SCROLLING=0 before running KiCad?
1803209,2019-09-16 04:17:30 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1803210,2019-10-07 11:27:14 UTC,This will happen naturally as a consequence of the agent work I'm doing now.
1803210,2019-03-25 14:23:47 UTC,This is related to apparmor cleanup. Once we implement cgroup vacancy notification we can address this. For now it is just acknowledged.
1803210,2019-02-19 15:08:07 UTC,I think that all that needs to happen is after all processes from the device cgroup have died/been killed is just to remove the /sys/fs/cgroup/devices/$SNAP_NAME.$SNAP_APP/ directory to remove the cgroup.
1803212,2018-11-14 13:41:21 UTC,This is documented like that:
1803212,2018-11-28 13:54:05 UTC,"I guess one case that hadn't been made clear in comment #3 but I can see from the forum post is that with the new behavior, an ""enabled and not running"" service would not get started with `snap restart SNAP`. I think that's wrong, because for example what about oneshot daemons and failed services? I think that both of those should still be started when issuing `snap restart`."
1803212,2018-11-28 13:19:45 UTC,I posted the proposed behavior change also to the forum:
1803212,2018-11-19 14:59:44 UTC,"What you described seems okay to us, as really the thing we want to not ever happen is to have a service manually disabled by a user start up again ""inadvertently"". The use case that's most important to us is:"
1803212,2018-11-16 10:00:09 UTC,We discussed this further also with the devs that did the original design/implementation of this.
1803212,2018-11-14 13:54:22 UTC,I think there are the following cases with my opinion on what should happen for every situation:
1803222,2019-12-29 12:53:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803230,2018-11-22 06:38:43 UTC,xxhash SRU info
1803230,2018-11-20 20:40:05 UTC,teckit
1803230,2018-11-20 22:05:33 UTC,"""- upstream has a testsuit which is not being used during build, we are going to look at changing that"" is a copy error, there is 1 test and it's used during the build"
1803230,2018-11-21 09:52:46 UTC,"Override component to main
teckit 2.5.8+ds2-5ubuntu1 in disco: universe/misc -> main
libteckit-dev 2.5.8+ds2-5ubuntu1 in disco amd64: universe/libdevel/optional/100% -> main
libteckit-dev 2.5.8+ds2-5ubuntu1 in disco arm64: universe/libdevel/optional/100% -> main
libteckit-dev 2.5.8+ds2-5ubuntu1 in disco armhf: universe/libdevel/optional/100% -> main
libteckit-dev 2.5.8+ds2-5ubuntu1 in disco i386: universe/libdevel/optional/100% -> main
libteckit-dev 2.5.8+ds2-5ubuntu1 in disco ppc64el: universe/libdevel/optional/100% -> main
libteckit-dev 2.5.8+ds2-5ubuntu1 in disco s390x: universe/libdevel/optional/100% -> main
libteckit0 2.5.8+ds2-5ubuntu1 in disco amd64: universe/libs/optional/100% -> main
libteckit0 2.5.8+ds2-5ubuntu1 in disco arm64: universe/libs/optional/100% -> main
libteckit0 2.5.8+ds2-5ubuntu1 in disco armhf: universe/libs/optional/100% -> main
libteckit0 2.5.8+ds2-5ubuntu1 in disco i386: universe/libs/optional/100% -> main
libteckit0 2.5.8+ds2-5ubuntu1 in disco ppc64el: universe/libs/optional/100% -> main
libteckit0 2.5.8+ds2-5ubuntu1 in disco s390x: universe/libs/optional/100% -> main
teckit 2.5.8+ds2-5ubuntu1 in disco amd64: universe/text/optional/100% -> main
teckit 2.5.8+ds2-5ubuntu1 in disco arm64: universe/text/optional/100% -> main
teckit 2.5.8+ds2-5ubuntu1 in disco armhf: universe/text/optional/100% -> main
teckit 2.5.8+ds2-5ubuntu1 in disco i386: universe/text/optional/100% -> main
teckit 2.5.8+ds2-5ubuntu1 in disco ppc64el: universe/text/optional/100% -> main
teckit 2.5.8+ds2-5ubuntu1 in disco s390x: universe/text/optional/100% -> main
19 publications overridden."
1803230,2018-11-22 01:45:35 UTC,Confirmed that xxhash is a code split rather than new code in main.
1803230,2018-11-21 11:47:56 UTC,"I think xxhash used to be bundled in texlive-bin too, but I don't have the time to investigate that now or work on this MIR."
1803230,2018-11-22 01:47:01 UTC,"Override component to main
xxhash 0.6.5-2 in disco: universe/misc -> main
libxxhash-dev 0.6.5-2 in disco amd64: universe/libdevel/optional/100% -> main
libxxhash-dev 0.6.5-2 in disco arm64: universe/libdevel/optional/100% -> main
libxxhash-dev 0.6.5-2 in disco armhf: universe/libdevel/optional/100% -> main
libxxhash-dev 0.6.5-2 in disco i386: universe/libdevel/optional/100% -> main
libxxhash-dev 0.6.5-2 in disco ppc64el: universe/libdevel/optional/100% -> main
libxxhash-dev 0.6.5-2 in disco s390x: universe/libdevel/optional/100% -> main
libxxhash0 0.6.5-2 in disco amd64: universe/libs/optional/100% -> main
libxxhash0 0.6.5-2 in disco arm64: universe/libs/optional/100% -> main
libxxhash0 0.6.5-2 in disco armhf: universe/libs/optional/100% -> main
libxxhash0 0.6.5-2 in disco i386: universe/libs/optional/100% -> main
libxxhash0 0.6.5-2 in disco ppc64el: universe/libs/optional/100% -> main
libxxhash0 0.6.5-2 in disco s390x: universe/libs/optional/100% -> main
xxhash 0.6.5-2 in disco amd64: universe/utils/optional/100% -> main
xxhash 0.6.5-2 in disco arm64: universe/utils/optional/100% -> main
xxhash 0.6.5-2 in disco armhf: universe/utils/optional/100% -> main
xxhash 0.6.5-2 in disco i386: universe/utils/optional/100% -> main
xxhash 0.6.5-2 in disco ppc64el: universe/utils/optional/100% -> main
xxhash 0.6.5-2 in disco s390x: universe/utils/optional/100% -> main
Override [y|N]? y
19 publications overridden."
1803230,2018-11-22 13:38:17 UTC,"this looks ok, besides the missing test run. The debian/rules file says:"
1803230,2020-06-30 14:39:55 UTC,xxhash promoted to main now
1803230,2020-06-25 05:14:02 UTC,"xxhash was a code split from a package already in main and already promoted in Disco/Eoan.
It came back now as dependency for rsync and (thanks Steve) Foundations is subscribed to cover it."
1803230,2018-12-06 09:51:00 UTC,"ack for me, seb told me he would take care of the tests."
1803230,2020-06-24 06:00:57 UTC,"FYI: As mentioned int he MIR Team meeting, since doko had to run I've sent a mail to vorlon asking if foundations is going to adopt it."
1803230,2020-06-23 15:04:47 UTC,"@it has been moved back to universe in focal, eoan isn't supported anymore and it's not a component desktop is using or interested in, I'm unsubscribing desktop-packages now. If it's promoted back one of the teams looking after rsync should subscribe"
1803230,2020-06-25 00:50:52 UTC,Foundations is now subscribed to xxhash.
1803233,2018-11-14 01:23:26 UTC,"FYI, I do have a patch ready and will submit shortly."
1803233,2018-11-29 21:28:04 UTC,Does https://review.openstack.org/#/c/613313/ help with this?
1803233,2018-11-29 22:18:38 UTC,"I'm aware of the above patch, it was from my co-worker :-)"
1803233,2020-01-30 15:30:06 UTC,"This sounds great! I am currently trying to debug some policies that somebody wrote in the dim past, and better checking would be great. Even with the latest oslo.policy it seems that the above features are not all present. Is there any progress in getting them merged?"
1803235,2018-11-14 08:13:33 UTC,"Hi Paul,"
1803235,2018-11-14 08:10:00 UTC,"Hi Seth,"
1803235,2018-11-14 02:13:27 UTC,Have you checked the gmail spam folder? Recently a very similar email I received went right into the spam folder.
1803235,2018-11-14 02:48:57 UTC,"It looks like Gmail is declining to accept messages from the forum, even after I switched discourse to using our mail relay instead of direct delivery."
1803236,2018-11-14 09:37:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1803236,2018-11-15 00:01:07 UTC,"Here it is:
https://bugzilla.gnome.org/show_bug.cgi?id=797383"
1803236,2019-07-19 13:19:48 UTC,Please follow the instructions of Thomas Haller in your upstream bug report.
1803247,2018-12-04 19:10:42 UTC,"As a workaround, clients can call juju show-controller to figure this manually by inspecting the ""models"" section."
1803247,2018-12-13 00:52:42 UTC,https://github.com/juju/juju/pull/9549
1803247,2018-12-04 19:57:11 UTC,Sorry I wasn't clear in the initial report but we need this exposed via the API for the GUI.
1803247,2018-12-18 12:17:12 UTC,If the fix is committed we don't remove the milestone. It goes into the list of  bugs addressed in that milestone. Was this landed against 2.5? If so it goes on the 2.5.0 milestone.
1803247,2018-12-19 00:51:57 UTC,Thanks for the prod in the right direction Rick. Should be all cleared up now.
1803267,2018-11-14 12:57:57 UTC,Please add version info
1803267,2018-11-14 13:18:04 UTC,"Application: eeschema
Version: (6.0.0-rc1-dev-1185-g3fd296831), release build
Libraries:
    wxWidgets 3.0.4
Platform: Linux 4.15.0-38-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    Compiler: GCC 7.3.0 with C++ ABI 1011"
1803269,2019-11-05 10:44:33 UTC,"Also, it would be great if the standard pinch/pan gestures worked on macOS, just like they already do in eeschema and pcbnew."
1803270,2018-11-14 17:19:51 UTC,Did you try gedit/chromium as snaps as well? or their deb version?
1803270,2019-01-02 07:40:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803270,2018-11-14 09:44:08 UTC,"Thanks for the report.
Can you try other snaps like gedit or chromium, and let us know whether the problem exists there too?"
1803270,2018-11-15 04:13:02 UTC,"@Sebastien: Yes, I think (Because I installed gedit/chromium from Ubuntu Market (Ubuntu Software)."
1803270,2018-11-14 10:21:47 UTC,I tried typing Vietnamese in gedit and chromium and It's ok.
1803270,2018-11-14 17:07:40 UTC,"Skype is a classic snap, so it doesn't use the desktop helpers, which enable ibus support."
1803275,2018-11-14 07:10:08 UTC,Same for me here using disco...
1803275,2018-11-14 14:10:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803275,2018-11-17 06:52:47 UTC,"Update:
With today's update - kernel 4.18.0-11-generic and new nvidia files - the 390 version driver does install however does not load.
see the attached /var/log/Xorg.0.log, and /var/log/gpu-manager.log .
What is promising is 'lshw' shows the nvidia driver as loaded/
sysop@x1904:~$ sudo lshw -C display
  *-display
       description: VGA compatible controller
       product: GK208B [GeForce GT 710]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:06:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:16 memory:fb000000-fbffffff memory:d8000000-dfffffff memory:e6000000-e7ffffff ioport:4c00(size=128) memory:c0000-dffff
sysop@x1904:~$"
1803275,2018-11-14 05:33:05 UTC,"sudo apt purge nvidia-dkms-390 successful in also removing nvidia-driver-390*.
However, sudo apt install nvidia-driver-390 results in same error condition of
""Errors were encountered while processing:
 nvidia-dkms-390
 nvidia-driver-390
E: Sub-process /usr/bin/dpkg returned an error code (1)
"""
1803275,2018-11-23 05:48:03 UTC,"Try and push this along.
Is this a packaging error ? As the Xorg file indicates:
4.976] (==) ModulePath set to ""/usr/lib/xorg/modules"""
1803292,2018-12-04 00:56:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803292,2018-11-16 18:48:34 UTC,Could you add the file /var/log/dist-upgrade/apt-term.log to this bug report? Thanks in advance!
1803294,2019-04-16 13:02:41 UTC,Thank you for your bug report. Could you get a debug log as described on https://wiki.gnome.org/Projects/NetworkManager/Debugging#Debugging_NetworkManager-openvpn  ? (you need to reboot or 'sudo systemctl restart NetworkManager' before starting the client in debug)
1803294,2019-06-16 04:17:27 UTC,[Expired for network-manager-openvpn (Ubuntu) because there has been no activity for 60 days.]
1803294,2018-11-14 08:20:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1803298,2019-06-05 04:17:23 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1803298,2019-04-05 16:47:32 UTC,"@Gabriel, do you still have these issues with 5.1? I am confused by your use of the term ""keep out"" when referring to footprints, as we don't currently allow keep out zones in footprints, see lp:1081846 [1]."
1803298,2018-11-15 04:45:29 UTC,Note that this bug may be related to this one as well (same project & file): https://bugs.launchpad.net/kicad/+bug/1803485
1803298,2018-11-15 03:03:39 UTC,"I think you mean ""Allow DRC violations"". See attached image. These are my settings for Route --> Interactive Router Settings..."
1803298,2018-11-14 08:49:48 UTC,Did you try to disable DRC before doing so?
1803309,2020-01-28 00:22:26 UTC,"The attachment ""makefile.patch (updated from debian 865758)"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1803309,2020-01-27 16:00:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803309,2020-01-27 21:32:50 UTC,"Actually, there are two bugs here:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823315
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857796"
1803309,2020-02-05 19:13:57 UTC,"In Debian it was fixed in <1 mouth after the initial 18.04 LTS release.
Would be great to have it integrated into 18.04 before the end of its long-term support period."
1803309,2020-01-27 21:42:22 UTC,"Here, a combined patch against the debian/ dir."
1803313,2018-11-16 15:07:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803321,2018-11-14 10:42:27 UTC,"StacktraceTop:
 clutter_input_device_xi2_update_pad_state (device=device@entry=0x55dbc2f5c1a0, button=<optimized out>, state=1, group=group@entry=0x55dbcaa2f324, mode=mode@entry=0x55dbcaa2f330) at x11/clutter-input-device-xi2.c:337
 clutter_device_manager_xi2_translate_event (translator=<optimized out>, native=<optimized out>, event=0x55dbcaa2f300) at x11/clutter-device-manager-xi2.c:1402
 clutter_backend_real_translate_event (backend=<optimized out>, native=0x7ffe92149020, event=0x55dbcaa2f300) at clutter-backend.c:597
 clutter_x11_handle_event (xevent=xevent@entry=0x7ffe92149020) at x11/clutter-event-x11.c:200
 handle_host_xevent (event=0x7ffe92149020, backend=0x55dbc2f1a110) at backends/x11/meta-backend-x11.c:383"
1803321,2020-11-16 08:39:29 UTC,I can't find any other reports of this crash. Does it still happen in 20.04?
1803321,2020-11-26 11:02:52 UTC,I don't have the tablet anymore and I'm still on 18.04.
1803321,2021-01-26 04:17:18 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1803321,2021-01-26 04:17:20 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1803324,2018-11-20 16:01:02 UTC,"Il s'agit de la ligne dans conf/local.php
$conf['start']       = 'Accueil';"
1803326,2018-12-05 05:10:15 UTC,"For this issue on azure-edge, I think it's related to bug 1803334"
1803326,2018-12-04 15:27:58 UTC,"Same issue found with bionic/linux-aws-edge on ADT tests:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-aws-edge/20181203_114936_4bb63@/log.gz"
1803326,2018-12-05 02:51:21 UTC,"Hi Kleber,
the zram test should be blacklisted, the reason why it's not working has been logged in bug 1806799."
1803326,2019-09-16 12:33:06 UTC,Test passed with all azure kernels.
1803330,2019-09-16 12:34:25 UTC,Module build OK with newer kernel.
1803331,2018-11-14 13:25:46 UTC,"ubuntu@b0ca2dda2a32:~$ openstack server set --state active a1b29f17-e910-4216-9165-e148e62d1ba1
ubuntu@b0ca2dda2a32:~$ openstack server resize --revert a1b29f17-e910-4216-9165-e148e62d1ba1
Cannot 'revertResize' instance a1b29f17-e910-4216-9165-e148e62d1ba1 while it is in vm_state active (HTTP 409) (Request-ID: req-fd828140-405b-4747-b6c5-7f846a46e2dc)"
1803331,2018-11-14 11:39:16 UTC,"based on irc conversation this is a more general bug then the title suggest.
this likly will effect resize and cold migrate between any to hosts where the image backend changes
e.g. any combination of lvm,rbd,image where the value differes on each host.
this may or may not also affect live migration."
1803331,2018-11-14 11:41:14 UTC,"not this usecase is currently not supported so we should either prevent this in the schduler/condoctor
or in the virtdirver so that we do not attempt the migration in this case."
1803331,2018-11-14 11:41:59 UTC,set as high due to possibility of data loss.
1803331,2018-11-14 11:49:05 UTC,"As discussed on IRC, I don't believe any data has been lost here, but it would be good if the reporter could confirm."
1803331,2018-11-14 13:18:49 UTC,"On the source node, yes I found the disk is still present in the _resize directory."
1803331,2018-11-14 14:00:39 UTC,"ubuntu@b0ca2dda2a32:~$ openstack server set --state resize_confirm a44021f5-a462-4b0c-9ed5-f49149e0059d
usage: openstack server set [-h] [--name <new-name>] [--root-password]
                            [--property <key=value>] [--state <state>]
                            <server>
openstack server set: error: argument --state: invalid choice: u'resize_confirm' (choose from 'active', 'error')"
1803334,2018-11-14 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803334,2018-11-30 12:36:16 UTC,"The quota smoke test on Azure 4.18 Bionic is now failing with other issue, marking this as Fix-released."
1803334,2018-12-04 09:48:36 UTC,"This bug was closed mistakenly (base on the header issue, bug 1803335)"
1803334,2018-12-04 11:21:48 UTC,"I can see this in the Bionic proposed package list, and it's pointing to the 4.18 package, will need some more check:"
1803335,2018-12-10 08:38:11 UTC,This bug was fixed in the package linux-azure-edge - 4.18.0-1006.6~16.04.2
1803335,2018-11-14 11:43:00 UTC,"This might be the cause of:
bug 1803333
bug 1803328
and
bug 1803330"
1803335,2018-11-14 12:00:21 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803335,2018-11-26 20:17:20 UTC,It does not look different in 4.18.0-1005
1803335,2018-11-30 11:50:22 UTC,"Hello Joshua,"
1803335,2019-02-14 12:11:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1803335,2019-03-04 11:45:01 UTC,"Works well with 4.18.0-1006.6~16.04.2
Kernel security test can be built (bug 1803333)."
1803336,2018-11-14 22:07:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803336,2020-05-21 12:06:01 UTC,"This affects me, I have a HP Pro 408 G1 tablet that can run 64 bit systems but has a 32 bit UEFI bootloader. This means I need to be able to install a 32 bit Grub to boot into a 64 bit Ubuntu system."
1803341,2019-05-25 10:24:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661441"
1803341,2019-06-14 17:37:15 UTC,"Reviewed:  https://review.opendev.org/661441
Committed: https://git.openstack.org/cgit/openstack/training-labs/commit/?id=af042e0716413f372160c7718fb99e8bf28cc864
Submitter: Zuul
Branch:    master"
1803343,2019-04-27 09:23:36 UTC,See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928063
1803343,2018-11-14 23:55:03 UTC,*** This is an automated message ***
1803343,2018-11-14 12:53:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803354,2019-02-21 15:35:22 UTC,I'm not sure about this. We should add a way to drop to a shell though.
1803357,2019-11-22 17:26:25 UTC,would be nice to have this solved before 20.04 LTS
1803357,2019-11-22 17:07:58 UTC,"Note, with MySQL
I often get this migration error"
1803357,2019-11-22 17:06:19 UTC,"please note, akonadi is not officially supported as a backend"
1803357,2019-11-22 16:42:43 UTC,still valid as of 19.10
1803357,2019-11-22 16:42:15 UTC,"Yes please !
we need this
please remove the hard dependency on mysql backend"
1803357,2019-11-22 16:40:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803364,2018-12-23 10:11:48 UTC,Upstream report closed. Fix should appear in version 3.32.
1803364,2018-11-14 20:58:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1803364,2018-11-14 21:11:50 UTC,Opened bug at https://gitlab.gnome.org/GNOME/gnome-calculator/issues/84
1803364,2019-07-01 13:36:46 UTC,3.32 is in Ubuntu now
1803382,2018-12-20 12:27:59 UTC,Here's how to patch ansible in an easy way:
1803382,2018-11-20 16:32:27 UTC,Suggested workaround by Francois:
1803382,2018-11-28 10:37:13 UTC,"In https://github.com/openstack/openstack-ansible/blob/1ab4e908f2cfd537171deff5dc3e237c3cf37dd7/inventory/host_vars/localhost/unbound.yml#L17, the unbound_physical_hosts is defined this way:"
1803382,2018-11-28 16:37:41 UTC,"Oops, please disregard the previous comment."
1803382,2018-11-28 16:51:27 UTC,"Downgrading to ansible 2.4.6 also fixed this issue while keeping the cache activated, it looks like an upstream ansible bug."
1803382,2018-11-30 10:42:53 UTC,Upgrading to ansible version 2.6.0 also fixes this issue.
1803382,2018-12-18 17:50:45 UTC,Here's the upstream ansible bug: https://github.com/ansible/ansible/issues/33259.
1803385,2019-05-16 21:25:18 UTC,"this was fixed a different way, in d-i and ca-certificates."
1803385,2019-05-16 21:24:31 UTC,"Closing this bug as Invalid.
The real solution is fix-released in LP#1807023."
1803385,2018-11-14 17:05:45 UTC,"Eric,"
1803385,2018-11-14 16:21:02 UTC,"The attachment ""disco_di-utils_httpsredir.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1803385,2018-11-14 16:03:27 UTC,Sponsor note:
1803385,2018-11-14 15:55:56 UTC,"Oops, I'll add the Debina/Ubuntu-Bug: DEP-3 tags in the debdiffs."
1803385,2018-11-14 15:17:29 UTC,"Testing performed with Disco, Cosmic, Bionic, Xenial, and Trusty."
1803385,2018-11-14 16:15:49 UTC,"Er, I mean, the right LP bug numbers in changelog,
and fix the version suffixes for Bionic and Cosmic,
as reported by slashd in IRC (thanks!)"
1803392,2018-11-16 21:48:00 UTC,"There are only 50 commits between Ubuntu-4.15.0-38 and Ubuntu-4.15.0-39, so it should be easy to track down.  I'll review the commit log.  If nothing sticks out we can perform a kernel bisect to identify the offending commit."
1803392,2018-11-14 16:00:07 UTC,This change was made by a bot.
1803392,2018-11-16 21:58:38 UTC,"Nothing sticks out in that range of commits.  There is nothing atheros related.  Before starting a bisect, can you confirm -proposed does not already fix the bug?"
1803392,2018-11-16 22:51:22 UTC,I also started a kernel bisect between Ubuntu-4.15.0-38 and Ubuntu-4.15.0-39. The kernel bisect will require testing of about 7-10 test kernels.
1803393,2018-12-03 22:55:20 UTC,We're trying to use server team's vsphere now.
1803398,2020-06-19 13:22:26 UTC,"Does not seem to be Windows specific.
Closing because I can't reproduce this on Inkscape 1.0 (4035a4fb49, 2020-05-01) on Manjaro Linux.
If anybody can reproduce this with 1.0 open a new issue in gitlab."
1803398,2018-11-15 02:22:52 UTC,"No, it also affect on normal installation. That's why I tried the Snap version, but the problem still exists."
1803398,2018-11-15 04:09:19 UTC,"first example reproduced on Windows 10, Inkscape 0.92.3 (0612fd7, 2018-10-23)
(does not always happen, had to try a few times)"
1803398,2018-11-15 04:16:41 UTC,"also reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1803398,2018-11-15 11:57:53 UTC,Tried Inkscape Portable under wine and got the same error. Backtrace file attached.
1803398,2018-11-16 23:54:17 UTC,"Not reproduced with Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1-64"
1803398,2019-05-03 01:54:08 UTC,Possibly related: bug 1809676
1803398,2019-10-09 21:07:41 UTC,"Can confirm this bug still exists and is reproducible, using the aforementioned steps, on Solus OS:"
1803398,2018-11-14 17:38:09 UTC,"not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1803399,2020-02-04 14:28:36 UTC,Fixed in launchpadlib 1.10.8:
1803405,2018-12-27 11:29:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803405,2018-12-27 11:36:23 UTC,"sudo apt-get install --reinstall libgtk2.0-0
solve the problem for me"
1803405,2019-08-20 01:46:40 UTC,"Thank you for reporting this bug. Since this was reported against a version of gimp included in a now end-of-life version of Ubuntu, please try to reproduce this bug using a more recent version of Ubuntu, and comment on this bug as to whether or not this bug still occurs."
1803405,2019-10-19 04:17:42 UTC,[Expired for gimp (Ubuntu) because there has been no activity for 60 days.]
1803406,2019-08-29 20:51:09 UTC,"Katherine, the following does not solve the bug, however, it might help a little:"
1803406,2019-07-18 14:22:03 UTC,We are also experiencing this in 3.1 on our production server and 3.3 on our test server.
1803406,2019-07-26 13:50:16 UTC,I've looked at this on our test servers running 3.3.
1803406,2019-10-22 18:52:15 UTC,Dan's patch works for me! My sign-off branch at:
1803406,2019-08-29 18:55:01 UTC,We have the same problem in Evergreen 3.3.3.
1803406,2019-08-08 08:34:14 UTC,"We have found the problem in Evergreen 3.3.2 and  in the Evergreen 3.3 demo.g?
However, we see only the year (not the day and the month) - could the date format differ due to some setting?"
1803406,2019-12-06 16:10:08 UTC,"Pushed to master, rel_3_4, rel_3_3, and rel_3_2. Thanks, Dan and Terran!"
1803406,2019-08-08 00:16:51 UTC,We see this on 3.2 - this patch adjusts the bootstrap .col classes so the due date has more space to display. https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbriem/lp1803406_specific_due_date_obscured
1803407,2018-11-14 17:27:03 UTC,"At the end, this problem is due to Wayland !
In an X session, Totem is able to read the video !"
1803407,2018-11-14 20:53:19 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1803407,2018-11-14 20:53:48 UTC,Do you have any error on stdout/stderr? Could you add your journal log when getting the issue?
1803407,2018-11-15 18:07:53 UTC,"Hi, bonjour,"
1803407,2018-11-15 18:19:47 UTC,Oups !
1803415,2018-11-14 18:42:50 UTC,"Please disregard, the Delete option is now available on the Marc Edit view."
1803415,2018-11-15 19:29:23 UTC,"Let's leave this bug open, since the Docs group should probably add a note to the docs about the new location of the Delete function."
1803415,2019-04-24 18:54:52 UTC,Pull Request Submitted
1803415,2019-04-25 15:52:48 UTC,"Thanks for contributing, Derek!  I have removed your name from this bug, so others will know it is ready to review."
1803415,2019-08-22 21:47:18 UTC,"Thanks, @dzoladz and @remocrevo! I squashed this into a single commit, and merged to rel_3_2, rel_3_3, and master. I also took the liberty of adding a short follow-up commit to add some alt text to the screenshots in the MARC_Editor.adoc file."
1803415,2019-04-24 17:21:29 UTC,I'll take a stab at creating the documentation for this issue.
1803416,2019-11-24 11:36:48 UTC,"No.  Distributions like Ubuntu once released don't update their packages to new releases (with a few exceptions, like browser, or packages that do bugfix-only releases)."
1803417,2018-11-14 18:59:06 UTC,"Alerting the cataloger to this location correction is especially important if there are any associated copy location specific circulation policies in play. For example, if the circ policy is constructed to look at SYS1 DVD location, and the cataloger is unaware that location was automatically corrected to BR1 DVD, then the circulation will not follow the expected circ rules."
1803421,2019-01-11 16:16:29 UTC,This issue was fixed in the openstack/paunch 4.2.0 release.
1803424,2019-04-05 06:15:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803433,2018-11-16 19:32:30 UTC,Targeting stx.2019.03; affects region config
1803433,2019-03-15 19:18:20 UTC,Marking as Low / not release gating as there are no plans to support regions in the next StarlingX release.
1803439,2018-12-05 22:52:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803439,2018-12-05 22:58:52 UTC,none
1803441,2019-03-26 15:23:11 UTC,Is this about https://lists.gnu.org/archive/html/bug-bash/2017-03/msg00077.html ? Or about https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html ?
1803441,2019-03-21 16:27:31 UTC,"Hi Andrew, thanks for reporting this. Do you know if a CVE was assigned for this issue?"
1803441,2019-03-21 17:58:58 UTC,I have not seen a CVE for the original upstream bug but cannot say with certainty none was assigned.
1803441,2019-03-22 23:45:42 UTC,CVE-2019-9924
1803441,2019-03-26 20:26:33 UTC,"I don't think they are the same issue. Or, at least, the first issue was only partially fixed. I can see both Fedora 29 and Ubuntu 18.10 being still affected by the issue outlined in https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html, though they are not affected by https://lists.gnu.org/archive/html/bug-bash/2017-03/msg00077.html."
1803441,2019-03-26 20:19:52 UTC,"I'm sorry Riccardo, I didn't notice the two separate BASH_CMDS issues when
I filed the request. The only mention in the changelog is:"
1803441,2019-03-27 08:33:52 UTC,"After looking a bit more into this, it seems the issue in https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html is maybe not a real security concern, since rbash was wrongly configured. Having . in PATH is not good with rbash and that makes the whole thing flawed. So, we could say CVE-2019-9924 is just for the issue in https://lists.gnu.org/archive/html/bug-bash/2017-03/msg00077.html ."
1803441,2019-03-27 09:02:16 UTC,"@Ricardo: Yes, that was my intent with the original report. I didn't even know about the other issue when I submitted this issue."
1803441,2019-07-15 14:26:05 UTC,This bug was fixed in the package bash - 4.3-14ubuntu1.4
1803441,2019-08-05 16:13:38 UTC,Fixed released https://usn.ubuntu.com/4058-2/
1803441,2019-03-26 19:21:34 UTC,"Yes, that's basically the same issue."
1803442,2018-11-24 13:18:46 UTC,"I was testing with mainline/v4.20-rc3 but it was unusable on my machine: running the Quadro P3200 with the nouveau driver created a completely broken display (the nVidia 390 drivers are fine, though). At least this behavior is is identical between 4.18.0-11 and mainline/v4.20-rc3"
1803442,2018-11-14 22:00:08 UTC,This change was made by a bot.
1803442,2018-11-14 22:31:05 UTC,"Also interesting that I get in the kern.log messages like:
Nov 14 23:18:55 kenobi kernel: [14566.011739] CPU2: Core temperature above threshold, cpu clock throttled (total events = 3475)
Nov 14 23:18:55 kenobi kernel: [14566.011739] CPU8: Core temperature above threshold, cpu clock throttled (total events = 3475)
Nov 14 23:18:55 kenobi kernel: [14566.011741] CPU8: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011743] CPU2: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011839] CPU0: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011840] CPU7: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011841] CPU6: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011842] CPU1: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011843] CPU4: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011844] CPU10: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011845] CPU3: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011845] CPU9: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011847] CPU5: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.011847] CPU11: Package temperature above threshold, cpu clock throttled (total events = 7672)
Nov 14 23:18:55 kenobi kernel: [14566.012760] CPU2: Core temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012761] CPU8: Core temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012762] CPU8: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012762] CPU2: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012763] CPU7: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012764] CPU1: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012764] CPU6: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012765] CPU0: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012766] CPU9: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012782] CPU10: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012783] CPU4: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012783] CPU3: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012814] CPU11: Package temperature/speed normal
Nov 14 23:18:55 kenobi kernel: [14566.012815] CPU5: Package temperature/speed normal"
1803442,2018-11-16 19:51:11 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1803442,2018-11-21 22:14:16 UTC,The system is new so I can't comment whether it was better using a previous ubuntu version.
1803444,2020-09-18 13:39:47 UTC,I'm pretty sure that has been fixed for a while now and should be working back to stein.
1803444,2018-11-15 06:51:17 UTC,This workaround seems to work:
1803444,2018-11-20 16:42:21 UTC,Running only the gnocci playbook works fine:
1803444,2018-11-27 16:37:26 UTC,"Francois,"
1803444,2018-11-27 16:38:43 UTC,"Francois,"
1803449,2018-11-14 23:07:44 UTC,"Review in progress for https://review.opencontrail.org/47681
Submitter: Piyush Srivastava (<email address hidden>)"
1803452,2020-05-03 04:17:33 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1803452,2020-03-03 13:32:12 UTC,"very old, letting expire unless someone has any current news"
1803453,2021-02-15 23:55:16 UTC,"Still an issue, see LP:1915765"
1803453,2018-11-14 23:14:48 UTC,"Also, sudo should be run with '-i'."
1803461,2020-03-07 11:12:31 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1803464,2018-12-06 03:59:44 UTC,This appears to have been fixed recently; at least apache2ctl status worked for me.
1803467,2018-11-26 00:33:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803469,2018-12-10 11:58:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803470,2018-11-16 19:58:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803474,2019-04-30 02:44:52 UTC,"Thank you so much, it was as simple as adding   GRUB_CMDLINE_LINUX=""i8042.nomux=1 i8042.reset""   on grub, updating and rebooting."
1803474,2018-11-15 02:00:08 UTC,This change was made by a bot.
1803474,2018-11-16 19:50:29 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1803474,2019-01-16 04:18:01 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1803474,2019-04-29 01:56:04 UTC,https://www.linuxquestions.org/questions/linux-newbie-8/ps-2-touchpad-not-working-correctly-4175643961/ seem to point to a working dkms-based solution already.
1803474,2019-04-29 00:29:36 UTC,"Hello, I am using Ubuntu Budgie (19.04) now and having the exact same problem. I stopped using the previous version because it was useless to me. Current kernel version is 5.1.0-050100rc6-generic
 version."
1803474,2019-04-29 01:03:23 UTC,There is some error during initialization in elantech driver.
1803474,2019-05-02 01:55:15 UTC,"@flxren, I don't have the hardware so I didn't have a try on the viable solution. I thought it takes a dkms to fix? Could you also help comment some more detailed steps, so others' with the same hardware may have another reference?"
1803474,2019-07-01 06:48:27 UTC,"Are both ""i8042.nomux=1"" ""i8042.reset"" required to make touchpad work, or just one of the parameter can make the touchpad work?"
1803481,2018-11-15 04:31:45 UTC,"reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1803481,2018-11-16 23:57:47 UTC,"Not reproduced with Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1-64"
1803481,2019-03-01 06:12:44 UTC,"This is still reproducible in Inkscape 0.92.4 (5da689c313, 2019-01-14), Win 8.1-64"
1803481,2019-03-01 15:07:24 UTC,"since Inkscape is moving its bug tracking system to GitLab it might be best to re-issue this report at:
https://gitlab.com/inkscape/inbox/issues"
1803481,2019-04-16 10:16:00 UTC,Tristan Bailey (OP) has moved the issue already (see https://gitlab.com/inkscape/inkscape/issues/118). So closing this issue as part of bug migration (also fix committed :-))
1803481,2018-11-15 04:37:21 UTC,"reproduced on Windows 10, Inkscape 0.92+devel (bac5395, 2018-11-10)"
1803486,2018-11-22 17:34:24 UTC,"I'm sorry, Akihiro. I did it by mistake:("
1803486,2018-11-22 10:51:50 UTC,"Ivan, what is the reason of ""Won't Fix""?"
1803520,2018-11-16 18:13:05 UTC,"Does this otherwise break any firefox functionality, or impair the system in any way?"
1803520,2018-11-19 09:42:11 UTC,Thanks for the confirmation. Setting the importance accordingly.
1803520,2018-11-17 04:39:18 UTC,"@ Oliver #3 no firefox works like a charm on this system
i cannot see breaking or unexpected behaviour GUI
only the syslog errors"
1803520,2018-11-16 18:12:28 UTC,"Not seeing those when testing in a clean 18.04 VM, but it looks like others are seeing them: https://askubuntu.com/questions/1093181/shutdown-freeze"
1803521,2018-11-15 10:23:32 UTC,There are 4 gnome-initial-setup.desktop files in my system
1803522,2018-11-15 11:02:51 UTC,"So when not using redis and instead using tooz as coordinator for gnocchi, deployment is fine but gnocchi_metricd container spams with:"
1803522,2018-11-15 19:25:13 UTC,Good evening.
1803522,2018-11-16 15:02:29 UTC,It also seems this error can happen directly after deployment:
1803522,2019-09-12 14:06:13 UTC,Is there something we need to do in kolla?
1803522,2019-09-12 14:06:39 UTC,Is this still a bug with latest code? Can you reproduce this and upload new logs?
1803522,2019-11-12 04:18:15 UTC,[Expired for kolla because there has been no activity for 60 days.]
1803522,2019-11-12 04:18:18 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1803524,2018-11-16 20:17:37 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1803527,2019-01-17 01:50:48 UTC,"> The left panel is over the purple-like lock screen and unusable (the only thing is that icons illuminate with mouse movement but they don't respond on click.
"
1803527,2018-11-19 02:38:02 UTC,Please run this command to send us more information about the system:
1803527,2018-11-20 18:59:47 UTC,apport information
1803527,2018-11-20 18:59:49 UTC,apport information
1803527,2018-11-20 18:59:50 UTC,apport information
1803527,2018-11-21 02:31:56 UTC,You seem to have a few extensions installed:
1803527,2018-11-26 11:06:56 UTC,It happens that after I original post this bug the frequency unreasonably decreased. But the problem is not solved with deactivated extensions.
1803527,2018-11-27 09:17:55 UTC,Could you attach your 'journalctl -b 0' log after getting the issue?
1803527,2018-11-27 10:06:25 UTC,Note that you may need to uninstall extensions and not just disable them. A broken extension can still break the shell even when disabled.
1803527,2019-01-07 08:12:44 UTC,"This sounds similar to bug 1740792. Although if you're experiencing a crash then it's a different issue, so please try these steps to see if there was any crash that can be reported:"
1803527,2019-01-16 10:05:20 UTC,This is not the same bug. After resuming from suspend with a new installation of ubuntu 18.10 and no extensions installed this happened:
1803527,2019-01-16 10:17:26 UTC,"ps. on /var/crash there is only a ""_user_bin_variety.1000.crash"" and some variety and rhythmbox .uploaded"
1803527,2019-07-22 04:06:29 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1803527,2019-01-27 13:13:59 UTC,"I have an update although. I enabled password promt on login, but the problem remains. I have two gnome extensions installed. On previous checks it doesn't happened that (if the password was enabled, then everything was fine). Now, either with password either without, sometimes (about 50%) returning from suspend or lock screen, the dash is above the lock screen and either I cannot login either I login but the app-icons missing from topbar and the gnome desktop lags in general or dash is non transparent and again app-icons missing from topbar and the gnome desktop lags in general. Hope it helps"
1803527,2019-01-17 17:59:00 UTC,ok
1803527,2019-01-16 11:32:32 UTC,"ps. there is a catch. Since my previous comment I am trying to reproduce the error. In the beginning it asks password no matter what. After that I tried this: ""gsettings set org.gnome.desktop.screensaver ubuntu-lock-on-suspend false"" that I found it here: ""https://askubuntu.com/questions/1029696/disable-password-request-from-from-suspend-18-04"". So the password is gone again. But I test it without addons installed (as in the first place (with the photo of my screen I sent above) and with the two addons I use (Advanced Volume Mixer by Hatell and GSConnect by andyholmes). The problem seems not to be reproducible. Although today morning as the day before, it was there. I suspend and resume over 10 times now, and it seems to be ok. I will try to let it more on stand by and let you know (I cannot understand the causes - like no logic at all)."
1803527,2019-01-16 19:22:43 UTC,I manage to record the crash. I resume from suspend 5 hours later (pc was suspended for about 5h) and the following behavior happened:
1803527,2019-01-17 01:53:46 UTC,Please wait until bug 1769383 is declared fixed for 18.10 and then we can see if the problem still occurs.
1803532,2019-01-03 18:23:52 UTC,"Reviewed:  https://review.opencontrail.org/48383
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/c963aa5e863da93a6db8b7a2a95984b514ea7745
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1803532,2018-12-27 16:04:50 UTC,"Review in progress for https://review.opencontrail.org/48383
Submitter: Magda Zaremba (<email address hidden>)"
1803538,2018-11-15 12:29:41 UTC,"If you can supply a targetted patch I will consider it, but I'm not going to go changing the default ruby version in a stable release."
1803553,2019-01-09 08:56:15 UTC,I also confirm this bug with the same behavior.
1803553,2019-01-11 15:05:45 UTC,This patch seems to correct the issue.
1803553,2019-01-11 15:26:41 UTC,But it prevents selection of the last two chars. Looking.
1803553,2019-01-11 16:44:09 UTC,"Hmm. That's actually already an issue, it prevents the crash."
1803553,2019-01-11 16:45:47 UTC,s/it/but it/
1803553,2019-01-11 19:02:29 UTC,"That patch disallows the legitimate case where best_char_index == _characters.size() - 1. I think better is this patch, which returns end() if the best index is equal to the size. I haven't tested this, as I'm having issues building in Fedora with the setup to abort on out-of-bounds access."
1803553,2019-01-16 20:24:56 UTC,This bug is fixed in gitlab merge request 488.
1803553,2019-01-10 21:14:55 UTC,Reproducing a comment in the downstream bug:
1803553,2019-04-25 15:26:00 UTC,Backported to 0.92.x here: https://gitlab.com/inkscape/inkscape/merge_requests/647
1803557,2019-07-31 21:00:35 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1803557,2019-07-31 21:00:43 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/612794
Reason: This review is > 90 days without comment, and failed Zuul the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1803559,2020-06-07 04:17:19 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1803564,2020-01-16 11:09:34 UTC,"Fixed in lazr.restful 0.21.0, now deployed on Launchpad production."
1803565,2019-08-14 02:58:17 UTC,"I've triggered this today with Luminous on Bionic, ceph-osd-285."
1803565,2018-12-04 16:17:53 UTC,"Worth noting that I think this is using ceph for key storage, so is not using vaultlocker."
1803565,2018-11-15 15:09:48 UTC,This is reliably seen on the ceph-encrypt mojo specs for bionic-queens(L) and bionic-rocky(M)
1803572,2019-01-14 17:04:57 UTC,"Review in progress for https://review.opencontrail.org/48666
Submitter: Michal Clapinski (<email address hidden>)"
1803572,2019-01-18 08:20:10 UTC,"Reviewed:  https://review.opencontrail.org/48666
Committed: http://github.com/Juniper/contrail-vrouter/commit/3a73deb399080f6236743a1da1cb4d307ef34438
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1803575,2018-11-19 08:37:23 UTC,A blueprint should be create.
1803575,2018-11-20 08:44:28 UTC,Blueprint https://blueprints.launchpad.net/nova/+spec/virtio-scsi-by-default has been created.
1803575,2019-06-13 23:43:39 UTC,this is really a feature request not a bug.
1803575,2020-04-17 14:52:36 UTC,"While the issue you highlight here is real, this wouldn't be a good solution. The primary issue with this approach is the same issue we have with the '[libvirt] rx_queue_size' and '[libvirt] tx_queue_size' - namely that it can break live migration as two hosts with different values will result in a change in the instance XML. If we were to take this approach, we'd have to store the information as part of the instance and we don't have a way to do this other than via the flavor or image metadata. As such, I'm closing this as WONTFIX."
1803581,2018-11-17 08:19:42 UTC,"I reported the GDM issue upstream, but LP does not handle Gitlab URLs yet: https://gitlab.gnome.org/GNOME/gdm/issues/443"
1803581,2018-11-16 01:53:48 UTC,Please report this bug to the GDM developers here:
1803581,2018-11-19 02:39:27 UTC,I know. Thanks.
1803584,2019-11-14 18:46:24 UTC,"HI Janet,"
1803584,2018-11-15 19:00:24 UTC,Looks like a reference to MultiMap was added to the wrong clearWorking() function. The template editor dies trying to clear that while it't not currently possible to clear multiple items when editing them. This fixes it:
1803584,2019-03-05 16:03:46 UTC,This code works as described on our system running EG 3.2.4.
1803584,2019-03-05 21:10:02 UTC,"I have tested this code and consent to signing off on it with my name, Beth Willis and my email address, <email address hidden>."
1803584,2019-03-08 17:14:45 UTC,New branch pushed:
1803584,2019-05-24 18:52:22 UTC,I note that Bill's follow-up patch is the belt to the suspenders I propose in 1830394.
1803584,2019-08-03 16:17:08 UTC,"Pushed to master, rel_3_3, and rel_3_2. Thanks, Jason, Beth, and Bill!"
1803584,2019-11-11 23:30:08 UTC,We now have this fix on release 3.2.8.
1803584,2019-11-14 20:32:34 UTC,"I think you are doing something different.
When someone adds holdings, the circ library of the workstation or of library selected in Holdings View if you start from there, is automatically filled in. When you apply a template that has NOT been created after using the 'clear' button, the circ library is saved in the item record and the item is created even if that field is not saved in the template."
1803584,2019-11-14 20:06:54 UTC,"Hi Janet,"
1803584,2019-11-14 17:49:24 UTC,I cannot replicate Janet's problem in our 3-2-8 system.  I followed the steps she indicated and included a circulation library in both templates.  I was able to create and save new items using both templates and did the circulation library was correct for both.
1803584,2019-11-14 18:26:12 UTC,"Hi Beth,
You are correct, we are able to confirm both templates work if the circ library IS stored in the template. The problem is if the circ library is NOT stored in the template."
1803584,2019-11-14 19:34:05 UTC,PINES libraries also have holdings templates with the circ library unset.
1803585,2018-11-15 19:06:29 UTC,I have been working for a while now in CI for KiCad. I think it would be easy to pack KiCad into a docker image and use KiCad to generate the corresponding reports. Just as an idea.
1803585,2018-11-15 18:47:15 UTC,"The problem I have with this solution aside from the amount of effort
involved in implementing is keeping the code in kicad up to date with
the klc python scripts.  Reusing the scripts makes more sense to me even
if it means improving the python scripts so they can be called without
using files.  Although it would be easy enough to create a memory file
and pass that to the script."
1803585,2018-11-15 18:27:41 UTC,"I assume this is linked to future DRC and ERC improvements, to have the ability to add custom rules and scripts, as well as to have the ability to run DRC/ERC from the python interface."
1803585,2018-11-15 17:53:18 UTC,"From the quality point of view I believe that would be more desirable to use existing in memory information through existing C++ interfaces. Current python scripts read the corresponding item file, load it into memory, perform parsing through a completely different engine than the one used by KiCad and then perform checks. That looks like very inefficient to me, both from th execution and maintenance point of views."
1803585,2018-11-15 17:33:16 UTC,It should not be terribly difficult at all to call the KLC from the footprint editor since python support is already in place for board and footprint editor.  The symbol editor is a different story.  Python support has not been implemented yet.  Hopefully it will be part of the v6 development but that may be a stretch as there are plenty of tasks planned for v6.  Until this happens your KLC implementation would only support footprints.  I don't know how useful this would be.
1803585,2018-11-15 16:47:35 UTC,I don't know anything about KiCad source code structure so I am not brave enough to provide a fix for this issue. On the other hand if a basic class structure was done by someone I would be willing to contribute with further work to migrate the existing checks.
1803587,2018-11-16 18:47:22 UTC,"@vorlon: OK, being commented out (and not set elsewhere) makes it default to True.
The misleading comment is fixed in later releases."
1803587,2018-11-16 18:46:16 UTC,In my tests u-u successfully removed the kernels as new unused packages even when hitting LP: #1803749 for the record.
1803587,2018-11-16 18:16:27 UTC,"$ grep -r Remove-New /etc/apt
/etc/apt/apt.conf.d/50unattended-upgrades://Unattended-Upgrade::Remove-New-Unused-Dependencies ""false"";
$"
1803587,2018-11-16 17:09:48 UTC,"@vorlon: OK, let's use this bug to track the improvement for u-m."
1803587,2018-11-15 19:34:39 UTC,"(In which case, I think this still warrants improvement, since AIUI the next run of update-manager will do removals after installations, which means a high water mark of 4 kernels rather than 3 which is what we want)"
1803587,2018-11-15 19:33:44 UTC,History log:
1803587,2018-11-15 17:22:17 UTC,Could you please attach the relavant part of dpkg history log a and dpkg terminal log?
1803588,2018-11-21 16:42:19 UTC,Could you please run 'apport-collect 1803588' in a terminal so log files regarding the upgrade process will be added to your bug report?
1803591,2018-11-22 11:18:19 UTC,The freezer logs location:
1803600,2019-12-13 05:30:05 UTC,Also a problem on my MSI GS43VR for 19.10
1803600,2018-12-13 07:58:53 UTC,Please test the kernel [1] with patch [2].
1803600,2018-11-21 23:52:59 UTC,"@Kai-Heng Feng : Wow, it fixed the issue for me at least, on Lenovo Thinkpad L580. :) :)"
1803600,2019-02-14 04:28:52 UTC,I'm using a Thinkpad T480s and while my Elantech touchpad was mostly functional upon moving to 18.10 two-finger right-click and three-finger middle-click stopped working. `libinput list-devices` showed 'none' for a couple of features like 'Click methods.'
1803600,2019-02-08 18:22:50 UTC,#8 from Kai-Heng Feng (kaihengfeng) fixed the issue for me on Lenovo P72 Intel® Core™ i7-8750H running Ubuntu 18.10 kernel 4.18.0-15-generic #16-Ubuntu SMP. I added the following line to my /etc/default/grub
1803600,2018-12-21 12:58:45 UTC,Lenovo ThinkPad L580:
1803600,2018-12-14 21:09:05 UTC,"P52:
""cat /sys/bus/serio/devices/serio1/firmware_id"":
PNP: LEN2132 PNP0f13"
1803600,2018-12-13 11:31:35 UTC,"L480:
cat /sys/bus/serio/devices/serio1/firmware_id
PNP: LEN2036 PNP0f13"
1803600,2018-12-13 05:46:26 UTC,"Upstream maintainer wants to know the firmware information of your touchpad, can you provide it?"
1803600,2018-12-06 18:31:54 UTC,Lenovo Thinkpad P52 is another laptop that uses this touchpad. Same issues with the kernel detecting/configuring it.
1803600,2018-11-26 12:18:10 UTC,"According to https://bugs.archlinux.org/task/59714, ThinkPad P72 is also affected."
1803600,2018-11-22 04:01:49 UTC,"Ok, I'll discuss with the patch author about how to solve the issue. Seems to me DMI based quirk is required."
1803600,2019-08-08 14:59:29 UTC,"The touchpad of my Lenovo Thinkpad L480 does not work in both Ubuntu Disco live and Eoan daily image. However, it works fine in Bionic 18.04.3 with the HWE kernel of Disco. So I guess there is a bug in a different place beside the kernel."
1803600,2018-11-21 12:59:48 UTC,"Yes, this seems to fix it with 4.20"
1803600,2018-11-21 06:36:40 UTC,"Boot with kernel parameter ""psmouse.elantech_smbus=0"" and see if this helps."
1803600,2018-11-19 17:17:20 UTC,"I have Lenovo L580. And a similar issue. The install image written to the USB drive worked fine, but after installation touchpad simply did not work. I've tried everything suggested (utilizing some google searches ...), including kernel parameters, blacklisting various i2c hid modules, and all the combinations, but nothing. It's a fresh 18.10 install, I have no idea if it would work with previous versions, but I rather wouldn't downgrade, if this bug is expected to be fixed."
1803600,2018-11-16 20:16:30 UTC,"Bug exists in upstream, 4.18.0-10 and 4.18.0-11 but not in 4.15.0-38"
1803600,2018-11-16 19:38:34 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1803600,2018-11-16 02:30:06 UTC,This change was made by a bot.
1803600,2018-11-16 02:02:01 UTC,Reassigned to the kernel.
1803600,2018-11-15 20:07:08 UTC,"Sorry, this is not meant to be in xorg. (Or I actually don't know...) However the bug-report application itsself seems to be buggy ;) (or the user using it)"
1803600,2019-05-31 03:12:05 UTC,"Thinkpad L480, same problem, same solution, but encountered while upgrading from 18.10 to 19.04. Machine was fresh installed with 18.10 and touchpad worked out of the box."
1803600,2019-05-19 09:15:55 UTC,I'm using a Thinkpad L480.
1803601,2018-11-15 20:32:37 UTC,A possible fix would be to make the unit execution conditional to the update-motd fragment being executable:
1803601,2019-01-30 20:51:53 UTC,I have the same problem and it looks like this issue brings my server in real trouble. I deactivated this services completly now and hope it helps.
1803601,2020-05-06 19:06:16 UTC,"On 2020-05-06 2:49 p.m., Andreas Hasenack wrote:

> There are many alternatives here.
"
1803601,2020-05-06 18:49:34 UTC,"There are many alternatives here. What you describe is one, and you could then also add a systemd override with that exec check. A bit cumbersome, though."
1803604,2019-11-22 12:13:29 UTC,Still not working in Ubuntu 19.10.
1803604,2018-03-05 17:13:13 UTC,"Description:
When tools/options/internet/email is set to /usr/bin/claws-mail, send by email fails.  If it's unsert, to allow a default of xdg-email, it still fails, and if it's explicitly set to /usr/bin/xdg-email it still does not work.  Trying to Send now leaves me in limbo, somewhere between LO and my email client (Claws), with neither having focus, so alt-tab gets me nowhere until I manually reassert focus on one or the other.
Build ID: 1:6.0.2~rc1-0ubuntu0.16.04.1~lo1
on Ubunto 16.04.4 LTS"
1803604,2018-03-06 07:32:06 UTC,"Tested and I can reproduce the issue when claws-mail is the default e-mail client on the system, even with apparmor profiles disabled (so unlikely to be an apparmor-related issue)."
1803604,2018-03-06 08:14:20 UTC,"(In reply to Olivier Tilloy from comment #1)

> Tested and I can reproduce the issue
"
1803604,2018-09-17 11:16:48 UTC,"Send by email still fails in 6.1.1.2.
This is disappointing, since 'sending' a document is a basic operation, which users would naturally expect.  As noted, this all worked prior to 6.0, so it's a regression."
1803604,2018-09-17 13:14:22 UTC,"I see a similar report on Apache OpenOffice, also on the Ubuntu bug reports.
Following a hint from the latter, I deleted the entry ""/usr/bin/claws-mail"" in Tools/Options/Internet/Email and tried again to send a document.  This time no error was reported to the GUI, but I'd called soffice from the commandline, and there an error had appeared ""/usr/lib/libreoffice/program/senddoc: 361: /usr/lib/libreoffice/program/senddoc: /usr/bin/claws-mail: Permission denied"""
1803604,2018-11-16 17:32:14 UTC,"I can observe the issue if I set the ""Tools > Options > Internet > E-mail"" field to ""/usr/bin/thunderbird"". But if I unset the field (blank) then LibreOffice calls xdg-email, which figures out the default e-mail client as expected (assuming thunderbird is configured as your default e-mail client)."
1803604,2018-09-18 09:50:33 UTC,"I modified 'senddoc' temporarily, to 'echo' the claws-mail command, and opened my testfile again from the commandline.  That showed
/usr/bin/claws-mail --attach /tmp/lu35337hoq3k.tmp/lu35337hoq3n.tmp/errors_090715.odt
(all on one line)."
1803604,2018-09-18 11:23:56 UTC,"See also Ubuntu Bug #1748895
LO unable to find a working email configuration"
1803604,2018-09-20 10:01:12 UTC,"I should have added that when Tools ... Email is set to xdg-email (timed at 10:12) or set to be blank (timed at 10:16), then claws-mail is called, but without focus, and without any COMPOSE window.  Focus has to be manually restored to CLAWS by clicking on it, before anything else can be done ..."
1803604,2018-09-22 10:39:55 UTC,"Sorry to post so much, but I think I've found the problem, and a solution."
1803604,2018-10-08 11:13:15 UTC,"Created attachment 145467
A proposed revision for /usr/lib/libreoffice/program/senddoc"
1803604,2018-10-08 11:15:16 UTC,"The uploaded revision of SENDDOC works ok on my system (LO 6.1.2.1, Ubuntu 18.04.1) when Tools, Options, Internet, Email E-mail program is left blank, or filled as /usr/bin/xdg-email."
1803604,2018-10-08 11:18:51 UTC,"Hi Bernard,
Thanks for the patch!
Would you mind submitting it to gerrit instead? you can have more informacion here https://wiki.documentfoundation.org/Development/gerrit/SubmitPatch"
1803604,2018-10-08 18:09:18 UTC,"Hi Xisco,"
1803604,2018-11-11 09:11:41 UTC,Since upgraded to LO 6.1.0 onwards started facing the problem of documents send by email stopped working
1803604,2018-11-11 14:13:58 UTC,"GEARY works simply because it is not named in program senddoc, which then uses xdg-email as a default, to call the system email client, whatever it is.  But hey, as an entry in Tools/.../Internet, it works!"
1803604,2018-09-20 09:56:35 UTC,"With respect, I think the problem is related to apparmor.
When Tools/Options/Internet/Email is set to /usr/bin/claws-mail, the error window appears (working email client not found), an error message is sent to screen (Writer called from the command line),
""/usr/lib/libreoffice/program/senddoc: 366: /usr/lib/libreoffice/program/senddoc: /usr/bin/claws-mail: Permission denied"", and the kernel log contains 3 DENIED lines,
Sep 20 10:09:04 USER_ID-Inspiron-5767 kernel: [ 1965.191418] audit: type=1400 audit(1537434544.991:41): apparmor=""DENIED"" operation=""file_inherit"" profile=""libreoffice-senddoc"" name=""/home/USR/errors_090715.odt"" pid=4934 comm=""senddoc"" requested_mask=""wr"" denied_mask=""wr"" fsuid=1001 ouid=1001
Sep 20 10:09:04 USER_ID-Inspiron-5767 kernel: [ 1965.191423] audit: type=1400 audit(1537434544.991:42): apparmor=""DENIED"" operation=""file_inherit"" profile=""libreoffice-senddoc"" name=""/home/USR/.config/libreoffice/4/user/uno_packages/cache/uno_packages.pmap"" pid=4934 comm=""senddoc"" requested_mask=""wr"" denied_mask=""wr"" fsuid=1001 ouid=1001
Sep 20 10:09:05 USER_ID-Inspiron-5767 kernel: [ 1965.196286] audit: type=1400 audit(1537434544.995:43): apparmor=""DENIED"" operation=""exec"" profile=""libreoffice-senddoc"" name=""/usr/bin/claws-mail"" pid=4940 comm=""senddoc"" requested_mask=""x"" denied_mask=""x"" fsuid=1001 ouid=0"
1803604,2019-08-14 11:04:15 UTC,"6.3.0.4 includes most of the changes I suggested, but still fails to operate properly - it switches the focus to the email client, but fails to create a new email."
1803604,2018-11-12 17:37:35 UTC,"(In reply to Bernard Moreton from comment #15)

> GEARY works simply because it is not named in program senddoc, which then
> uses xdg-email as a default, to call the system email client, whatever it
> is.  But hey, as an entry in Tools/.../Internet, it works!
>
> So, possibly, would ""/usr/bin/wxyz"" ...
"
1803604,2020-11-26 11:30:59 UTC,"There is a new twist to this saga.
With LO 7.0.1.2 today I get an error message
/home/mbm/.claws-mail/mimetmp/.comments: unlink: Is a directory"
1803604,2020-11-27 06:06:03 UTC,"Hopefully not confusing things by adding this information... I use LibreOffice ""E-mail as PDF"" a lot. After about a fortnight of not having used it, when it worked fine, today I tried again."
1803604,2020-08-13 20:17:13 UTC,"Changing the email-client to /usr/bin/thunderbird %s solved the problem for me, can send files from writer."
1803604,2021-01-19 01:39:50 UTC,I noticed a couple of days ago (17th or 18th Jan 2021) that Send e-mail as PDF started to work again. Presumably some update fixed things. So that's great!
1803604,2020-12-21 16:55:36 UTC,"It works under Ubuntu Linux 20.04 as well. Unfortunately only if you ""disable"" the apparmor rules for senddoc or set it to ""complain"" mode. In this mode the rules are not blocked, but they are logged."
1803604,2020-12-21 02:35:16 UTC,"Problem affecting LibreOffice 7.0.4.2 with Thunderbird 68.10.0 as well on Ubuntu-MATE 20.04.1.  This is pretty basic functionality, I'm surprised it's broken on Linux yet works fine on Windows."
1803604,2020-11-27 12:41:33 UTC,"And further to my last comment, the point is proved.
Claws[-mail] is set in senddoc to use
ATTACH=""${ATTACH:-}${ATTACH:+ }$2""
without any reference to encoding."
1803604,2020-11-27 09:00:31 UTC,"Just to clarify my remarks yesterday,
the error window in Claws-mail showed a filename that looked very much as though it had been encoded."
1803610,2019-06-27 20:36:20 UTC,"Same here, it is very to implement Masakari to Kolla without documentation."
1803612,2018-11-15 21:45:49 UTC,activity not opening pune shollapur
1803623,2019-07-06 14:45:11 UTC,"Fixed in revision 44734dc05993d9ec19569b64b75af7de06e52c81
https://git.launchpad.net/kicad/patch/?id=44734dc05993d9ec19569b64b75af7de06e52c81"
1803629,2018-11-19 02:57:55 UTC,"The panics in metrics are due to the system state being closed but the worker to gather the metrics is not stopped. The stateworker which registers the prometheus collector should unregister it when the worker dies. This is only done using a defer in the worker loop and it seems possible on a heavily loaded system that the state tracker Done() could be called before the defer executes, so there's a window where the collector could use a closed state pool."
1803629,2019-05-14 06:19:52 UTC,I am marking this as Incomplete to let it expire - comment # 7 seems to indicated that there were some changes landed that would prevent these panics from re-occurring. Let's re-open it if anyone sees re-occurrence.
1803629,2018-11-16 04:54:01 UTC,Just to mention the Panic() that we saw is what happens if you have a shared mgo.Session and one side calls .Close() while the other side tries to do a query. (Using a closed Session is a panic())
1803629,2018-11-16 04:54:39 UTC,"Or as likely we have some sort of ""defer st.Close()"" which is trying to close something already closed."
1803629,2018-11-22 03:27:22 UTC,We're parking these for now as fixes have landed elsewhere to address a state leak and we want to see if that incidentally addresses this issue.
1803629,2018-11-16 07:20:40 UTC,I have not looked at panic 2 which seems to be occuring in metrics collection path.
1803629,2018-11-19 00:01:01 UTC,The issue isn't the recently changed code - the new code simply essentially reorders the business logic a little - the state object is still used to fetch a unit and from there status is extracted. The root cause appears to be that the multiwatcher worker passes to a worker loop a state object that may be closed outside the loop when things are still being initialised.
1803629,2019-07-14 04:17:25 UTC,[Expired for juju because there has been no activity for 60 days.]
1803629,2019-07-14 04:17:23 UTC,[Expired for juju 2.4 because there has been no activity for 60 days.]
1803636,2018-11-16 05:40:43 UTC,It might hit. Is this something you've faced? I.e have you run out of MAX_PROCS?
1803636,2018-11-20 17:57:24 UTC,This might be a dupe of https://bugs.launchpad.net/swift/+bug/1554233 (fixed in swift > 2.15)
1803648,2019-02-21 21:09:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638510"
1803648,2018-12-26 02:58:36 UTC,"Oh god, After using the same method mentioned in #4, I found I forgot to also update this test setup:
https://review.openstack.org/#/c/618499/3/cinder/tests/unit/backup/drivers/test_backup_nfs.py@209"
1803648,2018-12-21 22:10:34 UTC,The issue still persists
1803648,2018-12-17 16:14:10 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/625644"
1803648,2018-12-12 18:28:09 UTC,"Reviewed:  https://review.openstack.org/618499
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=593d8dfa79980db651b88957f766604240e64e76
Submitter: Zuul
Branch:    master"
1803648,2019-01-23 19:11:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632796"
1803648,2018-11-19 11:06:23 UTC,"Change abandoned by Rajat Dhasmana (<email address hidden>) on branch: master
Review: https://review.openstack.org/618457"
1803648,2018-11-19 07:59:05 UTC,"diff --git a/cinder/tests/unit/fake_notifier.py b/cinder/tests/unit/fake_notifier.py
index 7e07a26..8a5fef0 100644
--- a/cinder/tests/unit/fake_notifier.py
+++ b/cinder/tests/unit/fake_notifier.py
@@ -49,6 +49,8 @@ class FakeNotifier(object):
         return len(self.notifications)"
1803648,2018-11-19 04:07:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/618670"
1803648,2018-11-16 10:00:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/618499"
1803648,2018-11-16 04:22:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/618457"
1803648,2019-01-09 02:40:31 UTC,"Reviewed:  https://review.openstack.org/627329
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=32ef92fa4bc7b7db6df1c023b6460fb25474b0f5
Submitter: Zuul
Branch:    master"
1803648,2019-01-11 21:20:24 UTC,"Reviewed:  https://review.openstack.org/625644
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=15c7ac73bc49a4d67c256890ff7ac259a4d001e2
Submitter: Zuul
Branch:    stable/rocky"
1803648,2018-12-26 03:00:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627329"
1803648,2018-12-08 05:16:01 UTC,"Reviewed:  https://review.openstack.org/618670
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=a2b9d4dd9bff6dab5047cd5841672c8cb22d9d37
Submitter: Zuul
Branch:    master"
1803648,2019-02-22 22:56:06 UTC,"Reviewed:  https://review.openstack.org/638510
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=6f9135b6a48d7e900e8b33adf1e69c2463eac852
Submitter: Zuul
Branch:    master"
1803648,2020-09-23 17:34:10 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/632796
Reason: Been sitting for a while. Feel free to restore and update if still needed."
1803648,2019-10-07 21:57:19 UTC,"Reviewed:  https://review.opendev.org/686523
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=ea39101a9c19f61cd5dec98986f67aad9518fdc4
Submitter: Zuul
Branch:    stable/queens"
1803648,2019-10-04 05:55:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/686523"
1803648,2019-09-13 03:16:25 UTC,"Reviewed:  https://review.opendev.org/681737
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=47f94ce24c5b3a21d1f004e466cd885b042b6894
Submitter: Zuul
Branch:    stable/stein"
1803648,2019-09-12 12:57:07 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/681737"
1803648,2019-09-10 23:08:33 UTC,"Reviewed:  https://review.opendev.org/681318
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=c586d0886ad4b239831a0b4a1827a8b4d054c120
Submitter: Zuul
Branch:    master"
1803648,2019-09-10 17:51:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/681318"
1803648,2019-04-19 00:48:17 UTC,"Reviewed:  https://review.openstack.org/651513
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=8bf4a1e801950dc26c07d43ae56b81146595c7cd
Submitter: Zuul
Branch:    stable/rocky"
1803648,2019-04-10 23:13:05 UTC,"Reviewed:  https://review.openstack.org/649634
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=96c3892bb103b7318ed650da089c7da412e61116
Submitter: Zuul
Branch:    stable/rocky"
1803648,2019-04-10 12:16:28 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/651513"
1803648,2019-04-09 21:21:15 UTC,"Reviewed:  https://review.openstack.org/651328
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d4c8a792da0fec2ba3547c101f396eb67cadc490
Submitter: Zuul
Branch:    master"
1803648,2019-04-09 16:56:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651328"
1803648,2019-04-03 14:33:32 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649634"
1803648,2019-03-21 17:21:58 UTC,This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.
1803648,2019-01-18 03:36:29 UTC,"@mriedem add this bug to elastic-recheck in [1], and it shows that this bug is still triggered."
1803648,2019-01-18 03:47:44 UTC,"Some investigation:
1. The cinder base test case using FakeNotifier mocks out all the real notifier [1][2].
2. [3][4] mock all the backup.createprogress related test case.
3. #4 shows the way to find all backup.createprogress info, after [3][4], all backup.createprogress notify has been mocked."
1803656,2019-02-16 14:43:13 UTC,"Change abandoned by jacky06 (zhang.min@99cloud.net) on branch: master
Review: https://review.openstack.org/618649"
1803656,2018-11-16 10:07:28 UTC,"Needs more information. Do you mean that setting openstack_release to the default of 'auto' does not work? I hit that issue recently, and was told it is expected, and need to set it to master/rocky etc."
1803656,2018-11-16 10:26:51 UTC,@Mark Goddard
1803656,2018-11-19 00:26:28 UTC,"I don't think this is a bug. This is how Kolla-ansible operates. You can download images from Docker Hub, other public Docker Registry or build those yourself. Then you can either re-tag images or simply provide expected images tag as configuration option."
1803656,2019-02-12 03:10:19 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.openstack.org/583641"
1803663,2020-08-28 15:27:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803667,2019-01-19 04:17:24 UTC,[Expired for base-installer (Ubuntu) because there has been no activity for 60 days.]
1803667,2018-11-19 07:12:13 UTC,"Hi Yuhua,
I think we need understand more what the actual request is about.
In general we are open to improve the installation paths and do so often, but in this case it is yet unclear what you actually request."
1803667,2018-11-19 08:26:18 UTC,"Right now if i need unattended install, I need to customize the official iso
1.take install guestOS with ubuntu-18.10-desktop-amd64.iso as a example:
  if I need unattended installation with ubuntu-18.10-desktop-amd64.iso, I need to uncompress the
  iso, modify boot parameter in file boot/grub/grub.cfg and modify file preseed/ubuntu.preseed,
  and then make a new iso."
1803667,2019-10-11 04:00:05 UTC,"Hi Joshua,
    >   document here:"
1803667,2019-04-28 07:05:23 UTC,"It would the function as described in:
https://www.dell.com/support/article/us/en/19/sln310803/unattended-auto-installation-of-sles12-using-lc?lang=en"
1803667,2019-10-10 22:09:56 UTC,Please see the following thread:
1803667,2019-10-11 13:39:06 UTC,"> Will it be implemented in ubuntu live server or ubuntu server or both ?
> Does the ubuntu desktop will support this feature ?
"
1803667,2020-03-30 06:01:56 UTC,new issue for auto install: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1869291
1803667,2020-04-22 20:49:59 UTC,Does this provide enough of an automated process for the requirements? https://discourse.ubuntu.com/t/please-test-autoinstalls-for-20-04
1803667,2020-06-06 01:44:38 UTC,This new feature for autoinstall is fixed. We can mark this PR as resolved.  Thanks.
1803667,2019-02-20 02:55:35 UTC,"change the issue's status since it expires due to no response for a long time.
Thanks."
1803686,2019-01-30 07:26:07 UTC,"The Failure is different this cycle:
 FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
 ---
 sent invalidate(passwd) request, exiting
 sent invalidate(group) request, exiting
 /usr/sbin/deluser: The user `lxcunpriv' does not exist.
 sent invalidate(passwd) request, exiting
 sent invalidate(group) request, exiting
 sent invalidate(passwd) request, exiting
 sent invalidate(group) request, exiting
 sent invalidate(passwd) request, exiting
 sent invalidate(group) request, exiting
 sent invalidate(passwd) request, exiting
 sent invalidate(group) request, exiting
 Failed to open connection to ""unix:path=/sys/fs/cgroup/cgmanager/sock"" message bus: Failed to connect to socket /sys/fs/cgroup/cgmanager/sock: Connection refused
 c2 is not running
 c1 is not running
 ---"
1803686,2018-11-16 10:15:55 UTC,Can be reproduced with 4.15.0-1030-azure #31~14.04.1-Ubuntu as well
1803687,2018-11-16 21:10:03 UTC,With gtk-common-themes revision 818 I only get one line output at startup:
1803687,2018-11-16 10:25:18 UTC,Reported in the best upstream location I could find: https://gitlab.gnome.org/Community/Ubuntu/gtk-common-themes/issues/4
1803687,2018-11-16 10:23:19 UTC,"This is actually a bug in gtk-common-themes snap, the $SNAP/share/sounds directory is missing but the content interface refers to two directories inside."
1803687,2018-11-16 09:52:08 UTC,"Reproduced, I suspect this is a fallout from fixing https://bugs.launchpad.net/snapd/+bug/1803535"
1803689,2018-12-10 18:00:04 UTC,Any chance 2.4.37-1 from buster/sid will be availible in devel/disco soon?
1803689,2018-11-20 19:33:48 UTC,Do you have logs of this failure? I wonder if https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1802630 is the same issue
1803689,2018-11-20 19:57:04 UTC,Just pulling up some commits:
1803689,2018-11-20 21:23:44 UTC,"When setting LogLevel to debug, I get something:"
1803689,2018-12-12 14:03:34 UTC,"Apache will be updated soon in disco. As for this specific bug, I need to setup a test scenario."
1803689,2019-02-06 18:23:52 UTC,The timeout does not occur with 2.4.38-2ubuntu1
1803689,2019-02-11 15:49:25 UTC,"So disco is good; but I guess cosmic is still affected, and bionic will be affected soon with the arrival of OpenSSL 1.1.1 there."
1803689,2019-06-18 15:53:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803689,2019-06-28 14:40:16 UTC,"Discussion is happening in bug #1833039, so I'm marking this as a duplicate of that one."
1803691,2019-01-27 19:03:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803692,2018-11-16 11:24:19 UTC,apport information
1803692,2018-11-16 11:17:57 UTC,apport information
1803692,2018-11-16 11:17:56 UTC,apport information
1803692,2018-11-16 11:17:55 UTC,apport information
1803692,2018-11-16 11:17:54 UTC,apport information
1803692,2018-11-16 11:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803692,2018-11-16 11:17:52 UTC,apport information
1803692,2018-11-16 11:17:51 UTC,apport information
1803692,2018-11-16 11:17:51 UTC,apport information
1803692,2018-11-16 11:17:58 UTC,apport information
1803692,2018-11-16 11:17:53 UTC,apport information
1803692,2018-11-16 11:24:18 UTC,apport information
1803692,2018-11-16 11:17:53 UTC,apport information
1803692,2019-09-26 16:05:45 UTC,A fix for those who has this issue with Intel SSD / NVMe drives:
1803692,2018-11-16 19:49:24 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1803692,2018-11-16 11:24:30 UTC,apport information
1803692,2018-11-16 11:24:29 UTC,apport information
1803692,2018-11-16 11:24:28 UTC,apport information
1803692,2019-05-17 09:53:17 UTC,The fix is available in the at least the 4.18 branch: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/log/drivers/nvme/host?h=Ubuntu-hwe-4.18.0-21.22_18.04.1
1803692,2018-11-16 11:24:27 UTC,apport information
1803692,2018-11-16 11:24:26 UTC,apport information
1803692,2018-11-16 11:24:25 UTC,apport information
1803692,2018-11-16 11:24:24 UTC,apport information
1803692,2018-11-16 11:24:23 UTC,apport information
1803692,2018-11-16 11:24:22 UTC,apport information
1803692,2018-11-16 11:24:20 UTC,apport information
1803692,2018-11-23 16:46:27 UTC,I have changed the bug to 'invalid' as I do not expect a fix in Ubuntu for the firmware bug.
1803692,2018-11-26 13:12:44 UTC,I tried to force install the Intel firmware which contains the fix but that did not work as the utility refused to overwrite the custom Lenovo firmware.  I opened a support case with Lenovo referencing the Intel fix but the case was closed with 'we don't support Linux' :(  Perhaps it would be possible to have a quirk for the faulty firmware...
1803692,2018-11-30 11:51:43 UTC,A workaround in the kernel nvme driver has been tested and proposed: http://lists.infradead.org/pipermail/linux-nvme/2018-November/021366.html
1803692,2019-01-16 11:19:00 UTC,The fix has been merged to the mainline kernel tree as commit 6299358d198a0635da2dd3c4b3ec37789e811e44.
1803692,2018-11-19 10:49:44 UTC,The issue exists upstream:
1803692,2018-11-23 15:55:20 UTC,The linked thread on fedoraproject.org indicates that a firmware update for the device will be necessary to resolve this issue.
1803696,2018-11-16 12:35:57 UTC,"Description:
(initially reported in Ubuntu: https://launchpad.net/bugs/1803696)"
1803696,2018-11-16 12:36:54 UTC,I reported the bug upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=121461.
1803696,2020-12-18 03:50:44 UTC,"Dear Olivier Tilloy,"
1803696,2018-12-19 16:08:01 UTC,As a workaround I installed libreoffice-gtk3 as per https://askubuntu.com/questions/285089
1803696,2018-12-18 15:51:34 UTC,Reproduced in
1803696,2018-11-16 12:24:25 UTC,"Confirmed, the outline around the icon is almost invisible, making it really hard to tell whether the option is checked."
1803700,2018-11-26 10:48:01 UTC,"The duplication is an interesting nuance of having to support older clouds which are v2 based, and their upgrade to keystone v3."
1803700,2018-11-30 12:18:13 UTC,I've added the suggested code to both scripts and commited to https://github.com/openstack-charmers/openstack-bundles/tree/fix-1803700 branch
1803706,2019-08-27 08:44:02 UTC,"Certainly in 19.04 (I do not remember when it begun: 18.10?), at some moment appeared a much larger line spacing, pushing the OK button or the Quit button out of the screen.
In LibreOffice Calc, I can choose formatting, but not get it actually: OK button out of reach.
In Nextcloud (dialog from notification area), I can not quit — I have to kill the application.
This was not the case in the past, with as much fonts (in LibreOffice), with as much folders to sync in Nextcloud."
1803706,2019-08-27 08:47:57 UTC,"Screen capture with Nextcloud.
I am not a professional. To me it seems reasonable to think GTK is the culprit but others may know better."
1803706,2018-11-17 13:27:23 UTC,Problem happens when your screen is to small to contain the menu or the window of the application is  positioned too low in the screen
1803706,2018-11-18 07:57:18 UTC,"Problem does not depend on yaru, it happens also in Ubuntu 18.04 Bionic. I suggest you change the bug title."
1803706,2018-11-18 11:34:39 UTC,"Bug title changed, should package be changed too? Unfortunately that is above my level of knowledge."
1803706,2018-11-18 13:01:01 UTC,On Bionic the problem happens also with ambiance theme
1803706,2018-11-18 16:30:45 UTC,I think the problem should be accounted to libreoffice and not to yaru because other applications (see GIMP) does not have the same problem
1803706,2018-11-18 17:34:43 UTC,"I agree, that other apps okay, however with submenus they running edge to edge. Is that intended behaviour?  see picture attached and previous picture with cherry tree (no 3.)
Too be frank that is not as bad as the other issue with libreoffice, whether it is intended or not."
1803706,2018-11-18 18:14:44 UTC,"Description:
Hi I am not a developer, only a user."
1803706,2018-11-18 18:19:51 UTC,"Created attachment 146723
This is from launchpad"
1803706,2018-11-18 18:25:35 UTC,Reported to LibreOffice on Bugzilla.
1803706,2018-11-19 09:25:38 UTC,"> Reported to LibreOffice on Bugzilla.
"
1803706,2018-11-19 09:35:41 UTC,"LibreOffice does make menus scrollable like Gimp does when their contents are too tall, however the y coordinate of the menu is offset, hiding the menu bar."
1803706,2018-11-19 09:47:08 UTC,"installed inxi, here is the output.
For the link to bugzilla, olivier has already copied it above. Bug 121495
I have 1366x768 display, 15 inch screen, hp laptop elitbook 8560p."
1803706,2018-11-19 09:52:00 UTC,I can confirm shotwell does it too on my laptop.
1803706,2018-11-19 10:06:08 UTC,"Terminal menu does an interesting thing too when it is resized to small window and pulled down to the edge of screen therefore restricting space underneath for menu.
when it is in the middle of the screen then menu opens normally but runs out of app window, I guess that is normal, though."
1803706,2018-11-21 11:49:48 UTC,"This behavior is from GTK+ (so NOTOURBUG), but good luck trying to convince GNOME it’s a bug; they’re notoriously stubborn."
1803706,2019-08-27 08:27:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803706,2019-08-27 08:45:54 UTC,Screen capture with a LibreOffice Calc dialog.
1803706,2018-11-19 09:00:19 UTC,"I'm unable to reproduce your problem also on my laptop with 1366x768 screen.
please post here the output from the command 'inxi -Fx' if you does not have inxi you may install it 'sudo apt install inxi'
please post also the link to your bug in bugzilla."
1803706,2018-11-18 18:17:16 UTC,"Created attachment 146722
LibreOffice overflowing menu in Yaru"
1803708,2018-11-16 19:38:48 UTC,"On Fri, Nov 16, 2018 at 01:24:00PM -0000, Evan wrote:

> Some users will install multipass and mistakenly run snapcraft inside of
> it, thinking that's why multipass was installed as a snapcraft
> dependency.
"
1803717,2019-04-23 14:09:50 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/655167"
1803717,2019-04-23 15:13:07 UTC,https://review.opendev.org/#/q/I3ed3303309fe2a25c0043fd206f36bada4b3b8f9 was also backported to stable/queens and the ceph job is failing there as well.
1803717,2019-07-10 21:40:05 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1803717,2019-06-18 03:41:12 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1803717,2019-04-25 12:05:55 UTC,"Reviewed:  https://review.opendev.org/655186
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d4dbbb645af4b4a8220cd3496cfb615f8904ec91
Submitter: Zuul
Branch:    stable/queens"
1803717,2019-04-25 03:08:58 UTC,"Reviewed:  https://review.opendev.org/655167
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=585e62e24481ce3e8c1d02a4d0b6f99b4f9df8c0
Submitter: Zuul
Branch:    stable/rocky"
1803717,2019-04-23 15:28:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/655186"
1803717,2019-04-23 15:11:42 UTC,"> With the merge of https://review.opendev.org/#/c/650064/ this bug was introduced on the Rocky stable branch two weeks ago.
"
1803717,2019-04-23 14:11:55 UTC,At the moment the snapshot feature is broken again on the Rocky stable branch.
1803717,2018-11-19 04:34:07 UTC,"Reviewed:  https://review.openstack.org/618534
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fd540e2135c26d8c297695a3fa73d993655f0ad8
Submitter: Zuul
Branch:    master"
1803717,2018-11-16 15:44:10 UTC,My patch broke all existing RBD deployments. I think that warrants a Critical priority :)
1803717,2018-11-16 15:05:02 UTC,based on our irc conversation and the docs you found i think the propsed patch is correct.
1803717,2018-11-16 14:54:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/618534"
1803717,2018-11-16 14:51:42 UTC,i was debating if this should be a high or medium. i was going to mark as medium but since people are already working on it ill set it to high.
1803717,2018-11-16 14:35:24 UTC,Seems this is a regression caused by https://review.openstack.org/614351
1803717,2019-03-22 03:46:01 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1803726,2018-11-16 18:58:10 UTC,Evergreen 3.1.6
1803726,2021-02-18 22:29:36 UTC,Looks like this is still an issue in 3.6.
1803726,2018-11-16 19:18:03 UTC,Fixing a typo in my description:
1803727,2018-11-16 17:04:47 UTC,"The solution is probably to remove this code. It says ""older versions of SBCL"" and dates from 2013, and was never enabled by default due to controversy (though it or equivalent code was used at ITA)."
1803727,2018-11-16 18:54:43 UTC,(A more conservative solution is to check whether the format control is a string before you go further.
1803729,2018-11-16 15:40:04 UTC,"Fix:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/blake/LP1803729_action_trigger_aggregator.pl_help_indicates_the_wrong_bash_argument_for_remote-acct"
1803729,2019-03-01 18:43:17 UTC,"Signoff branch at:
user/stompro/LP1803729_action_trigger_aggregator.pl_help_indicates_the_wrong_bash_argument_for_remote-acct_signoff"
1803729,2019-05-07 14:58:39 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Blake and Josh!"
1803733,2019-04-27 20:24:58 UTC,Can I get a log and/or more info?
1803735,2018-11-26 16:20:27 UTC,"The verification of the Stable Release Update for sosreport has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1803735,2018-11-20 13:15:49 UTC,"Hello Eric, or anyone else affected,"
1803735,2018-11-20 13:22:49 UTC,"Hello Eric, or anyone else affected,"
1803735,2018-11-22 02:32:06 UTC,[VERIFICATION COSMIC]
1803735,2018-11-20 13:26:38 UTC,"Hello Eric, or anyone else affected,"
1803735,2018-11-16 16:22:58 UTC,Uploaded in C/B/X
1803735,2018-11-22 02:28:23 UTC,[VERIFICATION BIONIC]
1803735,2018-11-22 02:34:21 UTC,[VERIFICATION XENIAL]
1803735,2018-11-26 16:20:41 UTC,This bug was fixed in the package sosreport - 3.6-1ubuntu0.18.04.2
1803735,2018-11-26 16:20:52 UTC,This bug was fixed in the package sosreport - 3.6-1ubuntu0.16.04.2
1803735,2018-11-26 16:30:28 UTC,This bug was fixed in the package sosreport - 3.6-1ubuntu0.18.10.2
1803740,2018-11-19 09:36:06 UTC,"The issue is procuded by the following commit https://review.openstack.org/#/c/606948/, it removes mixed_upgrade flag, this is the flag used to differenciate overcloud upgrade."
1803745,2018-11-23 07:51:51 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/619473
Reason: Should be really fixed by https://review.openstack.org/#/c/619652/"
1803745,2018-11-22 22:51:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619652"
1803745,2018-11-22 08:43:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619473"
1803745,2018-11-29 15:33:27 UTC,"Change abandoned by Hongbin Lu (<email address hidden>) on branch: master
Review: https://review.openstack.org/619652"
1803745,2018-11-20 14:16:20 UTC,http://logs.openstack.org/63/617763/1/check/openstack-tox-py27/6c0a1a9/testr_results.html.gz
1803745,2018-11-22 08:39:33 UTC,It looks from git bisect that culprit is 4ba87b06d74940d84b75488e1c28b435f2f1b3c2: https://review.openstack.org/#/c/611462/
1803745,2018-11-27 14:27:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620326"
1803745,2018-11-30 09:09:49 UTC,"Reviewed:  https://review.openstack.org/620334
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=7f82a19155abfb88f6f1d463ac90de3198ad67c9
Submitter: Zuul
Branch:    master"
1803745,2018-12-05 10:38:59 UTC,"Reviewed:  https://review.openstack.org/620326
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=7d3bb6862eb3f8e9dc0ee62be27845c9920a05a6
Submitter: Zuul
Branch:    master"
1803745,2020-03-04 15:23:57 UTC,Updating status on old gate-failure bug
1803745,2018-11-16 16:42:15 UTC,Skipping unit tests around rescheduling for now in Ubuntu packaging.
1803745,2018-11-27 14:40:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620334"
1803767,2019-08-20 22:10:59 UTC,The added clarity in the charm config documentation is quite helpful and appreciated (merged 8mo. ago).
1803768,2020-07-30 19:49:58 UTC,Based on Michele's and Mike's comments I'm marking this a duplicate of bug 1508208
1803768,2020-04-08 14:36:00 UTC,"FWIW, I've updated my branch proposing to fix bug 1508208, and I agree with Michele that it would address both that one and this -- I think they're the same bug."
1803768,2019-05-20 18:10:21 UTC,I have had many reports of delayed checkin of items with long list of holds. The process of seeing if the item is on hold takes longer than it should.  This causes problems when staff are checking in a stack of items. They continue scanning and don't realize the system is still working on the item with a hold. I know they should watch the screen to be sure the process has finished but they don't. We have categorized this as staff training for the most part but if the timing could be faster it would be wonderful. Confirming this behavior.
1803768,2018-11-16 22:24:54 UTC,related:
1803768,2019-04-02 16:33:47 UTC,"Description edited to remove the part about non-holdable items. Turns out that if targeting is up to date, non-holdable items will not exhibit the checkin delay because there will be no entries for the item in the hold_copy_map."
1803768,2018-11-16 21:32:16 UTC,One simple way to pre-filter would be to hook into the best hold selection sort.
1803768,2018-11-17 05:32:17 UTC,"I see why this is a hard problem.  The age hold protection determination depends on the hold matrix matchpoint to know if the owning lib or the circ lib is used to pull the active date use setting and to choose where to measure the distance from.  Maybe we could just look at all the variations and include the hold if any of them are true?  There would still be a chance that holds would be included that will fail the hold permit test later, but I cannot picture a situation where the owning lib and circ lib would be different where they would be in different age hold protection scopes."
1803769,2018-11-18 16:16:44 UTC,This seems like some changes have been made in the Python module index.py so it is not really an Inkscape extension issue but only a Python issue...
1803769,2020-03-29 09:50:23 UTC,Closing because INVALID: Can't replicate.
1803769,2018-11-16 22:21:06 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1803769,2018-11-18 16:17:45 UTC,s/index.py/inkex.py/
1803769,2018-11-18 15:58:02 UTC,"there have been some recent changes made in the Python support system, so that currently the Python extensions will typically generate unexpected errors or warnings, see:
https://gitlab.com/inkscape/extensions/issues/11"
1803769,2018-11-18 11:23:22 UTC,"What you mean by ""which is the last version ... python extensions work"" ?
Extensions can be written with other interpreters than Python..."
1803769,2018-11-17 10:40:25 UTC,"not reproduced on Windows 10, Inkscape 0.92+devel (b9177a8, 2018-09-07)"
1803769,2018-11-17 10:29:17 UTC,"reproduced on Windows 10, Inkscape 0.91 r13725 (Jan 30 2015)"
1803769,2018-11-16 23:53:47 UTC,"Not reproduced with Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1-64"
1803775,2019-08-16 08:01:22 UTC,"Since this failure was reported, we have made a lot changes in the area, including removing this test in favor of a more efficient one."
1803778,2019-05-02 03:29:13 UTC,"There have been a bit of renovations done in the destruction area since
this bug was filed and this failure was observed."
1803783,2020-04-19 08:57:54 UTC,"I propose these 2 patches mostly as a ""proof of concept"". They enable the user to cancel autologin by just clicking on the background. Surely it could be done much better, with, say, a button somewhere stating ""Cancel autologin"", but I'm not a coder. Anyway I do propose these patches to hopefully get some attention on this issue which makes lightdm-gtk-greeter mostly unusable in one of its main purposes (switching user) when autologin timeout is set to low values, like 5 seconds or so."
1803784,2018-11-16 22:23:24 UTC,"The problem was with Rosa. Grub reported it could not even find the folder /vmlinuz. I installed a minimal installation of Ubuntu 18.04 MATE on the partition (sda4) and everything works again. Don't know WHY Rosa caused this problem, I did not have it with OpenMandriva which is very near the same thing."
1803787,2019-06-13 21:35:34 UTC,"Thanks, Jane."
1803787,2019-05-09 01:35:16 UTC,"Thanks for the two branches, Bill!"
1803787,2019-05-31 16:01:36 UTC,Setting 3.2 target to WONTFIX since we're getting steadily further away from backport-ability.
1803787,2019-05-31 16:00:09 UTC,"Thanks, Jane."
1803787,2019-05-17 20:01:35 UTC,"Thanks for the refactor, Bill."
1803787,2019-05-09 16:17:27 UTC,"Also note the rebased code required quite a few changes, so the path to a 3.2 back-port is getting thornier."
1803787,2019-05-09 16:15:50 UTC,Force-pushed a master compat branch back to
1803787,2019-05-09 15:49:40 UTC,"Thanks for the i18n explanation, Bill.  That sounds excellent."
1803787,2019-05-09 14:06:30 UTC,"Thanks, Jane!"
1803787,2019-06-10 00:49:14 UTC,"Looks very good to me, Bill.  I pushed a small follow-up commit here, as well as sign offs to all your recent commits: user/sandbergja/lp1803787-ang-grid-context-menu-follow-up"
1803787,2019-03-06 20:44:26 UTC,Here's a 3.2-compatible branch:
1803787,2019-03-06 20:20:25 UTC,Thanks Bill!  I'm +1 for backporting if it's not too much of a hassle.
1803787,2019-03-06 19:40:36 UTC,"Note that after rebase, the working branch only merges cleanly to master / 3.3.  If we want to back-port, I can create a 3.2 compatible branch."
1803787,2019-03-06 19:38:58 UTC,Working branch rebased to master with merge repairs.  Added another commit to address the row selection issues raised by John.
1803787,2019-03-06 18:56:52 UTC,"Thanks, John.  I'll take a look at the multi-row issue."
1803787,2019-03-06 18:00:30 UTC,I took a quick look at this patch today.
1803787,2018-11-26 18:28:19 UTC,Patches pushed:
1803787,2019-03-06 20:35:51 UTC,"Thanks for the input, Andrea.  I'll push a 3.2 branch."
1803787,2019-06-17 21:53:00 UTC,"I added those missing signoffs, and pushed to master and rel_3_3.  Thanks so much for your work on this, Bill.  And thanks, Andrea, for the original report and John, for the testing."
1803788,2018-11-19 14:44:46 UTC,+1 for consistency to the end users if feasible
1803788,2019-03-27 13:06:26 UTC,"I agree with the sentiment, but I'd request that we standardize on the gear icon for grid configuration, rather than the down arrow.  I agree with using ""Actions"" for the actions menu."
1803790,2019-03-06 21:43:19 UTC,My patch here:
1803790,2018-11-18 15:33:36 UTC,Having these in English alphabetical order again would be great.  Even better would be if these were in alphabetical order for non-English translations as well.
1803790,2019-10-04 14:19:02 UTC,I've pushed this along with a follow-up to alphabetize the Angular server and local admin splash patches to master and rel_3_4. I've also backported the AngularJS versions to 3.3 and 3.2.
1803790,2019-03-06 23:12:21 UTC,A new wishlist bug would be great!
1803790,2019-03-06 23:45:49 UTC,Added new bug here: https://bugs.launchpad.net/evergreen/+bug/1818927
1803790,2019-05-24 19:18:44 UTC,"Galen: I ""stole"" this bug from you seconds after you assigned it to yourself.  I can't give it back to you, but you can reassert your ownership.  Sorry for the inconvenience."
1803790,2019-08-02 16:47:19 UTC,"Grabbed bug from Galen, but I really meant to grab bug #1818927."
1803790,2019-09-09 16:21:42 UTC,"I have tested this code and consent to signing off on it with my name, Jennifer Pringle and my email address, <email address hidden>."
1803794,2019-02-01 22:49:52 UTC,2.3 is not released yet.
1803795,2018-11-21 13:14:23 UTC,I forgot to mention one very important thing. In windows i have the asrock application F-Tune which does the fan control perfectly. Which leads me to conclude that all hardware support is in place.
1803795,2018-11-21 12:57:02 UTC,Thanks for filing this bug in Ubuntu.
1803795,2018-11-23 18:58:44 UTC,"Thanks for filing the upstream bug. That is the best place for this discussion. I'll mark this bug as ""confirmed"" in the meantime, but we will need a new upstream version or a patch from them to fix this in Ubuntu."
1803795,2018-11-21 13:19:59 UTC,The name of the utility is not f-tune but f-stream. I reported the bug here https://github.com/lm-sensors/lm-sensors/issues/144
1803802,2018-11-18 21:52:56 UTC,"It seems that you don't have in your TRAINSET folder the player locomotive needed for this activity, that is IR_EMD\KJM_WDP4.eng ."
1803805,2018-11-17 13:05:38 UTC,"Richard, as you didn't use 'apport' or 'ubuntu-bug' when creating this bug report I'm unsure if what you are reporting applies to me or not as your report doesn't include any version information."
1803805,2018-11-18 04:48:29 UTC,"I'm using Ubuntu 18.04. My issue is about installing GRUB, not about running update-grub or booting particular entries, so it sounds like your issue is something else."
1803805,2020-02-05 11:06:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803805,2020-02-05 11:38:35 UTC,"Thank you for reporting this, Richard!"
1803808,2018-11-01 11:04:25 UTC,"I get this warning normally (in addtion to the segfault):
void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action """" under id 195
void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action """" under id 196"
1803808,2018-10-31 09:46:51 UTC,"(In reply to Peter Wu from comment #2)

> Was this issue also present on Debian stretch/buster or other Ubuntu
> versions?
> Is this limited to the standard (Unity?) UI or is it also present on Kubuntu?
"
1803808,2018-10-31 09:08:59 UTC,"Was this issue also present on Debian stretch/buster or other Ubuntu versions?
Is this limited to the standard (Unity?) UI or is it also present on Kubuntu?"
1803808,2018-11-17 07:26:54 UTC,"The workaround I found was installing gtk2-engines-oxygen, with this package present the Qt interface does not crash."
1803808,2018-10-28 22:08:22 UTC,"Build Information:
TShark (Wireshark) 2.6.3 (Git v2.6.3 packaged as 2.6.3-1~ubuntu14.04.1)"
1803808,2019-09-11 08:39:31 UTC,According to the reproduction: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/1803808/comments/3
1803808,2018-10-28 22:11:13 UTC,Wireshark 2.6.3 has been rolled out as a security update on all supported Ubuntu versions which caused the sharp increase of the Qt GUI user base on all Ubuntu LTS releases.
1803808,2019-09-10 15:06:19 UTC,I have prepared packages proposed for -security at:
1803808,2019-07-03 10:52:46 UTC,*** Bug 15894 has been marked as a duplicate of this bug. ***
1803808,2019-07-18 22:59:29 UTC,This bug was fixed in the package wireshark - 2.6.10-1
1803808,2019-07-03 10:10:18 UTC,"As reported in https://bugs.launchpad.net/ubuntu/+bug/1803808, the issue cannot be reproduced on 3.0, but only 2.6. Bisection led up to:"
1803808,2019-07-03 10:09:28 UTC,"Oops, the commit reference for the master-2.6 branch was wrong, I meant to say:
* master-2.6 v2.6.8rc0-23-ga616bd2"
1803808,2019-07-02 23:08:41 UTC,Can reproduce the crash with a fully up-to-date Ubuntu 16.04.
1803808,2019-04-14 09:15:00 UTC,Is there a regression in 2.6.6-1~ubuntu16.04.0? I am seeing this error again.
1803808,2018-11-26 13:54:53 UTC,This bug was fixed in the package wireshark - 2.6.4-2~ubuntu14.04.1
1803808,2018-11-21 10:55:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803808,2019-07-03 10:28:17 UTC,"@lekensteyn Thanks! As a side note upgrade to 3.0 is not an option for many users yet since 3.0 is waiting for approval in Debian's NEW queue.
I'll be happy to include the fix in Wireshark's next security update though, thus users get this fixed automatically."
1803808,2018-11-20 09:51:21 UTC,The commit that Mikael refers to links to bug 14979.
1803808,2018-11-20 08:08:35 UTC,"Hi,"
1803808,2018-11-17 08:54:39 UTC,The bug seems to be in appmenu-qt rather than in Wireshark.
1803808,2018-11-17 08:51:53 UTC,"A possible other workaround that works on Xenial, too, is removing the appmenu-qt5 package until appmenu-qt5 is fixed."
1803808,2018-11-17 08:43:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803808,2018-11-17 07:57:02 UTC,The crash is observed only in the Unity session.
1803808,2018-11-17 07:36:22 UTC,This is also reported as an error many times: https://errors.ubuntu.com/problem/ac9b86e48c6b6b5792c1128a836ba63213d62b44
1803808,2018-11-20 08:22:16 UTC,"Hi,"
1803808,2019-07-03 10:29:49 UTC,"Change 33828 had a related patch set uploaded by Peter Wu:
Qt: fix QIcon crash on exit on Ubuntu 16.04 with Qt 5.5.1"
1803808,2019-07-03 10:33:48 UTC,Isn't bug 15894 a duplicate of this one?
1803808,2018-10-31 10:02:47 UTC,"(In reply to Balint Reczey from comment #3)

> (In reply to Peter Wu from comment #2)
> > Was this issue also present on Debian stretch/buster or other Ubuntu
> > versions?
> > Is this limited to the standard (Unity?) UI or is it also present on Kubuntu?
>
> I have not checked Debian, but I could not reproduce it with Trusty's KDE
> and Fluxbox thus it seems to be Unity-specific.
"
1803808,2019-07-03 15:19:37 UTC,"Change 33828 merged by Anders Broman:
Qt: fix QIcon crash on exit on Ubuntu 16.04 with Qt 5.5.1"
1803808,2019-07-07 13:43:32 UTC,@rbalint Should this bug be reopened until the fix actually gets merged?
1803808,2019-07-03 21:57:51 UTC,Fixed in v2.6.10rc0-40-g000cc11d8f
1803808,2019-09-10 14:27:19 UTC,Where is the update?
1803815,2018-11-20 09:56:08 UTC,I have reported the bug to Poppler project: https://gitlab.freedesktop.org/poppler/poppler/issues/673
1803815,2018-11-17 11:05:37 UTC,"Alright, it took many minutes but it eventually did load the PDF and now I can view it. So I guess this is more like performance issue that Firefox's PDF viewer can do better on this file than Evince."
1803815,2018-11-21 15:02:12 UTC,Thanks for reporting it upstream
1803816,2018-11-19 15:11:40 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1803816,2018-11-20 18:04:54 UTC,"Hello i'm tired of finding kernels under Ubuntu who have such problems and
you do not solve it. I am as well so tired of seeing you change the
destination folder where we install drivers for the scanner/printer and
Steam. So I decided to leave you for Debian 9.6. I hope for the other users
of Ubuntu and Mint that you will show more serious in the future in future
updates of your OS."
1803816,2018-11-20 18:06:16 UTC,Hello i'm tired of finding kernels under Ubuntu who have such problems and you do not solve it. I am as well so tired of seeing you change the destination folder where we install drivers for the scanner/printer and Steam. So I decided to leave you for Debian 9.6. I hope for the other users of Ubuntu and Mint that you will show more serious in the future in future updates of your OS.
1803816,2018-11-20 18:09:27 UTC,PS I am not a beta tester and I do not like when you create breakdowns (Stean divers of scanners/printers) because you do not think about what you do ...
1803816,2018-11-20 18:10:28 UTC,https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803818
1803816,2018-11-17 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803819,2018-11-20 05:53:12 UTC,I have not used KVM in a while. I am going to test it. Have you tried using VirtualBox instead of KVM?
1803819,2018-12-02 11:37:43 UTC,"Reviewed:  https://review.openstack.org/619924
Committed: https://git.openstack.org/cgit/openstack/training-labs/commit/?id=0761f7f85ab96e9f567555e9233ad67090a85259
Submitter: Zuul
Branch:    stable/queens"
1803819,2018-11-19 09:55:40 UTC,I've gived another try to the installation and it go through the previous blocking step I have no clue why it fail the first time.
1803819,2018-11-19 10:16:28 UTC,And with another try :
1803819,2018-11-19 17:45:58 UTC,I'm using Master
1803819,2018-11-20 12:15:17 UTC,"After switching to Virtualbox, controller node create fine but for compute node it fail there :"
1803819,2018-11-20 13:14:02 UTC,It looks like the compute node is not responding. Is it up and running? Did it fail to boot?
1803819,2018-11-19 16:03:28 UTC,"Did you get the code from https://docs.openstack.org/training_labs/? Is this Rocky, or Master?"
1803819,2018-11-20 13:24:08 UTC,Yes the in both case (Virtualbox or KVM) the nodes were responding and I was able to connect on it (From gui or ssh)
1803819,2018-11-20 14:35:22 UTC,"That is odd. The latest trace you posted shows that we are able to connect to the ssh server (""Connected to ssh server""), but then this ssh command returned 255 (which means an ssh error occured):"
1803819,2018-11-23 07:44:29 UTC,"I did some testing on master. With VirtualBox, the cluster build always succeeded (10 times out of 10). With KVM, it failed in config_public_network (5 out of 5). That is one of the errors you reported, and that is the bug that I am going to look into for now."
1803819,2018-11-25 09:50:18 UTC,"At least you find something. I'm going to try to find something more relevant with my problem.
Should I close this report ?"
1803819,2018-11-25 11:14:26 UTC,"Well,"
1803819,2018-11-26 10:48:08 UTC,Thank you very much for your update.
1803826,2018-11-17 13:30:04 UTC,This change was made by a bot.
1803827,2018-11-17 16:39:15 UTC,apport information
1803827,2018-11-17 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803827,2018-11-17 16:39:08 UTC,apport information
1803827,2018-11-17 16:39:09 UTC,apport information
1803827,2018-11-17 16:39:10 UTC,apport information
1803827,2018-11-17 16:39:11 UTC,apport information
1803827,2018-11-17 16:39:13 UTC,apport information
1803827,2018-11-17 16:39:17 UTC,apport information
1803827,2018-11-19 22:25:04 UTC,RE Joseph Salisbury:The links are for 64bit but i tried lubuntu 32bit 19.04 (Disco Dingo) Daily Builds and is still the same bug (displays same as my other device)
1803827,2018-11-18 17:14:42 UTC,"maybe but with other versions i didn't have this problem plus i have a
simular bug on different computer"
1803827,2018-11-19 15:27:26 UTC,Can you see if this issue also happens with the latest daily image?  It can be downloaded from:
1803827,2018-11-17 16:39:32 UTC,apport information
1803827,2018-11-17 16:39:30 UTC,apport information
1803827,2018-11-17 17:27:38 UTC,https://blog.linuxmint.com/?p=3597
1803827,2018-11-17 16:39:27 UTC,apport information
1803827,2018-11-17 16:39:28 UTC,apport information
1803827,2018-11-17 16:39:24 UTC,apport information
1803827,2018-11-17 16:39:23 UTC,apport information
1803827,2018-11-17 16:39:21 UTC,apport information
1803827,2018-11-17 16:39:19 UTC,apport information
1803827,2018-11-17 16:39:18 UTC,apport information
1803827,2018-11-17 16:39:26 UTC,apport information
1803827,2018-11-17 16:39:34 UTC,apport information
1803833,2018-11-28 03:35:23 UTC,"This should probably be some sort of Git-specific hook. ""update_refs_hook""?"
1803836,2021-01-06 14:01:39 UTC,That's great to hear. You may want to do an official release (to e.g. pypi) and send announcement to the bazaar and breezy lists.
1803836,2021-01-06 12:00:26 UTC,Have converted to PyQt5 as of now.
1803836,2020-08-13 08:39:28 UTC,Thank you - I shall have a look at it.
1803836,2020-08-13 00:00:45 UTC,I was looking into this and think this could be helpful: https://github.com/spyder-ide/qtpy
1803838,2018-11-18 02:57:06 UTC,There's also the new Mailman PPA:
1803838,2019-05-21 19:09:19 UTC,"Hello, we're currently tracking two CVEs in mailman:"
1803838,2019-05-20 14:28:45 UTC,"Great Paride, thanks. Let's see how it evolves and hopefully it gets an upgrade knowing the existing security issues to be applied and taking in consideration the LTS status of 16.04"
1803838,2019-05-20 08:57:45 UTC,"I reverted the bug status to what is was until 2019-05-17, I think the changes were not wanted. Please note that the bug was not assigned to anybody even before. The latest valid update to this bug is message #8 from Robie Basak."
1803838,2019-05-17 18:02:05 UTC,May I know why this was moved to Status incomplete e assigned to nobody ?
1803838,2018-11-23 23:07:27 UTC,"> given that the most appropriate is a version upgrade
"
1803838,2018-11-23 20:34:51 UTC,"Yeah, given that the most appropriate is a version upgrade, but I find a bit strange have to report a individual issue in order for that to happen as there are known pending security fixes. Perhaps it just speeds up things if I understand correctly."
1803838,2018-11-23 19:11:06 UTC,Current state of mailman in the Security Team's CVE tracker:
1803838,2018-11-19 04:10:04 UTC,"Hello Hans.
Thanks for the update."
1803838,2018-11-18 08:59:42 UTC,Thanks for reporting.
1803838,2018-11-18 00:50:26 UTC,"If you want to upgrade the Ubuntu 16.04 package from source, see https://wiki.list.org/x/17891606."
1803838,2018-11-23 19:12:26 UTC,"A ""blanket"" bug like this, requesting a big upgrade, is unlikely to be resolved. I think it's best to highlight a specific issue in a specific bug report, even if you end up with multiple reports. Then someone working on it can decide whether it's best to backport a fix, or upgrade the version. Usually the former is better, specially considering xenial is an LTS release."
1803840,2018-11-19 22:26:37 UTC,Hello Daniel and Team
1803840,2018-11-20 02:24:19 UTC,Thanks! Your feedback sounds like the missing piece to this puzzle. Until now the greenish problem had only been reported by people who didn't have a colorimeter so we just blamed the default profiles. However your comments now make me think it might have been a miscalculation in colord (or such) that is exaggerating the green channel most visibly.
1803840,2018-11-19 03:23:26 UTC,A greenish hue has been reported by other users in the past. It is caused by using an incorrect colour profile for the display. Please try removing all active colour profiles and tell us if that solves the problem.
1803842,2018-12-02 16:11:59 UTC,"Thanks for the confirmation. My followup on ""not installed"" was really a comment regarding the bug reporting system which had tagged ""(not installed)"" on the package name even though it was in fact installed.
I agree it does seem to be a package issue. However, Ubuntu is distributing the Skrooge package, and so an end user like myself should be able to just install it and go. I don't really understand the packaging system or skrooge well enough to sort this out myself."
1803842,2018-12-02 13:57:35 UTC,"Jim issue is not about installed, not installed, but about successful installation. Skrooge is installed, but can not be lunched. Below please find runtime messages with CRITICAL and FATAL errors. Take a look inside package and try to resolve this."
1803842,2018-11-18 00:47:09 UTC,Note that skrooge most definitely IS installed - no idea why the system summary tacked on says it isn't. There are no custom packages on this system; everything is either from the core system or added using software-manager.
1803847,2019-02-05 08:19:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803848,2018-11-27 21:05:44 UTC,"I have removed the nvidia drivers, it was automatically installed somehow even if i have amd, and intel graphics card:"
1803848,2018-11-28 02:33:16 UTC,"Wherever you can, please separate each issue into a new bug."
1803848,2018-11-28 02:22:08 UTC,"Sorry, just one thing more. If you look at my description, that it's a complex problem, and what the chromium bug says is not completely right."
1803848,2018-11-28 01:33:51 UTC,You don't need to keep commenting here. We have already established that this bug is about:
1803848,2018-11-27 21:47:48 UTC,"10) Called ""net usershare info "" but it failed: Failed to execute child process “net”"
1803848,2018-11-27 21:23:43 UTC,nvidia does not appear in the log at least:
1803848,2018-11-27 21:06:20 UTC,I have removed ureadhead service also
1803848,2018-11-27 20:12:52 UTC,"Nov 27 20:17:57 raxim-SATELLITE-L50-B systemd-udevd[1380]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1.
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.582066] nvidia-nvlink: Nvlink Core is being initialized, major device number 237
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.582294] NVRM: No NVIDIA graphics adapter found!
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.582371] nvidia-nvlink: Unregistered the Nvlink Core, major device number 237
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.642079] nvidia-nvlink: Nvlink Core is being initialized, major device number 237
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.642304] NVRM: No NVIDIA graphics adapter found!
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.642383] nvidia-nvlink: Unregistered the Nvlink Core, major device number 237
Nov 27 20:17:57 raxim-SATELLITE-L50-B systemd-udevd[1380]: Process '/usr/bin/nvidia-smi' failed with exit code 9.
Nov 27 20:17:57 raxim-SATELLITE-L50-B systemd[1]: nvidia-persistenced.service: Start request repeated too quickly.
Nov 27 20:17:57 raxim-SATELLITE-L50-B systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
Nov 27 20:17:57 raxim-SATELLITE-L50-B systemd[1]: Failed to start NVIDIA Persistence Daemon.
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.746077] nvidia-nvlink: Nvlink Core is being initialized, major device number 237
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.746324] NVRM: No NVIDIA graphics adapter found!
Nov 27 20:17:57 raxim-SATELLITE-L50-B kernel: [   40.746402] nvidia-nvlink: Unregistered the Nvlink Core, major device number 237"
1803848,2018-11-22 02:56:53 UTC,apport information
1803848,2018-11-27 19:56:10 UTC,"Sometimes the CPU is on a too high level, that it's crashing the whole ubuntu, and when I'm restarting, half of the screen contains lines, so I need to restart again."
1803848,2018-11-21 14:23:41 UTC,done
1803848,2018-11-22 01:25:16 UTC,The Bug Description sounds more like a Chrome issue than gnome-shell. Can you explain why you think this is a gnome-shell problem? Which process(es) use high CPU and when?
1803848,2018-11-22 02:56:51 UTC,apport information
1803848,2018-11-22 02:56:52 UTC,apport information
1803848,2018-11-22 02:56:55 UTC,apport information
1803848,2018-11-22 03:00:35 UTC,"Ok, i have tracked down the issue, for later reference, you can read it:
https://www.linuxuprising.com/2018/08/how-to-enable-hardware-accelerated.html
https://askubuntu.com/questions/1066105/how-to-install-amd-graphic-drivers-on-ubuntu-18-04"
1803848,2018-11-22 03:03:33 UTC,apport information
1803848,2018-11-22 03:03:35 UTC,apport information
1803848,2018-11-19 03:27:26 UTC,Please reword this bug so that it is about ONE issue only. You can open new bugs for other issues.
1803848,2018-11-22 03:03:36 UTC,apport information
1803848,2018-11-22 03:11:06 UTC,"At the last apport, i made the playback on both chrome, if it does help."
1803848,2018-11-22 03:12:04 UTC,Pls. remember there is a thread on https://bugs.chromium.org/p/chromium/issues/detail?id=906861 also.
1803848,2018-11-22 03:15:51 UTC,"Thanks. We are unable to track Chrome bugs on Launchpad, but can track bugs in the related 'chromium-browser' project. So reassigning there."
1803848,2018-11-22 03:19:00 UTC,"The bug is also reported upstream:
https://bugs.chromium.org/p/chromium/issues/detail?id=463440"
1803848,2018-11-22 03:20:32 UTC,Sorry VPN was DNS throttling.
1803848,2018-11-26 21:56:33 UTC,"Paco, with this last comment do you mean that after solving this DNS throttling issue the problem with video playback is seemingly resolved?"
1803848,2018-11-26 22:32:06 UTC,"I can't really test dns throttling, so the answer is no."
1803848,2018-11-27 20:08:18 UTC,"syslog is showing that in a never ending circle - No NVIDIA gra
phics adapter found!"
1803848,2018-11-22 03:03:37 UTC,apport information
1803848,2018-11-18 01:41:13 UTC,"Not just youtube, i'm using different web based players also"
1803848,2018-11-26 22:34:04 UTC,xperia phone = in context with usb tethering (so every test made on the ubuntu laptop - with and without usb tethering)
1803848,2018-11-26 22:55:58 UTC,at flickering - cpu was on 20-30%.
1803848,2018-11-26 22:49:32 UTC,"WIFI is unusable when I'm connecting with ubuntu directly. When I'm connecting with my phone and using the usb tethering is much more stable. Unfortunately, even if I set Xperia always on, it seems at some point it's disconnecting, even if the stream is trying to load the next batch."
1803848,2018-11-26 22:37:53 UTC,"When I'm restarting it (Grammarly bug - not with it :)), system-ud does not appear on the top 30 processes."
1803848,2018-11-26 22:36:41 UTC,"system-ud cpu hog and flickering issues are unrelated, as when i restarted the system-ud, and it did disappear from the top 20 process, flickering issues didn't disappear, just less frequently happened, if I restarted the chrome browser. (unfortunately my chrome browser is the first program, what i tend to open and does not stop, even if i work 14 hours a day)"
1803848,2018-11-26 22:57:31 UTC,"with GPU flickering hasn't been solved. The HD5500 using a different set of code in Ubuntu, so either with mesa or without it, the problem persists, and it's not just video playback, it's scrolling also. (with similar frequency)"
1803848,2018-11-26 23:02:43 UTC,"I have identified at power management at least 5 critical bug in the last 3 years which hasn't been solved. For example one year before my battery lifetime showed 4 hours, now just 2 hours. 2 years before 2 hours. So in the middle of the time frame something has been fixed and after that the fix has been reverted."
1803848,2018-11-26 22:52:19 UTC,"disabled all the power management option anyway being displayed on the gnome panel, so something still exists in the background"
1803850,2018-11-18 04:01:56 UTC,おそらくこれと関連する問題だと思います。
1803850,2018-11-18 12:24:00 UTC,"コメントありがとうございます。
いったん 18.10までアップグレードしましたが、症状は治りませんでした。"
1803850,2018-12-15 08:54:59 UTC,"その後、18.10やドライバの更新等行ってみましたが依然変わらずハングアップは発生します。
いったん刺さっているWifiカードを旧式のものに差し替えてインストールしなおして試してみます。"
1803851,2020-08-04 16:11:32 UTC,"1. What is the operating system you are using? Windows, Linux, MacOS?
2. What is operating system version?
3. What is your Pinta version from Help | About."
1803853,2020-07-26 10:30:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803855,2018-11-18 08:37:17 UTC,"Workaround for those who find here by search:
* remove `openjdk-11-jre-headless` and `gradle` package from repo and install `gradle` via PPA: https://launchpad.net/~cwchien/+archive/ubuntu/gradle which works with openjdk-8"
1803855,2019-03-16 01:25:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803855,2019-03-16 10:23:58 UTC,"Now that Gradle 4.4.1 is coming to Ubuntu 18.04 LTS, this bug is getting much more relevant as it isn't fixed yet."
1803855,2019-03-16 11:33:21 UTC,"The problem with the PPA mentioned in #2 is that it contains prebuilt jar files which we cannot ship in the main or universe components (has to be built from source). So yes, an updated gradle built from source would be appreciated."
1803855,2019-03-17 10:48:44 UTC,I investigated into upstream bugtrackers and apparently it's a Groovy issue:
1803856,2019-10-27 22:14:37 UTC,Any update on this? I'm affected by the same (or very similar) problem with Samsung Galaxy S7:
1803860,2019-09-10 23:36:25 UTC,Closing in favor of https://gitlab.com/inkscape/lib2geom/issues/4
1803863,2018-11-18 19:12:11 UTC,apport information
1803863,2018-11-18 19:12:13 UTC,apport information
1803863,2018-11-18 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803863,2018-11-18 19:12:16 UTC,apport information
1803863,2019-03-19 09:48:08 UTC,Is this fixed in latest Ubuntu kernel?
1803863,2018-11-19 17:11:44 UTC,I tested the latest upstream kernel v4.20-rc3. 'kernel-fixed-upstream'
1803863,2018-11-19 16:53:24 UTC,"Yes, jsalisbury. I've noticed that kernel versions 4.15.0-20, 4.15.0-22 and 4.15.0-23 don't have this problem, but every other one in the 4.15 kernel series does."
1803863,2018-11-19 15:24:42 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1803863,2018-11-18 19:12:38 UTC,apport information
1803863,2018-11-18 19:12:30 UTC,apport information
1803863,2018-11-18 19:12:28 UTC,apport information
1803863,2018-11-18 19:12:33 UTC,apport information
1803863,2018-11-18 19:12:25 UTC,apport information
1803863,2018-11-18 19:12:24 UTC,apport information
1803863,2018-11-18 19:12:22 UTC,apport information
1803863,2018-11-18 19:12:21 UTC,apport information
1803863,2018-11-18 19:12:20 UTC,apport information
1803863,2018-11-18 19:12:27 UTC,apport information
1803863,2018-11-18 19:12:18 UTC,apport information
1803865,2018-11-19 15:55:26 UTC,"Although this improves UX for the use case where you'd search for a certain artist or title in multiple crates, it may be regression for other use cases. Example:
* Tracks > filtered with 'bpm:=155-165' (footwork/juke)
* going to _vocal crate to throw in some samples or lay a story on top of an instrumental
 > have to clear search phrase to see all tracks
* back to Tracks > have to re-enter search prase to get my footwork tracks back into view"
1803866,2018-11-20 15:10:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803875,2018-11-19 18:08:56 UTC,"Typically you'd have two systems, A and B. Say you want to install ubuntu-core on B. So you create a ssh key pair on A (if you don't have one already), and associate the public key of your user account on A with your online account. You then tell the installer on B about your online account, and then you can ssh in from A without using the private key that corresponds to the public key."
1803875,2018-11-19 18:09:44 UTC,"er, ignore the ""without"" there, it was a mis-edit."
1803875,2018-11-19 19:29:12 UTC,"Well, what I initially wanted to have is a System that directly boots into firefox that shows the web frontend of my music management so that I have it on a big screen in my living room."
1803881,2018-11-19 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803881,2018-11-19 15:22:46 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1803881,2018-11-19 16:21:46 UTC,This issue happens with the stock 4.15 kernel. I have upgraded the kernel to 4.18 and 4.19 and was getting the same issue. I managed to get rid off the error now. It seems it does not like intel_pstate. I added intel_pstate=disable to grub and the error has gone away.
1803881,2018-11-19 16:23:53 UTC,I also want to add that my pc is the newest Intel NUC8i5BEH. I will try the latest kernel and will report back.
1803881,2019-01-19 00:41:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803881,2019-01-19 00:45:05 UTC,i am also seeing this.  In my case:
1803881,2019-01-19 16:28:16 UTC,"These are kernel bugs, so better to file in kernel bugzilla."
1803881,2019-07-08 18:51:08 UTC,"Still fails:
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu Eoan Ermine (development branch)
Release:	19.10
Codename:	eoan"
1803881,2020-12-10 22:14:17 UTC,"Still fails
uname -a
Linux ice-ubuntu 5.8.0-32-generic #34-Ubuntu SMP Fri Nov 27 15:10:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux"
1803883,2018-11-20 11:54:42 UTC,"Hi Lieven,"
1803883,2018-11-23 21:52:11 UTC,"Well, actually I installed the bionic version on cosmic, so I downgraded sysstat from version 12 to version 11."
1803883,2018-11-23 21:35:01 UTC,Hi Karl
1803884,2018-12-06 22:23:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803885,2019-03-31 18:59:42 UTC,"For future reference (probably my own), if anyone else has this issue."
1803885,2019-03-31 18:01:33 UTC,Anybody got a solution for this?
1803891,2019-01-15 13:53:03 UTC,"I got the same as above, except I'm coming from 16.04.5."
1803891,2018-12-04 03:25:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803895,2018-11-18 18:45:52 UTC,"I will add a
Settings.WheelNatural"
1803897,2020-06-30 04:24:06 UTC,python3.6-minimal 3.6.6-3~18.04.york0 [origin: LP-PPA-jonathonf-python-3.6]
1803904,2018-11-19 00:44:47 UTC,"If you can reproduce this, could you run cloud-init collect-logs (as root) and attach the resulting tarball to this report?"
1803904,2018-12-02 23:13:32 UTC,"On Wed, 21 Nov 2018 at 06:41, Nick Zaccardi <email address hidden>
wrote:"
1803904,2018-11-20 17:27:53 UTC,"Hi Michael,"
1803905,2019-05-22 10:25:41 UTC,"I can confirm that this also happens on Ubuntu 19.04. Slightly frustrating, in that once F9 is pressed you can't escape losing that window."
1803905,2019-08-08 17:09:38 UTC,"Same here on Ubuntu server 18.04
byobu version 5.125
tmux 2.9a"
1803905,2019-06-22 19:11:51 UTC,Can confirm on openSuse as well:
1803917,2018-12-12 00:28:28 UTC,These are all probably related:
1803917,2018-12-11 22:24:52 UTC,So I thought that uninstalling reset the preferences but I also did the thing you said but finally the thing that worked was deleting my appdata completely.
1803917,2018-12-11 21:12:13 UTC,">  but it didn't seem to have any effect on 92.1, 92 or 91
"
1803917,2018-12-11 20:51:00 UTC,"I've tried that but it didn't seem to have any effect on 92.1, 92 or 91. All of the times I've tried have been fresh installs. I'm fairly certain it's not opening offscreen since only one window is shown in the taskbar and in task manager. I also at one point tried only using one screen and that doesn't seem to help either. I've tried installing from the windows store and that doesn't change anything either. I'm grasping at straws here since I basically can't use inkscape and therefore can't make or use any vector graphics."
1803917,2018-12-08 01:29:46 UTC,"If the issue persists with an older version, it's likely to be the offscreen issue."
1803917,2018-11-19 17:38:46 UTC,It's possible the document properties dialog spawns off-screen for some reason (common problem in Windows in multi-monitor setups). If so you should be able to get it back following the steps described at [1].
1803917,2020-01-25 11:20:37 UTC,"Hi, we're tracking this issue over at Gitlab in this ticket: https://gitlab.com/inkscape/inbox/issues/1149"
1803917,2018-11-27 00:43:35 UTC,"I also can't open doc properties on Windows 10. It doesn't appear to be off-screen since I'm very used to that happening and all my tricks to get it back on screen, including the ones listed in #1 don't work. Going back to 92.1 isn't working either."
1803924,2020-03-29 20:31:22 UTC,I think this will finally be fixed in time for Ubuntu 20.04 LTS.
1803924,2020-03-29 22:27:44 UTC,"To give a few more details, mypaint was removed from the 20.04 archives for a different issue. mypaint 2.0.0 is now in the NEW queue where it will probably be accepted soon."
1803924,2018-11-19 15:58:00 UTC,I am unmarking this a duplicate. The other bug is closed in Ubuntu & isn't specific about this issue so let's keep this bug open.
1803924,2018-11-19 20:12:21 UTC,"@jbicha I agree, but I am not sure if this is really a bug with gimp since the problem is MyPaint's reliance on an older version of the library, and ultimately their failure to release a newer version that relies on libmypaint 1.3. We first approached this topic over 6 months ago (prior to Bionic's release) and it went nowhere. This is frustrating since we want to get MyPaint back in Ubuntu Studio, but we're stuck with them being not coinstallable."
1803924,2018-12-22 07:45:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803924,2019-04-27 09:01:38 UTC,"Same issue here on Ubuntu 18.04
I guess it's time for me to check out the snap system if I want to use both applications"
1803924,2019-05-05 22:00:19 UTC,ubuntu is on 19.04 and still this bug exist...amazing incompetence
1803924,2019-05-06 03:33:42 UTC,"@cs-. Such belittling comments are inappropriate in a bug comment. If you have nothing to contribute, please refrain from making such comments in the future."
1803924,2019-06-17 22:23:19 UTC,"Now that MyPaint 2.0.0-alpha is available, it's worth packaging it?"
1803924,2019-06-18 00:08:05 UTC,"@malix0 The MyPaint package is inherited from Debian. They typically do not package alpha or beta packages, but only final releases since the focus is on stability as opposed to having the latest thing. Therefore, this is likely not to happen until MyPaint has released 2.0.0."
1803925,2018-11-23 11:13:13 UTC,related: https://review.openstack.org/#/c/619126/
1803925,2019-01-21 12:16:45 UTC,"Abandoned https://review.openstack.org/#/c/619126/ in favor of https://review.openstack.org/#/c/624943/, which is now committed."
1803933,2018-11-19 15:55:45 UTC,"Hi there,"
1803933,2018-11-19 15:50:34 UTC,This is not a MAAS issue but a curtin issue (what MAAS uses for the installation).
1803933,2018-11-20 07:19:09 UTC,"Ryan,
I  can understand that, but if the case some form of variable check has to be put in place."
1803933,2018-11-27 17:13:56 UTC,"On Tue, Nov 20, 2018 at 1:30 AM Luca Cervigni
<email address hidden> wrote:

>
> Ryan,
> I  can understand that, but if the case some form of variable check has to be put in place.
"
1803933,2019-01-27 04:17:37 UTC,[Expired for curtin because there has been no activity for 60 days.]
1803933,2018-11-19 16:38:51 UTC,Curtin can validate the name value in the config; if it matches kernel names (mdXX) then the path can be /dev/{name} if it doesn't match then it needs to use /dev/md/{name}.
1803933,2020-06-01 21:53:21 UTC,"This bug is fixed with commit a0ede163 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=a0ede163"
1803942,2018-11-28 14:52:06 UTC,"This is caused by 876dcb relies on dev->driver to tell if __device_release_driver() was completed by other callers while calling remove(). But drivers like mei_wdt will set dev->driver to NULL after its remove() completes, thus it would do return instead of continuing __device_release_driver()."
1803942,2018-11-19 07:36:29 UTC,I commented out this patch of 876dcb and cannot reproduce the issue afterward.
1803942,2018-11-19 07:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803942,2018-11-19 07:34:02 UTC,"I tried mainline kernel 4.20-rc2, 4.18, 4.17, 4.16 and 4.15. They all passed a 50 run test.
To validate when the issue is introduced, I installed several Ubuntu kernel packages and address the issue/regression happens between 4.15.0-34 and 4.15.0-36."
1803942,2018-12-20 05:26:04 UTC,This bug was fixed in the package linux - 4.15.0-43.46
1803942,2018-12-10 03:21:48 UTC,"With the proposed kernel, my system passed a 30-run stress."
1803942,2018-12-07 12:36:23 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1803943,2018-11-20 19:23:58 UTC,"Hi Rick,"
1803943,2018-11-20 15:38:20 UTC,"Thanks, yes we have on our roadmap work to enable restoring to a new controller. At this time that's not a supported restore mechanism and so we suggest using HA with backups to help recover. You need to have one of the HA available to restore to in order to successfully use restore."
1803950,2020-04-27 04:17:39 UTC,[Expired for juju because there has been no activity for 60 days.]
1803950,2019-06-12 17:30:43 UTC,"I don't think anyone has ever been able to replicate this anywhere, it may have been specific to this air-gapped environment."
1803950,2018-11-20 16:06:54 UTC,What more info is needed?  I will do my best to gather whatever I can.  I have run oit of tests to try at this point.
1803950,2018-11-27 14:42:49 UTC,UPDATE:
1803950,2018-11-21 08:26:47 UTC,Some preliminary tests of deploying more units (aodh in this case) to controller nodes show I might have a solid work around.
1803950,2018-11-21 08:07:00 UTC,"Following Dean's suggestion, and going by some suggestions from Nobuto, I have the following results."
1803950,2018-11-20 17:24:37 UTC,"I'll give that a go.  If it works at least we narrow it down to juju lxc
something.  If not, I've got a bigger problem."
1803950,2018-11-20 16:50:38 UTC,"@jhillman, this doesn't look like a Juju bug, this looks like an environment issue. Please work with @nobuto or your colleagues to verify the environment. Can you deploy a machine, start a container and run an apt update inside it? If you can't, it's definitely an environmental issue."
1803950,2018-11-20 15:49:32 UTC,"That did not work either.  Per /var/log/cloud-init-output.log, the initial apt update before the postruncmds is also failing, which is causing some core components the cloud-init is asking for to fail installation."
1803950,2018-11-20 15:45:14 UTC,"Marking incomplete as we're awaiting new word on latest testing and we don't have a root cause to be able to work towards at the moment. However, I did mark critical in that this is a blocking issue and once we get more info we should do everything we can to address."
1803950,2018-11-20 15:31:41 UTC,Disabling MAAS proxy has no impact on this problem.
1803950,2018-11-20 13:12:04 UTC,"We just ran the curl, on a bare-metal machine, and the checksums matched for both updates and security (security was a particular repo that is failing)"
1803950,2018-11-21 09:05:15 UTC,"Doing a full deploy, it looks like my workaround is good.  i'll remove the field-critical tag."
1803950,2018-11-20 13:02:36 UTC,"RE my comment #9, that still did not fix the problem."
1803950,2018-11-19 14:47:27 UTC,2 things
1803950,2018-11-19 13:38:17 UTC,I realized we still had apt-mirror set in the model-config.yaml.  we are removing that and re-deploying.
1803950,2018-11-19 13:24:13 UTC,We tried this config in the juju model-config.
1803950,2018-11-19 12:42:05 UTC,FYI the previous workaround doesn't work.  We're running into race conditions when trying to do either apt clean or apt update via cloud-init where the charm is already running apt commands.
1803950,2018-11-19 09:32:34 UTC,"Interestingly, not all machines do appear to work out of the box.  aodh, for example, worked just fine."
1803950,2018-11-19 09:12:40 UTC,"I can (from a visual perspective), but it will be some time.  we have a deploy running and need to debug some other things.  Since we have a work around this is a lower priority, but we will eventually circle back to it."
1803950,2018-11-19 09:04:35 UTC,Any chance you can get the contents of /var/lib/apt/lists/... for comparison of metal vs one of the containers?
1803950,2018-11-19 08:46:10 UTC,We redeployed the cloud adding the cleaning of /var/lib/apt/lists and apt clean to juju cloud-init postruncmds and charms appear to have no issue upon initial LXD creation and installation.
1803950,2018-11-20 04:14:34 UTC,"@Jeff,"
1803950,2019-06-12 09:03:06 UTC,"Given this is no longer field-critical, is it still considered a Critical bug for Juju?"
1803950,2018-11-19 12:20:29 UTC,"Ok, so here's what is different about the bare-mtal vs. LXD in /var/lib/apt/lists..."
1803958,2019-06-03 08:45:34 UTC,This bug was fixed in the package s390-tools - 2.6.0-0ubuntu7.3
1803958,2019-05-22 09:00:45 UTC,In later releases PATH is set to a value that includes cryptsetup utilities and `zkey cryptsetup` operates correctly there. Thus this patch is not needed in later releases.
1803958,2019-05-23 08:42:14 UTC,Thanks for the context!
1803958,2019-05-23 08:44:20 UTC,"Hello bugproxy, or anyone else affected,"
1803958,2019-02-21 13:40:01 UTC,"------- Comment From <email address hidden> 2019-02-21 08:35 EDT-------
These patches should be easy to backport to whatever zkey code level you have currently..."
1803958,2019-02-21 12:16:02 UTC,"Yeap, that was it. However, I do need to get v2.8.0 into disco first...."
1803958,2019-05-23 09:32:57 UTC,Adjusting tags according to #20
1803958,2019-02-21 11:59:27 UTC,"------- Comment From <email address hidden> 2019-02-21 06:55 EDT-------
I guess you are referring to the GitHub issue #56 that you just submitted (and closed)?"
1803958,2019-02-21 10:48:46 UTC,"However, i'd then to also want to bring back the use PBKDF2 as default PBKDF, patch too."
1803958,2018-11-23 07:09:33 UTC,"------- Comment From <email address hidden> 2018-11-23 02:01 EDT-------
Fine with me."
1803958,2018-11-23 03:54:17 UTC,This bug was fixed in the package s390-tools - 2.6.0-0ubuntu10
1803958,2018-11-23 02:44:17 UTC,"As discussed on https://github.com/ibm-s390-tools/s390-tools/commit/9100327092c470c2e5b5819087c8094822a1c751 it is agreed that it is sufficient if the default configurations of sudo and su (or anything similar) set a predefined secured path. Which has always been true on Ubuntu. Thus, on Ubuntu, one need not set PATH in this instance."
1803958,2018-11-20 17:15:26 UTC,"I feel like I misunderstand the security implication here. Especially since it is my understanding, the binary requires to be executed by a priviledged user, and despite user-controlled PATH would not allow a non-priviledged user to escalate to root or execute arbitrary code."
1803958,2018-11-20 17:09:30 UTC,"Are you deploying zkey/zkey-cryptsetup with setuid bit on?
Do you allow calls to zkey/zkey-cryptesetup with sudoers?
Do you allow to elevate to root whilst executing zkey/zkey-cryptsetup with policykit?"
1803958,2019-05-16 16:25:55 UTC,"That is also something I would like to know before reviewing the SRU further. Was the patch dropped in the development series by accident, or was that intentional? Should we get it back there?"
1803958,2018-11-20 15:40:11 UTC,"------- Comment From <email address hidden> 2018-11-20 10:32 EDT-------
Regarding fork&exec: This would not solve the PATH security problem either. So we would also need to build our own PATH environment for exec."
1803958,2018-11-20 09:39:32 UTC,"------- Comment From <email address hidden> 2018-11-20 04:36 EDT-------
Additional info from Hendrik:"
1803958,2019-05-23 09:09:41 UTC,"------- Comment From <email address hidden> 2019-05-23 05:08 EDT-------
We/IBM already verified it and confirm that it's working."
1803958,2018-11-20 07:59:29 UTC,"------- Comment From <email address hidden> 2018-11-20 02:56 EDT-------
We set the PATH before calling system() to execute the generated program for security reasons. That way a user can not manipulate the PATH environment variable and that way cause a different executable to be used. By setting the path we restrict the search path to the well known executable locations. Remember zkey may run as root or somewhat privileged so that it can execute ""cryptsetup luksFormat"" or similar."
1803958,2018-11-19 18:29:27 UTC,Why is s390-tools overriding the path at all?  The default path on Ubuntu already includes /sbin and /usr/sbin.  Allowing use of the system path would seem preferable.
1803958,2019-06-11 06:39:59 UTC,"------- Comment From <email address hidden> 2019-06-11 02:34 EDT-------
IBM bugzilla status -> Fix released for all requested distros"
1803958,2019-06-03 08:45:46 UTC,"The verification of the Stable Release Update for s390-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1803958,2018-11-20 12:20:28 UTC,sudo is enabled by default for the first installed user.
1803958,2019-05-15 13:49:42 UTC,"The fix for this bug seems to have been inadvertently dropped from the current development release as far as I can tell. Something happened between 2.6.0-0ubuntu7 and 2.7.1-0ubuntu1 - 2.6.0-0ubuntu8, 2.6.0-0ubuntu9 and 2.6.0-0ubuntu10 are missing from debian/changelog in 2.7.1-0ubuntu1, and the fix for this bug was in 2.6.0-0ubuntu10 but vanished in 2.7.1-0ubuntu1. It looks like other fixes were also dropped somewhere, but I haven't investigated further."
1803960,2019-04-09 17:06:02 UTC,Continuing issues up to and including 5.0.0-8. Experienced three lock-ups today.
1803960,2018-12-24 16:03:39 UTC,I almost forgot about this; 4.17.19-041719-lowlatency has been running fine now for 16 days. I'm going to switch to 4.18.0-13-lowlatency and confirm the problem still exists.
1803960,2018-12-07 22:30:06 UTC,Five days running on 4.16.18-041618-lowlatency and had no problems so I'm going to try the mainline build of v4.17.19.
1803960,2018-12-02 15:39:03 UTC,This hang is affecting all mainline builds (from the kernel PPA) up to and including 4.20-rc4.
1803960,2018-11-28 10:44:04 UTC,"Just experienced the same symptom of a complete, silent, freeze with:"
1803960,2018-11-21 20:00:17 UTC,I've been using the 4.18.0-12-lowlatency kernel from cosmic and not had any freeze-ups in the last 48 hours. I'll continue monitoring and report back after a few more days.
1803960,2018-11-19 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1803961,2019-09-27 09:04:39 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1803961,2019-07-10 21:39:51 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1803961,2019-06-18 03:40:59 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1803961,2019-06-06 06:24:09 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1803961,2019-05-10 01:22:42 UTC,"Reviewed:  https://review.opendev.org/657579
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=01141392db549728e78865b6a56468d17102bee0
Submitter: Zuul
Branch:    stable/queens"
1803961,2019-05-09 14:54:54 UTC,"Reviewed:  https://review.opendev.org/657577
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8e130e2be7c2eb604d53fd6053254c6b54d47524
Submitter: Zuul
Branch:    stable/rocky"
1803961,2019-05-09 04:33:43 UTC,"Reviewed:  https://review.opendev.org/657575
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91282f879cb453e4baa6c6decb4fff849c7a1b2a
Submitter: Zuul
Branch:    stable/stein"
1803961,2019-05-07 11:44:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/657579"
1803961,2019-05-07 11:43:41 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/657577"
1803961,2019-05-07 11:39:38 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/657575"
1803961,2019-05-07 09:07:33 UTC,"Reviewed:  https://review.opendev.org/637224
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=53c3cfa7a02d684ce27800e22e00a816af44c510
Submitter: Zuul
Branch:    master"
1803961,2018-11-19 10:09:57 UTC,"In case I don't get back to this soon, anybody else should feel free to update my patches. See also tempest patch https://review.openstack.org/#/c/618533/ ."
1803961,2018-11-19 09:55:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/618717"
1803961,2019-02-15 17:03:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637224"
1803963,2019-07-05 07:26:49 UTC,Another example: filebeat <-> elasticsearch when filebeat <-> graylog <-> elasticsearch is already present.
1803963,2020-08-31 05:11:18 UTC,"Per 1805701 we're not currently checking relations in the linting code, so this bug should be considered whilst implementing relation checks - i.e. ensuring a relation is absent between two charms."
1803968,2019-04-22 11:37:57 UTC,I am planing to fix this issue. We use Ubuntu source images.
1803968,2021-01-07 17:12:43 UTC,This issue was fixed in the openstack/kolla 10.2.0 release.
1803968,2019-04-04 16:02:39 UTC,Also openstacksdk is required.
1803968,2019-04-08 08:35:46 UTC,Are you planning to fix this issue?
1803968,2020-06-03 00:10:06 UTC,"This issue is still occurring. Pip installs rally 2.1.0 and rally_openstack 1.7.0, but still get the same error.Openstacksdk is version 0.45.0"
1803968,2020-10-12 11:45:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/757542"
1803968,2020-10-14 16:58:58 UTC,"Reviewed:  https://review.opendev.org/757542
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=bc1abb3d7b217e46eb147bcc38f766c130bdd4cc
Submitter: Zuul
Branch:    master"
1803968,2020-10-16 09:17:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/758540"
1803968,2020-10-19 10:00:35 UTC,"Reviewed:  https://review.opendev.org/758540
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=48b81b86939e54044d4fa289f2f9e4e620cf44bc
Submitter: Zuul
Branch:    master"
1803968,2020-10-30 15:12:04 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/760574"
1803968,2020-11-07 22:01:42 UTC,"Reviewed:  https://review.opendev.org/760574
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=19e8efb1ce7d6a5c12cc9cd8d827bc229fbe3375
Submitter: Zuul
Branch:    stable/ussuri"
1803969,2019-02-04 16:49:50 UTC,Wes needs to follow up on this work... I think it's related to https://review.openstack.org/#/c/630363/
1803974,2018-11-19 23:55:08 UTC,*** This is an automated message ***
1803980,2020-10-15 14:46:37 UTC,Here is the error I received when I was running snapcraft.  Any clue?
1803993,2018-11-20 03:14:38 UTC,"Hello Thomas, can you please report back what version of plymouth you have installed?"
1803993,2018-11-20 03:34:11 UTC,"^^^
That is probably just to verify this really isn't a duplicate of bug 1767918, and that you have the fix for bug 1767918 already."
1803993,2018-11-20 12:48:19 UTC,"Hi Seth,"
1803993,2018-11-20 22:26:54 UTC,"Hello Thomas, sadly you only got half of the version number. Can you please paste in the full version number?"
1803993,2018-11-21 17:44:12 UTC,"HI Seth,"
1803993,2018-11-21 21:27:12 UTC,Thanks Thomas
1803993,2018-12-18 02:49:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1803993,2019-01-25 15:25:52 UTC,"It seems I can reproduce the issue in qemu and look at vt1 by stopping gdm3, since the switch to vt2 does not show vt1 even for a moment."
1803993,2019-03-21 06:17:02 UTC,Confirmed by https://askubuntu.com/q/1127408/66509
1803993,2019-06-05 01:33:15 UTC,This bug was fixed in the package systemd - 240-6ubuntu9
1803993,2019-04-16 23:35:08 UTC,"I'm pretty sure I just encountered this bug, although all I did was issue a shutdown, and very briefly I was able to see several plaintext passwords that had been used to log in across several user accounts.  I am on Ubuntu 18.04.2 LTS."
1803993,2019-04-17 14:44:32 UTC,@Robert Anderson - could you please report a new bug using ubuntu-bug plymouth? This will gather information from the system in question that will help us investigate the matter. Thanks in advance!
1803993,2019-09-06 12:01:44 UTC,added info from previous comment to the upstream freedesktop bug.
1803993,2019-09-05 12:40:37 UTC,"> Looking at the discussion at https://gitlab.freedesktop.org/xorg/xserver/issues/857#note_201402 this might be a bug in plymouth which is supposedly fixed in plymouth 0.9.4.
"
1803993,2019-09-05 12:18:29 UTC,"@rbalint if you can reliably reproduce the issue, it would probably be a good idea if you follow up on that upstream bug tracker"
1803993,2019-09-05 12:16:19 UTC,Looking at the discussion at https://gitlab.freedesktop.org/xorg/xserver/issues/857#note_201402 this might be a bug in plymouth which is supposedly fixed in plymouth 0.9.4.
1803993,2019-04-24 14:08:09 UTC,It looks like systemd is changing the mode (see argument=3) on VT1 on logouts.
1803993,2019-06-05 10:16:25 UTC,This is still not fixed.
1803993,2019-04-24 17:53:37 UTC,Forwarded proposed fix to systemd upstream: https://github.com/systemd/systemd/pull/12378
1803993,2019-05-29 15:41:07 UTC,"> can you get it pushed out to eoan-updates (or revert it)?
"
1803993,2019-05-29 13:31:27 UTC,"@rbalint, this is still in eoan-proposed, can you get it pushed out to eoan-updates (or revert it)?"
1803993,2019-05-21 10:52:27 UTC,"This may have caused a regression upstream, see
https://github.com/systemd/systemd/pull/12378#issuecomment-493776598"
1803993,2019-05-17 18:40:54 UTC,Use CVE-2018-20839.
1804001,2019-07-09 14:46:05 UTC,How come this is invalid? I do not see any documentation on this for 2.6.
1804006,2018-11-19 17:26:43 UTC,I think there is also a snapd bug here:
1804006,2018-11-21 16:00:37 UTC,"On snapcraft's side, don't your hooks in snap/hooks make it to prime/meta/hooks?"
1804006,2018-11-21 16:34:12 UTC,"Yes the hooks themselves are installed into the right place in the snap, but the associated confinement, i.e. AppArmor profiles, don't include the policies listed in the root level plugs like the apps do. This is a problem if you need your configure hook to access the network, or home folder, etc. You can fix it by manually also declaring all the plugs in the hooks section in the snapcraft.yaml, but I'm saying that if you use the root level plugs (and hence all apps), you shouldn't have to also declare it for all the hooks you have in the snap."
1804006,2018-11-23 12:22:59 UTC,Proposed PR for snapd: https://github.com/snapcore/snapd/pull/6180
1804006,2019-02-08 16:06:55 UTC,"Is this bug now fixed? It seems that now, hooks will implicitly pick up slots/plugs declared in the root snap.yaml rather than have the relevant interfaces specified explicitly in hooks in the snap.yaml."
1804006,2019-02-08 16:58:28 UTC,Bug should be now fixed in snapd 2.37.
1804007,2018-11-20 03:18:56 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1804007,2018-11-29 14:45:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804013,2019-10-10 12:35:33 UTC,During and after 18.10 we did quite a bit of work with snaps to help them launch quicker in 18.10 (a change in fontconfig made our previous work not be effective there).
1804015,2018-11-19 15:52:17 UTC,"Hi Nobuto,"
1804015,2018-11-19 16:13:55 UTC,"> Since in 2.5+ all the DNS traffic goes through the rack controller, can you please provide an example of what your expectation would be for 2.5+ ?
>
> Is this expected to be done both for the rack & the region controller ?
"
1804015,2018-11-19 19:55:02 UTC,"@Nobuto,"
1804015,2019-09-19 12:07:02 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1804027,2018-12-06 14:48:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804027,2018-12-06 15:10:25 UTC,"OK, the touchpad issue is not related at all, there is a kernel driver explanation of that. Now it works (the touchpad) but still, the mentioned dbus error message occurs from time to time, not so consistent though now."
1804028,2018-11-19 20:42:56 UTC,"https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/ath10k/QCA6174/hw3.0/ the files in that folder need to be modified I think and added the needed information in the board-2.bin . So if anyone knows which informations are needed, please let me know and I will help debugging to get the stuff upstream."
1804028,2018-11-20 16:00:53 UTC,So somehow with newer boad-2.bin files the card get recognized but the firmware still crashes.
1804028,2018-11-19 20:54:36 UTC,this is the output of dmesg after replacing the board.bin with the one from killernetworking.com:
1804028,2018-11-19 20:32:41 UTC,"After copying the above http://www.killernetworking.com/support/K1535_Debian/board.bin to the following folder ""/lib/firmware/ath10k/QCA6174/hw3.0"", the wifi works flawless. Just the ""board.bin"" and ""board-2.bin"" in ""/lib/firmware/ath10k/QCA6174/hw3.0"" have to be deleted before."
1804028,2018-11-20 16:00:08 UTC,Summary of all tests:
1804028,2019-07-23 20:32:13 UTC,"Using the currently latest version (linux-firmware-20190717-99) on Fedora 30, the Wifi network adapter is still not recognized:"
1804028,2019-06-20 15:21:40 UTC,This bug is still active on linux-firmware-20190514 that I'm running. I'll help any way I can if help is needed.
1804028,2018-11-20 07:25:59 UTC,"There is also a .zip files available https://www.killernetworking.com/killersupport/item/killer-drivers-inf which includes some .bin files for the QCA6174 (e.g.  ""qca61x4_1_1_2.bin"" )"
1804028,2019-10-07 07:33:29 UTC,"The driver should has been landed in Ubuntu-1.167, which available in bionic. Please verify with the latest LTS version."
1804028,2020-04-06 02:09:22 UTC,"I've just tested it booting with an ubuntu 20.04 beta iso and the problem seems to persist. From the top menu I see the wifi working but no networks appear, even thhough there are many available."
1804028,2019-03-07 12:20:33 UTC,I've installed latest linux-firmware (and all other possible updates) in Fedora 29 and wifi is still not working on a Surface Go
1804028,2019-02-24 04:08:28 UTC,"linux-firmware-20190213-93.git710963fe.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report."
1804028,2019-02-19 14:02:36 UTC,"linux-firmware-20190213-93.git710963fe.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report."
1804028,2019-02-15 02:57:11 UTC,"linux-firmware-20190213-93.git710963fe.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-42cbff0fd6"
1804028,2019-04-06 15:53:26 UTC,I can confirm that a freshly installed Fedora 30 with linux-firmware-93.git710963fe.fc30 does not recognize the QCA6174 on Surface Go. I'm willing to help any way I can.
1804028,2019-02-15 01:31:11 UTC,"linux-firmware-20190213-93.git710963fe.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-f27089e66c"
1804028,2019-02-14 12:26:33 UTC,linux-firmware-20190213-93.git710963fe.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-42cbff0fd6
1804028,2019-02-14 12:18:35 UTC,The inux-firmware-20190213-93.git710963fe has a new firmware for QCA6174 so please test
1804028,2018-11-20 22:41:35 UTC,"Did some additional tests with ""eeprom_ar6320_3p0_TX8_clpc.bin"":"
1804028,2018-11-20 22:41:25 UTC,"Did some additional tests with ""eeprom_ar6320_3p0_TX8_clpc.bin"":"
1804028,2018-11-20 22:18:48 UTC,"In the .zip from https://www.killernetworking.com/killersupport/item/killer-drivers-inf in the file ./Killer-Ethernet-Wireless_INF/Production/Windows10-x64/11AC/netathr10x.inf I finally found one matching subsystem-device=3370 entry, which leads to:"
1804028,2018-11-20 22:18:44 UTC,"In the .zip from https://www.killernetworking.com/killersupport/item/killer-drivers-inf in the file ./Killer-Ethernet-Wireless_INF/Production/Windows10-x64/11AC/netathr10x.inf I finally found one matching subsystem-device=3370 entry, which leads to:"
1804028,2018-11-20 19:42:11 UTC,Description of problem:
1804028,2019-02-14 12:26:45 UTC,linux-firmware-20190213-93.git710963fe.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f27089e66c
1804028,2019-06-20 15:19:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804038,2018-11-20 17:42:59 UTC,"After some chatting in IRC, a new potential branch is here:"
1804038,2018-11-19 21:02:34 UTC,This branch fixes all 3 undecorated calls to clense_ISO8601 that I found in a cursory search. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1772062_clense_iso8601  working/user/jboyer/lp1772062_clense_iso8601
1804038,2019-04-03 16:12:10 UTC,"Dependent bug #1552778 has now been merged to 3.1, so merging this as well."
1804038,2018-11-20 18:46:03 UTC,"Pushed to master and rel_3_2.  Thanks, Jason!"
1804038,2018-11-20 18:37:56 UTC,"And I prefer doing things the right way, so after testing Dans' branch everything looks good. Signoff lives here:"
1804038,2018-11-20 17:11:23 UTC,"Quick note to testers/committers, that is the correct branch to address this bug; I just mis-named it because I had too many LP tabs open apparently."
1804040,2019-02-01 01:45:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804041,2020-06-16 16:25:35 UTC,Sorry for the wrong update. It is still in triage mode.
1804042,2019-01-30 04:09:18 UTC,"One point I'd also like to add here, and it is an important one, how we implement this has to be VERY configurable around how the headers are parsed. Header spoofing, which ones to trust, which parts of the header (or which of the multiple headers) to trust, etc. All those are potential vectors we need to try and handle, or at least supply methods which will allow deployers to make sure the correct headers are used and parsed."
1804042,2019-01-30 03:49:20 UTC,"@tobias
Most of the APIs to configure MFA in Keystone are admin only, and while I think making them more user friendly may be a good idea it can be a little hard with Keystone."
1804042,2019-01-25 09:43:40 UTC,"I agree with Adrian, I won't advocate for any implementation but just for the feature itself."
1804042,2019-01-25 00:59:06 UTC,"So my original thoughts on this when bringing it up is for situations where you want to secure a service/api user with a second factor. Using totp is awkward with an automated account, and means that you'd be storing the password and secret together."
1804042,2018-12-10 19:26:16 UTC,This should be implemented after 1807751 (Resource Options For All). This is a good RFE.
1804043,2019-05-23 13:28:22 UTC,I think this bug could be related to the  bug I think this bug could be related to the  bug 1824723
1804043,2019-04-03 18:55:29 UTC,This is also true for item and record buckets.
1804052,2020-03-07 15:47:10 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1804054,2018-11-19 20:21:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804054,2019-03-05 09:51:26 UTC,"Issue remains in latest 4.15.0-1040-azure.
No new version for kdump-tools - latest 1.5.5-2ubuntu1.6."
1804055,2018-11-19 21:30:08 UTC,Managed to reproduce it on my testbench with a scope connected. https://i.imgur.com/dqbykIJ.png
1804055,2018-11-25 21:22:55 UTC,Played around a bit with the workaround flashed.
1804055,2018-11-28 10:33:51 UTC,"Any idea which version of the firmware was installed?  I mean, which branch and revision?"
1804055,2018-11-28 15:30:07 UTC,I agree on needing to fix it instead of just using a workaround.
1804055,2018-11-30 00:25:08 UTC,"I was mostly wondering if it still happens after the recent event system rewrite.  But it sounds like it probably does still happen, because it's likely more related to the WDT and sleep ticks, and less related to how logical events are handled."
1804055,2018-11-30 07:06:53 UTC,"Yes, it still happens with the event system rewrite."
1804055,2019-06-02 07:58:15 UTC,"I haven't seen this happen in at least six months, and haven't heard any reports about it either.  I think it may be fixed, but it's hard to say for sure since it was really rare and hard to reproduce even when it was definitely still an issue."
1804056,2019-03-22 13:28:45 UTC,"Yes, still the case in rocky.
(undercloud) [stack@c09-h11-r630 ~]$ openstack overcloud plan delete overcloud
Deleting plan overcloud...
None"
1804056,2019-05-22 04:17:17 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1804056,2019-02-19 13:11:52 UTC,Can you specify the version you're using?
1804056,2019-02-19 13:11:23 UTC,Is this still an issue?
1804057,2018-11-19 20:34:29 UTC,"FYI, this is semi-related to lp#1773377 where we're looking to pass dns_frontend IPs to n-ovs and n-gw charms via relation.  Instead of this, we can workaround by using/configuring these vips/service_ips and just manually configure the IPs in all three charms plus squash an upstream no-relation-available issu with this feature."
1804057,2018-11-20 06:00:20 UTC,My 2 cents:
1804057,2018-12-04 14:49:52 UTC,Linked bug 1773377
1804057,2018-12-04 14:52:52 UTC,"I'm not very keen on the approach of adding more out-of-band management of IP addresses via charm config - just like VIP's, having IP via config is brittle and prone to error.  How much of a problem is this really? I appreciate that having to update DNS pointers in upstream DNS systems to point to new bind servers in the deployment is *work*."
1804057,2018-12-06 17:05:27 UTC,"I think we could have this debate for a while about the work/changes involved.  This is a pain point for every cloud handover to bootstack.  the customer tests DNS with one set of bind IPs with Field Engineering, then Bootstack redeploys getting new bind IPs (without Dmitrii's workaround subnet)."
1804057,2020-07-26 08:42:48 UTC,"IMO, the most important point to consider: Day-2 operations."
1804057,2020-08-19 23:15:05 UTC,"Just to keep this wishlist alive, I was looking at pacemaker resource rules and I believe this could be done if we create two standard VIP (or SIP, service IP?) resources:"
1804060,2018-11-20 18:12:56 UTC,The Debian bug I referred to is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856429 . Launchpad shouldn't be so egocentric and assume all bug numbers are launchpad bug numbers ;-).
1804060,2018-11-22 09:04:06 UTC,"Hehe, ego LP
I added the bug to the tasks."
1804060,2018-11-22 09:23:32 UTC,"Hi Oliver,
I agree with Bernd on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856429#10
With sysV init being even ""less meant to be considered"" on Ubuntu than on Debian (and even there it is not more a big thing)."
1804062,2019-08-12 21:11:33 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1804062,2019-09-27 09:02:56 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1804062,2020-06-04 11:45:33 UTC,"Looking at the versions of nova that are in the archives, this seems to be fix-released"
1804062,2019-08-10 01:20:51 UTC,"Reviewed:  https://review.opendev.org/665790
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dc2963d2a0002d4ddacf50b1f80c470d5de7ec61
Submitter: Zuul
Branch:    stable/queens"
1804062,2019-07-24 19:10:12 UTC,"Reviewed:  https://review.opendev.org/665788
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4858074c89838eadeb9eaf9f39917e9fb90acd93
Submitter: Zuul
Branch:    stable/rocky"
1804062,2019-06-14 22:22:42 UTC,"Reviewed:  https://review.opendev.org/665147
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0cb6106b83c33bded9e6cdec7737964c36be8de5
Submitter: Zuul
Branch:    stable/stein"
1804062,2019-06-13 14:25:08 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/664841
Reason: https://review.opendev.org/665147"
1804062,2019-06-12 23:42:18 UTC,"Reviewed:  https://review.opendev.org/664940
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f545a25cc443c41dcd9bdd028064c28b53f56037
Submitter: Zuul
Branch:    master"
1804062,2019-08-19 15:40:53 UTC,This issue was fixed in the openstack/nova 17.0.12 release.
1804062,2019-06-12 14:34:43 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/664940"
1804062,2019-06-12 05:39:56 UTC,"Reviewed:  https://review.opendev.org/664622
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=18ba6e6e6a7d1294bd1f1ece454f84eb65b219bb
Submitter: Zuul
Branch:    master"
1804062,2019-06-11 15:30:26 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/664622"
1804062,2019-05-03 20:02:12 UTC,I'm tracking the Ubuntu SRU for the work-around in https://bugs.launchpad.net/bugs/1782786.
1804062,2019-05-03 17:54:08 UTC,I'm also hitting this on Bionic (bionic-proposed) with the final 2.7.15 release. So this is currently seen on bionic and above with 2.7/3.6/3.7. Ubuntu package versions can be tracked at:
1804062,2018-11-20 04:57:21 UTC,"Reviewed:  https://review.openstack.org/618843
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9875c37d9a09ee7160f13c9771cf14ce02cec027
Submitter: Zuul
Branch:    master"
1804062,2018-11-19 21:43:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/618843"
1804062,2018-11-19 21:09:25 UTC,"> The fix ought to be adding a newline to the code sample. Maybe.
"
1804062,2019-06-12 09:41:41 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/664841"
1804062,2019-08-12 20:42:12 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1804063,2018-11-19 21:23:49 UTC,Bundle:
1804063,2018-11-21 10:27:34 UTC,"I have marked this as incomplete, as I am peeling off to some other tickets."
1804063,2018-11-19 21:24:40 UTC,"FWIW, the same procedure with series: bionic:"
1804063,2018-11-19 21:33:28 UTC,Sorry but more info then. Can we verify that the charm in ../../../nova-cell-controller declares cosmic and bionic as valid series and to verify this works if you just change the top of the bundle from cosmic to bionic?
1804063,2018-11-19 21:38:03 UTC,"Indeed, confirmed.  Metadata contains series: cosmic."
1804063,2018-11-20 18:09:33 UTC,Reproduced. Will address as soon as I am able.
1804063,2018-11-21 10:25:17 UTC,The pertinent difference between these bundles is that nova-cell-controller-cell2 specifies a series here:
1804063,2018-11-19 21:21:22 UTC,IMPACT:  OpenStack CI cannot enable series: cosmic at this time.
1804063,2019-07-14 04:17:22 UTC,[Expired for juju because there has been no activity for 60 days.]
1804063,2019-07-14 20:04:18 UTC,"Resurrecting this ticket. Because its severity, I think that it should be actively closed rather than cleaned up by the janitor."
1804063,2019-07-14 23:14:49 UTC,"@Tim McNamara (tim-clicks),"
1804063,2019-07-15 06:41:02 UTC,"As a suggestion, when a bundle declares a series and a local charm does not, the deploy will fail with this error. If you bundle does not declare a series, I can understand requiring a series but, for a multiseries local charm, it seems reasonable that Juju could use the bundle's series rather than throwing this error."
1804063,2019-07-15 22:40:11 UTC,"Sounds good, I'll flick back to Triaged and it will be addressed as part of the queue."
1804063,2018-11-19 21:19:33 UTC,"Confirmed by another team member, concur this is a Juju core 'series: cosmic' issue."
1804064,2018-11-20 19:54:04 UTC,"Added mistralclient as affected project, I tested locally and other services work."
1804065,2020-11-16 14:44:05 UTC,Applies to EG 3-6-0
1804068,2018-11-20 12:21:00 UTC,"UPD: сегодня как только открыла прогу выяснилось, что настройки каким-то непостижимым образом сбились сами собой. Пропали метки кистей, рабочее пространство и прочие следы моего пребывания. Контур выделения появился, проблема решилась."
1804125,2019-08-29 10:45:03 UTC,"Reviewed:  https://review.opendev.org/678254
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e5b304af45423e61d5d591e5deb81d3848df1798
Submitter: Zuul
Branch:    stable/stein"
1804125,2019-08-23 15:23:35 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/678254"
1804125,2019-08-21 22:27:21 UTC,"Reviewed:  https://review.opendev.org/673496
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=588194d785b1bb52e53ed159c5d8645bf3a28b7d
Submitter: Zuul
Branch:    master"
1804125,2018-12-04 20:57:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622588"
1804125,2018-12-07 16:38:10 UTC,"@Jeff, yeah it's gross, and taken way too long to deal with (granted, I don't think anyone noticed/appreciated this regression until ~queens, about a year after it happened)."
1804125,2018-12-07 16:39:46 UTC,Added osc-placement to this bug given the previous proposal to provide a helper CLI to mirror the allocation ratio aggregate metadata in placement.
1804125,2018-12-07 16:52:53 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623546"
1804125,2018-12-07 16:57:00 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/623547"
1804125,2018-12-07 17:15:55 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/623552"
1804125,2018-12-07 17:16:43 UTC,Reviving the ML discussion on this:
1804125,2018-12-10 10:11:46 UTC,"Reviewed:  https://review.openstack.org/620713
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d65c18a0a9f02e6d37f2b87ff61f1740c8bfc867
Submitter: Zuul
Branch:    master"
1804125,2018-12-10 15:22:57 UTC,"Reviewed:  https://review.openstack.org/622588
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c50711249549a0abf84d0c0e26a3f3aae4928c4
Submitter: Zuul
Branch:    master"
1804125,2018-12-14 01:06:30 UTC,"Reviewed:  https://review.openstack.org/623546
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=899b4ca5a248eba252d3c89e373f8a787d68749c
Submitter: Zuul
Branch:    stable/rocky"
1804125,2019-02-22 00:14:08 UTC,"Reviewed:  https://review.openstack.org/623547
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5c7638bab40bd6cfdbc199527d3a8c86bde40897
Submitter: Zuul
Branch:    stable/queens"
1804125,2019-03-13 14:57:57 UTC,"Reviewed:  https://review.openstack.org/623552
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0cb9767e90c0e1121d4e7239a60340ce6f88e413
Submitter: Zuul
Branch:    stable/pike"
1804125,2019-04-12 16:11:45 UTC,https://review.openstack.org/#/c/640898/ is a related osc-placement change.
1804125,2019-08-22 20:13:53 UTC,"Reviewed:  https://review.opendev.org/677472
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=77efc084fc50d38d2a1b42aca864a2a56eae6eba
Submitter: Zuul
Branch:    master"
1804125,2019-05-31 15:49:23 UTC,I think at this point we can mark the nova portion of this as won't fix with these changes to manage allocation ratios:
1804125,2018-11-28 22:51:55 UTC,"As an operator, I don't really have a strong opinion one way or the other on whether allocation ratios should be controlled per compute in config files or per aggregate in metadata; in general, I consider the aggregate metadata approach more agile and more in keeping with OpenStack's common pattern of API accessibility to most operations, but I can see an argument on each side."
1804125,2018-11-28 22:10:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620713"
1804125,2018-11-28 21:46:15 UTC,"I guess there was a release note in queens: https://review.openstack.org/#/c/541018/ which was backported to pike and ocata, but the problem with release notes is they don't get noticed when you're past that old release and the issue is still not resolved...hence we need this in docs as well."
1804125,2018-11-28 21:40:36 UTC,At the very least we should probably document the bug in the docs for the aggregate ram/core/disk filters.
1804125,2018-11-28 21:38:02 UTC,I've linked this to blueprint https://blueprints.launchpad.net/nova/+spec/placement-aggregate-allocation-ratios.
1804125,2018-11-28 21:34:41 UTC,It's a regression with placement being used by the nova scheduler since Ocata. There is a related nova blueprint in the stein release:
1804125,2019-08-20 14:11:15 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/677472"
1804128,2018-11-20 13:38:01 UTC,"This is because swift-storage is now a py3 charm, but the code in charmhelpers wasn't actually upgraded to py3 code entirely."
1804128,2018-11-20 14:29:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619009"
1804128,2018-11-20 18:19:19 UTC,"Reviewed:  https://review.openstack.org/619009
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=25ec6c6a3dd609746d1194a07588ca954f19a333
Submitter: Zuul
Branch:    master"
1804128,2018-11-20 19:40:46 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/619078"
1804128,2018-11-22 18:53:28 UTC,"Reviewed:  https://review.openstack.org/619078
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=49b53d996c9cc5dac594844091ddbaac05a6f207
Submitter: Zuul
Branch:    stable/18.11"
1804137,2019-01-08 22:48:34 UTC,The preview pane allows custom text and always has.
1804138,2018-11-20 08:30:52 UTC,"It seems that ld is using “no” as a sysroot. The interesting part here is in the “large script” you removed; could you at least tell me what the “SEARCH_DIR” setting is, near the start of the script?"
1804138,2018-11-20 20:27:23 UTC,I guess you mean this...
1804140,2018-11-20 10:17:21 UTC,"I know Anastasia has been working in this area, and some of those fixes are
in more recent 2.4 series. This may have already been fixed."
1804140,2018-11-29 05:46:54 UTC,The problem is that we cache model api connection on the command.
1804140,2018-11-29 08:59:52 UTC,PR for 2.5: https://github.com/juju/juju/pull/9523
1804141,2018-11-20 07:11:46 UTC,On which OS are you? And which sound API do you use. Are all tracks effected?
1804141,2018-11-21 16:59:00 UTC,"This is probably a duplicate of Bug #1490580, which was fixed in Mixxx 2.1.0."
1804149,2020-01-14 05:22:36 UTC,@finnegan thanks for the feedback - closing this ticket according to comment #24.
1804149,2020-01-13 21:50:29 UTC,"------- Comment From <email address hidden> 2020-01-13 16:40 EDT-------
This defect can be closed."
1804149,2019-04-02 18:19:55 UTC,"------- Comment From <email address hidden> 2019-04-02 14:10 EDT-------
(In reply to comment #29)

> Can you please test the test kernel at:
> https://kernel.ubuntu.com/~juergh/lp1804149/
"
1804149,2019-05-14 11:00:09 UTC,"IBM, have you had any luck with the test kernel?"
1804149,2018-11-20 06:59:28 UTC,Default Comment by Bridge
1804149,2018-11-20 15:27:27 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1804149,2018-11-20 20:49:35 UTC,"------- Comment From <email address hidden> 2018-11-20 15:44 EDT-------
(In reply to comment #6)

> Did this issue start happening after an update/upgrade?
"
1804149,2018-11-26 17:05:44 UTC,Were you able to test the mainline kernel to see if this bug still exists there?
1804149,2018-11-28 18:59:36 UTC,"------- Comment From <email address hidden> 2018-11-28 13:52 EDT-------
(In reply to comment #9)

> Were you able to test the mainline kernel to see if this bug still exists
> there?
"
1804149,2018-12-03 19:07:16 UTC,"In bug 1782085 it looks like the bug stopped happening after upgrading to version 4.15.0-23.  Do you know if that is still the case with that older system, or has the bug come back after upgrading to a newer kernel version?"
1804149,2018-12-05 02:09:28 UTC,"------- Comment From <email address hidden> 2018-12-04 21:05 EDT-------
(In reply to comment #13)

> In bug 1782085 it looks like the bug stopped happening after upgrading to
> version 4.15.0-23.  Do you know if that is still the case with that older
> system, or has the bug come back after upgrading to a newer kernel version?
"
1804149,2018-12-11 07:19:58 UTC,"Not sure if I understand the overall situation correctly, but:"
1804149,2018-11-20 06:59:26 UTC,Default Comment by Bridge
1804149,2018-12-11 23:19:39 UTC,------- Comment on attachment From <email address hidden> 2018-12-11 18:14 EDT-------
1804149,2018-12-11 23:19:43 UTC,------- Comment on attachment From <email address hidden> 2018-12-11 18:16 EDT-------
1804149,2018-12-11 23:19:45 UTC,------- Comment on attachment From <email address hidden> 2018-12-11 18:17 EDT-------
1804149,2018-12-12 12:03:51 UTC,"Having a look at the new logs it shows that there are many different disks and disk systems in use.
I see DASDs, that get partly unhappy, like:
Dec  8 07:43:29 ilabg3 kernel: [651348.534047] dasd(eckd): I/O status report for device 0.0.248b:
Dec  8 07:43:29 ilabg3 kernel: [651348.534047] dasd(eckd): in req: 000000006004d11c CC:00 FC:01 AC:00 SC:01 DS:00 CS:00 RC:0
Dec  8 07:43:29 ilabg3 kernel: [651348.534047] dasd(eckd): device 0.0.248b: Failing CCW:           (null)
Dec  8 07:43:29 ilabg3 kernel: [651348.534047] dasd(eckd): SORRY - NO VALID SENSE AVAILABLE
Dec  8 07:43:29 ilabg3 kernel: [651348.534072] dasd(eckd): Related CP in req: 000000006004d11c
Dec  8 07:43:29 ilabg3 kernel: [651348.534072] dasd(eckd): CCW 00000000584ecfe4: 2740000C 7FE86BC0 DAT:  18000000 00000e00  00000000
Dec  8 07:43:29 ilabg3 kernel: [651348.534072] dasd(eckd): CCW 00000000a235ae5d: 3E000200 7FEDD400 DAT:  00000000 00000000  00000000
(of course not related to the reported issue)
I see 'local' scsi disks:
scsi 3:0:12:0: Direct-Access     IBM      FlashSystem-9840 1600 PQ: 0 ANSI: 5
and I see XIV Storage as well."
1804149,2019-01-11 02:40:55 UTC,"------- Comment From <email address hidden> 2019-01-10 21:11 EDT-------
In response to

>The error messages that belong to the Ops seem to be known and points to a potential race discussed here:
>[RFC,1/1] libiscsi: Fix race between iscsi_xmit_task and iscsi_complete_task
>https://patchwork.kernel.org/patch/10501773/
"
1804149,2019-01-11 02:40:58 UTC,------- Comment on attachment From <email address hidden> 2019-01-10 21:09 EDT-------
1804149,2019-01-11 02:41:01 UTC,------- Comment on attachment From <email address hidden> 2019-01-10 21:10 EDT-------
1804149,2019-03-05 16:00:33 UTC,"------- Comment From <email address hidden> 2019-03-05 10:50 EDT-------
@Canonical: Any update here. When will the test kernel via PPA be made available? Many thanks in advance"
1804149,2019-03-13 08:09:30 UTC,"Can you please give this test kernel a try:
https://kernel.ubuntu.com/~juergh/lp1804149/"
1804149,2019-03-19 11:23:16 UTC,"Can you please test the test kernel at:
https://kernel.ubuntu.com/~juergh/lp1804149/"
1804149,2019-03-15 12:47:25 UTC,------- Comment on attachment From <email address hidden> 2018-12-11 18:17 EDT-------
1804149,2019-06-24 09:16:40 UTC,After discussion with IBM this will now de-prioritized to Medium.
1804156,2019-03-08 11:28:21 UTC,@Pierre: This fully fixes the bug.
1804156,2019-02-06 00:27:38 UTC,Python 2.7? 3.5 or 3.6?
1804156,2019-02-19 03:34:10 UTC,python-novaclient: This issue is reproducible in python 2.7.
1804156,2019-02-21 12:25:42 UTC,"Fix proposed to branch: master (python-novaclient)
https://review.openstack.org/#/c/632942/"
1804156,2019-02-05 06:58:06 UTC,"In python-novaclient, if you try to list hypervisors passing --matching parameter with unicode data, then it gives KeyError."
1804156,2019-03-08 11:21:31 UTC,This fully fixes the bug.
1804156,2019-03-08 11:05:40 UTC,@Asmita: does this fully fix the bug or is some work required on Blazar as well?
1804156,2019-03-08 00:18:28 UTC,This issue was fixed in the openstack/python-novaclient 13.0.0 release.
1804156,2019-02-25 18:32:35 UTC,"Reviewed:  https://review.openstack.org/632942
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=4450e7ba3176cd26cdfa758355f8ed4ad8bacab2
Submitter: Zuul
Branch:    master"
1804160,2018-11-20 08:00:04 UTC,This change was made by a bot.
1804163,2018-11-20 08:10:24 UTC,"I edit in tools/ovs-dpdkctl.sh for fix this issue
https://review.openstack.org/#/c/618960/"
1804163,2018-11-20 07:53:34 UTC,"I think set bridge dpdk out of control of network manager. So, add below line to configuration of bridge dpdk
NM_CONTROLLED=""no"""
1804171,2018-11-23 16:16:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619763"
1804173,2018-11-26 09:23:41 UTC,This is the issue I'm talking about:
1804173,2018-11-20 13:22:39 UTC,"it seems the bug description contains at least two separate issues.
can you please consider to file separate bugs for separate issues?"
1804173,2018-11-26 07:19:28 UTC,"i'm not familiar with ""the infamous SSL handshake problem"". can you elaborate a bit? and/or maybe provide a reference?"
1804175,2018-11-21 14:17:15 UTC,@RaiMan where do I download bro? I try to download here https://raiman.github.io/SikuliX1/downloads.html but it says AttributeError: 'org.sikuli.android.ADBScreen' object has no attribute 'getScreenWithDevice'. I will donate bro if this work.
1804175,2018-11-21 14:31:40 UTC,I found it now bro. I thought I need not change sikulix.jar but only sikulixapi.jar lol.
1804175,2018-11-21 13:27:02 UTC,"I have added a solution to define an ADBScreen object for an other device than the first in the row, if more than one device/emulator is detected by ADB-support."
1804176,2018-11-20 15:30:30 UTC,You may need to run the following from a terminal:
1804179,2018-11-20 17:39:47 UTC,"So basically it seems that the touchpad gains the libinput mouse sensitivity instead, because the mouse sensitivity seem to affect the touchpad if I modify the one releated to the mouse settings when the ""issue"" occurs, no changes when you apply the workaround (re-apply the touchpad sensitivity)"
1804179,2018-11-21 13:44:47 UTC,"Also, it only happens with libinput, using synaptics+evdev is fine"
1804179,2018-11-20 18:41:58 UTC,"Not present on Manjaro KDE, so probably is a KDE upstream bug already solved but not present on the Actual version of Kubuntu"
1804179,2018-11-20 18:25:40 UTC,Only present on Kubuntu
1804183,2019-06-12 15:25:27 UTC,"This seems like a bit of an abuse of conffiles, as those files aren't really intended for user modification. It seems like this is a pretty niche use case that doesn't apply to the vast majority of users."
1804183,2019-06-12 14:40:58 UTC,"Hi,"
1804183,2019-08-12 04:17:30 UTC,[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.]
1804185,2018-11-20 11:38:38 UTC,"I see, thanks! Since http://man7.org/linux/man-pages/man2/statx.2.html has the same note, I though t it might have slipped past unnoticed. Thanks again!"
1804185,2018-11-20 11:24:05 UTC,"Upstream maintainer here. Yes, the currently released upstream manual page is out of date. But this is rectified already for the next upstream release."
1804186,2019-10-10 12:37:48 UTC,We fixed this in 2.37.
1804203,2018-11-20 11:14:32 UTC,The screenshot attached has a time log (right side) for output on terminal.
1804205,2019-06-18 12:18:14 UTC,@Wallace: please re-opend the issue if you still see this error after ./clean.sh
1804205,2018-11-22 11:10:18 UTC,"I will re-run an experiment using unstack and clean trying to isolate that. If I not observe this error again, I close this issue."
1804205,2018-11-22 10:55:25 UTC,This isn't a bug.
1804207,2019-09-01 04:17:32 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1804207,2019-07-03 02:43:54 UTC,If the main problem is getting logged out then:
1804207,2019-07-02 16:23:36 UTC,"Thank you for your bug report, it's like an xorg server or video driver issue. Could you add your 'journalctl -b 0' log after getting the issue? Do you get any error report generated when triggering the bug?"
1804207,2018-11-20 11:43:48 UTC,world.jpg
1804208,2021-02-18 12:07:14 UTC,"I had created 6 generic backends in devstack and created around 350 shares (between size 1 to 6). During share creation process, I kept checking manila service-list and found that all services were up during whole time. Then restarted m-shr service and checked service-list and again found that all services were up. Seems like I am not able to reproduce this bug for now."
1804208,2019-10-24 14:40:32 UTC,Do we have any updates on this issue?
1804208,2019-03-28 16:22:47 UTC,This bug will be discussed under the Edge PTG topic
1804208,2019-03-29 20:15:59 UTC,"Hi Maurice,"
1804208,2019-04-01 07:02:47 UTC,"Hi Lucio,"
1804208,2019-04-03 17:27:58 UTC,"Thanks for the details, Maurice."
1804208,2019-04-08 18:10:00 UTC,Seems that `_update_host_state_map` is not the only place to fix.
1804208,2019-04-08 20:52:43 UTC,"Actually, even modifying `_upodate_host_state_map` as Maurice suggested, it still shows ""Share service is down."" while creating the 500 shares:"
1804208,2019-04-08 22:07:26 UTC,"Sorry, please ignore the comments #4-#6.
It's normal to manila-share service be shown as `down` for a while until re-exporting all the shares.
If it still remains `down` after a long time after restarting, it should be another issue to be addressed in a new bug report."
1804208,2019-04-12 15:55:52 UTC,"Hello Team,"
1804208,2019-11-28 15:22:50 UTC,Not yet. Not sure if we'll be able to work on this issue during Ussuri.
1804208,2020-06-11 15:25:48 UTC,Do we have any updates on this issue?
1804208,2020-06-11 15:40:21 UTC,Additional comments  http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-06-11-15.00.log.html
1804208,2021-02-10 16:36:06 UTC,"Lucio, Naresh, Douglas,
What are exact steps of reproduction for this bug ?"
1804208,2021-02-16 12:50:17 UTC,"Hi Kiran,"
1804221,2019-09-16 08:24:22 UTC,Migrated to https://github.com/widelands/widelands/issues/3356
1804222,2018-11-20 13:34:09 UTC,"So the problem is on the Undercloud, we pull all containers from services that are in the default role:
https://github.com/openstack/tripleo-heat-templates/blob/master/roles/Undercloud.yaml#L14-L94"
1804222,2018-11-21 16:28:53 UTC,"I'm not sure the problem is CI specific, but rather that's something to be fixed in t-h-t DF"
1804222,2018-12-06 13:22:47 UTC,"Change abandoned by Thomas Herve (<email address hidden>) on branch: master
Review: https://review.openstack.org/619177"
1804222,2018-11-21 08:51:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619177"
1804239,2018-12-04 19:51:39 UTC,"Hey Maurice,"
1804239,2018-12-05 16:31:16 UTC,"Yes, the ones introduced here https://github.com/openstack/manila/commit/1ce2473f3f2657d08f90060f692f4f3516b17371"
1804239,2019-07-01 14:32:37 UTC,"Hello guys, I've found a possible scenario that may be slowing down requests in a dhss=true environment."
1804239,2020-11-17 14:13:35 UTC,"Hi Felipe and Douglas,"
1804239,2020-10-08 13:15:42 UTC,"Hi Felipe,"
1804239,2020-10-08 15:59:26 UTC,Additional comments http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-10-08-15.01.log.html
1804239,2020-10-15 12:47:02 UTC,"Thank you, Maurice."
1804239,2020-10-20 13:13:50 UTC,"Hi Felipe,"
1804239,2020-10-23 13:09:13 UTC,"Hi maurice,"
1804239,2020-11-06 17:26:45 UTC,"Hi Felipe and Maurice,"
1804239,2020-09-30 20:06:44 UTC,"Hi all,"
1804239,2019-07-02 15:41:53 UTC,"Hello Fernando,"
1804244,2018-11-20 14:43:55 UTC,As this is field-critical and as you note Juju doesn't currently support the ability to bootstrap to multiple subnets I think that the only work around atm is going to be to manually add the machines in the right subnets/zones and then enable-ha --to the machines brought up.
1804244,2018-11-20 14:30:14 UTC,marking as field critical as this is blocking the deployment on aws.
1804244,2018-11-20 14:33:12 UTC,subscribed ~field-critical
1804244,2018-11-20 14:53:45 UTC,"Actually rereading, if you're trying to bootstrap and deploy to only 3 of the 5, can we not just remove the extra subnets from the VPC?"
1804244,2018-11-20 15:03:26 UTC,"Richard,
They have to have more subnets because of vpn access to us. Also they have
plan to being more workloads on those extra subnet. It is field critical
critical if it blocks the deployment. But can we enable ha juju enable-ha
with --to parameters."
1804244,2018-11-20 15:24:22 UTC,Given that you have a workaround with the manual machines and enable-ha --to I'm going to move it from critical to field-high according to the standards in https://wiki.canonical.com/DCD/FieldSLA
1804244,2018-11-20 22:34:22 UTC,The fact that this is missing functionality in Juju this doesn't qualify for the field SLA definitions as outlined in the wiki linked above.
1804244,2018-11-21 02:08:11 UTC,can't you use
1804244,2018-11-21 06:25:54 UTC,"I have not tried syntax juju enable-ha --to subnet=b,subnet=c  i will try
that and let you know. There are five subnet in three zone and that could
be case in future deployment as well so its worth to find out what is
supported and whats not on aws. For spaces i have to bootstrap first. I
have plan to test single space multiple subnet as well."
1804245,2018-12-19 08:40:06 UTC,There are two things to consider to this:
1804245,2018-11-20 14:42:21 UTC,"The store is giving snapd the wrong reply, but snapd is then running with it."
1804245,2019-09-03 09:28:16 UTC,This was fixed in https://github.com/snapcore/snapd/pull/6400
1804253,2019-05-21 13:52:31 UTC,"Umm, was there a change posted for this? I'm not sure why it was marked as Fix Committed."
1804253,2019-05-22 10:17:56 UTC,"mhmm, the trigger from Gerrit was missing: https://review.opendev.org/#/c/660372/
Maybe it's caused by the fact, that Ops Guide uses Storyboard meanwhile instead Launchpad."
1804259,2018-11-20 16:11:00 UTC,"association proxies represent a link to another table so a simple ""order_by()"" is not so simple, and is not supported by SQLAlchemy.  if we did make it supported, it would involve ordering by a correlated subquery which would be very inefficient in any case."
1804259,2019-04-19 08:38:57 UTC,Seems to duplicated with issue: https://bugs.launchpad.net/neutron/+bug/1659175
1804259,2019-06-04 01:16:04 UTC,See the patch: https://review.opendev.org/#/c/653903/
1804261,2019-08-14 09:00:25 UTC,Could you please confirm that the 19.10 release includes a fix for this bug?
1804261,2020-06-15 16:39:58 UTC,This bug was fixed in the package ceph - 12.2.13-0ubuntu0.18.04.2
1804261,2020-09-29 16:17:47 UTC,This is still an issue with bionic-ussuri ceph 15.2.3-0ubuntu0.20.04.2~cloud0
1804261,2020-09-29 17:04:15 UTC,The bionic-ussuri package has the retries set for 10000.  My start time to vault unseal time was about 18 hours.  We should have this set to heal for up to 5 days after machine start.
1804261,2020-09-29 18:28:53 UTC,I think CEPH_VOLUME_SYSTEMD_TRIES can be set in /etc/default/ceph and then systemd units can pick the setting up from there. A charm change is being tracked at LP: #1897777. I think we can move the discussion to that bug unless there are thoughts that the upstream or package defaults should be different.
1804261,2019-03-07 08:14:42 UTC,"Once vault has been unsealed, it should be possible todo:"
1804261,2019-03-07 08:13:28 UTC,vs 10000 for vaultlocker.
1804261,2019-03-07 08:12:13 UTC,GROKing the code:
1804261,2019-03-07 07:11:20 UTC,ceph-volume systemd tasks seem to fail quicker than the 10000 second timeout configured.
1804261,2019-03-07 07:10:59 UTC,Comments #8->#10 relate to the previous linked bug; I realised these are two different issues.
1804261,2019-02-11 10:11:04 UTC,"I believe that they retry some number of times, but if it's too long of a wait, maybe they give up?"
1804261,2019-03-07 06:19:56 UTC,On my test deployment a full cloud bounce resulted in the vaultlocker and ceph-volume tasks spinning blocking boot; the design was that they should not do this and that they should background spin rather than block.
1804261,2020-06-15 06:36:35 UTC,"Just to clarify a bit to avoid confusion. In above comment, at step 5, I meant Wait for about 1.5 hour and unseal the vault."
1804261,2018-12-11 15:07:18 UTC,"OK so I reproduced - AFAICT the vaultlocker systemd unit does execute in the end, but the ceph-volume units trigger and then fail as the LVS's are not yet visible."
1804261,2018-12-11 15:01:53 UTC,I'll do another run on it soon to confirm
1804261,2018-12-11 14:39:24 UTC,Do the block devices unlock? if they do it may be a timeout on the actual ceph-volume systemd units rather than in the vaultlocker-decrypt systemd unit with retrieves the key and chats with vault.
1804261,2018-12-11 14:15:21 UTC,"I have let a deploy sit after reaching this state (ceph-osd came up before vault was unsealed) for hours, then I unsealed, and waited for more than 12 hours before giving up - the OSDs seem to reach a final timeout at some point and give up for good"
1804261,2018-11-21 06:57:41 UTC,I suspect that we're running into systemd's backoff for a failed start
1804261,2018-11-20 16:04:30 UTC,"That's definitely a bug - the systemd unit should spin until vault is unsealed, and then retrieve the keys and unlock the disks."
1804261,2019-03-07 06:26:21 UTC,The vaultlocker systemd units are of Type=oneshot which means that systemd won't consider the unit started until the subprocess completes.
1804261,2019-03-07 08:29:31 UTC,I'd suggest we just increase the number of re-tries to allow operators more time to unseal vault in the event of a full site outage.
1804261,2020-06-15 05:40:08 UTC,"I have verified the fix in bionic-proposed and confirm it can fix this issue.
The test steps I've performed:
1. deployed a ceph cluster with vault
2. upgrade some of the osds to 12.2.13
3. Add ""Environment=CEPH_VOLUME_SYSTEMD_TRIES=2000"" at /lib/systemd/system/ceph-volume@.service for all osds
4. First reboot vault, then reboot all osds
5. Wait for about 1.5 hour
6. All osds with version 12.2.13 can come up, while other osds with 12.2.12 remain blocked"
1804261,2020-06-05 05:29:39 UTC,"Hi All,"
1804261,2019-08-14 13:44:30 UTC,@janghoon: the 19.10 release will come out in October. I believe that some work may have been done to help resolve this in vaultlocker already but I'll see if I can replicate again
1804261,2019-08-14 18:20:38 UTC,"To confirm that this is still an issue as of the 19.07 charm release, I followed the below series of steps, reproduced with their results:"
1804261,2019-08-14 18:21:47 UTC,"and, because of how badly launchpad formats the plain text, https://pastebin.ubuntu.com/p/rrwkWjGwdt/ is a pastebin link, and attached is the plaintext version"
1804261,2019-12-04 11:16:27 UTC,Keying into:
1804261,2019-12-06 10:15:19 UTC,I was able to reproduce this bug. And what I've found is exactly matched with Jame's finding.
1804261,2019-12-10 12:53:45 UTC,Confirmed issue still exists with latest vaultlocker (1.0.3-0ubuntu1.18.10.1~ubuntu18.04.1) and 19.10 charms.
1804261,2019-12-10 13:59:13 UTC,"I forgot to paste the comment here.
Two ceph tracker bug issue opened and corresponding PR sent.
https://tracker.ceph.com/issues/43187
https://tracker.ceph.com/issues/43186"
1804261,2019-12-11 09:31:50 UTC,"Side note, I was initially unable to manually recover because I was restarting the wrong ceph-volume service:"
1804261,2020-03-09 10:31:35 UTC,"What is the test case for verification of this bug as part of the SRU? Since this bug is called out as being fixed by the new upload, please include the basic SRU information such as Test Case and Regression Potential. Thank you!"
1804261,2020-03-17 16:13:52 UTC,"Hello Chris, or anyone else affected,"
1804261,2020-03-30 14:37:34 UTC,"Is this bug also present in eoan? If yes, it would be good to have a fix scheduled there too."
1804261,2020-03-30 14:40:06 UTC,"Hello Chris, or anyone else affected,"
1804261,2020-04-01 07:15:45 UTC,"Hello Chris, or anyone else affected,"
1804261,2020-04-01 07:18:28 UTC,@sil2100 - yes this bug was present in the eoan version of ceph - the fix is included in the update to 14.2.8 covered under bug 1861789 so I elected not to cover it specifically under this bug.
1804261,2019-03-07 08:19:45 UTC,Scrub #15 - apparently wildcarding on that unit does not work.
1804261,2020-04-07 06:59:59 UTC,"Hello Chris, or anyone else affected,"
1804261,2020-04-07 11:57:55 UTC,"Hello Chris, or anyone else affected,"
1804261,2020-04-14 12:52:14 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1804261,2020-04-14 12:52:16 UTC,"This bug was fixed in the package ceph - 13.2.8-0ubuntu0.18.10.1~cloud0
---------------"
1804261,2020-04-14 12:53:13 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1804261,2020-04-14 12:53:15 UTC,"This bug was fixed in the package ceph - 13.2.8-0ubuntu0.19.04.1~cloud1
---------------"
1804261,2020-04-20 13:58:12 UTC,Bionic/Queens is currently blocked on a potential regression in bug 1871820
1804261,2020-06-01 07:48:20 UTC,"Hello Chris, or anyone else affected,"
1804261,2020-06-10 06:18:16 UTC,This fix need re-verification in bionic-proposed as a further change was added so the binaries have been rebuilt
1804261,2020-04-01 07:20:04 UTC,"Hello Chris, or anyone else affected,"
1804262,2019-08-27 20:07:17 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/678954"
1804262,2019-01-25 11:04:08 UTC,"On second thoughts... I think we should just delete this code right now, and stop aging backing files for swap disks. A slightly more conservative option would be to guard the whole lot in a workaround config option which defaults to off."
1804262,2019-03-05 17:32:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641093"
1804262,2019-01-25 14:05:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633213"
1804262,2019-01-25 10:26:32 UTC,"There's a slightly wider context here, which is that swap files and ephemerals shouldn't be using the image cache anyway: these should always be flat. My original imagebackend series addressed this, but of course to remove this particular code we'd also need an upgrade task, which would be fun to write :/ This is another consequence of that which I hadn't noticed before."
1804262,2019-01-24 17:32:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633042"
1804262,2019-01-24 16:11:14 UTC,I guess https://github.com/openstack/nova/blob/56811efa3583dfa3c03f9e43a9802bbe21e45bbd/nova/virt/imagecache.py#L53 was done specifically to avoid a message storm to conductor and the database:
1804262,2019-10-31 05:08:10 UTC,"Reviewed:  https://review.opendev.org/678954
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=708c11e96d01157704ba63b9b15a6e695c77ad07
Submitter: Zuul
Branch:    master"
1804262,2019-01-24 16:08:23 UTC,"Ah I see from that ""get_storage_users"" code that each compute service writes to the ""instances_path"" config option location a dict keyed by hostname to the last time that the check ran for that host. Then _run_image_cache_manager_pass will run over all of those instances across all nodes."
1804262,2019-01-24 15:49:46 UTC,Is there something holding a lock that makes this slower when on NFS? You could try getting a GMR:
1804262,2019-01-24 15:46:36 UTC,"Hi Bjoern, I saw you ask about this in the #openstack-nova IRC channel. Matthew Booth (mdbooth in IRC) is probably the person that is most familiar with the image cache manager code at this time so I would suggesting talking with him about this issue."
1804262,2018-11-20 17:35:35 UTC,Part of the problems seems to be that the image cache manager seems to run on all nodes and checking all instances:
1804262,2019-11-19 19:15:40 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/633042
Reason: This is in merge conflict now and with mdbooth's alternative https://review.opendev.org/#/c/641093/ and given the lack of urgency on resolving this (or even for the bug reporter to comment on it) I'm just going to abandon."
1804264,2019-04-01 13:53:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649032"
1804264,2018-11-21 10:22:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619196"
1804264,2019-05-02 16:26:09 UTC,"Change abandoned by Brent Eagles (<email address hidden>) on branch: master
Review: https://review.opendev.org/649032
Reason: I think this is covered through different mechanisms now."
1804264,2019-06-04 16:32:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/663092"
1804264,2019-03-19 18:22:11 UTC,"Change abandoned by Kamil Sambor (<email address hidden>) on branch: master
Review: https://review.openstack.org/619031"
1804264,2019-06-21 13:47:16 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1804264,2019-06-06 23:52:41 UTC,"Reviewed:  https://review.opendev.org/663092
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a483d0b53c8b05607082943870c5a3d852f9a622
Submitter: Zuul
Branch:    stable/rocky"
1804264,2019-06-07 16:09:06 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/663989"
1804264,2020-09-18 16:39:39 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.opendev.org/619196
Reason: https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1804264,2019-06-21 15:24:59 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1804264,2018-11-20 16:23:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619031"
1804264,2019-06-12 05:44:54 UTC,"Reviewed:  https://review.opendev.org/663989
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b2a9af00f51c28e74bedbec5d2466b4e51d1d2ba
Submitter: Zuul
Branch:    stable/queens"
1804269,2018-11-27 20:09:45 UTC,Confirmed in 3.2.1. This information is also missing when using Print Full Grid.
1804271,2018-12-15 01:10:17 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/625377"
1804271,2018-11-20 18:59:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619061"
1804271,2018-12-14 23:30:52 UTC,"Reviewed:  https://review.openstack.org/619061
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=248750578a938a1eaa2e49004302d14ab7318c5b
Submitter: Zuul
Branch:    master"
1804271,2018-12-17 17:14:15 UTC,"Reviewed:  https://review.openstack.org/625377
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=25dc6a467c641ccad5cc75f1003548af4f28b4fb
Submitter: Zuul
Branch:    stable/rocky"
1804271,2018-12-19 10:01:15 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1804271,2019-03-22 03:45:18 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1804271,2018-11-20 17:35:19 UTC,The regression is from this change which merged on November 13:
1804273,2018-12-07 00:37:53 UTC,Pin Table... might be nice too.
1804277,2018-12-09 09:35:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804280,2018-11-21 04:53:46 UTC,apport information
1804280,2018-11-20 19:49:41 UTC,Removed some identifying information from log files.
1804280,2018-11-21 04:53:44 UTC,apport information
1804280,2018-11-21 04:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804280,2018-11-21 04:53:32 UTC,apport information
1804280,2018-11-21 04:53:35 UTC,apport information
1804280,2018-11-21 04:53:36 UTC,apport information
1804280,2018-11-21 04:53:38 UTC,apport information
1804280,2018-11-21 04:53:39 UTC,apport information
1804280,2018-11-21 04:53:40 UTC,apport information
1804280,2018-11-21 04:53:41 UTC,apport information
1804280,2018-11-21 04:53:42 UTC,apport information
1804280,2018-11-21 04:53:31 UTC,apport information
1804280,2019-12-11 23:04:28 UTC,I can confirm same problem in 4.15.0-72-generic.
1804280,2018-11-21 04:53:45 UTC,apport information
1804280,2019-10-24 07:02:27 UTC,"At one point in my in-home streaming past I had to set the BSSID to my current router's IP address which resolved latency problems. I have multiple routers on my property with the same SSID, this is to provide wifi coverage to the entire property. I had to change the BSSID to the router I was using at any given time. Hopefully this is useful in some way."
1804280,2018-11-21 04:53:51 UTC,apport information
1804280,2018-11-21 04:53:52 UTC,apport information
1804280,2018-11-21 04:53:53 UTC,apport information
1804280,2018-11-21 04:53:56 UTC,apport information
1804280,2018-11-21 04:53:57 UTC,apport information
1804280,2018-11-21 04:54:03 UTC,apport information
1804280,2018-11-21 04:54:07 UTC,apport information
1804280,2018-11-21 04:54:09 UTC,apport information
1804280,2018-12-05 23:51:56 UTC,"This also occurs on wireless network connections, and *may* coincide with my USB mouse seeing lessened throughput."
1804280,2019-11-29 17:43:46 UTC,"The problem continues with 4.15.0-65-generic.  This is a ping summary coming into the affected system from another host on the same network segment with no connectivity problems, reflecting a four-minute period of recurrence (ping times were <1ms for the last 20 seconds or so, but while the problem was occurring, there was ~50% packet loss and >200ms response times for the packets that did get through):"
1804280,2019-01-14 13:14:35 UTC,Persists with 4.15.0-43-generic.
1804280,2019-01-14 16:38:16 UTC,"Possibly the same issue as bug #1666432, but I can't confirm that it occurs on the wireless interface, just Ethernet interfaces."
1804280,2019-01-16 12:32:28 UTC,Persists on a freshly reinstalled system.
1804280,2019-03-14 06:51:49 UTC,So this issue doesn't happen on v4.4 based kernel?
1804280,2019-03-14 12:28:04 UTC,"I don't have a record of which kernel I was using under xenial, but I'm
almost certain that it was 4.4-based."
1804280,2019-03-21 10:41:56 UTC,Is this same as LP: #1785171 and #1802691?
1804280,2019-03-26 18:29:03 UTC,"I have been experiencing identical issues since around mid-January or so (though my latency sometimes reaches 3000/4000+ ms during these times).  I am running a freshly installed and fully updated version of Ubuntu 18.04 Desktop.  For the first couple of months after installing 18.04 I had none of these issues whatsoever, they seemed to materialize during a period when I was doing a lot of heavy software development which used a great deal of system resources (multiple VMs). Originally the workstation was wired directly to my router, but even after purchasing a wireless USB adapter I am still experiencing the issue."
1804280,2018-11-21 04:53:49 UTC,apport information
1804280,2018-11-21 04:53:48 UTC,apport information
1804280,2019-10-24 06:47:10 UTC,"I'm also affected by this bug. I'm using Wireless AC 5ghz on an Acer Spin 5 which apparently uses the Ath10k drivers if that's relevant. Ubuntu 18.04 is the most recent version of Ubuntu that I've confirmed to not be affected by this bug. I have tested every release thereafter (18.10, 19.04, 19.10) and every one of them has the ""bouts of high latency"" bug. I wrote a more detailed description of what I experience on Ask Ubuntu: https://askubuntu.com/questions/1144521/bouts-of-high-latency-over-wifi-with-steam-in-home-streaming"
1804280,2019-03-26 18:49:31 UTC,"This could be the same issue as those other two.  Similar hardware is
involved.  I haven't had time to test changing those settings on the NIC."
1804281,2019-10-01 23:04:28 UTC,"Dear reporter, can you please check if the issue persists? I recall that we switched snapd to use the identity of the user when operating on user files. Perhaps this is fixed now?"
1804281,2018-11-20 18:20:57 UTC,"I've found that if I move /home/*/snap outside NFS and make it a symlink, refresh works. However, running the snap doesn't: ""cannot create user data directory: /home/[user]/snap/[snap_name]/[version]: Not a directory"""
1804281,2018-11-20 18:26:47 UTC,I created a workaround in https://gist.github.com/bryant1410/93474806716eeff537257518842bcff1
1804281,2019-12-01 04:17:31 UTC,[Expired for snapd because there has been no activity for 60 days.]
1804283,2018-11-20 18:29:00 UTC,When i try to do following.. no luck
1804283,2018-11-20 19:33:49 UTC,Found host passing ENV to container using lxc-attach command.
1804283,2018-11-27 16:31:13 UTC,I run into this issue as well.  I usually do this
1804283,2018-11-27 16:33:59 UTC,"A few questions for you:
- Which version of OSA do you run, or alternatively, which version of ansible do you run?
- What is the content of your bashrc/profile? Do you have anything like HOST or HOSTNAME in your environment variables?
- Could you paste the content of your /etc/hosts, please?"
1804283,2020-01-21 10:09:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/703577"
1804283,2020-02-10 18:14:12 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/706949"
1804283,2020-05-06 22:27:05 UTC,"Reviewed:  https://review.opendev.org/706949
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-rabbitmq_server/commit/?id=712e3557dfacc3863e07cce91209ed2fbb91210a
Submitter: Zuul
Branch:    stable/train"
1804283,2020-05-12 17:33:43 UTC,"Reviewed:  https://review.opendev.org/706948
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-rabbitmq_server/commit/?id=d75d33eec14a07a44c52f9375c895734253eedec
Submitter: Zuul
Branch:    stable/stein"
1804283,2020-02-10 15:18:18 UTC,"Reviewed:  https://review.opendev.org/703577
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-rabbitmq_server/commit/?id=00db9987f03c289e9904f9287dd551b08496e56e
Submitter: Zuul
Branch:    master"
1804283,2020-02-10 18:13:57 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/706948"
1804285,2018-11-28 18:49:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804285,2020-01-02 12:54:28 UTC,"My ""solution"":"
1804290,2018-11-20 20:34:48 UTC,Moving to 6.0 as it requires the new eeschema file format to store the deltas in.
1804290,2018-11-20 18:58:08 UTC,"Eeschema Symbol Properties window, showing it lacks the ability to easily turn on/off the visibility of pin names and numbers."
1804290,2018-11-20 18:57:27 UTC,"Another image. Making one of these MOSFETs show up with pin names shown (G, D, S), and the other without, required *copying* the entire symbol to make a new symbol just to change this property. That's silly. It should be easily overridden in Eeschema on a per-part basis, rather than as a fixed symbol property."
1804290,2018-11-20 21:12:31 UTC,Glad you're looking into this. Any idea on an estimate of how long version 6.0.0-rc1 might take to come out?
1804298,2019-01-11 13:34:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804308,2018-11-20 20:45:32 UTC,We should make this like the lxd code where if you've not used any spaces in the model yet we don't require you to bind endpoints. If you do have spaces work in the model then we require explicit placements to avoid guessing.
1804308,2018-11-21 02:42:11 UTC,"I do believe the same thing happens for an lxd container. Rereading this,
it sounds just that Michael would like a deploy time check of this rather
than a provisioning check.
We traditionally haven't done deploy time checks because the machines don't
exist until provisioned but for lxd/kvm:N we know the machine details."
1804308,2019-10-31 03:38:12 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1804313,2018-11-20 21:51:24 UTC,"This is on the road-map for 6.0, but requires a file format change to implement (so can't be done in a 5.x release)."
1804313,2019-01-14 12:21:00 UTC,I assume this will be handled by the new file format. Check out the mailing list discussion and the linked file format specification for more details.
1804314,2019-05-23 14:21:22 UTC,would be great if someone from Ubuntu/Canonical could triage this issue!?
1804314,2018-11-27 20:20:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804314,2018-11-27 20:25:23 UTC,"I can confirm this bug. I have a similar crypttab with only ""luks"" on the very right and I get the same warning every boot.
Unlocking the drive works without any problems. This did not happen with previous ubuntu versions."
1804314,2019-05-23 13:25:05 UTC,"It should be fairly simple to silence this warning. If cryptsetup is a script it should even be possible to find a simple workaround before an official fix is release.
The question is : which options are correct and which one should trigger a warning??
In case of a lvm, are we supposed to provide the hash, the luks and who knows which option explicitly in /etc/crypttab??"
1804314,2019-05-23 16:34:15 UTC,"The only message like this which appears in the cryptsetup source for any of cosmic, disco, and eoan is this call in debian/functions:"
1804314,2019-05-24 05:33:46 UTC,"/etc/crypttab
CryptDisk UUID=c9deed35-610e-4328-b8e7-079e95d43f76 none luks,retry=1,lvm=lvm-vg"
1804314,2019-05-24 08:53:02 UTC,"Because I followed an old and probably outdated documentation.
Should I remove the lines in /etc/default/grub and in /etc/initramfs-tools/conf.d/cryptroot completely?"
1804314,2019-05-24 16:56:47 UTC,"On Fri, May 24, 2019 at 08:53:02AM -0000, Xavier Gnata wrote:

> Because I followed an old and probably outdated documentation.
"
1804314,2019-05-24 18:25:28 UTC,Thanks!
1804314,2019-05-24 21:00:01 UTC,"Ah! I followed the same guide, as I also wanted manual disk encryption so I could dual boot and ran into the same issue."
1804314,2019-05-25 07:10:47 UTC,"I had exactly the same problem. Indeed removing the lines in the other files solved the issue!
I don't think I have followed the same guide but some other guide (don't remember which on exactly) a few years ago which roughly suggested the same."
1804314,2019-05-24 06:07:36 UTC,"Well, why are you configuring *anything* except /etc/crypttab?  It looks to me like the error is that you've duplicated the information from /etc/crypttab in different places on your system, but have not included the key 'luks' line, which means the wrong entry is copied into the initramfs because you've overridden it."
1804327,2019-04-16 08:47:47 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1804327,2018-11-21 22:32:49 UTC,"this isn't specific to DVR, right?"
1804327,2018-11-29 15:18:49 UTC,"https://review.openstack.org/#/c/618208/ was proposed, and it doesn't seem specific to DVR."
1804327,2018-12-06 14:52:09 UTC,The environment in which this was seen is with DVR routers.
1804327,2019-04-16 08:47:56 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/618208
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1804329,2021-02-25 07:45:10 UTC,"I tested for this today on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1804329,2020-03-19 05:23:51 UTC,"Lubuntu 20.04 QA-Test on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1804329,2019-11-12 07:10:52 UTC,"Lubuntu 20.04 QA-Test 2019-11-12 test on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1804329,2019-10-25 06:18:49 UTC,"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
purpose of this test is to start looking for old bugs & confirm focal impacted; these bugs are old & upstream issues and will impact very few end-users (impact me thus why chased)
boot up; adjust displays to match my setup (default-right display is below other display)
..
pcmanfm-qt when on bottom display and clicking devices (drive partitions) jumps so partially on top display, partially on bottom display - https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1804329"
1804329,2019-07-12 03:20:49 UTC,"continuation of comment #20 (still same QA-test) ...
-- from qa-test comments"
1804329,2019-07-12 02:57:29 UTC,"Lubuntu 19.10 QA-Test on hp 8200 mentioned previously
I could NOT re-create this issue today."
1804329,2019-06-08 09:36:53 UTC,"random note that may be of value, or complete red-herring"
1804329,2019-03-16 08:05:00 UTC,"QA-test Lubuntu 19.04 (daily 20190315) on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1804329,2019-02-18 01:02:28 UTC,sorry I copy/pasted too much in last comment;it mentioned screensaver issue more than it should have).  apologies.
1804329,2019-02-18 01:00:29 UTC,2019-02-17 19:30 QA-Test Lubuntu 19.04 daily (live)
1804329,2019-02-18 00:51:56 UTC,2019-02-17 19:30 QA-Test Lubuntu 19.04 daily (live)
1804329,2019-10-25 06:44:46 UTC,upstream comment (https://github.com/lxqt/lxqt/issues/1703) made..
1804329,2019-02-16 02:55:41 UTC,"QA-Test 2019-02-16 on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
// 19.04 daily x86_64
// following are selected portions copied/pasted from QA-test report."
1804329,2019-01-18 09:33:26 UTC,"still on QA-test today on same ""hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"""
1804329,2019-01-18 07:35:46 UTC,"QA-test today on same ""hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"""
1804329,2018-11-23 06:44:19 UTC,experimenting with this today; I noticed my pcmanfm-qt window is jumping on selection of a subdirectory (not just change of device/partition).
1804329,2018-11-21 00:09:23 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1804329,2018-11-20 23:41:04 UTC,"why separate - pcmanfm-qt causes a redraw sometimes (which causes window position to warp) but nother others.. i wouldn't notice this were my windows not warping to another location on screen, but it's why i'm filing this here..  if the window-warp issue is removed though - this pcmanfm-qt issue is moot anyway..."
1804329,2018-11-20 23:31:28 UTC,"sorry clicked wrong button, the last image shows it didn't always appear in the same position.  it jumped left yes, but the last comment (#5) was play as I wrote this bug-report, and the window was positioned to the right of firefox on monitor2 (bottom) before I clicked fed-dat and it moved.. in this 'warp' it only moved slighly left (thus covering part of firefox) instead of all the way to left of monitor (though it was further right before warp than most my other tests)."
1804329,2018-11-20 23:23:38 UTC,"monitor1 is top - what lubuntu see's as main (due connection no doubt)
monitor2 is bottom, where window was fully in before I clicked 'fed_dat' device/partition"
1804329,2018-11-20 23:13:19 UTC,"this was 2nd pic taken (I just didn't have picture before move), but this shows rough position before I clicked on another 'device' in pcman-fm."
1804329,2019-01-18 11:14:14 UTC,"I've linked this with pcmanfm-qt as it's mostly where I find this issue annoying me.  Still running the QA-test 'live' 19.04 daily image, and I just had Qterminal window move on me."
1804329,2019-12-12 05:40:27 UTC,"Lubuntu 20.04 QA-Test on
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1804329,2019-02-09 23:41:15 UTC,this needs a re-test; it's not doing it on my installed (& rather modified) lubuntu 19.04 system on d960 I just realized. i don't often qa-test with this box (it's usually running & where I enter comments etc) but has same [vertical] screen placement.  maybe it's related to video driver? or no longer an issue.  i need to re-test
1804333,2018-11-21 16:10:09 UTC,"I forgot to add that on the Cheese reference page...
https://developer.gnome.org/cheese/stable/cheese.html
...under ""Invocation: cheese takes a list of options as arguments: Options:"" a command line switch is documented that supposedly permits selecting the video device...
""--device=DEVICE, -d DEVICE    Use the supplied DEVICE as the video capture device.""
...but this has no effect, and even when entering a nonexistent video device (or random characters) no error message is returned; apparently this functionality is missing.
I've tried all permutations of video device, ex- ""/dev/video#"" and just ""video#"""
1804333,2019-02-02 20:47:13 UTC,Any hope of this being addressed? It makes Cheese essentially useless for multi-stream cameras because a particular stream cannot be selected.
1804333,2019-02-02 23:25:56 UTC,Thanls for the bug report & upstream reference
1804333,2019-02-03 23:18:56 UTC,Thank you!
1804333,2018-11-24 17:38:48 UTC,"Here's the problem:
https://gitlab.gnome.org/GNOME/cheese/issues/4
Cheese uses ""ID_V4L_PRODUCT"" to differentiate video devices...
My camera and others have multiple video streams which are enumerated as ""video0"" ""video1"" ""video2"" etcetera.
In all instances/streams ""ID_V4L_PRODUCT"" is the same..."
1804334,2021-02-16 11:43:41 UTC,"Thanks for this bug report. This is in my opinion more a casper (= live system) issue than an issue with the specific package providing the AppArmor profile, so I added a casper task."
1804337,2018-11-21 00:11:33 UTC,"firefox was already opened & fully displayed on monitor2 (bottom)
I entered 'ubuntu-bug' as seen in qterminal window on monitor1 (top), I selected 1 (launch firefox) and it warped/jumped my firefox window to be between screens (top on monitor1, bottom or bulk on monitor2, and now part of it off-screen)"
1804337,2018-11-21 00:16:28 UTC,i hit CTRL+ALT+T to open a terminal - this is how it opens..
1804337,2018-11-21 00:44:42 UTC,some more pictures with regards pcmanfm-qt can be seen via https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1804329
1804337,2018-11-21 01:06:02 UTC,firefox after exiting full-screen stream of some news
1804337,2018-11-21 02:00:02 UTC,probably unnecessary - but `lshw` for my d960  (my main desktop; rarely used in qa-testing)
1804337,2018-11-21 02:52:11 UTC,d960 still - ubuntu-bug opened firefox; window split across displays/monitors :(
1804337,2018-11-21 02:58:54 UTC,"firefox (qa-test still), bloomberg stream was made fullscreen on monitor2 (lower), when I ended full-screen the firefox window is part on monitor1 & part on monitor2"
1804337,2018-11-21 03:52:30 UTC,"I finished the QA-test on my d960, and rebooted to my installed 19.04, logging in with lubuntu/lxqt"
1804337,2018-11-23 06:35:38 UTC,"this session I've configured two monitors, one directly above the other."
1804337,2018-11-23 07:09:24 UTC,"if playing vids (using vlc) on top monitor0/display0 - no issues when it goes to next/prev vid
(fyi: i'm only using videos of lower-resolution than my 1920x1080 screen)"
1804337,2018-11-21 01:56:15 UTC,"subsequent QA-test on dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1804338,2018-11-21 00:21:33 UTC,"I note that the current Ubuntu version dates from 2011, which is nearly as old as me, and is slightly older than my mother."
1804341,2019-02-26 22:33:10 UTC,"My bug report description was poor; I raised multiple bugs & was rushing by the time of this one, and didn't return back as I'd intended, so apologies."
1804341,2019-02-26 10:23:01 UTC,I tested this today (26.02.29) with the build from 25.02.19 daily tests and found no problem.
1804341,2019-04-17 05:57:47 UTC,One thing I'm not clear about: does this *require* multiple displays to replicate?
1804341,2019-12-12 02:10:07 UTC,"I've been doing some testing of this on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) on a very recent QA-test install (20.04) fully upgraded."
1804341,2019-04-17 06:37:40 UTC,"Yes, and it's another that I can only replicate with vertical arrangement of displays (ie. one above the other; but if reversed it's not an issue)."
1804341,2019-10-25 05:32:42 UTC,"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
purpose of this test is to start looking for old bugs & confirm focal impacted; these bugs are old & upstream issues and will impact very few end-users (impact me thus why chased)
boot up; adjust displays to match my setup (default-right display is below other display)
moved cursor to my lower display, opened vlc from menu using keyboard; Privacy & Network Access Policy opened with window across displays -- this is not a significant issue as this window only appears first run, and it appears to depend on where cursor is when opened as to if this issue occurs, but https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1804341"
1804341,2019-12-01 10:12:52 UTC,"This bug is marked against VLC; I think it's related to a number of others that were filed upstream (LXQt said they were linked), and they have now blamed openbox as creating the issue."
1804341,2019-12-09 03:08:12 UTC,"I guess the simple solution would be to try a few other window managers to confirm that Openbox is indeed to blame. If it is, that will be pretty sad given that upstream considers Openbox to be a ""completed"" project of sorts. If we can find the fix, it would mean carrying an Ubuntu (or maybe Debian, too)-only patch."
1804341,2019-12-10 01:56:47 UTC,"Lubuntu 20.04 qa-test
I tried to re-create this issue yesterday on d780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350, portrait + landscape displays) but failed"
1804341,2019-12-10 01:56:56 UTC,"Lubuntu 20.04 qa-test
I tried to re-create this issue yesterday on d780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350, portrait + landscape displays) but failed"
1804341,2019-12-10 02:08:55 UTC,same hp8200 session as comment #11
1804341,2018-11-21 02:09:39 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1804341,2019-12-12 04:17:24 UTC,"QA-test, 20.04 daily on dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1804341,2019-12-12 02:23:15 UTC,"Okay before I shutdown the system I remembered I had to have panels on specific displays... Once I had a panel on both displays, I could re-create it on dc7700"
1804348,2018-11-22 18:53:10 UTC,"Reviewed:  https://review.openstack.org/619564
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=0a8455b0dfd07c017ed2d196c2ac73d68262c5df
Submitter: Zuul
Branch:    stable/18.11"
1804348,2018-11-21 02:39:53 UTC,the lack of python3-amqp is because in the config-changed hook:
1804348,2018-11-21 14:38:29 UTC,"Yes, so the first issue is caused by a python2 to python3 upgrade, where the script check_rabbitmq.py needs the PY3 package, but it doesn't get installed as only the charm is being upgraded.  We might need to special-case this condition."
1804348,2018-11-21 15:26:58 UTC,"Hi @xavprice,"
1804348,2018-11-21 18:48:34 UTC,@ajkavanagh thanks - I've tested the candidate and it looks good - alerts are all clear now.  Thanks for working on that!
1804348,2018-11-22 08:21:29 UTC,"@xavprice, excellent news; thanks for doing that.  I'll get the changes through gerrit and then backport to stable/18.11.  Yes, I agree, we do need to get a test (or tests) created to actually catch these errors.  These got through all of our CI and released without us knowing.  I'll raise a separate bug (against rabbitmq-server charm) to track that."
1804348,2018-11-22 11:04:38 UTC,"Reviewed:  https://review.openstack.org/619227
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=065914d696ffb39c77696925b55b9795147cae00
Submitter: Zuul
Branch:    master"
1804348,2018-11-22 13:23:04 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/619564"
1804349,2018-11-22 13:23:03 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/619564"
1804349,2018-11-21 12:30:44 UTC,"Well, that's embarrassing.  I missed that on the last bug fix.  Sadly we have no check for this; we probably need to think about how to improve it."
1804349,2018-11-21 12:33:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619227"
1804349,2018-11-22 11:04:34 UTC,"Reviewed:  https://review.openstack.org/619227
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=065914d696ffb39c77696925b55b9795147cae00
Submitter: Zuul
Branch:    master"
1804349,2018-11-22 18:53:08 UTC,"Reviewed:  https://review.openstack.org/619564
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=0a8455b0dfd07c017ed2d196c2ac73d68262c5df
Submitter: Zuul
Branch:    stable/18.11"
1804350,2018-11-21 02:37:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804353,2019-09-08 22:52:17 UTC,"""@INC contains: /usr/local/perl/lib/site_perl/5.26.2/x86_64-linux /usr/local/perl/lib/site_perl/5.26.2 /usr/local/perl/lib/5.26.2/x86_64-linux /usr/local/perl/lib/5.26.2"""
1804353,2019-09-08 22:52:36 UTC,"Sorry, I meant ""interfering with the upgrade process"" there, not ""interfering with the debugging process""."
1804354,2019-08-20 01:45:21 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1804359,2020-11-23 19:12:50 UTC,"I'm no longer sure h brings up the tutorial after installing common-non-dfsg.
The first lines displayed  after pressing h in info are:"
1804359,2019-04-03 23:05:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804359,2019-04-11 15:06:25 UTC,"Same here, Ubuntu 18.04.2 LTS, Info Version: 6.5.0.dfsg.1-2"
1804359,2020-11-23 18:59:37 UTC,"Same problem here. Ubuntu 19.10. Info 6.6.0.dfsg.1-2ubuntu2.
Following advice from https://unix.stackexchange.com/questions/588026/cannot-start-the-info-tutorial-in-debian-9-stretch I installed emacs-common-non-dfsg.
After that pressing h inside info brings up the tutorial but the command info info still results in:
info: No menu item 'info-stnd' in node '(dir)Top'"
1804362,2018-11-23 03:57:30 UTC,"Ian and I discussed this online, the above pastebin shows the offending relation at line 90 (we related a local juju-deployed openstack cloud to a remote nagios app)."
1804362,2018-11-22 10:01:42 UTC,https://pastebin.canonical.com/p/r3chFGk2Rd/
1804362,2018-11-28 07:07:31 UTC,https://github.com/juju/juju/pull/9509
1804378,2018-12-14 11:07:21 UTC,This looks like it should just worked provided the required actions are available in the node. This isn't the case when we get the nodes from the websocket. I think a backend change would be required to make this work.
1804390,2018-11-21 11:08:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619210"
1804390,2018-11-29 09:51:49 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620860"
1804390,2018-11-30 06:10:11 UTC,"Reviewed:  https://review.openstack.org/619210
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=d28495fe42ea9a940260e951b32e0a814c75ce70
Submitter: Zuul
Branch:    master"
1804390,2018-12-13 20:07:23 UTC,"Reviewed:  https://review.openstack.org/620860
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=ecef7c27c15a875f4b48440ea7c212984db88b62
Submitter: Zuul
Branch:    stable/rocky"
1804390,2019-02-19 14:50:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/637863"
1804390,2019-02-28 22:39:51 UTC,"Reviewed:  https://review.openstack.org/637863
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=f7a234a6ff414cfa52591f39d1b59d3d7dcab6e2
Submitter: Zuul
Branch:    master"
1804396,2018-11-21 09:32:44 UTC,it is a duplicate bug of https://bugs.launchpad.net/juniperopenstack/+bug/1804397
1804398,2019-10-27 21:59:08 UTC,autopkgtest is passing again with 1.4
1804398,2018-11-21 17:41:54 UTC,Upstream bug report: https://github.com/pgaudit/pgaudit/issues/62
1804398,2018-11-21 09:42:32 UTC,removed the package for now
1804400,2019-05-01 04:27:55 UTC,"@John
This does indeed looks fixed to me
Hats off to you, this is really great!"
1804400,2018-11-21 13:40:54 UTC,I also see this in the treeview on the side the library editor.
1804400,2018-11-21 11:57:33 UTC,"I see the same, at least with gkt3."
1804400,2018-11-26 00:02:11 UTC,GTK-specific?  (Doesn't reproduce on OSX.)
1804400,2018-12-11 10:59:48 UTC,"Funny, I do not see it even with GTK3. WM specific?"
1804400,2018-12-11 12:06:11 UTC,My WM is i3 (on Arch). I still see this issue on 4013f6424.
1804400,2018-12-12 17:08:08 UTC,This does not happen for me on GTK3.  I use xfce for a window manager.  Is it i3-specific?
1804400,2018-12-14 14:46:14 UTC,"If someone with i3 would like to take this on for v5.1, please update the status"
1804400,2019-01-31 01:03:53 UTC,"While annoying, it doesn't prevent proper use.  If someone has a thought for a quick fix for this issue, please re-set.  Otherwise, we should address in v6"
1804400,2019-01-31 22:05:20 UTC,"I don't really know what's going on here, but I'm not very familiar with the widget. But here is what I have found it does:"
1804400,2019-02-13 11:23:10 UTC,I have the same problem
1804400,2019-03-05 10:45:20 UTC,"This is also happening in the treeview in the symbol editor.
Something possibly interesting I noticed is the scrollbar scrolls down when as I'm typing.
If I hover over the list (while is has scrolled itself down) it will create the list from beginning at that scroll position. If I scrolls up and hover it will do the same thing again.
I have attached a video to show this behavior (In case I don't makes sense at all)
Please note the Key/mouse monitor in the top."
1804400,2019-04-02 23:45:03 UTC,The bug also happens in the *released* 5.1;  at least on Ubuntu 18.04 running Unity desktop.  It also happens in pcbnew when doing Place → Footprint and typing something to narrow-down the list of footprints:
1804400,2019-04-03 11:08:57 UTC,This might be an upstream GTK+ bug:
1804400,2019-04-03 16:45:01 UTC,"If John's assessment is correct, we cannot fix this until gtk fixes it upstream."
1804400,2019-04-27 22:53:03 UTC,"+1 here, also added a little recording as GIF, which might be easier to watch."
1804400,2019-04-28 16:18:59 UTC,<Janitor hat>
1804400,2019-04-29 01:25:49 UTC,I confirm that this corrects the issue I reported in duplicate bug https://bugs.launchpad.net/bugs/1804400.
1804400,2019-04-29 01:27:07 UTC,"I should have said ""duplicate bug 1815507"".  Regardless, the fix is good, and thanks for making it."
1804400,2019-02-21 21:44:27 UTC,"It seems to be consistent when the treeview contains both libraries and symbols. If only libraries or symbols are present, is doesnt do the update-thingy when it's hovered over"
1804401,2019-01-10 09:33:54 UTC,A possible workaround for this situation is to include the password in the accounts definition file. E.g.:
1804401,2019-10-31 03:41:58 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1804401,2018-11-26 20:30:48 UTC,"Thanks, we're investigating how we can make sure that the macaroons minted are good on each of the controllers. Typically we'd use a dns name to help with this, but understand that's not always part of the setup."
1804401,2018-11-21 13:54:51 UTC,this seems like an issue with the underlying macaroon authentication. I'll add the Candid project.
1804401,2018-11-21 13:58:14 UTC,https://github.com/CanonicalLtd/candid/issues/109
1804401,2018-11-26 13:41:59 UTC,"FWIW, candid is not being used here."
1804402,2018-11-23 10:27:31 UTC,Unity uses system-config-printer. It has lots of similar bugs when printing on network. Please remove unity and mark that as affected.
1804411,2018-11-21 13:35:45 UTC,Which version of Mixxx were you compiling? The master branch?
1804411,2018-11-21 13:58:24 UTC,"Yes, the master branch."
1804411,2018-11-24 17:41:59 UTC,"Recent changes to the build system in the master branch:
https://github.com/mixxxdj/mixxx/pull/1835
https://github.com/mixxxdj/mixxx/pull/1841"
1804411,2018-12-18 00:21:04 UTC,I also experience this same bug on master when compiling on Linux Mint 18.3 (which is based on Ubuntu 16.04 LTS).
1804411,2018-12-18 00:55:42 UTC,"I am also using Linux Mint 18.3 and I am also experiencing this bug. I tried solving it with https://github.com/mixxxdj/mixxx/pull/1926, but this is causing double -ldl in LIBS variable. :-/"
1804411,2018-12-23 13:00:53 UTC,I have the same Problem on Linux Mint 19 x64
1804411,2018-12-23 13:04:09 UTC,"I found some missing dependencies:
https://mixxx.org/wiki/doku.php/compiling_on_linux was not complete
for current master branch the following packages were not mentioned:
- libvamp-sdk2v5
- libhidapi-libusb0"
1804411,2018-12-26 03:27:18 UTC,"I came here to find a solution to this issue, then saw that a fix was committed 3 hours prior."
1804417,2018-11-21 12:27:23 UTC,"The attachment ""util-linux_2.31.1_runuser_pam.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1804417,2018-11-23 09:31:42 UTC,As a workaround we now use the following configuration as the maintainer suggested to us:
1804418,2018-11-21 11:04:31 UTC,"Contact Microsoft engineer help to debug as following, cloud you help to analyze and resolve ASAP, THX."
1804420,2018-11-23 11:07:36 UTC,This is in progress at https://review.openstack.org/#/c/619574/
1804420,2018-11-22 13:34:16 UTC,https://github.com/python/cpython/commit/af26c15110b76195e62a06d17e39176d42c0511c
1804420,2018-11-22 11:27:47 UTC,I've attached a simple script to reproduce this behaviour outside of placement.
1804420,2018-11-22 12:37:33 UTC,Is it possible that the 2.7.5 Python on CentOS has an older argparse module and that installing the one from PyPI clears the issue? If it does that ought to lend a clue.
1804422,2018-11-22 05:51:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804422,2018-11-22 08:02:01 UTC,this seems to be a gdebi bug. bad package? maybe re-installation helps
1804428,2018-11-21 11:23:31 UTC,This bug was fixed in the package osinfo-db - 0.20181120-1
1804430,2020-05-10 08:57:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804430,2018-11-21 16:23:18 UTC,"Addendum:
  * The Fedora patch(es) is/are contained in the .src.rpms which are available here: https://rpms.remirepo.net/rpmphp/zoom.php?rpm=vsftpd
  * In order to quickly view individual changes, see here: https://src.fedoraproject.org/cgit/rpms/vsftpd.git/log/"
1804430,2018-11-22 16:35:46 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1804430,2018-11-23 15:26:19 UTC,"Robie, ""Current vsftpd builds"" refers to *all* available packages atm; according to https://launchpad.net/ubuntu/+source/vsftpd, these are
  - v3.0.3-11 (Disco Dingo, Cosmic Cuttlefish)
  - v3.0.3-9build1 (Bionic Beaver)
  - v3.0.3-3ubuntu2 (Xenial Xerus)
  - v3.0.2-1ubuntu2.14.04.1 (Trusty Tahr)
  - v2.3.5-1ubuntu2 (Precise Pangolin)"
1804430,2020-05-11 12:46:24 UTC,"Yeah,
upstream releases rarely (2015 was the last) and while [1] is public the source [2] is behind some login it seems."
1804431,2018-11-21 12:27:47 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1804431,2020-12-11 19:27:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804431,2020-12-14 09:38:54 UTC,The issue is an upstream one and should probably be reported to them rather
1804432,2018-11-21 22:40:27 UTC,"Reading files from a pipe was implemented in inkscape in
  https://gitlab.com/inkscape/inkscape/commit/eaae266840146a0faa3332f253ba7bd63eecbb21
by adding ""-"" as a special input filename. (Someone should probably check if this still works after the latest rewrite of inkscape's main(), but the functionality is there in principle.)"
1804432,2018-11-21 18:06:48 UTC,"Sorry, looks like --version doesn't work yet, according to Tav on the mailing list."
1804432,2018-11-23 11:48:53 UTC,Asked the question about testing development builds in inkscape-devel https://sourceforge.net/p/inkscape/mailman/message/36475173/
1804432,2018-11-23 09:53:48 UTC,"On Wed, Nov 21, 2018 at 9:20 PM Hachmann <email address hidden> wrote:

>
> You maybe don't know that there have been made lots of changes and improvements to Inkview for the upcoming version. At least the help and --version part have been worked on, see also:
> http://wiki.inkscape.org/wiki/index.php/Release_notes/1.0#Inkview
"
1804432,2018-11-21 18:04:51 UTC,"You maybe don't know that there have been made lots of changes and improvements to Inkview for the upcoming version. At least the help and --version part have been worked on, see also:
http://wiki.inkscape.org/wiki/index.php/Release_notes/1.0#Inkview"
1804432,2018-11-21 14:20:03 UTC,Reading from stdin when '-' is used isn't implemented in Inkview.  It wouldn't be too tough to do though.
1804432,2018-11-21 14:06:09 UTC,"Reading from stdin if ""-"" is specified is what I expected, right. But there is not --help and man page doesn't list options, so I couldn't check if it is a bug or a missing feature."
1804432,2018-11-21 14:02:42 UTC,Antonio is right. I want to keep my files clean.
1804432,2018-11-21 13:29:02 UTC,"Hi Antonio,"
1804432,2018-11-21 12:47:59 UTC,I think the aim of the OP is to avoid temporary files.
1804432,2018-11-21 12:18:06 UTC,"Hi Anatoly,"
1804435,2019-01-25 15:56:38 UTC,"See https://sourceforge.net/p/mcj/tickets/37/
It's fixed in unreleased git commit cf4064e7d109aa122b372ed09b2c528006607c09"
1804435,2019-11-08 15:57:37 UTC,"I just uploaded fig2dev 3.2.7b-1 to Debian, which solves this issue."
1804435,2021-01-30 11:49:39 UTC,fixed in 3.2.7b-1 (available since groovy)
1804437,2018-11-23 07:18:36 UTC,Thanks
1804437,2018-11-21 16:08:16 UTC,"Thank you for your reply. I have now reported the bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=797392"
1804437,2018-11-21 14:29:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance."
1804441,2018-11-21 12:33:46 UTC,"Review in progress for https://review.opencontrail.org/47783
Submitter: Andrei Bunghez (<email address hidden>)"
1804442,2018-11-21 12:51:35 UTC,Thanks for the bug report!
1804442,2018-11-29 21:55:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804444,2020-05-02 00:12:52 UTC,from DpkgTerminalLog.txt:
1804444,2020-07-23 12:37:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804447,2018-11-21 14:27:36 UTC,"Thank you for your bug report, it's a known problem and there are several similar reqport like bug #1571354 or bug #1647714"
1804447,2018-11-23 16:32:03 UTC,"When reading some of the other reports, they appear to involve
installation on/to an USB-drive, not from a USB to a harddrive.
Any way, being new to ubuntu I solved it by booting from a live usb and
download / install GRUB from scratch.
Also, being new, I might not have understood the other reports proper.
But upp and rnning so alls well for me.
best regards"
1804453,2018-12-10 17:49:15 UTC,Resolved in https://review.openstack.org/#/c/624144/
1804453,2019-03-04 13:43:05 UTC,"There's a new bug related to this, and the fix described here was committed, so going to make it as such to avoid confusion."
1804453,2018-11-21 20:15:24 UTC,"This proved to be a significant issue while working on https://review.openstack.org/#/c/619248/ , a performance measuring job that uses placeload. That uses aiohttp to make concurrent connections to placement. At high concurrency _ensure_aggregate loops a great deal and causes the server to block enough that the client starts experiencing errors because it cannot make a good connection."
1804457,2018-11-21 14:02:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804458,2019-01-14 12:18:33 UTC,"A more flexible approach than simply adding yet another hardcoded default setting might be a better solution long term.
Some default field setup for example that can put the reference and value field on any layer with any default text sizes and add any number of additional text fields with any format string to any layer (again with an independent text size specification for each of them.)"
1804467,2018-11-22 01:31:34 UTC,Can you please report the issue to the developers here:
1804467,2018-11-22 09:10:45 UTC,https://gitlab.gnome.org/GNOME/mutter/issues/400
1804467,2019-04-23 20:23:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804467,2019-05-04 11:40:05 UTC,"The same bug has also been for at least 2 years present in the Linux Mint Cinnamon, which is based on Gnome."
1804473,2018-11-21 19:05:18 UTC,BTW. I'm suspecting that this one is related https://bugs.launchpad.net/netplan/+bug/1759014
1804473,2018-11-21 20:24:43 UTC,To me it seems that netplan (in combination with networkd) is not production ready.
1804476,2018-11-21 15:40:50 UTC,"Sometimes we use DHCP-AGENTS (To support SRIOV, keep that in mind when finding a solution)"
1804481,2019-06-04 09:17:46 UTC,This bug was fixed in the package linux-signed-hwe - 4.18.0-21.22~18.04.1
1804481,2019-05-22 07:49:09 UTC,This bug was fixed in the package linux-signed-hwe-edge - 5.0.0-15.16~18.04.1+signed1
1804481,2019-05-10 15:11:41 UTC,"Marking critical, as this prevents X-Gene/uboot systems from booting"
1804481,2019-02-15 11:14:19 UTC,This bug was fixed in the package linux - 4.19.0-13.14
1804481,2018-11-21 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804481,2019-02-04 16:56:44 UTC,These changes were committed after 4.19.0-12.13
1804481,2019-02-04 14:46:37 UTC,This bug was fixed in the package linux - 4.19.0-12.13
1804481,2019-02-04 14:46:32 UTC,This bug was fixed in the package linux-signed - 4.19.0-12.13
1804481,2019-02-15 11:14:16 UTC,This bug was fixed in the package linux-signed - 4.19.0-13.14
1804496,2020-01-31 12:17:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804499,2018-11-23 13:59:09 UTC,"I've removed the Invalid status while you all discuss best approaches. In my mind, the confusing aspect isn't necessarily which statuses are retargeted, but the fact that both need to be checked for Retarget All to work."
1804499,2020-01-23 21:15:27 UTC,"It would really make sense that ""Retarget Local Holds"" and ""Retarget All Statuses"" were combined into one, since they effectively serve the same purpose."
1804499,2019-04-19 16:30:38 UTC,"I wonder if it would make sense (or be possible) to automatically check the ""Retarget Local Holds"" modifier when ""Retarget All Statuses"" is checked since they must both be ON for ""Retarget All Statuses"" to work."
1804499,2018-11-23 13:31:27 UTC,"Oh I see what you mean. If you have both checked, it adds the word ""Always"" to the message in the red bar. Maybe we just need a minor wording change in both the Modifier selector and the message: Retarget Local Holds (Inprocess) and Retarget Local Holds (All Statuses). How does this sound?"
1804499,2018-11-21 19:44:25 UTC,Hi Scott!
1804499,2018-11-21 21:24:59 UTC,"OK, thanks for following up Michele! My comment was based on a misunderstanding of how this feature works."
1804499,2018-11-21 20:46:58 UTC,"Kathy,"
1804499,2018-11-23 13:24:13 UTC,"Hi Kathy,
   I appreciate the explanation and what you said makes sense. Having said that, it still would be nice, for the sake of consistency, if Retarget All Statuses could also appear in the red bar."
1804502,2020-01-16 20:00:28 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/702973"
1804502,2020-01-16 20:00:45 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/702974"
1804502,2020-01-17 16:32:48 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/703117"
1804502,2020-01-17 16:33:04 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/703118"
1804502,2020-01-17 17:49:31 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/703141"
1804502,2020-01-17 17:49:47 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/703142"
1804502,2020-01-31 15:43:43 UTC,"Reviewed:  https://review.opendev.org/702974
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8346c527b379395851a9de063b4978b489076bf6
Submitter: Zuul
Branch:    stable/stein"
1804502,2020-02-06 12:40:34 UTC,This issue was fixed in the openstack/nova 20.1.0 release.
1804502,2020-02-06 12:45:00 UTC,This issue was fixed in the openstack/nova 19.1.0 release.
1804502,2020-04-08 16:29:03 UTC,"Hey everyone,"
1804502,2020-08-18 02:30:13 UTC,"Reviewed:  https://review.opendev.org/703117
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f08d0ccf844e127f693cfc5498a205b13c873833
Submitter: Zuul
Branch:    stable/rocky"
1804502,2020-08-18 02:30:31 UTC,"Reviewed:  https://review.opendev.org/703118
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=84c63816602dcdf91885d20bb5d26cec336fb71e
Submitter: Zuul
Branch:    stable/rocky"
1804502,2019-12-23 19:28:37 UTC,"Reviewed:  https://review.opendev.org/700127
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=48bb9a9663374936221144bb6a24688128a51146
Submitter: Zuul
Branch:    stable/train"
1804502,2020-01-31 15:16:19 UTC,"Reviewed:  https://review.opendev.org/702973
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4a691c33d13611714135b9390cb53de726fc901d
Submitter: Zuul
Branch:    stable/stein"
1804502,2019-12-23 19:28:23 UTC,"Reviewed:  https://review.opendev.org/698532
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94c0362918169a1fa06aa6cf5a483e9285d7b91f
Submitter: Zuul
Branch:    stable/train"
1804502,2019-09-11 19:27:45 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/661503"
1804502,2019-12-20 09:43:03 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/700127"
1804502,2019-01-09 19:24:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/629646"
1804502,2019-01-09 19:24:48 UTC,suggested fix:  https://review.openstack.org/629646
1804502,2019-01-10 22:33:13 UTC,"as per my comment https://review.openstack.org/#/c/629646/4/nova/scheduler/filters/numa_topology_filter.py@103
we cannont skip valdiating the numa toplogy of a host on rebuild as the image can alter the guest numa toplogy."
1804502,2019-01-11 05:28:44 UTC,@sean-k-mooney the bug still exist so please don't disqualify the bug if you don't like the PR attached to it.
1804502,2019-05-26 20:14:54 UTC,"Couldn't we simply skip scheduling if the images properties remained unchanged ?  I mean, let's say I have RHEL 7.5 image with a given metadata, create a new RHEL 7.6 image containing the excat same metadata, why should we go through scheduling back again ?  This is an issue for customer lacking resources ..."
1804502,2019-05-26 21:29:18 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661503"
1804502,2019-12-20 11:42:03 UTC,"Reviewed:  https://review.opendev.org/698260
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f6060ab6b54261ff50b8068732f6e509619d713e
Submitter: Zuul
Branch:    master"
1804502,2019-05-27 14:33:44 UTC,"@inbar stoberg
i was not disqualifying it as invalid because i did not like the proposed change.
i marked it as invalid as in place rebuild for instance with a numa toplogy has never
been supported so this is a new feature not a bug."
1804502,2019-10-21 18:24:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/689861"
1804502,2019-10-21 19:48:47 UTC,please see comments on PR: https://review.opendev.org/661503
1804502,2019-12-10 12:59:09 UTC,"Reviewed:  https://review.opendev.org/689861
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3f9411071d4c1a04ab0b68fd635597bf6959c0ca
Submitter: Zuul
Branch:    master"
1804502,2019-12-10 14:28:38 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/698260"
1804502,2019-12-11 16:41:06 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/698532"
1804502,2019-09-11 19:25:25 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/629646
Reason: This looks abandoned so I'm going to abandon it. I didn't read all of the details, but ignoring this filter during rebuild if the image changes risks just pushing the failure down to the compute since we don't actually claim for rebuild in the compute which is bug 1763766."
1804508,2019-10-21 10:18:44 UTC,"Sorry ""path"" should read ""patch"""
1804508,2019-10-21 10:18:05 UTC,"Same problem for me, the provided path eliminates the problem.
Please accept the patch and release soon."
1804508,2018-11-21 19:48:43 UTC,"I'm using the attached patch on my system without issue, but it only kills direct children instead of everything in the process group. (busybox's kill doesn't support PGID at all from what I can see)"
1804508,2018-11-22 04:23:13 UTC,"The attachment ""dropbear.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1804508,2019-10-21 10:16:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804513,2019-03-29 16:48:47 UTC,"Mixxx doesn't follow a stable/unstable release process. All mixxx releases are considered stable and we recommend users always upgrade to the latest version.  Any release may introduce new bugs, but many more are also fixed.  We do offer point releases for a limited amount of time to address critical bugs, but most bugfixes are only committed to master."
1804513,2019-06-09 06:58:37 UTC,Any updates?
1804513,2019-06-02 20:00:19 UTC,Done.
1804513,2019-06-02 19:16:59 UTC,"> The issues mentioned to be caused by the 'buggy' version do seem to be high-impact, but from what I understand the application is still usable - is that correct?
"
1804513,2019-05-30 11:23:32 UTC,Thanks again for actively working on this! I'd certainly like Robie to take a look at this upload as he was the one originally involved in handling the SRU. But a few of my second-opinion cents here.
1804513,2019-04-22 08:51:58 UTC,"The cosmic package is still 2.1.3~dfsg-1
What can I do to make progress here?
@Robie Basak: can you have a look?"
1804513,2019-04-08 23:00:53 UTC,"Uploaded to the queue, it's up to the SRU team now."
1804513,2019-04-07 06:19:39 UTC,Thank you very much.
1804513,2019-04-07 04:46:48 UTC,I'll upload this on Monday.
1804513,2019-03-30 19:40:59 UTC,I have tried to improve the initial post. Is it OK like that?
1804513,2019-03-30 19:15:39 UTC,"We have a quite good experience with 2.2.0 on Linux since the release, no QT unrelated regressions."
1804513,2019-03-29 16:14:22 UTC,"Your bug description is a really good start, but I have a few more questions before we can proceed with this."
1804513,2019-03-28 22:50:56 UTC,"Hello, I was asked to take a look at this bug."
1804513,2019-03-29 13:29:53 UTC,"> Thank you Robert for you explainations. I appreciate you efforts to keep Ubuntu as stable as possible.
"
1804513,2018-11-22 20:01:32 UTC,...one more reason to not revert the migration from Qt4 to Qt5 in 2.2.0.
1804513,2019-01-18 12:51:02 UTC,"This package should be immediately updated to the latest stable release Mixxx 2.2.0
This is the first version that is stable with Qt5.
The package currently shipped with Cosmic is a untested alpha Version."
1804513,2019-01-18 13:11:17 UTC,"I have just emailed Matteo.
Is he also responsible for this bug?"
1804513,2019-02-11 16:06:38 UTC,"Ok, the Debian upstream packages are updated:
https://packages.debian.org/buster/mixxx
https://packages.debian.org/sid/mixxx"
1804513,2019-03-21 07:13:02 UTC,"Ping! This bug is still pending. Who can update the Mixxx package?
https://packages.ubuntu.com/cosmic/mixxx"
1804513,2019-03-29 14:27:50 UTC,I have update the initial post with all the requested info so far. Is anything missing?
1804513,2019-03-28 23:21:59 UTC,Thank you for taking care here.
1804513,2019-03-29 10:03:08 UTC,"We can certainly consider this _if_ the current version in Cosmic really is a problem for users that cannot practically be fixed any other way. But please could you actually demonstrate that? For the only bug actually linked, surely a cherry-pick would be lower regression risk for existing users?"
1804513,2019-03-29 10:04:39 UTC,"> Solutions would be to go to a 2.1.3 Qt4 build a 2.1.7 Qt4 build or a 2.2.0 Qt5 build.
"
1804513,2019-03-29 12:38:17 UTC,Thank you Robert for you explainations. I appreciate you efforts to keep Ubuntu as stable as possible.
1804534,2019-01-25 06:57:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804539,2018-11-22 10:15:07 UTC,"- confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
- confirmed on Windows 10, Inkscape 0.92.3 (4e01455, 2018-11-12)
- confirmed on Windows 10, Inkscape 0.92+devel (e1eae41, 2018-11-16)"
1804539,2018-11-22 15:22:23 UTC,Might be a Win10 or browser issue.
1804539,2018-11-22 20:15:45 UTC,"Indeed TylerDurden !
With Firefox (Win10 and Debian), I have the issue (the file has the ""a0:svg"" tag as you said). Downloading it with Chrome/Chromium (tested with Win10 and Debian), I can open the file."
1804539,2019-05-03 21:44:58 UTC,"- confirmed on Windows 10, Inkscape 1.0alpha (d7d7b92, 2019-05-03)"
1804540,2018-12-24 09:21:43 UTC,"Additional info:
On bionic + LDAP (where I can reproduce the bug) the ""logname"" command returns:

> logname: no login name


on 18.10 (where I cannot reproduce it) the ""logname"" command returns my username. So I don't think the problem is with dependencies, but rather some specifics of how login name is retrieved for different authentication types."
1804540,2018-12-24 09:16:50 UTC,"Can reproduce the bug on [classic] bionic where LDAP authentication is used, but on 18.10 everything works flawlessly with standard user auth."
1804541,2018-11-23 08:27:29 UTC,https://bugzilla.gnome.org/show_bug.cgi?id=717180
1804541,2018-11-23 08:28:49 UTC,and https://bugzilla.gnome.org/show_bug.cgi?id=717468  has a work-around
1804541,2019-01-23 00:26:29 UTC,From https://bugzilla.gnome.org/show_bug.cgi?id=717468:
1804542,2019-11-06 15:41:52 UTC,"The verification of the Stable Release Update for bind9 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1804542,2019-11-06 15:41:44 UTC,This bug was fixed in the package bind9 - 1:9.11.3+dfsg-1ubuntu1.10
1804542,2019-11-04 13:25:02 UTC,"I've installed the patch on a 2nd server with heavy traffic, and all run as flawlessly as with the previous patch. I think this patch totally fix the issue and it does not introduce bad behaviours (as far as I've seen)."
1804542,2019-11-04 10:33:17 UTC,"Had this problem on one of my servers (the only one running bind on Bionic), installed this proposed-update package on Thursday morning, 31st, and have not seen this error since then. Searching through my logs I saw this error appearing at least every second day - often more than once a day - and have not seen it now for more than four days!"
1804542,2019-11-03 18:17:51 UTC,"Hi,"
1804542,2019-10-31 13:14:01 UTC,"Please remember that in order for this update to be released, the tags need to be updated, as explained in comment #16."
1804542,2019-10-31 07:29:34 UTC,"Hi Łukasz,
I'm testing the proposed patch (https://launchpad.net/ubuntu/+source/bind9/1:9.11.3+dfsg-1ubuntu1.10/+build/17958751)."
1804542,2019-10-24 15:27:36 UTC,"Hello Tateru, or anyone else affected,"
1804542,2019-10-01 21:44:03 UTC,Lucas has a MP prepared at https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/bind9/+git/bind9/+merge/373431
1804542,2019-09-13 13:47:56 UTC,"Bryce, I think this can perhaps be proposed and uploaded, given the previous comments. For the actual [test] section of the sru, perhaps point at the comments above."
1804542,2019-10-24 15:27:49 UTC,"Roberto, could you re-verify if the changes fix your bug by using the packages in bionic-proposed? Thanks!"
1804542,2019-08-28 11:41:23 UTC,"Thanks for the patch!
I've installed it on a server that showed the problem and it hasn't appeared anymore.
In next days I'll apply it to another server showing the problem with more traffic, and I'll let you know the conclusions."
1804542,2018-11-22 16:40:52 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1804542,2018-12-27 14:10:20 UTC,I too am seeing this problem. This is on a computer that I'm using as a router using NAT. I have a dual stack IPv6 setup. My ISP gives me an IPv6 subnet that I use for my internal network. I have attached my configuration files.
1804542,2019-01-23 13:24:17 UTC,I do also have this problem:
1804542,2019-01-23 13:48:21 UTC,Thanks for the pointers. I agree we should try to backport this.
1804542,2019-06-04 13:32:12 UTC,"Looks like the patch that was applied is https://gitlab.isc.org/isc-projects/bind9/merge_requests/409, but it doesn't apply cleanly, so it's not an immediate candidate for the server-next queue."
1804542,2019-09-13 12:41:26 UTC,"I've tested the patch in two servers with heavy dns traffic showing the problem, and it has totally disappeared after installation. Also I haven't noticed any issue in the service after applying the patch."
1804542,2019-06-08 02:21:23 UTC,"The originally flagged patch was [2/2] of a 2-patch set (AIUI), and the second doesn't make much sense to include without the first.  The two patches also had a tiny dependence on a one tiny piece of an earlier third patch that was a smorgasbord of valgrind memcheck fixes.  Applying these three commits (and omitting their modifications to CHANGES or other files) goes cleanly:"
1804542,2019-06-08 00:11:53 UTC,"The upstream commit message is vague in explaining what was going on, but I'm gathering there was uninitialized data in a variable that would trigger the error message?  The fix appears to be switching to a static buffer and initializing it to {0}."
1804542,2019-07-18 21:47:05 UTC,Can someone help define steps to reproduce this issue?  Ideally in a vanilla install or ideally in a container.
1804542,2019-07-18 23:31:54 UTC,I've packaged the patch from comment #9 into a PPA for testing purposes:
1804543,2018-11-23 00:09:04 UTC,Hi!
1804543,2019-03-14 19:25:09 UTC,"Hello there,"
1804552,2018-11-22 16:39:41 UTC,"Only some additions - installing qt5ct is useless in LXQt. The only thing one want to install is qt5-style-plugins and switch to GTK+ if wanted. qtconfig is needed for Qt4 applications - to be honest, we as upstream don't care about Qt4 for years now - so Qt 4 problems can be considered as not LXQt releated."
1804552,2018-11-22 16:25:36 UTC,"I don't fully understand the way lxqt themes (Qt style) works.
However, the way I could get Breeze-Dark to work was to put this kdeglobals file in ~/.config"
1804552,2018-11-23 02:59:48 UTC,"@hmollercl - Thanks, Hans, for the input. What's wrong with me that I wouldn't have thought to look for a qt configuration file called 'kdeglobals'?! I've downloaded your file and will toy with it when I next visit the issue. For now, I'm all 'themed out'; it shouldn't be this difficult to swap bg/fg colors..."
1804552,2018-11-22 00:56:37 UTC,EDIT: The first line of the bug report should read:
1804552,2018-11-22 01:00:00 UTC,EDIT: The first line of the bug report should read:
1804554,2020-01-25 08:24:53 UTC,test
1804554,2020-01-25 08:24:16 UTC,I've same issue with fresh Lubuntu 19.10.
1804554,2019-06-03 13:04:45 UTC,"Thanks Ilya, for the feedback and work-around!"
1804554,2019-06-03 07:52:33 UTC,Also it's enough to set bg color in the autostart with: `xsetroot -solid black`.
1804554,2019-06-03 07:43:03 UTC,On Lubuntu 19.04 settings a wallpaper with `feh --bg-scale ~/wallpapers/foo.png` in ~/.config/openbox/autostart resolved the problem without the need to run compton.
1804554,2019-03-09 03:17:33 UTC,"I can also confirm that this happens on both an 18.10 live system and an installed system on physical hardware. I also tested a 19.04 installed system on physical hardware and it too was affected. My 18.10 install on KVM was not affected. The openbox session started as I would expect, a black background and the right click menu performed as I would expect.
I did find that on the installs that did not paint the screen correctly starting compton from the right-click menu caused the screen to begin to refresh properly."
1804554,2019-03-08 23:59:37 UTC,"Also, to be clear, it seems the problem isn't that merely selecting the Openbox session causes a problem. The problem begins when starting to log in. You end up in the Openbox session, but the SDDM screen isn't repainted and there's all sorts of weird graphics behavior."
1804554,2019-03-08 23:50:09 UTC,"Well, it's confirmed, it seems. The problem is not entirely clear. It is still bizarre it's not happening in a VM."
1804554,2019-03-08 23:03:46 UTC,Logged into my dx6120 (x86) qa-test machine
1804554,2019-01-03 01:12:07 UTC,"@Lucas: Welcome to the world of Linux... When I originally reported this bug, here[1], I also reported how to recover from it without needing to disconnect the power. For any operating system, disconnecting the power is undesirable; one of the advantages of Linux is that there is often a way to recover gracefully without losing your work and possibly damaging your file system. Unfortunately, learning all the techniques isn't easy."
1804554,2019-01-02 21:32:50 UTC,"I'm having this bug too! I can login into Lubuntu or LXQt Desktop, but when I choose Openbox in the menu the screen freezes and I have to restart the system pushing the on/off button. Btw, I'm new to Linux and I just installed Lubuntu 18.10 in an old Dell Inspiron 14 laptop."
1804554,2018-11-22 03:53:10 UTC,I've added another user and no difference. Can easily toggle between them.
1804554,2018-11-22 02:40:22 UTC,@walter:
1804554,2018-11-22 02:08:35 UTC,"I'm a little confused. You say ""logging in with that option"" does not allow you to ""select a user,"" which implies a log in step... but you're already logged in."
1804554,2019-03-04 04:18:16 UTC,[Expired for lxqt-session (Ubuntu) because there has been no activity for 60 days.]
1804554,2018-11-22 05:18:30 UTC,"@walter: The old-style log at /var/log was empty, but using the new-fangled systemd command 'journalctl -u sddm.service' gave me a pretty detailed, but ultimately useless play-back. It claims that the openbox session was successfully opened..."
1804563,2019-05-30 01:24:49 UTC,"After looking at this some more, update should allow us to modify the same fields that create is for the dnsresources endpoint."
1804563,2019-05-30 00:24:48 UTC,"I was able to update the name of the dnsresource using the cli.  The docs for this api endpoint were wrong as we should have been using ""name"" instead of ""fqdn"":"
1804563,2019-05-29 18:37:26 UTC,"Jack,"
1804563,2018-11-30 01:30:46 UTC,"I'd like to take a closer look at what you're doing here before calling this ""Triaged""."
1804563,2018-12-04 03:45:29 UTC,"Sorry for the delayed response. In short, I can't use cli to update dns resource. I believe the domain name is not very important. But I will try add 'example.com' and next update the fqdn to see whether update works."
1804568,2019-09-23 22:04:28 UTC,apport information
1804568,2019-09-23 22:04:30 UTC,apport information
1804568,2019-09-23 22:04:31 UTC,apport information
1804568,2019-09-23 22:04:33 UTC,apport information
1804568,2019-09-23 22:04:36 UTC,apport information
1804568,2019-09-23 22:04:40 UTC,apport information
1804568,2019-09-23 22:04:42 UTC,apport information
1804568,2019-09-23 22:04:44 UTC,apport information
1804568,2019-09-23 22:04:52 UTC,apport information
1804568,2019-09-23 22:05:47 UTC,apport information
1804568,2019-09-23 22:18:03 UTC,previous apport info from 19.10 ISO
1804568,2019-09-23 23:23:01 UTC,I don't think it's a Linux kernel bug.
1804568,2019-09-24 15:01:49 UTC,"Hello, if I can help you (by providing more info, etc) to fix this please let me know. Thank you in advance"
1804568,2020-02-03 16:39:34 UTC,apport information
1804568,2020-02-03 16:39:36 UTC,apport information
1804568,2020-02-03 16:39:38 UTC,apport information
1804568,2020-02-03 16:41:31 UTC,the problem is still present when ubuntu is installed from the 20.04 latest daily iso
1804568,2020-02-04 02:28:57 UTC,Thanks for testing that. Please report the bug upstream at:
1804568,2020-02-07 20:22:39 UTC,"Thanks @vanvugt, I'll do so :)"
1804568,2020-02-07 20:36:33 UTC,"https://gitlab.gnome.org/GNOME/mutter/issues/1036
let's hope they fix it"
1804568,2020-03-06 11:17:09 UTC,"I've just upgraded my 20.04 to check if the bug is still present, and it is. Can I expect it to be fixed in the 20.04 release version? Thank you in advance. (The gnome guys say it's already fixed, however I'm not sure if they are right)"
1804568,2020-03-09 12:49:48 UTC,"live installers are not affected, and installed 17.10 is not affected neither, it just worked as I expected it to work. I know that for sure."
1804568,2020-03-09 22:37:58 UTC,I figured out a workaround:
1804568,2020-05-30 01:17:16 UTC,"For me removing iio sensor not helping ...
My mouse cursor is still flipped like or your video."
1804568,2019-09-23 22:04:26 UTC,apport information
1804568,2019-09-23 22:04:24 UTC,apport information
1804568,2019-09-23 22:04:38 UTC,apport information
1804568,2019-09-23 22:04:21 UTC,apport information
1804568,2018-11-22 03:35:09 UTC,lshw
1804568,2018-11-22 18:56:49 UTC,"further explanation: https://youtu.be/ZI_qteOiB0I (250MB, 2:20)"
1804568,2018-11-22 19:00:55 UTC,17.10 isn't affected
1804568,2019-03-29 21:41:02 UTC,"hello, I hope this one gets fixed in 19.04. Also, I forgot to mention that the live installers aren't affected only the installed versions"
1804568,2019-09-23 22:04:23 UTC,apport information
1804568,2019-03-30 13:19:06 UTC,"what's ""tent"" mode?"
1804568,2019-03-30 13:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804568,2019-03-30 15:22:04 UTC,apport information
1804568,2019-03-30 15:22:05 UTC,apport information
1804568,2019-03-30 15:22:07 UTC,apport information
1804568,2019-03-30 15:22:08 UTC,apport information
1804568,2019-03-30 15:22:09 UTC,apport information
1804568,2019-03-30 00:44:08 UTC,"hi, I've just installed and fully upgraded
fcb7652dbabbbebe207f6d1c92eda29a  http://cdimage.ubuntu.com/daily-live/current/disco-desktop-amd64.iso"
1804568,2019-03-30 15:22:12 UTC,apport information
1804568,2019-03-30 15:22:10 UTC,apport information
1804568,2019-07-25 07:55:20 UTC,"I did a bios upgrade, it didn't help, issue is still present under disco dingo"
1804568,2019-03-30 15:31:46 UTC,"as requested in #8 I changed status to confirmed. thank you for the support, feel free to ask if you need any more info."
1804568,2019-03-30 15:22:24 UTC,apport information
1804568,2019-03-30 15:22:22 UTC,apport information
1804568,2019-03-30 15:24:04 UTC,(the above apport information is from the previously mentioned newly installed up-to-date disco dingo)
1804568,2019-03-30 15:22:19 UTC,apport information
1804568,2019-03-30 15:22:18 UTC,apport information
1804568,2019-03-30 15:22:16 UTC,apport information
1804568,2019-03-30 15:22:15 UTC,apport information
1804568,2019-03-30 15:22:15 UTC,apport information
1804568,2019-03-30 15:22:20 UTC,apport information
1804577,2018-11-28 05:14:39 UTC,4.20.0-042000rc4-generic
1804577,2020-02-01 19:03:59 UTC,"~esserre This is not the same bug - please report it separately (run ""ubuntu-bug linux"")."
1804577,2019-08-07 12:40:13 UTC,lshw results fwiw
1804577,2019-08-07 12:38:10 UTC,"Not sure if it is the same bug, but I have some errors related to ACPI at startup.
I experience freezes lasting around 5 seconds.
I experienced several compete freezes of the host needing a restart."
1804577,2019-08-02 10:03:29 UTC,"The same bug affects me as well.
MainBoard: Gigabyte AB350-Gaming-CF
CPU: Amd Ryzen 5 2400G
Kernel: 5.1.15-050115-generic (updated via UKUU).
lshw attached."
1804577,2018-11-28 05:30:44 UTC,"The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel.
Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/am..."
1804577,2018-11-26 18:10:46 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1804577,2018-11-22 05:27:05 UTC,dmesg
1804577,2018-11-25 08:32:58 UTC,Linux  4.18.0-11-generic #12-Ubuntu x86_64 x86_64 x86_64 GNU/Linux
1804577,2018-11-25 08:29:52 UTC,lspci
1804577,2018-11-25 08:29:22 UTC,procpuinfo
1804577,2018-11-25 07:30:06 UTC,This change was made by a bot.
1804577,2018-11-22 08:25:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1804577,2018-11-22 05:23:53 UTC,lspci info
1804577,2020-04-02 14:51:47 UTC,Done : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870368
1804577,2018-11-25 08:38:44 UTC,"More info in the bug reported early.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591"
1804584,2018-12-04 17:09:24 UTC,"Hello Sebastien, or anyone else affected,"
1804584,2018-12-01 02:54:06 UTC,This bug was fixed in the package systemd - 239-7ubuntu14
1804584,2018-11-22 17:22:49 UTC,In disco-proposed
1804584,2018-11-22 06:31:16 UTC,Note that the issue was initially mentioned on bug #1755490. We would like to see the fix backported to bionic (and probably to cosmic then by SRU team requirement).
1804589,2020-12-19 10:41:51 UTC,I've the same bug....  MOB MSI Tomahawk D450 Max and AMD Ryzen 3400G . 12/19/2020
1804589,2020-05-28 12:46:22 UTC,"Just a note, on the Dell OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.20 05/31/2019 (AGESA SummitPI-AM4 1.0.0.7a) I am only seeing the interrupt warning. Performance counters are supported there."
1804589,2020-05-28 12:38:04 UTC,It’d be great if Canonical also used their Dell and AMD contacts to get this fixed.
1804589,2020-05-28 12:37:26 UTC,"I am also seeing this with current Linux (5.7-rc7) on an MSI B350M MORTAR and a Dell OptiPlex 5055. Both are AMD Ryzen systems, so this seems to affect all of those."
1804589,2018-11-28 05:12:00 UTC,dmesg info with kernel 4.20.0-042000rc4-generic
1804589,2020-12-19 10:45:41 UTC,"Forgot the kernel version,sorry.."
1804589,2018-11-25 08:40:50 UTC,"More info in the bug reported early.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591"
1804589,2018-11-25 07:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804589,2018-11-22 08:25:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1804589,2018-11-22 06:36:15 UTC,"dmesg and lpci info attched in below post.
https://bugs.launchpad.net/ubuntu/+bug/1804577"
1804589,2018-11-26 18:11:04 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1804589,2018-11-28 05:30:10 UTC,"The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel.
Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/am..."
1804590,2018-11-26 18:12:01 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1804590,2018-11-28 06:07:24 UTC,"dmesg of kernel 4.18.0-11-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg
dmesg of kernel 4.20.0-rc4-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg"
1804590,2018-11-28 05:24:33 UTC,"The kgd2kfd_probe failed error seems gone with mainline kernel v4.20-rc4, here is the warnings during the installation.
Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module amdg..."
1804590,2018-11-28 05:20:44 UTC,4.20.0-042000rc4-generic
1804590,2018-11-25 08:39:58 UTC,"More info in the bug reported early.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591"
1804590,2018-11-25 07:30:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804590,2018-11-22 08:25:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1804590,2018-11-22 06:40:49 UTC,"dmesg and lpci info attched in below post.
https://bugs.launchpad.net/ubuntu/+bug/1804577"
1804590,2018-11-25 08:42:02 UTC,"More info in the bug reported early.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591"
1804591,2018-11-26 18:12:16 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1804591,2018-11-25 07:46:42 UTC,apport information
1804591,2018-11-25 07:54:12 UTC,dmesg
1804591,2018-11-25 08:27:57 UTC,UdevDb
1804591,2018-11-28 05:28:14 UTC,"The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel.
Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/am..."
1804591,2018-11-25 07:46:36 UTC,apport information
1804591,2018-11-28 06:07:38 UTC,"dmesg of kernel 4.18.0-11-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg
dmesg of kernel 4.20.0-rc4-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg"
1804591,2020-04-11 23:10:23 UTC,"It happened to one of mys systems this morning. The system never got past the logo for the motherboard manufacturer (AsRock). Here is the top part of dmesg down to where the failure message occurred, [code]
0.000000] kernel: Linux version 5.4.0-21-generic (buildd@lcy01-amd64-006) (gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)) #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 (Ubuntu 5.4.0-21.25-generic 5.4.27)
[    0.000000] kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgxubuntu-root ro text
[    0.000000] kernel: KERNEL supported cpus:
[    0.000000] kernel:   Intel GenuineIntel
[    0.000000] kernel:   AMD AuthenticAMD
[    0.000000] kernel:   Hygon HygonGenuine
[    0.000000] kernel:   Centaur CentaurHauls
[    0.000000] kernel:   zhaoxin   Shanghai
[    0.000000] kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
[    0.000000] kernel: BIOS-provided physical RAM map:
[    0.000000] kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
[    0.000000] kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d01fff] usable
[    0.000000] kernel: BIOS-e820: [mem 0x0000000009d02000-0x0000000009ffffff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
[    0.000000] kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20afff] ACPI NVS
[    0.000000] kernel: BIOS-e820: [mem 0x000000000a20b000-0x000000000affffff] usable
[    0.000000] kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000daaf5fff] usable
[    0.000000] kernel: BIOS-e820: [mem 0x00000000daaf6000-0x00000000dbfe7fff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x00000000dbfe8000-0x00000000dc169fff] usable
[    0.000000] kernel: BIOS-e820: [mem 0x00000000dc16a000-0x00000000dc57dfff] ACPI NVS
[    0.000000] kernel: BIOS-e820: [mem 0x00000000dc57e000-0x00000000dd0c5fff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x00000000dd0c6000-0x00000000deffffff] usable
[    0.000000] kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved
[    0.000000] kernel: BIOS-e820: [mem 0x0000000100000000-0x000000041f37ffff] usable
[    0.000000] kernel: NX (Execute Disable) protection: active
[    0.000000] kernel: SMBIOS 3.2.1 present.
[    0.000000] kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M/ac, BIOS P1.50 10/14/2019
[    0.000000] kernel: tsc: Fast TSC calibration fa..."
1804591,2020-05-28 13:15:44 UTC,This is a common problem on AMD Zen systems.
1804591,2020-05-28 14:21:21 UTC,"Thank you Paul for the pointer. I've just sent a ping in that thread..let's see how it goes.
Cheers,"
1804591,2018-11-28 05:28:34 UTC,4.20.0-042000rc4-generic
1804591,2018-11-25 07:46:40 UTC,apport information
1804591,2018-11-22 08:25:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1804591,2018-11-25 07:46:33 UTC,apport information
1804591,2018-11-25 07:46:31 UTC,apport information
1804591,2018-11-25 07:46:28 UTC,apport information
1804591,2018-11-25 07:46:27 UTC,apport information
1804591,2018-11-25 07:46:25 UTC,apport information
1804591,2018-11-25 07:46:20 UTC,apport information
1804591,2018-11-25 07:46:19 UTC,apport information
1804591,2018-11-25 07:30:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804591,2018-11-22 06:42:21 UTC,"dmesg and lpci info attched in below post.
https://bugs.launchpad.net/ubuntu/+bug/1804577"
1804591,2018-11-25 07:46:38 UTC,apport information
1804592,2018-11-28 05:21:55 UTC,"The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel.
Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/am..."
1804592,2021-01-09 21:25:16 UTC,"On ""Linux redacted-ubuntu 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux"""
1804592,2018-11-28 06:07:48 UTC,"dmesg of kernel 4.18.0-11-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg
dmesg of kernel 4.20.0-rc4-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg"
1804592,2018-11-26 18:11:48 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1804592,2020-01-08 04:33:30 UTC,<code>
1804592,2018-11-25 07:30:22 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804592,2018-11-22 08:25:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1804592,2018-11-22 06:43:15 UTC,"dmesg and lpci info attched in below post.
https://bugs.launchpad.net/ubuntu/+bug/1804577"
1804592,2018-11-25 08:42:26 UTC,"More info in the bug reported early.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591"
1804593,2018-12-22 00:06:50 UTC,If you need those newer vega firmware for your hardware you need to update linux-firmware. Best would be to get the src deb from debian sid or Ubuntu development (19.04) repo and recompile it on your system. I have not checked if it was backported.
1804593,2018-11-28 06:07:59 UTC,"dmesg of kernel 4.18.0-11-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216936/+files/4.18.0-11-generic%20dmesg
dmesg of kernel 4.20.0-rc4-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+attachment/5216937/+files/4.20-rc4%20dmesg"
1804593,2018-11-28 05:29:37 UTC,"The issue remains with mainline kernel v4.20-rc4, here is the warnings during the installation. kgd2kfd_probe failed error seems gone with the new kernel.
Processing triggers for linux-image-unsigned-4.20.0-042000rc4-generic (4.20.0-042000rc4.201811252331) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.20.0-042000rc4-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
W: Possible missing firmware /lib/firmware/amdgpu/raven2_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/raven2_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/picasso_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/am..."
1804593,2018-11-26 18:11:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1804593,2018-11-25 07:30:27 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804593,2018-11-22 08:25:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1804593,2018-11-22 06:44:15 UTC,"dmesg and lpci info attched in below post.
https://bugs.launchpad.net/ubuntu/+bug/1804577"
1804593,2018-11-25 08:42:57 UTC,"More info in the bug reported early.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591"
1804594,2019-10-09 12:13:17 UTC,Testcase fix applied to autotest-client-tests repo:
1804594,2019-10-09 09:25:41 UTC,"Reverting the changes, as I mentioned on comment #11, is not the best way to tackle it. I am working on a better solution."
1804594,2019-09-23 09:49:06 UTC,Test case #2 was added to fanotify09 as a regression test for the following upstream commit:
1804594,2019-08-27 11:26:19 UTC,Passed on X-4.15 Azure
1804594,2019-08-26 09:33:22 UTC,Passed on T-4.15 Azure
1804594,2019-08-29 09:10:32 UTC,"Test passed with generic 4.15, seems to be fixed via stable update:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=2225c33cd575efb02a0e5d7e3a6d57b2c9cb7ae4"
1804594,2019-05-31 08:42:34 UTC,Fix landed in Disco.
1804594,2018-11-22 07:00:10 UTC,This change was made by a bot.
1804594,2019-07-25 11:27:03 UTC,Cosmic EOL.
1804594,2019-01-09 04:41:19 UTC,"For the commit mentioned in this test:
   Test case #2 is a regression test for commit b469e7e47c8a"
1804594,2018-12-05 10:45:56 UTC,Could be found on Disco as well.
1804595,2018-11-25 21:08:00 UTC,"It is a typo, thanks for the bug!"
1804598,2018-11-22 21:36:13 UTC,IIUC the Mixxx installer first runs the MS Visual C++ Runtime installer if the MSVC runtime is not already installed. Was it that which didn't scale? Could you take screenshots of the parts that did not scale?
1804598,2018-11-25 07:41:56 UTC,Here is a photo.
1804600,2018-12-14 05:49:29 UTC,upstream bug: https://github.com/sosreport/sos/issues/1514
1804600,2019-07-27 02:17:22 UTC,"merged for 1
https://github.com/sosreport/sos/commit/9dc6b75f76062315c58196c51ffe9d1319988520#diff-d7d3c9ca39d610cbf8eb4c0bb5719a9f"
1804600,2020-09-23 11:59:30 UTC,"Fixed upstream in :
https://github.com/sosreport/sos/commit/9dc6b75f76062315c58196c51ffe9d1319988520"
1804600,2019-01-11 01:57:21 UTC,pull request for 1: https://github.com/sosreport/sos/pull/1523
1804608,2018-11-22 08:30:59 UTC,"@xavprice, if possible, do you have a (hopefully minimal!) bundle that includes the nrpe charms and rabbitmq-server that could be used to test the scripts?  Otherwise, if we want to hit all of the monitoring and the OpenStack charms, a bundle that includes all the monitoring relations?"
1804611,2019-02-20 21:04:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804611,2019-02-20 21:16:28 UTC,"I'm seeing the same behavior with Ubuntu 18.04.2 running in a VMware virtual machine. When networking for the VM is set to ""Host-only"", it takes two extra minutes to boot while waiting for systemd-networkd-wait-online.service to fail."
1804618,2018-11-25 09:45:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804623,2020-05-18 13:56:17 UTC,Old problem about Ubuntu 19.04. Changed status to invalid.
1804623,2018-11-23 10:27:13 UTC,"Problem does not occurred on same hardware, same partition with the new ISO: Ubuntu 19.04 ""Disco Dingo"" - Alpha amd64 (20181123)"
1804624,2018-11-22 12:45:10 UTC,thanks
1804624,2018-11-22 11:01:13 UTC,Attached a example mod file for testing. Mods are generally public domain so no copyright infringement should happen.
1804624,2018-11-22 10:19:45 UTC,"Thank you for your bug repot, could you attach a file example here or give an url to download one?"
1804626,2018-11-22 09:51:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804626,2019-04-13 04:56:29 UTC,"Hmmm, this happened to me after I tried to manually install Vagrant from source on an Ubuntu 18.04 system, and then tried to go back to the official Ubuntu Vagrant."
1804626,2019-04-13 04:58:51 UTC,"Oh, sorry, meant the command to be:"
1804630,2018-11-29 23:54:31 UTC,The panic line is actually a log message - https://github.com/juju/juju/blob/2.4/provider/openstack/provider.go#L1160.
1804630,2018-11-30 00:29:58 UTC,PR against 2.4: https://github.com/juju/juju/pull/9525
1804630,2018-12-04 01:52:31 UTC,PR for 2.5: https://github.com/juju/juju/pull/9539
1804636,2019-03-05 18:08:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804636,2019-08-20 01:45:01 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1804640,2018-11-22 15:34:05 UTC,"Hello again,"
1804640,2018-11-22 15:36:16 UTC,"> you cannot assume that Qt is built with cups support. For instance, if cups support in qtprintdialog is not enabled
"
1804640,2018-11-22 15:16:04 UTC,in the meantime here is attached the missing complementary part of the patch of the revision 2807
1804640,2018-11-22 22:49:01 UTC,"> This is not really of interest to the CUPS-specific printing code paths. If you built Qt (and on
> Gentoo via use flags also qpdfview) without CUPS support, none of this is relevant and fallback
> code paths will be used that do not consider such features at all.
"
1804640,2018-11-22 15:38:12 UTC,Actually the above patch does not like it is against revision 2087 where the current code reads:
1804640,2018-11-22 14:36:05 UTC,"ooops, I have just verified there is no way to know if the arbitrary print range field is visible in the print dialog.... It seems a missing feature of the libs :-("
1804640,2018-11-22 22:45:57 UTC,"Adam, I am sorry but I didn't apply revision 2086 too to the beta1 source distribution archive, so I needed the other patch I have posted here. The trunk code looks fine then as is :-)"
1804640,2018-11-22 13:42:04 UTC,(Trunk revision 2087 should now also hide the field using Qt 5.11.0 or later.)
1804640,2018-11-22 13:33:50 UTC,So it seems that printing to arbitrary ranges was introduced in 5.11.0 [1]:
1804640,2018-11-22 13:28:57 UTC,"Hello again,"
1804640,2018-11-22 13:09:37 UTC,(It would still be nice to find out via the Qt changelogs when support for page ranges was added to conditionally remove the additional field.)
1804640,2018-11-22 13:08:45 UTC,"I think I see the problem, while we do copy all CUPS options here:"
1804640,2018-11-22 14:07:40 UTC,It doesn't work because now printOptions.pageRanges is always empty. You should put conditional #ifdef also in source/documentview.cpp where page-ranges is overwritten.
1804640,2018-11-22 12:57:15 UTC,"Hello Fabio,"
1804642,2019-01-15 09:45:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/630916"
1804642,2019-01-04 19:50:26 UTC,"Reviewed:  https://review.openstack.org/627985
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=cabe86638b553c11bea024cea46f91667cb3da4c
Submitter: Zuul
Branch:    master"
1804642,2019-01-02 15:13:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/627985"
1804642,2019-01-02 10:53:59 UTC,"Reviewed:  https://review.openstack.org/622958
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=b508106c9b35f61b38de019acbda5fee5052bb09
Submitter: Zuul
Branch:    master"
1804642,2018-12-21 16:01:05 UTC,o/ folks wdyt http://logs.openstack.org/00/626900/1/check/openstack-tox-docs/af0c893/html/ vs https://docs.openstack.org/tripleo-docs/latest/ simple change at https://review.openstack.org/#/c/626900/ thanks
1804642,2018-12-28 08:38:54 UTC,"Reviewed:  https://review.openstack.org/626721
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=974cfb247f96eb5759cc42342cf153b2e8d58c79
Submitter: Zuul
Branch:    master"
1804642,2019-01-17 06:24:59 UTC,"Reviewed:  https://review.openstack.org/626900
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=452a0717d1b58a96816eb89fe7743f2e07a9dd17
Submitter: Zuul
Branch:    master"
1804642,2018-12-21 13:59:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/626900"
1804642,2018-12-20 20:34:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/626721"
1804642,2018-12-29 17:48:28 UTC,"Reviewed:  https://review.openstack.org/620543
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=f5cd2ce0ab117b84de6371692813cfd006926d34
Submitter: Zuul
Branch:    master"
1804642,2019-01-17 10:33:26 UTC,"Reviewed:  https://review.openstack.org/630916
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=5c434717368206bf4c4085bde21e11e62263d4e1
Submitter: Zuul
Branch:    master"
1804642,2019-01-22 08:30:04 UTC,"Reviewed:  https://review.openstack.org/632091
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=1d5e72b84e0d5c2f5c2f2fb477e39b8036e1b6ee
Submitter: Zuul
Branch:    master"
1804642,2019-01-18 14:04:23 UTC,"Reviewed:  https://review.openstack.org/631500
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=513a2fc3c91e3fc59e8fd1b32f5b5b630397b862
Submitter: Zuul
Branch:    master"
1804642,2019-01-21 13:32:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/632091"
1804642,2019-01-29 16:05:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/633771"
1804642,2019-02-01 11:44:19 UTC,"Reviewed:  https://review.openstack.org/633771
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=566efcd81e6dc77cebc69d08333bcc45e18debd8
Submitter: Zuul
Branch:    master"
1804642,2019-02-19 16:30:55 UTC,"Reviewed:  https://review.openstack.org/635881
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=ca9d24d0895f7639213557c7485b52d90bd9c901
Submitter: Zuul
Branch:    master"
1804642,2019-02-21 10:45:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638388"
1804642,2019-02-26 08:58:52 UTC,"Reviewed:  https://review.openstack.org/638388
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=5fbda50eafdb0cf98fee83a0887f6aa1bce1e62b
Submitter: Zuul
Branch:    master"
1804642,2019-03-06 09:47:03 UTC,"Reviewed:  https://review.openstack.org/640974
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=4fe6d68331668a98be030b8b8c65c0a9017eeacb
Submitter: Zuul
Branch:    master"
1804642,2019-04-04 12:14:51 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/649973"
1804642,2019-04-08 14:05:14 UTC,"Reviewed:  https://review.openstack.org/649973
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=98f9b120fb493e6749b727ab6c5d67efb48aa134
Submitter: Zuul
Branch:    master"
1804642,2021-01-07 14:40:19 UTC,closing this out
1804642,2018-12-12 16:45:11 UTC,"Reviewed:  https://review.openstack.org/624446
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=d730900e54dbcdc5c239cc6bb1daf9631d3702d3
Submitter: Zuul
Branch:    master"
1804642,2018-12-11 17:12:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624446"
1804642,2019-01-17 13:53:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/631500"
1804642,2018-12-05 13:03:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622958"
1804642,2018-11-22 12:41:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619557"
1804642,2018-11-22 13:07:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619560"
1804642,2018-11-22 13:42:47 UTC,"Since we are working on improving tripleo docs, can we restructure docs from a user point of view.
Like getting a standalone running on the system and then explain what happened in that deployment.
Something user driven scenario docs."
1804642,2018-11-22 13:46:55 UTC,Chandan; sure! Suggestions are welcome! Wanna do a proposal for that?
1804642,2018-11-23 13:21:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619733"
1804642,2018-11-24 18:57:24 UTC,"Reviewed:  https://review.openstack.org/619560
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=212d08ae6ef6db4cb0096170b24ecf6dd5d21bc1
Submitter: Zuul
Branch:    master"
1804642,2018-11-27 12:11:05 UTC,"Reviewed:  https://review.openstack.org/619733
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=54f5caaa8f078991a3fd864aec797f1fb75d1c16
Submitter: Zuul
Branch:    master"
1804642,2018-11-27 16:15:54 UTC,"Reviewed:  https://review.openstack.org/619557
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=48359b5e084e2baf895739c8faa07e7b6af58142
Submitter: Zuul
Branch:    master"
1804642,2018-11-27 16:20:09 UTC,"Here are a couple additional bugs to make some of the docs more newcomer-friendly, should people feel like poking that way as well: https://bugs.launchpad.net/tripleo/+bugs?field.tag=onboarding-docs"
1804642,2018-11-27 16:40:14 UTC,also this but wasn't picked up yet looks like https://review.openstack.org/#/c/616187/ Add simple diagram for contributor guide promotion stages
1804642,2018-11-27 18:25:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620382"
1804642,2018-12-11 15:42:31 UTC,"Reviewed:  https://review.openstack.org/616187
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=7d17b3057363073170249ba384a49672a2717a3c
Submitter: Zuul
Branch:    master"
1804642,2018-11-29 08:37:55 UTC,"Reviewed:  https://review.openstack.org/620615
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=7ba13b431066afb9ff99e0120e53138199cbf203
Submitter: Zuul
Branch:    master"
1804642,2018-11-29 11:26:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620887"
1804642,2018-11-29 13:32:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620910"
1804642,2018-11-29 14:16:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620921"
1804642,2018-11-30 07:39:56 UTC,"Reviewed:  https://review.openstack.org/620887
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=938a5732edcd14e45a86a579bdf69d2d8065ee79
Submitter: Zuul
Branch:    master"
1804642,2018-12-03 08:18:36 UTC,"Reviewed:  https://review.openstack.org/620910
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=d45285d21f65e1cda241959d1c90ee1b4bc0bbbd
Submitter: Zuul
Branch:    master"
1804642,2018-12-03 16:02:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621618"
1804642,2018-12-03 18:02:43 UTC,"Reviewed:  https://review.openstack.org/620382
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=5dba662cc2267b13e3eaf68cd530d8261140402c
Submitter: Zuul
Branch:    master"
1804642,2018-12-04 15:55:48 UTC,"Reviewed:  https://review.openstack.org/621618
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=699383c357d450344cbfb1514135814d38bbcc7d
Submitter: Zuul
Branch:    master"
1804642,2018-12-05 09:14:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622901"
1804642,2018-12-05 11:58:40 UTC,"Reviewed:  https://review.openstack.org/622901
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=b24a547c09ba142449da773a6107c15300ac6069
Submitter: Zuul
Branch:    master"
1804642,2018-11-28 14:51:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620615"
1804652,2020-03-03 02:18:58 UTC,"Reviewed:  https://review.opendev.org/619622
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9c0d188988eb86f9186bca98e544ba15105072e8
Submitter: Zuul
Branch:    master"
1804652,2018-11-29 09:49:30 UTC,https://review.openstack.org/619622
1804652,2018-11-29 09:32:49 UTC,"Incidentally this race isn't theoretical: see the BZ linked in comment 1. We're currently hitting this reliably on install in a script which runs on all controllers to wait for the schema to be loaded before continuing. We're also working on another workaround in the installer, but this remains a thing."
1804652,2018-11-29 09:26:39 UTC,Just noticed I hadn't tagged the patch I knocked up with this bug.
1804652,2018-11-28 21:22:45 UTC,"Not really sure what you would expect nova to do with this, it's handling the case that the migrate_version table doesn't exist (no schema) and puts the db under version control if not, and as noted in the bz it can race fail if 2 workers are doing that concurrently. I guess you want to handle db_version_control failing with:"
1804652,2018-11-22 14:05:45 UTC,See https://bugzilla.redhat.com/show_bug.cgi?id=1652287
1804657,2018-11-22 15:12:03 UTC,Note: on a default Ubuntu install there's no font to render Old Hungarian. I downloaded the font from https://github.com/OldHungarian/old-hungarian-font and unpacked the ttf file in ~/.fonts/ to get the document to render as intended.
1804657,2018-11-29 12:58:07 UTC,"Today I installed the snap in the candidate channel (6.1.3.2, revision 93). The problem appears to be fixed. Thanks for your help in testing!"
1804662,2018-11-22 14:10:20 UTC,"This happened with base-3.15.5 and cagateway-2.1.0.0, the OS is Debian-8.9."
1804662,2018-11-22 15:44:28 UTC,"Unless you're using name resolution on TCP (EPICS_CA_NAME_SERVERS), the code in casDGClient.cc applies (DG = datagram)."
1804662,2018-11-28 16:10:48 UTC,I should add that all gateways (more than 30 IIRC) issued the same message to the log at exactly the same time.
1804662,2018-11-28 17:44:24 UTC,"@Ralph if one of those errors actually comes from TCP name resolution, it might be a good idea to change the message to be ""unterminated PV name in TCP search request""."
1804662,2018-11-29 16:46:59 UTC,Thanks for the pointers. Interesting projects but not what I need to reproduce this problem.
1804662,2018-11-30 16:22:58 UTC,@Andrew: misleading error message fixed in 3.15 and pcas module.
1804668,2019-01-14 12:14:07 UTC,"For this to replace the current check workflow there would also need to be much better dimensioning tools. (We would at least need a way to restrict dimensions to vertical/horizontal/45°, snap to pad corners (or sides), snap to centers (for both pads and lines) Maybe also symetry help line. In other words a full dimensioning toolchain.)"
1804681,2020-01-31 07:30:56 UTC,Note: meanwhile CRITICAL has been changed to WARNING in the product but the bug is still valid.
1804687,2018-11-23 19:39:14 UTC,Issue with build dependency detection. Assigning to the build team.
1804687,2019-01-03 21:03:05 UTC,The issue here is with $MY_REPO/cgcs-tis-repo/dependancy-cache.
1804687,2019-01-21 21:39:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632166"
1804687,2019-02-01 23:23:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634513"
1804687,2019-05-30 19:27:16 UTC,"Reviewed:  https://review.opendev.org/634513
Committed: https://git.openstack.org/cgit/starlingx/root/commit/?id=e9bbaaf8a0dce05a8fe3c27c9f43d2208d11f36d
Submitter: Zuul
Branch:    master"
1804688,2018-10-21 22:27:39 UTC,"Tor Lillqvist committed a patch related to this issue.
It has been pushed to ""libreoffice-6-1-3"":"
1804688,2018-11-02 18:03:17 UTC,*** Bug 121093 has been marked as a duplicate of this bug. ***
1804688,2018-11-22 18:28:17 UTC,The .crash
1804688,2018-11-22 18:28:53 UTC,The sample
1804688,2018-11-30 18:23:27 UTC,*** Bug 120942 has been marked as a duplicate of this bug. ***
1804688,2018-11-23 08:37:03 UTC,Thanks for the report.
1804688,2018-11-23 20:27:15 UTC,"I ran it as root, I got permission errors as a regular user.
It still crashed though."
1804688,2018-11-26 21:24:14 UTC,"This is an upstream crash (https://bugs.documentfoundation.org/show_bug.cgi?id=118416), which was fixed in 6.1.3, which will soon be SRU’d to cosmic (see bug #1803142)."
1804688,2018-10-18 13:03:44 UTC,"We are using Libreoffice calc 6.0.6 in Manjaro. If we close the clipman, we don't get the error."
1804688,2018-11-22 18:31:36 UTC,The files were attached so look at the attachments.
1804688,2018-10-17 19:46:43 UTC,"Tor Lillqvist committed a patch related to this issue.
It has been pushed to ""libreoffice-6-1"":"
1804688,2018-07-16 19:36:31 UTC,"Tor Lillqvist committed a patch related to this issue.
It has been pushed to ""master"":"
1804688,2018-10-15 14:19:15 UTC,"Hi Tor, Eike,
the fix for this issue also fixes bug 120616, which is a crash.
Any chance the commit could be backported to 6.1? Gerrit's cherry-pick prompts a merge conflict"
1804688,2018-10-15 14:14:56 UTC,*** Bug 120616 has been marked as a duplicate of this bug. ***
1804688,2018-08-16 08:22:44 UTC,"A polite ping to Tor Lillqvist:
Is this bug fixed? if so, could you please close it as RESOLVED FIXED ? Otherwise, Could you please explain what's missing?
Thanks"
1804688,2018-06-28 06:47:43 UTC,"And if I copy just a few cells and quit LO, and then run:"
1804688,2018-06-28 06:44:07 UTC,"Using the xclip command to list what ""targets"" (formats?) are available on the X11 clipboard after quitting LO (this time running it ""normally"", not under gdb):"
1804688,2018-06-27 22:10:23 UTC,No problem with
1804688,2018-06-27 15:45:45 UTC,"Not sure why I don't get any message from the shell when running soffice and doing the same thing that the process would have been killed by that SEGV. Does cairo actually catch it? Anyway, even if it does, surely what the code tries to do is insane?"
1804688,2018-06-27 15:13:00 UTC,Related to bug #69460. No idea why this issue hasn't come up more often?
1804688,2018-06-27 15:11:07 UTC,"Description:
In a developer build, with --enable-debug:"
1804688,2018-10-17 10:07:30 UTC,*** Bug 120616 has been marked as a duplicate of this bug. ***
1804688,2018-06-28 06:32:39 UTC,"When you say ""no problem"", you mean that you did not get the SEGV when running LO under gdb, after first selecting an entire column and then attempting to quit LO?"
1804692,2018-11-23 10:38:02 UTC,"I just tried to bind resize_up, resize_down, resize_left and resize_right with other keys and it actually resizes the split windows well. I tried several key combinations and only those that are already used by Ubuntu do not work as expected. So are Ctrl+Shift+arrow now being used by something in Ubuntu 18.10 ?"
1804693,2018-11-27 09:26:54 UTC,"Ok, weird that gvfs works but nautilus not, those usually rely on the same underlining libraries. Could be worth reporting upstream also on https://gitlab.gnome.org/GNOME/nautilus/issues/"
1804693,2018-11-22 21:40:13 UTC,Thank you for your bug report. Could you give some details on how you configure/use libpam-mount and what sort of mounts you are doing with it? Can you copy files with cp or gvfs-copy without issue or do they have the same bug?
1804693,2018-11-26 18:32:50 UTC,"Hello,"
1804700,2018-11-26 22:01:32 UTC,I think bootstrap is handling this case properly. The keystone-manage bootstrap command needs to have a password to bootstrap with the administrator. It doesn't look like it was provided.
1804700,2018-11-28 12:04:11 UTC,"bootstrap is doing the right thing by requiring a password, but it's not acceptable to be emitting a traceback. The error message ""Either --bootstrap-password argument or OS_BOOTSTRAP_PASSWORD must be set."" and an appropriate exit code is correct, causing a traceback is not."
1804700,2019-01-28 17:48:18 UTC,"Currently, 1 is returned as the error code [0]. Do you think we should be returning something else?"
1804700,2019-05-20 20:22:43 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660203"
1804700,2019-05-29 13:01:11 UTC,"Reviewed:  https://review.opendev.org/660203
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=295b07cc76c8387adc2fd9a8f3efb769f260ff02
Submitter: Zuul
Branch:    master"
1804700,2019-09-27 09:10:51 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1804708,2019-01-25 21:23:21 UTC,Confirmed as well on ubuntu disco 19.04 pastebinit v1.5
1804709,2018-11-23 06:23:46 UTC,"Thank you for your bug report, screensaver != screenshot, I'm reassigning to the right component."
1804709,2019-08-27 13:13:41 UTC,This bug was fixed in the package gnome-screensaver - 3.6.1-8ubuntu3.2
1804710,2019-08-27 13:13:41 UTC,This bug was fixed in the package gnome-screensaver - 3.6.1-8ubuntu3.2
1804710,2018-11-23 06:26:11 UTC,"That doesn't have to do with the screenshoter, reassigning"
1804717,2018-11-23 00:02:14 UTC,I forgot to mention that the saturation of the NVRAM causes a considerable slowdown of the computer at startup.
1804721,2018-11-23 03:45:12 UTC,"I'm not asserting that my .yaml source is correct, just that a more specific/informative error handler should have been invoked."
1804721,2019-01-24 21:44:05 UTC,"Yes, absolutely. In fact, I fixed this already:"
1804721,2019-01-24 21:57:03 UTC,Thanks Mathieu. Looking forward to the fix being released into Bionic.
1804727,2018-11-23 23:46:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804727,2018-11-23 01:24:17 UTC,"My version is Ubuntu 18.04,1 LTS."
1804733,2018-12-25 06:54:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804739,2020-05-29 20:46:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804742,2019-01-08 19:15:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804762,2018-12-05 08:18:29 UTC,"Ok, I got it."
1804762,2018-12-05 06:50:53 UTC,Hi!
1804762,2018-12-04 21:04:44 UTC,"Hi,"
1804762,2018-12-05 05:12:29 UTC,Hi!
1804767,2019-08-20 01:44:45 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1804775,2018-11-23 08:56:26 UTC,https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/434492/
1804778,2018-11-23 09:22:04 UTC,https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/434492/
1804778,2018-11-23 09:24:29 UTC,Should be: https://review.gerrithub.io/#/c/mfcloud/python-zvm-sdk/+/434503/
1804779,2020-08-09 23:24:18 UTC,"openvas9-gsa 7.0.3-1xenial2
openvas9-cli 1.4.5-1xenial"
1804786,2019-05-20 02:15:31 UTC,"Comment #6 only demonstrates a nouveau bug. That is bug 1553328, or https://bugs.freedesktop.org/show_bug.cgi?id=92438 whereby nouveau is not thread safe. It's a very old issue so if you experience that my best advice is to just avoid nouveau."
1804786,2019-05-27 02:32:41 UTC,"@Daniel,"
1804786,2019-05-25 07:58:21 UTC,"I have 3 computers running Ubuntu desktop edition:
An old HP LapTop, 19.04;
An old Apple iMac, 18.04;
And a VM, 18.04, running on my main Ubuntu 16.04 test server.
All 3 have the issues, with one main difference in the 19.04 verses 18.04 ""play again"" stimulus response."
1804786,2019-05-25 21:04:11 UTC,"The VM that I revived had not been run or updated since an early development version of 18.04, and it worked fine for playing the help videos. When I updated it, the yelp package did not update, but webkit did:"
1804786,2019-05-27 05:50:41 UTC,@Daniel:
1804786,2019-05-14 13:37:15 UTC,"While the bug is annoying it's not a core feature/blocking work, we should fix it but it's not going to tracked as rls issue"
1804786,2019-05-27 15:13:44 UTC,"On 2019.05.26 19:18 Daniel van Vugt wrote:

> This bug might be getting confused...
"
1804786,2019-05-28 03:57:55 UTC,"@Doug,"
1804786,2019-05-28 04:49:43 UTC,@hugh: Looks like you forgot to attach the file.
1804786,2019-05-28 04:55:24 UTC,"@Sebastien: Yeah, the lack of duplicates is a fact. It may indicate that relatively few users are affected by the problem, or that few users read docs on disk..."
1804786,2019-05-28 05:02:46 UTC,sorry I forgot to attach the file...
1804786,2019-05-19 15:44:05 UTC,@Gunnar asked:
1804786,2019-05-27 11:28:19 UTC,"@Gunnar, one way to look at it is that the issue has one report, not a lot of activity and no duplicate which hints it's low importance (or that the users who have issues with don't know how to reach out to us)"
1804786,2019-05-17 18:41:57 UTC,Bug #1499419 and bug #1553328 seem kind of related.
1804786,2018-11-23 16:10:16 UTC,On my desktop 18.04 computer this happens for all the videos that I have tried (3 of the 5 so far).
1804786,2019-05-17 16:44:16 UTC,"I revived an old LapTop, that had Desktop 18.04 on it. Updated to current 18.04.
Verified that this video issue was present.
Upgraded the computer to 18.10.
Ran one help video about 15 times without any issues.
Upgraded the computer to 19.04.
Ran the video only 2 times before it messed up. It messed up every time thereafter."
1804786,2018-11-23 09:10:27 UTC,upload video which this issue was happening
1804786,2019-05-17 18:27:42 UTC,@Doug: Are you using Nouveau or some other graphics driver?
1804786,2018-11-23 14:51:21 UTC,Same problem in the current development version (disco).
1804786,2018-11-23 15:27:21 UTC,"Terminal output when attempting to run the ""Launch applications"" video in disco:"
1804786,2018-11-23 16:12:48 UTC,"@Gunnar: I do see ""WebKitWebProcess"" using the most CPU during video play."
1804786,2018-11-23 12:08:25 UTC,Thanks for your report! I can't even play it once. :(
1804786,2019-04-05 16:10:09 UTC,"Also something like this, not sure if those indicating some errors as well
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color"
1804786,2019-05-01 04:32:57 UTC,The problem seems not to be Ubuntu specific.
1804786,2019-05-11 15:42:10 UTC,"I think this bug needs attention by the desktop team, so I added the rls-ee-incoming tag. If this cannot be fixed, we should consider to drop gnome-getting-started-docs from the seed."
1804786,2019-05-16 15:48:55 UTC,Using disco the videos play fine here so it's not impacting every config
1804786,2019-05-16 16:23:08 UTC,"On 2019-05-16 17:48, Sebastien Bacher wrote:

> Using disco the videos play fine here
"
1804786,2019-04-05 16:04:51 UTC,"Description of problem:
I am getting those messages while running yelp in 7.7, I am not seeing them on RHEL-8 with X session"
1804795,2018-12-04 10:44:59 UTC,This bug was fixed in the package openvswitch - 2.10.1-0ubuntu2
1804804,2019-03-21 00:00:17 UTC,apport information
1804804,2019-03-21 00:00:18 UTC,apport information
1804804,2019-03-21 00:00:20 UTC,apport information
1804804,2019-03-21 00:00:22 UTC,apport information
1804804,2019-03-21 00:00:28 UTC,apport information
1804804,2019-03-21 00:00:26 UTC,apport information
1804804,2019-03-21 00:03:10 UTC,"Currently experiencing this problem in disco on an Acer One 10 S1003. screen is by default in portrait, which makes using the keyboard attachment a little painful.
For default landscape mode, I manually set:
xinput set-prop 13 ""Coordinate Transformation Matrix""  0 1 0 -1 0 1 0 0 1
and try to keep it in landscape mode by default. It'd be nice if this would automatically change when the screen rotated."
1804804,2019-03-21 00:00:16 UTC,apport information
1804804,2019-03-21 00:00:24 UTC,apport information
1804804,2019-03-21 00:00:13 UTC,apport information
1804804,2019-03-28 21:43:37 UTC,Also experiencing same problem on a Dell Inspiron 3168. Seems as though what should be handled by iio-sensor-proxy is not being handled for the input part of the touchscreen.
1804804,2019-03-21 00:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804804,2019-03-21 00:00:09 UTC,apport information
1804804,2019-03-21 00:00:07 UTC,apport information
1804804,2019-03-21 00:00:03 UTC,apport information
1804804,2019-03-21 00:00:01 UTC,apport information
1804804,2019-03-20 23:59:59 UTC,"ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  ashley     1774 F.... pulseaudio
 /dev/snd/controlC0:  ashley     1774 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 06cb:73f5 Synaptics, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer One S1003
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=fcaaf731-6ab3-4df3-80a7-52e36a5bc770 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-7-generic N/A
 linux-backports-modules-5.0.0-7-generic  N/A
 linux-firmware                           1.178
Tags:  disco
Uname: Linux 5.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/20/2018
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.19
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: One S1003
dmi.board.vendor: Acer
dmi.board.version: V1.19
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 32
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.19:bd03/20/2018:svnAcer:pnOneS1003:pvrV1.19:rvnAcer:rnOneS1003:rvrV1.19:cvnAcer:ct32:cvrChassisVersion:
dmi.product.family: CHT-CR
dmi.product.name: One S1003
dmi.product.sku: S1003_1025112B_1.19
dmi.product.version: V1.19
dmi.sys.vendor: Acer"
1804804,2019-02-12 04:17:55 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1804804,2018-12-14 01:53:33 UTC,Confirmed in LP: #1807250 and LP: #1792813̈́
1804804,2018-11-26 17:55:43 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1804804,2018-11-23 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1804804,2019-03-21 00:00:11 UTC,apport information
1804807,2018-11-26 11:09:09 UTC,"--- Java
In any case you should upgrade to the LTS version 11 (10 is out of service since September)."
1804807,2018-11-23 12:24:17 UTC,Apparently a problem with the grey overlay frame.
1804807,2018-11-26 10:15:12 UTC,Hi.
1804809,2019-07-18 22:23:43 UTC,Thanks for filing the issue.
1804810,2018-11-23 12:24:49 UTC,"Can you provide a bit more information about the machine you're installing on here? Architecture, specs, etc."
1804810,2018-11-23 13:24:21 UTC,"These are intel Dell PowerEdge R740, I can provide the full specs through internal
channels."
1804810,2018-11-23 14:10:23 UTC,Hummm... interesting:
1804810,2018-11-23 14:12:37 UTC,"on a node where I didn run the connect command manually,
that value doesn't turn up:"
1804810,2018-11-24 09:44:38 UTC,"Testing on a KVM instance, x86_64 architecture:"
1804810,2018-11-25 11:41:46 UTC,And since the original report mentioned a proxied setup:
1804810,2020-03-02 23:54:21 UTC,"Closing this ticket, due to lack of any followup"
1804811,2018-11-23 12:06:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/619723"
1804811,2020-05-22 20:35:44 UTC,"Reviewed:  https://review.opendev.org/619723
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cf74d2403272d37e011911b4bd9ffb5f1d8f3b9b
Submitter: Zuul
Branch:    master"
1804818,2018-12-08 02:09:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804825,2018-11-23 23:55:04 UTC,*** This is an automated message ***
1804844,2019-05-29 20:20:08 UTC,"Reviewed:  https://review.opendev.org/644526
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=9f78072ccc5eb0472a812a46c84ce433f93e68f5
Submitter: Zuul
Branch:    master"
1804844,2019-05-25 03:03:41 UTC,"Reviewed:  https://review.opendev.org/647931
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9f857631d8df2ae5c3d0e89d95958e1636e8e494
Submitter: Zuul
Branch:    master"
1804844,2019-03-26 21:32:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/647931"
1804844,2019-03-19 18:52:24 UTC,"Reviewed:  https://review.openstack.org/643389
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6ef6f2b59be09baa5663126b49fbdce27c4798d6
Submitter: Zuul
Branch:    master"
1804844,2019-03-19 09:47:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/644526"
1804844,2019-03-16 09:15:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/643702"
1804844,2019-03-14 16:25:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/643389"
1804844,2019-03-13 23:25:32 UTC,"Reviewed:  https://review.openstack.org/619742
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=33110fb7e87a57cda947da20926d8dd9912c19d4
Submitter: Zuul
Branch:    master"
1804844,2019-03-23 19:54:47 UTC,"Reviewed:  https://review.openstack.org/643702
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=303598289ddf56a9b4223487b4f8f382ccb350c4
Submitter: Zuul
Branch:    master"
1804844,2019-01-30 15:38:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/633979"
1804844,2019-01-18 10:40:30 UTC,"Reviewed:  https://review.openstack.org/627806
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=eacdf1f18fbd819ba737b11309f48278092a8798
Submitter: Zuul
Branch:    master"
1804844,2019-01-10 01:58:16 UTC,"Reviewed:  https://review.openstack.org/627053
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7ae764eff9fd4490b5b4e4d215e6bd647e3cd76a
Submitter: Zuul
Branch:    master"
1804844,2019-01-04 04:29:40 UTC,"Reviewed:  https://review.openstack.org/628145
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1f3e5f91f660b527013c0233d5cd20484edb72f7
Submitter: Zuul
Branch:    master"
1804844,2019-01-03 10:39:30 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/628145"
1804844,2019-01-02 11:00:22 UTC,neutron-tempest-iptables_hybrid job migrated with patch https://review.openstack.org/#/c/627168/
1804844,2018-11-23 14:54:03 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/619742"
1804844,2019-03-13 20:39:18 UTC,"Reviewed:  https://review.openstack.org/633979
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b3d26ab2dd51ec4dbe446564308a8ae95105f22e
Submitter: Zuul
Branch:    master"
1804845,2019-04-09 02:08:53 UTC,Another way.
1804865,2019-08-20 15:35:39 UTC,This bug was fixed in the package scite - 4.0.0-1ubuntu0.1
1804865,2019-08-19 12:26:35 UTC,"Alright, I should mention versions too: error in 4.0.0-1, and working fix in 4.0.0-1ubuntu0.1."
1804865,2019-08-19 12:03:07 UTC,"Alright, Installed the package from bionic-proposed in a clean virtual machine, and tested the package. The fix works."
1804865,2019-08-19 11:40:00 UTC,It's absolutely right to verify your own changes.
1804865,2019-07-08 10:27:32 UTC,"Please someone perform a SRU verification of this, so we finally can get this into Bionic. (I would do it myself if I could, but it doesn't seem right to verify my own changes)."
1804865,2019-05-06 15:03:07 UTC,"Hello Andreas, or anyone else affected,"
1804865,2019-04-20 21:44:50 UTC,"Sponsored to Bionic, thank you for your contribution to Ubuntu!"
1804865,2019-04-20 20:25:17 UTC,Done according to your instructions - I hope I got it right now. Thanks!
1804865,2019-04-20 18:25:45 UTC,"Thank you for the bug report, and apologies for the delay on this."
1804865,2018-11-23 20:36:37 UTC,"diff -Nru scite-4.0.0/debian/changelog scite-4.0.0/debian/changelog
--- scite-4.0.0/debian/changelog	2017-08-16 19:11:14.000000000 +0200
+++ scite-4.0.0/debian/changelog	2018-11-23 20:53:03.000000000 +0100
@@ -1,3 +1,10 @@
+scite (4.0.0-1ubuntu1) bionic; urgency=medium
+
+  * Add patch enable_lua_to_access_dynamic_libraries.patch
+    enabling dynamic Lua libraries in SciTE (LP: #1804865)
+
+ -- Andreas Rönnquist <email address hidden>  Fri, 23 Nov 2018 20:53:03 +0100
+
 scite (4.0.0-1) unstable; urgency=medium"
1804865,2018-11-23 16:54:47 UTC,Upstream fix here:
1804865,2019-05-06 15:02:50 UTC,"Looks good! The SRU description is missing the regression potential field but for a change like this, I guess that would be not very relevant anyway. Accepting."
1804869,2019-02-20 12:43:29 UTC,Proposed fix: https://github.com/snapcore/snapd/pull/6525
1804869,2019-02-20 05:49:09 UTC,Is the denial after adding AppArmorPermanentSlot on 18.04 something we need to address?
1804869,2019-02-19 22:09:36 UTC,"I previously tested this on Ubuntu 16.04. I did again just now on 18.04 and after adding the AppArmorPermanentSlot to the profile and starting mir-kiosk, it was also able to start and create the socket at /run/user/0/wayland-0. I did see this non-fatal deny:"
1804869,2019-02-19 21:52:23 UTC,I apologize for only just looking at this now.
1804869,2019-02-19 22:01:28 UTC,"I should mention that I after stopping mir-kiosk, rmdir /run/user/0, adding/loading the AppArmorPermanentSlot to the profile and starting mir-kiosk, it was able to start and create the socket at /run/user/0/wayland-0."
1804875,2018-11-24 08:12:54 UTC,thanks for the good problem description
1804879,2018-11-27 15:05:10 UTC,unit-cinder-volume-0.log
1804879,2020-07-30 20:47:14 UTC,I've hit this bug on a new deployment. I'm subscribing it to field-medium.
1804879,2019-11-28 21:03:52 UTC,This bug is present on a customer installation that requested CinderLVM driver.
1804879,2019-03-19 15:11:31 UTC,"Adding a comment to summarize:
When deploying the ``cinder`` charm and making use of the ``enabled-services`` configuration option to split out the cinder services over multiple units it breaks."
1804879,2018-11-27 15:06:50 UTC,unit-neutron-openvswitch-0.log
1804879,2018-11-27 15:02:32 UTC,unit-ntp-0.log   - from cinder-volume/0 /var/log/juju   ---- cinder volume is on a nova-compute node.
1804879,2018-11-27 15:00:04 UTC,"New test run --- same results as before
using same test bundle."
1804879,2018-11-26 21:10:57 UTC,Can you please provide (sanitized) juju unit logs from cinder-volume/0?  The can be found in /var/log/juju/unit*.
1804879,2018-11-27 13:37:18 UTC,"I had tried a different config so will need to re-run the original bundle and cinder install.
Should be able to post new results in an hour or so."
1804879,2018-11-26 21:20:25 UTC,"Along with this bug, we also need to re-validate and put a scenario test around the following, and update the readme if needed:"
1804879,2018-11-27 15:01:16 UTC,unit-nova-compute-0.log  from cinder-volume/0 /var/log/juju/
1804879,2018-11-23 20:02:28 UTC,Also of note:
1804879,2018-11-23 19:44:43 UTC,"cut and paste for work method did not come out looking so nice.
Attached file is better."
1804887,2018-11-24 00:22:57 UTC,"The attachment ""partial implementation"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1804887,2020-05-10 00:35:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804887,2020-05-10 00:36:31 UTC,Kubuntu 20.04. Still relevant. Any updates?
1804888,2019-08-20 01:44:25 UTC,Feature requests need to be made with the upstream project at gimp.org. Please request this there. Thank you.
1804891,2018-11-24 10:46:30 UTC,Released versions 0.2.8.3.X are unaffected.
1804891,2018-11-24 10:45:52 UTC,"A missing null check, basically; and also, the code was checking the target player, so you could not issue kick votes on players who already were silenced. player_ sould be named targetPlayer_ here, really."
1804891,2018-11-24 01:32:27 UTC,"A more useful backtrace (on +ap this time though, meh):"
1804894,2018-11-26 18:30:03 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1804898,2019-09-26 13:25:31 UTC,fixed in 5.0
1804899,2018-11-24 00:23:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1804899,2018-11-27 02:11:12 UTC,"Tested this, at first I didn't see the issue (I was too quick & knew what I wanted), then when I paused to read menus, yes the panel disappeared (if mouse is on menu & not over panel).  I did have this issue when panel was in default (@ bottom), or moved to top of my screen."
1804899,2018-11-27 02:11:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804899,2018-11-27 02:58:14 UTC,"Sorry. in #2 I wondered if a change to a config file would help mitigate the issue, my play didn't make any difference, so ignore my openbox 'I wonder' suggestion. unless you know more than I do :)"
1804918,2018-12-12 16:23:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804918,2018-12-12 16:25:58 UTC,"Graphics card not supported by default will force the GUI to 800x600px size. The installer screen is not resizable and can't be scrolled therefore, several buttons are out of reach from the user."
1804918,2019-04-08 14:47:19 UTC,"I use virtualbox 6.0.4 to install ubuntu19.04, but when I partition I find out I can not go on to next step."
1804925,2019-06-25 11:27:05 UTC,"Fixed in revision f088d4d762e2c00d4e8420eb1a2345601b8112d1
https://git.launchpad.net/kicad/patch/?id=f088d4d762e2c00d4e8420eb1a2345601b8112d1"
1804927,2018-11-24 16:09:08 UTC,"Works like a champ!
Thank you very much!"
1804927,2018-11-24 17:08:37 UTC,Thanks for confirmation
1804927,2018-11-24 10:18:28 UTC,"Just tried to fix it, but not tested on Windows."
1804928,2019-04-25 15:55:15 UTC,This only happens when using the `M` hotkey and not when using a mouse block selection
1804928,2019-04-25 18:48:51 UTC,Fixed in my local tree.
1804929,2018-11-24 17:18:07 UTC,"@Rene,
A button in the ERC dialog is not really needed.
You can run the Annotate dialog from the main toolbar even if the ERC dialog is open.
The ERC dialog is not modal."
1804929,2019-03-20 19:47:02 UTC,It is a bit confusing right now. There are a few tools that spawn the annotation window and some others the error message. I would guess it might be a good idea to decide which of the two should happen and then use it for all tools that need the schematic to be annotated.
1804935,2018-11-26 18:29:20 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1804935,2018-12-25 21:47:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804936,2018-12-28 12:28:06 UTC,Your welcome and wish you happy new year.
1804936,2018-11-26 19:15:37 UTC,"SOLVE ""rabbitmq docker container continously restarting on Ubuntu 18 LTS with Rocky ""
8:13 PM Build Image with tag Rocky must  be deploy with git stable/rocky release  Kolla & Kolla-ansible.
8:13 PM Thank you egonzalez for your help.
8:13 PM Cheers
8:13 PM Elvis"
1804936,2018-12-27 19:41:19 UTC,I have the same problem of restarting and broken rabbitmq.
1804936,2018-12-28 08:00:06 UTC,"my solution was: I mus running the same release for Kolla and Kolla-ansible,
because the Problem with Rabbitmq was running Kolla with Rocky Release und Kolla-ansible with Master Relaese, these combination ist not recomanded."
1804936,2018-12-28 12:02:54 UTC,Thank you!
1804938,2019-10-22 07:25:05 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it."
1804938,2018-11-24 17:23:16 UTC,There are no apparmor denials in dmesg.
1804939,2020-03-07 15:46:11 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1804944,2018-12-03 17:22:33 UTC,Related: https://bugs.launchpad.net/kicad/+bug/1787510.
1804944,2019-05-05 14:30:51 UTC,Jeff already implemented this in eemodern branch
1804946,2018-11-25 02:01:09 UTC,The problem is the start/(end point is strored in namedview like the grid so update namedview force update grids. Im compiling a fix and try to backport.
1804946,2018-11-25 11:19:52 UTC,"Fixed on master on 5e593d90927b37a54f5c2d663bd25d6d661d7be9
Fixed in 0.92.x on 5aff6bad34a274c9b5937e075edccbf159395029"
1804948,2018-12-02 16:27:43 UTC,A patch for the bug is available.
1804948,2018-12-06 19:49:04 UTC,Fixed in x.4326.
1804948,2018-12-08 17:42:15 UTC,"Missing null test causing crash added in x.4328, see http://www.elvastower.com/forums/index.php?/topic/32508-speed-signal-with-or-speedreset-not-working-in-explore-route/page__view__findpost__p__243101 ."
1804951,2018-11-25 16:41:00 UTC,What DE do you use?
1804951,2018-11-25 17:05:15 UTC,"Hi,"
1804954,2018-12-01 20:24:29 UTC,"Hmm I also see this now, I'm pretty sure this worked before. I wonder why this is broken, it seems to be working in Debian Testing. I'll continue investigating, and post anything if I find something..."
1804954,2018-12-01 18:22:23 UTC,"Thanks. By the way, the same problem is not unique to the communitheme snap. I can reproduce the problem with the standard Ubuntu-Wayland session (with the default Ubuntu theme), while themes work correctly in the Ubuntu Xorg session."
1804954,2018-12-01 17:30:28 UTC,So you are definitely on the same version as me. I just tried with a virtual machine and was able to reproduce this after installing the communitheme snap session (and using the wayland variant). I will mark this as confirmed for now and discuss this issue with flatpak developers.
1804954,2018-11-29 20:53:05 UTC,"flatpak list:
org.gtk.Gtk3theme.Communitheme/x86_64/3.22         system,runtime"
1804954,2018-12-02 00:23:48 UTC,"Thanks, that workaround does mostly work. However, the window controls still don't look quite right even after disabling and enabling the minimize and maximize buttons in Gnome Tweaks."
1804954,2018-12-02 00:25:23 UTC,Correction -- the issue of window controls is not specific to Wayland and perhaps belongs in a separate bug.
1804954,2018-12-01 16:56:55 UTC,The communitheme session was installed via snap.
1804954,2018-12-01 23:23:57 UTC,"OK after much discussion with flatpak developers and testing things in VMs, we have found the reason this happens on wayland only !"
1804954,2018-12-01 16:26:00 UTC,"Maybe, although it still seems a bit strange - i do wonder if snap and flatpak maybe conflicting somehow. For the communitheme-wayland session did you install that via a snap or PPA ?"
1804954,2018-11-24 18:00:33 UTC,Gnome Builder in Communitheme session
1804954,2018-11-30 02:30:59 UTC,Under Wayland:
1804954,2018-11-29 21:28:31 UTC,Thanks for the extra info!
1804954,2018-11-29 20:54:00 UTC,Gnome Recipes in Xorg
1804954,2018-11-29 20:53:32 UTC,Gnome Recipes in Wayland
1804954,2018-11-29 18:52:05 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1804954,2018-12-01 16:11:05 UTC,"Could this issue be related?
https://gitlab.gnome.org/GNOME/gtk/issues/1343"
1804954,2018-11-24 18:00:03 UTC,Gnome Builder (latest) in Communitheme-Wayland session
1804956,2020-06-23 09:00:58 UTC,"This looks to work as intended to me as this counter counts the number of items in the list, the first number shows the rows filtered out by the grouping and the text filter input in the bottom while the second is the total number of rows in the list.
It has never counted the download sources in any way."
1804957,2018-11-24 19:52:40 UTC,"note, its not specifically about the -package- but about malicious snapdevs ability to namesquat established project names away from their specific implementations"
1804957,2018-11-24 19:53:27 UTC,"so no, its not a duplicate"
1804960,2018-11-24 22:35:06 UTC,"You might try to disable ""Rewrap on resize"" under the Profile preferences."
1804960,2018-11-24 23:59:04 UTC,"""Rewrap on resizes"" doesn't work. It does the same."
1804961,2021-01-31 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1804961,2020-12-01 10:37:09 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1804961,2018-12-05 11:57:23 UTC,Yeah it seems to be. Windows boots fine after I disable hi ECAM region.
1804961,2018-12-05 11:32:50 UTC,Could it be related to:
1804961,2018-11-28 19:25:07 UTC,"@imammedo:
I am new to kernel debugging, but I managed to get some traces, hope that will help you."
1804961,2018-11-29 04:57:15 UTC,"And the namespace objects tree of virt-2.12 is this.
https://pastebin.com/GybigJ9r"
1804961,2018-11-26 12:14:38 UTC,"On Sat, 24 Nov 2018 20:36:54 -0000
GH Cao <email address hidden> wrote:"
1804961,2018-12-04 12:43:51 UTC,"On Wed, 28 Nov 2018 19:25:07 -0000
GH Cao <email address hidden> wrote:"
1804963,2019-01-04 20:57:42 UTC,"""Input/output error"" usually indicates a file system inconsistency.
Run a full file system check on your root file system."
1804968,2019-02-02 10:32:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804969,2018-11-24 23:23:34 UTC,"Issue 1 is already known upstream.  Workaround is to disable
animations via budgie settings"
1804970,2019-05-14 02:23:40 UTC,"The latest versions of this driver are only available to Ubuntu Advantage customers. I would probably suggest trying the openly available drivers from the Fedora project (which as far I can tell, is just a newer version of the same drivers published in this project - the commercial Ubuntu Advantage driver may be different, I am not sure):
https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html"
1804978,2019-11-05 02:13:24 UTC,"As of version 4.2.3-2 from https://deb.debian.org/debian testing/main amd64 Packages
bug is still present.
(bring` up external drive in second tab, eject: nemo window disappears)"
1804978,2019-11-13 01:14:48 UTC,"Debian apparently has a separate repository for debug packages.  I found and installed nemo-dbgsym and nemo-fileroller-dbgsym, and re-ran gdb.
(terminal output for gdb without dbgsym is shown in comment #6, above)"
1804978,2019-10-01 02:17:58 UTC,"As of version 4.0.6-1 from https://deb.debian.org/debian testing/main amd64 Packages
bug is still present.
(bring` up external drive in second tab, eject: nemo window disappears)"
1804978,2019-06-14 00:42:27 UTC,"As of Nemo 3.8.5, bug still present."
1804978,2019-07-07 15:02:18 UTC,Nemo was Fixed in version 4.0.2
1804978,2019-09-08 06:09:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804990,2018-11-25 09:12:23 UTC,"looks like this has been reported a couple of times, so feel free to link/close/reject it"
1804990,2019-03-27 12:54:18 UTC,I try to make some improvements on this problem. Can you test the attachment?
1804990,2019-03-27 13:28:16 UTC,"Hi Stefan,
thanks for looking into this. I don't have the test device at the moment (it's on a loan), but I believe I should be able to test in a month or so. Further info I've found in other, similar tickets, is that the playback won't work if I go to the ""episodes"" view. However, if I go to the podcast view, and find & play the episode from there (less intuitive for me, but what can you do), apparently the playback works. Can you confirm that on your device, if you have one to test?
Thanks,
Milan"
1804990,2019-04-08 08:42:50 UTC,"Hello Milan,"
1804990,2019-07-31 17:22:45 UTC,"For me, I find that I sometimes have to download the episode, then close and reopen the app for it to play offline."
1804992,2018-11-26 17:36:27 UTC,I add then that if you render 3D there are silk-screen printed in the air
1804992,2018-11-25 09:41:10 UTC,Motivation: https://github.com/KiCad/kicad-footprints/pull/1016
1804995,2019-09-12 03:06:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804996,2020-03-27 21:01:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1804996,2020-03-27 21:01:02 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1804999,2018-11-26 18:25:43 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1805003,2019-01-27 12:36:27 UTC,"It's not a bug, precision value must be set in the follwing way:
awk -M -v PREC=10000 'BEGIN {  x = 1;  y = 1;  result = 4*atan2 (y,x);  printf "" %.50f\n"", result}'"
1805004,2019-01-21 18:51:53 UTC,This issue was fixed in the openstack/karbor 1.2.0 release.
1805004,2019-04-11 14:51:31 UTC,"Why is this considered a bug? It was a very valuable feature for us actually, it allowed cross-project and even cross-cloud backup/restore"
1805004,2019-05-13 03:00:34 UTC,Only admin users should have the rights to restore other users' checkpoints. Non admin users can only restore the checkpoints belong to themselves.
1805011,2018-11-25 19:12:46 UTC,apport information
1805011,2018-11-25 19:12:41 UTC,apport information
1805011,2018-11-25 19:12:42 UTC,apport information
1805011,2018-11-25 19:12:45 UTC,apport information
1805011,2018-11-26 18:09:37 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1805011,2018-11-26 19:12:52 UTC,"I recently bought this old sound card. I can not say when it stopped working normally. In Ubuntu 12.04, it works stably. I will try to check in ubuntu 16.04
Updated the kernel, it became even worse. Linux is half frozen. Logs could not be saved."
1805011,2018-11-27 07:52:56 UTC,"Please try if older kernel works, e.g. v3.13, v4.4."
1805011,2018-11-26 19:29:57 UTC,Install latest kernek version v4.20-rc4. Nothing changed.
1805011,2018-11-25 19:12:40 UTC,apport information
1805011,2018-11-27 19:33:13 UTC,"Install the kernel 4.4 nothing has changed.
I failed to install kernel 3 versions.
3.20 version work no problem in Ubuntu 12.04.
I tested the sound card in Linux Mint 18. kernel 4.4v. All okay and work only 44.1 khz.
I think something is broken in the version of Ubuntu 18.04.
Need to do tests at Ubuntu 16.04"
1805011,2018-11-27 20:02:41 UTC,"I'm tested sound card Lubuntu 16.04 live usb. Kernel 4.15.0.39. All okey.
The problem is not in kernel. Ubuntu 18.04 broken."
1805011,2018-11-28 13:32:50 UTC,"I surrender, magic Linux won. I'm tested sound card Lubuntu 18.04 live usb. All okey.
Install Lubuntu 18.04 no work. On two laptops does not work."
1805011,2018-11-26 19:21:30 UTC,"There log
Nov 26 22:00:46 X230 kernel: [   95.099773] usb 1-1.2: new high-speed USB device number 7 using ehci-pci
Nov 26 22:00:47 X230 kernel: [   95.211494] usb 1-1.2: New USB device found, idVendor=041e, idProduct=3f02, bcdDevice= 1.00
Nov 26 22:00:47 X230 kernel: [   95.211496] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 26 22:00:47 X230 kernel: [   95.211497] usb 1-1.2: Product: E-MU 0202 | USB
Nov 26 22:00:47 X230 kernel: [   95.211498] usb 1-1.2: Manufacturer: E-MU Systems, Inc.
Nov 26 22:00:47 X230 kernel: [   95.211499] usb 1-1.2: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A
Nov 26 22:01:02 X230 kernel: [  110.403825] usb 1-1.2: reset high-speed USB device number 7 using ehci-pci
Nov 26 22:01:20 X230 kernel: [  128.584696] usb 1-1.2: cannot submit urb 0, error -2: endpoint not enabled
Nov 26 22:01:29 X230 kernel: [  137.732266] usb 1-1.2: USB disconnect, device number 7
Nov 26 22:01:34 X230 kernel: [  142.343904] usb 3-1: new high-speed USB device number 2 using xhci_hcd
Nov 26 22:01:34 X230 kernel: [  142.494670] usb 3-1: New USB device found, idVendor=041e, idProduct=3f02, bcdDevice= 1.00
Nov 26 22:01:34 X230 kernel: [  142.494675] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 26 22:01:34 X230 kernel: [  142.494679] usb 3-1: Product: E-MU 0202 | USB
Nov 26 22:01:34 X230 kernel: [  142.494682] usb 3-1: Manufacturer: E-MU Systems, Inc.
Nov 26 22:01:34 X230 kernel: [  142.494684] usb 3-1: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A
Nov 26 22:01:56 X230 kernel: [  164.372308] usb 3-1: reset high-speed USB device number 2 using xhci_hcd
Nov 26 22:02:18 X230 kernel: [  186.300396] usb 3-1: reset high-speed USB device number 2 using xhci_hcd
Nov 26 22:02:23 X230 kernel: [  191.676141] usb 3-1: device descriptor read/64, error -110
Nov 26 22:02:33 X230 kernel: [  201.808728] usb 3-1: cannot submit urb 0, error -19: no device
Nov 26 22:02:33 X230 kernel: [  201.809015] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x13.
Nov 26 22:02:33 X230 kernel: [  201.809173] usb 3-1: USB disconnect, device number 2
Nov 26 22:02:33 X230 kernel: [  201.810005] xhci_hcd 0000:00:14.0: Slot 1 endpoint 1 not removed from BW list!
Nov 26 22:02:33 X230 kernel: [  201.810009] xhci_hcd 0000:00:14.0: Slot 1 endpoint 2 not removed from BW list!
Nov 26 22:02:37 X230 kernel: [  205.608100] usb 3-1: new high-speed USB device number 3 using xhci_hcd
Nov 26 22:02:37 X230 kernel: [  205.758942] usb 3-1: New USB device found, idVendor=041e, idProduct=3f02, bcdDevice= 1.00
Nov 26 22:02:37 X230 kernel: [  205.758950] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 26 22:02:37 X230 kernel: [  205.758955] usb 3-1: Product: E-MU 0202 | USB
Nov 26 22:02:37 X230 kernel: [  205.758960] usb 3-1: Manufacturer: E-MU Systems, Inc.
Nov 26 22:02:37 X230 kernel: [  205.758964] usb 3-1: SerialNumber: E-MU-03-3F02-07DA0C14-0E730-8740T2A
Nov 26 22:03:54 X230 kernel: [  282.549975] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:0:26]
Nov 26 22:03:54 X230 kernel: [  282.549978] Modules linked in: acpi_call(OE) ccm cmac bnep uvcvideo videobuf2_vmalloc btusb videobuf2_memops b..."
1805011,2018-11-25 19:12:39 UTC,apport information
1805011,2018-11-25 19:12:44 UTC,apport information
1805011,2018-11-25 19:12:36 UTC,apport information
1805011,2018-11-25 19:12:35 UTC,apport information
1805011,2018-11-25 19:12:34 UTC,apport information
1805011,2018-11-25 19:12:33 UTC,apport information
1805011,2018-11-25 19:12:31 UTC,apport information
1805011,2018-11-25 19:12:30 UTC,apport information
1805011,2018-11-25 19:12:28 UTC,apport information
1805011,2018-11-25 19:12:27 UTC,apport information
1805011,2018-11-25 19:12:25 UTC,apport information
1805011,2018-11-25 19:12:23 UTC,apport information
1805011,2018-11-25 19:12:21 UTC,apport information
1805011,2018-11-25 19:12:20 UTC,apport information
1805011,2018-11-25 14:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805011,2018-11-25 19:12:37 UTC,apport information
1805015,2018-11-27 14:16:35 UTC,"Thanks Olivier, I see the potential leak. However, it makes LO somewhat less useful for me, because I very frequently access files form the recently used list. All in all, it seems that the question is, how snaps can be integrated into a desktop shell so as to give the user a flawless experience of the desktop as a whole. For years, desktop shells like GNOME or KDE strive to give an integrated ""touch and feel"" to the user. The (intended) separation of snaps from each other seem to contradict this design goal. In the end, the desktop might just feel like a loose assembly of separate applications running side by side without much interaction. I'm not sure how this can be resolved."
1805015,2018-11-27 08:29:57 UTC,I opened a thread on the snapcraft forum to discuss this further: https://forum.snapcraft.io/t/gtkrecentmanager-and-recently-used-files-in-sandboxed-applications/8702.
1805015,2018-11-25 19:06:52 UTC,"For me, this disrupts the daily workflow with LO to an extent where I consider changing back from the snap to deb."
1805015,2018-11-27 08:18:54 UTC,"When opening the file from nautilus, it is correctly added to the list of recently used files."
1805016,2019-06-02 21:38:47 UTC,"Hi, I wanted to let you know that Mugshot has moved to GitHub and this project has been migrated to the below URL. I'll be closing this report and further progress will be made on the linked issue. Thanks!"
1805018,2018-11-25 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805018,2018-11-25 16:15:13 UTC,No log files is required.
1805018,2018-11-25 16:25:59 UTC,Current kernel configuration
1805018,2019-06-02 15:25:59 UTC,config-5.0.0-16-generic: 'OK' - 43 / 'FAIL' - 60
1805018,2020-05-07 19:01:16 UTC,"Ubuntu 20.04 LTS (Focal Fossa) :
config check is finished: 'OK' - 57 / 'FAIL' - 79"
1805018,2020-11-21 09:22:41 UTC,"To be read!
https://blog.herecura.eu/blog/2020-05-30-kconfig-hardening-tests/"
1805019,2019-07-03 19:17:21 UTC,This bug was fixed in the package firefox - 68.0+build1-0ubuntu1
1805020,2019-11-04 09:03:33 UTC,Maybe I wasn't clear about my request. I want to have contrast between dark background and light colour font. As in example below from Okular:
1805020,2019-11-04 07:31:58 UTC,"Hello Axel,"
1805020,2019-11-04 09:33:23 UTC,So this is a duplicate of #1785407 were we await patches.
1805024,2019-08-21 21:42:04 UTC,This seems to have been fixed quite a while back.
1805024,2018-11-25 15:57:58 UTC,"Attaching log from xev showing, toward the bottom, scrolling up (button 4) and down (button 5)."
1805024,2020-03-09 02:53:46 UTC,"Well, the issue is back again in Disco and Dolphin 4:19.04.3-0ubuntu1~ubuntu19.04~ppa1."
1805032,2018-12-03 20:43:35 UTC,"After this length of time, and no response, it is most probable that the OP has solved his problem and is able to print."
1805032,2018-11-25 19:31:53 UTC,"> - I have just bought a HP ENVY Photo 6230 printer and it is working very well in > Wifi on a Windows PC. I wanted to install it also on my laptop provided with
> Linux Mint 18.3 Sylvia.
"
1805034,2018-12-02 03:42:55 UTC,Forgot to add: I also added some author information to the new files.
1805034,2018-12-02 03:41:26 UTC,"First of all, thank you for looking at this and sorry for the delay!"
1805034,2018-11-26 15:45:14 UTC,Patch (1/4) looks good; I've applied as bzr -r722
1805035,2018-12-22 22:23:45 UTC,"Yeah that looks about right. I'll merge the patch, give or take some minor alterations:"
1805035,2018-11-26 16:50:26 UTC,"Overall this is looking very nice - I like that you've nicely documented the new functions in comments, and updated the tests."
1805035,2018-12-02 05:39:56 UTC,Thank you for your feedback! I've incorporated your suggestions into a new patch that can be found here:
1805038,2020-08-19 23:41:28 UTC,"Netplan doesn't support ""dev"", so this is effectively a feature request. I also need this feature. Currently, ""via"" is required. As ""dev"" is added, that restriction will need to be relaxed (e.g. that either ""via"" or ""dev"" is required)."
1805040,2019-02-01 04:14:16 UTC,This can't be a good answer.
1805040,2019-05-01 19:53:42 UTC,Seeing the same issue on 18.04.2LTS Aarch64. How can I get arround it? Commercial software.
1805040,2019-09-18 20:00:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805040,2019-09-18 20:01:58 UTC,"Why is this still in an ""undecided"" stage?  Anyone who links against libreadline on Ubuntu 14 or 16, and tries to ship a package that can also run on 18, is screwed here."
1805040,2018-11-26 17:37:38 UTC,Thanks for reporting.
1805042,2018-11-26 07:29:26 UTC,"It is always possible that files can become corrupt, so a check is a good idea :)"
1805042,2018-12-12 00:35:26 UTC,"Finally got some time for Widelands again. Checked the preloader properly and found a few potential problems that can (for invalid files) lead to out-of-bounds operations.
What caused the crashes was likely an invalid player number which then lead to out-of-bounds access of the player name array (and possibly other stuff).
It was also possible too read too much data (possibly the whole file) when the null-terminator for name or author was missing. (At least that one would not have been critical, because our fileread data artificially ends with a null.)"
1805042,2019-09-16 08:25:02 UTC,Migrated to https://github.com/widelands/widelands/issues/3358
1805043,2019-05-20 06:40:58 UTC,This will be fixed by https://code.launchpad.net/~woutervb/graylog-charm/+git/graylog-charm/+merge/367556
1805043,2020-02-12 00:26:44 UTC,Linked MPs are still waiting on review?
1805044,2018-11-25 20:10:15 UTC,"Power management is affecting my wifi connection in the last three years, thus I'm using usb tethering from my Xperia, anyway it would be unusable, some point it's just dead, and even worse, holding my chrome tab, and I need to reopen in a different window, as it would be unresponsive."
1805044,2018-11-25 20:13:32 UTC,Disabling dimming solved my issues. Bloody crap!
1805044,2018-11-25 20:42:06 UTC,"Battery lifetime also didn't show up correctly, simply just using half of my battery. The problem disappeared one year before and came back again."
1805049,2018-11-26 17:14:36 UTC,"Are these mapped in script or straight XML? If script, is ignoreNextValue() called right before switching what the fader controls?"
1805049,2018-11-26 18:24:41 UTC,"With script, and yes, engine.ignoreNextValue gets called when switching layers."
1805050,2018-11-26 17:08:08 UTC,Renumbered as of -r725
1805050,2018-11-26 17:10:12 UTC,And now doc added in -r726
1805050,2018-11-26 17:00:38 UTC,LGTM. Nice coverage of test cases too including some full-width Unicode.
1805050,2018-11-25 21:31:52 UTC,I've implemented the REP CSI in the following patch:
1805063,2018-11-26 18:20:14 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1805063,2019-01-02 08:00:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805063,2020-04-25 08:09:32 UTC,"This is probably the same as this ""fixed"" (but not) issue: #1773859"
1805063,2020-04-25 08:10:36 UTC,Let's try to mention it properly:
1805074,2019-07-31 14:56:40 UTC,"pytz exposes the IANA database, which uses PDT and PST. You need to argue this on the IANA timezone mailing list, and will be required to cite official sources. Note that the timezone abbreviations are not globally unique, and many regions share the same codes."
1805076,2019-02-19 13:14:04 UTC,Is this still an issue?
1805076,2019-05-19 04:17:51 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1805077,2018-11-26 09:28:42 UTC,I do not use Bluetooth at all.
1805077,2019-01-26 04:17:16 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1805077,2019-04-30 02:42:52 UTC,"""1805077 do not appear again.""
[https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1826730/comments/13]"
1805077,2019-05-01 03:01:48 UTC,"This bug appear a few time today after I upgrade my system to ubuntu19.04.
This is definitely a bug."
1805077,2020-09-08 02:20:23 UTC,"I do not use ubuntu now.
I use deepin V20 instead."
1805077,2020-09-07 00:01:11 UTC,"I am a new Linux user, and I face the same problem in Ubuntu 20.04
A short (about a second or less) repeated sound occurs at random times, in the browser, in VLC or even the system sounds, and it's actually annoying.
I tried Fedora 32 but the same issue there but less likely to happens, and I tried OpenSUSE Leap 15.2 and it never happened.
My search led me to an Arch article explaining the situation:
""The newer implementation of the PulseAudio sound server uses timer-based audio scheduling instead of the traditional, interrupt-driven approach.
Timer-based scheduling may expose issues in some ALSA drivers. On the other hand, other drivers might be glitchy without it on, so check to see what works on your system.""
See https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches,_skips_or_crackling
I tried the proposed solutions but it Don't work."
1805077,2020-09-08 01:55:00 UTC,widon1104: Do you still experience this bug? How about in Ubuntu 20.04?
1805077,2020-09-08 16:14:34 UTC,"@vanvugt I did, see: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894872"
1805077,2019-05-01 10:37:51 UTC,"This bug happens dozens of times a day after I upgrade to ubuntu19.04.
Please do not let this bug to expire."
1805077,2018-11-26 09:09:36 UTC,Are you using Bluetooth audio?
1805077,2020-09-08 01:13:28 UTC,"It seems that it's an old bug:
It happened in 16.04, see: https://askubuntu.com/questions/915904/audio-glitches-every-2-10-minutes-ubuntu-16-04
and 18.04, see: https://askubuntu.com/questions/1044552/audio-stuttering-in-ubuntu-18-04
It turned out that there is a bug in kernel which causes audio stutter if a wifi enabled yet not connected to any wifi network.
So I disabled my internal unused wifi card (like in this refrence: https://askubuntu.com/questions/168032/how-to-disable-built-in-wifi-and-use-only-usb-wifi-card), and so far everything works fine."
1805077,2018-11-26 07:36:03 UTC,"I use smplayer to play local avi videos, sometimes this bug appear."
1805077,2018-11-26 08:53:02 UTC,vlc play local avi videos still has this problem
1805077,2018-11-26 05:30:45 UTC,"I use ubuntu18.04
widon@widon-X555YI:~$ dpkg -l | grep pulseaudio
ii  gstreamer1.0-pulseaudio:amd64                 1.14.1-1ubuntu1~ubuntu18.04.1               amd64        GStreamer plugin for PulseAudio
ii  pulseaudio                                    1:11.1-1ubuntu7.1                           amd64        PulseAudio sound server
ii  pulseaudio-module-bluetooth                   1:11.1-1ubuntu7.1                           amd64        Bluetooth module for PulseAudio sound server
ii  pulseaudio-utils                              1:11.1-1ubuntu7.1                           amd64        Command line tools for the PulseAudio sound server"
1805077,2018-11-26 05:51:54 UTC,Please:
1805077,2018-11-26 06:07:51 UTC,apport information
1805077,2018-11-26 06:07:53 UTC,apport information
1805077,2020-09-07 00:01:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805077,2018-11-26 06:07:55 UTC,apport information
1805077,2018-11-26 06:07:57 UTC,apport information
1805077,2018-11-26 06:07:59 UTC,apport information
1805077,2018-11-26 06:08:00 UTC,apport information
1805077,2018-11-26 06:45:27 UTC,I use firefox63.0.3(64bit)
1805077,2018-11-26 07:12:12 UTC,Thanks. Do you experience audio problems in any other apps? In particular when playing local files?
1805083,2019-04-19 19:22:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805084,2018-12-18 13:00:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805088,2018-11-30 16:57:51 UTC,"I encountered this iwlwifi failure while testing the Intel 9260 with the AMD Ryzen 7 2700x (8 core, 16 thread).  By bisecting the kernel, I was able to narrow it down to the same commit.  I can also verify that setting maxcpus=15, fixes wifi (at the cost of performance)."
1805088,2018-12-05 03:12:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1805088,2018-12-07 02:37:49 UTC,"There is a new kernel just uploaded, Ubuntu-4.15.0-43.46
but it looks like kernel team miss this patch.
According to the schedule[1], the next kernel in -proposed would be at Jan. 21st 2019"
1805088,2018-12-20 05:39:13 UTC,This bug was fixed in the package linux-oem - 4.15.0-1030.35
1805088,2018-11-26 08:03:54 UTC,"commit ab1068d6866e28bf6427ceaea681a381e5870a4a
Author: Hao Wei Tee <email address hidden>
Date:   Tue May 29 10:25:17 2018 +0300"
1805088,2018-12-06 20:33:33 UTC,"There isn't yet a new kernel in *bionic* -proposed to solve this issue, so I can't test it."
1805096,2018-12-12 10:12:41 UTC,lightdm was having some problem..
1805097,2018-12-18 09:58:48 UTC,apport information
1805097,2018-12-18 09:58:49 UTC,apport information
1805097,2018-12-18 09:58:52 UTC,apport information
1805097,2018-12-18 09:58:36 UTC,apport information
1805097,2018-12-19 06:00:44 UTC,dmesg
1805097,2018-12-19 06:07:55 UTC,UdevDb
1805097,2018-12-19 06:10:01 UTC,wifisyslog
1805097,2018-12-18 09:58:47 UTC,apport information
1805097,2018-12-18 09:58:53 UTC,apport information
1805097,2018-12-18 09:58:45 UTC,apport information
1805097,2018-11-26 18:07:33 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1805097,2018-12-18 09:58:43 UTC,apport information
1805097,2018-12-18 09:58:41 UTC,apport information
1805097,2018-12-18 09:58:39 UTC,apport information
1805097,2018-12-18 09:58:38 UTC,apport information
1805097,2018-12-18 09:58:35 UTC,apport information
1805097,2018-12-18 09:58:32 UTC,apport information
1805097,2018-12-18 09:58:31 UTC,apport information
1805097,2018-11-26 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805097,2018-12-18 09:58:44 UTC,apport information
1805098,2018-12-19 06:12:40 UTC,"More system info check this post below.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097"
1805098,2018-11-26 09:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805098,2018-11-26 18:07:09 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1805099,2018-11-26 09:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805099,2018-12-19 06:12:55 UTC,"More system info check this post below.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097"
1805103,2019-03-28 21:09:46 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1805103,2019-04-10 10:31:19 UTC,This bug was fixed in the package ukui-control-center - 1.1.7-0ubuntu1
1805111,2018-12-01 18:24:48 UTC,"I've also seen this issue on a 2010 or 2011 MacBook Air, which stopped working so I can no longer use to test."
1805112,2018-11-26 15:44:59 UTC,I think the argument was that AZ was a description of physical availablity - something like north-building or floor three or on-big-switch-with-backup-power-B.
1805112,2018-11-26 13:40:25 UTC,The zone name is “default”. Are you saying that if you change that to a different zone (the pod) the compose menu still uses “default”? (The screenshot doesn’t show that difference)
1805115,2018-11-29 17:24:15 UTC,"Confirmed working with gawk, failing with mawk."
1805115,2018-11-29 17:26:57 UTC,"Fails from trusty onwards, all the way to disco."
1805119,2019-06-28 09:25:48 UTC,Same problems happens for project names
1805119,2019-09-19 12:21:18 UTC,"openstack-ceilometer-notification-11.0.0-1.el7.noarch
python2-ceilometerclient-2.9.0-1.el7.noarch
python-ceilometer-11.0.0-1.el7.noarch
openstack-ceilometer-common-11.0.0-1.el7.noarch
openstack-ceilometer-polling-11.0.0-1.el7.noarch"
1805119,2019-09-19 12:38:28 UTC,This should be solved with tooz 1.62.1 and above
1805121,2019-12-19 14:17:56 UTC,"Not sure if it's still relevant, I'm moving it to ""invalid"", if it's still need some work, then do not hesitate to re-open it."
1805122,2019-05-28 05:53:18 UTC,Does the issue still happen?
1805122,2018-11-28 06:57:25 UTC,"Sorry for another comment.
Just restarted the computer again and had no troubles with the screens."
1805122,2018-11-27 14:27:24 UTC,"Hello,"
1805122,2018-11-27 14:22:29 UTC,apport information
1805122,2018-11-27 14:22:28 UTC,apport information
1805122,2018-11-27 14:22:27 UTC,apport information
1805122,2018-11-27 14:22:25 UTC,apport information
1805122,2018-11-27 14:22:23 UTC,apport information
1805122,2018-12-04 11:01:46 UTC,Hi! I just upgrade 4.20. Nothing changed
1805122,2018-11-27 14:22:22 UTC,apport information
1805122,2018-11-27 14:22:21 UTC,apport information
1805122,2018-11-27 14:22:20 UTC,apport information
1805122,2018-11-27 14:22:18 UTC,apport information
1805122,2018-11-27 14:22:16 UTC,apport information
1805122,2018-11-27 14:22:15 UTC,apport information
1805122,2018-11-27 14:22:14 UTC,"ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  patrick    2203 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-04-06 (235 days ago)
InstallationMedia: Ubuntu 17.10 ""Artful Aardvark"" - Release amd64 (20180105.1)
IwConfig:
 lo        no wireless extensions."
1805122,2018-11-26 19:14:43 UTC,Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].
1805122,2018-11-26 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805122,2018-11-27 14:22:23 UTC,apport information
1805126,2018-11-26 11:37:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620017"
1805129,2021-02-04 14:36:26 UTC,"I toyed around a bit based on the post #11 from Alkis Georgopoulos
(thank you for that, vala-panel-appmenu.sh is indeed the culprit, that was really really helpful)"
1805129,2021-01-24 14:35:27 UTC,"Just want to mention that:
I downloaded glade 3.38.1 as source code from glade.gnome.org and built it with meson and ninja, as instructed, on Ubuntu 20.04 Desktop. (Had to install a lot of packages to make it build, though).
When I run glade from bash cmd-line I get the message you are discussing:
(glade:20715): Gdk-WARNING **: 15:27:23.596: ../../../../../gdk/x11/gdkwindow-x11.c:5633 drawable is not a native X11 window"
1805129,2020-06-14 04:53:37 UTC,I want to confirm that glade worked from snap Ubuntu 20.04 as Alexander point
1805129,2020-07-07 18:05:36 UTC,"The problem seems to be caused by /etc/profile.d/vala-panel-appmenu.sh that sets
GTK_MODULES=""$GTK_MODULES:appmenu-gtk-module"""
1805129,2020-07-07 12:47:30 UTC,"Affects me too, on Ubuntu MATE 20.04."
1805129,2020-06-05 10:37:49 UTC,"Not a huge fan of snaps, but I was able to work around the issue and get a functioning glade instance on my 20.04 workstation by installing the image from https://snapcraft.io/glade. Since this image works I tend to agree with Nathan's assessment from comment #7."
1805129,2019-11-10 16:21:55 UTC,I am also experiencing this issue. Glade 3.22.1 with MATE (X11) on Ubuntu 19.10.
1805129,2020-05-29 12:31:55 UTC,Same issue on Ubuntu MATE 20.04 LTS with glade 3.22.2-1
1805129,2020-05-07 13:03:14 UTC,"I can add the info that:
1) Older versions of glade (i.e. 3.18) that worked before, crash with the current library set.
2) the snap version of glade does work on Ubuntu MATE focal."
1805129,2020-04-29 23:32:31 UTC,Same issue with glade 3.22.2-1 on Ubuntu MATE focal.
1805129,2019-01-26 18:56:56 UTC,I am experiencing the same issue with glade 3.22.1-1 in an Xfce X11 session on Ubuntu 18.04.1 LTS.
1805129,2019-01-26 18:51:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805129,2020-05-29 12:36:57 UTC,I can also add that this issue maybe due to Ubuntu/Debian specific patches in lower levels of the stack (eg. gtk or even gdk) because downloading the upstream source for 3.22.2 and building it outside of a deb package still results in this same crash
1805132,2018-12-05 15:29:22 UTC,Thank you for your bug report.
1805132,2018-12-10 13:33:27 UTC,There are multiple previous bug reports of 'Retry wrapper got retriable exception' on the table 'standardattributes':
1805132,2019-01-29 16:15:07 UTC,"I have not been able to confirm that the issues listed above are all duplicates, but these all fail in a very similar way. It does make me wonder whether there is an underlying issue related to the handling updates to standard attributes that affects operations on all resources like networks, subnets, and ports."
1805137,2018-11-28 17:13:48 UTC,"Thanks for the message. The anonymizing is not a problem. It turns out that this is almost an RFC 3464 compliant DSN and should be recognized by Mailman/Bouncers/DSN.py except for the fact that the 'action' in the Delivery Report is 'error'. This is non-compliant. RFC 3464, sec 2.3.3 defines action as:"
1805137,2018-11-29 15:41:42 UTC,"thanks Mark,"
1805137,2018-11-27 02:02:53 UTC,"Thank you for the report and suggested patch.  If possible, please post the entire, raw bounce message including all headers. We need that for the testing data. Also, depending on the headers and MIME structure of the message, SimpleMatch may not be the optimum recognizer."
1805137,2018-11-28 12:21:46 UTC,"Hi Mark,"
1805148,2018-11-27 01:57:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1805148,2018-11-27 03:40:40 UTC,apport information
1805148,2018-11-27 03:40:42 UTC,apport information
1805148,2018-11-27 03:54:44 UTC,Thanks. Unfortunately that didn't attach everything I was thinking of. Can you please also:
1805148,2018-11-30 03:15:21 UTC,"00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
 Subsystem: Hewlett-Packard Company Compaq 6910p
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:03.0 Communication controller: Intel Corporation Mobile PM965/GM965 MEI Controller (rev 0c)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: mei_me
 Kernel modules: mei_me
00:03.2 IDE interface: Intel Corporation Mobile PM965/GM965 PT IDER Controller (rev 0c)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: ata_generic
 Kernel modules: pata_acpi
00:03.3 Serial controller: Intel Corporation Mobile PM965/GM965 KT Controller (rev 0c)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: e1000e
 Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: uhci_hcd
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M-E) LPC Interface Controller (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel driver in use: lpc_ich
 Kernel modules: lpc_ich
00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
 Subsystem: Hewlett-Packard Company Compaq 6910p
 Kernel drive..."
1805148,2018-11-30 03:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805148,2018-11-30 12:19:42 UTC,apport information
1805148,2018-11-30 12:19:44 UTC,apport information
1805150,2019-04-17 06:37:27 UTC,"Hello,
the patch mentioned in the link has landed in 4.18, do you still have this issue with the latest HWe kernel on Bionic?"
1805150,2019-04-17 13:02:01 UTC,"The HWE kernel on Bionic does not have this problem anymore, as it was patched in a previous update."
1805150,2019-06-17 04:17:37 UTC,[Expired for linux-signed-hwe-edge (Ubuntu) because there has been no activity for 60 days.]
1805154,2019-02-04 14:46:37 UTC,This bug was fixed in the package linux - 4.19.0-12.13
1805154,2018-12-14 22:01:25 UTC,*** This bug has been marked as a duplicate of bug 1659295 ***
1805154,2018-12-14 20:47:41 UTC,The GNU_EH_FRAME segment is actually empty in our builds.  This breaks unwinding across signal handlers on i386 because the libgcc unwinder does not recognize i386 __kernel_sigreturn as a signal handler frame anymore.
1805154,2018-11-20 21:53:54 UTC,"Created attachment 279555
A testcase"
1805154,2018-11-26 14:37:29 UTC,"Looks to be a regression in the vdso caused by 379d98ddf41344273d9718556f761420f4dc80b3 ""x86: vdso: Use $LD instead of $CC to link"" in Linux 4.19."
1805154,2018-11-20 21:55:21 UTC,This is caused by
1805154,2018-11-18 17:29:41 UTC,"Under 4.19.2-300 kernel, i686 glibc tests failed with:"
1805154,2018-11-26 14:44:00 UTC,Applied a revert of 379d98ddf41344273d9718556f761420f4dc80b3 to fix this until a fix is available upstream.
1805162,2019-10-08 09:15:52 UTC,"Yes, this is a known limitation and the long term plan is to implement configuration schemas where options will be constrained and invalid ones rejected."
1805164,2019-02-23 10:14:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/638803"
1805164,2019-03-24 23:39:29 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1805164,2019-03-24 23:04:06 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1805164,2019-03-22 03:44:07 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1805164,2019-03-15 15:50:03 UTC,"Reviewed:  https://review.openstack.org/638803
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b041160c8d56f657059743bc5a0e6dbefc27ddd6
Submitter: Zuul
Branch:    stable/queens"
1805164,2019-02-14 23:08:35 UTC,"Reviewed:  https://review.openstack.org/636955
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=315d9fab7aaa6b9835e80f5f56b49b44d382ca1f
Submitter: Zuul
Branch:    stable/rocky"
1805164,2018-11-28 17:20:54 UTC,"As Takashi noted, disabling/enabling/forcing down/up services is only for compute services. There is no functional point to disabling conductor/scheduler/consoleauth. This was noted in the Pike release notes:"
1805164,2019-02-14 08:00:47 UTC,"Reviewed:  https://review.openstack.org/620667
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=95cbc35b0bdae0de15569bc35fadbcf970da5b9e
Submitter: Zuul
Branch:    master"
1805164,2018-11-29 09:53:22 UTC,This is not only about the error message. The command line client also should be fixed.
1805164,2018-11-28 17:54:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620667"
1805164,2018-11-27 09:52:41 UTC,So there is no way to disable other services? I would love to see that implemented
1805164,2018-11-27 09:35:46 UTC,"The ""PUT /os-services/disable"" API is just for a compute service (nova-compute).
It says that ""Disables scheduling for a Compute service."" in the compute API reference."
1805164,2018-11-26 15:39:02 UTC,"# nova-manage cell_v2 simple_cell_setup
Cell0 is already setup
All hosts are already mapped to cell(s), exiting."
1805164,2019-02-14 13:42:20 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/636955"
1805168,2019-07-03 21:07:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805169,2019-04-22 20:36:55 UTC,"FCE team is facing the same problem on all deployments.
juju run --application landscape-client 'sudo systemctl restart landscape-client.service'"
1805169,2019-05-08 20:34:21 UTC,This is still an issue with the upstream cs:landscape-client-31 charm.
1805170,2018-11-26 16:03:24 UTC,"Extend API to use Changes function in `overlord/configstate/transaction.go `func (t *Transaction) Changes() []string {`.
It returns changing keys associated with this transaction."
1805173,2019-04-29 22:29:06 UTC,"Somewhat related issue as well:
https://stackoverflow.com/a/48524106/8008576"
1805173,2019-04-29 21:38:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805174,2018-11-28 10:50:41 UTC,"Ok so, it's official that with 512MB you have to downgrade the CMA to 128MB:"
1805174,2018-11-28 10:52:20 UTC,Here is a pastebin of the above dmesg without the line wrap: http://paste.ubuntu.com/p/mGfz3St6c9/
1805174,2019-01-28 06:06:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805176,2019-02-04 16:46:02 UTC,"Bug 1805176 - tripleo jobs failing to setup bridge: fatal_signal|WARN|terminating with signal 14 (Alarm clock)
0 fails in 24 hrs / 0 fails in 10 days
Projects: (tripleo - Triaged)
No matches
Logstash Launchpad"
1805178,2019-01-31 12:00:31 UTC,"I suppose we need to ensure that the openldap package is using this abstraction, then, and that the latest apparmor package in Ubuntu contains it."
1805178,2019-01-30 04:17:25 UTC,[Expired for openldap (Ubuntu) because there has been no activity for 60 days.]
1805178,2018-11-30 18:42:35 UTC,"The above merge for apparmor appears to solve this issue. I agree with that issue that /etc/letsencrypt/live/** and /etc/letsencrypt/archive/** are probably the main places that have to be added. Shall we fix it in this package, or elsewhere?"
1805178,2018-11-29 19:44:53 UTC,I echo ahasenack's question. /etc/letsencrypt/** is pretty broad (especially if it contains private keys).
1805178,2018-11-29 18:59:03 UTC,Marked this public security for now so it is on the security team radar and it can be reviewed by them.
1805178,2018-11-29 18:42:50 UTC,Thanks for filing this bug in Ubuntu.
1805178,2018-11-30 15:49:48 UTC,"The ssl_certs and ssl_keys abstractions just got the paths for letsencrypt added:
    https://gitlab.com/apparmor/apparmor/merge_requests/283
(also backported to the 2.10..2.13 branches)"
1805178,2018-11-29 18:43:22 UTC,I'm removing apparmor from the affected list because the apparmor profile is shipped with slapd.
1805183,2018-12-13 09:08:52 UTC,"First of all, dhclient remaining in place is not a bug. Systems are not switching to netplan and networkd on upgrade."
1805183,2019-11-09 05:30:46 UTC,"All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1805183,2019-11-10 06:33:53 UTC,"I have tested Ubuntu Focal with systemd 243-3ubuntu1:
https://launchpad.net/ubuntu/+source/systemd/243-3ubuntu1
and the issue I have reported in Bug 1849608, which is marked as the duplicate of this bug, is gone now. Hence I confirmed the fix works here."
1805183,2019-11-14 15:00:40 UTC,"Hello Neil, or anyone else affected,"
1805183,2019-11-14 16:47:31 UTC,"with dnsmasq server setup to provide dhcp with 1m lease timeout, just run dhclient on test system:"
1805183,2019-11-14 17:11:39 UTC,LGTM on bionic
1805183,2019-11-15 00:55:07 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1805183,2019-11-15 13:36:48 UTC,"> ubuntu@srv-ywz63:~$ sudo dhclient eth0
> RTNETLINK answers: File exists
"
1805183,2019-11-15 14:19:01 UTC,"""I think you're trying to start dhclient on an interface that's already setup."""
1805183,2019-11-15 16:41:25 UTC,"Hello Neil, or anyone else affected,"
1805183,2019-11-16 02:55:53 UTC,"All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1805183,2019-11-25 11:18:51 UTC,This bug was fixed in the package systemd - 240-6ubuntu5.8
1805183,2019-11-25 11:19:21 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1805183,2019-11-26 03:14:42 UTC,"root@lp1805183-b:~# dpkg -l systemd|grep ii
ii  systemd        237-3ubuntu10.33 amd64        system and service manager
root@lp1805183-b:~# journalctl -b -u systemd-resolved | grep Started
Nov 26 03:04:30 lp1805183-b systemd[1]: Started Network Name Resolution.
root@lp1805183-b:~# dhclient ens8
cmp: EOF on /tmp/tmp.yJwQabpfMe which is empty
root@lp1805183-b:~# sleep 300 ; journalctl -b -u systemd-resolved | grep Started
Nov 26 03:04:30 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 26 03:06:06 lp1805183-b systemd[1]: Started Network Name Resolution."
1805183,2019-11-26 17:37:57 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.33
1805183,2019-11-09 00:51:32 UTC,"This has been wrongly marked as fixed in eoan.  It's not; the fix for this is still in eoan-proposed in systemd 242-7ubuntu3.2.  I don't know why the separate bug LP: #1849608 was used for that SRU vs this one.  Maybe the argument is that in eoan, systemd-resolved is *never* restarted, instead of being *always* restarted?  But I think they should be treated as the same bug."
1805183,2019-09-30 04:59:40 UTC,"Ok, I'll have a look at it; I only backported the Eoan fix to Bionic"
1805183,2019-11-09 01:02:56 UTC,"Hello Neil, or anyone else affected,"
1805183,2018-12-20 23:17:27 UTC,"@juliank
I *believe* this is impacting our AWS ubuntu EC2 machines and causing wild DNS errors impacting our users, I tried to apply the patch in this thread but it doesn't work, it complains like this"
1805183,2018-12-13 09:19:08 UTC,"The dbus API is only available in 239, which means we can't use it in bionic."
1805183,2018-12-13 09:23:27 UTC,"Ah no, 229, not 239 it seems."
1805183,2018-12-13 09:35:52 UTC,"I think just a delta change process would be fine. It's restarting when there is no change in lease details, and just clogging up the logs."
1805183,2018-12-17 10:21:03 UTC,Here's a patch while the git branch is pushing.
1805183,2018-12-17 10:25:30 UTC,"If we want to backport this to stable releases, we need a test case. What I came up with, as I was not able to simulate dhcp lease refreshes, is:"
1805183,2019-09-28 01:41:51 UTC,Steve in comment #9 I left a patch against the repo that iirc was working fine on my machines. Maybe it can be helpful. Thanks
1805183,2018-12-21 00:12:27 UTC,"been running for 1 hour, seems to be working as expected"
1805183,2019-05-30 19:13:11 UTC,"xnox, it looks like you're missing a ""$"" in md5sum command from:"
1805183,2019-10-28 00:13:03 UTC,I've found the patch applied to Eoan was the broken version where it used the bash'ism instead of the much more basic (and more portable) sh'ism of redirecting both STDOUT and STDERR.
1805183,2019-06-05 01:33:15 UTC,This bug was fixed in the package systemd - 240-6ubuntu9
1805183,2019-07-24 12:27:42 UTC,"For Info, I'm repearing an SRU upload for Bionic hopefully available by End Of Day"
1805183,2019-09-25 09:26:24 UTC,This still looks like an issue in Ubuntu 18.04 LTS. At least on systems that was upgraded from 14.04 release. I will disable systemd-resolved and revert to good old resolv.conf but what is the actual recommended workaround while the fix is not released?
1805183,2019-09-25 18:50:42 UTC,@tf8 the patch in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/comments/8 against a live server has been working fine for us on AWS for almost a year now.
1805183,2019-09-28 00:16:54 UTC,+              md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf &> $oldstate
1805183,2019-09-28 00:17:08 UTC,"An upload of systemd to bionic-proposed has been rejected from the upload queue for the following reason: ""wrong use of bashisms in shell script, does not work as intended""."
1805183,2019-09-28 00:18:57 UTC,This was also pointed out specifically in comment #8.
1805183,2019-05-30 20:15:57 UTC,Lol
1805185,2018-11-26 17:43:48 UTC,"That looks like a problem with your graphics driver. First, are you on the latest for your system? Second, try switching Mixxx's waveforms to Software rendering to work around the problem and let us know if that helps. (If you can't even start Mixxx, edit your mixxx.cfg file and set 'WaveformType 10'. then try starting it again.)"
1805185,2018-11-26 18:24:54 UTC,"Thank you for such a rapid response.  I do not need waveforms really so as
instructed I selected empty with no rendering other than overview. I am
using Tango skin at the moment. Is there anyway to completely remove any
waveform graphics with this skin or other skins available? I use MIXX as an
auto player of sorts in the background."
1805185,2018-11-26 18:38:38 UTC,"In Tango, you can click the waveform icon in the top bar to hide the waveforms. Alternatively you can drag the splitter to resize the waveforms and move it all the way to the top."
1805186,2019-02-04 16:41:12 UTC,"Bug 1805186 - tripleo jobs failing on ImageNotFoundException: Not found image: docker
0 fails in 24 hrs / 0 fails in 10 days
Projects: (tripleo - Triaged)
No matches
Logstash Launchpad"
1805186,2019-02-04 16:41:58 UTC,Let's monitor this a bit more.. if it continues to not be an issue we will close.
1805186,2019-03-19 13:34:34 UTC,Is this still an issue?
1805192,2018-11-26 22:56:07 UTC,Thank you for reporting this bug and helping to improve Ubuntu.
1805193,2019-02-26 03:36:14 UTC,"this is due to next part of the code haven't merged yet
https://review.openstack.org/#/c/168027/"
1805193,2019-09-25 09:50:49 UTC,This issue was fixed in the openstack/murano-dashboard 8.0.0.0rc1 release candidate.
1805193,2018-11-26 17:45:42 UTC,I'm not sure this code is even used.
1805193,2019-02-27 03:06:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639482"
1805193,2019-07-04 07:15:58 UTC,"Reviewed:  https://review.opendev.org/639482
Committed: https://git.openstack.org/cgit/openstack/murano-dashboard/commit/?id=dc0bc457139214251e483ed279f99c0cbafd1a7b
Submitter: Zuul
Branch:    master"
1805194,2018-11-26 21:41:00 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/620166"
1805194,2019-02-21 22:10:54 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/638519"
1805194,2019-02-21 22:13:00 UTC,"Change abandoned by Nagasai Vinaykumar Kapalavai (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/620166
Reason: Pushed change to incorrect branch."
1805194,2019-02-27 05:07:58 UTC,"Reviewed:  https://review.openstack.org/638519
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=63cc74e4bcdab117d353b54dc40ea27954e4e3bb
Submitter: Zuul
Branch:    stable/pike"
1805194,2019-05-14 14:37:17 UTC,This issue was fixed in the openstack/instack-undercloud 7.4.15 release.
1805197,2020-04-11 02:10:33 UTC,This bug seems still to be present in Xubuntu 20.04
1805197,2019-01-01 12:13:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805197,2018-12-04 21:08:11 UTC,It is a library for keyboard layout handling. The Ubuntu package used to include a patch which apparently fixes the problem with xfce4-keyboard-settings.
1805197,2018-11-29 10:11:19 UTC,"On Thu 2018-11-29 (09:50), Sebastien Bacher wrote:

> Thank you for your bug report, if it's a libxklavier issue then it
> should be reported upstream on
> https://bugs.freedesktop.org/enter_bug.cgi
"
1805197,2018-11-29 10:08:22 UTC,"The patch you mentioned as dropped by doko in this sync,
https://launchpad.net/ubuntu/+source/libxklavier/5.4-1"
1805197,2018-11-28 13:44:54 UTC,"Launchpad report:
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1805197"
1805197,2018-11-29 01:44:15 UTC,I tested. Thanks so much for fixing this!
1805197,2018-11-27 13:19:20 UTC,Building the libxklavier package with the dropped revert-default-group-change.patch file resolves the problem.
1805197,2018-01-22 10:43:38 UTC,It is very long time since this came in for me (4.10 -> 4.12 but I am not sure). Changing keyboard layout with enabled debug messages shows:
1805197,2018-11-29 09:50:47 UTC,"Thank you for your bug report, if it's a libxklavier issue then it should be reported upstream on https://bugs.freedesktop.org/enter_bug.cgi"
1805197,2018-11-27 11:27:59 UTC,This bug is not present anymore after downgrading the libxklavier package to the version from xenial (5.4-0ubuntu2).
1805208,2020-06-01 12:41:29 UTC,"Cannot repro anymore in Ubuntu 20.04, I suppose fixed"
1805208,2019-04-14 11:30:04 UTC,"Also repro on a different machine (Asus Zenbook Flip 15 UX561UD, Intel i915 Graphics)"
1805208,2018-11-26 19:18:58 UTC,"I am tagging this package-from-proposed because the package that crashes is from proposed (gnome-shell), though not the extension. I hope this is the right thing to do."
1805211,2019-10-10 13:59:58 UTC,https://github.com/snapcore/snapcraft/pull/2736
1805211,2019-10-16 21:32:55 UTC,https://github.com/snapcore/snapcraft/pull/2753
1805220,2019-07-24 12:37:40 UTC,this lives on the beta/remote-build branch for snapcraft
1805225,2020-06-04 16:06:31 UTC,Available as the `kde-neon` extension done by Sergio Schvezov.
1805225,2020-06-04 17:09:37 UTC,I tried the kde-neon snapcraft extension on arm64 and it did not work due I think to https://bugs.launchpad.net/snapcraft/+bug/1881963
1805226,2019-04-01 13:15:07 UTC,https://github.com/snapcore/snapcraft/pull/2398
1805227,2019-01-03 21:11:17 UTC,"One more argument in favor of issuing the delete: container listings may never have gotten the message about object deletes. This may lead to containers you can't easily delete via the S3 API (if, say, your s3 client is opinionated and only wants to issue multi-deletes). May be the root cause for https://ask.openstack.org/en/question/114715/s3-method-post-on-bucket-with-query-delete-doesnt-work/"
1805227,2019-01-04 06:16:34 UTC,"Tim, with reference to the ask.openstack query, the MultiPart object never received the delete, hence the container was not updated."
1805227,2019-01-04 23:50:17 UTC,"Thanks for the extra info Bhaskar! I wrote up https://bugs.launchpad.net/swift/+bug/1810567 to describe your trouble, and https://review.openstack.org/#/c/628701/ to fix it."
1805227,2019-01-07 03:30:38 UTC,"Thanks a lot, Tim!"
1805230,2020-02-22 08:48:32 UTC,Bug is not invalid. Ubuntu coders just ignore their bugs and focus on screwing up the next release.
1805231,2020-06-11 17:55:46 UTC,I cannot repro this anymore on 20.04
1805231,2018-11-26 19:59:30 UTC,"I am tagging this package-from-proposed because the package that apparently crashes is from proposed (gnome-shell), though not the extensions. I hope this is the right thing to do."
1805233,2020-09-25 10:33:09 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/754349"
1805233,2020-09-25 11:45:59 UTC,"Change abandoned by Harshavardhan Metla (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/754349
Reason: Changed in master in another commit"
1805233,2020-09-25 12:22:41 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/754365"
1805240,2018-11-30 19:28:05 UTC,"Thanks Ivan for your fix now in https://review.openstack.org/#/c/621186/ (now merged)
It seems to be working : http://logs.openstack.org/47/610547/1/check/openstack-tox-py27/33cd903/"
1805240,2019-05-09 22:23:47 UTC,This issue was fixed in the openstack/horizon 13.0.2 release.
1805240,2019-03-07 19:25:32 UTC,This issue was fixed in the openstack/horizon 15.0.0.0b2 development milestone.
1805240,2018-11-30 18:35:01 UTC,Ivan proposed a solution that was merged in to horizon: https://review.openstack.org/#/c/621186/
1805240,2019-05-10 18:42:32 UTC,This issue was fixed in the openstack/horizon 14.0.3 release.
1805240,2018-11-30 10:51:48 UTC,"@boden: That patch removes the utils.patch_middleware_get_user() from the setUp method of APITestCase, I think that causes the problem in networking-bgpvpn tests. So that patch introduced this test failure in networking-bgpvpn."
1805240,2018-11-27 04:14:51 UTC,"This happens in bgpvpn-dashboard test. I think some recent horizon change affects this, but I haven't checked it yet."
1805240,2018-11-30 14:49:45 UTC,"elod-illes I'm not familiar enough with the test/scenario to comment on the proper solution.
I do see that the no-op bgpvpn test patch https://review.openstack.org/#/c/620098/ is still failing. Perhaps someone needs to check with the dashboard team (or other)."
1805240,2018-11-29 21:17:40 UTC,"I don't think the fix in https://review.openstack.org/#/q/Ib9912090a87b716e7f5710f6f360b0df168ec2e3 is the solution. The patches in those reviews have merged, but the gate is still failing.
For example in: http://logs.openstack.org/periodic/git.openstack.org/openstack/networking-bgpvpn/master/openstack-tox-py35-with-neutron-lib-master/565dcb8/job-output.txt.gz"
1805240,2018-11-27 19:01:08 UTC,I think the change that causes this problem here is this bugfix in horizon: https://review.openstack.org/#/q/Ib9912090a87b716e7f5710f6f360b0df168ec2e3
1805241,2018-11-27 09:24:42 UTC,"Thank you for your bug report,  that request of working under sudo should be sent upstream on https://gitlab.gnome.org/GNOME/libsecret/issues"
1805241,2018-11-27 21:24:31 UTC,Done: https://gitlab.gnome.org/GNOME/libsecret/issues/19
1805241,2018-11-28 07:01:32 UTC,Thanks!
1805251,2018-11-30 06:34:00 UTC,I could not reproduce this at all... not on lxd provider not on aws...
1805251,2018-11-30 07:27:48 UTC,PR against 2.4: https://github.com/juju/juju/pull/9527
1805251,2018-12-03 00:54:34 UTC,PR for 2.5: https://github.com/juju/juju/pull/9533
1805256,2020-06-02 22:49:11 UTC,"Hello dann, or anyone else affected,"
1805256,2020-06-02 22:45:31 UTC,"Hello dann, or anyone else affected,"
1805256,2020-05-29 08:01:42 UTC,"Migrated right now, sponsoring the related SRU portions into B/E/F ... for consideration by the SRU Team."
1805256,2020-05-29 07:55:40 UTC,This bug was fixed in the package qemu - 1:4.2-3ubuntu8
1805256,2020-05-28 14:58:41 UTC,FYI: sponsored into groovy
1805256,2020-05-07 22:27:03 UTC,"Ike's backport in https://launchpad.net/~ikepanhc/+archive/ubuntu/lp1805256 tests well for me on Cavium Sabre. One minor note is that the function in_aio_context_home_thread() is being called in aio-win32.c, but that function didn't exist in 2.11. We probably want to change that to aio_context_in_iothread(). It was renamed in https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d2b63ba8dd20c1091b3f1033e6a95ef95b18149d"
1805256,2020-05-07 07:00:01 UTC,Tested debs in ppa:rafaeldtinoco/lp1805256 for focal and eoan and 1000 qemu-img convert passed.
1805256,2020-05-05 23:55:37 UTC,"fyi, I backported that fix also to focal/groovy and eoan, and with those builds. On my test systems the hang reliable occurs within 20 iterations. After the fix, they have survived > 500 iterations thus far. I'll leave running overnight just to be sure."
1805256,2020-05-06 19:57:26 UTC,"On Wed, May 6, 2020 at 1:20 PM Philippe Mathieu-Daudé
<email address hidden> wrote:

>
> Isn't this fixed by commit 5710a3e09f9?
"
1805256,2020-05-06 19:09:29 UTC,Isn't this fixed by commit 5710a3e09f9?
1805256,2020-06-02 22:54:33 UTC,"Hello dann, or anyone else affected,"
1805256,2020-05-05 18:48:06 UTC,"Hello Ike,"
1805256,2020-05-05 15:01:14 UTC,The test deb has been pushed to https://launchpad.net/~ikepanhc/+archive/ubuntu/lp1805256
1805256,2020-05-05 06:15:37 UTC,Thanks. I will test it.
1805256,2020-05-05 01:22:44 UTC,"Hi, Ike."
1805256,2020-05-05 00:54:27 UTC,"Take several CPUs offline and re-test. Even only 32 threads left, I still can reproduce this issue easily."
1805256,2020-05-06 20:11:21 UTC,"FYIO, from now on all the ""merge"" work will be done in the merge requests being linked to this BUG (at the top). @paelzer will be verifying those."
1805256,2020-06-03 04:09:37 UTC,"All autopkgtests for the newly accepted qemu (1:4.0+dfsg-0ubuntu9.7) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1805256,2020-06-17 05:16:43 UTC,"We had the 14 (instead f 7) days in -proposed for some extended maturing. Nothing came up in regard to this and all validations were good.
Dropping block-proposed to be released once the SRU Team gets to it."
1805256,2020-06-03 08:40:27 UTC,"All autopkgtests for the newly accepted qemu (1:4.2-3ubuntu6.2) for focal have finished running.
The following regressions have been reported in tests triggered by the package:"
1805256,2020-08-19 16:36:32 UTC,This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.31
1805256,2020-08-07 20:13:34 UTC,"Verified w/ over 500 successful iterations on a m6g.metal instance, and over 300 in an armhf chroot on the same."
1805256,2020-08-07 14:41:56 UTC,"All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.30) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1805256,2020-08-07 09:53:53 UTC,"Hello dann, or anyone else affected,"
1805256,2020-07-31 21:42:26 UTC,I just pushed/uploaded a SRU for bionic from:
1805256,2020-07-21 20:03:20 UTC,I've hidden last post as it was posted in the wrong bug.
1805256,2020-07-20 12:22:40 UTC,Thanks @dannf! I spoke to Christian and him and I agreed to confine this change into ARM builds only (as SRU for Bionic). Preparing it...
1805256,2020-07-15 15:31:15 UTC,"I ran the new PPA build (1:2.11+dfsg-1ubuntu7.29~ppa01) on both a ThunderX2 system and a Hi1620 system overnight, and both survived (6574 & 12919 iterations, respectively)."
1805256,2020-07-13 04:12:00 UTC,Worked being done for the Bionic SRU:
1805256,2020-07-12 13:16:31 UTC,Started working on this again...
1805256,2020-07-01 07:01:49 UTC,Re-open for bionic due to regression found
1805256,2020-06-30 06:54:56 UTC,"This will re-open again for Bionic due to bug 1885419 forcing a revert of the former backports.
After a deeper evaluation if the assert is wrong in the backport or just flagging a problem formerly already existing in Bionic this will be re-fixed."
1805256,2020-06-18 09:39:05 UTC,This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.27
1805256,2020-06-18 09:38:29 UTC,This bug was fixed in the package qemu - 1:4.0+dfsg-0ubuntu9.7
1805256,2020-05-04 07:24:06 UTC,PPA created with temporarily workaround in comment #34.
1805256,2020-06-18 09:23:26 UTC,This bug was fixed in the package qemu - 1:4.2-3ubuntu6.2
1805256,2020-06-05 03:51:39 UTC,"I've looked and retried the tests - all green now.
Let us give it a few extra days in proposed as planned, but other than that it looks ok to be released."
1805256,2020-06-03 06:35:25 UTC,100 run on bionic/eoan/focal -proposed `qemu-img convert` all successful. No hang occurs. Thanks a lot.
1805256,2020-06-18 09:23:33 UTC,"The verification of the Stable Release Update for qemu has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1805256,2020-02-13 09:20:29 UTC,"=》Could HiSilicon respond to Dann & Rafael's comments #36 and #38?
=》Is there an upstream acceptable patch that addresses this issue?"
1805256,2019-12-18 14:52:52 UTC,"fyi, what I tested in Comment #35 was upstream QEMU (@ aceeaa69d2) with a port of the patch in Comment #34 applied. I've attached that patch here. While it did avoid the issue in my testing, I agree with Rafael's Comment #36 that it does not appear to address the root cause (as I understand it), and is therefore unlikely something we'd ship in Ubuntu."
1805256,2019-09-11 02:15:00 UTC,"Paolo,"
1805256,2019-09-10 22:56:25 UTC,QEMU BUG: #1
1805256,2020-02-13 08:42:42 UTC,"Could HiSilicon respond to Dann & Rafael's comments #36 and #38?
Is there an upstream acceptable patch that addresses this issue?"
1805256,2019-09-10 02:04:59 UTC,"Alright,"
1805256,2019-09-09 16:47:25 UTC,"Alright, with a d06 aarch64 machine I was able to reproduce it after 8 attempts.I'll debug it today and provide feedback on my findings."
1805256,2019-09-06 21:22:42 UTC,"Alright, I couldn't reproduce this yet, I'm running same test case in a 24 cores box and causing lots of context switches and CPU migrations in parallel (trying to exhaust the logic)."
1805256,2019-09-06 15:16:57 UTC,"OOhh nm on the virtual environment test, as I just remembered we don't have KVM on 2nd level for aarch64 yet (at least in ARMv8 implementing virt extension). I'll try to reproduce in the real env only."
1805256,2019-09-11 02:17:15 UTC,"In comment #14, please disregard the second half of the issue, related to:"
1805256,2019-09-06 15:12:44 UTC,"Hello Liz,"
1805256,2019-04-16 13:32:03 UTC,"frazier, Do you find the conditions that necessarily make this problem appear?"
1805256,2019-04-16 08:16:52 UTC,Do you have any good ideas about it? Maybe somewhere lack of memeory barriers that cause it?
1805256,2019-04-15 23:37:35 UTC,"No, sorry - this bugs still persists w/ latest upstream (@ afccfc0). I found a report of similar symptoms:"
1805256,2019-04-15 14:37:48 UTC,"sorry, I make a spelling mistake here（""Hi, I also found a problem that qemu-img convert hands in ARM.""）.The right is ""I also found a problem that qemu-img convert hangs in ARM""."
1805256,2019-04-15 12:59:20 UTC,"Hi, I also found a problem that qemu-img convert hands in ARM."
1805256,2018-11-26 23:54:21 UTC,"ext4 filesystem, SATA drive:"
1805256,2018-11-26 23:26:10 UTC,"Hi, can you do a `thread apply all bt` instead? If I were to bet, we're probably waiting for some slow call like lseek to return in another thread."
1805256,2019-04-23 01:29:40 UTC,"I can reproduce this problem with qemu.git/matser. It still exists in qemu.git/matser. I found that when an IO return in worker threads and want to call aio_notify to wake up main_loop, but it found that ctx->notify_me is cleared to 0 by main_loop in aio_ctx_check by calling atomic_and(&ctx->notify_me, ~1) . So worker thread won't write enventfd to notify main_loop.If such a scene happens, the main_loop will hang:
    main loop                        worker thread1                  worker thread2
-----------------------------------------------------------------------------------------------
    qemu_poll_ns                    aio_worker
                            qemu_bh_schedule(pool->completion_bh)
    glib_pollfds_poll
    g_main_context_check
    aio_ctx_check
    atomic_and(&ctx->notify_me, ~1)                                aio_worker
                                                      qemu_bh_schedule(pool->completion_bh)
    /* do something for event */
    qemu_poll_ns
    /* hangs !!!*/"
1805256,2019-09-11 07:05:41 UTC,Quick update...
1805256,2019-09-10 14:16:48 UTC,"Alright, here is what is happening:"
1805256,2019-09-24 20:25:17 UTC,"On Wed, Sep 11, 2019 at 04:09:25PM -0300, Rafael David Tinoco wrote:

> > Zhengui's theory that notify_me doesn't work properly on ARM is more
> > promising, but he couldn't provide a clear explanation of why he thought
> > notify_me is involved.  In particular, I would have expected notify_me to
> > be wrong if the qemu_poll_ns call came from aio_ctx_dispatch, for example:
> >
> >
> >     glib_pollfds_fill
> >       g_main_context_prepare
> >         aio_ctx_prepare
> >           atomic_or(&ctx->notify_me, 1)
> >     qemu_poll_ns
> >     glib_pollfds_poll
> >       g_main_context_check
> >         aio_ctx_check
> >           atomic_and(&ctx->notify_me, ~1)
> >       g_main_context_dispatch
> >         aio_ctx_dispatch
> >           /* do something for event */
> >             qemu_poll_ns
> >
>
> Paolo,
>
> I tried confining execution in a single NUMA domain (cpu & mem) and
> still faced the issue, then, I added a mutex ""ctx->notify_me_lcktest""
> into context to protect ""ctx->notify_me"", like showed bellow, and it
> seems to have either fixed or mitigated it.
>
> I was able to cause the hung once every 3 or 4 runs. I have already ran
> qemu-img convert more than 30 times now and couldn't reproduce it again.
>
> Next step is to play with the barriers and check why existing ones
> aren't enough for ordering access to ctx->notify_me ... or should I
> try/do something else in your opinion ?
>
> This arch/machine (Huawei D06):
>
> $ lscpu
> Architecture:        aarch64
> Byte Order:          Little Endian
> CPU(s):              96
> On-line CPU(s) list: 0-95
> Thread(s) per core:  1
> Core(s) per socket:  48
> Socket(s):           2
> NUMA node(s):        4
> Vendor ID:           0x48
> Model:               0
> Stepping:            0x0
> CPU max MHz:         2000.0000
> CPU min MHz:         200.0000
> BogoMIPS:            200.00
> L1d cache:           64K
> L1i cache:           64K
> L2 cache:            512K
> L3 cache:            32768K
> NUMA node0 CPU(s):   0-23
> NUMA node1 CPU(s):   24-47
> NUMA node2 CPU(s):   48-71
> NUMA node3 CPU(s):   72-95
> Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics
> cpuid asimdrdm dcpop
"
1805256,2019-12-18 09:52:27 UTC,"I tested the patch in Comment #34, and it was also failed to pass 5 iterations.
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type ""show copying""
and ""show warranty"" for details.
This GDB was configured as ""aarch64-linux-gnu"".
Type ""show configuration"" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type ""help"".
Type ""apropos word"" to search for commands related to ""word"".
Attaching to process 3987
[New LWP 3988]
[Thread debugging using libthread_db enabled]
Using host libthread_db library ""/lib/aarch64-linux-gnu/libthread_db.so.1"".
0x0000ffffbd2b3154 in __GI_ppoll (fds=0xaaaae80ef080, nfds=187650381360708,
    timeout=<optimized out>, sigmask=0xffffc31815f0)
    at ../sysdeps/unix/sysv/linux/ppoll.c:39
39	../sysdeps/unix/sysv/linux/ppoll.c: No such file or directory.
(gdb)"
1805256,2019-12-18 02:40:46 UTC,"Hello Fred,"
1805256,2019-12-17 19:17:19 UTC,"I tested the patch in Comment #34, and it was able to pass 500 iterations."
1805256,2019-09-11 19:09:25 UTC,"> Zhengui's theory that notify_me doesn't work properly on ARM is more
> promising, but he couldn't provide a clear explanation of why he thought
> notify_me is involved.  In particular, I would have expected notify_me to
> be wrong if the qemu_poll_ns call came from aio_ctx_dispatch, for example:
>
>
>     glib_pollfds_fill
>       g_main_context_prepare
>         aio_ctx_prepare
>           atomic_or(&ctx->notify_me, 1)
>     qemu_poll_ns
>     glib_pollfds_poll
>       g_main_context_check
>         aio_ctx_check
>           atomic_and(&ctx->notify_me, ~1)
>       g_main_context_dispatch
>         aio_ctx_dispatch
>           /* do something for event */
>             qemu_poll_ns
>
"
1805256,2019-10-11 17:55:36 UTC,"On Fri, Oct 11, 2019 at 08:30:02AM +0000, Jan Glauber wrote:

> On Fri, Oct 11, 2019 at 10:18:18AM +0200, Paolo Bonzini wrote:
> > On 11/10/19 08:05, Jan Glauber wrote:
> > > On Wed, Oct 09, 2019 at 11:15:04AM +0200, Paolo Bonzini wrote:
> > >>> ...but if I bump notify_me size to uint64_t the issue goes away.
> > >>
> > >> Ouch. :)  Is this with or without my patch(es)?
> >
> > You didn't answer this question.
>
> Oh, sorry... I did but the mail probably didn't make it out.
> I have both of your changes applied (as I think they make sense).
>
> > >> Also, what if you just add a dummy uint32_t after notify_me?
> > >
> > > With the dummy the testcase also runs fine for 500 iterations.
> >
> > You might be lucky and causing list_lock to be in another cache line.
> > What if you add __attribute__((aligned(16)) to notify_me (and keep the
> > dummy)?
>
> Good point. I'll try to force both into the same cacheline.
"
1805256,2019-10-11 17:50:06 UTC,"On Fri, Oct 11, 2019 at 06:05:25AM +0000, Jan Glauber wrote:

> On Wed, Oct 09, 2019 at 11:15:04AM +0200, Paolo Bonzini wrote:
> > On 09/10/19 10:02, Jan Glauber wrote:
>
> > > I'm still not sure what the actual issue is here, but could it be some bad
> > > interaction between the notify_me and the list_lock? The are both 4 byte
> > > and side-by-side:
> > >
> > > address notify_me: 0xaaaadb528aa0  sizeof notify_me: 4
> > > address list_lock: 0xaaaadb528aa4  sizeof list_lock: 4
> > >
> > > AFAICS the generated code looks OK (all load/store exclusive done
> > > with 32 bit size):
> > >
> > >      e6c:       885ffc01        ldaxr   w1, [x0]
> > >      e70:       11000821        add     w1, w1, #0x2
> > >      e74:       8802fc01        stlxr   w2, w1, [x0]
> > >
> > > ...but if I bump notify_me size to uint64_t the issue goes away.
> >
> > Ouch. :)  Is this with or without my patch(es)?
> >
> > Also, what if you just add a dummy uint32_t after notify_me?
>
> With the dummy the testcase also runs fine for 500 iterations.
>
> Dann, can you try if this works on the Hi1620 too?
"
1805256,2019-10-11 08:30:02 UTC,"On Fri, Oct 11, 2019 at 10:18:18AM +0200, Paolo Bonzini wrote:

> On 11/10/19 08:05, Jan Glauber wrote:
> > On Wed, Oct 09, 2019 at 11:15:04AM +0200, Paolo Bonzini wrote:
> >>> ...but if I bump notify_me size to uint64_t the issue goes away.
> >>
> >> Ouch. :)  Is this with or without my patch(es)?
>
> You didn't answer this question.
"
1805256,2019-10-11 06:05:25 UTC,"On Wed, Oct 09, 2019 at 11:15:04AM +0200, Paolo Bonzini wrote:

> On 09/10/19 10:02, Jan Glauber wrote:
"
1805256,2019-12-17 01:34:00 UTC," include/block/aio.h | 3 +++
 qemu-img.c          | 4 ++++
 util/async.c        | 5 +----
 3 files changed, 8 insertions(+), 4 deletions(-)"
1805256,2019-10-07 14:44:32 UTC,"On Mon, Oct 07, 2019 at 01:06:20PM +0200, Paolo Bonzini wrote:

> On 02/10/19 11:23, Jan Glauber wrote:
> > I've looked into this on ThunderX2. The arm64 code generated for the
> > atomic_[add|sub] accesses of ctx->notify_me doesn't contain any
> > memory barriers. It is just plain ldaxr/stlxr.
> >
> > From my understanding this is not sufficient for SMP sync.
> >
> > If I read this comment correct:
> >
> >     void aio_notify(AioContext *ctx)
> >     {
> >         /* Write e.g. bh->scheduled before reading ctx->notify_me.  Pairs
> >          * with atomic_or in aio_ctx_prepare or atomic_add in aio_poll.
> >          */
> >         smp_mb();
> >         if (ctx->notify_me) {
> >
> > it points out that the smp_mb() should be paired. But as
> > I said the used atomics don't generate any barriers at all.
>
> Based on the rest of the thread, this patch should also fix the bug:
>
> diff --git a/util/async.c b/util/async.c
> index 47dcbfa..721ea53 100644
> --- a/util/async.c
> +++ b/util/async.c
> @@ -249,7 +249,7 @@ aio_ctx_check(GSource *source)
>      aio_notify_accept(ctx);
>
>      for (bh = ctx->first_bh; bh; bh = bh->next) {
> -        if (bh->scheduled) {
> +        if (atomic_mb_read(&bh->scheduled)) {
>              return true;
>          }
>      }
>
>
> And also the memory barrier in aio_notify can actually be replaced
> with a SEQ_CST load:
>
> diff --git a/util/async.c b/util/async.c
> index 47dcbfa..721ea53 100644
> --- a/util/async.c
> +++ b/util/async.c
> @@ -349,11 +349,11 @@ LinuxAioState *aio_get_linux_aio(AioContext *ctx)
>
>  void aio_notify(AioContext *ctx)
>  {
> -    /* Write e.g. bh->scheduled before reading ctx->notify_me.  Pairs
> -     * with atomic_or in aio_ctx_prepare or atomic_add in aio_poll.
> +    /* Using atomic_mb_read ensures that e.g. bh->scheduled is written before
> +     * ctx->notify_me is read.  Pairs with atomic_or in aio_ctx_prepare or
> +     * atomic_add in aio_poll.
>       */
> -    smp_mb();
> -    if (ctx->notify_me) {
> +    if (atomic_mb_read(&ctx->notify_me)) {
>          event_notifier_set(&ctx->notifier);
>          atomic_mb_set(&ctx->notified, true);
>      }
>
>
> Would you be able to test these (one by one possibly)?
"
1805256,2019-10-07 14:36:38 UTC,"On Mon, Oct 07, 2019 at 01:06:20PM +0200, Paolo Bonzini wrote:

> On 02/10/19 11:23, Jan Glauber wrote:
> > I've looked into this on ThunderX2. The arm64 code generated for the
> > atomic_[add|sub] accesses of ctx->notify_me doesn't contain any
> > memory barriers. It is just plain ldaxr/stlxr.
> >
> > From my understanding this is not sufficient for SMP sync.
> >
> > If I read this comment correct:
> >
> >     void aio_notify(AioContext *ctx)
> >     {
> >         /* Write e.g. bh->scheduled before reading ctx->notify_me.  Pairs
> >          * with atomic_or in aio_ctx_prepare or atomic_add in aio_poll.
> >          */
> >         smp_mb();
> >         if (ctx->notify_me) {
> >
> > it points out that the smp_mb() should be paired. But as
> > I said the used atomics don't generate any barriers at all.
>
> Based on the rest of the thread, this patch should also fix the bug:
>
> diff --git a/util/async.c b/util/async.c
> index 47dcbfa..721ea53 100644
> --- a/util/async.c
> +++ b/util/async.c
> @@ -249,7 +249,7 @@ aio_ctx_check(GSource *source)
>      aio_notify_accept(ctx);
>
>      for (bh = ctx->first_bh; bh; bh = bh->next) {
> -        if (bh->scheduled) {
> +        if (atomic_mb_read(&bh->scheduled)) {
>              return true;
>          }
>      }
>
>
> And also the memory barrier in aio_notify can actually be replaced
> with a SEQ_CST load:
>
> diff --git a/util/async.c b/util/async.c
> index 47dcbfa..721ea53 100644
> --- a/util/async.c
> +++ b/util/async.c
> @@ -349,11 +349,11 @@ LinuxAioState *aio_get_linux_aio(AioContext *ctx)
>
>  void aio_notify(AioContext *ctx)
>  {
> -    /* Write e.g. bh->scheduled before reading ctx->notify_me.  Pairs
> -     * with atomic_or in aio_ctx_prepare or atomic_add in aio_poll.
> +    /* Using atomic_mb_read ensures that e.g. bh->scheduled is written before
> +     * ctx->notify_me is read.  Pairs with atomic_or in aio_ctx_prepare or
> +     * atomic_add in aio_poll.
>       */
> -    smp_mb();
> -    if (ctx->notify_me) {
> +    if (atomic_mb_read(&ctx->notify_me)) {
>          event_notifier_set(&ctx->notifier);
>          atomic_mb_set(&ctx->notified, true);
>      }
>
>
> Would you be able to test these (one by one possibly)?
"
1805256,2019-10-03 12:29:09 UTC,"On 02/10/19 16:58, Torvald Riegel wrote:

> This example looks like Dekker synchronization (if I get the intent right).
"
1805256,2019-10-03 12:29:00 UTC,"On Wed, 2019-10-02 at 15:20 +0200, Paolo Bonzini wrote:

> On 02/10/19 13:05, Jan Glauber wrote:
>> The arm64 code generated for the
>> atomic_[add|sub] accesses of ctx->notify_me doesn't contain any
>> memory barriers. It is just plain ldaxr/stlxr.
>>
>> From my understanding this is not sufficient for SMP sync.
>>
>>>> If I read this comment correct:
>>>>
>>>>     void aio_notify(AioContext *ctx)
>>>>     {
>>>>         /* Write e.g. bh->scheduled before reading ctx->notify_me.  Pairs
>>>>          * with atomic_or in aio_ctx_prepare or atomic_add in aio_poll.
>>>>          */
>>>>         smp_mb();
>>>>         if (ctx->notify_me) {
>>>>
>>>> it points out that the smp_mb() should be paired. But as
>>>> I said the used atomics don't generate any barriers at all.
>>>
>>> Awesome!  That would be a compiler bug though, as atomic_add and atomic_sub
>>> are defined as sequentially consistent:
>>>
>>> #define atomic_add(ptr, n) ((void) __atomic_fetch_add(ptr, n, __ATOMIC_SEQ_CST))
>>> #define atomic_sub(ptr, n) ((void) __atomic_fetch_sub(ptr, n, __ATOMIC_SEQ_CST))
>>
>> Compiler bug sounds kind of unlikely...
>
> Indeed the assembly produced by the compiler matches for example the
> mappings at https://www.cl.cam.ac.uk/~pes20/cpp/cpp0xmappings.html.  A
> small testcase is as follows:
>
>   int ctx_notify_me;
>   int bh_scheduled;
>
>   int x()
>   {
>       int one = 1;
>       int ret;
>       __atomic_store(&bh_scheduled, &one, __ATOMIC_RELEASE);     // x1
>       __atomic_thread_fence(__ATOMIC_SEQ_CST);                   // x2
>       __atomic_load(&ctx_notify_me, &ret, __ATOMIC_RELAXED);     // x3
>       return ret;
>   }
>
>   int y()
>   {
>       int ret;
>       __atomic_fetch_add(&ctx_notify_me, 2, __ATOMIC_SEQ_CST);  // y1
>       __atomic_load(&bh_scheduled, &ret, __ATOMIC_RELAXED);     // y2
>       return ret;
>   }
>
> Here y (which is aio_poll) wants to order the write to ctx->notify_me
> before reads of bh->scheduled.  However, the processor can speculate the
> load of bh->scheduled between the load-acquire and store-release of
> ctx->notify_me.  So you can have something like:
>
>  thread 0 (y)                          thread 1 (x)
>  -----------------------------------   -----------------------------
>  y1: load-acq ctx->notify_me
>  y2: load-rlx bh->scheduled
>                                        x1: store-rel bh->scheduled <-- 1
>                                        x2: memory barrier
>                                        x3: load-rlx ctx->notify_me
>  y1: store-rel ctx->notify_me <-- 2
>
> Being very puzzled, I tried to put this into cppmem:
>
>   int main() {
>     atomic_int ctx_notify_me = 0;
>     atomic_int bh_scheduled = 0;
>     {{{ {
>           bh_scheduled.store(1, mo_release);
>           atomic_thread_fence(mo_seq_cst);
>           // must be zero since the bug report shows no notification
>           ctx_notify_me.load(mo_relaxed).readsvalue(0);
>         }
>     ||| {
>           ctx_notify_me.store(2, mo_seq_cst);
>           r2=bh_scheduled.load(mo_relaxed);
>         }
>     }}};
>     return 0;
>   }
>
> and much to my surprise, the tool said r2 *can* be 0.  Same if I put a
> CAS like
>
>        ...
"
1805256,2019-10-03 12:28:50 UTC,Documenting this here as bug# was dropped from the mail thread:
1805256,2019-10-02 11:05:59 UTC,"On Wed, Oct 02, 2019 at 11:45:19AM +0200, Paolo Bonzini wrote:

> On 02/10/19 11:23, Jan Glauber wrote:
> > I've tried to verify me theory with this patch and didn't run into the
> > issue for ~500 iterations (usually I would trigger the issue ~20 iterations).
>
> Awesome!  That would be a compiler bug though, as atomic_add and atomic_sub
> are defined as sequentially consistent:
>
> #define atomic_add(ptr, n) ((void) __atomic_fetch_add(ptr, n, __ATOMIC_SEQ_CST))
> #define atomic_sub(ptr, n) ((void) __atomic_fetch_sub(ptr, n, __ATOMIC_SEQ_CST))
"
1805256,2019-10-02 11:02:52 UTC,Debug files for aio-posix generated on 18.04 on ThunderX2.
1805256,2019-10-02 09:23:00 UTC,"I've looked into this on ThunderX2. The arm64 code generated for the
atomic_[add|sub] accesses of ctx->notify_me doesn't contain any
memory barriers. It is just plain ldaxr/stlxr."
1805256,2019-10-09 08:02:38 UTC,"On Mon, Oct 07, 2019 at 04:58:30PM +0200, Paolo Bonzini wrote:

> On 07/10/19 16:44, dann frazier wrote:
> > On Mon, Oct 07, 2019 at 01:06:20PM +0200, Paolo Bonzini wrote:
> >> On 02/10/19 11:23, Jan Glauber wrote:
> >>> I've looked into this on ThunderX2. The arm64 code generated for the
> >>> atomic_[add|sub] accesses of ctx->notify_me doesn't contain any
> >>> memory barriers. It is just plain ldaxr/stlxr.
> >>>
> >>> From my understanding this is not sufficient for SMP sync.
> >>>
> >>> If I read this comment correct:
> >>>
> >>>     void aio_notify(AioContext *ctx)
> >>>     {
> >>>         /* Write e.g. bh->scheduled before reading ctx->notify_me.  Pairs
> >>>          * with atomic_or in aio_ctx_prepare or atomic_add in aio_poll.
> >>>          */
> >>>         smp_mb();
> >>>         if (ctx->notify_me) {
> >>>
> >>> it points out that the smp_mb() should be paired. But as
> >>> I said the used atomics don't generate any barriers at all.
> >>
> >> Based on the rest of the thread, this patch should also fix the bug:
> >>
> >> diff --git a/util/async.c b/util/async.c
> >> index 47dcbfa..721ea53 100644
> >> --- a/util/async.c
> >> +++ b/util/async.c
> >> @@ -249,7 +249,7 @@ aio_ctx_check(GSource *source)
> >>      aio_notify_accept(ctx);
> >>
> >>      for (bh = ctx->first_bh; bh; bh = bh->next) {
> >> -        if (bh->scheduled) {
> >> +        if (atomic_mb_read(&bh->scheduled)) {
> >>              return true;
> >>          }
> >>      }
> >>
> >>
> >> And also the memory barrier in aio_notify can actually be replaced
> >> with a SEQ_CST load:
> >>
> >> diff --git a/util/async.c b/util/async.c
> >> index 47dcbfa..721ea53 100644
> >> --- a/util/async.c
> >> +++ b/util/async.c
> >> @@ -349,11 +349,11 @@ LinuxAioState *aio_get_linux_aio(AioContext *ctx)
> >>
> >>  void aio_notify(AioContext *ctx)
> >>  {
> >> -    /* Write e.g. bh->scheduled before reading ctx->notify_me.  Pairs
> >> -     * with atomic_or in aio_ctx_prepare or atomic_add in aio_poll.
> >> +    /* Using atomic_mb_read ensures that e.g. bh->scheduled is written before
> >> +     * ctx->notify_me is read.  Pairs with atomic_or in aio_ctx_prepare or
> >> +     * atomic_add in aio_poll.
> >>       */
> >> -    smp_mb();
> >> -    if (ctx->notify_me) {
> >> +    if (atomic_mb_read(&ctx->notify_me)) {
> >>          event_notifier_set(&ctx->notifier);
> >>          atomic_mb_set(&ctx->notified, true);
> >>      }
> >>
> >>
> >> Would you be able to test these (one by one possibly)?
> >
> > Paolo,
> >   I tried them both separately and together on a Hi1620 system, each
> > time it hung in the first iteration. Here's a backtrace of a run with
> > both patches applied:
>
> Ok, not a great start...  I'll find myself an aarch64 machine and look
> at it more closely.  I'd like the patch to be something we can
> understand and document, since this is probably the second most-used
> memory barrier idiom in QEMU.
>
> Paolo
"
1805257,2019-07-22 04:07:15 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1805257,2018-11-28 14:19:28 UTC,"@Daniel, yes, even disabling all extensions I still have the issue."
1805257,2018-11-27 02:17:11 UTC,Quick sanity check: Can you please try disabling/removing all extensions:
1805302,2018-11-27 17:03:20 UTC,"Additional info: I observe this bug in Raspberry Pi 3 B+ with ""RASPBIAN STRETCH WITH DESKTOP AND RECOMMENDED SOFTWARE"" released on 2018-11-13. Mouse is Logitech RX250."
1805306,2020-03-09 11:24:12 UTC,"Hi,"
1805306,2020-03-10 01:33:05 UTC,I don't remember... Please close.  Kentarou
1805307,2020-09-16 16:57:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805307,2020-09-16 17:15:25 UTC,I just switched from Xfce to KDE.  I'm experiencing the same problem with Okular Version 1.9.3 on a new installation of Kubuntu 20.04.
1805315,2020-02-08 12:53:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805319,2020-05-23 04:17:23 UTC,[Expired for tempest because there has been no activity for 60 days.]
1805319,2020-03-23 18:54:23 UTC,"Due to a long inactivity here we can say the bug is not in Progress , also due to a older report, could you, please, provide if the issue is still valid and per previous comment provide also tempest.conf used."
1805319,2019-09-06 02:08:26 UTC,can you post tempest.conf
1805322,2018-11-27 11:56:12 UTC,"    global CONFIGS
    if not config('action-managed-upgrade'):
        if openstack_upgrade_available('neutron-common'):
            status_set('maintenance', 'Running openstack upgrade')
            do_openstack_upgrade(CONFIGS)"
1805322,2018-11-27 11:57:54 UTC,The config-changed hook does directly install packages; that needs updating to be aware of action managed upgrades.
1805322,2019-08-02 09:26:58 UTC,"In BootStack, we also run the upgrade procedure via actions."
1805322,2019-08-02 10:09:09 UTC,"The above error when installing python3-neutron does not happen if the upgrade is stepped:
Note: from distro (bionic queens):
2b) juju config neutron-api --reset action-managed-upgrade
3b) juju config neutron-api openstack-origin='cloud:bionic-rocky'
3c) juju config neutron-api openstack-origin='cloud:bionic-stein'"
1805322,2019-10-24 14:53:49 UTC,Subscribing field-medium.
1805322,2019-10-24 14:54:17 UTC,Subscribing field-medium.
1805322,2019-10-24 15:02:55 UTC,"As a cowboy to work around this, I temporarily set apt_install fatal=False at:"
1805322,2020-11-18 14:43:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/763196"
1805322,2020-11-23 15:45:27 UTC,The issue got fixed on commit 518ae9a0 [1].
1805322,2020-11-23 16:16:56 UTC,"This test worked as expected:
""""""
juju deploy --series xenial neutron-api --config openstack-origin=distro
juju deploy --series xenial keystone --config openstack-origin=distro
juju deploy --series xenial percona-cluster --config source=distro
juju deploy --series xenial rabbitmq-server --config source=distro
juju status
juju add-relation keystone percona-cluster
juju add-relation neutron-api percona-cluster
juju add-relation neutron-api keystone
juju add-relation neutron-api rabbitmq-server
juju config neutron-api action-managed-upgrade=true
juju config neutron-api openstack-origin=""cloud:xenial-pike""
juju run-action --wait neutron-api/leader openstack-upgrade
juju config neutron-api openstack-origin=""cloud:xenial-queens""
juju run-action --wait neutron-api/leader openstack-upgrade
"""""""
1805338,2020-05-20 17:13:14 UTC,This bug was fixed in the package snort - 2.9.15.1-2
1805340,2018-11-27 08:29:30 UTC,"An update to the above description:
I was quite sure batch_timeout = None worked in my test, but I couldn't reproduce it.
Finally I had to set request_timeout = 45.0, but this option is marked as deprecated."
1805340,2019-08-13 17:19:59 UTC,@christian-zunker:
1805347,2018-11-27 08:26:41 UTC,I use OpenStack Rocky.
1805347,2018-11-27 10:27:26 UTC,"I comment `whoami` = ""root"" to skip this condition."
1805357,2018-11-27 21:41:28 UTC,"Thanks for reporting, I'll try to reproduce today."
1805357,2018-11-27 23:31:45 UTC,"Thanks for taking the time to report this bug.
This bug report is debatable because there are at least two sources claiming that the indent size can be 4. If you have time and can still reproduce the bug, please read pep8 ( https://bugzilla.gnome.org/bug-HOWTO.html ). Since bash8 was built to be equivalent to pep8, it could be a good reference to the correct number of spaces. Also, read Bash Style Guide and Coding Standard ( https://lug.fh-swf.de/vim/vim-bash/StyleGuideShell.en.pdf ), which describes the guidelines specifically for bash. It says that both 2 or 4 spaces might be used."
1805358,2018-12-03 07:09:33 UTC,Thanks!
1805358,2018-12-05 13:53:53 UTC,boot-and-services passed on all arches in cosmic autopkgtests.
1805358,2018-12-04 17:10:17 UTC,"Hello Christian, or anyone else affected,"
1805358,2018-12-01 02:54:06 UTC,This bug was fixed in the package systemd - 239-7ubuntu14
1805358,2018-11-27 14:03:54 UTC,"Reproducing the bug:
- of course it had to work reliably on a local amd64
- ppc based autopkgtest has the usual non-fun of bug 1630909 still failing me"
1805358,2018-11-27 15:48:59 UTC,"FYI - there is a chance that it works - by chance one of my retries now worked.
But given the low percentage I still think we should fix it to some way ignore that error."
1805358,2018-11-27 14:34:40 UTC,I wonder what you'd think about either:
1805358,2018-11-27 14:12:34 UTC,"It seems to me that this:
+  * boot-and-services: skip gdm test, when gdm-x-session fails.
+    Across all architectures, gdm fails to come up reliably since cosmic.
+    (LP: #1790478)"
1805358,2018-11-28 06:55:45 UTC,"Since it most reliably fails on LP infra and almost never locally I tried to verify it in [1][2]
But this becomes a can of worms hitting [3] now."
1805360,2018-11-29 21:05:25 UTC,The package has been published and the bug is being set to Fix Released
1805362,2018-11-29 08:53:11 UTC,"4.15.0-1029.30 - aws
Regression test CMPL, RTB."
1805362,2018-11-30 14:29:21 UTC,The package has been published and the bug is being set to Fix Released
1805363,2019-09-27 09:10:03 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1805363,2019-09-14 16:16:30 UTC,"Reviewed:  https://review.opendev.org/680794
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4f0c7394ede6ad479ff911bc373370f8b5e2f6f1
Submitter: Zuul
Branch:    master"
1805363,2019-09-13 04:39:12 UTC,"Reviewed:  https://review.opendev.org/680793
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=7a6c020a549e63fbfebd72e5d945d2b1d5204990
Submitter: Zuul
Branch:    master"
1805363,2019-09-07 02:27:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680793"
1805363,2019-07-23 14:22:33 UTC,We discussed this during the kesytone virtual midcycle. Bumping the priority of this to Low since we don't know of anyone using oauth1.
1805363,2019-09-07 02:27:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680794"
1805365,2018-12-04 05:21:09 UTC,"Dear Cordeiro,"
1805366,2019-09-27 09:10:00 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1805366,2019-09-15 22:15:46 UTC,"Reviewed:  https://review.opendev.org/680357
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=566f8e734d1b5416305b7ab04c6eda48f40e576b
Submitter: Zuul
Branch:    master"
1805366,2019-09-13 10:19:39 UTC,"Reviewed:  https://review.opendev.org/680341
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f3e6bba5dc5be42582bbf4c913a67ca9c7a7af16
Submitter: Zuul
Branch:    master"
1805366,2019-09-13 10:19:31 UTC,"Reviewed:  https://review.opendev.org/679966
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5cefb91c41c1a3b45977ff6ee06d2541cd0c0aa4
Submitter: Zuul
Branch:    master"
1805366,2019-09-13 10:15:35 UTC,"Reviewed:  https://review.opendev.org/679623
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=cc40014ec89afb55d054480057a323fee764d3b2
Submitter: Zuul
Branch:    master"
1805366,2019-09-13 10:19:22 UTC,"Reviewed:  https://review.opendev.org/679750
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d278ad38adac8020036843706e1472b830d8b1f4
Submitter: Zuul
Branch:    master"
1805366,2019-09-05 08:54:15 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680341"
1805366,2019-09-04 11:13:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/679966"
1805366,2019-09-03 11:04:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/679750"
1805366,2019-09-02 11:17:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/679623"
1805366,2019-07-23 14:31:22 UTC,We talked about this during the keystone virtual midcycle and wanted to note that the domain config API also has an API/policy that allows users to pull password security requirements for a domain.
1805366,2019-09-05 09:41:57 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680357"
1805368,2019-03-26 08:08:38 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647679"
1805368,2019-03-26 08:08:55 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647680"
1805368,2019-03-26 10:38:24 UTC,"Reviewed:  https://review.openstack.org/645889
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d1cfa3ab3f87f15f61c5387670d3b75ee2ba93ba
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 15:12:28 UTC,"Reviewed:  https://review.openstack.org/645890
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ef838a3a3f575562b1fc84623c3a8491d4f2e2f4
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 16:28:26 UTC,"Reviewed:  https://review.openstack.org/647673
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=fd08266abb3a4fb18ac05921ca11c4768daa2f6d
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-03-26 16:28:41 UTC,"Reviewed:  https://review.openstack.org/647674
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0786fde3932e218ef355a6cc958f83c3c7033686
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-03-26 16:28:56 UTC,"Reviewed:  https://review.openstack.org/647675
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ad108dafe2bdd1b6523d6f45315bb136b9b01408
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-03-26 16:29:10 UTC,"Reviewed:  https://review.openstack.org/647676
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4ccb4c258f54642a272e0d865aa1768b7f1ffee5
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-03-26 16:29:25 UTC,"Reviewed:  https://review.openstack.org/647677
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=de083009eb51d1af086387bbac0dca8d3c4474c0
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-03-26 16:30:22 UTC,"Reviewed:  https://review.openstack.org/647680
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=56e48127938be2d67b984d00b155833532233713
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-03-26 08:08:20 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647678"
1805368,2019-03-26 17:00:36 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647814"
1805368,2019-03-26 17:00:54 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647815"
1805368,2019-04-01 17:03:37 UTC,"Reviewed:  https://review.openstack.org/647814
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=db3b293cdea31b5a2b4fab1108d905832ee15550
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-04-02 12:02:30 UTC,"Reviewed:  https://review.openstack.org/647815
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=933b7509a4177680158baeeb582f82470f73ae38
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-06-26 20:58:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/667730"
1805368,2019-09-13 20:43:25 UTC,"Reviewed:  https://review.opendev.org/645968
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f0ef5741c1ffb4173ce5d845a4ec30e075984b3e
Submitter: Zuul
Branch:    master"
1805368,2019-09-13 20:55:03 UTC,"Reviewed:  https://review.opendev.org/667730
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bbd77d0bf9dde57e5ca5d53f7214df85713b9f1e
Submitter: Zuul
Branch:    master"
1805368,2019-09-27 09:10:10 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1805368,2019-03-26 16:30:05 UTC,"Reviewed:  https://review.openstack.org/647679
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=02eebfe5732fb9935331551e223337b22db7aebd
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-03-26 08:08:02 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647677"
1805368,2019-03-26 16:29:38 UTC,"Reviewed:  https://review.openstack.org/647678
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=1d8ac830a1ed6a571db6987d4ef657cf3e04d640
Submitter: Zuul
Branch:    stable/stein"
1805368,2019-03-26 08:07:26 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647675"
1805368,2018-12-04 22:32:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622615"
1805368,2019-03-20 22:00:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645021"
1805368,2019-03-20 22:00:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645022"
1805368,2019-03-20 22:00:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645023"
1805368,2019-03-20 22:01:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645024"
1805368,2019-03-21 19:29:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645309"
1805368,2019-03-21 19:29:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645310"
1805368,2019-03-21 19:30:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645311"
1805368,2019-03-26 08:07:44 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647676"
1805368,2019-03-22 21:27:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645889"
1805368,2019-03-22 04:58:09 UTC,"Reviewed:  https://review.openstack.org/622615
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=465a8bb59be13739253a52d7e457067cf63d3ba8
Submitter: Zuul
Branch:    master"
1805368,2019-03-25 17:53:50 UTC,"Reviewed:  https://review.openstack.org/645021
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bb4192e88d88b781b2a821f3a499b7168b7bbc31
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 01:28:27 UTC,"Reviewed:  https://review.openstack.org/645022
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8f4e179c69eae7ced731776717c09a979bd67cc5
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 01:28:39 UTC,"Reviewed:  https://review.openstack.org/645023
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8450d4a9cc76ce9e476d3cadf863f40f072f4cfe
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 01:28:49 UTC,"Reviewed:  https://review.openstack.org/645024
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=fac844c4ae058c148889b636ab6cbb637df7e554
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 01:31:46 UTC,"Reviewed:  https://review.openstack.org/645309
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=593e67e6ca429c6e6b54c5453a05c40a73abee85
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 01:32:18 UTC,"Reviewed:  https://review.openstack.org/645310
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ba09e89ba1b8a883b09ca81f43bf54bd870411c1
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 01:32:29 UTC,"Reviewed:  https://review.openstack.org/645311
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6e118bad3d49bc1da7137a406fb8cb2e3da931ca
Submitter: Zuul
Branch:    master"
1805368,2019-03-26 08:06:49 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647673"
1805368,2019-03-26 08:07:07 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647674"
1805368,2019-03-22 21:27:23 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645890"
1805371,2019-09-27 09:10:09 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1805371,2019-09-13 15:20:20 UTC,"Reviewed:  https://review.opendev.org/680797
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=afb312529ba1e1eb5acb9598d792f39f5a2500d7
Submitter: Zuul
Branch:    master"
1805371,2019-09-13 04:33:33 UTC,"Reviewed:  https://review.opendev.org/680796
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ee60db6f33554ccf613471d21832113ea9acdde1
Submitter: Zuul
Branch:    master"
1805371,2019-09-11 03:09:14 UTC,"Reviewed:  https://review.opendev.org/680795
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=00c2ecdf333c4026990fd04a44ce3692345ff4cc
Submitter: Zuul
Branch:    master"
1805371,2019-09-07 04:04:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680795"
1805371,2019-09-07 04:04:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680796"
1805371,2019-07-23 23:48:52 UTC,"This is not a correct statement:
""User2 can create a role Dom2R2 implies Dom1R1"""
1805371,2019-07-23 15:09:51 UTC,"Adam,"
1805371,2018-11-27 15:22:02 UTC,"Note that implied roles are used for domain specific roles.  Thus, a domain admin should be able to create an rule where the explicit role is a domain specific role and the implied role is a global role or another domain specific role."
1805371,2019-09-07 04:05:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680797"
1805398,2018-11-29 21:03:41 UTC,The package has been published and the bug is being set to Fix Released
1805400,2019-09-27 09:10:04 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1805400,2019-09-14 08:09:50 UTC,"Reviewed:  https://review.opendev.org/680844
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9b694fcd0846898be843d8779960de399497818d
Submitter: Zuul
Branch:    master"
1805400,2019-09-08 02:28:48 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680844"
1805400,2019-02-27 22:00:41 UTC,https://review.openstack.org/#/c/622526/ and https://review.openstack.org/#/c/622524/ partially fix this.
1805400,2019-02-28 03:30:30 UTC,"Reviewed:  https://review.openstack.org/622527
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=31eecfb2a42e44899ea2f72866be33cc7700db65
Submitter: Zuul
Branch:    master"
1805409,2019-09-27 09:10:13 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1805409,2019-09-11 04:49:39 UTC,"Reviewed:  https://review.opendev.org/678475
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=704cb2590e2f4496a73a79b3eeb22656083b4081
Submitter: Zuul
Branch:    master"
1805409,2019-09-09 22:12:54 UTC,"Reviewed:  https://review.opendev.org/678471
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=296ea0f6d9280798c9dbeabf50641bc413e1a627
Submitter: Zuul
Branch:    master"
1805409,2019-09-09 22:12:46 UTC,"Reviewed:  https://review.opendev.org/678467
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=2af630f06aa8c4636d8d705d88ea17656e5f84a1
Submitter: Zuul
Branch:    master"
1805409,2019-08-30 02:20:07 UTC,"Reviewed:  https://review.opendev.org/677997
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=2d185a5a91e3057be8e38afae1bfbfc02ef2899e
Submitter: Zuul
Branch:    master"
1805409,2019-08-30 02:02:32 UTC,"Reviewed:  https://review.opendev.org/677961
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b831856af3a3cc3c2610e7fd44080c18f4ff77fb
Submitter: Zuul
Branch:    master"
1805409,2019-08-29 07:22:33 UTC,"Reviewed:  https://review.opendev.org/677782
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0e52753898ba307306f8a9b47a217e5950dcde28
Submitter: Zuul
Branch:    master"
1805409,2019-08-27 13:14:08 UTC,"Reviewed:  https://review.opendev.org/676355
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=fd15bcd66f76156d771b3a844c351119c48f8d15
Submitter: Zuul
Branch:    master"
1805409,2019-08-27 13:14:17 UTC,"Reviewed:  https://review.opendev.org/677781
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f45a6f99d11df7b3de6063d108b12bb8fb1d1854
Submitter: Zuul
Branch:    master"
1805409,2019-08-26 06:48:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678471"
1805409,2019-08-26 06:37:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678467"
1805409,2019-08-22 12:23:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677997"
1805409,2019-08-22 10:59:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677961"
1805409,2019-08-21 16:26:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677782"
1805409,2019-08-21 16:16:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677781"
1805409,2019-08-14 06:18:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676355"
1805409,2019-08-13 11:16:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676162"
1805409,2019-07-23 15:52:52 UTC,"This could also include support for only system-scope, since domain or project scoped users shouldn't be accessing this endpoint."
1805409,2019-08-26 19:28:21 UTC,"Reviewed:  https://review.opendev.org/676162
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8f68b72e861a07675e6709307267cb31c7b96d00
Submitter: Zuul
Branch:    master"
1805411,2020-11-27 03:37:32 UTC,The scroll is very impractical.
1805411,2018-11-29 10:46:16 UTC,"what I mean is not dock icons can be scrolled or not, I want the docker icon redesign to be smaller, so we can put more icons in one screen."
1805411,2018-11-28 06:55:16 UTC,"Thank you for your bug report, did you try scrolling with your mouse wheel/touchpad on the launcher?"
1805411,2018-11-28 07:09:46 UTC,"I know scrolling with mouse more app icon will shown,  but it's inconvenient.
If ubuntu dock redesign to contain more app icons, that will be better."
1805411,2018-11-29 10:31:17 UTC,"The ""dock can only"" in the title is confusing then, your report is rather about ""not obvious that the dock icons can be scrolled""?"
1805426,2018-11-30 15:07:56 UTC,"I should note that the page does ""load"", but it takes around 4 to 5 minutes to get anything on the screen. After the wait, when something shows in the screen, I type my username, and proceed to type my password it says that an error has ocurred. On the VM (""disco"" VM) there is no wait time, and everything happens without a hitch. I'll test now with the ""cosmic"" VM."
1805426,2019-01-24 00:15:41 UTC,"Yes, that wouldn't be a problem."
1805426,2018-12-07 16:43:20 UTC,"Thank you for the debugging. I don't think goa requires IPv6, could you give details on how you disabled IPv6? Maybe doing the same steps is enough for others to reproduce the issue.
The issue connecting to ppas when IPv6 is enabling is a bug by itself, either in the software or in your local network configuration"
1805426,2018-11-30 21:55:48 UTC,"Ok, i've found that problem I was having had to do with IPv6 connectivity. Usually I disable the IPv6 connection because there are certain PPAs (archive.ubuntu.com, for example) that for some odd reason, never load, and they timeout on ""sudo apt update"". My network provider has no problem with the IPv6 service, but Ubuntu, usually, cannot load a PPA through IPv6. Because of that, I only allow IPv4 connectivity to be active, and that was the issue. It seems that g-i-s and g-c-c only want to connect via IPv6, even though it was disabled through the g-c-c. I think that both should first check on how the network is setup up and then load the webpages as determined by the settings. That is the issue. I hope it gets fixed."
1805426,2018-11-30 15:02:58 UTC,"So, i changed the language to english on my machine, but the same thing happens, it just won't load the page. And yes, i used the same machine to run the VM. I'm downloading the 18.10 ISO to install in a VM and see if it loads there. But this is a interesting situation, because it loads in a VM (at least in ""disco""), but not the real machine. I'm going to test it on the new 18.10 VM and post any new comments here."
1805426,2018-11-30 14:15:33 UTC,"I`m now running a virtual machine with ""disco"" and i`ve been able to connect all of my accounts without a problem. This bug seems to be affecting mainly ""cosmic"" (I don't know about ""bionic""). So, it seems like the issue has been fixed on ""disco"", or my install of ""cosmic"" has a problem. But it is interesting that this is affecting some colleagues of mine, so it looks like the issue is not on my install of ""cosmic""."
1805426,2018-11-30 00:19:59 UTC,"Ok, so , I've executed both g-i-s and gnome-control-center from the terminal, and all I've got was (on both g-i-s & g-c-c):"
1805426,2018-11-29 15:38:17 UTC,"gnome-control-center having the same issue makes sense (no need to test again g-i-s, but just for the record it's not in the standard directory so the full path needs to be used, '/usr/lib/gnome-initial-setup/gnome-initial-setup')"
1805426,2018-11-29 12:11:01 UTC,"1 - I've added the journalctl log for the first boot of this computer, which is when gnome-initial-setup runs automatically."
1805426,2018-11-29 10:53:41 UTC,"Thank you for your bug report. Do you get any details on the error?
1. could you add your journalctl log after getting the issue?
2. do you get any error printed on the command line if you start gnome-initial-setup from there?
3. does it work to add those from gnome-control-center?"
1805426,2018-11-30 14:22:19 UTC,"Hum, do you use the same locale in the vm? Did you try a cosmic in a VM? Disco didn't have much changes in its desktop stack yet so it would weird to have it fixed there. Could have to do with the translations maybe? Could you try on your machine by switching the language to english?"
1805433,2018-11-28 16:25:33 UTC,apport information
1805433,2018-12-16 14:10:30 UTC,Ok i have the new kernel loaded now. The new dmesg output still has 9 call traces in it.
1805433,2018-12-16 06:30:46 UTC,"$ yes '' | make localmodconfig
$ make -j`nproc` deb-pkg"
1805433,2018-12-13 15:13:26 UTC,Well i was able to get the patches with
1805433,2018-12-13 13:24:00 UTC,I can try to build a kernel. How can i download all the patches and apply them at the same time?
1805433,2018-12-13 08:42:41 UTC,"If you know how to build a kernel, please try this branch out:
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next"
1805433,2018-12-10 18:00:37 UTC,"The dmesg on 4.20 rc6 still contains a lot of call traces. I don't know if they are the same ones or of the same origin though. When comparing files i initially thought the 4.20rc6 has less call traces, but actually at the end of the diff there are more. So i would say both 4.18 and 4.20rc6 roughly have the same amount of call traces."
1805433,2018-12-10 17:58:18 UTC,Hi jsalisbury i can not tell you about the situation before because it was the first time i checked dmesg. I did a dist upgrade from 18.04 to 18.10 though. But like i said i don't know if this was already happening in 18.04
1805433,2018-12-10 15:49:12 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1805433,2018-11-28 16:25:36 UTC,apport information
1805433,2018-11-28 16:25:32 UTC,apport information
1805433,2018-11-28 16:25:31 UTC,apport information
1805433,2018-11-28 16:25:28 UTC,apport information
1805433,2018-11-28 16:25:27 UTC,apport information
1805433,2018-11-28 16:25:25 UTC,apport information
1805433,2018-11-28 16:25:24 UTC,apport information
1805433,2018-11-28 16:25:23 UTC,apport information
1805433,2018-11-28 16:25:22 UTC,apport information
1805433,2018-11-28 16:25:20 UTC,apport information
1805433,2018-11-28 16:25:19 UTC,apport information
1805433,2018-11-28 16:25:18 UTC,apport information
1805433,2018-11-28 16:25:16 UTC,apport information
1805433,2018-11-28 16:25:14 UTC,apport information
1805433,2018-11-28 13:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805438,2018-11-30 15:45:27 UTC,Thanks for your followup.
1805438,2018-12-10 03:35:34 UTC,"So, the error ""client-error-not-authorized"" is from CUPS. Can someone shed light on that error?"
1805438,2018-11-30 16:34:02 UTC,Yes.
1805438,2018-11-30 16:06:26 UTC,Is your user account in the lpadmin group in /etc/group (this is default for the first user created during installation)?
1805438,2018-11-30 14:48:34 UTC,"For cups-pk-helper problems we need appropriate log files, as Sebastien already asked for."
1805438,2018-11-29 10:49:00 UTC,"Thank you for your bug report, could you add your journalctl log/command line output after trying to add the printer and getting the error dialog?"
1805438,2018-11-29 21:12:35 UTC,"groups:
casey adm cdrom sudo dip plugdev lpadmin sambashare lxd"
1805438,2018-11-29 20:48:18 UTC,"what's the output of ""groups"" for your user?"
1805438,2018-11-29 20:07:05 UTC,apt policy cups-pk-helper reveals
1805438,2018-11-29 17:35:08 UTC,"That's useful, what version of cups-pk-helper is installed (dpkg -l | grep cups-pk-helper)? It would be interesting to know if you have the fix from https://launchpad.net/ubuntu/+source/cups-pk-helper/0.2.6-1ubuntu1.2"
1805438,2018-11-29 15:49:09 UTC,Sure.
1805438,2018-11-30 14:29:50 UTC,"Thanks, that looks normal. I'm Ccing Till who looks after printing in Ubuntu, maybe he has an idea what could be wrong/why cups-pk-helper errors out. You didn't attach your journalctl log around the time of the error, could you do that, it could include clues"
1805448,2018-11-27 14:37:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620333"
1805448,2018-11-27 14:37:19 UTC,Fix: https://review.openstack.org/620333
1805455,2018-11-30 14:13:46 UTC,I corrected the original horrendous title I had made for this bug. Apparently it just used my search terms when I was looking for related bugs.
1805455,2018-12-11 12:23:29 UTC,I can confirm that for two consecutive calendar days marked as closed when an item falls due on the first date the due date is set to the second closed date without checking for other closed date entries.
1805455,2018-12-11 12:23:59 UTC,"It doesn't just seem to affect partial days.  If you enter full closed dates as separate entries (NYE and then New Year's Day since they're in different years, for example), the second date is ignored."
1805468,2019-10-13 09:15:31 UTC,"For the clutter in 'mount', you could add '-t nosquashfs' to the options, either directly or via an alias. While you're at it maybe include nocgroup, and possibly notmpfs in there. Having"
1805468,2019-10-12 18:00:36 UTC,We have a long term plan of actually mounting the apps that you run and not those that are merely installed. This won’t happen overnight and is not a high priority item but it will eventually happen.
1805468,2019-12-13 04:17:17 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1805468,2019-10-10 12:40:12 UTC,"Have you _measured_ a performance impact due to just having things mounted? Beyond a delay at boot (which is something worth fixing, but doesn't seem to be your main issue), we have not been able to measure a difference. We did find bugs in the kernel and have fixed them though."
1805468,2019-10-12 13:29:33 UTC,"The issue so far is that the output of ""mount"" is cluttered by an annoying amount of entries not of any use to my daily routines with ""mount""."
1805468,2018-11-27 16:22:52 UTC,Actually I was surprised by seeing gnome-calculator coming at at `mount`s output. This is nothing anyone would ever expect.
1805473,2019-02-01 20:05:26 UTC,The behavior will be fixed in snapd 2.38.
1805473,2019-01-07 10:48:16 UTC,A discussion of this with a solution is now here:
1805473,2019-02-01 10:40:24 UTC,PR: https://github.com/snapcore/snapd/pull/6415
1805477,2018-11-27 18:00:04 UTC,"+1, this is problematic for knowing what traffic needs to be authorized between network zones/firewalls etc. The information is needed to form a complete view security wise."
1805477,2019-09-19 12:07:04 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1805477,2019-09-19 13:03:50 UTC,Adding note that gateway and dns setup is not documented enough.
1805477,2019-09-19 14:35:05 UTC,"in this bug report it was explained how setting of dns servers influences resulting proxy url
thus direct or via proxy communication:"
1805477,2020-08-26 14:20:12 UTC,"Yeah, I agree this needs fixing.  We have been a little hand-wavy about DNS and DHCP in a lot of places, at least by my standards.  It should be crystal clear, down to the protocol diagrams if necessary.  Assigning this to me."
1805489,2018-11-27 21:49:30 UTC,"Yeah this is just for us to remember that we have a strong reason to upgrade.
I would say this is High importance since the settings are useless, and while the workaround is disable dark mode, not all users might realize this."
1805489,2019-06-02 09:41:45 UTC,Can no longer reproduce in master builds. Those have moved to Qt 5.12 a while ago.
1805489,2018-11-27 21:30:31 UTC,"Haha, ""Another year, another version of macOS is out breaking our Qt."""
1805490,2019-04-17 22:14:49 UTC,See attached file with output from both commands.
1805490,2020-07-02 19:28:04 UTC,"Ubuntu 19.04 reached end of life on January 23, 2020.  I am therefore marking this bug 'wontfix' for that release."
1805490,2019-04-19 15:03:23 UTC,"Thanks, I think we have all the information we need right now; this needs further investigation by a developer."
1805490,2019-04-19 05:15:32 UTC,"root@laptop:/sys/firmware/efi/efivars# strace -ff efibootmgr -b 0000 -B
execve(""/bin/efibootmgr"", [""efibootmgr"", ""-b"", ""0000"", ""-B""], 0x7fff3ef3c210 /* 25 vars */) = 0
brk(NULL)                               = 0x55e921747000
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
access(""/etc/ld.so.preload"", R_OK)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, ""/etc/ld.so.cache"", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=99288, ...}) = 0
mmap(NULL, 99288, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f1d82acc000
close(3)                                = 0
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, ""/usr/lib/x86_64-linux-gnu/libefivar.so.1"", O_RDONLY|O_CLOEXEC) = 3
read(3, ""\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0203\0\0\0\0\0\0""..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=138312, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f1d82aca000
mmap(NULL, 141136, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f1d82aa7000
mmap(0x7f1d82aaa000, 69632, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f1d82aaa000
mmap(0x7f1d82abb000, 16384, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x14000) = 0x7f1d82abb000
mmap(0x7f1d82abf000, 45056, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0x7f1d82abf000
close(3)                                = 0
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, ""/usr/lib/x86_64-linux-gnu/libefiboot.so.1"", O_RDONLY|O_CLOEXEC) = 3
read(3, ""\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P$\0\0\0\0\0\0""..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=55216, ...}) = 0
mmap(NULL, 57376, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f1d82a98000
mmap(0x7f1d82a9a000, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f1d82a9a000
mmap(0x7f1d82aa2000, 12288, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xa000) = 0x7f1d82aa2000
mmap(0x7f1d82aa5000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc000) = 0x7f1d82aa5000
close(3)                                = 0
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, ""/lib/x86_64-linux-gnu/libc.so.6"", O_RDONLY|O_CLOEXEC) = 3
read(3, ""\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260A\2\0\0\0\0\0""..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1996592, ...}) = 0
mmap(NULL, 2004992, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f1d828ae000
mprotect(0x7f1d828d0000, 1826816, PROT_NONE) = 0
mmap(0x7f1d828d0000, 1511424, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x22000) = 0x7f1d828d0000
mmap(0x7f1d82a41000, 311296, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x193000) = 0x7f1d82a41000
mmap(0x7f1d82a8e000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1df000) = 0x7f1d82a8e000
mmap(0x7f1d82a94000, 14336, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f1d82a94000
close(3)                                = 0
access(""/etc/ld.so.nohwcap"", F_OK..."
1805490,2019-04-17 22:19:35 UTC,Ugh. Looks like the email attachment didn't survive the trip...
1805490,2019-04-17 22:18:30 UTC,"I looked at 1734147 but it didn't seem familiar. (That's not saying much though, as I've not really paid close attention other than to note that I'm affected by the grub issues.)"
1805490,2019-04-17 20:44:43 UTC,"In addition to the above; if anyone has previously had Ubuntu 17.10 installed on the affected system, it is possible this is due to bug 1734147. Please see if the bug's description matched with what you are seeing. If you're unsure, ask here for help."
1805490,2019-02-13 21:43:53 UTC,The output is attached.
1805490,2018-11-29 10:37:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805490,2018-11-29 10:38:43 UTC,Bug #1800363 for example claims it happened during a bionic to cosmic upgrade
1805490,2019-04-17 20:38:19 UTC,Alright; I think I've finally made some progress on this.
1805490,2019-02-13 03:14:26 UTC,Some more questions:
1805490,2019-02-13 21:40:07 UTC,"I have been using a workaround submitted by Ronan Mooney, listed as #11
on https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518"
1805490,2019-02-13 03:09:58 UTC,"I'm unable to reproduce this. I've tried upgrading from bionic to cosmic, or various partitioning set ups. Clearly there is something special about some set up that can cause this kind of issue, but I'm unsure what it could be."
1805493,2018-11-27 21:25:20 UTC,There's no remove command at the moment.
1805493,2018-12-04 16:50:28 UTC,This would mostly affect Kubernetes stuff where you *always* need to create storage pools.
1805493,2019-02-19 03:34:07 UTC,Fixed in 2.5.1
1805493,2019-03-08 22:39:58 UTC,It's not enough just to install the 2.5.1 snap - you need to upgrade your running controller to 2.5.1. That error you are getting says that the Juju CLI wants to remove a storage pool but cannot because the version of the controller is not recent enough.
1805493,2019-03-08 22:57:04 UTC,"Thanks to your input, I upgraded my controller as per documentation. However, the error message is not very descriptive. Should we open a bug on this?"
1805493,2019-03-10 21:37:12 UTC,Glad it worked for you. There's probably a dozen other similar version checks in the Juju CLI which use the same error message. It's the controller which implements the functionality so that's what needs to be up to date. A bug to make the error message more explicit wouldn't be out of place.
1805493,2019-03-08 21:23:39 UTC,It does not seem to work yet. I have the juju charm revision 6629 which contains juju version 2.5.1-bionic-amd64 installed and I get the error: ERROR removing storage pools is not supported by this version of Juju
1805497,2019-01-15 09:18:02 UTC,"Cody, could you please verify if this works for cloud images now? If yes, could you please set the tags to verification-done-bionic?"
1805497,2019-01-17 13:01:29 UTC,This bug was fixed in the package livecd-rootfs - 2.408.42
1805497,2019-01-16 19:40:11 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1805497,2019-01-16 19:39:59 UTC,This bug was fixed in the package livecd-rootfs - 2.525.12
1805497,2019-01-15 22:38:26 UTC,Verification done for Bionic and Xenial.
1805497,2019-01-14 15:11:07 UTC,Please note that for now this bug only applies to cloud images.
1805497,2018-12-12 00:03:16 UTC,"Hello Cody, or anyone else affected,"
1805497,2018-11-29 17:53:26 UTC,Is this change expected to appear in Stable Releases?  Does it conform to Stable Release Updates policy?
1805497,2019-01-11 01:03:09 UTC,"We aren't building daily xenial ISOs currently (since we're past the last point release), but I checked the log for the latest bionic daily:"
1805497,2018-12-12 00:00:18 UTC,"Hello Cody, or anyone else affected,"
1805497,2018-11-29 19:42:49 UTC,"On Thu, Nov 29, 2018 at 05:53:26PM -0000, Scott Moser wrote:

> Is this change expected to appear in Stable Releases?
"
1805499,2018-11-27 20:57:25 UTC,Can you evaluate the effort and record progress on this bug.
1805501,2018-11-30 21:20:22 UTC,Fix committed in x.4318.
1805501,2019-01-10 17:31:36 UTC,"I wonder if my problem is the same, when i enter the game i hear sound but the sound is frozen or completely muted. I would say by at least 2 minutes my game crashes and brings me to the menu."
1805501,2019-01-11 09:01:15 UTC,"Hi James,
you should attach file OpenRailsLog.txt that you get on the desktop after the crash, to let us understand what the problem is."
1805501,2019-01-12 15:08:35 UTC,"Carlo Santucci (carlosanit1), What do you mean by attaching the openrailslog.txt"
1805506,2018-11-29 07:32:55 UTC,"In summary, backup creation/restore took too much time and lead timeout. Currently, volume size is 1G, this is supported minimum capacity. So may we can update the timeout for backup creation/restore."
1805506,2018-11-29 07:31:01 UTC,"From http://logs.openstack.org/87/609587/11/check/tempest-multinode-full/d4ec462/testr_results.html.gz
It calls restore_volume, and checks status of backup to finish in 196s."
1805506,2018-11-28 15:04:02 UTC,Another examples of issues with Cinder backup:
1805509,2018-11-27 21:42:21 UTC,I should add that I have increased my panel size and that's probably the cause. I'm guessing the applet needs to provide either different sized icons or some sort of scalable icon.
1805515,2018-11-28 23:16:45 UTC,I can confirm this on Windows 10
1805515,2018-12-04 20:15:21 UTC,"Strange its work for my win7 x86 ultimate english & mixx 2.1.4
Only when its not work is related other problem when mixxx wont load tracks to decks and give error messages after couple hours playing. cant remember now the bug number."
1805515,2018-12-04 22:05:04 UTC,"We have added the feature in 2.2 to also select the file in windows explorer.
This breaks the whole feature in the upcoming Mixxx version."
1805515,2018-12-04 22:13:42 UTC,I mean 2.3 ..
1805515,2018-12-04 22:15:41 UTC,https://github.com/mixxxdj/mixxx/pull/1931
1805518,2019-10-12 15:58:31 UTC,This has been fixed with newer openstackdocstheme
1805520,2018-11-28 01:21:14 UTC,I didn't check when using `--constraints` during bootstrap.
1805520,2019-10-31 03:40:31 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1805523,2018-11-28 06:58:42 UTC,"Thank you for your bug report. Could you open the settings->sounds screen, select the applications tab and see if there is anything displayed when you tricker a such event? Maybe the volume for those events is set to 0?"
1805523,2018-11-29 02:20:24 UTC,"Thank you, I just tried that but nothing ever displays in settings when I trigger the event."
1805523,2019-01-07 02:05:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805523,2019-02-16 01:04:33 UTC,"It seems like only some of the sounds are triggered.
Like if I add the 'empty-trash' or 'item-delete' file from the freedesktop name spec (http://0pointer.de/public/sound-naming-spec.html), non of them are played."
1805539,2019-10-05 04:04:38 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/686864"
1805539,2019-10-05 05:38:48 UTC,"Reviewed:  https://review.opendev.org/686864
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=bfa8e9feb51f2b10adfec3a741661a76fcf73216
Submitter: Zuul
Branch:    feature/losf"
1805539,2019-09-05 05:42:36 UTC,"Reviewed:  https://review.opendev.org/620440
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=eed76d8bed446518bff2ca4af18259f7637c430e
Submitter: Zuul
Branch:    master"
1805539,2018-11-28 03:00:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620440"
1805539,2019-10-03 16:35:05 UTC,This issue was fixed in the openstack/swift 2.23.0 release.
1805543,2018-11-28 03:29:32 UTC,"On Wed, Nov 28, 2018 at 02:47:10AM -0000, Paul D wrote:

> feature yet.  Specifically, it's introduced in this commit on the
> iptables codebase:
> https://git.netfilter.org/iptables/commit/?id=8b0da2130b8af3890ef20afb2305f11224bb39ec.
"
1805543,2018-11-28 03:52:41 UTC,"First off, wow, thank you for the speedy response!  I am pretty confident that the kernel we're running supports this feature.  Here's why:"
1805543,2019-06-03 09:26:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805543,2019-06-03 13:48:55 UTC,For doing an SRU the bug would need a description of the impact and a test case / description of the regression potential (see https://wiki.ubuntu.com/StableReleaseUpdates). Could someone provide those informations (and ideally a debdiff for the update)
1805543,2019-07-04 09:37:50 UTC,"I found this thread because I ran into a problem with a brand-new installation of Kubernetes (K8s) running in AWS that was failing a large number of browser requests being serviced by the K8s cluster. There is a ton of detail about this problem at https://tech.xing.com/a-reason-for-unexplained-connection-timeouts-on-kubernetes-docker-abd041cf7e02. To make a very long story short, we need the 1.6.2+ version of iptables on Ubuntu because it supports the --random-fully flag. Without this, any K8s cluster created on Ubuntu is pretty useless if you use local DNS to resolve cluster services by name (e.g. http://my-backend-microservice), which is what we do to support namespaces for reverse proxies (nginx)."
1805543,2020-02-14 04:57:41 UTC,"Hi all,
I manually built iptables 1.6.2 using the instructions at http://www.linuxfromscratch.org/blfs/view/8.2/postlfs/iptables.html and my problem is if I use
#iptables -V
output is 1.6.2
and if I use
#apt-cache policy iptables
it is showing 1.6.0 only. i went through following process. can anybody suggest/correct me wr is the mistake."
1805545,2018-11-28 06:56:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1805552,2019-05-21 11:07:50 UTC,"Hi, probably a better fix is to ensure that data loss does not occur during save. As a result, please refer to our new bug tracker for further updates on this issue. Thank you!"
1805552,2019-03-11 09:49:54 UTC,Related: bug #1174079 (Crash during save causes data loss)
1805552,2018-12-12 19:36:06 UTC,"Would it be okay to rename the bug to ""Autosave does not help for crash on save""?"
1805552,2018-12-10 18:04:10 UTC,"Sorry, misunderstood completely. Deleted my previous comment."
1805552,2018-11-28 20:15:59 UTC,"Let me try to simplify the problem:
1. Open file
[optional: 2. wait x minutes]
3. Make some tiny change
4. Save (within < 10 minutes)
5. Assume that inkscape crashes in the middle of saving the file."
1805555,2018-11-28 03:56:51 UTC,"hello, world!"
1805556,2018-12-12 17:55:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805557,2018-11-28 15:57:36 UTC,"Thank you for reporting, I'll try to reproduce today."
1805561,2019-06-02 04:17:21 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1805561,2019-06-02 04:17:17 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1805561,2019-04-02 04:55:59 UTC,The only possible cause of this I can think of has now been fixed by the introduction of:
1805561,2018-11-28 16:53:24 UTC,"Hello Daniel,
Yes always test new Ubuntu and in 18.04 and 18.10 we had Wayland show on the login screen, in 19.04 the login is missing."
1805561,2018-11-28 04:59:33 UTC,"Technically Wayland was never working with the Nvidia driver. Even if you do remember to use nvidia-drm.modeset=1, the problem remains that Ubuntu's mutter builds are missing EGLStreams support. So when the ""Ubuntu on Wayland"" option was given in 18.04/18.10 it would still only provide software rendering..."
1805561,2018-12-11 02:35:19 UTC,"I've been testing nvidia-410 in Ubuntu 19.04 recently and can't reproduce this bug. I get the ""Ubuntu on Wayland"" login option on my machine. So I can't confirm this bug myself."
1805569,2018-11-28 06:45:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620473"
1805569,2019-06-27 14:53:49 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/620473
Reason: It's not clear to me what this is trying to fix (the commit message is not clear about what the issue is and how this fixes it). The tests are failing and this hasn't been updated since a -1 was posted last year, so I'm going to abandon."
1805569,2019-06-27 14:54:15 UTC,"It's not clear to me what the bug is here, please provide more details on how to recreate. Marking incomplete."
1805569,2019-08-27 04:17:28 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1805583,2019-02-19 13:17:51 UTC,Is this still an issue?
1805583,2019-03-14 10:38:02 UTC,This issue was fixed in the openstack/instack-undercloud 9.5.0 release.
1805583,2018-12-04 12:20:56 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/622282"
1805583,2018-12-04 08:56:12 UTC,"Reviewed:  https://review.openstack.org/619467
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=0b9002106a5e56da09d5212926913062e1abb13c
Submitter: Zuul
Branch:    stable/rocky"
1805583,2018-12-04 12:23:26 UTC,"Change abandoned by Carlos Camacho (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/622282"
1805585,2020-03-12 05:17:09 UTC,"My car windshield has a big crack, need an immediate replacement. will be away between 3pm-5pm"
1805585,2020-03-12 05:16:55 UTC,"My car windshield has a big crack, need an immediate replacement. will be away between 3pm-5pm"
1805585,2019-06-21 16:34:57 UTC,- Kuljinder
1805585,2019-06-20 23:00:18 UTC,I just started another reimage. Will let you know if that resolves. Thx!
1805585,2019-06-20 22:59:22 UTC,"Kuljinder,
After I reimage, I see disk error in b1s7-node2. Please see if anything wrong with the disk."
1805585,2019-06-21 00:59:38 UTC,"Kuljinder, second reimage fixed the issue."
1805585,2018-12-11 20:12:41 UTC,+config team
1805585,2018-12-10 19:59:16 UTC,FYI
1805585,2018-12-03 19:47:03 UTC,I am able to reproduce this issue on my local setup with 414 build.
1805585,2018-12-03 19:46:27 UTC,Related to 1794210 commit . Can you please take care of it ?
1805585,2018-11-29 17:26:12 UTC,"sajeesh, can you take a look."
1805585,2018-12-11 20:39:44 UTC,"Ok.
FYI, the cluster deployment and tempest run takes approximate 6 hrs. If the new trigger happening early morning for example at 6 am, cluster might be available after 12 noon."
1805594,2018-11-28 09:39:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/620544"
1805594,2018-11-28 09:54:38 UTC,This is a nuance of how we manage things in ubuntu; the default mysql driver in ubuntu is pymysql  (we patch to switch the default) so we should probably drop the WARNING message as well.
1805594,2019-02-13 14:37:26 UTC,"Change abandoned by sahid (<email address hidden>) on branch: master
Review: https://review.openstack.org/620544"
1805596,2018-12-04 02:32:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/621851"
1805615,2020-07-28 19:44:26 UTC,Behavior was resolved with https://bugs.launchpad.net/evergreen/+bug/1787479
1805615,2019-02-21 14:49:31 UTC,This appears to be resolved with the new work in:
1805615,2018-12-06 07:36:40 UTC,"Following on, there's more that needs to be changed on this. It's affecting the font settings preview, etc. I'm working on it now."
1805615,2018-12-06 06:02:17 UTC,"After quite a bit of troubleshooting, the best I can tell is this is a byproduct of saving to local DB storage and the templates maintaining the $scope.preview_scope values after saving. (I don't know if it affects other template storages outside of spine labels, but I can imagine it might.) e.g. template-example-1 gets saved with ""Arial, sans-serif"" and ""16px"" as its font family and font size settings, respectively. Then those get updated as ""Times, serif"" and ""12px"" and saved to template-example-2. Because $scope.templates is storing those values as references to $scope.preview_scope, template-example-1 gets saved with the new values, even when it's not intended."
1805630,2021-02-04 17:45:21 UTC,I wake up this ticket because I experienced exactly the same today.
1805630,2018-11-28 13:49:59 UTC,keystone playbook put nodes in maintenance (pre task) run keystone role then put them back in active (post task)
1805630,2021-02-15 10:14:14 UTC,Hi Dmitriy. Do you need further information ?
1805630,2021-02-08 14:51:50 UTC,# /openstack/venvs/keystone-21.2.2/bin/keystone-manage credential_migrate --keystone-user keystone --keystone-group keystone
1805630,2021-02-08 14:19:30 UTC,Can you try running this command manually and check exit code? Is there smth in keystone log when it fails?
1805630,2021-02-15 16:34:46 UTC,"Hi. At the moment I' not sure what causes the issue. It might be related to keystone itself. Didn't have time to dig into this yet, sorry."
1805630,2021-02-05 11:06:19 UTC,"I think specificly cherry-picking these commits should work though. But checkout or pull will fail, yes."
1805630,2021-02-05 09:27:55 UTC,"Thanks for helping Dmitriy, but this ansible code cannot work on my Ussuri deployment."
1805630,2021-02-04 18:06:02 UTC,"Oh, and it ofc needs https://review.opendev.org/c/openstack/openstack-ansible-os_keystone/+/760429 as well"
1805630,2021-02-04 18:03:48 UTC,Can you kindly check if cherry-picking https://review.opendev.org/c/openstack/openstack-ansible/+/769181 solves your issue?
1805630,2021-02-08 13:27:26 UTC,"You're right, Dmitriy. I did the test again from the start (containers destroy->containers create->os-keystone-install), with cherry-pick method, and it worked on the first run. But a second run of os-keystone-install, with the same user_variables.yml, fails here:"
1805631,2018-12-14 00:07:17 UTC,apport information
1805631,2019-08-07 19:18:45 UTC,"I'm currently not running that computer, since it became unbearable. During the weekend I will start testing it again."
1805631,2019-07-29 16:15:32 UTC,Does the issue still happen? Please attach `journalctl -b -1` after the issue happened and the system rebooted.
1805631,2019-01-16 11:08:15 UTC,"The 5.0rc1 is now installed, but the kernel doesn't appear in the grub list, also after grub-update. dpkg reports it as installed."
1805631,2019-01-16 10:43:52 UTC,"When checking the Kernel page again, the v5.0-rc1 is also successfully built. I'll test it."
1805631,2019-01-16 10:35:21 UTC,I tested the last kernel *successfully* built for AMD64. The bug is still there.
1805631,2019-01-14 04:24:41 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.20-rc2 kernel[0]."
1805631,2018-12-14 00:07:20 UTC,apport information
1805631,2018-12-14 00:07:19 UTC,apport information
1805631,2019-08-28 14:54:13 UTC,I haven't had a single crash with the v5.0 kernel although I really tried. I mark this bug as invalid.
1805631,2018-12-14 00:07:14 UTC,apport information
1805631,2018-11-28 16:22:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1805631,2018-12-14 00:07:15 UTC,apport information
1805631,2018-12-12 09:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805631,2018-12-14 00:07:08 UTC,apport information
1805631,2018-12-14 00:07:09 UTC,apport information
1805631,2018-12-14 00:07:16 UTC,apport information
1805631,2018-12-14 00:07:11 UTC,apport information
1805631,2018-12-14 00:07:12 UTC,apport information
1805631,2018-12-14 00:07:13 UTC,apport information
1805631,2018-12-14 00:07:10 UTC,apport information
1805636,2018-12-10 18:02:44 UTC,"There is a patch on debian's bugtracker, but it seems that they haven't implemented it yet.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611250#39 would be could if you would."
1805637,2018-11-28 14:05:31 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/620607"
1805637,2018-11-29 12:49:36 UTC,"Reviewed:  https://review.openstack.org/620607
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=d43ee8690221167ad69db74f65715229abb842ca
Submitter: Zuul
Branch:    stable/rocky"
1805640,2018-11-28 20:06:48 UTC,"Thanks for reporting this. Do you mind if I make it public so we can get some more eyes on it? I don't know that lcab is still actively maintained, so I'd like to get some more input from the community."
1805640,2018-11-29 07:47:10 UTC,"No problem, please do."
1805640,2019-09-17 09:17:33 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1805640,2019-11-17 04:17:32 UTC,[Expired for lcab (Ubuntu) because there has been no activity for 60 days.]
1805642,2019-05-17 06:29:04 UTC,This version is in eoan and the bionic/cosmic/disco backports.
1805642,2018-11-28 14:16:36 UTC,I would like to volunteer to fix this myself.
1805642,2019-03-14 07:23:05 UTC,"Fixed upstream in https://github.com/cockpit-project/cockpit/pull/11357 , will be in release 190. Thanks!"
1805644,2018-11-28 15:16:00 UTC,Possibly related to:
1805644,2019-07-18 22:14:29 UTC,Thanks for filing the issue.  the sysconfig renderer does need some updates for opensuse specifically around routes files.
1805650,2018-11-28 15:38:40 UTC,"https://bugs.launchpad.net/launchpad/+bug/60601 is relevant but not exactly a dupe; I'd be happy to just get a relevant error but still making the comment mandatory, while that one wants allowing comment-less keys."
1805653,2019-03-22 20:27:41 UTC,For some unknown reason I'm no longer getting this error in Ubuntu 19.04.
1805653,2019-09-06 20:46:16 UTC,This was fixed via ubuntu-mate-artwork 19.04.0
1805654,2018-11-28 16:13:57 UTC,How can this cause problems? Wouldn't some process (e.g. NM) need to bring the interface up without resetting the IP address for this to be still be meaningful?
1805659,2018-11-28 16:24:27 UTC,Setting the configuration to 'unversioned' can be used as a workaround.
1805659,2018-11-28 16:24:45 UTC,Can probably be changed once this bug is resolved https://bugs.launchpad.net/ceilometer/+bug/1665449
1805659,2019-06-05 13:10:14 UTC,"Reviewed:  https://review.opendev.org/603079
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ed613aa66fe37737ab97ce7e483949d931a0c3a5
Submitter: Zuul
Branch:    master"
1805659,2019-09-27 09:03:12 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1805661,2020-03-07 11:08:12 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1805663,2019-03-01 21:05:59 UTC,It's possible to add copies to bibs on sources with the can_have_copies flag set to false in the following ways:
1805663,2018-11-29 20:11:47 UTC,Confirming this is also an issue in 3.2.1
1805663,2018-11-28 21:34:46 UTC,I just verified that volumes/copies can be added to our digital subscription records whose source is set with can_have_copies field set to false. Web client version 3.1.8.
1805665,2020-02-24 07:02:38 UTC,"First step for fixing this is to evaluate if this check should actually be in the nova-cloud-controller charm or in openstack-service-checks, and if it's still relevant for the newest versions."
1805668,2019-01-15 16:52:41 UTC,"Hello Łukasz, or anyone else affected,"
1805668,2019-01-15 23:27:53 UTC,Bug 1811216 should be part of this bug.
1805668,2019-01-16 17:27:00 UTC,I don't see the need for separate images for the Pi 2 and 3. I think that there should only be one image that should work on both the Pi 2 and 3. u-boot works on the Pi 3 if setup with rpi_3_defconfig (for 64-bit) or rpi_3_32b_config (for 32-bit). You can enable BCM2836 support (if setup with rpi_3_32b_config) and then compile. This results in one u-boot binary that works on both the Pi 2 and 3).
1805668,2019-01-16 19:39:59 UTC,This bug was fixed in the package livecd-rootfs - 2.525.12
1805668,2019-01-21 18:58:44 UTC,"Hello Łukasz, or anyone else affected,"
1805668,2019-01-21 19:13:49 UTC,"Hello Łukasz, or anyone else affected,"
1805668,2019-01-22 23:34:31 UTC,"Lukasz, any plans to make Bluetooth work out of the box on the pi 3B/B+?  https://wiki.gentoo.org/wiki/Raspberry_Pi#Bluetooth"
1805668,2019-01-23 09:26:08 UTC,"Adam, that's certainly something worth considering - not sure if we'll make it for the bionic .2 point-release though. The problem is that basically linux-firmware-raspi2 is constructed from stripped raspberrypi/firmware tarballs, so including additional binary files from a different project (RPi-Distro/bluez-firmware) might not be well-received - especially for precompiled binaries. We'd probably have to create a separate source package for this and get it into multiverse/restricted. I'll discuss it with more experienced archive admins and check what is the best way forward. We'll want to have this ASAP for sure."
1805668,2019-01-23 09:29:25 UTC,"In the meantime: with bionic daily raspi3 images enabled (which are by default ran with PROPOSED=1, so including all the required packages), we can see that the raspi3 rootfs builds are succeeding for both arm64 and armhf. All other daily builds seem to be working correctly as well. Additionally to that, I have confirmed through the manifests that raspi3-firmware is no longer used."
1805668,2019-01-23 17:25:22 UTC,"I also did a quick sanity-test of the u-boot for the raspi3 on cosmic. I fetched my old pre-alpha cosmic-based arm64 image, mounted its boot partition, updated kernel8.img with the one provided in u-boot-rpi 2018.07~rc3+dfsg1-0ubuntu1~18.10.1 (u-boot.bin), flashed the SD card and powered on the device. The image was still booting successfully. Since we will not use cosmic for pi3 images, I consider this as verification-done."
1805668,2019-01-26 19:33:58 UTC,Why are the raspi3 images 120MB bigger than the raspi2 images?
1805668,2019-01-27 20:54:25 UTC,The new Linux-firmware-raspi2 package contains kernel.img and kernel7.img.  These definitely shouldn't be included in the package.
1805668,2019-01-29 17:44:09 UTC,This bug was fixed in the package u-boot - 2018.07~rc3+dfsg1-0ubuntu1~18.10.1
1805668,2019-01-27 21:01:34 UTC,Inspecting the raspi3 images on another computer /boot/firmware is populated with files.  These do not match the files on the system-boot partition.  /boot/firmware should be empty until mounted as system-boot.
1805668,2019-01-28 18:12:46 UTC,"Hello Łukasz, or anyone else affected,"
1805668,2019-01-28 19:03:19 UTC,New compute module released today.  Flash-kernel/linux-firmware-raspi2/linux-raspi2 will all need updating....
1805668,2019-01-29 15:00:36 UTC,"@Adam Thanks for pointing out the kernel*.img files in the firmware package! Fixed that and got the SRU into bionic. As for the new CM, not sure if we'll make it in time for the .2 point release with that one, it's already too close and the kernel cycle always takes a while. As for the config.txt, currently this comes from the pi3-gadget classic branch. In the nearest time both the core18 and classic gadgets will all be integrated into one repository."
1805668,2019-01-29 15:01:42 UTC,"As for the new linux-firmware-raspi2 - it was just a cleanup re-release, so I only performed a sanity run of the latest daily image (boot-test, all went fine). I have confirmed it has been built with the latest 1.20180919-0ubuntu0.18.04.2 version."
1805668,2019-01-29 17:40:55 UTC,This bug was fixed in the package livecd-rootfs - 2.525.14
1805668,2019-01-29 17:41:01 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1805668,2019-01-29 17:44:50 UTC,This bug was fixed in the package u-boot - 2018.07~rc3+dfsg1-0ubuntu1~18.04.1
1805668,2019-01-29 17:52:44 UTC,This bug was fixed in the package linux-firmware-raspi2 - 1.20180919-0ubuntu0.18.04.2
1805668,2019-01-15 16:39:03 UTC,"Hello Łukasz, or anyone else affected,"
1805668,2019-10-08 15:55:37 UTC,"> mkknlimg should be used consistently across the packages/snaps.
"
1805668,2019-01-27 20:56:45 UTC,Where does the config.txt on the raspi3 images come from?  It is not livecd-rootfs.
1805668,2019-01-15 14:31:37 UTC,"To use arm64 the config.txt should contain arm_64bit=1.  You've got kernel=uboot.bin, but there is no uboot.bin on arm64.  So what is happening is the pi is falling back to searching for kernel8.img which puts it automatically in arm64 mode.  Yes it works, but only because the config.txt contains an error (kernel=uboot.bin)."
1805668,2019-01-31 09:37:31 UTC,Expanding comment #46 above...
1805668,2019-01-14 21:24:10 UTC,"Hello Łukasz, or anyone else affected,"
1805668,2018-11-30 14:08:57 UTC,I have skipped uploading the livecd-rootfs changes for cosmic as we are not planning on enabling raspi3 images for this distro-series as far as I know. This package is only used during build time so there is no reason to worry about missing functionality.
1805668,2018-11-30 16:22:32 UTC,A bit confused by this bug.  Ubuntu doesn't use raspi3-firmware.  The package used is linux-firmware-raspi2.  I also think there is a high regression potential with the uboot/firmware packages - what happens to the people using Ryan Finnie's unofficial images?
1805668,2018-11-30 16:40:53 UTC,Recently the 3A+ was released https://www.raspberrypi.org/magpi/pi-3a-interview/ so this should be supported too in any new builds.
1805668,2018-11-30 18:25:31 UTC,"The raspi3 additions to livecd-rootfs are just wrong.  Is the use of raspi3-firmware intentional?
If it is you've got pi2 and pi3 having completely different booting.  The config.txt created by livecd-rootfs will be overwritten by raspi3-firmware.  Which is not necessarily bad, because the config.txt wouldn't work with arm64 anyway."
1805668,2018-12-01 14:30:12 UTC,I don't agree with the alterations to u-boot either.  Arm64 doesn't need to be called kernel8.img.  The config.txt should be changed to tell the pi's bootloader to expect aarch64.  That way you can keep the uboot.bin name and it is consistent between armhf and arm64.
1805668,2018-12-02 14:51:24 UTC,One of the good things about Raspbian is it is able to run on any Pi.  You can take an SD card out of a Pi2 and it will work in a Pi3B+ or vice versa.  This is definitely what Ubuntu should be aiming for and it is not hard to implement.
1805668,2019-01-15 12:31:53 UTC,"Adam: we are currently working on base support of the raspi3 boards based on the old work that was done for the raspi2 (and please note those did not get much love since a while anyway). The way they work right now is not perfect, but this is the first 'iteration' we intend to set as a baseline for further work. We're trying to get everything for that 'baseline' landed in bionic right now to make work on this easier (e.g. having daily builds etc). There are some things we could already do better but there's a tight time-frame we need to fit into."
1805668,2018-12-04 07:46:06 UTC,"Hello Łukasz, or anyone else affected,"
1805668,2018-12-04 09:37:57 UTC,Not sure why something that is clearly broken should be accepted?
1805668,2018-12-04 09:49:17 UTC,To answer the description update by vorlon: The raspi3-firmware package contains scripts that get run on a kernel update.  This creates a new config.txt and makes copies of kernel/dtb etc.  Pretty certain this is not how gadget snaps work (the firmware is obtained directly from git is it not?).  U-boot will be by-passed by raspi3-firmware.
1805668,2018-12-04 10:10:58 UTC,"@steve note that we will have to update to u-boot v2018.11 and rpi firmware tag 1.20180924 to support the recently released pi3b A+, i was planning to land a change for this soon in the gadget."
1805668,2018-12-04 10:14:00 UTC,"On Tue, Dec 04, 2018 at 09:49:17AM -0000, Adam Smith wrote:

> To answer the description update by vorlon: The raspi3-firmware package
> contains scripts that get run on a kernel update.  This creates a new
> config.txt and makes copies of kernel/dtb etc.  Pretty certain this is
> not how gadget snaps work (the firmware is obtained directly from git is
> it not?).  U-boot will be by-passed by raspi3-firmware.
"
1805668,2018-12-02 14:55:25 UTC,"If Ubuntu has to continue with u-boot (and I don't know why it does), then it should implement the recent improvements i.e. you don't have to specify a FDT address."
1805668,2018-12-04 12:43:03 UTC,"Ubuntu core and classic haven't been in sync for over a year.  Linux-firmware-raspi2 and the pi2 gadget use different versions of the firmware.  The pi2 v1.2 is closer to the pi3b than the original pi2.  Pegging the version of firmware for the pi2 makes little sense, stopping usb booting for example."
1805668,2018-12-04 11:43:03 UTC,"On Tue, Dec 04, 2018 at 10:10:58AM -0000, Oliver Grawert wrote:

> @steve note that we will have to update to u-boot v2018.11 and rpi
> firmware tag 1.20180924 to support the recently released pi3b A+, i was
> planning to land a change for this soon in the gadget.
"
1805668,2019-01-14 14:52:05 UTC,"The config.txt generated by livecd-rootfs will not work on arm64 and the fdt address conflicts with the bootscript address used with the pi3.  The beta image may boot okay, but that is only because so many mistakes have been made across the pi packages that somehow, miraculously, it actually works.  Works as intended?  Definitely not.  Or at least I hope not."
1805668,2019-01-14 14:18:39 UTC,How on earth do they work as intended?  You've ignored everything I've written.
1805668,2019-01-14 09:33:42 UTC,"To the SRU team: so the livecd-rootfs changes in 2.525.11 can go in and work as intended, although we're still missing a few additional changes needed for the images to be buildable through cdimage. But there will be a follow up upload with those. I'll be re-using this SRU bug for those."
1805668,2018-12-21 09:17:19 UTC,"For completeness I'll point out some problems with flash-kernel.... The 3B+ is not supported (bug 1764491), nor is the CM3 or new 3A+.  Whenever a new revision of a board comes out it breaks."
1805668,2019-01-10 16:45:52 UTC,"I suggest ditching u-boot or compiling it using rpi_3_32b_config and then enabling BCM2836 support in menuconfig. To boot the official server image on the Pi 3, you have to make a few tweaks first, which include disabling u-boot, updating the bootloader files, and adding additional firmware for WiFi to work. An official image with all of this done beforehand would be more simple. Considering that the original Pi 3 was released in 2016, Ubuntu Server should work on both the Pi 3B and 3B+/3A+ out of the box. It's a pretty easy thing to implement."
1805668,2018-12-07 13:21:48 UTC,That should of read bug 1806813 !
1805668,2018-12-07 13:20:23 UTC,But 1806813 contains results from some early testing.
1805668,2018-12-06 20:50:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805668,2018-12-06 08:54:21 UTC,"Also, raspi3-firmware was intended for use with the generic kernel.  The Debian generic kernel can be booted directly by the pi firmware (unlike  Ubuntu's which needs the assistance of u-boot/grub2).  Consequently the scripts expect different dtb names to those used by the linux-raspi2 kernel."
1805668,2018-12-04 22:26:43 UTC,"It's not just me who thinks raspi3-firmware is ""useless for many users"" - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848101"
1805668,2018-12-07 17:32:36 UTC,"As noted by Adam, my experience is documented in #1806813.   As a quick summary, I am attempting to boot the new 64-bit Arm Server image located at http://cdimage.ubuntu.com/releases/18.04/beta/ on a Compute Module 3.  I know that Ubuntu Core is supported on the Compute Module 3, but, Classic is preferred for this project.   I have actually gotten it booting with the changes Adam pointed out in that thread, but it would be nice if the CM3 was supported out-of-the-box with this image.  Thank is advance!"
1805670,2019-03-12 09:58:48 UTC,"Seems like there's new BIOS for this platform:
https://support.hp.com/us-en/drivers/selfservice/hp-zbook-studio-g5-mobile-workstation/18865653"
1805670,2018-11-29 10:26:23 UTC,apport information
1805670,2018-11-29 14:58:08 UTC,Link to change the package name does not work. It has already been changed to linux. I assume the issues are kernel related. Need I change anything else?
1805670,2019-03-12 09:47:50 UTC,"An update. I have update 18.04.2 with the 4.18 kernel.
Still not working. Still have ACPI errors. Now I get
error messages for thew USB ports - ""can't set config""."
1805670,2019-03-12 17:38:09 UTC,"That is one exercise I would like to avoid.
Don't want to brick this thing. Going to look into it."
1805670,2020-11-16 21:16:21 UTC,"This happens for me as well with 20.04 and HP ZBook G5. But after turning of almost everything in the BIOS and discovering that it actually booted (without acpi=off), I eventually discovered that it works if I disable... the microphone(!). There are some errors, but it boots and is stable afterwards."
1805670,2019-09-12 11:45:01 UTC,Updated to latest BIOS.
1805670,2020-08-06 09:26:36 UTC,Hi!
1805670,2020-08-06 13:58:15 UTC,"Please try ""safe graphics"" boot option."
1805670,2020-10-26 07:32:36 UTC,"Hi@all,"
1805670,2018-11-29 10:26:22 UTC,apport information
1805670,2019-07-04 19:05:58 UTC,I have the latest BIOS running on this machine and also getting ACPI errors (not running ubuntu but manjaro ( 5.1.15-1-MANJARO #1 SMP PREEMPT)
1805670,2018-11-29 10:26:20 UTC,apport information
1805670,2018-11-28 20:51:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1805670,2018-11-29 10:26:18 UTC,apport information
1805670,2018-11-28 17:28:22 UTC,Adding firmware output. I have the latest BIOS version
1805670,2018-11-28 21:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805670,2018-11-29 10:26:04 UTC,apport information
1805670,2018-11-29 10:26:06 UTC,apport information
1805670,2018-11-29 10:26:07 UTC,apport information
1805670,2018-11-29 10:26:09 UTC,apport information
1805670,2018-11-29 10:26:19 UTC,apport information
1805670,2018-11-29 10:26:12 UTC,apport information
1805670,2018-11-29 10:26:13 UTC,apport information
1805670,2018-11-29 10:26:15 UTC,apport information
1805670,2018-11-29 10:26:15 UTC,apport information
1805670,2018-11-29 10:26:16 UTC,apport information
1805670,2018-11-29 10:26:11 UTC,apport information
1805672,2019-01-10 13:56:12 UTC,So there are several bugs here.
1805672,2019-01-10 14:01:05 UTC,"Andres, you seem to indicate that the real bug was that configauth wasn't working during the failing maas-proxy restart. That should be fixed now, since i think RBAC and the proxy were fighting for the ports."
1805672,2019-01-10 14:11:14 UTC,"BTW, I did reproduce the maas-proxy failure, and I was able to use configauth to configure MAAS to use RBAC without any problems."
1805672,2019-07-31 04:17:27 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1805679,2019-06-06 13:42:43 UTC,https://review.opendev.org/#/c/663668/
1805679,2019-09-04 14:35:13 UTC,"Reviewed:  https://review.opendev.org/663668
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=90bffdc36187fb535e6a54bff16b2112513ec501
Submitter: Zuul
Branch:    master"
1805679,2019-09-18 15:36:36 UTC,This issue was fixed in the openstack/glance 19.0.0.0b1 development milestone.
1805686,2019-11-01 03:41:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805686,2019-11-01 03:42:09 UTC,"Confirmed fixed in eaon, and perhaps earlier."
1805691,2020-02-20 13:37:59 UTC,This is seeded now.
1805691,2019-11-14 08:01:48 UTC,"I think we were already fine because:
- security said this code was already acked when it was part of nova -> ack
- package looked ok and had new Dependencies over what nova had before
- we were afraid of duplication, but that is resolved now."
1805691,2019-11-13 15:52:45 UTC,I'd like to see if we can get this placement MIR evaluated again.
1805691,2019-02-13 15:16:06 UTC,"[16:01] <coreycb> cpaelzer: do you think we can re-evaluate this MIR? https://bugs.launchpad.net/ubuntu/+source/placement/+bug/1805691
[16:01] <ubottu> Launchpad bug 1805691 in placement (Ubuntu) ""[MIR] placement"" [Undecided,Expired]
[16:02] <coreycb> the security team ACKed it I believe
[16:02] <coreycb> i don't think nova is going to drop their placement support until train (corresponds to Ubuntu E release) but it would be nice if we could move forward with charm changes"
1805691,2020-04-21 18:49:21 UTC,"Override component to main
placement 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal: universe/net -> main
placement-api 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal amd64: universe/net/optional/100% -> main
placement-api 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal arm64: universe/net/optional/100% -> main
placement-api 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal armhf: universe/net/optional/100% -> main
placement-api 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal i386: universe/net/optional/100% -> main
placement-api 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal ppc64el: universe/net/optional/100% -> main
placement-api 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal riscv64: universe/net/optional/100% -> main
placement-api 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal s390x: universe/net/optional/100% -> main
placement-common 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal amd64: universe/net/optional/100% -> main
placement-common 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal arm64: universe/net/optional/100% -> main
placement-common 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal armhf: universe/net/optional/100% -> main
placement-common 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal i386: universe/net/optional/100% -> main
placement-common 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal ppc64el: universe/net/optional/100% -> main
placement-common 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal riscv64: universe/net/optional/100% -> main
placement-common 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal s390x: universe/net/optional/100% -> main
placement-doc 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal amd64: universe/doc/optional/100% -> main
placement-doc 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal arm64: universe/doc/optional/100% -> main
placement-doc 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal armhf: universe/doc/optional/100% -> main
placement-doc 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal i386: universe/doc/optional/100% -> main
placement-doc 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal ppc64el: universe/doc/optional/100% -> main
placement-doc 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal riscv64: universe/doc/optional/100% -> main
placement-doc 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal s390x: universe/doc/optional/100% -> main
python3-placement 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal amd64: universe/python/optional/100% -> main
python3-placement 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal arm64: universe/python/optional/100% -> main
python3-placement 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal armhf: universe/python/optional/100% -> main
python3-placement 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal i386: universe/python/optional/100% -> main
python3-placement 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal ppc64el: universe/python/optional/100% -> main
python3-placement 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal riscv64: universe/python/optional/100% -> main
python3-placement 3.0.0~b3~git2020041014.0f90d197-0ubuntu1 in focal s390x: universe/python/optional/100% -> main
29 publicat..."
1805691,2018-12-11 15:48:04 UTC,"@Christian, thanks for the review."
1805691,2018-12-11 14:45:58 UTC,Thank you for consulting the security team on this. No need for a security re-review since we were already supported this before and keeping it in main separately doesn't add a significant new cost.
1805691,2018-12-11 14:36:13 UTC,"Lintian only has 3*pedantic (debian-watch-does-not-check-gpg-signature, insecure-copyright-format-uri, package-uses-old-debhelper-compat-version) and 1*normal newer-standards-version"
1805691,2018-12-11 14:20:06 UTC,Team subscriber is ok “OpenStack Ubuntu packagers” is subscribed on the package already
1805691,2019-02-10 04:17:50 UTC,[Expired for placement (Ubuntu) because there has been no activity for 60 days.]
1805691,2018-11-28 19:29:29 UTC,LP won't allow opening bug against placement atm.
1805693,2018-11-28 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805693,2020-07-09 12:11:44 UTC,"This issue seems to occur with kernels > 4.10 and < v4.19
and got already fixed with applying two patches to bionic (and cosmic) in LP 1810998 - thx to Mauricio Faria de Oliveira.
Hence this bug here can be considered as done and I mark this bug as a duplicate of LP 1810998."
1805696,2018-11-28 22:42:57 UTC,"This is where people interested in getting a Mac build started to meet:
https://chat.inkscape.org/channel/mac-dev"
1805696,2018-11-28 22:41:34 UTC,"Yes, Inkscape doesn't have a Mac packager currently. We are in desperate need for one. You aren't by any chance?"
1805696,2018-11-28 22:16:49 UTC,"Oh great, thanks!"
1805696,2018-11-28 20:55:18 UTC,"if you are using Inkscape 0.92.1, as your text seems to indicate, then you might wish to upgrade to 0.92.3:
https://inkscape.org/release/inkscape-0.92.3/"
1805696,2018-11-28 22:19:35 UTC,"Oh, actually, I'm running Inkscape 0.92.2 5c3e80d on MacOS. 0.92.3 hasn't been released yet for MacOS. Is there some build issues preventing that?"
1805697,2020-12-01 10:35:50 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1805697,2019-02-22 13:53:55 UTC,I have the same issue.  The patch (which is already included in my git source) did not help.  I can use the command line solution but it's not ideal as I connect to the VM from multiple computers with different resolutions.
1805697,2018-12-01 09:07:22 UTC,"I mean this works: -device virtio-vga,xres=1920,yres=1080"
1805697,2021-01-31 04:17:19 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1805697,2018-11-29 13:16:59 UTC,"-device virtio-vga,xres=<width>,yres=<height>"
1805697,2018-11-29 13:15:22 UTC,https://patchwork.ozlabs.org/patch/1005355/
1805697,2018-12-01 06:23:35 UTC,"Hi, Gerd."
1805697,2018-11-28 20:35:15 UTC,Is it possible to set init resolution when VM is starting?
1805699,2019-01-18 19:42:39 UTC,"Hi, the problem happened again: i turned on the laptop and left it on the gdm login screen for a while, so the screen went black (all this with the lid closed, the laptop is connected to an external monitor and keyboard + mouse). I woke up the screen moving the mouse cursor and i typed in username and password, the login screen disappeared and the laptop went in suspend mode. I had to open the lid to continue using it."
1805699,2018-12-17 23:07:24 UTC,"I think that you can close this, the problem didn't show up anymore, probably it was something temporary."
1805699,2019-04-28 12:12:55 UTC,"Hi, as now i can reliably reproduce this by simply closing the lid before logging in. The laptop goes into suspend right after typing the password and pressing enter."
1805699,2018-11-29 08:06:14 UTC,systemd-inhibit:
1805699,2018-11-29 07:09:19 UTC,"@Daniel, the setting shouldn't matter in that case, when there is an external display connected suspend should be inhibited on lid close.
Could you profive the output of ""systemd-inhibit""?"
1805699,2018-11-29 01:52:53 UTC,Can you please run 'gnome-tweaks' and check that:
1805699,2018-11-29 09:21:22 UTC,"Right, in your log the lid is correctly inhibited"
1805699,2018-12-02 12:12:51 UTC,"Hi, sorry for the delay, I tried to trigger this behavior many times, but with no success."
1805701,2020-03-30 21:31:37 UTC,It was discovered recently that ntp was not related to nrpe in any of the FCB skus.  This check will also be useful to verify that nrpe and ntp have a required relation fulfilled.
1805701,2020-08-31 05:10:11 UTC,"Part of this is now implemented, in that you can write rules which simply target the charm name, rather than the unit name. So, if rules were added for these relations, they could simply ensure that all ""NTP"" deployed units (regardless of name) are related to NRPE unit. Or, more specifically, the hacluster/NRPE example provided should be possible now."
1805701,2020-10-07 21:32:41 UTC,"During implementation, it may be nice to have ""required relations"" (nrpe:nrpe-external-master to various charms) and ""forbidden relations"" (like filebeat<->elasticsearch)"
1805702,2018-11-29 19:21:04 UTC,"VirtualBox:~$ lsb_release -crid
Distributor ID:	Ubuntu
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic"
1805702,2018-11-29 19:21:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805702,2018-12-04 03:12:13 UTC,"My officemate just ran into this while upgrading to 18.10, and changing"
1805702,2018-12-04 16:53:24 UTC,"Yup, that fixes it, just installed from source.. attaching patch.
Unsure if this is a real solution because of the warning messages."
1805702,2018-12-05 04:21:24 UTC,"The attachment ""rules.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1805708,2018-11-29 13:31:04 UTC,"Which has been fixed in git now, https://gitlab.gnome.org/GNOME/gnome-user-docs/commit/4c2be261"
1805708,2018-11-29 09:46:51 UTC,"Thank you for your bug report, indeed it's an issue in the upstream GNOME documentation still
https://gitlab.gnome.org/GNOME/gnome-user-docs/blob/master/gnome-help/C/video-dvd.page#L49
Reported upstream https://gitlab.gnome.org/GNOME/gnome-user-docs/issues/31"
1805710,2018-11-30 19:54:58 UTC,This is actually an issue in the apport-package hook provided by compiz. It contains the following:
1805713,2018-11-30 21:17:55 UTC,Fixed in x.4317.
1805719,2020-11-20 04:17:26 UTC,[Expired for mate-terminal (Ubuntu) because there has been no activity for 60 days.]
1805721,2018-11-29 21:03:17 UTC,"This header is actually incorrect.  the root of the issue seems to be that the query for list of metrics in prometheus is missing the ext_net metrics, though the graphs work if you skip the check."
1805730,2020-11-20 04:17:27 UTC,[Expired for mate-terminal (Ubuntu) because there has been no activity for 60 days.]
1805733,2018-11-29 01:54:33 UTC,"Confirmed the bug is in 18.10, but not in 16.04. What version of Ubuntu are you using?"
1805733,2018-11-29 01:54:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805733,2018-11-29 01:56:46 UTC,Please also report the bug here:
1805733,2018-11-29 07:24:05 UTC,"Sorry, I'm using current 18.04."
1805733,2019-01-29 04:17:23 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1805736,2018-11-29 02:51:55 UTC,oops
1805736,2018-11-29 02:28:19 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1805740,2019-01-15 17:51:37 UTC,Fixed in https://review.openstack.org/#/c/620767/
1805740,2019-02-28 14:17:49 UTC,This issue was fixed in the openstack/senlin-dashboard 0.10.0 release.
1805753,2018-11-30 16:16:40 UTC,"I've also noticed that after disconnecting, if I drag windows to the right, they go off the laptop screen and become inaccessible from the screen."
1805755,2019-01-11 18:07:54 UTC,This issue was fixed in the openstack/python-karborclient 1.2.0 release.
1805758,2018-11-29 04:16:49 UTC,"Sounds like bug 1758967, although that one is a bit unclear."
1805767,2020-03-09 18:44:57 UTC,"Reviewed:  https://review.opendev.org/708340
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=09059de8a9325daceb890b6bae8af4e87aa2a2c1
Submitter: Zuul
Branch:    stable/train"
1805767,2020-02-18 10:56:04 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/708340"
1805767,2020-02-17 17:59:44 UTC,"Reviewed:  https://review.opendev.org/662522
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c29f382f69ed0bfe2c8782913e2a882344ff461f
Submitter: Zuul
Branch:    master"
1805767,2019-08-26 03:28:13 UTC,"Change abandoned by Alex Xu (<email address hidden>) on branch: master
Review: https://review.opendev.org/621077"
1805767,2018-11-30 06:53:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/621077"
1805767,2018-11-30 05:36:24 UTC,Separate PCI request part into another bug https://bugs.launchpad.net/nova/+bug/1805969. This bug report just focus on NUMA.
1805767,2018-11-29 10:14:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/620874"
1805767,2018-11-29 10:06:36 UTC,Both new numa topology request and pci request are missed in resize.
1805767,2019-06-13 14:26:15 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/620874
Reason: Going to take a leap of faith and abandon this because I think [1] is getting close. Hope that's okay, Alex :)"
1805769,2018-12-07 04:12:41 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/623369"
1805769,2018-12-07 04:13:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623393"
1805769,2018-12-07 06:24:50 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/623114"
1805769,2018-12-07 06:29:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623401"
1805769,2018-12-07 06:33:08 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/623393"
1805769,2018-12-19 08:59:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/626119"
1805769,2018-12-20 06:38:30 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/626119"
1805769,2018-12-21 07:38:59 UTC,"As this is proposal to add new config option, I think that it should be handled as RFE and discussed by drivers team before we will start merging code."
1805769,2018-12-21 15:16:20 UTC,This RFE was discussed and approved during today's meeting
1805769,2019-01-18 18:20:19 UTC,"Reviewed:  https://review.openstack.org/626109
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f1592c42d9649e8da952021aa1f6e7a4a127cd48
Submitter: Zuul
Branch:    master"
1805769,2019-01-21 06:48:27 UTC,"Reviewed:  https://review.openstack.org/623401
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=af902dfb2ac8e5bc253af8fb85bc4d0f61bdfa56
Submitter: Zuul
Branch:    master"
1805769,2018-12-19 08:09:48 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/626109"
1805769,2018-12-07 01:28:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623369"
1805769,2018-12-05 09:01:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622897"
1805769,2018-12-06 08:38:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623163"
1805769,2018-12-06 01:42:01 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623114"
1805769,2018-12-05 09:29:02 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/622897"
1805769,2018-12-05 08:07:41 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/622854"
1805769,2018-12-05 06:11:22 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/622075"
1805769,2018-12-05 06:10:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622854"
1805769,2018-12-04 07:53:27 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/621062"
1805769,2018-12-04 07:52:46 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622075"
1805769,2018-12-04 07:37:49 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/621740"
1805769,2018-12-04 05:22:26 UTC,"In the current version, users cannot directly change the max timeout of an rpc client. The value is just rpc_response_timeout (already in neutron.conf) times 10, which is way too long and inflexible."
1805769,2018-12-04 01:35:38 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621740"
1805769,2018-12-03 23:13:16 UTC,"Can you provide some more information on why the current way if handling this ""is not reasonable""? Marking it as incomplete for the time being"
1805769,2018-12-07 01:27:54 UTC,"Change abandoned by nicky (<email address hidden>) on branch: master
Review: https://review.openstack.org/623163"
1805773,2019-01-04 05:42:50 UTC,"Reviewed:  https://review.opencontrail.org/48203
Committed: http://github.com/Juniper/contrail-controller/commit/4e9b2a7e5747a7dc4ec9c5bc5388b58b29984d25
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1805773,2018-12-04 06:27:23 UTC,"Review in progress for https://review.opencontrail.org/47999
Submitter: Parth Sarupria (<email address hidden>)"
1805773,2018-11-29 06:58:22 UTC,"Review in progress for https://review.opencontrail.org/47918
Submitter: Parth Sarupria (<email address hidden>)"
1805773,2018-12-14 06:04:39 UTC,"Review in progress for https://review.opencontrail.org/48203
Submitter: Parth Sarupria (<email address hidden>)"
1805774,2018-12-03 08:28:12 UTC,"Review in progress for https://review.opencontrail.org/47969
Submitter: Pragash Vijayaragavan (<email address hidden>)"
1805780,2018-11-29 06:54:18 UTC,the error just like this
1805784,2018-11-30 18:52:06 UTC,"This is an interesting idea; I don't think you would need another type for this though. Part of the intent of a reserved range is that you can reserve it, and then use it for a particular purpose. I like the idea of adding tags; right now we just have a description field."
1805784,2019-09-19 12:07:07 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1805789,2018-11-30 20:16:33 UTC,"I rerun valgrind with more options to get a more detailed log:
```
$valgrind --leak-check=full --track-origins=yes -v gnome-games
```"
1805796,2019-09-11 12:33:49 UTC,"I also have this problem on latest Ubuntu-MATE 18.04.2 LTS, does not happen on Xubuntu, Lubuntu or any other Ubuntu flavor. Only way back is to toggle ""Use system title bar and borders""."
1805798,2018-12-04 20:48:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805799,2020-11-20 12:38:24 UTC,"Hello,
thank you all for the efforts. However, I am experiencing the same problem as mikivazquez. Has someone had luck installing proxmoxer in the snap? Sadly, I haven't had any. The feature would be really apreciated."
1805799,2020-08-30 21:16:27 UTC,"Instructions for the Snap version MaaS 2.8 build 7808 are the same as described by @mrjester,
only the path to the power drivers has changed:
Instead of 'squashfs-root/usr/lib/python3/dist-packages/provisioningserver/drivers/power/' it's now
'squashfs-root/lib/python3.6/site-packages/provisioningserver/drivers/power/'"
1805799,2020-10-24 20:20:32 UTC,Hello I do it for Maas build 8980 I change the path.. but in web interface I can see:
1805799,2020-11-23 14:47:22 UTC,"@davemcbrave, I could install it. do #13 for the new version."
1805799,2020-06-28 19:04:21 UTC,Instructions for the Snap version MaaS 2.8 build 7328.  I have no idea how to submit this for inclusion.
1805799,2020-12-31 20:20:03 UTC,"Hello,"
1805799,2021-01-03 19:21:12 UTC,If running from a 20.04 host and installing 2.9 with snaps you can do the following (running as root):
1805799,2021-01-21 11:51:33 UTC,When is this going to be available in the snap?
1805799,2020-12-28 21:44:46 UTC,In MAAS 2.9 I am getting errors when I try to use proxmox driver. I followed the procedure given above and copied the files and installed the python module. For some reason maas is giving me this error.
1805799,2020-01-04 13:58:48 UTC,This driver works great for me on proxmox 6
1805799,2018-12-01 19:05:36 UTC,Attachment to previous comment
1805799,2019-11-23 16:00:57 UTC,"Hey Tim,"
1805799,2018-12-01 17:55:57 UTC,"Hi Andres,
No problem, I wrote one, please find attached file.
It is not diff file, but it can be copied to provisioningserver/drivers/power and just register driver in registry.py. It works for me. Tested on MAAS 2.5.0rc1 and Proxmox VE 5.2 but should work with any Proxmox version. It requires python library proxmoxer.
It will be nice if you commit it to MAAS source and use it in future versions of MAAS"
1805799,2018-11-29 12:57:36 UTC,"Hi Woktek,"
1805799,2019-03-09 16:25:12 UTC,I also be interested in integrating proxmox power type. Thanks for your work Wojtek. Did it work with proxmox-container too? Or only vm ?
1805799,2019-03-09 17:22:33 UTC,"Okay I think, only vm's work with pxe-boot... so we don't need support for container here."
1805799,2019-11-23 16:01:23 UTC,(it would still be nice to have this native in MaaS as a package update seems to clear custom files)
1805799,2019-03-09 19:29:56 UTC,"Hi Wojtek,"
1805799,2019-03-27 23:24:05 UTC,Anyone has a handy guide for integrating the provided script to a brand new MAAS install? I'll see what I can do on my side.
1805799,2019-04-11 11:07:58 UTC,"Wojtek (#2): Thanks for sharing your Proxmox power driver, it works great! Would very much like to see it contributed or committed upstream, instead of having to patch my own installation."
1805799,2019-03-09 18:18:40 UTC,"Thank you very much, it work for me!"
1805805,2018-11-30 21:58:38 UTC,Fixed in x.4319.
1805806,2018-11-30 10:50:32 UTC,"This issue could be found on B-4.18 as well, but with 2 ARM64 nodes, it's only failing with the TunderX Cavium node ""starmie"", passed on the Moonshot node ""ms10-34-mcdivittB0-kernel"" instead."
1805806,2019-05-09 08:20:36 UTC,"For Disco,
failed on ThunderX (1 out of 2 runs)
failed on Moonshot"
1805806,2020-08-26 05:08:59 UTC,"Passed on Focal ARM64
5.4.0-44.48-generic"
1805806,2020-08-26 05:09:35 UTC,Need to check if we still have this issue on 5.3 / 5.0 Variants.
1805806,2020-10-01 05:22:50 UTC,This error is populating on Focal 'aws : 5.4.0-1026.26 : amd64' on c5.large and ' aws : 5.4.0-1026.26 : arm64' on a1.2xlarge
1805806,2020-11-23 19:34:34 UTC,affects aws cloud 5.X kernels.
1805806,2020-12-01 16:11:57 UTC,Found on Groovy 5.8.0-31.33 lowlatency & generic. Only failing on one node (lagalla) and passes on the other (rizzo)
1805806,2021-02-19 19:12:55 UTC,Seen with linux-aws 5.4.0-1038.40~18.04.1.
1805806,2018-11-29 10:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805811,2019-09-19 12:00:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1805815,2019-01-11 18:07:53 UTC,This issue was fixed in the openstack/python-karborclient 1.2.0 release.
1805816,2018-11-29 11:18:18 UTC,apport information
1805816,2019-07-01 04:01:15 UTC,What's the output of `cat /sys/power/mem_sleep`?
1805816,2019-06-28 22:44:43 UTC,I have the same problem on Thinkpad X1 Carbon 5th gen with NVMe drive. I get read-only rootfs every time I suspend my laptop (e.g. by closing the laptop's lid).
1805816,2018-11-29 11:18:17 UTC,apport information
1805816,2019-05-27 08:13:16 UTC,"Thanks for following up - we can close this bug, I no longer have this issue. I have attached info just for the record. I upgraded my system BIOS and the problems went away."
1805816,2019-05-27 05:28:32 UTC,"Ian,"
1805816,2019-05-28 10:27:35 UTC,"XPS 9550 is the consumer version of Precision 5510, right?"
1805816,2018-11-29 12:41:54 UTC,"Oops - I can mark this issue as ""New"" but not ""Complete"" (which in turn was me mis-reading the instruction from the bot in #4). Sorry for the noise."
1805816,2018-11-29 12:39:20 UTC,"Sorry - I've hit a hiccup. `apport` wants me to file extra information (as uploaded above, twice) but upon running at the command line it notes:
`
It appears you are currently running a mainline kernel.  It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the upstream kernel developers are aware of the issue.  If you'd still like to file a bug against the Ubuntu kernel, please boot with an official Ubuntu kernel and re-file.
`"
1805816,2018-11-29 12:17:36 UTC,apport information
1805816,2018-11-29 12:17:34 UTC,apport information
1805816,2018-11-29 11:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805816,2018-11-29 13:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1805817,2019-01-28 17:05:31 UTC,"Linked Horizon to this bug for historical context. The maintainers for python-openstackclient no longer use launchpad, so we'll have to track this separately with Storyboard [0]."
1805817,2019-12-10 05:32:49 UTC,"> now broken after configuring a federation protocol
>
> - clouds.yaml / openrc in Horizon
"
1805817,2019-12-09 12:28:46 UTC,Just commenting on this bug again - there is still very valid requirements for other projects be aware of federated keystone
1805817,2019-01-30 08:39:24 UTC,"From horizon developer perspective, it is not easy to setup all available authentication scenarios.
The identity API reference provides examples only for a standalone password auth case.
There is no example for saml and other authentication ways and it is not easy to know what kind of clouds.yaml and openrc should be provided. This is a bottleneck of implementing this feature in horizon( and this is the reason that I chose a way to custom templates in bug 1795851).
Some information from authentication experts (from keystone team) would be appreciated much."
1805817,2019-01-30 08:31:59 UTC,horizon now provides a way for operators to customize their own clouds.yaml and openrc (tracked by bug 1795851).
1805817,2019-01-29 08:32:16 UTC,horizon closed the bug I reported with the option of globally disabling API credentials
1805817,2019-01-28 16:38:37 UTC,"Keystone provides the data needed.  This should be an opentackapi, CLI, and Horizon change."
1805817,2018-11-29 17:48:00 UTC,"horizon could make an equivalent API call to
'openstack user show whoami' for project scoped API credentials"
1805817,2019-01-23 08:40:35 UTC,"Users only know there login credentials, they usually don't know what a federation protocol is, the keystone authentication type or where the ECP endpoint for example:"
1805817,2019-01-22 19:14:28 UTC,"> so the example would be an authenticated user in Horizon.
This is where users go to get their API credentials and there is no reliable resource either in Horizon or Keystone to get them.
"
1805817,2018-11-29 18:22:14 UTC,"thanks Adam, I noticed this, back to horizon team to extrapolate that? it would also be useful to finger users on the command line though"
1805817,2018-11-29 11:50:43 UTC,"> This is not very useful. - and I need a working RC file to get this far!
"
1805817,2018-11-29 17:32:03 UTC,"Thanks Colleen, so the example would be an authenticated user in Horizon.
This is where users go to get their API credentials and there is no reliable resource either in Horizon or Keystone to get them."
1805817,2018-11-29 15:49:51 UTC,"The response in a Keystone token reques provides this data, it is just not exposed in the CLI."
1805817,2019-01-28 16:10:31 UTC,"I may still be missing something, but this sounds like a horizon request. If a user is authenticated horizon could validate their token and display the useful bits of information."
1805818,2018-11-29 11:19:39 UTC,"This one might be the same, or it might be slightly different:"
1805818,2018-12-17 14:43:54 UTC,"Closing a channel is really making that channel inherit the release timeline of the upper channel (unless there isn't an open channel above, in which case the channel is closed for real, with no available releases)."
1805831,2018-11-29 13:00:17 UTC,This change was made by a bot.
1805835,2018-11-29 13:00:25 UTC,This change was made by a bot.
1805835,2019-03-29 11:57:41 UTC,"I can confirm having exactly the same issue with the  WS-C621E-SAGE
Complete configuration:"
1805841,2019-06-11 06:40:20 UTC,"------- Comment From <email address hidden> 2019-06-11 02:33 EDT-------
IBM bugzilla status ->closed, Fix Released for all requested distros"
1805841,2019-06-03 08:45:34 UTC,This bug was fixed in the package s390-tools - 2.6.0-0ubuntu7.3
1805841,2019-05-23 11:59:41 UTC,"------- Comment From <email address hidden> 2019-05-23 07:56 EDT-------
Successfully verified on cosmic with
s390-tools s390x 2.6.0-0ubuntu7.3"
1805841,2019-05-23 08:55:24 UTC,This bug was fixed in the package s390-tools - 2.3.0-0ubuntu3.3
1805841,2019-05-17 09:01:22 UTC,"------- Comment From <email address hidden> 2019-05-17 04:53 EDT-------
I can confirm that
http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main s390x s390-tools s390x 2.3.0-0ubuntu3.3
does fix the issue.
(verified with systemctl daemon-reload. This triggered the problem reliably)"
1805841,2019-05-23 08:45:24 UTC,"The verification of the Stable Release Update for s390-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1805841,2019-05-23 08:44:32 UTC,"Hello bugproxy, or anyone else affected,"
1805841,2019-05-16 16:47:04 UTC,"Hello bugproxy, or anyone else affected,"
1805841,2019-03-08 13:39:27 UTC,"------- Comment From <email address hidden> 2019-03-08 08:36 EDT-------
ping. Any progress on the minimal fix for now?"
1805841,2019-03-15 11:10:56 UTC,------- Comment on attachment From <email address hidden> 2018-12-03 08:05 EDT-------
1805841,2019-03-15 10:57:05 UTC,"Yes, that's in progress - indicated by the SRU Justification that was added to the bug description.
This is part of the SRU process and always needed in case of SRUing or backporting things back to already released Ubuntu versions.
Such things need to be processed starting with the current dev. release (which is disco here) going back to the 'oldest' release the patch should land (in this case bionic)."
1805841,2019-03-15 10:09:32 UTC,"------- Comment From <email address hidden> 2019-03-15 06:04 EDT-------
This is for the s390-tools in disco. Can we backport that fix also into the s390-tools 2.3 of bionic?"
1805841,2019-03-14 00:31:59 UTC,This bug was fixed in the package s390-tools - 2.8.0-0ubuntu4
1805841,2018-12-03 13:10:14 UTC,------- Comment on attachment From <email address hidden> 2018-12-03 08:05 EDT-------
1805841,2018-11-30 12:59:54 UTC,"------- Comment From <email address hidden> 2018-11-30 07:54 EDT-------
The problem is now, that /lib/systemd/system-generators/s390-cpi-vars  overwrites some values that are set by cpictl. (for example the KVM token)."
1805841,2018-11-29 18:45:49 UTC,/lib/systemd/system-generators/s390-cpi-vars correct is how I implemented cpi-vars before cpictl was avaiable.
1805841,2018-11-29 14:19:23 UTC,"------- Comment From <email address hidden> 2018-11-29 09:18 EDT-------
removing /lib/systemd/system-generators/s390-cpi-vars Seems to help. (this seems to be an ubuntu specific extension).
We just need to move this functionality (adding ubuntu and the version) into the common cpi handling."
1805841,2019-04-09 10:59:32 UTC,"------- Comment From <email address hidden> 2019-04-09 06:57 EDT-------
Any update on the SRU process for bionic?"
1805847,2019-01-23 15:46:41 UTC,"Reviewed:  https://review.openstack.org/630664
Committed: https://git.openstack.org/cgit/openstack/ansible-role-systemd_service/commit/?id=d11744b1efd098366792e39f0bc7314a485abb33
Submitter: Zuul
Branch:    master"
1805847,2019-01-15 08:58:48 UTC,"Hi Benoît,"
1805847,2019-01-14 13:26:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630671"
1805847,2019-01-14 09:43:01 UTC,"Hi Benjamin,"
1805847,2019-01-14 13:08:30 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/630664"
1805847,2019-01-03 13:58:32 UTC,DynamicUser needs to be aligned with Group
1805847,2019-01-03 13:57:06 UTC,shame on me
1805847,2019-01-03 13:56:00 UTC,Hello
1805847,2018-11-29 14:16:23 UTC,"I'm using OpenStack Ansible 18.1.0, but it looks like it's the same on master."
1805847,2019-01-07 16:09:39 UTC,"Hi Benjamin,"
1805858,2018-12-12 13:04:40 UTC,Fixed in https://review.openstack.org/#/c/624460/ . Not sure why the association didn't happen.
1805860,2020-07-20 21:42:14 UTC,"Pushed all the way to rel_3_3. Thanks, Dan and Terran!"
1805860,2020-02-19 20:40:51 UTC,"Dawn had tested while there was a problem with the server - after the server was refreshed, the New Developers Group tested and it looks great. Sign off is here:"
1805860,2020-02-19 19:21:08 UTC,This still appears not to be fixed. The long patron name still covers the patron barcode and user name. See attached screen shot.
1805860,2020-01-07 20:22:20 UTC,"I found that reducing the padding-top of .top-content-container didn't work well for all browser widths, so I posted a branch that removes the fixed position for #patron-fixed-tabs"
1805860,2020-01-03 21:44:14 UTC,Still seeing this as of:
1805869,2018-11-30 15:15:59 UTC,Thanks for all the info!
1805869,2018-11-30 01:28:21 UTC,"Sorry, I hit ""post"" too soon. That is to say, if we decide to include a count of explicit + implicit records, that should be a completely separate field."
1805869,2018-11-30 01:27:36 UTC,"Also, if we decide to fix this bug, I don't think we should change the meaning of this field, in case anyone is relying on it reporting the number of /explicit/ records (which is how it has always worked)."
1805869,2018-11-29 18:46:14 UTC,s/Roger/Robert/g sorry :)
1805869,2018-11-29 19:46:16 UTC,"In case it helps you form a workaround to this issue, you can find the BIND zone files that MAAS generates in /etc/bind/maas/zone.<domain>. On MAAS 2.4 and earlier, if you want to see and/or count the DNS records MAAS has generated, this may be the most accurate way to do it."
1805869,2018-11-29 17:17:13 UTC,Can you confirm the version of MAAS you are using?
1805869,2018-11-29 17:00:50 UTC,I have no custom RRs in that zone only the default A RRs placed auto by MAAS after deployment but I would like to get the same results what I got on the GUI where I have ~50 records.
1805869,2018-11-29 16:57:49 UTC,"Hi Andres,"
1805869,2018-11-29 16:45:27 UTC,"Hi Robert,"
1805869,2018-11-29 17:30:31 UTC,MAAS package 2.4.2-7034-g2f5deb8b8-0ubuntu1 on Ubuntu 18.04.1 LTS.
1805869,2018-11-29 18:33:16 UTC,"Hi Roger,"
1805874,2019-01-02 05:19:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1805874,2019-01-07 07:03:55 UTC,This piece of terminal output is interesting:
1805874,2019-10-09 13:17:02 UTC,Potential dupe of bug 1788702?
1805875,2020-11-25 19:51:15 UTC,This doesn't works on kubernetes as no k8s mandatory checks are on place in the contrib canonical rules.
1805875,2020-08-31 05:04:57 UTC,"This is taken care of now, as we have different rules for Kubernetes and OpenStack. The cloud type can be specified at runtime."
1805875,2018-12-05 14:53:58 UTC,"For clarity, not all of the above errors should be suppressed. Only the following are 'incorrect' for a K8's deploy (on AWS)."
1805880,2019-01-17 23:55:17 UTC,"Reviewed:  https://review.openstack.org/621019
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=7af769278aef7e3a170c0da619b67bad7a147d84
Submitter: Zuul
Branch:    master"
1805880,2019-10-10 02:26:30 UTC,"Reviewed:  https://review.opendev.org/687639
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d9217f07b83399373c6e0879a71d943b73632ff5
Submitter: Zuul
Branch:    stable/train"
1805880,2019-10-09 17:50:03 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/687639"
1805880,2019-10-04 21:47:05 UTC,"Reviewed:  https://review.opendev.org/682266
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d4a6023de5bdfe5a6e9214579a35e083a45c1151
Submitter: Zuul
Branch:    master"
1805880,2019-09-27 09:09:42 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1805880,2019-09-27 00:07:54 UTC,"Reviewed:  https://review.opendev.org/621025
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5b995cc8fbf0bb654ed0f6a88091c48548f53f6e
Submitter: Zuul
Branch:    master"
1805880,2019-09-26 22:09:00 UTC,"Reviewed:  https://review.opendev.org/621024
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=e938c496281daa6d1dab66d66bdb2d34abd5ddc3
Submitter: Zuul
Branch:    master"
1805880,2019-09-26 07:48:53 UTC,"Reviewed:  https://review.opendev.org/621023
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f249c9e2b0f39b688ba356feaca7818adfc9f739
Submitter: Zuul
Branch:    master"
1805880,2019-09-14 08:09:50 UTC,"Reviewed:  https://review.opendev.org/680844
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9b694fcd0846898be843d8779960de399497818d
Submitter: Zuul
Branch:    master"
1805880,2019-09-08 02:28:51 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680844"
1805880,2019-02-12 08:42:53 UTC,"Reviewed:  https://review.openstack.org/621022
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=1d4e40252884f054d692e82e170d3f69228ef7ee
Submitter: Zuul
Branch:    master"
1805880,2019-01-23 00:22:26 UTC,"Reviewed:  https://review.openstack.org/621021
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4cf85fcd5de2f903c085ee3a6edefd3091017880
Submitter: Zuul
Branch:    master"
1805880,2019-01-23 00:12:36 UTC,"Reviewed:  https://review.openstack.org/621020
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=3fee2399901bfc91b5eb5dfc71d17b008dd4b7fb
Submitter: Zuul
Branch:    master"
1805880,2019-01-17 23:55:00 UTC,"Reviewed:  https://review.openstack.org/621018
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bd2b7f3ed55dcfeb0036bec71920c785db65214c
Submitter: Zuul
Branch:    master"
1805880,2018-11-29 21:34:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621014"
1805880,2018-12-12 19:29:49 UTC,"Reviewed:  https://review.openstack.org/621016
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4f5e462844b6bebf112b54b75db87165f9e3919b
Submitter: Zuul
Branch:    master"
1805880,2018-11-29 21:34:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621015"
1805880,2018-11-29 21:35:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621016"
1805880,2018-11-29 21:35:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621017"
1805880,2018-11-29 21:35:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621018"
1805880,2019-01-16 01:42:43 UTC,"Reviewed:  https://review.openstack.org/621017
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=e29ff512bb2a5dde3f9eec2b2a2ec596384ec1a2
Submitter: Zuul
Branch:    master"
1805880,2018-11-29 21:36:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621020"
1805880,2018-11-29 21:35:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621019"
1805880,2018-11-29 21:36:43 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621022"
1805880,2018-11-29 21:36:56 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621023"
1805880,2018-11-29 21:37:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621024"
1805880,2018-11-29 21:37:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/621025"
1805880,2018-12-06 07:41:49 UTC,"Reviewed:  https://review.openstack.org/621014
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=216a4d5fc9e9d1f1956f26e7353cc9f09148aaf4
Submitter: Zuul
Branch:    master"
1805880,2018-12-06 23:44:50 UTC,"Reviewed:  https://review.openstack.org/621015
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8658011e41c05f79694eb4df306e07a0db1ce9a9
Submitter: Zuul
Branch:    master"
1805880,2018-11-29 21:36:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621021"
1805881,2018-11-29 18:08:17 UTC,The dkms compilation is failing with the following error:
1805894,2019-10-30 15:34:50 UTC,"I thought the `less_questions` options set to true would mean the ""save configuration on exit"" would be disabled as well but it doesn't seem to work?"
1805894,2019-12-27 07:33:11 UTC,"JumaX9: No, the configuration is always saved (that's the reason of this bug). Less questions options is just to disable some dialogs when sakura is closed."
1805895,2019-07-10 17:34:42 UTC,"(3.2.6) This looks like a saved column validation issue for eg-grids with the auto-fields attribute. Bucket grids load columns from an IDL class in addition to a default column config. But, at the point when saved columns are checked that they match a column on the grid, only the default columns have loaded, so any saved IDL columns are ignored as invalid."
1805895,2019-07-31 18:22:54 UTC,Patch does the thing. Signoff branch is user/gmcharlt/lp1805895_signoff.
1805895,2019-06-06 22:04:29 UTC,We are on 3.2.5. We are unable to save column configurations in the record buckets. It seems to stick with Item Status and User buckets. We are not using Hatch.
1805895,2019-08-01 16:30:20 UTC,"Also, congratulations on having your first patch accepted into Evergreen, Dan!"
1805895,2019-08-01 16:12:54 UTC,One more signoff from me and now it's pushed to everything between rel_3_1 and master.
1805895,2019-05-31 15:14:49 UTC,"I haven't tested Record or User buckets, but this is definitely affecting Item Buckets for me, (Evergreen 3.2.4). And no Hatch."
1805895,2019-01-16 23:26:16 UTC,"Update: In 3.2.2 we are seeing this problem with Record Buckets, but User Buckets and Item Buckets appear to be working fine."
1805895,2019-03-08 17:05:53 UTC,"Hmm, we're on 3.2.3 now and not seeing the problem with Item or User buckets, just Record buckets. (Not sure if we've applied a different patch from a different ticket that has fixed these?)"
1805895,2018-12-04 14:48:48 UTC,"These grids appear to have correct persist-key settings, and they are included in the new server-side database settings. So perhaps there's a bug in the bucket apps somewhere."
1805895,2019-01-16 23:26:52 UTC,"At PINES, we are only seeing this behavior in record buckets. Item and user buckets are saving column changes"
1805895,2019-05-15 16:13:53 UTC,"We're still seeing this consistently in Indiana, and we've always told staff to not use the local storage settings in Hatch, so probably not Hatch at fault."
1805895,2019-03-08 16:27:49 UTC,"We are on 3.2.3 and I am also finding the same issue in Item, Record and User buckets. As a cataloger I don't use User buckets, but I opened one, added fields, saved, refreshed, and it changed. I used reset columns, because I didn't remember exactly what they were before, and got a very different configuration (with lots of duplication of fields). I saved THAT configuration, refreshed again, and it went to the original set of columns. Could this have been set by our System Admin and that is why it sticks in that configuration and the user can't change it permanently?"
1805895,2019-02-11 15:25:51 UTC,"In 3.2.3 we are seeing the issue in Record,Item, and User buckets alike."
1805901,2018-12-19 08:13:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626110"
1805901,2018-12-19 14:04:05 UTC,"Reviewed:  https://review.openstack.org/626110
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b05ca399d86ae6103c717936cb462ca849a56382
Submitter: Zuul
Branch:    master"
1805901,2018-12-19 17:27:41 UTC,"Reviewed:  https://review.openstack.org/626113
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b4ebca1d029755ae778d6e462297d2182c6fc9e6
Submitter: Zuul
Branch:    master"
1805901,2018-12-20 13:45:18 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626580"
1805901,2018-12-20 13:45:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626581"
1805901,2019-01-02 12:53:27 UTC,"Reviewed:  https://review.openstack.org/626581
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c4db57c3de377e61a37b38115d8d9503badfae88
Submitter: Zuul
Branch:    stable/rocky"
1805901,2019-01-02 12:53:40 UTC,"Reviewed:  https://review.openstack.org/626580
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=44d405083d0da0c123d0794ede1f546e3c87a38d
Submitter: Zuul
Branch:    stable/rocky"
1805901,2019-03-22 03:45:11 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1805901,2019-03-24 23:40:00 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1805902,2019-03-24 23:40:02 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1805902,2019-03-22 03:45:03 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1805902,2019-01-02 12:53:50 UTC,"Reviewed:  https://review.openstack.org/626579
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ec91a66da4929a4d7634a57cba3cba79bd0a6146
Submitter: Zuul
Branch:    stable/rocky"
1805902,2018-12-20 13:42:29 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626579"
1805902,2018-12-20 04:20:05 UTC,"Reviewed:  https://review.openstack.org/626416
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f254696d061920890180083a9c8f76101aa2731
Submitter: Zuul
Branch:    master"
1805902,2018-12-20 01:04:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626416"
1805902,2018-12-19 08:23:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626113"
1805903,2018-11-30 21:14:23 UTC,Fixed in x.4316.
1805907,2018-11-30 17:29:01 UTC,There are several other options that could be used for example a system serial number or some other pattern node-{serial}. etc...
1805907,2019-04-03 13:36:20 UTC,cross referenced in design repo issues:
1805907,2019-09-24 07:10:04 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1805913,2020-04-03 22:43:24 UTC,"After reading through the discussion on the mailing list, as it's all about ext4, I got curious...
I'm testing with qemu-user-static and regulary build arm images in a tmpfs. This show similar behaviour and readdir() fails. However, running in the same root copied onto a btrfs, it seems fine.
Maybe this is an even less bad workaround for some folks?"
1805913,2020-03-27 16:00:12 UTC,"Yes, using a 32-bit host QEMU process will also work. You might run into a few guest programs that don't work with that -- a 64-bit QEMU process allows us to give the guest the full address space it might need, while a 32-bit QEMU process means that QEMU itself must share with the guest, so if the guest uses a lot of virtual memory or is picky about where it maps things then it might fail to mmap() things where it wants them. But it's probably overall the least-bad workaround at the current time."
1805913,2020-02-06 13:34:48 UTC,Thanks Marcin. I tested your solution but by me it still gets stuck at the same point. Here's what I did:
1805913,2020-02-02 20:11:10 UTC,"Ah, great thanks. It looks like there are patches that fix qemu, although the setup looks a bit complex. I'll report if I get something going."
1805913,2020-01-30 10:47:16 UTC,"There has been some motion on this by Aladjev Andrew.  I will butcher the explanation of his approach if I try, but it is described in the following bugs.  I have no idea of the schedule, or even possibility of adoption; it seems to still be in proof-of-concept phase."
1805913,2020-01-30 08:20:18 UTC,"Sorry, meant `< 2.28` above."
1805913,2020-03-27 15:19:09 UTC,"I seem to have found another workaround. Knowing now what causes this my guess was: If I make the qemu-arm-static on the host a 32 bit binary and get ""multilib"" running to make my 64 bit Linux installation run this, then in theory this incompatibility should not happen. If it would, then 32 bit x86 applications whould run into the same problem."
1805913,2019-08-01 13:32:06 UTC,"Unfortunately there is no kernel API which we can use on the host to say ""give me inodes and offsets which will fit into a 32 bit field"". The 'getdents' syscall uses the ""unsigned long"" type for the d_ino and d_off fields, so on a 64-bit host these will be the same size as the ino64_t and off64_t used by 'getdents64', and you will still have the ""trying to fit a quart into a pint pot"" problem."
1805913,2020-01-30 08:19:28 UTC,Is there a workaround for this? I tried:
1805913,2018-12-01 13:44:10 UTC,More notes: this bug hits glibc-2.28 and later. It works on glibc-2.27. Therefore to reproduce it it needs ubuntu 18.10 or later. Seems like it works for 18.04.
1805913,2019-03-19 17:16:50 UTC,"The bug also affects shared-mime-info. update-mime-database uses readdir and ends up generating an empty database without reporting any errors, causing pixbuf and anything else that relies on the mime database not to work properly."
1805913,2020-02-02 21:01:45 UTC,This problem affected my virtual environment which I used (via qemu-static) to build my project for RaspberryPI platform. After I upgraded my virtual Raspbian to buster release `readdir` stopped working (as described in this thread) due to mapping of 64 inode numbers to qemu 32bit ARM land. I needed this builder working and I found a workaround in some obscure (2nd page of google result) blog.
1805913,2019-04-16 13:20:43 UTC,https://lkml.org/lkml/2018/12/27/155
1805913,2019-03-25 20:11:59 UTC,"I was also hit by this on Gentoo with a 64bit host running 32bit static chroot (arm).  If it matters at all, I saw it after upgrading the 32bit arm chroot to glibc-2.28, while the host was still on 2.27."
1805913,2019-08-01 13:00:13 UTC,"After studying linux-user/syscall.c a bit, would it be possible to work around this issue by doing something like the following:"
1805914,2018-11-30 00:25:15 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f3162540c00 ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f3162542848 ""munmap_chunk(): invalid pointer"") at malloc.c:5336
 munmap_chunk (p=<optimized out>) at malloc.c:2830
 grep_source_clear (gs=gs@entry=0x55757aa67a38 <todo+2200>) at grep.c:2087
 work_done (w=<optimized out>) at builtin/grep.c:160"
1805914,2018-11-30 00:30:53 UTC,"Reproduced on different hardware.  It’s not entirely deterministic, and seems to disappear entirely with --threads=1, so it must be some kind of race condition."
1805914,2018-11-30 00:54:43 UTC,Bisecting git.git shows v1.9-rc0~63^2 as the first bad commit:
1805914,2018-12-04 00:21:55 UTC,The crash occurs with glibc 2.28 and not with glibc 2.27.  Bisecting glibc.git shows glibc-2.28~122 as the first bad commit:
1805914,2019-09-16 14:16:27 UTC,"Closing as fixed, since glibc 2.29 shipped in disco, and cosmic is EOL."
1805955,2018-11-30 03:53:08 UTC,"There's a new test in this version of adt, ""TEST-22-TMPFILES"". It looks like this test fails because there's a permission problem on the test script itself ""test.sh"""
1805966,2018-12-03 16:07:00 UTC,Is there any more detail we can get around steps to reproduce?
1805966,2018-12-06 07:13:52 UTC,"Sorry, here's some more info from Xav Paice - this is from a client site, so I'll leave it on pastebin.canonical.com rather than copying it in here."
1805966,2019-10-31 03:40:51 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1805966,2019-11-07 15:21:37 UTC,Proposed: https://github.com/juju/juju/pull/10878
1805969,2018-12-06 13:01:03 UTC,https://review.openstack.org/#/c/621077/
1805971,2019-10-03 13:31:58 UTC,still valid?
1805971,2019-12-12 01:44:56 UTC,plars is working on this https://code.launchpad.net/~pwlars/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/376659
1805976,2018-11-30 08:03:49 UTC,"When continuing with section 3.8 of the guide, the next step"
1805976,2018-11-30 08:08:41 UTC,"In section 3.9, I felt lost when finding out the version to inser in"
1805976,2018-11-30 08:14:43 UTC,Sent the previous comment too early. Completing here:
1805979,2018-11-30 13:55:30 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1805984,2018-12-05 23:48:00 UTC,"knowledge of the status of openstack service is currently not within the scope of placement to track.
it is undesirable however to get a No Valid host from the nova api due to the presence of downed compute nodes in the placement response."
1805984,2018-12-06 12:38:18 UTC,ML thread about this:
1805984,2019-04-22 18:16:51 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654596"
1805984,2019-07-09 17:32:14 UTC,"Reviewed:  https://review.opendev.org/654596
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3f0605c28987f46cf4a05af0140e2e5de7d5ad0a
Submitter: Zuul
Branch:    master"
1805984,2019-09-27 09:02:07 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1805985,2019-09-06 21:18:23 UTC,You can add arguments to a command in the Command: field when editing the menu entry via Mozo.
1805992,2018-12-05 17:27:41 UTC,So since this was reported before no action should be taken to fix the bug? !!!!
1805992,2018-12-09 17:45:32 UTC,"The ""bug"" is because the hyperspec package includes an invalid URL. Fix the package by correcting the URL and the ""bug"" is fixed."
1805993,2019-10-31 03:41:46 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1805993,2018-12-04 15:55:36 UTC,"Did the charm change name? I'm trying to see how it works after the upgrade-charm to the later store version and wonder if something in the metadata changed that allowed it to pass through. It looks like it's named ""nrpe-external-master"" but then you say it works after upgrade with just nrpe? Were these two different tests?"
1805993,2018-12-05 07:01:32 UTC,"> Did the charm change name ?
"
1805993,2018-12-06 04:29:40 UTC,The charm changed name. The original charm name was 'nrpe-external-master' ('name: nrpe-external-master' in its metadata.yaml). The upgrade-charm --switch was attempting to change it to a charm named 'nrpe'.
1805993,2018-12-07 03:59:04 UTC,This is the check that fails - https://github.com/juju/juju/blob/2.4/cmd/juju/application/upgradecharm.go#L513
1805994,2019-11-13 17:57:51 UTC,"From looking at the logs, I don't think our linux-hwe (now 5.0) experiences this failure on i386."
1806005,2018-11-30 10:33:10 UTC,"The TL;DR after this trip though the package:
- fixed by latest upstream/Debian
- upstream didn't release yet (debian at upstream/8.6.90 for now in git)
- Debian didn't release the upload with the fix yet
- package is ""only"" in Universe"
1806005,2018-11-30 10:24:50 UTC,I'm reading through git in Debian if/what the fix there would be.
1806005,2018-11-30 10:24:34 UTC,"With enough debugging switched on I got this error:
[error  ] virtual HRESULT M4LMAPISession::OpenMsgStore(ULONG_PTR, ULONG, const ENTRYID*, LPCIID, ULONG, IMsgStore**): msp->Logon failed: logon failed (80040111)"
1806005,2018-11-30 10:24:24 UTC,Trying with mysql (preferred on Ubuntu) instead of mariadb.
1806005,2018-11-30 09:40:01 UTC,Note: this is a universe package
1806005,2018-11-30 09:33:25 UTC,"Also apparmor Denies:
[   57.617995] audit: type=1107 audit(1543569390.209:16): pid=502 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor=""DENIED"" operation=""dbus_method_call""  bus=""system"" path=""/org/freedesktop/systemd1"" interface=""org.freedesktop.systemd1.Manager"" member=""GetDynamicUsers"" mask=""send"" name=""org.freedesktop.systemd1"" pid=3886 label=""/usr/sbin/kopano-server"" peer_pid=1 peer_label=""unconfined""
                exe=""/usr/bin/dbus-daemon"" sauid=105 hostname=? addr=? terminal=?'
[   57.959436] audit: type=1107 audit(1543569390.549:17): pid=502 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor=""DENIED"" operation=""dbus_method_call""  bus=""system"" path=""/org/freedesktop/systemd1"" interface=""org.freedesktop.systemd1.Manager"" member=""LookupDynamicUserByName"" mask=""send"" name=""org.freedesktop.systemd1"" pid=3886 label=""/usr/sbin/kopano-server"" peer_pid=1 peer_label=""unconfined""
                exe=""/usr/bin/dbus-daemon"" sauid=105 hostname=? addr=? terminal=?'
[   57.967647] audit: type=1107 audit(1543569390.557:18): pid=502 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor=""DENIED"" operation=""dbus_method_call""  bus=""system"" path=""/org/freedesktop/systemd1"" interface=""org.freedesktop.systemd1.Manager"" member=""LookupDynamicUserByName"" mask=""send"" name=""org.freedesktop.systemd1"" pid=3886 label=""/usr/sbin/kopano-server"" peer_pid=1 peer_label=""unconfined""
                exe=""/usr/bin/dbus-daemon"" sauid=105 hostname=? addr=? terminal=?'"
1806006,2018-12-03 10:10:42 UTC,"Hi Ben,"
1806012,2019-12-13 14:26:46 UTC,"as the merge request for this was rejected as not needed, i'm marking this bug as wontfix."
1806012,2019-05-15 16:27:03 UTC,Anyone with any opinions on whether the 'ondemand' service should be end-user configurable should please comment in the merge proposal.
1806012,2019-05-15 13:20:03 UTC,"Just opened a MP against systemd to make the 'ondemand' service configurable through
/etc/default/cpufrequtils file.
This change has two purposes :"
1806012,2019-05-01 19:15:59 UTC,"> > Reassigning to the kernel
>
> please don't. This is a bug in systemd
"
1806012,2019-05-01 17:45:11 UTC,It is normally always preferable to use the intel-pstate driver compared to pcc-cpufreq or acpi-cpufreq on modern Intel hardware.
1806012,2019-05-01 17:03:45 UTC,"> Reassigning to the kernel
"
1806012,2019-05-01 16:36:31 UTC,"Based on the analysis in the log, there does not appear to be a bug in systemd - which is behaving as intended, and defaulting to the best available cpufreq governor for low power consumption - but there may be a bug in the kernel resulting in the wrong scaling driver being used on the hardware in question.  Reassigning to the kernel."
1806012,2019-04-04 09:22:34 UTC,On the previously mentioned HP server today I was able to get closer to reproducing the situation by testing with bionic (4.15.0-47-generic) instead of xenial (4.4)
1806012,2019-04-02 08:46:51 UTC,"(as context to this information, apparently this particularly bad performance experienced with 'powersave' happens when the BIOS power control is set to the default, and goes away when in the BIOS you set power management to 'os control' - so there is some additional information needed to determine why this particular case offers bad performance, when as shown below, powersave/performance governors should not normally present more than a few percent performance difference)"
1806012,2019-04-03 13:56:49 UTC,TBH it was probably whatever the default mode was in the BIOS - we saw the same issue on Dell and HP servers.
1806012,2019-04-03 11:11:51 UTC,"@james-page
What was the the BIOS setting before setting it to ""OS control""?
Also what do you mean by ""we've just stuck with the default ondmand behaviour"" ?
You mean that you let systemd ondemand service do whatever it does by default or
that you use the ondemand governor ?"
1806012,2019-04-02 18:42:10 UTC,"I tried to get the ondemand script dropped in 2015 #1503773, Got Nacked."
1806012,2019-04-02 12:47:14 UTC,Confirmed that pcc-cpufreq *can* be used in preference to intel_pstate even on a CPU that supports intel_pstate if the firmware tables are setup to request such. One such server is an E5-2630 v3 HP DL360 G9 (shuckle).
1806012,2019-04-02 08:55:17 UTC,"Something I was not previously aware of that informs this a bit more, is that in some BIOS modes (apparently HP uses this extensively, unsure about Dell and others) you get a ""Collaborative Power Control"" mode, which sets the scaling_driver to pcc-cpufreq (as opposed to cpufreq) and is some weird hybrid of OS+BIOS defined behavior."
1806012,2019-04-02 08:38:45 UTC,See also LP: #1732696 and LP: #1579278.
1806012,2019-04-02 08:33:07 UTC,Just to add some more detail to this bug; for the impacted deployment we actually ended up re-configuring the power regulator settings via the BIOS to delegate to the OS for control; after a reboot we've just stuck with the default ondemand behaviour and performance has been consistent/better than before.
1806012,2019-04-03 21:32:39 UTC,@lathiat:
1806014,2019-11-20 17:56:39 UTC,https://github.com/canonical/cloud-init/commit/62bbc262c3c7f633eac1d09ec78c055eef05166a
1806014,2019-12-18 17:55:16 UTC,"This bug is believed to be fixed in cloud-init in version 19.4. If this is still a problem for you, please make a comment and set the state back to New"
1806014,2019-11-20 17:55:04 UTC,Merge Proposal migrated to github:
1806014,2019-07-18 21:48:44 UTC,Thanks for filing the bug.  We've another issue related here since the AUTOCONF controls ipv6 router advertisements.  the V1 network-config doesn't allow one to express whether you want to opt-in or out of router advertisements which may be desired with either static6 or dhcp6.
1806014,2019-10-14 13:31:27 UTC,There is a flag IPV6_FORCE_ACCEPT_RA[1] that can be set on an interface to accept_ra's while keeping autoconf (slaac) disabled. I wonder if that's what should be enabled for dhcp interfaces not IPV6_AUTOCONF which also set the autocnf sysctl.
1806014,2019-06-23 22:56:15 UTC,Also dealing with this bug. Working around it by manually editing /etc/sysconfig/network with bootcmd or manually setting the default route.
1806014,2019-10-14 14:47:38 UTC,"I did some testing, using an openstack instance with radvd running on a router in a flat provider network."
1806015,2018-11-30 10:23:42 UTC,Script used to tune bcache devices
1806015,2018-11-30 10:30:15 UTC,This change was made by a bot.
1806015,2018-11-30 15:20:06 UTC,Can you collect the following:
1806015,2018-12-12 01:01:30 UTC,"I confirmed that the underlying block devices (SAS, NVME) perform the same
on the 4.4 and 4.15 kernels.  Roughly 170 IOP/s direct to the SAS device
and 570 IOP/s direct to the bcache infront of the SAS device.  The block
scheduler has no effect, due to the use of O_DIRECT."
1806017,2020-03-02 10:09:40 UTC,Dropping Open Daylight support in Ussuri.
1806018,2020-03-02 10:10:06 UTC,Dropping OpenDaylight support in Ussuri.
1806023,2019-02-26 17:18:56 UTC,"Change abandoned by Chris Dent (<email address hidden>) on branch: master
Review: https://review.openstack.org/611707
Reason: no legs"
1806027,2019-08-26 13:47:30 UTC,This issue was fixed in the openstack/os-net-config ocata-eol release.
1806027,2019-05-14 14:37:48 UTC,This issue was fixed in the openstack/os-net-config 7.3.9 release.
1806027,2019-03-18 00:35:08 UTC,This issue was fixed in the openstack/os-net-config 8.4.4 release.
1806027,2019-03-14 10:39:02 UTC,This issue was fixed in the openstack/os-net-config 9.3.0 release.
1806027,2018-12-07 23:53:21 UTC,"Reviewed:  https://review.openstack.org/621990
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=0743c2c8036c441f4dbfb95750984831de1ec139
Submitter: Zuul
Branch:    stable/ocata"
1806027,2018-12-06 14:54:03 UTC,"Reviewed:  https://review.openstack.org/621989
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=2f6f6cb6ab190cf8c7bbe5c113d8279863cfff03
Submitter: Zuul
Branch:    stable/pike"
1806027,2018-12-06 14:53:55 UTC,"Reviewed:  https://review.openstack.org/621978
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=93f7f9dc4b1ecab3968bfd2fb5ae3d5b6ffcf400
Submitter: Zuul
Branch:    stable/queens"
1806027,2018-12-04 05:14:08 UTC,(The bug number on the master patch was incorrect. :( )
1806027,2018-12-04 05:01:33 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/621990"
1806027,2018-12-01 19:04:14 UTC,Proposed fix: https://review.openstack.org/621298
1806027,2018-12-06 14:54:11 UTC,"Reviewed:  https://review.openstack.org/621977
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=f7007b689e78154f26c2704da4804641e8beae50
Submitter: Zuul
Branch:    stable/rocky"
1806031,2019-06-11 03:35:18 UTC,"With bug 1803334 fixed, this issue can no longer be reproduced.
Marking this as fix released."
1806031,2019-06-10 11:28:20 UTC,"This issue for GKE kernel has been fixed in the ACT test suite:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=d0243344e19a5733ea607357a618860748a06386"
1806031,2019-06-03 19:07:43 UTC,linux-gke will fail this test version 4.15.0-1033.35
1806031,2018-12-04 14:09:43 UTC,"Same issue found with bionic/linux-aws-edge 4.18 on ADT:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-aws-edge/20181203_114936_4bb63@/log.gz"
1806031,2018-11-30 12:42:44 UTC,"This test can pass with all the other Azure kernel, just not this one."
1806031,2018-12-05 05:09:29 UTC,"Hi Kleber,
the cause for aws-edge is bug 1806799."
1806032,2019-02-27 23:40:41 UTC,"Reviewed:  https://review.openstack.org/637935
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=cb0d01db91a1f82b17117a7bb64e5dea3e6b3b28
Submitter: Zuul
Branch:    master"
1806032,2019-07-09 03:06:25 UTC,Directly deleting floatingip is a dangerous and unhumanized behavior when updating router:external to False. It should be a more reasonable behavior to prompt the user to delete these fips first before updating router:external to False.
1806032,2019-04-16 08:46:29 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/624751
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1806032,2019-04-16 08:46:13 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1806032,2019-02-19 16:57:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637935"
1806032,2019-07-16 14:51:11 UTC,FYI: In the abandoned patch I went for autodeleting for two reasons:
1806032,2018-12-12 16:38:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624751"
1806032,2018-12-03 13:57:06 UTC,Thank you for your bug report.
1806032,2018-12-03 15:52:25 UTC,"In neutron, it is allowed to update internal network to external. So we want to explore some related scenarios that supported by neutron. Then we find the unexpected support of updating an external network with FIPs to internal.
We don't have any usecases about this update. But it is a bug for this update feature obviously."
1806032,2019-02-04 16:46:12 UTC,"Reviewed:  https://review.openstack.org/631515
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=461be560769f4c591cd6a6513a873fcef92c0789
Submitter: Zuul
Branch:    master"
1806032,2018-12-06 10:20:32 UTC,"Change abandoned by Bence Romsics (<email address hidden>) on branch: master
Review: https://review.openstack.org/622170"
1806032,2018-12-04 10:00:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/622170"
1806040,2018-11-30 18:32:21 UTC,"Hi,"
1806042,2019-12-11 11:34:04 UTC,"Bug occures if you previously made
sudo apt install slack"
1806042,2020-08-09 22:34:43 UTC,slack-desktop 3.3.3
1806050,2019-01-22 08:04:11 UTC,The problem I'm seeing certainly isn't just juju's status lines being out of date. https://paste.ubuntu.com/p/zxvttJSyc6/ shows mongodb's rs.status() output for the system. I will try and dig further into exactly what happened to on this system.
1806050,2020-01-29 06:45:45 UTC,Merge proposal: https://code.launchpad.net/~dparv/charm-mongodb/+git/charm-mongodb/+merge/378219
1806050,2020-01-28 16:35:21 UTC,"Managed to reproduce the bug  (both bionic and xenial on juju 2.7.1) by downgrading from revision 51 to revision 50 and all nodes went to SECONDARY. Oddly enough it was fixed when upgrading back to revision 51, but this behavior was very inconsistent."
1806050,2019-01-23 09:05:40 UTC,I couldn't find a way to get the cluster to become health again.
1806050,2019-01-23 08:24:31 UTC,"Did MongoDB recover from being restarted after a few minutes, or was the cluster permanently broken?"
1806050,2019-01-22 13:52:07 UTC,In addition to the above timeline. The reported state of mongodb is as follows:
1806050,2019-01-22 12:37:39 UTC,I think I have a rough timeline for what happened on this system:
1806050,2018-12-11 12:40:24 UTC,"As best I can tell, Mongo is working fine and there is nothing to fix. All the charm is doing is (unnecessarily) restarting all the nodes."
1806050,2018-12-11 10:57:14 UTC,"Does the charm run any mongo command to fix this, or does mongo fix itself on its own ?"
1806050,2018-12-11 09:41:28 UTC,"Here is a fresh test run, which shows all units showing as SECONDARY immediately following the upgrade-charm, and then 5 minutes later showing that all is well: https://pastebin.ubuntu.com/p/VZqkv66Jx2/"
1806050,2018-12-10 07:10:42 UTC,"@mthaddon : nope, automatically-retry-hooks was and still is set to ""true""."
1806050,2018-12-06 15:12:25 UTC,"Junien, was automatically-retry-hooks in model-config set to false? Just trying to check if there's some difference in the models between what Stuart is seeing and what you're seeing."
1806050,2018-12-06 10:30:09 UTC,"(FAOD I was looking at rs.status() from mongo shell, not the juju status)"
1806050,2018-12-06 09:48:20 UTC,"The juju status will remain incorrect for up to five minutes after the MongoDB status changes, updated only when the update-status hook runs."
1806050,2018-12-06 09:07:57 UTC,"My experience is that all units were SECONDARY (or RECOVERING), and none would become PRIMARY even after an election"
1806050,2018-12-06 07:54:52 UTC,"The MongoDB cluster actually seems fine; if you wait until the next update-status hook (or manually connect and interrogate the cluster), you will find that one of the units is PRIMARY."
1806050,2018-12-04 17:09:43 UTC,"Fwiw, this has been used to manually undo the situation of no primary units (with a lot of restarts and kills because the commands sent to mongodb sometimes never finished):"
1806052,2019-05-22 12:36:27 UTC,"Reviewed:  https://review.opendev.org/632984
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2bcc178be15dce850162be76a870e443eee84c47
Submitter: Zuul
Branch:    master"
1806052,2019-04-10 16:49:15 UTC,"Reviewed:  https://review.openstack.org/644385
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=58ce96a7c296961e22a2ea9d4e71ec629bddd4fa
Submitter: Zuul
Branch:    master"
1806052,2019-04-05 03:41:21 UTC,"Reviewed:  https://review.openstack.org/633165
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6f26f4026b528e778fa653f51baff39f889181be
Submitter: Zuul
Branch:    master"
1806052,2019-03-27 14:43:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/648141"
1806052,2019-03-18 18:21:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/644385"
1806052,2019-03-07 08:36:44 UTC,"Reviewed:  https://review.openstack.org/633583
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=3f9ca0e441491ff49426dfe62ab6b93c082eb180
Submitter: Zuul
Branch:    master"
1806052,2019-01-28 19:03:28 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/633583"
1806052,2019-03-27 18:07:11 UTC,"Change abandoned by Rodolfo Alonso Hernandez (<email address hidden>) on branch: master
Review: https://review.openstack.org/648141
Reason: My bad: this exception exists in Neutron... and I didn't find it!"
1806052,2019-01-24 10:50:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632984"
1806052,2019-01-11 14:23:38 UTC,Some notes from the drivers meeting:
1806052,2019-01-11 14:20:19 UTC,This RFE has been approved by the drivers team. Next step is write a spec
1806052,2019-01-11 01:42:47 UTC,"Yes, it makes sense. Let's discuss it in the meeting"
1806052,2019-01-08 09:26:32 UTC,It is technically possible.
1806052,2018-12-21 01:45:01 UTC,"This entails re-binding all the ports in the network, since we need to re-wire the network in the data plane, right?"
1806052,2018-12-03 15:21:09 UTC,"Brian, I'm absolutely sure you know this, but for other's to see: This will be discussed on the neutron-drivers meeting:"
1806052,2019-01-25 09:07:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633165"
1806053,2019-05-16 17:53:50 UTC,"Hello Akihiro, or anyone else affected,"
1806053,2019-05-21 19:10:36 UTC,"Hello Akihiro, or anyone else affected,"
1806053,2019-05-22 01:27:00 UTC,"Hello Akihiro, or anyone else affected,"
1806053,2019-05-28 18:11:29 UTC,"Package built successfully in disco-proposed, cosmic-proposed, stein-proposed, and rocky-proposed. Tagging as verified."
1806053,2019-05-30 08:31:42 UTC,"The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1806053,2019-05-30 08:41:41 UTC,This bug was fixed in the package horizon - 3:14.0.2-0ubuntu4
1806053,2019-07-03 16:37:12 UTC,This bug was fixed in the package neutron-fwaas-dashboard - 1.5.0-0ubuntu3.1
1806053,2019-05-30 13:27:07 UTC,"This bug was fixed in the package horizon - 3:14.0.2-0ubuntu4~cloud0
---------------"
1806053,2019-07-03 16:36:29 UTC,This bug was fixed in the package neutron-fwaas-dashboard - 2.0.1-0ubuntu1.1
1806053,2019-05-16 11:43:38 UTC,"Hello Akihiro, or anyone else affected,"
1806053,2019-07-03 22:13:02 UTC,The verification of the Stable Release Update for neutron-fwaas-dashboard has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1806053,2019-07-03 22:13:06 UTC,"This bug was fixed in the package neutron-fwaas-dashboard - 2.0.1-0ubuntu1.1~cloud0
---------------"
1806053,2019-07-03 22:14:50 UTC,The verification of the Stable Release Update for neutron-fwaas-dashboard has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1806053,2019-07-03 22:14:52 UTC,"This bug was fixed in the package neutron-fwaas-dashboard - 1.5.0-0ubuntu3.1~cloud0
---------------"
1806053,2019-05-30 13:27:03 UTC,The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1806053,2019-05-15 14:25:02 UTC,"Hello Akihiro, or anyone else affected,"
1806053,2019-05-10 13:33:44 UTC,This bug was fixed in the package neutron-fwaas-dashboard - 2.0.1-0ubuntu2
1806053,2019-05-14 22:04:01 UTC,"Hello Akihiro, or anyone else affected,"
1806053,2018-11-30 15:36:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/621186"
1806053,2018-11-30 17:51:22 UTC,"Reviewed:  https://review.openstack.org/621186
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=de69edd0402146d76c65cec6cc7879c71259fbbf
Submitter: Zuul
Branch:    master"
1806053,2018-12-14 10:55:05 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/625209"
1806053,2018-12-15 09:37:39 UTC,"Reviewed:  https://review.openstack.org/625209
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=85fef71c0dfff3b7f816add638ad2d916a2ffe38
Submitter: Zuul
Branch:    stable/rocky"
1806053,2019-01-08 15:31:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/629236"
1806053,2019-01-10 14:08:13 UTC,"Reviewed:  https://review.openstack.org/629236
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=9ba7a0360756f0c8a0837cc0f9701711bb6e8888
Submitter: Zuul
Branch:    stable/queens"
1806053,2019-05-15 04:49:18 UTC,"I filed this bug to the upstream horizon, so I am not the right person to validate Ubuntu package status."
1806053,2019-01-30 08:34:37 UTC,"Reviewed:  https://review.openstack.org/633753
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=527553752a2a927ea0f505bd7f977e33fa7b6790
Submitter: Zuul
Branch:    stable/rocky"
1806053,2019-05-09 18:44:22 UTC,We'll need to cherry pick this for Ubuntu since it's not included in a stable release.
1806053,2019-05-09 20:00:29 UTC,It appears this is not needed for the Ubuntu Queens package as 0d163613265e036818fe567793a4fc88fe140d4a had not yet landed as of 13.0.1.
1806053,2019-05-09 22:23:44 UTC,This issue was fixed in the openstack/horizon 13.0.2 release.
1806053,2019-05-10 13:27:20 UTC,Fixed versions of neutron-fwaas-dashboard have been uploaded to eoan as well as disco/cosmic unapproved queues [1] where they are awaiting SRU team review.
1806053,2019-05-10 13:28:35 UTC,Also a fixed version of horizon has been uploaded to the cosmic unapproved queue [1] where it is awaiting SRU team review.
1806053,2019-05-10 18:42:30 UTC,This issue was fixed in the openstack/horizon 14.0.3 release.
1806053,2019-03-07 19:25:30 UTC,This issue was fixed in the openstack/horizon 15.0.0.0b2 development milestone.
1806054,2019-05-14 11:34:50 UTC,"As this is a missing feature in the upstream driver, I'm marking this bug task invalid for charm-cinder"
1806054,2018-12-02 01:46:50 UTC,"and here is log from /var/log/cinder/cinder-volume.log
ubuntu@juju-3884e1-1-lxd-0:/var/log/cinder$ tail -f cinder-volume.log
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/dist-packages/cinder/volume/manager.py"", line 3393, in delete_group
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server     vol_obj.save()
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py"", line 220, in __exit__
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server     self.force_reraise()
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py"", line 196, in force_reraise
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server     six.reraise(self.type_, self.value, self.tb)
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server   File ""/usr/lib/python2.7/dist-packages/cinder/volume/manager.py"", line 3358, in delete_group
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server     self.driver.delete_consistencygroup(context, cg,
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server AttributeError: 'RBDDriver' object has no attribute 'delete_consistencygroup'
2018-12-02 01:43:08.672 9139 ERROR oslo_messaging.rpc.server"
1806054,2019-03-05 15:13:46 UTC,The cinder RBD driver for ceph does not support consistency groups; I'm guessing this is why they are in an error state and cannot be deleted. Not particularly well handled.
1806057,2018-11-30 15:34:26 UTC,"We can do pre-flight checks on when the service is not running, but will not restart as it can kill existing workloads."
1806064,2018-11-30 15:35:00 UTC,It should be relatively easy to write a functional regression test similar to https://review.openstack.org/#/c/545123/5/nova/tests/functional/wsgi/test_servers.py but for this scenario.
1806064,2019-04-26 17:16:26 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1806064,2019-03-22 03:45:44 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1806064,2019-02-22 23:21:35 UTC,"Reviewed:  https://review.openstack.org/623937
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3eb9006b3e7e3e9fd296b6c15cceebb36b0495a5
Submitter: Zuul
Branch:    stable/pike"
1806064,2018-11-30 15:34:12 UTC,This is closer to this change https://review.openstack.org/#/c/544748/
1806064,2018-12-19 10:01:19 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1806064,2018-12-11 19:49:34 UTC,"Reviewed:  https://review.openstack.org/623934
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3dd42c2cd658fd3f73b11fbf5e81ccccd748b450
Submitter: Zuul
Branch:    stable/queens"
1806064,2018-12-11 15:45:55 UTC,"Reviewed:  https://review.openstack.org/623933
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3f37d0bba46fd7f39265863b227c5fd504fa7864
Submitter: Zuul
Branch:    stable/queens"
1806064,2018-12-11 00:56:33 UTC,"Reviewed:  https://review.openstack.org/623932
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3028d25705bbd54cdf0b7ba13859a809d401fc70
Submitter: Zuul
Branch:    stable/rocky"
1806064,2018-12-10 22:32:02 UTC,"Reviewed:  https://review.openstack.org/623931
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5b7e904126f68a8c9f5250620393dcdee54336d8
Submitter: Zuul
Branch:    stable/rocky"
1806064,2019-02-22 23:07:50 UTC,"Reviewed:  https://review.openstack.org/623935
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6b85dafd87a242b3d312f01eadc9e67376349ba4
Submitter: Zuul
Branch:    stable/pike"
1806064,2018-12-09 11:39:33 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/623935"
1806064,2018-12-09 11:50:35 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/623937"
1806064,2018-12-03 17:58:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621664"
1806064,2018-12-03 20:15:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/621692"
1806064,2018-12-08 01:11:14 UTC,"Reviewed:  https://review.openstack.org/621664
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5d514b33e28964b38aeb42a8dd5b93f3fc8ae239
Submitter: Zuul
Branch:    master"
1806064,2018-12-08 20:25:30 UTC,"Reviewed:  https://review.openstack.org/621692
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6d0386058b9628bbfcf64abdd707ad87ee19353c
Submitter: Zuul
Branch:    master"
1806064,2018-12-19 20:48:05 UTC,This issue was fixed in the openstack/nova 17.0.9 release.
1806064,2018-12-09 11:25:01 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623931"
1806064,2018-12-09 11:33:24 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623932"
1806064,2018-12-09 11:34:17 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/623933"
1806064,2018-12-09 11:36:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/623934"
1806070,2019-12-11 00:27:14 UTC,it seems we are running into something with network not being properly setup in a lxc snapshot. The issue/feature for snapd.seed seems to be that broken network configuration will result in snapd.seeded will wait indefinitely on network connectivity. I'll file a separate bug if need be with more details after triage.
1806070,2019-12-10 20:17:10 UTC,From within the container:
1806070,2019-12-10 20:15:01 UTC,"I'm wondering if we are seeing a regression here. On a focal host system, I am unable to launch disco or eoan containers as snapd.seeded service doesn't complete:"
1806070,2018-12-14 09:40:43 UTC,"That's great to know, thank you!"
1806070,2018-12-13 19:42:09 UTC,"@zyga, I'm happy to report the -proposed version fixed this bug and also allowed all my snap to be refreshed. Thanks for all your help, I really appreciate!"
1806070,2018-12-13 16:51:38 UTC,We have a suspicion this is a bug that was fixed and released via core snap but not released via SRU. Possible PRs https://github.com/snapcore/snapd/pull/5827 and https://github.com/snapcore/snapd/pull/6027
1806070,2020-05-14 12:43:47 UTC,"Chad, were you able to find the config that caused the effect? There is a similar issue open here:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225"
1806070,2018-12-13 16:13:51 UTC,"from the output of ""snap tasks 31"" it looks like that change requested snapd to restart but that never happened which is unexpected."
1806070,2018-12-13 15:22:23 UTC,"mmh, given that, what does  ""snap tasks 31"" shows?"
1806070,2018-12-13 15:12:21 UTC,@pedronis:
1806070,2018-12-13 15:05:24 UTC,I just realized now that this issue is preventing snap from refreshing all my snaps:
1806070,2018-12-13 17:14:32 UTC,"Dear reporter, can you please try to install the snapd package from the -proposed pocket. If this resolves the issue we will conclude it was the deadlock problem described above. We need ensure that the SRU is released so that everyone affected can update snapd using the classic package."
1806070,2018-12-13 15:05:25 UTC,"what does ""snap changes"" says on such a system?"
1806072,2020-03-07 10:59:39 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1806076,2019-01-11 17:56:28 UTC,This bug was fixed in the package apt - 1.8.0~alpha3
1806076,2018-11-30 17:36:24 UTC,"Unattended-upgrades does not print to stdout by default thus it can operate properly in the environments triggering the bug, but apt.systemd.daily executes u-u --help that may crash."
1806077,2018-11-30 17:13:43 UTC,run: curl -s -D- https://rdoproject.org/ | grep Strict
1806077,2018-11-30 17:19:37 UTC,"I also found the bug causing this, check http://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/nodepool-setup/templates/mirror_info.sh.j2"
1806077,2018-11-30 17:35:47 UTC,It seems that the default mirror to be used is mirror.regionone.rdo-cloud.rdoproject.org which means tha the entire configuration is invalid as at the moment I am writing this SSL is not configured for it.
1806077,2018-11-30 20:20:53 UTC,"Enabling SSL on the mirrors is not trivial right now.
We need to land the two following patches:
- https://review.openstack.org/#/c/529376
- https://review.openstack.org/#/c/528739"
1806077,2018-11-30 20:26:19 UTC,The review to toggle HSTS off for rdoproject.org is here: https://review.rdoproject.org/r/#/c/17629/
1806077,2018-11-30 23:04:38 UTC,"> run: curl -s -D- https://rdoproject.org/ | grep Strict
"
1806077,2018-11-30 16:40:04 UTC,I seen this SSL error when miss-matching HTTP(S) -- aka wrong port being used.
1806077,2020-05-27 06:10:36 UTC,"osas/ansible-role-ah-httpd gitlab merge request was not accepted, final workaround implemented as described in comment 7"
1806079,2018-11-30 16:38:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/621227"
1806079,2019-02-14 12:17:02 UTC,"Change abandoned by Corey Bryant (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/621227"
1806079,2019-03-21 14:20:51 UTC,The patch which reverts the problematic change in Nova has been released in our packages for version 2:16.1.6-0ubuntu1~cloud0 [0]. Let's mark this bug has Fix Released [1].
1806080,2018-12-04 13:37:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806080,2018-12-07 17:11:14 UTC,It works with version 71.0.3578.80  (538). It is currently available in the candidate channel.
1806080,2018-12-12 21:07:39 UTC,Version 71.0.3578.80 is now in the stable channel.
1806080,2019-08-07 15:34:18 UTC,"@Tejeev, can you confirm whether the latest version of the chromium snap has fixed the crashes?"
1806100,2019-09-03 16:22:38 UTC,"Adding more heat to this. Our libraries receive funding based on the values in one of our stat cats. They are not used to touching the field, so we're concerned about the affect on them when we are using the web client more widely."
1806100,2018-12-11 21:35:59 UTC,Adding one more screenshot of the xul client where the default patron statistical category is set when the registration screen is loaded.
1806100,2018-11-30 17:37:08 UTC,Here's a screenshot of the patron registration page in the web client showing the unpopulated statistical category entry.
1806110,2019-08-20 01:43:12 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1806114,2018-12-03 19:32:41 UTC,Hello! Thank you for your kindly and detailed report.
1806114,2018-12-03 22:07:06 UTC,I ran plenty of QEMU/SeaBIOS configurations and these are the results:
1806114,2018-12-03 22:24:03 UTC,"Alright, I managed to compile 2.5.0, 2.5.1 and 2.6.0 by simply making memfd_create() non-static."
1806114,2018-12-03 23:37:52 UTC,"The memfd_create() compilation failure is a bug in older QEMU versions that was only revealed by a newer glibc version (ie old QEMU built OK with older glibc but fails with newer glibc). It's fixed in git in commit 75e5b70e6b5dcc4f221, so backporting that to the older versions you're trying to build is probably the correct fix there, though it sounds like you've sufficiently worked around it anyway."
1806114,2018-12-04 00:01:57 UTC,"I see. That wasn't much of a problem, but thank you for the information. I'll try to keep it in mind when building QEMU in future."
1806121,2019-01-03 14:39:02 UTC,"Discovered that this bug has been fixed in the meantime, but only at master branch. Can we get the fix into stable/rocky as well?"
1806124,2019-08-27 20:40:08 UTC,"@Wayne
@Jeff"
1806124,2019-08-04 22:26:33 UTC,"Fixed in revision 95bfb733eef9afae4c1519964c6bd2aa88e41709
https://git.launchpad.net/kicad/patch/?id=95bfb733eef9afae4c1519964c6bd2aa88e41709"
1806124,2019-08-04 16:31:42 UTC,"I've put in some more defensive code, as well as fixed a bug where <enter> would OK the dialog even if there was a validation error."
1806124,2019-02-14 20:50:11 UTC,"Here is a video. After typing ""5.2"" I'm frantically pressing the Enter buttons but nothing happens. Clicking the OK button works."
1806124,2019-02-14 18:24:35 UTC,No luck reproducing this using your new steps.
1806124,2019-02-14 17:28:27 UTC,"OK, I may have figured it out. This is consistently working (actually, not working) for me:
1. Hover over some text.
2. Press the 'e' to open the Footprint Text Properties dialog.
3. Double-click the value in the Position Y text box to highlight it.
4. Type in a new value for Position Y.
5. Press Enter key."
1806124,2019-02-08 18:07:49 UTC,I'm not able to reproduce this in the following version. Perhaps this was fixed earlier or I was confused.
1806124,2019-02-08 00:32:08 UTC,And now I can't find an issue either. The Enter key always asserts the OK button and I can see the OK button highlighted when the dialog is invoked.
1806124,2019-02-08 19:21:26 UTC,"There were definitely some of these that got fixed, so I suspect that's the case."
1806124,2019-02-07 17:30:51 UTC,"Now running the following version and I still see this. I haven't found exact STR that works, because every time I open the dialog the Enter key never triggers the ""OK"" button. I did see it working earlier, but I can't find it working at all now."
1806124,2018-11-30 21:40:26 UTC,"@Devs, I can't reproduce on OSX.  Is this MSW-specific?"
1806124,2018-11-30 22:22:56 UTC,I can reproduce this in Linux Kubuntu with the board editor by selecting e.g. footprint ref text properties.
1806124,2018-11-30 23:44:53 UTC,"In Linux, Shift-Enter works for me to accept the text properties dialog. I think it should probably be Shift-Enter (maybe Ctrl-Enter on other platforms) *only* when in the text box, else Enter as normal?"
1806124,2018-12-01 11:56:46 UTC,"While they use the same base dialog, the control for entering text is different.  We implement the Shift-Enter CharHook just for the multi-line textbox as wxWidgets should handle it for everything else (and does at least on OSX)."
1806124,2019-02-07 18:12:39 UTC,"No matter what footprint text I edit, the enter key is the OK button with:"
1806124,2018-12-01 14:35:33 UTC,Seems to work here.
1806124,2018-12-04 00:15:33 UTC,Works for me with the newest nightly. Thanks!
1806124,2018-12-04 16:10:46 UTC,I spoke too soon. Sometimes it works and sometimes it doesn't. I haven't yet figured out a sequence of events  to reproduce either condition.
1806124,2018-12-01 11:58:07 UTC,"Fixed in revision 45ee95f5e25ad82585da1b965184400e78f413a3
https://git.launchpad.net/kicad/patch/?id=45ee95f5e25ad82585da1b965184400e78f413a3"
1806125,2020-02-09 07:45:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806129,2019-03-04 21:04:58 UTC,"Noting that this was fixed for 3.2 in Patron Holds, Patron Items Out, and Item Status List grids in bug 1746566"
1806129,2019-04-19 16:36:51 UTC,"I'm marking this as Fix Released, since it's in 3.2."
1806129,2019-04-22 14:52:14 UTC,"Michele, I don't think this bug is finished yet. It sounds like some of the screens mentioned in the bug report are fixed in 3.2 (via bug 1746566 as Andrea mentioned), but I think these three screens haven't been done yet:"
1806133,2019-01-22 17:25:34 UTC,"After discussion on this bug, we've decided the best approach for cloud-init in the short term is to extend the OVF datasource to allow for setting datasource configuration options to allow merging from both VMWare IMC data and OVF user-data."
1806134,2018-11-30 22:32:41 UTC,Fixed in x.4321.
1806135,2018-12-14 20:45:28 UTC,Great idea.
1806135,2019-04-16 14:28:39 UTC,"+1 point:
As I commented in https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1803476 (comment 21), AppArmor may be disabled for good reason - e.g. to allow various docker control commands to work."
1806137,2018-12-01 04:39:26 UTC,"OK, research has been done.  The problem is that hooks like GeneratesSchema.generate_schema_create_all are called before we apply the ReplaceEngineFacadeFixture to patch the local enginefacade into the one given to us by the application.   Since it's common that tests want to use their normal enginefacade-enabled application code to set up test data, this causes things to not work.  As a workaround, a fixture can do this:"
1806137,2018-12-04 17:07:14 UTC,So do we need to add a test fixture for this?
1806137,2018-12-04 19:20:09 UTC,"We will, yes.  I was planning to work on it at some point.  for the review where I had the problem see https://review.openstack.org/#/c/621304/."
1806139,2018-12-01 15:58:35 UTC,"Hi @alpha23,"
1806139,2019-08-20 01:06:46 UTC,I am going to close this bug due to no activity within 90 days.
1806143,2019-05-09 21:24:31 UTC,"See duplicate for other wishlist enhancements:
* Use separator between imperial/metric groups
* Remove the word ""Grid:"" from each entry"
1806143,2018-11-30 23:02:27 UTC,"On second thought, why not let the users define their own values there, even unrestricted custom grids?"
1806143,2018-12-01 11:44:01 UTC,"I think we have a wishlist item for custom grids, but I can't find it."
1806143,2019-01-28 09:46:00 UTC,"I can't find any similar wish, either. I did a search with only ""grid""."
1806155,2020-10-26 00:59:05 UTC,Still a problem in Groovy (20.10)
1806156,2020-09-22 12:16:49 UTC,Wondering if that has been fixed with https://review.opendev.org/#/c/748482/
1806156,2019-04-17 17:31:25 UTC,We facing same problem
1806156,2019-04-17 17:38:42 UTC,We have the same problem. Please provide some solution
1806156,2019-04-24 03:21:42 UTC,"I am also getting hit by this bug, using OSA 18.1.4 Rocky.
With my deployment, I am simply re-running playbooks on a fully working system."
1806156,2019-04-25 12:17:31 UTC,"We're also hit by this bug, using OSA 18.1.5 Rocky. While running 'openstack-ansible setup-openstack.yml' during major upgrade from Queens to Rocky."
1806156,2019-06-28 19:58:38 UTC,We've hit the same problem with 18.1.6 on Ubuntu 18.04.2 on a fresh install.
1806156,2019-07-11 10:36:45 UTC,"Whoever faces the same problem, please have a look at https://bugs.launchpad.net/cinder/+bug/1821207"
1806156,2019-07-11 15:08:05 UTC,"No, the problem exist even when all cinder service states are running (see my previous paste from 2018-12-12)"
1806156,2019-07-11 15:59:25 UTC,"If the migration fails when the cinder-volume services are online, it's failing for some other reason, so not (directly) related to this bug."
1806156,2019-07-11 16:34:19 UTC,"So should I submit another one bug report? I'm almost 100% sure, that all people who said that they face with the bug in terms of the OSA, have running cinder-volumes like I do. And this looks like smth that might be reproduced..."
1806156,2019-07-12 00:11:18 UTC,"Looking at your paste and log from 2018-12-12, the services were last updated at 19:57 but the failure occurred at 20:06, so it's not clear if the services we're actually operational at the time of the failure."
1806156,2020-09-22 15:49:40 UTC,I doubt it; that change doesn't look related.
1806156,2019-07-12 05:52:30 UTC,"Ok, placed fresh paste, with more clear timings: http://paste.openstack.org/show/754329/"
1806156,2019-07-25 14:09:08 UTC,"Today we did another Queens -> Rocky upgrade, and we hit problem again.
This time, no ERROR state volumes in the db."
1806156,2019-07-25 14:26:35 UTC,"when we hit this problem, I also observed RPC message timeout from the logfile."
1806156,2019-07-25 16:52:29 UTC,"I'm not sure about all of the scenarios where the symptom is being observed, but the bottom line here is that migrations are supposed to be capable of completing when services are not running, and there will never me an RPC response if services are not running, so the way that the migration is currently implemented is fundamentally flawed."
1806156,2019-07-26 07:30:25 UTC,TBH it would be great to prioritize this bug somehow since really lot's of people facing it and there's even no good workaround.
1806156,2019-08-01 10:57:11 UTC,"Ran into this issue as well on Stein 19.0.1dev14, Bionic 18.04, while performing a minor version upgrade."
1806156,2019-08-01 14:18:20 UTC,"Also ran into this issue when upgrading Rocky to Stein using kolla-ansible, all cinder-volume containers were up and running.
I then checked the database via"
1806156,2019-08-07 12:46:09 UTC,We upgraded openstack-ansible from rocky to stain and cinder-manage also fails (see below to fix/workaround).
1806156,2019-10-02 07:27:39 UTC,"Yesterday we ran a FRESH install of openstack-ansible 18.1.8 (Rocky), but it unfortunately failed a t the same place by cinder online_data_migration."
1806156,2019-10-02 10:55:43 UTC,I agree to what iain MacDonnell (imacdonn) explained in the ticket description.
1806156,2019-04-16 07:14:32 UTC,"I also catch this problem. When we configured backend_host (not host) for cinder-volume HA, then we execute the cli ""cinder-manage db online_data_migrations"", and we can get the following error: ""Error attempting to run shared_targets_online_data_migration: MessagingTimeout: Timed out waiting for a reply to message ID""."
1806156,2019-07-20 00:07:08 UTC,"Just came here to say I hit this as well in kolla-ansible during an upgrade from Queens to Rocky. All services were online and seemed to be working properly, but I hit the same RPC messaging timeout. I've commented out the migration in the playbook just to get by it, but I""m sure it'll rear its ugly head again come Stein upgrade time. I'm happy to share any logs if needed, but they mainly look like the above."
1806156,2019-04-13 14:45:17 UTC,"Gnn... formatting... here is a link:
http://paste.openstack.org/show/749273/"
1806156,2019-10-07 00:44:33 UTC,"I ran into a similar situation as comment 48:
https://bugs.launchpad.net/cinder/+bug/1806156/comments/48"
1806156,2019-04-13 14:13:00 UTC,"Sorry, my code should have said continue, i think, too many programming languages ;)"
1806156,2018-12-05 17:57:39 UTC,"My upgrade scenario (using my bespoke ansible-based deployment automation) involves shutting down all services, installing new code, then invoking the upgrade procedures for each component - e.g. apply any needed config changes, then ""db sync"", then start the service, then do online_data_migrations. cinder-volume separate from the core cinder services (api, scheduler), because I run multiple instances of cinder-volume for different storage backends (I think of it almost more like an agent than a service), on separate control VMs. I do not update and start up the cinder-volume services until later, so they are not running when I would normally do the online_data_migrations for cinder, so the migration fails. I'm working around this for now by just not doing the online_data_migrations during cinder upgrade - fortunately it seems that there have not been any added since Queens, so I don't actually need any ... for now."
1806156,2018-12-12 20:07:57 UTC,Forgot to mention trace from logfile:
1806156,2018-12-12 20:29:23 UTC,"The migrations requires an RPC response from all of the hosts that have cinder-volume services. If times out waiting for that response for any reason, the migration fails. The cinder-volume service being down is certainly one cause. There may be others. The point of this bug is that the migration should not assume that it can get a response from the service."
1806156,2019-01-21 23:38:15 UTC,"Also hitting this problem, using OpenStack-Ansible to upgrade from Queens to Rocky. Has anyone identified a workaround yet?"
1806156,2019-01-22 17:14:25 UTC,"I don't know how OpenStack-Ansible sequences the upgrade, so I can't confirm if it's susceptible to this bug, or how much you can manipulate it, but; it appears there were no new online migrations added in Rocky, so (if you can find a way) you can probably skip the step entirely for a Queens->Rocky upgrade. You could run it manually afterwards if you want to be sure (once all of the services are back up)."
1806156,2019-01-29 01:01:23 UTC,"Hey guys,"
1806156,2019-01-29 02:04:52 UTC,Did you check cinder-manage.log ?
1806156,2019-01-29 05:40:19 UTC,Looks like that after this systemd thing the logs where moved to God knows where...
1806156,2019-01-29 05:46:23 UTC,"Believe you or not, I just executed that command and it worked!  LOL"
1806156,2019-01-29 06:24:45 UTC,"Can't really help with the logging issue, although maybe you could try this and see if you can spot anything; journalctl --since '2019-01-28 23:12'"
1806156,2019-01-31 18:00:42 UTC,"I just reinstalled the whole thing from scratch, after going to Ubuntu MaaS and ""Release -> Deploy"" and then, running `openstack-ansible setup-everything.yml` again."
1806156,2019-02-10 01:39:31 UTC,I also hit the same error while running OSA 18.1.3 on freshly built bare metals running Ubuntu 18.04 LTS.
1806156,2018-12-12 19:59:21 UTC,I'm catching the same problem even when all cinder-volumes are running: http://paste.openstack.org/show/737164/
1806156,2019-02-10 19:40:38 UTC,"Actually, we have all cinder services running, but still hitting this, just FYI"
1806156,2019-02-10 19:38:01 UTC,"We also just hit this, and I'm wondering how this would work when cinder-manage service list returns a rbd:<poolname>@<config-definition> - what host should that contact?
Or is it all going trough rabbitmq and those hosts will just accept it?"
1806156,2019-03-27 21:29:59 UTC,It was accidental.
1806156,2019-03-27 21:07:35 UTC,"I've now read through this entire report and it's still unclear to me why you suspect this indicates an exploitable security vulnerability in Cinder. I'm switching the bug type back to a normal ""Public"" state, but if you do have some reason for the OpenStack VMT to triage it as report of a suspected security vulnerability please provide a clear explanation in a comment so we can better classify this. Thanks!"
1806156,2019-03-25 16:54:17 UTC,"Did anyone identify a workaround for this? I verified all Cinder services are up, rabbitMQ is working fine, I'm wondering if the transformation is maybe trying to do something that I can skip or don't care about? I see the comment about line 111 (I assume this is from /usr/lib/python2.7/site-packages/cinder/cmd/manage.py) from Iain but it didn't work for me."
1806156,2019-02-14 18:17:46 UTC,"Yeah, well, prior to that fix, the migration could have been failing silently, and you would have been unaware."
1806156,2019-04-13 14:44:38 UTC,"Someone asked for the error log, so here it is:"
1806156,2019-02-14 17:53:32 UTC,"@Cody: Probably you've got need_online_data_migrations cached in your ansible_facts, so you're not facing the problem anymore."
1806156,2019-02-14 17:50:33 UTC,I still catch this problem even with containerized cinder-volume on brand-new setup of OSA 18.1.3.
1806156,2019-02-12 18:16:36 UTC,The error is gone after I set the cinder service to be containerized:
1806156,2019-02-14 18:07:44 UTC,"Btw, I've started to facing this issue since the following patch https://review.openstack.org/#/c/614617/ - I didn't test if it's rollback helps, as I suggest, that before this patch migrations could simply not work at all (or partially)."
1806156,2019-02-11 18:35:23 UTC,"If possible, please post what you see in cinder-manage.log when this happens...."
1806156,2019-02-10 20:25:52 UTC,"Looking at it a bit more yields the following:
1. It can't handle rbd:
2. The volumes in ceph has shared_targets set
3. it's ""capabilities = rpcapi.get_capabilities("" on line 111 that fails to get information somehow..."
1806157,2018-12-03 13:34:12 UTC,Confirmed. I've compiled for Armv7E-M where smullbb is used but otherwise the same happens. The middle end seemed to do something to do something funky already since it converted operand to unsigned short and then back to short int for the result. However changing a and b to unsigned short does not change the assembly (it does improve gimple).
1806163,2019-11-21 12:23:00 UTC,any update on this bug ?
1806166,2020-07-16 16:29:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal:"
1806172,2018-12-16 02:42:06 UTC,"@Jeff Ahh I see but I had no access to change the Importance column therefore I was not able to change to ""Wishlist"" which was the next best thing. Is there any way to go about this when I don't have access to edit the Importance column?"
1806172,2018-12-12 21:45:08 UTC,"@Jessica, the database stores feature request items in the same records as bugs, so Invalid would mean it's an invalid feature request."
1806172,2018-12-16 11:40:49 UTC,"@Jessica, I think if you ask to join the bug squad you'll get access to Importance."
1806172,2018-12-02 13:09:27 UTC,I don't think so.  @shoomi?
1806172,2018-12-12 21:28:41 UTC,@jeyjey I did change it on purpose. I thought Invalid was appropriate since it is not a bug but a request? Was I wrong? still new at this and would like to learn.
1806172,2018-12-02 23:49:11 UTC,"Having the 1 page printed to representing all the difference Reference on each hierarchy page is a changeling. I'm rather to have hierarchy block show the page number of the schematic so that when I review the printed version is clear which one I'm looking at at least. And if we can control page number too, that would be nice too."
1806172,2018-12-02 11:41:52 UTC,Was the status changed on purpose?
1806177,2018-12-01 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1806177,2019-05-28 05:53:35 UTC,Does the issue still happen?
1806178,2019-07-30 13:19:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806178,2019-07-30 13:25:11 UTC,"As a workaround, you can preload libXtst as follows:"
1806179,2019-05-28 20:33:51 UTC,I just hit this with revision 37 of the elasticsearch charm.
1806179,2020-03-11 04:21:09 UTC,"On a non-lxd machine, the vm.max_map_count is 262144, but on a lxd container we can't set that within the container."
1806179,2020-03-11 07:04:53 UTC,It's probably worth evaluating if the elasticsearch charm can set this via the lxd-profile.yaml in the charm (which sets it in the container's profile) as a way to handle it with containers
1806179,2021-01-24 09:19:57 UTC,"Good tip if you run in vagrant/VM, always set max_map_count on VM because it may be set lower there. Lxd will inherit the same setting."
1806179,2020-03-11 04:18:30 UTC,Confirmed with the current 20.02 release charm.
1806182,2020-07-26 03:09:26 UTC,"> This renders the configuration script useless
"
1806192,2018-12-01 16:21:36 UTC,Updated problem description.
1806192,2018-12-01 16:28:19 UTC,There is a way to do things without `setup.py` https://github.com/takluyver/flit
1806193,2018-12-02 04:57:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806196,2018-12-18 18:15:13 UTC,"I think, this bug also can be triggered in qcow2. Unfortunately it is not so easy for me to find roots of the bug."
1806196,2018-12-18 12:03:37 UTC,"Thanks for reporting this.  QED is not widely used and its features have been incorporated into qcow2, QEMU's native image format.  Since there is no development effort behind QED it is unlikely that this bug will be addressed.  Patches are always welcome though!"
1806203,2018-12-08 00:37:06 UTC,You will be glad to hear that this is already the case in the development version:
1806205,2018-12-03 01:28:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806211,2019-01-29 21:12:41 UTC,Git patch improvement.
1806212,2018-12-01 22:22:30 UTC,Fixed in x.4323.
1806215,2019-02-16 16:30:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806217,2019-10-29 19:24:03 UTC,"Fixed in revision 7b2d6ab40e9ef4c6a05ec070e178eec3bc590a37
https://git.launchpad.net/kicad/patch/?id=7b2d6ab40e9ef4c6a05ec070e178eec3bc590a37"
1806218,2018-12-03 01:33:49 UTC,Hello. Thank you for submitting the report. I am marking this as a duplicate as other users have reported the same problem.
1806218,2018-12-03 12:39:13 UTC,"it's not a duplicate, the error is different"
1806222,2018-12-03 15:12:06 UTC,Here's the error from DpkgTerminalLog.txt:
1806224,2019-02-16 00:04:15 UTC,This seems to be a timing issue.
1806232,2020-01-13 15:40:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806232,2018-12-03 03:30:06 UTC,This change was made by a bot.
1806233,2018-12-02 10:00:06 UTC,This change was made by a bot.
1806239,2018-12-13 15:14:24 UTC,I downgraded glanceclient to version 2.9.1 and re-did the snapshot and it still worked.
1806239,2020-07-19 04:17:19 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1806239,2020-05-19 08:52:49 UTC,@Dilip: Could you reproduce the same problem with python-glanceclient >= 2.12.0 [1]?
1806239,2018-12-13 15:21:02 UTC,"Granted, I'm using a devstack created today:"
1806239,2018-12-13 15:11:00 UTC,Using devstack the os_hidden property is set in the default image:
1806239,2018-12-13 12:48:27 UTC,"Isn't os_hidden=false in all images by default since Rocky? I can't understand why tempest wouldn't hit this in it's snapshot testing, unless it's something with glanceclient in the mix - nova uses glanceclient but tempest doesn't. Tempest has its own REST client for glance. I'll see if I can reproduce in devstack."
1806239,2018-12-06 15:40:31 UTC,full trace file https://etherpad.openstack.org/p/e20ERvBEkw
1806239,2018-12-06 15:38:50 UTC,"Hi all,"
1806239,2018-12-06 15:07:48 UTC,There must be some other way this gets enabled because otherwise we should have seen this fail in Tempest when the os_hidden property was added to glance images - does the server have to expose the field or something? Does os_hidden need to be true for this to fail?
1806239,2018-12-06 15:06:27 UTC,The problem is likely in this code:
1806239,2018-12-06 15:04:15 UTC,"One workaround might be to add ""os_hidden"" to the non_inheritable_image_properties configuration option to filter that property out when creating the snapshot:"
1806242,2018-12-03 09:28:31 UTC,apport information
1806242,2019-07-30 02:06:50 UTC,"As far as I know, for the moment at least, this bug affects Xorg but might not affect Wayland Gnome sessions. Can anyone confirm that?"
1806242,2019-07-30 02:09:43 UTC,"From memory, only Xorg's modesetting_drv uses atomic modesetting, but I don't think mutter/Gnome's Wayland backend does."
1806242,2019-08-10 15:52:23 UTC,"Could you let me know when would this be fixed? I understand it needs to be prioritized and scheduled, developed, released, etc. My only laptop is using this distro and unfortunately I can't stand this screen flickering. I can try another distro and come back when this is resolved. Would this bug only affect Ubuntu?"
1806242,2019-08-12 02:18:07 UTC,It's difficult because it seems only certain laptop models will be affected very often. And while no developers are affected by the bug then it's unlikely to get fixed. Because nobody with the ability to fix the bug has the hardware to reproduce the bug.
1806242,2019-12-09 15:17:22 UTC,have same error:
1806242,2018-12-03 09:28:29 UTC,apport information
1806242,2019-12-09 15:32:03 UTC,sorry correction ThinkPad T590 is the faulty system (I have another T580 that I use too).
1806242,2019-12-09 15:33:29 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  gregory.starck   4026 F.... pulseaudio
 /dev/snd/controlC1:  gregory.starck   4026 F.... pulseaudio
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2279]
InstallationDate: Installed on 2019-07-30 (131 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS ""Bionic Beaver"" - Release amd64 (20180725)
MachineType: LENOVO 20N4CTO1WW
Package: xorg-server (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=b08d0197-709f-4706-bc47-d9678c90d2b3 ro quiet splash pci=nomsi vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-37-generic N/A
 linux-backports-modules-5.0.0-37-generic  N/A
 linux-firmware                            1.173.12
Tags:  bionic ubuntu
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm docker sudo
_MarkForUpload: True
dmi.bios.date: 11/26/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2IET80W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20N4CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N4CTO1WW:pvrThinkPadT590:rvnLENOVO:rn20N4CTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T590
dmi.product.name: 20N4CTO1WW
dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590
dmi.product.version: ThinkPad T590
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A"
1806242,2019-12-09 15:33:34 UTC,apport information
1806242,2019-08-27 08:48:43 UTC,It appears Intel knows Xorg is broken and is disabling atomic mode:
1806242,2018-12-03 09:28:26 UTC,apport information
1806242,2018-12-03 09:28:02 UTC,apport information
1806242,2018-12-03 09:28:23 UTC,apport information
1806242,2018-12-03 09:28:22 UTC,apport information
1806242,2018-12-03 09:28:20 UTC,apport information
1806242,2018-12-03 09:28:16 UTC,apport information
1806242,2018-12-03 09:28:15 UTC,apport information
1806242,2018-12-03 09:28:14 UTC,apport information
1806242,2018-12-03 09:28:13 UTC,apport information
1806242,2018-12-03 09:28:12 UTC,apport information
1806242,2018-12-03 09:28:11 UTC,apport information
1806242,2018-12-03 09:28:07 UTC,apport information
1806242,2018-12-03 03:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1806242,2019-12-09 15:33:35 UTC,apport information
1806242,2019-12-09 15:33:37 UTC,apport information
1806242,2018-12-03 09:28:25 UTC,apport information
1806242,2019-12-09 15:33:40 UTC,apport information
1806242,2020-04-03 20:09:23 UTC,i have the same issue on ubuntu 19.10
1806242,2019-12-09 15:34:10 UTC,apport information
1806242,2019-12-09 15:34:08 UTC,apport information
1806242,2019-12-09 15:34:06 UTC,apport information
1806242,2019-12-09 15:34:05 UTC,apport information
1806242,2019-12-09 15:34:03 UTC,apport information
1806242,2019-12-09 15:34:01 UTC,apport information
1806242,2019-12-09 15:33:59 UTC,apport information
1806242,2019-12-09 15:33:57 UTC,apport information
1806242,2019-12-09 15:33:38 UTC,apport information
1806242,2019-12-09 15:33:54 UTC,apport information
1806242,2019-12-09 15:33:42 UTC,apport information
1806242,2019-12-09 15:33:43 UTC,apport information
1806242,2019-12-09 15:33:45 UTC,apport information
1806242,2019-12-09 15:33:56 UTC,apport information
1806242,2019-12-09 15:33:47 UTC,apport information
1806242,2019-12-09 15:33:49 UTC,apport information
1806242,2019-12-09 15:33:51 UTC,apport information
1806242,2019-12-09 15:33:46 UTC,apport information
1806245,2018-12-02 13:30:05 UTC,This change was made by a bot.
1806248,2019-06-04 10:02:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806249,2019-06-21 02:29:37 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.opendev.org/560252"
1806251,2018-12-03 11:55:29 UTC,"- which OS are you using?
- have you tried the menu option: View->Display Mode->Outline, which will make even thin lines visible?
- do you mean that a 0.01mm line will cut properly?"
1806251,2018-12-03 12:03:08 UTC,"- okay, I gather that you are on Windows, in which case you could also try the menu option:
Extensions->Export->Win32 Vector Print
- see also https://bugs.launchpad.net/inkscape/+bug/630639"
1806256,2019-01-20 21:18:10 UTC,"This issue is resolved in garcon 0.6.2, available in 19.04
https://launchpad.net/ubuntu/+source/garcon/0.6.2-1"
1806256,2018-12-10 19:31:44 UTC,This problem is very annoying.
1806256,2018-12-09 12:50:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806256,2018-10-19 20:29:55 UTC,On the same system I also have this issue: https://bugzilla.xfce.org/show_bug.cgi?id=14774.
1806256,2017-08-25 21:12:10 UTC,"How do you suppose the scalling of the images has anything to do with the new return type
from libxfconf? The change in still hasn't permeated into every part of the software.
The settings-editor for example can't display arrays because it also assumes the old type."
1806256,2018-11-07 18:07:08 UTC,"Here is some information which may help to reproduce my problem. I have not installed Firefox via Synaptic but instead downloaded it via the mozilla page. I only had to extract the compressed file and then launch the executable. So my Firefox is installed under /home/myname/bin/firefox-release/. Then I created a .desktop file under /home/myname/.local/share/applications/ and set the icon name to ""firefox quantum"". This icon can be found under /home/myname/.local/share/icons/hicolor/128x128/apps/ and has a width and height of 128 pixels."
1806256,2018-10-19 20:09:57 UTC,I upgraded my system from Xubuntu 18.04 64 bit x86 to version 18.10. Since version 18.10 I have this issue :(
1806256,2017-08-24 17:01:07 UTC,"(In reply to Eric Koegel from comment #3)

> Pushed your patch, thanks!
"
1806256,2017-08-21 15:41:14 UTC,"Pushed your patch, thanks!"
1806256,2017-08-21 15:40:11 UTC,Stefan Berzl referenced this bugreport in commit 4387496fe332a50945e7db76bc2196b419656fe3
1806256,2017-08-15 21:01:45 UTC,"Created attachment 7269
The patch for scaling the icons"
1806256,2017-08-15 20:50:13 UTC,"Created attachment 7268
A screenshot of the issue"
1806256,2017-08-25 16:59:28 UTC,"(In reply to Olivier Duchateau from comment #4)

> (In reply to Eric Koegel from comment #3)
> > Pushed your patch, thanks!
>
> This patch breaks quicklaunch default applications icons (buttons have
> disappeared).
"
1806257,2019-08-22 09:45:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806257,2019-08-21 16:49:53 UTC,"gnome-shell's failure to bind can also be caused by namespace.conf settings, currently gdm/gnome-shell etc do not take this into account, breaking gdm which worked fine without wayland.
https://manpages.ubuntu.com/manpages/trusty/man5/namespace.conf.5.html"
1806257,2018-12-02 17:45:54 UTC,"For some reason (I cannot remember) my root filesystem node ""/"" had the owner set to my user. I guess this used to work for some time. And some change in mutter or related packages made this break."
1806257,2018-12-02 16:06:44 UTC,apport information
1806257,2018-12-02 16:06:43 UTC,apport information
1806257,2018-12-02 16:06:41 UTC,apport information
1806257,2018-12-02 16:09:54 UTC,The gigabytes of log messages consist only of messages like this:
1806258,2018-12-04 11:36:12 UTC,"The screenshot shows version 1.9.15rc1, but the package should provide 1.16.14 instead."
1806258,2018-12-04 11:57:58 UTC,"This an (unrelated) error in the package versioning.
If you download http://fr.archive.ubuntu.com/ubuntu/pool/universe/u/ublock-origin/webext-ublock-origin_1.16.14+dfsg-1_all.deb and extract it, you can see that /usr/share/webext/ublock-origin/manifest.json contains this:
""version"": ""1.9.15.101"""
1806258,2018-12-04 13:06:23 UTC,I can confirm this issue. I have tested with 1.17.0+dfsg-2 from 19.04 also (the correct version is shown in this case).
1806258,2018-12-04 15:21:34 UTC,Related report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827517
1806258,2018-12-22 18:24:37 UTC,"Issue is fixed in ublock-origin (1.17.0+dfsg-3):
  * Replace symlink to fontawesome-webfont with a real file again. Firefox
    silently ignored this symlink and icons were not displayed. This also fixes
    the logger window which was empty before. (Closes: #916431, #906911)
 -- Markus Koschany <email address hidden>  Sat, 15 Dec 2018 14:24:36 +0000"
1806259,2018-12-03 01:30:15 UTC,Hello. Thank you for submitting the bug report. I'm marking this submission as a duplicate.
1806259,2018-12-03 12:42:07 UTC,It's not a duplicate but a different error.
1806262,2018-12-04 10:42:10 UTC,"Hi Sam,"
1806262,2018-12-03 15:19:53 UTC,"> Debian and Ubuntu are removing libgnome-keyring in favor of the freedesktop.org secret service.
> For most OSes, libgnome-keyring has actually been proxying to the secret service for a while now (although Centos6 may be old enough that is not the case).
"
1806263,2019-02-25 18:58:59 UTC,Just hit this bug when trying to change from mysql to mariadb.
1806263,2020-08-22 12:00:47 UTC,This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1683229
1806263,2019-11-21 00:16:37 UTC,"Just to thank you all.  I just hit this problem, solved it and in the process learned something about apparmor."
1806263,2019-09-08 11:29:30 UTC,I see no activities here since may 19 and just ran into this bug on two installations of 18.04.3. This is a major issue preventing the use of mariadb!
1806263,2019-05-14 23:01:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806263,2019-03-13 18:43:38 UTC,Thank you so much for the solution.
1806263,2019-09-09 05:50:39 UTC,@Robie/@Lars  (no on CC) - IIRC this was somewhat known and on your list - are there any updates to the overall case of co-existence (at least after one another)?
1806263,2019-03-08 06:22:45 UTC,"I understand the back and forth between the packages responsibility here.
In fact I was involved in a similar problem for ntp that was discussed here:"
1806263,2019-03-07 12:00:56 UTC,"Yes this is true, and I agree."
1806263,2019-03-07 11:43:20 UTC,"I agree that it's not a MariaDB bug, but it should be tagged as a bug of the MySQL Ubuntu package as long as that one does not disable the apparmor profile upon deinstallation."
1806263,2019-03-07 11:29:21 UTC,"Hi,
thank you for your report and your help making Ubuntu better!
This is not a bug but a problem with apparmor profile shipped with mysql still enabled."
1806263,2019-02-25 19:00:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806263,2019-03-08 06:24:07 UTC,Added an apparmor task for its similarity to bug 1689585 but set it immediately to Won't Fix (as we did there). But having apparmor people getting notified might help with the continuation of this discussion.
1806264,2018-12-03 15:29:18 UTC,"> The moonshot-ui build generates way too many warnings both at the vala
> and  C compilation phases.
>
> I'm concerned that these warnings are likely to mask memory management
> or other problems that may eventually compromise user security.
>
> In addition, there are several design decisions in the code that significantly reduce the robustness of the identity selector below that which I'd consider viable for production security software.
> Here is what I noticed.  In general, I think this code needs some attention.
"
1806264,2019-01-03 08:50:45 UTC,"This commit avoid writing the entire keyring for each action. Instead, every Keyring subclass stores a map between the provided IdCard and the internal reference the Keyring uses. That way, it is possible to directly remove the card, even when display_name or NAI changed."
1806265,2019-06-17 22:53:21 UTC,"This was finally fixed by removing the webupd8team PPA from the repositories. I thought I had removed them completely, but one was still checked. I also had to follow the instructions in the first answer to the question:"
1806265,2021-02-11 19:26:52 UTC,"Similar bug: 1890592
I've solved it by removing JRE8 packages."
1806265,2020-11-23 08:20:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806265,2020-04-30 02:09:28 UTC,"I also had the same issue, have fixed it [by disabling the webupd8team repositories, but some days ago I went again into the same issue again.
Finally, the workaround from Manfred Hampl worked out at the first attempt (actually, on the second attempt, as I forgot to add the '--fix-broken install' apt parameters)."
1806265,2019-06-23 11:02:59 UTC,Possible workaround for such problem:
1806265,2019-06-17 17:42:11 UTC,"I was finally able to resolve this problem by unchecking/removing the entries for java in the webupd8team ppa, after manually installing the Oracle java-8-sdk using the procedures found in the following answer:"
1806265,2019-05-30 11:21:14 UTC,"I am reluctant to change this bug to a question because I think it is a bug that needs to be addressed, but I need some guidance as the next step that I can take to resolve the question. Since I'm not familiar with your bug process and not a member of the team I'm hesitant to assign the bug to myself."
1806265,2019-06-02 11:49:19 UTC,"Problem is definitely related to changes in Oracle licensing for Java, they made a change on April 16, 2019 to their licensing which requires a signature in order to download the DEB file online. There are articles on AskUbuntu regarding this issue related to the webupd8 team PPA:"
1806265,2019-05-30 11:12:44 UTC,I need to get this fixed soon - I haven't been able to run system updates or upgrades for several months.
1806265,2019-05-30 11:10:51 UTC,Noticed that there is a 'net.properties' in both /etc/java-8-openjdk: and /etc/java-11-openjdk:
1806265,2019-05-30 10:54:58 UTC,"I would appreciate a suggestion for appropriate commands in deb or dpkg that might help me narrow down the specific cause or fix the broken cache. I'm reluctant to use the file system to remove the
file '/etc/java-8-openjdk/net.properties' manually, but that will probably my next step."
1806265,2019-05-30 10:47:38 UTC,"I realize that I'm the only one that has reported this problem. I strongly suspect that somehow the Oracle supplied deb package was the root cause of the problem although it appeared to install correctly and without errors, but I can't be certain so I won't point fingers publicly."
1806265,2019-06-17 15:47:14 UTC,"I am still struggling with fixing this bug - I have tried manually installing the new Oracle JDK per the instructions in the following answer, but still run into problems with the automated install."
1806265,2019-05-30 10:37:16 UTC,"I suspect this bug may be related to an install of Oracle's Java package for Ubuntu which I installed using Oracle's deb package. This didn't cause problems for months until I suddenly got the error while running regular packaged updates using the normal user interface and standard Ubuntu tools. I can no longer use apt-get, synaptic or any other deb package installer and I'm hesitant to try to fix things manually by removing files. This latest occurrence was running ""sudo apt-get install -f"""
1806269,2019-10-15 05:01:36 UTC,"I don't have the graphical 'has closed unexpectedly' popups in my environment, but I ran gdb, loaded /usr/bin/nm-connection-editor, and reproduced the crash again. The output is the similar to the original poster of this issue:"
1806269,2019-10-15 14:54:14 UTC,I've built a package containing the fix patch (taken from Debian's 1.8.10-3) and tested to confirm it solves the issue when gnome-keyring is NOT installed.
1806269,2019-10-16 11:35:47 UTC,"I might misunderstand the workflow, but I don't think ""Fix Released"" status applies given the patch hasn't been applied to bionic yet. Currently [1] shows bionic has the following network-manager-applet releases:
1.8.10-2ubuntu2	updates (main)	2019-01-22
1.8.10-2ubuntu1	release (main)	2018-01-27"
1806269,2019-10-21 07:34:32 UTC,"@TJ, thanks for backporting that patch but please don't use an 'official' version number next time. I did a SRU with that fix and some others and it's waiting in the queue
https://launchpadlibrarian.net/446721648/network-manager-applet_1.8.10-2ubuntu3_source.changes"
1806269,2019-10-25 22:48:05 UTC,"OK, I have tested the bionic-proposed 1.8.10-2ubuntu3 release and can confirm it does indeed fix the issue. Thank you."
1806269,2019-10-25 10:20:06 UTC,"Hello TJ, or anyone else affected,"
1806269,2019-11-06 15:48:33 UTC,"The verification of the Stable Release Update for network-manager-applet has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1806269,2019-11-06 15:58:33 UTC,This bug was fixed in the package network-manager-applet - 1.8.10-2ubuntu3
1806269,2019-10-14 14:00:55 UTC,Could you get a backtrace using gdb as described on https://wiki.ubuntu.com/DebuggingProgramCrash ?
1806269,2019-10-22 19:18:17 UTC,"@Sebastian Oops! I usually add ~tj or ~lpXXXXXX but lost that change this time because whilst fighting with trying to combine the upstream, Debian, and Ubuntu git repos and use sbuild to test.
It failed in all sorts of confusing ways so I simply made a non-git copy and ran 'dch -i' immediately without thinking."
1806269,2019-10-14 11:51:40 UTC,"I also tried adding the deb-src repositories (for my sources.list which has bionic/bionic-updates/bionic-security with main/universe/multiverse), then attempted to use apport-retrace [1] with a sandbox to download symbols automatically, but log file didn't have sufficient fields:"
1806269,2018-01-14 11:09:00 UTC,"Hmm, I think these are definitely distinct issues.  Here's what I observe with 1.8.10:"
1806269,2019-10-14 10:05:46 UTC,You can find the dbgsym packages on https://launchpad.net/ubuntu/+source/network-manager-applet/1.8.10-2ubuntu2/+build/16250410
1806269,2019-10-14 02:27:29 UTC,"Hi,"
1806269,2018-12-11 10:27:37 UTC,"Thank you for your bug report, some questions"
1806269,2018-01-16 08:20:51 UTC,@David Tomaschik:
1806269,2018-01-15 10:30:12 UTC,"(In reply to BenWiederhake.GitHub from comment #5)

> Created attachment 366805 [details] [review]
> Patch to fix the crash-on-warning
"
1806269,2018-01-14 22:43:34 UTC,"Created attachment 366805
Patch to fix the crash-on-warning"
1806269,2018-01-14 22:42:18 UTC,"Cause: Apparently it's perfectly okay if the list of modules is empty
(e.g., NULL).  However, the code assume that this indicates an error,
tries to print the NULL error, and crashes.
Checking for NULL before printing it fixes the issue."
1806269,2018-01-14 05:20:32 UTC,"I believe I am having a related (or the same issue).  With network-manager-gnome 1.8.10, I also get a crash on clicking the ""Edit"" icon for any network.  I have discovered this only occurs when I have the opensc-pkcs11 package installed."
1806269,2017-08-01 09:27:08 UTC,"I forgot to mention:  This is *not* related to any of the existing bugs, for the following reasons:
- 781580: Different kind of behavior.  Here: segfault; there: disabled buttons.
- 768986: Crashes in a different place.
- 733034: May have the same underlying cause, but sounds different enough.
- 755663: Here: broken existing feature; there: proposed/missing feature."
1806269,2017-08-01 09:21:59 UTC,"Steps to reproduce on my system:
- Run 'nm-connection-editor'
- Select any network (in my case, a home WLAN for which the computer
  doesn't have the password yet; but *all other* networks are also affected)
- Click the 'Edit' button"
1806269,2019-10-14 11:48:37 UTC,I realized my sources.list file was not standard so I reconstructed my environment with bionic-backports disabled and added bionic-security.
1806270,2018-12-04 20:12:53 UTC,"Perhaps the info on these wiki pages might help:
https://help.ubuntu.com/community/PAE/PentiumM
https://help.ubuntu.com/community/PAE"
1806270,2018-12-05 03:59:38 UTC,i will try and use those links . thank you for your help
1806275,2018-12-03 03:09:17 UTC,Looks like a bug in the weather extension.
1806275,2018-12-13 22:23:47 UTC,Uninstalled and reinstalled the system monitor extension. The extension is as well affected.
1806275,2018-12-13 22:30:45 UTC,I've reported the issue as well upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/852
1806275,2018-12-17 01:51:42 UTC,I suspect this isn't a gnome-shell bug at all.
1806275,2019-07-22 03:57:35 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1806277,2018-12-03 13:05:22 UTC,"Indeed, that's a know feature request upstream, see https://gitlab.gnome.org/GNOME/gnome-calendar/issues/30"
1806279,2018-12-11 02:49:16 UTC,"OK, at scale 100% then this would not be a shell bug. Applications always have the final say in what size their windows are and then shell can't enforce otherwise unless it wilfully displays the window at the wrong size. You would notice if the window contents provided by the app don't fit in that case..."
1806279,2019-07-22 03:58:02 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1806279,2018-12-10 21:00:09 UTC,"Daniel, I disagree with that. Reading some other reports, it looks like windows handle those cases by making the 'half' screen larger to match the minimal width. Under unity7 it was not an issue either. In any case if gnome-shell refuses to do it, it could at least hint of the reason"
1806279,2018-12-10 02:40:16 UTC,If an app refuses to support such aspect ratios and resolutions then that's something only the app can fix. So reassigning to the apps.
1806279,2018-12-05 21:38:03 UTC,"right, well libreoffice is likely in the same case, unsure what would be the alternative option there if the application refuses to bend to the screen geometry"
1806279,2018-12-05 21:23:20 UTC,"There other applications which are affected as well (like LibreOffice). My screen has a resolution set to 2550*1440, scaling is set to 200% (sadly it isn't possible to set scaling to 150% without activating experimental features)."
1806279,2018-12-05 14:53:11 UTC,"The issue there is likely that the calendar minimal width is larger than the horizontal screen resolution, and in this case gnome-shell can't make it fit on screen and such refuse the action. Unsure if there is an easy solution there"
1806286,2019-08-20 01:41:36 UTC,"Thank you for reporting this bug. However, this is not an issue with the Ubuntu package, but an issue with the project itself. This should be reported directly upstream as a feature request."
1806286,2019-08-20 09:57:54 UTC,There is an upstream issue report - is Launchpad able to track the status of Gitlab issues?
1806289,2018-12-03 12:52:22 UTC,"Thank you, is that about scrolling only? Do you use the gesture on a touchscreen or on a touchpad?"
1806289,2018-12-03 15:16:40 UTC,I've just tried scrolling. On pinch to zoom the orientation doesn't matter. Can I test other gestures? Is there an overview of available gestures?
1806289,2019-07-22 03:58:32 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1806292,2018-12-04 19:37:25 UTC,"Description:
I've turned my screen around to work in portrait mode. Sadly LibreOffice which has been maximized came out of this mode. I'm not able to use LibreOffice in a maximized window. The window didn't fit into the screen and therefore it isn't possible to work with LibreOffice in portrait mode. I'll attach a screenshot to clarify what I mean."
1806292,2018-12-04 19:38:44 UTC,"Created attachment 147290
screenshot"
1806292,2018-12-04 19:39:25 UTC,Upstream bugreport: https://bugs.documentfoundation.org/show_bug.cgi?id=121911
1806292,2018-12-04 20:57:43 UTC,Thank you Alexander.
1806292,2018-12-14 15:16:33 UTC,looks like GTK_POLICY_EXTERNAL for a GtkScrolledWindow could be used to get this to work https://developer.gnome.org/gtk3/stable/GtkScrolledWindow.html#GtkPolicyType
1806292,2019-01-15 02:04:07 UTC,This should be fixed in the next version
1806292,2018-12-15 00:58:52 UTC,"Caolán McNamara committed a patch related to this issue.
It has been pushed to ""master"":"
1806292,2019-01-11 16:27:28 UTC,"Caolán McNamara committed a patch related to this issue.
It has been pushed to ""libreoffice-6-1"":"
1806292,2018-12-04 19:28:51 UTC,"I meant maximized window. There other applications which are affected as well. My screen has a resolution set to 2550*1440, scaling is set to 200% (sadly it isn't possible to set scaling to 150%)."
1806292,2019-01-15 02:04:07 UTC,*** Bug 121911 has been marked as a duplicate of this bug. ***
1806292,2019-01-15 09:21:14 UTC,The upstream bug suggests it's going to be fixed in 6.1.5 and 6.2.0.1
1806292,2018-12-15 00:58:43 UTC,"Caolán McNamara committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1806292,2018-12-04 16:11:08 UTC,"Do you mean fullscreen, or maximized window?"
1806292,2018-03-08 16:40:28 UTC,"Some screen clips would be helpful, not clear if you are refering to the Client Side Decorations of the frame or the text Menu."
1806292,2018-10-29 07:27:27 UTC,"Roy, please check 6.2.0.0 as bug 93085 could be related."
1806292,2018-03-08 10:53:20 UTC,At least in Mageia Linux the width of a LibreOffice window cannot be smaller than the length of the menu bar.
1806292,2018-11-08 11:31:58 UTC,Finally downloaded 6.2 and the problem is still present.
1806292,2018-03-08 20:38:50 UTC,"Created attachment 140486
LO 6 Writer screenshot"
1806292,2018-03-08 20:41:04 UTC,"Created attachment 140487
LO 6 Calc min window width"
1806292,2018-03-09 06:32:38 UTC,"Created attachment 140495
LO_6_Win7_shot"
1806292,2018-03-08 11:00:05 UTC,"Note that a couple of people on the mailing list indicated that this problem did not appear in their Linux versions (Puppy, Mint, openSuse)."
1806292,2018-03-10 21:28:36 UTC,"Its a native GtkMenuBar inside a toplevel GtkWindow. So presumably the min size is that of its contents. GtkToolBar comes with a ""show-arrow"" property which allows the toolbar to be shrunk past the size of its contents and show the entries in an overflow menu. I see no such properties with a GtkMenuBar, so I think that's just the way it is with a native gtk menubar so someone probably needs to ask upstream gtk if there's a mechanism to achieve this, if it even is something that should be desirable. Sticking it into a scrolledwindow would just leave the excess elements unusable."
1806292,2018-03-14 08:46:39 UTC,"""Sticking it into a scrolled window would just leave the excess elements unusable."""
1806292,2018-03-14 08:53:26 UTC,And that was the behavior of the x11/gtk2 build if I remember right
1806292,2018-10-24 11:14:27 UTC,"Hello Roy Reeese,
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version."
1806292,2018-10-24 13:01:57 UTC,Versions are getting a bit confusing at this point:
1806292,2018-03-09 09:09:51 UTC,"I'm seeing the same with 5.4.5.1-1.fc27 on FC27
Also with 6.0.2.1-1.mga7 on Mageia Cauldron."
1806295,2020-08-04 16:07:12 UTC,"Can you attach some picture what does it mean ""Text Tool"" icon is missing?
Can you also retest this problem using latest Ubuntu Daily PPA: https://launchpad.net/~pinta-maintainers/+archive/ubuntu/pinta-daily"
1806295,2020-08-13 00:02:52 UTC,"I set up a fresh VM with Linux Mint 20, and installed Pinta 1.7 from the stable builds PPA (https://launchpad.net/~pinta-maintainers/+archive/ubuntu/pinta-stable). The text tool icon appeared as expected, so I think this can be closed unless more details / steps to reproduce can be provided."
1806295,2020-08-13 01:22:51 UTC,"Have since upgraded and the newest edition it returned, no idea, thank
you..."
1806296,2018-12-06 05:13:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623137"
1806296,2018-12-07 05:42:29 UTC,A very basic minimal element seems to work based on the public beta per the above change.
1806296,2019-05-31 07:04:02 UTC,"Change abandoned by Ian Wienand (<email address hidden>) on branch: master
Review: https://review.opendev.org/623137
Reason: support for rhel8 is added with I90540675c70bb475d9db2ae24f81c648a31f3f95"
1806309,2019-04-28 17:58:10 UTC,The problem has been solved. Please checkout the current git master:
1806320,2019-10-07 22:46:06 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1806320,2018-12-03 03:55:58 UTC,The following test is failing on snapd on cosmic on s390x:
1806320,2019-10-07 00:49:18 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue is still happening with the current snapd version?"
1806321,2018-12-12 10:57:00 UTC,"I have determined this to be a lack of input overrides in the udev hwdb.d 60-keyboard.hwdb definition. For now, I have declared the following in my /etc/udev/hwdb.d/90-apple-keyboard.hwdb, which I'll attach. It may or may not be accurate for all Apple keyboards."
1806321,2018-12-12 11:03:15 UTC,"Disregard that, I am wrong. The bug appears to be with the plasma-desktop multimedia keys integration, which appears to be broken now."
1806323,2018-12-03 12:17:30 UTC,@superm1 ~superm1 ?
1806323,2018-12-04 16:48:14 UTC,"I foolishly sent logs from the wrong machine.  Please ignore the logs from machine ""hauser"" and use the logs from the machine ""gene-pc""."
1806323,2018-12-04 16:46:19 UTC,apport information
1806323,2018-12-04 16:46:18 UTC,apport information
1806323,2018-12-04 16:46:17 UTC,apport information
1806323,2018-12-04 16:46:15 UTC,apport information
1806323,2018-12-04 16:40:43 UTC,apport information
1806323,2018-12-04 16:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1806323,2018-12-04 15:59:58 UTC,Thanks for the response.  There is quite a lot going on here.
1806323,2018-12-04 04:16:32 UTC,The computer is a dell XPS 9570. Both the internal and external displays are 4K.
1806323,2018-12-03 17:35:46 UTC,Which XPS model? Important to figure out which code is run in i915.
1806323,2018-12-04 16:40:44 UTC,apport information
1806323,2018-12-04 16:40:45 UTC,apport information
1806328,2019-06-11 13:57:46 UTC,"Reviewed:  https://review.opendev.org/621473
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=4666dc02a0051e9eb7116e630986e7408480f927
Submitter: Zuul
Branch:    master"
1806328,2018-12-03 04:55:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/621473"
1806328,2019-02-19 13:17:13 UTC,Still working on this?
1806333,2020-04-10 04:17:32 UTC,[Expired for calamares (Ubuntu) because there has been no activity for 60 days.]
1806333,2020-02-09 22:15:45 UTC,"Since reporting this, 18.10 has since gone unsupported. If you could re-test with 19.10 that would be great. If you can reproduce, please let us know clear steps to do so so we can clearly identify the problem. Knowing your partition setup would help out a lot. You can use `apport-collect 1806333` to collect some of this information after you've had another failure."
1806338,2019-07-18 21:45:18 UTC,"Hi,"
1806343,2018-12-21 03:39:07 UTC,apport information
1806343,2018-12-21 03:50:02 UTC,I commented out asus_nb_wmi that I had in /etc/modules before I posted that.
1806343,2018-12-21 13:01:08 UTC,"Not sure why ""acpi_osi="" is uses in your kernel parameter, but please remove it and see if it starts working."
1806343,2018-12-21 17:26:36 UTC,"Whoops, forgot about that, I was attempting to use that to fix some things (trying things from internet searches,) didn't work before that."
1806343,2018-12-28 16:24:40 UTC,"Please boot without any workaround, then attach ""acpidump"" here, thanks!"
1806343,2019-01-02 00:34:47 UTC,"How do I get ""acpidump""? Does this refer to ""apport-collect 1806343""?"
1806343,2019-01-02 00:37:33 UTC,Found out it's part of the acpica-tools package.
1806343,2019-01-02 01:39:41 UTC,Steps:
1806343,2019-01-15 09:33:02 UTC,"Same problem with Lubuntu 18.10 on ASUS Zenbook UX31A. It loads asus kernel modules:
- asus_nb_wmi
- asus_wmi
- asus_wireless"
1806343,2019-01-15 09:36:42 UTC,See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652
1806343,2019-01-15 09:51:06 UTC,and and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796573
1806343,2019-01-27 18:10:39 UTC,I don't think it works on the 4.18 kernel.
1806343,2019-03-20 07:16:47 UTC,"Please update your system, I recall new upower has a fix for this issue."
1806343,2019-03-20 13:21:00 UTC,"Disco
5.0.2-050002-lowlatency
update / upgrade daily"
1806343,2019-07-22 19:32:48 UTC,"Hi, for me all fn combs work except keyboard backlight, I'm on an Asus ROG."
1806343,2018-12-21 03:39:03 UTC,apport information
1806343,2018-12-21 03:38:57 UTC,apport information
1806343,2018-12-21 03:38:48 UTC,apport information
1806343,2018-12-21 03:38:53 UTC,apport information
1806343,2018-12-03 08:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1806343,2018-12-03 14:11:47 UTC,apport information
1806343,2018-12-21 03:38:55 UTC,apport information
1806343,2018-12-17 05:08:23 UTC,So asus_nb_wmi isn't automatically loaded on the system?
1806343,2018-12-17 21:41:55 UTC,Correct.
1806343,2018-12-17 21:45:43 UTC,I also recently upgraded to kernel: 4.20.0-042000rc6-generic to test out as 4.19 was having issues corrupting ext4 partitions.
1806343,2018-12-18 07:02:02 UTC,"Can you boot to default Ubuntu kernel without any workaround, then run ""apport-collect 1806343""?"
1806343,2018-12-21 03:38:34 UTC,apport information
1806343,2018-12-16 20:44:36 UTC,Finally figured out to load module: asus_nb_wmi
1806343,2018-12-21 03:38:39 UTC,apport information
1806343,2018-12-21 03:38:41 UTC,apport information
1806343,2018-12-21 03:38:42 UTC,apport information
1806343,2018-12-21 03:38:46 UTC,apport information
1806343,2018-12-21 03:38:51 UTC,apport information
1806343,2018-12-21 03:38:49 UTC,apport information
1806343,2018-12-21 03:38:36 UTC,apport information
1806347,2018-12-11 20:17:40 UTC,"I removed the MPs too early, let me add them back.
We need some way to pass these tests atm"
1806347,2018-12-11 08:14:16 UTC,"No, in fact it is still as bad :-/
@xnox since the MPs marking them as badtest for now were ignored, should I open them up again or how do we plan to resolve that short term?"
1806347,2018-12-11 06:22:12 UTC,"Issues were fixed by the last upload implementing most of the suggested fixes.
At least the more recent tests all worked for me.
Cancelling the MPs and set to fix released."
1806347,2018-12-03 11:16:14 UTC,"(for now) Britney hints are supplied to unblock several SRUs that block on these tests while not causing it.
This bug will stay open to (hopefully) track and address it for real on the next systemd upload."
1806347,2018-12-11 06:24:06 UTC,"After actually waking up I realized that they still are broken, retriggering the tests to make sure they really work."
1806352,2018-12-16 10:17:23 UTC,"After a lot of wrong trying, I worsen the problem. So I reinstall Ubuntu again. This time I followed instructions from:
https://wiki.ubuntu.com/DebuggingPrintingProblems
and I typed the command
tail -f /var/log/syslog
From the screen report, I saw missing of systray and plugin. I concluded that systray is not essential so didn't install it at all. I just put the:
sudo hp-plugin -i"
1806352,2018-12-10 14:36:27 UTC,"> When I click 'Next', just get 'Failed to install Plug-in'.
"
1806352,2018-12-10 07:45:36 UTC,"Dear Brian
After a lot of trying everything, now I have a more serious problem then systemtry-icon."
1806352,2018-12-09 20:28:37 UTC,"Your problem solving has now changed from an inability of CUPS to detect ""usb://HP..."" /...."" to ""some problem with systray"" after installing the latest hplip-3.18.12.run."
1806352,2018-12-04 08:55:55 UTC,Dear Santhosh
1806352,2018-12-04 09:37:40 UTC,"I just installed 'libcanberra-gtk-module'. Now, 'canberra-gtk-module' problem disappeared.
But, I still have:"
1806352,2018-12-04 05:18:47 UTC,"Dear Zoran,"
1806352,2018-12-04 09:48:02 UTC,"I just reinstalled: python and python2.7, but the problem persists. It seems as there is some problem with systray."
1806352,2018-12-03 15:03:47 UTC,From the information you gave:
1806352,2018-12-03 14:40:32 UTC,"Hello Zoran,"
1806352,2018-12-03 14:16:29 UTC,Hello Brian
1806352,2018-12-03 13:52:11 UTC,"Hello Zoran,"
1806352,2018-12-03 13:01:58 UTC,"brian, Till, thanks for fast reply.
LaserJet 1005 is the local printer. Model of the network printer is HP LaserJet Professional P1102."
1806352,2018-12-03 12:00:20 UTC,Moved to HPLIP and added upstream task as original reporter is using upstream package.
1806352,2018-12-03 11:18:25 UTC,To confirm: The LaserJet 1005 is on the network?
1806352,2018-12-03 16:59:10 UTC,"Hello Zoran,"
1806377,2019-03-12 14:14:48 UTC,"Does the region ""SC2"" exist already?"
1806377,2019-05-12 04:17:30 UTC,[Expired for OpenStack Identity (keystone) because there has been no activity for 60 days.]
1806381,2020-07-01 01:15:16 UTC,"I already submitted the fixes, but no reaction from any maintainer. Additionally CI partially didn't work at the time. I'm not sure how to proceed after the maintainer fixed CI."
1806381,2020-06-30 18:24:04 UTC,"Hello Rohan, quick follow up with this bug, when will this fix been released?"
1806381,2019-04-10 22:14:19 UTC,"I'm not sure how this ever worked, but the issue is that the code expects that Jenkins will return a string like ""Result: <bool>"" where the boolean is the result of the call to check whether a restart is needed. However, the Groovy script run for this neither gathers the result or prints it in the format expected. I guess maybe old versions of Jenkins took a boolean result of the script itself and printed ""Result: <script result>""."
1806381,2019-12-17 10:20:47 UTC,"Hello Rohan, In which release, will it be included ?"
1806381,2019-06-21 21:36:38 UTC,"Hello, will the fix proposed by Dan Nicholson be added to a release some time soon? I verified that it worked. I am trying to automate plugin updates and this library is making it possible to do so."
1806381,2020-04-10 17:48:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/719059"
1806385,2019-01-10 16:25:26 UTC,"This seems to have begun at the below commit.
Adding Cc: to Andrzej J.R. Hunt ; Could you possibly take a look at this one?
Thanks"
1806385,2019-12-08 13:53:06 UTC,"No, you can easily tell where the new slide is created, simply by tying defferent text into the existing slides (suggestion: Type ""1"" into slide 1, ""2"" into slide 2, etc.). If you do so, you will find that as soon as the existing slides fill the side bar, the new slide will be created at an unexpected position."
1806385,2019-12-03 20:35:59 UTC,"As for improvement, that's welcome.
As for bug, I don't understand it. To me it looks like new slide is created at the end. Anyway, it's the same as the previous one, so how could you tell the difference."
1806385,2018-12-06 06:29:53 UTC,Confirmed from my side for
1806385,2018-12-07 13:30:57 UTC,Also reproduced in
1806385,2018-12-05 18:15:51 UTC,"Na problem, here it is:
https://bugs.documentfoundation.org/show_bug.cgi?id=121927"
1806385,2018-12-05 18:14:58 UTC,"Description:
Version: 6.1.3.2
Build-ID: libreoffice-6.1.3.2-snap1"
1806385,2018-12-04 15:58:19 UTC,"This is not a snap-specific issue, indeed. Would you mind filing an upstream bug report at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and sharing the link to that bug report here? Thanks!"
1806385,2018-12-05 19:16:18 UTC,Thanks!
1806385,2018-12-03 12:32:07 UTC,I don't know if the bug is related to the snap. Probably not.
1806386,2018-12-03 13:25:30 UTC,if it is of any help the above cluster has been deployed using this how to : https://github.com/juju-solutions/bundle-canonical-kubernetes/wiki/Running-CDK-in-a-restricted-environment
1806386,2018-12-04 15:57:29 UTC,The error you have is out of the Juju client which is deployed as a snap. I'm going to guess that you had some sort of snap upgrade issue and it's unrelated to rebooting the controller as it does not use a snap for any part of its operations currently.
1806387,2019-08-05 19:10:33 UTC,"py-pip must indeed be hard dependency. Why not python-pip and python3-pip?
---
2019-08-05 19:02:23.140 |   Found existing installation: PyYAML 3.12
2019-08-05 19:02:23.149 | ERROR: Cannot uninstall 'PyYAML'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.
---"
1806387,2019-02-22 15:03:39 UTC,"Devstack isn't meant to be part of a bigger stack, if you need that, please have a look at some other deployment project."
1806387,2019-02-22 15:41:51 UTC,"Here are two valid reasons-
- The OS provided pip package is supported by OS vendor but PyPi is not.
- Devstack deletes system python pip but does not migrate system python modules - thats data loss."
1806387,2019-02-22 15:43:04 UTC,"I have changed state to new because its not ""spam""."
1806387,2019-08-05 18:40:15 UTC,"Right now it sucks devstack has hard dependency on OS vendor-unsupported pip2.7 binary.
Running these commands on production systems is sickening from quality/security perspective."
1806388,2018-12-11 05:51:56 UTC,This bug was fixed in the package sbuild - 0.77.1-2ubuntu2
1806390,2019-07-08 09:57:17 UTC,"Hi @Yang, can You give us link to Your PoC patch?"
1806390,2019-07-09 01:15:42 UTC,@Slawek
1806390,2019-10-03 19:37:54 UTC,"Hi again,"
1806390,2019-04-02 04:59:46 UTC,"@Miguel Sorry for late. I posted a PoC patch, so please review it when you possible. Thanks."
1806390,2019-10-04 08:41:49 UTC,"After some investigation of routed network, I found out I could achieve distributed DHCP if segment are created for each hypervisor."
1806390,2019-11-29 08:54:01 UTC,"Hi Yang Youseok,"
1806390,2019-11-29 09:10:26 UTC,Hi Slawek.
1806390,2019-10-04 01:34:45 UTC,"Hi Slawek again,"
1806390,2019-02-08 00:59:52 UTC,"@Miguel,"
1806390,2019-01-03 23:06:46 UTC,"@Yang,"
1806390,2019-01-11 09:25:32 UTC,"Nice to see this old problem again, ;-)"
1806390,2019-01-11 03:02:10 UTC,"@Miguel,"
1806390,2019-01-11 00:44:17 UTC,I just emailed to your gmail address a copy of the presentation Carl and used in that presentation
1806390,2019-01-11 00:40:25 UTC,"@Yang,"
1806390,2019-01-04 01:18:25 UTC,@Miguel
1806390,2018-12-10 13:37:01 UTC,"@Brian Hi Brian. Yes, actually there is no problem with the concept of dhcp-agent on each compute node already. The issue is about performance degradation, not about working."
1806390,2018-12-05 21:53:44 UTC,"I thought with DVR enabled you could also start the dhcp-agent on each compute node and achieve this, but it's been a while since I tested that configuration, so I could be mis-remembering.  It's worth a try."
1806390,2018-12-04 05:41:11 UTC,@Bence Thank you for the guide. I will take this at the meeting. :)
1806390,2018-12-03 15:16:28 UTC,Thank you for your RFE report.
1806390,2019-02-07 23:29:43 UTC,"@Yang,"
1806394,2019-05-07 16:12:40 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jason, Millissa, and Rogan!"
1806394,2019-03-11 15:22:56 UTC,This might be redundant now but here goes:
1806394,2018-12-03 13:18:08 UTC,"Speaking of:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1806394_item_bucket_holds / working/user/jboyer/lp1806394_item_bucket_holds"
1806394,2019-03-05 22:45:28 UTC,"Millissa, can you please add a sign off comment? You can put it in this format:"
1806394,2019-03-05 22:30:31 UTC,Tested on the sandbox 3/5/19. Was able to place holds on different items in item bucket. Confirmed the hold was placed. Looks like it is working.
1806394,2019-03-06 14:29:47 UTC,"Worked as advertised, signoff here: user/rogan/lp1806394"
1806395,2018-12-11 19:50:57 UTC,"Created attachment 279957
dmesg 4.20.0-042000rc6-generic (Many messages from i2c...)"
1806395,2019-09-11 10:47:56 UTC,"Similar problems with Acer TravelMate B118-M that has ElanTech touchpad ELAN0502.
My distro is Lubuntu 16.04.6 LTS 64 bit with 4.15.0-60-generic kernel (up-to-date).
Tried to upgrade the kernel to latest releases, but it claims for libssl1.1 (used in 18.04) and 16.04 uses libssl1.0
I tested the laptop with Lubuntu 18.04.3 64bit (USB installation stick) that it comes with 5.0.0-23-generic kernel and it works!"
1806395,2018-12-11 10:46:11 UTC,"Created attachment 279933
dmesg 4.20.0-042000rc6-generic"
1806395,2018-12-03 13:30:12 UTC,This change was made by a bot.
1806395,2018-12-03 16:38:26 UTC,"Hello,"
1806395,2018-12-03 15:09:38 UTC,"dmesg 4.20.0-042000rc5-generic:
[   15.349630] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)"
1806395,2018-12-03 14:49:06 UTC,"dmesg 4.19.0-7-generic:
[   15.116463] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)"
1806395,2018-12-04 18:13:32 UTC,"dmesg 4.18.20-041820-generic:
[ 6314.257569] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.262609] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.272098] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.281645] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.291288] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.300927] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.310640] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.320165] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.329682] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[ 6314.339269] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)
[...]"
1806396,2018-12-03 13:30:19 UTC,This change was made by a bot.
1806396,2018-12-03 14:46:16 UTC,"dmesg 4.19.0-7-generic:
[   14.444653] lis3lv02d: unknown sensor type 0x0"
1806396,2018-12-03 15:06:42 UTC,"dmesg 4.20.0-042000rc5-generic:
[   15.029705] lis3lv02d: unknown sensor type 0x0"
1806396,2018-12-04 11:21:26 UTC,"Hello,"
1806396,2018-12-11 10:48:19 UTC,"Created attachment 279935
dmesg 4.20.0-042000rc6-generic"
1806397,2018-12-11 10:50:31 UTC,"Created attachment 279937
dmesg 4.20.0-042000rc6-generic"
1806397,2019-01-30 08:20:10 UTC,"Cristian, this message is harmless, kernel is just saying acer_wmi is not to be loaded because your machine is not an Acer."
1806397,2018-12-04 14:34:12 UTC,"Do you see any missing functionalities, such as some of the function keys/hotkeys not functional?"
1806397,2018-12-04 17:31:17 UTC,"Anthony Wong (anthonywong),"
1806397,2018-12-03 16:19:45 UTC,"dmesg 4.20.0-042000rc5-generic:
[   15.619027] acer_wmi: Acer Laptop ACPI-WMI Extras"
1806397,2018-12-03 14:51:34 UTC,"dmesg 4.19.0-7-generic:
[   16.578306] acer_wmi: Acer Laptop ACPI-WMI Extras"
1806397,2018-12-03 13:30:27 UTC,This change was made by a bot.
1806397,2018-12-03 16:56:26 UTC,"Hello,"
1806399,2018-12-04 19:59:20 UTC,From the attached DpkgHistoryLog.txt I can infer that the problem started after removing python3.
1806399,2018-12-06 18:48:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806399,2019-08-15 16:42:55 UTC,Have this same problem on 16.04LTS
1806403,2018-12-04 16:49:56 UTC,had a look here but no root cause yet adding note for now. looking at [1] periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset037-updates-queens has been failing for this for more than a week (we only get 1run/day on this job). I know this error is coming from [2] and trying to compare to a successful rocky run @ [3].. wondering if this bit is the problem from [4] (the config/auth config in particular)
1806403,2019-02-19 13:18:47 UTC,Is this still an issue?
1806407,2019-03-22 11:03:06 UTC,mate@mate-Lenovo-YOGA-330-11IGM:~$ dig google.com
1806407,2019-03-22 08:59:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806407,2019-03-22 08:52:38 UTC,still no luck when i change /etc/NetworkManager/NetworkManager.conf to bypass system-resolved with
1806407,2020-10-03 13:17:52 UTC,Thrilled to confirm that this now works in Ubuntu 20.04.1 LTS 64bit I have checked today.
1806407,2019-03-22 08:36:52 UTC,i'm using Mobile Broadband in Network Manager applet to make a connection from an usb modem.
1806407,2019-03-22 08:35:35 UTC,"in my Ubuntu-MATE 18.04.2, all my three modems after connect to provider but browser says it cannot Resolve domains. in /var/log/syslog somehow appears 'degraded nameserver' or something. But Wifi connection works smooth. i have Ubuntu-MATE 16.04.2 and my modems work fine."
1806407,2018-12-03 16:24:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1806407,2019-03-22 08:48:59 UTC,"Mar 22 15:46:59 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using degraded feature set (TCP) for DNS server 112.215.71.243.
Mar 22 15:47:03 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using degraded feature set (UDP) for DNS server 112.215.198.254.
Mar 22 15:47:05 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using degraded feature set (UDP) for DNS server 112.215.71.243.
Mar 22 15:47:08 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using degraded feature set (TCP) for DNS server 112.215.71.243.
Mar 22 15:47:08 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using degraded feature set (TCP) for DNS server 112.215.198.254.
Mar 22 15:47:14 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using degraded feature set (UDP) for DNS server 112.215.71.243.
Mar 22 15:47:14 mate-Lenovo-ideapad-D330-10IGM systemd-resolved[576]: Using degraded feature set (UDP) for DNS server 112.215.198.254."
1806412,2018-12-03 15:00:08 UTC,This change was made by a bot.
1806412,2018-12-04 19:49:23 UTC,"I leave this here:
https://bugzilla.kernel.org/show_bug.cgi?id=201685
--
Cristian Aravena Romero (caravena)"
1806413,2018-12-20 06:09:54 UTC,The package has been published and the bug is being set to Fix Released
1806413,2018-12-17 09:51:55 UTC,"4.18.0-13.14~18.04.1 - generic
Regression test CMPL, RTB."
1806415,2018-12-07 19:37:17 UTC,Release gating - introduced by the LVM Local Storage patch elimination code changes
1806415,2019-06-07 21:30:56 UTC,Are these the right steps to follow? execution has been done in both a bare metal and virtual deployment.
1806415,2019-07-03 14:26:40 UTC,Based on Abraham's re-test this issue no longer occurs.  Expectation is that a code change was done early in 2019 to address this issue.  Marking this LP as fix released and request the test team re-test.
1806415,2019-07-15 19:08:06 UTC,It is now fixed . I do not see the issue 20190708T233000Z
1806421,2020-04-29 08:08:47 UTC,"Use of uninitialized value $stopcond in quotemeta at /usr/lib/x86_64-linux-gnu/perl5/5.30/SNMP.pm line 884, <CONF> line 252.
Use of uninitialized value $stopcond in quotemeta at /usr/lib/x86_64-linux-gnu/perl5/5.30/SNMP.pm line 884, <CONF> line 252.
Use of uninitialized value $stopcond in quotemeta at /usr/lib/x86_64-linux-gnu/perl5/5.30/SNMP.pm line 884, <CONF> line 252.
Use of uninitialized value $stopcond in quotemeta at /usr/lib/x86_64-linux-gnu/perl5/5.30/SNMP.pm line 884, <CONF> line 252.
Use of uninitialized value $stopcond in quotemeta at /usr/lib/x86_64-linux-gnu/perl5/5.30/SNMP.pm line 884, <CONF> line 252."
1806421,2019-01-05 15:45:10 UTC,I just upgraded my Icinga server last night from 16.04 to 18.04 and I am also using the same script and I am having the same issue.  I also posted an issue on the author's page as a heads up to see if they can update the script:
1806421,2020-04-29 08:12:08 UTC,"Tested on standard debian buster, upped packages and issue persists"
1806421,2018-12-06 08:08:25 UTC,"Then I just get:
VRRP UNKNOWN: SNMP error: Unknown Object Identifier"
1806421,2018-12-06 00:55:45 UTC,What is the failure you get when running https://github.com/alaskacommunications/nagios_check_keepalived/blob/master/check_keepalived_vrrp.pl on ubuntu bionic? You only showed the undef errors when switching to SNMPv1
1806421,2018-12-06 00:54:17 UTC,Link to mentioned patch: https://sourceforge.net/p/net-snmp/patches/1278/
1806421,2019-01-05 15:37:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806429,2018-12-11 14:32:25 UTC,No pending verification.
1806429,2018-12-13 10:05:39 UTC,"3.13.0-164.214~precise1 - generic
Regression test CMPL, RTB."
1806429,2018-12-18 13:11:14 UTC,"Please note we do not have i386 images due to bug https://bugs.launchpad.net/maas/+bug/1807820
It appears that i386 precise support has been dropped in MAAS"
1806429,2018-12-19 15:25:45 UTC,"Removed tag regression-testing-passed and set regression-testing back to ""Incomplete"" since we are still missing i386 test results."
1806429,2018-12-20 10:25:19 UTC,"3.13.0-164.214~precise1 - generic
Regression test CMPL, RTB."
1806429,2018-12-20 17:00:40 UTC,The package has been published and the bug is being set to Fix Released
1806430,2018-12-11 14:30:30 UTC,"No non-security changes, no pending verification."
1806430,2018-12-13 09:46:31 UTC,"3.2.0-139.185 - generic
Regression test CMPL, RTB."
1806430,2018-12-20 12:07:49 UTC,"3.2.0-139.185 - generic
Regression test CMPL, RTB."
1806430,2018-12-20 17:03:27 UTC,The package has been published and the bug is being set to Fix Released
1806435,2020-03-07 10:32:10 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1806436,2018-12-03 15:46:18 UTC,"dmesg 4.19.0-7-generic:
[   14.432061] hp_accel: laptop model unknown, using default axes configuration
[   14.444657] hp_accel: probe of HPQ6007:00 failed with error -22"
1806436,2018-12-03 15:47:58 UTC,"dmesg 4.20.0-042000rc5-generic:
[   15.016177] hp_accel: laptop model unknown, using default axes configuration
[   15.029728] hp_accel: probe of HPQ6007:00 failed with error -22"
1806436,2018-12-03 16:00:09 UTC,This change was made by a bot.
1806436,2018-12-03 16:48:45 UTC,"Hello,"
1806436,2018-12-11 10:52:27 UTC,"Created attachment 279939
dmesg 4.20.0-042000rc6-generic"
1806436,2019-01-16 04:08:54 UTC,"Does your laptop use either SSD or m2 drive? If so, hp_accel is useless for them."
1806437,2020-02-12 10:31:34 UTC,"If possible, please attach your acpi dump for inspection:"
1806437,2020-02-12 15:26:21 UTC,Here is an ACPI dump on a Dell Latitude 5590 with kernel 5.5.3.
1806437,2020-02-13 07:39:28 UTC,"_SB.WTBT._HID = ""PNP0C14""
_SB.AMW0._HID = ""PNP0C14""
_SB.AMW4._HID = ""PNP0C14""
_SB.AMW2._HID = ""PNP0C14"""
1806437,2020-03-06 22:05:54 UTC,Any update on this?  I'm currently running into this issue as well.
1806437,2020-04-24 05:39:32 UTC,"It's benign; your BIOS has ""duplicate WMI entries"" within its ACPI tables and the kernel is reporting that."
1806437,2020-02-12 10:26:28 UTC,"https://github.com/torvalds/linux/blob/master/drivers/platform/x86/wmi.c#L1173
Such duplicated entries are dumped without further processing. Unless we find further info, especially from ACPI standard, this is probably a WONTFIX."
1806437,2020-03-25 04:21:12 UTC,Still seeing this in Ubuntu 20 daily.
1806437,2020-03-25 04:37:57 UTC,"Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.67.0
Qt Version: 5.12.5
Kernel Version: 5.4.0-18-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.4 GiB of RAM"
1806437,2020-04-24 05:43:53 UTC,https://lkml.org/lkml/2017/12/8/914
1806437,2020-03-20 21:47:55 UTC,"Same story here on a Lenovo S340 Ideapad with Xubuntu 19.10. More details can be found here https://superuser.com/q/1524979/865660
[    1.045638] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
[    1.045676] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)"
1806437,2020-02-11 06:26:19 UTC,"Same.
ASUS Prime X470 Pro
kernel 5.5.1-1-default"
1806437,2020-03-20 21:50:01 UTC,"From the Superuser link I left above, I suspect that this causes suspend issues."
1806437,2019-11-18 18:03:17 UTC,"For the stats i have it as well - came accross it, while troubleshooting freeze when shutting down opensuse :
uname -a
Linux linux-xnik.site 5.3.7-1-default #1 SMP Mon Oct 21 06:03:17 UTC 2019 (3eea5a9) x86_64 x86_64 x86_64 GNU/Linux
But has had it for since some versions back (OMG i see further down i have some cleaning up to do ...:"
1806437,2019-10-28 20:27:22 UTC,I also have these issues and many more on the Dell Precision 7540 with i7 9750H.
1806437,2019-09-10 07:22:31 UTC,The same issue occurs on a Lenovo ThinkPad P52. It occurs with various BIOS versions and with both kernel 4.19.x and kernel 5.2.x.
1806437,2019-04-05 18:21:01 UTC,I am also receiving this message as described in the Ubuntu bug tracker linked above
1806437,2019-03-14 03:18:28 UTC,"I get this bug on Ubuntu 18.10 with the kernel upgraded to 5.0.2 from the ubuntu repository. My machine is an Acer Predator Helios 500 Ryzen.
acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)"
1806437,2019-02-16 14:14:04 UTC,"Me also on a Lenovo X1 6 Gen on Debian 9:
dmesg =>
[    2.611547] thinkpad_acpi: ThinkPad ACPI Extras v0.26
[    2.611547] thinkpad_acpi: http://ibm-acpi.sf.net/
[    2.611548] thinkpad_acpi: ThinkPad BIOS N23ET59W (1.34 ), EC unknown
[    2.611549] thinkpad_acpi: Lenovo ThinkPad X1 Carbon 6th, model 20KG004JFR
[    2.612073] thinkpad_acpi: radio switch found; radios are enabled
[    2.612262] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[    2.612263] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[    2.613667] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[    2.614639] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is unblocked
[    2.617173] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
[    2.617398] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
[    2.617460] acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)"
1806437,2018-12-18 00:20:22 UTC,"I experience this problem on HP Spectre x360 15-df0850nz, when trying to boot from usb.
These lines are displayed and soon after the computer freezes.
Can this be the reason it fails to start?"
1806437,2018-12-11 10:54:47 UTC,"Created attachment 279941
dmesg 4.20.0-042000rc6-generic"
1806437,2018-12-04 13:00:48 UTC,"Hello,"
1806437,2018-12-03 16:00:16 UTC,This change was made by a bot.
1806437,2018-12-03 15:53:59 UTC,"dmesg 4.20.0-042000rc5-generic:
[    1.880322] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)"
1806437,2018-12-03 15:52:37 UTC,"dmesg 4.19.0-7-generic:
[   14.263457] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)"
1806437,2020-01-27 11:19:19 UTC,I am seeing this error message on a Dell Latitude 5590 with kernel 5.5.0:
1806439,2020-08-13 12:18:47 UTC,I faced the same error here.
1806439,2019-08-11 15:18:08 UTC,"Comment on attachment 284319
Dmesg"
1806439,2019-08-11 15:17:24 UTC,"Created attachment 284319
Dmesg"
1806439,2018-12-03 16:00:27 UTC,This change was made by a bot.
1806439,2018-12-03 17:00:57 UTC,"Hello,"
1806439,2018-12-03 16:00:45 UTC,"dmesg 4.20.0-042000rc5-generic:
[    1.880345] wmi_bus wmi_bus-PNP0C14:02: WQBJ data block query control method not found"
1806439,2018-12-03 15:58:42 UTC,"dmesg 4.19.0-7-generic:
[   14.263472] wmi_bus wmi_bus-PNP0C14:02: WQBJ data block query control method not found"
1806439,2018-12-11 10:56:12 UTC,"Created attachment 279943
dmesg 4.20.0-042000rc6-generic"
1806451,2019-01-07 16:31:00 UTC,"Reviewed:  https://review.openstack.org/626595
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=f750ab67ead3692145c7bf78f77edc96bf0cc97d
Submitter: Zuul
Branch:    stable/rocky"
1806451,2019-01-08 19:25:51 UTC,"Reviewed:  https://review.openstack.org/629200
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=5bb0a71c65d5f35e0945e93ddc0ce273da12fbe4
Submitter: Zuul
Branch:    stable/queens"
1806451,2019-01-08 19:25:43 UTC,"Reviewed:  https://review.openstack.org/629199
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a9d337396f8ccd60192c09dfb1b352afe9585cb1
Submitter: Zuul
Branch:    stable/queens"
1806451,2019-01-08 14:53:19 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/629200"
1806451,2019-01-08 14:49:41 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/629199"
1806451,2019-01-08 14:06:06 UTC,"Reviewed:  https://review.openstack.org/626597
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=608096fb3ce3cf291550278c39be3b0562bd18eb
Submitter: Zuul
Branch:    stable/rocky"
1806451,2018-12-20 15:29:28 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626597"
1806451,2018-12-20 15:21:22 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626595"
1806451,2018-12-20 05:25:11 UTC,"Reviewed:  https://review.openstack.org/621661
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=44985bd42d21ce705387c01b188f27711791f51f
Submitter: Zuul
Branch:    master"
1806451,2018-12-03 17:47:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621661"
1806451,2018-12-03 17:48:30 UTC,3) Will be taken care of by https://github.com/ClusterLabs/resource-agents/pull/1272 and https://bugzilla.redhat.com/show_bug.cgi?id=1655655
1806451,2018-12-12 01:08:05 UTC,"Hello Michele,"
1806451,2018-12-03 17:38:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/621660"
1806451,2018-12-14 07:59:03 UTC,"Hello Michele,"
1806451,2018-12-19 15:46:35 UTC,"Reviewed:  https://review.openstack.org/621660
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=34aa23814ed80be7202ae8d92bdae08ad640f861
Submitter: Zuul
Branch:    master"
1806451,2018-12-13 09:11:30 UTC,"No i don't intend n1. I wrote the message and tagged it with 4) in my comment#3:
""""""
There will still be a 4) message:
Dec 03 12:56:27 controller-0 su[244232]: (to rabbitmq) root on none
"""""""
1806457,2019-10-07 00:21:48 UTC,"Thanks for reporting this bug, sorry it's taken this long to respond. Could you confirm if this issue still happening with the current snapd version?"
1806457,2019-10-07 22:50:07 UTC,"I've been informed that all tests should be working correctly with the current snapd version, so this bug will be closed. Please reopen if this problem is still happening."
1806458,2018-12-04 15:51:38 UTC,apport information
1806458,2018-12-04 15:51:39 UTC,apport information
1806458,2018-12-04 15:51:41 UTC,apport information
1806458,2018-12-04 15:51:43 UTC,apport information
1806458,2018-12-04 15:51:44 UTC,apport information
1806458,2018-12-04 15:51:45 UTC,apport information
1806458,2018-12-04 15:51:49 UTC,apport information
1806458,2018-12-04 15:53:39 UTC,again with new kernel and x11 session
1806458,2018-12-05 09:11:17 UTC,"I do not know how to make a kernel bisection.
On my PC in different partitions I have:
Ubuntu xenial
Bionic
Cosmic
Disco with standard kernel
Disco with various kernels: 4.18.0-10 4.18.0-11 4.19.1 4.20rc2 4.20rc3 4.20rc4 4.20rc5
As You can see i have run apport from various kernel with wayland and x11 sessions.
I have random problems with ALL my partitions excluding Xenial.
the problem is i'm not sure if i have the problem because is random, yesterday on 4.20rc5 i had the problem 4 or 5 times in 1 hour, sometimes i have no problem for the whole day."
1806458,2018-12-17 10:48:14 UTC,Would it be possible to try older kernel releases like v4.4.X [1]?
1806458,2018-12-18 13:45:22 UTC,"Last time I had the problem was dec 10 20:08 and I was using Ubuntu 19.04 with kernel 4.20rc5 and network-manager version 1.12.4.
Since then I have not had the problem but I used kernel 4.20rc6 and 4.20rc7 also network-manager has changed to 1.12.6-0ubuntu2 and firefox has been updated too.
If the problem reappears I will do more test.
thanks"
1806458,2018-12-04 15:51:36 UTC,apport information
1806458,2018-12-19 09:04:48 UTC,A stupid question: I'm using mainly Ubuntu Disco; can I install an old kernel like v4.4.X without problems?
1806458,2018-12-19 09:14:49 UTC,It should be fairly safe.
1806458,2019-03-21 09:33:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806458,2019-03-21 10:42:30 UTC,Is this same as LP: #1785171 and #1802691?
1806458,2018-12-05 04:19:25 UTC,"If it's similar to LP: #1785171, would it be possible to do a kernel bisection?"
1806458,2018-12-04 15:51:35 UTC,apport information
1806458,2018-12-04 14:13:18 UTC,apport information
1806458,2018-12-04 14:16:25 UTC,apport information
1806458,2018-12-04 14:13:13 UTC,apport information
1806458,2018-12-04 14:13:14 UTC,apport information
1806458,2018-12-04 14:13:15 UTC,apport information
1806458,2018-12-04 14:20:15 UTC,Same problem with standard kernel.
1806458,2018-12-04 14:13:19 UTC,apport information
1806458,2018-12-04 14:13:20 UTC,apport information
1806458,2018-12-04 14:13:22 UTC,apport information
1806458,2018-12-04 14:13:25 UTC,apport information
1806458,2018-12-04 14:13:17 UTC,apport information
1806458,2018-12-04 14:16:14 UTC,apport information
1806458,2018-12-04 14:16:16 UTC,apport information
1806458,2018-12-04 14:16:17 UTC,apport information
1806458,2018-12-04 14:16:18 UTC,apport information
1806458,2018-12-04 14:16:19 UTC,apport information
1806458,2018-12-04 14:16:21 UTC,apport information
1806458,2018-12-04 14:16:22 UTC,apport information
1806458,2018-12-04 14:16:12 UTC,apport information
1806459,2018-12-08 15:57:55 UTC,"Addendum:
Managed to spell the name of the person, who provided the workaround, incorrectly twice. Therefore let me give the name on more time and this time correctly:
Alberto Garcia"
1806459,2018-12-07 17:38:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806459,2018-12-03 18:48:33 UTC,In the feature please take a look at https://ubuntu-mate.community/t/how-to-report-problems-in-ubuntu-mate/17943 when reporting problems.
1806459,2018-12-08 15:54:07 UTC,"Found this (Debian) thread, which suggests the root cause is the JIT:
""JavaScriptCore JIT compiler crashes in x86"", https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899338"
1806461,2021-02-25 09:24:22 UTC,"Hello, i have also this 'bug', and I found something. If you open Synapse, then you type to search a pdf file so you can see the name of your pdf."
1806466,2019-01-23 16:44:26 UTC,"This message appears no matter what files are in the backup folder, both of them triggers this error:"
1806466,2019-01-23 14:53:28 UTC,Try swapping the files.
1806466,2019-01-23 14:40:30 UTC,"I did that and I thought it was going to work, it was restoring files normally but then this error message appeared:"
1806466,2019-01-23 14:33:55 UTC,"No, move one out of the way and try again."
1806466,2019-01-23 13:46:28 UTC,"Yes, there are two vol46 files. Should I delete one of them?"
1806466,2019-01-20 15:01:58 UTC,"I'm sorry, I'm not much of an expert in this. I did the backup using the backup tool in Ubuntu. I saved the files on Google Drive and it seems that it doesn't have gaps there, maybe it was an error when downloading the files to my computer. The problem is I can't restore the files through Google Drive either even though it seems to have no gaps. This error message appears:"
1806466,2019-01-19 16:25:13 UTC,"It's obvious a lot of difftar files are missing, it starts with vol4 then skips to vol37.  There are a lot of other gaps like that, all fatal."
1806466,2019-01-17 13:52:21 UTC,"Hi, thanks for the reply. Here's the content of the backup folder:"
1806466,2019-01-17 13:36:13 UTC,"It appears that one of the backup volumes is missing, namely #1.  Could you list the contents of the backup location and see if that is the case?"
1806466,2019-01-05 14:44:01 UTC,Switching to a duplicity bug - I think this is on their side.
1806466,2019-01-23 13:21:01 UTC,Please check Google Drive to see if there are two entries for vol46.difftar.gpg.  This has happened before.
1806467,2019-02-14 10:22:43 UTC,"Of course I would like to use the local origin. The two origins serve different purposes. Another workaround is to change the grid temporarily to larger, but that's also tedious. To be clear, do you think this is a bug? You just told what is the ""expected behavior"" but it doesn't seem to work like that. That's natural because the special snapping points are added recently and haven't been used much yet, so no one else have noticed this and apparently it didn't occur to the developer that the percieved behavior is now kind of different."
1806467,2019-02-13 15:12:28 UTC,I go it now.  In this case use should change the grid origin (S hot key) to the snap point.  This way the grid is now referenced from the snap point assuming that is what you want.  You can clear the grid origin using the Z hot key.
1806467,2019-02-13 13:51:35 UTC,"In that case something about the current behavior is against the expected behavior. When the special snapping points are activated the KiCad cursor snaps to them. That's against what you said: ""always snaps to the nearest grid point"". In the situation when I activate the snapping points and set the local origin, the KiCad cursor snaps to a special snapping point but the origin snaps to the nearest grid point."
1806467,2019-02-13 13:19:57 UTC,The expected behavior is that the user origin is set to the KiCad cursor which always snaps to the nearest grid point.  This would require using a modifier key like shift to disable grid snapping temporarily to use the mouse cursor position.
1806467,2019-02-13 08:58:22 UTC,"If my speculation is correct, it sounds simple enough that I might be able to create a patch which can be evaluated and would unambigously show what I mean. But I don't know KiCad code, so I need to know two things:
1. File where is the code which sets the local origin.
2. How to get the location of the KiCad cursor (function and include file)."
1806467,2019-02-13 07:00:13 UTC,I'm sorry that I was still unclear. I still was want different kind of behavior because the percieved behaviour is incosistent. I just meant that the internal working of KiCad is probably logical and consistent. If I'm correct the origin is now always set to the snapping point nearest to the mouse cursor. It should be set to the KiCad cursor.
1806467,2019-02-12 21:26:25 UTC,So it this bug was either fixed or never valid.
1806467,2019-02-12 20:30:33 UTC,"No no, I was confused for a while. Choosing a *large value* for the grid makes it work like I want. Choosing a *small value* makes it behave in an unwanted way."
1806467,2019-02-12 19:11:45 UTC,This report expired. Is there still something unclear? It's easy to reproduce:
1806467,2019-02-12 19:41:15 UTC,Wait a second. Has something changed? I have to test a bit more.
1806467,2018-12-13 10:56:32 UTC,I want to add that I don't see any logic in *not* using the snapping point for the setting the local origin action. If I want to set the origin under the mouse cursor (or to the nearest grid point) and not to snapping point I just don't use Alt to snap. If I use Alt I expect it to have effect for what I'm doing.
1806467,2018-12-03 19:27:29 UTC,"When you say ""User Origin"" do you mean ""Grid Origin"" ?"
1806467,2019-02-12 04:17:37 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1806467,2018-12-03 20:32:17 UTC,"OK, bear with the questions.  Just trying to make sure I understand the issue before spending time to recreate it.  If I don't, then I spend a lot of time trying to figure out what the issue is before learning that I did not understand your report.  So there will be more ""obvious"" question ahead... :)"
1806467,2018-12-03 20:48:38 UTC,"About the name of the origin... in Move Exactly dialog it's ""user origin"" in ""Rotate around..."" combobox list, but Local Origin or Local coordinates origin in Position Relative dialog. I think in the past it was only user origin."
1806467,2018-12-03 21:03:36 UTC,"Yes, that's what the spacebar does."
1806467,2018-12-03 19:44:43 UTC,"No, Grid Origin works. Maybe it's called ""custom origin"" nowadays? Anyways, I said ""...was set with spacebar..."" which should make it obvious."
1806467,2018-12-03 22:12:05 UTC,"I've fixed Move Exactly to use ""local coordinates"" terminology...."
1806467,2018-12-12 17:02:15 UTC,Removing assignment to allow timeout if there are no updates
1806467,2018-12-12 20:00:16 UTC,"Video (in Linux, git b4910658b)"
1806467,2018-12-03 21:23:58 UTC,"Could you add a video or images?  I'm afraid that the Reset Local Coordinates behavior looks to me like it is behaving appropriately, so I'd like to understand better what you are seeing."
1806468,2018-12-03 23:12:23 UTC,"Huh... this reminds me a lot of https://bugs.launchpad.net/swift/+bug/1758710 ... I wonder if the listing_formats middleware isn't getting inserted where we expected it to be inserted? Following https://review.openstack.org/#/c/449394/ the proxy should always be requesting JSON listings, and the listing_formats middleware *should* get placed far enough left in the pipeline that it middlewares like staticweb, dlo, and symlink will always get back JSON..."
1806468,2018-12-04 22:14:04 UTC,"I got a chance to dig into this a bit more, and I think the pipeline auto-insertion code might be getting confused by the fact that there's only one proxy-logging filter in the pipeline. We've expected two for a long while now (since Swift 1.8.0 or so [1]), would you mind adding a second proxy-logging between gatekeeper and healthcheck then trying again?"
1806468,2019-08-23 09:50:27 UTC,"@Bulat, were you able to solve the issue with Tim's suggestion or are you still seeing this issue?"
1806476,2020-12-30 20:12:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806478,2019-08-01 20:22:55 UTC,Patch for this bug.
1806478,2019-09-08 13:26:49 UTC,b0864da4a91d06f99ae3325e45fd9d152d4dfd7b
1806479,2018-12-06 21:39:08 UTC,The procedure is something like this:
1806479,2018-12-05 17:35:53 UTC,"Juhani Numminen,"
1806479,2018-12-10 08:45:02 UTC,Juhani Numminen
1806479,2018-12-04 19:39:29 UTC,Regarding the first error that you mention:
1806479,2018-12-03 21:00:09 UTC,This change was made by a bot.
1806479,2018-12-05 17:33:57 UTC,"You tell me to ""So please disable that software source"". I am a Linux
newbie. How do I do that?"
1806485,2018-12-06 22:47:51 UTC,This also becomes a problem if you set allowed_recursion_nets with allowed_nets blank and without including the dns-backend space network in the allowed_recursion_nets.
1806485,2018-12-07 21:58:11 UTC,"Actually, it seems a bad practice to set the dns-backend network into allowed_recursion_nets, as it helps exhibit this bug:  https://bugs.launchpad.net/charm-designate/+bug/1807464"
1806485,2020-05-26 12:13:12 UTC,Subscribing field-high as this is a recurring issue in the field
1806485,2020-06-22 22:03:28 UTC,"Please correct me if I am misunderstanding, but this is entirely workable with specific set of charm config to match the deployment topology, and the ask is basically an improvement request -- to make it easier/more automatic or less error-prone."
1806485,2020-07-21 08:18:56 UTC,I raised a review to include the CIDR for the dns-backend binding but that's not actually correct - allowed nets needs to include the IP addresses of the designate servers - there is no guarantee that they will be in the same CIDR as the local unit binding to whatever space is configured.
1806485,2020-07-22 09:40:24 UTC,"Reviewed:  https://review.opendev.org/742092
Committed: https://git.openstack.org/cgit/openstack/charm-designate-bind/commit/?id=57d034b7299375bba294dad194292cf5a3722dd6
Submitter: Zuul
Branch:    master"
1806494,2018-12-04 16:50:06 UTC,I can confirm this issue. Tested in 3.1.2
1806495,2019-01-04 17:45:17 UTC,"Reviewed:  https://review.openstack.org/625915
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=dd975856144bb2c8bfd1a97a0e38e96d7e871763
Submitter: Zuul
Branch:    master"
1806495,2018-12-18 13:48:04 UTC,The same task can also fail with another error:
1806495,2018-12-18 13:46:59 UTC,Please check https://review.openstack.org/625915 which should allow us to track its failure with elastic-recheck.
1806495,2018-12-18 13:45:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625915"
1806495,2018-12-18 13:24:20 UTC,This task can fail with other errors like the one from http://logs.openstack.org/21/625621/2/check/tripleo-ci-centos-7-containers-multinode-queens/56b19bf/job-output.txt.gz
1806497,2019-01-28 20:56:08 UTC,http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2018-12-03.log.html#t2018-12-03T22:41:39
1806499,2018-12-04 09:22:40 UTC,The issue was mentioned also on https://bugzilla.gnome.org/show_bug.cgi?id=789490
1806499,2020-06-26 07:51:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806504,2019-10-15 04:17:21 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1806504,2019-04-26 21:15:26 UTC,"Hi, you may want to look at some additional documentation on using merge-how here:"
1806504,2018-12-23 01:17:16 UTC,"Hi Andres:
Sorry for the delayed response. Had some busy days."
1806504,2018-12-07 06:26:29 UTC,"Thanks for your reply Anastasia! I was just trying to understand your
conclusion provided that it still remains unclear to me how is he trying to
customize the user_data when using Juju."
1806504,2018-12-07 05:34:42 UTC,"@Andres Rodriguez (andreserl),"
1806504,2018-12-04 09:13:57 UTC,Thanks for you reply Dmitrii. Is there any chance to solve it in MAAS layer? Wandering how Juju runcmd overwrites runcmd defined under cloud.cfg.d/ ? I believe this is a feature supported by cloudinit instead of Juju?
1806504,2018-12-07 04:05:05 UTC,Adding cloud-init and MAAS as projects to this report and marking as Invalid for Juju since Juju operates as expected.
1806504,2018-12-04 09:16:12 UTC,"Thanks for your reply Dmitrii. Is there any chance to solve it in MAAS layer instead of using preruncmd supported by Juju? Wandering how Juju runcmd overwrites runcmd defined under cloud.cfg.d/, this should be a feature supported by cloudinit instead of Juju, right?"
1806504,2018-12-04 06:00:38 UTC,Try using cloudinit-userdata model-config:
1806504,2018-12-04 03:40:10 UTC,"Could you guys please help figure out the overwriting rules used in juju user-data?
I tested `write_files` section defined under cloud.cfg.d/ is not override by juju user-data.
Currently I use `write_files` to write my scripts into `/var/lib/cloud/instance/scripts/part-001` to customize juju deployed machine. But it's hack and not straight forward."
1806504,2018-12-07 04:33:25 UTC,"Hi all,"
1806505,2018-12-07 14:35:38 UTC,"tl;dr they get removed from the configuration file on disk, however they persist in the corosync messaging state until manually purged right now.  I've seen this in our QA deployment as well when we've been moving services around for the control plane.  Functionally there should be no impact however it is a bit ugly."
1806505,2018-12-07 14:37:13 UTC,The charm hook code should only be writing out the current nodes in the node list into /etc/corosync/corosync.conf.
1806509,2018-12-05 12:05:26 UTC,"Hi,"
1806509,2018-12-05 19:39:20 UTC,"...would it make sense to link to this reason why(eg some maintainers in other projects actually do use it) in the error message, rather than just warning about it?  Would a more descriptive warning message make sense so the next guy doesn't submit the same patch?"
1806510,2020-01-30 22:19:04 UTC,adding this:
1806510,2020-01-30 22:13:51 UTC,I've installed guacamole on current 18.04.3 LTS and failed to get it working.
1806510,2019-09-25 17:05:35 UTC,bump
1806510,2019-02-07 12:10:15 UTC,"Hi Anthony Godshall,"
1806510,2019-02-06 17:50:09 UTC,Thanks Andrey.
1806510,2019-01-25 23:35:53 UTC,Hi Hans.
1806510,2019-01-25 23:39:55 UTC,Hi again Hans.
1806510,2019-01-13 09:29:56 UTC,Marking as confirmed since others experience the same issue.
1806510,2018-12-04 00:44:47 UTC,"OK, this bug report is about gaucamole, guacd, and guacamole-tomcat."
1806510,2018-12-04 20:59:59 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1806510,2018-12-06 00:31:57 UTC,"> I'm somewhat curious why your listing seems to still include the
> guacamole-tomcat package and being version 0.8.3-1.2, when the bionic
> repositories offer 0.9.9+dfsg-1. Looks like you might have some of the
> older package versions which might be causing issues.
"
1806510,2019-01-14 09:51:01 UTC,A correction to my previous post:
1806510,2018-12-18 16:56:23 UTC,Could you add some more details on where you found the log message on missing guacamole.war?
1806510,2019-01-11 18:26:14 UTC,"Hello,"
1806510,2018-12-09 04:17:52 UTC,correction below
1806511,2018-12-04 02:28:09 UTC,Looks like a bug in the toolkit FreeCAD uses for text rendering.
1806511,2018-12-04 03:46:50 UTC,"Hello James,"
1806511,2018-12-04 05:14:01 UTC,"Thanks for the notification.
I'm a happy user of FreeCAD and was shocked at the screen display under
Ubuntu 18.10  and a bit worried about what was going on."
1806514,2018-12-04 02:00:20 UTC,"The second error message is when specifying the exact path in the script like this:
lo_proc = subprocess.Popen(shlex.split(""/snap/libreoffice/current/lib/libreoffice/program/soffice --accept=\""socket,host=localhost,port=2002;urp;\"" --norestore --nologo --nodefault""))"
1806515,2019-04-26 17:16:24 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1806515,2019-03-24 23:04:45 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1806515,2019-02-07 16:09:00 UTC,"Reviewed:  https://review.openstack.org/624824
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fa178ed4e5ab925d39f7176d851d3c735e328189
Submitter: Zuul
Branch:    stable/queens"
1806515,2018-12-19 10:01:17 UTC,This issue was fixed in the openstack/nova 18.1.0 release.
1806515,2019-03-26 04:02:10 UTC,"Reviewed:  https://review.openstack.org/624825
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=02c6e1364f3cd4fb1cd6d6e7f03a55681a1e364c
Submitter: Zuul
Branch:    stable/pike"
1806515,2018-12-12 22:37:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/624825"
1806515,2018-12-13 17:12:14 UTC,"Reviewed:  https://review.openstack.org/624813
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cbb9eb5b056b96ea507d65fea0e32c27bbf6cdfa
Submitter: Zuul
Branch:    stable/rocky"
1806515,2018-12-04 02:34:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/621856"
1806515,2018-12-12 03:58:33 UTC,"Reviewed:  https://review.openstack.org/621856
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3cd439ad8a99f122566f0b5d0264ff5c8d34f998
Submitter: Zuul
Branch:    master"
1806515,2019-03-22 03:45:27 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1806515,2018-12-12 21:08:42 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/624813"
1806515,2018-12-12 22:21:31 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/624824"
1806523,2018-12-04 23:20:33 UTC,"> hplip-3.16.7.run.
"
1806523,2018-12-05 04:22:14 UTC,"Thanks.
Good information."
1806523,2018-12-04 22:41:52 UTC,hplip-3.16.7.run.
1806523,2018-12-04 19:20:54 UTC,"> ...and your system has a broken printer-driver-postscript-hp package.
> What version is the package?
"
1806523,2018-12-04 16:48:57 UTC,"> Did you look at the list before you sent this? No 402 series is listed
> any more.
"
1806523,2018-12-04 15:35:27 UTC,"Did you look at the list before you sent this? No 402 series is listed
any more."
1806523,2018-12-04 11:53:15 UTC,The Laserjet Pro M402dw PPD is catered for by the Laserjet Pro M402d PPD. It is in the printer-driver-postscript-hp package. There is no need to restore it.
1806523,2018-12-04 05:15:41 UTC,"Hi Joseph,"
1806523,2018-12-04 15:36:23 UTC,"Yes, because my printer was misbehaving."
1806526,2018-12-04 13:13:42 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1806531,2018-12-27 13:44:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806531,2020-01-23 20:23:36 UTC,"Probably dupe of
https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1809579"
1806537,2018-12-04 09:08:51 UTC,Technically that bug doesn't exist in Ubuntu (yet)
1806537,2020-09-14 07:42:41 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1806538,2020-03-21 08:10:13 UTC,Closing because Similar Issue: see https://gitlab.com/inkscape/inbox/-/issues/196 and https://gitlab.com/inkscape/inbox/-/issues/689
1806538,2018-12-06 13:38:07 UTC,"My proposal does not ignore any of that. If you were to change the x0, y0, x1,y1, width or height and then click on custom then you would export whatever was in that custom range. If you want to export the page you just click on page. If you want to export the whole drawing you click drawing. If something is selected and you want to export it, selection would then be available for you to be clicked."
1806538,2018-12-04 11:43:48 UTC,"you are ignoring the fact that the parameters x0, y0, x1, y1, Width, and Height all depend on which choice was made concerning export size. Even the default filename depends on whether you choose ""Drawing"" or ""Selection"".
The normal usage would be to first choose option 'Custom', for example, then choose image size (or possibly dpi in order to see if the file size will be acceptable), then choose ""Export"". Your proposal would not allow this kind of workflow."
1806538,2018-12-08 00:22:35 UTC,"Andrew, I would suggest you join the UX team in Inkscape's chat channel to discuss this issue further. There have been suggestions made that will finally get rid of those number entry fields whose most obvious purpose is to confuse users."
1806543,2018-12-06 19:40:32 UTC,"Hi, it is me who reported this on AskUbuntu about Kubuntu 18.10, and I hereby confirm this bug."
1806543,2019-01-16 03:28:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806543,2019-01-16 03:32:39 UTC,Same issue here... I have the layout pop-up on every login and it never remembers my multi-monitor arrangement.
1806543,2019-02-18 03:22:39 UTC,"I seem to be afflicted with the same issue. Multi-monitor setup, the layout pop-up comes up after login (though it doesn't render properly, I just know to click the rightmost square), left/right displays have to be flipped manually, etc. Kubuntu 18.10, GTX 1060 (using nvidia driver 415.27), i7-860."
1806552,2018-12-08 00:50:13 UTC,#4327 - patch added
1806571,2018-12-17 10:39:47 UTC,Please provide more details.
1806571,2018-12-18 07:45:30 UTC,"Thank you for details.
I think this bug is related to https://bugs.launchpad.net/ceilometer/+bug/1805119"
1806576,2020-07-08 13:16:42 UTC,Running with separate caps for the separate ceph backends reportedly resolves this issue.
1806576,2019-05-10 11:32:12 UTC,"With different caps for manila, ganesha is working."
1806576,2019-05-10 10:41:46 UTC,"In our environment we have three controllers with manila_share containers (kolla) and nfs-ganesha.
Our error looks this same:
http://paste.openstack.org/show/751222/"
1806576,2019-04-03 10:15:54 UTC,@ Duc Xuan:
1806576,2019-02-27 22:41:27 UTC,"I'm sorry to be slow getting to this one but you appear to be running two ganesha servers against the same ceph cluster.  It may be that this can be fixed by setting the cluster up so that each ganesha server is working with a differenet ceph_volume_path (in your configuration they are both set to '/').  In any case, the error we're getting the error from the ceph software itself, not manila code or the manila ceph driver, when there is an attempt to 'stat' the path where by convention a directory would be created for the new share."
1806582,2018-12-06 11:32:59 UTC,"Μια ακόμα χρήσιμη ενέργεια θα είναι το ""Επαναφορά δικαιωμάτων αρχείων"", ώστε να διορθώνονται προβλήματα με λανθασμένα UID/GID ή με εσφαλμένη χρήση sudo."
1806582,2020-07-14 06:10:53 UTC,"Αναφέρθηκε στον νέο bug tracker:
https://gitlab.com/sch-scripts/sch-scripts/-/issues/16"
1806583,2020-07-14 06:12:52 UTC,"Κλείνεται από τον παλιό bug tracker, να δούμε εάν χρειάζεται για να ανοιχτεί στον νέο."
1806602,2018-12-05 20:53:56 UTC,Fixed in x.4324.
1806607,2018-12-04 10:49:17 UTC,maybe using os.path.basename is a more secure thing?
1806623,2018-12-06 03:30:39 UTC,Thanks for that - the query you have used isn't identical to what the shift reports will use to calculate as all dates/times in the database are stored in UTC.
1806623,2018-12-05 08:37:09 UTC,"these two screenshot are for same operator on same day.
Sometimes there is even bigger problem. In call and call_atempt tables are inserted wrong values.
E.g. Call start is yesterday at 19:45 and call end is today at 13:26. So it looks like operator is on call whole night and half of day. In that situation I have to find that call in asterisk database look for real start and end time and update call and call_attempt tables."
1806623,2018-12-05 04:20:45 UTC,Can you locate the call record in the database that is causing this?
1806623,2018-12-05 08:25:34 UTC,"Hi,
here is screenshot of another example."
1806623,2018-12-05 08:26:34 UTC,and here is screenshot of real duration
1806630,2021-02-25 13:26:40 UTC,"Hmm, I'm facing a similar issue if calling 'dpkg-buildpackage -S -d' (that calls again 'dpkg-source') and having a quilt patch in place that modifies debian/* content (i.e. debian/tests/control)."
1806649,2018-12-04 10:48:17 UTC,He does not work with 4.20.0-042000rc5-generic.
1806649,2018-12-04 10:54:44 UTC,"Hello,"
1806649,2018-12-05 19:37:34 UTC,"Hello,"
1806649,2018-12-11 10:57:35 UTC,"Created attachment 279945
dmesg 4.20.0-042000rc6-generic"
1806649,2018-12-11 10:58:18 UTC,Not work with linux 4.20-rc6
1806649,2019-01-07 08:37:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806649,2019-03-11 01:16:39 UTC,Please add driver for wireless RTL8821CE (HP Notebook - 14-df0010nr)
1806649,2019-05-25 10:39:54 UTC,rtl8821ce not work for 5.1 and 5.2 RC1
1806649,2019-05-25 10:42:05 UTC,"Have see this work :
https://github.com/tomaspinho/rtl8821ce"
1806657,2018-12-04 11:15:37 UTC,"Hi Mark,"
1806657,2018-12-04 15:18:02 UTC,"Hi Arthur,"
1806657,2018-12-04 15:25:23 UTC,"I doubt that this bookmark has been created by Xpad.
Xpad is not supposed to create bookmarks. :)"
1806657,2018-12-28 09:04:29 UTC,"Hi Mark,"
1806658,2019-05-08 22:21:23 UTC,Let's create a new task for supporting the store api side (added candy for snapcraft).
1806658,2019-05-07 20:35:54 UTC,https://github.com/snapcore/snapcraft/pull/2559
1806660,2018-12-04 11:13:16 UTC,"Hello,"
1806660,2018-12-05 17:12:13 UTC,It seems that it is a hardware problem.
1806660,2018-12-05 17:12:21 UTC,It seems that it is a hardware problem.
1806660,2018-12-05 17:14:12 UTC,headphone jack.
1806660,2018-12-05 17:14:21 UTC,headphone jack.
1806660,2018-12-12 18:09:35 UTC,I really do not know. In Windows 10 it works well.
1806660,2018-12-12 18:53:15 UTC,"!!################################
!!ALSA Information Script v 0.4.64
!!################################"
1806675,2018-12-20 06:04:40 UTC,The package has been published and the bug is being set to Fix Released
1806676,2018-12-04 12:00:06 UTC,This change was made by a bot.
1806680,2018-12-07 10:20:17 UTC,Contrail Cluster used in this setup was virtualized in VMware environment. It might be a behaviour specific to vmxnet3 paravirtualized NICs.
1806681,2019-12-31 11:16:37 UTC,"I have a new line `hp_wmi: bad event status 0x5` added into my dmesg report everytime when I plug in the charger into my laptop - HP Pavilion 15cb009nu, 5.0.0-37-generic #40~18.04.1-Ubuntu"
1806681,2020-04-22 21:53:19 UTC,HP ProBook 455 G3 (BIOS Version: N80 Ver. 01.45)
1806681,2020-04-22 21:46:48 UTC,"HP ProBook 455 G3
[   18.373200] hp_wmi: query 0x4 returned error 0x5
[   18.377701] hp_wmi: query 0x4 returned error 0x5
[   18.385171] hp_wmi: query 0xd returned error 0x5
[   18.397105] hp_wmi: query 0x1b returned error 0x5"
1806681,2020-03-23 15:36:16 UTC,"Related bug:
https://bugs.launchpad.net/ubuntu/+bug/1841039"
1806681,2020-03-23 15:35:47 UTC,"I support the conclusion by Marcel.
I have HP 450 G6 and brightness up/down generate the same scancode as mic mute."
1806681,2020-03-05 02:54:59 UTC,Any update on this?  I'm currently running into this issue.
1806681,2019-04-19 17:30:44 UTC,"Possibility that this error results in some hotkey combinations (brightness up/down) not working?
The corresponding combinations create no scan code.
And hence there not handled by ACPI maybe it's related to the hp_wmi module?"
1806681,2018-12-04 12:15:04 UTC,"Hello,"
1806681,2019-01-06 09:08:23 UTC,"Hi,"
1806681,2018-12-04 12:45:32 UTC,Most warnings like this are really for the per driver kernel developers.
1806681,2018-12-04 12:43:30 UTC,"If we fill the kernel up with friendly messages it will be massive. It's already got >100,000 kernel messages."
1806681,2018-12-04 12:40:17 UTC,A more friendly message?
1806681,2018-12-04 12:28:47 UTC,"This does not appear to be an error to worry about. The WMI driver for your machine is performing a feature query with the ACPI driver with HPWMI_FEATURE2_QUERY. This seems to be a feature that is enabled on HP WMI firmware from around 2009 onwards. Some machines may support this, however it seems that your firmware does not seem to have support for this, hence the query failure."
1806681,2018-12-04 12:27:49 UTC,"This does not appear to be an error to worry about. The WMI driver for your machine is performing a feature query with the ACPI driver with HPWMI_FEATURE2_QUERY.  This seems to be a feature that is enabled on HP WMI firmware from around 2009 onwards. Some machines may support this, however it seems that your firmware does not seem to have support for this, hence the query failure."
1806681,2018-12-04 12:11:26 UTC,"dmesg 4.20.0-042000rc5-generic:
[   16.320133] hp_wmi: query 0xd returned error 0x5"
1806681,2019-04-19 13:50:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806682,2020-07-15 21:30:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806682,2019-01-10 15:57:09 UTC,"Created attachment 280391
$ LANGUAGE=C grep . /sys/class/thermal/thermal*/*"
1806682,2019-01-10 15:21:51 UTC,"you can attach the out of ""grep . /sys/class/thermal/thermal*/*"""
1806682,2019-01-10 14:16:56 UTC,"> BTW, if you're running into a real overheating issue on this machine,
"
1806682,2019-01-10 13:54:41 UTC,"According to the acpidump, there is no _PSL control method, which is mandatory for a passive trip point.
So, this is a BIOS bug to me, and there is no way to fix it in Linux kernel."
1806682,2018-12-27 16:00:16 UTC,"Created attachment 280155
$ sudo acpidump > acpidump.out"
1806682,2018-12-27 15:55:45 UTC,please attach the acpidump output.
1806682,2018-12-11 11:00:48 UTC,"Created attachment 279947
dmesg 4.20.0-042000rc6-generic"
1806682,2018-12-04 12:24:33 UTC,"Hello,"
1806682,2018-12-04 12:21:32 UTC,"dmesg 4.20.0-042000rc5-generic:
[    1.637619] ACPI: Invalid passive threshold"
1806682,2019-01-10 13:20:33 UTC,"Needs more information? (:
--
Cristian Aravena Romero (caravena)"
1806687,2018-12-04 19:32:48 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1806687,2018-12-05 00:53:05 UTC,"No problem, although availability is part of the CIA triad, and if there is
a problem with certificates, then there could be a problem with
availability."
1806688,2018-12-04 13:30:08 UTC,This change was made by a bot.
1806688,2018-12-17 17:04:20 UTC,"Having reported the problem I wonder how to proceed. Could I:-
1. Simple delete the later, 4.15.0-39 & -42 versions, leaving me space on the /boot partition and perhaps try reloading one of them ?"
1806696,2019-02-09 03:45:19 UTC,"Reviewed:  https://review.openstack.org/633767
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_hosts/commit/?id=3138838ff8f169ae0cf413c459785d5f20306f33
Submitter: Zuul
Branch:    stable/rocky"
1806696,2019-01-29 15:52:02 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/633767"
1806696,2019-01-20 21:46:34 UTC,"Reviewed:  https://review.openstack.org/625998
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_hosts/commit/?id=d0d9384aee36277e899aa664bc9f64835c33d6c4
Submitter: Zuul
Branch:    master"
1806696,2018-12-20 20:30:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/626716"
1806696,2018-12-18 20:05:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625998"
1806696,2018-12-05 13:53:35 UTC,"root@controller-dc1r02n03:~# systemctl show lxc.service |grep ExecStop
ExecStop={ path=/usr/lib/x86_64-linux-gnu/lxc/lxc-containers ; argv[]=/usr/lib/x86_64-linux-gnu/lxc/lxc-containers stop ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }"
1806696,2018-12-20 21:15:03 UTC,"Change abandoned by Justin Alford (<email address hidden>) on branch: master
Review: https://review.openstack.org/626716"
1806697,2019-09-18 11:45:50 UTC,Confirmed in bionic that gnome-software 3.28.1-0ubuntu4.18.04.12 toggling the permissions on the chromium snap keeps correct state.
1806697,2019-12-05 13:02:14 UTC,This bug was fixed in the package gnome-software - 3.20.5-0ubuntu0.16.04.13
1806697,2019-11-27 04:08:31 UTC,Confirmed in xenial that gnome-software 3.20.5-0ubuntu0.16.04.13 toggling the permissions on the chromium snap keeps correct state.
1806697,2019-11-22 09:43:46 UTC,"Hello Efthimios, or anyone else affected,"
1806697,2019-09-24 07:55:04 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.12
1806697,2019-09-24 07:43:52 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu4.19.04.2
1806697,2019-09-24 07:38:51 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1806697,2019-09-17 15:18:14 UTC,"It works, disco"
1806697,2018-12-04 15:51:09 UTC,"I can observe the problem in an up-to-date cosmic VM. The interface is correctly connected, but gnome-software fails to display the switch in the correct state. Killing gnome-software ""fixes"" the problem. So it looks like the status of the permissions are cached in the running instance of gnome-software, and not properly updated when changing them from the UI."
1806697,2019-09-17 13:49:33 UTC,"Hello Efthimios, or anyone else affected,"
1806697,2019-09-17 07:34:26 UTC,It's uploaded and has to go through the Stable Release Update process which normally takes a couple of weeks to complete.
1806697,2019-09-16 15:51:01 UTC,Fix release for disco when?
1806697,2019-06-18 13:11:07 UTC,Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version
1806697,2019-06-17 03:51:25 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu8
1806697,2018-12-05 22:31:54 UTC,I have the same problem: GNOME software does not update the status of the interface.
1806697,2018-12-05 10:22:40 UTC,Added to Trello: https://trello.com/c/SO0NhQKt/174-bug1806697-status-of-interface-connections-not-properly-updated-in-the-ui
1806697,2019-09-17 14:05:59 UTC,"Hello Efthimios, or anyone else affected,"
1806699,2019-03-19 13:33:07 UTC,Is this still an issue?
1806699,2018-12-04 14:18:59 UTC,"There are some rules in the tempest-sendmail api, to avoid spam (since this is an email service). So the same ip was used in several vm's in a small amount of time, if we start to see this with frequency (now that standalone job run faster) I can change the rule on the api."
1806699,2018-12-04 17:08:29 UTC,"Arx, I am not sure how this is implemented but when I tried to make a HTTP request from my own machine I found that 8080 was not open (probably firewalled?)."
1806699,2018-12-04 17:09:43 UTC,The primary issue with current behaviour is that we cannot distinguish between some temporary rate-limting and a total downtime of the sendmail service.
1806701,2018-12-04 15:47:39 UTC,"@Peter,"
1806701,2018-12-04 23:44:12 UTC,"In the case of OVF customization the protection could  work. However, if a user choose to install an OS from the installation ISO image then it could not. In our example we were trying to install a SLES15 OS from its installer DVD attached by virtual CDROM(/dev/sr0)."
1806701,2018-12-05 14:53:24 UTC,"@Peter,"
1806701,2018-12-05 14:54:28 UTC,"well, not *all* we can do, but without adding either a 'mount' or a dependency on something like 'isoinfo'."
1806701,2018-12-06 08:47:30 UTC,Let me check with OVF team internally and update you if we use fixed name for the iso lable.
1806701,2019-02-22 08:18:32 UTC,"Hi Scott,"
1806701,2019-03-05 14:38:42 UTC,"it does seem like that would improve things, pengpeng.  Much better
would be for vmware to promise (at least with new versions) that the
attached OVF cdrom would have a specific label."
1806701,2019-03-06 06:47:48 UTC,"@Scott, agree with you. While I checked the current versions, the Label contains no fixed string. If you attached a VMTools ISO, then LABEL=VMware Tools, TYPE=iso9660.
If you attached a RHEL7.6 installer ISO, then LABEL=RHEL-7.6 Server.x86_64, TYPE=iso9660.
so LABEL depends on what's ISO attached.
We will try to get an official answer from OVF team internally, but the answer could be 'no specific label'."
1806701,2019-04-17 02:16:21 UTC,">Note that commit 530850f971e improves the situation on vmware to
>*not* do the grep if the filesystem has a label 'OVF ENV'. In some recent
>experience I've seen this label provided by vmware.
"
1806701,2019-06-18 09:56:48 UTC,"Post a merge request:
https://code.launchpad.net/~pengpengs/cloud-init/+git/cloud-init/+merge/368959"
1806701,2019-07-16 14:31:20 UTC,"This bug is fixed with commit d9769c47 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=d9769c47"
1806701,2019-07-17 17:12:08 UTC,"This bug is believed to be fixed in cloud-init in version 19.2. If this is still a problem for you, please make a comment and set the state back to New"
1806701,2019-12-16 11:27:33 UTC,"We got recurring problems with cloud-init/ds-identify process. It spawns sub-processes ""blkid -c /dev/null -o export"" which gets stuck in the ""D"" uninterruptible sleep state."
1806701,2019-12-17 03:21:51 UTC,"@Nicklas, I think the /var/run/cloud-init/ds-identify.log is helpful to investigate the problem.
And could you please file a new bug with above log file, it's a different issue with the one in this bug."
1806703,2019-09-13 16:06:19 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1806703,2019-05-16 06:40:55 UTC,"Reviewed:  https://review.opendev.org/622339
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=9bbc1d41d0a9cf8d4605a552e3fceb25c7dc4341
Submitter: Zuul
Branch:    master"
1806707,2018-12-04 14:50:18 UTC,"Hi Vladimir,"
1806707,2018-12-04 17:50:30 UTC,"After the call with team we have identified a root cause: second NIC has been configured not as bridge, but as regular interface - that's why MAAS failed to auto-detect corresponding VLAN."
1806707,2018-12-04 18:04:01 UTC,Note that the work-around for this issue is to use bridge interfaces on the KVM host where you want to attach VM interfaces to.
1806711,2018-12-13 10:07:02 UTC,"Change abandoned by garyk (<email address hidden>) on branch: master
Review: https://review.openstack.org/622207"
1806714,2018-12-05 10:23:22 UTC,The log suggests the issue is a full disk
1806724,2019-09-09 13:45:14 UTC,"Hello, 3.3.3 also has this issue.  We are getting display fields in triplicate because of our synonym dictionaries for numbers and roman numerals."
1806724,2019-04-18 17:00:28 UTC,"Jason, Mike's comment #6 on bug 1822875 is relevant."
1806724,2019-04-18 15:03:53 UTC,"And, nope. Just adding c.active and f.active to the left join criteria doesn't resolve the doubled subjects and content notes issue for me."
1806724,2019-04-18 15:07:03 UTC,"I want to add that I noticed the doubling occurs when the query string is present in the URL.  If you strip out the query=...; part, then the doubling does not occur, at least on our 3.2.4 system.  This suggest, to me, that there may be an alternate way to fix this."
1806724,2018-12-11 18:30:17 UTC,I wonder if the problem that search.best_tsconfig just needs to respect the active flag on the class and field ts_map tables?
1806724,2018-12-06 17:25:03 UTC,NOBLE's fix for both highlighting search terms and avoiding double subject headings is to change search.best_tsconfig to get ts_config's with a weight of 'A' which points to the non-stemmed simple indexes.  The custom dictionary is still weight 'C' so not producing duplicates anymore.  Highlighting is working for the dictionary words although I'm not sure why.  A search for 'no. nine' highlights 'no. 9'. (nine and 9 are in the synonym list).
1806724,2018-12-05 13:35:55 UTC,"Duplicate fields are being caused by additional dictionary definitions in config.metabib_class_ts_map.  NOBLE added a synonym dictionary and applied it to keyword, title, and subject classes with a weight of C.  A new view in 3.1, search.best_tsconfig, retrieves keyword, title, and subject classes twice, once for our synonym ts_config and once for the english_nostop ts_config."
1806724,2018-12-04 21:18:29 UTC,"Regarding the highlighting problem, NOBLE disabled stemming by setting all config.metabib_class_ts_map lines whose ts_config is english_nostop to FALSE.  This results in highlighting of some search terms but not others. For example a search for 'Harry Potter' highlights Potter but not Harry (which stems to harri).  A search for 'oboe' (stems to obo) results in no highlighting."
1806724,2019-04-18 14:57:40 UTC,Martha's suggesting in comment #7 works for us at CW MARS.  We encountered the doubling of some fields in OPAC record summary view after the upgrade.  We disabled search term highlighting because it was behaving inconsistently on our test machine. I guess this bug could explain that.
1806727,2020-07-18 14:00:23 UTC,This bug was fixed in the package eqonomize - 1.4.3-1
1806730,2019-03-16 11:37:48 UTC,"Sorry for the slow response times... I do taxes, and have been swamped."
1806730,2019-05-07 10:17:02 UTC,"Hi Gary,"
1806730,2018-12-21 17:17:39 UTC,using HP Scan:
1806730,2018-12-17 06:12:02 UTC,"Hi Gary,"
1806730,2019-01-18 09:35:07 UTC,Could you try with xsane application.
1806732,2018-12-04 17:00:39 UTC,Also Charm description in the store has to be updated with the guidance how to properly use V3 credentials.
1806735,2018-12-04 17:11:20 UTC,From /etc/network/interfaces (not using systemd networking)
1806735,2018-12-04 17:12:15 UTC,"Note: ""pon dsl-provider"" works after boot"
1806735,2018-12-05 08:59:46 UTC,I've found what looks like a possible cause.
1806738,2019-03-25 00:52:49 UTC,"In my work on https://bugs.launchpad.net/evergreen/+bug/1816475, I added a checkbox to the Booking Pickup screen.  When this is checked, only captured resources can be picked up.  When it is unchecked, uncaptured resources can be picked up too.  It doesn't make a distinction between cataloged and non-cataloged resources, but would this kind of flexibility meet these needs?"
1806738,2019-08-26 20:29:05 UTC,Hi Jane
1806740,2019-09-17 14:38:33 UTC,"@blackketter, please report that in a separate bug report with the version information & steps to treproduce (That seems to be a different issue than not being able to route from the pad)."
1806740,2019-09-17 14:16:19 UTC,"I have found a related behavior where traces routed to castellated pads (starting at a non castellated origin) may be deleted when ""Clean Up Tracks And Vias"" is used with ""Delete Dangling Tracks"".  It doesn't seem to happen all the time, which is a little weird.  Should this be in a separate bug?"
1806740,2019-06-12 12:53:03 UTC,"I find it strange in this post that apparently via's are used for the castellations.
Usually these are in a straight row with regular spacing, and using a (purposely designed) THT footprint seems much more logical to me."
1806740,2019-01-10 05:55:01 UTC,Do we leave this as-is for 5.1?  Any traces starting/ending on the edge will raise DRC errors.
1806740,2018-12-24 16:48:25 UTC,"@Wayne, I agree with Simon. How do we know if a via is a castellation via (without explicitly marking it as such somewhere in the design rules) or just a via that someone placed on the board edge by accident?"
1806740,2018-12-17 19:51:27 UTC,I can understand the router doing this if the castellation via is outside the board edge but the logic should to be changed when the castellation via is bisected by the board edge.
1806740,2019-01-23 14:50:33 UTC,I'll push this to 6 when we can mark the castellation holes properly unless someone can think of a good way to bypass that currently
1806745,2018-12-17 18:20:44 UTC,"Sahil, can you take a look."
1806751,2018-12-04 18:47:35 UTC,that was 18.04 over 16.04
1806751,2018-12-04 19:00:04 UTC,This change was made by a bot.
1806756,2018-12-05 03:19:01 UTC,Nice idea! It might be a bit strange if we generate both names with petname; you'd end up with hosts like:
1806756,2019-09-19 12:07:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1806759,2018-12-04 20:23:07 UTC,typo 18 should be 16.
1806760,2018-12-04 20:46:21 UTC,"Thank you. This falls directly into the work we want to do around an easy to consume health report for Juju controllers, in particular around HA status and mongo status."
1806761,2019-02-15 09:09:35 UTC,Is that fixed now? It seems to work fine here
1806761,2019-01-14 13:04:01 UTC,it should be fixed in that version https://launchpad.net/ubuntu/+source/snapd/2.37+19.04~pre1 (which is also being SRUed to older series)
1806761,2019-01-14 11:34:53 UTC,"$ lsb_release -rdc
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic"
1806761,2018-12-23 00:31:22 UTC,"$ lsb_release -rdc
Description:	Ubuntu Disco Dingo (development branch)
Release:	19.04
Codename:	disco"
1806761,2018-12-14 20:24:13 UTC,"Unfortunately our translator Artem Sierikov translated strings with ""s"" in all versions of snapd(((
For trunk series, Artful, Bionic, Cosmic, Yakkety, Zesty"
1806761,2018-12-14 20:18:14 UTC,"I fixed all strings with ""s"" in
https://translations.launchpad.net/ubuntu/cosmic/+source/snapd/+pots/snappy/ru/+translate"
1806761,2018-12-13 13:59:53 UTC,"All ""<foo>s"" changed to ""<foo>"". In suggestions. Except this one https://translations.launchpad.net/ubuntu/cosmic/+source/snapd/+pots/snappy/ru/34/+translate"
1806761,2018-12-14 20:28:17 UTC,It seems trunk is OK too
1806761,2018-12-13 11:20:52 UTC,I've fixed this in the following PR https://github.com/snapcore/snapd/pull/6305
1806761,2018-12-09 12:21:32 UTC,Confirm. It's irritating.
1806761,2018-12-09 15:57:33 UTC,"Another workaround:
sudo rm /usr/share/locale-langpack/ru/LC_MESSAGES/snappy.mo"
1806761,2018-12-09 16:51:40 UTC,Or use LANG=C before any snap command
1806761,2018-12-13 11:22:03 UTC,Apparently the message
1806761,2018-12-05 11:34:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806761,2018-12-12 08:10:36 UTC,"Also, I can help edit the ru.po file to get success."
1806761,2018-12-12 08:35:52 UTC,"Hm, probably this bug should be moved to snapd bugs. I'm not sure, but looks like..."
1806761,2018-12-12 08:08:12 UTC,"Yep, and use the LANG=C before every apt command, since it uses the snap."
1806762,2019-03-26 16:30:35 UTC,"Reviewed:  https://review.openstack.org/647681
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b7a64a9315a2bfe8c76b4e9b117458530df75e80
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-04-01 05:41:35 UTC,"Reviewed:  https://review.openstack.org/647586
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8877e9f01caf01fa66528afd78f32195d35d3b4a
Submitter: Zuul
Branch:    master"
1806762,2019-03-26 20:14:57 UTC,"Reviewed:  https://review.openstack.org/623323
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d2cc4c83c00256440eed0ed5b8d7131cc02d72d4
Submitter: Zuul
Branch:    master"
1806762,2019-03-26 20:14:06 UTC,"Reviewed:  https://review.openstack.org/647589
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=570e47dbf3c0c24483be94e0d338acbb6dc2f2c9
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 20:13:29 UTC,"Reviewed:  https://review.openstack.org/647552
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=24c875fe76474e3194100f138311a151aa2e6b6d
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 17:00:55 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647815"
1806762,2019-03-26 17:00:37 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/647814"
1806762,2019-04-01 15:21:31 UTC,"Reviewed:  https://review.openstack.org/647553
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=3d3fa99a0503be678d7fe7058fd9220aca70716d
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 16:29:40 UTC,"Reviewed:  https://review.openstack.org/647678
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=1d8ac830a1ed6a571db6987d4ef657cf3e04d640
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 16:30:07 UTC,"Reviewed:  https://review.openstack.org/647679
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=02eebfe5732fb9935331551e223337b22db7aebd
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-04-01 16:54:28 UTC,"Reviewed:  https://review.openstack.org/647587
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=7f257513f87c3eb9fd4aa9d904ed11cef6d9f47c
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 16:29:26 UTC,"Reviewed:  https://review.openstack.org/647677
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=de083009eb51d1af086387bbac0dca8d3c4474c0
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 16:29:13 UTC,"Reviewed:  https://review.openstack.org/647676
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4ccb4c258f54642a272e0d865aa1768b7f1ffee5
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 16:28:58 UTC,"Reviewed:  https://review.openstack.org/647675
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ad108dafe2bdd1b6523d6f45315bb136b9b01408
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 16:28:43 UTC,"Reviewed:  https://review.openstack.org/647674
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0786fde3932e218ef355a6cc958f83c3c7033686
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 16:28:29 UTC,"Reviewed:  https://review.openstack.org/647673
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=fd08266abb3a4fb18ac05921ca11c4768daa2f6d
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 16:30:24 UTC,"Reviewed:  https://review.openstack.org/647680
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=56e48127938be2d67b984d00b155833532233713
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-04-01 17:03:39 UTC,"Reviewed:  https://review.openstack.org/647814
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=db3b293cdea31b5a2b4fab1108d905832ee15550
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-04-03 00:17:16 UTC,"Reviewed:  https://review.openstack.org/622589
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bb141b1fb49c5391530399777586611f2a4b2e6d
Submitter: Zuul
Branch:    master"
1806762,2019-04-02 12:25:33 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/649297"
1806762,2019-10-10 20:52:46 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc2 release candidate.
1806762,2019-10-10 02:26:33 UTC,"Reviewed:  https://review.opendev.org/687639
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d9217f07b83399373c6e0879a71d943b73632ff5
Submitter: Zuul
Branch:    stable/train"
1806762,2019-10-09 17:50:06 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/687639"
1806762,2019-10-04 21:47:11 UTC,"Reviewed:  https://review.opendev.org/682266
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d4a6023de5bdfe5a6e9214579a35e083a45c1151
Submitter: Zuul
Branch:    master"
1806762,2019-09-20 09:35:19 UTC,"Reviewed:  https://review.opendev.org/682503
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8e67249d5bfb07b0a236189f62b3f338532f0df0
Submitter: Zuul
Branch:    master"
1806762,2019-09-15 22:15:48 UTC,"Reviewed:  https://review.opendev.org/680357
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=566f8e734d1b5416305b7ab04c6eda48f40e576b
Submitter: Zuul
Branch:    master"
1806762,2019-09-15 22:15:34 UTC,"Reviewed:  https://review.opendev.org/681162
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6435017c242d759ec18dac30d667f0e196e49f38
Submitter: Zuul
Branch:    master"
1806762,2019-09-15 19:14:49 UTC,"Reviewed:  https://review.opendev.org/667731
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=cf22f8004ed1dba9116c383ae287ad5b4af82dc2
Submitter: Zuul
Branch:    master"
1806762,2019-09-11 04:49:40 UTC,"Reviewed:  https://review.opendev.org/678475
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=704cb2590e2f4496a73a79b3eeb22656083b4081
Submitter: Zuul
Branch:    master"
1806762,2019-09-10 06:30:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/681162"
1806762,2019-09-07 04:05:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680797"
1806762,2019-08-26 07:32:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678475"
1806762,2019-06-26 20:59:16 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/667731"
1806762,2019-04-03 06:18:24 UTC,"Reviewed:  https://review.openstack.org/649344
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c78581b4608f3dc10e945d358963000f284f188a
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 15:12:32 UTC,"Reviewed:  https://review.openstack.org/645890
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ef838a3a3f575562b1fc84623c3a8491d4f2e2f4
Submitter: Zuul
Branch:    master"
1806762,2019-04-02 19:52:35 UTC,"Reviewed:  https://review.openstack.org/649297
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=2c102cad4769c1a6f6713c1379a1760f03ea0172
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-04-02 14:31:54 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/649344"
1806762,2019-04-02 12:02:33 UTC,"Reviewed:  https://review.openstack.org/647815
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=933b7509a4177680158baeeb582f82470f73ae38
Submitter: Zuul
Branch:    stable/stein"
1806762,2019-03-26 10:38:26 UTC,"Reviewed:  https://review.openstack.org/645889
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d1cfa3ab3f87f15f61c5387670d3b75ee2ba93ba
Submitter: Zuul
Branch:    master"
1806762,2019-09-13 15:20:21 UTC,"Reviewed:  https://review.opendev.org/680797
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=afb312529ba1e1eb5acb9598d792f39f5a2500d7
Submitter: Zuul
Branch:    master"
1806762,2019-03-22 04:58:11 UTC,"Reviewed:  https://review.openstack.org/622615
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=465a8bb59be13739253a52d7e457067cf63d3ba8
Submitter: Zuul
Branch:    master"
1806762,2019-01-09 03:16:19 UTC,"Reviewed:  https://review.openstack.org/624215
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b35928d5dcd8615d11c199c68c512aaa1dca4ec9
Submitter: Zuul
Branch:    master"
1806762,2018-12-14 22:02:30 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625357"
1806762,2018-12-14 22:02:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625356"
1806762,2018-12-14 22:02:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625355"
1806762,2018-12-14 22:01:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625354"
1806762,2018-12-14 22:01:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625353"
1806762,2018-12-14 22:01:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625352"
1806762,2018-12-10 22:25:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624220"
1806762,2018-12-10 22:25:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624219"
1806762,2018-12-10 22:24:56 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624218"
1806762,2018-12-10 22:24:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624217"
1806762,2018-12-10 22:24:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624216"
1806762,2018-12-10 22:24:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624215"
1806762,2018-12-06 21:18:26 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623323"
1806762,2018-12-04 22:32:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/622615"
1806762,2018-12-04 20:57:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/622589"
1806762,2019-03-22 21:27:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645889"
1806762,2019-01-09 03:16:31 UTC,"Reviewed:  https://review.openstack.org/624216
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6037ac58de0fe599df9220a068e1ef054194187a
Submitter: Zuul
Branch:    master"
1806762,2019-01-09 03:16:44 UTC,"Reviewed:  https://review.openstack.org/624217
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=718d122fe1595d59b4eab99c3a744bfe34941369
Submitter: Zuul
Branch:    master"
1806762,2018-12-10 22:25:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624222"
1806762,2019-02-28 01:59:30 UTC,"Reviewed:  https://review.openstack.org/625352
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a3c3a62a1287d4af398581ec65549a314b061358
Submitter: Zuul
Branch:    master"
1806762,2019-03-21 19:30:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645311"
1806762,2019-03-21 19:29:54 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645310"
1806762,2019-03-21 19:29:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645309"
1806762,2019-03-21 18:29:35 UTC,"Reviewed:  https://review.openstack.org/624222
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=546b7f1bba0c5a9b9c22828cc27a90191bb8f30d
Submitter: Zuul
Branch:    master"
1806762,2019-03-21 18:29:26 UTC,"Reviewed:  https://review.openstack.org/624220
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=09663a01a4eda4332e55637a120019e1784b967e
Submitter: Zuul
Branch:    master"
1806762,2019-03-21 01:31:40 UTC,"Reviewed:  https://review.openstack.org/624219
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=04dc72a908ce829d7aaf4c62f12d7cd2215812d5
Submitter: Zuul
Branch:    master"
1806762,2019-03-21 01:31:27 UTC,"Reviewed:  https://review.openstack.org/624218
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=65165e7e8b8cb9a18e5815a51ab75f0328d8eab4
Submitter: Zuul
Branch:    master"
1806762,2019-03-20 22:01:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645024"
1806762,2019-03-20 22:00:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645023"
1806762,2019-03-21 19:30:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/645312"
1806762,2019-03-20 22:00:39 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645022"
1806762,2019-03-20 22:00:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645021"
1806762,2019-03-02 03:04:33 UTC,"Reviewed:  https://review.openstack.org/625357
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=24b8db9e064713e7350f83cd77ed197b050b1fe1
Submitter: Zuul
Branch:    master"
1806762,2019-02-28 05:45:40 UTC,"Reviewed:  https://review.openstack.org/625356
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=532b9625de9717a08172de3f7e10a326c812670d
Submitter: Zuul
Branch:    master"
1806762,2019-02-28 05:45:32 UTC,"Reviewed:  https://review.openstack.org/625355
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c7cd4bcd5b5745a335b11e11b91aba0a4acf307a
Submitter: Zuul
Branch:    master"
1806762,2019-02-28 05:45:23 UTC,"Reviewed:  https://review.openstack.org/625354
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=87d93db90950065410e8fcb2866effc96c7153e4
Submitter: Zuul
Branch:    master"
1806762,2019-02-28 04:50:26 UTC,"Reviewed:  https://review.openstack.org/625353
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=85b87fa4795b94d918c88c74c1231468d61f0acc
Submitter: Zuul
Branch:    master"
1806762,2019-02-27 22:01:09 UTC,"Reviewed:  https://review.openstack.org/605876
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=87e50c029e11d412368f0b08b7e65c6796bf1871
Submitter: Zuul
Branch:    master"
1806763,2019-03-26 13:49:56 UTC,"It is a design bug. Adding boot sources and making selections isn't new functionality, and right now, due to an incomplete API, is inherently racy."
1806763,2019-03-20 19:07:54 UTC,subscribed to field-high as this has been hit in the field.
1806763,2019-03-26 02:41:41 UTC,When a new boot-source has been added the sources list is updated in a post-commit hook. Because of this there currently isn't a way to check if the boot-sources list is being updated over the API or UI. There are a couple ways we may be able to fix this I'll have to discuss with the team what the best option is.
1806763,2019-03-26 02:53:11 UTC,"This seems to fall under completely new functionality given that MAAS has
never been able to provide status about accessing/processing the sources."
1806772,2020-08-30 17:24:54 UTC,no GPU information -> Incomplete
1806772,2020-08-30 17:35:08 UTC,"Actually, this seems more like a support request since there's no real information here. Since support requests are not appropriate for a bug tracker, this is invalid. Additionally, this is an ancient bug, and newer versions of Blender may have this fixed."
1806776,2018-12-05 01:07:17 UTC,I believe this was fixed in 2.4. What version of Juju do you have?
1806776,2018-12-05 18:25:25 UTC,Snap installed juju 2.4.7      6012  stable
1806776,2018-12-09 06:35:21 UTC,"Need the juju version of the model, not the client."
1806776,2018-12-09 21:58:01 UTC,"I don't think the juju version of the model matters though, since it's the various shell aliases on the client's end."
1806777,2018-12-12 20:07:52 UTC,"Hello Dan, or anyone else affected,"
1806777,2018-12-12 16:49:01 UTC,Cosmic (modified per comment 4):
1806777,2018-12-12 20:12:50 UTC,"Hello Dan, or anyone else affected,"
1806777,2018-12-19 16:31:41 UTC,This bug was fixed in the package open-iscsi - 2.0.874-5ubuntu2.6
1806777,2018-12-19 16:31:24 UTC,This bug was fixed in the package open-iscsi - 2.0.873+git0.3b4b4500-14ubuntu3.7
1806777,2018-12-19 16:31:29 UTC,"The verification of the Stable Release Update for open-iscsi has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1806777,2018-12-19 16:32:34 UTC,This bug was fixed in the package open-iscsi - 2.0.874-5ubuntu9.3
1806777,2018-12-12 20:29:26 UTC,"verification was done with the previous build, but this code hasn't changed in the subsequent SRU which is a one-character change, so re-marking this verified for bionic and cosmic."
1806777,2018-12-12 15:02:32 UTC,Bionic (modified per comment 4 to replace netplan with ifupdown):
1806777,2018-12-08 21:05:17 UTC,This bug was fixed in the package open-iscsi - 2.0.874-5ubuntu12
1806777,2018-12-11 20:10:43 UTC,"Hello Dan, or anyone else affected,"
1806777,2018-12-11 18:56:44 UTC,"Hello Dan, or anyone else affected,"
1806777,2018-12-11 18:38:01 UTC,"Hello Dan, or anyone else affected,"
1806777,2018-12-05 20:32:16 UTC,Testing on bionic with above ppa:
1806777,2018-12-05 20:21:06 UTC,"ppa with test open-iscsi pkgs
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1806777"
1806777,2018-12-05 20:18:57 UTC,"On bionic iBFT system, I switched to ifupdown:"
1806777,2018-12-05 16:31:59 UTC,Discussed with @smoser and we think this can be fixed in open-iscsi's initramfs local-top script; I am patching and testing now.
1806777,2018-12-04 22:50:30 UTC,"I should note that while I marked this against cloud-init, it may be that something else (e.g. ipconfig as mentioned in the last comment) may need to be changed to fix this."
1806777,2018-12-04 22:45:14 UTC,It seems the option to restore cloud-init functionality to setting the iscsi root device interface to ifupdown 'auto' dhcp would lead back to the hang-on-shutdown.
1806777,2018-12-12 14:47:02 UTC,Xenial:
1806778,2018-12-05 02:56:31 UTC,"On Tue, Dec 4, 2018, 18:10 Robie Basak <<email address hidden> wrote:"
1806778,2018-12-04 23:29:16 UTC,"Yes, this is the design. Configuring lxd is outside the scope of
git-ubuntu. We could add a dependency on an interface provided by the lxd
snap. But it makes no sense to package lxd ourselves."
1806778,2018-12-04 22:41:49 UTC,"ubuntu@rbasak-gu-test:~$ snap run --shell git-ubuntu.self-test
ubuntu@rbasak-gu-test:~$ lxc
Command 'lxc' is available in '/usr/bin/lxc'
The command could not be located because '/usr/bin' is not included in the PATH environment variable.
lxc: command not found"
1806778,2018-12-04 23:56:55 UTC,"Thanks. What bothers me is that the classic snap (in my understanding)
should run anywhere snaps can run, with the ""classicness"" being for the
purposes of git-ubuntu being able to get to the user's git repository it
is to act upon only. AIUI, any reliance on any other thing on the host
system is a bug in the snap."
1806780,2019-10-31 21:21:24 UTC,Confirmed in 3.3.4
1806783,2019-03-07 18:00:31 UTC,My fix here:
1806783,2019-10-23 13:41:50 UTC,"Working in PINES production for some time and I see it working on current master.  Pushed to master, rel_3_3 and rel_3_4.  Thanks, Terran!"
1806784,2018-12-06 09:42:03 UTC,"sqlalchemy docs for reference on ""SELECT 1"":"
1806784,2019-03-14 07:18:22 UTC,Appears that the impacted deployments have the wait-timeout option configured to 180 seconds which means that there is an inconsistency between what oslo is expecting (3600 seconds) vs what PXC is doing (180 seconds) which would explain why this error is seen.
1806784,2019-02-25 19:24:21 UTC,This bug affects a project where all timeouts are commented out in designate units:
1806784,2018-12-06 09:29:55 UTC,The default in percona-cluster should be 28800 for termination of idle connections.
1806784,2020-05-19 22:47:11 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/729414"
1806784,2018-12-06 09:27:51 UTC,Configuration option switched from idle_timeout to connection_recycle_timeout at queens.
1806784,2018-12-06 09:24:13 UTC,Note that this is not service impacting - the query being run is the connection checker query used to validate a connection before its released from the connection pool; it will be discarded and a new connection created.
1806784,2018-12-06 09:21:52 UTC,I just de-duped three other bugs related to this against this bug report;  it would appear that we have a mismatch between the 'idle_timeout' set in openstack servers vs the idle timeout in mysql which results in this type of error message in the openstack service logs.
1806784,2018-12-04 23:43:04 UTC,The juju-crashdump is available at https://oil-jenkins.canonical.com/artifacts/425288fd-dc94-439a-80a9-896c9b955a99/generated/openstack/juju-crashdump-openstack-2018-12-04-00.20.10.tar.gz
1806784,2018-12-06 09:28:06 UTC,(it defaults to 3600 which is fairly sane).
1806786,2018-12-11 20:11:14 UTC,Confirmed for version 3.2.1
1806787,2019-11-24 19:32:31 UTC,"This issue is now fixed and addressed: when clicking on 'import sheet pin, it automatically includes the next hierarchical label."
1806787,2019-11-24 19:33:26 UTC,"To clarify, it looks like it was fixed by this eeschema version"
1806787,2019-11-24 22:21:24 UTC,Thanks for reporting back.
1806797,2018-12-05 02:41:41 UTC,"Does the problem only occur in Xorg sessions (the ""Ubuntu"" login option)? Or does it also occur in ""Ubuntu on Wayland"" sessions?"
1806797,2018-12-05 03:25:04 UTC,I don't use Wayland.
1806797,2018-12-05 03:32:26 UTC,"Please test ""Ubuntu on Wayland"" so that we can see if the problem is in code that's common to both."
1806797,2018-12-16 20:24:19 UTC,"When I try `Ubuntu on Wayland`, the behavior is, indeed, different.
After disconnecting HDMI, the system never suspends (so I cannot reproduce the problematic behavior), even when I close the lid.
However, `tmux` hangs and loadavg stays at 1.
After I `kill -9` tmux and force suspend using the power button, I can login fine."
1806797,2019-07-22 04:16:15 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1806804,2019-08-17 07:04:47 UTC,"same problem here, testing the workarround"
1806804,2019-08-17 07:04:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806804,2018-12-05 07:52:47 UTC,"should be a bug in nvidia then, if it doesn't restore then on uninstall?"
1806804,2018-12-05 03:26:51 UTC,Workaround:
1806804,2019-03-05 10:28:24 UTC,this is a bug in nvidia-340 which doesn't update the links on remove
1806810,2018-12-08 00:17:12 UTC,"For a workaround, see https://inkscape.org/release/inkscape-0.92.3/gnulinux/snap/dl/"
1806815,2019-04-26 20:54:51 UTC,"Hi Tyler,"
1806815,2019-05-22 12:43:38 UTC,"I can indeed get ""Always snap"" to snap to grid lines (not intersections) although, in a pretty edgecase scenario. I reckon this is because snapping is probably related to the screen size (i.e. zoom factor) and the threshold is high enough that it snaps to the intersections in most sensible cases."
1806815,2019-05-23 20:27:04 UTC,"Yes, the snapping distance is measured in screen pixels. Inkscape prefers fully constrained snaps (in both X and Y, i.e. snapping to a point) over partly constrained snaps (i.e. to a line, where one degree of freedom is still remaining). That's why it is difficult to snap to grid lines, if you want to avoid snapping to grid intersections. This ""always snap"" also works with guides though, which is easier to demonstrate."
1806823,2020-10-29 08:21:58 UTC,Thanks - This is upstream and will be in qemu v5.2 and therefore revisited when we merge that (December/January).
1806823,2021-02-12 08:30:49 UTC,"------- Comment From <email address hidden> 2021-02-12 03:26 EDT-------
IBM Bugzilla status->closed, Fix Release with hirsuite"
1806823,2021-01-27 10:58:42 UTC,"IMHO - the case isn't common and thereby not too important for an SRU. But I'm open to be convinced otherwise if you think it should go to Focal/Groovy as well.
If you want to do so I'd recommend outlining a use-case which isn't a corner case, and usually will be affected by it.
So far only the full series was outlined, for the SRU - as usual - we'd want to limit the changes to just what is needed for that - it would help if you could point to the smallest subset achieving that."
1806823,2021-01-27 10:51:22 UTC,"Hi Heinz, sorry 5.2 is merged in Hirsute already for a while, missed this bug in the update mania."
1806823,2021-01-27 09:40:26 UTC,"------- Comment From <email address hidden> 2021-01-27 04:27 EDT-------
@Canonical, any update available?"
1806823,2020-10-08 13:39:46 UTC,"------- Comment From <email address hidden> 2020-10-08 09:34 EDT-------
Patch set is upstream.
https://git.qemu.org/?p=qemu.git;a=commit;h=6eeea6725a70e6fcb5abba0764496bdab07ddfb3"
1806823,2020-10-07 05:59:47 UTC,"------- Comment From <email address hidden> 2020-10-07 01:53 EDT-------
this is fixed by the following series:"
1806823,2020-10-08 08:48:18 UTC,Thank you Thomas and Frank - yeah pulling this in in 21.04 then
1806823,2019-06-03 14:44:44 UTC,Setting to Incomplete for now until it gets addressed.
1806823,2020-04-23 20:10:45 UTC,@christian please open an upstream bug report about this?
1806823,2019-01-09 09:10:03 UTC,"------- Comment From <email address hidden> 2019-01-09 04:03 EDT-------
This is certainly something where we can improve the heuristics to guess the right boot device, but it is low priority and severity. It will not happen with libivrt and it will not happen when the user specifies a boot priority.
Reducing severity."
1806823,2020-06-24 04:17:16 UTC,[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]
1806823,2020-04-24 05:42:13 UTC,"Hi xnox,
this is IBM owned code, so by mirroring it to them (which already happened quite a while ago) it is where it needs to be. IMHO there is no need to also track a bugzilla on it without further gain."
1806825,2018-12-05 07:31:19 UTC,"I have eliminated the startup error messages by using synaptic package manager to install the following packages and their dependencies.  However, the ""Action"" and ""Tools"" menus still are not working."
1806825,2018-12-05 07:34:01 UTC,I also used synaptic package manager to install the following nepomuk packages but I am not sure they are necessary.
1806841,2019-01-16 09:35:07 UTC,"The issue happens because you've tried to paste unicode characters (in that case, the ""┌───"" characters that surrounds the different text fields)."
1806843,2018-12-05 09:41:41 UTC,The log shows it's trying to install grub on /dev/nvme0n1p4 but hits a full disk issue
1806843,2018-12-05 13:15:10 UTC,"So you mean 400 mb disk is not enough for grub...
Thats really strange."
1806843,2018-12-05 13:22:11 UTC,The log has
1806843,2018-12-06 07:20:28 UTC,"Yes, i can reproduce it every time.
And i'am already reproduce it with ubuntu 16.04 and 18.04.
More then 4 times."
1806843,2018-12-07 08:49:38 UTC,"Today i try one more time. Try install Ubuntu to windows boot manager uefi(500mb fat32, eps + boot flag) partition. and Remove second uefi(400mb fat32, eps + boot flag).
It's not help."
1806843,2018-12-07 13:14:25 UTC,"Issue was fixed after full reinstall of very thing.
Recreate GPT tables,
Reinstall windows 10
Reinstall all drivers for bios
and then repartion disk : add two additional partion for ubuntu uefi and ext4.
And ubuntu was successfully installed.
Have no idea where problem appeared previously."
1806843,2018-12-05 10:04:53 UTC,"I;am sorry i can't understand how it's possible.
I have 1 nvme disk for 500gb with
2 uefi boot sector by 400mb
nvme0n1p4 - fat32 with uefi for ubunru
nvme0n1p2 - was created before my installation with windows MBR.
nvme0n1p6 - ext4  250gb for ubuntu
nvme0n1p3 - ntfs near 240gb that was created with widnows."
1806845,2019-02-12 14:11:22 UTC,"@qanxian,"
1806845,2019-02-13 02:09:34 UTC,I have changed it to public. I don't find why I change it to private. Sorry.
1806845,2019-02-12 14:43:44 UTC,This can be made public bug.
1806845,2019-02-12 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1806845,2018-12-06 08:22:42 UTC,"Here're the reproduce steps of this issue, also attached the errors in dmesg log which were triggered by this issue."
1806845,2018-12-05 16:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1806845,2018-12-05 08:22:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1806845,2018-12-13 09:31:21 UTC,"I think we need to apply the entire series as one. So I guess we need all these commits?
5907cf6c5bbe78be2ed18b875b316c6028b20634 i40e: Prevent deleting MAC address from VF when set by PF
babbcc60040abfb7a9e3caa1c58fe182ae73762a i40evf: cancel workqueue sync for adminq when a VF is removed
5cba17b14182696d6bb0ec83a1d087933f252241 i40e: hold the rtnl lock on clearing interrupt scheme
3bd77e2ae1477d6f87fc3f542c737119d5decf9f i40evf: Don't enable vlan stripping when rx offload is turned on
e78d9a39fd06109022d11c8ca444cfcec2abb290 i40e: Check and correct speed values for link on open"
1806848,2018-12-06 10:41:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1806850,2019-02-14 13:08:00 UTC,This bug was fixed in the package linux-oem - 4.15.0-1033.38
1806850,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1806850,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1806850,2018-12-20 05:39:13 UTC,This bug was fixed in the package linux-oem - 4.15.0-1030.35
1806850,2018-12-12 02:15:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1806850,2018-12-05 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1806850,2019-01-15 10:33:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1806852,2018-12-06 07:23:38 UTC,"Seems like proprietary Nvidia driver is not there for your graphics card:
Kernel modules: nvidiafb, nouveau"
1806852,2018-12-05 17:31:23 UTC,"I hope that the report made by ""apport-collect 1806852"" is complete because the screen has become illegible during operation.
thank you"
1806852,2018-12-05 17:05:31 UTC,apport information
1806852,2018-12-05 17:05:29 UTC,apport information
1806852,2018-12-05 17:05:26 UTC,apport information
1806852,2018-12-05 17:05:24 UTC,apport information
1806852,2018-12-05 17:05:23 UTC,apport information
1806852,2018-12-05 17:05:21 UTC,apport information
1806852,2018-12-05 17:05:19 UTC,apport information
1806852,2018-12-05 17:05:18 UTC,apport information
1806852,2018-12-05 17:05:17 UTC,apport information
1806852,2018-12-05 17:05:15 UTC,apport information
1806852,2018-12-05 17:05:14 UTC,apport information
1806852,2018-12-05 11:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1806852,2018-12-05 17:05:22 UTC,apport information
1806860,2018-12-10 12:55:10 UTC,Thanks!
1806860,2018-12-10 11:12:18 UTC,Reported as suggested : https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604
1806860,2018-12-10 02:41:09 UTC,Please complete step 2 in comment 1.
1806860,2018-12-06 09:25:00 UTC,apport information
1806860,2018-12-06 09:24:58 UTC,apport information
1806860,2019-06-11 12:37:37 UTC,"The reported commented upstream 'Does not seem to occur with ubuntu 19.04 any longer.', closing the bug"
1806860,2018-12-06 09:24:56 UTC,apport information
1806860,2018-12-06 09:24:54 UTC,apport information
1806860,2018-12-06 09:24:53 UTC,apport information
1806860,2018-12-06 09:24:52 UTC,apport information
1806860,2018-12-06 01:51:26 UTC,Please:
1806860,2018-12-06 09:24:57 UTC,apport information
1806864,2018-12-06 19:12:33 UTC,https://github.com/juju/juju/pull/9543
1806869,2018-12-07 07:33:14 UTC,"Ah, I see, its the complete ANSI spec. Yes, way more complex. Always learning something new..."
1806869,2018-12-06 11:53:04 UTC,"Correct, VTE ist 0.54.2. About the brightness, it is definitely the case that the bright colors are used (which can be seen by changing these)."
1806869,2018-12-06 10:32:09 UTC,VTE developer here. VTE is the terminal emulation widget used by Terminator.
1806869,2018-12-06 14:16:00 UTC,"> According to [...] a ""1"" can only mean bold.
"
1806870,2018-12-05 12:26:11 UTC,Here is the patch in a file format (you should have better indentation)
1806870,2018-12-14 09:40:46 UTC,"Dear Olivier,"
1806870,2018-12-14 09:54:27 UTC,"Hi,"
1806870,2018-12-14 10:26:08 UTC,yes please find the attached.
1806870,2018-12-14 14:49:45 UTC,"Hi,"
1806896,2019-09-06 09:18:31 UTC,"In case this helps someone, I modified the current master files to clean up a few things and allow for nvme drives to be used.  Not much has changed over the past year or so, so the master version was plenty good.  We use Rocky currently and these changes work fine.  I have only tested a bluestore deployment, where we have both SATA SSDs and HDDs, and now NVMe SSDs (all assigned to their respective Ceph device classes)."
1806896,2019-10-21 09:08:56 UTC,Addressed in this PR: https://review.opendev.org/#/c/688328
1806898,2019-06-29 04:17:29 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1806898,2018-12-13 15:56:27 UTC,"Hi.
the cloud-init.log file shows some interesting bits.
I think the source of the issue is cloud-init trying to use dhclient to bring up a dhcp connection and not being allowed to execute it.  I suspect /var/tmp/ is mounted without execute permissions."
1806898,2018-12-08 15:57:27 UTC,any ideas what's going on here?
1806898,2018-12-05 13:10:07 UTC,"Other context: I have an ASG where I launch 25 instances, and this issue occurs in 1-2 of them per test.  The remaining 20ish instances launch and run their user-data without issue."
1806902,2018-12-06 18:11:09 UTC,"I installed xfwm4 version 4.13.1-1~18.10 with the PPA you provided, then I rebooted.
The behavior is much worse : when I maximize, the window fill only 1/4 of the screen. (top-left quarter of screen) (and still overlaps behind deskbar :)
XFCE is considered upstream source ?"
1806902,2018-12-07 10:57:29 UTC,"Yes, the source code is maintained by the upstream developers."
1806902,2018-12-07 11:21:20 UTC,"Ok thanks for the clarification.
I thought xfwm was a separate project."
1806902,2018-12-06 11:09:28 UTC,Please test with xfwm 4.13.x from the Xubuntu QA Experimental PPA:
1806912,2020-06-09 15:31:27 UTC,Hit this issue:
1806912,2019-04-23 14:22:08 UTC,"(9:10:04 AM) frickler: mriedem: humm, devstack is being run twice it seems. see the successful end of the first run here http://logs.openstack.org/67/648867/8/check/openstacksdk-functional-devstack/e155792/job-output.txt.gz#_2019-04-23_05_00_55_349794 and then the log of the second run in  http://logs.openstack.org/67/648867/8/check/openstacksdk-functional-devstack/e155792/controller/logs/devstacklog.txt.gz"
1806912,2019-04-23 13:52:43 UTC,Looks like it could be a problem with misconfigured ports:
1806912,2019-04-23 13:22:17 UTC,"Looking at logstash today for the past 10 days this hits predominantly in vexxhost-sjc1 nodes, but I'm not sure how that might be related."
1806912,2019-07-09 06:27:56 UTC,I'm also getting the same issue. I'm installing from stable/stein branch in Ubuntu 18.04. Could you please help me on how to resolve this issue.
1806912,2018-12-17 22:25:46 UTC,"g-api seems to be dead before devstack starts hitting it, and looking at the rabbit logs there are errors about the time the g-api logs stop:"
1806912,2018-12-17 22:18:40 UTC,"Looking at one of the failures, g-api starts in ~3 seconds:"
1806912,2018-12-17 22:05:48 UTC,"Now that bug 1807219 and bug 1807044 are closed in nova, it looks like the hits for this now are coming from glance-api."
1806912,2018-12-06 18:52:24 UTC,A few things which might help:
1806912,2018-12-17 22:32:53 UTC,"In this case, something very weird is happening because g-api is started twice:"
1806913,2018-12-05 17:36:14 UTC,"This looks similar to https://github.com/ubuntu/snapcraft-desktop-helpers/issues/152, but I cannot observe the problem in a clean and up-to-date 18.04 VM, even when using ibus (with ibus-pinyin)."
1806913,2018-12-06 11:26:16 UTC,https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806913/comments/1
1806914,2018-12-09 21:22:22 UTC,apport information
1806914,2018-12-16 12:05:25 UTC,This trouble arises when trying to update initramfs from the isofile (ubuntu-18.04.1-desktop-amd64.iso) as soon as ubiquity terminates the installation.
1806914,2018-12-09 21:22:32 UTC,apport information
1806914,2018-12-09 21:22:29 UTC,apport information
1806914,2018-12-09 21:22:25 UTC,apport information
1806914,2018-12-09 21:22:24 UTC,apport information
1806914,2018-12-09 21:22:21 UTC,apport information
1806914,2018-12-09 21:22:14 UTC,apport information
1806914,2018-12-09 21:22:19 UTC,apport information
1806914,2018-12-09 21:22:17 UTC,apport information
1806914,2018-12-09 21:22:16 UTC,apport information
1806914,2018-12-09 21:22:15 UTC,apport information
1806914,2018-12-09 21:22:11 UTC,apport information
1806914,2018-12-05 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1806914,2018-12-09 21:22:20 UTC,apport information
1806914,2018-12-09 21:22:12 UTC,apport information
1806947,2018-12-05 15:30:06 UTC,This change was made by a bot.
1806947,2018-12-10 09:08:34 UTC,"The issue is fixed by the latest kernel update:
(which my machine received by auto-update today)"
1806947,2019-08-22 09:40:59 UTC,Close this bug per #3.
1806953,2018-12-06 11:48:38 UTC,vrouter dpdk agnet logs
1806953,2018-12-06 11:03:47 UTC,Diagram
1806956,2019-01-02 16:46:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806957,2019-05-14 21:47:07 UTC,What is the current status on this bug?
1806957,2018-12-18 12:20:11 UTC,This is fixed in 13.1 (due to be released). 13.0 never had this feature published.
1806961,2018-12-07 14:17:33 UTC,"Yes, making it public is okay with me"
1806961,2018-12-07 14:06:52 UTC,"Thanks for reporting it to upstream.
LightDM and light-locker for Ubuntu 18.04 are in universe, which is community
maintained. So there's nothing else that we can do.
I would appreciate with you continue to coordinate with upstream and if there's
a new fixed version of any of the packages feel free to inform here in this
ticket and to post a debdiff to this issue.
Whenever a community user posts a debdiff for a universe package, we members of
the security team will review it and publish the package. For more information
see: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1806961,2018-12-07 01:03:02 UTC,"But in the meantime, don't you think that there should be a warning when using lightdm because it is impossible to use it securely?"
1806961,2018-12-06 20:37:17 UTC,"Yep, I was able to reproduce here, and it seems like light-locker is not working well with the current version of Gnome (or LightDM) on bionic. My suggestion is that you create a bug on light-locker's github page and try to get some feedback from them. My other suggestion is to install another screen locker if you still want to use LightDM (apt search screen lock ... should give you a pair of tools available). If LightDM is not really a necessity, then perhaps you stick with GDM+Gnome (GNOME DE). There's not much else that we can do from our side, this needs to be taken care by upstream developers in any of the projects (LightDM or light-locker).
Thanks for trying it and helping investigate. If you run into any other problems feel free to report to us in a new bug"
1806961,2018-12-06 18:00:29 UTC,"Running the gsettings commands and then light-locker does not help, it gives the same output still."
1806961,2018-12-06 16:34:44 UTC,Can you please try the following?
1806961,2018-12-06 15:53:34 UTC,"Yes, i have rebooted, and i ran the commands again, and still it gives the same output, and the exploit persists."
1806961,2018-12-06 15:24:58 UTC,"Just a quick check, did you reboot after creating the file ~/.config/autostart/org.gnome.SettingsDaemon.ScreensaverProxy.desktop ? Because it looks like it is still running the ScreensaverProxy"
1806961,2018-12-07 00:16:56 UTC,Relevant light-locker issue: https://github.com/the-cavalry/light-locker/issues/121
1806961,2018-12-06 14:37:34 UTC,"I'm reporting this bug, not for personal reasons, but for concern for users that just like the look of lightdm, and install lightdm without thinking more about it. They get no warnings, and they open themselves up to a massive vulnerability, while the proper configuration should have been done automatically either by dkpg-reconfigure or by apt itself."
1806961,2018-12-06 14:30:03 UTC,"Is there a particular reason for using LightDM instead of GDM?
I am asking this because I was looking at your previous comment:
'So adding light-locker as a dependency will not work, and I think that
if the lightdm developers are not willing to fix the issue, we should just
remove the package from future releases of ubuntu.'"
1806961,2018-12-06 14:19:00 UTC,"It looks like light-locker is not running, please check this: https://github.com/the-cavalry/light-locker/issues/97"
1806961,2018-12-06 13:57:37 UTC,running light-locker-command -l gives me this output:
1806961,2018-12-06 13:25:02 UTC,I locked my session by clicking the lock icon in the top right.
1806961,2018-12-06 13:07:16 UTC,"Hi smurfendrek,"
1806961,2018-12-06 12:27:05 UTC,"Disregard my previous comment, installing light-locker does NOT fix the issue. (I was accidentally testing it on wayland :s)"
1806961,2018-12-06 00:40:45 UTC,Installing light-locker does indeed fix the issue.
1806961,2018-12-05 18:17:21 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better.
LightDM has an internal tool called dm-tool which provides some features for minimalist
window managers. Although it provides this tool, because of the many locking issues
it is not recommended to use it. So an alternative screen-locker application is necessary
to provide better security, one of them is light-locker, but there are many others."
1806961,2018-12-06 14:47:43 UTC,I tried applying the fix in the light locker issue. However that did not help (even after rebooting):
1806967,2020-07-18 20:51:54 UTC,Can you try the latest Mono version from https://www.mono-project.com/download/stable/ ?
1806973,2019-04-22 13:49:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1806973,2020-03-26 17:53:13 UTC,The ZFS drivers are now provided by the kernel package and so zfs-dkms can be safely removed and will avoid this issue.
1806973,2020-09-10 21:36:36 UTC,"I have btrfs! why did apt upgrade hold back 180 files when 1765 just upgraded??
Why did Aptitude suggest (and I accepted) that more upgrade?
Why include zfs ;-("
1806976,2020-06-07 04:17:20 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1806976,2019-07-31 21:36:30 UTC,"It appears that this is not a bug, but users should reference the specific documentation for DPDK on OpenStack for configuration. The example templates do not cover all use cases."
1806976,2019-07-31 21:07:32 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/633057
Reason: This review is > 180 days without comment and WIP -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewers. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1806976,2019-03-19 18:36:53 UTC,"""Is this still being worked on?"""
1806976,2019-03-19 13:25:46 UTC,Is this still being worked on?
1806976,2019-07-31 21:06:59 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1806981,2018-12-05 21:28:15 UTC,"I did a bit of research and 3.18.7 was the release that included ""CDS support"" and that the .so files were required for that support."
1806985,2018-12-05 21:02:28 UTC,This might also tie into https://bugs.launchpad.net/juju/+bug/1772649 though they're slightly different with one being around autoload-credentials.
1806985,2019-05-17 22:11:44 UTC,"After a few try those are the right option: juju version 2.6.2
credentials:
  cloud-openstack:
    default-region: RegionOne
    test:
      auth-type: userpass
      domain-name: ''
      password: password
      project-domain-name: admin_domain
      tenant-id: 8650020e13774c0aaa73e1e173ce8adf
      tenant-name: kubernetes
      user-domain-name: admin_domain
      username: admin
      version: ""3"""
1806985,2019-07-07 22:35:31 UTC,"This bug has been referenced by a discourse post, where another workaround has been found:"
1806985,2019-10-07 13:17:07 UTC,"Hit again, reported via discourse post:
https://discourse.jujucharms.com/t/juju-bootstrap-error-from-openstack/2158"
1806985,2019-10-31 03:42:30 UTC,Removing from a milestone as this work will not be done in 2.5 nor 2.6 series.
1806985,2020-11-11 15:22:08 UTC,"Using the 2.8.6 snap installed client.  We confirmed the OS_PROJECT_ID environment variable was set, so when bootstrapping, we didn't fill in the 'tenant_id' or 'tenant_name' options."
1806985,2020-11-11 21:29:11 UTC,I think that the Juju client might be lagging behind OpenStack in terms of which environment variables it pays attention to. We should audit the client and update it as necessary.
1806989,2018-12-12 18:20:18 UTC,"Hi, Any updates on this? thanks."
1806989,2018-12-13 15:35:04 UTC,"Kinnaird,
Thanks for the bug and the follow up.
I marked this as triaged.  Hopefully someone with some RH knowledge can work up the changes."
1807000,2019-09-01 20:21:34 UTC,"intro/outro markers
https://github.com/mixxxdj/mixxx/pull/1242"
1807000,2020-04-21 12:21:46 UTC,"I found this feature request because I would like to have the remaining time until the next cue point (not only the cue out).
It could be useful for instance with a long intro you want to now when the beat will start and launch the track before to mix the intro with the previous track. In general if you have set several cue points in the track, it is useful to know when the next is coming."
1807000,2020-04-21 12:43:59 UTC,"By now (2.3 alpha) this feature is covered by right-click & hold on the overview waveform, isn't it: you get a position marker with the distance from the current playposition that counts down/up while the track is playing."
1807021,2020-10-13 20:52:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807028,2018-12-06 13:37:24 UTC,Here's my work in progress branch (one commit so far):
1807030,2018-12-05 23:07:08 UTC,Please reopen if you feel there's an issue with how curtin is handling the late_commands.
1807030,2018-12-05 23:52:57 UTC,"Gah! thanks, I didn't even notice that before... thanks for pointing it out."
1807030,2018-12-05 23:06:26 UTC,"This is not a curtin bug.  In your config, you're providing a late_commands which invoke grep and do not eat the return code, so if grep fails to find it's query, it returns 1 and this fails the install (one or more of the late_commands failed)."
1807030,2018-12-05 22:52:17 UTC,"curtin config: https://pastebin.canonical.com/p/CqYxpMgzqg/
power settings:"
1807030,2018-12-05 22:49:21 UTC,Couple notes:
1807030,2018-12-05 22:45:58 UTC,"Hi Jeff,"
1807030,2018-12-05 22:58:56 UTC,Thanks for the quick response. So from the information provided above I can conclude that:
1807033,2019-07-26 00:30:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807040,2018-12-05 23:12:15 UTC,"UpgradeStatus: No upgrade log present (probably fresh install)
_MarkForUpload: True"
1807040,2018-12-05 23:12:33 UTC,none
1807044,2019-02-13 14:29:53 UTC,Note this resulted in a side effect bug 1815697 when there is at least one down cell in the deployment.
1807044,2019-03-22 03:45:29 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1807044,2019-03-24 23:40:07 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1807044,2019-05-18 19:29:38 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/625051
Reason: Not worth the complexity at this point for queens."
1807044,2019-05-18 19:29:45 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/625060
Reason: Not worth the complexity at this point for queens."
1807044,2019-08-10 00:08:34 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/675714"
1807044,2019-08-09 23:04:19 UTC,"Reviewed:  https://review.opendev.org/675148
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7d7d58509d5e60ec19c6310931dc62eeff033595
Submitter: Zuul
Branch:    master"
1807044,2019-08-29 13:52:28 UTC,"Reviewed:  https://review.opendev.org/675714
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bd03723a0c1a16d67433658fb486a84bb1bddf02
Submitter: Zuul
Branch:    stable/stein"
1807044,2019-10-07 16:33:20 UTC,"Reviewed:  https://review.opendev.org/679449
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7732f0e6f3691025a06f2abfc5a57c71d83e5e72
Submitter: Zuul
Branch:    stable/rocky"
1807044,2019-08-07 16:31:22 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/675148"
1807044,2019-01-08 16:55:26 UTC,"Reviewed:  https://review.openstack.org/624982
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=db6fc29ad2b817652d6bceea6f5bd0bdd1cba3bd
Submitter: Zuul
Branch:    stable/rocky"
1807044,2019-08-30 13:41:33 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/679449"
1807044,2018-12-13 16:45:03 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/625051"
1807044,2018-12-13 17:14:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/625060"
1807044,2018-12-06 15:43:28 UTC,"Another thing that is probably contributing to the slow nova-api start time is that every nova.compute.api.API constructs a SchedulerReportClient, which grabs an in-memory lock per API worker during init:"
1807044,2018-12-06 18:41:04 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623282"
1807044,2018-12-06 18:41:28 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/623283"
1807044,2018-12-06 18:41:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623284"
1807044,2018-12-06 15:50:47 UTC,I've created bug 1807219 for the issue described in comment 1.
1807044,2018-12-12 11:42:55 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/624677"
1807044,2018-12-12 17:14:35 UTC,It should also be noted that you only hit this if you configure nova with [upgrade_levels]compute=auto.
1807044,2018-12-12 23:29:12 UTC,"Reviewed:  https://review.openstack.org/623284
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d779b33d72d6ef41651ce7b93fe982f121bae2d7
Submitter: Zuul
Branch:    master"
1807044,2018-12-13 10:45:31 UTC,"Reviewed:  https://review.openstack.org/624677
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=58d3ac01a041326a831d6799b217255881d825a7
Submitter: Zuul
Branch:    stable/rocky"
1807044,2018-12-13 13:00:11 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/624982"
1807044,2018-12-12 03:35:49 UTC,"Reviewed:  https://review.openstack.org/623282
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=183f6238c1d98b04fdcee0fb70212f01f4012ae4
Submitter: Zuul
Branch:    master"
1807047,2019-09-30 08:48:34 UTC,"Our d-i is different / forked to the one from debian, and we don't merge all the changes they do. And vice versa. We do cherrypick things from time to time, which are useful."
1807047,2019-09-28 20:23:59 UTC,"The attachment ""debian-installer_hd-media-floppysize.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1807047,2019-06-24 14:09:44 UTC,This does not fit:
1807047,2019-02-26 07:31:44 UTC,"some fit, some don't:"
1807047,2019-02-15 20:57:05 UTC,ubuntu-18.10-server-amd64.iso 2018-10-17 22:20 717M  (that fit)
1807047,2018-12-10 02:57:46 UTC,"why this?
  ubuntu-18.10-server-amd64.iso
It isn't listed on
http://releases.ubuntu.com/cosmic/
I did find it on:
http://cdimage.ubuntu.com/releases/18.10/release/"
1807047,2018-12-09 23:20:02 UTC,Why are you trying to put live-server-amd64.iso there? instead of the classic .iso?
1807047,2019-05-10 06:56:19 UTC,"I should have tested, the iso doesn't fit in the resulting free space."
1807051,2019-01-29 14:16:00 UTC,"Next year, next update, same policy: No word to the customer about their broken software."
1807051,2019-03-03 16:32:50 UTC,"No response as I expected.
My next printer ain't gonna be a HP one."
1807051,2019-01-06 00:02:18 UTC,Can anybody tell us what is happening please?
1807051,2018-12-07 00:54:26 UTC,"It really does not bring me anything new. I updated because I usually do it and because the distribution warns of an update. Now I have disabled that option.
Anyway, I made this observation in case it helps to solve some problem that others may have."
1807051,2018-12-09 19:49:06 UTC,Then it is exactly the same problem that gave me in 18.04. That same error also came out.
1807051,2018-12-08 12:24:12 UTC,"Happens on a fresh installed Ubuntu 18.10 with a HP LaserJet Pro MFP m226dn.
The plugin installation with hplip-3.18.10 worked fine, but not with 3.18.12."
1807051,2018-12-06 20:27:45 UTC,As a matter of interest: what does HPLIP's 3.18.12 give you that your distribution's packages don't? This printer has been supported since 3.13.11.
1807051,2018-12-21 09:28:58 UTC,Any status on this?
1807052,2018-12-05 23:57:36 UTC,"If I remote iothreads and writeback caching, it seems more reliable, but I can still get it to hang."
1807056,2019-09-18 05:52:06 UTC,"The behaviour has changed recently. When the freeze occurs, whatever we type goes to the dash search. It is visible only when we click the 3x3 icon and visualize the dash search panel. Earlier, whatever we type was disappears altogether. ie, when the freeze occurs and I continue to type, it is nowhere to be seen. But when we take dash search panel to unfreeze it, we can see what we typed after the freeze in the search box. Hope I explained properly."
1807056,2019-07-20 02:20:09 UTC,Can confirm #43
1807056,2019-07-14 11:42:37 UTC,"I found a new issue within this bug. At times, the mouse right-click does not show any menu at all. Clicking on the dash search box fixes it though."
1807056,2019-07-06 02:36:57 UTC,I encounter the occasional keyboard freezes on my Ubuntu 18.04 (Communitheme). Clicking the 'Show Application' menu strangely restores keyboard functionality.
1807056,2019-03-14 07:34:06 UTC,"During the time I used Wayland, I had no issue.I couldn't try it extensively because VLC when a video is played gets froze and I have to use the power button to do anything on the computer."
1807056,2019-03-12 05:34:19 UTC,Looks like this issue does not exist when we use Ubuntu with Wayland in 18.04. I am using it now. Will update the details if there is any change.
1807056,2019-01-16 03:15:58 UTC,"Other than installing Cinnamon for testing and the dash to panel and arc menu extensions, none. With my previous experience, I tried to keep Ubuntu as default as possible."
1807056,2019-01-30 09:23:39 UTC,"Even after erasing and fresh install using 18.04 live USB, the freeze issue exists. When I searched the word "" Communitheme in the Ubuntu partition and I found a bunch of them still exists. Please check the screenshot. Is there any way to remove these residues of Yaru ?"
1807056,2019-01-20 04:29:29 UTC,"A small correction, I logged in 1.5 hours ago. So the freeze came back within an hour."
1807056,2019-01-20 04:27:58 UTC,"I got so annoyed by the keyboard freeze and banking on ""something else"" is causing the issue, I erased my 18.04 and reinstalled it yesterday evening. Now in the morning, I started using Ubuntu again for typing. It was fine for a couple of hours. But now the freeze has come back."
1807056,2019-01-16 11:24:37 UTC,"As suggested by @Daniel, I have removed all extensions and been using default Ubuntu DE all day. Sadly, the keyboard freeze is annoyingly present in default Ubuntu session as well.The workaround fixes the issue as discussed before."
1807056,2019-11-18 00:57:26 UTC,"I took a screenshot of typing switching to dash search box as reported in comment #46. Typing froze, and what I typed was put into the dash search box as seen below. It was supposed to be in the browser where I was typing it."
1807056,2019-01-30 09:38:04 UTC,"Those files come from package 'ubuntu-session', so they are apparently correct. Not related to this bug anyway."
1807056,2019-12-02 04:54:41 UTC,"This time it happened during Ubuntu 18.04.3 installation through bootable USB. When I was entering the user name and password during installation, the keyboard froze. It took me around 15 minutes to get out of the mess and have a proper installation. It will unfreeze for a second and when I type two characters in the password box, it freezes again. There is not even a cursor blinking in the boxes when I click on them."
1807056,2021-01-12 13:25:51 UTC,"I'm getting something very similar. When editing text - mainly (perhaps always) when selecting text the keyboard freezes for a short time.  Resizing/moving the window seems to recover this, but it recovers by itself after  about 10 seconds.
This is with Libre Office text, geany and kate editors.
Also happening on two different computers - a Toshiba Z830 and an Acer Aspire XC-605
Ubuntu 20.04.1   Gnome 3.36.8  Wayland"
1807056,2020-02-01 14:56:40 UTC,Not happening in Lubuntu installed on 18.04 default through Synaptic Package Manager. Thought of reporting here.
1807056,2020-03-23 01:47:21 UTC,"I have the same issue.
It happens in 18.04.3, 18.10 and 19.10.
It happens on a stock, recently installed ubuntu.
I installed wayland and it continues."
1807056,2020-03-23 01:48:21 UTC,"The other thing that happens, its like when i'm using terminator, the focus goes on and off.
It's reeeeeally anoying."
1807056,2020-04-24 10:33:26 UTC,I installed 20.04. And the bug is back as is from 18.04. I can get out of this if I wait or type on the search box. Thanks.
1807056,2020-04-27 16:30:34 UTC,Installed Kubuntu Desktop. No keyboard freeze. Everything fine in 20.04.
1807056,2020-04-28 04:22:31 UTC,"Please clarify if you mean the bug is fixed in 20.04, or present in 20.04?"
1807056,2020-04-28 04:57:26 UTC,@Daniel bug exists in default 20.04 which uses Gnome.
1807056,2020-06-22 12:06:06 UTC,"This is the main reason i quit Ubuntu. The bug was always there since I begun with 18.04 and my workaround was to press the power key on my laptop and click cancel when shutdown window appears. It was taking away from professional feel of a computer and making it feel like a 2013 smart phone. I believe one of the reasons not a lot of people report this issue is because they silently read forum posts that have no resolution for about 2 years and then go install another distro like I did. It's sad that Ubuntu had a few other bugs that were appearantly experienced by a very few people, therefore never getting really addressed; like this keyboard bug will be ignored on this page as it have been the last 2 years. Yes, I'm bitter. Because Ubuntu was my first ""escape from Windows"" solution and I really liked it until I couldn't stand the unnoticed bugs anymore."
1807056,2020-07-18 21:02:02 UTC,"I am facing same problem as the problem mentioned. My keyboard is getting freeze for few minutes after which it is again working fine. I have checked in linux mint too, I am facing same problem. Any help in this regard will be highly helpful in this regard."
1807056,2020-08-13 06:04:31 UTC,"On Ubuntu 20.04, I have similar problem. Actually, I met this problem since 19.10, however in 19.04, it was fine."
1807056,2020-09-10 05:57:29 UTC,Update about #59
1807056,2020-12-23 08:17:42 UTC,"The same problem: my keyboard is getting freeze (especially after entering text in text boxes: Chrome, Kate) for few minutes after which it is again working fine."
1807056,2019-01-16 01:46:11 UTC,"Thanks. That's the answer to ""caused by something that most other people don't have"". Most Ubuntu users only encounter the community theme (now known as Yaru) where it is included in Ubuntu 18.10 and later."
1807056,2019-12-14 15:26:10 UTC,has there been a resolution to this problem ? it is happening to me and the frequency is increasing and it now happening every 3-4 minutes and it is becoming impossible to use ubuntu. any help would be appreciated. i hate to move away from ubuntu. many thanks
1807056,2019-01-15 13:54:49 UTC,Freeze is very less in default Ubuntu DE. CommuniTheme session is literally unusable.
1807056,2018-12-07 09:36:20 UTC,"Thanks for explaining. Only keyboard input gets lost. Windows, mouse everything else works fine. I tried for a single machine when inputs got lost
1.in built laptop keyboard"
1807056,2019-01-15 10:10:17 UTC,Screenshot of buttons attached
1807056,2018-12-06 02:08:36 UTC,Can you please try removing the gnome-shell extensions:
1807056,2018-12-06 02:12:26 UTC,Please also open a Terminal window and leave the command 'top' running to see if any process is using high CPU when the problem happens.
1807056,2018-12-07 00:28:26 UTC,@Daniel I did try without any extension. It was happening even then. So I put them back for comfort sake.
1807056,2018-12-07 01:54:10 UTC,"Yes if you're using Xorg (the default ""Ubuntu"" session) then mouse cursor movement is done by the Xorg process so it will keep moving even if gnome-shell was frozen."
1807056,2018-12-07 01:56:26 UTC,"Oh, actually this sounds like it might be related to USB or other kernel problems."
1807056,2019-01-15 13:45:37 UTC,"Now that I have a workaround, I tried to be fully on Ubuntu default DE. What I noticed in past hour are"
1807056,2018-12-09 13:18:26 UTC,Another screenshot of 'top' while freeze
1807056,2018-12-10 02:42:24 UTC,Please follow the steps in comment 6.
1807056,2018-12-10 06:08:26 UTC,"Ok. I was confused whether to hit the power button to exit and then come back. That is what you are asking to do, right ?"
1807056,2018-12-10 06:35:15 UTC,"Yes, that command collects the log of the previous boot. Not the current one."
1807056,2018-12-13 01:51:13 UTC,@Daniel Attaching Prevboot.txt from the command you gave
1807056,2018-12-13 02:13:52 UTC,Thanks. I can't find any obvious explanation in that log.
1807056,2018-12-14 16:07:43 UTC,I am sorry. This is my primary laptop. I plan to keep the Ubuntu as default as possible.
1807056,2018-12-18 04:05:45 UTC,I installed Cinnamon DE from ppa:embrosyn/cinnamon . I will let you know if the problem happens again.
1807056,2018-12-08 17:21:03 UTC,I got out of Yaru and used default Ubuntu while login just to be sure. The freeze occurred again. I had ' top ' running. Took a quick screenshot
1807056,2018-12-30 06:54:47 UTC,What I have noticed is that the freeze occurred only once in Cinnamon. Nothing since it happened first. I will update here if some progress happens.
1807056,2019-01-15 10:08:33 UTC,"First one, please find the screenshot attached"
1807056,2019-01-15 09:56:32 UTC,(all on the original Ubuntu 18.04 installation)
1807056,2019-01-15 09:56:07 UTC,^^^
1807056,2019-01-15 09:40:59 UTC,"Yeah, I guess that could be related to keyboard freezes."
1807056,2018-12-22 06:20:10 UTC,"@Daniel , It happened in Cinnamon as well. I had some important work so I was using Windows 10 ( dual boot ) all these days. The issue is limited to 18.04. I wanted to update this thread and started using Cinnamon today. The keyboard just froze for about 1 minute and then everything got ok by itself."
1807056,2019-01-15 09:28:49 UTC,"the log in one of the comments has that warning, unsure if it could have to do with the issue"
1807056,2019-01-15 09:36:49 UTC,"As suggested, I tried the latest daily build of Disco from USB. I used it for around 30 minutes.There was a moment which appeared to be a freeze. It went ok when I tried the dash search. Again, I am not sure whether I imagined it. Currently, I am not in a position to use Disco indefinitely. Thought I would update you guys."
1807056,2019-01-15 01:39:52 UTC,Sounds like a great workaround. But I have more questions :)
1807056,2019-01-14 18:21:07 UTC,I think this is a permanent workaround. It could get rid of keyboard freeze this time as well by trying to type something on the dash search.
1807056,2019-01-13 14:16:18 UTC,"Today, I came back to Ubuntu default DE and the freeze came back instantly. But for good, I found a workaround. If you try to type something on the dash search, the issue goes away. Good, right ? It worked for me a couple of times. I will see if this can be a permanent workaround."
1807056,2019-01-07 08:40:52 UTC,"@Daniel I have been using Cinnamon for around 15 days now. Other than the first instance where I felt that there is a freeze, it never happened in Cinnamon. In the last couple of days, I once switched to default Ubuntu DE and the freeze came back in no time. I guess it is more or less safe to say that this keyboard freeze is almost non-existent in Cinnamon."
1807056,2019-01-07 04:09:14 UTC,"Can you try a different desktop that doesn't share code with Gnome Shell? Unfortunately Cinnamon does, so isn't a useful test."
1807056,2019-01-15 04:29:57 UTC,"1. Once did try when I posted this in AskUbuntu. That was the first suggestion I got. I posted this on Discourse.Ubuntu but the thread got locked, but still got a like after one month of lock. In the It's Foss Community where I tried to seek help, there was someone who said it happens to him/her as well."
1807072,2018-12-06 02:49:33 UTC,bug fix: https://review.openstack.org/623121
1807072,2019-05-16 09:37:34 UTC,it's fixed now
1807073,2020-06-09 21:20:44 UTC,"I have a problem with fsfreeze that looks very similar to this, though I'm of course not 100% sure it's the same."
1807073,2019-04-07 08:17:32 UTC,"Just got almost the same
Ubuntu 16.04 as guest on Centos 7 host,
all will latest updates."
1807073,2019-04-07 08:23:49 UTC,"btw,I run OEL7 VM on the same host and Ubuntu 18.04 VM,
both have newer qemu-guest-agent:"
1807073,2019-04-08 05:16:10 UTC,But it happens in some times， this problem dose not occur 100 percent。I can not reproduce when I want to find WHY。So it‘s dangerous in my production environment。
1807074,2018-12-18 16:33:06 UTC,Similar fix to this
1807074,2018-12-19 15:53:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626222"
1807074,2020-02-21 08:33:20 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/626222"
1807075,2018-12-06 04:03:58 UTC,bug fix: https://review.openstack.org/623129
1807075,2019-05-16 16:13:26 UTC,"I4b2af19a62af260a02eb7b48e750da69418ad1c9 solved this (while fixing another problem), this is fixed now"
1807078,2018-12-08 00:19:02 UTC,Can you check the directory into which you must install your extensions? See Edit > Preferences > System: User extensions.
1807086,2019-05-20 05:43:08 UTC,I can confirm this as seen today:
1807101,2019-01-11 05:18:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630026"
1807101,2019-09-16 17:13:04 UTC,"Reviewed:  https://review.opendev.org/630026
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=fa6bb0b5b2976906214b7f7f4f4aa5cb24234736
Submitter: Zuul
Branch:    master"
1807101,2019-09-27 15:26:26 UTC,This issue was fixed in the openstack/blazar 4.0.0.0rc1 release candidate.
1807108,2018-12-08 11:55:13 UTC,"It's weird that I build a same code of captureDeviceScreen(0, 0, 1600, 900) and output the image file.
The image file is perfect. No black part in the lower part."
1807108,2018-12-08 13:31:50 UTC,I traced some code from the source for my test.
1807108,2018-12-07 10:14:22 UTC,No problem.
1807108,2018-12-12 15:51:35 UTC,"Thanks!!!
I saw that and tested it immediately."
1807108,2018-12-12 16:42:27 UTC,"Ok, thanks for immediate feedback."
1807108,2018-12-12 14:40:26 UTC,The capture section is completely revised and should work now (including the IDE menu check).
1807108,2018-12-07 09:24:48 UTC,"You can try bignox(https://en.bignox.com/) which supports mac.
But I do not have a mac system so I have no idea if the adb works on emulator in mac system."
1807108,2018-12-08 12:24:12 UTC,"--- same code of captureDeviceScreen(0, 0, 1600, 900) and output the image file.
could you paste the code?"
1807108,2018-12-06 17:03:13 UTC,"Ok, a step further ;-)"
1807108,2018-12-06 10:08:22 UTC,"--- IDE: Jython IDE
what is that?"
1807108,2018-12-06 10:11:23 UTC,BTW: I guess the IDE hangs caused by this non-RGBA problem
1807108,2018-12-06 11:38:09 UTC,--- IDE:what is that?
1807108,2018-12-07 08:59:55 UTC,"On Windows I have the ""black-lower-part"" effect with the emulator and my real device."
1807108,2018-12-06 14:02:31 UTC,"ok, thanks for feedback and tests."
1807108,2018-12-06 14:04:12 UTC,"BTW: might be a problem with Android 5.x --- but as mentioned: Android experience very, very bad ;-)"
1807108,2018-12-06 11:48:36 UTC,I also try the screencap command without -p
1807111,2019-03-16 13:56:56 UTC,"few question:
- what minimal info would you like ?
(money is quite over powerful for that for other reason than just put info into it)"
1807111,2019-07-11 04:17:52 UTC,[Expired for HomeBank because there has been no activity for 60 days.]
1807112,2018-12-06 08:55:56 UTC,"The following is all that is needed:
--- /home/paelzer/bin/lp-affects        2018-11-26 15:20:14.606100426 +0100
+++ /home/paelzer/bin/lp-affects-devel  2018-12-06 09:48:11.193017863 +0100
@@ -13,6 +13,8 @@
 parser.add_argument('package',
                     help='src name to add the task')
 parser.add_argument('release',
+                    default=None,
+                    nargs='?',
                     help='release to mark affected')
 args = parser.parse_args()"
1807126,2019-02-14 16:14:31 UTC,Missed the link in comment https://bugs.launchpad.net/manila/+bug/1807126/comments/7
1807126,2019-10-10 15:31:24 UTC,This bug has not been reproducible on the CI or locally after the fixes to manila-image-elements have been made. I'm closing this at the moment. Please report another bug if this issue recurs.
1807126,2019-02-14 16:42:11 UTC,Thank you guys for the effort investigating this issue and mitigating it. As soon as I can I'll retest it in my environment.
1807126,2019-02-14 16:13:14 UTC,"Hi Carlos,"
1807126,2018-12-26 13:45:59 UTC,"The issue reproduces with bionic host and bionic service VM [1] and, as Carlos noted, openssh client ssh from the devstack host to the SVM works, but only after a very long delay that would cause a timeout with paramiko code running from manila-share's generic driver service."
1807126,2018-12-26 14:58:22 UTC,I tried setting the paramiko banner_timeout as described here [1] to a large value but it doesn't seem to change the time it takes to hit the SSHException and accompanying Error reading protocol banner message.
1807126,2018-12-26 14:37:43 UTC,"Once the share server is created and you login to it (slowly) via openssh client, you can ssh from the share server to itself (ssh localhost) with no delay.  This suggests some kind of network issue between the devstack host and the service vm.  So I tried reducing the mtu on the relevant tap interface on the host to 576 and on the target interface on the SVM, as suggested here [1]."
1807126,2018-12-06 16:34:53 UTC,The used local.conf file was:
1807126,2018-12-06 16:16:56 UTC,Carlos reported on IRC that when he attempts the ssh connection manually it eventually works but that it is very slow.
1807126,2018-12-31 14:27:12 UTC,"Actually setting the paramiko banner_timeout is [1] a workaround for the underlying networking issue, In the previous comment [2] I didn't realize I needed to up the connection timeout so that it's not less than the banner_timeout."
1807127,2019-01-26 17:54:59 UTC,"Seb, I can duplicate the issue you found. I suggest we just drop thumbnail-Fix-use-after-free-when-getting-a-preview-icon.patch. It also added a leftover debug line ""got a preview thumbnail"" (that was removed in a later commit)."
1807127,2019-05-27 15:30:25 UTC,This package has been superseded by the following security update:
1807127,2019-05-14 16:45:20 UTC,What's the status of this SRU? We're awaiting on this to prepare a security update...
1807127,2019-02-26 17:50:19 UTC,"Hello Eugene, or anyone else affected,"
1807127,2019-02-25 21:44:10 UTC,Sorry about the delay. I have uploaded a new version to the cosmic UNAPPROVED queue that should fix the identified regression.
1807127,2019-01-29 09:10:16 UTC,"@Jeremy, the fix makes sense to keep since it's a potential segfault, the warning problem just got fixed upstream with that commit
https://gitlab.gnome.org/GNOME/gnome-desktop/commit/bbae26a6
We should rather add that change to the SRU (and drop the g_message call)"
1807127,2019-01-23 15:34:33 UTC,"On cosmic the SRU fixes the thumbnail creation, but starting from a command line nautilus shows those G_IS_OBJECT (object) warnings"
1807127,2019-01-29 13:13:58 UTC,"Ok, let's wait for the merge proposal to be accepted:
https://gitlab.gnome.org/GNOME/gnome-desktop/merge_requests/29"
1807127,2018-12-18 17:05:17 UTC,"Hello Eugene, or anyone else affected,"
1807127,2018-12-18 05:22:17 UTC,This bug was fixed in the package gnome-desktop3 - 3.28.2-0ubuntu1.2
1807127,2018-12-12 04:26:57 UTC,"Hello @Steve,
Checked your pkg/ppa in Bionic 32 bit - all back to normal
Thanks for your quick fix."
1807127,2018-12-06 11:09:22 UTC,I have forwarded the issue to GNOME at https://gitlab.gnome.org/GNOME/gnome-desktop/issues/89
1807127,2018-12-12 01:09:08 UTC,This bug was fixed in the package gnome-desktop3 - 3.30.2-3ubuntu1
1807127,2018-12-12 00:59:48 UTC,"For bionic, I've uploaded the gnome-desktop3 package with the fix for 32bit systems to the ubuntu-security-proposed ppa (https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/) for people to test. Any feedback would be appreciated."
1807127,2018-12-11 15:23:27 UTC,"Security Team, would you be interested in sponsoring directly from our git branch for bionic-security?"
1807127,2018-12-06 16:35:31 UTC,"I submitted a fix to upstream: https://gitlab.gnome.org/GNOME/gnome-desktop/merge_requests/20, let's see what they say."
1807127,2018-12-20 00:06:41 UTC,Proposed working on Bionic (18.04) 32 bit system
1807137,2018-12-12 01:48:42 UTC,"So, I think the best way to get travis working without the legacy hooks, would be to add the travis github app to the repository. However:"
1807137,2018-12-11 17:13:42 UTC,Might not need that after all. Will keep you posted.
1807137,2018-12-11 10:24:50 UTC,Not sure how I give permissions to other people in Travis CI.
1807137,2018-12-10 21:06:22 UTC,I think that's the one. When I go here:
1807137,2018-12-10 19:58:55 UTC,You mean this one?
1807137,2018-12-10 14:40:17 UTC,"Not really sure. I suppose it would be enough to have access to wherever github services are defined (karl?). I do have whole org access on karlhosting.
Carlos de la Guardia"
1807137,2018-12-10 14:24:53 UTC,"The organization as a whole, or:"
1807137,2018-12-09 18:57:06 UTC,"I have owner role on karlhosting, it's karlproject where I don't have enough permissions."
1807137,2018-12-09 17:02:51 UTC,Let me know if I need to do something on karlhosting
1807137,2018-12-09 07:16:46 UTC,Not sure if I need access to karlproject's settings on github to fix this.
1807137,2018-12-10 17:39:37 UTC,One more hurdle. Need access to travis-ci karlproject settings.
1807138,2019-08-22 03:18:15 UTC,"If the headphone doesn't work, please run:
sudo hdajacksensetest -a //without plugging the headphone"
1807138,2020-06-23 07:41:15 UTC,I'm having same issue with same machine. Is there any news?
1807138,2020-01-08 16:25:14 UTC,Having the same issue on the same machine and would be extremely happy if there is any help or advances in this regard.
1807138,2019-08-22 17:53:21 UTC,Posted alsa-info.sh to http://alsa-project.org/db/?f=aea8019642712707b206b1ebf30ceada504b58c2
1807138,2019-08-22 17:46:02 UTC,"OK, stopped working again today.  I think I undid everything I've been testing with hdajackretask (i.e. removed boot override) yesterday while it was still working and double-checked it today."
1807138,2019-08-21 23:52:28 UTC,"Just an FYI, the netcat -U /var/run/acpid.socket is now seeing the headphone jack event.  Everything appears to be working."
1807138,2018-12-06 12:17:10 UTC,"I've taken a screenshot of the alsamixer.
This configuration currently is the only way for me to get sound out of my headset and not the speakers:"
1807138,2019-04-20 17:58:37 UTC,Can confirm this is still and issue in 19.04.
1807138,2019-04-17 21:53:13 UTC,Do you need any other input to get a fix in for this? I've tried a number of different 'model' settings for the ALC256 to try to get this to work to no avail.
1807138,2019-04-05 19:35:08 UTC,I have an identical setup and problem.
1807138,2019-02-06 04:17:26 UTC,[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]
1807138,2018-12-07 15:07:34 UTC,I'm using a Razer Blade 15 2018
1807138,2018-12-07 14:37:16 UTC,What laptop model do you use? Upstream kernel driver has regular fixes like https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=c1732ede5 (the one should be in the current kernel already though)
1807138,2019-05-02 16:13:44 UTC,"Since it's still not working on 19.04, guess that answers my question as to whether to upgrade or not.  I've confirmed that the acpid isn't seeing the plug in event by running:"
1807140,2018-12-06 14:45:32 UTC,apport information
1807140,2018-12-06 14:45:36 UTC,apport information
1807140,2018-12-06 14:45:34 UTC,apport information
1807140,2018-12-06 14:45:33 UTC,apport information
1807140,2018-12-06 14:45:32 UTC,apport information
1807140,2018-12-06 14:46:14 UTC,The information above is from a VM with a reproducer.
1807140,2018-12-06 14:45:29 UTC,apport information
1807140,2018-12-06 14:45:28 UTC,apport information
1807140,2018-12-06 14:45:27 UTC,apport information
1807140,2018-12-06 14:45:25 UTC,apport information
1807140,2018-12-06 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1807140,2018-12-06 14:45:31 UTC,apport information
1807151,2018-12-06 13:45:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623206"
1807151,2018-12-20 13:49:32 UTC,"Change abandoned by Iury Gregory Melo Ferreira (<email address hidden>) on branch: master
Review: https://review.openstack.org/623206
Reason: We cannot fix this as it'll break a whole bunch of things on upgrades. It's unfortunate that it's like this but we likely won't be able to just change this."
1807152,2019-03-11 14:43:31 UTC,This issue was fixed in the openstack/networking-bagpipe 10.0.0.0b1 development milestone.
1807152,2019-01-08 14:02:18 UTC,"Reviewed:  https://review.openstack.org/629134
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=40951dbb0d622c0c0f5ad6711555fe9ac1c8d3c9
Submitter: Zuul
Branch:    master"
1807152,2018-12-21 09:20:16 UTC,"All runs > 2018-11-14T07:56:29 are FAILED.
All runs before are SUCCESS."
1807152,2019-01-08 06:18:06 UTC,The issue seems to be that the neutron agent extension stops the loop that tests the availability of bagpipe-bgp because of an exception:
1807152,2018-12-21 09:05:30 UTC,I haven't yet found the root cause.
1807152,2019-01-08 10:27:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/629134"
1807153,2019-11-07 08:54:51 UTC,"Reviewed:  https://review.opendev.org/693183
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ff07bacc9080ab5d904f4b82f5d16da4fd61df6e
Submitter: Zuul
Branch:    stable/stein"
1807153,2019-12-19 14:41:29 UTC,This issue was fixed in the openstack/neutron 14.0.4 release.
1807153,2019-11-14 01:17:11 UTC,"Reviewed:  https://review.opendev.org/692910
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=689c1125efcf586daea8c2bbe0c8913f465d22c8
Submitter: Zuul
Branch:    stable/rocky"
1807153,2019-11-06 14:11:47 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/693183"
1807153,2019-12-19 14:39:53 UTC,This issue was fixed in the openstack/neutron 13.0.6 release.
1807153,2019-09-19 10:12:36 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1807153,2019-07-19 19:33:14 UTC,"Reviewed:  https://review.opendev.org/666970
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9f541521bbbcf36325bfc250e3ce27a138ddef3c
Submitter: Zuul
Branch:    master"
1807153,2018-12-06 14:15:34 UTC,I included a fix for this in my change to fix metering for DVR routers: https://review.openstack.org/#/c/621165/
1807153,2019-06-22 21:54:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666970"
1807153,2019-11-04 21:40:37 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/692910"
1807155,2020-04-25 08:40:10 UTC,"The bug is still present in 20.04.
The ""shallow"" mode doesn't cause the problem, but the battery drain is about 10% of that during normal operation without stress (browsing, terminal, text editor, etc.)."
1807155,2020-04-17 09:35:28 UTC,Hi everyone!
1807155,2020-04-17 08:29:56 UTC,"Anton,"
1807155,2020-05-07 17:45:18 UTC,For me the issue was in secure boot (should be disabled) and in swapfile (should exist == your RAM)
1807155,2019-07-29 16:10:58 UTC,What happens if s2idle is used instead?
1807155,2019-05-23 15:13:52 UTC,"The bug is also present in 19.04, kernel 5.0.0-15
The behavior is identical with X server and Wayland."
1807155,2018-12-06 14:00:07 UTC,This change was made by a bot.
1807155,2020-04-17 07:11:11 UTC,"I have the same issue on XPS 13 9300 with Ubuntu 18.04.
Answering @kaihengfeng's question: with s2idle it works just fine from waking up perspective but as Mikhail mentioned it drains battery a lot."
1807156,2019-02-11 07:08:40 UTC,"Do you still remember what you were doing when this occurred? Looks like you opened a window, which one?"
1807156,2019-02-24 06:19:15 UTC,"I could not reproduce this, so the fix in the attached branch is just a guess."
1807156,2019-03-16 11:42:27 UTC,"Since this bug is not reproducible, can't we retarget it to build21?"
1807156,2019-03-18 07:47:40 UTC,Any objections to merging the attached branch and closing this?
1807156,2019-03-22 09:14:25 UTC,In my opinion a bug that isn't reproducible should be considered spurious therefore I would vote for postponing this and see whether we will get any new issues of that. If it is hard to reproduce the Chance of occuring is rather remote and therefore no showstopper.
1807156,2019-03-22 17:50:52 UTC,Let's merge it and postpone the bug then.
1807156,2019-04-22 16:03:29 UTC,"A late reply: I no longer have any idea what I was doing that might have triggered this.  If no one can reproduce this bug, and you may have solved it anyway, maybe you should just close this report?"
1807156,2019-04-23 04:22:49 UTC,"I have set it to incomplete, that should make it disappear from the list after a while."
1807156,2019-06-23 04:17:22 UTC,[Expired for widelands because there has been no activity for 60 days.]
1807157,2019-06-22 21:32:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666969"
1807157,2019-04-16 08:48:10 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/634016
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1807157,2018-12-06 14:15:07 UTC,I crated a change for this: https://review.openstack.org/#/c/621165/ and it seems to fix the issue on our Pike deployment.
1807157,2019-01-30 17:49:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634016"
1807157,2019-04-16 08:48:00 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1807177,2018-12-06 16:28:51 UTC,"Thank you for the (VERY fast) reply!  I don't really understand your comment about there being a dependency since Gluster and Samba install independently and the module in question (to my understanding) is only enabled if specifically configured; but I guess it's irrelevant because the bug you mentioned says that A) The security team ""NAK""ed it (twice), and B) As of 2018-09-25 it seems that there's not an [Ubuntu] team willing to maintain it, so it will not be included in Main regardless."
1807177,2018-12-06 16:57:03 UTC,"> Gluster and Samba install independently and the module in question (to my understanding)
> is only enabled if specifically configured
"
1807177,2018-12-07 09:36:00 UTC,"From what I can see... the glusterfs library in samba vfs grows a dependency, but if nothing else in the samba package does... then as I understand it, the only way you could need that library would be to install glusterfs-common... so surely that's a technicality?"
1807177,2018-12-10 13:08:00 UTC,"It's not like that. The Depends field is populated from debian/control, and from automatically calculated dependencies (like that ldd trick). The moment a package lists something in Depends, if that something cannot be installed, then the package itself will not be installed. It doesn't matter if your smb.conf is referring to the gluster module or not."
1807177,2018-12-06 15:41:56 UTC,Thanks for filing this bug in Ubuntu.
1807180,2019-08-19 15:34:59 UTC,This issue was fixed in the openstack/python-watcherclient 2.3.0 release.
1807181,2020-01-23 04:17:25 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1807181,2018-12-06 16:21:45 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1807181,2019-11-23 11:16:25 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.
1807189,2018-12-06 16:21:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1807194,2019-01-21 22:49:43 UTC,"This bug is particularly annoying because every time you submit and it tells you your username is taken, you have to type your password again twice."
1807197,2018-12-06 16:22:03 UTC,"On closer inspection, gdm3 does remember both my user and last chosen session/desktop when I log out of X but it fails to recall my user and session if I reboot or shutdown."
1807197,2018-12-07 14:11:39 UTC,"Thank you for your bug report, I can't confirm the issue on a new bionic installation
- log into the normal session
- log out
- click of the session selector, 'ubuntu' is selected, pick 'ubuntu wayland'
- log in
- reboot from the top right indicator
- select the same user and click on the session selector
-> the wayland session is still selected"
1807197,2018-12-07 16:41:22 UTC,Hi Sebastien
1807216,2021-02-18 17:15:01 UTC,Should this be Fix Released now?
1807221,2019-06-16 21:36:25 UTC,"I agree, it took me a long time to figure out the meanings of the buttons as well.  I would have found it easier to understand if there was a red X for the muted state and picture of sound waves for unmuted state, like the top two in this image here: https://stock.adobe.com/images/sound-volume-control-buttons-set-mute-unmute-quieter-louder-icons-in-circle-vector/188826766"
1807221,2019-06-16 21:31:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807229,2018-12-06 18:34:19 UTC,Fixed in x.4325.
1807233,2018-12-06 19:05:44 UTC,Three things to fix:
1807233,2018-12-06 19:34:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623295"
1807233,2018-12-06 19:41:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623297"
1807233,2018-12-06 19:56:58 UTC,"Although I would not recommend this in a production cloud, for testing purposes while we wait for reviews the built charm with the above fixes can be found here:"
1807233,2018-12-07 07:05:13 UTC,"Reviewed:  https://review.openstack.org/623295
Committed: https://git.openstack.org/cgit/openstack/charms.openstack/commit/?id=bba344aa6c4b2403f2eb771897443684eb8993d2
Submitter: Zuul
Branch:    master"
1807233,2018-12-07 12:49:19 UTC,"Reviewed:  https://review.openstack.org/623297
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-dynamic-routing/commit/?id=f17e32ea25e54d28c01e5a924c138dd9a9e40063
Submitter: Zuul
Branch:    master"
1807233,2018-12-06 17:24:58 UTC,I copied the [oslo_messaging_rabbit] section from the neutron-api unit's neutron.conf to neutron.conf on the neutron-dynamic-routing unit and copied /etc/neutron/rabbit-client-ca.pem as well.
1807235,2019-02-28 05:08:00 UTC,disco has 1.2.5 which has a fix for this.
1807235,2018-12-06 17:33:19 UTC,"This affects bionic, cosmic and disco.
bionic (1_0_X branch) patch: https://github.com/hughsie/fwupd/commit/282c7112a99585d66eaedb039fb0d72e3e0f120d
cosmic and disco (1_1_X branch) patch: https://github.com/hughsie/fwupd/commit/c9cf34ff00e48a6b247c6b6e4bc05f5c7dc3c1fe"
1807235,2018-12-06 17:34:12 UTC,As a mitigation for now anyone affected can workaround by disabling the appropriate wacom plugin in /etc/fwupd/daemon.conf.
1807240,2018-12-06 20:41:12 UTC,2.43.1+18.4 Ubuntu 18.04
1807240,2020-01-05 19:22:57 UTC,3.8 exhibits the same error. I am running snap in a podman container.
1807240,2020-01-05 19:59:57 UTC,The problem is conflict between `shutil.copystat` and SELinux. `copystat` in my case tries to copy attributes from system dir from inside container to mounted volume. I do not know how it triggers `relabelto` event.
1807240,2020-01-05 20:10:14 UTC,Ok. The problem solved by copying all files into project/ and mounting the project dir correctly.
1807240,2020-01-05 20:12:48 UTC,"To save some time and future confusion, a warning could have been issued if running inside container and an attempt is made to use some system dir as a source."
1807241,2019-11-01 20:18:43 UTC,We do now make sure to now choose EOL'd series and go to the next valid one unless the operator uses force. I'm going to mark this fix committed.
1807241,2018-12-10 17:27:37 UTC,I do think it's appropriate for Juju to pick the latest LTS if multiple releases are declared as supported. This will avoid this particular issue and seems like a reasonable decision for Juju to make.
1807241,2018-12-10 21:15:36 UTC,I like the approach proposed in comment #4.  +1 to that.
1807241,2018-12-06 18:40:39 UTC,"If you can put a process in place to crawl through all charms and unpromulgate the ones that have an EOL series as the preferred one (top of the list), then sure. TBH, I thought the default was to always pick the latest LTS (if listed in the charm, of course)."
1807241,2018-12-06 18:55:08 UTC,I think that'd it'd be very good of us to query charms supporting EOL and reaching out to those charm authors. We know who's they are and should be touching base with the charming community like that imo.
1807241,2018-12-06 18:23:18 UTC,Thanks for filing this. I can understand the request but I feel like honestly the root here is that the charm failed to be maintained and we should have been more proactive in pulling this down vs trying to sugar coat the series to keep it limping along. That's on us for not pushing to get it pulled sooner.
1807244,2019-02-10 21:42:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807244,2019-02-10 21:44:22 UTC,This seems to be a duplicate of #1798683
1807245,2020-05-04 15:34:15 UTC,I don't see a recent reproduction of this bug in logstash[1]. The current failure visible there is coming from a single patch that was broken. I close this as Incomplete as it seems it does not happen any more. If you see this issue again please set the bug state back to New and link to logs for the new reproduction.
1807245,2020-07-04 04:17:36 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1807249,2019-01-15 09:55:04 UTC,HI i left my laptop on over night and the next day i got a bug report that send me to this page... i dont know what the issue was since im not an expert in linux all so my wifi works exept the 5Ghz network that is extremely slow.
1807257,2018-12-07 18:03:29 UTC,"Marking this Confirmed, a few observations when I tested this, though:"
1807257,2018-12-07 18:39:40 UTC,See also bug 1648922.
1807264,2019-03-20 06:21:21 UTC,"Please try mainline kernel.
Also, what's the last working kernel?"
1807264,2019-02-07 11:20:57 UTC,"BTW: Two things: 1)inplugged is misspelled and should be unplugged; 2) I've been continuously upgrading the kernel, but still no fix. The kernel is now V4.20.7."
1807264,2019-02-07 11:16:51 UTC,"I'm not getting any help, suggestions, hints, or anything with this problem. I't seems that I'm alone and the only one with this problem. So, if you are looking at this, there are no experts assisting, but I've been experimenting ..."
1807264,2018-12-11 02:55:25 UTC,"I've degraded the kernel from 4.19.8 back to 4.14.41. This was suggested by several people and for them, it fixed the problem. With the degraded kernel I am able to suspend, but not hibernate. If the computer is left unattended and hibernates, the same response is seen as described above."
1807264,2019-06-25 01:32:01 UTC,"You asked the same questions I did, but the answer doesn't help. 16.04 was the last version and it's kernel was 4.10.0.27.30. Going back, doesn't help. There is something in the 18.04 version that overrides the kernel. Read my responses above. I've used almost every kernel in between and currently, I'm using 5.0.10. I may jump to the most recent at this writing, 5.1.14, just to see what happens."
1807264,2018-12-08 20:58:02 UTC,Very similar to kubuntu 16.04.1 with kernel 4.4.0-41
1807264,2018-12-07 04:03:59 UTC,apport-collect 1807264: data was gathered and sent.
1807264,2018-12-07 03:59:09 UTC,apport information
1807264,2018-12-07 03:59:08 UTC,apport information
1807264,2018-12-08 22:07:09 UTC,"Can we start with a logical first step?
Is there a solution for preventing/eliminating hibernation?"
1807264,2018-12-06 20:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1807270,2018-12-06 21:28:36 UTC,It looks like it is a duplicate of
1807270,2018-12-06 21:31:47 UTC,And this
1807274,2019-02-05 19:48:48 UTC,moved form https://bugs.launchpad.net/yade/+bug/1807274 to https://gitlab.com/yade-dev/trunk/issues/45
1807276,2018-12-07 14:03:28 UTC,Thank you for your bug report. Can you add your journalctl log after triggering the issue? Swipping from the bottom on an inspiron 11 using the Ubuntu (x11) default session works here on bionic & cosmic
1807276,2019-01-18 21:08:20 UTC,Adding journalctl output as requested
1807276,2019-01-18 21:08:38 UTC,Adding journalctl output as requested
1807276,2019-01-18 21:34:17 UTC,It may be worth mentioning that we are unable to reproduce the error on some more esoteric models like rugged machines.
1807276,2020-03-12 05:51:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807276,2020-03-17 14:45:55 UTC,"Tagging rls-ff-notfixing, would be nice to fix but it's not a recent regression nor impacting most users so not a rls target atm"
1807276,2020-03-17 20:04:20 UTC,"But it worked before for me before, see duplicate https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556
And the part where it does not appear at all occurred in the past and was fixed: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399"
1807276,2020-03-24 14:51:06 UTC,Dropped the champagne tag as not deemed release blocking.
1807276,2020-04-21 08:49:43 UTC,https://gitlab.gnome.org/GNOME/gnome-shell/issues/2378 is another report specific to configurations without a physical keyboard. Could you give more details on the configuration you are using and test if it works better under wayland for you?
1807276,2019-01-18 21:16:46 UTC,~30 second video reproduction of issue
1807277,2018-12-07 08:25:04 UTC,"Thank you for your bug report, that's known upstream
https://bugzilla.gnome.org/show_bug.cgi?id=689886"
1807279,2019-02-05 22:20:41 UTC,Hi Eva
1807279,2019-02-05 18:22:20 UTC,Correction - If Set to True - the check box for phone notifications should be removed from place hold screen
1807279,2019-02-05 19:32:55 UTC,"Such setting is currently available in Evergreen but not in the Library settings editor. It is possible to hide the phone notification in Open-ILS/src/templates/opac/parts/config.tt2,"
1807282,2020-07-28 17:06:26 UTC,"Confirmed, charm does not update mons after getting first mon relation with auth info."
1807282,2018-12-07 15:56:49 UTC,"Based on the output produced during a clean redeploy, I can see that the charm logic is incorrect in handling config changes."
1807289,2019-02-18 20:31:02 UTC,All I'm going to say on this bug at the moment is that this is the hairy part of guessing the user's intent.
1807289,2019-02-18 06:40:45 UTC,+1
1807289,2018-12-07 00:01:20 UTC,juju version 2.4.7-bionic-amd64
1807289,2018-12-10 15:54:08 UTC,"and/or, is there a way to --map-machines ""foo/0"" to ""foo/3""?"
1807289,2019-01-14 13:41:00 UTC,It's a tricky spot there. We'll have to see what we can figure out to help make that logic fit into a more expected path.
1807297,2019-07-18 21:44:10 UTC,"Hi,"
1807298,2019-03-12 16:28:16 UTC,"Are you using Kolla-Ansible's Ceph role or an external Ceph cluster? I am using the latter and it looks like Kolla-Ansible excepts to have an NFS-Ganesha service available on the controllers, but doesn't deploy any itself."
1807309,2019-02-19 13:19:48 UTC,Is this still an issue?
1807309,2019-02-20 21:38:37 UTC,"I think so, I've lost my environment for a while but when I get it back I'll confirm."
1807309,2020-06-07 04:17:22 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1807325,2018-12-07 17:36:15 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1807325,2020-07-24 08:17:06 UTC,"I was able to reproduce this issue using the ""USAA Federal Savings Bank"" (fid 483). A warning about a certificate mismatch appears."
1807325,2020-12-29 10:29:51 UTC,This should be fixed with libgwenhywfar 5.4.1-1.
1807325,2021-02-09 13:04:50 UTC,The fixed package libgwenhywfar/5.4.1-1 is available in Groovy Gorilla (current stable release). Changing status to Fix Released.
1807334,2019-02-14 12:11:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1807334,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1807334,2019-01-15 10:33:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1807334,2019-02-04 14:46:37 UTC,This bug was fixed in the package linux - 4.19.0-12.13
1807338,2018-12-11 15:46:11 UTC,"> Not sure if this project is being maintained
"
1807340,2019-02-09 04:14:00 UTC,"Reviewed:  https://review.openstack.org/634236
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6d38ba1589e58d13113b1a2e3549927c091ee17c
Submitter: Zuul
Branch:    stable/queens"
1807340,2020-01-15 02:19:12 UTC,"Reviewed:  https://review.opendev.org/702231
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b599bacbcd1f915acf9712662254b2f84baab279
Submitter: Zuul
Branch:    stable/pike"
1807340,2020-01-13 14:58:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/702231"
1807340,2019-03-24 23:39:43 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1807340,2019-03-24 23:04:28 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1807340,2019-03-22 03:44:27 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1807340,2019-01-31 14:00:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/634236"
1807340,2018-12-27 13:26:36 UTC,"Hi Sean,"
1807340,2019-01-29 13:32:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/633734"
1807340,2019-01-28 14:25:43 UTC,"Reviewed:  https://review.openstack.org/627540
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a19c38a6ab13cdf2509a1f9f9d39c7f0a70ba121
Submitter: Zuul
Branch:    master"
1807340,2018-12-27 15:27:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627540"
1807340,2018-12-27 15:17:23 UTC,"Change abandoned by Maria Luisa Arches (<email address hidden>) on branch: master
Review: https://review.openstack.org/627537
Reason: rebranch"
1807340,2018-12-27 14:58:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627537"
1807340,2018-12-10 16:03:58 UTC,"Hi,"
1807340,2019-01-31 13:44:31 UTC,"Reviewed:  https://review.openstack.org/633734
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1ac56a403876fa109385ef6281c525335a613b34
Submitter: Zuul
Branch:    stable/rocky"
1807340,2018-12-10 15:46:42 UTC,"ill try an reproduce this  tommorow.
if you want to address this yourself feel free to reassign.
otherwise ill try and resolve this in the next week or two."
1807342,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1807342,2018-12-12 02:16:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1807342,2018-12-20 05:39:13 UTC,This bug was fixed in the package linux-oem - 4.15.0-1030.35
1807343,2018-12-07 08:26:44 UTC,"StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f7bfa6f5ed8 ""*** Error in `%s': %s: 0x%s ***\n"") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f7bfa6f2caf ""free(): invalid pointer"", action=3) at malloc.c:5006
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3867
 __GI___libc_free (mem=<optimized out>) at malloc.c:2968
 ?? () from /tmp/apport_sandbox_5wzp201q/usr/lib/x86_64-linux-gnu/libFLAC.so.8"
1807344,2019-07-19 16:12:45 UTC,"I can confirm this bug. I'm not sure it should be against ubiquity though.. although some files do refer to fr-latin9 (i.e. the obsolete variant), a fix might be needed in console-setup as well."
1807344,2019-12-05 09:32:13 UTC,"When I use the button ""Detect the keyboard"" and answer to the questions, it's the good keyboard that is proposed : ""Francais (azerty)""."
1807344,2019-12-05 09:29:12 UTC,Screenshot when I choose French at boot.
1807344,2018-12-08 09:08:46 UTC,The wrong keyboard default choice :
1807344,2019-12-05 09:26:24 UTC,"Now, in Linux Mint MATE 19.3 :
- If I choose ""English"" at the boot screen on the ISO, and ""French"" as the locale once the installer loads, I get the ""French"" keyboard as the default choice.
- If I choose ""French"" at the boot screen on the ISO and ""Français"" as the locale once the installer loads, I get the ""Francais (variante obsolète)"" keyboard as the default choice."
1807344,2019-07-19 16:13:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807344,2019-12-05 09:28:52 UTC,Screenshot when I choose English at boot.
1807346,2019-01-09 12:08:00 UTC,It is affecting our important installations. Please resolve this on priority
1807346,2019-03-01 10:10:14 UTC,I can reproduce the problem after a fresh deploy of Rocky 18.1.4. Then adding mutlidomain with LDAP. Doing a minor Upgrade again. Any solution for this?
1807346,2019-04-24 17:07:28 UTC,"I too facing the same issue during fresh install of Rocky 18.1.4, any permanent fix would be great."
1807346,2019-06-26 08:37:40 UTC,"Hello,"
1807346,2019-09-09 11:58:09 UTC,"facing the same issue during upgrade to rocky from queens using openstack-ansible, there is any workaround for this?"
1807346,2019-09-13 15:59:37 UTC,This issue also affects Magnum install.
1807346,2019-09-19 14:54:21 UTC,Just an update on this one. As soon as you enable multidomain even running the nova playbook fails.
1807346,2020-03-30 20:52:49 UTC,Hey all.. I hit this in Stein as well with multi-domain enabled.  Work around.. check to see if the role is already added:
1807346,2020-04-03 17:07:06 UTC,"for stein you need the patch ansible with the following patch:
the issue is the os_user_role module in ansible doesn't pass the domain along when doing the lookup for the stack_domain_admin."
1807352,2020-05-04 15:26:28 UTC,@Pascal: do you have the qemu logs for the problematic instance? By default it is under /var/log/libvirt/qemu/
1807352,2020-05-05 08:27:05 UTC,Thanks for your reply!
1807352,2020-07-05 04:17:18 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1807355,2019-08-20 01:39:32 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1807375,2019-01-24 14:22:25 UTC,"Created attachment 280717
0003-Bluetooth-btrtl-Skip-initialization-if-firmware-is-a.patch"
1807375,2019-08-08 09:21:57 UTC,The patch has been working for me since kernel 5.1.
1807375,2019-01-27 08:35:16 UTC,"Turns out it's a regression, I sent V2 patch to address the issue."
1807375,2019-01-26 03:07:43 UTC,"Created attachment 280781
0004-Bluetooth-btrtl-Expose-btrtl_device_info.patch"
1807375,2019-01-24 14:23:17 UTC,Please try these patches. It should the issue.
1807375,2018-12-07 11:43:32 UTC,"Hello,"
1807375,2019-01-24 14:22:00 UTC,"Created attachment 280715
0002-Bluetooth-btrtl-Let-btrtl_initialize-always-return-e.patch"
1807375,2018-12-19 19:35:39 UTC,"Created attachment 280099
dmesg 4.20.0-042000rc7-generic"
1807375,2019-01-14 07:30:33 UTC,"Created attachment 280459
Kernel messages from various boot states."
1807375,2019-01-13 17:03:29 UTC,"vasthusya,"
1807375,2019-01-13 09:49:13 UTC,"Created attachment 280449
Add IC_INFO(a99e, 826c) to load rtl8821c firmware"
1807375,2019-01-09 08:09:39 UTC,"(In reply to Cristian Aravena Romero from comment #1)

> Created attachment 280099 [details]
> dmesg 4.20.0-042000rc7-generic
>
> I really do not know if the problem was definitively solved. Because
> Bluetooth devices now appear in GNOME.
"
1807375,2019-01-07 10:49:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807375,2019-01-24 14:21:13 UTC,"Created attachment 280713
0001-Bluetooth-btrtl-Let-rtl_load_file-always-return-erro.patch"
1807377,2020-10-25 15:41:31 UTC,I'm facing the same issue on my lenovo yoga slim 7i pc. I'm currently on ubuntu 20.10 and have also tried 20.04 and 18.04 . Is there a fix to this?
1807377,2020-10-25 15:38:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807377,2019-01-03 16:51:51 UTC,"Hi Andy,"
1807377,2019-01-03 16:31:13 UTC,Fixed patch - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807377/comments/5
1807377,2019-01-03 10:44:41 UTC, Fix - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807377/comments/3
1807377,2018-12-07 11:46:23 UTC,"Hello,"
1807377,2019-01-03 16:30:33 UTC,FIXED PATCH
1807377,2019-01-03 09:54:43 UTC,i2c-hid: Add a small delay for Synaptics/Elan touchpanel
1807379,2018-12-07 12:26:52 UTC,"Review in progress for https://review.opencontrail.org/48075
Submitter: Ankudinov Alexander (<email address hidden>)"
1807388,2018-12-07 13:20:32 UTC,"Wifi card:
06:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
 Subsystem: Hewlett-Packard Company RTL8822BE 802.11a/b/g/n/ac WiFi adapter [103c:831b]
 Kernel driver in use: r8822be
 Kernel modules: r8822be"
1807388,2018-12-07 13:30:07 UTC,This change was made by a bot.
1807388,2018-12-13 08:45:34 UTC,It should be the same as LP: #1806472.
1807389,2018-12-11 12:41:32 UTC,Did some surgery on the 'pinta-maintainers-ubuntu-pinta-stable-disco.list' file.  Changed 'disco' to 'utopic' reveling yet another problem with the distro ...
1807389,2018-12-11 12:44:37 UTC,Found additional problems with your files (see comment).
1807393,2019-02-04 08:47:55 UTC,This bug was fixed in the package linux - 4.4.0-142.168
1807393,2018-12-07 22:03:28 UTC,Patch sent to Ubuntu kernel mailing-list: https://lists.ubuntu.com/archives/kernel-team/2018-December/097208.html
1807393,2019-01-17 14:21:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1807393,2019-01-17 17:47:32 UTC,The bug was verified in Xenial kernel 4.4.0-142.168 available in -proposed.
1807393,2019-01-23 11:00:19 UTC,Also verified that in an AWS instance running the aws kernel in -proposed:
1807396,2019-04-16 08:49:55 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/581360
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1807396,2018-12-07 15:19:10 UTC,"It's not linked to here in the bug report for some reason, but here's a link to the review in progress https://review.openstack.org/#/c/581360/"
1807396,2019-04-16 08:49:45 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1807404,2019-09-20 11:51:26 UTC,"Deepin is not a part of the snapd CI system so we cannot ensure it is correctly packaged, up to date, and operational. Having said that, is that the only snap with this property on your system or are other snaps crashing as well?"
1807404,2019-09-20 11:52:35 UTC,On second read I think I can answer my own question. Can you please share the output of:
1807404,2019-11-20 04:17:31 UTC,[Expired for snapd because there has been no activity for 60 days.]
1807406,2020-07-15 20:04:50 UTC,"Sorry, more info... looking at kern.log, the context is as follows. Note that this occurred when the machine had auto-suspended with the laptop open, and the black screen with text was already visible when I came into the room. It did not suddenly appear as a result of my triggering a return from suspend. At the end you can see the beginning of the power off process I started by pressing the power button."
1807406,2020-07-15 19:54:17 UTC,"Following up, I have made the following changes to my system recently. Two occurred within the week prior to this problem appearing, but not immediately before to my knowledge, so it's not certain that any of them are applicable. They are listed in order of first use."
1807406,2020-07-15 17:21:43 UTC,"This problem just appeared on my Spectre x360 for the first time yesterday. When laptop auto-suspends form lack of activity, the screen goes black with three messages with this error. It is unresponsive so only solution is power off and reboot by pressing and holding the power button to shut down, then pressing again to power up."
1807406,2020-03-19 20:40:01 UTC,Same here: Toshiba Portege z20t C
1807406,2019-03-27 23:18:40 UTC,"I have the exact same issue.  My keyboard and touchpad stop working after returning from suspend.  I'm not sure if this error message is related or not, but I found it in the Logs app right after they stopped working."
1807406,2018-12-11 13:01:50 UTC,"Created attachment 279953
dmesg 4.20.0-042000rc6-generic"
1807406,2018-12-07 15:46:45 UTC,"Hello,"
1807406,2018-12-07 15:30:06 UTC,This change was made by a bot.
1807406,2019-07-14 13:53:52 UTC,I also started having this same issue on my HP Spectre x360.
1807408,2018-12-07 15:30:12 UTC,This change was made by a bot.
1807408,2018-12-13 08:49:07 UTC,Does it connect to an internal hub or to an external hub?
1807408,2018-12-13 10:27:14 UTC,Yes.
1807410,2019-02-19 12:59:27 UTC,it seems like a bug. what happens when removing one of them?
1807410,2019-02-21 09:19:33 UTC,"If I delete one of them, all rules on the ovs related to the source port will be removed, but in database there still exists the tap-flow on the source port"
1807416,2019-07-20 03:59:20 UTC,Same here. I wonder Ubuntu team do anyway
1807416,2018-12-07 16:30:06 UTC,This change was made by a bot.
1807416,2019-04-11 16:18:44 UTC,I see the same in Ubuntu 18.04.2.
1807420,2018-12-15 00:05:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807423,2019-04-09 07:13:12 UTC,https://github.com/snapcore/snapcraft/pull/2527
1807432,2018-12-07 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1807432,2018-12-07 19:01:56 UTC,"Here is the details on a bare metal ubuntu 18.04 LTS server running an IO benchmark:
# uname -a
Linux xxx 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1807432,2018-12-07 19:46:46 UTC,These are all the logs I have...
1807432,2019-07-29 06:45:27 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/"
1807433,2019-07-01 00:38:04 UTC,This is fixed in 19.04.
1807434,2019-12-11 16:25:53 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.opendev.org/623489"
1807439,2019-05-08 13:45:24 UTC,"Hello Joy, or anyone else affected,"
1807439,2019-05-08 13:45:48 UTC,"Hello Joy, or anyone else affected,"
1807439,2019-05-08 13:48:24 UTC,"Accepted, thanks."
1807439,2019-05-08 13:49:48 UTC,"Oh, and a special thanks for explaining clearly all the details in the bug description. That got me up to speed quickly and allowed me to review without having to ask any questions!"
1807439,2019-05-29 01:33:10 UTC,Hello there!
1807439,2019-06-03 08:47:23 UTC,"The verification of the Stable Release Update for openvpn has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1807439,2019-05-31 19:11:00 UTC,"Successfully verified xenial, bionic, and cosmic."
1807439,2019-05-31 19:11:57 UTC,Verified using same test data allowing for interoperability testing between the various releases and with fips for xenial and bionic.
1807439,2019-05-31 19:20:58 UTC,"verification done on following:
xenial: openvpn-2.3.10-1ubuntu2.2
bionic: openvpn-2.4.4-2ubuntu1.2
cosmic: openvpn-2.4.6-1ubuntu2.1"
1807439,2019-05-08 13:45:06 UTC,"Hello Joy, or anyone else affected,"
1807439,2019-06-03 09:19:28 UTC,This bug was fixed in the package openvpn - 2.3.10-1ubuntu2.2
1807439,2019-05-31 14:26:57 UTC,Testing in progress...
1807439,2019-01-11 20:49:44 UTC,This bug was fixed in the package openvpn - 2.4.6-1ubuntu3
1807439,2019-06-03 09:18:58 UTC,This bug was fixed in the package openvpn - 2.4.4-2ubuntu1.2
1807439,2019-01-10 20:42:19 UTC,"Applied fixes for above comments. After some team discussion, decided to use sha256 for internal hash rather than sha1 in xenial as well. Internal hash is never communicated externally. Performed additional interoperability testing successfully using same test parameters as previously."
1807439,2019-01-10 21:15:26 UTC,"This bug has been reported:
1.Upstream Bug: https://community.openvpn.net/openvpn/ticket/725
2.Suse Bug report: https://build.opensuse.org/package/view_file/network:vpn/openvpn/openvpn-fips140-2.3.2.patch"
1807439,2018-12-10 14:31:37 UTC,"Hi,
I'm really unsure what the expectation here is now.
This does not contain steps to reproduce the issue nor any suggested changes to make it work better.
Both would be needed."
1807439,2018-12-10 14:33:58 UTC,"Checked on IRC, there are debdiff, testing data, etc...
Please set back to new once that was made available."
1807439,2018-12-13 16:27:09 UTC,"Thanks for the first update, when you attach the rest of the test data please make sure to not only add words like ""comprised establishing a tls connection between an openvpn client and server"" but more like:
#1 fresh container
$ command 1
$ command 2
<result>"
1807439,2018-12-13 16:34:12 UTC,build log for disco: https://launchpad.net/~j-latten/+archive/ubuntu/joyppa/+build/15743680
1807439,2018-12-13 16:36:15 UTC,debdiff.disco
1807439,2018-12-13 16:42:25 UTC,"testcase-data contains some of the data produces as a result of interoperability testing. It is applicable to xenial, bionic and disco."
1807439,2019-06-03 08:57:22 UTC,This bug was fixed in the package openvpn - 2.4.6-1ubuntu2.1
1807439,2018-12-13 18:03:19 UTC,build log for bionic: https://launchpad.net/~j-latten/+archive/ubuntu/joyppa/+build/15743676
1807439,2018-12-13 18:17:18 UTC,build log for xenial: https://launchpad.net/~j-latten/+archive/ubuntu/joyppa/+build/15743720
1807439,2018-12-13 18:34:22 UTC,"The xenial patch has additional code. In version 2.3.10, openvpn uses MD5 for PRF and internally for configuration status verification. FIPS 140-2 permits MD5 for PRF, but not as a hash for internal verification.  Subsequent versions of openvpn (2.4) was changed upstream to not use MD5, instead uses SHA256. The attached patch provided by atsec uses SHA1 instead of MD5."
1807439,2018-12-13 17:05:22 UTC,"Hi Christian,"
1807439,2018-12-13 21:59:07 UTC,"2 testcases using same parameters for prior testcases, except that installed FIPS-mode libcrypto.so to test and ensure FIPS-mode libcrypto.so honors the flag to allow MD5 in PRF and does not cause openvpn to segfault because MD5 is missing."
1807439,2019-01-07 16:40:17 UTC,Taking a look
1807439,2019-01-08 13:02:31 UTC,Thanks for all this testing!
1807440,2019-09-20 13:38:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807440,2019-09-24 15:31:12 UTC,The sensible-utils package which provides the sensible-browser script is in sync with the version of the package in Debian. Would you mind forwarding this bug to Debian? Thanks in advance.
1807442,2019-07-03 17:12:12 UTC,probably another job running
1807445,2020-02-14 18:46:08 UTC,The theme you are using is not one of the Ubuntu MATE themes. Please report this issue to the theme maintainer.
1807450,2019-04-04 15:56:15 UTC,"https://bugs.launchpad.net/bugs/1823199
Is the new one covering the critical part."
1807450,2019-04-04 15:48:04 UTC,Ups.. now I am aware that I missread the bug title. I have fixed a bug that you can't close the window.
1807450,2019-04-04 15:46:07 UTC,"The Auto Update of the window is broken.
There is some code for this but I am afraid it is a copy and paste left over from the original implementation."
1807450,2019-04-04 14:04:07 UTC,"I tried to address the bug title here:
a dummy image would allow to keep the cover window open when you found a nice place and size for it, but the new track doesn't have a cover attached. when another track WITH cover is loaded the window would be populated again."
1807450,2019-04-03 21:32:44 UTC,Can we load a dummy image like for the deck cover art?
1807450,2019-04-03 20:24:39 UTC,"2.2.0 is also effected, not 2.1.8 even not compiled with qt5."
1807450,2019-04-03 19:26:37 UTC,"This is a critical bug, because you cannot use the Mixxx GUI anymore in this state."
1807450,2019-04-03 22:00:32 UTC,"Or just nothing like before:
https://github.com/mixxxdj/mixxx/pull/2073"
1807452,2018-12-09 20:00:51 UTC,Thanks
1807452,2018-12-09 15:54:56 UTC,"1. Reported to upstream https://gitlab.gnome.org/GNOME/nautilus/issues/780
2. launchpad should recognize such links to upstream - see https://bugs.launchpad.net/launchpad/+bug/1738870 ."
1807452,2018-12-09 15:33:53 UTC,"The issue looks like an upstream request, to be reported on https://gitlab.gnome.org/GNOME/nautilus/issues/"
1807457,2018-12-07 21:19:51 UTC,Error state from check_disk on nagios unit.
1807457,2020-03-03 03:38:26 UTC,Current versions of the charm are OK now without needing the extra switch.
1807457,2018-12-10 17:50:03 UTC,I was able to put in a temporary fix in place by adding -X squashfs to the check_all_disks command line in /etc/nagios-plugins/config/disk.cfg
1807457,2018-12-07 23:14:01 UTC,That's shipped out by the nrpe charm isn't it?
1807457,2018-12-10 17:47:49 UTC,"Haw, this is specifically the nagios-charm local monitoring config."
1807457,2018-12-07 21:39:03 UTC,Also happens with canonical-livepatch charm which uses a snap.
1807457,2018-12-07 21:26:27 UTC,"aws-integrator is the charm that brings that snap into play, however this is related to prior bug on charm-nrpe to ignore snaps by default.  I believe it's an upstream nagios package bug."
1807457,2018-12-07 21:22:19 UTC,"It appears that this is actually a result of having amazon-ssm-agent snap installed, which I believe means this is specific to AWS cloud monitoring."
1807457,2018-12-07 21:40:32 UTC,"ultimately, we should update the upstream nagios plugin code for check_disk to always ignore snap loop mounts specifically that are of the type that snaps use (we don't want to ignore /snap in upstream if a user mounts a non-snapd based filesystem into /snap).  This would ultimately help the wider community with snap adoption."
1807459,2018-12-07 22:30:29 UTC,"Also, you haven't specified the MAAS version, nor the version used for commissioning."
1807459,2018-12-10 20:36:10 UTC,"That's fair enough.  In reality, I was a bit too general in the summary, when I said ""disk"" in relation to not touching them, what I meant was ""usb or removable"" disks, not onboard devices.  I completely understand why we'd want to wipe onboard disks.  And from your comments, it appears that this may actually be unintended behaviour in wiping my USB sticks."
1807459,2019-07-31 04:17:28 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1807459,2018-12-07 21:41:43 UTC,"MAAS will continue to wipe the superblock of all available disk. That won’t vhange. That’s fine by design and to ensure MAAS can always deploy a machine. Otherwise, you could have grub installed on other devices and prevent machines from successfully deploying or booting in other installations on other disks."
1807462,2018-12-08 15:57:40 UTC,See also bug 1571855.
1807464,2020-03-31 19:45:52 UTC,"This appears to be described in upstream project bug:
https://bugs.launchpad.net/designate/+bug/1802227"
1807464,2018-12-07 21:58:37 UTC,experiend while working around https://bugs.launchpad.net/charm-designate-bind/+bug/1806485
1807464,2018-12-17 09:34:08 UTC,Drew - is there a bug raised against the designate project for this issue?
1807464,2019-08-21 14:32:30 UTC,"James, I think you may be on to something, this should be filed against upstream.  If the record being looked up comes back from the bind server being controlled by designate as being non-authoritative, it should be assumed that the bind server is performing recursive lookups and that it's no longer hosted in the local zone files."
1807466,2019-05-10 18:07:48 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1807466,2018-12-20 17:22:49 UTC,"This bug is fixed with commit f55bb17d to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=f55bb17d"
1807466,2019-02-27 21:48:59 UTC,Added the cloud-images project to capture the image changes that will be required to make this available as a transport by default.
1807468,2019-05-03 17:12:31 UTC,"Yes, accelerated is normal."
1807468,2018-12-07 23:12:23 UTC,"This is the fall-back render mode where zone edges overlap.  Since Cairo doesn't draw by layer, the zones have their alpha channels added together."
1807479,2018-12-08 02:04:41 UTC,I went ahead and submitted a PR here:
1807479,2019-07-02 15:55:18 UTC,"@earlruby.org I think you already filed the PR at the best place, i.e. at upstream. Ubuntu (and other distributions as well AFAIK) preferes carrying patches only when it is critical to the distribution and preferably only for a shorted period until it becomes available in a new upstream release.
This patch don't seem to fit either category unless upstream accepts the patch."
1807479,2019-03-07 23:32:22 UTC,Is there a different repository where I should submit this PR?
1807479,2018-12-08 01:06:59 UTC,"I can fix this bug if someone can point me to the source repo. I found https://github.com/rhinstaller/system-config-kickstart on-line, but I'm not sure if Ubuntu pulls from the RHEL source repo so I don't know if fixing it there will help or not."
1807479,2019-01-18 19:13:07 UTC,Can I make this bug public?
1807479,2019-01-19 05:27:48 UTC,I don’t see why not. I fixed it and submitted a PR but can’t get anyone to look at the PR.
1807488,2018-12-08 15:18:28 UTC,It will be pushed by the clearance value.  We could have an option somewhere to push in grid increments but I think that might be more work than benefit but maybe someone's up for it.
1807497,2019-02-06 07:28:20 UTC,Maybe the destination folder is not writable?
1807498,2020-01-28 03:25:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807499,2019-08-08 12:37:10 UTC,"According to your post, I have modified /lib/udev/rules.d/69-lvm-metad.rules the line 96, but no.
# the ACTION!=""remove"", ENV{violently _pv_gone}==""1"", RUN+=""/usr/bin/systemd-run /sbin/ LVM pvscan --cache $major:$minor"", GOTO="" violently _end""
The ACTION!=""remove"", RUN+=""/sbin/ LVM pvscan --cache $major:$minor --activate ay"""
1807499,2018-12-08 21:36:44 UTC,A the moment I can see following solutions:
1807503,2018-12-08 14:27:33 UTC,"StacktraceTop:
 __libc_message (action=(do_abort | do_backtrace), fmt=0x7fcf82025796 ""%s"", fmt=0x7fcf82025796 ""%s"", action=(do_abort | do_backtrace)) at ../sysdeps/posix/libc_fatal.c:181
 __GI___libc_fatal (message=<optimized out>) at ../sysdeps/posix/libc_fatal.c:191
 __GI___netlink_assert_response (fd=16, result=result@entry=-1) at ../sysdeps/unix/sysv/linux/netlink_assert_response.c:102
 __netlink_request (h=h@entry=0x7fcf16371c90, type=type@entry=18) at ../sysdeps/unix/sysv/linux/ifaddrs.c:174
 getifaddrs_internal (ifap=ifap@entry=0x7fcf16371d58) at ../sysdeps/unix/sysv/linux/ifaddrs.c:336"
1807503,2019-04-28 15:55:04 UTC,Upstream bug reports (not mine):
1807506,2018-12-09 21:17:32 UTC,What would you like to see as the output for this?
1807506,2018-12-11 14:53:34 UTC,Tim Penhey <email address hidden> writes:
1807506,2019-11-01 20:16:23 UTC,This came up in a discussion with folks today. They're doing HPC with hundreds of nodes and the status output is useless because of the number of units involved. Just have the applications/base status would be useful and a list-applications would be one path towards that.
1807507,2020-02-10 09:31:48 UTC,"this is no longer heppinng in
1.0beta2 (c38fd11e78, 2020-02-09)"
1807507,2018-12-11 15:54:32 UTC,">Do you maybe mean that when the clip is released, it does not go back to the layer it came from?
"
1807507,2018-12-12 00:38:17 UTC,"It would require adding the original location of an object in the defs to the definition in the defs, and adding an additional Inkscape-specific value to the document."
1807507,2018-12-08 22:29:01 UTC,"The clipping/masking path is removed from all layers, and moved into the defs section (a kind of 'hidden cupboard') of the SVG file, as far as I know."
1807508,2019-04-12 20:20:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807508,2019-12-09 13:13:20 UTC,There was a specific tweak for this application which probably get lost in the latest upstream rebase. I will try to bring it back
1807508,2020-01-02 18:51:55 UTC,It seems fixed in gnome-weather version 3.34 without any change on Yaru side
1807511,2018-12-09 14:02:48 UTC,apport information
1807511,2019-11-12 21:33:51 UTC,"The issue has been solved since 5.3.0-rc1 , closing https://bugzilla.kernel.org/show_bug.cgi?id=201077"
1807511,2019-05-23 14:03:21 UTC,"I have bisected this problem here: https://bugzilla.kernel.org/show_bug.cgi?id=201077
also reported it"
1807511,2019-03-15 13:48:20 UTC,Same annoying problem AMD APU 9720P RX 540.
1807511,2018-12-16 23:05:37 UTC,https://bugs.freedesktop.org/show_bug.cgi?id=109073
1807511,2018-12-16 06:14:00 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu"
1807511,2018-12-15 16:19:37 UTC,I am missing allot of powerplay failed to send message errors in dmesg when booting without power cable plugged in the laptop... Also allot less freezes...
1807511,2018-12-10 18:49:45 UTC,Mainline kernel had to be installed with secure boot disabled...
1807511,2018-12-10 04:46:41 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20-rc6 kernel[0]."
1807511,2018-12-09 14:02:50 UTC,apport information
1807511,2018-12-09 14:02:49 UTC,apport information
1807511,2018-12-09 14:02:46 UTC,apport information
1807511,2018-12-09 14:02:44 UTC,apport information
1807511,2018-12-08 20:20:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1807511,2018-12-08 22:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1807511,2018-12-09 14:02:31 UTC,apport information
1807511,2018-12-09 14:02:32 UTC,apport information
1807511,2018-12-09 14:02:34 UTC,apport information
1807511,2018-12-09 14:02:45 UTC,apport information
1807511,2018-12-09 14:02:37 UTC,apport information
1807511,2018-12-09 14:02:39 UTC,apport information
1807511,2018-12-09 14:02:40 UTC,apport information
1807511,2018-12-09 14:02:41 UTC,apport information
1807511,2018-12-09 14:02:42 UTC,apport information
1807511,2018-12-09 14:02:35 UTC,apport information
1807513,2020-10-27 12:33:58 UTC,"No I was wrong.
In my case this only happens with the certificate with a strange Issuer name like ""x00d\x00b\x00_\x00M\x00a\x00n\x00u\x00f\x00a\x00c\x00t\x00u\x00r\x00e\x002\x000\x001\x005\x000\x006\x001\x007"". Only this certificate fails to load."
1807513,2020-02-21 08:51:35 UTC,This happens when `mokutil --use-db` setting is applied. With `--ignore-db` this doesn't happen. I suppose this is only applicable for situaltions  where Secure Boot's db / KEK / PK are modified by the user.
1807513,2018-12-08 18:55:33 UTC,apport information
1807513,2018-12-08 18:55:32 UTC,apport information
1807513,2018-12-08 18:55:30 UTC,apport information
1807513,2018-12-08 18:55:28 UTC,apport information
1807513,2018-12-08 18:55:26 UTC,apport information
1807513,2018-12-08 18:55:23 UTC,apport information
1807513,2018-12-08 18:55:25 UTC,apport information
1807513,2018-12-08 18:55:20 UTC,apport information
1807513,2018-12-08 18:55:16 UTC,apport information
1807513,2018-12-08 18:55:15 UTC,apport information
1807513,2018-12-08 18:55:13 UTC,apport information
1807513,2018-12-08 18:55:12 UTC,apport information
1807513,2018-12-08 18:55:09 UTC,apport information
1807513,2018-12-08 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1807513,2018-12-08 18:55:21 UTC,apport information
1807513,2018-12-08 18:55:19 UTC,apport information
1807514,2019-01-18 19:12:00 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1807514,2019-02-20 15:16:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807514,2020-05-15 23:58:23 UTC,systemd-shim is a xenial package.  Your distro information is bionic.  Am I right to assume that this happened while you were trying to upgrade a xenial system to bionic?  I have to admit I just ran into this myself.
1807514,2020-07-15 04:17:27 UTC,[Expired for systemd-shim (Ubuntu) because there has been no activity for 60 days.]
1807514,2020-08-18 05:27:33 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1773859, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1807517,2018-12-10 17:24:13 UTC,"Yes, it's because of the confusion with the BMP format."
1807517,2019-12-04 10:44:38 UTC,Migrated to GL:  https://gitlab.com/inkscape/inbox/issues/1278
1807517,2018-12-08 22:31:20 UTC,"yes, I can see that would be confusing; although to be perfectly honest, nobody these days still uses the bmp format, it has more or less gone the way of the dodo."
1807517,2018-12-08 20:38:06 UTC,"um, what is the difference between the two?
in my experience, 'bitmap' is the more common of the two."
1807517,2018-12-08 22:26:28 UTC,I think it's the naming overlap between Windows bmp file format which causes the confusion.
1807524,2018-12-08 22:25:20 UTC,"I agree that for layers, I wouldn't expect the filter to carry over, unlike for groups, where I would."
1807524,2018-12-10 10:34:37 UTC,Yes right.  I'm only suggesting this for the special groups called layers.  Not for all groups.
1807524,2019-12-11 06:02:20 UTC,Not reproduced in 1.0beta2.  So not migrating.  Closing.
1807524,2019-12-11 06:08:27 UTC,Actually I was wrong about that.
1807527,2018-12-10 00:53:19 UTC,Implementation proposed in https://review.openstack.org/#/c/623582/
1807527,2018-12-12 13:42:29 UTC,"It sounds reasonable that some floating IP pool is preferred when a deployment has multiple floating IP pools. From my operator experiences, there are cases where some floating IP pool is a preferred route and other pools are optional. In such cases, it sounds reasonable that the preferred pool is pre-selected."
1807527,2019-03-11 19:13:03 UTC,"Change abandoned by Lars Kellogg-Stedman (<email address hidden>) on branch: master
Review: https://review.openstack.org/623582"
1807528,2018-12-08 19:30:08 UTC,This change was made by a bot.
1807528,2018-12-08 19:53:52 UTC,"I'm not sure how to close it, but it's resolved. I may have forgotten to reboot after installing the Synaptic package."
1807528,2019-12-27 03:35:53 UTC,Closing with comment #3
1807529,2020-05-09 09:05:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807529,2020-05-09 09:06:00 UTC,I'm also getting this bug on Ubuntu MATE 20.04 LTS with the exact same error message
1807533,2018-12-15 16:51:20 UTC,It's merged in rocky already.
1807533,2018-12-15 16:37:34 UTC,What about rocky? :(
1807533,2018-12-08 21:13:47 UTC,Testing from stable/queens branch.
1807533,2018-12-11 10:31:29 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/624342"
1807533,2018-12-09 18:11:32 UTC,stable/rocky has the same issue as well.
1807533,2018-12-11 10:51:25 UTC,"Change abandoned by Serhat Rıfat Demircan (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/624342
Reason: abandoned due to COMMITID backport"
1807535,2020-11-09 08:40:10 UTC,"Hello,
do you still have this issue with the latest 4.15 kernel on Xenial?
Thanks"
1807535,2021-01-09 04:17:27 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1807537,2020-07-12 12:54:35 UTC,Same with Ubuntu 20.04 LTS kernel 5.4.0-40-generic
1807537,2021-02-04 20:32:17 UTC,???
1807537,2021-02-04 13:10:42 UTC,"We are on 2021-02-04, I am using ubuntu 20.04 and we have the same problem."
1807537,2020-07-15 14:49:12 UTC,Same with peppermint 10-amd-64
1807537,2020-07-01 12:42:48 UTC,Same with Ubuntu 20.04 LTS kernel 5.4.0-39-generic
1807537,2019-01-10 17:27:33 UTC,"I had exactly the same problem. I'm running 18.10, grub2-common 2.02+dfsg1-5ubuntu8"
1807537,2020-04-25 07:41:11 UTC,Same issue with Ubuntu 20.04 kernel 4.19.13
1807537,2019-06-23 13:34:04 UTC,I had a look at the recovery-fsck option on this in exploring https://askubuntu.com/questions/1153259/problem-with-grub-recovery-menu-on-xubuntu-18-04-2 and had this issue.
1807537,2019-06-14 20:17:40 UTC,"Same issue with Ubuntu 18.04 and kernel version 4.20.0, Asus zenbook ux533fd"
1807537,2019-01-10 17:27:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807537,2020-04-25 07:48:41 UTC,Also failed with kernel 5.6.7 on Ubuntu 20.04
1807539,2018-12-08 22:59:37 UTC,"It's also interesting that when I attach an external monitor to an external mode in tent mode, the screen orientation changes to standard mode and can therefore no longer be used in tent mode because everything is upside down. Should I open another bug report for this?"
1807539,2018-12-09 15:20:22 UTC,"The issue looks like an upstream one, could you report it as well on https://gitlab.gnome.org/GNOME/gnome-shell/issues/ ?
The fact that the screen is forced back to its non-rotated mode when connecting the other display seems like it could be the same bug (shell refuses to handle rotations when an external screen is connected)"
1807539,2018-12-12 20:24:08 UTC,Reported it upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/847
1807539,2019-07-22 04:07:30 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1807540,2018-12-09 15:21:23 UTC,"Thank you for your bug report. The issue is probably an upstream one, could you report it as well on https://gitlab.gnome.org/GNOME/gnome-shell/issues/ ?"
1807540,2018-12-12 20:21:52 UTC,Reported it upstream as well: https://gitlab.gnome.org/GNOME/gnome-shell/issues/846
1807540,2019-07-22 04:08:04 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1807543,2018-12-31 10:30:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807544,2020-03-21 07:40:59 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1807544,2019-06-27 09:17:26 UTC,"I'd say that, configurable options notwithstanding (I like them), any properly thought-out piece of software should have a well-chosen set of default preferences."
1807544,2018-12-10 18:50:49 UTC,I think the best option is to let the user determine that via a preferences setting: just a list of extensions to be included.
1807544,2018-12-10 17:44:17 UTC,"Inkscape removes files from the list of recent documents that are not present on the file system anymore, so if they still show up for you, they're cached somewhere (if you happen to open them from within a browser, the browser will save a copy to your cache folder, from where it is loaded by Inkscape)."
1807544,2018-12-10 14:05:23 UTC,"I've also been frustrated with the Open Recent menu, recently, but for a slightly different reason.  In my work providing support for Inkscape (mostly in forums) I'm always opening other people's files (of any format which Inkscape supports)."
1807545,2018-12-09 02:00:03 UTC,This change was made by a bot.
1807546,2018-12-09 22:10:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807547,2018-12-09 15:18:17 UTC,the log is showing internet access failing and the grub deb failing to download
1807553,2018-12-09 05:22:08 UTC,I guess the install tree isn't cleaned before re-build?
1807557,2019-01-16 16:54:55 UTC,"Thank you for your bug report. The keyboard navigation is buggy, indeed it looks like those widgets needs to have focus properties changed"
1807557,2020-03-31 20:00:58 UTC,The keyboard navigation issue has been fixed in newer Ubuntu versions
1807559,2019-09-06 02:04:27 UTC,We can close this bug
1807559,2019-08-29 01:10:50 UTC,Since having no metadata defined is a deployment choice we have decided this better to abandon Soumya PS and handle this through blacklist in the downstream  CI
1807559,2018-12-24 09:32:46 UTC,"Change abandoned by Liu Xiaolei (<email address hidden>) on branch: master
Review: https://review.openstack.org/623924"
1807559,2018-12-09 08:54:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/623924"
1807559,2019-07-19 21:34:41 UTC,Rather than assigning a random value to resource name a skip check can be added if the deployment does not have image metadata. If the resource_types is empty and we can skip the test.
1807559,2019-08-02 14:11:08 UTC,"Change abandoned by Soumya Purohit (<email address hidden>) on branch: master
Review: https://review.opendev.org/672346
Reason: Abandoning as blacklisted in downstream CI"
1807569,2021-02-05 19:31:23 UTC,After testing on Arch (no netplan)
1807569,2019-08-26 08:49:02 UTC,"I have the same problem here. We depend on RAs for gateway configuration as router belongs to our provider, but we utilize specific OUTBOUND IPv6 for our services."
1807569,2019-08-26 19:17:23 UTC,Thanks for filing the bug.
1807569,2019-08-27 19:20:56 UTC,"Hi Ryan,"
1807569,2019-10-27 04:17:37 UTC,[Expired for netplan because there has been no activity for 60 days.]
1807569,2019-10-27 04:17:38 UTC,[Expired for netplan.io (Ubuntu) because there has been no activity for 60 days.]
1807569,2021-02-05 16:03:33 UTC,Can we get this reopened (and solved)?
1807592,2019-09-26 20:06:44 UTC,Hello !
1807595,2020-03-07 11:06:47 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1807599,2018-12-09 19:55:09 UTC,It looks like a problem with the document portal. James can you please have a look?
1807600,2020-06-16 23:40:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807603,2018-12-20 17:44:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807603,2018-12-20 17:49:23 UTC,"This seems to have been deliberately removed:
https://bugzilla.gnome.org/show_bug.cgi?id=793824"
1807603,2020-04-29 10:46:29 UTC,Exists in Ubuntu 20.04 LTS.
1807605,2018-12-09 18:00:06 UTC,This change was made by a bot.
1807608,2018-12-09 18:44:08 UTC,"Hello,"
1807608,2018-12-10 18:39:29 UTC,"Created attachment 279925
dmesg 4.20.0-042000rc6-generic"
1807608,2018-12-10 21:44:09 UTC,"Created attachment 279927
dmesg 4.20.0-042000rc6-generic (restart)"
1807615,2019-02-14 00:30:18 UTC,"Besides ""no default gateway"" I had this in cloudinit-userdata:"
1807615,2019-02-14 09:45:37 UTC,Back to the behavior in #16. I think there is something wrong in how bootcmd is generated by Juju or processed by cloud-init.
1807615,2019-02-14 12:53:38 UTC,Pull-request:
1807615,2019-02-14 12:54:50 UTC,Subscribed ~field-high (Juju) to expedite this https://github.com/juju/juju/pull/9751
1807615,2020-05-29 18:58:45 UTC,"I believe this issue was resolved outside of the charm.  If that is not the case, please set this bag back to a ""New"" status and add an updated comment/reproducer.  Thank you."
1807615,2019-02-18 05:54:39 UTC,"By the way, Ed, in your cloud-init attachments https://bugs.launchpad.net/juju/+bug/1807615/comments/6 I can see the following:"
1807615,2019-02-25 11:14:40 UTC,https://github.com/juju/juju/pull/9782 is a backport of this to 2.5
1807615,2019-02-13 20:26:10 UTC,"@James P - I'll set up an environment to recreate.  Certainly half explains it, but adds the confusion why cloud-init isn't getting an IP from the host VM.  Can't see why it's a GCE specific thing, sounds more like a delay in the fan network coming up?"
1807615,2019-02-14 13:05:11 UTC,I am facing the same issue. Work-around at this moment with Juju 2.5 is:
1807615,2019-02-13 20:10:41 UTC,Routing table for that container:
1807615,2018-12-10 12:17:03 UTC,machine-0-lxd-14.log attached
1807615,2019-02-11 12:09:29 UTC,Would it also be possible to get the contents of /var/lib/cloud ?  that might give us a bit more of a clue as to what's going on here.
1807615,2019-02-11 12:05:51 UTC,(from cloud-init-output.log)
1807615,2019-02-11 12:02:23 UTC,OK so here is the root cause:
1807615,2019-02-05 07:45:10 UTC,is any more info required from us?  Note this bug will be marked for expiry soon.
1807615,2018-12-15 09:07:47 UTC,/var/log/cloud-init* logs
1807615,2018-12-15 09:06:33 UTC,Adding /var/log/juju/*.logs
1807615,2018-12-14 15:05:24 UTC,Ed - any chance you can attach all of the log files in /var/log/juju and /var/log/cloud-init* to this bug report? that might tell us a bit more as to what's not happening correctly.
1807615,2018-12-14 15:03:41 UTC,enable-os-refresh-update = true so units should get an update call before the charm is installed and executed; the referenced aodh bug may have the same root cause.
1807615,2018-12-10 12:15:04 UTC,Post discussion with James P - this failed again this morning.  Here is the the model config:
1807615,2019-02-13 20:09:05 UTC,I managed to reproduce this in an environment where there is no default gateway at all and package downloads are only doable via a proxy server. I do not recall the same happening when a default gateway was configured.
1807618,2018-12-11 16:47:21 UTC,"thank you for your bug report, that looks like a local issue/corruption rather than an udisk bug though"
1807621,2019-06-14 04:17:17 UTC,[Expired for qpdfview (Ubuntu) because there has been no activity for 60 days.]
1807621,2018-12-10 00:52:30 UTC,"I had updates & hadn't rebooted, so re-tried after boot to same results."
1807621,2019-04-14 06:44:12 UTC,"In qpdfview 0.4.17~beta1+git20180709-2, opening from Firefox, pcmanfm-qt, and terminal, all work without problems. Sure, there's the complaint about the icon, but that's not particularly surprising. If you still have the problem, please attach an example PDF file and the specs of your machine."
1807621,2018-12-10 00:19:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807621,2018-12-09 22:52:11 UTC,"have you verified this is a bug before reporting it ?
have you looked at the theme - it appears to be a KDE theme
have you tried installing the the missing theme ?"
1807621,2018-12-10 00:24:41 UTC,this bug hit my inbox; so I booted 18.10 on x86 & tried it
1807622,2019-08-20 01:38:52 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1807626,2021-01-07 15:07:21 UTC,Same issue here. This left snapshot entry should be deleted when the cloned child volume will be deleted.
1807627,2019-01-01 14:29:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807627,2019-01-01 14:38:40 UTC,"it is the post-installation script that always returns 1, after throwing errors about unsafe symlinks encountered in /var/log/journal/. but there are no symlinks at all. Seems it is the systemd-tmpfiles --create call that throws this errors."
1807627,2019-06-19 16:53:51 UTC,"This affected me too, breaking a system in the middle of a release upgrade."
1807628,2018-12-10 04:39:40 UTC,Trace:
1807628,2018-12-12 11:51:59 UTC,I sent a fix: https://github.com/lxc/lxcfs/pull/262
1807628,2019-04-11 22:49:02 UTC,Any updates on this one? This hit us again (see latest internal incident report).
1807642,2020-03-07 15:43:34 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1807647,2018-12-19 00:39:35 UTC,"Oddly, this is exactly what I need."
1807647,2019-11-12 05:38:00 UTC,"The Full Intro + Outro and Fade At Outro Start modes added in https://github.com/mixxxdj/mixxx/pull/2103 kinda do that if you don't set the intro end or outro start cues. The difference is that they would start the new song at 0:02 (3 seconds before 0:05). In the case where the intro start point is left at its autodetected point, this works fine because the automatic placement is where the first sound is. However, if you move the intro start point later in the track, it would not work as desired."
1807647,2018-12-19 07:24:19 UTC,I think so.
1807647,2018-12-16 22:42:22 UTC,https://bugs.launchpad.net/mixxx/+bug/1808725
1807647,2018-12-19 07:08:57 UTC,"So we need to play silence instead of the tracks intro in you cade, right?
The track starts in this case appubt on a beat, right? Is this intended?"
1807647,2018-12-16 22:35:39 UTC,"OK this is by design. When designing the gap mode (negative transition) we did not consider your use case. Normally the people want to have the ""into"" and not an abrupt start on a beat in that mode. I am not sure how to improve the situation for you?
I think we need a special type of transition for this?"
1807647,2018-12-11 20:28:43 UTC,"Is 'Jump to main cue point on track load' option enabled in your Preferences, under Decks, in 'Deck options' section?"
1807647,2018-12-12 06:04:04 UTC,"Yup. The *first* song that starts playing when AutoDJ is enabled starts at the cue point, the rest do not."
1807647,2018-12-16 22:39:31 UTC,The gap is generated by cuing the track into the lead in. I think the track should be loaded at this point in gap mode to avoid surprises. I will file a separate bug.
1807647,2018-12-16 01:56:33 UTC,"The tracks ""load"" at the cue point; the waveform before the cue point is darker than the waveform after it (which is the ""normal"" brightness) using the Deere skin."
1807647,2018-12-15 23:04:20 UTC,"Do the tracks always ""load"" at the cue point?
That is currently the only point where the track is seeked to the cue point.
Is this broken? I cannot confirm it here."
1807654,2018-12-10 06:34:33 UTC,after reopening libreoffice.
1807654,2018-12-10 06:35:04 UTC,a confirmation dialog.
1807654,2018-12-10 06:36:02 UTC,"It is only libreoffice, not other apps."
1807656,2018-12-12 02:58:40 UTC,Done.
1807656,2018-12-11 19:14:51 UTC,"@Gabriel, I doubt you request will get implemented as a single commit so please break this into two separate bug reports.  There is no way in Launchpad to close multiple bugs in a single bug report."
1807661,2018-12-10 20:25:49 UTC,That is an incompatibility between numpy and casacore. Please make sure that they are compiled against the same API version. From the terminal log:
1807662,2018-12-10 09:35:28 UTC,https://pastebin.canonical.com/p/PfTnD65fYw/ is an example diff which gets it working.
1807662,2019-05-31 13:58:12 UTC,"I've sent a PR to Twisted for this, with quite a lot more work to get things like EPSV ALL working, to add tests, and a bunch of other bits and pieces:"
1807665,2019-02-18 01:11:35 UTC,2019-02-17 19:30 QA-Test Lubuntu 19.04 daily (live) x86_64
1807665,2018-12-10 08:07:58 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1807665,2019-02-05 02:28:19 UTC,"this may still exist; x86 & gone & I forgot, but discovered a 'new' bug
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1814490
that may be a duplicate of this one... 19.04 x86_64"
1807678,2018-12-10 11:22:43 UTC,The lack of support for deviceid 12d1:1001 in the linux serial driver option  is not an usb_modeswitch bug.
1807681,2019-05-19 04:17:52 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1807681,2019-02-19 13:21:00 UTC,Is this still an issue?
1807682,2018-12-10 10:30:06 UTC,This change was made by a bot.
1807682,2019-01-11 15:03:09 UTC,"I got the same issue. ""systemctl status systemd-tmpfiles-setupd-dev.service"" yields the same response. But my system (Ubunutu 18.04.1) is starting properly and there are no problems when using it.
In /var/log/syslog these lines precede the error:
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Started Apply Kernel Variables.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/cuse, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/autofs, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/btrfs-control, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/userio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/vfio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/vfio/vfio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/vhci, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/uhid, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/vhost-net, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/vhost-vsock, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/snd, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/snd, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/snd/timer, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks encountered in /dev/snd/seq, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: systemd-tmpfiles-setup-dev.service: Main process exited, code=exited, status=1/FAILURE
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: systemd-tmpfiles-setup-dev.service: Failed with result 'exit-code'.
Jan 11 14:37:48 Intel-i5-Tower systemd-fsck[584]: Ubuntu/home: sauber, 316299/66273280 Dateien, 223989723/265086556 Blöcke
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Failed to start Create Static Device Nodes in /dev.
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Reached target Local File Systems (Pre)."
1807682,2019-01-11 15:13:22 UTC,"Found a possible solution on
https://ubuntuforums.org/showthread.php?t=2406453
---------------------------------------------------
Well. Problem is the root folder has user as an owner.
Code:"
1807682,2020-02-15 03:46:55 UTC,Thats it! Thank you!!!
1807682,2020-09-22 09:16:14 UTC,Thanks g.bruno ..it has solved my headache
1807689,2019-04-08 08:45:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650635"
1807689,2019-05-21 03:33:58 UTC,"Reviewed:  https://review.opendev.org/650635
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=89bfc325caa86fd0af4eaa691d04e6772d55f588
Submitter: Zuul
Branch:    master"
1807689,2019-09-27 15:26:28 UTC,This issue was fixed in the openstack/blazar 4.0.0.0rc1 release candidate.
1807691,2018-12-10 11:28:43 UTC,It seems the Ubuntu system transmits a data sequence that forces the RFXtrx in boot load mode
1807691,2018-12-14 16:52:42 UTC,"After a ""software updater"" in Ubuntu Mate, the problem remains:
The Ubuntu system transmits a data sequence that forces the RFXtrx in boot load mode."
1807691,2018-12-22 10:28:58 UTC,"If you want the Domoticz community to use Ubuntu Mate, you'll need to fix this bug. About me, I leave Ubuntu Mate for Raspbian."
1807697,2019-05-28 17:23:52 UTC,"Okay, in that case I'll close this bug for now. If you get stuck or have questions, feel free to reopen this or contact us in #openstack-keystone or on the openstack-discuss mailing list."
1807697,2019-05-17 02:33:00 UTC,"Thanks for the answer, then I'm going to take actions at service side."
1807697,2019-05-16 17:06:06 UTC,"I could see possibly adding the project parent ID to the token body, however again you could just query keystone to get the project's parent."
1807697,2019-05-15 01:14:37 UTC,"@Collen Murphy I don't want to bother you anymore though, you mentioned about hierarchy project, so I'm sorry but let's talk about little bit more about that. :)"
1807697,2019-05-14 21:13:52 UTC,"I think using the /v3/projects/<id> API to request the project information directly is the best way forward for now, even for policy purposes. In client code, it would end up looking something like this: https://opendev.org/openstack/cinder/src/branch/master/cinder/quota_utils.py#L102-L108"
1807697,2019-05-14 01:14:41 UTC,"Change abandoned by Yang Youseok (<email address hidden>) on branch: master
Review: https://review.opendev.org/654301"
1807697,2019-05-14 01:13:06 UTC,"@Colleen Oh, I assumed the word of 'unbounded' is related to the scope, but it does not at all. After thinking about more Gage's comments, it's not reasonable to add more mutable data because keystone have done it before."
1807697,2019-05-08 05:38:53 UTC,"This is because services have to add keystone client code besides keystonemiddleware to access keystone. Some of service like Nova already have keystone client code though, it's currently only for limited use like validation of projects, and others like Neutron does not have at all."
1807697,2018-12-10 19:30:26 UTC,"It is highly recommended that ""extras"" not be used. If we could do away with them, we would (with exception of the API-Contract that requires us to maintain them). These attributes are poorly implemented and it is not easy to unwind them. As is the current behavior it is not possible to unset them (behavior that must be maintained). Another concern is any/all extras could be eaten / lost if a similar column is added to the project model. It is impossible to know what operators/deployers have named the ""extra"" values. There are also concerns about typos leading to useless data / un-removable data without direct DB modification."
1807697,2019-05-05 04:41:57 UTC,"@Gage Hugo
imho, there would be barrier to use Tag feature if we have to request Keystone one more time in the Nova or Neutron side. We actually did like you said, but I felt It's better to keep tag in the auth token to avoid to request to Keystone."
1807697,2019-05-04 16:18:16 UTC,Project Tags their own path[0] to call that can be backed by separate policy from projects if needed. Would using this alongside the default reader role help with this issue?
1807697,2019-04-26 03:40:10 UTC,"We got a parallel submission in Neutron on this topic: https://bugs.launchpad.net/neutron/+bug/1825336. Since this seems to need changes in several projects, let's stay in synch"
1807697,2019-04-22 05:30:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654301"
1807697,2018-12-13 05:23:30 UTC,@Morgan. Thanks for the further explanation.
1807697,2018-12-11 16:09:30 UTC,"AH! Project Tags is something more in line with something we could expose directly and I totally could see the benefits there. It is also possible for neutron to directly request the project details from Keystone via the /v3/projects api, which should return the tags (which might be the easiest and shortest path, changing the token body/format is def. a high barrier as the token format is consumed externally / is a contract. If the direct request from neutron for the project info is sufficient we can roll with that, if not then we can explore the tags being in the token."
1807697,2018-12-11 02:41:06 UTC,@Morgan Hi Morgan.
1807697,2019-05-07 15:44:47 UTC,"Is there a reason for trying to cut down on API request calls, other than saving time/bandwidth? I'm not following how an additional GET /projects/[id]/tags call would be a significant barrier?"
1807697,2019-05-13 21:02:22 UTC,"By ""unbounded"" we mean that projects can have effectively limitless tags, but if all of the tags are included in the token that expands the size of the token."
1807698,2018-12-10 12:34:46 UTC,"this bub can be duplicated
just opened same file
crashed"
1807700,2019-01-25 07:45:26 UTC,"I reopened this bug report because even changing the timezone to ""Europe/Rome"" does not solve."
1807700,2018-12-12 12:30:38 UTC,"I forgot to mention that I tried ""Europe/Rome"" with same results."
1807700,2018-12-12 05:16:36 UTC,"Use pytz.timezone(""Europe/Rome"") for Italy's timezone. CET is deprecated (like all non-Region/City zonenames), for the very reason that often individual regions do not follow the same rules as their surrounding regions."
1807702,2018-12-18 11:50:45 UTC,"4.15.0-1007.9 - oci
Regression test CMPL, RTB."
1807702,2019-01-14 11:15:39 UTC,All tasks have been completed and the bug is being set to Fix Released
1807703,2018-12-10 14:48:01 UTC,I found one of the sources: https://github.com/openstack-infra/zuul-jobs/blob/master/roles/fetch-zuul-cloner/tasks/main.yaml#L24
1807703,2018-12-17 11:53:49 UTC,It seems that this become a blocker for https://bugs.launchpad.net/tripleo/+bug/1807703 because it prevents implementation of a workaround which requires adding a new value to ansible.cfg.
1807703,2019-11-28 08:54:47 UTC,Closing because I fixed it for tripleo jobs few month ago. The only remaining jobs reporting it are nova-live-migration and some other legacy jobs that are not related to tripleo.
1807709,2019-08-19 13:06:47 UTC,Would someone be able to indicate how to get a full backtrace & coredump? That could be useful in getting the reason of the crashes?
1807709,2019-08-07 06:29:08 UTC,"Hello, I might have the same issue here, though, I have noted that from the time of the crash it seems to be at shutdown, however I am notified when I next boot the laptop. Perhaps others could check if the time does show that at startup or shutdown? Please see log attached for the latest crash."
1807709,2019-06-30 15:31:09 UTC,"Here's crash report. Ubuntu 19.04, not on wayland."
1807709,2019-03-15 15:14:05 UTC,"Additionally, apport-retrace cannot load the core dump:
$ apport-retrace /var/crash/_usr_bin_dbus-daemon.1000.crash
ERROR: Invalid core dump: BFD: warning: /tmp/apport_core_pj5lncdz is truncated: expected core file size >= 2015232, found: 61440"
1807709,2019-03-15 15:09:19 UTC,"Same issue here. UnreportableReason is usually something about core dump sizes.
systemctl --user status dbus does not seem to indicate anything is off."
1807709,2019-03-12 04:17:18 UTC,[Expired for dbus (Ubuntu) because there has been no activity for 60 days.]
1807709,2018-12-10 21:28:12 UTC,Could you also include your journalctl log?
1807709,2019-01-10 08:44:26 UTC,I believe I have the same issue
1807709,2018-12-10 21:27:53 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1807709,2018-12-10 14:51:40 UTC,"ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Dec 10 21:25:48 2018
DistroRelease: Ubuntu 18.10
ExecutablePath: /usr/bin/dbus-daemon
ExecutableTimestamp: 1536206167
ProcCmdline: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
ProcCwd: /home/laichiaheng
ProcEnviron:
 LANG=zh_TW.UTF-8
 LANGUAGE=zh_TW:zh
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
ProcMaps:
 564b7d73e000-564b7d747000 r--p 00000000 08:13 1442493                    /usr/bin/dbus-daemon
 564b7d747000-564b7d769000 r-xp 00009000 08:13 1442493                    /usr/bin/dbus-daemon
 564b7d769000-564b7d777000 r--p 0002b000 08:13 1442493                    /usr/bin/dbus-daemon
 564b7d777000-564b7d779000 r--p 00038000 08:13 1442493                    /usr/bin/dbus-daemon
 564b7d779000-564b7d77a000 rw-p 0003a000 08:13 1442493                    /usr/bin/dbus-daemon
 564b7ef9b000-564b7f0fd000 rw-p 00000000 00:00 0                          [heap]
 7ff119c84000-7ff119c8a000 r--p 00000000 08:13 1442178                    /lib/x86_64-linux-gnu/libnss_systemd.so.2
 7ff119c8a000-7ff119cb5000 r-xp 00006000 08:13 1442178                    /lib/x86_64-linux-gnu/libnss_systemd.so.2
 7ff119cb5000-7ff119cc4000 r--p 00031000 08:13 1442178                    /lib/x86_64-linux-gnu/libnss_systemd.so.2
 7ff119cc4000-7ff119cc7000 r--p 0003f000 08:13 1442178                    /lib/x86_64-linux-gnu/libnss_systemd.so.2
 7ff119cc7000-7ff119cc8000 rw-p 00042000 08:13 1442178                    /lib/x86_64-linux-gnu/libnss_systemd.so.2
 7ff119cc8000-7ff119cc9000 rw-p 00000000 00:00 0
 7ff119cc9000-7ff119ccc000 r--p 00000000 08:13 1442226                    /lib/x86_64-linux-gnu/libnss_files-2.28.so
 7ff119ccc000-7ff119cd3000 r-xp 00003000 08:13 1442226                    /lib/x86_64-linux-gnu/libnss_files-2.28.so
 7ff119cd3000-7ff119cd6000 r--p 0000a000 08:13 1442226                    /lib/x86_64-linux-gnu/libnss_files-2.28.so
 7ff119cd6000-7ff119cd7000 r--p 0000c000 08:13 1442226                    /lib/x86_64-linux-gnu/libnss_files-2.28.so
 7ff119cd7000-7ff119cd8000 rw-p 0000d000 08:13 1442226                    /lib/x86_64-linux-gnu/libnss_files-2.28.so
 7ff119cd8000-7ff119ce3000 rw-p 00000000 00:00 0
 7ff119ce3000-7ff119d01000 r-xp 00000000 08:13 1442177                    /lib/x86_64-linux-gnu/libgpg-error.so.0.24.3
 7ff119d01000-7ff119f01000 ---p 0001e000 08:13 1442177                    /lib/x86_64-linux-gnu/libgpg-error.so.0.24.3
 7ff119f01000-7ff119f02000 r--p 0001e000 08:13 1442177                    /lib/x86_64-linux-gnu/libgpg-error.so.0.24.3
 7ff119f02000-7ff119f03000 rw-p 0001f000 08:13 1442177                    /lib/x86_64-linux-gnu/libgpg-error.so.0.24.3
 7ff119f03000-7ff119f04000 r--p 00000000 08:13 1442159                    /lib/x86_64-linux-gnu/libdl-2.28.so
 7ff119f04000-7ff119f06000 r-xp 00001000 08:13 1442159                    /lib/x86_64-linux-gnu/libdl-2.28.so
 7ff119f06000-7ff119f07000 r--p 00003000 08:13 1442159                    /lib/x86_64-linux-gnu/libdl-2.28.so
 7ff119f07000-7ff119f08000 r--p 00003000 08:13 1442159                    /lib/x86_64-linux-gnu/libdl-2.28.so
 7ff119f08..."
1807709,2018-12-10 14:50:33 UTC,"It not only happens on Wayland, it also happens on Xorg."
1807709,2018-12-10 14:23:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807709,2019-01-10 08:45:10 UTC,And the journalctl log
1807717,2019-01-29 13:07:51 UTC,"FWIW, I believe all workers now backoff when they fail to operate. So it
will still continue to try, but it will try less frequently the more
failures it encounters."
1807717,2019-10-31 03:43:17 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1807722,2018-12-10 15:32:05 UTC,"p.s. in changelog of package is no hint why rsvg support was dropped, so i had to ask. rsvg is very useful, please reenable if possible."
1807722,2018-12-19 08:18:20 UTC,"Hello,"
1807722,2019-02-18 07:26:43 UTC,"I second this request. Even the official SVG logo can not be converted properly with only MSVG support. It needs RSVG.
Building from source would work, but is not an option in an automated environment."
1807722,2019-02-18 07:26:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807722,2020-05-01 13:14:37 UTC,"Still no rsvg support in eoan imagemagick 8:6.9.10.23+dfsg-2.1ubuntu3.1
This is very inconvenient for tools such as sphinx that automatically convert svg to something compatible with the build output format."
1807723,2019-06-19 21:02:14 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/624491"
1807723,2019-02-05 13:40:42 UTC,My proposed tempest fix apparently didn't do the trick since the tempest change to run slow multiattach tests on top of it still failed.
1807723,2018-12-11 20:58:39 UTC,I have a fix for tempest here: https://review.openstack.org/#/c/624491/
1807723,2018-12-11 20:03:31 UTC,"In that error log in comment 11, 26af085c-f977-4508-8bb1-46a57c8f34ed is the volume1 (it's the volume that is swapped *from* on server1)."
1807723,2018-12-11 19:56:35 UTC,With the debug patch I see that we're definitely having some weird DB issue with BDMs during server delete:
1807723,2018-12-10 19:44:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624181"
1807723,2018-12-10 17:41:47 UTC,We start deleting server2 here:
1807723,2018-12-11 20:13:22 UTC,"Oh I guess tempest will detach the volume from each server before deleting each server, because of it's cleanup steps."
1807723,2018-12-10 17:27:55 UTC,Here are the n-cpu details from volume1 is attached to server2:
1807723,2018-12-10 17:07:01 UTC,I'm not sure that a retry in cinder will fix the problem since the attachment delete for server1/volume1 fails here:
1807723,2018-12-10 16:41:34 UTC,"Looking at the swap volume flow in nova again, I think"
1807723,2018-12-10 15:55:51 UTC,I'm not sure if multiple hosts is really the main culprit because the test passed on this tempest-slow job:
1807723,2018-12-10 16:16:45 UTC,I think this is where that cinder attachment delete fails:
1807723,2018-12-10 16:11:27 UTC,"For the fail scenario, it looks like this is where we delete the old attachment record:"
1807723,2018-12-10 15:59:03 UTC,"Ignore comment 1, the original description of the bug was wrong because in the fail scenario, volume1 is on the primary node and server1 is on the subnode."
1807723,2018-12-10 17:37:29 UTC,Details from attaching volume1 to server1:
1807725,2018-12-10 15:57:13 UTC,"Hi Wojtek,"
1807725,2018-12-10 17:36:11 UTC,"Hi Andres,
I'm often changing interface name in linux to vlan name (not number) or similar. It is not limitation of linux. In linux you can use _ in interface name without problem, it works also with maas. When you configure interface with underscore character, maas properly configure interface names in netplan and interfaces will work properly in linux.
Problem is limitation of domain names. According to https://tools.ietf.org/html/rfc1035 only letters, digits and - character is only allowed.
I assume that in linux for interface name it is possible to use the same characters as for file names."
1807725,2020-02-15 23:49:22 UTC,"I have also encountered this bug.
Maas kept adding docker_gwbridge interface to the zone config."
1807725,2020-05-13 01:49:22 UTC,I've also got this with 2.7.0 with a snap install.
1807730,2020-11-05 19:52:13 UTC,"This feature wont likely make it into these charms, as the change is non-trivial."
1807730,2020-11-05 19:53:19 UTC,update contrib rules in juju-lint to ensure nagios enable_livestatus=true
1807734,2020-03-18 11:08:55 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1807745,2020-08-06 21:53:59 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1807745,2020-08-06 21:54:48 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/624021
Reason: This review is > 180 days without comment and WIP -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewers. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1807746,2018-12-10 18:08:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/624147"
1807746,2018-12-10 18:10:17 UTC,https://review.openstack.org/#/c/624147/
1807746,2019-02-19 15:48:39 UTC,"Reviewed:  https://review.openstack.org/624147
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=1cbc51af37407d28536560d6b864156df340690f
Submitter: Zuul
Branch:    stable/queens"
1807746,2019-06-21 15:26:24 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1807747,2019-09-27 09:06:02 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1807747,2019-06-06 06:23:58 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1807747,2019-05-24 10:23:39 UTC,"Reviewed:  https://review.opendev.org/660330
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e13513010fdb48a4538daa3ca8b7ae3853635587
Submitter: Zuul
Branch:    stable/stein"
1807747,2018-12-10 20:04:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624185"
1807747,2019-05-18 02:04:38 UTC,"Reviewed:  https://review.opendev.org/624185
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c27af238ad99c0330eb4b55398f44be28e6f0485
Submitter: Zuul
Branch:    master"
1807747,2018-12-10 18:10:41 UTC,The format error comes from this:
1807747,2019-05-21 09:55:51 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660330"
1807747,2018-12-10 20:39:17 UTC,There's a patch to oslo.utils to fix this too: https://review.openstack.org/#/c/620686/
1807749,2018-12-10 21:39:00 UTC,"> As far as I understand my setup, I do not have DNS before nss_ldap
> is started.
"
1807751,2018-12-10 18:47:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624162"
1807751,2019-05-06 15:59:37 UTC,"Reviewed:  https://review.opendev.org/624162
Committed: https://git.openstack.org/cgit/openstack/keystone-specs/commit/?id=2d0de7cccd172c6c70349851b0ca50ada8dd5c79
Submitter: Zuul
Branch:    master"
1807751,2019-08-23 23:56:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678322"
1807751,2019-09-13 13:50:09 UTC,"Reviewed:  https://review.opendev.org/678322
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b31ff3f991d16968db65373f3096c8cacb84219b
Submitter: Zuul
Branch:    master"
1807755,2018-12-10 19:23:39 UTC,"Going to discuss w/ Marios and Sorin whether or not we think, the following should be default."
1807755,2018-12-11 02:41:36 UTC,https://review.openstack.org/#/c/624174/ <--- test change
1807755,2019-02-19 13:22:09 UTC,Is this still an issue?
1807755,2019-02-21 07:48:58 UTC,Not anymore no. Abandoned.
1807755,2020-04-07 08:01:27 UTC,Closed as wontfix because it doesn't happen anymore and not sure on what fixed it.
1807759,2018-12-10 20:54:30 UTC,"The screenshot is a gtk one, the issue sounds like an upstream one though"
1807761,2019-01-23 17:07:25 UTC,That's still an issue in disco/with gnome-shell-extension-desktop-icons
1807761,2018-12-12 06:18:06 UTC,It would appear the issue is that a gdebi instance opened from the context menu on a desktop item is unable to do any action on any .deb file located anywhere. In other words it's doomed to fail upon simply opening.
1807761,2018-12-11 14:52:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807761,2018-12-11 20:17:12 UTC,"Thanks for idea, but on launch gdebi is shown in `htop` as"
1807761,2018-12-11 16:48:53 UTC,Could you look in the list of process what url was called exactly for gdebi? maybe it's using a x-desktop: url which gdebu doesn't handle?
1807761,2018-12-10 21:13:00 UTC,This happens only on desktop. Which is controlled by `nautilus-desktop` executable (part of `nautilus` package).
1807761,2018-12-10 20:55:36 UTC,is the issue only happening on the desktop view? does it work in 'normal' directories?
1807761,2018-12-10 20:45:20 UTC,Reported to upstream as https://gitlab.gnome.org/GNOME/nautilus/issues/782 .
1807761,2018-12-10 21:18:01 UTC,And Ubuntu 18.04 LTS (xenial) is affected too.
1807767,2018-12-10 21:52:53 UTC,"In looking at the code, and discussing with thedac, we think one should:"
1807769,2019-07-10 10:20:49 UTC,questions about a PPA should be directed towards the PPA owner. Marking this as invalid
1807772,2018-12-17 04:10:18 UTC,Need more info to understand the issue
1807777,2019-07-31 04:17:28 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1807777,2018-12-10 23:18:24 UTC,The work around to solve this issue is to restart maas-regiond.
1807777,2018-12-10 23:41:05 UTC,I've tested 2.5 and it seems unaffected.
1807780,2018-12-11 17:42:10 UTC,"Review in progress for https://review.opencontrail.org/48133
Submitter: <email address hidden> (<email address hidden>)"
1807780,2018-12-11 20:56:05 UTC,"Reviewed:  https://review.opencontrail.org/48133
Committed: http://github.com/Juniper/contrail/commit/3594f3df6d05dcd4fcf2f7d6446b11583fcd70a2
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1807781,2018-12-11 20:08:17 UTC,"12/11/18:  More Info; I made sure that the ""Secure Boot"" option in the Win Bios was disabled, along with with the ""legacy Boot"" was already 'greyed out' so I can guess that it is already disabled.  I used the gparted app in ubuntu, deleted the previous installations of ubuntu, plus a couple more that were no longer needed, so that I had plenty of free space.  A new attempt at installation created a partition size of 16G."
1807784,2019-02-11 21:48:16 UTC,Hi!  The problem is here:
1807784,2019-03-28 23:04:20 UTC,"I'm not sure this is a duplicate -- if the bookings refresh is largely keeping the backend OpenSRF Perl code unchanged, (which the bug only references updating Angular interfaces) you'll likely still hit this problem.   Feel free to re-mark as duplicate of 1816475 and comment with rationale :)"
1807793,2019-07-24 07:56:00 UTC,Thanks for reporting.
1807798,2018-12-11 14:48:25 UTC,"Hi Aaron,"
1807798,2019-11-15 17:03:32 UTC,I have the same problem.
1807798,2020-01-16 15:26:58 UTC,snap-store is based on gnome-software which has removed the snap login capability.  We need to investigate bringing that code back.
1807803,2018-12-11 03:11:21 UTC,"In addition to ""after"" job parameter, we may need a ""before"" job parameter to make sure a job is executed before another one."
1807803,2018-12-11 07:20:01 UTC,The rule of thumb to ensure such ordering always has been the test plan.
1807805,2018-12-17 09:38:45 UTC,"I can't seem to reproduce this on devstack with MySQL/InnoDB, seems the select always returns results in order by ID. Can you share more information about your database configuration? What version of keystone are you using? Do you have any LDAP or federated users in addition to the SQL users?"
1807805,2019-01-28 17:20:28 UTC,Marking as incomplete until we get a little more information on how to reproduce this.
1807808,2018-12-11 04:17:15 UTC,"You'll want to apply for the https://launchpad.net/~ubuntu-wiki-editors team in order to update the wiki (this instruction is linked in the footer of every wiki page, but it's easy to miss!), once you have that, you'll be able to edit pages on the wiki :)"
1807817,2018-12-11 08:27:51 UTC,The symlinks are different on the two architectures.
1807817,2020-03-10 06:06:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807818,2020-09-02 07:30:20 UTC,@Kai-heng it still happens on kernel 5.4 on 20.04 (dmesg on #8)
1807818,2020-09-02 06:04:59 UTC,Maybe try the 5.4 based kernel?
1807818,2020-08-30 10:51:11 UTC,@ Kai-heng #6
1807818,2019-12-01 18:10:36 UTC,Still happens on 20.04 development branch with kernel 5.3.0-18-generic
1807818,2019-11-15 01:29:11 UTC,"This bug is still active on 20.04 development branch, with kernel 5.3.0-18-generic
@15/11/2019"
1807818,2019-04-27 04:55:17 UTC,the mouse pointer seems also to slide slower when this bug happens
1807818,2018-12-11 09:08:21 UTC,"lotuspsychje@RooTBooK:~$ xinput --list-props 13
Device 'SynPS/2 Synaptics TouchPad':
 Device Enabled (142):	1
 Coordinate Transformation Matrix (144):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
 Device Accel Profile (273):	1
 Device Accel Constant Deceleration (274):	2.500000
 Device Accel Adaptive Deceleration (275):	1.000000
 Device Accel Velocity Scaling (276):	25.000000
 Synaptics Edges (277):	1574, 5366, 1343, 4507
 Synaptics Finger (278):	25, 30, 0
 Synaptics Tap Time (279):	180
 Synaptics Tap Move (280):	252
 Synaptics Tap Durations (281):	180, 180, 100
 Synaptics ClickPad (282):	0
 Synaptics Middle Button Timeout (283):	75
 Synaptics Two-Finger Pressure (284):	282
 Synaptics Two-Finger Width (285):	7
 Synaptics Scrolling Distance (286):	114, 114
 Synaptics Edge Scrolling (287):	1, 1, 0
 Synaptics Two-Finger Scrolling (288):	0, 0
 Synaptics Move Speed (289):	1.000000, 1.750000, 0.034843, 0.000000
 Synaptics Off (290):	0
 Synaptics Locked Drags (291):	0
 Synaptics Locked Drags Timeout (292):	5000
 Synaptics Tap Action (293):	0, 0, 0, 0, 1, 0, 0
 Synaptics Click Action (294):	1, 0, 0
 Synaptics Circular Scrolling (295):	0
 Synaptics Circular Scrolling Distance (296):	0.100000
 Synaptics Circular Scrolling Trigger (297):	0
 Synaptics Circular Pad (298):	0
 Synaptics Palm Detection (299):	1
 Synaptics Palm Dimensions (300):	10, 200
 Synaptics Coasting Speed (301):	20.000000, 50.000000
 Synaptics Pressure Motion (302):	30, 160
 Synaptics Pressure Motion Factor (303):	1.000000, 1.000000
 Synaptics Resolution Detect (304):	1
 Synaptics Grab Event Device (305):	0
 Synaptics Gestures (306):	1
 Synaptics Capabilities (307):	1, 0, 1, 1, 1, 1, 1
 Synaptics Pad Resolution (308):	70, 45
 Synaptics Area (309):	0, 0, 0, 0
 Synaptics Noise Cancellation (310):	28, 28
 Device Product ID (269):	2, 7
 Device Node (268):	""/dev/input/event5"""
1807818,2018-12-11 06:30:06 UTC,This change was made by a bot.
1807818,2019-11-15 06:30:33 UTC,"Please try different i8042 parameter listed here:
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html"
1807820,2019-09-19 14:50:00 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1807820,2018-12-18 14:47:40 UTC,"Hello Andres,"
1807820,2018-12-18 14:47:19 UTC,"Thanks Sam for filing this, the kernel team relies on this to be working in MAAS, so if there is any assistance we can offer, please let us know."
1807820,2018-12-18 03:34:23 UTC,"Hi Andres,"
1807820,2018-12-13 00:11:06 UTC,squashfs images that is.
1807820,2018-12-13 00:10:58 UTC,"or maybe, this is a regression on the image streams side because seems at a certain point we started building precise images: https://git.launchpad.net/maas-images/commit/?id=49fb1e42572873184104d77c027e0b823d726f8a"
1807820,2018-12-13 00:04:54 UTC,"So it seems MAAS is no longer creating the root-tgz, and that's the bug."
1807820,2018-12-13 00:03:15 UTC,So MAAS is correctly trying to download the root-tgz but the files avialable do not include a root-tgz. I also looked in the code and it seems that root-image.gz should be converted into root-tgz:
1807820,2018-12-12 07:04:37 UTC,BTW Precise i386 deployment works fine before we upgrade the MaaS from 2.3 something to 2.4.2
1807820,2018-12-13 00:14:18 UTC,Actually it seems this is because we may have dropped support for i386 in ubuntu altogether because the squashfs image exists for amd64:
1807822,2018-12-13 18:53:20 UTC,This is not a UI issue. The issue is because of having different passwords for local Keystone in contrail-command and Keystone of OpenStack cluster.
1807822,2018-12-13 19:17:38 UTC,"agent is a go routine, which watches/polls go-api-server for the resource change(CRUD) and takes action to provision/upgrade etc."
1807823,2018-12-11 07:11:36 UTC,"StacktraceTop:
 wav_w64_read_fmt_chunk (psf=psf@entry=0xd4b420, fmtsize=875972178) at wav_w64.c:333
 rf64_read_header (framesperblock=<synthetic pointer>, blockalign=<synthetic pointer>, psf=0xd4b420) at rf64.c:224
 rf64_open (psf=psf@entry=0xd4b420) at rf64.c:88
 psf_open_file (psf=0xd4b420, sfinfo=sfinfo@entry=0x7ffd71fd0930) at sndfile.c:2746
 sf_open (path=path@entry=0x7ffd71fd2301 ""crash-0_00018173"", mode=mode@entry=16, sfinfo=sfinfo@entry=0x7ffd71fd0930) at sndfile.c:333"
1807825,2018-12-11 07:24:31 UTC,"StacktraceTop:
 psf_binheader_readf (psf=psf@entry=0x95e420, format=0x7f36299f6651 """", format@entry=0x7f36299f664f ""pb"") at common.c:1040
 id3_skip (psf=psf@entry=0x95e420) at id3.c:35
 guess_file_type (psf=psf@entry=0x95e420) at sndfile.c:2423
 guess_file_type (psf=psf@entry=0x95e420) at sndfile.c:2424
 guess_file_type (psf=psf@entry=0x95e420) at sndfile.c:2424"
1807826,2018-12-11 07:39:34 UTC,"StacktraceTop:
 __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
 memset (__len=<optimized out>, __ch=0, __dest=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:90
 paf24_read_block (psf=<optimized out>, ppaf24=0x7f5f72d0c010) at paf.c:496
 paf24_init (psf=0x840420) at paf.c:375
 paf_open (psf=psf@entry=0x840420) at paf.c:149"
1807838,2018-12-11 08:30:07 UTC,This change was made by a bot.
1807842,2018-12-11 08:30:14 UTC,This change was made by a bot.
1807842,2019-07-22 04:16:45 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1807856,2018-12-22 15:10:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807856,2019-03-27 20:22:54 UTC,Moving over to snapd as the failure actually hits before any of the LXD migration code runs.
1807856,2019-03-28 01:11:56 UTC,I added apport for the python2 -> python3 bug.
1807856,2019-03-28 14:07:48 UTC,What version of apport did you have installed? This should have been fixed when bug 1766337 was fixed.
1807859,2020-08-20 04:17:19 UTC,[Expired for tempest because there has been no activity for 60 days.]
1807859,2020-03-23 18:47:52 UTC,"What is the status here? Is it really in progress?
FYI, there is a similar bug for verify-config command: https://bugs.launchpad.net/tempest/+bug/1719459"
1807859,2020-06-20 10:16:43 UTC,"Doesn't seem this is InProgress, anyway, could you specify what exactly is the problem here? The values from tempest.conf (given by -c argument) are not used because it silently reads a tempest.conf from the current workspace - similar to https://bugs.launchpad.net/tempest/+bug/1719459  ?"
1807872,2019-02-13 08:47:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636569"
1807872,2018-12-16 10:47:28 UTC,"Do you mean ""escaped"" by ""translated""?"
1807872,2018-12-16 10:49:58 UTC,"NOTE: If someone would like to fix it, you need to consider risk of script injection in other delete forms and other templates carefully."
1807878,2018-12-11 10:01:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807878,2018-12-11 12:22:31 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1807886,2018-12-11 18:45:28 UTC,"I increased the value for $cnt variable, at the line 189 in the file scripts\config_private_network.sh, from 20 to 600 seconds but I have the same problem."
1807886,2018-12-12 12:09:29 UTC,"Hello Roger,"
1807886,2018-12-12 14:22:40 UTC,"I have tried and, so far, failed to reproduce the problem. I have downloaded the code from http://tarballs.openstack.org/training-labs/dist/labs-stable-rocky.tgz, did not change anything about the configuration and let it run (""./st.py -b base"", ""./st.py -b cluster"")."
1807886,2018-12-12 15:13:43 UTC,For me the steps are :
1807886,2018-12-18 08:58:09 UTC,"Sorry, I missed your comment. No, the ""base"" command (creating a basedisk) is implied in the ""cluster"" command (if the basedisk is missing, it gets built automatically). I have a habit of running ""base"" for testing because it recreates the basedisk which may help find errors created by changes in the upstream software repositories."
1807886,2018-12-18 15:08:42 UTC,"Hello Roger,"
1807886,2018-12-19 09:36:04 UTC,Hi Yannick
1807887,2018-12-11 10:07:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807893,2019-02-19 13:22:33 UTC,Is this still an issue?
1807893,2018-12-11 12:51:53 UTC,"So after some discussion on IRC (thanks marios & ykarel!) it seems this is a duplicate of https://bugs.launchpad.net/tripleo/+bug/1806853, which was fixed by https://review.rdoproject.org/r/#/c/17746/3/deps.yml"
1807893,2020-02-13 12:24:31 UTC,Closing this really old bug.
1807893,2018-12-11 11:56:47 UTC,Hmm actually -extras is also defined in tripleo-quickstart (config/release/tripleo-ci/CentOS-7/master.yml if you're using the tripleo-ci master release) so we may need to remove that?
1807893,2018-12-11 12:34:31 UTC,"Ok after disabling -extras it then fails installing skopeo so it seems like there is more than one repo config, probably we need to confirm if --release master-tripleo-ci is still tested in CI or if that should now be removed"
1807893,2018-12-11 11:36:32 UTC,I'm seeing the same thing installing tripleoclient via quickstart so I suspect some repo conflict is causing this
1807893,2018-12-11 15:05:57 UTC,"Ok so the fix in my case was to rm -fr /var/cache/tripleo-quickstart, the cached images were stale."
1807893,2018-12-11 11:49:36 UTC,"python-docker-py-1:1.10.6-7.el7.noarch seems to be pulled in from centos extras - disabling that repo on my virthost seems to have resolved the issue, Martin can you confirm if that also resolves your problem?"
1807900,2018-12-11 11:34:39 UTC,Confirming on Xubuntu 18.04.
1807900,2020-11-30 13:21:11 UTC,"Setting as wontfix for bionic, it isn't important enough to justify the target"
1807900,2019-01-12 04:07:19 UTC,The gnome-control-center is not installed with xubuntu.
1807900,2021-01-09 00:31:54 UTC,This bug was fixed in the package update-manager - 1:21.04.3
1807900,2018-12-18 11:57:59 UTC,Probably I did mean canonical-livepatch - that certainly sounds sensible. I mentioned gnome-control-center because it was implicated in Bug #1770686. Maybe that bug isn't as closely related to this one as I thought?
1807900,2018-12-18 09:14:45 UTC,"Did you mean “if canonical-livepatch is not installed”? I don’t think this has anything to do with gnome-control-center, as long as software-properties-gtk is (unfortunately) separate from it."
1807900,2018-12-11 11:34:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1807900,2019-01-07 10:04:37 UTC,"Ah, well spotted. Several programs should vary their UI depending on whether canonical-livepatch is installed. update-manager is one of them (this bug); software-properties is another; and gnome-initial-setup is another."
1807900,2019-01-29 22:45:34 UTC,"Andrea, could you have a look to that issue?"
1807936,2019-04-07 20:53:21 UTC,"We have a version with more debug info.
http://downloads.mixxx.org/builds/2.1/release/mixxx-2.1.8-2.1-git6827-release-x64.exe"
1807936,2018-12-12 15:45:36 UTC,It can be same as this ?
1807936,2018-12-25 23:04:50 UTC,"I cannot reproduce the issue on Win10 64 using Mixxx 2.1.5 64 bit.
Maybe it is related to the path of the tracks.
Is there something suspicious in the log file?
https://www.mixxx.org/wiki/doku.php/finding_the_mixxx.log_file
Are all tracks effected.
Does dropping from the windows explorer work?"
1807936,2018-12-27 23:43:14 UTC,"-Nothing suspicious noticed in the log file as far as I am aware.
-All tracks are affected.
-Dropping from Windows Explorer does not work neither."
1807936,2018-12-27 23:56:36 UTC,"Can you post the lines that are logged when dropping the file from Windows Explorer?
Mine are:"
1807936,2018-12-28 12:06:33 UTC,"@kek001 (kek001)
This is another issue. I have faced what you wrote in the past but not now with 2.3.0 master latest versions. Now mouse selects tracks correctly."
1807936,2018-12-28 14:02:19 UTC,"Interesting:
https://superuser.com/questions/59051/drag-and-drop-file-into-application-under-run-as-administrator"
1807954,2018-12-20 14:52:49 UTC,"I'm going to have to remove my Confirmed update on this bug. I was not able to test SIP. I incorrectly thought this referred to Evergreen's Self-Check, which also doesn't block the new alert messages."
1807957,2019-10-31 03:43:37 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1807957,2019-07-24 01:05:45 UTC,I've looked into this to a small degree. It doesn't appear to be a simple change.
1807959,2018-12-11 13:31:03 UTC,"[root@undercloud overcloud]# cat group_vars/ComputeOvsDpdk
ComputeOvsDpdk_pre_deployments:
  - EnableDpdkDeployment
  - NetworkDeployment
  - ComputeOvsDpdkUpgradeInitDeployment
  - ComputeOvsDpdkDeployment
  - ComputeOvsDpdkHostsDeployment
  - ComputeOvsDpdkAllNodesDeployment
  - ComputeOvsDpdkAllNodesValidationDeployment
  - ComputeOvsDpdkArtifactsDeploy
  - ComputeOvsDpdkHostPrepDeployment"
1807959,2019-02-28 03:28:32 UTC,Simpler way to reproduce the problem in ansible http://paste.openstack.org/show/746470/
1807959,2019-02-28 04:32:11 UTC,"using ""strategy: free"" fixes the issue by ensuring the order of the execution. but it would increase the time of the execution, as execution will not be clubbed together for hosts having same var items."
1807959,2019-06-13 04:23:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665059"
1807959,2019-06-20 09:00:52 UTC,"Change abandoned by Saravanan KR (<email address hidden>) on branch: master
Review: https://review.opendev.org/665059"
1807959,2019-06-20 10:29:27 UTC,This issue will be fixed as part of https://review.opendev.org/#/c/663710
1807961,2018-12-18 22:11:27 UTC,Hi Calvin - I think supporting resource pools should be straightforward. Folders are a bit trickier because at the moment we use them to track controller/model hierarchy at the provider level (in other providers we use tags for this).
1807961,2019-02-13 03:54:05 UTC,Support for resource pools: https://github.com/juju/juju/pull/9744
1807961,2019-03-01 08:25:32 UTC,https://github.com/juju/juju/pull/9817 merges this into develop
1807968,2019-01-14 13:27:54 UTC,I've seen the same issue: https://paste.ubuntu.com/p/T5zdbRSXmY/
1807969,2019-01-02 14:35:47 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/627981"
1807969,2019-01-02 14:07:36 UTC,"Reviewed:  https://review.openstack.org/627730
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=68f6578adcd84598a6ce253f33e1c46c9a6b50ea
Submitter: Zuul
Branch:    stable/queens"
1807969,2018-12-28 17:52:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/627730"
1807969,2019-01-03 11:12:15 UTC,"Reviewed:  https://review.openstack.org/627981
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=65a64521fee00240b1d9df8f444732f342e1b73f
Submitter: Zuul
Branch:    stable/pike"
1807969,2018-12-21 12:42:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626888"
1807969,2018-12-20 04:20:29 UTC,"Reviewed:  https://review.openstack.org/623551
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=6299ed5ed001ae2768ed2b954730b526b4053b2c
Submitter: Zuul
Branch:    master"
1807969,2018-12-11 14:21:12 UTC,Attaching the devstack log since the gerrit logs referenced are ephemeral.
1807969,2018-12-28 15:47:42 UTC,"Reviewed:  https://review.openstack.org/626888
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=758eaac8cc273c6e035cece339a4215d2ce8c6e9
Submitter: Zuul
Branch:    stable/rocky"
1807973,2018-12-11 17:08:14 UTC,"this issue is caused by a change in behavior in tar 1.3, wherein it sets the exit code ""2"" when positional arguments are used out of order."
1807973,2018-12-19 12:36:39 UTC,Described solution #2 works for me. Thank you.
1807974,2019-11-07 12:08:09 UTC,"Same issue here, Dell 9570. It seems to happen more often when I have Bluetooth devices associated."
1807974,2020-05-28 23:51:35 UTC,"Same problem for me. Dell XPS 13 9380 ubuntu edition.
Happens at least once a day, sometimes more often. Seems to happen more when the network load is not high.
I've upgraded to the latest firmware, but without improvement."
1807974,2020-05-29 08:34:25 UTC,On my XPS 9370 the problem was only reproductible on 1 type of wireless access point and only when the network SSID was set to use both the 2.4Ghz and 5Ghz bands.
1807974,2020-07-01 17:31:47 UTC,"This broke again for me on upgrade from Bionic to Cosmic on the Dell XPS 9380. When it starts to go bad it requires a reload of the driver every 10 minutes or so. The dmesg log says ""device successfully recovered, but it fails to rejoin any wifi networks and doesn't work properly until I rmmod ath10k_pci; modprobe ath10k_pci. dmesg logs follow, I'm on the latest 4.4.1 firmware (not sure if I need c1/c2/c3)"
1807974,2020-07-01 17:38:06 UTC,"oliverp, my wifi access point uses different SSIDs for 2.4 and 5 G and still has this problem."
1807974,2020-07-01 17:44:05 UTC,"Sorry, correction above, this broke on the upgrade to Ubuntu 20.04 Focal."
1807974,2020-07-29 15:25:24 UTC,"And sometimes it can be recovered, but not always...
[28023.806953] ath10k_pci 0000:02:00.0: firmware crashed! (guid e4f47d81-ff1a-4173-9847-bbc2770ee439)
[28023.806968] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[28023.806973] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[28023.808665] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
[28023.810003] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b
[28023.810009] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[28023.820139] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[28023.820140] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[28023.820142] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[28023.820151] ath10k_pci 0000:02:00.0: [00]: 0x00034400  11  11   3   3
[28023.820158] ath10k_pci 0000:02:00.0: [01]: 0x00034800  23  23 356 357
[28023.820166] ath10k_pci 0000:02:00.0: [02]: 0x00034c00  60  59  58  59
[28023.820173] ath10k_pci 0000:02:00.0: [03]: 0x00035000  14  14  16  14
[28023.820181] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4335 4331 182 118
[28023.820188] ath10k_pci 0000:02:00.0: [05]: 0x00035800   0   0  64   0
[28023.820196] ath10k_pci 0000:02:00.0: [06]: 0x00035c00   8   8   4   4
[28023.820203] ath10k_pci 0000:02:00.0: [07]: 0x00036000   1   1   1   0
[28023.844105] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[28023.926083] ieee80211 phy0: Hardware restart was requested
[28024.133190] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[28024.236270] ath10k_pci 0000:02:00.0: device successfully recovered
[28117.136734] wlp2s0: deauthenticating from 18:35:d1:ba:ad:67 by local choice (Reason: 3=DEAUTH_LEAVING)
[28119.676844] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536"
1807974,2020-07-29 15:23:35 UTC,"Hi
I have the same problem with XPS 13 9380, Ubuntu 20.04.1 LTS, 5.4.0-42-generic"
1807974,2020-10-03 06:32:31 UTC,Bionic was rock solid for me - Focal has been a nightmare of crashes. I can disconnect from the AP and reconnect and it comes back to life.
1807974,2020-11-10 02:40:48 UTC,This happens for me quite often on 20.10:
1807974,2020-11-10 14:46:04 UTC,Broke again on upgrade from Focal to Groovy.
1807974,2020-12-02 10:56:11 UTC,has anyone solve the issue? it's driving me mad!
1807974,2020-12-05 08:30:22 UTC,Just installed 20.10 and WiFi crashed in a few hours.
1807974,2020-07-04 12:03:36 UTC,"Same for me, crashing on XPS 13 9370 with Ubuntu 20.04 Focal and 5.4.0-40-generic #44-Ubuntu SMP"
1807974,2019-08-19 09:12:34 UTC,This also affects Dell Precision 5520 running Ubuntu 19.04.
1807974,2020-04-21 13:41:52 UTC,Same issue here.
1807974,2019-07-23 10:14:41 UTC,Broken with the latest firmware:
1807974,2018-12-11 15:00:07 UTC,This change was made by a bot.
1807974,2018-12-13 08:38:30 UTC,"Was the network is under heavy load, or in idle?"
1807974,2018-12-18 10:00:50 UTC,Normally (maybe always?) it is when the network is idle. Thanks.
1807974,2018-12-19 06:04:46 UTC,"The firmware for this device got updated recently [1].
Please copy binary blobs in [2] to the same relative path under /lib/firmwares/."
1807974,2019-01-07 15:03:43 UTC,"Done, thanks Kai-Heng. How can I check I'm using the new versions?"
1807974,2019-01-07 15:39:41 UTC,Do you mean the issue happen less frequently when using S3 instead of S2Idle? I thought this should be the other way around.
1807974,2019-01-07 16:09:55 UTC,"Correct. Since I have been using Deep instead of S2Idle I have seen the issue less -- though it has only been a couple of days as I was not using this machine over the holidays. Even when it does break, Deep suspending and resuming the machine brings the wireless back up and working."
1807974,2019-07-24 08:08:47 UTC,"Mike,"
1807974,2019-01-08 07:35:30 UTC,"According to [1], new firmware can fix the issue."
1807974,2019-01-08 09:17:23 UTC,"Using the firmware from Comment #5 above stopped the wireless and my my Bluetooth mouse from working, so I have reverted it to the standard Ubuntu version."
1807974,2019-01-11 18:16:01 UTC,"I think the firmware is the same, so only the board-2.bin file needs to be copied."
1807974,2019-02-09 10:32:11 UTC,Any updates or progress being made on this?
1807974,2019-03-21 06:51:26 UTC,Possible to try Cosmic's firmware + Bionic's v4.15 kernel? Let's find the which package introduces the regression first.
1807974,2019-07-21 15:53:36 UTC,"This also affects the Dell XPS 13 9380 and Disco 19.04. The issue occurs after resume from sleep.
Firmware version RM.4.4.1.c2-00057-QCARMSWP-1 (latest from the ath git repo)
Kernel version 5.0.0-20-generic
dmesg output:
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: failed to read device register, device is gone
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: firmware crashed! (guid a6019044-1af6-47d3-b950-770d4257c7cb)
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -28
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:10 2019] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: failed to reset chip: -5
[Sun Jul 21 11:43:11 2019] ath10k_pci 0000:02:00.0: Could not init hif: -5"
1807974,2019-07-21 16:23:32 UTC,"Ok, looks like I was still running an older firmware version. I upgraded by:"
1807974,2019-01-08 07:18:21 UTC,"Please attach output of `sudo lspci -vvv -s 02:00.0`.
I think I've seen several platforms that requires to tweak PCI ASPM bits."
1807975,2019-02-04 03:01:06 UTC,My Students can not type any correct Farsi Text in python IDLE.
1807975,2019-02-04 03:25:40 UTC,"A similar bug in the Mu Editor:
https://github.com/mu-editor/mu/issues/752"
1807982,2019-01-14 11:18:36 UTC,All tasks have been completed and the bug is being set to Fix Released
1807982,2018-12-17 11:07:10 UTC,"4.15.0-1007.9~16.04.1 - oci
Regression test CMPL, RTB."
1807983,2018-12-18 17:05:29 UTC,"Hello Jeremy, or anyone else affected,"
1807983,2019-05-27 15:30:19 UTC,This package has been superseded by the following security update:
1807983,2019-05-14 16:45:17 UTC,What's the status of this SRU? We're awaiting on this to prepare a security update...
1807983,2018-12-22 19:02:36 UTC,I installed gnome-desktop3 3.30.2-0ubuntu1 on Ubuntu 18.10 and verified that the GNOME version in the Settings app is now 3.30.2.
1807983,2019-02-26 17:50:29 UTC,"Hello Jeremy, or anyone else affected,"
1807985,2018-12-11 18:32:38 UTC,"Review in progress for https://review.opencontrail.org/48135
Submitter: Witaut Bajaryn (<email address hidden>)"
1807985,2018-12-11 20:04:34 UTC,"Reviewed:  https://review.opencontrail.org/48135
Committed: http://github.com/Juniper/contrail/commit/1009e78f2f5a36dd8f4b36f63ecd01ff500c9705
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1807988,2019-07-04 07:47:19 UTC,This is also https://github.com/CanonicalLtd/multipass/issues/522
1807988,2019-07-26 08:29:56 UTC,"I can confirm this bug.
Is there any update on this bug?
As UbuntuCore and Snapcraft target explicitly production and enterprises, it is sadly completely unusable in any bigger company that uses a proxy."
1807988,2020-06-24 08:28:50 UTC,"Looks like cloud-init has a CACerts module to add system certificates to an instance:
https://cloudinit.readthedocs.io/en/latest/topics/modules.html#ca-certs"
1807988,2020-07-02 08:03:13 UTC,"So Masahiro and I both managed to reproduce this:
- run mitmdump (from mitmproxy package)
- install mitmproxy cert system wide
- update environment to point at proxy
- restart snapd"
1807988,2020-07-02 12:07:13 UTC,"We might need to add a CLI option for this so not only that env is set, but the actual certs passed into the environment."
1807988,2020-07-27 14:37:06 UTC,"Fix PR available for testing in `edge/pr-3224` channel:
https://github.com/snapcore/snapcraft/pull/3224"
1807988,2020-06-24 08:23:51 UTC,"This is still an issue with snapcraft 4.0.5, I guess it doesn't affect destructive mode (build on host). I see snapcraft build has these options:
  --http-proxy <http-proxy>       HTTP proxy for host build environments.
  --https-proxy <https-proxy>     HTTPS proxy for host build environments."
1807990,2019-05-22 16:29:43 UTC,Confirmed on 3.3.0 test server
1807995,2019-09-20 11:59:03 UTC,I'm not aware of details of synchronization plans between separate snaps but we have the following broad set of opinions:
1807996,2018-12-12 20:04:09 UTC,Possibly related bug 1752098
1807996,2018-12-11 16:53:47 UTC,I should clarify that this action occurs with volumes that have more than two copies. I used two copies for the purpose of testing.
1807996,2018-12-11 17:22:24 UTC,"While it is true that users should select delete items rather than delete call numbers and items if only one item is to be deleted, I can see where someone would accidentally choose the wrong action. Having the correct copy count in the warning dialog would alert the user that an error had been made so that they could cancel the delete."
1807998,2018-12-11 18:40:04 UTC,I filed the save failure at bug 1808012.
1807998,2018-12-11 20:28:25 UTC,I independently just found the save bug myself and didn't know there was a separate ticket for it.
1807998,2019-05-20 20:45:39 UTC,"Thanks for your patch, Rogan.  A few thoughts:"
1807998,2018-12-11 17:32:47 UTC,Confirmed in 3.2.1
1808002,2020-05-27 01:48:10 UTC,"JPM,"
1808002,2020-05-26 15:54:21 UTC,I'm having this issue in Ubuntu 20.04.
1808002,2019-07-22 03:54:19 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1808002,2018-12-12 07:28:06 UTC,Thanks. It sounds like I need to get back to my CPU fix relating to the Ubuntu Dock impacting gnome-shell (bug 1743976). The only way to avoid that is to not have any windows near the dock. That's a separate but also related bug to this and should be tracked in bug 1743976.
1808002,2018-12-12 07:07:10 UTC,Unpinned the chrome from the Dock but gnome shell is consuming high CPU but not constantly. If I keep idle gnome-shell usage becomes low untill I move the curser. Chromium also consuming high usage.
1808002,2018-12-12 06:41:17 UTC,"Finally, please try moving the Chrome window away from the dock on the left so it is definitely not touching (not even the window shadow). Does that reduce the CPU usage of gnome-shell when using Chrome?"
1808002,2018-12-12 06:38:19 UTC,"Thanks, that confirms gnome-shell's CPU usage is due to Chrome redrawing. Moving the cursor is a different bug (https://gitlab.gnome.org/GNOME/mutter/issues/283) so be careful to not confuse the two."
1808002,2018-12-12 05:17:10 UTC,"Also, please run these commands and send us the output:"
1808002,2018-12-12 05:16:20 UTC,Does closing Chrome also stop the gnome-shell CPU usage?
1808002,2018-12-12 05:02:20 UTC,"gnome shell consuming min 15% and chrome consuming 5-10% with 2 tabs, If I play any youtube videos it goes like more than 100%. No other applications are running in the system."
1808002,2018-12-12 02:37:19 UTC,"Also, please run 'top' and tell us which processes are using how much CPU each."
1808002,2018-12-12 02:36:04 UTC,Does the high CPU usage stop after you close Chrome?
1808002,2018-12-12 06:01:49 UTC,Stopping chrome is not stopping the gnome-shell usage. If I keep idle then the load is becoming low 1.xx if the move the cursor then the gnome-shell is going high. I have tried with chromium but facing the same issue.
1808004,2019-01-20 04:05:09 UTC,"Hi!  I am not arguing that the access points should be eliminated, however a giant list of authors is not the first thing the user should see ""above the fold"".   It's confusing."
1808004,2018-12-11 23:27:06 UTC,"I wanted to share how I have dealt with something similar to this, in case my perspective helps for finding what to do or not do going forward. At Berklee we have always used a lot of 511s, 700s, and 710s, which we used for back up musicians, producers, etc. So when we first got on EG, by default we would see more or less what we are seeing right now in this bug. At the time, my (music) catalogers told me not to display any the 700s/710s/711s, or 511s right below the title of the item."
1808004,2018-12-11 18:22:14 UTC,"I wouldn't mind the capping at 10 but would prefer to show them all elsewhere. I don't know how many uses would click on ""and others"""
1808004,2018-12-11 18:10:07 UTC,"What would your solution to this be? I would argue that that many access points for a title is a user service, even though the display is large."
1808004,2018-12-11 18:14:49 UTC,"Should we cap it at 10 and hide the rest behind a JS-driven ""and others"" link?"
1808007,2018-12-11 20:39:34 UTC,I was able to reproduce the issue on a VM built from master as of 12/10/18 so 3.2+.
1808007,2018-12-11 20:55:35 UTC,"I went ahead and marked the LP confirmed, since Rogan tested on a separate 3.2 database."
1808007,2019-03-18 19:05:29 UTC,We are not seeing this problem in our EG 3.2.4 system.
1808010,2019-10-24 14:48:12 UTC,"Ignore the config drive comment in PS17, that's nothing to do with the flavor's root disk since it's a separate device."
1808010,2019-12-11 18:49:55 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/690991"
1808010,2020-05-22 11:23:53 UTC,"I'm still seeing this on nova-next, I'm assuming the initial config drive copy into /run/cirros/ is failing but these sysvinit scripts are pretty cryptic so it could be later during the public key import. I also don't see an attempt by cirros to reach out to the metadata service however likely due to the failure to set a default route?"
1808010,2020-05-22 12:06:02 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/730307"
1808010,2020-05-23 13:42:55 UTC,"Reviewed:  https://review.opendev.org/730307
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=54edc7aeef97df768477b5fa14f8fc45266a9c2e
Submitter: Zuul
Branch:    master"
1808010,2020-05-23 13:53:08 UTC,"Related fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/730456"
1808010,2019-10-24 14:47:48 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/690991"
1808010,2020-05-23 13:55:28 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/730458"
1808010,2020-05-23 13:55:41 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/730459"
1808010,2020-05-27 06:38:33 UTC,"Reviewed:  https://review.opendev.org/730459
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=4acdb97d27fd1db6e66c5bd50fbf201777c67088
Submitter: Zuul
Branch:    stable/rocky"
1808010,2020-05-27 06:43:24 UTC,"Reviewed:  https://review.opendev.org/730458
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=d9225369eba2bdcbaead5a6d2029fa84a7f568bf
Submitter: Zuul
Branch:    stable/stein"
1808010,2020-05-27 06:43:32 UTC,"Reviewed:  https://review.opendev.org/730457
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=2e73509fbfc6f96b1f1ba690ba4ddf238bdc6266
Submitter: Zuul
Branch:    stable/train"
1808010,2020-05-27 06:43:41 UTC,"Reviewed:  https://review.opendev.org/730456
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=9707dba33830b8a3ca97fa6abf091d9d1d0d7899
Submitter: Zuul
Branch:    stable/ussuri"
1808010,2020-05-23 13:55:14 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/730457"
1808010,2019-10-24 14:25:22 UTC,"This is still an issue, and might be due to this change in devstack to set the root disk size in tempest flavors:"
1808010,2018-12-12 03:00:23 UTC,Adding more notes based on what clarkb found and described in #openstack-infra:
1808010,2019-09-30 14:32:17 UTC,"I think we need to update the logstash query for this because I'm seeing out of space issues causing ssh to fail but the existing query isn't in the guest console output, e.g.:"
1808010,2019-07-25 21:33:58 UTC,https://review.opendev.org/#/c/672715/ might resolve this in the gate.
1808010,2018-12-19 12:09:44 UTC,"So the issue of cirros not being able to handle config-drive information properly has been fixed with cirros 0.3.6, which is now used by default in devstack. The remaining issue(s) seem(s) to be somewhere in the nova-neutron interaction, so marking as incomplete in DevStack for now."
1808010,2018-12-17 23:09:16 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/624778
Reason: The join in security_groups should be trivial since the table should be empty in neutron cases, and when getting base metadata we also return the password which is stored in instance.system_metadata, so pre-joining instance_system_metadata is actually something we should be doing when we pull the instance from the cell database - it's used more than just vendordata v2 requests, which makes this change essentially not worthwhile."
1808010,2018-12-13 11:19:09 UTC,The initial cirros issue when running from a config-drive has been fixed in https://bugs.launchpad.net/cirros/+bug/1808119 and there is a patch for devstack to use the updated cirros version in https://review.openstack.org/624716 . This should mitigate the network metadata issue at least in those scenarios where a config-drive is being used.
1808010,2018-12-12 18:18:40 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/624778"
1808010,2018-12-12 18:12:59 UTC,"Bug 1567655 would also be related to performance issues in the nova metadata-api because when using neutron, the metadata API has to query security group information from neutron per instance:"
1808010,2018-12-12 17:31:18 UTC,"(11:25:40 AM) clarkb: frickler: mriedem melwitt to TL;DR the cirros ssh issues, they all root cause down to metadata being slow, but in the case of running out of disk we are attempting to use config drive first (which would ignore the metadata server), but since disk is full that fails then we fall back to metadata then that times out and fails?
(11:26:16 AM) mriedem: metadata api being slow?
(11:26:25 AM) mriedem: as in the guest doesn't get network info fast enough from the meta api?
(11:26:46 AM) clarkb: mriedem: yup, cirros has a 10 second timeout on that network request, and nova was taking 10.something seconds to respond"
1808010,2018-12-12 09:23:39 UTC,"O.k., so I did some further local testing with cirros 0.3.5 and config-drive. If I add a keypair that contains 4 pubkeys, I get /run to be 100% filled. If I use a keypair with 8 pubkeys, I'm getting the same ""write error"" sequence as above, _but_ cirros seems to manage to clean up after that and reverts to using the network based metadata successfully. Also /run is only 32% filled then, so the ""/run full"" issue only seems to affect instances with a config drive attached. I'll open up a separate cirros bug for that."
1808010,2018-12-12 00:26:42 UTC,"clarkb noted in #openstack-infra that even though we see the WARN message ""WARN: failed: route add -net ""0.0.0.0/0"" gw ""10.1.0.1"""" in the cirros console log, we also later see:"
1808010,2018-12-11 23:34:11 UTC,"Just a data point, I was looking at a recently failed job and found the ""WARN: failed: route add -net ""0.0.0.0/0"" gw ""10.1.0.1"""" message in the cirros console but _no_ messages about disk space:"
1808010,2018-12-11 22:04:04 UTC,We've done a bit more digging. From an example failure we get cirros console logs that look like this:
1808010,2018-12-11 18:49:06 UTC,Looks like this is by far (62%) happening the most in the networking-odl-tempest-fluorine job.
1808010,2018-12-11 18:44:15 UTC,"Until https://review.openstack.org/#/c/619319/ devstack uses root_gb=0 for the flavors that tempest uses, and root_gb=0 means the size of the image is used for the disk on nova-compute, not what is in the flavor (since it's essentially unbounded)."
1808010,2019-10-07 14:24:07 UTC,This issue was fixed in the openstack/tempest 22.0.0 release.
1808011,2018-12-11 20:14:31 UTC,This will be a good thing to address in v6 as the number of templates keeps growing.
1808012,2018-12-11 20:07:29 UTC,Noting this is a bug in the Dojo interfaces as well.
1808013,2019-01-14 10:32:54 UTC,"Maybe a better (longterm) solution would be to get rid of the current plot dialog and create a new CAM output dialog combining gerber generation, drill file generation and position file genertation."
1808013,2019-02-26 11:34:36 UTC,"> Maybe a better (longterm) solution would be to get rid of the current plot dialog and create a new CAM output dialog combining gerber generation, drill file generation and position file genertation.
"
1808013,2019-07-08 20:16:27 UTC,The fall-behind issue has been fixed.
1808013,2019-08-05 14:18:17 UTC,Wishlist bug created: https://bugs.launchpad.net/kicad/+bug/1838987
1808013,2018-12-20 18:51:24 UTC,@Jeff- Is this part of the dialog re-stacking?
1808016,2019-03-14 21:43:20 UTC,Noting this is also the underlying cause for bug #1693580 and bug #1716765.
1808030,2020-03-18 11:21:01 UTC,Migrated to https://gitlab.com/inkscape/inbox/-/issues/895
1808032,2018-12-12 00:31:42 UTC,I think this is already possible (and done for master) with the 'menus.xml' file in /share/inkscape/ui.
1808032,2018-12-13 16:17:58 UTC,You are right about the menu and 1st level submenu for all *BUT* filters end extensions.
1808032,2020-03-21 07:07:32 UTC,Closing because INVALID: works as intended.
1808033,2018-12-18 19:01:17 UTC,"After 4 Studio installs in 8 days of Studio 18.10 (Previous version was Studio 18.04, which also had a lot of bugs.) with 3 of them being total clean installs, I have finally given up entirely on Studio 18 of any version. I have installed the main Ubuntu version (Gnome) of 18.04 LTS."
1808033,2018-12-21 10:19:40 UTC,"Hi, Lloyd."
1808033,2019-08-21 13:58:53 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1808033,2019-10-21 04:17:40 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1808034,2019-01-14 05:58:59 UTC,Fix PR: https://github.com/juju/1.25-upgrade/pull/67
1808034,2019-01-09 02:52:06 UTC,"When upgrading from Juju 1 to Juju 2 on a cloud that hosts LXD containers, the upgrade process updates the instanceid field in the instanceData collection incorrectly.  You need to fix this if you want to be able to remove a unit that is an LXD container. This can be corrected as follows:"
1808034,2019-01-08 14:03:10 UTC,Subscribed field-medium
1808034,2018-12-11 21:14:10 UTC,"NOTE: the fix isn't in Juju itself, but in the 1.25 upgrade process."
1808034,2018-12-11 21:13:17 UTC,"After investigation we think this was a bug in the 1.25 upgrade process. The LXC containers when converted to LXD containers got new IDs, like juju-machine-1-lxd-0 -> juju-958f87-1-lxd-0, but the instanceID collection wasn't updated to reflect that. So when the LXD provisioning on the machine tries to stop the container, it gets told it doesn't exist."
1808035,2018-12-11 21:31:58 UTC,">  even though they are translated (and not marked ""fuzzy"").
"
1808035,2018-12-11 21:54:29 UTC,"I'm actually working on an extensive update of the Croatian translation, working with Poedit, generating .mo files, and then checking it in Inkscape. Most translations show as expected. Also I don't think, that source strings like ""Apply"" changed in recent past."
1808035,2018-12-12 00:29:48 UTC,Are there any commonalities between the strings that don't work?
1808035,2018-12-13 01:56:21 UTC,"this is what's inside my .po file.
compare it to the attached picture from my previous comment."
1808035,2020-03-26 06:47:58 UTC,"Closing because INVALID: 1.0beta2 (2b71d25, 2019-12-03), Mac OS X 10.11.6, doesn't exhibit the problem."
1808036,2018-12-11 22:08:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624509"
1808041,2019-01-23 16:36:30 UTC,"Reviewed:  https://review.openstack.org/624773
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=3fb15ad780c769c1991affff3b7ccb75ae138169
Submitter: Zuul
Branch:    master"
1808041,2018-12-12 14:46:53 UTC,See also https://bugs.launchpad.net/openstack-ansible/+bug/1800185. We started with Mitaka.
1808041,2018-12-12 11:22:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624667"
1808041,2018-12-12 12:01:00 UTC,"Interestingly, https://github.com/openstack/openstack-ansible/blob/stable/queens/scripts/upgrade-utilities/playbooks/deploy-config-changes.yml#L33-L56 is meant to handle copying changes over, but clearly isn't doing the right thing. Perhaps it would be better if we were to change it to check for env.d file and to halt the upgrade to allow manual inspection."
1808041,2018-12-12 13:56:48 UTC,"I have an /etc/openstack_deploy.PIKE directory, so I can confirm that the ${UPGRADE_PLAYBOOKS}/deploy-config-changes.yml playbook was run during the upgrade."
1808042,2018-12-12 09:43:54 UTC,"So what comes to my mind is that you may not have fencing enabled. When fencing not enabled, a reboot of those services can be problematic. See https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/advanced_overcloud_customization/sect-fencing_the_controller_nodes on how to configure fencing"
1808042,2019-05-19 04:17:54 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1808042,2019-02-19 13:23:25 UTC,Did Yolanda's comment address your issue?
1808044,2018-12-12 07:14:15 UTC,"Hi and thanks for your report,
this does not have the complete logs, so I might struggle to see the root cause, lets try."
1808048,2019-09-03 16:48:29 UTC,"Not 100% clear to me why the much newer bug wasn't marked as a dupe of this one, but hopefully someone will actually pay some attention to that one!"
1808048,2018-12-11 21:28:16 UTC,"(Note that you'll want to reinstall the snaps separately if you're trying to reproduce, due to https://bugs.launchpad.net/snapd/+bug/1808051.)"
1808050,2019-09-06 12:24:49 UTC,I think that's a fair point. I didn't realize myself one can easily remove default content-provider snaps (such as gtk-3-themes or gnome platform snap)...
1808050,2019-10-16 14:54:30 UTC,I installed the signal-desktop snap. At no point it told me it was also going to install gnome-3-28-1804 and gtk-common-themes.
1808051,2019-02-12 13:54:56 UTC,"$ snap install anbox canonical-livepatch
error: cannot install ""anbox"", ""canonical-livepatch"": cannot install snap ""anbox"": no snap revision
       available as specified"
1808051,2019-02-12 13:57:17 UTC,"Thinking about this some more, I'll see if we can't make it even better."
1808055,2018-12-12 19:19:13 UTC,"I've pushed an untested attempt to address this to http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1808055-support_nested_static_filters for others to look at.  If I can find the tuits to test soon, I will, but please grab if you're interested.  I'll not add a pullrequest tag until someone gives it a spin."
1808055,2018-12-12 19:44:35 UTC,"Thanks, Mike. I gave your branch a try and it did not appear to make a difference in catalog searches or when using query_parser.pl"
1808055,2019-01-31 15:03:08 UTC,Hello. This issue causes our custom KPAC search filter (uses copy locations) to stop working after our Evergreen upgrade from 2.12.12 to 3.1.8. We did a bunch of testing in Open-ILS/src/perlmods/lib/OpenILS/Application/Storage/Driver/Pg/QueryParser.pm
1808055,2019-11-08 23:13:28 UTC,"I've pulled out a patch from another branch that I've been working on, because I believe it will address the issue on this bug.  You can find the branch containing the relevant patch at:"
1808056,2019-06-10 15:05:34 UTC,"Thanks Paolo! We'll do that once we have everything in place. For now Dave (the person responsible for Pi images) will do some tests to make sure we're able to handle all the upgrade cases. But what we think will have to happen is that we'd probably ask not to backport this change into bionic and xenial. With snaps lacking dependency handling, it would be too easy to actually cause machines to stop working - even if in our gadget snaps we support loading of both compressed and uncompressed kernels (with determining which case is currently needed), there's still the case where someone could update only the kernel and leave an old gadget snap. So we'd probably have to stick to uncompressed kernels for core18, only switching to .gz in core20."
1808056,2019-06-12 08:55:04 UTC,"I've put together an update for flash-kernel that handles booting an uncompressed image (to support existing arm64 installs), a self-compressed image (to support existing armhf installs), and a gzip'd image (to support the proposed format). It assumes the kernel is called ""vmlinuz"" in all cases (because that's currently the case, and I presume will continue to be the case in future)."
1808056,2019-06-07 07:26:57 UTC,"@p-pisati After discussing it with Steve and Dave, we have decided that we'd like to switch to compressed images by default in linux-raspi2. Yes, we might break some edge cases here, but in overall we only officially support our own raspi images which we will be making sure are still working correctly after this change."
1808056,2019-07-16 09:39:13 UTC,"It would be nice to start building compressed arm64 kernels for eoan, but it may have to wait a bit as the core boot-env won't yet handle this correctly (that doesn't matter for core-16, but core-18 has arm64 images)."
1808056,2019-06-28 07:28:52 UTC,"The needed flash-kernel changes landed in 3.98ubuntu2, setting to Fix Released. Should we start looking into building compressed linux-raspi2 kernels for eoan?"
1808056,2019-05-23 14:10:33 UTC,"Yes, arm64 kernels don't have any decompressor build-in (and they'll never get one) - i'm fine with your idea of compressing / decompressing kernels upon installation (to avoid regression in corner cases) but i would like (at some point in the future) to switch to compressed kernels though (next LTS? F?)."
1808056,2019-06-07 12:57:13 UTC,"On the kernel side, the switch to a compressed kernel is a trivial change:"
1808056,2019-05-22 14:12:34 UTC,"Armhf is already using zImage (and the kernel decompress itself once we jump to it), so this is an arm64-only issue and no, there's no reason to have vmlinuz uncompressed as long as the bootloader can handle it - i'll send a fix to switch to Image.gz in Eoan."
1808056,2018-12-12 17:19:27 UTC,"fyi, -generic ships an Image.gz as vmlinuz, and this boots fine on X-Gene/u-boot based systems. (Trivia: the uncompressed Image grew too large for these systems, which is what precipitated the switch to Image.gz in -generic)"
1808056,2018-12-12 22:43:25 UTC,So it seems after some testing that if one changes the boot.scr to this:
1808056,2018-12-12 22:45:41 UTC,"That said we just shipped a bunch of images with the original boot.scr to a bunch of people and I don't think we have a mechanism for updating the boot.scr on these images, although I would love to be wrong about that."
1808056,2019-05-22 15:06:36 UTC,"Paolo - so last time we talked about this, you mentioned that the arm64 kernel doesn't support decompressing the kernel on boot like the armhf one. Is that still the case? Since I have marked the linux-raspi2 task as 'Won't Fix' because of this. If yes, is there any way of having the same functionality of uncompressing the kernel on boot for arm64 as we have for armhf?"
1808056,2018-12-11 22:09:53 UTC,It seems the vmlinuz is not compressed on arm64 which would explain the difference. If u-boot on arm64/rpi3b+ supports a compressed image that would suggest the fix is fairly simple.
1808056,2019-05-22 13:47:25 UTC,Can kernel team elaborate on this ticket?
1808056,2018-12-17 12:32:41 UTC,"@mwhudson I think those can get updated by flash-kernel actually. Not sure if that works though as I did not have any occasion to test that. But in theory the flash-kernel triggers, besides updating the kernel on the boot partition, should also update the boot.scr script every time."
1808058,2018-12-11 22:14:38 UTC,"Review in progress for https://review.opencontrail.org/48139
Submitter: Nachi Ueno (<email address hidden>)"
1808058,2019-01-05 20:20:45 UTC,"Hi~ :
Please kindly +2 for the following change again. Thank you very very much.
Zhiqiang."
1808058,2019-01-08 19:17:31 UTC,"Hi~ :
Please kindly +2 for the following change again. Thank you very very much.
Zhiqiang"
1808058,2019-01-03 20:10:54 UTC,Please kindly +2 for the following change. Thank you very very much.
1808060,2020-04-20 01:35:14 UTC,"worsk great. thanks. anyway, this should be fixed automaticaly :/"
1808060,2018-12-12 15:07:34 UTC,"As you can see in https://packages.ubuntu.com/disco/libmirclient-dev they are actually not co-installable so it's not as minor a problem as you state, but it's certainly fixable."
1808060,2018-12-12 23:51:33 UTC,That's good to hear and would be very useful! :D
1808060,2018-12-13 14:08:06 UTC,Isn't the most sensible way to fix this to change the libsdl2-dev packaging to depend on libmirclient9 directly?
1808060,2018-12-13 15:55:03 UTC,"On reflection, there are several factors contributing to the problem. Addressing any one of them would resolve the problem reported."
1808060,2020-04-09 02:41:55 UTC,"My steps to dirty fix:
find libmirclient-dev_*_i386.deb in /var/cache/apt/archives
I have libmirclient-dev_1.4.0-0ubuntu3_i386.deb. If you don't have - find one in launchpad.
Then:
$ mkdir tmp
$ dpkg-deb -R libmirclient-dev_1.4.0-0ubuntu3_i386.deb tmp
// remove tmp/usr/include and tmp/usr/share (that files alredy installed by libmirclient-dev:amd64)
// remove this lines from tmp/DEBIAN/control
Breaks: libmirclientcpp-dev
Replaces: libmirclientcpp-dev
Provides: libmirclientcpp-dev (= 1.5)
// Then back to terminal:
$ dpkg-deb -b tmp libmirclient-dev_1.4.0-0ubuntu3_FIX_i386.deb
$ sudo dpkg -i libmirclient-dev_1.4.0-0ubuntu3_FIX_i386.deb"
1808061,2020-02-10 20:54:40 UTC,"this is still an issue, but with the move to setting VFs in os-net-config no longer relevant."
1808061,2019-02-26 13:08:18 UTC,Is this still an issue?
1808061,2018-12-12 15:20:24 UTC,"I did try to add /etc/udev to the docker mount, it didnt help"
1808062,2018-12-13 19:32:15 UTC,"Note that it appears that NSX-T has a concept called ""Transport Zones"" that enables the feature that is being requested here. Compute nodes within a given transport zone will only be able to communicate with compute nodes within that same transport zone. This prevents network traffic from being sent between zones. More information here:"
1808062,2019-01-11 01:17:03 UTC,"I think this makes sense. Let's move this to triaged stage, so it can be discussed by the Neutron drivers team"
1808062,2019-01-11 16:50:26 UTC,"@Dan,"
1808062,2019-01-14 20:43:19 UTC,"1) In the example you show above, was L2pop enabled? Would l2pop be a solution for this?"
1808062,2019-01-16 20:57:40 UTC,"One question to last use case which You mentioned. Will nova also somehow restrict VMs to be spawned always in same zone?
What if user will lets say have network which works only in AZ 1, there will be couple of VMs connected to this network and then user will create VM on compute node in different AZ. How neutron should then behave? Do You want to failed to bind such port or bind it properly - and then it will just not have connectivity to other VMs in same network because there will be no tunnel to it?"
1808062,2019-01-17 19:51:09 UTC,"@slaweq, spawning VMs in the correct Neutron AZ is important, and in the use case I wanted to use this I would be using Nova Host Aggregates to separate compute nodes by Nova AZ."
1808062,2019-01-18 00:22:29 UTC,This RFE is closely related: https://bugs.launchpad.net/neutron/+bug/1808594
1808062,2019-01-25 14:39:51 UTC,"We discussed this RFE today and it is approved. We think the changes are sizable, so we are requesting a spec as the next step. We want this spec to be scoped at tunnels in general, not only VXLAN. Thanks for the submission"
1808062,2019-01-29 09:50:36 UTC,Adding some of my comments from related bug https://bugs.launchpad.net/neutron/+bug/1808594
1808067,2018-12-12 07:55:08 UTC,Separate settings is the best way for me.
1808067,2018-12-12 14:21:11 UTC,I this actually a bug or a wishlist item?
1808067,2018-12-12 14:45:52 UTC,@Wayne- Could be a wishlist.  The only reason I tagged v5.1 here was that removing the anti-aliasing addresses some of the performance problems in GTK3.  But hopefully we'll get those addressed elsewhere.
1808069,2018-12-12 20:02:36 UTC,apport information
1808069,2018-12-12 20:02:37 UTC,apport information
1808069,2018-12-12 20:02:35 UTC,apport information
1808069,2018-12-12 20:02:40 UTC,apport information
1808069,2018-12-12 20:04:06 UTC,All apport information from last working kernel -39
1808069,2018-12-12 20:02:39 UTC,apport information
1808069,2018-12-12 20:02:34 UTC,apport information
1808069,2018-12-12 20:02:29 UTC,apport information
1808069,2018-12-12 20:02:32 UTC,apport information
1808069,2018-12-12 20:02:31 UTC,apport information
1808069,2018-12-12 20:02:30 UTC,apport information
1808069,2018-12-12 20:02:27 UTC,apport information
1808069,2018-12-12 20:02:26 UTC,apport information
1808069,2018-12-12 20:02:25 UTC,apport information
1808069,2018-12-12 20:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808069,2018-12-12 20:02:33 UTC,apport information
1808070,2018-12-12 11:25:09 UTC,I tried to attach some apport-collected information and here's a manually acquired stack trace as well.
1808070,2018-12-12 11:22:30 UTC,apport information
1808070,2018-12-12 11:22:27 UTC,"ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2015-05-23 (1298 days ago)
InstallationMedia: Kubuntu 15.04 ""Vivid Vervet"" - Release amd64 (20150422)
Package: imagemagick 8:6.8.9.9-7ubuntu5.13
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
Tags:  xenial
Uname: Linux 4.4.0-140-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-07-17 (877 days ago)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
_MarkForUpload: True"
1808070,2018-12-12 11:22:28 UTC,apport information
1808070,2018-12-12 11:19:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808070,2018-12-12 11:22:29 UTC,apport information
1808071,2018-12-12 14:08:27 UTC,This is kind of related to bug https://bugs.launchpad.net/juju/+bug/1614010 about allowing users to register different accounts on an existing controller.
1808071,2019-05-22 13:22:49 UTC,Some of this has been addressed in bug 1825166.
1808072,2018-12-19 21:31:51 UTC,"From a CPC perspective, we are strongly -1 on blocking SSH on all of cloud-init completing.  As Scott notes, the user could be doing anything in cloud-final.service; further to that, I think there's a good chance this would cause a noticeable regression in apparent-time-to-system-up for almost all boots, regardless of user-provided data."
1808072,2018-12-12 14:18:32 UTC,I think I'd rather move password modification things to happen before ssh starts.
1808072,2018-12-12 00:44:05 UTC,Similar race was observed by a partner cloud in production too.
1808072,2018-12-12 00:42:01 UTC,"One solution for this would be to add Before=systemd-user-sessions.service to cloud-final.service, or something like that, so that login is inhibited until cloud init has completed."
1808072,2018-12-12 00:47:04 UTC,I am +1 on systemd-user-sessions not running (and removing /run/nologin) until cloud-init has finished.
1808074,2018-12-12 06:37:19 UTC,This relates to the new feature of bug 1758801.
1808079,2018-12-12 04:19:35 UTC,"The attachment ""Add vertical resize ability."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1808079,2019-07-15 12:51:48 UTC,"Is there any reason why this bug is ignored from Canonical side? If there are need some additional info, could somebody tell something. For Ubuntu 18.4 (Bionic) there is new aptdaemon revision (LP: #1831981 -> 1.1.1+bzr982-0ubuntu19.1), but the file /usr/lib/python3/dist-packages/aptdaemon/gtk3widgets.py in the package python3-aptdaemon.gtk3widgets is not even touched. Why?
Updated package just replace the fix (of course)."
1808079,2020-12-13 16:50:10 UTC,"Hi @ravikantcool, can you point me out what exactly is incomplete???!"
1808082,2018-12-12 02:54:33 UTC,"Application: pcbnew
Version: 6.0.0-rc1-unknown-82f657e~84~ubuntu14.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Platform: Linux 4.4.0-112-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.54.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.35.0
    Compiler: GCC 4.8.4 with C++ ABI 1002"
1808083,2019-02-25 22:24:44 UTC,Is there any ETA?
1808089,2019-01-30 14:27:18 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/633962"
1808089,2019-03-24 23:04:27 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1808089,2019-03-22 03:44:28 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1808089,2019-02-09 04:13:38 UTC,"Reviewed:  https://review.openstack.org/633962
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b8704a1d1cfe0b1fecfb21fb9373b0659f9a611d
Submitter: Zuul
Branch:    stable/queens"
1808089,2019-01-31 13:43:52 UTC,"Reviewed:  https://review.openstack.org/633960
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e7dc43bf848105fdd24b89216676e3a56f1f6689
Submitter: Zuul
Branch:    stable/rocky"
1808089,2019-01-30 14:26:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/633960"
1808089,2019-03-24 23:39:40 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1808089,2018-12-13 16:49:56 UTC,Yeah I recreated:
1808089,2018-12-12 21:40:58 UTC,I'm pretty sure there is a tempest integration test for the scenario you're describing:
1808089,2018-12-12 21:42:37 UTC,Can you provide a step by step recreate scenario?
1808089,2018-12-13 01:43:55 UTC,"Hi, thanks for the reply, the test step could be as follows:"
1808089,2019-01-30 13:20:50 UTC,"Reviewed:  https://review.openstack.org/624959
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=41b982c9feec3105247bc72d23d1470bcabc3a0f
Submitter: Zuul
Branch:    master"
1808089,2018-12-13 11:34:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624959"
1808089,2018-12-13 01:46:27 UTC,"I checked the tempest cases you mentioned, the key point is that as you mentioned,
VOLUMES ARE ATTACHED AFTER THE INSTANCE GOT SHELVED, and for this kind of volume,
they are in ""in-use"" status. Meanning this is only testing about that people
can attach volume to shelved instances and will be able to detach these newly
attach volumes, but cannot detach volumes that are already attached to instances
before shelve."
1808089,2018-12-13 11:37:05 UTC,"The resize case is OK because in compute.manager._finish_resize() we
updated the attachments with connectors, so the volumes are in
'in-use' status."
1808097,2019-01-15 10:32:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1808097,2019-01-15 10:37:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1808097,2019-01-22 08:37:23 UTC,The -proposed kernel has verified on x86.
1808097,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1808097,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1808098,2018-12-12 06:50:52 UTC,Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/340
1808101,2019-02-19 13:22:51 UTC,Is this still an issue?
1808102,2018-12-12 07:30:03 UTC,This change was made by a bot.
1808107,2019-07-10 09:58:57 UTC,"Mark this as invalid for Xenial, this issue should be tracked in bug 1775165 for fanotify07"
1808107,2019-07-08 08:24:40 UTC,"The test will pass if you run this directly:
tag=fanotify11 stime=1562574226
cmdline=""fanotify11""
contacts=""""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
fanotify11.c:66: INFO: Test #0: without FAN_REPORT_TID: tgid=2380, tid=0, event.pid=0
fanotify11.c:91: PASS: event.pid == tgid
fanotify11.c:66: INFO: Test #1: with FAN_REPORT_TID: tgid=2380, tid=2381, event.pid=2380
fanotify11.c:72: CONF: FAN_REPORT_TID not supported in kernel?"
1808107,2018-12-12 08:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808108,2019-04-03 10:36:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808108,2018-12-12 08:47:05 UTC,apport information
1808108,2018-12-12 08:47:02 UTC,apport information
1808108,2018-12-12 08:46:59 UTC,apport information
1808108,2018-12-12 08:46:56 UTC,apport information
1808108,2018-12-12 08:46:55 UTC,apport information
1808108,2018-12-12 08:46:53 UTC,apport information
1808108,2018-12-12 08:46:43 UTC,apport information
1808108,2018-12-12 08:46:49 UTC,apport information
1808108,2018-12-12 08:46:48 UTC,apport information
1808108,2018-12-12 08:46:46 UTC,apport information
1808108,2018-12-12 08:46:44 UTC,apport information
1808108,2018-12-12 08:46:39 UTC,apport information
1808108,2018-12-12 08:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808108,2018-12-12 08:46:51 UTC,apport information
1808108,2018-12-12 08:46:40 UTC,apport information
1808111,2018-12-13 13:10:30 UTC,"Reviewed:  https://review.opencontrail.org/48178
Committed: http://github.com/Juniper/contrail-tripleo-heat-templates/commit/093e901a11aaa7d19542fdc94871f555ae367d57
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    stable/queens"
1808111,2018-12-13 13:10:26 UTC,"Review in progress for https://review.opencontrail.org/48178
Submitter: Danil Zhigalin (<email address hidden>)"
1808113,2019-09-27 09:04:33 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1808113,2019-04-04 18:40:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650094"
1808113,2019-05-30 16:29:07 UTC,"Reviewed:  https://review.opendev.org/650094
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=4ec5c76c8cd5b8ce98fdcb30f47bc5bc8aac1e0f
Submitter: Zuul
Branch:    master"
1808120,2020-03-07 10:31:01 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1808121,2018-12-12 09:45:10 UTC,I'm not sure if we should keep testing KVM capabilities on a KVM node.
1808122,2019-03-27 06:10:57 UTC,"Επίσης, το μενού Γρανάζι → Αναστολή υπάρχει σε όλους τους fat clients, φορητούς και μη, και τους κάνει να κολλάνε."
1808122,2019-03-27 06:28:13 UTC,"Thanks, fix committed in https://git.launchpad.net/ltsp/commit/?id=dc8fb26f26989f28c36ae69b1684adc63afb1640"
1808123,2019-12-15 03:36:45 UTC,"Dear Alexander Kallenbach,"
1808123,2019-11-14 03:43:57 UTC,"Dear Alexander Kallenbach,"
1808123,2018-12-13 21:32:45 UTC,I've filed an upstream bug:
1808123,2019-05-16 13:12:46 UTC,"Hello Alexander,
I've tested the scenario with external monitor but couldn't reproduce it."
1808123,2018-12-12 20:57:21 UTC,"Thanks Alexander, so that looks like a libreoffice-specific problem. Would you mind filing an upstream bug report at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and sharing the link to that bug here?"
1808123,2018-12-12 20:15:16 UTC,"I've tested to do with Chromium, Firefox and Gedit. They all work as expected. Just libreoffice is having this problem."
1808123,2018-12-12 14:44:55 UTC,Thanks for the report Alexander.
1808123,2018-12-13 21:31:05 UTC,"Description:
As described above. I work in the classroom with my notebook, to which I have connected a beamer. Sometimes I write things down in the Writer and show it via the beamer. I would like to use the fullscreen mode here.
Unfortunately, the fullscreen mode is always displayed on the internal monitor, even if the window with the Writer maximized was previously displayed on the beamer.
Other apps like Firefox, Chromium and Gedit are working fine."
1808127,2018-12-12 10:08:54 UTC,console  log
1808127,2018-12-12 10:11:17 UTC,api log
1808127,2018-12-12 10:12:41 UTC,data service log
1808127,2018-12-12 10:13:42 UTC,scheduler log
1808127,2018-12-12 10:14:51 UTC,share log
1808132,2019-02-01 08:03:48 UTC,"Reviewed:  https://review.opencontrail.org/48542
Committed: http://github.com/Juniper/contrail-controller/commit/66a7b709f304d6178bc13e556b1d89609bc0d3d3
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1808132,2019-02-01 08:27:03 UTC,"Reviewed:  https://review.opencontrail.org/48543
Committed: http://github.com/Juniper/contrail-controller/commit/87ba14bb55669df4bbba225af9ad9698ace36e55
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    R5.0"
1808132,2019-02-01 07:07:32 UTC,"Reviewed:  https://review.opencontrail.org/48544
Committed: http://github.com/Juniper/contrail-controller/commit/07729cef9793cba0e3f6541d56289878d6c4a612
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1808132,2019-01-08 08:36:17 UTC,"Review in progress for https://review.opencontrail.org/48542
Submitter: Édouard Thuleau (<email address hidden>)"
1808132,2019-01-08 08:45:21 UTC,"Review in progress for https://review.opencontrail.org/48544
Submitter: Édouard Thuleau (<email address hidden>)"
1808132,2019-01-08 08:45:09 UTC,"Review in progress for https://review.opencontrail.org/48543
Submitter: Édouard Thuleau (<email address hidden>)"
1808132,2018-12-13 17:07:06 UTC,"Review in progress for https://review.opencontrail.org/48191
Submitter: Jean-Philippe Braun (<email address hidden>)"
1808132,2019-01-24 18:48:36 UTC,"Reviewed:  https://review.opencontrail.org/48191
Committed: http://github.com/Juniper/contrail-controller/commit/d7cad149c26325790f5f0dfb9059c8cb50452fe4
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1808137,2019-07-12 23:56:42 UTC,"Fixed in revision f2f2b4bcf901a46d0af484ced2a5c7a1af6af381
https://git.launchpad.net/kicad/patch/?id=f2f2b4bcf901a46d0af484ced2a5c7a1af6af381"
1808143,2018-12-13 10:35:14 UTC,"I noticed that at the moment footprints behave a bit like this. If a pad is close enough when I press M or grab the footprint to move it, the mouse is warped to the nearby pad. Not only to the anchorpoint of the footprint. This makes moving footprints easier especially when they are so large they don't fit in the view. It also allows to align the center of the pad to other items."
1808145,2018-12-17 04:06:42 UTC,"Hi zdohnal,"
1808145,2019-03-06 14:32:54 UTC,"I'm sorry - I overlooked the attached archive was converted to plain text. Reattaching, unfortunately as whole patch."
1808145,2019-07-12 05:50:31 UTC,"I rewrote the patch a little, because previous fix caused new covscan issues."
1808146,2019-01-15 11:37:29 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/630658"
1808146,2019-01-16 13:46:46 UTC,"Reviewed:  https://review.openstack.org/629248
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=29d07bec1694b05287aa175bc4de10a5dc04965e
Submitter: Zuul
Branch:    master"
1808146,2019-01-16 16:35:02 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/628254"
1808146,2019-03-11 14:44:52 UTC,This issue was fixed in the openstack/networking-ovn 6.0.0.0b1 development milestone.
1808146,2019-01-29 12:08:52 UTC,"Reviewed:  https://review.openstack.org/632677
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=abcf76499e056b848a96db85ec3931e8b61a3b56
Submitter: Zuul
Branch:    stable/rocky"
1808146,2019-02-26 08:22:42 UTC,"Change abandoned by Daniel Alvarez (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/627543"
1808146,2019-01-23 10:03:27 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/632677"
1808146,2019-01-08 11:34:01 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/628157
Reason: abandoning, cleaning queue"
1808146,2019-01-08 11:33:38 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/627190
Reason: abandoning, cleaning the gate queue"
1808146,2019-01-03 11:23:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/628157"
1808146,2019-01-03 10:53:38 UTC,"Re-opening, the error still happens sometimes in the gate"
1808146,2019-01-02 10:03:14 UTC,"Change abandoned by Lucas Alvares Gomes (<email address hidden>) on branch: master
Review: https://review.openstack.org/626589"
1808146,2018-12-27 16:30:04 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/627543"
1808146,2018-12-27 11:39:36 UTC,"Reviewed:  https://review.openstack.org/627191
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=649c7d7af9a23da46b44db344ad16b1b186ef3ca
Submitter: Zuul
Branch:    master"
1808146,2018-12-24 15:23:56 UTC,I suspect it's got to do with these tests [0] that inherit from SqlTestCaseLight and this FIXME message [1].
1808146,2018-12-12 13:20:33 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22sqlite3.OperationalError%3A%20no%20such%20table%5C%22%20AND%20project%3A%5C%22openstack%2Fnetworking-ovn%5C%22
1808146,2018-12-12 12:50:46 UTC,"Sorry, it's not always the same table. Sometimes another tables like ml2_geneve_allocations are found missing."
1808146,2019-01-03 18:31:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/628254"
1808154,2018-12-12 18:05:13 UTC,"Review in progress for https://review.opencontrail.org/48160
Submitter: Ignacy Osetek (<email address hidden>)"
1808154,2019-01-08 18:40:29 UTC,"Reviewed:  https://review.opencontrail.org/48160
Committed: http://github.com/Juniper/contrail/commit/47614a7727d42613c8ca43dbb81f46856b0fcf39
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1808158,2019-05-16 13:32:29 UTC,"Closing this bug as Invalid due to lack of activity from the reporter.
If you still encounter issues, please open a new bug with fresh data."
1808158,2019-04-17 14:38:17 UTC,"I tested this method for verifying USB content, comparing one of our labs against the installation source:"
1808158,2019-04-17 14:26:47 UTC,The only thing we can think about is that the USB was not burned properly. How did you burn the USB? I suggest that you re-burn the USB or try another one. It maybe good to do a sync before ejecting as well.
1808158,2019-04-16 20:05:49 UTC,"It's suppose to be controller-0.
I am installing from USB emulating CD-ROM drive, as CD-ROM is the only allowed boot method in BIOS. This was working fine for initial StarlingX release, is working fine for TitaniumCloud installer and any other Linux iso images."
1808158,2019-04-16 19:49:03 UTC,"@Michal,
For your baremetal system, is the install issue you are seeing on controller-0? Are you installing from USB? Is the BIOS setup properly to boot from USB? Or is it perhaps going to disk and finding some other grub config there?  It looks like your server is not even getting to the StarlingX installer."
1808158,2019-04-16 19:33:35 UTC,"From Michal:
Hi,"
1808158,2018-12-14 14:38:47 UTC,"ovs-vswitchd.log:
2018-12-12T13:02:31.233Z|00009|dpdk|INFO|DPDK Enabled - initializing...
2018-12-12T13:02:31.233Z|00010|dpdk|INFO|No vhost-sock-dir provided - defaulting to /var/run/openvswitch
2018-12-12T13:02:31.233Z|00011|dpdk|INFO|IOMMU support for vhost-user-client disabled.
2018-12-12T13:02:31.233Z|00012|dpdk|INFO|EAL ARGS: ovs-vswitchd -c 3 --huge-dir /mnt/huge-1048576kB --socket-mem 1024 -n 4
2018-12-12T13:02:31.233Z|00013|dpdk|INFO|EAL: Detected 8 lcore(s)
2018-12-12T13:02:31.234Z|00014|dpdk|WARN|EAL: Some devices want iova as va but pa will be used because..
2018-12-12T13:02:31.234Z|00015|dpdk|WARN|EAL: IOMMU does not support IOVA as VA
2018-12-12T13:02:31.235Z|00016|dpdk|INFO|EAL: 10174 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size
2018-12-12T13:02:31.235Z|00017|dpdk|INFO|EAL: Probing VFIO support...
2018-12-12T13:02:31.235Z|00018|dpdk|INFO|EAL: VFIO support initialized
2018-12-12T13:02:31.384Z|00019|dpdk|INFO|EAL: PCI device 0000:02:00.0 on NUMA socket -1
2018-12-12T13:02:31.384Z|00020|dpdk|WARN|EAL:   Invalid NUMA socket, default to 0
2018-12-12T13:02:31.384Z|00021|dpdk|INFO|EAL:   probe driver: 8086:10fb net_ixgbe
2018-12-12T13:02:31.384Z|00022|dpdk|ERR|EAL:   0000:02:00.0 VFIO group is not viable!
2018-12-12T13:02:31.384Z|00023|dpdk|ERR|EAL: Requested device 0000:02:00.0 cannot be used
2018-12-12T13:02:31.384Z|00024|dpdk|INFO|EAL: PCI device 0000:02:00.1 on NUMA socket -1
2018-12-12T13:02:31.384Z|00025|dpdk|WARN|EAL:   Invalid NUMA socket, default to 0
2018-12-12T13:02:31.384Z|00026|dpdk|INFO|EAL:   probe driver: 8086:10fb net_ixgbe
2018-12-12T13:02:31.385Z|00027|dpdk|INFO|DPDK Enabled - initialized"
1808158,2018-12-19 18:37:43 UTC,Steve will look at the new data after he is back from holidays in January 2019.
1808158,2018-12-19 18:37:01 UTC,"Marking as Release Gating until further investigation.
Note: This issue has not been reported by anyone else and could be hardware specific."
1808158,2018-12-14 14:18:36 UTC,"This is a similar symptom to https://bugs.launchpad.net/starlingx/+bug/1796380 , which to me points to a memory issue, or lack thereof."
1808158,2018-12-14 06:30:19 UTC,"Yes, VT-d is enabled in BIOS."
1808158,2018-12-13 23:58:59 UTC,"Michal, Can you confirm that you have VT-d enabled in the BIOS? What type of NIC are you using for the data port?"
1808158,2019-04-04 02:04:25 UTC,"Hi Michal, Our apologies for not following up on this report earlier. Is this still an issue?"
1808165,2018-12-12 19:14:55 UTC,"The logs show that the zun-compute process cannot connect to docker daemon, possibly due to a configuration issue. A few things to check:"
1808165,2018-12-12 19:17:17 UTC,"BTW, the option 'docker_custom_option' is for allowing the docker daemon to listen to an IP address that your zun_compute container can access."
1808165,2019-08-20 01:06:19 UTC,I am going to close this bug due to no activity within 90 days.
1808171,2019-06-19 15:02:36 UTC,Marking this as fixed because it looks that this is ok with newer os-vif version IMO.
1808171,2019-01-30 12:02:56 UTC,Is it still an issue with os-vif 1.14.0? I don't see any new example of such failure in logstash. Last one which I saw was from 24.01 and it was still with os-vif 1.13.1: http://logs.openstack.org/77/616777/9/check/nova-multiattach/93a13d2/logs/devstacklog.txt.gz
1808171,2019-01-21 11:59:55 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/631763"
1808171,2019-01-19 00:33:01 UTC,"Reviewed:  https://review.openstack.org/631584
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f8e0a497ad6a36fa0d9510cda9e7344c2ed73763
Submitter: Zuul
Branch:    master"
1808171,2019-01-18 10:03:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/631763"
1808171,2019-01-17 17:26:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/631584"
1808171,2019-01-17 17:03:42 UTC,"So, what I think is fact that when port is initially added by os-vif, it triggers OvsdbMonitor event: http://logs.openstack.org/32/602432/3/check/tempest-full/4b76af0/controller/logs/screen-q-agt.txt.gz#_Jan_16_21_35_54_776433 and such port is added to events['added'] list thus neutron-openvswitch-agent process this port.
That is causing issues and some errors in logs as port is actually not configured yet (ofport=-1) so it isn't actually processed. But for some reason it's indeed added to port_info[""current""] and if it happens, such port will be not processed later probably as it already is in ""current"" list."
1808171,2019-01-17 02:50:49 UTC,"you know what looking at this again.
assuming what normal is say regarding libvirt is corerct.
about libvirt requesting the port very shortly after os-vif does."
1808171,2019-01-17 01:10:18 UTC,"i think it is related but not the way you are implying.
i think the os-vif change is triggeing a latent bug in the l2 agent"
1808171,2019-01-14 14:00:22 UTC,"I wonder if this issue isn't somehow related to patch https://github.com/openstack/os-vif/commit/165ed325917e5deadb274ad9c122db157c0b55b2#diff-024723487bc761f5ba9d39bbf77f7721 in os-vif.
Please check Numan Siddique's comment in https://review.openstack.org/#/c/449695/6 for details"
1808171,2019-01-11 13:40:59 UTC,"After more investigating this issue based on example from http://logs.openstack.org/46/623246/3/check/nova-multiattach/efa830b/logs/screen-q-agt.txt.gz I know that this warning that port has ofport -1 isn't real problem.
It may happen like that when neutron-openvswitch-agent will ask ovs for port's details just after Libvirt creates this port. And in fact it was like that in case of e.g. port 8c3289ef-07aa-4048-8df1-979c2d8af07b and 472ab433-bc18-41b5-85ae-009611117b70 in analyzed log file."
1808171,2019-01-09 16:26:43 UTC,From this warning in q-agt it looks that port tap472ab433-bc wasn't properly created in ovs thus it had ofport = -1. Because of that neutron-openvswitch-agent didn't process it and it wasn't provisioned by L2 entity at all.
1808171,2018-12-15 17:12:45 UTC,"Looks like these failures started showing up around Dec 11, and looking at neutron commit history I wonder if this could be related:"
1808171,2018-12-12 15:20:38 UTC,so just loking at the logs around when processing of the port was skipped in the neutron agent we see
1808171,2019-01-17 13:12:32 UTC,"Hi,"
1808175,2018-12-12 15:38:15 UTC, fresh install
1808183,2019-01-29 08:39:04 UTC,Disco kernel receives this fix via stable update.
1808183,2018-12-15 06:57:18 UTC,apport information
1808183,2018-12-15 06:57:19 UTC,apport information
1808183,2018-12-15 06:57:20 UTC,apport information
1808183,2018-12-15 06:57:22 UTC,apport information
1808183,2018-12-15 07:01:36 UTC,I finally managed to work my way through the text based apport-collect and was able to send the data.
1808183,2018-12-16 06:10:04 UTC,"Seems like this commit fixes the issue:
commit 5478ad10e7850ce3d8b7056db05ddfa3c9ddad9a
Author: Thomas Zimmermann <email address hidden>
Date:   Thu Nov 15 11:42:16 2018 +0100"
1808183,2018-12-16 19:15:31 UTC,"I have installed the kernel and rebooted the server 3 times.
All reboots were as fast as the previous ubuntu 16.04.
So I think your fix has solved the problem.
Thanks a lot."
1808183,2018-12-17 02:03:38 UTC,"> Has there been a change in the VESA/AST mechanism from 16.04 to 18.04 ?
"
1808183,2018-12-20 07:48:08 UTC,"^^^
It's not documented but I think that means to say the bug is fixed in:"
1808183,2019-01-08 06:30:35 UTC,May i know when can we expect the official release for this issue?
1808183,2019-01-08 07:11:23 UTC,"The fix seems to have been released for both 18.04 and 18.10 already, a couple of weeks ago."
1808183,2019-01-08 07:19:00 UTC,Assuming comment #23 is correct...
1808183,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1808183,2019-01-12 15:38:09 UTC,"I've just done a clean install of 18.04 and have the same issue where running 18.04 off a boot usb stick works flawlessly, however after installing on the hard drive the login screen is very laggy and once I enter my password the screen resolution is all messed up and unreadable."
1808183,2019-01-13 07:32:14 UTC,Seems like 4.15.0-43.46 is a CVE respin so the patch is not included. Please wait for the next kernel release.
1808183,2019-01-14 08:46:22 UTC,"Hello Team,"
1808183,2019-02-08 08:41:04 UTC,"I cannot confirm that 4.15.18-041518-generic works stable.
It did work for a while though..
Since a few days my boot is slow again and yesterday and today the system again got stuck in emergency mode because of too slow boot.
Thus I think there is more to it than just the kernel.
The only explanation I do have is that there is some dependency between the kernel and other packages which get updated when I run apt dist-upgrade.
I am also puzzled that my system boots very fast when I do a CTRL-ALT-DELETE when it is stuck in emergency mode.
So there is a difference between a warm start and a cold boot.
I suppose that there is some hardware initialization which is done too late during cold boot but makes the following warm start fast."
1808183,2019-01-15 10:37:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1808183,2019-01-23 11:26:49 UTC,"Encountered the same issue today. Updated from 16.04 to 18.04 on a SuperMicro server with ASPEED AST 2400 VGA controller. The boot console scrolling was very slow after the update and X11 performance was unusable. Enabled the ""proposed"" apt feed and updated to 4.15.0-44-generic kernel. Can confirm that console performance is back to normal again."
1808183,2019-01-28 11:46:06 UTC,"In the last couple of days my system boots as slow again as before the fix.
I am currently on linux-image-unsigned-4.15.0-43-generic.
So there must have something changed along the way which brought back the bug."
1808183,2019-01-28 12:01:01 UTC,"The system boot is so slow that two times it got stuck in emergency mode saying that some configured disk drives were not found.
Strangely when I use a Ctrl-Alt-Del to reboot from emergency mode, the system boots fast.
I used UKTools to upgrade to kernel 4.15.18-041518-generic but the problem is still there."
1808183,2019-01-28 16:05:13 UTC,The -44-generic kernel is in -proposed.
1808183,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1808183,2019-01-29 08:09:57 UTC,"OK, I installed the 4.15.0-44-generic kernel and my system is back to normal."
1808183,2019-01-29 08:25:22 UTC,"It appears the fix for 18.04 was released into 'updates' 15 hours ago. See comment #38 and:
https://launchpad.net/ubuntu/+source/linux/4.15.0-44.47"
1808183,2019-01-29 08:26:42 UTC,Have we established the bug was never in 19.04?
1808183,2019-01-13 07:23:55 UTC,"Mat,"
1808183,2019-01-15 10:33:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1808183,2018-12-15 06:57:15 UTC,apport information
1808183,2018-12-15 06:57:14 UTC,apport information
1808183,2018-12-13 14:03:58 UTC,"Please find attached the desired files.
I am talking about text console only.
There is no X.org installed and thus no glxinfo, so this bug might be in the wrong category although it is display/graphics related.
The problem is the same as can be seen here: https://www.youtube.com/watch?v=4VEis5jtsJk.
I am obviously not the only one with the problem as the thread https://ubuntuforums.org/showthread.php?t=2399941 shows.
Bootup messages are as slow as typewriter consoles from the 1980
The dmesg part is still relatively fast but the Ubuntu boot up messages are really slow and take more than 100s.
They are in fact so slow that the server sometimes runs into emergency shell due to timeouts.
As said it only happened after upgrade to 18.04 whereas 16.04 was without problems for the last 2 years."
1808183,2018-12-14 02:13:20 UTC,"I see now, thanks."
1808183,2018-12-13 03:07:32 UTC,Please:
1808183,2018-12-14 02:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808183,2018-12-14 03:26:16 UTC,Can you please also run 'lsmod' and send us the output?
1808183,2018-12-15 06:57:16 UTC,apport information
1808183,2018-12-14 08:53:09 UTC,You should be able to open the link required by apport-collect by copying and pasting it to another machine.
1808183,2018-12-15 06:57:12 UTC,apport information
1808183,2018-12-15 06:57:13 UTC,apport information
1808183,2018-12-14 08:08:56 UTC,"My server doesn't have a graphical UI and the apport-collect did not work.
The output of lsmod is attached."
1808183,2018-12-15 06:57:11 UTC,apport information
1808187,2019-01-14 12:50:30 UTC,"This sounds like the context the user is at isn't valid. When the login is done, I wonder if it defaulted to trying to set context to the admin model or something and if you'd be able to juju switch after that login point."
1808187,2019-03-22 04:04:02 UTC,"This is a usability issue - communication to the user, only the error message needs to be changed. As such I am lowering the priority on this report to standard Medium."
1808187,2019-03-22 03:59:34 UTC,This is not a context issue.
1808187,2019-01-14 14:10:52 UTC,The output does state explicitly which model is the current one ('admin/euphoric').
1808188,2018-12-15 22:55:46 UTC,I have the same issue for spoken word files or Christmas Tracks during the rest of the year.
1808188,2018-12-16 21:16:42 UTC,"We need them in the sql library to put them in the history playlist.
A separate feature for them is a good idea.
Does it relate to load and save sampler sets?"
1808188,2018-12-16 19:04:07 UTC,"I think some people have lot of samples and loops it can make sqlite file huge.
Have over 400 000 samples and loops. I dont have lot.
Would let mixxx analyze loops/samples on fly, and not filed them to a main sqlite file.
and keep them separate in treeview(tracks,autodj,playlist,crates,samples&loops) section."
1808193,2018-12-13 16:32:05 UTC,apport information
1808193,2018-12-13 16:32:06 UTC,apport information
1808193,2018-12-13 16:32:08 UTC,apport information
1808193,2018-12-14 02:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808193,2018-12-14 17:13:03 UTC,apport information
1808193,2018-12-14 17:13:05 UTC,apport information
1808193,2018-12-14 17:13:08 UTC,apport information
1808193,2018-12-14 17:13:12 UTC,apport information
1808193,2019-07-22 04:08:20 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1808193,2018-12-13 02:44:15 UTC,Please run this command to send us more information about the system:
1808193,2018-12-13 16:32:02 UTC,apport information
1808196,2018-12-13 09:15:34 UTC,I'm +1 on this change.
1808196,2019-07-02 16:24:05 UTC,The defaults seems already patched to 0 in Debian/Ubuntu
1808197,2019-03-04 22:15:24 UTC,Subscribing field medium.  Customer is complaining that dashboard has non-functional items enabled.
1808197,2019-09-03 20:11:55 UTC,Note that this would require charm config enable-consistency-groups=True. I just came across this bug when looking into https://bugs.launchpad.net/bugs/1841188.
1808197,2018-12-12 17:19:10 UTC,"It may be related to this bug
https://bugs.launchpad.net/charm-cinder/+bug/1684113"
1808197,2018-12-12 17:15:51 UTC,Confirmed in bionic-queens
1808198,2018-12-13 10:12:32 UTC,"You need to attach the file OpenRailsLog.txt that you get on the desktop, else we can't analyse the problem."
1808201,2018-12-14 15:38:01 UTC,Related upstream bug report:
1808202,2018-12-14 23:21:05 UTC,Should be consistent with messaging coming out of bug 1807462.
1808202,2019-02-04 16:34:38 UTC,"Due to the way that the 'juju grant' codepath is implemented, even
if the user is granted 'add-model', the codepath in 'juju show-controller'
will treat the user as having 'login' controller access which means
that they still cannot get back model-related information due to a
failing permission check."
1808213,2019-05-13 12:53:12 UTC,"> What does this framework even do about languages that don't have upper/lower case?
"
1808213,2019-05-13 13:59:05 UTC,missed a word: ... don't really /have/ the resources ....
1808213,2019-05-13 13:53:57 UTC,"I have changed the translation now (""Kommunikér med apt via en apt-hook""), but please keep in mind that I/we have definitely not been one-sidedly ignoring anything.  AFAIK it was the English string which was supposed to change, and the warning persists only because this did not happen."
1808213,2019-05-13 13:41:10 UTC,I've proposed a change to snapd
1808213,2019-05-13 11:10:00 UTC,Right - the English string wasn't changed after all.
1808213,2019-05-13 14:36:08 UTC,"Yeah, I know you don't see the warning. We do periodically import them and run the test, but the cycle is super slow. That's why we put all the // TRANSLATORS: messages in..."
1808213,2018-12-15 14:56:36 UTC,So what will happen exactly on the dev side?
1808213,2018-12-12 19:00:34 UTC,Here's another person who sees this: https://askubuntu.com/questions/1088575/weird-message-when-installing-programs
1808213,2018-12-12 19:02:00 UTC,Running the same snap commands with locale LANG=C there is no message.
1808213,2019-05-12 14:56:12 UTC,"As you probably know, this is still an issue in the danish ubuntu-translations of ubuntu 19.04."
1808213,2018-12-12 19:49:22 UTC,"The localisation is wrong, the translated string should be capitalised."
1808213,2019-05-13 13:58:30 UTC,"Just FYI, translators don't see this kind of warning while translating because we don't really the resources (or an appropriate environment) to compile and test the programs.  The best I can do is usually to infer the context by looking at the source code."
1808213,2018-12-14 10:12:30 UTC,"I recently worked on something similar, let me look at this closely."
1808213,2018-12-14 19:21:18 UTC,"Thanks for reporting this, and to all of you for the discussion."
1808213,2018-12-14 20:00:48 UTC,"Reading the code, the English original is wrong also. Apologies for that; we'll fix."
1808213,2018-12-14 19:22:02 UTC,"Sorry, I meant to say that it is used as a noun, not a verb.  But this does not change much."
1808213,2018-12-14 06:07:05 UTC,"Maybe the translator wanted to use the command name (lower case) instead of translating ""Advise"" to ""Rådgiv""."
1808215,2018-12-13 18:51:29 UTC,Fixed by https://github.com/Juniper/contrail-analytics/commit/e7b63011f14c8783d2019c27c6c27df97c93c959
1808218,2019-09-16 08:25:52 UTC,Migrated to https://github.com/widelands/widelands/issues/3371
1808232,2018-12-13 16:22:17 UTC,Strange. I also have a 4k monitor but I've never encountered this. Which waveform renderer do you use? Are you using X or Wayland? I use GNOME on Wayland.
1808232,2018-12-13 16:37:50 UTC,"Where can I see that? I use whatever is default with KDE Neon, so afaik KDE Plasma on X."
1808232,2020-05-13 01:02:53 UTC,Is this still a problem?
1808232,2018-12-13 04:00:28 UTC,The screenshot links do not work. Can you attach the screenshot files on Launchpad?
1808232,2018-12-13 15:58:19 UTC,Launchpad keeps being painful -.-
1808248,2019-01-15 22:00:01 UTC,"Change abandoned by melanie witt (<email address hidden>) on branch: master
Review: https://review.openstack.org/624832
Reason: Ended up handling propagation of the failure reason in the top patch:"
1808248,2018-12-12 23:31:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624832"
1808251,2018-12-13 01:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808251,2018-12-13 01:30:39 UTC,This bug is easily reproduced and will not leave any meaningful log entries.
1808251,2018-12-13 01:31:31 UTC,No applicable logs
1808255,2020-03-07 10:55:49 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1808264,2018-12-13 05:06:20 UTC,"Whoops, misinterpreted the version numbering scheme and accidentally submitted a patch numbered for 18.04.2!"
1808264,2018-12-13 04:33:32 UTC,"I have added a patch which applies both upstream merge requests linked above. I was not above to successfully set up pbuilder, but built and tested it successfully with debuild in a bionic VM. Subscribing ubuntu-sru in accordance with http://packaging.ubuntu.com/html/security-and-stable-release-updates.html as I'm pretty sure the change I'm requesting would be a stable release update."
1808269,2018-12-13 04:58:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624857"
1808269,2019-06-28 04:45:59 UTC,"Change abandoned by Trinh Nguyen (<email address hidden>) on branch: master
Review: https://review.opendev.org/624857"
1808286,2018-12-20 04:12:44 UTC,"Reviewed:  https://review.openstack.org/624870
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2ef704cba619a149336692311c2614742aa32909
Submitter: Zuul
Branch:    master"
1808286,2019-12-18 13:37:45 UTC,"Reviewed:  https://review.opendev.org/677201
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=133232603168e240292ca54a49cbab599e8e566a
Submitter: Zuul
Branch:    stable/ocata"
1808286,2019-08-19 13:18:49 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/677201"
1808286,2019-04-26 17:16:12 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1808286,2019-03-26 04:17:32 UTC,"Reviewed:  https://review.openstack.org/628954
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3d3a263789c5cc49899d63d18f9233c981f5b894
Submitter: Zuul
Branch:    stable/pike"
1808286,2019-03-24 23:39:59 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1808286,2019-03-22 03:45:05 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1808286,2019-01-07 13:05:38 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/628954"
1808286,2019-01-07 04:32:45 UTC,"Reviewed:  https://review.openstack.org/626585
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8aadd4ebdfea3f1b46b2e2e62b355e8b40b6261b
Submitter: Zuul
Branch:    stable/queens"
1808286,2019-01-02 12:59:56 UTC,"Reviewed:  https://review.openstack.org/626584
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3eb0ba988f4cfca4399c92cd6bb7b4ae8665720c
Submitter: Zuul
Branch:    stable/rocky"
1808286,2018-12-20 13:54:58 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/626585"
1808286,2018-12-20 13:53:29 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626584"
1808286,2019-03-24 23:04:34 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1808286,2018-12-13 07:36:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624870"
1808305,2020-02-11 18:18:24 UTC,"Thanks for reporting this. It's unfortunate that it's a bit inconsistent, but it is at least documented, and IMO not a tremendous burden. In general we're trying to move toward doing all new work in openstacksdk and not python-keystoneclient, and I think the hassle of going through the deprecation process for these modules outweighs the benefits of changing the interfaces. Therefore I'm closing this as ""Won't Fix""."
1808312,2019-10-28 21:27:41 UTC,The above PR didn't work out. I'm doing an update based on the update that was made to the Charms Deployment Guide here: https://review.opendev.org/#/c/691241
1808312,2018-12-13 10:13:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/624941"
1808312,2019-10-29 17:02:21 UTC,"Reviewed:  https://review.opendev.org/691770
Committed: https://git.openstack.org/cgit/openstack/charm-guide/commit/?id=9e8aad59029b2a34a1fbdf5a9feb548f793ee674
Submitter: Zuul
Branch:    master"
1808312,2020-10-09 12:57:19 UTC,"Change abandoned by Aurelien Lourot (<email address hidden>) on branch: master
Review: https://review.opendev.org/624941
Reason: Has been superseded by another review, see linked bug"
1808312,2019-10-28 23:23:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/691770"
1808321,2018-12-13 11:30:07 UTC,This change was made by a bot.
1808325,2020-06-23 09:15:49 UTC,"I believe that this has been resolved in an update to the rabbitmq-server package in the queens Cloud Archive as I cannot reproduce this, and the archive now holds newer package versions."
1808327,2019-10-31 03:59:38 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1808330,2019-12-11 09:17:55 UTC,I've fixed the FreeBSD port with the following patch:
1808340,2019-10-10 12:43:10 UTC,How is running an app causing Wayland to crash a bug in anything but Wayland?
1808340,2019-12-10 04:17:25 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1808340,2019-03-26 00:30:35 UTC,"This appears to be related to the package manager snapd, not the DNA analysis tool snap."
1808342,2018-12-13 13:43:32 UTC,Attaching devstack log since gerrit logs are ephemeral.  This is from the Manila CentOS lvm job [1] for stable/rocky.
1808342,2019-03-14 09:51:40 UTC,Fixed by requirements change https://review.openstack.org/#/c/622262/ and its backports.
1808352,2019-01-03 23:02:40 UTC,"Theo, your workaround helps a lot. Any disadvantages to this option being set to true? I don't see any right now. It works good."
1808352,2018-12-20 12:56:06 UTC,As possible workaround try setting ui.context_menus.after_mouseup to 'true' in about:config.
1808353,2018-12-13 15:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808353,2019-01-15 10:37:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1808353,2019-01-16 05:43:56 UTC,IPMI is correctly blacklisted.
1808353,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1808353,2019-02-04 20:24:26 UTC,This bug was fixed in the package linux-oem - 4.15.0-1033.38
1808356,2018-12-13 17:27:04 UTC,"What does dpkg-buildpackage do? Or sbuild. Let's not implement a different
policy than those."
1808356,2018-12-13 15:31:09 UTC,"well,
https://code.launchpad.net/~smoser/usd-importer/+git/usd-importer/+merge/358200
will fix this failure."
1808356,2018-12-13 16:10:36 UTC,"Thanks, I didn't think of that. Unfortunately though previous changelog entry isn't always better, because in the case of an Ubuntu package merge, the previous changelog entry will probably be ""unstable""."
1808356,2018-12-13 17:45:24 UTC,"On Thu, Dec 13, 2018 at 05:27:04PM -0000, Nish Aravamudan wrote:

> What does dpkg-buildpackage do? Or sbuild. Let's not implement a different
> policy than those.
"
1808360,2018-12-13 19:05:17 UTC,I created a file /etc/apparmor.d/abstractions/mysql and inserted the folowing:
1808360,2018-12-13 19:06:41 UTC,Didn't meant to have the tags (<pre> and </pre>)
1808360,2019-12-17 19:04:42 UTC,The apparmor package provides this file:
1808368,2019-11-12 04:18:24 UTC,[Expired for kolla because there has been no activity for 60 days.]
1808368,2019-09-12 14:13:27 UTC,Does this bug still occur? Can you check on latest code and post new logs?
1808371,2019-02-19 13:29:23 UTC,Is this still an issue?
1808379,2018-12-14 07:40:10 UTC,"Hi,
the recent update was only a security fix [1] that seems totally unrelated."
1808379,2018-12-14 07:40:28 UTC,"prio low due to ""only"" affecting -backports"
1808379,2018-12-15 23:54:07 UTC,"I was not able to downgrade (force version) in synaptic apache2, though selected it did nothing. So I had to remove:
apache2
apache2-mpm-prefork
libapache2-mod-php5
virtualmin-lamp-stack"
1808383,2018-12-13 17:02:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808383,2019-03-13 19:23:20 UTC,"Hello,
the next upstream release 1.10.6 did still not yet happen after some longer delay.
Last talked about end of January here:
https://mail-archives.apache.org/mod_mbox/ant-dev/201901.mbox/browser"
1808383,2019-03-14 16:45:57 UTC,This bug was fixed in the package ant - 1.10.5-2ubuntu1
1808383,2019-04-16 16:21:27 UTC,This bug was fixed in the package ant - 1.10.5-3~18.04
1808387,2020-12-06 17:02:50 UTC,"reported for 2.3 beta
https://i.imgur.com/UPeaGmp.png"
1808388,2018-12-13 17:12:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625057"
1808388,2018-12-18 10:26:08 UTC,"Reviewed:  https://review.openstack.org/625057
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=01c81314b8b9a49040eb04555961e8d30f9ac38d
Submitter: Zuul
Branch:    master"
1808389,2019-11-05 18:47:28 UTC,"Ok, this is a complex matter. I just experienced this unpleasant feature on my laptop using the above described driver and hardware for the last two days. =>It seems to be a radio transmission issue.<="
1808389,2020-01-30 20:26:48 UTC,@ellisonleao: Eoan already has the firmware which was identified as fixing this issue. If you are having a similar issue in eoan then it must have a different cause. Please open a new bug for your issue. Thanks!
1808389,2019-11-14 17:55:33 UTC,"I have a X1 Carbon 6th gen, kernel 5.3.0-22-generic and the error remains. I've also tried moving to static channels on my router (1, 6 and 11) and also moving the frequency to 20 Mhz."
1808389,2019-09-24 21:43:53 UTC,"Affects me too on X1g6
Both, 2.4 and 5 GHz essids.
Easily reproduces, while i am trying to rsync whole / to local NAS."
1808389,2019-09-24 21:54:09 UTC,"Sorry, forget to point, that it happens on 19.04 for me"
1808389,2020-02-19 09:54:50 UTC,"I installed 5.3.0-40.32~18.04.1 kernel on my 18.04 Ubuntu and in certain cases the kernel becomes unresponsive. I don't know whether it is a 2G/5G switching or something else, but rolling back to 4.15.0-88-generic solved an issue."
1808389,2020-08-22 14:13:16 UTC,I have similar problem with similar dmesg output with Lenovo T480 (Intel 8265 wifi) and Huawei router.
1808389,2020-03-30 13:06:06 UTC,"While using 5.3.0-42-generic, problem remains on my 8265."
1808389,2020-04-04 13:07:13 UTC,"@suvl, that was fixed in linux-firmware, please update your linux-firmware package. And, if that problem persists, please file a new bug."
1808389,2020-05-02 09:29:54 UTC,Issue still exists after dist-upgrade.
1808389,2020-08-14 16:13:55 UTC,Same here.  I don't think this bug has been fixed.  Can we please reopen it?
1808389,2020-08-14 16:15:44 UTC," kernel: iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.
 kernel: iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
 kernel: iwlwifi 0000:02:00.0: Status: 0x00000040, count: 6
 kernel: iwlwifi 0000:02:00.0: Loaded firmware version: 36.79ff3ccf.0 8265-36.ucode
 kernel: iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
 kernel: iwlwifi 0000:02:00.0: 0x00800AB4 | trm_hw_status0
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
 kernel: iwlwifi 0000:02:00.0: 0x000248FC | branchlink2
 kernel: iwlwifi 0000:02:00.0: 0x0003A872 | interruptlink1
 kernel: iwlwifi 0000:02:00.0: 0x0000083A | interruptlink2
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | data1
 kernel: iwlwifi 0000:02:00.0: 0x00000080 | data2
 kernel: iwlwifi 0000:02:00.0: 0x07830000 | data3
 kernel: iwlwifi 0000:02:00.0: 0x3A00ECBD | beacon time
 kernel: iwlwifi 0000:02:00.0: 0xEE5E030C | tsf low
 kernel: iwlwifi 0000:02:00.0: 0x00000422 | tsf hi
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | time gp1
 kernel: iwlwifi 0000:02:00.0: 0x08035370 | time gp2
 kernel: iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type
 kernel: iwlwifi 0000:02:00.0: 0x00000024 | uCode version major
 kernel: iwlwifi 0000:02:00.0: 0x79FF3CCF | uCode version minor
 kernel: iwlwifi 0000:02:00.0: 0x00000230 | hw version
 kernel: iwlwifi 0000:02:00.0: 0x00489000 | board version
 kernel: iwlwifi 0000:02:00.0: 0x0B1B001C | hcmd
 kernel: iwlwifi 0000:02:00.0: 0x8002200E | isr0
 kernel: iwlwifi 0000:02:00.0: 0x00800000 | isr1
 kernel: iwlwifi 0000:02:00.0: 0x0800180A | isr2
 kernel: iwlwifi 0000:02:00.0: 0x004178C8 | isr3
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | isr4
 kernel: iwlwifi 0000:02:00.0: 0x00B3019C | last cmd Id
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | wait_event
 kernel: iwlwifi 0000:02:00.0: 0x00000094 | l2p_control
 kernel: iwlwifi 0000:02:00.0: 0x00010020 | l2p_duration
 kernel: iwlwifi 0000:02:00.0: 0x0000000F | l2p_mhvalid
 kernel: iwlwifi 0000:02:00.0: 0x00000004 | l2p_addr_match
 kernel: iwlwifi 0000:02:00.0: 0x0000000D | lmpm_pmg_sel
 kernel: iwlwifi 0000:02:00.0: 0x02052035 | timestamp
 kernel: iwlwifi 0000:02:00.0: 0x0034E0F0 | flow_handler
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | ADVANCED_SYSASSERT
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink1
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink2
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac interruptlink1
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac interruptlink2
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac data1
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac data2
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac data3
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac major
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac minor
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | frame pointer
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | stack pointer
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | last host cmd
 kernel: iwlwifi 0000:02:00.0: 0x00000000 | isr status reg
 kernel: iwlwifi 0000:02:00.0: Fseq Registers:
 kernel: iwlwifi 0000:02:00.0: 0x04A24B2F | FSEQ_ERROR_CODE
 kernel: iwlwifi 0000:02:00.0: 0x4C1A2CA0 | FSEQ_TOP_INIT_VERSION
 kernel: iwlwifi 0000:02:00.0: 0x9CC..."
1808389,2020-08-14 16:20:24 UTC,"Comment #28 seems to offer some good insights about the best path forward here, also supporting that this bug should be reopened.  Note that with a Google Wifi router, there is no capability to reconfigure the router to work around this issue, as the poster mentions."
1808389,2020-08-22 14:42:20 UTC,"I just found out that my Lenovo dock also affects this situation -- when I undock my T480, wifi starts working properly. (No, the dock doesn't have ethernet cable attached.)"
1808389,2020-02-19 14:13:21 UTC,"@kay, please file a new bug instead."
1808389,2019-09-24 15:22:36 UTC,I'm seeing this very same issue on a new Lenovo T590 running 19.10 with linux-firmware 1.182 and linux-image-generic 5.3.0.10.11. See attached files for more verbose info on the network controller and journalctl logs.
1808389,2020-01-30 19:51:19 UTC,Any updates on this for eoan release?
1808389,2019-04-25 10:00:41 UTC,This bug was fixed in the package linux-firmware - 1.173.5
1808389,2018-12-14 00:24:51 UTC,"It looks like bug:
https://bugs.launchpad.net/bugs/1805088"
1808389,2018-12-14 00:37:16 UTC,I am on 4.18.0-12-generic and I've tried 4.19.6 without joy.
1808389,2019-08-29 20:34:07 UTC,"I have a problem that looks very similar to this one, but it's happening with linux-firmware 1.173.9 and only on my home 5 GHz SSID (the 2.4 GHz SSID connects fine). What do I need to send you in order to have it fixed?"
1808389,2018-12-16 09:10:06 UTC,"I just pushed a firmware that should fix this.
Please try our latest version from https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git/plain/iwlwifi-8265-36.ucode"
1808389,2018-12-17 12:46:10 UTC,Josh just pushed out the new firmware in mainline's linux-firmware.git.
1808389,2018-12-18 04:02:22 UTC,"Thanks, Emmanuel."
1808389,2018-12-18 04:12:22 UTC,I've been running it for two days and it looks good.
1808389,2019-02-08 21:58:54 UTC,"I think the test and regression potential templates on this bug are not up to the normal SRU standard.  There are a number of firmware blobs updated, what is the set of chips that make use of these firmware blobs that could potentially be affected by this update?  Why is this complete range of firmware blobs being updated, if there is a bug being reported with only a single chip?"
1808389,2019-02-11 13:33:34 UTC,"It is because of the way Intel updated the firmware upstream. The updates which brought in the fixes wanted for 8265 wireless also updated these other files, and since the upstream changelog doesn't provide any specifics about what fixes the updates contain we don't know whether or not the update contains the same fixes in the other firmware files. In the past we've generally just pulled in the bundle of updates where the fix was identified. Perhaps Emmanuel can chime in with more information (though I'm pretty sure he'd prefer we were always pulling in the newest firmware anyhow)."
1808389,2019-03-01 18:17:59 UTC,"Seth, my only preference here is that the test cases be appropriate for what's being updated.  If there are going to be updates affecting multiple series of chips, then I think the test case should also cover testing across multiple series.  Otherwise, if that testing is onerous, I think withdrawing this SRU and changing only the firmware for the series we know is affected by this bug would be better."
1808389,2019-11-13 00:20:38 UTC,"On my X1 Carbon 4th gen, kernel 5.3.0-22-generic seems to have completely fixed the issue. Yay!"
1808389,2019-03-25 06:59:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808389,2019-03-25 07:33:55 UTC,"src:linux-firmware is only accepted into cosmic-proposed but still waiting in Bionic-unapproved.
AFAIK the current status of ""Fix committed"" will make it not to be seen by the SRU Team (at least for similar cases I had in the past).
Therefore to increase the chance to get also the Bionic portion accepted into -proposed lets dial back the current status of the bug task."
1808389,2019-03-29 08:47:07 UTC,"Hello James, or anyone else affected,"
1808389,2019-03-29 09:45:13 UTC,I have had no issues anymore since I switched to my self built 1.177~ppa0f22c85 (PPA) - while before they were rather common.
1808389,2019-04-01 05:50:22 UTC,"After a weekend using the wireless (on Bionic) I have got no new
  ""kernel: iwlwifi 0000:04:00.0: Microcode SW error detected.  Restarting 0x2000000.""
entries and I'm still connected (also before it hit really fast).
Therefore I'd think this firmware in proposed is as good as the PPA I used int he last time."
1808389,2019-04-01 08:13:34 UTC,"The version from the PPA did not solve this issue for me on Cosmic, but I've been running the version from proposed over the weekend and the issue did not occur. Looks good so far!"
1808389,2019-04-15 15:20:31 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1808389,2019-04-15 15:20:07 UTC,This bug was fixed in the package linux-firmware - 1.175.3
1808389,2019-04-12 12:19:18 UTC,Added verifiction-done tags for bionic and cosmic based on comments #17 and #18.
1808389,2019-03-22 20:29:16 UTC,"Hello James, or anyone else affected,"
1808396,2019-05-17 02:36:40 UTC,Why is podman popping up in Rocky logs? The Rocky release notes have nothing about podman and I am getting podman pulls in my ansible deployment logs!!!!
1808396,2019-05-17 09:57:25 UTC,"I'm not sure why do we have any mentions of podman for Rocky, like https://review.opendev.org/#/c/588659/4/container-images/tripleo_kolla_template_overrides.j2"
1808397,2019-06-05 07:54:15 UTC,"Note that firefox seems to have the same issue, chromium does display the text though"
1808397,2019-06-05 07:53:48 UTC,"Opening the example it displays that warning
Unimplemented annotation: POPPLER_ANNOT_CARET.  It is a known issue and it might be implemented in the future."
1808412,2018-12-19 14:44:23 UTC,apport information
1808412,2018-12-19 14:44:22 UTC,apport information
1808412,2018-12-19 14:44:20 UTC,apport information
1808412,2018-12-19 14:44:19 UTC,apport information
1808412,2018-12-19 14:44:17 UTC,apport information
1808412,2018-12-20 20:47:56 UTC,I see the same behavior on both Bionic and Xenial on the 4.15.0-43 kernel.
1808412,2018-12-19 14:44:15 UTC,apport information
1808412,2018-12-19 14:44:15 UTC,apport information
1808412,2018-12-19 14:44:13 UTC,apport information
1808412,2018-12-19 14:44:12 UTC,apport information
1808412,2018-12-19 14:44:10 UTC,apport information
1808412,2018-12-14 13:46:04 UTC,"When the memory allocation was stalled, here is what perf top was giving me:
Samples: 483K of event 'cycles:ppp', Event count (approx.): 52114089074
Overhead  Shared Object                             Symbol
  28.53%  [kernel]                                  [k] total_mapcount
  25.34%  [kernel]                                  [k] kvm_age_rmapp
  13.54%  [kernel]                                  [k] slot_rmap_walk_next
  11.24%  [kernel]                                  [k] kvm_handle_hva_range
   6.35%  [kernel]                                  [k] rmap_get_first
   3.69%  [kernel]                                  [k] __x86_indirect_thunk_r13
   1.33%  [kernel]                                  [k] __isolate_lru_page
   0.63%  [kernel]                                  [k] isolate_lru_pages.isra.58
   0.48%  [kernel]                                  [k] page_vma_mapped_walk
   0.40%  [kernel]                                  [k] __mod_node_page_state
   0.35%  [kernel]                                  [k] clear_page_erms
   0.31%  [kernel]                                  [k] shrink_page_list
   0.28%  [kernel]                                  [k] _find_next_bit
   0.27%  [kernel]                                  [k] putback_inactive_pages
   0.27%  [kernel]                                  [k] move_active_pages_to_lru
   0.27%  [kernel]                                  [k] inactive_list_is_low
   0.22%  [kernel]                                  [k] __mod_zone_page_state"
1808412,2018-12-13 20:50:59 UTC,"u cannot run the apport-collect script, but if there is something that is really needed, please ask me and i will do my best give the information."
1808412,2018-12-13 20:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808412,2018-12-19 14:44:16 UTC,apport information
1808412,2018-12-13 20:11:44 UTC,"4.18.0 is also affected.
Installed the pkg on xenial, and the same issue was present, i didn't tested disabling the transparent_hugepage tho."
1808418,2020-04-20 17:27:13 UTC,I'm hopeful that doing the bisect over again will find a more relevant commit. While bisecting this time I ran into a weird scenario the I believe may have affected the previous attempts to do a bisect.
1808418,2020-04-17 19:29:31 UTC,The article I linked was for an AMD CPU so it only helped me up to a certain point.
1808418,2020-04-17 18:19:17 UTC,I'm still tinkering...
1808418,2020-04-17 15:07:43 UTC,"I booted 4.13.0-rc1, removing noapic and adding dis_ucode_ldr. Unfortunately it still doesn't boot."
1808418,2020-04-17 15:13:32 UTC,"After that I tried booting 5.3.0-7642-generic, removing noapic and adding dis_ucode_ldr. And it booted just fine."
1808418,2020-04-22 19:36:41 UTC,"Due to the aforementioned issue, I believe I was getting a lot of false negatives and my previous bisects were faulty as a result."
1808418,2020-04-17 09:19:51 UTC,"Hmm, please try kernel parameter ""dis_ucode_ldr"" to disable microcode loading."
1808418,2020-04-17 15:16:05 UTC,"Oops, please disregard that last message. I'm multitasking :P"
1808418,2020-04-23 08:21:38 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc2/"
1808418,2020-05-04 17:34:51 UTC,I tried booting another half dozen times or so with 5.7 on Ubuntu 20.04 and I didn't have any issues. So maybe it's fixed with that combination? Unfortunately since the wifi doesn't work I can't continue to use the 5.7 kernel.
1808418,2020-04-23 15:18:24 UTC,"> Maybe the bcmwl-kernel-source package just isn't compatible with 5.7 yet?
"
1808418,2020-04-24 20:33:36 UTC,I just upgraded to 20.04 and I can confirm that this bug affects the default 5.4 kernel that it ships with.
1808418,2020-04-27 05:25:11 UTC,Is there any log when the hang happens on v5.7?
1808418,2020-05-05 03:57:33 UTC,"One possible choice is to use the 5.7 kernel here:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap"
1808418,2020-05-28 12:38:53 UTC,I installed 5.7.0-5 from that link but it looks like the bcmwl module still fails to compile:
1808418,2020-06-07 17:08:24 UTC,Oh cool. Is there a page I can check to see when that happens so I can test it? Thanks!
1808418,2020-06-08 03:38:25 UTC,$ rmadison linux
1808418,2021-01-10 17:55:16 UTC,5.8.0-36-generic was just installed as part of the 20.04 HWE and it does not boot without intremap=off.
1808418,2020-04-03 13:11:03 UTC,I'm still seeing this same behaviour for the 5.3 kernel.
1808418,2020-04-23 14:17:20 UTC,"Very odd... 5.7 boots (without noapic or intremap=off), but not consistently."
1808418,2019-07-25 13:32:40 UTC,I can confirm the same behaviour:
1808418,2020-06-03 05:08:14 UTC,"We are gonna have 5.7 lands to 20.10 soon, so the DKMS build fail will also be fixed there."
1808418,2019-03-10 14:37:46 UTC,"> - First, try latest mainline kernel (v5.0) again, hopefully there's a fix already.
No, it looks like it still won't boot (without noapic).
"
1808418,2019-03-11 06:01:07 UTC,Try changing IRQ configs (CONFIG_GENERIC_IRQ_MIGRATION=y to =n) and i2c-designware's (CONFIG_I2C_DESIGNWARE_CORE=y to =m).
1808418,2018-12-17 09:05:58 UTC,"Please try latest mainline kernel [1] without ""noapic"" parameter."
1808418,2018-12-21 15:04:05 UTC,I just tried kernel v4.20-rc7 and without noapic my computer hangs at a blank screen. With noapic it boots fine.
1808418,2018-12-13 21:00:08 UTC,This change was made by a bot.
1808418,2018-12-21 20:16:40 UTC,"I'm not sure if this helps, but I removed noapic and added earlyprintk=efi,keep in an attempt to show some logs. I took a video and extracted the frames. I've gone through them briefly but I don't see any errors or warnings:"
1808418,2018-12-23 06:32:43 UTC,The next step is to find the last working -rc kernel and first non-working -rc kernel.
1808418,2018-12-26 19:04:43 UTC,"I'm still using v4.20-rc7, and I wanted to try some more kernel parameters to narrow down the problem. Since the last kernel messages I got using earlyprintk (https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot7.png) were related to the Spectre mitigations, I removed noapic and replaced it with spec_store_bypass_disable=off and it booted. Oddly enough then I removed spec_store_bypass_disable=off altogether and it booted without any special parameters."
1808418,2018-12-29 19:13:38 UTC,"I tried to boot with an older kernel (4.15.0-43), and it wouldn't boot without noapic. But v4.20-rc7 seems to boot fine. I guess it must've been a fluke that it didn't boot for me the first time."
1808418,2019-01-14 10:18:40 UTC,Maybe you can try adding 'apic=debug' and remove 'quiet splash' parameters when you boot and see if kernel shows more messages that can point to the problem.
1808418,2019-01-14 16:45:40 UTC,"I'm assuming I should add apic=debug to a kernel that has the bug (and not one that boots fine), correct?"
1808418,2019-01-26 15:59:51 UTC,"I tested a few kernels, and v4.12.14 is the last kernel that works without noapic. Starting with v4.13-rc1 my computer will hang on boot unless I use noapic."
1808418,2019-01-25 17:46:23 UTC,"I haven't reformatted my machine in years and was running into some other issues, so I just did a reinstall of 18.04. With both the install media and the latest 18.04 kernel (4.15.something), I needed noapic."
1808418,2019-01-26 16:01:28 UTC,Here's the kernel log from v4.12.14 (with apic=debug)
1808418,2019-03-06 11:15:58 UTC,"- First, try latest mainline kernel (v5.0) again, hopefully there's a fix already.
- Does the issue happen 100% of the time? Otherwise the bisection can be inconclusive.
- Or, take a look kernel config on v4.12 and v4.13-rc1 - maybe some new option breaks your system."
1808418,2019-01-26 16:28:07 UTC,So I guess v4.12 also works? Let's do a kernel bisection:
1808418,2019-02-22 18:38:03 UTC,"I finally got around to doing the bisect, and here's the result:"
1808418,2019-02-25 13:27:27 UTC,"The commit is not correct. When doing a bisection, please skip stable release, (e.g. 4.12.1), and use mainline release (e.g. 4.12)."
1808418,2019-02-25 14:04:15 UTC,I followed your instructions exactly as written. How can I use the mainline release?
1808418,2019-02-26 01:52:48 UTC,"This is really weird. I don't think you system has ""ccree"" device which only presents on ARM devices."
1808418,2019-02-26 15:27:49 UTC,"This is the correct commit, right?:"
1808418,2019-01-26 16:01:05 UTC,Here's the kernel log from v4.12.14
1808418,2019-02-27 03:55:10 UTC,You are right.
1808418,2019-02-27 04:06:55 UTC,"Oh it's a merge point so there are still some commits:
$ git diff e5770b7bdbfe..32c1431eea48"
1808418,2019-02-28 20:19:01 UTC,This is what I'm getting:
1808420,2019-05-01 10:56:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808421,2020-11-15 16:20:58 UTC,"It seems gparted is interpreting data from blkid. In this case, when PTTYPE is 'gpt', that should just take precedence over TYPE being 'zfs_member'."
1808421,2020-08-13 12:12:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808421,2020-06-24 21:42:52 UTC,Any resolution on this? Has anyone contacted people who work on util-linux?
1808421,2019-07-31 19:26:17 UTC,I experience the same problem. Is there a workaround?
1808421,2018-12-13 22:15:48 UTC,From the description it appears that at one time the whole disk was formatted as zfs and that those file system signatures remain.
1808421,2019-04-23 18:49:27 UTC,"If other partitions on the disk the display is correct, if only 2 zfs partitions are on the disk the display is wrong. The disk have been partitioned originally with the gnome-disk-utility."
1808421,2019-04-23 18:44:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808421,2018-12-14 03:40:04 UTC,"Yes, the issue you are experiencing looks similar."
1808421,2018-12-13 23:21:57 UTC,"It looks like your comment is appropriate:
86204"" TYPE=""zfs_member"" PTUUID=""eba09d2e-0f70-4d11-8e37-c1c170cfd9dd""
PTTYPE=""gpt"""
1808421,2019-04-23 18:52:08 UTC,"And now the complex SDD (boot-datapool, 2xlog and 2xcache partitions) displayed correctly"
1808421,2018-12-13 22:20:58 UTC,Alternatively you may need a fixed version of blkid if blkid is reporting 2 contradictory signatures for the whole disk:
1808421,2018-12-13 23:17:17 UTC,"That gitlab issue looks like what I'm seeing. I've collected the requested information. Can you confirm this is the problem?
hbarta@saugage:~$ sudo blkid /dev/sda
[sudo] password for hbarta:
/dev/sda: LABEL=""rpool"" UUID=""4510611204828545482"" UUID_SUB=""9816084798696086204"" TYPE=""zfs_member"" PTUUID=""eba09d2e-0f70-4d11-8e37-c1c170cfd9dd"" PTTYPE=""gpt""
hbarta@saugage:~$ sudo wipefs --no-act /dev/sda
DEVICE OFFSET       TYPE       UUID                LABEL
sda    0xe8e0d3f000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d3e000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d3d000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d3c000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d3b000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d3a000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d39000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d38000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d37000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d36000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d35000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d34000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d33000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d32000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d31000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d30000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d2f000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d2e000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d2d000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d2c000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d2b000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d2a000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d29000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d28000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d27000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d26000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d25000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d24000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d23000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d7f000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d7e000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d7d000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d7c000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d7b000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d7a000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d79000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d78000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d77000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d76000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d75000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d74000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d73000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d72000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d71000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d70000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d6f000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d6e000 zfs_member 4510611204828545482 rpool
sda    0xe8e0d6d000 zfs_member 4510611204828545482 rpool
sda    0..."
1808421,2018-12-13 21:18:01 UTC,Problem gparted display.
1808428,2018-12-15 10:47:34 UTC,"Thank you for your bug report, that looks similar to the bug fixed in https://github.com/iputils/iputils/pull/100"
1808432,2019-01-03 01:21:53 UTC,This is related to https://github.com/systemd/systemd/issues/661
1808435,2019-10-06 22:28:05 UTC,"Sorry, Ubuntu MATE 16.04 is now EOL."
1808440,2018-12-16 03:49:26 UTC,"Hi @Yulong Song,"
1808440,2019-08-20 01:05:25 UTC,I am going to close this bug due to no activity within 90 days.
1808450,2019-08-20 15:21:12 UTC,"This won't be fixed in Ubuntu only, so what's the point with setting higher importance for Ubuntu compared to upstream?"
1808450,2019-08-20 15:49:28 UTC,"> No need to mansplain.
"
1808450,2019-08-20 05:57:20 UTC,No need to mansplain. I’ve been translating software for more than a decade; I know my typography.
1808450,2018-12-14 10:24:20 UTC,"Note we're not using ""English"" quotes (“”), but rather the ASCII ""quotation mark"" glyph, which is a compromise."
1808450,2019-08-20 15:49:49 UTC,"strconv.Quote, sorry."
1808456,2019-02-28 20:38:42 UTC,This issue was fixed in the openstack/glance_store 0.28.0 release.
1808460,2018-12-19 23:41:12 UTC,"Hi, solved it.
Used dconf-editor, went to org/gnome/terminal
Right click on terminal and click on reset recursively and approve.
that sorted it.
Thanks
koli"
1808466,2018-12-20 00:28:51 UTC,"I think the best course of action here (for 2.4.x) is simply to disable the raft workers. They are not used for anything in particular in 2.4.
Just add the ""disable-raft"" feature flag to the controller config and the raft workers should shut down."
1808472,2021-01-30 21:27:19 UTC,superseded by poelzi's https://github.com/mixxxdj/mixxx/pull/3063
1808472,2020-09-28 01:03:52 UTC,"stalled.
https://github.com/mixxxdj/mixxx/pull/2378"
1808472,2018-12-20 17:35:45 UTC,"hmm the main issue here seems to be that my mouse makes the current not-yet-focused table view jump ~20 lines up as soon as I use the mouse scroll wheel; I noticed this behaviour in other apps, as well."
1808472,2019-09-14 19:26:39 UTC,the reason seems to be that the first table cell is somehow focused and the selection jumps there when keys or selection controls attempt to move it.
1808472,2018-12-16 23:04:13 UTC,"I cannot confirm this with the current master using mouse.
After creating a new carte and than clicking back on the Track tree icon, the scrol bar search and highlighting are back.
Any idea what else can I do to reproduce the issue."
1808472,2019-01-07 16:38:41 UTC,"I updated the report, it now just describes the scroll position jump when using a controller."
1808472,2020-09-03 09:43:00 UTC,It this fixed now or in progress by one of the related PRs?
1808472,2019-09-11 18:22:37 UTC,I can confirm this. I t happens also if you use the up and down keys on keyboard.
1808475,2019-01-10 19:19:45 UTC,"The pull request is closed, but not because it was merged I think. Was another one opened, and was that one merged?"
1808475,2019-01-11 01:56:28 UTC,"well, I have not opened a new one yet. I'd like to wait for https://github.com/sosreport/sos/pull/1523 to be merged first."
1808475,2019-01-11 16:45:17 UTC,"Cool, please update this bug once you have one."
1808475,2020-09-23 12:03:13 UTC,"There was a PR, that has been 'closed' by the author of the PR himself."
1808475,2020-11-23 04:17:16 UTC,[Expired for sosreport (Ubuntu) because there has been no activity for 60 days.]
1808476,2019-12-16 13:25:48 UTC,This bug was fixed in the package python2.7 - 2.7.17-1~18.04
1808476,2019-12-06 06:37:45 UTC,"All autopkgtests for the newly accepted python2.7 (2.7.17-1~18.04) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1808476,2019-04-06 18:39:13 UTC,This bug was fixed in the package python2.7 - 2.7.16-2
1808476,2019-04-29 16:47:55 UTC,This bug was fixed in the package python2.7 - 2.7.16-2~18.10
1808476,2019-04-11 20:06:13 UTC,"Hello Dimitri, or anyone else affected,"
1808476,2019-12-05 21:19:41 UTC,"Hello Dimitri, or anyone else affected,"
1808495,2019-02-21 15:41:35 UTC,Can you extract the log from /var/log/installer/subiquity-debug.log and get it to me somehow? I don't think I can fix it without more information.
1808499,2018-12-14 08:18:49 UTC,not working Windows example?
1808506,2018-12-14 08:49:03 UTC,"As an example of the error, when using the multi-pool driver, upon a kuryr-controller restart, trying to recover the precreated neutron ports will fail with:
2018-12-13 16:31:53.328 1 ERROR oslo_service.service [-] Error starting thread.: TypeError: sequence item 0: expected string, NoneType found
2018-12-13 16:31:53.328 1 ERROR oslo_service.service Traceback (most recent call last):
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/oslo_service/service.py"", line 796, in run_service
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     service.start()
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/kuryr_kubernetes/controller/service.py"", line 112, in start
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     self.pool_driver.sync_pools()
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/kuryr_kubernetes/controller/drivers/vif_pool.py"", line 855, in sync_pools
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     vif_drv.sync_pools()
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py"", line 328, in inner
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     return f(*args, **kwargs)
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py"", line 328, in inner
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     return f(*args, **kwargs)
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/kuryr_kubernetes/controller/drivers/vif_pool.py"", line 299, in sync_pools
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     self._recover_precreated_ports()
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/kuryr_kubernetes/controller/drivers/vif_pool.py"", line 416, in _recover_precreated_ports
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     vif = ovu.neutron_to_osvif_vif(vif_plugin, port, subnet)
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/kuryr_kubernetes/os_vif_util.py"", line 347, in neutron_to_osvif_vif
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     name=vif_translator, invoke_on_load=False)
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/stevedore/driver.py"", line 61, in __init__
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     warn_on_missing_entrypoint=warn_on_missing_entrypoint
2018-12-13 16:31:53.328 1 ERROR oslo_service.service   File ""/usr/lib/python2.7/site-packages/stevedore/named.py"", line 88, in __init__
2018-12-13 16:31:53.328 1 ERROR oslo_service.service     ', '.join(self._missing_names))
2018-12-13 16:31:53.328 1 ERROR oslo_service.service TypeError: sequence item 0: expected string, NoneType found
2018-12-13 16:31:53.328 1 ERROR oslo_service.service"
1808506,2018-12-17 16:42:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/625655"
1808506,2018-12-18 15:02:22 UTC,"Reviewed:  https://review.openstack.org/625655
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=040bea51d5695227b340676685eaf3eaece5f4d2
Submitter: Zuul
Branch:    master"
1808509,2019-03-19 13:34:17 UTC,Is this still an issue?
1808509,2019-02-04 16:28:41 UTC,Any updates on this bug ?
1808518,2019-01-07 16:39:29 UTC,"Review in progress for https://review.opencontrail.org/48529
Submitter: Édouard Thuleau (<email address hidden>)"
1808518,2018-12-26 09:07:38 UTC,"Review in progress for https://review.opencontrail.org/48368
Submitter: Jean-Philippe Braun (<email address hidden>)"
1808518,2019-01-07 16:39:16 UTC,"Review in progress for https://review.opencontrail.org/48528
Submitter: Édouard Thuleau (<email address hidden>)"
1808518,2019-02-01 07:13:32 UTC,"Reviewed:  https://review.opencontrail.org/48529
Committed: http://github.com/Juniper/contrail-controller/commit/89bf1a8eb99ab38ea21b56a5e8cc8516432a4ea4
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1808518,2019-02-01 08:27:07 UTC,"Reviewed:  https://review.opencontrail.org/48527
Committed: http://github.com/Juniper/contrail-controller/commit/d092d65c4155790c69d6e93f7ea46e0f3e984746
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1808518,2019-01-07 16:39:06 UTC,"Review in progress for https://review.opencontrail.org/48527
Submitter: Édouard Thuleau (<email address hidden>)"
1808518,2019-01-07 17:36:32 UTC,"Reviewed:  https://review.opencontrail.org/48368
Committed: http://github.com/Juniper/contrail-controller/commit/c67b8dde7da032a9adab592a19e0034a249e8713
Submitter: Zuul (<email address hidden>)
Branch:    R3.2"
1808518,2019-02-01 08:28:03 UTC,"Reviewed:  https://review.opencontrail.org/48528
Committed: http://github.com/Juniper/contrail-controller/commit/6bba357726eca3cdc8f57eaf76536a6357088d3a
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    R5.0"
1808522,2018-12-15 10:54:59 UTC,"solved - transfer to old 14 lts version, works perfectly"
1808540,2019-01-17 11:59:56 UTC,"The banner issue seems to have gone away, but I'm still seeing broken images for the 'installed' badge."
1808540,2020-01-16 16:11:47 UTC,Can you please confirm if you are still seeing this issue?
1808540,2020-01-16 16:28:50 UTC,Looks good now.
1808541,2018-12-20 10:08:18 UTC,Hello Anton:
1808541,2018-12-20 12:15:24 UTC,Hello Rodolfo
1808541,2018-12-20 12:32:59 UTC,"Not sure, but looks like the root cause is in how tap device is removed from the ovs bridge:"
1808541,2018-12-20 16:48:44 UTC,Hi Anton:
1808541,2019-01-07 11:15:38 UTC,Hi:
1808541,2018-12-20 09:27:55 UTC,Hello Anton:
1808543,2019-06-05 21:19:53 UTC,"Reviewed:  https://review.opendev.org/663077
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=9019e2ce104f0805cfa89513ebd97cf694415183
Submitter: Zuul
Branch:    stable/stein"
1808543,2019-06-04 15:56:50 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/663078"
1808543,2019-05-23 18:19:33 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/661077"
1808543,2019-05-27 15:32:23 UTC,"Reviewed:  https://review.opendev.org/661077
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=c5dcce8879b45682c19ec6cce898273f99a16552
Submitter: Zuul
Branch:    master"
1808543,2019-06-04 15:56:37 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/663077"
1808543,2019-06-05 13:55:25 UTC,"Reviewed:  https://review.opendev.org/663078
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=d57676fd11b63cdb648a336517548672cf162220
Submitter: Zuul
Branch:    stable/rocky"
1808546,2019-01-17 22:18:11 UTC,"Reviewed:  https://review.opencontrail.org/48267
Committed: http://github.com/Juniper/contrail-vrouter/commit/108368ac733d5623d4c256e99c35a30dbd484c74
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1808546,2018-12-19 15:00:21 UTC,"Review in progress for https://review.opencontrail.org/48267
Submitter: sagarkchitnis (<email address hidden>)"
1808546,2018-12-14 17:02:10 UTC,"Upon investigation, the problem is in dp-core."
1808550,2020-01-10 18:11:51 UTC,"I think this is probably still an issue, marking as triaged."
1808551,2019-10-31 03:43:55 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1808555,2020-08-22 04:17:27 UTC,[Expired for OpenStack nova-cloud-controller charm because there has been no activity for 60 days.]
1808555,2020-06-22 21:17:42 UTC,"If this issue persists, please provide new logs, juju-crashdump, and sanitized bundle artifacts -- with debug logging turned on for nova-cloud-controller, keystone and keystone-ldap.  Thank you."
1808555,2019-04-05 14:59:54 UTC,"The 10.244.40.91 address that it's getting a no route to host on is a VIP.
I would suspect there is some problem with the VIP assignment."
1808555,2019-01-16 16:06:30 UTC,https://solutions.qa.canonical.com/#/qa/testRun/95186358-9e2a-4bd9-957d-c6fd94960549
1808555,2019-04-05 14:10:56 UTC,It might be useful to run with 'debug: true'. I see your bundle only has debug on for keystone-ldap. Although with that said I don't think this is pointing at a nova-cc issue.
1808555,2019-04-05 12:57:31 UTC,"Hi Jason, I'm taking a look at the crashdump."
1808555,2019-03-27 23:59:53 UTC,we need to move this to a n-c-c charm bug.
1808555,2019-04-04 14:13:21 UTC,"sub'd to field high - we have been hitting this since December, twice in the last 10 days."
1808555,2019-04-05 14:41:21 UTC,I was going to take a look at SSL termination config in the crashdump but there are no /etc/apache2 directories in the crashdump. I'm not sure why.
1808555,2019-04-05 13:56:22 UTC,"Looking at the hacluster and nova-cc logs, nothing is jumping out:"
1808555,2019-04-05 14:10:16 UTC,"There are also no obvious errors in nova API logs (other than the typical early deployment sqlite errors that occur prior to percona bing introduced to the deployment):
./21/lxd/5/var/log/nova/nova-api-os-compute.log
./20/lxd/5/var/log/nova/nova-api-os-compute.log
./18/lxd/5/var/log/nova/nova-api-os-compute.log"
1808560,2019-05-13 08:34:27 UTC,Can you please include a reproducing bundle?
1808560,2018-12-14 17:44:54 UTC,juju crashdump logs part1
1808560,2018-12-14 17:48:17 UTC,juju crashdump logs part2
1808560,2019-07-13 04:18:01 UTC,[Expired for OpenStack hacluster charm because there has been no activity for 60 days.]
1808569,2018-12-14 22:03:46 UTC,"Another example, from FreeCAD. The item which was selected before opening is highlighted and the last in the list."
1808569,2018-12-14 19:42:32 UTC,"Application: kicad
Version: (6.0.0-rc1-dev-1388-g3e640030f), debug build
Libraries:
    wxWidgets 3.0.3
Platform: Linux 4.13.0-46-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.8.0
    Compiler: GCC 7.2.0 with C++ ABI 1011"
1808569,2018-12-14 19:44:45 UTC,They need to be scrolled because the item you have currently selected is at the bottom of the list.
1808569,2019-01-28 18:05:58 UTC,"I just looked at the revert difficulty and realized there were multiple commits that touched this.  Not fun, so I'll revert.  I'm going to reset this item for addressing during v6 so I don't forget it."
1808569,2019-01-28 15:37:38 UTC,Hi Jeff-. That would be great thanks.  I have a few thoughts on the cause but they can wait for v6
1808569,2019-01-28 13:30:16 UTC,"@Seth, do you want me to back this change out, or are you still looking at it?"
1808569,2019-01-13 13:12:00 UTC,"On OSX, issues with wxComboBox in auiToolbars are not recent."
1808569,2018-12-14 21:49:25 UTC,"No. As can be seen in the screenshot, there's plenty of room in the bottom of the list area. It's unnecessarily wasted space. It should be opened so that the whole area is filled. For example, attached is LibreOffice font size combobox list when it's opened. The selected value is highlighted and centered but the whole list area is in use. That's how comboboxes usually behave and look. KiCad's behavior is very annoying."
1808569,2019-01-13 10:55:35 UTC,"@Seth,"
1808569,2019-01-13 03:45:38 UTC,@Jeff-
1808569,2019-01-13 10:57:39 UTC,"That last part is odd since clicking the text part of an owner-drawn popup /does/ work (for instance, the layer popup just above the problematic ones)."
1808569,2019-01-11 18:37:53 UTC,"Well, shoot.  I've been trying to get the kicad-mac-builder compile working again on my machine for a couple days without success.  Some python compile error.  I guess we should back out and live with it for 5.1 until I can spend some quality time petting the mac build.  No point in holding 5.1 back for this."
1808569,2018-12-14 22:14:03 UTC,"Probably this depends on GTK and so is out of bounds for KiCad development. I can accept that. But it's still bad usability. I'll change this to Opinion (""doesn't fit with the project"") to satisfy myself."
1808569,2019-01-04 00:09:00 UTC,"Fixed in revision 7d06651a1040348d0459fd575755bfd3bd152149
https://git.launchpad.net/kicad/patch/?id=7d06651a1040348d0459fd575755bfd3bd152149"
1808569,2019-01-10 00:54:17 UTC,"@Seth, this breaks them on OSX completely.  I looked at adding conditional compilation, but it would affect a lot of places (including requiring some solution for .fbp files).  Mind if we back it out and just live with it?"
1808569,2019-01-10 01:12:09 UTC,Ugh.  Sorry!  Broken how?
1808569,2018-12-14 22:32:20 UTC,"Thanks, those are good examples.  I see that you want a combobox instead of a choicebox.  That probably makes sense for this use case.  And you are correct, the usability is better."
1808569,2019-01-10 13:20:05 UTC,"Oh, and the fix for drawing ""---"" as a separator line doesn't work (but we could probably move that if the other stuff worked)."
1808569,2019-01-10 17:58:13 UTC,That sounds really bad.  I haven't been able to test Mac builds in a while as the nightly server hasn't generated a new build in a week or so.
1808569,2019-01-10 18:40:05 UTC,"They're pretty dodgy on Mac.  The libedit part selector works, but the items don't highlight as you hover over them, so it feels like it's not working."
1808569,2019-01-10 13:18:50 UTC,"Menus pop-up, but there's no highlighting in them and clicking on items does nothing (other than close the pop-up)."
1808569,2019-01-11 19:35:05 UTC,Sigh. I was so happy and thankful.
1808576,2018-10-31 01:55:46 UTC,"Created attachment 1499189
File: open_fds"
1808576,2020-01-20 20:54:50 UTC,"So... How about a fix!
For Ubuntu 18.04.3 the bug happens when you inadvertently hit the gnome-control-center devices/thunderbolt section.
gnome-control-center segfaults and will not restart! Fault:
(gnome-control-center:8315): thunderbolt-cc-panel-WARNING **: 15:36:34.212: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked."
1808576,2019-03-06 14:47:42 UTC,The new version including the fix is in disco
1808576,2019-01-08 16:41:40 UTC,The bug has been fixed upstream now
1808576,2018-12-18 12:34:37 UTC,Reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/318
1808576,2018-10-31 01:55:48 UTC,"Created attachment 1499190
File: proc_pid_status"
1808576,2018-10-31 01:55:44 UTC,"Created attachment 1499188
File: mountinfo"
1808576,2018-10-31 01:55:24 UTC,"Created attachment 1499186
File: limits"
1808576,2018-10-31 01:54:53 UTC,"Description of problem:
Hi! i open the Control Center after upgrading to F29."
1808576,2018-10-31 01:55:06 UTC,"Created attachment 1499179
File: backtrace"
1808576,2018-10-31 01:55:42 UTC,"Created attachment 1499187
File: maps"
1808576,2018-10-31 01:55:08 UTC,"Created attachment 1499180
File: cgroup"
1808576,2018-10-31 01:55:22 UTC,"Created attachment 1499185
File: exploitable"
1808576,2018-10-31 01:55:20 UTC,"Created attachment 1499184
File: environ"
1808576,2018-10-31 01:55:18 UTC,"Created attachment 1499183
File: dso_list"
1808576,2018-10-31 01:55:14 UTC,"Created attachment 1499182
File: cpuinfo"
1808576,2018-10-31 01:55:12 UTC,"Created attachment 1499181
File: core_backtrace"
1808580,2018-12-14 21:19:49 UTC,OpenSRF branch is working/user/dyrcona/lp1808580-remove-ubuntu-trusty: http://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/dyrcona/lp1808580-remove-ubuntu-trusty
1808580,2019-02-19 06:00:58 UTC,Pushed to OpenSRF master and backported to rel_3_1 series.
1808581,2018-12-15 23:42:27 UTC,"Oops.  I had previously turned off my printer.  Now, with the printer on:"
1808581,2018-12-15 23:34:27 UTC,"Forget the last post, please. It's in the error_log."
1808581,2018-12-15 23:20:33 UTC,Apologies for the typos.
1808581,2018-12-15 23:00:42 UTC,"I get no output.  It runs for about 5 seconds and returns to the prompt:
kim@kim-MS-7865:/usr/lib/cups/backend$ /usr/lib/cups/backend/cnijnet
kim@kim-MS-7865:/usr/lib/cups/backend$"
1808581,2018-12-15 22:38:41 UTC,It seems that the only way to contact the printer is with the cnijjet backend. One last last thing if you would: execute
1808581,2018-12-15 21:00:25 UTC,Thank you.  It may be a week or two until I have time to reinstall drivers.  I will repost if that helps.  Let me know if I should do anything else today.
1808581,2018-12-15 20:48:36 UTC,Let me know if you agree.
1808581,2018-12-15 20:43:48 UTC,Thanks.
1808581,2018-12-15 20:34:58 UTC,"I think my only other option is to de-install and re-install the printer driver.  That is a pain because Canon does not support Linux drivers.  I have to search the web for the latest version from a hopefully reliable source.  It takes a day.  Doing this always results in inconsistent results for print and scan function on the printer.  Sometimes only print works, other times only scan.  Since this happened when I upgraded my machine to 18.04, re-installing may be the best answer."
1808581,2018-12-15 20:01:15 UTC,"> I ran commands:
> sudo lpadmin -p mx860 -v socket://192.168.1.87:9100 -E -P /etc/cups/ppd/MX860.ppd
> and lp -d mx860 /etc/nsswitch.conf
"
1808581,2018-12-15 19:45:55 UTC,"The printer continues to be connectable via the printer web host.
http://192.168.1.87/English/pages_WinUS/_top.html"
1808581,2018-12-15 19:44:09 UTC,Print job submitted and hung:
1808581,2018-12-15 19:24:26 UTC,"> -rw-r----- 1 root lp 131822 Dec 14 13:17 MX860.ppd
"
1808581,2018-12-15 18:51:51 UTC,"There was an error above:
PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MX860.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MX860.ppd: Permission denied"
1808581,2018-12-15 18:48:52 UTC,"/etc/cups/ppd/MX860.ppd:
*cupsFilter:	""application/vnd.cups-raster 100 rastertogutenprint.5.2"""
1808581,2018-12-15 17:43:41 UTC,"I'm a little perplexed, Kim, because CUPS appears not to detect your printer. Anyway, we'll leave that on one side and look at the error_log and at the line"
1808581,2018-12-15 15:47:13 UTC,"kim@kim-MS-7865:~$ lpinfo -v
network lpd
direct hp
network ipps
network http
network https
network ipp
file cups-brf:/
network beh
network socket
serial serial:/dev/ttyS0?baud=115200
network smb
network bjnp
direct hpfax
kim@kim-MS-7865:~$"
1808581,2018-12-15 10:43:04 UTC,Please supply the output of 'lpinfo -v'
1808581,2018-12-15 20:13:16 UTC,kim@kim-MS-7865:/etc/cups/ppd$ nmap 192.168.1.87
1808581,2018-12-15 19:48:19 UTC,"I ran commands:
sudo lpadmin -p mx860 -v socket://192.168.1.87:9100 -E -P /etc/cups/ppd/MX860.ppd
and
lp -d mx860 /etc/nsswitch.conf"
1808590,2018-12-14 21:39:15 UTC,We will need to check policy.json with users in two different domains:
1808590,2019-11-08 13:28:56 UTC,This is probably better done (now) with the policy.d overrides options in the designate charm.  Note that they are in a 'preview' state (on designate) as the functional tests haven't been done as designate charm tests have not yet been migrated to zaza: https://bugs.launchpad.net/charm-designate/+bug/1845639
1808594,2019-01-11 01:21:54 UTC,"@Dan,"
1808594,2020-03-24 21:59:29 UTC,"This RFE is clone of https://bugs.launchpad.net/neutron/+bug/1808062 which was created for VXLAN network and is already approved by drivers team.
So I will mark this one as approved too based on approval of https://bugs.launchpad.net/neutron/+bug/1808062"
1808594,2019-01-11 01:19:49 UTC,"@usha veepuri,"
1808594,2019-01-29 09:46:58 UTC,"@minsel,"
1808600,2018-12-15 00:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808600,2019-05-23 15:32:55 UTC,"Idk if bumping is permitted, but it would be nice if someone would interest in this one, especially you can get microSD cards that are 1TB capacity already"
1808600,2018-12-15 18:50:07 UTC,apport information
1808600,2018-12-15 18:50:05 UTC,apport information
1808600,2018-12-15 18:50:03 UTC,apport information
1808600,2018-12-15 18:50:02 UTC,apport information
1808600,2018-12-15 18:49:49 UTC,apport information
1808600,2018-12-15 18:50:00 UTC,apport information
1808600,2018-12-15 18:49:52 UTC,apport information
1808600,2018-12-15 18:49:51 UTC,apport information
1808600,2018-12-15 18:49:54 UTC,apport information
1808600,2018-12-15 18:50:01 UTC,apport information
1808600,2018-12-15 18:49:59 UTC,apport information
1808600,2018-12-15 18:49:58 UTC,apport information
1808600,2018-12-15 18:49:56 UTC,apport information
1808600,2018-12-15 18:49:55 UTC,apport information
1808601,2019-01-28 06:44:51 UTC,"I have the same issue, except with Alt+Space. I've got Albert set to use that as a global shortcut, but it doesn't work within Terminator even though there's no Terminator keybinding for Alt+Space."
1808613,2018-12-15 05:32:37 UTC,See also bug 1808614.
1808613,2019-01-14 12:52:30 UTC,I think the issue here is that ssh is managed through ssh commands and is tied to the ssh-keys that are available. It's not as cleanly tied to just permissions. I wonder that if your user still had a valid ssh key available on the machines in the model and that was causing issues.
1808613,2019-01-14 13:53:32 UTC,Once 'admin' model access is revoked from the user with 'superuser' controller access that user can no longer connect.
1808616,2019-01-08 16:58:57 UTC,"Thanks, more clear error messaging is definitely useful."
1808616,2019-11-13 12:51:21 UTC,This seems to have been fixed some releases ago:
1808617,2019-05-18 22:45:34 UTC,Recent bug report: http://beefy12.nyi.freebsd.org/data/head-amd64-default/p500768_s347066/logs/esys-particle-2.3.5_4.log (IPv6)
1808617,2019-05-18 23:03:15 UTC,Correction: recent log: http://beefy12.nyi.freebsd.org/data/head-amd64-default/p500768_s347066/logs/esys-particle-2.3.5_4.log
1808623,2019-05-28 16:20:53 UTC,Same in Ubuntu 19.04 with hplip-3.19.1 and hplip-3.19.5
1808623,2018-12-15 17:04:45 UTC,"> i tried  but  error msg :  debian-9.6 version is not supported.
"
1808623,2018-12-15 10:33:30 UTC,i tried  but  error msg :  debian-9.6 version is not supported.
1808623,2018-12-15 10:05:42 UTC,See
1808623,2018-12-17 07:20:56 UTC,Hello
1808623,2018-12-17 03:58:43 UTC,"Hi Bruno,"
1808626,2018-12-15 15:57:18 UTC,Here's a listing of my hardware:
1808626,2018-12-24 13:28:50 UTC,I've been running the same setup and it runs absolutely perfectly if I boot up with editing the Ubuntu command line in grub and add video=VGA-1:e
1808626,2018-12-27 15:12:16 UTC,I've been hesitant to try to reproduce this because my system runs so well for a long time when this doesn't crop up.
1808626,2018-12-27 15:32:39 UTC,And another video of just dragging the display settings window around:
1808626,2018-12-27 17:34:35 UTC,"Been fiddling with rotating and unrotating displays and when it starts drawing improperly when rotated, I can unrotate the displays and the improper drawing/flickering disappears."
1808626,2018-12-30 17:29:01 UTC,I didn't think that Ubuntu's SimpleScreenRecorder would record the corruption but it records it just fine:
1808626,2020-02-26 16:11:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808626,2020-02-27 17:58:40 UTC,Any other workarounds?
1808632,2020-08-29 09:12:21 UTC,"#3049 that enforces a selection on FocusIn events of WLibraryTableView:
no previously focused item: select first
previously focused item, but no selection: select previous item"
1808632,2020-09-28 00:49:25 UTC,https://github.com/mixxxdj/mixxx/pull/3090
1808632,2020-08-29 09:03:19 UTC,https://github.com/mixxxdj/mixxx/pull/3049
1808632,2019-07-09 18:57:36 UTC,"So far I used gdb only to create crash reports.
I'll see if I can wrap my head around that, but I'm afraid this won't happen soon as there are other issues more itching and more likely for me to solve them."
1808632,2019-06-27 10:32:31 UTC,@daschuer What easy solution do you propose?
1808632,2019-06-28 23:08:10 UTC,I do not have a recipe for an easy fix.
1808632,2019-09-11 12:30:27 UTC,So far I've found out that the first table row is always soemhow focused but not selected/highlighted.
1808632,2018-12-15 21:46:48 UTC,I can confirm the issue with Mixxx 1.2.5 as well.
1808633,2018-12-15 14:55:11 UTC,this is the line from corresponding file in /etc/apt/sources.list.d
1808637,2018-12-17 08:40:52 UTC,"Hi Dezi,"
1808637,2019-01-10 19:32:10 UTC,I can confirm this is happening in disco.
1808642,2018-12-15 17:53:59 UTC,"Hello,"
1808644,2020-03-21 07:05:07 UTC,Closing because CAN'T REPLICATE.
1808645,2018-12-15 17:43:13 UTC,Also filed here:
1808645,2020-03-21 06:15:57 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1808647,2019-12-18 17:55:19 UTC,"This bug is believed to be fixed in cloud-init in version 19.4. If this is still a problem for you, please make a comment and set the state back to New"
1808647,2019-11-20 17:56:14 UTC,https://github.com/canonical/cloud-init/commit/62bbc262c3c7f633eac1d09ec78c055eef05166a
1808647,2019-11-20 17:55:23 UTC,Merge Proposal migrated to github:
1808647,2019-09-09 04:17:34 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1808647,2019-09-09 15:37:55 UTC,bump to keep alive
1808647,2019-07-07 00:21:44 UTC,Thanks for the fast response Ryan!
1808647,2019-07-01 16:20:17 UTC,"The log looked a bit strange, it shows cloud-init 0.7.9, not 18.2.  In any case, it still reproduced on master.  The provided network-config is to dhcp4 and dhcp6 on the primary interface."
1808647,2019-07-01 14:54:53 UTC,"Hello since this issue is pending a look from a cloud-init maintainer, could we please reopen?"
1808647,2019-06-29 04:17:32 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1808647,2019-04-29 15:46:36 UTC,"If you need a repro case, here's how I generate the base centos AMI: https://github.com/irvingpop/packer-chef-highperf-centos7-ami/blob/master/create_base_ami/create_base_ami.sh"
1808647,2019-04-29 15:42:13 UTC,"collect-logs attached, thank you for taking a look!"
1808647,2019-04-29 14:21:03 UTC,"Hello,"
1808647,2019-07-10 23:35:19 UTC,"absolutely!  the behavior is identical whether `IPV6_AUTOCONF=yes` is in /etc/sysconfig/networking or if the line is totally omitted (presumably because IPV6FORWARDING is not set to ""yes""?)"
1808647,2019-07-08 16:21:47 UTC,Thanks for the additional information. Could you also provide the output of the same commands this time with IPV6_AUTOCONF=yes?
1808649,2018-12-18 16:12:51 UTC,"Now that courier is compiled with gnutils instead of openssl the only setting in pop3d-ssl or imapd-ssl that will limit the ciphers or protocols is the setting TLS_PRIORITY.
Example: TLS_PRIORITY=""SECURE128:+SECURE192:-VERS-ALL:+VERS-TLS1.2""
You can test pop with:
nmap --script ssl-enum-ciphers -p 995 localhost
. /etc/courier/pop3d-ssl
gnutls-cli --priority=""$TLS_PRIORITY"" --list"
1808649,2018-12-18 16:45:43 UTC,Idézem/Quoting Gerald Drouillard <email address hidden>:
1808657,2018-12-15 23:23:47 UTC,"Removing the maybe-ubiquity from the boot params, booted to live session 3 out 3 attempts."
1808657,2018-12-15 23:29:59 UTC,"Another note, in the last 2 years, Ubiquity has never booted correctly on this hardware so this problem is not something new.  I never realized the issue was ubiquity until today.  (Neon live booted on this laptop without requiring nomodeset and thus provided the ubiquity clue as Neon does not use ubiqutiy)."
1808657,2019-08-06 03:00:32 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1808661,2019-11-13 16:30:02 UTC,"Just tested this, this should be done as well. Marking it as fixed"
1808668,2019-01-18 06:43:18 UTC,"I also observed - I do not get above error on my other server which is RHEL 6 . I checked ""ps -ef | grep mistral""found a small difference - Server which is failing does not have ""/var/run/mistral/mistral-api.pid"""
1808668,2019-01-13 01:52:30 UTC,"Also, mistral-server is eating up all the CPU. Please help - How to kill all the actions running in mistral workflow or any other solution.
 PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 14304 mistral   20   0  400836  95684   6968 R  98.3  0.3   0:20.71 mistral-server
 14206 st2       20   0  327088  54864   6428 S   2.3  0.2   0:01.73 st2notifier"
1808668,2018-12-20 02:07:28 UTC,Can anyone please suggest here.
1808668,2019-01-03 08:02:10 UTC,Could you share the contents of the custom_workflow_common.yaml please?
1808668,2019-01-16 20:15:53 UTC,"$ tail -f mistral-api.log
    fileobj = self.make_tempfile()
  File ""/opt/stackstorm/mistral/lib/python2.7/site-packages/webob/request.py"", line 1018, in make_tempfile
    return tempfile.TemporaryFile()
  File ""/usr/lib64/python2.7/tempfile.py"", line 489, in TemporaryFile
    (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags)
  File ""/usr/lib64/python2.7/tempfile.py"", line 239, in _mkstemp_inner
    fd = _os.open(file, flags, 0600)
  File ""/opt/stackstorm/mistral/lib/python2.7/site-packages/eventlet/green/os.py"", line 109, in open
    fd = __original_open__(file, flags, mode)
OSError: [Errno 2] No such file or directory: '/tmp/tmpGoLWVx'"
1808668,2019-01-13 01:49:51 UTC,version: '2.0'
1808672,2020-05-22 04:17:26 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1808678,2020-03-07 14:04:58 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1808679,2018-12-16 10:43:15 UTC,showing the latest version is being used
1808682,2018-12-16 12:00:28 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/625427"
1808682,2019-06-18 20:26:34 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.opendev.org/625426"
1808682,2019-01-31 10:25:33 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/625446"
1808682,2019-01-31 10:24:52 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/625445"
1808682,2018-12-16 11:59:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625426"
1808682,2019-01-31 10:24:42 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/625427"
1808682,2018-12-16 20:13:23 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/625446"
1808682,2018-12-16 12:00:36 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/625427"
1808682,2019-01-31 10:24:47 UTC,"Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/625444"
1808682,2018-12-16 20:13:11 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/625445"
1808682,2018-12-16 20:12:44 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/625444"
1808694,2019-11-11 14:51:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808694,2019-01-19 08:41:59 UTC,"This workaround solved it for me, my result from $ apt-cache policy xfce4-session exo-utils:"
1808694,2018-12-16 14:40:34 UTC,"This is resolved in Debian package version 0.12.2-2, currently available in Debian Testing/Unstable and Ubuntu 19.04."
1808694,2019-05-13 21:11:19 UTC,"On Ubuntu 19.04, I still see this problem."
1808694,2018-11-24 16:20:50 UTC,"I think I found out the problem, libexo-helpers package is arch independent but all .desktop files it contains use the x86-64 prefix."
1808694,2018-11-24 10:43:03 UTC,Someone found a workaround
1808694,2018-11-23 15:39:31 UTC,"dpkg -S exo-compose-mail-1
libexo-1-0:i386: /usr/lib/i386-linux-gnu/xfce4/exo-1/exo-compose-mail-1"
1808694,2018-11-23 11:51:30 UTC,"It's included in the libexo-1-0 package. In Debian and Ubuntu, the file is installed in an arch-specific location to allow 32-bit and 64-bit applications to coincide as needed."
1808694,2018-11-23 11:29:07 UTC,"All thunar sendto-mail plugin does it to call exo_execute_preferred_application, passing ""MailReader"" as category.
That helper script on my system is located at /usr/lib/xfce4/exo-1/exo-compose-mail-1, looking at bionic-updates packages[1] contents, I can't find that file. Maybe a packaging issue."
1808694,2018-11-21 10:56:02 UTC,"lsb_release -rc
Release:	18.04
Codename:	bionic"
1808694,2018-12-16 14:39:06 UTC,"This is resolved in Debian package version 0.12.2-2, currently available in Debian Testing/Unstable and Ubuntu 19.04."
1808695,2019-09-16 08:26:21 UTC,Migrated to https://github.com/widelands/widelands/issues/3374
1808696,2019-02-23 07:01:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808702,2019-08-03 20:38:08 UTC,"Hi, I'm getting the exact same problem with my thumbnailer:
https://github.com/illwieckz/crunch-thumbnailer"
1808702,2020-09-25 13:02:13 UTC,The issue is fixed in G now
1808702,2020-08-12 08:49:35 UTC,"The issue has been fixed upstream with that commit now
https://gitlab.gnome.org/GNOME/gnome-desktop/-/commit/df477a3d
the change will land in the next update (and is probably a candidate for a SRU)"
1808702,2020-08-11 09:21:28 UTC,"The ""/etc/alternatives"" problem breaks totem-video-thumbnailer, causing thumbnails of some MP4 files can't be shown. (see https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/92#note_888505)"
1808702,2019-01-20 19:17:14 UTC,@c4pp4 --- you're right. So probably the only thing we need is the bind of /etc/alternatives; upstream seems to agree it's the only way to go: https://gitlab.gnome.org/GNOME/gnome-desktop/issues/92
1808702,2018-12-19 16:29:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808702,2019-01-20 16:57:30 UTC,"@c4pp4, could be, but I think this is already in..."
1808702,2019-01-20 12:36:00 UTC,"I think the bug is related to:
https://github.com/GNOME/gnome-desktop/commit/f4dcb2f2a9f0593ca8f8da6acfe553eaf7600aea"
1808702,2018-12-20 09:31:56 UTC,"As an aside, can you hint where I can find the messages printed by the `g_warning()` in the code? I was utterly unable to find them..."
1808702,2018-12-20 09:25:05 UTC,"Indeed. So it must be something different; the problem with alternative is real, but nevertheless the aforementioned thumbnailer does not work even with the absolute path to composite..."
1808702,2018-12-20 08:55:32 UTC,the commit you mentioned is already in Ubuntu since https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/3.28.2-0ubuntu1.2
1808702,2018-12-19 09:08:38 UTC,"Ok, the problem is that the commit from:"
1808702,2018-12-16 16:46:31 UTC,Notice anyway that one of the problems was that originally the thumbnailer called
1808702,2019-01-20 17:06:19 UTC,@Romano Giannetti
1808710,2020-06-07 08:55:42 UTC,"Apparently it's a bug in libx11, which persisted for a long time but
became much more likely with an update in libxcb.
Please see the still open merge request/patch at"
1808710,2020-04-07 06:56:57 UTC,Code::Blocks is affected too. I keep losing unsaved work.
1808710,2019-11-22 02:47:39 UTC,"I have the same problem with audacious, on UbuntuStudio 18.04"
1808710,2019-05-05 05:08:52 UTC,"Looks like there's an upstream bug against Claws Mail, too:
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203"
1808710,2019-04-25 05:13:32 UTC,"Unfortunately, setting LIBGL_DRI3_DISABLE to true did not help to bypass the bug."
1808710,2018-12-16 19:09:13 UTC,Same bug for libreoffice https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161
1808710,2019-04-07 20:06:34 UTC,Related pcmanfm bug https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984
1808710,2019-10-01 22:01:35 UTC,"I have the same problem with eboard 1.1.3 on Debian Buster. The program build is quite old (2016), hence it seems that the problem is with some high-level library."
1808710,2019-01-31 22:04:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808710,2019-04-08 13:07:10 UTC,"Apparently, same bug for Audacious media player: https://redmine.audacious-media-player.org/issues/798 ."
1808711,2018-12-16 20:30:51 UTC,"Update: it seems to happen when I reboot the system by sudo reboot,then an shortcut set that bug"
1808717,2019-01-17 20:25:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808722,2019-01-28 17:01:28 UTC,"I confirm the problem, it occured to mee too."
1808725,2019-11-12 05:19:30 UTC,I cannot reproduce this. I think it was fixed in https://github.com/mixxxdj/mixxx/pull/2103
1808728,2018-12-17 08:41:56 UTC,"It's similar with BUG 1707830.
https://bugs.launchpad.net/nova/+bug/1707830"
1808729,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1808729,2019-02-04 14:46:37 UTC,This bug was fixed in the package linux - 4.19.0-12.13
1808729,2019-01-15 10:37:09 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1808729,2019-01-15 10:33:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1808729,2018-12-26 02:35:53 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-December/097402.html
1808729,2018-12-26 02:27:27 UTC,"commit 9c27369f4a1393452c17e8708c1b0beb8ac59501
Author: Mario Limonciello <email address hidden>
Date:   Tue Dec 11 08:16:14 2018 -0600"
1808729,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1808731,2019-01-18 11:07:35 UTC,"It's not only upgrade, but also neutron config update. As I said in comment #5, if we don't restart metadata proxy. The changed configuration will not take effect."
1808731,2019-02-07 23:03:51 UTC,Marking this RFE as postponed until we hear again from submitter
1808731,2019-01-18 15:39:29 UTC,In today's drivers meeting it became clear that we don't have an actual use case to justify the changed proposed in this RFE. Submitter agreed to start a thread in the mailing list to identify operators who might see a benefit to the proposed change
1808731,2019-01-17 23:30:15 UTC,"I am pretty sure that for the vast majority of users, the main concern (and assumption) is not to disrupt the data plane when the control plane is re-started. Changing this assumption is highly risky so I don't think we should change it. The upgrading of base software in a deployment's hosts should be part of on-going admin processes where hosts are vacated, upgraded and then populated again, which are beyond the scope of Neutron. But I don't think we should break the promise of Neutron not disrupting the data plane on its own."
1808731,2018-12-18 03:21:30 UTC,"As Slawek mentions other processes, like dnsmasq. I make some tests of dnsmasq process.
1. stop dhcp agent. The dnsmasq is not stopped
2. start dhcp agent. The dnsmasq process is restarted."
1808731,2018-12-19 07:59:57 UTC,Please have a look into https://github.com/openstack/neutron/blob/master/neutron/agent/metadata/driver.py#L247-L256
1808731,2018-12-19 07:34:52 UTC,"OK, I read first message one more time: Version: latest devstack on Ubuntu 16.04."
1808731,2018-12-19 07:29:16 UTC,IMO that issue seems to be related to specific infra/deployment.
1808731,2018-12-17 17:38:46 UTC,"I don't think the metadata proxy should be stopped when the l3-agent is stopped.  Currently when the agent is stopped there is no data plane disruption - namespaces, IP addresses, floating IPs, etc are all left intact, which was intentional, since destroying everything and rebuilding (for example on a restart) could take a long time.  We leave things alone and the agent will eventually converge at the end of its full-sync.  Stopping the proxy breaks that, and so something like a soft reboot of a VM is no longer possible if the l3-agent is stopped since it will fail to get metadata."
1808731,2018-12-17 13:57:50 UTC,"1. If You spawn new vm with fixed IP address only, You don't need to have working L3 agent but You still need to have working metadata service to make it boot properly."
1808731,2018-12-17 09:40:15 UTC,"I'm not sure if that is good idea because such stop of metadata proxy process will cause data plane interruption as metadata for instances will not be available. IMO this shouldn't happen at any time.
Maybe we should clearly document that when You want to upgrade metadata proxy, You should kill existing processes and then restart l3/dhcp agents."
1808731,2018-12-19 08:46:36 UTC,"okay, let me update the title"
1808731,2018-12-17 10:33:15 UTC,I would prefer to keep upgrade steps as simple as possible. I had heard some Openstack users complain about Openstack upgrade.
1808732,2018-12-17 03:49:37 UTC,"Dear Ndang,"
1808736,2020-10-02 04:17:36 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1808736,2020-10-04 00:44:12 UTC,Here's a novel idea:
1808736,2018-12-17 03:30:08 UTC,This change was made by a bot.
1808736,2020-10-02 04:17:35 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1808736,2020-10-04 07:36:26 UTC,"This bug was reported against 18.10, which is now EOL.
You can simply reopen this bug if it still happens on supported releases."
1808738,2020-11-13 14:02:04 UTC,Just ran into this issue with a massive SR-IOV deployment on Train. The amount of logs is simply ridiculous. I believe this should really be a DEBUG-level message...
1808738,2018-12-17 03:27:43 UTC,This is what my nova.conf look like
1808738,2019-03-07 14:41:53 UTC,"A follow-up to the previous post:
We were trying to wrap a Virtual Function into macvtap so that NFVs not supporting modern NICs would still get decent performance.
The root cause of our issue was that Nova (and libvirt) require the VFs to be visible to the host OS as the network devices, which wasn't the case for us. We 'sorted' the issue by loading VF driver, i40evf in our case, manually, and after this we were able to launch VM with macvtap port."
1808738,2019-03-05 22:58:01 UTC,"We have faced this bug on Openstack Pike too. Also we cannot boot VM with Neutron port of vnic_type=macvtap:
2019-03-05 12:31:30,695.695 47453 DEBUG nova.network.os_vif_util [req-173f5f59-3173-45ad-a304-8e68b504047d 1c0451fbdf0448ad81ea0a538460bf83 f1412680333743d288cc13ba57055580 - default default] No conversion for V
IF type hw_veb yet nova_to_osvif_vif /usr/lib/python2.7/dist-packages/nova/network/os_vif_util.py:494
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [req-173f5f59-3173-45ad-a304-8e68b504047d 1c0451fbdf0448ad81ea0a538460bf83 f1412680333743d288cc13ba57055580 - default default] [instance: d1c6f9d1-c5a
7-4520-93db-be53e0e19e9e] Instance failed to spawn: PciDeviceNotFoundById: PCI device 0000:19:04.7 not found
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e] Traceback (most recent call last):
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]   File ""/usr/lib/python2.7/dist-packages/nova/compute/manager.py"", line 2185, in _build_resources
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]     yield resources
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]   File ""/usr/lib/python2.7/dist-packages/nova/compute/manager.py"", line 2000, in _build_and_run_insta
nce
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]     block_device_info=block_device_info)
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]   File ""/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py"", line 2913, in spawn
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]     block_device_info=block_device_info)
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]   File ""/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py"", line 5251, in _get_guest_xml
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]     context)
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]   File ""/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py"", line 5066, in _get_guest_confi
g
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]     flavor, virt_type, self._host)
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]   File ""/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py"", line 567, in get_config
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]     inst_type, virt_type, host)
2019-03-05 12:31:30,696.696 47453 ERROR nova.compute.manager [instance: d1c6f9d1-c5a7-4520-93db-be53e0e19e9e]   File ""/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py"", line 331, in get_config_hw_veb
2019-03-0..."
1808738,2018-12-17 14:30:24 UTC,"you might be able to filter out these message by appending
nova.pci.utils=ERROR to the default set of log level and defined for this config option
https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.default_log_levels"
1808738,2018-12-17 14:46:46 UTC,"note i am triagging this as low as it does not cause an operational issue in normal opertation but
does needlessly consome log space. i would suggest we descalate the log to debug level as in manycase there is nothing the operator can do."
1808738,2019-10-16 11:21:16 UTC,Hello:
1808740,2019-02-14 06:30:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808748,2020-07-16 16:30:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal:"
1808755,2018-12-18 02:17:35 UTC,"Hi,"
1808755,2018-12-18 03:00:55 UTC,@Alexander: I am a volunteer. I attempt to maintain and publish the Ubuntu Severguide. I did not write the LXD chapter of the server guide.
1808755,2018-12-18 07:00:57 UTC,"@Doug ok, I see. Do you think someone will fix the LXD chapter to include the official documentation of LXD at readthedocs?"
1808755,2018-12-18 00:20:35 UTC,"> When searching for ""lxd documentation"" on duckduckgo.com,
> the readthedocs site of LXD (which is the official LXD
> documentation website)
"
1808755,2018-12-18 01:12:25 UTC,"> It is? Says who? It doesn't appear to be a Canonical owned site. Myself, I've never heard of it.
"
1808768,2018-12-17 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808768,2019-01-11 14:43:27 UTC,"This bug report was made for tracking changes on how snaps are being produced. Unfortunately this is not reflecting well with Launchpad because the required changes had to be made in git trees which not directly map to a source package in Launchpad's mind.
I have applied the changes to both makefiles (xenial and bionic) so the next snaps being done should be fixed. But again there will not be an automatic state change on this bug report."
1808775,2019-01-24 19:41:33 UTC,See https://help.gnome.org/users/evolution/stable/offline.html for how to debug the problem.
1808775,2019-04-30 07:54:17 UTC,Could you get the debug information from the url mentioned in the previous comment and perhaps report it upstream as well on https://gitlab.gnome.org/GNOME/evolution/issues/ ?
1808775,2019-06-30 04:17:25 UTC,[Expired for evolution (Ubuntu) because there has been no activity for 60 days.]
1808781,2018-12-17 10:00:43 UTC,vrouter agent gcore
1808781,2018-12-17 10:02:33 UTC,"docker logs:
10:19:45 | [root@overcloudn0f-comp-7 ~]# docker logs contrail_vrouter_agent
10:19:45 | INFO: terminating process 187
10:19:45 | /agent-functions.sh: line 640:   187 Killed                  $@
10:19:45 | INFO: agent started in kernel mode
10:19:45 | INFO: vhost0 is already up
10:19:45 | INFO: Kernel version does not support the driver required for vrouter to vrouter encryption
10:19:45 | INFO: Physical interface: vlan301, mac=68:05:ca:41:ff:d0, pci=0000:00:00.0
10:19:45 | INFO: vhost0 cidr 100.66.144.33/21, gateway 100.66.144.1
10:19:45 | INFO: Preparing /etc/contrail/contrail-vrouter-agent.conf
10:19:45 | INFO: /etc/contrail/contrail-vrouter-agent.conf
10:19:45 | [CONTROL-NODE]
10:19:45 | servers=100.66.144.24:5269 100.66.144.23:5269 100.66.144.19:5269
10:19:45 | [DEFAULT]
10:19:45 | collectors=100.66.168.24:8086 100.66.168.22:8086 100.66.168.16:8086
10:19:45 | log_file=/var/log/contrail/contrail-vrouter-agent.log
10:19:45 | log_level=SYS_NOTICE
10:19:45 | log_local=1
10:19:45 | xmpp_dns_auth_enable=False
10:19:45 | xmpp_auth_enable=False
10:19:45 | physical_interface_mac = 68:05:ca:41:ff:d0
10:19:45 | tsn_servers = []
10:19:45 | [SANDESH]
10:19:45 | introspect_ssl_enable=False
10:19:45 | sandesh_ssl_enable=False
10:19:45 | [NETWORKS]
10:19:45 | control_network_ip=100.66.144.33
10:19:45 | [DNS]
10:19:45 | servers=100.66.144.24:53 100.66.144.23:53 100.66.144.19:53
10:19:45 | [METADATA]
10:19:45 | metadata_proxy_secret=secret
10:19:45 | [VIRTUAL-HOST-INTERFACE]
10:19:45 | name=vhost0
10:19:45 | ip=100.66.144.33/21
10:19:45 | physical_interface=vlan301
10:19:45 | gateway=100.66.144.1
10:19:45 | compute_node_address=100.66.144.33
10:19:45 | [SERVICE-INSTANCE]
10:19:45 | netns_command=/usr/bin/opencontrail-vrouter-netns
10:19:45 | docker_command=/usr/bin/opencontrail-vrouter-docker
10:19:45 | [HYPERVISOR]
10:19:45 | type = kvm
10:19:45 | [FLOWS]
10:19:45 | fabric_snat_hash_table_size = 4096
10:19:45 | [SESSION]
10:19:45 | slo_destination = collector
10:19:45 | sample_destination = collector
10:19:45 | INFO: Kernel version does not support vrouter to vrouter encryption - Not adding decrypt0 to vrouter
10:19:45 | Config file </etc/contrail/contrail-vrouter-agent.conf> parsing completed.
10:19:45 | log4cplus:ERROR No appenders could be found for logger (SANDESH).
10:19:45 | log4cplus:ERROR Please initialize the log4cplus system properly.
10:19:45 | INFO: terminating process 187
10:19:45 | /agent-functions.sh: line 640:   187 Killed                  $@
10:19:45 | INFO: agent started in kernel mode
10:19:45 | INFO: vhost0 is already up
10:19:45 | INFO: Kernel version does not support the driver required for vrouter to vrouter encryption
10:19:45 | INFO: Physical interface: vlan301, mac=68:05:ca:41:ff:d0, pci=0000:00:00.0
10:19:45 | INFO: vhost0 cidr 100.66.144.33/21, gateway 100.66.144.1
10:19:45 | INFO: Preparing /etc/contrail/contrail-vrouter-agent.conf
10:19:45 | INFO: /etc/contrail/contrail-vrouter-agent.conf
10:19:45 | [CONTROL-NODE]
10:19:45 | servers=100.66.144.24:5269 100.66.144.23:5269 100.66.144.19:5269
10:19:45 | [DEFAULT]
10:19:45 | collectors=100.66.168.24:8086 100.66.168.22:8086 100.66.168.16:8086
10:19:45 | ..."
1808785,2018-12-18 15:12:23 UTC,On a clean install of 18.04 this works as expected.
1808786,2018-12-17 10:30:04 UTC,This change was made by a bot.
1808800,2020-08-24 18:20:26 UTC,Fixed many moons ago
1808801,2019-02-25 19:15:45 UTC,"I have the same issue in the current 2.2 release, however not with any master build I've done locally."
1808801,2018-12-17 20:31:28 UTC,I cannot confirm this with Ubuntu Trusty.
1808801,2019-02-25 19:19:47 UTC,"I'm on macOS 10.14.3, running 2.2-r6659"
1808802,2019-05-16 18:22:33 UTC,"Q: Hmm, no help is being received here?
A: Since there's been nothing since I reported this I've now given up with Livepatch and uninstalled it. If nobody else has the problem I'd suggest closing the bug."
1808802,2019-06-26 04:53:51 UTC,well i have the same thing...been struggling with it
1808802,2019-10-24 17:47:55 UTC,"Canonical livepatch client is saying the kernel is too old to patch. User seems unable to upgrade it. There are many possible reasons for this. Unfortunate, but this is also not a Canonical livepatch client bug."
1808802,2019-12-24 04:17:54 UTC,[Expired for Canonical Live Patch Client because there has been no activity for 60 days.]
1808802,2019-05-16 07:10:24 UTC,"Hmm, no help is being received here?"
1808809,2018-12-18 11:27:54 UTC,related: LP:1309089
1808809,2018-12-20 17:35:53 UTC,I cannot confirm this on Ubuntu Trusty using the recent 2.2.0.
1808809,2020-08-24 02:37:43 UTC,Defaults seem important especially for Broadcasting: lp:1818054
1808812,2019-05-08 12:13:08 UTC,https://github.com/snapcore/snapcraft/pull/2560
1808814,2020-04-06 22:39:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717873"
1808814,2020-04-14 14:46:05 UTC,"Reviewed:  https://review.opendev.org/717873
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=30f821c62416aa79d98c0c79b81bb981eb49155f
Submitter: Zuul
Branch:    master"
1808819,2019-01-08 15:33:13 UTC,"Reviewed:  https://review.openstack.org/625616
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=bf3e123e1f7c09c64beecf0ff092c7e6b84590b4
Submitter: Zuul
Branch:    master"
1808819,2018-12-17 14:57:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625616"
1808821,2019-08-13 11:36:37 UTC,This isn't specific to the arch triplet as I surmised in my original post. I've reproduced it with a layout of:
1808821,2018-12-18 14:09:08 UTC,I spent some time looking at this and I cannot reproduce it on 2.36.3 on openSUSE Tumbleweed. I will add a test that examines the mount changes across the layout mount profile evolution to see if we are doing something wrong there.
1808821,2018-12-18 14:27:27 UTC,The reporter cannot reproduce this issue either. According to snap changes there was a core refresh in last night so whatever (perhaps broken) state was present in the mount profiles or mount namespace was discarded.
1808821,2019-02-14 13:54:03 UTC,"I'm resuming investigation, perhaps merging this issue with https://forum.snapcraft.io/t/snapd-2-37-1-refresh-broke-layouts-snap-remove-install/9803"
1808821,2019-08-14 13:08:25 UTC,This is now fixed in the following pull request https://github.com/snapcore/snapd/pull/7254
1808821,2019-08-13 12:56:35 UTC,I've debugged the issue now. For the sake of leaving a trace:
1808821,2019-08-14 12:17:16 UTC,I've fixed this locally. I need some extra time for unit tests but it should be going into master today.
1808824,2018-12-20 04:46:47 UTC,"https://youtu.be/Vpi59ptOiyc
Here is a video demonstrating the main issue. This does not show any lag but, it does show how VM doesn't capture the mouse correctly."
1808830,2018-12-18 16:22:03 UTC,"For reference, the conversation which precipitated this bug and some triage was done in the IRC channel. See http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2018-12-17.log.html#t2018-12-17T14:23:23"
1808831,2018-12-17 16:01:34 UTC,"Review in progress for https://review.opencontrail.org/48243
Submitter: Jarek Lukow (<email address hidden>)"
1808831,2018-12-20 13:56:16 UTC,"Reviewed:  https://review.opencontrail.org/48243
Committed: http://github.com/Juniper/contrail-infra/commit/e862ca543eaab5f0656ff6a7e5bac234fcedc889
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    production"
1808833,2019-05-16 15:06:36 UTC,The issue has not been reported with > 2.4.7
1808839,2018-12-17 17:04:50 UTC,bundle: https://pastebin.canonical.com/p/Px6B5n7Ybj/
1808839,2019-05-14 13:41:53 UTC,"Marking as critical, though the work to do might just be to validate that the latest charms have fixed the race."
1808839,2019-05-30 11:34:47 UTC,@Jason have you seen this again since the 19.04 charms release?
1808839,2019-07-30 04:17:19 UTC,[Expired for OpenStack nova-cloud-controller charm because there has been no activity for 60 days.]
1808842,2018-12-17 17:30:07 UTC,This change was made by a bot.
1808842,2020-01-09 16:12:05 UTC,Supporting it via module is not possible as the changes touch core parts of the kernel. It's unfortunately not able to support it out of the box but there's no good way yet except asking users to change the setting to AHCI in BIOS.
1808842,2020-04-09 09:32:52 UTC,"Hi,"
1808842,2021-01-28 08:47:02 UTC,Hello
1808844,2019-05-03 22:05:32 UTC,"Change abandoned by Athlan-Guyot sofer (<email address hidden>) on branch: master
Review: https://review.opendev.org/625676
Reason: in favor for https://review.opendev.org/#/c/654407/1"
1808844,2019-04-22 08:32:23 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/654407"
1808844,2019-01-14 14:13:08 UTC,"So, according to https://tickets.puppetlabs.com/browse/PUP-9366 we can disable this by using manage_internal_file_permissions=false in puppet configuration[1]"
1808844,2020-08-06 21:53:40 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/654407
Reason: This review is > 90 days without comment, and failed Zuul the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results. For more details check policy https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1808844,2018-12-17 17:45:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625676"
1808849,2018-12-17 19:48:09 UTC,App.open() is not working either.
1808849,2018-12-18 07:30:29 UTC,please paste the sample code
1808849,2018-12-18 15:48:30 UTC,"# TEST CASE 1
from time import ctime"
1808849,2018-12-18 16:34:33 UTC,Thanks for the details - very helpful :-)
1808849,2018-12-18 17:42:57 UTC,Just noticed that there is also a related (I assume) response problem with closeApp.
1808849,2018-12-20 14:18:58 UTC,The main problems with standard apps like TextEdit (not having a space in name - to be fixed) should be fixed now.
1808849,2018-12-20 14:22:00 UTC,BTW: about timing: I never saw elapsed times beyond 2 seconds for a not running app.
1808849,2018-12-20 14:22:44 UTC,... and the problem with App.focus() is fixed.
1808856,2018-12-31 21:08:13 UTC,"Can confirm this behavior for SCLENDS, 3.1.7."
1808857,2019-10-26 05:38:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808860,2019-11-19 04:17:39 UTC,[Expired for curtin because there has been no activity for 60 days.]
1808860,2019-01-08 21:02:00 UTC,I've confirmed this is happening however I believe this is a bug in Curtin instead of MAAS. MAAS is telling Curtin to install linux-signed-generic and not the AWS kernel.
1808860,2019-09-19 14:50:05 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1808860,2019-01-09 00:18:10 UTC,"Curtin does not specific which kernel to install.  Rather MAAS does, and if it doesn't specify a kernel, we use linux-generic (or linux-signed-generic."
1808862,2019-05-08 16:07:43 UTC,Works again in disco!
1808864,2020-04-16 02:06:49 UTC,Would you mind comparing this to the new version at
1808864,2020-04-16 04:04:30 UTC,"Hello,"
1808865,2018-12-19 08:10:46 UTC,"Bonjour,"
1808865,2018-12-18 09:04:02 UTC,"Bonjour,"
1808868,2019-09-25 14:23:46 UTC,"Reviewed:  https://review.opendev.org/681866
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=3a281b9bc62a1b8b0f1468bc641105a5662f8ecd
Submitter: Zuul
Branch:    master"
1808868,2019-09-12 18:09:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/681866"
1808868,2019-10-02 10:05:56 UTC,This issue was fixed in the openstack/glance 19.0.0.0rc1 release candidate.
1808873,2018-12-20 13:10:22 UTC,"Sure,
I tried that and it worked fine in both configuration."
1808873,2018-12-21 01:52:09 UTC,Incomplete for now. The bug will automatically close after 60 days if there are no further comments.
1808873,2018-12-22 14:58:50 UTC,"Ok, I'm back :)"
1808873,2019-04-06 16:42:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808873,2019-04-06 16:43:41 UTC,"Same bug after upgrading to 18.10, but with completely different graphics card (nvidia)."
1808873,2019-04-06 17:13:46 UTC,"Observation: In /var/log/syslog, after upgrading to 18.10 these critical messages appear for the first time:
Apr  4 01:12:02 hmm-desktop gnome-session[3467]: gnome-session-binary[3467]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Fehler beim Aufruf von StartServiceByName für org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited
: Process org.gnome.ScreenSaver exited with status 1
Apr  4 01:12:02 hmm-desktop gnome-session-binary[3467]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Fehler beim Aufruf von StartServiceByName für org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.S
creenSaver exited with status 1"
1808873,2019-04-06 17:34:07 UTC,Some context from these errors.
1808873,2019-08-05 03:38:44 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1808873,2018-12-18 01:53:48 UTC,Can you please run this command:
1808873,2018-12-18 07:34:12 UTC,Voila
1808873,2018-12-18 07:49:53 UTC,Can you please test to see if this issue is related to just one of the outputs? Try the DVI monitor and HDMI projector separately. Any difference?
1808874,2019-04-09 14:33:32 UTC,"From what I remember, nvidia-detector was never meant to detect anything other than obsolete nvidia drivers. It is, or was, only used by the nvidia-common debconf script."
1808874,2019-04-09 14:38:56 UTC,"note: I think, in your case, the output of nvidia-detector is correct, since you don't seem to have an obsolete driver installed. Also, the list of obsolete drivers hasn't been updated in a long time (LP: #1682291), and we have managed driver migrations using transitional packages."
1808874,2019-04-08 20:47:12 UTC,Its been a couple of months is anything happening with this?
1808874,2018-12-18 14:41:52 UTC,"Not a release blocker, so marking as not fixing.  tseliot has said he would work on this though."
1808874,2019-05-18 13:00:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808876,2018-12-17 22:41:38 UTC,Did rename the space from special-test to default and rebootstrap and tried and same issue. Without a request to be on a space no network device is added by default.
1808876,2018-12-19 00:49:37 UTC,"To be clear, the names `default` and `maas` are not significant when assigned to spaces in MAAS. If you have a network by those names *defined in libvirt*, MAAS will attempt to attach to them (in the absence of better information about which bridges are available and what networks they represent)."
1808876,2019-09-19 12:07:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1808880,2019-06-05 16:48:17 UTC,"Marking as invalid as we no longer use Ubuntu Reviews, we've switched to ODRS."
1808880,2019-02-16 14:19:44 UTC,You're right: in Bionic I do not see the 'Write a Review' button for snap packages.
1808880,2019-01-08 16:48:03 UTC,"> I have this message each time i try to write a review for a snap package
"
1808880,2019-01-08 13:51:44 UTC,This will be fixed by the switch from Ubuntu Reviews to ODRS.
1808880,2019-01-02 18:52:20 UTC,I have this message each time i try to write a review for a snap package
1808880,2019-01-02 18:45:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808880,2018-12-18 19:11:52 UTC,"Yes, tried to write feedback and receive message constantly."
1808880,2018-12-18 08:48:42 UTC,"Thank you for your bug report. What did you do exactly, did you try to write a review? Do you get the issue every time?
Could you add your journalctl log from around the time of the issue to the bug?"
1808881,2018-12-18 02:06:18 UTC,Could you please try live booting (no need to install) Ubuntu 18.10 and tell us if the newer version of libinput there is any better?
1808881,2018-12-18 20:33:12 UTC,"Hi, with 18.10 (live session) the behaviour is the same. I opened: https://gitlab.freedesktop.org/libinput/libinput/issues/199."
1808881,2018-12-18 20:38:18 UTC,Don't know if this is related:
1808884,2018-12-18 01:10:39 UTC,"FWIW, the version of the compiler gcc-arm-none-eabi-7-2017-q4-major also exhibits the issue.  I am not able to go back further because the program depends on some compiler features added in GCC7."
1808884,2018-12-29 04:05:20 UTC,I believe I have a test case for this issue.  I've run it through the three releases from 2017 and on the one release in 2018.  All of them produce the same erroneous code.
1808884,2018-12-29 04:29:26 UTC,The attached archive has the pre-processed compiler output from the source file to eliminate a need for headers.  It can be converted into a ELF file with the build.sh script.  The linker script is necessary to generate the broken output.  The output of my build is included as well.
1808886,2018-12-27 19:18:32 UTC,Still actual for me
1808886,2019-02-04 05:51:37 UTC,"Still actual for me.
Please, can someone answer on the bug?"
1808886,2019-02-26 10:52:59 UTC,Still having this bug..
1808886,2019-09-20 04:44:41 UTC,"wifi works after seeing these messages.
dmesg:
[   25.581538] iwlwifi 0000:04:00.0: regular scan timed out
[   25.581919] iwlwifi 0000:04:00.0: Microcode SW error detected.  Restarting 0x2000000.
[   25.582132] iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
[   25.582136] iwlwifi 0000:04:00.0: Status: 0x00000080, count: 6
[   25.582139] iwlwifi 0000:04:00.0: Loaded firmware version: 36.77d01142.0
[   25.582144] iwlwifi 0000:04:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
[   25.582147] iwlwifi 0000:04:00.0: 0x000006F7 | trm_hw_status0
[   25.582149] iwlwifi 0000:04:00.0: 0x00000000 | trm_hw_status1
[   25.582152] iwlwifi 0000:04:00.0: 0x00024200 | branchlink2
[   25.582155] iwlwifi 0000:04:00.0: 0x00039872 | interruptlink1
[   25.582157] iwlwifi 0000:04:00.0: 0x00004B86 | interruptlink2
[   25.582160] iwlwifi 0000:04:00.0: 0x00000000 | data1
[   25.582162] iwlwifi 0000:04:00.0: 0x00000080 | data2
[   25.582165] iwlwifi 0000:04:00.0: 0x07830000 | data3
[   25.582168] iwlwifi 0000:04:00.0: 0x1E418F71 | beacon time
[   25.582170] iwlwifi 0000:04:00.0: 0x6FBD1092 | tsf low
[   25.582173] iwlwifi 0000:04:00.0: 0x000002B6 | tsf hi
[   25.582176] iwlwifi 0000:04:00.0: 0x00000000 | time gp1
[   25.582178] iwlwifi 0000:04:00.0: 0x00BD9200 | time gp2
[   25.582181] iwlwifi 0000:04:00.0: 0x00000001 | uCode revision type
[   25.582184] iwlwifi 0000:04:00.0: 0x00000024 | uCode version major
[   25.582186] iwlwifi 0000:04:00.0: 0x77D01142 | uCode version minor
[   25.582189] iwlwifi 0000:04:00.0: 0x00000201 | hw version
[   25.582191] iwlwifi 0000:04:00.0: 0x00C89008 | board version
[   25.582194] iwlwifi 0000:04:00.0: 0x0000001C | hcmd
[   25.582197] iwlwifi 0000:04:00.0: 0x82F62000 | isr0
[   25.582199] iwlwifi 0000:04:00.0: 0x01000000 | isr1
[   25.582202] iwlwifi 0000:04:00.0: 0x08001802 | isr2
[   25.582204] iwlwifi 0000:04:00.0: 0x00400084 | isr3
[   25.582206] iwlwifi 0000:04:00.0: 0x00000000 | isr4
[   25.582209] iwlwifi 0000:04:00.0: 0x0B16001C | last cmd Id
[   25.582212] iwlwifi 0000:04:00.0: 0x00000000 | wait_event
[   25.582214] iwlwifi 0000:04:00.0: 0x00000080 | l2p_control
[   25.582217] iwlwifi 0000:04:00.0: 0x00003C20 | l2p_duration
[   25.582219] iwlwifi 0000:04:00.0: 0x0000003F | l2p_mhvalid
[   25.582222] iwlwifi 0000:04:00.0: 0x000000CE | l2p_addr_match
[   25.582225] iwlwifi 0000:04:00.0: 0x0000000D | lmpm_pmg_sel
[   25.582227] iwlwifi 0000:04:00.0: 0x19071249 | timestamp
[   25.582230] iwlwifi 0000:04:00.0: 0x0000A0B0 | flow_handler
[   25.582398] iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
[   25.582401] iwlwifi 0000:04:00.0: Status: 0x00000080, count: 7
[   25.582405] iwlwifi 0000:04:00.0: 0x00000070 | NMI_INTERRUPT_LMAC_FATAL
[   25.582407] iwlwifi 0000:04:00.0: 0x00000000 | umac branchlink1
[   25.582410] iwlwifi 0000:04:00.0: 0xC0086B38 | umac branchlink2
[   25.582412] iwlwifi 0000:04:00.0: 0xC008D91C | umac interruptlink1
[   25.582415] iwlwifi 0000:04:00.0: 0xC0083D08 | umac interruptlink2
[   25.582417] iwlwifi 0000:04:00.0: 0x00000800 | umac data1
[   25.582420] iwlwifi 0000:04:00.0: 0xC0083D08 | umac data2
[   25.582422] iwlwifi 0000:04:00.0: 0xDEADBEEF | umac data3
[   25.582425] iwlwifi 0000:04:00.0: 0x00000024 ..."
1808886,2019-03-20 06:24:00 UTC,I think it's the same one as LP: #1808389.
1808886,2019-04-05 02:27:25 UTC,"Updated firmware for bug #1808389 is in -proposed, please check whether or not this firmware solves the issue. Thanks!"
1808886,2018-12-22 15:50:58 UTC,shat about this bug?
1808886,2019-03-19 20:58:11 UTC,"I still have this bug.
Can someone say me, what can i do to fix him? I wanna use ubuntu on my notebook"
1808886,2018-12-18 17:28:56 UTC,apport information
1808886,2018-12-18 17:28:47 UTC,apport information
1808886,2018-12-18 17:28:53 UTC,apport information
1808886,2018-12-18 01:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1808886,2018-12-18 17:28:39 UTC,apport information
1808886,2018-12-18 17:28:55 UTC,apport information
1808886,2018-12-18 17:28:40 UTC,apport information
1808886,2018-12-18 17:28:41 UTC,apport information
1808886,2018-12-18 17:28:42 UTC,apport information
1808886,2018-12-18 17:28:45 UTC,apport information
1808886,2018-12-18 17:28:48 UTC,apport information
1808886,2018-12-18 17:28:52 UTC,apport information
1808886,2018-12-18 17:28:50 UTC,apport information
1808886,2018-12-18 17:28:51 UTC,apport information
1808886,2018-12-18 17:28:44 UTC,apport information
1808890,2018-12-18 02:41:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625763"
1808891,2018-12-18 01:29:57 UTC,"Here's the equivalent Debian bug.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700681"
1808894,2018-12-18 02:46:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625764"
1808895,2018-12-18 02:50:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625765"
1808896,2019-02-07 22:44:49 UTC,"I solved it by placing the requirements.txt file into the directory specified in ""source"""
1808897,2018-12-18 10:33:24 UTC,"Change abandoned by Mark Goddard (<email address hidden>) on branch: master
Review: https://review.openstack.org/625817
Reason: Already proposed https://review.openstack.org/#/c/621948/2. Please check."
1808897,2018-12-18 06:50:36 UTC,"https://review.openstack.org/#/c/621948/   already pushed, this is not impacting any functionality, so filing as not necessary."
1808897,2018-12-18 02:07:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625753"
1808897,2018-12-18 07:15:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625817"
1808897,2018-12-18 06:49:37 UTC,"Change abandoned by Surya Prakash (spsurya) (<email address hidden>) on branch: master
Review: https://review.openstack.org/625753
Reason: https://review.openstack.org/#/c/621948/"
1808902,2018-12-18 04:06:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625781"
1808902,2019-11-13 23:44:07 UTC,"Reviewed:  https://review.opendev.org/625781
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=70e5c214f06729eda06df4201349c135bec88107
Submitter: Zuul
Branch:    master"
1808905,2018-12-18 03:37:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625778"
1808913,2018-12-18 07:30:27 UTC,"Oh well, I just use 301 to forward from http to https. I've updated the code, but never rolled a new release. Looks like it is about time."
1808913,2018-12-18 12:21:53 UTC,"Oh hey! I actually found your mercurial repo and built from source so everything's copacetic on my end. As an aside with the dev build I needed to xsetroot -solid black in my .bashrc because subtle apparently wasn't setting any color(?) and I got ghosting issues when I moved windows. I signed up on your site as alessa, was hoping the bug tracker and forum there still work so I could dig in more and mention the xsetroot thing. Having fun using subtle to learn ruby and shake the rust off my C skills from college years back. It's very enjoyable to use!"
1808913,2018-12-18 13:44:56 UTC,"Yeah, I already activated your account, so it is probably better to move any discussion to IRC or forum, but some quick answers:"
1808920,2018-12-18 06:56:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625810"
1808923,2018-12-18 07:03:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625815"
1808927,2018-12-28 17:13:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808927,2018-12-28 17:26:36 UTC,"same problem on ubuntu 18.04.1 LTS and firefox 64.0+build3-0ubuntu0.18.04.1
tested with Netflix and Amazon Prime Video, I can see wallpaper and desktop icons under the videos with both firefox windowed or in fullscreen mode"
1808928,2019-02-19 10:56:40 UTC,"Sorry, because of log time, VM logs were removed. Journalctl for libvirtd is remain.. It was like that.
018-12-17 17:01:50.990+0000: 43198: error : qemuMonitorIORead:606 : Unable to read from monitor: Connection reset by peer
Dec 17 20:01:50 vm-kvm09 libvirtd[43198]: 2018-12-17 17:01:50.991+0000: 43198: error : qemuProcessReportLogError:1935 : internal error: qemu unexpectedly closed the monitor: .guest_agent.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio
Dec 17 20:01:51 vm-kvm09 libvirtd[43198]: 2018-12-17T17:01:50.984315Z qemu-kvm: -drive file=/var/lib/libvirt/images/exo1-jb-h01-2.qcow2,format=qcow2,if=none,id=drive-virtio-disk1,cache=none: Bitmap extra data is not supported
Dec 17 20:02:02 vm-kvm09 libvirtd[43198]: 2018-12-17 17:02:02.652+0000: 43203: warning : virQEMUCapsInit:923 : Failed to get host CPU cache info
Dec 17 20:02:02 vm-kvm09 libvirtd[43198]: 2018-12-17 17:02:02.668+0000: 68990: warning : virQEMUCapsInit:923 : Failed to get host CPU cache info
Dec 17 20:02:02 vm-kvm09 libvirtd[43198]: 2018-12-17 17:02:02.683+0000: 17099: warning : virQEMUCapsInit:923 : Failed to get host CPU cache info
Dec 17 20:09:58 vm-kvm09 libvirtd[43198]: 2018-12-17 17:09:58.700+0000: 68889: warning : virQEMUCapsInit:923 : Failed to get host CPU cache info
Dec 17 20:09:58 vm-kvm09 libvirtd[43198]: 2018-12-17 17:09:58.717+0000: 43200: warning : virQEMUCapsInit:923 : Failed to get host CPU cache info
Dec 17 20:09:58 vm-kvm09 libvirtd[43198]: 2018-12-17 17:09:58.732+0000: 43202: warning : virQEMUCapsInit:923 : Failed to get host CPU cache info
Dec 17 20:09:59 vm-kvm09 libvirtd[43198]: 2018-12-17 17:09:59.144+0000: 43198: error : qemuMonitorIORead:606 : Unable to read from monitor: Connection reset by peer
Dec 17 20:09:59 vm-kvm09 libvirtd[43198]: 2018-12-17 17:09:59.145+0000: 43198: error : qemuProcessReportLogError:1935 : internal error: qemu unexpectedly closed the monitor: 2018-12-17T17:09:59.132340Z qemu-kvm: -drive file=/var/lib/libvirt/images/exo1-jb-h01-2.qcow2,f..."
1808928,2019-02-12 01:16:07 UTC,"Hi, bitmap extensions have a field that allows us to attach extra/arbitrary data to them. It is not currently used by QEMU. If this field is set, it means something corrupted your qcow2."
1808928,2019-02-18 19:56:22 UTC,"OK, I think it is a bug that you cannot at least repair the image, though the cause of corruption is still unknown to me. Do you have libvirt/QEMU logs from when then VM was shut down, before it wouldn't boot properly again?"
1808928,2019-02-12 12:49:04 UTC,"as far as i know nothing happened. it had worked normally while instance was running. For a reason, instance is shutdown, then it never open again. i have some backups, i tried to return previous backups. But they also gave same error. Thanks to replication i could get it back. i copied image from replication site..."
1808928,2019-12-23 20:45:54 UTC,"For now, QEMU cannot accept images with extra bitmap data, because QEMU isn't aware of the semantics of those fields, so we cannot even allow the image to load, just in case."
1808932,2020-03-07 10:54:28 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1808944,2018-12-18 08:53:32 UTC,What to do?
1808944,2018-12-19 02:18:59 UTC,"Sounds almost like bug 1514243, but the function name has changed."
1808951,2019-09-27 09:05:38 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1808951,2019-07-03 18:20:27 UTC,This bug was fixed in the package nova - 2:19.0.0-0ubuntu2.3
1808951,2019-07-03 18:11:00 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1808951,2019-07-03 09:42:00 UTC,To complement Sahid's testing I also ran a tempest smoke against a SSL enabled Disco cloud:
1808951,2019-07-03 09:19:10 UTC,"$ dpkg -s nova-compute | grep -i version
Version: 2:19.0.0-0ubuntu2.3"
1808951,2019-07-02 16:18:25 UTC,In comment #20 my verification is not right I should have deployed with SSL enabled.
1808951,2019-07-01 20:02:29 UTC,Subscribed field-medium as we're deploying a cloud with this.
1808951,2019-06-27 12:49:58 UTC,"disco-proposed tested, please consider the results:"
1808951,2019-06-25 21:55:26 UTC,"Hi Corey, I don't have access to a Disco cloud to test. Can we still get this fix in stein? This is a blocker for a customer deployment."
1808951,2019-06-21 13:11:56 UTC,"Przemyslaw/David, this also needs to get verified on disco before it can land in stein UCA. Any chance you can test that as well? If not please let us know. Thanks!"
1808951,2019-06-19 18:04:42 UTC,Unsubscribing field-critical
1808951,2018-12-21 17:16:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/626952"
1808951,2019-05-04 22:49:45 UTC,"Reviewed:  https://review.opendev.org/647310
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d0f540742efc1004b4d2c64814dcc6f7b9f0ccf6
Submitter: Zuul
Branch:    stable/stein"
1808951,2019-01-25 21:00:06 UTC,Adding tripleo because this is affecting our fedora28 containers when deployed via an undercloud with ssl enabled.
1808951,2019-03-22 22:31:23 UTC,"Reviewed:  https://review.openstack.org/626952
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c5e2b0e9fac985294a949852bb8c83d4ed77e04
Submitter: Zuul
Branch:    master"
1808951,2019-03-25 08:22:46 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/647310"
1808951,2019-04-25 19:12:37 UTC,"For the Ubuntu SRU, a new version of the package has been uploaded to eoan and disco, and is awaiting review by the SRU team in disco [1]."
1808951,2019-04-26 15:20:56 UTC,This bug was fixed in the package nova - 2:19.0.0-0ubuntu3
1808951,2019-06-19 17:50:21 UTC,I subscribed field-critical to this bug as this is affecting a customer deployment.
1808951,2019-06-19 20:18:43 UTC,"Hi, I have also verified that the fix works on bionic-stein, with -proposed packages."
1808951,2019-05-09 12:04:17 UTC,"Hello yatin, or anyone else affected,"
1808951,2019-05-16 17:10:57 UTC,"Hello yatin, or anyone else affected,"
1808951,2019-05-17 20:42:05 UTC,I can confirm the python3-nova and associated dependencies from cloud-archive:stein-proposed have stopped the errors like these ones form the original report:
1808951,2019-05-31 13:55:15 UTC,"Hi Jamon, If you've tested the packages in -proposed pockets that fix this issue, please can you tag this bug appropriately (ie. verification-done-disco, etc)."
1808951,2019-06-06 06:24:56 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1808951,2019-06-17 20:05:04 UTC,I confirm the package in stein-proposed fixes the issue.
1808951,2019-05-08 19:28:35 UTC,"Hello yatin, or anyone else affected,"
1808959,2019-09-20 10:17:22 UTC,In absense of test systems to check this I'm marking this as incomplete. If the reporter can confirm the issue is fixed it would help us with the bug tracking.
1808959,2019-06-06 16:47:26 UTC,"Just tested again in a fully up-to-date Fedora 29 VM, and the chromium snap from the candidate channel now starts and works as expected."
1808959,2019-03-15 14:22:39 UTC,"Fully up-to-date Fedora 29 VM, the chromium snap still fails to launch with the same error."
1808959,2019-03-30 17:44:33 UTC,"I just found the issue with our solus snapd package, I had to build snap-exec static and after this chromium snap starts again."
1808959,2019-02-12 09:20:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808959,2018-12-19 09:37:24 UTC,It looks like this might be similar to what's being observed on Fedora 29 (https://forum.snapcraft.io/t/error-lunching-gitkraken/8524/).
1808959,2018-12-19 10:05:43 UTC,@Olivier
1808959,2019-02-18 08:37:58 UTC,I am experiencing this same issue on Fedora 29 after installing the Krita snap. It is using core18 also.
1808959,2019-02-12 09:21:43 UTC,"FYI, this is still an issue."
1808959,2019-01-09 09:03:23 UTC,The core18 version of the chromium snap is the only supported and maintained version now.
1808959,2019-01-07 11:32:11 UTC,"I'm also trying to run the Chromium snap on Solus, I get the same error."
1808959,2018-12-19 10:28:22 UTC,Thanks for the confirmation.
1808965,2019-01-04 20:38:14 UTC,"Reviewed:  https://review.openstack.org/625877
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=1baecc6b5b82df1b822ecda038e52e2c4d6052ab
Submitter: Zuul
Branch:    stable/queens"
1808965,2019-01-08 07:37:08 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/629100"
1808965,2019-01-09 14:59:16 UTC,"Reviewed:  https://review.openstack.org/629100
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b6b01d5c247e6d6ed4a128a380114a393dcd2e29
Submitter: Zuul
Branch:    stable/pike"
1808965,2019-02-15 15:13:56 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.3.0 release.
1808965,2019-03-04 13:30:02 UTC,Is this going to be backported to Queens?
1808965,2019-03-05 07:54:28 UTC,It got already merged in pike and queens too: https://review.openstack.org/#/c/625877/ (queens) and https://review.openstack.org/#/c/629100/ (pike)
1808965,2019-05-14 14:39:02 UTC,This issue was fixed in the openstack/tripleo-heat-templates 7.0.18 release.
1808965,2018-12-18 10:57:16 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/625877"
1808970,2018-12-18 12:42:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/625901"
1808972,2018-12-18 16:38:38 UTC,I believe that system fonts in Eeschema is under consideration for v6 at the moment.
1808972,2019-01-14 22:35:25 UTC,"For the love of God, please solve this ;-)"
1808978,2019-12-09 09:41:43 UTC,Closing this as this was fixed by Ian's netlink based device monitor.
1808979,2019-09-23 09:39:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808979,2019-06-12 09:18:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808979,2019-06-12 09:49:48 UTC,"The issue is in python-defaults, maybe on systemd where the default python was changed"
1808989,2018-12-20 10:29:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1808989,2018-12-20 13:38:40 UTC,"In particular, following 4 issues are related to to tightvnc viewer:"
1808994,2018-12-27 16:10:07 UTC,"You can do that with custom paste only pads right now.
(It might be something where a script could help a lot.)"
1808998,2020-05-14 19:54:50 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/728274"
1808998,2019-02-22 13:50:40 UTC,This is quite true; as a workaround the rmq charm now sets a TTL for messages in notification queues but ideally we'd just not send them if ceilometer is not deployed.
1808998,2018-12-18 15:36:19 UTC,"neutron-api is also sending notifications, so adding it here"
1808998,2020-05-14 19:59:46 UTC,"Change abandoned by Gabriel Ramirez (<email address hidden>) on branch: master
Review: https://review.opendev.org/728274"
1809003,2018-12-19 11:00:45 UTC,"Hi Jeff,"
1809003,2019-01-07 09:49:26 UTC,"I'm not sure that package version ""6.5+svn4324-1"" reporting as ""6.6"" is a bug. It's quite common for VCS-based builds to anticipate the next version."
1809003,2019-01-07 13:10:08 UTC,"> ... It's quite common for VCS-based builds to anticipate the next version.
"
1809003,2019-01-08 18:30:19 UTC,"Our package is currently a sync from debian, so as soon as Debian updates it over there, we will get it in ubuntu as well."
1809008,2018-12-18 17:52:54 UTC,Have you tried the:-
1809008,2018-12-18 17:53:50 UTC,"Or disabling ""Memory Hole"" in the BIOS ?"
1809010,2019-08-05 05:41:26 UTC,Same for pad-length-to-die and net.
1809010,2019-08-05 22:50:45 UTC,"Fixed in revision 6c0a3b45344f043eeeb681b9d9cafbc7574c19d5
https://git.launchpad.net/kicad/patch/?id=6c0a3b45344f043eeeb681b9d9cafbc7574c19d5"
1809014,2020-03-30 15:23:09 UTC,Problem present in upstream (Debian)
1809014,2020-03-30 15:22:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809015,2019-02-17 16:41:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809017,2019-09-19 12:07:20 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1809017,2019-01-24 15:28:41 UTC,"Hi Kathryn,"
1809018,2020-03-07 17:34:54 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1809019,2018-12-18 18:15:53 UTC,It's a non-trivial change to the code but we'll be able to have a look at it with v6
1809019,2019-04-09 17:26:37 UTC,"@Seth, it looks like most of the code is pretty good about using GERBER_DRAWLAYERS_COUNT, and that we could just bump that up.  Did you find places where this is not the case (or where we assume GERBER_DRAWLAYERS_COUNT has a particular value)?"
1809019,2019-04-09 18:10:03 UTC,This issue with Gerbview are the places where the layer count is a bitmask on the 32-bit value.
1809019,2019-04-09 18:38:16 UTC,"Ah, I recall more now.  Search for ""SetVisibleLayers"" and ""GetVisibleLayers"" to find a bunch more bitmasks. (files.cpp, gerbview_layer_widget.cpp, gerbview_frame.cpp)"
1809019,2019-04-09 19:02:37 UTC,Hmmm... indeed.
1809019,2019-04-10 20:22:20 UTC,"Fixed in revision b7c12b238fe29e7cf2eefc56910fca4c1c211688
https://git.launchpad.net/kicad/patch/?id=b7c12b238fe29e7cf2eefc56910fca4c1c211688"
1809019,2019-04-17 21:31:41 UTC,"Hi,"
1809022,2019-01-26 15:48:49 UTC,"The actua beahavior is:
- the part of the category is used to colpute budget (or statistics in stats report)
- the detail is just a transaction list, so if you have a txn with a split on 2 category, for example
  + catA 10.00
  + catB 20.00"
1809022,2019-01-27 18:50:08 UTC,"the same apply:
- in statistics when you filter on catA, detail will show 30.00, should be 10
- in trend time when you select on catA, detail will show 30.00, should be 10"
1809022,2019-01-28 08:33:56 UTC,"Maxime,"
1809027,2018-12-18 19:22:41 UTC,"The easiest thing to do would be to just ship a keyring that had the
obsolete public signing keys.  Then the consumer could hard code
that 'precise' was signed with keys A, B, C.  and work stuff out like
that."
1809027,2020-02-11 13:35:35 UTC,"Removed keys, which are no longer in use by the current series by have been used by previous series are always shipped in the /usr/share/keyrings/ubuntu-archive-removed-keys.gpg and similar, which are not trusted by the new systems by default."
1809028,2020-03-07 10:29:58 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1809031,2018-12-20 13:38:42 UTC,show-controller also shows a good HA state here:
1809031,2019-01-17 06:40:28 UTC,"Removed field-crit as not more reproducing anymore.
For tracking purposes: the only important thing that changed in this deployment (not sure if this related to actual root cause or not) - we have removed a following from cloudinit-userdata:"
1809031,2019-01-11 14:21:42 UTC,"Any news or ideas re this?
We are ready to provide an access to environment or do some kind of troubleshooting to help you identify a root cause of this issue."
1809031,2019-01-08 13:24:18 UTC,"Greping the container name from the logs is a bit misleading, as the first error message does not contain this name."
1809031,2018-12-20 05:30:23 UTC,"The other command to check is ""juju show-controller"" which will tell us
whether we think the controllers are happy in HA."
1809031,2018-12-19 13:01:56 UTC,For a record:
1809031,2018-12-19 15:35:04 UTC,Tried to find that lxc container across logs:  https://pastebin.canonical.com/p/HbYDpBnQdg/
1809031,2018-12-19 15:26:37 UTC,"Oh, sorry, no possibility to edit; pretty-formatted lxc list: http://paste.ubuntu.com/p/vR3bDscBxf/"
1809031,2018-12-19 15:25:47 UTC,"Same behaviour on 2.5rc1
Controller and failed machine logs: https://drive.google.com/drive/u/1/folders/1sdapO0FyQKK2a_V31kMyuDjpPjQQzeFl"
1809031,2018-12-19 14:58:06 UTC,So chatting HA is settled before deployment happens. The smaller 8 machine version works but the larger 23 machine prod version fails. What's interesting is that each version puts the same number of containers (8) on converged machines like machine 5 that failed with the container exists issue.
1809031,2018-12-19 14:18:30 UTC,"2.3.9 HA failed with one container failed with message from bug subject.
Controller and machine logs: https://drive.google.com/drive/folders/1EfZp5gae9XFSgJimsUJga1oFimR4XSHY?usp=sharing"
1809031,2018-12-18 20:30:38 UTC,"Yes, this is controller IP addresses:"
1809031,2018-12-18 19:39:16 UTC,I assume .128 and .129 are controllers? Can they reach other on the mongodb ports for replication to setup?
1809031,2018-12-18 19:34:08 UTC,Subscribing field-crit as this impacts customer delivery.
1809031,2018-12-19 17:15:58 UTC,"2.4.7, HA mode, ""small"" bundle with 8 machines with 5..7 LXCs on each - all works fine.
So it looks like there is a dependency between machine quantity and possibility of raising this error."
1809036,2019-01-03 09:08:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809037,2019-07-17 01:57:27 UTC,"I don't think it worked well for sriov port bonding. IMO, it only supports active-backup. Bond Mode0 (balance-rr) will set same mac in two vNic, however the vf mac isn't changed. So, the vm communication will failed."
1809037,2019-04-15 07:10:47 UTC,We may need to handle QoS part.
1809037,2018-12-19 08:15:57 UTC,Seems to be related to https://blueprints.launchpad.net/nova/+spec/sriov-bond
1809037,2019-01-18 15:08:20 UTC,It makes sense to me. Let's bring it to the drivers meeting
1809037,2018-12-19 21:04:34 UTC,"Actually, I am the assignee of that BP which is created for Nova. It is a cross-project effort with Neutron and this RFE is the neutron counter-part."
1809037,2019-01-25 14:59:03 UTC,This RFE was discussed and approved during today's Neutron drivers meeting
1809037,2019-04-14 05:18:48 UTC,Quick link to the Neutron drivers meeting mentioned by Miguel: http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-01-25-14.00.log.html
1809037,2019-03-28 18:54:15 UTC,"can't we already add a key, val like we add local_link info incase of physical switch ?
we can still modify the code to assign some value to it by default, each port will have affinity =0 by default means that port want to be on its own ? for all other ids expect 0 nova can infer if they are same they belong to same group ?"
1809039,2021-01-19 18:02:34 UTC,"Bileto now honors hints for devel, I have not verified the stable ones yet."
1809045,2018-12-20 10:48:30 UTC,That's nautilus. And nautilus doesn't use trackerin 18.04. But it should still find something. Check if search is disabled or not. Not a unity bug.
1809045,2018-12-20 11:46:42 UTC,"Nautilus search is working fine, as stated in the description. Except when you come from dash. I don't know if that's a problem from the dash or nautilus."
1809045,2018-12-20 12:19:32 UTC,advised to change this to gnome-shell
1809045,2018-12-20 12:59:30 UTC,I'm reassigning to nautilus since nautilus provides the gnome-shell search provider.
1809045,2018-12-19 09:15:17 UTC,Can't reproduce this on cosmic. Can you take a screenshot ? Make sure all the default scopes and the local dash-plugins are enabled. Online scopes will be removed in disco.
1809045,2019-02-01 10:48:39 UTC,"Thanks for your bug report, indeed that's still an issue, reported upstream now on https://gitlab.gnome.org/GNOME/nautilus/issues/870"
1809045,2018-12-19 18:42:31 UTC,A screenshot of the page with no results?
1809045,2019-02-01 10:48:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809050,2018-12-23 15:19:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809051,2020-03-07 10:57:42 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1809052,2018-12-19 00:33:34 UTC,"tail: impossible d'ouvrir '/etc/grub.d/39_custom' en lecture: Aucun fichier ou dossier de ce type
tail: impossible d'ouvrir '(copie)' en lecture: Aucun fichier ou dossier de ce type"
1809052,2019-02-06 08:33:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809058,2020-11-16 07:53:00 UTC,Zero crash reports after 19.10 so consider it closed.
1809065,2018-12-19 09:51:10 UTC,"Change abandoned by yfzhao (dsware@126.com) on branch: master
Review: https://review.openstack.org/626073
Reason: has been fixed"
1809065,2018-12-19 03:14:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626073"
1809076,2019-01-21 01:40:20 UTC,Unable to fetch connection information from backend: 'wwpns'
1809079,2018-12-19 18:27:49 UTC,"crash not reproduced on Windows 10, Inkscape 0.92+devel (b9177a8, 2018-09-07)"
1809079,2018-12-19 18:16:07 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (6afa35c, 2018-12-14)"
1809080,2018-12-21 06:43:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626829"
1809080,2019-04-16 08:48:41 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1809080,2019-04-16 08:48:50 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/626829
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1809095,2019-06-13 19:38:28 UTC,"Reviewed:  https://review.opendev.org/661500
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=841d7d329df6832dcadcd9a1d59b1cf7c758209b
Submitter: Zuul
Branch:    stable/rocky"
1809095,2019-06-06 06:23:51 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1809095,2019-06-13 19:38:16 UTC,"Reviewed:  https://review.opendev.org/661499
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=28e7be8c8be5609ee33ff3eedacd20a70b9a409d
Submitter: Zuul
Branch:    stable/rocky"
1809095,2019-06-02 11:49:38 UTC,"Reviewed:  https://review.opendev.org/661495
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=77a339c4e8d51de82cd6c4530b8473cc8bb6aea8
Submitter: Zuul
Branch:    stable/stein"
1809095,2019-07-02 03:00:42 UTC,"Reviewed:  https://review.opendev.org/661572
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ab445a027a6262eb5d54f82edf76e8d925ac427e
Submitter: Zuul
Branch:    stable/queens"
1809095,2019-07-10 21:39:26 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1809095,2019-09-27 09:03:39 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1809095,2019-06-18 03:40:38 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1809095,2019-06-01 04:34:31 UTC,"Reviewed:  https://review.opendev.org/661494
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=84bb00a86da539183211364961ada2c1b1bb5edc
Submitter: Zuul
Branch:    stable/stein"
1809095,2019-07-02 03:00:28 UTC,"Reviewed:  https://review.opendev.org/661571
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8519b1ce6d0d001a57f57cf0a9ffcfdd2b6bc813
Submitter: Zuul
Branch:    stable/queens"
1809095,2019-05-27 09:08:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/661571"
1809095,2019-03-13 11:51:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/643024"
1809095,2019-05-27 09:08:41 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/661572"
1809095,2019-03-13 11:50:58 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/643023"
1809095,2019-03-13 13:13:45 UTC,"Change abandoned by Maria Luisa Arches (<email address hidden>) on branch: master
Review: https://review.openstack.org/630978
Reason: Abandoned, Adrian has another proposed fix for this"
1809095,2019-04-02 10:14:32 UTC,"triaged as medium.
i think this is a valid bug and i think its possible for the cold migration of
one instance it effect the connectivy of another on it previous host."
1809095,2019-01-15 13:51:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630978"
1809095,2019-05-24 22:14:25 UTC,"Reviewed:  https://review.opendev.org/643024
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=000e93df09fd4941bb69f715c955b940871a1ec6
Submitter: Zuul
Branch:    master"
1809095,2019-05-26 18:04:16 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661494"
1809095,2019-05-26 19:47:47 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/661500"
1809095,2019-05-26 18:04:30 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661495"
1809095,2019-05-26 19:47:33 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/661499"
1809095,2019-05-24 22:14:13 UTC,"Reviewed:  https://review.opendev.org/643023
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5a1c385b996090b80f5881680e04c88abc21828a
Submitter: Zuul
Branch:    master"
1809098,2019-07-18 08:05:48 UTC,"Hi,
what I know from the upstream is that libdfp is work in progress on x86 32b/64b.
So as the Debian package maintainer of libdfp, I don't intend to add other architectures than the one well supported.
In Debian, libdfp is also compiled on powerpc and ppc64.
So no other arch is planned to be added at the moment."
1809098,2020-07-29 10:09:59 UTC,"Small update on this.
Not sure I should have close that bug in my latest upload in Debian, but
with 1.0.15, libdfp has support for i386 and amd64."
1809099,2019-10-10 12:46:12 UTC,"As I understand it there are two different problems, neither of which are snapd-specific. Setting the bug as Invalid for snapd."
1809099,2019-03-26 00:30:55 UTC,"This appears to be related to the package manager snapd, not the DNA analysis tool snap."
1809100,2018-12-19 21:19:19 UTC,Looks that it's already addressed by https://review.openstack.org/#/c/599030/
1809108,2018-12-19 13:59:00 UTC,"The failure is not related to unattended-upgrades, but happened when upgrading packages using synaptic and synaptic lost debconf frontend connection when debconf tried to ask a question about the changed conffile:"
1809111,2018-12-20 02:23:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626426"
1809113,2018-12-19 13:08:00 UTC,data service log
1809113,2018-12-19 13:08:32 UTC,scheduler service log
1809113,2018-12-19 13:09:01 UTC,share service log
1809113,2019-03-22 14:41:30 UTC,Tom or Goutham are either of you taking this bug?
1809113,2019-04-03 10:17:57 UTC,I'm not going to work on this one immediately and would rather leave it in backlog rather than assigned until someone is ready to pick it up and actually begin working on it.
1809113,2018-12-19 13:06:37 UTC,api log
1809114,2019-01-21 20:52:08 UTC,"Reviewed:  https://review.openstack.org/626187
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=7e39428691eab57bfb23fda2185695da4a666fc4
Submitter: Zuul
Branch:    master"
1809114,2018-12-19 15:03:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626187"
1809114,2018-12-20 15:51:10 UTC,The reproduction test that I have indicated in the description is not right. Not for this issue. The bug looks to be a race condition by a missing mutex preventing updating container references. Basically executing tests in parallel is creating the issue.
1809116,2019-08-26 15:00:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678586"
1809116,2019-08-20 13:53:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677469"
1809116,2020-10-27 14:24:25 UTC,Keystone ussuri is still affected by the duplicate bug https://bugs.launchpad.net/keystone/+bug/1832092.
1809116,2020-04-10 09:37:55 UTC,"Reviewed:  https://review.opendev.org/714507
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c18956f198f223e3a47b2377b9007649187f4fd8
Submitter: Zuul
Branch:    master"
1809116,2020-04-10 00:18:51 UTC,"Reviewed:  https://review.opendev.org/713976
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=8153a9d5925b0ba60e43329ff6bfb5a4d1a12f97
Submitter: Zuul
Branch:    master"
1809116,2019-07-19 21:14:25 UTC,"Reviewed:  https://review.opendev.org/604201
Committed: https://git.openstack.org/cgit/openstack/keystone-specs/commit/?id=11885fcd929420ef4b4a6524765392296cdba8ab
Submitter: Zuul
Branch:    master"
1809116,2020-04-08 15:51:53 UTC,"Reviewed:  https://review.opendev.org/677469
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ee54ba0ce49a5cebbf991e705492ad060e11867f
Submitter: Zuul
Branch:    master"
1809116,2020-03-23 18:06:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/714507"
1809116,2020-03-19 20:28:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/713976"
1809116,2020-01-28 17:16:58 UTC,"Reviewed:  https://review.opendev.org/698951
Committed: https://git.openstack.org/cgit/openstack/keystone-specs/commit/?id=09f8b8b4b4b65e440af6c11fa940bdea83340370
Submitter: Zuul
Branch:    master"
1809116,2019-12-13 16:23:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/698951"
1809116,2020-04-10 00:18:42 UTC,"Reviewed:  https://review.opendev.org/678586
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d8938514fe3f9df54467f557e13770533c614259
Submitter: Zuul
Branch:    master"
1809123,2019-03-13 12:24:47 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/642997
Reason: Fixing up the cherry pick here:"
1809123,2019-03-24 23:39:07 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1809123,2019-03-24 23:03:59 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1809123,2019-03-22 18:16:33 UTC,"Reviewed:  https://review.openstack.org/633493
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2b1544390cd0afd4d2b0c6ea4636a49a73b50dcf
Submitter: Zuul
Branch:    stable/queens"
1809123,2019-03-22 03:43:10 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1809123,2019-03-19 20:23:27 UTC,"Reviewed:  https://review.openstack.org/643011
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7d0dd625d35a08d159b50154809a53e8444ae25c
Submitter: Zuul
Branch:    stable/rocky"
1809123,2019-03-19 15:59:39 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/641023"
1809123,2019-03-13 11:44:15 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/642998
Reason: Proper backport is here:"
1809123,2019-03-01 21:08:42 UTC,"Tim - just wanted to let you know that I've today been able to test that your fix (as at https://review.openstack.org/#/c/625741/2) seems reliably successful with my team's system testing.  I've run system tests with your fix for about 15 hours today, and they were all successful.  (I'll comment this on the change as well.)"
1809123,2019-03-13 10:47:14 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/642998"
1809123,2019-03-13 10:45:36 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/642997"
1809123,2019-03-13 00:26:00 UTC,"Reviewed:  https://review.openstack.org/641315
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=362bba9011f8445285c3f72a0b00630163bfbc2f
Submitter: Zuul
Branch:    master"
1809123,2019-03-05 14:27:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/641023"
1809123,2019-03-04 14:00:35 UTC,"Reviewed:  https://review.openstack.org/625741
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=525631d8dc058910728e55def616358b0e7f2f69
Submitter: Zuul
Branch:    master"
1809123,2019-02-01 15:23:19 UTC,"Tim, I'm sorry, I only just noticed your comment, because I forgot to subscribe to this bug."
1809123,2019-01-28 14:45:04 UTC,"Hey Neil,
""The biggest thing that I don't understand about this is: why aren't there loads of OpenStack users hitting this all the time? Do most OpenStack deployment using Queens or later not use NFS for instance ephemeral storage? If not, is that because they don't care about live migration, or because they're getting that some other way?"""
1809123,2019-03-13 11:33:15 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/643011"
1809123,2019-01-28 12:45:55 UTC,"Actually, after looking at your patch in detail, s/simpler/less mysterious/ !"
1809123,2019-01-28 12:26:34 UTC,"I have been regularly hitting this too, in a test suite (for the Calico networking driver) using Queens."
1809123,2019-01-28 12:40:22 UTC,"Since yesterday I have been running my test successfully with the workaround at https://review.openstack.org/#/c/633493/.  In other words, just don't worry if that utime call fails.  I'd be interested to hear if you think there's anything fundamentally wrong with that; it feels to me like a simpler fix than the locking that you have proposed."
1809125,2019-12-23 18:31:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809125,2021-02-19 17:46:19 UTC,"This problem (""libotf.so.0: cannot open shared object file"") is now over two years old, and has been reported more than 10 times, across multiple versions.
Is anyone working on this?"
1809128,2018-12-19 17:39:27 UTC,"I have just found that if I leave kompare set to a font that gets the wrong vertical alignment, then restart it, it displays properly in the new instance. The issue only seems to occur in the instance of kompare in which you first make the change."
1809128,2018-12-19 15:00:04 UTC,Every font I've tried suffers from these vertical spacing issues. It is not limited to the fonts I mentioned in the initial report.
1809132,2020-03-17 15:36:22 UTC,SRUing the newer version failed since it changed behaviour in some configuration which created issue for existing users.
1809132,2019-05-22 17:58:14 UTC,"Due to the SRU regressions reported in LP: #1829838 and LP: #1829566, I have reverted this SRU for the moment, restoring network-manager 1.10.6-2ubuntu1.1 to bionic-updates.  I am marking this bug verification-failed pending resolution of the reported regressions."
1809132,2019-05-13 14:14:17 UTC,"The verification of the Stable Release Update for network-manager has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1809132,2019-05-13 14:14:00 UTC,This bug was fixed in the package network-manager - 1.10.14-0ubuntu2
1809132,2019-05-10 13:55:22 UTC,Resetting verification status to verification-done as the re-upload is a trivial fix of the autopkg test which does not change anything in the functionality of the package itself.
1809132,2019-05-10 12:58:09 UTC,"Hello Sebastien, or anyone else affected,"
1809132,2019-03-14 19:24:03 UTC,"Sorry, I mean network-manager 1.10.14."
1809132,2019-03-18 11:12:16 UTC,Also on the Bionic VM on my main laptop I have updated network-manager to 1.10.14 and there are no issues.
1809132,2019-03-18 09:08:04 UTC,Now my Bionic test box is running for the whole weekend and it does not show any irregularities. No crash reports. The new network-manager seems to work fine on Bionic.
1809132,2019-03-14 19:11:18 UTC,"I have set up Bionic on an old laptop now and updated it with -proposed included, landing on network-manager 1.10."
1809132,2019-02-11 17:20:52 UTC,"Hi osomon,"
1809132,2019-02-05 10:22:10 UTC,I've installed and been running 1.10.14-0ubuntu1 for a while without problems now.
1809132,2018-12-21 17:22:19 UTC,"Please test and share your feedback on this new version here, but refrain from changing the verification-needed-bionic tag for now. This new version includes many changes and we want to give it an extended testing period to ensure no regressions sneak in, before it is published to bionic-updates. Thanks!"
1809132,2018-12-21 16:53:30 UTC,"Hello Sebastien, or anyone else affected,"
1809132,2018-12-20 09:53:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809132,2019-03-18 14:17:44 UTC,"Now after 3 months time for testing and no complaints coming up, Ken VanDine, Will Cooke, Olivier Tilloy, and me agreed on considering this SRU as verified. So I have marked this bug report appropriately."
1809136,2019-04-26 17:16:17 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1809136,2019-03-26 06:43:48 UTC,"Reviewed:  https://review.openstack.org/626556
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e61b1d7d72470a95068470d67779e08ececdb2e5
Submitter: Zuul
Branch:    stable/ocata"
1809136,2019-03-24 23:40:04 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1809136,2019-03-22 03:45:08 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1809136,2019-03-24 23:04:40 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1809136,2019-01-26 12:38:05 UTC,"Reviewed:  https://review.openstack.org/626550
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=79a90d37027b7ca131218e16eaee70d6d5152206
Submitter: Zuul
Branch:    stable/queens"
1809136,2018-12-19 23:50:04 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626410"
1809136,2018-12-19 23:43:51 UTC,"Reviewed:  https://review.openstack.org/626228
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1def76a1c49032d93ab6c7ee61dbbfe8e29cafca
Submitter: Zuul
Branch:    master"
1809136,2018-12-19 16:17:06 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626228"
1809136,2019-01-28 21:30:12 UTC,"Reviewed:  https://review.openstack.org/626554
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7b4f5725f821ef89176ef69f036471eaaf8a6201
Submitter: Zuul
Branch:    stable/pike"
1809136,2018-12-20 04:20:17 UTC,"Reviewed:  https://review.openstack.org/626410
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bc0a5d0355311641daa87b46e311ae101f1817ad
Submitter: Zuul
Branch:    stable/rocky"
1809136,2018-12-20 11:17:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/626550"
1809136,2018-12-20 11:21:13 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/626554"
1809136,2018-12-20 11:27:12 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/626556"
1809140,2020-01-27 13:29:37 UTC,"We will not be able to redistribute the snaps via the store, but this still has value.  Marking wishlist for now."
1809150,2019-08-07 15:39:14 UTC,Sorry for the lack of timely feedback Kulfy.
1809150,2019-08-20 17:23:01 UTC,@osoman It seems this has been fixed. I'm not able to reproduce with newer versions.
1809150,2019-08-20 17:34:02 UTC,Thanks! I'm marking the bug fixed accordingly.
1809151,2019-07-15 18:59:10 UTC,+1
1809153,2019-02-01 13:28:39 UTC,"Hi Vignesh,"
1809163,2018-12-19 20:29:55 UTC,"(Other bug that tracks the ""Bootloader install failed"" recovery dialog getting stuck: bug 1809164)"
1809163,2019-01-31 02:51:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809165,2019-03-24 23:40:03 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1809165,2018-12-20 13:41:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/626578"
1809165,2019-01-02 11:22:27 UTC,"Reviewed:  https://review.openstack.org/626578
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3b18ab4b32f7720c961a88865b781e77ca731501
Submitter: Zuul
Branch:    stable/rocky"
1809165,2018-12-20 12:42:32 UTC,"Reviewed:  https://review.openstack.org/626388
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1a4cc6c96dc9acd5e6bc467f85cb77dd9e32c8d4
Submitter: Zuul
Branch:    master"
1809165,2018-12-19 20:33:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626388"
1809165,2019-03-22 03:45:07 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1809167,2020-01-09 10:30:32 UTC,I can experience the same issue with byobu in Fedora 30.
1809167,2020-01-09 10:36:58 UTC,"Sorry for the noise.
Just recognise that 5.128 is out but Fedora30 still ships 5.127."
1809167,2019-01-25 08:50:57 UTC,"Hi David,
summarizing what was found so far."
1809167,2019-01-23 22:24:20 UTC,I implemented a fix and then noticed someone else also found a fix on Github. https://github.com/dustinkirkland/byobu/pull/30
1809167,2018-12-22 07:04:16 UTC,Here's a screenshot of the corruption happening.
1809167,2019-01-22 07:23:46 UTC,"I haven't tested from Ubuntu proper -- I didn't realize at first about the difference in code paths for Ubuntu derivatives.  Since 'pretending' to be Ubuntu for byobu purposes, and when I reported for System76 they didn't see the issue on Ubuntu, I'd say that it probably doesn't happen on Ubuntu proper."
1809167,2019-01-19 16:48:28 UTC,The Byobu prompt works fine for me in Ubuntu. I see the issues described above in Arch Linux.
1809167,2019-01-12 06:30:59 UTC,So I was able to verify that if ~/.byobu/prompt contains
1809167,2019-01-14 13:28:00 UTC,"So in Ubuntu it doesn't happen? When I start byobu in bionic, my shell gets BYOBU_DISTRO set to Ubuntu:
andreas@nsnx:~$ byobu
andreas@nsnx:~$ echo $BYOBU_DISTRO
Ubuntu"
1809167,2019-01-07 19:14:03 UTC,I was going to open a report for the same thing and then found this one.  Same problem I am sure.
1809167,2019-01-24 00:22:12 UTC,"The attachment ""non_ubuntu_color_fix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1809168,2018-12-27 18:43:44 UTC,"We now believe this to be the case.  The above is an issue
of new HW enablement."
1809168,2018-12-21 18:30:45 UTC,"This issue is not any of the above mentioned bugs,
after some checking."
1809168,2018-12-21 00:42:18 UTC,"I started a ""Reverse"" kernel bisect between v4.10 final and v4.11-rc1. The kernel bisect will require testing of about 7-10 test kernels."
1809168,2018-12-20 16:57:19 UTC,One check to see if the above is the issue:
1809168,2018-12-20 16:38:03 UTC,"v4.10 Final <---- FAILS
v4.11-rc1 <---- WORKS"
1809168,2018-12-19 23:25:41 UTC,The disk in question is a PERC_H740P_Adp.
1809168,2018-12-19 22:51:13 UTC,"Thanks, Joe. I'll update this bug as soon as I get the results
from the reporter."
1809168,2018-12-19 22:35:42 UTC,"We can perform a ""Reverse"" bisect to identify the commit that fixes this bug in 4.11.0-1.6.  It is easiest to bisect the mainline kernel.  Per the description, 4.11 final works.  Can you test the following two kernels?"
1809168,2018-12-19 21:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809168,2018-12-20 17:05:29 UTC,"Or the missing crypto packages (I should have added).
It's not likely the second URL above."
1809168,2018-12-20 16:48:20 UTC,There are some similar issues out there:
1809174,2019-01-07 17:55:21 UTC,"""reporting bugs to the effect that a no-change update should finish instantly."""
1809174,2019-01-07 16:32:11 UTC,"Note that the file we have in lists/ is not what we downloaded as we have downloaded a highly compressed version of the content (e.g. xz), but store it either uncompressed (for which we have a checksum) or lightly compressed (e.g. lz4 for which we have no checksum and can not as different versions of a compressor could produce different files). So such a check is not exactly free as we need to potentially uncompress the content we want to check – we can't even do a size check in the general case ""for free"". It might be worth it paying the price in ""update"", but there are a bunch of people who believe we shouldn't, reporting bugs to the effect that a no-change update should finish instantly."
1809174,2019-01-07 12:56:10 UTC,"I'm just curious, but what filesystem are those filesystems on? My understanding is that 0 byte files should not happen on ext4 at least."
1809174,2019-01-07 15:00:10 UTC,"I was picturing scenario (1); if there are updates or the checksum on the existing doesn't match, download the index."
1809174,2019-01-07 14:48:59 UTC,"So, 0.166s is very expensive in the sense that we can't do it every time we open the cache. We're literally optimizing every 10ms we can get there - apt-cache show would be twice as fast."
1809174,2019-01-07 15:21:49 UTC,I agree.
1809174,2019-01-07 14:40:08 UTC,"The problem with deferring the situation to the clean command is that the system appears to be working properly with no problem, and the user will have to _guess_ that cleanup is required."
1809174,2019-01-07 14:33:23 UTC,Filesystem is ext4
1809174,2019-01-07 12:57:30 UTC,"Verifying the checksums in normal operation is too expensive. I think it would be reasonable to make the clean command do that, and remove broken files."
1809175,2019-09-16 12:55:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809179,2019-01-28 15:31:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809179,2019-06-15 04:22:01 UTC,I found that version 2.0.2-4 in Debian fixed this problem. You can find it here:
1809183,2019-07-30 15:50:00 UTC,"Thanks, Jane.  Looks good.  I have merged to master for 3.4.  Since this is new-feature-ish and does not cleanly merge to rel_3_3, I opted not to backport for now.  Could be done pretty easily though if needed."
1809183,2019-05-27 16:48:59 UTC,"Here's a branch that implements Bill's solution, as well as including a sandbox example.  Enjoy!"
1809183,2018-12-27 16:56:40 UTC,"Jane, I think the Angular issue is to blame.  It looks like plurals in attributes won't be supported until they release the new Ivy rendering engine.  (Possibly available in Angular 8 -- I have confirmed it's not in Angular 7 for bug #1801984)."
1809183,2018-12-20 04:08:39 UTC,Maybe it is because of this? https://github.com/angular/angular/issues/21615
1809183,2018-12-20 03:11:53 UTC,"Sorry, wrong link to the documentation.  Should be this instead: https://angular.io/guide/i18n#regular-expressions-for-plurals-and-selections"
1809185,2018-12-21 17:56:43 UTC,"Don't know if this is related, but this morning I can't start  anakondi and syslog has the following:"
1809185,2018-12-20 00:52:13 UTC,apport information
1809185,2018-12-20 00:52:11 UTC,apport information
1809185,2018-12-20 00:52:09 UTC,apport information
1809185,2018-12-20 00:52:08 UTC,apport information
1809185,2018-12-20 00:52:04 UTC,apport information
1809185,2018-12-20 00:52:06 UTC,apport information
1809185,2018-12-20 00:52:05 UTC,apport information
1809185,2018-12-20 00:52:02 UTC,apport information
1809185,2018-12-20 00:52:01 UTC,apport information
1809185,2018-12-20 00:52:00 UTC,apport information
1809185,2018-12-20 00:51:58 UTC,apport information
1809185,2018-12-20 00:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809185,2018-12-20 00:52:07 UTC,apport information
1809189,2020-03-20 08:33:09 UTC,Closing because INVALID.
1809190,2021-02-05 00:02:46 UTC,"With the updated documentation and the various changes in the neutron code, I'm removing this from field-high. The bug will not expire due to the multiple tasks at this point in time, but if there continue to be issues here please reopen on the charm-neutron-gateway with appropriate logs and commentary."
1809190,2020-11-04 14:16:20 UTC,So a lot of work has been done on code related to this bug around the charm neutron code.  Please could you indicate if it is still a problem?  Setting to incomplete to get a reminder in 60 days.  Thanks.
1809190,2021-02-17 23:19:14 UTC,I've opened a new bug that is related to this issue. lp#1915967
1809190,2020-08-27 13:35:10 UTC,"Reviewed:  https://review.opendev.org/717074
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=bbc621edca348c2d0a9061bffb6d65f823b236c1
Submitter: Zuul
Branch:    master"
1809190,2020-04-02 16:19:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717074"
1809190,2019-07-31 15:30:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/673849"
1809190,2019-05-28 14:30:09 UTC,"Having discussed this bug in the OpenStack team, we've come to the following conclusion:"
1809190,2020-05-12 20:16:00 UTC,"To completely address the issue, I think work also needs to be done on the neutron-openvswitch charm for scenarios where neutron-gateway is not used."
1809190,2019-03-19 08:16:49 UTC,https://review.openstack.org/#/c/630290/
1809190,2019-01-11 19:07:31 UTC,"So the actual neutron-gateway code doesn't attempt to delete existing bridges.  i.e. if any of the parameters changes a mapping, the old mappings are left with the changes to the config being added via ovs.  The question is whether the neutron-gateway charm should enumerate what is currently configured in ovs (for example), see what the config is, diff that, and then take the appropriate action to remove bridge/port mappings that are no longer configured."
1809190,2018-12-20 22:06:41 UTC,"On Wed, Dec 19, 2018 at 8:40 PM Xav Paice <email address hidden> wrote:"
1809197,2018-12-20 17:35:56 UTC,"An example of an error that happened due to yaml containing unicode-encoded """
1809201,2019-10-25 06:33:30 UTC,Chase-up comment left on https://github.com/lxqt/lxqt/issues/1704
1809201,2019-11-12 07:04:43 UTC,"Lubuntu 20.04 QA-Test 2019-11-12 test on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1809201,2019-12-01 10:14:45 UTC,"This bug is marked against `lxqt-session`; and was filed upstream (LXQt).  Upstream LXQt linked a number of bugs, and have now said they aren't LXQt bugs, but an bug/issue in `openbox`."
1809201,2019-12-09 06:53:43 UTC,"20.04 QA-test on daily on dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
Purpose today was testing for a different bug so loads of different screens setups were being tried.. I noticed I'd lost ability to maximize qterminal on one display"
1809201,2021-02-25 07:34:51 UTC,I tested for this today using Lubuntu hirsute daily.
1809201,2020-04-17 01:49:06 UTC,"Lubuntu 20.04 QA-Test 2020-04-17 (20200416 ISO) test on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1809201,2020-04-17 01:50:09 UTC,refer prior comment.
1809201,2019-10-25 05:37:47 UTC,"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
purpose of this test is to start looking for old bugs & confirm focal impacted; these bugs are old & upstream issues and will impact very few end-users (impact me thus why chased)
boot up; adjust displays to match my setup (default-right display is below other display)
..
on lower display (as i adjust matching my setup) maximized windows go full width but only use 1/8th of vertical part of screen; this again is an upstream issue - https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1809201"
1809201,2019-12-12 05:41:51 UTC,"Lubuntu 20.04 QA-Test on
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1809201,2019-09-13 05:41:29 UTC,"QA-Test on Lubuntu 19.10 - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
no issues for two hours until I adjusted displays to match my setup, then https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1809201, https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1812342 .."
1809201,2019-12-09 06:56:15 UTC,"Same sessin as #23; except Qterminal is maximized
Qterminal is full width of display (landscape display) but has almost no height and is unusable as a terminal. Top window dressing, menu & tab is about all that can be seen"
1809201,2019-05-17 10:09:35 UTC,"I need to give up today; comment #14 is good, my request to ignore it was wrong (ie. please ignore my comment 15).  apologies for my wrong apology"
1809201,2019-05-17 10:07:29 UTC,Sorry - PLEASE IGNORE comment #14; attached to wrong report - Apologies.
1809201,2019-05-17 08:53:31 UTC,"dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
lubuntu 19.10 QA-test on d780
--- notes taken from qa-test comment
firefox; add ublock origin, stream vids in window, maximized, f11 & fullscreen on each display, firefox would NOT maximize correctly on portrait display
open term - it would NOT maximize on portrait display (not using all of screen; the part of the portrait display that's lower than the landscape display isn't used unless manually dragged there)"
1809201,2019-03-16 07:16:46 UTC,"QA-test Lubuntu 19.04 on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1809201,2019-03-15 07:53:50 UTC,Lubuntu 19.04 daily x86_64 QA-test (20190314)
1809201,2018-12-20 05:07:44 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1809201,2019-02-22 06:11:32 UTC,QA-Test of Lubuntu 19.04 x86_64
1809201,2019-02-18 00:53:49 UTC,2019-02-17 19:30 QA-Test Lubuntu 19.04 daily (live)
1809201,2019-02-16 02:47:20 UTC,"QA-Test 2019-02-16 on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1809201,2019-02-09 23:41:25 UTC,this needs a re-test; it's not doing it on my installed (& rather modified) lubuntu 19.04 system on d960 I just realized. i don't often qa-test with this box (it's usually running & where I enter comments etc) but has same [vertical] screen placement.  maybe it's related to video driver? or no longer an issue.  i need to re-test
1809201,2019-01-18 07:51:08 UTC,"QA-test on x86_64 machine ""hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"" and very similiar behavior so I won't create new bug-report; I'm adding here."
1809201,2019-01-18 08:15:45 UTC,qa-test on x86_64 - firefox window when unmaximized on display 2
1809201,2019-01-18 08:18:04 UTC,see prior comment please too
1809201,2019-05-17 11:01:39 UTC,"19.10 QA-test on d755[-8]
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
this box shares the same screens as #14 yet no issues here [today] !!!
but scrolling up - this d755 box had the issue in comment #11 ???
(same displays, but I forget when I fixed d780 to share the screens permanently which would have caused cabling to change..)"
1809205,2019-12-01 10:22:47 UTC,(and I should NOT have mentioned `vlc` - sorry... upstream response is same for each of upstream 'linked' bugs)  #6 ^^
1809205,2019-12-01 10:19:50 UTC,"This bug is marked against `lxqt-session`; and was filed upstream (LXQt).  Upstream LXQt linked a number of bugs, and have now said they aren't LXQt bugs, but an bug/issue in `openbox`."
1809205,2018-12-20 05:16:49 UTC,t43 qa-test; different machine to that used on first report..
1809205,2018-12-20 05:07:43 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1809205,2018-12-20 04:48:07 UTC,"I note internal display (LVDS) is set to primary; so this could be reason why  (d610 has laptop monitor as primary, and my focus was trying to re-create settings of aforementioned bug..)."
1809205,2019-12-01 10:21:07 UTC,sorry `lxqt-session` should say `lxqt-panel` in #6 ^^
1809206,2021-01-23 06:33:04 UTC,"Jeffrey,"
1809206,2019-07-01 19:55:38 UTC,Hp is a complete Linux enemy
1809206,2021-01-21 16:13:01 UTC,"I'm still seeing this issue on Focal. The rub is, this is a new machine - a Dell 8930 with fully updated firmware (https://www.amazon.com/gp/product/B078N85NCR)."
1809206,2021-01-21 16:12:38 UTC,Output of acpidump.
1809206,2020-05-02 13:54:15 UTC,"(In reply to Hans de Goede from comment #20)

> I see that you have already filed:
> https://bugzilla.redhat.com/show_bug.cgi?id=1830475
>
> Can you please attach full dmesg output and an acpidump (""sudo acpidump -o
> acpidump.txt"") there ?
"
1809206,2020-05-02 12:40:52 UTC,"I see that you have already filed:
https://bugzilla.redhat.com/show_bug.cgi?id=1830475"
1809206,2020-05-02 12:36:48 UTC,"(In reply to Jeffrey Walton from comment #18)

> Add a mee too. Hardware is ProLiant DL360 G5. Software is Fedora Server 32
> released Apeil 2020. Machine is fully patched.
"
1809206,2020-05-02 04:27:41 UTC,Add a mee too. Hardware is ProLiant DL360 G5. Software is Fedora Server 32 released Apeil 2020. Machine is fully patched.
1809206,2019-12-03 22:27:02 UTC,"The fixes for this have landed upstream, closing."
1809206,2019-11-27 13:37:40 UTC,"I've recently hit this seem issue, this is caused by the hp-wmi driver passing a buffer which is not big enough when making WMI related ACPI calls. I've submitted a patch-series which fixes this upstream:"
1809206,2019-07-01 19:06:41 UTC,"Follow-up,
The current ACPI status still remain unresolved to this date. The dmesg is located on https://linux-hardware.org/index.php?probe=ce83006200"
1809206,2018-12-29 19:07:00 UTC,"Created attachment 280191
acpidump data from HP Envy x360 15-cp0xxx"
1809206,2019-03-21 06:34:24 UTC,"I will never take Hp computers again
I don't know if the source of this problem is Hp or Amd."
1809206,2019-03-21 05:44:18 UTC,"Created attachment 281941
dmesg | grep ACPI"
1809206,2019-03-14 04:06:20 UTC,"[serdar@fedora Masaüstü]$ uname -a
Linux fedora 5.0.0-300.fc30.x86_64 #1 SMP Mon Mar 4 22:46:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1809206,2019-03-02 07:44:26 UTC,Updated to 4.20.12
1809206,2019-02-20 20:05:43 UTC,"Fedora 30 Raw
Kernel 5.0.0.0.rc6
[serdar@localhost Masaüstü]$ uname -a
Linux Fedora 5.0.0-0.rc6.git1.1.fc30.x86_64 #1 SMP Wed Feb 13 15:51:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1809206,2019-02-20 06:54:59 UTC,Same issue with kernel 4.20.8
1809206,2019-01-23 17:12:05 UTC,All amd processors have this error
1809206,2019-01-23 17:10:43 UTC,"Hp Device
Amd A10 9600P Cpu
R5 + R7 Apu Gpu
Kernel: 4.20.4"
1809206,2019-01-08 06:32:17 UTC,Switch to possibly right component
1809206,2018-12-29 19:07:59 UTC,Updated the priority and the kernel version.
1809206,2018-12-20 05:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809206,2018-12-13 08:35:02 UTC,I brought a brand new HP Envy x360 laptop and install a distribution. The issue occurred on both with the following error:
1809206,2018-12-14 02:29:14 UTC,Additional link to related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1520703
1809206,2018-12-20 04:07:10 UTC,"Hi
Hp Amd A10 9600p
[    3.546921] RAS: Correctable Errors collector initialized.
[    9.979321] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201)
[    9.979438] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.979484] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.979764] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201)
[    9.979872] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.988903] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.989220] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201)
[    9.989318] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.989358] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.990180] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201)
[    9.990274] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.990312] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.990557] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201)
[    9.990646] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516)
[    9.990682] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516)"
1809206,2019-04-05 07:31:15 UTC,"Created attachment 282133
acpidump data from HP Envy x360 15-cp0xxx"
1809210,2019-11-11 22:21:41 UTC,"For clarity, the commands used to remove the services (via ssh on one of the Cinder units):"
1809210,2019-01-16 14:07:14 UTC,"As suggested looks like a similar issue to the nova compute service problem - old, crufty service entries cause issues on upgrade."
1809210,2018-12-21 02:15:38 UTC,"This actually affected the Cinder volume and API services as well, the services started OK but didn't function until the db records had been cleaned up and the services restarted."
1809210,2018-12-20 06:59:53 UTC,"There were some entries in the Cinder db, in the 'services' table, which were elderly and should have been cleaned up, which were blocking the start of cinder-scheduler.  When I deleted them using cinder-manage service remove cinder-volume cinder@LVM (etc) that fixed the issue."
1809210,2020-01-31 16:41:53 UTC,Hi Xav
1809212,2018-12-20 08:43:03 UTC,Thank you for your bug report. What ubuntu version and desktop environment do you use?
1809212,2018-12-20 09:19:25 UTC,18.04 and GNOME.
1809212,2018-12-23 10:44:42 UTC,"Can confirm also on Ubuntu 18.04.
Related to bug 1726116?"
1809216,2019-04-03 15:14:49 UTC,"Interesting. This check is for standalone mode, where keystone is not used at all. Is there some trigger we can use to check for multi-region deployments?"
1809219,2018-12-20 08:03:54 UTC,"commit 0a5257bc6d89c2ae69b9bf955679cb4f89261874
Author: Emmanuel Grumbach <email address hidden>
Date: Tue Jul 17 13:43:56 2018 +0300"
1809219,2019-01-03 07:54:05 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-January/097456.html
1809219,2019-01-15 10:37:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1809219,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1809220,2019-06-27 20:42:46 UTC,"Keywords are being deprecated and removed, in favor of searching in the snap's description, summary and other current fields."
1809224,2019-09-16 07:15:20 UTC,"lotuspsychje, cool, thanks for the report.
The changeset is too large to fit in the SRU rules, so the iwlwifi changeset only applied on oem osp1 kernel."
1809224,2019-09-13 14:09:49 UTC,"Ubuntu 18.04.3 with kernel 5.0 default .iso
iwlwifi intel wifi was not loading properly on a Clevo N750WU"
1809224,2019-07-02 02:18:34 UTC,"You can also try the dkms package, backport-iwlwifi-dkms
https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-dkms"
1809224,2019-07-01 08:06:18 UTC,I'm running Disco 64-bit and my AX200 currently does not work with the stock kernel (5.0.0.20.21)  and linux-firmware (from proposed: 1.178.2).
1809224,2019-06-18 06:22:42 UTC,"linux-oem-osp1 has this now in bionic-proposed, please test"
1809224,2019-07-26 15:56:41 UTC,fixed in linux-oem-osp1 -1009.10
1809224,2019-07-01 09:32:14 UTC,"the backport is too big for the disco kernel, so either you get the osp1 kernel or wait for 19.10 to maybe have support for this in it's kernel"
1809224,2019-07-01 10:53:36 UTC,@tjaalton
1809225,2019-04-15 10:18:30 UTC,I eventually fixed it.
1809225,2018-12-21 12:11:39 UTC,Some more info on this problem.
1809225,2019-03-05 16:47:06 UTC,"We have a similar cloud which is Bionic/Queens; images are synced under the admin domain and marked as public, and users in the 'user' domain can see and use those images from both the CLI and the dashboard."
1809225,2019-01-07 15:37:25 UTC,I have found the root cause of my problem but are uncertain whether this is as designed or is in fact a bug.
1809226,2018-12-20 09:30:04 UTC,This change was made by a bot.
1809239,2018-12-20 12:33:12 UTC,"Hi Junien,"
1809239,2018-12-20 12:55:13 UTC,Hey Andres :)
1809241,2019-04-03 09:27:33 UTC,"This happens because BlockDevice has a unique_together on (node,name)."
1809243,2018-12-20 10:58:31 UTC,Attached converted PDF file.
1809243,2018-12-20 20:56:31 UTC,"in my testing, on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
and also in your pdf file in comment 2, the pdf file appears to be correctly oriented relative to the original svg.
could you indicate which part of this output is unexpected?"
1809243,2018-12-21 06:36:11 UTC,Alvin thanks for your quick response.
1809243,2018-12-21 11:49:10 UTC,"interesting.
I do not have Inkscape 0.92 on my machine so I cannot reproduce this problem."
1809243,2018-12-21 12:02:12 UTC,"attached here is the output I get from:
Windows 10, Inkscape 0.91 r13725 (Jan 30 2015)"
1809243,2018-12-21 12:03:35 UTC,"The problem is with Inkscape 0.92.3 version. If you see your attached PDF ""Arc Testing"" is going out of the artboard, whereas its inside the artboard in SVG."
1809243,2018-12-21 12:20:40 UTC,"part of the problem may be that this was not created by Inkscape, it was apparently created by:
<desc>Created with Fabric.js 1.4.12</desc>"
1809243,2018-12-21 12:32:33 UTC,"When you open up the SVG in the browser(Chrome), that show correct text as expected.
If you open up the same SVG in Inkscape 0.92.3 version GUI word ""Arc Testing"" comes rotated wherein you can see in SVG the letter ""g"" from ""Arc Testing"" is going out of the artboard. The reason is being observed that it gets rotate automatically especially with ""Arc text""(Curve text)."
1809243,2018-12-21 12:48:03 UTC,"Everything is working fine with Old version Inkscape 0.92(SVG and converted PDF ""GUI and Command line"")
This happing after update Inkscape 0.92.3."
1809243,2020-03-20 08:31:33 UTC,Closing because INVALID.
1809246,2018-12-20 13:18:33 UTC,"I have realized also, that it might be a hardware warm-up also.
(as if I try to start computer immediately after stop it happens - does not wait for a one-two sec)"
1809246,2018-12-20 13:13:50 UTC,"I have no time to reinstall the whole ubuntu right now, but I have cleanly removed the obaif, and the revert back was successful, although there is no error line that a Nvidia driver still persists on my ubuntu install."
1809246,2018-12-20 12:07:45 UTC,Isn't that the same issue you reported in bug #1808646 ?
1809246,2018-12-20 13:08:42 UTC,"The thing is I have some driver mess up, and I had to clean some of them to find the root cause."
1809246,2019-02-04 21:53:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809251,2019-01-08 22:30:05 UTC,What version of Juju is being used to see this issue? Juju does report any pod errors via juju status. It also reports pod status.
1809251,2019-01-09 02:25:58 UTC,"This was Juju 2.5, rc1 I believe. I'm testing with both Juju and microk8s edge using the snaps. I'll try and reproduce it."
1809254,2019-02-11 12:45:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809256,2019-06-24 21:32:31 UTC,bump
1809256,2019-06-25 11:26:38 UTC,you are welcome to submit your Pull Request at https://github.com/pld-linux/OpenCASCADE
1809257,2018-12-21 07:17:10 UTC,This is also suspicious to me:
1809257,2018-12-21 07:18:13 UTC,Adding prettier output of automaton for this state space:
1809257,2018-12-21 07:55:30 UTC,I've got same automaton as above even if I define it this way:
1809258,2019-06-17 04:17:41 UTC,[Expired for elogind (Ubuntu) because there has been no activity for 60 days.]
1809258,2019-09-04 16:41:05 UTC,question is still unanswered.  Please don't set expired bugs back to new without answering...
1809258,2019-10-07 20:02:01 UTC,"sway's build-depends is libsystemd-dev (>= 239) | libelogind-dev (>= 239), so it does not require elogind, and the packages are (hence) not build with it, as can be seen in the build log; but it would allow building on systemd-less system, but that's irrelevant for us."
1809258,2020-02-21 20:31:33 UTC,"Removing packages from focal:
 elogind 241.3-1+debian3 in focal
  elogind 241.3-1+debian3 in focal amd64
  elogind 241.3-1+debian3 in focal arm64
  elogind 241.3-1+debian3 in focal armhf
  elogind 241.3-1+debian3 in focal ppc64el
  elogind 241.3-1+debian3 in focal s390x
  libelogind-dev 241.3-1+debian3 in focal amd64
  libelogind-dev 241.3-1+debian3 in focal arm64
  libelogind-dev 241.3-1+debian3 in focal armhf
  libelogind-dev 241.3-1+debian3 in focal ppc64el
  libelogind-dev 241.3-1+debian3 in focal s390x
  libelogind-dev-doc 241.3-1+debian3 in focal amd64
  libelogind-dev-doc 241.3-1+debian3 in focal arm64
  libelogind-dev-doc 241.3-1+debian3 in focal armhf
  libelogind-dev-doc 241.3-1+debian3 in focal i386
  libelogind-dev-doc 241.3-1+debian3 in focal ppc64el
  libelogind-dev-doc 241.3-1+debian3 in focal s390x
  libelogind0 241.3-1+debian3 in focal amd64
  libelogind0 241.3-1+debian3 in focal arm64
  libelogind0 241.3-1+debian3 in focal armhf
  libelogind0 241.3-1+debian3 in focal ppc64el
  libelogind0 241.3-1+debian3 in focal s390x
  libpam-elogind 241.3-1+debian3 in focal amd64
  libpam-elogind 241.3-1+debian3 in focal arm64
  libpam-elogind 241.3-1+debian3 in focal armhf
  libpam-elogind 241.3-1+debian3 in focal ppc64el
  libpam-elogind 241.3-1+debian3 in focal s390x
Comment: Unused in Ubuntu, redundant with systemd; LP: #1809258
1 package successfully removed."
1809258,2019-04-17 15:37:51 UTC,sway has a build-dependency on libelogind-dev (>= 239).  What should be done with that package?
1809260,2019-01-16 12:21:52 UTC,"a ""openstack compute service delete"" might be possible to clean up the old, versioned services."
1809260,2019-01-16 12:19:41 UTC,@aieri
1809260,2019-01-16 12:45:48 UTC,deployment guide update: https://review.openstack.org/631209
1809260,2019-01-17 09:28:42 UTC,"Reviewed:  https://review.openstack.org/631209
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=5b82aa481447bdd033d8250f851422642ee46db3
Submitter: Zuul
Branch:    master"
1809262,2020-02-13 16:34:37 UTC,This bug was fixed in the package isc-kea - 1.6.1-0ubuntu1
1809262,2020-02-12 22:03:52 UTC,"I believe control-agent-commands.so was just in the example, and it's one of the ""premium"" hooks that isc sells for its customers. Also, the new example and documentation in 1.6.1 no longer show it at https://kea.readthedocs.io/en/latest/arm/hooks.html#ha-high-availability and I tested that setup."
1809262,2020-01-18 08:01:53 UTC,"Ran into this today, confirming."
1809263,2019-01-04 19:19:12 UTC,possible duplicate of 1807954
1809263,2019-03-29 13:21:06 UTC,"After consulting with our self check libraries, the libraries prefer that an item alert not block a check out.  It would be helpful if this bug is resolved that there be an option (probably a Library Setting) to block or not block the check out of an item with an item alert with the ability to set it at the library depth."
1809263,2019-01-04 20:26:47 UTC,It's not a duplicate of bug 1807954.
1809266,2018-12-21 09:23:11 UTC,"If I choose for example /guest/slb27 and give no authorization, it comes back with no authorization:
{""rs"": 16, ""overallRC"": 8, ""modID"": 1, ""rc"": 100, ""output"": """", ""errmsg"": ""SMUT error: SMUT request failed. RequestData: 'getvm SLB27 directory', Results: '{'rs': 16, 'errno': 0, 'strError': u'ULGSMC5100E Request not authorized by server', 'overallRC': 8, 'rc': 100, 'response': [u'(Error) ULTVMU0300E SMAPI API failed: Image_Query_DM, overall rc: 8, rc: 100, rs: 16, errno: 0, cmd: sudo /opt/zthin/bin/smcli Image_Query_DM --addRCheader -T SLB27, out:   API issued : Image_Query_DM', u'Failed', u'  Return Code: 100', u'  Reason Code: 16', u'  Description: ULGSMC5100E Request not authorized by server', u'  API issued : Image_Query_DM']}'""}"
1809266,2018-12-21 09:30:11 UTC,"Ok, I believe smcli need some toleration on the error message, we will recreate the problem and try to fix it"
1809266,2018-12-21 02:28:28 UTC,"ok, so I think the question here is when some API not authorized ,we should report some useful info instead of core dump or weird error"
1809266,2018-12-21 09:16:33 UTC,"I run this in the browser and get the next message:
{""rs"": 0, ""overallRC"": 500, ""modID"": 1, ""rc"": 301, ""output"": """", ""errmsg"": ""Unexpected internal error in ZVM SDK, error: SMUT internal error. Results: {'rs': 0, 'errno': 0, 'strError': '', 'overallRC': 25, 'rc': 301, 'response': ['(Error) ULTVMU0301E SMAPI API failed: Image_Performance_Query, response header does not have the expected 3 values before the (details) string. cmd: sudo /opt/zthin/bin/smcli Image_Performance_Query --addRCheader -T CLDCONO1 -T SLB27 -c 1, response header: , out: ']}""}"
1809267,2018-12-20 15:25:01 UTC,"After some more debugging the issue seems to come from lack of project scoped token that horizon uses.
I'm not sure that when using SSO, you should get a project scoped token when working with horizon, but in our case it seems we don't have one, and calling the keystone application_credential create with an unscoped token, gives you an unscoped application token, which is useless."
1809267,2020-08-19 04:31:49 UTC,"Just a note, we're seeing this still on a cloud running Stein, when logged in as a user from an LDAP domain."
1809267,2018-12-20 22:54:26 UTC,"after a lot of debbuging it was an issue with multidomain support being enabled.
when it is enabled, the api.keystoneclient overrides the user token with a domain token.
the user token has project scope, but the domain token does not; and thus application credential will (always?) fail"
1809269,2018-12-21 18:21:39 UTC,"Thanks for filing a bug. It is also helpful to briefly describe the bug in the ""summary"" field as well. I've paraphrased a sentence from your report for that purpose."
1809269,2019-11-15 04:09:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809269,2019-11-15 04:23:19 UTC,"This appears to be fixed for usbguard/0.7.4+ds-1, but not for earlier versions, including Bionic (see https://launchpad.net/ubuntu/+source/usbguard )."
1809274,2020-04-10 09:45:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809274,2018-12-20 16:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809275,2020-03-11 21:18:34 UTC,"I've been unable to reproduce this, is there something specific we can do to get a reproducer?"
1809275,2019-01-07 09:00:41 UTC,"UPDATE:  We re-deployed and just giving logs permissions isn't enough, ES also wants to create and add to /usr/share/elasticsearch/data.  Giving user.gorup ownership to elasticsearch for /usr/share/elasticsearch seems to resolve this better."
1809275,2019-02-25 08:33:04 UTC,"Is this being seen anywhere else? If not, what is special about this deployment?"
1809275,2019-02-27 14:51:31 UTC,"I also encountered this issue.
Deployed via `juju deploy cs:elasticsearch --config apt-repository=""deb https://artifacts.elastic.co/packages/6.x/apt stable main""`."
1809275,2020-06-15 04:17:20 UTC,[Expired for Elasticsearch Charm because there has been no activity for 60 days.]
1809275,2020-03-11 21:35:07 UTC,"We no longer have access to the environment that this was found in.  It was
both offline and air-gapped."
1809278,2018-12-28 14:08:45 UTC,"There's the nagios_uncommitted_{warn|crit} knob in current charm versions, is there anything else that is missing?"
1809279,2019-02-25 08:36:56 UTC,Is this being seen anywhere else?
1809279,2020-03-11 21:20:41 UTC,"I was able to reproduce this when running Elasticsearch in a lxd using fan-out networking, and another node on bare metal (i.e. different subnets)."
1809279,2019-02-18 13:35:29 UTC,I encountered this issue again (same customer as Jeff).
1809280,2018-12-20 16:25:56 UTC,https://review.openstack.org/#/c/626608/
1809280,2018-12-20 19:24:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626661"
1809280,2018-12-20 19:26:25 UTC,Would have been ideal if we had CI folks weighing in on the review https://review.openstack.org/#/c/612526/
1809280,2018-12-20 22:18:35 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.openstack.org/626661
Reason: waiting on results from https://review.openstack.org/#/c/626546/ and https://review.openstack.org/#/c/626546/"
1809280,2018-12-31 18:43:52 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.openstack.org/626661"
1809280,2018-12-20 19:15:22 UTC,Root cause is that the wrong options were updated for featureset010
1809282,2018-12-21 14:32:04 UTC,"Reviewed:  https://review.opencontrail.org/48308
Committed: http://github.com/Juniper/contrail-windows-docker-driver/commit/93077729ba79259e3b4aead0b6c412b2272948e9
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1809282,2018-12-20 16:29:33 UTC,"Review in progress for https://review.opencontrail.org/48306
Submitter: Micha? C?api?ski (<email address hidden>)"
1809282,2018-12-20 16:45:52 UTC,"Review in progress for https://review.opencontrail.org/48308
Submitter: Micha? C?api?ski (<email address hidden>)"
1809282,2019-01-02 13:28:28 UTC,"Reviewed:  https://review.opencontrail.org/48306
Committed: http://github.com/Juniper/contrail-vrouter/commit/86cd58b66bf7626000a5bd1957a6d150529e9dc7
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1809286,2018-12-20 19:55:18 UTC,Thank you for the report. I think this is an oversight. git ubuntu build should definitely enable proposed by default.
1809291,2018-12-20 18:21:49 UTC,"Hi, from this report your setup is unclear to me.
Are you saying that QEMU used to work on Ubuntu 15.10/18.04 and stopped working on 18.10,
or than current QEMU works with the default Linux kernel from Ubuntu 15.10/18.04 and does not work with the 18.10 kernel?
What is the size of your 'sdimage', what is the kernel used in 't.bin'?
Please provide more info.
Thanks,
Phil."
1809291,2018-12-20 18:53:53 UTC,"'Hi, from this report your setup is unclear to me'."
1809291,2019-01-22 18:54:57 UTC,"Hi -- could you please either provide a guest binary to reproduce with, or a complete set of sources to build to produce the test binary?"
1809291,2019-03-28 13:54:06 UTC,I'm marking this bug as incomplete since we can't investigate it without a test binary and QEMU command line to reproduce with.
1809291,2019-05-01 19:48:14 UTC,"I googled some code from comment #2 and got a hit for ""u32 RCA = (u32)0x45670000; // QEMU's hard-coded RCA"". Then I found kcwang's book: https://link.springer.com/content/pdf/10.1007%2F978-3-319-51517-5.pdf and read:
""I am also grateful to Springer International Publishing AG for allowing me to disclose the source code of this book to the public for free, which are available at http://www.eecs.wsu.edu/~cs460/ARMhome for download"". This link gives 404, however googling again ""site:www.eecs.wsu.edu/~cs460"" I found https://www.eecs.wsu.edu/~cs460/samples/ which thankfully provides sdc.tgz with the source files and binaries mentioned."
1809291,2019-05-02 03:47:21 UTC,The offending code is:
1809291,2019-12-05 13:54:39 UTC,"Dear Dr. KC.Wang,"
1809291,2020-11-12 17:29:38 UTC,"The new code in Qemu is correct, the real problem is that the code [1] is trying to negotiate an invalid working voltage with CMD41.
The SD specification marks the first 15 bits as reserved (except for the 7th, that's the dual-voltage flag) meaning that compliant cards will timeout as well."
1809291,2020-11-16 18:40:00 UTC,"The test expects the card wired as SPI, so adding ""-global sd-card.spi=true"" makes the test case work."
1809293,2019-01-08 18:30:35 UTC,This bug is related to: https://bugs.launchpad.net/kicad/+bug/1685516
1809293,2019-04-08 13:11:43 UTC,"Fixed in revision a1c162e59fa8f4c206bcaf22bece58404e0614db
https://git.launchpad.net/kicad/patch/?id=a1c162e59fa8f4c206bcaf22bece58404e0614db"
1809294,2020-05-02 14:52:19 UTC,"Workaround: Simply rename the path or, if you can't, move the ISO to another place, and burn it to Multisystem from where."
1809294,2020-05-02 15:45:33 UTC,"Yes, thank you for the workaround. But it's not convenient. Hope this bug will be solved."
1809306,2019-02-14 04:06:34 UTC,"Reviewed:  https://review.openstack.org/627199
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=6023978ae7b9a7fdc960cb577ec3e1474d5677a8
Submitter: Zuul
Branch:    master"
1809306,2019-03-07 10:32:20 UTC,This issue was fixed in the openstack/kuryr-libnetwork 3.0.0 release.
1809306,2019-01-20 13:21:59 UTC,"Reviewed:  https://review.openstack.org/627198
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=5fb8275d1202d6ab8880e9fd021e22c59353ce4f
Submitter: Zuul
Branch:    master"
1809306,2018-12-22 23:14:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627054"
1809306,2019-01-06 06:30:43 UTC,"Reviewed:  https://review.openstack.org/627055
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=dc3cf2cc93a36006f8c16450a3e11b146314258c
Submitter: Zuul
Branch:    master"
1809306,2019-01-06 06:18:58 UTC,"Reviewed:  https://review.openstack.org/627054
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=610fd5f02443f2b97e9d10557bc680868951dbb9
Submitter: Zuul
Branch:    master"
1809306,2018-12-23 00:26:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627057"
1809306,2018-12-22 18:33:49 UTC,I ran your script in master branch and the result is as below:
1809306,2018-12-21 20:05:07 UTC,"My supervisor said we probably won't keep using Queens much longer, so there is no need to backport.  But we do appreciate that you offered."
1809306,2018-12-20 21:28:30 UTC,Short answer:
1809306,2019-01-06 06:33:21 UTC,"Reviewed:  https://review.openstack.org/627057
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=b194b0732fd4c0ed7ecaf211de06952339b38e3e
Submitter: Zuul
Branch:    master"
1809316,2019-01-04 17:22:18 UTC,apport information
1809316,2020-02-03 04:17:25 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1809316,2019-11-08 07:42:30 UTC,This should be solved by later kernel release. Does this issue still occur?
1809316,2019-01-04 17:22:27 UTC,apport information
1809316,2019-01-04 17:22:23 UTC,apport information
1809316,2019-01-04 17:22:12 UTC,apport information
1809316,2019-01-04 17:22:39 UTC,apport information
1809316,2019-01-04 17:22:02 UTC,apport information
1809316,2018-12-21 01:56:46 UTC,Your kernel log suggests the problem is originating in the kernel:
1809316,2019-01-04 17:22:07 UTC,apport information
1809316,2018-12-21 02:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809316,2019-01-04 17:20:42 UTC,apport information
1809316,2019-01-04 17:20:35 UTC,"ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-01-03 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS ""Bionic Beaver"" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 04f3:25ec Elan Microelectronics Corp.
 Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc.
 Bus 001 Device 003: ID 0a5c:5834 Broadcom Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 7530
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=89239537-83fb-4668-9120-bb13ce96bc1f ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-43-generic N/A
 linux-backports-modules-4.15.0-43-generic  N/A
 linux-firmware                             1.173.2
Tags:  bionic
Uname: Linux 4.15.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:"
1809316,2019-01-04 17:21:03 UTC,apport information
1809316,2019-01-04 17:21:52 UTC,apport information
1809316,2019-01-04 17:21:08 UTC,apport information
1809316,2019-01-04 17:21:47 UTC,apport information
1809316,2019-01-04 17:20:52 UTC,apport information
1809317,2019-01-07 07:38:32 UTC,"Thanks Scott for filing that with some details and examples, I'll mostly copy and paste that upstream for their consideration to fix it there."
1809317,2019-01-07 07:42:25 UTC,Added there and a tracker here
1809319,2018-12-22 09:44:38 UTC,It looks like the timer code requires some improvement. Another report:
1809322,2019-07-13 15:19:43 UTC,Both issues seem to have been resolved.
1809323,2020-07-24 02:54:43 UTC,"Reviewed:  https://review.opendev.org/742220
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=29d956c0cee09465730f304cee7cc69dd137f2be
Submitter: Zuul
Branch:    stable/rocky"
1809323,2020-07-20 21:34:02 UTC,"Reviewed:  https://review.opendev.org/739606
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=ef07bc95471101e42d531908a00c242710834784
Submitter: Zuul
Branch:    stable/stein"
1809323,2020-07-06 21:19:22 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/739606"
1809323,2019-09-27 09:03:33 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1809323,2018-12-21 01:35:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626790"
1809323,2020-07-21 15:08:47 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/742220"
1809323,2019-08-16 04:55:11 UTC,"Reviewed:  https://review.opendev.org/626790
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=a62fabfa65bf02ab91ff61ad2b74a6eb7509ee24
Submitter: Zuul
Branch:    master"
1809348,2018-12-27 17:24:45 UTC,I wound up editing the permission we gave it by binding a custom role that granted the specific IAM permission it was seeking and that seems to have resolved the inconsistencies for now.
1809350,2018-12-21 02:39:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626800"
1809350,2018-12-21 06:09:46 UTC,"Change abandoned by Yang Le (<email address hidden>) on branch: master
Review: https://review.openstack.org/626800"
1809350,2018-12-21 06:22:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626822"
1809355,2019-02-18 10:10:46 UTC,It should be a bit more elaborate as there can be many pools per a single Calico deployment:
1809355,2019-02-26 09:13:09 UTC,Dmitrii what's the urgency on this?
1809355,2019-06-18 19:32:55 UTC,"Fixed by https://github.com/charmed-kubernetes/layer-calico/pull/33, which is available with cs:~containers/calico-630 in the edge channel."
1809357,2019-08-01 15:07:48 UTC,Fixed in 1.15-ck1
1809363,2019-08-01 20:10:45 UTC,"This can be done by setting a version in `docker_runtime_package`.  E.g. `docker_runtime_package=""docker=2.0.3+docker18.09.1-1""`."
1809371,2018-12-21 03:07:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626802"
1809371,2018-12-21 06:22:19 UTC,"Change abandoned by Yang Le (<email address hidden>) on branch: master
Review: https://review.openstack.org/626802"
1809373,2019-07-02 11:38:22 UTC,"Same problem
Please see the post
https://bugs.launchpad.net/kolla-ansible/+bug/1736692/comments/2"
1809373,2019-07-22 14:40:25 UTC,"We are also seeing the problem:
Following a planned maintenance outage in our data center where each node had to be powered down in a  controlled fashion . One kolla node (containing ceph OSD and compute) failed to start any docker containers after boot."
1809373,2019-01-03 18:39:27 UTC,I have the same issue. I'm deploying a development Openstack.
1809373,2018-12-21 09:12:25 UTC,@Mark Goddard (mgoddard)
1809373,2018-12-21 08:52:48 UTC,"Looking at the code around this task, it looks like this might happen if not all ceph hosts are in the ceph-mon group. It looks like that could be the case in your environment, since the storage hosts will be in the ceph-osd group but not ceph-mon."
1809373,2018-12-21 08:46:04 UTC,Could you provide more information? Which command were you running at the time? Which release of kolla-ansible?
1809373,2019-01-08 13:28:37 UTC,It's strange but this task must be executed on monitors nodes wich are the control not storage.
1809374,2019-08-01 20:14:02 UTC,This is handled by the reactive framework.
1809377,2019-07-11 22:03:18 UTC,Another PR: https://github.com/charmed-kubernetes/cdk-addons/pull/133
1809377,2019-07-30 19:30:56 UTC,Charm fixes cherry-picked to stable branches:
1809377,2019-07-16 21:16:45 UTC,"The cdk-addons part of this fix has been backported to release-1.15, release-1.14, release-1.13."
1809377,2019-07-05 18:00:53 UTC,"In testing, we found that the TLS client charms do not handle the transition from easyrsa to vault properly. I've added all of the affected components to this issue."
1809377,2019-07-01 15:10:32 UTC,https://github.com/charmed-kubernetes/kubernetes-docs/pull/223 adds instructions to transition a CDK cluster from EasyRSA to Vault and improves the documentation for making Vault HA.
1809377,2019-06-26 21:48:21 UTC,"Thanks Xav. This is an old bug that should actually be closed now, since in the meantime we've provided a new recommended way to establish a HA certificate authority, using Vault instead of EasyRSA. Read https://ubuntu.com/kubernetes/docs/using-vault for details on using Vault with Charmed Kubernetes."
1809377,2019-06-18 05:47:00 UTC,"I've added the canonical-bootstack tag here, as this affects our production Bootstack environments in the following way:"
1809377,2019-06-18 05:47:44 UTC,"adding field-high, as the current implementation needs some design review"
1809377,2019-06-28 00:18:11 UTC,"For the sake of clarity, there's two models right now where we need to have a migration path:"
1809377,2019-06-26 22:12:20 UTC,Tim Van Steenburgh <email address hidden> writes:
1809377,2019-06-27 16:35:44 UTC,"James H - Yes and yes, but we're missing docs for that migration. Working on that now."
1809377,2019-06-26 22:37:57 UTC,">
> Canonical OpenStack supports full disk encryption.  It does this using
> vault.  vault uses etcd as a backing store.  etcd gets its TLS from
> easyrsa.
>
"
1809377,2019-06-26 22:55:04 UTC,Tim - Are you aware of a migration path between the easyrsa charm and the vault charm? Are users wanting to migrate from a non-HA deployment to a HA deployment based on Vault considered a supported use case?
1809377,2019-06-27 08:52:08 UTC,"There has to be a migration path. A solution involving new technology is not a solution for existing users unless there is a documented, tested migration path."
1809385,2019-05-24 20:54:22 UTC,"What possibly is trying to lock /dev/null? I'm trying to understand this problem; a simple redirection (like something >/dev/null) seems not to cause the lock attempt. I have not much experience in juju/snaps/charms, so I'm trying instrumenting the kernel file locking functions to collect information."
1809392,2019-05-30 17:52:52 UTC,Deploying kubernetes on Power9 I have the same problem reported here.
1809392,2019-05-30 19:21:30 UTC,"We don't officially support POWER, so this likely won't be fixed or documented until we do."
1809397,2018-12-21 07:47:03 UTC,The problem can be solved by add linux-image-extra-4.4.0-140-generic in package list.
1809400,2018-12-21 05:04:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809407,2019-10-08 03:43:34 UTC,Set up a new bionic machine and tested both Nvidia 430 and 340. The bug doesn't exist there.
1809407,2019-10-04 07:55:04 UTC,Curious. I was looking at preparing a fix for Ubuntu 18.04 but in my initial setup for backporting have found that I can't reproduce the bug with Gnome 3.28. Though this is now with Nvidia driver 430.50 too.
1809407,2019-09-25 21:20:10 UTC,"Glad to see this proposed as a fix for 19.04, thanks for the work!"
1809407,2019-09-19 12:54:54 UTC,Progress!
1809407,2019-09-16 09:44:39 UTC,"satmandu,"
1809407,2019-09-13 17:11:23 UTC,I'm still seeing this issue on resume from sleep today on my updated 19.10 setup with gnome-shell 3.34.0-1ubuntu1.
1809407,2019-08-31 18:54:22 UTC,How to apply the patch https://gitlab.gnome.org/GNOME/mutter/merge_requests/600.patch ? Thx
1809407,2019-10-08 10:53:37 UTC,"Hello, Daniel. I've experienced it in 18.04 and 19.04 both with nvidia-390.129 in a XPS with hybrid intel x nvidia.
I hope had contributed. If you need some thing let me know."
1809407,2019-08-27 13:14:14 UTC,This bug was fixed in the package mutter - 3.33.91-1ubuntu1
1809407,2019-08-08 03:37:16 UTC,"The fix for this bug is in mutter version 3.33.4, which will eventually reach Ubuntu version 19.10, and then maybe others after that."
1809407,2019-08-08 02:49:07 UTC,"Sorry for inconvenient Daniel, but the version 3.33.4 was rejected in review?"
1809407,2019-08-05 00:45:54 UTC,I have three screens:
1809407,2019-07-22 03:27:03 UTC,"I want to give the fix time to settle, because the number of sub-fixes required seemed to change between the 3.33 source and 3.32. And aside from that, we are required to get the fix into 19.10 first."
1809407,2019-09-02 01:59:42 UTC,"Ubuntu 19.10: Just update your system.
Ubuntu 19.04: Please wait for future updates.
Ubuntu 18.04: Please wait for future updates."
1809407,2019-10-09 06:25:56 UTC,I've now tried nvidia-390 on 18.04 and still can't reproduce the bug there.
1809407,2018-12-21 07:01:40 UTC,This sounds like a combination of bug 1769383 and something else. Can you please provide a photo of the issue so we can figure out what the second part is?
1809407,2019-10-10 01:54:07 UTC,"I've had this issue in the past on Ubuntu 18.04 with the NVidia 340.x driver series.  Two days ago with driver 340.107 and the latest released system updates, the lockscreen wallpaper corrupted for about 2 seconds on resume from suspend, then the wallpaper reloaded, appearing fine.  In the past, the lockscreen wallpaper would remain corrupted for at least a minute (presumably indefinitely, but I didn't wait to find out)."
1809407,2020-08-25 01:30:07 UTC,"^^^
That is bug 1892440. It is not relevant here."
1809407,2020-08-24 13:36:40 UTC,For now you can easily fix this without any third-party applications by following these instructions: https://askubuntu.com/a/1269431/1119550
1809407,2020-07-28 02:46:02 UTC,This bug is closed. Please use bug 1855757 instead.
1809407,2020-07-27 18:45:26 UTC,This bug is still present in a fresh install of Ubuntu 20.04.1 LTS on a Lenovo T510.
1809407,2020-03-12 21:13:58 UTC,"I just fixed my issue with this script:
https://slimbook.es/tutoriales/linux/422-fixing-the-broken-desktop-after-resuming-from-a-suspension-in-gnome"
1809407,2019-12-18 01:39:36 UTC,"This bug is closed. Some people have said they still see an issue though, so please use bug 1855757 from now on..."
1809407,2019-07-20 23:10:24 UTC,"@vanvugt can this fix be backported to gnome-3-32 branch? I just talked to the package maintainer in Arch repos and they said 3.33.4 is odd numbered, hence not a stable release, so we would have to wait for 3.34, but given how this is affecting many people I wished it sooner rather than later. They said they track 3.32, so if it gets backported, the package registry will pick it."
1809407,2019-12-17 13:14:14 UTC,I only want to add that the bug still exists. Since I don't know if the patch is on the way I don't know if it is worth to add a new bug. I am using Ubuntu 19.10 with Nvidia drive 340.107. Attached find a hardcopy of the screen
1809407,2019-12-02 14:28:00 UTC,"Also workaround is to restart gnome, Alt+F2, ""r"" and it seems to refresh the wallpaper."
1809407,2019-12-02 14:26:41 UTC,Nvidia Version 340.107
1809407,2019-12-01 22:19:10 UTC,"Having recently tried upgrading an 18.04 system to 19.10, I can confirm ~rigues 's behavior - complete screen corruption after resuming from suspend when using the Nouveau driver (NVidia driver only partly corrupts)."
1809407,2019-12-01 19:23:59 UTC,"I am still experiencing this on 19.10, with *both* the Nvidia and Nouveau drivers (maybe a new issue?). I'm currently running Nouveau, and when resuming from sleep the screen is completely corrupt, the only distinguishable feature is the mouse cursor. I tried logging in ""blindly"", but I don't know if I succeeded, as the only thing I can see is color noise."
1809407,2019-11-09 14:23:40 UTC,"OK, this is how the screen looks with latest Ubuntu 19.10. It's still a problem."
1809407,2019-10-22 03:48:44 UTC,Dropped the bionic task until such time as this becomes a reproducible and testable bug there.
1809407,2019-12-04 09:49:58 UTC,"This bug is closed, rightly or wrongly. So if you continue to experience any problems then you will need to open a new bug by running:"
1809407,2019-10-09 06:34:27 UTC,There appear to be no bug reports from 18.04 either.
1809407,2019-07-17 09:39:13 UTC,The official fix landed upstream last night. It is fixed in mutter version 3.33.4 and later.
1809407,2019-07-15 01:49:38 UTC,The formal fix is awaiting review;
1809407,2019-04-19 14:01:14 UTC,"I got this bug too after upgrading to 19.04 release with nvidia driver 418.
I see the corruption in lock screen and desktop background."
1809407,2019-04-18 20:23:51 UTC,"The attachment ""nvidia-background-workaround.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1809407,2019-04-18 16:30:01 UTC,I was able to work around this with the attached patch. Apply by adding the file to debian/patches and its name to the end of debian/patches/series
1809407,2019-04-18 15:49:46 UTC,There is an upstream bug related to GNOME 3.32 here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084
1809407,2019-04-12 18:47:59 UTC,"Just chiming in from Arch Linux, we got it too."
1809407,2019-04-11 01:56:15 UTC,"Hmm, actually, if the problem did get worse or more common in 19.04 then we should use bug 1822179 instead."
1809407,2019-05-03 07:03:14 UTC,Also in Trello: https://trello.com/c/i5hENxSO
1809407,2019-04-10 10:24:20 UTC,"Hi, in debian testing this does not happen, neither in debian unstable or other distros with the same gnome-shell package version"
1809407,2019-04-01 02:05:54 UTC,That's OK. This bug is tagged 'disco' meaning it also occurs in 19.04.
1809407,2019-03-29 12:32:51 UTC,"Hi Daniel, I've seen you marked my bug as this duplicate, but for me this doesn't happen on Ubuntu 18.10, only after the 19.04 upgrade"
1809407,2019-03-29 04:57:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809407,2019-02-21 04:17:15 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1809407,2019-02-21 04:17:12 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1809407,2018-12-22 05:34:04 UTC,I did some random trial and error debugging.
1809407,2019-04-01 11:02:03 UTC,"Okay, it's fine anyway I tested 18.10 again as well with another distribution with roughly the same packages and I was not able to reproduce the issue"
1809407,2019-07-17 09:27:17 UTC,"Hello,
A few weeks ago we fixed this bug with this script:"
1809407,2019-05-03 20:40:31 UTC,"What I've made a temp fix is this
place file in /lib/systemd/system-sleep
credits to: Paul Knopf (https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084)"
1809407,2019-05-07 09:53:23 UTC,Sorry... chmod a+x (I haven't got my coffee yet)
1809407,2019-06-26 01:30:01 UTC,"The Ubuntu release process requires that we always get the fix into the _next_ release first. That means 19.10. After that we are free to propose it for 19.04 and earlier. I have nominated 19.10, 19.04 and 18.04 at the top of this bug."
1809407,2019-06-25 12:16:18 UTC,"I'm also interested in this, will it be fixed for 19.04 too?"
1809407,2019-06-21 20:34:06 UTC,Will this be fixed for disco as well?
1809407,2019-06-07 10:22:04 UTC,Fix proposed: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/368536
1809407,2019-06-07 10:04:47 UTC,"Since this is a potentially large set of fixes required (in the long term), I am explicitly only aiming to fix the background wallpaper corruption in this bug. If anyone finds other things corrupt upon resuming from suspend then please open additional bugs for those."
1809407,2019-05-31 01:19:23 UTC,"It's a general problem with the Nvidia driver. A fix is on the way here:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/600"
1809407,2019-05-07 09:43:15 UTC,I added @gwolf2u-website patch as /lib/systemd/system-sleep/nvidia.sh and changed permissions to a+w. The problem persists
1809407,2019-05-30 18:47:10 UTC,I dont think this issue is exclusive to ubuntu I get the same thing on arch using gnome https://imgur.com/a/ILOLikj
1809407,2019-05-09 20:49:43 UTC,Here's a video of a typical loop. It's still sometimes possible to type my password and press Enter to get out of this.
1809407,2019-05-09 13:22:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809407,2019-05-09 09:03:08 UTC,"Tried to resume, and was greeted with this (attached photo)."
1809407,2019-05-09 08:20:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809407,2019-05-07 13:59:40 UTC,"Daniel, you seem to have a looked at that/pinged Jonas, I'm assigning to you"
1809407,2019-05-07 13:13:33 UTC,I've just tested adding the
1809407,2019-05-10 01:46:03 UTC,"Petter,"
1809407,2019-07-11 22:17:46 UTC,I fixed the workaround script mentioned above here:
1809411,2019-01-09 06:30:49 UTC,"No I'm not grepping for anything. I just think ""juju status <app>"" should be robust and always show the same applications when run multiple times on the same model."
1809411,2019-01-08 16:46:58 UTC,"I'm confused. Why is juju status with the ceph-osd returing other applications? Actually, looks like it's returning status for anything on those ceph machines."
1809415,2019-09-17 11:49:59 UTC,I think we should close this bug since it doesn't meet the ESM criteria required by Trusty and Precise (since these kernels have recently transitioned to ESM).
1809418,2019-01-23 00:22:08 UTC,"Reviewed:  https://review.openstack.org/626853
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=47937b6113dfe34202926536a2c43d3f85676026
Submitter: Zuul
Branch:    master"
1809418,2018-12-21 08:35:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626853"
1809418,2019-01-23 13:29:28 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/632720"
1809418,2019-03-24 23:39:47 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1809418,2019-02-02 01:22:06 UTC,"Reviewed:  https://review.openstack.org/632720
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ba269da87a7ac0130f87fca78083a09231533c2f
Submitter: Zuul
Branch:    stable/rocky"
1809418,2019-03-22 03:44:30 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1809423,2018-12-21 09:43:19 UTC,"Can you say whether the problem applies to all applications' windows, or just some?"
1809423,2018-12-21 09:45:42 UTC,Oops. Actually this issue is likely just lack of support for the GTX 1080 in the nouveau driver.
1809423,2018-12-21 09:59:16 UTC,"Hi,"
1809423,2018-12-21 10:38:02 UTC,"Hi,"
1809423,2019-03-11 01:57:16 UTC,It appears the problem is most likely this:
1809423,2019-07-22 04:21:12 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1809423,2018-12-21 09:42:45 UTC,"Please keep each bug report about a single issue. This bug will now be about only ""stuttering when dragging windows around""."
1809424,2018-12-21 09:28:25 UTC,I selected the Display(xorg) category because it seems to have to do with the intel graphics card driver. But probably not directly with xorg.
1809424,2018-12-21 10:00:06 UTC,This change was made by a bot.
1809425,2019-05-05 17:53:24 UTC,Any progress? I also have a N151ZU
1809425,2019-08-19 07:40:13 UTC,I open an issue here for those who want help.
1809425,2020-11-25 15:06:39 UTC,Drivers requests are upstream bugs and as such should be redirected to the official wiki
1809425,2018-12-24 23:27:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809425,2019-03-05 21:20:03 UTC,Just to say  similar 06cb:00a8 is also on Clevo N151ZU
1809425,2018-12-21 09:42:21 UTC,The windows driver could be downloaded here:
1809428,2018-12-21 10:00:12 UTC,This change was made by a bot.
1809428,2020-01-17 08:16:16 UTC,"This is affecting Trusty kernel.
In Xenial this has been modified to SUB_DIRS."
1809435,2018-12-21 10:30:04 UTC,This change was made by a bot.
1809437,2018-12-21 10:32:25 UTC,secondo me legato all'installazione di playOnlinux e l'errore nell'installazione di internet explorer 7 o 8.
1809438,2019-01-09 09:43:15 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1809438,2019-03-31 10:56:48 UTC,"not sure if this gives helpful information, but here is a backtrace:"
1809438,2019-03-31 11:17:17 UTC,"the backtrace is not always the same, here another one:"
1809438,2020-02-28 20:57:19 UTC,"How should I persistently bypass systemd-resolved ? The DNS failures are causes other applications to fail. I'd like resolv.conf to update with dhcp returned data for DNS servers, but, for the time being, I'd like applications to talk to the upstream DNS servers until this issue is resolved."
1809438,2021-02-19 10:28:42 UTC,I seem to be affected by the same issue. I get regular DNS query time-outs coinciding with a lot of the following log messages (syslog):
1809438,2019-01-02 03:20:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809439,2018-12-21 11:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809439,2018-12-21 11:08:16 UTC,This issue looks like a bug for s390x in the kernel.
1809439,2018-12-24 03:11:47 UTC,"Verified with the test suite upstream, this issue still exist."
1809439,2019-01-22 10:44:34 UTC,"This issue has been addressed by Colin's commit:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=53ef6cf2cc35cbd13a16c363af05e22a0cbcbb75"
1809441,2019-10-31 02:51:09 UTC,2.6.7 release never went out. This fix was instead released in 2.6.8 - re-targeting this report.
1809441,2019-08-28 21:50:31 UTC,This is actually released as part of Juju 2.6.
1809441,2019-01-10 17:08:56 UTC,"> Unfortunately as different controllers could have differnet user backends/etc it's not in the scope to deal with the user/permission side during model migrations.
"
1809441,2019-01-11 02:35:43 UTC,"On 11/01/19 3:07 PM, James Troup wrote:

> If it can't be done automatically that's fine, but the current
> behaviour is dangerously misleading.
>
> Acceptable behaviour:
>
>  1) both user(s) and model are successfully migrated
>  2) model is migrated, user(s) are not and the operator is warned that
>     this the case
>  3) user(s) can not be migrated and so the model is not migrated and
>     the operator is told this with an option (--force-mumble) to
>     override
>
> Unacceptable behaviour:
>
>  1) what we do now
"
1809441,2019-01-11 02:36:56 UTC,Additional 2.5 milestone will be set as the work is picked up.
1809441,2019-01-10 14:38:28 UTC,"I'm not sure I agree it's expected behaviour. It certainly wasn't for me. I was migrating using the admin account in each case, but expected the user that had permissions to the model I was migrating to be migrated as part of the model migration. I understand that might not be possible in all cases, but could it not be attempted and warn in case of failure? Or at least be an option to migrate the user with the model, or even to migrate the user as a separate action (where migrating the model would suggest there's a user that had permissions to the model we were migrating from doesn't exist on the target controller)?"
1809441,2019-01-10 20:42:44 UTC,"I'm fairly sure that the model users are transferred with the model, so two controllers that use the same identity manager and the model access is controlled with the external users, all should be fine."
1809441,2019-01-08 16:40:24 UTC,Unfortunately as different controllers could have differnet user backends/etc it's not in the scope to deal with the user/permission side during model migrations. There's just no promises that we can keep there. It's expected behavior that if you migrate as different users that you'd have to reset up any access for users that are valid on the new home controller for a model after migration.
1809441,2019-01-11 02:07:11 UTC,Tim Penhey <email address hidden> writes:
1809443,2019-02-26 15:10:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809445,2018-12-21 22:24:33 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1809447,2018-12-24 12:08:51 UTC,"Hello, thank you for your commitment. Unfortunately I am not sure if that could be handled easily. Neutron server/agent is expanding from release to release. Performance might change between versions. I would leave that issue as open question. Maybe someone else will be able to share his insights related to performance here. Cheers!"
1809447,2019-01-03 14:03:57 UTC,"Do you see the same behavior on master or stable/rocky?  It could be different there especially given Ocata is quite old, plus any fix would need to be targeted at master first anyways."
1809447,2019-01-13 16:30:07 UTC,i have done the tests also on rocky and are better then ocata. First post updated with the new test.
1809447,2019-01-03 16:04:03 UTC,"I have tested it with devstack from ocata to rocky and there are no differences. Unfortunately i was not able to install mitaka with devstack.
For completeness i'll do the same test next week with rocky (ubuntu packages and same specs)."
1809452,2019-04-23 09:47:32 UTC,Can you still reproduce it with salt 2018.3.4~git20180207+dfsg1-1 in Ubuntu 19.04?
1809452,2018-12-21 12:42:15 UTC,One possible cause might be the tornado package itself.
1809452,2018-12-21 13:18:38 UTC,Having built and installed upstream packages (http://repo.saltstack.com/py3/ubuntu/18.04/amd64/latest/)
1809453,2019-09-28 04:17:20 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1809453,2019-07-29 09:48:29 UTC,What is your version of qemu? I understand you are running qemu on ubuntu.
1809454,2019-02-19 13:50:13 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1809454,2019-02-18 10:14:03 UTC,This bug was fixed in the package nova - 2:17.0.7-0ubuntu2
1809454,2019-02-19 13:47:57 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1809454,2019-02-19 13:48:02 UTC,"This bug was fixed in the package nova - 2:17.0.7-0ubuntu2~cloud0
---------------"
1809454,2019-02-19 13:49:14 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1809454,2019-02-19 13:49:16 UTC,"This bug was fixed in the package nova - 2:16.1.6-0ubuntu1~cloud1
---------------"
1809454,2019-10-29 18:19:10 UTC,This was fix-released in ocata via nova 2:15.1.5-0ubuntu1~cloud1.
1809454,2019-03-24 23:04:35 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1809454,2019-02-12 19:55:06 UTC,"This bug was fixed in the package nova - 2:18.0.3-0ubuntu2~cloud0
---------------"
1809454,2019-03-26 07:38:01 UTC,"Reviewed:  https://review.openstack.org/627012
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=779e58e97612d9fcb15d8a926fa8e9ddcf88feba
Submitter: Zuul
Branch:    stable/ocata"
1809454,2019-04-26 10:03:51 UTC,Released in 17.0.10.
1809454,2019-04-26 17:16:13 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1809454,2019-07-22 17:58:52 UTC,"For some reason this wasn't automatically marked ""Fix Released"" for upstream stable/pike. It's available in the 16.1.8 release for nova. https://opendev.org/openstack/nova/commit/779e58e97612d9fcb15d8a926fa8e9ddcf88feba"
1809454,2019-03-22 03:44:55 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1809454,2019-02-12 19:55:04 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1809454,2019-03-24 23:39:54 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1809454,2019-02-12 19:26:00 UTC,This bug was fixed in the package nova - 2:18.0.3-0ubuntu2
1809454,2018-12-21 13:48:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/626897"
1809454,2018-12-25 03:27:28 UTC,"Reviewed:  https://review.openstack.org/626897
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=47b7c4f3cc582bf463fd0c796df84736a0074f48
Submitter: Zuul
Branch:    master"
1809454,2019-02-12 19:26:14 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1809454,2019-01-02 12:53:15 UTC,"Reviewed:  https://review.openstack.org/627009
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f5d8ee1bfc3b7b9f1a25f85b42e207db0c9f4b04
Submitter: Zuul
Branch:    stable/rocky"
1809454,2019-01-06 13:18:04 UTC,"Reviewed:  https://review.openstack.org/627010
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=accef50f9648dc40f1a6f457f83f5359e9dd2a24
Submitter: Zuul
Branch:    stable/queens"
1809454,2019-01-07 20:46:33 UTC,"New packages have been uploaded to Ubuntu disco, cosmic and bionic with patches cherry-picked from upstream nova. cosmic and bionic are awaiting SRU review."
1809454,2019-01-07 23:10:07 UTC,This bug was fixed in the package nova - 2:19.0.0~b1~git2018120609.c9dca64fa6-0ubuntu2
1809454,2019-01-08 19:18:41 UTC,"Hello Corey, or anyone else affected,"
1809454,2019-01-08 19:27:51 UTC,"Hello Corey, or anyone else affected,"
1809454,2019-02-19 13:50:17 UTC,"This bug was fixed in the package nova - 2:15.1.5-0ubuntu1~cloud1
---------------"
1809454,2019-01-09 00:21:16 UTC,"Hello Corey, or anyone else affected,"
1809454,2019-01-09 00:18:31 UTC,"Hello Corey, or anyone else affected,"
1809454,2019-02-12 15:36:47 UTC,Verified on cosmic.
1809454,2019-02-12 19:20:20 UTC,Adding a bit more context.
1809454,2019-02-11 23:57:57 UTC,"The newton-proposed, ocata-proposed, pike-proposed, queens-proposed, bionic-proposed and rocky-proposed packages have all been tested."
1809454,2019-02-11 02:00:00 UTC,How do we go about getting this moving forward from cloud-archive:queens-proposed to stable so we can run this in production?
1809454,2019-02-05 18:09:53 UTC,"Reviewed:  https://review.openstack.org/627011
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a7e25aa3d2088e2726988c03e84b3b5ea47bfb7e
Submitter: Zuul
Branch:    stable/pike"
1809454,2019-01-09 04:28:43 UTC,"Hello Corey, or anyone else affected,"
1809454,2019-01-09 00:21:22 UTC,"Hello Corey, or anyone else affected,"
1809457,2019-04-05 07:53:42 UTC,"I'm not able to reproduce this currently. Can you let us know which version of the charm you're deploying, and with what constraints and config options?"
1809457,2019-04-05 09:07:39 UTC,Sorry about that - I submitted a change (which was subsequently landed) for the charm that seems to have fixed this.
1809459,2018-12-22 05:01:39 UTC,"https://github.com/paulgear/ntpmon/pull/3 is where this merge is being handled.  I've pushed an update and added some comments there, built a new charm and pushed to cs:~paulgear/telegraf, and started a CI run."
1809459,2019-03-15 06:57:26 UTC,"The upstream NTPmon changes have been merged into master.  I've built a new version of the telegraf charm and pushed it to cs:~te​legraf-charmers/tele​graf-35 (candidate channel).  But CI seems to be a bit borked at the moment, so I'm not ready to declare this fixed.  When it gets a successful CI run, I think we're good to go."
1809463,2019-09-19 12:07:24 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1809463,2019-01-07 09:19:14 UTC,"So the node was commissioned on Sep 17th, a time at which MAAS might have been on version 2.3. Here are the logs anyway :"
1809463,2018-12-21 14:40:36 UTC,"(Also, please mark it as New once the information has been attached)."
1809463,2018-12-21 14:39:59 UTC,"Another question, was this machine commissioned at the same time as others?"
1809463,2018-12-21 14:39:39 UTC,"Hi Junien,"
1809466,2018-12-21 15:31:14 UTC,Modif #1
1809469,2019-11-11 15:40:41 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1809469,2019-09-09 09:18:19 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.2 release.
1809469,2019-09-09 09:17:24 UTC,This issue was fixed in the openstack/kolla-ansible 6.2.2 release.
1809469,2019-07-18 00:37:38 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc2 release candidate.
1809469,2019-06-24 13:08:35 UTC,"Reviewed:  https://review.opendev.org/666088
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ec2aa48c1713187dcb4ebfc836e45b8cfe5329c4
Submitter: Zuul
Branch:    stable/queens"
1809469,2019-06-24 13:08:23 UTC,"Reviewed:  https://review.opendev.org/666093
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d66e95d1d96c9f5aee52740df53d6e784c7b8194
Submitter: Zuul
Branch:    stable/rocky"
1809469,2019-06-20 15:27:06 UTC,"Reviewed:  https://review.opendev.org/666090
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=8e627c1eef5e7ef047cd3860d162a0e2a800e5ab
Submitter: Zuul
Branch:    stable/stein"
1809469,2019-06-20 15:26:55 UTC,"Reviewed:  https://review.opendev.org/666086
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=1a6e9f7e927ebb3c2f021befc3630f4279dbceb1
Submitter: Zuul
Branch:    stable/stein"
1809469,2019-06-18 18:09:24 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/666095"
1809469,2019-06-24 13:08:45 UTC,"Reviewed:  https://review.opendev.org/666095
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d5cef35a7fbb8349ed6cbd5862b24caed52ff7a4
Submitter: Zuul
Branch:    stable/queens"
1809469,2019-06-18 18:04:12 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/666090"
1809469,2019-05-09 09:39:16 UTC,"So I believe the tokens Keystone hands out last 1 hour (not sure on that), and with three controllers the default behaviour is to rotate every 8 hours:"
1809469,2019-05-09 09:44:23 UTC,so token timeout is 1 day...
1809469,2019-05-09 09:46:47 UTC,"So looks like this is incorrect:
https://github.com/openstack/kolla-ansible/blob/2dd69e9140b1ce1bd248c5c09217fb3a6502a9fc/ansible/roles/keystone/templates/keystone.conf.j2#L37"
1809469,2019-06-18 18:06:47 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/666093"
1809469,2019-05-09 09:52:16 UTC,"Actually it is more complicated, due to:"
1809469,2019-05-16 09:28:43 UTC,"Change abandoned by John Garbutt (<email address hidden>) on branch: master
Review: https://review.opendev.org/657967"
1809469,2019-06-24 12:39:25 UTC,"Reviewed:  https://review.opendev.org/666087
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=c3e5ab0dc3b87c6ddae78a8f29d268ebe840638d
Submitter: Zuul
Branch:    stable/rocky"
1809469,2019-06-06 16:29:25 UTC,"Reviewed:  https://review.opendev.org/659619
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=25ac955a4e2645da29f8c7b807f0bac5afb43838
Submitter: Zuul
Branch:    master"
1809469,2019-06-06 16:33:11 UTC,"Reviewed:  https://review.opendev.org/659293
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=6c1442c385450004dd253f3f464fe4336194be99
Submitter: Zuul
Branch:    master"
1809469,2019-05-16 16:34:57 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/659619"
1809469,2019-06-18 18:02:31 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/666086"
1809469,2019-06-18 18:02:57 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/666088"
1809469,2019-06-18 18:02:44 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/666087"
1809470,2018-12-22 17:41:23 UTC,I have confirmed the same behavior in 2.5.
1809472,2018-12-21 18:22:54 UTC,The intent there was not to force a recalculate on un-dirtied suffixes every 11th replication cycle.
1809472,2018-12-22 10:33:38 UTC,"This bug i raised after the following scenerio in a production setup,"
1809474,2018-12-21 22:51:51 UTC,This would be really helpful.  The only way to find them now is to clean them up and then cycle through undo/redo watching for changes on screen.
1809474,2019-04-01 01:25:38 UTC,"I haven't moved these to DRC, but I have implemented a dry run when the dialog opens that then shows you all the clean-up items (and allows you to click on them like in the DRC window)."
1809474,2019-04-05 17:53:34 UTC,"Fixed in revision 87f303319cb252fc647da192695deffdd8a0157d
https://git.launchpad.net/kicad/patch/?id=87f303319cb252fc647da192695deffdd8a0157d"
1809475,2018-12-21 15:47:35 UTC,The problem is whether should we append the content when an existing .gitignore file is found.
1809477,2018-12-21 16:00:04 UTC,This change was made by a bot.
1809478,2019-01-15 10:03:07 UTC,"Reproduced my issue again on openstack, see attached logs/storage info. Issue is actually ""quota exceeded"" but I didn't figure this out until looking at the yaml format of `juju storage`. Nothing in the logs to indicate this was the underlying cause."
1809478,2019-01-15 10:01:56 UTC,"Machine log, unit log and output of juju storage --format yaml"
1809478,2019-01-11 01:38:23 UTC,"So turns out that AWS xen pv block devices do not have identifying hardware info from udev that we can use to match the volume request from Juju, so we need to fall back to matching on device name. It's not ideal but all we can do for now."
1809478,2019-01-08 10:19:25 UTC,Maybe it's related to the newish NVMe EBS instances?
1809478,2019-01-08 10:12:47 UTC,"So it looks like AWS is broken - Juju runs the udevadm command for each of the block devices it finds using lsblk. The udevadm command prints various attributes of the device which Juju needs to know, including WWN, device link etc. When I ssh'ed into an AWS instance running a deployed postgresq with storage, the /dev/xvdf device showed up when the EBS volume was create, but the udevadm output was virtually empty. Without this info, Juju cannot complete the storage setup. There's no issue when I tested on GCE - the udevadm output was fully populated."
1809478,2019-01-07 23:37:12 UTC,"The charm hook execution will block until all requested storage is attached. For block storage, this means that the machine agent on the worker node has to poll block devices using lsblk and report back what it sees to Juju - the storage provisioner will attempt to match the /dev/foo block device name with the storage request and thus mark the storage as attached. Juju pauses charm hook execution until this happens."
1809478,2019-01-07 22:05:27 UTC,"I'm able to deploy other charms just fine, only kafka seems to be getting stuck. It's not even getting to the install hook, so I don't think it's anything to do with the charm. I forced the log level on one of the stuck units to DEBUG (by editing agent.conf) and it looks like the resolver is stuck waiting for storage, see log snippet below."
1809478,2019-01-07 13:51:15 UTC,"""unit-postgresql-5"" cannot open api: unable to connect to API: dial
tcp 10.25.2.109:17070: i/o timeout"
1809478,2018-12-21 17:17:40 UTC,"I got an update-status hook error on a postgresql unit, seems caused by API connection issues? https://paste.ubuntu.com/p/vfz2pZHwjH/"
1809478,2018-12-21 16:46:23 UTC,"The ubuntu deploy continues.. it's been running over 30 min now, currently at ""agent installing"". https://paste.ubuntu.com/p/NSrM75tz83/"
1809478,2019-01-08 10:13:30 UTC,Note - the above was with 2.5 but there's no difference between 2.4.7 and 2.5 in this area.
1809478,2018-12-21 17:18:48 UTC,"The ubuntu deploy completed successfully and went to a ""ready"" state. So perhaps if I keep retrying deploys, they may eventually succeed."
1809483,2018-12-24 06:30:06 UTC,This change was made by a bot.
1809483,2019-03-22 02:53:26 UTC,"70:00.0 Network controller [0280]: Intel Corporation Device [8086:2526] (rev 29)
 Subsystem: Intel Corporation Device [8086:0014]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at de200000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi"
1809483,2020-07-03 06:25:54 UTC,This should no longer be an issue. Tried:
1809486,2019-01-03 10:10:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809486,2019-01-07 09:20:28 UTC,First of all I confirm that /usr/bin/mysql_plugin is owned:
1809486,2019-01-07 09:34:14 UTC,This sounds valid to me.
1809487,2019-06-18 04:17:39 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1809487,2019-04-18 23:40:00 UTC,"Hi everyone,
finally got the time to test your suggestions. Thank you very much for your help.
I installed the KiCAD 5.1 Release and I'm very happy with the outcome."
1809487,2018-12-26 21:13:18 UTC,"Does the issue happen if you run PCBNew in Legacy mode?  If that works fine, I'd try updating your graphics card drivers."
1809487,2018-12-27 18:25:05 UTC,I updated to the newest Driver:
1809487,2019-02-19 02:34:08 UTC,Hi Dave-
1809487,2019-02-19 02:34:56 UTC,One other thing to also try is to disable anti-alias settings in OpenGL.  This may partially resolve the issue for you
1809489,2018-12-21 18:50:05 UTC,"Review in progress for https://review.opencontrail.org/48342
Submitter: Paul Carver (<email address hidden>)"
1809492,2019-01-07 21:02:09 UTC,"ubuntu has nocache 1.1 version in repo https://packages.ubuntu.com/disco/nocache
and nocache 1.0 don't work on ubuntu 18.10 as there is deadlock in combination of nocache 1.0 and libc 2.28 on ubuntu 18.10
So it make sense to release 1.1 as fixed version for ubuntu 18.10 (working version)"
1809492,2018-12-22 21:04:40 UTC,more info here https://github.com/Feh/nocache/issues/34
1809492,2019-01-12 18:30:33 UTC,Can you plz upgrade nocache to 1.1 on ubuntu 18.10 ?
1809492,2018-12-28 23:59:22 UTC,"can you create fix package for nocache with
fix from
https://github.com/Feh/nocache/issues/34"
1809496,2018-12-21 20:00:15 UTC,This change was made by a bot.
1809500,2018-12-21 21:17:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809500,2018-12-21 21:23:50 UTC,GMail crashes:
1809500,2018-12-22 22:03:49 UTC,"After further research, this seems to actually not be Ruby version specific - because I purged my Ruby 2.5.1 that comes with Ubuntu 18.10 and installed 2.5.3 and 2.4.5 via ([ruby-install](https://github.com/postmodern/ruby-install) and tried both versions - and they both show up with the bug. So, my conclusion must be that there is something else wrong in 18.10, perhaps not Ruby specific at all (but still very odd that it works with Python and openssl directly)."
1809513,2020-03-07 10:52:10 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1809514,2020-09-21 12:06:41 UTC,OOPS! Meant to write...
1809514,2020-09-21 12:05:37 UTC,Closing because INVALID.
1809519,2018-12-22 03:17:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627028"
1809522,2020-03-19 21:10:46 UTC,Closing because INVALID.
1809538,2018-12-22 19:25:50 UTC,"> On MX-17 (debian)
"
1809538,2018-12-24 20:28:14 UTC,"No response as yet to a very, very simple request."
1809541,2018-12-22 14:09:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627038"
1809546,2018-12-22 15:08:51 UTC,Adding the link script.
1809546,2019-01-04 14:32:43 UTC,"Yes, our PL011 implementation assumes that you only ever access the 32-bit registers with full width 32-bit word reads and writes. Don't try to do byte accesses to them. The PL011 data sheet doesn't specifically say that partial-width accesses to registers are permitted, so I think that trying to access offset 0x39 falls under the general note in section 3.1 that attempting to access reserved or unused address locations can result in unpredictable behaviour."
1809546,2019-01-04 16:29:54 UTC,Thanks for the response.
1809547,2018-12-22 23:28:43 UTC,"Hi,"
1809549,2019-01-03 01:25:17 UTC,"Hello, the attached logs look like there was an attempt to upgrade from 14.04 LTS to 16.04 LTS that might not have gone well."
1809550,2018-12-22 19:02:54 UTC,"I guess that Atril cannot handle several levels of ""ul"" lists in the toc.xhtml file, structure is like this:"
1809552,2019-01-07 08:56:24 UTC,Does the problem also occur in Wayland sessions?
1809552,2019-03-09 04:17:28 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1809552,2018-12-22 19:33:04 UTC,"I should specify, the specific model of Macbook Pro which I am using is the mid-2012 15"" version (version 10,1)"
1809552,2019-01-07 08:55:33 UTC,Your XorgLog seems to show that you do have two different GPU drivers both connected to the same physical screen (or two identical screens):
1809553,2020-07-16 17:17:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal:"
1809556,2019-03-30 09:29:48 UTC,I have the same problem.
1809556,2019-02-13 13:59:39 UTC,"There is a discussion about this topic, I followed the recommendation there but my system freezed again, so purged zram now."
1809556,2019-02-13 12:33:27 UTC,"I think the above link will not gonna help because it's related to computer freezing when RAM is full, my computer wasn't with high usage of RAM on the freeze moment, it was using something about 50%"
1809556,2019-02-13 12:15:41 UTC,"Maybe this helps, there are a couple of suggestions:"
1809556,2018-12-22 21:44:19 UTC,As the computer crashes I got no errors on the syslog except one time when I got the error attached on crash.txt
1809556,2018-12-22 21:41:15 UTC,https://launchpadlibrarian.net/402582142/WifiSyslog.txt
1809556,2018-12-22 21:39:21 UTC,https://launchpadlibrarian.net/402582128/ProcModules.txt
1809556,2018-12-22 21:39:04 UTC,https://launchpadlibrarian.net/402582127/ProcInterrupts.txt
1809556,2018-12-22 21:38:44 UTC,https://launchpadlibrarian.net/402582121/ProcCpuinfo.txt
1809556,2018-12-22 21:38:38 UTC,https://launchpadlibrarian.net/402582096/Lspci.txt
1809556,2019-01-25 10:20:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809556,2018-12-22 21:37:36 UTC,"ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: typer 2994 F.... pulseaudio
 /dev/snd/pcmC0D0p: typer 2994 F...m pulseaudio
CurrentDesktop: LXQt
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-20 (2 days ago)
InstallationMedia: Lubuntu 18.10 ""Cosmic Cuttlefish"" - Release amd64 (20181017.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
 Bus 001 Device 002: ID 046d:c083 Logitech, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B360M-D3H
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=ba2e86e4-48ce-47f3-a413-98536fe6febd ro quiet splash resume=UUID=5b571422-2d63-4044-88be-ecd5e66732d8 vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-12-generic N/A
 linux-backports-modules-4.18.0-12-generic N/A
 linux-firmware 1.175.1
RfKill:"
1809558,2018-12-22 21:58:28 UTC,Input test.csv file is attached.
1809561,2019-02-23 00:32:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809564,2019-10-26 17:15:10 UTC,Fixed by https://github.com/ubuntu/yaru/pull/1547
1809566,2020-03-07 10:50:31 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1809572,2019-10-27 20:16:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809577,2018-12-29 09:46:04 UTC,"Hi,"
1809579,2020-01-23 20:24:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809580,2019-05-16 12:51:44 UTC,"Fixed in revision 0eb8f92c690f4480e14b066536aa7483e4244f98
https://git.launchpad.net/kicad/patch/?id=0eb8f92c690f4480e14b066536aa7483e4244f98"
1809580,2018-12-24 10:11:51 UTC,"I think this could be done as a ""skip"" parameter."
1809580,2019-02-11 10:44:31 UTC,"I see you already sent in a lot of updates/rework for the array tool:
https://lists.launchpad.net/kicad-developers/msg39213.html"
1809580,2018-12-26 23:11:07 UTC,"@Sebastian: I see, yes, this is not currently possible to do in one go."
1809580,2018-12-24 11:54:15 UTC,This is true John.
1809580,2019-01-29 12:26:03 UTC,Note: A patch for this was submitted in 2015 and died on the mailing list: https://lists.launchpad.net/kicad-developers/msg19326.html
1809584,2018-12-23 15:24:21 UTC,"I have LANG=""en_US"" set"
1809590,2018-12-23 19:35:07 UTC,"I'd suggest going to the Canon web page for the Pixma MG3650, download & install their drive for it."
1809590,2018-12-23 20:43:53 UTC,"Yrs, I already had them installed. It does not depend on the drivers, but only and exclusively from that module."
1809593,2018-12-23 18:30:04 UTC,This change was made by a bot.
1809594,2019-02-21 01:47:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809594,2019-07-04 09:01:11 UTC,"Anything we can do to help resolve this issue ?
I am able to replicate on my desktop, and will assist anyone who wants to fix this."
1809595,2018-12-31 01:35:56 UTC,"Mixxx should normally send artist and title via shoutcast.
Which requirements does citrus3 have?
Can you try an other server to verify that it is working?
This one works for me:
http://stream.4vip2.com/"
1809595,2020-07-29 04:17:36 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1809595,2018-12-23 22:44:14 UTC, I am using Mixxx 2.1.5 on Windows 10
1809595,2018-12-23 20:30:57 UTC,"Please describe your setup, including the software versions used.
On which OS are you?"
1809597,2020-03-07 10:47:51 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1809605,2019-07-22 04:00:03 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1809607,2019-07-18 14:50:17 UTC,"Please could you clarify:
* Does extended asm apply to naked functions?
* Should the caller of naked function backup the registers?"
1809607,2019-07-15 12:05:46 UTC,See https://gcc.gnu.org/PR85593
1809607,2019-07-15 08:49:26 UTC,"Hi,"
1809607,2019-07-15 11:50:07 UTC,"I think it was actually a genuine bug, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85593
This ticket predates the fix, but the fix was included in the latest release (2019-q3-update)."
1809607,2019-07-15 10:57:01 UTC,"No this isn't. If the register isn't in the clobber list or the output list, there's no way the compiler can divine what's happening here.  See documentation here for more - https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html"
1809607,2019-05-29 11:20:05 UTC,yes
1809607,2019-05-29 08:14:04 UTC,The referenced code doesn't include the modified register in the clobber list of the inline asm. Does adding r1 there fix the problem?
1809607,2019-07-15 12:05:31 UTC,ACtually I've just been told I'm wrong and I'd misunderstood this.
1809607,2018-12-23 20:15:40 UTC,Ich bin bis 07.01. nicht im Haus und kann Ihre Nachricht daher leider nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
1809612,2019-12-22 13:42:06 UTC,This has been fixed in opendkim version 2.11.0~alpha-7 (Ubuntu 18.04).
1809615,2019-07-30 11:35:24 UTC,Is this still an issue? Can you explain in detail how this relates to devstack?
1809615,2019-07-30 14:25:23 UTC,Hello:
1809623,2018-12-24 03:33:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627096"
1809623,2019-02-11 13:54:57 UTC,This sounds like more of an opinion than a bug.
1809624,2018-12-24 03:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809624,2019-03-26 09:28:31 UTC,This also affects the 4.18 kernels (cosmic/linux and bionic/linux-hwe).
1809630,2018-12-25 09:17:34 UTC,This seccomp test passed on Cosmic AMD64.
1809630,2018-12-24 04:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809630,2018-12-25 03:19:16 UTC,"With Cosmic s390x KVM, 6 failures reported in our source tree and in the upstream source tree:
[ RUN      ] TRACE_syscall.ptrace_syscall_dropped
TRACE_syscall.ptrace_syscall_dropped: Test failed at step #127
[     FAIL ] TRACE_syscall.ptrace_syscall_dropped
[ RUN      ] TRACE_syscall.syscall_dropped
TRACE_syscall.syscall_dropped: Test failed at step #2
[     FAIL ] TRACE_syscall.syscall_dropped
[ RUN      ] TRACE_syscall.skip_after_RET_TRACE
seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (728)
seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12
[     FAIL ] TRACE_syscall.skip_after_RET_TRACE
[ RUN      ] TRACE_syscall.kill_after_RET_TRACE
TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0)
[     FAIL ] TRACE_syscall.kill_after_RET_TRACE
[ RUN      ] TRACE_syscall.skip_after_ptrace
seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (728)
seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_ptrace: Test failed at step #15
[     FAIL ] TRACE_syscall.skip_after_ptrace
[ RUN      ] TRACE_syscall.kill_after_ptrace
TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0)
[     FAIL ] TRACE_syscall.kill_after_ptrace"
1809636,2019-01-07 08:20:47 UTC,Thanks for the bug report. Please could you provide the juju log from the vault unit(s) ?
1809636,2019-01-12 19:38:50 UTC,We were deploying charmed Kubernetes in high-availability mode.
1809639,2018-12-24 07:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809639,2020-07-31 10:17:14 UTC,"Oh Sorry Frank,
I misread the bug title, I thought this was for KVM kernel."
1809639,2020-07-31 08:30:11 UTC,This is not failing anymore on KVM kernels.
1809639,2018-12-25 03:10:23 UTC,"For Cosmic s390x KVM, it's:
[12] ftrace - function glob filters	[FAIL]
[35] event trigger - test inter-event combined histogram trigger	[FAIL]
[44] event trigger - test histogram trigger	[FAIL]
[49] trace_marker trigger - test snapshot trigger	[FAIL]
[64] (instance)  event trigger - test histogram trigger	[FAIL]"
1809640,2019-09-12 14:15:39 UTC,Does this bug still occur with latest code? If yes - please upload new logs (Horizon logs from /var/log/kolla/horizon/* and docker logs horizon)
1809640,2019-11-12 04:18:28 UTC,[Expired for kolla because there has been no activity for 60 days.]
1809656,2018-12-25 22:08:39 UTC,apport information
1809656,2018-12-25 22:08:34 UTC,apport information
1809656,2018-12-25 22:08:31 UTC,apport information
1809656,2018-12-25 22:08:38 UTC,apport information
1809656,2019-01-07 09:08:51 UTC,The Xwayland binary comes from source package 'xorg-server' so reassigning to that.
1809656,2018-12-25 22:08:48 UTC,apport information
1809656,2018-12-25 22:08:36 UTC,apport information
1809656,2018-12-25 22:08:46 UTC,apport information
1809656,2018-12-25 22:08:44 UTC,apport information
1809656,2018-12-25 22:08:47 UTC,apport information
1809656,2018-12-25 22:08:42 UTC,apport information
1809656,2018-12-25 22:08:40 UTC,apport information
1809656,2018-12-25 22:08:43 UTC,apport information
1809657,2018-12-24 13:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809657,2018-12-24 21:34:48 UTC,"I ran update-manager in the terminal and made it crash as I mentioned, however no useful input was shown in terminal :/ any idea?"
1809659,2019-08-26 18:54:28 UTC,This should be solved in
1809665,2020-07-12 13:07:59 UTC,"> This happened to me as well, but I managed to find a solution, if I ban the xpad driver through modprobe.d, then the problem disappear.
"
1809665,2020-07-12 12:50:02 UTC,"This happened to me as well, but I managed to find a solution, if I ban the xpad driver through modprobe.d, then the problem disappear."
1809665,2019-01-02 15:09:46 UTC,So! These are the options and respective logs; they still don't make the controller work - it doesn't work at all.
1809665,2019-01-02 10:53:57 UTC,"Do you get a different behavior if you use ""-device usb-ehci"" or ""-device nec-usb-xhci"" instead of the ""-usb"" parameter?"
1809675,2019-01-03 17:12:15 UTC,"Update: Actually, the history is produced and shown in a separate 'History' tab. But finding that tab is not obvious! And if you activate the History tab and request history, again Eclipse jumps to the (not-helpful) console tab. Behavior should be: 1) run the history and then 2) activate the History tab!"
1809676,2020-05-05 04:14:05 UTC,"@Mark thanks for the fix, we've all been waiting for this one :-D
Do you have an idea what version this fix will come out in?"
1809676,2020-05-05 07:42:11 UTC,"Inkscape 1.0 has just been released. If the issue still occurs, please report it on inkscape.org/report/"
1809676,2020-04-02 16:31:43 UTC,"I have the same when I simply press Ctrl+Shift+P to attempt to open preferences. I never go there so I don't know when this started, but I know I haven't updated inkscape in a longer time than that, and I update Ubuntu 18.04 LTS regularly. My version is identical to OP."
1809676,2018-12-29 13:17:49 UTC,I couldn't reproduce this with locally compiled versions of both the 0.92.x branch and the master branch. What I tried:
1809676,2019-04-12 18:32:29 UTC,"Closing because bug is fixed in 1.0alpha (331007d, 2019-04-11)"
1809676,2019-03-11 07:06:30 UTC,Can reproduce in Inkscape 0.92.4 on openSUSE TW 20190301.
1809676,2019-01-19 14:49:44 UTC,"Tested on Ubuntu 18.04.1, with empty config before every try: (rm -r ~/.config/inkscape/)."
1809676,2018-12-27 15:10:35 UTC,Confirmed on stock current Ubuntu + Inkscape installed by GUI software installer.
1809676,2018-12-24 22:26:03 UTC,"not reproduced on Windows 10, Inkscape 0.92+devel (44a3c91, 2018-12-16)"
1809676,2018-12-24 22:19:22 UTC,"confirmed on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)"
1809676,2019-04-16 01:26:46 UTC,The fix is not in a stable release of Inkscape yet.
1809680,2018-12-27 15:56:14 UTC,"Review in progress for https://review.opencontrail.org/48361
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2019-01-03 21:58:45 UTC,"Review in progress for https://review.opencontrail.org/48363
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2018-12-26 12:41:09 UTC,"Review in progress for https://review.opencontrail.org/48363
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2018-12-24 21:57:04 UTC,"Review in progress for https://review.opencontrail.org/48361
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2018-12-24 22:57:57 UTC,"Review in progress for https://review.opencontrail.org/48362
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2018-12-24 22:56:59 UTC,"Review in progress for https://review.opencontrail.org/48363
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2018-12-24 22:26:59 UTC,"Review in progress for https://review.opencontrail.org/48362
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2018-12-24 22:24:44 UTC,"Review in progress for https://review.opencontrail.org/48361
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2018-12-24 21:59:40 UTC,"Review in progress for https://review.opencontrail.org/48362
Submitter: Michal Clapinski (<email address hidden>)"
1809680,2018-12-26 12:37:38 UTC,"Review in progress for https://review.opencontrail.org/48361
Submitter: Michal Clapinski (<email address hidden>)"
1809682,2020-08-10 13:03:35 UTC,"Hum, looks like systemd used your sysv scripts (perhaps because of upgrades) and it had issues because they had no runlevels by default... and your workaround was to use the systemd unit, which is the one used by default..."
1809682,2020-09-28 12:05:16 UTC,"The verification of the Stable Release Update for corosync-qdevice has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1809682,2020-09-28 12:05:14 UTC,This bug was fixed in the package corosync-qdevice - 3.0.0-4ubuntu1.1
1809682,2020-09-28 12:04:58 UTC,"Please be sure to include the version number of the tested package, as we should not be releasing updates without this information provided!"
1809682,2020-09-24 17:38:08 UTC,All good with published package. Good to go.
1809682,2020-09-09 16:45:36 UTC,"Hello Don, or anyone else affected,"
1809682,2020-09-08 17:34:15 UTC,Fixed in Debian:
1809682,2020-08-10 08:53:52 UTC,workaround for now:
1809682,2019-02-08 12:21:52 UTC,"The attachment ""bionic-fix-for-corosync-qdevice-lp1809682.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1809682,2020-07-11 03:22:47 UTC,In groovy:
1809682,2019-01-09 13:48:54 UTC,"Bug confirmed. It's an odd looking initscript, as it does not have the usual actions in itself."
1809682,2019-02-08 08:45:58 UTC,"Attached debdiff, based on corosync (2.4.3-0ubuntu1) for Ubuntu 18.04/bionic removes the debian/corosync-qdevice.init script from the package. If already installed previously, it removes the /etc/init.d/corosync-qdevice script through the corosync-qdevice.postinst script upon package upgrade."
1809682,2020-08-10 08:51:04 UTC,For me it's not fixed in focal:
1809682,2019-04-20 19:06:49 UTC,"Hello Don, thank you for your work on this!"
1809682,2018-12-24 23:57:11 UTC,"I forgot to mention, this bug report concerns:
Ubuntu 18.04
Package: corosync-qdevice
Version: 2.4.3-0ubuntu1"
1809682,2020-02-27 21:40:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809682,2020-03-20 05:01:35 UTC,"I'm closing up corosync / corosync-* bugs for Focal and will check sysv script tomorrow. For now, I can say that:"
1809682,2020-03-20 04:58:02 UTC,"Hello Bert,"
1809682,2019-07-08 14:47:25 UTC,"Actually removing the sysv script is not an acceptable fix for this error. I mean, it might come to a day where we will disable all sysv inits, but, for now, they are called by systemd through systemd generator mechanism (https://www.freedesktop.org/software/systemd/man/systemd-sysv-generator.html) and the fix for this bug is:"
1809682,2020-02-27 23:31:29 UTC,"Just as a side note, I'm not sure why sysvinit script is provided at all. The daemon seems to work just fine with the included systemd config file in /lib/systemd/system/corosync-qdevice.service. Unless there's a compelling reason to keep the sysv init script I'd ditch it, if only to cut on the potential for confusion."
1809687,2019-01-02 22:11:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809688,2019-02-05 19:47:41 UTC,moved form https://bugs.launchpad.net/yade/+bug/1809688 to https://gitlab.com/yade-dev/trunk/issues/46
1809692,2019-01-21 11:33:12 UTC,"I have tested several days the firefox and also snap package of chromium
and they both don't show that problem."
1809692,2019-03-23 04:17:41 UTC,[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]
1809692,2019-01-08 02:36:56 UTC,"Thanks. That's either a bug in the web browser, graphics driver, or even in the web page."
1809692,2019-01-07 16:08:58 UTC,Thanks!
1809692,2019-01-07 09:17:09 UTC,Can you please attach a screenshot or photo of the problem?
1809692,2019-01-09 10:47:11 UTC,"Can you confirm you're seeing these issues only in chrome/chromium, not other apps (I'm particularly interested in other browsers, such as firefox)?"
1809692,2019-01-08 10:06:53 UTC,"Yes, they both have the same issue."
1809693,2018-12-27 14:03:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627532"
1809693,2019-01-22 08:13:21 UTC,I have met this problem too.
1809693,2019-02-12 12:43:30 UTC,"I found a way to reproduce this bug in all_in_one environment：
1) Make sure the nova-conductor and nova-compute services are running on the same node.
2) Delete nova-conductor service.
    openstack compute service delete <nova-conductor service id>
3) Delete nova-compute service.
    openstack compute service delete <nova-compute service id>"
1809693,2019-12-30 22:04:55 UTC,"For those experiencing this during a situation where you've re-deployed a node and it has a new hostname (FQDN vs short hostname), you can remove the old service record by updating /etc/nova/nova.conf to reflect the old short hostname, restart the nova-compute service, delete the openstack compute service entry, and then reset the nova.conf entry back to the FQDN."
1809693,2020-09-11 11:04:17 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/627532
Reason: This change was handled (inadvertently) with I8403a841f21a624a546ae5f26bb9ba19318ece6a"
1809701,2018-12-25 05:30:07 UTC,This change was made by a bot.
1809702,2018-12-27 17:52:26 UTC,"Since the project_id parameter is stored in the DB while creating the group, I wouldn't consider this as a bug, rather an API response change.
I've proposed the blueprint[1], spec[2] and patch[3] here."
1809704,2020-01-03 10:57:51 UTC,https://lists.ubuntu.com/archives/kernel-team/2020-January/106590.html
1809704,2018-12-25 07:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809704,2019-06-12 03:30:09 UTC,"C/D:
  * dff6d2ae56d0056261e2f7b19c4b96b86b893cd8
X/B:
  * 1f0ea95853bd55a1812f2903b2f776853069f21f
  * dff6d2ae56d0056261e2f7b19c4b96b86b893cd8"
1809704,2019-09-18 12:49:52 UTC,"This patchset will need the test framework to land first (bug 1812352)
otherwise it will fail on ARM64, as it will skip this test with a non-zero return code (with 4 in commit 1f0ea9585)"
1809704,2020-02-17 10:36:02 UTC,This bug was fixed in the package linux - 4.15.0-88.88
1809704,2020-02-03 23:12:32 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1809704,2018-12-25 09:02:40 UTC,https://lkml.org/lkml/2018/12/25/21
1809704,2020-01-27 12:13:59 UTC,This bug was fixed in the package linux - 4.4.0-173.203
1809704,2020-01-13 11:23:55 UTC,Verified with Disco in proposed.
1809704,2020-01-10 18:02:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1809704,2020-01-09 16:09:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1809704,2020-01-27 13:21:23 UTC,This bug was fixed in the package linux - 5.0.0-40.44
1809704,2020-01-14 06:34:43 UTC,"Verified with Xenial in proposed
$ uname -a
Linux michael 4.4.0-172-generic #202-Ubuntu SMP Wed Jan 8 21:56:36 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux"
1809707,2018-12-25 07:37:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627255"
1809707,2018-12-26 03:41:54 UTC,"Change abandoned by wanghao (<email address hidden>) on branch: master
Review: https://review.openstack.org/627255"
1809707,2019-01-02 07:22:15 UTC,Now this bug will be fixed in: https://review.openstack.org/#/c/627169/
1809708,2018-12-25 07:15:13 UTC,Discussion held at https://forum.snapcraft.io/t/bug-1809708-allow-snaps-to-query-interface-connection-status-directly-from-snapd/9147
1809708,2019-09-06 12:54:17 UTC,I agree some way of interrogating snapctl will be useful. Thank you for the report.
1809708,2019-09-25 21:58:07 UTC,In Paris we agreed that this would be `snapctl is-connected <plug-name>` (or slot-name)
1809708,2020-01-17 11:42:31 UTC,"Implemented with https://github.com/snapcore/snapd/pull/7771, should become available with snapd 2.43."
1809709,2019-01-30 11:07:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809712,2019-01-15 01:47:34 UTC,"If you're using a Xorg session (the default one named ""Ubuntu"") then the mouse pointer is moved by xorg-server independently of gnome-shell. This means that if the mouse pointer is frozen then it's either Xorg or the kernel that's freezing."
1809712,2019-04-16 04:19:08 UTC,These look most relevant:
1809714,2018-12-25 08:18:53 UTC,mixxx-2.2.0-win32.exe on a Win10 64 bit is also effected.
1809714,2019-04-24 22:10:42 UTC,mixxx-2.2.1-win32.exe on Win10 64 bit is also effected.
1809714,2019-12-09 22:24:34 UTC,"I cannot confirm this any more with:
https://downloads.mixxx.org/mixxx-2.2.3/mixxx-2.2.3-win32.exe"
1809719,2019-03-29 01:26:11 UTC,This issue was fixed in the openstack/zaqar-tempest-plugin 0.2.0 release.
1809729,2018-12-25 11:36:03 UTC,I think this is possibly a Deja Dup bug (so I used `ubuntu-bug deja-dup`) but I've marked it as also affecting snappy for now because it's an interaction bug so might be snappy that needs to be fixed rather than Deja Dup.
1809729,2019-10-15 10:47:56 UTC,"I suspect this is caused by `udevadm trigger` and `udevadm settle` that snapd invokes, for some snaps, depending on how they are made, when they are removed."
1809733,2018-12-25 13:31:03 UTC,This description doesn't do an effective job of explaining why you've marked this as a suspected security vulnerability.
1809733,2019-05-19 04:17:55 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1809733,2019-02-19 13:28:24 UTC,I agree with Jeremy. This doesn't really sound like a security vulnerability. Mind updating this bug? It would also make it easier for other contributors to look at this and help you fix the issue.
1809737,2020-09-12 15:37:49 UTC,Never mind - I figured out how to recompile the source Onboard package for Debian 10 and was able to incorporate sonald's (yinshuiboy) patch (see post #8) into updated .deb installation files.  I have zipped this updated version and it is attached for anyone who may find it useful.  Thanks!
1809737,2020-09-11 15:18:51 UTC,"Hi Cagnulein - thank you so much for making this patch!  I am having trouble installing it however on MX Linux 19.2, which is based on Debian 10. Your file name says your patch is for Onboard version 1.3.1-5, however when you unzip the file the version of Onboard contained within is 1.4.1-5.  I am trying to install Onboard 1.4.1-5 and your .deb files onto my Debian 10 Buster system, but it won't let me install any version of Onboard newer than 1.4.1-4.  How did you install your patched version to your Debian 10 system?  Thank you!"
1809737,2020-07-06 14:47:59 UTC,i created a debian 10 package with this patch. I hope it could be useful to someone
1809737,2020-07-06 13:33:44 UTC,This bug is happening on Debian 10 too.
1809737,2020-01-14 12:07:48 UTC,This bug is happening on Ubuntu Focal Daily too.
1809737,2019-11-21 19:23:03 UTC,"Hello,"
1809737,2019-11-08 01:21:24 UTC,"Is there a packaged version available with the fix for this bug? I'll have one problematic machine for a few days so I can test. However, it is an Intel Atom netbook, unlikely to be successful building onboard directly on it."
1809737,2019-11-11 09:04:52 UTC,"thanks for the feedback, I'll test and try to fix it later"
1809737,2019-11-08 20:14:22 UTC,I did a build applying the patch (fortunately no GTK 3 build was required) and I was testing with one offending netbook.
1809737,2019-10-24 11:59:13 UTC,"I don't know where to submit either, it's a pity. hope someone may merge the fix."
1809737,2019-10-21 01:40:43 UTC,"daniel,"
1809737,2019-03-04 17:08:38 UTC,"I have the same problem. It happens when a character from outside of current layout is chosen. For instance I set `setxkbmap -layout pl`. When choosing ""ć"" from popup (a character that belongs to ""pl"" layout) everything is fine. The character gets into text. But choosing something else causes Fluxbox (1.3.7) to segfault (corrupted stack?) in standard library:"
1809737,2019-04-10 13:09:46 UTC,I can reproduce too.
1809737,2019-10-21 02:18:04 UTC,"Oops, sorry. I was expecting a Xorg fix since that's what's crashing, and probably should still get its own fix."
1809737,2019-04-11 15:37:59 UTC,"The Xserver segfault so likely an issue there, I reported it upstream on https://gitlab.freedesktop.org/xorg/xserver/issues/679"
1809737,2019-04-12 01:08:40 UTC,"Although this bug was reported against Fedora, it sounds like Seb has reproduced it with Ubuntu 19.04."
1809737,2019-10-16 12:27:54 UTC,"The attachment ""0001-fix-handle-map-keysym-correctly.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1809737,2019-04-23 09:26:53 UTC,Does anyone have a workaround?
1809737,2019-10-17 02:41:39 UTC,"sonald,"
1809737,2019-04-22 11:19:43 UTC,Just a friendly bump.
1809737,2019-08-28 01:56:40 UTC,Stack trace with debug symbols from bionic here:
1809737,2019-10-16 08:29:38 UTC,"I have a fix, which I've tested on Deepin. I think the main reason is that ChangeMap request needs more info than provided."
1809748,2019-06-25 08:44:21 UTC,"It is yet unclear if there is an issue in the userspace tools, hence I made the sibling bug a dup and added the tools as a task here marked as incomplete for now."
1809748,2019-01-02 07:57:40 UTC,hint if testing this - add module_blacklist=bcache to your kernel boot line to boot and reset the metadata :)
1809748,2018-12-25 21:35:01 UTC,after doing a wipefs on the cache drive the BUG still occured; wipefs's the backing drive corrected that. I haven't yet tried wiping just the backing drive.
1809748,2018-12-25 21:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809748,2018-12-25 21:25:01 UTC,"cache superblock info - sb.magic		ok
sb.first_sector		8 [match]
sb.csum			5A3217E583DB5B86 [match]
sb.version		0 [cache device]"
1809749,2018-12-26 00:21:52 UTC,"The attachment ""Bugfix"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1809750,2018-12-25 21:48:03 UTC,i wish i had stuck with windows now tbh
1809750,2018-12-25 21:46:58 UTC,unable to reinstall.
1809757,2018-12-26 02:30:06 UTC,This change was made by a bot.
1809780,2019-04-26 21:07:44 UTC,"Hi,"
1809780,2019-06-26 04:17:21 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1809788,2019-07-30 01:28:50 UTC,"Hi Marco,"
1809788,2019-07-30 01:08:53 UTC,"Gold Star,"
1809788,2019-07-30 01:07:57 UTC,I booted the wrong iso. 19.10 daily is indeed fixed. Sorry for the confusion.
1809788,2019-07-30 00:52:41 UTC,"I don't think ""the bug"" is fixed (It looks that way because the dialog shows only a single line)"
1809788,2019-07-30 00:30:38 UTC,"Fixed, proof: https://i.imgur.com/4gFckd0.png"
1809788,2019-07-02 18:10:46 UTC,"Hello Yuan-Chen, or anyone else affected,"
1809788,2019-06-01 02:36:03 UTC," apt-cache policy gnome-shell
gnome-shell:
  Installato: 3.28.4-0ubuntu18.04.1
  Candidato:  3.28.4-0ubuntu18.04.1
  Tabella versione:
 *** 3.28.4-0ubuntu18.04.1 100"
1809788,2019-06-06 09:33:24 UTC,This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.1
1809788,2019-07-31 16:34:40 UTC,This bug was fixed in the package gnome-shell - 3.32.2-2ubuntu1~ubuntu19.04.1
1809788,2019-06-06 09:33:45 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1809788,2019-05-07 17:17:55 UTC,"I'm going to upload this to bionic before it's fixed in disco/eoan. There we're giving upstream a couple of days to release 3.32.2 which will contain this. SRU person, If you happen to review this before then, hope that's OK. :-)"
1809788,2019-01-17 05:07:03 UTC,can't be reproduced in 18.10.
1809788,2019-01-17 09:54:38 UTC,"that looks similar to bug #1721908 , unsure what commit fixed it if it's resolved in 18.10 though"
1809788,2019-05-21 20:24:48 UTC,This bug was fixed in the package gnome-shell - 3.32.2-1ubuntu1
1809788,2019-01-17 10:22:24 UTC,Added to Trello: https://trello.com/c/oCjHLjTB/190-bug1809788-bionic-tbt-authentication-message-will-be-cut-from-the-dialog-box
1809788,2019-01-18 11:06:16 UTC,"Testing on current 3.30 version in disco it doesn't seems to be fixed to me, can you make a screenshot showing how it's like for your on 18.10?"
1809788,2019-01-25 00:47:09 UTC,Can anyone please point out the command to simulate the same issue to happen?
1809788,2019-05-28 21:40:06 UTC,"Hello Yuan-Chen, or anyone else affected,"
1809788,2019-04-30 18:45:37 UTC,"Yeah, disco isn't fixed either here."
1809788,2019-05-01 01:39:19 UTC,Tracking upstream in https://gitlab.gnome.org/GNOME/gnome-shell/issues/922
1809788,2019-05-01 01:41:37 UTC,I can't see any history of a fix. But it's only reported in 3.28 here and 3.30 upstream...?
1809788,2019-05-01 01:44:38 UTC,"I would say remove Yaru here. The theme can't directly control whether the dialog is too small and needs wrapping. Although it can control the dialog size indirectly with some tweaks, but doing that would be a hack."
1809788,2019-01-25 08:47:10 UTC,"@Marco, Laney pointed out the other day than using 'boltctl enroll foo' was enough without needing the hw"
1809788,2019-04-30 18:48:00 UTC,"Ok, this is somewhat theme related.
See: https://imgur.com/a/SSsYBfO"
1809799,2019-09-16 13:01:55 UTC,"i believe this could be that the ppa-extras file simply needs to be populated with the correct PPA, if it has changed"
1809799,2019-10-23 09:01:11 UTC,We have the ppa-extras updated.
1809802,2019-02-22 14:21:13 UTC,This issue was fixed in the openstack/telemetry-tempest-plugin 0.2.0 release.
1809802,2018-12-26 12:33:38 UTC,"Fix Proposed to branch: master
Review: https://review.openstack.org/#/c/627401/"
1809803,2019-01-03 01:56:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809815,2019-01-22 09:33:30 UTC,"Thank you for your bug report, what Ubuntu version and desktop environement/session do you use?"
1809815,2019-01-25 21:12:39 UTC,It's Ubuntu 18.04.1 LTS:
1809819,2018-12-26 20:21:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1809823,2018-12-26 19:38:29 UTC,"Code above is taken from ""/usr/lib/python2.7/site-packages/oslo_service/service.py"" Line 794"
1809823,2019-01-08 19:16:33 UTC,suggested fix - https://review.openstack.org/629289
1809823,2019-01-11 21:08:45 UTC,"Change abandoned by Yossi Ovadia (<email address hidden>) on branch: master
Review: https://review.openstack.org/629289
Reason: after alot of research, this fix does not fix the initial neutron reported issue."
1809823,2019-01-11 21:12:59 UTC,"UPDATE:
to reproduce the bug:
log into the neutron_api container :"
1809823,2019-01-31 18:13:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634290"
1809823,2019-04-16 08:47:28 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/634290
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1809828,2020-03-17 10:49:44 UTC,For me (on bionic) the conflict seems to be against `libgdal-dev` and other libraries installed from ubuntugis/stable repo when I compiled GrassGIS from source.
1809828,2019-08-12 09:12:42 UTC,"This happens because nodejs in bionic is linked against OpenSSL 1.0 (see #1779863) while most other packages in bionic use OpenSSL 1.1. Installing any package using OpenSSL 1.1 will conflict with nodejs (more exactly: any package depending on libssl-dev, which conflicts with libssl1.0-dev)."
1809828,2019-07-11 13:18:50 UTC,#1799261 is basically the same issue.
1809828,2019-12-05 08:43:34 UTC,"I still have this issue with the most recent updates on Ubuntu 18.04.
Also reported here:
https://askubuntu.com/questions/1088662/npm-depends-node-gyp-0-10-9-but-it-is-not-going-to-be-installed"
1809828,2019-01-19 10:01:51 UTC,I tested this on 18.04.1 up to date to latest @ 19/1/2019
1809828,2018-12-27 13:59:12 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1809828,2018-12-27 16:21:02 UTC,I was able to install it following the instructions I found here: https://askubuntu.com/questions/899756/cant-install-npm-unable-to-correct-problems-you-have-held-broken-packages
1809828,2019-07-11 12:32:41 UTC,Here's the rabbit hole I went down:
1809828,2019-07-11 12:54:46 UTC,So apt is suggesting to give up current ssl-dev for a very old ssl-dev? Not cool :-/
1809828,2019-01-11 20:53:34 UTC,This issue also affects 18.04.1.
1809828,2019-01-11 21:00:03 UTC,"Possibly related: bug #1517491
See also: https://askubuntu.com/questions/1088662/npm-depends-node-gyp-0-10-9-but-it-is-not-going-to-be-installed"
1809834,2018-12-26 22:53:09 UTC,"okay I'm guessing I've reported this in the wrong area, but the fact that your site hosts a bad package would technically be a website issue as well so whatever.  :P"
1809838,2018-12-29 00:51:46 UTC,Now that I play-tested this and once again got it explained by WorldSavior I understand the mechanics. It definitely isn't a bug. The target is used to favor the production of corn flour.
1809838,2018-12-29 01:10:00 UTC,"Having the excess blackroot and blackroot flour being transported to and from the farms, mills and warehouses does mean the roads are carrying unnecessary traffic, though."
1809838,2018-12-29 01:31:42 UTC,But this is also true for all wares where one cannot set a target.
1809838,2019-01-01 23:13:36 UTC,"If the economy target for blackroot flour is not being adhered to, perhaps it should be removed from the GUI. The fact I could see the target prompted me to assume the current behaviour is incorrect. The lack of economy target for blackroot, corn etc. is (to a seasoned player) self-explanatory."
1809838,2019-01-12 13:19:50 UTC,"Removing blackroot flour from the economy settings would (as far as I know) require that there in no longer a economy target for blackroot flour. That would mean that it would always be milled, even when the time would be better spend only producing corn flour."
1809838,2019-01-12 17:01:39 UTC,I'd say 1) and have an explanation either in the Atlantean Tutorial and/or the encyclopedia.
1809838,2019-09-15 15:21:08 UTC,Migrated to https://github.com/widelands/widelands/issues/3376
1809838,2018-12-27 20:40:21 UTC,"Related entries in the forum at:
https://wl.widelands.org/forum/topic/2786/?page=21#post-26749"
1809838,2019-01-01 11:19:07 UTC,"Personally I like the behavior described in #2, so I wouldn't object to keeping it that way.
However, I think we should add some player-visible documentation of it somewhere. Maybe add some comment to the documentation of the atlanteans mill? And/Or describe it in the first atlanteans campaign? With the current state it does look like a bug; different from other wares the economy ""limit"" for blackroot flour is more of a minimum threshold and seems to be ignored.
Also, we should add a comment to the init file of the mill that the ""missing"" condition is missing on purpose."
1809839,2018-12-28 18:08:58 UTC,Thanks
1809839,2018-12-27 23:17:48 UTC,Thanks.
1809843,2018-12-27 01:13:57 UTC,apport information
1809843,2018-12-27 01:00:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809843,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1809843,2019-07-06 11:29:59 UTC,"I verified the proposed kernel for bionic, all good, no issue over 10 trials. Since I am only running bionic on this laptop I will not test xenial and cosmos unless instructed otherwise. Thank you very much everyone for your help!"
1809843,2019-07-03 13:06:35 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1809843,2019-07-03 13:03:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1809843,2019-04-16 15:31:30 UTC,"Hi Mike,"
1809843,2019-04-09 01:26:27 UTC,"I have attempted to test the kernel mentioned above and have not been able to; I enabled the given repo, installed the packages linux-image-5.0.0-8-generic, linux-headers-5.0.0-8, linux-headers-5.0.0-8-generic and linux-modules-5.0.0-8-generic and upon reboot was not able to start gdm. Fine, my nvidia modules failed to recompile for the new kernel, but when attempting to start networking I found that the sky2 kernel module was not present on my system. Indeed, linux-modules-5.0.0-8-generic does not contain sky2, even though it is built as a module according to the kernel config. Am I missing something? How do you suggest I test these changes?"
1809843,2019-04-04 18:06:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1809843,2019-03-29 16:32:01 UTC,This bug was fixed in the package linux - 5.0.0-8.9
1809843,2019-03-04 07:01:14 UTC,https://lkml.org/lkml/2019/3/4/50
1809843,2018-12-27 01:13:55 UTC,apport information
1809843,2019-02-20 15:13:00 UTC,"Please test the kernel without the ""disable_msi"" options:
https://people.canonical.com/~khfeng/linux-lp1807259-sky2-msi/"
1809843,2019-02-16 20:30:26 UTC,"Thank you for your response, this seems to do the trick. I was worried that disabling MSI would decrease networking performance, but a simple iperf3 test comparison showed no difference. Long term it seems that this should be handled in the kernel driver code (according to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/comments/34)."
1809843,2019-03-02 16:46:26 UTC,"Thank you very much for the kernel Feng, and sorry for the late response. I tested it as instructed and it works! Performed close to 20 suspend/start cycles without issue; before I would get a failure around every 3 runs."
1809843,2019-01-25 03:12:29 UTC,Is there any more information I can add to help debug this issue?
1809843,2018-12-27 01:13:59 UTC,apport information
1809843,2018-12-27 01:14:00 UTC,apport information
1809843,2018-12-27 01:14:01 UTC,apport information
1809843,2019-02-10 19:59:31 UTC,In terminal try
1809843,2018-12-27 01:14:03 UTC,apport information
1809843,2018-12-27 01:14:05 UTC,apport information
1809843,2018-12-27 01:14:02 UTC,apport information
1809843,2018-12-27 01:14:08 UTC,apport information
1809843,2018-12-27 01:14:09 UTC,apport information
1809843,2018-12-27 01:14:10 UTC,apport information
1809843,2018-12-27 01:14:12 UTC,apport information
1809843,2018-12-27 01:14:13 UTC,apport information
1809843,2018-12-27 01:14:06 UTC,apport information
1809843,2018-12-27 01:13:56 UTC,apport information
1809844,2019-12-16 11:00:30 UTC,"Reviewed:  https://review.opendev.org/698259
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=e414adf0353e30fa7d71b53e4cc3d6c580df35fc
Submitter: Zuul
Branch:    stable/rocky"
1809844,2020-01-30 10:26:57 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.1 release.
1809844,2020-01-30 10:24:12 UTC,This issue was fixed in the openstack/kolla-ansible 8.1.0 release.
1809844,2020-01-30 10:21:57 UTC,This issue was fixed in the openstack/kolla-ansible 7.2.0 release.
1809844,2019-12-16 17:05:49 UTC,"Reviewed:  https://review.opendev.org/698257
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=efe6083bb36ef90ea40db73dd633507cab0d59ec
Submitter: Zuul
Branch:    stable/train"
1809844,2019-12-16 11:00:19 UTC,"Reviewed:  https://review.opendev.org/698258
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=f1fe39bcafbe51bc2a4174b591dc1095d7410686
Submitter: Zuul
Branch:    stable/stein"
1809844,2019-12-10 14:26:53 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/698258"
1809844,2018-12-27 09:21:18 UTC,"I don't think this is currently possible. From looking at the docker-py code [1], we should be able to pass a timeout argument to the docker.APIClient constructor. We'd need a new module argument for the kolla_docker module in kolla-ansible."
1809844,2019-01-02 01:58:49 UTC,I could not find a way to accomplish this without hard-coding the timeout in /usr/local/lib/python2.7/dist-packages/docker/api/client.py
1809844,2019-12-10 14:27:20 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/698259"
1809844,2019-12-10 12:39:11 UTC,"Reviewed:  https://review.opendev.org/696316
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=01050dc01fa8558eb453c48faa2a8efd398c5367
Submitter: Zuul
Branch:    master"
1809844,2019-09-12 14:03:58 UTC,I have hit this issue in virtualised environments that are heavily loaded.
1809844,2019-12-10 14:25:09 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/698257"
1809844,2019-11-27 14:55:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/696316"
1809847,2019-01-15 10:33:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1809847,2018-12-27 03:19:16 UTC,https://lists.ubuntu.com/archives/kernel-team/2018-December/097407.html
1809847,2019-01-15 10:37:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1809847,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1809847,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1809848,2018-12-27 02:00:04 UTC,This change was made by a bot.
1809849,2018-12-27 09:40:32 UTC,Use apt-get to rebuild packages in a simple fashion.
1809851,2018-12-27 16:11:36 UTC,"The temporary file error is a known, but hard to repeat bug.  It's not the cause."
1809851,2018-12-27 17:50:52 UTC,"/media/eric/Lnx_bk0 is an ext4 partition on a Western Digital MyBook
external USB drive."
1809853,2019-09-12 14:02:51 UTC,Is it still an issue? Are you running an up to date docker python package?
1809853,2019-09-12 15:52:08 UTC,I have swift working now.  That bug report was submitted over 8 months ago so I don't remember the details.
1809853,2019-11-12 04:18:36 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1809856,2019-07-22 04:43:17 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1809856,2019-07-02 13:11:28 UTC,"Hi Hui Wang, sorry it has taken me so long to test this. I installed your patch and noticed the following things:"
1809856,2019-05-11 23:13:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809856,2019-04-26 11:26:43 UTC,Please install and test this deb under 4.18 kernel:
1809856,2019-04-25 00:41:22 UTC,"Ok, thanks."
1809856,2019-04-24 16:52:16 UTC,This noise disappears when running this command.
1809856,2019-04-16 10:50:50 UTC,Sorry for asking this again - is the original issue solved?
1809856,2019-04-22 10:23:17 UTC,No. The issue remains.
1809856,2019-04-16 10:08:27 UTC,It seems this was a red herring. I was testing on battery power which is why the audio was being runtime suspended. The hissing remains constant when the laptop is plugged in.
1809856,2019-04-14 19:58:27 UTC,"Hi Kai-Heng Feng, I successfully applied the patch, thanks. Now when the headphones are plugged in there are a few seconds of hissing before it goes quiet. If I change the volume, the hissing returns and stops after around 3-5s. If I play some music and then stop the music, the hissing returns and eventually stops after around 10s. Is this the expected behaviour?"
1809856,2019-04-09 05:45:10 UTC,"Download those files into a new directory, cd to the directory and run `sudo dpkg -i *deb`."
1809856,2019-04-03 11:07:25 UTC,"Hi Kai-Heng Feng,"
1809856,2019-03-11 15:24:05 UTC,"Please see if this kernel helps:
https://people.canonical.com/~khfeng/lp1809856/"
1809856,2019-03-06 10:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809856,2019-01-07 09:34:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1654448, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1809856,2019-04-23 03:41:21 UTC,"When there is noise, please do a test:"
1809856,2019-04-15 05:36:59 UTC,Seems like it goes away as soon as the audio gets runtime suspended.
1809860,2018-12-28 09:52:21 UTC,"Libluajit-5.1-dev is a non-optional build-dep for sysbench releases more recent than the ancient version in xenial. Hence, this is not a bug in the sysbench package unless/until one can show there's something wrong with the dependency itself. Otherwise, if you want sysbench to build on s390x, you'll have to ensure its build-deps are present and accounted for on that architecture."
1809860,2019-08-28 16:43:33 UTC,"+1 to blacklist this test on s390x, I don't see any value on bothering with xenial only per comment #1"
1809860,2019-08-28 16:47:29 UTC,"* cb9d9a84 (HEAD -> master, origin/master, origin/HEAD) Blacklist s390x arch on ubuntu_btrfs_kernel_fixes"
1809874,2019-01-17 05:33:50 UTC,thanks for correcting indeed it is with flag --wait
1809874,2019-01-16 19:38:42 UTC,"Hi Noam, Thanks for reporting this and making Ubuntu and OpenStack better. I've confirmed this and triaged it. This is currently targeted at the Ubuntu package only so I will also add the upstream project."
1809874,2019-03-08 04:20:17 UTC,This issue was fixed in the openstack/python-openstackclient 3.18.0 release.
1809875,2018-12-27 08:48:27 UTC,Specific handle is found in Adobes Photoshop.
1809875,2018-12-27 08:46:22 UTC,Rotation handle.
1809878,2019-01-11 00:47:05 UTC,Worth discussing. Marking it as triaged
1809878,2019-02-01 13:49:15 UTC,The request sounds reasonable. It is also nice to allow stadium/3rd-party projects to implement sanity checks.
1809878,2019-02-01 14:23:46 UTC,The RFE was approved and discussed by the drivers team
1809878,2019-02-20 22:02:07 UTC,First patch: https://review.openstack.org/#/c/627424/
1809879,2019-01-14 07:55:03 UTC,Ubuntu Trusty kernel does not contain this commit.
1809879,2019-01-14 08:42:08 UTC,"To reach this patch (9f03740a956) on Trusty tree:
  1. backport 16e7549 (Btrfs: incompatible format change to remove hole extents)
  2. cherrypick 2c68653 (btrfs: Check read-only status of roots during send)
  3. cherrypick 66ef7d6 (btrfs: check balance of send_in_progress)
  4. cherrypick 896c14f (Btrfs: fix wrong send_in_progress accounting)
  and finally this one (Btrfs: fix infinite path build loops in incremental send) with cherryick"
1809879,2019-01-29 10:24:56 UTC,"Kernel trace triggered by this test:
[  385.822256] ------------[ cut here ]------------
[  385.822262] WARNING: CPU: 1 PID: 1487 at /build/linux-pWDSBu/linux-3.13.0/mm/page_alloc.c:2552 __alloc_pages_nodemask+0x455/0xb90()
[  385.822263] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt x86_pkg_temp_thermal coretemp kvm_intel kvm joydev lpc_ich shpchp mac_hid btrfs xor raid6_pq libcrc32c crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel igb aes_x86_64 hid_generic lrw i915_bdw dca gf128mul intel_ips glue_helper usbhid ptp ablk_helper drm_kms_helper cryptd ahci hid drm pps_core libahci i2c_algo_bit video
[  385.822286] CPU: 1 PID: 1487 Comm: btrfs Not tainted 3.13.0-164-generic #214-Ubuntu
[  385.822287] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015
[  385.822288]  0000000000000000 ffff8804551916d8 ffffffff8173c0c8 0000000000000000
[  385.822290]  0000000000000009 ffff880455191710 ffffffff8106db6d 0000000000124050
[  385.822292]  0000000000000000 0000000000104050 0000000000000000 0000000000000000
[  385.822294] Call Trace:
[  385.822298]  [<ffffffff8173c0c8>] dump_stack+0x64/0x80
[  385.822301]  [<ffffffff8106db6d>] warn_slowpath_common+0x7d/0xa0
[  385.822303]  [<ffffffff8106dc4a>] warn_slowpath_null+0x1a/0x20
[  385.822305]  [<ffffffff81161bd5>] __alloc_pages_nodemask+0x455/0xb90
[  385.822317]  [<ffffffffa02dfa4d>] ? generic_bin_search.constprop.35+0x8d/0x1a0 [btrfs]
[  385.822320]  [<ffffffff811a1e53>] alloc_pages_current+0xa3/0x160
[  385.822323]  [<ffffffff8115c92e>] __get_free_pages+0xe/0x50
[  385.822325]  [<ffffffff81179abe>] kmalloc_order_trace+0x2e/0xc0
[  385.822327]  [<ffffffff811afc3f>] __kmalloc_track_caller+0x23f/0x260
[  385.822336]  [<ffffffffa0363e67>] ? fs_path_ensure_buf+0x67/0x1c0 [btrfs]
[  385.822338]  [<ffffffff81173d7f>] krealloc+0x4f/0xa0
[  385.822345]  [<ffffffffa0363e67>] fs_path_ensure_buf+0x67/0x1c0 [btrfs]
[  385.822352]  [<ffffffffa0363ff3>] fs_path_prepare_for_add+0x33/0xa0 [btrfs]
[  385.822359]  [<ffffffffa0364ae0>] fs_path_add_path+0x20/0x50 [btrfs]
[  385.822365]  [<ffffffffa0364fdb>] get_cur_path+0x6b/0x140 [btrfs]
[  385.822371]  [<ffffffffa0365340>] send_utimes+0xd0/0x190 [btrfs]
[  385.822378]  [<ffffffffa03662ce>] finish_inode_if_needed+0x1fe/0x4e0 [btrfs]
[  385.822384]  [<ffffffffa0367e35>] changed_cb+0x55/0x9f0 [btrfs]
[  385.822392]  [<ffffffffa0324e5c>] ? read_extent_buffer+0xbc/0x110 [btrfs]
[  385.822399]  [<ffffffffa0319d89>] ? btrfs_get_token_32+0x59/0xe0 [btrfs]
[  385.822406]  [<ffffffffa03255f1>] ? memcmp_extent_buffer+0xc1/0x120 [btrfs]
[  385.822411]  [<ffffffffa02e4fb3>] btrfs_compare_trees+0x783/0x960 [btrfs]
[  385.822418]  [<ffffffffa0367de0>] ? process_extent+0x1180/0x1180 [btrfs]
[  385.822424]  [<ffffffffa0369078>] btrfs_ioctl_send+0x8a8/0xc90 [btrfs]
[  385.822432]  [<ffffffffa0337579>] btrfs_ioctl+0x1129/0x2770 [btrfs]
[  385.822434]  [<ffffffff810ad752>] ? enqueue_task_fair+0x422/0x6d0
[  385.822436]  [<ffffffff810a4cc5>] ? sched_clock_cpu+0xb5/0x100
[  385.822439]  [<ffffffff8109b8d0>] ? enqueue_task+0x40/0x70
[  385.82244..."
1809879,2018-12-27 10:00:07 UTC,This change was made by a bot.
1809880,2019-06-05 22:23:37 UTC,This is most likely a vlc bug and should be reassigned to it. I am experiencing it in VLC under sway so unless the same bug exists across sway and mutter it's probably a vlc thing.
1809885,2019-01-07 09:36:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1809885,2019-01-08 15:25:22 UTC,apport information
1809885,2019-01-08 15:25:24 UTC,apport information
1809885,2019-01-08 15:25:26 UTC,apport information
1809885,2019-07-22 04:08:57 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1809887,2019-12-09 09:58:11 UTC,This is fixed in https://review.opendev.org/#/c/632733/.
1809887,2019-02-25 23:30:07 UTC,"Change abandoned by Ian Wells (<email address hidden>) on branch: master
Review: https://review.openstack.org/629256
Reason: Duplicate change.  Taken some of the neatness from this one for the other."
1809887,2019-01-08 15:58:30 UTC,"Apparently I can't edit previous messages - the `brctl` was deprecated *after* Rocky.
Also, this problem might be caused by a missing privsep init, similar to [2], and not by a missing filter.
I'm testing a fix now and will propose it if it works as expected."
1809887,2019-01-07 23:54:05 UTC,"FWIW, starting with Openstack Rocky, `brctl` was deprecated in favor of `ip link` [1]."
1809891,2019-05-07 00:30:49 UTC,"Change abandoned by fupingxie (<email address hidden>) on branch: master
Review: https://review.opendev.org/627516"
1809891,2018-12-27 12:28:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/627516"
1809891,2019-05-06 16:08:53 UTC,The stderr are not intended to open for read. Opening it with O_WRONLY is correct and should not need to change to O_RDWR.
1809902,2018-12-27 14:59:55 UTC,"As disused on IRC, the error message you are getting is the incorrect one for the problem you have, which is that neither the encfs or cryfs backend are actually installed on your machine."
1809902,2018-12-27 15:06:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809909,2019-02-26 21:48:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809909,2019-03-05 15:57:28 UTC,There was a segfault w/ python2.7 and its not actually an issue with apport. From dmesg:
1809918,2018-12-27 18:15:52 UTC,"This would be nice, it is already implemented for graphical lines, holding Ctrl while moving a line end allows it to move only in the vertical/horizontal direction"
1809918,2019-05-24 15:44:04 UTC,"I agree. Also it could be useful to implement it for every action in powerpcb eeschema, libedit etc that require a start point and an end point (move, drag, draw segment, draw wire, draw bus etc.): that should also simplify implementation and make the behaviour consistent between tools/operations."
1809919,2019-05-14 19:54:11 UTC,"I can't reproduce this. I tried with the firmware I'm working on, and with https://github.com/blacksphere/blackmagic."
1809920,2018-12-27 18:21:54 UTC,Screenshot.
1809920,2019-03-20 21:21:09 UTC,There is a RELEASE_UPGRADE_IN_PROGRESS environmental variable which gets set to 1 when the release upgrade starts but it was check-new-release-gtk that presented the dialog so we'll need a different way to denote that a release upgrade is already happening.
1809920,2019-03-28 18:06:40 UTC,"I went ahead and tested this to see what would happen if I did click 'yes' on the upgrade prompt to Ubuntu 18.04. As the team suspected the upgrade to 18.04 failed because it was unable to get an exclusive lock, so while this is ugly it won't actually break anybody. Additionally, if I recall correctly the release upgrade prompt is on a timer so if somebody received a prompt to upgrade to the next release and clicked 'yes' they shouldn't receive a prompt to upgrade to the next next release. Attached you find a screenshot of the ugly."
1809922,2018-12-28 12:04:16 UTC,the above with kolla-ansible 7.0.0
1809922,2019-06-25 04:17:22 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1809922,2018-12-27 21:42:07 UTC,then I add:
1809922,2019-04-18 18:52:20 UTC,not in stein
1809922,2019-04-25 09:27:24 UTC,The backup functionality was added only in the Stein release.
1809922,2018-12-27 21:53:20 UTC,additionally...
1809922,2018-12-29 09:15:47 UTC,"Thanks for your reporting! :)
Which kolla_install_type do you use? binary or source?"
1809922,2018-12-29 11:28:29 UTC,binary
1809928,2018-12-27 20:23:33 UTC,"Btw, this is Windows 10 64 bit build 1803"
1809929,2020-04-07 15:26:21 UTC,"KiCad has migrated to Gitlab, this issue is available here: https://gitlab.com/kicad/code/kicad/-/issues/2918"
1809929,2020-03-07 14:12:12 UTC,"Also of note: tested with ""Modern Toolset (Accelerated)"" and ""Modern Toolset (fallback)"" both with no effect on using any of the accelerator keys (but hotkeys operate as expected in all permutations)."
1809929,2020-03-07 14:08:58 UTC,Just found this thread as I am a Linux Mint user testing out migrating to Kicad from Altium/Eagle.
1809929,2019-08-12 19:14:08 UTC,"@Jeff, I closed this out since the v6 changes have changed the hotkey behavior.  We'll see whether or not users prefer both the immediate and non-immediate modes combined in v5 or the either or mode of v6.  That would be a different bug report."
1809929,2019-08-09 21:48:19 UTC,"@Wayne, is the 6.0 hotkeys architecture sufficient to close this bug, or is there still work to be done?"
1809929,2019-02-05 17:44:08 UTC,"I think we should fix this during v6.  Once the legacy canvas code is removed from the source tree, the hotkey and menu accelerator code should be simplified since we will only have the new toolkit to deal with.  There are some subtle key handling differences between platforms so I don't think this bug will be as trivial to fix as it would appear."
1809929,2019-01-11 13:49:24 UTC,"On 1/10/2019 4:56 PM, Seth Hillbrand wrote:

>> A hotkey is effectively a menu accelerator plus a left mouse click
> combined at the current cursor location.
>
> Got it.  That's certainly different from how I've been considering
> hotkeys, so I'll have to look around a see if I've been implementing
> things counter to this thinking.
>
> Two issues come to mind when thinking about this.  The first is that we
> allow hotkey definition at the moment that includes the shift key.  If
> we have accelerators automatically generated that include the shift key,
> we should preclude them from being re-assigned.
"
1809929,2019-01-10 21:56:02 UTC,"> A hotkey is effectively a menu accelerator plus a left mouse click combined at the current cursor location.
"
1809929,2019-01-10 19:33:27 UTC,"On 1/10/2019 1:59 PM, Seth Hillbrand wrote:

> I guess that we should decide what we show in the menus.  Eeschema shows
> the accelerators and pcbnew shows the hotkeys.
"
1809929,2019-08-27 14:28:10 UTC,"Through this may be fixed in 6.0, it is still present in 5.1, leading to confusion for Linux users, especially the ones coming from Windows and having used Shift+[key]."
1809929,2019-01-10 06:33:44 UTC,"Hello Wayne,"
1809929,2019-01-09 22:40:43 UTC,"On 1/9/19 1:46 PM, Seth Hillbrand wrote:

> Hmm... In more detail, re-assigning the menu accelerator for the line
> tool to Shift+L in pcbnew and testing.  It works as expected.
>
> In Eeschema, the menu accelerators show Shift+letter but in the hotkey
> list, they are only the capital letter.  Assigning the hotkey in
> Eeschema to Shift+letter causes the accelerator to behave correctly.
> The menu display does not change.
"
1809929,2019-01-09 18:46:31 UTC,"Hmm... In more detail, re-assigning the menu accelerator for the line tool to Shift+L in pcbnew and testing.  It works as expected."
1809929,2019-01-09 18:00:50 UTC,I believe the reason this works in with the new tool framework is that the menu accelerators have a Ctrl+ prefixed.  At least this is what I remember seeing when I was testing.  This would explain why it works in pcbnew and not in eeschema.  I'm at work so I cannot confirm this.
1809929,2019-01-09 17:41:41 UTC,"Application: kicad
Version: (6.0.0-rc1-dev-1505-gd1b53028a1-dirty), release build
Libraries:
    wxWidgets 3.0.4
Platform: Linux 4.18.0-3-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Compiler: GCC 8.2.0 with C++ ABI 1013"
1809929,2019-01-03 17:51:55 UTC,"It seems that the problem only in displaying shortcuts in the menu.
Shortcuts in Preferences->Preferences...->Hotkeys displays as only [letter] without [shift] and work fine.
In my opinion, the lack of need to press shift is better."
1809929,2019-01-09 17:41:41 UTC,"After tests:
This issue is Linux specific (works fine on W7):
Shift+letter does not work both using GTK2 and GTK2 on my installs (KDE and Unity)"
1809929,2019-01-09 17:41:23 UTC,"Shift+Key works as expected in pcbnew.  Does not work in Eeschema.  In Eeschema, the same key works without the ""Shift"" modifier"
1809929,2019-01-09 14:23:38 UTC,"@JP, did you test using gtk3?  I did some quick testing and the Shift menu accelerator keys do not appear to be working for me.  I don't see the correct tool being enabled.  I seem to remember this working with gtk2.  Would one of the developers using a gtk3 build please confirm this?"
1809929,2019-01-06 06:05:27 UTC,I personally can live fine with just the [letter] as hotkey. But no matter what behavior is (still) intended here there is some inconsistency between the menus and the help display then.
1809929,2019-01-10 18:59:59 UTC,I guess that we should decide what we show in the menus.  Eeschema shows the accelerators and pcbnew shows the hotkeys.
1809929,2019-01-06 09:42:11 UTC,Shift + letter works fine.
1809929,2019-01-06 10:10:07 UTC,"Well, I'm aware that hotkeys something different than shortcuts."
1809933,2018-12-28 00:21:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1809935,2018-12-27 23:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1809935,2018-12-27 23:09:36 UTC,"  Apport-recogida 1809935
Apport-recogida: orden no encontrada"
1809936,2019-07-01 16:50:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809936,2019-07-04 15:16:10 UTC,"@Per-Inge: this is a separate issue, tracked by bug #1741074."
1809936,2019-07-01 17:11:12 UTC,"In a new installation of EOAN it's not possible to install gnome extensions in Chromium.
You get this error message
""Although GNOME Shell integration extension is running, native host connector is not detected."" Refer documentation for instructions about installing connector.""
The method advised in the instruction ""GNOME Shell integration for Chrome Installation Guide""
$ sudo apt-get install chrome-gnome-shell
isn't working."
1809936,2018-12-28 00:20:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1809939,2020-10-02 10:44:21 UTC,Patches are ready. Just waiting for launcpad repo to be fixed.
1809939,2019-09-19 12:07:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1809940,2019-01-07 09:43:41 UTC,Can you please try editing /etc/gdm3/custom.conf and uncommenting this line:
1809940,2019-01-07 19:51:44 UTC,Dear Daniel!
1809940,2019-03-09 04:17:49 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1809940,2019-04-11 05:59:53 UTC,I ran into this problem as well. Thank you so much for the fix!
1809943,2019-03-24 23:39:51 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1809943,2019-03-24 23:04:31 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1809943,2018-12-28 05:52:21 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/627603"
1809943,2019-02-09 04:13:48 UTC,"Reviewed:  https://review.openstack.org/627604
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dcd7a30c9548512eaee91b96d0ed0f4b18bcdbff
Submitter: Zuul
Branch:    stable/queens"
1809943,2019-01-18 04:39:34 UTC,"Reviewed:  https://review.openstack.org/627603
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6e1120ae3025a532ff8957a6952f445152a69967
Submitter: Zuul
Branch:    stable/rocky"
1809943,2019-01-17 14:00:09 UTC,"Reviewed:  https://review.openstack.org/627034
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a31157c527ae88af2e8c283e8b5156e9ace55dfa
Submitter: Zuul
Branch:    master"
1809943,2019-03-22 03:44:41 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1809943,2018-12-28 05:52:44 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/627604"
1809945,2020-07-28 09:21:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809945,2020-07-28 11:49:49 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu."
1809951,2018-12-28 06:04:11 UTC,xrdp-build-pulse-modules is part of the xrdp-pulseaudio-installer package:
1809951,2019-11-26 07:57:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809951,2020-11-23 05:23:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1809957,2020-12-11 08:41:13 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1809957,2021-02-10 04:17:19 UTC,[Expired for tftp-hpa (Ubuntu) because there has been no activity for 60 days.]
1809957,2020-12-11 08:41:01 UTC,From your log:
1809957,2020-12-10 19:16:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809960,2019-09-16 08:20:20 UTC,Migrated to https://github.com/widelands/widelands/issues/3377
1809962,2018-12-28 13:53:20 UTC,Thanks for reporting. This is already fixed in the development version (which will be released 1.0 at some point in the future).
1809970,2019-01-05 20:47:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1809971,2020-05-02 04:17:27 UTC,[Expired for GNU Arm Embedded Toolchain because there has been no activity for 60 days.]
1809971,2019-01-17 17:41:36 UTC,"I had the same problem for gcc 8 2018-q4/8.2.1.
Tried the suggestions none works."
1809971,2019-01-18 15:50:02 UTC,"Jerry, same here. I believe this is a genuine new bug."
1809971,2019-01-11 04:00:57 UTC,"Google ""lto-wrapper failed"", or ""stack overflow lto-wrapper failed""."
1809971,2019-01-07 11:21:23 UTC,"Marc, I tried googling around and found nothing. Some links would be greatly appreciated."
1809971,2018-12-29 04:03:05 UTC,"I believe there is documentation online about fixing this.  You need to add a reference to the plugin.  Also, I believe this is a duplicate."
1809971,2020-03-02 11:24:18 UTC,"Hi john,
Can you provide reduced testcase to with corresponding command line options so I can reproduce this issue ?"
1809972,2018-12-28 12:37:03 UTC,Please note that system uses different SSD during bug reporting.
1809972,2018-12-28 13:00:08 UTC,This change was made by a bot.
1809972,2018-12-28 16:27:35 UTC,Thanks for the patch.
1809972,2018-12-29 16:12:53 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=202093
1809972,2021-02-24 09:27:33 UTC,This also happens on the brand new Samsung 870 EVO.
1809972,2021-02-24 09:31:43 UTC,I'm seeing this with my 870 EVO on 20.04 kernel 5.4.0-65-generic.
1809975,2019-02-22 13:08:16 UTC,"In error, jebeld17 provided the following information on Launchpad instead of here:"
1809975,2019-02-22 14:46:47 UTC,"Paul,"
1809975,2019-02-08 04:33:59 UTC,"I believe it functions with Graph APIs, but I'm not certain for sure."
1809975,2019-02-20 03:30:22 UTC,jebeld17 ?
1809975,2019-01-12 13:29:56 UTC,This is something that needs to be implemented upstream by the developers of Thunderbird.
1809975,2019-02-05 19:31:54 UTC,"I'm unfamiliar with what this ""Your Phone/Companion"" product is. Can you link to something about it?"
1809975,2019-02-05 18:45:11 UTC,"Bug added to Mozilla's registry at:
https://bugzilla.mozilla.org/show_bug.cgi?id=1525360"
1809975,2019-02-06 15:16:10 UTC,"@clokep-4
https://support.microsoft.com/en-us/help/4459358/windows-10-your-phone-app-help"
1809975,2019-01-12 15:39:53 UTC,setting to wishlist per request from PaulW2U on #ubuntu-bugs. Leaving as new.
1809975,2019-02-05 18:35:50 UTC,Original Launchpad bug: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1809975
1809975,2019-02-05 18:35:13 UTC,"User Agent: Mozilla/5.0 (Linux; Android 8.0.0; HTC U11) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.99 Mobile Safari/537.36 EdgA/42.0.92.3330"
1809979,2019-12-31 14:01:11 UTC,"This happens particularly for timezone format of datetime(18,12,28,10,30,19). Is there any solutions or fix to the problem"
1809979,2019-12-31 22:45:53 UTC,"I suspect the problem is your use of ""18"" to mean ""2018"". Your print output probably says ""0018-12-28 10:30:19+05:41"", which is a good hint. I get the following with the corrected year:"
1809979,2020-01-01 02:03:09 UTC,"Hi Brian,"
1809980,2019-02-04 08:11:03 UTC,"Dommage qu'il n'y ait pas de réactivité sur le projet, il semblait intéressant et j'aurais aimé m'en servir comme support pour mes TP..."
1809980,2019-02-04 11:48:36 UTC,"Bonjour,"
1809981,2019-05-13 08:32:36 UTC,Can you include any more details about what you're seeing? What's in the stats file when this error occurs?
1809981,2019-07-13 04:18:00 UTC,[Expired for OpenStack rabbitmq-server charm because there has been no activity for 60 days.]
1809994,2021-02-04 21:08:03 UTC,With bridges or vlans interfaces same problem here
1809994,2019-10-07 17:44:18 UTC,This impacts bonded interfaces on a fresh install of Ubuntu 18.04.3 LTS
1809996,2019-01-09 21:33:07 UTC,"Update: I don't thinks the NIC is a reliable workaround. I'm now 99% sure a reliable workaround is to disable Intel SW Guard Extensions (SGX) in the BIOS. Once I did this, I can reliably Commission and Deploy 18.04."
1809996,2018-12-29 00:18:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1809998,2018-12-28 22:00:08 UTC,This change was made by a bot.
1810000,2019-01-02 11:08:33 UTC,"Thanks for the bug report! Unfortunately, the bluetooth code in QEMU is completely unmaintained and quite bit-rotten already, so it is already marked as deprecated and will be removed soon unless somebody steps up and volunteers to maintain it:"
1810000,2020-05-24 21:57:21 UTC,"This issue has nothing to do with bluetooth rather something with xhci. I've got the same error while trying to pass through a usb device to a Windows VM, once the guest driver is loaded in the the assert fires so probably it's trying to send something that's not handled correctly. A similar (same?) issue is also mentioned in this bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849884"
1810000,2020-06-16 15:23:23 UTC,We found a reproducer during fuzzing:
1810000,2020-08-11 21:02:59 UTC,Here's a QTest reproducer:
1810004,2019-05-28 01:10:42 UTC,Fixed by: https://review.opendev.org/#/c/630922/
1810012,2020-09-21 15:16:57 UTC,Fixed in 0.4.2-2
1810017,2018-12-31 20:13:08 UTC,"Brian,This is what I got in the last email. Where's the is the mistake and the way you type the instructions are really hard for me to understand. What does ""CreateIPPPrinterQueues All"" mean? Do I copy and paste both lines or just the sudo nano /etc/cups/cups-browsed?  'sudo nano /etc/cups/cups-browsed' and find the line ""#CreateIPPPrinterQueues All""
 I copied and pasted. sudo nano /etc/cups/cups-browsed
1. Do 'sudo nano /etc/cups/cups-browsed' and find the line ""#
CreateIPPPrinterQueues All""."
1810017,2018-12-31 18:14:20 UTC,"> First off this is getting fun, but all I got with the Nano is
> and will quit there till this step gets figured out. Here's the
> Nano and you guessed right with Mint using it.
> The etc/cups/cups-browsed is blank.
"
1810017,2018-12-31 20:33:16 UTC,"Sorry Dan,"
1810017,2019-01-01 18:45:41 UTC,"Thanks for the update Brian, but I tried the USB cable hooked to my system again and It came up and printing at forty feet with no problems.Dan"
1810017,2019-01-01 19:14:39 UTC,"> Thanks for the update Brian, but I tried the USB cable hooked
> to my system again and It came up and printing at forty feet
> with no problems.Dan
"
1810017,2018-12-31 17:12:16 UTC,"Thanks, Brain
First off this is getting fun, but all I got with the Nano is and will quit there till this step gets figured out. Here's the Nano and you guessed right with Mint using it. The etc/cups/cups-browsed is blank."
1810017,2019-01-01 11:56:13 UTC,I'll record that following the advice given in this thread leads to success for somebody.
1810017,2018-12-31 16:08:42 UTC,"Ok, Dan. I can see what 'lpstat -t' in a terminal gave you. Basically, it looks like you have set up two printers with HPLIP. One is named OfficeJet_Pro_6970. The other is named OfficeJet_Pro_6970_2. There are also three jobs sent to MSTOfficeJet_Pro_6970 which haven't printed. What is ""MST""? Where does it come from?"
1810017,2018-12-31 20:58:41 UTC,Nor me brian. I'll wait for the next HPLIP version because this version isn't going to work.Happy trails...
1810017,2018-12-31 12:18:34 UTC,"Hi Dan,"
1810017,2018-12-31 01:54:04 UTC,"I did nothing other than showing you the command. Here's the output of the command you sent:billyrey@billyrey-Aspire-E5-575:~$ pstat -a
Command 'pstat' not found, but there are 19 similar ones.
billyrey@billyrey-Aspire-E5-575:~$
Thanks, Brian.Dan"
1810017,2018-12-30 22:47:36 UTC,"Dan,"
1810017,2018-12-30 19:10:04 UTC,"Hi Brian,Knowing absolutely nothing about any of this. I ran a line from the link you sent the lpstat -t
Notice: printer OfficeJet_Pro_6970 disabled since Wed 26 Dec 2018 04:41:59 PM MST - File ""/usr/lib/cups/filter/hpcups"" not available: No such file or directoryprinter OfficeJet_Pro_6970_2 is idle.  enabled since Thu 27 Dec 2018 07:35:22 AM MSTprinter OfficeJet_Pro_6970_fax disabled since Wed 26 Dec 2018 04:11:37 PM MST - File ""/usr/lib/cups/filter/hpcupsfax"" not available: No such file or directory
Are the lines saying ""No such file or directory"" mean that the file or directories weren't installed n the first place?Thank youDan
billyrey@billyrey-Aspire-E5-575:~$ lpstat -tscheduler is runningsystem default destination: OfficeJet_Pro_6970device for OfficeJet_Pro_6970: hp:/net/OfficeJet_Pro_6970?ip=192.168.1.14device for OfficeJet_Pro_6970_2: hp:/net/OfficeJet_Pro_6970?ip=192.168.1.14device for OfficeJet_Pro_6970_fax: hpfax:/net/OfficeJet_Pro_6970?ip=192.168.1.14device for OfficeJet_Pro_6970_fax_2: hpfax:/net/OfficeJet_Pro_6970?ip=192.168.1.14OfficeJet_Pro_6970 accepting requests since Wed 26 Dec 2018 04:41:59 PM MSTOfficeJet_Pro_6970_2 accepting requests since Thu 27 Dec 2018 07:35:22 AM MSTOfficeJet_Pro_6970_fax accepting requests since Wed 26 Dec 2018 04:11:37 PM MSTOfficeJet_Pro_6970_fax_2 accepting requests since Thu 27 Dec 2018 07:35:44 AM MSTprinter OfficeJet_Pro_6970 disabled since Wed 26 Dec 2018 04:41:59 PM MST - File ""/usr/lib/cups/filter/hpcups"" not available: No such file or directoryprinter OfficeJet_Pro_6970_2 is idle.  enabled since Thu 27 Dec 2018 07:35:22 AM MSTprinter OfficeJet_Pro_6970_fax disabled since Wed 26 Dec 2018 04:11:37 PM MST - File ""/usr/lib/cups/filter/hpcupsfax"" not available: No such file or directoryprinter OfficeJet_Pro_6970_fax_2 is idle.  enabled since Thu 27 Dec 2018 07:35:44 AM MSTOfficeJet_Pro_6970-3    billyrey         17408   Thu 27 Dec 2018 07:45:07 AM MSTOfficeJet_Pro_6970-4    billyrey         19456   Thu 27 Dec 2018 07:52:02 AM MSTOfficeJet_Pro_6970-5    billyrey        279552   Fri 28 Dec 2018 02:32:03 PM MSTbillyrey@billyrey-Aspire-E5-575:~$"
1810017,2018-12-31 14:43:06 UTC,"Brain,I think I've done what you've asked and if not I then sorry, but I don't understand any of this. This is what the terminal gave me I have no idea how to edit anything. Thanks  Dan
 billyrey@billyrey-Aspire-E5-575:~$ systemctl restart cups-browsedbillyrey@billyrey-Aspire-E5-575:~$ lpstat -ts scheduler is runningsystem default destination: OfficeJet_Pro_6970device for OfficeJet_Pro_6970: hp:/net/OfficeJet_Pro_6970?ip=192.168.1.14device for OfficeJet_Pro_6970_2: hp:/net/OfficeJet_Pro_6970?ip=192.168.1.14device for OfficeJet_Pro_6970_fax: hpfax:/net/OfficeJet_Pro_6970?ip=192.168.1.14device for OfficeJet_Pro_6970_fax_2: hpfax:/net/OfficeJet_Pro_6970?ip=192.168.1.14OfficeJet_Pro_6970 accepting requests since Wed 26 Dec 2018 04:41:59 PM MSTOfficeJet_Pro_6970_2 accepting requests since Thu 27 Dec 2018 07:35:22 AM MSTOfficeJet_Pro_6970_fax accepting requests since Wed 26 Dec 2018 04:11:37 PM MSTOfficeJet_Pro_6970_fax_2 accepting requests since Thu 27 Dec 2018 07:35:44 AM MSTprinter OfficeJet_Pro_6970 disabled since Wed 26 Dec 2018 04:41:59 PM MST - File ""/usr/lib/cups/filter/hpcups"" not available: No such file or directoryprinter OfficeJet_Pro_6970_2 is idle.  enabled since Thu 27 Dec 2018 07:35:22 AM MSTprinter OfficeJet_Pro_6970_fax disabled since Wed 26 Dec 2018 04:11:37 PM MST - File ""/usr/lib/cups/filter/hpcupsfax"" not available: No such file or directoryprinter OfficeJet_Pro_6970_fax_2 is idle.  enabled since Thu 27 Dec 2018 07:35:44 AM MSTOfficeJet_Pro_6970-3    billyrey         17408   Thu 27 Dec 2018 07:45:07 AM MSTOfficeJet_Pro_6970-4    billyrey         19456   Thu 27 Dec 2018 07:52:02 AM MSTOfficeJet_Pro_6970-5    billyrey        279552   Fri 28 Dec 2018 02:32:03 PM MSTbillyrey@billyrey-Aspire-E5-575:~$"
1810017,2018-12-30 09:20:45 UTC,"Hello Dan,"
1810017,2018-12-30 04:14:16 UTC,"Hi Brian,It's Network (wireless), but even when I try by Ethernet it still doesn't install the printer. Just the FAX. I don't know about the CUPS. Where do I look?Thanks"
1810017,2018-12-29 10:27:21 UTC,Is the OfficeJet Pro 6970 connected by USB or is it on the network? What is your CUPS version?
1810018,2019-07-02 13:10:04 UTC,"Thank you for your bug report. The change is commit from Debian
https://salsa.debian.org/gnome-team/librsvg/commit/1c53c0b1d
Could you report it to them on https://packages.qa.debian.org/libr/librsvg.html ?"
1810019,2018-12-29 05:30:03 UTC,This change was made by a bot.
1810026,2020-10-21 20:08:22 UTC,Some Hadoop connector also apparently expects this; I'm not sure there's many workarounds with the client is a 3rd party plugin that expects you're talking to s3 and they want this feature?
1810026,2020-01-01 03:25:09 UTC,"We are also struggling with this issue. We backup the Elasticsearch snapshots to swift cluster using the ES S3 plugin but failed, because the plugin only support chunked encoding upload (ES 6.x, it can be configured to disable chunked encoding in ES 7.5 S3 plugin), and Swift + S3api doesn't. Moreover, some applications rely on chunked encoding for video/media streaming data upload. We are investigating and try to resolve it. Any hint is welcome."
1810026,2019-02-15 13:50:00 UTC,"Reviewed:  https://review.openstack.org/637142
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=b68bef5cd80e2a1b71a1ef544e122b39dfa7ac57
Submitter: Zuul
Branch:    feature/losf"
1810026,2019-02-15 07:48:47 UTC,"Related fix proposed to branch: feature/losf
Review: https://review.openstack.org/637142"
1810026,2019-01-04 17:15:29 UTC,"Bah, forgot about that. Apparently that's not uncommon -- I tried fixing it in https://github.com/minio/minio-go/pull/1048 (for example), but apparently S3 might start responding with an *empty* Content-Encoding header... bleh."
1810026,2019-01-04 04:16:35 UTC,"Thanks, Tim."
1810026,2019-01-03 19:13:00 UTC,"Good news: as of https://github.com/openstack/swift/commit/79539ea you'll no longer store bad data (!), and you'll no longer have the client raising exceptions about mismatched hashes."
1810026,2019-02-08 23:52:41 UTC,"Reviewed:  https://review.openstack.org/621055
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=1a51604b26e7cd1b3f3e7d30176b251501070e07
Submitter: Zuul
Branch:    master"
1810027,2019-02-15 11:30:01 UTC,"@J.Snow, don't run binaries from inside the snap directly, you won't have the right LD_LIBRARY_PATH and all the rest of the environment needed to run the snap."
1810027,2019-10-29 17:41:30 UTC,@jon.snow - can you do one interesting test:
1810027,2019-03-12 23:54:17 UTC,"I should have also mentioned that once the program opens via the associated file, I can also open the program via terminal or desktop shortcut normally. As long as the program is started for the first time after boot via the associated file, it will work normally afterwards and can be started again via all normal ways. On the other hand, if the program is started for the first time after boot via terminal or desktop shortcuts, it crushes and nothing will make it work again but a reboot."
1810027,2019-03-12 23:51:14 UTC,I think the bug is much weirder than it looked originally. It seems to be related to how the applications start.
1810027,2019-12-29 04:17:32 UTC,[Expired for snapd because there has been no activity for 60 days.]
1810027,2019-03-12 02:54:18 UTC,Still not working for me on Ubuntu 16.04:
1810027,2019-03-05 19:31:47 UTC,"It was fixed on the latest snapd version:
$ snap version
snap    2.37.2
snapd   2.37.2
series  16
ubuntu  18.10
kernel  4.18.0-15-generic"
1810027,2019-02-16 10:55:40 UTC,Thanks for the prompt reply John.
1810027,2019-02-16 09:07:28 UTC,"Thank you for that.
Could you tell me the output of
type vlc
?"
1810027,2019-02-16 00:40:13 UTC,"@Seth:
The file exists:"
1810027,2019-02-15 00:05:59 UTC,"On Thu, Feb 14, 2019 at 07:45:51PM -0000, J. Snow wrote:

> $ ls -lh /snap/vlc/770/usr/lib/libvlc.so.5
> lrwxrwxrwx 1 root root 15 Jan 10 18:27 /snap/vlc/770/usr/lib/libvlc.so.5 -> libvlc.so.5.6.0
"
1810027,2019-01-23 22:22:21 UTC,@john Happy to do help anyway I can. The problem is I'm not sure what other info I could provide other than the above. I literaly type vlc on console and get the stack smashing error. Any ideas on what other information I could provide?
1810027,2019-01-25 21:00:21 UTC,Here you are:
1810027,2019-01-25 07:54:23 UTC,There's always a scenario in which there is a actual bug in the code and stack protector acts accordingly.
1810027,2019-01-24 23:18:33 UTC,"@jamie: Agreed. To ensure that apparmor is not the problem, I installed the snap in classic confinement but got the same ""stack smashing detected"" error."
1810027,2019-01-24 17:17:57 UTC,"[154475.952709] audit: type=1400 audit(1548282309.635:537): apparmor=""DENIED"" operation=""open"" profile=""snap.vlc.vlc"" name=""/etc/pulse/client.conf.d/"" pid=3895 comm=""vlc"" requested_mask=""r"" denied_mask=""r"" fsuid=1000 ouid=0"
1810027,2019-01-23 22:56:35 UTC,I also tried installing the apt version of vlc to see if it works. Now both versions are installed on the system at the same time.
1810027,2019-01-23 22:40:02 UTC,I just noticed that every time I try to start vlc I get on dmesg the following lines:
1810027,2019-01-15 09:38:08 UTC,"Could you help me reproduce this, please? I've tried both those snaps in 18.10 just now and neither of them crash the way you report."
1810027,2019-01-14 21:07:09 UTC,The problem persists on the latest version on VLC:
1810027,2019-01-03 15:21:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810027,2019-02-14 19:45:51 UTC,Is there anything else I can do to help on the debugging?
1810029,2019-02-20 21:16:07 UTC,"It's fixed, Secure Boot has to be disabled in BIOS before updating, since it's an UEFI system. It seems like updating linux-headers with Secure Boot enabled messes nvidia drivers. Intel drivers keep working though."
1810029,2018-12-29 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810029,2019-01-03 15:37:53 UTC,"This bug is recurring, it happened before and it's still there"
1810031,2018-12-31 02:56:57 UTC,cups version:
1810031,2018-12-31 10:51:53 UTC,"To have the device automatically set up for printing, please read"
1810031,2018-12-30 19:19:59 UTC,What version of CUPS are you running?
1810031,2019-01-01 09:55:59 UTC,starting up cups-browsed did the job .. test page prints ok now through network.
1810033,2018-12-29 14:30:06 UTC,This change was made by a bot.
1810035,2018-12-29 14:52:51 UTC,"schöne bildchen sind das geworden, sind die für die seite auch transparent im Hintergrund?"
1810035,2019-01-28 21:37:17 UTC,"A first attempt for the new website development news logo. Quite experimental, the texture is not good."
1810035,2019-01-30 21:19:29 UTC,"Next try, now the logo is also made of marble. The W is brighter than the L."
1810035,2019-01-31 22:08:09 UTC,Another one. W and L now have the same texture and are equal in brightness.
1810035,2019-02-04 20:39:31 UTC,Modified the block underneath the logo in a way that the lower left serif of the 'L' is buried in it.
1810035,2019-02-04 20:41:01 UTC,Blender file for the Development News version 5 image.
1810035,2019-02-09 11:01:44 UTC,"Yes yes yes, I think these look great!"
1810035,2019-09-06 08:19:53 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/293
1810036,2019-01-02 15:31:43 UTC,"@Tom and @JP, AFAIK, Jon already has the new schematic netlist code done which keeps the schematic netlist up to date on as the schematic is edited.  He is just waiting for the v6 development window to open to get it merged.  Once that is merged, this issue should go away unless I'm not understanding something."
1810036,2019-01-02 15:19:34 UTC,"@Jean-Pierre: JP, isn't it because the netlisting algorithm in eeschema is still a bit slow? In case of the P&S&PCB connectivity algorithms it takes fractions of a millisecond for a single net (and most of the time is taken anyway by point-to-polygon queries, which are not used in eeschema). Should we try optimizing this in V6?"
1810036,2019-07-09 21:30:24 UTC,I've made the highlighting consistent in both directions based on Jon's new connection code.
1810036,2019-01-02 08:30:48 UTC,The expected behavior is not good.
1810036,2019-01-02 09:33:09 UTC,this could be mitigated by adding a switch which enables/disables that behavior (but enabled by default). On the contrary side:
1810037,2018-12-29 16:00:07 UTC,This change was made by a bot.
1810037,2019-07-29 16:10:00 UTC,Does this issue happen under 19.04 or 19.10?
1810040,2019-09-06 21:12:39 UTC,This was fixed a while back by disabling the animations in Ubuntu MATE Welcome.
1810041,2018-12-29 20:16:10 UTC,On what version of Ubuntu Mate are you having this issue?
1810041,2018-12-29 20:33:15 UTC,"Hi,"
1810043,2019-08-20 20:28:44 UTC,"The attachment ""Rescans network interfaces after NetworkManager may have deleted some"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1810043,2019-10-02 21:55:08 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1~18.04.1
1810043,2019-10-02 21:54:51 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1~19.04.1
1810043,2019-09-30 20:56:04 UTC,Verification-done on disco as well:
1810043,2019-08-28 17:45:58 UTC,Fix confirmed in LXD container:
1810043,2019-08-27 22:48:03 UTC,"Hello Don, or anyone else affected,"
1810043,2019-08-22 01:13:47 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1
1810043,2019-06-06 18:03:03 UTC,"I ran into this one on 18.04 because I have a Pacemaker/Corosync virtual IP failover, which aliases the ethernet in the same way.  Thanks for the bug fix, I will try to test soon."
1810043,2018-12-29 18:02:20 UTC,more specifically... if there is a label set for alias as in:
1810043,2019-05-12 00:04:58 UTC,@Deltik - applied most recent patch - confirmed resolves original bug on Ubuntu 18.04.2 LTS
1810043,2019-05-11 17:12:01 UTC,@donthorntonjr: Please try the updated patch attached to this comment.
1810043,2019-05-11 16:48:41 UTC,@donthorntonjr: It looks like you're using the networkd renderer.  I had only considered the NetworkManager renderer for the patch.
1810043,2019-05-11 16:16:26 UTC,@Deltik - applied patch has no effect on original bug: netplan apply fails if NIC alias exists
1810043,2019-05-11 15:13:15 UTC,"This bug affects bridges like ""br0"" as well: https://superuser.com/q/1435615/83694"
1810043,2019-05-11 15:10:04 UTC,I have a patch that fixes this bug.
1810043,2019-05-01 16:35:48 UTC,"A very similar problem, perhaps the same bug seems to impact the use of vlan interfaces. ""netplan apply"" fails the first run with the output shown below (and leaves the networking in a bad state) then succeeds the second time it is run."
1810043,2019-10-02 21:55:32 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1810043,2019-05-21 16:14:29 UTC,The fix has been merged into CanonicalLtd/netplan: https://github.com/CanonicalLtd/netplan/pull/86
1810045,2019-01-01 21:02:59 UTC,I'm not sure this has a high priority.  It's really a new feature request.
1810045,2018-12-29 17:17:23 UTC,Line color and line with controls are already in version 5
1810045,2018-12-30 17:11:37 UTC,1) draw circle / ellipse;
1810048,2018-12-29 18:15:22 UTC,"sorry, i forgot: install method is 'distro'"
1810048,2019-02-28 16:14:26 UTC,"Just to say, seeing the same issue with CentOS Linux release 7.6.1810 (Core) and OSA 18.1.4. Also tried with the latest checkout of ""stable/rocky"" OSA with same result."
1810048,2019-10-17 16:48:22 UTC,I just hit the same issue.  Here are some notes I was dumping to when looking over the issue:
1810048,2019-10-17 17:00:49 UTC,Actually these look like different issues due to the same set of changes:  https://github.com/openstack/openstack-ansible-os_horizon/commit/20e47c9e4b7bcf564905c3b8b090d1b31be8f523
1810048,2019-10-17 18:31:46 UTC,As far as I'm aware the 'Enable project panels' task only happens on 'source' installs.  I created a new ticket just for the source install issues.
1810050,2020-09-14 07:42:22 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1810055,2019-07-29 16:09:09 UTC,Does this issue still happen?
1810055,2018-12-29 21:30:06 UTC,This change was made by a bot.
1810058,2018-12-30 18:59:37 UTC,"You will be told by upstream that Arch Linux is not supported by HPLIP, so you are left to the tender mercies of people like me. :)"
1810058,2018-12-31 20:47:45 UTC,I realise now the purpose of the original post was to propose a patch and not to ask for help. Apologies for the noise.
1810058,2019-01-01 23:17:32 UTC,"I don't think it's a CUPS issue, but I'm running CUPS 2.2.10."
1810058,2019-01-04 18:30:00 UTC,"> I don't think it's a CUPS issue,...
"
1810064,2019-01-03 19:25:37 UTC,"Due to the nature of this bug (a completely frozen screen, it isn't possible to get a log."
1810064,2019-09-30 16:43:56 UTC,"This bug seems to affect my dell laptop as well (amd r6 with radeon video) when attempting to install either lubuntu or kubuntu versions 18.04.04, or 18.0.02 with a 4.15.x kernel. I think it may be related to the kernel itself as the bug seems to be related to hwe. I am going to try and do a lean install with ubuntu desktop and see if i can recreate my issue and apport."
1810064,2019-01-24 00:04:33 UTC,I DL'ed the 19.04 image and it seems to be working very well. I DL'ed from here: http://cdimage.ubuntu.com/daily-live/current/
1810064,2019-01-18 06:30:55 UTC,Please give 18.10/19.04 daily image a try.
1810064,2019-01-02 14:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810064,2019-01-01 19:44:46 UTC,"""The following symptoms typically are due to GPU issues in the kernel DRM driver (linux package):"""
1810064,2018-12-30 12:08:26 UTC,"Well, I went over to https://wiki.ubuntu.com/Bugs/FindRightPackage and looked under Graphical Environment. I read the following test:"
1810064,2018-12-30 04:16:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1810064,2019-01-02 14:17:55 UTC,Thanks! Finally got it to work.
1810065,2019-01-29 23:43:37 UTC,"I have been affected by the same issue (except it was the CentOS installer, booted in CSM while the system on the hard rive was EFI). I have already reported the bug to CentOS. I used boot-repair but it did not help; I later stumbled onto the solution while experimenting (I could ont google it out). Boot-repair should fix this issue."
1810070,2018-12-30 08:35:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1810070,2019-04-22 03:51:02 UTC,"> Laptop does not support UEFI
"
1810070,2019-11-09 21:31:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810070,2019-11-09 21:35:43 UTC,I am getting exactly the same error messages on my Fujitsy Lifebook E751.
1810070,2019-11-30 18:00:07 UTC,"I can confirm the same error on the Lifebook S761.
Any solution? You cannot run any Linux Live Distribution from USB."
1810074,2019-11-13 17:13:35 UTC,Bugs in the snap version of handbrake do not belong here.
1810075,2019-09-03 07:06:47 UTC,Lubuntu 19.10 QA-test.
1810075,2019-10-28 13:11:17 UTC,"Lubuntu 20.04 QA-test  (from QA-test comments)
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1810075,2019-04-20 05:01:30 UTC,Upstream bug report : https://github.com/lxqt/lxqt/issues/1709
1810075,2021-02-23 08:29:54 UTC,Fresh Lubuntu hirsute (2020-02-22.1) QA-test install on d755-8 box
1810075,2019-12-01 10:24:47 UTC,"This bug is marked against `lxqt-panel`; and was filed upstream (LXQt). Upstream LXQt linked a number of bugs, and have now said they aren't LXQt bugs, but an bug/issue in `openbox`."
1810075,2019-04-05 05:16:42 UTC,QA-TEST 2019-04-05  (AEST (au) local time) -- comments from test
1810075,2021-02-25 07:24:24 UTC,"I just re-created this on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
using Lubuntu hirsute daily (live QA-test)."
1810075,2019-03-19 04:20:16 UTC,"QA-test (19.04 daily) on same dell 755 (c2d, 8gb, radeon rv610)
i changed the right-side monitor so it was rotated left (look at picture for clue)
head /etc/apt/sources.list says i'm using 20190318"
1810075,2019-03-15 07:34:51 UTC,"QA-test (19.04 daily) on same dell 755 (c2d, 8gb, radeon rv610)
i changed the right-side monitor so it was rotated left (look at picture for clue)"
1810075,2019-02-22 04:46:08 UTC,"QA-test on dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) today on 19.04 daily - issue remains."
1810075,2018-12-30 11:25:49 UTC,"Could be related - https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1810079
Both are menu's not appearing where expected (just not the same place)"
1810075,2018-12-30 10:07:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1810075,2019-04-02 03:33:33 UTC,Lubuntu 19.04 daily QA-Test comments -
1810079,2019-12-12 05:44:12 UTC,"Lubuntu 20.04 QA-Test on
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1810079,2019-11-16 17:49:12 UTC,Closed per OP.
1810079,2019-11-12 07:02:58 UTC,"Lubuntu 20.04 QA-Test  2019-11-12 test on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1810079,2019-10-25 06:12:28 UTC,"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
purpose of this test is to start looking for old bugs & confirm focal impacted; these bugs are old & upstream issues and will impact very few end-users (impact me thus why chased)
boot up; adjust displays to match my setup (default-right display is below other display)
..
added panel & menu etc to it (my lower display), menu was unusable :(  - https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1810079"
1810079,2019-01-18 07:39:01 UTC,"QA-test on same hardware ""hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"""
1810079,2018-12-30 11:25:21 UTC,"Could be related - https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1810075
Both are menu's not appearing where expected (just not the same place)"
1810079,2018-12-30 11:07:16 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1810079,2019-04-25 02:05:48 UTC,FYI: this also occurs on debian buster's weekly ISO of 2019-04-22 06:17
1810086,2019-01-22 20:19:10 UTC,"Thanks for the report, we need to review the changes to see if those are bugfixes only"
1810086,2019-01-26 17:25:52 UTC,I have been using the deb from Cosmic since I opened this bug without problems so far. It fixes the buggy seek slider as described above.
1810087,2018-12-30 14:30:03 UTC,This change was made by a bot.
1810092,2019-01-09 02:57:20 UTC,It looks like the compiler has failed!?
1810092,2019-02-12 15:09:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810096,2018-12-30 18:00:24 UTC,apport information
1810096,2018-12-30 18:12:22 UTC,"It's not easy to do an APPORT execution under WSL because firefox is very slow to respond and the display server mixes a bit.
  I have a screenshot."
1810096,2018-12-30 17:55:56 UTC,apport information
1810096,2018-12-30 17:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810096,2018-12-30 17:36:47 UTC,apport information
1810096,2018-12-30 16:59:48 UTC,Result of the commande non the terminal:
1810096,2018-12-30 17:50:50 UTC,apport information
1810097,2019-01-07 10:25:34 UTC,Please run this command and send us the output:
1810097,2019-01-07 15:54:34 UTC,Hallo!
1810097,2019-01-08 03:30:18 UTC,Thanks. This means the kernel can't detect anything plugged into HDMI:
1810097,2019-01-08 11:06:19 UTC,"Hello!
Many thanks for your help. The cable I have changed and connected
another monitor. Always the same result.
Best regards"
1810097,2019-01-09 02:21:54 UTC,In that case this is either a problem with the HDMI socket on the computer or a kernel bug.
1810097,2019-01-09 02:30:06 UTC,This change was made by a bot.
1810099,2019-04-13 10:45:57 UTC,"no edit option in launchbad?
macOS is 10.13.6 not 10.14.4"
1810099,2019-04-13 10:14:01 UTC,Retested and unable to reproduce.
1810099,2018-12-30 22:35:01 UTC,Is this from side effect from moving to Qt 5? Was performance better with 2.1?
1810099,2018-12-30 22:24:03 UTC,"Same on macOS 10.14.2 (18C54) with latest master
Macbook pro 2018 with automatic graphics switching
Qt 5.12.0 via homebrew
OpenGL: 4.1"
1810099,2018-12-30 17:22:48 UTC,"By unusable, I mean there are multiple seconds of GUI lag for any action (clicking play, scratching a waveform, etc.)."
1810099,2018-12-30 17:40:16 UTC,Can you reproduce this with --safeMode? Which macOS SDK do you build with?
1810099,2018-12-30 17:23:26 UTC,"Lots of hypotheses about potential root causes for this, I'll add some more comments and a video to better demonstrate the symptoms."
1810099,2019-04-28 13:06:53 UTC,@jus do you have a retina mac to try and reproduce this? could you test if this problem persists in current master?
1810099,2018-12-30 19:32:26 UTC,"10.13 SDK on macOS 10.13.6 built via Homebrew, not using the official build environments. But the 2.2.0 release binary has this problem too."
1810099,2019-06-02 09:27:10 UTC,"retested:
macbook pro 2017
macOS 10.14.5
mixxx 2.3.0-alpha-pre (build master r6796)"
1810100,2018-12-30 17:36:49 UTC,Printer used is a Canon Pixma MG6850
1810102,2018-12-30 18:36:03 UTC,I'm not familiar with other Linux desktop applications that allow one to change the language. Perhaps you could list some?
1810102,2018-12-30 21:46:05 UTC,"Sure - Darktable, GIMP, Inkscape, all give that choice as an interface option, I believe Libreoffice too but because mine came with english UI I didn't really fiddle with it."
1810105,2018-12-30 19:32:55 UTC,I do not see this bug. Did you check if it affects another user account too?
1810105,2018-12-30 19:54:34 UTC,"Yes, it happens with a new user."
1810105,2018-12-30 20:05:38 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1810105,2018-12-30 20:24:06 UTC,It seems that this happen only if using the QEMU -device virtio-tablet-pci
1810105,2019-11-07 17:43:45 UTC,I finally found a real computer on which this bug is present.
1810105,2019-11-11 06:40:55 UTC,"If it's reproducible with real hardware, then it's definitely not a bug of QEMU ==> Removing QEMU from this bug ticket."
1810109,2018-12-30 20:00:19 UTC,"In fact, reading it again, there might be two ""Terminator""... But the listed features are so similar... Please someone help me clarify this"
1810109,2018-12-31 12:23:52 UTC,It's quite obvious to me that the Wikipage you've found describes just another Terminator than this one. The Wikipage links to this project here which is written in Java and has gotten the last update in 2015 (last release in 2014): https://code.google.com/archive/p/jessies/wikis/Terminator.wiki
1810115,2019-01-06 16:46:19 UTC,Fixed in x.4333.
1810120,2020-08-26 08:37:51 UTC,"I've tried to change the keyboard type : from USB to PS/2 connection.
No change in Nemo: After some directory creations and/or renaming keyboard is lost by Nemo but continue to work properly with other programs."
1810120,2020-08-19 22:07:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810120,2020-08-19 21:59:38 UTC,"Exactly the same problem but in Mint 19.3 cinnamon.
He accepts to rename one or 2 files with the keyboard and then lost it."
1810126,2019-02-09 14:08:16 UTC,This seems to at least help:
1810129,2019-04-01 16:25:10 UTC,Not sure if blake support is in TLS certificates.
1810129,2019-04-19 14:44:14 UTC,"> did you try to use sha3-512 and did that work?
"
1810129,2019-06-10 23:19:40 UTC,I don't think it follows.
1810129,2019-06-10 23:21:20 UTC,(specifically published RFCs defining the relevant digest-algo / signature types format to be used in x.509 certificates / or any pki generically. Just the definition of the math to calculate the digest is not enough)
1810130,2020-06-25 04:10:47 UTC,This is not necessarily a duplicate of bug 1884288 for they don't share the same symptoms judging from the information available till now. This one has:
1810130,2019-05-11 04:17:32 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1810130,2019-03-12 04:10:37 UTC,Mark this Incomplete for the request in #12
1810130,2019-02-21 16:20:48 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1810130-2/"
1810130,2019-01-10 21:09:12 UTC,"Not working.
V5.0RC_1 - also not"
1810130,2019-01-07 04:03:32 UTC,Please test this kernel out:
1810130,2019-01-01 16:08:22 UTC,"No, not at all.
Am 01.01.2019 07:01:00 schrieb Kai-Heng Feng <email address hidden>:
Does the touchpad work after a cold boot?"
1810130,2019-01-02 17:12:00 UTC,kernel-bug-exists-upstream
1810130,2019-01-02 04:40:24 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0]."
1810130,2019-01-03 07:25:54 UTC,Please attach dmesg under v4.20.
1810130,2019-01-01 05:55:53 UTC,Does the touchpad work after a cold boot?
1810130,2018-12-31 00:30:07 UTC,This change was made by a bot.
1810132,2018-12-31 17:33:40 UTC,"le lien est un href=""#"", avec un javascript pour ouvrir la vraie cible.
donc en fait ce n'est pas forcément la page d'accueil qui s'affiche dans un nouvel onglet, mais l'url actuelle suivie de #, ce qui a pour effet de ré-afficher la page courante."
1810134,2018-12-31 13:45:53 UTC,"the difference is probably caused by the fact that, on non-Windows systems a GTK dialog is used, while on Windows a native Windows dialog is used instead."
1810134,2020-01-25 10:20:45 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1810143,2019-11-15 20:34:47 UTC,Thanks for the report. Fix applied at https://git.launchpad.net/lightdm-gtk-greeter/commit/?id=a8e3bdbcf19bd88159dfd847efd34de041ff75a2
1810148,2019-01-17 15:33:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/631533"
1810148,2019-09-23 03:39:36 UTC,"Reviewed:  https://review.opendev.org/631533
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=26a7bc33428c4aee288f57709127e6b15fd64916
Submitter: Zuul
Branch:    master"
1810148,2019-09-26 09:16:40 UTC,This issue was fixed in the openstack/ceilometer 13.0.0.0rc1 release candidate.
1810151,2018-12-31 12:00:06 UTC,This change was made by a bot.
1810154,2020-01-08 01:52:25 UTC,"The verification of the Stable Release Update for plymouth has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1810154,2019-12-24 03:35:23 UTC,"I've confirmed that after upgrade to plymouth from unstable, the testcase passes (and zfs initramfs decryption works now in Ubuntu 19.10)."
1810154,2020-01-08 01:54:46 UTC,This bug was fixed in the package plymouth - 0.9.4git20190712-0ubuntu4.1
1810154,2019-12-16 11:22:59 UTC,"Hello Andreas, or anyone else affected,"
1810154,2019-12-17 20:35:47 UTC,"As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of plymouth from eoan-proposed was performed and bug 1856712 was found.  Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the ""verification-failed-eoan"" tag from this bug report and add the tag ""bot-stop-nagging"" to bug 1856712 (not this bug). Thanks!"
1810154,2019-12-12 23:20:21 UTC,"To clarify, as those questions were asked on IRC:
1. I'm the author of the patch.
2. The bug exists only in Ubuntu, not in upstream version of plymouth - it's caused by the changes included in ""misc-changes.patch"" (that I'm not touching with at 30 foot pole)."
1810154,2019-11-12 00:24:52 UTC,"The attachment ""cached-password-fix.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1810154,2019-11-11 23:04:50 UTC,"There's a bug in processing cached password replies from plymouthd which causes this assertion,  the attached patch fixes this issue (it happens e.g. when using ZFS with native encryption)."
1810154,2019-11-11 23:00:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810154,2019-12-14 22:33:20 UTC,This bug was fixed in the package plymouth - 0.9.4git20190712-0ubuntu5
1810157,2019-01-02 10:45:22 UTC,This is the first time that a Ubuntu release has failed to install for me. In fact it bricked my Acer Aspire S7 (which is this report). Luckily I managed to reinstall 16.04 without problems.
1810160,2019-05-11 16:30:09 UTC,There are privacy and ethics problems with using codepad.org because it uses Amazon AWS.  See:
1810161,2019-07-10 22:19:14 UTC,"Fixed in revision 5c43924338d74b1e5cc6fa9833a9bd16e603ac04
https://git.launchpad.net/kicad/patch/?id=5c43924338d74b1e5cc6fa9833a9bd16e603ac04"
1810161,2019-06-24 12:57:27 UTC,"@Jeff, I changed my mind about using one symbol per file symbol libraries.  The reason is due to inheritance.  If you split an inherited symbol over multiple files, you would have to copy all relevant files to another library path ensure that the symbol was not broken.  This would not be very portable compared to the fully self contained footprint files.  The other issue is the number of file stats that happen when loading footprint libraries.  Way back when our libraries where not as complete as they are now, this was not a big issue.  There are probably an order of magnitude more symbols than footprints so this problem is compounded.  Your fp-info-cache work has made me rethink the whole per file library concept.  At the time it seemed like a good idea.  Now I'm not so sure."
1810161,2019-06-24 09:29:16 UTC,"@Wayne, will the 6.0 symbol libraries be moving to the FP library architecture (one file per symbol)?  If so, it probably doesn't make sense to fix this...."
1810161,2018-12-31 22:15:14 UTC,Footprint libs do indeed report at the end. Symbol libs however give me an error message per missing lib. The progress bar stops until i click ok. If another lib is missing i get another message.
1810161,2018-12-31 22:04:19 UTC,"Are you sure about this, Rene?  We currently load footprint libraries in parallel threads, so we can't do anything /but/ wait till the end to report errors."
1810167,2021-01-23 10:49:51 UTC,Arch Linux Package was updated to 2.1-1~bzrev43 today :)
1810167,2021-01-03 17:41:32 UTC,Thank you!
1810167,2021-01-02 22:49:20 UTC,Thanks! I flagged the arch linux packages as out-of-date with reference to this bug-thread.
1810167,2020-12-29 20:02:30 UTC,Sorry for the delayed answer. The version should be qtqr-2.1-0~rev43.
1810167,2020-12-24 09:44:16 UTC,"Thanks, same to you! Which Version will contain that bugfix? (I have arch linux actually, so I have to wait for our maintaner here https://archlinux.org/packages/community/any/qtqr/)."
1810167,2020-12-24 09:16:52 UTC,Thank you Pokulo. I've merged your branch into trunk. The fix should be available in the Daily PPA soon.
1810167,2020-12-23 13:41:58 UTC,finally pushed my branch to https://code.launchpad.net/~pokulo/qr-tools/bugfix_wifi_code_hidden_flag
1810167,2020-12-23 13:31:31 UTC,"Indeed. I first found an old fork on github, which confused me. I am currently trying to crate an push a new branch with bazaar, but I am completely new to this. Its a one-character fix. Do you need a branch (not even shure if you have Pull requests in bazaar)?"
1810167,2020-12-23 12:43:02 UTC,Hi!
1810167,2020-12-23 12:20:55 UTC,"Changing  ""[H:]+(.*)"" to  ""[H:]*(.*)"" helped in my case, Will create a pull request on GitHub :)"
1810167,2020-12-23 12:08:23 UTC,"Actually the current code differs from original post, so my stack trace looks different as well:"
1810167,2020-12-23 11:58:10 UTC,This bug keeps qtqr failing when scanning WIFI qr codes generated by FritzBox. Attached a PNG of the failing QR Code. Its content is:
1810167,2020-01-04 04:17:39 UTC,[Expired for QR Tools because there has been no activity for 60 days.]
1810167,2019-11-04 22:20:25 UTC,Hello!
1810173,2019-02-20 05:50:23 UTC,"Reviewed:  https://review.opencontrail.org/49385
Committed: http://github.com/Juniper/contrail-ansible-deployer/commit/6d56f894b1547baddfc84059e0f6ab3cd34dec8e
Submitter: Vinay Vithal Mahuli (<email address hidden>)
Branch:    R6.0-WIP"
1810173,2019-01-08 13:59:07 UTC,"Reviewed:  https://review.opencontrail.org/48483
Committed: http://github.com/Juniper/contrail-ansible-deployer/commit/b947f6c6b88e3910d9aa6049f6988b3ff6e733d5
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1810173,2019-01-04 15:14:11 UTC,"Review in progress for https://review.opencontrail.org/48483
Submitter: Michal Clapinski (<email address hidden>)"
1810173,2019-01-02 18:32:23 UTC,"Reviewed:  https://review.opencontrail.org/48405
Committed: http://github.com/Juniper/contrail-ansible-deployer/commit/91e748ba79dca6d29e4cb3b7b9e28371209bd82c
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1810173,2018-12-31 20:02:48 UTC,"Review in progress for https://review.opencontrail.org/48405
Submitter: Michal Clapinski (<email address hidden>)"
1810176,2020-07-11 09:51:47 UTC,"The Mint workaround almost worked for me. I am also on 20.04. I moved a file out of my target folder and into a new folder on the same level. The files in both folders became accessible. I moved the file back into the original folder and the folder became inaccessible again. When I try to move any files from my computer into the target folder, the folder once again becomes inaccessible. After a few minutes of nothing happening, I get the message, ""Error While Copying: There was an error creating the folder ""folder_to_transfer"". File not found"". After that, if I leave the folder and go back in, I can no longer access the files. I get the same error I originally did: ""Location could not be displayed: Sorry, could not display contents of ""target_folder"": libmtp error: could not get object handles of [hex]"""
1810176,2020-06-27 09:38:27 UTC,I have the same problem on Linux Mint 18.3 (Ubuntu derivitive). I could access files and folders except for the folder containing a whole lot of images. Error message was:
1810176,2020-06-08 01:18:42 UTC,Experiencing the same problem on Ubuntu 20.04 when trying to copy files to DCIM/Camera folder on Android Samsung a20 device.
1810176,2020-04-27 20:15:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810176,2019-10-11 18:56:48 UTC,I am experiencing the same issue on Ubuntu Budgie 18.04.3 LTS bug when trying to copy .mp3 files via USB to an encrypted SD inside a Sony Xperia ZX2.
1810176,2019-09-13 04:17:29 UTC,[Expired for libmtp (Ubuntu) because there has been no activity for 60 days.]
1810176,2020-04-27 07:51:59 UTC,hello experiencing the same issue on ubuntu 20.04 lts bug when trying too see content of my music folder in sd card sumsung galexy m20
1810176,2019-06-08 13:20:14 UTC,"It seems it got fixed somehow, and i can open folders on my phone's micro-sd card again"
1810176,2019-05-08 16:14:22 UTC,My cell phone is a Samsung Note 3 (SM-N9005) running Android 5.0.
1810176,2019-03-25 08:12:41 UTC,"Just the same issue with my Galaxy C5 PRO, when i'm  trying to get access to Сamera folder inside DCIM  folder on the micro-sd card. Both with Ubuntu 16.04 and Ubuntu 18.04 (default nau managers)"
1810176,2019-03-18 11:17:03 UTC,"Thank you for your bug report, could you try on a recent Ubuntu verison (maybe from a liveCD) if that's still an issue?"
1810176,2019-03-16 19:42:44 UTC,"Similar error here.
Can copy file from Phone folder, but if I try to access Camera folder (inside DCIM folder), Nemo shows this error after some time processing."
1810176,2019-03-16 19:39:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810176,2019-07-15 02:40:49 UTC,I am experiencing this problem on Ubuntu Mate 18.04.2 reading/writing the
1810179,2018-12-31 23:13:31 UTC,Got a 'bug' message after trying to find a local community to contribute to.
1810183,2020-09-18 08:23:37 UTC,"Hello,"
1810183,2020-09-17 12:20:19 UTC,On my x412da the touchpad is detected as 3 input devices:
1810183,2020-09-03 19:51:07 UTC,"+1 same problem with me, asus UX425JA"
1810183,2020-07-27 07:47:12 UTC,"Same problem for me :
Asus Vivobook M433I Model S433IA-EB372T with AMD Ryzen 7 47000 processor
OS : Linux Mint 20 based on Ubuntu 20.04 with Kernel 5.8 RC6"
1810183,2020-06-28 12:14:52 UTC,Same here:
1810183,2020-06-19 18:32:24 UTC,"Same here w/
- UX431FA
- Ubuntu 20.04"
1810183,2020-05-12 09:57:12 UTC,Same here +1
1810183,2020-04-13 08:28:29 UTC,sudo dmidecode -t bios -t system
1810183,2020-04-13 08:32:16 UTC,":~$  uname -a
Linux laptop 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux"
1810183,2020-09-18 09:13:32 UTC,"I had the same thought reading the last message,
best wishes to everyone that will try to solve the problem that is sadly
ignored by the official developers.
Many thanks, If you need any kind of support providing logs of any other
things please let me know, I will be happy to help.
Cheers,
Andrea"
1810183,2020-04-13 08:22:58 UTC,Even flashing Asus UX433 BIOS with last version had not effect on the numpad :-/
1810183,2020-04-13 08:19:26 UTC,"With some code modification, this last solution just above works on a UX433 BUT this does not allow to switch the numpad light ON :'(
So very hard to use."
1810183,2020-03-24 14:44:53 UTC,"My reply seems to have been removed, but this worked for me.
https://gitlab.com/Thraen/gx735_touchpad_numpad"
1810183,2020-03-24 03:57:45 UTC,"While not an actual driver...I found this utility on reddit...It's a python script that checks for the mode, and if you're in the num pad mode, it evaluates position of tap and sends numpad presses.  Works for me!"
1810183,2020-03-14 20:45:27 UTC,+1 affected by this.
1810183,2020-05-02 20:17:11 UTC,Same here!
1810183,2020-09-18 11:11:50 UTC,I got a link from kernel maintainers to a tool that can help to hack Windows i2c bus.
1810183,2020-10-03 12:55:23 UTC,@turboconnard That repo is not useful. It is a python prog that has nothing to do with the touchpad features. It emulates the touchpad capabilities. It can be done on any touchpad.
1810183,2020-09-30 13:35:56 UTC,+1
1810183,2020-03-09 22:11:39 UTC,Same problem here!!!
1810183,2021-02-24 03:07:55 UTC,"So sad, Asus doesn't care about linux users, that's the reality ... Our only hope is a community developed driver for this feature."
1810183,2021-02-21 09:08:42 UTC,"It should advertise the fact that the Asus notebooks do not support linux
and features do not work. Maybe it would push Asus to change strategy."
1810183,2021-02-21 09:00:06 UTC,2 year old thread. I don't think Asus or some other hardware manufacturer wants to fix it anymore. Once again Asus has shown that the linux community is the least of its concerns. Too bad :/
1810183,2021-02-01 22:50:07 UTC,+1 same for me
1810183,2021-01-23 21:19:34 UTC,"Hello,
having the same problem here with my Asus Zenbook 14. It would be great to have such a nice feature in Linux. Let me know if I can be of any help to provide logs or test some patches."
1810183,2021-01-22 22:22:18 UTC,"Maybe it is possible to ask them directly :
http://www.emc.com.tw/emc/en/Product/Solution/TouchpadSolutions"
1810183,2021-01-22 21:22:02 UTC,"@hydrogencl

> I have reported this issue to ASUS support
"
1810183,2021-01-22 09:40:44 UTC,"I have reported this issue to ASUS support. If they don't reply, we have to demand them solve it by the support website:"
1810183,2021-01-14 04:52:53 UTC,Same issue with me.
1810183,2020-10-03 22:44:05 UTC,"Hello,"
1810183,2020-10-03 19:03:05 UTC,"It's a shame that Asus doesn't support Linux.  They make great laptops that a lot of developers use because of it.
  If they continue not to support Linux, personally I will probably start to see what its competitors offer like Huawei for example."
1810183,2020-10-03 17:52:22 UTC,@turboconnard Asus won't help. Their policy is not to support Linux. It can be resolved only by someone who can hack the Windows driver.
1810183,2020-10-03 16:38:20 UTC,"Yep, I know that... the fact is the ""bug"" is here for a long time and apparently it's not going to be resolved soon without the help of Asus. This thread is linked every time someone on the internet ask for help with there laptop so my idea was to investigate the hack/software solution instead of waiting for a proper hardware one."
1810183,2020-10-03 12:41:19 UTC,"Hi, I've got a vivobook X412D and I found this on stackoverflow:
https://gitlab.com/Thraen/gx735_touchpad_numpad/ .
It's not a driver but with a little tweaks in a minute, I managed to get numpad inputs (without leds on and by plugin a usb keyboard).
When ""Num lock"" on the usb keyboard is enabled I get correct values."
1810183,2020-09-22 18:29:22 UTC,"I would be happy to help with this tool but it is too complicated for me... We have to compile the software. If an executable would exist, it will be more simple and I will try to help."
1810183,2020-02-20 20:01:38 UTC,"I've never written drivers before but if someone wants to work on this with me, I'd love to help out."
1810183,2019-12-11 03:03:13 UTC,I have an ASUS Zephyrus-GX501GI and I am affected by this issue (inability turn on the numeric pad).
1810183,2020-01-20 16:47:37 UTC,"+1 (with kernel 5.4.0-2-amd64)
No message with ""dmesg"""
1810183,2019-05-17 19:27:58 UTC,"Not explicity for the numpad. It does, however, show entries when changing the keyboard backlight as well as the monitor backlight."
1810183,2019-05-17 15:36:09 UTC,Does acpi_listen show anything?
1810183,2019-05-17 13:22:10 UTC,"+1 also, affected by this issue"
1810183,2019-04-27 23:14:50 UTC,dmesg reports nothing when pushing the button to activate the button.
1810183,2019-04-14 19:33:08 UTC,"Hello, I buy almost same asus Zenbook UX433FN and I have the same problem : numpad doesn't work.
I didn't find any driver running on ubuntu...
My config is ubuntu 18.04.2 LTS"
1810183,2019-04-09 05:39:02 UTC,Please attach dmesg after the hotkey gets pressed.
1810183,2019-03-09 04:17:17 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1810183,2019-01-07 05:19:58 UTC,Seems like there's no driver support yet for this new feature.
1810183,2019-01-05 00:15:25 UTC,"""kernel-bug-exists-upstream"""
1810183,2019-01-04 22:01:22 UTC,"I just got the same laptop today, and am having the same problem (although I'm running Linux Mint 19.1 instead of Ubuntu directly).  I'm still getting things set up, but will get the 4.20 kernel installed as soon as I can and try this..."
1810183,2019-01-03 18:28:24 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0]."
1810183,2019-01-03 17:19:36 UTC,apport information
1810183,2019-01-03 17:19:35 UTC,apport information
1810183,2019-01-03 17:12:41 UTC,apport information
1810183,2019-01-03 17:12:40 UTC,apport information
1810183,2019-06-05 23:31:43 UTC,+1 also affected by this. I have an ASUS ROG Zephyrus S which also had a touchpad/numpad.
1810183,2019-01-03 11:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810183,2019-06-14 06:32:17 UTC,+1 also affected by this. Kubuntu 18.04 kernel 5.0.0-050000-generic on Asus ZenBook UX433FN
1810183,2019-07-09 13:30:38 UTC,"Oh please run evtest on ""AT Translated Set 2 keyboard"", ""Asus WMI hotkeys"" or ""00:16:94:31:EF:23""."
1810183,2020-01-11 04:36:37 UTC,Similar defiled experience on ASUS Zenbook 14 UM431D with Ubuntu 19.10.
1810183,2019-12-20 14:37:23 UTC,"+1 (with kernel 5.3.0-24)
No message with ""dmesg""
No input with ""xinput test"""
1810183,2019-12-11 01:04:03 UTC,+1 also affected by this.
1810183,2019-12-07 08:31:07 UTC,"Hi everyone, same here with ubuntu 19.10 and with asus vivobook S14 X420F."
1810183,2019-10-24 19:53:40 UTC,Same with the ASUS Zenbook UX333FA on Ubuntu 19.10.
1810183,2019-10-19 00:22:51 UTC,"Same here, How can we help to solve it?"
1810183,2019-06-15 14:30:32 UTC,"+1
Using Zenbook UX433FN, Ubuntu 18.04, kernel 4.20.6-042006-generic."
1810183,2019-10-18 20:18:15 UTC,"Same here, on Ubuntu 19.10 with kernel 5.3.0"
1810183,2019-09-26 19:42:14 UTC,"Same here,"
1810183,2019-09-26 15:38:16 UTC,"Same here, UX433FN"
1810183,2019-09-24 00:50:27 UTC,"Same here, UX433FN."
1810183,2019-08-21 11:26:53 UTC,Same with UX433FA and Ubuntu 18.04
1810183,2019-07-17 13:48:16 UTC,+1
1810183,2019-07-17 13:42:29 UTC,+1
1810183,2019-10-01 21:15:52 UTC,Wanted to drop in that I have an asus ROG zephyrus and no touchpad functionality for me either. Anything I can do to help?
1810183,2020-02-20 11:28:49 UTC,"+1 on ASUS Vivobook 14 R424D with kubuntu 18.04 or 19.04.
This feature is usefull for 14 inch notebook."
1810185,2020-12-31 20:53:51 UTC,Bug resolved
1810185,2020-12-31 08:42:49 UTC,any other error message when running grub2-mkconfig as root on command line? This just says that the temporary cfg file was not created.
1810188,2019-01-03 02:43:46 UTC,It looks a little bit like you were trying to upgrade to a newer release that does not support your hardware. Take a look at this table for a guide of supported architectures: https://wiki.ubuntu.com/SecurityTeam/FAQ#Architectures
1810197,2019-01-01 15:03:38 UTC,Tested with some Cosmic chroots and it works nicely.
1810200,2019-05-04 13:13:25 UTC,"There are no logs available since it hasn't been installed, the issue is with the installer."
1810200,2019-05-04 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810200,2019-05-04 12:23:18 UTC,Though this is a workaround and installer should run from a dvd too.
1810200,2019-05-04 12:19:41 UTC,"I solved it eventually, but forgot about this post.
If I remember correctly I had to make a bootable pendrive with the 18.04 installer, because it wanted to modify something, and couldn't do it with live cd.
And how I found this out is a mystery for me right now."
1810200,2019-07-04 04:17:20 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1810200,2019-03-04 09:20:19 UTC,Reverting the spam changes in title and description
1810200,2019-01-02 05:39:42 UTC,"Try ""nouveau.modeset=0""."
1810200,2019-01-01 14:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810200,2019-05-04 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1810207,2019-01-01 18:30:06 UTC,This change was made by a bot.
1810210,2019-01-02 14:30:22 UTC,apport information
1810210,2019-07-28 18:09:45 UTC,"Hi there,"
1810210,2019-01-18 08:51:18 UTC,"Yes, hi I will try this. Sorry have been very busy with work."
1810210,2019-01-18 06:05:50 UTC,"The fix for LP: #1804604 should fix your issue. It's not yet in -generic kernel yet, but you can use linux-oem to verify this issue:
$ sudo apt install linux-oem"
1810210,2019-01-08 17:54:32 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1810210,2019-01-02 14:33:02 UTC,"If this is of any help, the laptop will not boot with any kernel from 4.15.0-34 upwards. 4.15.0-33 seems to be the most recent useable kernel that my laptop will work with."
1810210,2019-01-02 14:30:25 UTC,apport information
1810210,2019-01-02 14:30:24 UTC,apport information
1810210,2019-01-02 14:30:21 UTC,apport information
1810210,2019-01-02 14:30:16 UTC,apport information
1810210,2019-01-02 14:30:19 UTC,apport information
1810210,2019-01-02 14:30:18 UTC,apport information
1810210,2019-01-02 14:30:17 UTC,apport information
1810210,2019-01-02 14:30:15 UTC,apport information
1810210,2019-01-02 14:30:13 UTC,apport information
1810210,2019-01-02 14:30:11 UTC,apport information
1810210,2019-01-02 14:30:10 UTC,apport information
1810210,2019-01-01 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810210,2019-01-02 14:30:20 UTC,apport information
1810213,2019-05-22 14:30:31 UTC,Doug Hellman's patch rolling back `cmd2` to 0.8.9 worked for me on Python 3.7.3
1810213,2020-03-12 00:22:58 UTC,Please try my patch: https://review.opendev.org/#/c/712591/
1810213,2019-07-26 22:41:39 UTC,"I just noticed that my copy/paste of the error was from when I was using Python 3.5, but the same error is returned with Python 3.7.3:"
1810213,2019-07-26 22:40:45 UTC,It seems that this problem happens even with the patch mentioned in #8.
1810213,2019-05-17 07:11:28 UTC,"(mistral) workflow-create workflow.yaml
Traceback (most recent call last):
  File ""/usr/local/lib/python3.6/dist-packages/cmd2/cmd2.py"", line 1739, in onecmd_plus_hooks
    statement = self.precmd(statement)
  File ""/usr/local/lib/python3.6/dist-packages/cliff/interactive.py"", line 172, in precmd
    statement.command = cmd_name
  File ""/usr/local/lib/python3.6/dist-packages/attr/_make.py"", line 428, in _frozen_setattrs
    raise FrozenInstanceError()
attr.exceptions.FrozenInstanceError
EXCEPTION of type 'FrozenInstanceError' occurred with message: ''"
1810213,2019-10-11 18:16:41 UTC,This is still broken with python3.7 and cmd2==0.9.18
1810213,2019-02-06 13:18:11 UTC,Same error with python 3.5
1810213,2019-01-02 17:21:55 UTC,"It looks like we're going to have to create a new Statement object there, since they have marked the attributes of the Statement class as frozen. Let me know if you want to work on that. I'm available for code review and other pointers if you need them."
1810213,2019-01-08 18:05:01 UTC,https://review.openstack.org/#/c/629269/1
1810213,2019-02-11 21:48:36 UTC,Same with python 3.6.7
1810213,2019-02-06 13:11:33 UTC,"Hi,
I've got the same issue using Python 3.7 to build a cliff app.
Using Python 2.7 there is no issue."
1810213,2019-01-09 06:37:55 UTC,does 0.9.7 help?
1810214,2019-01-15 09:14:05 UTC,"Looks like it should be fixed with that kernel commit
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=0bea4cc8383519f78f3f74caca7bdebdfb346d3b"
1810214,2020-01-16 04:59:42 UTC,"Hello,"
1810214,2020-03-17 04:17:14 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1810214,2020-04-24 13:47:33 UTC,I think the same bug is here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439?comments=all
1810215,2020-06-01 09:31:41 UTC,See also: https://www.smartmontools.org/wiki/SAT-with-UAS-Linux
1810215,2020-06-01 09:18:50 UTC,"For more information about this issue, see https://askubuntu.com/a/1106020/50254"
1810215,2019-08-09 02:05:38 UTC,"""but we
probably don't need to try any harder tracking down the history of the
Armbian kernel releases here in an Ubuntu bug report..."""
1810215,2019-08-09 01:38:31 UTC,"On Thu, Aug 08, 2019 at 23:50:14 -0000, James Kingdon wrote:

> Hmm, you've got me curious now. It's been a while since I really looked
> at the ARM boards. sources.list.d contains armbian.list which has a
> single entry:
>
> deb http://apt.armbian.com xenial main xenial-utils xenial-desktop
>
> That seems like a reasonable candidate? I don't recall if I used an
"
1810215,2019-08-08 23:50:14 UTC,"Hmm, you've got me curious now. It's been a while since I really looked at the ARM boards. sources.list.d contains armbian.list which has a single entry:"
1810215,2019-08-08 23:26:27 UTC,"On Thu, Aug 08, 2019 at 21:59:50 -0000, James Kingdon wrote:

> source.list is using http://ports.ubuntu.com/
"
1810215,2019-08-08 21:59:50 UTC,source.list is using http://ports.ubuntu.com/
1810215,2019-08-08 18:57:24 UTC,"Yes, hdparm -S. Not sure if it's relevant, but the distro is 16.04.6 LTS (Xenial Xerus) in this case."
1810215,2019-08-08 21:34:22 UTC,"On Thu, Aug 08, 2019 at 18:57:24 -0000, James Kingdon wrote:

> Yes, hdparm -S.
"
1810215,2019-08-08 18:05:55 UTC,"Hi Nathan, thanks for the reply."
1810215,2019-08-08 16:33:49 UTC,"On Thu, Aug 08, 2019 at 15:27:20 -0000, James Kingdon wrote:

> I got hit by this after a power outage cycled my file servers and
> presumably activated a previous automatic kernel update (the servers
> normally stay up for months at a time).
>
> The kernel that is currently running is:
>
> Linux oban8 4.14.111-odroidxu4 #2 SMP PREEMPT Wed May 8 17:30:01 CEST
> 2019 armv7l armv7l armv7l GNU/Linux
"
1810215,2019-08-08 15:27:20 UTC,I got hit by this after a power outage cycled my file servers and presumably activated a previous automatic kernel update (the servers normally stay up for months at a time).
1810215,2019-08-06 01:03:45 UTC,@Mike/Robie:
1810215,2019-01-07 10:17:57 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1810215,2019-01-02 09:04:06 UTC,"> If not is there any way to turn off uas ?
"
1810215,2019-01-02 01:43:14 UTC,It look like there was a patch added to fix this
1810215,2019-01-01 23:17:14 UTC,"> Read Device Identity failed: scsi error unsupported field in scsi command
> ...
> [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a
> ...
> [6041018.009432] usb 3-2.4: Manufacturer: Seagate
> ...
> [6041018.015808] scsi host5: uas
"
1810215,2019-08-08 18:49:34 UTC,"On Thu, Aug 08, 2019 at 18:05:55 -0000, James Kingdon wrote:

> I'm not sure what kernel was there before. I was expecting to see traces
> in /boot but the only references are to 4.14.133.
"
1810220,2020-01-08 17:09:26 UTC,@Mike: No one will look at a report unless a second person has confirmed it. :-(
1810220,2020-01-08 17:08:40 UTC,"It seems to fail on my Kyocera printer name, which I cannot include here, because I had to uninstall print-manager!"
1810220,2019-01-01 23:19:03 UTC,cf. https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044
1810220,2019-06-11 12:41:41 UTC,related (or even identical) bugs:
1810220,2020-01-08 17:05:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810224,2019-01-02 02:10:33 UTC,Upstream: https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/194
1810226,2019-01-02 22:37:48 UTC,[Looks like this is quoting https://github.com/mpv-player/mpv/issues/6124#issuecomment-421444905]
1810226,2019-01-02 23:06:14 UTC,Slightly related to this - I notice libplacebo gained support for glslang[1]. Copying that has the advantage that glslang is already packaged.
1810235,2019-01-28 15:23:49 UTC,I hope my change of bug title clarifies the edge case when this bug occurs. If I have misunderstood I'd appreciate being corrected.
1810235,2019-01-21 20:14:25 UTC,"Possibly, if there is a way to ensure bcache only caches encrypted block data and not the cleartext blocks."
1810235,2019-01-28 15:24:39 UTC,There is no action possible in the bcache-tools package so I'm marking that task as Invalid - but the cryptsetup task remains open.
1810235,2019-01-13 03:00:05 UTC,"Following up and to clarify my initial post a bit, I've found the main issue is with cryptsetup (or related system) expecting LUKS to be located within a certain boundary and bcache creates an offset on the backing drive that shifts this boundary outside where cryptsetup looks. The package should throw an exception or at the least say it didn't find the partition but it fails silently and that will require further investigation."
1810235,2019-01-14 13:36:39 UTC,"Could this be solved with different ordering? Luks first, then bcache? Luks definitely expects its header to be in a certain position:"
1810235,2019-01-25 15:36:03 UTC,It may be that cryptsetup needs to be taught to use offset= and skip= for LUKS as well as plain.
1810235,2019-01-02 05:54:26 UTC,Additional Information:
1810239,2019-01-02 05:32:20 UTC,apport information
1810239,2019-01-02 05:30:09 UTC,"root@mythfe-amd:~# lspci  -knnv -s 01:00.0
01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller [1b4b:9230] (rev 11) (prog-if 01 [AHCI 1.0])
 Subsystem: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller [1b4b:9230]
 Flags: bus master, fast devsel, latency 0, IRQ 56
 I/O ports at f050 [size=8]
 I/O ports at f040 [size=4]
 I/O ports at f030 [size=8]
 I/O ports at f020 [size=4]
 I/O ports at f000 [size=32]
 Memory at f7d10000 (32-bit, non-prefetchable) [size=2K]
 Expansion ROM at f7d00000 [disabled] [size=64K]
 Capabilities: [40] Power Management version 3
 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
 Capabilities: [70] Express Legacy Endpoint, MSI 00
 Capabilities: [e0] SATA HBA v0.0
 Capabilities: [100] Advanced Error Reporting
 Kernel driver in use: ahci
 Kernel modules: ahci"
1810239,2019-01-02 05:30:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810239,2018-08-12 11:41:19 UTC,"I have this issue with ""Marvell Technology Group Ltd. 88SS9183 PCIe SSD Controller"" in my ""Asus Rog Strix Z370-F Gaming"" and solved it by adding ""DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9183,
quirk_dma_func1_alias);"" to ""quirk_dma_func1_alias()""."
1810239,2018-05-14 20:12:56 UTC,"v4.16 already contains a quirk for the Marvell 88SE9230 (added by cc346a4714a5 (""PCI: Add function 1 DMA alias quirk for Marvell devices"") way back in v3.16)."
1810239,2018-05-14 18:09:13 UTC,"(In reply to Bjorn Helgaas from comment #131)

> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=aa0082066343 for Marvell 9128 appeared in v4.16-rc1.
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=832e4e1f76b8 for Marvell 88SE9220 appeared in v4.17-rc1.
>
> Are there any devices that are still broken in v4.17-rc1?  If not, maybe we
> can close this bug?
"
1810239,2018-04-19 17:25:33 UTC,http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=aa0082066343 for Marvell 9128 appeared in v4.16-rc1.
1810239,2018-04-19 02:52:21 UTC,Addendum to the above:
1810239,2019-06-11 17:56:55 UTC,"Christoper, I filed the bug. Anyway I made a mistake. I took the output from lshw where scsi@6 was not populated and I took for granted, that ata6 equals scsi@6 which isn't the case. Therefore I get the mentioned errors on my boot drive.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383"
1810239,2018-01-12 23:32:53 UTC,If you've got the quirk fix and done the testing then I would see Documentation/process/submittingpatches.rst and submit your quirk fix as a patch with an explanation of what it fixes. The change looks correct to me.
1810239,2017-12-29 04:58:14 UTC,Hi There
1810239,2015-11-23 12:34:32 UTC,"There seems to have been a regression sometime after the 4.3 tag (6a13feb9c82803e2b815eca72fa7a9f5561d7861) and before one of the commits on 2015-11-07 (as that's when my kernel was compiled), which causes the same errors in dmesg as Comment #118.
This results in the drives attached to the controller becoming inaccessible."
1810239,2015-08-13 07:11:30 UTC,"(In reply to oh-itsme from comment #124)

> I had found that thread in a websearch as I have encountered similar issues
> as you had, also using a Supermicro X10SBA. I had contacted Supermicro about
> this, but support did not really seem to be aware of this issue, and no
> update for the controller was sent to me.
"
1810239,2015-08-12 21:09:50 UTC,"(In reply to frollic from comment #123)

> For the 9230 you might want to check the updated BIOS we've discussed at:
> http://homeservershow.com/forums/index.php?/topic/9179-marvell-9230-firmware-
> updates-and-such/
"
1810239,2015-08-05 14:21:35 UTC,"For the 9230 you might want to check the updated BIOS we've discussed at:
http://homeservershow.com/forums/index.php?/topic/9179-marvell-9230-firmware-updates-and-such/"
1810239,2015-08-05 14:14:34 UTC,*bump*
1810239,2015-08-03 21:21:08 UTC,Hi.  Old Newbie to kernel things here.  I see from Alex's (initial?) patch at https://github.com/awilliam/linux-vfio/blob/02f8c6aee8df3cdc935e9bdd4f2d020306035dbe/drivers/ata/ahci.c that my 88SE9128 is in the quirks list.
1810239,2019-01-02 05:32:23 UTC,apport information
1810239,2018-04-19 02:31:40 UTC,"I can confirm that this issue occurs with the Marvell 88SE9128 controller on my Gigabyte GA-X59A-UD7 (rev2.0) motherboard. As with Kevin Hunt above, adding a new entry in quirks.c appears to resolve the issue."
1810239,2019-01-02 05:32:25 UTC,apport information
1810239,2019-01-02 05:32:28 UTC,apport information
1810239,2019-06-09 20:21:21 UTC,"Johannes (piktogrammdd+ubuntu), it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux"
1810239,2019-06-08 22:57:23 UTC,"Hi,
I had similar Problems with my Marvell 88EE9230. I was able to improve the situation quite a lot by updating the firmware of the controller itself. In General all firmware versions beyond version 2.3.xxx improved the situation quite a lot. The remaining problem is, that I get failures on ata6 which is the only port which is not connected to any drive at all. Any drive connected to the marvell controller itself is perfectly stable (24/7 for +400 days)."
1810239,2019-03-04 04:40:53 UTC,I've only recently traced the issue to the iommu kernel option. This device has been unstable since I bought it and I pull it out occasionally to see if the driver issues have been addressed.
1810239,2019-01-16 09:11:45 UTC,"Steven Ellis, for you personally:"
1810239,2019-01-02 09:13:59 UTC,"Rebooted with the 4.20.0-042000-generic and the option ""amd_iommu=off"" and the card works"
1810239,2019-01-02 09:10:23 UTC,I attempted a boot with the following upstream kernel packages
1810239,2019-01-02 08:38:57 UTC,"Looks like there is a new upstream issue with
 - https://bugzilla.kernel.org/show_bug.cgi?id=199733"
1810239,2015-06-23 03:25:22 UTC,"(In reply to Alex Williamson from comment #119)

> It's already queued in the pull request for v4.2:
>
> http://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/drivers/
> pci/quirks.c?id=247de694349c2eeea11b8d8936541f5012a09318
"
1810239,2019-01-02 05:37:40 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0]."
1810239,2019-01-02 05:32:42 UTC,apport information
1810239,2019-01-02 05:32:38 UTC,apport information
1810239,2019-01-02 05:32:35 UTC,apport information
1810239,2019-01-02 05:32:34 UTC,apport information
1810239,2019-01-02 05:32:32 UTC,apport information
1810239,2019-01-02 05:32:31 UTC,apport information
1810239,2019-01-02 05:32:29 UTC,apport information
1810239,2019-01-02 05:32:45 UTC,apport information
1810239,2019-01-02 05:32:26 UTC,apport information
1810239,2015-06-23 03:10:07 UTC,"(In reply to Tasos Sahanidis from comment #118)

>
> Could this device id be added to the list of affected devices?
"
1810239,2015-06-15 15:18:19 UTC,`lscpi -nnvv`
1810239,2013-01-20 07:43:58 UTC,"Created attachment 91521
dmesg on Asus P9X79 WS, kernel 3.7.3"
1810239,2013-01-20 07:43:03 UTC,"This problem happens here as well. Asus P9X79 WS, BIOS 3306, X79, i7-3930K. Running kernel 3.7.3. In addition to being unable to use the Marvel SATA controller ports, this causes a ~40s hang during boot."
1810239,2012-12-15 20:30:24 UTC,"I'm seeing similar errors with AMD-Vi (AMD's IOMMU implementation) and a couple of Marvell 88SE9128-based cards, and can confirm that it is still present in 3.7.0 builds."
1810239,2012-05-13 02:24:21 UTC,"Created attachment 73265
lspci output including device capabilities"
1810239,2012-05-13 02:15:59 UTC,"From a pdf file by Intel with title ""Intel® Virtualization Technology for Directed I/O
Architecture Specification"":
--snip--
3.6.1.4 PCI Express Devices Using Phantom Functions
To increase the maximum possible number of outstanding requests requiring completion, PCI Express allows a device to use function numbers not assigned to implemented functions to logically extend the Tag identifier. Unclaimed function numbers are referred to as Phantom Function Numbers (PhFN). A device reports its support for phantom functions through the Device Capability configuration register, and requires software to explicitly enable use of phantom functions through the Device Control configuration register."
1810239,2012-03-27 21:13:08 UTC,"(In reply to comment #6)

> I confirm this bug with kernel 3.2.6: same error with VT-d enabled in bios.
>
> With mainboard ""Asus Rampage III Gene"", Z68, onboard Marvell; CPU Xeon L5520;
> 3x4GB Ram. Logs/Printouts follow this evening.
"
1810239,2012-03-27 21:12:27 UTC,"Created attachment 72735
lspci, asus rampage III gene, z68, vt-d enable, 3.2.13"
1810239,2013-01-20 07:44:34 UTC,"Created attachment 91531
lspci -knvv on Asus P9X79 WS, kernel 3.7.3"
1810239,2012-03-27 21:11:50 UTC,"Created attachment 72734
dmesg intel z68, asus rampage III gene, vt-d enable"
1810239,2012-03-26 12:21:35 UTC,I confirm this bug with kernel 3.2.6: same error with VT-d enabled in bios.
1810239,2012-02-16 23:27:05 UTC,"Created attachment 72420
Output of `lspci -knnv' command"
1810239,2012-02-16 23:24:40 UTC,"Created attachment 72419
config file / kernel 3.2.2"
1810239,2012-02-16 23:23:18 UTC,The same problem occurs on a Z68A-GD65 MSI G3 system Marvell 88SE91xx.
1810239,2012-01-28 17:58:19 UTC,"Created attachment 72219
Kernel config"
1810239,2012-01-28 17:56:30 UTC,"Created attachment 72218
Output of `lspci -knnv' command"
1810239,2012-01-28 17:55:38 UTC,"Created attachment 72217
Output of `dmesg' command"
1810239,2012-03-27 21:10:49 UTC,"Created attachment 72733
kernel config"
1810239,2013-05-14 14:08:46 UTC,"Same problem with Marvell 88SE9172 SATA Controller.
I have Gigabyte GA-Z77X-UD5H with two Marvell 88SE9172 SATA controllers and Intel E3-1245v2 CPU. VT-d is enabled. When running normal Debian 7 or >Ubuntu 12.04 i can see HDDs and SSDs connected to Marvell ports. After installing XenServer 6.1 and Xen Cloud Platform 1.6 - HDDs and SSDs are not detected, but lspci showing that Marvell 88SE9172 controllers are detected."
1810239,2013-02-18 22:01:33 UTC,"FWIW, I still have this issue with 3.7.8 and 3.8-rc7. BIOS update 3401 for the P9X79 WS didn't help. Additionally the hang during boot becomes worse (up to ~65 seconds), when a hard drive is connected. Since the drive is unusable anyway, I hacked the AHCI driver to ignore the Marvell controller. While no solution to this problem, at least my boot time is back to normal (<30s)."
1810239,2013-09-27 20:48:15 UTC,"ZhenHua, can you elaborate on this?  Do you mean a device accessed the MMIO space used to program the IOMMU itself?  If so, how did you conclude that?  I doubt the IOMMU space is at address 0xfff00000."
1810239,2015-06-15 15:13:28 UTC,"Created attachment 179961
dmesg of 4.0.5 patched kernel with iommu=on"
1810239,2015-06-15 15:11:11 UTC,"Created attachment 179951
dmesg of 4.0.5 vanilla kernel with iommu=on"
1810239,2015-06-15 15:05:00 UTC,(In reply to Alex Williamson from comment #95)
1810239,2015-02-04 19:05:06 UTC,"In addition, mobo is brand new (doesn't mean it can't be faulty), WDC drives are 2 months old (installed just before X-mas last year). The SSD was purchased used, so I can't tell you how old that is."
1810239,2015-02-04 19:00:39 UTC,"Indeed, I don't have DMAR errors in my syslog."
1810239,2015-02-04 18:43:27 UTC,"Actually, refreshing my memory in the comments here, others are also reporting that issues for 1b4b:9230 persist, but they're different than the problem we're trying to fix here and suggest either broken hardware or broken driver (or both).  As suggested previously, if you're not getting DMAR faults, file a new bug."
1810239,2015-02-04 18:36:11 UTC,"(In reply to frollic from comment #109)

> Is there any progress ?
>
> I'm hitting this error on Fedora 3.17.8-200.fc20 kernel, which makes my
> system pretty much unusable :(
>
> 07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe
> SATA 6Gb/s Controller [1b4b:9230] (rev 10) (prog-if 01 [AHCI 1.0])
"
1810239,2013-09-27 08:52:58 UTC,"The root cause of this bug seems to be : the device illegally accessed the memory that should be reserved for IOMMU module, and this changed iommu registers."
1810239,2014-11-04 20:40:01 UTC,"The quirk installs entries for both function numbers. If function 1 would have been unknown, you would have seen warnings about presence bit not set (see comment 78 as example). The lack of those messages indicates that you successfully installed entries for both function 0 and 1, hence that the patch is working."
1810239,2015-02-04 18:21:06 UTC,Is there any progress ?
1810239,2014-11-04 10:57:06 UTC,"Accidentally created an attachment. Can't seem to find any way to remove it.
Sorry about that... Please feel free to remove it if possible."
1810239,2014-11-04 10:46:27 UTC,"Created attachment 156481
attachment-10507-0.html"
1810239,2014-10-27 15:22:29 UTC,"Created attachment 155441
dmesg linux 3.17"
1810239,2014-10-25 11:50:26 UTC,"I tried with all of the kernel options you recommended, and also included dmesg with intel_iommu=on and intel_iommu=off for comparison. Regardless of the other kernel options, the SSD is not visible when intel_iommu=on"
1810239,2013-09-30 07:11:03 UTC,"Each context_entry has a present bit. If a context entry is used for a device, but its present bit is not set to 1, an error with fault number 2 will occur."
1810239,2013-09-30 05:02:30 UTC,"Created attachment 109981
Patch with quirk for incorrect PCI requester IDs"
1810239,2013-09-29 07:30:39 UTC,"Hi guys,"
1810239,2014-11-04 19:11:24 UTC,"My kernel lives on another disk drive. /dev/sda1 is my EFI system partition, /dev/sda2 is the MSR, /dev/sda3 is NTFS Windows 7, /dev/sda4 is my / partition. Marvell controller is the SSD on /dev/sdb. I don't know what you mean by ""preset bit"" (sorry, I'm not so fluent in C)."
1810239,2015-06-23 02:35:58 UTC,"I believe I am affected by the same bug with the Marvell 88SE9120 controller on an ASRock 990FX Extreme 4 motherboard.
Although there are no DMAR errors in dmesg, when AMD's IOMMU is enabled in the bios I get the following a couple of times, before it gives up"
1810241,2019-01-18 23:29:47 UTC,"The tar maintainers have disclosed the issue via the commit, so that sounds fine to me."
1810241,2019-03-22 18:47:16 UTC,Use CVE-2019-9923.
1810241,2019-03-07 20:22:10 UTC,"The attachment ""patch against git head"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1810241,2019-01-16 02:16:58 UTC,This has been fixed in git: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=cb07844454d8cc9fb21f53ace75975f91185a120
1810241,2019-01-03 14:11:00 UTC,"Hi Seth,"
1810241,2019-01-03 02:46:55 UTC,"Hello Daniel, very nice."
1810241,2019-01-18 19:05:08 UTC,Can I make this bug public?
1810260,2019-01-02 06:46:30 UTC,There is no validation done while setting the quota values. Hence leads to setting the quota values even less than the usage value.
1810267,2019-01-02 07:30:07 UTC,This change was made by a bot.
1810267,2019-01-07 20:38:11 UTC,Did this issue start happening after an update/upgrade?  Was there a prior kernel version where you were not having this particular problem?
1810271,2019-01-02 07:40:13 UTC,"After I changed the ""connection_info"" in nova and cinder database by hand, I have hard-rebooted instance, then the instance is working well."
1810274,2019-07-15 14:08:16 UTC,great!
1810274,2019-01-21 06:52:25 UTC,"Thanks Liviu,"
1810274,2019-01-09 12:31:42 UTC,"The next schedule release is 9-2019-q4-major, expected 2019-12-31.
Was there ever an out of schedule bugfix release of GNU Arm Embedded Toolchain?"
1810274,2019-01-09 12:15:59 UTC,"The bug upstream was fixed, now all is needed is a new Arm release to include this fix."
1810274,2019-01-05 14:57:03 UTC,https://sourceware.org/bugzilla/show_bug.cgi?id=24065
1810274,2019-01-05 14:00:19 UTC,"I also tested on a 32-bit Linux virtual machine, and the behaviour is the same, objcopy fails with something like '64-bit address 0x4a2a7708000000 out of range for Intel Hex file'."
1810274,2019-01-05 13:33:20 UTC,"Hi All,"
1810274,2019-01-20 15:32:40 UTC,In the mean time those interrested on a fixed toolchain can use the GNU MCU Eclispe binaries:
1810274,2019-01-05 04:01:08 UTC,"Speaking of which, why is launchpad not offering 64 bit windows binaries at all? in the year of 2019 is not that a bit weird?"
1810274,2019-01-05 03:37:49 UTC,"I did a new test on a  64-bit Win 10 virtual machine, and it confirms my hypothesis, the 64-bit build of MCU Eclipse ARM GCC works:"
1810274,2019-01-04 22:30:12 UTC,"> C:\Program Files (x86)\GNU Tools ARM Embedded\8 2018-q4-major\bin\arm-none-eabi-objcopy.exe: test.hex 64-bit address 0x4b4fa300000000 out of range for Intel Hex file
"
1810274,2019-01-04 13:44:19 UTC,The toolchain from 'https://gnu-mcu-eclipse.github.io/blog/2019/01/03/arm-none-eabi-gcc-v8-2-1-1-1-released/' produces the same error.
1810274,2019-01-04 09:47:06 UTC,An alternative source for high quality gnu gcc embedded arm compiler packages is: gnu-mcu-eclipse
1810274,2019-01-03 07:35:01 UTC,Temporary workaround
1810274,2019-01-02 12:22:48 UTC,"It seems that this affects the Windows build, but not the Linux build."
1810274,2019-01-05 13:08:01 UTC,We have a report that gcc 8.2.1 from August build is NOT affected. Complete version line of NOT affected version:
1810275,2020-10-06 07:39:44 UTC,"Any update on this issue? We are facing the same situation with queens and luminous!
Not event the replication_status on volume is getting enabled after the retype."
1810278,2019-01-28 17:02:56 UTC,"This might need more investigation, but it could be an issue with rendering options recursively since the plugin option you're referencing here is actually a keystoneauth configuration option, which is just consumed by keystonemiddleware."
1810278,2019-01-29 03:09:37 UTC,@Lance
1810285,2019-01-03 18:45:16 UTC,"Hi,"
1810286,2019-09-24 14:37:37 UTC,Ran into this too. Went Q -> R -> S
1810287,2019-07-22 04:43:37 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1810288,2019-01-09 21:26:25 UTC,Might have to do with GTK not being able to set the highlight background color
1810293,2019-01-02 12:00:06 UTC,This change was made by a bot.
1810296,2019-01-02 12:26:03 UTC,This should do the trick:
1810296,2019-08-02 15:50:29 UTC,"Might this be a local issue, Chris? circ.selfcheck.patron_password_required's datatype is bool and I'm seeing nothing in the commit history that indicates that it was ever otherwise in stock Evergreen. As is, your patch breaks the check in master."
1810297,2019-01-12 16:51:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810299,2019-01-12 09:17:30 UTC,"for the first whish, in what window, can you add a small screenshot ?"
1810299,2019-01-14 18:03:57 UTC,"Sorry, just getting back home. I don't have a beta home app running, only
my production so I am not comfortable showing the screen with the cash
transactions but it is the screen where you add you daily account
transactions that has the Payee, Category, Status, Expense, Income, and
Balance.  The Balance column is the one that I suggested making the lowest
balance into the future bold."
1810299,2019-09-17 21:05:37 UTC,When will the next version be released?
1810299,2019-09-21 14:34:26 UTC,"once it is finished, for now planned as RC on oct. 6th
but this may slide a little depending my free time"
1810299,2019-09-21 23:50:14 UTC,Thank you
1810299,2020-01-06 23:32:09 UTC,Thank you for your ongoing support. Will these fixes be in the next release?
1810299,2020-04-21 17:36:09 UTC,"This was committed to 5.3, and I am running 5.4 - Running against GTK+ 3.24.14.
I'm not sure I'm able to see the effects of this feature. I created a dummy account and looked in the register, sorted by Date and do not see any amount in bold."
1810303,2020-10-08 19:22:39 UTC,"@Dennis: Instead of suggesting that somebody else changes the bug status, please just do it yourself. ""Fix released"" should be proper to denote that a previously reported issue is no longer present."
1810303,2020-10-08 19:01:44 UTC,Is this bug still affecting anyone? Are the before mentioned strings in the ubiquity package? That package is fully translated in German.
1810303,2020-10-09 21:01:23 UTC,"@Gunnar: Sorry for my misleading comment. Of course it was my intention to close this bug by myself, if nobody reports any occurrence of the problem any more."
1810303,2019-01-02 15:05:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1810305,2019-01-02 15:46:41 UTC,I can't reproduce it.
1810310,2019-01-02 15:26:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810313,2019-01-02 15:48:08 UTC,Logs & introspection reports uploaded to https://private-fileshare.canonical.com/~paulgear/lp1810313/
1810313,2019-01-06 23:09:57 UTC,"An initial look at the logs indicates there's a whole world of hurt occurring with regards to network connectivity in general. After various restarts, the juju controller agent reports errors connecting to mongo, connecting to itself via the api etc. The engine report shows that most/all workers are reporting their connection is lost. The raft worker is likewise affected - it is reporting timeouts trying to process lease claims; these are not fatal (and it retries the request) and are more symptoms of an underlying problem than the root cause."
1810313,2019-01-07 04:46:04 UTC,"So Ian and I spent some time digging through the logs again this morning. I think we've worked out that the issue is likely because of a charm requesting a reboot, and things like raft errors are a red herring."
1810313,2019-01-07 05:41:30 UTC,"Paul confirmed that manually deleting the doc from the ""reboot"" collection for the controller 0 machine cleared the reboot flag and stopped the reboot loop."
1810313,2019-01-08 04:02:51 UTC,https://github.com/juju/juju/pull/9603
1810313,2019-01-08 16:38:32 UTC,Moving this down from critical as a workaround has been validated. Thanks for the PR thumper.
1810316,2019-03-26 17:49:33 UTC,"Thanks, nice collection of crashes, but no NetworkManager."
1810316,2019-04-14 21:56:40 UTC,https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
1810316,2019-03-27 11:07:51 UTC,@Till
1810316,2019-03-26 17:12:18 UTC,To anyone who has observed this problem:
1810316,2019-03-23 12:53:36 UTC,I'm connecting 2 WiFi USB in ubuntu disco.
1810316,2019-01-10 12:01:40 UTC,"NetworkManager was running, as far as I know."
1810316,2019-01-10 11:52:45 UTC,"Thank you for your bug report, that looks similar to this upstream bug when happens when network-manager is not started
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342"
1810316,2019-01-02 16:43:55 UTC,"StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x5634bde857f0 <__func__.26485> ""cc_object_storage_add_object"", message=<optimized out>) at ../../../../glib/gtestutils.c:2596
 g_assertion_message_expr (domain=domain@entry=0x5634bde853f7 ""cc-object-storage"", file=file@entry=0x5634bde85409 ""../shell/cc-object-storage.c"", line=line@entry=167, func=func@entry=0x5634bde857f0 <__func__.26485> ""cc_object_storage_add_object"", expr=expr@entry=0x5634bde85426 ""G_IS_OBJECT (object)"") at ../../../../glib/gtestutils.c:2619
 cc_object_storage_add_object (key=0x5634bde91c4b ""CcObjectStorage::nm-client"", object=0x0) at ../shell/cc-object-storage.c:167
 cc_wifi_panel_static_init_func () at ../panels/network/cc-wifi-panel.c:130
 cc_panel_loader_fill_model (model=0x5634c04bcd80) at ../shell/cc-panel-loader.c:216"
1810332,2019-08-09 14:01:56 UTC,Thanks for the bug report. Patch is already applied.
1810335,2019-09-06 21:20:26 UTC,Run the following in a terminal:
1810335,2019-11-06 04:17:33 UTC,[Expired for mate-tweak (Ubuntu) because there has been no activity for 60 days.]
1810341,2019-01-11 13:35:27 UTC,If there is anything else I can supply to help resolve this please ask. It is making the product almost unusable.
1810345,2019-01-02 23:00:09 UTC,This change was made by a bot.
1810345,2019-01-04 02:17:14 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0]."
1810345,2019-01-05 19:55:47 UTC,"i tried with 4.20.0-042000-generic and got a crash again (when running in screensaver mode/idle). even sysreq reisub didnt work, had to hardreset. i dont know how to trigger this crash on purpose. yesterday it worked with the 4.20 kernel without crash."
1810345,2019-02-13 17:34:25 UTC,the last times the kernel panic got triggered by watching Youtube Video in Firefox.
1810346,2019-06-29 17:16:45 UTC,"This is the behaviour I have been describing from the beginning : the video is useable, but most of the controls are not.
This happens on *every* laptop used with an external TV as main screen since 18.04 - it was fine until 16.04.
I would event bet it alson happens on every computer using a second monitor as main display unit.
In order to be able to use vlc correctly, I have to launch it from terminal with the command QT_AUTO_SCREEN_SCALE_FACTOR=0 vlc, which I could find in many of the thousands posts about this on the net since 2010 or so.
Which tends to prove that the bug has never been reported, otherwise no doubt the devs would have fixed it already.
And would not have thought that I was the only one to encounter it.
To the devs : I am ready to help you trying to trace this, but keep in mind that, just like you, I have a real life beside, which makes I may not react as quickly as one would expect.
This is also why I did not give any reminder though there was no reaction after a long time : I know you have many things to do, that may be more important (or valualble), and 24 hours per day are not enough for many of us.
This bug kind of puzzles me, and I sometimes wonder if I did not install something the wrong way : many things changed since 16.04, so being able to tell what is good or not is not that easy for a poor end user.
If I find some time, I plan to load the latest 16.04 LTS iso and reinstall it from scratch, but without preserving my /home. This means I will have to do some savings before, and be very carefull, and it will take me far more time then just upgrading my distro.
However, I may take some time to do some testings, a"
1810346,2019-06-29 20:00:36 UTC,"Hey, Thanks Jean Luc, the QT_AUTO_SCREEN_SCALE_FACTOR=0 does the trick here too!
I wonder if this only affects Ubuntu or other Linux distributions too."
1810346,2019-06-29 17:20:08 UTC,"Oops ! I hit the return key unintentionally !
So, I make take some time to do some testings, but you have to tell me what to do exactly, and how."
1810346,2019-06-29 13:56:46 UTC,"On my last test (the one where it works but is exageratly zoomed), when switching to fullscreen mode, the VLC overlays(control buttons, volume, etc) are not usable because too large, they don't fit on screen."
1810346,2019-07-02 12:35:34 UTC,"As a temporary fix, so you don't have to launch it from the terminal you can do something like this, (need root):"
1810346,2019-06-27 20:12:24 UTC,I just checked and the bug is still there on 19.04.
1810346,2019-06-27 22:16:49 UTC,"I also tested 18.04 again with another setup, still dual screen on a samsung TV, the vlc GUI is exageratly zoomed but still correctly visible and usable, not sure if they want it to be zoomed like that."
1810346,2019-06-07 15:56:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810346,2019-06-07 15:33:01 UTC,Another screenshot playing a video...
1810346,2019-06-07 15:30:49 UTC,"Hi, I think it's the same bug, i got a laptop with a second screen plugged, optimus laptop, nvidia-drivers-390, on the integrated laptop screen, vlc works just fine, but as soon as i drag the vlc window to the second screen GUI elements gets extra zoomed, and unusable ( but i can see some parts of GUI buttons reacting to mouse-over events for exemple). If i drag n drop a video file to the vlc window while on second screen the vlc window gets extra large and still displays extra zoomed GUI elements. note that if i drag the window back the laptop screen it's back to normal."
1810346,2019-01-18 14:47:58 UTC,"This looks like the typical Qt HiDPI breakage and needs to be fixed in Qt. As a temporary workaround, disable scaling for Qt."
1810346,2019-01-08 21:49:25 UTC,2 more hardcopies.
1810346,2019-06-08 07:30:57 UTC,Can one of you please check if the issue still exists with Ubuntu 19.04 (which has Qt 5.12)?
1810348,2019-01-02 23:36:20 UTC,We are working on some optimizations now: https://github.com/mixxxdj/mixxx/pull/1974
1810348,2019-08-09 10:37:06 UTC,"fix for battery widget
https://github.com/mixxxdj/mixxx/pull/2221#event-2541311756"
1810348,2019-08-09 10:37:28 UTC,"first implementation in Deere
https://github.com/mixxxdj/mixxx/pull/2161"
1810348,2019-08-09 10:41:05 UTC,"whoopsy, wrong bug..."
1810349,2019-09-19 10:14:00 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1810349,2019-05-18 21:22:10 UTC,"Reviewed:  https://review.opendev.org/628071
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dcdb6e1c8aea8fd0f425097c9db0a140a2cf6104
Submitter: Zuul
Branch:    master"
1810349,2019-04-04 19:32:08 UTC,Helps with the initial setup
1810349,2019-04-04 19:17:50 UTC,Disregard notes from step 18
1810349,2019-04-04 20:02:54 UTC,Help create non dvr vm
1810349,2019-04-04 19:03:19 UTC,"Hi Swaminathan, here are steps to reproduce. I'm new to Openstack, apologies if this is too lengthy:"
1810349,2019-02-01 01:29:19 UTC,"Are you sure for a non-dvr router connected subnet is it creating a fip agent gateway port.
It only creates a fip agent gateway port when there is first VM that pops up on the compute for the DVR routed subnet.
If the VM on the compute is removed, the Fip agent gateway for that compute host will not be disturbed until the gateway is cleared for that network."
1810349,2019-01-03 00:18:28 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/628071"
1810349,2019-04-04 19:09:40 UTC,#I'll try attaching the scripts as opposed to pasting them. For readability.
1810351,2019-01-03 22:45:44 UTC,Part of the mystery is solved and part not.
1810352,2019-04-14 11:35:23 UTC,This has been fixed for 0.92.x on the Feb 26 2019 (and also 1.0alpha)
1810352,2019-04-14 11:56:01 UTC,"Is 0.92.4 out officially, or still a beta build?"
1810352,2019-04-14 12:27:54 UTC,Closing because fix has been committed.
1810354,2019-01-10 02:39:45 UTC,Thanks. Moved to: https://gitlab.gnome.org/GNOME/gnome-desktop/issues/98
1810354,2019-01-10 00:46:18 UTC,Here is the upstream report I just created:
1810354,2019-01-07 10:07:05 UTC,Please report the bug to the upstream developers at:
1810364,2019-02-12 13:53:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810368,2019-01-03 06:16:02 UTC,"Some further information: As I'm intending to switch to MATE for preference anyway, I went ahead and installed the ubuntu-mate-desktop package and set gdm3 to default in the process (I believe it is already default for Bionic?); now on boot I see the MATE loading screen, am taken to the Gnome login screen, gnome-control-center opens. The halt-on-shutdown bug, another bug I've seen a few threads on with fresh installs, and had with my last install as well as this, was also fixed. So now I'm wondering, what has MATE changed during it's install to fix these bugs? Interesting."
1810368,2019-01-10 11:49:10 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1810368,2019-01-10 11:50:11 UTC,Do you have the launcher placed at the bottom? we got some reports about this creating issues probably because by lack of vertical space to fit the settings dialog
1810368,2019-01-22 15:18:40 UTC,"I'll see about getting a backtrace when I have some time again to mess around.
No, I left the launcher on the side."
1810368,2019-03-22 20:05:20 UTC,"Please report your findings, thank you."
1810380,2019-12-08 18:26:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810382,2019-02-12 19:44:19 UTC,"@corrado, on 19.04 gnome-software use the ODRS review server and reviewing snaps should work, when you say ""same provblem"" you mean that you also get the text/html error there?"
1810382,2019-02-12 20:02:38 UTC,"Sorry not same problem, I can write a review and i have NO errors"
1810382,2019-02-12 16:20:59 UTC,"Do you always get that ""write a review"" button for snaps? It's weird, that control is supposed to be hidden there :/"
1810382,2020-05-18 13:49:51 UTC,Old problem about Ubuntu 18.10. Changed status to invalid.
1810382,2019-02-12 19:27:59 UTC,I have the same problem also with Ubuntu 19.04 with all kernels up to Kernel: 5.0.0-050000rc6-generic
1810382,2019-02-13 03:47:09 UTC,"@azzar1 correct the upstream change made the snaps reviewable, however the ubuntu-reviews plugin suppresses the ODRS plugin so reviews fail to be posted. We should have patched the NOT_REVIEWABLE quick back in."
1810382,2019-02-12 16:43:09 UTC,"It looks like that since https://gitlab.gnome.org/GNOME/gnome-software/commit/e54b31cc85ddef6f9579cb85bbdf53dbb9d9091d snaps are no longer marked AS_APP_QUIRK_NOT_REVIEWABLE. This because ODRS supports Snap Reviews. Unfortunately, ODRS plugin is disabled for you (and maybe for all cosmic users?) while ubuntu-reviews plugin is still installed/enabled hence the issue. @robert-ancell what's the proper way to fix this? Maybe we should enable ODRS in cosmic and disable ubuntu-reviews?"
1810382,2019-02-11 14:30:21 UTC,"try again to write a review for GIMP, problem occurred again. I attach journalctl hoping it will help."
1810382,2019-02-09 19:44:44 UTC,"Try to write a review for GNOME characters
corrado@corrado-p3-cosmic:~$ inxi -Fx
System:
  Host: corrado-p3-cosmic Kernel: 4.18.0-15-generic x86_64 bits: 64
  compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.1
  Distro: Ubuntu 18.10 (Cosmic Cuttlefish)
Machine:
  Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: <root required>
  UEFI: American Megatrends v: P1.10 date: 05/11/2017
CPU:
  Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 L2 cache: 3072 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296
  Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800
  3: 800 4: 800
Graphics:
  Device-1: Intel HD Graphics 630 driver: i915 v: kernel bus ID: 00:02.0
  Display: x11 server: X.Org 1.20.1 driver: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
  v: 4.5 Mesa 18.2.2 direct render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3
  Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus ID: 1-2:2
  Sound Server: ALSA v: k4.18.0-15-generic
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e v: 3.2.6-k port: N/A
  bus ID: 00:1f.6
  IF: enp0s31f6 state: up speed: 100 Mbps duplex: full
  mac: 70:85:c2:44:7b:86
Drives:
  Local Storage: total: 931.51 GiB used: 56.44 GiB (6.1%)
  ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
Partition:
  ID-1: / size: 31.25 GiB used: 14.31 GiB (45.8%) fs: ext4 dev: /dev/sda3
  ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 225 Uptime: 13m Memory: 7.50 GiB used: 1.17 GiB (15.6%)
  Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 4.4.19
  inxi: 3.0.24
corrado@corrado-p3-cosmic:~$"
1810382,2019-02-08 19:28:37 UTC,Thank you for your bug report. Could you describe the steps you take to trigger that issue? How do you write the review/on what page? The review widgets are not supposed to be displayed for snaps (and they are not showing here on bionic or cosmic)
1810382,2019-02-08 19:07:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810382,2019-01-03 08:24:36 UTC,Same problem also with x11 session
1810383,2019-01-03 08:30:04 UTC,This change was made by a bot.
1810384,2019-01-14 11:14:41 UTC,Spotted on Cosmic.
1810384,2019-01-03 08:30:15 UTC,This change was made by a bot.
1810384,2019-01-03 08:40:35 UTC,This issue could be found on a SUT with 1TB disk space.
1810384,2019-03-28 10:59:02 UTC,"Test disabled in A-C-T
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=bbbb3e497633108cf62f91587d4e0b4804f7248d"
1810386,2019-01-04 16:53:59 UTC,It works if you're logged in (login_with rather than login_anonymously).  ICve's security declarations probably need to be looked at a bit more carefully.
1810387,2019-08-02 13:56:47 UTC,fixed in https://review.opendev.org/#/c/671990/
1810396,2019-07-14 04:17:25 UTC,[Expired for OpenStack ceph-mon charm because there has been no activity for 60 days.]
1810396,2019-05-14 07:21:34 UTC,"It looks, to me, like those machines have been re-used? The ceph-osd charm's osd count ""(1 OSD)"" comes from a `pgrep ceph-osd`, so re-using machines can lead to a scenario where there is a ceph osd process running on the machine, but that OSD is _not_ configured to talk to the monitors."
1810396,2019-02-09 17:34:35 UTC,"I also deployed a charm openstack-base-bionic-queens-3 and encountred you same issue.
I tried to downgrade the charm ceph-mon, I didn't resolve the problem. The only things is too cheet.
set expected-osd-count to 1 and everythings work fine."
1810400,2019-08-16 22:47:07 UTC,Acknowledged; target is 4.2.
1810400,2019-12-23 20:36:22 UTC,"Hi, this should be fixed in 4.2. It looks like you're still on 2.12.0 based on the report. Closing under the assumption this is fixed. If you discover otherwise, please feel free to re-open (or file a new bug.)"
1810406,2019-01-09 03:00:00 UTC,Looks like a repeat of bug 1760876. But that's meant to be fixed already!?
1810406,2019-01-09 14:00:47 UTC,I could reproduce it at every kernel upgrade in the past 2 months.
1810406,2019-01-30 10:05:50 UTC,I confirm that this still happens
1810415,2019-01-11 16:18:07 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.3.0 release.
1810416,2019-08-18 08:07:23 UTC,This problem also affects me on a Dell Precision 5510 in combination with a SanDisk Extreme Pro 128 GB.
1810416,2019-08-29 16:23:44 UTC,"Hi, I had the same issue with an RTS525A."
1810416,2019-08-25 10:41:53 UTC,"The same problem(mmc0: error -110 whilst initialising SD card):
HW: Dell Precision 3520
OS: Ubuntu 19.04
KERNEL: 5.0.0-25-generic
SSD: SanDisk Extreme Pro 256 GB"
1810416,2019-08-26 10:56:33 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc6/"
1810416,2019-08-29 19:07:46 UTC,"Since it has ""Cc: <email address hidden>"", it'll also land to Ubuntu's kernel."
1810416,2019-03-28 23:06:05 UTC,the above is on Dell Latitude 5490 with RTS525A card reader.
1810416,2020-01-25 19:03:06 UTC,"Still broken @ 19.10,  5.3.0-24-generic."
1810416,2020-06-24 02:27:38 UTC,"I would like to know how to install those patch (https://patchwork.kernel.org/patch/11088719/ and https://patchwork.kernel.org/patch/11116271/), listed above, on Ubuntu, deepin or gpart distro. I am trying to install linux on a mini pc that came with windows 10, but while trying.to do that I receive erros containing ""HS 400 -84 whitest mmc"", or something like that.
Could somebody help me on that? My WhatsApp is +5596991121266. I am Brazilian, by the way..."
1810416,2020-07-15 07:07:27 UTC,"Please just test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/"
1810416,2020-10-11 10:39:02 UTC,https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/comments/25
1810416,2019-06-13 05:06:32 UTC,"If it worked on older kernels, please do a kernel bisection to find the regression commit."
1810416,2019-11-15 23:12:34 UTC,Almost a year and still nothing changed. 18.04.3 with 4.20.0-042000-generic still have the same issue.
1810416,2019-06-12 20:57:08 UTC,"I have same problem.
Laptop HP Omen Pro 15, SanDisk 64Gb
I tested it on Ubuntu 18.04, Ubuntu 18.10, Ubuntu 19.04.  It did not work. In all environments, I  always get in logs(system) message: ""mmc0: error -110 whilst initialising SD card"""
1810416,2019-02-17 22:16:37 UTC,"I've got the same issue on Dell e5470 with Manjaro. Tried kernel v4.19, v4.20, v4.4
The issue is visible on each kernel. The card is brand new and works perfectly fine on camera and on Windows booted on the same machine."
1810416,2019-05-27 20:17:27 UTC,Same bug with Notebook Acer Aspire E5-575G-55GR with Sandisk 64GB extreme.
1810416,2019-05-28 11:34:59 UTC,Please file an upstream bug at [1]. Component -> MMC/SD.
1810416,2019-01-03 17:51:08 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0]."
1810416,2019-01-04 14:53:20 UTC,Still the same:
1810416,2019-01-08 06:56:57 UTC,"The system was upgrade from 16.04, did you see the same issue on Linux kernel v4.4?"
1810416,2019-03-28 22:54:28 UTC,The same problem with SanDisk Extreme 64GB.
1810416,2019-01-03 14:30:06 UTC,This change was made by a bot.
1810416,2019-04-13 12:53:57 UTC,"Same issue here, also with a SanDisk Extreme microSD card (128GB)."
1810416,2019-04-13 13:58:14 UTC,For anyone experiencing this issue with a Realtek RTL8411 card reader:
1810416,2019-04-29 22:22:35 UTC,I'm having the same problem with a Sandisk 64G.
1810416,2019-05-10 07:58:39 UTC,"Same bug here on Toshiba Tecra X40-D, with:
""01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)"""
1810425,2019-01-03 23:00:30 UTC,"The problem seems to be the length of the input (-f option) and output (-E option) paths, using short paths with the same input file works!"
1810425,2019-05-28 05:05:16 UTC,"Hi there, is this still an issue with Inkscape 0.92.4? Also is this specific to s390x or is this an arch-independent issue?"
1810425,2019-09-19 12:12:29 UTC,"Closing as there has been no activity for 60 days. If you still have this problem, check the already reported issues at https://inkscape.org/report. Thank you!"
1810426,2019-04-18 15:49:54 UTC,Thank you for your bug report. It's probably an issue similar to bug #1825085 and might have to do with which IM is in use of about xorg vs wayland.
1810429,2019-06-26 18:42:46 UTC,"After some further discussion, I think this needs some discussion from the wider community - the refunds UI is overall fairly confusing. The Refund action itself doesn't do anything unless a negative bill is selected(possibly greying out this action when a positive bill or no bill is selected would be a good course of action?), and even then is only effectively a placebo(it brings up a modal saying what it's doing, but that's already done when you select a negative balance). It seems to me that the refund button might at this point be worth removing entirely."
1810429,2019-06-18 14:58:34 UTC,"I like the Issue Refund button.  An additional check is needed, though, to prevent users from seeing/clicking the 'Issue Refund' button when a mix of refundable and non-refundable transactions are selected.  As it stands, when clicking the button with that scenario, the user gets an error alert for REFUND_EXCEEDS_BALANCE on the positive-balance transaction."
1810429,2019-05-23 17:10:20 UTC,I've pushed a branch here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1810429-refund-not-working-as-expected
1810429,2020-01-29 16:17:04 UTC,A new commenter/end-user here: We find it confusing that the refunds actions are on the Unpaid Bills display.  This is especially true for configurations that do not allow negative balances.  Does it make more sense that a single refund actions button display on the Bill History > Payments? Would this eliminate the need for a confusing third button on the main bill display?
1810429,2019-01-24 03:47:11 UTC,I have determined this is a regression introduced by 4efaa63 (see LP 1749994)
1810429,2019-01-04 12:43:01 UTC,Confirming this and marking High importance since it affects direct service to the public.
1810429,2019-01-28 18:10:31 UTC,"Just spitballing a thought I had, but I wonder if the ""Apply Payment"" button should say ""Issue Refund"" or something when issuing a refund, or there should be a separate button that is greyed unless a refund is happening?"
1810430,2019-01-03 20:37:24 UTC,"Hi, tested with upstream 4.20 as requested and still the same symptoms..."
1810430,2019-01-03 17:51:01 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0]."
1810430,2019-01-08 02:23:50 UTC,Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1394912
1810430,2021-02-06 22:29:19 UTC,"Not on Ubuntu, but I'm having this issue on 5.9.1 with an ASRock X399M Taichi and Threadripper 1920X."
1810430,2019-01-03 17:30:07 UTC,This change was made by a bot.
1810430,2019-06-21 17:33:50 UTC,Still seeing this on the (upstream) 5.19 vanilla/mainstream kernel.
1810432,2019-06-21 13:48:39 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1810439,2019-01-03 19:48:12 UTC,Why isn't systemd-resolved forwarding my query for mirror1.eng.local to the configured upstream DNS server?
1810446,2019-09-13 18:51:06 UTC,This how it works in our system (3.2.5) and we would love to see the change made.
1810448,2020-02-26 16:26:40 UTC,The real issue here is that nova-cert doesn't exist in Pike and later and the charms didn't cleanup.  related bug: lp#1810449
1810449,2019-01-03 23:13:06 UTC,"This may be a semi-red-herring.  the service needs to be removed from the database to not confuse operators and monitoring tools, but the reasoning behind it affecting nova-api-metadata on the neutron-gateway nodes are incorrect.  It turns out my issue with the ServiceTooOld message is that my cloud-archive on the neutron-gateway is stuck at newton when the charm is set to xenial-pike."
1810449,2020-10-14 20:56:13 UTC,Here's a slightly easier deletion workaround:
1810450,2019-01-06 19:48:10 UTC,Figured out that I just had to install some packages (libgfortran4 and cpp-7 for my case) required by the hold back packages (listed in Apt log)..
1810452,2019-01-08 23:14:30 UTC,"Not present on Neon, the KDE distro, so it's an upstream bug which got fixed"
1810452,2019-01-26 17:22:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810452,2019-01-26 17:50:02 UTC,"After sleep and re-login there is a graphics-fail:
the central image is proper, the surrounding blur is damaged."
1810452,2019-01-26 17:59:59 UTC,"i don't think it's the same issue, the problem about that graphics corruption is due to the nvidia proprietary drivers, the issue I mentioned happens only on reboot and even if the GPU driver isn't the nvidia proprietary one"
1810458,2019-01-14 22:56:32 UTC,"ubuntu-release-upgrader does not have an explicit dependency on gnupg, but gnupg is part of the daily-live seed and is part of the minimal task for xenial."
1810461,2019-09-22 17:45:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810463,2019-01-04 04:10:51 UTC,The raspbian and raspberry pi foundation repositories are available over https
1810463,2019-01-04 04:24:09 UTC,"OK, thanks, I'll give that a try."
1810471,2018-08-22 12:24:34 UTC,This seems to be the upstream fix:
1810471,2018-08-22 12:35:19 UTC,"This fixes the problem, I've prepared a submission: https://build.opensuse.org/request/show/630909"
1810471,2018-08-22 14:07:45 UTC,"Another problem that fixed itself :-)
Thanks for the report and the submission."
1810471,2019-04-19 00:07:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810471,2018-08-22 12:19:33 UTC,"Created attachment 780410
Screenshot of messed up terminal"
1810490,2019-01-04 08:23:56 UTC,fix patch: https://review.openstack.org/628354
1810490,2019-03-20 20:47:19 UTC,This issue was fixed in the openstack/placement 1.0.0.0rc1 release candidate.
1810502,2019-01-04 11:56:39 UTC,I think these are provided by the system theme (Adwaita probably). Should be fixed in the next version.
1810502,2019-01-04 14:30:38 UTC,"Merci for the fast reply. (it's ""elementary xfce"" in my case but themes share a lot.)"
1810502,2019-01-04 18:09:40 UTC,Is the icon size for the close buttons of the docks related?
1810507,2019-01-04 14:38:20 UTC,"Reviewed:  https://review.opencontrail.org/48466
Committed: http://github.com/Juniper/contrail-vnc/commit/fa8afda1471507995cde5207458295a03dc24943
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1810507,2019-01-04 11:29:47 UTC,"Review in progress for https://review.opencontrail.org/48466
Submitter: Michal Clapinski (<email address hidden>)"
1810509,2019-06-23 04:18:07 UTC,[Expired for Variety because there has been no activity for 60 days.]
1810509,2019-04-23 08:22:16 UTC,Can you attach ~/.config/variety/variety.log after enabling the option? Any program errors should be logged there.
1810511,2019-01-17 16:15:52 UTC,Why not use the various --file-prefix* commands to get what you need?  See the man page.
1810513,2019-02-01 16:28:24 UTC,"Hi Ramon, there are two places to set snmp config in ceilometer and they each have different uses. The [hardware] section in ceilometer.conf is only for use with the TripleO discoverer which we don't currently support. The other way is to use static resources in polling.yaml but unfortunately the charm does not yet support adding custom sources in this way. Since the latter is supportable i'll update this bug to reflect that."
1810513,2019-02-01 16:31:23 UTC,Note also that in order to use snmp metering you also need to install and setup snmp[d] on client and targets which is not currently undertaken by the charms either.
1810516,2019-01-04 13:28:21 UTC,"With python3.7 it produces same output
Unhandled Error
Traceback (most recent call last):
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/commands/crawl.py"", line 58, in run
    self.crawler_process.start()
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/crawler.py"", line 293, in start
    reactor.run(installSignalHandlers=False)  # blocking call
  File ""/usr/local/lib/python3.7/dist-packages/twisted/internet/base.py"", line 1267, in run
    self.mainLoop()
  File ""/usr/local/lib/python3.7/dist-packages/twisted/internet/base.py"", line 1276, in mainLoop
    self.runUntilCurrent()
--- <exception caught here> ---
  File ""/usr/local/lib/python3.7/dist-packages/twisted/internet/base.py"", line 902, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/utils/reactor.py"", line 41, in __call__
    return self._func(*self._a, **self._kw)
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/core/engine.py"", line 135, in _next_request
    self.crawl(request, spider)
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/core/engine.py"", line 210, in crawl
    self.schedule(request, spider)
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/core/engine.py"", line 216, in schedule
    if not self.slot.scheduler.enqueue_request(request):
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/core/scheduler.py"", line 57, in enqueue_request
    dqok = self._dqpush(request)
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/core/scheduler.py"", line 86, in _dqpush
    self.dqs.push(reqd, -request.priority)
  File ""/usr/lib/python3/dist-packages/queuelib/pqueue.py"", line 33, in push
    self.queues[priority] = self.qfactory(priority)
  File ""/usr/local/lib/python3.7/dist-packages/Scrapy-1.5.0-py3.7.egg/scrapy/core/scheduler.py"", line 114, in _newdq
    return self.dqclass(join(self.dqdir, 'p%s' % priority))
  File ""/usr/lib/python3/dist-packages/queuelib/queue.py"", line 142, in __init__
    self.size, = struct.unpack(self.SIZE_FORMAT, qsize)
struct.error: unpack requires a buffer of 4 bytes"
1810517,2021-02-24 22:02:37 UTC,The decision to modify the default ImageMagick policy to prevent calling Ghostscript was not made on behalf of any single flaw. There are 50 Ghostscript CVEs allocated after this bug report was opened.
1810517,2021-02-24 13:28:29 UTC,"Although the security vulnerability in GhostScript that led to this restriction on converting to and from PostScript and PDF has been addressed in version 9.24, this restriction remains in place in at least Ubuntu and Gentoo, and an attempt to remove it in Gentoo has been stopped, apparently out of an abundance of caution: https://bugs.gentoo.org/716674."
1810517,2021-02-25 15:24:49 UTC,Thanks for the context! It makes sense.
1810517,2020-04-25 12:40:51 UTC,"The underlying security issue has been fixed many years ago:
https://www.kb.cert.org/vuls/id/332928/"
1810517,2019-07-06 22:08:19 UTC,I have the same errors: (Ubuntu 18.04)
1810517,2019-07-06 22:05:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810517,2020-07-18 02:21:59 UTC,"In ubuntu 20.04,"
1810519,2019-01-04 13:23:51 UTC,The bug seems very similar to this one:
1810519,2019-01-04 13:42:39 UTC,I just figured out this tool is also provided by libeccodes-tools. Works well with this one.
1810520,2019-01-04 15:19:23 UTC,"Hi Lionel.
Thanks for the bug report but unfortunately I no longer develop this application."
1810520,2019-01-09 19:19:10 UTC,"Hi Michael,"
1810520,2019-01-09 21:28:06 UTC,"Hi Daniel,"
1810520,2019-01-09 22:34:15 UTC,"Hi again Daniel,"
1810520,2019-01-10 05:34:25 UTC,"Thanks a lot for the quick action and many thanks for this app. Very useful and beautiful!
Yes, Brian sorted the OpenStore part out.
If I may have any questions regarding the code may I get in touch with you?"
1810524,2020-03-19 21:08:26 UTC,Closing because INVALID: Support request.
1810526,2019-03-06 21:39:20 UTC,"Given that this seems to be exposing a legitimate issue with the underlying service, do we still want to try to work around it with retries in tooz?"
1810526,2019-02-12 00:18:30 UTC,"Re IO issues on OVH nodes I do think there are some known problems with IO there, but unfortunately no known fixes. Maybe we can get dpawlik and amorin reengaged on this?"
1810526,2019-01-15 19:41:10 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=(message%3A%5C%22Remote%20error%3A%20ToozConnectionError%20Service%20Unavailable%5C%22%20OR%20message%3A%5C%22tooz.coordination.ToozConnectionError%3A%20Service%20Unavailable%5C%22)%20AND%20(tags%3A%5C%22screen-c-api.txt%5C%22%20OR%20tags%3A%5C%22screen-c-vol.txt%5C%22)&from=7d
1810526,2019-01-29 13:58:20 UTC,One other piece of information is this seems to only happen on OVH nodes (for the vast majority of failures). I wonder if there is something about those nodes that indicate problems with etcd? Like maybe I/O issues?
1810526,2019-01-29 14:27:21 UTC,frickler pointed this out: https://review.openstack.org/#/c/626885/
1810526,2019-01-15 19:35:26 UTC,Also seen in the cinder-volume service logs:
1810526,2019-01-28 13:23:51 UTC,The idea was brought up in IRC that tooz should recognize these service unavailable states and perform retries. I think that makes more sense than trying to so something in the consuming services.
1810532,2020-06-01 17:01:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810535,2020-01-23 23:50:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810535,2020-01-24 00:13:05 UTC,Same issue on 18.04. Resolved with $ cd /usr/lib/go-1.10/ ; sudo ln -s ../../share/go-1.10/misc misc
1810539,2019-02-19 13:25:56 UTC,"John, why do you need to do that? Can you explain the issue in more detail? maybe I can help here."
1810539,2020-02-11 14:08:16 UTC,This bug is fixed.
1810542,2019-01-04 23:38:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810543,2020-02-08 04:17:34 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1810543,2019-12-09 22:15:28 UTC,I have removed the milestone to let it expire.
1810543,2019-01-05 09:22:05 UTC,"for now, i can only reproduce with reverb."
1810543,2019-01-04 20:37:16 UTC,Does this happen with other effects or only Reverb?
1810543,2019-04-24 22:28:21 UTC,I cannot reproduce this with Mixxx 2.2.1 on ubuntu Xenial.
1810546,2019-01-04 19:46:48 UTC,apport information
1810546,2019-01-04 19:46:45 UTC,apport information
1810546,2019-01-04 19:38:04 UTC,"Another potential upstream BZ
 - https://bugs.freedesktop.org/show_bug.cgi?id=108098"
1810546,2019-01-04 19:26:50 UTC,"# lspci -nn | grep -E 'VGA|Display'
0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] [1002:15dd] (rev cb)"
1810546,2019-01-04 18:54:19 UTC,Potential upstream kernel issue
1810546,2019-01-04 18:43:03 UTC,Example error message with 4.18.0.13.63 kernel
1810546,2019-01-04 18:50:44 UTC,This appears to be similar to
1810546,2019-01-04 18:46:01 UTC,Reproduced with Mainline kernel
1810546,2019-01-04 18:45:01 UTC,apport information
1810546,2019-01-04 18:44:59 UTC,apport information
1810546,2019-01-04 19:46:59 UTC,apport information
1810546,2018-08-04 04:46:54 UTC,"(In reply to Andrey Grodzovsky from comment #34)

> notsyncing, can you close this ticket then ?
"
1810546,2019-01-04 18:53:58 UTC,Note that crash is happening with MPEG2 and H.264 video playback under MythTV
1810546,2019-01-04 19:47:02 UTC,apport information
1810546,2019-01-04 19:47:40 UTC,apport information
1810546,2019-01-04 19:47:12 UTC,apport information
1810546,2019-01-04 19:47:22 UTC,apport information
1810546,2019-01-04 19:47:25 UTC,apport information
1810546,2019-01-04 19:47:29 UTC,apport information
1810546,2019-01-04 19:47:34 UTC,apport information
1810546,2019-01-04 19:47:46 UTC,apport information
1810546,2019-01-04 19:47:52 UTC,apport information
1810546,2019-01-06 06:11:59 UTC,"Switched back to the Stock 18.04 LTS kernel and installed
 - amdgpu-pro-18.50-708488-ubuntu-18.04
 - https://www.amd.com/en/support/kb/release-notes/rn-rad-lin-18-50-unified"
1810546,2019-01-15 02:00:33 UTC,"I have it too: (random hangups of whole system either under load/idle)
- Ryzen5 2400 G
- Ubuntu 18.04 and 18.10
- kernel 4.18"
1810546,2019-01-15 02:00:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810546,2019-05-18 09:11:44 UTC,This fixes it for me (raven ridge 2200g though). But unfortunately it seems that the version in linux-firmware is not sufficient and after every update it gets back.
1810546,2019-07-03 07:58:19 UTC,"I am seeing the same sort of bug on my machine.
msi X470 motherboard (just tried latest firmware - no change)
AMD Ryzen 5 2400G and Ubuntu 18.04
Linux paul-ubuntu 4.18.0-25-generic #26~18.04.1-Ubuntu SMP Thu Jun 27 07:28:31 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Sometimes it happens overnight when machine is idle / screen locked, other times when using machine. Oddly enough the most recent one still had the mouse moving but keyboard unresponsive. Also a remote reboot fails - unless I use the watchdog with 'nowayout=1' to for a hard reset 60s after things should have gone down so it seem systemd won't/can't stop the hung graphics system.
Typically the error messages look like:"
1810546,2018-08-02 20:02:57 UTC,"notsyncing, can you close this ticket then ?"
1810546,2019-01-04 19:47:07 UTC,apport information
1810546,2018-07-14 06:45:17 UTC,"Now about half a month passed, and my machine is running fine with zram disabled. No more freezes. Seems my problem is related to zram, not this bug, while the ""ring gfx timeout"" error never happened again. Thanks for everyone who gave me advice."
1810546,2018-06-16 18:59:20 UTC,"(In reply to Andrey Grodzovsky from comment #6)

> Are you seeing sdma0 timeout message when the system freezes like muelladi
> above ? I expect
> amdgpu.vm_update_mode=3 to help only in that case.
"
1810546,2018-07-01 08:56:41 UTC,"(In reply to notsyncing from comment #30)

> Finally got logs from serial port when freezed. Seems my problem has nothing
> to do with amdgpu. Maybe I should file a new bug.
"
1810546,2018-06-12 21:27:50 UTC,Can you load kernel with grub command line amdgpu.vm_update_mode=3 to force CPU VM update mode and see if this makes the issue go away ?
1810546,2018-06-13 07:17:17 UTC,Added the grub cmdline and will investigate
1810546,2018-06-16 15:47:54 UTC,"Hello, I think I'm experiencing the same problem here. My Ryzen 5 2400G system freezes often, especially under some high cpu and disk activity, even after the ""Typical Current Idle"" UEFI workaround. Sometimes I could reboot with sysrq, most of the times I need a hard reset. The freezes never leave a message in kernel log until today, after 2 months I built my machine."
1810546,2018-06-16 16:29:24 UTC,"Not sure if this is related to bug #199653, which concerns freezing on the 2500U and 2700U. It hasn't received any attention from AMD or other kernels devs but there is more information that could potentially be useful. I tried amdgpu.vm_update_mode=3 but that didn't help."
1810546,2018-06-16 18:24:58 UTC,Those two bugs are unrelated.
1810546,2018-06-16 18:31:40 UTC,"(In reply to James Le Cuirot from comment #4)

> Not sure if this is related to bug #199653, which concerns freezing on the
> 2500U and 2700U. It hasn't received any attention from AMD or other kernels
> devs but there is more information that could potentially be useful. I tried
> amdgpu.vm_update_mode=3 but that didn't help.
"
1810546,2018-07-01 09:00:55 UTC,"I've set that option to ""Typical Current Idle"" and still freezes. The logs in 196683 points to RCU, which seems not my case. I suspect it's due to the zram. Now I'm trying to reproduce it with zram disabled."
1810546,2018-06-17 09:37:00 UTC,"Today I tried the amdgpu.vm_update_mode=3 option, and my computer still freezed. This time no log was recorded."
1810546,2018-05-17 09:21:39 UTC,"System video freezes randomly during the day while working on the system normally (no 3D).
Logfile shows only:"
1810546,2018-06-18 06:16:38 UTC,"So far I have not had any more freezes during normal, non-3D work."
1810546,2018-06-18 08:55:22 UTC,Other Raven Ridge users have reported that updating to the current microcode files from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu has fixed stability issues.
1810546,2018-06-21 13:34:45 UTC,"I updated to the current microcode files at linux-firmware.git. Today I replicated the same workload, and my computer freezed in just 5 minutes! Even sysrq does not work. I have to do a hard reset."
1810546,2018-06-21 16:23:29 UTC,"(In reply to notsyncing from comment #12)

> I updated to the current microcode files at linux-firmware.git.
"
1810546,2018-06-22 13:29:46 UTC,"(In reply to Michel Dänzer from comment #13)

> Did you update the microcode files in the initrd as well?
"
1810546,2018-06-17 09:41:47 UTC,"I found I'm able to reproduce the freeze when I'm compiling two Android ROMs at the same time while browsing or something else. It will freeze in at most 3 hours. I have a 300W PSU, and 2 SSD + 1 HDD storages. Android sources are stored in the HDD. This time I can reboot with sysrq, seems not a PSU fault."
1810546,2018-06-25 14:30:34 UTC,What kernel version are you using ?
1810546,2018-06-26 12:03:58 UTC,"(In reply to Andrey Grodzovsky from comment #16)

> Then launch your X with ENV variable GALLIUM_DDEBUG=always to dump all the
> 3D commands into files in ~/ddebug_dumps/
"
1810546,2018-06-26 12:04:36 UTC,"BTW, I'm using KDE plasma 5.13 with sddm."
1810546,2018-06-26 12:40:17 UTC,"(In reply to notsyncing from comment #18)

> BTW, I'm using KDE plasma 5.13 with sddm.
"
1810546,2018-06-26 14:58:04 UTC,"(In reply to Andrey Grodzovsky from comment #20)

> You just prepend this before command to start your graphic stack. You need
> to manually run your graphic stack from command line and add this before.
> E.G. for me on Ubuntu I will disable graphics launch on boot from GRUB. Then
> from terminal I will run
> GALLIUM_DDEBUG=always service lightdm start
"
1810546,2018-06-26 16:55:23 UTC,"(In reply to notsyncing from comment #21)

> (In reply to Andrey Grodzovsky from comment #20)
> > You just prepend this before command to start your graphic stack. You need
> > to manually run your graphic stack from command line and add this before.
> > E.G. for me on Ubuntu I will disable graphics launch on boot from GRUB.
> Then
> > from terminal I will run
> > GALLIUM_DDEBUG=always service lightdm start
>
> I compiled and installed umr and executed ""GALLIUM_DDEBUG=always service
> sddm start"" on a root tty, and no ""ddebug_dumps"" directory was found in
> /root or in my home directory after desktop started. Is that normal?
"
1810546,2018-06-27 11:44:58 UTC,"In fact there is no specified graphic work. I just put an Android source compilation running and go to bed, besides only firefox and dolphin running. The next morning, I found the machine has already freezed. Still no log. The log I posted is just a lucky one."
1810546,2018-06-27 13:39:06 UTC,"(In reply to notsyncing from comment #23)

> In fact there is no specified graphic work. I just put an Android source
> compilation running and go to bed, besides only firefox and dolphin running.
> The next morning, I found the machine has already freezed. Still no log. The
> log I posted is just a lucky one.
>
> Would you mind telling me if the umr had some system-wide debugging methods?
> Or should I make a netconsole to see if there was anything?
"
1810546,2018-06-29 19:59:23 UTC,"Created attachment 277059
Trace process"
1810546,2018-06-29 20:03:18 UTC,"Created attachment 277061
Trace process 2"
1810546,2018-06-30 03:09:38 UTC,"After 3 days, I managed to reproduce it again with 2 android compilation and firefox with kernel parameter mem=4096m (I have 16GB memory). I found that it's easier to reproduce when the memory is full."
1810546,2018-06-30 03:10:06 UTC,"btw, these umr commands are executed after reboot."
1810546,2018-06-30 04:17:36 UTC,I just upgraded to mesa 18.1.3 and kernel 4.17.3. I ran firefox with GALLIUM_DDEBUG after reboot. It produces these after I opened some tabs and firefox stopped responsing.
1810546,2018-06-24 06:12:21 UTC,"Still freezed under two Android source compilation + 2 intellij idea + 10 firefox tabs + EVE online playing after 3 hours. Sysrq does not work, need hard reset. No log was recorded."
1810546,2018-07-01 06:57:26 UTC,"Created attachment 277101
Kernel log from serial port when it freezes"
1810551,2019-01-09 17:24:30 UTC,"Robert, to have page numbers printed in a text document, you need to insert a ""page number"" field in the header/footer section of the page, this is not done automatically for new documents.
Just tested (printed to PDF) and that works as expected."
1810551,2020-02-05 14:19:56 UTC,This bug has sat incomplete for over a year. Marking invalid.
1810557,2019-08-20 01:38:05 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1810557,2019-05-20 22:01:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810565,2019-01-08 15:52:57 UTC,From which release were you upgrading?  I ask as the release upgrader should require you to have all updates installed before doing the upgrade. I do see your point about how more verbose logging would be helpful.
1810565,2019-01-08 17:44:36 UTC,"FRom: 16.04 LTS
To: 18.04 LTS"
1810565,2019-01-08 18:02:42 UTC,I didn't go deep enough do understand what _checkStoreConnectivity was called for. It might happen that was just a part of updates validation.
1810565,2019-01-09 16:03:34 UTC,"On Tue, Jan 08, 2019 at 06:02:42PM -0000, sergiiF wrote:

> I didn't go deep enough do understand what _checkStoreConnectivity was
> called for. It might happen that was just a part of updates validation.
>
> I'd like to make it clear - I do understand that having snap version old
> is my fault. The ticket I created is against the logging that doesn't
> allow to figure out what is going wrong.
"
1810565,2019-01-11 21:01:07 UTC,"2019-01-03 21:02:19,137 INFO uname information: 'Linux skashaba-laptop 4.4.0-83-gene
ric #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64'
2019-01-03 21:02:19,410 INFO apt version: '1.2.20'
2019-01-03 21:02:19,411 INFO python version: '3.5.2 (default, Nov 17 2016, 17:05:23)"
1810565,2019-01-11 21:02:43 UTC,"All logs from there:
2019-01-03 21:02:19,137 INFO Using config files '['./DistUpgrade.cfg.xenial']'
2019-01-03 21:02:19,137 INFO uname information: 'Linux skashaba-laptop 4.4.0-83-gene
ric #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64'
2019-01-03 21:02:19,410 INFO apt version: '1.2.20'
2019-01-03 21:02:19,411 INFO python version: '3.5.2 (default, Nov 17 2016, 17:05:23)"
1810568,2019-08-21 13:51:27 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago but I'm unsure how your problem relates to the Ubuntu project.
1810568,2019-10-21 04:17:38 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1810569,2019-03-07 13:33:51 UTC,"KiCad UI guidelines[1] recommend the GNOME HIG[2], which states:"
1810569,2019-01-31 04:25:36 UTC,This is not critical for v5.1
1810569,2019-06-25 11:27:03 UTC,"Fixed in revision cda3a82c668ca66b7d22ebc4b4a7040b90456509
https://git.launchpad.net/kicad/patch/?id=cda3a82c668ca66b7d22ebc4b4a7040b90456509"
1810569,2019-06-24 12:37:54 UTC,"I believe I've hooked up ctrl-tab to work in MSW and GTK.  (I can't be 100% sure, as I can only test on OSX.)"
1810569,2019-01-08 18:33:09 UTC,Nope.  I'm pretty sure that Ctrl-Tab cycles the visible application windows on MSW and it does nothing for linux.
1810569,2019-01-09 01:42:36 UTC,"@Seth, I think you mean Alt-Tab.  Ctrl-Tab does not exit the grid on windows.  Ctrl+Enter is the same as clicking the default button so for most dialogs that would be the OK button."
1810569,2019-01-07 21:55:52 UTC,"> We can use keyboard to move around the grid but can't exit the grid.
"
1810569,2019-01-05 15:08:08 UTC,Please add your KiCad version information
1810569,2019-01-05 22:35:37 UTC,Done.
1810569,2019-01-07 20:09:17 UTC,We can use keyboard to move around the grid but can't exit the grid.
1810569,2019-01-08 17:50:45 UTC,Ctrl-Tab exits the grid on Mac.  Does this not work on other platforms?
1810569,2019-01-07 21:50:22 UTC,"Sigh, my apologies. That was not what I intended to paste."
1810569,2019-01-07 21:49:32 UTC,"> Thanks,
> Tamar
>
> On Thu, Dec 27, 2018 at 6:27 AM Ben Gamari <email address hidden> wrote:
>
>> TL;DR. https://gitlab.haskell.org/ghc/ghc.git is now the official
>>        upstream GHC repository. Various introductory notes are
>>        discussed. Let me know if you have any trouble.
>>
>>        Also, please do verify the correctness of the email address
>>        associated with your Trac account in the next few weeks. It will
>>        be used to map users when we transition Trac tickets to GitLab.
>>
>>
>>
>> Hello everyone,
>>
>> I am happy to announce that CI on GHC's GitLab instance [1] is now
>> stable. At this point https://gitlab.haskell.org/ghc/ghc.git is to be
>> considered the official upstream repository of GHC.
>>
>> The rest of this email is meant to serve as a brief introduction and
>> status update. It can also be viewed on the GitLab Wiki [2].
>>
>> [1] https://gitlab.haskell.org/
>> [2] https://gitlab.haskell.org/ghc/ghc/wikis/welcome
>>
>>
>> # Getting started
>>
>> To get started on GitLab you will first want to either create a new account
>> [1] or login with your GitHub credentials [2].
>>
>> Once you have an account you should add an SSH key [3] so that you can push
>> to your repositories. If you currently have commit rights to GHC notify me
>> (Ben Gamari) of your user name so I can grant you similar rights in GitLab.
>>
>>
>> [1] https://gitlab.haskell.org/users/sign_in
>> [2] https://gitlab.haskell.org/users/auth/github
>> [3] https://gitlab.haskell.org/profile/keys
>>
>>
>> # Updating your development environment
>>
>> You can updated existing working directory (assuming the usual upstream
>> remote name of `origin`) for the new upstream repository location by
>> running the following:
>>
>>     git remote set-url origin https://gitlab.haskell.org/ghc/ghc.git
>>     git remote set-url --push origin <email address hidden>:ghc/ghc
>>
>> This is all that should be necessary; a quick `git pull origin master`
>> should verify that everything is working as expected.
>>
>>
>> # Continuous integration
>>
>> Continuous integration is now provided by GitLab's native continuous
>> integration infrastructure. We currently test a variety of
>> configurations, including many that neither Phabricator nor
>> CircleCI/Appveyor previously tested (see [1] for an example run):
>>
>>  * With the make build system:
>>     * x86_64/Linux on Fedora 27, Debian 8, and Debian 9
>>     * i386/Linux on Debian 9
>>     * aarch64/Linux on Debian 9 (currently broken due to a variety of
>>       issues)
>>     * x86_64/Windows
>>     * x86_64/Darwin
>>     * x86_64/Linux on Debian 9 in a few special configurations:
>>         * unregisterised (still a bit fragile due to #16085)
>>         * integer-simple
>>         * building GHC with -fllvm
>>  * With Hadrian:
>>     * x86_64/Linux on Debian 9
>>     * x86_64/Windows (currently broken due to #15950)
>>
>> We also run a slightly larger set of jobs on a nightly basis. Note that
>> binary distributions are saved from most builds and are available for
>> download for a few weeks (we may put in place a longer retention policy
>> for some builds in the future).
>>
>> There are admittedly a few ki...
"
1810569,2019-01-05 00:06:58 UTC,I've not yet verified this but it's possible that this has been fixed in master by c8b02674dcc80b19c7f8af94ddd5cd3027b17373.
1810570,2019-06-16 16:23:19 UTC,Closing in favor of https://gitlab.com/inkscape/inkscape-docs/documentation/issues/2
1810574,2019-02-18 07:41:29 UTC,It sounds like there might be a mismatch between one component playing at 44.1kHz and another thinking that is 48kHz.
1810574,2020-12-09 01:27:12 UTC,I can confirm this same bug while using DisplayPort output on an AMD R5 240 OEM. I'm using Mint 19 (Ubuntu 18.04)
1810574,2019-02-15 10:35:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810577,2019-01-05 23:22:27 UTC,"Forget about plugins. To have the device automatically set up for printing with Linux Mint 19.1, please read"
1810578,2019-01-05 08:50:04 UTC,"Hmm... that .profile causes this on SSH logins, so needs tweaking:"
1810578,2019-01-05 08:52:39 UTC,&& works better :)
1810583,2019-09-13 14:44:51 UTC,The following 3 bugs:
1810583,2019-09-04 18:13:15 UTC,"Yup, us too :("
1810583,2019-09-04 17:57:25 UTC,"Thank you Karl, this one bit us too this morning. Will there be a fix soon?"
1810583,2019-09-04 08:55:12 UTC,Nice one keepalived crew for this excellent little app!  Any news on a fix of this bug for the 1.x branch?
1810583,2019-03-21 23:36:04 UTC,"Thanks Karl.  This solution from Chris Aumann seems perfect, and I've just deployed it onto our HAPROXY pair.  Just restarted udev and networkd, and everything survives as expected now.  Much appreciated."
1810583,2019-03-20 13:47:40 UTC,"There is a fix upstream for this issue in keepalived 2.0. I'm looking into what would be required to backport the fix. In the meantime, there is a workaround that I hope will be sufficient for your needs, as discovered by https://chr4.org/blog/2019/01/21/make-keepalived-play-nicely-with-netplan-slash-systemd-network/"
1810583,2019-02-20 10:14:47 UTC,"We had this happen again this morning, causing an outage.  Same issue, apt daily leads to a udev restart, which in turn restarted the network service and caused VRRP address to be lost on both haproxy nodes.  I am going to try and completely disable the apt daily  scheduled job while this bug remains."
1810583,2019-01-15 14:29:32 UTC,"> something triggered a udev reload (and last week the same seemed to happen) which obviously triggers a network restart
"
1810583,2019-01-15 14:30:08 UTC,"Andreas, in our case this was a one off.  The system had been running for 2 months without any issues, and this sudden network restart due to a daily update check was not expected.  We did a lot of testing different failover events (disconnecting vNIC, powering off a single node, stopping keepalived service etc), but we never specifically tested a restart of the networkd service.  This bug has potentially gone unnoticed for some time because of this aspect, and the frequency of this event occurring (in our case), is low."
1810583,2019-01-15 12:06:10 UTC,"I guess you want to systemctl reload keepalived on most state changes in networkd, but I'm not sure. Probably not on off and no-carrier, as well, there's no traffic possible yet."
1810583,2019-01-15 12:03:23 UTC,Do all of you have daily network restarts? What's the reason? Or was this a one-off update that just by chance had a package upgrade that required such a restart?
1810583,2019-01-14 12:32:03 UTC,"Just to add, we also attempted to work around this by adding a systemd override to netplan to recycle the keepalived service whenever network management was restarted.  While it corrected the issue, it also created another problem whereby the system hung on startup after a reboot waiting endlessly for the network daemon to start.  I had to revert this change in light of this."
1810583,2019-01-13 21:30:11 UTC,"I don't have a desktop edition ready at the moment, but would be willing to pick that up if time allows. I concur with the findings of Ben, we seem to hit the same, although we 'patched' the systemd unit file."
1810583,2019-01-11 11:46:40 UTC,"Hi Karl.
I can confirm this issue also, we encountered it this morning on a 2 node keepalived cluster consisting of 2 VMWARE ubuntu 18.04.1 VMs.  In our case, a daily update task had restarted UDEV, which in turn restarted systemd-networkd.  When this service restarted, the virtual ip on the MASTER node's NIC was lost, but nothing was recognised by keepalived and the ip was never restored on either MASTER or BACKUP.  This caused an outage of services hosted on the virtualip."
1810583,2019-01-07 09:21:21 UTC,"Hi Tom, thanks for bringing up this issue!"
1810583,2019-01-24 02:13:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810583,2019-01-15 11:54:31 UTC,"There are three cases:
- upgrades from xenial with ifupdown
- fresh installs with netplan/systemd-networkd
- fresh installs with network-manager"
1810584,2020-04-15 00:56:30 UTC,"What release was a fix for this released? This exact same task fails for me on 19.1.0, with the _exact_ same aria2c log output as initially reported..."
1810584,2020-11-10 11:11:22 UTC,"The reported symptom in the previous comment is related to another bug, not related to this bug:
https://bugs.launchpad.net/openstack-ansible/+bug/1900975"
1810584,2020-11-10 10:44:05 UTC,"I am facing the same bug now, but this time the ubuntu image doesn't exist, I even can't download it using wget."
1810584,2020-04-15 01:15:02 UTC,When creating the aria2c command that the role lxc_hosts runs to pull the image the download fails as well. It could very well be sporadic errors with aria2c's ability to pull the image as I can very easily download the image with wget. I don't quite understand why something like aria2c was used here instead of just pulling this with curl or wget...
1810584,2019-05-09 06:48:11 UTC,"Having the same issue on centos 7, please share how this was resolved."
1810584,2019-02-12 02:13:34 UTC,Also i had same issue.
1810584,2019-02-07 11:18:01 UTC,Please disregard my above bug filing. My problem is different although with similar a symptom.
1810584,2019-02-06 17:25:12 UTC,I have the same problem. Execution of the setup-hosts.yml fails systematically with not attempt to retry.
1810584,2019-01-08 16:11:57 UTC,"This seems to be a third-party failure (cdimage.ubuntu.com) having problems, we consider this a low bug because we should have some retries."
1810584,2019-01-07 12:56:14 UTC,Also i had same issue.
1810584,2019-01-05 22:53:04 UTC,"I had the same problem, I thought it was my connection but It seems to be a real issue."
1810584,2019-05-06 02:04:17 UTC,I have a similar issue on CentOS:
1810585,2019-01-25 19:29:04 UTC,The (probably more common) i5-9600K has the same PCI ID and is affected as well.
1810585,2019-01-25 19:29:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810585,2019-09-11 06:54:00 UTC,should be fixed in eoan
1810587,2020-07-19 17:22:06 UTC,"I installed the Mono repository (allready installed but updated).
Installed Pinta again and the problem seems so be solved.
Tryed the rectangle tool > copy / paste as new image: no crashes.
Solved. Thank you!!"
1810587,2020-07-19 16:15:14 UTC,The Mono repository installs an updated version of the runtime environment that Pinta requires. I suspect this is a duplicate of 1786822 since that issue can cause a lot of random crashes.
1810587,2020-07-19 13:32:41 UTC,"Because the many crashes I removed Pinta. The distro I use Xubuntu 18.0.4
I didn 't try it on Xubuntu 2.0
What is the mono repository ?"
1810587,2020-07-19 12:09:40 UTC,"I also can't replicate this. Maybe this is just a Mono problem and it seams to bug reporter it crashes using resizing, but actually there are other ways to crash Pinta because of old Mono on Ubuntu."
1810587,2020-07-18 20:49:51 UTC,I can't reproduce this - can you describe the steps to reproduce or a crash log?
1810592,2019-01-26 23:58:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810592,2019-01-27 00:00:23 UTC,"Confirming for up-to-date but otherwise unmodified Ubuntu 18.04.1.
ssh-askpass fails to render the chars, ssh-askpass-gnome works as expected."
1810597,2019-01-09 23:39:52 UTC,"Thanks for the patch, I'll apply it."
1810597,2019-01-10 12:17:25 UTC,"This patch was came from the FreeBSD port of panoglview. For now, the FreeBSD ports tree contains wxgtk versions 2.8, 3.0 and 3.1, and many ports uses wxgtk28 as a default. So I see no reason to drop the wxWidgets 2.x support while it works.
But you are the master. :)"
1810597,2019-01-11 17:58:16 UTC,"I committed the full patch, if this is what FreeBSD want then fair enough."
1810602,2019-03-08 23:19:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810603,2021-02-03 14:01:06 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1810603,2019-01-28 09:46:39 UTC,"> Looking at the file size isn't helpful. The 23 GB
> are the space that is actually used. You can use 'du -h'
> to confirm this, but I think it gets the number in the exact same way as qemu-img.
"
1810603,2019-01-18 12:24:02 UTC,"Looking at the file size isn't helpful. The 23 GB are the space that is actually used. You can use 'du -h' to confirm this, but I think it gets the number in the exact same way as qemu-img."
1810603,2019-01-05 16:25:13 UTC,"On 1/5/19 9:32 AM, Lenny Helpline wrote:"
1810603,2019-01-11 13:06:11 UTC,"Regarding snapshot deletion, QEMU does punch holes into the image file when deleting snapshots, so the space should effectively be freed, even if this isn't visible in the file size. To get actually meaningful numbers, you'd have to look at the allocated blocks rather than the file size (e.g. by using 'du -h' instead of 'ls -lh')."
1810603,2019-01-08 15:41:43 UTC,"On 1/8/19 2:30 AM, Lenny Helpline wrote:

> I don't have many commands handy, as we manage almost everything through
> libvirt manager.
>
> 3) create a snapshot of the lined clone:
>
> virsh snapshot-create-as --domain <VMNAME> --name ""test"" --halt
>
> 4) revert the snapshot every X minutes / hours:
>
> virsh destroy <VMNAME>
> virsh snapshot-revert --snapshotname test --running --force
>
> Does that help?
"
1810603,2019-01-08 08:30:09 UTC,"I don't have many commands handy, as we manage almost everything through libvirt manager."
1810603,2019-01-18 11:01:38 UTC,"We have played a bit around with external snapshots (as suggested by Eric Blake in post #3), however, it appears that external snapshots are not fully supported yet. While I can create external snapshots, I'm unable to revert to them using virt-manager (which we use for managing our VM farm):"
1810604,2019-01-05 16:03:34 UTC,"I can confirm this, although I'm not sure what good it does to use a touch screen on a UI not designed for it at all."
1810604,2019-01-05 22:08:39 UTC,with touch it does all i need ;). Without it I have to search my old controller.. there are some usefull skins (except for the knobs).
1810604,2019-05-07 13:26:53 UTC,"I can confirm this bug; please please please fix this :)
I am running Mixx 2.2.0 on Ubuntu Mate 18.04 (Odroid XU4, armhf processor, Mali GPU); with a 1024x600 Touchscreen, which works well in other applications (e.g. chrome-browser); I did not custom build the source;"
1810604,2019-05-07 13:33:06 UTC,sorry typo; it should read: (note for other users....
1810606,2019-01-05 15:46:04 UTC,Source code that fails compile.
1810606,2019-01-05 15:46:40 UTC,Temporary file
1810606,2019-01-05 15:47:26 UTC,Temporary file generated by the compiler.
1810607,2020-09-28 09:30:16 UTC,"the issue is with the notification service used by lubuntu, unsure what component that is but it's not libnotify that does render those dialogs"
1810608,2019-01-05 17:02:17 UTC,The package from Dico is fine though. I took that.
1810612,2020-03-19 08:03:23 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here."
1810612,2019-01-05 19:21:21 UTC,"Bug also in Inkscape Version 0.91, but here the dialog window is not empty, here is shows the message ""'Inkscape Manual' working, please wait..."", an info icon and a ""Chancel""-button. But the button is not working."
1810612,2019-01-08 22:28:28 UTC,"Same bug with help menu entry ""Keys and Mouse References"""
1810612,2019-01-05 19:14:23 UTC,"When I close the web browser during freeze an info dialog appears:
""[22291:22291:0105/194758.446578:ERROR:x11_input_method_context_impl_gtk.cc(144)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const base::string16 &, const gfx::Range &)"""
1810620,2020-03-07 10:25:20 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1810621,2019-11-24 15:20:15 UTC,"Please can you add the field ""info"" in search conditions in the ""manage assigments"" ?"
1810621,2020-02-28 21:34:43 UTC,"what I am doing is a real mass prefill, like the actual create template faeture:
- you can select multiple txn
- then it will create an assignment prefilled with:
+ Search field = *PREFILLED* + memo
+ cat/pay/paymode prefilled with the one from each txn"
1810622,2019-09-27 21:20:32 UTC,regular expression should handle this with |
1810622,2019-09-27 21:23:35 UTC,"I confirm just use
(Bob|Martin|Shell)"
1810625,2019-02-09 10:25:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810626,2019-05-15 11:04:34 UTC,"Hi there, I'm going to move this conversation over to our new bug tracker on GitLab. This will make it easier for us to discuss a solution. Please check there for future updates. Thank you!"
1810626,2019-05-04 16:37:13 UTC,Arghs... I had high hopes for this one to 'just work'...
1810626,2019-05-04 12:29:18 UTC,"I just tested this with 1.0alpha (56f1b1b843, 2019-04-29) and this was not fixed."
1810626,2019-05-04 11:47:05 UTC,"(I assume this might be fixed already, due to the unicode migration that was done with extensions, but needs testing)"
1810626,2019-05-02 23:40:45 UTC,"So, to be more clear: This issue isn't currently reproducible because another issue is making it untestable. That is not the same as saying that this issue is fixed now."
1810626,2019-05-02 23:38:41 UTC,"Hi Firoz, I'm a long-term Inkscape project member, and I will retest this when the extension works again. I will leave this open. Thanks for your understanding."
1810626,2019-05-02 21:02:13 UTC,"Hi Hachmann,"
1810626,2019-05-01 23:13:09 UTC,Thanks for looking at this.
1810626,2019-05-01 21:49:40 UTC,"Closing because Inkscape 1.0 has a different bug with Text > Extract, currently being investigated here: https://gitlab.com/inkscape/inbox/issues/409"
1810626,2019-05-02 23:41:23 UTC,Only issues that are FIXED should be marked as such without migration.
1810627,2019-05-01 21:45:03 UTC,Closing because Inkscape 1.0 produces a different error when using Text > Merge and is currently being investigated here: https://gitlab.com/inkscape/inbox/issues/412
1810627,2019-05-01 23:14:35 UTC,"I disagree that that issue supersedes this one. Please migrate this, or keep it open."
1810627,2019-05-01 23:15:06 UTC,(This requires retesting once the extension works at all)
1810627,2019-05-02 23:36:41 UTC,? Undoing again. Please stop the 'edit war'.
1810627,2019-05-04 06:05:21 UTC,"That bug does not refer to this error, and solving that bug would not solve this one. Please either migrate the bug as a separate issue or keep it open here. Thank you."
1810627,2020-01-07 15:15:07 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1810629,2019-02-08 11:40:06 UTC,"oh.... I see, you need a writable /usr to fix the issue..."
1810629,2019-02-08 11:39:03 UTC,please update it!
1810629,2019-02-04 16:58:58 UTC,It is also impossible to remove or purge virtualbox-ext-pack 5.2.18-1~ubuntu18.04.1
1810629,2019-02-04 16:56:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810634,2019-01-20 01:49:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810634,2019-01-20 03:40:50 UTC,I have the same problem. The fcitx-hangul package is missing.
1810634,2019-01-23 02:13:54 UTC,affect me
1810634,2019-01-24 20:10:44 UTC,List of Input Methods of Fcitx what I know in other languages by alphabet orders
1810634,2019-04-10 17:49:19 UTC,"https://launchpad.net/~wxl
@wxl
Can you check this out?"
1810634,2019-04-16 05:16:58 UTC,"From 16.04 to 19.04, Lubuntu has shipped the fcitx input method framework, yet it has not included support for Korean, such as found in the fcitx-hangul package. In fact, even in 14.04, which used the iBus input method framework, no Korean support was included."
1810634,2019-04-16 07:30:12 UTC,"Thank you ^^
Then, now we are about start to ship input methods.
Good news!!"
1810636,2019-01-06 17:14:10 UTC,board-2.bin is also required.
1810636,2019-01-06 21:56:16 UTC,"@kaihengfeng - after adding board-2.bin, neither the wireless or bluetooth is loading. I've ensured I downloaded the files correctly and used the same file permissions."
1810636,2019-01-06 22:11:09 UTC,@kaihengfeng - do I need to do an update-initramfs -u -v -k all and then shutdown completely after placing the files?
1810636,2019-01-07 04:04:54 UTC,"No, ath10k_pci is not included in the initramfs so replace firmware alone is sufficient."
1810636,2019-01-07 08:53:52 UTC,"Ok, I managed to get the latest firmware working. It still exhibits the same issue. I think I must of only rebooted last time instead of shutting down completely."
1810636,2019-01-07 09:22:37 UTC,"Here is a demo of the stuttering sound, you can hear it at around 11 seconds after I start a file copy over SMB."
1810636,2019-01-07 20:54:03 UTC,"It might be worth saying, however, without the pulseaudio-modules-bt in [2] in comment #27, the throughput of the WLAN was not affected when playing sound via the A2DP sync and I was seeing abotu 18 MB/s. Maybe I'm a bit premature in saying it's solely a pulseaudio-modules-bt issue. Regardless, it seems to be working a lot better with LDAC."
1810636,2019-01-07 15:02:45 UTC,"Subscribed ath10k maintainer. I think he uses Launchpad, but if he doesn't reply here, please raise this issue to <email address hidden>."
1810636,2019-01-07 20:46:35 UTC,"Ok, I'm pretty sure this is a pulseaudio issue now and I'm going to close."
1810636,2019-01-06 13:32:05 UTC,"@kaihengfeng I did try the latest version of the QCA6174 4.4.1 firmware which matches the firmware in linux-firmware v176, and the result is the same. I replaced firmware-6 file in the /lib/firmware/ath10k/QCA6174/hw3.0 folder to test this."
1810636,2019-01-19 11:45:17 UTC,"I'm happy this is pretty much solve. With the pulseaudio-modules-bt from comment 27 [2], I've experienced far less audio lag overall. Every now and again I get a small glitch that delays it 10ms or so, but it's so much better now I'm happy to close this and mark it as non-issue."
1810636,2020-04-19 06:01:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810636,2019-01-07 09:26:45 UTC,"To clarify, higher bandwidth transfers on the radio seems to increase the stuttering, delay."
1810636,2019-01-06 11:13:50 UTC,Does firmware in [1] help?
1810636,2019-01-06 04:51:27 UTC,apport information
1810636,2019-01-06 04:51:48 UTC,apport information
1810636,2019-01-06 02:49:56 UTC,"3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
 Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 138
 Region 0: Memory at ed200000 (64-bit, non-prefetchable) [size=2M]
 Capabilities: [40] Power Management version 3
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
  Address: fee00498  Data: 0000
  Masking: 000000fe  Pending: 00000000
 Capabilities: [70] Express (v2) Endpoint, MSI 00
  DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
  DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 256 bytes, MaxReadReq 512 bytes
  DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
  LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
   ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
  LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
   ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
  LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
  DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
  LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
    Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
    Compliance De-emphasis: -6dB
  LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
    EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
 Capabilities: [100 v2] Advanced Error Reporting
  UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta:	RxErr+ BadTLP- BadDLLP+ Rollover- Timeout+ NonFatalErr-
  CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
 Capabilities: [148 v1] Virtual Channel
  Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
  Arb:	Fixed- WRR32- WRR64- WRR128-
  Ctrl:	ArbSelect=Fixed
  Status:	InProgress-
  VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
   Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
   Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
   Status:	NegoPending- InProgress-
 Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00
 Capabilities: [178 v1] Latency Tolerance Reporting
  Max snoop latency: 3145728ns
  Max no snoop latency: 3145728ns
 Cap..."
1810636,2019-01-06 03:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810636,2019-01-06 04:51:51 UTC,apport information
1810636,2019-01-06 04:51:29 UTC,apport information
1810636,2019-01-06 04:51:31 UTC,apport information
1810636,2019-01-06 04:51:34 UTC,apport information
1810636,2019-01-06 04:51:25 UTC,apport information
1810636,2019-01-06 04:51:37 UTC,apport information
1810636,2019-01-06 04:51:38 UTC,apport information
1810636,2019-01-06 04:51:40 UTC,apport information
1810636,2019-01-06 04:51:41 UTC,apport information
1810636,2019-01-06 04:51:43 UTC,apport information
1810636,2019-01-06 04:51:45 UTC,apport information
1810636,2019-01-06 04:51:35 UTC,apport information
1810640,2019-01-06 09:48:39 UTC,"Apparently the cleanup, that is done at normal script termination, is not done in this case.
I will fix asap."
1810640,2019-01-06 18:47:45 UTC,"should be fixed.
a test is appreciated."
1810645,2019-12-23 16:46:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810649,2020-03-16 18:47:42 UTC,This bug was fixed in the package ffmpeg - 7:4.2.2-1ubuntu1
1810649,2020-03-16 10:18:42 UTC,"Since the NEW package has been reviewed and ACKed by an AA, this looks good to go. Approving the FFe."
1810649,2020-03-14 08:54:00 UTC,nv-codec-headers is now in Focal proposed pocket (pending new binary acceptance) LP: #1866709
1810649,2020-03-14 12:43:03 UTC,Will this be backported to Eoan?
1810649,2019-05-14 17:15:59 UTC,"Yes, it is very simple to fix, I built all that for ROSA Linux, nothing unusual"
1810649,2019-04-19 09:15:05 UTC,Is there a detailed work around for this?
1810649,2019-05-14 16:41:39 UTC,"NVENC now have a seperate upstream and are a build dependency of other packages, not onl;y ffmpeg, but e.g. also e.g. handbrake"
1810649,2019-01-29 14:10:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810649,2019-03-13 21:57:54 UTC,On ubuntu 18.10 the hevc_nvenc codec is also missing. ffmpeg doesn't list --enable-nvenc as one of it's configure flags that was used.
1810649,2019-05-14 16:55:53 UTC,"All the more reason this issue should be easily fixable by referencing that package as a builddep... again, unless licensing issues come into play."
1810649,2019-05-14 15:23:38 UTC,The help at https://askubuntu.com/questions/778100/how-to-install-compile-nvenc-in-ubuntu is how I got to build working packages in my system (19.04 fresh install).
1810649,2019-04-06 12:12:04 UTC,"Hi, I was wondering the same question. Why did it worked in the past and now not anymore?"
1810654,2019-01-06 16:52:40 UTC,The attached patch solves the issue.
1810657,2020-08-07 02:09:36 UTC,"Hi,Eric, I got error: tox: command not found. Why did you set the problem is Invalid ?"
1810660,2019-01-08 16:31:15 UTC,The issue seems similar to upstream https://gitlab.gnome.org/GNOME/gnome-control-center/issues/138
1810660,2019-01-08 21:25:07 UTC,"Yes, seems to be the same. Running nm-connection-editor instead allows to save the configuration without a specific gateway."
1810661,2019-01-08 20:32:01 UTC,"Makes sense. On percentages, it would be least fragile to pass that down to the lowest level tool that can handle them, which means changes to curtin at least."
1810661,2020-06-05 06:45:16 UTC,"In the meanwhile, is there any way to tell subiquity/curtin to use all remaining disk space for certain partitions? This would really help creating generic cloud-init configuration that works on multiple types of machines!"
1810662,2020-10-22 20:07:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu."
1810665,2019-01-06 16:19:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1810665,2019-11-14 02:00:33 UTC,The missing dependency issue should be fixed in 19.10
1810667,2019-01-07 12:28:58 UTC,We did a lot of prelilminary troubleshooting here:  https://forum.inkscapecommunity.com/index.php?topic=1483.0
1810667,2019-01-25 03:24:48 UTC,I noticed this message in a different forum:  http://www.inkscapeforum.com/viewtopic.php?f=29&t=34412
1810671,2019-05-21 03:41:16 UTC,"Hello, apologies for the delayed response. Have you been able to get it working yet?"
1810671,2019-09-19 12:09:58 UTC,"Closing as there has been no activity for 60 days. If you still have this problem, check the already reported issues at https://inkscape.org/report. Thank you!"
1810683,2019-06-30 08:58:47 UTC,Does anybody care about lightdm bugs? I'm still seeing this issue but I haven't found a way to debug it. Is there some environment variable or some other method that can make all g_debug() messages visible from lightdm? Currently no log seems to contain any of the g_debug() messages in the lightdm source code.
1810685,2019-01-08 21:55:01 UTC,Fixed in x.4334.
1810693,2019-01-07 00:40:37 UTC,"This is the link to the breeze-skin:
https://addons.videolan.org/p/1183821/
https://github.com/varlesh/VLC-Breeze"
1810693,2019-01-07 23:55:16 UTC,*** This is an automated message ***
1810701,2019-01-07 03:48:57 UTC,"Also, this is the 5.0.2 stable release for macOS 10.14 found here: http://kicad-pcb.org/download/osx/"
1810701,2019-01-07 03:55:04 UTC,Please add the crash report from eeschema listed in the console log:
1810701,2019-01-07 04:28:08 UTC,"Sorry, this is my first Rodeo.
I think this is what you are looking for.."
1810701,2019-01-07 13:41:58 UTC,Can you please try one of the test builds form http://downloads.kicad-pcb.org/osx/testing/5.0/ ?
1810701,2019-01-07 16:51:53 UTC,Still crashing. Thanks for your super fast responses. I really appreciate it.
1810701,2019-01-07 20:18:50 UTC,Can you start the main KiCad application?
1810701,2019-01-07 20:29:05 UTC,Woohoo! That worked. I was also able to open eeschema from the main application.
1810701,2019-01-07 20:50:11 UTC,"OK, that's good to know and will help us track this down.  It looks like there is a packaging issue with how the dynamic libs are linked."
1810701,2019-01-07 20:51:57 UTC,@Adam-  Do you think that this is the same issue as the others?  Chase is on 10.13
1810701,2019-05-01 12:09:20 UTC,The 5.0 branch is no longer supported. Does this still occur with the latest stable release (5.1.2)?
1810701,2019-07-01 04:17:22 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1810703,2019-01-07 19:52:17 UTC,"Hi,"
1810703,2019-02-16 21:14:20 UTC,"Hi,
Was the bug solved?"
1810703,2019-03-06 20:41:06 UTC,This issue was fixed in x1.3.1-27.
1810707,2019-02-19 16:23:08 UTC,"Reviewed:  https://review.openstack.org/628862
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=77998d4316436b3cf97c6d9f7c8b71f8f0701a64
Submitter: Zuul
Branch:    master"
1810707,2019-02-19 16:23:00 UTC,"Reviewed:  https://review.openstack.org/628871
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=6ab8c4511d3fff5db3cc192f4de1e96397aafdb4
Submitter: Zuul
Branch:    master"
1810707,2019-01-07 06:29:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/628871"
1810707,2019-01-07 06:08:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/628862"
1810712,2019-01-07 06:32:00 UTC,Full logs from juju-machine-74 machine.log are available at https://private-fileshare.canonical.com/~jsing/lp1810712/juju-machine-74.log.gz
1810712,2019-01-07 13:16:50 UTC,"These particular lines seem suspicious:
2018-12-30 01:09:29 ERROR juju.worker.dependency engine.go:632
""migration-inactive-flag"" manifold worker returned unexpected error: txn
watcher restarted
2018-12-30 01:09:29 ERROR juju.api.watcher watcher.go:92 error trying to
stop watcher: txn watcher restarted
2018-12-30 01:09:29 ERROR juju.api.watcher watcher.go:92 error trying to
stop watcher: txn watcher restarted
2018-12-30 01:09:29 ERROR juju.api.watcher watcher.go:92 error trying to
stop watcher: txn watcher restarted
2018-12-30 01:09:29 ERROR juju.api.watcher watcher.go:92 error trying to
stop watcher: txn watcher restarted"
1810712,2019-01-08 03:26:14 UTC,"This is a machine in a non-controller model. Given the repeated controller failures were primarily due to mongo becoming desynced, it could make sense that the controller was failing to connect to mongo - if so, this would be fairly easy to reproduce/test (i.e. shutdown mongo on the controllers)."
1810712,2019-01-08 16:35:33 UTC,This seems like something we can dig into better messaging and possibly double checking the failure case of a controller getting desync'd and how the agents talking to that controller recover.
1810714,2019-01-08 16:32:41 UTC,"Thanks, I can't disagree with what you've got here. It's something we should get into some discussions and see about plotting out a proper path for some self-healing around this for sure."
1810729,2019-01-07 18:06:34 UTC,I uploaded this so I'm unsubscribing ubuntu-sponsors.
1810729,2019-01-07 23:55:05 UTC,*** This is an automated message ***
1810742,2019-01-17 15:18:06 UTC,(see bug #1811489)
1810742,2019-01-17 15:16:00 UTC,"oh, also do we still need that package? it was added for xubuntu/lubuntu which were still using gtk2 at the time but xubuntu switched to gtk3 since no? (and is lubuntu still a thing?)"
1810742,2019-01-11 08:20:38 UTC,"The attachment ""deprecated_declarations.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1810742,2019-01-17 15:12:34 UTC,"The patch doesn't do what the title/description claims, you remove -Werror (which is fine) which has impact on warning other than the 'deprecated-declarations' ones"
1810742,2019-01-11 06:51:29 UTC,The patch is attached.
1810742,2019-01-17 15:14:51 UTC,"Also what vcs are you talking about? Did we have one for the gtk2 compat version? If so could you share the url, maybe we can get that one updated?"
1810745,2019-09-25 20:17:04 UTC,"Only HPLIP have problems with showing icon.
Other apps as RedShift and Solaar do not have such a problem on upcoming Ubuntu MATE 19.10."
1810745,2020-03-22 12:26:42 UTC,Still not fixed in Ubuntu MATE 20.04 LTS installed from 20200321.
1810745,2019-12-24 16:21:11 UTC,"Does not seem specific to Mate, here is Ubuntu Budgie 18.04 → https://discourse.ubuntubudgie.org/t/hplip-hplip-toolbox-broken-in-budgie/2749/26?u=coeur-noir"
1810745,2019-01-10 09:43:38 UTC,As I have already wrote on AskUbuntu ( https://askubuntu.com/a/1107774/66509 ):
1810745,2019-01-07 16:08:16 UTC,"Same problem here - the hplip version is 3.17.10+repack0-5,m btw. (not exactly recent, it could really use an SRU to the latest upstream release)."
1810745,2019-01-07 17:00:02 UTC,Ubuntu MATE 19.04 (disco) is affected too.
1810745,2019-01-07 16:43:10 UTC,Ubuntu MATE 18.10 (cosmic) is affected too.
1810745,2019-01-07 16:01:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810745,2019-01-07 09:45:58 UTC,Hmm feels more a hp-lip problem then a Ubuntu Mate one
1810745,2019-03-29 16:48:24 UTC,Still a problem for Ubuntu MATE 19.04 beta2.
1810746,2020-06-26 06:36:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810746,2020-06-26 06:39:08 UTC,"the same is happening to me when using Ubuntu 18.04. With ubuntu 20.04 everything works just fine, though."
1810746,2020-06-26 06:41:48 UTC,"At least, I just discovered a workaround: by double clicking on the tray icon, you can take a screenshot."
1810764,2019-01-07 10:33:14 UTC,"2018-12-22 03:59:26.233 | +functions-common:service_check:1545      (B sudo systemctl status <email address hidden> --no-pager
2018-12-22 03:59:26.279 | ● <email address hidden> - Devstack <email address hidden>
2018-12-22 03:59:26.279 |    Loaded: loaded (/<email address hidden>; enabled; vendor preset: enabled)
2018-12-22 03:59:26.280 |    Active: failed (Result: exit-code) since Sat 2018-12-22 03:59:22 UTC; 3s ago
2018-12-22 03:59:26.280 |   Process: 14962 ExecStart=/usr/local/bin/neutron-openvswitch-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini.domU (code=exited, status=1/FAILURE)
2018-12-22 03:59:26.280 |  Main PID: 14962 (code=exited, status=1/FAILURE)
2018-12-22 03:59:26.280 |    CGroup: /<email address hidden>
2018-12-22 03:59:26.280 |
2018-12-22 03:59:26.280 | Dec 22 03:59:22 DevStackOSDomU neutron-openvswitch-agent[14962]: DEBUG oslo.privsep.daemon [-] privsep: request[140688752052816]: (3, 'neutron.privileged.agent.linux.ip_lib.get_ip_addresses', (None,), {'index': 6, 'address': '10.71.136.118'}) {{(pid=15427) loop /usr/local/lib/python2.7/dist-packages/oslo_privsep/daemon.py:443}}
2018-12-22 03:59:26.280 | Dec 22 03:59:22 DevStackOSDomU neutron-openvswitch-agent[14962]: DEBUG oslo.privsep.daemon [-] privsep: reply[140688752052816]: (4, ()) {{(pid=15427) loop /usr/local/lib/python2.7/dist-packages/oslo_privsep/daemon.py:456}}
2018-12-22 03:59:26.280 | Dec 22 03:59:22 DevStackOSDomU neutron-openvswitch-agent[14962]: DEBUG oslo.privsep.daemon [-] privsep: request[140688752052816]: (3, 'neutron.privileged.agent.linux.ip_lib.get_ip_addresses', (None,), {'index': 7, 'address': '10.71.136.118'}) {{(pid=15427) loop /usr/local/lib/python2.7/dist-packages/oslo_privsep/daemon.py:443}}
2018-12-22 03:59:26.280 | Dec 22 03:59:22 DevStackOSDomU neutron-openvswitch-agent[14962]: DEBUG oslo.privsep.daemon [-] privsep: reply[140688752052816]: (4, ()) {{(pid=15427) loop /usr/local/lib/python2.7/dist-packages/oslo_privsep/daemon.py:456}}
2018-12-22 03:59:26.281 | Dec 22 03:59:22 DevStackOSDomU neutron-openvswitch-agent[14962]: DEBUG oslo.privsep.daemon [-] privsep: request[140688752052816]: (3, 'neutron.privileged.agent.linux.ip_lib.get_ip_addresses', (None,), {'index': 8, 'address': '10.71.136.118'}) {{(pid=15427) loop /usr/local/lib/python2.7/dist-packages/oslo_privsep/daemon.py:443}}
2018-12-22 03:59:26.281 | Dec 22 03:59:22 DevStackOSDomU neutron-openvswitch-agent[14962]: DEBUG oslo.privsep.daemon [-] privsep: reply[140688752052816]: (4, ()) {{(pid=15427) loop /usr/local/lib/python2.7/dist-packages/oslo_privsep/daemon.py:456}}
2018-12-22 03:59:26.281 | Dec 22 03:59:22 DevStackOSDomU neutron-openvswitch-agent[14962]: ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Tunneling can't be enabled with invalid local_ip '10.71.136.118'. IP couldn't be found on this host's interfaces.
2018-12-22 03:59:26.281 | Dec 22 03:59:22 DevStackOSDomU systemd[1]: <email address hidden>: Main process exited, code=exited, status=1/FAILURE
2018-12-22 03:59:26.281 | Dec 22 03:59:22 DevStackOSDomU systemd[1]: devstack@q-do..."
1810769,2019-09-09 22:19:33 UTC,"Ouh, I never tested but ""+"" and ""-"" works to expand/collapse but the most of the time KiCad opens the filter and start to type ""+-""."
1810769,2019-09-09 22:16:49 UTC,"This ""issue"" was always in KiCad Linux-Ubuntu 16 build. I am just reporting because works normal in Windows (as far I tested) and it is some expected behavior of a tree graphical object."
1810769,2019-09-10 12:58:24 UTC,"@Ian, thanks for the heads up.  I wonder if this was a good idea.  I'm sure who ever wrote this assumed that it was.  I'm not as confident in this decision.  I guess at the very least we should try to make the arrow keys work on gtk builds.  It would be interesting to see what would happen if we stripped out our custom tree key event behavior and used the stock wxWidgets behavior.  Maybe I will be able to find some time to test this."
1810769,2019-09-09 22:05:47 UTC,"@Wayne, that appears to be KiCad specific (look inside LIB_TREE::onQueryCharHook). It appears that we also implemented the +/- expand/collapse separate from the platforms in there as well."
1810769,2019-09-10 15:50:31 UTC,"+/- are standard expand/collapse keys under GTK.  The work this way for Gimp, Inkscape, FreeCAD, LibreOffice.  I haven't found an application yet that doesn't accept them.  They only start the search function in the tree when you are not on an expandable element.  This is also expected."
1810769,2019-09-10 16:17:10 UTC,LibreOffice works with both: +/- and <left>/<right>.
1810769,2019-09-10 16:17:48 UTC,I just tested this and indeed this is the correct behavior on gtk so I agree that this bug report is not valid.
1810769,2019-09-10 13:55:49 UTC,"Using ""-"" do collapse maybe a not good idea since it is used in some part description (such ""regulator -5V"")."
1810769,2019-09-09 21:47:04 UTC,I would prefer the native behavior as well but it's not quite that simple.  The wxWidgets folks apparently decide that they disagreed with the gtk folks and used the return key to expand and collapse the tree view widget (unless we did it somewhere that I am not seeing) so it's not quite the same as the standard gtk behavior.
1810769,2019-05-06 12:34:02 UTC,"Yes, still not on Linux (GTK 2)."
1810769,2019-09-09 20:45:49 UTC,"I'd vote for sticking to platform specific standards (or lack thereof). If GTK supports this in the future, hopefully it will be picked up by wxWidgets and trickle down into KiCad."
1810769,2019-09-09 20:53:08 UTC,"I'd normally vote for platform conventions as well, but this might be a special case.  Then again, I'm not a GTK user, so I'd rather defer to those that are...."
1810769,2019-05-06 13:11:42 UTC,"@Hildo, thanks for reporting back. Do the left/right arrow keys not work in other tree controls (eg Library editor tree controls, preferences dialog etc.)?"
1810769,2019-05-06 13:56:59 UTC,The left/right works fine in other dialog with the function like select cell in tables (Symbol Properties dialog). But doesn't in any three element (doesn't matter the dialog).
1810769,2019-05-08 23:48:32 UTC,Should this issue be pumped from Whishlist to low priority?
1810769,2019-05-05 12:45:49 UTC,"@Hildo, I just tested this with 5.1.2 on Windows and macOS, and the arrow keys work as you describe. Does this still not work on Linux?"
1810769,2019-09-09 20:03:24 UTC,Has anyone actually tested any other native GTK apps to determine what the default behavior is supposed to be for tree controls.  I tested this using the GIMP application and the tree control in the preferences dialog and it did not behave this way.  I know this is not a definitive test but assuming the behavior would be the same as MSW and macos may not be valid.
1810769,2019-09-09 20:16:39 UTC,"Testing with an app I have on my system that seems to be installed with gtk3 I have gtk3-widget-factory, and on the tab page 3 there is a tree control. I can't make it do any folding/un-folding with the arrowkeys or any other way than to click with the mouse."
1810769,2019-09-07 21:46:49 UTC,"It is not GTK2 specific, since it also happens on my GTK3 builds. It also hasn't been fixed by wxWidgets, since it exists when I run KiCad with their current master branch."
1810769,2019-09-09 20:33:48 UTC,"This behavior is a point of contention in the GTK community apparently. The keys that expand/collapse the items in my window manager is Shift+Left/Shift+Right, but that expands/collapses all sub items of the selected item. There has been a bug filed against GTK to get them to make this change (https://gitlab.gnome.org/GNOME/gtk/issues/717), and it seems to be a large annoyance for users based on a quick web search (mainly because they don't really document the key bindings for it). Most people seem to prefer the Windows/Mac way of doing it (using unmodified arrow keys), so I guess the question is do we follow the Gnome method (that isn't actually listed in their UI guide) or make it consistent across the platforms."
1810771,2019-01-09 21:30:00 UTC,"Hmm...Is this same for mate too. No? What is the content of etc/xdg/autostart/hplip-systray.desktop ? For some reason it is not generating the menu. Though for me, it works fine. May be something to do with LP: #1688684"
1810771,2019-01-10 10:32:48 UTC,The desktop-file is default:
1810771,2019-01-11 06:43:13 UTC,"It seems dbus realted issue, on unity it simply couldn't get the bus. But dbus-launch works for me. Ask the maintainer (~till-kamppeter )to upload new version of hplip."
1810774,2019-04-10 15:34:26 UTC,It seems my issue is described here
1810775,2019-01-07 12:24:19 UTC,Join all `core.gz.00N` to get the gzipped core dump.
1810780,2019-01-07 12:48:04 UTC,"This also affects cosmic, but is not worth an SRU of its own just for that."
1810780,2019-01-07 18:19:01 UTC,"Debian just fixed it, and we will get that in our next sync."
1810780,2019-04-08 07:27:55 UTC,"cosmic ftbfs:
https://launchpadlibrarian.net/418304881/buildlog_ubuntu-cosmic-amd64.lftp_4.8.4-1_BUILDING.txt.gz"
1810780,2019-06-25 18:46:47 UTC,"This is fix released in the devel release, which was disco back then. A cosmic task can be added, but it's probably not worth an SRU just for this."
1810785,2019-01-07 19:18:33 UTC,"Have I really made this ticket on CFFI and not SBCL? Oh good gods, now that's embarassing..."
1810786,2020-01-10 20:26:44 UTC,How do I use this as a new software source?  Software Sources rejects every attempt I've made to enter this under Additional Repositories.
1810786,2019-06-14 00:27:28 UTC,The fix in Debian:
1810786,2019-06-14 00:21:02 UTC,"I see that this bug has been fixed in disco (19.04).  Could we get the fix backported to bionic (18.04)?  I'm willing to help if someone could point me in the correct direction.  I know software and compiling, though I am not familiar with .deb packaging."
1810786,2019-02-14 22:59:45 UTC,"Scratch that. I just found out that the build of SILO I was doing from source is somehow different from libsiloh5-0, but it includes the silo_exports.h so things things were silently breaking until I uninstalled libsiloh5-0"
1810786,2019-02-06 18:42:14 UTC,"I was also using libsilo-dev under 16.04 and everything was fine.
Then I upgraded to 18.04 (and reinstalled libsilo) and my previously working builds using silo broke."
1810786,2019-02-06 18:01:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810786,2019-02-15 09:02:16 UTC,So can somebody of the packagers help us? I want to have parflow running in a docker container and thus it would be cool to activate silo without recompiling libsilo in it.
1810796,2019-01-09 14:40:23 UTC,"To you have the ability to test with MAAS 2.5? I believe this issue has been fixed in that release. At the moment I cannot find the bug to reference for you, but I do believe this is fixed."
1810796,2019-03-11 04:17:24 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1810796,2019-03-11 09:47:07 UTC,I have tried 2.5 for one month and currently no similar issue was found. Thanks.
1810796,2019-03-22 04:39:50 UTC,"Hi, the issue happens with v2.5 MaaS."
1810796,2019-03-22 04:43:02 UTC,log for comment#6 https://bugs.launchpad.net/maas/+bug/1810796/comments/6
1810796,2019-05-14 13:30:32 UTC,"@taihsiangho I would suggest to investigate a reliable steps to reproduce the issue with newer version of maas. If we can not reproduce the issues, we can close this bug and report it again once we are seeing the issue."
1810796,2019-06-11 03:53:33 UTC,"Per  MAAS version: 2.3.0 (6434-gd354690-0ubuntu1~16.04.1), I am aware when this issue happens, only the ip address (e.g. ""IP for APC PDU"" field) was changed. The ""APC PDU node outlet number"" field is unchanged."
1810796,2019-09-20 11:33:29 UTC,I don't understand exactly what the problem here is.
1810796,2019-11-12 04:22:52 UTC,@bjornt Thank you for your comments.
1810796,2019-11-13 04:03:45 UTC,I made a merge request to make the front-end message more explicit and to confirm what I understand now is expected from yours. I will appreciate if someone could have a look of the merge request https://code.launchpad.net/~taihsiangho/maas/+git/maas/+merge/375466  Thanks.
1810796,2020-08-20 14:21:34 UTC,I think the corresponding fix was committed a while ago. Not sure if it is landed in the recent maas.
1810799,2020-06-07 04:17:23 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1810799,2019-01-08 08:37:08 UTC,This resembles https://bugs.launchpad.net/tripleo/+bug/1802203
1810799,2019-02-19 13:30:34 UTC,Is this still an issue?
1810799,2019-02-19 14:11:39 UTC,"I'm not sure. I just disabled selinux to ""fix"" it ;)"
1810799,2019-01-07 16:51:26 UTC,"Hey,"
1810805,2019-01-07 16:19:59 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1810805,2019-01-07 16:27:56 UTC,Hello
1810805,2019-01-08 06:40:22 UTC,The name of the installer program is ubiquity. I am assigning this bug to the package that I believe is correct.
1810805,2020-03-07 10:27:53 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1810805,2020-05-07 04:17:19 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1810810,2019-09-10 21:21:59 UTC,https://github.com/mixxxdj/mixxx/pull/2276
1810810,2019-12-13 12:33:58 UTC,"not entirely fixed. features still get activated after
* renamed crate/playlist
* un/locked crate/playlist
* toggle 'Auto DJ Track Source'"
1810810,2021-01-11 01:50:22 UTC,"Funny thing is:
if I set the default to 1 (AutoDJ) it works correctly.
https://github.com/mixxxdj/mixxx/blob/5cc093d35ef1c20ad3dd44d78b247cdb74ecda00/src/library/sidebarmodel.cpp#L26"
1810813,2020-10-22 19:13:24 UTC,closing since the package is removed from Ubuntu
1810815,2020-04-14 08:17:30 UTC,Let's assume this is the same as bug 1868240 for now. I will post updates in bug 1868240 in the coming weeks.
1810815,2019-01-07 17:10:01 UTC,Plymouth logs in syslog are:
1810815,2019-12-24 03:08:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810816,2019-01-14 16:17:06 UTC,also cosmic seems to work!
1810816,2019-01-24 10:26:56 UTC,This bug was fixed in the package hedgewars - 0.9.25-5~ubuntu18.04.1
1810816,2019-01-21 12:08:57 UTC,"The verification of the Stable Release Update for hedgewars has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1810816,2019-01-21 12:08:52 UTC,This bug was fixed in the package hedgewars - 0.9.25-5~ubuntu18.10.1
1810816,2019-01-14 16:15:56 UTC,also upgrade works from current version
1810816,2019-01-10 12:48:25 UTC,"-5 is now in release pocket, migrated with qt yesterday."
1810816,2019-01-14 13:18:55 UTC,"Hello Gianfranco, or anyone else affected,"
1810816,2019-01-14 13:16:15 UTC,"Hello Gianfranco, or anyone else affected,"
1810816,2019-01-14 13:15:56 UTC,"Indeed, no sense in having an outdated version for an LTS. Approving."
1810816,2019-01-10 12:49:51 UTC,"I think supporting Bionic and Cosmic is feasible, also xenial is with some minor changes"
1810816,2019-01-07 17:14:27 UTC,"the -5 didn't migrate yet, because of gnutls28/qt that is being worked on."
1810816,2019-01-14 16:15:44 UTC,"just tested bionic, game starts and works."
1810827,2019-09-19 10:21:37 UTC,I mean the crash is not frequent enough.
1810827,2019-09-19 10:21:22 UTC,"There is a fix available, but is not frequent enough and there is a simple workaround: restart instead of reload. Also only that specific ""force group"" config change is affected."
1810827,2019-09-10 17:24:24 UTC,Still in our queue.
1810827,2019-07-11 16:28:59 UTC,"The upstream bug is marked resolved, and includes patches backported to various samba versions.  I haven't examined them for the nature of the fix but with them now released and available this issue may be worth another look."
1810827,2019-01-08 19:43:28 UTC,I can reproduce this crash with the instructions from the samba upstream bug:
1810827,2019-01-08 19:06:00 UTC,This might be https://bugzilla.samba.org/show_bug.cgi?id=13690
1810831,2020-08-17 22:15:18 UTC,"I've been trying to reproduce this bug reported last year in Inkscape 1.0 on Windows 10 64-bit, but I'm not experiencing any crashing. This issue might have been solved in the this latest release."
1810831,2019-03-19 03:29:39 UTC,"I can reproduce with 0.92.3 on Windows 10 64-bit, let me try with 0.92.4 and get a backtrace for this."
1810831,2019-01-08 11:55:32 UTC,could you try running Inkscape from DOS with a command like this:
1810831,2019-01-08 19:51:58 UTC,"thanks for testing.
I have not been able to reproduce the problem, on Windows 10, [Version 10.0.17763.195],
with Inkscape 0.92.3 (2405546, 2018-03-11) (32 bit version)"
1810831,2019-01-08 18:04:56 UTC,"I started it with CMD and when the crash occurs, there is still nothing. It it supposed to output nothing when everything is apparently going well? Are there any ways (besides recompiling) to enable a higher logging level?"
1810831,2019-01-08 21:09:31 UTC,Unfortunately gdb keeps crashing too. Tried from both the gdb and Inkscape directories. Bit width is correct otherwise it doesn't even recognize it as an executable.
1810835,2021-02-23 22:59:14 UTC,This logic has been completed.
1810844,2019-07-18 14:34:24 UTC,MIR at LP: #1811139 has been Fix Released. Marking this as Fix Released as well.
1810844,2019-01-09 19:54:39 UTC,MIR being prepared: https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/1811139
1810845,2019-01-07 19:44:37 UTC,"Application: kicad
Version: (6.0.0-rc1-dev-1489-gcec97ebfa6-dirty), release build
Libraries:
    wxWidgets 3.0.4
Platform: Linux 4.18.0-3-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Compiler: GCC 8.2.0 with C++ ABI 1013"
1810845,2019-01-07 20:02:01 UTC,"Forgot to add that the rule and violation should be shown together.  For example, ""Measured 3.98 mils, rule requires 4.00 mils"".  This allows me to know which rule is being used."
1810848,2019-01-07 19:52:27 UTC,"Items that are visible in the OPAC, but not holdable, are also not viewable basket in either the staff client or OPAC. Both staff and patrons would want to be able to use the print and email functions for these titles"
1810851,2019-01-09 22:38:40 UTC,Confirmed in 3.2.2. The web staff client requires that you also take the action to Suspend Hold.
1810853,2021-01-12 00:01:08 UTC,Confirming that this is still an issue in 3.5
1810854,2019-01-09 22:43:37 UTC,In 3.2.2 I'm able to successfully merge a patron that is in collections with a patron not in collections as long as the one in collections is the lead.
1810854,2019-11-01 19:41:00 UTC,"Confirmed in 3.3.4. Unable to merge two accounts when the account in collections is not the lead account. In this case, the intended lead account has the up-to-date contact information and changes to name (no longer married), etc. that would be tedious to edit if the older (collection) account were made lead. Seems like this might be the case more often than not - collections account is the older one."
1810857,2019-10-21 14:35:55 UTC,"The verification of the Stable Release Update for cloud-utils has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1810857,2019-10-21 14:35:41 UTC,This bug was fixed in the package cloud-utils - 0.31-0ubuntu1.2
1810857,2019-10-16 17:29:23 UTC,Verified:
1810857,2019-09-24 18:01:02 UTC,"Hello Daniel, or anyone else affected,"
1810857,2019-09-24 06:58:10 UTC,I confirm version 0.31-0ubuntu1.1 indeed fixes the issue.
1810857,2019-07-31 16:36:29 UTC,"For the Disco SRU, what if some user is already relying on the typo'd option --reserveration-id. Won't this change break that user's automation? Do we need to support both in the SRU?"
1810857,2019-09-02 15:16:09 UTC,"Hello Daniel, or anyone else affected,"
1810857,2019-08-16 07:06:36 UTC,"@rbasak,"
1810857,2019-07-31 16:37:45 UTC,"While you're answering that, please complete the required SRU information in this bug!"
1810857,2019-07-14 03:31:08 UTC,This bug was fixed in the package cloud-utils - 0.31-3-gfadd07fe-0ubuntu1
1810857,2019-01-08 00:21:26 UTC,"The attachment ""ec2metadata.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1810857,2019-09-02 16:42:38 UTC,"All autopkgtests for the newly accepted cloud-utils (0.31-0ubuntu1.1) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1810857,2019-01-08 14:31:37 UTC,"Daniel,
Thanks for the bug report.
I've committed the fix to trunk."
1810858,2019-10-29 19:15:21 UTC,"Dear Maciej, can you please update this bug with relevant information. What is the situation in snapd 2.41?"
1810858,2019-03-13 04:33:38 UTC,"Looks like ""SELinux is preventing umount from 'getattr' accesses on the filesystem /."" may contain reports of one of these AVC denials: https://bugzilla.redhat.com/show_bug.cgi?id=1597878"
1810858,2019-03-13 07:02:13 UTC,See my previous comment. Things have slipped a bit and the current target for the fixes is 2.39.
1810858,2019-01-08 06:14:07 UTC,"Thanks for the report. The work to address this is ongoing, you can track it here: https://github.com/snapcore/snapd/pulls?q=is%3Apr+is%3Aopen+label%3ASELinux Since 2.37 release is near, I'm afraid the full set of fixes won't be available until 2.38."
1810859,2019-04-26 20:16:53 UTC,"> Would it be possible to have an option as Robert S. suggested
> or would it be possible to change Nocloud seed directory to
> another directory which is not likely to be on a separated filesystem ?
"
1810859,2019-03-21 14:24:01 UTC,"Hi, I have similar concern here."
1810859,2019-04-26 20:15:18 UTC,"The goal of ds-identify is ensure that cloud-init does not run unless a datasource is present.  We don't yet have the idea of ""present"" being much later than when the generators run.  Note that generators may run multiple times, including in the initramfs and as soon as root device is found."
1810859,2019-04-30 14:58:27 UTC,"@Robert,"
1810859,2019-04-30 15:23:11 UTC,"On Tue, Apr 30, 2019 at 10:11 AM Scott Moser <email address hidden>
wrote:"
1810859,2019-04-30 16:29:18 UTC,"@Scott,"
1810860,2019-03-26 09:48:01 UTC,This will be fixed in Clang 9
1810860,2019-01-14 20:52:23 UTC,Very funny. Arrgh.
1810860,2019-01-07 22:26:29 UTC,"Looks like this is by design:
https://github.com/llvm-mirror/clang/blob/master/lib/Driver/Driver.cpp#L1631"
1810860,2019-01-07 22:22:48 UTC,"oh, funny, I have been maintaining clang for a while and never noticed that :)"
1810860,2019-01-14 21:05:28 UTC,"I found similar error: https://bugs.llvm.org/show_bug.cgi?id=38836
Wanted to add my +1 to it, but registration is disabled at the moment. If you have account on clang bugzilla, maybe you could forward my opinion that this is a bug. and should be fixed?"
1810863,2019-01-10 00:28:44 UTC,"Here is the RMB menu from PADS.  Once you have chosen what you'd like to select, that is all you'll select until you change that choice.  That's the way Allegro works as well, and I don't see it as a burden, but rather, as the proper way to filter what you want to select.  Currently on the board I'm designing, I have to move all my reference designators, which is a pain because I have to use disambiguation on each click because they are all on top of footprints.  If I could tell Kicad I just want references, my work would be much easier."
1810863,2019-05-05 16:15:32 UTC,+1 https://bugs.launchpad.net/kicad/+bug/1827781 :-)
1810863,2019-01-10 16:38:26 UTC,"By the way at least now - I found faster way to applying Filter Selection:
1) Group select
2) RMB -> Key ""S"" -> ""Key"" F -> Key Enter"
1810863,2019-01-10 03:00:48 UTC,"No thing are intuitive, and make common to me so far on this when I doing silkscreen."
1810863,2019-01-10 03:00:04 UTC,"This may be another bug: Group select cannot select Reference Text. The reference text can only be selected by group select component (No mater where the reference text 1 miles aways still fine). Then uncheck all the filter, except the Text. Hit ok. NOTHING will be selected!"
1810863,2019-01-08 14:13:28 UTC,"An improved selection filter will come along with the Object Inspector. The current plan is to add a docked window where one quickly toggle filtering. Perhaps it will get a hotkey assigned too, I have not considered this yet."
1810863,2019-01-08 00:21:07 UTC,"In my experience, the typical way the selection filter works is by checking off the items you want to select before you actually do the selection. This is done with a selection menu either in a docked window or by simply right clicking on empty space in the layout. I find the way Kicad does it requires lots of clicking through menus and is generally awkward since it works by deselecting."
1810863,2019-01-08 10:44:21 UTC,"I don't like to enforce my bias in here yet. But instead I would like to further clarify my concern. That is, the new work flow for this selection filter seem to have some trivial issues. Let me do some comparison:"
1810863,2019-01-08 04:02:26 UTC,"I don't understand how pre-filtering (applying a predefined filter while you're selecting items) would be feasible. Mostly when I select items there are only one or a couple of them or there's otherwise no need for filtering. If an existing filter, which is remembered, would always be used, I would have to check checkbox items before doing even the most simple selections after I once have changed the settings for some rare case. I'd rather do extra work for those rare cases only, i.e. when I need filtering I filter, otherwise I get all items which I select."
1810863,2019-01-07 23:46:35 UTC,"OK, I'll try to understand better."
1810863,2019-01-07 23:31:04 UTC,"It do not applied on every selection actions. It only applied if you open the filter selection dialog, and hit on OK.
Or try this:
1) Select a group of items
2) Open the filter dialog, and turn of some of the item type in the group
3) The current selection will be correctly filtered.
4) Now do the group selection action again
5) Everything will be selected
6) Repeat step #2."
1810863,2019-01-07 23:28:13 UTC,The setting of filter selection are been remembered.
1810863,2019-01-07 23:19:25 UTC,Are you asking for the Filter Selection dialog box to remember your last choices?  Or is there something more?
1810863,2019-01-08 11:33:35 UTC,"As long as the filter isn't applied automatically to all selections I'm happy. A hotkey would work, I think."
1810866,2019-01-08 00:01:02 UTC,See also: https://bugs.launchpad.net/hplip/+bug/1810866
1810866,2019-01-08 00:01:57 UTC,See also: https://h30434.www3.hp.com/t5/Printer-Software-and-Drivers/Let-s-Encrypt-support/td-p/6965130
1810867,2019-04-11 14:23:58 UTC,This issue was fixed in the openstack/kolla 5.0.5 release.
1810867,2019-04-11 09:37:53 UTC,This issue was fixed in the openstack/kolla 7.0.2 release.
1810867,2019-04-05 13:54:17 UTC,This issue was fixed in the openstack/kolla 8.0.0.0rc1 release candidate.
1810867,2019-02-20 12:55:19 UTC,This issue was fixed in the openstack/kolla 6.2.0 release.
1810867,2019-01-14 13:37:30 UTC,"Reviewed:  https://review.openstack.org/629440
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=2b9b7901a2bca5a5b9449f90211542b8c4ad1c51
Submitter: Zuul
Branch:    stable/rocky"
1810867,2019-01-10 03:07:25 UTC,"Reviewed:  https://review.openstack.org/629445
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0c5fa8208e21e41dfd4f20189aec5f00033d22d5
Submitter: Zuul
Branch:    stable/pike"
1810867,2019-01-09 22:04:18 UTC,"Change abandoned by Jason Anderson (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/629072"
1810867,2019-01-09 11:04:14 UTC,"Reviewed:  https://review.openstack.org/629380
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=ae883440255b02478bc3bd5cdcaf23a26869c5f1
Submitter: Zuul
Branch:    master"
1810867,2019-01-09 05:40:42 UTC,Fix for master is pushed at https://review.openstack.org/#/c/629380/
1810867,2019-01-08 15:16:34 UTC,"Note:
This site (http://docs.grafana.org/installation/rpm/) mentions to use the following repository:"
1810867,2019-01-10 09:26:58 UTC,"Reviewed:  https://review.openstack.org/629442
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=d4464fa4d9c7e2ab7826bf7224cd7a15506acaf3
Submitter: Zuul
Branch:    stable/queens"
1810867,2019-01-07 23:59:58 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/629072"
1810869,2019-01-08 20:52:37 UTC,Thank you for reporting a bug in ufw. Can you attach a tarfile of your firewall configuration. Use this to create your tarfile:
1810869,2019-01-08 23:25:38 UTC,Here you go...
1810869,2019-03-07 22:37:21 UTC,Sorry for just getting to this now. Your /etc/default/ufw file has unicode quotes here:
1810874,2019-01-08 01:48:31 UTC,this comes from https://answers.launchpad.net/python-zvm-sdk/+question/676964
1810874,2019-01-08 01:49:14 UTC,"we need further investigate how to support prototype , it might need some code changes in cloud connector such as configuration and deploy code flow etc"
1810882,2019-01-09 05:10:53 UTC,"@stevenGao, these two places have been updated to ""可用的"". see if it works on your side."
1810882,2019-01-08 05:45:15 UTC,Translation bug should be fixed in https://translate.openstack.org/.
1810882,2019-01-08 07:25:13 UTC,"Hi Horace,"
1810882,2019-01-08 06:00:06 UTC,"@stevenGao, could you share the document link? I am searching around translate.openstack.org but not sure if I captured the right phrase. thanks."
1810882,2019-01-08 07:25:47 UTC,"Hi Akihiro,"
1810887,2019-01-08 05:41:29 UTC,"Review in progress for https://review.opencontrail.org/48537
Submitter: Parth Sarupria (<email address hidden>)"
1810887,2019-01-16 06:18:22 UTC,"Reviewed:  https://review.opencontrail.org/48537
Committed: http://github.com/Juniper/contrail-controller/commit/c3ef11e2a001ec663de71f67319c1c99b9f694bd
Submitter: Zuul (<email address hidden>)
Branch:    R4.1"
1810902,2019-08-11 10:11:35 UTC,"Further to comment #8, the upstream bug was closed ""VERIFIED FIXED""
on 2019-02-21 with an additional report of being fixed on Ubuntu."
1810902,2019-02-24 03:40:52 UTC,From upstream bug:
1810902,2019-02-05 04:03:15 UTC,This has been reported upstream:
1810902,2019-01-16 09:44:28 UTC,Does the bug occur if you disable the focus-follows-mouse policy?
1810902,2019-01-16 09:43:44 UTC,The use of i3 is likely relevant. I can't reproduce the problem with gnome shell.
1810902,2019-01-15 09:19:15 UTC,I've now reproduced on a freshly rebooted ubuntu instance.
1810902,2019-01-09 16:39:40 UTC,"I'm not seeing the behaviour you describe. In my tests, the URL will always open in the last activated firefox window (even if it's on a different workspace)."
1810902,2019-01-24 09:44:38 UTC,"With a bit of experimentation, I have the following hypothesis, which is consistent with observed behaviour:"
1810904,2019-02-11 12:44:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810907,2019-01-08 17:24:51 UTC,You have no font files installed in your personal font directory.
1810907,2020-08-09 10:07:56 UTC,"@jerrycasiano, I cannot confirm your reply."
1810908,2019-01-11 22:54:34 UTC,Fixed by: https://review.openstack.org/#/c/629111/
1810908,2019-03-07 10:32:33 UTC,This issue was fixed in the openstack/python-zunclient 3.3.0 release.
1810913,2021-01-05 07:11:52 UTC,also affects 20.04 as i tried once again after 2 years ...
1810913,2019-01-25 08:55:09 UTC,https://errors.ubuntu.com/bucket/?id=/usr/lib/xorg/Xorg%3A6%3Auxa_glyphs_to_dst%3Auxa_glyphs%3AdamageGlyphs%3AProcRenderCompositeGlyphs%3ADispatch
1810913,2019-01-08 09:38:16 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like the graphics driver has crashed:
1810913,2019-01-08 10:11:07 UTC,"this is all very confusing ... i hope this is the right link.
https://errors.ubuntu.com/oops/c098662c-132a-11e9-8e47-fa163e6cac46"
1810914,2019-01-08 09:33:41 UTC,And here is the scrennshot
1810914,2019-06-04 21:25:15 UTC,"I can confirm this behavior on linux as well.
Version: (5.1.0-869-geb1faebf1), debug build"
1810914,2019-06-06 02:45:01 UTC,"Fixed in revision 27a5ed1a9f0f22eef3fa4418c0056f6a6cc0228f
https://git.launchpad.net/kicad/patch/?id=27a5ed1a9f0f22eef3fa4418c0056f6a6cc0228f"
1810916,2020-06-09 02:23:57 UTC,Still affecting X-4.15 P8
1810919,2019-02-21 15:31:29 UTC,bug 1810918
1810920,2019-02-06 06:34:34 UTC,"btw, compiled 3.2.
it justs works."
1810920,2019-01-08 16:19:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810920,2019-02-05 05:37:25 UTC,"Sorry, rule _can_ be created, but passess all traffic on ubuntu 18.04..."
1810920,2019-02-05 05:33:55 UTC,"I have the same problem with download.
I can download using scripts from 3.1, but resulting rules does not work with 3.0, shipped with ubuntu.
Rule can't be created, but it passes all traffic, no matter which country it is from.
iptables -I INPUT  -m geoip ! --src-cc RU -j DROP
allows traffic from Japan...
although module built and running on Centos 7 works..."
1810922,2019-01-08 11:22:30 UTC,"Note: pausing the principal charm would probably be enough if LP#1810919, LP#1810918, and LP#1810926 were fixed. Pausing hacluster will however always be a little cleaner as it puts the node on standby in the cib, whereas pausing the principal charm masks haproxy and must rely on pacemaker noticing and acting upon that."
1810922,2019-11-18 22:36:43 UTC,This has been fixed here:
1810924,2019-01-24 08:52:34 UTC,"Thanks @egmont-gmail. For reference, here are some more details around this: https://cirw.in/blog/bracketed-paste"
1810924,2019-01-09 08:42:38 UTC,"FYI: bash can already treat pasted multiline text safely, see its enable-bracketed-paste mode."
1810926,2019-01-09 13:02:57 UTC,"Hi Hans,"
1810926,2019-01-09 13:34:21 UTC,"Ah good catch, the exit 0 was higher up.
Additionally, I had misread the haproxy_status function, the pid is actually looked up in the process table at line 99 (even if the comment is wrong and 3 should be returned, not 1)."
1810926,2019-07-10 16:58:26 UTC,"You are forcing the compatibility between sysv and systemd into a corner here. I understand that your idea is to provide a simple case to reproduce the bug, but let's step back for a second and look at this statement:"
1810926,2019-07-16 09:01:37 UTC,"Yeah I agree, service masking is a corner case and it's just making things more confusing.
I also got misled by the haproxy_status function, which doesn't actually seem to ever be called (although I still think some return codes are wrong)."
1810926,2019-07-17 20:59:36 UTC,"Thanks updating status to closed as per last comment.  This does sound like it may be more of a pacemaker issue than haproxy, particularly if it's still reproducible on a newer LTS."
1810931,2020-02-27 01:40:09 UTC,Andreas explained a workaround:
1810931,2020-02-25 23:14:40 UTC,"Perhaps of note, php-imagick had been merged via git ubuntu in the past (it has an upload tag), but subsequent uploads were not done through git ubuntu.  Could this be what's confusing the cherry-picking?"
1810931,2020-02-25 22:58:11 UTC,Found a similar failure with php-imagick:
1810931,2019-10-07 21:51:47 UTC,"Not sure how to reproduce this synthetically, at least at the moment, since the current package is caught up with debian.  Checking out 0a8d80deb8cfdb7 and doing the git ubuntu merge start command appears to no longer be sufficient."
1810934,2019-01-08 12:13:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/629161"
1810934,2019-05-23 16:56:48 UTC,"Reviewed:  https://review.opendev.org/629161
Committed: https://git.openstack.org/cgit/openstack/pbr/commit/?id=50356da8393abdb47cc6c64de4fa387d8499cbc4
Submitter: Zuul
Branch:    master"
1810943,2019-05-07 10:24:01 UTC,"Hi Zdenek,"
1810943,2019-05-07 10:26:20 UTC,"Hi Zdenek,"
1810943,2019-05-14 07:51:39 UTC,"Hi Umesh,"
1810946,2019-01-08 14:53:43 UTC,Merge proposal: https://code.launchpad.net/~info-martin-konrad/epics-base/+git/epics-base/+merge/361500
1810946,2019-01-08 14:55:15 UTC,This issue was discussed on Core Talk: https://epics.anl.gov/core-talk/2018/msg00678.php
1810949,2019-01-09 11:51:18 UTC,This hits the negative end of my personal relevance scale: a memory leak in a short running tool only used at build time.
1810949,2019-01-09 14:00:48 UTC,Fixing this issue came as a byproduct of rewriting catMacroReplacements() to fix https://bugs.launchpad.net/epics-base/+bug/1810946. The latter was actually preventing us from moving to 3.15.6.
1810949,2019-01-09 15:03:03 UTC,Sorry for the harsh tone.
1810949,2019-01-09 15:18:21 UTC,"On 1/9/19 7:03 AM, Ralph Lange wrote:

> Sorry for the harsh tone.
>
> I was surprised to see a bug report and a branch and a merge proposal
> for this issue, which is certainly nice to have been fixed but IMHO
> doesn't deserve that level of publicity.
"
1810949,2019-01-09 16:14:26 UTC,"On one hand I agree that this leak is benign and that there's not too much value in having a ticket for it. On the other hand, I would consider every leak a bug. And it wouldn't be the first time a leak led me to a piece of code that had other issues as well."
1810949,2019-01-09 17:10:19 UTC,"> Seriously ?!?
"
1810949,2019-01-09 17:20:52 UTC,"> Sorry about the noise...
"
1810949,2019-01-08 14:53:46 UTC,Merge proposal: https://code.launchpad.net/~info-martin-konrad/epics-base/+git/epics-base/+merge/361500
1810955,2019-01-08 16:50:17 UTC,"What are your requirements for ""adoption""? (I assume you want the machine to be in ""Deployed"" state and ready for redeployment; you can sort of ""adopt"" a machine today, but it would sit perilously in ""New"" state unless you ""Mark broken"" or similar.)"
1810955,2019-01-08 20:07:08 UTC,In particular can the adopted machine boot into commissioning or are you asking for a script from MAAS to add it without rebooting the machine? Would it be okay if the adopted machine did not capture the current storage and networking layout?
1810955,2019-01-09 14:35:27 UTC,I think being able to take an already deployed machine (not in MAAS). Being root on that machine should be able to use the MAAS CLI to add the machine to MAAS.
1810955,2019-09-20 11:41:36 UTC,"This is a good idea. It needs design, though, so we need to get it on the roadmap. We have it in our Ideas section already, so let's track it there instead."
1810959,2021-01-15 08:30:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810960,2019-02-07 16:42:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810961,2019-02-13 16:51:04 UTC,"coud you try to cherry pick that change and run the playbook with your LDAP config?
https://review.openstack.org/#/c/636630/"
1810961,2019-01-11 09:49:46 UTC,"Could you give us your overrides? (user_*.yml files, and maybe your openstack_user_config?)"
1810961,2019-01-11 10:10:16 UTC,Added the other config file as well
1810961,2019-01-14 13:14:26 UTC,"Hi All,"
1810961,2019-01-11 10:09:45 UTC,"Hi,"
1810971,2020-01-05 10:55:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1810976,2019-01-16 19:14:36 UTC,"I don't foresee being able to do this myself, as every time I try to re-learn packaging it is a very long nightmare with different requirements. However if someone else has the familiarity, I definitely welcome a PR :)"
1810976,2019-08-20 22:32:15 UTC,This would shortly after need a port to python3 (https://github.com/mrooney/wxbanker/issues/10).
1810976,2019-08-28 03:57:36 UTC,"Removing packages from eoan:
 wxbanker 1.0.0-0ubuntu1 in eoan
  wxbanker 1.0.0-0ubuntu1 in eoan amd64
  wxbanker 1.0.0-0ubuntu1 in eoan arm64
  wxbanker 1.0.0-0ubuntu1 in eoan armhf
  wxbanker 1.0.0-0ubuntu1 in eoan i386
  wxbanker 1.0.0-0ubuntu1 in eoan ppc64el
  wxbanker 1.0.0-0ubuntu1 in eoan s390x
Comment: Ubuntu-specific, unmaintained, depends on obsolete beautifulsoup; LP: #1810976
1 package successfully removed."
1810977,2020-05-11 14:35:16 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/726868"
1810977,2019-03-24 23:39:44 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1810977,2019-03-22 03:44:40 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1810977,2019-01-25 12:58:35 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/633197"
1810977,2019-01-18 09:00:43 UTC,"Reviewed:  https://review.openstack.org/629281
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b24ad3780bc872d1a17907909cd6bcbea7e804b3
Submitter: Zuul
Branch:    master"
1810977,2019-01-08 18:24:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/629281"
1810977,2019-01-08 17:12:36 UTC,"triaged as medium as while this will affect all deployment with ram_allocation_ratio >1.0
that use numa affined guests without hugepages, the propotion of clouds that it affect is
expected to be low."
1810977,2019-03-04 14:04:59 UTC,"Reviewed:  https://review.openstack.org/633197
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=780ccfcbdea919b196c18372d1c66bc88b4fa48c
Submitter: Zuul
Branch:    stable/rocky"
1810979,2020-04-04 18:25:14 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/717506"
1810979,2020-04-07 12:26:48 UTC,"Reviewed:  https://review.opendev.org/717506
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=c59dc07e9031eaf127b4222a66efc06db29454d2
Submitter: Zuul
Branch:    stable/train"
1810979,2020-04-04 13:06:27 UTC,"Reviewed:  https://review.opendev.org/713221
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=dfddcce3a5bc98cbd177c984fd9d0a8bab51d40c
Submitter: Zuul
Branch:    master"
1810979,2019-11-06 01:14:41 UTC,This issue was fixed in the openstack/kolla 9.0.0.0rc1 release candidate.
1810979,2019-12-07 10:51:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/697831"
1810979,2019-07-22 14:11:37 UTC,"Reviewed:  https://review.opendev.org/629275
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=8c3cb6b4d29ac386297af5c1a6d67b1f031df3c8
Submitter: Zuul
Branch:    master"
1810979,2019-03-19 15:01:17 UTC,"Change abandoned by Jason Anderson (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/629270"
1810979,2020-03-16 12:59:55 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/713221"
1810980,2019-01-08 17:33:09 UTC,"@Lee
Would this kind of QA be possible for MAAS images?"
1810980,2019-01-08 19:58:10 UTC,CPC currently owns the image build and publishing process while MAAS owns the scripts which create the images. Before the holiday break I fixed LP:1787050(builders using inconsistent mirrors causing build failures) and tested the built image. I then pushed the changes which fixed the CPC job. Between when I pushed my changes and the CPC job ran CentOS updated cloud-init to a newer version than what Canonical provides in its yum repository[1].
1810980,2019-09-19 12:07:29 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1810980,2019-09-20 11:49:12 UTC,This isn't a bug in MAAS.
1810982,2019-09-20 12:44:14 UTC,We learned that the way some of the live build scripts did pre-seeding by implementing the entire logic in shell. Unfortunately the semantics and details of seeding evolved and are more complex than those scripts implemented.
1810982,2019-11-20 04:17:52 UTC,[Expired for snapd because there has been no activity for 60 days.]
1810983,2019-04-04 14:19:16 UTC,This issue was fixed in the openstack/keystone 14.1.0 release.
1810983,2019-03-06 01:19:36 UTC,"Change abandoned by guang-yee (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/636222
Reason: Not needed."
1810983,2019-01-08 18:08:37 UTC,"On master, this is a duplicate bug [0], which has already been fixed [1]."
1810983,2019-01-29 10:18:31 UTC,"Reviewed:  https://review.openstack.org/629692
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a2e307ed4d526e21cddf7551f160b587b89360e4
Submitter: Zuul
Branch:    stable/rocky"
1810983,2019-01-10 00:23:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/629692"
1810983,2019-01-09 22:10:31 UTC,"After further investigation, turns out my initial analysis was incorrect. Looks like we are no longer be able to specify something like this for the credential match anymore."
1810983,2019-02-11 21:08:05 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/636222"
1810985,2019-01-29 10:02:16 UTC,"It is normal to not get all the metrics corresponding to that resource instantly.
I believe it takes time for the resource to collect the valid metrics corresponding to it.
I suggest you to run the ""resource show"" command again and check."
1810988,2020-03-19 15:44:44 UTC,Additional comments http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-03-19-15.00.log.html
1810992,2019-03-07 01:52:47 UTC,The package ca-certificates_20170717~16.04.1_all.deb includes the expired certificate.
1810993,2019-07-08 21:19:01 UTC,"Fixed in revision 183687c69e780a89cc926303f16626de1f0b2984
https://git.launchpad.net/kicad/patch/?id=183687c69e780a89cc926303f16626de1f0b2984"
1810993,2019-06-28 09:40:05 UTC,See also https://bugs.launchpad.net/kicad/+bug/1832476.
1810993,2019-01-17 00:32:54 UTC,"And this also happens with all windows, not just the one that appears during refill."
1810993,2019-01-15 18:35:53 UTC,The good news is the commit b0da1e19 has fixed that issue on Windows.
1810993,2019-01-15 18:09:56 UTC,This is annoying but not a show-stopper
1810993,2019-01-09 00:24:25 UTC,"Hmm... That's odd.  Well, something deeper then."
1810993,2019-01-09 00:12:50 UTC,Tried the fix but the issue is still there
1810993,2019-01-08 20:39:47 UTC,"Fixed in revision b0da1e19eeb5414c8dff9a6ac8588361b78119ae
https://git.launchpad.net/kicad/patch/?id=b0da1e19eeb5414c8dff9a6ac8588361b78119ae"
1810993,2019-01-17 00:31:51 UTC,"It is still reproducible.
What is interesting is if you restart PCBnew, keep the cursor in the bounds of refill window, press B and do not move the cursor, the hotkeys will work.
But if you refill with cursor outside of the refill window bounds, it breaks."
1810998,2019-01-22 17:41:45 UTC,The reporter verified the Bionic kernel successfully as well.
1810998,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1810998,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1810998,2019-01-21 16:25:07 UTC,"Verification done on Bionic (no errors seen on dmesg).
Still waiting on verification by the reporter (different hardware), but this verification shows no regression in dmesg."
1810998,2019-01-11 12:17:42 UTC,Patch v2 series posted to the kernel-team mailing list:
1810998,2019-01-15 10:37:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1810998,2019-01-08 21:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1810998,2019-01-17 14:39:17 UTC,"Verification done on Cosmic (no errors seen on dmesg).
Waiting for verification on Bionic by the reporter."
1810998,2019-01-10 03:25:37 UTC,Patch series posted to kernel-team mailing list:
1810998,2019-01-15 10:32:50 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1811001,2019-01-08 21:10:01 UTC,"Review in progress for https://review.opencontrail.org/48564
Submitter: Arvind (<email address hidden>)"
1811001,2019-01-08 21:10:33 UTC,"Review in progress for https://review.opencontrail.org/48562
Submitter: Arvind (<email address hidden>)"
1811001,2019-02-04 21:01:23 UTC,"Reviewed:  https://review.opencontrail.org/48562
Committed: http://github.com/Juniper/contrail-controller/commit/afc3066d4e27fa2f0ed0c8a2f668f26a43b527a1
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1811005,2020-01-06 10:27:18 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.3.1 release.
1811005,2019-11-27 19:30:08 UTC,This issue was fixed in the openstack/tripleo-heat-templates 12.0.0 release.
1811005,2019-11-07 20:02:12 UTC,"Reviewed:  https://review.opendev.org/693187
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=fdc08ebba17f2c4859647bf358649bc9522c97b1
Submitter: Zuul
Branch:    stable/train"
1811005,2019-11-07 16:23:18 UTC,"Reviewed:  https://review.opendev.org/693193
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=669f60260440914d60d55453c07ba2b0751e8cb2
Submitter: Zuul
Branch:    stable/queens"
1811005,2019-12-12 10:14:52 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.2 release.
1811005,2019-11-06 14:58:35 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/693193"
1811005,2019-11-07 13:56:56 UTC,"Reviewed:  https://review.opendev.org/693191
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a7cafbc50007690681d3d4eebcb169fcd6e17ed2
Submitter: Zuul
Branch:    stable/rocky"
1811005,2019-11-05 00:02:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/692932"
1811005,2019-11-06 06:27:53 UTC,"Reviewed:  https://review.opendev.org/692932
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=068527d139b4b521782873fdd97ac46cb10b0885
Submitter: Zuul
Branch:    master"
1811005,2019-11-07 23:08:13 UTC,"Reviewed:  https://review.opendev.org/693188
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=f29003fa18d301803cc66734616af5e374bfe7fa
Submitter: Zuul
Branch:    stable/stein"
1811005,2019-11-06 14:46:30 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/693188"
1811005,2019-11-06 14:56:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/693191"
1811005,2019-11-06 14:44:30 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/693187"
1811008,2019-01-08 22:59:45 UTC,originally described in bug 1801110
1811008,2019-01-08 23:10:44 UTC,"StacktraceTop:
 dixGetPrivate (key=<optimized out>, privates=0x3000003d0) at ../../../../include/privates.h:122
 dixLookupPrivate (key=<optimized out>, privates=0x3000003d0) at ../../../../include/privates.h:166
 present_screen_priv (screen=0x300000000) at ../../../../present/present_priv.h:198
 present_wnmd_flip (damage=0x561e7959c1d0, sync_flip=1, pixmap=0x561e794b8b60, target_msc=10695, event_id=21050, crtc=0x561e7965fe30, window=0x561e7959c180) at ../../../../present/present_wnmd.c:357
 present_wnmd_execute (vblank=0x561e78f2b750, ust=4919664407, crtc_msc=10694) at ../../../../present/present_wnmd.c:465"
1811008,2019-01-09 01:49:42 UTC,I couldn't find any existing reports of this crash. Although bug 1811024 and bug 1811025 look related.
1811008,2019-07-22 04:21:26 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1811008,2019-05-29 12:32:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811013,2019-09-19 14:50:08 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1811018,2019-01-09 01:26:43 UTC,"I think this bug report is a duplicate.  If you happen to find the original bug report, please mark this one as a duplicate."
1811018,2019-01-09 21:18:17 UTC,"I looked and didn't find any existing issue, but it may help if I knew which part of my report you were referring to. I mentioned the following above:
- Moving the grid selection pulldown from a dialog to the toolbar in Eeschema and the symbol editor.
- No Imperial/Metric unit selector in the symbol editor.
- No Full Window Crosshair option in the symbol editor."
1811018,2019-01-14 07:53:11 UTC,I think the reason this was changed is to align eeschema to pcb_new in this regard.
1811018,2019-05-16 13:13:18 UTC,I just added the N/Shift+N hotkeys to eeschema.
1811018,2019-05-16 16:31:54 UTC,How about (to save toolbar space) putting it status bar? The zoom value could also be converted to a combobox.
1811019,2019-01-15 04:06:40 UTC,We'll put this under optimization of routed path.  In this case to minimize the number of bends
1811019,2019-04-24 12:24:24 UTC,In my layout I had to make the last move of the differential tracks one-by-one.
1811020,2019-02-20 14:53:56 UTC,"Hello,"
1811020,2019-03-25 15:17:05 UTC,Original bug was against very old Kolla code - we got rid of Debian 'jessie' in 2017.
1811020,2019-03-25 15:18:25 UTC,"Latest HEAD of stable/rocky builds ""centos-binary-grafana"" image just fine."
1811020,2019-03-25 15:20:16 UTC,https://git.openstack.org/cgit/openstack/kolla/commit/?h=stable/rocky&id=2b9b7901a2bca5a5b9449f90211542b8c4ad1c51
1811020,2019-01-09 15:28:42 UTC,Still broken on centos 7 even after i have removed/changed the lines in Dockerfile.j2  and the grafana.repo but still getting on install this
1811023,2020-02-10 02:25:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811023,2020-02-10 02:28:59 UTC,Also tracking in:
1811023,2020-02-13 10:09:25 UTC,See also bug 1792932
1811023,2020-02-13 10:15:23 UTC,"1792932 was fixed upstream in 1.20.2, so this is something different"
1811024,2019-01-09 14:34:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811024,2019-07-22 04:24:59 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1811025,2019-07-22 04:25:16 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1811025,2019-01-09 14:35:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811029,2019-01-09 02:10:46 UTC,"Oops, was meant for geoip-database-contrib. My bad."
1811029,2019-01-19 07:41:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811029,2019-02-05 18:13:50 UTC,Will it ever be addressed?
1811029,2019-04-07 12:24:26 UTC,"The Debian BTS has a related report [1] which suggests to me this issue should have been fixed way back in v1.11. But even if installing wasn't broken, with the legacy databases discontinued, it's not much use in the long term."
1811037,2019-02-21 15:46:32 UTC,We are going to support reusing existing partitions and raids and LVMs fairly soon; I don't know when we'll get to supporting ZFS properly. But we'll get to it eventually.
1811037,2019-12-26 20:55:35 UTC,"> I don't know when we'll get to supporting ZFS properly. But we'll get to it eventually.
"
1811044,2019-01-10 02:47:54 UTC,Here is a simple fix version: http://paste.openstack.org/show/741004/
1811044,2019-01-10 02:54:01 UTC,Another option is this: http://paste.openstack.org/show/741005/
1811044,2019-01-10 02:57:46 UTC,"I'm sure there are other options as well. To fix the bug we could do a combination. Start with the the simple fix that could be backported so people who _have_ already removed it and may not have updated versioning on these old containers, everything still works. and the second can be the actual deprecation, which we could include in the next swift release?"
1811047,2019-01-09 05:30:03 UTC,This change was made by a bot.
1811050,2019-03-14 10:43:35 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.3.0 release.
1811050,2019-02-15 15:13:54 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.3.0 release.
1811050,2019-01-16 22:54:31 UTC,"Reviewed:  https://review.openstack.org/630941
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=85826b52dae723536dfe1a62f2d80c4901c35641
Submitter: Zuul
Branch:    stable/pike"
1811050,2019-05-14 14:39:01 UTC,This issue was fixed in the openstack/tripleo-heat-templates 7.0.18 release.
1811050,2019-01-12 03:05:54 UTC,"Reviewed:  https://review.openstack.org/629750
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=bd2da9bf4e264d2629125ff2db37d0212039b973
Submitter: Zuul
Branch:    stable/queens"
1811050,2019-01-15 11:35:07 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/630941"
1811050,2019-01-10 03:07:41 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/629750"
1811050,2019-01-09 05:50:55 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/629383"
1811050,2019-01-09 17:28:26 UTC,"Reviewed:  https://review.openstack.org/629383
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=8bdef1e7b6ff7ea39be29575ff6529634340a0a2
Submitter: Zuul
Branch:    stable/rocky"
1811051,2019-08-21 07:06:51 UTC,"apt-get install lxc-templates
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  bridge-utils cgroup-lite dnsmasq-base iptables libcap2 libdbus-1-3 libidn11 libip4tc2 libip6tc2 libiptc0 liblxc-common liblxc1 libmnl0 libnetfilter-conntrack3 libnfnetlink0 libnftnl11 libpopt0
  libxtables12 lxc-utils multiarch-support rsync
Suggested packages:
  ifupdown kmod btrfs-tools lvm2 lxctl openssh-client openssh-server
Recommended packages:
  dns-root-data nftables dbus lxcfs uidmap busybox-static cloud-image-utils | cloud-utils debootstrap | cdebootstrap openssl uuid-runtime libpam-cgfs
The following NEW packages will be installed:
  bridge-utils cgroup-lite dnsmasq-base iptables libcap2 libdbus-1-3 libidn11 libip4tc2 libip6tc2 libiptc0 liblxc-common liblxc1 libmnl0 libnetfilter-conntrack3 libnfnetlink0 libnftnl11 libpopt0
  libxtables12 lxc-templates lxc-utils multiarch-support rsync
0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.
Need to get 2449 kB/2686 kB of archives.
After this operation, 10.5 MB of additional disk space will be used."
1811057,2019-08-27 10:48:31 UTC,"And I didn't see this on Xenial, so the bug can be closed."
1811057,2019-05-09 09:10:51 UTC,It turns out that the seccomp in Bionic does not support seccomp metadata retrieval.
1811057,2019-08-27 10:43:58 UTC,"Test reverted in Bionic:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=e1e61701203686f235ee14e5e53919e16848400d"
1811057,2019-05-09 07:55:29 UTC,This test passed on Disco / Cosmic
1811057,2019-02-04 17:08:58 UTC,We have seen similar failures on Xenial and Bionic in the Oracle OCP Cloud.  Across all instances flavor sizes
1811057,2019-01-22 06:09:15 UTC,Found on Power8 as well.
1811057,2019-01-09 08:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811057,2019-05-09 07:56:43 UTC,"With upstream tree, this test still failed on Bionic:
[ RUN      ] global.get_metadata
seccomp_bpf.c:3034:global.get_metadata:Expected sizeof(md) (16) == ret (18446744073709551615)
seccomp_bpf.c:3039:global.get_metadata:Expected md.flags (0) == SECCOMP_FILTER_FLAG_LOG (2)
seccomp_bpf.c:3044:global.get_metadata:Expected sizeof(md) (16) == ret (18446744073709551615)
global.get_metadata: Test failed at step #6
[     FAIL ] global.get_metadata"
1811058,2019-01-09 08:51:21 UTC,Offers do show up in model status. The problem seems limited to list-offers and consume.
1811058,2019-01-14 13:50:21 UTC,https://github.com/juju/juju/pull/9626
1811058,2019-01-09 08:06:06 UTC,"(Juju 2.6-beta1 , current edge channel snap, using local lxd controller and microk8s)"
1811060,2020-01-07 12:37:31 UTC,"Hi, I can't replicate this in master (1.1-dev (03ae7f7, 2020-01-04)), so if this happens again, please file a report against http://inkscape.org/report, this time with more information on OS and printer."
1811060,2020-01-07 13:32:35 UTC,This was another duplicate of https://bugs.launchpad.net/inkscape/+bug/490866
1811060,2020-01-07 13:35:13 UTC,"(P.S. Should actually have been fixed in 0.92.3 already, so if it really still occurs for Carles it might be a different issue after all, but I doubt it)."
1811063,2019-02-12 13:02:07 UTC,Thank you for the report!
1811063,2019-10-29 21:41:04 UTC,John are you still working on this?
1811065,2020-05-19 05:45:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811068,2019-01-14 07:50:18 UTC,If this is implemented that way then it would be nice to still be able to see the old value of the fields. (Like is done in the current edit library reference dialog with the separate column for the current values.)
1811072,2019-09-26 13:26:36 UTC,"assuming fixed in later versions, reopen if not"
1811073,2020-09-23 23:51:52 UTC,Duplicate Bug #1633115
1811073,2020-09-24 01:35:52 UTC,Fixed in lighttpd 1.4.51 released Oct 2018
1811074,2020-11-02 12:52:08 UTC,"Hi Ganesh, we no longer officially support Newton and as you mentioned above, the code changed in Pike to support Unisphere for VMAX RESTAPI.  Please let me know if I can close this bug.
Kind regards,
Helen"
1811076,2019-01-09 22:35:52 UTC,"The send_arp_for_ha and send_arp_for_ha_count options are for nova-network, not neutron.
So the sample nova configuration file is accurate."
1811076,2019-01-14 13:49:25 UTC,The send_arp_for_ha* options could be deprecated in nova like the other nova-network related config options if that would help avoid confusion.
1811083,2019-09-03 17:02:57 UTC,"I've updated the README to fix the location of the charm, but haven't pushed that change to the charmstore yet. Will do that shortly."
1811086,2019-10-16 10:24:46 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/688895"
1811086,2019-07-26 10:55:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672948"
1811086,2019-08-23 20:58:18 UTC,"Reviewed:  https://review.opendev.org/672948
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=288634ce0bf042bed614b3f764753d7b65a7170f
Submitter: Zuul
Branch:    master"
1811086,2019-10-16 22:01:22 UTC,"Reviewed:  https://review.opendev.org/688895
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=eccb5c13fec9d9efcccb821dbcf0f344cd515eec
Submitter: Zuul
Branch:    stable/stein"
1811086,2020-02-03 20:58:49 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705555"
1811086,2020-02-03 21:30:43 UTC,"Change abandoned by Shannon Mitchell (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/705555
Reason: Submitting a separate bug just for the public/private url fix."
1811087,2019-11-17 21:08:30 UTC,"Hm, I just figured out that I missed the last really useful comment because I did not get an e-mail about it."
1811087,2019-10-21 04:18:22 UTC,"Marking as ""won't fix"" as we can't really ship `fuidshift` as part of a strictly confined snap."
1811087,2019-10-16 06:22:24 UTC,"I added a task for lxd as this seems to be about the lxd snap itself, not so much about snapd the package manager."
1811087,2019-03-26 00:31:10 UTC,"This appears to be related to the package manager snapd, not the DNA analysis tool snap."
1811088,2020-06-16 20:57:13 UTC,"@phdocq
You can enable this option by this way :
(I'm not sure what the menu names are in ""English"")"
1811088,2020-07-14 18:37:33 UTC,"Adding the HPLIP plug-in allowed me to scan by doing
hp-scan -f ~/temp/output.png"
1811088,2020-07-14 18:22:22 UTC,"I have the HP MFP M31W, and I don't see either a Security or a Parameter options when I log into the printer's server."
1811088,2021-02-04 23:11:41 UTC,"@nico207
You made my day (#9). I had been struggling with scanning from MFP M479fdw for over an hour, reinstalling things over and over. And after all, it turned out to be a security settning. Thank you."
1811088,2020-02-28 17:11:26 UTC,"Hi Umesh. I have the exact same problem. Trying your solution, I do not see a Security Tab..."
1811088,2019-01-14 11:39:57 UTC,hp-testpage -i
1811088,2019-03-27 11:30:32 UTC,"Same here, on latest hplip: 3.19.3
Linux Mint 19.1 (kernel 4.18.0-15-generic)
printer: hpaio:/net/HP_LaserJet_MFP_M28-M31"
1811088,2019-01-12 11:28:19 UTC,Anything shown with 'journalctl'?
1811088,2019-04-15 09:39:52 UTC,"Hi All,"
1811098,2019-02-11 09:35:44 UTC,"The verification of the Stable Release Update for ceilometer has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1811098,2019-02-18 09:28:41 UTC,This bug was fixed in the package ceilometer - 1:10.0.1-0ubuntu0.18.04.2
1811098,2019-02-11 09:45:45 UTC,This bug was fixed in the package ceilometer - 1:11.0.1-0ubuntu2
1811098,2019-02-11 16:04:15 UTC,"Hello Edward, or anyone else affected,"
1811098,2019-02-15 02:07:14 UTC,This flaw has been assigned as CVE-2019-3830 https://access.redhat.com/security/cve/cve-2019-3830
1811098,2019-02-25 14:52:58 UTC,The verification of the Stable Release Update for ceilometer has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1811098,2019-02-06 09:34:31 UTC,bionic-proposed verified using [Test Case].
1811098,2019-02-26 12:38:44 UTC,queens-proposed verified using [Test Case].
1811098,2019-02-26 12:46:42 UTC,The verification of the Stable Release Update for ceilometer has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1811098,2019-02-26 12:46:44 UTC,"This bug was fixed in the package ceilometer - 1:10.0.1-0ubuntu0.18.04.2~cloud0
---------------"
1811098,2019-03-21 10:20:07 UTC,This issue was fixed in the openstack/ceilometer 12.0.0.0rc1 release candidate.
1811098,2020-02-27 12:49:16 UTC,This issue was fixed in the openstack/ceilometer 11.1.0 release.
1811098,2019-02-06 23:29:56 UTC,"A CVE can be requested by anyone for any defect. The OpenStack VMT doesn't generally request CVEs for projects it doesn't oversee, but we have a brief overview of what we'd generally recommend putting in MITRE's CVE Request form documented at https://security.openstack.org/vmt-process.html#send-cve-request if you're interested in following a similar process. Note that for an already-public report like this one, there are fewer bits to worry about (the process documentation attempts to call out the difference between what you'd do for still private embargoed reports vs already public reports)."
1811098,2019-02-25 14:52:59 UTC,"This bug was fixed in the package ceilometer - 1:11.0.1-0ubuntu2~cloud0
---------------"
1811098,2019-02-06 22:56:16 UTC,I agree with VMT's rating of class A. Will a CVE be requested for this?
1811098,2019-01-11 18:11:27 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/630364"
1811098,2019-01-16 19:14:45 UTC,Note there is a public fix proposed for this issue.
1811098,2019-02-05 16:14:11 UTC,cosmic-proposed verified using [Test Case].
1811098,2019-02-04 09:50:52 UTC,"Hello Edward, or anyone else affected,"
1811098,2019-01-31 23:18:33 UTC,"Hello Edward, or anyone else affected,"
1811098,2019-01-31 23:17:23 UTC,"Hello Edward, or anyone else affected,"
1811098,2019-01-28 23:31:48 UTC,This bug was fixed in the package ceilometer - 1:12.0.0~b1~git2018111615.da95ab99-0ubuntu2
1811098,2019-01-28 20:21:58 UTC,"This has been sponsored and uploaded to disco, cosmic and bionic and is awaiting SRU team review in the cosmic and bionic unapproved queues."
1811098,2019-01-16 19:42:24 UTC,"While reports of suspected vulnerabilities for ceilometer aren't officially overseen by the OpenStack vulnerability management team, we're happy to provide guidance in such matters. I've subscribed the Ceilometer Core security reviewers to the report, to improve visibility among them while it's set as private."
1811098,2019-02-06 15:20:15 UTC,rocky-proposed verified using [Test Case].
1811098,2019-01-12 00:22:16 UTC,"The attachment ""lp1811098-stein.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1811098,2019-01-11 18:13:03 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/630366"
1811098,2019-01-10 16:18:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/629891"
1811101,2019-08-01 19:58:44 UTC,I moved this to storyboard:
1811101,2019-04-11 23:11:31 UTC,"Looks like you were on a py35 host, I'm having a hard time reproducing this on a py27 host, but this would likely be the issue - these keys are not sorted and coming from a dict:"
1811103,2019-01-11 09:52:30 UTC,"you are right, 1.3 doesn't have the info (we found the info is needed but didn't backport)
@Bill, can you help to backport the doc patch to 1.3 branch"
1811103,2019-01-11 09:34:20 UTC,"For the 1st install I used 1.3 documentation. In that it is not mentioned, now it is mentioned. We will install it and see what happens.
Thanks"
1811103,2019-01-11 03:39:25 UTC,"Just as Huang Rui said and we also mentioned in the Pre-requirement of docs(https://cloudlib4zvm.readthedocs.io/en/latest/quickstart.html) that VM66120 is required.
Apply it and if there still a problem pls tell us, thanks."
1811103,2019-01-10 10:20:16 UTC,Does your z/VM with APAR VM66120 applied?
1811103,2019-01-10 01:57:39 UTC,"Bill, can you take a look?"
1811103,2019-01-10 12:18:34 UTC,"I think you hit the nail, we missed this one, we thought it was in 640 already. We will now apply FIX 1802 for z/VM 6.4."
1811107,2019-05-15 15:59:12 UTC,"I cant't seem to replicate the issue, although I have set up RBAC/Candid with Ubuntu SSO. Is this still happening for you, Bjorn?"
1811107,2019-05-16 12:45:48 UTC,"I haven't tried it lately, but I could give it a try to reproduce it again next week. Note that it didn't happen all the time."
1811107,2019-08-30 12:02:57 UTC,"FTR I could reproduce the issue without rbac enabled, just right after installing maas"
1811107,2019-08-30 14:07:55 UTC,"this can easily be reproduced in master by stoppingat the ""add ssh keys"" page at the first user journey. it doesn't always happen, but a few page reloads should show it."
1811107,2020-01-15 13:51:39 UTC,Fixed via https://github.com/canonical-web-and-design/maas-ui/pull/635
1811108,2019-01-30 19:37:27 UTC,"Reviewed:  https://review.openstack.org/633848
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=e2ca8f06de0d727cb9b196ad6b10d021071c9948
Submitter: Zuul
Branch:    master"
1811108,2019-02-08 15:48:27 UTC,"Reviewed:  https://review.openstack.org/635639
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=0a59a19ad20221b088843458e3b1cc8c3cdca6c3
Submitter: Zuul
Branch:    master"
1811108,2019-02-07 20:47:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/635639"
1811108,2019-02-01 13:24:46 UTC,Note that running the action again does clear the blocked message.
1811108,2019-02-01 13:23:49 UTC,@thedac i think this patch might needs fixing because I just upgraded my ceilometer after having run the action and it displays the blocked status:
1811108,2019-01-09 17:16:52 UTC,Triage:
1811108,2019-01-29 23:54:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633848"
1811108,2019-01-30 21:56:40 UTC,The workload status will now accurately inform the end user for the need to run the ceilometer-upgrade action.
1811109,2019-01-09 17:14:51 UTC,This is a duplicate of bug:  https://bugs.launchpad.net/maas/+bug/1809470
1811109,2019-01-18 10:55:43 UTC,"FWIW, a non-admin can't mount any filesystem, it can only unmount them. This is a UI issue only, it works using the API."
1811109,2019-01-10 10:20:39 UTC,"I've change the summary to make it clear that this is about the user is able to turn the machine unusable, and the only way of fixing it is to release and reacquire the machine. So it's not a duplicate of 1809470."
1811114,2019-03-16 23:25:11 UTC,Fix committed in rev 1356
1811114,2019-01-15 17:02:42 UTC,NOTE:  Should use https://github.com/OneDrive/onedrive-sdk-python since it's an MS supported SDK.
1811114,2019-01-15 16:23:44 UTC,@rtfm_07 -- You marked that as no longer affecting Ubuntu.  Has it already been fixed there?
1811114,2019-01-15 17:30:03 UTC,"@Kenneth Loafman,"
1811114,2019-01-13 19:53:49 UTC,"I can confirm this with duplicity 0.7.18.2. Logs indicate last successful run was 1/8/2019.
Please let me know how I can help solving this issue."
1811114,2019-01-12 15:18:30 UTC,"I have the same problem here, when I try to backup on onedrive. The last successful run was on 1/8/2019 since then I get the same error: ""HTTPError: 410 Client Error: Gone for url: https://apis.live.net/v5.0/me/skydrive/files"""
1811114,2019-01-15 14:31:59 UTC,"Hi ,
the problem is microsoft has changed the api.
please see the link."
1811132,2019-02-05 18:35:04 UTC,related to https://bugs.launchpad.net/evergreen/+bug/1669445
1811132,2019-03-08 22:30:42 UTC,Working branch user/jeffdavis/lp1811132-debit-payment-type has an untested first stab at adding a Debit Card payment type:
1811132,2020-02-20 15:51:39 UTC,"I have tested this code and consent to signing off on it with my name, rfrasur, and my email address, <email address hidden>."
1811132,2020-02-26 21:25:53 UTC,Works for me too.  Pushed to master.  Thanks Jeff and Ruth!
1811135,2019-01-09 19:54:18 UTC,"it's hard to clarify ones memories of such a mostly 'unreal' experience like the everyday interaction with a computer. Why unreal? This is, because what happens can't be touched nor heard, just be seen. Moreover I never talk to others about that and the mentioned procedures are not part of my active vocabulary. I suppose a developer has more of a fluently used practice in this field. So be kind and patient with me, please."
1811139,2019-07-17 06:39:06 UTC,"Hi guys,"
1811139,2019-07-16 17:54:09 UTC,"Override component to main
kronosnet 1.8-2 in eoan: universe/misc -> main
libknet-dev 1.8-2 in eoan amd64: universe/libdevel/optional/100% -> main
libknet-dev 1.8-2 in eoan arm64: universe/libdevel/optional/100% -> main
libknet-dev 1.8-2 in eoan armhf: universe/libdevel/optional/100% -> main
libknet-dev 1.8-2 in eoan i386: universe/libdevel/optional/100% -> main
libknet-dev 1.8-2 in eoan ppc64el: universe/libdevel/optional/100% -> main
libknet-dev 1.8-2 in eoan s390x: universe/libdevel/optional/100% -> main
libknet-doc 1.8-2 in eoan amd64: universe/doc/optional/100% -> main
libknet-doc 1.8-2 in eoan arm64: universe/doc/optional/100% -> main
libknet-doc 1.8-2 in eoan armhf: universe/doc/optional/100% -> main
libknet-doc 1.8-2 in eoan i386: universe/doc/optional/100% -> main
libknet-doc 1.8-2 in eoan ppc64el: universe/doc/optional/100% -> main
libknet-doc 1.8-2 in eoan s390x: universe/doc/optional/100% -> main
libknet1 1.8-2 in eoan amd64: universe/libs/optional/100% -> main
libknet1 1.8-2 in eoan arm64: universe/libs/optional/100% -> main
libknet1 1.8-2 in eoan armhf: universe/libs/optional/100% -> main
libknet1 1.8-2 in eoan i386: universe/libs/optional/100% -> main
libknet1 1.8-2 in eoan ppc64el: universe/libs/optional/100% -> main
libknet1 1.8-2 in eoan s390x: universe/libs/optional/100% -> main
libnozzle-dev 1.8-2 in eoan amd64: universe/libdevel/optional/100% -> main
libnozzle-dev 1.8-2 in eoan arm64: universe/libdevel/optional/100% -> main
libnozzle-dev 1.8-2 in eoan armhf: universe/libdevel/optional/100% -> main
libnozzle-dev 1.8-2 in eoan i386: universe/libdevel/optional/100% -> main
libnozzle-dev 1.8-2 in eoan ppc64el: universe/libdevel/optional/100% -> main
libnozzle-dev 1.8-2 in eoan s390x: universe/libdevel/optional/100% -> main
libnozzle1 1.8-2 in eoan amd64: universe/libs/optional/100% -> main
libnozzle1 1.8-2 in eoan arm64: universe/libs/optional/100% -> main
libnozzle1 1.8-2 in eoan armhf: universe/libs/optional/100% -> main
libnozzle1 1.8-2 in eoan i386: universe/libs/optional/100% -> main
libnozzle1 1.8-2 in eoan ppc64el: universe/libs/optional/100% -> main
libnozzle1 1.8-2 in eoan s390x: universe/libs/optional/100% -> main
31 publications overridden."
1811139,2019-07-15 14:41:44 UTC,ubuntu-server is now subscribed
1811139,2019-07-15 13:10:14 UTC,"This is ""almost"" complete, I pinged powerj to subscribe the server Team to kronosnet as initially discussed in comment #2."
1811139,2019-07-17 19:51:34 UTC,"On Wed, Jul 17, 2019 at 06:39:06AM -0000, Fabio Massimo Di Nitto wrote:

> upstream maintainer here :)
"
1811139,2019-07-03 06:53:55 UTC,"I reviewed kronosnet 1.8-2 as checked into eoan.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1811139,2019-05-06 13:45:13 UTC,"[Duplication]
There is no equivalent functionality in main.
Some of its crypto functionality referred to be simlar to libnss3 but that is no duplication either as it implements it by using libnss3 just providing a different level of abstraction and integration into the other kronosnet features."
1811139,2019-05-06 13:06:02 UTC,Taking the review on this
1811139,2019-07-15 10:43:58 UTC,"Since the change that triggers the mismatch is already in the archive the correct state for now is actually ""Fix Committed"" - waiting for an AA to resolve the mismatch."
1811142,2019-01-14 07:20:42 UTC,The datasheet field in the lib file is a legacy field. The current behavior is that it is overwritten (if empty) by the one in the dcm file. (The dcm file allows different datasheets for different aliases.)
1811142,2019-05-06 17:20:29 UTC,"Rene pointed me to this because I just posted a proposal for a KICAD_DATASHEET_DIR environment variable to have a default location for datasheets.
https://forum.kicad.info/t/kicad-datasheet-dir-proposal/16845"
1811142,2019-05-06 17:37:05 UTC,"Got me thinking...
Now there is a ""Datasheet"" field.
An easy way to add priority is to sort all fields which start with ""Datasheet"" alfabetically for searching."
1811143,2019-01-09 21:56:08 UTC,It seems that even if Juju does not report the user as having 'add-model' rights (when they rightfully should) the user actually does.
1811147,2019-10-31 02:57:29 UTC,2.6.7 release never went out. This fix was instead released in 2.6.8 - re-targeting this report.
1811147,2019-09-25 22:42:41 UTC,To address @jsing's commentary above:
1811147,2019-09-25 22:40:13 UTC,"Release was actually in 2.6.5, but I don't want to open the milestone just to assign this bug."
1811147,2019-09-25 22:28:26 UTC,We've just run into this again on our 2.5.1 controller.
1811147,2019-05-06 03:07:09 UTC,"Related to this I think is backing off a failed worker rather than just
restarting every three seconds."
1811147,2019-05-06 02:10:04 UTC,"Here are two example messages from an outage this weekend where units ran out of disk, and their agent logs filled the controller's disks and broke the HA cluster:"
1811147,2019-05-05 22:36:47 UTC,Since reporting this bug we've run into this a few more times and have been forced to resize our Juju 2 controllers to 100G disk to avoid outages before we have time to react.
1811147,2019-05-06 04:47:39 UTC,There are multiple issues at hand here:
1811148,2019-07-08 20:18:19 UTC,"It has a lot to do with the zoom and grid settings.  In any case, I think it is now fixed."
1811148,2019-01-10 07:20:26 UTC,"Please, update your Kicad install.
Many issue are fixed since 1455."
1811148,2019-06-18 14:11:56 UTC,"Update to the last one.
Now, 5 hours later, full keyboard control is restored (up,down,left,right).
Weird.. I don't know what could have changed during these 5 hours."
1811148,2019-06-18 09:04:56 UTC,"Hey!
I'm experiencing similar weirdness.
With me, in eeschema, I can move the mouse pointer (and parts) both down and right the way I'm used to with arrow keys 'down' and 'right'. Trying to move the pointer (or parts) left or up doesn't work with the arrow keys 'left' and 'up'. Funnily enough, moving the pointer ""large steps"" having the CTRL-key pressed works all directions (up/down,left/right). Also in PCBNew, moving with arrow keys works as should.
Does anyone have a clue what's going on?"
1811148,2019-01-10 16:39:14 UTC,I'm seeing this corner case as well but only when zoomed way out.  The left and up arrow seem to work fine but the down and right arrows do not.
1811148,2019-01-10 15:53:20 UTC,"I Work much more better on Version: (6.0.0-rc1-dev-1512-gfe30460ae), release build. (r12127 build)
So this great. BUT, I play with it a bit and found another corner case that seem to not right:"
1811148,2019-01-10 05:48:23 UTC,Version 5.0.2_1 do not have this weird issue.
1811148,2019-01-10 05:44:37 UTC,"I check more on the Select Item mode. Bay using hotkey ""E"" to check if the invisible cross cursor is controllable by arrow key. And it did look like the cross cursor go out of the symbol so that ""E"" key did not open dialog at some point. Again, how all of this make sense, if cross cursor is invisible and can go out of view (event in the mode that make it visible) far far away with arrow keys!
Again, I use all default setting from original clean install."
1811148,2019-01-10 05:38:21 UTC,"To compare, 4.0.7 arrow key actually move the mouse pointer and cross cursor."
1811148,2019-01-09 22:41:44 UTC,Can't reproduce on Linux.  Can someone on windows see if they reproduce?
1811148,2019-01-09 21:57:30 UTC,It does not matter which Canvas. That behave the same way.
1811148,2019-01-09 21:52:50 UTC,I use default setting from installation. So it is Accerlrated mode. The first Select Item Mode right above the Net Highlight mode.
1811148,2019-01-09 21:39:18 UTC,Couple questions:
1811149,2019-01-12 16:52:58 UTC,I've written a small script to reproduce the issue and I got following results using VMs from Linode:
1811149,2019-12-05 06:49:44 UTC,As near as I can tell the fix for this was never backported from systemd v241 to bionic. I recently filed a related a bug report here:
1811150,2019-04-29 22:43:30 UTC,It's good that there'a bugreport on this. This is driving me absolutely nuts.
1811150,2019-01-15 16:22:41 UTC,"I confirm it!
I my case the Eeschema (in modern accelerated) page goes to right side.
I couldn't confirm at Pcbnew of Eeschema fallback mode."
1811150,2019-01-12 02:50:01 UTC,It any one and confirm this? I think I completed my description how to reproducing it.
1811150,2019-01-10 15:58:18 UTC,"Version: (6.0.0-rc1-dev-1512-gfe30460ae), release build
pcbnew do not have this issue.
eeschema still have this issue but avoidable if user know about it corner case which to avoid overly zoom out to it's limit."
1811150,2019-01-10 05:50:43 UTC,5.0.2_1 do not have this issue.
1811150,2019-01-10 02:56:43 UTC,"I think I found the better description for reproduce it:
Zoom out all the way, and keep zoom out - you should see the center shifted.
Then zoom in will no long at the right center."
1811150,2019-01-10 02:51:28 UTC,I think to reproduce it you need to do zoom in/out many many time and fast like crazy person...
1811150,2019-01-09 23:36:51 UTC,"Your KiCad version looks old, it may be the bug https://bugs.launchpad.net/kicad/+bug/1810403 which has been fixed."
1811150,2019-01-09 23:37:53 UTC,"Sorry, the subject was about both eeshcema and pcbnew, so it's different."
1811150,2019-01-09 22:44:16 UTC,Which setting do you have for Center and Warp cursor on zoom?  This is under Preferences->Common
1811150,2019-01-09 21:56:26 UTC,Well it does not matter what CANVAS it in.
1811150,2019-01-09 21:54:38 UTC,"Did my bug title imply both ""PCBNEW"" and ""EESCHEMA""?
All Accelerated (The default after installation)."
1811150,2019-01-09 21:40:16 UTC,Which application are you using?
1811150,2019-01-10 02:48:32 UTC,"I have ""Center and Warp cursor on zoom"" checked."
1811151,2019-01-10 01:33:16 UTC,General recommendation for apps that behave this way (open a connection per request) is to place pgbouncer between the client and PostgreSQL. This greatly improves performance under any sort of load.
1811151,2019-01-10 01:31:39 UTC,"If regular DB connections are being used, the default setting of superuser_reserved_connections=3 should avoid this."
1811152,2019-01-10 14:52:29 UTC,Thanks
1811152,2019-01-10 14:17:38 UTC,"I filed the issue upstream as well.
https://gitlab.freedesktop.org/dbus/dbus/issues/253"
1811152,2019-01-10 00:13:02 UTC,"I did not check upstream yet no, thanks for checking. I'll report it upsteam as well."
1811152,2019-01-09 22:07:04 UTC,Did you check if the issue is specific to Ubuntu? https://gitlab.freedesktop.org/dbus/dbus/blob/dbus-1.12/bus/system.conf.in doesn't seem to include it either upstream?
1811154,2019-01-11 03:36:01 UTC,The problem was because of no mechanism to create journal file inside the condition.
1811154,2019-01-11 04:11:25 UTC,"Hello Sreejith, creation of that file already present in line 112. Please check the whole file once again. We don't have to add anything there. Actually this script can be much better to cover all scenarios. But this fix will only address the regression and to work with Mimic, hence the flag."
1811154,2019-01-11 04:12:03 UTC,proposed fix https://review.openstack.org/#/c/629673/
1811154,2019-01-11 18:01:29 UTC,"Hello Kranthi,"
1811159,2019-01-09 22:50:47 UTC,"And... spoke too soon.  It happens under xrender as well.  Shorter freezes, frequency is the same."
1811159,2019-01-10 03:02:11 UTC,"It appears the nouveau kernel driver is crashing, which may well be the main problem here. And thanks for testing kernel 4.20 already."
1811159,2019-01-10 03:30:06 UTC,This change was made by a bot.
1811160,2019-03-20 21:55:10 UTC,Triaged / Wishlist
1811162,2019-01-09 23:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811166,2020-11-15 04:55:35 UTC,"Reviewed:  https://review.opendev.org/744901
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=531d337db5fec668437beba48f65134d44b255db
Submitter: Zuul
Branch:    master"
1811166,2020-09-25 15:39:00 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/744901
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1811166,2020-08-05 13:00:12 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/744901"
1811166,2019-09-19 10:12:50 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1811166,2019-07-27 02:12:03 UTC,"Reviewed:  https://review.opendev.org/625134
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=00b6460df2748cbf0bfa8fccdaad6a7356c15388
Submitter: Zuul
Branch:    master"
1811166,2019-07-10 15:35:22 UTC,"Reviewed:  https://review.opendev.org/634509
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=adc6a7087f0b7aa07730e25a9b946157bbf98c53
Submitter: Zuul
Branch:    master"
1811166,2019-01-11 00:24:24 UTC,Matt and I had a brief irc chat about this RFE. IWe will get to it soon. Thanks
1811166,2019-01-18 16:06:42 UTC,"This submission was discussed today by the drivers team. We agreed that it is not a RFE. It is a bug, since the proposed behavior was what the code was originally intended to do. Having said that, the current API behavior has been living in the wild for a long time. As a consequence, if we are going to change it to what is should have been, we need to make it discoverable. Thus the fix should include a shim API extension. An example of how this has to be implemented in neutron-lib and Neutron can be found here https://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/empty_string_filtering.py and here https://github.com/openstack/neutron/blob/master/neutron/extensions/empty_string_filtering.py."
1811166,2019-01-18 00:05:02 UTC,"Looking at the code (https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvr_db.py#L86) it seems that what the submitter proposes is the original intent. Since it has already been marked as RFE, let's discuss it in the drivers meeting just to be on the safe side"
1811166,2019-01-17 15:36:18 UTC,"Fix starts here:
https://review.openstack.org/#/c/625134/"
1811166,2019-01-10 13:39:13 UTC,"Have you spoken to anyone on the neutron drivers team regards this change?
IMHO it seems borderline RFE and appears to change the API behavior."
1811166,2019-01-19 00:01:51 UTC,"Thank you to the Neutron drivers team for the input.
I agree with the conclusion of writing a shim api extension."
1811169,2019-03-07 23:24:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811169,2019-01-15 09:46:20 UTC,Added fwupd for reference
1811169,2019-01-15 09:56:15 UTC,"Maybe a small detail which may have an impact:  the laptop has SecureBoot enabled by default.
During the installation, the Ubuntu installer made me go about setting a password."
1811169,2019-01-10 15:50:39 UTC,To me this sounds like it's probably Gnome Software not fwupd.
1811169,2019-01-15 09:45:43 UTC,Sorry for the delay in following up.
1811169,2019-01-10 14:57:51 UTC,"Thank you for your bug report. Sounds like there are some real problems there
- connecting to power should automatically close/dismiss the warning and let you install the update
- the UI interaction seems at minimal confusing, it shouldn't have applied firmware updates without communicating about it properly"
1811169,2019-01-10 08:47:26 UTC,"After a reboot, clicking on the Update buttons don't complain about connecting to the AC power."
1811169,2019-01-10 15:04:32 UTC,I've reported it upstream on https://gitlab.gnome.org/GNOME/gnome-software/issues/567
1811172,2019-01-22 10:29:36 UTC,"Hello, i've uploaded fix for that:"
1811172,2019-03-06 13:31:15 UTC,correct link is: https://code.launchpad.net/~degorenko/maas/+git/maas/+merge/362125
1811172,2019-07-26 18:58:48 UTC,I think this commit should address the build failures from the previous
1811181,2019-01-10 03:39:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/629755"
1811181,2019-05-14 07:48:09 UTC,"Reviewed:  https://review.opendev.org/629755
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f62349a92bd90e913d5d56273cc542469216bf65
Submitter: Zuul
Branch:    master"
1811181,2019-06-12 14:44:10 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1811182,2019-01-10 04:30:06 UTC,This change was made by a bot.
1811184,2019-02-08 18:49:43 UTC,"Reviewed:  https://review.openstack.org/633015
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0551f0a9ff7b787fcb3e1b686b83e25f99cad874
Submitter: Zuul
Branch:    stable/pike"
1811184,2019-02-06 21:59:04 UTC,This issue was fixed in the openstack/cinder 13.0.3 release.
1811184,2019-01-24 15:19:01 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/633015"
1811184,2019-01-24 00:15:37 UTC,"Reviewed:  https://review.openstack.org/629463
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=937af5be0e7c17b34860e25cc434a219d7143387
Submitter: Zuul
Branch:    stable/queens"
1811184,2019-01-22 15:41:56 UTC,"Reviewed:  https://review.openstack.org/631997
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=844b627c38bb810abd3ef0b464577191f193ad7d
Submitter: Zuul
Branch:    stable/rocky"
1811184,2019-01-20 21:36:22 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631997"
1811184,2019-01-18 08:11:51 UTC,"Reviewed:  https://review.openstack.org/629766
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=16b4346171d2027bb3c2630d5f28f6f002878870
Submitter: Zuul
Branch:    master"
1811184,2019-01-10 04:44:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/629766"
1811184,2019-03-21 17:21:36 UTC,This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.
1811201,2019-01-18 02:31:14 UTC,"As we are going to adopt graphics/{index}_auto_switch_card_{product_slug}, this could be a verification of job."
1811201,2019-01-10 07:39:35 UTC,Sounds more like a new test case request of plainbox-provider-checkbox:graphics. Triaged.
1811204,2019-01-10 07:48:53 UTC,https://ubuntuforums.org/showthread.php?t=2330707
1811205,2019-06-04 11:47:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811214,2016-04-14 12:53:03 UTC,"Currently, I use intel_drv with SNA. I have compositing enabled (opengl 3.1)."
1811217,2019-01-12 05:02:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811219,2020-07-09 07:32:33 UTC,Thanks for confirming the fix Daniel!
1811219,2020-07-08 07:30:17 UTC,Not today... I don't use a machine with a touchpad usually.
1811219,2020-07-08 07:19:23 UTC,"Daniel: any chance you can test this with the chromium snap from the beta channel, and confirm the fix?"
1811219,2020-07-08 03:24:08 UTC,"^^^
Fixed in Chromium 84, apparently."
1811219,2020-07-09 01:23:15 UTC,Verified fixed in chromium 84 (beta).
1811219,2019-01-10 10:10:49 UTC,"Surprisingly, it's Chromium that's broken. Not Xwayland..."
1811219,2019-01-10 09:33:55 UTC,"Looks like it was implemented, but seems to have either regressed since then or just never been as precise as it should have been:"
1811219,2020-05-07 03:07:04 UTC,Fix committed upstream:
1811222,2019-08-30 06:34:47 UTC,I've hit the same issue  but in MAAS 2.6.0 (7802-g59416a869-0ubuntu1~18.04.1) configured without MAAS HA. The uploaded logs are the same in my case.
1811222,2019-08-30 07:16:14 UTC,"MAAS interface list in the database, note duplicates:"
1811222,2019-09-10 13:02:59 UTC,"Blake, could you expand a bit on the fix you made? I see that you added an index, but what code paths were creating interface in parallel?"
1811222,2019-09-10 13:21:45 UTC,The code path is that 2 controller processes that could be a regiond process or a rackd process can start a registration at the same time. The validation check was done inside the code and not at the database level for the physical interface 1 mac address.
1811222,2019-09-10 15:46:13 UTC,"Sure, I get why we won't error out anymore."
1811222,2019-09-10 15:59:54 UTC,Storage of the interface information happens in 2 stages for registration.
1811223,2019-09-19 12:07:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1811226,2019-01-10 10:37:53 UTC,apport information
1811226,2019-01-10 10:37:55 UTC,apport information
1811226,2019-01-10 10:37:54 UTC,apport information
1811226,2019-01-10 10:37:53 UTC,apport information
1811226,2019-01-10 10:37:52 UTC,apport information
1811226,2019-01-10 10:37:56 UTC,apport information
1811226,2019-01-10 10:37:49 UTC,apport information
1811226,2019-01-10 10:37:48 UTC,apport information
1811226,2019-01-10 10:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811226,2019-01-10 10:37:51 UTC,apport information
1811228,2019-05-20 09:20:38 UTC,This bug was fixed in the package mdadm - 4.1~rc1-3~ubuntu18.04.2
1811228,2019-05-20 09:20:27 UTC,This bug was fixed in the package mdadm - 4.1~rc1-4ubuntu1.1
1811228,2019-05-16 10:23:31 UTC,"Hi,"
1811228,2019-05-13 10:18:28 UTC,"Thanks Mariusz!
Since this verification needs special HW which at least I currently have none of - do you see a chance to also do the verification for cosmic-proposed? Lacking that it can't be really released for Bionic as it would then become an upgrade-regression."
1811228,2019-05-13 09:41:01 UTC,"Hi,
the issue is fixed in bionic-proposed."
1811228,2019-05-09 14:49:59 UTC,"Hello Roman, or anyone else affected,"
1811228,2019-04-23 08:12:21 UTC,Thanks for checking the PPA Mariusz.
1811228,2019-04-19 10:35:21 UTC,"Hi,
The issue is fixed in PPA."
1811228,2019-04-10 14:44:13 UTC,Incomplete waiting for PAP verification
1811228,2019-04-10 14:43:49 UTC,"Hi,
I need your help in testing this.
I have created a PPA [1] with the fixes for this issue, but I lack a IMSM HW."
1811228,2019-04-08 05:04:54 UTC,"Hi,
It is fixed in 19.04 (mdadm there is 4.1).
Any chances to include the fix in 18.04 LTS?"
1811228,2019-02-20 12:53:49 UTC,Patch which fix this issue: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=9bd99a90e110bd39beaa539cb44a70ee3264a270
1811228,2019-05-20 09:20:44 UTC,"The verification of the Stable Release Update for mdadm has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1811228,2019-05-09 14:27:54 UTC,"Hello Roman, or anyone else affected,"
1811228,2019-01-30 14:35:02 UTC,"Hi,
Is there any update on this one?"
1811228,2019-01-10 10:46:22 UTC,This issue was already fixed in released mdadm-4.1. https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=20e8fe52e7190b3ffda127566852eac2eb7fa1f7
1811228,2019-01-10 11:15:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811230,2019-01-28 10:06:07 UTC,"Hello Timo, or anyone else affected,"
1811230,2019-03-05 12:37:51 UTC,"tested on cosmic VM, works fine"
1811230,2019-05-24 10:11:39 UTC,"will be handled as part of hwe stack update, see bug 1824111"
1811232,2019-01-14 12:15:06 UTC,"FWIW I can edit storage for a machine as admin with RBAC, not as operator.
I think the latter is expected."
1811232,2019-01-14 13:16:24 UTC,"Ok, it turns out you can only edit storage if you have admin on the global scope (so user.is_superuser is True)."
1811232,2019-01-18 10:22:21 UTC,Turns out that the API is broken as well.
1811235,2019-12-05 20:14:33 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/676022
Reason: I'm just going to drop this backportable workaround option. If some really needed this we could think about it as a stable-only change but this is a really latent bug that not many have cared much about fixing so not a high priority to backport and introduce the complexity that this brings. I'll drop this and focus on the master-only traits-based solution in https://review.opendev.org/#/c/695220/."
1811235,2019-06-20 14:40:29 UTC,"Also note that setting the instance to ERROR just to see the fault means that to reset the status on the instance, if you use the resetState API your only options are ACTIVE or ERROR. But if I'm resizing from a STOPPED server and we go to ERROR state just to see a fault, then resetting the instance to ACTIVE is a lie since the guest is really stopped - the power state sync task in the compute should eventually correct that, but it's still annoyingly wrong."
1811235,2019-06-20 16:44:36 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/666638"
1811235,2019-06-20 16:44:53 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/666639"
1811235,2019-06-20 18:48:31 UTC,"Reviewed:  https://review.opendev.org/633212
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=46cb2fdfe2df333d870aca8e6afc521172b8e061
Submitter: Zuul
Branch:    master"
1811235,2019-06-20 18:51:18 UTC,"Reviewed:  https://review.opendev.org/633227
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d1931ac0630415519f9c3d906caba9c83cc8162a
Submitter: Zuul
Branch:    master"
1811235,2019-06-28 19:17:00 UTC,"Reviewed:  https://review.opendev.org/666638
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cdaa80078491517af3143690d40d30a5b7591edf
Submitter: Zuul
Branch:    stable/stein"
1811235,2019-09-27 09:03:19 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1811235,2019-08-12 20:42:02 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1811235,2019-08-12 21:31:57 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/676022"
1811235,2019-06-20 14:37:20 UTC,"@melanie, I've replied to your questions from comment 16 in the code review:"
1811235,2019-11-20 15:30:46 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/695220"
1811235,2020-01-30 19:22:27 UTC,"Reviewed:  https://review.opendev.org/695220
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4921e822e73383af0c8da4c5e3acfaa021eafe68
Submitter: Zuul
Branch:    master"
1811235,2019-06-28 19:17:24 UTC,"Reviewed:  https://review.opendev.org/666639
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1a11d5c7f35c17cfafc6b8ba57da88995c35b595
Submitter: Zuul
Branch:    stable/stein"
1811235,2019-06-20 00:19:51 UTC,"At a high level, I agree it makes sense not to go into ERROR state if a cold migrate to self fails, but ERROR state + fault message is generally ""the way"" that nova communicates failure of an action upon an instance. The end user sees the ERROR state and looks at the fault message to discover that something was not successful."
1811235,2019-01-25 15:58:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633227"
1811235,2019-01-25 16:18:23 UTC,Per comment 2:
1811235,2019-01-11 03:16:46 UTC,"@David Li, which branch of nova with this issue?"
1811235,2019-01-14 10:35:05 UTC,"Dear Brin, I feel so sorry for replying too late.
I found this issue in private cloud, and also I found  Ocata version of nova (15.1.5 release) may have this issue after reading its code. The key codes in nova/compute/manager.py --> class ComputeManager --> prep_resize --> _error_out_instance_on_exception."
1811235,2019-01-24 14:26:45 UTC,To answer your question: Nova has a config option allow_resize_to_same_host that is False by default. If it is False the nova does not allow migrating or resize an instance to the host it is already on. So latest nova still supports migrating to the same host if configuration allows it.
1811235,2019-01-25 01:27:35 UTC,"@BalazsGibizer, thank you for you reply. I saw the config option allow_resize_to_same_host. However, that config makes no sense since I want to migrate to selfhost because exception.CannotMigrateToSameHost will be raised in the beginning of function resize.see [1]."
1811235,2019-01-25 01:52:55 UTC,"David, thanks for the code link."
1811235,2019-03-08 20:41:06 UTC,Bug 1819216 is related to this.
1811235,2019-01-25 02:03:39 UTC,"Actually, looking at the code further [1], the docstring says that the host_name variable will only be set when the user has specified a target host for a cold migration. So, a resize without a target host specified will be able to land on the same host if CONF.allow_resize_to_same_host = True. BUT, a resize with a target host specified will be rejected. Prior to that change, it was not possible to specify a target host during a resize, at all."
1811235,2019-01-25 13:22:39 UTC,Resize does not allow specifying a target host at all. Specifying a target host only applies (in that code) for cold migrate:
1811235,2019-01-25 13:31:54 UTC,"I don't see where UnableToMigrateToSelf would eventually set the instance to error status, either in the compute manager prep_resize flow or in conductor if it tried to reschedule to another host. The fault does come from the compute manager recording UnableToMigrateToSelf as a fault."
1811235,2019-01-25 13:37:44 UTC,Oh yes I see:
1811235,2019-01-25 13:41:42 UTC,"I'm going to mark this low severity because it should be rare to get into this scenario if you're doing a cold migrate. The scheduler should filter out the instance.host unless the allow_resize_to_same_host config option is True (which I guess it is in this case), but even then if you had more compute hosts in your deployment then we should be able to reschedule to another host (unless they are all full). And even if you do hit this, nothing changed with the underlying VM so you can reset the state using this API:"
1811235,2019-01-25 14:05:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/633212"
1811235,2019-01-25 02:20:34 UTC,"Dear melaniewitt, I just do cold-migrate with same target host specified in my command but resize."
1811236,2020-04-16 06:24:55 UTC,This should be addressed by later kernel and firmware releases. Please check whether the issue still happen on up-to-date system.
1811236,2019-01-10 12:30:08 UTC,This change was made by a bot.
1811236,2019-01-16 07:44:53 UTC,"It seems that the workaround mentioned above creates another problem. My keyboard is plugged into the docking station USB port. After some seemingly random while, the connection between the laptop and the keyboard is lost. I suspect it's due to the change in the ACPI settings, otherwise I can't imagine what could have brought it."
1811236,2020-06-16 04:17:17 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1811236,2019-01-11 12:07:26 UTC,"An update on the matter, I went through this awesome page [0] regarding debugging suspend/resume issues, and this particular instruction seems to have removed the unwanted resume problem in my case:"
1811244,2019-01-16 09:20:43 UTC,"As for the other outcome, when the guest hangs (instead of QEMU crashing), the guest CPUs that block forward progress are halted in an idle loop, have interrupts enabled and have a queued timer IRQ 248 and a pending software IPI IRQ 250. It appears another timer IRQ is currently being serviced (but the CPU is idling)."
1811245,2019-01-10 14:23:35 UTC,I am so tired. sorry
1811248,2019-01-16 14:03:57 UTC,This issue accelerating/cascading to the extent that that the lxc arch linux guest is now entirely dead
1811248,2019-01-11 09:47:09 UTC,Some further input from the lxc dev team:
1811248,2019-01-11 09:31:24 UTC,strace does not seem to be the tool to figure out the info you are asking for. Considering that the pid of the involved processes would be unknown at the time of starting strace. And executing the process(es) from the cli along with strace will not bear fruit for the case.
1811248,2019-01-11 03:29:57 UTC,"On Fri, Jan 11, 2019 at 02:36:30AM -0000, km wrote:

> profile=""lxc-container-default-cgns""
>
> profile lxc-container-default-cgns flags=(attach_disconnected,mediate_deleted) {
>   #include <abstractions/lxc/container-base>
>
>   # the container may never be allowed to mount devpts.  If it does, it
>   # will remount the host's devpts.  We could allow it to do it with
>   # the newinstance option (but, right now, we don't).
>   deny mount fstype=devpts,
>   mount fstype=cgroup -> /sys/fs/cgroup/**,
>   mount fstype=cgroup2 -> /sys/fs/cgroup/**,
> }
"
1811248,2019-01-11 02:36:30 UTC,"profile=""lxc-container-default-cgns"""
1811248,2019-01-11 01:58:55 UTC,Could you add to this bug which mount flags are being used by the mount(2) system call that's failed and which mount rules are in the profile? I couldn't find either information in the linked bugs.
1811248,2019-02-07 01:56:57 UTC,https://github.com/lxc/lxd/issues/5439#issuecomment-461257784
1811248,2019-02-07 20:50:34 UTC,Whilst 'lxc.apparmor.profile: unconfined' appears the only way to keep unprivileged lxc guests with systemd v240 alive it defeats the purpose of AppArmor.
1811248,2019-02-11 02:41:58 UTC,adding cross reference
1811248,2019-01-21 01:49:27 UTC,"Going further, for those who are running arch containers in proxmox who reach here after googling via getting a message similar to this:"
1811248,2019-04-19 14:34:40 UTC,After having upgraded the host to:
1811248,2019-07-17 03:32:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811250,2020-03-07 10:23:47 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1811260,2019-01-10 17:27:18 UTC,https://bugs.launchpad.net/horizon/+bug/1811261   << horizon bugs
1811260,2019-01-11 15:50:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630298"
1811260,2020-08-06 15:15:28 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/630298"
1811270,2019-01-10 18:43:41 UTC,Additionaly the sys.F90 does not match what we really need.
1811275,2019-01-10 20:23:00 UTC,"This is not a bug unless the symbol is not showing up in your schematic.  This had to be done in order to support the new library ID which cannot handle ':' and '/' characters in symbol names.  It's been this was since 5.0.0 was released.  Once the new schematic and symbol library file formats are implemented, this issue will be resolved."
1811275,2019-01-10 21:09:07 UTC,"Yes, I understand that '/' character is deprecated. I don't understand why it is impossible to search modified name (e.g. name with '/' replaced by '_') in library?"
1811275,2019-01-10 21:12:01 UTC,It's quite annoying to search whole schematics for all elements mapped to project_name-rescue lib and manually replace project_name-rescue to actual global lib name.
1811279,2019-01-10 20:24:00 UTC,Building probert from git tip (HEAD = 8b56d73068ec1f293d3db3b0b44966ede9ed1c94) works fine.
1811280,2019-01-30 00:15:13 UTC,"Hi Doug,"
1811280,2019-02-06 22:08:29 UTC,"The files are stored in my personal files (my mahara account).  The owner is me.  If I open them from files it works fine, if I open it from the gallery on my page it shows ""The requested content cannot be loaded"""
1811280,2019-02-24 21:45:18 UTC,"Hi Doug,"
1811280,2019-02-25 22:47:55 UTC,"Here you go
<!doctype html>
<!--[if IE 8 ]><html lang=""en"" class=""ie ie8""><![endif]-->
<!--[if IE 9 ]><html lang=""en"" class=""ie ie9""><![endif]-->
<!--[if (gt IE 9)|!(IE)]><!--><html lang=""en""><!--<![endif]-->
<head data-basehref=""https://mahara.fsd38.ab.ca/"">
<meta name=""generator"" content=""Mahara 19.04 (https://mahara.org)"" />
<meta http-equiv=""Content-type"" content=""text/html; charset=UTF-8"">
<meta http-equiv=""X-UA-Compatible"" content=""IE=edge"" />
<meta property=""og:title"" content=""Designing 3D Models - Mahara ePortfolio""
/>
<meta property=""og:description"" content=""Mahara is an open source
ePortfolio and social networking web application.
It provides users with tools to create and maintain a digital portfolio of
their learning and social networking features to allow users to interact
with each other."" />
<meta property=""og:image"" content=""
https://mahara.fsd38.ab.ca/theme/raw/images/site-logo-facebook.png"" />
<meta property=""og:image:width"" content=""1200"" />
<meta property=""og:image:height"" content=""630"" />
<meta name=""viewport"" id=""viewport"" content=""
width=device-width,minimum-scale=1.0,maximum-scale=10.0,initial-scale=1.0""
/>
<meta name=""author"" content=""Doug Stevens"">
<title>Designing 3D Models - Mahara ePortfolio</title>
<script>
var config = {
'theme': [],
'sesskey' : 'Ov2xNS67IunW8B9J',
'wwwroot': 'https://mahara.fsd38.ab.ca/',
'loggedin': 1,
'userid': 6439,
'mobile': 0,
'handheld_device': 0,
'cc_enabled': 0,
'mathjax': 1,
'select2_lang': '',
'maxuploadsize': '2097147904',
'maxuploadsizepretty': '2GB'
};
</script>
<script>var strings = {""confirmcopytitle"":""Confirm
copying"",""confirmcopydesc"":""Please choose which you would like to
copy:"",""View"":""Page"",""Collection"":""Collection"",""attachedimage"":""Attached
image"",""namedfieldempty"":""The required field \""%s\"" is
empty"",""processing"":""Processing"",""unknownerror"":""An unknown error occurred
(0x20f91a0)"",""loading"":""Loading ..."",""showtags"":""Show my
tags"",""couldnotgethelp"":""An error occurred trying to retrieve the help
page."",""password"":""Password"",""deleteitem"":""Delete"",""moveitemup"":""Move
up"",""moveitemdown"":""Move
down"",""username"":""Username"",""login"":""Login"",""sessiontimedout"":""Your session
has timed out. Please enter your login details to
continue."",""loginfailed"":""You have not provided the correct credentials to
log in. Please check your username and password are
correct."",""home"":""Home"",""youhavenottaggedanythingyet"":""You have not tagged
anything yet"",""wanttoleavewithoutsaving?"":""You have made changes - do you
want to leave the page without saving
them?"",""Help"":""Help"",""Close"":""Close"",""closehelp"":""Close
help"",""tabs"":""Tabs"",""toggletoolbarson"":""Toggle toolbars on. Show full list
of buttons"",""toggletoolbarsoff"":""Toggle toolbars off. Show basic
buttons"",""imagexofy"":""Image {x} of
{y}"",""remove"":""Remove"",""errorprocessingform"":""There was an error with
submitting this form. Please check the marked fields and try
again."",""element.calendar.opendatepicker"":""Open date
picker"",""rule.maxlength.maxlength"":""This field must be at most %d
characters long."",""rule.required.required"":""This field is required.""};
function plural(n) { return n != 1; }
</script>"
1811287,2019-01-11 04:33:36 UTC,https://github.com/juju/juju/pull/9622
1811293,2020-01-07 10:26:59 UTC,"Hi, this issue is being discussed in https://gitlab.com/inkscape/inkscape/issues/612. I added your repro as comment and closed this issue."
1811296,2020-03-30 20:55:04 UTC,"Not sure about older released, but it's actually broken again already— currently in Sid, the versions of gcc-arm-none-eabi and libstdc++-arm-none-eabi are both 15:8-2019-q3-1:"
1811296,2020-03-02 17:24:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811296,2020-03-13 12:30:59 UTC,Fixed in libstdc++-arm-none-eabi-newlib 15:8-2019-q3-1+12build1
1811296,2020-02-27 03:40:24 UTC,This was working correctly on Ubuntu Focal with gcc-arm-none-eabi (15:7-2018-q2-6) and libstdc++-arm-none-eabi-newlib (15:7-2018-q2-5+12).
1811300,2019-01-11 17:22:31 UTC,"Yes, that would be useful. Maybe surprising but actually intuitive."
1811300,2020-10-14 01:55:07 UTC,"for anyone interested:
take a look at how tracks are dragged from deck to deck for example, and how deck cloning works."
1811302,2019-01-11 01:19:09 UTC,Nevermind!  I see that using the named param works on py3
1811302,2019-01-11 01:20:07 UTC,"You can close this issue, or convert to a question if it might be helpful to someone else...
Thanks everyone for your work on this project!"
1811303,2019-08-04 07:32:58 UTC,"Hello Non,"
1811303,2019-08-04 09:01:41 UTC,"Indeed, this is an issue with Fitz, as mupdf-gl fails to render the text correctly. Looking at their code I see they don't handle encoding at all; I'll file a bug with Ghostscript. I believe this bug can be closed now."
1811325,2019-02-18 08:22:10 UTC,"@DucTruong, pls help me !!!"
1811325,2019-01-15 07:58:00 UTC,"Dear Truong,"
1811325,2019-01-14 17:13:31 UTC,That probably won't work.  Is there a reason why you need 2 lb policies to the same cluster?
1811325,2019-01-11 18:07:27 UTC,Are you attaching 2 lb policies to the same cluster?  what is the use case for that?
1811325,2019-01-12 04:28:41 UTC,OK.. I want attach 2 lb policies to the same cluster.
1811330,2019-08-09 05:10:50 UTC,"Sorry, but this happened many months ago and I do not have any of that
information any more. The flavour was in Nectar (australia) and I just used
the dashboard to create it."
1811330,2019-01-17 01:57:17 UTC,"Needs more information.
Nova version, flavor information, parameters when creating the instance, nova-api logs, etc."
1811330,2019-08-06 10:44:34 UTC,"Please provide more information regarding the flavor,nova version and the parameters used while launching an instance and the related nova logs."
1811335,2019-01-11 07:48:40 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-January/097797.html
1811335,2019-01-28 17:12:01 UTC,This bug was fixed in the package linux - 4.15.0-44.47
1811335,2019-01-11 07:34:38 UTC,"To avoid conflict, have to cherry pick one more commit
   17ac526824a8 pinctrl: cannonlake: Fix community ordering for H variant
   e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant"
1811335,2019-01-15 10:37:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1811335,2019-02-04 08:48:45 UTC,This bug was fixed in the package linux - 4.18.0-14.15
1811335,2019-01-15 10:34:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1811336,2019-03-14 16:05:28 UTC,"Hi Kay was just wondering when you say ""However the API call doesn't pass this parameter"" whom are you expecting the API to pass the parameter too?"
1811336,2019-03-18 11:02:37 UTC,"Sorry for the confusion, I meant, the ""create"" function, which doesn't pass this parameter to the ""share_api.create_snapshot"""
1811336,2019-05-02 21:40:23 UTC,We discussed this at the PTG and so far as we can tell there is not actually a use case for creating snapshots from shares that are not available and we should resolve this issue by removing the option from our api doc (and some internal but really effective places in our codebase - https://github.com/openstack/manila/blob/d877b61c5e37ff012341194b8349af6f38155e5d/manila/share/api.py#L1081). If you think there are legitmate use cases please let us know.
1811336,2019-10-29 15:34:53 UTC,"Hello, Kay, I am wondering if you have any input if this is a valid use case for you, thanks!"
1811336,2019-10-29 16:53:48 UTC,"Hi Jason. I don't remember the use case, probably I tried to play with the API and then realized that this option is not passed."
1811336,2020-04-23 04:17:21 UTC,[Expired for Manila because there has been no activity for 60 days.]
1811348,2019-01-11 12:22:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1811349,2019-01-11 10:19:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630128"
1811349,2019-08-29 01:16:05 UTC,getting close i update ps to fix typo to get it going
1811349,2019-09-06 02:03:10 UTC,let me know if you are going to update the parent commit. If not I can address the review
1811349,2020-06-03 12:46:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/733127"
1811349,2020-06-23 21:13:25 UTC,"Reviewed:  https://review.opendev.org/733127
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=58b0538670097c762880f384749ac007f7fd01c8
Submitter: Zuul
Branch:    master"
1811349,2020-12-17 12:53:55 UTC,This issue was fixed in the openstack/tempest 25.0.1 release.
1811350,2019-01-12 22:40:45 UTC,With Nvidia Prime does not open.
1811350,2019-01-11 14:10:23 UTC,It looks like something strange is going on with the preview column in the library. Is it okay if you hide that? Right click the header row of the library table to select which columns to show.
1811350,2019-06-17 15:04:51 UTC,Thank you for confirmation.
1811350,2019-06-17 08:31:48 UTC,It seems that with version 2.2.1 this error no longer occurs. It can be taken for granted as of version 2.2.1.
1811350,2019-06-10 02:01:54 UTC,"I currently can't reproduce this anymore, neither with mixxx 2.2.1 nor with mixxx 2.3 (from latest git master). As it seems like this bug only happend on kde/plasma, maybe it was a bug on their side?"
1811350,2019-04-02 11:16:15 UTC,"Just added some tracks on kde to a crate (kde is my main de, i'm using i3 only for djing ^^) and saw that there are some errors in the log which i don't have on i3:
```
$ mixxx
Warning [Main]: Icon theme ""ubuntu-mono-dark"" not found.
Warning [Main]: Icon theme ""gnome"" not found.
Warning [Main]: Configuration file is at version ""2.1.1"" instead of the current 2.2.0
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)
attempt to connect to server failed
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)
attempt to connect to server failed
ALSA lib pcm_oss.c:377:(_snd_pcm_oss_open) Unknown field port
ALSA lib pcm_oss.c:377:(_snd_pcm_oss_open) Unknown field port
ALSA lib pcm_usb_stream.c:486:(_snd_pcm_usb_stream_open) Invalid type for card
ALSA lib pcm_usb_stream.c:486:(_snd_pcm_usb_stream_open) Invalid type for card
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)
attempt to connect to server failed
Warning [Main]: WaveformRenderMark::setup - redefinition of ""cue_point""
Warning [Main]: WaveformRenderMark::setup - redefinition of ""cue_point""
Warning [Main]: WaveformRenderMark::setup - redefinition of ""cue_point""
Warning [Main]: WaveformRenderMark::setup - redefinition of ""cue_point""
Warning [BrowseThread]: TagLib - Cannot read audio properties from inaccessible/unreadable/invalid file: /home/kerle/2019-02-28_01h43m33s.wav
Warning [Main]: src/skin/legacyskinparser.cpp:1784 SKIN ERROR at skin:deck_row_loop_jump.xml:28 <WidgetGroup>: Could not parse widget MaximumSize: ""-1,-1""
Warning [Main]: src/skin/legacyskinparser.cpp:1784 SKIN ERROR at skin:deck_row_loop_jump.xml:65 <WidgetGroup>: Could not parse widget MaximumSize: ""-1,-1""
Warning [Main]: src/skin/legacyskinparser.cpp:1784 SKIN ERROR at skin:deck_row_loop_jump.xml:44 <WidgetGroup>: Could not parse widget MaximumSize: ""-1,-1""
Warning [Main]: src/skin/legacyskinparser.cpp:1784 SKIN ERROR at skin:deck_row_loop_jump.xml:65 <WidgetGroup>: Could not parse widget MaximumSize: ""-1,-1""
Warning [Main]: src/skin/legacyskinparser.cpp:1784 SKIN ERROR at skin:deck_row_loop_jump.xml:28 <WidgetGroup>: Could not parse widget MaximumSize: ""-1,-1""
Warning [Main]: src/skin/legacyskinparser.cpp:1784 SKIN ERROR at skin:deck_row_loop_jump.xml:65 <WidgetGroup>: Could not parse widget MaximumSize: ""-1,-1""
Warning [Main]: src/skin/legacyskinparser.cpp:1784 SKIN ERROR at skin:deck_row_loop_jump.xml:44 <WidgetGroup>: Could not parse widget MaximumSize: ""-1,-1""
Warning [Main]: src/skin/legacyskinparser.cpp:1784 SKIN ERROR at skin:deck_row_loop_jump.xml:65 <WidgetGroup>: Could not parse widget MaximumSize: ""-1,-1""
Warning [Main]: Output sound device clock ..."
1811350,2019-03-26 18:54:20 UTC,"I have the same problem with archlinux and kde plasma. Mixxx on i3 works without a problem. This only occures with the qt5 stuff, mixxx 2.1 (maybe 2.2) with qt4 worked without problems.
My system is a thinkpad t540p with an intel gpu. Using modesetting or intel drivers doesn't change a thing. Might be related to some kde/plasma stuff? Disabling composer also didn't help."
1811350,2019-01-12 22:38:18 UTC,One more
1811350,2019-06-17 08:36:08 UTC,I'm using
1811350,2019-01-12 22:37:23 UTC,One more
1811350,2019-01-12 22:36:44 UTC,One more
1811350,2019-01-12 22:36:15 UTC,I have tested with all wave types and still giving the same error. Attached screen captiras of the graphic configuration of the computer where I have installed Mixxx.
1811350,2019-01-11 14:43:36 UTC,What GPU and graphics driver do you use? Do you use X11 or Wayland? Can you reproduce this with different options for waveform renderer in Preferences -> Waveforms?
1811350,2019-01-11 14:33:07 UTC,I removed the preview from the library and the problem keeps playing.
1811350,2019-01-12 22:37:53 UTC,One more
1811352,2019-01-18 09:19:15 UTC,"Yes it should be the openstackclient, neutron client is deprecated.
It should be included within ""openstack floating ip create/set"" options"
1811352,2019-05-16 06:42:45 UTC,This issue was fixed in the openstack/openstacksdk 0.28.0 release.
1811352,2019-04-04 16:38:44 UTC,"Patches:
https://review.openstack.org/#/c/650062/
https://review.openstack.org/#/c/650063/"
1811352,2019-02-01 21:18:44 UTC,This RFE really should be filed in python-openstackclient and openstack/openstacksdk. I filed a story there: https://storyboard.openstack.org/#!/story/2004924. We will keep the RFE open in Neutron to track the activity in the clients
1811352,2019-02-01 13:47:47 UTC,"Yeah, this fits OSC and OpenStack SDK repositories."
1811352,2019-01-15 08:02:32 UTC,"I suppose we should change neutronclient to openstackclient, am I right? As I know neutronclient (the old component CLIs) were deprecated in Rocky as well."
1811352,2019-09-12 09:37:32 UTC,This issue was fixed in the openstack/python-openstackclient 4.0.0 release.
1811352,2019-01-14 13:13:22 UTC,"It's not clear to me if we should treat this as an ""RFE"" or a ""bug"".
Going to ask a driver team member."
1811352,2019-02-01 08:26:41 UTC,"If we are talking about OSC, we should be good to go to add such feature there. I don't see anything what could block this."
1811352,2019-12-20 14:16:34 UTC,"I think it would be great to add some documentation from the user pov to neutron, I only found the admin docs describing how to enable the extension: https://docs.openstack.org/neutron/rocky/admin/config-fip-port-forwardings.html"
1811353,2019-04-20 18:45:36 UTC,"Hi Andrey, thanks for your work on this!"
1811353,2019-04-20 18:46:13 UTC,Unsubscribing the sponsors team; please resubscribe once those questions are answered.
1811353,2019-03-09 22:32:35 UTC,Upstream commit at https://sourceforge.net/p/smbnetfs/git/ci/09f0c3f0c8eaee76e48f00458a779619b6f95cb7/
1811353,2019-01-11 20:34:48 UTC,"The patch in comment 1 fixed only fstat, but further tests show that stat can also return invalid nsec values.
New patch fixes both functions stats and fstat."
1811353,2021-02-03 21:05:22 UTC,Fixed in 0.6.3-1
1811353,2019-01-11 12:22:46 UTC,"The attachment ""lp1811353.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1811353,2019-01-11 10:12:39 UTC,"The bug is forwarded upstream, see
https://sourceforge.net/p/smbnetfs/bugs/46/"
1811353,2019-01-11 20:06:22 UTC,The patch in comment 1 does not fix problem. Another solution needed.
1811358,2019-01-11 13:53:59 UTC,This also happens when creating a machine from the API
1811358,2019-01-11 16:42:48 UTC,"It turns out the reason is that when start_commissioning is called, it sets the min_hwe_kernel unconditionally to the default one (which was empty in my case)."
1811358,2019-01-11 16:46:04 UTC,Also see https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/327404 for reasons behind the chnage
1811358,2019-01-11 17:28:57 UTC,Bjorn also pointed out that in the API documentation for commissioning there is no mention of setting the min_hwe_kernel.
1811358,2019-01-11 23:21:51 UTC,After discussing this in the SU I went through the code and some old reviews. We were mistaken that you can define the min_hwe_kernel during commissioning. You can only set it when creating a new machine or updating its settings. The min_hwe_kernel value is set to the value of default_min_hwe_kernel whenever commissioning is started. Before [1] min_hwe_kernel was only set if it wasn't set to something before. After [1] it was always set to the value of default_min_hwe_kernel regardless if the user had previously defined something. This means as of today if a user defines a min_hwe_kernel when adding a new machine it is always overwritten by the default_min_hwe_kernel even if that means no min_hwe_kernel will be set.
1811358,2019-01-11 23:24:34 UTC,@Andres I assigned this to you as what we do is a product decision. Feel free to assign it to me or back to Alberto once we come to a decision.
1811361,2019-04-13 15:15:29 UTC,"ok, the case is clear now."
1811361,2019-04-13 12:31:17 UTC,"Ok, made a test with 2 copies of the portable Chrome:
They do not report having a Window, hence focus() will not work as currently implemented."
1811361,2019-04-13 12:04:50 UTC,"Portable Chrome - is it from here?
https://portableapps.com/de/apps/internet/google_chrome_portable"
1811361,2019-04-13 11:01:35 UTC,any update on this?
1811361,2019-01-16 07:21:55 UTC,"ok, understood.
see changed bug description."
1811361,2019-04-13 11:57:47 UTC,"Uuuups, lost in space;-)"
1811361,2019-01-15 16:23:55 UTC,I tested your script and it worked perfectly fine.
1811361,2019-01-15 14:53:10 UTC,This is my test:
1811361,2019-01-15 13:15:48 UTC,1.1.4-SNAPSHOT-2019-01-13_11:36/Windows10.0/Java8(64)1.8.0_191-b12
1811361,2019-01-15 12:44:14 UTC,"Tested with the latest build (> #180):
everything works as expected."
1811361,2019-01-16 02:48:48 UTC,I found more evidence that the issue is related to Portable version of chrome. This is another test I runned:
1811364,2019-01-21 18:13:12 UTC,"Had the same issue.
As user Do Quyet (mr.quyetdx) suggested here: https://bugs.launchpad.net/plank/+bug/1811492
adding export XDG_SESSION_TYPE=x11` in ~/.xinitrc fixed it for me.
I'm using Arch with Kernel 4.20.3
plank 0.11.4.24-0a84Arch
xfce4 4.12.1"
1811364,2019-10-13 09:35:17 UTC,Same problem
1811368,2020-11-25 15:59:52 UTC,Drivers requests are upstream issues and as such should be redirected to the official wiki:
1811368,2020-10-01 21:43:30 UTC,My reader Elan fingerprint 04f3:305 not detected with Ubuntu 20.04.
1811368,2020-08-06 08:11:52 UTC,I've been working on reverse engineering these sensors and have a semi functional prototype at https://github.com/mincrmatt12/elan-spi-fingerprint and the mincrmatt12/elan-spi branch of https://github.com/mincrmatt12/libfprint.
1811368,2020-07-17 21:22:43 UTC,"I'm using Ubuntu 20.04 and I have Elan fingerprint reader 04f3:3057 that cannot work yet.
I hope you can solve the issue."
1811368,2020-06-13 14:30:36 UTC,I'm on Ubuntu focal
1811368,2019-02-17 10:41:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811368,2020-06-13 14:29:22 UTC,"Same here:
even lsusb doesn't show it"
1811372,2019-01-11 11:47:48 UTC,This bug is related to https://bugs.launchpad.net/osprofiler/+bug/1811373
1811372,2019-04-08 16:00:33 UTC,OSProfiler should be extended to support the same parameters as gnocchi: https://github.com/gnocchixyz/gnocchi/blob/master/gnocchi/common/redis.py
1811380,2019-01-11 12:32:33 UTC,"This doesn't affect any functionality, it's just a UI issue."
1811383,2020-05-07 14:40:43 UTC,"Change abandoned by Dan Prince (<email address hidden>) on branch: master
Review: https://review.opendev.org/647742"
1811383,2019-01-16 18:37:14 UTC,"Reviewed:  https://review.openstack.org/631215
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=704b6870ba339345dc1de5d698df38f5467e4dd4
Submitter: Zuul
Branch:    master"
1811383,2019-03-26 13:59:20 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/647742"
1811383,2019-01-16 13:07:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/631215"
1811383,2019-01-11 13:01:44 UTC,https://review.openstack.org/629546
1811383,2019-01-16 05:18:51 UTC,"Reviewed:  https://review.openstack.org/614639
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=fda5b5ab3cc4f2eb92330e05751730c6c6a11825
Submitter: Zuul
Branch:    master"
1811383,2019-01-11 14:18:09 UTC,"just to note that the surface area might be more than docker-puppet tooling, but paunch and pacemaker bundles that running podman CLI with multi-process as well"
1811383,2019-01-16 08:38:36 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/629546
Reason: We finally went with the retry option."
1811384,2019-01-14 12:43:02 UTC,https://review.openstack.org/#/c/630211/
1811384,2019-03-14 10:33:12 UTC,This issue was fixed in the openstack/paunch 4.3.0 release.
1811390,2019-01-16 21:50:22 UTC,It isn't trivial issue I think. To ensure something like that we should ask keystone if such tenant exists during processing every API call which would probably slow down our (already not fast) API.
1811390,2019-01-14 13:37:30 UTC,I have not tried with master.
1811390,2019-01-14 16:31:05 UTC,Confirmed on master
1811390,2019-01-14 13:11:38 UTC,Any idea if this happens on master as well?
1811394,2019-01-31 12:31:57 UTC,apport information
1811394,2019-03-15 23:37:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1811394,2019-02-21 07:21:33 UTC,It works. The script runs through without any errors.
1811394,2019-02-20 13:54:36 UTC,Looks like only 4.15 needs this patch.
1811394,2019-02-20 12:34:07 UTC,"It seems the issue was fixed in commit 0b8d9073539e217f79ec1bff65eb205ac796723d
Tested it with our kernel (for simplicity reasons) and the panic was gone."
1811394,2019-02-19 10:06:54 UTC,I will try to do that. I've narrowed down the versions for now (using mainline kernel). The bug appeared sometime between 4.13.16 and 4.14.0 and was fixed between 4.15.18 and 4.16.0.
1811394,2019-02-18 10:39:45 UTC,Would it be possible for you to run a kernel bisection?
1811394,2019-01-31 12:31:58 UTC,apport information
1811394,2019-01-31 12:31:56 UTC,apport information
1811394,2019-01-31 12:31:52 UTC,apport information
1811394,2019-01-31 12:31:53 UTC,apport information
1811394,2019-01-31 12:31:53 UTC,apport information
1811394,2019-03-18 10:37:26 UTC,"Tested it and it works, updated the tag."
1811394,2019-01-31 12:31:51 UTC,apport information
1811394,2019-01-31 12:31:49 UTC,apport information
1811394,2019-01-31 12:31:47 UTC,apport information
1811394,2019-01-11 14:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811394,2019-01-31 12:31:55 UTC,apport information
1811394,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1811395,2019-06-03 04:17:23 UTC,[Expired for tap-as-a-service because there has been no activity for 60 days.]
1811395,2019-04-03 11:07:30 UTC,"- your procedure has two ""step 2"". is it just a typo?"
1811396,2019-04-24 16:40:52 UTC,There was a discussion around this topic some time ago at the bug https://bugs.launchpad.net/juju/+bug/1746073
1811397,2019-05-14 14:33:21 UTC,"Lajos, the generic way of proposing a fix is not via attaching a file on LP, but creating a review on the Openstack site, as charms are part of the official Openstack review process.
Could you open a review there and link it here? Thanks"
1811402,2019-01-11 17:30:45 UTC,"According to your bug description, this it not a bug in light-locker."
1811402,2019-01-12 07:59:18 UTC,"If I switch from nvidia-340 to nouveau driver, the problem disappears."
1811402,2019-01-12 17:22:25 UTC,Maybe related to bug 1760068.
1811402,2019-01-13 06:05:14 UTC,I reported this by nvidia-bug-report.sh
1811402,2019-03-08 17:00:53 UTC,Does not work with 340.107-0ubuntu0.18.04.2 either. HW: Geforce 9400M.
1811402,2019-03-13 10:10:58 UTC,"My 18.04 upgrade was somewhat corrupted. I had to do some manual troubleshooting  first to make the upgrade complete. I do not know, if it is still complete, but this bug exists anyway."
1811403,2019-01-25 19:43:36 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1811403,2019-01-11 17:32:30 UTC,Does not seem to affect Debian. On a Debian 9 Stretch system:
1811408,2019-01-28 08:22:17 UTC,"4.18.0-14.15~18.04.1 - generic
Regression test CMPL, RTB."
1811408,2019-02-04 09:10:54 UTC,All tasks have been completed and the bug is being set to Fix Released
1811433,2021-01-14 12:49:46 UTC,https://review.opendev.org/c/openstack/charm-rabbitmq-server/+/766011
1811433,2020-12-03 16:53:15 UTC,My intention is to add new option `-e vhost queue` to the script that would allow user to specify which queues on which host should be ignored when checking queue limits. This will be configurable via charm config in the similar way that option `queue_thresholds` is specified now.
1811433,2019-03-29 16:19:56 UTC,"check_rabbitmq_queues.py will sum up counts of any queue that matches the glob, but it will only do so for queues that have not been been summed yet.
Basically, if you ask for something like '-c vhost myqueue x y -c * * w z', the w and z thresholds will only apply to !myqueue.
See https://github.com/openstack/charm-rabbitmq-server/blob/master/scripts/check_rabbitmq_queues.py#L33 : if one of your globs matches, the following ones won't be evaluated.
It is not exactly what you're asking, but it does allow you to factor out event.sample."
1811438,2019-01-12 00:22:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1811439,2019-03-04 20:01:42 UTC,"Tested the following BMC firmware build from IBM, and ipmipower was found to work."
1811439,2019-03-04 21:28:11 UTC,"------- Comment From <email address hidden> 2019-03-04 16:20 EDT-------
Hi Manjo - so the system is working, other than seeing that error?  You restarted the BMC after the update, then restarted the system using ipmipower, so it looks like it's largely working."
1811439,2019-03-04 20:10:53 UTC,"After firmware update I see the following ""High Error"" on the BMC webui."
1811439,2019-03-04 21:08:01 UTC,dmesg on the BMC has the following:
1811439,2019-03-04 21:19:23 UTC,"Booting into old BMC firmware (ibm-v2.1-438-g0030304-r12-0-g5ee4fb00) I dont see these errors in BMC's dmesg output. But, I am not able to power on the server anymore.. will post further findings and datapoints soon."
1811439,2019-03-04 21:44:01 UTC,Switching back to old BMC firmware ibm-v2.1 I get the following error on the webui
1811439,2019-02-12 22:09:32 UTC,"------- Comment From <email address hidden> 2019-02-12 17:00 EDT-------
Upstream patches/review:
https://gerrit.openbmc-project.xyz/#/q/topic:freeipmi_support+status:open"
1811439,2019-05-20 13:49:39 UTC,F/w upgrade will be performed during machine's processor upgrade which requires RMA. ETA to bug closure likely to be June 2019.
1811439,2019-07-22 14:13:54 UTC,"Witherspoon has now been upgraded to the latest BMC release, but this issue is still occurring. So, the assumption is that the fix did not make it into IBM's latest BMC f/w release."
1811439,2019-07-22 18:00:08 UTC,"------- Comment From <email address hidden> 2019-07-22 13:50 EDT-------
Could you please provide firmware level installed? cat /etc/os-release from ssh shell or firmware page in webui should show it."
1811439,2019-08-08 08:01:44 UTC,changed to Incomplete while waiting on (blocking) RT 120488
1811439,2019-08-12 10:59:45 UTC,"System was down (powered off - for whatever reason, I saw lot's of ""FQPSPAA0007G: A system checkstop occurred"" in the BMC log) and got now restarted (and partly resetup - now with different address: .132)."
1811439,2019-04-29 13:56:10 UTC,"Awaiting f/w GA release, ETA mid May 2019."
1811439,2019-02-06 22:03:21 UTC,"My take on this is that the authentication_status.null_user for the BMC's capabilities (in the response) is set to 0h and this is telling us that the BMC does not support a null username.  ipmipower seems to be actually handling this properly in the sense that since a null username is provided, i.e. no username, that it errors out since the BMC does not support this.  ipmitool just returns when the username is not set and does not raise an error (take a look at the function ipmi_intf_session_set_username in https://github.com/ipmitool/ipmitool/blob/master/src/plugins/ipmi_intf.c)."
1811439,2019-02-01 20:27:44 UTC,"@<email address hidden>,"
1811439,2019-02-06 20:38:37 UTC,"On the output above, I see a difference:"
1811439,2019-02-06 20:29:21 UTC,"To compare, I'm providing the debug output from ipmipower for:"
1811439,2019-02-06 20:15:02 UTC,"Hi all,"
1811439,2019-02-06 20:41:03 UTC,"Or, I actually wonder whether freeipmi-tools, when not passing the user parameter, it actually uses zeros to contact the BMC, and OpenBMC interprets that as a user being passed, hence fails authentication?"
1811439,2019-02-01 15:59:43 UTC,"------- Comment From <email address hidden> 2019-02-01 10:52 EDT-------
For security reasons, we recently moved OpenBMC to not support the nameless option anymore. So the -U parameter will always be required in latest firmware. Will this be ok for you or do your tools need -U to be optional? We could backport that change which accepts (and requires) -U."
1811439,2019-01-29 15:07:47 UTC,Also it might be worth noting that ipmipower with nameless user (null) works on bostons. It would be worth figuring out the difference in BMC firmware implementation betweeen bostons and witherspoons.
1811439,2019-01-28 21:13:28 UTC,Posting detailed output from ipmipower. Is there a way to add a named user just for IPMI commands? I could not find any on the BMC GUI and could not find a way to add using xyz/openbmc_project/user/ management either.
1811439,2019-01-28 21:08:20 UTC,"MAAS uses ipmipower, and ipmi commands using nameless user and password does not work."
1811439,2019-01-28 19:30:13 UTC,"IBM, This should be documented in the release notes, or in a readme."
1811439,2019-01-28 18:29:33 UTC,"Yes, I agree - I think it's the extra IP address and removing it should make it respond correctly."
1811439,2019-01-28 16:01:24 UTC,Installed  the latest firmware image.
1811439,2019-01-28 14:42:20 UTC,"Manoj will upload the firmware from ftp://testcase.software.ibm.com/fromibm/linux/
witherspoon_prod.pnor.squashfs.tar to the BMC and flash & retest."
1811442,2019-10-01 20:41:02 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Chris and Kyle!"
1811442,2019-07-23 21:34:48 UTC,"There was a small typo(VIEW_COPY_ALERTS instead of VIEW_COPY_ALERT), but otherwise it works! I've pushed a sign-off branch, fixing the typos here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1811442_assign_copy_alert_perms_signoff"
1811442,2019-05-20 19:55:10 UTC,Branch available at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/csharp/lp1811442_assign_copy_alert_perms
1811444,2019-01-11 17:28:00 UTC,"Also affects xenial, though mono-complete does not install the monodoc-http package as a dependency. I needed to manually install monodoc-http after mono-complete to test whether it failed."
1811444,2019-01-11 17:31:08 UTC,Also affects bionic. Unlike xenial mono-complete DOES pull monodoc-http by default.
1811444,2019-01-11 17:57:55 UTC,"Also affects disco. mono-complete DOES pull monodoc-http by default here, too."
1811449,2019-12-22 13:59:27 UTC,need fallback keyservers in script
1811453,2020-03-07 10:22:44 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1811458,2019-07-18 21:20:18 UTC,"Thanks for filing the bug.  Cloud-init does have support for DataSources to apply network-config on each boot, it's not currently enabled by default on OpenStack Datasources."
1811459,2020-04-04 15:44:00 UTC,Sorry I had not seen this until now! (my Launchpad notifications settings seemed to be off...):
1811459,2020-04-06 13:57:16 UTC,"Thanks for the clarification, indeed this was written in the code... Sigh... :)"
1811463,2019-01-11 19:29:02 UTC,"Hotkey Fn + F6 (touchpad on) does not work, all others work"
1811463,2019-01-11 19:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811464,2019-01-16 19:23:26 UTC,great! thanks!
1811464,2019-01-13 16:15:21 UTC,"I have now backported the fix to 4.1, and propagated it to trunk-psml."
1811464,2019-01-12 23:28:58 UTC,"Actually, 4.1 also exhibits the bug. I had assumed it was a 'trunk' issue and
started with that branch, instead of checking.
The problem is that the chain of if_then_else's acts on several logical variables that can
be true at the same time (e.g., spin%SO and spin%none)"
1811464,2019-01-12 22:51:25 UTC,"Ah, so something changed between 4.1 and trunk... I see..."
1811464,2019-01-12 22:37:12 UTC,"It is indeed a bug and it affects the trunk version also.
The fix is coming soon."
1811464,2019-01-11 21:39:12 UTC,Thanks for the bug-report!
1811465,2019-06-13 18:26:45 UTC,I couldn't find anything called Caliber in ubuntu.
1811466,2020-08-07 23:43:27 UTC,"Thanks, Michele and Rogan.  Pushed to master, rel_3_5, and rel_3_4."
1811466,2020-08-07 20:41:30 UTC,Works as advertised.  Signoff pushed to user/rogan/lp1811466_add_creator_editor
1811466,2019-10-28 19:27:38 UTC,"Elizabeth, Thanks for the screenshot. The wider display is a definite improvement. Having the column on the left took up too much screen real estate. We have some libraries that won't move cataloging to the web client because there was too much scrolling to see the item fields. Your screenshot doesn't show the holdings details, is it still above the item fields?
You also show additional stat cats. Does having additional ones change the layout of the item fields? I'm not sure if the fields are intended to be read horizontally (which makes more sense) or vertically (which seems jumbled).
I'm trying to figure out how easy the display would be to use/read if adding multiple items to a single library or to multiple branches.
Janeat"
1811466,2019-09-24 15:07:29 UTC,"Holly, there is another bug for more columns options in Holdings View: https://bugs.launchpad.net/evergreen/+bug/1761222"
1811466,2019-09-23 19:11:25 UTC,will we have the option to view creator in item details or in the columns drop down so when we are in the holdings view we can see the creator of each added holding?  Or is this another bug that I don't know about?
1811466,2019-09-23 18:04:09 UTC,"I am glad this bug has been fixed, but. Isn't there always a but. On the working copies tab the space to display the information is so small that to me it seems beside the point that we can see the creator, last edit Date, and last editor because there is so little room to display all the choices. I think it would be more helpful to have these displayed in a column format like in xul. There is a lot of wasted white space on the item record screen.
Thanks for thinking about this.
Janet"
1811466,2019-09-24 19:54:44 UTC,"Janet, we liked the old XUL display with this information in a vertical column, but this at least gives us a way to make the information visible.  And we think it's potentially more useful in the grid in Working Items when you're working with multiple items.  Depending on what you're doing, you might not need all of those data elements, but if they are all in the column picker users can pick and choose depending on what they need to see."
1811466,2019-08-27 13:25:02 UTC,"Completed grid showing added creator, editor, edit date"
1811466,2019-08-27 13:24:08 UTC,"Working grid showing added creator, editor, edit date"
1811466,2019-08-27 13:19:00 UTC,Working branch available at:
1811466,2019-08-27 18:07:18 UTC,"Works well for me, Michele!  Here's a sign-off branch: user/sandbergja/lp1811466_add_fields_to_holdings_editor_grids_signoff"
1811466,2019-08-20 15:50:20 UTC,"We would really like to see the all data elements from the Identification column in the Copy Editor in the XUL client be part of the display in both Edit and View screens: Creator, Creation Date, Active Date, Last Edit Date, Last Editor, in addition to being available in the column picker.  This is basic information -- we care as much about who created or edited an item as we do the bib, and we have a lot more items and a lot more staff adding and editing items than bibs.  I'm attaching a screenshot from XUL for reference."
1811466,2019-01-14 15:58:30 UTC,Also true in Evergree 3.1.8
1811468,2019-03-08 22:00:11 UTC,I do not agree this is not a bug ;-)
1811468,2019-03-08 22:17:24 UTC,"One note for whoever is interested in taking care of this.  The WAI-ARIA Authoring Practices have some simple guidance for show/hide widgets (which they call disclosures): https://www.w3.org/TR/wai-aria-practices-1.1/#disclosure.  Especially note the summary, keyboard interaction subsection, and WAI-ARIA Roles, States, and Properties subsection (most of which should be relatively easy to implement)."
1811477,2020-03-20 06:50:43 UTC,Closing because INVALID: Support request.
1811478,2020-03-24 09:54:40 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1811479,2019-01-30 22:03:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811479,2019-03-26 04:10:39 UTC,"Xubuntu 19.04 DAILY (live) QA-Test (20190325)
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)"
1811479,2019-03-26 05:09:00 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1811479,2019-06-08 00:13:09 UTC,OK It also happened on my 19.10 development branch
1811479,2019-06-23 13:08:56 UTC,Xubuntu 19.10 (daily) install from a very recent QA-Test install booted for a test of something related to a ask-ubuntu question.
1811482,2019-01-12 02:06:27 UTC,"budgie-desktop 10.4, Ubuntu Budgie 18.10, fully up to date."
1811485,2019-01-12 02:55:10 UTC,"See https://github.com/Bumblebee-Project/bbswitch/issues/182 for more details.
The only difference is that I have changed 2 discreate cards to 3 in this bug report, which have no affect to the situation."
1811490,2019-01-12 04:31:06 UTC,"""sudo hp-doctor"" command shows errors."
1811492,2019-01-18 07:10:17 UTC,Plank starts successfully if I add `export XDG_SESSION_TYPE=x11` in ~/.xinitrc.
1811496,2020-01-14 00:10:28 UTC,"I'm merging this fix together with fix for: LP: #1858374 in a new merge request, respecting credits, and link it here."
1811496,2020-02-06 12:54:38 UTC,This bug was fixed in the package ipxe - 1.0.0+git-20190109.133f4c4-0ubuntu3
1811496,2020-01-14 01:22:33 UTC,There is a MR already for this in salsa but it hasn't been looked yet. I have sent out a debdiff containing fixes for this bug AND LP: #1858374 altogether in:
1811496,2020-01-14 01:08:28 UTC,Current merge:
1811496,2020-01-06 19:44:10 UTC,Posted comments on:
1811496,2019-12-15 10:20:05 UTC,"Another issue was that 20_ipxe didn't call save_default_entry, to save the selected grub entry for subsequent reboots."
1811496,2019-12-15 09:36:49 UTC,"I don't know if it helps, but I uploaded it as a merge proposal too:"
1811496,2019-11-08 08:32:39 UTC,:-/
1811496,2019-11-07 16:00:24 UTC,"Passing by this bug after 180 days of no activity, no changes."
1811496,2019-04-23 16:16:24 UTC,"The bug is still valid in Ubuntu regardless of where the code comes from, subsequently I'm reopening the task and adding a bug watch for the debian bug."
1811496,2019-04-23 07:26:53 UTC,"I was thinking that the 20_ipxe code comes from Ubuntu, as grub-ipxe doesn't exist in Debian.
But on second look, it comes from the Debian's ipxe package.
So I've filed https://bugs.debian.org/927783 and I'm marking this issue as ""invalid"";
I believe that the fix will reach Ubuntu with some future import from Debian."
1811496,2019-11-07 16:33:29 UTC,Yeah it's ready for upload but no Debian or Ubuntu developer seems to have time to upload it. :)
1811496,2019-02-04 23:58:55 UTC,"On Mon, Feb 04, 2019 at 09:51:11PM -0000, Alkis Georgopoulos wrote:

> We talked a lot about secure boot, so let me clarify that the initial
> issue, that my included patch addresses, is unrelated to secure boot.
"
1811496,2019-01-14 14:12:15 UTC,"Sounds reasonable. Subscribing foundations, since it involves grub."
1811496,2019-01-16 18:58:18 UTC,"Attaching a 20_ipxe that does what I mentioned. I tried to keep the .diff minimal, by reusing the IPXEPATH variable:"
1811496,2019-04-20 19:03:51 UTC,"Unsubscribing the Ubuntu Sponsors Team, as there are no debdiffs to sponsor."
1811496,2019-01-20 10:53:22 UTC,"Note that this grub entry already shows up in UEFI and is not working at all (since it's just linux16).
So making it work under UEFI, even with secure boot disabled, is definitely an improvement."
1811496,2019-01-20 11:22:22 UTC,"On Sun, Jan 20, 2019 at 10:53:22AM -0000, Alkis Georgopoulos wrote:"
1811496,2019-01-20 10:15:07 UTC,"Andreas, /etc/grub.d/20_ipxe appears to be a file shipped by the grub-ipxe package built from ipxe source, which is maintained by the server team.  I think it's for you to decide if this is what you want, not foundations."
1811496,2019-02-04 20:46:44 UTC,"As discussed on IRC, we are not going to sign multiple bootloader implementations with the key because this would increase the attack surface of UEFI Secure Boot (which is already quite large, but signing multiple competing bootloader implementations would be an unforced error)."
1811496,2019-02-04 21:41:59 UTC,"> If there are features missing from grub, that should be addressed as a bug in grub.
"
1811496,2019-02-04 21:51:11 UTC,"We talked a lot about secure boot, so let me clarify that the initial issue, that my included patch addresses, is unrelated to secure boot."
1811496,2019-02-03 08:22:28 UTC,"> Steve Langasek (vorlon) wrote on 2019-01-20:
I would add the caveat that /boot/ipxe.efi will not be bootable on SecureBoot-enabled systems and this is not something that will be changed.
"
1811498,2019-01-12 08:46:52 UTC,how to solve it
1811498,2020-03-07 15:34:59 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1811504,2019-07-24 19:16:49 UTC,"Hi,
Good news, it works.
The automatic installation of the plugin did not work, I had to install it manually
Thanks for your help
Yannick"
1811504,2019-07-16 06:52:29 UTC,"Hi
we are working on this. and will update you this week."
1811504,2019-07-22 06:34:35 UTC,"Hi,
I've installed hplip 3.19.6 on my Debian Buster using experimental repositories. I've just purchased an M28a LaserJet.
With the new driver I'm able to scan just in text mode and 300dpi or 600dpi resolution (using Gnome simple scan tool). If I set the color scan mode (or picture mode), I get I/O error."
1811504,2019-07-18 07:53:31 UTC,"No change with the problem with me. Context Xubuntu 19.04, One minute before scan work between each page to scan."
1811504,2019-07-17 07:05:01 UTC,"It seems to work well.. tried with xscan, skanlite and skanimage and everything is fine.
I just get an I/O error sometimes, probably because I tried to scan to quickly after another scan.
I will continue to test and give feedback :)"
1811504,2019-07-17 06:05:10 UTC,"Hi,"
1811504,2019-07-15 20:23:34 UTC,"Hi,
no news since May....does anyone know if hp is working on this bug  or if definitely the problem will not be solved .
rgds
Yannick"
1811504,2019-04-19 05:22:44 UTC,@brian_p @Umesh Mahindrakar
1811504,2019-05-19 17:33:26 UTC,That Scan.py script fails on several printers I know of . If you have an android device try Mopria client when scanner is connected to network
1811504,2019-05-01 15:23:41 UTC,To summarize the state of wifi scanning: hp-scan fails with output
1811504,2019-05-01 13:55:06 UTC,"The command line wifi scanning tool (not using HPLIP) given in comment #36 works for me. Thanks a lot, @petrj!"
1811504,2019-04-23 09:52:48 UTC,"> .....is worth a try.
"
1811504,2019-04-19 12:57:09 UTC,"Thank you for your response, Luca."
1811504,2019-08-07 18:58:11 UTC,"Hi,
**Works** for me via WiFi with the 'hp-scan' CLI and Simple Scan 3.28.0"
1811504,2019-05-21 23:10:38 UTC,"It seems to me the error is of SANE timing out prematurely, as if it assumes the `hpaio` class all have automatic feeders."
1811504,2019-08-12 15:03:25 UTC,"Did you have to install a binary plugin (using hp-plugin) for it to work, Thomas? (In theory none is required for this model.)"
1811504,2020-05-05 19:16:14 UTC,"Edit for #63 : I tested again today and I was able to scan both in gray and colour (and up to dpi), although I didn't change anything in my hplip configuration (3.20.3) since that comment! So problem mysteriously solved for me... for now."
1811504,2019-10-21 19:21:53 UTC,"Hi,"
1811504,2020-04-06 20:30:23 UTC,I have the exact same problem on Ubuntu 3.18.04 with hplip 3.19.12 installed. It worked fine for a few months but things went wrong a few days ago (scanner now only works in gray mode and up to 200 dpi). So maybe an update caused a regression ?
1811504,2020-04-20 14:32:30 UTC,"Hi,
I don't know if I can ask help here, so if not please just tell me."
1811504,2020-04-24 21:30:19 UTC,"I installed the LJ M28A with Ubuntu 18.04.3  provided HPLIP. When I tried scanning, it asked me for additional plugins and I did install them. Everything went fine, printing and scanning. I unfortunately decided to remove the hplip from Ubuntu and use the latest HP one. Now I can only scan Text, no color."
1811504,2020-03-27 18:22:46 UTC,Scanner works with hplip-3.20.3 and updates enabled.
1811504,2020-05-07 13:20:25 UTC,"I was also affected by this problem. The MFP support AirScan, therefore it is possible to scan with such interface. Very recent version of SANE support this, but for old SANE versions you can find an driver here. https://github.com/alexpevzner/sane-airscan I've install it from the repository and it works!!! I can scan any modes with hi resolution (600 dpi)."
1811504,2020-05-08 20:59:41 UTC,"Hi, I'm an absolute newbie and may be asking something trivial. I've installed the sane-airscan package,so now what? Should I use the same applications that didn't work before such as skanlite or xsane and expect them to work now? This is not the case, is there any other thing that I'm missing?
Thanks a lot,"
1811504,2019-08-20 23:30:02 UTC,I would not have revisited this bug report if it had not been for
1811504,2020-05-08 21:28:07 UTC,"OK, it was actually a trivial thing, just needed to refresh the search for scanners, it works!! Thanks very much for posting the different solutions"
1811504,2020-06-01 09:00:48 UTC,"From my point of view the bug should be closed somehow. As I understand MFP M28 uses closed source protocols from Apple (AirScan) and Microsoft (WP-scan) for scanning, therefore the scanning plugin form HP is closed source and Ubuntu developers can do little with it, otherwise MFP M28 linux users, who can push HP directly to fix the problem. The workaround solution (sane-airscan/current SANE) are open source and based on reverse engineering specification of the protocol. My opinion that the proper way of fixing the issue is not to do something in the plugin, but asap include a new version of SANE to next Ubuntu release and/or backported SANE airscan to current Ubuntu if possible.
P.S. As many other users of HP, I absolutely disappointed of such ""good quality"" drivers from the vendor. I hope it will change in the future."
1811504,2021-02-19 07:56:13 UTC,This worked for me:
1811504,2019-01-13 14:52:00 UTC,Interesting! The plugin seems not required but when I scan with hp-scan it asks me to install the plugin (I previously uninstalled the plugin and moved out /var/lib/hp/hplip.state)
1811504,2020-02-17 22:08:15 UTC,"Just FYI there is now a new solution, no need for HPLIP nor proprietary drivers with other manufacturers."
1811504,2020-02-02 12:08:53 UTC,"Hi all,"
1811504,2019-11-21 21:30:32 UTC,"Hi,"
1811504,2020-05-31 16:22:30 UTC,"While there are workarounds for this, I don't see any indication that this is fixed in Ubuntu."
1811504,2019-04-18 17:27:05 UTC,"> Testing should be done with an HPLIP version of 3.18.9
> or greater to avoid bug 1797501.
"
1811504,2019-01-13 14:28:06 UTC,The evidence from models.dat is that a plug-in is not required. This is repeated at
1811504,2019-04-15 12:35:03 UTC,"Hi All,"
1811504,2019-01-13 15:23:35 UTC,"I can scan via network and I get a 503 error like previous test.
409 error seems disappeared after I removed the plugin."
1811504,2019-01-13 15:14:51 UTC,"I cannot account for your experience with hp-scan. Using it with a USB-connected PSC 1300 here does no such thing. Altering models.dat? That shouldn't be needed as it has ""plugin=0"". Try xsane or simple-scan."
1811504,2019-01-13 15:05:32 UTC,ok made some progress but still no luck!
1811504,2019-01-12 11:16:11 UTC,Message #5:
1811504,2019-01-12 17:08:00 UTC,"still no luck!
modified models.dat but always get sane: i/o error. and no scan at all.
Tried in ubuntu 18.04.1 and Manjaro with hplip-3.18.12 but same issue."
1811504,2019-01-12 18:44:20 UTC,Anything shown with 'journalctl'?
1811504,2019-01-13 15:34:26 UTC,curl -v -s http://<IP_or_hostname.local>:8080/eSCL/ScannerCapabilities
1811504,2019-01-12 18:55:53 UTC,"-> %   avahi-browse -rt _uscan._tcp
+ wlp6s0 IPv4 HP LaserJet MFP M28w (4FA59A)                 _uscan._tcp          local
= wlp6s0 IPv4 HP LaserJet MFP M28w (4FA59A)                 _uscan._tcp          local
   hostname = [NPI4FA59A.local]
   address = [192.168.1.173]
   port = [8080]
   txt = [""note="" ""duplex=F"" ""is=platen"" ""cs=color,grayscale"" ""pdl=application/pdf,image/jpeg"" ""uuid=564e4333-4b34-3438-3737-84a93e4fa59a"" ""rs=eSCL"" ""representation=http://NPI4FA59A.local./ipp/images/printer.png"" ""vers=2.63"" ""usb_MDL=HP LaserJet MFP M28-M31"" ""usb_MFG=HP"" ""mdl=LaserJet MFP M28-M31"" ""mfg=HP"" ""ty=HP LaserJet MFP M28-M31"" ""adminurl=http://NPI4FA59A.local."" ""txtvers=1""]"
1811504,2019-01-13 10:21:50 UTC,Apologies - I hadn't fully appreciated you were using a USB connection. You could disconnect it and try wireless.
1811504,2019-01-13 11:00:16 UTC,"Yes, I'm using a USB connection.
I tried also via wireless but it fails the same way (i/o error code 9) when it starts scanning."
1811504,2019-01-13 13:27:58 UTC,"A 409 http error code indicates a conflict. A portion of the data which is sent conflicts with the software's idea of what the scanner is capable of. The capabilities are shown in your journalctl file by the ""Platen"" entries."
1811504,2019-01-13 13:30:23 UTC,bb_esc ---> bb_escl
1811504,2019-04-18 17:22:25 UTC,@lucazade and Samuele Rini (and anyone else who is interested).
1811504,2019-01-13 13:43:27 UTC,if I remove /usr/share/hplip/scan/plugins/bb_escl.so
1811504,2019-01-12 20:22:41 UTC,Your avahi-browse output shows
1811504,2019-01-13 15:37:18 UTC,here is the output! hope you can find the culprit! :)
1811504,2019-01-13 01:31:10 UTC,"if I remove ""hp_"" prefix in both entries in models.dat the printer is not recognized during hp-setup:"
1811504,2019-01-13 16:11:16 UTC,using hp-scan and network device and looking output in journalctl -f
1811504,2019-02-01 22:28:54 UTC,I've just craeted command line scanning tool as a workaround for this bug. It works only with printer connected via network. Script scan.py did not work for me.
1811504,2019-01-13 16:05:42 UTC,Please would you describe how you got scan-debug_wifi.txt?
1811504,2019-01-14 18:37:47 UTC,"Thanks for your support! Really appreciated!
I hope some developer will take care of this issue in the plugin.
Have a nice day ;)"
1811504,2019-01-14 18:22:13 UTC,"> any other way to pass width? maybe hardcode bb_escl.c? just wondering!
"
1811504,2019-01-14 17:55:43 UTC,"unfortunately it doesn't work :(
any other way to pass width? maybe hardcode bb_escl.c? just wondering!"
1811504,2019-03-27 09:46:41 UTC,"I have the same problem with latest hplip (now is @ version 3.19.3, released a few hours ago) and same printer, both with wi-fi or USB.
Linux Mint 19.1."
1811504,2019-01-14 14:31:59 UTC,Port 80 here works the same way as 8080. I don't know why it is automatically choosen instead of 8080.
1811504,2019-01-14 17:04:37 UTC,"> Port 80 here works the same way as 8080.
"
1811504,2019-01-14 12:15:36 UTC,"I was trying with wget to get the image and it works!. I didn't think about curl :)
Now I'm modifying scan.py to suit my needs!"
1811504,2019-01-14 12:04:49 UTC,Dispiriting! I imagine you have tried switching the device on and off?
1811504,2019-01-14 06:39:48 UTC,"no luck also with this tool!
the webserver on the printer always answers with a 503 error."
1811504,2019-01-13 18:24:28 UTC,"> I've uninstalled hplip and removed /usr/share/hplip dir and reinstalled it back.
>
> Unfortunately it always ask for plugin installation even modifying models.dat
> (stripping hp_).
"
1811504,2019-01-13 17:59:01 UTC,I've uninstalled hplip and removed /usr/share/hplip dir and reinstalled it back.
1811504,2019-01-13 17:12:30 UTC,"scan-debug_wifi.txt
-------------------
scl_open() calling bb_escl.so PASSED
scan/sane/escl.c 89: Calling escl bb_unload:"
1811504,2019-01-14 12:31:12 UTC,wget is as suitable a tool as curl; the location should also display in a web browser. Did port 80 work with wget? (I was thinking in terms of a firmware bug). Perhaps not all HP eSCL scanners work in exactly the same way.
1811505,2020-03-07 10:20:45 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1811517,2020-06-02 08:22:33 UTC,As per the description above - 2nd June 2020 - bug still extant:
1811517,2020-06-02 08:27:00 UTC,Version of Raspberry Pi OS - buster:
1811517,2020-06-04 09:17:15 UTC,"Indeed, same version as yours."
1811522,2019-01-21 12:09:57 UTC,This bug was fixed in the package budgie-artwork - 0.9.6.1
1811522,2019-01-21 12:07:52 UTC,"The verification of the Stable Release Update for budgie-artwork has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1811522,2019-01-14 18:00:53 UTC,"Hello fossfreedom, or anyone else affected,"
1811522,2019-01-15 19:16:22 UTC,"v0.9.7.1 for cosmic has been tested successfully, installed from proposed. Test case was completed successfully."
1811522,2019-01-15 18:55:29 UTC,v0.9.6.1 for bionic has been tested successfully on a clean 18.04.1 ISO install.  Test case was completed successfully
1811522,2019-01-14 18:14:21 UTC,"Hello fossfreedom, or anyone else affected,"
1811522,2019-01-21 12:07:48 UTC,This bug was fixed in the package budgie-artwork - 0.9.7.1
1811530,2020-08-07 12:26:18 UTC,I can confirm the behaviour Muench describes on Ubuntu 20.04 with LO 6.4.4.2.
1811530,2020-08-07 11:49:33 UTC,"I am also affected by the problem with the flickering video.
May be my observation helps someone to find a solution or workfix."
1811530,2019-10-24 03:02:27 UTC,"Upgrading to HWE kernel and graphic stacks somewhat relieves the problem. At least now the presentation doesn't show it, but only the info screen."
1811530,2019-10-21 10:11:23 UTC,"Thanks for that shemgp, so if the same version of the snap works on one version of Ubuntu and not another, this may not actually be a libreoffice bug but rather something render-related on 18.04 specifically."
1811530,2019-10-21 08:52:11 UTC,And that it does exist in Ubuntu 18.04 but not in Ubuntu 19.10.
1811530,2019-10-21 08:50:59 UTC,"I can confirm that the flickering white stripes doesn't exist in upstream debs:
eg. https://mirror.aarnet.edu.au/pub/tdf/libreoffice/stable/6.3.2/deb/x86_64/LibreOffice_6.3.2_Linux_x86-64_deb.tar.gz"
1811530,2019-01-17 14:57:54 UTC,"after experimenting with different slideshows: it does change somehow, there are some videos that work fine now, others show green patches instead and some still show the same error than with the old packages."
1811530,2019-01-17 15:48:13 UTC,"well the bug exists already: https://bugs.documentfoundation.org/show_bug.cgi?id=118631 they sent me here, because the bug doesn't appear in the appimages."
1811530,2019-01-17 15:30:33 UTC,"Thanks for the additional feedback. It looks like this might be an upstream bug, rather than something specific to Ubuntu. Would you mind filing a bug at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided, and sharing the link to it here? Thanks!"
1811530,2019-01-17 14:47:26 UTC,apport information
1811530,2019-01-17 16:23:23 UTC,"Ah, thanks."
1811530,2019-01-17 14:47:20 UTC,apport information
1811530,2019-01-17 14:47:23 UTC,apport information
1811530,2019-01-15 11:45:10 UTC,"Is the upstream package the same as in the ppa? If yes, the bug is still present after updating LO per ppa. If necessary I can test the newest package from the LO Site as well."
1811530,2019-01-15 11:49:56 UTC,"Running: apport-collect 1811530, produces the following output:
Package libreoffice not installed and no hook available, ignoring
GtkDialog mapped without a transient parent. This is discouraged."
1811530,2019-01-15 12:42:28 UTC,"The upstream package is not the same as in the PPA, if you don't mind testing it that would be useful."
1811530,2019-01-15 13:39:01 UTC,apport information
1811530,2019-01-14 11:00:16 UTC,Thanks for the report!
1811530,2019-01-15 13:39:03 UTC,apport information
1811530,2019-01-15 13:42:44 UTC,"ok than I give the upstream package a go, but at the earliest tomorrow. The apport informations seem to have worked now."
1811530,2019-01-16 10:11:51 UTC,Thanks! Looking forward to your feedback on the upstream packages.
1811530,2019-01-15 13:39:02 UTC,apport information
1811530,2019-01-17 14:46:17 UTC,There is no change with the newest upstream packages. The behavior stays the same. As addition I give some apport informations from a second pc that shows the same behavior.
1811533,2020-08-20 15:38:56 UTC,https://git.qemu.org/?p=qemu.git;a=commitdiff;h=76525114736e8f669766
1811533,2020-04-01 08:01:29 UTC,"I have been using this patch https://patchwork.kernel.org/patch/11346881/ on qemu 4.2 as a fix since January without any ill effects. It is already included into qemu 5.0 rc0 and rc1, so it seems qemu 5.0 will be free from this bug."
1811533,2020-03-18 00:01:05 UTC,Also affects me when running Qemu 4.0.0 with -machine pc-q35-3.1. I get this on the command line:
1811533,2020-01-08 17:28:00 UTC,"I have applied these patches on qemu 4.2 and it seems they do fix the problem: no more  vhost_region_add_section in the log, and I haven't observed network or general performance loss in the span of one hour."
1811533,2020-01-08 13:57:02 UTC,"Can you try the pair of patches I've just posted:
    vhost: Don't pass ram device sections
    hyperv/synic: Allocate as ram_device"
1811533,2019-10-10 17:47:48 UTC,"Hi,"
1811533,2019-09-20 19:41:50 UTC,Also attaching my libvirt log with a few errors at the end of the log.
1811533,2019-09-20 15:38:40 UTC,"No, I think it's the other way around: clearing guest pages is unrelated. It is easy to check with the following kernel patch:"
1811533,2019-09-20 11:24:09 UTC,"x-hv-synic-kvm-only does two things:
1) Disables in-QEMU synic and this should be unrelated to the issue as it is unrelated to stimers."
1811533,2019-09-20 11:02:03 UTC,"Another observation:
Adding CPU flag x-hv-synic-kvm-only also fixes the issue, because it switches only synic to Qemu 3.0 behavior, leaving other features of > Qemu 3.0 available."
1811533,2019-09-20 10:22:09 UTC,Zilvinas/Damir: Can you paste in the qemu commandline you're using please.
1811533,2019-09-20 10:20:35 UTC,"CC's in Vitaly; he knows a bunch about the Hyperv hv_ and windows stuff.
It feels weird that something timer related should change something hugepage related."
1811533,2019-09-19 19:22:09 UTC,What can be done to increase the visibility of this? It's quite annoying to deal with.
1811533,2019-08-11 07:44:00 UTC,"Other users are having similar issues:
https://github.com/virtio-win/kvm-guest-drivers-windows/issues/402
https://www.reddit.com/r/VFIO/comments/cc2473/virtio_network_drivers_failing_on_win10_guest/etk6f6i/"
1811533,2019-08-07 19:13:20 UTC,Still broken with Qemu 4.1rc2 /w Kernel 5.2.
1811533,2019-07-12 15:40:20 UTC,Refresh: still happening with Qemu 4.0 and Kernel 5.2.
1811533,2019-09-20 19:01:46 UTC,"As asked by dgilbert-h, I am attaching my qemu command line. It is ripped from libvirt log."
1811534,2019-12-10 04:17:28 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1811534,2019-08-24 13:33:12 UTC,I tried reproducing this with 2.39.2+18.04 on 18.04 by setting the following as root:
1811534,2019-01-12 20:00:03 UTC,"snap    2.36.3
snapd   2.36.3
series  16
ubuntu  18.10
kernel  4.18.0-13-generic"
1811534,2019-12-10 04:17:26 UTC,[Expired for snapd because there has been no activity for 60 days.]
1811537,2019-08-06 14:47:28 UTC,"I managed to reproduce this, although the other way around (with MAAS in a container and PXE booting VMS)."
1811538,2019-01-13 05:51:53 UTC,"Note those characters are not the preferred encoding for these temperature symbols. GNOME Recipes used to use them as well, and I asked its developer to remove them: https://gitlab.gnome.org/GNOME/recipes/commit/2eda5945131d1bec59bf0762d13118dab4e39e19"
1811538,2019-01-13 17:32:58 UTC,"Ah that's interesting. I found the bug report where gnome-weather changed to use the single-codepoint encoding (https://bugzilla.gnome.org/show_bug.cgi?id=785274), and this is what made me think it was the preferred encoding. They were concerned about linebreaks between the ° and the C/F, not about looking good in monospaced fonts as I had guessed."
1811538,2019-01-13 18:03:32 UTC,Bug reported against libgweather: https://gitlab.gnome.org/GNOME/libgweather/issues/8
1811550,2019-11-06 20:13:37 UTC,"Related feature request is here: https://bugs.launchpad.net/kicad/+bug/1850793
It could be handled at the same time."
1811557,2019-01-14 23:22:00 UTC,Also the feature permits far more shapes and sizes making this feature vastly superior in precision and customization to the distribution of parts.
1811557,2019-01-14 23:51:32 UTC,Please lets not clutter this bug report with debate over other tools.  It makes it harder to find/resolve issues.
1811557,2019-01-14 23:20:49 UTC,The create array is vastly inaccurate in the likes of the feature this bug is calling for. Manually laying a geometric shape is far more accurate than the create array tool since it is finely placed by the user in a given area.
1811557,2019-01-14 16:37:50 UTC,@Nick-  I think the idea of distributing along other elements on the board is pretty straight-forward and could be helpful.  I imagine it working in a method similar to the Solidworks implementation.  Let's keep this triaged for now.  Create array is a good tool for some things but it doesn't move existing elements
1811557,2019-01-13 22:03:15 UTC,"I don't think this bug is of much use without examples on what is expected, and how it is supposed to work."
1811557,2019-01-13 07:36:37 UTC,also create array is very inaccurate and cumbersome since you are not permitted to draw a guide circcle or other geometric primitive to which you want your footprints orientated to.
1811557,2019-01-14 17:09:59 UTC,Falls in the geometry constraint solver work package.
1811557,2019-01-13 07:24:07 UTC,"Take a look at the ""Create array..."" tool. You can access it from the context menu or by hiting Ctrl-T while cursor is over component."
1811557,2019-01-13 07:35:43 UTC,its not the same thing and will not work since you may well have many different footprints instead of just a single type.
1811559,2019-01-13 22:01:00 UTC,"What exactly do you mean by ""clobbers the whole footprint file - regardless if it was saved or not.""?"
1811559,2019-01-14 23:24:27 UTC,Import a kicad mod file into a footprint and the whole footprint turns into nothing more but that kicad mod file with everything else automatically removed from the footprint.
1811560,2020-10-05 04:17:20 UTC,[Expired for tempest because there has been no activity for 60 days.]
1811560,2019-01-13 09:03:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630495"
1811560,2020-03-23 14:03:43 UTC,What is the status here? Is now Tempest failing in Glance due to image visibility?
1811560,2020-06-14 13:14:12 UTC,"Moving to Incomplete for now, the change in glance hasn't got through and it doesn't seem like it will."
1811560,2020-08-05 14:50:59 UTC,"Change abandoned by Abhishek Kekane (<email address hidden>) on branch: master
Review: https://review.opendev.org/630495
Reason: Dependent patch has been abandoned
https://review.openstack.org/#/c/628430/"
1811562,2019-03-06 14:28:07 UTC,"Removing packages from disco:
 mathicgb 1.0~git20170606-2ubuntu1 in disco
  libmathicgb-dev 1.0~git20170606-2ubuntu1 in disco amd64
  libmathicgb-dev 1.0~git20170606-2ubuntu1 in disco arm64
  libmathicgb-dev 1.0~git20170606-2ubuntu1 in disco armhf
  libmathicgb-dev 1.0~git20170606-2ubuntu1 in disco i386
  libmathicgb-dev 1.0~git20170606-2ubuntu1 in disco ppc64el
  libmathicgb-dev 1.0~git20170606-2ubuntu1 in disco s390x
  libmathicgb0 1.0~git20170606-2ubuntu1 in disco amd64
  libmathicgb0 1.0~git20170606-2ubuntu1 in disco arm64
  libmathicgb0 1.0~git20170606-2ubuntu1 in disco armhf
  libmathicgb0 1.0~git20170606-2ubuntu1 in disco i386
  libmathicgb0 1.0~git20170606-2ubuntu1 in disco ppc64el
  libmathicgb0 1.0~git20170606-2ubuntu1 in disco s390x
  mathicgb 1.0~git20170606-2ubuntu1 in disco amd64
  mathicgb 1.0~git20170606-2ubuntu1 in disco arm64
  mathicgb 1.0~git20170606-2ubuntu1 in disco armhf
  mathicgb 1.0~git20170606-2ubuntu1 in disco i386
  mathicgb 1.0~git20170606-2ubuntu1 in disco ppc64el
  mathicgb 1.0~git20170606-2ubuntu1 in disco s390x
Comment: LP: #1811562, remove mathicgb
1 package successfully removed."
1811571,2019-05-25 00:04:00 UTC,"Hello Amr, or anyone else affected,"
1811571,2019-06-05 17:27:15 UTC,I have been using 2.2.4-0ubuntu0.18.04.1 from bionic-proposed without any issues. I successfully read and write .lyx files and export them into PDF using several backbends without any problems.
1811571,2019-05-20 12:55:22 UTC,I am one of the upstream developers. What I can say about this 2.2.4 version is
1811571,2019-06-06 09:45:13 UTC,This bug was fixed in the package lyx - 2.2.4-0ubuntu0.18.04.1
1811571,2019-06-06 09:35:09 UTC,"The verification of the Stable Release Update for lyx has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1811571,2019-05-18 15:16:40 UTC,"@Jean-Mark, would you shed some light on comment #7?"
1811571,2019-04-21 15:50:51 UTC,Uploaded with some minor changelog edits.
1811571,2019-05-15 13:15:35 UTC,Same question as https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1595358/comments/18:
1811571,2019-04-20 18:55:45 UTC,Thanks for your work on this!
1811571,2019-02-03 00:20:15 UTC,"The attachment ""lyx_2.2.4-0ubuntu1.patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1811571,2019-02-02 22:25:57 UTC,I attached the diff that was posted in duplicate bug #1602145 by Juhani Numminen
1811571,2019-02-02 22:21:20 UTC,debdiff
1811571,2019-01-13 11:04:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811571,2019-05-15 13:32:32 UTC,"To one of the Lyx upstream developers, could you please answer comment #7?"
1811573,2019-01-13 11:39:06 UTC,"Fixed, thanks for spotting it!"
1811573,2019-08-03 18:15:17 UTC,"Fixed in version 1.0.2, released yesterday,"
1811580,2019-02-26 17:54:49 UTC,"Okay.  I guess I would have expected that if there was a dependency on a specific kernel version, that I wouldn't be able to install a package that wasn't compatible and breaks the system by installing a security update.  It would be preferable to be informed there is a security update but that I can't install it because I am running an out of date kernel...then I know I am insecure and that the kernel is the issue.  But I guess that is a topic for the package management guys.  The error message from systemd-tmpfiles about too many symlinks isn't particularly helpful either since in this case the problem (apparently) has nothing to do with symlinks but rather filesystem apis in the old kernel (I guess?)."
1811580,2019-02-07 09:52:49 UTC,"Hi xnox
Thank your for your fast reply!"
1811580,2019-02-26 14:39:55 UTC,Same situation.  Ubuntu 16.04 openvz vps image of unknown origin.
1811580,2019-02-26 17:05:22 UTC,"On Tue, Feb 26, 2019 at 02:39:55PM -0000, Matt P wrote:"
1811580,2019-04-23 16:44:07 UTC,There is something that I cant understand.
1811580,2019-02-06 15:37:37 UTC,@cadirol
1811580,2019-04-23 23:10:43 UTC,"On Tue, 26 Feb 2019 at 18:05, Matt P <email address hidden> wrote:

>
> Okay.  I guess I would have expected that if there was a dependency on a
> specific kernel version, that I wouldn't be able to install a package
> that wasn't compatible and breaks the system by installing a security
> update.  It would be preferable to be informed there is a security
"
1811580,2019-05-14 15:20:29 UTC,"Thank you @vorlon . I made some test with that image on a clean server and it works with no issues, but I had issues in different servers with the same image and other worked fine with the same AMI."
1811580,2019-07-14 04:17:41 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1811580,2020-08-16 01:37:38 UTC,"I think I had the same problem.  I think it was fixed with ""chown root:root /var""."
1811580,2019-04-23 17:44:29 UTC,"On Tue, Apr 23, 2019 at 04:44:07PM -0000, Julian Alarcon wrote:

> There is something that I cant understand.
"
1811580,2019-02-06 14:10:55 UTC,"Good day
Same issue here! After upgrade systemd from  229-4ubuntu21.10 to 229-4ubuntu21.15 and a reboot, ssh did not start anymore.
As ugly workaround i ran #mkdir -p -m0755 /var/run/sshd && systemctl restart ssh.service"
1811580,2019-01-14 15:39:47 UTC,"Thank you for your bug report. What update are you talking about? Did you try to downgrade the packages to see if that resolves your issue? The most recent security update includes fixes for journal and tmpfile error, that shouldn't have an impact on the ssh service and there has been no other report about that..."
1811580,2019-01-16 12:54:21 UTC,@ Spas Spasov (spaszspasov)
1811580,2019-01-16 12:51:00 UTC,"@ David (dasoto)
Please report bad permissions to whoever is distributing the ""NVIDIA Jetson TX2 users"" installation you are using. Maybe there are some upgrade hooks that could be shipped by packages install in that installation to fix / mitigate this issue."
1811580,2019-01-16 10:00:41 UTC,I'm experiencing the same problem with Ubuntu 16.04.5 on OpenVZ (with kernel: 2.6.32-042stab127.2).
1811580,2019-01-15 20:58:19 UTC,"@Dimitri John Ledkov (xnox) I manully upgrade to
Linux pan 4.19.13-sunxi #5.70 SMP Sat Jan 12 15:43:21 CET 2019 armv7l armv7l armv7l GNU/Linux
and the issue seems also to be fixed for me now"
1811580,2019-01-15 20:16:40 UTC,@Dimitri John Ledkov (xnox) I think I'm forced by Armbian to this kernel revision by default. TBH I don't know if a manual upgrade will break the OS or not. I also have not investigated on how to upgrade it manually. I have no permission issues like David (dasoto) I already checked that before I replied to this bug report. Everything on the root directory of my machine is root / root.
1811580,2019-01-15 19:59:10 UTC,@Dimitri John Ledkov (xnox) It's Armbian (Xenial) for OrangePI One. Here df -Th of my filesystem:
1811580,2019-01-15 18:34:15 UTC,This solve the issue.
1811580,2019-01-15 18:11:59 UTC,@ David (dasoto)
1811580,2019-01-15 17:47:27 UTC,@Dimitri John Ledkov (xnox)
1811580,2019-01-15 16:48:36 UTC,"@ Andreas Kar (thexmanxyz)
3.4.113-sun8i is an extremely ancient kernel. Why are you using such a kernel and where does it come from?"
1811580,2019-01-15 16:25:18 UTC,I have exactly the same problem. I check and an auto update was made for systemd from  229-4ubuntu21.10 to  229-4ubuntu21.15 on many of my devices (Jetson TX2). Now devices rebooted doesn't start ssh and I lost complete communication with all those devices.
1811580,2019-01-14 16:45:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811580,2019-01-17 16:45:42 UTC,"@Dimitri John Ledkov (xnox)
I know that in my case the Kernel is quite old, however it still affects the version I reported above and upgrading has some drawbacks in this case. What is the reason causing the issue I described? Are there any options fixing it without switching kernel version? Thanks in advance!"
1811580,2019-01-14 16:35:05 UTC,"This problem is not new and it appears again with the new systemd ""229-4ubuntu21.15"" released."
1811586,2019-06-01 11:50:40 UTC,I would expect the courtesy of a BRIEF statement of why this is considered invalid.
1811587,2019-01-13 15:23:28 UTC,I had a kind problem in my atualization and i would like shared.
1811588,2019-01-14 09:11:53 UTC,"Hi Olivier,"
1811588,2019-01-14 06:13:34 UTC,"Try checking the ""Show Any"" option in the ""View"" menu.
Does this show your saved passwords?"
1811589,2019-04-19 06:17:13 UTC,"Hi Levgen, thanks for fill the bug.
Just two things about:
About object dialog:
Is working on groups not layers (but retain original id, thats why it show you as Layer)
About root layers as groups:
What can a user like work without layers to use a group like a group not like a layer?"
1811589,2019-04-19 06:28:02 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1811589,2019-04-19 07:31:52 UTC,See the answer https://gitlab.com/inkscape/inbox/issues/385
1811591,2019-01-13 19:33:54 UTC,Thanks for taking your time to report this issue and help making Ubuntu better.
1811596,2019-04-14 13:51:36 UTC,"I'm a new Linux user, but I started with Fortran in 1968. I don't usually get this stumped. I just signed in here to ubuntu single sign on with no problem. When I try to sign in through settings, I get a pop-up asking for authentication for Snap Daemon (it accepts my password) then there is a pop-up asking for authentication for keyring ""Default. . . I don't recall being asked to set a password for this, but log in to ubuntu single sign on fails. In Windows I would scan the disk for errors, but I can't seem to find the right commands. I would appreciate any suggestions."
1811596,2019-05-19 04:46:35 UTC,I had this problem last year and found a fix by asking here:
1811596,2019-04-13 13:21:11 UTC,Upstream bug: https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/58
1811596,2019-05-21 08:58:12 UTC,Could well be a bug in gtk3-nocsd
1811596,2019-04-13 07:13:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811596,2019-01-13 20:20:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1811596,2019-01-13 17:55:47 UTC,"Ubuntu 18.04/amd64
unity-control-center 15.04.0+18.04.20180216-0u"
1811596,2019-04-13 07:22:48 UTC,"This bug seems like only in a unity session and the UI is normal in a ubuntu session.
Someone mentioned it there https://community.ubuntu.com/t/testing-unity-session-in-18-04/987/156"
1811596,2019-01-13 17:36:45 UTC,"It seems that the buttons are missing.
My window:
https://ibb.co/0QvWrGB"
1811603,2019-08-01 16:37:08 UTC,There's been a new release since you reported this issue - could you check with that release for me please?
1811603,2019-01-15 10:04:25 UTC,Sorry - couldn't log in again yesterday for some reason.
1811603,2019-01-14 18:51:51 UTC,"I’d be happy to. I’m leaving in a few minutes, be back around 3:30-4 Pacific Standard time this afternoon."
1811603,2019-01-14 18:30:29 UTC,"Not too long, maybe 20 seconds at the very longest."
1811603,2019-01-14 16:03:31 UTC,"Thanks for working on this. How long should I wait? My Mac is not terribly slow, as my boot dive is a SSD, even though it’s an older Mac."
1811603,2019-01-14 13:57:47 UTC,"Also, bear in mind a lot of files need to be loaded when it starts - it might just take a long time to open fully. Still investigating."
1811603,2019-01-14 13:47:29 UTC,"I can't seem to reproduce this error yet, but I did find a different one, so I am still investigating this issue."
1811603,2019-01-14 10:46:44 UTC,Hi.
1811603,2019-01-13 18:26:25 UTC,"I just tried again, and this time I briefly saw the opening graphic, but then nothing. I have to force quit. I would love to use this, but can't!"
1811603,2019-01-14 16:01:37 UTC,"I am runnn8ng the latest version, and never saw any pop up. I only saw a brief graphic with the name  and then nothing."
1811613,2019-04-26 19:17:37 UTC,"Hi,"
1811613,2019-06-26 04:17:20 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1811615,2019-01-14 20:36:44 UTC,"Thanks for pointing that the dock is conflict with that specific keybinding, reassigning"
1811615,2019-01-14 01:06:00 UTC,I don't know what I did but it doesn't happen anymore (😕)
1811615,2019-01-14 09:48:41 UTC,Thank you for your bug report. Could you add your journalctl log from a session having the issue?
1811615,2019-01-14 19:24:36 UTC,"There it is. I think I found the reason this happens, though. It's the dash to dock extension, which overrides the custom commands:
https://askubuntu.com/questions/977876/changing-command-super-q"
1811622,2019-08-20 01:36:04 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1811624,2019-01-16 01:04:25 UTC,Thanks for the report and fix Thomas!
1811626,2019-01-14 08:14:02 UTC,On the local client I have the following log snippet when I print a test page:
1811626,2019-01-14 13:44:46 UTC,"I would advise that you remove HPLIP and the plugin software from the client, read"
1811628,2020-07-27 15:11:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811629,2019-05-19 15:09:29 UTC,"I do think, the 2 first items would be possible with #1719184
and the third with #1811629"
1811629,2019-05-19 15:10:02 UTC,i meant #1818450
1811631,2019-01-14 01:07:17 UTC,when the actual menu of the system is
1811637,2020-03-02 11:27:28 UTC,"Xiaodong,"
1811637,2020-05-02 04:17:28 UTC,[Expired for GNU Arm Embedded Toolchain because there has been no activity for 60 days.]
1811641,2020-01-25 01:48:59 UTC,I think this is the same as https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/1769848
1811641,2020-01-25 02:46:04 UTC,"Yes, this looks like the same thing.  The root of the problem is that /usr/bin/wodim is lacking the u+s (where user=root) permission."
1811641,2019-08-29 07:57:10 UTC,Thanks for taking the time to report this bug.
1811641,2019-08-29 06:38:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811641,2019-08-29 19:58:16 UTC,@Chris Guiver Thank-you for taking the time to respond to this bug report!
1811641,2019-08-29 06:39:55 UTC,"I was affected by this, the sticky bit workaround resolved my issue."
1811645,2019-05-28 02:51:12 UTC,"Verified the bug was fixed with testing PPA on Italia - 201810-26511.
Passed the tests:
thumderbolt3/insert
thumderbolt3/storage-test
thumderbolt3/remove"
1811645,2019-05-22 10:23:24 UTC,"Hi Sylvain,"
1811645,2019-05-23 12:40:10 UTC,"@Jerry,"
1811650,2019-03-26 08:06:56 UTC,Fixed in ukui-menu 1.1.10-1:
1811651,2019-04-27 18:05:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811653,2021-01-19 06:57:26 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1811660,2020-04-06 14:59:08 UTC,I think this is fixed based on the status of bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811785.  I will wait to close this bug until I can verify the fix in focal.
1811660,2019-09-04 15:17:47 UTC,Possible to provide nfit kmod with fix?
1811660,2019-09-04 13:04:55 UTC,"Khaled, could you build a test kernel 4.15.0-60-generic with fix please?"
1811660,2019-09-04 13:03:22 UTC,Tested latest ndctl version 66 with ubuntu  4.15.0-60-generic
1811660,2019-09-04 12:27:46 UTC,Seeing this on bionic with 4.15.0-60-generic x86_64 kernel.
1811660,2019-02-19 15:37:29 UTC,"This is a kernel issue and we have seen this with upstream kernels and verified the fixes on upstream kernels.
I expect bionic kernel 4.15 and above kernels to display this defect."
1811660,2019-02-19 09:07:08 UTC,"Has this been tested with Disco (19.04) or Cosmic (18.10)?  IOW does this issue with ndctl only exist in Bionic, or does it carry forward?"
1811660,2019-02-14 16:54:48 UTC,This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.
1811660,2019-02-21 08:33:31 UTC,"Sujith,"
1811660,2019-02-12 05:16:40 UTC,I have built a bionic test kernel with those fixes (+2 others needed for backporting) for testing.
1811660,2019-01-28 07:30:17 UTC,Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811785
1811660,2019-01-25 17:12:18 UTC,"After booting to the OS, user is unable to create namespaces by running ""ndctl create-namespace"". Even by using flags such as -f or -e, the operation is not successful.
I am not aware of ipmctl being approved as a management tool for nvdimm-n (yet?)"
1811660,2019-01-25 15:54:45 UTC,"Out of curiosity, Are you using ipmctl and libsafec from Juston Li's PPAs to do the configuration of the NVDIMMs?"
1811660,2019-01-23 13:22:15 UTC,"Fix:
acpi/nfit: Block function zero DSMs
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/commit/?h=libnvdimm-fixes&id=11189c1089da413aa4b5fd6be4c4d47c78968819"
1811660,2019-01-23 12:40:52 UTC,Issue seen across all kernels of Ubuntu 18.04
1811660,2019-01-23 12:39:23 UTC,It can be seen across all 14G Dell EMC servers carrying NVDIMM-N.
1811660,2019-01-22 21:54:26 UTC,Can you add the Firmware versions for the BIOS and for the NVDIMM.  Also can you include the uname -a information as well.
1811660,2019-02-12 06:54:04 UTC,"Another issue pops-up, looks like there are a few nvdimm patches that require backporting:"
1811660,2019-01-22 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811663,2019-01-14 11:11:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/630648"
1811663,2019-01-16 01:49:54 UTC,"Reviewed:  https://review.openstack.org/630648
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=c841dce838397c0d1e57f5964eac699672536814
Submitter: Zuul
Branch:    master"
1811668,2019-05-10 11:51:12 UTC,"> - We add oem-priority because it affects our clients directly but we don't have any contract with
> Canonical.
"
1811668,2019-05-10 09:33:08 UTC,Just a note :
1811668,2019-05-10 09:22:09 UTC,"per current oem project, we don't have this issue."
1811668,2019-03-18 09:13:54 UTC,Please follow the instructions in comment #8.
1811668,2019-05-13 01:57:42 UTC,"Due to no reply to comment #8 I'm just going to assume this is a duplicate of bug 1798790, which seems most likely. Otherwise maybe bug 1705369."
1811668,2019-03-17 04:17:36 UTC,[Expired for OEM Priority Project because there has been no activity for 60 days.]
1811668,2019-03-18 08:59:06 UTC,"I think that is a real important problem, could anybody at least reproduce the issue ?"
1811668,2019-01-16 02:16:16 UTC,"> gnome-shell[30907]: Failed to create backend: No resources
"
1811668,2019-03-17 04:17:34 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1811668,2019-01-14 15:16:26 UTC,Reproduced on a 1080 ti desktop
1811668,2019-01-14 15:16:31 UTC,Thank you for your bug report. Could you attach the journalctl log from a boot hitting the issue of not getting the greeter? Is the configuration a dual GPU or nvidia only?
1811668,2019-01-14 15:31:50 UTC,Salut Sebastien
1811668,2019-03-17 04:17:37 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1811668,2019-01-15 14:29:50 UTC,The log has those errors
1811668,2019-01-15 15:50:46 UTC,Many thanks for being so quick to answer.
1811668,2019-01-15 13:27:56 UTC,Please find attached the Journal log with the user oem-config wizard and one reboot
1811668,2019-01-15 16:19:48 UTC,"Well, the upstream discussion/other bug are about gdm failing to fallback from wayland (which it uses by default) to xorg on nvidia machines where wayland is not working, that could be the issue here as well"
1811670,2019-05-13 12:03:14 UTC,This is live migrate? or cold migrate?
1811670,2020-04-23 18:48:36 UTC,"Looks like this could be a duplicate of bug 1669054. The fix for pike was merged in April 2019, *after* this bug was filed in January 2019. Could you update to latest pike and let us know if that fixes the issue?"
1811670,2020-05-04 15:20:27 UTC,Marking the bug incomplete as there are question for the reporter. Please set it back to New when such question is answered.
1811678,2019-01-14 13:39:27 UTC,I guess this is due to the following lines in debian/rules:
1811678,2019-06-08 07:21:54 UTC,"Sorry for the delay, for some reason I have not received a mail about this bug."
1811681,2019-10-11 22:11:11 UTC,"Reviewed:  https://review.opendev.org/681343
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=81860afeca1b189dfcd8c06c67efcb94d67eeec5
Submitter: Zuul
Branch:    master"
1811681,2019-09-03 13:36:49 UTC,The placement APU was officially removed from nova in train.
1811681,2019-10-25 19:19:23 UTC,This was fixed in train with a new placement charm and changes to nova-cloud-controller.
1811692,2020-01-29 03:50:17 UTC,This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.2
1811692,2020-01-27 19:07:11 UTC,"I can't reproduce the issue on xenial. Either with only the udev rules added to the version on -updates, or with the complete version on -proposed."
1811692,2019-05-20 08:46:51 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1811692,2020-01-14 14:18:30 UTC,"Hello Thadeu, or anyone else affected,"
1811692,2019-05-20 09:21:33 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.1
1811692,2019-05-20 08:46:37 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.10.1
1811692,2019-04-29 16:20:31 UTC,"Hello Thadeu, or anyone else affected,"
1811692,2019-05-16 14:47:54 UTC,"I ran it on a i386 VM where this was found, and it works just fine with the version from bionic-proposed."
1811692,2019-04-29 16:19:42 UTC,"Normally I should request a separate SRU bug for the 'backporting' operation, but basically the test case here is fitting to check if the backport works. So accepting those conditionally."
1811692,2019-04-29 16:09:25 UTC,"Hello Thadeu, or anyone else affected,"
1811692,2019-01-18 18:21:25 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1
1811692,2019-01-18 14:52:31 UTC,Tested that the upload fixes the bug.
1811692,2019-05-16 19:49:38 UTC,Same test worked just fine for cosmic.
1811692,2019-03-08 09:32:22 UTC,"this is referenced in the cosmic backport, so needs SRU template, test case etc"
1811695,2019-01-29 14:58:54 UTC,Here's the Traceback:
1811695,2019-01-31 17:30:27 UTC,juliank indicated this shouldn't be a new issue with update-manager but I had a look around the Error Tracker and didn't find any more RuntimeError crashes re the lock file in it.
1811695,2019-04-11 15:42:29 UTC,"If this is actually happening when someone is trying to cancel the transaction, which isn't really possible, perhaps we should remove the cancel button."
1811696,2019-09-06 22:00:51 UTC,"Pushed to master for inclusion in 3.4. Thanks, Jason and Bill!"
1811696,2019-04-26 19:40:59 UTC,I force pushed a rebased branch with Bill's suggestion to do the rebuild of the reporter.materialized_simple_record table after the other ingests have finished.
1811696,2019-04-03 16:49:53 UTC,Removing pull request tag to make the change suggested by Bill Erickson in comment #4.
1811696,2019-01-24 18:05:46 UTC,"Here's the branch that actually addresses this bug's description, in retrospect, this option is more useful, so when testing this feature, use this branch and not the one in comment #1."
1811696,2019-02-20 17:33:54 UTC,"Code works as expected, but I have a question."
1811696,2019-02-12 18:57:16 UTC,FYI: I rebased the branch on master today and squashed in a small bug fix for keeping track of the child process that is rebuilding the reporter.materialized_simple_record table.
1811696,2019-01-24 16:32:44 UTC,"So, I have added an option to pingest.pl to update the rmsr entries for the ingested records rather than rebuild the entire table. I decided to go this route because rebuilding the entire table cannot be done in parallel and doing so in pingest.pl would end up being done in its own process and would just do what can be done now, via psql. A feature to completely rebuild the table could still be added, as part of my branch if so desired."
1811700,2019-03-22 04:05:59 UTC,This has been forward ported to 2.6. I'll mark as Fix Committed.
1811700,2019-01-28 17:35:17 UTC,https://github.com/juju/juju/pull/9676
1811703,2019-01-14 16:05:23 UTC,"Site of our wait call for container creation:
https://github.com/manadart/juju/blob/3f246e23791455ff482c5089e87f1c6b2173abe2/container/lxd/container.go#L220"
1811703,2019-01-14 17:35:13 UTC,"So the broken pipe would be an indication of getting a TCP RST from the destination when the data was sent, that's usually either because the connection got closed on that side or because of a network issue, like an IP conflict which would cause the other owner of the IP to reject all traffic."
1811703,2019-01-15 01:09:20 UTC,the new dep change has been reverted from 2.5 branch by this PR https://github.com/juju/juju/pull/9627
1811703,2019-01-16 10:24:35 UTC,"If you can reproduce this and are using the LXD snap, you'd probably want to set ""snap set lxd daemon.debug=true"" followed by ""systemctl reload snap.lxd.daemon"", this will have LXD log a lot more details (all requests) and may be helpful in tracking this down."
1811703,2019-01-16 12:00:17 UTC,I am running the 3.9 tagged code with my logging change and --debug so we're getting that level.
1811703,2019-01-16 13:10:55 UTC,Can you get me the LXD debug log too?
1811703,2019-01-16 13:46:21 UTC,In the pastebin up there ^.
1811703,2019-01-16 15:57:02 UTC,"As discussed with Stephane, this looks to be resolvable by ensuring that goroutines are spawned for listener notifications *after* the current connection and listeners have been previously cleared."
1811706,2019-06-22 04:17:28 UTC,[Expired for console-setup (Ubuntu) because there has been no activity for 60 days.]
1811706,2019-04-22 18:44:22 UTC,We run debootstrap on bionic/arm64 on a daily basis for building daily images without encountering this error.  Please provide more detail on how you are invoking debootstrap and the output it produces.
1811706,2019-01-20 11:37:00 UTC,bump
1811709,2020-04-06 18:27:45 UTC,This should include a check for ceph-mon customize-failure-domain=true to ensure that ceph utilizes AZs from MAAS.
1811709,2020-08-31 05:59:04 UTC,"The current code base now caters for this. If you have suggestions for rule updates please submit an MR against the contributed Canonical rules - these are forming a ""good practice"" list for folks to check their cloud deployments against. We already have example rules for nova-compute, but any extras would be very welcome additions."
1811710,2020-09-15 15:18:52 UTC,Pushed to master.  Thanks all!!
1811710,2020-07-29 14:33:01 UTC,I've done a forced push to the new working branch to account for the newly-pushed patch for bug 1889296.
1811710,2020-07-28 19:52:14 UTC,I've pushed a fresh rebase to user/gmcharlt/lp1811710_hopeless_holds_rebased_2020-07-28.
1811710,2020-01-16 16:04:40 UTC,Here you go:
1811710,2020-01-16 15:57:26 UTC,Digging into the error a bit:
1811710,2020-01-14 16:16:35 UTC,We applied this branch to a 3.4.1 test server and were seeing the following errors in the logs:
1811710,2020-01-03 19:38:47 UTC,The issue with OU sorting in the pickup library selector was bug 1857350 and is now fixed.
1811710,2019-11-07 21:06:33 UTC,"We've applied this code to a 3.4 test server with a copy of real PINES data on it, and the only problem I've seen so far is that the dropdown box for the Pickup Library isn't sorted correctly (see screenshot)."
1811710,2020-09-15 15:12:30 UTC,"This looks good and works well for the various scenarios I've thrown at it, and we're no longer seeing the errors in the logs! My signoff is at:"
1811710,2019-08-28 15:32:13 UTC,"Bill, I'm going to ignore the Firefox issues (and/or open new bugs as needed)."
1811710,2019-08-26 21:44:24 UTC,I may have jumped the gun assuming it no longer worked (hold targeter quite naturally changed the data out from under me so I saw what I feared to see).  Date filtering appears to work still in Chrome.
1811710,2019-08-26 20:35:36 UTC,"Not sure about Firefox yet, but date filtering no longer works with the interface under the new regime with any browser.  I'll try to poke at it."
1811710,2019-08-26 20:24:36 UTC,Thanks Bill; the Firefox specific commit isn't critical for the rest of it; I'm testing things without it to see if Moment works.
1811710,2019-08-26 16:17:30 UTC,"Jason, I started reviewing the code, but was quickly stymied by the merge conflicts with current master, the modified date handling in the FormatService, in particular.  It should be possible to remove the date parsing additions and let Moment parse the dates for us."
1811710,2019-08-16 15:22:30 UTC,updated
1811710,2019-08-16 15:17:07 UTC,"Realized the upgrade scripts are missing the changes that went into 002.schema.config.sql and 090.schema.action.sql, will force push a new branch shortly"
1811710,2019-08-16 14:50:07 UTC,Pushed an 8th commit with release notes.
1811710,2019-08-16 14:37:10 UTC,"Hrmm, needs documentation."
1811710,2019-08-16 14:36:33 UTC,top 7 commits from collab/phasefx/lp1811710-hopeless-holds
1811710,2019-09-10 20:34:25 UTC,Added a re-based branch with automated tests:
1811711,2019-01-16 13:30:22 UTC,"Hi,"
1811711,2019-01-16 14:05:09 UTC,"This bug was related to an IRC discussion on Jan 14th but this bug description is not showing the problem that was raised on IRC. The IRC discussion showed a source image with a 9GB Windows 10 installation, turning into an image with only 8 MB of data present.  The images in this bug description don't have any data written so are not illustrating the data conversion issue."
1811711,2021-01-19 06:57:08 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1811713,2019-01-14 20:20:27 UTC,This appears to be affecting current rocky
1811713,2019-08-13 14:59:34 UTC,"Reviewed:  https://review.opendev.org/675358
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=84beb53b79f813b7b974cc6bc3bb36000f1c5de2
Submitter: Zuul
Branch:    stable/queens"
1811713,2019-08-08 14:42:45 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/675358"
1811713,2019-07-15 22:12:52 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/644257
Reason: won't fix it for rocky."
1811713,2019-03-18 15:50:30 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/644257"
1811713,2019-03-14 10:43:28 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.3.0 release.
1811713,2019-01-19 15:40:55 UTC,"Reviewed:  https://review.openstack.org/631876
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=d95b5b9a71955137cc9590ba4b6d1bafe3b1b080
Submitter: Zuul
Branch:    stable/rocky"
1811713,2019-01-19 01:19:31 UTC,"Reviewed:  https://review.openstack.org/631875
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7d24a21b892a19c6a56c1ff49d3f9eae68253587
Submitter: Zuul
Branch:    stable/rocky"
1811713,2019-01-19 00:26:41 UTC,"Reviewed:  https://review.openstack.org/631874
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=4208b04741bb3cf581afe55f71be9b4008e18f4e
Submitter: Zuul
Branch:    stable/rocky"
1811713,2019-01-18 22:33:41 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/631869
Reason: we're just backing out the selinux items"
1811713,2019-01-18 19:39:54 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631876"
1811713,2019-01-18 19:37:50 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631874"
1811713,2019-01-18 19:39:25 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631875"
1811713,2019-01-18 19:05:25 UTC,"openstack-selinux-0.8.15-1.el7ost.noarch works, openstack-selinux-0.8.17-0.20190116193749.faef39f.el7.noarch does not."
1811713,2019-01-14 21:09:56 UTC,Appears to be failing in CI as well.
1811713,2019-01-14 21:33:22 UTC,"Oh nevermind, that failed for a different reason."
1811713,2019-01-18 19:18:56 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631869"
1811713,2019-01-16 21:42:31 UTC,Ok so it's an selinux enforcing problem. You can set undercloud_selinux to permissive and install the undercloud and it should be fine.
1811713,2019-01-16 21:47:35 UTC,"Sorry, set undercloud_enable_selinux to False in undercloud.conf"
1811713,2019-01-15 21:32:13 UTC,"I am able to reproduce the problem. I traced the problem to an selinux issue, and ultimately to [1], which was recently introduced to stable/rocky."
1811713,2019-01-17 00:11:23 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631354"
1811713,2019-01-17 00:11:36 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631355"
1811713,2019-01-17 22:08:46 UTC,"Reviewed:  https://review.openstack.org/631355
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=606ce4bc564e8cd1d5da67f0df15c38782327cd4
Submitter: Zuul
Branch:    stable/rocky"
1811713,2019-01-18 19:01:30 UTC,This appears to be an issue with the openstack-selinux package available in rocky.
1811713,2019-01-16 23:48:13 UTC,"I was able to successfully complete undercloud installations, without error, using both Alan's and Alex's workarounds."
1811713,2019-01-17 22:05:33 UTC,"Reviewed:  https://review.openstack.org/631354
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=666573d15b44428856bbfe953ac34458d7219dde
Submitter: Zuul
Branch:    stable/rocky"
1811714,2019-01-15 13:39:31 UTC,Kelvin is looking into this. Marking as critical because if it's replicatable and changed our status --format=yaml output that's a backward compatible issue that would not be ok for 2.5.
1811714,2019-01-16 14:20:28 UTC,We should update status to filter properly. I understand the way it works currently is that we get all storage data but we should update it to filter more appropriately.
1811722,2020-08-20 03:03:19 UTC,"I encounter a Synchronous Exception crash when booting shim with qemu-system-aarch64 on Focal. But on an real aarch64 server this doesn't happen.
Not sure if it is the same issue."
1811722,2020-08-20 07:15:02 UTC,Please open a new bug.
1811722,2020-02-10 14:23:14 UTC,This bug was fixed in the package shim - 15+1552672080.a4a1fbe-0ubuntu1
1811722,2019-01-15 23:18:38 UTC,"There are actually 2 separate bugs. The first is a bug in gnu-efi, triggered by this call in shim's errlog.c:"
1811722,2019-01-15 20:50:37 UTC,Doesn't look like a grub bug anymore. We can set back to New if necessary.
1811722,2019-03-08 05:11:44 UTC,"I've proposed a fix upstream:
  https://github.com/rhboot/shim/pull/173"
1811723,2019-08-15 07:19:24 UTC,Still here in 4.15.0-58-generic #64-Ubuntu SMP
1811723,2019-06-07 17:39:39 UTC,I still have the bug in 4.15.0-51-generic #55-Ubuntu SMP.
1811723,2019-05-31 20:08:22 UTC,"I have tried the 4.18 kernel (see comment 3) and while it seems to fix this samba issue it was no good for my system, unless I of course installed it wrong.  Is there a definitive guide on how to install and choose different kernels for ubuntu?"
1811723,2019-05-31 04:38:56 UTC,According to [1] it's fixed in newer kernel version. Please try it out.
1811723,2019-05-30 12:36:47 UTC,apport information
1811723,2019-05-30 12:36:46 UTC,apport information
1811723,2019-05-30 12:36:45 UTC,apport information
1811723,2019-05-30 12:36:42 UTC,apport information
1811723,2019-05-30 12:36:42 UTC,apport information
1811723,2019-05-30 12:36:44 UTC,apport information
1811723,2019-05-30 12:36:39 UTC,apport information
1811723,2019-01-15 04:20:11 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1811723,2019-01-15 06:31:21 UTC,Selected package to file bug against. Hopefully it is the right one.
1811723,2019-05-30 12:36:40 UTC,apport information
1811723,2019-05-30 12:26:39 UTC,linux-image-4.15.0-50-generic
1811723,2019-05-30 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811723,2019-05-30 12:10:44 UTC,"I found this, https://bugzilla.samba.org/show_bug.cgi?id=13647 , on the Samba bug tracker and the issue seems gone with 4.18 (which brings other issues so I'm back on 4.15)."
1811723,2019-05-30 12:36:35 UTC,apport information
1811723,2019-05-30 12:36:36 UTC,apport information
1811723,2019-05-30 12:36:37 UTC,apport information
1811723,2019-05-30 12:36:38 UTC,apport information
1811723,2019-05-30 12:36:35 UTC,apport information
1811724,2020-08-17 15:28:01 UTC,I have the same message:
1811724,2020-12-14 16:22:17 UTC,hasn't come up in awhile though
1811724,2020-12-14 16:21:22 UTC,Seems to be just the warning in the log for me
1811724,2020-12-14 09:40:50 UTC,Is there anything really failing or is that just a warning in the log?
1811724,2020-12-10 22:19:31 UTC,Still fails
1811724,2020-10-03 18:18:18 UTC,I have something similar:
1811724,2020-05-27 03:15:12 UTC,My system has a raid filesystem present.
1811724,2019-12-01 13:17:20 UTC,Error still exists on Ubuntu 18.04
1811724,2020-05-01 14:18:00 UTC,Confirmed on focal.
1811724,2019-08-17 09:45:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811724,2019-08-17 09:56:23 UTC,"Well, I too am getting these errors, every time I boot up Ubuntu Mate 19.04 x64:"
1811724,2019-09-17 16:36:29 UTC,Confirmed on fresh install of Ubuntu 18.04.3:
1811724,2020-05-27 03:12:40 UTC,Present in 18.04:
1811724,2019-12-12 01:17:25 UTC,apparently Adding libblockdev-crypto2 and libblockdev-mdraid2 will solve this
1811724,2019-12-12 01:15:02 UTC,upgraded from 18.04 to 19.10 and now getting these also
1811724,2020-03-05 19:17:58 UTC,"Ubuntu focal
linux 5.4.0-17-generic x86_64
udisks2 2.8.4-1ubuntu1
libblockdev-crypto2 2.23-2ubuntu3"
1811726,2019-12-18 13:37:32 UTC,"Reviewed:  https://review.opendev.org/666865
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bd2e0972993ffd732cde0a3a6154424e74d44f0a
Submitter: Zuul
Branch:    stable/pike"
1811726,2019-09-27 09:02:51 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1811726,2019-08-19 15:41:20 UTC,This issue was fixed in the openstack/nova 17.0.12 release.
1811726,2019-08-12 21:11:45 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1811726,2019-08-12 20:41:59 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1811726,2019-07-20 02:17:38 UTC,"Reviewed:  https://review.opendev.org/657070
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4adface8b9c1cdb04f9401d4bbd1c2dc795f94a5
Submitter: Zuul
Branch:    master"
1811726,2019-07-04 18:03:49 UTC,"Reviewed:  https://review.opendev.org/666854
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=64d52788831f0e676f0b9bf9780eeadb38232def
Submitter: Zuul
Branch:    stable/rocky"
1811726,2019-07-01 16:25:32 UTC,"Reviewed:  https://review.opendev.org/666840
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e9889be94ee58a6da78ef96d09d8f5282b86f648
Submitter: Zuul
Branch:    stable/stein"
1811726,2019-06-21 15:41:27 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/666874"
1811726,2019-06-21 15:27:22 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/666865"
1811726,2019-06-21 15:11:27 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/666862"
1811726,2019-08-09 17:21:51 UTC,"Reviewed:  https://review.opendev.org/666862
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b2f438bab4a0fdaa37b1a57cff0b27fb2a3f3437
Submitter: Zuul
Branch:    stable/queens"
1811726,2019-06-21 13:52:35 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/666840"
1811726,2019-06-21 08:32:49 UTC,"Reviewed:  https://review.opendev.org/657021
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8921a470ee797cd75def387ce184ee0ffaae6517
Submitter: Zuul
Branch:    master"
1811726,2019-06-21 08:22:16 UTC,"Reviewed:  https://review.opendev.org/657016
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=650fe118d128f09f78552b82abc114bb4b84930e
Submitter: Zuul
Branch:    master"
1811726,2019-05-03 22:05:43 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657070"
1811726,2019-05-03 19:42:41 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657021"
1811726,2019-01-14 22:03:10 UTC,I don't think [3] is doing what you'd expect for cleaning up orphans since it won't return compute nodes records from the database if the API deleted them:
1811726,2019-05-03 19:29:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657016"
1811726,2019-05-03 18:04:44 UTC,Bug 1817833 could be related and my comment 4 might not be accurate if we can't recreate the providers (or fail if they already exist).
1811726,2019-01-14 22:10:18 UTC,Related IRC discussion:
1811726,2019-01-14 22:09:41 UTC,"I'd say this is medium/low severity since we do correlate compute_nodes / resource providers / ironic node resources via the same uuid, which comes from the ironic node uuid, so although we orphan any other ironic node resource providers in this case, if a compute service is managing those compute node records (ironic nodes) anywhere, it should re-use the same resource providers based on the same uuid. The possible downside is if you have the scheduler configured with a low value for limiting placement allocation candidates and placement is reporting resource providers that aren't actually being managed by any compute service - in that case you could get NoValidHost errors."
1811726,2019-01-14 22:06:50 UTC,"FYI, this applies all the way back to Ocata:"
1811726,2019-06-21 14:44:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/666854"
1811726,2019-01-14 22:05:41 UTC,"Re comment 1, in other words, that orphan cleanup code is meant (I think) for cases like the admin deleting ironic nodes via the ironic API so the ironic driver no longer reports them, and nova needs to cleanup the related compute nodes records in the DB (so the admin didn't do anything about deleting the compute service record in the API)."
1811728,2019-01-14 22:19:12 UTC,"Review in progress for https://review.opencontrail.org/48674
Submitter: Michal Clapinski (<email address hidden>)"
1811728,2019-01-30 05:24:57 UTC,"Reviewed:  https://review.opencontrail.org/48674
Committed: http://github.com/Juniper/contrail-vrouter/commit/fd7809ddc09cade6d6ba8f650ff4f87f8e4d8eae
Submitter: Zuul v3 CI (<email address hidden>)
Branch:    master"
1811729,2019-01-15 22:17:01 UTC,"Related IRC discussion about this, note the comments from lyarwood about cryptsetup being flaky in os-brick:"
1811729,2019-01-16 15:32:44 UTC,"Finally got around to looking at the logs here and unfortunately I still can't see anything obvious. The host correctly connects to the iSCSI volume, formats the device and opens it using cryptsetup before it's then attached to the domain by Libvirt."
1811729,2019-12-13 14:16:09 UTC,Bug 1820007 could be related.
1811730,2019-09-19 08:34:38 UTC,This bug was fixed in the package thermald - 1.7.0-5ubuntu5
1811730,2019-09-08 12:57:30 UTC,"Alex, 18.10 is EOL as of the end of July so no fix is planned"
1811730,2019-08-15 16:28:37 UTC,"@Srinivas
It doesn't look too good on thermald 1.9 until dptfxtract is used."
1811730,2019-09-08 06:05:21 UTC,Is there any chance this fix will be available for 18.10 as well?
1811730,2019-09-03 06:39:30 UTC,"Verified on Thinkpad T495s and an old X1 Carbon, both work fine."
1811730,2019-08-16 12:12:47 UTC,"That was tested on 4.15, which is the default kernel in ubuntu 18.04.
When tested on 5.3rc4, without dptfxtract seems to be good enough [1],
although after using dptfxtract, the system is more consistent [2].
So do you suggest users to always have dptfxtract installed? It shouldn't
make the system perform worse, am I right?"
1811730,2019-08-15 17:43:49 UTC,"Hello Pablo, or anyone else affected,"
1811730,2019-08-15 16:41:05 UTC,"Correct.
I think you are using with 5.3 kernel or using workaround option.
Without dptfxtract output or user manually created thermal-conf.xml or
using aurogenerated, this is risky to play with power as the skin will
hit limit."
1811730,2019-08-15 15:20:17 UTC,"Hi,
Is this issue reproducible in the latest thermald 1.9 release? If yes, I want to fix ASAP."
1811730,2019-08-08 15:54:14 UTC,A test package has been built in https://launchpad.net/~anthonywong/+archive/ubuntu/for-review?field.series_filter=bionic for testing.
1811730,2019-08-13 18:25:43 UTC,"Oops, typos:"
1811730,2019-08-15 12:12:57 UTC,The commit pointed out by Colin can fix the build failure on i386. This is the new debdiff.
1811730,2019-01-23 12:30:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811730,2019-08-08 15:47:41 UTC,debdiff against thermald 1.7.0-5ubuntu2 in Bionic.
1811730,2019-08-08 16:25:56 UTC,"The attachment ""debdiff.patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1811730,2019-01-14 23:05:04 UTC,Seems similar (but probably not the same): https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1769236
1811730,2019-08-13 17:59:05 UTC,"Hello Pablo, or anyone else affected,"
1811730,2019-08-13 18:03:10 UTC,"Let's use the ""block-proposed"" tag to indicate that this needs a longer period of time for verification. When you think its baked long enough please remove the tag."
1811730,2019-08-13 18:25:06 UTC,Looks like the i386 build failed:
1811730,2019-08-08 16:55:14 UTC,I've sponsored this and uploaded it to -proposed.
1811732,2019-01-15 00:10:31 UTC,"StacktraceTop:
 xdgSearchableConfigDirectories (handle=0x7ffef66afbf8) at basedir.c:628
 xdgConfigOpen (relativePath=relativePath@entry=0x55821d9ef313 ""dunst/dunstrc"", mode=mode@entry=0x55821d9efbac ""r"", handle=handle@entry=0x7ffef66afbf8) at basedir.c:675
 load_settings (cmdline_config_path=0x0) at src/settings.c:95
 dunst_main (argc=1, argv=0x7ffef66afdb8) at src/dunst.c:140
 __libc_start_main (main=0x55821d9e4e00 <main>, argc=1, argv=0x7ffef66afdb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffef66afda8) at ../csu/libc-start.c:308"
1811732,2019-03-14 07:41:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811735,2019-02-27 19:40:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811735,2019-02-27 19:47:15 UTC,Server install of Ubuntu 18.04:
1811738,2019-01-15 03:16:23 UTC,3d export does not yet support bezier curves.  3d-viewer does.
1811758,2019-01-15 06:49:50 UTC,"To be clear, the problem with using /dev/urandom as a backend is that it's possible to feed data from an uninitialized pool into the guest."
1811758,2019-04-17 16:54:59 UTC,"Yes, using getrandom() in qemu by default on systems that support it will be an improvement, and is the right approach."
1811758,2019-11-13 09:34:49 UTC,rng-builtin is the new RNG default backend for virtio-rng and is based on getrandom().
1811758,2019-04-16 02:16:33 UTC,"any word on this?  If this is not considered for adoption, i would like to know the reason, so that we can have better predictions about what to do for entropy in a QEMU system."
1811758,2019-04-16 05:37:26 UTC,"Feel free to send some patches to implement this! Alternatively, you could also try to write a mail to the virtio-rng maintainer (see the MAINTAINER file in the top directory of the sources), maybe he can help."
1811763,2019-01-26 15:39:43 UTC,"Well, without a file or at least the first lines of your file, no analysis possible."
1811763,2019-03-01 12:28:32 UTC,"you can send me a sample file (maybe an example file provided by your bank) at the email at the bottom of this page http://homebank.free.fr/en/support.php, not to expose the file into this case."
1811763,2019-03-30 22:42:46 UTC,might be related to #1822436
1811763,2019-05-30 04:17:33 UTC,[Expired for HomeBank because there has been no activity for 60 days.]
1811768,2019-01-15 07:38:48 UTC,See https://gitlab.com/mailman/mailman/issues/31 (alsp LP: #883193).
1811769,2019-07-18 12:55:19 UTC,@cinghu
1811776,2019-07-18 09:28:44 UTC,This issue should be fixed now in the --edge version.
1811776,2019-01-16 02:42:31 UTC,"u@u-Precision-5820-Tower:~$ sudo qabro.lspci
lspci: Cannot open /sys/bus/pci/devices/0000:00:03.0/resource: No such file or directory"
1811776,2019-01-16 09:39:45 UTC,"Searching around, I found another user of this device had the same issue with lspci:"
1811777,2019-03-06 10:49:37 UTC,This bug was fixed in the package linux - 4.18.0-16.17
1811777,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1811777,2019-01-15 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811777,2019-02-11 11:06:22 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1811777,2019-01-17 06:29:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1811777,2019-03-01 05:01:27 UTC,This is the final reminder to please verify that the kernel in -proposed resolves the issue for which you've filed this bug report.   Canonical is planning to release these kernels early next week.   Thank you in advance!
1811778,2019-03-19 13:22:51 UTC,Is this still an issue?
1811778,2019-03-19 18:32:22 UTC,"YES, lots of warnings and this tickets is unlikely to be addressed very soon."
1811785,2019-09-18 15:34:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811785,2019-12-05 12:09:08 UTC,Tested latest kernel 4.15.0-72-generic on bionic.
1811785,2019-11-25 16:36:06 UTC,TODOs in this bug:
1811785,2019-11-25 16:33:40 UTC,The kernel issue pointed at the github was solved by:
1811785,2019-11-23 00:56:05 UTC,"Hello Torel and Juliet,"
1811785,2019-11-23 00:39:27 UTC,A PPA containing the fixes (Disco and Bionic) will be available here:
1811785,2019-11-23 00:11:06 UTC,It fixes an issue introduced by :
1811785,2019-11-23 00:06:48 UTC,libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host (256 byte) labels
1811785,2019-09-26 09:33:29 UTC,Needed --no-autolabel to get it working. New ndctl didn't help. Which is nice as I didn't have to interrupt metadata operations of the servers with nvdimm's.
1811785,2019-02-12 09:25:34 UTC,Everything is explained in the ndctl issue 78.
1811785,2019-01-15 10:22:48 UTC,apport information
1811785,2019-01-18 11:05:59 UTC,"In case anybody else runs into this issue, here's some things you could do :"
1811785,2019-01-15 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811785,2019-01-15 10:22:38 UTC,apport information
1811785,2019-01-15 10:22:39 UTC,apport information
1811785,2019-02-06 15:28:29 UTC,Missing Kernel Fix?
1811785,2019-01-15 10:22:41 UTC,apport information
1811785,2019-01-15 10:22:40 UTC,apport information
1811785,2019-01-15 10:22:43 UTC,apport information
1811785,2019-01-15 10:22:44 UTC,apport information
1811785,2019-01-15 10:22:45 UTC,apport information
1811785,2019-01-15 10:22:47 UTC,apport information
1811785,2019-01-15 10:22:42 UTC,apport information
1811791,2019-01-30 06:32:33 UTC,"Hi Hongbin,
I have used  Ubuntu18.04 und Rocky:
https://docs.openstack.org/project-deploy-guide/kolla-ansible/rocky/quickstart.html
And
https://docs.openstack.org/kolla-ansible/rocky/reference/zun-guide.html"
1811791,2019-02-04 00:23:57 UTC,Here is my zun settings to use websocket for cloud shell.
1811791,2019-02-02 02:00:03 UTC,"The best guess I can make is that some ports are not open. In particular, the port 6784 is the zun websocket proxy port. The browser will use that port to connect to the container's shell."
1811791,2019-02-01 20:43:20 UTC,"Hi Hongbin,
with Ubuntu 16.04 und master Release Zun_ui is working,
but Cloud Shell on the UI or Browser is don't working fine,
still waiting the terminal prompt. Look the screenshot attached."
1811791,2019-01-26 21:54:57 UTC,"Hi PrinzElvis,"
1811791,2019-01-17 06:29:38 UTC,I found this too in # tail -f /var/log/kolla/horizon/horizon.log
1811791,2019-01-17 03:45:10 UTC,"@PrinzElvis, thanks for providing the detailed information. It looks there are two issues there. One is the cloud shell issue, the other is the pull image issue. This bug is confirmed."
1811791,2019-01-16 21:30:17 UTC,"Pull Image  with UI is not possible and I can not also select Host ""Select host that stores the image""
But on CLI is possible:"
1811791,2019-01-16 07:33:53 UTC,"This error only happened in the UI/cloud shell.
CLI is working fine."
1811791,2019-01-16 04:06:20 UTC,"Hi @PrinzElvis,"
1811791,2019-01-16 04:06:48 UTC,s/Doesn't/Does/
1811791,2019-01-23 16:20:09 UTC,"Note: according to the feedback from IRC, https://review.openstack.org/#/c/631556/ doesn't fix the problem. I will find another time to look into it."
1811795,2019-05-13 10:18:26 UTC,"Thanks Mariusz!
Since this verification needs special HW which at least I currently have none of - do you see a chance to also do the verification for cosmic-proposed? Lacking that it can't be really released for Bionic as it would then become an upgrade-regression."
1811795,2019-05-20 09:20:46 UTC,"The verification of the Stable Release Update for mdadm has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1811795,2019-05-20 09:20:38 UTC,This bug was fixed in the package mdadm - 4.1~rc1-3~ubuntu18.04.2
1811795,2019-05-20 09:20:27 UTC,This bug was fixed in the package mdadm - 4.1~rc1-4ubuntu1.1
1811795,2019-05-16 09:06:37 UTC,"Hi,"
1811795,2019-05-13 09:37:24 UTC,"Hi,
the issue is fixed in bionic-proposed."
1811795,2019-05-09 14:50:10 UTC,"Hello Mariusz, or anyone else affected,"
1811795,2019-05-09 14:28:43 UTC,"Hello Mariusz, or anyone else affected,"
1811795,2019-04-23 08:12:24 UTC,Thanks for the real test steps and checking them Mariusz.
1811795,2019-04-19 10:22:11 UTC,"Hi,
Here test steps:
1. Create IMSM Container:
    mdadm -CR imsm0 -e imsm -n 2 /dev/sd[bc]
2. Create IMSM level 0 Array:
    mdadm -CR vol0 -l 0 -n 2 /dev/sd[bc]
3. Wait for resync to complete
   mdadm --wait /dev/md/vol0
4. Read /proc/mdstat and check /dev/md/ directory
   cat /proc/mdstat
   ls /dev/md/
5. Fail one disk incrementaly (simulate device disappearing from system)
   mdadm -If sdc
6. Check mdstat file and /dev/md/
   cat  /proc/mdstat
   ls /dev/md/
Result:
   After disk fail [5] raid 0 array should disappear from mdstat, link /dev/md/imsm0 should  exist."
1811795,2019-04-10 14:44:45 UTC,Incomplete waiting for PAP verification and better test steps
1811795,2019-04-10 14:43:03 UTC,"Hi,
I need your help in testing this.
I have created a PPA [1] with the fixes for this issue, but I lack a IMSM HW."
1811795,2019-04-08 05:04:28 UTC,"Hi,
It is fixed in 19.04 (mdadm there is 4.1).
Any chances to include the fix in 18.04 LTS?"
1811795,2019-01-30 15:44:18 UTC,"Yes, Bionic"
1811795,2019-01-30 14:55:31 UTC,"The fix is in 4.1 which is released into Ubuntu 19.04 already
There are 4.1~rc1 based versions in 18.04 and 18.10 which do not contain the fix."
1811795,2019-01-30 14:33:49 UTC,"Hi,
Are there any update on this one?"
1811795,2019-01-30 14:33:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811795,2019-01-15 10:49:17 UTC,"Fixed in upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cb8f5371352f6c16af5aab8a40861e13aa50fc2b"
1811798,2019-02-04 13:07:52 UTC,"(In reply to Andreas Krebbel from comment #14)

> (In reply to Jakub Jelinek from comment #11)
> > ... Can't what you are doing in the splitters be done in
> > define_peephole2 instead?
>
> Not that easy unfortunately.  peephole2 will run after reload. So the FP
> constant ok 0.0 will already be reloaded into a register first or pushed
> into literal pool. The point of doing the transformation is to avoid this.
"
1811798,2019-02-05 15:23:51 UTC,I'll commit a patch which just removes the splitter for now. I'll try to come up with a nicer testcase.
1811798,2019-02-05 15:26:07 UTC,"(In reply to Andreas Krebbel from comment #16)

> I'll commit a patch which just removes the splitter for now. I'll try to
> come up with a nicer testcase.
"
1811798,2019-02-05 17:14:43 UTC,"Author: krebbel
Date: Tue Feb  5 17:14:11 2019
New Revision: 268550"
1811798,2019-02-04 12:59:43 UTC,"(In reply to Jakub Jelinek from comment #11)

> ... Can't what you are doing in the splitters be done in
> define_peephole2 instead?
"
1811798,2019-02-05 17:19:58 UTC,"Author: krebbel
Date: Tue Feb  5 17:19:26 2019
New Revision: 268552"
1811798,2019-02-05 18:23:46 UTC,"(In reply to Jakub Jelinek from comment #17)

> (In reply to Andreas Krebbel from comment #16)
> > I'll commit a patch which just removes the splitter for now. I'll try to
> > come up with a nicer testcase.
>
> All 3 s390 splitters that do this?
"
1811798,2019-02-06 16:33:40 UTC,"What we could do there is remove the first of those two splitters, remove the
&& !dead_or_set_p (insn, operands[1])
test from the second, and add peephole2 that would transform
   (set (access part 1) (subreg:SI (match_dup 1) low))
   (set (match_dup 1) (rotate:DI (match_dup 1) (const_int 32)))
   (set (access part 2) (subreg:SI (match_dup 1) low))
with a lshiftrt instead of rotate if reg 1 is dead after the third insn (assuming rotate is more expensive as right shift, if it is the same expensive/same size, then having the two splitters makes no sense).  The last rotate should have been removed by DCE already if it was truly dead (though, of course, if it for some reason isn't yet, you could have another peephole2 for that too)."
1811798,2019-02-06 16:34:42 UTC,"That said, the regression is fixed now."
1811798,2019-02-05 17:17:32 UTC,"Author: krebbel
Date: Tue Feb  5 17:17:00 2019
New Revision: 268551"
1811798,2019-02-01 19:43:38 UTC,"> Segher on IRC says that removing REG_DEAD notes that aren't valid is the
> right thing, so paging others what they think.
"
1811798,2019-02-01 17:46:52 UTC,"The r265193 patch was found via reghunt. However, it just reveals an underlying issue."
1811798,2019-02-01 18:07:00 UTC,"So, to me this looks like a backend bug, using dead_or_set_p in a splitter when the split passes don't really compute the note problem.  Seems s390 is the only backend that does this, other backends use dead_or_set_p either only in peephole2s (which is fine, peephole2 pass starts with
  df_set_flags (DF_LR_RUN_DCE);
  df_note_add_problem ();
  df_analyze ();
and even when many targets don't use df_or_set_p, they do use peep2_dead*), or (cris) in delayed branch scheduling (I believe that doesn't guarantee that either).  Can't what you are doing in the splitters be done in define_peephole2 instead?"
1811798,2019-02-01 17:59:46 UTC,"I admit I have just a vague recollection of this, but I thought since df has been added, usually if a pass wants REG_DEAD notes, it needs to df_note_add_problem () and df_analyze should rebuild the REG_DEAD/REG_UNUSED notes."
1811798,2019-02-01 17:50:35 UTC,"Created attachment 45588
experimental patch"
1811798,2019-02-01 17:23:47 UTC,"gfortran -O3 -march=zEC12 -funroll-loops -fpie qrsolv-reduc.f -c
gcc qrsolv-caller.c -c
gcc qrsolv-caller.o qrsolv-reduc.o -o t"
1811798,2019-02-01 17:17:03 UTC,"Created attachment 45587
A C wrapper to call the qrsolv function in the fortran snippet"
1811798,2019-02-01 17:16:24 UTC,"Created attachment 45586
qrsolv-reduc.f   the miscompiled fortran file autoreduced from scipy"
1811798,2019-01-28 10:00:41 UTC,I'm able to reproduce the problem now and will try to have a look.
1811798,2019-01-17 10:17:36 UTC,I've tried building scipy 1.1.0 from github on a Fedora installation. The build already uses -funroll-loops. But I couldn't reproduce the problem with the resulting binary.
1811798,2019-01-16 11:56:13 UTC,"Yeah, like that problematic source, all gfortran options used to compile that, any needed modules too + stubbed whatever it calls and whatever is needed in MAIN__ or main to reproduce, ideally with minimal dependencies.
If you know the exact problematic routine, see in the debugger how many times it is called and in which invocation of the routine it misbehaves and try to capture on which arguments it is called.  If you don't know the exact problematic routine, one can e.g. play with assembly bisection between -funroll-loops and no -funroll-loops, rename .L* labels in one of them so that it can be merged by hand more easily.  I think gfortran doesn't have optimize (0) attribute yet."
1811798,2019-01-15 13:37:23 UTC,I guess we need something better than a python testcase.
1811798,2019-01-15 11:58:06 UTC,"seen when build scipy on s390x with the current GCC 8 branch.  According to the Debian report [1] this is tracked down to miscompilation of one Fortran file with -funroll-loops. The Ubuntu report [2] has a ""standalone"" python test case."
1811798,2019-02-01 19:29:07 UTC,"Segher on IRC says that removing REG_DEAD notes that aren't valid is the right thing, so paging others what they think."
1811799,2019-01-15 11:15:18 UTC,I think this is an actual issue with non-RBAC MAAS too.
1811799,2019-01-15 12:38:20 UTC,"Yes, this is an issue with non-RBAC as well. That's why I didn't mention RBAC here."
1811802,2019-01-15 15:42:55 UTC,https://github.com/CanonicalLtd/netplan/pull/67
1811805,2019-04-18 18:53:00 UTC,same in stein
1811805,2019-04-25 09:30:11 UTC,Could you provide more information? Logs of the failure? Investigation into why the network nodes cannot be accessed with the containers running?
1811805,2019-04-25 09:31:39 UTC,Now it works in stein after some updates of the containers running in the network node
1811807,2019-01-15 12:00:08 UTC,This change was made by a bot.
1811807,2019-01-25 03:00:37 UTC,We do not enable fingerprint reader for OEM projects. From what I see this is more a lack of support in libfprint. There is someone who is working on reverse engineering the protocol so that it works in libfprint:
1811808,2019-01-23 02:30:17 UTC,"It doesn't take any effort if you use the default Gnome Shell, which is a compositing window manager already."
1811808,2019-01-22 23:19:25 UTC,"Ok, thanks; I guess I'll live with the tearing for now, then. I agree that it seems a bit pointless/unlikely to spend time fixing this given most people won't run into it now that compositors are so common."
1811808,2019-01-22 06:30:45 UTC,"Come to think of it, one probably could modify some combination totem/cogl/clutter to avoid tearing in old-style non-compositing window managers. But that's unlikely to ever get done considering Ubuntu has been defaulting to compositing window managers for some years now (Unity/Compiz, Gnome Shell)."
1811808,2019-01-22 02:39:11 UTC,Thanks Josh.
1811808,2019-01-21 21:49:08 UTC,"> Does using a Wayland session avoid the bug?
"
1811808,2019-01-21 02:39:24 UTC,Thanks.
1811808,2019-01-21 02:40:55 UTC,"Also, what shell are you using?"
1811808,2019-01-18 01:50:09 UTC,Thanks for those files. I can see two possible problems (which may not be problems but should be checked):
1811808,2019-01-16 02:24:32 UTC,Thanks for the detailed bug report. That jagged black tearing is the result of unsynchronized nonlinear buffers being used on screen.
1811808,2019-01-17 22:35:22 UTC,"This Xorg.1.log was last modified in November, so I'm unsure if it's relevant."
1811808,2019-01-17 22:27:00 UTC,"I don't have an /etc/X11/xorg.conf, but I do have (along with the various distribution-provided files) a /usr/share/X11/xorg.conf.d/99-custom.conf."
1811808,2019-01-17 22:21:54 UTC,"Unfortunately, the BIOS doesn't have an option to disable the Nvidia GPU."
1811808,2019-01-17 02:07:46 UTC,Thanks.
1811808,2019-01-16 12:22:33 UTC,Removing gstreamer1.0-vaapi doesn't appear to help.
1811808,2019-01-18 12:42:05 UTC,"I'm using only one monitor (the one built-in to the laptop), at times I use an external monitor as well, but this problem persists without it plugged in."
1811808,2019-01-16 02:25:26 UTC,5. Please also run 'lspci -k' and send us the output.
1811810,2019-10-14 08:45:52 UTC,"Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help posting your problem in the support forum of your local Ubuntu's community http://loco.ubuntu.com/ or asking at http://askubuntu.com. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs."
1811817,2019-08-05 05:32:20 UTC,The following worked for me:
1811817,2020-01-22 08:35:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811817,2020-01-22 08:51:06 UTC,"I did download the weex_2.8.3+b1_amd64.deb package from debian and extract the executable into /usr/local/bin/weex - that works too, including SSL - will that mean, ubuntu will get a working weex package some time automagically?"
1811819,2019-10-14 12:39:44 UTC,This bug was fixed in the package linux-kvm - 5.3.0-1003.3
1811819,2019-10-04 09:56:34 UTC,This bug was fixed in the package linux-kvm - 5.0.0-1019.20
1811819,2019-09-05 02:56:10 UTC,"Hi Jeffrey,
This should be available in the end of September (next kernel release)
Thanks"
1811819,2019-09-03 00:56:50 UTC,Just curious on an update of when this should be available in the apt repositories? Thanks!
1811819,2019-09-30 22:04:32 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1047.47
1811819,2019-08-17 00:38:19 UTC,"Both of those, B and D, are confirmed to work."
1811819,2019-07-01 03:48:47 UTC,"Hello,"
1811819,2019-08-06 02:37:18 UTC,"Hello,
can you give the kernel in comment #1 a try?
Thanks"
1811819,2019-08-19 06:17:26 UTC,"Thanks again! Jeffrey.
I have submit the SRU request:
https://lists.ubuntu.com/archives/kernel-team/2019-August/103191.html"
1811819,2019-08-15 11:20:26 UTC,"Hi Jeffery,
thanks for the test, sure this can be enabled on Bionic 4.15 (and newer for the future releases) as well.
I will build a test kernel tomorrow for you to test."
1811819,2019-08-16 10:04:31 UTC,"Please give the B/D KVM kernel here a try:
https://people.canonical.com/~phlin/kernel/lp-1811819-vxlan/B
https://people.canonical.com/~phlin/kernel/lp-1811819-vxlan/D"
1811819,2019-08-15 00:53:04 UTC,I just tried this on a ubuntu cloud 18.04.3 VM and it works. Could this get foreported to the 4.15.x kernels as well?
1811826,2019-02-11 11:57:28 UTC,"I've tried to reproduce this error using AIO on a ubuntu 16.04 on a vagrant machine and have been unable to reproduce it. Libpython exists within my containers base image and seems to be installed without fault. Octavia seems to run fine. If you have any other info to help reproduce please let me know.
I was looking at /var/lib/machines/ubuntu-xenial-amd64/var/log/apt/history.log on the host for libpython2.7 and checked it was installed through dpkg -l libpython* on the octavia container."
1811826,2019-02-13 09:48:39 UTC,"Marking this as incomplete - we need further verification in the originial environment that libpython was missing in the container base image, and therefore also missing in the octavia container."
1811826,2019-02-25 09:53:16 UTC,"i can indeed see, in the apt log file you reference that there was an installation for libpython2.7"
1811857,2019-01-24 04:17:42 UTC,"3.13.0-165.215~precise1 - generic
Regression test CMPL, RTB."
1811857,2019-02-04 22:01:00 UTC,All tasks have been completed and the bug is being set to Fix Released
1811861,2020-06-24 04:20:05 UTC,"Thanks for clarifying, closing."
1811861,2019-01-15 15:46:11 UTC,"Actually, it looks like this is already fixed in cosmic. Can this be ported to bionic as well?"
1811861,2019-01-16 13:24:06 UTC,"Sorry for the noise, it seems this is not related to rsyslog after all. In our install process we are moving /var/log to another partition (mounted in /data/) and then symlink it to /var/log. Permissions are set up properly and work while the system is running. When the system is rebooted though there is an unknown process changing the permissions of /data/log, my best guess something related to systemd."
1811862,2021-01-19 06:56:29 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1811862,2021-01-25 08:47:06 UTC,This is fixed in 5.2.
1811863,2019-01-16 02:42:33 UTC,According to your XorgLog.txt it looks like the choice of 75Hz is coming from the AMDGPU driver:
1811863,2019-01-17 10:54:16 UTC,The monitor works fine when plugged in the Nvidia GPU or when booting the same hardware in Windows 10.
1811863,2019-03-19 04:17:27 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1811863,2019-03-19 04:17:29 UTC,[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.]
1811863,2019-03-19 07:37:48 UTC,"I have the flickering problem with 2560x1440 screens, AMD Radeon RX 550.
tried it on two screens: asus and samsung. asus is capable of freesync, samsung not. asus can handle higher frequency, samsung 50Hz only."
1811867,2019-11-08 18:32:52 UTC,"Reviewed:  https://review.opendev.org/693424
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=c74ce0fbdf81996331d7bddd259e15492ce7ee1d
Submitter: Zuul
Branch:    master"
1811867,2019-04-11 00:58:51 UTC,Regarding:  2. Is this configuration possible (mix 18.04 and 16.04 nova compute hosts)?
1811867,2019-04-11 00:51:14 UTC,The ceph-mon and ceph-osd charms should be updated to latest stable charm revs before taking on a migration or payload upgrade task.  We should make the docs explicit about that.
1811867,2019-04-10 22:33:18 UTC,"This is ultimately caused due to having a new ceph-mon charm that supports expected-osd-count, and your ceph-osd charm either not reporting, or not correctly reporting, the number of OSDS bootstrapped.  This prevents the ceph-mon charm from being ready to hand out auth tokens."
1811867,2019-11-07 20:29:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/693424"
1811869,2019-01-16 00:47:02 UTC,apport information
1811869,2019-01-16 00:46:58 UTC,apport information
1811869,2019-01-16 00:46:55 UTC,apport information
1811869,2019-01-16 00:46:53 UTC,apport information
1811869,2019-01-16 00:46:50 UTC,apport information
1811869,2019-01-16 00:46:51 UTC,apport information
1811869,2019-01-16 00:46:46 UTC,apport information
1811869,2019-01-16 00:46:45 UTC,apport information
1811869,2019-01-16 00:46:43 UTC,apport information
1811869,2019-01-16 00:46:42 UTC,apport information
1811869,2019-01-16 00:46:40 UTC,apport information
1811869,2019-01-16 00:46:38 UTC,apport information
1811869,2019-01-16 00:46:48 UTC,apport information
1811869,2019-01-15 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811870,2020-10-12 10:22:38 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/631038
Reason: No longer applies to master. Stable-only change proposed at https://review.opendev.org/#/c/757524/"
1811870,2020-10-12 09:58:11 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/757524"
1811870,2019-01-15 21:43:11 UTC,"setting this to high as while  people generally dont use expcit small pages this was
considerd sevear enough to include in a redhat security update for libvirt."
1811881,2019-01-16 12:16:18 UTC,"Hi Steffen,"
1811881,2019-04-19 17:35:36 UTC,Is there any update on this.  I don't see any images for EKS 1.11 or 1.12 yet?
1811881,2019-05-21 20:04:22 UTC,ubuntu 1.11 images have been added this ticket can be closed. https://cloud-images.ubuntu.com/docs/aws/eks/
1811886,2020-03-19 18:15:59 UTC,"I'm not saying it's a good thing, but this is what we do already if you forget about page sizes. See [1]. We're simply not considering hugepages when we should be."
1811886,2020-03-17 21:59:50 UTC,"> # Test C, pinned, implicit small pages, oversubscribed
>
> This should fail because we don't allow oversubscription with CPU pinning.
>
>     $ openstack flavor create --vcpu 2 --disk 0 --ram 7168 test.pinned
>     $ openstack flavor set test.pinned --property hw:cpu_policy=dedicated
>
>     $ openstack server create --flavor test.pinned --image cirros-0.3.6-x86_64-disk --wait test1
>     $ openstack server create --flavor test.pinned --image cirros-0.3.6-x86_64-disk --wait test2
>
> Expect: FAILURE
> Actual: SUCCESS
"
1811886,2020-03-17 22:06:38 UTC,"Continuing from comment #5 - with an explicit instance page size, we don't allow oversubscription, so is that why we don't want oversubscription with an implicit page size either?"
1811886,2019-01-16 15:10:08 UTC,"> # Test C, pinned, implicit small pages, oversubscribed
> This should fail because we don't allow oversubscription with CPU pinning.
"
1811886,2019-01-16 14:42:48 UTC,"@Stephen, you test those without the patch https://review.openstack.org/#/c/629281/, right?"
1811886,2019-01-15 19:20:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/631053"
1811886,2019-01-24 15:26:38 UTC,"> @Stephen, you test those without the patch https://review.openstack.org/#/c/629281/, right?
"
1811889,2019-01-19 21:27:50 UTC,Found more info.
1811889,2019-03-14 14:31:08 UTC,Fix available in kubernetes-worker 490 and kubernetes-master 623.
1811889,2019-01-29 10:14:40 UTC,Fix the problem with following steps.
1811889,2019-01-19 21:31:26 UTC,Below are the daemon.json and startup config file. Thank you so much for your help!
1811889,2019-01-19 20:15:46 UTC,"Hi Joseph,"
1811889,2019-01-16 20:37:07 UTC,Hi Joseph~
1811889,2019-01-17 03:34:04 UTC,"Hi Joseph,"
1811889,2019-01-16 18:45:31 UTC,"Hi Yen, I pushed a fix for the nvidia-docker2 issue you're seeing: https://github.com/juju-solutions/layer-docker/pull/130/files"
1811889,2019-01-16 17:49:35 UTC,"Tried reply once again with version 1.12
#juju deploy cs:bundle/kubernetes-core-502"
1811889,2019-01-16 07:29:17 UTC,"By the way, I forgot to mention I deploy this bundle on my on prem servers. They are Dell r720s."
1811889,2019-01-15 21:43:29 UTC,"Hi Joe,"
1811889,2019-01-15 20:08:50 UTC,"Hi Yen,"
1811889,2019-01-17 14:08:55 UTC,"No problem Yen, thanks for your feedback."
1811893,2020-04-16 02:12:00 UTC,"Thanks for reporting this bug.  This looks to be a bug with either xubuntu login manager or xubuntu default X11 session, so I'm reassigning it to lightdm."
1811896,2019-01-15 23:32:11 UTC,"I can't really say that the mcclim thingy is totally surprising, I had
known about the class of problems that it might cause at the time, and
reversed a test case not from mcclim but from sbcl code. So it can't
be said that it was some obscure interaction of intermingling parts,
just a lapse of concentration."
1811896,2019-01-17 13:57:37 UTC,"The compiler has about 57K lines.  Of that, maybe 45K could be mutated.  At 2 min/build (say) this would be two months to build with one mutant per line.   So this doesn't seem entirely absurd as an ongoing project.  It would help if I had coverage information on the compiler so I could know which parts are not being touched by tests."
1811897,2019-01-15 21:53:36 UTC,I guess this might also apply to the metadefs?
1811898,2019-09-12 17:15:37 UTC,"I just tried testing this bug again on this sandbox:
https://bugsquash.mobiusconsortium.org/eg/staff"
1811898,2019-09-26 20:28:40 UTC,Fix rolled into https://bugs.launchpad.net/evergreen/+bug/1845556
1811898,2019-08-16 06:26:13 UTC,There was some commenting junk in this that I fixed. It's ready for testing.
1811898,2019-09-13 18:52:11 UTC,"Chrisy, I don't think Adam's latest patch has been installed on the bug squashing sandbox (unless a request went directly to Blake that I didn't see?) so I would expect to still see the error there."
1811898,2019-04-09 18:44:03 UTC,"I (finally) found the same phenomena in our catalog, but I have to go 8 digits past the decimal before it triggers the erroneous call number label. We generally have a policy that our call numbers only go 7 digits past the decimal. In OCLC Connexion, we can get a call number like:
KR
929
.1072042
G226g"
1811898,2019-03-07 02:00:04 UTC,Confirmed.  Evergreen 3.1.6
1811898,2019-02-28 15:52:03 UTC,https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=9e338b98e7ee8cf9a065d8a4e1ffba395bbaf62d
1811898,2019-05-14 14:40:20 UTC,"Thanks for the branch, Adam.  I noticed that you changed the permissions on Open-ILS/web/js/ui/default/staff/cat/printlabels/app.js.  Is there a specific reason for this?  If not, could you please change the permissions back for consistency purposes?  Thanks!"
1811898,2019-01-15 22:39:17 UTC,Bug report for inability to edit identical call numbers separately is https://bugs.launchpad.net/evergreen/+bug/1811899
1811899,2019-09-26 20:28:29 UTC,Fix rolled into https://bugs.launchpad.net/evergreen/+bug/1845556
1811899,2019-08-29 15:26:45 UTC,Removed signoff and pullrequest. Adam Bowling is reworking the approach and will update.
1811899,2019-03-07 05:42:52 UTC,"NOTE: These changes do not incorporate the call number sorting and long call number fixes in the bugs #1775870 and #1811898, respectively. The final code for testing should put those two bug fixes and this in the same commit."
1811899,2019-03-07 01:37:14 UTC,Confirmed.  Webclient 3.1.6
1811899,2019-03-08 17:38:08 UTC,Tested on PINES servers successfully.
1811901,2019-03-08 05:11:29 UTC,"I've proposed a fix upstream:
  https://github.com/rhboot/shim/pull/174"
1811901,2020-02-10 14:23:14 UTC,This bug was fixed in the package shim - 15+1552672080.a4a1fbe-0ubuntu1
1811904,2019-08-04 02:09:08 UTC,"Reviewed:  https://reviews.mahara.org/10237
Committed: https://git.mahara.org/mahara/mahara/commit/23f135e6aaee9f75859cc41c76c20edf62d5bbe6
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-08-04 02:07:11 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10237"
1811904,2019-07-31 21:48:06 UTC,"Reviewed:  https://reviews.mahara.org/10152
Committed: https://git.mahara.org/mahara/mahara/commit/0a9c93569d03777a7397ef9160969b7afd9fb721
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-10 10:45:38 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10152"
1811904,2019-07-09 03:53:53 UTC,"Reviewed:  https://reviews.mahara.org/10150
Committed: https://git.mahara.org/mahara/mahara/commit/e2901f9c7c7f9edc1729cef5d34fbbe71bb8ce0d
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-09 03:52:51 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10150"
1811904,2019-07-09 02:09:49 UTC,"Reviewed:  https://reviews.mahara.org/10101
Committed: https://git.mahara.org/mahara/mahara/commit/045ab473849444ec31e633b0055b6c38528acab1
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-09 02:09:50 UTC,"Reviewed:  https://reviews.mahara.org/9975
Committed: https://git.mahara.org/mahara/mahara/commit/3b8810105c03a38783bd416840fade56649f3120
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-09 02:09:50 UTC,"Reviewed:  https://reviews.mahara.org/9984
Committed: https://git.mahara.org/mahara/mahara/commit/7b9529647e8cfd4243762599fac5dbd7ae9664d5
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-09 02:09:50 UTC,"Reviewed:  https://reviews.mahara.org/9994
Committed: https://git.mahara.org/mahara/mahara/commit/e84165b0292037a851d05a3673f6060242b0b66a
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-09 02:09:50 UTC,"Reviewed:  https://reviews.mahara.org/10005
Committed: https://git.mahara.org/mahara/mahara/commit/c3479dc655284801802add1848d6c6fcb7be41f8
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-09 02:09:50 UTC,"Reviewed:  https://reviews.mahara.org/9987
Committed: https://git.mahara.org/mahara/mahara/commit/7db2c719a27b3ef963274c81bc1145c3669f6c9d
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-09 02:09:50 UTC,"Reviewed:  https://reviews.mahara.org/9988
Committed: https://git.mahara.org/mahara/mahara/commit/4b16a73fad28ffce634a5281b2c5656845ac69c5
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-07-09 02:09:51 UTC,"Reviewed:  https://reviews.mahara.org/9968
Committed: https://git.mahara.org/mahara/mahara/commit/90e4d5d7d9eb475fc3550a3d2556134193567263
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1811904,2019-06-26 20:13:51 UTC,TITLE:  Admin overview page displays incorrect icon for Web services and Manage groups sections
1811904,2019-06-26 20:12:27 UTC,TITLE:  Legal page when viewed when not logged in is not displayed with correct icon
1811904,2019-01-22 03:49:37 UTC,"There are a lot of changes from v4 to v5, it's not as simple as changing the lib files."
1811904,2019-05-07 01:01:36 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9968"
1811904,2019-05-08 00:44:23 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9975"
1811904,2019-05-08 06:28:50 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9981"
1811904,2019-06-26 20:12:58 UTC,TITLE:  Portfolio Page in Edit mode does not display most icons for the Content type chooser (located left side of page)
1811904,2019-05-09 06:51:56 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9987"
1811904,2019-05-08 23:33:13 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9984"
1811904,2019-05-13 04:54:44 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9994"
1811904,2019-05-14 02:11:32 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10005"
1811904,2019-05-14 04:29:33 UTC,Notes for testing:
1811904,2019-06-19 00:57:19 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10101"
1811904,2019-06-26 20:10:43 UTC,TITLE:  User menu Profile pictures link is missing icon
1811904,2019-06-26 20:11:52 UTC,"TITLE:  Site options page, Account settings section displays the incorrect icon"
1811904,2019-05-10 01:33:46 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9988"
1811904,2019-06-26 20:11:28 UTC,TITLE:  My Tags page does not display icon for journal entry that have a tag
1811916,2019-01-17 09:52:33 UTC,Also affects SDL 1.2 UI in QEMU 2.12.1
1811916,2019-01-17 10:56:18 UTC,"I'm currently reverted the commit f8d2c9369b8302f65f4f43f14ed3987c2268a02a to use only CTRL-ALT.
https://gist.github.com/Low-power/822eace3f37c893bc6aad3af647b4c7d"
1811916,2021-01-19 06:58:13 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1811929,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1811929,2019-01-16 06:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811929,2019-01-17 06:29:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1811929,2019-02-04 14:46:37 UTC,This bug was fixed in the package linux - 4.19.0-12.13
1811929,2019-02-11 11:06:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1811929,2019-03-04 05:04:43 UTC,Please verify that the kernel in -proposed resolves the problem described in this bug report and update the bug as verification-done-cosmic.  These kernels are releasing this week.
1811929,2019-03-06 10:49:37 UTC,This bug was fixed in the package linux - 4.18.0-16.17
1811935,2019-02-24 13:05:30 UTC,Unfortunately the 17.04 repositories don't seem to be available anymore. So I can't install the older version and upgrade to the new version to reproduce this issue.
1811935,2019-02-24 13:15:28 UTC,Unfortunately the 17.04 repositories don't seem to be available anymore. So I can't install the older version and upgrade to the new version to reproduce this issue.
1811935,2019-02-24 14:16:07 UTC,"As a workaround it should work to upgrade the package manually from the command line with something like ""sudo apt install vim-lastplace""."
1811935,2019-02-24 14:45:48 UTC,I filed a bug report agains vim-addon-manager:
1811935,2020-07-02 00:18:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811935,2020-07-02 00:20:39 UTC,Fixed in version vim-addon-manager/0.5.10
1811936,2019-05-14 15:17:10 UTC,I have not been able to reproduce this.  I am able to add a domain and dnsresource and delete both in the UI and/or API without any issues.  This is similar to what I have reported with #1814164
1811936,2019-05-21 21:16:57 UTC,The UI doesn't allow a user to add a domain name which is invalid as you will not be able to create it.  Additionally in the API if entering invalid names you will get errors.  Here is some MAAS cli commands to create a domain and A record that we can then delete without any issues.
1811937,2019-01-22 11:51:57 UTC,"In this case I use Ubuntu 18.04. On another device with Ubuntu 18.10 I
have the same UI problem."
1811937,2019-01-22 09:52:17 UTC,Reading again it seems there is at least one settings issue. What version of Ubuntu are you using?
1811937,2019-01-22 12:22:33 UTC,"I've reported the settings issue upstream
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/353"
1811937,2019-01-22 09:51:18 UTC,"Thank you for your bug report, it's not clear from the description what the issue is. Is the problem with the settings UI or with the top bar indicator popdown? Or is there an issue with each (in which case it would be better to have 2 reports, it would be less confusing)"
1811943,2019-03-07 17:50:07 UTC,Will be part of PTG discussion
1811943,2019-05-02 21:56:23 UTC,We discussed this at the PTG and don't any fundamental obstacles with implementing this for manila.  Please feel free to propose a brief statement of the use cases to justify the addition to the manila codebase and a review with the proposed change and we will take it up.
1811943,2019-05-02 21:56:30 UTC,"Related, cinder blueprint: https://blueprints.launchpad.net/cinder/+spec/cinder-quota-define-per-volume"
1811943,2021-01-12 10:22:04 UTC,Review: https://review.opendev.org/c/openstack/manila/+/768816
1811946,2019-09-28 09:28:29 UTC,"I can report that the new packages in bionic-proposed work without any problem.
Scanner- canon LiDE 200 on ubuntu 18.04."
1811946,2019-09-27 22:32:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1811946,2019-09-28 01:15:41 UTC,There are updated packages in bionic-proposed which may fix this issue; please see bug #1731459. What remains is that somebody who has an affected device tests those packages and confirms that the updated packages address the issue.
1811957,2019-05-21 12:02:46 UTC,"no feedback over a month, closing as invalid"
1811957,2019-01-19 19:23:30 UTC,To proceed we need the following:
1811963,2020-04-24 11:12:59 UTC,This was fixed for me by patching the latest firmware on the GBICs.
1811963,2019-01-16 10:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811963,2019-01-16 11:43:17 UTC,Unable to serve the logs via apport-collect due to policy restrictions.
1811963,2019-01-30 11:31:21 UTC,Can anyone follow up on this?
1811963,2019-03-06 11:19:10 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0]."
1811963,2019-03-07 11:57:01 UTC,I tested and can reproduce the problem with this combination:
1811963,2019-03-07 16:20:27 UTC,Please file a bug to Intel ethernet developers.
1811963,2020-04-16 10:30:01 UTC,"Hi Malte,"
1811975,2019-01-16 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811976,2019-01-30 09:20:45 UTC,This bug can be closed.
1811976,2019-01-30 09:20:05 UTC,The problem was with HAproxy and VIP.
1811980,2020-10-02 14:48:24 UTC,Thanks for reporting.
1811981,2019-07-22 20:28:34 UTC,This bug was fixed in the package linux-kvm - 5.0.0-1011.12
1811981,2019-07-22 10:56:28 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1039.39
1811981,2019-07-16 21:36:39 UTC,I can confirm that the CONFIG_LOCK_DOWN_KERNEL config is enabled in the 5.0.0-1011.12 linux-kvm kernel in disco-proposed. Thanks!
1811981,2019-07-16 21:21:35 UTC,I can confirm that the CONFIG_LOCK_DOWN_KERNEL config is enabled in the 4.15.0-1039.39 linux-kvm kernel in bionic-proposed. Thanks!
1811981,2019-03-11 11:01:59 UTC,"Hello Steve,"
1811981,2019-03-07 09:13:44 UTC,"I think the fix is here for the PowerPC:
https://git.launchpad.net/qa-regression-testing/commit/?id=2082aec714a3a053664082a747b9c166b398cc4f"
1811981,2019-06-10 10:23:46 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-June/101275.html
1811981,2019-01-31 14:33:17 UTC,This testcase also fails with linux-kvm for Cosmic.
1811981,2019-01-17 07:50:54 UTC,"Po-Hsu, thanks for the report. I'm not sure the lock down kernel config makes sense for ppc64el and s390x, and the qa-regression-testing script should be updated to reflect that."
1811981,2019-01-17 03:16:34 UTC,This could be found on KVM kernel as well.
1811981,2019-01-16 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1811981,2019-02-01 10:53:37 UTC,Didn't see this for ppc64el on the latest 4.15 bionic kernel (4.15.0-45)
1811983,2019-01-16 12:25:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1811985,2019-01-18 18:59:40 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1811989,2019-04-15 03:34:28 UTC,Any news?
1812014,2019-02-18 07:48:01 UTC,Thanks.
1812014,2019-01-30 01:38:13 UTC,Thanks. Please also run 'xrandr' and send us the output.
1812014,2019-01-30 16:06:44 UTC,"Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080     60.02*+  60.01    59.97    59.96    59.93
   1680x1050     59.95    59.88
   1600x1024     60.17
   1400x1050     59.98
   1600x900      59.99    59.94    59.95    59.82
   1280x1024     60.02
   1440x900      59.89
   1400x900      59.96    59.88
   1280x960      60.00
   1440x810      60.00    59.97
   1368x768      59.88    59.85
   1360x768      59.80    59.96
   1280x800      59.99    59.97    59.81    59.91
   1152x864      60.00
   1280x720      60.00    59.99    59.86    59.74
   1024x768      60.04    60.00
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   800x512       60.17
   700x525       59.98
   800x450       59.95    59.82
   640x512       60.02
   720x450       59.89
   700x450       59.96    59.88
   640x480       60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   680x384       59.80    59.96
   640x400       59.88    59.98
   576x432       60.06
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32"
1812014,2019-01-31 02:31:12 UTC,Thanks. The best guess I can make is a problem in upower or the Nvidia driver (comment #15). Those are definitely performance problems (100% CPU for no obvious reason) and could well explain why the keyboard stops responding.
1812014,2019-02-01 16:28:03 UTC,journalctl -b-1 > prevlog.txt
1812014,2019-01-29 17:22:58 UTC,dpkg  -l
1812014,2019-03-13 20:33:15 UTC,"Hi,
I have no unusual extensions installed and even though I disabled all gnom extensions the problem remained.
After checking that, I did what I should have done at the beginning - I changed display driver to X.Org X Server nouveau and since then I have got no problems with the keyboard at all. So it clearly indicates that the problem is with nvidia-driver-390. As I haven't played any video games recently it doesn't' bother me, but it would be nice to have this driver working correctly.
Regards
Krzysztof"
1812014,2019-06-04 04:17:35 UTC,[Expired for upower (Ubuntu) because there has been no activity for 60 days.]
1812014,2019-03-14 02:04:35 UTC,Although ^^^ the above error ^^^ is already covered by bug 1812593.
1812014,2019-04-04 20:01:44 UTC,"Hi, recently I had changed the gpu driver to the latest one from nvidia nvidia-driver-418(opensource) and I since then, I started experiencing performance problems similar to those mentioned earlier: ""'upower' using 100% CPU and another shows 'kworker/6:0-events' using 100%."". The prolems starts after suspending my system and bringing it back to life like previously, but this time keyboard is working fine."
1812014,2019-04-05 01:41:16 UTC,Please keep this bug about the keyboard only.
1812014,2019-06-04 04:17:32 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1812014,2019-06-04 04:17:34 UTC,[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been no activity for 60 days.]
1812014,2019-01-29 17:21:12 UTC,dmesg
1812014,2019-03-14 02:01:03 UTC,I'm not sure how the Nvidia driver could be related.
1812014,2019-01-29 02:40:40 UTC,Please also run:
1812014,2019-01-22 02:43:08 UTC,"I will still avoid mentioning ""performance"" in the bug title to stop other people from jumping on board thinking this is the same as their ""performance"" problems."
1812014,2019-01-25 21:44:14 UTC,"Hi,
I've attached three photos with running the top command. One of them looks normal but the others are not, I guess :)
I hope it will help.
The second thought: I updated the system about a week ago and now this bug happens after a much longer time... maybe this is by chance, but anyway I wanted to share this with you."
1812014,2019-01-16 20:40:11 UTC,the description sounds a bit similar to bug #1807056
1812014,2019-01-17 02:24:25 UTC,"Next time the keyboard stops responding, please try the workaround suggested in bug 1807056:"
1812014,2019-01-18 17:47:35 UTC,apport information
1812014,2019-01-18 17:47:36 UTC,apport information
1812014,2019-01-21 02:43:55 UTC,Thanks.
1812014,2019-01-21 16:46:37 UTC,"Hi,
I mentioned the performance problem because as I believe it is connected with not responding keyboard. If I notice a performance problem for instance during watching yt video I know that keyboard stopped working."
1812014,2019-01-18 18:02:31 UTC,So... it happend again. The workaround doesn't work.
1812014,2019-01-29 02:39:31 UTC,"Thanks, those photos are very helpful."
1812014,2019-01-22 02:45:37 UTC,Can you please:
1812014,2019-01-25 21:35:17 UTC,foto 1 of the terminal with running top command
1812014,2019-01-25 21:36:35 UTC,Foto 2 of the terminal with running top command
1812014,2019-01-25 21:37:40 UTC,Foto 3 of terminal with running top command
1812014,2019-01-22 02:42:30 UTC,"OK then, maybe they are related. That's quite possible since gnome-shell is basically one single threaded event loop."
1812018,2019-01-17 21:05:49 UTC,Patch attached.
1812027,2019-01-16 16:11:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631270"
1812027,2019-01-23 23:02:50 UTC,This issue was fixed in the openstack/kuryr-kubernetes 0.5.3 release.
1812027,2019-01-16 16:10:28 UTC,"For master, this is fixed by patch https://review.openstack.org/#/c/627175/"
1812027,2019-01-21 15:18:01 UTC,"Reviewed:  https://review.openstack.org/631270
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=9dd7c1a5fc98c78229f7a77f8c41c7e890a07aec
Submitter: Zuul
Branch:    stable/rocky"
1812036,2019-08-26 16:06:42 UTC,Looks like this is a duplicate of bug 1826953 which was fixed here:
1812047,2019-01-16 16:20:20 UTC,"For master, this is fixed by patch https://review.openstack.org/#/c/627175/"
1812047,2019-01-16 16:22:46 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631273"
1812047,2019-01-21 11:11:12 UTC,"Reviewed:  https://review.openstack.org/631273
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=a8951134edd22c29cd97f4b0b17e8e534b91c7a6
Submitter: Zuul
Branch:    stable/rocky"
1812047,2019-01-21 11:53:04 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/632071"
1812047,2019-01-22 11:15:45 UTC,"Reviewed:  https://review.openstack.org/632071
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=06e88c90996d2b53d97900117fea4b53ea60cf59
Submitter: Zuul
Branch:    stable/queens"
1812047,2019-01-23 23:02:51 UTC,This issue was fixed in the openstack/kuryr-kubernetes 0.5.3 release.
1812047,2019-01-23 23:11:12 UTC,This issue was fixed in the openstack/kuryr-kubernetes 0.4.6 release.
1812061,2019-01-17 11:07:07 UTC,"Sponsored as 2.3.1-3ubuntu1. Discussed with Dave the possibility of getting this fix upstream, but since the last upstream commit was 3 years ago this doesn't seem like a high priority."
1812061,2019-01-17 11:07:17 UTC,Thanks for the fix!
1812086,2019-08-22 15:29:57 UTC,That's a different stack trace and looks like a different problem that just results in the kernel dying in the same place. And 4.18 is no longer supported.
1812086,2019-01-16 17:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812086,2019-01-17 08:06:27 UTC,"For clarification, this happens on the target after it comes back from the reboot and restores the iSCSI configuration."
1812086,2019-02-15 14:42:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812086,2019-02-18 13:17:02 UTC,Tested successfully.
1812086,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1812086,2019-08-22 15:13:27 UTC,Looks like this patch has not been applied to the 4.18 kernels yet:
1812087,2019-01-16 17:22:18 UTC,Here's a slightly modified test case from Ciro Santilli of ARM.
1812089,2019-01-24 23:03:36 UTC,"What fixed that bug for me was simply doing this:
apt-get install -f"
1812089,2019-01-24 15:00:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812089,2019-01-18 18:59:29 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1812096,2019-01-16 19:09:35 UTC,"What is particularly interesting here is that the soldermask behaves as expected (confined to the footprint) until the minimum width gets to be at least the distance to the next footprint.  At which point, there is interference.  The user's example file shows this at about 57mm, but with closer footprint spacing, we would see this at more rational values as well."
1812096,2019-01-16 19:40:10 UTC,Related?
1812096,2019-05-03 05:54:15 UTC,This came up in another thread when a user was confused about why the plotted output didn't match the previews
1812100,2019-08-23 13:17:43 UTC,"Since the checkout screen portion of this bug was recently fixed with bug 1789256, all that remains of this bug is the check-in screen.  And that makes this a duplicate of bug 1739609 (adding parts and other columns to check-in)."
1812101,2019-01-22 21:50:09 UTC,"(In reply to Hans P. Möller from comment #13)

> how can I change it to use the qt5 VCL? I thought there where only kde and
> gtk
"
1812101,2019-01-29 20:05:28 UTC,"(In reply to Michael Weghorn from comment #14)

> (In reply to Hans P. Möller from comment #13)
> > how can I change it to use the qt5 VCL? I thought there where only kde and
> > gtk
>
> Set ""SAL_USE_VCLPLUGIN=qt5"".
>
> In fact, there's currently quite a bunch of VCL plugins on Linux (gtk, gtk3,
> kde4, kde5, gtk3_kde5, gen,...), some of them deprecated already (kde4 e.g.
> has already been removed from the current development version). Note
> however, that qt5 (which kde5 is based upon) and kde5 are only available
> from 6.2 on and currently still have several known issues... (s. meta bug
> 102495).
"
1812101,2019-01-29 20:36:59 UTC,">
> Did you try this in lubuntu? it doesn't work in my case. I had to use export
> instead of set to change the envvar but it still launches with vcl=kde4
"
1812101,2019-01-29 20:38:59 UTC,So VCL=qt5 havs the checkbox but doesn't add the extension. Should I open a new bug?
1812101,2019-01-29 21:02:22 UTC,"Sorry for my misleading comment 14. That was not meant as a command to be executed ""as is"", but rather as a ""human-readable instruction"" that first had to be converted into a ""machine-readable command"" like the one you used..."
1812101,2019-01-30 10:58:59 UTC,"Michael Weghorn committed a patch related to this issue.
It has been pushed to ""master"":"
1812101,2019-01-30 12:23:48 UTC,"Michael Weghorn committed a patch related to this issue.
It has been pushed to ""master"":"
1812101,2019-01-30 19:34:58 UTC,"Michael Weghorn committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1812101,2019-01-22 21:06:04 UTC,how can I change it to use the qt5 VCL? I thought there where only kde and gtk
1812101,2019-02-02 21:39:57 UTC,Better late than never...
1812101,2019-02-03 00:39:10 UTC,"Hi Rene,"
1812101,2019-02-03 07:59:31 UTC,"(In reply to Michael Weghorn from comment #25)

> My previous comment was targeted at question B), and one thought of mine was
> to drop gtk3_kde5 from the list for the LXQt case, for the reasons mentioned
> in comment 21, which would mean that the fallback list for LXQt would be
> [""kde5"", ""gtk3"", ""gtk"", ""gen""] in case A) stays as is.
"
1812101,2019-02-07 21:27:10 UTC,I'm closing this bug report. Please leave a comment here or open a new bug if you think anything else still needs to be done.
1812101,2019-02-21 08:21:05 UTC,*** Bug 123595 has been marked as a duplicate of this bug. ***
1812101,2019-01-30 19:23:40 UTC,"Michael Weghorn committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1812101,2019-01-22 19:42:33 UTC,"As your screenshots show, more custom controls are missing in the save dialog when run on LXQt (""Save with password"", ""Encrypt with GPG key"")."
1812101,2019-01-30 12:35:34 UTC,Backports for LibreOffice 6.2 for the two commits:
1812101,2019-01-22 00:26:23 UTC,"(In reply to Michael Weghorn from comment #9)

> (In reply to Hans P. Möller from comment #7)
> > Created attachment 148473 [details]
> > lubuntu LXQt file saver
>
> @Hans: Is that screenshot with LibreOffice 6.1 and the the gtk3_kde5 VCL
> plugin or with 6.2 and the kde4 one?
>
> Btw, when using the ""qt5"" VCL plugin (i.e. starting LibreOffice with the env
> variable ""SAL_USE_VCLPLUGIN=qt5"" set), the checkbox is also there, but seems
> to have no effect, the file extension is not added.
"
1812101,2019-01-22 00:49:38 UTC,"Created attachment 148495
LO 6.2 Lubuntu 18.10 filepicker"
1812101,2019-01-16 17:44:10 UTC,"On my Linux PC, LibreOffice vanilla works properly with all flavours of Ubuntu 18.10. IMHO, bug has to be filed at KDE or Canonical as the software is tweaked/recompiled by them."
1812101,2019-01-16 18:56:48 UTC,"Thank you for reporting the bug.
KDE5 support has been hugely improved in LibreOffice 6.2.
Could you please try to reproduce it with LibreOffice 6.2 from https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version."
1812101,2019-01-16 20:09:27 UTC,"I installed 6.2RC2 but I don't get the ""kde look"" in the file picker/dialog that the libreoffice-kde5 package gave me.
In help->about appears VCL:kde4 and not gtk3_kde5 which i was getting before."
1812101,2019-01-17 16:15:14 UTC,"Just tested on a kubuntu desktop, and there's a checkbox option in the save dialog that reads ""Automatically select filename extension (.docx)"". See attached screenshot."
1812101,2019-01-17 17:36:36 UTC,"I don't have the checkbox, see the .png in the above comment"
1812101,2019-01-18 11:04:41 UTC,"I installed 6.2.0.2 in an up-to-date lubuntu 18.10 VM as you suggested Xisco. I can confirm that the issue Hans is reporting is still there: the VCL is ""kde5"", the save dialog doesn't have an option to add the file extension automatically, and files are saved without an extension if not explicitly added."
1812101,2019-01-16 09:50:35 UTC,"Description:
libreoffice-kde5 file dialog doesn't add automatically the file extension which are important for.docx .xlsx, otherwise the system recognize them as zip."
1812101,2019-01-18 01:21:18 UTC,Who is responsible of that checkbox? the filemanager? in kubuntu's case dolphin?
1812101,2019-01-18 11:51:56 UTC,How did you test it in 6.2? How could you add libreoffice-kde5 to 6.2?
1812101,2019-01-18 14:32:12 UTC,"I downloaded the main DEB package from https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases, unpacked the archive and installed all the debs in it (sudo dpkg -i *.deb). That was enough to have libreoffice use the ""kde5"" VCL by default."
1812101,2019-01-20 19:31:17 UTC,"FYI KDE4 used to have its own auto-extension checkbox in the file open dialog, so the LO KDE4 integration used that KDE setting and skipped LOs' own handling. Probably that setting doesn't exist anymore, as file dialogs are now Qt5 based and now LO has to handle the file auto-extension on its own."
1812101,2019-01-20 21:43:26 UTC,"Created attachment 148457
Screenshot of save dialog in KDE 5"
1812101,2019-01-21 12:31:56 UTC,"Created attachment 148473
lubuntu LXQt file saver"
1812101,2019-01-21 22:21:34 UTC,"(In reply to Hans P. Möller from comment #7)

> Who creates the checkbox? Libreoffice or the filemanager (in kubuntu
> dolphin)?
"
1812101,2019-01-21 22:34:52 UTC,"(In reply to Hans P. Möller from comment #7)

> Created attachment 148473 [details]
> lubuntu LXQt file saver
"
1812101,2019-01-18 11:05:43 UTC,"I tested the upstream 6.2.0.2 build as suggested by Xisco in the upstream bug report, and I can confirm that the bug still exists. This appears to be an upstream issue."
1812102,2019-01-31 21:33:37 UTC,Example is RT#116647 where deployments are failing because of a warning from the load check.
1812110,2019-03-22 03:44:24 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1812110,2019-03-24 23:39:41 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1812110,2019-03-24 23:04:24 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1812110,2019-02-06 21:09:04 UTC,"Reviewed:  https://review.openstack.org/633807
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e5e929f019c05fa57f6b216855b9246b7a5f8d48
Submitter: Zuul
Branch:    stable/queens"
1812110,2019-01-29 19:24:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/633807"
1812110,2019-01-30 02:17:23 UTC,"Reviewed:  https://review.openstack.org/631684
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b797f6f7e99fdef380340d6fe29e4004be48781
Submitter: Zuul
Branch:    master"
1812110,2019-01-29 19:23:51 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/633806"
1812110,2019-01-18 01:01:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/631684"
1812110,2019-01-31 13:44:04 UTC,"Reviewed:  https://review.openstack.org/633806
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2662df48526a2a4ddcd4a7bdbb6108102fe8321
Submitter: Zuul
Branch:    stable/rocky"
1812111,2019-01-16 21:49:37 UTC,http://ci.jujucharms.com/job/make-check-juju/2313/consoleFull
1812111,2019-01-17 06:24:05 UTC,Can you make sure we've got a card for this on the ci day board please?
1812111,2019-06-12 13:10:56 UTC,"Also seen here
http://ci.jujucharms.com/job/make-check-juju/5725/consoleFull#88914144916634ad4-80e2-4403-a89b-6238558073ce"
1812111,2019-07-23 23:42:38 UTC,Saw a recent occurrence https://jenkins.juju.canonical.com/job/github-make-check-juju/65/testReport/junit/github/com_juju_juju_worker_uniter/TestPackage/
1812111,2019-08-09 04:26:14 UTC,https://github.com/juju/juju/pull/10506
1812114,2019-01-16 22:14:35 UTC,apport information
1812114,2019-01-16 22:14:37 UTC,apport information
1812114,2019-01-17 07:54:36 UTC,"Seems like it need ipu3 driver, which gets included since v5.0-rc1 [1]."
1812114,2019-01-16 22:14:34 UTC,apport information
1812114,2019-01-18 19:30:55 UTC,apport information
1812114,2019-01-18 19:34:15 UTC,Booted mainline rc2.
1812114,2019-01-27 13:10:37 UTC,"As well as a kernel driver, this platform also needs user space support to enable the camera."
1812114,2019-01-18 19:30:54 UTC,apport information
1812114,2019-01-16 22:14:33 UTC,apport information
1812114,2019-01-16 22:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812114,2019-01-16 22:14:31 UTC,apport information
1812114,2019-01-16 22:14:30 UTC,apport information
1812114,2019-01-16 22:14:29 UTC,apport information
1812114,2019-01-16 22:14:28 UTC,apport information
1812114,2019-01-16 22:14:27 UTC,apport information
1812114,2019-01-16 22:14:26 UTC,apport information
1812114,2019-01-16 22:14:25 UTC,apport information
1812114,2019-01-16 22:14:24 UTC,apport information
1812114,2019-01-16 22:14:24 UTC,apport information
1812114,2019-01-16 22:14:32 UTC,apport information
1812118,2020-02-21 16:43:06 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1812118,2019-12-19 14:43:11 UTC,This issue was fixed in the openstack/neutron 15.0.1 release.
1812118,2019-10-23 15:58:54 UTC,"Reviewed:  https://review.opendev.org/689853
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8da6836b5b232c1847bb4dee78239e79c6ec7d5c
Submitter: Zuul
Branch:    stable/train"
1812118,2019-10-21 17:45:08 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/689853"
1812118,2019-10-19 22:44:47 UTC,"Reviewed:  https://review.opendev.org/670177
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=040b550a861ce321c87ac33e92836a502d9531d3
Submitter: Zuul
Branch:    master"
1812118,2019-07-10 20:05:46 UTC,"I was going through old bugs and found this one, figured I'd update."
1812118,2019-07-10 20:06:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670177"
1812118,2019-04-18 12:46:13 UTC,"> According to your scenario, the unprivileged user may not have access to the external network and subnet which are created by the admin.
"
1812118,2019-04-18 10:07:06 UTC,"Hi Kay,
According to your scenario, the unprivileged user may not have access to the external network and subnet which are created by the admin. That's why the update gets failed. Would you please double check whether you can see the corresponding external network and its subnet when login as the unprivileged user?"
1812118,2019-01-30 17:13:48 UTC,The external network and the subnet were created by admin. The external subnet belong to the external network. An unprivileged user tries to create a router.
1812118,2019-01-30 16:56:38 UTC,Hello Kay:
1812118,2019-07-11 05:11:19 UTC,"Finally. Thanks for the update, I was not sure whether the fix I proposed is correct."
1812123,2019-05-14 19:04:29 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18
1812123,2019-06-25 13:08:32 UTC,This bug was fixed in the package linux-azure - 4.15.0-1049.54
1812123,2019-06-07 01:27:24 UTC,"Hi, Joe and Josh."
1812123,2019-05-14 22:56:08 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1812123,2019-05-14 22:55:23 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18~18.04.1
1812123,2019-04-03 16:16:37 UTC,"Hi, Josh."
1812123,2019-01-17 17:00:53 UTC,"Affects 4.15-azure in Xenial, 4.15-azure and 4.18-azure in Bionic."
1812123,2019-03-27 12:20:49 UTC,"Because these kernels are made for 18.10, but our DPDK PPAs are on 18.04 and 16.04, there has been difficulty testing this kernel. Can we get a one-off build for bionic?"
1812123,2019-03-19 18:09:08 UTC,"I believe these fixes from testing the scenario of rescinding/revoking the VF while DPDK is active, which is a scenario triggered by a host networking driver update."
1812123,2019-03-14 19:07:46 UTC,Test kernel for cosmic: https://kernel.ubuntu.com/~mhcerri/azure/lp1812123-cosmic/
1812123,2019-03-14 18:45:56 UTC,Patchset for cosmic/linux-azure: https://lists.ubuntu.com/archives/kernel-team/2019-March/099256.html
1812123,2019-03-14 15:46:22 UTC,"b5679cebf780 (""vmbus: fix subchannel removal"") seems to be a fix to ae6935ed7d42 (""vmbus: split ring buffer allocation from open""), which we currently don't have in the azure kernel. Is it really necessary and we should pick ae6935ed7d42 as well, or is it possible to skip it?"
1812123,2019-01-31 17:20:40 UTC,Commit b5679cebf780  is now in mainline as of v5.0-rc4
1812123,2019-03-28 17:38:56 UTC,Test kernel for bionic: https://kernel.ubuntu.com/~mhcerri/azure/lp1812123-bionic/
1812127,2019-01-17 04:20:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1812127,2019-01-17 19:41:19 UTC,"I am sorry, but I do not know to which ""package"" this is related."
1812127,2019-01-17 20:00:31 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812127,2019-01-17 21:17:03 UTC,"Thanks for your help in categorizing this, Brian.  I had not clue at all."
1812127,2019-01-17 21:44:34 UTC,"I cannot comply with request for apport as it ""collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material"" and I am not allowed to share such information."
1812128,2020-04-23 19:28:06 UTC,Can you provide a dmesg log at least?
1812128,2020-04-23 20:06:14 UTC,"Wow, this is really old.  I am sorry for the lack of information.  The built-in system is obviously flawed, as previously noted.  Further, I no longer use Xubuntu, and have been very happy moving to Debian for a long time now.  No more errors and screw-ups from trying to reinvent the wheel, and no more bad tech support."
1812128,2019-01-17 21:14:57 UTC,"Cannot comply with request for apport as it ""collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material"" and I am not allowed to share such information."
1812128,2019-01-17 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812128,2019-01-17 05:30:53 UTC,"That is probably a kernel message, reassihned to linux."
1812128,2019-01-17 04:20:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1812128,2019-01-17 20:14:31 UTC,"Juhani, thank you so much.  I am so sorry for that mistake.  You are quite correct; it should have been IRQ.  I wrote it down and was trying to hurry before I missed the message.  Shame on me.  That makes a huge amount of difference and I will change the title."
1812132,2019-01-16 23:58:41 UTC,Note: This only occurs if the file is in a search location that was manually added.
1812132,2019-01-18 10:37:09 UTC,"Thank you for your bug report. What's the output of that command on your system?
- dpkg -l | grep tracker?"
1812132,2019-01-18 21:42:31 UTC,"I *think* it's tracker because I'm using the `vanilla-gnome-desktop` package which creates a plain Gnome Shell session, which I think uses tracker in the Overview search (when pressing Super in Gnome Shell)."
1812132,2019-01-22 11:16:47 UTC,Would be probably best to report it upstream on https://gitlab.gnome.org/GNOME/tracker/issues
1812132,2019-05-23 17:52:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812136,2019-11-12 17:37:37 UTC,Moved:
1812138,2019-01-20 19:31:32 UTC,"About xserver-xorg-video-radeon: It is a binary package, one of many built from the xserver-xorg-video-ati source package."
1812138,2019-01-18 18:33:28 UTC,Sorry - I forgot to add in the original post that streaming the same stream with mpv worked OK.
1812138,2019-01-18 14:45:50 UTC,So not a vlc bug.
1812138,2019-01-17 01:39:37 UTC,This might be useful(?):
1812138,2019-01-17 01:39:08 UTC,"NOTE: that I tried to add an ""also affects"" package of:"
1812139,2019-01-17 04:04:10 UTC,Duplicate of https://bugs.launchpad.net/gcc-arm-embedded/+bug/1809971
1812141,2019-09-19 12:07:35 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1812141,2019-09-19 13:11:50 UTC,"@adam-collard, this is a feature request, not an issue that is should expire after 6 months. If you do not want to implement this feature than that is fine, but please say so."
1812141,2020-10-07 13:55:56 UTC,"Modifying this request slightly, rather than finding a way to re-commission a node while it is deployed, it would be to have the deploy automatically update hardware information or at least skip comparison of drive serial numbers. In MAAS 2.8.2 if a machine is released, and a drive is replaced or otherwise is seen with a new serial number MAAS will fail to redeploy that node presenting an error about not finding the drive device that was replaced. This is only resolved by  recommissioning the machine to update this hardware information."
1812141,2020-10-07 21:13:51 UTC,"Mark (our support engineer) was kind enough to add our service issue to this. However, to make our request clear, we do NOT want to recommission. When a drive is ""replaced"" (BOSS, RAID-1 virtual disk rebuilt) we want any ""serial number"" or UUID check to simply be skipped. This will become more important moving forward (composable systems, where disks are ""attached"" just for a single deployment and generally moved to another system upon release. No doubt there exist some group of users who wish to require the absolute same disk each time, but we have no such requirement nor do we ever foresee that as being helpful."
1812141,2020-10-07 21:17:22 UTC,"I suppose if one were to insist on having the system details updated, the relevant bits of commission (primarily lshw?) could be run as a ""test"" during deploy, and any gratuitous packages cleaned up by curtin scripts. That's not a requirement from our perspective, but I can appreciate a desire to have the database have correct information about each system even if we don't want it enforced ;>"
1812143,2020-08-03 02:01:46 UTC,If you are experiencing any problems in Ubuntu 20.04 or 18.04 then please run:
1812143,2020-07-31 13:48:34 UTC,"I am getting this error while installing hostapd, lighttpd and isc-dhcp-server on Kali Linux. How can I fix this error and install these packages?"
1812143,2020-04-26 22:06:39 UTC,I got the same error after upgrading to Ubuntu 20.04 from 18.04
1812143,2019-10-09 13:51:11 UTC,This bug was fixed in the package ukwm - 1.1.13-0ubuntu1
1812143,2019-01-24 20:48:49 UTC,This bug was fixed in the package gsettings-desktop-schemas - 3.31.0.2-2ubuntu3
1812143,2019-01-20 12:00:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812143,2020-01-24 08:57:38 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1812149,2019-01-17 03:38:52 UTC,The script will return 4 if the test was skipped.
1812149,2019-01-22 10:47:30 UTC,"To make the skip code work, we will need to fix 1812352 first.
And bring the CPU hotplug skip code change to older releases if needed."
1812149,2019-11-21 10:10:24 UTC,"With bug 1812352 fixed, this is now affecting Xenial."
1812149,2020-11-17 04:24:25 UTC,Still visible in Xenial 4.4.0-1118.132 AWS t2.small
1812152,2019-01-17 04:30:06 UTC,This change was made by a bot.
1812154,2019-01-17 06:22:56 UTC,"After I posted this, the following message appeared:
The logfile C\Program Files (x86)\Jokosher\jokosher.exe.log could not be opened: [Errno 13] permission denied: C\Program Files (x86)\Jokosher\jokosher.exe.log"
1812159,2019-06-06 09:28:18 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-June/101176.html
1812159,2019-07-24 20:29:46 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1052.59
1812159,2019-07-22 20:28:34 UTC,This bug was fixed in the package linux-kvm - 5.0.0-1011.12
1812159,2019-07-22 10:56:28 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1039.39
1812159,2019-01-17 07:26:32 UTC,This option checks for a stack overrun on calls to schedule(). If the stack end location is found to be over written always panic as the content of the corrupted region can no longer be trusted. This is to ensure no erroneous behaviour occurs which could result in data corruption or a sporadic crash at a later stage once the region is examined. The runtime overhead introduced is minimal.
1812159,2019-05-06 11:06:04 UTC,Found on X-KVM as well.
1812159,2019-01-31 14:31:45 UTC,This testcase also fails on linux-kvm for Cosmic.
1812159,2019-07-16 22:37:56 UTC,"I can confirm that the SCHED_STACK_END_CHECK config option has been enabled in the linux-kvm kernel 4.4.0-1052.59 for xenial, 4.15.0-1039.39 for bionic, and 5.0.0-1011.12 for disco. Thanks!"
1812168,2020-01-15 22:59:29 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/702767"
1812168,2020-02-24 18:05:43 UTC,"Reviewed:  https://review.opendev.org/702767
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9def99f3d20df5253bafba24bd1ca2ea9c99a032
Submitter: Zuul
Branch:    stable/rocky"
1812168,2019-12-19 14:43:02 UTC,This issue was fixed in the openstack/neutron 15.0.1 release.
1812168,2020-04-07 20:16:00 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/718209"
1812168,2020-04-10 04:24:08 UTC,"Reviewed:  https://review.opendev.org/718209
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0d3d689a4e8c97ca25841444e7d425614b6c977d
Submitter: Zuul
Branch:    stable/queens"
1812168,2020-02-28 15:29:15 UTC,This issue was fixed in the openstack/neutron 13.0.7 release.
1812168,2019-12-19 14:41:26 UTC,This issue was fixed in the openstack/neutron 14.0.4 release.
1812168,2020-02-21 16:42:38 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1812168,2019-11-20 18:23:46 UTC,"Reviewed:  https://review.opendev.org/693707
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a9b4a4553ecd27e764e3b4789e51ba1d84c2ab4e
Submitter: Zuul
Branch:    stable/stein"
1812168,2019-11-11 14:53:21 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/693707"
1812168,2019-11-11 14:53:07 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/693706"
1812168,2019-11-11 13:32:47 UTC,"Reviewed:  https://review.opendev.org/691640
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4379310846078c45df140071688f740cd900c1d6
Submitter: Zuul
Branch:    master"
1812168,2019-10-28 09:26:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/691640"
1812168,2019-10-22 08:46:07 UTC,"In my opinion the problem is that disassociate_floating_ips (https://opendev.org/openstack/neutron/src/branch/master/neutron/db/l3_db.py#L1576) operates directly on DB models but has not interaction with the external DNS server, so when the port is deleted any existing DNS record associated to the floating IP will stay until the floating IP is reassociated."
1812168,2019-09-04 08:18:30 UTC,@Miguel: Are you actively working on this? Otherwise maybe better unassign yourself?
1812168,2019-11-21 00:59:15 UTC,"Reviewed:  https://review.opendev.org/693706
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5c5e17bd7d57be715ad5cd37089ad3a4cb4a81c6
Submitter: Zuul
Branch:    stable/train"
1812170,2019-05-29 09:16:13 UTC,Need to see if it repeats again.
1812170,2019-07-22 07:32:18 UTC,"Not seen for long. It might have been fixed. If it happens again, we'll reopen it."
1812172,2019-08-22 16:32:54 UTC,"Reviewed:  https://review.opendev.org/663688
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=092449a9c6da8311914b2b13f1fdc5f0a5f68f0c
Submitter: Zuul
Branch:    stable/queens"
1812172,2019-07-31 23:43:38 UTC,"Reviewed:  https://review.opendev.org/663657
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=99ac7f9e119c5366ed0b1ebb112c7ee90be863ec
Submitter: Zuul
Branch:    stable/rocky"
1812172,2019-02-22 13:20:18 UTC,"Reviewed:  https://review.openstack.org/630970
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=cad7916ce8d21295992c2efe0e18657c6e56604d
Submitter: Zuul
Branch:    master"
1812172,2019-06-06 13:23:21 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/663657"
1812172,2019-06-06 14:37:07 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/663688"
1812176,2020-06-09 21:14:52 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1067.68
1812176,2020-06-09 21:18:55 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1075.82
1812176,2020-06-09 21:16:45 UTC,This bug was fixed in the package linux - 4.4.0-184.214
1812176,2020-06-09 21:09:10 UTC,This bug was fixed in the package linux - 4.15.0-106.107
1812176,2019-06-12 06:52:28 UTC,"After discussed with Kamal, we're not going to enable this for the KVM kernel."
1812176,2020-05-19 18:08:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1812176,2020-05-19 18:05:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812176,2019-07-15 09:02:31 UTC,Fix applied upstream: ff95bf28c23490584b9d75913a520bb7bb1f2ecb
1812176,2019-01-17 08:19:49 UTC,"To enable this kallsyms symbol, CONFIG_KALLSYMS must be enabled in the kernel."
1812176,2020-06-09 07:22:46 UTC,"X-kvm:
-------------------
running psock_tpacket test
--------------------
[SKIP] CONFIG_KALLSYMS not enabled"
1812177,2019-03-25 17:42:24 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/647557"
1812177,2020-03-19 21:10:21 UTC,"Reviewed:  https://review.opendev.org/660456
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8a20b086a14dd73bfa57cdef632a28e72e265eb2
Submitter: Zuul
Branch:    stable/ocata"
1812177,2019-05-21 17:02:02 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/660456"
1812177,2019-04-26 17:15:52 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1812177,2019-04-15 15:04:11 UTC,"Reviewed:  https://review.openstack.org/647557
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ebf011f11ebb4d329e90e7ec0e498a3a6832e154
Submitter: Zuul
Branch:    stable/pike"
1812177,2019-03-24 23:39:49 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1812177,2019-01-31 22:01:19 UTC,"Reviewed:  https://review.openstack.org/631731
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6061186d2d86eb628dcdc61667c240576fa8f10e
Submitter: Zuul
Branch:    stable/rocky"
1812177,2019-03-22 03:44:36 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1812177,2019-03-15 15:51:52 UTC,"Reviewed:  https://review.openstack.org/634439
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7c85ebad0bf13d609b384e7637b0787bf8d484f7
Submitter: Zuul
Branch:    stable/queens"
1812177,2019-02-01 15:47:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/634439"
1812177,2019-01-18 09:12:21 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/631731"
1812177,2019-01-18 00:46:31 UTC,"Reviewed:  https://review.openstack.org/631179
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=975f0156137e37f7a9139c0268547d79dcc3c43c
Submitter: Zuul
Branch:    master"
1812177,2019-03-24 23:04:25 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1812179,2020-10-29 04:07:34 UTC,"seeing the same behavior even as of 2020-10-28, basically it's only the ceph-mgr binary specifically that effects my own ability to run ceph on odroid-hc2 armv7l systems."
1812191,2019-10-31 03:44:12 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1812194,2020-07-24 09:23:16 UTC,"This test will need:
CONFIG_DUMMY
CONFIG_NETDEVSIM"
1812194,2019-07-22 03:59:39 UTC,"Error message on D-KVM:
 selftests: net: rtnetlink.sh
 ========================================
 Error: Unknown device type.
 Cannot find device ""test-dummy0""
 FAIL: cannot add dummy interface
 not ok 1..11 selftests: net: rtnetlink.sh [FAIL]"
1812194,2019-04-18 15:42:42 UTC,Also found in cosmic/linux-azure:
1812194,2019-03-11 10:50:20 UTC,Found in 4.18 Bionic AWS as well.
1812194,2019-04-18 16:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812196,2019-01-17 21:30:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/631649"
1812196,2019-01-24 23:08:50 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/633086"
1812196,2019-01-31 13:34:37 UTC,"Reviewed:  https://review.openstack.org/631649
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=edd1cd9ee4d149b01a388f03fb423374020033d7
Submitter: Zuul
Branch:    master"
1812196,2019-02-01 02:17:14 UTC,"Reviewed:  https://review.openstack.org/633086
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a0f5618ffa02cc8622669a5c31b98f9b4773ed60
Submitter: Zuul
Branch:    stable/rocky"
1812196,2019-03-22 03:44:35 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1812196,2019-03-24 23:39:45 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1812204,2019-01-22 21:31:18 UTC,Until this is implemented in kicad one can use freecad to create footprints (with the powerful sketcher workbench) and export with stepup. Demo video can be found here: https://forum.kicad.info/t/kicad-stepup-the-sketcher-for-footprint-generation/9582
1812204,2019-01-22 22:38:06 UTC,It actually only works for really old DXF revisions.
1812204,2019-01-18 10:06:17 UTC,The roadmap is that I have a partial implementation and I'll continue working on it when 5.1 is out.
1812204,2019-01-22 22:35:25 UTC,Thats great because importing DXF objects doesen't work.
1812204,2019-01-17 17:24:44 UTC,"@Nick, it doesn't really matter the version is, he's asking for a new feature. We promised constraint-driven outline/mechanical editing in V6, so it will happen, sooner or later."
1812204,2019-01-18 09:55:19 UTC,Is there a road map for constraint the tool
1812204,2019-01-17 17:02:04 UTC,added version info
1812204,2019-01-17 12:41:40 UTC,Please add version info.
1812205,2021-02-18 16:46:31 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1812215,2019-01-18 08:22:20 UTC,"If you are using the prime keyword, it behaves the same with any plugin used.
Can you expand on this?"
1812215,2019-01-18 09:51:07 UTC,"Yes, but the problem is not with prime keyword. The problem is with stage-packages. When used with dump plugin, the content of the packages are not included into the final snap."
1812215,2019-02-03 21:29:58 UTC,Could you provide a snapcraft.yaml file where this problem happens? I ran a quick test with the dump plugin (yaml file attached) and files from stage-packages were included in the final snap:
1812215,2020-06-04 16:03:32 UTC,"Put simply, `prime` does filter the files in the part's stage-packages.  If using prime, you have to account for the stage packages, or put them in another part that isn't filtered."
1812221,2019-01-24 07:05:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632941"
1812223,2019-10-23 16:22:17 UTC,"Today on GitHub a ppc64el webhook was turned on for the systemd project. The fuzzers (built with ASan) crashed there as soon as they started with something like
```
757/758 fuzz-varlink:oss-fuzz-14708:address     FAIL     0.02 s (exit status 1)"
1812223,2019-01-23 07:20:01 UTC,Maybe related to bug 1812955?
1812223,2019-01-23 11:28:24 UTC,This bug was fixed in the package meson - 0.49.0-2ubuntu1
1812224,2019-04-19 22:41:09 UTC,Problem disappears with VBox guest additions 6.0.6 when setting VBox VMSVGA Graphics Controller.
1812225,2019-08-10 06:48:51 UTC,"Hi all, So can I remove entry with the two asterics for firewall group from Rocky?"
1812225,2019-08-10 20:40:05 UTC,"Hi Sapna, yes, I think You can safely remove it as this feature was implemented by https://github.com/openstack/neutron-fwaas/commit/dbac4b8922a82e38e6e03444640cbabab96c5ad7 IIUC.
Please propose patch to remove it from master branch first (https://docs.openstack.org/neutron/latest/admin/fwaas.html) and than we can backport it to stable branches which needs it."
1812225,2019-08-10 22:27:54 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675743"
1812225,2019-08-11 19:27:34 UTC,"Reviewed:  https://review.opendev.org/675743
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1f09cff08e8ca2e02b04e6ad4379bcd9a07f4b51
Submitter: Zuul
Branch:    master"
1812225,2019-09-19 10:12:15 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1812232,2019-05-14 16:57:47 UTC,If openstack.org is an important bin for your pastes please open a new bug report about this issue with pastebinit.
1812232,2019-06-20 23:15:14 UTC,The version of pastebinit in the proposed pocket of Disco that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.
1812232,2019-05-14 22:04:08 UTC,"Howdy,"
1812232,2019-05-14 16:56:08 UTC,This isn't a regression in disco as the same error occurs with the version of the package in the release pocket for disco.
1812232,2019-05-13 19:46:31 UTC,Verification done for disco:
1812232,2019-04-30 22:21:07 UTC,"Hello Robie, or anyone else affected,"
1812232,2019-04-21 10:39:27 UTC,"An upload of pastebinit to disco-proposed has been rejected from the upload queue for the following reason: ""Version isn't lower than eoan (try moving that tilde one word left)""."
1812232,2019-05-14 00:46:24 UTC,"Howdy,"
1812232,2019-01-18 18:48:47 UTC,Thanks for reporting.
1812237,2019-02-19 17:42:13 UTC,"Is this still an issue? I haven't been able to reproduce it.
Here is what I have tried so far:"
1812241,2019-01-17 16:51:20 UTC,Branch:
1812241,2019-05-25 01:32:38 UTC,"Thanks for this branch, Rogan.  I signed off on it, and added a follow up commit based on our IRC conversation."
1812241,2019-07-29 15:32:39 UTC,Looks like something has changed in master since this was done as it's not patching cleanly for me.
1812243,2019-07-23 16:33:53 UTC,"This is indeed something that we'd like to have in ubuntu-image for sure, sooner or later. But I would prefer this to be an official part of the gadget.yaml spec, allowing for more fine-grained control of how the final partitions and volumes would look (support for sparse images as well)."
1812243,2019-06-11 23:09:38 UTC,It would be preferable to use standard ubuntu-image tool for our snapdragon project. Is this bug on the radar?
1812243,2019-06-12 09:46:48 UTC,"Hi, I understand what Ondrej did and db-builder which was good enough for project, so here we just want to see if ubuntu-image has a chance to fix this case based on my hook. The post-populate-rootfs hook I proposed is also based on part of db-builder to create system-boot and writable image (for Android sparse image). Of course it's rough prototype now and meanwhile it has to refine how we put content from source to target specifed by gadget.yaml, for system-boot partition. We're craving to discuss with foundation team to have the same identical code available by default in the ubuntu-image."
1812243,2019-07-23 21:45:07 UTC,"@Lukasz Zemczak <email address hidden> feel free to pull me for
brainstorming about this as by now I have accounted for multiple scenarios
where ubuntu-image was not suitable.
I totally agree right way would be to extend language in gadget to the
point we have flexible yet robust way to describe what ubuntu image should
do, rather than feeding it with endless amount of parameters. Image
building experience should not change, one should just get expected output.
Given changes planned for UC20 which will need to be accommodated anyway,
we better be more forward thinking here rather than short term fix...."
1812243,2019-07-23 21:58:10 UTC,"The implementation here needs to take on board Gustavo's feedback at the UC20 sprint last month regarding overall design, since this requires changes to gadget yaml which needs to be agreed between ubuntu-image and snapd."
1812247,2019-01-29 23:38:30 UTC,"schamane, thanks for reporting back your success. I've seen this question asked a dozen times and never seen an answer documented. Thanks!"
1812247,2019-01-30 16:10:35 UTC,"We checked what actually is the backend that the ""ssh-add -c"" is trying to reach.
First we thought that should be the ssh-agent spawned for gnome-keyring-daemon [1]"
1812247,2019-01-29 23:26:55 UTC,"Steps for a workaround by disabling gnome-keyring's SSH agent component, tested in Ubuntu 18.04.1:"
1812247,2019-07-02 07:55:47 UTC,"My suspicion is that we never get as far as askpass – gnome-keyring-daemon spawns a ssh-agent to pass requests on to (in my case, that's easy to spot because I use PKCS#11 tokens and that's the one spawning ssh-pkcs11-helpers), and that one doesn't have DISPLAY in its environment, so it won't even try to obtain permission that way."
1812247,2019-07-02 08:10:19 UTC,"Issuing call setenv(""DISPLAY"", "":0"", 1) via gdb seems to result in a dialog popping up, as desired."
1812247,2019-07-02 06:15:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812247,2019-01-29 20:32:02 UTC,I originally reported this against gnome-session. @vanvugt changed it to openssh. I think it should be changed to gnome-keyring. I didn't see it at first but now it's clear that it is actually gnome-keyring that interferes: `SSH_AUTH_SOCK=/run/user/1000/keyring/ssh`
1812247,2019-01-18 05:12:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1789523, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1812247,2019-01-29 18:26:11 UTC,Could this answer be related? https://unix.stackexchange.com/a/351742/254144
1812247,2019-01-26 22:14:43 UTC,"Gosh, I was mistaken in #7. As in my initial report: ssh-askpass is working, it is only failing for ssh-add -c:"
1812247,2019-01-26 21:51:08 UTC,"@paelzer, you put a lot of work into this. Much appreciated! Thanks a lot!"
1812247,2019-01-25 09:49:20 UTC,"Hi,
I tried the same on Bionic/Cosmic/Disco (a VM each running the same commands)
1. created an ssh key (ssh-keygen)
2. added it to authorized key (cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys)
3. added it with ssh-add (ssh-add)
4. verified it was added (ssh-add -l)
5. logged to local IP via ssh using the key (ssh ubuntu@127.0.0.1 uname -a)
   (working)
6. removed the key (ssh-add -d)
7. added the key in confirm mode (ssh-add -c)
8. logged to local IP via ssh using the key (ssh ubuntu@127.0.0.1 uname -a)
   Got the confirmation prompt"
1812247,2019-01-24 03:46:41 UTC,"Sorry, the combination of ssh-agent and ""log out and log back in"" made me immediately think of bug 1789523."
1812247,2019-01-22 22:40:03 UTC,"I have now removed the ""marked as a duplicate of bug 1789523""."
1812247,2019-01-18 10:55:34 UTC,@vanugt I fail to see how bug 1789523 could be a duplicate since I have shown that ssh-agent is running and working. It just fails to call ssh-askpass in some cases.
1812247,2019-01-29 18:48:06 UTC,"The bug has been reproduced with the system's own ssh-keygen and the command `ssh-keygen -N $passphrase -f ~/.ssh/id_rsa`. Also, https://unix.stackexchange.com/a/351742 is about keys that didn't work at all. The problem here is that confirmation fails, everything seems to be working."
1812255,2019-02-06 10:09:22 UTC,"Hi, can I know what is the version of gfortran you used ? It is not working with gfortran 8. It is related to compile qcdloop inside it. Hua-Sheng"
1812255,2020-01-23 13:56:31 UTC,"Hi Olivier, what to do for this release ? A temporal fix can be done for the ff in qcdloop is by increasing a bit the array of ipi12"
1812267,2019-01-18 19:56:46 UTC,"As discussed with Ken, this is a minor build issue and does not gate any release"
1812270,2019-01-17 23:39:00 UTC,I never imagined it being in that dialog. particularly because the preferences dialog in pcb_new also allows one to edit the footprint editor preferences. This includes the default settings.
1812270,2019-01-17 23:53:26 UTC,"Right.  We don't have an editable default in pcbnew, only the board-specific settings.  I suppose that we could add a panel to the pcbnew preferences to store application-level defaults."
1812270,2019-01-17 22:49:44 UTC,Do you not have this dialog in Board Settings?
1812271,2019-01-18 16:32:12 UTC,@sforshee
1812271,2019-01-23 21:09:26 UTC,apport information
1812271,2019-01-23 21:08:53 UTC,"The same issue happened on another DELL desktop model OptiPlex 7060.
Running apport-collect 1812271 now."
1812271,2019-01-23 21:09:23 UTC,apport information
1812271,2019-01-23 21:09:24 UTC,apport information
1812271,2019-01-23 21:09:28 UTC,apport information
1812271,2019-01-23 21:09:38 UTC,apport information
1812271,2019-01-23 21:09:31 UTC,apport information
1812271,2019-01-23 21:09:32 UTC,apport information
1812271,2019-01-23 21:09:34 UTC,apport information
1812271,2019-01-23 21:09:35 UTC,apport information
1812271,2019-01-23 21:09:36 UTC,apport information
1812271,2019-01-25 13:48:02 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Since this appears to be a kernel issue I'm marking the openssh task as Invalid for now. If there's any reason to think it's a problem in userspace, please change its status back to New."
1812271,2019-01-23 21:09:29 UTC,apport information
1812271,2019-01-18 16:25:45 UTC,apport information
1812271,2019-01-18 16:25:37 UTC,apport information
1812271,2019-01-18 16:25:39 UTC,apport information
1812271,2019-01-18 16:25:42 UTC,apport information
1812271,2019-01-18 13:47:25 UTC,Do you have a reason to think this is a firmware issue? Otherwise the bug should probably be against the linux package.
1812271,2019-01-18 14:05:45 UTC,"@sforshee
Sorry I don't know how to categorize it into a firmware issue or package.
Checked the links (Read our guide or take a tour) but didn't find a clue.
But I should have mentioned it happened on a DELL XPS 8700 but not on any other computers like ThinkCentre M92P or Dell OptiPlex 7060 I've been using for years."
1812271,2019-01-18 15:24:47 UTC,I've changed it to affect the linux package. Please run 'apport-collect 1812271' in a terminal after seeing this issue to attach logs and system information to this bug to aid in diagnosing your issue. Thanks!
1812271,2019-01-18 15:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812271,2019-01-18 16:25:17 UTC,apport information
1812271,2019-01-18 15:26:31 UTC,"Sorry, I just read comment #3 and realized I wasn't very clear. Please make sure you've reproduced the issue on your system before running apport-collect to ensure that logs will contain any information relevant to your issue."
1812271,2019-01-18 16:25:22 UTC,apport information
1812271,2019-01-18 16:25:25 UTC,apport information
1812271,2019-01-18 16:25:28 UTC,apport information
1812271,2019-01-18 16:25:30 UTC,apport information
1812271,2019-01-18 16:25:33 UTC,apport information
1812271,2019-01-18 16:25:35 UTC,apport information
1812271,2019-01-18 16:25:20 UTC,apport information
1812275,2019-09-24 15:46:03 UTC,"Interesting about the event log, can you reproduce the behavior of no event log?"
1812275,2020-08-27 16:11:11 UTC,"if the issue is about making a breaking change, I propose optional parameter to power_off"
1812275,2020-08-27 16:05:20 UTC,@Blake Rouse
1812275,2020-08-27 14:25:25 UTC,"This bug has been open for a long time, with MAAS engineering's explanation that all this is expected behavior.  There may be some doc nuances here, but not enough to warrant this bug.  Closing, please re-open if you disagree, but make a strong case for what the doc should explain if you do, please."
1812275,2019-09-24 16:40:12 UTC,"> Interesting about the event log, can you reproduce the behavior of no event log?
"
1812275,2019-09-24 15:25:40 UTC,"Additionally, does this mean that 'Allocate->Power On' does a deploy that's not actually logged in the event log?"
1812275,2019-09-19 11:54:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1812275,2019-09-24 14:28:07 UTC,"I see no use case for that, as the the cloud-init credentials place on the installed system would now be invalid and the system cannot talk back to MAAS at all."
1812275,2019-09-24 14:10:24 UTC,"I understand this operation could be restricted (for example to only admins) due to security reasons, but I still believe there could be valid reasons for someone to power-on a machine and attempt to access the data that it's in the disk(s) from an installation that maas is not aware of. The case that kicked off this bug was someone automating tasks in their datacenter (an Ubuntu Advantage user)."
1812275,2019-09-24 14:01:13 UTC,This is expected behaviour. You cannot just power on a machine without it deploying. This would break the machine lifecycle and possible allow a user to get another users previous deployment.
1812275,2019-09-24 13:40:23 UTC,MAAS version: 2.6.0 (7802-g59416a869-0ubuntu1~18.04.1)
1812275,2019-01-18 12:49:15 UTC,"On Fri, 2019-01-18 at 09:47 +0000, Björn Tillenius wrote:

> I agree. Having the power-on command to be a subset of deploy in some
> cases (i.e. when the machine is Allocated) is just confusing.
>
> Although, to be fair, they don't seem to quite do the same thing. If
> I
> deploy a machine without any parameters, the UI shows ""Deploy 18.04
> LTS', and the deployment succeeds. If I power on an allocated node,
> the
> UI shows ""Deploying /"" and the deployment fails for some reason.
"
1812275,2019-01-18 09:47:43 UTC,I agree. Having the power-on command to be a subset of deploy in some cases (i.e. when the machine is Allocated) is just confusing.
1812275,2019-09-24 14:50:26 UTC,"On Tue, 2019-09-24 at 14:28 +0000, Blake Rouse wrote:

> I see no use case for that, as the the cloud-init credentials place
> on
> the installed system would now be invalid and the system cannot talk
> back to MAAS at all.
>
> For that use-case rescue-mode is what you want to boot, and from
> there
> you can mount the installed system if needed.
"
1812310,2019-06-01 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812310,2019-08-03 04:17:34 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1812310,2019-08-03 04:17:36 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1812316,2019-09-17 09:15:36 UTC,This was fixed a while ago:
1812316,2019-09-12 15:10:55 UTC,Upstream fix: https://github.com/systemd/systemd/commit/83d4ab5533 (in systemd-242).
1812316,2019-01-18 18:47:49 UTC,"Thanks for reporting this issue, we'll update this bug once we've investigated."
1812316,2019-04-04 18:40:32 UTC,This bug has 14 days remaining until its disclosure date (2019-04-18). Can you give me an update on its status?
1812316,2019-03-04 14:59:02 UTC,CVE-2019-3842 has been assigned by Red Hat to this issue.
1812316,2019-04-05 15:12:06 UTC,systemd upstream has a patch ready that simply uses secure_getenv instead of getenv.
1812317,2019-01-18 06:40:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812317,2019-01-24 23:19:53 UTC,"@mahmoh - do you know if GRUB is the only blocker here? That is, does an Ubuntu kernel otherwise support any of these platforms?"
1812317,2019-01-25 01:03:31 UTC,@dannf it's the first of two I believe. This will allow any kernel to boot but then we hit other problems booting stock kernels. The -snapdrogon kernel is for 410E vs. 835/850.
1812317,2019-02-02 02:31:18 UTC,@dannf it appears the patches have may now have been finally approved?:
1812317,2019-02-03 18:02:15 UTC,"On Fri, Feb 1, 2019 at 7:40 PM mahmoh <email address hidden> wrote:

>
> @dannf it appears the patches have may now have been finally approved?:
>
>   https://<email address hidden>/msg28322.html
"
1812317,2019-03-06 15:20:47 UTC,This bug was fixed in the package grub2 - 2.02+dfsg1-12ubuntu1
1812318,2019-01-18 03:27:32 UTC,It looks like this config is needed: CONFIG_FTRACE
1812318,2019-05-28 13:40:17 UTC,This issue also affects cosmic/linux-kvm.
1812318,2019-10-17 08:52:31 UTC,"Solved on B-kvm with the following commit for bug 1841956:
  UBUNTU: [Config] linux-kvm: CONFIG_FTRACE=y"
1812318,2019-10-17 08:55:43 UTC,Could be found in E-kvm as well
1812318,2020-07-31 08:29:12 UTC,"For the test itself, this can be fixed with https://github.com/torvalds/linux/commit/cbd965bde74c3d0e53798404fd4b9829a68ccec8#diff-71290e3874c89695bb4bc63f892d5c93"
1812334,2019-01-25 10:07:42 UTC,Fix commited x1.3.1-13.
1812334,2019-01-20 05:22:07 UTC,Ok i will try
1812334,2019-01-19 15:53:42 UTC,"So can i move this into royal Rajasthan route and how can i check before
downloading any activity Which tyoe of route."
1812334,2019-01-19 13:44:07 UTC,"The “19032 Yoga Express” activity as a “Read Me First.txt” file. You can read, that this activity is for the “Royal Rajasthan route ( ADI-AII )” route but you still running the NFR route.
Once installed this Activity into the right route “ADI-AII” all worked fine."
1812334,2019-01-19 16:44:34 UTC,"You must download the ADI-AII route (ir_wr-nwr_route) and install it.
If you are looking for the Activity file from ""trainsim"" each downloadable file has a ""View"" option below the title, and allows you to read all files related with the download. Usually, there is a file named ""Read Me First.txt"" that indicate the required route."
1812335,2019-02-27 21:28:46 UTC,"Eric, could you please verify that bug is reproducible on master too?"
1812342,2019-10-25 06:14:24 UTC,"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
purpose of this test is to start looking for old bugs & confirm focal impacted; these bugs are old & upstream issues and will impact very few end-users (impact me thus why chased)
boot up; adjust displays to match my setup (default-right display is below other display)
..
pcmanfm-qt menu can't be seen/used when on lower display - https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1812342"
1812342,2021-02-25 07:38:49 UTC,"I've attempted to re-create this (again) today using Lubuntu hirsute daily (LXQt 0.16) on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1812342,2021-02-23 10:20:21 UTC,"I just swapped my TOP & bottom display positions (a few times) in Monitor.Settings on the dc7700 (which shares displays with 8200 this bug was filed on) which is more confirmation  that I believe this is solved, but I'll endeavour to test on either hp 8200 or d960"
1812342,2021-02-23 10:10:04 UTC,I've tried to re-create this on Lubuntu's hirsute daily (using LXQt 0.16) installed on dc7700 & d755-8 and been unable to.
1812342,2019-12-12 05:45:09 UTC,"Lubuntu 20.04 QA-Test on
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1812342,2019-12-10 02:12:35 UTC,"Lubuntu 20.04 QA-test on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1812342,2019-11-16 17:51:25 UTC,Closed per OP
1812342,2019-11-12 07:00:23 UTC,"Lubuntu 20.04 QA-Test  2019-11-12 test on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1812342,2019-09-27 03:04:46 UTC,19.10 Lubuntu x86_64 qa-test (beta) 2019-09-26.1
1812342,2019-09-27 03:17:23 UTC,"lenovo thinkpad sl510 (c2d-t6570, 2gb ram, i915)   for #13"
1812342,2019-07-12 03:09:07 UTC,"Lubuntu 19.10 QA-Test on hp 8200 mentioned previously
I could NOT re-create this issue today."
1812342,2019-01-18 09:36:54 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1812342,2019-01-18 09:45:30 UTC,"Still on QA-Test (x86_64 on hp8200), if `pcmanfm-qt` is on 2nd display where menu doesn't show, I can use menu shortcuts (eg. ALT+F then T for file->new-tab) and they work. This is useful only if you knew what keys to press. Likewise ALT+F then ENTER produced another open tab. I can use ALT+F(for file, v for view etc) and then arrow-keys and enter to select - but I have to know what I should be navigating for it to work. The function is there, it's just not displaying..."
1812342,2019-02-09 23:41:40 UTC,this needs a re-test; it's not doing it on my installed (& rather modified) lubuntu 19.04 system on d960 I just realized. i don't often qa-test with this box (it's usually running & where I enter comments etc) but has same [vertical] screen placement.  maybe it's related to video driver? or no longer an issue.  i need to re-test
1812342,2019-02-16 02:49:49 UTC,"QA-Test 2019-02-16 on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1812342,2019-07-12 03:24:30 UTC,"continuation of comment #11 (still same QA-test) ...
-- from qa-test comments"
1812342,2019-04-11 08:32:45 UTC,I'm sure I had experienced this on my recent opensuse tumbleweed install (on 8200 box).
1812342,2019-04-25 02:04:54 UTC,FYI: this also occurs on debian buster's weekly ISO of 2019-04-22 06:17
1812342,2019-07-06 02:36:49 UTC,"19.10 QA-test on lenovo thinkpad x201 (i5-m520, 4gb, i915)
with external vga display connected"
1812342,2019-01-18 08:27:21 UTC,-- I've copied the following from my QA-test comments; point is in 2nd paragraph! --
1812342,2019-02-18 00:59:45 UTC,2019-02-17 19:30 QA-Test Lubuntu 19.04 daily (live)
1812347,2019-01-18 08:48:38 UTC,Reproduced as follows on 18.04.1 / Gnome-Shell:
1812347,2019-01-18 08:48:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812348,2019-01-28 15:07:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812348,2019-01-28 15:12:17 UTC,I got the same issue.
1812348,2019-03-08 00:09:25 UTC,"Also affects me, after idling for some time computer is taking a very long time to come back to life."
1812352,2019-12-02 13:04:55 UTC,This bug was fixed in the package linux - 4.15.0-72.81
1812352,2019-11-19 02:49:01 UTC,Verified on Bionic. Works as expected.
1812352,2019-11-14 18:48:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812352,2019-11-06 10:30:13 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-November/105243.html
1812352,2019-11-06 09:34:14 UTC,Test result for B-4.15 after this patch set.
1812352,2019-11-06 09:33:57 UTC,Test result for B-4.15 before this patch set.
1812352,2019-09-18 12:59:29 UTC,"We don't have kselftest in Trusty, mark this as Invalid for it."
1812352,2019-01-18 09:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812352,2019-11-06 10:18:12 UTC,"Xenial will require more work, I will split the test report here (see bug 1851486 for X)"
1812352,2019-01-18 11:06:19 UTC,"For Bionic, it's:
771cbc3bcbb59084766a501772853f2de7009534
10f531f6748228583b8c4244216e9e3f34d47379
a33554401e4746cc33307910a1baad63ce3fd650
42b44c34136857ccdf90ebb1cbc38f2bf0aec7a1
3f4435b5149372b3bbc5acab5c835d490490d6bc"
1812356,2019-01-31 02:33:31 UTC,Triaged as a systemd issue per https://gitlab.freedesktop.org/libinput/libinput/issues/232
1812356,2019-01-18 09:30:39 UTC,This change was made by a bot.
1812356,2019-01-29 03:08:31 UTC,Please report the bug to the libinput developers here:
1812356,2019-01-30 02:57:24 UTC,Reported the bug to libinput developers.
1812356,2019-01-30 03:09:12 UTC,Thanks.
1812356,2019-01-30 03:30:07 UTC,This change was made by a bot.
1812356,2019-01-30 11:07:46 UTC,"Yes, I confirm. The same bug exists on Ubuntu Disco Dingo (development branch), Release 19.04 with libinput --version 1.12.6."
1812357,2019-01-21 10:15:07 UTC,thanks
1812357,2019-01-18 10:59:47 UTC,"Thank you for your bug report. That's an upstream issue, could you report it on https://gitlab.gnome.org/GNOME/gnome-control-center/issues ?"
1812357,2019-01-21 02:40:18 UTC,Thanks for the pointer. A bug was just reported to https://gitlab.gnome.org/GNOME/gnome-control-center/issues as https://gitlab.gnome.org/GNOME/gnome-control-center/issues/351
1812359,2019-01-30 07:22:14 UTC,"1. I did not get what are you saying for laptop, both 18.04.2 and 19.04 working well in laptop with SSD installed"
1812359,2019-01-30 08:00:53 UTC,Comment #57 is an image. Please remember to attach a log instead :)
1812359,2019-01-30 07:11:32 UTC,Also remember to keep the laptop open :) Because the login screen might only ever appear on the laptop screen.
1812359,2019-01-30 08:57:21 UTC,"Note1: Atom D425 machine only has one screen and that screen is the VGA monitor.
----"
1812359,2019-01-30 09:14:27 UTC,Please run:
1812359,2019-01-30 09:20:38 UTC,In the log of comment #62 I can only see the Xwayland crash that is bug 1731911. That probably means gnome-shell started crashing or shutting down earlier so we will need you to search for evidence of the 'gnome-shell' process crashing by following these instructions:
1812359,2019-01-31 03:49:34 UTC,"If I consider 4.19, then which of these files I need to install,"
1812359,2019-01-30 09:45:11 UTC,Please run:
1812359,2019-01-30 10:01:53 UTC,Please also run:
1812359,2019-01-30 10:03:53 UTC,Please also run:
1812359,2019-01-30 10:19:24 UTC,grep . /sys/class/drm/*/enabled
1812359,2019-01-31 02:48:09 UTC,Great! I think I understand the problem now.
1812359,2019-01-31 02:55:50 UTC,"Next, please try some newer kernels (you only have kernel 4.18 with Ubuntu 19.04) from here:"
1812359,2019-01-30 07:13:36 UTC,I've not connected laptop and lcd monitor together with either HDMI or VGA?
1812359,2019-01-30 09:31:20 UTC,"I did,"
1812359,2019-01-31 04:19:37 UTC,"Generally for each version you try you need to install all the packages _except_ the ""lowlatency"" ones."
1812359,2019-01-31 04:42:15 UTC,"Thanks. Please test v5.0 too, and then that's enough."
1812359,2019-02-21 16:13:11 UTC,"For several years now the one and only place to file drm/i915 bug has been
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel"
1812359,2019-02-20 01:58:57 UTC,"daisy,"
1812359,2019-02-19 07:59:10 UTC,Yes I am sure.
1812359,2019-02-19 01:55:53 UTC,"Are you sure about that? This is a kernel bug, not a Mesa bug."
1812359,2019-02-18 08:53:08 UTC,Please file i915 bugs to https://bugs.freedesktop.org
1812359,2019-02-02 06:25:20 UTC,"I've reported a bug,"
1812359,2019-01-31 04:30:46 UTC,grep . /sys/class/drm/*/enabled
1812359,2019-02-02 06:22:48 UTC,"Created attachment 280927
LVDS & VGA status"
1812359,2019-02-01 06:06:41 UTC,We don't need any more logs as this bug is fully understood.
1812359,2019-02-01 05:42:32 UTC,"Okay thanks,"
1812359,2019-01-31 06:41:39 UTC,"Thanks. That's definitely a kernel bug (or a hardware fault, but let's hope a kernel bug)."
1812359,2019-01-31 06:28:46 UTC,"$ uname -r
   5.0.0-050000rc4-generic
grep . /sys/class/drm/*/enabled
   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled
grep . /sys/class/drm/*/status
   /sys/class/drm/card0-LVDS-1/status:connected
   /sys/class/drm/card0-VGA-1/status:connected"
1812359,2019-01-31 06:21:24 UTC,"$ uname -r
   4.20.0-042000-generic
grep . /sys/class/drm/*/enabled
   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled
grep . /sys/class/drm/*/status
   /sys/class/drm/card0-LVDS-1/status:connected
   /sys/class/drm/card0-VGA-1/status:connected"
1812359,2019-01-31 04:44:44 UTC,Oops. Please also run this:
1812359,2019-02-02 06:21:08 UTC,I've installed Ubuntu 19.04 on a NETBOX nT-435/535 and no login screen displayed whenever the VGA is connected to LG monitor.
1812359,2019-01-30 06:50:44 UTC,"For 19.04, I am working on it because I found some strange issue with HDMI too after installing it."
1812359,2019-01-30 08:04:16 UTC,"Oh, now I can access bug 1731911 and it's a red herring so forget that one..."
1812359,2019-01-30 04:47:03 UTC,"Okay,
First thing, Laptop is Dell and cpu architecture is Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz, I have used laptop just to install 18.04.2 and 'Try Ubuntu' for 19.04"
1812359,2019-01-25 09:05:08 UTC,"> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
"
1812359,2019-01-25 08:26:00 UTC,"There are two files in /var/crash, I did, ubuntu-bug MYFILE.crash, after it run, it did not show anything. There are four files:"
1812359,2019-01-25 06:01:51 UTC,"Also, it sounds like there's a chance this problem is caused by something crashing. Please follow these instructions to investigate that:"
1812359,2019-01-25 05:26:39 UTC,Thanks. That new log is nice and small. The errors of possible interest in order are:
1812359,2019-01-25 04:09:43 UTC,I did following:
1812359,2019-01-25 02:32:43 UTC,Thanks. I can still see three potential problems in the log from comment #12:
1812359,2019-01-25 09:12:10 UTC,"No, I could not see anything reported today: https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4"
1812359,2019-01-24 11:12:23 UTC,"journalctl -b | grep Mutter
Jan 24 16:31:22 test gsd-xsettings[1034]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ""org.gnome.Mutter.DisplayConfig"" does not exist"
1812359,2019-01-24 06:33:10 UTC,Actually there's a simpler solution. Please try this:
1812359,2019-01-24 06:18:02 UTC,Thanks.
1812359,2019-01-23 04:24:28 UTC,"At last, I did switching of display manager from gdm to lightdm but after login, nothing appeared on screen, only Ubuntu 18.04 wallpaper."
1812359,2019-01-23 04:10:46 UTC,"I am running Ubuntu on SSD. I've done fresh installation of Ubuntu downloaded from here: http://cdimage.ubuntu.com/bionic/daily-live/current/ but no change
and tried all the previous solution of commenting out WaylandEnable=false and installing haveged."
1812359,2019-01-19 04:58:41 UTC,"I've changed #WaylandEnable=false to WaylandEnable=false and reboot the system,
after splash there is nothing so I entered into VT with Ctrl+Alt+F2,
it shows a message, 'a start job is running for hold until boot process finishes up.'"
1812359,2019-01-30 06:35:03 UTC,Please also remember comments #43 and #44.
1812359,2019-01-24 11:09:27 UTC,"Daniel van Vugt,"
1812359,2019-01-25 09:58:33 UTC,"I've moved all files from /var/crash and reboot system, regenerate crash files."
1812359,2019-01-24 01:54:23 UTC,"daisyd,"
1812359,2019-01-25 11:11:34 UTC,"I did further more steps,"
1812359,2019-01-30 01:46:37 UTC,"Finally, please take a photo of ""no login screen and blank default wallpaper"" so we can understand exactly what you are describing."
1812359,2019-01-30 01:46:01 UTC,Also remember to keep the laptop open :) Because the login screen might only ever appear there.
1812359,2019-01-30 01:45:09 UTC,Thanks.
1812359,2019-01-29 12:14:36 UTC,"Install 19.04 downloaded from here http://cdimages.ubuntu.com/daily-live/current/ and it has same issue like 18.04.2 whenever the external monitor connected to VGA, no login screen and blank default wallpaper."
1812359,2019-01-25 10:01:11 UTC,"While reporting ubuntu-bug _usr_bin_Xwayland.121.crash, when I've clicked on show details,
It shows duplicate of bug https://bugs.launchpad.net/bug/1731911"
1812359,2019-01-29 09:58:02 UTC,How can I install 18.04.2: http://cdimages.ubuntu.com/bionic/daily-live/current/ with no monitors connected. Would it be okay with laptop?
1812359,2019-01-29 09:47:14 UTC,To avoid bug 1727356 you still need to avoid installing 18.04.1. Please only install
1812359,2019-01-29 11:15:11 UTC,"Okay, I did fresh installation of 18.04.2 downloaded from here: http://cdimages.ubuntu.com/bionic/daily-live/current/ in my laptop.
After than I installed SSD into smart station. Issue is same when VGA is connected."
1812359,2019-01-29 07:03:49 UTC,Thanks.
1812359,2019-01-29 05:03:17 UTC,"Also, please allow the system at least 15 minutes to boot before giving up. There might be something slowing it down dramatically making it look like it's hung when it's not. If that's true then we need to see it all in the log."
1812359,2019-01-29 04:57:46 UTC,Thanks but you seem to have made the same mistake again. That log is from recovery mode so is not useful:
1812359,2019-01-29 04:25:09 UTC,"vanvugt,"
1812359,2019-01-29 02:49:31 UTC,"Thanks for your efforts. Over the weekend I also set up Ubuntu 18.04 on some Pineview Atom netbooks, but only found bug 1727356."
1812359,2019-01-28 09:33:24 UTC,"vanvugt,"
1812359,2019-01-28 05:58:52 UTC,@ daisy
1812359,2019-01-29 09:26:16 UTC,@ Daniel van Vugt
1812360,2019-03-15 12:49:57 UTC,"@Canonical, any update available ?"
1812360,2019-08-07 13:20:17 UTC,"------- Comment From <email address hidden> 2019-08-07 09:10 EDT-------
IBM bugzilla status-> closed, Fix Release by Canonical"
1812360,2019-04-04 09:19:28 UTC,------- Comment From <email address hidden> 2019-01-23 06:32 EDT-------
1812360,2019-04-03 18:19:10 UTC,"Sorry for the delay in responding to this.  As Chrisitian correctly assumed in his first paragraph, yes to get this to work for x86 we needed two serial consoles and I assume this was was the case without testing out the second xml snippet.  Just tried it and it worked so will be pushing this to MAAS.  Cheers."
1812360,2019-04-03 16:04:05 UTC,"Thanks for that - I think we are done and have to thank @IBM.
We have pinged MAAS to consider the insight in their next updates."
1812360,2019-02-14 13:41:33 UTC,FWIW
1812360,2019-07-11 17:10:06 UTC,Since MAAS 2.6 supersedes 2.5 - I'm changing to project entry to Fix Released (like 2.6 is).
1812360,2019-01-24 10:57:41 UTC,"Yes, since this looks like a valid alternate way I've already shared this with newell (subscribed him) who is working on LP 1811986 / LP 1811992.
Just shared it with andreserl, too."
1812360,2019-01-24 10:41:19 UTC,"I'd think the use case was mostly for logging to a file.
x86 serial in the past needed some tweaks to be able to log but at the same time be interactive - maybe that was the reason for the double entries."
1812360,2019-01-24 09:59:34 UTC,"So what is the use case? Really having 2 consoles so that one can log like
<console type='pty'>
<target type='sclp' port='0'/>
</console>
<console type='pty'>
<log file='/var/log/libvirt/qemu/{name}-serial0.log' append='off'/>
<target type='sclplm' port='1'/>
</console>"
1812360,2019-01-23 14:13:07 UTC,A 2nd console could be the sclplmconsole.
1812360,2019-01-18 09:52:10 UTC,"To avoid confusion, on x86 this is generated from a libvirt xml that has two contole entries on the same port - one"
1812360,2019-01-18 09:56:20 UTC,"Found it - this is the template they render into for x86 (working)
...
        <controller type='virtio-serial' index='0'>
          <address type='pci' domain='0x0000'
            bus='0x00' slot='0x05' function='0x0'/>
        </controller>
        <serial type='pty'>
          <log file=""/var/log/libvirt/qemu/{name}-serial0.log"" append=""off"" />
          <target port='0'/>
        </serial>
        <console type='pty'>
          <target type='serial' port='0'/>
        </console>
..."
1812360,2019-01-31 19:19:44 UTC,Finally got some time to test out the first xml snippet in #4 above and although I was able to get console output in the VM the log file stopped at:
1812361,2019-01-25 14:01:29 UTC,"heat is also using the public keystone endpoint even with ""use-internal-endpoints"" set to true."
1812361,2019-02-22 09:47:09 UTC,This is somewhat complicated - currently we template:
1812361,2019-02-22 10:41:35 UTC,I think exposing the internal endpoint for keystone and an additional set of keys is a good idea; the admin endpoint is a bit of a legacy concept.
1812361,2019-12-09 10:38:49 UTC,Exposing internal url - https://review.opendev.org/#/c/696997
1812361,2021-02-17 19:46:57 UTC,PR for openstack-dashboard https://review.opendev.org/c/openstack/charm-openstack-dashboard/+/776254
1812363,2019-09-12 14:01:36 UTC,I think this is more of a problem of RDO than kolla.
1812363,2019-11-12 04:18:06 UTC,[Expired for kolla because there has been no activity for 60 days.]
1812364,2020-03-19 22:29:09 UTC,Kibana query: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22OSError:%20%5BErrno%2022%5D%20failed%20to%20open%20netns%5C%22
1812366,2019-01-30 02:08:33 UTC,"The workarond is to use packages for Ubuntu from the following PPA
https://launchpad.net/~certbot/+archive/ubuntu/certbot"
1812366,2019-01-30 01:16:00 UTC,"Just wanted to reinforce that there is a high probability that all Ubuntu LTS servers will start failing to renew Let's Encrypt certificates as the minimum version for certbot should be 0.28 to fix TLS-SNI-01 problems.
https://community.letsencrypt.org/t/how-to-stop-using-tls-sni-01-with-certbot/83210"
1812366,2019-01-30 01:27:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812367,2019-01-20 15:34:34 UTC,Issue with the --clearmodifiers seems to be fixed in v3.20160804.1 (https://github.com/jordansissel/xdotool/releases/tag/v3.20160804.1)
1812367,2019-01-20 16:08:44 UTC,Probably related to https://bugzilla.xfce.org/show_bug.cgi?id=7845 (key press vs. key release).
1812367,2021-01-11 18:37:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812369,2019-01-18 11:14:32 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1812375,2019-08-28 16:04:29 UTC,I believe the machines are already tagged with kerneltesting flags are they not?  This should be sufficient in warning others the machines are in use.
1812375,2019-09-06 03:41:32 UTC,"I think this is a request from server team,
Here are the tag for 3 PowerPC:
  * baltar - Kernel-Team-SRU-Test-System Power9 Boston Reserved
  * entei - Kernel-Team-SRU-Test-System Power8 Reserved kerneltesting embargo-cve-regression-testing-power8
  * modoc - Kernel-Team-SRU-Test-System Power8 Reserved"
1812385,2020-03-24 08:22:59 UTC,KeyError got fixed by the linked review so I'm gonna mark this as Fixed .. although providing a way how to verify plugin's configuration within tempest.conf is still missing - for that I created a new bug: https://bugs.launchpad.net/tempest/+bug/1868683
1812385,2019-01-20 12:46:32 UTC,"Yes, with current code verify-config does not handle the Tempest plugin. We should extend that for plugin but i agree as of now we can catch that error and print appropriate msg."
1812385,2019-01-18 14:33:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/631801"
1812385,2019-01-20 14:30:23 UTC,"Reviewed:  https://review.openstack.org/631801
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=07a572ca175d10fb7366c5015aa28419b76af3c8
Submitter: Zuul
Branch:    master"
1812387,2019-02-14 11:22:16 UTC,"Hi Prasanna,"
1812387,2019-02-13 10:13:20 UTC,Confirmed. LXD repro instructions:
1812387,2019-02-12 07:45:45 UTC,"Reproduction steps again, for reference:"
1812387,2019-02-12 07:42:12 UTC,I've updated the docker image prasannavl/tmux-launchpad-bug-1812387 to only use ubuntu-repo based tmux-plugin-manager.
1812387,2019-02-06 12:00:37 UTC,"Hi Prasanna,"
1812387,2019-01-25 20:59:21 UTC,Reference attachment: tmux.conf
1812387,2019-01-25 09:24:03 UTC,"Hi Prasanna,
thank you for the detailed instructions.
I ran this on Bionic/Cosmic/Disco to get a feeling if tmux recently broke or got fixed.
That is matching versions:
 tmux | 2.6-3ubuntu0.1 | bionic-updates
 tmux | 2.7-1          | cosmic
 tmux | 2.8-2          | disco"
1812387,2019-01-25 20:08:46 UTC,"Hi Christian,"
1812387,2019-01-24 17:53:49 UTC,Note: You probably might want to set `ulimit -c unlimited` before any of the above to make the system generate the core dumps.
1812387,2019-01-24 17:51:43 UTC,"Hi Karl,"
1812387,2019-01-23 11:56:34 UTC,"Hi Prasanna, thanks for the report!"
1812387,2019-01-18 13:54:25 UTC,"StacktraceTop:
 ?? ()
 evbuffer_add (buf=0x55fae21ee6f0, data_in=data_in@entry=0x55fae21d14c0, datlen=0) at buffer.c:1730
 cmdq_print (item=<optimized out>, fmt=fmt@entry=0x55fae1094589 ""%s"") at cmd-queue.c:421
 cmd_run_shell_print (msg=msg@entry=0x55fae21ca3b0 """", job=<optimized out>) at cmd-run-shell.c:68
 cmd_run_shell_callback (job=0x55fae21f1850) at cmd-run-shell.c:131"
1812387,2019-01-25 20:58:51 UTC,Reference attachment: Dockerfile
1812392,2019-05-18 12:33:33 UTC,Ubuntu 18.04.2 LTS with kernel 4.18.0-20-generic all up to date @18/5/2019
1812392,2019-05-21 14:49:17 UTC,Scanner seems not to work afterall so i have to reinstall latest hplip again
1812394,2019-01-18 14:25:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812394,2019-01-18 14:28:06 UTC,"I'm seeing the same issue on Ubuntu 18.04 x86_64 (upgraded from 16.04), with AMD RX580 graphics using amdgpu (with amdgpu.dc=1 set), running the HWE kernel (4.18 )."
1812394,2019-01-18 14:46:09 UTC,I'm running a fresh install of Ubuntu 18.10 with an RX 580 graphics card. Here is my driver info:
1812394,2019-01-18 14:53:15 UTC,"To clarify, I'm able to reproduce this both with Firefox playing back the video in windowed mode and when Firefox plays the video back full screen. As soon as I pause the video (in either mode), the artifact vanishes, so it only occurs during video playback."
1812394,2019-01-18 14:54:14 UTC,"$ lspci -knnv | grep -A10 VGA
2d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3417]
 Flags: bus master, fast devsel, latency 0, IRQ 53
 Memory at e0000000 (64-bit, prefetchable) [size=256M]
 Memory at f0000000 (64-bit, prefetchable) [size=2M]
 I/O ports at f000 [size=256]
 Memory at fe900000 (32-bit, non-prefetchable) [size=256K]
 Expansion ROM at 000c0000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: amdgpu
 Kernel modules: amdgpu"
1812394,2019-01-18 14:56:52 UTC,Tested this on 18.04.1 up to date 18/1/2019
1812394,2019-01-18 23:54:06 UTC,"Setting this option in about:config and restarting Firefox fixes (or works around?) it for me:
layers.acceleration.force-enabled = true"
1812394,2019-01-19 14:32:40 UTC,Setting `layers.acceleration.force-enabled = true` also works around it for me.
1812395,2020-01-30 19:48:41 UTC,Still a problem in 3.4.1
1812395,2020-10-15 21:11:58 UTC,"Noting that in the Angular Staff Catalog (the default for 3.6+) appears to re-fetch the Patron View every time the Patron View tab is selected, therefore showing up to date data every time."
1812407,2019-01-24 02:21:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812407,2019-01-24 02:21:07 UTC,"I think this is a combination of bug 1769383, and some other hover/resize bug that is also mentioned in bug 1812996 and bug 1812998."
1812409,2019-05-20 14:46:09 UTC,Confirmed in webclient 3.1.10.
1812410,2019-03-27 17:08:35 UTC,@Kevin (thenewmanium)
1812410,2019-03-27 14:58:18 UTC,I'm pushing on Dell to push on Intel. Not getting a lot of traction on that but I'll update if I do. Definitely have this issue on all my Dell R640s with X550s though.
1812410,2019-03-25 18:51:20 UTC,@Kevin (thenewmanium).
1812410,2019-01-27 05:46:15 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc3 kernel[0]."
1812410,2019-01-18 17:49:27 UTC,apport information
1812410,2019-01-18 17:49:25 UTC,apport information
1812410,2019-01-18 17:49:18 UTC,apport information
1812410,2019-01-18 17:49:16 UTC,apport information
1812410,2019-01-18 17:49:14 UTC,apport information
1812410,2019-03-25 17:33:05 UTC,"Hi, this issue affects my hosts as well. I have about 40 hosts running Intel X550s that were working fine on kernel 4.4.0-141-generic with regard to negotiating 10Gb automatically. Suddenly after booting into 4.15.0-43-generic they automatically negotiate at 1Gb. I have to use ethtool to force them to 10Gb."
1812410,2019-01-18 17:49:09 UTC,apport information
1812410,2019-01-18 17:49:12 UTC,apport information
1812410,2019-01-18 16:37:55 UTC,adding additional log information.
1812410,2019-01-18 16:38:17 UTC,adding additional log information
1812410,2019-01-18 16:38:41 UTC,adding additional log information
1812410,2019-01-18 17:00:19 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812410,2019-01-18 17:49:21 UTC,apport information
1812410,2019-01-18 17:49:01 UTC,apport information
1812410,2019-01-18 17:49:03 UTC,apport information
1812410,2019-01-18 17:49:05 UTC,apport information
1812410,2019-01-18 17:49:07 UTC,apport information
1812410,2019-01-18 17:48:58 UTC,apport information
1812411,2019-01-18 19:50:52 UTC,"seems likely related to bug 1762748, and maybe that change overlapping with bug 1666853 ?"
1812411,2019-01-18 20:09:36 UTC,"Hi Scott,"
1812411,2019-01-22 14:25:17 UTC,"There are 2 issues at play here:
a. bug 1666853: grub2 does not work correctly in 16.04 with ext4 filesystems larger than 2TB.  This appears to be fixed in 18.04, but the bug is not currently  marked as fixed there."
1812417,2020-09-28 16:28:02 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: master
Review: https://review.opendev.org/751178
Reason: Abandoning in favor of https://review.opendev.org/#/c/738242/"
1812417,2020-06-16 16:29:28 UTC,Work around for console access (local)
1812417,2020-04-21 13:23:13 UTC,"@mightywomble: when you create an instance, you can add an ssh key to it (MicroStack automagically does this if you use the microstack.launch command), and then you can ssh to the machine with the key. Since cloud instances often don't have a default password, this is often more useful than a console."
1812417,2020-04-18 17:14:25 UTC,"From a webinterface point of view, if this isn't working, how would I do access the console from the command line? Without a console installing machines is a bit of a problem surely?"
1812417,2020-02-24 16:44:31 UTC,"@INMD: with the current build of MicroStack, I believe that console is broken. To fix it, we'd need to add a daemon to the snapcraft.yaml."
1812417,2020-02-18 19:57:20 UTC,"Brief update on this: getting the console working is still on the roadmap, but it's behind several other priorities."
1812417,2020-02-17 10:26:55 UTC,I am now rejected in 127.0.0.1.  So how do I change the ip to try?
1812417,2020-02-06 22:02:45 UTC,I am also having the same issue on Ubuntu 18.04. Has anyone found a work around to get the console working in the mean time?
1812417,2019-09-11 20:23:31 UTC,"Seconded. There doesn't appear to be any way to expose the VNC console in the current (candidate, edge, beta) builds nor to forward the correct ports to make that work."
1812417,2019-01-18 16:59:07 UTC,Github comment from @javacruft:
1812417,2020-02-19 03:16:50 UTC,Are you saying it's hard to use now?Or is there any other way to use it?  I'm going to micro-stack the Windows server.
1812417,2019-11-11 19:44:41 UTC,"The console does not appear to be configured (I can not `grep -R` any ""\[spice\]"" or ""\[vnc\]"" or ""\[rdp\]"" in the system).
I tried an example configs from https://docs.openstack.org/nova/latest/admin/remote-console-access.html but I `netstat -plnt` I do see any running console service."
1812418,2019-01-18 17:02:27 UTC,"Per the discussion on github (https://github.com/CanonicalLtd/microstack/issues/39), we've temporarily turned off the material theme."
1812422,2019-01-18 22:33:51 UTC,Thanks for filing this ticket.
1812422,2019-07-20 12:00:14 UTC,"I moved a significant amount of other functionality into the Formatter class, so I'm now comfortable with the amount of documentation coverage I gave this feature."
1812422,2019-07-08 03:05:43 UTC,"I spent some time duplicating Isaac's investigation. We can't get consistent behavior across Python versions, but we can make it possible to turn off sorting."
1812422,2019-04-14 18:46:23 UTC,"Unfortunately, looking into this a bit more, there isn't currently a way to make this sane across the board. It appears we could successfully force preserved ordering in html.parser, but not lxml and html5lib (at least below Python 3.7). We can't really control how those libraries return attributes, with that said, maybe in Python 3.7 and above, you could theoretically just avoid sorting, as I imagine dictionary usage in lxml and html5lib would then be ordered (unless they opt to sort)."
1812422,2019-03-07 18:48:02 UTC,"Ah, yeah, that does make sense. Forced sorting adds some predictability. I like the idea of preserving order though. If I get some time, I'll probably throw together the merge request."
1812422,2019-03-07 18:22:27 UTC,"Isaac,"
1812422,2019-03-07 16:48:45 UTC,"Interestingly, in Python 3.7 dictionaries are ordered by default now. So a good test would be to see if Python 3.7 gives you what you're looking for. At this point, since that is the future, I think it makes sense just to make them ordered by default in Beautiful Soup."
1812422,2019-02-02 03:34:27 UTC,"That sounds like a good compromise, I'll try it out."
1812422,2019-01-28 22:08:04 UTC,What about preserving the order the attributes were inserted via collections.OrderedDict instead?
1812426,2019-01-19 17:02:35 UTC,just mentioning it because there are a number of Fedora-specific bugs related to text
1812426,2019-04-25 15:13:41 UTC,"As this has been backported to 0.92.x in https://gitlab.com/inkscape/inkscape/merge_requests/647, seems this is 'fix committed'."
1812426,2019-01-18 19:56:52 UTC,"crash not reproduced on Windows 10, Inkscape 0.92.4 (5da689c313, 2019-01-14)"
1812426,2019-01-19 09:42:10 UTC,are you by any chance running Fedora?
1812426,2019-01-19 14:47:39 UTC,"@Alvin, indeed I am running fedora but I use inkscape from flathub so it's not really fedora."
1812426,2019-04-21 10:44:39 UTC,"Okay, looks like it was fixed and the fix mentioned here: https://github.com/flathub/org.inkscape.Inkscape/issues/30"
1812426,2019-04-19 10:54:08 UTC,"Florian, are you still having the issue? Could you post what version of Fedora you are on?"
1812435,2019-01-18 20:25:42 UTC,Here is the snapcraft.yaml file that goes with it
1812443,2019-01-19 13:26:48 UTC,"it is true. I have exactly the same problem. I have to use the old
dosemu versions that work wonderfull under ubuntu 18.04. For exemple
dosemu_1.4.0+svn.2080-1_amd64.deb I have already pointed it out. But
that has not been corrected. Very sincerely Patrice Lemonnier"
1812445,2019-04-09 22:49:46 UTC,"The output track angle should use same IC/pad angle (or 90 deg rounded from it):
1) If IC / pad angle = 0 / 90 / 180 or 270deg => use 0 / 90 / 180 and 270deg;
2) If  ....          = 45 / ...               => use 45 ...."
1812452,2019-01-29 21:00:49 UTC,"Helo Brian
I come back.
Not easy when the printer I need to test is not mine...
---------------

> Why I have message from HPLIP 3.17.10 and 3.18.12 ???
"
1812452,2019-01-29 21:11:17 UTC,previously :
1812452,2019-01-29 21:15:26 UTC,"sorry
Don't read the end of the previous post !
(copy error)"
1812452,2019-01-29 21:19:15 UTC,"even if I try to pause / start the task, no print ..."
1812452,2019-01-29 21:24:48 UTC,"$ ippfind -T 5
ipp://NPI19F58A.local:631/printers/Laserjet"
1812452,2019-01-21 21:15:09 UTC,"Sorry, msg send and after I don't succeed to post !
I don't need HPLIB ?"
1812452,2019-01-29 21:35:06 UTC,I try again :
1812452,2019-01-29 23:16:07 UTC,"> sudo lpadmin 1217 -v ipp://NPI19F58A.local:631/printers/Laserjet
> -m drv:///hpcups.drv/hp-laserjet_professional_m1217nfw_
"
1812452,2019-01-29 23:41:50 UTC,Hello Brian
1812452,2019-01-30 09:33:55 UTC,"> I post the reply for these 3 commands.
"
1812452,2019-01-30 12:39:09 UTC,lpadmin -p m1217 -v hp:/net/HP_LaserJet_Professional_M1217nfw_MFP?ip=192.168.1.100 -E -m drv:///hpcups.drv/hp-laserjet_professional_m1217nfw_mfp.ppd
1812452,2019-01-31 19:22:03 UTC,"Hello Brian
I delete (via Gnome Shell) the 2 printer ""m1217"" and ""m1217b""."
1812452,2019-01-31 19:23:01 UTC,"All is ok
We can print from LibreOffice Writer and Calc, and from Firefox and Thunderbird, on the ""1217"" default printer.
Thanks"
1812452,2019-01-31 20:35:23 UTC,"> I try :
>
> sudo lpadmin -p 1217 -v ipp://NPI19F58A.local:631/printers/Laserjet -E -m everywhere
>
> AND IT'S WORK !!!
"
1812452,2019-01-21 18:06:10 UTC,The situation is:
1812452,2019-01-28 10:50:14 UTC,Good luck on Tuesday!
1812452,2019-01-27 20:18:48 UTC,"Brian
I'm not at home.
I will go to my friends about this printer, Tuesday."
1812452,2019-01-21 21:17:14 UTC,hp-check.log
1812452,2019-01-24 14:13:17 UTC,Didier - thanks for the level of detail and the print dialog image.
1812452,2019-01-21 21:18:22 UTC,"if I don't need HPLIP,
how can I uninstall HPLIP ?"
1812452,2019-01-21 21:44:34 UTC,Didier - you have said nothing about what happens when you follow the advice about cups-browsed.conf I gave. Does a printer appear in Firefox?
1812452,2019-01-21 22:37:28 UTC,Hello Brian
1812452,2019-01-21 23:15:17 UTC,That is really strange. What do get with
1812452,2019-01-21 23:25:22 UTC,"This printer called ""LaserJet"" in Firefox. What happens when you try to print to it?"
1812452,2019-01-21 23:49:04 UTC,"Hello Didier,"
1812452,2019-01-23 20:32:33 UTC,Hello Brian
1812452,2019-01-27 12:43:37 UTC,"Didier,"
1812452,2019-01-23 20:49:07 UTC,"Hello Brian
=======================================
I expect that all you want to do is print, so we will use HPLIP to set up a print queue rather than have it done automatically with cups-browsed."
1812452,2019-01-18 22:50:46 UTC,"this is a NETWORK (RJ45, not WiFi) printer.
------------------"
1812452,2019-01-18 22:53:05 UTC,HP plugin :
1812452,2019-01-19 15:53:57 UTC,"Your are managing the printer in two ways, which is why you have duplicate entries."
1812452,2019-01-21 17:27:15 UTC,"Ubuntu PC and HP printer are not mine.
So I cannot go and check every days..."
1812452,2019-01-24 13:49:05 UTC,"Hello Didier,"
1812452,2019-01-23 20:35:55 UTC,lpstat -l -e
1812457,2019-03-20 21:42:29 UTC,Thanks!
1812461,2020-03-07 15:33:24 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1812462,2019-01-19 09:51:31 UTC,"similar to:
https://bugs.launchpad.net/inkscape/+bug/1809676 ?"
1812462,2019-01-19 10:03:06 UTC,"reproduced on Windows 10, Inkscape 0.92.4 (5da689c313, 2019-01-14)
using a blank preferences file"
1812462,2019-03-27 05:39:24 UTC,"Confirmed behavior on first try with 0.92.3 on Ubuntu 18.04.
Cannot reproduce in 1.0alpha (3a1866ab31, 2019-03-25), after dozens of attempts."
1812462,2019-03-27 05:50:56 UTC,"Closing as fixed since it is no longer reproducing in trunk.  I skimmed through git log for src/xml/ but didn't spot an obvious commit that would have fixed it.  There has been quite a bit of cleanup and code strengthening, so perhaps the general code improvement fixed it."
1812464,2019-02-21 14:41:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812466,2019-03-31 23:50:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812466,2019-01-19 04:40:36 UTC,Another reasonable solution is to ask isc-dhcp packagers to change the dhclient hook script `/etc/initramfs-tools/lib/etc/dhcp/dhclient-enter-hooks.d/config`.
1812468,2019-01-22 07:57:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1812470,2019-05-08 14:22:40 UTC,"doh: forgotten the internal xfer case
now fixed as well."
1812472,2019-02-05 16:42:52 UTC,"Thanks, any methods to reproduce this to help identify the race would be appreciated."
1812479,2019-02-15 15:25:26 UTC,Stop running all ceph containers on control nodes...
1812479,2019-07-04 12:44:35 UTC,We lose the whole platform setup when we do the suggested volume/folder cleanup (cinder backend etc ...)
1812480,2019-01-25 09:04:04 UTC,">  * Fix CAF integer-underflow
"
1812480,2019-05-06 17:03:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812480,2019-05-06 17:04:23 UTC,Please update VLC so I can stop using a third party PPA for the latest version.
1812480,2019-06-07 07:47:19 UTC,vlc 3.0.7 was released fixing another 20+ security issues. So please update to 3.0.7 instead.
1812480,2019-07-22 09:43:55 UTC,"Will this ever be updated for Bionic?
I don't like the sound of ""remote code execution exploit.""
Apt version is now vulnerable, best way to install/update as of now appears to be snap."
1812483,2019-01-22 18:41:19 UTC,"thinking about the curve and looking at the filter implementation, I think I got why you're referring to brake/softStart using the alphaBetaFilter as a ""hack"". the generated curves just don't match acceleration (deceleration respectively).
From what I understood, brake/softStart/spinback could just use a simple acceleration formula:
rate(time) = accel.factor * (time - startTime)"
1812483,2019-02-15 14:45:29 UTC,"I just updated the description to include another related brake issue.
If I adopt this bug I think both issues can be solved in on PR."
1812483,2019-01-19 14:56:20 UTC,It is probably time to move this hack into the engine to make it available inside the GUI.
1812483,2019-01-19 16:21:59 UTC,"the quick fix I have in mind is just one line, like here:
https://github.com/mixxxdj/mixxx/pull/1226/files#diff-9289ba7fe799f555352e9653196f4b00R1417"
1812483,2019-01-19 14:58:22 UTC,https://bugs.launchpad.net/bugs/1692261
1812500,2019-04-16 21:21:50 UTC,https://github.com/snapcore/snapcraft/pull/2534
1812500,2019-04-16 21:22:11 UTC,"discard comment #1, wrong bug"
1812500,2019-04-16 22:19:45 UTC,Mind trying with my slightly modified yaml to trigger snapcraft 3.0 behavior? (setting a base) and using the snapcraft snap instead?
1812500,2019-04-16 22:21:19 UTC,"At the time of this writing, --use-lxd is only available on snapcraft 3.4, currently in the candidate channel. You can omit the --use-lxd if you want snapcraft from the stable channel which default to the a different underlying build tech."
1812500,2019-08-04 05:01:29 UTC,I also am having this issue. Is there any work around or do I need to use the dump plugin instead?
1812500,2019-08-04 06:08:44 UTC,My code is available here: https://github.com/trampster/Ropu if you want to reproduce this exactly
1812500,2019-08-06 01:49:19 UTC,"My solutions is multiproject, that is there are two dotnet projects with a solution (.sln) file that ties them together."
1812500,2019-08-26 13:06:17 UTC,This works in 18.04
1812500,2019-08-26 13:11:43 UTC,"This bug has been marked as Invalid as it cannot be reproduced with the detail provided.
If this issue is still occurring feel free to open a new bug or re-open this one with enough detail (host OS, versions of software used, ...) to be able to reproduce."
1812500,2019-08-28 05:25:32 UTC,"Sorry you didn't reproduce it, because I already switched to using the dump plugin because the dotnet one didn't work. I am using ubuntu 18.04"
1812500,2019-08-28 05:26:23 UTC,I had given up waiting
1812506,2019-01-20 08:38:04 UTC,"When I insert a blank DVD (or CD) a new icon appears on the desktop (bottom right on my attachment),
in the nautilus sidebar i see the DVD, if i click the new icon i see the window bottom left but i don't have the message 'You have just inserted ...'
also if I specified 'ask what to do'"
1812510,2019-01-20 12:05:02 UTC,Screenshot from acer laptop
1812510,2019-01-19 20:07:50 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1812516,2019-01-20 13:04:46 UTC,There seem to be a workaround for that: https://trac.wxwidgets.org/ticket/17244
1812516,2019-01-20 13:11:19 UTC,"jp-charras, make sure you have the archive in ""Рабочая папка"""
1812516,2019-01-20 13:35:56 UTC,"OK.
It happens on wxWidgets 3.04, not on wxWidgets 3.1.1
Looks like is is fixed in wxWidgets."
1812516,2019-01-21 01:08:22 UTC,"Fixed in revision 3a1e66dba3e4fa7b658d30b742e9bc66b7fac896
https://git.launchpad.net/kicad/patch/?id=3a1e66dba3e4fa7b658d30b742e9bc66b7fac896"
1812516,2019-01-21 07:51:18 UTC,"Unfortunately, the bug is not fixed (W7, wxWidgets 3.04).
The archive is still empty: files named ""Рабочая папка.xxx"" are not stored in archive"
1812516,2019-01-21 15:04:06 UTC,"Hi JP-  That part is not fixable in the same way as this bug report.  URI encoding of the input files results in archive names that are encoded with a string of '%xx' blocks.  This is unreadable to me, so I suspect others would not like it."
1812516,2019-01-21 15:44:10 UTC,"Hi Seth,"
1812516,2019-01-20 04:15:40 UTC,This appears to be a wx issue but we might get around it using a different archive method in v6
1812516,2019-01-20 13:01:53 UTC,I cannot reproduce this issue on W7 32 bits
1812522,2019-02-13 13:46:45 UTC,"Ok, getting the master from github, using"
1812522,2019-02-11 17:47:38 UTC,"ah you only need the header files! so you don't need any other packages but libcaffe-cuda-dev?
we got ubuntu 18.04, and coda 10, so we need to get this built from source..."
1812522,2019-02-15 05:31:25 UTC,I'm sorry I didn't make it clear that I just needed the header files. libcaffe-cuda-dev was the only package I needed.
1812522,2019-02-11 15:44:41 UTC,"I'd publish my source .dsc if I had one.
I only installed the pre-built binaries myself.
- sudo apt install libcaffe-cuda-dev
- edited /usr/share/caffe/CaffeTargets-release.cmake"
1812522,2019-02-11 09:56:26 UTC,"Hi Lenin,"
1812522,2019-02-11 14:56:05 UTC,"The original package might work because the dependencies are not resolved until the deb package is created.
https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/caffe-contrib/1.0.0-8ubuntu2/caffe-contrib_1.0.0-8ubuntu2.dsc"
1812522,2019-02-11 15:27:34 UTC,"Unfortunately not, even when patching away gcc-6 deps, replacing the gcc version in debian/rules, and dropping the nvidia-cuda 9 dependency."
1812522,2019-02-11 08:35:08 UTC,Hi Jesse
1812522,2019-02-08 20:10:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812522,2019-02-11 12:08:53 UTC,Do you have a debian source package that is already fixed/patched as .dsc link that I can just dget?
1812522,2019-02-11 12:09:21 UTC,"Out of interest, what do you need it for? I have some photogrammetry people here that asked for it..."
1812523,2019-03-04 17:41:39 UTC,"Here's a screencast that I took just now, since the issue is still ongoing as of today."
1812523,2019-03-04 17:42:15 UTC,Screencast to help visualize the issue more clearly.
1812523,2019-09-28 09:07:25 UTC,"If you're using Ubuntu 18.04 LTS, bug #1775971 is for updating gpaste to 3.28.3 in Bionic, which fixes two crashes, one with emptying history and one with image support."
1812524,2019-01-20 09:30:26 UTC,What is your printer model?
1812524,2019-01-21 01:13:19 UTC,"Oh, I should have noted that, right,  HP LaserJet 5 and HP DeskJet 5650A.  I realize both are older printers, but using CUPS and using various available drivers, work fine, such as the guten variants."
1812524,2019-01-21 09:52:38 UTC,"If it's a matter of simply enabling printing, the Debian 9.6 packages or 3.18.12 in backports should be sufficient. OTOH, if testing the HPLIP installer is the objective, I have no idea why it fails."
1812525,2019-02-18 09:48:21 UTC,"Alternate is to use socket.SocketIO class instead of _fileobject, verifying if it will cause any regression."
1812527,2019-05-08 00:55:42 UTC,"Hi, guys! I saw that this problem has been fixed. My system was updated today(apt-get update/upgrade), but I'm still facing the crashes. I'm not familiar with this, but how do I force an update to benefit of this fix? Sorry for this question."
1812527,2019-05-03 01:23:42 UTC,"Thanks. I was going to backport and patch it today, but having it done while I sleep is good too."
1812527,2019-05-02 19:29:49 UTC,Upstream cherry-pick is ready at https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/527
1812527,2019-05-02 19:17:25 UTC,"Daniel, thanks for the finding..."
1812527,2019-05-02 10:18:25 UTC,"Oh, actually there was a formal fix done for this exact bug upstream in the 3.30 series. We should use that:"
1812527,2019-05-02 09:33:55 UTC,Good news:
1812527,2019-04-30 02:22:03 UTC,It appears we still get crash reports for this from the latest gnome-shell version 3.28.3+git20190124-0ubuntu18.04.1
1812527,2019-04-09 21:48:07 UTC,"Same problem here, and I have absolutely nothing related to Android installed. When I switch workspaces, occasionally the system flashes and all screens disappear, but all workspaces are correctly displayed after 2-3 seconds. Rarely a lot more crashes and the login screen reappears."
1812527,2019-04-15 07:33:02 UTC,"Yep, no crashes so far with Animation disabled."
1812527,2019-04-10 00:07:26 UTC,"This problem also affects me with Zoom. I am also using a Dell Precision 5520 with Intel HD Graphics, and disabling animations in Tweaks / Appearance / Animations fixes the problem for me."
1812527,2019-03-14 13:35:22 UTC,"I'm also having the same problem with the same configuration: Ubuntu 18.04.2 and GNOME 3.28, but the solution of Fabrizio Bertoglio (fabriziobertoglio) #28 aliviated the problem."
1812527,2019-03-28 09:04:34 UTC,"Agreed - I've experimented using different desktop switching methods, and the only thing that seems to work is to have another window on the same desktop as the emulator, and ensure this is active prior to changing desktops.  The trouble is I rarely remember to do this, so I've no way of knowing if it works 100%."
1812527,2019-05-08 01:45:24 UTC,"The fix is not released yet. At the top of the bug you will find ""Bionic  In Progress""."
1812527,2019-03-25 17:55:54 UTC,"I have tested without gnome extensions and the same happens to me.
I've also tried the theory of ekimai by switching workspaces with mouse scroll on right bottom corner, unfortunately with the same crash."
1812527,2019-03-17 02:20:23 UTC,"On my end, I haven't been able to reproduce this so far with Ubuntu Appindicators disabled. It's very stable for me now. I am not 100% sure this is the fix for me, time will tell. But it's definitely more stable and possibly even fixed now."
1812527,2019-03-15 16:44:35 UTC,"I have a theory, and it isust a theory..."
1812527,2019-04-19 17:28:05 UTC,"I experienced this issue as well. The scenario is same all the time.
When I'm on a Skype CALL and try to switch my workspace to the Skype workspace, it either hangs or logs me out of the system.
Please let me know if I can provide anything to help fix this bug, this is very crucial to me."
1812527,2019-05-08 01:48:43 UTC,"Also, since the bug was only in 3.30.0 and older (fixed in 3.30.1), that makes it Invalid for cosmic and later. Because cosmic and later never had the bug and never needed a fix."
1812527,2019-05-14 22:31:35 UTC,"Enabling this plugin is the easiest way to work around this issue in bionic.
https://extensions.gnome.org/extension/1328/disable-workspace-switch-animation/"
1812527,2019-05-08 05:13:14 UTC,"No, the fix is not yet available."
1812527,2019-03-12 08:59:43 UTC,"Also, my Android Emulator version info:"
1812527,2019-06-06 09:33:48 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1812527,2019-06-06 09:33:24 UTC,This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.1
1812527,2019-05-31 10:04:40 UTC,Thanks for your efforts :)
1812527,2019-05-31 10:03:30 UTC,"It would appear that something has changed in the Android emulator, and it's less likely to be the cause of the crash."
1812527,2019-05-31 09:37:04 UTC,"Thank you, Ahmed Mamdouh.
After your suggestion, I update gnome-shell.
Finally, it won't be crash.
I was waitting for a long time, and can not use ""workspace"".
Now I can use multi workspaces again."
1812527,2019-05-29 20:10:56 UTC,"package : gnome-shell 3.28.4
verification-done-bionic"
1812527,2019-05-08 05:02:41 UTC,"My ubuntu 18.04 have already been updated to the latest state!
But it still crash when I swich workspace.
Is any package I need to install to solve this bug? Or other suggestion?"
1812527,2019-05-28 21:40:26 UTC,"Hello Jean-Francois, or anyone else affected,"
1812527,2019-05-28 08:43:13 UTC,"In my experience, there's no such thing :)"
1812527,2019-05-28 08:31:13 UTC,"The fix is not yet available for testing. We are glad you no longer experience the crash, but that's probably just luck."
1812527,2019-05-28 08:13:48 UTC,I can confirm - this is fixed with the latest Gnome update.
1812527,2019-05-15 01:31:38 UTC,"The fix has ""landed"" in git, meaning it will be in the next 18.04 update of gnome-shell. But I don't know when that will be."
1812527,2019-05-12 22:27:01 UTC,"I'm seeing the same message `st_widget_get_theme_node called on the widget [0x559c32c8cc50 StWidget] which is not in the stage.` even updating individual gnome-shell / *gjs packages to eoan (gnome-shell 3.32.1) although it does not seem to actually crash gnome-shell but rather ""reload"" it (It notifies me that application is ""ready""). It happens almost everytime I switch among windows, even with all extensions disabled."
1812527,2019-05-11 18:54:52 UTC,"After update (Ubuntu 14.04.2 LTS; 3.28.2, GNOME 3.28.2) it works flawless!"
1812527,2019-05-08 09:57:49 UTC,"Thanks, Daniel! I subscribed to the bug to be notified on release.
Waiting for it. Nice work, guys!"
1812527,2019-05-28 08:53:39 UTC,That's great news.
1812527,2019-03-12 08:48:26 UTC,I can confirm that the crash is 100% reproducible with no Gnome extensions installed.
1812527,2019-01-22 09:11:11 UTC,Bug 1812780 suggests the regression started with gjs 1.52.5-0ubuntu18.04.1
1812527,2019-03-08 01:50:15 UTC,Thanks for the reminder...
1812527,2019-02-21 20:48:12 UTC,"@Pavel++
This also helps me out too. Thanks!"
1812527,2019-02-18 13:09:20 UTC,Disabling animations seemed to resolve it for me too. But now switching workspaces just feels very odd without it.
1812527,2019-02-18 12:51:51 UTC,"I had the same, without using any Android emulation. When changing workspace, the gnome-shell was actually freezing and then restarting. Sometimes it could kill the session."
1812527,2019-02-14 09:22:23 UTC,"@Pavel - That's awesome!
Thanks for the workaround."
1812527,2019-02-12 21:23:38 UTC,I can confirm the same bug on 18.04 and Android Studio + running AVD. Disabling system animation by Tweaks / Appearance / Animations works!! It does not crash anymore...
1812527,2019-02-05 14:06:49 UTC,"I'm seeing this same problem, and on my end I am not using the Android emulator. The only apps I use on a regular basis that are always open are the following:"
1812527,2019-02-05 02:36:13 UTC,"Crashing here as well, and I don't have the Android emulator running. It's happening seemingly randomly when switching between workspaces."
1812527,2019-02-25 16:55:46 UTC,"Just an update - I do still get the occasional crash without animations, but it's much less likely."
1812527,2019-01-29 10:13:13 UTC,"I can confirm the problem here too.  I'm currently completely unable to use the emulator, and developing on hardware devices for testing."
1812527,2019-01-22 10:03:42 UTC,"I can't find any relevant change to mutter or gnome-shell. If the bug is caused by a change in gjs then I guess the problem would be that gjs previously would not try calling functions on NULL objects, and now it does...?"
1812527,2019-01-22 09:47:43 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee"
1812527,2019-01-22 09:36:46 UTC,"The offending line of JavaScript is the one that says ""Window gone"". I guess maybe a NULL pointer?"
1812527,2019-01-22 09:20:20 UTC,Generalized the bug title to cover the common aspects between this and bug 1812780.
1812527,2019-01-21 07:26:46 UTC,Everyone please follow the steps in comment #2.
1812527,2019-01-21 07:17:24 UTC,"Same issue here [https://answers.launchpad.net/ubuntu/+question/677918]. Please see my answer, hope it helps."
1812527,2019-01-21 05:55:06 UTC,"I am also seeing this problem, which seemed to manifest itself after a recent update. By experimenting, I've determined that there seems to be a segfault in libmutter-2.so.0.0.0 each time the workspace changes (when the Android emulator is running)."
1812527,2019-01-22 10:15:41 UTC,"And an upstream bug:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/927"
1812527,2019-03-10 22:22:27 UTC,"I faced this problem first when I was using skype and zoom. Both in shared screen mode.
Using Android Emulator, my Ubuntu are crashing too."
1812527,2019-02-27 16:47:43 UTC,"I think we need to completely remove Android Emulation from the title and description. I never use that, nor have I ever, and I see this crash constantly. It's EXTREMELY frustrating."
1812527,2019-03-01 09:41:15 UTC,Indeed this is not related to Android and it should be better upstream. Thanks Daniel.
1812527,2019-03-07 20:28:01 UTC,I have a Dell Precision 3510 with Radeon HD 8830M/R7 M465X and Intel HD Graphics 530 (radeon and i915 drivers) running Ubuntu 18.04.2.
1812527,2019-03-07 11:44:17 UTC,"I'm using a Dell Precision 7530, with Quadro P1000 running NVidia drivers Version 396.54."
1812527,2019-03-07 02:00:45 UTC,"@Daniel, I understand that you want to reproduce it. However, if you aren't experiencing this bug, then that tells me you don't have a hardware configuration that is affected by it. If you're affected, reproducing it is very easy - simply use the keyboard shortcut designated for switching up or down to another workspace. Every time I do this, I have a one in five chance of GNOME crashing. It's so common that I have no chance of NOT reproducing it."
1812527,2019-03-07 01:46:08 UTC,I use 18.04 all day every day with multiple workspaces and do not encounter this crash. However if I am to fix it then I need to know how to reproduce it.
1812527,2019-03-07 01:44:37 UTC,"Jeremy,"
1812527,2019-03-06 14:11:06 UTC,"@Daniel,
Android Emulator version:
28.1.9-5346014
It was packaged with IntelliJ IDEA (Android Studio)"
1812527,2019-03-06 13:53:55 UTC,"@Daniel, this bug has absolutely nothing to do with using an Android Emulator. I literally get this crash every five minutes, and I've never used emulation or virtualization of any kind on either of my machines. I think the Android Emulator was just a red herring."
1812527,2019-02-28 01:47:32 UTC,Done. I think this bug should now be discussed upstream where a fix would occur and there are people who know the code:
1812527,2019-03-06 09:28:03 UTC,"Which ""Android Emulator"" are people using to see this bug?"
1812527,2019-03-06 08:40:34 UTC,Curious how this crash only exists on 18.04 (Gnome 3.28). Not on later releases.
1812527,2019-03-05 19:45:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812527,2019-03-03 22:00:54 UTC,"Anonymized, gzipped and attached."
1812527,2019-03-02 15:40:14 UTC,Attached.
1812527,2019-03-02 14:22:02 UTC,Can anyone affected post a the result of
1812527,2019-03-01 17:17:01 UTC,Issue was solved for me by disabling animation between workspaces https://extensions.gnome.org/extension/1328/disable-workspace-switch-animation/
1812527,2019-03-01 09:43:07 UTC,"By the way, in my case, the track does not show ""self=NULL"".  It's just empty:
gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed()"
1812527,2019-03-06 08:43:40 UTC,Although there was 1 (out of 7139) instance of the crash reported in version 3.30.1-2ubuntu1.18.10.2. I guess that suggests it was fixed around Gnome 3.30.1-ish.
1812527,2019-01-21 03:15:31 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1812529,2019-01-20 11:16:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812535,2019-01-28 09:32:15 UTC,"Fixed in revision fd0381ea09c08f7c488e55656cf0f956e26a280e
https://git.launchpad.net/kicad/patch/?id=fd0381ea09c08f7c488e55656cf0f956e26a280e"
1812535,2019-01-21 13:13:54 UTC,It might be better to create a short screencast that shows this instead of a static image.
1812535,2019-01-21 13:32:41 UTC,It is probably also a good idea to add a screenshot of your PNS settings.
1812540,2019-01-20 07:57:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/631957"
1812540,2020-01-10 21:52:50 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/631957
Reason: replaced by 701548"
1812543,2019-01-22 16:24:36 UTC,This bug was discussed in the OSA weekly meeting 22/01/2019 and it was agreed that the ceph example is unclear and the page needs refactoring.
1812543,2019-01-22 20:20:07 UTC,That are good news.
1812544,2019-01-22 00:05:24 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1812554,2019-01-20 10:23:48 UTC,lol
1812554,2019-01-21 23:54:17 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1812554,2019-02-28 10:25:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812555,2019-08-20 01:35:30 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1812561,2019-02-12 10:54:02 UTC,"Selwyn, as the latest version of Ubuntu is based on 4.19.x, to confirm this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?"
1812561,2019-02-12 11:03:52 UTC,"Sorry I don't understand, could you clarify?"
1812561,2019-04-14 04:17:28 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1812561,2019-05-08 09:23:13 UTC,"Hi Christopher, the committed fix can be seen at https://github.com/torvalds/linux/commit/d92f2c59cc2cbca6bfb2cc54882b58ba76b15fd4"
1812561,2019-07-09 04:17:31 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1812561,2019-05-09 02:07:46 UTC,"Selwyn, to clarify, have you tested the commit noted in #31 with your hardware and confirmed it fixes the issue?"
1812561,2019-05-09 18:16:39 UTC,"Yes, the issue is not present anymore in the mainline kernel 5.1. :)"
1812561,2019-02-11 22:30:14 UTC,"Selwyn, one may follow the below to confirm results for your hardware:
https://wiki.ubuntu.com/Kernel/KernelBisection"
1812561,2019-05-08 09:35:14 UTC,"Sorry about that Christopher, I didn't understand what you meant in #28.
I have tested on the latest version of 19.04 on the 'default' kernel 5.0.0-13-generic and this issue is still present."
1812561,2019-02-11 21:54:44 UTC,"There should be multiple dmesg attachments, do I have to make them public or something? For me the following are shown:
dmesg-2-systemctl-suspend-keywake.txt
dmesg-2-usbcore-dyndbg.txt
dmesg-core.txt
dmesg-devices.txt
dmesg-freezer.txt
dmesg-none.txt
dmesg-processors.txt"
1812561,2019-01-21 04:12:43 UTC,"Selwyn, thank you for reporting this and helping make Ubuntu better."
1812561,2019-02-11 14:20:25 UTC,"Selwyn, given the workaround never worked, this isn't confirmed a usb problem (although could still be due to usb)."
1812561,2019-02-11 13:47:00 UTC,Christopher:
1812561,2019-02-11 09:17:32 UTC,"Christopher, the workaround is invalid so I removed it. Btw. should I retry sending the email? I did not get any reply."
1812561,2019-02-01 15:29:44 UTC,The delivery status gives:
1812561,2019-02-01 10:39:23 UTC,"Thanks again Christopher! I could not send the email though, the email address ""<email address hidden>"" seems invalid. Any ideas?"
1812561,2019-01-30 20:48:29 UTC,"Alright went through all steps! For the suspend command I replaced `pm-suspend` with `systemctl suspend`, since I don't have the first, hopefully the latter is okay too."
1812561,2019-01-30 19:55:53 UTC,"Thank you for your replies Christopher & Kai-Heng, sorry for the slow reply I'm trying to find time to debug and figure out how to debug."
1812561,2019-01-22 05:18:26 UTC,"If disabling wakeup on XHC helps, this means USB device wakes the system up."
1812561,2019-01-22 04:58:11 UTC,"Selwyn, could you please provide all of the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?"
1812561,2019-01-21 18:31:02 UTC,"Thanks for the info, I've reproduced this on the latest kernel and updated the tags!"
1812561,2019-01-20 13:00:12 UTC,This change was made by a bot.
1812561,2019-02-11 19:47:44 UTC,"What? I spend an hour going through that page, all information is in the attachments of the post. Anyways this is confirmed to be a regression: https://marc.info/?l=linux-usb&m=154915973623396&w=2"
1812563,2019-01-20 15:07:40 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1812563,2019-04-25 13:37:26 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1812563,2019-06-25 04:17:35 UTC,[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]
1812566,2019-01-20 16:24:29 UTC,"The attachment ""sphinxsearch.service"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1812569,2019-01-20 16:59:33 UTC,apport information
1812569,2019-01-20 17:30:12 UTC,This change was made by a bot.
1812569,2019-01-20 16:59:36 UTC,apport information
1812569,2019-01-20 16:59:35 UTC,apport information
1812569,2019-01-20 16:59:34 UTC,apport information
1812569,2019-01-20 16:59:32 UTC,apport information
1812569,2019-01-20 16:59:29 UTC,apport information
1812569,2019-01-20 16:59:31 UTC,apport information
1812569,2019-01-20 16:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812569,2019-01-20 16:59:31 UTC,apport information
1812569,2019-01-20 16:59:24 UTC,apport information
1812569,2019-01-20 16:59:22 UTC,apport information
1812569,2019-01-20 16:59:26 UTC,apport information
1812569,2019-01-20 16:59:28 UTC,apport information
1812569,2019-01-20 16:59:26 UTC,apport information
1812573,2019-03-30 13:03:00 UTC,"Thanks for spotting, I have forwarded it to Debian (see upstream bug watch)."
1812574,2020-02-10 23:28:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812575,2019-06-30 13:50:44 UTC,"You should start Unetbootin from terminal - type this command:
sudo QT_X11_NO_MITSHM=1 /usr/bin/unetbootin"
1812582,2019-04-15 12:05:56 UTC,sh hplip-3.19.3-plugin.run file
1812582,2019-05-02 09:56:33 UTC,"Hi Francesconorth,"
1812582,2019-04-19 11:33:13 UTC,Get the following error see attached
1812582,2019-04-19 09:26:50 UTC,"Hi Francesconorth,"
1812582,2019-04-17 22:03:45 UTC,"1) Uninstalled hplip-3.17.1
2) Did a fresh install of hplip-3.19.3
3) Installed the plugin"
1812582,2019-04-17 04:56:21 UTC,"Hi Francesconorth,"
1812582,2019-04-16 21:40:15 UTC,So did that and then tried to print a test page.
1812582,2019-04-15 12:04:42 UTC,"Hi Francesconorth,"
1812582,2019-01-29 00:38:23 UTC,"I also tried hplip 3.19.1, it just can't download the plugin, so I've downloaded and installed without problems, however, the hplip installation stops at the plugin installation."
1812582,2019-03-29 21:21:57 UTC,Note that's with Mint 19.1 which 3.19.3 is supposed to supoprt
1812582,2019-03-29 21:20:42 UTC,Just tried 3.19.3 - same issue as before
1812582,2019-03-07 12:49:06 UTC,This problem also apply to Ubuntu Bionic Beaver.
1812582,2019-01-29 20:35:29 UTC,"Yes you are correct, its just the plugin that doesn't install.
Will hplip support Mint 19.1 officially? I see in the latest release you have added support for other distros."
1812582,2019-01-20 19:37:41 UTC,HP Check log
1812582,2019-01-28 21:11:52 UTC,"Just to say tried hplip  3.19.1. I know it doesn't say Mint 19.1 is supported in the release notes, but I thought I might as well give it a try."
1812582,2019-01-21 21:50:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812582,2019-01-21 21:41:31 UTC,"Hi, I've got the same problem, I've got:
error: Python gobject/dbus may be not installed
error: Plug-in install failed.
 then the script stops and a widow with: lug-In install failed appears."
1812582,2019-03-29 21:26:06 UTC,HP check log
1812583,2019-01-21 15:42:42 UTC,Here's the error message from Apttermlog.txt:
1812583,2019-01-21 15:54:39 UTC,/usr/bin/tl-paper is part of texlive-base. Moving ...
1812585,2019-01-20 19:54:02 UTC,jscheffl@hp840g1:~$ python3 /usr/share/hplip/doctor.py
1812589,2019-02-02 01:39:40 UTC,"I believe this has been fixed in the configparser source, thanks to Jason R. Coombs (https://github.com/jaraco/configparser/issues/17)."
1812589,2019-03-24 02:43:44 UTC,I suspect this was the cause of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865359
1812589,2019-02-01 23:26:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812589,2019-02-01 23:25:55 UTC,This just cost me four hours on Ubuntu 18.04.
1812589,2019-02-01 23:27:10 UTC,"More specifically, if I do"
1812593,2019-01-21 03:24:57 UTC,Please try uninstalling these extensions and then tell us if the bug still occurs after they are gone:
1812593,2019-01-27 15:11:00 UTC,I was seeing this same warning.  The only overlap of extensions with the list above and my list (I only use 3 extensions) is '<email address hidden>'.
1812593,2019-01-31 06:57:38 UTC,The status should remain Incomplete until the original reporter has answered comment #2.
1812593,2019-03-11 10:45:57 UTC,"Hi,
I believe my problem is related to this bug report. I am running Ubuntu 18.04.2 with GNOME 3.28.2, intel graphics and dual screen. The /var/log/syslog file keeps on expanding out of control. I believe this is happening when the screen is locked. If the screen is locked for a long time, it is impossible to unlock it (it becomes kind of frozen). Eventually, the syslog file fills the whole disk (it grows well beyond 100 GB) and the system does not boot any longer. Also when the screen is locked the system keeps on cycling between turning on and off the monitors."
1812593,2019-03-12 02:05:49 UTC,"^^^
That is bug 1772677. Not this one."
1812593,2019-03-14 02:04:10 UTC,Possibly related to bug 1812266?
1812593,2019-03-14 02:06:36 UTC,You can test the proposed bionic fix for bug 1812266 using this:
1812593,2019-05-13 04:17:27 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1812594,2019-08-05 16:37:42 UTC,"The verification of the Stable Release Update for lubuntu-default-settings has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1812594,2019-07-31 08:34:51 UTC,"Hi Chris Guiver,"
1812594,2019-08-05 16:37:33 UTC,This bug was fixed in the package lubuntu-default-settings - 0.54.3
1812594,2019-07-31 11:52:48 UTC,You were spot on apt-ghetto.
1812594,2019-07-31 06:14:39 UTC,"`whereis lxlock` produces no results (ie. ""lxlock: \n"")"
1812594,2019-07-31 04:34:56 UTC,"I have tested 0.54.3 on a fully updated Bionic system and following the testcase, I was able to lock the screen successfully with CTRL-ALT-L. This was equivalent to running `light-locker-command -l`."
1812594,2019-07-31 05:21:55 UTC,"Sorry I hadn't noticed your comment here Walter.
No, I was afraid it'd cause the reason the 18.04.2 couldn't be used be void, and as updating wasn't specifically mentioned I didn't fully update!  (yeah I know this mentally created confusion as to how this test was supposed to prove anything without updates, but I let that slide...).
Updating now as stated in irc."
1812594,2019-07-31 05:07:58 UTC,"Chris, is that a fully updated Bionic?"
1812594,2019-07-31 04:57:39 UTC,Virtual box VM created on 19.10 host (sony vaiocrap)
1812594,2019-07-30 21:53:19 UTC,"Hello Chris, or anyone else affected,"
1812594,2019-07-31 06:11:50 UTC,"full upgraded 18.04.1 installed VM on sonycrap, rebooted & logged in"
1812594,2019-07-29 01:58:54 UTC,Uploaded to the queue.
1812598,2019-06-16 18:30:53 UTC,"Maxime,"
1812598,2019-03-02 07:16:48 UTC,"It's not the same thing as flags. Flags are supposed to be visual reminders, but more detailed. In the end, flags could be replaced by another text box for explaining what to do, and a visual reminder, as we have now. But I agree the amount of the transaction set to ""remind"" should be calculated in the Total if it has a past date, and not calculated if the date is in the future. You could also add another status, ""Void"", to mark a transaction and not display its amount in the balance, this could be useful in case of non-cashed checks and all the other cases where it's important to register a void transaction."
1812598,2019-01-30 12:02:09 UTC,"your wish seems close to flags:
https://bugs.launchpad.net/homebank/+bug/1600356"
1812598,2019-03-10 17:20:57 UTC,"Thanks kjdfofghdfrke; you've described a good picture of the complete/desired functionality, which I think agree with. So there's a few tickets"
1812609,2019-01-21 05:30:13 UTC,This change was made by a bot.
1812609,2019-01-21 05:41:59 UTC,"It has miraculously fixed itself... I had installed the synaptic drivers, rebooted and no joy the first time round. After rebooting just now, the device is being picked up."
1812609,2019-03-07 09:12:43 UTC,"Please remove ""apci*"" kernel parameters, and attach dmesg."
1812613,2019-07-12 16:18:08 UTC,This should be fixed in Ubuntu 19.04.
1812618,2019-01-21 08:00:13 UTC,This change was made by a bot.
1812618,2019-11-13 23:30:43 UTC,Cosmic has gone EOL.
1812620,2020-10-13 22:48:12 UTC,This bug was fixed in the package linux-hwe - 5.3.0-68.63
1812620,2020-08-10 14:17:23 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'."
1812620,2020-08-31 13:57:07 UTC,This bug was fixed in the package linux - 5.4.0-45.49
1812620,2020-08-31 07:39:10 UTC,Just noticed that this issue still exists in B/hwe (5.3)
1812620,2020-08-31 07:33:47 UTC,"Temporary workaround reverted:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=13720efa8789e63a65b6ea9251ce70b0df500d3a"
1812620,2020-08-26 08:57:35 UTC,This bug was fixed in the package linux - 5.8.0-16.17
1812620,2020-08-11 02:47:17 UTC,The net test was skipped on all of the instances with B-gke-5.3.0-1033.35
1812620,2020-08-10 16:54:37 UTC,"Ran the tests with -proposed kernel on a 1 CPU system, tests now pass:"
1812620,2020-09-04 08:35:20 UTC,Passed with F-kvm 5.4.0-1022.22
1812620,2020-08-06 10:00:58 UTC,Fix sent to mailing list:
1812620,2020-08-05 21:50:32 UTC,"Only occurs on systems that cannot set affinity to CPU 2 and CPU 3 because the test tries to do this and fails. Tut tut, bad test."
1812620,2020-07-27 21:43:34 UTC,Focal 5.4(SRU 2020/06/29)
1812620,2020-07-16 10:28:37 UTC,"With Oracle 5.4.0-1021
This is failing on VM.Standard2.1 but passed with VM.Standard2.16"
1812620,2019-12-11 09:47:24 UTC,Found on E-AWS 5.3.0-1009.10-aws
1812620,2019-11-26 03:57:39 UTC,"For D-AWS , it's not failing on all nodes.
Take ARM64 instances for example, this has passed on a1.2xlarge but not a1.large / a1.medium"
1812620,2019-10-14 09:31:26 UTC,"For this issue on D-Azure 5.0
5.0.0-1023.24"
1812620,2019-08-08 03:44:42 UTC,"Saw this on 5.0 D-AWS (at lease on c4.large, m4.large)"
1812620,2019-07-30 07:07:48 UTC,Didn't see this on 5.0 B-AWS
1812620,2019-03-11 10:47:17 UTC,Found in 4.18 Bionic AWS as well.
1812620,2019-01-21 08:00:27 UTC,This change was made by a bot.
1812620,2020-08-07 03:19:17 UTC,"I would like to note that although Eoan and Disco has already reached their end-of-life, we still have 5.3 / 5.0 kernel for clouds."
1812622,2020-08-18 17:02:39 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1812622,2020-07-24 03:42:04 UTC,Issue found on B-5.3 generic kernel with google cloud (didn't see this issue with other gcp / gke cloud kernels)
1812622,2019-11-26 03:20:41 UTC,Didn't see this on D-AWS
1812622,2019-10-14 09:22:56 UTC,Didn't see this with D-Azure 5.0 kernel.
1812622,2020-09-22 02:29:37 UTC,fib_tests.sh / fib-onlink-tests.sh failed with Error: Unknown device type. on gkeop-5.4
1812622,2019-07-22 04:03:15 UTC,Error message on D-KVM:
1812622,2019-10-07 09:08:11 UTC,Didn't see this with B-GCP 5.0 kernel
1812622,2019-03-11 10:51:42 UTC,Found in 4.18 Bionic AWS as well.
1812622,2019-10-14 11:40:35 UTC,"Still exist on D-KVM 5.0
5.0.0-1020.21"
1812622,2019-04-18 16:00:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812622,2019-04-18 15:44:53 UTC,Also found in cosmic/linux-azure:
1812622,2019-07-16 17:10:22 UTC,also occurs on AWS-disco 5.0.0-1011.12 : amd64
1812624,2019-01-31 11:57:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812624,2019-01-31 11:57:59 UTC,"This also affects cosmic/linux-aws:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux-aws/20190115_155144_26f2e@/log.gz"
1812624,2019-01-31 15:58:35 UTC,"I'm not aware of any reason that the PAGE_POISONING configs should differ from master for any derivative kernels.  Po-Hsu, if you want to submit config patches for those affected, that would be great."
1812624,2019-02-19 22:38:47 UTC,"OK will do.
Thanks for the input."
1812624,2019-02-21 22:40:32 UTC,"It looks like azure disco is affected too, change the status accordingly."
1812624,2019-03-12 10:31:24 UTC,This bug was fixed in the package linux-aws - 4.18.0-1011.13
1812624,2019-04-02 10:47:03 UTC,This bug was fixed in the package linux-kvm - 4.18.0-1009.9
1812624,2019-04-02 10:47:46 UTC,This bug was fixed in the package linux-azure - 4.18.0-1014.14
1812624,2019-04-11 15:42:33 UTC,This bug was fixed in the package linux-azure - 5.0.0-1002.2
1812624,2019-06-11 07:20:07 UTC,For D/linux-kvm https://lists.ubuntu.com/archives/kernel-team/2019-June/101294.html
1812624,2019-07-16 21:53:01 UTC,"I can confirm that the PAGE_POISONING, PAGE_POISONING_NO_SANITY, and PAGE_POISONING_ZERO config options are set in the linux-kvm 5.0.0-1011.12 kernel in disco proposed. Thanks!"
1812624,2019-07-22 20:28:34 UTC,This bug was fixed in the package linux-kvm - 5.0.0-1011.12
1812630,2019-06-06 06:45:14 UTC,As I introduced a new txn type with 5.3 (see #1756681)
1812630,2019-05-20 06:11:09 UTC,or that the multiple edit or another menu let you transform normal txn to transfer
1812630,2019-03-19 12:39:27 UTC,"what you want to do already exists:
- go into the account you may have imported internal xfer
- menu tools/check internal xfer"
1812630,2019-03-19 11:51:09 UTC,"OK, I understand. What's the recommended way of importing transactions with transfers between accounts, then?"
1812630,2019-02-24 10:23:24 UTC,"Internal xfer is not just a payment mode, this is why it is intentionally disabled in that dialog (and when you mass edit transaction)."
1812630,2019-03-28 18:08:27 UTC,"sorry, my bad, this only check the existing internal xfer
what you would need is a process that detect possible internal xfer from account A and account B
an maybe popup you to assign if multiple match"
1812633,2019-01-25 07:40:26 UTC,"You may use `version-script:` to forge your own command line.
Maybe default options of `git describe` aren't good for your project."
1812633,2019-02-11 15:01:23 UTC,"Super, thanks for the tip."
1812636,2019-01-23 10:11:00 UTC,Spotted on Cosmic.
1812636,2019-05-08 11:30:47 UTC,"The test was blacklisted in ACT:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=a02ccfa8d"
1812636,2019-01-21 11:00:06 UTC,This change was made by a bot.
1812638,2020-04-28 19:47:58 UTC,This bug was fixed in the package linux - 4.15.0-99.100
1812638,2020-04-14 06:38:40 UTC,Passed with X-hwe 4.15 i386.
1812638,2020-03-16 03:27:30 UTC,https://lists.ubuntu.com/archives/kernel-team/2020-March/108270.html
1812638,2020-04-08 02:37:32 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812638,2019-12-16 14:34:47 UTC,affects 5.0 kernel as well on power (D) linux-generic
1812638,2019-08-30 06:18:06 UTC,Issue can be found on X-4.15 as well (i386)
1812638,2019-01-21 11:30:06 UTC,This change was made by a bot.
1812638,2020-02-25 10:35:58 UTC,"On B-5.3 P8, test result is a bit different:
 # selftests: net: reuseport_bpf_numa
 # ---- IPv4 UDP ----
 # send node 0, receive socket 0
 # send node 1, receive socket 1
 # libnuma: Warning: Cannot read node cpumask from sysfs
 # ./reuseport_bpf_numa: failed to pin to node: No such file or directory
 not ok 3 selftests: net: reuseport_bpf_numa # exit=1"
1812638,2020-03-10 10:27:17 UTC,"More detail on B-5.3
* Skipped on i386 with no api support
* Passed on ARM64
* Passed on AMD64
* Passed on P9
* Failed with P8
The output on B-5.3 P8 is:
 # selftests: net: reuseport_bpf_numa
 # ---- IPv4 UDP ----
 # send node 0, receive socket 0
 # send node 1, receive socket 7
 # ./reuseport_bpf_numa: node id/receive socket mismatch
 not ok 3 selftests: net: reuseport_bpf_numa # exit=1"
1812640,2019-01-21 11:25:28 UTC,the podman containers where this was observed are rhel8/f28-based containers
1812640,2019-01-24 14:04:13 UTC,This is likely due to a mismatch between iptables inside the container f28 (1.6.x which uses the traditional iptables modules) vs the iptables on the rhel8 host which uses iptables based on the nftables backend.
1812645,2019-01-21 12:00:07 UTC,This change was made by a bot.
1812645,2019-01-23 10:26:16 UTC,Spotted on Cosmic i386 as well:
1812653,2019-01-21 12:19:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812653,2019-01-21 12:10:11 UTC,"StacktraceTop:
 ?? () at ../../../../glib/gmem.c:169 from /tmp/apport_sandbox_7vu82sol/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_bytes_unref (bytes=0x559a430510f0) at ../../../../glib/gbytes.c:337
 g_variant_unref (value=0x559a431eaaf0) at ../../../../glib/gvariant-core.c:638
 g_hash_table_remove_all_nodes (hash_table=hash_table@entry=0x559a430e8980, notify=notify@entry=1, destruction=destruction@entry=1) at ../../../../glib/ghash.c:552
 g_hash_table_remove_all_nodes (destruction=1, notify=1, hash_table=0x559a430e8980) at ../../../../glib/ghash.c:1103"
1812655,2019-01-21 12:24:44 UTC,"StacktraceTop:
 wnck_screen_finalize (object=0x55a3ed0dc360) at screen.c:501
 g_object_unref (_object=0x55a3ed0dc360) at ../../../../gobject/gobject.c:3346
 block1_data_unref (_userdata_=0x55a3ecfb8420) at ../../src/daemon/main.vala:45
 block1_data_unref (_userdata_=0x55a3ecfb8420) at main.c:170
 _vala_main (args=<optimized out>, args_length1=<optimized out>) at ../../src/daemon/main.vala:96"
1812655,2019-01-25 06:43:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812663,2019-01-21 21:06:20 UTC,The issue is an upstream one and should be reported on https://gitlab.gnome.org/GNOME/gedit/issues
1812663,2020-07-12 22:37:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812665,2019-02-13 13:16:03 UTC,"We found the issue, it turns out OS brick and HP's AJ76A HBA don't play nicely together."
1812665,2019-03-05 07:00:33 UTC,Code changes need to be done in os_brick/initiator/linuxfc.py
1812665,2019-06-12 07:30:11 UTC,"Hi Shefi,"
1812665,2019-06-12 07:33:05 UTC,"We are currently working on this issue.
It is being tracked via: https://bugs.launchpad.net/cinder/+bug/1809249
Also submitted code changes for community review: https://review.opendev.org/#/c/657585/"
1812665,2019-09-27 09:03:31 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1812665,2019-10-04 08:51:57 UTC,This issue was fixed in the openstack/cinder 14.0.2 release.
1812665,2019-10-04 13:00:16 UTC,This issue was fixed in the openstack/cinder 13.0.7 release.
1812665,2019-10-24 14:30:24 UTC,This issue was fixed in the openstack/cinder 12.0.10 release.
1812669,2019-04-23 20:49:10 UTC,"An upload of ruby2.5 to bionic-proposed has been rejected from the upload queue for the following reason: ""Sorry, needs rebased on ruby2.5 2.5.1-1ubuntu1.2 in the security pocket""."
1812669,2019-06-13 15:26:52 UTC,i think this is done.
1812669,2019-03-11 14:57:53 UTC,"The verification of the Stable Release Update for ruby2.5 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1812669,2019-03-11 14:57:47 UTC,This bug was fixed in the package ruby2.5 - 2.5.1-5ubuntu4.2
1812669,2019-01-27 19:28:01 UTC,This bug was fixed in the package ruby2.5 - 2.5.3-3ubuntu3
1812669,2019-03-01 20:33:26 UTC,"Hello Andreas, or anyone else affected,"
1812669,2019-02-20 21:39:26 UTC,In unapproved
1812669,2019-03-06 09:09:15 UTC,It built! https://launchpad.net/ubuntu/+source/ruby2.5/2.5.1-5ubuntu4.2
1812672,2019-02-04 11:11:46 UTC,"Reviewed:  https://review.openstack.org/633482
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=131497868f442bcf06bc199a36e2962b8ac0018d
Submitter: Zuul
Branch:    master"
1812672,2019-02-21 09:15:54 UTC,"Reviewed:  https://review.openstack.org/637148
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=503fe150ed94d9b499137e60b90868eb86d82bcb
Submitter: Zuul
Branch:    stable/18.11"
1812672,2019-02-04 12:30:15 UTC,"Reviewed:  https://review.openstack.org/633218
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=fc68571c51d81fd3e9786faebce3946564920ab5
Submitter: Zuul
Branch:    master"
1812672,2019-02-04 13:01:15 UTC,"Error occur also on stein, I already submit a fix to oslo.cache and now waiting the merge to backport it to rocky.
https://review.openstack.org/#/c/634457/"
1812672,2019-02-04 14:31:18 UTC,"@herveberaud, I'm still able to recreate the error with your change: https://paste.ubuntu.com/p/9vYwwm3Byw/"
1812672,2019-02-15 09:13:55 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/637148"
1812672,2019-02-15 09:14:09 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/637149"
1812672,2019-02-21 09:16:25 UTC,"Reviewed:  https://review.openstack.org/637149
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=9092ab63678962bb942b7e0ff03438c32147d60a
Submitter: Zuul
Branch:    stable/18.11"
1812672,2019-02-04 12:30:24 UTC,"Reviewed:  https://review.openstack.org/633219
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=13eca55803c8320a401ccf923c29b7bfeb85d0fc
Submitter: Zuul
Branch:    master"
1812672,2019-02-21 21:16:06 UTC,And available in the charm store.
1812672,2019-04-24 14:15:03 UTC,"Reviewed:  https://review.opendev.org/640500
Committed: https://git.openstack.org/cgit/openstack/oslo.cache/commit/?id=caf5443de8ff4ff353d741a125f782c67f579f52
Submitter: Zuul
Branch:    stable/rocky"
1812672,2019-04-24 15:03:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/655468"
1812672,2019-05-10 15:18:36 UTC,"Reviewed:  https://review.opendev.org/655468
Committed: https://git.openstack.org/cgit/openstack/oslo.cache/commit/?id=38dcffa904c7d4b5bd61896b972c1e16477fcc56
Submitter: Zuul
Branch:    stable/queens"
1812672,2019-05-16 06:34:03 UTC,This issue was fixed in the openstack/oslo.cache 1.30.4 release.
1812672,2019-05-31 14:21:12 UTC,This issue was fixed in the openstack/oslo.cache 1.28.1 release.
1812672,2020-09-04 11:55:21 UTC,"As the change that got all of the Cloud Archive releases marked Fix-Released was backported from master, I'm marking the Ubuntu bug task as fix-released as well"
1812672,2019-01-30 13:31:07 UTC,"Package-wise this is fix-released for disco (stein). We're only switching to apache2+mod_wsgi in stein from a package pov because it's a pretty big switch to SRU, plus the rocky packages are py2 by default. https://launchpad.net/ubuntu/+source/nova/2:19.0.0~b1~git2018120609.c9dca64fa6-0ubuntu4"
1812672,2019-02-21 21:15:53 UTC,This is now fixed in the nova-cloud-controller stable/18.11 branch.
1812672,2019-01-30 13:28:27 UTC,Yeah sahid is focused on it. Btw thedac is going to look at your other bug.
1812672,2019-01-24 13:57:26 UTC,There's a big difference in the base classes of _MemcacheClient that are resolved at run-time when comparing Junien's testcase in comment #1 vs the code being executed via nova-api-os-compute in the failure case. Also showing arguments here for the failing case since I have them handy:
1812672,2019-01-30 12:48:25 UTC,Charm review: https://review.openstack.org/633219
1812672,2019-01-21 14:50:01 UTC,Note that I have not been able to reproduce this outside of the nova-api-os-compute context. The following works fine in python3 REPL :
1812672,2019-01-21 16:04:31 UTC,I can't find so far any relevant detail which could help to fix the issue.
1812672,2019-01-22 06:54:14 UTC,Rephrasing my comment.
1812672,2019-01-22 11:00:18 UTC,I understand your point regarding Python versions but still I don't see any incompatible changes and commenting that line should not make differences.
1812672,2019-01-22 12:39:03 UTC,Looks good :
1812672,2019-01-30 13:18:58 UTC,Oh wow ok pretty big changes. Thanks !
1812672,2019-01-22 21:34:44 UTC,"It seems we should be ok with oslo_cache.memcache_pool. Check the documentation at (search for ""backend ="") at: https://docs.openstack.org/nova/rocky/configuration/sample-config.html"
1812672,2019-01-23 07:00:18 UTC,Sharing the config anyway : https://pastebin.canonical.com/p/4WNpkff4vN/
1812672,2019-01-24 01:11:16 UTC,I was able to recreate this with juju by relating nova-cloud-controller to memcached.
1812672,2019-01-22 17:45:17 UTC,"Can you share nova.conf of controller? I would say you have configured 'memcached_servers'. Our charm (charm-nova-cloud-controller) is configuring the backend to use 'oslo_cache.memcache_pool' where based on nova/cache_utils.py, the right value nowadays would be 'dogpile.cache.memcached'."
1812672,2019-01-24 01:42:27 UTC,This is an interesting one and proving difficult to debug. It seems like the overrides in _MemcacheClient are having unintended side-effects with python3. I'll look some more tomorrow but for now adding upstream to the bug. I wonder if we can get Alexander Makarov to take a look as he added this code segment way back in 2015.
1812672,2019-01-24 01:45:23 UTC,"Note that commenting out __new__ = object.__new__ above does seem to ""fix"" things but I'm not sure if that is the correct fix."
1812672,2019-01-24 14:06:37 UTC,I'm guessing this is something to do with eventlet monkey patching.
1812672,2019-01-24 14:19:22 UTC,This recreates with Junien's testcase + eventlet.monkey_patch():
1812672,2019-01-24 15:18:38 UTC,In Ubuntu we should probably be running nova-api-os-compute under apache2 with mod_wsgi anyway and as a bonus it will bypass this issue. I just tested successfully with the attached site enabled. Add /etc/apache2/sites-enabled/wsgi-openstack-api-os-compute.conf; sudo systemctl stop nova-api-os-compute && sudo systemctl restart apache2.
1812672,2019-01-30 06:23:03 UTC,Where's the commit ? I'm curious :)
1812672,2019-01-24 01:15:12 UTC,"To add to comment #8, that of course was a queens deployment, created an instance, upgraded nova-cc to rocky, then 'openstack server list' errored out and nova-api-os-compute.log contains the traceback: https://paste.ubuntu.com/p/nj93928wXt/ (should be the same as what Junien posted but posting again as the formatting is better)."
1812675,2020-01-10 21:08:11 UTC,Branch w/ release notes pushed:
1812675,2020-01-10 21:10:31 UTC,Too many tabs open...  Comment above was meant for bug #1859241.  Note however the code for bug #1859241 does address the custom permission group tree display in patron search on the Angular side of things.
1812676,2019-02-26 06:41:26 UTC,"After reporting this in issue in 2015 (https://bugs.launchpad.net/cloud-init/+bug/1494040),
and describing the root cause being the migrator module coupled with the #cloud-config default of
 'migrate: true'"
1812676,2019-02-27 19:44:45 UTC,The current committed patch LGTM.
1812677,2019-09-02 09:09:29 UTC,"Hi,"
1812677,2019-10-07 09:28:42 UTC,"How recent is your kolla-ansible code? We added a retry to this command, and backported it to Rocky 6 months ago: https://review.opendev.org/#/c/648318/."
1812678,2019-01-21 15:34:25 UTC,"Hi Jeroen,"
1812680,2020-02-05 23:33:18 UTC,"Yep, confirmed here too..."
1812680,2020-02-05 08:48:21 UTC,I have the same issue on my gre tunnels.
1812680,2020-02-05 08:22:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812683,2019-02-04 06:15:07 UTC,This bug was fixed in the package rhythmbox-plugin-alternative-toolbar - 0.18.3-1
1812683,2019-03-20 14:22:45 UTC,I have tried reproducing it both on disco (without the prevent-reordering patch) and stock bionic with german locale installed.
1812683,2019-03-20 12:32:59 UTC,"I can easily trigger it this way on bionic (stock install, no music on disk)
$ sudo apt install language-pack-gnome-de
$ LANG= LANGUAGE= LC_ALL=de_DE.UTF-8 rhythmbox"
1812683,2019-03-19 08:30:22 UTC,I'll try looking at it again tomorrow. I tried multiple combinations yesterday and no luck so far…
1812683,2019-03-06 14:13:50 UTC,"(the upstream issue has some detail on the code impacted, it looks like it could be a gtk/binding issue, unless the rb-plugin is doing something stupid that gtk doesn't like)"
1812683,2019-03-06 14:12:11 UTC,"Didier, as discussed could you take over that one? The upstream commit of disabling column reordering in !en locale is not a fix, we should get at the bottom of it.
That's also blocking SRUing a newer bugfix version to bionic"
1812683,2020-03-17 14:35:04 UTC,"There is no proper fix, the workaround is questionable, nobody is actively working on it though so let's be realistic, it's a wontfix atm for bionic"
1812683,2019-01-22 20:18:46 UTC,"The fix commited upstream looks like more a workaround, unsure it qualifies for a SRU. Could you provide details on the gtk call/api/functions that doesn't like the non english label? Maybe we can come with a small python testcase and get the real gtk/binding issue fixed instead?"
1812683,2019-01-22 13:26:06 UTC,Git Master has a suggested fix now - initial testing indicates success ...
1812683,2019-01-22 12:45:12 UTC,Thanks!
1812683,2019-01-22 09:41:52 UTC,Reported it here: https://github.com/fossfreedom/alternative-toolbar/issues/138
1812683,2019-01-22 09:02:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812683,2019-01-22 09:01:48 UTC,Could you describe how you trigger the issue? Is that by clicking play? Does it happen on local files (any of those?) or other sources?
1812683,2019-01-22 07:45:52 UTC,This might be a dupe of bug #1801436 as it only happens with the alternative-toolbar plugin that was enabled by default.
1812683,2019-01-22 07:24:32 UTC,"(gdb) bt
#0  0x00007ffff7183384 in gtk_tree_view_get_column (tree_view=tree_view@entry=0x555555e847f0 [GtkTreeView], n=n@entry=16)
    at ../../../../gtk/gtktreeview.c:12343
#1  0x00007ffff6ecf5da in _gtk_tree_view_accessible_add_state (treeview=0x555555e847f0 [GtkTreeView], tree=tree@entry=0x555555f801c0, node=node@entry=0x555556aca100, state=state@entry=GTK_CELL_RENDERER_SELECTED)
    at ../../../../gtk/a11y/gtktreeviewaccessible.c:1993
#2  0x00007ffff71727f9 in gtk_tree_selection_real_select_node (selection=selection@entry=0x555555e24610 [GtkTreeSelection], tree=tree@entry=0x555555f801c0, node=node@entry=0x555556aca100, select=select@entry=1)
    at ../../../../gtk/gtktreeselection.c:1632
#3  0x00007ffff7173146 in _gtk_tree_selection_internal_select_node (selection=0x555555e24610 [GtkTreeSelection], node=0x555556aca100, tree=0x555555f801c0, path=0x555555c58500, mode=<optimized out>, override_browse_mode=0)
    at ../../../../gtk/gtktreeselection.c:1585
#4  0x00007ffff71861c8 in gtk_tree_view_real_set_cursor (tree_view=tree_view@entry=0x555555e847f0 [GtkTreeView], path=path@entry=0x555555c58500, flags=flags@entry=(CLEAR_AND_SELECT | CLAMP_NODE)) at ../../../../gtk/gtktreeview.c:13306
#5  0x00007ffff718d4e9 in gtk_tree_view_multipress_gesture_pressed (gesture=0x555555e7d430 [GtkGestureMultiPress], n_press=1, x=<optimized out>, y=<optimized out>, tree_view=0x555555e847f0 [GtkTreeView])
    at ../../../../gtk/gtktreeview.c:3379
#6  0x00007ffff10bedae in ffi_call_unix64 ()
---Type <return> to continue, or q <return> to quit---
   .so.6
#7  0x00007ffff10be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#8  0x00007ffff6be3ced in g_cclosure_marshal_generic_va (closure=0x555555e939f0, return_value=0x0, instance=<optimized out>, args_list=<optimized out>, marshal_data=<optimized out>, n_params=3, param_types=0x5555559f4940) at ../../../../gobject/gclosure.c:1604
#9  0x00007ffff6be3346 in _g_closure_invoke_va (closure=0x555555e939f0, return_value=0x0, instance=0x555555e7d430, args=0x7fffffffcd70, n_params=3, param_types=0x5555559f4940)
    at ../../../../gobject/gclosure.c:867
#10 0x00007ffff6bfe9ff in g_signal_emit_valist (instance=0x555555e7d430, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffffffcd70) at ../../../../gobject/gsignal.c:3300
#11 0x00007ffff6bff12f in g_signal_emit (instance=instance@entry=0x555555e7d430, signal_id=<optimized out>, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
#12 0x00007ffff700f7fc in gtk_gesture_multi_press_begin (gesture=0x555555e7d430 [GtkGestureMultiPress], sequence=<optimized out>) at ../../../../gtk/gtkgesturemultipress.c:241
#13 0x00007ffff6be6008 in g_cclosure_marshal_VOID__BOXEDv (closure=0x555555ab92d0, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x5555559aa9c0) at ../../../../gobject/gmarshal.c:1950
#14 0x00007ffff6be3346 in _g_closure_invoke_va (closure=0x555555ab92d0, return_value=0x0, instance=0x555555e7d430, args=0x7fffffffd130, n_params=1, param_types=0x5555559aa9c0)
    at ../../../../gobject/gclosure.c:867
#15 0x00007ffff6bfe9ff in g_signa..."
1812683,2019-01-21 21:07:33 UTC,"Could you install the dbgsym (https://wiki.ubuntu.com/Debug%20Symbol%20Packages) for glib, gtk and rhythmbox and get a debug backtrace?"
1812683,2019-03-25 16:00:48 UTC,"We need a decision if we SRU the workaround or not. After further investigations, I still can't reproduce it.
There is nothing clear in the bindings and it seems people can reproduce it without the plugin?"
1812683,2019-06-18 13:11:56 UTC,Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version
1812689,2019-01-21 18:09:35 UTC,"as user Do Quyet (mr.quyetdx) suggested here: https://bugs.launchpad.net/plank/+bug/1811492
adding export XDG_SESSION_TYPE=x11` in ~/.xinitrc fixed it for me.
I'm using Arch and
plank --version
0.11.4.24-0a84Arch"
1812689,2019-02-01 22:26:07 UTC,"Indeed that helped, thanks a lot!"
1812693,2019-03-04 14:58:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812693,2019-04-23 15:44:57 UTC,Same with me.
1812693,2019-05-03 21:52:02 UTC,"FWIW, https://blog.kafaiworks.com/posts/arch-linux-audio-setup-on-msi-gp63/ fixed it for me. Might give the package maintainers a hint what's wrong."
1812693,2019-05-03 21:53:20 UTC,"FWIW, https://blog.kafaiworks.com/posts/arch-linux-audio-setup-on-msi-gp63/ fixed it for me. Might give the package maintainers a hint what's wrong."
1812703,2020-03-26 11:02:54 UTC,"I'm not sure when this changed, but on a 3.4 master server I'm now seeing the username in the Closed By column."
1812703,2020-07-31 18:25:45 UTC,"Additionally, in Angular Acq Search (bug 1850547) the username of the closer is visible."
1812727,2019-01-22 13:46:28 UTC,"Ok i see what's happened, i forgot to set the ceph-osd charm config explained in [1]. One thing tho is that it appears to be the case the charm will only attempt to install vaultlocker on install() i.e. if you do what i did and want to change the config post-install the charm does not appear to let you so you can't unbreak the unit."
1812727,2019-01-22 14:03:42 UTC,the charm should ensure vaultlocker is available - https://github.com/openstack/charm-ceph-osd/blob/master/hooks/ceph_hooks.py#L409-L412
1812731,2020-04-04 19:15:17 UTC,"Marking as ""won't fix"" due to report being over one year old."
1812731,2019-01-22 18:03:55 UTC,"The best way to test your camera when in PTP / MTP mode is to use gphoto2 from the command line, having already (and this is extremely important) ""ejected"" or ""unmounted"" the camera from nemo. It's possible that the version of libgphoto2 on your system is having problems with your camera model, or there could be another problem. The way to start to diagnose the problem is using gphoto2."
1812731,2019-01-22 05:38:19 UTC,"Yes, I'd tried that of course, since that's the recommended setting.  MTP
is not recognized by my system for some reason I do not understand - my
ignorance is vast (lsusb reports 'couldn't open device') - and I've not had
time to pursue.   Auto setting on the camera devolves to USB Mass storage
and does allow me to import my images using RPD or other similar
applications."
1812731,2019-01-22 04:54:16 UTC,"I strongly suggest setting your camera to PTP mode instead of USB mass storage mode, then trying again. There should be an option in the camera to do that."
1812731,2019-01-21 21:34:07 UTC,"The log should have been attached to the bug report, but is again here.
The config file is attached here."
1812731,2019-01-21 22:44:28 UTC,Can you please describe in words what action you were taking when the program exception occurred?
1812731,2019-01-21 20:27:15 UTC,Thank you for your bug report. More details are required.
1812731,2019-01-22 04:06:13 UTC,"Hi
I'm sorry my bug report had so little information.  Your application is
quite insistent that a bug report be filed! grin.
I was in the process of quitting the application when the crash occurred.
I was frustrated because the exif data wasn't being extracted and the
camera was only being recognized in mass storage mode, not as a Sony
camera.  The app had apparently refused to download the images since the
exif was needed to rename them.  I attempted to start the download again
and couldn't.  I was pressed for time so I gave up and exited, or started
to exit the program when the crash occurred.
I'm happy to (try to) repeat my actions if that would help you."
1812737,2019-01-22 19:56:56 UTC,"Removing packages from disco:
 jscommunicator 2.1.3-1ubuntu1 in disco
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco amd64
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco arm64
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco armhf
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco i386
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco ppc64el
  jscommunicator-web-phone 2.1.3-1ubuntu1 in disco s390x
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco amd64
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco arm64
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco armhf
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco i386
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco ppc64el
  libjs-jscommunicator 2.1.3-1ubuntu1 in disco s390x
Comment: Transitively depends on to-be-removed node-websocket, FTBFS, removed from Debian testing; Debian bug #888579, LP: #1812737
1 package successfully removed."
1812737,2019-06-21 12:43:08 UTC,"node-marked-man has been fixed in version 0.4.0-1 in the meanwhile, so just invalid for now."
1812737,2019-06-20 19:54:40 UTC,unsubscribing ubuntu-archive; there's no further action to take until someone sorts out what should be done with the reverse-dependencies of node-marked-man.
1812737,2019-01-25 20:11:21 UTC,"Demoting packages to disco-proposed:
 jssip 0.6.34-5 in disco
Comment: LP: #1812737: remove node-websocket and demote rdep jssip
1 package successfully demoted."
1812737,2019-01-25 20:09:59 UTC,"Removing packages from disco:
 node-websocket 1.0.23-3build2 in disco
  libjs-websocket 1.0.23-3build2 in disco amd64
  libjs-websocket 1.0.23-3build2 in disco arm64
  libjs-websocket 1.0.23-3build2 in disco armhf
  libjs-websocket 1.0.23-3build2 in disco i386
  libjs-websocket 1.0.23-3build2 in disco ppc64el
  libjs-websocket 1.0.23-3build2 in disco s390x
  node-websocket 1.0.23-3build2 in disco amd64
  node-websocket 1.0.23-3build2 in disco arm64
  node-websocket 1.0.23-3build2 in disco armhf
  node-websocket 1.0.23-3build2 in disco i386
  node-websocket 1.0.23-3build2 in disco ppc64el
  node-websocket 1.0.23-3build2 in disco s390x
Comment: LP: #1812737: remove node-websocket and demote rdep jssip
1 package successfully removed."
1812737,2019-01-25 18:04:23 UTC,removing the block-proposed tag which is almost always counterproductive.
1812737,2019-01-22 20:01:22 UTC,"Debian bug #918441 is not on its own sufficient justification to remove node-websocket, since the missing -lnode is easily fixed by adding a build-dependency on libnode-dev.  However, after adding that build-dependency locally, the package still fails to build."
1812737,2019-01-22 19:42:52 UTC,"> they should all go in proposed too, as it is happening in debian
> (millstone is already out from testing)
"
1812737,2019-01-22 18:12:24 UTC,"$ reverse-depends src:jssip
Reverse-Depends
===============
* libjs-jscommunicator          (for libjs-jssip-bundle)"
1812737,2019-01-22 19:18:11 UTC,"$ reverse-depends src:jssip
Reverse-Depends
===============
* libjs-jscommunicator (for libjs-jssip-bundle)"
1812737,2019-01-22 19:14:21 UTC,"$ reverse-depends src:node-sqlite3
Reverse-Depends
===============
* node-mbtiles (for node-sqlite3)
* node-millstone (for node-sqlite3)
* node-tilejson (for node-sqlite3)"
1812737,2019-01-22 18:13:45 UTC,"$ reverse-depends src:node-sqlite3
Reverse-Depends
===============
* node-mbtiles                  (for node-sqlite3)
* node-millstone                (for node-sqlite3)
* node-tilejson                 (for node-sqlite3)"
1812737,2019-01-22 18:13:29 UTC,"$ reverse-depends src:node-marked-man -b
Reverse-Build-Depends
=====================
* node-gulp                     (for node-marked-man)
* node-loose-envify             (for node-marked-man)
* node-semver                   (for node-marked-man)
* node-sshpk                    (for node-marked-man)
* npm                           (for node-marked-man)"
1812737,2019-01-22 18:11:08 UTC,"Removing packages:
 node-duplexer2 0.1.4-1 in disco
  node-duplexer2 0.1.4-1 in disco amd64
  node-duplexer2 0.1.4-1 in disco arm64
  node-duplexer2 0.1.4-1 in disco armhf
  node-duplexer2 0.1.4-1 in disco i386
  node-duplexer2 0.1.4-1 in disco ppc64el
  node-duplexer2 0.1.4-1 in disco s390x
Comment: (From Debian) ROM; FTBFS + provided by node-duplexer3; Debian bug #919575
Remove [y|N]? y"
1812737,2019-01-22 19:22:13 UTC,"for marked-man, I presume we have to fix it in some way..."
1812741,2019-01-25 19:13:06 UTC,Thanks for reporting.
1812750,2019-01-22 16:06:09 UTC,"Thank you for your bug report, I can't confirm the issue here, unsure what's different between those installations though"
1812754,2020-04-09 03:36:07 UTC,"Dear Kevin,"
1812754,2019-07-14 16:34:27 UTC,No blanks here. I also tried with the gtk2 UI backend as that is what Xfce uses.
1812754,2020-03-09 02:54:20 UTC,"Dear Kevin,"
1812754,2019-09-22 15:46:28 UTC,I just saw this.  Sorry for the delay.
1812754,2019-09-10 17:20:05 UTC,If it helps I don't think its specific to using the command line. I'm having the same problem of random blank pages being added using the normal GUI version. I think its a more widespread fundamental problem. This seems to mostly happen when there are a lot of pages and images involved. This is basically the same report I put in here:
1812754,2019-08-15 13:04:24 UTC,"A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version."
1812754,2019-03-20 20:40:40 UTC,"I have a better idea.  Instead of inventing reasons for me to mess up my settings why don't YOU try to confirm it.  I sent all the stuff you'd need to try this.  If it does not add blank pages for you with whatever settings you have, go ahead and mark it invalid.  If it _does_ add blank pages, mark it confirmed and go from there."
1812754,2019-03-18 19:49:01 UTC,"Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?"
1812754,2019-03-15 20:39:56 UTC,"Sorry, I do not have a spare machine to download the software."
1812754,2019-03-14 17:28:19 UTC,"Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version."
1812754,2019-02-09 23:28:04 UTC,Filed.  https://bugs.documentfoundation.org/show_bug.cgi?id=123297
1812754,2019-02-09 23:24:08 UTC,"Created attachment 149064
sample file (see instructions)"
1812754,2019-02-09 23:21:59 UTC,"Description:
I use LibreOffice mostly on Xubuntu."
1812754,2019-01-24 15:22:37 UTC,"I can reliably reproduce the problem, and indeed waiting for some time (sleep 2) in between doesn't exhibit the problem.
This seems to be an upstream bug, would you mind filing it at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and sharing the link to it here? Thanks!"
1812758,2020-08-03 23:00:25 UTC,"I had a similar issue with an existing Ubuntu 16.04 LTS install on my Dell Precision 5820 tower that has booted without issue for 2 years.  After updating the BIOS via the Ubuntu Software Center (to 1.13.0), my computer gave only a black screen."
1812758,2019-02-01 14:09:23 UTC,What status should this bug be moved to?
1812758,2019-02-01 14:06:23 UTC,"I was able to install 18.04 without issue. It looks like the solution to disable ""Intel VMD Technology"" in the BIOS solved the issue."
1812758,2019-01-23 22:22:51 UTC,I had some luck with Dell after I told them to give me a different machine. Finally got in touch with someone with Dell support that checked their knowledge base.
1812758,2019-01-22 14:42:51 UTC,@Kai-Heng Feng (kaihengfeng)
1812758,2019-01-21 23:57:46 UTC,Here is another related experience which may give some insight:
1812758,2019-01-22 00:04:05 UTC,Related Canonical/Ubuntu hardware certification for this model. Notes suggest Dell-installed image is/may not be the same as used by Ubuntu.
1812758,2019-01-21 23:54:37 UTC,Have you used the service tag to see if you can get a link to the Dell Ubuntu 16.04 installation images?
1812758,2019-01-21 23:45:30 UTC,A workaround...but not a complete work around...
1812758,2019-01-22 13:23:36 UTC,"- Does your system have a video output from integrated GPU? Use it for installation.
- Booth with kernel parameter ""nouveau.modeset=0""
- Install Ubuntu and Nvidia proprietary graphics driver.
- Reboot and now it's ok to use to Nvidia as video output."
1812765,2019-01-23 01:33:27 UTC,"Hi Jeff,
  1.I am still not test on the 16.05.5 with kernel 4.15;
  2.18.04.1 with kernel 4.15 can not reproduce the failure."
1812765,2019-01-22 17:22:21 UTC,Please confirm the following:
1812765,2019-03-06 21:24:54 UTC,"Another interesting question, why does each socket show two different IDs?"
1812767,2019-01-22 04:19:14 UTC,"It seems we're deploying from the master branch, which probably isn't what we want. Said branch also seems to be broken at present (or we have a dependency mismatch somewhere)."
1812767,2019-01-22 04:26:39 UTC,"The stable branch requires 2.4.4, so the ruby layer's default is still too old."
1812768,2019-01-22 08:55:04 UTC,Thank you for your detailed report.
1812768,2019-01-22 21:25:44 UTC,Many thanks. Appreciate the quick response.
1812768,2019-01-23 12:02:01 UTC,"> 2) Have it manifest itself as a broken symlink to the URL target
"
1812768,2019-01-23 14:57:52 UTC,"Thank you. I think if it would be possible to have both of those things, it would be very helpful."
1812768,2019-01-24 08:02:16 UTC,"> I think if it would be possible to have both of those things, it would be very helpful
"
1812772,2019-03-19 13:23:52 UTC,Is this still an issue?
1812772,2019-03-19 15:34:39 UTC,Yes. You can see both neutron lbaas and octavia are enabled by default in: https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/horizon/horizon-container-puppet.yaml
1812777,2020-03-07 15:31:08 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1812796,2019-04-25 06:49:02 UTC,https://github.com/torvalds/linux/commit/ed5f13261cb65b02c611ae9971677f33581d4286
1812796,2019-08-22 16:17:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1812796,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1812796,2019-06-18 16:02:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812796,2019-06-18 12:02:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1812796,2019-01-22 07:00:07 UTC,This change was made by a bot.
1812796,2019-02-01 17:10:16 UTC,"I see this failure in cosmic as well:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/ppc64el/l/linux/20190201_014942_1b783@/log.gz"
1812796,2019-08-23 02:43:59 UTC,"Hmm, how come this was marked as verification-needed-xenia?"
1812796,2019-05-16 10:21:50 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-May/100758.html
1812805,2019-05-20 14:02:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1812805,2019-05-22 10:55:38 UTC,Passed with proposed Cosmic kernel.
1812805,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1812805,2019-05-20 02:30:46 UTC,Passed with the proposed Bionic kernel.
1812805,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1812805,2019-05-16 15:03:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812805,2019-04-30 12:01:22 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100365.html
1812805,2019-04-24 03:58:22 UTC,Patch already applied in Disco.
1812805,2019-04-24 03:27:02 UTC,https://github.com/torvalds/linux/commit/98415da03ae6559dc62899fd31e55e194779c45b#diff-f3f3c5959dabe5acc09dba521f69484f
1812805,2019-04-18 07:59:50 UTC,This issue affects Cosmic as well:
1812805,2019-01-24 08:05:42 UTC,"For the ptrace issue, please refer to bug 1813127"
1812805,2019-01-24 07:46:18 UTC,"Didn't see this:
    ptrace-tm-spd-gpr [FAIL]"
1812805,2019-01-22 07:30:08 UTC,This change was made by a bot.
1812807,2020-04-05 11:26:43 UTC,there was some discussions around this in LP: #1764596.
1812809,2019-05-14 19:08:52 UTC,This bug was fixed in the package linux - 4.4.0-148.174
1812809,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1812809,2019-04-30 10:20:50 UTC,"Passed with Bionic P9:
 [21] Kprobe event string type argument	[PASS]
 [22] Kprobe event argument syntax	[PASS]
 [23] Kprobes event arguments with types	[PASS]
 [24] Kprobe event auto/manual naming	[PASS]
 [25] Kprobe dynamic event with function tracer	[PASS]"
1812809,2019-04-29 16:03:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812809,2019-05-14 22:53:57 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1812809,2019-04-23 11:01:08 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100250.html
1812809,2019-04-22 08:24:46 UTC,"Tested with the latest selftest in Linus' tree, this test will pass. So this looks like a test case issue to me."
1812809,2019-01-22 08:00:11 UTC,This change was made by a bot.
1812809,2019-04-26 14:31:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1812812,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1812812,2019-02-15 14:42:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812812,2019-02-11 11:06:20 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1812812,2019-03-06 10:49:37 UTC,This bug was fixed in the package linux - 4.18.0-16.17
1812812,2019-01-22 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812812,2019-02-04 14:46:37 UTC,This bug was fixed in the package linux - 4.19.0-12.13
1812813,2019-10-24 17:10:58 UTC,"Experienced this on bionic-distro to bionic-rocky upgrade today.  The service is masked, it appears we should somehow update the nrpe check within the remove_legacy_nova_metadata() function."
1812813,2020-04-02 23:20:02 UTC,"For future travelers: a successful workaround is to manually inject an updated monitors value that doesn't list the nova-api-metadata check. This is described in bug 1870438; that example is about keystone, but the process is the same."
1812813,2020-05-10 15:35:33 UTC,Here's a more step by step explanation of the workaround:
1812813,2020-05-29 17:24:46 UTC,"Hi, I faced this issue recently. My conclusion is that quantum-network-service relation should be outdated from Rocky onward."
1812813,2020-05-29 19:40:47 UTC,"The least damaging change we can do here is to add ""nova-api-metadata"" to deprecated services:
https://github.com/openstack/charm-neutron-gateway/blob/a03fe36fa65b710b6cd8059b870c44204f3e3856/hooks/neutron_utils.py#L1124"
1812813,2020-06-01 17:40:36 UTC,"Reviewed:  https://review.opendev.org/732094
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=775c06f8ff513017454597724a2c52089caad95c
Submitter: Zuul
Branch:    master"
1812813,2020-06-02 09:00:24 UTC,"Fix proposed to branch: stable/20.05
Review: https://review.opendev.org/732501"
1812813,2020-06-19 13:47:54 UTC,"Reviewed:  https://review.opendev.org/732501
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=3dd6d68c2ceaef1b7deab010aaadd4f236d24abc
Submitter: Zuul
Branch:    stable/20.05"
1812816,2019-01-31 10:00:36 UTC,Sure! https://storyboard.openstack.org/#!/story/2004902
1812816,2019-01-30 08:10:26 UTC,Can you move this to storyboard? I'll make this launchpad account non writable as the magnum one.
1812822,2019-02-15 10:13:16 UTC,"I couldn't get the crash file in the disco system though I set the apport, but get the qemu_system-s390x.crash under /var/crash in the original test system ubuntu16.04(qemu: 2.11.1)."
1812822,2020-01-20 06:20:51 UTC,"The mentioned commit 6ab79a20af3a7b3bf610ba9aebb446a9f0b05930 is in qemu 4.1 and later.
Since we will have qemu 4.2 in 20.04 please retry with that once available.
I'll set a bug tak reference in the changelog of the update."
1812822,2020-02-06 20:45:52 UTC,This bug was fixed in the package qemu - 1:4.2-1ubuntu1
1812822,2020-03-12 10:31:05 UTC,"------- Comment From <email address hidden> 2020-03-12 06:24 EDT-------
IBM bugzilla status -> closed. If the problem will be detected again, a new LP will be created."
1812822,2019-02-15 08:19:24 UTC,"------- Comment From <email address hidden> 2019-02-15 03:09 EDT-------
(In reply to comment #12)

> Can this be reproduced with the upstream qemu? If yes, can you also report
> this to the  qemu-s390x mailing list?
"
1812822,2019-02-14 13:30:37 UTC,"------- Comment From <email address hidden> 2019-02-14 08:22 EDT-------
Can this be reproduced with the upstream qemu? If yes, can you also report this to the  qemu-s390x mailing list?"
1812822,2019-06-04 14:37:55 UTC,This may be fixed by https://git.qemu.org/?p=qemu.git;a=commit;h=6ab79a20af3a7b3bf610ba9aebb446a9f0b05930
1812822,2019-02-01 09:39:20 UTC,"To some extend this feels a bit like:
- https://bugzilla.redhat.com/show_bug.cgi?id=1242383
- https://bugzilla.redhat.com/show_bug.cgi?id=1151306"
1812822,2019-02-01 09:39:07 UTC,"I used a recent version of the softwrae stack from Disco
- qemu 3.1
- libvirt 5.0
- openvswitch 2.11"
1812822,2019-01-31 19:44:32 UTC,I couldn't use the command apport-collect 1812822
1812822,2019-02-01 09:40:29 UTC,"We now need to find out what the difference is:
a) your test case is slightly different and you can trigger it on the same SW levels it works for me, then we need to report that to upstream as those are the very latest versions
b) your test is good once you use the more recent SW levels, in that case we need to drill down into your crash and identify the fix (that must be in between qemu 2.11 and 3.1 somewhere) to consider backporting it.
c) This would be arch dependent (I tested x86), but we would find that further down the road as you'd report (a) to happen. After all TUNSETVNETLE is for setting big/little endian operations for linux tap/macvtap so it could be s390x only after all."
1812822,2019-01-30 12:39:45 UTC,"As of comment #1, please share/attach the relevant logs."
1812822,2019-01-22 10:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812824,2019-01-22 09:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812824,2020-09-14 08:19:33 UTC,"Didn't see this on B-s390x (LPAR / zVM)
Closing this bug."
1812826,2019-04-20 05:06:53 UTC,"(wxl) ""That's a great first bug report, Adam. We need to get you on the Lubuntu bug team!"""
1812826,2019-04-14 17:59:38 UTC,"That's a great first bug report, Adam. We need to get you on the Lubuntu bug team!"
1812826,2019-01-22 10:05:22 UTC,"Ugghh, formatting."
1812826,2019-04-14 08:23:41 UTC,I got this on two different machines. Thanks for your contribution.
1812828,2019-01-22 20:28:02 UTC,"I see,"
1812828,2019-01-22 21:09:40 UTC,"See lp:~maddevelopers/mg5amcnlo/bug_1812828
for my proposition."
1812828,2019-01-28 11:30:02 UTC,"Hi Olivier,"
1812828,2019-02-04 20:04:45 UTC,"Hi,"
1812829,2019-03-20 20:47:17 UTC,This issue was fixed in the openstack/placement 1.0.0.0rc1 release candidate.
1812829,2019-01-22 09:51:49 UTC,Fix proposed in https://review.openstack.org/#/c/632365/
1812843,2019-04-22 04:21:06 UTC,And Disco s390x KVM (5.0.0-8.9-generic)
1812843,2019-04-22 04:18:09 UTC,Found on Cosmic s390x as well:
1812843,2020-09-14 08:25:23 UTC,"Didn't see this with Bionic / Focal s390x LPAR and zVM.
Closing this bug."
1812843,2019-01-22 11:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812845,2019-04-10 08:01:20 UTC,Test 3b080b2564287be91605bfd1d5ee985696e61d3c and 5fbc7c59fd22c5a6531b40b0759624b680a95e52 and have passed on X-i386 (node pepe)
1812845,2019-05-14 22:56:12 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1812845,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1812845,2019-04-23 21:35:02 UTC,This bug was fixed in the package linux - 4.18.0-18.19
1812845,2019-04-23 13:19:09 UTC,This bug was fixed in the package linux - 4.4.0-146.172
1812845,2019-04-16 10:09:51 UTC,Test 3b080b2564287be91605bfd1d5ee985696e61d3c and 5fbc7c59fd22c5a6531b40b0759624b680a95e52 and have passed on C-i386 (node pepe)
1812845,2019-04-16 10:01:16 UTC,Test 3b080b2564287be91605bfd1d5ee985696e61d3c and 5fbc7c59fd22c5a6531b40b0759624b680a95e52 and have passed on B-i386 (node pepe)
1812845,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1812845,2019-04-04 18:04:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1812845,2019-04-04 18:06:07 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1812845,2019-03-22 09:25:26 UTC,"Just found that this issue for autotest-client-tests has already been addressed in 3c2347e74, so we're good, previous commit reverted. https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=e8225af0687c7cb804458fa6cd03956739f24d39"
1812845,2019-03-22 08:17:54 UTC,"I have the test disabled on i386, so we can still run other tests without being interrupted.
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=47c843d9a608f212b9b1138b410151ae1e8f5b24"
1812845,2019-03-13 12:33:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812845,2019-03-13 10:26:46 UTC,This patch seems to fix the problem for me.
1812845,2019-01-23 08:36:15 UTC,Spotted on X / D / mainline 5.0rc2 as well.
1812845,2019-01-23 07:51:39 UTC,This issue could be found on Cosmic.
1812845,2019-01-22 12:34:45 UTC,This change was made by a bot.
1812845,2019-04-04 18:01:30 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1812846,2019-09-19 12:07:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1812853,2019-08-28 16:36:56 UTC,Fix released in 18.5-13-gb74ebca56 or later
1812855,2020-02-27 15:55:51 UTC,The bugs cannot be reproduced. I am closing this as invalid and open specific ones to track missing tests.
1812855,2019-03-23 15:15:01 UTC,"When changing the contents defined within the 'authorized_keys' parameter, the updated contents will now get updated within the '/etc/ssh/authorized-keys/glance-sync-slaves' file on the unit."
1812857,2019-07-17 17:12:11 UTC,"This bug is believed to be fixed in cloud-init in version 19.2. If this is still a problem for you, please make a comment and set the state back to New"
1812857,2019-09-16 18:24:48 UTC,"Hi, we're still being affected by this on Azure with 19.2-24-ge7881d5c-0ubuntu1~18.04.1 - using PACKER to build from image: BuildSource : Marketplace/Canonical/UbuntuServer/18.04-DAILY-LTS"
1812857,2019-09-16 20:45:39 UTC,"Hi Danno,"
1812857,2019-07-15 20:12:34 UTC,"This bug is fixed with commit e5f54213 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=e5f54213"
1812857,2019-09-16 18:26:50 UTC,"I am not able to change the state as requested by Ryan, I see message ""Only changeable by a project maintainer or bug supervisor""."
1812857,2019-06-05 13:43:47 UTC,Also affected by this bug.
1812857,2019-03-02 09:09:29 UTC,"It's correct and expected behaviour
It's exactly what I want to have: bond0 uses mac address(9c:XX:XX:46:5d:91) of one physical interface."
1812857,2019-02-26 14:39:50 UTC,"Thanks for the logs.  Yes, bond0 as a device exists as soon as bond module is loaded; the critical bit is that the kernel has enslaved one of the interfaces and then takes the underlying device's MAC address.  We can see that in the output:"
1812857,2019-02-25 13:02:59 UTC,@raharper according to logs bond0 exists at the beginning
1812857,2019-02-25 09:47:58 UTC,journalctl -b 0 -o short-monotonic     -u cloud-init-local.service     -u systemd-networkd     -u systemd-networkd-wait-online     -u cloud-init.service
1812857,2019-01-23 16:43:57 UTC,I think I understand what happened here.  If you could please run and attach output of:
1812857,2019-01-22 14:22:11 UTC,"Usually bonds inherit mac address from one of
physical interface"
1812861,2019-09-23 14:07:34 UTC,I'm not sure exactly when we fixed this (the fix is probably in the 4.1 release) but as of current head-of-git this correctly generates the SIGSEGV.
1812862,2019-04-01 03:09:24 UTC,"Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here."
1812864,2019-12-12 10:04:57 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc2 release candidate.
1812864,2019-11-21 10:57:05 UTC,"Reviewed:  https://review.opendev.org/694985
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=21e5924ef4f20e5e39bd708388088e565936e868
Submitter: Zuul
Branch:    stable/train"
1812864,2019-11-19 11:22:09 UTC,"Change abandoned by Radosław Piliszek (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/694986
Reason: not now"
1812864,2019-11-19 11:21:58 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/694986"
1812864,2019-11-19 11:21:40 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/694985"
1812864,2019-11-19 11:14:50 UTC,"Reviewed:  https://review.opendev.org/694666
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=2cd00dadc0ad06610e94f879ddce145ad1134ea5
Submitter: Zuul
Branch:    master"
1812864,2019-11-16 11:33:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/694666"
1812864,2019-11-16 09:45:19 UTC,"Also, the feature was backported to stein, just not released. Negotiating new heat release."
1812864,2019-11-16 09:37:57 UTC,"Mark, this is not fixed. Heat still tries keystone over public endpoint. Only heat-to-heat was fixed."
1812864,2019-08-15 15:13:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676716"
1812864,2019-10-08 09:03:44 UTC,"Reviewed:  https://review.opendev.org/676716
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d54c8fbdccfd8145b65d0fcc50dc8628b37c1a88
Submitter: Zuul
Branch:    master"
1812864,2019-05-03 20:09:55 UTC,It would be good for heat to provide a separate configuration option for its own access to the keystone endpoint vs that which is passed to instances with software deployments.
1812864,2019-05-03 20:08:43 UTC,Would it be helpful to provide a flag in kolla-ansible that sets whether to use the internal or external keystone endpoint in this config section?
1812864,2019-05-03 19:53:55 UTC,"The reason for adding https://review.openstack.org/#/c/566361/ is that it is passed to instances by heat for calling back to the heat API. Instances can't be assumed to have access to the internal API, so we need to pass the external URL."
1812864,2019-05-03 10:22:21 UTC,I did a workaround and put this in the config files for Heat:
1812864,2019-05-02 07:45:53 UTC,"Hi, any solution for this bug?"
1812864,2019-11-11 15:39:52 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1812865,2019-01-23 15:56:03 UTC,"Thanks, that's still an issue on disco"
1812866,2021-02-10 15:10:31 UTC,"Testing this, I added item alerts to an item bucket columns. (alert messages choice doesn't have any display)"
1812866,2021-02-10 15:55:04 UTC,"Ah, so when you clear a message, it's not actually deleting it. Hmm."
1812866,2021-02-10 00:09:31 UTC,You'll need to use the column picker to display the Item Alerts column.
1812866,2019-04-19 16:54:36 UTC,"Note that the xul ""Alert Message"" field is available and should not be, the web client ""Alerts"" field is not available."
1812866,2020-12-30 19:12:04 UTC,This adds a new column called Item Alerts to the copy buckets grid (regular grid and pending grid) that displays the 'note' for all alerts that are attached to that item.
1812866,2021-02-09 23:52:36 UTC,"Which page should I be seeing your changes on?  I'm applying the patch then I'm visiting Cataloging -> Item Buckets.  Then I select a bucket. There's only 4 fields on the grid:  name, call number, location, title"
1812871,2019-02-04 16:13:44 UTC,"OK, I see what's happening."
1812871,2019-02-04 15:42:57 UTC,"FWIW, Guillermo also wasn't able to repro, which is baffling because I did reproduce it on 4 different hosts as noted in the original report."
1812871,2019-02-04 15:22:16 UTC,"I'm not able to repro. Can you please provide ""ps uwwxf"" ? (the tree of ""codetree"" will be enough)"
1812871,2019-02-04 15:10:40 UTC,Sorry I meant codetree not mojo
1812871,2019-02-05 07:26:38 UTC,Ah I see. The code has this :
1812871,2019-02-04 14:21:26 UTC,"Hm, I can repro this with codetree alone, without involving mojo. Do you still need pstree for mojo?"
1812871,2019-02-04 07:14:25 UTC,"Can you please provide the pstree for the ""mojo"" command ? I suspect it's running a ""charm"" command. Can you please try running that command outside of mojo and see if it prompts something from the shell ?"
1812871,2019-01-22 15:42:05 UTC,"Oh! Forgot to mention! If a version of the charm *lower* than 185 is specified, things work well:"
1812871,2019-02-04 14:38:19 UTC,Here's the pstree for codetree:
1812880,2019-01-22 20:09:48 UTC,"The desktop is not handled by nautilus anymore, reassigning"
1812880,2019-01-23 16:13:01 UTC,"Similar to bug #1812884, upstream ""fixed it"" by removing support for scripts..."
1812880,2019-08-26 06:23:42 UTC,"But this is a serious problem, and this bug report has status ""Won't Fix"""
1812883,2019-08-19 20:44:54 UTC,"Hi Jonathon,"
1812883,2019-08-20 01:44:00 UTC,Thanks for pointing out that test. I will remember to suggest it to people in future in other CPU-related bugs.
1812883,2019-08-20 06:38:37 UTC,The extension is only fully removed if you purge it and reboot your system.
1812883,2019-08-26 06:57:37 UTC,I removed desktop icons. Clean a nice desktop and no more 5 seconds save on every file.
1812883,2020-06-22 08:53:19 UTC,This bug is still present in Focal. It seems to have lost focus in upstream. In Focal it is much harder to remove the extension as it is even more tightly linked in as a mandatory dependency for a number of major system components. The only way to remove it is by deleting or renaming its files.
1812883,2019-08-27 02:11:26 UTC,This issue is in progress with the upstream developers. If you would like to contribute then the page is:
1812883,2019-08-19 19:28:19 UTC,I hardly think enough research into this has been done for it to be obvious that this is a duplicate.
1812883,2020-06-22 09:03:43 UTC,I think bug 1872796 and bug 1832812 cover the performance issues already. If there are any more then please open new bugs for them.
1812883,2019-08-26 10:55:52 UTC,"""Just get rid of the desktop icons"" is not a good response to ""The desktop icons flash every time I change anything that affects the desktop."""
1812883,2019-08-19 19:13:55 UTC,I think this bug may well be a duplicate of #1825623. Would anyone object if I marked it as such.
1812883,2019-01-22 20:08:59 UTC,"The desktop is not handled by nautilus anymore, reassigning"
1812883,2019-08-19 04:15:36 UTC,Please also note; if you experience prolonged high CPU when making desktop changes then most likely that is bug 1815550.
1812883,2019-01-27 20:49:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812883,2019-01-28 09:46:49 UTC,Could someone report it upstream on https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/ ?
1812883,2019-01-28 13:50:21 UTC,https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/86
1812883,2019-08-19 19:03:52 UTC,I worked round this issue by uninstalling gnome-shell-extension-appindicator. This fixed this issue and also a number of high cpu usage issues I was seeing. The cpu issues were sometimes severe enough to also expose weaknesses in the compositor.
1812883,2019-01-28 13:53:13 UTC,"Right, sorry about that, thx for looking upstream though!"
1812883,2019-08-19 04:14:53 UTC,Several duplicates of this bug mention:
1812883,2019-01-28 13:51:28 UTC,"Actually, correction, I shouldn't have reported, it, it's already reported upstream as https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/58."
1812884,2019-01-22 20:08:40 UTC,"The desktop is not handled by nautilus anymore, reassigning"
1812884,2019-01-23 16:08:48 UTC,"Upstream 'fixed it' by removing support to excute anything else than .desktop files, see their comment on https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/73"
1812885,2019-08-19 03:46:06 UTC,This bug is open already. It was never closed.
1812885,2019-01-22 20:08:17 UTC,"The desktop is not handled by nautilus anymore, reassigning"
1812885,2019-01-23 16:09:26 UTC,"Similar to bug #1812884, upstream ""fixed it"" by removing support for scripts..."
1812885,2019-01-23 18:38:08 UTC,The issue persists in a slightly different form with .desktop files:
1812885,2019-01-29 16:33:05 UTC,PLEASE SEE MY COMMENT ABOVE AND REOPEN THIS ISSUE.
1812887,2019-01-28 11:06:57 UTC," I am pretty sure I have seen something like this before . Worth trawling https://gcc.gnu.org/bugzilla for more such examples and I'll take a look when I can. If someone beats me to it, please do :) It's also reproducible with upstream trunk (or what will be GCC-9)"
1812887,2019-01-28 08:54:40 UTC,It is useful to give the compiler flags as well as the version.
1812887,2019-01-23 15:21:33 UTC,"Okay , I've played a bit more ."
1812887,2019-01-23 11:59:08 UTC,The testcase is not compilable and there is no input on the options that are required to provoke this code generation.
1812889,2019-01-22 18:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812889,2020-07-06 04:17:14 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1812892,2019-02-19 06:09:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812892,2021-02-24 01:19:25 UTC,"When I enable GSConnect version 28 (as reported by GSConnect > About) in Tweaks > Extensions > GSConnect, after a while my Ubuntu 18.04 system becomes unresponsive, with the disk activity light solidly on. With it disabled, the system never becomes unresponsive."
1812894,2019-08-01 14:44:49 UTC,https://github.com/charmed-kubernetes/bundle/issues/720
1812894,2019-01-29 10:22:13 UTC,Fix the problem with following steps.
1812894,2019-08-01 14:40:49 UTC,"We've pinned the versions of packages you mentioned, so this should be fixed moving forward.  Feel free to comment or open a new ticket if you see this issue again."
1812896,2019-01-22 18:13:17 UTC,"and MAAS 2.3
MAAS version: 2.3.5 (6511-gf466fdb-0ubuntu1)"
1812896,2019-01-22 20:28:47 UTC,This is a documentation issue. A machine must be commissioned before it can be used. A NEW machine means commissioning hasn't been run or in 2.5+ it has been run but hasn't been accepted by an administrator.
1812896,2020-11-20 17:43:56 UTC,"This whole confusion of how MAAS actually processes nodes in various states versus the policy that the documentation lays out is annoying me as an ""unclear thing.""  When 2.9 pops out, I'm going to test it, figure out what MAAS actually does, and document that, possibly with guidance on what's recommended, but with accuracy about what will work."
1812896,2020-12-10 15:32:58 UTC,"After looking through the 2.5 documentation, I cannot find a passage which matches what's been quoted above.  Please provide a URL to the page where this error occurs.  The remainder of the MAAS documentation (2.6++) seems to be relatively okay on this point.  Marking incomplete."
1812896,2020-12-10 18:34:33 UTC,"Don't have the time or patience to track down 2.5. The documentation in this area continues to evolve, so. https://maas.io/docs/concepts-and-terms#heading--controllers ""Commission
This action commissions a node, changing a node’s status from ‘New’ to ‘Commissioning’ to ‘Ready’."""
1812896,2020-12-10 19:06:12 UTC,"No, a formal state diagram is a good idea, and it's on the list.  It's just
a long list."
1812897,2019-01-22 20:15:11 UTC,"Hi Max,"
1812898,2019-01-22 19:11:07 UTC,sorry for the typo s/exiting/existing/
1812898,2019-09-20 11:50:34 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1812899,2020-06-23 08:14:30 UTC,Please provide a crash log the way https://answers.launchpad.net/dcplusplus/+faq/337 describes if you still experience this.
1812899,2020-08-23 04:17:13 UTC,[Expired for DC++ because there has been no activity for 60 days.]
1812900,2019-02-05 14:35:59 UTC,"We have found that many of the settings under the Defaults tab do not always stick when unchecked. So far, we have found those that don't stick are:"
1812900,2019-03-07 14:06:44 UTC,See additional comments with duplicate https://bugs.launchpad.net/evergreen/+bug/1818916
1812900,2019-03-07 14:09:12 UTC,"While Michele reports that they are seeing this with the use of add holdings, we are seeing the settings revert to default both with add holdings and using the Actions menu at holdings view. Some users never see the settings revert to default and others never have the settings save beyond one or two records (settings will save for a few records and then revert to defaults)"
1812900,2019-03-07 14:12:18 UTC,Edited title to be more inline with issue
1812900,2019-03-11 15:51:17 UTC,"Adding a note that we have encountered this with the ""Allow Call Number attributes in Copy Templates"" checkbox as well.  It sporadically un-sticks, and I haven't been able to trace a reason."
1812900,2019-04-18 17:13:41 UTC,"We have found that ""Always show holding default pane"", ""Use checkdigit"", and ""Auto-generate barcodes"" do not stay checked.
The latter two make it harder for libraries to add multiple copies because there is no indication why entering the first barcode doesn't auto-generate the next ones. It's also problematic because without ""use checkdigit"" there is no warning that a barcodes is invalid .
Because the ""holdings default pane' can also be toggled on and off using a button on the item record screen, turning it on with the button keeps it on even if the checkbox is unchecked."
1812900,2019-04-19 20:45:47 UTC,The problem has been observed in 3.1.11 as well.
1812900,2019-04-19 20:55:48 UTC,"I note that the patch for bug 1793196 that moved one of the calls to $scope.fetchDefaults() seemed to caused (or revealed) the issue between 3.1.10 and 3.1.11, but that doesn't account for why folks also saw the problem in 3.2.2."
1812900,2019-05-24 20:58:58 UTC,I tested Galen's branch and it worked as expected. And his code and explanation make sense to me. Here's my signoff.
1812900,2019-06-06 13:43:53 UTC,Guess I should add that we're testing this at CW MARS.  Don't let the fact that I've assigned the bug to myself stop you from looking at it or even pushing it before I get around to it.  It might be a few days/weeks.  We've got a lot going on right now.
1812900,2019-06-13 15:07:11 UTC,"I tested this with our local data at CW MARS, and it worked well in my testing. Adding my signoff, too. I have tested this code and consent to signing off on it with my name, John Amundson, and my email address, <email address hidden>."
1812900,2019-06-13 16:10:55 UTC,"It also works for Janet Schrader at CW MARS, so I've added our sign offs and pushed the patch to master, rel_3_3, rel_3_2, and rel_3_1."
1812900,2019-06-13 16:54:23 UTC,"Thanks, Jason. Yes, this worked in my testing also, looking forward to seeing it live.
I'll be official and add my signoff with my name, Janet Schrader and my email address, <email address hidden>."
1812901,2019-09-27 10:23:39 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io/c/features) to discuss the feature?"
1812901,2019-09-19 15:16:19 UTC,"This is a request for enhancement. Closing it as ""invalid"" seems inappropriate. If the answer is won't fix, say so."
1812901,2019-09-19 15:01:01 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1812901,2019-01-22 23:31:37 UTC,"note that the provided RH pointer explicitly says ""CLOSED WONTFIX"" so it's not a terribly helpful approach ;>"
1812901,2019-01-22 23:01:45 UTC,We currently don't have any plans to support VirtualBox however it may be possible to use virt-manager to control VirturalBox[1].
1812901,2019-01-23 00:48:48 UTC,"Sorry, should have read the cited RH more closely. Yes, virt-manager GUI won't expose it (that's the won't fix); but the same underlying libvirt code which is misfiring in virsh (see https://www.redhat.com/archives/libvirt-users/2019-January/msg00014.html if curious)."
1812905,2021-01-01 16:08:07 UTC,no one else seem to need this so I close.
1812909,2019-01-22 20:18:37 UTC,"I used gparted to double check and it looks like the disks application resized my extended partition, although I didn't ask it to."
1812909,2019-06-03 14:16:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1812909,2019-06-03 14:17:08 UTC,"Having specific steps/descriptions or better a screencast would help, can you add some details?"
1812909,2019-06-03 20:40:38 UTC,"Thanks for the info. I ll do a screencast next time, no prob."
1812909,2019-08-03 04:17:29 UTC,[Expired for gnome-disk-utility (Ubuntu) because there has been no activity for 60 days.]
1812915,2019-07-15 21:13:22 UTC,"As this is a low priority LP and impacts a debug tool, removing the stx.2.0 tag."
1812915,2019-01-23 18:22:24 UTC,Marking as release gating; tool is useful in debugging.
1812915,2019-05-13 13:53:34 UTC,Returning to Frank to re-assign. Irene is no longer contributing to the stx team as her coop term with WR ended.
1812916,2020-10-17 20:29:26 UTC,"loopback.cfg is supposed to be on the ISO, and cannot be provided by the package."
1812916,2020-10-17 15:58:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1812916,2020-10-17 16:17:59 UTC,"Same issue, though for some reason the menu entry seem to actually boot to the ISO just fine, which is just really strange..."
1812920,2019-07-17 13:16:10 UTC,This was fixed ages ago.
1812922,2019-01-23 20:41:21 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: master
Review: https://review.openstack.org/632562
Reason: Abandoning in favor of correct measures."
1812922,2019-01-22 21:44:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/632562"
1812922,2019-01-23 06:55:10 UTC,"I think this is the relevant logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22AssertionError%3A%20Trying%20to%20re-send()%20an%20already-triggered%20event%5C%22%20AND%20project%3A%5C%22openstack%2Fneutron%5C%22%20AND%20build_status%3A%5C%22FAILURE%5C%22%20AND%20build_name%3A%5C%22openstack-tox-py27-with-oslo-master%5C%22"
1812922,2019-01-23 07:19:49 UTC,"It is failing in periodic jobs which results can be found in http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master/
See Grafana: http://grafana.openstack.org/d/Hj5IHcSmz/neutron-failure-rate?orgId=1&panelId=38&fullscreen&from=1547623152690&to=1548227952690"
1812922,2019-01-23 12:44:47 UTC,"Seems to work fine to me locally with python 2.7, 3.5, 3.6, 3.7 and oslo.utils 3.40.1"
1812922,2019-01-23 15:18:56 UTC,"I think I see the problem here. It won't reproduce without the new oslo.service release too, which is why it's failing on the constraints bump."
1812922,2019-01-23 15:29:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632758"
1812922,2019-01-23 16:03:52 UTC,"Thanks Ben, tomorrow I change the requirements patch (https://review.openstack.org/632658) to blacklist the buggy versions."
1812922,2019-01-25 05:27:34 UTC,Change in requirements (https://review.openstack.org/632658) is on its way.
1812922,2019-01-31 05:02:11 UTC,"Reviewed:  https://review.openstack.org/632758
Committed: https://git.openstack.org/cgit/openstack/oslo.utils/commit/?id=4eb61941f811a8ab96745a5ea07e6a4a89fe764c
Submitter: Zuul
Branch:    master"
1812922,2019-02-01 19:11:11 UTC,This issue was fixed in the openstack/oslo.utils 3.40.2 release.
1812925,2019-01-28 15:44:50 UTC,AIUI there is no action for bcache-tools right now so I'm marking as Incomplete.
1812925,2019-01-25 16:12:48 UTC,Workaround for the time being until the actual root cause is identified:
1812925,2019-01-24 22:02:19 UTC,"It's failing somewhere in between: https://pastebin.canonical.com/p/bBSkf7mh9f/ (take a look at ln-sv-ostk05, it's already missing some bcaches); however they were there (see previous comment)."
1812925,2019-01-25 06:48:59 UTC,Third redeployment:
1812925,2019-01-28 15:54:29 UTC,"I spent time looking at a udev debug log and I can confirm that during a cold plug of the storage subsystem the bcache symlinks (kernel (/dev/bcache/by-{uuid/label}, dname (/dev/disk/by-dname/)) will be removed due to how the bcache driver works (it binds a backing and a cache device) and when they aren't bound, then the symlinks have no reference in the kernel and udev removes them."
1812925,2019-01-25 07:02:19 UTC,Just have run an 'udevadm trigger' before Vault unlocking and looks like it's getting that links back:
1812925,2019-01-29 17:38:01 UTC,After looking at the journal I can conclude a few things.
1812925,2019-08-16 17:09:18 UTC,"I do not think there was any remaining work for bcache-tools to do and that this is fixed, so I am marking the bcache-tools task as invalid. If my assumption is incorrect, please feel free to respond to this bug if there is open work remaining. Thanks!"
1812925,2019-01-30 21:51:18 UTC,I've recreated an VM instance that uses the curtin config attached to this bug.
1812925,2019-02-14 07:16:50 UTC,For information: I have redeployed the same bundle [with only difference - removed Livepatch references] on similar hardware and no reproducer here - all symlinks are in-place.
1812925,2019-03-19 07:55:08 UTC,"Reviewed:  https://review.openstack.org/632738
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=8655dbd9e34a31b11b276e34118e190f6bf8467e
Submitter: Zuul
Branch:    master"
1812925,2019-03-19 08:04:26 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/644503"
1812925,2019-03-19 15:36:30 UTC,"Reviewed:  https://review.openstack.org/644503
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=c8124598617f68023ed59dc207d2d4fbe25a6004
Submitter: Zuul
Branch:    stable/18.11"
1812925,2019-01-29 17:54:09 UTC,"On Tue, Jan 29, 2019 at 5:50 PM Ryan Harper <email address hidden>
wrote:"
1812925,2019-01-24 21:52:00 UTC,I just captured this once more after starting an openstack bundle deployment: https://pastebin.canonical.com/p/dhc8tBqt8Q/
1812925,2019-01-23 07:04:34 UTC,"After triggering config-changed (""juju config ceph-osd use-syslog=true"", nothing important) situation become a little better: https://paste.ubuntu.com/p/5jFd6Dg6xg/"
1812925,2019-01-24 20:21:22 UTC,After systems being idle for ~2h currently it looks like they have all the symlinks in-place:
1812925,2019-01-24 21:21:19 UTC,Just did two deployments of simple single charm in a row to exclude some openstack charm influence:
1812925,2019-01-22 22:05:31 UTC,Subscribed field-critical as this blocks us from starting handover preparations.
1812925,2019-01-22 23:07:04 UTC,in ceph-osd/0:
1812925,2019-01-22 23:20:46 UTC,"ceph-osd-3.log:
2019-01-22 15:37:39 INFO juju-log secrets-storage:118: Skipping osd devices previously processed by this unit: []
2019-01-22 15:37:39 DEBUG juju-log secrets-storage:118: Checking for pristine devices: ""[]""
2019-01-22 15:37:39 INFO juju-log secrets-storage:118: ceph bootstrapped, rescanning disks"
1812925,2019-01-23 10:35:26 UTC,When the  secrets-storage hook fire some /dev/disk/by-dname/ sym links are missing and the setup fails. Triggering a subsequent config-changed hooks seems to fix the issue as by then the symlinks have appeared. The missing symlinks can be seen in the juju unit log: https://pastebin.canonical.com/p/R2nrsFzB9g/
1812925,2019-01-23 12:25:59 UTC,"Changed to field-high since further testing unblocked, but workaround provided (like ""triggering config-changed"") is not applicable for Bootstack handover."
1812925,2019-01-22 23:15:03 UTC,in var/log/juju/unit-ceph-osd-0.log:
1812925,2019-01-24 13:43:41 UTC,OK so some digging later - we held a deployment to inspect the state of the by-dname directory before the ceph-osd charm tries to actually use the links - comparison of numbers of links in by-dname on identical servers:
1812925,2019-01-24 13:49:29 UTC,Raising a bug task for bcache-tools
1812925,2019-01-24 17:49:54 UTC,@raharper the /dev/disk/by-dname/* entries are created by the /etc/udev/rules.d/bcache*.rules created by maas whereas the /dev/bcache/by-* entries are created by /lib/udev/rules.d/69-bcache.rules from bcache-tools. The deployment in this bug is not using the /dev/bcache/by-* and is only using the by-dname bcache pointers so the question is really why the maas rules didn't run and if somehow maybe they are sometimes conflicting/racing with the bcache-utils rules such that they just never complete.
1812925,2019-01-24 13:51:35 UTC,An obvious workaround would be to trigger a re-scan before the ceph-osd charm tries to osdize the bcache devices - I would consider this a workaround only as the by-dname devices really should be present before the charm executes.
1812925,2019-01-23 14:48:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632738"
1812925,2019-01-24 13:54:10 UTC,Re-triggering udev outside of the charm creates the missing by-dname entries:
1812925,2019-01-24 17:22:01 UTC,"Looking at the syslog and kern.log, the kernel has emitted the change events which trigger the bcache rules, for all 12 devices, each time.  So what remains to understand is whether udevd ran the hook (69-bcache.rules) and I see no reason it wouldn't."
1812927,2020-03-23 04:17:38 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1812927,2020-01-10 09:49:28 UTC,Were the passwords generated before the initial deployment and untouched?
1812945,2019-09-27 09:04:45 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1812945,2019-07-10 21:40:11 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1812945,2019-06-18 03:41:22 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1812945,2019-06-06 06:24:30 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1812945,2019-04-25 12:10:37 UTC,"Reviewed:  https://review.opendev.org/653033
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ee52fb12bb42b80ace19ab898bac008076cb67e6
Submitter: Zuul
Branch:    stable/queens"
1812945,2019-04-16 15:53:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/653033"
1812945,2019-04-16 15:51:21 UTC,"Reviewed:  https://review.openstack.org/651796
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2cde44659c42ebab25259e2b05cd5c2ffe38c131
Submitter: Zuul
Branch:    stable/rocky"
1812945,2019-04-06 15:23:15 UTC,"Reviewed:  https://review.openstack.org/632598
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=79bcb4e21b7909f3e989d4fbcf68ac268680b865
Submitter: Zuul
Branch:    master"
1812945,2019-04-10 21:56:02 UTC,"Reviewed:  https://review.openstack.org/650931
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d773e3b1469a76f129d2f7a4edab68d007f3f928
Submitter: Zuul
Branch:    stable/stein"
1812945,2019-04-08 15:36:20 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650931"
1812945,2019-04-06 00:06:07 UTC,Feel free to backport this since it was introduced in Queens.
1812945,2019-03-28 01:47:37 UTC,I think so @Lee Yarwood (lyarwood)
1812945,2019-02-21 13:52:21 UTC,I wonder if we also need to drop the NoOpEncryptor?
1812945,2019-01-23 03:09:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632598"
1812945,2019-04-11 14:36:42 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/651796"
1812946,2019-05-26 18:28:21 UTC,"My understanding from the image was that this would allow conversion from any intersecting group of primitives into a polygon.  Personally, I don't see this outside of a larger graphics manipulation context but I was willing to let it sit for a while and see what kind of heat it drew."
1812946,2019-05-27 00:30:18 UTC,This bug requests any intersecting polygons from any layers can be filled on selected layer.
1812946,2019-05-26 18:14:01 UTC,Is this not what the filled polygon tools does?
1812946,2019-05-26 18:57:22 UTC,Yes I think I am working on something that will take care of this.
1812946,2019-01-23 03:52:33 UTC,On the same layer if there is a closed contour the shade tool will fill it in solid and create a solid shape.
1812946,2019-01-23 03:31:56 UTC,I'm afraid that I don't follow this request at all.  Sorry!  Can you provide a graphical example of what this would look like?
1812946,2019-01-23 03:54:19 UTC,This is especially usefull for basic shapes and will prevent users from importing bitmaps and turning them into kicad mod files by simply drawing and shading shapes straight onto the layers.
1812950,2019-01-29 09:46:41 UTC,This is indeed a charm bug as we specifically configure the use of ``/var/log/mysql/error.log`` in our templates.
1812950,2020-10-01 19:35:20 UTC,Workaround is to use https://jaas.ai/logrotated
1812951,2019-01-23 09:07:13 UTC,"It's the same issue as in bug #1243926
It requires a bit of UI redesign, hence I cannot promise to do it in the near future."
1812951,2019-01-23 20:52:02 UTC,"I understand, no problem.  Thank you for looking into it."
1812953,2019-01-23 16:27:12 UTC,See e.g. https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780501 for details.
1812954,2019-01-23 05:52:25 UTC,"As a workaround, you should be able to just set the value with:
  juju controller-config prune-txn-sleep-time=10ms"
1812954,2019-01-23 05:52:55 UTC,"Note that 2.4.8 would be the version that had the bug (if it was released), so the fix only needs to go in there so that if we *do* release 2.4.8 we don't have the bug."
1812954,2019-01-24 14:42:27 UTC,https://github.com/juju/juju/pull/9667 is merging this into 2.5
1812956,2019-09-12 14:00:44 UTC,"Is this still a problem? We build images every day in CI, including for queens."
1812956,2019-09-12 14:14:08 UTC,"Hi Mark,"
1812960,2019-08-23 13:03:35 UTC,"Change abandoned by Martin Mágr (<email address hidden>) on branch: master
Review: https://review.opendev.org/665707"
1812960,2019-07-29 21:09:33 UTC,"Reviewed:  https://review.opendev.org/640344
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=f7cc16c2359cf740c93eb153dc02e0f7aa6f0579
Submitter: Zuul
Branch:    master"
1812960,2019-07-29 21:09:17 UTC,"Reviewed:  https://review.opendev.org/640038
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=70d41af00a1d4489d37ad0659748a4ff8ce5ed1f
Submitter: Zuul
Branch:    master"
1812960,2019-09-18 19:28:41 UTC,This issue was fixed in the openstack/tripleo-common 11.2.0 release.
1812960,2019-03-01 11:49:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640344"
1812960,2019-02-28 14:19:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640038"
1812960,2019-01-23 11:10:09 UTC,The CreateDatabaseBackup depends on the mysqldump command which is not installed on the mistral_executor container.
1812960,2019-06-17 15:16:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665707"
1812968,2019-01-28 09:04:17 UTC,apport information
1812968,2019-01-28 09:04:16 UTC,apport information
1812968,2019-01-28 09:03:33 UTC,"Kernel 5.0 rc3-4
The problem remained"
1812968,2019-01-27 09:12:43 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc3 kernel[0]."
1812968,2019-01-25 02:41:29 UTC,apport information
1812968,2019-01-25 02:41:27 UTC,apport information
1812968,2019-01-25 02:41:24 UTC,apport information
1812968,2019-01-25 02:41:22 UTC,apport information
1812968,2019-01-25 02:41:21 UTC,apport information
1812968,2019-01-25 02:41:19 UTC,apport information
1812968,2019-01-25 02:41:18 UTC,apport information
1812968,2019-01-25 02:41:16 UTC,apport information
1812968,2019-01-25 02:41:12 UTC,apport information
1812968,2019-01-25 02:41:11 UTC,apport information
1812968,2019-01-25 02:41:09 UTC,apport information
1812968,2019-01-25 02:41:08 UTC,apport information
1812968,2019-01-23 10:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812968,2019-01-23 10:14:52 UTC,It's not an issue with the document viewer evince
1812968,2019-01-28 09:04:19 UTC,apport information
1812968,2019-01-25 02:41:20 UTC,apport information
1812968,2019-01-28 09:04:20 UTC,apport information
1812968,2019-01-28 09:04:35 UTC,apport information
1812968,2019-01-28 09:04:23 UTC,apport information
1812968,2019-01-28 09:04:24 UTC,apport information
1812968,2019-01-28 09:04:25 UTC,apport information
1812968,2019-01-28 09:04:26 UTC,apport information
1812968,2019-01-28 09:04:28 UTC,apport information
1812968,2019-01-28 09:04:30 UTC,apport information
1812968,2019-01-28 09:04:33 UTC,apport information
1812968,2019-01-28 09:04:21 UTC,apport information
1812968,2019-01-28 15:56:01 UTC,"I can see your system was upgraded from Ubuntu 12.04.5 LTS ""Precise Pangolin"", which uses Linux kernel v4.4, right?"
1812969,2019-07-10 21:40:35 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1812969,2019-04-15 16:38:06 UTC,"Reviewed:  https://review.openstack.org/637391
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4a7575bf1445fc111ab7d55d9fb9a11176b2dd9d
Submitter: Zuul
Branch:    stable/queens"
1812969,2019-03-24 23:39:31 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1812969,2019-03-22 03:44:12 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1812969,2019-02-14 13:41:45 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/636954"
1812969,2019-02-14 23:08:03 UTC,"Reviewed:  https://review.openstack.org/636954
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1a684f6fbef941de88556ec023860ab532938d88
Submitter: Zuul
Branch:    stable/rocky"
1812969,2019-02-14 08:01:18 UTC,"Reviewed:  https://review.openstack.org/632657
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=595866eb62db56fbd4f965619031ac902f99441a
Submitter: Zuul
Branch:    master"
1812969,2019-01-23 09:03:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632657"
1812969,2019-02-16 19:30:28 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/637391"
1812972,2019-05-14 09:44:30 UTC,"Confirmed, i just upgraded to 19.04 charms for a queens deployment and glance-registry won't start anymore due to missing paste.ini:"
1812972,2019-05-23 10:47:22 UTC,"Reviewed:  https://review.opendev.org/659030
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=efd939a188eb5c8d69fd67726f556f7700a875d5
Submitter: Zuul
Branch:    stable/19.04"
1812972,2019-05-14 13:11:34 UTC,"Reviewed:  https://review.opendev.org/659029
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=160e5d2d9f332afe6d6581bed0b590153249fdd2
Submitter: Zuul
Branch:    master"
1812972,2019-05-14 10:31:35 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/659030"
1812972,2019-05-14 10:29:57 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659029"
1812972,2019-04-10 00:57:55 UTC,"I've set this to new, because although the patch adds the package install back in, the upgrading the charm doesn't fix installations that are already broken."
1812972,2019-04-10 00:56:32 UTC,"After updating the charm to the current 18.11 (including the backport above), the glance-registry-paste.ini file is missing entirely, and reinstalling the package doesn't fix it.  I wound up manually copying in the file from the package source."
1812972,2019-02-22 14:53:09 UTC,"Reviewed:  https://review.openstack.org/638634
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=c71044ca0b36285ad790fec45e0ff9c7d7e0866b
Submitter: Zuul
Branch:    stable/18.11"
1812972,2019-02-22 11:36:16 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/638634"
1812972,2019-02-20 10:37:20 UTC,This patch did not allow glance-registry on start on bionic-queens. The charm removes glance-registry-paste.ini in reinstall_paste_ini() but this file is required for the service to start.
1812972,2019-01-24 13:43:28 UTC,"Reviewed:  https://review.openstack.org/632782
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=c24e2cf4230550741ab057eb891e9b12d6741b64
Submitter: Zuul
Branch:    master"
1812972,2019-01-23 17:01:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632782"
1812978,2020-07-24 09:54:00 UTC,"Checked on the following kernels, this is not failing anymore:
aws 5.4.0-1020.20~18.04.2-aws
aws 5.3.0-1032.34~18.04.1
aws 5.3.0-1032.34
aws 4.15.0-1079.83
aws-fips 4.15.0-2023.23
aws 4.15.0-1079.83~16.04.1
aws 4.4.0-1111.123
gcp 5.4.0-1021.21~18.04.1
gcp 5.3.0-1032.34~18.04.1
gke 5.3.0-1032.34~18.04.1
gke-generic 5.3.0-64.58~18.04.1
gke-generic  5.0.0-53.57~18.04.1
gcp 5.3.0-1032.34
gcp 4.15.0-1080.90"
1812978,2020-07-22 11:05:48 UTC,Issue found on 4.15.0-2006.7-azure-fips
1812978,2020-04-21 08:38:07 UTC,"Passed on Eoan (5.3.0-48.41):
 # selftests: net: rtnetlink.sh
 # PASS: policy routing
 # PASS: route get
 # PASS: preferred_lft addresses have expired
 # PASS: promote_secondaries complete
 # PASS: tc htb hierarchy
 # PASS: gre tunnel endpoint
 # PASS: gretap
 # PASS: ip6gretap
 # PASS: erspan
 # PASS: ip6erspan
 # PASS: bridge setup
 # PASS: ipv6 addrlabel
 # PASS: set ifalias 268cc6ee-d755-450a-bf54-432633518347 for test-dummy0
 # PASS: vrf
 # PASS: vxlan
 # FAIL: can't add fou port 7777, skipping test
 # PASS: macsec
 # PASS: ipsec
 # PASS: ipsec_offload
 # SKIP: fdb get tests: iproute2 too old
 # SKIP: fdb get tests: iproute2 too old
 ok 11 selftests: net: rtnetlink.sh"
1812978,2020-07-24 09:24:13 UTC,"For comment #6, install the module-extra package can solve this problem."
1812978,2019-01-23 10:30:13 UTC,This change was made by a bot.
1812978,2019-01-23 10:21:22 UTC,"This test has passed on B-hwe, with some syntax error:
 selftests: net: rtnetlink.sh
 ========================================
 PASS: policy routing
 PASS: route get
 PASS: tc htb hierarchy
 PASS: gre tunnel endpoint
 PASS: gretap
 Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
 [ local ADDR ]
 [ [i|o]seq ]
 [ [i|o]key KEY ]
 [ [i|o]csum ]
 [ hoplimit TTL ]
 [ encaplimit ELIM ]
 [ tclass TCLASS ]
 [ flowlabel FLOWLABEL ]
 [ dscp inherit ]
 [ fwmark MARK ]
 [ dev PHYS_DEV ]
 [ noencap ]
 [ encap { fou | gue | none } ]
 [ encap-sport PORT ]
 [ encap-dport PORT ]
 [ [no]encap-csum ]
 [ [no]encap-csum6 ]
 [ [no]encap-remcsum ]
 [ erspan IDX ]"
1812978,2019-05-24 14:34:10 UTC,"I'm seeing similar , possibly related failures on Bionic linux-aws, 4.15.0-1040.42,
I'm going to start consolidating this bug to track these failures on the various clouds."
1812980,2019-09-30 08:20:43 UTC,related pr: https://github.com/juju/juju/pull/9695
1812981,2019-01-24 04:58:55 UTC,https://github.com/juju/juju/pull/9660 is the patch for 2.4
1812981,2019-02-13 04:09:33 UTC,https://github.com/juju/juju/pull/9672 was landed.
1812986,2019-01-23 11:08:32 UTC,"Do you mean for agents talking to each other, or are you saying the
controller/provisioner talking to Openstack?"
1812986,2019-01-24 06:37:22 UTC,I mean the controller/provisioner talking to Openstack.
1812986,2019-03-20 04:31:01 UTC,"I'm fine adding some way to tell Juju that ""use 'internal' APIs rather than 'public' APIs for services"". However, I'd be curious why those are better. I thought 'internal' was meant to be 'for traffic from Openstack to Openstack, use internal, not ""for cloud traffic to the Openstack""."
1812986,2019-03-20 06:34:15 UTC,"""However, I'd be curious why those are better."" nothing is ""better"", it's just something I feel people should be able to tweak. And it would certainly help us very much in our scenario where juju is used to deploy, in the cloud, a proxy to the APIs (said proxy becoming the ""public"" endpoint, but not the internal one)."
1812986,2019-04-25 20:47:52 UTC,"Being able to juju config the model to use any of the os-internal, os-admin, or os-public hostnames would be very useful."
1812988,2019-06-24 09:48:15 UTC,"For Cosmic generic kernel, it has passed on amd64 node amaura, but failed with amd64 node gonzo."
1812988,2019-06-19 09:06:15 UTC,"For the KVM kernel,
the kernel trace is a bit different, but just like description here, it will pass when you just run this test alone."
1812988,2019-05-21 03:38:34 UTC,"I found this issue on B-hwe 4.18, node ""gonzo"" (passed on another node amaura)"
1812988,2019-03-28 04:03:33 UTC,Found on Cosmic i386 node pepe
1812988,2019-01-23 11:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1812988,2019-05-09 10:04:48 UTC,This issue does not exist on Disco.
1812999,2019-01-23 12:10:42 UTC,There are a few possible ways to implement this.
1812999,2019-11-01 21:17:30 UTC,I think we have this with the separation of the HA traffic from unit agent traffic and the startup process being brought into a more serial fashion making sure the HA peers are up before we bring in outside traffic.
1813003,2019-10-10 06:08:52 UTC,"What does the packag ""golang-github-docker-docker-credential-helpers"" do?
->It stores username and password used for `docker login` to ""docker registries"" in a ""safer way""."
1813003,2019-01-24 23:51:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813003,2019-05-09 10:33:00 UTC,"A fix could be ported, or a package could be upgraded to v0.6.2. See https://github.com/docker/docker-credential-helpers/pull/29/commits/79f93e5e69abc2ead458d19f4577b64b7e35c504"
1813003,2019-05-11 07:39:16 UTC,I agree with @anatoly.borodin - in fact the commit https://github.com/docker/docker-credential-helpers/commit/73e5f5dbfea31ee3b81111ebbf189785fa69731c and pull request https://github.com/docker/docker-credential-helpers/pull/29/commits/79f93e5e69abc2ead458d19f4577b64b7e35c504 are the same fix. It's a crying shame that @aidanh010 filed this with a link to a fix last year but then it was somehow forgotten about...
1813003,2019-05-11 07:41:05 UTC,"diff --git a/secretservice/secretservice_linux.go b/secretservice/secretservice_linux.go
index 95a1310..383b0c2 100644
--- a/secretservice/secretservice_linux.go
+++ b/secretservice/secretservice_linux.go
@@ -93,7 +93,7 @@ func (h Secretservice) List() (map[string]string, error) {
  var listLenC C.uint
  err := C.list(credsLabelC, &pathsC, &acctsC, &listLenC)
  if err != nil {
-		defer C.free(unsafe.Pointer(err))
+		defer C.g_error_free(err)
   return nil, errors.New(""Error from list function in secretservice_linux.c likely due to error in secretservice library"")
  }
  defer C.freeListData(&pathsC, listLenC)"
1813003,2019-07-17 10:14:08 UTC,"Hello, we are also affected by this bug."
1813003,2020-01-08 17:42:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813003,2020-05-25 16:58:15 UTC,(For anyone who comes across this one of the upstream issues (https://github.com/docker/docker-credential-helpers/issues/103#issuecomment-576854271 ) mentions the problem goes away if `pass` package is also installed and this seemed to make the issue disappear for me too)
1813003,2020-05-25 20:25:52 UTC,"It works for me.
I confirm that error is not displayed anymore if package 'pass' is installed."
1813007,2019-04-05 07:20:28 UTC,"Reviewed:  https://review.openstack.org/648004
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9751ebd36dc24f99b1951e928f8b910e7e0e01f7
Submitter: Zuul
Branch:    stable/queens"
1813007,2019-04-05 08:41:06 UTC,@coreycb please note that the SRU from bug 1818614 that is bundled with this one in proposed has failed verification due to a regression (see that bug for details)
1813007,2019-04-03 22:08:15 UTC,"Thanks for the heads up, Joshua!"
1813007,2019-04-08 21:29:39 UTC,"Reviewed:  https://review.openstack.org/648003
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=569b3fddaba0737f150b75cf7ec9cb4137b3991b
Submitter: Zuul
Branch:    stable/rocky"
1813007,2019-04-05 01:03:22 UTC,"Reviewed:  https://review.openstack.org/648002
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f6652f0ee6c51a0238d2b1ce10a86040456c85d9
Submitter: Zuul
Branch:    stable/stein"
1813007,2019-04-05 11:58:14 UTC,"@edward, Yes thanks for pointing that out. That will delay this fix from landing. Looks like your new fix for 1818614 is on track to land so that's good. https://review.openstack.org/#/c/649991"
1813007,2019-04-04 23:12:43 UTC,"Updated impact statement draft. If any of this information is incorrect, please feel free to correct and I will revise."
1813007,2019-04-04 18:16:36 UTC,"Here's an OSSA impact statement draft. If any of this information is incorrect, please feel free to correct me and I will revise."
1813007,2019-04-04 22:22:08 UTC,"The earliest I saw the changes that lead to this were in Pike. I agree with Corey, the pre-reqs are not there in Ocata."
1813007,2019-04-04 20:50:40 UTC,In other words I don't think or knoww if this exists on Ocata seeing as pre-reqs aren't there.
1813007,2019-04-04 20:49:48 UTC,"@Gage, regarding Ocata can you take a look at comment #30 above? https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1813007/comments/30"
1813007,2019-04-04 18:48:15 UTC,"Thanks Gage, your proposed impact description in comment #43 looks great (modulo decisions on any stable/ocata backport altering the ""affects"" line)."
1813007,2019-04-04 18:17:34 UTC,"I don't see a backport change to Ocata, are there plans on submitting one?"
1813007,2019-04-09 15:18:24 UTC,This bug was fixed in the package neutron - 2:14.0.0~rc1-0ubuntu3
1813007,2019-04-03 22:14:51 UTC,"I see backports to pike, queens, rocky and the stein release candidate branches have been proposed according to https://review.openstack.org/#/q/I17ab643abbd2ec21eda4ae1dfb9abf2d4b0657f2 and have been positively scored by some stable branch reviewers, so I'm going to take that as a sign the solution is acceptably backportable. I'll draft an impact description in a forthcoming bug comment to solicit further feedback."
1813007,2019-04-04 22:29:29 UTC,"In that case, as we expect stable/ocata is unaffected, the affects line should be revised as follows:"
1813007,2019-04-12 23:21:14 UTC,This issue was fixed in the openstack/neutron 11.0.7 release.
1813007,2019-05-01 01:50:31 UTC,"The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813007,2019-04-12 23:32:10 UTC,This issue was fixed in the openstack/neutron 12.0.6 release.
1813007,2019-09-19 10:15:12 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1813007,2019-05-13 19:18:59 UTC,"This bug was fixed in the package neutron - 2:11.0.6-0ubuntu1~cloud2.1
---------------"
1813007,2019-05-13 19:18:57 UTC,The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1813007,2019-05-09 09:59:28 UTC,This bug was fixed in the package neutron - 2:12.0.5-0ubuntu4
1813007,2019-05-08 15:32:34 UTC,Verified successfully on pike-proposed. Please see attached for results.
1813007,2019-05-08 14:51:40 UTC,Verified successfully on queens-proposed. Please see attached for results.
1813007,2019-05-08 13:48:20 UTC,Verified successfully on bionic-proposed. Please see attached for results.
1813007,2019-05-02 20:06:48 UTC,s/bionic-proposed/rocky-proposed ^^
1813007,2019-05-02 20:06:25 UTC,Verified successfully on bionic-proposed. Please see attached for results.
1813007,2019-05-01 02:00:46 UTC,This bug was fixed in the package neutron - 2:13.0.2-0ubuntu3.1
1813007,2019-04-30 19:45:36 UTC,Verified successfully on cosmic-proposed. Please see attached for results.
1813007,2019-04-17 14:20:00 UTC,"Hello Diko, or anyone else affected,"
1813007,2019-04-17 13:47:41 UTC,"Hello Diko, or anyone else affected,"
1813007,2019-04-16 17:56:22 UTC,This issue was fixed in the openstack/neutron 14.0.1 release.
1813007,2019-04-15 13:45:29 UTC,"Hello Diko, or anyone else affected,"
1813007,2019-04-12 23:32:05 UTC,This issue was fixed in the openstack/neutron 13.0.3 release.
1813007,2019-04-03 21:38:46 UTC,"Red Hat are treating this as a security issue, whilst similar to OSSA-2019-001 it is not considered quite as severe."
1813007,2019-04-05 01:19:23 UTC,"Reviewed:  https://review.openstack.org/648102
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a9bc8ab1e1931aac84f30e29412f17264d88a5a0
Submitter: Zuul
Branch:    stable/pike"
1813007,2019-04-01 13:46:40 UTC,"Hello Diko, or anyone else affected,"
1813007,2019-02-28 10:28:18 UTC,I've not yet been able to recreate this but it's possible I'm doing something wrong.
1813007,2019-02-28 09:27:33 UTC,s/neutron-gateway/neutron-openvswitch
1813007,2019-02-28 09:27:20 UTC,Note that for a charm deployment this requires neutron-gateway to use:
1813007,2019-02-28 09:21:03 UTC,The follow security group commands should resemble what causes the issue:
1813007,2019-02-27 21:48:53 UTC,For now we have this marked private as a security issue for that reason ^.
1813007,2019-02-27 21:48:28 UTC,"@elmo Agreed, if a user can crash neutron-ovs-agent on a compute node that's not good. I'll dig more in the morning."
1813007,2019-02-27 21:20:35 UTC,Also - super important detail is that the cloud in question is using the openvswitch firewall driver (per /etc/plugins/ml2/openvswitch_agent.ini) and not the default iptables based one.
1813007,2019-02-27 21:17:40 UTC,"@corey.byrant This is a managed customer cloud so we can't provide the exact commands used to trigger this because we didn't create the security group rules - our customer's customer did.  Also, you seem to be assuming these rules make sense but it's not at all a given that they do; I suspect they were created by mistake."
1813007,2019-02-27 19:38:17 UTC,Marking private as this may be a security issue.
1813007,2019-02-27 17:14:31 UTC,@dparv
1813007,2019-01-23 18:01:13 UTC,"Note, this is a Xenial queens install."
1813007,2019-01-23 17:53:53 UTC,"Found https://paste.ubuntu.com/p/s5Z4DNJspV/ missing.
New copy here: https://pastebin.ubuntu.com/p/g7Q3nFmhWN/"
1813007,2019-01-23 13:27:21 UTC,It affects qpenstack queens; neutron-openvswitch-agent 2:12.0.5-0ubuntu1~cloud0.
1813007,2019-01-23 12:59:33 UTC,"Hi,
Could you please specify which openstack/neutron release are you using, and add the relevant logs to the bug report as pastebin is not visible for everybody."
1813007,2019-01-23 12:28:30 UTC,It's affecting neutron-openvswitch-agent             2:12.0.5-0ubuntu1~cloud0
1813007,2019-02-28 10:53:01 UTC,"Ok I've recreated this, I just needed to deploy an instance. I'll work on getting some clear steps together for recreating."
1813007,2019-02-28 13:51:30 UTC,"Here are the steps I used to reproduce this, using juju but of course it should be simple enough to recreate with other deployment tooling."
1813007,2019-02-27 14:59:58 UTC,I'm working on recreating this but any more details you can provide in the mean time will help speed that up (ie. juju crashdump and ensuing commands that lead up to the error).
1813007,2019-02-28 15:43:22 UTC,Currently am unable to test on stein but assuming for now that this is also broken there.
1813007,2019-02-28 15:41:50 UTC,I was able to recreate this on a bionic-rocky deployment as well.
1813007,2019-04-01 13:45:47 UTC,"Hello Diko, or anyone else affected,"
1813007,2019-03-29 12:53:58 UTC,Is there a chance anyone's working on backporting I17ab643abbd2ec21eda4ae1dfb9abf2d4b0657f2 upstream to stable/pike through stable/rocky? Is the impact roughly similar in nature to https://security.openstack.org/ossa/OSSA-2019-001.html or can someone make an attempt at describing a viable exploit scenario so we can draft an appropriate impact description?
1813007,2019-03-29 10:23:34 UTC,"Hello Diko, or anyone else affected,"
1813007,2019-03-29 10:21:49 UTC,"Hello Diko, or anyone else affected,"
1813007,2019-03-27 16:48:46 UTC,"Hello Diko, or anyone else affected,"
1813007,2019-03-27 14:24:42 UTC,"New versions of the Ubuntu neutron package have been uploaded to disco, cosmic, and bionic unapproved queues where they are awaiting review by the SRU team, and also be uploaded to pike-staging."
1813007,2019-03-27 13:28:41 UTC,For Ubuntu I've dropped pre-Pike releases from affected series as a fix for https://bugs.launchpad.net/neutron/+bug/1708092 would be a pre-requisite at least for Ocata. That fix is fairly involved and we would have to evaulate the risk of backporting that to Ocata if in fact any fixes were needed back that far.
1813007,2019-04-02 14:45:13 UTC,"This bug was fixed in the package neutron - 2:14.0.0~rc1-0ubuntu2~cloud0
---------------"
1813007,2019-03-01 03:24:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640252"
1813007,2019-03-27 02:09:04 UTC,"Reviewed:  https://review.openstack.org/640252
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=18c578aa10c19a6befdf1f1510645200f173eb44
Submitter: Zuul
Branch:    master"
1813007,2019-03-01 03:13:30 UTC,"I'll work on this change, think I have a fix, just need to get some reviews."
1813007,2019-02-28 21:42:19 UTC,Thanks Gage.
1813007,2019-02-28 19:18:55 UTC,"Since this was public for about a month prior to making private, it doesn't seem worth keeping under embargo here. Getting this fixed quickly is preferable and opening it up publicly would allow more eyes on it and easier communication to help fix this."
1813007,2019-02-28 17:35:28 UTC,Apologies for the delay:
1813007,2019-02-28 17:21:35 UTC,"This also occurs on xenial-pike, but not on xenial-ocata."
1813011,2019-05-06 18:41:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813018,2019-10-21 14:40:42 UTC,@mluypaert
1813018,2019-10-29 17:56:53 UTC,Checking if this snippet is properly spaced in a LP comment text (instead of Description.)
1813018,2019-10-29 17:57:46 UTC,"Not quite -- using a pastebin (expire 1y):
https://pastebin.ubuntu.com/p/pjMNxkJfJy/"
1813018,2019-10-29 18:05:13 UTC,Test-case snippet on modified kernel on ESM (3.13.0-174.225 + patch)
1813018,2019-10-29 18:04:25 UTC,Test-case snippet on original kernel on ESM (3.13.0-174.225)
1813018,2019-10-21 08:54:37 UTC,Hi @mfo
1813018,2019-11-18 23:14:56 UTC,Verification on Trusty ESM updates.
1813018,2019-11-20 00:30:33 UTC,"This bug has been fixed on Ubuntu 14.04 ESM,
linux kernel package version 3.13.0-175.226."
1813018,2019-10-29 18:03:57 UTC,Test-case snippet on original kernel (3.13.0-170.220)
1813018,2019-10-21 01:04:20 UTC,"Hi @mluypaert,"
1813018,2019-01-23 14:08:55 UTC,apport information
1813018,2019-01-23 14:08:56 UTC,apport information
1813018,2019-01-23 14:08:53 UTC,apport information
1813018,2019-01-23 14:08:52 UTC,apport information
1813018,2019-01-23 14:08:50 UTC,apport information
1813018,2019-01-23 14:08:49 UTC,apport information
1813018,2019-01-23 14:08:46 UTC,apport information
1813018,2019-01-23 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813018,2019-01-23 14:09:00 UTC,apport information
1813018,2019-01-23 14:08:47 UTC,apport information
1813021,2019-09-19 12:07:41 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1813025,2019-10-07 22:44:55 UTC,"RBAC is now in edge snap.
This should be solved by proper RBAC setup in the charm."
1813025,2019-08-15 05:42:32 UTC,We currently do not support setting up service accounts or rbac (in juju 2.6). This feature is being added to 2.7 and will be available to test via the edge snap in a few weeks.
1813026,2019-02-12 15:50:15 UTC,"This bug is fixed by the following upstream commit:
d3736d82e816 (“tty: Don't hold ldisc lock in tty_reopen() if ldisc present”)"
1813026,2019-01-24 00:20:32 UTC,"While I do not see the commit in the 4.18.0-1008 changelog ( https://launchpad.net/ubuntu/+source/linux-azure-edge/4.18.0-1008.8~18.04.1 ) I would plant the upstream bisect near ""Input: hyper-v - fix wakeup from suspend-to-idle"" which was merged upstream in December:"
1813027,2019-03-15 14:08:39 UTC,https://review.openstack.org/#/c/643390/
1813030,2019-10-24 22:01:30 UTC,"Any update on this? It doesn't look like our eventlet req has been updated in a couple of years, so I'm guessing it isn't done: https://github.com/openstack/oslo.messaging/blame/master/test-requirements.txt"
1813031,2020-03-07 15:31:59 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1813032,2019-01-23 15:44:00 UTC,Probably also related https://review.openstack.org/#/c/625078/ (https://bugs.launchpad.net/tripleo/+bug/1792613)
1813032,2019-01-23 15:45:08 UTC,https://review.openstack.org/#/c/632745/
1813032,2019-01-23 19:18:10 UTC,"Change abandoned by Jiri Stransky (<email address hidden>) on branch: master
Review: https://review.openstack.org/632745
Reason: This is not a path forward"
1813038,2019-11-01 17:54:45 UTC,Cool.  I'll keep an eye out...
1813038,2019-11-01 17:02:02 UTC,@Jeff-  I pushed a small mod here to focus on the duplication action.  Let me know if it misses any of the cases you were seeing
1813038,2019-09-03 15:53:33 UTC,"@Aleksandr, new bits up.  Let me know if this one works any better in the 5.1 tree..."
1813038,2019-09-03 12:48:07 UTC,"Yeah, there were a bunch of fixes to the point editor which this is now running into.  There may be too many divergences to backport this one.  However, let me try one more idea...."
1813038,2019-09-02 19:53:58 UTC,"@Aleksandr, cool.  I've made a modification to the fix.  Can you try it and see if it fixes the performance issue?  If so I'll cherry-pick the two of them back to 5.1."
1813038,2019-09-02 22:10:09 UTC,"With the attached here patch applied, the performance when moving duplicated items is still low. But when duplicating, the duplicated items do not follow the cursor at all, until I zoom/pan. Also, when moving lines/polygons/zones, their control points now do not move with the rest of the item."
1813038,2019-09-02 18:20:12 UTC,"@Aleksandr, do you mean that you applied this patch to your local 5.1 tree and did a build from there?  (As far as I'm aware this patch wasn't cherrypicked back into 5.1.)"
1813038,2019-09-02 15:15:22 UTC,"While trying to use this patch with 5.1 branch, I noticed ~2-3x slowdown while moving interf_u board (opengl canvas, ratsnest disabled), compared with a similar debug build without the patch. It takes 434 vs 166 ms to update footprint location."
1813038,2019-07-07 21:32:38 UTC,"Fixed in revision 986392d88e9eff86cb80d90d833c7545c9e6d38b
https://git.launchpad.net/kicad/patch/?id=986392d88e9eff86cb80d90d833c7545c9e6d38b"
1813038,2019-01-27 17:37:34 UTC,This also happens when modifying duplicated graphics.
1813038,2019-09-02 18:40:31 UTC,"Yes, I ported this to 5.1 revision 1ed8912f5762043489efab1f52e2f1c9330fdf43 and built (because I do not use 6.0 yet but was curious why this wasn't cherry-picked into 5.1). I attached the exact diff."
1813046,2019-01-23 18:00:09 UTC,"Emilien, can you try rebooting your host please?
Attached is my log, it worked. I'm running toci now, you can have my env when it comes up."
1813047,2019-01-25 12:03:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633190"
1813047,2019-01-31 10:14:38 UTC,"Hi,"
1813047,2019-01-31 11:20:27 UTC,"Hi Bence,"
1813047,2019-12-04 08:46:03 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1813047,2019-12-04 08:46:13 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/633190
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1813052,2019-01-25 23:25:01 UTC,reassign 1813052 systemd
1813052,2019-01-25 23:26:07 UTC,"reassign 1813052 systemd
thanks"
1813052,2019-01-25 23:17:15 UTC,"OK, I found a workaround:"
1813052,2019-01-25 23:46:48 UTC,re-assigning to systemD as requested.
1813052,2019-01-23 19:07:06 UTC,"Attempting to diagnose, I had added /var/run/utmp and /var/run/utmpx as directories.  I just removed those, same empty result:
# who
# who;echo $?
0
# strace who
execve(""/usr/bin/who"", [""who""], [/* 21 vars */]) = 0
brk(NULL)                               = 0x1726000
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
access(""/etc/ld.so.preload"", R_OK)      = -1 ENOENT (No such file or directory)
open(""/etc/ld.so.cache"", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0bce0000
close(3)                                = 0
access(""/etc/ld.so.nohwcap"", F_OK)      = -1 ENOENT (No such file or directory)
open(""/lib/x86_64-linux-gnu/libc.so.6"", O_RDONLY|O_CLOEXEC) = 3
read(3, ""\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0""..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7efc0bcdf000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7efc0b70e000
mprotect(0x7efc0b8ce000, 2097152, PROT_NONE) = 0
mmap(0x7efc0bace000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c0000) = 0x7efc0bace000
mmap(0x7efc0bad4000, 14752, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7efc0bad4000
close(3)                                = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7efc0bcde000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7efc0bcdd000
arch_prctl(ARCH_SET_FS, 0x7efc0bcde700) = 0
mprotect(0x7efc0bace000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ)     = 0
mprotect(0x7efc0bcfd000, 4096, PROT_READ) = 0
munmap(0x7efc0bce0000, 117369)          = 0
brk(NULL)                               = 0x1726000
brk(0x1747000)                          = 0x1747000
open(""/usr/lib/locale/locale-archive"", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0b436000
close(3)                                = 0
access(""/var/run/utmpx"", F_OK)          = -1 ENOENT (No such file or directory)
open(""/var/run/utmp"", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
access(""/var/run/utmpx"", F_OK)          = -1 ENOENT (No such file or directory)
open(""/var/run/utmp"", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
close(1)                                = 0
close(2)                                = 0
exit_group(0)                           = ?
+++ exited with 0 +++
#"
1813052,2019-01-25 20:17:02 UTC,"Oh, and to be clear, this is a regression."
1813056,2019-05-20 17:01:17 UTC,A proposed fix is at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1813056_circ_history_csv_checkin
1813056,2019-09-13 21:03:24 UTC,EG 3.3.3 - I can confirm that I still see this issue without the fix.
1813056,2019-10-03 21:37:40 UTC,"Pushed all the way back to rel_3_1. Thanks, Garry and Josh!"
1813057,2019-07-09 04:59:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669790"
1813057,2019-07-18 16:54:11 UTC,"Reviewed:  https://review.opendev.org/669790
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4fb4d8b8a4055dfacf13a409e590485461d766b2
Submitter: Zuul
Branch:    master"
1813057,2019-09-27 09:10:40 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1813060,2019-02-18 13:53:33 UTC,Due to scripts/check-installed-headers.sh using a regex to search for obsolete types.
1813060,2019-02-19 08:57:29 UTC,Proposed fix:
1813060,2019-02-20 08:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813060,2019-02-20 08:34:25 UTC,We've applied a patch temporarily to replace ulong in the comment with unsigned long to avoid having glibc tests broken in ADT. Once the glibc test has been updated we can revert the patch in the kernel.
1813060,2019-03-11 16:44:48 UTC,This bug was fixed in the package linux - 5.0.0-7.8
1813068,2019-08-05 08:28:39 UTC,This bug was fixed in the package rtl8812au - 4.3.8.12175.20140902+dfsg-0ubuntu8.1
1813068,2019-05-17 18:23:53 UTC,"Hello Seth, or anyone else affected,"
1813068,2019-08-02 14:41:47 UTC,This fix works as intended.
1813068,2019-08-05 08:28:47 UTC,"The verification of the Stable Release Update for rtl8812au has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813068,2019-05-08 21:44:19 UTC,Experiencing this same issue on bionic/linux-hwe-edge:
1813068,2019-02-11 19:43:29 UTC,This bug was fixed in the package rtl8812au - 4.3.8.12175.20140902+dfsg-0ubuntu10
1813068,2019-02-07 16:03:15 UTC,Debdiff attached.
1813068,2019-05-09 17:18:43 UTC,Attaching revised .debdiff containing provenance for these changes.
1813073,2019-02-01 20:39:35 UTC,This bug was fixed in the package xtables-addons - 3.2-1ubuntu1
1813073,2019-04-24 17:41:15 UTC,"Hello Seth, or anyone else affected,"
1813073,2019-07-24 19:29:19 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1813073,2019-08-05 09:43:30 UTC,ii  xtables-addons-dkms                  3.0-0.1ubuntu1
1813073,2019-08-05 10:07:25 UTC,This bug was fixed in the package xtables-addons - 3.0-0.1ubuntu2
1813073,2019-08-05 10:07:29 UTC,"The verification of the Stable Release Update for xtables-addons has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813076,2019-01-24 02:51:26 UTC,Excellent question. If we lie about the version of Safari it might cause other tools to emit HTML etc that it can't parse.
1813076,2019-01-24 03:37:41 UTC,"Wait a second - is goa based on Safari code?  Is that why it's being shut-out from DUO?  And, I'm not suggesting that anyone lie - I suspect that DUO is misreading goa as Safari."
1813077,2019-07-06 21:55:42 UTC,"Fixed in revision 70ca02537d1f91b162123e00db3500fee72046e6
https://git.launchpad.net/kicad/patch/?id=70ca02537d1f91b162123e00db3500fee72046e6"
1813077,2019-01-27 18:27:28 UTC,Should this be fixed for 5.1?  It seems to me like it should.
1813078,2019-08-01 20:21:53 UTC,"Good catch, Garry.  I've pushed this to master, rel_3_3, rel_3_2, and rel_3_1.  Thanks, Terran, Garry, and Kyle."
1813078,2019-05-20 18:50:35 UTC,"The menu font changes color when the browser is sized to a width between 768px and 800px.  Here's a patch that changes css so that the change takes place at 768px, the md column definition for bootstrap.
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1813078_menus_sometimes_grayed_out"
1813078,2019-07-22 17:55:35 UTC,"I have tested this code and consent to signing off on it with my name, Kyle Huckins and my email address, <email address hidden>."
1813078,2019-05-20 17:35:27 UTC,"Also happens in Chrome on a Mac.  It occurs when you are collapsing the screen, right before the menus collapse into a hamburger menu."
1813086,2019-01-25 14:34:40 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1813088,2019-01-24 14:30:01 UTC,"This column is displaying Yes/No on our production server, (3.0.12), but is not populating on our training server, (3.2.2)."
1813088,2019-10-15 21:39:42 UTC,This column displays but doesn't populate values in the Hold Shelf or View Holds (in the record) in 3.3.4
1813088,2019-10-15 21:58:49 UTC,Values (Yes/No) populate on our 3.1.7 test server for both Hold Shelf and View Holds.
1813088,2020-03-23 12:54:12 UTC,"This looks to be a more general bug than just this one field. None of the Boolean fields populate values for me on a 3.2 test system. I suspect this is related to the hold fetch speed up code introduced in bug 1712854. The code for that appears in Evergreen 3.2+, but not 3.0 nor 3.1."
1813088,2020-03-26 15:14:39 UTC,It turns out that the problem was an integer versus string value in egGridFilterValue. The branch below alters the check for Boolean columns to force a comparison on string types. Thanks to Mike Rylander for pointing out the type mismatch in IRC!
1813088,2020-03-27 18:23:21 UTC,"Thanks for your work on this patch, Jason."
1813088,2020-05-01 17:27:40 UTC,"Works for me too.  Pushed to 3.3, 3.4, 3.5, and master.  Thanks, John and Jason!"
1813090,2019-10-26 14:49:50 UTC,"I've been dealing with this issue for years and finally tracked it down a few minutes ago.
This is caused by the line:"
1813090,2019-01-24 00:22:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1813090,2019-10-26 14:52:25 UTC,re-adding attachment due to copy&paste error
1813090,2019-10-26 16:28:03 UTC,"The attachment ""add -g to declare of _xspecs to ensure it stays in the global scope"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1813095,2019-06-14 06:20:28 UTC,"We meet same error, manila-6.0.1 with Generic driver.
Share server never get created succesfully."
1813095,2019-03-01 18:11:21 UTC,As we discussed on irc but for the record here one uses 'sudo systemctl restart devstack@m-shr' to restart the share service.
1813095,2019-03-01 16:11:04 UTC,"Hi!
Which file does manila.conf refer to and where can I find it?
Also what should be the expected behavior after introducing the error in the conf file?"
1813095,2019-03-01 16:28:15 UTC,I found out the location of the file and made the said changes. I wanted to know how do we restart the manila services after that?
1813095,2019-02-27 14:23:06 UTC,Hi! I intend to apply for Outreachy Summer 2019 and would like to work on this issue as my first contribution.
1813095,2019-01-24 01:12:54 UTC,The fix for this bug is to prevent updating the database with NULL values
1813095,2019-02-27 14:49:45 UTC,Varsha - thanks for picking this one up!
1813104,2019-01-24 14:24:15 UTC,"logsink.go needs a bunch more logging added, so that you can set DEBUG and see the level of granularity that we see on /api. It doesn't have to be *every* log message, but you should see a message every time an agent connects, what agent, for what model, and when they disconnect."
1813104,2019-01-24 13:51:20 UTC,"I also set up a 'badlogsender.go' (attached). This randomly corrupts a packet so that it introduces a write error into the system. However, I still don't see any leaking goroutines."
1813104,2019-01-24 13:50:46 UTC,"After running 200 concurrent loggers repeated 10x, and letting the machine sit for a bit, the memory seems to have gone back down.
So it doesn't seem to be a reproducer."
1813104,2019-01-25 01:56:45 UTC,"From the goroutine dump we could see that the leaked goroutines were blocked sending on logCh, so it seems like the ServeHTTP handler has finished (so nothing is reading on logCh). This PR adds a channel that gets closed when the handler finishes to avoid that situation.
https://github.com/juju/juju/pull/9669"
1813104,2019-01-24 08:18:35 UTC,"I wrote a go script that connects to the Juju Log endpoint, and sends messages (as fast as possible) for 5s. (see attached)"
1813104,2019-01-24 04:54:39 UTC,(note that the original heap dumps have 1 line from stderr at the top that have to be trimmed. I've attached a tar of the cleaned up dumps to this bug).
1813104,2019-01-24 10:14:33 UTC,"After running 200 concurrent loggers repeated 10x, and letting the machine sit for a bit, the memory seems to have gone back down.
So it doesn't seem to be a reproducer."
1813106,2019-01-24 05:56:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632933"
1813106,2019-11-12 08:52:39 UTC,"Change abandoned by pengyuesheng (<email address hidden>) on branch: master
Review: https://review.opendev.org/632933"
1813112,2019-09-07 18:27:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813112,2020-01-09 00:27:03 UTC,"I have seen this in about 20 Lubuntu/Ubuntu 16.04 installations dist upgraded to 18.04
Also it works in some others.."
1813116,2019-01-29 15:42:45 UTC,"Hi Bence,
thank you for your report.
It's not easy to implement what you request. It was already difficult to implement the save/resume feature..."
1813117,2019-02-19 12:57:22 UTC,maybe we can remove the one in taas_db.
1813118,2019-06-27 07:45:38 UTC,"Hmm wait a second, I think I was check on P8 instead of P9, let me check this again."
1813118,2019-08-22 16:16:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1813118,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1813118,2019-07-16 09:45:52 UTC,The copy_unaligned test was removed as expected.
1813118,2019-06-27 07:33:29 UTC,PowerPC test passed as expected on baltar with Cosmic kernel.
1813118,2019-01-24 07:30:07 UTC,This change was made by a bot.
1813118,2019-06-18 12:02:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1813118,2019-05-14 09:01:46 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-May/100696.html
1813118,2019-05-13 11:17:42 UTC,"B:
  * 8d1915873d492b8e1f03bbcab527db62a8d49542
  * 83039f22ba2f6aff935a2acbb6bf671374e8317d
C:
  * 83039f22ba2f6aff935a2acbb6bf671374e8317d"
1813118,2019-06-18 16:02:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813126,2019-08-13 04:17:32 UTC,[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]
1813126,2019-06-13 15:57:19 UTC,"Disregard my post, my issue was unrelated. (I inadvertently must have removed my crypttab file, sigh.)"
1813126,2019-06-07 17:18:14 UTC,"I can confirm similar behavior, but slightly different setup."
1813126,2019-06-04 18:51:10 UTC,Further investigation revealed that a change to the semantics of 'cryptsetup' tool is responsible for the specific manual build I did.
1813126,2019-06-04 16:20:35 UTC,"I've confirmed this with a new 19.04 install, and it's not just the d-r-u process."
1813126,2019-01-24 07:58:57 UTC,"To me, this seems related to #1062623."
1813126,2019-06-04 17:29:47 UTC,"If you manage to boot off a USB key or something else and discover the drives, can you then run grub-probe on the device to check if grub correctly identifies the disk as a crypto disk?"
1813127,2019-02-15 14:42:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813127,2019-03-04 06:46:02 UTC," selftests: ptrace-tm-spd-gpr
 ========================================
 test: ptrace_tm_spd_gpr
 tags: git_version:unknown
 success: ptrace_tm_spd_gpr
 ok 1..3 selftests: ptrace-tm-spd-gpr [PASS]"
1813127,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1813129,2019-05-16 15:03:57 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813129,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1813129,2019-04-23 11:00:35 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100310.html
1813129,2019-05-21 10:07:10 UTC,Passed with Bionic PowerPC
1813129,2019-01-24 09:00:13 UTC,This change was made by a bot.
1813129,2019-04-23 08:38:22 UTC,"Tested on Bionic P9 with the latest kernel tree from upstream, this test will pass (skipped):
 selftests: tm: tm-unavailable
 ========================================
 test: tm_unavailable_test
 tags: git_version:v5.1-rc6-0-g085b77558-dirty
 [SKIP] Test skipped on line 346
 skip: tm_unavailable_test
 ok 1..10 selftests: tm: tm-unavailable [PASS]"
1813131,2020-05-02 01:51:54 UTC,I can confirm this is not working on Bionic. vainfo output:
1813131,2019-08-14 01:48:35 UTC,This bug now affects Bionic (and the core18 snap as a result) after picking up Mesa 19 from Disco in the 18.04.3 HWE release.
1813131,2020-04-03 01:43:00 UTC,"Sorry for the confusion, I was travelling at the time of comment #20. Mention of ""wl_drm_interface"" in bug 1866356 convinces me that it's just a duplicate of this one. And this one is still open for bionic."
1813131,2020-03-06 16:00:49 UTC,Comments #17 and #19 might be a different bug (bug 1866356). I'm not sure yet...
1813131,2020-03-06 14:38:58 UTC,This is still an issue which requires a fix asap. It is affecting bionic release 18.04.4 LTS
1813131,2019-10-15 01:28:49 UTC,That *might* be a different bug. This bug is specifically about:
1813131,2019-10-14 15:16:24 UTC,Same for me  on Bionic.
1813131,2019-09-06 08:14:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813131,2019-08-14 07:27:25 UTC,so libva/intel-vaapi-driver needs fixing in bionic now
1813131,2019-03-13 08:45:43 UTC,This bug was fixed in the package intel-vaapi-driver - 2.3.0-0ubuntu2
1813131,2019-03-13 02:09:34 UTC,The bug is still present in i965-va-driver 2.3.0-0ubuntu1 on disco.
1813131,2019-03-13 04:48:03 UTC,"The ubuntu package doesn't include needed patch, i.e
0004-Check-the-interface-from-libva-first.patch"
1813131,2019-03-12 13:18:27 UTC,This bug was fixed in the package intel-vaapi-driver - 2.3.0-0ubuntu1
1813131,2019-02-13 21:57:43 UTC,"Is a newer intel-vaapi-driver package planed?
(- currently in Debian Sid & does fix the issue in a wayland session.."
1813131,2019-02-02 13:35:41 UTC,Fixed in 2.4.0-1.
1813131,2019-01-27 17:59:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813131,2019-01-25 07:28:58 UTC,probably needs a newer libva too
1813131,2019-01-25 07:28:05 UTC,moving back to the driver
1813131,2019-01-24 10:59:34 UTC,"it's a bug in the mesa build which is using meson now, it doesn't link with libwayland_drm, not sure why"
1813132,2019-09-25 19:03:04 UTC,"For me this happens without hovering over any menu, it's enough to start VLC from the command line with ""vlc"" for it to crash in libmicrodns. Please, backport a working version to Ubuntu 18.04."
1813132,2019-06-02 12:41:19 UTC,This issue has to be fixed in Ubuntu's version of libmicrodns. No change in vlc is required.
1813132,2019-05-31 23:09:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813134,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1813134,2019-01-24 09:30:07 UTC,This change was made by a bot.
1813134,2019-05-16 15:03:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813134,2019-05-17 03:04:38 UTC,Test no longer exist.
1813136,2019-05-09 10:17:14 UTC,Correction: this test can be found failed with Disco with Power9 (ok with P8)
1813136,2019-04-23 08:28:04 UTC,"Tested with upstream code on Bionic P9, this issue can still be reproduced."
1813136,2020-02-21 11:16:25 UTC,Failed with Eoan on P9 (passed with P8)
1813136,2020-03-25 08:45:57 UTC,"On Bionic P9, this issue still exist on P9.
On Eoan P9, it's now:
  not ok 6 selftests: dscr: dscr_sysfs_test # TIMEOUT"
1813136,2019-01-24 10:00:07 UTC,This change was made by a bot.
1813136,2020-05-15 08:48:22 UTC,"This issue does not exist on Eoan P9
Fixed by this commit.
https://github.com/torvalds/linux/commit/850507f30c38dff21ed557cb98ab16db26c32bbc"
1813138,2019-01-24 10:40:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/632982"
1813138,2019-01-28 12:40:17 UTC,Note: I updated the bug title and description. Initially i made a connection to the provider_location attribute which was wrong.
1813140,2019-01-24 10:00:14 UTC,This change was made by a bot.
1813140,2019-04-23 08:33:27 UTC,"Tested on Bionic P9 with the latest kernel tree from upstream, this issue still exist."
1813141,2019-01-24 09:58:24 UTC,dmesg output when launching Cheese
1813141,2019-01-24 10:00:22 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813141,2019-01-24 10:13:20 UTC,apport-collect 1813141 : error : connecting to Launchpad failed...
1813141,2019-04-21 10:24:26 UTC,"The new version of Gstreamer could resolve this bug ?
https://bugzilla.gnome.org/show_bug.cgi?id=796789"
1813142,2019-01-24 10:30:08 UTC,This change was made by a bot.
1813142,2020-06-18 06:17:47 UTC,Does this issue still happen under 20.04?
1813142,2020-08-18 04:17:27 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1813146,2019-01-28 08:25:12 UTC,I have to check.
1813147,2019-09-14 00:09:45 UTC,"Reviewed:  https://review.opendev.org/682133
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2973faa07063d2112ef7459ab07cc07e20d74610
Submitter: Zuul
Branch:    master"
1813147,2019-09-13 19:09:04 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/682140"
1813147,2019-09-13 18:21:41 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/682133"
1813147,2019-06-16 03:33:30 UTC,"Reviewed:  https://review.opendev.org/662965
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0956539edf93736ef23169610b08959a69ec0d92
Submitter: Zuul
Branch:    stable/stein"
1813147,2019-05-02 16:54:29 UTC,For the issue in comment 35 I wonder if we could flush the stdio buffer between runs of each sub-action in that test.
1813147,2019-06-04 08:06:37 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/662965"
1813147,2019-05-02 17:01:42 UTC,So one issue is we're getting a giant traceback because these tests are using the CastAsCall fixture and we're not registering an expected_exception so we get a big traceback from oslo.messaging:
1813147,2019-05-03 00:35:41 UTC,"Reviewed:  https://review.opendev.org/656633
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=84e64a995eb456772519ba26dc8a98f042a7a44a
Submitter: Zuul
Branch:    master"
1813147,2019-05-02 19:47:03 UTC,"It's the notification listener in oslo.messaging that logs the traceback, that's why it wasn't the CastAsCall thing I was expecting:"
1813147,2019-05-02 18:27:23 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/656844"
1813147,2019-05-02 17:53:24 UTC,The test injects an exception here [1] that cause the stack trace.
1813147,2019-05-02 17:43:05 UTC,Actually the test isn't using the CastAsCall fixture so I'm not sure why we're getting the traceback from oslo.messaging since I thought that was only used if you're doing a synchronous RPC call.
1813147,2019-09-14 13:40:53 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/682210"
1813147,2019-06-03 19:25:34 UTC,"Reviewed:  https://review.opendev.org/656844
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=93027713ab614b59ebb66f0617f85d43c956427c
Submitter: Zuul
Branch:    master"
1813147,2019-09-14 17:29:36 UTC,"Reviewed:  https://review.opendev.org/682140
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bb2b7cad294bebd6b3bdd6d10043c3c2fb038140
Submitter: Zuul
Branch:    master"
1813147,2019-01-31 22:44:04 UTC,https://review.openstack.org/#/c/625125/ could help glance if someone can update it.
1813147,2019-09-25 15:23:54 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/684781"
1813147,2020-03-23 14:10:26 UTC,"Reviewed:  https://review.opendev.org/713611
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a2f30f9d7cad1c025592c1087ff0cba6dec9a309
Submitter: Zuul
Branch:    master"
1813147,2019-05-02 16:39:24 UTC,We seem to be hitting this in nova again with a notifications functional test:
1813147,2020-03-19 15:50:42 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/700522
Reason: This should be resolved with testtools 1.4.0 and whatever the next version of stestr ends up being"
1813147,2020-03-18 10:21:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/713611"
1813147,2019-12-24 18:31:12 UTC,"I have a potential ""fix"" for this proposed at [1], with a related change for stestr here [2]."
1813147,2019-12-24 17:17:49 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/700522"
1813147,2019-09-18 17:31:32 UTC,"Reviewed:  https://review.opendev.org/682210
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6b5e81df55394a87ec7c3e2fb75618506fffaa6
Submitter: Zuul
Branch:    stable/stein"
1813147,2019-12-09 21:38:06 UTC,"Reviewed:  https://review.opendev.org/697301
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=945d662d4f0a0b1b14f32ab92aaf3f0f35e0be4b
Submitter: Zuul
Branch:    master"
1813147,2019-10-22 16:27:57 UTC,"Reviewed:  https://review.opendev.org/685072
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=58ad6aba98afe25a0f596decce3af567d0abe4e0
Submitter: Zuul
Branch:    stable/stein"
1813147,2019-10-09 21:07:13 UTC,"Reviewed:  https://review.opendev.org/686836
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c27f3cdc0538c2b8a14cf309f04acaf1599a44b
Submitter: Zuul
Branch:    master"
1813147,2019-10-04 20:51:28 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/686836"
1813147,2019-09-26 13:32:34 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/685072"
1813147,2019-09-25 23:11:14 UTC,"Reviewed:  https://review.opendev.org/684772
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d0ca30b80a5063d5541587deda33e1a466a10f30
Submitter: Zuul
Branch:    master"
1813147,2019-09-25 23:11:03 UTC,"Reviewed:  https://review.opendev.org/684781
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=79ee80d159e8be0d9f8215c2c5e210c545c551a7
Submitter: Zuul
Branch:    master"
1813147,2019-12-04 14:53:47 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/697301"
1813147,2019-05-01 12:59:11 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/656633"
1813147,2019-01-31 21:35:08 UTC,Yeah that's a good point Sean. We have a lot of warnings in the py35 console output logs:
1813147,2019-02-16 18:55:32 UTC,"Reviewed:  https://review.openstack.org/635859
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=102679a1cf80d7a2191acb3ca84c815d4622a3f1
Submitter: Zuul
Branch:    master"
1813147,2019-04-03 14:04:28 UTC,"The issue is back in Glance py37 tests:
https://review.openstack.org/#/c/649395/
https://review.openstack.org/#/c/649596/"
1813147,2019-01-24 10:26:27 UTC,Added the signature to elastic-recheck https://review.openstack.org/632977
1813147,2019-01-24 14:14:38 UTC,I think I first noticed it on this change which merged on Jan 18:
1813147,2019-01-24 14:17:16 UTC,This goes back to at least Jan 14 so it could be something else:
1813147,2019-01-24 14:38:09 UTC,"In about half of the cases the ""Captured Parser Error"" is missing from the logs, but other than that the symptoms are the same. Execution is aborted and the output of the test case triggered the error is truncated."
1813147,2019-01-26 17:35:27 UTC,The
1813147,2019-01-31 22:49:15 UTC,Here is an example of where that SAWarning comes from:
1813147,2019-01-31 22:57:28 UTC,"I opened bug 1814182 against oslo.db in case it's something in the oslo.db code, but it could be a problem in how nova's data models are done, I'm not sure, need help from Mike Bayer."
1813147,2019-02-01 16:33:15 UTC,Reported sqlalchemy-migrate bug 1814288 for the inspect.getargspec warnings generated from that library.
1813147,2019-02-01 16:41:32 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/634450"
1813147,2019-02-01 16:46:47 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/634451"
1813147,2019-02-01 21:25:17 UTC,"Reviewed:  https://review.openstack.org/634450
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1fa2e9c3a0afcbaeecbb9e336a4711c2e9add189
Submitter: Zuul
Branch:    master"
1813147,2019-02-04 23:14:59 UTC,This is probably the next one to squash:
1813147,2019-02-05 13:02:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/634928"
1813147,2019-01-28 13:20:59 UTC,"Cinder hit ""Not a text type application/octet-stream"" pretty consistently after switching to stestr. The trigger for it seemed to be any time a test had a very large amount of stderr output. Trienish and I tried to track down exactly where that was causing an issue, but unfortunately were not able to find what was causing the issue. It seemed to be something with the py3 handling of the output stream."
1813147,2019-02-07 13:44:52 UTC,Looks like this is our biggest issue in the functional py35 job now:
1813147,2019-02-14 13:49:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/636957"
1813147,2019-02-13 16:47:24 UTC,Although if OS_STDERR_CAPTURE=0 then we wouldn't see deprecation warnings in the logs and we want to know those.
1813147,2019-02-13 16:46:25 UTC,We might want to think about defaulting OS_STDERR_CAPTURE to 0.
1813147,2019-02-13 16:30:40 UTC,Another giant traceback in functional test logs:
1813147,2019-02-08 17:36:25 UTC,Reported bug 1815223 against oslo.versionedobjects for that logging in the fixture.
1813147,2019-02-06 16:05:44 UTC,"Reviewed:  https://review.openstack.org/634928
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd1823195fac3d18aa58a45c819e6e97151b0f23
Submitter: Zuul
Branch:    master"
1813147,2019-02-14 21:46:47 UTC,"Reviewed:  https://review.openstack.org/636957
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0840bcccc0ae5700dd5c3d22a3bd6f67d1a8e4bb
Submitter: Zuul
Branch:    master"
1813147,2019-02-08 15:21:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/635859"
1813147,2019-02-08 15:09:54 UTC,That MismatchError in the fake_deserialize_context just gets swallowed and logged in oslo.messaging:
1813147,2019-02-08 14:56:18 UTC,Hit another failure in a unit test job that failed and dumped a ton into the console log:
1813147,2019-02-08 05:41:29 UTC,"Reviewed:  https://review.openstack.org/635516
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c03cc26ee04734b610d13c694cc8b12ad554b4aa
Submitter: Zuul
Branch:    master"
1813147,2019-02-07 14:17:46 UTC,"Reviewed:  https://review.openstack.org/634451
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d916a045c19beb0d058fa04e387bc0c4097d5990
Submitter: Zuul
Branch:    master"
1813147,2019-02-07 14:11:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/635516"
1813147,2019-02-08 17:24:01 UTC,Here is another one:
1813153,2019-03-16 03:43:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813161,2019-11-06 09:43:54 UTC,"sudo rm /usr/share/doc/libmkl-core/changelog.Debian.gz
sudo rm /usr/share/doc/libmkl-meta-interface/changelog.Debian.gz"
1813161,2019-11-06 09:42:06 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813162,2019-01-24 13:42:01 UTC,The lib isn't multiarch ready. Patches welcome
1813162,2019-08-01 17:04:17 UTC,"how could you install both amd64 and i386 if the package is not marked as multi-arch ready?
looks like not a bug to me...
(making it multiarch might be considered a feature request, but for sure this apt error is not something you can have with stuff in the archive and normal apt commands)"
1813162,2019-10-01 04:17:23 UTC,[Expired for llvm-toolchain-7 (Ubuntu) because there has been no activity for 60 days.]
1813165,2020-03-05 17:21:07 UTC,Here is the error:
1813165,2020-03-05 17:22:12 UTC,Here is the CLI error I get:
1813165,2020-03-06 08:33:26 UTC,"If you're seeing ""KVM internal error. Suberror: 1"" it can be multiple things, not necessarily the same bug. Could you please confirm that:
- You are running a nested configuration
- The issue is observed with a UEFI booted guest"
1813165,2020-03-06 13:17:45 UTC,Ok Vitaly I will take a look and report back.
1813165,2020-03-06 16:36:34 UTC,"Nested Configuration check
tstrike39@islandhealthcenter-media:~$ sudo cat /sys/module/kvm_intel/parameters/nested
[sudo] password for tstrike39:
Y"
1813165,2020-03-09 11:25:56 UTC,"'nested' parameter for kvm_intel module controls whether you're able to run nested configurations and it is enabled by default, it doesn't say anything about whether your configuration is nested or not."
1813165,2020-03-10 00:18:24 UTC,"L0 DistroRelease: Ubuntu 20.04  on Kernel Linux 5.4.0-14-generic x86_64
L1 3 guests    Windows 10, Centos 8
No L2s"
1813165,2020-03-10 11:10:39 UTC,Just performed what you asked Vitaly.
1813165,2020-03-15 21:02:31 UTC,I created a new bug request to track the Ubuntu 20.04 package (bug #1867545)
1813165,2020-08-12 12:51:43 UTC,"According to comment #12, the bug underlying this LP ticket was fixed in Linux kernel commit ad7dc69aeb23 (""x86/kvm/mmu: fix switch between root and guest MMUs"", 2019-02-22), released in v5.0."
1813165,2020-03-10 11:51:45 UTC,"Thanks for checking,"
1813165,2020-03-10 12:21:16 UTC,Ok. I will open another bug report. Give me about an hour or so I can regather my logs (plus get my workout in) for a repost.
1813165,2020-03-10 12:38:03 UTC,"Sorry but I'm not at all familiar with bug reporting process in Ubuntu. The ""KVM internal error. Suberror: 1"" issue is definitely not libvirt related (may be induced by the VM configuration created in libvirt but that's it)."
1813165,2020-03-10 08:44:12 UTC,With Win10 you need to make sure it is not running Hyper-V under the hood (e.g. when you enable Hyper-V role Windows will put itself in a VM -- and thus you will get a nested environment).
1813165,2020-03-05 17:17:36 UTC,"Hey folks, I am having the same problem."
1813165,2019-02-11 17:41:31 UTC,Note the error here is on stderr of L1's qemu; there's nothing in dmesg on host or L1 and nothing in the libvirt log.
1813165,2019-02-22 19:35:02 UTC,">>> On 2/22/2019 at 9:50 AM, Vitaly Kuznetsov <email address hidden> wrote:

> I sent a patch which is supposed to fix the issue:
> https://marc.info/?l=kvm&m=155085391830663&w=2
>
> it would be great if someone could give it a spin!
>
"
1813165,2019-02-22 16:50:03 UTC,"I sent a patch which is supposed to fix the issue:
https://marc.info/?l=kvm&m=155085391830663&w=2"
1813165,2019-02-20 19:18:57 UTC,"Thank you David, I see the issue now."
1813165,2019-02-20 18:47:21 UTC,"Right, an L1 line of :
./x86_64-softmmu/qemu-system-x86_64  -M q35,accel=kvm -cpu host"
1813165,2019-02-20 18:31:54 UTC,"Thomas, Albert, David,"
1813165,2019-02-18 09:57:56 UTC,"Ack, thanks for the bisect! It seems something was overlooked when we did host/guest mmu split. I'll try to investigate."
1813165,2019-02-11 20:08:20 UTC,Thanks for the bisect! I've cc'd in Vitaly.
1813165,2019-02-11 19:37:11 UTC,I have bisected the kernel and ended with first bad commit:
1813165,2019-02-11 18:50:06 UTC,"This is related to SMM usage in SeaBIOS. The QEMU register dump states SMM=1, plus ""<0f> aa"" from the dumped code stands for the RSM instruction (0F AA -- RSM—Resume from System Management Mode, see it in the Intel SDM.)"
1813165,2019-02-11 17:38:47 UTC,"Hmm, I've also just hit this in a nest:"
1813165,2019-02-06 14:28:41 UTC,Yes. I was using a 4.20.x kernel. But i guess the bug can be closed because the vm does not exist anymore and the new one does not show this behaviour.
1813165,2019-02-05 14:32:46 UTC,Which kernel are you using on the physical host?
1813165,2019-02-22 20:10:48 UTC,"The patch works fine for me too, many thanks!"
1813167,2019-05-22 18:48:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1830066, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1813170,2019-11-05 04:17:24 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1813170,2019-09-05 09:02:14 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates.
1813170,2019-01-24 14:33:30 UTC,Effect also observed if tab begins playing audio after reader mode is opened.
1813170,2019-01-24 14:37:15 UTC,Observed that effect seems to resolve if audio/video is stopped for a short while (~5 minutes in this case).
1813171,2019-01-24 14:42:14 UTC,"This crash has the same stack trace characteristics as bug #1713581. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package."
1813171,2019-01-24 14:42:16 UTC,"StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x1, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4023
 g_object_ref (_object=0x1) at ../../../../gobject/gobject.c:3212
 g_list_copy_deep (list=list@entry=0x55e7c95b2ac0, func=0x7feb969e6880 <g_object_ref>, user_data=user_data@entry=0x0) at ../../../../glib/glist.c:685
 nautilus_files_view_set_selection (nautilus_files_view=<optimized out>, selection=0x55e7c95b2ac0) at ../src/nautilus-files-view.c:3162
 load_new_location (self=<optimized out>, location=0x55e7c8ce80c0, selection=0x55e7c95b2ac0, file_to_activate=0x0, tell_current_content_view=<optimized out>, tell_new_content_view=<optimized out>) at ../src/nautilus-window-slot.c:2141"
1813171,2020-04-03 14:11:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813173,2019-07-03 16:03:13 UTC,"Hi,
I've been running without the gpaste extension for a few weeks and gnome-shell no longer crashes.
So I guess this bug should be reassigned?"
1813173,2019-01-24 14:45:28 UTC,"StacktraceTop:
 clutter_container_get_child_meta (container=0x0, actor=0x55db499c7480) at clutter-container.c:973
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x55db41f47eb8, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7fff6837ecf8, avalue=avalue@entry=0x7fff6837ebe0) at ../src/x86/ffi64.c:525
 gjs_invoke_c_function (context=context@entry=0x55db41795240, function=function@entry=0x55db41f47ea0, obj=..., obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at gi/function.cpp:1088
 function_call (context=context@entry=0x55db41795240, js_argc=1, vp=0x7fff6837f278) at gi/function.cpp:1406"
1813173,2019-01-25 02:53:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813173,2019-01-25 02:53:45 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/ced4a4eb6e94763756d8b463a6135c31dd711619"
1813173,2019-06-13 06:52:15 UTC,"Hi,
This crash is still present in the latest gnome-shell version 3.28.4-0ubuntu18.04.1"
1813173,2019-06-13 07:07:59 UTC,"It appears this crash is not very common, suggesting it might be related to some extension(s)."
1813173,2019-06-13 07:10:30 UTC,The attached file JournalErrors.txt suggests the GPaste extension might be the most suspicious extension:
1813173,2019-06-13 07:13:37 UTC,"Yes, that does seem to be the problem, most likely. The only calls to 'get_child_meta' in gnome-shell are in environment.js, which seems to be called from the GPaste extension per the above comment."
1813173,2019-09-28 09:05:56 UTC,"Bug #1775971 is for updating gpaste to 3.28.3 in Bionic, which fixes two crashes, one with emptying history and one with image support."
1813182,2019-06-02 17:44:27 UTC,"@Norbert, hi! This actually isn't a sshuttle bug, but a UbuntuMATE bug - shuttle in Ubuntu/Kubuntu works normally - something that UbuntuMATE is bringing up to the table breaks python dependencies and sshuttle doesn't work."
1813183,2019-01-25 03:07:34 UTC,"This might not be specific to this bug, but I did notice that we are calling the external authentication plugin twice, which we probably don't need to do."
1813183,2019-01-25 16:51:02 UTC,"After digging into this, I think I figured out why this is happening."
1813184,2019-02-15 15:13:48 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.3.0 release.
1813184,2019-01-24 16:02:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/633026"
1813188,2020-05-19 08:31:11 UTC,Sorry but both Juno and Liberty are long time ago reached end of life upstream support. Setting the bug to Won't Fix.
1813191,2019-01-28 15:02:01 UTC,Note: Because of some current issues with might_have links in the IDL in web reports the proposed fix (or some equivalent) to bug 1796945 will be required to use this view.
1813191,2019-01-28 15:25:27 UTC,"Here we go:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1813191_dewey_reports / working/user/jboyer/lp1813191_dewey_reports"
1813191,2019-08-21 02:59:37 UTC,"Thanks for this branch, Jason.  It will need some brief release notes.  Also, will the reporter.asset_call_number_dewey view need to be added to the seed data too, not just the upgrade script?"
1813191,2020-08-20 22:20:54 UTC,After far too long I finally return to take care of this. Release note and db build scripts are finally in order in this branch: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1813191_dewey_reports_rebase / working/user/jboyer/lp1813191_dewey_reports_rebase
1813191,2020-09-22 21:34:42 UTC,"Not sure if this is a deal breaker since a library who has LC call numbers probably won't be making use of this source, but it does look like it assigned a Dewey Block to LC call numbers in the Concerto data. All else works as expected."
1813191,2020-09-22 22:03:21 UTC,"The only scenario I can think of where that would be an issue if is a library were using both LC and Dewey in the same catalog for some reason... maybe if two libraries merged? Personally, I would consider that too much of a corner case to prevent this from moving forward, but it's not a hill I would die on one way or the other."
1813191,2020-09-24 18:14:07 UTC,"I agree, Terran."
1813192,2019-01-24 19:50:11 UTC,"From a previous debugging session with DanPB on this dreaded ""cannot
acquire state change lock"" error, it occurs under various situations:"
1813193,2019-09-10 20:52:11 UTC,Agree that customization here would be beneficial.
1813199,2019-01-28 03:51:32 UTC,"GNOME Software doesn't have a field to show this, so this needs some thought as to how it fits into the upstream design."
1813199,2019-01-28 17:16:30 UTC,"The Flathub store for flatpak apps also have that date, so it would make sense to show the 'Last Upload Date' for both, snaps and flatpaks."
1813199,2019-01-31 01:17:54 UTC,"Contact URL was accepted into the AppStream spec:
https://github.com/ximion/appstream/commit/556f01190df1a9158b2532e5ee23a9f2f24ae1f6"
1813199,2019-02-01 01:26:18 UTC,"Oops, that last comment was meant for another bug."
1813201,2021-01-21 18:15:32 UTC,https://git.qemu.org/?p=qemu.git;a=commitdiff;h=3df1a3d070575419859
1813201,2020-11-21 22:48:21 UTC,"This should be fixed by this patch:
https://<email address hidden>/"
1813201,2019-01-30 18:06:12 UTC,"Alberto Ortega writes:

> Public bug reported:
>
> QEMU version:
> -------------
>
> qemu from git, master branch commit
> d058a37a6e8daa8d71a6f2b613eb415b69363755
>
> Release versions are also affected.
>
> Summary:
> --------
>
> QEMU i386 and x86_64 system emulation crash when executing the following
> ""int"" instruction:
>
> cd08  int 8
>
> This generates a kernel NULL pointer dereference error in Linux, and a
> BSOD error in Windows.
>
> No special permissions are required to execute the instruction, any
> unprivileged user can execute it.
> ...
"
1813202,2021-02-07 17:55:31 UTC,"Hello, I've been affected by the same issue.
When I try to overwrite the object with s3api, it creates new segments in bucket+segmens, and cause space usage overhead and orphaned segments."
1813202,2020-09-15 07:15:30 UTC,"We've been also affected by this bug since last year. Are there any update for this case ?
It'll be great if we've a workaround solution to detect and cleanup the orphaned/segments objects."
1813202,2020-05-28 07:54:34 UTC,We're also affected by this bug.
1813202,2019-01-25 03:00:41 UTC,"Thanks, Tim.
We also need to handle cases to clean up parts, when the multipart upload stops mid-way(or fails due to some error) or remains pending (no complete called) for some time interval. Something like slo-parts-expirer is needed to scan +segments bucket and delete parts which do not have a valid manifest file."
1813202,2019-01-28 09:06:13 UTC,Another case to consider is managing large objects(with multi-part enabled) in versioning enabled buckets.
1813203,2019-01-24 21:47:34 UTC,Please contact vlc maintainers. This is not a ubuntu mate specific problem.
1813203,2019-01-25 21:56:20 UTC,Yes it is :
1813203,2019-05-28 21:14:38 UTC,"Yep this does appears to be related to mate's marco window manager, I opened an issue about this over there before finding this thread:"
1813206,2019-01-24 20:45:46 UTC,Yeah. Fix is there: https://github.com/kassoulet/soundconverter/commit/f75f9fe752dfd90f9ad0f191f8bd8fe550f92b80
1813210,2019-05-28 20:49:43 UTC,"Change abandoned by Jay Rubenstein (<email address hidden>) on branch: master
Review: https://review.opendev.org/656778
Reason: DuplicateSfVolumeNames exception is caused by using sf_allow_template_caching in an HA A/A environment.  Cinder driver has the same ability to cache image volumes and manage them through cinder.conf.   sf_allow_template_caching  will be removed in some future release.   Any one  experiencing this error should switch to cinder's version of image-caching"
1813210,2019-01-30 22:29:59 UTC,"inder server |  t1 | t2 | t3 | t4 | t5 | t6 | t7
-------------|----------------|---------------|------------|-----------|---------|---------|------------
cs1| _create_image_volume | get image from glance| _do_volume_create| copy image to vol|  x-time| _get_sf_volume| throw exception
cs2|time-diff|_create_image_volume| get image from glance|_do_volume_create|copy_image to vol|_get_sf_volume|throw exception
change|_create_image_volume|get image from glance|_do_volume_create|_get_sf_volume|catch exception, delete-wait-return or continue| cont-copy image to vol|_get_sf_volume"
1813210,2019-03-27 20:08:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648228"
1813210,2019-05-02 13:54:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656778"
1813210,2019-05-28 20:48:59 UTC,"Change abandoned by Jay Rubenstein (<email address hidden>) on branch: master
Review: https://review.opendev.org/648228
Reason: DuplicateSfVolumeNames exception is caused by using sf_allow_template_caching in an HA A/A environment.  Cinder driver has the same ability to cache image volumes and manage them through cinder.conf.   sf_allow_template_caching  will be removed in some future release.   Any one  experiencing this error should switch to cinder's version of image-caching"
1813213,2019-02-01 22:24:14 UTC,"Reviewed:  https://review.openstack.org/633839
Committed: https://git.openstack.org/cgit/openstack/ovsdbapp/commit/?id=923abc1bf016f80e7595b481456d46d5c22b2af3
Submitter: Zuul
Branch:    stable/queens"
1813213,2019-02-06 21:59:47 UTC,This issue was fixed in the openstack/ovsdbapp 0.10.3 release.
1813213,2019-02-06 22:08:08 UTC,This issue was fixed in the openstack/ovsdbapp 0.12.3 release.
1813213,2019-01-31 11:11:41 UTC,"Reviewed:  https://review.openstack.org/633838
Committed: https://git.openstack.org/cgit/openstack/ovsdbapp/commit/?id=210be9fb1aafa85026e8c62f2a2bda2a97d00acb
Submitter: Zuul
Branch:    stable/queens"
1813213,2020-01-23 13:37:51 UTC,"Apparently the issue has been fixed, marking it as such but pelase re-open if that's not the case."
1813213,2019-01-31 02:56:35 UTC,"Reviewed:  https://review.openstack.org/633772
Committed: https://git.openstack.org/cgit/openstack/ovsdbapp/commit/?id=62f02f40d9fea533a9a6bb56246530274aabe0a4
Submitter: Zuul
Branch:    stable/rocky"
1813213,2019-01-31 03:03:22 UTC,"Reviewed:  https://review.openstack.org/633837
Committed: https://git.openstack.org/cgit/openstack/ovsdbapp/commit/?id=547777a9cfc6fd0be667bae17ab503b49b705116
Submitter: Zuul
Branch:    stable/rocky"
1813213,2019-01-30 13:34:07 UTC,"Change abandoned by Terry Wilson (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/633772
Reason: Having trouble adding dependent patch, trying again"
1813213,2019-01-29 22:14:57 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/633838"
1813213,2019-01-29 21:26:16 UTC,This issue was fixed in the openstack/ovsdbapp 0.15.0 release.
1813213,2019-01-29 16:06:05 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/633772"
1813213,2019-01-25 16:07:06 UTC,"Reviewed:  https://review.openstack.org/633070
Committed: https://git.openstack.org/cgit/openstack/ovsdbapp/commit/?id=692653f49fb32391b04b117290137ace912ef891
Submitter: Zuul
Branch:    master"
1813213,2019-01-30 13:38:36 UTC,"Change abandoned by Terry Wilson (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/633772"
1813215,2019-01-24 21:52:55 UTC,Looks like this is in all multinode grenade jobs and has been happening since before Jan 21:
1813216,2019-07-10 21:40:07 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1813216,2019-04-22 23:18:38 UTC,"Reviewed:  https://review.opendev.org/640197
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5d5e7be8cbb6d37b20c7efcac7850562d3281904
Submitter: Zuul
Branch:    stable/queens"
1813216,2019-04-18 16:35:48 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/653811"
1813216,2019-03-24 23:39:23 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1813216,2019-03-22 03:44:16 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1813216,2019-03-04 13:20:38 UTC,"Reviewed:  https://review.openstack.org/640186
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c4a2a32f07cbe139b5889654bbc82d3ddeaeeb94
Submitter: Zuul
Branch:    stable/rocky"
1813216,2019-02-28 21:41:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/640197"
1813216,2019-04-22 12:57:04 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/653811
Reason: https://review.opendev.org/#/c/640207/ is working."
1813216,2019-02-12 23:08:58 UTC,"Reviewed:  https://review.openstack.org/634962
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2db43d57ae980d8cdf08de4f5e6290d7edcc95c
Submitter: Zuul
Branch:    master"
1813216,2019-02-05 16:04:11 UTC,Here is a stable/queens job run from Jan 2 and nova.conf is being used in the nova-compute service as well:
1813216,2019-02-05 15:50:31 UTC,"Looking at the job in pike, nova-compute would run with nova.conf rather than nova-cpu.conf:"
1813216,2019-02-05 15:44:26 UTC,"I also noticed the job is failing on stable branches which implies the regression could be due to a change to a branchless project, like tempest/openstack-zuul-jobs/devstack-gate but I don't see anything immediately obvious there. It could also be that we backported something in devstack that messed up the job."
1813216,2019-02-05 15:42:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634962"
1813216,2019-02-05 15:19:34 UTC,One thing I noticed is that the script that sets up the grenade + live migration environment is trying to use nova.conf rather than nova-cpu.conf here:
1813216,2019-02-28 20:44:42 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640186"
1813217,2019-04-11 16:27:06 UTC,This is likely a duplicate of bug 1483434.
1813222,2019-01-24 23:54:54 UTC,proposed fix: https://gitlab.com/yade-dev/trunk/commits/fix/crash_intrAllWire
1813222,2019-02-05 19:46:40 UTC,moved form https://bugs.launchpad.net/yade/+bug/1813222 to https://gitlab.com/yade-dev/trunk/issues/48
1813223,2019-06-18 12:29:14 UTC,I think you instance did not reached the active power state before you hit rebuild.
1813225,2019-07-31 19:25:23 UTC,"This works well for me too; thanks Terran, Garry, and Michele.  I added a brief release note entry and pushed to master -- it'll be available in 3.4."
1813225,2019-05-22 19:17:25 UTC,Tested and works perfectly.  Signedoff branch at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1813255_link_billing_location_to_library_info-signoff
1813225,2019-03-07 15:42:39 UTC,"LOL - sorry and thank you, Michele!"
1813225,2019-03-07 15:27:32 UTC,Looks like the link to Terran's working branch didn't make it into a comment. This appears to be it:
1813227,2019-01-25 06:34:06 UTC,"Hi,
I'm not sure what exactly will be needed, but the following would surely help.
Do you have a way to fetch the following while at the error condition and attach it here?:
- sudo multipath -ll
- lsblk"
1813227,2019-01-29 02:41:14 UTC,The MAAS ephemeral environment does not have the multipath kernel module nor multipath-tools. To get this log I had to install both.
1813227,2019-02-22 09:26:37 UTC,"Hi Lee,
thanks for the logs - once multipath is installed the devices are multipath mapped.
But obviously at the time pvscan failed they were not."
1813227,2019-02-22 09:33:09 UTC,"I saw [1] by xnox popping up, so he might work on this already. I have pinged him to clarify."
1813227,2019-02-22 09:38:03 UTC,"If the change by xnox fixes your case then the resolution is to ship multipath on those images.
@Lee - waiting for your answer if the services (and thereby the pvscan) works after multipath is installed."
1813227,2019-02-22 09:38:28 UTC,I also pinged jfh to make it part of the s390x related tracking
1813227,2019-04-05 00:28:46 UTC,I tested a Disco image today with multipath-tools installed and I still get the same thing.
1813228,2019-04-27 03:00:37 UTC,"/sys/class/block/sdcy/sdcy1 actually doesn't exist, although this is in rescue mode and not directly after the failed deployment."
1813228,2019-04-26 18:29:49 UTC,"If you're on the box now, if you could run:"
1813228,2019-04-27 00:17:21 UTC,"root@maas-node-3:~# ls -alh /dev/mapper
total 0
drwxr-xr-x  2 root root    2.1K Apr 27 00:07 .
drwxr-xr-x 20 root root     17K Apr 27 00:07 ..
lrwxrwxrwx  1 root root       8 Apr 27 00:10 Z_APPL_ROOT_lvm_382F5B8E-root_pool -> ../dm-94
lrwxrwxrwx  1 root root       8 Apr 27 00:10 Z_APPL_ROOT_lvm_473D86E3-root_pool -> ../dm-95
lrwxrwxrwx  1 root root       8 Apr 27 00:10 Z_APPL_ROOT_lvm_BBD0E8D4-root_pool -> ../dm-96
crw-------  1 root root 10, 236 Apr 27 00:10 control
lrwxrwxrwx  1 root root       7 Apr 27 00:10 mpatha -> ../dm-0
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpatha-part1 -> ../dm-58
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpatha-part2 -> ../dm-59
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpatha-part5 -> ../dm-60
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathaa -> ../dm-26
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathab -> ../dm-27
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathac -> ../dm-28
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathad -> ../dm-29
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathae -> ../dm-30
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathaf -> ../dm-31
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathag -> ../dm-32
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathah -> ../dm-33
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathai -> ../dm-34
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathaj -> ../dm-35
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathak -> ../dm-36
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathal -> ../dm-37
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpatham -> ../dm-38
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathan -> ../dm-39
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathao -> ../dm-40
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathap -> ../dm-41
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathaq -> ../dm-42
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathar -> ../dm-43
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathas -> ../dm-44
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathat -> ../dm-45
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathat-part1 -> ../dm-86
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathau -> ../dm-46
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathau-part1 -> ../dm-87
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathav -> ../dm-47
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathav-part1 -> ../dm-88
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathaw -> ../dm-48
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathax -> ../dm-49
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathay -> ../dm-50
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathay-part1 -> ../dm-89
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathaz -> ../dm-51
lrwxrwxrwx  1 root root       7 Apr 27 00:10 mpathb -> ../dm-1
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathb-part1 -> ../dm-54
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathb-part2 -> ../dm-55
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathba -> ../dm-52
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathba-part1 -> ../dm-90
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathba-part2 -> ../dm-91
lrwxrwxrwx  1 root root       8 Apr 27 00:10 mpathbb -> ../dm-53
lrwxrw..."
1813228,2019-04-27 02:16:24 UTC,"# udevadm info --query=all /sys/class/block/sdcy1
Unknown device ""/sys/class/block/sdcy1"": No such device"
1813228,2019-04-29 14:12:14 UTC,"Ok, I think we did the right thing, but as I said, need to wait for the
symlink/node to be removed after the dmsetup remove."
1813228,2019-04-26 18:13:56 UTC,Curtin is still failing to deploy
1813228,2019-05-16 19:14:00 UTC,"This bug is fixed with commit 6e82b6f7 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=6e82b6f7"
1813228,2019-05-22 14:21:49 UTC,"This bug is believed to be fixed in curtin in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1813228,2019-04-23 16:18:40 UTC,Thanks.
1813228,2019-04-22 18:58:48 UTC,Thanks for the logs.  Looks like we'll need some work on clear-holders to deal with these sorts of devices.
1813228,2019-05-03 21:20:09 UTC,"OK, with much debugging, I'm going to push the latest bits to address the multipath issue; but this isn't all that's needed and we need some discussion to move forward."
1813228,2019-04-22 18:43:50 UTC,Curtin still fails to install with the attached branch
1813228,2019-04-23 01:06:27 UTC,Attached is the output from probert on the system Curtin is failing on.
1813228,2019-04-05 19:41:59 UTC,"I xz compressed the logs this time since the uncompress tar was a bit bigger than before. The tar itself works fine, xz is very efficient :)"
1813228,2019-04-05 20:07:26 UTC,"Sorry, I see.  The archive opener didn't notice it."
1813228,2019-01-29 02:34:33 UTC,Just to clarify while the system is using multipath the MAAS ephemeral environment does not have the multipath kernel module nor the multipath userland tools.
1813228,2019-01-29 17:18:18 UTC,That's fair; it's the duplicate paths which have the same LVM_UUID on them; so we'll see this with or without multipath daemon/module any how.
1813228,2019-02-22 09:25:03 UTC,"I think we'd like have the commissioning stage ensure that multipath-tools is installed such that multipathd will have scanned and assembled any paths, this will result in persistent storage paths to the devices, and will allow maas to reference a particular lun via the serial of the lun and path.  For example:"
1813228,2019-02-22 10:00:28 UTC,"FYI - xnox just added multipath-tools to the seed so sooner or later this will be avilable already.
Never the less ensuring it gets installed (we can apt-get there right?) especially for older images seems to be the right way."
1813228,2019-01-28 19:04:33 UTC,"Curtin generally expects vgchange -ay to exit with 0, non-zero exit indicates as failure."
1813228,2019-04-05 04:27:56 UTC,Adding multipath changes the error message but Curtin still fails.
1813228,2019-04-05 12:32:56 UTC,Can you enable curtin verbose?
1813228,2019-04-05 18:31:21 UTC,Curtin logs with verbose enabled.
1813228,2019-02-27 22:26:51 UTC,"On Fri, Feb 22, 2019 at 4:05 AM Christian Ehrhardt  <
<email address hidden>> wrote:"
1813228,2019-04-05 19:21:00 UTC,The curtin-logs.tar.xz appears invalid (only 12.5kb vs. 140kb previously).
1813229,2019-01-26 22:34:13 UTC,Proposed fix: https://gitlab.com/yade-dev/trunk/merge_requests/34
1813229,2019-01-26 23:34:48 UTC,"Same proposed fix, but this time with"
1813229,2019-01-30 18:49:32 UTC,It is fixed now: https://gitlab.com/yade-dev/trunk/commit/0d2d11a2eaaa2bcc2e253744914f80cdfaf7fee6
1813235,2020-02-04 11:58:39 UTC,Thanks for reporting this.
1813235,2020-04-05 04:17:29 UTC,[Expired for Snapcraft because there has been no activity for 60 days.]
1813238,2019-01-25 05:08:51 UTC,"As far as Mnemosyne's development is concerned, as mentioned before, please report bugs against the latest released version, 2.6.1 currently. 2.4 is really ancient, and Ubuntu should update its version."
1813238,2019-01-25 07:58:49 UTC,"Ubuntu disco 19.04 does have 2.6.1, but that doesn't change the fact that the LTS version of ubuntu has 2.4.  It's not likely to be updated, outside of patches to fix issues as they come up (like this)."
1813238,2019-01-25 08:47:48 UTC,I don't think it makes a lot of sense to keep these old bug reports around then. Backporting fixes to 2.4 is certainly not something I intend to spend my time on :-)
1813238,2019-01-25 19:47:52 UTC,"That's fine, there's plenty of python developers out there who could
do it.   The maintainer listed is"
1813239,2019-04-21 22:42:42 UTC,Its correct aside from nobody mentioning it must remain locked into any constraint which the user puts any entities into. A small glyph which appears only when mouse hover over depicts which constraints the entities are subject to and clicking the glyphs and hitting delete is the method to remove any constraint from the entities. The glyphs should be hidden to prevent obstructions as there may be many constraints for an object.
1813239,2019-04-21 22:43:22 UTC,The entities are drawn objects such as lines circles or other such objects.
1813239,2019-03-08 07:49:45 UTC,This bug is very much inline with bug https://bugs.launchpad.net/kicad/+bug/1812204 they should both be on the RC roadmap.
1813239,2019-01-25 04:02:49 UTC,This isnt a duplicate since its a separate feature request but in the same category.
1813239,2019-04-20 12:21:29 UTC,"@zakhar, it sounds to me like you are requesting CAD object snapping capability.  If this is incorrect, please clarify your request."
1813244,2019-04-08 07:58:23 UTC,@arighi - will this fix go into disco soon? I have an OVS upload for a high fix blocked on failing tests on i386 - just need to know whether to update the hinter or wait for the fix.
1813244,2019-04-08 08:20:55 UTC,"@james-page, the fix has been sent to the Ubuntu kernel mailing list [1], so it's scheduled for the next SRU cycle (assuming it gets two ACKs)."
1813244,2019-04-08 08:38:08 UTC,@juergh ok I'll propose a hint for disco them!
1813244,2019-04-09 06:04:04 UTC,The referenced patch fixes an earlier commit [1] that was added in the 3.11 time frame so Trusty needs this too.
1813244,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1813244,2019-04-25 22:32:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1813244,2019-04-29 10:24:16 UTC,Verification done using the test case reported in the description (https://launchpadlibrarian.net/416589265/lp1262692)
1813244,2019-04-29 16:03:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813244,2019-05-02 08:26:01 UTC,Verification done in bionic using the test case reported in the description (https://launchpadlibrarian.net/416589265/lp1262692)
1813244,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1813244,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1813244,2019-05-14 19:08:52 UTC,This bug was fixed in the package linux - 4.4.0-148.174
1813244,2019-05-14 22:54:00 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813244,2019-04-26 14:31:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1813244,2019-04-05 07:40:50 UTC,Fix has been merged upstream.
1813244,2019-03-21 16:29:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813244,2019-03-27 22:19:02 UTC,"With this patch applied I can't reproduce the problem anymore.
See also: https://lkml.org/lkml/2019/3/27/1762"
1813244,2019-01-25 05:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813244,2019-01-25 05:14:55 UTC,apport information
1813244,2019-03-28 06:39:23 UTC,New patch after the review from the LKML.
1813244,2019-01-25 05:14:59 UTC,apport information
1813244,2019-01-25 05:15:00 UTC,apport information
1813244,2019-01-25 05:15:02 UTC,apport information
1813244,2019-01-25 05:15:04 UTC,apport information
1813244,2019-01-25 05:14:56 UTC,apport information
1813244,2019-01-25 05:15:08 UTC,apport information
1813244,2019-01-25 05:15:10 UTC,apport information
1813244,2019-01-25 05:15:11 UTC,apport information
1813244,2019-01-25 09:28:21 UTC,"Tried to reproduce this with:
  1. NTP time sync set to false
  2. Change the time to 23:57:00
  3. Run the ubuntu_cts_kernel test and wait for the logrotate to kick in"
1813244,2019-01-25 11:34:24 UTC,This issue was successfully reproduced with the Cosmic kernel in -updates. Not 100% reproducible but this is what I did:
1813244,2019-03-21 16:10:35 UTC,"I have also been able to reproduce this bug with 4.18.0-10, 4.18.0-13, 4.18.0-14 and 4.18.0-16. So it doesn't seem to be a regression."
1813244,2019-03-26 17:05:11 UTC,"I did more tests with this, it looks like the problem is hidden somewhere in openvswitch. The specific test case that seems to trigger the bug 100% of the time is the one attached, but it requires to change the time immediately before running it (for example using date --set ""23:57:00"", as suggested before)."
1813244,2019-01-25 05:15:06 UTC,apport information
1813248,2019-09-16 18:48:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813248,2019-02-04 08:44:25 UTC,"Since removing
- gnome-shell-extension-multi-monitors
- gnome-shell-extension-system-monitor
The issue is no more triggering."
1813248,2019-01-25 08:03:40 UTC,"Hi Daniel, thanks for taking a look."
1813248,2019-01-25 06:46:12 UTC,Unassigning gdm3 since it is unchanged since October.
1813248,2019-01-25 06:45:28 UTC,There'a a lot of log data in comment #4 and a few possible problems:
1813248,2019-01-25 06:51:16 UTC,Given the CPU started to overheat you might want to log in remotely via SSH from another machine and leave 'top' running. Then next time the problem occurs tell us what is using all the CPU according to 'top'.
1813249,2019-01-27 20:12:51 UTC,"SOLVENT
Debian Stretch / Mate
# apt-get remove --purge evolution
# apt-get install gconf-editor
TERMINAL-MATE
gconf-editor
--------desktop
-------------gnome
-------------------url-handles
-------------------------------mailto
-------------------------------------command   ====> thunderbird %"
1813251,2019-10-15 02:14:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813251,2019-10-16 11:42:19 UTC,This likely has something to do with the issue:
1813251,2019-12-16 04:17:33 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1813255,2020-05-26 08:58:17 UTC,Please provide a reproduction steps for the bug or a functional test the reproduce the bug as Matt requested it in the code review https://review.opendev.org/633160 .
1813255,2019-01-25 08:37:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633160"
1813255,2019-01-28 05:00:22 UTC,">Yea, this is really strange. @DongCan, What is your Env looks like,
>like all-in-one one node setup, or you have multiple node?Each building request only can be >accepted by one compute node, I
>don't understand why there is conflict happened.
"
1813255,2020-05-26 08:56:09 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/633160
Reason: This is an old patch with negative review. So I'm abandoning it. If you would like to continue working on it then please answer the question from Matt."
1813262,2019-01-25 09:28:29 UTC,"Thank you for your bug report, that's because those strings are new and there was no langpack update to include the translations since they have been added"
1813262,2019-01-25 09:31:49 UTC,"Those strings also seem not translated in Dutch at the moment
https://translations.launchpad.net/ubuntu/bionic/+source/update-manager/+pots/update-manager/nl/8/+translate
https://translations.launchpad.net/ubuntu/bionic/+source/update-manager/+pots/update-manager/nl/9/+translate"
1813262,2020-03-26 13:40:52 UTC,"Fixed on 20.04 daily
Thank you!"
1813263,2020-05-27 15:12:23 UTC,"I have in mind that if loadbalancer-topology is set to !SINGLE, then set enable_anti_affinity=true and anti_affinity_policy=soft-anti-affinity , although adding a config option so the operator is able to opt-in to anti-affinity in case their needs are of having a strict spread of the loadbalancers at the cost of failures from time to time."
1813263,2020-09-12 19:25:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/751583"
1813265,2019-01-25 19:51:54 UTC,Marking this as low-hanging-fruit because the documentation process can be a good learning experience.
1813266,2019-02-18 13:49:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813266,2020-01-31 10:56:01 UTC,"This has been open for over a year, with a fix indicated from the very beginning. Is there any chance that patch can be applied?"
1813266,2020-02-09 01:22:01 UTC,"Anyway to raise the priority on this?, almost two years since the bug was fixed in busybox but ubuntu has not picked the patch. I had to update the service stop script to do a pkill -9 udhcpd but that is not ideal."
1813268,2019-01-25 13:33:28 UTC,"Thanks, setting as fix commited but technically it's fixed in disco and a request for a SRU, it would be a good idea to udpate to the current 3.30 version in cosmic indeed"
1813268,2019-02-14 09:43:57 UTC,The fix is in the current disco version and being SRUed to 18.10
1813268,2019-02-21 14:18:18 UTC,"Hello bjo, or anyone else affected,"
1813268,2019-05-23 19:29:09 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1813268,2019-05-24 08:09:25 UTC,"I'm on disco now, but I will set up a VM and test it."
1813268,2019-05-27 11:56:58 UTC,"Tested with 3.30.5 from cosmic-proposed, bug is gone."
1813268,2019-05-30 08:33:37 UTC,This bug was fixed in the package evolution-data-server - 3.30.5-0ubuntu0.18.10.1
1813268,2019-05-30 08:33:48 UTC,"The verification of the Stable Release Update for evolution-data-server has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813277,2019-09-16 13:11:42 UTC,Fix released as per comment #3
1813277,2019-01-25 17:42:42 UTC,"Ack, thanks for the reports. I'll fix up the qrt check for this."
1813277,2019-01-26 01:11:20 UTC,This should now be fixed in qrt with commit https://git.launchpad.net/qa-regression-testing/commit/?id=93b87455c0297ac63548b3c1450308dabfa4bfbf
1813277,2019-01-25 11:01:39 UTC,Could be seen on ARM64 in regression-testing as well (for P8 the system deployment is blocked with bug 1812629)
1813288,2020-03-12 04:08:34 UTC,"Confirmed, in apache_input(apache) addr = rel['private-address'] (the relation private-address) and that could be switched to localhost, if we're sure that we don't want to have telegraf monitor non-local Apache instances.  If we do, then we need to fix the vhost template which has 127.0.0.1 hardcoded in."
1813288,2020-05-06 04:59:24 UTC,"Also, we'll want a 'Listen 127.0.0.1:8080' in ports.conf."
1813291,2019-01-31 22:56:03 UTC,Junien
1813291,2019-02-01 13:34:45 UTC,I wonder if a relation is needed between nova-cloud-controller and memcached to recreate. That was needed to recreate the other bug for LP#1812672.
1813291,2019-02-01 13:35:32 UTC,Bug 1812672
1813292,2019-01-25 13:22:25 UTC,I do not reproduce this for the SM:
1813292,2019-01-25 13:25:54 UTC,I see the same for the MSSM model...
1813292,2019-01-30 15:34:59 UTC,"Thank you for having looked into this.
Yes, I checked again and, at least in 3.x what I get is a warning, not a crash (sorry for the confusion), so yes this would be the undesired behaviour I am reporting."
1813292,2019-02-04 22:07:01 UTC,"Hi,"
1813293,2019-02-02 21:37:59 UTC,"In Linux Mint 19.1, I get the error"
1813293,2019-01-25 13:22:35 UTC,no special added comment
1813293,2019-02-01 13:23:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813296,2020-03-11 21:44:25 UTC,"Although it would be great to check the response from Horizon, it sounds like this was caused by a poorly tested update release rather than the sort of thing monitoring is intended to pick up.  Given that the css for Horizon is customized per cloud with custom themes, confirming the result is 'good' is even more unlikely to be realistic."
1813297,2019-07-21 04:17:33 UTC,[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]
1813297,2019-05-21 18:56:29 UTC,I tried to reproduce this with DevStack master (for Train release development).
1813304,2019-01-29 02:12:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1813304,2019-01-29 17:01:20 UTC,apport information
1813304,2019-01-29 17:01:21 UTC,apport information
1813304,2019-01-29 17:01:23 UTC,apport information
1813304,2019-01-30 01:52:57 UTC,"Sounds like it might be related to bug 1725676 or bug 1652618, or bug 1566357."
1813304,2019-01-30 12:57:19 UTC,"bug 1725676 is about not being able to select a different keyboard layout while this is about being able to select a different layout, but it not actually working.  It's unrelated."
1813308,2019-10-31 03:44:31 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1813311,2019-07-15 13:30:55 UTC,Setting back to new - this was pending information that has now been provided - bug still needs to be reproduced.
1813311,2019-11-01 12:27:24 UTC,single-nova-consoleauth has been dropped from the charm in commit: b6e314077fa352ba58c346919a1e1cd4f6593226 (gerrit I2ac91b2bd92269b761befeb7563ad01cc5431151):
1813311,2019-07-14 04:17:40 UTC,[Expired for OpenStack nova-cloud-controller charm because there has been no activity for 60 days.]
1813311,2019-05-14 14:20:41 UTC,This is the current bundle of the installation with some sanitized data (IPs and domains)
1813311,2019-05-14 13:54:47 UTC,"@soumplis: would you please post the bundle? We'll try to reproduce with the simplest possible setup of nova-cloud-controller and hacluster, but the original bundle would be useful, just in case that doesn't reproduce the issue."
1813311,2019-07-15 12:44:55 UTC,Is this resolved somehow ? Have you been able to reproduce ?
1813314,2019-07-22 04:43:52 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1813319,2019-07-26 12:11:09 UTC,"Hey, just checking in on the new release? :)"
1813319,2019-08-06 20:20:29 UTC,Also checking on progress. Is it possible to make a new release?
1813319,2019-06-13 14:06:51 UTC,friendly ping :)
1813319,2019-06-01 11:51:39 UTC,It looks like the necessary code merged.. could we possibly have a new release?
1813319,2019-07-16 14:01:05 UTC,"hey.. checking in on the progress, is it possible to make a new release with these changes?"
1813319,2019-02-04 17:08:09 UTC,This should have automatically been changed to confirm with the three affected but I'll change it now.
1813323,2019-05-31 13:17:58 UTC,"Thank you for using ufw and filing a bug. It is true that there is only the one explicit input rule, ufw be default allows all outgoing. From the man page:"
1813323,2019-06-06 12:10:40 UTC,"Hi Jamie,"
1813323,2019-06-06 20:30:28 UTC,"""Hence, when the UFW protected host is a DHCPv6 server, this rule is needed to let that initial solicit pass:"
1813323,2019-06-06 21:07:02 UTC,"On second thought I agree. The extra line I proposed should not be added by default, for the reasons you explained."
1813325,2019-05-29 15:38:20 UTC,"Change abandoned by Steven Webster (<email address hidden>) on branch: master
Review: https://review.opendev.org/658222
Reason: New review: https://review.opendev.org/#/c/661987/"
1813325,2019-06-03 19:18:26 UTC,"TC is passed on WCP_61-62
BUILD_ID=""20190602T233000Z""
JOB=""STX_build_master_master"""
1813325,2019-05-30 18:26:02 UTC,"Reviewed:  https://review.opendev.org/661987
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=9a1ddaa291493226a3e282781c4409665c849161
Submitter: Zuul
Branch:    master"
1813325,2019-05-09 22:14:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658222"
1813325,2019-05-07 17:49:19 UTC,This issue is causing failures in Nightly regression on continuous basis. There are also 35+ test cases failing due to this defect in Nova automated regression. Increasing the priority to P2 and requesting for an early fix.
1813325,2019-01-25 19:42:06 UTC,"Assigning to Steve to triage and determine if this is related to:
https://storyboard.openstack.org/#!/story/2004472"
1813325,2019-05-29 13:49:43 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661987"
1813325,2019-01-28 18:28:02 UTC,Marking as release gating - a semantic check is needed to cover this scenario as a result of the recent story
1813325,2019-04-05 16:18:07 UTC,"Related to this, but perhaps not the exact same bug:
The memory accounting overheads for NOVA is not yet configured (i.e. for 4K platform reserved overhead, and vswitch hugepages overhead), so there is a discrepancy in knowing what the actual available memory.  The end result is that nova's reported available memory is overstated."
1813328,2019-04-13 17:23:23 UTC,Still the case in nightly. We experience this quite often on high-voltage boards.
1813328,2019-05-01 12:34:42 UTC,@Michael thanks for flagging. I have cherry-picked and committed the patch on 5.1.
1813328,2019-04-29 15:38:19 UTC,"Hi Tom,"
1813328,2019-05-01 10:09:58 UTC,Was this ever cherry-picked onto the 5.1 branch? I cant seem to find it.
1813328,2019-04-20 18:57:13 UTC,"@Bob, sorry about the versioning confusion.  Version 6 will is the next major stable release and is currently under heavy development.  The current stable release is 5.1.0 which derived from a separate 5.1 branch.  5.1.1 is almost ready and will be released any day."
1813328,2019-04-20 16:28:40 UTC,Thank you Aleksandr
1813328,2019-04-20 16:08:12 UTC,"I'm not Wayne, but the bug is not fixed yet, only ""Confirmed"", but supposed to be fixed in version 5.1.2."
1813328,2019-04-20 15:48:05 UTC,"Hi, Wayne"
1813328,2019-04-21 00:28:03 UTC,"Yes thanks a lot, Wayne."
1813328,2019-04-30 14:34:35 UTC,"Fixed in revision 9e00f48efc2eb70a884a7f0a6620bf519021513b
https://git.launchpad.net/kicad/patch/?id=9e00f48efc2eb70a884a7f0a6620bf519021513b"
1813333,2019-01-25 20:22:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1813335,2019-07-09 23:56:39 UTC,"I think the doc is wrong. We should never recommend external auth be used with X.509 certificate based authentication. X.509 certificate based auth should always us the federation mechanism. External is based on a single attribute, REMOTE_USER, which is very limited."
1813335,2019-07-10 01:21:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669959"
1813336,2019-07-10 00:32:19 UTC,I think this is an invalid use case. X.509 certificate based authentication is not meant to be used with external auth. It is designed to be a federation protocol and hence using the federation workflow.
1813336,2019-07-10 00:32:51 UTC,"If documentation is unclear about that, we should update the doc instead."
1813336,2019-08-08 17:39:01 UTC,I think this is more about tokenless authentication than about external vs mapped X.509 authentication. We allow setting scope with tokenless auth:
1813339,2019-12-17 19:02:20 UTC,"The path to vivaldi indicates that the application you are trying to launch is not in the Ubuntu repositories. To accommodate this sort of thing, apparmor profiles in Ubuntu ship files in /etc/apparmor.d/local for admins to modify. I suggest adding this to /etc/apparmor.d/local/usr.bin.evince:"
1813339,2019-12-18 09:56:36 UTC,"Thank you for the reply! The evince (3.28.4-0ubuntu1.2) update done the trick.
So your suggested fix isn't needed anymore in this constellation."
1813339,2020-05-07 17:16:15 UTC,"That is a very suboptimal solution. for the average user, it just does not work."
1813349,2019-01-25 18:20:25 UTC,"I forgot to mention that the bug also occurs for a newly created user account, so I assume it is not directly related to configuration file changes I might have made."
1813351,2019-01-25 21:22:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633281"
1813351,2019-03-19 13:26:40 UTC,Is this still being worked on?
1813351,2020-09-18 16:50:24 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.opendev.org/633281
Reason: https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1813354,2019-02-28 16:55:10 UTC,"I don't remember for sure which article it was, but I was travelling at the time and looking to auto-select the fastest mirrors. Searching now finds a familiar-looking article and forum answer:"
1813354,2019-02-28 17:30:36 UTC,"Most appear in places like Ask Ubuntu (and other Stack Exchange sites). I had not seen ""official"" information but I searched and found a blueprint:"
1813354,2019-01-26 08:03:53 UTC,I did right after posting the bug and it worked just fine. Possibly something to fix for an upcoming release?
1813354,2019-01-25 20:46:33 UTC,"I don't think the release upgrader understands the ""deb mirror"" lines in your sources.list file. Please replace those with an official Ubuntu mirror and try the upgrade again."
1813354,2019-02-28 16:26:13 UTC,"I'm not questioning the fact that this is a bug but I'm curious what documentation lead you to add ""deb mirror"" entries to your sources.list file. Could you point me at it?  Thanks in advance."
1813357,2019-01-27 08:24:50 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc3 kernel[0]."
1813357,2019-01-26 04:02:16 UTC,apport information
1813357,2019-01-26 04:02:13 UTC,apport information
1813357,2019-01-26 04:02:10 UTC,apport information
1813357,2019-01-26 04:02:08 UTC,apport information
1813357,2019-01-26 04:02:05 UTC,apport information
1813357,2019-01-26 04:02:03 UTC,apport information
1813357,2019-01-26 04:02:07 UTC,apport information
1813357,2019-01-26 04:02:01 UTC,apport information
1813357,2019-01-25 23:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813357,2019-01-26 04:01:51 UTC,apport information
1813357,2019-01-26 04:01:53 UTC,apport information
1813357,2019-01-26 04:02:02 UTC,apport information
1813357,2019-01-26 04:01:57 UTC,apport information
1813357,2019-01-26 04:01:59 UTC,apport information
1813357,2019-01-26 04:01:55 UTC,apport information
1813357,2019-01-26 04:01:58 UTC,apport information
1813362,2019-06-07 08:37:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813363,2019-01-25 21:30:49 UTC,"Note, whatever it was that caused bind to die didn't affect a restart:
bladernr@weavile:~$ sudo service bind9 restart
bladernr@weavile:~$ sudo service bind9 status
● bind9.service - BIND Domain Name Server
   Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-01-25 16:23:09 EST; 5s ago
     Docs: man:named(8)
 Main PID: 6792 (named)
    Tasks: 23 (limit: 4915)
   CGroup: /system.slice/bind9.service
           └─6792 /usr/sbin/named -f -u bind"
1813363,2019-05-28 16:56:31 UTC,"If you go to the Controller Summary tab in the UI for a specific region controller, you will see that MAAS does monitor the status of its services, including bind."
1813364,2019-03-28 04:14:21 UTC,https://github.com/snapcore/snapcraft/pull/2518
1813364,2019-10-20 19:57:00 UTC,`long_description` isn't actually a good candidate for the `description` field in snapcraft because the text is actually used for the project homepage on pypi (and often also on Github).
1813370,2019-02-15 21:22:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813371,2019-01-28 13:01:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813371,2019-09-07 20:25:11 UTC,This bug was fixed in the package openvswitch - 2.12.0~git20190903.1cdf291dc-0ubuntu1
1813372,2019-02-25 04:14:33 UTC,apport information
1813372,2019-02-26 10:38:55 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc8 kernel[0]."
1813372,2019-02-26 15:43:13 UTC,I have tested with kernel version 5.0-rc8 and the issue with connection speed is still there (see below)
1813372,2019-03-02 15:48:51 UTC,"I have been in touch with several members of the Realtek module development team.  They have provided access to the code for a newer module, called rtw88, which is currently under review.  Based on comments from Tony Chuang and local tests performed here confirms that this new module better supports 802.11ac connection speeds than the previous r8822be driver."
1813372,2019-02-26 18:26:09 UTC,"Although iwconfig reports a bit rate of 866.7 Mb/s, it still appears that my wireless connection speeds are less than 300 Mb/s.  I recommend this bug report stay open until information can be obtained on the r8822be kernel module and any required fixes."
1813372,2019-02-27 03:48:01 UTC,"Please raise the issue to mailing list:
Ping-Ke Shih <email address hidden> (maintainer:REALTEK WIRELESS DRIVER (rtlwifi family))
<email address hidden> (open list:REALTEK WIRELESS DRIVER (rtlwifi family))
<email address hidden> (open list:NETWORKING DRIVERS)
<email address hidden> (open list)"
1813372,2019-02-25 04:14:32 UTC,apport information
1813372,2019-02-26 18:02:28 UTC,"It appears there is a problem with my Verizon router.  If I manually set the 5 Hz wi-fi channel number to any available channel, I see bit rates of 866.7 Mb/s on my Ubuntu Studio machine."
1813372,2019-02-25 04:14:30 UTC,apport information
1813372,2019-03-04 05:38:17 UTC,Thanks for the info.
1813372,2019-02-25 04:14:27 UTC,apport information
1813372,2019-02-25 04:14:28 UTC,apport information
1813372,2019-02-25 04:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813372,2019-02-25 04:14:15 UTC,apport information
1813372,2019-02-25 04:14:17 UTC,apport information
1813372,2019-02-25 04:14:18 UTC,apport information
1813372,2019-02-27 04:16:16 UTC,"Per the request above, a message has been sent to the maintainers list in entry #20 (below is a copy)."
1813372,2019-02-25 04:14:21 UTC,apport information
1813372,2019-02-25 04:14:22 UTC,apport information
1813372,2019-02-25 04:14:23 UTC,apport information
1813372,2019-02-25 04:14:25 UTC,apport information
1813372,2019-02-25 04:14:20 UTC,apport information
1813372,2019-02-25 04:14:26 UTC,apport information
1813375,2019-01-29 15:37:39 UTC,"Hi Derek,
thank you for your new release of Tsection.dat. Maybe this is not the best place for this request. Maybe the private OR forum could have more visibility. Anyhow I subscribe James to this ""bug"" report."
1813375,2019-01-29 22:18:13 UTC,"thanks Carlo, noted"
1813377,2019-03-31 21:21:59 UTC,"Just tested it also happens in Modern Fallback Toolset. As previously reported, is an intermittent bug, the crosshairs don't always get stuck."
1813377,2019-03-31 19:20:22 UTC,Pcbnew modern accelerated.
1813377,2019-03-31 19:04:34 UTC,"@Michael, What canvas is used?"
1813377,2019-03-31 13:06:49 UTC,"Confirmed using test dxf on 5.1.0, Windows 10 64bit."
1813377,2019-03-31 19:04:45 UTC,Is this in the footprint editor or in pcbnew?
1813377,2019-01-26 18:38:46 UTC,Thank you!
1813377,2019-01-26 18:10:45 UTC,"Sometimes the cross is visible during placement and hides afterwards.
Sometimes the cross is hidden during placement and shows afterwards."
1813377,2019-01-26 16:38:40 UTC,This appears to be fixed in the master branch.
1813377,2019-01-26 13:46:14 UTC,The cursor cross is still visible after interactively placing any dxf.
1813377,2019-01-26 11:32:47 UTC,Please attach the dxf you are testing and possibly a screenshot.
1813377,2019-01-26 18:55:10 UTC,Hmm... Maybe MSW-specific
1813378,2019-01-27 00:44:19 UTC,"I don't know why it says project=""indicator-multiload"" and Affecting System Load Indicator.  I didn't specify those."
1813379,2019-09-19 12:07:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1813381,2019-09-19 12:07:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1813384,2019-09-20 11:54:00 UTC,Which version of MAAS are you using?
1813384,2019-11-20 04:17:32 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1813384,2019-01-26 06:14:17 UTC,empty section in Used IP
1813388,2019-01-26 07:54:57 UTC,"running pip3 install lhafile removed the warning about lhafile, but the program still fails to start."
1813388,2019-12-28 01:54:07 UTC,Are you sure you installed the package from the default Ubuntu repository? I'm maintaining fs-uae in Debian and the package gets imported to Ubuntu automatically. I don't see the issue you are reporting here.
1813390,2019-02-02 00:27:18 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1813394,2020-03-05 04:55:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813394,2020-05-24 11:11:23 UTC,I agree. I confirm this is still happening on Ubuntu 20.04.
1813394,2020-05-25 01:51:54 UTC,This also applies when set up with static IP's in /etc/initramfs-tools/initramfs.conf. That case is most prominently noticed as lacking nameservers after boot.
1813394,2020-05-25 18:02:58 UTC,Investigating further reveals that the package is not adapted for netplan in the first place. The maintainer is not on launchpad and the package was imported from Debian Sid.
1813394,2020-05-25 18:26:24 UTC,"Digging even further back, it turns out that IFDOWN is in itself a workaround for an equal issue dating back to ~2012. As such, the core of the issue lies with how initramfs network setup overrides netplan. Adding that package."
1813394,2020-05-27 05:43:04 UTC,It seems the workaround above does not work on Ubuntu 20.04.
1813394,2020-10-26 18:32:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813394,2020-12-24 14:17:39 UTC,The easiest way to fix this on linux mint for me was to edit:
1813394,2021-01-13 14:04:16 UTC,Which version of Mint (or which upstream Ubuntu it is based on?) I wonder if there is a way to get those rows into the configs rather than editing packaged files?
1813395,2019-08-21 13:35:44 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1813395,2019-10-21 04:17:35 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1813396,2019-04-26 19:10:55 UTC,"Hi, thanks for reporting the bug.  I suspect cloud-init can check if there's a tty and if not append the --no-tty flag."
1813396,2020-11-24 17:58:41 UTC,"This bug is believed to be fixed in cloud-init in version 20.4. If this is still a problem for you, please make a comment and set the state back to New"
1813398,2019-02-07 17:35:57 UTC,"I'm not sure how extensively the RCU code is used (it looks like not much), but I don't think this bug is fixable without disabling it, or at least getting rid of the RCU thread in cases where the emulated process is not multithreaded."
1813398,2019-02-10 12:51:06 UTC,"note that the bug affects qemu-user on a glibc system too in case
malloc is interposed: glibc can only take the internal locks of
its own malloc implementation, any other malloc has the same issue
as musl's after fork."
1813399,2019-04-17 09:16:15 UTC,i ran in to the exact same problem. i see it the same way and believe we have to add dirmngr as package dependency for cloud-init.
1813399,2019-04-17 09:40:29 UTC,btw: i have fixed this with a little workaround in the cloud-init config by running a bootcmd that installs the package very early in the boot process:
1813399,2019-04-17 09:54:27 UTC,Just some words from the APT side:
1813399,2019-04-17 09:58:59 UTC,"So in fact, HKP is quite easy to do by hand, e.g.:"
1813399,2019-04-17 09:59:42 UTC,"That said, if you do, do require HKPS (HKP using HTTPS)."
1813400,2019-01-26 17:03:02 UTC,hmmmm
1813400,2019-10-26 00:22:08 UTC,Still happens on 237-3ubuntu10.31
1813400,2019-10-26 00:12:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813401,2019-01-26 15:00:53 UTC,"uh, now I see that I shouldn't have pasted them all here. Now this bug report is unreadable :/"
1813401,2019-01-30 18:48:31 UTC,"OK, it is fixed now https://gitlab.com/yade-dev/trunk/commit/8d28c1ff138d4962f5abfe6d663848cadc0d6674"
1813406,2019-01-28 14:07:23 UTC,Preliminary debugging seems to hint that wrong image convert status for some sectors during iteration in convert_do_copy() accumulated a much smaller allocated_sectors than it should.
1813406,2019-01-28 19:25:49 UTC,Possibly a duplicate of https://bugs.launchpad.net/qemu/+bug/1776920
1813406,2021-02-03 13:55:24 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1813411,2019-01-26 23:55:04 UTC,*** This is an automated message ***
1813413,2019-01-27 08:15:47 UTC,"A temporary workaround is in place:
https://github.com/mixxxdj/mixxx/pull/2009"
1813413,2019-01-26 19:12:48 UTC,https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/analysis.20errors
1813415,2020-07-22 08:03:48 UTC,"We have same problem, Ubuntu 18.04.4 LTS (stunnel 5.44 on x86_64-pc-linux-gnu platform):"
1813415,2020-07-22 08:32:10 UTC,"And... not only logs, memory is really leaked:
---
## Before restart:
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
14589 root      20   0 2029276 1.460g   5016 S   1.0 75.0  18:14.70 /usr/bin/stunnel4 /etc/stunnel/foobar.conf
## After restart:
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
  580 root      20   0  390604   7084   5556 S   0.0  0.3   0:00.33 /usr/bin/stunnel4 /etc/stunnel/foobar.conf
---"
1813415,2019-02-12 04:18:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813423,2020-04-03 20:07:28 UTC,i have the same issue on ubuntu 19.10
1813423,2019-12-09 15:51:33 UTC,I am running with :
1813423,2019-09-05 12:33:19 UTC,https://www.dedoimedo.com/computers/intel-microcode-atomic-update.html
1813423,2019-03-28 18:54:44 UTC,">
> Hello!
>
> I will explain what I did, I have little ability, so i made some research
> to get knowledge on how I could perform the configuration of this parameter.
>
> I found a location with the instructions I followed:
>
> # sudo cat /sys/module/i915/parameters/enable_psr
>
> This command returned -1;
> # sudo nano /etc/modprobe.d/i915.conf
>
> In this file I put:
> options i915 enable_psr = 0;
>
"
1813423,2019-03-28 07:07:26 UTC,"https://bbs.archlinux.org/viewtopic.php?id=233230 is this related? It seems it was fixed by ""i915.enable_rc6=0"" kernel parameter. Could you have a try?"
1813423,2019-03-27 01:43:58 UTC,"In theory logging into ""Ubuntu on Wayland"" should avoid the problem."
1813423,2019-03-26 19:23:25 UTC,"Same problem here, brand new install 18.10 in a new laptop, i cant pass the login, freezes all and the logs  keeps raising"
1813423,2019-03-27 12:21:10 UTC,"Having same issue, freeze without any changes on screen, on Ubuntu 18.10, Dell Precision 5530."
1813423,2019-03-21 02:03:50 UTC,We could probably fold bug 1806242 and bug 1658632 in with this one.
1813423,2019-02-04 17:39:52 UTC,Would it help to post more of the kern.logs from when it's hung?
1813423,2019-02-01 12:23:41 UTC,"there is no separate modesetting driver anymore, it's folded in the server"
1813423,2019-02-01 08:34:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813423,2019-02-01 05:14:11 UTC,"I understand that every user would like every bug they file to be considered ""Important""."
1813423,2019-01-29 03:30:06 UTC,This change was made by a bot.
1813423,2019-01-27 09:29:07 UTC,"EG, the last kern.log:"
1813423,2019-01-26 19:36:56 UTC,"I have records of the last 5 kern.og / syslog / Xorg.log files from when it hung. When it does hang, the last thing visible on the screen stays there stationary, the cursor doesn't move and no keyboard inputs eg. alt+crtl+f2 / crtl+sysrq+RSEINUB, do nothing."
1813423,2019-03-22 01:38:32 UTC,"Browsing the Xorg modesetting source code it appears that might be to blame too, since it seems to try to use atomic mode setting."
1813427,2019-05-30 03:12:55 UTC,Fix applied at this commit: https://git.launchpad.net/menulibre/commit/?id=023280bd745198a29bb1b3bbf0aa2d86fbc28fac
1813429,2019-02-01 00:12:24 UTC,I observed that libmtp contains a large listing of device/vendor information tied in with special flags for handling/mitigating errors. I noticed my device is not in the list.
1813429,2019-02-02 08:40:54 UTC,"I'm wondering if it could be related to https://sourceforge.net/p/libmtp/bugs/1797/.
Newer Linux kernels require an updated udev rule which is only available with libmtp 1.1.16 (not in cosmic)."
1813429,2019-02-01 01:07:20 UTC,android-udev-rules https://github.com/M0Rf30/android-udev-rules as installed exactly according to the directions did not fix the issue.
1813429,2019-02-01 00:23:03 UTC,Please Disregard last comment. It is listed.
1813429,2019-01-31 23:24:42 UTC,Might be related to https://forum.antergos.com/topic/10165/how-to-connect-access-android-smartphone-via-usb
1813429,2019-01-28 14:33:27 UTC,"Thank you for your bug report, could you give some details on how is connected your phone? with a cable in mtp mode? Could you also add the journalctl log from a session which showed the issue? (and maybe include a screenshot of the error dialogà"
1813429,2019-01-31 19:40:47 UTC,From the error generated by gmtp: 'error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device'
1813429,2019-01-31 16:56:53 UTC,"<edit last comment> The 'warnings' from gmtp are coming from the command line, not the graphical portion of the application."
1813429,2019-01-31 16:55:56 UTC,"As part of a more thorough test of the connection of my device, I reproduced the error again today, and also installed gmtp (1.3.10-1) on my system to see if I could move files over more easily that way instead. gmtp fails to connect to my device. I'm including another journalctl, testing started about 8:40am. You should find similar errors relating to my reproduction of the file transfer via copy/paste, and there may or may not be errors relating to gmtp failing to connect to my phone."
1813429,2019-01-31 16:35:09 UTC,"Yes, that's the proper time code."
1813429,2019-01-30 12:51:55 UTC,"The log has that error at 08:06:01, do you remember if that's the time where you saw the problem?"
1813429,2019-01-28 16:14:54 UTC,"I reproduced the bug again this morning, first thing this boot cycle. I am including the journalctl log as requested, as well as a screenshot."
1813429,2019-01-31 22:49:42 UTC,Unsure at this point where the issue is but it seems with the lower part of the stack so libmtp/libusb/kernel probaly...
1813432,2019-02-13 10:08:08 UTC,I have added this case to upstream discussion now:
1813432,2019-02-09 22:17:01 UTC,">In comment #13 you told that it prints with Ghostscript via
>
>lp -d duplex -o fit-to-page -o pdftops-renderer=gs
>
>Did it again send the job with a weird paper size? Or did the job come out straight away?
"
1813432,2019-02-05 10:00:32 UTC,In comment #13 you told that it prints with Ghostscript via
1813432,2019-01-31 15:31:17 UTC,Please try to print with
1813432,2019-01-31 17:02:45 UTC,"mupdftoraster is part of cups-filters. If it is missing for you, run"
1813432,2019-01-31 15:25:35 UTC,To remove the setting:
1813432,2019-02-01 16:03:00 UTC,"I tried `lp -d duplex -o fit-to-page -o pdftops-renderer=XXX` with hybrid, gs, pdftops, pdftocairo, and mupdf as the renderers (for the last I had to install both mupdf and mupdf-tools)."
1813432,2019-01-31 15:09:52 UTC,">How do I undo what I just did, i.e., how do I undo the option setting you just had me add to perform this test?
"
1813432,2019-01-31 15:16:19 UTC,It doesn't print with lpr. It doesn't print with lp -d. It doesn't print from evince. It doesn't print from the chrome PDF viewer.
1813432,2019-01-29 17:59:33 UTC,Please run the following command:
1813432,2019-01-31 14:40:02 UTC,"How did you print this file? Did you use evince? ""lp -d <printer> <file>""? Or some other application? Can you try to print with another of the possible methods/applications? Does the file print then?"
1813432,2019-01-31 13:56:51 UTC,No change.
1813432,2019-01-31 14:59:24 UTC,What is the default pdftops-renderer for CUPS in Ubuntu? I can't find it documented anywhere and I can't figure out how to query CUPS to ask what it is.
1813432,2019-01-31 14:56:36 UTC,"I take it back, there _is_ a difference."
1813432,2019-01-31 15:07:00 UTC,"So, if I use pdftops-renderer=pdftops or pdftops-renderer=pdftocairo nothing happens on the printer at all. If I use pdftops-renderer=gs the printer prints the job with a non-standard paper size. If I use pdftops-renderer=mupdf it fails, even if I have mupdf or mupdf-tools installed, because apparently mupdftoraster isn't in the mupdf package (and I'm not sure what package it's in)."
1813436,2019-03-23 22:43:39 UTC,"Here is a possible fix:
https://github.com/mixxxdj/mixxx/pull/2063"
1813436,2019-03-20 20:03:15 UTC,I am still experiencing this issue (2.3.0-alpha-pre (build master r6745)).
1813436,2019-01-29 15:19:08 UTC,fix for the spinnies is in https://github.com/mixxxdj/mixxx/pull/2013
1813436,2019-01-28 20:48:05 UTC,Mixxx 2.2.0 doesn't seem to be affected. Since I didn't notice any major code changes for this parts of the code between 2.2 and 2.3 I suppose the bug might be caused by a slight change in initialization order or a race condition.
1813436,2019-01-28 20:43:27 UTC,"Ok, I am able to reproduce the bug when switching the key notation."
1813436,2019-01-27 19:45:31 UTC,@ronso0
1813436,2019-01-27 19:31:12 UTC,@ronso0
1813436,2019-01-27 18:55:06 UTC,"okay, I'll look into it."
1813436,2019-03-20 23:21:31 UTC,"@swiftb0y
It hasn't been fixed yet. It isn't marked in progress yet. That's why you are still experiencing it."
1813436,2019-01-27 14:42:15 UTC,"probably due to some QT changes, dunno..
is it just the file path or any selected cell?"
1813436,2019-01-27 14:26:40 UTC,"@ronso0
You are right.. I still can't read the path of selected track due to this color. But before 6706 it didn't hppened.. Why it happens now? :("
1813436,2019-01-27 14:16:51 UTC,You don't need to delete your whole settings directory for testing. Just rename or move it temporarily and restore it after testing. I cannot afford losing my whole library just for testing ;)
1813436,2019-01-27 14:13:15 UTC,Key analysis will be back soon: https://github.com/mixxxdj/mixxx/pull/2010
1813436,2019-01-27 13:53:18 UTC,The last build I installed from scratch and continues is build 6711 I wrote 6710 by mistake.. The correct is 6711 . You will see it in the log anyway..
1813436,2019-01-27 13:53:18 UTC,you can see the file paths now also in Linux Mint? Looks like it was the Mint os theme styling that cell..
1813436,2019-01-27 13:45:19 UTC,Hello Uwe Klotz (uklotzde)
1813436,2019-01-27 13:05:52 UTC,"Regarding the green table cell: I thought we had this sorted earlier.
@geozubuntu Is every cell you select green or is it just the file location cell?"
1813436,2019-01-27 08:21:15 UTC,I cannot confirm this bug on Fedora for the current master. The preference settings are preserved between restarts when switching the key notation.
1813436,2019-01-27 14:55:26 UTC,@ronso0
1813437,2019-04-29 16:27:07 UTC,Confirming that this happens to me as well on 18.04.
1813439,2019-01-28 16:50:21 UTC,"Hi, Finally I managed to have a multihost devstack (everything from master), but still with some weird config problems...
For me it seems that even with openvswitch firewall driver there is no visible icmp traffic in the vm (VM2 or VM1 in your setup).
Could you please send the security-groups you used?"
1813439,2019-01-27 04:17:48 UTC,"I am not sure, this is my neutron ml2_config.ini:"
1813439,2019-07-23 13:20:48 UTC,"I agree with James, this bug is a duplicate of https://bugs.launchpad.net/neutron/+bug/1732067."
1813439,2019-07-22 21:18:16 UTC,This could be a duplicate of: https://bugs.launchpad.net/neutron/+bug/1732067
1813439,2019-05-22 16:19:35 UTC,"hi, Lajos katona, do you check it on stable/rokcy?  we find that every clusters with openvswitch firewall driver have this issues. but it works well with iptables firewall driver."
1813439,2019-01-29 15:19:53 UTC,"OK, I will check it on master using devstack, My Rocky OpenStack environment is deployed by kolla."
1813439,2019-01-27 03:32:10 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1813439,2019-01-29 13:59:16 UTC,"Thanks, I checked and my group rules are similar, and finally I got a working environment, but still can't see icmp in the vm not directed by ping.
Do you have a chance to check on master?"
1813439,2019-01-29 02:31:39 UTC,"Hi, this is my security group rule:"
1813439,2019-02-07 01:31:35 UTC,"@kolla-coresec, I've subscribed you to this bug as it may be affecting kolla ovs firewall user."
1813441,2020-10-22 02:22:50 UTC,"> I was quite surprised to find the icons on the Desktop not navigable with arrow keys.
"
1813441,2020-10-22 05:51:16 UTC,That appears to be bug 1886322.
1813441,2020-10-23 05:34:28 UTC,"How about Ubuntu is not asking any ""are you sure"" questions when I delete (del or shift+del) something from the desktop?"
1813441,2020-10-23 06:01:33 UTC,"> How about Ubuntu is not asking any ""are you sure"" questions when I delete (del or shift+del) something from the desktop?
"
1813441,2020-10-23 08:12:39 UTC,I did it. Bug 1901150.
1813441,2020-12-01 15:12:07 UTC,"Hangs on Hirsute too :(
@seb128
did try now"
1813441,2020-12-01 15:55:17 UTC,"I have created Bug #1906420 which, if implemented, will solve this and other bugs."
1813441,2021-01-23 17:38:50 UTC,"Really daft regression, makes you wonder what other functionality taken for granted is missing you don't know about.."
1813441,2020-10-22 05:36:33 UTC,"You can't move around multiple icons on the desktop, only one by one.
What's the bug number for that?"
1813441,2020-10-21 21:08:23 UTC,"I was quite surprised to find the icons on the Desktop not navigable with arrow keys. Also, I couldn't cut and paste files to and from the Desktop."
1813441,2019-01-27 20:54:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813441,2020-10-09 06:59:18 UTC,"The updated Desktop Icons, ""Desktop Icons NG (DING)"" (by the same author), fixes these problems."
1813441,2020-08-26 07:00:09 UTC,@Hai NGUYEN VAN (psaxl)
1813441,2020-08-26 06:36:12 UTC,A bit more explanation can be found here: https://didrocks.fr/2018/01/23/welcome-to-the-ubuntu-bionic-age-nautilus-a-lts-and-desktop-icons
1813441,2020-06-11 01:58:21 UTC,1. That is bug 1832407 you are describing. Although you don't actually need to be able to remove the extension package in order to replace it. Installing any extension locally for your own account will override the system version.
1813441,2020-06-10 13:12:05 UTC,"> We are somewhat trapped. It's a choice between using the old version of nautilus forever with bugs and incompatibilities, or the new version of nautilus without desktop support. Those are not good choices but they are all we have now. This is not a problem created by, or unique to Ubuntu.
"
1813441,2020-06-10 12:07:53 UTC,"We are somewhat trapped. It's a choice between using the old version of nautilus forever with bugs and incompatibilities, or the new version of nautilus without desktop support. Those are not good choices but they are all we have now. This is not a problem created by, or unique to Ubuntu."
1813441,2020-06-10 11:32:12 UTC,I agree with Carlos Garcia.
1813441,2020-05-25 02:25:52 UTC,"Confirmed, happening to me as well in Ubuntu 20.04... I cannot understand why you think the importance of this is ""Low"" or ""Wishlist""... It looks to me quite serious, the desktop is used every day and most people are used to this functionality, which is uniform across the system... but not in the desktop now."
1813441,2020-04-27 18:51:57 UTC,"For what it's worth, this also prevents icons from working with multiple dock applications in the gnome-flashback session: cairo-dock, docky, avant window navigator. The launchers are created, but just show up with ""?"" icons."
1813441,2020-04-27 15:30:30 UTC,I didn't realize my bug was a duplicate (https://bugs.launchpad.net/bugs/1875125).
1813441,2020-04-26 12:16:07 UTC,"Here is a workaround for ubuntu 20.04:
    1. remove gnome extension `sudo rm -r /usr/share/gnome-shell/extensions/desktop-icons@csoriano/`
    2. install nemo: see https://gitlab.gnome.org/GNOME/nautilus/issues/158#alternative-solution and replace `dnf` with `apt`."
1813441,2020-10-09 07:09:50 UTC,"This functionality should exist without damn extensions. It is essential
functionality of normal feature-rich desktop."
1813441,2020-01-13 13:20:48 UTC,Applies to 19.10 as well
1813441,2020-04-24 15:46:48 UTC,Applies to 20.04.
1813441,2019-01-28 09:46:28 UTC,"Thanks, that's known upstream (https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/)"
1813441,2019-01-28 13:54:37 UTC,"Let's see how much of a deal that is, you can still dnd from a nautilus view on the desktop or double click on the file so it's easy to workaround..."
1813441,2019-01-28 14:14:34 UTC,">you can still dnd from a nautilus view on the desktop
"
1813441,2019-01-28 13:52:36 UTC,I think you mean to link this to https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/29?
1813441,2019-04-26 11:15:21 UTC,nautilus is the problem. when I replaced nautilus with nemo everything works correctly
1813441,2019-04-30 15:55:37 UTC,Would be worth report to nautilus upstream then
1813441,2019-05-28 18:37:54 UTC,Possible duplicates: #1822254 #858913
1813441,2019-11-25 14:23:51 UTC,"Being able to move Applications from the Menu to the desktop or move documents from the file manager to the desktop is a function that is required by many users, it is a feature that any OS and Linux Desktop has, for years that I use my PC for the first time. it's such a limit, and only GNOME-Shell has it.
Is there anyone working on it or is there a plan to get it?"
1813441,2019-04-23 17:42:39 UTC,This problem persists in the released version of Ubuntu 19.04:
1813442,2019-02-13 02:15:21 UTC,Hello? Is this thing on? My organization pays for this service. I assumed I might actually get an answer on account of that. Is Landscape abandoned?
1813442,2020-04-17 20:40:11 UTC,"Hi, we've encountered this issue as well. Our issue was with a misplaced U+FFFD � REPLACEMENT CHARACTER in the veeam packages file."
1813445,2019-02-07 18:36:26 UTC,One of the pleasurable things about triaging bug reports is the possibilty of learning something new. I was particularly interested in what responses to messages #8 and #9 would say.
1813445,2019-02-08 16:01:29 UTC,All along I have been assuming you are experiencing bug #1797501:
1813445,2019-02-08 04:25:42 UTC,"After changing to 'laserjet...'

>>>>>>


Feb 07 20:02:38 grifcj-MS-7B09 hp-scan[4375]: io/hpmud/model.c 532: no HP_LaserJet_MFP_M28-M31 attributes found in /usr/share/hplip/data/models/models.dat
Feb 07 20:02:38 grifcj-MS-7B09 hp-scan[4375]: io/hpmud/model.c 543: no HP_LaserJet_MFP_M28-M31 attributes found in /usr/share/hplip/data/models/unreleased/unreleased.dat
Feb 07 20:02:38 grifcj-MS-7B09 hp-scan[4375]: io/hpmud/model.c 532: no hp_HP_LaserJet_MFP_M28-M31 attributes found in /usr/share/hplip/data/models/models.dat
Feb 07 20:02:38 grifcj-MS-7B09 hp-scan[4375]: io/hpmud/model.c 543: no hp_HP_LaserJet_MFP_M28-M31 attributes found in /usr/share/hplip/data/models/unreleased/unreleased.dat
<<<<<<"
1813445,2019-02-08 03:46:04 UTC,"Sorry about my availability. The weekdays are tough, but I got home a little earlier tonight, so here goes."
1813445,2019-02-04 10:42:13 UTC,3.16.9 should be 3.19.1.
1813445,2019-02-04 00:48:57 UTC,From j.txt
1813445,2019-01-27 14:26:12 UTC,Try downloading and installing the plugin from
1813445,2019-02-03 01:19:40 UTC,I tried the modified scan.py from 1811504 which automatically issues the request for the image and that gets the job done.
1813445,2019-02-03 00:48:53 UTC,I finally had time to get back to this.
1813445,2019-01-29 14:23:42 UTC,"Although it may not fit your workflow, it would be useful to know whether the technique at"
1813445,2019-01-28 10:11:07 UTC,https://bugs.launchpad.net/hplip/+bug/1811088
1813445,2019-01-27 20:03:07 UTC,Sorry that I neglected to mention that I had already tried that.
1813445,2019-02-03 23:32:55 UTC,See message #2 at
1813446,2019-06-14 00:16:55 UTC,making as invalid as there appears to be sever different issues from you database to the kernel locking up which seam unrelated to nova.
1813446,2019-01-27 05:41:48 UTC,"Well maybe it's not a bug , an issue with the OS really:"
1813446,2019-01-29 02:48:00 UTC,again new installation because the old one crashed giving:
1813446,2019-05-18 23:25:42 UTC,"[root@localhost network-scripts]# systemctl status network -l
? network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2019-01-19 03:47:01 EST; 21s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 86319 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS)
  Process: 86591 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
    Tasks: 0"
1813447,2019-01-27 03:50:47 UTC,install_sources and install_keys have been implemented for landscape (server) charm and are available as of revision 30 in the charm store.
1813447,2019-02-25 23:31:12 UTC,Seems like the install_sources code path does not execute apt update somehow:
1813447,2019-05-22 19:59:39 UTC,It looks like install_keys is being handled after install_sources:
1813454,2020-03-22 16:01:59 UTC,@MatejMlakar what is your Ubuntu version?
1813454,2020-09-11 04:17:16 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1813455,2021-01-10 18:19:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1255794, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1813456,2019-01-31 18:32:35 UTC,"Hi all,"
1813456,2019-02-04 20:35:38 UTC,"Hi,"
1813456,2019-01-27 18:52:23 UTC,"Hi,
As the amd64 VM might get -kvm switch or other performance accelerating options,
whereas other VMs just don't have."
1813456,2019-01-27 14:41:05 UTC,"> The qemu image has only 1 GB RAM assigned.
"
1813456,2019-01-27 16:17:35 UTC,"Hi,
I could ask you, what lets you doubt that gdb wasn't able to allocate memory.
One more thing, media files tend to be large and require some RAM."
1813456,2019-01-27 16:51:03 UTC,"Hi again,
About excessive usage of RAM:
http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/test/audio/osc/ags_functional_osc_server_test.c?h=2.1.x#n498"
1813456,2019-01-27 08:24:48 UTC,asked on #ubuntu-release:
1813457,2019-01-27 08:50:30 UTC,this is what I have in /sys/class/power_supply/BAT0 folder:
1813463,2019-01-27 10:20:39 UTC,"Interestingly when i let the laptop suspend/sleep and then wake it up bluetooth starts to work.
$ dmesg | egrep -i 'blue|firm'
[    0.364229] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.406110] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[    2.788840] Bluetooth: Core ver 2.22
[    2.788859] Bluetooth: HCI device and connection manager initialized
[    2.788878] Bluetooth: HCI socket layer initialized
[    2.788881] Bluetooth: L2CAP socket layer initialized
[    2.788885] Bluetooth: SCO socket layer initialized
[    2.810244] Bluetooth: hci0: Firmware revision 0.1 build 130 week 44 2018
[    2.817186] iwlwifi 0000:04:00.0: loaded firmware version 41.fc1a7aea.0 op_mode iwlmvm
[    3.042541] [drm] Found VCN firmware Version: 1.73 Family ID: 18
[    3.042568] [drm] PSP loading VCN firmware
[    3.401831] psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3
[    4.065429] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.065430] Bluetooth: BNEP filters: protocol multicast
[    4.065434] Bluetooth: BNEP socket layer initialized
[    4.933825] Bluetooth: hci0: command 0x080f tx timeout
[    4.933855] Bluetooth: hci0: sending frame failed (-19)
[    6.949824] Bluetooth: hci0: command 0x0c1b tx timeout
[    6.949845] Bluetooth: hci0: sending frame failed (-19)
[    8.970148] Bluetooth: hci0: command 0x0c46 tx timeout
[    8.970210] Bluetooth: hci0: sending frame failed (-19)
[   10.981885] Bluetooth: hci0: command 0x2001 tx timeout
[   10.982056] Bluetooth: hci0: sending frame failed (-19)
[   12.998061] Bluetooth: hci0: command 0x200f tx timeout
[   12.998122] Bluetooth: hci0: sending frame failed (-19)
[ 2705.041640] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[ 2705.044665] Bluetooth: hci0: Device revision is 2
[ 2705.044668] Bluetooth: hci0: Secure boot is enabled
[ 2705.044670] Bluetooth: hci0: OTP lock is enabled
[ 2705.044672] Bluetooth: hci0: API lock is enabled
[ 2705.044674] Bluetooth: hci0: Debug lock is disabled
[ 2705.044677] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 2705.048826] Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
[ 2706.367400] Bluetooth: hci0: Waiting for firmware download to complete
[ 2706.367614] Bluetooth: hci0: Firmware loaded in 1298523 usecs
[ 2706.367724] Bluetooth: hci0: Waiting for device to boot
[ 2706.383685] Bluetooth: hci0: Device booted in 15620 usecs
[ 2706.385856] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc
[ 2706.397687] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 2706.578691] Bluetooth: RFCOMM TTY layer initialized
[ 2706.578698] Bluetooth: RFCOMM socket layer initialized
[ 2706.578705] Bluetooth: RFCOMM ver 1.11
[ 2718.694753] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 2718.694760] Bluetooth: HIDP socket layer initialized
[ 2718.702815] input: MagicMouse as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:256/0005:05AC:030D.0001/input/input16
[ 2718.703050] magicmouse 0005:05AC:030D.0001: input,hidraw0: BLUETOOTH HID v3.06 Mouse [MagicMouse] on fc:77:74:eb:f6:2b"
1813463,2019-06-12 12:24:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1813463,2019-06-13 01:58:38 UTC,Does Ubuntu 19.04 work better with this hardware?
1813463,2019-06-13 02:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813463,2019-08-12 04:17:35 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1813463,2019-08-12 07:20:40 UTC,"Same author from https://ubuntuforums.org/showthread.php?t=2411215
```
$ uname -a
Linux tp-ThinkPad-E485 4.20.4-042004-generic #201901222207 SMP Tue Jan 22 22:09:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
```"
1813463,2019-08-12 07:28:47 UTC,https://bugzilla.kernel.org/show_bug.cgi?id=202429
1813465,2019-03-12 09:11:25 UTC,"Added myself to the list. Same issue here, fresh install of 18.10 with vanilla-gnome-default-settings and arc theme."
1813465,2019-03-12 09:10:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813467,2019-02-13 21:27:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813467,2019-02-13 21:28:04 UTC,Duplicate to bug: #1781243
1813467,2019-02-13 21:30:34 UTC,"Apologies, meant to say related to #1781243"
1813471,2019-06-18 19:44:42 UTC,"I've tested 6.70.0, 6.70.1, 68.0b1, and the daily on Ubuntu 19.04, all crash after all dialogs are closed and it seems (still needs a little more testing) at least one email account is setup."
1813471,2019-06-18 19:49:10 UTC,Here are the crash reports generated using the beta
1813471,2019-07-26 20:34:49 UTC,"FWIW, 12 crashes from the same person today, on 69.0b1"
1813471,2019-08-19 09:00:09 UTC,"I am experiencing this crash on kubuntu 18.10 using thunderbird 60.8.0.  Installed package is 60.8.0+build1-0ubuntu0.18.10.1
I set GTK_USE_PORTAL=1 in the '.profile' file in the home folder.
Could provide debugging backtrace/data."
1813471,2019-08-20 13:47:00 UTC,"This seems to be the only reference to GTK_USE_PORTAL in Mozilla's code.
https://searchfox.org/comm-central/source/mozilla/toolkit/system/gnome/nsGIOService.cpp#35"
1813471,2019-08-23 21:35:52 UTC,*** Bug 1545489 has been marked as a duplicate of this bug. ***
1813471,2019-09-10 13:02:59 UTC,So it seems this has been in the code a LONG time. So if it is a regression I haven't found it yet. I still find it odd that Firefox doesn't suffer from the same issue given we share so much of the code base.
1813471,2019-09-10 13:43:22 UTC,"Created attachment 9091741
bug1514605_GTK_USE_PORTAL.patch"
1813471,2019-09-17 10:44:43 UTC,We'll release TB 70 beta 2 early next week.
1813471,2019-09-10 14:31:18 UTC,"Seems fixed, `GTK_USE_PORTAL=1 thunderbird` goes to work well on Ubuntu 19.04 with `thunderbird-mozilla-build_68.0-0ubuntu1_amd64.deb`!
With `thunderbird-mozilla-build_60.8.0-0ubuntu1_amd64.deb` now there are no crash, but dialog is still GTK.
Can any of other subscribers confirm, that this is fixed too?"
1813471,2019-09-10 17:57:37 UTC,"Pushed by <email address hidden>:
https://hg.mozilla.org/comm-central/rev/aa6de4b5b0db
fix Thunderbird startup crash when GTK_USE_PORTAL=1 is set. r=jorgk"
1813471,2019-09-11 20:05:41 UTC,"Comment on attachment 9091741
bug1514605_GTK_USE_PORTAL.patch"
1813471,2019-09-12 09:51:06 UTC,"TB 70 beta 2:
https://hg.mozilla.org/releases/comm-beta/rev/366991cd4304a6d424f25a10d8899b83e2ae8469"
1813471,2019-09-12 13:16:22 UTC,"TB 68.1.1 or TB 68.2:
https://hg.mozilla.org/releases/comm-esr68/rev/d741c4f6b95c5f3e063738d171b2fccea3695263"
1813471,2019-09-17 10:27:42 UTC,"I am having this issue with the latest version 70.0b1 but I don't see any release for 70.0b2 so basically I cannot use thunderbird.
I can confirm that using the nightly there are no problems."
1813471,2019-05-19 14:48:28 UTC,Learned something new today. :)
1813471,2019-09-10 13:51:09 UTC,"Comment on attachment 9091741
bug1514605_GTK_USE_PORTAL.patch"
1813471,2019-05-19 06:35:32 UTC,"Hi Wayne,
I tried recompiling Thunderbird but, despite adding the proper configuration switches to add debug symbols, apparently the build process did not add them."
1813471,2019-01-29 07:17:49 UTC,"Here is Report contents for this crash:
Add-ons: gconversation%40xulforum.org:2.14.7,%7Ba300a000-5e21-4ee0-a115-9ec8f4eaa92b%7D:0.3.17b1,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:60.4.0,messagingmenu%40mozilla.com:1.4
BuildID: 20190115190018
ContentSandboxCapabilities: 119
ContentSandboxCapable: 1
ContentSandboxLevel: 0
CrashTime: 1548746230
Email: <email address hidden>
FramePoisonBase: 9223372036600930304
FramePoisonSize: 4096
InstallTime: 1548745720
Notes: Ubuntu 18.10FP(D00-L1100-W00000000-T000) OpenGL: Intel Open Source Technology Center -- Mesa DRI Intel(R) Haswell  -- 3.0 Mesa 18.2.2 -- texture_from_pixmap
WR? WR- OMTP? OMTP-
ProductID: {3550f703-e582-4d05-9a08-453d09bdfdc6}
ProductName: Thunderbird
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 487409
StartupCrash: 0
StartupTime: 1548746229
TelemetryEnvironment: {""build"":{""applicationId"":""{3550f703-e582-4d05-9a08-453d09bdfdc6}"",""applicationName"":""Thunderbird"",""architecture"":""x86-64"",""buildId"":""20190115190018"",""version"":""60.4.0"",""vendor"":null,""platformVersion"":""60.4.0"",""xpcomAbi"":""x86_64-gcc3"",""updaterAvailable"":false},""partner"":{""distributionId"":null,""distributionVersion"":null,""partnerId"":null,""distributor"":null,""distributorChannel"":null,""partnerNames"":[]},""system"":{""memoryMB"":7792,""virtualMaxMB"":null,""cpu"":{""count"":4,""cores"":2,""vendor"":""GenuineIntel"",""family"":6,""model"":60,""stepping"":3,""l2cacheKB"":256,""l3cacheKB"":3072,""speedMHz"":3400,""extensions"":[""hasMMX"",""hasSSE"",""hasSSE2"",""hasSSE3"",""hasSSSE3"",""hasSSE4_1"",""hasSSE4_2"",""hasAVX"",""hasAVX2"",""hasAES""]},""os"":{""name"":""Linux"",""version"":""4.18.0-13-generic"",""locale"":""ru-RU""},""hdd"":{""profile"":{""model"":null,""revision"":null},""binary"":{""model"":null,""revision"":null},""system"":{""model"":null,""revision"":null}},""gfx"":{""D2DEnabled"":null,""DWriteEnabled"":null,""ContentBackend"":""Skia"",""adapters"":[{""description"":""Intel Open Source Technology Center -- Mesa DRI Intel(R) Haswell "",""vendorID"":""Intel Open Source Technology Center"",""deviceID"":""Mesa DRI Intel(R) Haswell "",""subsysID"":null,""RAM"":null,""driver"":null,""driverVersion"":""3.0 Mesa 18.2.2"",""driverDate"":null,""GPUActive"":true}],""monitors"":[],""features"":{""compositor"":""none"",""gpuProcess"":{""status"":""unused""}}},""appleModelId"":null},""settings"":{""blocklistEnabled"":true,""e10sEnabled"":false,""e10sMultiProcesses"":4,""telemetryEnabled"":false,""locale"":""en-US"",""update"":{""channel"":""release"",""enabled"":true,""autoDownload"":true},""userPrefs"":{""browser.cache.disk.capacity"":276480,""browser.search.region"":""RU""},""sandbox"":{""effectiveContentProcessLevel"":0},""addonCompatibilityCheckEnabled"":true,""isDefaultBrowser"":null},""profile"":{}}
ThreadIdNameMapping: 28980:""Gecko_IOThread"",28981:""Link Monitor"",28982:""Socket Thread"",28983:""JS Watchdog"",28990:""BGReadURLs"",28991:""Hang Monitor"",28996:""Timer"",28997:""StreamTrans #1"",28998:""Cache2 I/O"",28999:""Cookie"",29000:""GMPThread"",29001:""SoftwareVsyncThread"",29002:""Compositor"",29003:""VRListener"",29004:""ImgDecoder #1"",29005:""ImageIO"",29010:""IPDL Background"",29011:""LoadRoots"",29012:""DataStorage"",29013:""DataStorage"",29015:""mozStorage #1"",29016:""HTML5 Parser"",29020:""ImgDecoder #2"",29021:""DOM Worker"",29022:""ImageBridgeChild"",
Throttleable: 1
UptimeTS: 1.03866891
Vendor:
Version: 60.4.0
useragent_..."
1813471,2019-03-09 14:00:02 UTC,"I confirm I'm seeing the crash as well on TB 60.5.3 - since the Arch Linux build does not have debug symbols enabled, I'm recompiling the package to see if I can get a proper backtrace."
1813471,2018-12-16 19:12:05 UTC,Note that I cannot post a backtrace because archlinux doesn't ship debug symbols. But given that this crash is 100% reproducible I hope that someone else will be able to.
1813471,2018-12-17 02:10:54 UTC,If you cannot get symbols with archlinux  then please get a backtrace using https://archive.mozilla.org/pub/thunderbird/releases/60.3.3/linux-x86_64/en-US/
1813471,2018-12-19 21:20:13 UTC,"Thanks for the link, it doesn't crash using that package. I'll report the crash downstream."
1813471,2019-05-12 13:34:15 UTC,"(In reply to Alessandro Menti from comment #13)

> I confirm I'm seeing the crash as well on TB 60.5.3 - since the Arch Linux build does not have debug symbols enabled, I'm recompiling the package to see if I can get a proper backtrace.
"
1813471,2019-01-28 14:39:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1813471,2019-01-29 07:10:21 UTC,"Seems this issue will be fixed only in Thunderbird 68 version, here is issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1471420"
1813471,2019-01-29 07:11:03 UTC,And here https://phabricator.kde.org/T10189 is KDE discussion about this problem.
1813471,2019-01-29 07:13:12 UTC,Here https://bugzilla.mozilla.org/show_bug.cgi?id=1514605 is same bug in Mozilla tracker.
1813471,2019-01-27 12:06:59 UTC,Also affects Arch Linux; see here: https://bugs.archlinux.org/task/61134
1813471,2018-12-16 19:11:03 UTC,User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0
1813471,2019-02-17 19:43:37 UTC,I've experienced this same crash with Thunderbird 60.5.1 from the mozilla team's ppa on Ubuntu 18.10.
1813471,2019-03-03 12:43:01 UTC,murz
1813471,2019-03-03 12:43:29 UTC,"(In reply to Elvis Angelaccio from comment #3)

> Thanks for the link, it doesn't crash using that package. I'll report the crash downstream.
"
1813471,2019-03-09 10:50:03 UTC,(In reply to Wayne Mery (:wsmwk) from comment #8)
1813471,2019-03-09 12:09:14 UTC,Anyone else see crashes with this setting?
1813471,2019-03-09 12:48:40 UTC,"Here is my two fresh crash id's for this issue:
bp-b9d80041-48a4-42d9-a4fd-8a1eb0190309
bp-e0e1b55d-99be-43eb-8ace-487550190309"
1813471,2019-03-09 13:23:11 UTC,Thanks Murz.  Was this using a download from https://releases.mozilla.org/pub/thunderbird/releases/60.5.1/linux-x86_64/en-US/ ?
1813471,2019-01-29 07:14:23 UTC,I got same crash on Ubuntu with GTK_USE_PORTAL=1 environment variable set.
1813474,2019-02-24 12:19:40 UTC,It would be great if this were implemented. Thank you.
1813474,2019-02-24 10:36:05 UTC,"I probably did not included it because of automatic cheque numbering.
But for other payment mode, there seems no reason indeed."
1813475,2019-01-28 09:41:43 UTC,I agree with your findings and reasoning.
1813479,2020-01-21 06:11:12 UTC,This bug was fixed in the package appstream - 0.12.10-1
1813480,2019-01-27 20:09:19 UTC,"Part of this overhead is that every controller is creating a dependency
engine and all the workers for every model. Now not all those workers
are running, but some, like api-caller are."
1813488,2019-01-28 09:06:31 UTC,"Hi Janek,
It is actually still correct. The github->buildbot->yadedaily pipe is still active.
But of course it will be replaced by gitlab pipeline. Thanks for spotting that, it will become a valid bug soon. ;)
Bruno"
1813488,2019-02-05 19:44:50 UTC,moved from https://bugs.launchpad.net/yade/+bug/1813488 to https://gitlab.com/yade-dev/trunk/issues/49
1813491,2019-01-28 12:04:21 UTC,Thanks for finding and documenting.
1813491,2019-03-21 08:07:59 UTC,"Same issue with snapshot build #249.
On Linux, what kind of argument for App class is expected?"
1813494,2019-02-03 15:47:38 UTC,I added the feature this way:
1813494,2019-01-30 20:03:52 UTC,"Can confirm, that worked wonderfully. Process ran as expected."
1813494,2019-01-28 20:37:14 UTC,When you do:
1813494,2019-01-28 12:05:56 UTC,Please give me an example and your expectation.
1813494,2019-01-29 10:38:16 UTC,Thanks for the detailed explanation - appreciated and understood.
1813496,2019-03-15 23:34:12 UTC,"Same here, HP Zbook 17 G5 showing something around 365mW."
1813496,2019-06-25 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813496,2019-06-27 07:32:04 UTC,"Same error on HP zBook 15 G5, with a discharge rate between 300-400 mW. Running arch linux though. Would the log files still help?"
1813496,2019-06-27 08:27:24 UTC,Which kernel version is in use?
1813496,2019-07-04 18:44:39 UTC,Currently using 5.1.15-1-MANJARO #1 SMP PREEMPT. Had the same error on arch linux.
1813496,2019-07-08 05:41:02 UTC,Do you see this issue on Linux v5.0?
1813496,2019-07-29 11:39:05 UTC,Thanks Kai-Heng - Manjaro doesn't have a 5.0 kernel (only offers me realtime and that does not boot for me) but i can confirm on both 5.1 and 5.2.
1813496,2019-09-28 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1813496,2020-04-22 11:52:05 UTC,Confirm this is still an issue on Kernel 5.6.6-1-MANJARO #1 SMP PREEMPT
1813497,2019-04-24 16:27:48 UTC,"I have begun to do some profiling of the design in question. Indeed the main problem with Eeschema is netlisting, even with the new algorithm.  I can see some approaches to improve this."
1813497,2019-04-18 03:02:54 UTC,"Hi Victor,
On the latest nightly, do you see the slowdown every time you select an object to highlight (with the tool already active) or just when you click the button to activate the highlight tool?"
1813497,2019-04-18 01:01:01 UTC,"Hi,"
1813497,2019-01-28 07:32:21 UTC,"I also suspect that is the netlist rebuilding.
It could be worth to test the new Jon'algoritm with this schematic, and see it is able to fix calculation time issue."
1813497,2019-01-28 03:12:00 UTC,"@Tom, Victor-"
1813497,2019-01-28 00:39:23 UTC,"Hi Victor,"
1813497,2019-02-23 18:11:38 UTC,Tagging the milestone so that we remember to re-visit after Jon merges his code.
1813502,2019-01-30 22:33:56 UTC,"Yes. The @name_suffix@ is removed for normal builds, but replaced with "" (Devel)"" for development builds. How'd you notice / is it causing a problem?"
1813502,2019-01-30 22:58:23 UTC,I dont think its a good idea to have @name_suffix@ for the translators to translate in case they translate it incorrectly.
1813502,2019-01-30 23:16:17 UTC,"Ah right right, translators are seeing the string.  I'll take a look at stopping that."
1813503,2020-11-24 15:13:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813504,2020-01-20 08:12:57 UTC,"I am hit by the same issue. After a few days of usage my machine got unreactive due to memory running out. I can not tell since when this issue exists, the version on my system is 2.4-6 as well. glipper now takes regularly up to 6GB of RAM. Killing glipper results in the immediate freeing of this memory."
1813506,2019-02-01 22:03:10 UTC,From UbuntuForums https://ubuntuforums.org/showthread.php?t=2407348&page=2
1813506,2019-02-04 09:33:38 UTC,"Yes, disco will get 6.2 shortly."
1813506,2019-02-01 20:59:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813506,2019-01-28 13:59:18 UTC,Do you get an error if you start it from a command line? Could you add your journalctl log after getting the issue?
1813506,2019-01-29 15:49:39 UTC,Note - https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1813755
1813506,2019-01-28 19:11:34 UTC,"I got this when running ""libreoffice"" from the command line"
1813506,2019-01-29 18:44:26 UTC,Note 2 - I've tried the latest 18.04.1 Ubuntu Budgie daily iso and I cannot reproduce this issue - so it appears to be 19.04 specific.
1813509,2021-01-03 10:20:22 UTC,"@illweckz
Please try to close the bug as it seems to apply only to unsupported ubuntu versions and fixed on current LTS kernel (5.4)."
1813509,2020-10-10 23:26:50 UTC,This bug seems to not affect Ubuntu 20.04 stock kernel.
1813509,2019-02-05 23:39:30 UTC,I have exactly the same problem on a Lenovo ThinkPad T410 running Xubuntu 18.10.
1813509,2019-04-05 09:12:15 UTC,This is affecting me on an X230 as well.
1813509,2019-02-04 23:46:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813509,2019-01-31 10:51:17 UTC,@illwieckz I see. I posted the dmesg in that thread. Thanks for replying.
1813509,2019-01-30 19:26:51 UTC,"@paed808 see my comment on that thread, as a dmesg from the faulty kernel would be useful to compare. By the way I would be surprised the bugs are the same because you really use a very far more recent hardware (mine is perhaps four years older than yours), but if the bug is in a shared component it's possible."
1813509,2019-01-30 17:00:53 UTC,Is this the same issue as my issue here?
1813509,2019-02-04 23:48:04 UTC,"If you still have the 4.18.0-13-generic kernel try booting that, it helped me get a working screen again."
1813520,2019-01-28 09:41:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813524,2020-08-04 16:06:02 UTC,I can't reproduce this problem. Maybe it was fixed somewhere in the road. Can you please retest this problem using Ubuntu Daily PPA: https://launchpad.net/~pinta-maintainers/+archive/ubuntu/pinta-daily
1813527,2019-01-31 23:52:49 UTC,https://review.openstack.org/#/c/633527/
1813527,2019-07-29 17:18:15 UTC,rpm_setup_config is correctly set in kolla-build.conf after https://review.openstack.org/#/c/633527/.
1813532,2019-03-06 10:49:37 UTC,This bug was fixed in the package linux - 4.18.0-16.17
1813532,2019-02-18 13:18:38 UTC,Successfully tested both kernels.
1813532,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1813532,2019-02-11 11:06:13 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1813532,2019-02-15 14:42:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813532,2019-01-28 08:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813534,2019-09-17 14:48:14 UTC,https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=b28a03c10e21884284ec7b8ea8952e0e715b3270
1813535,2020-07-18 20:46:10 UTC,"Yeah, it looks like effects are just applied to the entire bounding box of the selection"
1813535,2020-07-20 23:13:19 UTC,See also bug 1813535 for a related issue
1813535,2020-07-20 23:32:00 UTC,You tagged this issue as a related-to itself :-D
1813537,2019-03-31 00:41:53 UTC,"Assuming that it did install -- it's still not working most of the time (sometimes does work, don't know why). Attached logs."
1813537,2019-04-01 09:58:02 UTC,"In case of version conflict, I built a new kernel based on v5.0, please test it out:
https://people.canonical.com/~khfeng/lp1813537-2/"
1813537,2019-04-05 08:19:50 UTC,Now it installed properly but still experiencing the same issue. Attached logs.
1813537,2019-04-10 08:52:09 UTC,"Please follow [1] and see if it helps:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730331/comments/25"
1813537,2019-04-11 06:47:25 UTC,"No, sorry."
1813537,2019-04-11 07:35:03 UTC,"Ok, this can be a power management issue at platform level."
1813537,2019-04-14 01:57:41 UTC,"Definitely support uefi capsule update.
2.10 is posted here: https://fwupd.org/lvfs/device/com.dell.uefi5ffdbc0d.firmware"
1813537,2019-04-13 15:08:20 UTC,"Hmm, as I recall XPS 9360 should support UEFI capsule update.
Need help from Mario here."
1813537,2019-04-14 09:27:28 UTC,"Apparently I'm on legacy boot (""Legacy boot on HDD""), but don't care about it as long as everything works."
1813537,2019-04-14 14:19:01 UTC,You won't be able to update the BIOS from Ubuntu (this time or in the future) in legacy mode.
1813537,2019-12-24 09:18:14 UTC,"Ended up formatting my pc and changing the bios to UEFI, now things are working."
1813537,2019-04-11 09:31:34 UTC,"ignoring XPS 13 9360 TPM 1.2 [6f9095025a636a5185bfce08ed8e9fc845bc4b8a] as not updatable
No upgrades for XPS13 9360 Thunderbolt Controller, current is 21.00: 21.00=same"
1813537,2019-03-31 00:41:26 UTC,I did this - but not sure if it worked as I got some error messages (attached logs).
1813537,2019-03-12 23:02:36 UTC,Here it is.
1813537,2019-03-22 10:37:53 UTC,Can you provide instructions how to install? (I don't want to mess anything up)
1813537,2019-03-23 14:39:54 UTC,"Download them to a directory, cd to the directory, then run
$ sudo dpkg -i *.deb"
1813537,2019-01-28 15:57:03 UTC,Please attach dmesg when this issue happens.
1813537,2019-01-28 22:36:27 UTC,Attached.
1813537,2019-03-07 08:26:57 UTC,"Please update the system and try kernel 4.15.0-46.49?
It has some fix for USB that may help."
1813537,2019-03-10 14:25:45 UTC,"Didn't seem to help.
To make sure I updated to 5.0.0-050000-generic and that is not working either."
1813537,2019-01-28 09:30:07 UTC,This change was made by a bot.
1813537,2019-03-12 23:03:20 UTC,And in case it helps here it is after suspend + restart (still not working).
1813537,2019-03-12 23:04:16 UTC,And this is after power off and on - then it starts working properly.
1813537,2019-03-22 07:40:57 UTC,"[33031.949163] ath10k_pci 0000:3a:00.0: Refused to change power state, currently in D3
[33032.529373] usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[33040.549168] usb 1-3: device descriptor read/64, error -71
[33045.220988] usb 1-3: device descriptor read/all, error -71"
1813537,2019-03-22 09:13:28 UTC,Have you ever seen this issue under Arftul?
1813537,2019-03-22 09:58:32 UTC,"Please test:
https://people.canonical.com/~khfeng/lp1813537/"
1813537,2019-03-11 05:36:58 UTC,Please attach dmesg under v5.0.
1813541,2021-02-21 19:05:47 UTC,"@patpat, see at that top of this page, the link that says:"
1813541,2021-02-21 18:33:12 UTC,"This is still unsolved.
where is ""upstream"" to politely request this fixed?
Even if shim is highly security sensitive it's TFTP requesting
the wrong server in a proxyDHCP environment.
thanks"
1813541,2020-06-13 01:37:18 UTC,"The upstream bug is still unresolved, and shim is highly security sensitive code.  So we need to wait for an agreed upstream fix."
1813541,2020-06-13 00:26:13 UTC,Over 1 year and 2 Ubuntu versions later (one of them LTS) and this problem is still not fixed. Even with googling this took me hours to figure out today. :/
1813541,2019-01-28 20:55:46 UTC,To be more clear (some times I'm not very confident about my English):
1813541,2019-01-28 21:25:08 UTC,"Pseudocode for UEFI/BIOS firmwares:
If the DHCP server doesn't offer a boot filename,
and a proxyDHCP server is available,
then use the boot filename from the proxyDHCP offer,
and set TFTP=proxyDHCP."
1813541,2019-01-28 20:52:50 UTC,"The PXE specification, which also describes proxyDHCP, can be found for example at:
http://www.pix.net/software/pxeboot/archive/pxespec.pdf"
1813541,2019-01-28 20:24:23 UTC,"By chance can you provide a reference to an RFC that explains the ""correct"" interaction between proxy DHCP servers and DHCP boot file option?  Does the grub DHCP client implementation work the way you describe?"
1813541,2019-01-28 19:01:28 UTC,"Specifically, I think the issue is in
https://git.launchpad.net/ubuntu/+source/shim/tree/netboot.c#n293"
1813541,2019-01-28 21:26:50 UTC,"*Actually you can use ""boot filename = /path/to/shimx64.efi"" just to derive the /path/to/grubx64.efi if you want; but that's not very important, just for TFTP directory organization."
1813550,2019-02-05 21:09:23 UTC,moved from https://bugs.launchpad.net/yade/+bug/1813550 to https://gitlab.com/yade-dev/trunk/issues/5
1813550,2019-01-28 10:15:25 UTC,flow.reuseOrdering functionality makes a copy of the factor for efficient reuse. Algorithm was not freeing unnecessary copies.
1813550,2019-01-28 10:32:56 UTC,"Good one!
Can you push this to a gitlab branch for merge?
Tell me if you need help.
Bruno"
1813551,2020-01-21 10:37:00 UTC,The OVN driver now lives in the neutron repository. Moving this bug to their tracker.
1813551,2020-01-21 12:23:14 UTC,Isn't this patch: https://review.opendev.org/703537 is related to this bug?
1813551,2020-01-21 13:21:20 UTC,"In the master branch of networking-ovn, it has support both directions and DSCP of QoS. The related patch is [0]"
1813551,2020-02-08 01:36:18 UTC,"Reviewed:  https://review.opendev.org/703537
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dcec852b7f091c67a378db96c4841c3eec0d496a
Submitter: Zuul
Branch:    master"
1813551,2020-02-21 16:40:24 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1813553,2019-01-30 08:19:38 UTC,"The problem seems fixed, I ran a new build with the latest GDB commit from 20190129 and now I can debug the projects using LTO."
1813553,2019-01-29 19:06:51 UTC,"One more detail, it looks like the problem affects only C++ projects, since I managed to successfully debug a similar C project."
1813553,2019-01-29 19:05:57 UTC,"Ramana, do you have any contacts amongst GDB maintainers, to help us with this issue?"
1813553,2019-01-28 14:11:42 UTC,https://sourceware.org/bugzilla/show_bug.cgi?id=24145
1813553,2019-01-28 13:45:48 UTC,"> Is the same issue occurring on a linux host
"
1813553,2019-01-28 11:08:43 UTC,In this case please file a bug upstream in the gdb bugzilla. Is the same issue occurring on a linux host and could you please put up a testcase (source and binaries) that folks could use to reproduce the issue ?
1813556,2019-03-08 06:45:56 UTC,"Thanks for opening the upstream issue as well, it is sad that no one there is replying or merging your change as the preferred way would be to grab a new version of it."
1813556,2019-03-08 06:48:46 UTC,"I pinged the upstream bug as well, lets see ..."
1813556,2020-10-01 11:04:54 UTC,Fix released in htop 3.0.0
1813561,2019-01-28 11:40:52 UTC,"Version: 3.3
Build ID: 3.3+ (2018-09-29)
Finance::Quote: 1.47
Ubuntu : 18.10."
1813565,2019-01-29 23:41:27 UTC,and config file
1813565,2019-01-29 23:37:03 UTC,"well, here it is in attchment instead of text in comment #1"
1813565,2019-01-29 04:53:40 UTC,"You're right  — I didn't write the software taking into account users who have chosen to download over the network where they set it up so that the files they want can be listed but not actually read. Instead, I wrote the software so that people can download from cameras, memory cards, smartphones, and portable storage devices. I will update the program website to let others know that downloading from a NAS is at the user's own risk and is not supported."
1813565,2019-01-28 19:49:05 UTC,"Franck, Rapid Photo Downloader cannot read the files you are trying to download. That's the root cause of the problem. How it deals with unreadable files could be improved, i.e. not throwing an exception. But unless you fix your NAS configuration, Rapid Photo Downloader will not work. Period."
1813565,2019-01-28 18:59:28 UTC,"Hello,"
1813565,2019-01-29 02:11:55 UTC,">>How it deals with unreadable files could be improved, i.e. not throwing an exception.
"
1813565,2019-01-28 15:24:50 UTC,"Include in your bug report the log files, which are found in the log directory ~/.cache/rapid-photo-downloader/log. You can open this directory by clicking on the link in the ""Report a Problem"" dialog window. If possible, please also include the configuration file found in the directory ~/.config/Rapid Photo Downloader/."
1813581,2019-04-08 07:14:24 UTC,"also fails in cosmic:
https://launchpadlibrarian.net/418306128/buildlog_ubuntu-cosmic-amd64.gpgme1.0_1.11.1-1ubuntu3_BUILDING.txt.gz"
1813581,2019-08-12 09:33:06 UTC,"Uploaded. Wondering if it makes sense to actually release that fix and have users install a pointless rebuild, or just keep it stuck in proposed for whoever needs to do an SRU later?"
1813581,2019-08-13 18:12:46 UTC,"We can signal that it should be left in -proposed by adding the ""block-proposed"" tag to the bug tags and this information will be displayed on the SRU report."
1813581,2019-08-13 18:13:27 UTC,"Hello Matthias, or anyone else affected,"
1813581,2019-08-16 12:21:54 UTC,"Package built successfully, so marking it as verified."
1813581,2019-08-29 12:46:09 UTC,"All autopkgtests for the newly accepted gpgme1.0 (1.10.0-1ubuntu2.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1813582,2019-01-31 14:49:21 UTC,"DEBUG:runner:2019-01-31 14:44:29 Deployment complete in 606.56 seconds
DEBUG:runner:2019-01-31 14:45:34,400 __init__ INFO: Waiting on extended status checks...
DEBUG:runner:2019-01-31 14:45:34,402 _auto_wait_for_status INFO: Waiting for extended status on units for 5400s...
DEBUG:runner:2019-01-31 14:45:34,402 _auto_wait_for_status DEBUG: Default extended status wait match:  contains READY (case-insensitive)
DEBUG:runner:2019-01-31 14:45:34,402 _auto_wait_for_status DEBUG: Excluding services from extended status match: ['mysql', 'mongodb', 'memcached', 'ceilometer']
DEBUG:runner:2019-01-31 14:45:34,403 _auto_wait_for_status DEBUG: Waiting up to 5400s for extended status on services: ['percona-cluster', 'rabbitmq-server', 'keystone', 'ceph-osd', 'ceph-mon', 'gnocchi']
DEBUG:runner:2019-01-31 14:45:37,063 _auto_wait_for_status INFO: OK
DEBUG:runner:2019-01-31 14:45:37,064 get_default_keystone_session DEBUG: Authenticating keystone admin...
DEBUG:runner:2019-01-31 14:45:37,876 run_ceilometer_upgrade_action DEBUG: Checking ceilometer-upgrade
DEBUG:runner:2019-01-31 14:46:06,343 _auto_wait_for_status INFO: Waiting for extended status on units for 5400s...
DEBUG:runner:2019-01-31 14:46:06,344 _auto_wait_for_status DEBUG: Default extended status wait match:  contains READY (case-insensitive)
DEBUG:runner:2019-01-31 14:46:06,344 _auto_wait_for_status DEBUG: Excluding services from extended status match: ['mysql', 'mongodb', 'memcached']
DEBUG:runner:2019-01-31 14:46:06,344 _auto_wait_for_status DEBUG: Waiting up to 5400s for extended status on services: ['ceilometer', 'percona-cluster', 'rabbitmq-server', 'keystone', 'ceph-osd', 'ceph-mon', 'gnocchi']
DEBUG:runner:2019-01-31 14:46:37,214 _auto_wait_for_status INFO: OK
DEBUG:runner:2019-01-31 14:46:37,214 run_ceilometer_upgrade_action DEBUG: OK
DEBUG:runner:2019-01-31 14:46:37,214 test_100_services DEBUG: Checking system services on units...
DEBUG:runner:2019-01-31 14:46:37,214 validate_services_by_name DEBUG: Checking status of system services...
DEBUG:runner:2019-01-31 14:46:41,478 get_ubuntu_release_from_sentry DEBUG: gnocchi/0 lsb_release: bionic
DEBUG:runner:2019-01-31 14:46:42,763 validate_services_by_name DEBUG: gnocchi/0 `sudo service haproxy status` returned 0
DEBUG:runner:2019-01-31 14:46:44,045 validate_services_by_name DEBUG: gnocchi/0 `sudo service gnocchi-metricd status` returned 0
DEBUG:runner:2019-01-31 14:46:45,348 validate_services_by_name DEBUG: gnocchi/0 `sudo service apache2 status` returned 0
DEBUG:runner:2019-01-31 14:46:45,349 test_100_services DEBUG: OK
DEBUG:runner:2019-01-31 14:46:45,349 test_200_api_connection DEBUG: Checking api functionality...
DEBUG:runner:2019-01-31 14:46:45,960 test_200_api_connection DEBUG: OK
DEBUG:runner:2019-01-31 14:46:49,735 run_action WARNING: charmhelpers.contrib.amulet.utils.run_action has been deprecated for amulet.run_action
DEBUG:runner:2019-01-31 14:47:01,997 run_action WARNING: charmhelpers.contrib.amulet.utils.run_action has been deprecated for amulet.run_action
DEBUG:runner:Exit Code: 0
DEBUG:bundletester.utils:Updating JUJU_MODEL: ""fnordahl-serverstack:admin/default"" -> """"
_______________________________________________________________..."
1813582,2019-02-01 06:55:16 UTC,Unfortunately I am seeing this in Cosmic (and subsequently the Rocky UCA).
1813582,2019-02-01 09:31:17 UTC,"Amendment to comment #14, the test was executed on bionic-rocky UCA which strictly speaking is not Cosmic.  There might be other things at play here, setting back to Fix Released for Cosmic"
1813582,2019-02-05 22:32:39 UTC,"The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813582,2020-02-12 15:09:09 UTC,The xenial/queens fix got tangled with some following SRU work but its all now released.
1813582,2019-02-07 09:28:52 UTC,"Hello Frode, or anyone else affected,"
1813582,2019-02-07 10:45:41 UTC,13.2.4+dfsg1-0ubuntu0.18.10.1~cloud0 is in rocky-proposed for the UCA so marking bug task as fix committed.
1813582,2019-02-07 11:06:35 UTC,Bionic/Rocky proposed tested OK:
1813582,2019-02-05 22:42:40 UTC,This bug was fixed in the package ceph - 12.2.8-0ubuntu0.18.04.2
1813582,2019-01-31 11:01:10 UTC,"Hello Frode, or anyone else affected,"
1813582,2019-01-28 16:20:59 UTC,Maybe http://tracker.ceph.com/issues/25175
1813582,2019-01-29 14:41:37 UTC,Cosmic is not actually impacted by this bug so marking as Invalid for >= Cosmic
1813582,2019-01-29 09:37:51 UTC,Bionic update uploaded for SRU team review; I already had a point release in flight for cosmic so will upload that referencing this bug shortly.
1813582,2019-01-29 07:33:59 UTC,I can confirm that using the packages from PPA mentioned in #4 solves the issue for Bionic:
1813582,2019-01-28 16:39:27 UTC,cosmic is still on 13.2.1 so will potentially be impacted.
1813582,2019-01-28 16:39:12 UTC,disco has the latest mimic release which contains the proposed fix for this issue so should be fine - marking Fix Released.
1813582,2019-01-28 16:38:29 UTC,May impact cosmic and disco - checking now.
1813582,2019-01-28 16:36:11 UTC,Test package for bionic building here:
1813582,2019-01-28 16:22:56 UTC,I think this is fixed in 12.2.9 - we should probably just rev up to the latest 12.2.x release to resolve.
1813582,2019-01-28 12:21:13 UTC,Downgrading the ceph packages to 12.2.7 resolves the issue and gnocchi status succeeds
1813582,2019-01-29 14:42:19 UTC,Actually make that Fix Released rather than invalid - changes in gnocchi or ceph have resolved this issue in later versions.
1813587,2019-03-29 11:49:46 UTC,"This is something that is currently fixing just a build failure, not something that the end user is affected... Marking as verification done (and I'm using the package because my system is on bionic)"
1813587,2019-04-03 13:36:44 UTC,What about Cosmic? Has anyone actually checked that the packages still work on Cosmic?
1813587,2019-04-04 00:56:16 UTC,"> What about Cosmic? Has anyone actually checked that
> the packages still work on Cosmic?
"
1813587,2019-04-04 09:36:22 UTC,This bug was fixed in the package libunistring - 0.9.9-0ubuntu2
1813587,2019-03-29 10:08:02 UTC,"Hello Matthias, or anyone else affected,"
1813587,2019-04-04 09:36:42 UTC,This bug was fixed in the package libunistring - 0.9.10-1ubuntu1.18.10.1
1813587,2019-04-11 08:06:39 UTC,This bug was fixed in the package libidn - 1.33-2.2ubuntu1.1
1813587,2019-04-11 08:10:28 UTC,This bug was fixed in the package libidn - 1.33-2.1ubuntu1.2
1813587,2019-04-04 09:36:26 UTC,"The verification of the Stable Release Update for libunistring has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813587,2019-03-29 10:06:17 UTC,"Hello Matthias, or anyone else affected,"
1813587,2019-04-04 09:35:30 UTC,"its a build fix...
anyway, its a library, so not that easy to test, but I picked up gnome-characters, one of its reverse-dependencies that uses a lot of unicode, and it still works"
1813587,2019-03-27 11:48:12 UTC,@Brian
1813587,2019-01-29 13:19:29 UTC,"yes, it is the same, but unfortunately I don't know if the fix is sane or not.
the real bug is this one
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250"
1813587,2019-02-25 12:03:58 UTC,"An upload of libunistring to bionic-proposed has been rejected from the upload queue for the following reason: ""This upload has only an FTBFS bug attached to it even though it's a new upstream release SRU (from 0.9.9 tp 0.9.10). That does not seem like the 'fix' to a FTBFS issue. Please re-upload with just the FTBFS fix or fill in additional SRU bugs for all the other changes.""."
1813587,2019-03-29 09:50:33 UTC,"Hello Matthias, or anyone else affected,"
1813587,2019-03-21 09:31:05 UTC,"I uploaded the upstream patch in the unapproved queue, thanks!"
1813587,2019-03-21 09:36:24 UTC,"In the same way, I'm uploading a fix for libidn, I think it is really better to have as-needed used for the binary size, so better use the upstream patch and revert the package currently in updates."
1813587,2019-03-15 19:22:47 UTC,"The FTBFS was fixed upstream, in gnulib (from which libunistring takes most of its source files), through this commit:
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=cca32830b57e91f837c01d15b8732f23ff97fc36"
1813587,2019-03-26 17:12:27 UTC,"Hello Matthias, or anyone else affected,"
1813587,2019-03-26 17:17:38 UTC,"The regression potential here in the description is incorrect ""We are simply backporting the workaround we applied in Ubuntu 18.10."" The fix in Ubuntu 18.10 for both packages was to add ""--no-as-needed"" to the build options which you now indicate is a worse solution. Please also upload the better fix to the cosmic SRU queue."
1813587,2019-03-27 11:33:05 UTC,"Ok Brian, so lets backport the fix from 19.04 and fix also 18.10"
1813587,2019-03-27 11:35:00 UTC,"libunistring backport patch to cosmic from Disco:
diff -Nru libunistring-0.9.10/debian/changelog libunistring-0.9.10/debian/changelog
--- libunistring-0.9.10/debian/changelog        2018-07-23 16:46:28.000000000 +0200
+++ libunistring-0.9.10/debian/changelog        2019-03-27 12:21:30.000000000 +0100
@@ -1,3 +1,10 @@
+libunistring (0.9.10-1ubuntu1.18.10.1) cosmic; urgency=medium
+
+  * Cherry-pick pthread fix from upstream and disco release.
+    (LP: #1813587)
+
+ -- Gianfranco Costamagna <email address hidden>  Wed, 27 Mar 2019 12:21:30 +0100
+
 libunistring (0.9.10-1ubuntu1) cosmic; urgency=medium"
1813587,2019-01-29 09:19:49 UTC,"Cosmic got that workaround, it includes no details about the issue it fixes but could be the same one?
http://launchpadlibrarian.net/379762076/libunistring_0.9.10-1_0.9.10-1ubuntu1.diff.gz"
1813590,2019-04-08 07:44:17 UTC,"also ftbfs in cosmic:
https://launchpadlibrarian.net/418304747/buildlog_ubuntu-cosmic-amd64.pep8_1.7.1-1ubuntu1_BUILDING.txt.gz"
1813592,2019-05-08 20:36:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813594,2019-04-06 03:37:42 UTC,"also ftbfs in disco:
https://launchpadlibrarian.net/417924365/buildlog_ubuntu-disco-amd64.python-formencode_1.3.0-0ubuntu5_BUILDING.txt.gz"
1813594,2019-04-08 07:57:22 UTC,"also ftbfs in cosmic:
https://launchpadlibrarian.net/418304767/buildlog_ubuntu-cosmic-amd64.python-formencode_1.3.0-0ubuntu5_BUILDING.txt.gz"
1813595,2020-03-24 12:07:28 UTC,Confirmed still and issue for Bionic.
1813596,2020-03-24 11:57:26 UTC,Resolved by security team as part of a set of security updates.
1813596,2019-04-06 03:38:39 UTC,"also ftbfs in disco:
https://launchpadlibrarian.net/417924498/buildlog_ubuntu-disco-amd64.python-pysaml2_4.5.0+dfsg1-0ubuntu2_BUILDING.txt.gz"
1813596,2019-04-08 08:03:12 UTC,"also ftbfs in cosmic:
https://launchpadlibrarian.net/418305080/buildlog_ubuntu-cosmic-amd64.python-pysaml2_4.5.0+dfsg1-0ubuntu2_BUILDING.txt.gz"
1813596,2019-06-18 12:52:32 UTC,same in eoan
1813598,2019-12-24 07:16:46 UTC,"---
 efi/fio.h | 9 ---------
 1 file changed, 9 deletions(-)"
1813598,2020-09-17 15:32:29 UTC,This seems to be fixed.
1813601,2019-01-30 20:23:50 UTC,"Hi,"
1813601,2019-01-31 13:39:02 UTC,"Hi Ian,"
1813603,2019-01-28 14:34:45 UTC,apport information
1813603,2019-07-09 09:18:31 UTC,Was able to make it work with 5.2-rc7 kernel with this repo: https://github.com/EntropicEffect/rtl8822bu with this patch: https://github.com/EntropicEffect/rtl8822bu/commit/70d7b10a2eafdbf36ee64790646d74b5baf3a807.diff and it's connecting with protected/secure networks unlike the other repo.
1813603,2019-07-09 09:08:51 UTC,I can confirm that it doesn't work with 5.2.0-050200rc7-generic #201906300430 SMP Sun Jun 30 04:32:31 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux.
1813603,2019-01-29 04:01:57 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc3 kernel[0]."
1813603,2019-01-28 14:35:26 UTC,apport information
1813603,2019-01-28 14:35:12 UTC,apport information
1813603,2019-01-28 14:34:48 UTC,apport information
1813603,2019-01-28 14:34:46 UTC,apport information
1813603,2019-01-28 14:34:43 UTC,apport information
1813603,2019-01-28 14:34:42 UTC,apport information
1813603,2019-01-28 14:34:41 UTC,apport information
1813603,2019-01-28 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813603,2019-01-28 14:34:30 UTC,apport information
1813603,2019-01-28 14:34:31 UTC,apport information
1813603,2019-01-28 13:51:56 UTC,kernel version 4.18.0-13-generic #14-Ubuntu SMP
1813603,2019-01-28 14:34:36 UTC,apport information
1813603,2019-01-28 14:34:37 UTC,apport information
1813603,2019-01-28 14:34:39 UTC,apport information
1813603,2019-01-28 14:34:33 UTC,apport information
1813604,2019-01-30 08:52:31 UTC,apport information
1813604,2019-02-18 09:29:09 UTC,"If that's a regression, can you test if the issue doesn't happen on v4.4 kernel, which is used by 16.04?"
1813604,2019-02-18 09:28:03 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1813604,2019-02-14 08:15:02 UTC,"Is there any way to ""bump this up""?"
1813604,2019-01-30 08:52:36 UTC,apport information
1813604,2019-01-30 08:52:35 UTC,apport information
1813604,2019-01-30 08:52:33 UTC,apport information
1813604,2019-01-30 08:52:32 UTC,apport information
1813604,2019-01-30 08:52:30 UTC,apport information
1813604,2019-01-30 08:52:25 UTC,apport information
1813604,2019-01-30 08:52:27 UTC,apport information
1813604,2019-01-30 08:52:24 UTC,apport information
1813604,2019-01-30 08:52:23 UTC,apport information
1813604,2019-01-30 08:52:22 UTC,apport information
1813604,2019-01-29 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813604,2019-01-29 15:56:02 UTC,Am attaching alsa-info text file generated using:
1813604,2019-01-29 15:53:21 UTC,Adding to linux source package as suggested in https://wiki.ubuntu.com/DebuggingSoundProblems
1813604,2019-01-28 16:20:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1813604,2019-01-30 08:52:29 UTC,apport information
1813605,2019-06-14 14:58:49 UTC,and ^^ is using CMR
1813605,2019-06-14 16:41:56 UTC,The etcd update is actually available in the edge channel (--channel edge)
1813605,2019-06-14 16:37:22 UTC,One extra piece of info is that the etcd charmstore version has not yet been updated to include the fix from https://github.com/juju-solutions/interface-tls-certificates/pull/16 but i tried building one myself and despite vault receiving the new unit_name setting it does not appear to be responding with certs.
1813605,2019-06-14 14:58:32 UTC,@chris.macnaughton I just tried this a vault charm based off master that I built myself (so should have latest charm-helpers patches in it) and I get:
1813605,2019-06-18 13:41:11 UTC,"Ok, I have retested this and it is actually working. It needed the edge version of the etcd charm and I had also forgotten to run the generate-root-ca action on vault. Once I did those it worked."
1813605,2019-04-18 22:08:36 UTC,Fixed in https://github.com/juju-solutions/interface-tls-certificates/pull/16
1813605,2019-02-05 07:50:29 UTC,I have reproduced this and am digging in further.
1813605,2019-02-05 10:01:42 UTC,This issue will impact the tls-certificates and vault-kv interfaces as both make use of the remote unit name on the providing side when generating key prefixes for unit specific responses.
1813605,2019-05-16 11:17:53 UTC,"charm-vault has had commits land in the two weeks since, in both stable and master branches. This bug should, thus, be fix-released."
1813605,2019-02-07 23:21:34 UTC,I'm working on the fix for the interface layer.
1813605,2019-02-05 10:06:36 UTC,https://github.com/juju-solutions/interface-tls-certificates/issues/14
1813610,2019-02-12 11:40:55 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/636309"
1813610,2019-02-12 11:41:10 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/636310"
1813610,2019-02-12 11:41:24 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/636311"
1813610,2019-03-07 08:49:49 UTC,"Reviewed:  https://review.openstack.org/636309
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=8aa46b6c8d1a861efefa43b6d6e5267c155744f5
Submitter: Zuul
Branch:    stable/queens"
1813610,2019-03-07 09:05:07 UTC,"Reviewed:  https://review.openstack.org/636310
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=967542fcb18363b85fdd6cf5cde5844c1321b693
Submitter: Zuul
Branch:    stable/queens"
1813610,2019-03-07 09:05:15 UTC,"Reviewed:  https://review.openstack.org/636311
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=c05aa892eb7119f590e0e0488c0fb6a977d34e43
Submitter: Zuul
Branch:    stable/queens"
1813610,2019-03-14 03:32:07 UTC,Its stable/queens only changes. All the required changes are merged.
1813610,2019-06-21 15:26:09 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1813620,2020-12-14 06:03:06 UTC,"I met same panic too, and enabled lockdep in kernel 4.19.67, the log is:"
1813620,2019-11-12 08:15:44 UTC,I found that the latest drm-tip kernel for amd64 was at https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2019-11-08/ as the more recent ones had failed to compile according to the READMEs.
1813620,2019-11-12 04:24:01 UTC,"Please test drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip"
1813620,2019-10-03 18:24:34 UTC,Here is a better link that might allow anyone who wants to review the thread or use a local email client to reply https://<email address hidden>/
1813620,2019-08-06 18:12:12 UTC,Reported by e-mail to recipients listed in comment 6. Here's a link to the post in the archive of the Linux Foundation virtualization mailing list:
1813620,2019-08-06 17:24:12 UTC,Sorry for the spam. I'm not used to those Ubuntu bug reporting tools.
1813620,2019-08-06 17:18:42 UTC,apport information
1813620,2019-05-21 18:05:34 UTC,"Sorry for the belated reply. Does this issue still happen on 5.2-rc1? If the issue still exists, please raise the issue to the following maintainers via email:
Dave Airlie <email address hidden> (maintainer:DRM DRIVER FOR QXL VIRTUAL GPU)
Gerd Hoffmann <email address hidden> (maintainer:DRM DRIVER FOR QXL VIRTUAL GPU)
David Airlie <email address hidden> (maintainer:DRM DRIVERS)
Daniel Vetter <email address hidden> (maintainer:DRM DRIVERS)
<email address hidden> (open list:DRM DRIVER FOR QXL VIRTUAL GPU)
<email address hidden> (open list:DRM DRIVER FOR QXL VIRTUAL GPU)
<email address hidden> (open list:DRM DRIVERS)
<email address hidden> (open list)"
1813620,2019-05-04 07:29:32 UTC,Still happens with 5.1-rc7.
1813620,2019-05-02 10:12:17 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc7 kernel [0]."
1813620,2019-04-30 20:35:38 UTC,"This still occurs with 19.04 (Disco Dingo) and kernel 5.0.0-13-generic, and does not seem to be Firefox specific. I've also had this crash when using some KDE apps. This issue seems to occurs at 2-3 times a day on frequent use, each time requiring a forced reboot to fix (because Ubuntu never reboots gracefully when Xorg is hanging in kernelspace)."
1813620,2019-01-28 16:30:07 UTC,This change was made by a bot.
1813620,2019-08-06 17:18:44 UTC,apport information
1813623,2019-01-28 17:13:56 UTC,https://prnt.sc/mdcy64
1813626,2019-06-19 14:33:36 UTC,The problem still exists after do-release-upgrade to 18.04.2 LTS.
1813626,2019-01-31 00:35:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813626,2019-01-30 23:45:12 UTC,"I see the same problem, see https://ubuntuforums.org/showthread.php?t=2411319&page=2&p=13834468#post13834468"
1813633,2019-05-14 17:05:58 UTC,Fix pushed:
1813633,2019-05-14 23:02:27 UTC,Tested with the concerto data.  Works perfectly.  Signed-off branch is at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1813633-tcn-search-deleted-rec-signoff
1813633,2019-05-16 15:38:07 UTC,"Thanks, Garry.  Fix merged to 3.2 and above."
1813634,2019-04-29 20:54:15 UTC,I can reproduce this with snapcraft version 3.4+git7.gba7c6e1
1813634,2019-04-29 20:54:44 UTC,This is also discussed on the forum at https://forum.snapcraft.io/t/cross-compile-snap-on-amd64-to-arm/11133
1813634,2019-05-02 00:49:39 UTC,"yep, SNAPCRAFT_ARCH_TRIPLET works OK in destructive mode. When running using by multipass snapcraft becomes different beast, a bit tricky to predict. In general snapcraft is not giving much help to handle cross compiling.
I understand that it would be naive to expect from snapcracft to solve cross compiling for all the various build systems, but giving enough information about host and target is minimum info it can provide.... And I believe this should not be hard to pass, especially since we have already have env variable there.
A bit worrying this is not getting any attention... not even comment from snapcraft team"
1813634,2019-06-06 16:36:53 UTC,We are facing the same issue and it's critical to have it fixed please. I don't wanna introduce fragile hacks into build and deployment pipeline to fix such issues.
1813644,2019-01-29 20:21:25 UTC,"Just tested again. I am not trying to make it launch for all users, just the user I'm logging in as."
1813644,2019-01-29 18:36:56 UTC,How did you set it to launch for all users?
1813646,2019-01-28 19:58:16 UTC,"Confirmed.  This is an oversight.  The menu entry for ""Cataloging => Search The Catalog"" is correct, so that entry could be copied into place under the main ""Search"" menu."
1813646,2019-02-26 16:44:38 UTC,"I asked in IRC, but more broadly, are there any objections to me just fixing this and pushing it to master now? I'd prefer to avoid the time of a branch dance... :)"
1813646,2019-02-26 17:08:30 UTC,Sounds good to me.
1813646,2019-02-26 17:22:05 UTC,OK by me.
1813646,2019-02-27 15:45:49 UTC,"Interestingly, the search link seems to be correct in current master (fixed back in November of 2018 in 7075905d588919bce7e6a520b3a061e142e16e19).  I'm correcting the splash page link here, and that's it."
1813650,2019-01-28 20:05:15 UTC,"When I change the cloud name to 'localhost' I can actually change the configuration via the yaml file, and everything works as expected:"
1813650,2019-07-05 11:50:09 UTC,"This is still problem in juju 2.6 too, except that on 2.6 changing the cloud name to 'localhost' doesn't work either:"
1813650,2019-07-23 23:17:47 UTC,PR for 2.5:   https://github.com/juju/juju/pull/10459
1813651,2019-01-31 14:29:19 UTC,Correction: it happens in 4.19 also. I continue with the bisect process.
1813651,2019-04-19 18:37:35 UTC,"Guilherme, is there going to be further work on this bug?"
1813651,2019-04-22 13:11:44 UTC,"Hi Terry, I'm planning to post an update this week.
It seems the problem is related with physical block size adjustments,
after the introduction of the patch: ""eb53a3ea3e00 scsi: hpsa: limit transfer length to 1MB, not 512kB"""
1813651,2019-04-30 21:39:28 UTC,"I've narrowed down the problem for devices in HBA mode; if device is in RAID mode (despite if it's effectively using some raid level or has only 1 disk), it does not reproduce the issue. I'll attach files with outputs from HP RAID utility (accessed in BIOS) for both cases.
I continue the investigation."
1813651,2019-11-11 17:47:38 UTC,"The problem was fixed by the following commit, present in all Ubuntu releases: 625d7d351887 (""scsi: hpsa: correct ioaccel2 chaining""). Basically it was an access to a DMA non-mapped region, and was restricted to non-RAID mode adapters due to the I/O path being different."
1813651,2019-11-11 18:03:36 UTC,"For the current Ubuntu releases, the kernels with this fix are listed below."
1813656,2019-04-22 20:49:40 UTC,I sent a reminder to the mailing list trying to get the feedback from the community.
1813656,2019-05-22 19:25:57 UTC,Any objection to close this bug?
1813656,2019-01-30 18:27:31 UTC,"This may already be covered by:
https://storyboard.openstack.org/#!/story/2004877"
1813656,2019-01-30 18:23:39 UTC,Marking as release gating; missing API documentation.
1813656,2019-01-30 18:44:34 UTC,"Hi Ghada,"
1813659,2019-02-11 00:14:01 UTC,Was this with on of the modern canvases or the legacy canvas?  I cannot duplicate this behavior on 5.1.0-rc1-28-g605d0ab3c on Linux using either modern canvas.
1813659,2019-02-11 00:41:03 UTC,"With modern canvas, can still be reproduced."
1813659,2019-02-11 00:42:56 UTC,Does not reproduce in Legacy Toolset.
1813659,2019-03-16 12:08:22 UTC,It appears that there is a tool state issue at play here.
1813659,2019-07-26 04:33:08 UTC,TOOL_MANAGER's event dispatch logic is having trouble when the activating tool and the deactivating tool are both states in the same TOOL_INTERACTIVE.
1813659,2019-07-26 15:32:16 UTC,Two ACTIONs by the same TOOL_INTERACTIVE turned out to be a red herring.  It was just some missing AF_ACTIVATE flags on the ACTIONs in question.
1813659,2019-07-26 18:22:10 UTC,"Fixed in revision 815602d1af0f3d4381b0795cbe9bec55d38afc51
https://git.launchpad.net/kicad/patch/?id=815602d1af0f3d4381b0795cbe9bec55d38afc51"
1813660,2019-02-07 20:48:45 UTC,Are there plans to backport this to Pike->Queens as well or is the transition of neutron-agents to baremetal getting in the way of this?
1813660,2019-01-29 16:51:31 UTC,"FYI https://review.openstack.org/625898 resolved this for Queens->Rocky, and for Rocky->Stein we've opted to change the whole process to something a lot simpler which also solves the issue: https://review.openstack.org/624773"
1813662,2019-01-31 00:39:13 UTC,* Jarl:
1813662,2019-10-10 03:37:49 UTC,I'm creating a file:
1813662,2019-10-10 03:34:44 UTC,"BUG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725 is super, ultra annoying and useless!"
1813662,2019-04-30 20:54:20 UTC,"Hilko, you probably know this but it looks like in the original thread here:"
1813662,2019-04-30 00:04:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813662,2019-02-04 14:23:29 UTC,* Jarl:
1813662,2019-01-31 13:01:02 UTC,@Hilko:
1813662,2019-01-31 12:39:27 UTC,"@Pino: Thanks for emphasizing that only Ubuntu (and derivatives) is affected. I should have researched myself, sorry."
1813662,2019-01-30 11:43:05 UTC,"(In reply to Jarl Friis from comment #0)
This prerequisite is not true

> for Debian and Ubuntu (and maybe others), hence the virt-builder does not
> work on these platforms. If Debian and Ubuntu should continue to be
> ""supported"" target platforms (and I suggest they should) then a change is
> needed for virt-builder.
"
1813662,2019-01-28 22:14:56 UTC,"This looks like an instance of our old favourite:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725"
1813662,2019-01-30 11:32:30 UTC,"@Hilko. First of all thank you very much for putting your time into maintaining packages. This is highly appreciated.
Secondly, I don't consider this issue a packaging issue (neither on the linux nor the libguestfs package). Even though it is an issue that has emerged from the ubuntu/debian decision that system kernel images shall not be readable by non-root users, I consider it an issue of the libguestfs software. Therefore I have opened a bug report on the libguestfs bug-system: https://bugzilla.redhat.com/show_bug.cgi?id=1670790"
1813662,2019-01-30 11:21:37 UTC,Description of problem:
1813662,2019-01-29 14:46:34 UTC,* Jarl:
1813662,2019-01-29 13:36:04 UTC,"You can choose arbitrary kernels by setting the SUPERMIN_* environment
variables.  See:
http://libguestfs.org/supermin.1.html#ENVIRONMENT-VARIABLES
http://libguestfs.org/guestfs-faq.1.html#how-can-i-compile-and-install-libguestfs-if-my-distro-doesnt-have-new-enough-qemu-supermin-kernel"
1813662,2019-01-29 12:24:02 UTC,OK. Thanks for the link and explanation. So it doesn't have to be the exact image of the kernel that is running? just a reasonable image?
1813662,2019-01-29 10:48:56 UTC,It's how it works: http://libguestfs.org/guestfs-internals.1.html#architecture
1813662,2019-01-29 09:32:21 UTC,I tend to agree with you and the discussion on the other bug that I don't see that preventing read-access to the running kernel gives any security at all.
1813662,2019-01-29 09:01:05 UTC,"The problem is that the kernel isn't readable by non-root for
voodoo reasons.  (I don't agree this is a sane configuration)"
1813662,2019-01-28 23:23:51 UTC,@Richard Jones: I don't quite agree. It is not reported on the same package. This bug is not about requesting read-permission on the kernel (that may be one solution though). This bug is about virt-builder not working on ubuntu (where kernels are not readable by non-root users).
1813662,2019-01-30 11:41:48 UTC,"This is a bug in Ubuntu, please see my and Hilko's extensive comments in
https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1813662
I have nothing more to add."
1813665,2019-01-30 09:50:52 UTC,Tested also in Windows with the latest nightly build. Doesn't work correctly.
1813665,2019-01-29 01:19:17 UTC,"Fixed in revision cf6ba6ad94395460a7c84cd95e67624d4c9769dc
https://git.launchpad.net/kicad/patch/?id=cf6ba6ad94395460a7c84cd95e67624d4c9769dc"
1813665,2019-01-29 08:41:40 UTC,"The fix doesn't seem to work. I'm testing git a4d4d9a2419. If the farthest end point of the short segment is inside the second-last segment, ""D"" still grabs the joint of the two segments, not the farthest end point."
1813666,2019-07-20 00:27:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813670,2019-01-28 22:53:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633616"
1813670,2019-08-12 16:30:27 UTC,"Reviewed:  https://review.opendev.org/633616
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=78e382c3a5e84fa838d1ede8c49bab515150a7dd
Submitter: Zuul
Branch:    master"
1813670,2019-09-13 16:41:57 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.
1813673,2019-02-08 15:18:16 UTC,I see this semi-regularly too.  We're on 3.2 currently.
1813673,2020-01-27 22:53:54 UTC,Still a problem in 3.4.1
1813673,2020-02-26 18:47:23 UTC,Evergreen 3.2.8
1813673,2020-02-27 18:20:35 UTC,The missing header/footer while still logged in is related to this:
1813679,2020-05-20 12:49:03 UTC,Is that still an issue in focal?
1813679,2020-05-21 16:48:35 UTC,"I haven't upgraded to Focal yet, but it's still an open issue upstream: https://github.com/vim/vim/issues/5237"
1813679,2019-11-19 04:14:39 UTC,I did a bisect as asked in the upstream issue I reported at https://github.com/vim/vim/issues/5237 and I think that https://github.com/vim/vim/commit/cd142e3369db8888163a511dbe9907bcd138829c is the offending commit.
1813679,2019-11-19 09:00:30 UTC,"Thanks for the investigation, looks like it's a vim issue from your bisecting"
1813679,2019-11-19 00:56:23 UTC,"The permissions and ownership are the same. It seems to persist across ejecting and remounting the SSH mount. I can see if it persists across a reboot or magically spreads from one SSH mount to a different mount (via a different hostname/ip for the same machine), but I suspect it won't."
1813679,2019-11-19 03:13:06 UTC,"Sorry, I misremembered my results from yesterday. I just checked again. The permissions are in fact different: the Nautilus-created files are 644 (because my ""New Text Document.txt"" template in ~/Templates is 644), while files created with e.g. touch are 664."
1813679,2019-11-18 20:37:59 UTC,Thank you for your bug report. Does it only happen directly after creating the file or is it still an issue for those files after e.G a reboot?
1813679,2019-11-17 20:20:39 UTC,I can actually only get this to manifest *for files created by Nautilus*. Files that are created from an ssh session or by cd-ing into the /run/user/1000/... directory are unaffected. So I guess this also affects Nautilus?
1813679,2019-11-17 19:28:13 UTC,"This is an interaction between vim and GVFS, so I've added GVFS as affected."
1813680,2019-01-29 00:32:13 UTC,The bRestrict import should have been addressed by lp:1772245
1813680,2019-01-29 00:56:23 UTC,Please find attached the .brd file in question. I would have also attached the .sch file as well but it appears that one can only attach one file at a time. Is this sufficient?
1813680,2019-01-29 00:58:25 UTC,... and the .sch file.
1813680,2019-01-29 04:12:41 UTC,Thanks.  We should take care of the layer imports during v6.
1813688,2019-02-07 23:41:13 UTC,We discovered that adding the time to the DATE_FORMAT in config.tt2 adds the due date time in the Items Checked Out section of My Account but not in the record view.  The due date display in the record view comes from copy_table.tt2
1813701,2019-03-18 17:41:04 UTC,I can confirm kernel 4.18.10 there is no flickering.
1813701,2019-04-01 07:56:57 UTC,"I tested this in ubuntu 19.04 beta (core 5.0.0-7), artifacts are present.
Currently this error is missing exclusively in the core 4.18.0-10."
1813701,2019-04-01 09:29:03 UTC,"$ git log --pretty=oneline v4.18.12..v4.18.13 drivers/gpu/drm/amd
d9ef158adf04b81772a7e9d682a054614ebac2fd Revert ""drm/amd/pp: Send khz clock values to DC for smu7/8""
5113d730a1ee26bb13cbe38fdc10a7ebe7baf3cd drm/amdgpu: fix error handling in amdgpu_cs_user_fence_chunk
ed14acd316bae2d3365f71ea9941490a71d3adf2 drm/amdgpu: Fix SDMA hang in prt mode v2"
1813701,2019-03-07 14:30:17 UTC,"Why look for -rc? if there is no problem only in the kernel version 4.18. (10, 11, 12), in all other kernel versions 4.18 there is a bug"
1813701,2019-04-01 10:30:39 UTC,"Kai-Heng Feng (kaihengfeng), not, i don't know.
Please tell me as much as possible.
I don't speak English very well, but I'll try to figure it out."
1813701,2019-03-14 22:46:50 UTC,Can confirm this is happening on fresh install of Linux Mint and Manjaro as well. Tried installing Kernel 5.0.2 but no fix.
1813701,2019-04-02 13:30:59 UTC,"Drew Walton (drewwalton19216801), Thanks! it works."
1813701,2019-04-04 06:04:54 UTC,"But following the description, the commit canceled the previous patch due to some problems. I think you need a more detailed study of the problem"
1813701,2019-04-03 07:36:29 UTC,"$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
$ cd linux
$ git checkout ed14acd316bae2d3365f71ea9941490a71d3adf2
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it."
1813701,2019-04-03 19:24:57 UTC,"Kai-Heng Feng (kaihengfeng),i built kernel with commit ed14acd316bae2d3365f71ea9941490a71d3adf2."
1813701,2019-04-04 06:02:43 UTC,"Ok, I found a problem commit. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.18.y&id=d9ef158adf04b81772a7e9d682a054614ebac2fd"
1813701,2019-04-04 09:26:03 UTC,I also tested the d9ef158adf04b81772a7e9d682a054614ebac2fd commit. There is a problem in it.
1813701,2019-04-04 11:41:07 UTC,"Commit c3cb424a0869 (""drm/amd/pp: Send khz clock values to DC for smu7/8
"") is in mainline but mainline still has the issue?"
1813701,2019-04-04 13:41:17 UTC,"has already
https://bugs.freedesktop.org/show_bug.cgi?id=110199"
1813701,2019-04-04 13:49:05 UTC,and https://bugs.freedesktop.org/show_bug.cgi?id=102646
1813701,2019-03-06 16:22:19 UTC,Would it be possible for you to do a kernel bisection?
1813701,2019-04-03 07:20:05 UTC,"Drew, Thanks!"
1813701,2019-02-28 16:29:45 UTC,I tried the v5.0-rc7 and rc8 kernels. the problem is not solved
1813701,2019-04-01 22:41:28 UTC,The issue is somewhere in the dynamic power management code. Here's a workaround that has completely resolved the flickering (for me):
1813701,2019-02-02 00:34:33 UTC,This also happens on my system with RX480
1813701,2019-02-18 11:04:32 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1813701,2019-01-29 06:44:36 UTC,It looks like a problem with the Xorg graphics driver:
1813701,2019-01-29 06:47:04 UTC,"Oh, it appears you have at least one unsupported PPA installed that has replaced some graphics packages:"
1813701,2019-01-29 06:49:31 UTC,"To get rid of the problem, I tried to install the amdgpu-pro driver 18.50, but it is supported only in ubuntu 18.04. Then I installed the free driver https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers. but unfortunately the problem is not solved."
1813701,2019-01-29 07:15:07 UTC,"The correct ""free"" drivers come built into Ubuntu automatically."
1813701,2019-01-29 07:17:16 UTC,"third-party PPA removed, packages updated"
1813701,2019-01-29 07:20:18 UTC,"This problem is detected immediately after installing the system. I tried to install third-party drivers to fix the problem, but it did not help. Now all removed"
1813701,2019-01-29 07:55:44 UTC,Thanks.
1813701,2019-01-30 01:45:13 UTC,"I think this problem is identical to mine.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1802976
I also found some more videos confirming the problem on Ubuntu 18.04
https://www.youtube.com/watch?v=jYdoA7wTuz4
https://www.youtube.com/watch?v=BqBc9kZvjHQ"
1813701,2019-01-29 07:13:50 UTC,"Yes, please remove both of those from your system and follow the steps in comment #3. The drivers you installed seem to be causing problems so we can't really see the original problem right now."
1813701,2019-01-30 03:13:36 UTC,"what packages do I need to install? for example for kernel version 4.18.16
linux-headers-4.18.16-041816-generic_4.18.16-041816.201810200431_amd64.deb
linux-headers-4.18.16-041816_4.18.16-041816.201810200431_all.deb
linux-image-unsigned-4.18.16-041816-generic_4.18.16-041816.201810200431_amd64.deb
?
or i can put all the kernels of the sub version immediately
sudo apt install linux-image-4.18.0* linux-headers-4.18.0*
?"
1813701,2019-01-30 03:26:35 UTC,"For any given directory/folder on that site, scroll down to:"
1813701,2019-01-30 06:19:34 UTC,"Ok, I consistently checked the kernels from version 10.18.20 to 10.18.10. There is no bug at 10.18.10. If you need it later, I can check on versions from 10.18.9 to 10.18.1.
What need to provide logs on the working core?"
1813701,2019-01-30 06:21:33 UTC,"sorry typo, kernel version 4.18"
1813701,2019-02-02 00:33:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813701,2019-01-30 06:46:05 UTC,"Thanks. If there is no bug at kernel 4.18.10, did you verify the bug is present in 4.18.11?"
1813701,2019-01-30 12:21:39 UTC,"I rechecked all kernels of version 4.18 again. No bug kernels only:
4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
4.18.12-041812-generic #201810032137 SMP Thu Oct 4 01:39:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
4.18.11-041811-generic #201809290731 SMP Sat Sep 29 11:33:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
4.18.10-041810-generic #201809260332 SMP Wed Sep 26 07:34:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
On all others starting 4.18.1 ending 4.18.20 there is a bug."
1813701,2019-01-31 03:00:07 UTC,This change was made by a bot.
1813701,2019-01-30 02:09:34 UTC,Sounds like we _could_ make this a duplicate of bug 1802976. But I wouldn't just yet...
1813704,2019-04-08 22:08:22 UTC,"Reviewed:  https://review.openstack.org/649366
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=195c1378317719d548dfd149ecc0ec9b01d53eef
Submitter: Zuul
Branch:    stable/queens"
1813704,2019-04-08 22:09:25 UTC,"Reviewed:  https://review.openstack.org/649369
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=51a766653395c11985b7dd5d3e3549224ae4ca88
Submitter: Zuul
Branch:    stable/pike"
1813704,2019-04-09 07:06:34 UTC,"Reviewed:  https://review.openstack.org/649365
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6494fcc2e44d9d9310e3ebaa92582f4f78d08b75
Submitter: Zuul
Branch:    stable/rocky"
1813704,2019-04-09 13:54:02 UTC,"Reviewed:  https://review.openstack.org/649682
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7d30ea950844f11348fa2827908622e3a8c7dfb
Submitter: Zuul
Branch:    stable/stein"
1813704,2019-05-20 22:51:41 UTC,"Reviewed:  https://review.opendev.org/649691
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fa16540d2dd80f836c8fa2a424717899ac64af60
Submitter: Zuul
Branch:    stable/pike"
1813704,2019-04-17 19:23:50 UTC,"Reviewed:  https://review.openstack.org/649683
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5d705468de1e495639f8b87266ccfc9391ce6135
Submitter: Zuul
Branch:    stable/rocky"
1813704,2019-04-30 20:33:55 UTC,"Does anyone have a recommended rpc_response_timeout to set? The default of 60 is far too low, IMO, even with these fixes. Is there a downside to setting it as high as 480 or even 600? If the network is down, it won't matter. If neutron-server, it is better to wait than retry the request and making neutron-server to double the work."
1813704,2019-05-21 08:29:05 UTC,"Reviewed:  https://review.opendev.org/649701
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=49df07c7039206c537c17f40140d290e1b28a3f4
Submitter: Zuul
Branch:    stable/ocata"
1813704,2019-08-17 18:31:06 UTC,"Reviewed:  https://review.opendev.org/649693
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bb2734b0d524aef348b69ae02988449f9dd63c56
Submitter: Zuul
Branch:    stable/ocata"
1813704,2019-04-03 19:06:41 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649701"
1813704,2019-04-17 02:06:32 UTC,"Reviewed:  https://review.openstack.org/649688
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=39afe0a129b6b979d0b56ec59048a4e16bedf7a9
Submitter: Zuul
Branch:    stable/queens"
1813704,2019-04-03 18:52:24 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649693"
1813704,2019-04-08 22:07:46 UTC,"Reviewed:  https://review.openstack.org/649343
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=98139553424375a2a0ec18fb6b07b4bf30fe88d0
Submitter: Zuul
Branch:    stable/stein"
1813704,2019-04-03 18:14:13 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/649688"
1813704,2019-04-03 18:29:00 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/649691"
1813704,2019-01-29 18:48:06 UTC,"Does playing around with the rabbitmq config options help, in accepting more requests?"
1813704,2019-01-30 06:17:23 UTC,"The RPC timeout wes only seen in ovs-agent side. Timeout was met in this function setup_port_filters with high probability:
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1791-L1792
Mostly because there are some heavy query in neutron server side, but we did not see exception in neutron server side. Or maybe neutron server does not complete the data response. Or there are large table join query or insufficient conditions.
So for this issue, IMO, we should narrow down the RPC query request size for this method."
1813704,2019-02-22 12:01:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638646"
1813704,2019-04-02 00:30:33 UTC,"Reviewed:  https://review.openstack.org/638642
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6ac420df7eb3ed324669472c61fec41b3d9cb35b
Submitter: Zuul
Branch:    master"
1813704,2019-04-02 14:30:40 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/649343"
1813704,2019-02-22 12:00:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638642"
1813704,2019-04-02 15:23:11 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/649366"
1813704,2019-04-02 15:28:49 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/649369"
1813704,2019-04-03 06:39:38 UTC,"Reviewed:  https://review.openstack.org/638646
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8408af4f173a0ffde354599e26c49bf9e17e8bef
Submitter: Zuul
Branch:    master"
1813704,2019-04-03 17:52:21 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/649682"
1813704,2019-04-03 18:04:07 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649683"
1813704,2019-04-02 15:14:44 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649365"
1813705,2019-04-05 17:34:21 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/650394"
1813705,2019-04-16 21:07:17 UTC,"Reviewed:  https://review.openstack.org/650393
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bb508f9e6051ccb27b6dfda05b5c52b961f7370a
Submitter: Zuul
Branch:    stable/pike"
1813705,2019-04-15 21:38:30 UTC,"Reviewed:  https://review.openstack.org/650394
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7a4bc6e43fb7274b940fb88f13011821e283b3bb
Submitter: Zuul
Branch:    stable/ocata"
1813705,2019-04-15 20:56:22 UTC,"Reviewed:  https://review.openstack.org/650392
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=df4e0a5394dff4cc176096abc64079d2c43fa9e7
Submitter: Zuul
Branch:    stable/queens"
1813705,2019-04-15 20:56:02 UTC,"Reviewed:  https://review.openstack.org/650390
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=26a9765afb917901ca40e3117ff092774823ada2
Submitter: Zuul
Branch:    stable/rocky"
1813705,2019-04-15 20:55:44 UTC,"Reviewed:  https://review.openstack.org/650389
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7764064d0455634b18cc0931bcc44343913a1c6
Submitter: Zuul
Branch:    stable/stein"
1813705,2019-04-05 17:33:21 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/650393"
1813705,2019-04-05 17:31:52 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/650389"
1813705,2019-04-05 17:32:21 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650390"
1813705,2019-04-05 04:19:05 UTC,"Reviewed:  https://review.openstack.org/638645
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=64ea642359e8f8aee2ebe494e037ecdfe8cf1b2c
Submitter: Zuul
Branch:    master"
1813705,2019-02-22 12:01:12 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638645"
1813705,2019-02-20 03:03:27 UTC,"Paste some logs:
2019-02-20 11:00:41.944 2268474 WARNING ovsdbapp.backend.ovs_idl.vlog [-] tcp:127.0.0.1:6640: send error: Broken pipe 2019-02-20 11:00:41.968 2268474 WARNING ovsdbapp.backend.ovs_idl.vlog [-] tcp:127.0.0.1:6640: connection dropped (Broken pipe)
2019-02-20 11:01:46.027 2268474 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor tcp:127.0.0.1:6640 Interface name,ofport,external_ids --format=json]: None
2019-02-20 11:01:47.331 2268474 ERROR neutron.agent.linux.async_process [-] Process [ovsdb-client monitor tcp:127.0.0.1:6640 Interface name,ofport,external_ids --format=json] dies due to the error: None"
1813705,2019-01-30 06:24:19 UTC,"We do not find out the root cause of this issue, but we can see those drop or broken in the ovs-agent log.
IMO, this issue is someting related to coroutine switching. When restart the ovs-agent, there heavy I/O for ovs-agent to commincate the message queue to do sync action. So if there are large data transfer. The connection belongs to other coroutine (greenlet) for ovs-agent can be hang up for a long time. So the server side (ovs-vswitchd) may close the connection due to long time no heart beat."
1813705,2019-01-29 18:42:00 UTC,"Are we running out of some OS resources and is that the reason for the ovs-agent connection to get dropped to the ovs-vswitchd.
If that is the case, is it possible for us to throttle the number of ports for initial sync when the agent comes up.
We did similar throttling mechanism for the number of routers that are handled by the l3-agents, may be a similar approach to throttle the amount of ports on a particular node may be solution."
1813705,2019-04-05 17:32:59 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/650392"
1813706,2020-04-23 13:01:18 UTC,"Reviewed:  https://review.opendev.org/721242
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=713ad71c6f4e389f3a224ce2898b09977b5045bb
Submitter: Zuul
Branch:    stable/queens"
1813706,2019-04-17 19:23:56 UTC,"Reviewed:  https://review.openstack.org/649683
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5d705468de1e495639f8b87266ccfc9391ce6135
Submitter: Zuul
Branch:    stable/rocky"
1813706,2020-04-23 12:39:06 UTC,"Reviewed:  https://review.opendev.org/721239
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a10413eb3fa52de2f330b165ac81c9dd47aeda57
Submitter: Zuul
Branch:    stable/stein"
1813706,2020-04-20 11:28:38 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/721242"
1813706,2020-04-20 11:25:05 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/721240"
1813706,2020-04-20 11:24:27 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/721239"
1813706,2019-09-13 03:15:53 UTC,"Reviewed:  https://review.opendev.org/638641
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8e73de8bc42067c0a6796df3cca9938d25ae754e
Submitter: Zuul
Branch:    master"
1813706,2019-08-17 18:31:11 UTC,"Reviewed:  https://review.opendev.org/649693
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bb2734b0d524aef348b69ae02988449f9dd63c56
Submitter: Zuul
Branch:    stable/ocata"
1813706,2019-04-17 02:06:37 UTC,"Reviewed:  https://review.openstack.org/649688
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=39afe0a129b6b979d0b56ec59048a4e16bedf7a9
Submitter: Zuul
Branch:    stable/queens"
1813706,2020-04-23 12:44:26 UTC,"Reviewed:  https://review.opendev.org/721240
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=41fe9ff147244eb6d7573235fa12f45ed56be9b3
Submitter: Zuul
Branch:    stable/rocky"
1813706,2019-04-03 18:52:27 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649693"
1813706,2019-04-09 13:54:08 UTC,"Reviewed:  https://review.openstack.org/649682
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7d30ea950844f11348fa2827908622e3a8c7dfb
Submitter: Zuul
Branch:    stable/stein"
1813706,2019-01-29 18:37:03 UTC,"Again I have the same question here. Do you have any logs from the ovs-agent that what is doing or where it is held up.
Is it having trouble to contact the ovswitchd and is that causing any problems?
Is there any information to track?"
1813706,2019-01-30 06:26:36 UTC,"All the following bugs can cause such infinitely fullsync:
(1) RPC timeout during ovs-agent restart
https://bugs.launchpad.net/neutron/+bug/1813704
(2) local connection to ovs-vswitchd was drop or timeout
https://bugs.launchpad.net/neutron/+bug/1813705
(7) multipe cookies flows (stale flows) (failed to clean stale flows)
https://bugs.launchpad.net/neutron/+bug/1813712
(8) dump-flows takes a lots of time (failed to dump flows)
https://bugs.launchpad.net/neutron/+bug/1813709"
1813706,2019-02-22 12:01:35 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638646"
1813706,2019-04-03 06:39:41 UTC,"Reviewed:  https://review.openstack.org/638646
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8408af4f173a0ffde354599e26c49bf9e17e8bef
Submitter: Zuul
Branch:    master"
1813706,2019-05-20 22:51:45 UTC,"Reviewed:  https://review.opendev.org/649691
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fa16540d2dd80f836c8fa2a424717899ac64af60
Submitter: Zuul
Branch:    stable/pike"
1813706,2019-04-03 18:04:12 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649683"
1813706,2019-04-03 18:14:15 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/649688"
1813706,2019-04-03 18:29:04 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/649691"
1813706,2019-04-03 17:52:24 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/649682"
1813707,2019-04-08 22:08:24 UTC,"Reviewed:  https://review.openstack.org/649366
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=195c1378317719d548dfd149ecc0ec9b01d53eef
Submitter: Zuul
Branch:    stable/queens"
1813707,2019-04-08 22:09:27 UTC,"Reviewed:  https://review.openstack.org/649369
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=51a766653395c11985b7dd5d3e3549224ae4ca88
Submitter: Zuul
Branch:    stable/pike"
1813707,2019-04-09 07:06:37 UTC,"Reviewed:  https://review.openstack.org/649365
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6494fcc2e44d9d9310e3ebaa92582f4f78d08b75
Submitter: Zuul
Branch:    stable/rocky"
1813707,2019-04-09 13:54:05 UTC,"Reviewed:  https://review.openstack.org/649682
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7d30ea950844f11348fa2827908622e3a8c7dfb
Submitter: Zuul
Branch:    stable/stein"
1813707,2019-04-15 20:55:46 UTC,"Reviewed:  https://review.openstack.org/650389
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7764064d0455634b18cc0931bcc44343913a1c6
Submitter: Zuul
Branch:    stable/stein"
1813707,2019-04-15 20:56:04 UTC,"Reviewed:  https://review.openstack.org/650390
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=26a9765afb917901ca40e3117ff092774823ada2
Submitter: Zuul
Branch:    stable/rocky"
1813707,2019-04-15 20:56:23 UTC,"Reviewed:  https://review.openstack.org/650392
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=df4e0a5394dff4cc176096abc64079d2c43fa9e7
Submitter: Zuul
Branch:    stable/queens"
1813707,2019-04-15 21:38:33 UTC,"Reviewed:  https://review.openstack.org/650394
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7a4bc6e43fb7274b940fb88f13011821e283b3bb
Submitter: Zuul
Branch:    stable/ocata"
1813707,2019-04-16 21:07:19 UTC,"Reviewed:  https://review.openstack.org/650393
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bb508f9e6051ccb27b6dfda05b5c52b961f7370a
Submitter: Zuul
Branch:    stable/pike"
1813707,2019-04-17 02:06:34 UTC,"Reviewed:  https://review.openstack.org/649688
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=39afe0a129b6b979d0b56ec59048a4e16bedf7a9
Submitter: Zuul
Branch:    stable/queens"
1813707,2019-05-21 08:29:09 UTC,"Reviewed:  https://review.opendev.org/649701
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=49df07c7039206c537c17f40140d290e1b28a3f4
Submitter: Zuul
Branch:    stable/ocata"
1813707,2019-04-08 22:07:50 UTC,"Reviewed:  https://review.openstack.org/649343
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=98139553424375a2a0ec18fb6b07b4bf30fe88d0
Submitter: Zuul
Branch:    stable/stein"
1813707,2019-08-17 18:31:08 UTC,"Reviewed:  https://review.opendev.org/649693
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bb2734b0d524aef348b69ae02988449f9dd63c56
Submitter: Zuul
Branch:    stable/ocata"
1813707,2019-09-13 03:15:51 UTC,"Reviewed:  https://review.opendev.org/638641
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8e73de8bc42067c0a6796df3cca9938d25ae754e
Submitter: Zuul
Branch:    master"
1813707,2020-04-20 11:24:24 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/721239"
1813707,2020-04-20 11:25:04 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/721240"
1813707,2020-04-20 11:28:37 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/721242"
1813707,2020-04-23 12:39:02 UTC,"Reviewed:  https://review.opendev.org/721239
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a10413eb3fa52de2f330b165ac81c9dd47aeda57
Submitter: Zuul
Branch:    stable/stein"
1813707,2020-04-23 12:44:24 UTC,"Reviewed:  https://review.opendev.org/721240
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=41fe9ff147244eb6d7573235fa12f45ed56be9b3
Submitter: Zuul
Branch:    stable/rocky"
1813707,2020-04-23 13:01:16 UTC,"Reviewed:  https://review.opendev.org/721242
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=713ad71c6f4e389f3a224ce2898b09977b5045bb
Submitter: Zuul
Branch:    stable/queens"
1813707,2019-04-17 19:23:53 UTC,"Reviewed:  https://review.openstack.org/649683
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5d705468de1e495639f8b87266ccfc9391ce6135
Submitter: Zuul
Branch:    stable/rocky"
1813707,2019-04-05 17:34:23 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/650394"
1813707,2019-05-20 22:51:42 UTC,"Reviewed:  https://review.opendev.org/649691
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fa16540d2dd80f836c8fa2a424717899ac64af60
Submitter: Zuul
Branch:    stable/pike"
1813707,2019-04-05 17:33:01 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/650392"
1813707,2019-04-05 17:33:22 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/650393"
1813707,2019-01-30 06:29:07 UTC,"Again this function setup_port_filters is mostly time-consuming:
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1791-L1792
https://bugs.launchpad.net/neutron/+bug/1813704"
1813707,2019-02-06 13:10:31 UTC,Is there a debug log available of that restart? it would be good to see the timings of
1813707,2019-02-22 11:59:49 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638641"
1813707,2019-02-22 12:00:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638642"
1813707,2019-02-22 12:01:14 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638645"
1813707,2019-02-22 12:01:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638646"
1813707,2019-04-02 00:30:34 UTC,"Reviewed:  https://review.openstack.org/638642
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6ac420df7eb3ed324669472c61fec41b3d9cb35b
Submitter: Zuul
Branch:    master"
1813707,2019-04-02 15:14:46 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649365"
1813707,2019-01-29 18:34:33 UTC,"So do you know where the 15-4-mins is spent by the ovs-agent, is it just spending time in the polling loop or is it locked by some resource."
1813707,2019-04-02 15:23:13 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/649366"
1813707,2019-04-02 14:30:42 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/649343"
1813707,2019-04-03 06:39:39 UTC,"Reviewed:  https://review.openstack.org/638646
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8408af4f173a0ffde354599e26c49bf9e17e8bef
Submitter: Zuul
Branch:    master"
1813707,2019-04-05 17:32:24 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650390"
1813707,2019-04-05 17:31:54 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/650389"
1813707,2019-04-02 15:28:51 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/649369"
1813707,2019-04-03 19:06:43 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649701"
1813707,2019-04-03 18:52:25 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649693"
1813707,2019-04-05 04:19:06 UTC,"Reviewed:  https://review.openstack.org/638645
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=64ea642359e8f8aee2ebe494e037ecdfe8cf1b2c
Submitter: Zuul
Branch:    master"
1813707,2019-04-03 18:14:14 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/649688"
1813707,2019-04-03 18:04:09 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649683"
1813707,2019-04-03 17:52:22 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/649682"
1813707,2019-04-03 18:29:02 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/649691"
1813708,2019-04-09 00:38:24 UTC,"Reviewed:  https://review.openstack.org/648219
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e4bfc7d50ee94502bead86078a123676bc9c24f9
Submitter: Zuul
Branch:    stable/queens"
1813708,2020-04-20 11:32:20 UTC,Do You think we can do anything else related to this bug? Or should we maybe close it?
1813708,2019-04-10 23:44:30 UTC,"Reviewed:  https://review.openstack.org/649414
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ea3d844c75541cc2be17865bad6336cd1b8385c4
Submitter: Zuul
Branch:    stable/ocata"
1813708,2019-04-09 13:53:44 UTC,"Reviewed:  https://review.openstack.org/648207
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7865264aaba615f6e52f5806d844531696186d56
Submitter: Zuul
Branch:    stable/stein"
1813708,2019-04-09 13:20:38 UTC,"Reviewed:  https://review.openstack.org/648217
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=af67d516a5b39b883fa6fb2fca4673fb7602b292
Submitter: Zuul
Branch:    stable/rocky"
1813708,2019-04-09 00:38:44 UTC,"Reviewed:  https://review.openstack.org/648220
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fb84771d1364d9be6fa7d0bce1bc89b2e3541271
Submitter: Zuul
Branch:    stable/pike"
1813708,2019-04-02 18:05:41 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649414"
1813708,2019-03-27 18:27:10 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/648207"
1813708,2019-03-27 19:24:50 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/648219"
1813708,2019-03-27 19:17:23 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/648217"
1813708,2019-03-27 07:44:57 UTC,"Reviewed:  https://review.openstack.org/638647
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f898ffd71fba4f9b8fd9f4cb851fc3976d72396a
Submitter: Zuul
Branch:    master"
1813708,2019-02-22 12:01:52 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638647"
1813708,2019-01-30 06:42:42 UTC,"LOL, we don't expect that to be human readable. But we should have methods to repair/locate the problem. So maybe this bug is related to the BP: https://blueprints.launchpad.net/neutron/+spec/troubleshooting. Besides, I will file another RFE to propose we can start to do that."
1813708,2019-01-29 18:50:53 UTC,"Not sure what you meant by 'flow tables are almost unreadable'?
Is this really a bug or human capability to read from 30k+ flows after filtering.
Can we filter and read the flows or since it is busy we are not able to even dump the flows?"
1813708,2019-03-27 19:25:18 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/648220"
1813709,2019-04-09 13:53:41 UTC,"Reviewed:  https://review.openstack.org/648207
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7865264aaba615f6e52f5806d844531696186d56
Submitter: Zuul
Branch:    stable/stein"
1813709,2019-04-10 23:44:28 UTC,"Reviewed:  https://review.openstack.org/649414
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ea3d844c75541cc2be17865bad6336cd1b8385c4
Submitter: Zuul
Branch:    stable/ocata"
1813709,2019-04-15 20:55:39 UTC,"Reviewed:  https://review.openstack.org/650389
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7764064d0455634b18cc0931bcc44343913a1c6
Submitter: Zuul
Branch:    stable/stein"
1813709,2019-04-15 20:55:56 UTC,"Reviewed:  https://review.openstack.org/650390
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=26a9765afb917901ca40e3117ff092774823ada2
Submitter: Zuul
Branch:    stable/rocky"
1813709,2019-04-15 20:56:16 UTC,"Reviewed:  https://review.openstack.org/650392
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=df4e0a5394dff4cc176096abc64079d2c43fa9e7
Submitter: Zuul
Branch:    stable/queens"
1813709,2019-04-15 21:38:25 UTC,"Reviewed:  https://review.openstack.org/650394
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7a4bc6e43fb7274b940fb88f13011821e283b3bb
Submitter: Zuul
Branch:    stable/ocata"
1813709,2019-04-16 21:07:13 UTC,"Reviewed:  https://review.openstack.org/650393
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bb508f9e6051ccb27b6dfda05b5c52b961f7370a
Submitter: Zuul
Branch:    stable/pike"
1813709,2020-04-20 11:25:09 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/721240"
1813709,2020-04-20 11:24:30 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/721239"
1813709,2020-04-20 11:28:40 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/721242"
1813709,2020-04-23 12:39:08 UTC,"Reviewed:  https://review.opendev.org/721239
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a10413eb3fa52de2f330b165ac81c9dd47aeda57
Submitter: Zuul
Branch:    stable/stein"
1813709,2020-04-23 12:44:28 UTC,"Reviewed:  https://review.opendev.org/721240
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=41fe9ff147244eb6d7573235fa12f45ed56be9b3
Submitter: Zuul
Branch:    stable/rocky"
1813709,2020-04-23 13:01:20 UTC,"Reviewed:  https://review.opendev.org/721242
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=713ad71c6f4e389f3a224ce2898b09977b5045bb
Submitter: Zuul
Branch:    stable/queens"
1813709,2019-04-09 13:20:36 UTC,"Reviewed:  https://review.openstack.org/648217
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=af67d516a5b39b883fa6fb2fca4673fb7602b292
Submitter: Zuul
Branch:    stable/rocky"
1813709,2019-09-13 03:15:49 UTC,"Reviewed:  https://review.opendev.org/638641
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8e73de8bc42067c0a6796df3cca9938d25ae754e
Submitter: Zuul
Branch:    master"
1813709,2019-04-09 00:38:42 UTC,"Reviewed:  https://review.openstack.org/648220
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fb84771d1364d9be6fa7d0bce1bc89b2e3541271
Submitter: Zuul
Branch:    stable/pike"
1813709,2019-03-27 18:27:08 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/648207"
1813709,2019-04-05 17:34:18 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/650394"
1813709,2019-04-09 00:38:22 UTC,"Reviewed:  https://review.openstack.org/648219
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e4bfc7d50ee94502bead86078a123676bc9c24f9
Submitter: Zuul
Branch:    stable/queens"
1813709,2019-01-30 06:37:44 UTC,"For now, we have no solution for this issue, but IMO we shoud divide-and-conquer the entire flows. It is really a giant beast."
1813709,2019-02-20 07:00:03 UTC,dump-flows failed with timeout:
1813709,2019-02-22 12:01:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638645"
1813709,2019-02-22 12:01:51 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638647"
1813709,2019-01-29 19:02:22 UTC,"I think you are talking about this
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ofswitch.py#L170
So you are suggesting that we should be cleaning the stale flows without a lookup, is it possible to clean without a lookup."
1813709,2019-03-27 19:17:21 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/648217"
1813709,2019-03-27 07:44:55 UTC,"Reviewed:  https://review.openstack.org/638647
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f898ffd71fba4f9b8fd9f4cb851fc3976d72396a
Submitter: Zuul
Branch:    master"
1813709,2019-03-27 19:25:17 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/648220"
1813709,2019-04-02 18:05:38 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649414"
1813709,2019-04-05 04:19:02 UTC,"Reviewed:  https://review.openstack.org/638645
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=64ea642359e8f8aee2ebe494e037ecdfe8cf1b2c
Submitter: Zuul
Branch:    master"
1813709,2019-04-05 17:31:49 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/650389"
1813709,2019-04-05 17:32:16 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650390"
1813709,2019-04-05 17:32:56 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/650392"
1813709,2019-04-05 17:33:17 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/650393"
1813709,2019-03-27 19:24:48 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/648219"
1813710,2019-02-18 09:45:23 UTC,I can't down load either I am using Mint 19.1 almost finishes the errors come up. To get my HP Deskjet 2540 going. I am getting over Linux not working
1813710,2019-04-19 11:13:54 UTC,"Hi Tracey,"
1813712,2019-04-09 00:38:49 UTC,"Reviewed:  https://review.openstack.org/648220
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fb84771d1364d9be6fa7d0bce1bc89b2e3541271
Submitter: Zuul
Branch:    stable/pike"
1813712,2019-04-10 23:44:37 UTC,"Reviewed:  https://review.openstack.org/649414
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ea3d844c75541cc2be17865bad6336cd1b8385c4
Submitter: Zuul
Branch:    stable/ocata"
1813712,2019-04-09 13:53:49 UTC,"Reviewed:  https://review.openstack.org/648207
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7865264aaba615f6e52f5806d844531696186d56
Submitter: Zuul
Branch:    stable/stein"
1813712,2019-04-09 13:20:44 UTC,"Reviewed:  https://review.openstack.org/648217
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=af67d516a5b39b883fa6fb2fca4673fb7602b292
Submitter: Zuul
Branch:    stable/rocky"
1813712,2019-04-09 00:38:30 UTC,"Reviewed:  https://review.openstack.org/648219
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e4bfc7d50ee94502bead86078a123676bc9c24f9
Submitter: Zuul
Branch:    stable/queens"
1813712,2019-09-06 11:08:24 UTC,Should we maybe consider this bug as fixed now? Or there is still some work to do there?
1813712,2019-03-27 19:25:21 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/648220"
1813712,2019-03-27 19:24:53 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/648219"
1813712,2019-03-27 19:17:27 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/648217"
1813712,2019-03-27 18:27:14 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/648207"
1813712,2019-03-27 07:44:59 UTC,"Reviewed:  https://review.openstack.org/638647
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f898ffd71fba4f9b8fd9f4cb851fc3976d72396a
Submitter: Zuul
Branch:    master"
1813712,2019-02-22 12:01:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638647"
1813712,2019-04-02 18:05:46 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/649414"
1813713,2019-02-01 09:14:59 UTC,"This is failing in a similar way on ADT with bionic/linux (also only on i386):
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190201_082722_4cb3e@/log.gz"
1813713,2019-02-01 09:18:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813713,2019-02-01 09:20:38 UTC,"This is also affecting xenial/linux (only i386 as well):
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190201_082722_4cb3e@/log.gz"
1813713,2019-10-03 10:58:18 UTC,"Didn't see this on X-4.15
4.15.0-65.74~16.04.1 - generic	/ lowlatency."
1813716,2019-06-12 08:43:54 UTC,OK. I will not reopen this bug.
1813716,2019-06-12 08:39:30 UTC,"Weird I can still reproduce this crash using mutter master from git (https://gitlab.gnome.org/GNOME/mutter/issues/629), but there is no evidence of Ubuntu crashing since the above fix."
1813716,2019-06-03 09:13:56 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813716,2019-06-12 08:42:11 UTC,Ooh...
1813716,2019-05-20 18:01:49 UTC,"No crash has been recorded for 3.32.1-2ubuntu1 and SRU'ed version for this, so marking as verified"
1813716,2019-05-06 12:17:09 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1813716,2019-05-01 11:34:41 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1
1813716,2019-04-30 02:05:07 UTC,"Tracking in both:
https://errors.ubuntu.com/problem/a27089759201dfe884a9070c2d62c50680fb2de4
https://errors.ubuntu.com/problem/1a5d1f99fd9215f7a79b718d2e915c675ebcd69f"
1813716,2019-06-03 09:13:38 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1~19.04.1
1813721,2019-01-29 08:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813721,2019-07-16 21:01:13 UTC,"Turning this option off is only significant in 4.12 kernels and newer, where the LSM hooks make use of __ro_after_init if CONFIG_SECURITY_SELINUX_DISABLE is disabled."
1813725,2019-10-25 13:01:44 UTC,"Reviewed:  https://review.opendev.org/690636
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=4af86c78f364c8c3bd8a576420d1c71ff89b4a6c
Submitter: Zuul
Branch:    stable/rocky"
1813725,2020-07-23 21:57:33 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/742756"
1813725,2020-07-30 05:06:59 UTC,"Change abandoned by Tim Burke (<email address hidden>) on branch: master
Review: https://review.opendev.org/742756
Reason: Squashed into parent patch, which probably shouldn't land without this functionality."
1813725,2020-08-30 04:12:12 UTC,"Reviewed:  https://review.opendev.org/742033
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=7d429318ddb854a23cdecfe35721b1ecbe8bcccc
Submitter: Zuul
Branch:    master"
1813725,2020-08-30 17:24:36 UTC,"Related fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/748882"
1813725,2020-08-30 17:25:56 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/748883"
1813725,2020-09-02 15:10:56 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/749532"
1813725,2020-09-02 06:29:23 UTC,"Reviewed:  https://review.opendev.org/748882
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=8ed74c264605e12717c93e9b07f4ff50924e619f
Submitter: Zuul
Branch:    stable/ussuri"
1813725,2020-09-02 15:24:45 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/749536"
1813725,2020-09-05 00:09:21 UTC,"Reviewed:  https://review.opendev.org/749532
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=db485392fc238b32e29c8aca12d2e70dd9561004
Submitter: Zuul
Branch:    stable/stein"
1813725,2020-09-05 00:49:21 UTC,"Reviewed:  https://review.opendev.org/749536
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=ca66e2e96f2272870a03cebfb8c24b9b6bbacf16
Submitter: Zuul
Branch:    stable/rocky"
1813725,2019-10-24 02:54:02 UTC,"Reviewed:  https://review.opendev.org/690629
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=8fc622b28a4fc7ed23ba79ee1db2103a541866b7
Submitter: Zuul
Branch:    stable/rocky"
1813725,2020-09-02 02:57:37 UTC,"Reviewed:  https://review.opendev.org/748883
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=eef87ee21229c8f8cc794b29e0f9abc159fc98e7
Submitter: Zuul
Branch:    stable/train"
1813725,2019-10-23 16:30:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/690636"
1813725,2019-01-29 19:55:57 UTC,"Can we get some more info from logs about the history of this object? I'd go grepping for both names, ""AUTH_abcdef/default/Infomaniak Swiss Backup Todo.txt"" and ""/AUTH_abcdef/default/Infomaniak Swiss Backup .txt"" (and probably *also* go grepping for those url-encoded, and even double-url-encoded :-/)"
1813725,2019-04-29 04:18:49 UTC,"I should have triaged this earlier, but definitely confirmed, and with https://opendev.org/openstack/swift/commit/9b3ca94 and https://opendev.org/openstack/swift/commit/4310331 landed, most of bad is contained. We should definitely make it harder to configured known-problematic pipelines (including ones that become problematic because of *our own* auto-insertion logic), but I *think* this is reasonable at Medium now? FWIW, we've got https://review.opendev.org/#/c/635040/ proposed to help with that."
1813725,2019-10-23 16:14:29 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/690629"
1813725,2019-01-29 20:06:02 UTC,"Oh yeah, and a couple other notes:"
1813725,2019-02-01 23:20:49 UTC,"So I could definitely repro... first by manually inserting the copy middleware after encryption, then again by only having *one* proxy-logging middleware and letting auto-insertion do its thing (though at that point container listings were *also* broken, as I also let listing_formats get auto-inserted and it got inserted right of encryption as well, leading to a JSON decode error in symlink, just like in https://bugs.launchpad.net/swift/+bug/1806468)."
1813725,2019-02-04 04:44:23 UTC,Sounds like we need to seriously think about rejigging how our auto-insert and maybe even pipeline management works.
1813725,2019-02-04 17:43:16 UTC,"Yup. I wonder if a decent starting point may be to start raising errors in some middlewares if we see that some other (known-problematic) middleware has already registered in get_swift_info... like, encryption could check for copy and raise an exception during proxy-server start-up saying ""hey, copy needs to be *left* of encryption""."
1813725,2019-02-05 08:17:47 UTC,"Hello Tim,"
1813725,2019-02-05 17:06:42 UTC,"Ah! Yep, looks like a pipeline problem. When you add the second proxy-logging, you'll want to make sure you move encryption (and probably kms_keymaster) over near the new proxy-logging, so your pipeline looks like"
1813725,2019-02-12 08:42:23 UTC,"Reviewed:  https://review.openstack.org/635380
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=43103319d0aa27f24e6520c0962bd19e55568ad4
Submitter: Zuul
Branch:    master"
1813725,2019-02-15 07:48:45 UTC,"Related fix proposed to branch: feature/losf
Review: https://review.openstack.org/637142"
1813725,2019-02-15 13:49:58 UTC,"Reviewed:  https://review.openstack.org/637142
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=b68bef5cd80e2a1b71a1ef544e122b39dfa7ac57
Submitter: Zuul
Branch:    feature/losf"
1813725,2019-03-22 22:31:37 UTC,"Reviewed:  https://review.openstack.org/633671
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=9b3ca9423eb8cf9420a3e98f60cd56dd281b4208
Submitter: Zuul
Branch:    master"
1813725,2019-03-27 21:11:24 UTC,"Fix proposed to branch: feature/losf
Review: https://review.openstack.org/648245"
1813725,2019-03-28 21:13:10 UTC,"Reviewed:  https://review.openstack.org/648245
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=6afc1130fd753306d64745c9bee7712182b273d3
Submitter: Zuul
Branch:    feature/losf"
1813725,2019-02-07 00:52:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/635380"
1813733,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1813733,2019-02-15 14:42:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813733,2019-03-06 10:49:37 UTC,This bug was fixed in the package linux - 4.18.0-16.17
1813733,2019-02-11 11:06:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1813733,2019-02-15 11:14:19 UTC,This bug was fixed in the package linux - 4.19.0-13.14
1813733,2019-01-29 09:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813741,2019-01-29 15:02:22 UTC,Bug fix proposed for merge.
1813744,2020-06-07 04:17:24 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1813745,2019-01-29 11:37:45 UTC,"If you see the grub menu on boot, just select an older kernel... but:"
1813745,2019-01-29 12:36:29 UTC,Same
1813745,2019-01-29 14:41:23 UTC,Done.
1813745,2019-01-29 14:44:10 UTC,I installed the 4.15.0-45 test kernel at https://people.canonical.com/~khfeng/lp1813663/
1813745,2019-01-29 15:39:43 UTC,"Per previous comments, I'm going to duplicate this report against bug 1813663. Thank you!"
1813745,2019-01-29 15:52:54 UTC,I can also confirm that the test kernel located at https://people.canonical.com/~khfeng/lp1813663/ fixed my issues as well.
1813745,2019-01-29 16:01:44 UTC,Upstream commit ID is be1c63c8017bb00a4
1813745,2019-01-31 14:50:59 UTC,"Kai,"
1813745,2019-02-03 14:14:10 UTC,"Hi Kai,"
1813745,2019-02-03 14:47:42 UTC,"Is it possible to boot under -45, reboot to -43, then attach output of `journalctl -b -1 -k`?"
1813745,2019-02-03 15:17:53 UTC,"4.15.0-45 does not fix my problem.  The boot continues to hang when gnome tries to start.  I cannot ""Ctrl-Alt-F1 (or any F?)"", but I can ssh from another computer to this affected computer.  Log files don't show anything remarkable to me, but I wouldn't know what was remarkable in all of the verbiage.  The boot process was working fine in the week of Jan 28 2019 through, oh say Jan 31."
1813745,2019-02-04 14:45:39 UTC,"Download the .deb files to an empty directory, then open terminal,
$ cd $(the directory)
$ sudo dpkg -i *deb"
1813745,2019-02-04 15:38:45 UTC,Stephane Guilard:
1813745,2019-01-29 11:16:59 UTC,"Download the .deb files to an empty directory, then open terminal,
$ cd $(the directory)
$ sudo dpkg -i *deb"
1813745,2019-02-03 10:04:44 UTC,Can you attach `dpkg -l | grep linux`? Maybe some packages are not correctly installed.
1813745,2019-01-29 11:01:48 UTC,"What is the procedure to test this kernel? (I normally get & install kernels through Ubuntu software update, and have never installed one from the shell)"
1813745,2019-01-29 10:11:47 UTC,apport information
1813745,2019-01-29 10:31:35 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1813663/"
1813745,2019-01-29 10:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813745,2019-01-29 10:11:41 UTC,apport information
1813745,2019-01-29 10:11:42 UTC,apport information
1813745,2019-01-29 10:11:43 UTC,apport information
1813745,2019-01-29 10:11:44 UTC,apport information
1813745,2019-01-29 10:11:45 UTC,apport information
1813745,2019-01-29 10:32:24 UTC,Should be the same as LP: #1813663.
1813745,2019-01-29 10:11:46 UTC,apport information
1813745,2019-01-29 10:11:49 UTC,apport information
1813745,2019-01-29 10:11:50 UTC,apport information
1813745,2019-01-29 10:11:51 UTC,apport information
1813745,2019-01-29 10:11:52 UTC,apport information
1813745,2019-01-29 10:11:53 UTC,apport information
1813745,2019-01-29 10:11:54 UTC,apport information
1813745,2019-01-29 10:23:18 UTC,"Note that all apport attachments above were done running 4.15.0-43 kernel and not the problematic 4.15.0-44, with which I cannot boot to login."
1813745,2019-01-29 10:11:48 UTC,apport information
1813749,2019-02-05 18:39:02 UTC,This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu27
1813749,2019-02-05 18:29:01 UTC,"The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813749,2019-01-29 11:32:30 UTC,"Hello Kleber, or anyone else affected,"
1813749,2019-01-29 10:51:16 UTC,Attaching patch based on ubuntu/xenial-devel branch.
1813749,2019-01-29 12:46:35 UTC,zfs-linux/0.6.5.6-0ubuntu27 ADT tests on linux-meta-snapdragon/4.4.0.1107.99 were successful:
1813751,2019-05-13 09:48:16 UTC,"Hi,"
1813751,2019-08-07 14:00:24 UTC,"Hey,"
1813751,2019-05-13 09:45:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813757,2019-01-29 12:23:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1813758,2020-04-18 20:44:49 UTC,"It has emerged that this problem is related to MATE, and is accordingly observed in all distributions that include MATE. I created a bug on Github:"
1813758,2020-04-26 10:22:45 UTC,"For Ukrainian and Russian fix released and sent to upstream.
See https://github.com/mate-desktop/libmatekbd/issues/55"
1813758,2020-04-26 18:25:03 UTC,I agree that the bug can be considered closed. But there are two questions:
1813758,2020-04-27 07:14:40 UTC,I m sorry. I forgot that full support for the Ukrainian language is not part of ISO.
1813758,2020-05-21 13:30:22 UTC,"So - the problem is solved, and the fix will get to Focal:"
1813759,2019-01-30 08:24:17 UTC,"Forgot the screen resolution, both displays use 3840x2160"
1813759,2019-07-22 03:58:58 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1813759,2019-01-29 13:26:24 UTC,"Thank you for your bug report, could you add your journalctl log after triggering the issue? What screen resolution do you use?"
1813759,2019-01-30 07:16:19 UTC,"You have the journalctl output first, when I disconnect the USB-C cable and then when I connect it back."
1813759,2019-01-30 09:15:52 UTC,"the log has this warning which might have to do with it
'setup_framebuffers: assertion 'width > 0' failed'"
1813767,2019-07-03 11:34:00 UTC,Proposed PR to fix the issue: https://github.com/juju/juju/pull/10419 - will need forward porting to 2.6 and then develop if successful.
1813767,2019-10-31 03:45:45 UTC,This work has landed in 2.7.
1813768,2019-11-28 06:11:52 UTC,"@peacecop the command for me was `hp-plugin`, maybe you can try that."
1813768,2020-09-30 09:25:21 UTC,"In all three cases of Ubuntu 18.04 and later 19.10 and also in Ubuntu 20.04 I solved this bug by clicking:
System → Synaptic Package Manager
Search for python-is
Uninstall python-is-python2
install python-is-python3"
1813768,2020-09-28 21:12:28 UTC,"I think that last comment by Rowland Barkley would solve my problem, but I don't understand his fix since I can't find ""python-is-python-2""
Help?"
1813768,2020-07-15 23:04:24 UTC,"I finally found a solution. I tried various version of HPLIP, and there were apparently completely different dependencies reported as missing, and that would not install."
1813768,2020-07-15 22:01:42 UTC,Ubuntu 18.04 . HPLIP 3.20.6
1813768,2020-06-21 16:45:59 UTC,Ubuntu 18.04 latest updates ... the above work around is not working for me. I get:
1813768,2020-06-16 08:09:02 UTC,Ubuntu  16.04  . HPLIP 3.20.5
1813768,2020-01-26 21:37:37 UTC,"I tried many workaround including these mentioned above.
I installed 19.10. yesterday though 3.19.12 just didn't work.
I installed 3.17.10 eventually."
1813768,2020-01-19 17:58:46 UTC,After Ra in Answer #8 with minor changes the below worked in Kubuntu 19.1
1813768,2019-12-26 22:45:24 UTC,"Having worked around for three days, finally I have figured out where the problem lay and I understood Brian's comment. Thank you!!"
1813768,2019-10-07 20:50:15 UTC,Thanks. I have been dealing with this problem for 3 days. This share helped me solve it .
1813768,2019-07-03 18:18:02 UTC,"The last suggestion didn't change anything better. And there's no command hplip-plgin nor hplip-plugin, it's hp-plugin which keeps complaining about the missing key."
1813768,2019-06-06 06:23:09 UTC,Install apparmor utils
1813768,2019-04-27 14:50:58 UTC,"Hi
After adding the gpg-key manually I installed apparmor-utils and then disable the profile like described above.
Now it works with HPLIB 3.19.3"
1813768,2019-04-25 18:47:47 UTC,"Berend,"
1813768,2019-04-22 00:11:18 UTC,Did you install apparmor when asked? I think that's where the problem is. Try disabling the apparmor profile: aa-disable /usr/share/hplip/plugin.py
1813768,2019-01-30 02:32:31 UTC,"Thanks, Brian!  I appreciate your help very much.  :)"
1813768,2019-01-29 14:52:40 UTC,"> ....I downloaded and renamed 3.17.11 plugin to 3.17.10
"
1813768,2019-01-29 14:20:06 UTC,"Thanks, Brian!  Yeah, I ended up using the hplip packages from 18 LTS."
1813768,2019-01-29 13:56:52 UTC,Also
1813768,2019-08-04 13:17:48 UTC,"Thank you so much Ra, that worked for me with hplip 3.19.6"
1813770,2020-09-09 17:19:28 UTC,This is actually already done (was changed as part of the upgrade to focal)
1813774,2019-11-08 10:30:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813778,2019-03-28 15:25:22 UTC,"I know of 3 different cases already where people have pushed to the wrong url and were not able to create MPs later on for their fixes. Launchpad would just say something along the lines of what you are proposing cannot be proposed for a merge, with no further info."
1813778,2019-01-29 15:09:00 UTC,Rationale: new contributors evidently find it difficult to figure out where to push. Hopefully this will help.
1813781,2019-02-01 11:14:22 UTC,"4.15.0-45.48~16.04.1 - lowlatency
Regression test CMPL, RTB."
1813781,2019-02-04 21:57:13 UTC,All tasks have been completed and the bug is being set to Fix Released
1813782,2019-02-05 20:54:15 UTC,moved from https://bugs.launchpad.net/yade/+bug/1813782 to https://gitlab.com/yade-dev/trunk/issues/12
1813782,2019-02-09 18:31:31 UTC,"In case if you don't get emails from gitlab I write here because it is fixed, see https://gitlab.com/yade-dev/trunk/issues/12"
1813783,2019-03-18 10:54:54 UTC,"Hi Kay-Heng, sorry for the delay, I'm currently on the road a lot."
1813783,2019-05-01 10:01:09 UTC,"This bug is still unresolved, however my touchpad started working after last update. I've tried the hotkeys again but cannot seem to toggle it."
1813783,2019-03-21 04:18:13 UTC,"I am afraid not. The basic idea is to find the correct scan code of the hotkey, and map it in systemd's hwdb."
1813783,2019-03-20 07:10:21 UTC,Try KEYBOARD_KEY_76=f21.
1813783,2019-03-19 10:47:12 UTC,"Yes, the error only appears when pressing Function button only."
1813783,2019-03-19 05:08:52 UTC,"So this shows when FN gets pressed, before F5?
[ 248.412826] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
[ 248.412833] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known."
1813783,2019-03-18 10:58:30 UTC,Results from running evtest:
1813783,2019-03-07 16:45:41 UTC,Something like:
1813783,2019-03-20 19:07:40 UTC,"I've tried, no success. Is there any more information I could provide?"
1813783,2019-03-07 10:16:18 UTC,"Reading through some documentation I've composed the following rules:
```
evdev:input:b0001v0001p0001eab83-customkeyboardnobrand
KEYBOARD_KEY_f5=f21
```"
1813783,2019-03-07 09:32:13 UTC,"Following the instructions of the file /lib/udev/hwdb.d/60-keyboard.hwdb I've created another file /etc/udev/hwdb.d/70-keyboard.hwdb.
From what I understand I need to place the configuration in there and reload the configuration.
I just would like to know under what segment I'd place this line? Or could I just place this at the bottom?
Also, the physical key I'm pressing is F5, I'm inclined to change the f8 to f5 in the configuration, would that be correct?"
1813783,2019-03-07 03:53:28 UTC,"For this case, the key will be ""KEYBOARD_KEY_f8=f21""."
1813783,2019-03-06 16:41:03 UTC,"You need something similar to [1].
But since your system is ""Standard"" everything, and upstream systemd hwdb would be impossible."
1813783,2019-03-06 12:18:02 UTC,"Hi Kai-Heng,"
1813783,2019-03-07 10:41:25 UTC,"Above did not work, I'm now trying to find the correct configuration. I'm fairly certain that I've found the keyboard info such as brand and all but that I need to format it correctly."
1813783,2019-03-06 11:22:59 UTC,Does your system have a model name?
1813783,2019-01-29 19:34:09 UTC,"As per request of lotuspsychje I updated my kernel from 43 -> 44.
This does NOT make a difference, bug still there."
1813783,2019-01-29 16:00:14 UTC,This change was made by a bot.
1813786,2020-05-02 16:24:37 UTC,"Reviewed:  https://review.opendev.org/722929
Committed: https://git.openstack.org/cgit/openstack/puppet-horizon/commit/?id=c399a6a5ce35e271492b92604e3a63ff161c1fe5
Submitter: Zuul
Branch:    stable/rocky"
1813786,2020-04-24 16:20:21 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/722930"
1813786,2019-05-27 16:39:19 UTC,"Reviewed:  https://review.opendev.org/633779
Committed: https://git.openstack.org/cgit/openstack/puppet-horizon/commit/?id=004142d577a1388244b19b2869797a4653b46bed
Submitter: Zuul
Branch:    master"
1813786,2019-06-06 06:43:00 UTC,This issue was fixed in the openstack/puppet-horizon 15.0.0 release.
1813786,2019-01-29 16:39:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633779"
1813786,2020-04-24 16:19:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/722929"
1813787,2020-11-16 14:57:25 UTC,"Reviewed:  https://review.opendev.org/757662
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=297f4c20c4c914f7fc8528e70d572adbeff68b0f
Submitter: Zuul
Branch:    stable/rocky"
1813787,2020-10-13 01:31:56 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/757662"
1813787,2020-05-26 20:36:04 UTC,"Reviewed:  https://review.opendev.org/728287
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0b9f4f275c681feb9dcbf4bef0ff29d5344f0fdc
Submitter: Zuul
Branch:    stable/rocky"
1813787,2020-05-21 05:40:50 UTC,"Reviewed:  https://review.opendev.org/728288
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=90496824c0253d2534f299ebcf5dc00774f70fe7
Submitter: Zuul
Branch:    stable/queens"
1813787,2020-05-14 20:38:03 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/728288"
1813787,2020-05-14 20:32:27 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/728287"
1813787,2019-05-26 03:21:38 UTC,"Reviewed:  https://review.opendev.org/660758
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fe4fc33f1c1bbb655e99733edf762e3e9debdd3e
Submitter: Zuul
Branch:    stable/stein"
1813787,2019-07-24 13:15:35 UTC,"Increase the bug level, because this issue has been submitted for a long time."
1813787,2019-04-26 10:44:55 UTC,"Reviewed:  https://review.opendev.org/654815
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9d60716cf1d61286a684f20ef8e05c77a0df5aa3
Submitter: Zuul
Branch:    master"
1813787,2019-04-23 07:38:20 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/654815"
1813787,2019-03-23 02:05:07 UTC,"Reviewed:  https://review.openstack.org/641490
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7369b69e2ef5b1b3c30b237885c2648c63f1dffb
Submitter: Zuul
Branch:    master"
1813787,2019-03-06 21:51:42 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641490"
1813787,2019-02-16 05:52:07 UTC,"Reviewed:  https://review.openstack.org/633869
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=837c9283abd4ccb56d5b4ad0eb1ca435cd2fdf3b
Submitter: Zuul
Branch:    master"
1813787,2019-01-30 06:00:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/633871"
1813787,2019-01-30 05:51:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/633869"
1813787,2019-01-29 21:37:58 UTC,"I think (1) and (2) will both help, with the provisioning block probably working in more cases perhaps."
1813787,2019-05-22 15:28:08 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/660758"
1813789,2020-03-19 16:48:37 UTC,"Reviewed:  https://review.opendev.org/713674
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b097959c1cbc9af1d90c7502286bc3e20972201f
Submitter: Zuul
Branch:    master"
1813789,2020-03-25 21:41:29 UTC,"Reviewed:  https://review.opendev.org/713962
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e7cd8b49e21852b5fafec7215d40e758cde92a35
Submitter: Zuul
Branch:    stable/stein"
1813789,2020-03-25 12:39:02 UTC,"Reviewed:  https://review.opendev.org/713961
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91d410b92f86524dffb781c7a49ecb3ec8ac8a56
Submitter: Zuul
Branch:    stable/train"
1813789,2020-03-19 18:43:48 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/713962"
1813789,2020-03-16 22:38:11 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/713342"
1813789,2020-03-19 18:42:57 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/713961"
1813789,2019-05-27 18:19:05 UTC,"Change abandoned by Artom Lifshitz (<email address hidden>) on branch: master
Review: https://review.opendev.org/639396
Reason: Abandoned, see commit message of [1] for explanation. Looks like we still need to wait in the virt driver, just not in all cases. Patch on top will be modified."
1813789,2019-03-20 14:47:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/644881"
1813789,2019-02-20 21:38:14 UTC,"We're hitting this in our internal CI, but for revert_resize instead of evacuate [1]. Same root cause though: by the time we've started listening to the event, it's already been received and discarded."
1813789,2019-02-26 17:38:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639396"
1813789,2019-02-20 21:50:45 UTC,FWIW we also have the same issue in unshelve:
1813789,2019-02-20 21:46:29 UTC,What's probably happening is we're getting the network-vif-plugged event due to the port binding change here:
1813789,2019-05-27 18:20:42 UTC,"Change abandoned by Artom Lifshitz (<email address hidden>) on branch: master
Review: https://review.opendev.org/639396"
1813790,2019-03-06 08:06:03 UTC,Fix committed in X1.3.1-30.
1813791,2019-01-29 17:14:24 UTC,Are they supported by HPLIP?
1813793,2020-10-13 17:09:54 UTC,"Similar comments apply to git.launchpad.net's host key to some extent, although at least it's 2048-bit."
1813793,2020-10-13 17:11:35 UTC,We should also offer at least one of the rsa-sha2-512 and rsa-sha2-256 host key algorithms rather than just ssh-rsa.  This doesn't require changing the host key itself.
1813793,2020-10-13 17:16:11 UTC,I believe that supporting rsa-sha2-* will require some work in Twisted; it appears that it only supports ssh-rsa for RSA keys today.
1813794,2019-10-31 03:25:33 UTC,Removing from a milestone as this work will not be done in 2.6 series.
1813794,2020-03-12 03:11:19 UTC,"Due to current priorities, I am not currently working on this bug, so I am un-assigning myself from it."
1813794,2019-02-19 02:01:02 UTC,This is a list of all the data that 'show-application' can display - https://pastebin.ubuntu.com/p/fdFHTJnrNz/.
1813794,2019-02-18 04:11:24 UTC,"@Richard Harding,"
1813794,2019-02-25 14:47:04 UTC,"Part of the goal is to put into one pane some of the things that's spread out that folks have to assemble data for. Personally, I'd like to include things like storage/resources details we can in this as a single overview."
1813799,2019-02-15 12:46:29 UTC,The objective here is to add support for a .jujuignore file format in charms that would not be deployed as part of the application.
1813799,2019-02-26 10:49:53 UTC,The current edge snap contains our proposal for addressing this issue by means of a .jujuignore file (uses same syntax as .gitignore files). For more information on the supported patterns please refer to the extended commit log here: https://github.com/juju/charm/pull/271/commits/2ed83967f1668fae235d9a4dbb610ee63532f735
1813799,2019-04-04 07:05:20 UTC,This fix was back-ported and released with 2.5.3
1813804,2019-02-01 00:44:47 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1813806,2019-01-30 15:13:54 UTC,"Here's a patch that moves the handler from a class variable to a method, which can be passed to the grid via markup.  No changes to the grid are required."
1813807,2019-03-20 16:45:33 UTC,This bug was fixed in the package ceph - 12.2.11-0ubuntu0.18.04.1
1813807,2019-03-20 16:45:48 UTC,"The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1813807,2019-03-21 09:27:26 UTC,xenial/queens-proposed
1813807,2019-03-21 09:30:28 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1813807,2019-05-29 05:21:22 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1813807,2019-05-20 08:28:42 UTC,"Hello James, or anyone else affected,"
1813807,2019-05-22 09:45:00 UTC,xenial/pike-proposed
1813807,2019-03-20 14:07:29 UTC,"$ juju status ceph-*
Model             Controller                  Cloud/Region             Version    SLA          Timestamp
bqueens-proposed  jamespage-serverstack-edge  serverstack/serverstack  2.6-beta1  unsupported  14:07:16Z"
1813807,2019-03-21 09:30:29 UTC,"This bug was fixed in the package ceph - 12.2.11-0ubuntu0.18.04.1~cloud0
---------------"
1813807,2019-03-20 14:07:05 UTC,bionic-proposed:
1813807,2019-05-29 05:21:24 UTC,"This bug was fixed in the package ceph - 12.2.11-0ubuntu0.17.10.1~cloud0
---------------"
1813807,2019-03-20 08:11:16 UTC,Tweaking the default domain ID to match the domain where testing users are created resolved the test failure for tempest.api.identity.admin.v3.test_domains.DefaultDomainTestJSON.test_default_domain_exists
1813807,2019-03-20 07:59:58 UTC,"That said I think we can configured the testing users better - they get created in the admin_domain, but the failing test is trying to get the defaults on the 'default' domain."
1813807,2019-03-20 07:57:28 UTC,Confirmed - I see exactly the same issue with proposed disabled.
1813807,2019-03-20 07:34:13 UTC,References:
1813807,2019-03-20 07:15:11 UTC,fair enough - digging into this failure today.
1813807,2019-03-19 18:10:07 UTC,I ask as I'm not familiar with the specific test and don't feel comfortable releasing the package with a test failure.
1813807,2019-03-19 18:09:27 UTC,Is the test that failed also failing with the version of ceph in -updates for Ubuntu 18.04?
1813807,2019-03-19 17:07:03 UTC,bionic/proposed test results:
1813807,2019-03-19 16:20:53 UTC,"Hello James, or anyone else affected,"
1813807,2019-02-27 22:55:11 UTC,"Hello James, or anyone else affected,"
1813807,2019-03-20 08:28:25 UTC,Re-running bionic-proposed testing with testing configuration changes.
1813812,2019-01-29 17:53:06 UTC,"When after discovering all available interfaces in find_fallback_nic() the nics are sorted in lexical order and then the first nic that has an address, i.e. /sys/class/net/$NIC_NAME/address has useful data is assumed to be the NIC to use for accessing the metadata server. However, this may not be true."
1813817,2019-02-22 20:24:58 UTC,These could be related as well:
1813817,2019-01-30 19:13:54 UTC,You mentioned that it is trying to migrate from the same source to the same target. So we are just removing and adding it to the same node?
1813817,2019-01-30 19:23:10 UTC,"Sorry, that should have been more clear. The source and target are 2 different hosts, but all VM's are being moved to the same place."
1813819,2019-01-29 19:57:36 UTC,apport information
1813819,2019-02-18 23:10:35 UTC,"Given the amazing product support, I decided to completely give up and re install the entire OS. That was an astonishing support for an LTS product ... For people who have a similar issue here are the things that does not work so don't waste time one:
- rebooting
- rapidly updating the system time
- use a different time package
- adjust the CPU frequency
- switch different CPU modes
- removing/reinstalling/purging:
 - chrome
 - xinput
 - xorg
 - xserver
 - I/O drivers
 - display drivers
 - sd drivers
 - network drivers
 - optical  drivers
 - power management tools
 - browsers
- recovery mode
- rolling back"
1813819,2019-02-18 09:19:05 UTC,The only thing I observed in the dmesg is that the Realtek card reader keeps dropped off the USB bus.
1813819,2019-01-29 20:49:36 UTC,"New update:
- network connection is affected too, wifi keeps dropping out"
1813819,2019-01-29 20:42:28 UTC,"New update:
- When using arrow keys, the keyboard random spews out num key values of the arrows as if the button is stuck even when number lock is off. All I have to to replicate this bug is to hold arrow key down
- Putting the laptop into sleep and waking it up, seem to reduce the clock speed effect until it reboots again. (it made the computer usable enough for me to take the bug report and start pushing my files to repos)"
1813819,2019-01-29 19:57:47 UTC,apport information
1813819,2019-01-29 19:57:39 UTC,apport information
1813819,2019-01-29 19:57:37 UTC,apport information
1813819,2019-01-29 19:57:33 UTC,apport information
1813819,2019-01-29 19:57:34 UTC,apport information
1813819,2019-01-29 19:57:22 UTC,apport information
1813819,2019-01-29 19:57:31 UTC,apport information
1813819,2019-01-29 19:57:30 UTC,apport information
1813819,2019-01-29 19:57:29 UTC,apport information
1813819,2019-01-29 19:57:28 UTC,apport information
1813819,2019-01-29 19:57:26 UTC,apport information
1813819,2019-01-29 19:57:25 UTC,apport information
1813819,2019-01-29 19:57:23 UTC,apport information
1813819,2019-01-29 19:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813819,2019-01-29 19:57:32 UTC,apport information
1813820,2019-03-14 05:23:50 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu"
1813820,2019-01-31 00:42:27 UTC,"$ uname -a
Linux craig-Predator-PH517-61 5.0.0-050000rc4-generic #201901272036 SMP Mon Jan 28 01:38:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1813820,2019-02-18 21:04:28 UTC,"took the following steps:
Went to https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
Downloaded the master branch which was uploaded 5 days ago by Josh Boyer
Backup my current firmware: sudo cp -r /lib/firmware /lib/firmware-$(uname -r)
tar -xvzf linux-firmware-master.tar.gz
CD into the resulting directory
sudo make install
mkdir -p /lib/firmware
sudo cp -r * /lib/firmware
sudo find /lib/firmware \( -name 'WHENCE' -or -name 'LICENSE.*' -or         -name 'LICENCE.*' \) -exec rm -- {} \;"
1813820,2019-02-18 08:51:44 UTC,"It's a Vega 10 graphics, so please also test AMDGPU firmware in linux-firmwares [1]."
1813820,2019-03-14 05:24:08 UTC,Also please attach `journalctl -b -1 -k`.
1813820,2019-03-14 03:37:41 UTC,"today tried another new kernel with the same result, still the screen produces garbage after resuming from suspend. This was the kernel used: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.2/"
1813820,2019-03-15 02:49:24 UTC,here is the output of 'journalctl -b -1 -k'
1813820,2019-04-14 03:54:16 UTC,tested the kernel from here today with the same result: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc4/
1813820,2019-03-16 14:15:30 UTC,ok produced this with the correct steps this time
1813820,2019-03-18 08:27:15 UTC,"I don't see any error after the resume. The system is apparently alive, so it's more likely to ba graphics driver issue."
1813820,2019-03-18 12:01:02 UTC,Reported here: https://bugs.freedesktop.org/show_bug.cgi?id=110117
1813820,2019-04-29 01:51:56 UTC,if by chance this is an Acer UEFI bug is there somewhere else I could report it? either in launchpad or upstream?
1813820,2019-05-11 15:01:16 UTC,today I started to follow the steps here: https://wiki.ubuntu.com/DebuggingKernelSuspend
1813820,2020-04-12 22:56:22 UTC,Similar issues on the HP Envy 13 x360 (Ryzen 3500U)
1813820,2019-03-15 03:45:46 UTC,"Sorry I didn't make it explicit - please reproduce the issue, reboot, then attach 'journalctl -b -1 -k'."
1813820,2019-01-30 03:18:59 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc4 kernel[0]."
1813820,2019-01-30 02:23:34 UTC,apport information
1813820,2019-01-30 02:23:53 UTC,apport information
1813820,2019-01-29 18:47:57 UTC,"Expected Behaviour:
I expect to continue to be able to use my machine normally and be able to see what is happening on screen."
1813820,2019-01-30 02:23:55 UTC,apport information
1813820,2019-01-30 02:23:29 UTC,apport information
1813820,2019-01-30 02:23:30 UTC,apport information
1813820,2019-01-30 02:23:32 UTC,apport information
1813820,2019-01-30 02:23:36 UTC,apport information
1813820,2019-01-30 02:23:37 UTC,apport information
1813820,2019-01-29 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813820,2019-01-30 02:23:40 UTC,apport information
1813820,2019-01-30 02:23:42 UTC,apport information
1813820,2019-01-30 02:23:44 UTC,apport information
1813820,2019-01-30 02:23:45 UTC,apport information
1813820,2019-01-30 02:23:48 UTC,apport information
1813820,2019-01-30 02:23:49 UTC,apport information
1813820,2019-01-30 02:23:39 UTC,apport information
1813824,2019-01-29 20:50:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813825,2019-03-14 06:20:34 UTC,"If I can expand upon duplex printing I have encountered an issue in the control centre 18.10 too.
When enabling duplex in gnome-control-center it does not work,"
1813825,2019-03-14 15:13:37 UTC,"@Clint, that seems another issue, could you maybe open a new bug about that one?"
1813825,2019-03-02 13:09:38 UTC,"I deleted all printers and waited for CUPS / driverless to find them again.
Here a few CLI outputs (which are small enough so I dare to spost them inline )"
1813825,2019-03-20 15:26:38 UTC,"Christian, first, it seems that you did ""cupstestppd"" on a PPD file which is not auto-generated:"
1813825,2019-03-22 13:47:00 UTC,Exactly:
1813825,2019-03-20 15:52:03 UTC,"I think the problem here is CUPS' own method of generating temporary queues for discovered driverless printers. gnome-control-center, and probably other GUIs, like the GTK print dialog, cannot cope with this. So we leave this bug report assigned to gnome-control-center for now."
1813825,2019-03-22 13:43:52 UTC,"First, here the new attrs.txt"
1813825,2019-03-22 16:03:35 UTC,This temporary queue (Kyocera_ECOSYS_P6026cdn) is actually not needed here. Therefore I have reported this upstream issue on CUPS:
1813825,2019-03-20 15:33:32 UTC,"Christian, both your attached PPD files are auto-generated, and both pass cupstestppd."
1813825,2019-03-02 12:23:55 UTC,"Second file. The printer is added automatically twice. Maybe this is because the printer has a print server, which exports the printer again and announces it to the network? KM15881D.local is the network name of the printer."
1813825,2019-01-30 16:31:47 UTC,"First, driverless printers (automatically created queues for IPP printers) can be generated by cups-browsed and by CUPS."
1813825,2019-02-20 09:31:33 UTC,one shouldn't make promises. Follows ASAP. Give me a few days.
1813825,2019-03-02 12:22:05 UTC,"This file is named .0 because I have the printer installed with a custom ppd file (from kyocera) manually - with the same name, so I think cups adds the .0 automatically."
1813825,2019-01-29 22:50:46 UTC,"Thank you for your bug report. Could you attach your journalctl log from a boot where you triggered the issues described?
Could you also add your logs from /var/log/cups?"
1813825,2019-01-30 08:09:51 UTC,"I'm sorry to write ""more than"" one problems into one bug, but from a users POV they are all the same - seen as ""usability"" bug. If you tell mo more how I can help, I can also file separate ones if this is needed. But to gather information, maybe it's best to leave it ATM as one?
Logs attached, irrelevant parts snipped."
1813825,2019-01-30 09:08:31 UTC,"Thanks for the info, the logs don't have much though :/"
1813825,2019-01-29 19:57:43 UTC,"Additionally, since ""driverless"" printing, I always have a printer named ""print"" in my printing dialog, which I can't print to, and can't delete neither. Print jobs are denied at any time there."
1813825,2019-01-30 13:19:05 UTC,It seems you used gdb just right yes.
1813825,2019-01-30 09:55:55 UTC,"Ok; I never used gdb before, just visual debuggers.
I'm not sure this is not a blind alley. The ""gtk_container_add warning"" is not reproducible and has IMHO nothing to do with this bug(s) (just IMHO)."
1813825,2019-02-19 15:30:37 UTC,"Christian, where is the rest which you wanted to post the day after Jan 30?"
1813825,2019-01-30 20:41:47 UTC,"First small thing: stopping cups-browsed dowsn't change anything. Even when stopped, deleting a driverless printer lets it popup again after a few seconds.
Rest tomorrow."
1813826,2019-03-18 12:36:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813826,2021-02-23 02:29:01 UTC,"Hello,
4.18 kernel is not supported anymore, thus I am closing it here.
Please feel free to open a new bug if you're seeing any issue.
Thanks"
1813835,2019-03-20 21:26:50 UTC,"That's odd. Let's dig in deeper, as it quite likely might be a systemd bug, but I rather be certain it's not us doing something wrong."
1813835,2019-05-20 04:17:35 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1813835,2019-05-20 04:17:36 UTC,[Expired for netplan because there has been no activity for 60 days.]
1813835,2019-05-20 04:17:37 UTC,[Expired for netplan.io (Ubuntu) because there has been no activity for 60 days.]
1813842,2019-01-30 06:19:15 UTC,"rae@rae-W540:~$ rae@rae-W540:~$ sudo ubuntu-bug
/var/crash/linux-image-4.15.0-44-generic.232084.crash
rae@rae-W540:~$: command not found"
1813842,2019-02-07 14:02:12 UTC,"Hello,"
1813847,2019-01-30 16:51:02 UTC,"I'm not sure this really is a stress-ng issue, the purpose of stress-ng is to force out kernel problems like this. Isn't this a kernel issue instead?"
1813847,2019-01-30 18:51:57 UTC,"I can see that argument, and also an argument that this isn't a bug at all. That is, the kernel is telling us something strange is happening, but ""something strange"" is stress-ng's middle name :) That said, these errors combined with a later (and now known to be unrelated) kernel Oops caused me to dig into it. It would be nice if we could somehow prevent this from raising hackles for other users."
1813847,2019-01-30 21:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813847,2019-03-21 09:48:38 UTC,Fix committed: https://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=a4e26439837ce6e472b502da430ff863f6c7c265
1813849,2019-04-28 14:52:59 UTC,"Hi,"
1813851,2019-09-27 09:04:10 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1813851,2019-01-30 02:36:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633861"
1813851,2019-06-27 07:43:50 UTC,"Reviewed:  https://review.opendev.org/633861
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d960cb0477c3e782463632c94d888bcd121083da
Submitter: Zuul
Branch:    master"
1813853,2019-01-30 02:02:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813853,2020-09-07 04:11:31 UTC,No crash reports after 18.10.
1813855,2019-01-30 02:09:39 UTC,"StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? () from /tmp/apport_sandbox_x6yxjuuc/lib/x86_64-linux-gnu/libc.so.6"
1813855,2019-02-17 15:12:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813856,2019-09-12 13:59:38 UTC,"It looks like your ironic node has booted from the inspector dnsmasq server, instead of neutron. It has posted back to ironic inspector."
1813856,2019-11-12 04:18:04 UTC,[Expired for kolla because there has been no activity for 60 days.]
1813857,2020-07-29 10:38:29 UTC,"In this cycle it's now being tested.
I will close this bug."
1813860,2020-01-28 09:04:35 UTC,"We have finally uncapped pip again, so this should be fixed."
1813860,2019-02-04 22:03:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634822"
1813860,2019-02-08 10:21:39 UTC,"Change abandoned by Arun S A G (<email address hidden>) on branch: master
Review: https://review.openstack.org/634822
Reason: Abandoning in favor of https://review.openstack.org/#/c/561597/9"
1813860,2019-01-30 21:50:56 UTC,Please note that upstream CI is likely hiding this issue due to this line in the fix_stuff.sh script:
1813863,2019-01-30 04:30:07 UTC,This change was made by a bot.
1813863,2019-01-30 07:38:05 UTC,"dmesg output for ""mkfs.btrfs -f $DEV0"""
1813867,2019-01-30 15:06:59 UTC,https://github.com/juju/juju/pull/9616 is a PR against 2.5.1 that should deal with this.
1813868,2019-02-01 06:49:20 UTC,https://github.com/juju/juju/pull/9701 is a patch against 2.5. We may go for 2.5.1 or we may delay for 2.5.2
1813869,2019-03-04 12:39:14 UTC,"@Siva,"
1813869,2019-03-15 15:34:40 UTC,This bug was fixed in the package linux - 4.4.0-143.169
1813869,2019-03-04 11:57:37 UTC,"@Ganapathi,"
1813869,2019-02-12 13:36:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1813869,2019-03-01 01:10:41 UTC,Final reminder: We are at the end of the SRU Cycle and request that you please provide verification the kernel in proposed resolves the problem for which this bug was submitted.  -Thank you!
1813869,2019-01-30 05:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813869,2019-03-04 10:29:27 UTC,"Hi All,"
1813873,2019-02-19 00:36:20 UTC,Confirming the login loop bug for 16.04.5 LTS with 4.4.0-142-generic
1813873,2019-02-20 06:53:59 UTC,Also seen on AskUbuntu - https://askubuntu.com/q/1113704/66509 - with 16.04 LTS and 18.04 LTS.
1813873,2019-02-25 09:29:25 UTC,"Are we going to see a release on this soon?
Nearly a month for a userspace impacting regression :("
1813873,2019-02-26 08:19:03 UTC,I tested 4.15.0-46 from bionic-proposed. I can confirm that it is working for Ubuntu 18.04.
1813873,2019-02-26 08:26:16 UTC,I tested the kernel 4.15.0-46 from bionic/proposed. I confirm that it fix the problem for Ubuntu 18.04
1813873,2019-02-26 09:28:45 UTC,I tested the kernel 4.4.0-143 from xenial-proposed on 16.04 and from trusty-proposed on 14.04 and it fix the problem for these 2 releases.
1813873,2019-02-26 11:16:24 UTC,Thanks all for the tests.
1813873,2019-02-27 06:09:36 UTC,"Considering that this is a regression, with major impact (TTY login no longer possible, often no graphical login either), many affected users on (amongst other) the latest LTS release, and both this fact and how to fix it has been known since at least January 30, I am puzzled as to why this is being handled as an update with the default stable release cadence."
1813873,2019-05-06 18:04:01 UTC,"Hi Chris, as per comment #21, the issue exists in kernel 4.18.0-14, and was fixed in 4.18.0-15.
So, you need to update your kernel."
1813873,2019-02-27 06:24:42 UTC,"Thanks for the link Guilherme, guess that answers that question.
Given March 4 is just round the corner, I am not sure there is much can be done at this point, but I will however just echo what Tom beat me to saying:"
1813873,2019-03-05 08:13:10 UTC,Am I wrong or the fix hasn't yet been released?
1813873,2019-03-05 08:29:46 UTC,"Hey Andrea,"
1813873,2019-03-05 08:41:54 UTC,I'm located in solar > earth > europe but still waiting for the -update version of xenial too (@_@)
1813873,2019-03-05 13:13:49 UTC,Update?
1813873,2019-03-05 15:20:29 UTC,still available only in Proposed though
1813873,2019-03-05 22:51:09 UTC,I just made right now the update on my ubuntu 18.02 and got the new 4.15.0-46-generic kernel. The bug is fixed to me. Thanks all
1813873,2019-03-05 23:04:52 UTC,"My system updated today, and I can confirm that the issue for login to
the shell seems to have gone away. tnx."
1813873,2019-03-06 06:37:25 UTC,In xenial with hwe stack I got 4.15.0-46-generic now also and the bug is gone.
1813873,2019-03-06 08:00:20 UTC,"Regarding Ubuntu 16.04's ""xenial"" GA kernel (4.4), I've been told that the Kernel team ran into some issues with these and are now planning to release them next week. As Brandon discussed, installing the 4.15 hardware enablement (HWE) kernel - as documented at https://wiki.ubuntu.com/Kernel/LTSEnablementStack - works around this bug, too."
1813873,2019-03-06 08:22:06 UTC,"I was forced to install the LTSEnablementStack because with the regular 4.4.0 kernel, suddenly with an update, a certain combination of docking/undocking my laptop led to a system freeze. Newer kernels (4.8 back then) did not have the problem, also I could name the 4.4.0 kernel image that also ran fine. Even though I put an impressive amount of working hours (40h+) into pinpointing the problem by doing kernel bisecting, this still not enough. At some time, I just installed the LTSEnablementStack to get regular updates of the 4.8 and I could get back to work."
1813873,2019-03-06 08:59:43 UTC,"Confirming fix, login working again on bionic. Thanks for your work."
1813873,2019-03-06 09:12:48 UTC,"fix confirmed, thanks"
1813873,2019-03-06 10:27:34 UTC,"Yes, the fix seems to have saved us. Confirmed, with kernel 4.15.0-46-generic, an Ubuntu 18.04 update on 4th of March."
1813873,2019-03-07 18:01:21 UTC,"Will the fix for 16.04 32 bit be available through normal channels in the near future?
Thank you."
1813873,2019-03-15 15:34:40 UTC,This bug was fixed in the package linux - 4.4.0-143.169
1813873,2019-05-02 17:11:34 UTC,"I'm on Kernal version
more /proc/version
Linux version 4.18.0-14-generic (buildd@lcy01-amd64-026) (gcc version 7.3.0 (Ubu
ntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Mon Jan 14 11:09:26 UTC 2019"
1813873,2019-05-03 01:27:53 UTC,"Chris (~iplayfast): You're not running the latest HWE kernel image:
  linux-image-generic-hwe-18.04 | 4.18.0.18.68 | bionic-updates"
1813873,2019-02-18 14:27:57 UTC,"Confirming the login loop bug for 18.04.2 with 4.15.0-45-generic
And also confirming the fix in proposed with 4.15.0-46-generic"
1813873,2019-03-05 15:00:44 UTC,This bug was fixed in the package linux - 4.15.0-46.49
1813873,2019-02-18 14:05:18 UTC,"Hi Edgar, I've changed it back =)
It should be Fix Committed if the patch is present/merged in the kernel, but kernel wasn't released yet. Once it gets released, it'll get changed to Fix Released."
1813873,2019-02-14 10:17:36 UTC,"Hi Guilherme,"
1813873,2019-02-17 20:51:43 UTC,"I think I may have run into another issue related to the same bug. While the login loop problem appears to have been fixed, the fix does not seem to have cascaded down to other prompts that one may encounter in special circumstances. In my case, I had an external USB drive connected to my server and this happened to have been powered off (physically) when booting. As expected, the system did not complete the boot process and stopped (momentarily) at the ""Enter Ctrl-D etc"" prompt to allow repair. Well, it just kept going. I was unable to get in at all and eventually just had to physically reset the box and reconnect power to the USB drive. So the looping that used to happen at the console login persists when dropping to the emergency shell. I will be grateful if anyone else can confirm. Just add a spurious entry to fstab and try to reboot."
1813873,2019-01-30 07:00:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813873,2019-01-30 09:37:27 UTC,See https://marc.info/?t=154883032500001&r=1&w=2 for LKML discussion and replies.
1813873,2019-01-30 14:56:13 UTC,We will pick the follow-up patch up for the next cycle.
1813873,2019-02-18 13:23:08 UTC,"Hello, I mistakenly change the status of Bionic to Fix released, I didn't know that I could change something like this since I'm not a maitainer of some sort, I'm just an end user. I tried to cancel the change but I don't have the right to do so."
1813873,2019-02-10 13:04:31 UTC,"Hi,"
1813873,2019-02-10 23:28:27 UTC,"Hi Joe, can you please paste the output of ""uname -a"" from your system that is presenting this issue?"
1813873,2019-02-10 23:43:28 UTC,"No package containing the fix for 18.04 has been released yet, only 18.10.
It is therefore expected that 18.04.X still displays the issue."
1813873,2019-02-10 23:56:13 UTC,I am running 18.04 with linux-image-generic-hwe-18.04 installed. I can confirm that the issue has been resolved with the latest kernel which is 4.18.0-15-generic.
1813873,2019-02-11 10:05:46 UTC,"Great, thanks Rehan!"
1813873,2019-02-12 13:36:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1813873,2019-02-13 10:16:59 UTC,"I tried xenial-proposed, but the fix doesn't seem to be available yet. It's still pulling 4.15.0 from xenial-updates (and that one still has the problem)."
1813873,2019-02-13 10:43:52 UTC,"Putatieve,"
1813873,2019-02-13 10:51:42 UTC,"I most definitly do have linux-generic-hwe-16.04 installed. I installed linux-generic to test if xenial-proposed was properly configured, as 'apt-get install -t xenial-proposed linux-genric-hwe-16.04' didn't install anything."
1813873,2019-02-08 10:53:46 UTC,This bug was fixed in the package linux - 4.18.0-15.16
1813873,2019-02-13 10:52:53 UTC,And I am running ubuntu 16.04
1813873,2019-02-13 10:52:18 UTC,PS: linux-genric-hwe-16.04 is a typo in this post
1813873,2019-02-16 12:56:45 UTC,"The kernel in -proposed solves the problem, I've tested it !"
1813873,2019-02-15 12:18:21 UTC,Error seems to be fixed. I have made the following solution:
1813873,2019-02-14 14:43:28 UTC,"I enabled proposed, did an apt-get update, it got the index file:"
1813873,2019-02-14 12:11:09 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813873,2019-02-14 11:12:15 UTC,"Samuel, for now the suggestion is to keep kernel 4.15.0-43, as it doesn't show the issue reported in this LP."
1813873,2019-02-13 15:00:47 UTC,I'm under unbuntu 16.04 kernel 4.4.0 and the xenial-proposed solved problem reading /dev/tty for me
1813873,2019-02-14 10:48:58 UTC,"You're welcome Putatieve, thanks for testing the Xenial 4.4.0-143 version!"
1813873,2019-02-14 10:46:48 UTC,Hi all.
1813873,2019-02-13 17:47:11 UTC,"Hi Putatieve, thanks for you attention here. Let me try to clarify what happens here: the issue is present in kernel 4.4.0-142, 4.15.0-45 and 4.18.0-14. The three versions were already released,
but the fix for the regression observed in this LP is present in the new versions that are getting released in this cycle."
1813873,2019-02-13 17:27:17 UTC,"Of course, the bug/regression only appeared in 4.15.0-45 (4.15.0-43 is fine)."
1813873,2019-02-13 11:54:10 UTC,"You don't seem to understand what I said: I DO HAVE 4.15.0 installed (linux-generic-hwe-16.04):
https://packages.ubuntu.com/search?keywords=linux-generic-hwe-16.04&searchon=names&suite=xenial-updates&section=all"
1813873,2019-02-14 10:58:10 UTC,"On Thu 2019-02-14 (10:46), SAMUEL TEIXEIRA SANTOS wrote:"
1813873,2019-02-13 11:32:54 UTC,"Right, the fixed kernel mentioned in -proposed is NOT the 4.15 HWE kernel, it's the 4.4.0 kernel."
1813877,2020-01-06 22:31:20 UTC,This bug was fixed in the package linux - 5.4.0-9.12
1813877,2020-01-06 13:26:17 UTC,This bug was fixed in the package linux - 4.15.0-74.84
1813877,2020-01-06 13:12:44 UTC,This bug was fixed in the package linux - 5.0.0-38.41
1813877,2019-12-05 11:27:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1813877,2020-01-06 12:53:38 UTC,This bug was fixed in the package linux - 5.3.0-26.28
1813877,2019-12-03 13:02:04 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34
1813877,2019-12-02 13:36:15 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34
1813877,2019-11-25 11:41:18 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1813877,2019-11-12 22:31:28 UTC,This bug was fixed in the package linux-oem - 4.15.0-1063.72
1813877,2019-12-03 15:43:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1813877,2019-12-03 13:01:06 UTC,This bug was fixed in the package linux-oem - 4.15.0-1065.75
1813878,2019-10-18 07:17:54 UTC,"This one failed on T-4.15-azure as well:
 FAIL: lxc-tests: /usr/bin/lxc-test-containertests
 ---
 161: lxc_conf is not NULL as it should be"
1813878,2019-10-18 07:21:10 UTC,"Failure for azure : 4.15.0-1061.66~14.04.1 in this cycle, the error message is a bit different."
1813878,2020-11-24 10:15:47 UTC,Still failing 4.15.0-1100.111~14.04.1 - azure
1813880,2019-01-30 09:05:41 UTC,"Or make just one dialog which can be configured with toolbar buttons. There could be two main modes, tree view and two column view. The two column view could have filters for both columns individually."
1813880,2019-05-21 23:11:27 UTC,"My option is that the two column dialog is quick to navigate and use better the widescreen rate aspect of current displays.
The filter in this case could show all the found parts/footprints at the second column and in the first, show only the categories that have the founded parts/footprints. This will allow the user to filter the category filter change the filter and appear better to navigate in the long libraries of KiCad."
1813883,2019-01-30 09:33:04 UTC,Found on Xenial 4.15 as well. So this is something we might need to fix in the generic kernel.
1813883,2019-01-30 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1813883,2019-08-30 06:08:51 UTC,"Didn't see this issue for 4.15.0-60.67~16.04.1
Mark this as fix-released."
1813886,2019-01-30 08:38:24 UTC,"juju destroy-model hangs, and there is no --force option, so cleanup requires destroying the controller."
1813886,2019-01-30 09:05:27 UTC,"(manual destruction of the controller, since destroy-controller --destroy-all-models also hangs and also has no --force option)"
1813886,2019-01-30 11:09:51 UTC,I can reproduce this.
1813886,2019-01-30 09:17:04 UTC,"Do you know what 'juju offers' run on hte offering model printed?
This will show if Juju thinks there are any consumers still using the offer."
1813886,2019-05-24 14:30:40 UTC,I ran into this 'in the wild' in that I was attempting to add a unit that failed. Had I waited to consume the offer until after the provisioning was finished it may have been ok.
1813886,2019-05-23 17:10:31 UTC,"juju destroy-model and juju destroy-model --force also hang, waiting on the wedged application."
1813886,2019-05-23 17:09:54 UTC,"juju destroy-model and juju destroy-model also hang, waiting on the wedged application"
1813886,2019-06-26 03:10:44 UTC,"The fix[0] for this bug has passed code review. It is should be part of the 2.6.5 release, which is expected to land early next week[1]."
1813886,2019-01-31 10:14:01 UTC,I can confirm that the offer can be removed after the pod has been spun up.
1813886,2019-01-31 07:07:27 UTC,Discussed in IRC - it appears that the issue arises when the offering (k8s) charm has not fully come up yet and initialised its pod info. This looks like it falls into the existing class of problem where Juju is not good at removing apps/relations/units etc if there's an underlying error or the charm hasn't started running hooks yet.
1813886,2019-01-31 00:07:11 UTC,"I tried to reproduce in a similar way using these charms (also using a LXD controller and microk8s):
- deploy mariadb-k8s charm to k8s model and offer it
- deploy mediawiki to IAAS model and consume the k8s offer"
1813886,2019-05-23 17:07:25 UTC,This is also happening with Juju 2.6.2 (currently targetted to 2.5.8).
1813889,2019-01-30 14:36:08 UTC,I added the error message
1813889,2019-05-27 07:17:00 UTC,"I thought this was a Tilda issue, but also Guake has this problem."
1813889,2019-06-20 12:21:58 UTC,Also happens in 19.10
1813893,2019-02-12 20:15:21 UTC,"Thank you for your bug report, that's known upstream
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/1"
1813893,2019-07-10 12:36:48 UTC,any update on this? or maybe a workaround?
1813893,2019-07-10 19:09:28 UTC,"No update or the bug would have some activity, upstream is probably a better place to discuss such changes though"
1813897,2019-03-07 05:24:16 UTC,Bug-1818885- In my case after booting the iso there was no GUI. Only after installing the intel driver was i able to login into the desktop.
1813897,2019-01-30 09:40:30 UTC,"StacktraceTop:
 raise () from /tmp/apport_sandbox_cjq0na66/lib/x86_64-linux-gnu/libc.so.6
 abort () from /tmp/apport_sandbox_cjq0na66/lib/x86_64-linux-gnu/libc.so.6
 OsAbort () at ../../../../os/utils.c:1350
 AbortServer () at ../../../../os/log.c:879
 FatalError (f=f@entry=0x5581752e8208 ""AddScreen/ScreenInit failed for driver %d\n"") at ../../../../os/log.c:1017"
1813897,2019-01-30 10:00:45 UTC,I'm guessing this crash is just a consequence of the LVDS issue mentioned in bug 1812359.
1813897,2019-03-06 17:55:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813899,2019-01-30 09:36:59 UTC,Reproduce rate 3 out of 3 attempts.
1813899,2019-01-30 10:01:52 UTC,"Do we have any more logs of the run, e.g. kernel messages etc?"
1813899,2019-01-30 10:54:43 UTC,Sorry I can't get that without access to the node.
1813899,2019-01-30 11:43:53 UTC,Added some extra debug and some more sanity checking. Looks like on a single CPU the pthread reaping was not unlocking a mutex causing the issue.
1813903,2019-01-30 10:16:16 UTC,Here is the suggested patch
1813903,2019-01-30 10:35:45 UTC,"thx!
 I suspect we have two possible courses of action:
 1) place the patch into our kernel build tree now
   - possibly as part of that 4.19 PR
 2) wait until the CVE is fixed in 4.19.x, and update the PR to match a fixed kernel"
1813903,2019-01-30 10:44:43 UTC,Agree.
1813903,2019-01-30 11:37:55 UTC,"thx Xu. Relevant github posting is at:
https://github.com/kata-containers/runtime/pull/1111#pullrequestreview-198010809"
1813909,2020-02-26 11:45:42 UTC,"Hi Liviu,"
1813909,2020-02-26 11:57:06 UTC,"Great, thank you."
1813913,2019-03-19 13:31:08 UTC,Is this still an issue?
1813913,2019-08-20 13:27:14 UTC,fedoora28 is removed and replaced with rhel 8
1813913,2019-01-30 10:45:55 UTC,"This job is in experimental state, it's destined to fail for some time, until we have a clear understanding of how to build containers in fedora, and they are actually building correctly."
1813913,2019-01-31 10:06:05 UTC, https://review.openstack.org/634109 to fix ResourceWarning: unclosed file <_io.TextIOWrapper name='/home/zuul/./hieradata-overrides-t-h-t-undercloud.yaml' mode='r' encoding='UTF-8'>
1813914,2019-01-30 11:05:38 UTC,Opened a discussion thread at https://forum.snapcraft.io/t/fail-to-verify-tls-certificates/9738
1813914,2019-01-30 11:06:35 UTC,Bug related to https://bugs.launchpad.net/graylog-charm/+bug/1794505
1813916,2019-03-04 11:41:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813916,2019-11-28 14:25:14 UTC,"This seems to be fixed now in 19.10, though the command is unmodified"
1813919,2019-03-04 11:40:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1813925,2019-01-30 11:52:30 UTC,"Note, I was testing snapcraft against older yaml files I'd made which worked before. I did not add a ""base"" specifier or anything"
1813928,2019-01-30 12:30:06 UTC,This change was made by a bot.
1813928,2019-01-31 03:35:11 UTC,"Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed."
1813928,2019-05-22 19:11:55 UTC,"This LP is a duplicate for #1824981 - I'll mark it as dup.
Thanks,"
1813931,2019-07-19 12:27:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671713"
1813931,2019-07-03 23:22:26 UTC,Working on this.
1813931,2019-07-19 20:48:48 UTC,"Reviewed:  https://review.opendev.org/671713
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=52af8d8d6df42097eba8d282d704b8e86fc7d8a5
Submitter: Zuul
Branch:    master"
1813931,2019-05-15 13:43:11 UTC,"Thanks, we have faced this issue as our current deployment use DVR and L3HA, effectively the `configure-resources` effectively create a set of resources which are not able to work with our current Neutron setup, e.g. creating a lb you can see the instances spin-up but the health monitor is unable to communicate with them."
1813931,2019-06-25 12:01:43 UTC,Are you guys working on this? I was wondering if there is scheduled a fix for DVR deployments.
1813931,2019-07-19 15:51:48 UTC,"As pointed to in the fix referenced in comment #5, the Octavia charm side of this issue was the use of an arbitrary string in the ``device_owner`` field of the ports created.  When enabling DVR, Neutron uses this field multiple places in the code to determine how to handle traffic."
1813931,2019-01-31 06:21:44 UTC,A note for passers by while we figure out the root cause to this.
1813937,2019-01-30 16:13:57 UTC,"Thanks, that's somewhat a similar discussion to https://bugzilla.gnome.org/show_bug.cgi?id=719919 but it seems upstream isn't considering providing that feature back"
1813938,2019-01-30 17:53:15 UTC,From your paste:
1813938,2019-01-30 19:03:18 UTC,"I dont known if is this, but, in the past the openstackneutron package is working (another old version)"
1813938,2019-01-31 10:01:06 UTC,I my environment:
1813938,2019-01-31 14:04:34 UTC,"Well, oslo.log was added to python-neutronclient requirements.txt in April 2018, which in turn is requiring pyinotify:"
1813938,2019-02-11 22:42:37 UTC,"Cesar - so it looks like this issue only applies to oslo.log and not neutron then, since we are just depending on it.  Perhaps you could just propose that requirements change there, or someone from the oslo team can?"
1813938,2019-02-12 08:02:20 UTC,"Yes, but is here, not? Only is change the require for oslo.log, including
this !=cygwin"
1813938,2019-01-31 18:45:10 UTC,"Hi,"
1813940,2021-02-03 13:54:26 UTC,"That patch has been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=4f8260248c68e4599a5
Thus closing this ticket now."
1813940,2019-02-05 18:53:34 UTC,"The bug is also reproducible with virtio-9p
-fsdev local,id=r,path=/,security_model=none -device virtio-9p-pci,fsdev=r,mount_tag=r"
1813940,2019-02-05 20:25:09 UTC,Hmm that's not surprising because coalesced ranges were completely broken before that commit.  I'll take a look.
1813940,2019-02-06 14:29:40 UTC,"Does this patch from Jagannathan Raman fixes it?
https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg01397.html"
1813940,2019-02-13 09:31:25 UTC,"> Does this patch from Jagannathan Raman fixes it?
> https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg01397.html
"
1813940,2019-02-13 11:54:35 UTC,That also fixes the case I'd hit
1813950,2020-05-26 21:16:55 UTC,"Let's close this.
I'm 99% sure it was fixed by https://opendev.org/openstack/tripleo-heat-templates/commit/f222681a435b19ef28d30a8293fb615863b094d6"
1813950,2019-03-05 19:05:29 UTC,"I tried to test it but there are some other bugs with the deployment that are stopping me from validating it. That said, I'm not really working on this anymore so I think you can close it."
1813950,2019-05-08 04:42:49 UTC,"Change abandoned by Harald Jensås (<email address hidden>) on branch: master
Review: https://review.opendev.org/633975"
1813950,2019-02-24 22:39:37 UTC,"Change abandoned by Harald Jensås (<email address hidden>) on branch: master
Review: https://review.openstack.org/633975
Reason: We improved the upstream fix to rename the existing queue. The service will now start properly without having to delete the old queue first. https://review.openstack.org/638114"
1813950,2019-01-30 15:19:06 UTC,OPNFV bug: https://jira.opnfv.org/browse/APEX-659
1813950,2019-01-30 15:23:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/633975"
1813950,2019-02-24 22:44:22 UTC,"@Tim, Is this still and issue after https://review.openstack.org/638440 ?"
1813953,2019-02-01 14:37:28 UTC,"As discussed in irc
3:22 PM <tilmanb> manadart:  bad controller https://pastebin.canonical.com/p/hG4PRGtsgk/
3:22 PM <tilmanb> manadart: good controller https://pastebin.canonical.com/p/FN9NjYPG7P/"
1813953,2019-01-31 16:40:13 UTC,I tested against MAAS 2.5 with Juju 2.3-latest and edge.
1813953,2019-01-31 16:11:32 UTC,"On Thu, 2019-01-31 at 15:42 +0000, Joseph Phillips wrote:

> I think I understand what is happening here.
>
> Juju should not be selecting a machine-local address for peer group
> usage, as you correctly state. But we should not be falling through
> to
> that choice at all, because the machines have addresses in subnets
> that
> are on the ""oam"" space.
>
> I believe the reason they are not chosen by space is due to a bug
> that we fixed in this patch:
> https://github.com/juju/juju/pull/8283
>
> That bug was to do with sourcing machine addresses directly from the
> machine, instead of through the provider (MAAS) which is space aware;
> thus the addresses are not decorated with the information required to
> select them by space.
>
> This could be confirmed by looking directly at the documents for
> these
> machines in the MongoDB ""machines"" collection. If the members of
> ""addresses"" don't have a ""spacename"", then it is definitely the
> issue.
>
> The best option is to move forward to the latest Juju 2.4 version.


Maybe we could add that information manually, so we get the controllers
up-n-running and then upgrade."
1813953,2019-01-31 15:42:45 UTC,I think I understand what is happening here.
1813953,2019-01-31 14:13:13 UTC,"right   100.107.0.0/22 should be the oam addresses that Juju is seeing, so
we aren't labeling the HostPorts correctly to match that subnet."
1813953,2019-01-31 13:49:29 UTC,"$ juju spaces
Space  Subnets
cbe    100.88.197.0/24
       100.88.199.0/24
       100.88.200.0/24
       100.88.201.0/24
clo    100.84.1.0/24
       100.84.197.0/24
       100.84.199.0/24
       100.84.2.0/24
       100.84.200.0/24
       100.84.201.0/24
       100.86.0.0/20
help
ipmi  100.100.1.0/24
      100.100.197.0/24
      100.100.199.0/24
      100.100.2.0/24
      100.100.200.0/24
      100.100.201.0/24
      100.102.1.0/24
      100.102.197.0/24
      100.102.199.0/24
      100.102.2.0/24
      100.102.200.0/24
      100.102.3.0/24
      100.106.231.0/24
      100.106.232.0/24
      100.106.233.0/24
oam   100.101.1.0/24
      100.101.197.0/24
      100.101.199.0/24
      100.101.2.0/24
      100.101.200.0/24
      100.107.0.0/22
      100.107.128.0/22
      100.107.64.0/22
      100.99.1.0/24
      100.99.197.0/24
      100.99.199.0/24
      100.99.2.0/24
      100.99.200.0/24
      100.99.201.0/24
ovr   100.68.1.0/24
      100.68.2.0/24
      100.70.0.0/20"
1813953,2019-01-31 13:17:35 UTC,It is behaving as if there was a network topology change.
1813953,2019-02-07 09:20:06 UTC,"As discussed in irc
3:22 PM <tilmanb> manadart:  bad controller https://pastebin.canonical.com/p/hG4PRGtsgk/
3:22 PM <tilmanb> manadart: good controller https://pastebin.canonical.com/p/FN9NjYPG7P/"
1813953,2019-01-31 12:10:13 UTC,I also first suspected an actual problem with the spaces. And it still might in some way.
1813953,2019-01-31 11:21:24 UTC,"All of them *are* in ""*107*"" and ""*70*"" and ""*86*"", so those should be possible values. And, in fact, they are currently configured to use the ""*107*"" addresses. (rs_addr=)"
1813953,2019-01-31 11:12:45 UTC,"Note this entry in the log file:
2019-01-29 10:56:27 ERROR juju.network address.go:316 no hostPorts found in spaces [oam]
2019-01-29 10:56:27 DEBUG juju.mongo mongo.go:293 Failed to select hostPort by space - trying by scope from [X.X.X.X:37017 Y.Y.Y.Y:37017 Z.Z.Z.Z:37017 127.0.0.1:37017]"
1813953,2019-01-31 09:28:48 UTC,"Can you supply also the output of the ""juju spaces""?"
1813953,2019-01-30 16:10:29 UTC,"SelectPeerHostPortBySpace() should implement ""allowMachineLocal = false"" as SelectPeerHostPort() did with the PR https://github.com/juju/juju/pull/8066"
1813953,2019-01-30 15:58:57 UTC,"I uploaded the machine logs from the controllers, juju status, juju show-controller, and rs.status()"
1813953,2019-01-30 15:35:01 UTC,"I'm compiling a set of logs, they should be ready to download soon."
1813953,2019-01-31 12:16:11 UTC,Upgrade to 2.4 is certainly an option. If we know the bug is gone there.
1813957,2019-05-12 04:17:27 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1813957,2019-03-12 04:05:18 UTC,Mark this as Incomplete for the request in comment #5
1813957,2019-03-12 10:20:24 UTC,"I haven't try @AaronMa tip (comment #5). However, with kernel 4.15.0-46-generic I haven't noticed the reported problem."
1813957,2019-02-01 09:00:38 UTC,I have just tried with 4.15.0-45-generic and the problem is still there.
1813957,2019-01-31 02:57:02 UTC,"There is a newer linux kernel in -proposed pocket released today with version 4.15.0-45.48, please give it a try."
1813957,2019-01-30 17:00:07 UTC,This change was made by a bot.
1813957,2019-03-01 05:33:17 UTC,Could you try these steps:
1813958,2019-02-15 20:03:27 UTC,Use cs:~cmars/xenial/kafka-5 for storage attach to work.
1813958,2019-02-15 20:06:41 UTC,Reproduced.  Additional detail of logs:
1813958,2019-02-15 20:59:42 UTC,juju config kafka bigtop_version=1.3.0 is required for install to succeed.
1813959,2020-03-19 22:15:31 UTC,"I didn't saw issues like that which causes directly job failure for long time.
I know that things like that may happen but it's more like red herring and the root cause is other issue which happened earlier.
So lets close this bug for now, we can always reopen it if needed."
1813959,2020-05-19 04:17:28 UTC,[Expired for neutron because there has been no activity for 60 days.]
1813960,2019-01-30 16:42:14 UTC,I will also add the bundle file that i use
1813960,2019-05-14 20:35:45 UTC,"Wieger,"
1813960,2019-07-14 04:17:47 UTC,[Expired for OpenStack cinder charm because there has been no activity for 60 days.]
1813962,2019-02-11 14:04:12 UTC,"Ironically, the now-missing CL_SCAN_STDOPT constant was documented to ""make your software ready for new features in the future versions of libclamav""."
1813962,2019-02-11 13:14:53 UTC,"Sorry, i was a to fast with that response, everything works fine now."
1813962,2019-02-10 04:44:20 UTC,"I found a thread about the same issue on Freebsd Bugzilla forum:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235002
They provided a patch for cyrusimap/cyrus-imapd that I borrowed (see below) and it worked for me, I was able to build ecap_clamav_adapter after modifying ClamAv.cc
cyrusimap/cyrus-imapd patch that I used a reference:
https://github.com/cyrusimap/cyrus-imapd/commit/09b5bf11e12185727d53a6ae06d71a767952a537#diff-e162ed934ed89d2014e496fc1961be01"
1813962,2019-02-01 02:57:33 UTC,just hit this on fedora 29
1813962,2019-02-11 12:41:53 UTC,"Well that solved the compile error, but the ecap_clamav_adapter.so does not work anymore with the old configurations of squid."
1813965,2019-03-16 19:13:03 UTC,"On a UK layout keyboard on Linux, the numpad +/- work the same as the +/- on the number row (left of backspace). Numlock does not affect these keys."
1813965,2019-03-18 11:42:27 UTC,"Just tested it again, it seems the issue has been already fixed."
1813965,2019-03-18 14:36:23 UTC,Looks fixed to me as well.  I'm not sure how this got fixed.  I played around with the num-lock key and it doesn't seem to make any difference so I'm going to set the status to fix committed.  Please reopen if the problem comes back.
1813965,2019-08-12 18:56:22 UTC,"Seems like this one made a comeback.  D-pad + and - doesn't change the layer while routing, however it does steps through the layers in the regular mode."
1813965,2019-03-15 19:16:46 UTC,"Since the keypad - works the same as the normal keyboard -, it stands to reason the that + behavior should be the same."
1813967,2019-02-05 20:54:27 UTC,https://review.openstack.org/#/c/634022/
1813967,2019-05-16 06:20:40 UTC,This issue was fixed in the openstack/python-cinderclient 4.2.0 release.
1813967,2019-08-22 23:26:28 UTC,This issue was fixed in the openstack/python-cinderclient 4.3.0 release.
1813972,2019-01-30 21:04:17 UTC,Please provide additional information/logs. There's not enough information to go on to reproduce. We've previously seen an index out of range when using capital letters in host names but that was results.  What version is being deployed?
1813972,2019-01-31 15:39:10 UTC,"[root@undercloud ~]# cat /etc/hosts
127.0.0.1   undercloud.opnfvlf.org undercloud localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6"
1813972,2019-03-19 13:30:30 UTC,Is this still an issue?
1813972,2019-03-19 13:47:20 UTC,I'm not working on it anymore so not sure. If no one else hits it then I guess we can close it.
1813972,2019-05-19 04:17:48 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1813976,2019-05-13 14:32:19 UTC,"Reviewed:  https://review.opendev.org/657682
Committed: https://git.openstack.org/cgit/starlingx/metal/commit/?id=5c043f7ca94a1bf4d121c209d42687184ec58a18
Submitter: Zuul
Branch:    master"
1813976,2019-05-31 20:42:12 UTC,"Verified in load BUILD_ID=""2019-05-30_16-58-16"""
1813976,2019-05-07 20:27:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657682"
1813976,2019-01-30 18:48:03 UTC,Marking as release gating -- issue found during feature testing (HA Recovery Improvements)
1813976,2019-05-03 14:47:00 UTC,Assigning to the stx-metal Core to triage this issue and determine root cause and how to fix.
1813978,2019-02-03 13:23:08 UTC,"HI ,"
1813979,2019-01-30 21:19:47 UTC,"Can you give me the output of (if possible the same shell instance where
this failed)"
1813979,2019-01-30 21:30:12 UTC,"Also, regarding the modprobe failure, the check_kvm_support script first checks if `/dev/kvm` is there and if not, then tries to load the msr module so it can probe CPU features to see if virtualization is available."
1813979,2019-01-30 21:55:29 UTC,I was running snapcraft from the archives on bionic:
1813979,2019-01-31 17:50:58 UTC,"@cmars,"
1813980,2019-03-19 11:44:47 UTC,Is /usr/bin/scp installed by the distro?
1813980,2019-03-20 12:20:14 UTC,"1.4.1 is working, thanks very much!"
1813980,2019-03-20 05:17:46 UTC,"@Rui, thanks for confirm, let's wait for reply from Corey"
1813980,2019-03-20 01:24:55 UTC,"@jichenjc, I've done the check before my last reply."
1813980,2019-03-20 00:50:07 UTC,"The ""'-P', '22', '-o StrictHostKeyChecking=no'"" is added by the following path"
1813980,2019-03-19 13:46:28 UTC,"it's not related to scp ,it's"
1813980,2019-03-19 11:45:00 UTC,I'm on Ubuntu disco fwiw.
1813980,2019-03-19 02:29:00 UTC,"The fix is not distro related. I also downloaded the 1.4.1, run both py27 and py36 unittests, all passed in my local env."
1813980,2019-03-15 13:26:03 UTC,release 1.4.1 available for both github and pypi. Hopefully this can fix the UT failure.
1813980,2019-03-18 01:33:21 UTC,I believe 1.4.1 includes the fix to the failure in commment #6.
1813980,2019-03-15 13:56:04 UTC,"ella, let's test it on 1.4.1 first and see whether we need 1.4.2 .."
1813980,2019-01-31 03:57:21 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/442815
1813980,2019-03-15 12:03:50 UTC,I do have that patch applied but the expected scp output isn't the same:
1813980,2019-03-14 06:49:33 UTC,"per Ella mentioned, the patch already fixed and cherry picked to
https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/442817"
1813980,2019-03-14 06:33:04 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/442815
1813980,2019-03-14 05:40:57 UTC,"Ella, can you help to take a look at this? Thanks"
1813980,2019-03-14 01:52:56 UTC,That fixed all but one test for me when I cherry-picked it to 1.4.0. It's possible there are other fixes in master that haven't been released yet. Here's the remaining failure:
1813980,2019-03-18 14:09:35 UTC,"Looking at the code it doesn't appear to be fixed. It seems the scp calls can have different arguments, perhaps that varies depending on what release of a distro you run on."
1813982,2019-02-02 01:45:05 UTC,"Reviewed:  https://review.openstack.org/634525
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=b6f6dd7e3c28bd9f9a2dde49557486cca1a1cef6
Submitter: Zuul
Branch:    master"
1813982,2019-02-02 01:44:06 UTC,"Reviewed:  https://review.openstack.org/634527
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cell-controller/commit/?id=5d09b43119c268f40e748f993de350f8105d887e
Submitter: Zuul
Branch:    master"
1813982,2019-02-02 00:14:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634528"
1813982,2019-02-02 00:14:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634527"
1813982,2019-02-02 00:14:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634526"
1813982,2019-02-02 00:13:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634525"
1813982,2019-02-02 00:02:09 UTC,"Reviewed:  https://review.openstack.org/634510
Committed: https://git.openstack.org/cgit/openstack/charms.openstack/commit/?id=982ae33054e57c8f64095ebbfbb187a181db13e6
Submitter: Zuul
Branch:    master"
1813982,2019-02-02 00:13:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634523"
1813982,2019-02-02 00:13:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634522"
1813982,2019-02-02 01:45:14 UTC,"Reviewed:  https://review.openstack.org/634524
Committed: https://git.openstack.org/cgit/openstack/charm-barbican/commit/?id=2cdcea8d1589bf7a42e648fcd26bfcc42f169833
Submitter: Zuul
Branch:    master"
1813982,2019-02-01 23:07:23 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634510"
1813982,2019-02-01 23:05:21 UTC,The reactive OpenStack charms do not use charmhelpers.contrib.openstack.cert_utils.install_certs when related to the certificates relation with vault.
1813982,2019-02-01 19:23:24 UTC,Almost all charms are fine except of aodh and gnocchi - they are still affected.
1813982,2019-02-02 00:13:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634524"
1813982,2019-02-02 01:47:38 UTC,"Reviewed:  https://review.openstack.org/634526
Committed: https://git.openstack.org/cgit/openstack/charm-manila/commit/?id=5fc15ee7a4afd304e130273375a24dab43131ac6
Submitter: Zuul
Branch:    master"
1813982,2019-02-02 15:24:46 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634568"
1813982,2019-02-02 15:22:23 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634566"
1813982,2019-03-12 07:36:34 UTC,"Change abandoned by Frode Nordahl (<email address hidden>) on branch: stable/18.11
Review: https://review.openstack.org/634571
Reason: Superseded by rebuild done in https://review.openstack.org/#/c/640073/"
1813982,2019-02-04 18:34:07 UTC,"Reviewed:  https://review.openstack.org/634696
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=f3e92848b4da5fc1ed22a33f0755b208dfc9e491
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-02-04 18:29:03 UTC,"Reviewed:  https://review.openstack.org/634567
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=7169a56ce10d2ffe7c28b4dc653aa441717eda7a
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-02-04 18:27:45 UTC,"Reviewed:  https://review.openstack.org/634569
Committed: https://git.openstack.org/cgit/openstack/charm-manila/commit/?id=b10f8995c196fd4ef2ab987a933738b5a594c5fb
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-02-04 18:25:45 UTC,"Reviewed:  https://review.openstack.org/634566
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cell-controller/commit/?id=75744256afb7a7b4343bc432b3e87dd3802ea816
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-02-04 18:23:59 UTC,"Reviewed:  https://review.openstack.org/634570
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=9e47becae622a17fdc09dd173fe9bf7e9777184b
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-02-02 15:21:32 UTC,"Reviewed:  https://review.openstack.org/634528
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=920c630a9e50c43685004e07eb0358df4644c3b6
Submitter: Zuul
Branch:    master"
1813982,2019-02-04 18:20:53 UTC,"Reviewed:  https://review.openstack.org/634568
Committed: https://git.openstack.org/cgit/openstack/charm-barbican/commit/?id=d75350838a2c17bf9f094cda39f0ed6ccf6cc1ac
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-02-04 14:22:53 UTC,"Reviewed:  https://review.openstack.org/634523
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=ee68a502a36fdc25fe95faa4b003908c5a9db325
Submitter: Zuul
Branch:    master"
1813982,2019-02-02 15:25:41 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634570"
1813982,2019-02-02 15:25:16 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634569"
1813982,2019-02-01 17:47:23 UTC,"Reviewed:  https://review.openstack.org/634136
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=a09d89f5f459ba7f99017f7442b268696164eeb9
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-02-02 15:24:18 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634567"
1813982,2019-02-02 15:23:40 UTC,"Reviewed:  https://review.openstack.org/634522
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=7f1ea17ec4bc2f2448008a43a462b927b3fb2e43
Submitter: Zuul
Branch:    master"
1813982,2019-02-04 14:23:26 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634696"
1813982,2019-02-01 16:56:19 UTC,"Reviewed:  https://review.openstack.org/634259
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=b9173f1587611f6f0bb998751ee38b72d048aef3
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-02-02 15:31:10 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634571"
1813982,2019-02-01 16:51:01 UTC,"Reviewed:  https://review.openstack.org/634134
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=1dff4ab5ead1892b5271f99ea458d13a1f422984
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 08:30:24 UTC,"Having said that the stable reactive charms may still need a rebuild for it to be marked as ""Fix Released"""
1813982,2019-01-31 08:28:42 UTC,FTR; all reactive charms already contain the fix after rebuild commits landed January 24th
1813982,2019-01-31 08:27:13 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634132"
1813982,2019-01-31 08:25:53 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634131"
1813982,2019-01-31 08:24:25 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634130"
1813982,2019-01-31 08:23:09 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634128"
1813982,2019-01-31 08:50:56 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634135"
1813982,2019-01-31 08:21:21 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634127"
1813982,2019-01-31 08:17:32 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634124"
1813982,2019-01-31 07:00:43 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634107"
1813982,2019-01-31 06:42:06 UTC,This is fixed in charm-helpers here https://github.com/juju/charm-helpers/commit/cb2c2282f900a6e198b3578610c6c5375ea83292
1813982,2019-01-30 20:32:59 UTC,Some kind of workaround:
1813982,2019-01-30 20:03:11 UTC,Subscribed ~field-high as this may impact ongoing customer delivery and handover.
1813982,2019-02-01 16:56:10 UTC,"Reviewed:  https://review.openstack.org/631570
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=329beab23915578b8ce438f8d0334c28ef9bdab5
Submitter: Zuul
Branch:    master"
1813982,2019-01-31 08:19:34 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634125"
1813982,2019-01-31 08:54:10 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634136"
1813982,2019-01-31 08:47:52 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634134"
1813982,2019-01-31 09:03:06 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634141"
1813982,2019-02-01 11:04:19 UTC,"Reviewed:  https://review.openstack.org/634131
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=4365f896ddf5fc54df335059fc7e67a41b040438
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 21:56:28 UTC,"Reviewed:  https://review.openstack.org/634138
Committed: https://git.openstack.org/cgit/openstack/charm-manila/commit/?id=7a00cf39ab017ced583dff3c24ef9569ce1eccb3
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 21:43:06 UTC,"Reviewed:  https://review.openstack.org/634142
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=168bf9219f83e6b40ef0cf0a08fb142a5ae00ad3
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 21:42:02 UTC,"Reviewed:  https://review.openstack.org/634127
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=c25012e6232c16c18a07676c662c3b72943efe17
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 21:41:43 UTC,"Reviewed:  https://review.openstack.org/634132
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=0cdf8c2518259178b33f80a2874015ae97e63a62
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 08:59:03 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634138"
1813982,2019-01-31 21:40:24 UTC,"Reviewed:  https://review.openstack.org/634130
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=d76a3f4a01a75f2375b71936af306b2512b154a0
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 21:41:01 UTC,"Reviewed:  https://review.openstack.org/634141
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cell-controller/commit/?id=3da05863c0bc4c80d3db454b6f9dc858897f3e42
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 18:06:37 UTC,"Reviewed:  https://review.openstack.org/634128
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=23cdf769cd457ba8ef1b57bae660374159773524
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 17:31:09 UTC,"Reviewed:  https://review.openstack.org/634125
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=76cb969967330df3249304398a2ccd98dfc67c54
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 17:30:44 UTC,"Reviewed:  https://review.openstack.org/634107
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=9cc0c77d568e7e17bf4da1e05be9b68b7014ed24
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 17:30:08 UTC,"Reviewed:  https://review.openstack.org/634135
Committed: https://git.openstack.org/cgit/openstack/charm-barbican/commit/?id=23ce1be4514b40294bf39b75c4f4c084cbdc1ff8
Submitter: Zuul
Branch:    stable/18.11"
1813982,2019-01-31 15:48:35 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634259"
1813982,2019-01-31 09:05:59 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/634142"
1813982,2019-01-31 21:38:29 UTC,"Reviewed:  https://review.openstack.org/634124
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=0e3181d09f9c80c3b1a3f68e85cc2f3571ae13c1
Submitter: Zuul
Branch:    stable/18.11"
1813984,2019-01-30 21:00:07 UTC,This change was made by a bot.
1813984,2019-01-31 14:13:55 UTC,"Was the nvidia module actually compiled and installed for the new kernel? What does ""dkms status"" report?"
1813986,2019-09-06 18:08:31 UTC,I forgot the full path to the default keybinds file in my one-liner in comment #6.  It should be
1813986,2019-10-03 17:57:38 UTC,"Apologies, the snippet in my previous post is wrong. This should work (followed by `F5` to reload config):"
1813986,2019-10-03 17:51:02 UTC,"Please, devs. This is a big deal. I've lost work due to this bug."
1813986,2019-09-06 18:05:37 UTC,"I'm running Debian 10 (buster), tmux 2.8-3, byobu 5.112-1.1 and see the same behavior."
1813986,2019-10-03 19:13:48 UTC,"Some good news! It looks like this issue has been fixed (by removing `-k`, not adding `-ak`) as of 2019-06-01 in this rev: https://bazaar.launchpad.net/~kirkland/byobu/trunk/revision/2612"
1813986,2019-08-08 17:10:19 UTC,"Same here on Ubuntu server 18.04
byobu version 5.125
tmux 2.9a"
1813986,2019-07-15 21:24:01 UTC,I really feel the scarcity of bug reporters here belies the severity of the issue. A terminal multiplexer that can unexpectedly kill off *any number* of operations as a result of a single misplaced keystroke seems like a pretty serious issue.
1813986,2019-07-01 09:43:02 UTC,Same thing here Ubuntu Mate 19.04
1813986,2019-06-22 19:18:19 UTC,Can confirm on openSuse as well:
1813986,2019-08-21 04:29:45 UTC,affected on:
1813987,2019-10-23 01:11:24 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10466"
1813987,2019-10-23 00:28:28 UTC,"Reviewed:  https://reviews.mahara.org/10450
Committed: https://git.mahara.org/mahara/mahara/commit/9e81132db3bf24df4db98b217aa2ab3abb0bff48
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-22 21:56:37 UTC,"Reviewed:  https://reviews.mahara.org/10448
Committed: https://git.mahara.org/mahara/mahara/commit/6f2f9f8ff8de7f5d7745662a45e50015536bb5dc
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-22 21:26:16 UTC,"Reviewed:  https://reviews.mahara.org/10444
Committed: https://git.mahara.org/mahara/mahara/commit/3ab2c9126d80db0aeb53095f20d7708a814dce03
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-22 21:26:16 UTC,"Reviewed:  https://reviews.mahara.org/10447
Committed: https://git.mahara.org/mahara/mahara/commit/0e7ce5c1c0377d82ec84ccc56f37bf9a39d3bc3e
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-22 21:26:16 UTC,"Reviewed:  https://reviews.mahara.org/10436
Committed: https://git.mahara.org/mahara/mahara/commit/a8b9bfb186ed721ccca66d0578f1ae6ea408ba59
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-18 00:58:57 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10450"
1813987,2019-10-16 23:28:03 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10448"
1813987,2019-10-08 22:45:58 UTC,"Reviewed:  https://reviews.mahara.org/10411
Committed: https://git.mahara.org/mahara/mahara/commit/02c6617dc28b9ddaea3fb9f433b08dc89832ae18
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:25 UTC,"Reviewed:  https://reviews.mahara.org/10398
Committed: https://git.mahara.org/mahara/mahara/commit/fa4085d5664f333f943ac0f58e3065d89137c10e
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:25 UTC,"Reviewed:  https://reviews.mahara.org/9329
Committed: https://git.mahara.org/mahara/mahara/commit/61acdaa6235bdc25388e13aeb1ba079605fac597
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:24 UTC,"Reviewed:  https://reviews.mahara.org/9509
Committed: https://git.mahara.org/mahara/mahara/commit/2c861ec11807d1747d631a9ed568b985bb17bf17
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:24 UTC,"Reviewed:  https://reviews.mahara.org/9556
Committed: https://git.mahara.org/mahara/mahara/commit/5f57b6023ede89e35c70ba2575626646c64c75b5
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:24 UTC,"Reviewed:  https://reviews.mahara.org/9551
Committed: https://git.mahara.org/mahara/mahara/commit/d45aed8d9200e409459ef8ba326c869c420494d3
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:24 UTC,"Reviewed:  https://reviews.mahara.org/9714
Committed: https://git.mahara.org/mahara/mahara/commit/2a9211b3e2d8abe8699ed781f4fa52ec0b7cc68a
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:24 UTC,"Reviewed:  https://reviews.mahara.org/9508
Committed: https://git.mahara.org/mahara/mahara/commit/ca51ed794b745b991f734f88b61cdeec3d182b68
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:24 UTC,"Reviewed:  https://reviews.mahara.org/9952
Committed: https://git.mahara.org/mahara/mahara/commit/6cee4292a93deaeb049c856f7fb2b261eb76fe79
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:23 UTC,"Reviewed:  https://reviews.mahara.org/9972
Committed: https://git.mahara.org/mahara/mahara/commit/6aadcd020ab6e76bfe8471a6b7c87e675173fd96
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:23 UTC,"Reviewed:  https://reviews.mahara.org/9953
Committed: https://git.mahara.org/mahara/mahara/commit/c0f57e7da518c25352b30ca11a20d9be46205674
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-06 22:39:41 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10411"
1813987,2019-10-23 03:07:34 UTC,"Reviewed:  https://reviews.mahara.org/10466
Committed: https://git.mahara.org/mahara/mahara/commit/9a241ca8b302c0110b9d2ee62f37054c776104d3
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-23 03:17:11 UTC,"Reviewed:  https://reviews.mahara.org/10469
Committed: https://git.mahara.org/mahara/mahara/commit/d190004ce6dedb8a1f05ae57f008df48f2f9baca
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1813987,2019-10-23 03:20:23 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10470"
1813987,2019-10-05 16:41:23 UTC,"Reviewed:  https://reviews.mahara.org/9970
Committed: https://git.mahara.org/mahara/mahara/commit/a5fd2d09e190a7dc08936039ea9e388758f71e51
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-30 03:56:42 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10512"
1813987,2019-10-30 03:44:05 UTC,"Reviewed:  https://reviews.mahara.org/10511
Committed: https://git.mahara.org/mahara/mahara/commit/0a8454f922ab37b8bb7b1a322c9c5098ba8251ea
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1813987,2019-10-30 03:43:57 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10511"
1813987,2019-10-30 03:43:50 UTC,"Reviewed:  https://reviews.mahara.org/10509
Committed: https://git.mahara.org/mahara/mahara/commit/f7632dbe9bd37acb8b1d775f88f66d98b7880a6b
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1813987,2019-10-30 01:34:21 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10509"
1813987,2019-10-30 00:59:50 UTC,"Reviewed:  https://reviews.mahara.org/10508
Committed: https://git.mahara.org/mahara/mahara/commit/f83b4c6b148a3e9e66916cd15428da9c6ec08261
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.10_STABLE"
1813987,2019-10-30 00:59:40 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10508"
1813987,2019-10-30 00:59:22 UTC,"Reviewed:  https://reviews.mahara.org/10505
Committed: https://git.mahara.org/mahara/mahara/commit/9b3a9303cc8d314214c16dd2d7a78f771ee53f99
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-29 22:11:35 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10505"
1813987,2019-10-23 03:25:27 UTC,"Reviewed:  https://reviews.mahara.org/10475
Committed: https://git.mahara.org/mahara/mahara/commit/5766ea5a40b5d9de2190f885020fea1ec3b93401
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1813987,2019-10-23 03:25:21 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10475"
1813987,2019-10-23 03:24:36 UTC,"Reviewed:  https://reviews.mahara.org/10473
Committed: https://git.mahara.org/mahara/mahara/commit/d2bf336b58e6167fa75594039b6ee4811710f1dc
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1813987,2019-10-23 03:24:29 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10473"
1813987,2019-10-23 03:23:08 UTC,"Reviewed:  https://reviews.mahara.org/10472
Committed: https://git.mahara.org/mahara/mahara/commit/712cd9dca39b15d506bf1d8c4d6794e1bd8192fe
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1813987,2019-10-23 03:23:02 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10472"
1813987,2019-10-23 03:22:36 UTC,"Reviewed:  https://reviews.mahara.org/10471
Committed: https://git.mahara.org/mahara/mahara/commit/1e43c06a496a82f3823efc9e4701ff9f2fd66bb8
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1813987,2019-10-23 03:22:25 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10471"
1813987,2019-10-23 03:20:49 UTC,"Reviewed:  https://reviews.mahara.org/10470
Committed: https://git.mahara.org/mahara/mahara/commit/3eb6196dbde3de675d0909146443c3d79aaba412
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    19.10_STABLE"
1813987,2019-10-23 03:17:05 UTC,"Patch for ""19.10_STABLE"" branch: https://reviews.mahara.org/10469"
1813987,2019-10-05 16:41:23 UTC,"Reviewed:  https://reviews.mahara.org/9986
Committed: https://git.mahara.org/mahara/mahara/commit/565776fb60d1e0b1c50f3ac2315b331244a647ab
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-05-07 07:29:52 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9972"
1813987,2019-10-05 16:41:23 UTC,"Reviewed:  https://reviews.mahara.org/9979
Committed: https://git.mahara.org/mahara/mahara/commit/f9295a81ad4483c1f829c2ecb25192d034e1a770
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-07-30 05:16:02 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10230"
1813987,2019-07-25 22:10:24 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10223"
1813987,2019-07-23 23:41:57 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10222"
1813987,2019-07-11 05:56:31 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10155"
1813987,2019-07-05 06:36:19 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10145"
1813987,2019-07-05 03:36:09 UTC,This is a library we could use for reordering blocks in accessibility fixed layout
1813987,2019-07-05 03:34:22 UTC,Decisions taken for accessibility and upgrade to new layout
1813987,2019-05-14 04:57:21 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10010"
1813987,2019-05-12 22:32:18 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9992"
1813987,2019-05-09 05:53:42 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9986"
1813987,2019-05-08 03:02:07 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9979"
1813987,2019-01-30 21:12:44 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9509"
1813987,2019-05-07 04:34:52 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9971"
1813987,2019-05-07 03:13:56 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9970"
1813987,2019-05-03 06:00:38 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9953"
1813987,2019-05-03 05:12:02 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9952"
1813987,2019-04-05 04:28:08 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9714"
1813987,2019-02-13 03:20:44 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9556"
1813987,2019-02-12 21:34:58 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9551"
1813987,2019-08-01 02:28:36 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10236"
1813987,2019-08-06 22:26:04 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10247"
1813987,2019-10-05 16:41:23 UTC,"Reviewed:  https://reviews.mahara.org/9971
Committed: https://git.mahara.org/mahara/mahara/commit/b8afbd1599dd83368d2659200e2efe0938ec0920
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-08-08 05:08:11 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10251"
1813987,2019-10-05 16:41:23 UTC,"Reviewed:  https://reviews.mahara.org/9992
Committed: https://git.mahara.org/mahara/mahara/commit/0772a2407bfefbb4cede46ac7efcc55de7578c07
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:22 UTC,"Reviewed:  https://reviews.mahara.org/10155
Committed: https://git.mahara.org/mahara/mahara/commit/32de0b181b0d06ca1f70e4134d5f8e7760ca10a0
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:22 UTC,"Reviewed:  https://reviews.mahara.org/10010
Committed: https://git.mahara.org/mahara/mahara/commit/15bca1e7bc4acea225193819548f7a44b0e08eff
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:22 UTC,"Reviewed:  https://reviews.mahara.org/10223
Committed: https://git.mahara.org/mahara/mahara/commit/7b17b833ebc13071355844cd57f61b8071e1d5ab
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:22 UTC,"Reviewed:  https://reviews.mahara.org/10222
Committed: https://git.mahara.org/mahara/mahara/commit/f342e41b6c096d4fabfae645508e4041cb0b8af9
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:22 UTC,"Reviewed:  https://reviews.mahara.org/10145
Committed: https://git.mahara.org/mahara/mahara/commit/66c08ce0e95b6c8d17e2989d2938dce8929352d7
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:21 UTC,"Reviewed:  https://reviews.mahara.org/10230
Committed: https://git.mahara.org/mahara/mahara/commit/b6cd876f38bec044914ce688b1d9ea455664e409
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:21 UTC,"Reviewed:  https://reviews.mahara.org/10247
Committed: https://git.mahara.org/mahara/mahara/commit/1a1d2a69ef7d860733973610cb602dc4f5b8f5aa
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:21 UTC,"Reviewed:  https://reviews.mahara.org/10236
Committed: https://git.mahara.org/mahara/mahara/commit/af08a13805b48adddb4da1f98fa1ad8e52000e55
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:21 UTC,"Reviewed:  https://reviews.mahara.org/10346
Committed: https://git.mahara.org/mahara/mahara/commit/9cf3d8eb493ec2b8d3d63cad2f2e6ddec7527c85
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:21 UTC,"Reviewed:  https://reviews.mahara.org/10251
Committed: https://git.mahara.org/mahara/mahara/commit/250829882ef38ef6da690beba4677b8ecb4fc8db
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:21 UTC,"Reviewed:  https://reviews.mahara.org/10297
Committed: https://git.mahara.org/mahara/mahara/commit/ccc2446d7451e3d545865e6d70f089045f663799
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:20 UTC,"Reviewed:  https://reviews.mahara.org/10394
Committed: https://git.mahara.org/mahara/mahara/commit/279c2d49bb958ef9c9399ef2ded337b7420bf7e2
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-05 16:41:20 UTC,"Reviewed:  https://reviews.mahara.org/10386
Committed: https://git.mahara.org/mahara/mahara/commit/24e838cf0904ef79ec129fc053eb1c91af76ed6b
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-10-03 23:10:54 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10398"
1813987,2019-10-03 21:32:18 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10394"
1813987,2019-10-01 01:21:11 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10386"
1813987,2019-09-13 06:10:48 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10346"
1813987,2019-09-05 04:52:53 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10297"
1813987,2019-10-05 16:41:21 UTC,"Reviewed:  https://reviews.mahara.org/10249
Committed: https://git.mahara.org/mahara/mahara/commit/69916a3da2aeb8087c12d17a783e46049c4e5ecd
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1813987,2019-08-07 05:32:01 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10249"
1813993,2019-01-30 23:55:05 UTC,*** This is an automated message ***
1813995,2019-02-07 05:09:18 UTC,PR to fix this: https://github.com/juju/juju/pull/9724
1813995,2019-02-13 19:49:32 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1813996,2019-02-13 19:49:25 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1814003,2019-01-31 00:00:08 UTC,This change was made by a bot.
1814003,2019-02-18 08:48:19 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1814005,2019-09-16 14:28:42 UTC,"This has something to do with the AWS blacklisting, Sean got this fixed by putting an autotest-client-test directory to the server."
1814012,2021-01-17 06:15:18 UTC,"This bug affects me
tested on two different adaptors
/sbin/wpa_supplicant -c /run/netplan/wpa-wlxd037453da72a.conf -iwlxd037453da72a -Dwext
will work for me
lsusb reports 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
however running
/sbin/wpa_supplicant -c /run/netplan/wpa-wlxd037453da72a.conf -iwlxd037453da72a -Dnl80211
will not work
same with
/sbin/wpa_supplicant -c /run/netplan/wpa-wlxd037453da72a.conf -iwlxd037453da72a
which appears to corrospond with how netplan is attempting to initialise the usb adapter
this option works for one adaptor that does not use nl80211 drivers"
1814012,2020-11-21 20:22:42 UTC,Same here. Also using rtl8188 chipset which only works with wext.
1814012,2020-05-31 17:32:01 UTC,This also affects me: the wireless dongle I am using needs wext driver but by default netplan is trying to use the nl80211 driver.  If I specify -Dwext as seen in this paste I can get a connection:
1814012,2020-05-19 22:09:13 UTC,This bug affects me too: to be able to use my RTL-8188EUS on Ubuntu Server 18.04.4 I have to pass -Dwext as parameter to wpa_supplicant. My workaround up to now has been to create a wrapper script named wpa_supplicant renaming the original executable.
1814012,2020-11-08 02:15:44 UTC,"I have this problem too, I think netplan is garbage, because it has no config for some networkd config(such as mdns and ipv6 prefix delegation), it only have is a basic network config, I don't know why bother use netplan but it's integrated in ubuntu as essential(ubuntu-minimal and cloud-init all depends on it). I don't know why this isn't an option to to user, and they have many ancient bug that are still open."
1814012,2019-04-20 20:33:33 UTC,I'm afraid I still don't understand from this why one would specify a -D option by hand
1814012,2019-04-20 17:44:33 UTC,Re range of possible values for -D option:
1814012,2019-04-20 20:57:29 UTC,Here's one (e.g. my) case:
1814012,2019-03-21 01:09:30 UTC,"What is the range of possible values for this -D option, and why would you ever want to specify it in the netplan yaml instead of inferring it?"
1814012,2019-03-20 21:24:15 UTC,Triaged; we will need some input from Steve though to figure out how to addess this in the netplan schema.
1814012,2019-03-20 21:22:30 UTC,"That's not quite the device, but a driver value though. I wonder if it wouldn't be best to either always set -Dnl80211 on wireless (and -Dwired for 802.1x on ethernet...), or to make it possible to use an alternative value if matching by driver."
1814014,2021-02-16 00:46:39 UTC,"I didn't have much luck downgrading to 0.9.1, due to dependency issues with pymq. However I did some more checks on the imported files. From the logs, it appears that metadatavideo.py is failing to find the date/time in the videos, so RPD is falling back on exiftool. I ran the following script to view the metadata of the imported files:"
1814014,2021-02-14 13:18:14 UTC,"Actually it's not working properly on Ubuntu either, I should be more wary of testing and making assertions at 2am ;-)"
1814014,2021-02-14 02:13:52 UTC,Same for me on an up-to-date OpenSuSE Tumbleweed. I had 0.9.26 installed from the OpenSuSE repos and encountered the bug. I removed the package and installed via the script from the RPD website. I still encounter this bug. I am downloading videos via PTP from an LG-H850 phone.
1814014,2019-07-29 17:06:41 UTC,I can confirm the bug affects me as well using 0.9.15 (and the 0.9.13).
1814014,2019-02-02 02:35:36 UTC,"Okay, I'll take a look at this when I get the chance later this year. Sorry no time to investigate it now."
1814014,2021-02-16 01:19:55 UTC,"Robert, I wonder if you are mistaken about how Rapid Photo Downloader determines video metadata. It never reads the metadata directly itself. It always relies on two external programs for videos: mediainfo, and ExifTool. These two programs don't always return the correct results. Sometimes Rapid Photo Downloader has to choose between them."
1814014,2019-02-02 00:52:07 UTC,"Ahh yes, now I see from further in the log that when you upgraded to 0.9.13, the install script installed the missing libmediainfo package."
1814014,2019-02-01 22:35:31 UTC,libmediainfo0v5 was already installed....
1814014,2019-02-01 15:40:50 UTC,From the log file:
1814014,2019-02-01 00:20:19 UTC,Hi - test video attached....
1814014,2019-01-31 19:56:54 UTC,"Create a test video on the drone that is a few seconds long. Make its content be of something be of something completely benign, i.e. no problems with privacy or copyright etc. Do not modify the file in any manner, at all (very important). Attach it to the bug report. Thanks."
1814014,2019-02-02 02:23:11 UTC,"Yes I did record that video and can confirm that the drone had correct
time. Still photos uploaded correctly again but the time on the video
upload was 9 hours in the future."
1814016,2019-02-22 15:15:39 UTC,What was the failure in the subnode before you added the workaround? Because this could be a duplicate of bug 1815082.
1814016,2020-07-29 04:17:19 UTC,[Expired for devstack because there has been no activity for 60 days.]
1814017,2020-01-01 11:10:14 UTC,Try https://hub.docker.com/r/yakshaveinc/snapcraft
1814029,2019-01-31 21:25:46 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1814031,2019-02-02 18:28:03 UTC,"You might have an anti-virus or other protection software installed which is interfering here. If you can, please try adding an exception for Open Rails or - temporarily - disable it just long enough to confirm whether that fixes the problem."
1814036,2019-01-31 09:36:36 UTC,"You modified the redis-server.service file, is it actually a correct file?"
1814036,2019-01-31 09:49:23 UTC,"No,I am not modified that file
Its actually a correct file,
Installing of new apps is not possible,
It shows an error:
     dpkg: unrecoverable fatal error, aborting:
     unknown user 'redis' in statoverride file
     E: Sub-process /usr/bin/dpkg returned an error code (2)"
1814039,2019-04-19 12:11:52 UTC,With a bit of tinkering this could be solved by a generalized version of the current chamfered pad. See https://bugs.launchpad.net/kicad/+bug/1824614
1814039,2019-04-13 07:48:55 UTC,A bit off topic: Yes some manufactuers suggest such a pad shape. The industry standard (IPC) however suggests the use of pads that are symetrical. In 7351-B and earlier oblong pads (In kicad called oval) are suggested. The future 7351-C suggests to move to rounded rectangle pads.
1814039,2019-01-31 16:35:29 UTC,"Aaron, you can compose your own pad shapes with KiCad 5.0, which has a tool for this purpose. Select one of `Custom` as a pad shape then open third tab in pad properties."
1814043,2019-02-05 13:16:18 UTC,the patch: https://review.openstack.org/#/c/263911/ seems no longer be responsible to the action on the master branch
1814043,2019-02-07 03:20:48 UTC,@XiaojuGuan https://github.com/openstack/horizon/blob/master/openstack_auth/backend.py#171 is it not a valid code you mean?
1814046,2019-01-31 07:57:26 UTC,sla2 for 9.0-updates
1814046,2019-02-04 06:34:41 UTC,"Hi Roman,"
1814046,2019-02-04 08:11:56 UTC,"Alexander, setting any OOM-killer value is tightly connected to the real environment's characteristics. Since we find memory leaks as a rare-to-none occurring event we don't see any reason to change anything there. Moreover, neither a Controller node or a Compute nodes have any sacrificial processes that are not important for proper OpenStack operations. You just cannot save everything, since making priorities for every process effectively means that no process has a priority (exactly what we have now). Additionally, a memory leak should be fixed, not worked around or masked, otherwise it may be hiding until it's too late and all the data is lost. OpenStack is designed to have a failover in case if one of the nodes is failed, this idea allows cloud operators to troubleshoot the failed node, learn the lesson and avoid it re-occurrence in the future."
1814046,2019-01-31 14:50:55 UTC,"Hi Alexander,"
1814066,2019-02-01 15:42:44 UTC,We can do this on snapcraft's side as long as we have storeapi. I added a task for that team to either provide the documentation or implementation.
1814066,2019-07-25 19:13:04 UTC,"Sergio,"
1814068,2019-01-31 10:30:08 UTC,This change was made by a bot.
1814068,2019-02-06 20:15:12 UTC,Does the 4.15.0-45 kernel resolve this issues?
1814068,2019-09-30 11:14:54 UTC,How do you know it crashes?
1814072,2019-02-02 08:06:38 UTC,Main source is https://code.launchpad.net/software-properties (I thought upstream was Debian due to versioning)
1814072,2019-02-02 07:46:47 UTC,"it also does not recognize lines like this:
deb mirror+https://bryanquigley.com/mirrors.txt disco main restricted universe multiverse"
1814072,2019-01-31 10:45:23 UTC,Other Software tab
1814072,2019-02-02 07:42:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814072,2019-01-31 10:44:57 UTC,Ubuntu software tab
1814079,2019-01-31 14:16:35 UTC,Do you see any other failures in the log around failing to claim leadership?
1814079,2019-06-25 06:11:28 UTC,I believe this has already been fixed in the 2.5 branch.
1814080,2019-04-25 13:43:25 UTC,"Hi Alvaro,"
1814080,2019-04-26 15:16:04 UTC,Please provide all of the things you would need to customize.
1814080,2019-09-25 09:00:35 UTC,"Hi Alvaro. We've started to track feature request on discourse instead, https://discourse.maas.io/, since it's a better forum for that."
1814088,2019-04-04 04:51:32 UTC,"Confirmed, but the number of crash reports is incredibly low right now:"
1814088,2019-04-04 04:46:46 UTC,Also tracking in https://errors.ubuntu.com/problem/e6f21a21cd523f0c489de07464069cea59d69427
1814088,2019-04-04 04:17:24 UTC,[Expired for totem (Ubuntu) because there has been no activity for 60 days.]
1814088,2019-02-01 12:10:16 UTC,Thanks for the reply. It's a bit weird if it comes from firefox because the totem webbrowser plugin got deprecated and there is no reason firefox would call to totem to play video...
1814088,2019-02-01 12:00:57 UTC,"I agree it's a bit of a nightmare. It was the start of the day and I
literally just had Firefox-Next open, and Slack (using the app, not via
Firefox). No video had been posted to slack. I can only think some
random embedded video went by on the timeline or activities column in
tweetdeck (the only tab) on firefox. Nothing else was going on, and said
embedded videos usually either work fine or not at all. In the past I've
had stuff like this happen when opening a Nautilus window onto a
directory with videos in it, so it being the preview of said videos that
probably crashed... but not this time."
1814088,2019-02-01 10:01:59 UTC,"Thank you for your bug report. Without steps to reproduce the issue it's going to be a bit difficult to debug that though, could see if you can trigger it again by doing the same things you were doing?"
1814088,2019-01-31 11:55:44 UTC,"StacktraceTop:
 tcache_get (tc_idx=1) at malloc.c:2927
 __GI___libc_malloc (bytes=bytes@entry=35) at malloc.c:3034
 g_malloc (n_bytes=n_bytes@entry=35) at ../../../../glib/gmem.c:99
 g_strconcat (string1=string1@entry=0x7f609f01d969 ""assertion failed: ("") at ../../../../glib/gstrfuncs.c:585
 g_assertion_message_expr (domain=domain@entry=0x7f609f0cf07b ""GLib-GObject"", file=file@entry=0x7f609f0d12ce ""../../../../gobject/gobject.c"", line=line@entry=1813, func=func@entry=0x7f609f0d28c0 <__func__.14400> ""g_object_new_internal"", expr=expr@entry=0x7f609f0d148e ""nqueue != NULL"") at ../../../../glib/gtestutils.c:2618"
1814088,2019-02-01 12:34:09 UTC,"True. And I can confirm it's not listed in my plugins at all. (There's
just Cisco OpenH264 and Widevine). Only potentially-relevant extension
is Disable HTML5 Autoplay, which if anything should *stop* any video
being played before it gets to the software that does it."
1814095,2019-03-22 16:05:33 UTC,"Just briefly wanted to say that this is one we've discussed at
length -- we may not be able to get someone who has the right
NIC to test with it in time."
1814095,2019-03-25 14:47:15 UTC,Are there repro steps that can be passed along to test?
1814095,2019-03-15 20:04:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1814095,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1814095,2019-02-26 21:21:40 UTC,"Nivedita, per the request to test this patch, determining the correct FW version seems an open issue.  There is also the issue of having hardware available to properly test."
1814095,2019-03-03 19:34:18 UTC,"Terry,"
1814095,2019-01-31 13:23:46 UTC,"Due to earlier NIC flapping observed on systems for the
25Gb Broadcom NIC, with originally the following config,
the firmware was upgraded to avoid a known FW bug:"
1814095,2019-03-25 17:27:06 UTC,"I am not sure we could deterministically provoke the
issue. At the very least to ensure no other regression
was introduced, I would run it under heavy network load."
1814095,2019-01-31 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1814095,2019-02-21 09:17:01 UTC,"If anyone is interested and willing to test a 4.4 kernel
patched with the fix ""bnxt_en: Fix TX timeout during netpoll""
backported to the bnxt_en_bpo driver, please find the packages
here:"
1814096,2019-02-23 13:09:32 UTC,https://github.com/mixxxdj/mixxx/pull/2038
1814099,2019-01-31 19:16:42 UTC,"It looks like you started aa-genprof as user, which isn't supported. I admit the error message should be more helpful ;-)"
1814099,2019-02-02 17:52:08 UTC,"Well, I really thought I had tried that. I'm sorry about wasting your time. That did work. Thank you for the quick response."
1814100,2019-02-01 08:00:47 UTC,"I assume that, by pressing Alt+1(Numkey) after coupling, the rear cam (3) jumps to the new end of train."
1814100,2019-02-01 13:35:22 UTC,Thanks for your mail!
1814100,2019-02-02 08:21:54 UTC,By CR you mean change requests? And do you mean only the request itself or also the related code changes?
1814100,2019-02-02 11:56:24 UTC,"Only the request itself. The major request is regarding shunting operations, that have been implemented in the MSTS (due to performance and resource limitations) only partially (at least ... only the signal type ""SHUNTING"", that causes the MSTS to crash sometimes.
In difference so DE, where the ""Sperrsignal"" can be treated as main signal (affects shunting and train), the former k&k states (AT, SK, CZ, HU, partially PL, IT with associated private lines, and CH) distinguish between shunting an train signals. Clean shunting would be a major benefit for interesting scenarios. I do not know the state in the US, but UK has also shunting signals on some lines, an i think some lines in the USA also."
1814100,2019-02-02 20:22:35 UTC,Here http://www.elvastower.com/forums/index.php?/topic/28517-open-rails-12-planning/page__view__findpost__p__201634 you can read how to propose new features for OR.
1814108,2019-02-05 19:43:58 UTC,Moved from https://bugs.launchpad.net/yade/+bug/1814108 to https://gitlab.com/yade-dev/trunk/issues/50
1814109,2020-02-22 01:21:50 UTC,"This issue has been fixed in libarchive release 3.4.2
https://github.com/libarchive/libarchive/commit/250476b9adf53cf7fcb027802b0d4104de7c07cb"
1814109,2020-03-16 19:57:34 UTC,The fix is in 3.4.2 update request LP: #1867390.
1814109,2020-07-06 14:27:14 UTC,Fix released in groovy.
1814109,2019-01-31 16:00:35 UTC,"The issue is with libarchive, installed libarchive-tools and trying to extract the archive with bsdtar gives that"
1814109,2019-01-31 16:04:02 UTC,Reported upstream https://github.com/libarchive/libarchive/issues/1129
1814112,2019-01-31 14:39:49 UTC,"StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=<optimized out>) at ../../../../glib/gslice.c:538
 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=1) at ../../../../glib/gslice.c:841
 g_slice_alloc (mem_size=mem_size@entry=32) at ../../../../glib/gslice.c:1015
 g_slice_alloc0 (mem_size=mem_size@entry=32) at ../../../../glib/gslice.c:1050
 g_type_create_instance (type=<optimized out>) at ../../../../gobject/gtype.c:1846"
1814112,2019-03-19 19:39:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814113,2019-01-31 15:00:04 UTC,This change was made by a bot.
1814113,2019-02-11 17:55:24 UTC,"I'm facing the same issue in KDE Neon, I ran the usual package updates in Muon around 2 weeks back and now I see this error message every time I update or install a new package."
1814118,2019-12-05 01:17:26 UTC,These two packages were tested on Ubuntu 18.04 for armhf in a Raspberry Pi 3b
1814118,2020-01-16 11:40:30 UTC,This bug was fixed in the package rpi.gpio - 0.6.5-1ubuntu0.18.04.1
1814118,2020-01-16 11:40:22 UTC,"The verification of the Stable Release Update for rpi.gpio has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1814118,2020-01-16 11:39:46 UTC,"Excellent, thank you for the verification. Let me adjust the tags and release (the tags need to be set as otherwise we could not see that the fix has been verified)."
1814118,2019-10-21 19:29:23 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1814118,2019-06-25 17:03:55 UTC,"I have sponsored the backport to bionic, since even though this is certainly not a priority, we do support arm64 on Pi3 officially for this series - so it would be good to have things working there."
1814118,2019-03-16 20:25:06 UTC,"Subscribing Łukasz, he sponsored this the last time and is also on the SRU Team (so he can examine its suitability for a stable release)."
1814118,2019-03-14 16:16:46 UTC,SRU: debdiff from current bionic (0.6.3-1ubuntu5) to disco (0.6.5-1ubuntu1) attached.
1814118,2019-02-05 18:21:46 UTC,Sponsored.
1814118,2019-02-05 18:20:49 UTC,"The package looks good and I guess I'll just sponsor it as is. For a moment I was wondering about proposing a small change to the relevant patch: since currently when we're able to open /proc/device-tree/system/linux,revision but are not able to read the contents, the patch forces an error. Was thinking that maybe we should fall-back to the cpuinfo check in this case as well. But then, I suppose that if the linux,revision is openable but unreadable, that's actually a bug and maybe one should actually error out. Besides, this might make the code less clean as for handling an edge-case. Might be worth considering, but I now lean towards just releasing this to disco as-is."
1814118,2019-07-22 15:15:44 UTC,"Hello Dave, or anyone else affected,"
1814120,2020-10-05 03:47:46 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1814120,2019-02-25 13:19:36 UTC,Please attach dmesg under the test kernel.
1814120,2019-02-27 05:10:30 UTC,"[   34.784492] Bluetooth: Can't change to loading configuration err
[   34.784572] ath3k: probe of 2-4:1.0 failed with error -110"
1814120,2019-02-22 13:41:32 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1814120/"
1814120,2019-01-31 15:30:07 UTC,This change was made by a bot.
1814120,2019-02-22 21:31:57 UTC,"Problem is still exists, even after installing and rebooting."
1814123,2019-06-07 20:23:04 UTC,This looks to be out of date. Feel free to reopen if still an issue.
1814125,2019-03-27 13:25:19 UTC,"As a PRIME (NVIDIA+Intel) user, I would be happy to help you test but I don't know how to trace the events."
1814125,2019-03-27 14:16:21 UTC,"PRIME Sync on/off changes:
__GL_MaxFramesAllowed=1 unset:
g-c-c bluetooth animation - 85% -> 30%
dragging windows - 85% -> 40%"
1814125,2019-03-27 14:03:31 UTC,"With glxgears, I get spikes up to 3% without moving the mouse and 4% while moving the mouse. This is a massive improvement (mr281 + mr363). My desktop feels very fast!"
1814125,2019-03-27 14:00:39 UTC,"With mr363 and mr281 (minus the first commit of 281), moving the mouse spikes the CPU up to 3% and then settles down. dragging windows around spikes CPU usage up to 10% but then immediately goes back to 0% once the dragging stops."
1814125,2019-03-27 13:58:55 UTC,"@Maik I think you should also try with or without PRIME Synchronisation, just in case."
1814125,2019-03-27 13:51:09 UTC,"Doing some more testing on the desktop system, this now gets weird and weirder. My desktop is also effected by this, just not when running glxgears, I bought a bluetooth dongle to have the circle animation.
gnome-shell cpu usage:
Threaded swap wait enabled - Desktop:
glxgears - normal, no cpu spikes
g-c-c bluetooth animation - 85% cpu
dragging windows - 85%cpu"
1814125,2019-03-27 12:02:00 UTC,A quicker fix for people might just be to use:
1814125,2019-03-26 10:17:37 UTC,"https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-KDE-High-CPU-Fix
gnome-shell-3.32.0+mutter-3.32.0
Setting __GL_MaxFramesAllowed=1 returns cpu usage to normal when running glxgears or opening the bluetooth pane. Mystery solved?"
1814125,2019-03-27 09:37:19 UTC,"Leo, I can confirm that setting __GL_MaxFramesAllowed=1 also mitigates gnome-shell freezes in startup animations. The icon zoom animation would sometimes freeze for some seconds when starting an application from the dash. Just as additional info."
1814125,2019-03-27 01:32:37 UTC,Although not entirely the same.
1814125,2019-03-27 01:22:15 UTC,"The fix in comment 81 sounds the same as what this does:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/281"
1814125,2019-03-26 21:13:58 UTC,"Interesting, so GNOME is also affected by this glXSwapBuffers misimplementation?
Furthermore, setting this environment variable also fixes some big freezes that I had with GNOME Shell (or Mutter ?) 3.32."
1814125,2019-03-27 15:02:15 UTC,"Now applied mr363+mr281, results are mixed:
Desktop:
g-c-c bluetooth animation - 85% -> 9% Good!
dragging windows - 85% -> 75% slightly better"
1814125,2019-02-28 21:23:55 UTC,Even just the small circle animation in the g-c-c bluetooth pane puts gnome-shell to constant 85% cpu usage.
1814125,2019-02-28 21:20:50 UTC,"Ok, nvidia driver 418.43, gnome-shell 3.31.91 + mutter 3.31.91 freshly built without any additional patches.
Running only glxgears in a small window, not anything else open, not touching anything, gnome-shell cpu usage spikes to 85%."
1814125,2019-02-25 01:52:40 UTC,"OK, thanks."
1814125,2019-03-27 09:47:41 UTC,"Yes, it sounds like a good theory that COGL_FRAME_EVENT_SYNC/COGL_FRAME_EVENT_COMPLETE are missing/invalid in hybrid/PRIME setups. Someone should test that. Maybe me when I get time :)"
1814125,2019-03-27 20:51:31 UTC,"On the desktop system with single nvidia gpu, I can only second Hussam: it's a blast when using mutter-3.32 plus both patches. Snappy, fast, great user experience.
Great work Daniel, thank you.
In the prime sync case, mutter obviously somehow derails taking different code paths."
1814125,2019-04-03 10:21:15 UTC,"Daniel, re-reading your comment, I think I might have misunderstood you. So I now restested the following setup:
Single GPU, mutter-3.32+mr216 only (mr363+mr281 left out)
I can confirm that this setup also fixes this specific bug ( High cpu while constant rendering) but only this. (mr363 also fixes high cpu on mouse movement.)"
1814125,2019-03-28 01:46:02 UTC,"I almost forgot, dragging windows is extra expensive with the Nvidia driver:"
1814125,2019-02-24 12:21:43 UTC,"OK. I just removed graphics PPA, removed nvidia 415, then installed nvidia 390. rebooted.
same again : gnome shell eats 100% CPU when screen is locked and seconds are displayed !"
1814125,2019-07-22 05:10:16 UTC,"Although the linked upstream fix is coming in GNOME 3.34 for Ubuntu 19.10, I have still marked this bug as 'Won't Fix'. That's because I am not completely confident this is the right downstream bug for what was fixed upstream."
1814125,2019-07-22 04:09:51 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1814125,2019-06-07 19:48:24 UTC,Closed via https://gitlab.gnome.org/GNOME/mutter/merge_requests/363
1814125,2019-06-03 17:23:17 UTC,"Tested mutter 3.32.2 +MR281+520+576(-1Hunk)+602 on the single gpu system, runs fine. No noticeable issues until now. Due to the removal of threaded wait moving windows is also back to normal/expected cpu usage now."
1814125,2019-05-31 15:33:54 UTC,"I now tested on my Optimus system using PRIME sync with __GL_MaxFramesAllowed unset using mutter/gnome-shell-3.33.2+MR602.
The good news is, while previously MR363 had no effect on CPU usage while constantly rendering on this system, MR602 now fixes it. CPU usage on bluetooth-pane circle is ~12%.
The bad news, unrelated to this bug is that without setting __GL_MaxFramesAllowed=1 on PRIME sync, mutter is stuttering and intermittently freezing. Let alone still being laggy with or without that setting."
1814125,2019-05-31 11:12:29 UTC,"Nevermind, didn't get that MR602 includes MR363."
1814125,2019-03-28 01:41:29 UTC,"Maik,"
1814125,2019-05-31 11:04:48 UTC,"Thanks again, Daniel.
Unfortunately, I'm unable to apply MR602, tried mutter 3.32.2+MR363, mutter 3.33.2+(rebased)MR363 and mutter-HEAD+(rebased)MR363
Any prerequisite I'm missing?"
1814125,2019-04-29 02:16:42 UTC,"I think there's a reasonable chance this bug is the same as:
https://bugzilla.gnome.org/show_bug.cgi?id=781835"
1814125,2019-04-12 03:17:14 UTC,My mistake. If you ever do experience the problem fixed by:
1814125,2019-04-04 01:29:51 UTC,Maybe I need to provide a backport for older mutter releases?
1814125,2019-04-04 01:28:39 UTC,"Thanks, that is very encouraging because mr216 would explain the root cause here, and why the bug randomly affects some Nvidia systems sometimes and not others."
1814125,2019-04-03 09:27:26 UTC,"Of course, this is now mutter-3.32.0+mr216+mr363+mr281."
1814125,2019-04-03 09:20:20 UTC,"Just to put it straight:
- mr363 fixes this bug on single GPU systems
- mr363 does not have any effect on hybrid GPU systems using PRIME sync
- __GL_MaxFramesAllowed=1 is a workaround on PRIME systems currently."
1814125,2019-04-03 08:45:08 UTC,Random thought: This might be the real root cause:
1814125,2019-05-31 08:33:45 UTC,"And an extra, final nail in the coffin for this bug:"
1814125,2019-02-20 02:04:37 UTC,"OK. Since the problem seems to be in the Nvidia-415 driver, and that driver is not part of Ubuntu then this bug is not a valid Ubuntu bug right now. Sorry."
1814125,2017-05-12 01:17:09 UTC,"(In reply to Frank from comment #11)

> (In reply to Peet from comment #10)
> > I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and
> > latest mutter release the high cpu usage is finally gone. Also the
> > animations are back to normal as in having very smooth animations and window
> > movements, whatever. I am not sure if it's the NVIDIA release or mutter
> > which has included a fix but I would assume that NVIDIA has somehow fixed
> > the locking issue.
>
> The update to mutter-3.24.2 (ArchLinux) has not resolved the issue for me.
"
1814125,2019-02-19 02:25:47 UTC,OK. Does the bug still happen if:
1814125,2017-05-12 12:58:30 UTC,"(In reply to alecdc272 from comment #14)

> (In reply to Peet from comment #10)
> > I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and
> > latest mutter release the high cpu usage is finally gone. Also the
> > animations are back to normal as in having very smooth animations and window
> > movements, whatever. I am not sure if it's the NVIDIA release or mutter
> > which has included a fix but I would assume that NVIDIA has somehow fixed
> > the locking issue.
>
> The Mutter 3.24.2 and Nvidia 381.22 updates have not fixed the issue for me
"
1814125,2017-05-12 12:55:30 UTC,"The nvidia changelog says:
""Disabled OpenGL threaded optimizations by default, initially enabled in 378.09, due to various reports of instability.""
Could this be related?"
1814125,2017-05-12 12:26:57 UTC,"(In reply to Peet from comment #10)

> I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and
> latest mutter release the high cpu usage is finally gone. Also the
> animations are back to normal as in having very smooth animations and window
> movements, whatever. I am not sure if it's the NVIDIA release or mutter
> which has included a fix but I would assume that NVIDIA has somehow fixed
> the locking issue.
"
1814125,2017-05-12 01:44:53 UTC,I use the nvidia-340.102 legacy drivers which is up-to-date.
1814125,2017-04-27 13:41:23 UTC,"As per bug 779039#c14, this checkin https://git.gnome.org/browse/mutter/commit/?id=383ba566bd7c2a76d0856015a66e47caedef06b6 makes gnome-shell use ~80% cpu of one core out of 4 (I am running a skylake corei5) constantly when running something like glxgears."
1814125,2017-05-12 00:05:39 UTC,"(In reply to Peet from comment #10)

> I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and
> latest mutter release the high cpu usage is finally gone. Also the
> animations are back to normal as in having very smooth animations and window
> movements, whatever. I am not sure if it's the NVIDIA release or mutter
> which has included a fix but I would assume that NVIDIA has somehow fixed
> the locking issue.
"
1814125,2017-05-11 23:01:04 UTC,"I am on ArchLinux and it seems that with the new NVIDIA release (381.22) and latest mutter release the high cpu usage is finally gone. Also the animations are back to normal as in having very smooth animations and window movements, whatever. I am not sure if it's the NVIDIA release or mutter which has included a fix but I would assume that NVIDIA has somehow fixed the locking issue."
1814125,2017-05-12 16:25:39 UTC,This is was my recent upgrade:
1814125,2017-05-07 10:00:50 UTC,"Same for me, this is a really annoying issue."
1814125,2017-05-03 01:51:44 UTC,I've been experiencing sluggish animations in gnome-shell after updating to v3.24.1 on ArchLinux on my laptop with dedicated Nvidia GPU (NVS 5100M); no integrated GPU is present.
1814125,2017-04-29 18:44:20 UTC,I am seriously wondering why no devs have noticed this yet. This bug seems to affect literally everyone who uses an NVIDIA gpu.
1814125,2017-04-28 17:39:11 UTC,"(In reply to Maxim from comment #4)

> I make a screenshot of cpu usage before and after  applying
> Call-coglxlibrenderersetthreadedswapwaitenabled.patch
> http://storage4.static.itmages.ru/i/17/0411/h_1491948046_9928347_1598f98b62.
> png
>
>
> I also noticed that this patch have improved responsiveness when moving
> windows. But now, the animations of the Gnome Shell to lag even more. Now
> without the load on the CPU, the decrease in FPS became visible. This is all
> tested on a proprietary Nvidia + 650GTX.
"
1814125,2017-04-27 22:18:42 UTC,"I make a screenshot of cpu usage before and after  applying
Call-coglxlibrenderersetthreadedswapwaitenabled.patch
http://storage4.static.itmages.ru/i/17/0411/h_1491948046_9928347_1598f98b62.png"
1814125,2017-04-27 18:44:19 UTC,I have also encountered this issue on the Nvidia proprietary driver. Reverting the patch fixes the problem.
1814125,2017-04-27 18:36:03 UTC,"I can also confirm this issue, gnome-shell hits around 80% CPU usage on one core when running glxgears, It also causes stuttering in all games I have tried as well. Reverting the patch mentioned by Hussam brings the CPU usage back down to normal levels."
1814125,2017-04-27 13:46:22 UTC,I forgot to mention that I had asked a nvidia developer about this and he said it was due to the overhead of many xlib calls.
1814125,2017-05-03 02:06:35 UTC,"(In reply to Frank from comment #7)

> I've been experiencing sluggish animations in gnome-shell after updating to
> v3.24.1 on ArchLinux on my laptop with dedicated Nvidia GPU (NVS 5100M); no
> integrated GPU is present.
>
> The previous Gnome version did not show this behaviour.
>
> I reverted the commit:
> https://git.gnome.org/browse/mutter/
> commit?id=383ba566bd7c2a76d0856015a66e47caedef06b6
> as mentioned by somebody on the Arch Forums and this fixed the issue for me.
"
1814125,2017-05-12 16:31:07 UTC,Not resolved for me too.
1814125,2019-02-19 11:16:25 UTC,"disabled nvidia gpu in nvidia-settings (and rebooted)
 without any application : OK
 with just a firefox empty private browsing window : OK
 with a normal firefox (many tabs & plugins) : OK
 many apps running : OK
enabling nvidia GPU, rebooted
 without any application : KO"
1814125,2017-05-18 16:24:19 UTC,"Hi, I'm a Manjaro user. I was redirected to here from Manjaro Forum and I think I have the issue explained here, and if it's true, I have something to add."
1814125,2019-02-18 10:08:36 UTC,Thanks. In that case I am going to declare this bug invalid for 'gnome-shell'. But we can reopen it for a different component if you can find out which gnome-shell extension was causing the problem.
1814125,2019-02-14 18:42:42 UTC,seems that the bug disappears with all gnome extensions uninstalled.
1814125,2019-02-01 02:29:10 UTC,"If you have any gnome-shell extensions installed, please try uninstalling them and tell us if the problem persists."
1814125,2019-02-01 02:27:55 UTC,"This might be a different issue, but your kernel log is also getting flooded with error messages about the touchpad(?)"
1814125,2019-02-01 01:58:32 UTC,"And remember, this bug is about high CPU only. Other issues should not be discussed here."
1814125,2018-12-04 11:46:44 UTC,Correction: Please DON'T note if the bug affects Xorg or Wayland sessions.
1814125,2018-12-04 10:22:04 UTC,"For those of you who still find reverting commit 383ba566bd7c2a76d0856015a66e47caedef06b6 helps to reduce CPU, can you please note the Nvidia driver version you are using? I've tested some theories today and retested drivers 340 and 390 but can't find any problem. Or at least can't find any problem that's unique to Nvidia."
1814125,2019-02-18 11:08:14 UTC,the bug still happens if I enable seconds display. still no gnome extensions installed.
1814125,2018-11-27 04:03:20 UTC,Just a reminder to all:
1814125,2018-10-26 07:59:21 UTC,"Thank you, Daniel. This specific info destroys my idea:

> Moving GL commands into a new thread is non-trivial (you need to manually set
> up the context so that the commands will work)
"
1814125,2017-05-19 11:38:11 UTC,"(In reply to Eduardo Medina from comment #23)

> It seems the problem is systemd-coredump, it appears with a high CPU usage
> more or less in the same times than GNOME Shell crashed.
"
1814125,2017-05-19 11:08:14 UTC,"I see, I'm collecting all data I can to fill another bug."
1814125,2017-05-19 10:40:22 UTC,That's definitively a different issue. This bug is about high CPU usage cause by mutter/gnome-shell on Nvidia GPUs.
1814125,2017-05-19 10:34:19 UTC,"Created attachment 352150
CPU log from Eduardo Medina's old Toshiba laptop"
1814125,2017-05-18 17:54:25 UTC,"(In reply to Eduardo Medina from comment #20)

> Well, the problem I have is sometimes the environment crashes randomly. It
> recovers perfect after crashing, but when the bug occurs is very annoying.
>
> I couldn't catch any log or message to know what is the exact error, the
> only thing I have clear is the bug runs always when I have an amount of
> windows spreaded through some virtual desktops.
>
> Yes, the bug occurs on Mesa too if it's the same problem I'm responding.
"
1814125,2017-05-18 16:37:36 UTC,"I forgot to say that Wayland looks much more stable than Xorg, but the bug happens on both servers."
1814125,2018-10-26 08:29:43 UTC,"PS:
Daniel, in general I completely agree with you, curently mutter uses too many glFinish and glxWaitVideoSync which are both blocking. The prop. driver to my knowledge needs exactly one glFinish per frame for proper operation so my idea was about using that as efficiently as possible.
A web-search trying to re-find the mentioned article brought up that many gl devs were hitting the same behaviour of the prop. driver and used the same solution I was thinking of.
I didn't look into why mutter uses glxWaitVideoSync so often to wait a little here, wait a little there."
1814125,2017-05-12 16:36:04 UTC,"I am not sure if this can make a difference but, @Léo could you try using nvidia-dkms instead of the nvidia package?"
1814127,2019-02-13 09:56:47 UTC,Fix released in https://review.openstack.org/#/c/635676/
1814131,2019-06-11 18:09:56 UTC,"This is a duplicate bug of 1827250, which explains the issue in more precise details."
1814134,2019-01-31 16:28:46 UTC,"Fixed.
I am using HP Probook 640 G4. Steps I've done was same which I did during Ubuntu 18.04 installation.
BIOS-> Security-> Bios Sure Start:
Uncheck: Boot Keys Protection, Enhance HP Firmware Runtime Intrusion Prevention.., Dynamic Runtime Scanning..."
1814134,2019-01-31 17:56:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814140,2019-05-18 04:17:32 UTC,[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]
1814140,2019-03-18 22:45:45 UTC,"I am getting the same bug on an asus laptop, just an ext4 volume.
put ""nautilus /home/username/recipes"" and I no longer can double click links to folders on desktop.
uncheck that entry, and links start working"
1814140,2019-02-01 17:22:37 UTC,Possibly integration problem of Btrfs & LVM
1814140,2019-01-31 22:33:19 UTC,"Thank you for your bug report, could you add the journal log from a session where you have the issue?
Also note that nautilus 3.30 in disco removed handling of the desktop so technical that issue is deprecated"
1814140,2019-02-01 10:00:21 UTC,"the log has those warnings
'nautilus-deskto[3224]: cannot open folder on desktop, freedesktop bus not ready'"
1814141,2019-02-06 23:53:19 UTC,"Thanks a lot for the hint! The following fixed the problem here:
$ sudo mv /etc/apparmor.d/usr.lib.snapd.snap-confine $HOME/tmp
$ sudo service apparmor restart"
1814141,2019-02-08 13:06:34 UTC,"$ ls -latr usr.lib.snapd.snap-confine
-rw-r--r-- 1 root root 14496 Dec 21  2016 usr.lib.snapd.snap-confine"
1814141,2019-02-08 09:50:44 UTC,Thanks for the report. I created a PR that should fix the issue: https://github.com/snapcore/snapd/pull/6484
1814141,2019-02-07 18:50:03 UTC,Please remove the profile at /etc/apparmor.d/usr.lib.snapd.snap-confine - on Ubuntu the profile with the suffix .real is the one to keep. After removing the profile please restart apparmor.service - things should be back to normal.
1814141,2019-02-07 17:35:44 UTC,My apparmor files are the same as the ones pasted by Marc.
1814141,2019-02-07 11:24:17 UTC,"Ah, I see your point now Jamie, thank you for clarifying that."
1814141,2019-02-07 01:52:53 UTC,"""AFAIK, last time I looked at apparmor_parser, it was smart enough to ignore .dpkg-dist and similar files."""
1814141,2019-02-07 00:25:26 UTC,"I don't know, whether this matters: I still get some apparmor=""DENIED""-messages as shown in the attachment."
1814141,2019-02-06 23:35:46 UTC,According to apt-file usr.lib.snapd.snap-confine.real seems to be from snapd:
1814141,2019-12-09 15:43:18 UTC,Various fixes to remove such stale snap-confine profiles have landed now.
1814141,2019-02-06 16:16:38 UTC,"$ find /etc/apparmor.d/ -name '*snap-confine*'
/etc/apparmor.d/usr.lib.snapd.snap-confine
/etc/apparmor.d/usr.lib.snapd.snap-confine.real
/etc/apparmor.d/local/usr.lib.snapd.snap-confine
/etc/apparmor.d/local/usr.lib.snapd.snap-confine.real
/etc/apparmor.d/cache/usr.lib.snapd.snap-confine
/etc/apparmor.d/cache/usr.lib.snapd.snap-confine.real
/etc/apparmor.d/cache/snap.core.4486.usr.lib.snapd.snap-confine
/etc/apparmor.d/snap.core.4486.usr.lib.snapd.snap-confine"
1814141,2019-02-06 13:56:37 UTC,"AFAIK, last time I looked at apparmor_parser, it was smart enough to ignore .dpkg-dist and similar files."
1814141,2019-02-06 13:47:39 UTC,"What may be happening is there is a .dpkg-dist file in /etc/apparmor.d for snap-confine indicating that the user made changes to it prior to upgrade, upgraded but chose to keep the changed profile instead of the distro profile so now there are missing rules."
1814141,2019-02-06 13:23:23 UTC,"Interesting, thank you for the feedback."
1814141,2019-02-06 12:54:19 UTC,"$ snap version
snap    2.37.1.1+18.04
snapd   2.37.1.1+18.04
series  16
ubuntu  18.04
kernel  4.15.0-43-generic"
1814141,2019-02-06 09:37:36 UTC,"Er, above when I said ""snap info"" I really meant ""snap version"""
1814141,2019-02-06 09:35:34 UTC,I updated one of my machines to disco (taking note of the 4.19 kernel) but I was unable to reproduce this.
1814141,2019-02-05 23:29:20 UTC,I observe a similar behaviour since latest upgrade of snapd (update from around 2019-02-02):
1814141,2019-02-05 23:29:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814141,2019-02-06 21:07:41 UTC,I believe the issue is directly caused by:
1814145,2019-02-05 20:01:10 UTC,package linux-image-4.15.0-45-generic appears to have resolved this issue. I will follow up after further testing.
1814145,2019-02-06 23:09:25 UTC,"This has definitely been resolved with linux-image-4.15.0-45-generic.  Reboots, hot dock / undock, changing the displays in system prefs, etc no longer lock the laptop up."
1814146,2019-06-26 08:27:52 UTC,This bug was fixed in the package spice - 0.14.2-0ubuntu2
1814146,2019-06-21 09:49:05 UTC,"Ok, I also have a spice-gtk upload ready that seems to work, but I'm not triggering all that on a friday :-)"
1814146,2019-06-21 09:20:51 UTC,"[1] breaks some projects rebuilds.
Most are good I think, but we probably need 0.36/0.37 of [2] spice-gtk.
Unfortunately this is complex as the fix is actually in spice-common path but packaged into spice-gtk."
1814146,2019-05-28 12:05:04 UTC,"I'll try to merge a newer spice into Eoan, then we will see if that helps as assumed."
1814146,2019-06-19 11:59:14 UTC,"FYI - there were a few test errors (and there might be more).
For now I have identified a few issue that won't work in the build env and I fixed [1]"
1814146,2019-04-22 15:34:19 UTC,"Unfortunately, after using the system for a couple of days, I received another BSOD in qxldd.sys."
1814146,2019-04-23 17:19:54 UTC,Is https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1824786 a duplicate of this one perhaps?
1814146,2019-04-16 16:59:34 UTC,"Thank you very much for the explanation of how QEMU references libspice, Christian.  One of the reasons my previous response took so long was because I went down the path of compiling QEMU along with libspice, spice-protocl, etc.  Your assessment that it was complex was spot-on, although I learned quite a bit from the experience."
1814146,2019-04-15 06:28:36 UTC,"Hi John,
Qemu links to libspice like this:"
1814146,2019-04-12 15:24:23 UTC,Bear with me.  I'm learning a lot from this experience and think I'm finally getting the idea of building from source on Linux - a new concept to me.
1814146,2019-01-31 22:41:55 UTC,"Looking to the git commit that one reference to the redhat bug
https://github.com/freedesktop/spice/commit/b5479191"
1814147,2019-04-18 22:22:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814150,2019-01-31 18:56:40 UTC,"I thought there was already a launchpad bug for this, but I'm unable to find it."
1814150,2019-08-19 11:18:55 UTC,"I would recommend for the date format to match the OPAC data setting, among other things because of localization. E.g., in Czech both YYYY-MM-DD and YYYY/MM/DD are quite unusual date format and thus they are confusing for users."
1814150,2020-01-23 21:59:41 UTC,See also:
1814150,2020-03-02 18:35:01 UTC,"Firefox for OPAC Self Registration
Chrome for staff Web Client
Evergreen release 3.4.2"
1814151,2019-01-31 23:33:41 UTC,I believe this bug a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663. Please confirm by reviewing that bug to see if your conditions are similar.  At your earliest convenience could you please try the 4.15.0-45 to it it resolves your issue?
1814151,2019-01-31 18:30:07 UTC,This change was made by a bot.
1814160,2019-03-14 17:37:31 UTC,"The same thing happened for our ""other"" production cloud during its Pike -> Queens upgrade last Tuesday. `local_ip` in linuxbridge_agent.ini got misconfigured with each infra host's br-mgmt IP rather than br-vxlan IP."
1814164,2019-05-14 14:43:22 UTC,"Ryan,"
1814164,2019-05-21 21:04:08 UTC,I am also able to the above steps via the API and I don't have any issues.  Marking invalid until more steps are given.
1814164,2020-04-21 14:21:37 UTC,"This bug also hit us in MAAS version: 2.4.2 (7034-g2f5deb8b8-0ubuntu1).
After upgrading to MAAS version: 2.6.2 (7841-ga10625be3-0ubuntu1~18.04.1) I can still reproduce it in a slightly different scenario. In this scenario the update of dnsresource fails:"
1814164,2020-06-21 04:17:32 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1814172,2019-09-12 14:14:40 UTC,Does this bug still occur on latest code? If yes - please upload new logs.
1814172,2019-11-12 04:18:26 UTC,[Expired for kolla because there has been no activity for 60 days.]
1814177,2019-03-24 23:39:19 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1814177,2019-03-22 03:44:11 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1814177,2019-03-04 16:37:01 UTC,"Reviewed:  https://review.openstack.org/640595
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=40771bc155fe28977c805aed5f60b5d84b1ac2bc
Submitter: Zuul
Branch:    stable/rocky"
1814177,2019-01-31 22:21:23 UTC,Looks like we already hit this once with bug 1704392.
1814177,2019-02-23 06:33:16 UTC,"Reviewed:  https://review.openstack.org/634334
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=03e4e3ce1357123f9f53a3901a17a64f160653a4
Submitter: Zuul
Branch:    master"
1814177,2019-01-31 22:39:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634334"
1814177,2019-01-31 22:25:45 UTC,The difference since that bug was fixed is the check here:
1814177,2019-03-02 14:38:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640595"
1814178,2019-02-04 19:53:53 UTC,"Once I used ""juju update-series"" before trying to use ""juju ssh app/N  -- sudo juju-updateseries ..."" things worked."
1814178,2019-01-31 22:33:46 UTC,Are you updating the series from a client or from the machine itself? The client is required to help manage the flow as the agent will go down and restart. I'm not sure it's viable to do it from the machine you're actually upgrading?
1814178,2019-01-31 22:35:48 UTC,"Actually, you've bypassed the upgrade series feature entirely from what I can see here."
1814178,2019-01-31 23:01:25 UTC,"On Thu, 2019-01-31 at 22:35 +0000, Richard Harding wrote:

> Actually, you've bypassed the upgrade series feature entirely from
> what
> I can see here.
>
> Please see https://docs.jujucharms.com/2.5/en/upgrade-series and let
> me
> know if I'm misunderstanding your issue. Marking incomplete pending
> feedback.
"
1814183,2019-02-04 14:57:24 UTC,For the staff that have created a item copy bucket with a duplicating item row deleting one of the duplicates results in the other one remaining. Staff reported this issue today and several rows had 4 duplicates per barcode. This would require four deletes per each barcode to remove the one row displayed.
1814183,2019-02-08 15:14:40 UTC,Related Bug #1771568
1814183,2019-03-05 14:57:09 UTC,PINES suggests that when an item is scanned or added to a bucket multiple times that it is only added and counted once. No error message would be needed alerting staff since it doesn't negatively effect workflow for the item not to be counted or displayed in the bucket every time it is scanned.
1814183,2019-09-16 15:12:03 UTC,"I have a branch forthcoming that will add a ""duplicate check and exclude"" option to the container item creation API that can be used to silently ignore requests to add duplicate items to a bucket (of any type).  I'll update here when that's pushed, so that once committed it could be used to avoid duplicate additions in specific interfaces."
1814183,2019-09-30 15:56:54 UTC,"UGH. Nevermind comment #5, wrong bug.  Sorry for the noise."
1814187,2019-11-05 02:51:25 UTC,"I had the same issue, and installing mokutil fixes it for me too. Thanks @arndbehring!"
1814187,2020-10-12 12:08:34 UTC,"This this bug still stands upgrading to #groovy Gorilla the next 20.10 release, thanks @arndbehring, it's all in his fix."
1814187,2019-02-10 12:04:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814187,2019-02-10 13:01:24 UTC,I've also encountered this problem while installing updates on Ubuntu 18.04.2.
1814188,2019-04-09 22:09:50 UTC,Add some marker to the line and not just different colors. The markers could improve the identification if the graph was printed in black-and-white.
1814188,2019-03-21 13:20:44 UTC,"I already propose:
1) Current and power probe measure
https://bugs.launchpad.net/kicad/+bug/1740321
2) In sheet graph
https://bugs.launchpad.net/kicad/+bug/1740318"
1814188,2019-03-21 14:21:14 UTC,"Also a future interactive simulation
https://bugs.launchpad.net/kicad/+bug/1758234
but, this could be the last improvement of all. Since this will need a change in the simulation paradigm."
1814188,2019-11-06 20:13:59 UTC,Pt. 11 is a duplication of:
1814188,2019-11-21 01:48:57 UTC,"@Evan, can you please split each of these enhancement requests into separate bug reports. That allows easier tracking of each item as it is implemented."
1814191,2019-10-31 03:47:04 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1814192,2019-02-05 18:51:02 UTC,Hi Galen
1814192,2019-02-01 16:15:49 UTC,Hi Galen
1814192,2019-02-01 15:59:52 UTC,"Since a lot of online services let users update their email addresses, I'm wondering what the motivation is for this wishlist item. Are you seeing cases where patrons are intentionally or unintentionally setting their record to the wrong address?"
1814192,2019-02-01 20:49:42 UTC,Thanks for the additional information. (And I guess there's no need to recapitulate the debate about official vs. unofficial email addresses for college students. :-) )
1814193,2019-02-04 11:31:44 UTC,"Hi,
In general I first have to agree that the openvpn services are a bit of a mess.
The deduplication of the openvpn services is a known and ongoing issue [1].
That requires to merge both of them and create sort of a best of both worlds approach."
1814201,2019-02-01 07:34:52 UTC,"What's ""juju storage --format yaml"" for that model ? You can find more info about the model with : db.models.find({""uuid"": <model-uuid>})"
1814201,2019-08-28 21:30:12 UTC,Marking this as incomplete and see if we can find a repro with the additional details Junien notes would be useful in chasing it down better.
1814201,2019-10-31 02:44:00 UTC,"Removing milestone since this is Incomplete. If we do not get additional information, this bug will expire."
1814201,2019-12-30 04:17:44 UTC,[Expired for juju because there has been no activity for 60 days.]
1814207,2019-02-02 00:30:04 UTC,This change was made by a bot.
1814207,2019-02-02 00:21:30 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1814209,2019-09-17 12:43:24 UTC,I've seen the same issue on a deployment that had been upgraded to Queens and was using a cluster of three RabbitMQ servers for messaging.
1814209,2019-03-14 17:23:14 UTC,I'm confused.  Were all of your neutron-server processes restarted?  It almost seems like there is one running on an older version and still publishing to the wrong exchange.
1814209,2019-02-01 06:36:11 UTC,"Neutron versions:
python-neutron-12.0.4-1.el7.noarch
python2-neutronclient-6.7.0-1.el7.noarch
python2-neutron-lib-1.13.0-1.el7.noarch
openstack-neutron-common-12.0.4-1.el7.noarch
python-neutron-lbaas-12.0.0-1.el7.noarch
openstack-neutron-ml2-12.0.4-1.el7.noarch
openstack-neutron-openvswitch-12.0.4-1.el7.noarch
openstack-neutron-12.0.4-1.el7.noarch
openstack-neutron-lbaas-12.0.0-1.el7.noarch"
1814209,2019-02-05 11:53:19 UTC,What patch?
1814209,2019-02-04 18:49:29 UTC,I suspect that there may be some patch missing to get into this state.
1814209,2019-03-08 13:23:41 UTC,"I'm also affected by this bug, it seems."
1814214,2020-10-20 14:19:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814216,2020-06-07 04:17:26 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1814226,2020-05-04 15:09:58 UTC,Based on the bugzilla linked in the report the solution for this is merged upstream in 17.0.9 but I did not find it in the git log. Based on the code on master the attached patch was never applied. @Matthew Booth: do you still think there is something to be fixed in nova?
1814226,2020-07-04 04:17:33 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1814231,2020-03-05 18:34:12 UTC,Powerpc hung on vfat stress using the 5.3.0-42.34 eoan kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/ppc64el/l/linux/20200229_025412_feca6@/log.gz
1814232,2019-11-21 10:33:09 UTC,"BTW it's instance a1.large, and the error message is a bit different:"
1814232,2019-11-21 10:31:54 UTC,Failed on AWS X-4.15 ARM64 (it's only failing on ARM64)
1814232,2019-06-04 06:03:37 UTC,CPU hotplug for Azure has been enabled in https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821934
1814232,2019-03-13 09:28:12 UTC,"BTW, the CONFIG_HOTPLUG_CPU for azure was disabled in bug 1776293"
1814232,2019-03-12 06:53:11 UTC,"This will need to CONFIG_HOTPLUG_CPU=y, which was not set on Azure kernel."
1814237,2019-04-19 11:04:28 UTC,Probably a dup with bug 1822247.
1814237,2019-02-01 10:07:49 UTC,"I can see this test has passed with 4.15.0-44.47~16.04.1, so this might be a regression."
1814237,2019-02-01 10:17:51 UTC,Can we re-run this to see if it's 100% reproduceable?
1814237,2019-02-01 10:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1814237,2019-02-01 10:52:57 UTC,Some more useful info:
1814237,2019-03-22 19:44:00 UTC,"This bug appeared to surface on aws Bionic linux-aws  kernel-version"": ""4.15.0-1035.37"", AMD64
We also see this occurring on arm64 instances a1.medium so it does not appear to be arch specific."
1814237,2019-04-18 18:34:11 UTC,"Affects , 4.15.0-1036.38~16.04.1 linux-aws-hwe"
1814238,2019-02-02 04:11:28 UTC,OK... there is at least one sequence that does this.
1814238,2019-02-01 17:18:02 UTC,Thanks for the report! We should definitely fix this!
1814240,2019-02-01 10:30:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1814243,2019-02-01 10:44:04 UTC,Did you switch terminals in between or reset it?
1814243,2019-02-01 13:17:01 UTC,"> Did you switch terminals in between or reset it?
"
1814245,2020-01-27 19:18:41 UTC,"Reviewed:  https://review.opendev.org/683008
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8396dcae3eee4bdf7d2d5b4d0cc0f9b58d16117
Submitter: Zuul
Branch:    stable/pike"
1814245,2019-09-18 23:30:56 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/683008"
1814245,2019-03-24 23:39:33 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1814245,2019-03-22 03:44:03 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1814245,2019-03-15 23:52:46 UTC,"Reviewed:  https://review.openstack.org/637827
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=013f421bca4067bd430a9fac1e3b290cf1388ee4
Submitter: Zuul
Branch:    stable/queens"
1814245,2019-03-24 23:04:12 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1814245,2019-02-19 11:54:05 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/637827"
1814245,2019-02-14 10:15:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/636895"
1814245,2019-02-13 23:48:29 UTC,"Reviewed:  https://review.openstack.org/551302
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b626c0dc7b113365002e743e6de2aeb40121fc81
Submitter: Zuul
Branch:    master"
1814245,2019-02-01 15:02:38 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: master
Review: https://review.openstack.org/634398
Reason: As discussed this is wrong as instance.host isn't updated until later in the flow."
1814245,2019-02-01 12:07:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634398"
1814245,2019-02-25 11:58:42 UTC,"Reviewed:  https://review.openstack.org/636895
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=75e0f5a9b18293546db0ddf0fb073854e6704115
Submitter: Zuul
Branch:    stable/rocky"
1814246,2019-09-18 17:26:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814246,2019-09-18 17:34:37 UTC,failed because exfalso / quodlibet requires mutagen version 1.34 - aur installs version 1.30
1814248,2019-08-20 01:34:50 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1814250,2019-02-22 15:46:11 UTC,This bug should be fixed by https://review.openstack.org/#/c/634399/
1814250,2019-02-28 11:45:11 UTC,"I don't think the error is the bridge. If the bridge is not there, the error is ""Cannot find device ""br-ex""'.
I could reproduce the error by passing the argument with quotes"
1814250,2019-02-28 12:11:04 UTC,"This error happens in all the jobs, even the ones that succeed, so it's not fatal"
1814250,2019-02-28 16:30:27 UTC,"I tried to investigate a bit more, I think when the command is formed on os-net-config and oslo_concurrency.processutils.execute is called with the string that form the command, it may be espaping or quoting the strings inside the parameters after ""ip"". So the command never runs correctly"
1814254,2019-02-06 20:23:40 UTC,This bug was fixed in the package net-snmp - 5.7.3+dfsg-5ubuntu1
1814254,2019-02-01 13:14:42 UTC,I linked the related Debian bug
1814254,2019-02-01 12:56:13 UTC,"Debian added an attempted fix for this in commit https://salsa.debian.org/debian/net-snmp/commit/8b0dce0557add809a9b42e7f37c8d0bb36ec35ee, piggy backing on another unrelated fix."
1814257,2019-07-16 11:25:28 UTC,"Thanks for the workaround! I did see that it used _ in the template names, but didn't occur to me to change it in the code!"
1814271,2019-02-19 05:06:40 UTC,"@Ed Stewart (emcs2),"
1814271,2019-05-07 03:39:26 UTC,We have done a lot of work in removal/destruction area in Juju 2.6.
1814271,2019-05-16 11:44:09 UTC,We have tried to retest this on Juju 2.6RC2 with a slightly different triggering error condition.  In this case it was creating a VM with a floating ip on an Openstack network with no route to the target external network.  Here are the notes from our engineer:
1814271,2019-05-16 22:56:40 UTC,"@Ed Stewart (emcs2),"
1814272,2020-04-15 20:20:52 UTC,"This bug affects me as well. It's preventing me from installing my printer. It is frustrating to see that this bug, and a proposed fix, have been around for over a year with no fix."
1814272,2020-10-12 12:58:25 UTC,"I moved the added lines to be applied only when the file is gzipped. If it is a clean ppd, it led to traceback."
1814272,2020-10-13 09:31:07 UTC,Even adding PPD in GUI now works with this patch (GUI hp-setup uses completely different code...).
1814273,2020-12-08 11:37:50 UTC,Should be fixed with latest 2.3 CMake build. Can someone verify?
1814273,2020-08-11 15:05:38 UTC,I installed the latest Redistributable Visual C++ 2015 in version 14.27.29016 or higher from the following page: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
1814273,2020-08-09 22:35:48 UTC,The installer needs to take newer versions of the runtime into account and must either not try to install the MSCV 2015 redistributables or handle the corresponding error correctly:
1814273,2019-12-26 00:00:25 UTC,Same error with 2.2.3
1814273,2019-06-14 23:07:53 UTC,"A user on the forum reported that uninstalling the MSVC2017 runtime is a workaround. Mixxx 2.2 is built with MSVC2015, so it seems that having newer versions of the runtime installed are somehow messing with the installer."
1814273,2019-06-14 23:08:05 UTC,https://mixxx.org/forums/viewtopic.php?p=42140#p42140
1814273,2019-04-29 16:46:19 UTC,what the status of this defect? can we repackage? currently i'm unable to install the latest package or the previous stable
1814273,2019-04-23 19:30:57 UTC,I have a friend getting the same message and checked her computer. She does have microsoft visual c++ redistributable installed. not sure why she is getting this message
1814273,2019-02-03 13:17:39 UTC,"Duplicates?
lp:1813260
lp:1779530"
1814273,2019-12-02 01:25:52 UTC,"I am confirming that this error occurs in 2.2.2, too."
1814281,2019-02-01 16:21:06 UTC,apport information
1814281,2019-02-04 14:27:32 UTC,Set package to subversion
1814281,2019-02-01 16:21:09 UTC,apport information
1814281,2019-02-01 16:21:07 UTC,apport information
1814281,2019-02-01 16:21:05 UTC,apport information
1814281,2019-02-01 16:21:03 UTC,apport information
1814281,2019-02-01 16:21:02 UTC,apport information
1814281,2019-02-01 16:21:01 UTC,apport information
1814281,2019-02-01 16:21:00 UTC,apport information
1814281,2019-02-01 16:20:58 UTC,apport information
1814281,2019-02-01 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1814286,2019-02-04 17:38:34 UTC,"Robert Caulk said:     (by the date of Mon, 04 Feb 2019 17:07:16 -0000)"
1814286,2019-02-04 17:57:00 UTC,I checked on debian Buster (inside chroot). The problem is also present there.
1814286,2019-02-04 18:58:49 UTC,"Bruno Chareyre said:     (by the date of Mon, 04 Feb 2019 18:39:36 -0000)"
1814286,2019-02-04 19:02:49 UTC,Just have a look at errors produced by imgmath
1814286,2019-02-05 08:49:09 UTC,"Alright, I think I figured out the problem. See [1] and the solution [2]. He adds the latex macros (\def, \let, \newcommand, etc) to his layout.html. I will try this today and report back :-)"
1814286,2019-02-05 09:32:12 UTC,"Ok, let us know Robert."
1814286,2019-02-05 12:23:19 UTC,"aah, so it's entire preamble. No wonder that my simple \newcommand
replacement did not work. Congrats on finding this! :)"
1814286,2019-02-05 15:58:08 UTC,"[1] replaces \vec by \boldsymbol using Robert's trick in layout's preamble.
To me it sounds like a dirty trick to define latex conventions in the layout of web pages but there seem to be no other option."
1814286,2019-02-04 17:30:32 UTC,"Sorry for causing those problems. Yes, I did not check this
change on older distributions."
1814286,2019-02-05 15:59:57 UTC,"I did not follow all commits.
Were there changes in the latex_preamble used for building the pdf (ther should not, I would think)?
B"
1814286,2019-02-05 16:52:03 UTC,"in formula (3) and (4) I guess that the problem is with \rm, not something else..."
1814286,2019-02-05 17:29:52 UTC,I think we can merge the branch now (without deleting it) since it fixes a number of problem online already. Right?
1814286,2019-02-05 18:05:24 UTC,agreed. Let's merge it. It will be useful in my branch where I add more text to documentation ;)
1814286,2019-02-05 18:07:00 UTC,I think rebasing will work now :) Unless Robert will happen to have a conflict in lib/triangulation/FlowBoundingSphereLinSolv.ipp which is in the first commit in this branch. Let us know!
1814286,2019-02-05 18:32:11 UTC,It’s ok to merge that full commit including flowboundingsphere.
1814286,2019-02-05 19:43:16 UTC,Moved from https://bugs.launchpad.net/yade/+bug/1814286 to https://gitlab.com/yade-dev/trunk/issues/51
1814286,2019-02-05 13:29:16 UTC,It looks better and better! :)
1814286,2019-02-04 17:07:16 UTC,">>Hmm, this search in Buster indicates that pngmath is still there,
am I missing something?
"
1814286,2019-02-04 18:39:36 UTC,"It sounds like the pragmatic move is to replace the macros by what they mean. Search & replace should work, and I think there are very few pages where those macros are used (if not just one page).
Bruno"
1814286,2019-02-04 16:43:29 UTC,"Anton Gladky said:     (by the date of Fri, 01 Feb 2019 17:46:29 -0000)"
1814286,2019-02-01 16:18:15 UTC,"In fact, it looks like the compiler is ignoring \defs. For example:"
1814286,2019-02-01 16:43:15 UTC,"Ok, after downloading the artifacts from the build, the PDF is built perfectly fine."
1814286,2019-02-01 16:45:51 UTC,"The problem appeared in [1].
Maybe it fixed the new sphinx while breaking the older one?
B"
1814286,2019-02-01 16:48:03 UTC,"Ah, it is probably worth moving away from pngmath. I guess we just need to rewrite the \defs to accommodate mathjax?"
1814286,2019-02-01 16:56:15 UTC,"Before 34fb5ffef all equations in the html were retrieved from png files.
With ""mathjax instead of pngmath"" they are replaced by inline code, which actually works for some of them, but not all of them.
You probably found why (#1)."
1814286,2019-02-01 17:05:25 UTC,Maybe http://docs.mathjax.org/en/latest/misc/faq.html#does-mathjax-support-tex-macros
1814286,2019-02-01 17:20:19 UTC,"Yes, Mathjax seems cleaner. Does it result in better resolution of math on the web. The old equations used to look grainy with pngmath iirc."
1814286,2019-02-01 17:46:29 UTC,"Hi guys,"
1814286,2019-02-01 17:50:03 UTC,"> Is there a way to test changes and their effect on the website without
> merging to develop branch?
"
1814286,2019-02-04 16:47:35 UTC,"Yes, I had the same errors locally with imgmath: https://yade-dev.gitlab.io/-/trunk/-/jobs/156037536/artifacts/public/formulation.html"
1814286,2019-02-01 20:31:09 UTC,"Right of course. I am doing this right now every 15 minutes, and I
forgot to tell Robert about that ;)"
1814286,2019-02-04 11:41:19 UTC,"There must be a problem in your compile+buildDoc workflow Robert, since on gitlab side the problem clearly appeared with 34fb5ffef.
Let's discuss it directly.
B"
1814286,2019-02-03 18:07:36 UTC,"Strange, I tried reverting that commit [1] and the problem persisted."
1814286,2019-02-03 16:32:22 UTC,"Hm, maybe this means that switching to mathjax breaks build on all older ubuntus. I wonder if it is possible to make this switch dependable on python-sphinx version?"
1814286,2019-02-01 19:25:57 UTC,"This is not website-related. You can simply «make doc» locally and check
html output.
 It is a good opportunity to play with gitlab pipeline, still, but it will
also imply ~8min of full recompile time...
B"
1814286,2019-02-03 16:18:31 UTC,it was this commit actually:
1814286,2019-02-03 15:30:48 UTC,"I am unable to identify the source of the problem. I tried reverting [1] and [2], but the problem persists. I tried changing delimiters, I tried replacing \def with \newcommand (despite the fact that we should not have to, see #12), but the problem persists."
1814286,2019-02-03 09:39:47 UTC,"According to [1], \def and \let should both work fine with mathjax"
1814286,2019-02-03 16:20:48 UTC,"Anton did this when preparing for debian relelase, and there python-sphinx is 1.7.9. Maybe that is related?"
1814287,2020-03-07 15:28:42 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1814288,2019-09-17 13:23:50 UTC,https://review.opendev.org/#/c/682518/
1814288,2019-09-18 13:40:36 UTC,"Reviewed:  https://review.opendev.org/682518
Committed: https://git.openstack.org/cgit/x/sqlalchemy-migrate/commit/?id=5d1f322542cd8eb42381612765be4ed9ca8105ec
Submitter: Zuul
Branch:    master"
1814288,2019-10-22 21:08:09 UTC,This issue was fixed in the x/sqlalchemy-migrate 0.13.0 release.
1814289,2019-06-26 04:17:18 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1814289,2019-02-01 21:04:07 UTC,"If you have scripts that you want to put into the system and have cloud-init execute them, you can put them in /var/lib/cloud/scripts/per-instance/"
1814289,2019-04-26 19:08:37 UTC,"@smoser  IIUC, if Abel were to include"
1814289,2019-04-26 19:09:49 UTC,"That said, it may be interested to extend the runcmd to allow specify a prefix to control where in per-instance-scripts order runcmd is placed."
1814291,2019-02-01 17:08:32 UTC,"From a quick look at the logs, it seems that a lot more time than it should."
1814291,2019-03-27 13:53:04 UTC,A similar issue is also happening with bionic/linux-hwe:
1814295,2019-02-01 17:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1814295,2020-06-05 08:39:58 UTC,Issue found on Precise 3.2 i386 3.2.0-145.192
1814295,2020-04-09 12:55:43 UTC,Issue found on 4.4.0-178.208~14.04.1 with node onza.
1814295,2019-10-31 02:24:27 UTC,Issue found on 4.4.0-167.196~14.04.1 with node onza.
1814295,2019-04-12 20:21:31 UTC,"Hrm, I am unable to reproduce this on i386 in either trusty with lts-xenial or in xenial directly, despite attempting to reproduce the test failure repeatedly."
1814295,2019-05-07 09:25:02 UTC,"Hello,
It looks like this is a bit flaky for i386,
I can see this failure with 4.18.0-19.20~18.04.1-generic on i386 node ""onza"", fail rate 2 out of 3 attempts."
1814295,2019-04-11 08:44:30 UTC,BTW this test has been disabled for PPC
1814295,2019-04-11 08:43:42 UTC,Found on T-LTS-X i386 as well.
1814295,2019-09-30 11:19:45 UTC,Found on 5.0 B-hwe i386 with node pepe.
1814296,2019-02-04 17:30:18 UTC,"Good bug, valid and we can drop this upstream module now as snap module should cover all of these use cases."
1814296,2019-02-09 01:13:34 UTC,"I have spoken too early.
I have problem creating user with snap module, but apart of that specific bug snap module seems to work fine.
So I'm +1 to deprecate snappy module"
1814302,2020-07-16 11:30:09 UTC,This bug was fixed in the package quassel - 1:0.12.4-3ubuntu1.18.04.2
1814302,2020-07-16 08:58:33 UTC,This bug was fixed in the package quassel - 1:0.13.1-3ubuntu2.1
1814302,2020-07-16 08:48:32 UTC,"The verification of the Stable Release Update for quassel has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1814302,2020-07-08 17:33:25 UTC,bionic:
1814302,2020-07-07 23:31:22 UTC,"Hello Yancy, or anyone else affected,"
1814302,2020-07-07 23:30:26 UTC,"Hello Yancy, or anyone else affected,"
1814302,2020-06-30 22:44:20 UTC,This bug was fixed in the package quassel - 1:0.13.1-3ubuntu3
1814302,2019-02-25 12:39:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814302,2020-07-08 17:27:04 UTC,focal:
1814302,2019-07-28 03:01:44 UTC,The above workaround isn't enough to totally resolve the issues with AppArmor and this application inside LXD.  I also had to switch to aa-complain for PostgreSQL migration so features will have to be thoroughly tested to identify it.  I'm willing to setup a secondary instance to do any testing that is necessary but I don't know anything about AppArmor to fix the profile.
1814303,2019-07-25 10:42:48 UTC,Released to stable
1814303,2019-07-01 22:15:39 UTC,Seems the day of changing has come. I am seeing failures such as:
1814303,2019-07-11 02:25:14 UTC,"Released to edge. If someone can confirm the edge channel of cs:grafana is working as intended, I can release it to stable."
1814303,2019-07-25 07:55:57 UTC,"Validated by running:
juju deploy cs:grafana-29
The unit goes into active state."
1814305,2020-08-09 22:35:27 UTC,slack-desktop 3.3.7
1814307,2019-02-01 19:56:42 UTC,I have tried USB and Network.
1814307,2019-02-03 18:24:24 UTC,"> Why i can't install last version hplip on my Ubuntu 18.04.
"
1814307,2019-02-03 18:13:12 UTC,Thanks for you help.
1814307,2019-02-03 17:33:06 UTC,"That addition you made to models is the way to go. There is nothing wrong with it for getting scanning going. (But do you really have it beginning with ""[hp_colorlaserjet_mfp_m278-m281]""? I have made enough slipups dealing with your issue, so maybe I am misinterpreting your earlier journalct output)."
1814307,2019-02-03 16:12:16 UTC,"This show ""  avahi-browse -rt _uscan._tcp > log"":"
1814307,2019-02-02 23:32:34 UTC,I am a little surprised that having
1814307,2019-02-02 22:53:44 UTC,I have add this to my file models.dat and now i can scan:
1814307,2019-02-02 18:06:49 UTC,"> in models.dat put this:
"
1814307,2019-02-02 10:57:40 UTC,"Please forget about printer-driver-postscript-hp; I got confused. Instead, in models.dat put this:"
1814307,2019-02-02 01:23:57 UTC,I haven't line.
1814307,2019-02-02 00:32:37 UTC,I made a mistake. The line is
1814307,2019-02-02 00:42:33 UTC,It is unfortunate but I think you may have hit another bug. This time it is in Ubuntu.
1814307,2019-02-02 00:25:03 UTC,I have open /usr/share/hplip/data/models/models.dat  for change the line but i haven't it.
1814307,2019-02-01 23:57:17 UTC,Aplogies:
1814307,2019-02-01 23:33:33 UTC,Ah! Now we are getting somewhere. Thanks. Let's see how we go on with this:
1814307,2019-02-01 23:09:15 UTC,"This show ""journalctl"":"
1814307,2019-02-01 23:01:53 UTC,Forgot. Also try to scan and look in 'journalctl' at the end of the output.
1814307,2019-02-01 23:01:49 UTC,"This show log ""avahi-browse -art > log"":"
1814307,2019-02-01 22:59:13 UTC,"> cat /etc/sane.d/dll.d/hplip:
> # dll.conf snippet for hplip
> #
? hpaio
"
1814307,2019-02-01 21:07:15 UTC,I prefer use with network. My system is KDE Neon 18.04 but with Ubuntu 18.04 neither run.
1814307,2019-02-01 20:37:49 UTC,You didn't post the log I asked for.
1814307,2019-02-01 20:30:36 UTC,"> I have tried USB and Network.
"
1814307,2019-02-02 00:27:54 UTC,This is my log file from avahi-browse :
1814307,2019-02-01 19:31:35 UTC,Which type of connection do you want? USB or network? Post the outputs of 'lpinfo -v' and 'scanimage -L'.
1814314,2019-08-06 14:28:31 UTC,"This was fixed in https://launchpad.net/ubuntu/+source/nut/2.7.4-9ubuntu1, which is currently in eoan-proposed, and this bug will auto-close once the package migrates."
1814314,2019-08-14 15:29:04 UTC,This bug was fixed in the package nut - 2.7.4-9ubuntu1
1814314,2019-08-07 07:46:16 UTC,The addition of nutscan made it hit the new queue which explains the extra delay.
1814314,2019-02-05 08:28:24 UTC,"Hi fellows,"
1814314,2019-02-05 08:05:04 UTC,"Thanks Raul,
I linked the bug here and subscribed on the Debian bug to see what their opinion on this is.
If nothing happens for quite a while we need to reconsider doing this just on our own, but for now lets see."
1814314,2019-02-04 19:34:03 UTC,"Done.
Upstream is #921379."
1814314,2019-02-04 12:52:23 UTC,"Hi Raul,
I agree that the tool is missing, but this bug is present in Debian too.
And IMHO it would be best fixed in Debian, and then Ubuntu will pick it up on the next merge."
1814314,2019-08-05 09:04:36 UTC,"Our check on potentially dormant bugs brought this one up and I realized that it was recently fixed in 2.7.4-9.
Lets merge that for Eoan ..."
1814321,2019-02-01 21:46:22 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/443058
1814321,2019-02-11 06:51:07 UTC,"Mike, really appreciate your findings
can you let us know what's the version of your SLES? I believe we did some test before on 12.1 and it works , will the new tools you suggested shipped by SLES 12.x and don't need to be installed ? thanks  a lot ~"
1814321,2019-02-11 06:59:23 UTC,"forget above this, I learned this is SLES12SP4 but still curious on why wicked is ok while systemctl doesn't ..."
1814321,2019-02-12 04:58:07 UTC,I am able to duplicate this issue with SLES12SP1.  The problem is resolved with the proposed patch.
1814321,2019-02-12 05:24:59 UTC,"Thanks for the detailed information, let me merge the code first and see why we havn't have the issue later , in the mean time need dig more on the command used.. thanks for the patch"
1814331,2019-02-04 17:02:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814332,2019-07-10 18:37:12 UTC,"Hey George, I think this is now done? https://github.com/charmed-kubernetes/layer-tigera-secure-ee/blob/master/metadata.yaml"
1814332,2019-07-10 18:56:01 UTC,"Yeah, looks like it. Thanks."
1814337,2019-04-23 14:20:59 UTC,"Yes (8.3), please. We need this for testing compilation of our projects with the latest gcc in Travis CI."
1814337,2019-04-07 18:07:46 UTC,Change to GCC 8.3?
1814346,2019-02-01 23:46:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/634517"
1814346,2020-09-23 20:27:29 UTC,"Change abandoned by Vipin Balachandran (<email address hidden>) on branch: master
Review: https://review.opendev.org/634517"
1814347,2019-02-05 20:43:28 UTC,"Vipin, is this fixed now? I seem to remember a patch related to something like this."
1814347,2019-02-06 00:10:00 UTC,"Sean,
No, the fix depends on the following os-brick patch:
https://review.openstack.org/#/c/634508/"
1814349,2019-04-05 16:26:14 UTC,"fundamentally the same issue (I believe) in 2.5.2. My case is slightly different in that I created the hostname from the POD -> compose in the GUI. The GUI accepts the _ (it should flag it! and refuse to proceed) followed by it cheerfully creating the machine ... the virsh name HAS the _ but the MAAS name is self assigned. This mismatch is annoying (admittedly, it's a ""user error"" in that the hostname should follow Linux rules ... but virsh doesn't ... so the resulting mismatch is an operational hazard. The most direct fix (for the GUI) is to enforce the naming requirement. If we can't do that, at the very least we should use the *same name* for MAAS and virsh ... not bifircating. For context, support ticket 00221358"
1814349,2019-05-21 15:45:45 UTC,"Irinia,"
1814349,2020-04-26 04:17:20 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1814351,2019-03-20 20:34:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814352,2019-05-10 16:40:51 UTC,"Thank you, all."
1814352,2019-08-16 02:02:36 UTC,Released as part of v4.1.0.
1814352,2019-04-29 22:15:46 UTC,Please let me know if further work or another patch submission is required.
1814352,2019-05-10 16:40:38 UTC,https://git.qemu.org/?p=qemu.git;a=commit;h=43330b7169ae76222472a4b20c7f4db9d8880527
1814352,2019-04-09 13:51:42 UTC,Your suggested fix looks good -- did you want to send it to qemu-devel with a suitable Signed-off-by: line ?
1814352,2019-04-09 20:16:29 UTC,"On Wed, 10 Apr 2019 at 01:26, Erik Kline <email address hidden> wrote:

> Sure.  Looking at HEAD, and even the surrounding the lines, I think I
> should have tried STRUCT_short_ifreq instead of STRUCT_int_ifreq, though
> I'm not sure what the real difference would be.
"
1814352,2019-04-09 18:18:49 UTC,"Sure.  Looking at HEAD, and even the surrounding the lines, I think I
should have tried STRUCT_short_ifreq instead of STRUCT_int_ifreq, though
I'm not sure what the real difference would be."
1814352,2019-04-23 22:31:37 UTC,Patch sent to the list.  Apologies for the delay.
1814353,2019-02-05 23:03:10 UTC,"@ryouaki. Thanks for sharing the nodejs client. Do you have specific questions about the swift client?
You could take a look at the swift API doc[1] or even the client doc[2] and see if they help. Also we hang out in the #openstack-swift channel on freenode so that could be a good place to ask specific question you might have."
1814353,2019-02-13 02:34:12 UTC,"Yes, thank you for your help. I will read them."
1814353,2019-09-19 08:11:21 UTC,Are you still developing this? I think I could contribute a bit
1814353,2019-09-19 11:33:44 UTC,@Nguyen Quoc Viet (axblueblader)
1814355,2019-02-12 15:40:36 UTC,This bug was fixed in the package initramfs-tools - 0.131ubuntu17
1814355,2019-02-12 13:18:34 UTC,"Also initramfs-tools sets PATH without /usr/local, which may leak into init environment. Fixing this as well."
1814355,2019-02-05 17:10:33 UTC,The release of 2.37.1.1 fixed my issue .
1814355,2019-02-03 18:07:58 UTC,"The verification of the Stable Release Update for snapd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1814355,2019-02-03 15:53:18 UTC,The path is correct again.  Marking as verification-done.
1814355,2019-02-03 15:48:13 UTC,"Ignore the previous comment, I still had the wrong version installed.  Let's try that again..."
1814355,2019-02-03 15:40:49 UTC,After upgrade:
1814355,2019-02-03 15:31:05 UTC,Performing the same tests as mvo.  Before upgrading...
1814355,2019-02-03 18:07:55 UTC,This bug was fixed in the package snapd - 2.37.1.1+18.04
1814355,2019-02-03 12:26:05 UTC,"As for the questions of xnox:
""""""
ubuntu@autopkgtest:~$ sudo systemd-run --unit=check-env /usr/bin/env
Running as unit: check-env.service
ubuntu@autopkgtest:~$ sudo journalctl --no-pager -u check-env
-- Logs begin at Mon 2018-07-23 18:30:47 CEST, end at Sun 2019-02-03 13:25:21 CET. --
Feb 03 13:25:21 autopkgtest systemd[1]: Started /usr/bin/env.
Feb 03 13:25:21 autopkgtest env[543]: LANG=en_US.UTF-8
Feb 03 13:25:21 autopkgtest env[543]: PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin
Feb 03 13:25:21 autopkgtest env[543]: INVOCATION_ID=4c9b05e577224d6284cc641778807a16
Feb 03 13:25:21 autopkgtest env[543]: JOURNAL_STREAM=9:18437
ubuntu@autopkgtest:~$ cat /etc/systemd/system.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See systemd-system.conf(5) for details."
1814355,2019-02-03 15:02:36 UTC,"Hello E., or anyone else affected,"
1814355,2019-02-02 17:28:42 UTC,This is not a duplicate of 1771858 . This a critical regression from update for fixing 1771858 .
1814355,2019-02-02 17:29:30 UTC,"This is related to 1771858 , i agree ."
1814355,2019-02-03 06:53:22 UTC,"agree, cannot deploy Kubernetes charm from canonical, or add Kubernetes-worker units to existing deployment"
1814355,2019-02-02 11:14:48 UTC,likely fallout of the fix from 1771858
1814355,2019-02-03 10:45:48 UTC,"Hi,"
1814355,2019-02-03 12:24:24 UTC,Here is what I see in a clean VM:
1814355,2019-02-03 06:53:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814356,2019-02-04 14:40:22 UTC,"I can't reproduce this. Per https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814355, it looks like it was fixed over the weekend with the release of snapd 2.37.1.1 to bionic-updates. Can you confirm you are no longer experiencing the issue?"
1814356,2019-02-04 21:56:56 UTC,I dont have anymore the issue .
1814356,2019-02-03 06:33:52 UTC,confirmed -- this has broken juju canonical Kubernetes charm.  Cannot deploy new Kubernetes workers with flannel.
1814362,2019-02-04 20:17:02 UTC,apport information
1814362,2019-02-18 15:33:41 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1814362,2019-02-04 20:17:06 UTC,apport information
1814362,2019-02-04 20:17:10 UTC,apport information
1814362,2019-02-04 20:38:08 UTC,"I enter apport-collect 1814362 command at EZbook3.
I select 1 hour, and some touchpad operation."
1814362,2019-03-31 21:38:13 UTC,"I update linux kernel v5.0.5-generic.
EZbook touchpad work fine."
1814362,2019-02-21 20:58:53 UTC,"I backup my EZbook system, then I update kernel to 5.0 rc7.
jumper EZbook touchpad could click, it work fine.
I send update log, and name -a information.
if you need any other information( etc. syslog ), I will send log."
1814362,2019-03-06 11:25:57 UTC,It's a Hantick touchpad. Can you upgrade the system and see if latest Bionic kernel helps?
1814362,2019-03-08 21:39:43 UTC,"sorry, I send mail too late."
1814362,2019-02-04 20:17:00 UTC,apport information
1814362,2019-02-18 19:16:08 UTC,"Thank you mail.
I showed 2 url documents.
One is kernel update operation,
other is kernel modules download url.
I will test to update weekend."
1814362,2019-02-04 20:16:58 UTC,apport information
1814362,2019-02-04 20:16:42 UTC,apport information
1814362,2019-02-04 20:16:54 UTC,apport information
1814362,2019-02-04 20:16:55 UTC,apport information
1814362,2019-02-02 08:19:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1814362,2019-02-02 09:00:13 UTC,<https://www.dropbox.com/sh/zi60aotqs1sa5dv/AAATgqUU9Wa6ByceJkc5NIg2a?dl=0>
1814362,2019-02-04 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1814362,2019-02-04 20:16:40 UTC,apport information
1814362,2019-02-02 22:45:13 UTC,"I missed to affects grub, perhaps xinput or kernel driver."
1814362,2019-02-04 20:16:46 UTC,apport information
1814362,2019-02-04 20:16:49 UTC,apport information
1814362,2019-02-04 20:16:51 UTC,apport information
1814362,2019-02-04 20:16:52 UTC,apport information
1814362,2019-02-04 20:16:44 UTC,apport information
1814364,2019-02-11 09:57:53 UTC,"I found /dev/sda3 ubuntu-18.03 syslog has a lot of ureadahead messages at 16:50:35.
I grub-install command to use recover /dev/sda3 pbr."
1814364,2019-08-18 20:05:02 UTC,"Now I use ubuntu-18.04.3 (5.0.0-25).
this probrem cleared from ubuntu-18.04.2 at some day."
1814364,2019-03-14 21:13:06 UTC,"I occured same trouble at same PC.
I clean install ubuntu-18.04.1 at PC, and now no trouble"
1814364,2019-03-10 20:00:09 UTC,"yestaday I update ubuntu-18.04 to use software-updater.
I update partition 4 ( /dev/sda4) ubuntu-18.04.
finished update, I shutdown PC, and today I boot up PC from /dev/sda4.
but could not bootup."
1814364,2019-02-11 08:13:59 UTC,Dear everyone.
1814364,2019-02-02 08:40:00 UTC,<https://www.dropbox.com/sh/beq6qrrkqv654sx/AAB1L0Y-tlmjZRJMGegfkog7a?dl=0>
1814364,2019-02-02 23:49:56 UTC,thank you mail.
1814364,2019-02-02 23:15:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1814364,2019-02-02 22:42:48 UTC,"I missed affects, perhaps grub-pc( or grub)."
1814364,2019-02-02 11:54:03 UTC,<https://www.dropbox.com/sh/4c1dbbor07nasx9/AABD4kQrg0UH3kukdWPYImeva?dl=0>
1814364,2019-02-02 08:19:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1814364,2019-02-09 21:17:04 UTC,"today, ubuntu software updated to use software updater.
same situation occured."
1814367,2019-02-02 11:44:44 UTC,"It doesn't warn for (the list (make-instance 'foo)), now that can be fixed."
1814367,2019-02-02 11:27:21 UTC,"Truth be told, neither do I."
1814367,2019-02-02 10:43:46 UTC,"In other words, you need to define a class, define a function that makes its instances via MAKE-INSTANCE with a symbol, then replace the class bound to that class name with a funcallable class. Ugly, but a valid edge case."
1814367,2019-02-02 10:13:59 UTC,(defclass foo () ())
1814367,2019-02-02 11:20:12 UTC,I don't believe you have (break (make-instance #.(find-class 'foo)) in your code.
1814370,2020-04-25 14:04:18 UTC,"Official support for Xubuntu 18.10 ended on July 18, 2019.  Are these issues still occurring on Xubuntu 20.04?"
1814370,2020-06-25 04:17:20 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1814370,2019-02-02 12:23:58 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1814374,2020-09-23 23:25:26 UTC,"/usr/lib/lighttpd/mod_openssl.so did not exist in the official lighttpd distribution until lighttpd 1.4.46 (not 1.4.35 or 1.4.36), so I am going to close this as a not a bug in lighttpd or packaging, but a user-error with a bad config mixed with a manual installation of a different version of lighttpd."
1814374,2020-09-23 23:21:55 UTC,"buffer_copy_buffer was introduced in lighttpd 1.4.36.
Did someone improperly backport something?
Is this still an issue?"
1814376,2019-04-16 07:37:17 UTC,Changed the error message in https://sourceforge.net/p/sbcl/sbcl/ci/143d47eeca22fad26404f26101510d613bda20ad/
1814377,2019-04-23 23:57:59 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1814377,2019-06-23 04:19:20 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1814381,2019-02-02 13:32:57 UTC,ping6 output when the network is not connected:
1814381,2019-02-02 13:34:18 UTC,ip output when the network is not connected:
1814381,2019-02-02 13:35:59 UTC,"The logic in util/qemu-sockets.c is very complicated, containing workarounds
for all sorts of broken/obsolete GAI implementations, so it's hard to tell
what's going on there."
1814384,2019-02-03 21:55:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814384,2019-02-03 21:56:37 UTC,I can confirm this bug.
1814384,2019-05-08 16:50:12 UTC,Because it happened even by upgrade from 18.04 LTS to 19.04 again when mnually installed kernel version 5 ... temporary solved by putting following code in /etc/kernel/postinst.d/kdump-tools
1814386,2019-02-02 17:22:39 UTC,"What does ""first time"" mean? Has this crash happened after upgrading from an earlier version of DC++? Is the crash permanent at every start or happened only once or a few times?
If the crash is permanent can you re-install the 32-bit version and check with that? Thanks!"
1814386,2019-02-03 07:13:22 UTC,sorry for my english (not speak/write in English and using GoogleTranslate)
1814387,2019-02-02 19:33:31 UTC,"No I don't have ""dash to dock"" installed (never heard of it before)
No, I don't scroll on the application button, it is just exactly the same behavior. It works on the complete pixel line at the edge."
1814387,2019-02-02 15:54:32 UTC,"Thank you for your bug report, what's the output of the command?
- dpkg -l | grep dock"
1814387,2019-02-02 15:55:54 UTC,or do you scroll over the application button?
1814389,2019-02-02 20:36:33 UTC,Description of problem:
1814393,2019-02-14 20:56:27 UTC,"This happens for me with 18.04, kernel 4.15.0-45-generic."
1814393,2019-02-28 20:45:28 UTC,I have yet to see any issue (i.e. it's working fine) with 4.15.0.46 (I used xenial-proposed to upgrade).
1814393,2019-02-21 19:10:20 UTC,I can confirm that moving back to 4.15.0-43-generic avoids this issue.
1814393,2019-02-21 18:40:56 UTC,"This is happening to me, started in the last 10 days or so:
$ uname -r -v
4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019"
1814393,2019-02-15 13:38:43 UTC,This looks to me like it might be a duplicate of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873
1814393,2019-02-15 09:06:10 UTC,"I can confirm this.  I noticed after the upgrade from 4.15.0-43-generic, but at first wasn't sure if I had messed up my build; I downgraded to 43 and forgot about it until the system upgraded again yesterday.  I'm now on 45, and my build fails as before, an excerpt:"
1814393,2019-02-14 12:27:06 UTC,I can confirm that this does not happen via ssh.
1814393,2019-02-04 22:51:02 UTC,I am seeing the same problem on a fully updated Ubuntu system running Linux 4.15.0-45.
1814393,2019-02-13 12:55:49 UTC,"This problem happens with both the standard GNU Make 4.1 that comes with Ubuntu 16.04.5, and with a self-compiled GNU Make 4.2.1."
1814393,2019-02-12 14:40:04 UTC,I have recently started experiencing the same problem.
1814393,2019-02-12 13:00:47 UTC,affects me
1814393,2019-02-11 16:52:22 UTC,I have this problem as well on 16.04LTS with kernel 4.15.0-45-generic #48.
1814393,2019-02-07 18:25:10 UTC,I'm running 16.04 and seeing the same problem on Linux 4.15.0-45. I can also confirm that when booting with 4.15.0-43 I no longer see the problem.
1814393,2019-02-07 17:41:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814393,2019-02-13 13:17:07 UTC,"It is not GNU Make itself. If I pipe GNU Make's output to tee, then it is tee that fails:"
1814395,2019-07-05 02:05:49 UTC,"Solution for FP3, 'show-credential' now caters fro both local and remote credentials: https://github.com/juju/juju/pull/10426"
1814395,2019-07-19 00:01:45 UTC,"Solution for FP2, uploading credential to a controller on 'add-credential': https://github.com/juju/juju/pull/10447"
1814395,2019-06-25 03:01:08 UTC,I have numbered your commands and updated description to be able to refer to them.
1814395,2019-02-02 21:32:05 UTC,The add-cloud and add-credential commands currently only operate on the local Juju client's internal YAML files. They are intended to set up the Juju client so that a *new* controller can be bootstrapped from scratch with a new cloud. These commands do not affect any running controller.
1814395,2019-06-25 03:36:46 UTC,FRICTION POINT 2:
1814397,2019-12-04 11:36:38 UTC,"Hi Liviu,"
1814397,2019-10-23 16:11:58 UTC,Ich bin bis 28.10. nicht im Haus und kann Ihre Nachricht daher leider nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
1814397,2019-10-23 16:03:08 UTC,Fixed in 8.3-2019-08 release
1814397,2019-12-03 22:57:10 UTC,"Hi Joey,"
1814397,2019-02-04 07:11:30 UTC,https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89183
1814397,2019-02-03 17:33:09 UTC,"It is easy to reproduce this bug, create an empty main.c and try to compile it with -g or -g3:"
1814397,2019-02-03 09:35:52 UTC,Even more tests revealed the problem to be related to the presence of debug information.
1814397,2019-02-03 09:08:09 UTC,I did further tests and the previous version (7-2018-q2-update) builds my projects (both C and C++) properly with -flto.
1814397,2019-02-04 09:29:01 UTC,The problem was fixed upstream and will probably be included in 8.3.
1814398,2019-02-02 21:36:50 UTC,"The error messaging certainly seems wrong here. After adding a user to a controller, they will at that point only have login permission, unless they were granted add-model permission.
It seems Juju is getting confused by the fact that a new local cloud is added."
1814398,2019-10-31 03:49:53 UTC,A lot has changed in this area since the report was originally written. Please re-try with 2.7.
1814400,2019-02-02 20:30:06 UTC,This change was made by a bot.
1814400,2019-02-05 00:48:21 UTC,"I am not sure what changed (I have run apt upgrade a couple of times), but I am no longer having this issue."
1814407,2019-12-10 04:17:32 UTC,[Expired for lxqt-panel (Ubuntu) because there has been no activity for 60 days.]
1814407,2019-12-10 04:17:34 UTC,[Expired for byobu (Ubuntu) because there has been no activity for 60 days.]
1814407,2019-10-10 17:22:22 UTC,"Setting to incomplete, because 18.10 is out of support and with 19.04 I could not reproduce it."
1814407,2019-02-09 22:13:10 UTC,"Hi,"
1814407,2019-02-04 14:31:53 UTC,"Thanks didrocks, not knowing any better I've filed it against the lxqt-metapackages assuming that LXQt packagers will sooner or later re-task it to the right component in LXQt"
1814407,2019-02-04 13:41:19 UTC,Hey!
1814407,2019-02-04 13:19:25 UTC,"I should have included the file as well. Unlike for you, /usr/share/applications/byobu.desktop was a file on my system and not a symlink. And the content was different:"
1814407,2019-02-04 12:59:06 UTC,"Hi decimus,
thank you for your report to make Ubuntu better.
Unfortunately .desktop files sometimes are like a dark mystery to me, I don't see how the file"
1814415,2019-02-03 00:00:07 UTC,This change was made by a bot.
1814415,2019-02-19 14:18:40 UTC,"Please attach the output of:
$ grep . /sys/class/power_supply/BAT0/*"
1814419,2019-07-30 08:46:04 UTC,This old issue is resolved and the tests worked at least since ubuntu-image/1.7+19.04ubuntu1 - lets mark it Fix released.
1814420,2019-12-23 20:59:46 UTC,"Hi, qemu version 3.1 is a bit old in terms of upstream support. Can you confirm that this is still an issue on 4.2 ?"
1814420,2020-02-22 04:17:25 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1814421,2019-02-03 09:57:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814421,2019-02-03 06:56:32 UTC,Modern releases as 18.10 and 19.04 are affected too.
1814422,2019-02-03 06:56:44 UTC,Modern releases as 18.10 and 19.04 are affected too.
1814422,2019-02-03 09:58:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814424,2019-02-04 15:58:20 UTC,https://github.com/juju/juju/pull/9706 is a patch against 2.5.1
1814436,2019-02-17 01:12:26 UTC,Further resources on this (had to update the laptop as well as desktop)
1814436,2019-02-04 14:03:35 UTC,"> Print Test Page.......
>
> SUCCESS!!!!
"
1814436,2019-02-04 12:57:41 UTC,"but of course the ubiquitous
$ error:  No system tray detected on this system.  Unable to start, exiting."
1814436,2019-02-04 12:53:20 UTC,OMG OMG OMG SUCCESS!! SUCCESS!!
1814436,2019-02-04 10:38:03 UTC,In your first message you say:
1814436,2019-02-03 22:51:45 UTC,"> ls: cannot access '/usr/share/hplip/prnt/plugins': No such
> file or directory
"
1814436,2019-02-03 12:06:28 UTC,"Ubuntu 18.04's hplip should work with the CP-1025nw, so I imagine it's testing of 3.19.1 you are doing. Required reading is"
1814436,2019-02-03 21:11:23 UTC,ls -l /usr/share/hplip/prnt/plugins
1814436,2019-02-03 20:37:09 UTC,Can you print (the plugin is required for this)?
1814436,2019-02-03 20:19:21 UTC,"Thank you Brian,"
1814436,2019-02-04 07:04:35 UTC,"Hello Brian,"
1814457,2019-03-22 23:31:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814459,2019-02-04 08:26:42 UTC,"That would change the meaning of empty rule from ""rule is ignored"" to
""exclude empty values"". That would change the way the GUI works. This is
particularly bad since there are default rules with empty values."
1814459,2019-02-05 06:23:00 UTC,agree.
1814460,2019-02-14 17:10:25 UTC,This is interesting.
1814460,2020-01-22 20:28:23 UTC,I don't think that anyone should invest effort in sorting dracut unless Ubuntu is actually going to be move to dracut.
1814460,2020-03-25 16:03:30 UTC,This bug was fixed in the package clevis - 12-1ubuntu1
1814465,2019-06-11 08:55:27 UTC,"Ubuntu 14.04 reached end-of-life in April 2019, and the Extended Security Maintenance plan (which is a paid option) doesn't include firefox (see https://wiki.ubuntu.com/SecurityTeam/ESM/14.04)."
1814465,2019-06-09 04:20:52 UTC,"According to https://hg.mozilla.org/integration/autoland/rev/6fc6bdea42a6 (associated with https://bugzilla.mozilla.org/show_bug.cgi?id=1501218),"
1814465,2019-04-02 20:50:21 UTC,"Confirmed, this is affecting firefox only on trusty.
The Flash plugin works as expected on xenial, bionic, cosmic, disco.
wl_surface_interface is a Wayland symbol."
1814465,2019-03-26 13:55:35 UTC,"Same in ""66.0.1+build1-0ubuntu0.14.04.1"":"
1814465,2019-02-09 17:18:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814465,2019-02-07 22:09:32 UTC,The same error message appears in the shell (different pipe error) when running a local flash (.swf) that always worked before the recent firefox 65 that was pushed to ubuntu 14.04 LTS systems.  Sure 14.04 LTS and flash are approching end of support so the number of users affected may not be large but it would be great if this could be fixed.
1814473,2019-02-18 11:35:59 UTC,Would it be possible for you to boot an older kernel?
1814473,2019-07-19 13:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1814473,2019-09-18 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1814473,2019-07-19 13:15:31 UTC,"As manual setup of networking also does not work it looks more like a kernel problem, moving ..."
1814478,2019-02-14 08:24:56 UTC,"Indeed I had the same issue, try having ~/.dhexrc
#DHEXCOLORSCHEME
#VERSION 0
#possible colors are: BLACK,RED,GREEN,YELLOW,BLUE,MAGENTA,CYAN,WHITE
#possible extra flags are: UNDERLINE,REVERSE,BLINK,DIM,BOLD
BRACKETS: FG=BLACK,BG=BLACK,BOLD
HEXFIELD: FG=WHITE,BG=BLACK
INPUT: FG=BLACK,BG=WHITE
CURSOR: FG=WHITE,BG=BLACK
TEXT: FG=WHITE,BG=BLACK,BOLD
MENU_NORMAL: FG=CYAN,BG=BLACK
MENU_HIGHLIGHT: FG=BLACK,BG=CYAN
MENU_HOTKEY: FG=YELLOW,BG=BLACK,BOLD
MENU_HOTKEY_HI: FG=YELLOW,BG=CYAN,BOLD
FRAME: FG=BLUE,BG=BLACK,BOLD
NORMAL_DIFF: FG=YELLOW,BG=BLACK
CURSOR_DIFF: FG=YELLOW,BG=WHITE,BOLD
HEADLINE: FG=BLUE,BG=BLACK,BOLD
HEADER: FG=BLACK,BG=CYAN
KEYF1:1b 5b 31 31 7e
KEYF2:1b 5b 31 32 7e
KEYF3:1b 5b 31 33 7e
KEYF4:1b 5b 31 34 7e
KEYF5:1b 5b 31 35 7e
KEYF6:1b 5b 31 37 7e
KEYF7:1b 5b 31 38 7e
KEYF8:1b 5b 31 39 7e
KEYF9:1b 5b 32 30 7e
KEYF10:1b 5b 32 31 7e
KEYESC:1b
KEYBACKSPACE:08
KEYDEL:7f
KEYENTER:0a
KEYTAB:09
KEYUP:1b 5b 41
KEYDOWN:1b 5b 42
KEYRIGHT:1b 5b 43
KEYLEFT:1b 5b 44
KEYPGUP:1b 5b 35 7e
KEYPGDOWN:1b 5b 36 7e
KEYHOME:1b 5b 37 7e
KEYEND:1b 5b 38 7e"
1814478,2019-08-17 04:18:53 UTC,I belive this is caused by a high cpuload patch in 0.69
1814478,2020-11-11 04:31:52 UTC,This bug was fixed in the package dhex - 0.69-2
1814481,2019-12-08 18:36:39 UTC,"Same problem with Keychrom K2 ubuntu 19.10
but when I'm in the loggin screen it works fine..."
1814481,2020-02-12 08:26:44 UTC,"Hello,"
1814481,2020-02-21 20:15:30 UTC,I can confirm https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/comments/19 fixed it. thanks a lot @eferox!
1814481,2020-02-24 02:21:20 UTC,"@vanvugt, shouldn't that be after actually merging the fix?"
1814481,2019-10-21 10:19:09 UTC,Upgrading to Ubuntu 19.10 seems to have fixed this problem.
1814481,2020-02-24 02:35:44 UTC,"To ensure this bug does not become oversubscribed by other people with other problems I have clarified this bug is only about the ""Keychron K1 keyboard""."
1814481,2020-02-24 02:55:06 UTC,"good idea, thanks"
1814481,2020-02-24 03:22:15 UTC,Note that if the problem is fixed in later Ubuntu releases then it likely would be fixed in Ubuntu 18.04.4 too:
1814481,2020-03-25 15:00:22 UTC,"Keychron K1v3 (firmware V3.7) on Ubuntu 19.10 (upgrad path from 18.04), can confirm that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/comments/19 fixes the issue when connected via Bluetooth."
1814481,2020-03-25 15:11:25 UTC,"Additionally if you want to change the default `F<num>` key behaviour again, press and hold `fn + X + L` in that order for >3 seconds until the keyboard blinks red twice."
1814481,2020-02-24 02:32:44 UTC,"Yes, sorry. I'm not sure what I was aiming for there."
1814481,2019-10-13 08:49:10 UTC,"Same problem,"
1814481,2019-02-25 23:20:39 UTC,"I disabled secure boot and tried the latest, 4.20.12... problem persists, and evtest workaround too."
1814481,2019-07-09 09:16:29 UTC,"I can confirm mine ""stopped"" working via Bluetooth after updating from 18.10 to 19.04. Works with the evtest workaround."
1814481,2019-03-29 04:21:31 UTC,So it's not a kernel bug. I am not sure which update fixed it though...
1814481,2019-03-04 21:54:28 UTC,"I just tried updating the kernel to v5.0, same situation as before. works on lightdm but not on X... until I run evtest."
1814481,2019-02-26 18:52:19 UTC,"I just realised the keyboard works in lightdm, and the stops working after logging in."
1814481,2019-02-26 14:11:49 UTC,"nope, didn't."
1814481,2019-02-26 02:03:25 UTC,"Does kernel parameter ""btusb.enable_autosuspend=0"" help?"
1814481,2019-02-25 20:44:42 UTC,"I had to uninstall virtualbox because apparently, something related to dkms was preventing me from generating correct initramfs... then it refused to boot because the image wasn't properly signed... are there _signed_ equivalents to these kernel packages?"
1814481,2019-02-25 01:56:42 UTC,Thanks.
1814481,2019-02-22 22:30:33 UTC,"I can confirm it works out of the box using the latest Ubuntu ""disco"" live stick."
1814481,2019-02-18 09:22:48 UTC,You say Xubuntu 19.04 live doesn't have the problem... Can you please try regular Ubuntu 19.04 live?
1814481,2019-02-13 08:01:42 UTC,I did test with bluez ppa and didn't change anything.
1814481,2019-02-10 14:01:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814481,2019-09-24 19:24:27 UTC,Same probleme with ubuntu 19.04 and Keychron K2 keyboard
1814482,2019-02-08 08:09:51 UTC,"I suggest that local.conf file like this one https://github.com/openstack/tacker/blob/master/devstack/local.conf.example. You can update to stable/rocky and before run stack.sh, please completely uninstall devstack as this guide: https://nguyentrihai.com/?p=481"
1814482,2019-02-12 02:12:37 UTC,"Thanks a lot, Cong Phuoc. It's of great help. While I continue to have issues w/ devstack rocky installation due to glance uwsgi related changes, I can now do clean/repeat runs, thanks to the cleanup procedure provided. Best regards!"
1814485,2019-02-15 07:09:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814486,2019-02-06 00:11:39 UTC,"UnitBinder is for multi-part controls (a static text label, text ctrl or static text value and a static text units).  It /does/ give you NumericEvaluation for free (although there's also TEXT_CTRL_EVAL if you want numeric evaluation /without/ a units support -- such as for mask ratios, etc.)."
1814486,2019-02-05 21:49:04 UTC,"In the same dialog, neither do the netclass grid cells or Tracks & Vias grid cells."
1814487,2019-02-04 10:09:48 UTC,"./run-sbcl.sh --dynamic-space-size 3800
This is SBCL 1.4.15.81-7dbc076, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>."
1814487,2019-02-05 01:27:30 UTC,"Thanks, useful data point!"
1814487,2019-02-05 01:59:58 UTC,I whipped up a simple mmap program:
1814487,2019-02-05 10:24:53 UTC,You can't map more than 4 GB on a 32-bit process.
1814490,2021-02-25 07:43:03 UTC,"I've attempted to re-create this 3 times in last few days and failed to RE-CREATE this bug using
lubuntu hirsute dailies using LXQt 0.16 (not all today)"
1814490,2020-02-14 08:52:51 UTC,https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1855792
1814490,2020-01-17 08:43:26 UTC,On d960 box..
1814490,2020-01-17 07:28:55 UTC,I just noticed screensaver kicked in on both my displays on my primary (d960) 20.04 box.  This maybe the first time I've seen this on this box since Lubuntu went to LXQt (whilst using LXQt/Lubuntu anyway).
1814490,2019-12-12 05:45:24 UTC,"Lubuntu 20.04 QA-Test on
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1814490,2019-10-25 06:37:37 UTC,"upstream message left on https://github.com/lxqt/lxqt/issues/1705
Another user has commented upstream having this issue with 3 screens"
1814490,2019-10-25 06:16:31 UTC,"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
purpose of this test is to start looking for old bugs & confirm focal impacted; these bugs are old & upstream issues and will impact very few end-users (impact me thus why chased)
boot up; adjust displays to match my setup (default-right display is below other display)
..
opened screensaver settings; clicked preview & only top display is hidden - https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1814490"
1814490,2019-09-13 05:44:37 UTC,"this issue occurs on installed systems (my primary d960 which used to be 19.04, now 19.10), plus live systems (19.04 & 19.10, not when initially booted; but when screens adjusted to be one above the other - but issue only occurs one way; if swapped top-bottom both screens have xscreensaver active on them).   Adding disco & eaon tag is reason for this comment; still present on today's daily reason I looked."
1814490,2019-07-21 03:25:44 UTC,I have marked https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1807665 as a duplicate of this one.
1814490,2019-04-25 02:03:40 UTC,FYI:  this also occurs on debian buster's weekly ISO of 2019-04-22 06:17
1814490,2019-04-06 00:19:40 UTC,"adding a screenshot (delay of 70 secs on screenshot, 1 min till bsod scrensaver shows)"
1814490,2019-02-16 02:51:18 UTC,"QA-Test 2019-02-16 on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1814490,2019-02-18 01:12:01 UTC,2019-02-17 19:30 QA-Test Lubuntu 19.04 daily (live) x86_64
1814490,2019-02-06 03:29:50 UTC,from #lubuntu-devel
1814490,2019-02-05 03:08:05 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1814490,2019-02-05 02:08:14 UTC,"latest daily image  (lubuntu 19.04 daily image), and at first no problems  (just re-did test in comment #6)"
1814490,2019-02-05 01:34:48 UTC,"I just booted a 19.04 daily image used in my last Lubuntu x86_64 QA-test  [booted on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)]. The daily.ISO was downloaded 29-Jan with ISO dated 28-Jan, and xscreensaver had no issues with two screens (both showed different color & different images & no htop's visible).   I've re-powered up my file server so updating my daily & plan to re-test with todays."
1814490,2019-02-05 00:32:32 UTC,from #lubuntu-devel
1814490,2019-02-04 10:10:24 UTC,I rebooted x86 lubuntu 18.04.1  (no xscreensaver package is installed by default)
1814490,2019-02-04 08:23:15 UTC,in #lubuntu-devel
1814490,2019-02-04 07:41:29 UTC,in #lubuntu-devel  Krytarik suggested I try an older version
1814490,2019-02-04 03:41:14 UTC,"on this box I normally don't have LOCKED SCREEN enabled, but I get the same result if that box is ticked or not. I tried changing screensaver & it made no difference (my default was random anyway), and the issue only occurs in Lubuntu (not Xubuntu) so it's likely a different package or config at fault so sorry."
1814490,2019-03-16 07:09:11 UTC,"QA-test Lubuntu 19.04 on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
1814498,2019-05-15 19:02:18 UTC,"If this affects the 5.1 branch, it should be cherry-picked."
1814498,2019-05-15 19:20:02 UTC,"It relies on the new pad shapes, so it'll need to remain a 6.0-only feature."
1814498,2019-02-04 09:11:24 UTC,Custom pad shapes do not support thermals right now [1]. Mapping octagon to custom is at best a hotfix. A full support for them can only happen with the chamfered pads that might be added to version 6 [2]. (Or if custom pads support thermals)
1814498,2019-05-15 18:13:53 UTC,"Fixed in revision 44e111b37e372307000b5682b5e3dd1553623d11
https://git.launchpad.net/kicad/patch/?id=44e111b37e372307000b5682b5e3dd1553623d11"
1814502,2019-02-04 07:10:32 UTC,Are you sure this is actually a regression from 17.10 -> 18.04?
1814502,2019-02-04 18:11:00 UTC,"I'm not absolutely certain, but I'm fairly sure. The behavior changed when I installed 18.04, which was relatively recently compared to its release date. For a couple of months, I'd try to use it for a few months, remember it was wonky, and need to get work done before the end of the train trip. Finally was on a longer one the other day where I went hunting for the solution."
1814502,2019-02-04 18:31:51 UTC,"Thanks, that's interesting. There were almost no changes to the Juniper code between v7.06 and v7.08, and none that affected MTU handling (git diff v7.06 v7.08 -- oncp.c auth-juniper.c)"
1814502,2019-02-04 18:46:33 UTC,I don't use OpenConnect on MacOS -- I'm using the real Pulse Secure software version 5.2.5 (869).
1814502,2019-02-04 18:47:13 UTC,"Note that this does not appear to be a detected MTU, but a server-provided MTU (if there is indeed a difference)."
1814502,2019-02-04 19:31:17 UTC,"Ah, that's useful to know."
1814502,2019-02-04 20:13:33 UTC,"It's not doing it right now on either 17.10 or 18.04, on either Optimum Online or VZW via hotspot. :-|"
1814502,2019-02-04 20:16:26 UTC,...until I said that. Now it's doing it again on 18.04 on VZW. I'll try to see under what circumstances it does and does not happen.
1814502,2019-02-05 00:01:43 UTC,"You can still work around it by setting a lower MTU manually though, right? (openconnect --mtu=X)"
1814504,2019-02-09 13:36:38 UTC,apport information
1814504,2019-02-09 13:36:43 UTC,apport information
1814504,2019-02-09 13:36:39 UTC,apport information
1814504,2019-02-09 13:36:37 UTC,apport information
1814504,2019-02-09 13:36:41 UTC,apport information
1814504,2019-02-09 13:36:34 UTC,apport information
1814504,2019-02-09 13:36:28 UTC,apport information
1814504,2019-02-09 12:43:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1814504,2019-02-09 13:36:35 UTC,apport information
1814504,2019-02-09 13:36:32 UTC,apport information
1814504,2019-02-09 13:36:30 UTC,apport information
1814508,2019-02-04 09:18:22 UTC,"i add tz = 'UTC' in the code before:
         if tz:
            timezone.activate(tz)
in the file:
horizon/horizon/middleware/base.py"
1814508,2019-02-05 20:52:24 UTC,"XiaojueGuan, what is the value of USE_TZ in your local_settings? If it's not set or set to False, could you please set it to True and try to reproduce the issue again?"
1814508,2019-05-21 19:46:48 UTC,Horizon depends on the Django feature [1]. django_timezone key should exist in the session information.
1814508,2019-07-21 04:17:36 UTC,[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]
1814508,2019-02-04 09:11:55 UTC,"One more interesting phenomenon is when i browse it with incognito window it works ok but in a common window it fails. As i dive into the code with help of pdb, i find when horizon handles the request form incognito window there is no ""django_timezone"" in the request object while request from common window will have the django_timezone in the request object."
1814511,2019-02-04 09:27:21 UTC,Additional hint: The same code lines don't trigger any errors when running in Apache - only from CLI.
1814511,2019-02-04 09:34:10 UTC,"Another hint: The problem seems to appear only together with PHPUnit.
When running the same code parts from regular Symfony commands, the error does not occur."
1814511,2019-02-06 16:44:47 UTC,"Can you come up with a simple single .php script that shows the problem? That would help with diagnosing this and searching the upstream bug tracker, or even filing an upstream bug."
1814511,2019-02-11 08:44:39 UTC,"Hi Andreas, so far I didn't succeed to generate a simple script to reproduce.
Will try to put more effort soon."
1814511,2019-09-12 07:37:47 UTC,"Hi Martin,"
1814511,2019-09-12 14:08:00 UTC,"Hi Bryce,
I just created an updated Docker image from the current state of ubuntu:19.10, using Ubuntu's ""php7.3"" package.
I could no longer reproduce the bug."
1814511,2019-09-12 14:42:26 UTC,"Hi again,
using ubuntu:18.04 + php7.2 in Docker, I can still reproduce the issue :-(
Same strange error messages, ""Undefined variable: value""."
1814511,2020-01-22 01:25:05 UTC,"Thanks for the testing, I'll update the bug states and priorities."
1814517,2019-10-31 03:52:20 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1814517,2019-02-04 10:20:26 UTC,"This can happen if a default, existing storage class is used, that is not created by Juju. The storage class's Reclaim Policy attribute defines the policy on any volume it creates. We may need to look at trying to edit the policy on volumes after creation."
1814518,2019-10-31 03:53:51 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1814529,2019-02-04 12:03:07 UTC,And an attempt using apport-collect:
1814529,2019-02-04 12:07:59 UTC,"`apport-cli --save /tmp/1814529.apport apport` appears to save the collected information to a file, as intended. I used this mechanism to generate the following information so that I could attach it to this bug report (due to this bug, I can't use the normal mechanism):"
1814529,2019-03-02 05:51:56 UTC,"ais523: Why is this filed under ""evolution""? How is this related to Evolution at all?"
1814529,2019-03-02 06:07:49 UTC,"It isn't (except that if apport-bug were working, it would have made sure the bug was filed against the right package!). Sorry, it's easy to make a mistake when filing a bug manually."
1814529,2019-12-17 00:54:35 UTC,"Although it was reliably reproducable at the time, I can no longer reproduce this bug (using ubuntu-bug version 2.20.9 on Ubuntu Bionic). Perhaps it's been fixed incidentally."
1814535,2019-05-28 07:16:27 UTC,"It is not a limitation of Playground nor Dr.Geo. It is an installation problem.
Playgroound setting can be change to a disk location with write permission."
1814536,2019-03-26 05:36:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814536,2019-03-26 05:40:04 UTC,"This is affecting me trying to update the debian-multimedia package in Ubuntu. Running 'make dist"" in the debian-multimedia package worked in December 2018. Now it fails with:"
1814536,2019-07-08 23:50:16 UTC,This bug was fixed in the package debian-archive-keyring - 2019.1ubuntu2
1814539,2019-02-19 14:16:08 UTC,Please do a kernel bisection between v4.18 to v5.0.
1814539,2019-02-19 14:05:45 UTC,"$ git log Ubuntu-4.18.0-12.13..Ubuntu-4.18.0-13.14 --pretty=oneline
bfe015d2df84299c03b3189e6a6f5d97a68b213c (tag: cod/changeset/cosmic/hash--bfe015d2df84299c03b3189e6a6f5d97a68b213c, tag: Ubuntu-4.18.0-13.14) UBUNTU: Ubuntu-4.18.0-13.14
b834bd41a001f0aa21aa877b63c245539d064b63 UBUNTU: link-to-tracker: update tracking bug
dd03636af187923c3cf63fa471a02c07ad93ef7a UBUNTU: [Packaging] buildinfo -- add buildinfo support to getabis
6efd1e8d2894b530095bdf75c64107b3ed279d6f UBUNTU: [Packaging] buildinfo -- add compiler information to the flavour ABI
2d7f191a3315096bbce261fbd4a1562c440a734a UBUNTU: [Packaging] buildinfo -- add firmware information to the flavour ABI
8c9154e701ec5fb0da7cd0e495836bc06e4c873c UBUNTU: [Packaging] buildinfo -- add basic build information
d70801b56935ecfb472ab4be61b9ee06326c5667 UBUNTU: [Packaging] ABI -- accumulate abi information at the end of the build
bb224d4911f2a527a665be13cc9a1e31e13f46c0 UBUNTU: [Packaging] commonise debhelper invocation
6af14034d456af0c9a09de0bd2401453240efe3a UBUNTU: [Packaging] limit preparation to linux-libc-dev in headers
811bdb9c90e7058b5f58bf269c3727287ec3923e UBUNTU: [Packaging] own /usr/lib/linux/triggers
1adbe114f170a131658147f013e4f2c048a69015 Revert ""net-next/hinic: add checksum offload and TSO support""
c2f0cb7a8222f28eb6ffe876f406c1e3e7e161d2 cdrom: fix improper type cast, which can leat to information leak.
b9565132d7340de78dbd8eec542910f6194b6fc9 UBUNTU: Start new release"
1814539,2019-02-21 15:15:55 UTC,Commits between each kernel releases are backported from mainline series. It can be easier to find out the regression commit.
1814539,2019-02-18 15:52:48 UTC,The issue remains in both mainline 4.20.0 and 5.0.0rc7 generic kernels.
1814539,2019-02-18 15:57:50 UTC,I should perhaps add that then the laptop goes from unpowered to powered the led in the power button does blink.  So the firmware stil sennses the power being plugged.
1814539,2019-02-04 14:00:07 UTC,This change was made by a bot.
1814539,2019-02-20 14:29:16 UTC,Who do you want to do a bisection?
1814539,2019-02-18 10:55:49 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1814545,2019-02-04 14:38:26 UTC,777
1814545,2019-02-05 03:12:11 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1814545,2019-02-05 03:14:51 UTC,"Hello Joshua, different tools will handle passwords differently. Backslashes in particular may be funny. It's better to generate passwords with an algorithm that outputs enough characters from a more restricted character set to provide the security level you want."
1814546,2019-02-04 14:42:28 UTC,Investigate if it is possible to stop interface:pgsql setting the relation flags when the unit is a subordinate not co-hosted with a PostgreSQL principal.
1814547,2019-02-04 16:13:11 UTC,"Hi Charles,"
1814547,2019-02-04 21:34:40 UTC,home/bert/LP1814547_review
1814547,2019-02-08 13:09:12 UTC,We may need to be careful here. Do we know for sure that a Coord has a consistent type alias across platforms?
1814547,2019-02-11 19:26:34 UTC,"OK, I've determined that this test failure is not going to hurt anything in this version of pcb. There isn't any code that calls the affected function. Therefore we do not need to do a quick release to fix the original issue."
1814547,2019-02-11 22:13:13 UTC,Merged into master and pushed upstream.
1814551,2019-08-05 11:15:55 UTC,"I still can't reproduce the problem in a fully up-to-date bionic VM, using the instructions in bug #1795169, which is a duplicate of the original bug report.
I've tested both X (default) and Wayland sessions."
1814551,2019-08-03 06:23:23 UTC,"This is still not resolved, from further upstream, for users running gnome-shell."
1814551,2019-08-05 11:08:18 UTC,"This bug was originally reported against Cosmic, which is now end of life."
1814551,2019-02-21 14:14:25 UTC,"I cannot reproduce the issue. I'm on cosmic fully up-to-date with the same versions of gnome-shell and ibus as in the descriptino, tested firefox 66 beta 9 from the firefox-next PPA."
1814551,2019-02-21 14:19:04 UTC,"Also tested firefox 65.0+build2-0ubuntu0.18.10.1 from the Ubuntu repositories, and I cannot observe the problem there either."
1814551,2019-02-04 15:30:05 UTC,"Apologies, I meant to state in step one that the input method system is iBus."
1814551,2019-02-21 15:37:57 UTC,I can into this when using the following:
1814551,2019-02-07 09:59:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814552,2019-02-04 15:34:12 UTC,This probably also affects Kolla as well.
1814552,2019-09-16 07:02:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/682280"
1814552,2020-01-31 17:57:48 UTC,"Reviewed:  https://review.opendev.org/682280
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=15b68c15c1dd0c2df1cc49b550f2fa03a4c65e8e
Submitter: Zuul
Branch:    master"
1814552,2020-01-31 19:29:10 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/705287"
1814552,2020-02-04 15:24:05 UTC,"Reviewed:  https://review.opendev.org/705287
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=ffaf585d0f05ccd9123459bb0cdf345af5b09573
Submitter: Zuul
Branch:    stable/train"
1814552,2020-02-05 17:45:33 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/706065"
1814552,2020-02-06 14:41:40 UTC,"Reviewed:  https://review.opendev.org/706061
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=757fe57563ed54e53c14c8cfae780b71fb49b7ba
Submitter: Zuul
Branch:    stable/stein"
1814552,2020-02-11 07:30:09 UTC,I think ooo got fixed by kolla fix unless you override it.
1814552,2020-02-19 11:04:18 UTC,"Reviewed:  https://review.opendev.org/706065
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=f39fc9b0a77c2c7d75afedb217bb0f8d6e7eed19
Submitter: Zuul
Branch:    stable/rocky"
1814552,2020-03-23 15:56:38 UTC,This issue was fixed in the openstack/kolla 7.1.1 release.
1814552,2020-04-22 01:46:48 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/721764"
1814552,2020-05-27 07:51:52 UTC,This bug is marked incomplete for tripleo. Please remove the milestone to stop the spam with each RC :)
1814552,2020-05-27 10:42:53 UTC,"Change abandoned by Jeffrey Zhang (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/721764"
1814552,2020-02-05 17:37:02 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/706061"
1814553,2019-02-04 16:20:44 UTC,"The attachment ""bf.c.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1814556,2019-02-13 19:50:15 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1814556,2019-02-04 16:02:39 UTC,https://github.com/juju/juju/pull/9712 is a WIP progress down this path.
1814558,2019-02-04 20:51:26 UTC,"As a note, I had considered using juju actions for this, but that still doesn't honor the undercloud/overcloud privilege separation we use in our managed service offerings, however, an action would make it a much easier process for undercloud operators."
1814558,2019-04-24 18:10:48 UTC,"I've noted that in production that basic_auth.csv appears to be frequently touched for some reason, roughly once every 5 minutes.  If kube-apiserver gets restarted on the kubernetes-master nodes, additional logins may stop working."
1814558,2019-04-24 18:15:54 UTC,subscribed ~field-critical
1814558,2019-04-24 19:25:27 UTC,unsubscribed ~field-critical; broke my concerns out into a new ticket: https://bugs.launchpad.net/charm-kubernetes-master/+bug/1826260
1814561,2019-02-04 17:15:01 UTC,This bug is appear in kicad release 5.0.2 too
1814561,2019-02-24 21:58:54 UTC,We'll get this bug when we integrate kicad2step
1814563,2019-02-04 16:46:36 UTC,This is effectively an API guarantee which we ought to make to avoid inadvertently breaking other services that integrate with SSO.
1814567,2019-02-04 17:35:12 UTC,"It would appear after looking closer that there are indeed 2x separate failures for Xenial and Bionic, both occuring at different points in time runing the tests, however all of the instance types in the series will fail at the same point.
Again, same type of failure, rather vague... the test will need to be run by hand in order to identify it, as the logs did not record the crash dump."
1814567,2019-02-04 17:35:39 UTC,Above logs for Xenial
1814569,2019-02-04 19:18:02 UTC,Bug fix proposed for merge.
1814574,2019-02-05 09:32:29 UTC,"And it is hplip-3.18.12, which I speak of."
1814587,2019-02-04 21:13:53 UTC,"Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic"
1814587,2019-06-03 08:20:07 UTC,"The snap seems to install and set things up without issue. When you run it, if you run it from the terminal, you'll see that it is actually doing quite a lot of stuff, downloading the actual game at that time; the snap is just an installer."
1814588,2019-02-09 15:42:28 UTC,I have uninstalled and reinstalled the Firefox browser on the 18.04 laptop and the Start page does not display the search box. I have now installed 19.02 to a USB SanDisk to test out and the Start Page is as expected.
1814588,2019-09-06 21:24:58 UTC,I can't reproduce this issue.
1814588,2019-11-06 04:17:35 UTC,[Expired for ubuntu-mate-settings (Ubuntu) because there has been no activity for 60 days.]
1814595,2019-03-11 17:26:29 UTC,"Reviewed:  https://review.openstack.org/642170
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=77cbb985f294fbcb48c1a2946f2d63174588710e
Submitter: Zuul
Branch:    master"
1814595,2019-07-15 21:08:57 UTC,"To add to Cindy's comment, the main reason this issue is no longer gating stx.2.0 is the original issue reported in StarlingX has been avoided by using a different implementation for size of PVs used by StarlingX (see: https://review.opendev.org/#/c/642170/)."
1814595,2019-05-08 23:22:27 UTC,"we reviewed in non-openstack-dist project meeting and agreed this is not gating stx.2.0. Due to the reason that Jim found it's CentOS 7.6 upstream issue, WR provided and upstream bug opened."
1814595,2019-05-08 19:45:02 UTC,Changing priority to Low based on Cindy's update that this should not be release gating. I've asked Cindy to add justification for tracking purposes as well.
1814595,2019-03-19 19:14:49 UTC,"This issue occurs in out-of-the-box standard CentOS 7.6 and earlier, nothing to do with any of our kernel patches or other modifications."
1814595,2019-03-18 15:09:40 UTC,Downgraded to Medium given that a workaround has been pushed.
1814595,2019-03-18 15:09:19 UTC,Dropping priority to Medium since workaround (using 1G volume for rabbitmq) prevents issue.  Still need to find a solution and Jim continues to investigate the kernel.
1814595,2019-03-08 22:23:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/642170"
1814595,2019-02-25 15:57:08 UTC,Changed priority to High due to the # of labs that have seen this issue in the past week (at least 7).  Also looks like this is a duplicate of https://bugs.launchpad.net/starlingx/+bug/1815541
1814595,2019-03-06 19:13:59 UTC,"That's interesting about rabbitmq, do you have a link or bug number?"
1814595,2019-03-06 18:22:49 UTC,"DX and Standard 2+2 configurations faced problems with the provisioning due to an existing issue related to “rabbitmq” service pod.
The same issue affected the Stress and Stability execution. Seems that “rabbitmq” pod had issue to manage signals when there is a big load."
1814595,2019-03-01 19:09:08 UTC,The issue has been recently reproduced in 3 labs - 2 running the CentOS 7.6 kernel. Jim Somerville is actively investigating; assigning the launchpad to him.
1814595,2019-02-28 21:32:13 UTC,Possible candidate:
1814595,2019-02-13 15:23:15 UTC,"We also saw the issue. During normal operation yet we were unable to reproduce it consistently, it's good that you are able to reproduce it. Sharing below our data:"
1814595,2019-02-08 19:39:29 UTC,"Marking as release gating until further investigation.
The issue was reported during testing in a containerized environment. It was not seen w/o containers."
1814595,2019-02-06 19:15:26 UTC,"The general steps are as follows, then they are repeated for several hours."
1814595,2019-03-06 21:28:30 UTC,I think Juan Carlos refers to this one: https://bugs.launchpad.net/starlingx/+bug/1815541 which was marked as duplicated of this one.
1814596,2019-04-17 14:36:40 UTC,I'm fine with simply making this public at any time.
1814596,2021-02-24 13:19:58 UTC,This appears to already be fixed; when running the reproducer it fails to fchmod:
1814596,2019-10-09 23:32:33 UTC,"DynamicUser is only supported in systemd>=235 so this is not needed for xenial, only bionic and disco."
1814596,2019-10-09 14:18:19 UTC,"This is fixed in systemd 242 present in Eoan.
@seth-arnold Please target to releases to which the fix should be backported according to Security Team's opinion."
1814596,2019-04-25 22:18:49 UTC,Thanks Jann
1814596,2019-04-25 17:23:36 UTC,The copy of this bug report at https://bugs.chromium.org/p/project-zero/issues/detail?id=1771 is now public.
1814596,2019-04-17 11:52:22 UTC,"What to do with this? The 90 days should end on May 5th 2019, though the above PR (https://github.com/systemd/systemd/pull/12106) has been already merged upstream for a while."
1814596,2019-02-05 03:18:11 UTC,"Hello Jann, thanks for the excellent report."
1814596,2019-03-18 12:00:07 UTC,"Hi,"
1814596,2019-03-05 16:11:57 UTC,CVEs assigned:
1814596,2019-02-13 15:27:19 UTC,"> Without really the need of another process to help the
> service, as long as there is a writable path (with no
> nosuid flag) somewhere accessible by both the local
> attacker and the service
"
1814596,2019-02-13 10:23:48 UTC,"> I disagree. This, in itself, is working normally. If you pass
> a file descriptor to some file, the recipient can use the
> file descriptor just like the sender could; and if you pass
> a file descriptor to a directory, the recipient gains the
> ability to look up surrounding paths.
>
> I think the difference here is that I expect systemd's
> controls on this to be enforced in a way that is kind of
> like DAC - systemd prevents the service from directly
> accessing the filesystem, but allows it to gain access if
> that access is granted by another process with access -
> while you expect Mandatory Access Control that can not be
> overridden by other unprivileged userspace processes.
"
1814596,2019-02-08 12:43:24 UTC,"> The attack scenario seems either the service is malicious or
> a local attacker was able to exploit a vulnerable service and
> he is now trying to escape the sandbox enforced by systemd.
"
1814596,2019-02-08 11:02:24 UTC,"Hello,"
1814596,2019-03-21 13:34:00 UTC,Upstream PR to implement fixes: https://github.com/systemd/systemd/pull/12056
1814601,2021-02-23 17:11:25 UTC,Triaged to medium.
1814602,2019-02-07 23:28:08 UTC,I believe if you put:
1814602,2019-05-20 04:17:33 UTC,[Expired for netplan because there has been no activity for 60 days.]
1814602,2019-05-20 04:17:34 UTC,[Expired for netplan.io (Ubuntu) because there has been no activity for 60 days.]
1814605,2020-09-22 07:15:40 UTC,"neutron_bridge_name depends on that other variable, but I'm still not getting what override is meant to help in here."
1814605,2019-02-05 00:22:31 UTC,"I've tracked this error to
https://github.com/openstack/kolla-ansible/blob/stable/queens/ansible/roles/neutron/templates/ml2_conf.ini.j2#L76"
1814605,2020-09-17 03:51:34 UTC,How specifically is ml2_conf.ini modified to resolve this issue for the neutron_external_interface?
1814607,2019-02-18 09:47:31 UTC,My first guess is that this might be an amdgpu-specific problem. So yes please do try a non-Hades system. I'm running 18.04.2 and can't reproduce any problem using Intel graphics.
1814611,2020-03-30 12:49:58 UTC,This bug was fixed in the package apport - 2.20.9-0ubuntu7.13
1814611,2020-03-27 16:39:26 UTC,"This, apport/2.20.9-0ubuntu7.13 (i386), has passed after a retest."
1814611,2020-03-26 09:19:17 UTC,This bug was fixed in the package apport - 2.20.11-0ubuntu8.7
1814611,2020-03-26 09:09:17 UTC,"The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1814611,2020-03-19 18:24:40 UTC,"All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.13) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1814611,2020-03-19 18:02:34 UTC,"On an Ubuntu 19.10 system I installed the version of apport from eoan-proposed and I was able to report a bug to Launchpad about gnome-terminal, as such I'm setting this to verification-done for eoan."
1814611,2020-03-19 17:56:56 UTC,"I installed the version of apport from bionic-proposed and was able to report a bug to Launchpad about gnome-terminal, so I'm setting this to verification-done for bionic."
1814611,2020-03-19 15:52:44 UTC,"Hello jimav, or anyone else affected,"
1814611,2020-03-19 15:37:52 UTC,"Hello jimav, or anyone else affected,"
1814611,2020-03-10 04:59:02 UTC,This bug was fixed in the package apport - 2.20.11-0ubuntu19
1814611,2020-03-04 16:51:21 UTC,It certainly caused me to waste some time trying to work out why it was not sending them.
1814611,2020-02-02 21:02:15 UTC,"So, um, this has been broken since Bionic and still not fixed, despite the fact that ubuntu-bug is the only supported way for reporting bugs?"
1814611,2019-07-26 19:29:07 UTC,"Well if ""automatic"" sending is enabled in Settings->Privacy->Problem Reporting, then
  is-enabled is ""enabled"" and is-active is ""active""."
1814611,2019-02-07 20:00:26 UTC,apport will first try using xdg-open and that also appears as being found in the strace output. What happens if your run 'xdg-open http://bugs.launchpad.net'?
1814611,2019-02-09 04:47:19 UTC,xdg-open http://bugs.launchpad.net opens the page in Firefox.
1814611,2019-02-09 04:48:48 UTC,x not z
1814611,2019-07-04 01:56:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814611,2019-07-04 02:02:28 UTC,I'm using ubuntu 18.04 with all updates installed.
1814611,2019-07-26 19:41:31 UTC,"Clarification: By ""settings"" I meant the single setting (as seen by users) controlled by the ""Send error reports to Canonical"" switch in Settings->Privacy->problem"
1814611,2019-07-04 02:20:59 UTC,"For this to work, I had to enable the error reporting switch in system settings/privacy protection."
1814611,2019-07-26 16:42:59 UTC,What is the output of 'systemctl is-enabled whoopsie' and 'systemctl is-active whoopsie'? Thanks in advance.
1814611,2019-07-26 05:54:52 UTC,"In privacy settings, it says I am enabling ""Send error reports to Canonical... Send report *automatically*""."
1814611,2019-07-04 02:09:24 UTC,"Documentation says (after having pressed the ""send"" button):"
1814611,2019-07-04 02:55:58 UTC,A quick fix could be to document at https://help.ubuntu.com/community/ReportingBugs that the error reporting must be switch on first.
1814611,2019-07-09 13:09:22 UTC,"This is still a UX bug, as thomas303 said, ubuntu-bug should still inform the user of what happened and why."
1814613,2019-02-05 11:27:31 UTC,"Reassigned to qtdeclarative-opensource-src which is responsible for the qmlscene binary. qtchooser is just a ""wrapper to select between Qt development binary versions."""
1814613,2019-02-05 18:23:12 UTC,"Ok, thanks.  FYI the underlying qmlscene executable (/usr/lib/qt5/bin/qmlscene)
is provided by the ""qmlscene"" package in Ubuntu 18.04."
1814613,2019-02-14 03:50:30 UTC,Upstream bug: https://bugreports.qt.io/browse/QTBUG-73818
1814617,2019-09-20 10:18:13 UTC,This is a known limitation of snapd https://forum.snapcraft.io/t/limitations-in-snapd/9718
1814631,2019-10-31 02:57:22 UTC,2.6.7 release never went out. This fix was instead released in 2.6.8 - re-targeting this report.
1814631,2019-08-26 11:17:50 UTC,This is now released as part of the 2.6.0 release of python-libjuju. You can see the release announcement here.
1814631,2019-04-15 10:49:00 UTC,"Whilst we wait for this to be fully provided by libjuju, would it be possible to get any sample code for how we can do it using the straight API facades?"
1814631,2019-02-05 10:39:45 UTC,@thumper Will your team do this or do you want help from Cory?
1814631,2019-06-17 14:43:37 UTC,This is actively being worked on as Juju works this cycle to bring CMR relations and URL to bundles. As work there progresses we'll also be adding CMR support to libjuju for both individual charms as well as supporting the new bundle expressions.
1814633,2019-07-16 07:37:58 UTC,Thanks for the quick response
1814633,2019-07-16 17:07:47 UTC,I'll need to obfuscate the logs which may take some time.  Some quick greps:
1814633,2019-07-16 15:32:32 UTC,"@Ed Stewart (emcs2),"
1814633,2019-07-16 13:59:44 UTC,Thanks!
1814633,2019-07-16 13:25:44 UTC,"Hmm, I was playing around with 'controller-config' to answer you but was actually looking at the output of 'juju help model-config' to get config keys... :D You are absolutely right - image-metadata-url is a model property.
However, I am a bit 'surprised' that the new image-metadata-url seems to have no effect. I'll look into it my tomorrow. Any chance you could provide logs around the time when you would have expected the URL to be hit when provisioning a new VM into the model. I would have love to see a TRACE level but this might be very verbose..."
1814633,2019-07-16 07:00:48 UTC,"Also image-metadata-url is actually a controller-config. So on a bootstrap controller, you'd want to run 'juju controller-config image-metadata-url=<ur new url>', see 'juju help controller-config' for configuration keys. You might also ensure that image-stream is correct."
1814633,2019-04-02 06:00:19 UTC,"Hi Ian,"
1814633,2019-07-16 06:46:37 UTC,"FYI we have been testing this successfully, so thanks for the update."
1814633,2019-04-16 08:22:29 UTC,Thanks for the update - looking forward to the beta
1814633,2019-04-16 05:15:09 UTC,Ed - thanks for the report. Thanks for your patience while other issues were being addressed.
1814633,2019-04-02 05:01:44 UTC,The available image ids for the GCE regions is queried at bootstrap time and is sourced from here:
1814633,2019-07-16 22:55:55 UTC,"I have opened a separate report to deal with changed image-metadata-url (bug # 1836814) since the request reported here has been addressed. We should continue this conversation there. While opening a new report, I have discovered a bug that was describing similar failures around image-stream."
1814633,2019-07-16 06:58:09 UTC,"@Ed Stewart (emcs2),"
1814633,2019-02-05 08:38:38 UTC,For info; the GCP provider for juju doesn't seem to follow the standard pattern of simplestreams.
1814634,2019-10-31 03:30:33 UTC,Removing from a milestone as this work will not be done in 2.6 series.
1814635,2019-02-06 06:14:30 UTC,"Trust is just setting the application config 'trust: true'. I think you can
do it with a regular ""juju config app trust=true"", which you could do in
the python library. It probably isn't wrapped as a ""Trust"" wrapper, like we
do in the CLI."
1814635,2019-02-05 11:03:43 UTC,@thumper Let me know if you want Cory's help on this.
1814635,2019-10-31 02:58:38 UTC,2.6.7 release never went out. This fix was instead released in 2.6.8 - re-targeting this report.
1814638,2019-02-13 19:49:42 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1814639,2019-03-22 03:05:55 UTC,This PR https://github.com/juju/juju/pull/9942 changes the output for help to be https://pastebin.ubuntu.com/p/9t2yhkxbbR/
1814640,2019-02-05 09:23:19 UTC,"$ snap info sshoot
name:      sshoot
summary:   Manage sshuttle VPN sessions
publisher: Alberto Donato (ack)
contact:   https://github.com/albertodonato/sshoot
license:   GPL-3.0+
description: |
  Command-line interface to manage multiple sshuttle VPN sessions."
1814640,2019-02-05 09:27:37 UTC,"snapd seems to not understand the license that the store does, so that when the snaps are installed it thinks the license is unset."
1814640,2019-02-05 13:25:13 UTC,When the snap is installed a number of fields in `snap info` come from the installed snap; license is one of these.
1814640,2019-02-05 14:29:01 UTC,"> The store treats it as if it were per snap, meaning that it lets a publisher unilaterally change the license of something, which is not ideal.
"
1814640,2019-02-05 14:40:48 UTC,"> I also believe that snapcraft *does* support license, but only when actually running 3.x code (i.e. base: keyword is present).
"
1814640,2019-02-05 14:41:18 UTC,"That is correct, as evidenced by this test:
https://github.com/snapcore/snapcraft/blob/master/tests/spread/general/license-valid/task.yaml
and this one
https://github.com/snapcore/snapcraft/blob/master/tests/spread/general/license-invalid/task.yaml"
1814640,2019-02-05 15:09:52 UTC,"Not sure what combination I tried and failed, last weekend; I'm glad it's working in snapcraft."
1814640,2019-02-05 15:32:48 UTC,"The behavior of snapd seems correct, in the sense different revisions of the snap may have different licenses. ""Rectifying"" a license in a way that future information affect past code seems very bogus in this context."
1814640,2019-02-14 04:43:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814643,2019-06-03 14:15:16 UTC,"After a couple of updates this bug went away, so it can be closed"
1814643,2019-07-02 13:27:08 UTC,"Thanks, closing then"
1814643,2019-07-03 02:47:08 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1812266, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1814646,2019-03-13 10:01:24 UTC,"3.13.0-166.216~precise1 - generic
Regression test CMPL, RTB."
1814646,2019-03-13 13:03:24 UTC,All tasks have been completed and the bug is being set to Fix Released
1814650,2019-02-05 11:19:12 UTC,"That appears to be a printer, so I'm guessing it's not a problem with the installer."
1814653,2019-02-05 11:10:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814653,2019-02-07 08:22:27 UTC,"The issue is that if `get_python_lib()` is called with `prefix='/usr/local'` argument then Ubuntu version returns:
``` sh
$ /usr/bin/python3 -c ""from distutils.sysconfig import *;print(get_python_lib(prefix='/usr/local'))""
/usr/local/lib/python3/dist-packages
```"
1814653,2019-06-10 10:31:12 UTC,Reported this to the correct package: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1832215
1814729,2019-03-28 22:10:08 UTC,"Note that it only takes effect when the multipass VM machine is created.  Hence, if you have an existing VM, you not only need to use multipass to stop it, you also need to delete it (and purge the deleted image) before snapcraft re-create it and in doing so check the environment variables."
1814732,2019-02-05 20:06:06 UTC,"Hello Anton, it looks a little like there may not be any EFI partitions on this system:"
1814746,2019-03-05 15:44:05 UTC,All tasks have been completed and the bug is being set to Fix Released
1814751,2019-03-06 12:14:25 UTC,All tasks have been completed and the bug is being set to Fix Released
1814753,2019-02-21 19:40:20 UTC,go ahead and publish to edge
1814753,2019-02-27 11:07:04 UTC,All tasks have been completed and the bug is being set to Fix Released
1814756,2019-02-05 13:02:53 UTC,Please add version information and test on nightly if possible as well.
1814756,2019-02-06 04:01:17 UTC,This is perhaps a misunderstanding in terms.
1814756,2019-02-08 04:39:27 UTC,Hmm... I was too hasty in reviewing this.
1814756,2019-07-08 20:21:48 UTC,Fixed a few weeks ago with the new zone fill algorithm.
1814761,2019-02-28 10:00:52 UTC,All tasks have been completed and the bug is being set to Fix Released
1814767,2019-02-05 13:45:25 UTC,"This was fixed in groff upstream between 14.04 and 16.04, by https://git.savannah.gnu.org/cgit/groff.git/commit/?id=49abd7a9093ae903bb0032eb74d647fb481d2acb.  However, snapd could work around it by not emitting doubled .TP lines in its man page output; as far as I can see it has no good reason to do so."
1814767,2019-02-05 14:58:28 UTC,https://github.com/snapcore/snapd/pull/6476 FWIW
1814773,2019-02-22 03:35:39 UTC,"I have some confidence that this is happening because you're running terminator with python3 instead of python2.
In python 2 the syntax is valid:
except (KeyError,ValueError), ex:"
1814781,2019-03-07 08:48:19 UTC,Changing the component for this bug.
1814786,2019-11-07 03:25:18 UTC,"Did Juju ever error as opposed to warn about config attributes that didn't match the schema? For a long time, Juju had no way of allowing model config that was provider specific, so it had to allow unknown attributes to be set - the provider would use them but the attribute was unrecognised by Juju's config schema. eg AWS clouds can have a vpc-id, Openstack can have use-floating-ip etc. So Juju just used to warn about such values. And I suspect that behaviour still exists today. Or are you saying for controller config, we used to be more strict and genuinely did error?"
1814786,2019-11-07 03:43:55 UTC,"No, juju never errored out, only warned about unknown config."
1814787,2019-09-19 14:59:11 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1814792,2019-02-08 11:05:15 UTC,"I just discovered option --asynchronous-upload, which makes my request largely irrelevant (except for the reduced IO usage)."
1814803,2019-04-22 19:19:38 UTC,I tried adding this key by
1814803,2020-04-11 15:17:13 UTC,Does this problem have a solution?
1814803,2019-02-05 20:23:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1814803,2019-04-22 19:16:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814816,2019-02-06 10:37:19 UTC,"Hi there,"
1814816,2019-02-06 10:37:54 UTC,s/directly/directed/
1814827,2019-02-06 16:16:54 UTC,apport information
1814827,2019-02-06 16:16:47 UTC,apport information
1814827,2019-02-06 16:16:48 UTC,apport information
1814827,2019-02-06 16:16:50 UTC,apport information
1814827,2019-02-06 16:16:51 UTC,apport information
1814827,2019-02-06 16:16:56 UTC,apport information
1814827,2019-03-08 09:52:17 UTC,Result of 'sudo evtest':
1814827,2019-02-06 16:16:58 UTC,apport information
1814827,2019-02-06 16:17:04 UTC,apport information
1814827,2019-02-06 16:17:07 UTC,apport information
1814827,2019-02-22 13:39:28 UTC,"Please install evtest, then run `sudo evtest`, pick the one that looks like ""Toshiba input"" or similar, then attach the output of pressing wifi hotkey."
1814827,2019-02-06 16:16:46 UTC,apport information
1814827,2019-04-01 06:45:08 UTC,"Please add this to /etc/udev/hwdb.d/61-keyboard.hwdb
evdev:name:Toshiba*input*device:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSATELLITEP850:pvr*
 KEYBOARD_KEY_9e=wlan"
1814827,2019-02-06 16:16:57 UTC,apport information
1814827,2019-02-06 16:16:43 UTC,apport information
1814827,2019-02-06 16:16:52 UTC,apport information
1814827,2019-02-06 16:15:58 UTC,apport information
1814827,2019-02-06 16:16:42 UTC,apport information
1814827,2019-02-06 11:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1814827,2019-02-06 16:15:31 UTC,apport information
1814827,2019-02-06 16:15:34 UTC,apport information
1814827,2019-02-06 16:15:35 UTC,apport information
1814827,2019-02-06 16:15:37 UTC,apport information
1814827,2019-02-06 16:15:38 UTC,apport information
1814827,2019-02-06 16:15:30 UTC,apport information
1814827,2019-02-06 16:15:41 UTC,apport information
1814827,2019-02-06 16:15:43 UTC,apport information
1814827,2019-02-06 16:15:45 UTC,apport information
1814827,2019-02-06 16:15:47 UTC,apport information
1814827,2019-02-06 16:15:40 UTC,apport information
1814827,2019-02-06 16:15:48 UTC,apport information
1814827,2019-02-06 16:15:54 UTC,apport information
1814828,2019-02-06 01:38:41 UTC,"The remote unit names for a CMR are unique - the local model sees any connecting application named as remote-<uuid> and hence any remote units will be remote-<uuid>/0, remote-<uuid>/1 etc. So essentially the unit names are unique across controller, model etc. Does that help?"
1814828,2019-10-31 02:49:56 UTC,2.6.7 release never went out. This fix was instead released in 2.6.8 - re-targeting this report.
1814829,2019-11-27 17:50:40 UTC,"Reviewed:  https://review.opendev.org/693450
Committed: https://git.openstack.org/cgit/x/microstack/commit/?id=1a25e50a172db7331edf2f836f3c2005222bb4c5
Submitter: Zuul
Branch:    master"
1814829,2019-11-12 18:14:49 UTC,PR: https://review.opendev.org/#/c/693450/2
1814829,2019-04-30 14:43:36 UTC,"An update on the workaround for the download timeout issue: the cirros image now gets downloaded to /var/snap/microstack/common/images, so you'll want to sudo mkdir -p that path, and put the cirros image there if you want to download in advance."
1814829,2019-03-20 13:28:32 UTC,"Right now, microstack is pretty rude about port selection, hogging the default http and mysql ports. This makes it easy to find stuff, but not easy to run it alongside other projects on a laptop. I think that we should give this some thought, as possibly switch up the ports that it uses."
1814829,2019-11-12 18:14:21 UTC,"I've got a PR in for using non default ports for the dashboard (as well as MySQL and Rabbit, though both of those are hidden from operators)."
1814830,2019-02-07 12:25:43 UTC,"I am now studying the Grub2/Upgrading documentation and I intend to
perform the upgrade. Then I suppose I will not need a repair of the
menu.lst creation software, so we may close the complaint."
1814830,2019-02-07 07:19:14 UTC,"That the old version of the boot loader was not replaced might be an oversight in the updater or a feature for those systems which where installed a very long time ago. (If you are interested, see [1]).
Reading [2] it sounds like it is necessary to remove menu.lst before it will get re-generated again:"
1814830,2019-02-06 23:43:24 UTC,"I observe that menu.lst is used here for starting Linux. And I assume
that when the 'Software Updater' sends me this, it is needed and is not
obsolete. My policy is to use the most recent kernel update, provided
that I can get it working."
1814830,2019-02-06 10:44:11 UTC,Thanks for the reply.
1814830,2019-02-06 08:58:41 UTC,"This problem sounds like it might be related to problems in the setup but not the kernels themselves. Is /boot a separate filesystem (which possibly is out of space)? Looking into /boot, are all initrd* and vmlinux* files report a roughly similar size (du -h)? Unfortunately a bit messy to read but looking at /boot/grub/grub.cfg, do the references to the root disk (usually UUIDs) make sense?"
1814830,2019-02-05 22:30:06 UTC,This change was made by a bot.
1814830,2019-02-06 11:34:21 UTC,"I missed menu.lst mentioned before. This is a grub1 file and even for a 32bit (i386) installation I would have thought everything already migrated to use grub2. The only thing which I thought were still using menu.lst were paravirt Xen guests on the Amazon cloud.
There was some pain with grub1 and menu.lst related to configuration questions (do you want to keep the current version or install a new one). Answering keep there would any future update and basically keep people from using any updated kernel."
1814838,2019-03-25 04:28:04 UTC,"There is now a 4.01.01 version.  I have found that the pre-compiled versions on the XpdfReader.com site do not properly support printing to local printers, but a custom compiled version under Xubuntu 18.10 with system libraries does work.  Please check that cups printers are displayed on the print dialog before packaging."
1814838,2020-10-22 19:13:57 UTC,closing since the package is removed from Ubuntu
1814839,2019-02-18 09:54:42 UTC,Are you able to try Ubuntu 19.04 and tell us if the same problem happens there?
1814839,2019-02-19 01:08:08 UTC,"Daniel van Vugt wrote:

> Are you able to try Ubuntu 19.04 and tell us if the same problem happens
> there?
"
1814839,2019-02-19 07:25:51 UTC,"Yes, confirmed in both 18.04 and 19.04. Although the mode changed names from ""Sloppy"" to ""Focus on Hover"". It's still the same bug."
1814839,2019-02-19 07:30:30 UTC,Confirmed. If you would like to discuss the problem with Gnome developers then please report it here:
1814839,2019-02-19 21:06:00 UTC,Okay.  Upstream bug is https://gitlab.gnome.org/GNOME/mutter/issues/469
1814843,2020-09-18 18:15:10 UTC,Moved this issue to the kubernetes-docs project: https://github.com/charmed-kubernetes/kubernetes-docs/issues/471
1814844,2019-02-06 00:47:04 UTC,a little more info apparently when not using the encrypt my home option it works just fine...
1814850,2019-09-13 16:05:33 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1814850,2019-09-13 19:11:27 UTC,This issue was fixed in the openstack/python-mistralclient 3.10.0 release.
1814850,2019-08-28 13:15:38 UTC,"Reviewed:  https://review.opendev.org/676897
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=6c0bd2a26844b215f16252af7c28a88513451c90
Submitter: Zuul
Branch:    master"
1814850,2019-08-16 10:46:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676901"
1814850,2019-08-29 07:39:20 UTC,"Reviewed:  https://review.opendev.org/676901
Committed: https://git.openstack.org/cgit/openstack/python-mistralclient/commit/?id=e3357c4a92cb735698e96ebfb6ec711692ebf637
Submitter: Zuul
Branch:    master"
1814850,2019-08-16 10:03:09 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676897"
1814856,2019-02-06 08:28:37 UTC,"see debian bug: #904010
debian bug: #840748"
1814856,2019-02-15 14:12:02 UTC,done
1814859,2020-03-09 03:03:30 UTC,"I don't see any reason that it is related to security. Moving it back to the normal bug type ""Security""."
1814859,2019-02-07 14:14:56 UTC,"Can You do those calls with ""--debug"" option and provide output which You will have there?
It looks for me that it is more likely OSC issue instead of Neutron bug but if Your requests are reaching neutron server, can You also put here error which You got there?"
1814859,2019-02-07 14:29:02 UTC,"Indeed the request doesn't reach Neutron backend. Client debug output below:
$ neutron quota-update --firewall-rule 200 --debug
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
DEBUG: stevedore.extension found extension EntryPoint.parse('v1password = swiftclient.authv1:PasswordLoader')
DEBUG: stevedore.extension found extension EntryPoint.parse('token_endpoint = openstackclient.api.auth_plugin:TokenEndpoint')
DEBUG: stevedore.extension found extension EntryPoint.parse('noauth = cinderclient.contrib.noauth:CinderNoAuthLoader')
DEBUG: stevedore.extension found extension EntryPoint.parse('v2token = keystoneauth1.loading._plugins.identity.v2:Token')
DEBUG: stevedore.extension found extension EntryPoint.parse('none = keystoneauth1.loading._plugins.noauth:NoAuth')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3oauth1 = keystoneauth1.extras.oauth1._loading:V3OAuth1')
DEBUG: stevedore.extension found extension EntryPoint.parse('admin_token = keystoneauth1.loading._plugins.admin_token:AdminToken')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3oidcauthcode = keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
DEBUG: stevedore.extension found extension EntryPoint.parse('v2password = keystoneauth1.loading._plugins.identity.v2:Password')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3samlpassword = keystoneauth1.extras._saml2._loading:Saml2Password')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3password = keystoneauth1.loading._plugins.identity.v3:Password')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3adfspassword = keystoneauth1.extras._saml2._loading:ADFSPassword')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3oidcaccesstoken = keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAccessToken')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3oidcpassword = keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3kerberos = keystoneauth1.extras.kerberos._loading:Kerberos')
DEBUG: stevedore.extension found extension EntryPoint.parse('token = keystoneauth1.loading._plugins.identity.generic:Token')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3oidcclientcredentials = keystoneauth1.loading._plugins.identity.v3:OpenIDConnectClientCredentials')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3tokenlessauth = keystoneauth1.loading._plugins.identity.v3:TokenlessAuth')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3token = keystoneauth1.loading._plugins.identity.v3:Token')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3totp = keystoneauth1.loading._plugins.identity.v3:TOTP')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3applicationcredential = keystoneauth1.loading._plugins.identity.v3:ApplicationCredential')
DEBUG: stevedore.extension found extension EntryPoint.parse('password = keystoneauth1.loading._plugins.identity.generic:Password')
DEBUG: stevedore.extension found extension EntryPoint.parse('v3fedkerb = keystoneauth1.extras.ker..."
1814862,2019-04-23 23:57:40 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1814862,2019-06-23 04:19:19 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1814873,2020-03-12 05:55:58 UTC,"Confirmed using current charms, the 'Network Throughput' graph shows stats for all hosts when only one is selected.  I was unable to verify the drops/errors since my test VMs had no drops/errors to report."
1814874,2019-05-14 22:54:04 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1814874,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1814874,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1814874,2019-05-09 03:12:16 UTC,Cosmic VM with proposed kernel withstand the stress for over 12 hours.
1814874,2019-04-29 16:04:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1814874,2019-04-25 22:32:30 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1814874,2019-04-12 04:43:34 UTC,"Can be reproduced easily with Cosmic kernel, patch works as expected. A test kernel could be found here: http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Cosmic/"
1814874,2019-04-09 09:42:21 UTC,"Thanks for the feedback, I will see if I can reproduce this and SRU this patch."
1814874,2019-04-03 11:46:09 UTC,"I don't recall seeing a soft lockup at all, not a related one anyway. Sadly I don't have a specific command but I did find it triggered when:"
1814874,2019-04-03 11:21:21 UTC,"Hello Ken,"
1814874,2019-04-02 07:51:34 UTC,"Fix available in upstream:
https://github.com/torvalds/linux/commit/ca0246bb97c23da9d267c2107c07fb77e38205c9"
1814874,2019-05-08 11:36:22 UTC,Cosmic verification in progress.
1814874,2019-03-04 17:36:18 UTC,"As above: this should be fixed in Disco, though I have only just switched to the upstream kernel for testing, I suspect that Jagannathan's testing is correct."
1814874,2019-03-04 17:43:03 UTC,"As an aside: I'm seeing much better system response time using zRAM alone than I am using zswap alone, but this may have improved in the newer kernel. In both cases though I am using KSM and THP which clearly improve memory use."
1814874,2018-11-02 10:41:46 UTC,"Created attachment 279297
dmesg log of crash"
1814874,2018-11-06 12:28:15 UTC,"Created attachment 279341
Log before kernel panic and after hard reset"
1814874,2018-11-06 21:48:41 UTC,"(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface)."
1814874,2018-11-06 22:10:44 UTC,"Created attachment 279353
attachment-22937-0.html"
1814874,2018-11-07 01:40:55 UTC,"Created attachment 279367
attachment-27234-0.html"
1814874,2019-05-08 09:59:09 UTC,Bionic VM with proposed kernel withstand the stress for over an hour.
1814874,2019-02-06 09:16:54 UTC,Any update on this and does anyone know if this is a regression?
1814874,2019-02-12 10:47:55 UTC,"This seems related from Chrome OS:
https://bugs.chromium.org/p/chromium/issues/detail?id=822360"
1814874,2019-02-21 17:45:25 UTC,"Wait a second, you are sitting on a discontinued kernel. The fix has gone in back in December. Upgrade to longterm series, it's there since 4.19.6, and retest. Otherwise I do suggest that we close this issue."
1814874,2019-02-21 17:59:25 UTC,"I am going to enable zswap and z3fold to confirm the fix. Sorry, I didn't follow through after it was merged."
1814874,2019-02-21 18:08:53 UTC,I'm installing it too. I didn't know there was a fix in-place anywhere so this is good news! It'll take me a few days of testing to get a result.
1814874,2019-03-04 10:52:22 UTC,"I can confirm there have been no crashes since I switched, so closing. Thanks for the help and fix :)"
1814875,2019-02-06 12:04:44 UTC,"thanks, once the disco merge request is reviewed and in, we can look at backporting"
1814875,2019-03-14 17:07:00 UTC,ubiquity (19.04.6) disco; urgency=medium
1814877,2019-05-24 16:16:16 UTC,"Verified
root@node-1:~# cat /usr/lib/python2.7/dist-packages/openstack_dashboard/api/neutron.py | grep ""filter_values = list(filter_values)""
            filter_values = list(filter_values)"
1814877,2019-05-13 11:45:58 UTC,https://review.fuel-infra.org/#/c/41091/
1814877,2019-04-02 17:47:46 UTC,"Verified.
root@node-1:~# cat /usr/lib/python2.7/dist-packages/openstack_dashboard/api/neutron.py | grep  ""if not isinstance""
        if not isinstance(filter_values, (list, tuple, set, frozenset)):"
1814877,2019-02-06 11:28:42 UTC,https://review.fuel-infra.org/#/c/40348/
1814877,2019-04-08 11:35:46 UTC,"Reopened, the issue is not fixed yet."
1814880,2019-02-07 09:36:18 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/635462"
1814880,2019-02-07 11:26:40 UTC,"Reviewed:  https://review.openstack.org/635207
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=c5977cd0d6d0e827230ffd8264fecb94b5e48b15
Submitter: Zuul
Branch:    stable/rocky"
1814880,2019-02-07 16:39:30 UTC,"Reviewed:  https://review.openstack.org/635462
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=7b4ac4603fb7376760f20e9ba0a93d4399aad76a
Submitter: Zuul
Branch:    stable/queens"
1814880,2019-02-08 13:17:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/635833"
1814880,2019-02-19 13:10:04 UTC,"Reviewed:  https://review.openstack.org/635833
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=31ab969ed9bcc8a5602c41431292ef7ed96771a3
Submitter: Zuul
Branch:    stable/queens"
1814880,2019-03-14 10:43:17 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.3.0 release.
1814880,2019-03-18 00:36:03 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.3.1 release.
1814880,2019-02-06 16:29:48 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/635207"
1814896,2019-03-09 04:57:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814896,2019-03-26 22:48:21 UTC,Actually the recommended version is at least 18.09.2 which fixes some security issues. And there is a more stable 18.09.3 that would be even better
1814896,2020-05-19 16:12:46 UTC,"18.09.9 has been in stable for a while now, and 19.03.8 has been in beta for a short time (hopefully stable soon). :)"
1814908,2019-07-08 21:13:16 UTC,"New behaviour: if there's a selection that contains nothing more than tracks and vias, its tracks or vias will be increased/decreased.  Otherwise it works like it did before: it increases/decreases the current track width or via size settings (as seen in the popup menus in the auxiliary toolbar."
1814908,2019-07-08 21:18:58 UTC,"Fixed in revision b8013648d2c26be0eee107884ff2824612095464
https://git.launchpad.net/kicad/patch/?id=b8013648d2c26be0eee107884ff2824612095464"
1814908,2019-02-06 15:34:44 UTC,"I wouldn't get too comfortable with this work around.  In fact, it wont be available on linux builds with gtk3 because the legacy canvas is disabled.  This will be the case for all platforms in the next version.  I seem to remember a similar bug being reported so if someone finds it, please mark this bug as a duplicate."
1814908,2019-02-06 15:28:34 UTC,Thanks John for the tip.
1814908,2019-02-06 15:05:48 UTC,I agree there should be a proper hotkey for adjusting the width of selection (or under the cursor).
1814908,2019-02-07 09:48:58 UTC,@Laurent: That bit is definitely a bug! The context menu should certainly still open the properties dialog!
1814909,2020-02-03 21:30:44 UTC,"Change abandoned by Shannon Mitchell (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/705555
Reason: Submitting a separate bug just for the public/private url fix."
1814909,2020-02-03 20:58:51 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705555"
1814909,2019-10-16 22:01:25 UTC,"Reviewed:  https://review.opendev.org/688895
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=eccb5c13fec9d9efcccb821dbcf0f344cd515eec
Submitter: Zuul
Branch:    stable/stein"
1814909,2019-10-16 10:24:47 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/688895"
1814909,2019-08-23 20:58:19 UTC,"Reviewed:  https://review.opendev.org/672948
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=288634ce0bf042bed614b3f764753d7b65a7170f
Submitter: Zuul
Branch:    master"
1814909,2019-07-26 10:55:27 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/672948"
1814909,2019-07-01 08:40:46 UTC,"After testing this patch, I get the following error:"
1814909,2019-02-27 09:03:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639601"
1814909,2019-02-13 20:30:14 UTC,Another note:
1814909,2019-02-13 14:29:26 UTC,Just verified this a few minutes ago. Solves the issue for me. Netherless the practice to go to the external API should be questioned.
1814909,2019-02-13 13:21:50 UTC,+1
1814909,2019-02-12 17:13:30 UTC,Here is the patch we did in our Rocky OSA deployment to solve the bug:
1814913,2019-03-24 23:39:35 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1814913,2019-03-22 03:44:19 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1814913,2019-02-06 15:12:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/635185"
1814913,2019-02-07 15:17:38 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/635534"
1814913,2019-02-07 14:17:35 UTC,"Reviewed:  https://review.openstack.org/635185
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ccec9ba82de7c9525981a34bb126e9ca98042d04
Submitter: Zuul
Branch:    master"
1814913,2019-02-11 01:14:56 UTC,"Reviewed:  https://review.openstack.org/635534
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cb65d3d69c2b36a1a18d3fe4347b445f17f6d856
Submitter: Zuul
Branch:    stable/rocky"
1814916,2019-02-06 15:58:26 UTC,"Something is messed up because looking at the c-api logs, the MessagingTimeout happens before even 60 seconds have passed. The request starts here:"
1814916,2019-02-12 13:21:16 UTC,Seen again here:
1814921,2019-03-06 12:15:30 UTC,"Which version? I can try to test. However, as I wrote previously the issue
disappears from time to time even on the current kernel.
At the moment I have a sound card correctly detected."
1814921,2019-03-06 11:28:00 UTC,Does previous kernel version work?
1814921,2019-02-07 12:21:57 UTC,"The same error persists when booted from Ubuntu 18.04 USB live stick.
However, after power cycle prompted at Live Ubuntu shutdown, the sound card had been correctly detected in my main Ubuntu 16.04."
1814921,2019-02-07 09:19:22 UTC,"Unfortunately, it worked only before Suspend. After that again Dummy output only in Sound settings.
Reboot doesn't help. It's a strange problem."
1814921,2019-02-07 10:22:47 UTC,"I'm almost sure
dmesg:
[    7.949843] snd_hda_intel 0000:00:1f.3: no codecs found!
is related to the problem."
1814921,2019-02-06 16:56:22 UTC,Updating the BIOS fixed the issue for me. Please consider whether the bug requires further investigation.
1814921,2019-02-06 15:41:01 UTC,apport information
1814921,2019-02-06 15:41:03 UTC,apport information
1814921,2019-02-06 15:41:03 UTC,apport information
1814921,2019-02-06 15:41:00 UTC,apport information
1814921,2019-02-06 15:40:58 UTC,apport information
1814921,2019-02-06 15:40:57 UTC,apport information
1814921,2019-02-06 16:00:07 UTC,This change was made by a bot.
1814923,2019-02-07 16:27:04 UTC,"This is a valid request, though probably not a very common need, it can be useful."
1814923,2019-05-16 12:51:46 UTC,"Fixed in revision 6ade8c25e1bfb6d0eb6d591a17c995e70a4dbc24
https://git.launchpad.net/kicad/patch/?id=6ade8c25e1bfb6d0eb6d591a17c995e70a4dbc24"
1814925,2019-07-20 06:09:18 UTC,"I can confirm this happens also with 19.04
DMI: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 04/18/2019
Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)"
1814925,2019-02-18 08:00:45 UTC,"Looks like the same chip as bug 1520343. Maybe merge with that bug, or update it."
1814925,2019-02-18 07:55:02 UTC,Thanks. If comments #4-#5 are correct then this bug should be assigned to package 'linux-firmware' instead of 'bluez'.
1814925,2019-02-13 19:53:27 UTC,Dell OEM image with updated kernel has the qca\qca6174 fix.  I reloaded the dell image and have not been able to reproduce this issue with LE BT mouses.  I will let it run and confirm.  So it looks like the issue is just with the generic image not dell image.  non-oem.
1814925,2019-02-06 18:51:12 UTC,"More detailed information on this issue is below:
The customer has Ubuntu OEM through Dell.  The laptop goes into deep sleep over night and they can no longer use their BT devices.  You click on bt via GUI and try to toggle on and it looks like it is doing something and goes right back to off."
1814925,2019-02-06 16:29:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814925,2019-02-07 12:50:50 UTC,I am told by internal engineering the Qualcom fix below is being tested for this issue:
1814926,2019-02-06 17:00:03 UTC,This change was made by a bot.
1814927,2019-02-06 17:01:15 UTC,"As jistr explained on IRC, ""the reason was that in the config-data/foo there's a lot of files which we don't want copied into the containers. So we only look at files which changed in the duration of the puppet run, copy them into config-data/puppet-generated/foo and that then gets used for the containers."""
1814927,2019-02-06 17:10:14 UTC,"whatever works for me, if I can put a ""never use puppet-generated in tht files"" into the YAML/pep checker in the end"
1814927,2019-02-06 17:24:24 UTC,some background from irc
1814927,2019-02-06 17:28:18 UTC,"so the current logic is: if the container is started by kolla_start, it must use files from puppet_generated."
1814928,2019-02-11 11:16:13 UTC,"Have you also tried with --destructive-mode? (assuming you're running inside the container, otherwise it can install dependency packages in your host system)."
1814928,2019-06-17 04:17:47 UTC,[Expired for Snapcraft because there has been no activity for 60 days.]
1814929,2019-02-10 21:30:48 UTC,Fix commited x1.3.1-18.
1814929,2019-02-06 16:53:26 UTC,The attached patch solves the issue.
1814929,2019-02-06 17:52:00 UTC,Bug fix proposed for merge.
1814932,2019-02-06 17:32:46 UTC,yea the atop code doesn't work with dnf/fedora28
1814934,2020-05-27 20:31:01 UTC,"For option 1, I'm not sure how easy it would be to copy over the comments; a separate model for PackageDeclarationClosedComments?"
1814934,2020-05-28 15:37:19 UTC,"15:28 < nessita> hasanammar, what do you think of a slight variation of option 1, where the PackageDeclarationClosed model has ""static"" fields holding the frozen view of the declaration state to that point? in there, the comments do not need to be a separated model, but a list of strings saved for future auditing
15:28 <@     roadmr>| frozen! let it gooooo let it goooo
15:28 < hasanammar> nessita, yup, that would work as well
15:31 < hasanammar> nessita, the nice thing there is that the comments are essentially a transcript and not really comments (which can be added/removed)
15:32 <@     roadmr>| +1 on that, just a historical log is enough
15:36 < nessita> hasanammar, ok, great, will propose that in the bug as resolution"
1814936,2019-03-19 23:43:38 UTC,I think the behavioral component may be to log the browser in to google.
1814936,2019-03-19 23:45:36 UTC,"I've narrowed down to $HOME/.config/chromium/Default/Preferences.  When I
kill all the chromium-browser processes and restore that file to a prior
version, chromium-browser starts normally."
1814936,2019-03-19 23:48:47 UTC,Affects users on xenial and Debian stretch as well.
1814936,2019-03-20 15:44:02 UTC,Are there any extensions installed on those profiles that get corrupted?
1814936,2019-03-20 17:22:23 UTC,"On Wed, Mar 20, 2019 at 8:55 AM Olivier Tilloy
<email address hidden> wrote:

>
> Are there any extensions installed on those profiles that get corrupted?
"
1814936,2019-03-20 18:22:38 UTC,"> > Could you please file an upstream bug report at
> > https://bugs.chromium.org/p/chromium/issues/list and share the link
> > here?
>
> OK, I'll try to do that.
"
1814936,2019-03-20 19:30:53 UTC,"OK, maybe here?  But lots of those are Chrome browser, not chromium-browser."
1814936,2019-03-20 20:40:49 UTC,"The link is correct. Just click on the ""New issue"" button to report a bug (you might need to create an account)."
1814936,2019-03-20 21:58:40 UTC,Thanks Oliver.
1814938,2020-03-24 18:08:18 UTC,I can confirm that davidaf's work around worked. Though the interesting thing to me was that in 19.10 I didn't have to put the file in initrafs. After upgrading to the 20.04 daily builds this became necessary. Not sure if that means anything or not. Just thought I'd provide an extra data point.
1814938,2020-03-03 19:24:43 UTC,SOLVED.
1814938,2019-02-07 03:57:47 UTC,"[drm:drm_load_edid_firmware [drm]] *ERROR* Requesting EDID firmware ""edid/edid1.bin"" failed (err=-2)"
1814938,2019-02-06 18:00:06 UTC,This change was made by a bot.
1814938,2019-03-06 16:15:21 UTC,Is the EDID file in initramfs?
1814940,2019-02-14 00:04:00 UTC,This issue also sometimes occurs when adding translations for Library Name in Administration -> Server Administration -> Organizational Units
1814940,2020-04-27 21:51:31 UTC,This is resolved in 3.5 for the Copu/Item Statuses screen by the new angular interfaces.
1814943,2019-02-06 19:04:04 UTC,Patch ready for testing:
1814943,2019-03-01 17:29:31 UTC,"I can confirm that the page title was missing, and that the fix works to add it in.  Tested on EG 3.2.3"
1814943,2019-03-05 21:24:35 UTC,Works as advertised.  sign off at user/rogan/lp1814943
1814943,2019-04-29 14:47:06 UTC,"Removing the 3.1 target, as the closed dates editor did not have an AngularJS version until 3.2."
1814943,2019-04-29 14:51:59 UTC,"Pushed to master, rel_3_3, and rel_3_2, along with a follow-up that removes an ersatz ctx.page_type line. Thanks, Terran, Josh, and Rogan!"
1814959,2019-02-08 01:31:16 UTC,"Everything Jay ran by hand is part of the prepare_codebase reaction in the charm, we may just want to add a reaction to call that when plugins change."
1814959,2019-02-15 15:25:39 UTC,"David is correct.  The issue is that the plugin are loaded after these steps are run.  To fix this bug, the code needs to be adjusted to download the plugins first, then do rhe bundle steps."
1814962,2019-02-21 16:05:40 UTC,Fix has been backported to 2.5 via https://github.com/juju/juju/pull/9774
1814962,2019-02-14 09:11:49 UTC,Fixed with https://github.com/juju/juju/pull/9747
1814962,2019-02-12 13:58:02 UTC,"Apologies, I completely misread this and missed the run vs run-action distinction. This is definitely something that we could look at adding to flesh out the support here. Thanks for the prod."
1814962,2019-02-07 21:57:39 UTC,This is added in Juju 2.5 and there are instructions on using it in the help docs.
1814964,2019-02-18 09:59:32 UTC,Please run this command:
1814964,2019-03-06 20:54:40 UTC,Sorry for the slow reply!  See attached.
1814964,2019-03-07 01:54:02 UTC,Thanks. It appears this isn't the problem I thought it was.
1814964,2019-03-08 06:47:52 UTC,"Thanks Daniel for the suggestion, I'll try it.  The audio issue doesnt always happen and I can't spot exactly what the triggers are, this morning 3 sessions are all working fine."
1814964,2019-03-08 07:06:00 UTC,"No I have no more ideas on the audio issue. In fact if ""The audio issue doesnt always happen"" then that suggests even comment #4 might not work."
1814964,2019-03-08 07:25:30 UTC,"Understood.  I wont have daemonize=yes set, I will wait until the bug next occurs."
1814964,2019-03-08 07:42:55 UTC,A quick Google shows some hints:
1814964,2019-03-12 22:54:42 UTC,"thats actually really useful information.  the Arch link in particular.  think i am happy to have my family members able to change volume etc, but not sure how to set up a systemd service."
1814964,2019-03-16 08:37:03 UTC,"I was reading more about pulseaudio and saw this on one of the Arch pages:
https://wiki.archlinux.org/index.php/PulseAudio#Configuration_files
""PulseAudio uses udev and logind to give access dynamically to the currently ""active"" user"""
1814964,2019-03-16 08:40:39 UTC,"ah, sadly not.  added my user to audio group, logged in/out and still dont get sound (my wife's session is running in the background)"
1814965,2019-02-06 21:52:43 UTC,the bug is related to this image http://cdimage.ubuntu.com/releases/18.04/beta/
1814971,2019-02-07 00:14:53 UTC,"For me, parseable snap info is spelt ""curl --silent --unix-socket
/var/run/snapd.socket a/v2/find?name=$x"". I would like snap to grow a 'snap
query' command like lxc has but until then..."
1814971,2019-02-07 02:46:51 UTC,"That's helpful Michael, thanks!"
1814972,2019-02-08 04:27:05 UTC,Fixed in mythtv_30.0+fixes.20190207.1c2068c62b
1814978,2020-02-05 17:01:55 UTC,Related bug #1697003 (webstaff: keyboard-nav for uib-dropdown)
1814978,2019-05-20 14:44:05 UTC,"Confirmed in webclient 3.1.10 using steps above. Can tab through the main menu fine, but when getting to a dropdown menu, cannot navigate any further via keyboard."
1814980,2019-05-30 22:34:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1814983,2020-10-28 11:11:23 UTC,Excellent news.
1814983,2020-10-28 02:46:41 UTC,"Hi Colin, thanks so much for giving this another look. I don't see any references to trying different zfs_arc_meta_limit* settings here!"
1814983,2020-10-27 12:22:52 UTC,"OK, Seems like we can resolve this by using some tuning.  I was able to reproduce this on a single drive SSD pool configuration with 30 clones of the linux source and grep'ing for various strings."
1814983,2020-06-10 09:17:44 UTC,"The fix seems to be causing some issues, as reported here:"
1814983,2020-05-15 15:55:44 UTC,"Thanks for the heads-up on this fix. It does not seem to have been merged yet, so I'll wait for it to get through the regression tests and once it's upstream I'll backport it for you to test."
1814983,2020-05-15 03:55:31 UTC,"Hello Colin, this looks promising for my arc_prune spinlock contention problems:"
1814983,2020-04-18 00:27:25 UTC,"I forgot to mention, my l2arc is used on the second pool on this system:"
1814983,2020-04-18 00:18:34 UTC,"Andreas, this system is running 18.04 LTS, 0.7.5-1ubuntu16.8, 4.15.0-91-generic."
1814983,2020-04-18 00:24:32 UTC,"Colin, thanks for the link to https://github.com/openzfs/zfs/issues/9966 ; unfortunately I think that's a different problem, my meta use seems less drastic than the github issue"
1814983,2020-04-17 21:49:23 UTC,"Hi there, https://github.com/openzfs/zfs/issues/9966 contains some advice that seems pertinent to this issue."
1814983,2020-04-16 23:37:25 UTC,"Thanks Colin,"
1814983,2020-04-17 13:06:18 UTC,"For what is worth, I also have the arc_prune eating cpu problem. I thought it was because my ""machine"" has just 3Gb of RAM, but this report makes me think there is something wrong in that area with zfs 0.8.x, since you have what, 64Gb of RAM?"
1814983,2020-04-17 02:15:26 UTC,"Writing 8589934592 (eight gigs) into the zfs_arc_dnode_limit seemed to make an improvement: the arc_prune threads would periodically spike above 20% CPU use, but would return to 2-5% CPU use quickly; it worked well for a long time, perhaps even hours, before all the arc_prune threads returned to ~50% CPU use."
1814983,2020-03-26 16:24:22 UTC,It may be worth reading the following article as it has some tuning tweaks that may help resolve your issue:
1814983,2019-02-11 00:48:34 UTC,"echo 1 > /proc/sys/vm/drop_caches  # still slow
echo 2 > /proc/sys/vm/drop_caches  # goes faster"
1814983,2019-02-08 07:02:39 UTC,"This is also repeatable on my pool of slower spinning metal disks, srv:"
1814983,2019-02-07 03:01:21 UTC,"Oh yes, and perf top output after dropping caches:"
1814983,2019-02-07 02:42:44 UTC,And top(1) output after dropping caches:
1814983,2019-02-07 02:39:35 UTC,Debugging by voodoo dolls: I made a wild guess that stumbling over cached objects was getting in the way. I dropped caches with:
1814983,2019-02-07 01:53:16 UTC,sudo perf top output:
1814983,2020-04-17 13:37:15 UTC,I've filed an issue with the upstream bug tracker: https://github.com/openzfs/zfs/issues/10222
1814984,2019-02-07 00:46:24 UTC,output file
1814984,2020-10-27 04:21:47 UTC,"In a PDF file, links point to positions on a page, there is no good way to translate these accurately to HTML marku as used by ebooks. In general PDF conversion has lots of limitations, https://manual.calibre-ebook.com/conversion.html#convert-pdf-documents"
1814994,2019-02-11 15:29:48 UTC,"I think this is an artifact of the fact that:
a) Ubuntu likes to distribute things from http:// so that you can get
proxies that share the load
b) Because of this Ubuntu signs their files with a GPG signature, so you
can trust the contents
c) LXD didn't want to implement GPG signature verification, so instead they
require that you download the content over HTTPS so you can trust the
source (though with things like MitM certificates and DNS poisoning that
isn't quite so trustworthy)."
1815001,2019-02-11 10:18:24 UTC,"Madhavi, as paer the CVE, all versions under 2.20 has this vulnerability. So,updating requirements to not support 2.20 does not fix the problem. Also, as I pointed out above certain platform/distro have released patches (for eg. Ubuntu has patches on 2.18)."
1815001,2019-02-11 08:54:22 UTC,"Can we update our requirements.txt , not to support requests 2.20.0?"
1815001,2019-02-07 16:50:29 UTC,"This is public knowledge, so I'm opening this up"
1815001,2019-02-08 11:08:30 UTC,OpenStack maste lists requests lib version as 2.21.0 >> https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L199
1815001,2019-02-07 16:50:10 UTC,"I would argue that this is not a security vulnerability of pypowervm. We're not requiring a vulnerable version of requests, we're just allowing for it. Anyone concerned about the requests vulnerability (and rightly so) is welcome to use a newer version of requests with pypowervm."
1815001,2019-02-08 13:01:24 UTC,"be careful... upper-constraints.txt just sets an upper limit. I.e. that means requests cannot be newer than 2.21.0. It does not mean that requests should be 2.21.0, which is a very different story."
1815003,2019-02-07 07:00:01 UTC,"netstat has a different view. It lists 2649 sockets, and 65 of them are under:
Active UNIX domain sockets (w/o servers)
...
unix  3      [ ]         STREAM     CONNECTED     22022469 /run/systemd/journal/stdout
unix  3      [ ]         STREAM     CONNECTED     22025835
unix  3      [ ]         DGRAM                    22022209
unix  3      [ ]         STREAM     CONNECTED     22027567
unix  3      [ ]         DGRAM                    22022210
unix  3      [ ]         STREAM     CONNECTED     22022016
unix  3      [ ]         STREAM     CONNECTED     22022934 /run/systemd/journal/stdout
..."
1815003,2019-02-07 07:01:09 UTC,All of the CLOSE_WAIT entries in netstat are for port 17070.
1815003,2019-02-08 01:55:35 UTC,I think the tcp keep alives would help with this.
1815019,2019-03-13 20:07:38 UTC,"I see, I just tried, and by default I get the krb5* options in /etc/pam.d/common-auth's pam_winbind.so line."
1815019,2019-03-13 18:29:25 UTC,"The krb5 options you were using in the pam_winbind.so line are only meant to be used with active directory controllers. Your smb.conf file shows your security to be of the ""domain"" style, which is an NT style controller which does not support kerberos."
1815019,2019-02-13 09:08:38 UTC,"Il 12/02/19 20:38, Andreas Hasenack ha scritto:> [...]

> I found some bugs in debian and upstream, still open, but in a
> ""needinfo"" state.


do you mean the bug https://bugzilla.samba.org/show_bug.cgi?id=10455?"
1815019,2019-02-13 08:09:13 UTC,I have forgot common-session!!!
1815019,2019-02-13 07:56:38 UTC,"Il 12/02/19 20:38, Andreas Hasenack ha scritto:

> Ok, can you please share your configuration files so I can give it a
> try?


of course!"
1815019,2019-02-12 14:00:18 UTC,I have enabled debugging in pam_winbind.conf but strange things happen... this is what I've done:
1815019,2019-02-12 14:27:32 UTC,"I write a new post because the behaviour has changed now... now if I run winbind offline the system goes really offline:
root@103note0512:~# smbcontrol winbind offline
root@103note0512:~# smbcontrol winbind onlinestatus
PID 1102: global:Offline BUILTIN:Online 103NOTE0512:Online MYDOMAIN:Offline"
1815019,2019-02-11 17:17:51 UTC,"Can you set these two to ""yes"" in pam_winbind.conf (or in the pam_winbind.so command line in the pam config):"
1815019,2019-02-11 15:51:17 UTC,"Il 11/02/19 14:41, Andreas Hasenack ha scritto:

> When you are offline, does ""getent passwd <user>"" still recognize your
> user? Both things need to work: the user must ""exist"", and the password
> must be correct, in the offline case.


yes, when winbind is offline ""getent passwd DOMAIN\\user"" correctly
shows the user infos..."
1815019,2019-02-11 13:41:27 UTC,"When you are offline, does ""getent passwd <user>"" still recognize your user? Both things need to work: the user must ""exist"", and the password must be correct, in the offline case."
1815019,2019-02-08 08:48:33 UTC,"Hi piviul,
I appreciate the bug report and your help to make Ubuntu better."
1815019,2019-02-12 19:38:08 UTC,"Ok, can you please share your configuration files so I can give it a try?"
1815022,2019-06-11 06:39:34 UTC,"------- Comment From <email address hidden> 2019-06-11 02:37 EDT-------
IBM bugzilla status -> closed, Fix released for all requested distros"
1815022,2019-06-03 08:45:34 UTC,This bug was fixed in the package s390-tools - 2.6.0-0ubuntu7.3
1815022,2019-05-23 14:28:29 UTC,"Package s390-tools 2.6.0-0ubuntu7.3 landed inbetween in cosmic's proposed pocket:
$ apt-cache policy s390-tools
s390-tools:
  Installed: 2.6.0-0ubuntu7.3
  Candidate: 2.6.0-0ubuntu7.3
  Version table:
 *** 2.6.0-0ubuntu7.3 500
        500 http://us.ports.ubuntu.com/ubuntu-ports cosmic-proposed/main s390x Packages
        100 /var/lib/dpkg/status
     2.6.0-0ubuntu7.2 500
        500 http://us.ports.ubuntu.com/ubuntu-ports cosmic-updates/main s390x Packages
     2.6.0-0ubuntu7 500
        500 http://us.ports.ubuntu.com/ubuntu-ports cosmic/main s390x Packages
I have it now running for an entire working day and it looks good, no regressions so far,
hence adjusting tags accordingly ..."
1815022,2019-05-23 09:26:10 UTC,"The s390-tools package s390-tools_2.6.0-0ubuntu7.3_s390x.deb for cosmic didn't landed yet in cosmic's proposed pocket.
Hence I downloaded and installed it manually:
$ apt-cache policy s390-toolss390-tools:
  Installed: 2.6.0-0ubuntu7.3
  Candidate: 2.6.0-0ubuntu7.3
  Version table:
 *** 2.6.0-0ubuntu7.3 100
        100 /var/lib/dpkg/status
     2.6.0-0ubuntu7.2 500
        500 http://us.ports.ubuntu.com/ubuntu-ports cosmic-updates/main s390x Packages
     2.6.0-0ubuntu7 500
        500 http://us.ports.ubuntu.com/ubuntu-ports cosmic/main s390x Packages
I'll let it go for a while until my eod - before I'm going to adjust the tags ..."
1815022,2019-05-23 08:55:24 UTC,This bug was fixed in the package s390-tools - 2.3.0-0ubuntu3.3
1815022,2019-05-23 08:45:26 UTC,"The verification of the Stable Release Update for s390-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815022,2019-05-20 12:58:28 UTC,"# dpkg-query -W s390-tools
s390-tools	2.3.0-0ubuntu3.3"
1815022,2019-05-16 16:47:23 UTC,"Hello bugproxy, or anyone else affected,"
1815022,2019-04-24 08:28:05 UTC,"Since LP 1814892 got just 'Fix Released' (incl. SRUs for cosmic and bionic), this is now unblocked."
1815022,2019-02-21 10:23:06 UTC,"(xnox, note to self, kernel ticket is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814892 )"
1815022,2019-02-12 13:09:41 UTC,"------- Comment From <email address hidden> 2019-02-12 08:01 EDT-------
This git commit will seamless apply also to 2.3.0 and 2.6.0 for Bionic and Cosmic
https://github.com/ibm-s390-tools/s390-tools/commit/20145b6d06debd47944bff0a471d17e5eba07010"
1815022,2019-05-23 08:44:47 UTC,"Hello bugproxy, or anyone else affected,"
1815026,2019-02-16 21:39:04 UTC,"Open ""CNB KALKA.act"" file with a text editor.
At the first lines, look for the entry RouteID(....) which will indicate to you the required route for this activity."
1815026,2019-09-10 14:18:13 UTC,"Since the testing version x1. 3.1-13 (Bug #1812334), Open Rails does his crosscheck between the activity and the current route."
1815030,2019-02-19 16:00:40 UTC,+1 on this suggestion. get_linux_distro should be extended to support freebsd.
1815030,2019-11-26 03:19:38 UTC,Upstream commit landed https://github.com/canonical/cloud-init/commit/2a135c4a421af47f5bd511e89e385a72f62bde33
1815030,2019-12-18 17:55:22 UTC,"This bug is believed to be fixed in cloud-init in version 19.4. If this is still a problem for you, please make a comment and set the state back to New"
1815033,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1815033,2019-03-15 23:37:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1815033,2019-02-07 12:48:39 UTC,Patch was posted in the mailing-list for the SRU process: https://lists.ubuntu.com/archives/kernel-team/2019-February/098380.html
1815033,2019-03-27 17:35:08 UTC,"Kernel was validated by the user that reported the issue - ran for more than 72h
with no problems."
1815036,2020-08-07 23:05:35 UTC,1.5 years on this is still broken: connectivity-check.ubuntu.com has no AAAA record.
1815036,2020-11-15 06:03:37 UTC,As of now connectivity-check.ubuntu.com has still no AAAA record and... it causes no IPv6 problem on Ubuntu 20.04. I doubt it ever did.
1815036,2019-02-07 13:00:30 UTC,"Thank you for your bug report, that's not a network-manager issue but indeed that's a problem on the Ubuntu infrastructure side which I'm going to report"
1815039,2019-04-23 23:57:33 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1815039,2019-06-23 04:19:18 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1815041,2019-02-21 09:02:48 UTC,+1 can reproduce this bug 100%. Disabling Enigmail allows Thunderbird to compose messages again with global menus.
1815043,2019-03-11 12:44:09 UTC,I observed the same issue. The 'nova' tag heading the entire common-playbooks/nova.yml playbook certainly prevents the execution of 'nova-config' related tasks in nova role.
1815043,2020-03-12 00:16:51 UTC,"This is most certainly broken in the Rocky release, and seems to stem from Ansible's behavior around ""forwarding"" tags through the ""include"" mechanism used in the common playbooks. Right now this means that all configuration subtags (nova-config, nova-keys, neutron-config, etc) for roles invoked via the common playbooks are non-functional, which is a fairly significant regression. How can I help move this bug forward toward a fix?"
1815046,2019-10-03 10:38:41 UTC,"I am having the same problem. It is not just the letter ""e"" with an accent. I realized that any special character typed in automatically logs me out."
1815047,2019-02-13 17:17:16 UTC,Sorry I guess this is the wrong place for this bug. Uppon more investigation it seems that layers get downloaded from github in realtime and are not present on any package.
1815048,2019-02-12 14:18:26 UTC,Example logs:- http://logs.openstack.org/85/635785/5/check/tripleo-ci-centos-7-undercloud-containers/edefdaa/job-output.txt.gz
1815048,2019-02-12 14:16:02 UTC,"It was not just ovb, non-ovb jobs are also affected."
1815048,2019-02-11 16:14:21 UTC,fixed in https://review.openstack.org/#/c/635510/
1815052,2019-02-11 07:09:29 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/443058 is this related to this question?
1815052,2019-02-11 09:23:54 UTC,"I read the manual again, we did step ""5.2.2. Installation and Configuration of IUCV service in zLinux"", but did not do steps 5.2.3 and 5.2.4 because we thought it is just an image capture and deploy. Are 5.2.3 and 5.2.4 necessary for a good deployment? (we will not use cloud-init)"
1815052,2019-02-11 09:44:49 UTC,"yes,  zvmguestconfigure is needed and"
1815052,2019-02-11 10:01:59 UTC,"Ok, we will install zvmguestconfigure."
1815052,2019-02-12 02:25:27 UTC,"ok, I think if you provide more API usage including zvmsdk logs etc will be helpful for us to know the
solution we might find or workaround etc..."
1815052,2019-02-14 16:07:42 UTC,"We tried some deployment:
1: SUSE 12.SP3 on 1 disk, the 100 (EXT3). This works; capture and deploy works on new guest.
2: SUSE 12.SP3 on 1 disk but with BTFRS. This leads to 2 partitions in SUSE12 because of /boot/zipl is not allowed on BTFRS and it makes this partition EXT3. Capture of the disk is not working now because he will only capture the boot partition, the other part is nowhere included. So deployment of new guest is not possible now.
3: SUSE 12.SP3 on 2 disks. This  was the bug described. This doesn't work also."
1815052,2019-02-14 16:19:29 UTC,Deployment of 200 disk without /boot/zipl
1815055,2019-03-20 21:15:15 UTC,There may be info about the DHCP response in /run/systemd/netif/leases/<ifindex>
1815055,2019-03-20 18:07:18 UTC,I'm sorry you've had issues with netplan so far.
1815055,2019-02-07 14:50:35 UTC,"found the docs for disabling and going back to /etc/network/interfaces in that file. is there a way to vote for not having this enabled by default while it's still so buggy? looking at the bug reports here, it looks like it doesn't really handle a fraction of what the old ifupdown stuff does yet."
1815055,2019-03-20 20:42:33 UTC,"These domains are provided by a DHCP server I don't have access to for our corporate VPN, unforunately. I'll try and get a packet capture of the DHCP protocol traffic when I connect and pick out what's happening, when I get a chance."
1815056,2019-02-07 19:42:49 UTC,Thank you for your bug report. When do you get that error? What location do you have configured to store the backup in the preferences?
1815056,2019-02-08 07:14:28 UTC,I get the error when the backup is running. I have configured the home directory for backup. It is on the local drive of the machine.
1815056,2019-02-08 09:25:09 UTC,Can you start 'DEJA_DUP_DEBUG=1 deja-dup --backup' and see if that triggers the prompt and what is written in the log at this time?
1815056,2019-02-08 09:43:47 UTC,"Yes, the prompt is there. I click on Cancel and then nothing further was written to the console. The last lines are these:
DUPLICITY: INFO 10 20190108T091631Z 'home/waschk/snap/picard/3/.local/share/mime/x-content' dir
DUPLICITY: . Tue Jan  8 10:16:31 2019 home/waschk/snap/picard/3/.local/share/mime/x-content"
1815056,2019-12-10 08:05:32 UTC,"I forgot to add, that XDG_CACHE_HOME was redirected in this centrally managed system to /tmp/.xdgcache-$USER, maybe that is of relevance?"
1815056,2019-12-10 23:52:32 UTC,Ahh...  yes. Deja Dup just checks to see if anything is outside your home folder and then prompts if so.
1815060,2020-05-31 17:24:53 UTC,"For those interested in 18.04, the file to replace is:"
1815060,2019-08-20 05:08:11 UTC,In meld (3.18.2-1) the bug is solved
1815060,2019-03-28 11:31:57 UTC,"Traceback (most recent call last):
  File ""/usr/lib/python3/dist-packages/meld/filediff.py"", line 1559, in file_saved_cb
    self.on_delete_event()
  File ""/usr/lib/python3/dist-packages/meld/filediff.py"", line 842, in on_delete_event
    del self._cached_match
AttributeError: _cached_match"
1815060,2019-03-28 11:29:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815060,2019-08-09 13:54:06 UTC,Probably duplicate of https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1768369
1815063,2019-02-08 20:44:33 UTC,steps to reproduce
1815065,2020-04-30 02:52:44 UTC,Can we merge this info bug 1802614 ?
1815065,2020-09-05 22:04:32 UTC,"This bug has been open for over a year, and evidently did not stop gnome-remote-desktop 0.1.7-1 from reaching the release pocket in eoan and later, for whatever reason.  Is there really a reason to keep this open?  I'd rather we not leave this package lingering in -proposed indefinitely."
1815065,2020-09-22 10:57:25 UTC,It's still right. I'm going to remove 0.1.7-1 from groovy now. We could remove g-r-d from the archive altogether if that's required for some reason. Personally I like it as a reminder to bring it back (there's a link to this issue) when we can.
1815065,2021-02-01 15:32:51 UTC,Since this will be finally resolved through bug 1802614 let us mark it as a dup now to have one less to forget to close.
1815066,2019-02-08 09:19:58 UTC,"it's probably handled by xfce, like it is on every other desktop"
1815066,2019-02-08 10:24:53 UTC,Similar report: bug 1716805
1815066,2019-02-15 12:45:21 UTC,"#2 Thank you, I'll give it a shot."
1815082,2020-04-18 13:01:01 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/635577"
1815082,2019-07-29 14:59:31 UTC,"Hi,"
1815082,2019-02-07 17:13:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/635577"
1815082,2019-10-22 14:29:14 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/635577
Reason: I'm not actively working on this."
1815083,2019-09-19 12:00:36 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1815083,2019-09-19 13:00:24 UTC,"Sorry, it hasn't seen any activity because it was triaged and then never worked on.  There's not much I can do to move this forward but wait for someone to resolve it."
1815083,2020-03-31 09:19:09 UTC,"This is now fixed in MAAS 2.7.0. There's no longer an edit button on the overview page. Instead there's a normal link that takes you to the configuration page, where you can edit the tags, if you want to."
1815084,2019-09-19 14:59:13 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1815084,2019-09-19 15:37:12 UTC,This has not seen any activity in the last 6 months because it was triaged and then forgotten.
1815089,2019-03-13 14:20:05 UTC,The / usr / lib / tracker / tracker-extract is using almost 100% CPU resources see attached image
1815089,2019-02-08 13:28:30 UTC,"Hi, Sebastien Bacher"
1815089,2019-06-15 04:17:38 UTC,[Expired for tracker (Ubuntu) because there has been no activity for 60 days.]
1815089,2019-02-07 23:31:49 UTC,The Ubuntu version is this:
1815089,2019-02-07 19:40:32 UTC,Thank you for your bug report. On what Ubuntu serie are you? Could you add your journalctl log to the bug?
1815089,2019-02-08 12:09:50 UTC,"It could be https://gitlab.gnome.org/GNOME/tracker/merge_requests/35 , does 'tracker reset --hard' resolves the issue?"
1815094,2019-02-07 18:04:55 UTC,"This seems to be caused by bool and gboolean incompatibility, but it is not only build error..."
1815097,2019-10-31 02:57:51 UTC,2.6.7 release never went out. This fix was instead released in 2.6.8 - re-targeting this report.
1815097,2019-08-28 21:28:00 UTC,This has been updated in 2.6 and now provides better error messaging and hints for using outdated series. Marking this as fix-released.
1815097,2019-02-11 19:00:03 UTC,"We're working to define the full UX around unsupported series with the charmstore API teams as well as Juju. We agree that Juju should ERROR on deploy, however it should also allow you to override with the existing `deploy --force` command in cases of testing upgrade paths and such."
1815097,2019-02-11 18:14:53 UTC,"TBH, I'm not sure how much better Juju could handle it, though, since it won't know until the point it queries simplestreams what series are supported.  Maybe the client or controller could do a preliminary query to be able to fail fast."
1815097,2019-02-07 17:35:38 UTC,Probably https://github.com/juju-solutions/charm-mysql/issues
1815097,2019-02-07 17:23:43 UTC,I think I've filed this with the wrong project. Where would be a more appropriate place to file this?
1815097,2019-02-11 18:12:06 UTC,"Actually, while I agree that the mysql charm should be updated to correct the series, I think this issue as written would be better placed on the Juju project, as it would involve the Juju CLI or agent handling the request better."
1815099,2019-04-23 23:57:23 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1815099,2019-06-23 04:19:17 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1815100,2019-02-08 12:32:12 UTC,"Thanks, I've updated the description accordingly."
1815100,2019-02-08 08:36:18 UTC,"Hi Harald,
this would be a backport of [1][2] which I'm fine with in general.
But there are few constraints we need to resolve first - and I get the feeling you are more acquainted binfmt than I am - so I'd ask you to help me a bit."
1815100,2019-02-08 08:36:54 UTC,"FYI - fix is in 2.12 in Cosmic and later, setting tasks accordingly"
1815101,2019-11-19 16:42:33 UTC,"(k)rafaeldtinoco@kcluster01:~$ dpkg -l | grep ""ii  systemd ""
ii  systemd    243-3ubuntu1    amd64    system and service manager"
1815101,2019-11-19 16:56:03 UTC,Flagging this as wont fix as heartbeat is already being kept just for historical reasons (and systemd-networkd can workaround that by the fix we're backporting to it: KeepConfiguration .service file stanza).
1815101,2020-02-11 07:19:50 UTC,"Hi all,"
1815101,2019-11-25 10:55:23 UTC,This bug was fixed in the package systemd - 242-7ubuntu3.2
1815101,2019-11-25 10:55:28 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815101,2020-01-14 19:54:06 UTC,"as disco reaches EOL next week, marking this as wontfix for disco."
1815101,2020-02-07 14:06:31 UTC,Can we backport the fixes to Bionic?
1815101,2020-02-13 22:26:43 UTC,"Balint, based on your input..."
1815101,2019-11-07 21:45:07 UTC,"All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1815101,2020-05-12 13:35:28 UTC,"FYI I stumbled on this problem after a system update (which broke production!) and collected data in a troubleshooting session and documented this here https://www.claudiokuenzler.com/blog/959/keepalived-virtual-ip-addresses-gone-lost-after-systemd-update. Once I found out the restart of systemd-networkd causes the keepalived vips to be gone, I finally came across this bug."
1815101,2020-05-14 14:19:51 UTC,"@napsty: the ""workaround"" (from your blog) is actually to use:"
1815101,2020-05-14 14:28:28 UTC,TL;DR TODO SUMMARY:
1815101,2020-09-24 17:45:55 UTC,Ubuntu HA wise:
1815101,2020-10-06 15:48:45 UTC,I have a first iteration of a package:
1815101,2020-10-06 15:49:20 UTC,The above test package has been made for 'systemd' in bionic ^
1815101,2021-02-23 11:55:19 UTC,i'm marking this as wont-fix for xenial.
1815101,2021-02-24 12:40:41 UTC,"For the people on Focal that want to use netplan and keepalived together: you can just put in an override for the network unit file, to keep systemd-networkd from touching your interface!"
1815101,2020-05-08 16:34:47 UTC,Removing charm-keepalived since I believe no changes are needed there. It should pick up fixes once they are available on apt archives.
1815101,2019-11-07 13:30:12 UTC,"Hello Leroy, or anyone else affected,"
1815101,2020-11-19 09:26:30 UTC,"Dear Eric Desrochers,
  I add the PPA into my ubuntu 18.04 corosync/pacemaker service node.
Then I upgrade the following libnss-systemd libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev package."
1815101,2019-10-10 19:23:58 UTC,(k)rafaeldtinoco@kcluster01:~$ sudo vi /etc/systemd/network/10-netplan-eth3.network
1815101,2019-02-07 18:24:57 UTC,Kept a task for keepalived (Incomplete) in case it turns out there's something we can do there.
1815101,2019-02-07 23:37:53 UTC,I am trying ifupdown.  Do I need to do anythnig else or is what I've done adequate?
1815101,2019-03-07 22:09:12 UTC,"Newer keepalived (> 2.0.x) addresses the systemd-networkd behavior.  From keepalived 2.0.0 release notes: ""Transition to backup state if a VIP or eVIP is removed When we next transition to master the addresses will be restored.  If nopreempt is not set, that will be almost immediately."""
1815101,2019-03-07 23:19:12 UTC,"I note this bug is marked Incomplete meaning that information is missing, what else is needed?"
1815101,2019-03-08 06:26:03 UTC,Might I ask - how much is this bug related or a dup to bug 1819074?
1815101,2019-03-11 18:37:07 UTC,Seems a dupe to me.
1815101,2019-05-08 04:14:41 UTC,"If I understand the keepalived > 2.0.x behavior referred to by cdmiller above (see 2019-03-07 comment) that is not the appropriate response to the problem.  Granted, it mitigates the consequences butr doesn't address the underlying issue. A systemd-source issue should not cause keepalived failover since failover is designed to address issues of system or hardware failure, not the bad behavior of other system software.  systemd needs to be made to cooperate with other software rather than assuming it is the only authority on the system."
1815101,2019-05-09 11:01:21 UTC,"It looks like there is some clear and actionable work in keepalived here (even if as a workaround and the real fix ends up being in systemd), so I'm marking it as Triaged."
1815101,2019-02-07 18:18:03 UTC,"This isn't netplan, it's systemd-networkd. Netplan only writes configuration for the chosen renderer (in this case, systemd-networkd)."
1815101,2019-08-21 14:28:00 UTC,For reference: https://github.com/systemd/systemd/pull/12511
1815101,2019-09-13 14:44:41 UTC,The following 3 bugs:
1815101,2019-09-13 14:57:02 UTC,"Based on comment #12, and other comments from other duplicate cases, I'll summarize here in a better (and consolidated way) how to reproduce the issue, how to mitigate it using the dummy workaround, and how to fix it (with the backports/merge requests). At the end I might provide a PPA asking for feedback."
1815101,2019-09-25 13:23:50 UTC,"Alright,"
1815101,2019-09-26 09:15:32 UTC,"The commits bellow implement support to ""keep configuration"":"
1815101,2019-09-26 09:20:13 UTC,"If you are lazy to look for these commits, feel free to use these links
https://github.com/systemd/systemd/commit/7da377ef16a2112a673247b39041a180b07e973a
https://github.com/systemd/systemd/commit/95355a281c06c5970b7355c38b066910c3be4958
https://github.com/systemd/systemd/commit/db51778f85cb076e9ed1fe7f7e29cc740365c245
https://github.com/systemd/systemd/commit/c98d78d32abba6aadbe89eece7acf0742f59047c
https://github.com/systemd/systemd/commit/1e498853a39b46155cb89b5c9e74ecb27aaba3ed"
1815101,2019-09-28 14:20:34 UTC,"Thanks Rafael/Christian,"
1815101,2019-10-09 21:35:25 UTC,"@ed,"
1815101,2019-10-10 19:23:34 UTC,Test Case:
1815101,2019-08-27 00:51:54 UTC,"The aforementioned link shows there's been work towards a fix in systemd.  Can't say if that suggests what can be done to improve keepalived, but I've tagged this ""server-next"" to get it on the Ubuntu SErver Team's high priority list, as per Robie's earlier comment."
1815101,2019-10-11 11:09:00 UTC,Eoan SRU:
1815104,2019-02-12 14:58:00 UTC,+1 on both the ability to move buckets to another account and to have org owned buckets.
1815104,2019-05-28 13:15:20 UTC,Hello.  I had posted a message to the dev list with some functions I had created to move or copy bib record and copy buckets.  I had not noticed this ticket.  Here is a link to that message:
1815107,2019-02-13 17:17:41 UTC,Sorry I guess this is the wrong place for this bug. Uppon more investigation it seems that layers get downloaded from github in realtime and are not present on any package.
1815110,2019-12-03 10:50:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815110,2019-12-03 14:27:54 UTC,v0.4.0 cmake does not create and install a pkgconfig/libglog.pc file
1815118,2020-08-12 04:52:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815119,2019-02-07 21:46:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815119,2019-10-17 19:32:26 UTC,The font fix is backported to OpenJDK 11.0.6 with the following Backport Bug Report:
1815119,2019-10-17 19:34:59 UTC,"Fix committed upstream in OpenJDK 11.0.6 to be released January 14, 2020."
1815119,2020-03-22 04:52:11 UTC,"2020-01-15: OpenJDK 11.0.6 is available on Ubuntu 18.04 LTS with the fix.
2020-01-17: OpenJDK 8 Update 242 is available on Ubuntu 16.04 LTS and Ubuntu 18.04 LTS with the fix."
1815127,2019-06-20 08:12:18 UTC,No problem here parsing and displaying the line
1815127,2019-04-09 12:11:02 UTC,Could you perhaps report it upstream as well on https://gitlab.gnome.org/GNOME/evolution/issues/ ?
1815127,2019-03-08 22:28:04 UTC,My apologies - I no longer have the example email.
1815127,2019-02-24 20:59:43 UTC,"Can you please share/attach a public testcase? ""File > Save as mbox..."", then edit that text file with a text editor to remove/alter any confidential information. Thanks!"
1815127,2019-03-08 22:30:15 UTC,It seems that the parser in evolution fails to parse:
1815131,2019-03-04 09:02:25 UTC,"also when the package only has some binaries on that architectures. picard-tools/i386 now triggered by openjdk-* fails on i386, but the packages are now built on amd64 only, the -doc package being the only architecture independent package."
1815134,2020-09-08 20:57:55 UTC,This won't be a significant issue with config-download
1815140,2020-02-18 23:45:07 UTC,"Unfortunately the repo for repcached looks to be unmaintained, and there's no supported package for this software.  In light of that, I'll mark this as wontfix."
1815146,2019-10-31 03:26:21 UTC,Removing from a milestone as this work will not be done in 2.6 series.
1815148,2019-03-05 18:35:44 UTC,Just ran the latest update/upgrade w/ new kernel and rebooted . . . flickering bottom panel problem remains . . . .
1815148,2019-02-12 18:35:31 UTC,"Problem continued, even after I did a ""panel reset"" to the panel . . . .  Tried to flip up an ""apport-collect 1815148"" to add the data, but apport ""failed to find a browser"" even though Firefox was launched . . . and I was logged in to LP . . . no report generated--""failed"" to report . . . ???"
1815148,2019-02-07 23:50:47 UTC,Noticed that the problem was happening while using the Terminal as well. As an update/upgrade was running the panel was flickering . . .
1815148,2019-02-08 00:21:51 UTC,"Oops . . . seems like possibly after the problem showed in the Terminal for the latest upgrade . . . problem may have resolved??? I'll ""monitor"" the situation . . . didn't do the restart yet on the upgrade . . . possibly might return??? But, for now . . . not happening . . . after some weeks of it being there . . . this recent upgrade may have fixed it???"
1815148,2019-02-08 00:32:40 UTC,"Sorry . . . nope, problem still happening . . . as type this post the panel flickers . . . same as before . . . ."
1815153,2019-02-08 14:04:23 UTC,"I'm not sure but another case this could affect is rebuilding with a new image, in which case the API sets the new image on the request spec:"
1815153,2019-02-08 14:07:32 UTC,"Since I found this only in a functional test, I think we probably want functional tests for everywhere this could be a problem, which I think is:"
1815153,2019-02-08 14:36:58 UTC,I made this change to try and test scenario #4 but the test still passed which was unexpected:
1815153,2019-02-08 14:40:19 UTC,"OK I see why rebuild + new image + old request spec doesn't blow up on save() in heal_reqspec_is_bfv, the RequestSpec.save() routine doesn't rely on the id:"
1815153,2019-02-12 06:43:33 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636271"
1815153,2019-03-05 23:58:21 UTC,"Reviewed:  https://review.openstack.org/636271
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=67d5970445818f2f245cf1b6d9d46c36fb220f04
Submitter: Zuul
Branch:    master"
1815153,2019-03-06 05:43:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641200"
1815153,2019-03-14 02:14:32 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/643215"
1815153,2019-03-15 22:32:22 UTC,"Reviewed:  https://review.openstack.org/643215
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=02d6146e4d8b5af2aae0d046a58598aa0102f53d
Submitter: Zuul
Branch:    stable/rocky"
1815153,2019-03-22 03:43:47 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1815153,2019-03-24 23:39:02 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1815161,2020-08-31 16:01:37 UTC,"Sorry, ""it doesn't work"" is not a bug report I can help with."
1815163,2019-02-08 07:19:37 UTC,"I did a ""Install (entire disk) in Lubuntu Desktop amd64 in Bionic Daily""
on a virtual-machine (virtual box on fedora 29 host) and window borders were evident at all times on this install (same downloaded ISO mounted from nfs share)"
1815163,2019-02-08 06:05:15 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1815163,2019-02-08 05:46:54 UTC,I listed this is calamares-settings-ubuntu from searches online (mainly lubuntu.me).  it wasn't used by Lubuntu until 18.10 so it should be Ubiquity I now believe...
1815167,2019-06-12 01:54:23 UTC,This bug has been fixed in https://review.opendev.org/#/c/638475/ .
1815171,2019-02-12 01:20:55 UTC,"On 8/2/19 04:39, Mark Shuttleworth wrote:

> Public bug reported:
>
> I have a bug in my snapcraft plugin which causes it to crash. Snapcraft
> shows me this:
>
> Sorry, an error occurred in Snapcraft.
> We would appreciate it if you anonymously reported this issue.
> No other data than the traceback ('/tmp/tmpw4id89ag/trace.txt') and the version of snapcraft in use will be sent.
> Would you like to send this error data? (Yes/No/Always) [no]:
>
> That's nice, but it would be even better if it actually showed me the
> traceback. Perhaps like this:
"
1815171,2019-02-14 02:26:30 UTC,"Aha, nice to know you're a few steps ahead :)"
1815172,2019-03-05 12:12:21 UTC,please test the new mesa on bionic/cosmic
1815172,2019-03-12 10:37:27 UTC,"Alkis, please test 18.2.8 for bionic and if possible, cosmic"
1815172,2019-03-12 11:50:52 UTC,"actually, bionic was already tested earlier, and the tested fix is a one-line change to mesa which is still the same on 18.2.8 so marking bionic verified.. and also cosmic since it's the exact same version there, and cosmic kernel was also tested to be buggy"
1815172,2019-03-13 13:12:05 UTC,bionic was already fixed earlier by 18.2.2-0ubuntu1~18.04.2 in time for 18.04.2 release
1815172,2019-03-13 14:29:49 UTC,"Exactly. I did the ""verification-done-bionic"" step for 18.2.2 in comment #12 above; and unfortunately I don't have an affected school nearby, where I could test 18.2.8 in cosmic, and installing cosmic in a remote school would be hard."
1815172,2019-03-20 00:25:32 UTC,This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.04.2
1815172,2019-03-20 00:35:15 UTC,This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.10.2
1815172,2019-08-05 21:38:29 UTC,"Reopening mesa for bionic, because the revert needs to be dropped once the kernel is fixed, otherwise Ice Lake is broken because it needs softpin for the DRI driver to work."
1815172,2019-08-06 14:29:51 UTC,"could you please test with ppa:canonical-hwe-team/ppa which has a new 4.15 kernel with a couple of backports that should fix this, and it also comes with mesa that dropped the revert"
1815172,2019-08-06 18:34:36 UTC,"Nevermind, I used a thinkpad t470s plus an external ssd which I could wipe out and install ubuntu mate 18.04 32bit on it. To reproduce I enabled the HWE ppa and upgraded mesa, then installed linux-generic and booted 4.15.0-55. It ended up with a mostly blank screen but keyboard had no effect other than the power button."
1815172,2019-03-04 09:02:47 UTC,disco has 4.19.x
1815172,2019-08-29 10:06:22 UTC,"Hello Alkis, or anyone else affected,"
1815172,2019-08-29 23:31:27 UTC,"All autopkgtests for the newly accepted mesa (19.0.8-0ubuntu0~18.04.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1815172,2019-09-02 12:26:03 UTC,This bug was fixed in the package linux - 4.15.0-60.67
1815172,2019-09-03 12:53:12 UTC,"There's a follow up fix for bionic/linux which needs to be applied:
https://lists.ubuntu.com/archives/kernel-team/2019-August/103175.html"
1815172,2019-09-03 13:16:50 UTC,This bug was fixed in the package linux - 4.15.0-60.67
1815172,2019-09-16 07:10:53 UTC,"Alkis, could you double-check if your setup is fine now with the current 4.15 kernel and mesa from proposed? Mine is, but I'd rather not rely on that test alone."
1815172,2019-09-16 14:26:44 UTC,"Hi Timo,"
1815172,2019-09-19 15:25:24 UTC,"I asked another user to test this on a duplicate bug (from a newer mesa backport, where the original revert was missing), and it's indeed fixed now"
1815172,2019-09-23 09:31:12 UTC,This bug was fixed in the package mesa - 19.0.8-0ubuntu0~18.04.2
1815172,2019-09-30 21:48:23 UTC,This bug was fixed in the package linux - 4.15.0-65.74
1815172,2019-08-22 16:15:06 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1815172,2019-02-14 12:19:36 UTC,"Just correcting a wrong comment (#2) I made:

> It happens on both 32bit and 64bit installations.
"
1815172,2019-02-08 08:59:14 UTC,"Hello Alkis, thank you for the report.
Do you know, what kernel version was used on those machines? It might be helpful also."
1815172,2019-02-08 21:44:57 UTC,"The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815172,2019-02-08 08:04:22 UTC,Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.
1815172,2019-02-08 09:04:12 UTC,"Thank you Denis,"
1815172,2019-02-09 18:01:27 UTC,"Hello Alkis, or anyone else affected,"
1815172,2019-02-08 09:21:41 UTC,Can you please:
1815172,2019-02-08 09:32:05 UTC,"I used ""/sys/module"" instead of ""/sys/modules"":"
1815172,2019-02-08 09:33:24 UTC,"Sorry, I forgot the >"
1815172,2019-02-08 09:48:56 UTC,"(In reply to Chris Wilson from comment #4)

> Hopefully we remembered to tag the EINVAL.
"
1815172,2019-02-08 12:40:27 UTC,"I just tried with 4.18.0-14-generic, the same issue happens there as well."
1815172,2019-02-08 13:20:57 UTC,one theory is that this is related to legacy bios boot
1815172,2019-02-08 13:53:21 UTC,"Hello, Alkis.
Could you, please, try to use a kernel not less than v4.19.3?"
1815172,2019-02-08 14:31:31 UTC,"Hello Sergii,"
1815172,2019-02-08 09:10:38 UTC,"The Ubuntu folks uploaded 18.3.3 in their ppa:ubuntu-x-swat/updates PPA for me to test with, and it has the exact same issue."
1815172,2019-02-08 15:19:30 UTC,I don't know the software stacks involved:
1815172,2019-02-08 15:32:45 UTC,"Most likely mesa were broken with commit:
commit a363bb2cd0e2a141f2c60be005009703bffcbe4e
Author: Kenneth Graunke <email address hidden>
Date:   Tue Apr 10 01:18:25 2018 -0700"
1815172,2019-02-08 16:20:39 UTC,"I tried a small kernel bisection using the ubuntu kernel binaries,
4.19.2-041902=fails,
4.19.3-041903=works"
1815172,2019-02-08 17:10:25 UTC,"this is caused by enabling softpin in mesa, which is supported in kernel 4.5 and up but is still somewhat buggy as seen here.. we need these commits backported to the kernel:"
1815172,2019-02-08 17:18:00 UTC,"4.15 is EOL upstream, but Canonical does pull patches from stable to the distro kernel in 18.04, I'm not sure why these never got in.. probably didn't apply cleanly."
1815172,2019-02-08 17:40:53 UTC,"FWIW, I am not able to reproduce this issue on Arch Linux with Mesa 18.3.3 and kernel 4.18.16."
1815172,2019-02-08 18:40:04 UTC,"Hello Alkis, or anyone else affected,"
1815172,2019-02-08 18:41:57 UTC,"Hello Alkis, or anyone else affected,"
1815172,2019-02-08 21:08:59 UTC,I verify that the bionic-proposed package addresses the issue.
1815172,2019-02-08 21:44:49 UTC,This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.2
1815172,2019-02-08 15:04:04 UTC,< I tried with 4.20.7 and it appears to work fine! Thanks!
1815173,2019-12-22 04:17:21 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1815173,2019-12-22 04:17:17 UTC,[Expired for snapd because there has been no activity for 60 days.]
1815173,2019-10-22 07:23:47 UTC,"Is is still an issue? Given that this report is very old I suspect the problem was resolved, therefore I'm setting to 'incomplete'. Please respond if you think it is still the case."
1815173,2019-10-17 11:44:41 UTC,Looking at the log:
1815173,2019-02-08 11:11:19 UTC,Is this lp:1778219?
1815173,2019-02-08 08:34:56 UTC,Note: This seems to have been an intermittent problem for the past year: https://askubuntu.com/questions/1037431/receiving-the-error-snapd-snap-repair-service-is-a-disabled-or-a-static-unit-n
1815173,2019-02-08 12:25:49 UTC,I think this is also causing autopkgtest-build-lxd to fail:
1815176,2019-02-08 10:00:06 UTC,This change was made by a bot.
1815177,2019-02-08 15:09:57 UTC,"On 2/8/19 1:48 AM, Ralph Lange wrote:

> Public bug reported:
>
> Using EPICS 7.0.2 on a Linux box with a system clock that was set to the
> Posix epoch (NULL) by an irresponsible time synchronization daemon, use
> of a simple CA client sends it into a fast infinite loop printing
"
1815178,2019-02-08 10:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1815178,2019-05-15 22:41:40 UTC,"Hi Louis,"
1815178,2019-08-05 11:02:22 UTC,"Hi, this bug has not been replied to for a while. I will mark it closed next week if it has not been updated."
1815178,2019-09-24 15:22:30 UTC,"This bug has been dormant for a while with no update. I'm marking it as won't fix. If this is still and issue, please re-open this bug."
1815183,2019-09-13 16:05:26 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1815183,2019-09-13 10:15:27 UTC,"Reviewed:  https://review.opendev.org/676373
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=7e7f1cb92b34b62b235c52e45fea187e466f40cb
Submitter: Zuul
Branch:    master"
1815183,2019-08-22 08:34:45 UTC,This issue was fixed in the openstack/mistral-lib 1.2.0 release.
1815183,2019-08-14 09:04:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676373"
1815183,2019-08-07 10:37:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675086"
1815183,2019-06-03 15:44:04 UTC,"> I'm in favour of moving all utils actually into mistral-lib.
"
1815183,2019-05-29 09:04:10 UTC,You're correct. They are not needed in mistral repo anymore. It's just a left over from the refactoring around mistral-lib. I'm in favour of moving all utils actually into mistral-lib.
1815183,2019-08-13 07:48:52 UTC,"Reviewed:  https://review.opendev.org/675086
Committed: https://git.openstack.org/cgit/openstack/mistral-lib/commit/?id=070080bd1bc4c4742f6a98370b7ce1616084eded
Submitter: Zuul
Branch:    master"
1815183,2019-05-29 09:05:14 UTC,I assigned it to T-2 but if you can't take care of that please either move it to a later time or we can reassign it to someone else.
1815190,2019-05-29 09:06:24 UTC,"Hi, what DB are you using?"
1815190,2019-06-24 07:58:00 UTC,"Hi, it is PostgreSQL 10.8"
1815193,2019-07-10 19:46:26 UTC,"Hi, thanks for taking the time to report this bug.  Sorry its taken woefully long for me to see it.
I'm going to set this as 'opinion'.  It is valid shell as it is:"
1815194,2019-02-08 13:06:24 UTC,subscribed field-medium
1815194,2019-02-09 01:40:31 UTC,"This bug report really needs more info, especially since it can't be reproduced easily. Knowing which charm versions are affected would increase the chances of addressing this bug."
1815194,2019-02-18 09:28:37 UTC,"Hi Simon,"
1815194,2019-08-19 16:18:50 UTC,"I was able to reproduce the issue, while using the following revisions, and using a bundle based on the original bug reporter's example."
1815196,2019-03-28 07:49:15 UTC,"Reviewed:  https://review.openstack.org/643701
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=b96f7120c44b6c8bc7b804b72f9a25a7c55d005e
Submitter: Zuul
Branch:    master"
1815196,2019-04-15 15:35:47 UTC,https://review.openstack.org/#/c/649083/
1815196,2019-05-13 17:46:08 UTC,So my concern is similar to the problem for rabbitmq-server in LP#1818260. If the cluster is acting on its own to remove units independent of the charm. During deploy time when resources are scarce we are likely to hit false positives and have units removed.
1815197,2019-02-08 19:51:41 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1815197,2019-02-08 19:52:02 UTC,"Hello, it looks like there's no EFI partition but an EFI installed was tried. I hope this helps."
1815199,2020-03-29 23:55:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815201,2019-06-18 23:26:18 UTC,This bug was fixed in the package mdadm - 4.1-2ubuntu3
1815201,2020-07-02 19:28:15 UTC,"Ubuntu 19.04 reached end of life on January 23, 2020.  I am therefore marking this bug 'wontfix' for that release."
1815202,2019-02-15 15:11:41 UTC,I have also tried this just now
1815202,2019-02-14 15:09:10 UTC,Clone this repo for a real world example:
1815202,2019-02-11 15:07:56 UTC,I cannot seem to reproduce your issue. Mind adding more information or trying again? Here's what I tried out:
1815204,2019-06-21 15:26:15 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1815204,2019-02-14 10:08:26 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/636891"
1815204,2019-02-19 14:27:12 UTC,"Reviewed:  https://review.openstack.org/636891
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ded38b744037bc6bffc0b63039933b58ab5e5018
Submitter: Zuul
Branch:    stable/rocky"
1815204,2019-02-22 11:10:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/638630"
1815204,2019-02-22 17:52:43 UTC,"Reviewed:  https://review.openstack.org/638630
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a9d10fdf722990d8258abd3987b1a4f6d81e0300
Submitter: Zuul
Branch:    stable/queens"
1815204,2019-02-23 15:20:02 UTC,Fixed in master with https://review.openstack.org/#/c/635492/
1815204,2019-03-14 10:35:11 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.4.0 release.
1815204,2019-03-14 10:43:12 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.3.0 release.
1815207,2019-04-09 21:35:51 UTC,fix pushed to collab/phasefx/lp1145213-test-race-condition
1815207,2019-04-10 16:44:51 UTC,"Thanks, Jason! Picked to master."
1815208,2019-03-19 13:36:09 UTC,"If you have a fix, could you submit that?"
1815214,2019-08-09 13:40:27 UTC,Affects me too on a T480 running Manjaro
1815214,2019-08-16 12:56:12 UTC,"AFAICT, this bug report is a duplicate of bug 1763144."
1815214,2019-08-15 16:12:36 UTC,Lenovo T580 is also affected by this
1815214,2019-07-18 11:02:20 UTC,I think the solution at https://github.com/intel/dptfxtract/issues/6 can fix this issue?
1815214,2019-04-11 17:23:31 UTC,"You marked this for thermald bug.
Can you try this?
#systemctl disable thermald
reboot
then try to reproduce."
1815214,2019-05-04 16:37:31 UTC,"This is not a thermald bug.  Linux doesn't have ABI to change PL1 limit set via MMIO I/F as suggested in the link, so thermald can't us."
1815214,2019-07-18 09:59:04 UTC,Currently facing the same issue myself.
1815214,2019-02-08 16:30:08 UTC,This change was made by a bot.
1815214,2019-04-11 05:54:02 UTC,Affects my Lenovo X1 6th gen as well
1815214,2019-05-04 00:58:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815217,2019-03-20 17:58:31 UTC,"This happens as we update things often in the development release, but backporting new features takes time and needs to be done with care to not break existing things."
1815217,2019-05-20 04:17:31 UTC,[Expired for netplan because there has been no activity for 60 days.]
1815219,2019-02-12 10:01:45 UTC,It really looks like you've got some extra `askpass` configuration that we're picking up somehow. I'd like to know more :-)
1815219,2019-06-18 19:31:15 UTC,I see this as well on ubuntu 18.04.2 with snap version:
1815220,2019-02-08 20:34:13 UTC,This seems to apply to export-key as well-- the password prompt is a GUI dialog.
1815220,2019-02-12 10:00:42 UTC,can you `xwininfo` the dialog?
1815222,2019-02-20 15:12:52 UTC,This issue was caused by strict type-coercion rules (int -> float in particular) in `juju/schema`. The schema package had already been updated to support this but juju used an older dep. PR https://github.com/juju/juju/pull/9768 bumps the package dep in 2.5 and fixes this issue.
1815222,2019-03-01 08:25:03 UTC,https://github.com/juju/juju/pull/9817 merges this into develop
1815225,2019-06-21 17:54:15 UTC,Please note: This bug also applies to Ubuntu 18.04 (in addition to 14.04 as originally reported).
1815225,2019-02-10 15:05:56 UTC,"Sorry... I should have said if this is no longer an issue in later **32-bit** versions... because hot patching might must be for 64 bit versions, which wouldn't help in this case. Thanks."
1815225,2019-02-10 14:53:36 UTC,"Sorry, one last thing. If this issue is not an issue in later versions than 14.04 LTS, due to later-introduced hot patching for example (so that restarts are never required for updates), that would be considered a reasonable solution, and I would just upgrade to Version 16 or 18 as needed. Thank you."
1815225,2019-02-08 23:01:05 UTC,I remembered some additional information I should have put in the original post:
1815225,2019-02-08 18:00:06 UTC,This change was made by a bot.
1815226,2019-02-11 16:53:03 UTC,"Nagasai, I hadn't tried internal TLS in standalone. Did you add that on purpose? what did you mean to deploy?"
1815226,2019-02-11 20:53:02 UTC,"Yes, I'm trying to deploy standalone UC with TLS enabled to verify the patches I'm looking at. But after running the above command I'm hitting that issue."
1815226,2019-02-12 05:35:05 UTC,Do you need external TLS or TLS everywhere?
1815229,2019-02-08 19:05:56 UTC,Working branch user/jeffdavis/lp1815229_auth_proxy_bail_on_fail implements this proposal:
1815229,2019-05-24 19:54:45 UTC,"Hello Jeff,"
1815233,2019-02-08 21:16:14 UTC,"Hello Vitaliy, it looks like there's no EFI partition on the disk, but it was trying to do an EFI install."
1815235,2019-02-08 19:19:37 UTC,"I should have better worded the name of this bug to clearly show that I'm surfacing the _default_ display of the plugin's nickname. There is a method to name a plugin manually when adding the plugin, but for the default (included) plugins this step doesn't happen."
1815235,2019-05-06 18:52:58 UTC,@Michael
1815238,2019-03-20 13:55:02 UTC,"My thought would be the easiest(?) thing would be to add a check in the PO activation for if eg_bib_id is deleted or is null, indicate which line item is affected. Then users can go undelete the record and try to activate again."
1815238,2019-02-11 13:03:29 UTC,Related bug: https://bugs.launchpad.net/evergreen/+bug/1634244
1815239,2019-04-25 11:00:40 UTC,Testing 6.2.3.2 (released Tuesday) it seems this issue may have been subsequently resolved.
1815239,2019-06-29 04:17:30 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1815241,2019-08-20 01:34:19 UTC,"Thank you for reporting this bug. Since this was reported against a version of gimp included in a now end-of-life version of Ubuntu, please try to reproduce this bug using a more recent version of Ubuntu, and comment on this bug as to whether or not this bug still occurs."
1815241,2019-10-19 04:17:41 UTC,[Expired for gimp (Ubuntu) because there has been no activity for 60 days.]
1815243,2019-02-12 22:15:44 UTC,"Reviewed:  https://review.openstack.org/635948
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer-agent/commit/?id=058cd81d400cf443070043a55802d3e8684291b8
Submitter: Zuul
Branch:    master"
1815243,2019-02-12 18:55:27 UTC,"Reviewed:  https://review.openstack.org/635957
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=6f7c61c488f1f8d886c3579bde0c950da18f3508
Submitter: Zuul
Branch:    master"
1815243,2019-02-10 19:52:54 UTC,"Reviewed:  https://review.openstack.org/635940
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-radosgw/commit/?id=c4e5565799fa761494cce96f75e5baca10da290f
Submitter: Zuul
Branch:    master"
1815243,2019-02-10 19:52:28 UTC,"Reviewed:  https://review.openstack.org/635937
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=be74c0fd1c6ebfc4d5da1f6e583abc8047438e0c
Submitter: Zuul
Branch:    master"
1815243,2019-02-10 19:52:15 UTC,"Reviewed:  https://review.openstack.org/635945
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=5e2ed7f212686f4ef1eb19e04c41dc421fcbc593
Submitter: Zuul
Branch:    master"
1815243,2019-02-10 19:51:58 UTC,"Reviewed:  https://review.openstack.org/635942
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=f1fffb788517b829b537000b75667724cce24efc
Submitter: Zuul
Branch:    master"
1815243,2019-02-09 00:34:12 UTC,"Reviewed:  https://review.openstack.org/635962
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=0e35fadab38f4a4b1ff30a821100f8481f7491f4
Submitter: Zuul
Branch:    master"
1815243,2019-02-09 00:27:52 UTC,"Reviewed:  https://review.openstack.org/635967
Committed: https://git.openstack.org/cgit/openstack/charm-glance-simplestreams-sync/commit/?id=d597eaedbb672c68b3c730ba4c039db9e4cdeaec
Submitter: Zuul
Branch:    master"
1815243,2019-02-09 00:27:04 UTC,"Reviewed:  https://review.openstack.org/635960
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=6868b47b3e67f17009651742a84e17de3fc7f41f
Submitter: Zuul
Branch:    master"
1815243,2019-02-09 00:24:11 UTC,"Reviewed:  https://review.openstack.org/635963
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=56358d1d335bc59ad6af4fed675119ceb95a6ef9
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:36:36 UTC,"Reviewed:  https://review.openstack.org/635961
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=3ca3cd3f870fd28f29c4cee12ca456e6d76b9a8f
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:34:17 UTC,"Reviewed:  https://review.openstack.org/635956
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=2b6943ddad5d572329391d7b88ba2d5173c044d1
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:31:30 UTC,"Reviewed:  https://review.openstack.org/635959
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=3edfdfd152a106fb5a3a5a27db5b28e39655b52f
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:11:39 UTC,"Reviewed:  https://review.openstack.org/635949
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=9eb22b894914f36da8ceaa71eb243e465b6a9731
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:09:37 UTC,"Reviewed:  https://review.openstack.org/635947
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=554bf0af8eb2e6738cc078a7ae8440c61ecc0b04
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:09:04 UTC,"Reviewed:  https://review.openstack.org/635955
Committed: https://git.openstack.org/cgit/openstack/charm-hacluster/commit/?id=84ca05beb859f75268d25a986ef189fd8924ece5
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:07:18 UTC,"Reviewed:  https://review.openstack.org/635946
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=30466da23da2b962280ccbd5c2438080db77b49f
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:07:08 UTC,"Reviewed:  https://review.openstack.org/635950
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=d3cfc3ff1300175674338ebc6cafb2225e5bee59
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 23:05:07 UTC,"Reviewed:  https://review.openstack.org/635954
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=8b2c46cff7035db47af8ca344feaebd4ebac6633
Submitter: Zuul
Branch:    master"
1815243,2019-02-08 22:11:32 UTC,"Change abandoned by David Ames (<email address hidden>) on branch: master
Review: https://review.openstack.org/635968
Reason: Duplicate"
1815243,2019-02-08 21:39:15 UTC,"Reviews:
https://review.openstack.org/#/q/topic:bug/1815243+(status:open+OR+status:merged)"
1815243,2019-02-08 23:36:24 UTC,"Reviewed:  https://review.openstack.org/635958
Committed: https://git.openstack.org/cgit/openstack/charm-lxd/commit/?id=2996db663ffe78ef4754233f9ab565cc92551c9c
Submitter: Zuul
Branch:    master"
1815246,2019-06-25 12:16:35 UTC,"verified
20190622T013000Z"
1815246,2019-06-25 02:55:53 UTC,"Sorry, please ignore the last comment from me, it's a wrong paste."
1815246,2019-06-25 02:46:58 UTC,"Should have been fixed by https://review.opendev.org/664831
Please have a re-test."
1815246,2019-02-13 18:25:49 UTC,Re-opening based on Tyler's comment above. Marking as release gating until further investigation.
1815246,2019-02-11 18:59:49 UTC,"I took a quick look and it appears there is functionality to create server groups from the upstream dash, but think it may be turned off due to the policy.  If that's the case it would be a configuration issue that we need to correct, should be investigated"
1815246,2019-02-11 18:45:10 UTC,"We’re abandoning our modifications to the panels and as a result adopting the upstream server groups panels. Please refer to Stein documentation for how the new panel is suppose to work, and if there is an issue please open a LP in applicable upstream openstack project."
1815246,2019-06-21 12:29:26 UTC,Assigned to Bruce for re-assignment.
1815247,2019-02-13 20:01:39 UTC,Confirmed on EG 3.2.3.
1815247,2019-09-13 21:02:14 UTC,"I've added ""cataloging"" and ""marc"" tags so that this bug will be more visible to catalogers."
1815252,2019-02-08 23:08:20 UTC,I forgot to add that the kernel in that image (/usr/lib/kernel/org.clearlinux.*) does not have 9p support. So to compile the kernel I used the attached config
1815252,2019-02-08 23:08:42 UTC,I forgot to add that the kernel in that image (/usr/lib/kernel/org.clearlinux.*) does not have 9p support. So to compile the kernel I used the attached config
1815252,2019-04-09 20:24:09 UTC,"Damn, I just ran into this bug again! Then realized I'd already reported it.... :("
1815253,2019-02-09 03:51:22 UTC,"Hello, it looks like there's no EFI partition, but an EFI install was attempted:"
1815254,2019-10-08 14:49:10 UTC,"@thinktwo  nothing missing, the fix is entirely in systemd.  Please open a new bug and put in your steps so we can track down what's going wrong."
1815254,2019-10-08 12:30:52 UTC,"From what understand the fix in systemd was release with 18.04.3, but i still seem to hit this with cloud-init 19.2-36-g059d049c-0ubuntu2~18.04.1 on 18.04.3. Are something still missing in cloud-init to resolve this?"
1815254,2019-08-13 20:18:42 UTC,The systemd SRU has landed in Bionic and later.
1815254,2019-08-05 15:59:49 UTC,"This will require no work from cloud-init as it is a systemd related fix. Cloud-init just needs to be aware of when the existing systemd SRUs land in Bionic, Disco and Eoan"
1815254,2019-08-05 15:58:54 UTC,I have verified that Bionic and Disco work with the aforementioned SRU (and have attached logs to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835581).   Eoan SRU is not yet queued for SRU verification with a fix because an existing SRU is already in the pipeline there and needs to land first.
1815254,2019-07-15 23:50:37 UTC,This issue is resolved by the following WIP branch: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/370152
1815254,2019-07-01 20:40:05 UTC,filed a related bug against netplan for discussion about how best to express this type of configuration https://bugs.launchpad.net/netplan/+bug/1834956
1815254,2019-03-07 20:38:12 UTC,"OK, this is easily reproduced by adding a single static IP in the same subnet as the IP that comes from dhcp'ing on the interface."
1815254,2019-02-09 00:14:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815254,2019-02-08 23:38:47 UTC,ip addr show output:
1815254,2019-07-26 16:09:22 UTC,A systemd SRU [1] has started with the branch referenced in comment 6 included in it. It would be good to verify this actually fixes this issue and reply on the SRU bug.
1815255,2019-02-09 00:00:07 UTC,This change was made by a bot.
1815255,2019-02-20 10:20:38 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1815257,2020-08-29 04:17:23 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1815257,2020-06-29 17:15:36 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
1815257,2019-02-10 03:38:46 UTC,This is while running as a live CD from a USB drive.
1815260,2020-03-19 14:03:37 UTC,"Reviewed:  https://review.opendev.org/635995
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=7c8b567ba70cbc6e54d60bc4d94adcda25c36dfa
Submitter: Zuul
Branch:    master"
1815261,2020-03-27 02:35:53 UTC,I got similar issues on KVM (x86) VMs  via manual clouds of charm bundle cs:bundle/canonical-kubernetes-879
1815261,2020-03-27 11:50:33 UTC,"We do not support POWER architectures yet. Supported arches right now are x86, arm64, s390x."
1815263,2021-02-17 10:34:18 UTC,Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays?
1815271,2019-02-21 22:30:49 UTC,That would be a wishlist for upstream
1815271,2019-02-21 17:58:22 UTC,"Like what the old software centre did before Xenial, it showed a notice that the same software is already installed but with a different version (older or newer). This notice could be shown in the Details section of gnome-software, like the notice that is shown when installing an unconfined snap."
1815271,2019-02-19 19:32:08 UTC,"On 13/02/2019 1:37, Sebastien Bacher wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we cannot work on this bug because your
> description didn't include enough information. You may find it helpful
> to read ""How to report bugs effectively""
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem.
>
> We have instructions on debugging some types of problems at
> http://wiki.ubuntu.com/DebuggingProcedures.
>
> At a minimum, we need:
> 1. The specific steps or actions you took that caused you to encounter the problem.
> 2. The behavior you expected.
> 3. The behavior you actually encountered (in as much detail as possible).
"
1815271,2019-02-12 23:37:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1815271,2019-02-20 07:39:17 UTC,How do you envision it to work? Having a split screen which twice the same page on the left/right for example? What's the usecase?
1815272,2019-02-28 16:05:54 UTC,Marking as invalid as it's informational rather than a bug.  Thank you for the patch to add additional documentation to the project.
1815272,2019-02-28 17:32:36 UTC,"Reviewed:  https://review.openstack.org/636001
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=6693f08db68626e27033a66e9751952be75ce7bc
Submitter: Zuul
Branch:    master"
1815272,2019-02-28 16:02:01 UTC,See review:
1815273,2019-02-28 15:19:35 UTC,Hi Rikimaru
1815273,2019-02-28 15:21:04 UTC,"Marking as invalid as it's not something that will be fixed (i.e. nova-lxd mitaka, pike, queens works on xenial with the associated nova versions)."
1815273,2019-02-28 16:02:20 UTC,See review: https://review.openstack.org/#/c/636001/
1815273,2019-02-28 17:32:33 UTC,"Reviewed:  https://review.openstack.org/636001
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=6693f08db68626e27033a66e9751952be75ce7bc
Submitter: Zuul
Branch:    master"
1815276,2019-02-09 10:41:34 UTC,"Can you bring this up on the support forum:
https://forum.peppermintos.com
mentioning exactly what happens when you right-click a folder and select ""Rename"". Along with which Gtk theme you're using."
1815277,2019-02-11 08:23:33 UTC,I managed to fix 1 of 2 memory leaks in the attached branch: The remaining leak:
1815277,2019-09-16 08:20:58 UTC,Migrated to https://github.com/widelands/widelands/issues/3382
1815279,2019-04-15 22:31:40 UTC,Will this break portability? Juju's CLI can be run outside of Linux environments where watch(1) may not be available. Perhaps procps has been reimplemented in Go..?
1815279,2020-01-17 08:28:46 UTC,"Adding a link back to #1856527. Although that's a duplicate of this bug, it contains some good discussion about what the requested functionality could look like."
1815286,2019-05-06 20:58:23 UTC,As am I.
1815286,2019-05-17 08:02:21 UTC,"So it sounds stranger.
There may be other bugs here not just GPU related or it maybe that at some point there is some disturbance on the OpenGL machine, as you can see, even the axis arrows are not rendered :\"
1815286,2019-05-16 15:50:06 UTC,"An interesting note is that when browsing the PCB using 3D Viewer using the RayTracing option, everything works fine, even the pre-rendering when moving the object.  But my guess is the pre-rendering when in RayTracing is CPU generated and doesn't leverage the GPU (OpenGL)."
1815286,2019-05-16 16:10:40 UTC,"Hi Brice.
Its true that Raytracing is mostly is CPU generated but still is using some openGL commands to render the image."
1815286,2019-05-16 16:30:10 UTC,"Hi Mario,
No, STEP files do not render (Footprint Properties->3D Settings).  The only thing that renders is a transparent PCB and copper pads."
1815286,2019-05-16 16:54:08 UTC,"Same here. Once it breaks, both footprint 3d shapes, and the 3D board viewer stop working, and render only the transparent PCB and copper pads."
1815286,2019-05-16 23:27:17 UTC,"Crazy theory here, could this just be a problem with Radeon Pro hardware?  Is anyone out there with a consumer ATI card having issues?"
1815286,2019-05-17 14:04:58 UTC,"@Brice - it could be hardware related, but the fact that we can get it working again by just fully restarting the application tells me that it's something that can be fixed in software. Why does a restart of the application fix it? As I said before, it sounds like an OpenGL (re)initialisation issue in Kicad."
1815286,2020-01-07 00:39:35 UTC,"Hi. Everyone,
I cannot attach more than 1 pictures in a comment. So I create more than one comments to make a detailed description.
This is the 3D preview that with the enhanced setting of my display card. Of course it works."
1815286,2019-10-05 12:39:31 UTC,"Same issue on AMD FirePro W6150M, windows 10. Ray tracing works, however it is not being rendered by GPU at all. Only by CPU."
1815286,2019-10-07 17:49:14 UTC,@Jaroslav - I actually removed my WX3100 GPU and running my system using the integrated Intel GPU.  KiCad is much slower but at least 3D rendering works properly.
1815286,2020-01-07 00:34:37 UTC,"Hi.Every one,
I am a new user of the KiCAD software and my display card is the AMD Redeon W4300. I found the 3D viewer module of the current version KiCAD (v5.1.5) can not work on my computer. On the default display driver configuration, it just displayed the PCB with Pads and wire in the 3D viewer without the 3D component, like the above mentioned."
1815286,2020-01-07 00:38:21 UTC,"Hi. Everyone,
I cannot attach more than 1 pictures in a comment. So I create more than one comments to make a detailed description.
This is the 3D preview that with the default setting of my display card. Of course it did not work."
1815286,2019-05-06 20:47:04 UTC,I'm using the latest drivers from AMD.
1815286,2020-01-07 00:40:49 UTC,"Hi. Everyone,
I cannot attach more than 1 pictures in a comment. So I create more than one comments to make a detailed description.
This is the 3D viewer with the enhanced display card setting. It also works."
1815286,2020-01-07 01:41:43 UTC,The KiCad project has moved to GitLab for its bug tracking. You can follow this bug report here: https://gitlab.com/kicad/code/kicad/issues/2547.
1815286,2020-01-07 10:46:53 UTC,"Hi Wenmao, could you follow the Ian sugestion and report there the your findings?
Also, could you post a configuration of your GPU when it was not working? so.. what did you changed to make it work?"
1815286,2020-01-07 18:30:18 UTC,"@wenmao - Thank you for the pointer. I've just created a KiCad profile, making only a single change to the default setting, and it's now working for me too! The only change I made was to switch Anti-aliasing Mode from 'Override application settings' to 'Use application settings' and it's now rendering correctly!!! :)"
1815286,2019-05-17 14:26:05 UTC,I just saw it in the attachments.
1815286,2019-05-06 20:39:41 UTC,I don't think any of our windows devs have an AMD/ATI graphics card that they can test with so I'm not sure if we can resolve this issue any time soon.  I didn't notice but I'm assuming you are using the latest and greatest drivers for your graphics cards.
1815286,2019-05-06 17:45:13 UTC,"@Ken, are you using KiCad 5.1.2?  I'm not sure Brice's issues are the same as yours although they may be related.  The legacy canvas is disable in 5.1.2 so your starting in legacy canvas may be a different issue."
1815286,2019-05-06 19:13:57 UTC,"That's confused me a little bit. I've just installed the latest nightly, and its still reporting a version 5.1.0 (467-gb7e67073e). Same result, so I'm now downloading the latest stable release 5.1.2 and will try it instead."
1815286,2019-02-09 14:00:32 UTC,"Original thread on forum KiCad.info:
https://forum.kicad.info/t/3d-rendering-not-working-reliably/15115/10"
1815286,2019-02-27 19:11:18 UTC,"@Seth, any chance your recent fix handles this?"
1815286,2019-02-27 19:29:35 UTC,There's a good chance that the recent fix will change this behavior.
1815286,2019-02-27 20:26:24 UTC,Just installed and tested the latest nightly:
1815286,2019-03-16 12:01:16 UTC,"@Ken, would you please post the board and 3D models files that cause the problem.  Since the recent opengl fixes did not seem to resolve the issue.  Perhaps it is an issue with your board and/or 3D models.  If you cannot post it publicly, you can send it to me directly."
1815286,2019-03-16 15:01:53 UTC,"Hi. Simply creating a new PCB, and adding a basic footprint creates the problem for me. In the attached example, I've run up Pcbnew.exe and added footprint DIP-28_W15.24mm to a blank PCB. This pulls in the standard 3D image Package_DIP.3dshapes/DIP-28_W15.24mm.wrl."
1815286,2019-05-06 19:55:48 UTC,Exactly the same with 5.1.2 stable build.
1815286,2019-03-18 16:44:15 UTC,"Thank you for looking into this for me. I'm running Kicad on a Dell Precision M6700 laptop with an AMD FirePro M6000 Mobility Pro graphics adaptor. I downloaded and installed the latest driver for this from AMD the other week, but it didn’t make any difference."
1815286,2019-03-18 16:59:58 UTC,"Just installed the Dell driver, but it's exactly the same. Here's some more details from the AMD control centre, if it's of any help:"
1815286,2019-03-18 14:09:58 UTC,"@Ken, I tested the sample board you provided and I'm still not seeing this no matter how many times I open and close the 3D viewer.  I'm thinking it might be a video driver issue.  Do you have the latest video driver installed on your system?  If not, updating them may help resolve your issue.  Does your system use one of the older Intel video chips (the model number escapes me at the moment)?  I know we've had some issues with them in the past."
1815286,2019-03-19 16:10:13 UTC,"@Wayne - According to OpenGL Extensions Viewer, my laptop is running OpenGL v4.6 (although it appears to be using shading language version 4.50). It's worth noting that I have been able to get Kicad 5 running on another PC with an AMD graphics card without any problem."
1815286,2019-05-01 12:44:04 UTC,I'm having the same issues.  All the problems go away when I pull the WX 3100 from my PC and run everything using the integrated Intel HD 530 graphics.
1815286,2019-05-04 00:46:35 UTC,This shows there are 3D parts to be rendered with RayTracing enabled but the OpenGL engine is failing to load the PCB correctly.  All parts load correctly when I remove my AMD WX 3100 graphics card and run KiCad using integrated graphics (Intel HD 530).
1815286,2019-05-04 12:19:08 UTC,"@Brice, thanks for the extra data point.  This definitely seems like a driver issue.  I used to use AMD/ATI cards a long time ago but found their opengl support to be spotty so I switched to nvidia.  I'm not sure we can do anything about this."
1815286,2019-05-04 15:50:45 UTC,The OpenGL engine on 3D Viewer works differently on version 5. It is using some (legacy) OpenGL capabilities to speedup the load and render of the board polygons so it does not need to compute some boolean operations between layers.
1815286,2019-05-05 10:11:19 UTC,The problem I have seems to be more to do with some form of 3D initialisation.
1815286,2019-05-06 18:34:41 UTC,I'm currently running 5.1.0-22-g7e34a5a10.
1815286,2019-03-19 14:31:52 UTC,"@Ken, thanks for the information.  I believe we started using opengl shaders in version 5.0 which may be the issue.  This requires opengl 2.1 or later.  I cannot tell from the AMD version info what version of opengl support is provided by this driver.  The latest opengl version is 4.6 so I'm not sure what 24.20.11000.13543 is telling me.  Anyone else out there successfully using kicad 5.0 or 5.1 with an ATI/AMD graphics card?"
1815286,2019-05-05 23:10:21 UTC,"I can confirm Ken's comments.  My system is having very similar features.  Sometimes 3D content will load, but once it fails once, KiCad has to be restarted."
1815289,2020-05-14 08:10:39 UTC,This bug was fixed in the package chromium-browser - 81.0.4044.129-0ubuntu0.20.04.1
1815289,2020-06-16 17:51:20 UTC,This bug was fixed in the package chromium-browser - 81.0.4044.129-0ubuntu0.19.10.1
1815289,2020-06-11 15:38:43 UTC,Confirmed fixed with chromium-browser 81.0.4044.129-0ubuntu0.19.10.1 from eoan-proposed.
1815289,2020-05-27 11:46:27 UTC,"Hello Jeremy, or anyone else affected,"
1815289,2020-05-14 08:10:44 UTC,"The verification of the Stable Release Update for chromium-browser has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815289,2020-05-08 16:10:09 UTC,Confirmed fixed with chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 from focal-proposed.
1815289,2020-05-07 08:54:18 UTC,"Hello Jeremy, or anyone else affected,"
1815289,2020-04-28 08:12:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815289,2020-04-28 11:54:08 UTC,Also related (and should probably be fixed together with): bug #1870640.
1815289,2020-05-07 11:05:53 UTC,"All autopkgtests for the newly accepted chromium-browser (81.0.4044.129-0ubuntu0.20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:"
1815289,2020-05-02 07:17:41 UTC,This bug was fixed in the package chromium-browser - 81.0.4044.129-0ubuntu1
1815289,2020-04-30 12:38:50 UTC,Fixed with https://bazaar.launchpad.net/~chromium-team/chromium-browser/groovy-stable/revision/1537.
1815293,2019-03-17 12:00:10 UTC,"Maybe there is something wrong with your audio config:
~/.mixxx/soundconfig.xml
or effects:
~/.mixxx/effects.xml
Please try to rename these files."
1815293,2019-02-20 09:42:17 UTC,"Allright, thank you very much for your attention so far."
1815293,2019-02-16 11:29:17 UTC,"The stacktrace doesn't show a crash, just a freeze. Unfortunately the executable does not contain debug symbols, so the trace doesn't reveal any Mixxx source code references."
1815293,2019-02-11 19:37:00 UTC,You're right! I had to ctrl-z to suspend Mixxx from its freeze first. I have pasted the trace I got here: https://pastebin.com/DDYLngTz
1815293,2019-03-16 11:36:03 UTC,Bump?
1815293,2019-02-11 17:11:30 UTC,"Unfortunately that's not the stacktrace, but only the first lines of the log. After Mixxx has crashed you display the stacktrace of all threads by entering the following command in the debugger:"
1815293,2019-02-11 16:12:03 UTC,Thank you for your attention.
1815293,2019-02-10 20:44:08 UTC,The crash is not related to the database as far as I can tell.
1815293,2019-02-11 17:12:55 UTC,You may have skipped step 3 in the instructions?
1815293,2019-02-10 17:20:19 UTC,I am using Mixxx 2.2.0 (build 2.2 r6659). Newest log file attached.
1815293,2019-02-09 16:18:17 UTC,Which version of Mixxx are you using?
1815295,2019-02-16 23:11:37 UTC,"On 2019-02-16 23:04, Christian Boltz wrote:

> You are reporting two issues that are (technically) completely
> different:
"
1815295,2020-08-22 11:04:02 UTC,Did you Vincas file or forward this to actual upstream bug reports at https://gitlab.com/groups/apparmor/-/issues ?
1815295,2019-02-16 21:04:58 UTC,You are reporting two issues that are (technically) completely different:
1815295,2019-02-09 16:41:00 UTC,"Original issue actually is that aa-enforce does not like completely empty profile, like, with only comments, for example:"
1815307,2019-02-20 13:11:02 UTC,Michael Sweet was not able to reproduce this bug with the Canon printer he got at Apple. See
1815307,2019-02-11 21:42:07 UTC,Probably your printer suffers the problem shown in the following upstream bug report on cups-filters:
1815307,2019-02-11 22:29:55 UTC,"The issues referenced in the previous comment are all fixed upstream now. If they were the cause for your problem, your problem will be solved in Disco."
1815307,2019-02-12 16:46:32 UTC,Added the requested result of the ipptool query
1815307,2019-02-12 21:13:09 UTC,Also added the ipptool results of the modified test given in https://github.com/OpenPrinting/cups-filters/issues/22
1815307,2019-02-15 21:23:16 UTC,A similar report got also to CUPS upstream:
1815307,2019-02-15 21:26:47 UTC,@till-kamppeter
1815307,2019-02-15 21:41:08 UTC,"@fargoth, sorry for that comment. I was wrong. What got actually fixed was another thing which I observed during the investigations for this bug."
1815309,2019-04-08 18:10:54 UTC,Don't remember Changing anything
1815309,2019-04-08 18:10:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815314,2019-02-25 13:35:42 UTC,"The issue is that the we need normal & the maximized libary as two different occurences of a library singleton in Deere & Tango, due to the stacked waveforms that can be hidden/moved.
I tried a few things earlier but couldn't solve this issue from within the skins."
1815314,2019-02-25 14:06:26 UTC,"btw the keyboard shortcuts also work again when I click into any overview widget.
maybe it's just that no widget has focus after toggling the swapping the library singletons?"
1815314,2019-09-11 21:58:20 UTC,"If I'm not missing something I think skin.xml of Deere and Tango could both use a WidgetStack to toggle maximized Library, like it works in LateNight. There, the focus jumps to the Sidebar and back to the tracks table when repeatedly toggling [Master],maximize_library, but the shortcuts still work"
1815314,2019-09-21 15:01:01 UTC,https://github.com/mixxxdj/mixxx/pull/2289
1815314,2020-01-29 15:06:14 UTC,https://github.com/mixxxdj/mixxx/pull/2289 is ready for review.
1815318,2019-02-11 08:01:41 UTC,I can confirm the issue using Ubuntu MATE 18.04 LTS as server and Ubuntu MATE 16.04 LTS as client.
1815318,2019-02-11 08:08:41 UTC,Also happens with Ubuntu MATE 18.04 LTS as server and Ubuntu 18.04 LTS as client.
1815318,2019-02-12 17:54:30 UTC,"I believe this is just a different behavior in caja itself. You see, in both cases there is already a caja process running. In bionic's version, if you run caja again, it doesn't bring up a new copy, but instead uses the existing one to spawn the new windows:"
1815318,2019-09-06 21:27:24 UTC,Does using either of these help?
1815318,2019-09-06 22:13:09 UTC,I used ssh -X 192.168.1.162 and gained admittance to the remote system as shown below:
1815318,2019-12-20 04:17:25 UTC,[Expired for caja (Ubuntu) because there has been no activity for 60 days.]
1815318,2020-09-12 16:46:34 UTC,Still happens on 20.10.
1815320,2019-05-17 16:08:55 UTC,"An upload of cryfs to bionic-proposed has been rejected from the upload queue for the following reason: ""This upload includes changes to the packaging (debian/rules, debian/control) that are unrelated to the SRU issue and no justification is given.  Please upload a package that introduces only the necessary upstream changes.""."
1815320,2019-05-15 13:03:39 UTC,Thank you for preparing this. I see a couple of minor packaging changes that don't cause me concern. Everything else looks OK.
1815320,2019-04-20 19:58:28 UTC,"Hello Sebastian, thanks for your work on this! I appreciate the thorough and standards-compliant bug description on the first try. :)"
1815320,2019-04-27 17:11:25 UTC,"That's great, thank you :)
What queue is this? A CI service? Is it normal that the queue takes more than a week or did something go wrong? You uploaded it a week ago but it still says 0.9.9 for cosmic and bionic at https://launchpad.net/ubuntu/+source/cryfs ."
1815322,2019-05-02 11:12:52 UTC,Try to rename the file to something without special characters. it worked for me.
1815322,2019-05-02 11:28:45 UTC,Work too.
1815330,2019-02-10 03:27:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636038"
1815330,2019-12-23 16:51:49 UTC,"Reviewed:  https://review.opendev.org/636038
Committed: https://git.openstack.org/cgit/openstack/tooz/commit/?id=842c7404b2d01c5dd718c14bb55f0cd47471f0e1
Submitter: Zuul
Branch:    master"
1815330,2020-01-06 10:24:00 UTC,This issue was fixed in the openstack/tooz 1.67.2 release.
1815332,2019-02-10 07:30:06 UTC,This change was made by a bot.
1815332,2019-02-20 10:23:08 UTC,"Seems like it's a regression,
Would it be possible for you to do a kernel bisection?"
1815334,2019-04-05 06:13:34 UTC,"Yes, probably we have original missread ^ as Shift."
1815334,2019-06-18 07:48:59 UTC,https://github.com/mixxxdj/mixxx/pull/2178
1815340,2019-04-09 09:16:26 UTC,"Change abandoned by Zoltán Szentgyörgyi (<email address hidden>) on branch: master
Review: https://review.openstack.org/651145"
1815341,2019-02-10 16:06:12 UTC,"If you need instructions for how to test a pull request, refer to the wiki: https://mixxx.org/wiki/doku.php/using_git"
1815341,2019-02-17 19:08:58 UTC,"Can I activate Qt5 in 2.1.7 with this command? Or had qt5=1 no effect of waveform? If I compile Mixxx with this command, the waveform is smoth."
1815341,2019-02-17 15:34:42 UTC,"Hmm, I'm not sure what else to suggest at this point. We may need to talk to a KDE developer."
1815341,2019-02-17 14:43:21 UTC,"I started KDE and killed the kwin_x11 process. I can't handle windows, but I can start Mixxx 2.2 and see the waveform. The waveform already jerk."
1815341,2019-02-16 20:38:04 UTC,Maybe try killing kwin_x11 after starting KDE and start a different window manager? Does it work with GNOME using X or Wayland?
1815341,2019-02-16 17:01:23 UTC,"I tried lot of various settings. Composer de/activate, OpenGL 2.0/3.1/XRender, all VSync setting, HDMI monitor and/or Laptop screen, Display resolution. On all settings Mixxx 2.2 waveform jerk."
1815341,2019-02-16 16:31:53 UTC,Go to KDE System Settings -> Display and Monitor -> Compositor and try changing the various settings there.
1815341,2019-02-16 16:17:08 UTC,I installed Xfce (parallel) on this computer where I have the problem on KDE. I installed also IceWm and the problem exist only on KDE. All desktop environment run on X.org.
1815341,2019-02-16 15:17:07 UTC,That is interesting that it is okay on Xfce. Can you test with Xfce on the computer you originally saw this bug on? Can you test with KDE on the computer where it is working with Xfce? Are you using KDE with X or Wayland?
1815341,2019-02-16 13:46:49 UTC,I run Mixxx 2.2 (Qt 5.7.1) on Xfce and the waveform are smooth. Only on KDE jerk the waveform. This seems to be a problem between KDE and Mixxx. I think there the same problem as https://bugs.launchpad.net/mixxx/+bug/1762111
1815341,2019-02-16 09:28:03 UTC,"I installed Debian Buster with Qt 5.11.3 with Mixxx 2.2.0 and there is the same problem, the waveform is scrolling smother if Mixxx is not in focus. I compile also the pull request https://github.com/mixxxdj/mixxx/pull/1974 but there is the same effect."
1815341,2019-02-13 07:23:15 UTC,On Mixxx 2.1 the VsyncTest is blinking too and the waveform scroll smoothly. Same on Mixxx 2.2 in background.
1815341,2019-02-12 20:56:07 UTC,"Ha moving horizontal line also called tearing happens if there is a vsync issue.
Ideal at 60 Fps, you should see a equal pink area. A red or white flickering is a jerking in the real waveform."
1815341,2019-02-12 17:32:34 UTC,"No, soundcard clock or network clock doesn't change anything."
1815341,2019-02-12 17:03:15 UTC,So the soundcard clock does not change anything?
1815341,2019-02-12 16:16:12 UTC,I change the Engine Clock to Network and Soundcard Clock with the same result.
1815341,2019-02-12 08:58:07 UTC,"I tried to build Mixxx without installed system Qt headers (in a VM) and Mixxx don't find Qt. My steps are:
 cd /mnt/home/qt-everywhere-src-5.12.1/
 ./configure -prefix /mnt/home/qt -system-sqlite -sql-sqlite -qt-zlib -opensource -confirm-license -nomake examples -nomake tests -skip qt3d -skip qtwebengine
 make -j2
 make install
 export PKG_CONFIG_PATH=/mnt/home/qt
 cd ../mixxx/
 scons prefix=/mnt/home/local -j 2 optimize=native qtdir=/mnt/home/qt"
1815341,2019-02-11 21:12:47 UTC,"Try using ""qtdir=/where/you/installed/Qt"" with scons"
1815341,2019-02-11 19:59:34 UTC,"Yes, Debian Stretch use Qt 5.7.1. I try to compiled Qt 5.12.1 with Mixxx master branch and effect was the same. But I think the compiler use the Qt system libraries and the export PKG_CONFIG_PATH=... doesn't work. My guess is confirmed by the fact that during compilation the following is written:"
1815341,2019-02-11 03:32:04 UTC,According to https://packages.debian.org/stretch/qt5-default Debian Stretch ships Qt 5.7.1. Perhaps this is caused by a Qt bug that has been fixed. That could explain why I saw this a while ago with my old laptop but I can no longer reproduce it. Maybe you could try building Mixxx with Qt 5.12.1? There are instructions on the wiki for how to build Mixxx with a version of Qt other than what your distribution ships with: https://mixxx.org/wiki/doku.php/compiling_on_linux#non-system_qt
1815341,2019-02-10 22:25:09 UTC,I am on Ubuntu Xenial with X11 which should be based on Debian Stretch and cannot confirm the issue with similar Hardware.
1815341,2019-02-10 20:13:14 UTC,Thank you for the fast answer.
1815341,2019-02-10 15:47:33 UTC,Thank you for attaching the videos. We have had a few reports of this before (Bug #1762111) but it was not clear if it affected Mixxx 2.2.
1815344,2019-03-06 10:32:48 UTC,"Sorry for late reply. I can only test it on a Samsung laptop because
Toshiba laptop is with my in-laws, who live quite far away from me. Is
testing the v5.0-rc7 up to date?
Yours faithfullyDarek"
1815344,2019-03-08 09:59:04 UTC,"OK. I installed version 5.0. What should I do now to test this? I
worked with a new kernel for 2 days and there was no crash."
1815344,2019-02-20 12:36:35 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1815344,2019-02-20 12:36:53 UTC,Also please remove non-default kernel parameter.
1815344,2019-03-06 10:48:19 UTC,Now the latest one is v5.0.
1815344,2019-02-10 12:30:07 UTC,This change was made by a bot.
1815346,2019-02-10 15:37:10 UTC,"Do you mean that you want the PNS to ""un-push"" tracks that were moved when the cursor allows it?  In other words, tracks should all prefer their original positions unless forbidden by the new track?"
1815346,2019-02-10 16:38:18 UTC,"I hope the attached video makes it clearer. The pushed track is moved beyond pads 5 and 3. It happens in certain point, when the cursor hits some certain coordinates. But when I move the cursor back, the track which was pushed by the working track isn't moved back to its original position. I have to move the cursor way farther back. What it should do is to act like a reversed video, if I follow the same route back with the cursor than which I just moved forward, everything should move backwards exactly like it moved forward, but reversed. If the cursor jumps from one grid point to another and at the same time a track is pushed, that pushed track should move exactly where it was if I move the cursor back to the previous grid point."
1815349,2019-02-28 19:46:53 UTC,We could only provide the static build info.  Some of the info used in the about dialog is generated at run time and requires a valid wxApp instance in order to run.  Calling this from a script where no wxApp was present would fail.  I looked at this and it will require factoring out the static info code from the run time info code before this can be implemented.
1815349,2019-05-11 13:19:58 UTC,"For me, it would be enough to expose DIALOG_ABOUT::buildVersionInfoData( wxString& aMsg, bool aFormatHtml ) to python."
1815353,2019-04-23 23:57:09 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1815353,2019-06-23 04:19:16 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1815355,2019-08-08 23:58:19 UTC,This bug was fixed in the package fonts-junicode - 1.002-1
1815355,2019-08-08 18:14:14 UTC,Welcome I am part of the team and it was just sponsored/uploaded. ;)
1815355,2019-08-06 07:56:49 UTC,"working on upgrading fonts-junicode to 1.002 with the new source format, thanks for the link. guess the release won't happen, nor the move to github..."
1815355,2019-08-06 11:00:51 UTC,Thanks! I have send a message to the Debian Fonts Task Force to do an update.
1815355,2019-04-05 03:05:02 UTC,"i wish he'd move to github.com, that sf.net web interface is so 1995."
1815355,2019-05-29 07:41:25 UTC,"@Pander sure there is, but it's only there because someone made it, usually taking an upstream source tarball release, which is still missing for the version you ask for. sure I could go ahead an create one from the sf svn snapshot, you miss a feature that was added with 1.002?"
1815355,2019-02-10 13:30:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815355,2019-08-06 10:01:44 UTC,"Enjoy! http://phd-sid.ethz.ch/debian/fonts-junicode/fonts-junicode_1.002-1.dsc (src)
http://phd-sid.ethz.ch/debian/fonts-junicode/fonts-junicode_1.002-1_all.deb (deb)"
1815355,2019-02-14 14:07:27 UTC,Here are the source files https://sourceforge.net/p/junicode/junicode/ci/master/tree/
1815355,2019-02-14 08:21:14 UTC,Where's the source files? There's only binary fonts for me to find...
1815358,2019-02-10 14:08:54 UTC,Ah almost forgot the most important information. The project is
1815358,2019-02-10 14:10:11 UTC,I also ran `snapcraft clean term-cheat` which also does not clean the cached package
1815366,2019-02-10 16:54:45 UTC,"After following the entire disk QA scenario - on a full real install, budgie-welcome and an install of gnome-calculator are available via the menu."
1815366,2019-02-13 09:11:03 UTC,It is odd I fully agree with you.
1815366,2019-10-17 12:25:43 UTC,"I played around with the default 18.04.3 live CD, and desktop snap are properly listed in the live session. Note that the default image is using Gnome, so perhaps Budgie desktop is missing something?"
1815366,2019-10-17 12:27:25 UTC,"Note that XDG_DATA_DIRS pointing to /var/lib/snapd/desktop is injected into the environment. If budgie spin is using a different shell than bash, then there's a known problem since zsh does not load /etc/profile.d"
1815366,2019-10-17 13:51:49 UTC,Budgie is using the same shell as GNOME-Shell i.e. Bash
1815366,2019-12-17 04:17:28 UTC,[Expired for snapd because there has been no activity for 60 days.]
1815366,2019-12-17 04:17:29 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1815366,2019-02-12 23:28:36 UTC,"It's weird that vm/real machine would make a difference, maybe it's a timing issue (.desktop created by snapd later than the desktop UI loads and the UI doesn't refresh?)"
1815368,2019-02-10 17:44:41 UTC,Please see the attached corrected wallpaper.
1815369,2019-08-20 11:29:39 UTC,"Thank you for pointing this out.  However, this was filed using the automated method recommended by GIMP at the time of the crash, with no instruction to file using the ""ubuntu-bug"" tool or to open a terminal and type ""ubuntu-bug {packagename}"".  Therefore, this advice is not very practical or useful, considering the fact that the crash results in an automated bug report.  Please help GIMP bug reporting so that the automated bug report provides the correct information, hints on the correct tool, in the future."
1815369,2019-08-20 01:33:34 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1815370,2020-10-14 23:35:38 UTC,We should backport the fix (if it s fixed) to 2.2 if we're going to release another 2.2 version.
1815370,2020-10-14 17:09:57 UTC,"Fixed in 2.3?
Looks goog on ubuntu 20.04"
1815370,2019-02-10 23:16:36 UTC,"Strange, I could confirm it on the first start after installation on windows 10.
However, it is gone in after the second start.
I can also not confirm this on Ubuntu Xenial with the latest 2.2.1-rc1"
1815370,2020-05-09 08:49:39 UTC,This is still an issue in 2.3 alpha.
1815370,2020-07-12 12:33:22 UTC,Any volunteers for this? ronso0?
1815376,2019-02-11 19:43:08 UTC,They’re fetched through RENDER_SETTINGS::GetColor() and GetLayerColor().
1815376,2019-02-11 18:25:59 UTC,"maybe slightly related:
i wish there was an easier way to change the colors/settings of the 3D Viewer, like, i could make a few ""presets"" for more realistic-looking green, yellow, blue, red, white, black, etc.. with various combinations of gold, copper, HASL..
right now it's possible only by hacking around with the config files (but there are many other settings contained in it besides these colors)"
1815376,2019-04-07 16:52:53 UTC,"You may need to enter a palette based on html code in kicad, For example, #000000 or #FFFFFF."
1815376,2019-03-19 13:45:58 UTC,"@Arnie, unless you are creating package builds where you need a different path than CMAKE_INSTALL_PATH, you don't need to set DEFAULT_INSTALL_PATH separately as it defaults to CMAKE_INSTALL_PATH.  Just set -DCMAKE_INSTALL_PATH=/path/to/install/kicad when you run cmake and you should be fine.  FYI, development questions like these should be posted to the developers mailing list.  This prevents the bug report being polluted with information that is not related to the actual bug."
1815376,2019-03-16 19:01:55 UTC,"So I've done a successful build with MSYS2, and made some initial mods to a few files, I'm about to do a test build But..."
1815376,2019-03-06 19:03:17 UTC,Once 5.1 is branched we can start merging v6 changes.  That should happen by this weekend unless yet another critical bug get reported before then.  I still have to prioritize the list of merges that are ready to go which I will do before 5.1 gets branched but it should be more than a month or so until everything is merged and v6 is under heavy development.
1815376,2019-05-01 12:16:08 UTC,"@Arnie, are you still looking at this? What is the status on your proposed patch? I know @Jon Evans is planning on working on this area during v6. To avoid duplicating effort, I think we should mark this report as a duplicate with https://bugs.launchpad.net/kicad/+bug/1678345"
1815376,2019-03-06 16:44:52 UTC,"Yeah, was hoping to get back to it this week and do that. Did it anyway. I'm expecting submission openings for next version and hoping to have something solid by then. Anybody have a timeline on that??"
1815376,2019-03-05 12:54:29 UTC,"@Arnie, are you still looking at this?  Should I assign the bug to you?"
1815376,2019-02-12 02:58:45 UTC,*** ACK! BLAH! ***
1815376,2019-02-12 02:43:09 UTC,The colors are defined in colors.cpp file as an ENUM type.
1815376,2019-03-06 18:31:11 UTC,"@Arnie, good question.  2 to 6 weeks would be my best guess, but @Wayne would have a better idea."
1815376,2019-02-11 20:15:25 UTC,I believe someone already sent a patch for review to the developers mailing list for user defined color palettes although I don't think this was general approach.  I don't think the patch has been reviewed because it would not be allowed until v6 development opens which should be soon.  Please search the dev mailing list and coordinate with other developers before you spend any time working on this so you don't waste your time duplicating this feature.
1815377,2019-08-14 10:10:47 UTC,You're always welcome to create a patch. I think these days that'd be the fastest solution for yourself especially if you still keep using DC++ code as upstream.
1815377,2019-02-11 15:27:14 UTC,"There were numerous reports over the years of files being left out of share in situations similar to what's described here and this seems to be the most probable reason of those ""randomly"" skipped files in folders containing an .sfv file.
Thanks for taking care of reporting it."
1815377,2019-08-14 06:42:38 UTC,"Should I make a code fix and send a patch, or will you fix it yourself? EiskaltDC++ is waiting for upstream code fix in DC++."
1815378,2019-02-18 07:25:55 UTC,"Thank you for the advice, it's hard to find the right place for a bug report."
1815378,2019-02-18 07:46:29 UTC,Thanks
1815378,2019-02-12 23:25:38 UTC,"Thank you for your bug report, could you maybe report it as well to the gvfs upstream gitlab?
https://gitlab.gnome.org/GNOME/gvfs/issues"
1815380,2019-09-19 14:54:14 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1815383,2019-02-10 22:19:18 UTC,"It seems that something is wrong in the C:\1msts\ROUTES\Cima\openrails\Cima.trk file.
Could you attach it?"
1815383,2019-02-10 23:08:20 UTC,"Hi there, I did finally get it fixed. I had to change the name of the trk file from Cima to Cimasub to get it working.Thanks for the reply.Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: mbm_OR <email address hidden> Date: 2019-02-10  3:19 PM  (GMT-07:00) To: <email address hidden> Subject: [Bug 1815383] Re: cima route won't load It seems that something is wrong in the C:\1msts\ROUTES\Cima\openrails\Cima.trk file.Could you attach it?Regards,Mauricio.-- You received this bug notification because you are subscribed to the bugreport.https://bugs.launchpad.net/bugs/1815383Title:  cima route won't loadStatus in Open Rails:  NewBug description:  Cima route won't loadTo manage notifications about this bug go to:https://bugs.launchpad.net/or/+bug/1815383/+subscriptions"
1815383,2019-02-11 12:33:39 UTC,"Hi Johnny,"
1815383,2019-11-11 04:17:17 UTC,[Expired for Open Rails because there has been no activity for 60 days.]
1815386,2019-02-10 21:37:57 UTC,Error was: Cannot open mailbox
1815387,2019-02-10 21:55:18 UTC,This is what I expect to happen
1815387,2019-02-10 21:56:15 UTC,This is what I expect to happen
1815390,2019-02-11 14:54:21 UTC,We originally didn't allow capacity base QoS mixed with setting max values. Is this related to what you are seeing? https://review.openstack.org/#/c/625058/
1815396,2019-02-13 09:01:20 UTC,"Removing packages from disco:
 golang-1.8 1.8.3-2ubuntu1 in disco
  golang-1.8 1.8.3-2ubuntu1 in disco amd64
  golang-1.8 1.8.3-2ubuntu1 in disco arm64
  golang-1.8 1.8.3-2ubuntu1 in disco armhf
  golang-1.8 1.8.3-2ubuntu1 in disco i386
  golang-1.8 1.8.3-2ubuntu1 in disco ppc64el
  golang-1.8 1.8.3-2ubuntu1 in disco s390x
  golang-1.8-doc 1.8.3-2ubuntu1 in disco amd64
  golang-1.8-doc 1.8.3-2ubuntu1 in disco arm64
  golang-1.8-doc 1.8.3-2ubuntu1 in disco armhf
  golang-1.8-doc 1.8.3-2ubuntu1 in disco i386
  golang-1.8-doc 1.8.3-2ubuntu1 in disco ppc64el
  golang-1.8-doc 1.8.3-2ubuntu1 in disco s390x
  golang-1.8-go 1.8.3-2ubuntu1 in disco amd64
  golang-1.8-go 1.8.3-2ubuntu1 in disco arm64
  golang-1.8-go 1.8.3-2ubuntu1 in disco armhf
  golang-1.8-go 1.8.3-2ubuntu1 in disco i386
  golang-1.8-go 1.8.3-2ubuntu1 in disco ppc64el
  golang-1.8-go 1.8.3-2ubuntu1 in disco s390x
  golang-1.8-go-shared-dev 1.8.3-2ubuntu1 in disco amd64
  golang-1.8-go-shared-dev 1.8.3-2ubuntu1 in disco arm64
  golang-1.8-go-shared-dev 1.8.3-2ubuntu1 in disco armhf
  golang-1.8-go-shared-dev 1.8.3-2ubuntu1 in disco i386
  golang-1.8-go-shared-dev 1.8.3-2ubuntu1 in disco ppc64el
  golang-1.8-go-shared-dev 1.8.3-2ubuntu1 in disco s390x
  golang-1.8-src 1.8.3-2ubuntu1 in disco amd64
  golang-1.8-src 1.8.3-2ubuntu1 in disco arm64
  golang-1.8-src 1.8.3-2ubuntu1 in disco armhf
  golang-1.8-src 1.8.3-2ubuntu1 in disco i386
  golang-1.8-src 1.8.3-2ubuntu1 in disco ppc64el
  golang-1.8-src 1.8.3-2ubuntu1 in disco s390x
  libgolang-1.8-std1 1.8.3-2ubuntu1 in disco amd64
  libgolang-1.8-std1 1.8.3-2ubuntu1 in disco arm64
  libgolang-1.8-std1 1.8.3-2ubuntu1 in disco armhf
  libgolang-1.8-std1 1.8.3-2ubuntu1 in disco i386
  libgolang-1.8-std1 1.8.3-2ubuntu1 in disco ppc64el
  libgolang-1.8-std1 1.8.3-2ubuntu1 in disco s390x
Comment: LP: #1815396, remove golang-1.8, no rdeps
1 package successfully removed."
1815396,2019-03-02 01:09:01 UTC,An upload is also needed to cosmic.
1815396,2019-03-08 09:36:31 UTC,"Hello Michael, or anyone else affected,"
1815396,2019-03-08 09:37:38 UTC,"Hello Michael, or anyone else affected,"
1815396,2019-06-07 19:29:09 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1815396,2019-06-27 16:14:36 UTC,The test case was 'build the package'.
1815396,2019-06-27 16:16:35 UTC,This bug was fixed in the package golang-1.8 - 1.8.3-2ubuntu1.18.04.1
1815396,2019-06-27 16:16:40 UTC,"The verification of the Stable Release Update for golang-1.8 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815396,2019-07-23 20:20:23 UTC,The version of golang-1.8 in the proposed pocket of Cosmic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.
1815397,2019-02-11 01:11:24 UTC,https://github.com/juju/juju/pull/9730
1815397,2019-02-13 19:49:36 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1815398,2019-02-11 00:43:03 UTC,dmesg output for the microSD card insertion.
1815403,2019-11-14 20:35:00 UTC,"Reviewed:  https://review.opendev.org/694329
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2d91a8463f194edae863b51b2224bbec5cd8c68a
Submitter: Zuul
Branch:    master"
1815403,2019-11-14 15:27:32 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/694329"
1815403,2019-02-14 21:21:37 UTC,"By the way, I think the suggested re-wording in the server concepts guide is good so I've marked the bug as confirmed based on that docs clarification."
1815403,2019-06-06 10:34:51 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/663590"
1815403,2019-02-14 21:20:42 UTC,"Is this just a request for a clarification in the docs or something more, like making the suspend API optional also shelve the server? Because the former is easy, the latter is a new more complicated feature which has been discussed before:"
1815403,2019-11-14 03:08:21 UTC,"Reviewed:  https://review.opendev.org/663590
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3badb674f6604d3beca4ba557939d4fbc07f6178
Submitter: Zuul
Branch:    master"
1815405,2019-02-11 03:21:33 UTC,Fix here: https://github.com/juju/juju/pull/9734
1815405,2019-02-13 19:49:21 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1815407,2019-03-19 20:27:54 UTC,This should be fixed in 1.6.
1815409,2019-02-12 15:19:54 UTC,Title mis-leading and needed to point to Virtualbox not vagrant. VirtualBox 5.2.26 still boots fine.
1815409,2019-02-12 15:55:22 UTC,"Hi Coury,"
1815409,2019-02-13 01:09:05 UTC,"Hello Dan,"
1815409,2019-02-13 15:31:13 UTC,"Hi Coury,"
1815409,2019-02-14 02:42:14 UTC,"Hey Dan,"
1815412,2019-09-16 13:53:53 UTC,Migrated to https://github.com/widelands/widelands/issues/2127
1815417,2020-07-04 04:17:30 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1815417,2020-05-04 14:50:57 UTC,"From the information in the report it is not clear that
* the network ec3c94d7-50fb-41cc-843e-e55074dbdfc4 exists in neutron and
* visible for the demo user"
1815417,2020-05-04 14:52:24 UTC,I set the bug to Incomplete as I have questions above. When you answer it please set the bug back to New state.
1815420,2020-05-11 16:34:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815422,2019-07-22 19:58:00 UTC,"That is odd, perhaps there is a paste error?"
1815422,2019-07-23 05:52:01 UTC,"Did you run this directly in a a subdir of /home/? It depends on the
current working dir."
1815422,2021-01-21 16:49:27 UTC,"It looks like in Python >=3.5 we can match against os.path.commonpath() as it will actually compare path elements for the common leading components, rather than just treating them as opaque strings."
1815422,2021-01-21 16:59:12 UTC,I've proposed this as a fix in https://review.opendev.org/771854 since it seemed like nobody else was interested in picking it up.
1815422,2021-01-25 21:04:22 UTC,That change merged a few days ago and was subsequently deployed to the site moments thereafter.
1815423,2019-08-05 18:14:53 UTC,"https://<email address hidden>/ is a patch which fixes the C test case (and may also fix the node.js case, though I don't have a setup to test that)."
1815423,2019-09-20 15:23:02 UTC,"This should be fixed by commit 1e8a98b53867f61da9, which will be in the 4.2 release."
1815427,2019-02-11 13:38:17 UTC,This bug was fixed in the package kauth - 5.54.0-2ubuntu1
1815428,2019-03-18 01:26:52 UTC,"ok, understood, again, this might take some time :(, I don't want to break current functionalities :("
1815428,2019-03-29 04:45:52 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/449510
1815428,2019-03-15 03:47:35 UTC,"ok, this is because of some history reason....."
1815428,2019-03-13 10:06:05 UTC,"Hi,"
1815428,2019-03-15 07:38:01 UTC,"For now it is acceptable. The create guest is more difficult I think. For us if create guest is done, also the deploy over more than 1 disk for an OS is necessary.
The customer can now live with the OS on 1 disk, but if the other disks can be added through CC then is that a big winner for us."
1815445,2019-02-22 17:48:59 UTC,"Can you please provide your QEMU version, command line, and any QMP/HMP commands you issued, and the expected/desired effect?"
1815447,2019-02-11 17:47:03 UTC,Thanks for reporting.
1815447,2019-04-17 16:55:55 UTC,"Demoting packages to disco-proposed:
 fasttracker2 0.1+b137-1 in disco
Comment: Not for release, per Debian maintainer and upstream; LP: #1815447
1 package successfully demoted."
1815447,2019-10-14 12:37:46 UTC,Drop block-proposed tag
1815448,2019-02-15 09:09:13 UTC,"So this needs investigation. Strangely, it feels to me that the feature works as intended now. I have renamed the current/ directory of that 'broken' run into current.broken/ and, when checking yesterday, I have noticed many symlinks to the old images there. It seemed like it just needed some more time for that to happen (and the mirror sync happened at the wrong time)."
1815451,2019-02-14 11:33:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1815451,2019-02-20 10:12:58 UTC,This bug was fixed in the package linux-azure - 4.18.0-1011.11~18.04.1
1815451,2019-02-21 07:31:44 UTC,This bug was fixed in the package linux-azure - 4.15.0-1039.43
1815453,2020-12-16 08:55:16 UTC,This has long been resolved. Marking this as resolved to reflect so.
1815453,2019-02-15 17:06:16 UTC,"Agreed with Jeremy here.  Thanks for the feedback, Jeremy."
1815453,2019-02-15 16:46:43 UTC,"Why will sending announcements from another address make you more comfortable? The only way Kata users and distributors are going to get to know and trust the community members handling vulnerability reports is to see them engaging in public activity like making official announcements. Signing the announcement cryptographically with your personal key is also a good way to provide attestation in the public record, but your users should ideally grow to trust Kata's community members who are doing this work. In most cases your users likely even have no idea who/what the OSF is so, seeing announcements from such an address conveys no useful authority for them anyway."
1815453,2019-02-14 02:18:35 UTC,"FWIW, here is the attacking code [1] and a blog explaining the bug in more details by the original researcher [2]."
1815453,2019-02-15 12:20:20 UTC,"I'm marking this item as 'medium' - we should do more investigation and update libcontainer, but there is no immediate threat to Kata Containers."
1815453,2019-02-13 11:30:14 UTC,"@fungi - great suggestion. Indeed, I think there are a few steps we need to take now:"
1815453,2019-02-13 11:34:55 UTC,"Update. I've emailed an early heads up and update to Aleksa privately. It may be that he has some deeper insight and ideas that are applicable to kata, so I'll be interested to see what he thinks."
1815453,2019-02-11 15:45:50 UTC,"Chatted with EricE. I will ask JulioMontes if he can evaluate this for us, as he has experience in the area of libcontainer and our use in the agent."
1815453,2019-02-11 21:58:01 UTC,"Since exploit code will be release until 2019-02-18, I had to write an exploit in C to reproduce it and effectively, runC binary can be modified from inside the container :S.
As is mentioned in the report, the process that runs inside the container will be able to modify the binary until it's available (not running), in the case of kata-containers our ""runC"" binary is the kata-agent and in our case (fortunately) kata-agent is always busy (running), bu we should update libcontainers either way ;)"
1815453,2019-02-14 06:08:20 UTC,"Right now since we do not restart kata-agent, we are not affected by the CVE. However, there were discussions about live-upgrading kata-agent in a running sandbox. So when that feature is implemented, we need to take care not be bitten by the same issue here."
1815453,2019-02-12 15:07:26 UTC,"When you do, it would also be a good idea to update the CVE-2019-5736 record with MITRE noting that Kata deployments aren't practically vulnerable to this."
1815453,2019-02-12 10:18:02 UTC,"Excellent Julio - thanks for reproducing and the clear diagnosis.
Are you able to PR an update to the libcontainers? Let me know when you have it ready and I will publish this report."
1815457,2019-02-11 16:04:29 UTC,Would need the glance server logs to troubleshoot
1815457,2019-02-12 05:07:50 UTC,How can I send glance server logs?
1815457,2019-02-12 05:52:06 UTC,This is the logs of glance after I run the command 'openstack overcloud image upload':
1815457,2019-03-19 13:38:15 UTC,Is there any stack trace in the logs? that doesn't provide any information as to what could have been wrong. Could you also provide the versions that you're using?
1815457,2019-05-19 04:17:33 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1815461,2020-05-25 14:06:15 UTC,"Reviewed:  https://review.opendev.org/723533
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=096d582d60f18f309e7a985ed4e48e22646a4a6c
Submitter: Zuul
Branch:    stable/rocky"
1815461,2020-05-25 05:35:05 UTC,"Reviewed:  https://review.opendev.org/723531
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=21d91974ac922c33be867e11b17b6fdade46dd5b
Submitter: Zuul
Branch:    stable/stein"
1815461,2020-05-06 10:17:13 UTC,"Reviewed:  https://review.opendev.org/723530
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=644e05ce9d94a1f96bf8d036c0eaf0ec1deb818b
Submitter: Zuul
Branch:    stable/train"
1815461,2020-04-29 14:47:16 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/724339"
1815461,2020-05-05 13:41:16 UTC,"Reviewed:  https://review.opendev.org/724339
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=e779c0e274062a48e327c752ea46a8b70ecef845
Submitter: Zuul
Branch:    stable/ussuri"
1815461,2020-04-27 13:37:31 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/723531"
1815461,2020-04-27 13:37:17 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/723530"
1815461,2020-04-27 12:00:15 UTC,"Reviewed:  https://review.opendev.org/714019
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=3c33f46dc8196809d67301f20c8b920cad03b372
Submitter: Zuul
Branch:    master"
1815461,2020-04-07 14:18:07 UTC,"Hi Norman, thanks for the fix. Could you add more steps how can I reproduce this bug so I can try your fix?"
1815461,2020-03-20 02:27:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/714019"
1815461,2020-04-27 13:37:57 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/723533"
1815466,2019-10-30 14:52:15 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/635440"
1815466,2019-10-30 14:53:06 UTC,"Marking as incomplete because as I said on the proposed fix, I don't see how the failure in the compute manager code is setting the instance to ERROR status or reflecting anything back in the API because the API does an asynchronous RPC cast to the compute service to do the abort operation."
1815466,2019-12-30 04:17:26 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1815468,2019-02-11 15:00:11 UTC,"This is only a flaky test, not a critical issue for production, as it is only an 'observe behavior in the test suite' problem."
1815468,2019-02-11 15:03:33 UTC,https://github.com/juju/juju/pull/9737 is a fix for 2.5
1815468,2019-02-13 19:49:14 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1815469,2019-02-11 16:24:17 UTC,"It looks like the issue might actually be on the worker instead of the master, but I think we should be doing similar checks & reporting on both."
1815469,2019-02-11 17:15:11 UTC,I'm pretty sure we can't stop most of the systemd services from starting because snapd starts them as soon as you install the snap. Best we could do to reduce log spam there is to make the wrapper scripts not run the underlying service if the snap isn't configured yet.
1815469,2019-03-04 09:24:20 UTC,reverting spam changes to description and summary
1815471,2019-02-13 19:49:12 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1815471,2019-02-11 18:35:39 UTC,http://ci.jujucharms.com/job/make-check-juju/2863/testReport/junit/github/com_juju_juju_worker_lease/TestPackage/
1815471,2019-02-11 15:16:59 UTC,"I don't think this is a production issue, just a flaky test, as such it shouldn't block 2.5.1"
1815471,2019-02-12 11:07:05 UTC,https://github.com/juju/juju/pull/9742 fixes ~5 tests that seem flaky in worker/lease.
1815475,2019-02-27 18:51:02 UTC,"Hello Dimitri, or anyone else affected,"
1815475,2019-03-06 08:49:32 UTC,The package builds! https://launchpad.net/ubuntu/+source/libevent-rpc-perl/1.08-2ubuntu0.1
1815475,2019-03-07 10:16:13 UTC,"The verification of the Stable Release Update for libevent-rpc-perl has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815475,2019-03-07 10:26:14 UTC,This bug was fixed in the package libevent-rpc-perl - 1.08-2ubuntu0.1
1815476,2019-02-14 21:28:06 UTC,"Hmm, it looks like the API does allow passing a string for the flavor swap size:"
1815476,2019-02-19 10:49:56 UTC,"Hi Matt,"
1815476,2019-02-25 01:16:42 UTC,"Flavor's checksum uses the check rule of volume_size [1], As Matt said, that's unfortunate. Personally think that the transfer type of swap can be restricted to 'integer'."
1815476,2019-02-25 05:38:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639012"
1815476,2019-06-28 22:26:05 UTC,"Change abandoned by Brin Zhang (<email address hidden>) on branch: master
Review: https://review.opendev.org/639012"
1815476,2019-09-25 09:25:13 UTC,Handled as part of https://blueprints.launchpad.net/nova/+spec/api-consistency-cleanup
1815477,2019-03-21 09:49:57 UTC,And sorry for dragging in even the Openstack team into this who even did their verification in the first day I asked.
1815477,2019-03-21 09:48:43 UTC,"Sad but ok for now - thanks Frank for the info.
For the coming SRu I'll strip 2.11.2 out and only fix the so far bundled qemu-img fix."
1815477,2019-03-21 09:32:23 UTC,"This ticket was discussed in a call with the outcome that it will be handled differently. Hopefully there was not too much effort that got already spent.
Since this is no longer needed, we think it's best to mention it and drop it now and not wait until the SRU process already started ..."
1815477,2019-03-21 06:28:57 UTC,"@lagarcia - That is unfortunate to hear, as I'm sure people would benefit in general from the fixes in the stable release - if we can ensure well enough that there are no new issues introduced."
1815477,2019-03-20 22:49:21 UTC,"------- Comment From <email address hidden> 2019-03-20 18:45 EDT-------
After further discussion, IBM is withdrawing this request."
1815477,2019-03-06 10:07:01 UTC,"There is a test PPA [1] available that we can use to pre-check this before the actual SRU.
Since there are quite some changes I'll run all my checks on the PPA, but I'd ask you to please test ppc64el before I bring that to the SRU Team."
1815477,2019-03-05 16:30:12 UTC,"I've got all changes applied fine, tomorrow I'll create PPAs to test"
1815477,2019-02-27 06:08:03 UTC,"FYI - The currently ongoing SRU is IMHO ready to be released, but gated by some tests (not broken by qemu but needing cleanup). Furthermore the 2.11.2 changes need the same machine type cleanup as in our former discussion about the same topic - but that I can do on my own.
Just to let you know why this takes a while this time, but IIRC this isn't of a particular urgency right now (let me know you think different) - I checked CVEs all that are contained we have already."
1815477,2019-02-26 15:24:09 UTC,"Adjusting ""Importance"" to reflect tagging."
1815477,2019-03-08 08:17:48 UTC,Migration and an assortment of Misc regression checks look good as well.
1815477,2019-02-11 16:41:08 UTC,"Hi Leonardo,
I'm generally for that, but we are still in a freeze for 18.04.2 being released and even then there is a qemu in the SRU queue that has to clear first.
I'll work on that once these blockers are removed, if there is any extra urgency behind it let me know."
1815483,2019-08-19 06:09:41 UTC,"Thanks for the check Eduardo, I'm actually not sure the Desktop Team still drives this oO.
All mid/high prio issues of the MIR review got adressed as well.
In terms of the process it seems this would be ok to be promoted, given that no commit is made to trigger the component mismatch per [1] the state for this until that is done is ""in progress""."
1815483,2019-02-13 08:42:18 UTC,"Doing the usual MIR checks I found most of them to be good:
- Duplication: it is actually deduplicating the embedded copies
- no lintian complains about packaging
- no functional bugs in Debian / Ubuntu yet (not used that much thou)
- Upstream is at and LGTM
- no embedded other libs
- no static linking
- d/rules and d/control are very clean
- meson build seems straight forward
- hardning=+all is in place
- runs (a few) build time self-tests
- you volunteered Ubuntu-Desktop as package subscriber
- no FTBFS currently nor in the recent history
- symbols are tracked for dh_makeshlibs
- packaging hs the most current release and updates ~monthly at least for now
- LD_LIBRARY_PATH only used in build
- no sudo (or similar) usage"
1815483,2019-02-24 14:52:36 UTC,I fixed the build issues you pointed out in Debian and Ubuntu now.
1815483,2019-02-24 14:53:00 UTC,*will begin shipping*
1815483,2019-08-16 14:59:21 UTC,"I reviewed libhandy 0.0.10-1 as checked into eoan. This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1815483,2020-03-02 11:15:17 UTC,gnome-calendar is now depending on it so we are going to promote
1815483,2020-03-04 15:41:19 UTC,package subscriber is missing
1815483,2020-03-09 09:44:23 UTC,desktop-package subscribed and package promotoed
1815494,2019-02-28 13:20:51 UTC,This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.9
1815494,2019-02-28 13:20:41 UTC,"The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815494,2019-04-25 10:50:00 UTC,This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.2
1815494,2019-03-12 17:49:49 UTC,Verified with unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 on Xenial:
1815494,2019-02-28 13:20:31 UTC,This bug was fixed in the package unattended-upgrades - 1.5ubuntu3.18.10.2
1815494,2019-02-20 19:23:38 UTC,This bug was fixed in the package unattended-upgrades - 1.10ubuntu1
1815494,2019-02-22 10:35:31 UTC,Verified with unattended-upgrades/1.1ubuntu1.18.04.9 on Bionic:
1815494,2019-02-22 10:17:02 UTC,Verified on unattended-upgrades/1.5ubuntu3.18.10.2 for Cosmic:
1815494,2019-02-21 17:31:01 UTC,"Hello Balint, or anyone else affected,"
1815494,2019-02-21 16:25:26 UTC,"Hello Balint, or anyone else affected,"
1815494,2019-02-28 13:01:32 UTC,"Hello Balint, or anyone else affected,"
1815497,2020-04-03 02:39:33 UTC,Fixed in the 20.04 documentation:
1815500,2019-09-30 15:22:45 UTC,"Where would you like to see the pod monitoring? Are you using prometheus to monitor the cluster or just nagios? If just nagios, how would you suggest something not tied to a single host is handled in nagios?"
1815500,2019-10-02 05:28:45 UTC,Node ready checks are in https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/37
1815500,2019-12-10 03:23:19 UTC,Review from #37 covered in #42:
1815508,2020-08-04 08:22:47 UTC,"I'm assuming this is fixed in a later release like 20.04, but if not, reopen or file a new bug"
1815508,2019-02-21 01:33:38 UTC,I use ZFS. I looked here:
1815508,2019-02-13 11:21:49 UTC,"please try the latest mainline kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/"
1815508,2019-02-11 20:05:16 UTC,redacted copy of apport-collect output
1815508,2019-02-11 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1815508,2019-02-11 20:10:15 UTC,"Following advice I saw on Stackexchange, I've been setting `intel_iommu=igfx_off` on the kernel command line; this seems to mitigate, but the bug still occurs."
1815510,2019-10-21 09:59:38 UTC,"if you still see the bug, feel free to reopen, otherwise I'm assuming it's fixed by a later update"
1815510,2019-02-15 13:30:36 UTC,this needs to be filed upstream and preferably bisected to see why that's happening
1815510,2019-02-13 17:57:36 UTC,"Yes, when upgrading MESA in Bionic, the issue would arise. I can't imagine why MESA would be this damaging though."
1815510,2019-02-13 11:18:14 UTC,You say just upgrading mesa would cause it on bionic too? It already got 18.2.2 from cosmic.
1815510,2019-02-12 04:43:24 UTC,apport information
1815510,2019-02-12 04:43:22 UTC,apport information
1815510,2019-02-12 04:43:17 UTC,apport information
1815510,2019-02-12 04:43:18 UTC,apport information
1815510,2019-02-12 04:43:15 UTC,apport information
1815510,2019-02-12 04:43:20 UTC,apport information
1815510,2019-02-12 04:43:13 UTC,apport information
1815510,2019-02-12 04:05:04 UTC,"Was told to include a package name. Though it's quite difficult to actually narrow down a specific *package* that causes this issue, the linked wiki document  suggests 'linux' if I'm filing this against the kernel, which I guess I am as versions with older kernels are alright."
1815510,2019-02-12 04:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1815510,2019-02-12 04:43:06 UTC,apport information
1815510,2019-02-11 20:21:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1815510,2019-02-12 04:43:08 UTC,apport information
1815510,2019-02-12 04:43:10 UTC,apport information
1815510,2019-02-12 04:43:12 UTC,apport information
1815510,2019-02-12 04:43:07 UTC,apport information
1815510,2019-02-12 04:43:14 UTC,apport information
1815513,2019-06-19 18:32:36 UTC,"I am not sure storage nodes related issue. But just to make sure we test in same configuration .
I was able to test in similar configuration . When I pull controller-0 Mgt ment cable for less than 30 seconds as I described above description controller-0 got rebooted and came as failed state below . Then after long wait ~15min it got rebooted again to recover the failed state . This was observed cable pull for active and standby controller. But if we have the cable pull for more than 30 seconds with one reboot host is recovered as available."
1815513,2019-08-14 20:33:28 UTC,This was verified in load 2019-08-12 21:00:17
1815513,2019-07-23 18:25:38 UTC,"As confirmed above by Yi Wang, this is a duplicate of https://bugs.launchpad.net/starlingx/+bug/1835268"
1815513,2019-07-23 01:09:19 UTC,"Re-verified this issue with 20190721T013000Z build plus bare metal 2+1+1 configuration. Tried three times, not reproduced this issue. So I think this issue has been resolved by https://review.opendev.org/#/c/670615/. Will set the bug to ""Fixed Released""."
1815513,2019-07-19 01:57:40 UTC,LP1835268 has just been fixed. I will use tomorrow daily build to re-verify this issue.
1815513,2019-07-05 03:32:21 UTC,"Per Eric's analysis, this LP may be a duplicate of LP 1815969 which depends on LP 1835268. I will retest this  issue once the other two LPs are resolved."
1815513,2019-06-20 01:11:41 UTC,"@Anujeyan, it seems we both can see the same phenomenon for ""pulling cable for more than 30s"". The whole behavior is expected."
1815513,2019-06-19 00:54:26 UTC,@Anujeyan Thanks for your help! I don't have enough machines. That's why I chose 2+1+1 configuration. Is the number of storage nodes related to this issue?
1815513,2019-06-14 06:00:38 UTC,"@Anujeyan, any updates from your side?"
1815513,2019-06-06 05:37:57 UTC,"@Anujeyan, I did one more round test since I didn't see the same phenomenon as what you reported. Below is my steps. I made some changes on step 2 for reproducing your result."
1815513,2019-06-04 09:57:33 UTC,"@Anujeyan, I didn't see the same phenomenon as yours. Could you check if you can reproduce this issue?"
1815513,2019-06-04 09:24:16 UTC,"@Anujeyan, as I commented before. With duplex configuration, I saw different behavior. After lock/unlock operations, the system recovered."
1815513,2019-04-24 05:25:00 UTC,"4.17 codebase, duplex configuration, bare metal env, reproduced this issue."
1815513,2019-04-24 05:16:01 UTC,"4.17 codebase, duplex configuration virtual env, not reproduced this issue."
1815513,2019-02-13 18:20:53 UTC,Marking as release gating; requires further investigation
1815513,2019-06-18 13:52:40 UTC,I will try when I get a similar lab. In the above test I see only one storage I would suggest to have similar configuration with 2 storage .
1815514,2019-03-01 16:17:10 UTC,"Hello roland
I did:
make distclean
./autogen.sh
./configure
make
make check
make install
Here is log"
1815514,2019-02-28 19:26:00 UTC,"> It appear to delay compile and the initial make for example, no errors.
> make and make install now works
"
1815514,2019-02-28 17:38:09 UTC,"Hello Roland
git clone git://git.geda-project.org/geda-gaf fresh install"
1815514,2019-02-12 16:12:28 UTC,Thank you for reporting this.
1815514,2019-02-27 16:31:47 UTC,"Sorry, I missed this the first time."
1815514,2019-02-20 18:45:43 UTC,"HelloDescription: Debian GNU/Linux 9.7 (stretch)
Release: 9.7
Codename: stretch
Operating System: Debian GNU/Linux 9 (stretch
 Kernel: Linux 4.9.0-8-686-pae
 Architecture: x86"
1815514,2019-02-11 21:02:15 UTC,"Making all in examples
make[2]: Entering directory '/home/coco/geda-gaf/examples'
Making all in gTAG
make[3]: Entering directory '/home/coco/geda-gaf/examples/gTAG'
cd . && /home/coco/geda-gaf/xorn/src/command/gnetlist -g PCB -o gTAG-pcb.net gTAG.sch
/bin/bash: /home/coco/geda-gaf/xorn/src/command/gnetlist: No such file or directory
Makefile:642: recipe for target 'gTAG-pcb.net' failed
make[3]: *** [gTAG-pcb.net] Error 127
make[3]: Leaving directory '/home/coco/geda-gaf/examples/gTAG'
Makefile:518: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/coco/geda-gaf/examples'
Makefile:543: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/coco/geda-gaf'
Makefile:475: recipe for target 'all' failed
make: *** [all] Error 2"
1815514,2019-02-27 20:52:39 UTC,Hello Roland
1815515,2020-03-02 14:51:39 UTC,This issue was fixed in the openstack/mistral 10.0.0.0b2 development milestone.
1815515,2020-01-23 09:13:13 UTC,"Reviewed:  https://review.opendev.org/636583
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=c1c21d7cddca2f307e93f42b4758e64fcdf0a630
Submitter: Zuul
Branch:    master"
1815515,2019-02-13 10:08:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636583"
1815518,2019-08-20 01:33:02 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1815535,2019-02-12 00:00:06 UTC,This change was made by a bot.
1815535,2019-02-13 05:57:13 UTC,Are you able to find the last known good kernel in grub and boot into it to see if the problem exist? Please also reproduce the problem and attach your /var/log/kern.log to this bug in your next reboot. Thanks.
1815535,2019-02-13 06:17:36 UTC,The problem has mysteriously resolved itself.
1815539,2019-02-16 01:27:10 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/637341"
1815539,2019-02-21 00:02:29 UTC,"Reviewed:  https://review.openstack.org/637341
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4420b78c0151783b5e1acb0cfc060eb35713d0ae
Submitter: Zuul
Branch:    stable/rocky"
1815539,2019-04-04 14:19:15 UTC,This issue was fixed in the openstack/keystone 14.1.0 release.
1815543,2019-02-13 23:31:01 UTC,Yes can reproduce this easily. Sigh.
1815546,2019-09-30 22:06:39 UTC,"I'm glad to hear you were able to resolve the problem @maruino2. A proper fix is still needed however, because doing a move of a file from location A to location B after having just copied it from location C is highly inefficient. Better to copy from C to B without the intermediary A. Please look at the code copyfiles.py and examine how to handle the situation that is arising with your file system setup."
1815546,2019-09-30 16:52:49 UTC,I ran into the same bug and resolved it (at least for myself) by replacing os.rename() with shutil.move() in line 753 of renameandmovefile.py (version 0.9.17). I got the idea from https://stackoverflow.com/questions/42392600/oserror-errno-18-invalid-cross-device-link
1815546,2019-02-12 19:57:53 UTC,"the config file, modified back to the original location (/home/anarcat/Photos) which triggered the failure. current location is /srv/Photos and works."
1815546,2019-02-12 19:55:59 UTC,logfile with the errors
1815546,2019-02-12 19:38:44 UTC,"Please include in your bug report the log files, which are found in the log directory ~/.cache/rapid-photo-downloader/log. You can open this directory by clicking on the link in the ""Report a Problem"" dialog window. Please also include the configuration file found in the directory ~/.config/Rapid Photo Downloader/."
1815546,2019-03-29 04:13:16 UTC,"I'm puzzled by this bug. When I use python to create a temporary directory within a directory pointed to by a symlink on my system, it first follows the symlink and then creates the temp dir, which is exactly the behavior I expect. In your case, for some reason it has not done that. Instead, it has created a temporary directory in your home directory. That is unexpected. Is there some kind of permission issue at play here, such as a mount folder being owned by root and not your user?"
1815550,2019-04-08 06:02:39 UTC,(Using the stock gnome session for longer suggests that there may indeed be a separate memory leak bug; its memory use was up to 1GB RSS after a couple of hours. I'll file that separately if it continues)
1815550,2019-04-08 06:20:26 UTC,"> Turned off “Show the personal folder”; the problem remains.
"
1815550,2019-04-08 06:21:13 UTC,"> I've got the standard set of icons: 21 folder icons (apparently $HOME contains 21 folders), a text file icon, and the trash icon.
"
1815550,2019-04-08 06:36:34 UTC,"Also, does:"
1815550,2019-04-08 08:37:36 UTC,"On 8 April 2019 4:21:13 pm AEST, Daniel van Vugt <email address hidden> wrote:

>> I've got the standard set of icons: 21 folder icons (apparently $HOME
>contains 21 folders), a text file icon, and the trash icon.
>
>You mean $HOME/Desktop, right?
"
1815550,2019-04-08 09:15:28 UTC,"OK, that's a red flag. Those folders should not appear on your desktop."
1815550,2019-04-17 01:35:17 UTC,"Chris,"
1815550,2019-09-05 10:54:30 UTC,I think we might go via bug 1842904 before fixing this in disco.
1815550,2019-06-10 09:10:43 UTC,Hello!
1815550,2019-07-04 03:56:09 UTC,It looks like most (not all) of the leak is fixed in the next version 19.01.4:
1815550,2019-08-08 12:00:37 UTC,Fix proposed:
1815550,2019-08-16 04:56:26 UTC,Fixed in Debian (Ubuntu coming soon?):
1815550,2019-08-27 02:19:33 UTC,gnome-shell-extension-desktop-icons (19.01.3+git20190814.1-1) experimental; urgency=medium
1815550,2019-04-08 06:00:47 UTC,Turned off “Show the personal folder”; the problem remains.
1815550,2019-10-08 08:00:52 UTC,"Closing as wontfix for Disco, that's not a LTS serie and 19.10 is about to turn stable, for those who need the fix it's recommended to upgrade to the new serie"
1815550,2021-01-27 10:04:07 UTC,"Just retested the pathological case of this leak, which involves creating and deleting desktop files as fast as you can (thousands of times) via a script. In that case even the latest gnome-shell-extension-desktop-icons still leaks badly. So the fix I had hopes for is not enough:"
1815550,2019-05-12 22:02:26 UTC,Can confirm this bug also affects me.
1815550,2019-04-08 01:39:52 UTC,"Finally, how many and what type of icons do you have on the desktop when the problem is happening?"
1815550,2019-04-05 08:44:03 UTC,It appears the relationship between zsh and gnome-shell can be explained:
1815550,2019-04-07 23:15:09 UTC,"Yup! In the stock GNOME session I do *not* see the multi-second pause on the zsh prompt, nor does gnome-shell's RSS increase each prompt."
1815550,2019-02-19 03:38:46 UTC,"Chris,"
1815550,2019-02-20 10:56:36 UTC,Uninstalling all extensions did not seem to make a difference; the gnome-shell process is back up to 10G RSS after an hour.
1815550,2019-02-21 01:21:18 UTC,In that case I would agree with the theory this is likely nvidia-related (or a new regression).
1815550,2019-03-19 00:49:40 UTC,Another data point: it appears that pressing <enter> in a terminal window (tested both gnome-terminal and qterminal) at a zsh shell prompt (but not a bash shell prompt!) results in GNOME Shell being unresponsive for ~4s at 100% CPU and increasing RSS by ~50MB.
1815550,2019-04-02 06:46:46 UTC,confirming. I'm seeing the same regularly.
1815550,2019-04-03 15:03:33 UTC,Is this only on disco or is it observed on prior versions? I was planning to upgrade and have two systems with nvidia GPUs. On cosmic I cannot see the resident memory grow as described above.
1815550,2019-04-04 23:12:57 UTC,This is *not* specific to nvidia_drm.modeset=1¹. With KMS disabled gnome-shell still freezes for a second or two and its RSS grows by ~50MB each time a zsh prompt is displayed.
1815550,2019-04-05 07:43:48 UTC,This sounds important:
1815550,2019-04-04 01:51:12 UTC,Chris and Didier have both told me that they use the nvidia-drm.modeset=1 kernel parameter. But instead of using it to enable Wayland support they still use Xorg sessions. So that's worth checking to see if the problem is specific to nvidia-drm.modeset=1. If so then it would nicely explain why more Nvidia users never see this bug.
1815550,2019-04-05 08:51:52 UTC,What we might be achieving right now is drawing a line between multiple different bugs :)
1815550,2019-04-05 08:57:41 UTC,"I'm also mildly cautious about what difference bcachefs might have, due to Chris':"
1815550,2019-04-05 09:02:40 UTC,"Also, it sounds like avoiding zsh might avoid the majority of the problem here?"
1815550,2019-04-05 09:29:53 UTC,Please also try:
1815550,2019-04-05 10:26:08 UTC,"BTW, Didier is now using bug 1823301 instead."
1815550,2019-04-07 09:52:24 UTC,"Chris,"
1815550,2019-04-07 23:00:24 UTC,"Relevant bit of glxinfo:
...
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
...
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
...
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8192 MB
    Total available memory: 8192 MB
    Currently available dedicated video memory: 6393 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 418.56
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
...
Yup, it's all there."
1815550,2019-04-05 07:47:28 UTC,Ah. The above journal entries are from gnome-shell-extension-desktop-icons.
1815550,2019-04-08 01:38:13 UTC,"Chris, please try this:"
1815551,2019-02-16 20:52:41 UTC,You seem to have an ... interesting[tm] filename:
1815551,2019-02-24 23:28:38 UTC,"Sorry for the late respond didn't have time to get to this right away.
It is indeed very strange. I don't have the original log file from when I uploaded the bug report, but I reproduced the bug and found a line that matches what you were looking for. Please let me know if there is anything else you need that might help you in fixing this.
This is the line matching the second grep pattern from my audit.log file:"
1815551,2019-02-26 21:07:48 UTC,"# aa-decode 2F686F6D652F696C617972617A2F2E6A6176612F2E7573657250726566732F6A6574627261696E732F5F212821216367227021287D217D40226A21286B217C772277212738216221227021273A2165403D3D2F70726566732E786D6C
Decoded: /home/ilayraz/.java/.userPrefs/jetbrains/_!(!!cg""p!(}!}@""j!(k!|w""w!'8!b!""p!':!e@==/prefs.xml"
1815554,2019-10-02 09:50:19 UTC,mpi4py (2.0.0-3build4) disco; urgency=medium
1815561,2019-02-14 08:42:33 UTC,"Yes the touchpad works now by inserting hid.ignore_special_drivers=1
 just after ""quite splash"""
1815561,2019-02-14 05:07:48 UTC,Can you attach dmesg output to this bug when you boot with that kernel param added?
1815561,2019-02-13 08:04:23 UTC,"If you add hid.ignore_special_drivers=1 to the kernel command line, does your touchpad work? You can follow https://wiki.ubuntu.com/Kernel/KernelBootParameters on how to do that."
1815561,2019-02-12 07:30:10 UTC,This change was made by a bot.
1815561,2019-02-13 08:41:54 UTC,"Hello Anthony,
I passed the parameters as suggested but no difference. Touchpad doesn't
work.
However I realized that three fingers tap work s irrespective of adding
following:"
1815562,2019-02-12 08:00:08 UTC,This change was made by a bot.
1815568,2019-02-12 15:36:34 UTC,"This looks like an error in the VA driver. But regardless, please note that Wayland support is incomplete and experimental in VLC 3.0.x."
1815568,2019-02-12 19:41:25 UTC,"The error seems to be that sometimes the driver isn't found at all. That's why I was suspecting some kind of locking issue. But I should probably move back to Xorg, there are other Wayland specific bugs as well in gnome-shell/mutter."
1815568,2019-02-12 20:41:49 UTC,Note that vlc is also broken on gnome-shell with Xorg:
1815568,2019-02-13 15:07:14 UTC,This is another important bug that makes the current Xorg gnome-shell session noticeably broken when viewing fullscreen video in VLC:
1815568,2019-04-25 21:59:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815570,2019-02-13 11:41:47 UTC,Rocky branch currently holds the download.ceph.com packages back to luminous release during tests so there is no conflict with the UCA packages.
1815570,2019-02-13 12:17:20 UTC,Just to note:
1815572,2019-05-20 18:31:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815578,2019-02-16 20:38:17 UTC,"family= ""unknown(27)"" looks interesting[tm] - any idea what could have triggered it? (Might be a kernel issue.)"
1815580,2019-05-15 06:53:00 UTC,This bug was fixed in the package ubuntu-image - 1.7+19.10ubuntu1
1815580,2019-04-24 12:30:30 UTC,Fixed in master.
1815581,2019-02-12 17:48:31 UTC,"I tested again (vagrant ""ubuntu/bionic64"" box) running these commands first.
```
yum check-update -y || apt-get update -y
yum install git libffi-devel -y || apt-get install git libffi-dev -y
```"
1815585,2019-02-12 14:56:08 UTC,"The change in https://review.openstack.org/#/c/602694/ made this a little better by waiting, but I can confirm that this test still does fail occasionally."
1815585,2019-02-22 15:37:12 UTC,"I did some initial investigation on this. It looks that nova-compute received information to detach interface and told Libvirt to detach it:
http://logs.openstack.org/91/635691/1/gate/neutron-tempest-plugin-scenario-linuxbridge/3cc34c4/controller/logs/screen-n-cpu.txt.gz#_Feb_12_09_16_39_511365"
1815585,2019-02-25 10:52:13 UTC,"According to last comment. I also checked that port status was actually changed from ""ACTIVE to DOWN"" because there was event to nova send here:
http://logs.openstack.org/91/635691/1/gate/neutron-tempest-plugin-scenario-linuxbridge/3cc34c4/controller/logs/screen-q-svc.txt.gz#_Feb_12_09_16_41_263557"
1815585,2019-02-25 11:21:19 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/639067"
1815585,2019-03-04 16:36:49 UTC,"Reviewed:  https://review.openstack.org/639067
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=7451ad7fe0fede24c15e39ecd15e46dd6fbf4d86
Submitter: Zuul
Branch:    master"
1815585,2019-03-10 10:43:10 UTC,"It happened again. And indeed it confirmed what I wrote in my previous comments here. Port is ACTIVE but it's ""unbound"" and device_id is empty."
1815585,2019-03-10 10:43:54 UTC,I forgot to add link. It was confirmed in http://logs.openstack.org/52/640252/5/check/neutron-tempest-plugin-scenario-linuxbridge/89ad62c/job-output.txt.gz#_2019-03-08_10_26_10_209623
1815585,2019-03-24 08:31:50 UTC,Maybe it is somehow related to https://bugs.launchpad.net/neutron/+bug/1819446 but I will have to investigate that.
1815585,2019-03-26 17:01:55 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/647816"
1815585,2019-03-27 07:45:37 UTC,"Reviewed:  https://review.openstack.org/647816
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=5ddcf33322f1e257322369fff6416aa48c4214b9
Submitter: Zuul
Branch:    master"
1815586,2019-08-14 11:48:29 UTC,"Fixed in revision fb0fd825bab99199b2acae4dbed53afaa4117a50
https://git.launchpad.net/kicad/patch/?id=fb0fd825bab99199b2acae4dbed53afaa4117a50"
1815586,2019-08-14 09:11:31 UTC,"This is another example of us trying to be too smart.  If the user says ""print worksheet"" then we should print the worksheet.  If they blow up the scale by enough to push the worksheet off the page then it's off the page.  Same as would happen with the board if they're not printing the worksheet."
1815586,2019-03-25 17:57:53 UTC,"@John, I confirmed this behavior but I'm not sure this is actually a bug.  What I find odd is that when you enable print worksheet and fit to page, it doesn't actually fit the board to the page.  It fits the worksheet to the page which makes sense.  I don't think we should change this behavior.  However, we should give the user some indication that enabling the worksheet will ignore the board scaling."
1815586,2019-03-27 17:22:53 UTC,This is odd.  KiCad may be using the assigned paper size rather than the selected printer paper size when trying to determine if the worksheet is outside the print area.
1815586,2019-03-27 10:04:14 UTC,"@Wayne, sorry, I don't quite follow. I think the current behaviour with ""Fit to page"" is correct - it will fit whatever is shown (board or board+worksheet) to the page, which doesn't guarantee a fixed scaling factor."
1815590,2019-02-12 11:28:17 UTC,(see https://docs.docker.com/registry/configuration/#storage)
1815590,2019-06-14 12:03:17 UTC,PR: https://github.com/CanonicalLtd/docker-registry-charm/pull/37
1815590,2019-09-13 15:25:43 UTC,Released in rev 152 and higher:
1815592,2019-02-12 11:38:53 UTC,"I'd like to know if we're actually using the olddirs functionality right now, other than for removing old releases. Once we know that, I would propose using only st.st_mtime for the timestamp check. Checksums only care about the *contents* of the image, not the metadata. Move and link operations will only touch the st_ctime timestamp, so it would allow re-using the checksums in cases of image moves. Also, image moves and hard-links should be fairly safe."
1815592,2019-02-12 15:27:30 UTC,For the archival script I'm currently working around it by touching the *SUMS files after performing the move operation. But I think the implementation should really just look at mtime. Any reason for it to have to consider ctime?
1815594,2019-02-18 09:42:11 UTC,"Marked as incomplete as title says update member fails but description talks about image update, need more information on this."
1815594,2019-02-18 10:03:44 UTC,I meant glance member-update... Fixed it in the original description.
1815594,2019-03-18 14:05:44 UTC,"Some general information:  When v2 image sharing was implemented in Grizzly, the thinking was that making a call to keystone to verify that the ID of the member was a known project ID was too expensive, so it wasn't implemented.  The implication of this decision is that when you create an image member, glance will accept anything of the correct type, which is a JSON 'string' type:"
1815594,2019-03-18 14:07:57 UTC,@David: please read through the above and let us know if it explains what you're seeing.
1815594,2019-03-18 14:44:42 UTC,"Hi Brian,"
1815596,2019-02-13 01:23:16 UTC,"FYI, the title indicates [WIN64] but it also happens on win32 I use."
1815596,2019-02-12 19:02:49 UTC,"It seems to be Windows only, I took part in the discussion https://forum.kicad.info/t/kicad-5-0-2-pcbnew-inconsistent-footprint-selection/15179/8 and can affirm the bug on Windows 7 and Windows 10. However, I can't reproduce it on Linux (Kubuntu, KiCad with GTK3)."
1815596,2019-02-12 12:44:49 UTC,"I assume that you can't reproduce the Disappearing ""Clarify selection"" menu using ALT+LMB combination.
I will check in the evening on a second machine with latest nightly installed.
So far one another user on kicad.info forum confirmed the behaviour."
1815596,2019-02-12 12:24:40 UTC,"I cannot reproduce in the current 5.1RC (or 5.0.1, for that matter). Could still be platform or toolkit specific."
1815596,2019-02-12 13:00:05 UTC,I believe this may be a windows only bug.  I'm seeing it on my windows 10 system.  I have to use Alt+Shift+LMB to get the disambiguation context menu to stay visible.  The context menu disappears immediately if I use Alt+LMB.
1815597,2019-02-12 14:41:53 UTC,"Hi,"
1815599,2019-02-12 16:22:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1815599,2019-02-13 06:30:20 UTC,"I'm not sure what the exact problem is that's reported here.
Is it the string ""#:#:#:#"" itself that replaces the disk ID in case of an error with the disk/path.
And if so - which problem is it causing then?"
1815599,2019-02-13 07:59:19 UTC,"------- Comment From <email address hidden> 2019-02-13 02:58 EDT-------
These issue paths cannot be recovered for a long time by itself, if we lost other 2 healthy paths, data will be lost"
1815599,2019-03-22 06:33:40 UTC,"Some configurations are possible to face this and similar issues, please have a look here:
http://public.dhe.ibm.com/software/dw/linux390/lvc/zFCP_Best_Practices-BB-Webcast_201805.pdf"
1815599,2019-03-22 06:58:41 UTC,@JFH - As just discussed you have mentioned that you have discussed the existing tunables to Heinz Werner. Thanks for linking these here again to make sure that Shixm knows.
1815599,2019-03-22 07:06:26 UTC,"The loss of that path info suggests that it lost the knowledge about that.
I found very old bug 1032550 - the assumption there was that it would eventually be a kernel bug due to sysfs loosing the information multipath might need. But back then the actions on the bug stopped (I have no insight why as I wan't around at the time)."
1815599,2019-03-22 07:26:15 UTC,"I'll ask to get the SME's on zFCP pulled into this topic, too - so that this can be looked at from different angles ..."
1815599,2019-06-03 08:11:41 UTC,Changing to Incomplete until feedback from IBM SMEs ...
1815599,2019-07-15 09:49:56 UTC,"------- Comment From <email address hidden> 2019-07-15 05:42 EDT-------
Problem could not be reproduced within our last cycle testing on Ubuntu 18.04.2 4.15.0-51-generic.
This problem will be closed. New new bugzilla will be opended if the problem come up again.. Thx"
1815602,2019-06-05 15:13:10 UTC,"Using 3.28.5-0ubuntu1 it seems to work fine, browsing google, launchpad, clicking on url, using the history, opening the shell menu were done without issue, marking as verified"
1815602,2019-06-06 09:40:09 UTC,This bug was fixed in the package epiphany-browser - 3.28.5-0ubuntu1
1815602,2019-06-06 09:30:10 UTC,"The verification of the Stable Release Update for epiphany-browser has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815602,2019-05-28 19:57:51 UTC,Newer versions are in cosmic and disco
1815602,2019-05-28 21:52:29 UTC,"Hello Amr, or anyone else affected,"
1815607,2019-07-31 21:11:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815607,2019-08-22 14:43:41 UTC,This is due to a difference in the way GNU and BSD versions handle the -t argument. The BSD version assumes that it can add XXX if it likes to.
1815607,2019-08-22 14:45:13 UTC,https://unix.stackexchange.com/questions/30091/fix-or-alternative-for-mktemp-in-os-x
1815611,2019-04-23 23:57:03 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1815611,2019-06-23 04:19:14 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1815622,2020-02-28 19:32:24 UTC,We're seeing this behavior on 3.3.4.
1815624,2019-02-19 08:23:11 UTC,"Hello,"
1815625,2019-08-03 19:39:11 UTC,"--- 1.2.0 2019-08-03
  + Added ability to include DMARC policy in DMARC results
  * Updated references for new RFCs, ARC no longer experimental
  * Converted http references to https (thanks DKG)"
1815625,2019-02-13 01:48:55 UTC,"On Tuesday, February 12, 2019 03:23:39 PM you wrote:

> If there are better ways to submit patches (e.g. a ""merge request"" or
> the equivalent) i don't know how to do it on launchpad, which is why
> i've requested membership in this group, to do comparable cleanup work.
"
1815625,2019-02-12 15:23:39 UTC,"If there are better ways to submit patches (e.g. a ""merge request"" or the equivalent) i don't know how to do it on launchpad, which is why i've requested membership in this group, to do comparable cleanup work."
1815626,2019-11-04 14:09:32 UTC,"The verification of the Stable Release Update for geary has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815626,2019-11-04 14:09:22 UTC,This bug was fixed in the package geary - 0.12.4-4~ubuntu18.04.3
1815626,2019-10-30 16:37:51 UTC,I confirm that geary 0.12.4-4~ubuntu18.04.3 from bionic-proposed is working nicely in sending and receiving emails.
1815626,2019-10-25 10:15:29 UTC,"Hello Amr, or anyone else affected,"
1815626,2019-10-08 12:50:02 UTC,(unsubscribing sponsors since the change have been uploaded)
1815626,2019-10-02 22:48:32 UTC,"I have made some tiny tweaks to the changelog itself, but as requested I have merged in #3 with #11 and successfully built the package against all target architectures here https://launchpad.net/~ubuntubudgie-dev/+archive/ubuntu/geary-test/+packages"
1815626,2019-09-26 21:18:01 UTC,Please re-upload the package incorporating the modifications in comment #11 now that Cosmic is dead.
1815626,2019-05-25 04:52:41 UTC,"The changelog in the now rejected upload to bionic-proposed claimed to fix bug #1779574. Well, it would not have done so. Actually it would have resulted in geary being shipped untranslated. It's not practicable to enable Ubuntu's language packs retroactively."
1815626,2019-04-20 21:01:31 UTC,"Hi Amr, thanks for your work on this!"
1815626,2019-05-24 23:49:49 UTC,"It would be trivial to upload the package with a version number that sorts properly less than the version in cosmic so that upgrades work without issue (or even to base this on the cosmic version, since the changes from 0.12.4-2 and 0.12.4-4 don't seem relevant on bionic).  We also do not want to leave this upload in the queue for months until cosmic has reached EOL.  So I am rejecting this package from the queue now.  It can be reuploaded at any time with a proper version number, or in July with the same version number."
1815626,2019-05-21 12:23:41 UTC,No one cares about Cosmic at the moment. So let's wait until it's EOL.
1815626,2019-05-15 13:13:57 UTC,"This would place the version of geary higher in Bionic than in Cosmic, which will cause problems as users upgrade to Cosmic. One way to resolve this would be to also update (and verify) Cosmic, or wait until Cosmic is EOL."
1815626,2019-04-21 15:35:51 UTC,Uploaded to Bionic with minor changelog edits.
1815626,2019-04-04 16:21:27 UTC,"The attachment ""geary_0.12.0-1ubuntu1_0.12.4-4~ubuntu18.04.1~ppa1.diff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1815626,2019-02-13 08:25:42 UTC,"Hey, 0.12.4 is indeed a bug fix release. It would be good to have that in Bionic."
1815626,2019-02-12 15:38:12 UTC,"I'm subscribing Michael Gratton, the upstream maintainer, maybe he could say something here, whether this is a bug-fix release or not."
1815626,2019-05-24 23:50:09 UTC,"An upload of geary to bionic-proposed has been rejected from the upload queue for the following reason: ""Wrong version number for upload which sorts > cosmic""."
1815630,2019-09-19 14:54:17 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1815631,2020-04-14 11:24:19 UTC,"Reviewed:  https://review.opendev.org/718509
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_horizon/commit/?id=abbfeb0529520bc047db44fb550df80822b7fae6
Submitter: Zuul
Branch:    master"
1815631,2020-04-08 16:10:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/718509"
1815631,2019-10-11 13:00:24 UTC,"+1
Got the ""Unable to create the image."" error message in Horizon Dashboard and got to modify this option to upload images."
1815631,2020-04-08 16:03:41 UTC,"Actually I do think, that ""remote"" is not valid option here. As according to [1] only ""direct"", ""legacy"" or ""off"" can be set here."
1815632,2020-09-23 12:18:54 UTC,"As long as it is still installed by default at installation time in order to prevent customers to have to install it manually as an extra steps, when needing support from us."
1815632,2020-09-23 13:32:56 UTC,"FYI server-ship isn't used anymore to build an ISO or anything like it (only server-ship-live is).
We recently migrated everything off server-ship as it will likely go away in the future."
1815632,2019-02-12 16:37:47 UTC,"+1 from me on removing from server-ship and supported, since it's in server.."
1815634,2019-05-14 13:58:42 UTC,"It's unclear to me whether this is an issue w/ the charm, or an underlying networking issue. At the very least, however, we should have a test that validates API access so that we can rule out charm issues."
1815635,2019-02-12 17:57:07 UTC,There is a similar issue in Nova because it has it's own implementation of get_server_version: https://github.com/openstack/nova/blob/78d6aca9a6cfb25ac180e28dc519fb76d22a2314/nova/volume/cinder.py#L104-L146
1815635,2019-03-14 17:32:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/643405"
1815635,2019-03-19 17:19:32 UTC,"Change abandoned by Nikita Gerasimov (<email address hidden>) on branch: master
Review: https://review.openstack.org/643405"
1815635,2020-03-18 15:39:54 UTC,"Basically duplicate of https://bugs.launchpad.net/horizon/+bug/1744670
Should be fixed by:
- https://github.com/openstack/horizon/commit/285c51f7e1b27a786fa9684abdc489998285b4e2
- https://review.opendev.org/#/c/675894/"
1815637,2019-04-30 16:17:00 UTC,"From some experiments, it looks like Xenial's python3-libvirt may be problematic, old or need API changes. Trusty doesn't have the package. This may cause some issues with supporting older Ubuntu releases in the PPA, though it might be possible with dual compatible code and/or some smarter packaging or release process."
1815637,2019-02-12 16:43:50 UTC,This probably needs:
1815637,2019-02-15 15:03:33 UTC,"ack. a quick test gets that to actual python3 problems.  ie, the build
change is correct, but upstream needs some changes. thanks."
1815644,2019-02-13 14:30:53 UTC,The attached patch fix this issue.
1815644,2019-02-16 18:15:36 UTC,Fix commited x1.3.1-21.
1815649,2019-02-26 13:34:55 UTC,Vim still does not open
1815649,2019-05-24 18:26:13 UTC,What lead you to use the command 'vim'? Was it listed in software-center? Was it something you read online?  Thanks in advance.
1815649,2019-05-23 08:23:14 UTC,Sebastien's information is correct (Thanks!) Command 'vim.tiny' works. Also 'vi'.
1815649,2019-05-23 07:49:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815649,2019-02-26 13:36:47 UTC,As synaptci it is installed
1815649,2019-02-15 18:01:02 UTC,When entering F1 the following information appeared:
1815649,2019-02-12 21:58:16 UTC,Follow the Requested:
1815649,2019-02-15 17:35:06 UTC,"the command is ""vim.tiny"" not ""vim-tiny"", but yeah it's confusing that it matches ""vim"" in the graphical software"
1815649,2019-02-15 15:24:35 UTC,"Vim appears installed, but clicking Exit by store or executing the command does not open it.
See the attachments, please."
1815649,2019-02-15 14:28:22 UTC,What doesn't work? What happen if you type 'vim.tiny' on a command line?
1815649,2019-02-12 23:00:04 UTC,"Hi, Sebastien Bache"
1815649,2019-02-12 22:41:57 UTC,"the log shows that only 'vim-tiny' is installed (and that's what Ubuntu installs by default), the 'vim.tiny' command should work? It's a bit misleading that gnome-software shows 'vim' as installed though"
1815649,2019-07-24 04:17:41 UTC,[Expired for vim (Ubuntu) because there has been no activity for 60 days.]
1815649,2019-02-15 17:49:20 UTC,"Hi,"
1815649,2019-02-12 20:07:10 UTC,"What's the output of that command?
- dpkg -l | grep vim"
1815656,2019-02-13 16:38:55 UTC,Confirmed in EG 3.1.8.
1815666,2019-02-12 22:07:58 UTC,"Well, that's grub2 inside centos7 ..."
1815666,2019-02-13 00:19:31 UTC,Both grub2 and lvm2 have been updated since the last image build but nothing has stands out
1815666,2019-02-13 00:31:21 UTC,"I attached strace to the running $(vgs --options vg_uuid,pv_name --noheadings --separator :) process. Its stuck in the following loop. /run isn't being bind mounted into the target environment."
1815666,2019-02-13 00:53:29 UTC,Patching[1] Curtin to bind mount /run fixes CentOS 1901 deployments to both BIOS and UEFI systems.
1815666,2019-03-06 14:15:08 UTC,"This bug is fixed with commit 0dc77168 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=0dc77168"
1815666,2019-05-22 14:21:52 UTC,"This bug is believed to be fixed in curtin in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1815666,2019-02-12 20:34:20 UTC,It looks like GRUB probing for LVM is what is hanging.
1815676,2019-02-13 00:29:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636505"
1815676,2019-02-14 00:18:34 UTC,"Change abandoned by Swaminathan Vasudevan (<email address hidden>) on branch: master
Review: https://review.openstack.org/636505
Reason: Abandon this patch, since _external_gateway_removed will not clean the snat_namespace."
1815682,2019-02-12 22:41:37 UTC,typo :)
1815682,2019-10-07 07:38:29 UTC,"Tested with the last stable release 0.49, it works:"
1815684,2020-04-28 13:09:32 UTC,@ddstreet did you have a chance to look at this?
1815684,2020-04-18 12:57:00 UTC,"Hi Dan,"
1815684,2020-04-16 15:33:19 UTC,"> We have released 3.7.3, what should we do at this point, get first this 3.7.2 uploaded or skip it and try to get 3.7.3 in?
"
1815684,2020-04-16 14:10:01 UTC,"Unsubscribing ubuntu-sponsors, I will sponsor when updated pkg is ready."
1815684,2020-04-16 14:24:03 UTC,"Hi Dan,"
1815684,2020-04-16 14:09:06 UTC,"> I'm marking this as won't-fix for cosmic, since it's EOL.
"
1815684,2019-06-26 12:40:45 UTC,Updated debdiff for Ice 3.7.2 bionic backport
1815684,2019-06-26 12:53:21 UTC,"Hi Simon,"
1815684,2019-06-26 12:42:10 UTC,Updated debdiff for Ice 3.7.2 cosmic backport
1815684,2019-06-25 16:07:00 UTC,"Hello José, thanks for adjusting the bug description. Everything looks good there."
1815684,2019-04-24 08:14:01 UTC,"Hi Simon, I have updated the description as requested"
1815684,2019-04-20 20:03:10 UTC,"Hello José, thanks for your work on this!"
1815684,2020-04-16 14:07:57 UTC,"@y-jose, hello and sorry for the delay."
1815688,2019-02-12 23:25:36 UTC,Pull request: https://github.com/juju/juju/pull/9689 to install the juju-db snap
1815688,2019-04-11 19:58:37 UTC,given the PR linked is this ok then? Marking incomplete.
1815690,2019-02-13 09:20:51 UTC,"Hi,"
1815690,2019-02-13 22:16:09 UTC,Thanks for the quick reply. It's great to hear that this is supported.
1815691,2019-04-08 17:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1815691,2019-06-08 04:17:50 UTC,[Expired for linux (Ubuntu Disco) because there has been no activity for 60 days.]
1815691,2019-04-08 16:50:07 UTC,"Given the options shown in firmware and switching to AHCI fixes things as per xnox's comments; this is squarely a ""kernel"" issue -- one we can't really fix in ubiquity in any case."
1815691,2019-06-08 04:17:48 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1815691,2019-02-27 17:48:19 UTC,I switched the chipset SATA mode to AHCI and then the disk was detected by the Ubuntu 19.04 installer.
1815691,2019-02-14 16:49:42 UTC,"Can you please go into the bios settings; find the entries for the hard-drive and change the setting to present the drive as ""ACPI"" rather than ""RAID""."
1815691,2019-02-27 17:49:41 UTC,I got the photos and comments screwed up but you know what I mean right?
1815691,2019-02-27 17:47:26 UTC,"The drive was not actually presented as RAID but as ""Intel RST Premium With Intel Optane System Acceleration""."
1815691,2019-02-14 16:50:10 UTC,See syslog:
1815693,2019-11-21 08:42:59 UTC,I have crashes from OOM reaper for Kubuntu 19.04:
1815693,2019-07-22 04:25:40 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1815693,2019-07-09 16:42:17 UTC,"I'm still having issues with Xorg memory consumption on 19.04.
- it is somehow connected with sleep/wakeup of the system
- it is same for nvidia and intel graphic
- it is same whenever I call pm-suspend or close the lid
- uptime does not matter"
1815693,2019-06-03 16:05:43 UTC,Yesterday I upgraded to Ubuntu 19.04 and this issue seems to finally be resolved for the configuration I described in the initial report.
1815693,2019-05-13 21:20:57 UTC,"Hello,"
1815693,2019-05-12 11:39:51 UTC,"Hi everyone,
  I encountered the same problem after updating from kubuntu 17.10 to kubuntu 18.04 (no virtual box).
Infact after the update, checking the xorg virtual size memory with 'ps aux', i can see that it keeps growing. Even using the 'free' command the buff/cache field continues to grow.
Even when booting directly from a USB stick (before installation) with kubuntu18.04 the problem persists."
1815693,2019-03-25 20:51:58 UTC,"This bug also affects me. My computer has an AMD R9 280x GPU, a 16 gigs RAM, as well as a Core i7 processor. The memory allocated to Xorg triples and sometimes takes up all the available RAM when switching from themes, as from a dark theme to a light theme for instance. Kubuntu 18.10 with backports ppa is enabled and installed on the computer."
1815693,2019-03-15 00:37:14 UTC,"Thank you for the suggestion.
I tried enabling 3D-acceleration.
But there is no difference."
1815693,2019-03-11 11:13:46 UTC,"I also opened a bug report for Mesa (https://bugs.freedesktop.org/show_bug.cgi?id=109958) as the glxgears problem occurs on different distributions, not just (K)ubuntu."
1815693,2019-03-11 09:27:20 UTC,I might have found the same or a similar problem and a simple way to reproduce this issue using glxgears. This works even on some real hardware systems (depending on the graphics driver which is used).
1815693,2019-03-09 04:27:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815693,2019-02-16 16:05:05 UTC,According to this stackexchange thread
1815693,2019-03-25 20:55:17 UTC,"It's unlikely that its a bug affecting the current distributions of Mesa, as I compile and install newer versions of Mesa every day from the Obilaf ppa."
1815694,2019-02-15 08:13:52 UTC,"1) I installed this package:
sudo apt install adwaita-icon-theme-full"
1815694,2019-02-15 07:34:39 UTC,you also need this package https://packages.ubuntu.com/bionic/adwaita-icon-theme-full
1815694,2019-02-13 13:14:46 UTC,Note how the reporter runs Linux Mint though.
1815694,2019-02-13 13:04:40 UTC,I seem to remember I also had this problem...
1815694,2019-02-13 13:30:22 UTC,"Yeah, that's definitely a concern.  I had a very quick dig in the Inkscape code at the time but didn't dwell on it.  @Jabiertxof has been working on Icons recently... maybe he can advise?"
1815696,2019-02-13 04:16:07 UTC,Do you have a constraint on what spaces you want those units deployed to?
1815696,2019-06-11 04:17:30 UTC,[Expired for juju because there has been no activity for 60 days.]
1815697,2019-02-13 09:25:46 UTC,"Thanks for reporting this, I do change my max_retries value in devstack during testing to avoid long waits."
1815697,2019-02-13 13:44:56 UTC,I was hoping that maybe Dan's change here would help with the API startup issue:
1815697,2019-04-28 20:22:58 UTC,"Reviewed:  https://review.opendev.org/649197
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ae659668b5679cf7223474193d3b9a584dd3f016
Submitter: Zuul
Branch:    master"
1815697,2019-09-24 17:20:35 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/684405"
1815697,2019-10-01 23:36:12 UTC,"Reviewed:  https://review.opendev.org/684405
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7d54f91e9f5782413807b284a77b3f34f5551fa0
Submitter: Zuul
Branch:    stable/stein"
1815698,2019-02-13 10:19:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815698,2019-03-13 04:29:45 UTC,Both these packages are reported as broken after both a fresh install and as an upgrade from 16.04.
1815699,2019-04-22 20:49:55 UTC,"@Ivan Kurnosov: If it's possible to detect being run inside a container I would welcome a patch for the maintainer scripts to do the necessary adjustments automatically, as I don't use containers myself (yet)."
1815699,2019-04-22 18:47:24 UTC,"Please assist. I need a work-around, and can't figure out what to do:
https://unix.stackexchange.com/questions/513874/ejabberd-victum-of-systemd-security-enhancements"
1815699,2019-04-22 21:04:53 UTC,@Philipp Huebner
1815699,2019-04-22 17:52:07 UTC,So what are the exact steps necessary to get it running in a Linux container?
1815699,2019-02-13 02:28:33 UTC,"Ok, found it:"
1815699,2019-02-13 01:45:06 UTC,It looks like it only happens inside linux containers (lxc) :-(
1815699,2019-04-22 17:52:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815705,2019-02-13 03:42:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636544"
1815719,2019-02-13 09:38:08 UTC,https://github.com/juju/juju/pull/9745 is a PR against 2.5 to fix this behavior.
1815719,2019-02-13 09:46:49 UTC,Note that this seems to raise the priority of bug #1814735
1815719,2019-02-13 19:49:02 UTC,https://github.com/juju/juju/pull/9748 merges the fix into 2.6
1815721,2020-09-28 07:15:04 UTC,"Hello as far as I can tell, there is a major problem with PLIC implementation. When decompiling DTB on virt board with X harts, I see that hartid 0 has MEI and SEI, hartid 1 has MEI and SEI, etc... But when configuring context 1 (hartid 0 SEI) no interrupt is generated, but context 0, 2, 4 etc... work. So for me the problem is within PLIC or RISC-V implementation... If anyone wants to correct it, I can help. Best regards. Serge Teodori"
1815721,2020-11-19 20:24:54 UTC,I'm going to close this bug as it seems like the issue that RTOS Pharos raised is not an issue.
1815721,2020-03-24 10:35:08 UTC,"On Tue, Mar 24, 2020 at 4:20 PM RTOS Pharos <email address hidden> wrote:

>
> Hi,
>
> After some debugging (and luck), the problem (at least in the Virt
> board) was that the PLIC code inside QEMU addresses the core x 2 instead
> of just the core (core=hart). That is why it worked for core 0 (0x2 = 0)
> but for core 1 it has to address the PLIC memory area for core 2.
>
> For example, the interrupt enable address for core 1 starts at offset
> 0x002080 (see https://github.com/riscv/riscv-plic-spec/blob/master
> /riscv-plic.adoc) but we actually have to change the enable bit for core
> 2 (at 0x002100) to make to work for core 1.
"
1815721,2020-03-24 08:14:36 UTC,"Hi,"
1815721,2020-03-25 17:04:44 UTC,"Thank you for the explanation. I actually built it for ""Virt"" machine. I'll try the ""sifive_u"" when I can."
1815724,2019-05-14 07:57:28 UTC,Marking as invalid as it is not reproducible anymore
1815726,2019-02-18 08:48:13 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/637491"
1815726,2019-02-19 07:05:42 UTC,"Change abandoned by Sagar Waghmare (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/637491"
1815726,2019-02-27 08:26:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639591"
1815726,2019-10-14 14:15:09 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/639591
Reason: This was completed in change Iff2a23e09f2c5330b8fc0e9456860b65bd6ac149 so I'm abandoning this"
1815732,2019-02-21 14:04:37 UTC,I have hit the very same error.
1815732,2019-05-09 22:14:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815732,2019-03-26 13:04:05 UTC,"I have same problem, clients (mqttfx or java with paho) can not connect to mosquitto with same error if option acl_file is used.
No problem with mosquitto 1.5.8-0mosquitto1~bion from ppa."
1815732,2019-02-27 09:57:30 UTC,I've re-built 1.4.15-2ubuntu0.18.04.1 from source locally and I get the same connect issue.
1815732,2019-02-13 10:23:29 UTC,I see that the acl handling has been changed.
1815732,2019-02-13 10:05:13 UTC,mosquitto.conf is attaced
1815732,2019-02-13 10:10:07 UTC,/etc/mosquitto/users.acl is attached
1815732,2019-02-13 10:09:44 UTC,local.conf is the only config file inside /etc/mosquitto/conf.d/
1815732,2019-02-13 10:07:54 UTC,/etc/mosquitto/conf.d/local.conf is attached
1815732,2019-02-13 09:57:06 UTC,Can you share what config you are using?
1815732,2019-02-13 10:13:11 UTC,"users.pwd does *not* contain any empty lines or comments
and each line *does* contain the "":"" character"
1815733,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1815733,2019-04-25 06:49:14 UTC,"Hi,"
1815733,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1815733,2019-05-20 14:01:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1815733,2019-05-14 19:03:14 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1815733,2019-05-03 15:43:28 UTC,But i don't see changes for linux-4.15.
1815733,2019-05-03 12:47:45 UTC,"Thanks, i see it is fixed in 5.0.0-14 bionic hwe-edge kernel."
1815733,2019-05-02 07:44:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1815733,2019-03-18 09:33:22 UTC,"Hello, colleagues,
These patches are merged into linux-5.1-rc1 now.
Is it ready to be backported to 4.15 ubuntu kernel?"
1815733,2019-02-13 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1815733,2019-02-22 11:36:22 UTC,"We can still put it into Disco (19.04)'s kernel (v5.0) and see how it goes.
If no regression happens for a while, we can back port it to v4.15."
1815733,2019-03-11 16:44:48 UTC,This bug was fixed in the package linux - 5.0.0-7.8
1815733,2019-02-21 14:48:14 UTC,Seems to be not that trivial without commit a79050434b45959f397042080fd1d70ffa9bd9df.
1815733,2019-02-21 14:48:24 UTC,A test kernel can be found at https://people.canonical.com/~khfeng/lp1815733/
1815733,2019-02-13 12:24:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1815733,2019-02-22 08:09:54 UTC,Thanks for pointing that out. I thought they belong to the same series.
1815733,2019-02-22 10:15:10 UTC,"I'd like to wait till they at least land to v5.1-rc and get more thoroughly test.
I'll request an SRU once they are there."
1815733,2019-02-21 15:30:28 UTC,"Hi, thank you!
0002-block-avoid-setting-none-scheduler-if-it-s-already-n.patch - looks good."
1815733,2019-02-22 09:30:57 UTC,I've tested this kernel - there's no latency spike when setting none scheduler while it's already none - nice.
1815734,2019-02-13 09:56:16 UTC,Somebody is defacing the URLs in my initial bug description!
1815734,2019-03-20 17:53:18 UTC,Sure. This seems like a simple fix / enhancement.
1815734,2019-12-02 03:34:11 UTC,"just got burned by this.  could not figure out why it wouldn't work, spent some time banging head.  there's no error emitted, just fails to produce anything."
1815734,2020-05-13 10:08:22 UTC,"In a discussion upstream the .yml file extension was rejected, because it isn't part of the YAML standard:
https://github.com/CanonicalLtd/netplan/pull/106"
1815735,2019-02-13 09:54:57 UTC,"Indeed. When using many species and/or LDA+U, etc, the pool might overflow.
The fix is relatively straightforward, by using a re-sizable allocatable array.
We could write an ad-hoc piece of code, or take the opportunity to write a 'bud' container
for re-sizable arrays."
1815738,2020-07-01 11:50:21 UTC,"Hello,"
1815744,2020-01-03 17:39:15 UTC,moving to new tools to build packages
1815744,2019-08-25 11:08:07 UTC,"Change abandoned by Sagi Shnaidman (<email address hidden>) on branch: master
Review: https://review.opendev.org/636588
Reason: because long time passed since last update"
1815744,2019-04-23 22:50:32 UTC,"Reviewed:  https://review.opendev.org/654460
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=c6478adc8666c6ba3e0d8c92bf133b9da143614f
Submitter: Zuul
Branch:    master"
1815744,2019-04-22 14:15:38 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/654460"
1815744,2019-04-15 19:10:24 UTC,Lowering to high as it's not breaking anything at the moment.
1815744,2019-02-22 06:57:30 UTC,You have to look at patchset 2 where we have the Depends-On to github -> https://review.openstack.org/#/c/636511/2
1815744,2019-02-21 18:44:20 UTC,I see in https://logs.rdoproject.org/11/636511/5/openstack-check/tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001/93b8ab2/
1815744,2019-04-09 12:26:52 UTC,Being worked on here: https://review.openstack.org/#/c/636588/
1815759,2019-03-15 16:34:38 UTC,"The actual driver is in the kernel, which in your case is ancient"
1815759,2019-03-16 10:20:16 UTC,"I tried in Xubuntu 18.04 with HWE, kernel 4.18.0-16-generic,
and I get image on external display via HDMI."
1815759,2019-03-16 10:32:59 UTC,But hardware acceleration does not work and image flickers in Kodi during playback and in use unlike with nvidia driver.
1815759,2019-05-16 04:17:24 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1815762,2019-07-05 19:05:02 UTC,"No, we upgraded to a version of openvswitch that didn't work, it kept busylooping and didn't actually handle any packets - so we reverted, but connections was left in this disconnected state."
1815762,2019-07-05 19:05:33 UTC,"(note, we use the fact that nova will set them up if they are missing - but it will not do a small sanity check)"
1815762,2019-07-03 16:25:24 UTC,Hello Ian:
1815762,2019-06-14 00:13:09 UTC,"this might be somthing that could be added to the exsiting
neutron-ovs-cleanup script
that is generated by this entry point https://github.com/openstack/neutron/blob/master/setup.cfg#L49
and impmeneted here https://github.com/openstack/neutron/blob/master/neutron/cmd/ovs_cleanup.py"
1815762,2019-06-14 08:20:13 UTC,Is this script run on each startup? The issue is that nothing will work until it's been run.
1815765,2019-02-13 16:07:48 UTC,Is it possible to use the existing templating system for this purpose (File > New > Project from Template)? I've used templates (TI Launchpad/Boosterpack) but haven't dug deeper into what a template can do.
1815765,2019-02-13 16:19:30 UTC,It probably should be added to the default project file (kicad.pro) and the code used to create a new project.  It makes more sense to do it there than the templates because templates have their own specific requirements.
1815765,2019-02-15 09:50:36 UTC,"It should be done with user templates system anyway, because it's highly related ""per user""."
1815771,2019-02-13 14:58:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636645"
1815771,2019-05-29 23:32:48 UTC,"Reviewed:  https://review.opendev.org/636645
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=479a2a0afaeb505c371ee97a1f2fbc1b11e3cef1
Submitter: Zuul
Branch:    master"
1815771,2019-09-27 09:10:55 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1815773,2019-02-13 19:34:25 UTC,"Juju tracks a list of authorized keys. You can update them with 'juju
add-ssh-key' which will change what keys we set in authorized_keys on all
machines in the model."
1815773,2019-06-27 08:53:05 UTC,"As per comment # 1, this functionality is already provided."
1815774,2019-02-14 19:33:52 UTC,"Confirmed, that's fixed with that update"
1815774,2019-02-14 16:22:02 UTC,gdb 8.2.50.x handles this.
1815774,2019-02-13 21:03:48 UTC,The pointed commit is in 2.32 (see https://sourceware.org/bugzilla/show_bug.cgi?id=23919 for details) but that seems not enough since the disco-proposed version seems to not fix the issue from local testing
1815774,2019-02-13 18:14:37 UTC,An example of apport's behavior in this situation can be found in https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815703.
1815774,2019-02-13 18:04:13 UTC,"The retracers do not treat this as a failure because apport returns 0 when retracing the crash and that's because gdb also returns 0 as I believe this is just a warning from gdb. That being said there is no record of this failure in the retracers and it would not have been noticed if not for seb128, so there is some room for improvement in how the retracers / apport handle this situation."
1815774,2019-02-14 05:41:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815780,2019-09-12 14:16:47 UTC,"Does this bug still occur?
Can you check with latest code and provide Ansible deployment logs and docker logs, not just two lines?"
1815780,2019-11-12 04:18:30 UTC,[Expired for kolla because there has been no activity for 60 days.]
1815782,2019-02-13 17:01:54 UTC,The account in question has all the things that should trigger 2fa:
1815782,2019-02-13 19:45:37 UTC,"That is correct I was a member of ~canonical, but am not any more."
1815783,2019-02-13 17:48:11 UTC,Submitted a trivial patch for review: https://code.launchpad.net/~vultaire/graylog-charm/+git/graylog-charm/+merge/363145
1815783,2019-04-20 11:34:02 UTC,"LP let's you link MPs to bugs, which I've just done."
1815783,2019-05-16 08:08:57 UTC,Marking as fix released since I've just released cs:graylog-28
1815784,2019-02-14 02:18:26 UTC,I spent some time today looking at this.
1815784,2019-09-19 14:59:16 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1815786,2019-10-13 19:34:11 UTC,"This is Bzr probing for a Git repository, but failing because launchpad replies with a 500."
1815788,2019-02-14 21:04:48 UTC,Can you confirm storage is working correctly for you? Does the system you are experiencing this on have Intel SGX? Upstream recently committed a patch [1] to prevent a segmentation fault when using Intel SGX.  Can you try building lshw from source[2] and see if you can reproduce the issue?
1815788,2019-02-20 17:57:04 UTC,"I've moved one of the nodes out of maas control and performed a fresh install. The storage subsystem seems to be working fine (it's an old plain sata I controller). The system is an old ibm X3455, older than SGX, and the CPUs are AMD Opterons 2218."
1815788,2019-02-22 13:44:16 UTC,"Just for completeness, the version tested is the actual last commit, with ID 40e8f907cc36ab8b904d8606f3109cfc27c1569b"
1815788,2019-02-26 22:55:19 UTC,Took contact with Lyonel Vincent in order to report this bug to upstream.
1815788,2019-05-19 04:17:28 UTC,[Expired for lshw (Ubuntu) because there has been no activity for 60 days.]
1815788,2021-01-27 12:09:16 UTC,"We are a few versions further, of everything, but I'm still having issues with (nearly identical) HPE Bl460gen7 hosts, some of which fail on the lshw step, others don't. Did anyone get an insight on how to solve this? Or work around it?"
1815791,2019-03-24 23:39:17 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1815791,2019-03-21 15:59:10 UTC,"Reviewed:  https://review.openstack.org/640772
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=81b0e5a0680883d68d12253af64f8e10200df746
Submitter: Zuul
Branch:    stable/rocky"
1815791,2019-03-22 03:43:37 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1815791,2019-03-02 02:36:49 UTC,"Reviewed:  https://review.openstack.org/636699
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=19cb8280232fd3b0ba0000a475d061ea9fb10e1a
Submitter: Zuul
Branch:    master"
1815791,2019-02-18 17:23:03 UTC,Patch is here: https://review.openstack.org/#/c/636699/
1815791,2019-03-04 14:25:11 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640772"
1815793,2019-02-14 14:41:57 UTC,"It seems that to fix this https://github.com/openstack/nova/blob/c6218428e9b29a2c52808ec7d27b4b21aadc0299/nova/api/openstack/compute/hypervisors.py#L393 should be changed to https://github.com/openstack/nova/blob/5a09c81af3b438ecbcf27fa653095ff55abb3ed4/nova/objects/instance.py#L1377-L1383, providing both compute_node.host and compute_node.hypervisor_hostname"
1815793,2019-02-14 21:16:20 UTC,More details in the IRC discussion about this:
1815798,2019-02-13 21:45:57 UTC,"Hmm, ok. The solution is to remove the ""if"" stuff."
1815798,2019-02-15 09:44:41 UTC,"Thank you so much. Your advice was much useful.
Sincerely yours,
Ali Nourblin
Master of Information Technology,
Nourblin.com"
1815799,2019-06-03 16:34:45 UTC,"Reviewed:  https://review.opendev.org/662479
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=95ace7cf8daf4ff935ff6df877554fdfddef9e4a
Submitter: Zuul
Branch:    stable/stein"
1815799,2019-09-27 09:03:49 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1815799,2019-06-18 03:40:33 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1815799,2019-06-14 02:56:56 UTC,"Reviewed:  https://review.opendev.org/662584
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1ed3f8f9e487c233fdf714edad57d126fe6b1cd7
Submitter: Zuul
Branch:    stable/rocky"
1815799,2019-06-06 06:23:43 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1815799,2019-05-31 22:05:27 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/662584"
1815799,2019-05-16 18:48:33 UTC,"Also hitting this, on Rocky release. It was pretty obvious, not sure how we've not seen it sooner."
1815799,2019-05-30 21:59:22 UTC,"Reviewed:  https://review.opendev.org/659809
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=060e42b7fd185bf3b827b7aa5c9ab6131f6a21d7
Submitter: Zuul
Branch:    master"
1815799,2019-05-31 14:26:37 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/662479"
1815799,2019-03-14 22:41:14 UTC,"In this specific case, it is not needed, Ironic has long nuked the field. I'll put up a patch to gracefully handle this."
1815799,2019-03-14 23:03:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/643484"
1815799,2019-03-14 21:26:34 UTC,I'm not sure what nova can do about this besides waiting / retrying the delete of the ironic node before giving up. The libvirt driver has some retry stuff in it:
1815799,2019-05-17 14:31:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659809"
1815799,2019-05-30 19:40:02 UTC,"Change abandoned by Julia Kreger (<email address hidden>) on branch: master
Review: https://review.opendev.org/643484"
1815801,2019-03-06 21:00:14 UTC,"It appears the new RBAC feature (currently beta) has introduced an Operator role, that solves this issue.  This can be closed."
1815801,2019-09-19 14:54:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1815815,2021-02-12 22:46:58 UTC,"Oops, step 1 above shouldn't say Even Branches, just Example Consortium"
1815815,2021-02-12 22:46:11 UTC,"Thanks, Mike. That does make sense to me for the actual search results. To test that, I deleted the holdings for BR2 and BR4 from one of the records, then tested to be sure that limiting the search results to Even Branches didn't bring in that record - that part works great."
1815815,2021-02-12 21:34:53 UTC,"Hi Terran,"
1815815,2021-02-12 20:31:32 UTC,Testing on the festivus test server during feedback fest:
1815815,2021-02-09 21:16:19 UTC,"I've added a commit to this branch to facilitate testing by creating two Concerto-stock library groups:
 * A global library group containing ""Non-branches"", the test bookmobile and sub-library
 * A non-global library group containing the even numbered Concerto branches, Example Branch 2 and Example Branch 4"
1815815,2021-02-05 22:13:00 UTC,Docs here to facilitate testing:
1815815,2020-11-13 20:31:27 UTC,And I've now added an extra commit to add library group support to the BooPAC.
1815815,2020-11-12 14:54:57 UTC,"Hi all,"
1815815,2019-02-14 01:54:07 UTC,"I gave this a quick test, and the new dropdown seems confusing to me.  I don't think it will be obvious to the user why there are two dropdowns for ""scope"" (broadly construed) or why certain entries appear in one dropdown rather than the other.  In the standard case, where no library groups or location groups are configured, we get a new ""Where"" dropdown in the searchbar containing a ""No Restrictions"" entry and one or more entries under Search Scope; I think the average user will not know what this stuff means.  The Search Scope options also seem unnecessary when the Location dropdown already lets you adjust search scope in a straightforward way; it's confusing to provide the same option in two different ways."
1815815,2020-08-10 16:09:51 UTC,"Hi folks,"
1815815,2020-08-06 19:49:57 UTC,"I'm grabbing this back as I'll be offering a 1-dropdown version of the UI components soon.  This will roll back the depth-scoping capabilities of the branch that exists now, which is disappointing to me personally, but hopefully we can get Library Groups in to 3.6!"
1815815,2020-06-24 20:32:34 UTC,"I've force-pushed a master-rebased version of the above-linked branch.  I'll be looking at how we might fold some of the ideas from Jeff and Jane into this work soon, and I'll update here when that happens."
1815815,2019-08-21 00:33:48 UTC,A few thoughts:
1815815,2019-05-31 16:38:24 UTC,"I've rebased and pushed an updated version of the above branch.  I haven't addressed Jeff's concerns, but I think we can do some of that.  I think we can definitely provide ways to suppress the new dropdown, either entirely or just in certain cases (such as when there are no library groups to choose from given the context).  And a way to suppress the depth selector seems reasonable, but I disagree that the equivalent functionality exists today."
1815815,2019-02-27 14:27:09 UTC,"I've force-pushed an update to the branch to address a display issue with location groups in the new UI component, and with a label in the IDL.  Same coords."
1815815,2019-02-14 13:59:34 UTC,"Hi Jeff-- thanks for the feedback!  This development was sponsored by PaILS, and they will be testing it over the next few weeks as well.  We have not pullrequested this yet since a final branch will be posted after partner testing is complete & I hope you can take a look at that branch, too, when it's ready."
1815815,2019-02-13 21:41:54 UTC,The promised branch:
1815815,2020-09-23 19:56:01 UTC,"Well, this is a fun feature."
1815824,2019-02-15 18:01:05 UTC,Thanks for reporting.
1815824,2019-02-15 20:29:53 UTC,"It reports:
src/waveform/renderers/glvsynctestrenderer.cpp: In member function ‘virtual void GLVSyncTestRenderer::draw(QPainter*, QPaintEvent*)’:
src/waveform/renderers/glvsynctestrenderer.cpp:79:18: error: ‘GL_PROJECTION’ was not declared in this scope
     glMatrixMode(GL_PROJECTION);
                  ^~~~~~~~~~~~~
src/waveform/renderers/glvsynctestrenderer.cpp:79:18: note: suggested alternative: ‘GL_LOCATION’"
1815824,2019-02-15 21:20:34 UTC,"we need to set
opengles=1
to make the build work"
1815824,2019-05-10 16:54:45 UTC,https://bugs.launchpad.net/ubuntu/+source/mixxx/2.2.0~dfsg-1 built successfully for all architectures (including arm64) so I believe this is resolved.
1815827,2019-02-15 14:25:46 UTC,This RFE was discussed and approved by the drivers team. Please go ahead with implementation
1815827,2019-02-14 15:00:32 UTC,"I think this makes sense, changing to rfe-triaged so we can discuss at drivers meeting."
1815827,2019-02-15 13:28:10 UTC,Miguel - does that fact that this was moved to 'Wishlist' mean that the drivers team thinks it's OK to move forward??
1815842,2019-02-14 07:36:30 UTC,"In my case I hit the same bug, but lxd seems to be in the correct path (/usr/bin) directly from vanilla Ubuntu bionic."
1815842,2019-02-14 07:49:51 UTC,"So a variety of issues:
func (s *Server) ensureDefaultNetworking(profile *api.Profile, eTag string) error {"
1815842,2019-02-14 17:09:12 UTC,PR which has been committed https://github.com/juju/juju/pull/9752
1815842,2019-03-01 08:25:24 UTC,https://github.com/juju/juju/pull/9817 merges this into develop
1815843,2019-05-02 20:54:23 UTC,"Do you have a tcpdump of the network traffic? That is needed to be able to determine what the issue is. We need to inspect the HTTP headers that is being sent from nginx to the client. Specifically the ""Content-Length"" header to see if there is a mismatch there."
1815843,2020-02-17 04:17:25 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1815843,2019-09-20 12:05:35 UTC,"Can this still be reproduce with MAAS 2.6? If so, we'll try to reproduce this on our side."
1815843,2019-05-03 14:19:21 UTC,"If you could configure nginx to log the required information that would also work, but a tcpdump would really get us a lot of information about what is going on. Would would only need to run it on the rack controller where the booting is occurring from. I understand that it would be a huge amount of data, so if not possible we can do our best to work with out it. Just will take more time to find the actual issue."
1815843,2019-05-02 21:06:48 UTC,"No, it's impractical to catch a tcpdump for every single VM on every single run... the logs would be enormous."
1815843,2019-04-30 20:28:39 UTC,"We don't modify the nginx templates at all, they are just default. here they are:"
1815843,2019-02-14 16:52:55 UTC,"Hi guys,"
1815843,2019-04-30 19:05:22 UTC,"Andres, I specified in comment #5 that it's grafana-1 that had the issue. The logs for that are attached in comment #6."
1815843,2019-02-28 17:09:10 UTC,"Ok, we hit this again and I dug more into it. We aren't going to get serial console logs because it never makes it to linux. The VM is downloading the boot-kernel file and never downloads the initrd."
1815843,2019-03-01 16:08:41 UTC,Sub'd to field-high as this is causing a sudden spike in failures.
1815843,2019-04-30 20:23:39 UTC,"Setting this back to incomplete. Since these are accessing nginx, we would like to see the configuration. This is available in /var/lib/maas/http . Please gather all the nginx config files. That should give us an idea of whether that has any impact."
1815843,2019-04-30 17:53:33 UTC,can you please specify which machines are having these failures?
1815843,2019-04-30 17:46:07 UTC,"Is automatic image syncing enabled in this deployment? If so, while this error happens, are images being download and/or updated?"
1815844,2020-07-28 04:17:18 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1815844,2020-05-28 07:04:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1815844,2020-05-28 06:40:31 UTC,Marking charm task as invalid as this is a kernel issue with the xenial release kernel.
1815844,2020-03-30 06:59:20 UTC,On xenial if I install a kernel 4.8.0 instead of 4.4.0 on the nova-compute nodes the problem vanishes:
1815844,2020-03-27 15:34:18 UTC,As mentioned here [0] it seems to be a kernel bug. It is indeed reproducible on xenial (kernel 4.4.0-176-generic) instead of bionic (4.15.0-91-generic). I can consistently reproduce it on xenial-queens without CPU load. For the record on that deployment we get os-brick 2.3.0-0ubuntu1~cloud0 but the problem is clearly outside of os-brick: on this setup when re-attaching a volume the following files don't show up anymore: /sys/block/sda/device/wwid and /sys/block/sdb/device/wwid
1815844,2020-03-27 11:32:35 UTC,"I can successfully create, attach, detach and re-attach several times purestorage volumes with multipath and they remain multipath (i.e. I can't reproduce the issue). I tried with the following setups, with and without high CPU load on the nova-compute node running the instance to which I'm attaching the volume:
- bionic-train (with os-brick 2.10.0-0ubuntu1~cloud0 installed on nova-compute)
- bionic-stein (with os-brick 2.8.1-0ubuntu1~cloud0 installed on nova-compute, which should be approximately the version that the original reporter was using at that time)
- bionic-rocky (with os-brick 2.5.3-0ubuntu1~cloud0 installed on nova-compute)"
1815844,2019-03-19 13:43:44 UTC,"OK fair-enough, perhaps I'm wrong. I'm exposing here what I'm suffering in my env. There are several factors, also it might be that there is a bug in the version of multipath that we are shipping. I don't know."
1815844,2019-03-19 12:24:12 UTC,"That is not how ""find_multipaths"" works. If it's set to ""no"" multipathd will create a DM for ALL non blacklisted devices that appear in the system, even if only 1 device appears."
1815844,2019-03-19 11:28:12 UTC,Thanks working on this Gorka I really appreciate.
1815844,2019-03-19 10:48:07 UTC,"Sorry, not exactly check if it's in ""wwn_paths"", we must look for the match on the real paths on the wwn_paths."
1815844,2019-03-19 10:36:51 UTC,"I looked into this and the problem is not specific to ""find_multipaths yes"", and can happen with the configuration option set to ""no"" as well."
1815844,2020-07-29 17:56:24 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.opendev.org/638639
Reason: After reading the bug report, I'm going to abandon this. Feel free to restore and update if there is anything else to be done."
1815844,2019-02-21 18:25:33 UTC,OK so I was able to make thing working by applying that patch to os-brick. But it's probably not the right fix. Something seems clear is not related to Nova.
1815844,2019-02-20 21:40:44 UTC,"https://review.openstack.org/#/c/636226/ is related to failing to attach. In the case for which this bug was filed, the volume successfully attaches but the multipath device is not used."
1815844,2019-02-19 14:06:11 UTC,Maybe related to:
1815844,2019-02-19 13:58:31 UTC,Ok so my previous comment was not right we use new Cinder API. Also I start to think that issue may not be related to Nova since we don't reuse bdm details previously stored in the database also it seems that Nova were able to attach and detach the volume without any issues.
1815844,2019-02-18 13:48:10 UTC,"Yes, as Matt said it's probably the first place where we should look at. I should have access to that env soon and will be able to ensure it."
1815844,2019-02-14 21:13:51 UTC,"The new-style volume attachment flow with the volume attachments API was introduced in Queens, so maybe there is something regressed from that:"
1815844,2019-02-14 15:31:17 UTC,"I don't think this is related to the charm, it looks like a bug in upstream nova."
1815844,2019-02-14 01:53:24 UTC,"Subscribed this bug to field-high. A dev environment is accessible at the customer site for approximately one week, which includes an attachment to the Purestorage array."
1815844,2019-02-27 15:44:12 UTC,"Basically the issue is related to 'find_multipaths ""yes""' in /etc/multipath.conf. The patch I proposed fix the issue but adds more complexity to the algorithm which is already a bit tricky. So let see whether upstream is going to accept it."
1815844,2019-02-22 12:00:48 UTC,Patch proposed against os-brick here [0]
1815846,2019-02-14 06:29:23 UTC,/cc @Zuul
1815847,2019-02-14 04:19:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1815847,2019-02-22 09:27:54 UTC,"Per the Foundations wiki, ""If you encounter the bug when booting the Live CD (or alternative installer), file the bug against the kernel."""
1815847,2019-02-14 02:31:22 UTC,This error would disappear if not Choose Chinese Language in first screen (F2 or grub manual screen). The UEFI boot would not provide this option choosing too.
1815848,2019-02-14 03:46:42 UTC,"you could say:
  no machine ""0"" in model ""default""
which might give you the hint"
1815849,2019-02-15 01:18:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637083"
1815849,2019-02-15 03:42:51 UTC,"I think your title and your content doesn't match, your title says, ``can still get`` seems to me
that you can get extra records that the old type is ``ironic``, but your content seems describes
the case that some of them is missing."
1815849,2019-02-15 05:48:17 UTC,"@ Zhenyu Zheng
thanks for your attention, i have update bug title and content.
hope to help you understand what i mention"
1815849,2019-02-15 08:13:13 UTC,"@ Zhenyu Zheng
the following is my truble shoot"
1815849,2020-02-20 11:21:35 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/637083"
1815854,2019-02-20 15:59:39 UTC,"The input field had a maximum value of 30000 pixels set. So when trying to set the correct value of 50000x3000 or so about the width was truncated to 30000, but the height remained unchanged. This resulted in the changed cropped."
1815854,2019-02-20 00:23:07 UTC,"I take it that you found the problem?
Boy - that was fast!"
1815854,2019-02-19 16:20:17 UTC,"OK.  I have done the SSR recording of the process, and will attach it, and the .log file (to which I added the terminal output), and the stitching log and the .pto file."
1815854,2019-02-19 20:01:34 UTC,Fixed in repository.
1815854,2019-02-18 17:19:11 UTC,"I can't reproduce the issue. I loaded your project and pressed  calculate optimal size. The results was 53352x6474 (with the black border).
Then it tried ""Fit"" + ""Calculate size""+""auto crop"" to get rid of the black border. The results was ""53199x2785"". This is in the range, you expected, isn't it.
The change of the crop during stitching I can't reproduce. I set the crop and this one was used during stitching. Maybe there was an unintentional mouse click?"
1815854,2019-02-18 02:24:54 UTC,Here is the .pto file requested.
1815854,2019-02-17 07:17:16 UTC,Can you provide the pto file which shows the described behaviour?
1815854,2019-02-19 02:23:42 UTC,No. I was able to reproduce it several times.
1815861,2019-02-14 15:47:24 UTC,That's a really cool idea!
1815864,2019-10-18 20:34:02 UTC,Does it still fail with make 4.2.1 on Windows?
1815864,2021-01-26 18:00:06 UTC,It indeed is only happening for some versions of make.
1815867,2019-11-11 05:42:30 UTC,"I would suggest to use inhibit API[1] to suppress the suspend with the user session, so the test script would not mess around the user settings. The inhibit API should only apply to the machine that are running Desktop."
1815867,2021-01-26 08:08:31 UTC,Tested on Checkbox RC stack:
1815871,2019-02-14 08:37:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636855"
1815871,2019-02-14 15:22:00 UTC,Hello Jesse:
1815871,2019-02-15 13:25:48 UTC,"Hi Rodolfo,
I have put log in the description of this bug.
I referred to nova side implementation in: https://github.com/openstack/nova/blob/master/nova/wsgi.py#L197
And I tested, which works."
1815871,2019-02-21 03:44:17 UTC,"I find there is an issue when neutron-server API implement graceful stop.
When stop neutron-server, API worker will stop first [1] in a graceful way, and WSGI is waiting all running requests to neutron-server close.
But there maybe persistent connection requests on neutron-server API workers which will prevent API workers from stopping. About persistent connection HTTP, refer to [2].
I checked my environment, nova-api and nova-compute using neutronclient to connect neutron-server, neutronclient will use persistent connection to neutron-server.
When API workers do not stop, and after 60s (graceful_shutdown_timeout in oslo-service), parent neutron-server will stop. This will make RPC workers stop immediately.
There is no time for RPC workers stop gracefuly."
1815871,2019-04-16 08:47:22 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/636855
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1815871,2019-04-16 08:47:13 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1815873,2019-02-21 09:25:48 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1815876,2019-02-14 12:23:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1815877,2019-02-14 09:21:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/636864"
1815877,2019-02-25 21:07:50 UTC,(Copying my comment in the proposed review)
1815877,2019-02-26 03:52:56 UTC,"I found that the physical_network and segmentation_id field filled with a value under first tab, could reproduce the case. Maybe the required class on page for field made your solution."
1815877,2019-02-26 07:13:28 UTC,"> I found that the physical_network and segmentation_id field filled with a value under first tab
"
1815878,2019-02-14 13:40:36 UTC,Fixed with https://github.com/juju/juju/pull/9749
1815879,2019-02-21 12:09:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638407"
1815879,2019-02-18 12:59:10 UTC,I have created a blog post describing how to setup Swift Global Cluster with the patched charms:
1815879,2019-02-21 12:07:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638406"
1815879,2019-12-17 10:30:28 UTC,"Reviewed:  https://review.opendev.org/638406
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=fc261a5adc62b04af178fac7a36b69f8589f55bf
Submitter: Zuul
Branch:    master"
1815879,2019-12-17 11:18:36 UTC,"Reviewed:  https://review.opendev.org/638407
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=44df5db97d59e9de3510553082d276fc3a1c3bbf
Submitter: Zuul
Branch:    master"
1815882,2019-05-29 08:58:49 UTC,"3.30.5-0ubuntu0.18.10.1 seems to work fine, no report of regression, marking as verified"
1815882,2019-05-30 08:33:37 UTC,This bug was fixed in the package evolution-data-server - 3.30.5-0ubuntu0.18.10.1
1815882,2019-05-30 08:33:51 UTC,"The verification of the Stable Release Update for evolution-data-server has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815882,2019-02-21 14:18:28 UTC,"Hello Sebastien, or anyone else affected,"
1815882,2019-05-23 19:29:15 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1815884,2019-02-21 14:36:25 UTC,"Hello Sebastien, or anyone else affected,"
1815884,2019-05-30 08:33:20 UTC,This bug was fixed in the package evolution - 3.30.5-0ubuntu0.18.10.1
1815884,2019-05-30 08:33:27 UTC,"The verification of the Stable Release Update for evolution has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815884,2019-05-29 09:00:50 UTC,"3.30.5-0ubuntu0.18.10.1 seems to work fine, no report of regression, marking as verified"
1815884,2019-05-23 19:29:25 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1815889,2019-04-02 13:03:15 UTC,"(In reply to Michel Dänzer from comment #8)

> Mesa doesn't really need explicit thread affinity at all. All it wants is
> that certain sets of threads run on the same CPU module; it doesn't care
> which particular CPU module that is. What's really needed is an API to
> express this affinity between threads, instead of to specific CPU cores.
"
1815889,2019-02-27 10:01:15 UTC,"Summary:
- qemu crash when using GL
- ""sched_setaffinity"" is the syscall that is seccomp blocked and kills qemu
- the mesa i915 drivers (and your radeon as well) will do that call
- it is blocked by the current qemu -sanbox on,...,resourcecontrol=deny which is libvirts default
- Implemented by qemu 24f8cdc572
- Similar issue being fixed last year qemu 056de1e894
- new code in mesa 18.3 since mesa d877451b48"
1815889,2019-02-27 09:56:22 UTC,"From Ubuntu's POV this is rather new as the code in Mesa came in with the fresh 18.3.0_rc4-1
It is possible that no one else saw it so far ...
It is in mesa upstream since
  https://github.com/mesa3d/mesa/commit/d877451b48a59ab0f9a4210fc736f51da5851c9a"
1815889,2019-02-27 09:42:42 UTC,"Eventually it is an ""Program terminated with signal SIGSYS, Bad system call""
So we need to find what is bad about it."
1815889,2019-02-27 09:03:42 UTC,Stack trace with slightly more info as all DBG and source is installed here.
1815889,2019-02-27 08:47:19 UTC,I can make the viewers (virt-viewer / virt-manager) crash when attaching to it semi-remotely - but that might be a broken setup for a local only spice definition.
1815889,2019-02-27 08:18:12 UTC,That left only the actual disk+iso of fedora vs ubuntu cloudimg based qcow and that the boxes VM used userspace networking. Still the issue remained.
1815889,2019-02-27 10:38:13 UTC,"IMHO that mesa change is not valid. It is settings its affinity to run on all threads which is definitely *NOT* something we want to be allowed.  Management applications want to control which CPUs QEMU runs on, and as such Mesa should honour the CPU placement that the QEMU process has."
1815889,2019-02-27 11:07:49 UTC,(I reported that issue a few days ago too: https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg06066.html)
1815889,2019-02-27 13:55:56 UTC,"See also mesa bug:
https://bugs.freedesktop.org/show_bug.cgi?id=109695"
1815889,2019-02-27 11:50:05 UTC,"I did wonder if we could set the action for some syscalls to be ""errno"" instead of ""kill process"", but I worry that could then result in silent mis-behaviour as processes fail to check return value as they blindly assume the call cannot fail."
1815889,2019-11-25 19:37:45 UTC,This bug was fixed in the package mesa - 19.2.4-1ubuntu1
1815889,2019-10-21 09:52:24 UTC,I believe this was fixed by qemu 4.0 in eoan.
1815889,2019-05-07 14:28:11 UTC,Reopening/Assigning to TImo for eoan since there is a patch which can we dropped once qemu is fixed
1815889,2019-04-13 13:50:57 UTC,"This problem was solved by qemu [1], so this mesa bug can be closed."
1815889,2019-04-03 12:09:34 UTC,"Thank you Daniel,
we will most likely keep Disco as-is for now and merge this in 19.10 where then mesa can drop the revert. I tagged it for 19.10 to be revisited."
1815889,2019-04-02 17:38:08 UTC,FYI the QEMU change merged in the following pull request changed to return an EPERM errno for the thread affinity syscalls:
1815889,2019-03-15 07:54:14 UTC,This bug was fixed in the package mesa - 19.0.0-1ubuntu1
1815889,2019-03-11 17:04:20 UTC,"I'm removing this from the 19.0 blocking tracker. Generally we don't add bugs to block a release if they were present in the previous release, additionally there doesn't seem to be any consensus on a solution, at this moment. If there is a fix implemented I'd be happy to pull that into a later 19.0 release."
1815889,2019-03-06 18:17:01 UTC,"We're getting down to just a few bugs blocking 19.0, so I'm pinging those bugs to see what the progress is?"
1815889,2019-03-04 17:15:30 UTC,"The PPA was built against -proposed so I had to enable that to install all libs.
That done the 19.0.0~rc6-1ubuntu0.1 with the set affinity change reverted works quite nicely."
1815889,2019-03-04 16:55:25 UTC,"I don't have that issue on a chroot, so you should at least tell me why it would refuse to upgrade them all.. apt should show an error"
1815889,2019-02-27 11:32:56 UTC,As & when libvirt & QEMU supports the external vhost processes for this I expect it will still restrict the CPU affinity and apply seccomp filters that likely to be as strict as they are today at minimum.
1815889,2019-03-04 16:13:50 UTC,"Hi Timo,
I tried to test with the mesa from ppa:canonical-x/x-staging
But there is a dependency issue in that PPA - I can't install all packages from there.
It seems most of the X* packages will need a transition for the new mesa and those are not in this ppa right now."
1815889,2019-03-02 11:36:02 UTC,"(In reply to Daniel P. Berrange from comment #3)

> (In reply to Ahzo from comment #2)
> > To check for the availability of the syscall, one can try it in a child
> > process and see if the child is terminated by a signal, e.g. like this:
>
> Afraid not, QEMU's seccomp filter blocks use of fork() too :-)
"
1815889,2019-02-28 10:39:09 UTC,Adding Timo who maintainers mesa.
1815889,2019-02-28 10:21:44 UTC,"(In reply to Marek Olšák from comment #7)

> An even better solution would be to have a virtual thread affinity that only
> the application can see and change, which should be silently masked by
> administrative policies not visible to the application.
"
1815889,2019-02-28 10:08:07 UTC,"@Ubuntu-Desktop Team (now subscribed) - is there a chance we can revert [1] in mesa before it will be released with Disco for now. That would be needed until an accepted solution throughout the stack of libvirt/qemu/mesa is found?
Otherwise using GL backed qemu graphics will fail as outlined in the bug."
1815889,2019-02-28 10:04:29 UTC,"Thanks Daniel and MarcAndre for chiming in here.
Atfer thinking more about it I agree to Daniel that actually mesa should honor and stick with its affinity assignment."
1815889,2019-02-28 00:15:48 UTC,"(In reply to Daniel P. Berrange from comment #4)

> I'm curious what motivated this change to start with ?  Even if QEMU was not
> enforcing seccomp filters, I think I'd consider it a bug for mesa to be
> setting its process affinity in this way.  The mgmt application or sysadmin
> has decided that the process must have a certain affinity, based on how
> it/they want the host CPUs utilized. Why is mesa wanting to override this
> administrative policy decision to restrict CPU usage ?
"
1815889,2019-02-27 23:14:50 UTC,"Sent a quick RFC for an env variable workaround on the ML ""[PATCH] RFC: Workaround for pthread_setaffinity_np() seccomp filtering""."
1815889,2019-02-27 14:54:09 UTC,"(In reply to Daniel P. Berrange from comment #4)

>
> I'm curious what motivated this change to start with ?  Even if QEMU was not
> enforcing seccomp filters, I think I'd consider it a bug for mesa to be
> setting its process affinity in this way.  The mgmt application or sysadmin
> has decided that the process must have a certain affinity, based on how
> it/they want the host CPUs utilized. Why is mesa wanting to override this
> administrative policy decision to restrict CPU usage ?
"
1815889,2019-02-27 14:45:24 UTC,"(In reply to Ahzo from comment #0)

> The problematic code at src/util/u_queue.c:252 was added in the following
> commit:
> commit d877451b48a59ab0f9a4210fc736f51da5851c9a
> Author: Marek Olšák <email address hidden>
> Date:   Mon Oct 1 15:51:06 2018 -0400
>
>     util/u_queue: add UTIL_QUEUE_INIT_SET_FULL_THREAD_AFFINITY
>
>     Initial version discussed with Rob Clark under a different patch name.
>     This approach leaves his driver unaffected.
>
>
> Since setting the thread affinity seems non-essential here, the failing
> syscall should be handled gracefully, for example by setting a signal
> handler to ignore the SIGSYS signal.
"
1815889,2019-02-27 14:42:21 UTC,"(In reply to Ahzo from comment #2)

> To check for the availability of the syscall, one can try it in a child
> process and see if the child is terminated by a signal, e.g. like this:
"
1815889,2019-02-27 08:18:05 UTC,"Since my domain ran gl fine I was eliminating more differences one by one, keeping <gl enable='yes'/> to check if there is a second ingredient needed."
1815889,2019-03-04 09:40:15 UTC,You can test 19.0~rc6 with this reverted on a ppa:
1815889,2019-02-21 17:15:56 UTC,"To check for the availability of the syscall, one can try it in a child process and see if the child is terminated by a signal, e.g. like this:"
1815889,2019-02-15 12:37:58 UTC,"Interestingly, the Ubuntu 18.10 image works.
So is it really an attribute of the guest that breaks it?"
1815889,2019-02-20 20:12:32 UTC,"Since upgrading Mesa from 18.2 to 18.3, launching a QEMU virtual machine with Spice OpenGL enabled (for virgl), causes QEMU to crash with SIGSYS inside the radeonsi driver. The reason for this is that the QEMU sandbox option 'resourcecontrol=deny' disables the sched_setaffinity syscall called in pthread_setaffinity_np, which is now used by the radeonsi driver."
1815889,2019-02-14 10:40:12 UTC,"StacktraceTop:
 __pthread_setaffinity_new (th=<optimized out>, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
 ?? () from /tmp/apport_sandbox_8_pwkx51/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? ()
 ?? ()
 ?? ()"
1815889,2019-02-15 12:16:33 UTC,I can confirm the reported issue
1815889,2019-02-15 12:16:52 UTC,"Trace looks similar:
--- stack trace ---
#0  0x00007f1570fec0bf in __pthread_setaffinity_new (th=<optimized out>, cpusetsize=128, cpuset=0x7f156d4e3680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
        __arg2 = 128
        _a3 = 139730004883072
        _a1 = 22587
        resultvar = <optimized out>
        __arg3 = 139730004883072
        __arg1 = 22587
        _a2 = 128
        pd = <optimized out>
        res = <optimized out>
#1  0x00007f156dc8dc73 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
No symbol table info available.
#2  0x00007f156dc8d5d7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
No symbol table info available.
#3  0x00007f1570fe1164 in start_thread (arg=<optimized out>) at pthread_create.c:486
        ret = <optimized out>
        pd = <optimized out>
        now = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139730004887296, -2085932122569588158, 140733496626446, 140733496626447, 0, 139730004883520, 2100820740254843458, 2100830499542516290}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
        not_first_call = <optimized out>
#4  0x00007f1570f09def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
--- source code stack trace ---
#0  0x00007f1570fec0bf in __pthread_setaffinity_new (th=<optimized out>, cpusetsize=128, cpuset=0x7f156d4e3680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
  [Error: pthread_setaffinity.c was not found in source tree]
#1  0x00007f156dc8dc73 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#2  0x00007f156dc8d5d7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#3  0x00007f1570fe1164 in start_thread (arg=<optimized out>) at pthread_create.c:486
  [Error: pthread_create.c was not found in source tree]
#4  0x00007f1570f09def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  [Error: clone.S was not found in source tree]"
1815889,2019-02-20 21:30:42 UTC,Mesa needs a way to query that it can't set thread affinity.
1815889,2019-02-15 13:19:30 UTC,"The following gets me to non boxy libvirt:
$ virsh -c qemu+unix:///session?socket=/run/user/1000/libvirt/libvirt-sock list --all"
1815889,2019-02-15 13:22:46 UTC,"FTR: this guest XML (not out of gnome-boxes) works on the very same Host system.
This runs qxl + gl=yes as well and does not fail.
We need to find what the difference is between those is as well."
1815889,2019-02-15 12:17:11 UTC,"libvirt XML that was generated:
<domain type=""kvm"">
  <name>fedora29-wor</name>
  <uuid>2f4e83f7-18ed-45e2-bbf7-eef9f1c6c6c0</uuid>
  <title>Fedora 29 Workstation</title>
  <metadata>
    <boxes:gnome-boxes xmlns:boxes=""https://wiki.gnome.org/Apps/Boxes"">
      <os-state>live</os-state>
      <media-id>http://fedoraproject.org/fedora/29:0</media-id>
      <media>/home/paelzer/Fedora-Workstation-Live-x86_64-29-1.2.iso</media>
    </boxes:gnome-boxes>
    <libosinfo:libosinfo xmlns:libosinfo=""http://libosinfo.org/xmlns/libvirt/domain/1.0"">
      <libosinfo:os id=""http://fedoraproject.org/fedora/29""/>
    </libosinfo:libosinfo>
  </metadata>
  <memory unit=""KiB"">2097152</memory>
  <currentMemory unit=""KiB"">2097152</currentMemory>
  <vcpu placement=""static"">2</vcpu>
  <os>
    <type arch=""x86_64"" machine=""pc-q35-3.1"">hvm</type>
    <boot dev=""cdrom""/>
    <boot dev=""hd""/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode=""host-passthrough"" check=""none"">
    <topology sockets=""1"" cores=""2"" threads=""1""/>
  </cpu>
  <clock offset=""utc"">
    <timer name=""rtc"" tickpolicy=""catchup""/>
    <timer name=""pit"" tickpolicy=""delay""/>
    <timer name=""hpet"" present=""no""/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>destroy</on_reboot>
  <on_crash>destroy</on_crash>
  <pm>
    <suspend-to-mem enabled=""no""/>
    <suspend-to-disk enabled=""no""/>
  </pm>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type=""file"" device=""disk"">
      <driver name=""qemu"" type=""qcow2"" cache=""writeback""/>
      <source file=""/home/paelzer/.local/share/gnome-boxes/images/fedora29-wor""/>
      <target dev=""vda"" bus=""virtio""/>
      <address type=""pci"" domain=""0x0000"" bus=""0x03"" slot=""0x00"" function=""0x0""/>
    </disk>
    <disk type=""file"" device=""cdrom"">
      <driver name=""qemu"" type=""raw""/>
      <source file=""/home/paelzer/Fedora-Workstation-Live-x86_64-29-1.2.iso"" startupPolicy=""mandatory""/>
      <target dev=""hdc"" bus=""sata""/>
      <readonly/>
      <address type=""drive"" controller=""0"" bus=""0"" target=""0"" unit=""2""/>
    </disk>
    <controller type=""usb"" index=""0"" model=""ich9-ehci1"">
      <address type=""pci"" domain=""0x0000"" bus=""0x00"" slot=""0x1d"" function=""0x7""/>
    </controller>
    <controller type=""usb"" index=""0"" model=""ich9-uhci1"">
      <master startport=""0""/>
      <address type=""pci"" domain=""0x0000"" bus=""0x00"" slot=""0x1d"" function=""0x0"" multifunction=""on""/>
    </controller>
    <controller type=""usb"" index=""0"" model=""ich9-uhci2"">
      <master startport=""2""/>
      <address type=""pci"" domain=""0x0000"" bus=""0x00"" slot=""0x1d"" function=""0x1""/>
    </controller>
    <controller type=""usb"" index=""0"" model=""ich9-uhci3"">
      <master startport=""4""/>
      <address type=""pci"" domain=""0x0000"" bus=""0x00"" slot=""0x1d"" function=""0x2""/>
    </controller>
    <controller type=""sata"" index=""0"">
      <address type=""pci"" domain=""0x0000"" bus=""0x00"" slot=""0x1f"" function=""0x2""/>
    </controller>
    <controller type=""pci"" index=""0"" model=""pcie-root""/>
    <controller type=""pci"" index=""1"" model=""pcie-root-port"">
      <model name=""pcie-root-port""/>
      <target chassis=""1"" port=""0x10""/>
      <address type=""pci"" domain=""0x0000..."
1815892,2019-02-21 14:25:12 UTC,"Hello Sebastien, or anyone else affected,"
1815892,2019-05-30 08:33:34 UTC,"The verification of the Stable Release Update for evolution-ews has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1815892,2019-05-30 08:33:29 UTC,This bug was fixed in the package evolution-ews - 3.30.5-0ubuntu0.18.10.1
1815892,2019-05-29 08:59:26 UTC,"3.30.5-0ubuntu0.18.10.1 seems to work fine, no report of regression, marking as verified"
1815892,2019-05-23 19:29:19 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1815894,2019-02-14 11:22:37 UTC,please your help if there is any solution
1815899,2020-07-25 17:17:20 UTC,"I have the same problem: trying to install hplip-3.20.6.run on a Raspberry ends up with the error:
/usr/bin/ld: skipping incompatible ./prnt/hpcups//libImageProcessor.so when searching for -lImageProcessor
/usr/bin/ld: cannot find -lImageProcessor"
1815908,2019-10-14 17:43:43 UTC,This is the patch for 7.0.3. Just the location of the file changes.
1815908,2019-03-01 16:32:24 UTC,"I found the bug. It's a use-after-realloc problem. There is a code patch realloc, then copy from the old (new deallocated) buffer. I fixed it with the attached patch that takes into account that realloc already moved the data to the new buffer for us."
1815908,2019-02-14 15:16:44 UTC,"With right, I mean: As I would expect in this place. Not shifted by this amount."
1815908,2019-02-14 14:59:24 UTC,EPICS_CA_AUTO_ARRAY_BYTES=0 gives me
1815908,2019-02-14 14:43:11 UTC,Could you try repeating your test with EPICS_CA_AUTO_ARRAY_BYTES=0 in the environment?  This might help to narrow down which code path is involved.
1815908,2019-02-14 15:02:16 UTC,"BTW: I cannot confirm if this is a constant, but the data seem to be right from byte 32 in this case."
1815908,2019-10-24 17:14:40 UTC,Committed as 69035629154c1ea20e8dacf5d122802d3d3277e5
1815908,2019-10-16 03:10:30 UTC,"Sorry, this ticket fell through a crack.  Looking at your proposed fix I think I see what the logic bug is.  The only change I'll make when applying is to test if realloc() returns NULL."
1815910,2019-03-04 13:59:09 UTC,"Yeah, thanks James that is just what I have assumed.
And the paused device is enough to have the rule added as expected."
1815910,2019-02-14 14:15:39 UTC,Thanks Christian for replying.
1815910,2019-02-14 14:53:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815910,2019-02-14 15:45:49 UTC,"Repro:
1. Starting a new guest from which I dropped any network (e.g. created via uvtool)"
1815910,2019-02-14 16:06:39 UTC,"Use the full list as breakpoints yoou can easily get from source like
$ tail -n 60  src/security/security_apparmor.c | awk '/ = App/ {gsub("","",""""); printf(""b %s\n"", $3);}'"
1815910,2019-02-14 16:10:05 UTC,@security - for the issue outlined above I'd like to suggest to add /dev/vhost-net statically in src/security/apparmor/libvirt-qemu (and drop the detection in virt-aa-helper as it is superfluous).
1815910,2019-02-18 17:13:46 UTC,"As discussed I just send the patch and you can comment there :-)
So upstream for discussion now ..."
1815910,2019-02-19 07:41:07 UTC,"Thanks Christian.
So I will wait for merge your patch."
1815910,2019-02-19 11:30:43 UTC,"FYI: https://www.redhat.com/archives/libvir-list/2019-February/msg00986.html
No feedback there yet"
1815910,2019-02-26 06:28:10 UTC,Unless the security Team really dislikes the idea of opening it up I'd want to at least SRu this change to Bionic - further back I'm not so sure (the further we go back the less hardening/fixes the interface will have).
1815910,2019-03-01 16:58:22 UTC,"FYI, I communicated my preference here: https://www.redhat.com/archives/libvir-list/2019-March/msg00046.html"
1815910,2019-03-04 10:44:48 UTC,"Thanks Jamie, that is exactly why I asked about it."
1815910,2019-03-04 11:45:51 UTC,I am chiming in on behalf of our customer that is affected by this bug and patched his AppArmor profile manually for the time being to solve his issue.
1815910,2019-05-17 02:01:57 UTC,This bug was fixed in the package libvirt - 5.0.0-1ubuntu4
1815910,2019-05-15 11:00:38 UTC,"This issue is different, and so will be the solution.
I have separated the work on the vhost-scsi hotplug case into bug 1829223"
1815910,2019-05-15 10:24:11 UTC,"With vhost fix:
Host: <nothing>
Guest:
[  915.674097] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=4
[  915.674230] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0
[  915.713074] NET: Registered protocol family 40"
1815910,2019-05-15 10:06:33 UTC,Since quite often hot/clodplug is different I was looking into that as well:
1815910,2019-05-15 09:58:56 UTC,vhost_scsi would be like:
1815910,2019-05-15 09:07:17 UTC,"I checked vsock devices, those are fully mediated by libvirt and only an already open FD is passed when using those.
Without apparmor allowing a new open to qemu I have:"
1815910,2019-02-14 13:55:58 UTC,"Hi Daniel,
thank you for your report and your help making Ubuntu better."
1815910,2019-04-11 11:22:26 UTC,"I think they vhost_scsi might be covered by AppArmorSetSecurityHostLabel adding the rule as needed.
I'm not so sure on vhost_vsock.
Certainly worth to come up with a few tests and ensure that is true for all early/late access cases when implementing this."
1815910,2019-04-11 09:52:14 UTC,I would also consider vhost_scsi and vhost_vsock besides vhost_net.
1815910,2019-04-11 09:21:25 UTC,Thanks Jamie for providing an approach that is a compromise between upstreams needs and Ubuntu as a downstream - as well as at the same time being a tradeoff between comfort and security.
1815910,2019-04-10 20:49:22 UTC,I've stated my preference for upstream: https://www.redhat.com/archives/libvir-list/2019-April/msg00750.html
1815910,2019-03-04 13:04:38 UTC,"I chatted with David and got this when asking why this would be a common case.
  <dnegreira> cpaelzer: yep, it is the default setup of the latest version of the nova-compute charm"
1815910,2019-03-20 10:46:24 UTC,"The same behavior is reproduced in case when VM was created with network interface, interface detached, VM stopped (virsh destroy) and started again without network. This usecase does not need OpenStack admin privileges."
1815910,2019-03-05 07:40:07 UTC,Thanks @Christian for continuing the discussion.
1815910,2019-03-04 13:55:28 UTC,This is not the default otherwise no ones cloud would actually work right now.
1815910,2019-03-26 04:10:14 UTC,I tripped over this problem recently with an instance that needed its neutron port recreated.
1815910,2019-03-20 07:46:00 UTC,"Nothing else came up in a while, I have forwarded the comments to the mailing list and now wait for a consensus there."
1815911,2020-08-12 06:44:39 UTC,"Just verified it with a very recently compiled version of QEMU from git master and, indeed, the bug seems to be fixed as I can no longer reproduce the crash. The command executes correctly."
1815911,2020-08-12 06:30:38 UTC,"John, can you still reproduce it with the latest version of QEMU?"
1815911,2020-08-10 15:20:15 UTC,"I think this is probably a duplicate of bug #1594394, in which case it seems to be fixed in 5.0.0+."
1815911,2019-02-16 17:11:37 UTC,"On 2/15/19 1:47 PM, Laurent Vivier wrote:

> It seems it crashes during futex syscall:
>
> ...
> [pid     4] getpid()                    = 4
> [pid     4] tgkill(4, 24, SIGRT_1)      = 0
> [pid    24] <... futex resumed> )       = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
> [pid    24] --- SIGRT_1 {si_signo=SIGRT_1, si_code=SI_TKILL, si_pid=4, si_uid=0} ---
> [pid     4] futex(0x7f77abb4f610, FUTEX_WAIT_PRIVATE, 16777216, NULL <unfinished ...>
> [pid    24] getpid()                    = 4
> [pid    24] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x10} ---
> ...
"
1815911,2019-02-15 12:47:17 UTC,It seems it crashes during futex syscall:
1815918,2021-02-18 16:46:35 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1815920,2019-05-29 15:36:40 UTC,"The snap has a password management interface but it's not autoconnected, you should be able to enable it from gnome-software epiphany's detail page (it has an interfaces button). Could you try if that makes it work for you?"
1815920,2019-06-09 13:03:38 UTC,"OK, I turned on the password management interface from gnome-software, and now syncing has partially worked. The Epiphany snap could sync bookmarks and history, but not passwords from Firefox. I tried to log into Outlook and Gmail but the Epiphany snap did not have the passwords synced from Firefox, the Epiphany deb does that correctly, it knows about the passwords synced from Firefox."
1815921,2019-02-15 02:47:27 UTC,we have following code in each layer
1815921,2019-02-15 08:22:22 UTC,"Hi,"
1815921,2019-02-18 05:26:45 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/445058 proposed
1815921,2019-03-28 09:18:12 UTC,"I saw that the code was checked in. I downloaded the master and tested it. I created a guest and added the parameter ""ipl_from"". This works if it has only ""cms"" as value. We adjusted our situation and now we need besides ""cms"" also ""parm autocr"". I tested also with ""ipl_from"" set as ""cms parm autocr"", but got the error:
{
   ""rs"": 6,
   ""overallRC"": 500,
   ""modID"": 1,
   ""rc"": 4,
   ""output"": """",
   ""errmsg"": ""Unexpected internal error in ZVM SDK, error: SMT internal error. Results: {'rs': 6, 'errno': 0, 'strError': '', 'overallRC': 4, 'rc': 4, 'response': [\""(Error) ULTGUT0006E MAKEVM's DIRECTORY subfunction encountered an unknown operand: parm\""]}""
}
So I think there is some error if there is more than 1 word in the ipl_from parameter."
1815921,2019-03-28 10:46:33 UTC,https://bugs.launchpad.net/python-zvm-sdk/+bug/1822074
1815922,2019-02-14 16:02:25 UTC,bundle with bionic-queens
1815922,2019-02-14 16:05:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815929,2019-02-14 16:52:04 UTC,"For example, here's what the console says if you install the extension but not the native application: ""Hatch disconnected: Specified native messaging host not found."" And Firefox: ""Hatch disconnected: No such native application org.evergreen_ils.hatch"""
1815929,2020-01-16 18:04:23 UTC,"+1 to alert users when native application is not installed
After spending too much time troubleshooting Hatch when the application was not installed, I can confirm the benefit of pointing new Hatch users to the download page on evergreen-ils.org to install the native application."
1815930,2019-09-19 14:54:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1815930,2019-09-20 12:14:28 UTC,"Clearing the storage configuration can now (in MAAS 2.6) be done in one action, both in the UI and in the API."
1815933,2019-02-15 15:45:47 UTC,"Per discussion during the drivers meeting, we think the best approach would be to tag the ports during creation. However, the OpenStack community guidelines for tagging (https://specs.openstack.org/openstack/api-wg/guidelines/tags.html) don't support that. We will start a conversation in the mailing list with the SIG API to propose supporting adding tags on creation"
1815933,2019-03-01 14:26:17 UTC,"This RFE has been discussed by Neutron drivers team and it has been approved. The suggested approach is to support tag association during POST and then leverage bulk creation of resources, like it is being done for ports"
1815933,2019-12-16 01:25:37 UTC,This is how we are going to specify the tags to be attached to each port in the bulk POST request (as discussed in this ML thread: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003116.html):
1815933,2019-12-30 00:49:09 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/700754"
1815933,2019-12-30 01:49:34 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/700755"
1815933,2020-01-08 11:30:19 UTC,"Reviewed:  https://review.opendev.org/700754
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=8673f033196771ef907314f823ca23ef9360134d
Submitter: Zuul
Branch:    master"
1815933,2020-01-30 15:26:49 UTC,"Reviewed:  https://review.opendev.org/700755
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e22a191f47fe0d1a05cd707a0ad6a1ca637f69d1
Submitter: Zuul
Branch:    master"
1815933,2020-04-21 10:57:37 UTC,This is implemented in Neutron already. The only missing part is OSC/SDK support and that is tracked in BP https://blueprints.launchpad.net/neutron/+spec/tagging-on-post so I'm closing this LP now.
1815935,2019-03-05 20:16:35 UTC,"Thanks!
Do you know when will the new package be released?"
1815935,2019-02-18 17:27:19 UTC,"Thanks for the report! While I don't use or maintain the Ubuntu version of rssh, it looks like Ubuntu is importing the Debian security fixes, and this is indeed a regression in Debian as well. I'm working on a fix now, and checking with the Debian security team to confirm that it's worth a regression update. Presumably Ubuntu would then pull it in."
1815935,2019-03-02 16:12:25 UTC,Confirmed the bug based on the Debian report.
1815935,2019-02-28 02:40:54 UTC,"Thanks for fixing it in Debian.
I'll request someone from Ubuntu to import the fix."
1815935,2019-02-15 00:59:24 UTC,"Also libssh2 scp_send() uses ""-pt"" option."
1815935,2019-02-27 01:13:00 UTC,"Russ,"
1815935,2019-02-19 05:02:34 UTC,"Sounds good. We will keep that as an option for the long term solution.
It would be great if you could provide a fix for the regression.
Thanks again!"
1815935,2019-02-19 02:05:10 UTC,"sftp is natively supported by sshd (with ForceCommand internal-sftp and ChrootDirectory), so that avoids the problem that rssh has where ssh keeps adding new features that add new security vulnerabilities in the rssh model. That's probably the best solution if you're currently using scp."
1815935,2019-02-27 02:43:30 UTC,"Debian has released the fix for both stable and oldstable.  As I said above, I personally don't use Ubuntu, don't maintain the Ubuntu package, and don't have upload rights to Ubuntu, so I'm afraid I can't help with fixing the bug in Ubuntu.  Presumably you need to find someone who works on Ubuntu to import the fix from Debian, if that doesn't happen automatically."
1815935,2019-02-19 01:48:08 UTC,"Thanks for looking into it.
Do you have any suggestion for the alternative solutions?
If we decide to not use rssh tomorrow, the user we created that was meant only for file transfer would be a regular user, that would solve current issue and remove dependency on rssh. But that will be step down from the security provided by rssh. We will definitely look into alternative solution, but let me also know if you have other solutions in mind."
1815935,2019-04-12 05:42:54 UTC,That's great news. Thanks!
1815935,2019-04-11 20:07:43 UTC,Fixes were released today. Please upgrade (sudo apt-get update && sudo apt-get upgrade).
1815937,2019-02-20 01:35:53 UTC,"I attached the log.from starting a sway session, ending it (with rv=0), and not seeing sway be selected as the default session again. Line 98 of the log seems to be suspicious."
1815937,2019-02-18 09:21:03 UTC,"It does check /usr/share/wayland-sessions, do you have a /var/log/lightdm/lightdm.log after a failed session selection?"
1815938,2019-02-14 19:31:19 UTC,"That's a snapd issue mostly, see https://forum.snapcraft.io/t/implication-of-the-word-developer/3960"
1815939,2019-02-18 01:43:55 UTC,I have done a fresh install from Xubuntu 18.04.2 and did notice it was using zfs 0.7.9 with Linux 4.18. So probably you have to add those to the upgrade of the HWE stack.
1815939,2019-10-23 09:24:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815939,2019-10-24 13:02:34 UTC,I just noticed that SPL and ZFS is not needed as DKMS with hwe kernels - I do not know in which version it was included as kernel module.
1815939,2019-10-24 14:12:16 UTC,"This is an ancient bug-report on a HW stack upgrade of 18.04, that should have included an upgrade from ZFS 0.7.5 to 0.7.9. For those older ZFS releases 0.7.x, SPL is still needed. Only at ZFS release 0.8.x SPL has been integrated into zfsutils-linux.
I think we could say, that this bug-report has died of old age. Nobody will upgrade the hw stack of 18.04 anymore and the chance, that they also use ZFS is almost zero."
1815939,2019-12-01 23:29:52 UTC,"I am running into this same error. I have a home server on Ubuntu 18.04 with a raidz2 3 disk ZFS array (not as root filesystem). Today I tried upgrading to the new HWE kernel, but building failed. It hangs at 'checking spl build directory...'."
1815939,2019-12-02 00:09:23 UTC,"Ok, it seems that zfs is just included in the kernel. Also on 18.04 HWE.
I removed zfs-dkms and spl-dkms, and needed to run 'zpool import' after which my zpool showed up again."
1815940,2019-02-14 17:57:34 UTC,"https://github.com/git-ftp/git-ftp/issues/456
https://github.com/git-ftp/git-ftp/issues/447
https://github.com/git-ftp/git-ftp/issues/439
https://github.com/git-ftp/git-ftp/issues/417
https://github.com/git-ftp/git-ftp/issues/410"
1815940,2019-08-10 22:48:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815941,2019-06-05 16:26:06 UTC,Upstream closed the request with that comment
1815941,2019-06-05 16:28:44 UTC,(https://blogs.gnome.org/kalev/files/2018/09/gnome-software-source-drop-down-1024x723.png)
1815941,2019-06-05 17:18:48 UTC,"It would be great to have the ""old"" source field work in Bionic for snaps and debs though. It's already shown for flatpaks in Bionic. The same fix could be applied for snaps and debs in gnome-software 3.28 in Bionic. See the attached screenshot for clarification on the telegram app."
1815949,2019-07-10 21:40:13 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1815949,2019-03-06 20:08:26 UTC,"I suspect it's this line in qemu:
https://github.com/qemu/qemu/blob/master/qdev-monitor.c#L848"
1815949,2019-03-06 20:32:48 UTC,"Which I think means it'll be this code in libvirt that raises the actual exception:
https://github.com/libvirt/libvirt/blob/master/src/qemu/qemu_monitor_json.c#L392"
1815949,2019-03-07 00:08:32 UTC,"Okay, looks like lp still doesn't auto-comment for a patch that was originally proposed without the (correct) Closes-Bug tag. The fix is here: https://review.openstack.org/#/c/641480/"
1815949,2019-03-13 21:00:17 UTC,"Reviewed:  https://review.openstack.org/641480
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2a8ee40fccc65b177275d6fe80c10fdb83b86e1f
Submitter: Zuul
Branch:    master"
1815949,2019-03-22 03:43:17 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1815949,2019-04-10 20:31:59 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/651637"
1815949,2019-04-10 20:37:23 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/651642"
1815949,2019-04-15 23:48:53 UTC,"Reviewed:  https://review.openstack.org/651637
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6a7e45c750f2759c6b813042413afb9aaa8d1ca4
Submitter: Zuul
Branch:    stable/rocky"
1815949,2019-04-21 02:06:02 UTC,"Reviewed:  https://review.opendev.org/651639
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5433dc6a7525a5c356b4b5cd400bbea4e8edd0b0
Submitter: Zuul
Branch:    stable/queens"
1815949,2019-04-22 05:25:52 UTC,"Reviewed:  https://review.opendev.org/651642
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cc697d676c14a4abbf82b063910736897bddbdac
Submitter: Zuul
Branch:    stable/pike"
1815949,2019-04-26 17:15:41 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1815949,2019-06-18 03:41:25 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1815949,2019-02-14 20:04:24 UTC,"Marking this as Confirmed based on the traceback -- we can see that libvirt is raising an 'internal error' for a 'not found' condition, which our current code does not expect. To be thorough, we should locate where in the libvirt source this is raised, to see if we can learn the origin of this new error combo (if it's a change from a newer version of libvirt, etc)."
1815949,2019-03-06 19:32:38 UTC,"The "" unable to execute QEMU command 'device_del'..."" error message is coming from the libvirt code that calls into qemu, so I think it's actually something in qemu that's triggering it."
1815949,2019-04-10 20:34:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/651639"
1815950,2019-02-14 21:28:43 UTC,here's a patch
1815950,2019-02-14 19:16:49 UTC,"I agree with the description, but think this is a change in behavior and so not exactly a bug. I've confirmed this and set the importance to Wishlist as I think this would be a new feature or at least a change in behavior of an existing feature."
1815952,2019-02-15 15:24:19 UTC,I'm asking for help to have a server where I can compile. Please give me a few days to generate a patched kernel and confirm that this actually works.
1815952,2019-06-02 17:31:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1815952,2019-04-01 11:48:32 UTC,I also have the same problem in my HP Pavilion 15-bc202na. Is there any chance to add it to the list of quircks?
1815952,2019-02-15 00:18:47 UTC,Now YES!
1815952,2019-02-14 23:59:58 UTC,"Hello,"
1815952,2019-02-14 20:55:58 UTC,Ok.
1815952,2019-02-14 20:55:34 UTC,Ok.
1815952,2019-02-14 20:14:43 UTC,https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/pci/hda/patch_conexant.c?id=v5.0-rc6#n934
1815952,2019-02-14 19:43:33 UTC,This happens on kernel 5.0.0-050000rc6-generic
1815952,2019-02-14 19:24:52 UTC,"Open bug in launchpad.net:
https://bugs.launchpad.net/bugs/1815952"
1815954,2020-09-10 15:29:55 UTC,"Can confirm, the command is broken."
1815954,2020-01-30 05:21:43 UTC,I’ve fixed the issue in https://github.com/openstack/diskimage-builder/compare/master...mvgijssel:bug/fix-ramdisk-building. Will try to create a PR to get this merged.
1815954,2020-01-16 15:33:21 UTC,"I have the same issue. Change which might be related https://github.com/openstack/diskimage-builder/commit/97c01e48edd278dad3258d9e708cdbbe4c729691, though that would mean it's broken since version 2.0.0 (2+ years)."
1815954,2020-09-24 04:03:02 UTC,"I got same issue as @Julia, and I checked the commit by @Maarten, it seems that is a different issue maybe? He is building an iso image. https://github.com/openstack/diskimage-builder/pull/24/commits/4a9d0f4ddef4170ca9ec7407626e6bc3b3e535a1"
1815954,2020-09-24 06:20:02 UTC,"And if i setup _BASE_ELEMENT_DIR manually, dib will complains ""EXTRA_DETACH"" and ""EXTRA_UNMOUNT"" unbound."
1815955,2020-05-08 01:22:23 UTC,"Hi,"
1815955,2019-03-20 13:16:22 UTC,"Right now, this is working as intended, since everything runs with default passwords, and we don't want to open up laptops running microstack to attack."
1815955,2019-09-23 14:16:43 UTC,Perhaps this could be resolved by adding a snap configuration option to microstack such that we can install it as currently and then just
1815955,2019-10-09 18:12:27 UTC,"As of the latest build in --edge, this bug is partially resolved. You can override horizon settings by dropping a file into `/var/snap/microstack/common/etc/horizon/local_settings.d/` with any overrides. For example, you might create _10_hosts.py, with the following contents:"
1815955,2020-05-08 14:29:12 UTC,"@aliesma: what url are you typing in when you attempt to access the MicroStack dashboard? Are you tunneling from another machine, as in the original bug, or simply trying to access the dashboard on your local machine?"
1815955,2020-05-08 02:08:50 UTC,"No idea, I no longer use this."
1815955,2019-11-12 18:42:05 UTC,"As of the latest edge, we open Horizon to the outside world by default, which resolves this issue."
1815957,2019-02-19 14:47:45 UTC,apport information
1815957,2019-02-19 14:47:46 UTC,apport information
1815957,2019-02-19 14:47:32 UTC,apport information
1815957,2019-02-19 14:47:47 UTC,apport information
1815957,2019-02-19 14:47:49 UTC,apport information
1815957,2019-02-19 14:47:50 UTC,apport information
1815957,2019-02-19 14:47:52 UTC,apport information
1815957,2019-02-19 14:47:53 UTC,apport information
1815957,2019-02-19 14:47:44 UTC,apport information
1815957,2019-02-19 14:47:43 UTC,apport information
1815957,2019-02-19 14:47:39 UTC,apport information
1815957,2019-02-19 14:47:40 UTC,apport information
1815957,2019-02-19 14:47:34 UTC,apport information
1815957,2019-02-19 14:47:38 UTC,apport information
1815957,2019-02-19 14:47:36 UTC,apport information
1815957,2019-02-19 14:47:35 UTC,apport information
1815957,2019-02-19 14:47:27 UTC,apport information
1815957,2019-02-19 14:47:28 UTC,apport information
1815957,2019-02-19 14:47:30 UTC,apport information
1815957,2019-02-19 14:47:31 UTC,apport information
1815957,2019-02-19 14:47:41 UTC,apport information
1815957,2019-02-19 03:56:59 UTC,Please run this command to send us more information about the system:
1815957,2019-02-19 14:47:58 UTC,apport information
1815957,2019-02-19 14:47:55 UTC,apport information
1815957,2019-02-20 02:30:08 UTC,This change was made by a bot.
1815957,2019-02-20 08:17:45 UTC,"What happens when there's no ""acpi_os_name=Linux acpi_osi=""?"
1815957,2019-03-03 13:37:42 UTC,"Removing ""acpi_os_name=Linux acpi_osi="" from /etc/default/grub doesn't fix this problem."
1815957,2019-03-04 07:05:15 UTC,Please attach dmesg without those kernel parameters.
1815957,2019-03-12 04:04:41 UTC,Mark this as Incomplete for the request in #31
1815957,2019-05-12 04:17:19 UTC,[Expired for libinput (Ubuntu) because there has been no activity for 60 days.]
1815957,2019-02-19 14:47:56 UTC,apport information
1815957,2019-05-12 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1815957,2019-05-12 04:17:24 UTC,[Expired for xserver-xorg-input-libinput (Ubuntu) because there has been no activity for 60 days.]
1815957,2019-02-19 14:47:54 UTC,apport information
1815962,2019-06-20 08:42:24 UTC,Created pull request: https://github.com/CanonicalLtd/docker-registry-charm/pull/38
1815966,2019-02-14 21:55:49 UTC,Specification detailing the work needed to implement this feature: https://review.openstack.org/#/c/554320
1815966,2019-02-14 21:56:16 UTC,Proposed implementation: https://review.openstack.org/#/c/483514/
1815966,2019-02-14 21:57:13 UTC,"Deprecation of the current templated catalog backend, which will be obsolete after support for a YAML-based equivalent is implemented: https://review.openstack.org/#/c/482714/"
1815966,2019-09-24 16:03:26 UTC,"Change abandoned by Morgan Fainberg (<email address hidden>) on branch: master
Review: https://review.opendev.org/483514"
1815967,2019-02-15 20:00:59 UTC,"We had some discussion about this today.  We could certainly add logic in the k8s charms to create an appropriate SC out of the box depending on which, if any, integrator charm is available.  However, due to the differing levels of support from the various providers and the need to handle the case where an integrator charm isn't available, it may be that another approach would give us a more consistent and reliable level of support."
1815967,2019-02-15 21:14:45 UTC,"The requirement is to provide out of the box a storage class which provisions opinionated default disk volumes from the underlying cloud. Such disks are mounted into the pods as required to satisfy the standard Juju storage semantics. Cephfs out of the box may be a good thing to do as well, but it's not relevant in this case."
1815967,2019-02-15 22:29:44 UTC,"Sorry, the bit about in-cluster Ceph was me getting side-tracked on a different problem, unrelated to this bug."
1815967,2019-02-15 22:36:28 UTC,"Although, if we need to ensure that k8s-master *always* configures a default storage class, regardless of how it's deployed, then I feel like the order of preference should be:"
1815967,2019-02-19 15:06:42 UTC,"To be clear, CDK does not support CephFS today. The provisioner that we use on Ceph is RBD. I'm pretty sure field does the same."
1815967,2019-11-29 16:02:51 UTC,"PR to add the default storage classes for AWS, Google Cloud, and Azure:"
1815967,2019-02-15 20:37:38 UTC,"Actually, I'm not certain that LXD is a limitation for CephFS, since you can deploy it into Kubernetes: http://docs.ceph.com/docs/mimic/start/kube-helm/"
1815968,2019-11-07 16:14:25 UTC,"EG 3.3.4 - In production, our self check stations do play sounds.  We are using the OpenKiosk browser distribution."
1815969,2019-02-15 19:26:42 UTC,we believe this is expected behavior; assigning to Bin to confirm
1815969,2019-02-20 18:50:46 UTC,Marking as release gating; issue with SM failure handling as confirmed by Bin
1815969,2019-07-02 15:15:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668692"
1815969,2019-07-04 14:57:39 UTC,"Reviewed:  https://review.opendev.org/668692
Committed: https://git.openstack.org/cgit/starlingx/ha/commit/?id=f4be3908c3717328772f1a9eda3f703e434b6f13
Submitter: Zuul
Branch:    master"
1815969,2019-07-19 13:24:25 UTC,"Additional fix (to reboot failed controller) has been merged under the other LP.
https://review.opendev.org/#/c/670615"
1815969,2019-08-15 20:29:04 UTC,Verified in load  2019-08-14 05:30:00 +0000
1815969,2019-08-15 20:17:51 UTC,Verified in load 2019-08-14 05:30:00
1815971,2019-02-14 22:08:46 UTC,Proposed specification detailing the work: https://review.openstack.org/#/c/373983
1815974,2020-04-04 00:36:54 UTC,"This is not a manila bug, it was in manila-ui and was addressed with https://review.opendev.org/#/c/691184/"
1815975,2019-04-11 15:14:06 UTC,"Thanks for the request. I discussed that a bit with upstream and they changed the default
https://gitlab.gnome.org/GNOME/evolution/commit/9b0d2916"
1815975,2019-05-21 15:46:39 UTC,This bug was fixed in the package evolution - 3.32.2-1
1815975,2019-02-14 22:54:22 UTC,"Looks like the default settings are here:
https://git.launchpad.net/ubuntu/+source/evolution/tree/data/org.gnome.evolution.plugin.mail-notification.gschema.xml.in?h=ubuntu/disco-proposed"
1815980,2020-01-10 18:22:23 UTC,This is no longer an issue; the above all works now.
1815982,2020-06-07 03:04:08 UTC,also...it doesn't come back when a number is pushed.
1815983,2019-02-15 00:27:37 UTC,"Actually can reproduce this 100%, if you
1) activate only a set of cards that there are no non-memorized cards,
2) hit '0'"
1815987,2019-04-25 18:06:05 UTC,Still nothing?
1815987,2019-03-01 18:21:00 UTC,Bump.
1815987,2019-03-13 15:24:05 UTC,"Thank you for your bug report, what filesystem do you use? There are similar warnings in bug #1804603"
1815987,2019-03-13 16:43:11 UTC,"Ext4... the last two messages in that thread direct me to open a new bug, so I have."
1815987,2019-04-04 02:34:39 UTC,Bump.
1815987,2019-04-11 22:53:27 UTC,"Bump.  Still up to date on all patches, still have this issue."
1815987,2019-04-18 01:46:17 UTC,Still no idea/help on this bug?
1815987,2019-04-25 23:51:48 UTC,"You are running a correct/ubuntu kernel, and otherwise things look up to date."
1815987,2019-04-26 02:44:39 UTC,"krisbee@mythserver2018:~$ sudo ls -la /
total 120
drwxr-xr-x  25 root root  4096 Apr 11 18:41 .
drwxr-xr-x  25 root root  4096 Apr 11 18:41 ..
drwxr-xr-x   2 root root  4096 Apr 20 15:34 bin
drwxr-xr-x   3 root root  4096 Apr 20 15:37 boot
drwxrwxr-x   2 root root  4096 Jul  8  2018 cdrom
drwxr-xr-x  21 root root  4580 Apr 25 07:32 dev
drwxr-xr-x 157 root root 12288 Apr 20 15:37 etc
drwxr-xr-x   5 root root  4096 Feb  1 21:37 home
lrwxrwxrwx   1 root root    33 Apr  7 16:19 initrd.img -> boot/initrd.img-4.15.0-47-generic
lrwxrwxrwx   1 root root    33 Apr  7 16:19 initrd.img.old -> boot/initrd.img-4.15.0-46-generic
drwxr-xr-x  21 root root  4096 Sep  6  2018 lib
drwxr-xr-x   2 root root  4096 Jul 29  2018 lib32
drwxr-xr-x   2 root root  4096 Apr 26  2018 lib64
drwx------   2 root root 16384 Jul  8  2018 lost+found
drwxr-xr-x   3 root root  4096 Jul  8  2018 media
drwxr-xr-x   4 root root  4096 Jul 11  2018 mnt
drwxr-xr-x   5 root root  4096 Mar  5 19:57 opt
dr-xr-xr-x 294 root root     0 Apr 20 15:38 proc
drwx------   6 root root  4096 Nov 23 17:51 root
drwxr-xr-x  33 root root  1120 Apr 25 06:30 run
drwxr-xr-x   2 root root 12288 Apr 20 15:35 sbin
drwxr-xr-x   2 root root  4096 Jul  8  2018 snap
drwxr-xr-x   2 root root  4096 Apr 26  2018 srv
dr-xr-xr-x  13 root root     0 Apr 25 22:40 sys
drwxrwxrwt  22 root root 12288 Apr 25 22:39 tmp
drwxr-xr-x  12 root root  4096 Jun 11  2010 usr
drwxr-xr-x  15 root root  4096 May 23  2010 var
lrwxrwxrwx   1 root root    30 Apr  7 16:19 vmlinuz -> boot/vmlinuz-4.15.0-47-generic
lrwxrwxrwx   1 root root    30 Apr  7 16:19 vmlinuz.old -> boot/vmlinuz-4.15.0-46-generic
krisbee@mythserver2018:~$ sudo ls -la /var/
total 60
drwxr-xr-x 15 root    root     4096 May 23  2010 .
drwxr-xr-x 25 root    root     4096 Apr 11 18:41 ..
drwxr-xr-x  2 root    root     4096 Apr 21 00:06 backups
drwxr-xr-x 20 root    root     4096 Jul 27  2018 cache
drwxrwsrwt  2 root    whoopsie 4096 Apr 23 00:05 crash
drwxr-xr-x 90 krisbee krisbee  4096 Apr  7 16:16 lib
drwxrwsr-x  2 root    staff    4096 Apr 24  2018 local
lrwxrwxrwx  1 root    root        9 Jul  8  2018 lock -> /run/lock
drwxrwxr-x 18 root    syslog   4096 Apr 25 00:06 log
drwxrwsr-x  2 root    mail     4096 Apr 25 22:40 mail
drwxrwsrwt  2 root    whoopsie 4096 Apr 26  2018 metrics
drwxr-xr-x  2 root    root     4096 Apr 26  2018 opt
lrwxrwxrwx  1 root    root        4 Jul  8  2018 run -> /run
drwxr-xr-x  2 root    root     4096 Apr 16  2018 snap
drwxr-xr-x 10 root    root     4096 Oct 20  2018 spool
drwxrwxrwt 10 root    root     4096 Apr 25 22:39 tmp
drwxr-xr-x  3 root    root     4096 Jul 10  2018 www
krisbee@mythserver2018:~$ sudo ls -la /var/lib/
total 360
drwxr-xr-x 90 krisbee          krisbee       4096 Apr  7 16:16 .
drwxr-xr-x 15 root             root          4096 May 23  2010 ..
drwxr-xr-x  4 root             root          4096 Apr 26  2018 AccountsService
drwxr-xr-x  2 root             root          4096 Apr 30  2013 acpi-support
drwxr-xr-x  2 root             root          4096 Apr 20 15:38 alsa
drwxr-xr-x  5 root             root          4096 Jul 10  2018 apache2
drwxr-xr-x  4 root             root          4096 Apr 20 15:32 app-info
drwxr-xr-x  5 root    ..."
1815987,2019-04-26 02:56:53 UTC,I have reclaimed /var/lib with chown to root:root and now everything is working.
1815989,2020-05-22 11:16:26 UTC,These patches seems to work fine on stein but not on rocky.
1815989,2020-05-11 09:40:13 UTC,anyone help to fix a workaround in neutron?
1815989,2020-05-07 17:48:37 UTC,"It works.
I changed the nova/conf/workarounds.py and nova/network/neutronv2/api.py only on controllers nodes.
I changed neutron/agent/rpc,py on on compute nodes (deleting lines as you suggested)."
1815989,2020-05-07 17:43:04 UTC,I am sorry . I have not understand the output of diff command .Now is clear. I am going to test it
1815989,2020-05-07 17:19:08 UTC,Both are needed.
1815989,2020-05-07 16:16:34 UTC,"The neutron agent rpc.py on compute nodes contains the code you suggested so it does not need to be patched, right ?"
1815989,2020-05-07 15:20:55 UTC,"The neutron agent must be patched on compute node ?
And nova on controllers ?"
1815989,2020-05-07 14:12:04 UTC,"Add for #15, we should also skip in neutron/agent/rpc.py for workaround to disable port binding:"
1815989,2020-05-06 10:12:02 UTC,"Hello,
I did not understand if I must patch only nova/network/neutronv2/api.py and nova/workarounds.py
or also neuttron/agent/rpc.py as yao ning suggested."
1815989,2020-04-29 13:15:11 UTC,no we  cant activate teh port biding before the vm is runing on the the dest unless you are using post copy live migration.
1815989,2020-04-29 13:17:33 UTC,i could add a workaround config option to nova to forcully disable the multiple portbinding flow for live migration but that would really just be a hack and it would increase network downtime in some cases so it could not be enabled by default. it also has other issues like the inablity to migrate between ovs hosts with different firewall driver backends.
1815989,2020-07-16 16:40:51 UTC,Interesting having issues with this now after moving to Train and CentOS 8.
1815989,2020-07-16 16:41:09 UTC,Note that you need QEMU >= 4.0 to support announce_self
1815989,2020-10-27 13:51:50 UTC,"Thanks Sean for your in-depth information, really appreciate. I've added another neutron bug linking to this one."
1815989,2020-10-27 11:55:14 UTC,it should be noted that post-copy live migration with the force-complete live migration timeout action will signifcatly shorten the time to activate teh dest port binding.
1815989,2020-10-27 11:35:39 UTC,the binding of the port should not be requried for neutno to have wired up the port so that it has netwrok connectivity. before rocky neutron woudl wireup the port on any host at least for the in tree drivers. after rocky nova prebinds the port by creating a second port bingding. it then activates the port binding in post live migration.
1815989,2020-10-26 13:30:44 UTC,The race exists for iptables_hybrid based deployments when live_migration_wait_for_vif_plug=true (default value) as well.
1815989,2020-10-23 01:22:34 UTC,"Reviewed:  https://review.opendev.org/756478
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=24dd977c2217bb10baf2cf226eab2bd0e5b47d62
Submitter: Zuul
Branch:    stable/victoria"
1815989,2020-10-19 11:24:37 UTC,"live_migration_wait_for_vif_plug=true is the default value.
if you have set live_migration_wait_for_vif_plug=false then yes it would result in
packet loss and the mac learning frame not propagating if the vlan tag application took a protracted period of time."
1815989,2020-10-15 20:10:01 UTC,@sean-k-mooney
1815989,2020-10-13 14:03:36 UTC,"yes but likely not for a few months
im trying to get this merged in master once that is actully done we can start backporting.
at present all the neutron patches we are aware of are now merged there are 2 needed for nova at present once those merge we can start backporting. it has been quite hard to get core review on this feature which is why the fixes have been in flight for 2+ years. i am hopeful this will be resolved before the end fo the year and we will have done the backports but i also said that 2 years ago and i could not get people to actully review the chagnes."
1815989,2020-10-13 08:56:47 UTC,Do we have a clear path on how to solve this on rocky?
1815989,2020-10-12 12:17:36 UTC,the issue is not related to the firewall used but rather a side effect of which firewall is enabel if any.
1815989,2020-10-12 11:15:46 UTC,This issue happens even without firewall. It happens with openvswitch tap interfaces with native plug and disabled security groups (enable_security_group=false in [securitygroup] config section).
1815989,2020-10-12 10:44:57 UTC,"the issue does not happen when using the iptables_hybrid firewall driver.
it only happens when using the the openvswtich driver."
1815989,2020-10-12 10:14:50 UTC,"After reading through Sean's latest message again, I interpret it as the above mentioned patch only fixes OVS firewall related issues and the issue is still there when running the iptables_hybrid setup."
1815989,2020-10-07 09:51:44 UTC,"Related fix proposed to branch: stable/victoria
Review: https://review.opendev.org/756478"
1815989,2020-10-06 23:01:27 UTC,"Reviewed:  https://review.opendev.org/753314
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c8a819aff4db62e58192af0a272a7f1ce7923146
Submitter: Zuul
Branch:    master"
1815989,2020-10-01 18:26:37 UTC,"Just to shime in, we also have this issue using the hybrid iptables driver. But if https://review.opendev.org/#/c/640258 solves the issue and is backported we are happy :)"
1815989,2020-10-01 14:05:41 UTC,for the hybrid iptables driver os-vif adds a veth pair between the ovs bridge an a linux bridge so teh of-port will not be -1 so it will have no effect in that case.
1815989,2020-09-25 19:30:15 UTC,"@sean-k-mooney - Thanks for the quick response. We're using the hybrid driver, but also experience the RARP issues. However, looking back through this bug, it seems like https://review.opendev.org/#/c/640258 might address our issue, especially since the issue appears to be due to the amount of time it takes to apply the VLAN tag to the OVS port."
1815989,2020-09-25 19:29:25 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/754475"
1815989,2020-09-24 19:46:15 UTC,"we figured out what was cause issue for the neutron openvswitch firewall driver yesterday.
rodolfo has propsoed the testing patch https://review.opendev.org/#/c/753314/ bugfix.
that should allow https://review.opendev.org/#/c/602432/20 to move forward and hopefully merge next week once the neutron patch is merged. the nova patch also requires https://review.opendev.org/#/c/751642/5 which should also be merged shortly."
1815989,2020-09-23 15:33:27 UTC,Also hoping for guidance on how to address this. Thanks!
1815989,2020-09-19 09:41:10 UTC,"Sorry for asking again, do we have a clear path on how to solve this?"
1815989,2020-09-08 10:56:36 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: master
Review: https://review.opendev.org/748296"
1815989,2020-08-26 20:01:06 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/748296"
1815989,2020-08-25 15:38:58 UTC,"Reviewed:  https://review.opendev.org/640258
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7fd2725cb14b81f442eb57a38755829270ff2c43
Submitter: Zuul
Branch:    master"
1815989,2020-08-16 14:40:42 UTC,Rodolfo do you have any clear path on how we can work this bug?
1815989,2020-07-16 19:33:16 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/741529"
1815989,2020-03-24 11:25:41 UTC,"Hi, sean"
1815989,2019-05-29 11:23:45 UTC,"I use some virsh commands to avoid the first situation, modify the migration speed to 1M/s, make sure the flows and tag are configed in br-int before live-migration completed.
# virsh migrate-setspeed instance-0000003b --bandwidth 1
# virsh migrate-getspeed instance-0000003b
# virsh migrate --live --persistent --undefinesource instance-0000003b qemu+tcp://node-3/system"
1815989,2019-05-29 10:50:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661938"
1815989,2019-05-29 11:17:02 UTC,"I think there are 2 problems cause connectivity broken in the live-migration
1. When the VM is migrated to the destination, and the VM send the rarp packets, but because it's too fast, the openflow and tag haven't been configed in br-int, then the rarp packets will be drop."
1815989,2019-02-18 11:00:22 UTC,this happens as a result of the fact that os-vif is currently not plugging the ovs port and that is instead being done by libvirt.
1815989,2019-02-18 20:13:23 UTC,I've added the os-vif component based on Sean's comment.
1815989,2019-02-19 13:46:32 UTC,Thanks Sean for detailing the history around this issue. Let us fix the known issue Sean is aware first.
1815989,2019-02-20 13:05:03 UTC,"Please note the qemu series:
  http://lists.gnu.org/archive/html/qemu-devel/2019-02/msg04128.html"
1815989,2019-03-01 04:54:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640258"
1815989,2019-02-15 15:58:58 UTC,Just want to make sure I understand this correctly after reading the bug you referenced.
1815989,2019-04-19 07:36:49 UTC,so how can we deal with this issue?  @sean mooney
1815989,2019-04-20 21:22:07 UTC,"im going to unabandon the patch i was working on https://review.openstack.org/640258
and try and get back to this over the next 2 weeks or so."
1815989,2019-04-29 08:37:58 UTC,Note that the qemu changes mentioned in #5 are merged into qemu v4.0
1815989,2019-05-29 09:23:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661921"
1815989,2019-04-16 08:46:35 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/640258
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1815990,2019-02-19 15:51:06 UTC,This is a bug that we need to resolve shortly in cloud-init.
1815990,2019-02-15 16:32:21 UTC,"When explicitly configured, cloud-init needs to honor the datasource configuration and ignore any secondary datasource validation on the system. The user told us so, so cloud-init should commit to it."
1815991,2020-03-10 14:11:33 UTC,"Ready for promotion but has gained some depending packages.
I set the status of this MIR here accordingly."
1815991,2020-02-25 10:38:43 UTC,"@james-page - apologies for not looking closer at those unit test ""failures"" - thanks for investigating them and fixing the postinst typo :)"
1815991,2019-04-09 13:09:39 UTC,As we're late in cycle and this is a preview feature for disco/openstack stein happy to defer this until next cycle when we've had more field testing of this feature.
1815991,2020-02-25 10:03:32 UTC,masakari unit test error messages:
1815991,2020-02-25 02:09:05 UTC,"I reviewed masakari-monitors 9.0.0~b1~git2019121714.b717be1-0ubuntu1 as
checked into focal.  This shouldn't be considered a full audit but rather a
quick gauge of maintainability."
1815991,2020-02-25 01:31:07 UTC,"I reviewed masakari 9.0.0~b2~git2020020609.8b122a8-0ubuntu2 as checked into
focal.  This shouldn't be considered a full audit but rather a quick gauge
of maintainability."
1815991,2020-02-05 10:20:49 UTC,"[Summary]
Coming from the same source the review results seemed virtually identical so let us handle it as one."
1815991,2020-02-04 15:51:02 UTC,I hope I find the time to review those two tomorrow morning
1815991,2019-04-23 13:31:39 UTC,"Assigned to James until this testing in the field happened.
Will be switched back to new when it is ready for review later in the 19.10 cycle."
1815991,2020-02-25 10:08:43 UTC,From masakari security review:
1815992,2019-05-30 06:40:29 UTC,"Verified that Ethernet adapter added in manifest.
If the answer for Ethernet adapter was no, the ethernet/detect job were skipped."
1815992,2019-02-19 12:19:44 UTC,My approach to this would be to make two changes:
1815993,2019-02-20 15:20:20 UTC,"On Fri, Feb 15, 2019 at 03:03:34AM -0000, Cheng Chen wrote:

> When the drive-backup is running, I manually crash the iscsi server（or
> interrupt network, eg. iptables -j DROP）.
>
> Then after less than 1 minute：
> virsh qemu-monitor-command ${DOMAIN} --pretty '{ ""execute"": ""query-block"" }' will block and no any response, until timeout. This is still excusable.
> But, the disk（drive-virtio-disk0）will occur the same situation：in vm os, the disk will block and no any response.
>
> In other words, when qemu and iscsi-server lose contact, It will cause
> the vm unable.
"
1815996,2019-02-15 03:18:44 UTC,"The attached screenshot shows what the desktop with the empty window and empty Error box looks like, after going away to a different desktop (to file this bug) and then returning to it.
Part of the window gets erased, but not redrawn with anything, and hence remains blank, and the rest doesn't even get redrawn.
The error box gets erased and redrawn blank."
1815999,2019-02-15 17:35:44 UTC,"I do see a lock being taken and released in asCaStart() and asCaStop() around the signal/wait for asCaTask() to do its thing. This isn't easy to follow and certainly not how I would have written it, but in conjunction with the RCU-like approach to modifying the volatile ASBASE *pasbase in asLibRoutines.c and the LOCK/UNLOCK pair in asInitialize() I suspect there is enough here to prevent races."
1815999,2019-02-16 00:14:11 UTC,"I was looking at asCa.c from the prospective of whether I would use it as a template for some similar code w/ PVA.  Given that asLock isn't exposed outside of asLibRoutines.c, and the whole thing is a singleton anyway, my conclusion is that trying to use 'pasbase' from external code is a bad idea."
1816001,2019-02-15 05:06:17 UTC,Hi Dick-
1816001,2019-02-15 08:12:19 UTC,Yes the algorithm allows this. It even allows cutouts. (The emc shields in the official library use this fact.)
1816001,2019-02-28 19:42:07 UTC,"Tthe nested courtyards are a solution to some problems, its doesn't solve all of them.  I think a flag in the footprint definition in the board something like (drc-ignore a b c) where a, b, and c are drc footprint tests to ignore could prove useful  I actually have a use case were I place a SMT resistor in the middle of an opto-isolator footprint to allow for isolated and non-isolated variants of a design.  Disabling the courtyard drc test in this case would be helpful.  Since this will require a board file format change, it will have to wait until v6 development.  This could be done as part of the v6 DRC changes."
1816001,2019-06-19 08:44:04 UTC,Would it maybe be better to have this as part of DRC instead of the footprint? Maybe a DRC message manager that allows permanently ignoring a specific error message could be the way to go. (It would allow ignoring specific messages that are not connected to a footprint. This might become handy if DRC capabilities are expanded.)
1816002,2019-02-15 13:58:25 UTC,"@Dick, there's a hack that you can use for now as a back door: make sure your Keywords start with ""net tie""."
1816002,2019-02-15 19:07:09 UTC,"@Jeff-  Unfortunately, that hack only works for draw items to pad clearance.  The library solder-bridge footprints are made using custom pads that are overlapping.  And we can't simply mark pad-to-pad in the same footprint as passing without breaking a large usecase for DRC."
1816002,2019-02-15 19:16:41 UTC,Looks like there is already an issue open for this (https://github.com/KiCad/kicad-footprints/issues/1165)  And there is a proposed fix.  It would be good if it were merged for the 5.1 libraries.
1816002,2019-04-27 20:32:31 UTC,"@Seth,"
1816003,2019-02-16 14:07:19 UTC,"Finally i want to know the meaning of run_card missed argument pt_min_pdg. Takes default: i paste run_02_tag_1_debug.log}
#************************************************************
#*               MadGraph5_aMC@NLO/MadEvent                 *
#*                                                          *
#*                *                       *                 *
#*                  *        * *        *                   *
#*                    * * * * 5 * * * *                     *
#*                  *        * *        *                   *
#*                *                       *                 *
#*                                                          *
#*                                                          *
#*         VERSION 2.6.4                 2018-11-09         *
#*                                                          *
#*    The MadGraph5_aMC@NLO Development Team - Find us at   *
#*    https://server06.fynu.ucl.ac.be/projects/madgraph     *
#*                                                          *
#************************************************************
#*                                                          *
#*               Command File for MadEvent                  *
#*                                                          *
#*     run as ./bin/madevent.py filename                    *
#*                                                          *
#************************************************************
generate_events run_02
Traceback (most recent call last):
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1501, in onecmd
    return self.onecmd_orig(line, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1450, in onecmd_orig
    return func(arg, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/madevent_interface.py"", line 2469, in do_generate_events
    self.run_generate_events(switch_mode, args)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/common_run_interface.py"", line 6801, in new_fct
    original_fct(obj, *args, **opts)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/madevent_interface.py"", line 2561, in run_generate_events
    self.exec_cmd('reweight -from_cards', postcmd=False)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1528, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1450, in onecmd_orig
    return func(arg, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/common_run_interface.py"", line 2140, in do_reweight
    reweight_cmd.import_command_file(path)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1643, in import_command_file
    self.exec_cmd(line, precmd=True)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1528, in exec_cmd
    stop = Cmd.onecmd_orig(current_interfa..."
1816003,2019-02-15 08:52:26 UTC,"Hi,"
1816003,2019-02-16 19:36:38 UTC,"Hi,"
1816003,2019-02-16 13:58:08 UTC,"Hi,i am so sorry to answer you too late because i am rusty to linux .I have used the order 'wangxiaiandeAir:Subprocesses liuyiming$ patch -p0 makefile loop_rwgt.patch
patching file makefile'(if i understand your expression correctly),and i launch eezhtest again.wangxiaiandeAir:MG5_aMC_v2_6_0 liuyiming$ ./bin/mg5_amc
For tab completion and history, install module readline.
************************************************************
*                                                          *
*                     W E L C O M E to                     *
*              M A D G R A P H 5 _ a M C @ N L O           *
*                                                          *
*                                                          *
*                 *                       *                *
*                   *        * *        *                  *
*                     * * * * 5 * * * *                    *
*                   *        * *        *                  *
*                 *                       *                *
*                                                          *
*         VERSION 2.6.4                 2018-11-09         *
*                                                          *
*    The MadGraph5_aMC@NLO Development Team - Find us at   *
*    https://server06.fynu.ucl.ac.be/projects/madgraph     *
*                            and                           *
*            http://amcatnlo.web.cern.ch/amcatnlo/         *
*                                                          *
*               Type 'help' for in-line help.              *
*           Type 'tutorial' to learn how MG5 works         *
*    Type 'tutorial aMCatNLO' to learn how aMC@NLO works   *
*    Type 'tutorial MadLoop' to learn how MadLoop works    *
*                                                          *
************************************************************
load MG5 configuration from input/mg5_configuration.txt
fastjet-config does not seem to correspond to a valid fastjet-config executable (v3+). We will use fjcore instead.
 Please set the 'fastjet'variable to the full (absolute) /PATH/TO/fastjet-config (including fastjet-config).
 MG5_aMC> set fastjet /PATH/TO/fastjet-config"
1816003,2019-02-20 02:22:25 UTC,"Hi,"
1816003,2019-02-19 21:58:53 UTC,"sorry,"
1816003,2019-02-19 21:39:12 UTC,Unfortunately it does not contains the reason why it crash at the compilation this time.
1816003,2019-02-19 12:12:37 UTC,"#************************************************************
#*               MadGraph5_aMC@NLO/MadEvent                 *
#*                                                          *
#*                *                       *                 *
#*                  *        * *        *                   *
#*                    * * * * 5 * * * *                     *
#*                  *        * *        *                   *
#*                *                       *                 *
#*                                                          *
#*                                                          *
#*         VERSION 2.6.4                 2018-11-09         *
#*                                                          *
#*    The MadGraph5_aMC@NLO Development Team - Find us at   *
#*    https://server06.fynu.ucl.ac.be/projects/madgraph     *
#*                                                          *
#************************************************************
#*                                                          *
#*               Command File for MadEvent                  *
#*                                                          *
#*     run as ./bin/madevent.py filename                    *
#*                                                          *
#************************************************************
generate_events run_05
Traceback (most recent call last):
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1501, in onecmd
    return self.onecmd_orig(line, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1450, in onecmd_orig
    return func(arg, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/madevent_interface.py"", line 2469, in do_generate_events
    self.run_generate_events(switch_mode, args)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/common_run_interface.py"", line 6801, in new_fct
    original_fct(obj, *args, **opts)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/madevent_interface.py"", line 2561, in run_generate_events
    self.exec_cmd('reweight -from_cards', postcmd=False)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1528, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1450, in onecmd_orig
    return func(arg, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/common_run_interface.py"", line 2140, in do_reweight
    reweight_cmd.import_command_file(path)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1643, in import_command_file
    self.exec_cmd(line, precmd=True)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1528, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File ""/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/madgraph/interface/extended_cmd.py"", line 1450, ..."
1816003,2019-02-19 10:43:48 UTC,"Do you have the compilation error in /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/eezhtest/run_05_tag_1_debug.log ?
If so could you copy it here?"
1816003,2019-02-19 10:29:10 UTC,"Hi,"
1816003,2019-02-19 10:22:49 UTC,"Command ""generate_events run_05"" interrupted with error:
ImportError : No module named allmatrix2py
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in '/Users/liuyiming/Desktop/MG5_aMC_v2_6_5/eezhtest1/run_05_tag_1_debug.log'.
Please attach this file to your report"
1816003,2019-02-19 09:34:22 UTC,"Could you copy-paste the new error message?
In principle this should not be the same one as the original message.
(if you applied the patch correctly)"
1816003,2019-02-19 09:12:06 UTC,Hi
1816003,2019-02-19 08:13:19 UTC,"Hi,"
1816003,2019-02-19 01:38:05 UTC,"Hi,"
1816003,2019-02-18 07:56:30 UTC,"Hi,"
1816003,2019-02-20 07:50:12 UTC,"Hi,"
1816003,2019-02-18 03:20:35 UTC,"Hi,"
1816003,2019-02-21 08:33:39 UTC,"This is not a file, this is the command that you need to run (and that will likely crash) in order to (attempt to ) create the allmatrix2.py.so"
1816003,2019-02-21 08:00:06 UTC,The last line stated that you have created
1816003,2019-02-21 08:10:54 UTC,"wangxiaodiandeMacBook-Air:MG5_aMC_v2_6_0 liuyiming$ cd validation_sa/
wangxiaodiandeMacBook-Air:validation_sa liuyiming$ ls
Cards			SubProcesses		bin
MGMEVersion.txt		TemplateVersion.txt	lib
Source			__init__.py
wangxiaodiandeMacBook-Air:validation_sa liuyiming$ cd SubProcesses/
wangxiaodiandeMacBook-Air:SubProcesses liuyiming$ ls
MadLoop5_resources		check_sa.py
MadLoopCommons.f		coupl.inc
MadLoopParamReader.f		cts_mpc.h
MadLoopParams.dat		cts_mprec.h
MadLoopParams.inc		global_specs.inc
MadLoop_makefile_definitions	makefile
P0_emep_zh_no_g0gpgp		makefileP
__init__.py			mp_coupl.inc
all_matrix.f			mp_coupl_same_name.inc
wangxiaodiandeMacBook-Air:SubProcesses liuyiming$ cd -
/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/validation_sa
wangxiaodiandeMacBook-Air:validation_sa liuyiming$ cd bin
wangxiaodiandeMacBook-Air:bin liuyiming$ ls
internal
wangxiaodiandeMacBook-Air:bin liuyiming$ cd -
/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/validation_sa
wangxiaodiandeMacBook-Air:validation_sa liuyiming$ cd cards
wangxiaodiandeMacBook-Air:cards liuyiming$ ls
MadLoopParams.dat		param_card_default.dat
MadLoopParams_default.dat	proc_card_mg5.dat
ident_card.dat			run_card.dat
param_card.dat			run_card_default.dat
wangxiaodiandeMacBook-Air:cards liuyiming$ cd -
/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/validation_sa
wangxiaodiandeMacBook-Air:validation_sa liuyiming$ cd lib
wangxiaodiandeMacBook-Air:lib liuyiming$ ls
libcts.a	libiregi.a	mpmodule.mod	ninja_lib
libdhelas.a	libmodel.a	ninja_include
wangxiaodiandeMacBook-Air:lib liuyiming$ cd -
/Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/validation_sa
wangxiaodiandeMacBook-Air:validation_sa liuyiming$ cd sourse
-bash: cd: sourse: No such file or directory
wangxiaodiandeMacBook-Air:validation_sa liuyiming$ cd source
wangxiaodiandeMacBook-Air:source liuyiming$ ls
DHELAS		MODEL		coupl.inc	make_opts	makefile
wangxiaodiandeMacBook-Air:source liuyiming$"
1816003,2019-02-21 09:04:30 UTC,"wangxiaodiandeMacBook-Air:SubProcesses liuyiming$ make allmatrix2py.so
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -w -fPIC -ffixed-line-length-132 -O3  -c P0_emep_zh_no_g0gpgp/polynomial.f -o P0_emep_zh_no_g0gpgp/polynomial.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c MadLoopParamReader.f -o MadLoopParamReader.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c MadLoopCommons.f -o MadLoopCommons.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/loop_matrix.f -o P0_emep_zh_no_g0gpgp/loop_matrix.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/improve_ps.f -o P0_emep_zh_no_g0gpgp/improve_ps.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/born_matrix.f -o P0_emep_zh_no_g0gpgp/born_matrix.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/CT_interface.f -o P0_emep_zh_no_g0gpgp/CT_interface.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/loop_num.f -o P0_emep_zh_no_g0gpgp/loop_num.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/helas_calls_ampb_1.f -o P0_emep_zh_no_g0gpgp/helas_calls_ampb_1.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/mp_compute_loop_coefs.f -o P0_emep_zh_no_g0gpgp/mp_compute_loop_coefs.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/mp_helas_calls_ampb_1.f -o P0_emep_zh_no_g0gpgp/mp_helas_calls_ampb_1.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/coef_construction_1.f -o P0_emep_zh_no_g0gpgp/coef_construction_1.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/bin/gfortran-7 -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c P0_emep_zh_no_g0gpgp/loop_CT_calls_1.f -o P0_emep_zh_no_g0gpgp/loop_CT_calls_1.o -I /Users/liuyiming/Desktop/software/MG5_aMC_v2_6_0/HEPTools/include
/usr/local/Cellar/gcc/7.3.0/b..."
1816003,2019-02-21 01:33:22 UTC,"wangxiaodiandeMacBook-Air:MG5_aMC_v2_6_0 liuyiming$ ./bin/mg5_amc
For tab completion and history, install module readline.
************************************************************
*                                                          *
*                     W E L C O M E to                     *
*              M A D G R A P H 5 _ a M C @ N L O           *
*                                                          *
*                                                          *
*                 *                       *                *
*                   *        * *        *                  *
*                     * * * * 5 * * * *                    *
*                   *        * *        *                  *
*                 *                       *                *
*                                                          *
*         VERSION 2.6.4                 2018-11-09         *
*                                                          *
*    The MadGraph5_aMC@NLO Development Team - Find us at   *
*    https://server06.fynu.ucl.ac.be/projects/madgraph     *
*                            and                           *
*            http://amcatnlo.web.cern.ch/amcatnlo/         *
*                                                          *
*               Type 'help' for in-line help.              *
*           Type 'tutorial' to learn how MG5 works         *
*    Type 'tutorial aMCatNLO' to learn how aMC@NLO works   *
*    Type 'tutorial MadLoop' to learn how MadLoop works    *
*                                                          *
************************************************************
load MG5 configuration from input/mg5_configuration.txt
fastjet-config does not seem to correspond to a valid fastjet-config executable (v3+). We will use fjcore instead.
 Please set the 'fastjet'variable to the full (absolute) /PATH/TO/fastjet-config (including fastjet-config).
 MG5_aMC> set fastjet /PATH/TO/fastjet-config"
1816004,2019-03-05 12:50:50 UTC,"would be nice to get a new upstream release, since this commit isn't in a tagged release"
1816004,2019-03-13 15:51:13 UTC,"I just tagged a 1.1.1 release for libglvnd with the AARCH64 and PPC64LE fixes:
https://github.com/NVIDIA/libglvnd/releases/tag/v1.1.1"
1816004,2019-03-26 06:09:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816004,2019-03-28 10:22:29 UTC,"Hi Timo,"
1816004,2019-03-28 11:45:47 UTC,"disco will, it's on the queue and should be accepted after beta freeze is over"
1816004,2019-03-29 00:34:35 UTC,This bug was fixed in the package libglvnd - 1.1.1-0ubuntu1
1816004,2019-04-15 05:55:51 UTC,Thanks Timo.
1816004,2019-04-29 05:31:07 UTC,"Timo,"
1816004,2019-04-29 08:17:25 UTC,"depends on the nature of the backport, I'll ask if we can just update straight to 1.1.1"
1816004,2019-04-29 08:34:59 UTC,Updating to v1.1.1 would be best. Thanks.
1816004,2019-05-10 12:01:29 UTC,Any update here? Thanks!
1816004,2019-05-30 09:21:52 UTC,Is there an update on the inclusion of the fix in bionic-update?
1816004,2019-05-30 09:38:42 UTC,"somehow the upload didn't end up in the queue earlier, but is there now.."
1816004,2019-05-30 14:55:52 UTC,"Hello Sai, or anyone else affected,"
1816004,2019-06-04 09:26:24 UTC,"I have verified that the libglvnd package libglvnd-1.0.0-2ubuntu2.3 fixes the bug for me.
Added the verification-done-bionic tag."
1816004,2019-06-06 09:21:49 UTC,This bug was fixed in the package libglvnd - 1.0.0-2ubuntu2.3
1816004,2019-06-06 09:21:54 UTC,"The verification of the Stable Release Update for libglvnd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1816004,2019-05-10 12:19:24 UTC,"uploaded to bionic-proposed queue, with just the fix added"
1816007,2019-09-23 03:39:32 UTC,"Yeah, this driver is an issue for me too. Took me a while to figure out that it was it that was screwing with my system, because I had kept ticking the ""proprietary drivers"" box during installation.
   The only difference between I can see between our situations is that my HP TouchSmart iq506 has the G988M [GeForce 9300M GS].
   Also to note, my system does work for a very short amount of time after boot. I can even sometimes get to the point of loading up the ""additional drivers"" page, and switching back to the open source driver. But then it all freezes up."
1816014,2019-02-15 10:23:32 UTC,Error also with Fluidstream.net
1816014,2019-02-15 22:04:27 UTC,"I have a dual boot with 18.04, the problem also appeared there. I had found an advice on disabling HPET in the BIOS, but there is no option.
So I tried to enable secure boot (I know it has nothing to do with it), but it seems to me that the error no longer occurs."
1816018,2019-06-05 19:20:03 UTC,"I've also encountered this issue multiple times, except in single player and with normal, manual saves. Looks like it's the same bug though, so I'm posting it here instead of opening a new bug."
1816018,2019-06-05 20:05:23 UTC,I think it's the same issue as in bug 1829848.
1816018,2019-09-15 18:38:38 UTC,Migrated to https://github.com/widelands/widelands/issues/1085
1816018,2019-02-18 23:20:46 UTC,I don't know if this observation helps.
1816018,2019-02-15 19:34:33 UTC,The attached branch will print some debug output from the debug window.
1816018,2019-02-19 06:57:01 UTC,"Yes, this helps. I'll keep digging."
1816018,2019-03-18 07:42:50 UTC,Information from Nordfriese:
1816018,2019-02-24 19:23:30 UTC,Could it be that the game has been reloaded from an emergency save game?
1816018,2019-02-24 22:38:27 UTC,It is what I suspected. This bug can be easily reproduced.
1816018,2019-02-15 14:57:25 UTC,I think a replay would be helpful. So one can see e.g. if some roads were rearranged.
1816018,2019-02-25 06:28:43 UTC,I can reproduce this like you described. This not tribe specific.
1816018,2019-02-25 17:26:11 UTC,"The original savegame is from an emergency save too, so we can reproduce this now. Thanks, Toni!"
1816018,2019-02-26 23:19:57 UTC,IMHO this bug is the last one which needs fixing for build 20.
1816018,2019-03-04 07:27:32 UTC,How did you manage this?
1816018,2019-03-04 08:43:41 UTC,Quite easily. Shall I make a video/replay/savegame?
1816018,2019-03-04 10:14:00 UTC,I just clicked the X in the title bar of the window the client is running in.
1816018,2019-03-05 09:47:08 UTC,I do that too but I can never catch the right moment :(
1816018,2019-03-05 19:26:18 UTC,@GunChleoc which revision are you using? I currently have the same problem with trunk r9007. I cannot reproduce this error. But I'm able to reproduce it with the revision from the linked branch.
1816018,2019-03-06 07:58:39 UTC,hm... couldn't reproduce this with bzr9005 too... but that was a release build. Will try a debug build also.
1816018,2019-03-06 08:29:22 UTC,The bug is magically gone :-)
1816018,2019-03-06 17:18:54 UTC,"It took me 30 minutes or so, but I finally have the debug log. I compiled the linked branch with debug and set the game log to verbose."
1816018,2019-02-19 08:19:27 UTC,Sounds exactly like bug 1797213 'Sometimes ware(s) are lying at a flag and get not transported'
1816018,2019-03-07 14:19:00 UTC,I could not trigger this bug by following the exact steps in your video. I have tried debug and release builds with gcc and clang.
1816018,2019-03-07 12:28:39 UTC,"I dug through the log here is what if found. After the game has been saved all movement for wares get cancelled. The stuck ware is MO(761,grout) which becomes MO(746,grout) after loading the game. The movement gets cancelled once again after the game has been loaded. As far as I understand the log, after destroying the road MO(746,grout) gets cancelled again. I hope this somehow helps."
1816018,2019-03-10 12:28:31 UTC,"I see, well I'll continue testing now that I know where to look :D Do you mind if I merge trunk into this branch?"
1816018,2019-03-10 13:14:56 UTC,"Merging trunk will invalidate the attached savegame, but if you can create a new savegame, that won't be a problem."
1816018,2019-03-10 06:42:49 UTC,"It will not show on screen yet, unfortunately - you will have to check the console log."
1816018,2019-03-09 14:09:06 UTC,None of this shows up here... please have a look at the attached screenshot. Am I doing something wrong?
1816018,2019-03-09 11:29:50 UTC,"When clicking ""constructionsite"" in the building's debug window:"
1816018,2019-03-16 10:45:33 UTC,Looks like this happens also in singleplayer games (r9007): https://wl.widelands.org/forum/post/27311/
1816018,2019-03-09 09:22:47 UTC,I totally agree. We could add a known issues/bug section to the release notes and since we know how to workaround this issues we could list this as well.
1816018,2019-03-08 17:33:25 UTC,Agreed.
1816018,2019-03-07 15:02:07 UTC,"Yes, it is very hard to trigger the right moment for this bug to appear. I guess I just got lucky on the first try. If you need more savegames later on, to test your fix, let me know."
1816018,2019-03-08 06:30:24 UTC,"The extra logging is only triggered by the debug window, so it will be hard to get anything from there, since it takes a split second already to trigger the bug at all."
1816018,2019-03-09 09:41:06 UTC,"Just one question. What exactly does the log you added output? I can't find any ware-specific output when I open the debug windows for roads/flags or construction sites. Also when I click on the button in the windows it just shows ""Flag at XX/YY"" or ""this: 0x....."" for roads and buildings..."
1816018,2019-03-08 09:26:29 UTC,Just my 5 cents:
1816019,2019-02-26 15:17:17 UTC,Could you please share the tacker server logs.
1816022,2020-03-23 14:11:28 UTC,"The patches have been merged, the issue is no longer occurring."
1816022,2019-02-27 11:26:24 UTC,need this series to be merged for this bug - https://review.openstack.org/#/q/topic:bug/1816022+(status:open+OR+status:merged)
1816022,2019-02-27 11:15:36 UTC,"yeah, that is overridden by configre_tempest where we used the upper_constarint from master. We can make install_tempest also use master one to avoid duplication of uninstall/install."
1816022,2019-02-27 05:56:00 UTC,RE on your latest comment:
1816022,2019-02-27 05:23:31 UTC,Let me understand it clearly.
1816022,2019-02-20 11:28:48 UTC,"The backport was merged, so now  tempest list-plugins is correctly executed."
1816022,2019-02-15 18:39:21 UTC,It looks like the following bug and patch may be related:
1816022,2019-02-19 10:15:22 UTC,The backport has been already proposed last year but it got stuck due to a flaky test; now it's time recheck it.
1816022,2019-02-19 10:05:25 UTC,The reason may be traced back to the lack of the following devstack patch in stable/pike:
1816022,2019-02-27 08:46:47 UTC,But also tempest itself is installed using the requirements from the branch. See the content of install_tempest():
1816023,2019-02-15 13:25:45 UTC,All the log files required are in the attachment.
1816023,2019-02-15 10:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816024,2019-02-15 09:53:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816024,2019-02-15 09:48:45 UTC,See also bug #1210138.
1816024,2019-05-09 22:29:06 UTC,update-notifier is part of the designed experience of the Ubuntu Desktop and it should not be necessary to remove it to address the issues you've identified.  Reassigning to update-notifier.
1816034,2019-02-15 14:46:38 UTC,Are you setting [workarounds]/report_ironic_standard_resource_class_inventory=False? I assume so since you said you migrated your flavors and nodes so that scheduling for those baremetal nodes should only use the custom resource class from the ironic node (and flavor).
1816034,2019-02-15 14:47:49 UTC,Correction:
1816034,2019-02-15 14:56:18 UTC,Maybe that won't work because then old instance allocations won't be reported to placement which would re-introduce bug 1724589:
1816034,2019-02-15 16:07:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637217"
1816034,2019-02-15 16:11:33 UTC,I've removed Pike and Queens from this since those are lower priority since https://review.openstack.org/#/q/Id3c74c019da29070811ffc368351e2238b3f6da5 hasn't landed on those branches.
1816034,2019-10-22 14:32:34 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/637217
Reason: I'm not actively working on this, someone else should pick it up."
1816034,2019-02-15 14:46:53 UTC,"(8:38:42 AM) mriedem: belmoreira: and you have this enabled yes? https://review.openstack.org/#/c/609043/
(8:38:53 AM) mriedem: which is probably why the ironic driver isn't reporting standard resource class inventory
(8:44:45 AM) mriedem: i wonder if we should just set IronicDriver.requires_allocation_refresh = not CONF.workarounds.report_ironic_standard_resource_class_inventory
(8:45:11 AM) mriedem: because if we're not going to report the standard inventory we shouldn't try to put allocations for those standard inventory resource classes
(8:46:23 AM) openstackgerrit: Merged openstack/nova master: Libvirt: do not set MAC when unplugging macvtap VF  https://review.openstack.org/624842
(8:46:34 AM) belmoreira: mriedem: is set to False"
1816038,2019-02-15 15:03:25 UTC,"> We don't even know what the printer is....
"
1816038,2019-02-18 10:29:43 UTC,No problem! Thank you that you are asking again.
1816038,2019-02-15 16:16:57 UTC,"Apologies for the false start, but the other information would still be useful."
1816038,2019-02-15 14:18:10 UTC,Not a clue. We don't even know what the printer is or whether it happens with all PDFs or when printing from an application like Firefox!
1816038,2019-02-18 12:05:29 UTC,"Hello Jean,"
1816040,2019-02-22 15:48:26 UTC,Here is the debdiff in case it could help the maintainers to solve the bug.
1816040,2019-03-15 00:30:32 UTC,"Hi Eduardo,"
1816040,2019-03-11 14:42:13 UTC,"Hey Alejandro,"
1816040,2019-02-22 16:19:54 UTC,"The attachment ""1.7.2-2ubuntu1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1816040,2019-04-20 20:10:20 UTC,Unsubscribing the Ubuntu Security Sponsors Team as there is nothing left to sponsor.
1816043,2019-02-16 13:13:42 UTC,"Have you installed an emoji font to ~/.fonts? In that case, LO won’t read it until bug 1703638 is fixed."
1816043,2019-02-19 16:14:22 UTC,"I have not installed any additional emoji font, there should already one be bundled with LibreOffice at version 5.3 and earlier, see release notes:"
1816043,2019-02-19 19:12:47 UTC,"*5.3 and later, not earlier. Sorry."
1816043,2021-01-23 04:18:34 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1816043,2020-11-23 09:43:35 UTC,Thank you for your bug report. Could you try if that's still an issue for you? Copying those emojis to a writter document in the current version renders correctly
1816045,2019-02-15 13:45:42 UTC,Update affected package
1816045,2020-09-02 22:04:50 UTC,"so the mtime is set to the one mentioned inside the changelog, ""Fri, 19 Oct 2018 11:20:34 -0700"" and that's what's included in the package, and by Debian Policy, one should maintain the timestamps as much as possible."
1816045,2020-09-04 08:09:20 UTC,"Thanks for explaining. I am using an internally developed, Python-based backup system. It makes backups from Btrfs snapshots and regularly verifies the integrity of the entire restore process. The verification shows discrepancies such as the one above."
1816047,2019-02-15 15:02:00 UTC,I decided to uncheck all the boxes and after running the final two commands everything seemed to run pretty normally except for this error:
1816047,2019-02-16 04:34:47 UTC,"Hi Mark,
Try this"
1816047,2019-02-15 14:49:28 UTC,Are they all 3rd party repositories?
1816047,2019-02-15 14:39:22 UTC,"Hi Mark,"
1816047,2019-02-19 05:37:10 UTC,"Hi Lakhan,"
1816048,2019-02-15 14:19:45 UTC,"Exception caught in process_line:
Traceback (most recent call last):
  File ""/usr/lib/ubiquity/ubiquity/filteredcommand.py"", line 145, in process_line
    return self.dbfilter.process_line()
  File ""/usr/lib/ubiquity/ubiquity/debconffilter.py"", line 374, in process_line
    progress_info):
  File ""/usr/lib/ubiquity/ubiquity/filteredcommand.py"", line 456, in progress_info
    self.description(progress_info))
  File ""/usr/lib/ubiquity/ubiquity/filteredcommand.py"", line 324, in description
    return misc.utf8(self.db.metaget(question, 'description'),
  File ""/usr/lib/python3/dist-packages/debconf.py"", line 83, in <lambda>
    lambda *args, **kw: self.command(command, *args, **kw))
  File ""/usr/lib/python3/dist-packages/debconf.py"", line 87, in command
    self.write.write(""%s %s\n"" % (command, ' '.join(map(str, params))))
ValueError: I/O operation on closed file."
1816048,2019-02-18 14:11:23 UTC,"I can confirm this issue also happens to me, only using UEFI installation."
1816049,2019-05-14 16:09:51 UTC,done in eoan
1816054,2019-02-15 14:58:39 UTC,"Original specification: https://review.openstack.org/#/c/311268/
Specification removal due to inactivity: https://review.openstack.org/#/c/439194/"
1816054,2019-02-15 14:59:49 UTC,Patches that attempt to implement this functionality:
1816066,2019-02-15 15:15:44 UTC,The first step can be to add new roles for controller and keystone node to devstack-gate: https://review.openstack.org/#/c/394895
1816076,2020-04-10 11:02:41 UTC,"Reviewed:  https://review.opendev.org/448755
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=1627c28282c832f4fb837e2c445ed74d0ad3c68b
Submitter: Zuul
Branch:    master"
1816076,2020-04-10 11:02:46 UTC,"Reviewed:  https://review.opendev.org/448765
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=e723a1c16ebe04c927216a64f1025118f0094df1
Submitter: Zuul
Branch:    master"
1816076,2020-04-10 10:54:04 UTC,"Reviewed:  https://review.opendev.org/448730
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=652f02c8b50e20be3df562099869be3a391335c4
Submitter: Zuul
Branch:    master"
1816076,2019-12-13 16:20:45 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/698950"
1816076,2020-04-07 15:41:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/718153"
1816076,2020-01-28 17:14:52 UTC,"Reviewed:  https://review.opendev.org/698950
Committed: https://git.openstack.org/cgit/openstack/keystone-specs/commit/?id=569101e9ab51ccb406a93f0d101c7b4c402e4f18
Submitter: Zuul
Branch:    master"
1816076,2019-05-17 20:22:02 UTC,"Reviewed:  https://review.opendev.org/653492
Committed: https://git.openstack.org/cgit/openstack/keystone-specs/commit/?id=9ecdbc980231ef6d80ff785c41912f64a3eab2cd
Submitter: Zuul
Branch:    master"
1816076,2019-02-15 15:25:03 UTC,"Specification review: https://review.openstack.org/#/c/397410/
Specification doc: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/support-federated-attr.html"
1816076,2019-04-17 17:05:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653492"
1816076,2019-02-15 15:28:17 UTC,Patches that work towards this initiative:
1816076,2020-04-10 05:22:06 UTC,"Reviewed:  https://review.opendev.org/718153
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d23965aaf1920bd8f3231ef73ab6baa408f34b5d
Submitter: Zuul
Branch:    master"
1816086,2019-09-27 09:01:55 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1816086,2019-08-12 21:11:23 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1816086,2019-08-12 20:41:33 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1816086,2019-02-15 17:12:12 UTC,Talked this over with Belmiro in IRC [1].
1816086,2019-07-24 20:20:24 UTC,"Reviewed:  https://review.opendev.org/670179
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=754d8eb76c6fcd539fc2c32f0e2f90f6503b9f0c
Submitter: Zuul
Branch:    stable/stein"
1816086,2019-07-10 20:11:48 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/670179"
1816086,2019-02-15 17:04:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637225"
1816086,2019-07-10 15:21:18 UTC,"Reviewed:  https://review.opendev.org/637225
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8c797450cbff5194fb6791cd0a07fa060dc8af72
Submitter: Zuul
Branch:    master"
1816086,2019-08-01 19:49:29 UTC,"Reviewed:  https://review.opendev.org/670182
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=00e5e3a7443dd31720244497013b040729490dcd
Submitter: Zuul
Branch:    stable/rocky"
1816086,2019-07-10 20:22:59 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/670182"
1816090,2019-02-15 16:18:13 UTC,"Just found out, that you can make Firefox play that video by pressing 'Pause' and afterwards 'Play', when it halts. I think, it looks like a timing issue in Firefox itself. Still it is very confusing for a user and I had the same problem trying to play voice maWhatsapp"
1816097,2019-02-15 15:50:04 UTC,Specification: https://review.openstack.org/#/c/332940/
1816097,2019-05-04 16:36:10 UTC,Specification for the nested domain for inherited assignments into child domains: https://review.openstack.org/#/c/332940/
1816098,2019-02-25 10:19:08 UTC,"'permanently impossible' is a case where we were able to successfully
connect to a controller, but when we try to login with the credentials we
have, we are told that those credentials are not valid.
I believe the teardown existed for the manual provider case, if you had a
machine that was down, and the controller was destroyed, it wouldn't clean
up until the machine started again. We can certainly reevaluate the
position."
1816105,2019-02-15 16:08:33 UTC,"Specification review: https://review.openstack.org/#/c/148730/
Specification doc: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/mitaka/tree-deletion.html"
1816105,2019-02-15 16:13:22 UTC,Patches the work towards this initiative:
1816107,2019-02-15 16:16:28 UTC,"Specification review: https://review.openstack.org/#/c/131531/
Specification doc: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/alembic.html"
1816107,2019-02-15 16:17:37 UTC,Patches that work towards this initiative:
1816107,2019-06-11 10:35:02 UTC,"Now we have two commands that are related to migrations -- db_sync to migrate and db_version to show the current version. It works OK with sqlalchemy-migrate, but not with Alembic that we will be using. What needs to be done is to create a set of commands - ""db upgrade/downgrade/stamp/revision/version"". It will comply with alembic commands and with oslo.db migration_cli interface."
1816109,2019-02-15 16:21:53 UTC,"Specification review: https://review.openstack.org/#/c/173424/
Specification doc: https://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/materialize-project-hierarchy.html"
1816109,2019-02-15 16:23:37 UTC,The following patches work towards this initiative:
1816111,2020-01-11 04:17:30 UTC,[Expired for kolla because there has been no activity for 60 days.]
1816111,2019-11-11 15:29:38 UTC,"Hi,"
1816111,2019-09-12 14:18:18 UTC,"Does this bug still occur on latest code?
If yes - please upload:
- cinder logs from /var/log/kolla/cinder/*
- docker logs cinder_*
- cinder configuration from /etc/kolla/config/cinder*"
1816115,2019-02-15 16:38:32 UTC,"Specification review: https://review.openstack.org/#/c/189816/
Specification doc: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/unified-delegation.html"
1816115,2019-02-15 16:41:57 UTC,"The following patches work towards this initiative, or its dependencies:"
1816120,2019-02-15 16:45:39 UTC,"Specification review: https://review.openstack.org/#/c/395841/
Specification doc: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/devstack-plugin.html"
1816120,2019-02-15 16:46:44 UTC,"Added keystone identity provider installation to Devstack plugin: https://review.openstack.org/484121
Only upload SP metadata to testshib.org if IDP id is testshib: https://review.openstack.org/545471
Copy shibboleth logs in v3 functional jobs: https://review.openstack.org/580401"
1816125,2019-09-06 22:00:58 UTC,It still affects me despite the updates. Every single time I boot.
1816125,2019-11-06 04:17:41 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1816130,2019-02-16 16:48:32 UTC,What was the result of upping ulimit to a reasonable size as suggested?
1816130,2019-02-17 00:39:08 UTC,that makes it work - as I wrote on the mailing ist.
1816136,2019-02-15 17:05:33 UTC,Please find the changes that I have made and the same working fine. Would it be good to have one ?. I am using for my current project and is helpful. So thought of contributing the same..
1816158,2019-02-15 17:31:20 UTC,Specification review: https://review.openstack.org/#/c/147548/
1816158,2019-06-11 10:36:50 UTC,We will track this in [1]. Thus marking this as duplicate of [1].
1816160,2019-02-15 17:35:55 UTC,"Context from the blueprint, while it was still active:"
1816160,2019-02-15 17:34:50 UTC,Specification review: https://review.openstack.org/#/c/324552/
1816160,2019-02-15 17:37:32 UTC,"This bug actually has some overlap with another bug report [0]. In addition to fixing [0], we could extend support and scope checking of the mapping API to open this functionality up to domain users."
1816165,2019-02-15 17:50:11 UTC,"Specification review: https://review.openstack.org/#/c/188534/
Specification doc: http://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/service-providers-filters.html"
1816165,2019-02-15 17:51:43 UTC,Patches that work toward this initiative:
1816166,2019-02-15 17:55:30 UTC,Specification review: https://review.openstack.org/#/c/186979/
1816166,2019-02-15 17:55:46 UTC,Proposed solution: https://review.openstack.org/#/c/310074/
1816171,2019-02-15 19:47:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816171,2019-02-16 00:18:51 UTC,"Thanks for the report! I can confirm this; forwarded to:
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/81"
1816177,2019-02-20 07:29:09 UTC,to make my question more clear:
1816177,2019-07-15 15:37:49 UTC,Verification passed on AIO-SX system on master 20190713T013000Z.
1816177,2019-02-15 19:46:48 UTC,Marking as release gating; related to containers; specific to AIO-SX
1816177,2019-06-11 14:58:06 UTC,"Reviewed:  https://review.opendev.org/663286
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=884fbc92adfa3a2b5f6c2e8fc008b046e8f94dbe
Submitter: Zuul
Branch:    master"
1816177,2019-06-05 09:34:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/663286"
1816177,2019-06-04 01:37:23 UTC,Paste Emails here:
1816177,2019-06-03 15:33:52 UTC,Ran mentioned that this issue is now being worked by Yan
1816177,2019-02-20 07:23:05 UTC,"Hi Yang, I'm trying to reproduce this issue.
When I unlock my controller after configure the controller(not apply the application yet), all k8s_* containers fail to run which run well before unlock."
1816177,2019-05-28 15:59:12 UTC,Raising the priority as this appears to be reported regularly from All-in-one Simplex testing in WR labs
1816177,2019-05-24 17:30:56 UTC,"Issue was reproduced on
Lab: SM_2
Load: 2019-05-23_18-37-00"
1816177,2019-05-30 07:26:24 UTC,"Change abandoned by Ran An (<email address hidden>) on branch: master
Review: https://review.opendev.org/646031
Reason: this workaround do not work on latest code base"
1816177,2019-04-02 02:00:03 UTC,#13 is reported as https://bugs.launchpad.net/starlingx/+bug/1822697
1816177,2019-02-20 19:53:30 UTC,"Hi Ran, I did not see the issue you encountered."
1816177,2019-02-15 19:47:22 UTC,Assigning to Cindy as a good learning opportunity
1816177,2019-02-28 02:19:28 UTC,"Hi Yang. sorry to reply so late. Could you help and run attached verify script on your env, when stx-openstack application gone into apply-failed status after unlock controller?"
1816177,2019-03-11 16:21:54 UTC,"I reproduced this issue by image made in March 5th on master branch (after stein is merged).
I found it was container ""armada_service"" fail to run armada cmd during re-apply application process after unlock controller made application apply failed. By analyzing container's log (following) , it is an issue of docker generating ""docker run"" with existing container[1]."
1816177,2019-02-22 02:22:04 UTC,Thanks Yang. I'll check my env and show it if there are any progress or questions.
1816177,2019-03-19 02:28:27 UTC,follow #8
1816177,2019-03-24 06:49:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/646031"
1816177,2019-03-26 08:06:24 UTC,verification on latest code base was failed.
1816177,2019-03-28 07:36:13 UTC,"the sm will disable/enable serial of services during boot process when it is ready, including services sysinv-inv(trigger application reapply), sysinv-conductor(download images and start armada container) and docker-distribution(besides local registry for docker)."
1816177,2019-03-15 17:45:18 UTC,"by bind a directory[1] instead of a file[2], the container error mentioned above is solved."
1816177,2019-04-10 08:28:35 UTC,https://bugs.launchpad.net/starlingx/+bug/1822697 is solved. but the verify base on latest code is still failed.
1816180,2019-02-15 19:57:28 UTC,Patch ready for review:
1816180,2019-05-15 19:01:01 UTC,Test on current master.  The patch works perfectly.  The signed-off branch is at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1816180_pending_patron_address_type-signoff
1816180,2019-05-30 17:42:31 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Terran and Garry!"
1816184,2019-02-15 22:06:12 UTC,"Rebooted and reinstalled.
Using different order for selecting ESP/efi partition it worked without error on not using sda, but installed to ESP on sda.
Install log showed this:"
1816187,2019-02-19 15:54:37 UTC,"Thanks for filing this bug. Is there a particular reason you want this 0.101.1 version, or is this just a request for a normal upgrade?"
1816187,2019-08-31 08:44:38 UTC,Now available in Ubuntu Eoan https://launchpad.net/ubuntu/+source/clamav/0.101.4+dfsg-1ubuntu1
1816187,2019-04-21 18:25:49 UTC,"I am not sure about the original reason an upgrade was requested, but two other packages now build depend on libclamav-dev >= 0.101.1 (see bug 1825737)"
1816188,2019-09-19 14:54:25 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1816189,2019-02-15 21:04:38 UTC,Adding System Information
1816189,2019-02-15 21:06:39 UTC,"Before kernel 4.20.x this was not an issue as nested virtualization was not enabled by default. In any distribution using 4.20.x or later, snapshots and migration do not work."
1816189,2021-02-17 08:20:15 UTC,"Can you still reproduce this issue with the latest version of QEMU and libvirt? Anyway, since the problem occurs with libvirt, have you already tried to report this issue to the libvirt project instead?"
1816196,2019-02-16 00:21:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1816196,2019-02-16 03:25:24 UTC,"My post says pretty clearly what package is the problem. But it also says
that the problem arises from a choice made by Ubuntu in which version to
include."
1816196,2019-03-08 08:21:58 UTC,"There have been similar problems, which have been recently fixed as described here:
https://bugs.kde.org/show_bug.cgi?id=393478 and duplicates"
1816196,2019-03-08 08:22:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816197,2019-03-19 17:34:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816198,2020-07-27 04:08:57 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1816198,2020-01-21 15:46:47 UTC,"Thanks for the update and the confirmation. Seems to be related to Bug 1858670 which although filed under 'xfburn' package, seems to have the same symptoms and possibly the same cause."
1816198,2020-01-21 04:15:08 UTC,Lubuntu 18.04.4 QA-test install on hp dx6120mt (box mentioned in last comment)
1816198,2019-02-17 03:06:39 UTC,Thanks Glenn.
1816198,2019-02-16 21:02:54 UTC,"Hi Chris, thanks for your interest. First, a family emergency just popped
up that will require all my time for about the next week, so there's that.
Secondly, 'open & re-close' tray function appears to work properly with
pcmanfm; what does not seem to work properly is xfburn writing correctly to
the CD. Using my 32-bit notebook & Lubuntu 18.04.1 + updates, I attempted
to make an audio CD-R with 8 tracks but failed to complete the burns for 2
CD-R's, even thought the audio files are fine playing with VLC from the
HDD. Next, I tried burning the same audio tracks with xfburn to an audio
CD-R on my 64-bit Lubuntu 18.04.1 + updates notebook; this time the CD burn
completed but the audio tracks have a number of 'skips' in the audio. This
may very well be an issue with xfburn, but since the initial indication of
something out of the ordinary is with pcmanfm, I thought it might be some
kind of CD mounting or dependency issue in pcmanfm."
1816198,2019-02-15 23:29:30 UTC,"I booted up Lubuntu 18.04 (x86_64) LTS and inserted a blank dvdr & two folder-icons appeared titled ""Blank CD-R Disc"" appeared, plus a option-dialog titled ""Removable media is inserted"" asking if I want to open in Xfburn or File.Manager."
1816200,2019-02-15 23:27:11 UTC,Mozilla Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1383563.
1816201,2019-02-15 23:44:19 UTC,Same bug in RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=1667308
1816204,2019-02-19 15:57:14 UTC,Can you try this with node 6?
1816204,2019-02-21 10:27:04 UTC,Node 8.15.0 failed in the same way. I will try with node 6 next.
1816204,2019-02-21 11:31:17 UTC,"Node 6 fails in a slightly different place, but the solution is the same:
build-environment:
      - SUDO_GID: ""0""
      - SUDO_UID: ""0"""
1816204,2019-10-24 19:02:50 UTC,This PR should resolve this issue: https://github.com/snapcore/snapcraft/pull/2747
1816205,2019-02-18 20:52:02 UTC,Saving text file and disappearing from desktop
1816205,2019-02-21 17:36:06 UTC,Any solution for this case? The problem still continues.
1816205,2019-02-26 19:45:16 UTC,"Any solution for this case? The problem still continues, see attachment"
1816205,2019-03-03 19:38:21 UTC,Hello guys
1816205,2019-02-26 19:43:45 UTC,"Any solution for this case? The problem still continues, see attachment"
1816205,2019-03-06 12:33:43 UTC,Hello guys
1816205,2019-04-14 15:44:13 UTC,Hello guys
1816205,2019-05-17 07:25:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816205,2019-02-18 20:49:28 UTC,Hi Sebastian
1816205,2019-03-03 20:08:01 UTC,Recorded by cell phone got a little better
1816205,2019-02-18 20:17:52 UTC,Could you try to move the content of your Desktop directory somewhere else and just add a text file and see if you still get the problem? Also what monitors config do you use?
1816205,2019-02-18 17:17:30 UTC,"Hello Sebastian,"
1816205,2019-02-18 17:20:27 UTC,But the above images show the two situations:
1816205,2019-02-18 17:21:17 UTC,Icons disappear after clicking save in gedit or image capture
1816205,2019-02-18 16:04:48 UTC,"Do you have the desktop staying empty until you do an action again or just for a second or so? If it's staying empty, does it make a difference it you move the content of the desktop view somewhere else and only try with a text example?"
1816205,2019-02-18 07:54:00 UTC,"You can probably just wait at this point, if we have extra questions we will comment here"
1816205,2019-02-17 17:56:46 UTC,Hi Sebastien Bacher
1816205,2019-02-17 17:27:54 UTC,The log has those errors
1816205,2019-02-17 10:58:31 UTC,Hi Sebastian
1816205,2019-02-17 10:32:13 UTC,"Thank you for your bug report, could you attach a journalctl log after getting the issue?"
1816205,2019-02-15 23:59:02 UTC,n this case it was possible to use ubuntu -bug -w normally to generate the report as it was available and opened on the desktop.
1816206,2019-02-17 10:30:55 UTC,"Thank you for your bug report, could you also sent it upstream on https://gitlab.gnome.org/GNOME/gnome-disk-utility/ ?
It would be useful to have your journalctl log from around the time you did the change"
1816210,2019-02-19 15:12:33 UTC,"Thank you for filing this bug, this is an issue and cloud-init will need to properly parse link/void interface types"
1816214,2019-02-16 05:11:13 UTC,"After some more playing around, I realized that I was slightly off in my initial analysis.  It's not /etc/fstab that it obtains the /dev/vg/* references from, but lvdisplay:"
1816221,2019-04-02 06:32:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816222,2019-02-20 19:19:38 UTC,apport information
1816222,2019-02-20 19:19:25 UTC,apport information
1816222,2019-02-20 19:19:26 UTC,apport information
1816222,2019-02-20 19:19:27 UTC,apport information
1816222,2019-02-20 19:19:28 UTC,apport information
1816222,2019-02-20 19:19:29 UTC,apport information
1816222,2019-02-20 19:19:30 UTC,apport information
1816222,2019-02-20 19:19:32 UTC,apport information
1816222,2019-02-20 19:19:33 UTC,apport information
1816222,2019-02-20 19:19:35 UTC,apport information
1816222,2019-02-20 19:19:37 UTC,apport information
1816222,2019-02-20 19:19:23 UTC,apport information
1816222,2019-02-20 19:19:39 UTC,apport information
1816222,2019-02-20 19:19:36 UTC,apport information
1816222,2019-02-21 05:39:52 UTC,"x@x-Inspiron-15-7000-Gaming:~/Documents$ dkms status
x@x-Inspiron-15-7000-Gaming:~/Documents$ dpkg -l | grep nvidia
rc  libnvidia-compute-390:amd64                  390.77-0ubuntu0.18.04.1                      amd64        NVIDIA libcompute package
rc  libnvidia-compute-390:i386                   390.77-0ubuntu0.18.04.2                      i386         NVIDIA libcompute package
rc  libnvidia-compute-396:i386                   396.24-0ubuntu0~gpu18.04.1                   i386         NVIDIA libcompute package"
1816222,2019-02-21 05:42:12 UTC,BTW Since the update I am getting an error message on login which may not be related to this issue:
1816222,2019-02-21 05:42:38 UTC,And also
1816222,2019-02-21 05:44:47 UTC,`dkms status` didn't yield anything or I don't know what I am doing.
1816222,2019-02-21 09:37:44 UTC,"Please add ""blacklist nouveau"" to /etc/modprobe.d/blacklist.conf, run `update-initramfs -u -k all`, then reboot."
1816222,2019-02-21 19:28:43 UTC,I can boot with the official 4.18 kernel but the external monitor is no longer detected.
1816222,2019-02-22 06:18:16 UTC,I went on I installed the recommended PPA nvidia driver 415 rebooted. Got a few graphics and mouse clicking glitches.
1816222,2019-03-30 06:09:10 UTC,"After the last big update - I am unable to boot to desktop unless in safe mode. No matter what kernel I use.
At least previously 4.15 worked.
I tried the Beta 19.04 live usb it booted very slowly and hanged."
1816222,2019-04-02 06:43:08 UTC,I don't see this issue after install Ubuntu Bionic Daily (which uses 4.18 kernel) + Nvidia driver on Inspiron 7567.
1816222,2019-04-07 05:12:20 UTC,At the moment I am inclined to wait for the 19.04 release before I try again.
1816222,2019-04-09 06:12:06 UTC,"Boot with `nomodeset`, run `sudo ubuntu-drivers autoinstall` then everything works."
1816222,2019-02-20 19:19:22 UTC,apport information
1816222,2019-02-20 22:46:58 UTC,"Okay, since it's ""Inspiron 15 7000 Gaming"", so I think we should focus on make the proprietary Nvidia driver works."
1816222,2019-02-20 19:16:06 UTC,apport information
1816222,2019-02-20 19:15:00 UTC,apport information
1816222,2019-02-20 19:16:03 UTC,apport information
1816222,2019-02-16 08:58:15 UTC,The b
1816222,2019-02-16 09:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816222,2019-02-20 13:05:08 UTC,Do older 4.18 releases have this issue?
1816222,2019-02-20 19:05:43 UTC,apport information
1816222,2019-02-20 19:05:44 UTC,apport information
1816222,2019-02-20 19:14:05 UTC,"I just tried 4.18.0 it won't boot either. I also noticed while installing it an error message of the sort: ""missing nouveau firmware"".
Well, that's it! Nouveau fails to start."
1816222,2019-02-20 19:14:56 UTC,apport information
1816222,2019-02-20 19:14:57 UTC,apport information
1816222,2019-02-20 19:16:05 UTC,apport information
1816222,2019-02-20 19:14:59 UTC,apport information
1816222,2019-02-20 19:15:01 UTC,apport information
1816222,2019-02-20 19:15:03 UTC,apport information
1816222,2019-02-20 19:15:04 UTC,apport information
1816222,2019-02-20 19:14:58 UTC,apport information
1816222,2019-02-20 19:16:02 UTC,apport information
1816222,2019-02-20 19:15:48 UTC,apport information
1816222,2019-02-20 19:16:01 UTC,apport information
1816222,2019-02-20 19:16:00 UTC,apport information
1816222,2019-02-20 19:15:58 UTC,apport information
1816222,2019-02-20 19:15:56 UTC,apport information
1816222,2019-02-20 19:15:57 UTC,apport information
1816222,2019-02-20 19:15:54 UTC,apport information
1816222,2019-02-20 19:15:52 UTC,apport information
1816222,2019-02-20 19:15:51 UTC,apport information
1816222,2019-02-20 19:15:49 UTC,apport information
1816222,2019-02-20 19:15:55 UTC,apport information
1816226,2019-02-18 20:56:32 UTC,Installing the following packages from Cosmic re-produced the plugin libm problem:
1816226,2019-02-18 19:40:56 UTC,"> I did
>
>  apt purge libsane-hpaio libhpmud0 hplip-data hplip printer-driver-postscript-hp
"
1816226,2019-02-18 19:56:05 UTC,Apologies: I have just noticed I put
1816226,2019-02-18 20:33:25 UTC,"> apt purge hplip
"
1816226,2019-02-18 23:14:27 UTC,"Ok, we have resolved your printing issue but lack of scanning remains. I am mystified.
I have dealt with your printer type previously and met similar problems. Some involvement from HPLIP upstream would be appreciated."
1816226,2019-02-20 12:00:02 UTC,"> After that and using your scanimage command, there is success!
"
1816226,2019-02-18 23:51:55 UTC,"Your device has a ""Scan to Network Folder"" feature. See the manual. It could be useful."
1816226,2019-02-19 00:02:03 UTC,"Hi Peter,"
1816226,2019-02-19 15:37:31 UTC,"Peter,"
1816226,2019-02-19 23:18:01 UTC,"I tried this before, but not recently."
1816226,2019-02-18 19:12:32 UTC,"> After adding the printer ID to /usr/share/hplip/data/models/models.dat
> scanimage -L reports a scanner with URI
>
> device `hpaio:/net/colorlaserjet_mfp_m278-m281?ip=192.168.0.88&queue=false'
> is a Hewlett-Packard colorlaserjet_mfp_m278-m281 all-in-one
"
1816226,2019-02-18 23:40:26 UTC,"> Yes, I did that, it was part of my huge purge command.
"
1816226,2019-02-18 18:44:44 UTC,@ Comment #9
1816226,2019-02-18 19:10:51 UTC,@ Comment #10
1816226,2019-02-18 13:59:17 UTC,"I forgot to say: the scanimage command should also be tried without the -d option both times,"
1816226,2019-02-16 20:08:34 UTC,Have I missed something? Your account appears to have no mention of the printer model.
1816226,2019-02-16 20:43:55 UTC,I have a MFP M281fdw scanner/colorlaser combination.
1816226,2019-02-16 23:20:29 UTC,"Knowing the printer is always useful and it means that certain things can be worked. For example, we now know the printer does not require a plugin."
1816226,2019-02-17 15:33:14 UTC,To answer your question: there is currently no USB connection but I could try to connect it temporarily if that would help you to gain some insights.
1816226,2019-02-17 17:29:16 UTC,"No, a network connection is fine; best, in fact."
1816226,2019-02-17 15:22:13 UTC,Thank you.
1816226,2019-02-17 21:44:12 UTC,"I have a small addition: when trying xsane, the journal shows the following messages:"
1816226,2019-02-18 11:38:37 UTC,"> It says that for scanning, installing libsane-hpaio should be sufficient.
"
1816226,2019-02-18 11:40:05 UTC,"> But xsane reports ""Failed......
"
1816226,2019-02-18 11:41:19 UTC,Now for this plugin business.
1816226,2019-02-17 21:37:03 UTC,"Thank you for the links. Printing now works, my next problem is scanning. ;)
I found useful information in your link https://wiki.debian.org/QuickPrintQueuesCUPS
It says that for scanning, installing libsane-hpaio should be sufficient.
I installed the package but scanning still does not work (scanimage -L do not report any scanner)."
1816231,2019-05-01 02:10:33 UTC,The file 'journal.txt' is created in the current directory when you run:
1816231,2019-07-03 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1816231,2019-05-03 08:08:46 UTC,"try this kernel, install amd64/generic versions of linux-image-unsigned and -modules"
1816231,2019-05-01 10:29:43 UTC,"Hey,
I managed to modeset i915=0 and that seemed to stop the flickering.
But now the display is at 800X600 resolution and there is no other option
to change to."
1816231,2019-04-30 13:08:03 UTC,"Hey, could you tell me how to get the journal.txt file.
after I run journalctl -b0 > journal.txt nothing happens. i removed the
i915 driver and reset it."
1816231,2019-04-20 04:17:23 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1816231,2019-04-24 01:12:39 UTC,Thanks for the video...
1816231,2019-02-18 08:10:35 UTC,Could you please take a photo or video of the flickering problem and attach it here?
1816231,2019-04-24 01:20:47 UTC,"This looks like a low level problem. So either in the kernel, or in the Xorg driver."
1816235,2019-02-16 13:49:38 UTC,I'm also attaching the CLI version of the same.
1816235,2019-02-18 09:12:59 UTC,"This looks like an issue with tacker to me, or maybe the tacker devstack plugin."
1816235,2019-02-18 12:22:17 UTC,"Thanks for you guidance, Jens! I just opened an issue at the Tacker forum. Regards."
1816236,2019-02-21 09:53:30 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1816240,2019-02-17 21:50:53 UTC,"OK I installed again from CD on the real hardware on partition sdc5. I had the same old problem, but than I detected, that I told the BIOS some time ago to boot from the SSD. I did forget it completely and normally I have no problem, since I install the boot loader on all disks after running update-grub.
I did set the BIOS back to sda and now the btrfs system boots as expected."
1816240,2020-01-02 05:00:20 UTC,"After installing Ubuntu 19.10 after a few days the software would not come on when I turned the computer on. Have tryed all that I know to fix it, still not working, after reinstalling 3 times."
1816240,2019-05-14 14:50:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816240,2019-02-18 01:19:39 UTC,WRAP UP
1816240,2019-02-17 20:30:54 UTC,"I tried to reconstruct the issue using Virtual Machines. I took an Ubuntu 18.04.2 VM with Linux 4.15 and added a second disk. I booted that VM from the ISO with Xubuntu 18.04.2 and installed Xubuntu on that second disk and it rebooted after install without any problem.
So I have to retry it on the real hardware."
1816240,2019-02-17 17:25:16 UTC,"Thanks for the details, it's not clear from the description though what you tried to do exactly to get the error? Was that using the xubuntu installer (and if so what did you do in the partioning step?) or did you end up in that situation by using update-grub manually from one of your existing installations?"
1816240,2019-02-17 16:05:40 UTC,"The boot loader is stored on sda since 2014 and used by all systems on sdc and sdd. Up to now all 18.04.2 systems use Linux 4.15, since the 4.18 HWE upgrade failed on the compilation of the ZFS-SPL module (another bug report).
I remember that after trying to repair the system by running update-grub from another system on sdd5, the btrfs sdc5 boot entry has not been detected anymore by the Linux 4.15 update-grub."
1816240,2019-02-17 10:10:09 UTC,Thank you for your bug report. You did select custom partitioning in the installer right? Could you describe what partitions you add/their fs type and if you picked to format or not? What grub error do you get exactly?
1816240,2019-02-17 20:31:08 UTC,"I tried to reconstruct the issue using Virtual Machines. I took an Ubuntu 18.04.2 VM with Linux 4.15 and added a second disk. I booted that VM from the ISO with Xubuntu 18.04.2 and installed Xubuntu on that second disk and it rebooted after install without any problem.
So I have to retry it on the real hardware."
1816242,2019-02-16 16:37:12 UTC,"I just now built a emacs-26.1 on the machine I created this bugreport on, and it seems, that 26.1 doesn't crash."
1816244,2019-02-17 15:53:01 UTC,Fix committed in x.1.3.1-24.
1816245,2019-02-16 15:56:11 UTC,"StacktraceSource:
 #0  0x00007f0fcae59505 in ?? () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #1  0x00007f0fcae39a1e in g_object_get () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #2  0x00007f0fbc007840 in ?? ()
 #3  0x00007f0fcad4f780 in g_source_get_context () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #4  0x0000000000000000 in ?? ()
StacktraceTop:
 ?? () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_get () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_source_get_context () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()"
1816245,2019-03-26 11:07:32 UTC,Is this crash still reproducible? Does it affect version 4.13.3?
1816245,2019-03-26 11:54:59 UTC,Random crashes are _never_ reproducible.  I report those as I encounter them but often are thwarted by the bug reporting system telling me that this bug has already been reported and I can add information to it but then redirects me to a bug page that refuses to let me view/access anything because it is marked as containing private information.
1816249,2019-02-21 18:23:49 UTC,"For me I can give some context:
- DELL XPS 9370
- Installed 18.04, dual boot, part of which I think meant that I needed secure boot (may be wrong)
- Attempted to upgrade Kernel to fix some bluetooth issues (known bugs) using UKUU
- Kernel install went OK, grub updated, but then on reboot the system complains that the kernel is not signed
- Attempted upgrade to 18.10, failed on same issue to new kernel not being signed
- But rebooted and checked kernel and it had updated OK to 4.18...
Thanks all I know... hope it helps."
1816249,2019-02-19 03:15:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816252,2019-09-08 12:48:51 UTC,Crash report on current version has already been uploaded above.
1816252,2019-09-05 16:50:40 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates.
1816252,2019-09-01 13:16:42 UTC,"Reproduced on Ubuntu MATE 19.04, 64 bit on the same machine."
1816252,2019-08-20 01:32:13 UTC,"Thank you for reporting this bug. Since this was reported against a version of gimp included in a now end-of-life version of Ubuntu, please try to reproduce this bug using a more recent version of Ubuntu, and comment on this bug as to whether or not this bug still occurs."
1816253,2019-02-22 06:42:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816253,2019-02-22 06:44:47 UTC,"For me this occured after hwe-18.04 upgrade:
sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04"
1816253,2019-03-07 01:20:55 UTC,"I also got that problem after upgrading the hwe-18.04
It's the xserver-xorg-hwe-18.04 part to be exact. If you only do the linux-generic-hwe-18.04 it will still work."
1816253,2019-03-26 21:59:38 UTC,"oh thank you so much the modified package worked for me..
I had xorgxrdp running on an older install a few months ago, and then
they broke it.  Now if someone can tell me how to get it to load lxde instead of gnome3"
1816253,2019-04-29 15:28:04 UTC,"I can confirm this bug, and that Sig Bee's modified .deb file fixed the problem."
1816254,2019-08-20 01:31:51 UTC,"Thank you for reporting this bug. Since this was reported against a version of gimp included in a now end-of-life version of Ubuntu, please try to reproduce this bug using a more recent version of Ubuntu, and comment on this bug as to whether or not this bug still occurs."
1816254,2019-10-19 04:17:39 UTC,[Expired for gimp (Ubuntu) because there has been no activity for 60 days.]
1816257,2019-07-07 20:53:35 UTC,"you need to update boinc to 7.9.3+dfsg-5ubuntu1 by doing
sudo apt-get update && sudo apt-get dist-upgrade"
1816257,2019-11-03 09:15:06 UTC,"I tried the solutions, but the error 127 is still present."
1816257,2019-12-27 14:58:46 UTC,Is it no bug if a package cannot be removed from the system any more?
1816257,2019-07-07 20:50:52 UTC,sudo apt-get install boinc-client should fix the problem.
1816257,2019-11-03 09:20:40 UTC,"user@PC:~$ sudo apt-get dist-upgrade
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.
1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] j
boinc-app-seti (8.00~svn3701-1) wird eingerichtet ...
/var/lib/dpkg/info/boinc-app-seti.postinst: 20: /var/lib/dpkg/info/boinc-app-seti.postinst: update-boinc-applinks: not found
dpkg: Fehler beim Bearbeiten des Paketes boinc-app-seti (--configure):
 Unterprozess installed boinc-app-seti package post-installation script gab den Fehler-Ausgangsstatus 127 zurück
Fehler traten auf beim Bearbeiten von:
 boinc-app-seti
E: Sub-process /usr/bin/dpkg returned an error code (1)"
1816262,2019-02-18 13:02:38 UTC,"Patch applied in branch LP1816262. Once someone else has tested these instructions, we can include them. I'll try to find some time to do that."
1816262,2019-05-26 14:19:21 UTC,I made a few minor edits and pushed to master.
1816262,2019-03-25 18:25:40 UTC,"gettext is installed automatically as dependency if some of packages in step ""Install all dependencies"" - but as part of Ming64 environment (mingw-w64-x86_64-gettext)"
1816262,2019-03-25 12:10:47 UTC,"When I run autogen.sh I get a failure. The gettext package does appear to be installed, however, the referenced archive isn't present. In fact, there's no ""gettext"" directory in /usr/share at all!"
1816262,2019-04-28 11:00:07 UTC,"Hi,"
1816262,2019-03-25 19:10:20 UTC,"Ah, that's probably it. I didn't realize they were different. I'll give it
another go tomorrow."
1816267,2019-02-24 12:26:10 UTC,Marking as confirmed based on https://packages.ubuntu.com/disco/nm-tray.
1816267,2019-10-09 20:44:55 UTC,This bug was fixed in the package nm-tray - 0.4.3-0ubuntu2
1816269,2019-02-18 03:30:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816269,2019-02-18 08:48:33 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0]."
1816269,2019-02-23 21:41:41 UTC,"@Kai-Heng - thanks. Been testing 5.0-rc7 and seems to be working, but want to test it a few more days."
1816269,2019-02-24 19:44:01 UTC,"@Kai-Heng seems to be working better (not 100%, but much better) using Wayland, but doesn't seem better on x11"
1816269,2019-02-27 05:01:08 UTC,Please attach dmesg.
1816269,2019-03-03 01:36:21 UTC,See attached.
1816269,2019-03-04 05:31:34 UTC,"[  135.089830] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
and then Thunderbolt hotplug messages."
1816269,2019-03-14 23:11:51 UTC,Reported at https://bugs.freedesktop.org/show_bug.cgi?id=109829
1816269,2019-02-17 20:53:14 UTC,"@Update: cancel above comment, worked initially."
1816269,2019-02-17 20:49:24 UTC,@Update: Disabling DP1.2 and DDC/CI on the monitors seems to solve this. The monitors are Dell U2415.
1816283,2019-02-22 09:33:54 UTC,The Bug is having diskparted fail to report it had encountered a DOS partition table with a hidden DOS partition that it could not re-partition or completely re-format.  I only found this out by running the Ubuntu recovery option after the install fail and the subsequent boot failure. This would have saved me several weeks. [first try was Ubuntu 14.04 LTS]   **See 2019-02-22 comment.
1816283,2019-02-18 00:52:24 UTC,"Went to
https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu#3
to check the ISO check-sum to see if the download was corrupted
or if
I had burned it to a faulty DVD.
However I could find no workable answer to this question."
1816283,2019-02-17 08:19:49 UTC,"Exception during installation:
Feb 17 07:36:45 ubuntu /plugininstall.py: Traceback (most recent call last):
Feb 17 07:36:45 ubuntu /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 1725, in <module>
Feb 17 07:36:45 ubuntu /plugininstall.py:     install.run()
Feb 17 07:36:45 ubuntu /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 61, in wrapper
Feb 17 07:36:45 ubuntu /plugininstall.py:     func(self)
Feb 17 07:36:45 ubuntu /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 239, in run
Feb 17 07:36:45 ubuntu /plugininstall.py:     self.remove_extras()
Feb 17 07:36:45 ubuntu /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 1445, in remove_extras
Feb 17 07:36:45 ubuntu /plugininstall.py:     self.do_remove(recursive, recursive=True)
Feb 17 07:36:45 ubuntu /plugininstall.py:   File ""/usr/share/ubiquity/plugininstall.py"", line 1028, in do_remove
Feb 17 07:36:45 ubuntu /plugininstall.py:     install_misc.chroot_setup(self.target)
Feb 17 07:36:45 ubuntu /plugininstall.py:   File ""/usr/lib/ubiquity/ubiquity/install_misc.py"", line 128, in chroot_setup
Feb 17 07:36:45 ubuntu /plugininstall.py:     with open(policy_rc_d, 'w') as f:
Feb 17 07:36:45 ubuntu /plugininstall.py: FileNotFoundError: [Errno 2] No such file or directory: '/target/usr/sbin/policy-rc.d'
Feb 17 07:36:45 ubuntu /plugininstall.py:"
1816285,2019-02-17 08:49:30 UTC,"I experienced the above bug with a disk size of 4.5GB, inside virtualbox."
1816285,2019-02-17 12:55:07 UTC,"I'm afraid you're right, the minimum disk space requirement information hasn't been updated on our website for some time, thanks for pointing it out and I'll look into posting the correct details there soon."
1816285,2019-02-17 19:37:55 UTC,"(I wonder out loud why not distribute lubuntu with just a graphical package manager (and a console), and let user choose ... whatever."
1816286,2019-05-12 14:04:19 UTC,Patch was committed in 5685174808f5ca973e916a10f9f93660ee4dc4f2
1816286,2019-05-12 06:43:11 UTC,I can confirm it working too on Slackware current: thanks!
1816286,2019-05-10 08:01:24 UTC,"Steven,"
1816286,2019-05-08 14:10:42 UTC,Here is the whole file as an attachement.
1816286,2019-05-08 14:08:45 UTC,Here is more of the file:
1816286,2019-05-10 14:57:38 UTC,"The patch is good.  I built for Fedora 29, 30, and rawhide.  All built completely."
1816286,2019-05-08 13:44:46 UTC,I'm seeing this failure on Fedora Rawhide.  pcbnew.py contains:
1816286,2019-05-08 14:01:19 UTC,The header has changed and fix_swig_imports.py needs a patch.
1816286,2019-02-17 11:38:59 UTC,I see no problem on my builds. Please add more information.
1816286,2019-02-17 12:14:54 UTC,"I sent this report just after a ""rm -Rf * ; cmake ../"" in my ""build"" directory.
The ""cmake ../"" raised no error on the console, I then ran ""make""."
1816286,2019-05-09 12:40:33 UTC,"For completeness, this bug has also been reported downstream at the Fedora bug tracker:"
1816286,2019-05-08 07:01:29 UTC,following this as swig 4.0.0 has been released and I got the exact same output also on Slackware current.
1816286,2019-05-08 09:42:45 UTC,fix_swig_imports.py is a script to cleanup pcbnew.py
1816286,2019-02-17 12:28:41 UTC,So since the swig version is 4.0.0 I guess you are running a development version you built yourself as I think the latest swig release is 3.0.12.
1816288,2019-02-17 10:40:23 UTC,First seen on AskUbuntu ( https://askubuntu.com/q/1118918/66509 ).
1816288,2019-05-09 22:24:38 UTC,The mini iso is not guaranteed to offer the complete set of features provided by the desktop installer.
1816291,2019-02-17 11:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816291,2019-02-17 12:07:45 UTC,not possible to spawn apport collect.
1816294,2019-09-05 10:41:39 UTC,"Hi Jeremy,"
1816294,2020-06-18 09:23:53 UTC,"Some references for those who are willing to install ldac support
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922154
https://wiki.debian.org/BluetoothUser/a2dp?highlight=%28ldac%29#aptX_.28HD.29_and_LDAC_codecs_are_not_available_to_be_used_with_my_device
https://askubuntu.com/questions/1071469/how-to-enable-aptx-for-bluetooth-devices
https://launchpad.net/~berglh/+archive/ubuntu/pulseaudio-a2dp
https://github.com/EHfive/pulseaudio-modules-bt/issues/108"
1816294,2020-06-25 14:15:14 UTC,"Seems the bug for this package on Debian was closed, so I hope we can have it on groovy."
1816294,2020-06-26 08:35:35 UTC,"https://packages.ubuntu.com/source/groovy/libldac
can you release an official backport for LTS?"
1816294,2020-07-04 17:01:07 UTC,">Seems the bug for this package on Debian was closed, so I hope we can have it on groovy.
"
1816296,2020-05-20 15:26:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816296,2020-12-28 16:34:52 UTC,"Using focal Kubuntu.
Firefox filling .xsession-errors
Has pyqt5 (5.14.1+dfsg-3build1) focal; & current versions of other dbus related files that are standard."
1816300,2020-07-25 10:26:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816304,2019-02-17 18:25:35 UTC,"Additional bug report from OpenALPR referring to the pull-request as stated in the bug description:
https://github.com/openalpr/openalpr/issues/692"
1816304,2019-10-03 17:05:55 UTC,This is done.
1816306,2020-02-04 13:40:16 UTC,"Hi,"
1816310,2019-02-17 19:46:28 UTC,"Passing 'DOCKER_OPTS = ""--dns 8.8.8.8 --dns 8.8.4.4""' should work - maybe it should be documented."
1816316,2020-06-02 02:47:13 UTC,Same issue.
1816316,2020-06-05 17:57:43 UTC,Looks like programming error in freezer.
1816321,2019-03-13 16:11:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816322,2019-02-18 00:09:07 UTC,"This isn't directly tied to the effects system. I think the existing deck BPM tap button should work for this. If that doesn't already work, it would be a nice feature to add."
1816322,2019-02-18 13:29:07 UTC,"I'll test this again. I may not have tapped enough times, it was a while ago."
1816322,2019-02-19 04:18:10 UTC,"Tested with master, tapping the bpm tap button on my controller with the deck in passthrough mode doesn't seem to do anything."
1816324,2019-02-18 00:27:41 UTC,I think you reporting to the wrong package.
1816324,2019-02-18 20:27:07 UTC,Sorry!
1816337,2019-10-25 21:15:10 UTC,"In 5.1, the import dialog does indeed not show the copper layers. But when imported it can be moved to F.Cu and B.Cu."
1816337,2020-01-16 13:19:45 UTC,"Bump!
This is quite gamebreaking when doing something that needs some cad design/drawings. HF stuff and touchpad's etc. :("
1816342,2019-02-18 04:30:06 UTC,This change was made by a bot.
1816344,2019-02-18 13:12:24 UTC,Could you provide steps for how you had a 0 size image?
1816344,2019-02-18 13:53:08 UTC,@Sean
1816348,2019-04-20 20:46:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816360,2019-04-26 17:15:57 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1816360,2019-03-26 15:32:14 UTC,"Reviewed:  https://review.openstack.org/641398
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2e31f057514fece68b428f9541b3380cdd7f4feb
Submitter: Zuul
Branch:    stable/pike"
1816360,2019-03-24 23:39:10 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1816360,2019-03-24 23:04:02 UTC,This issue was fixed in the openstack/nova 17.0.10 release.
1816360,2019-03-22 03:43:22 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1816360,2019-03-15 02:53:02 UTC,"Reviewed:  https://review.openstack.org/641359
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bc2c3359b32f452cd772e510d4c139a8e4594900
Submitter: Zuul
Branch:    stable/queens"
1816360,2019-03-13 00:26:27 UTC,"Reviewed:  https://review.openstack.org/641355
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=31b74bfa4063d68d0f5ea9e883cad8cbcb70ab09
Submitter: Zuul
Branch:    stable/rocky"
1816360,2019-03-06 14:41:04 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/641398"
1816360,2019-03-06 13:52:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/641359"
1816360,2019-03-06 13:48:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/641355"
1816360,2019-03-06 12:25:59 UTC,"Reviewed:  https://review.openstack.org/641143
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=84533f5eb3c5b4ab7598d7c278b53524acc1c6e0
Submitter: Zuul
Branch:    master"
1816360,2019-03-05 22:22:16 UTC,Fix proposed: https://review.openstack.org/641143
1816360,2019-02-28 02:32:29 UTC,Yeah looks like it was an accidental regression in Pike:
1816360,2019-02-18 07:50:48 UTC,"The solution of the bug is extremly simple.
In nova/scheduler/filter_scheduler.py,"
1816362,2020-03-07 10:17:52 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1816367,2019-07-31 11:07:30 UTC,Thank you for the bug report. I changed it's status to confirmed because the problem is known to the developer: https://gitlab.gnome.org/GNOME/gnome-music/issues/168
1816367,2020-02-23 13:55:01 UTC,This bug has been fixed in the 3.34 release of Gnome Music.
1816371,2020-08-30 11:20:00 UTC,"Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'."
1816371,2020-10-30 04:17:14 UTC,[Expired for python-pip (Ubuntu) because there has been no activity for 60 days.]
1816377,2019-09-15 16:56:24 UTC,Migrated to https://github.com/widelands/widelands/issues/581
1816377,2019-02-19 19:27:31 UTC,"If we have only the 'maps/' folder, i guess people will just save it there resulting in a mixed view of shipped and downloaded maps. That's not good."
1816377,2019-02-19 18:57:48 UTC,"""Downloads"" would only make sense if we implemented in-game map downloads. As it is now, players can create their own an way they like. It would be a great feature to have, but we'd need more people in order to implement it."
1816377,2019-02-19 15:38:36 UTC,"#1 This means that when staring a new game, the player will always have to navigate to the ""official"" directory before starting to play a new game. Also, how will the installer recognize that an official map has been updated? Do we want to replace them without prompt/install a copy/... handle this on Linux/Windows?"
1816377,2019-02-19 08:59:51 UTC,"Probably it might be a good idea to save the ""official"" Maps in this folder as well. Maybe in a subfolder ""official"". So one doesn't need to reinstall all maps if a new / development version of Widelands is installed. We might need a dialog in the installer then ""It seems there are already the official maps installed. Do you want to reinstall?"""
1816377,2019-02-19 18:07:44 UTC,We may want different folders below the maps directory?
1816378,2019-04-22 11:53:46 UTC,I'd like to add a request. Allow at least one step between 1x and 2x.
1816378,2019-02-18 10:44:21 UTC,"IMHO it should be possible to set the game speed to extremely low values like 0.01×, this is useful for building stuff unhurriedly without having to pause"
1816378,2019-02-18 11:51:51 UTC,How low would you set it? 1/32th?
1816378,2019-02-18 22:11:45 UTC,"> set the game speed to extremely low values like 0.01×, this is useful for building stuff unhurriedly
"
1816378,2019-02-19 05:02:04 UTC,"Like in the forum thread: At pause speed, your changes only get applied when you press speedup and then speeddown again, which is annoying. But if I need to do many things in a short time, doing everything at 1x speed can be quite hectic. A super-low speed would allow my changes to get applied without pressing the speed keys all the time while being slow enough not to get hectic even in complicated situations (e.g. major economic overhaul during attacks, …)."
1816378,2019-02-19 08:15:42 UTC,"> It´s already possible to use ""snail"" mode there if some players set the speed to 0
"
1816378,2019-02-20 16:41:00 UTC,Idea from the forum: Use ctrl+PageUp/PageDown to change by factor 2 and leave the old function as it is.
1816378,2019-02-22 14:59:11 UTC,This is just what i have already suggested:
1816378,2019-09-16 17:30:18 UTC,Migrated to https://github.com/widelands/widelands/issues/2128
1816379,2019-06-18 19:40:18 UTC,We have a uc18 project that will require a customized initramfs. Does the central repository referenced above exist for this yet?
1816379,2019-03-10 11:08:49 UTC,"As agreed, when foundations produces the central repository to consume the generic initramfs from, we will proceed to consume from there."
1816387,2019-02-18 19:23:43 UTC,"So I have create a service account and bind it with user ""kubernetes-worker_3"".
after binding curl to api-server is working now."
1816387,2019-02-18 19:44:09 UTC,Don't know what are the parameters I need to use in order to start Kubelet therefore I reboot the worker node.
1816387,2019-02-26 11:38:00 UTC,To restart kubelet on all workers:
1816387,2019-02-26 15:44:25 UTC,thank you @Tim
1816393,2019-02-18 14:05:31 UTC,"I think we were initially hesitant on something like this to respect
potential sensitive data there."
1816394,2019-04-22 11:41:25 UTC,Live QA-Test so I'm almost certain a new of test would not create identical trace details for the issue. This condition occurs about once a fortnight on my primary box (the d960 in list of machines it occurs on) but that system is somewhat modified (with loads more packages installed).
1816394,2019-09-04 04:14:42 UTC,"quick Ubuntu-MATE 19.10 daily ISO (2019-09-03) test on
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)"
1816394,2019-06-25 07:55:07 UTC,test system: d780  (installed lubuntu 19.04)
1816394,2019-06-25 04:52:02 UTC,Please test kernel in disco-proposed.
1816394,2019-05-20 08:24:54 UTC,"Lubuntu 19.10 QA-test (live 20190519)
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)"
1816394,2019-05-17 10:13:16 UTC,For additional info please look at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829494
1816394,2019-05-17 09:51:30 UTC,"just had this occur in a lubuntu 19.10 qa-test (live)
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
which is a box I don't see mentioned above"
1816394,2019-10-11 08:07:31 UTC,"19.10 Lubuntu LIVE qa-tests (x2)
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1816394,2019-04-22 11:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816394,2019-04-17 07:30:34 UTC,"No it's NOT listed as off.  When I go there I just take note of what it says (""Analogue Stereo Output"" on this d960 box) and turn the profile so it says off.  I then re-click the drop-down again to get the list, and put it back to ""Analogue Stereo Output"" (for my current box)."
1816394,2019-04-17 06:42:58 UTC,Yeah writing is not great... my mind wanders...
1816394,2019-04-17 06:09:28 UTC,"What are you doing with pavucontrol that ""fixes"" it? With that last comment, it's clear it's not the installation that solves the problem. You're doing something with the program but I'm not sure what."
1816394,2019-03-27 05:22:22 UTC,"Lubuntu 19.04 daily QA-test (20190326.1 from /etc/apt/sources.list)
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
.
suspended system, waited, it resumed, circles on firefox, then after eth reconnected it resumed (silently).  vlc wouldn't play sound either...  :(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816394)  - i fixed using `pavucontrol` as it was already installed...  this I consider a minor issue."
1816394,2019-02-18 22:16:42 UTC,"It was a 'live' QA-test so re-running the test may not result in the same detail, and is extremely unlikely to match PID."
1816394,2019-02-18 20:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816394,2019-02-18 20:29:44 UTC,"gnome-power-manager only provides an UI to display battery/power stats, that's not the faulty component there, maybe the kernel if it's a driver issue?"
1816394,2019-02-18 12:08:05 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1816394,2019-04-17 06:56:19 UTC,OH! Interesting. Three more questions:
1816395,2019-02-21 17:52:58 UTC,https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking is what's there in https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/contributor/internals/sriov_nic_agent.rst
1816396,2020-01-13 07:55:58 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.14
1816396,2019-12-02 11:04:30 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1816396,2019-12-02 11:04:20 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu10.19.10.0
1816396,2019-11-27 03:55:59 UTC,"That should say ""Ubuntu 18.04 LTS"""
1816396,2019-11-27 03:55:46 UTC,Using gnome-sofware 3.28.1-0ubuntu4.18.04.13 on Ubuntu 19.10 I was able to install moon-buggy and launch it from the notification.
1816396,2019-11-27 03:32:28 UTC,Using gnome-sofware 3.30.6-2ubuntu10.19.10.0 on Ubuntu 19.10 I was able to install moon-buggy and launch it from the notification.
1816396,2019-07-09 05:04:54 UTC,https://gitlab.gnome.org/GNOME/gnome-software/issues/726
1816396,2019-11-22 09:39:17 UTC,"Hello Sebastien, or anyone else affected,"
1816396,2019-11-01 06:11:16 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu11
1816396,2019-07-09 04:55:50 UTC,"The cause of this is:
1. You install a snap.
2. GNOME Software generates a notification, with a button that will contact the GNOME Software process and perform the action ""app.launch"" with the app ID. (gs-common.c:gs_app_notify_installed)
3. GNOME Software uses the ID as a desktop ID (i.e. the name of a .desktop file) to launch the application via the GAppInfo object (gs-application.c:launch_activated)"
1816396,2019-06-18 13:10:56 UTC,Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version
1816396,2019-02-18 13:30:29 UTC,"I'm seeing the same behavior on cosmic, so not specific to disco."
1816396,2019-11-22 09:41:20 UTC,"Hello Sebastien, or anyone else affected,"
1816399,2019-07-25 14:01:33 UTC,"Reviewed:  https://review.opendev.org/637716
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=57112a7174945cdcd9f395d20fd6a242cecf5072
Submitter: Zuul
Branch:    master"
1816399,2019-02-19 07:39:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637716"
1816399,2019-07-22 17:59:43 UTC,I just realized that the fix for this cannot be backported because it involves a versioned object bump.
1816399,2019-09-27 09:01:41 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1816399,2019-03-14 21:03:43 UTC,I've dropped the stein-rc-potential tag since this is a latent bug since at least Rocky and not a new regression in Stein.
1816408,2019-02-22 15:05:37 UTC,"I think it might be nicer to work these into the status of the units, rather than having a specific action?"
1816410,2019-02-18 12:56:05 UTC,Here's part of the stacktrace:
1816410,2019-02-18 20:28:40 UTC,"It's not an issue with the code but glib aborting on a missing schemas key (which is considered as a corrupted installation), the reasons can include
- the schemas update failed
- there is a local installation taking over the system schemas and outdated/not providing the key
- could be that the program get started before the schemas cache has been updated (by its trigger), that's not likely though"
1816410,2019-02-18 12:58:14 UTC,This is related to the following change:
1816413,2019-02-19 15:45:21 UTC,The problem seems to be caused by the miscellanea/sosreport_attachment job; deleting that job from /usr/share/plainbox-provider-checkbox/units/miscellanea/test-plan.pxu causes the problem to go away.
1816421,2019-02-20 12:52:59 UTC,This falls a bit under future work to make ssh keys per user and to allow ssh access as a permission level change.
1816425,2019-03-15 23:31:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1816425,2019-03-18 23:56:13 UTC,Verified - I was able to successfully crash dump a cosmic system.
1816425,2019-04-02 10:29:42 UTC,This bug was fixed in the package linux - 4.18.0-17.18
1816430,2019-09-19 16:04:19 UTC,Setting Importance to Low since we aren't getting reports on this issue from the field and we haven't seen it in CI lately. If you hit this issue please update this Bug and bump the priority if it's justified.
1816432,2020-04-02 12:52:21 UTC,"I'm closing this since we can't reproduce, and we don't have the full logs. Feel free to reopen it if it happens again."
1816432,2019-02-20 00:23:04 UTC,"If commissioning causes DNS to become so unreliable that commissioning itself cannot continue, that's a serious issue. I wonder if this is related to bug #1816452; if this bug is causing DNS reloads to become extremely slow, for example, this bug might be mitigated by fixing it."
1816432,2019-02-19 23:08:53 UTC,"After some investigation, we discovered that the reason of the failure, is that the script runner inside the commissioning environment is unable to send the data back to MAAS because it is unable to resolve to DNS."
1816432,2019-02-19 20:32:36 UTC,"By the way, you can do the following to determine the `id` of each controller (I'm not sure why we're using a numeric ID there; normally we would log the system_id and/or hostname):"
1816432,2019-02-18 14:33:39 UTC,"Weird thing noticed, which seems unrelated, is this:"
1816432,2019-02-19 16:38:01 UTC,Restarting the rack servers seems to have updated the dhcpd.conf on both of them.
1816432,2019-02-19 08:46:14 UTC,"Interestingly, although the dates are very different, the contents are the same w.r.t. hosts, and both of them are missing a device I added recently (the stealth-ipmi device which is part of the new tidy-salmon server)."
1816432,2019-02-19 08:36:30 UTC,I wonder if rack controller 'id:249' is ypso or charybdis? I see that the dhcpd.conf on that in /var/lib/maas has remained unchanged for a different period than the other rack controller dhcpd.conf:
1816432,2019-02-19 19:57:00 UTC,Does this behavior persist after the DHCP has been properly configured and restarted?
1816435,2019-05-29 07:41:50 UTC,"Reviewed:  https://review.opendev.org/639411
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=3b91afa9ce69f838789d6c0c3c671c15b061d813
Submitter: Zuul
Branch:    master"
1816435,2019-03-27 12:53:11 UTC,Patch pushed to gerrit: https://review.openstack.org/#/c/639411/
1816435,2019-05-15 15:41:24 UTC,"James, are you referring to the SCSI backend used by QEMU? I think we always have referred to iscsiadm to support transport."
1816435,2019-03-05 15:10:36 UTC,"I'm pretty sure that nova has made use of the native userspace support for iscsi built into qemu; this was introduced a long time ago, making any dependency on kernel based integration and associated daemon obsolete."
1816435,2019-03-27 12:52:18 UTC,"James, I updated the description with the logs from nova-compute."
1816437,2019-09-18 07:42:33 UTC,"As explained by Sylvain, the Checkbox sessions are hosted here:"
1816437,2019-09-19 07:59:04 UTC,In addition:
1816442,2019-02-18 17:59:34 UTC,I was able to get this working by dropping the ports on the ceph-proxy monitor-hosts config:
1816442,2019-03-21 14:36:53 UTC,"We redeployed today and, after reconfiguring the ceph cluster and entering the new mon server info, we encountered this bug again."
1816442,2019-02-19 07:42:07 UTC,"This looks like a bug in the charm-interface-ceph-client project, so will affect all reactive charms that use ceph."
1816442,2019-02-18 17:17:13 UTC,Downgrading to ~field-medium since I was told by on-site engineer (Vern) that a workaround as dropping the port number from the charm config worked for now.
1816442,2019-02-18 17:08:42 UTC,Simpler steps:
1816442,2019-02-18 16:40:07 UTC,Subscribing ~field-critical since Gnocchi deployment with ceph-proxy charm is blocked.
1816442,2019-02-18 16:36:27 UTC,`juju export-bundle` for your reference of the deployed model.
1816442,2019-02-18 16:35:55 UTC,"I've reproduced it as:
unable to parse addrs in '10.0.8.129:6789 10.0.8.169:6789 10.0.8.188:6789:6789'"
1816442,2019-02-18 15:17:00 UTC,If I run ceph --id gnocchi mon_status I get:
1816445,2020-02-26 19:31:20 UTC,"The ""-i"" option DOES work on NVMe devices; it's just not reporting what the script expects. For instance, here's the output on jehan on /dev/sda (a SATA SSD):"
1816445,2020-02-26 15:27:46 UTC,Detection of NVMe support in the disk is the least of the problems here. That issue could be worked around fairly easily; however....
1816445,2020-02-26 16:39:30 UTC,So that sounds like two issues then.
1816445,2020-02-26 16:40:59 UTC,"errr, that was supposed to be ""support FOR -i started...""  Probably worth checking again just to see if -i in Disco or later does properly report SMART support or not."
1816445,2020-02-26 20:15:02 UTC,"Here's a run of ""smartctl -i"" on drapion, which has a RAID that's not supported by the current test:"
1816449,2020-04-02 19:40:23 UTC,"Reviewed:  https://review.opendev.org/710765
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=18e3d76fb8bcd803bb6b0f2fbff600044880abf9
Submitter: Zuul
Branch:    stable/queens"
1816449,2019-09-19 10:09:57 UTC,This issue was fixed in the openstack/networking-ovn 7.0.0.0b1 development milestone.
1816449,2020-03-02 13:08:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/710765"
1816449,2020-02-28 15:26:53 UTC,This issue was fixed in the openstack/networking-ovn 5.1.0 release.
1816449,2019-07-12 14:10:40 UTC,"Reviewed:  https://review.opendev.org/669626
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=017c49ecd59a0173e6cbdbeb874a8673b38e46b4
Submitter: Zuul
Branch:    stable/rocky"
1816449,2020-02-18 14:09:35 UTC,This issue was fixed in the openstack/networking-ovn 6.0.1 release.
1816449,2019-07-08 09:17:05 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/669626"
1816449,2019-07-08 09:14:11 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/669624"
1816449,2019-05-24 11:06:31 UTC,"Reviewed:  https://review.opendev.org/645483
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=1daffa9634a813ccbcf00a4c4c9dbd2c504d326d
Submitter: Zuul
Branch:    master"
1816449,2019-07-08 21:31:36 UTC,"Reviewed:  https://review.opendev.org/669624
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=87ecdd8e0b3a7564ac9bc003debe0afad0782f46
Submitter: Zuul
Branch:    stable/stein"
1816451,2019-09-19 11:51:36 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1816454,2019-07-29 09:49:07 UTC,Could you trying hw:mem_page_size=2MB here?
1816454,2019-07-29 09:55:06 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/673252"
1816454,2019-07-30 11:09:08 UTC,"Reviewed:  https://review.opendev.org/673252
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e8f5641aef4696374026b887c713175899f0719b
Submitter: Zuul
Branch:    master"
1816454,2019-11-11 04:33:39 UTC,Sorry for taking so long to respond; have not been able to test this until tonight.
1816454,2020-03-13 11:33:16 UTC,Looks like this was resolved in https://review.opendev.org/#/c/673252/
1816458,2019-02-21 08:55:27 UTC,"The newer version is in disco, https://launchpad.net/ubuntu/+source/gnome-keyring/3.31.90-1ubuntu1"
1816458,2019-02-20 23:06:55 UTC,"Sebastien Bacher, could you create a [0]package with the version of [1]""gnome-keyring 3.31.90""? My intention is to confirm or inform what happens with this version of the application. Thanks!"
1816458,2019-02-20 16:50:41 UTC,"Never stop the process 'gnome-keyring-daemon', I must close it with 'kill -9 <PID>'."
1816458,2019-02-20 13:17:45 UTC,"Upstream might have an idea but there is nothing special in those backtraces, is seems to just be waiting for event, were they taken at the time of the issue when happening?"
1816458,2019-02-20 13:02:20 UTC,'t a a bt' worked. Do you need any other information?
1816458,2019-02-18 16:36:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1816458,2019-02-19 19:09:11 UTC,https://wiki.ubuntu.com/Backtrace#Already_running_programs
1816458,2019-02-19 17:41:47 UTC,Do you know of any guidelines for reporting a problem in an application when it stays in a loop?
1816458,2019-02-18 16:37:12 UTC,Could you also add the journalctl log from around the time of the issue?
1816458,2019-02-21 12:44:15 UTC,The problem still occurs in 'gnome-keyring 3.31.90-1ubuntu1'.
1816458,2019-02-20 07:42:09 UTC,"your gdb prompt shows you managed to attach the process, can you try to type 't a a bt' instead if 'continue'?"
1816464,2019-08-27 06:57:48 UTC,This fix was verified on below version
1816470,2019-02-24 15:24:12 UTC,Submitted https://gitlab.com/apparmor/apparmor/merge_requests/344 which I think is the real fix and does not reintroduce the bug fixed in a91d199ab1da3004cf3744d7087a32c91097a16e.
1816470,2019-02-24 15:15:55 UTC,"The problem is not the fact alternation. It's that I messed up the alternation in a91d199ab1da3004cf3744d7087a32c91097a16e and there's one extra ""/"" i.e. the rule is about @{HOME}/.local//share (note the ""//"")."
1816470,2019-02-18 17:49:57 UTC,"I am proposing this workaround, motivated by upcoming Debian Buster full freeze:
https://gitlab.com/apparmor/apparmor/merge_requests/340"
1816473,2020-03-05 20:25:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816473,2020-03-05 20:27:13 UTC,"Also the shebang should be changed to #!/usr/bin/env python2 since /usr/bin/python does not exist anymore in
Ubuntu focal"
1816473,2020-03-05 23:39:38 UTC,I just ran 2to3 on obamenu and it looks like a simple fix. Maybe we can push this upstream to Debian and not need the python2 call?
1816473,2020-03-06 00:24:09 UTC,"The attachment ""Fixup obamenu for python3"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1816473,2020-03-06 00:34:35 UTC,"Confirmed, but… since obamenu is an external tool not supplied by Openbox developers, I think the appropriate solution here would be to simply remove obamenu from the Openbox package. You can always download it if you want it:
https://rmoe.anukis.de/obamenu.html"
1816473,2020-03-06 00:54:23 UTC,"Also reading /etc/xdg/openbox/menu.xml There's a comment above the call to obconf that says ""This requires the presence of the 'openbox-menu' package to work."" Needless to say, that doesn't help XD"
1816473,2020-03-11 06:46:21 UTC,I will push fix for that to Debian repo at this week.
1816473,2020-03-30 01:27:53 UTC,This bug was fixed in the package openbox - 3.6.1-9
1816475,2019-08-15 00:24:30 UTC,"Good catches, Terran.  I will take a look at those."
1816475,2019-08-15 16:25:39 UTC,"The video is very helpful, Jane!"
1816475,2019-08-20 17:50:13 UTC,"Thanks for your patience as I address your comments, Terran!"
1816475,2019-08-20 18:26:47 UTC,"Thanks, Jane! We'll try to get the changes tested. For the terminology in #20, what about something like ""Location"" instead of Pickup Library?"
1816475,2019-08-20 18:44:42 UTC,"Re: terminology -- I'm going to throw out ""Resource Location""? Or ""Reservation Location""? Something to indicate where the resource is to be used/retrieved from, whether that's an item being picked up, or a room reservation, or what. I can't think of a good word for that. I do agree that Pickup Library is a little restrictive, but Library by itself is too vague. Could also include a help popover whatever word is chosen, to help staff if they're unclear about the meaning."
1816475,2019-08-20 19:51:56 UTC,"+1 to a help popover -- good idea, Tiffany.  How about ""Reservation Location"" with a help popover that says ""The library where the resource is picked up or used""?"
1816475,2019-08-20 20:01:54 UTC,+1!
1816475,2019-09-06 15:25:28 UTC,"Pushed to master for inclusion in 3.4. Thanks, Jane and Christine."
1816475,2019-09-13 18:18:01 UTC,I broke the follow-up work off into its own bug here: https://bugs.launchpad.net/evergreen/+bug/1843938
1816475,2019-09-10 01:43:16 UTC,I threw a few more fixes into that branch.  Here are the issues Galen found that I haven't gotten to yet:
1816475,2019-09-09 12:41:03 UTC,"Thanks for your testing and pushing, Galen."
1816475,2019-09-04 19:49:55 UTC,"Here is a branch rebased against master, including Christine's sign off: user/sandbergja/lp1816475_booking_refresh_more_rebasing"
1816475,2019-08-27 21:40:51 UTC,"I have tested this code and consent to signing off on it with my name, Christine Burns and my email address, <email address hidden>"
1816475,2019-08-26 22:37:43 UTC,Just threw another commit into the branch to address the issue that Christine pointed out: https://bugs.launchpad.net/evergreen/+bug/1738494/comments/2
1816475,2019-08-20 21:45:15 UTC,"Branch updated to include the terminology changes, and fixing a warning that Jeff Davis discovered."
1816475,2019-08-14 21:02:40 UTC,Two more notes:
1816475,2019-05-04 16:30:34 UTC,"FYI, I've rebased this against master, and added a few bugfixes here: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/sandbergja/lp1816475_booking_refresh_rebased_against_ang_catalog"
1816475,2019-08-14 20:28:52 UTC,"Hi Jane,"
1816475,2019-08-14 20:56:04 UTC,Point of confusion: On our test server we have Circulator set to have branch level access to the booking perms and we have System Administrator set to the system level.
1816475,2019-03-27 15:31:34 UTC,"I will be sure to do that, Bill. The dialog option seems more likely."
1816475,2019-03-26 21:05:59 UTC,"Thanks, Jane!"
1816475,2019-03-26 19:26:47 UTC,"Thanks for asking, Bill.  Book Item Now will be part of the Booking Refresh project, but ""Make Items Bookable"" will not."
1816475,2019-03-26 18:20:38 UTC,"Jane, I am working through bug #1821382 -- Angular holdings maintenance -- and there are 2 menu entries in the holdings grid for booking actions: ""Make Items Bookable"" and ""Book Item Now"".  Will the interfaces that drive these actions be included in your booking refresh work?  Just want to be sure we are not duplicating effort, thanks."
1816475,2019-03-09 01:35:16 UTC,"Thanks for the interest, and for the link, Michele.  Unfortunately, that will not be within the scope of this project."
1816475,2019-03-08 21:39:10 UTC,Adding a link to an old bug that still is relevant in case it falls in the scope of this work: bug 1175766.
1816475,2019-05-08 22:48:45 UTC,"Thanks for your interest, Jason.  That branch should now have two commits.  The first has the two new date-related components: daterange-select and datetime-select.  The second has everything else. :-)"
1816475,2019-05-07 20:47:23 UTC,Oops!  I relied on tab completion and actually pulled the wrong branch.
1816475,2019-08-14 19:50:48 UTC,Good point!  I've force-pushed a change to that file to get rid of the whitespace changes.
1816475,2019-08-14 19:12:58 UTC,"One quick comment from glancing through the branch: There seems to be a lot of whitespace-only changes, at least in the main ""Booking Refresh"" commit, in this file:"
1816475,2019-08-14 17:57:43 UTC,"One quick note: I had two []s showing up in the Create Reservations screen for my own testing purposes.  I forgot to take them out, so I just pushed a follow-up commit to the user/sandbergja/lp1816475_booking_refresh_for_coop branch that removes them."
1816475,2019-05-07 20:43:19 UTC,"Jane, could you rebase again?  I'm having trouble reconciling it with current master.  Also, if you still have an unsquashed branch, I wonder if you'd mind putting the reusable shared components into a separate commit?  What really brought me here was your daterange-select. :D :D  Thanks!"
1816475,2019-05-26 04:09:50 UTC,"A note that this branch is now built atop my branch for https://bugs.launchpad.net/evergreen/+bug/1828840.  Ideally, that one will be merged first. :-D"
1816475,2019-05-09 16:23:38 UTC,"Gracias!  I'll try to give booking a lookover as well, but I have no domain expertise there."
1816475,2019-08-12 20:32:44 UTC,This is ready for community review in the following branch: user/sandbergja/lp1816475_booking_refresh_for_coop
1816476,2019-02-18 19:41:50 UTC,Hello. I am Ali Abbasi.
1816476,2019-02-21 09:21:54 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1816480,2019-03-05 22:23:06 UTC,Fixes for Angular grid pushed:
1816480,2019-05-22 23:01:17 UTC,"This is fantastic, Bill!  All this keyboard functionality is really nice to have."
1816480,2019-05-23 00:00:33 UTC,"...actually, ignore that 3.2-compatible branch, since it doesn't compile.  I'll correct that later this week."
1816480,2019-05-24 17:25:47 UTC,"All right, I added a small follow-up commit to the 3.2-compatible branch, so that should work now."
1816480,2019-05-24 18:02:32 UTC,"Thanks, Jane.  3.2 branch merged to 3.2, other branch merged to 3.3 and master."
1816480,2019-05-24 18:03:21 UTC,"Marking as fix committed.  If we want to pursue similar changes to AngJS grids, I propose we handle that via a new LP."
1816480,2019-03-05 17:40:24 UTC,Grabbing to update Angular grid.
1816482,2020-03-07 10:17:10 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1816485,2019-11-07 17:00:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/693396"
1816485,2019-03-02 14:18:54 UTC,"Reviewed:  https://review.openstack.org/637019
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=61b231a9995a0fe3230302ce913ffde707393d81
Submitter: Zuul
Branch:    master"
1816485,2020-04-03 17:30:27 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/693415
Reason: Cancelling backport b/c this does not meet backport rules."
1816485,2020-04-03 17:30:21 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/693412
Reason: Cancelling backport b/c this does not meet backport rules."
1816485,2019-11-13 16:25:49 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/693396
Reason: impossible due to backport requirements change"
1816485,2019-11-07 19:17:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/693412"
1816485,2019-11-07 19:33:33 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/693415"
1816485,2019-11-07 19:32:56 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/693413"
1816485,2019-02-20 10:03:31 UTC,"Reviewed:  https://review.openstack.org/637119
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=2c1e09bfd5a275c74213d200a7455bbf46893a1a
Submitter: Zuul
Branch:    master"
1816485,2019-11-07 17:41:04 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/693396
Reason: Sorry, I thought this was a neutron change not a neutron-lib change."
1816485,2019-11-13 16:25:21 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/693413
Reason: impossible due to backport requirements change"
1816486,2020-09-02 13:11:46 UTC,"Reviewed:  https://review.opendev.org/747773
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=7ed8f7fac41d5c77ff85265e30b5cf39f048104a
Submitter: Zuul
Branch:    stable/stein"
1816486,2020-08-25 19:43:45 UTC,"Reviewed:  https://review.opendev.org/747505
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=e13af0882e3f133c0c5a8737e61980d34e07f0d1
Submitter: Zuul
Branch:    stable/train"
1816486,2020-08-24 16:57:10 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/747773"
1816486,2020-08-24 13:24:50 UTC,"Reviewed:  https://review.opendev.org/747504
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=b780ef9ef36e7e4bce3fdba8895e445f8d7eb88b
Submitter: Zuul
Branch:    stable/ussuri"
1816486,2020-08-22 01:10:53 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/747505"
1816486,2020-08-21 22:58:57 UTC,"Reviewed:  https://review.opendev.org/745234
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=36a7ec422bf2ff41aeeeff777c81ab83576ce207
Submitter: Zuul
Branch:    master"
1816486,2020-08-07 00:07:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/745250"
1816486,2020-08-06 22:15:17 UTC,Partial Bug fix proposed: https://review.opendev.org/745234/
1816486,2020-08-22 01:10:33 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/747504"
1816486,2020-08-21 22:58:33 UTC,"Reviewed:  https://review.opendev.org/745250
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=271214a0511d345a11947531ac4fb41305ba325f
Submitter: Zuul
Branch:    master"
1816491,2019-02-22 14:40:16 UTC,"There seems a file missing in the MSTS environment files.
Either you find the missing file (it seems to be a sky with clouds texture) or you uncheck the MSTS environment files option."
1816491,2019-03-19 21:15:49 UTC,"Hi Carlo,"
1816497,2020-07-17 11:40:11 UTC,Tentative fix to enable building on !amd64: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=d8f8bf958810e0b48a1dd9e480fbe2def7e8f9f1
1816497,2021-01-05 13:46:48 UTC,"Hi Olivier,"
1816497,2020-07-19 18:55:45 UTC,"From X11 without Wayland:
Vulkan still shows as disabled but the init error doesn't turn up."
1816497,2020-07-19 18:51:15 UTC,The problem also might be that I'm running Chromium inside XWayland rather than natively on X11. I'll try popping over to X11 to see whether it works...
1816497,2020-07-19 18:40:56 UTC,Can we try pulling in https://packages.ubuntu.com/bionic-updates/mesa-va-drivers instead of the base bionic package pulled right now by the https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-enable-vaapi build config (which doesn't use Bionic-Updates)?
1816497,2020-07-19 18:37:08 UTC,"Now we're getting somewhere!
chrome://gpu shows:
```
Vulkan: Disabled
...
Video Acceleration Information
Vulkan Information
Device Performance Information
Log Messages
[4784:4784:0719/142605.755018:ERROR:vaapi_wrapper.cc(511)] : vaInitialize failed: unknown libva error
[4784:4784:0719/142605.967571:ERROR:sandbox_linux.cc(374)] : InitializeSandbox() called with multiple threads in process gpu-process.
[4784:4784:0719/142607.971915:ERROR:gl_surface_presentation_helper.cc(258)] : GetVSyncParametersIfAvailable() failed for 1 times!
[4784:4784:0719/142607.987560:ERROR:gl_surface_presentation_helper.cc(258)] : GetVSyncParametersIfAvailable() failed for 2 times!
[4784:4784:0719/142607.990878:ERROR:gl_surface_presentation_helper.cc(258)] : GetVSyncParametersIfAvailable() failed for 3 times!
[4784:4784:0719/142858.879624:WARNING:ipc_message_attachment_set.cc(49)] : MessageAttachmentSet destroyed with unconsumed attachments: 0/1
[4784:4784:0719/142858.880096:WARNING:ipc_message_attachment_set.cc(49)] : MessageAttachmentSet destroyed with unconsumed attachments: 0/1
[4784:4784:0719/142951.806243:WARNING:ipc_message_attachment_set.cc(49)] : MessageAttachmentSet destroyed with unconsumed attachments: 0/1
```"
1816497,2020-07-17 14:05:43 UTC,https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=ff07991f41f89a21355b6e1c77a4db4393321d47 hopefully fixes it
1816497,2020-07-17 13:25:13 UTC,`stage-packages libdrm-intel1` still fails despite skipping the build steps. Needs a selector to skip it on !amd64/i386.
1816497,2020-07-16 02:17:26 UTC,"As was pointed out by @jon-nettleton, the intel parts are not required to build, and only are used for intel onboard graphics, which necessarily won't be present on ARM64. Is it possible to make it conditional to build those parts depending upon architecture?"
1816497,2020-07-15 22:22:49 UTC,"Oddly enough, you do include it in the snap definition as of May 13..."
1816497,2020-07-20 15:55:29 UTC,Thanks for testing and the feedback Liz.
1816497,2020-07-15 22:15:40 UTC,"@osomon: I see linux-libc-dev is installed in the snap build process but not libc6-dev. I know that normally libc6-dev is included in build-essentials when building .deb files, but is it possible that it isn't in the default set of things for a snap build environment?"
1816497,2020-07-06 16:17:06 UTC,"Sorry for the lack of feedback Liz. I attempted a build on arm64 and ran into errors (https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-source-enable-vaapi/+build/995860) when building the intel-gmmlib part. I spent a bit of time trying to figure those out, unsuccessfully."
1816497,2020-07-01 19:44:27 UTC,@osomon: did you build for arm64? should I try again?
1816497,2020-06-11 13:06:41 UTC,"@Michel: can you share the output of ""LIBVA_MESSAGING_LEVEL=2 snap run chromium"" ?"
1816497,2020-06-10 17:21:13 UTC,I'm unable to find the channel/branch on arm64. Can you also publish an arm64 snap in that branch?
1816497,2020-06-10 10:21:17 UTC,Failure report :
1816497,2020-06-09 10:23:49 UTC,"This is now ready for testing again in the candidate/vaapi channel (rebased on the latest stable chromium release, 83.0.4103.97): revision 1191."
1816497,2020-06-08 16:27:16 UTC,"Pietrek: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=77dc6ad516a8f5ce9dbf8306f4d4f8297a1c7654 should do the trick. I'll trigger a rebuild in a moment, if you're still on the candidate/vaapi channel you should be getting a refresh within the next 24 hours. Please retest and report here when you do."
1816497,2020-06-03 07:57:28 UTC,"Hi,"
1816497,2020-07-06 16:28:43 UTC,"No worries, let me see if @jon-nettleton can have a look."
1816497,2020-05-22 14:34:00 UTC,"hw is working now, 4k vp9 youtube video 8 to 15 % cpu usage, without that jumps to 80%"
1816497,2020-07-20 16:33:15 UTC,"```
Gtk-Message: 12:30:13.823: Failed to load module ""canberra-gtk-module""
Gtk-Message: 12:30:13.826: Failed to load module ""canberra-gtk-module""
/usr/share/libdrm/amdgpu.ids: No such file or directory
libva info: VA-API version 1.7.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[88603:88603:0720/123014.054495:ERROR:vaapi_wrapper.cc(511)] vaInitialize failed: unknown libva error
[88603:88603:0720/123014.127389:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[88603:88603:0720/123016.338346:ERROR:gl_surface_presentation_helper.cc(258)] GetVSyncParametersIfAvailable() failed for 1 times!
[88603:88603:0720/123016.415428:ERROR:gl_surface_presentation_helper.cc(258)] GetVSyncParametersIfAvailable() failed for 2 times!
[88603:88603:0720/123016.506070:ERROR:gl_surface_presentation_helper.cc(258)] GetVSyncParametersIfAvailable() failed for 3 times!
[88724:24:0720/123021.662653:ERROR:batching_media_log.cc(38)] MediaEvent: {""error"":""{\""causes\"":[{\""causes\"":[],\""data\"":{},\""stack\"":[{\""file\"":\""../../media/filters/decrypting_video_decoder.cc\"",\""line\"":53}],\""status_code\"":264,\""status_message\"":\""\""}],\""data\"":{\""Decoder name\"":\""DecryptingVideoDecoder\""},\""stack\"":[{\""file\"":\""../../media/filters/decoder_selector.cc\"",\""line\"":172}],\""status_code\"":265,\""status_message\"":\""\""}""}
[88724:24:0720/123021.663088:ERROR:batching_media_log.cc(38)] MediaEvent: {""error"":""{\""causes\"":[{\""causes\"":[],\""data\"":{},\""stack\"":[{\""file\"":\""../../media/mojo/clients/mojo_video_decoder.cc\"",\""line\"":158}],\""status_code\"":261,\""status_message\"":\""\""}],\""data\"":{\""Decoder name\"":\""MojoVideoDecoder\""},\""stack\"":[{\""file\"":\""../../media/filters/decoder_selector.cc\"",\""line\"":172}],\""status_code\"":265,\""status_message\"":\""\""}""}"
1816497,2020-07-20 16:42:06 UTC,"Aha, it's a detection issue on wayland. passing `LIBVA_DRIVER_NAME=radeonsi` does a trick."
1816497,2021-01-20 10:09:50 UTC,"Hi again Olivier,"
1816497,2021-01-05 14:20:27 UTC,For once I'll make some noise :
1816497,2020-11-06 12:13:56 UTC,"You're right Marc, the snap currently in the edge channel is missing pieces (specifically building and bundling recent versions of the drivers), I'm still working on merging my changes from the experimental VA-API support branch."
1816497,2020-10-10 19:11:33 UTC,"Hi Olivier,"
1816497,2020-09-06 21:25:19 UTC,Most of us have tryed h264ify it dose not help the issue seem to be with the build
1816497,2020-08-26 00:28:57 UTC,"If you want to test this, force YouTube to serve H264, which your card supports judging by the vainfo results. A 4k 60fps YouTube video won't be in a codec your hardware can handle, I guess. There are 'h264ify' extensions for Chromium."
1816497,2020-08-24 20:36:10 UTC,I also can't get the hardware acceleration on Youtube.
1816497,2020-08-22 03:14:31 UTC,I'm seeing the same problem. Debug information below.
1816497,2020-07-20 16:37:37 UTC,from x11 without wayland:
1816497,2020-08-22 02:52:26 UTC,* now not working
1816497,2020-08-07 20:33:24 UTC,"Tested the snap package and it works fine!
Running on DELL XPS13
Version 84.0.4147.89 (Official Build) snap (64-bit)
+ using the h264ify extension in the browser to force Youtube (VP9 by default) to run on h264"
1816497,2020-08-07 20:02:18 UTC,"This used to do the trick for me. Since an upgrade to 20.04 the decoding is not working properly. Chromium (86 here) is not calling MojoVideoDecoder.
https://www.linuxuprising.com/2018/08/how-to-enable-hardware-accelerated.html"
1816497,2020-07-29 23:00:44 UTC,"can I beg the favor of having `rtc_use_pipewire` turned on for your branch? otherwise I'm happy to fork, just let me know :)"
1816497,2020-07-20 18:15:31 UTC,Correct. I'ts a Polaris chip = UVD6.3 (https://en.wikipedia.org/wiki/Unified_Video_Decoder#UVD_6). no vp9 or av1.
1816497,2020-07-20 18:03:12 UTC,"Mojo is the decoder you want for hardware-accelerated video decoding. So you're good with H264. As for VP9 and AV1, I suppose your GPU doesn't support those?"
1816497,2020-07-20 17:48:20 UTC,VP9 decodes in software with VpxVideoDecoder
1816497,2020-07-20 17:19:51 UTC,That's great news Liz!
1816497,2020-07-20 16:49:47 UTC,"although Vulkan is showing as off in chrome://gpu, I _am_ seeing better performance now when switching tabs, watching youtube, and using webgl :)"
1816497,2020-08-22 02:49:48 UTC,Was working last week even with vp9:
1816497,2020-05-21 03:06:29 UTC,"Just for comparison, I disabled hardware acceleration and see CPU usage up at ~70%"
1816497,2020-11-06 10:25:12 UTC,"Hi Olivier,"
1816497,2020-05-20 14:29:11 UTC,Vaapi seems to be working for mpv and Firefox under wayland though.
1816497,2020-04-20 13:35:12 UTC,I have updated the enable-vaapi branch and test snaps are currently building for amd64 and i386 at https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-source-enable-vaapi.
1816497,2020-04-17 19:52:41 UTC,Thank you for the recommendation.
1816497,2020-04-14 01:44:18 UTC,"If anyone doesn't mind, Brave has vaapi support out the box.
1. install gstreamer-vaapi
2. go to brave://flags and enable Override software rendering list, restart browser.
3. go to brave://gpu/ and look at Video Acceleration Information:"
1816497,2020-04-14 00:41:57 UTC,"It does appear to be abandoned, unfortunately. I had hoped that the official addition of VAAPI support to Firefox would be an alternative but it is dependent on Wayland, which is not currently default supported by Ubuntu."
1816497,2020-04-13 19:48:28 UTC,I can also confirm this. Is VAAPI Chromium snap abandoned? It really makes a huge difference.
1816497,2020-04-09 18:12:38 UTC,"Can confirm it is still not working. I don't like the idea of using a ppa in software as sensitive as a browser. But also, vaapi acceleration makes a really important deference, specially in a laptop. The snap was a great solution, it is a shame it is not longer working."
1816497,2019-05-12 16:34:19 UTC,The landing page for the build has disappeared: https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source-enable-vaapi so it's possible that your installation has reverted to the main branch again.
1816497,2019-05-12 06:11:24 UTC,"Hi,"
1816497,2020-04-22 05:03:13 UTC,"Hi Olivier,"
1816497,2019-04-28 13:34:48 UTC,I have a slightly newer chipset (Kabylake) so VP9 is supported in my case. Thanks for the suggestion though.
1816497,2019-04-13 23:59:06 UTC,"Interesting. Since I'm only getting VpxVideoDecoder decode, I guess I have an installation issue of some kind."
1816497,2019-04-10 17:27:08 UTC,"As far as i know, Chromium uses a new video decoding backend. If chrome://media-internals is showing MojoVideoDecoder as VideoDecoder it's using VA-API. Otherwise it falls back to FFMpegVideoDecoder or VPXVideoDecoder."
1816497,2019-04-07 00:07:29 UTC,Some updates:
1816497,2019-04-05 09:33:18 UTC,"I have resurrected the candidate/vaapi channel with an up-to-date build, however it's currently pending a manual review in the store."
1816497,2019-03-24 20:17:51 UTC,"It appears that the candidate/vaapi channel has either been broken or abandoned, since the last build was on February 15th: https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source-enable-vaapi"
1816497,2019-02-19 07:15:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816497,2019-02-19 07:14:56 UTC,"VAAPI in Chromium snap 71 worked really well,
after update to 72 It does not work anymore."
1816497,2020-05-21 03:04:15 UTC,"Looks like it's working for me on 18.04 with upgraded libva since I see MojoVideoDecoder again. CPU usage seemed fair for a 2k video, details as follows:"
1816497,2019-04-28 08:41:15 UTC,@Matt have you tried h264ify extension from the chrome store? It ensures that only h264 videos are loaded. On my Broadwell hardware decoding of VP9 is not supported.
1816497,2020-04-22 11:31:15 UTC,"Thanks for the testing and feedback Matt, much appreciated!"
1816497,2019-04-14 20:38:00 UTC,I wonder if my problem may be related to this error in the chrome://gpu log:
1816497,2020-04-28 09:26:59 UTC,Test on 20.04 on Pentium N5000 :
1816497,2020-05-20 13:53:19 UTC,"I just tried in X11. It seems to be working :)
Sadly, most videos in YouTube seem to be av1 so it took me a while to get a vp9 video, but that's another issue altogether."
1816497,2020-04-23 06:57:55 UTC,Here is my few tests from yesterday :
1816497,2020-05-20 13:34:45 UTC,"Yes, I suspect chromium (or at least the vaapi patches we apply) isn't sufficiently wayland-aware. Nicolás, could you test in an X11 session just to let us know whether accelerated HW video decoding works there? That would be a useful data point."
1816497,2020-05-20 13:18:55 UTC,"It doesn't work here.
Intel i5-7200u running Ubuntu 20.04 on wayland. Maybe wayland is the issue?"
1816497,2020-05-20 12:33:34 UTC,"It's working here with an Intel Core i5-7200U CPU (Intel HD 620); ""intel-gpu-top"" confirms it is. Both VP9 and h264 are accelerated. CPU usage is around 20 to 35% while playing a 1080p video on Youtube (VP9), and a bit higher on Twitch (h264). Though it's way better than with software decoding."
1816497,2020-05-20 08:40:39 UTC,Everyone: a new snap is ready for testing in the candidate/vaapi channel (revision 1163):
1816497,2020-05-19 01:06:13 UTC,"Thanks Olivier. I'll keep my eye out for that, so I can test"
1816497,2020-05-20 14:01:31 UTC,@nicolas  :that s because of https://bugs.launchpad.net/libva/+bug/1698287
1816497,2020-05-18 16:33:15 UTC,"@Matt and others: I'm still working on this. I got chromium to build with the latest libva release, and there's an ongoing build with the latest releases of the corresponding drivers, which in my local tests is working fine. If everything goes well this should be available to test in the candidate/vaapi channel within less than 24 hours."
1816497,2020-05-18 16:33:47 UTC,"A note of interest: when testing the snap, use this command line to output more libva debug information:"
1816497,2020-05-16 15:09:43 UTC,"@osomon If bionic provides only libva-driver-abi-1.1, maybe its time to move chromium snap to core20?"
1816497,2020-05-20 14:09:53 UTC,"@Nicolás: thanks, that's very useful feedback."
1816497,2020-05-15 14:59:48 UTC,Still working on this. I had to patch chromium's vaapi code to enable it to build against a custom libva: https://chromium-review.googlesource.com/c/chromium/src/+/2204178.
1816497,2020-05-13 13:58:32 UTC,"@Alain: thanks for the info. That might explain it, indeed."
1816497,2020-05-11 07:17:01 UTC,"Same ""libva error"" issue here, with an Intel Core i5-7200U CPU (Intel HD 620). I attached the output of running ""chromium --enable-logging=stderr"", the chromium's journalctl entries (from installation to first and second launch) and vainfo."
1816497,2020-05-09 13:55:13 UTC,I am using Ubuntu 20.04. Here is the output of snap info:
1816497,2020-05-08 17:30:30 UTC,"@Michel: sorry for the late feedback. On that Pentium N5000 system, could you please include the full output of running ""chromium --enable-logging=stderr"", and the corresponding journalctl entries, filtered on ""chromium""?"
1816497,2020-05-07 11:28:53 UTC,"I have tried the 81.0.4044.113 vaap candidate, but it is showing this warning at startup:
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)"
1816497,2020-05-18 01:25:18 UTC,"HW acceleration doesn't work for me in the latest build. I noted that Olivier was going to build with a newer version of libva so I went ahead an installed the latest version, as per this guide: https://github.com/intel/media-driver/wiki/How-to-build-and-use-media-driver%3F. Unfortunately that did not change the behavior, so I still see kVideoDecoderName=""VpxVideoDecoder"""
1816498,2019-02-19 02:26:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637665"
1816502,2019-02-19 10:12:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637811"
1816502,2019-02-19 02:40:51 UTC,My apologies - I do see it is a different bug. Disregard my previous comment!
1816502,2019-02-19 02:33:45 UTC,A fix for this merged a few weeks ago and may need to be backported:
1816507,2019-02-19 03:39:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637675"
1816518,2019-03-02 03:50:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816524,2019-04-22 05:22:40 UTC,"With the exception of the default-key hex bytes, and the account hash(?), I get identical output, down to the line numbers."
1816524,2019-04-22 06:08:48 UTC,"'sudo snapcraft register-key <keyname>' does open the gpg key unlock ""screen"", however, it shows the <keyname> with a creation date of 2016-01-01, which is not accurate, creation date is actually 2019-04-21 give or take timezones."
1816531,2019-02-19 08:49:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/637731"
1816534,2019-03-04 02:00:34 UTC,"Since this update involves new features, and Disco is in a Feature Freeze, this change would require a Feature Freeze Exception: https://wiki.ubuntu.com/FreezeExceptionProcess"
1816534,2019-08-19 08:07:43 UTC,"Hi,"
1816534,2019-08-19 15:17:49 UTC,"uploaded to eoan, thanks!"
1816543,2019-07-19 13:56:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671731"
1816543,2019-06-14 09:48:14 UTC,"We hit this yesterday, trying to delete some old nova-compute services for ironic."
1816543,2020-05-19 16:06:25 UTC,"this bug has been fixed, track by https://bugs.launchpad.net/nova/+bug/1852993"
1816548,2019-07-11 15:38:47 UTC,">  - lacks symbols tracking for libusbguard.so.0
"
1816548,2019-07-12 05:35:49 UTC,"Hi Seb,
thanks for putting effort into this in general - I know it can be rather time consuming to clean up those review findings. You asked me to look again into the aspect of the library lacking a symbols file due to the new info presented above."
1816548,2019-07-12 07:24:16 UTC,"> The file is in the normal directory as all other libs (on the current version in Eoan):
>  /usr/lib/x86_64-linux-gnu/usbguard/libusbguard.so.0.0.0
"
1816548,2019-07-12 07:33:58 UTC,"> > The file is in the normal directory as all other libs (on the current version in Eoan):
> >  /usr/lib/x86_64-linux-gnu/usbguard/libusbguard.so.0.0.0
>
> Well, the fact that it's in a subdir there and not directly in
> /usr/lib/x86_64-linux-gnu means it's not in the standard LD_LIBRARY_PATH
> and wouldn't be available to other programs unless they do tweaks to go
> look in that location no?
"
1816548,2019-12-04 21:38:27 UTC,I found the cause of usbguard becoming unresponsive and filed https://bugs.launchpad.net/usbguard/+bug/1855189 (with https://github.com/USBGuard/usbguard/issues/349).
1816548,2020-08-17 10:53:35 UTC,"Sorry for the lack of status update here, we probably own one from a desktop perspective. The feature is still something we would like to see landing but it has disruption potential and Desktop is currently busy with other things, I don't think we have the capacity to deal with the integration and fallouts of usbguard this cycle. We might try to get that done next cycle but it's not sure at this point, I will update the bug when we revisit our backlog and determine what we will be working on in the next cycles."
1816548,2020-08-17 11:24:16 UTC,"Thanks for letting us know, in that case (until really ready) let us mark this incomplete."
1816548,2020-05-06 18:01:59 UTC,"From https://bugs.launchpad.net/ubuntu/+source/usbguard/+bug/1855189/comments/2: ""FYI, upstream committed https://github.com/USBGuard/usbguard/pull/378 to address this issue. It is essentially what I mentioned in the bug description."""
1816548,2020-05-12 12:27:27 UTC,Thanks Jamie!
1816548,2020-08-17 09:18:27 UTC,@Rex - hi I see you added a priority tag.
1816548,2019-07-03 15:33:19 UTC,"sorry ignore that about the warning, it's still there, reported to debian"
1816548,2019-12-04 21:39:42 UTC,"0.7.5 does not fix bug #1855189 (and code inspection suggests 0.7.6 is also affected). IMO, bug #1855189 needs to be fixed as part of main inclusion."
1816548,2019-07-03 15:25:53 UTC,">   dpkg-shlibdeps: warning: debian/libusbguard0/usr/lib/x86_64-linux-gnu/usbguard
> /libusbguard.so.0.0.0 contains an unresolvable reference to symbol pthread_create: it's
> probably a plugin
>  That is concerning as in this case it is not meant to be a plugin.
>  Missing dependency?
"
1816548,2019-04-10 00:38:49 UTC,"On Tue, Apr 09, 2019 at 11:33:00PM -0000, Jamie Strandboge wrote:

> Understanding that usbguard is a target for main, I've been running it
> on my laptop for a little while and can say that there is a real issue
> with the daemon stopping which causes all USB inserts to fail closed
> until the daemon is restarted. I've also suspected some external
"
1816548,2019-05-10 11:49:49 UTC,"I reviewed usbguard 0.7.4+ds-1 as checked into eoan.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1816548,2019-04-19 00:01:17 UTC,"Oh, cool, a starting point to work with! Any chance an apt-get install --reinstall would trip it?"
1816548,2019-04-18 22:07:14 UTC,The error happened again after a snapd upgrade. I suspect it isn't handling the udev trigger events that snapd does particularly well (even though that is supposed to be safe).
1816548,2019-04-12 18:56:37 UTC,"> > Understanding that usbguard is a target for main, I've been running it
> > on my laptop for a little while and can say that there is a real issue
> > with the daemon stopping which causes all USB inserts to fail closed
> > until the daemon is restarted. I've also suspected some external
>
> Did you get any logs or apport crash reports when it died?
"
1816548,2019-04-10 08:28:42 UTC,"Thanks for the review Christian, It seems we have some work to do there, we will plan some of that for next cycle."
1816548,2019-04-10 08:12:22 UTC,"As an addendum to the TODOs, after purging it it should no more block new devices (as it does right now). Which is not fun since the tools to make them allowed are no more installed."
1816548,2019-04-10 07:59:25 UTC,"[Duplication]
Function-wise there seems to be usbauth and usbguard (thanks Seth and Jamie for adding your early experiences).
None of them is in main yet so it would be no duplication.
Picking among the two projects can be hard as they promise almost the same.
But in terms of upstream activity, commits, forks and all that USBGuard seems to win over USBAuth for now.
Therefore the choice between those to seems to be made by the community."
1816548,2019-04-09 23:33:00 UTC,"Understanding that usbguard is a target for main, I've been running it on my laptop for a little while and can say that there is a real issue with the daemon stopping which causes all USB inserts to fail closed until the daemon is restarted. I've also suspected some external keyboard weirdness after plug/unplug/plug to be because of usbguard. I've not debugged any of this but feel like it has something to do with an udevadm trigger events, perhaps as done by snapd, perhaps by suspend/resume. I highly recommend someone really test this software's usability before we put ourselves on the hook for maintenance (I tried it a year or more ago and it was quite unusable, but seems better now, so I may be biased)."
1816548,2019-04-09 13:25:25 UTC,Assigned to me for MIR review
1816548,2019-07-03 15:18:46 UTC,"Thanks for the review, I'm going to try to help moving that a bit forward."
1816551,2019-02-19 12:24:37 UTC,"The attachment ""alpine.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1816556,2019-02-27 20:44:14 UTC,"Everything + reset would be ideal but certainly in this case something is better than nothing. I suppose someone will at some point ask for more anyways, so why not leave this open for the time being if you are willing to do that."
1816556,2019-02-27 18:18:59 UTC,"@eelik, I've fixed up the dialogs to remember the scope and filters.  I stopped short of the Specified Values as I agree that those would need a Reset."
1816556,2019-02-19 15:58:29 UTC,"@eelik, I think you just mean the Edit Text & Graphic Properties dialog.  The Edit Track and Via Properties dialog does remember its settings, I just never got around to implementing it for the other."
1816556,2019-02-19 18:14:10 UTC,"I think that if I want to change something completely different it's easier and safer to start from scratch. For example text character values are <...> by default which is safe, but it would be difficult to change all the values to <...> from e.g. 1, 1, 0.3 etc."
1816557,2019-03-30 01:42:16 UTC,"Hi,"
1816557,2019-03-30 00:14:17 UTC,"Hi,"
1816558,2019-02-19 12:30:12 UTC,"Another problem: When I close the user session and log in again with the same user or another user, the monitor resolution is wrong.
To resolve I have to restart the PC."
1816558,2019-02-19 12:30:59 UTC,I attach LOG after logout and login
1816559,2019-04-06 20:22:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816559,2019-02-19 12:40:19 UTC,"StacktraceTop:
 ?? ()
 ply_keyboard_stop_watching_for_renderer_input (keyboard=0x55a798eeebf0) at ply-keyboard.c:406
 ply_keyboard_stop_watching_for_input (keyboard=keyboard@entry=0x55a798eeebf0) at ply-keyboard.c:406
 ply_device_manager_deactivate_keyboards (manager=0x55a798edca60) at ply-device-manager.c:1002
 on_deactivate (state=0x7ffda0317120, deactivate_trigger=<optimized out>) at main.c:1364"
1816562,2019-02-19 15:05:26 UTC,Narrowed it down to GSConnect crashing.
1816585,2019-06-14 01:32:27 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.1 release.
1816585,2019-04-05 13:59:47 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.
1816587,2019-02-19 14:32:58 UTC,No
1816587,2019-06-25 14:38:13 UTC,Yes
1816587,2019-06-25 15:05:07 UTC,Tri-State
1816587,2019-06-25 16:35:19 UTC,"From: <email address hidden>
To: <email address hidden>
Subject: Test"
1816626,2019-09-16 08:21:36 UTC,Migrated to https://github.com/widelands/widelands/issues/3387
1816630,2019-02-20 20:32:41 UTC,@Sebastien Bacher thank you very much for looking into this issue. I don't know if it is worth tracking this further.
1816630,2019-02-21 08:50:09 UTC,"Thank for the debugging, I'm updating the title to reflect better the issue and it's up to the systemd team then to see how important they believe the issue to be"
1816630,2019-02-20 17:20:30 UTC,that are my permissions on /home:
1816630,2019-02-20 17:18:21 UTC,"Nope, `/lib` is on the system's partition."
1816630,2019-02-20 15:37:26 UTC,"Weird, is /lib in another partition or something?"
1816630,2019-02-20 12:44:45 UTC,@Sebastien Bacher thank you for looking into this!
1816630,2019-02-20 08:57:39 UTC,"The issue is with systemd, /lib/systemd/systemd-timedated is part of that package"
1816630,2019-02-20 13:38:25 UTC,"```
root@home:/var/lib/polkit-1/localauthority/10-vendor.d# ll
insgesamt 44
drwxr-xr-x 2 root root 4096 Feb 19 17:12 ./
drwxr-xr-x 7 root root 4096 Jul 25  2018 ../
-rw-r--r-- 1 root root  196 Apr 20  2018 50-com.canonical.indicator.sound.AccountsService.pkla
-rw-r--r-- 1 root root  154 Nov  9 07:42 60-libvirt.pkla
-rw-r--r-- 1 root root 2363 Nov  6  2015 com.ubuntu.desktop.pkla
-rw-r--r-- 1 root root  135 Sep 11 20:33 fwupd.pkla
-rw-r--r-- 1 root root  217 Jul 14  2017 geoclue-2.0.pkla
-rw-r--r-- 1 root root  485 Okt 31 13:01 gnome-initial-setup.pkla
-rw-r--r-- 1 root root  212 Mär 26  2018 org.freedesktop.NetworkManager.pkla
-rw-r--r-- 1 root root  209 Nov  9 02:24 org.freedesktop.packagekit.pkla
-rw-r--r-- 1 root root  199 Jan 28  2018 systemd-networkd.pkla
```"
1816633,2019-05-22 13:50:13 UTC,Fix kernel config? har har har
1816634,2019-02-26 16:25:17 UTC,"Daniel,
This bug has been reported as
https://gitlab.gnome.org/GNOME/mutter/issues/475.
--
Steve McConnel"
1816634,2019-02-20 02:34:37 UTC,"Steve,"
1816634,2019-02-20 21:24:06 UTC,"Daniel,
I tried Bloom on Ubuntu 18.10 and things have partially improved.  Left
mouse clicks inside the text boxes now move the current selection point in
the text as expected.  Left clicking on the gear button usually brings up
the Styles dialog (a javascript dialog), but the next left click always
closes the dialog without allowing the user to actually do anything.  I
wasn't able to install Bloom on the build for 19.04 because one of its
dependencies had a dependency that couldn't be met.  (chmsee /
libwebkitgtk-1.0-0)
(We'll probably phase out using .chm help files in the next year or two,
but haven't come up with a suitable replacement that all of our projects
like yet.)
--
Steve McConnel"
1816634,2019-02-21 01:46:33 UTC,Thanks for the quick response.
1816635,2019-02-21 13:38:31 UTC,"It sounds like we do want to track down why this particular failure case caused a cluster reset, as even with more RAM provisioned, this could happen for other reasons (other processes on the master running out of control, for instance)."
1816635,2019-02-21 20:04:06 UTC,I agree that the charms should tell you if the machine isn't up to spec.
1816635,2019-02-19 17:50:08 UTC,"Let’s find out why that happened. Out of memory shouldn’t catastrophically
kill a cluster like that. There any number of reasons for an OOM. The
disappearing everything else is scary."
1816635,2019-03-05 08:19:47 UTC,"Sorry for the delayed response. We'd been running it for about a week with one application, and had done about 20 deployments (image updates) to that application. The cluster wasn't heavily loaded as far as we could tell."
1816635,2019-02-19 17:25:20 UTC,The official CDK bundles have a constraint on the master nodes for 4 gigs of memory. This is required to prevent the master node from running out of memory. I think this is just a case of not provisioning enough memory for the master.
1816635,2019-02-19 17:31:46 UTC,"Ok, thanks. Sounds like an invalid bug."
1816635,2020-05-08 15:49:18 UTC,"I doubt we will have any luck reproducing this, but we can give it a try."
1816642,2019-04-09 18:17:26 UTC,"For go-lxc, the goal is to get a clean autopkgtest result on all arches, manual testing of the package did show that we should be getting that now."
1816642,2019-04-17 09:01:21 UTC,This bug was fixed in the package golang-gopkg-lxc-go-lxc.v2 - 0.0~git20161126.1.82a07a6-0ubuntu1~ubuntu16.04.2
1816642,2019-04-17 09:01:11 UTC,"The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1816642,2019-04-17 09:11:16 UTC,This bug was fixed in the package lxc - 2.0.11-0ubuntu1~16.04.3
1816642,2019-04-09 19:57:06 UTC,"Hello Stéphane, or anyone else affected,"
1816642,2019-04-09 17:44:47 UTC,"Hello Stéphane, or anyone else affected,"
1816642,2019-04-09 18:16:36 UTC,"Adding go-lxc to this as the fixes in 2.0.11 ended up showing bugs in go-lxc's test logic, so we'll have to cherry-pick a couple of fixes from upstream to have it be happy and give us a meaningful test result."
1816642,2019-03-12 16:55:32 UTC,Uploaded to the SRU queue for Ubuntu 16.04 LTS.
1816642,2019-04-01 16:39:38 UTC,"Hello Stéphane, or anyone else affected,"
1816642,2019-04-17 09:00:52 UTC,Did manual testing on LXC 2.0.11 both using it directly and through LXD with pre-existing and new containers.
1816642,2019-04-09 19:51:22 UTC,"Hello Stéphane, or anyone else affected,"
1816642,2019-03-12 16:51:06 UTC,"The upstream announcement is now available here:
  https://discuss.linuxcontainers.org/t/lxc-2-0-11-has-been-released/4238"
1816642,2019-02-19 19:08:17 UTC,"We'll have to make that 2.0.11 as unfortunately the 2.0.10 release tarball is bad, waiting for the new release to unblock this bug."
1816644,2019-12-04 08:53:53 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/638429
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1816644,2019-03-04 20:46:40 UTC,"Thomas, if I understand comment #13 it's basically what I did for tricircle [1]; separating those dependencies we want from git into their own requirements file?"
1816644,2019-02-28 16:35:06 UTC,I agree we need a long term solution to that.
1816644,2019-02-27 15:42:34 UTC,"Thanks for comment #10 and the PS.
I also pushed one to tricircle https://review.openstack.org/#/c/639662/"
1816644,2019-02-26 21:32:49 UTC,"Reviewed:  https://review.openstack.org/639363
Committed: https://git.openstack.org/cgit/openstack/networking-bagpipe/commit/?id=d02b173d170edb1002f36aa44fe507752a8c47a8
Submitter: Zuul
Branch:    master"
1816644,2019-02-26 17:42:14 UTC,"In https://review.openstack.org/639363, I proposed another solution to update networking-sfc dependency to stein b1.
networking-bagpipe gate still pulls networking-sfc from PyPI, but we can now consume networking-sfc which is compatible with the latest stein neutron and neutron-lib. I hope this will fix the gate failure."
1816644,2019-02-21 09:01:49 UTC,"Last time I checked, devstack-based josb weren't inheriting the magic behavior of required-projects, which was inherited via tox-siblings. Are we sure that simply rewriting the job as a non-legacy job would be sufficient ?"
1816644,2019-02-25 13:24:26 UTC,"I still haven't gotten an answer on this topic.
I created a QA bug [1] in hopes someone on that team can help with a better solution."
1816644,2019-02-21 13:12:39 UTC,"I can't say for certain, but seems to be what the infra team was saying in [4] from the description."
1816644,2019-02-21 14:04:45 UTC,"Looking more into this, I think the playbooks need to include the required projects on their PROJECTS env var in the playbook like [1]. These projects would also be required-projects for the job definition."
1816644,2019-02-21 14:54:56 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638429"
1816644,2019-02-26 15:13:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/639363"
1816644,2019-02-21 17:29:02 UTC,Appears to be the same issue in https://review.openstack.org/#/c/638099
1816644,2019-02-22 20:26:04 UTC,"I was able to get things working for tricircle [1], but it required to separate out the ""required projects"" that are pulled from source into their own requirements file so they are not picked up by devstack."
1816644,2019-02-21 17:27:56 UTC,I sent a question to the ML [1]. It seems like some additional magic is needed if a project requires a dependency from source and also has it in requirements.txt.
1816648,2019-02-19 19:16:42 UTC,i think we should wait to train to re add the job but if patches are propsed before the non client lib freeze next week ill review them
1816648,2019-07-08 13:39:11 UTC,fixed by https://github.com/openstack/os-vif/commit/81f2002b848448898be934db13e358a969b2cf14#diff-7415f5ff7beee2cdf9ffe31e12e4c086
1816650,2019-02-26 19:11:46 UTC,"Hello Nish, or anyone else affected,"
1816650,2019-03-01 15:28:03 UTC,Before:
1816650,2019-03-25 08:54:52 UTC,This bug was fixed in the package lldpd - 0.9.9-1ubuntu0.1
1816650,2019-03-25 08:54:56 UTC,"The verification of the Stable Release Update for lldpd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1816650,2019-03-25 08:55:01 UTC,Thank you for the verification! I have released this to bionic-updates just now. Could you or someone else perform the same validation on a 18.10 system?
1816650,2019-06-24 19:29:10 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1816650,2019-07-23 05:41:23 UTC,The version of lldpd in the proposed pocket of Cosmic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1816650,2019-02-26 19:10:28 UTC,"Hello Nish, or anyone else affected,"
1816653,2020-04-19 23:59:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816653,2020-04-20 00:02:01 UTC,"Gthumb 3.8, browsing in a directory with >1300 pictures, mixture of webp and jpeg.
Gthumb consumes all RAM (32GB), causing system to stutter."
1816653,2020-04-20 00:04:33 UTC,Possible duplicate: bug #1620060
1816655,2020-07-17 00:51:44 UTC,"A note that Bill Erickson created an Angular component called <eg-patron-search> -- it would provide just the desired behavior.  It's available in Evergreen 3.5, see bug 1859241."
1816655,2020-12-14 16:52:34 UTC,Here's a branch that implements this: user/sandbergja/lp1816655_booking_patron_search
1816655,2020-12-15 15:33:13 UTC,Tested and works perfectly.  A sign-off branch is at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1816655_booking_patron_search-signoff
1816655,2021-02-09 16:35:41 UTC,"Pushed to master for inclusion in 3.7. Thanks, Jane and Garry!"
1816657,2019-10-25 20:01:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816658,2020-10-07 16:57:57 UTC,"I wonder if I should set this bug to 'solved', since in 20.04, I encountered a solution that works at least rudimentary. (Right lower corner is unhandy, two finger conflicts with scrolling.)"
1816658,2019-02-20 20:33:27 UTC,apport information
1816658,2019-02-20 20:33:26 UTC,apport information
1816658,2019-02-20 20:33:24 UTC,apport information
1816658,2019-02-20 20:33:22 UTC,apport information
1816658,2019-02-20 20:33:21 UTC,apport information
1816658,2019-02-20 20:33:20 UTC,apport information
1816658,2019-02-20 20:33:24 UTC,apport information
1816658,2019-02-20 20:33:16 UTC,apport information
1816658,2019-02-20 20:33:19 UTC,apport information
1816658,2019-02-19 20:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816658,2019-02-20 20:33:10 UTC,apport information
1816658,2019-02-20 20:33:17 UTC,apport information
1816658,2019-02-20 20:33:12 UTC,apport information
1816658,2019-02-20 20:33:15 UTC,apport information
1816658,2019-02-20 20:33:11 UTC,apport information
1816658,2019-02-20 20:33:14 UTC,apport information
1816662,2020-08-08 04:17:25 UTC,[Expired for devstack because there has been no activity for 60 days.]
1816662,2019-03-18 12:57:38 UTC,"The log that you show as example seems atypical, because there the issue is caused by a spontaneous reboot of the test node:"
1816669,2019-05-14 22:56:25 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1816669,2019-05-14 19:11:53 UTC,"Kim, This is on the plan for applying to the 4.15 kernel in the June SRU cycle"
1816669,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1816669,2019-05-14 18:56:17 UTC,"Terry,
The  next SRU cycle will be which kernel?"
1816669,2019-03-20 11:12:40 UTC,Removing the Bionic nomination and the tag as it's only requested for 4.18 Cosmic.
1816669,2019-05-14 16:29:09 UTC,"Terry,
We need the patches to be in the 4.15 kernel."
1816669,2019-05-14 15:53:55 UTC,"Per comment #17 Kim, can you please indicate exactly which kernel you want these commits in?"
1816669,2019-04-25 22:32:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1816669,2019-04-25 17:20:07 UTC,I would like these patches in 18.04.1 LTS. What do I need to do?
1816669,2019-03-20 11:16:53 UTC,"It's already in Disco, mark it as fix released. Keep tracking this for older releases."
1816669,2019-05-14 17:56:58 UTC,"Kim, this works is staged for the next SRU cycle."
1816669,2019-03-06 15:40:04 UTC,apport information
1816669,2019-03-06 15:40:02 UTC,apport information
1816669,2019-03-06 15:39:58 UTC,apport information
1816669,2019-03-06 15:39:57 UTC,apport information
1816669,2019-03-06 15:39:55 UTC,apport information
1816669,2019-03-06 15:39:53 UTC,apport information
1816669,2019-03-06 15:39:50 UTC,apport information
1816669,2019-03-06 15:39:49 UTC,apport information
1816669,2019-03-06 15:39:47 UTC,apport information
1816669,2019-03-06 15:39:45 UTC,apport information
1816669,2019-03-06 15:39:42 UTC,apport information
1816669,2019-02-27 05:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816669,2019-03-06 15:42:52 UTC,Not familiar with apport-collect and hopefully I did the right thing.
1816669,2019-03-06 15:39:59 UTC,apport information
1816670,2019-02-24 21:05:44 UTC,90cf89f10044138932d893ee1b5e558b40bb7146
1816671,2019-02-19 21:26:49 UTC,First seen on AskUbuntu ( https://askubuntu.com/q/1119380/66509 ). Fixable by manual installation of `python3-setuptools` package.
1816671,2019-07-20 08:27:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816674,2021-02-10 20:09:42 UTC,Could you give some details on how you workarounded the startup issue?
1816674,2020-06-12 11:59:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816674,2021-02-10 11:56:14 UTC,Same problem with 20.04.
1816678,2019-02-19 22:20:52 UTC,See attachment for odd distance in the save game menu.
1816678,2019-02-20 20:41:49 UTC,"About the error reported, it seems to be an issue about the Activity evaluation data when restored.
A fix proposal will be generated to solve this issue.
In the meantime, you can disable the ""Debrief Evaluation"" option until the fix proposal is released, then your current Activity evaluation data will be restored."
1816678,2019-02-28 09:39:18 UTC,Fix commited x1.3.1-27.
1816678,2019-02-20 21:09:35 UTC,Bug fix proposed for merge.
1816679,2019-04-09 15:52:40 UTC,Fixed:
1816679,2019-05-22 22:09:51 UTC,"Works well for me.  Thanks, Bill and Dan.  I've signed off and pushed this to master and rel_3_3."
1816681,2019-02-23 14:06:24 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1816681,2019-02-20 00:58:35 UTC,"I'm not an expert but I noted other problems with Ubuntu Mate 18.10. Others were mainly GUI failures, elements that dissapear from panels and some windows that looks like wrongly canvas-cut."
1816682,2019-02-20 18:45:40 UTC,"The system impact is that the platform processes are not affined to the platform cores as expected, resulting in a potential system performance degradation."
1816682,2019-06-07 23:31:00 UTC,"In order to retest, do we need any pre task to do before the swact? Are there specific processes affined to specific CPUs already? Do we need to affine any processes to specific CPUs? Any preferred method to affine them?"
1816682,2019-06-21 12:26:14 UTC,Assigned to Bruce for re-assignment.
1816682,2019-06-24 07:00:47 UTC,"Issue is reproduced in my environment. I find there is always a /etc/platform/.task_affining_incomplete in standby controller node.
And after check the code, it seems like a expected behavior. When do swact, the controller node which enter standby status, will ""affining tasks to idle cores"", and this is done in function affine_tasks_to_idle_cores of task_affinity_functions.sh. And at the end of this script, it will record the cores in this incomplete file. Here is the code:
    # Save the cpu list to the temp file which will be read and removed when
    # tasks are reaffined to the platform cores later on.
    echo $idle_cpulist > ${TASK_AFFINING_INCOMPLETE}
And for the controller node which be active node, it will get cpulist from this .task_affining_incomplete file, and ""Reaffining tasks to platform cores"". Then remove this file. Here is the code:
    rm -rf ${TASK_AFFINING_INCOMPLETE}
    log_debug ""${TAG} $count tasks were reaffined to platform cores."""
1816682,2019-06-24 07:03:17 UTC,"Hi Yang,
Per my understanding of the code, ""there is .task_affining_incomplete in standby controller, and active controller should not have this file.""
So I will close this issue as invalid. What is your suggestion?
Thanks."
1816682,2019-06-24 12:45:06 UTC,"Hi Shuicheng,"
1816682,2019-06-25 00:29:18 UTC,"Hi Yang,
Thanks for the clarification. I mis-understood it.
I will close the it as 'Invalid' since cannot reproduce it now. Feel free to re-open it or report a new LP when you meet the issue again."
1816683,2019-02-21 02:06:31 UTC,Probably should also handle: ERROR connection is shut down
1816683,2019-10-31 23:47:44 UTC,"Ran into this today as well, we should continue and skip right through it."
1816683,2019-11-04 02:55:02 UTC,Dies like this:
1816685,2019-02-20 03:01:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638066"
1816686,2019-09-27 09:03:44 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1816686,2019-05-21 08:28:49 UTC,"Reviewed:  https://review.opendev.org/640271
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6c6ffc0476b56fe0bf822ddcf3c9a2d543912f38
Submitter: Zuul
Branch:    master"
1816686,2019-03-01 08:26:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640271"
1816686,2019-02-26 01:19:24 UTC,The force_raw_images in nova.conf was False so the issue can be reproduced.
1816686,2019-02-20 05:02:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638080"
1816686,2019-04-15 09:51:06 UTC,"Change abandoned by Boxiang Zhu (zhu.boxiang@99cloud.net) on branch: master
Review: https://review.openstack.org/638080
Reason: I just abandon this patch now. If there is something else to discuss, I will re-open it later. Thanks, @Eric."
1816689,2019-02-20 03:46:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816691,2019-02-26 12:33:14 UTC,https://git.launchpad.net/compiz/commit/?id=9527c55642a2f5f3934663e1b11481f0d1b39c20
1816699,2019-02-20 06:28:50 UTC,"Sorry, I meant in cosmic cuttlefish 18.10. An importerror occurs because import gobject does not work."
1816702,2019-02-20 08:08:26 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1816702,2019-07-12 02:32:22 UTC,"I'll have to re-test this;  just did a Lubuntu 19.10 (daily) QA-test on the j3400 mentioned, and it was woken using power-button and only wacom-pen was required to resume session."
1816702,2019-07-12 07:29:21 UTC,"The waking up is probably lower level, gnome-power-manager also isn't a service but just an UI showing power usage statistics nowadays"
1816702,2019-07-12 07:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816702,2019-07-12 07:43:38 UTC,"> If due to the nature of the issue you have encountered, you are unable to run this command,
> please add a comment stating that fact and change the bug status to 'Confirmed'.
It was a 'live' QA-test (19.04 daily) so I cannot add information on that run.
"
1816702,2019-07-12 09:47:01 UTC,"My comment #3 is in error, on the QA-test I wrote"
1816702,2019-07-12 10:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816702,2019-07-12 13:12:54 UTC,"Ubuntu 19.10 QA-test
motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
-- notes from qa-test comments
screensaver has kicked in four times now, and both times I could stroke-up with pen & session resumed (not requiring keyboard).
--
I don't think I can change status to ""fix-released"" or ""invalid"" as bug was for 19.04 (it'd require me to download & test 19.04).  It's not an issue in 19.10 anyway."
1816702,2019-07-12 13:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1816702,2019-07-13 04:17:40 UTC,"Marking invalid - i cannot re-create on j3400 using released 19.04, nor daily 19.10"
1816702,2019-07-12 07:47:54 UTC,Is this a regression?
1816708,2019-02-20 07:44:38 UTC,this is the output of command openstack --debug server create --flavor m1.large --image centos7.5-image --nic port-id=ba5fed9d-addf-4617-b9de-280bba52f1a0 --key-name mykey --availability-zone nova:zeus-59.localdomain vm-sriov-neutron-1
1816708,2019-06-13 15:48:53 UTC,"looking at the compute log this  was a port binding issue in neutron.
without the neutron server logs we cannot debug this properly."
1816708,2019-08-13 04:17:27 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1816727,2019-03-15 19:35:02 UTC,"AFAICT, this is behavior in websockify and I'm not yet sure whether we can avoid it."
1816727,2019-02-20 14:34:05 UTC,"Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions."
1816727,2019-06-18 03:41:23 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1816727,2019-06-06 06:24:39 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1816727,2019-04-12 02:51:28 UTC,"Reviewed:  https://review.openstack.org/649375
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7766027c890dc79cc6a5697e18f719e4fd1c2b35
Submitter: Zuul
Branch:    stable/rocky"
1816727,2019-04-10 22:02:23 UTC,"Reviewed:  https://review.openstack.org/649374
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b1b28169af9f835f5b99a4d70d1c0eff2d9fc2f4
Submitter: Zuul
Branch:    stable/stein"
1816727,2019-04-02 15:43:46 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649375"
1816727,2019-04-02 15:43:28 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/649374"
1816727,2019-03-29 21:07:03 UTC,"Reviewed:  https://review.openstack.org/644998
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e4fa061f17353f49615d4850b562699d55a0641b
Submitter: Zuul
Branch:    master"
1816727,2019-03-20 20:39:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/644998"
1816727,2019-03-20 18:27:39 UTC,"Given lack of objections and Melanie's assertion in comment #10 that this doesn't seem to be a vulnerability in websockify itself nor is the condition which is caused by a potential attacker sending TCP/RST packets immediately after an SSL handshake necessarily any more problematic than repeatedly opening SSL connections and dropping them silently without closing, I'm triaging this as a class D (security hardening opportunity) report and switching it to a normal public bug. Please feel free to continue with patch deliberations in normal public code reviews."
1816727,2019-09-27 09:05:25 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1816727,2019-03-20 12:10:29 UTC,"Well, correction - it fixes the cpu overconsumption problem, which is the thing I care about and the main security problem. It doesn't fix the tracebacks that appear in the nova-novncproxy debug logs when haproxy disconnects. I think that part is indeed a websockify bug, but not necessarily a security one."
1816727,2019-03-20 18:27:21 UTC,"The tracebacks are a socket.error ""error: [Errno 104] Connection reset by peer"" coming from websockify. I think we could probably try-except socket.error and log only the exception message, to handle that part. It would still spam the logs, but not with tracebacks."
1816727,2019-03-15 20:00:18 UTC,"Given this, are we likely to catch the websockify maintainers off-guard by making this issue public? If not, I'd like to switch it to public and classify it as a C2 or D class report per https://bugs.launchpad.net/bugs/1816727 ."
1816727,2019-03-15 20:18:47 UTC,"Er, sorry, I meant per https://security.openstack.org/vmt-process.html#incident-report-taxonomy (that was a rather confusing mis-paste)."
1816727,2019-03-15 21:28:20 UTC,I did some local testing with this using devstack and think I might have a patch that will solve this problem on the nova side. I'm going to post it here in the interim while I test it a bit more.
1816727,2019-02-20 14:45:57 UTC,"I agree, from the description, this seems to fall into that grey area between exploitable denial of service vulnerability and security hardening opportunity. If this turns out to be an obviously incorrect implementation in openstack/nova for which an effective fix can be safely backported to affected stable branches, and assuming it's not already at least as easy for an unauthenticated user to have a similar impact by sending other sorts of traffic to that socket, then I can see making the case for issuing an advisory. That said, I would also support not continuing this in private under embargo, if you and the Nova security reviewers feel the report isn't of an overly-sensitive nature."
1816727,2019-03-19 13:50:03 UTC,"The patch looks simple and likely backportable, and it doesn't seem to me that this is actually exposing a bug in websockify (but it's possible I'm just not seeing the bug you see in their implementation)."
1816727,2019-03-19 18:49:51 UTC,"++ class D if this is the case, also ++ on marking as public and getting this fixed."
1816727,2019-03-19 20:04:08 UTC,"Jeremy, correct that this is not a bug in websockify. Apologies for not being clearer in comment 6. I should have said, ""I did some local testing and discovered that this does not appear to be a bug or issue in websockify and that the fix can be handled entirely in nova."""
1816727,2019-03-18 23:37:08 UTC,The last patch had a bug in it. This is the new patch that seems to work properly. I tested it locally by running the tempest NoVNCConsoleTestJSON tests on it.
1816727,2019-03-20 09:40:04 UTC,"I tested the patch in our environment and it fixes the issue when haproxy is hammering nova-novncproxy, thanks! I don't object to marking this as public."
1816728,2019-12-02 16:39:36 UTC,"Reviewed:  https://review.opendev.org/696300
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=945ca73225112da1f672a3b5e9a713d30ddd5df8
Submitter: Zuul
Branch:    stable/train"
1816728,2020-01-06 10:26:52 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.3.1 release.
1816728,2019-11-27 13:06:07 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/696300"
1816728,2019-11-01 06:50:48 UTC,"Reviewed:  https://review.opendev.org/638119
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=d41f0d7c35758bcafe88127d7f56b39bf95bb5f8
Submitter: Zuul
Branch:    master"
1816728,2019-02-20 09:57:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638119"
1816728,2019-11-27 19:30:29 UTC,This issue was fixed in the openstack/tripleo-heat-templates 12.0.0 release.
1816735,2019-09-03 07:37:03 UTC,"Checked with snapd 2.41+git1457.73f3b15, the message has been fixed."
1816739,2019-06-03 20:45:51 UTC,tripleo doesn't own vbmc.
1816741,2019-07-27 18:17:54 UTC,This code isn't normally used and I do not consider it a security risk that a user can start a program that writes to a file that the user provided on the command line. That applies to many command line tools.
1816741,2019-02-25 11:12:38 UTC,"Hi, could someone comment on this vulnerability?  How can this be mitigated?"
1816742,2019-02-20 12:59:31 UTC,"The failure is in the acpid package, because for some reason the service is failing start.  As a package included in the default install, we should be ensuring that the unit does not fail to start (and therefore the system is not considered degraded by systemd).  Reassigning to acpid."
1816742,2019-07-21 04:54:43 UTC,hello. I am facing a similar one. is there any update on this issue? where can i follow it? thanks
1816742,2019-07-22 08:21:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816742,2019-07-22 08:30:00 UTC,"I'm affected by this also.
This occurred during LTS dist-upgrade to 18.04 on a physical computer with very basic configuration."
1816742,2019-10-28 09:53:13 UTC,"Also having this issue while installing ""kubuntu-desktop"" on top of an minimal installed (new) ubuntu 18.04."
1816743,2019-07-04 19:28:19 UTC,"I'll mark this bug as duplicate from LP #1800566 - we'll track progress only in that bug, the SRU for this will be worked along with the reset_devices thing."
1816743,2019-12-20 17:56:09 UTC,"I'm un-marking this as duplicate - LP #1800566 is being worked only for the reset_devices portion, so I'm decoupling both bugs in order we can work this one soon-ish.
Cheers,"
1816743,2020-08-18 17:00:02 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1816749,2019-08-22 17:10:02 UTC,"Fixed in revision 85df994eda4caae28049e92d9d48e7d45d160605
https://git.launchpad.net/kicad/patch/?id=85df994eda4caae28049e92d9d48e7d45d160605"
1816749,2019-03-14 03:05:45 UTC,"Ok, now I've hit this a few times.  It appears to relate to how we calculate the position on various platforms.  Since the scroll thumb for GTK3 is variable size, we need to adjust how much size is available, not the size of the scrollbar."
1816749,2019-02-20 18:51:47 UTC,Does it happen in any other applications?
1816749,2019-02-27 20:29:38 UTC,I can't reproduce
1816749,2019-03-02 15:07:10 UTC,Does this still happen?
1816749,2019-02-20 14:38:19 UTC,"That's actually the status after just opening pcbnew, without doing any pan or zoom action. After doing such an action the scroll-bar position is correct."
1816749,2019-02-20 14:14:10 UTC,I cannot recreate here.  Can you start the video before you launch pcbnew?
1816758,2019-06-06 06:43:55 UTC,This issue was fixed in the openstack/puppet-neutron 15.0.0 release.
1816758,2019-02-20 13:43:23 UTC,"Fix patch:
https://review.openstack.org/#/c/638149/"
1816759,2020-09-30 21:32:29 UTC,"This issue has been observed on a customer cloud.  Requests piling up in a ""wsrep in pre-commit stage"" state resulted in an outage; this check would allow us to detect this type of issue sooner."
1816759,2020-11-04 17:03:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/761449"
1816777,2019-06-21 01:44:24 UTC,This bug blocked a project I'm working with and I rewrote the procedure to use the Alternative Installer built much like D-I. This was a fine workaround but I do like subiquity so I tried to build the master branch. This failed (which is another bug) but I don't know if this is fixed in master. Is it?
1816777,2019-11-11 23:04:49 UTC,This bug is at long last fixed in the edge channel and will be released to stable soon.
1816781,2019-07-07 12:59:09 UTC,privatebin.net redirects to privatebin.info.  Seems to be privacy respecting so it's a good suggestion to add it.
1816785,2019-02-20 16:00:22 UTC,"Hmm, I don't think we can avoid it full stop as clouds support working through VPN and there's no promise of the public addresses. We'd have to figure out how to determine that as part of bootstrap so that we call when needed, but don't when not."
1816785,2019-02-26 12:24:23 UTC,"We also do verification checks about the unit (nonce files on disk, etc),
so even if we do get connected to an IP that isn't the actual machine, we
don't actually treat it as the target. I do think we could potentially bias
it a bit for public clouds where it is more likely that the public IP is
what you want. Certainly on Private clouds there is much less guarantee as
to what address is actually best."
1816793,2019-03-21 17:21:15 UTC,This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.
1816793,2019-03-26 01:12:20 UTC,This issue was fixed in the openstack/cinder 12.0.6 release.
1816793,2019-03-26 01:08:44 UTC,This issue was fixed in the openstack/cinder 13.0.4 release.
1816793,2019-03-04 23:50:13 UTC,"Reviewed:  https://review.openstack.org/638389
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=309f72202d0c76b7b4be3ca96327a8b784a1bc69
Submitter: Zuul
Branch:    stable/queens"
1816793,2019-02-21 10:46:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/638389"
1816793,2019-02-21 10:45:45 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/638387"
1816793,2019-02-21 08:59:37 UTC,"Reviewed:  https://review.openstack.org/630085
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=175aaa879d8b940d800e1b96e8871bd350798038
Submitter: Zuul
Branch:    master"
1816793,2019-02-27 22:40:48 UTC,"Reviewed:  https://review.openstack.org/638387
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=48d188c78af52696b90fb9e90d823b56e7429ab3
Submitter: Zuul
Branch:    stable/rocky"
1816805,2019-12-23 21:14:30 UTC,"Hi, versions 2.5 and 2.11 are quite old (though version 2.10 fixed the bug mentioned in the Red Hat BZ, so I think this might be a different bug.)"
1816805,2020-09-17 04:17:17 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1816806,2019-03-15 20:04:27 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1816806,2019-03-15 23:31:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1816806,2019-03-15 23:37:32 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1816806,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1816806,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1816806,2019-04-02 10:29:42 UTC,This bug was fixed in the package linux - 4.18.0-17.18
1816809,2019-02-26 07:14:09 UTC,Failed test case is power-management/suspend-30-cycles-time-check-with-reboots
1816809,2019-03-05 03:15:44 UTC,"I tried to run the newly created “30 suspend/resume cycles and 1 poweroff, 3 times” tests [1] on a test device and ran into similar issue:"
1816819,2019-02-21 13:10:57 UTC,I can confirm that this patch fixes the issue. I can now reconnect after a client has disconnected.
1816819,2020-11-08 09:46:03 UTC,https://git.qemu.org/?p=qemu.git;a=commitdiff;h=dd154c4d9f48a44ad24e1
1816819,2019-02-21 10:42:24 UTC,Patch proposed
1816825,2019-02-26 15:50:49 UTC,Thanks @cory
1816825,2019-02-26 09:15:16 UTC,"That file is included in the charm, so it's definitely available, so it seems like the issue is with the sys path or import process, but I can't for the life of me think of anything that would make it to that point but fail there.  (For reference, the code being executed can be found here: https://github.com/juju-solutions/layer-basic/blob/master/hooks/hook.template#L7)"
1816825,2019-02-20 20:59:39 UTC,Sorry here is a more detail logs.
1816825,2019-02-20 18:11:34 UTC,"The first place I would start is the logs. `juju debug-log --replay` is useful here to try and get a callstack for the failure. Another option is to use the cdk field agent, which will grab lots of logs and debug information and tar it up."
1816825,2019-02-20 20:47:00 UTC,"below is the result from ""juju debug-log --replay --include kubernetes-master/0"""
1816834,2019-02-20 20:21:04 UTC,"The attachment ""move-clock.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1816834,2019-08-10 02:29:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816838,2019-02-22 21:41:44 UTC,Still happening on mainline kernel 4.20.11
1816838,2019-02-27 09:26:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816841,2019-03-07 02:42:03 UTC,"@Till, What is the status of this patch?  Does it need a refresh?"
1816841,2019-03-09 08:30:44 UTC,Hi Michael.
1816841,2019-03-09 08:30:11 UTC,https://github.com/epics-base/epics-base/pull/24
1816841,2019-03-07 17:09:10 UTC,@Michael D.: Heinz has already created a commit with my patch applied. He added an #ifdef (see his comment above) and removed the 'isEpicsThread' member (except from os/Linux/osdThread.h from where it should be removed as well). I had suggested this step as it then allows non-Epics threads to user epicsThreadSetPriority().
1816841,2019-03-07 09:16:15 UTC,I created Till's patch as a separate commit:
1816841,2019-02-25 14:10:10 UTC,I removed isEpicsThread from the struct too.
1816841,2019-02-25 13:12:04 UTC,"We are able to use SCHED_FIFO on our fast controllers.
I need to get my hands on such a machine, though. Will keep you posted."
1816841,2019-02-21 18:58:22 UTC,"On 2/21/19 7:42 PM, Heinz Junkes wrote:

> Yes, I can confirm that with your changes the behavior has now changed and everything works even with the _main_ task
> with prio 0. (Tested with RTEMS5)
>
> I also already  removed the test  for isEpicsThread in
> epicsThreadSetPriority


Just for the record: IIRC, this is the only place where 'isEpicsThread'
is used. If the
test is removed then we should remove the struct member, too, IMHO."
1816841,2019-02-21 18:42:53 UTC,"Yes, I can confirm that with your changes the behavior has now changed and everything works even with the _main_ task
with prio 0. (Tested with RTEMS5)"
1816841,2019-02-21 18:25:09 UTC,"With the changes I made, epicsThreadSetPriority() should -- in principle
-- also work for non-EPICS threads,
as long as the target thread uses the same scheduling policy as pcommonAttr."
1816841,2019-02-21 08:33:21 UTC,"Thanks Till,"
1816841,2019-02-20 23:20:36 UTC,Thanks Till.
1816842,2019-08-20 13:08:17 UTC,We have not seen this issue in recent sanity runs. Closing.
1816842,2019-02-22 19:46:31 UTC,Marking as release gating; issue impacts container env. Medium priority as issue is intermittent
1816842,2019-04-09 19:36:44 UTC,"The force reboot of controller-0 happened here:
[2019-02-20 01:40:28,952] 139 INFO MainThread host_helper.reboot_hosts:: Rebooting active controller: controller-0
[2019-02-20 01:40:28,952] 262 DEBUG MainThread ssh.send :: Send 'sudo reboot -f'"
1816842,2019-04-09 20:08:57 UTC,"The issue with mariadb-server-0 is a known issue.  The problem is related to the design of the openstack-helm chart.  Basically they're prioritizing data integrity over coming back into service, so when we're starting up a new mariadb cluster (i.e. there is no running server to join) then as long as one of the mariadb-server pods is not updating the state configmap the other mariadb-server pods will not come up.  We plan on adding a monitor to deal with this case after a certain amount of time."
1816842,2019-04-09 20:09:39 UTC,"I'm not surprised that garbd can't connect, as neither of the mysqld daemons are actually running...we're still in the startup code in the mariadb-server pods."
1816842,2019-06-10 17:27:54 UTC,"Looking at the logs, we see the mariadb-server-1 logs ending here:"
1816842,2019-06-20 21:02:00 UTC,"Looking at the garbd logs on compute-0, we see this message which is odd given that controller-1 was rebooted:"
1816842,2019-08-13 14:54:50 UTC,"While there are some unresolved questions lingering about this issue, after making some changes in this area to deal with other issues the original problem doesn't seem to be hitting us anymore."
1816846,2019-02-21 13:29:48 UTC,I solved the problem with the solution proposed by johan-zaxmy.
1816846,2019-02-21 10:15:01 UTC,Same issue here since since yesterday afternoon
1816846,2019-02-21 10:10:59 UTC,"Same error as reporter, on several machines. Happens during manual installation from netinstall image (PXE booted)."
1816846,2019-02-21 14:12:26 UTC,"netboot from xenial-proposed 20101020ubuntu451.28 works!
Thanks Johan!"
1816846,2019-02-20 21:00:24 UTC,I can verify this while doing amd64 netboot and following preseed install of a VM on 3 separate KVM hosts. It's been also working for me several hours ago
1816846,2019-02-21 13:59:39 UTC,kernel and initrd.gz from xenial-proposed 20101020ubuntu451.28 works fine. Thank you Johan Zaxmy for suggestion.
1816846,2019-02-20 21:06:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1816846,2019-02-21 14:32:20 UTC,"Just tested Johan's workaround, and it works for us."
1816846,2019-02-22 10:26:23 UTC,Mine's still not working. It downloads
1816846,2019-02-25 17:17:50 UTC,"When glibc was *uploaded* isn't meaningful here, it's when it was released to -updates, which was the 20th, and is when people started seeing this issue.  Unfortunately, the NSS ABI is easily perturbed and seemingly unrelated changes can break it."
1816846,2019-03-22 11:10:05 UTC,I am having the same issues as above using netboot via pixiecore.
1816846,2019-03-19 12:33:07 UTC,"It looks like it might be related to the fact there there isn't a linux-signed-image-4.4.0-143-generic available? I was able to force it to use the 142 image by setting:
d-i base-installer/kernel/image string linux-image-4.4.0-142-generic"
1816846,2019-03-19 10:39:53 UTC,Confirming the same issue as Nathaniel Priddy.
1816846,2019-03-18 20:29:21 UTC,"I'm currently using Foreman to provision machines. I've updated the image to pull from xenial-updates, but now the installer is unable to install the base system (the latest linux-headers-4.4.0-143). It's specifically unable to find the linux-headers-signed-generic. I did not have this issue before using the xenial-updates? Just pointing it to us.archive.ubuntu.com/ubuntu. I'm not sure of where to get help with this, but this is me specifically trying to use the xenial-updates netboot install since the bug has been introduced with just xenial. Any help is greatly appreciated."
1816846,2019-03-05 08:27:39 UTC,"Question:
If images in
http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/
are broken for nearly all us and having about 30 postings in 2 threads, what is the reason to place the new images NOT in ...dists/xenial/main... ?
Or to give as at least a README.md in ...dists/xenial/main... ?
Thanks!"
1816846,2019-02-28 09:09:55 UTC,"Fixing older images is literally impossible.  If this bug were reported before the fix already existed, the fix would have been to build and publish a new netboot to -updates.  Given that a new (and working) one already lives there, job done.  The reason I haven't closed it yet (though, I should) is because it's much harder to find closed bugs, and I'd rather people see this one than file duplicates.  At least for now."
1816846,2019-02-28 07:37:06 UTC,"Can we get confirmation that this won't be fixed in terms of fixing older images, and that the correct solution (as suggested by Adam Conrad) is to update to the latest 'xenial-updates' netboot image?"
1816846,2019-02-27 07:24:30 UTC,"Confirming the issue.
Using initrd.gz and linux from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/, as suggested above, works."
1816846,2019-02-25 16:44:56 UTC,I see this problem with the following initrd/kernel (I'm unable to trace the provenance of these files to their upstream sources):
1816846,2019-02-24 00:33:52 UTC,What we're the chances that I needed a netboot of 16.04 today...
1816846,2019-03-22 11:50:48 UTC,I tried Nathaniel Priddy solution and it works for me. Thanks N!
1816846,2019-02-23 17:52:17 UTC,"I'm not an expert in this bit of the installer, but it seems to me that the problem is that installation using older kernel/initrd is what is failing. If you download the initrd/kernel from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ today, it works. Can someone who is experiencing the problem post the SHA1 of their initrd/kernel?"
1816846,2019-02-23 03:39:57 UTC,I’m also experiencing this issue.
1816846,2019-02-23 01:26:48 UTC,This bug is still confirmed and active.
1816846,2019-02-22 20:11:49 UTC,"Yes, This problem _started_ on the 21st. I am seeing it when we attempt to do netboot preseed installs of Xenial.  Bionic using the same identical preseed is working fine."
1816846,2019-02-22 19:07:07 UTC,We faced with totally the same issue. We run PXE Installation on daily basis as part of our CI/CD Process. It started to fail since Feb 21st.
1816846,2019-02-22 14:56:34 UTC,"> we were able to just drop in the new kernel and initrd over top of the our previous
> ones and our menu configs and preseeds came forward without any tweaks.
"
1816846,2019-02-22 14:40:27 UTC,"> My install image (with a modified boot meny, that loads the preseeding etc)
> is about a year old now, so not sure what the correct fix is. Updating our
> customised boot image would be a lot of work, so I’d prefer to have it
> fixed “correctly” (whatever it is).
"
1816846,2019-02-22 14:15:13 UTC,"> I'm not sure exactly what happened that started causing the segfaults,
> but it must have been a package update. As you note, libc6-udeb was last
> updated 2 weeks ago, so it doesn't make sense that it would only start
> causing issues this week. My suspicion is that something that depends on
> libc6-udeb is actually what was changed and is causing the fault.
"
1816846,2019-02-22 14:00:07 UTC,@turbo-bayour
1816846,2019-02-22 11:01:40 UTC,"Version 2.23-0ubuntu11 is currently the latest version (xenial-updates). Will there be a new, fixed upload? I'm guessing it's only the udeb that was botched?"
1816846,2019-02-21 16:12:46 UTC,This appears to be fixed in the latest netboot installer published today (2019-02-21 13:49 UTC).
1816846,2019-02-23 14:11:00 UTC,Thanks @johan-zaxmy for proposed hotfix using kernel and initrd from suite xenial-proposed
1816846,2019-03-22 18:03:41 UTC,The Nathaniel Priddy solution worked for me to - adding
1816849,2019-02-20 20:36:41 UTC,"This would be wonderful! The way things are now, we have to do a lot of digging to find a basic piece of information."
1816849,2020-02-11 16:17:08 UTC,"I'm wondering if this is resolved, on our 3.4 system, the current shelf lib shows up in the Item Status, detailed view, holds/transits tab."
1816852,2019-08-09 17:28:06 UTC,"Thank you.
Can you also check the release candidate 2.2.2?"
1816852,2019-08-09 09:06:06 UTC,"Hi Daniel,
Drag 'n drop from explorer to Mixxx works in mixxx-2.3.0-alpha-pre-master-git6892-release-x64.
Win7 64
Drag 'n drop inside Mixxx, from library or autodjlist to player still does't work, but that's another bugreport."
1816852,2019-10-09 04:17:30 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1816852,2019-04-24 16:12:16 UTC,The streaming metadata issue is also fixed in Mixxx 2.1.8 and Mixxx 2.2.1
1816852,2019-04-24 12:05:14 UTC,"The main Problem was:
My Mixxx Displays not a Played Track in Winamp, VLC, Homepage etc.
It shows always the stream Name"
1816852,2019-07-30 11:34:14 UTC,"Hi Thomas, I cannot reproduce the issue as my more. Please verify if the track and drop issue still exists in the recent master build.
http://downloads.mixxx.org/builds/master/release/mixxx-2.3.0-alpha-pre-master-git6882-release-x64.exe"
1816852,2019-03-31 09:46:28 UTC,we have prepared a version with more debug info: http://downloads.mixxx.org/builds/2.1/release/mixxx-2.1.8-2.1-git6825-release-x64.exe
1816852,2019-02-28 12:19:16 UTC,"i have used different versions: 2.0.0 / 2.1.0 / 2.2.0
In everyone was the same problem"
1816852,2019-02-27 21:34:52 UTC,"Which version of Mixxx do you use?
Does this work? https://ci.appveyor.com/api/buildjobs/kea63km7tcs6hw86/artifacts/mixxx-2.3.0-alpha-pre-master-PR2040-git6737-release-x64.exe"
1816852,2019-04-03 22:28:23 UTC,https://bugs.launchpad.net/mixxx/+bug/1819319 related?
1816857,2019-03-12 20:48:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642889"
1816857,2019-03-11 16:47:12 UTC,"Reviewed:  https://review.openstack.org/642135
Committed: https://git.openstack.org/cgit/openstack/puppet-cinder/commit/?id=ae0c571a525e22f3ba891c3157093ccda666e642
Submitter: Zuul
Branch:    master"
1816857,2019-03-08 20:08:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642135"
1816857,2019-03-14 21:04:08 UTC,"Change abandoned by Soledad Kuczala (<email address hidden>) on branch: master
Review: https://review.openstack.org/642889"
1816857,2019-03-04 17:54:23 UTC,"Thanks Alex, I'm on it."
1816857,2019-03-01 23:13:23 UTC,"Sofia, missed your IRC question about bundler. The docs for setting up an env for testing can be found @ https://docs.openstack.org/puppet-openstack-guide/latest/contributor/testing.html"
1816857,2019-03-08 19:38:43 UTC,"Reviewed:  https://review.openstack.org/640863
Committed: https://git.openstack.org/cgit/openstack/puppet-cinder/commit/?id=c09a93456eb806f0cdb6e858470334413ac61ea6
Submitter: Zuul
Branch:    master"
1816858,2019-02-21 08:31:56 UTC,this has also come up in the forum before:
1816860,2019-02-25 02:01:41 UTC,"Tracking upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=109750"
1816860,2019-02-21 08:28:32 UTC,apport information
1816860,2019-02-23 12:00:25 UTC,"Thanks so far, Daniel! - I still encounter the strange boot problems on that dock, but sometimes it works; in W10 as well as in kubuntu."
1816860,2019-02-22 09:30:06 UTC,This change was made by a bot.
1816860,2019-02-22 01:44:36 UTC,Please also tell us how many and what type display/HDMI ports are on the tablet and are on the dock.
1816860,2019-02-22 01:43:09 UTC,"Please clarify which commands above are from when the dock is connected, and which are from when the dock is not connected. If you get the same output in both scenarios then that means the kernel or hardware isn't detecting the dock."
1816860,2019-02-21 21:11:26 UTC,"udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/enabled
/sys/class/drm/card0-eDP-1/enabled:enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-HDMI-A-2/enabled:disabled
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/status
/sys/class/drm/card0-eDP-1/status:connected
/sys/class/drm/card0-HDMI-A-1/status:disconnected
/sys/class/drm/card0-HDMI-A-2/status:disconnected
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/dpms
/sys/class/drm/card0-eDP-1/dpms:On
/sys/class/drm/card0-HDMI-A-1/dpms:Off
/sys/class/drm/card0-HDMI-A-2/dpms:Off
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/enabled
/sys/class/drm/card0-eDP-1/enabled:enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-HDMI-A-2/enabled:disabled
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/status
/sys/class/drm/card0-eDP-1/status:connected
/sys/class/drm/card0-HDMI-A-1/status:disconnected
/sys/class/drm/card0-HDMI-A-2/status:disconnected
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/dpms
/sys/class/drm/card0-eDP-1/dpms:On
/sys/class/drm/card0-HDMI-A-1/dpms:Off
/sys/class/drm/card0-HDMI-A-2/dpms:Off
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/enabled
/sys/class/drm/card0-eDP-1/enabled:enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-HDMI-A-2/enabled:disabled
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/status
/sys/class/drm/card0-eDP-1/status:connected
/sys/class/drm/card0-HDMI-A-1/status:disconnected
/sys/class/drm/card0-HDMI-A-2/status:disconnected
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/dpms
/sys/class/drm/card0-eDP-1/dpms:On
/sys/class/drm/card0-HDMI-A-1/dpms:Off
/sys/class/drm/card0-HDMI-A-2/dpms:Off"
1816860,2019-02-21 09:35:06 UTC,I mean please send us the output from all of those commands.
1816860,2019-02-21 09:24:42 UTC,"Thanks. It looks like an Intel-graphics-only system. So if the extra display doesn't show up in xrandr, can you please run this command to see if it's showing up in the kernel?"
1816860,2019-02-21 08:28:33 UTC,apport information
1816860,2019-02-21 08:28:31 UTC,apport information
1816860,2019-02-22 09:11:27 UTC,Thanks for the clarification.
1816860,2019-02-21 08:28:28 UTC,apport information
1816860,2019-02-21 08:28:27 UTC,apport information
1816860,2019-02-21 08:28:26 UTC,apport information
1816860,2019-02-21 08:28:25 UTC,apport information
1816860,2019-02-21 08:28:24 UTC,apport information
1816860,2019-02-21 08:28:23 UTC,apport information
1816860,2019-02-21 08:28:22 UTC,apport information
1816860,2019-02-21 08:28:21 UTC,apport information
1816860,2019-02-21 08:28:13 UTC,apport information
1816860,2019-02-21 01:51:34 UTC,I am keen to figure this problem out. But first please run this command to send us more information about the machine (while the dock is connected):
1816860,2019-02-22 09:17:54 UTC,"Actually, maybe quick sanity check first: If you can then please try a different HDMI cable, and plug/replug it in firmly."
1816860,2019-02-21 08:28:29 UTC,apport information
1816860,2019-02-22 08:25:49 UTC,"The three sets of three are: the first three on dock after start, the next three off the dock and the last three after reinsertion. It looks like no detection of any change with respect to display."
1816860,2019-02-21 08:28:24 UTC,apport information
1816861,2019-02-21 08:30:31 UTC,"snapcraft status, snapcraft release also do this."
1816861,2019-03-10 11:00:25 UTC,"Hey John, in order to keep things consistent, mind stating what the fallback logic is?"
1816861,2020-05-26 20:35:10 UTC,https://github.com/snapcore/snapcraft/pull/3145
1816887,2019-02-21 00:20:37 UTC,"The attachment ""Patch removes the -cl-std kernel build option"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1816907,2019-04-12 21:12:42 UTC,...after upgraded to stein...
1816907,2019-02-25 12:51:47 UTC,the installer does not recognize that the cache has already been installed and been used. It stills try to find the label used to define the cache.
1816907,2019-02-28 08:09:36 UTC,when
1816907,2019-03-01 15:19:52 UTC,By following https://bugs.launchpad.net/kolla/+bug/1797094 by manually executing
1816907,2019-04-12 21:12:24 UTC,"The error appears with a redeployed ceph cluster. By erasing the cluster and deploy as if new, then no error message!!"
1816907,2019-04-18 18:57:12 UTC,screenshot
1816907,2019-04-25 09:12:14 UTC,Not sure I fully understand the problem. Are you deploying a *new* Ceph cluster using disks that have previously been used for an old ceph cluster? Or are you just doing a deploy against an existing cluster with new images?
1816907,2019-04-25 09:29:44 UTC,1. a new deploy of ceph bluestore cluster
1816917,2019-04-18 18:49:10 UTC,no problem in stein
1816927,2019-02-26 21:11:01 UTC,"Reviewed:  https://review.openstack.org/639237
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=f0b11d7a87ad86f59de973a16e7732ea12700edf
Submitter: Zuul
Branch:    stable/ocata"
1816927,2019-02-26 21:12:50 UTC,"Reviewed:  https://review.openstack.org/639234
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=3a3f062cb66a4d7b046d9fd49842cdbd6fdcd738
Submitter: Zuul
Branch:    stable/rocky"
1816927,2019-02-26 21:12:41 UTC,"Reviewed:  https://review.openstack.org/639236
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=5d47236c891dafd786552a91520dd0bc95d5d4a2
Submitter: Zuul
Branch:    stable/pike"
1816927,2019-03-21 14:54:50 UTC,This issue was fixed in the openstack/keystone 15.0.0.0rc1 release candidate.
1816927,2019-02-26 20:57:38 UTC,"Reviewed:  https://review.openstack.org/639235
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=e476286de2b5a3c402b00ad1550e579b7a5c6882
Submitter: Zuul
Branch:    stable/queens"
1816927,2019-03-12 21:35:36 UTC,"Reviewed:  https://review.openstack.org/638397
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=261eeaa19bb4c9e9ea89fac28e473fa44c4a55de
Submitter: Zuul
Branch:    master"
1816927,2019-02-26 00:58:12 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/639237"
1816927,2019-02-26 02:06:06 UTC,"Reviewed:  https://review.openstack.org/638327
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_keystone/commit/?id=28a0c5abbf654ff8b625edc0c12af50a3def2429
Submitter: Zuul
Branch:    master"
1816927,2019-02-26 00:57:45 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/639235"
1816927,2019-02-26 00:57:32 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/639234"
1816927,2019-02-21 14:36:36 UTC,Verifying this for keystone since won't don't go into much detail about the ordering or keys during a transfer between hosts.
1816927,2019-02-21 14:13:20 UTC,"Right, I should have clarified the rsync command being used in those details [0]."
1816927,2019-02-21 08:28:39 UTC,"> The rsync implementation deletes the contents of the key repository and rebuilds it
"
1816927,2019-02-21 04:27:53 UTC,"Cloudnull and I discussed possible solutions in IRC [0]. There is a patch up, but it likely needs to get verified against the OSA project directly [1]."
1816927,2019-02-26 00:57:58 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/639236"
1816938,2019-09-27 09:05:41 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1816938,2019-06-18 03:41:43 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1816938,2019-06-06 06:24:53 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1816938,2019-04-17 00:01:13 UTC,"Reviewed:  https://review.openstack.org/647651
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8d757888a8179e5bfbdfee26eb672590f964f574
Submitter: Zuul
Branch:    stable/rocky"
1816938,2019-04-10 21:47:15 UTC,"Reviewed:  https://review.openstack.org/647646
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ae40ceba8420b3b6c4bd8e29cf95ec21fd20e1e8
Submitter: Zuul
Branch:    stable/stein"
1816938,2019-03-26 08:34:11 UTC,"Reviewed:  https://review.openstack.org/638821
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c66b40dbd23e3f792a86da5a15c993c52c9b377
Submitter: Zuul
Branch:    master"
1816938,2019-03-26 02:20:39 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/647646"
1816938,2019-02-23 12:18:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638821"
1816938,2019-03-26 03:14:29 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/647651"
1816939,2019-02-21 00:25:18 UTC,Failure occurred here: https://review.openstack.org/#/c/637318/1
1816940,2019-02-21 01:09:04 UTC,Commit to address this:
1816944,2019-02-21 10:24:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638382"
1816944,2019-02-28 12:47:40 UTC,"Change abandoned by Yushiro FURUKAWA (<email address hidden>) on branch: master
Review: https://review.openstack.org/638382
Reason: It worked without this patch!! Sorry!!"
1816947,2019-02-21 04:05:24 UTC,apport information
1816947,2019-02-21 04:05:22 UTC,apport information
1816947,2019-02-21 04:05:23 UTC,apport information
1816947,2019-02-21 04:05:21 UTC,apport information
1816947,2019-02-21 04:05:32 UTC,apport information
1816947,2019-02-21 04:05:17 UTC,apport information
1816947,2019-02-21 04:00:44 UTC,"Thanks a lot for your prompt reply, I hope someone can put some effort into into it."
1816947,2019-02-21 03:26:22 UTC,Could you please:
1816947,2019-02-21 04:05:26 UTC,apport information
1816947,2019-02-21 04:05:19 UTC,apport information
1816947,2019-02-21 04:05:29 UTC,apport information
1816947,2019-02-21 04:05:27 UTC,apport information
1816947,2019-02-22 03:13:29 UTC,I can confirm that the touchpad DOES work as expected in ubuntu 17.10
1816947,2019-02-22 08:41:47 UTC,opensas:
1816947,2019-02-24 04:40:36 UTC,"I've just installed ubuntu 18.04.2 to a new partition, and then installed the following packages:"
1816947,2019-02-24 11:17:31 UTC,"opensas, the next step is to fully commit bisect from 4.13.13 to 4.15."
1816947,2019-02-25 08:04:06 UTC,I'm trying to pinpoint the kernel version in which the bug appeared.
1816947,2019-02-25 08:25:41 UTC,"Maybe go back a little further to a 4.12 or 4.11 version. If they still don't work then that's an indication the ""fix"" might have been in a patch that only existed in artful."
1816947,2019-02-25 08:27:10 UTC,"Also, if you haven't already please try much newer kernels too. Like 4.20 or 5.0."
1816947,2019-02-27 06:32:45 UTC,"All right, I took your advice and tested several older kernels:"
1816947,2019-02-27 09:01:24 UTC,"you should've installed linux-image-extra for 4.13.0-19.22, testing without it doesn't prove a thing"
1816947,2019-02-27 14:04:22 UTC,1) I tried with all these:
1816947,2019-02-21 04:05:31 UTC,apport information
1816947,2019-02-27 15:15:14 UTC,"Yes, in #43 you said that you tested 4.13.0-19.22 but didn't seem to install the package with the drivers (linux-image-extra). If you do, does it work like the live version did?"
1816947,2019-02-28 03:15:15 UTC,I installed the following deb files:
1816947,2019-03-07 06:27:58 UTC,Please attach dmesg when it works and when it doesn't work.
1816947,2019-03-07 23:10:47 UTC,"Hello.
I have the same laptop.. It malfunctions all the time. The touchpad has to be used slowly or it freezes. and I am unable to drag and select/move text..
I can see there was a simillar bug to this..
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1048258
Some interesting information about these drivers.. project sputnik?
https://bartongeorge.io/2012/06/20/sputnik-update-touchpad-driver-now-available/
Let me know If i can help with something else.. thanks"
1816947,2019-03-08 07:07:50 UTC,"yoshiki2, it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux"
1816947,2019-04-27 20:10:30 UTC,"fredo@fredo-Dell-System-XPS-L321X:~$ sudo libinput measure touchpad-pressure
Using CyPS/2 Cypress Trackpad: /dev/input/event5"
1816947,2019-04-27 20:12:05 UTC,"fredo@fredo-Dell-System-XPS-L321X:~$ dmesg|grep -i ""ps/2""
[    1.006927] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    1.010735] mousedev: PS/2 mouse device common for all mice
[    2.667559] input: CyPS/2 Cypress Trackpad as /devices/platform/i8042/serio1/input/input6
fredo@fredo-Dell-System-XPS-L321X:~$"
1816947,2019-05-03 05:05:53 UTC,"Also tracking upstream:
https://gitlab.freedesktop.org/libinput/libinput/issues/276"
1816947,2019-05-26 05:58:34 UTC,"Any solution pending on this? I have same fault - as expected I guess.
Have just rebuilt PC from old Ubuntu 16.04LTS to 18.04LTS and Trackpad has developed same problem.
Confirming I'm on DELL XPS13 L321X
 - Trackpad only works sporadically, short distances, if very light touch and moving slowly++
 - Cannot click and drag anything
 - Cannot highlight text
PS: I'm virtually coding illiterate but will do whatever I can to assist if needed
Is there something I can download and overwrite as a fix?
If so, please spell out coding syntax required to complete
Cheers guys. (Linux noob)"
1816947,2019-05-27 16:06:54 UTC,"The only way to fix this is using libinput 13.
You might need to compile it, and those new drivers would fix it.
I tried libinput on fedora 30.
I do not know how to update/build libinput, though. (i am using linux mint debian for now).
Can someone give us instructions?"
1816947,2019-02-27 18:06:26 UTC,"Thanks for the tip (I didn't know which packages to include), I'll give it
a try asap"
1816947,2019-02-21 20:27:32 UTC,"sure, as soon as I get back home I'll do it ;-)"
1816947,2019-02-21 19:37:38 UTC,opensas:
1816947,2019-02-21 13:43:30 UTC,apport information
1816947,2019-02-21 04:07:24 UTC,I just ran
1816947,2019-02-21 04:25:30 UTC,The problem is not related to xserver-xorg-input-synaptics so please don't use that in the data collection.
1816947,2019-02-21 04:30:06 UTC,This change was made by a bot.
1816947,2019-02-21 08:44:56 UTC,"opensas, please advise to all of the following:"
1816947,2019-02-21 13:06:00 UTC,Thanks a lot for your time & effort
1816947,2019-02-21 13:43:23 UTC,apport information
1816947,2019-02-21 13:43:28 UTC,apport information
1816947,2019-02-21 16:04:03 UTC,"1) ok, sorry"
1816947,2019-02-21 13:43:32 UTC,apport information
1816947,2019-02-21 13:43:33 UTC,apport information
1816947,2019-02-21 13:43:35 UTC,apport information
1816947,2019-02-21 13:43:36 UTC,apport information
1816947,2019-02-21 13:43:38 UTC,apport information
1816947,2019-02-21 13:43:40 UTC,apport information
1816947,2019-02-21 13:43:42 UTC,apport information
1816947,2019-02-21 13:43:44 UTC,apport information
1816947,2019-02-21 13:43:46 UTC,apport information
1816947,2019-02-21 13:45:05 UTC,all this was sent from ubuntu bionic livecd
1816947,2019-02-21 13:54:17 UTC,opensas:
1816947,2019-02-21 04:05:36 UTC,apport information
1816947,2019-02-21 04:05:34 UTC,apport information
1816954,2019-05-01 15:20:46 UTC,"Identical issue, namely you cannot progress without having a DHCP server and configuring a manual IP crashes the installation process and it starts over.  However, I have experienced this on both VMware and a bare-metal HP ProLiant installations."
1816954,2019-05-15 16:04:21 UTC,"Can I ask by what magic ""snap refresh subiquity"" works, on a system incapable of having a static IP address assigned to it?"
1816954,2019-03-27 22:57:28 UTC,"It's fixed in the installer code but not in any released media yet. If you switch to tty2 and run ""snap refresh subiquity"" you'll get a version of the installer with this bug fixed."
1816954,2019-07-20 00:08:15 UTC,Previous release iso images still available under http://old-releases.ubuntu.com/releases/18.04.1/.
1816954,2019-02-21 07:40:29 UTC,I noticed the info crash the other day and fixed that in subiquity master a few days ago.
1816954,2019-05-02 14:16:57 UTC,"To clarify (thanks teward!), setting static IPv4 or IPv6 addresses is possible."
1816954,2019-03-27 22:38:57 UTC,Is this still ongoing? I was able to reproduce the installer crash if I added a domain search name. It does not crash when leaving the field blank.
1816954,2019-05-01 15:24:08 UTC,Follow-up suggestion: make 18.04.1 Server ISO available again for in the meantime installations.
1816954,2019-05-02 13:54:47 UTC,@modiford http://cdimage.ubuntu.com/releases/18.04.2/release/ubuntu-18.04.2-server-amd64.iso
1816955,2019-02-21 13:52:59 UTC,This is not a CLI bug. This should be fixed in neutron-fwaas.
1816957,2019-02-21 06:39:06 UTC,"At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!"
1816957,2019-06-13 18:23:45 UTC,Closing after no response in 4 months.
1816970,2019-02-21 09:29:54 UTC,"Yes, there's a possible window where your job can be finished executing all the commands, but the artifacts tarball is not yet available on the server.  This is because the agent automatically takes care of that part for you. In fact, it's also smart enough to retry it if the upload fails for any reason.  At the time, I was thinking it would be better to return control to the user as soon as the test run is complete, and let the agent take care of all this in the background.  But if you have something monitoring the test run and trying to collect the results (like jenkins, etc), you want to get those artifacts before finishing. The way I deal with this in our jenkins jobs is to do something like this:"
1816970,2019-02-26 06:49:59 UTC,"Hi Paul,
"" testflinger-cli artifacts ${{JOB_ID}} || (sleep 30 && testflinger-cli artifactstestflinger-cli artifacts ${{JOB_ID}} ${{JOB_ID}})"""
1816970,2019-09-04 16:46:42 UTC,"So this might be fixed for your purposes, but it doesn't really check the checksum yet. I'd still like to add that so I'm going to leave it open but there were some changes a while back on the testflinger-agent side, which should mean that you don't exit from testflinger poll, until that artifact is uploaded completely. Because if anything goes wrong during the artifact upload, it will fall out of that and put it into a results queue to retry. It's not until later when the results json gets uploaded that the job will be marked ""complete"", and at that point polling will stop listening, so by then, the artifact *must* be uploaded, which means you shouldn't get a truncated artifact unless some other network problem interferes."
1816974,2019-11-12 04:18:31 UTC,[Expired for kolla because there has been no activity for 60 days.]
1816974,2019-09-12 14:20:21 UTC,"Please deliver:
- list of NICs and their settings (ethtool output)
- dump of Neutron components (networks, subnets, routers)
- iperf output of testing between VMs on the same network, but on different hosts"
1817020,2019-06-06 09:33:51 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1817020,2019-06-06 09:33:24 UTC,This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.1
1817020,2019-05-28 21:40:39 UTC,"Hello Will, or anyone else affected,"
1817020,2019-05-31 07:49:43 UTC,I have installed GNOME Shell 3.28.4-0ubuntu18.04.1 from proposed.
1817020,2019-03-12 14:40:07 UTC,Fixed in gnome-shell 3.32.0-1ubuntu1
1817020,2019-03-12 15:17:58 UTC,"For me things got a lot better when i deleted a ""pixel saver"" plugin from ~/.config/ or ~/.local or some such."
1817022,2019-06-01 03:05:44 UTC,"Reviewed:  https://review.opendev.org/660074
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6e661ecd2de3994de25af0337f7e2ae781c2cca9
Submitter: Zuul
Branch:    stable/stein"
1817022,2019-06-04 13:41:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/663034"
1817022,2019-06-04 13:03:53 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/663024"
1817022,2019-06-04 14:35:42 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/663050"
1817022,2019-03-29 18:36:56 UTC,Retested with https://git.openstack.org/cgit/openstack/neutron/commit/?id=f898ffd71fba4f9b8fd9f4cb851fc3976d72396a and it makes a difference. Now need about 400 ports (~98K flows) before the problem happens. This is with OVS rebuilt to allow 1 sec inactivity probe.
1817022,2019-06-07 13:22:48 UTC,"Reviewed:  https://review.opendev.org/663024
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3e555347956acd8841951e5b18c2c6b59325e197
Submitter: Zuul
Branch:    stable/rocky"
1817022,2019-06-10 18:44:50 UTC,"Reviewed:  https://review.opendev.org/663034
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7891c7cd05ad5cff12b1f386cd116db408708371
Submitter: Zuul
Branch:    stable/queens"
1817022,2019-06-11 00:22:13 UTC,"Reviewed:  https://review.opendev.org/663050
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4ba9f694c63fcd2a9a3b1091e67a91d5496fe087
Submitter: Zuul
Branch:    stable/pike"
1817022,2019-05-20 10:07:57 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660074"
1817022,2019-06-04 15:03:10 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/663059"
1817022,2019-05-18 00:05:40 UTC,"Reviewed:  https://review.opendev.org/641681
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=540d00f68ecf1c11b0296922f965ef60d15d1a86
Submitter: Zuul
Branch:    master"
1817022,2019-03-08 10:18:25 UTC,"RFE is related to the second connection type (the per bridge openflow controller connection: ovs-vswitchd<->ovs-agent:6633), which can't be configured by ovs-agent now, and the errors under heavy load are:"
1817022,2019-03-29 14:37:46 UTC,InvalidDatapath: Datapath Invalid 104209607453507
1817022,2019-03-29 13:48:15 UTC,Reran with a LOG.exception(e) to show the exception from os_ken.
1817022,2019-03-11 17:25:35 UTC,Did some more scale testing and found increasing inactivity_probe can stop InvalidDatapath errors.
1817022,2019-03-08 15:26:11 UTC,"During the drivers meeting discussion, it was suggested that this script can be used to simulate load: http://paste.openstack.org/show/745685/"
1817022,2019-12-04 08:50:37 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/ocata
Review: https://review.opendev.org/663059
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1817022,2019-03-08 09:48:47 UTC,"The bug description mixes two distinct connection types:
1. the manager connection for ovsdb: ovs-agent<->ovsdb-server:6640.
2. the per bridge openflow controller connection: ovs-vswitchd<->ovs-agent:6633"
1817022,2019-03-07 15:18:49 UTC,"Let's talk about this at the drivers meeting, but from the logs you linked seems valid."
1817022,2019-03-07 14:36:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641681"
1817022,2019-05-17 14:49:32 UTC,This RFE was revisited today during drivers meeting and it was approved
1817023,2019-09-05 15:22:30 UTC,"Seeded back into main, as it has moved to py3."
1817023,2019-08-07 15:50:44 UTC,swift py3 support is well in progress.
1817023,2019-04-29 11:37:02 UTC,Adding swift upstream.
1817023,2019-04-29 11:48:46 UTC,"We are now down to: swift, duplicity/deja-dup, heartbeat and etckeeper."
1817026,2019-02-21 16:28:19 UTC,"Thanks for reporting this Daniel. We generally don't do stable point releases for clients. We do have options though. If there are specific bugs, then we can cherry-pick patches for those bugs."
1817026,2020-10-21 11:22:01 UTC,Marking this as incomplete as it is not actionable and hasn't been updated in a year and a half
1817026,2020-12-21 04:17:19 UTC,[Expired for Ubuntu Cloud Archive because there has been no activity for 60 days.]
1817027,2019-04-04 20:41:51 UTC,will do when it crashed again :)
1817027,2019-03-19 11:58:57 UTC,And the same with source references
1817027,2019-04-01 07:19:30 UTC,"Hi Thomas, you can follow [1] to report a bug upstream."
1817027,2019-03-31 16:34:00 UTC,"Id like to do that but i cant find a upstream bug, im not getting a window to report a bug or so, no notification in ubuntu if you mean that. I can confirm now that whenever i create a folder, hit refresh and try to rename it it always stops working and i need to restart samba service."
1817027,2019-03-19 12:36:18 UTC,"We see a crash in __strlen_sse2 but that seems ""expected"" to me as we are passing `src` to it.
And at the level above src is a null pointer."
1817027,2019-03-19 11:58:40 UTC,From the crash I got this:
1817027,2019-02-22 06:26:50 UTC,"Hi Thomas,"
1817027,2019-02-23 22:58:31 UTC,"Some extra info sambo: 2:4.7.6+dsfg~ubutnu-0ubuntu2.6
Crash
apport V. 2.20.9"
1817027,2019-02-23 22:56:31 UTC,"Ok thanks i will do that,"
1817027,2019-03-19 11:58:15 UTC,"Hi Thomas,
I forgot to subscribe back then and this lay for a while on the todo list of a coworker.
I now got made aware of your reply and will take a first look."
1817027,2019-02-21 09:10:50 UTC,here is the log file
1817028,2019-04-09 10:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817028,2019-06-09 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1817029,2019-03-11 09:49:44 UTC,"The reason why so many fields are missing is because when exporting a Checkbox session to a json submission, the jinja2 exporter removes the namespaces from the job id:"
1817029,2019-07-15 08:29:58 UTC,I've tried the MP by spineau [1] with the 18.04 cert client test plan (only a subset of tests).
1817029,2019-07-16 08:38:22 UTC,"The lost of status in the HTML report is a limitation of HEXR as it only supports pass,fail and skip statuses. When exporting to json checkbox maps for example 'not-supported' to just 'skip'."
1817031,2019-02-21 09:45:05 UTC,"No, it is ok as a bug."
1817031,2019-02-21 09:33:58 UTC,"Sorry, was intended to become a question."
1817037,2019-02-21 10:34:21 UTC,"Further commentary from ""whoopsie"":"
1817042,2019-02-25 14:11:07 UTC,Can you clarify if the IPV4 addresses are listed in juju show-machine X and in the status --format=yaml please?
1817042,2019-03-04 09:58:47 UTC,"juju show-machine does indeed show IPv4 fixed and (if associated) floating IPs, in addition to IPv6:"
1817042,2019-03-04 10:19:05 UTC,"""Is there an indicator you think Juju should be respecting to determine if the v4 vs the v6 address is preferred for default status output?"""
1817043,2019-02-22 12:28:23 UTC,"added: TracisCI build number in all places, where detailed version info is requested (Env.getSikuliVersionBuild(), IDE About info as examples)"
1817045,2019-02-21 10:52:39 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638391"
1817045,2019-02-22 03:00:27 UTC,"Reviewed:  https://review.openstack.org/638391
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3f38c58cffddf7f2763455cce9d0ebf875230994
Submitter: Zuul
Branch:    master"
1817046,2019-06-26 14:25:44 UTC,"Hi,"
1817049,2019-04-11 12:18:38 UTC,https://github.com/CanonicalLtd/subiquity/pull/451 has an implementation (and asciinema video) of opportunistically downloading/installing updates.
1817049,2019-04-11 04:00:00 UTC,"Thanks, Marc.  I think there are some doubts about what the ubiquity option actually does today or what it's supposed to do.  I think we can at least commit to ""install immediately after first reboot"", and probably opportunistically download/install while waiting for the user to click the 'reboot' button."
1817049,2019-04-10 01:11:26 UTC,"Today, ubiquity has the ""Download updates while installing Ubuntu"" option during installation, which will then be installed automatically after the first reboot. This bug was filed to obtain a similar feature."
1817049,2019-04-10 00:37:24 UTC,"We discussed this on a Foundations internal call this afternoon, and several counterarguments came up:"
1817049,2019-04-05 11:09:39 UTC,I would prefer simply installing all updates also.
1817049,2019-04-05 02:19:20 UTC,"On Thu, Apr 4, 2019 at 9:06 PM Seth Arnold <email address hidden>
wrote:"
1817049,2019-04-04 22:03:15 UTC,"Hi Marc, do you happen to know how to install security updates only via apt?"
1817049,2019-04-05 02:00:18 UTC,Two methods come to mind:
1817049,2019-02-21 12:42:17 UTC,"I think it's important to install security updates at a minimum, but I don't see any reason not to install them all, besides the time it would take to do so."
1817049,2019-02-21 12:30:09 UTC,Do you think it is important to be able to install security updates specifically vs just installing all updates?
1817049,2019-04-05 02:14:31 UTC,Certainly just installing all updates would be easier (very easy in fact). Maybe we should just do that.
1817050,2019-02-21 13:59:41 UTC,"What gadget does this happen with, and should it not be considered a bug in the gadget that it produces a layout that is incompatible with the layout as expected by the grub packages?"
1817050,2019-02-21 14:17:11 UTC,Something like this gadget.yaml will make this happen: https://paste.ubuntu.com/p/ncPBvvqD7W/
1817050,2019-02-25 16:35:23 UTC,"This feels to me like a missing piece in the current image build behavior. When preparing the classic image, we delegated the assembly of all grub (bootloader) bits to the gadget tree. Because of that, we were discarding the /boot/grub/* files from the root filesystem to not duplicate the boot info in both the rootfs build and the gadget build. But obviously we missed the fact that in case of grub, we need to have the bootloader configuration in both the boot partition and rootfs. Right now our gadget-prepared grub bits only go to the boot partition."
1817050,2019-06-05 14:42:21 UTC,So I worked on this quite recently and prepared two different solutions to the problem:
1817050,2020-01-16 13:27:26 UTC,"Alfonso, sorry this took so long - the work on this piece has been a bit pushed back and pushed back, which was also my fault. So after discussing this with Steve some more and investigating all other fancy approaches, we came to the conclusion that not clearing /boot/grub/ at all feels like the lesser evil. So I prepared a PR that reverts the design decision of clearing /boot/grub."
1817050,2020-01-16 15:17:09 UTC,"@Lukasz, +1 on the change, this should protect against breakages when updating grub-efi. Thank you!"
1817050,2020-04-28 08:40:50 UTC,(released in 1.9)
1817051,2019-05-29 20:46:55 UTC,Setting the region_name_for_services explicitly is a good workaround.
1817051,2019-04-12 23:29:10 UTC,This issue was fixed in the openstack/kolla-ansible 6.2.0 release.
1817051,2019-04-12 23:29:35 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.0 release.
1817051,2019-04-05 13:59:45 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.
1817051,2019-03-04 15:10:41 UTC,"Reviewed:  https://review.openstack.org/639308
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=43bb77fe977b4bc7e58de9b0d1c823e04d35abce
Submitter: Zuul
Branch:    stable/queens"
1817051,2019-02-26 11:09:24 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/639308"
1817051,2019-02-21 11:34:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638400"
1817051,2019-02-28 15:03:15 UTC,"Reviewed:  https://review.openstack.org/639307
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=124dbcecacf960c38c1ec48fd4c49df97e6ab70d
Submitter: Zuul
Branch:    stable/rocky"
1817051,2019-02-25 10:08:46 UTC,"Reviewed:  https://review.openstack.org/638400
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=54203843dd944211ef0b99e8c69d09638701a086
Submitter: Zuul
Branch:    master"
1817055,2019-06-04 19:29:28 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1817055,2019-06-20 23:16:05 UTC,The version of python-eventlet in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1817055,2019-06-20 23:15:41 UTC,The version of python-eventlet in the proposed pocket of Cosmic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1817055,2019-03-05 18:57:47 UTC,"Hello Pedro, or anyone else affected,"
1817055,2019-03-04 14:46:24 UTC,Patched versions of eventlet for bionic and cosmic uploaded for SRU Team review.
1817055,2019-03-05 19:06:16 UTC,"Hello Pedro, or anyone else affected,"
1817055,2019-02-23 14:05:04 UTC,"Also, despite those issues, charm is stating ""Ready/Active"" on its status"
1817055,2019-02-23 12:17:31 UTC,"To keep it registered, I've set up swift-proxy on Bionic containers (same configs as described on the main text of this bug)."
1817055,2019-02-23 12:15:20 UTC,"The problem disappears when switching to your PPA. However, I still see some trace on journalctl for swift-proxy: https://pastebin.ubuntu.com/p/RFzk7qRQ6J/"
1817055,2019-02-22 15:04:17 UTC,Patched packages for bionic/cosmic uploaded to:
1817055,2019-02-22 14:52:07 UTC,Distro issue; needs pick of:
1817055,2019-02-24 10:50:04 UTC,"Well, I've found out why charm is not complaining: systemctl is marking as SUCCESS despite failures on journalctl."
1817058,2019-02-21 13:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817058,2019-03-11 16:44:48 UTC,This bug was fixed in the package linux - 5.0.0-7.8
1817058,2019-04-02 10:45:28 UTC,This bug was fixed in the package linux-oem - 4.15.0-1035.40
1817060,2019-02-22 09:37:28 UTC,"Thanks for the report, I'm marking this public so the kernel team can more easily work with it."
1817060,2019-02-22 10:00:06 UTC,This change was made by a bot.
1817060,2019-03-13 09:48:54 UTC,This patch was already applied to the Bionic kernel as part of our upstream stable update (bug 1815234) and will be available on the next kernel SRU udpate.
1817060,2019-03-13 10:04:30 UTC,"Hi Jonathan,"
1817063,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1817063,2019-04-02 10:29:42 UTC,This bug was fixed in the package linux - 4.18.0-17.18
1817063,2019-03-15 23:37:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1817063,2019-03-11 16:44:48 UTC,This bug was fixed in the package linux - 5.0.0-7.8
1817063,2019-02-21 14:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817063,2019-03-15 23:31:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1817066,2020-05-05 18:59:04 UTC,"The installer properly populates both ESP's, and I can confirm I get a bootable system after yanking the first disk with just the installer's efforts. Brilliant!"
1817066,2020-05-05 10:58:25 UTC,The code to do that is in the grub-efi-amd64's maintainer scripts.
1817066,2020-05-05 08:23:20 UTC,Does the release fix ensure the ESP contents are in sync? I was unable to find any indication of such in the code nor in a test install.
1817066,2020-04-29 13:32:50 UTC,"What I have now is an Ubuntu Mini test system with root,  including /boot, on a raid1 array over two disks and 2 EFI partitions mounted at /boot/efi and /boot/eficopy."
1817066,2020-04-28 00:03:06 UTC,"The work that has been done so far is Ubuntu specific, Debian are welcome to take it too but I don't know of any plans to do so."
1817066,2020-04-26 10:21:18 UTC,"Thank you for this change.  When applying an update to a 20.04 system I was given the option of specifying two EFI partitions.  However when I did I ended up with an unbootable system,  just went into the grub command line."
1817066,2020-05-02 08:49:53 UTC,"Apologies but I'm not sure what is happening here.  The next day my machine wouldn't boot from either entry - I must have changed something but I'm not sure what.  However, I purged and reinstalled all the grub packages and now everything seems to be fine.  I'll have to watch out for the next grub update."
1817066,2020-04-21 00:31:46 UTC,It's very very late but this is landing for focal.
1817066,2019-12-30 20:08:17 UTC,"We are using this type of boot redundancy in production with a simple addon script in Bionic. The installation is done with two non-RAID ESP. It would be great to have it as an officially supported feature, raid or not."
1817066,2019-12-16 18:12:27 UTC,"Related: bug 1466150 discusses how ESP on RAID is a non supportable configuration, grub failing to install in this scenario"
1817066,2019-11-13 21:07:30 UTC,"This bug was filed as ""support ESP on raid"" but that's not really possible. What we will do is support installing (and updating) multiple ESPs, which will achieve the goal of allowing an install that can survive the total failure of a disk."
1817066,2019-02-25 21:35:40 UTC,"Well, you *can* put ESP on software raid, if you use a md metadata version that puts the metadata at the end so that the ESP still looks like a regular vfat partition to the firmware, e.g. https://outflux.net/blog/archives/2018/04/19/uefi-booting-and-raid1/ -- but that does seem more complicated than I was expecting because I didn't realize that the firmware writes to the ESP under some circumstances!"
1817066,2019-02-23 03:34:28 UTC,"Is this about supporting ESP on hardware or firmware/fake RAID then? Since it could not work on software RAID, I guess (the UEFI would be unable to read it, at least in a reliable way)."
1817066,2020-04-24 10:53:57 UTC,Do you know whether this will be included in Debian 10?
1817068,2019-12-16 16:13:32 UTC,"For reference, bug 1817066 intends to support installing to (and keeping up to date?) multiple separate ESPs."
1817070,2019-02-21 15:03:38 UTC,apport information
1817070,2019-02-21 15:03:37 UTC,apport information
1817070,2019-02-21 15:03:36 UTC,apport information
1817070,2019-02-21 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817070,2019-02-21 15:03:34 UTC,apport information
1817070,2019-02-21 15:02:59 UTC,apport information
1817070,2019-02-21 15:03:39 UTC,apport information
1817070,2019-02-21 15:03:35 UTC,apport information
1817070,2019-02-21 15:03:42 UTC,apport information
1817070,2019-02-21 15:03:43 UTC,apport information
1817070,2019-02-21 15:03:46 UTC,apport information
1817070,2019-08-14 06:15:25 UTC,Maybe related:
1817070,2019-02-26 11:42:32 UTC,"Yes, please do. Intel Graphics folks know better than me."
1817070,2019-02-25 07:07:26 UTC,@kaihengfeng Might this also be an USB issue? It seems to me that the root cause is somewhere in the order the USB-C to miniDP is detected. Does it make sense to post the issue there?
1817070,2019-02-21 15:39:37 UTC,"Ok. Please try latest DRM kernel here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2019-02-21/"
1817070,2019-02-21 15:14:42 UTC,"I don't this is going to work, as this port is for data only and not for displays"
1817070,2019-02-22 08:46:09 UTC,"Ok tried with new kernel but no change. I also figured out this is  nit related to the dock. Behaves the same when I connect the adapter directly to thunderbolt port on the laptop. Order matters here as well. First adapter, then cable :).
I will then create a bug for Intel graphics."
1817070,2019-02-21 15:03:55 UTC,apport information
1817070,2019-02-21 15:03:53 UTC,apport information
1817070,2019-02-21 15:03:51 UTC,apport information
1817070,2019-02-21 15:03:49 UTC,apport information
1817070,2019-02-21 15:03:47 UTC,apport information
1817070,2019-02-21 15:04:08 UTC,Seems like Caldigit TS3 Plus has a front USB-C port. Does this issue happen when using that port instead of Thunderbolt port?
1817073,2019-10-21 14:53:33 UTC,"Too quick on that one, was not fixed just by reinstalling gnome-shell-extension-appindicator. Now i also noticed that this isn't just in the game, the whole desktop freezes for a moment when talking in discord if the appindicator package is installed.
Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. Didn't notice before since gnome performance wasn't that good by itself up until now."
1817073,2019-02-21 14:53:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817073,2019-02-26 14:55:01 UTC,"That doesn't seem to hit lot of users, setting rls-dd-notfixing but we should still have a look if possible"
1817073,2019-03-13 21:30:17 UTC,Similar bug affects me and puts a hit on performance. When speaking in discord there is supposed to be an icon change and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40.
1817073,2019-10-20 14:36:29 UTC,"Didn't have a problem with this in 19.04, but after upgrading to 19.10 it's back..."
1817073,2019-10-20 14:48:51 UTC,Answer #15 from bug #1825623 fixed it though
1817073,2020-03-24 12:24:58 UTC,This bug was fixed in the package gnome-shell-extension-appindicator - 33-1
1817076,2019-02-21 15:20:25 UTC,"In cases where errors are associated with a specific deck, I think this is a good idea."
1817077,2019-02-22 06:39:21 UTC,"Hi John,
the report has a lot of red herrings (all the error device is in use), but IMHO in the log the error that you hit was."
1817077,2020-04-20 17:17:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817077,2020-04-20 20:59:39 UTC,Prévisualisation du noyau 5.3 disponible en tant que noyau Linux-aws-edge.
1817077,2020-04-22 18:16:42 UTC,"@dbalde, send messages here in English please. I could translate you comment but your attachment make me think whether it is just a spam message."
1817085,2019-02-22 11:27:03 UTC,Any change to SR-IOV configuration should trigger a remote restart in nova-compute:
1817085,2019-02-22 11:48:39 UTC,"It does indeed trigger a remote restart but the fact that nova does not take the VFs into account might be due to several factors:
- Timing issue: the restart happens too fast just after the creations of the VFs
- nova-compute is restarted before neutron-sriov-agent. See https://github.com/openstack/charm-neutron-openvswitch/blob/ee81e0eaf53a9b64319947565b378cee3e5d5f88/hooks/neutron_ovs_utils.py#L663-L672"
1817085,2019-02-25 15:30:47 UTC,Nova is not depending of neutron-sriov-agent to read the VFs. Nova is referring to libvirt which refers to udev events to update its cache.
1817085,2019-02-26 09:50:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639285"
1817085,2019-02-28 13:14:54 UTC,Can you provide full log of nova.conf in debug?
1817085,2019-03-04 08:55:48 UTC,"Change abandoned by sahid (<email address hidden>) on branch: master
Review: https://review.openstack.org/639285
Reason: nova-compute is already restarted after any config change."
1817091,2019-03-07 05:18:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817097,2019-05-29 08:00:16 UTC,"------- Comment From <email address hidden> 2019-05-29 03:51 EDT-------
IBM bugzilla status -> closed, Fix Released by Canonical"
1817097,2019-05-28 17:46:31 UTC,Updated package landed in release pocket - changing project entry to Fix Released.
1817097,2019-05-28 17:01:29 UTC,This bug was fixed in the package e2fsprogs - 1.45.1-1ubuntu1
1817097,2019-05-24 12:04:44 UTC,"Modified version e2fsprogs 1.45.1-1ubuntu1  still in eoan-proposed.
Once it left proposed this ticket will be changed to Fix Released (e2fsprogs and project)."
1817097,2019-05-15 19:32:52 UTC,"With Eoan we now always default to 4k, hence Fix Released in e2fsprogs and the project."
1817097,2019-03-13 09:27:49 UTC,"Decreasing importance from critical to medium, because the bug is known to the community, it is already discussed in RH Bug 1669751, and here https://www.redhat.com/archives/linux-lvm/2019-February/msg00018.html / https://www.redhat.com/archives/linux-lvm/2019-March/msg00000.html, and not platform specific, nor specific to a certain Ubuntu release.
On top there are actions possible to easily avoid this situation, like explicitly setting / forcing the sector size to be 4096 bytes or using a bigger image size (>512 MB - which is not uncommon), so that the sector size default changes to 4k anyway.
A patch was already suggested upstream:
https://sourceware.org/git/?p=lvm2.git;a=commit;h=dd6ff9e3a75801fc5c6166aa0983fa8df098e91a
Once that patch got upstream accepted and became picked-up in a new lvm2 version, it will eventually land in Ubuntu, too."
1817097,2019-03-11 15:25:26 UTC,"/etc/mke2fs.conf:
[defaults]
 blocksize = 4096
[fs_types]
 small = {
  blocksize = 1024
  inode_size = 128
  inode_ratio = 4096
 }"
1817097,2019-03-11 15:11:53 UTC,"This is a well-known upstream issue/bug.
This is not s390x, Ubuntu 18.10, any other Ubuntu release specific.
There is no dataloss -> one can execute pvmove operation in reverse (or i guess onto any 512 sector size PV) to mount the filesystems again."
1817097,2019-03-11 14:04:25 UTC,"Ok, reproduced this on x86_64 with raw files which are in multiples of 4k."
1817097,2019-03-11 12:29:28 UTC,"------- Comment From <email address hidden> 2019-03-11 08:22 EDT-------
The message ""Device size is not aligned to the requested sector size."" is because the size of your loopback device is not a multiple of 4096 bytes. With --sector-size 4096, it's size must be a multiple of 4096 bytes, otherwise you would a half sector at the end of the device."
1817097,2019-01-26 17:38:46 UTC,Description of problem:
1817097,2019-03-05 22:43:42 UTC,"Here's an initial, lightly-tested solution to the VG-consistency part.  It does not address the issue of checking that a given LV is used with a consistent sector size.  Perhaps if a user overrides the VG consistency check, it should be their responsibility to ensure LVs are consistent."
1817097,2019-02-25 18:25:05 UTC,"Interesting, I asked about this here few weeks ago:
https://www.redhat.com/archives/linux-lvm/2019-February/msg00002.html"
1817097,2019-02-25 15:51:54 UTC,"Another report of this problem
https://www.redhat.com/archives/linux-lvm/2019-February/msg00018.html"
1817097,2019-02-22 10:29:24 UTC,"------- Comment From <email address hidden> 2019-02-22 05:23 EDT-------
Further investigations revealed that no dm-crypt mapper device is needed at all to reproduce the behaviour but just two block devices with different physical block sizes, e.g."
1817097,2019-02-21 17:59:26 UTC,"------- Comment From <email address hidden> 2019-02-21 12:51 EDT-------
There is a minor correction needed to the setup outlined above, as the enc-loop mapper device is backed by the second loopback device, and the volume group consists of the two devices listed in [ ] :"
1817097,2019-02-21 16:19:22 UTC,Default Comment by Bridge
1817097,2019-02-21 16:19:21 UTC,Default Comment by Bridge
1817097,2019-01-28 16:46:28 UTC,Basically that's what we have agreed in meeting - since we don't know yet how to handle different sector-sized PVs.
1817097,2019-01-28 15:53:23 UTC,Should we just require all PVs in the VG to have the same sector size?
1817097,2019-03-11 11:59:49 UTC,"I see that this bug was created with Ubuntu 18.10 (judging by the tags).
I am trying to reproduce the issue on Ubuntu 19.04 (current development release)."
1817119,2019-03-10 18:52:27 UTC,"Reviewed:  https://review.openstack.org/635312
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=5b85ad8c3f2f13003143b0810679466341dd95bc
Submitter: Zuul
Branch:    master"
1817119,2019-03-10 11:09:26 UTC,"Reviewed:  https://review.openstack.org/635311
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5e0fc3d2da6fbc5154debcc4a98bb8b6419326f9
Submitter: Zuul
Branch:    master"
1817119,2019-02-23 10:27:20 UTC,"Reviewed:  https://review.openstack.org/635313
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=c0a6d727c85b92ed22f5eda434f4f6576177180d
Submitter: Zuul
Branch:    master"
1817119,2019-02-22 01:35:27 UTC,This makes sense to me. Let's discuss it in the drivers meeting
1817119,2019-02-22 14:13:15 UTC,This RFE was discussed and approved by the drivers team
1817121,2019-02-25 06:03:38 UTC,This sounds like a good idea.
1817122,2019-03-22 05:39:03 UTC,I agree that this behavior is misleading and not very intuitive.
1817122,2019-07-15 01:48:11 UTC,PR for develop: https://github.com/juju/juju/pull/10439
1817123,2019-06-17 22:19:34 UTC,Just got the same bug again in Disco Dingo.
1817123,2019-03-15 07:02:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817123,2019-04-28 22:56:07 UTC,"Apr 28 18:34:20 fred-Z170N-disco systemd-tmpfiles[615]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
Apr 28 18:34:20 fred-Z170N-disco systemd-tmpfiles[615]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly.
Apr 28 18:34:20 fred-Z170N-disco systemd-tmpfiles[615]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
Apr 28 18:34:20 fred-Z170N-disco systemd-tmpfiles[615]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
Apr 28 18:34:20 fred-Z170N-disco systemd-tmpfiles[615]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly.
Apr 28 18:34:20 fred-Z170N-disco systemd-tmpfiles[615]: [/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly."
1817123,2020-05-16 21:25:19 UTC,"Fixed in version speech-dispatcher/0.9.1-4
Fixed in version spice-vdagent/0.19.0-1"
1817124,2019-04-05 17:53:38 UTC,"Fixed in revision e563184eace8b1fe8d5d1c60fa46f11ebc25606a
https://git.launchpad.net/kicad/patch/?id=e563184eace8b1fe8d5d1c60fa46f11ebc25606a"
1817124,2019-03-08 10:41:06 UTC,"@Evan: Yeah, I just wanted to post that bug/feature.request also. I think ""Plot"" should be in the ""Fabrication outputs"" sections, exactly as you wrote. Named ""gerber"" and just pointing to the plot command preselected the gerber output. One point less for people new to kicad to search. And that´s always better ;-)"
1817124,2019-02-21 17:55:42 UTC,That's a good catch.  I'm glad you were able to sort through the excess to find a useful item!
1817125,2019-02-21 17:45:39 UTC,"Thanks, good point."
1817125,2019-02-21 18:14:26 UTC,please give it a test (no chance currently to do that)
1817127,2019-02-22 12:39:21 UTC,"@Evan, I seem to remember a bug report about this already being filed but I could be wrong.  There may have even been a patch to provide mils as a third unit option."
1817127,2019-02-22 16:56:16 UTC,"In the video, Dave was asking for dynamic updates of the dialog in addition to the units. I don't know that it's possible to click a toolbar icon when a blocking dialog is open so I'm not sure this is possible. But anyway, just letting you know this video Seth pointed out (from an Altium user) contained this request."
1817127,2019-02-22 17:13:53 UTC,I'm pretty sure that Jeff has implemented most of this already.
1817133,2019-03-25 11:24:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817133,2019-02-21 20:20:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1817180,2019-02-21 19:02:39 UTC,"Ah, this was meant for Debian, sorry and feel free to close it (or maybe update Xenial? :D)"
1817199,2019-02-21 19:30:00 UTC,"and in the terminal I got this:
(menulibre:19168): Gtk-WARNING **: 14:15:52.875: gtk_menu_attach_to_widget(): menu already attached to GtkMenuButton"
1817208,2019-02-25 18:39:47 UTC,apport information
1817208,2019-02-25 18:39:48 UTC,apport information
1817208,2019-02-25 18:39:50 UTC,apport information
1817208,2019-02-25 18:39:39 UTC,apport information
1817208,2019-02-25 18:39:53 UTC,apport information
1817208,2019-02-25 18:39:46 UTC,apport information
1817208,2019-02-25 18:39:51 UTC,apport information
1817208,2019-02-25 18:39:44 UTC,apport information
1817208,2019-02-25 18:39:37 UTC,apport information
1817208,2019-02-25 18:39:42 UTC,apport information
1817208,2019-02-25 18:39:41 UTC,apport information
1817208,2019-02-25 18:39:38 UTC,apport information
1817208,2019-02-25 18:39:54 UTC,apport information
1817208,2019-02-25 18:39:34 UTC,apport information
1817208,2019-02-25 02:04:32 UTC,Please run this command to send us more information about the system:
1817208,2019-02-25 18:39:43 UTC,apport information
1817209,2019-10-31 03:53:03 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1817210,2019-10-31 03:53:23 UTC,Removing from a milestone as this work will not be done in 2.5 series.
1817211,2019-11-13 21:08:46 UTC,"I think this bug is fixed yes, but I can't test it myself and I haven't heard any reports back. If someone can test it, I'd happy close it!"
1817211,2019-10-04 17:29:33 UTC,@mwhudson was this fixed and the bug not updated?
1817211,2019-02-25 16:15:18 UTC,Perfect. Thank you so much for this!
1817211,2019-02-22 07:04:43 UTC,"To be clear, this is more ""firmware raid"" (i.e. imsm) than software raid, right? If so, it's on the list to be fixed before 19.04."
1817211,2019-02-22 16:53:59 UTC,"Well, that's what is integrated into intel's motherboard. The major difference with the normal raid cards is that I can still see the physical devices in the OS, as well as mdraid device created by the controller.
Is it somehow appear in the roadmap list? So that I can prove it to the customer.
Thanks!"
1817211,2019-02-23 17:59:11 UTC,"Yes, that's the thing I mean. It is going to be fixed as part of the ""reusing existing partitions"" roadmap item."
1817212,2020-01-12 21:16:08 UTC,Closing as not seen in sanity since upversioned to train.
1817212,2019-10-30 01:47:48 UTC,The fix for the duplicate bug was merged on 2019-09-16; marking as Fix Released
1817212,2019-09-03 08:48:55 UTC,"if set tcp_tw_recycle=1 , then pass 150 times pause/unpause vm in AIO. if set tcp_tw_recycle=0, pause/unpause vm will fail ~30 times in AIO. so it should be same as https://bugs.launchpad.net/starlingx/+bug/1817936. but tcp_tw_recycle=1 will cause openstack horizon access issue, need investigate more for 1817936 solution."
1817212,2019-08-23 17:45:22 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1817212,2019-08-23 17:45:14 UTC,Removed the duplicate link based on the comment above
1817212,2019-07-09 00:58:04 UTC,"duplicate bug #1817936, once bug #1817936 is fixed, please verify this issue if fixed or not."
1817212,2019-06-11 03:08:04 UTC,"in AIO setup. this issue can be reproduced, i will investigate further."
1817212,2019-06-07 08:20:18 UTC,"The tests are done in latest version on virtual environment:
  1) Pause and unpause more than 500 times
  2) set and unset property more than 1000 times on flavor .
  3) run  script 10000 times to curl nova-api  which is provided by Bart in [1]"
1817212,2019-07-30 09:06:15 UTC,"There are a lots of 'iptables-in-dropped' in kern.log , it might be not same as bug1817936."
1817212,2019-04-17 16:56:33 UTC,It is possible that this bug has the same root cause as https://bugs.launchpad.net/starlingx/+bug/1817936 - that possibility should at least be investigated.
1817212,2019-04-17 13:40:21 UTC,Issue was reproduced on
1817212,2019-04-04 00:44:46 UTC,"I will set this issue to invalid now, if you still can produce this issue, could you provide the detail log."
1817212,2019-04-04 00:44:29 UTC,"used latest version 20190401T233000Z on multi-node deploy.
can not reproduce this issue when run 100 times nova pause/unpause command
1) could you check latest iso?"
1817212,2019-03-15 19:36:04 UTC,Assigning to Cindy to identify a prime to work on this issue.
1817212,2019-02-22 19:35:30 UTC,Marking as release gating; issue impacts container env. medium priority as the issue is intermittent.
1817212,2019-04-19 02:43:08 UTC,from ./nova-api-osapi-6474c75c7-jk522_openstack_nova-osapi-cb68c66b7a33817d7d6ea579fa4752d962d0164ccc3697d67043beeae0732944.log
1817214,2019-02-25 19:59:45 UTC,"> It can now be deduced that their scanner URIs are definitely
"
1817214,2019-02-23 15:29:18 UTC,In /usr/share/hplip/data/models/models.dat there is a section for each device supported by HPLIP. For example
1817218,2020-07-18 00:05:29 UTC,"Reviewed:  https://review.opendev.org/638307
Committed: https://git.openstack.org/cgit/x/networking-vpp/commit/?id=f661e06e4ac3b906e1d9591ac101bcbb1f077f72
Submitter: Zuul
Branch:    master"
1817225,2019-02-22 16:09:22 UTC,Ran
1817225,2019-03-19 16:34:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817225,2019-03-21 04:59:06 UTC,It also affects Kubuntu 18.04.2
1817225,2019-03-21 07:32:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817225,2019-03-22 17:38:05 UTC,​​​​please test on cosmic or disco
1817225,2019-04-03 22:12:17 UTC,I can confirm that this works. Thank you Thiago!
1817225,2019-04-05 07:39:43 UTC,"Ok, so xrdp in bionic builds modules for the xserver, which won't work with the HWE xserver. These modules got since split from src:xrdp as src:xorgxrdp. Note that xrdp in bionic did not have these modules, so this issue is new with bionic HWE and wasn't expected."
1817225,2019-02-22 16:07:40 UTC,apport information
1817225,2019-07-23 21:19:32 UTC,..by making sure xrdp-hwe-18.04 is installed
1817225,2019-07-24 11:56:22 UTC,"Confirmed, your staging PPA fixes it for our Hyper-V image"
1817225,2019-08-08 22:06:21 UTC,"Hello Rushi, or anyone else affected,"
1817225,2019-08-12 20:44:14 UTC,Confirmed this works in the Hyper-V 18.04 desktop image.
1817225,2019-08-20 15:48:58 UTC,This bug was fixed in the package xrdp-hwe-18.04 - 0.9.5-2~18.04.1
1817225,2019-08-20 15:49:05 UTC,"The verification of the Stable Release Update for xrdp-hwe-18.04 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1817225,2019-07-23 21:18:27 UTC,"src:xrdp-hwe-18.04 uploaded to ppa:canonical-x/x-staging, please test!"
1817225,2019-02-22 16:07:38 UTC,apport information
1817225,2019-02-22 16:07:19 UTC,apport information
1817225,2019-02-22 16:07:32 UTC,apport information
1817225,2019-02-22 16:07:34 UTC,apport information
1817225,2019-03-30 03:33:35 UTC,And here is the xrdp-0.9.9 and xorgxrdp-0.2.9 for Bionic HWE!
1817225,2019-02-22 00:19:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1817225,2019-02-22 09:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817225,2019-02-22 16:07:17 UTC,apport information
1817225,2019-03-30 04:22:46 UTC,I'll maintain the following repo:
1817225,2019-02-22 16:07:20 UTC,apport information
1817225,2019-03-30 03:19:49 UTC,"So, there is a need to rebuild xrdp against HWE 18.04."
1817225,2019-02-22 16:07:23 UTC,apport information
1817225,2019-02-22 16:07:24 UTC,apport information
1817225,2019-02-22 16:07:25 UTC,apport information
1817225,2019-02-22 16:07:27 UTC,apport information
1817225,2019-02-22 16:07:28 UTC,apport information
1817225,2019-02-22 16:07:29 UTC,apport information
1817225,2019-02-22 16:07:21 UTC,apport information
1817225,2019-02-22 16:07:31 UTC,apport information
1817227,2019-06-23 04:19:13 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1817227,2019-04-23 23:56:10 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We noticed that you were installing the LTS version of Ubuntu using an older version of the installation media.  The latest point release of 16.04 is 16.04.3. Please try installing from that version of the installation media and see if that resolves your issue. Thanks in advance!
1817227,2019-02-25 14:45:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1817228,2019-02-22 02:31:56 UTC,"I upgraded to Ubuntu 18.04, and now it gets to:"
1817228,2019-02-22 04:03:39 UTC,"Upgraded gcc to 8 and set it to be used via sudo update-alternatives --config gcc, still have same problem."
1817228,2019-02-23 23:23:38 UTC,"ran it with strace, last few lines are:"
1817228,2019-02-24 04:58:22 UTC,I ran it with valgrind and turned binaries off for pip:
1817232,2019-08-27 20:28:17 UTC,"Correct, those items were just some possibilities I mentioned based on thinking about the frustration shared in the video. It wasn't my original request."
1817232,2019-08-21 21:22:17 UTC,"@Michael, those were just off the top of Evan's head."
1817232,2019-08-21 20:46:10 UTC,"@Jeff, there are already a number of suggested items in the bug description that don't yet exist."
1817232,2019-07-26 12:22:53 UTC,Some of these were added in commit bb290abe91e7e47596ee93c8a9ec383e82a54816
1817232,2019-03-02 08:50:48 UTC,Would be useful to have SMD/TH pad count info to estimate assembly costs.
1817232,2019-08-21 18:44:08 UTC,"The board statistics dialog has been implemented.  If there are items missing from it, please log specific requests."
1817232,2019-03-01 17:53:59 UTC,"Sure. Maybe I shouldn't have used the word ""dialog"" since Dave was only asking for info."
1817232,2019-02-22 12:44:58 UTC,"Most of this information is already provided in the message panel when right clicking on any empty area of the canvas.  We certainly can add more status information to this panel.  I don't know how thrilled I am about adding another dialog to display information that is already being displayed now but if someone feels motivated to provide such a dialog, I will consider it.  I really want to avoid duplicating features from other EDA tools just because users think we should.  If we can provide a better solution (which I think we partially already do) than we should explore that."
1817234,2019-05-08 11:00:31 UTC,"Hi Raúl, I packaged python-ebooklib originally. I no longer use this package personally, but if you would like to see a new version please forward this bug to Debian and I will help get it updated there."
1817234,2019-05-14 03:43:59 UTC,"With all due respect, this kind of response is ridiculous. Don't take
this personally, I'm talking about the situation, not your reply."
1817234,2019-10-15 09:55:37 UTC,"Hi Raúl, I'm not an Ubuntu developer so I'm not replying on behalf of Ubuntu, just myself. If you would like to see this package updated in Ubuntu, the best way to do that is to report it to Debian so that a new maintainer can be found. As Python 2 is going away, the package will be Python 3 only in future."
1817237,2019-11-15 21:52:27 UTC,This issue should be fixed with Catfish 1.4.6
1817239,2020-11-04 23:04:47 UTC,This series appears to have stalled as of v7: https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg04241.html -- moving back to 'New' status.
1817239,2019-02-22 07:32:57 UTC,"On 22/02/2019 04:31, Launchpad Bug Tracker wrote:

> I'd like to ask for the addition of option '--targets' to scripts/qemu-
> binfmt-conf.sh, in order to allow registering the interpreters for the
> given list of architectures only, instead of using all of the ones
> defined in qemu_target_list. The following is a possible patch that
> implements it:
>
>   qemu-binfmt-conf.sh | 9 ++++++++-
>   1 file changed, 8 insertions(+), 1 deletion(-)
"
1817239,2019-03-09 01:35:41 UTC,"I submitted a first version some days ago, which homogeneized the implementation, as suggested by Laurent Vivier. It received some feedback from Eric Blake. A patchset (v3) is ready for review: https://patchew.org/QEMU/20190306031221.GA53@03612eec87fc/#"
1817244,2019-09-13 11:11:03 UTC,"@Zebediah and all:
All gstreamer plugins are now coinstallable in Debian Bullseye (testing).  If there are any issues please tell me."
1817244,2019-09-18 08:01:48 UTC,https://discourse.ubuntu.com/t/community-process-for-32-bit-compatibility/12598/21 what needs to be done to make sure this change lands in eoan?
1817244,2019-09-18 17:11:10 UTC,"@vorlon: sync wine-development 4.14-1, just uploaded to Debian unstable."
1817244,2019-08-16 23:54:26 UTC,"$ dpkg-query -s libmpg123-0:i386
Package: libmpg123-0
Status: install ok installed"
1817244,2019-12-12 19:08:49 UTC,Closing.
1817244,2019-12-13 06:24:50 UTC,This bug was fixed in the package wine - 4.0.3-1
1817244,2019-09-18 22:55:15 UTC,"> @vorlon: sync wine-development 4.14-1, just uploaded to Debian unstable.
"
1817244,2019-08-15 00:42:34 UTC,"Our packages do not install gstreamer-plugins as a dependency because most Windows apps don't need them at all, and for those that do, which plugin package they actually need will vary greatly. It makes no sense to force additional dependencies on everyone when the majority don't need that functionality at all. Users who do need plugins can easily install the one(s) they need."
1817244,2020-12-14 20:38:44 UTC,*** Bug 50328 has been marked as a duplicate of this bug. ***
1817244,2019-08-14 17:30:45 UTC,"(In reply to Zebediah Figura from comment #1)

> In some specific cases libmpg123 alone can be used, but in general this
> isn't enough, no. Various applications need different codecs, some of which
> are available in -good, some in -bad, some in -ugly.
"
1817244,2019-08-14 16:56:33 UTC,"(In reply to Jens Reyer from comment #0)

> In this specific case I couldn't reproduce the issue as long as
> libmpg123-0:i386 was installed.  But I assume current Wine still generally
> needs them!?  Please comment.
"
1817244,2019-08-14 16:44:29 UTC,"Hi,"
1817244,2019-08-14 15:16:06 UTC,Thanks again. Probably my last round of nitpicking questions:
1817244,2019-08-10 19:29:53 UTC,"$ wine --version
wine-3.0 (Ubuntu 3.0-1ubuntu1)"
1817244,2019-08-10 17:01:23 UTC,Thanks for your answer.  Unfortunately not the hoped for outcome.
1817244,2019-08-10 16:16:55 UTC,"$ dpkg --print-architecture
amd64"
1817244,2019-08-10 00:27:09 UTC,"Hi Dave,"
1817244,2019-05-20 02:54:54 UTC,"Yeah, no GNOME. This was on Lubuntu (LXDE)."
1817244,2019-08-14 17:38:00 UTC,"(In reply to Jens Reyer from comment #2)

> (In reply to Zebediah Figura from comment #1)
> > In some specific cases libmpg123 alone can be used, but in general this
> > isn't enough, no. Various applications need different codecs, some of which
> > are available in -good, some in -bad, some in -ugly.
>
> Thanks! Can you also comment on ""gstreamer1.0-libav""?
"
1817244,2019-05-20 00:17:39 UTC,"Thanks for your report, you're right."
1817247,2019-10-01 14:21:05 UTC,This is fixed now based on the updated version.
1817247,2019-04-09 18:29:47 UTC,"Thanks, that source change makes sense.   Hopefully now that the similar bug:"
1817247,2019-04-09 15:06:40 UTC,"The correct source is linux-hwe, linux-signed-hwe is the signed binary of the former."
1817247,2019-03-12 22:06:12 UTC,"This report does not appear to have received any human's attention yet at Ubuntu, even though it was written weeks ago and is a significant performance/functionality concern that the --ops facility can not be used as is.  It must be patched.  Unfortunately for us in the interim, it was discovered that the -36 kernel we did the livepatch remedy for now has to be quickly replaced by a later kernel due to a TCP window performance problem fixed in a later maintenance release."
1817247,2019-04-09 03:11:58 UTC,The test kernel supplied for the 4.15 kernel in the 18.04LTS release fixed the identical issue there:
1817247,2019-02-22 19:07:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817253,2019-06-12 14:43:44 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1817253,2019-02-22 06:11:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638586"
1817253,2019-05-28 14:51:17 UTC,"Reviewed:  https://review.opendev.org/638586
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=09da336e9cec7295a9269fd1446a24f4ca94a742
Submitter: Zuul
Branch:    master"
1817260,2019-02-22 07:24:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638599"
1817263,2019-02-22 08:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817263,2019-03-15 23:31:49 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1817263,2019-03-15 23:37:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1817263,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1817263,2019-04-02 10:29:42 UTC,This bug was fixed in the package linux - 4.18.0-17.18
1817264,2019-02-22 17:16:23 UTC,"A little change in plans. len-ovenwerks and I discovered that, as it turns out, Patchage is still in active development despite not having a release in >3 years."
1817264,2019-02-22 17:16:58 UTC,"jack-rack, sorry for the wrong package name."
1817264,2019-02-22 17:30:24 UTC,"Just one thing to add: The version I packaged is 1.9.13 (2.0-RC3). falktx hopes to get 2.0-RC4 soon, and has given himself a rough deadline for a 2.0 release for the end of March. Depending on the timing, it would be good to get 2.0 (final) in for either an FFe or SRU, depending on the timing."
1817264,2019-02-22 23:55:05 UTC,*** This is an automated message ***
1817264,2019-03-30 02:55:26 UTC,carla (1.9.13-0ubuntu1) disco; urgency=medium
1817266,2019-03-11 14:55:30 UTC,"The verification of the Stable Release Update for glewmx has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1817266,2019-03-11 15:43:27 UTC,This bug was fixed in the package glewmx - 1.13.0-4ubuntu0.18.04.1
1817266,2019-03-11 14:55:23 UTC,This bug was fixed in the package glewmx - 1.13.0-4ubuntu0.18.10.1
1817266,2019-03-01 21:39:57 UTC,"Hello Andrea, or anyone else affected,"
1817266,2019-03-04 13:10:26 UTC,"I triggered a new rebuild in bileto and now Unity correctly builds both in cosmic and bionic:
https://bileto.ubuntu.com/log/3655/status/1018/
https://bileto.ubuntu.com/log/3654/status/1018/"
1817266,2019-03-01 21:38:24 UTC,"Hello Andrea, or anyone else affected,"
1817268,2019-02-22 11:58:41 UTC,"Thanks you, so it is a bug and not the expected behavior right ?"
1817268,2019-02-22 12:29:16 UTC,"Yes, I think so; although old-style block migration doesn't get much work on it now; so probably the fix I'd recommend for most cases now would be to pad the var file."
1817268,2019-02-22 10:29:18 UTC,"Hi David,"
1817268,2019-02-22 10:46:12 UTC,Yep that Length mismatch is expected - the source and destination do have to match.
1817268,2019-02-22 09:26:28 UTC,"Hi Mathieu,
  How big is your testuefi-VM_VARS.fd file ?   Does the problem go away if you pad it to 1MB?"
1817270,2019-02-22 09:00:48 UTC,"No bug there!
However I increase the zoom factor.
It is a factor of x5 faster when [Shift] is pressed to make the boost more tangible."
1817270,2019-03-07 10:45:30 UTC,It will never work as there is a limitation within Pharo to use whell mouse and modifier keys at the same time
1817272,2019-04-14 22:14:30 UTC,Will do.  (In the meantime I've fixed up the code policy issues.)
1817272,2019-04-14 21:31:56 UTC,"@Andrey, I've merged you patch.  Thanks for your contribution to Kicad!"
1817272,2019-04-14 14:16:11 UTC,Fixed
1817272,2019-04-14 21:51:33 UTC,"@Jeff, there were a few coding policy violations (trailing white space, missing spaces before and after braces, and line length greater than 99 columns) in the patch.  Please do not hesitate to ask the patch submitter to fix formatting issues.  Now that we have a commit hook for clang-format, getting the formatting correct is fairly trivial."
1817272,2019-04-10 06:12:13 UTC,"Ok.
patch rebase for current master"
1817272,2019-04-09 16:51:00 UTC,Master is now open for 6.0.
1817272,2019-02-22 14:45:22 UTC,This patch for the current master (5.1.0-rc). This is a functional from the branch kicad-gost-committers.
1817272,2019-02-22 13:52:44 UTC,"I'll set this to v6 so that we can look at merging as soon as the window opens.  At first glance, I see no issues with this patch.  Anyone else?"
1817272,2019-04-12 10:06:26 UTC,"@Andrey, can you recreate the patch using git format-patch?  If I commit a diff-based patch it will go in under my name rather than yours."
1817274,2019-02-24 10:52:34 UTC,"I more and more think of a user configurable order for paymode.
I do think that would solve your problem and enable to position debit card at first."
1817274,2019-05-20 07:41:53 UTC,from 1817462
1817275,2020-05-11 21:53:11 UTC,"This is fixed, but I don't recall by what."
1817275,2020-05-11 20:12:25 UTC,"Is this still an issue, or was this resolved by updates to MAAS or Maniacs-setup?"
1817276,2019-02-22 11:21:45 UTC,I see a similar behavior on a machine using btrfs for both host and containers
1817276,2019-10-29 21:35:50 UTC,The referenced pull request was merged into snapd. I'm marking this as fix committed.
1817276,2019-12-05 10:06:43 UTC,"I'm still seeing this issue on conatiners when ""core"" is also installed."
1817276,2020-02-20 16:38:45 UTC,"I was trying to reproduce this with the following setup:
- 19.10 (eoan) VM with clean image with ext4 fs
- installed lxd/3.20 snap
- created bionic container
- installled snapd in the contains and the maas snap
- then installed manually core
- rebooted both host and container
- ran ""maas init"" and watched ""top"" output - I see 1-2 snapfuse processes taking up to 60% cpu"
1817276,2020-02-20 16:56:09 UTC,"I just re-did my test with btrfs as the lxd storage pool and see similar behavior as before, cpu of snapfuse hoovers around 20-30% with some spikes to ~65%. Maybe I'm missing something to reproduce?"
1817276,2020-02-20 17:15:06 UTC,"I was asked for the supervisor log: http://paste.ubuntu.com/p/MkgJwgfhnf/ - my test system got up to 1600 processes and was close to OOM, I wonder if maybe this is causing the high snapfuse cpu load. But could be just coincidence of course."
1817276,2020-02-20 18:05:54 UTC,"I am having a similar issue. Brand new maas 2.7 running as a snap on ubuntu lts 18.04.
Here is brief supervisor log:
https://paste.ubuntu.com/p/tqgfT6P362/"
1817276,2019-09-20 10:19:28 UTC,"I believe this was debugged and fixed yesterday. Assigning to mvo, who did the work, for tracking."
1817276,2020-02-20 19:09:43 UTC,@Paul thanks! this looks super similar to what I see. The number of processes keeps growing it seems.
1817294,2019-02-22 14:40:27 UTC,"This is by design since you are not the owner of the device.  If you want
to own the device then MAAS has to send snap user info and email to become
the owner and consoleconf won’t run if the device is owned."
1817294,2019-02-22 16:01:21 UTC,"Thanks, That makes a lot of sense. What about if you use a custom network configuration? For example say I create an assertion to manually configure the network with a netplan yaml? You still end up in this same situation, and the only way to fix it is to mount the image, and manually 'touch' complete in to /var/lib/console-conf on the writable partition so that I can login to the device?"
1817294,2019-02-22 16:18:45 UTC,"You can’t take over network when MAAS, you need to model what you want in
MAAS and MAAS sends configure networking and cloud init will apply."
1817294,2019-03-26 18:09:55 UTC,"A potential customer is running into this issue. They are using Cloud-init to create users on the device and while it is not impacting the use of the device, if someone connects to the console, they see that the device is not configured and when they try to configure it, they get the netplan error and cannot move forward.
They are using the work around I mentioned in comment 2 to get around this bug. They would like to see it so that if using cloud-init to configure the device, console-conf should not run."
1817307,2019-11-28 10:26:50 UTC,"As nothing happened I reported it to Debian myself now.
Bug is linked above (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945764)"
1817307,2019-07-29 19:10:36 UTC,Cosmic is EOL
1817307,2019-03-05 21:43:31 UTC,This bug was fixed in the package ipmitool - 1.8.18-6ubuntu1
1817307,2019-03-04 14:29:01 UTC,"@paelzer, yes will do"
1817307,2019-03-01 11:18:57 UTC,@Manoj - Andreas is working on getting this into Disco. But since upstream releases [1] rareley or lets call it sporadic could you plesae file a bug in Debian as well to ensure we can somewhen into 19.10 drop the Delta?
1817307,2019-02-28 13:56:28 UTC,I wonder if it's this upstream bug: https://github.com/ipmitool/ipmitool/issues/72
1817307,2019-02-28 14:35:06 UTC,Package with that patch building in this PPA: https://launchpad.net/~ahasenack/+archive/ubuntu/ipmitool-segfault-1817307
1817307,2019-02-28 14:13:52 UTC,"With the patch being:
https://github.com/pjdhpe/ipmitool/commit/815aae70cf8dc9f0e1ba1923fc4ec3cc16d0d2f1"
1817307,2019-02-22 11:54:30 UTC,"StacktraceTop:
 memmove (__len=<optimized out>, __src=0x564d10980b75 <rsp+21>, __dest=0x564d10980b61 <rsp+1>) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:40
 ipmi_lan_poll_single (intf=intf@entry=0x564d1097d720 <ipmi_lanplus_intf>) at lanplus.c:878
 ipmi_lan_poll_recv (intf=0x564d1097d720 <ipmi_lanplus_intf>) at lanplus.c:913
 ipmi_lanplus_recv_sol (intf=0x564d1097d720 <ipmi_lanplus_intf>) at lanplus.c:2693
 ipmi_sol_red_pill (intf=intf@entry=0x564d1097d720 <ipmi_lanplus_intf>, instance=instance@entry=1) at ipmi_sol.c:1650"
1817307,2019-02-28 17:12:19 UTC,"I tested the ipmitool in the above PPA on the same machine this crash was reported from, and I was able to power off/on the system who's output triggered this crash. I can report that ipmi sol does not crash and the console connection is persistent."
1817309,2019-02-22 12:42:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638655"
1817309,2019-03-11 19:22:42 UTC,"Change abandoned by Rafael Folco (<email address hidden>) on branch: master
Review: https://review.openstack.org/638655
Reason: wrong spot"
1817310,2020-03-10 18:50:03 UTC,"Can we get this in for focal? It should be much easier, since it already has the f2fs.mod, the only backport required should be this commit to add the f2fs module to the efi image:"
1817310,2019-06-01 10:46:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817311,2019-02-22 14:20:25 UTC,"Change abandoned by Rafael Folco (<email address hidden>) on branch: master
Review: https://review.openstack.org/638668
Reason: <EvilienM> weshay, rfolco|rover : not sure we want https://review.openstack.org/#/c/638668/ in Stein
<EvilienM> I think we need to properly deprecate the service
<EvilienM> and remove in the next release"
1817311,2019-02-22 16:26:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/638701"
1817311,2019-02-22 14:14:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/638668"
1817311,2019-02-22 13:57:15 UTC,"site is up again and repo is again reachable
https://nexus.opendaylight.org/content/repositories/opendaylight-oxygen-epel-7-x86_64-devel/repodata/"
1817311,2019-02-22 12:09:11 UTC,Pretty sure we can remove opendaylight from Stein
1817311,2019-02-22 12:04:26 UTC,"https://nexus.opendaylight.org/ is currently down. Slow, times out. The container build job is unable to build opendaylight container because it can't get the repo information from the site."
1817312,2019-02-22 11:56:47 UTC,This might be related: https://bugs.launchpad.net/kicad/+bug/1754130
1817312,2019-02-22 13:01:33 UTC,"@Ortwin, are you sure that Eagle zone fills subtract off the zone outline line width when performing fills?  This doesn't make any sense to me but it's possible.  Anyone else have any Eagle experience that could shed some light on this issue?  If this is the case then we should adjust the zone outline accordingly.  Also, don't expect Eagle imports to produce identical boards.  Eagle has some features that KiCad does not so all imports need to be carefully reviewed."
1817312,2019-02-22 13:23:47 UTC,Not sure I understand you correctly. Eagle zone fill does not subtract by adds the line width by my experience. I'll try to illustrate with example pictures.
1817312,2019-02-22 13:31:22 UTC,Adding screenshots of KiCad behaviour as well.
1817312,2019-02-22 14:44:40 UTC,"You images appear to support what I described.  It looks like Eagle uses the line thickness to created the inside edge for the zone filling where KiCad doesn't use any zone line thickness.  This means that we are off by 1/2 the zone line thickness when importing Eagle boards.  That being said, no one else has filed a bug report on this so I am suspicious that there may be an option setting in Eagle that defines if the zone fill uses the line segment width or not so we should proceed with caution here."
1817312,2019-02-22 15:16:27 UTC,I have tried this with our workplace Eagle 9.2.2 as well as a fresh unconfigured Eagle 6.6.0 and both behave the same way. I have had a few customer layouts that obviously expected the Eagle behaviour because the output in KiCad had anomalies while in Eagle it looked more sane. I do however agree that somebody with deeper understanding of these tools should take a look as well.
1817312,2019-02-26 00:47:50 UTC,@Ortwin-
1817312,2019-02-26 11:46:04 UTC,Here are some example pictures.
1817312,2019-02-26 13:24:02 UTC,Perfect.  Thank you very much for the details.  We'll get this adjusting in v6.
1817312,2019-05-21 22:43:47 UTC,"Fixed in revision 490c805319974ec84a8fbe8b10e9b59b9a3922a6
https://git.launchpad.net/kicad/patch/?id=490c805319974ec84a8fbe8b10e9b59b9a3922a6"
1817315,2019-02-22 13:16:58 UTC,"This job is passing in TripleO CI.
Also in RDO Third Party CI jobs are passing as the hostname seems correct:"
1817315,2020-07-11 04:17:40 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1817316,2019-03-07 16:32:16 UTC,I've added this to the Train PTG planning etherpad.
1817316,2019-05-02 21:19:44 UTC,"Hi Maurice,"
1817316,2019-05-05 08:55:59 UTC,"Hi Goutham, we don't need to see the password. I'm okay with stopping exposing it for users as well as admins."
1817316,2020-12-03 16:01:17 UTC,Additional comments http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-12-03-15.00.log.html
1817320,2019-02-24 15:00:22 UTC,"You're correct that the current behavior doesn't conform, but is there any practical benefit to having #P""C:/test-dir/test-subdir/test"" in the -PATHNAME* variables?"
1817320,2019-02-24 20:45:03 UTC,"Thank you for the response and insight.
My reason for reporting this were purely from a conformance standpoint, and as such I've no concrete answer to your first question paraphrased as ""How would it be useful?""."
1817320,2019-04-17 18:23:01 UTC,I don't think we're nonconforming. The purpose of the -pathname* variables is precisely to tell you the _actual_ thing on which the LOAD or COMPILE is being performed after implementation-specific defaulting as expressed by the issue writeup http://clhs.lisp.se/Issues/iss218_w.htm and the -truename* variant is to inform you of the filesystem-specific name. (I think there's no complain about the latter?)
1817324,2019-02-22 14:03:09 UTC,"This might be rare since I don't see hits for this in logstash, but indexing is also currently behind by a few hours so the hit I have above isn't indexed."
1817324,2019-02-22 15:07:01 UTC,"Posting the full QEMU command-line, because the Gate logs can get cleaned up."
1817324,2019-02-25 08:18:23 UTC,"Some debugging notes from Friday, after talking to QEMU and libvirt
devs:"
1817325,2019-02-22 14:05:39 UTC,In order to access to this signature:
1817328,2019-03-27 15:02:49 UTC,This might be helpful https://bugs.launchpad.net/fuel/6.0.x/+bug/1405549
1817332,2019-05-24 19:08:40 UTC,"Looks good.  Merged to 3.2 and above.  Thanks, All."
1817332,2019-05-23 15:21:36 UTC,I've pushed a branch that signs off on the original patch and adds a follow-up to both implement Jane's suggestion and avoid overwriting any custom description of the setting that may have been added.
1817332,2019-02-22 15:33:22 UTC,"I like it -- thanks, Remington.  I think that it's important to include an example with an underscore too (e.g. Africa/Addis_Ababa or America/Los_Angeles).  Otherwise users might not know they need the underscore.  Various things break if you try entering one of these with a space instead of an underscore!"
1817332,2019-02-22 15:16:19 UTC,Here's a simple branch which updates the setting description with examples and a link to Wikipedia. Upgrade script is included.
1817334,2019-02-23 02:16:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817334,2019-02-23 05:17:39 UTC,"Thank you for your bug report. Indeed not an ""ideal upgrade experience"" but that's part of using a non stable serie of Ubuntu. The problem is that the dock migrated out of disco-proposed before the new gnome-shell version did, you can either downgrade to the previous version of ubuntu dock or get the new gnome-shell version out of proposed"
1817334,2019-02-23 05:37:47 UTC,"Can you clarify? Do you mean that the new version of gnome-shell has the dock functionality built in, or that it has a dependency on the dash-to-dock deb which means when the new version of gnome-shell is installed dash-to-dock will get installed automatically?"
1817334,2019-02-25 02:07:49 UTC,"Gnome Shell does indeed have its own dock built-in, which you will see whenever the Ubuntu Dock is missing or broken. But the built-in one may also hide by default (until you click Activities)."
1817334,2020-09-14 07:43:20 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1817336,2020-03-02 10:40:53 UTC,"Seed change approved and done, since this only is going to the supported seed but not getting a direct package/task dependency please help to let us later double check it actually shows up in component mismatches."
1817336,2020-03-02 09:06:19 UTC,Seeed change MP opened: https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/380071
1817336,2020-03-04 11:02:14 UTC,"Override component to main
runc 1.0.0~rc10-0ubuntu1 in focal: universe/misc -> main
golang-github-opencontainers-runc-dev 1.0.0~rc10-0ubuntu1 in focal amd64: universe/devel/extra/100% -> main
golang-github-opencontainers-runc-dev 1.0.0~rc10-0ubuntu1 in focal arm64: universe/devel/extra/100% -> main
golang-github-opencontainers-runc-dev 1.0.0~rc10-0ubuntu1 in focal armhf: universe/devel/extra/100% -> main
golang-github-opencontainers-runc-dev 1.0.0~rc10-0ubuntu1 in focal i386: universe/devel/extra/100% -> main
golang-github-opencontainers-runc-dev 1.0.0~rc10-0ubuntu1 in focal ppc64el: universe/devel/extra/100% -> main
golang-github-opencontainers-runc-dev 1.0.0~rc10-0ubuntu1 in focal s390x: universe/devel/extra/100% -> main
runc 1.0.0~rc10-0ubuntu1 in focal amd64: universe/devel/extra/100% -> main
runc 1.0.0~rc10-0ubuntu1 in focal arm64: universe/devel/extra/100% -> main
runc 1.0.0~rc10-0ubuntu1 in focal armhf: universe/devel/extra/100% -> main
runc 1.0.0~rc10-0ubuntu1 in focal ppc64el: universe/devel/extra/100% -> main
runc 1.0.0~rc10-0ubuntu1 in focal s390x: universe/devel/extra/100% -> main
12 publications overridden."
1817336,2020-01-22 14:22:34 UTC,"This is ready to go on, just FYI this is a few more days on hold as we want to move this at once together with containerd (bug 1819761)."
1817336,2020-01-17 15:47:19 UTC,"I reviewed runc 1.0.0~rc8+git20190923.3e425f80-0ubuntu1 as checked into focal.
This shouldn't be considered a full audit but rather a quick gauge of
maintainability."
1817336,2020-01-10 07:53:36 UTC,"Yes, if all vendorized deps that are packaged are not in main either there is no gain by de-vendorizing them right now for this case."
1817336,2020-01-09 21:13:00 UTC,"According to the report from comment #6, of the 17 vendorized packages runc uses, 16 exist as debs in universe, and 1 (go-criu) isn't packaged at all."
1817336,2020-03-02 07:17:40 UTC,"containerd (bug 1819761) is now ready for promotion as well.
We need to make a seed change to pull them in."
1817336,2019-09-23 06:50:34 UTC,"Last open CVE fixed as of 1.0.0~rc6+git20181203.96ec2177-0~ubuntu2 backports are in all releases.
So past CVEs are no more part of the discussion."
1817336,2019-03-18 23:11:10 UTC,ubuntu-server is now subscribed to bugs
1817336,2019-03-14 18:30:46 UTC,"In general vendored depends are ""okay"" in that they are a known issue that we generally need to deal with, even if it should be avoided whenever possible."
1817336,2019-02-26 12:46:05 UTC,"You mean this?
ubuntu@disco-mir:~/deb/runc-1.0.0~rc6+git20181203.96ec2177$ cat vendor.conf
# OCI runtime-spec. When updating this, make sure you use a version tag rather
# than a commit ID so it's much more obvious what version of the spec we are
# using.
github.com/opencontainers/runtime-spec 5684b8af48c1ac3b1451fa499724e30e3c20a294
# Core libcontainer functionality.
github.com/mrunalp/fileutils ed869b029674c0e9ce4c0dfa781405c2d9946d08
github.com/opencontainers/selinux v1.0.0-rc1
github.com/seccomp/libseccomp-golang 84e90a91acea0f4e51e62bc1a75de18b1fc0790f
github.com/sirupsen/logrus a3f95b5c423586578a4e099b11a46c2479628cac
github.com/syndtr/gocapability db04d3cc01c8b54962a58ec7e491717d06cfcc16
github.com/vishvananda/netlink 1e2e08e8a2dcdacaae3f14ac44c5cfa31361f270
# systemd integration.
github.com/coreos/go-systemd v14
github.com/coreos/pkg v3
github.com/godbus/dbus v3
github.com/golang/protobuf 18c9bb3261723cd5401db4d0c9fbc5c3b6c70fe8
# Command-line interface.
github.com/cyphar/filepath-securejoin v0.2.1
github.com/docker/go-units v0.2.0
github.com/urfave/cli d53eb991652b1d438abdd34ce4bfa3ef1539108e
golang.org/x/sys 7ddbeae9ae08c6a06a59597f0c9edbc5ff2444ce https://github.com/golang/sys"
1817336,2019-02-23 17:46:16 UTC,"A correction: the package in disco vendors its dependencies, in the way that docker.io and snapd do, and for much the same reason: to enable backports to LTS. So there are no build-depends in universe but there is bundled source code from other projects."
1817336,2019-12-18 20:16:41 UTC,I've been investigating the vendorized dependencies in runc and below you can find my notes so far:
1817343,2019-02-22 16:50:18 UTC,"We can:
1) Add a new feature by adding an extra var in this line:
https://github.com/openstack/openstack-ansible/blob/442d53a4d58d2a58d91813dee9ff96b51ef5063e/inventory/group_vars/haproxy/keepalived.yml#L60"
1817343,2019-02-25 11:24:46 UTC,That would be ideal.
1817344,2019-02-24 22:15:27 UTC,Thanks Iain! I'll keep an eye on this.
1817344,2019-02-24 21:45:54 UTC,Done. Please let me know here if this is still a problem.
1817344,2019-02-24 21:44:14 UTC,"Yeah OK, I'm pretty sure that change is bogus. I think it'll mean that if we hit the 'cache' we'll post back to the wrong status URL, since we don't check the environment matches."
1817344,2019-02-24 07:53:08 UTC,"It seems to me that the logs are internally consistent, i. e. the mentioned UPSTREAM_PULL_REQUEST in the log does match the test results. But they get sent to the wrong PR, i. e. to the wrong statuses API."
1817344,2019-02-24 17:10:15 UTC,Another example: https://github.com/systemd/systemd/pull/11802 refers to the correct amd64 log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/amd64/s/systemd-upstream/20190222_161608_7fe1f@/log.gz .
1817344,2019-02-24 20:17:51 UTC,"Thanks, I would guess that I broke this somehow in https://git.launchpad.net/autopkgtest-cloud/commit/?id=58adff467c108506f979e229aa8e9e955a7d0d0a - which was a commit I made because systemd PRs were taking a long time after their jobs finished (several hours) to report any results due to that script having terrible runtime."
1817345,2019-08-02 17:46:23 UTC,Antonio's patches are in git and will be in the upcoming 4.1.0 release.
1817345,2019-08-16 04:59:52 UTC,"Patch included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=4ace32e22713ffd79deb22"
1817345,2019-05-03 17:26:30 UTC,"Antonio has submitted a patchset here:
https://<email address hidden>/"
1817345,2019-03-10 03:46:31 UTC,"Oh~
Okay!"
1817345,2019-03-09 20:54:46 UTC,"Deepika: the tricky part is the makefiles, not the configure script..."
1817345,2019-02-25 07:36:34 UTC,I am OK with just checking and complaining.
1817345,2019-02-24 19:54:23 UTC,"On Sun, 24 Feb 2019 at 19:46, Michael Tokarev
<email address hidden> wrote:

> I think it is better to just disallow building in a path containing
> spaces, -- there are so many packages and other tools that fails in this
> config, might require lots of work to fix this AND to ensure all future
> changes are still working, and there's an easy workaround
"
1817345,2019-02-24 19:38:56 UTC,"I think it is better to just disallow building in a path containing spaces, -- there are so many packages and other tools that fails in this config, might require lots of work to fix this AND to ensure all future changes are still working, and there's an easy workaround"
1817345,2019-03-09 19:16:31 UTC,"If calling from any Unix shell, and the parameter has spaces, then we need to quote it.we can also use single quotes, these are more powerful. They stop the shell from interpreting anything ($, !, \, *, "", etc, except ')."
1817347,2019-05-23 11:59:54 UTC,The _validate_partitioning(device) method in ironic_python_agent/extensions/standby.py throws warning that the output of parted comment does not match the format while listing the partition but the partition format looks to be correct.
1817350,2019-02-22 17:20:26 UTC,I should note that I've also tested this on 16.04.6 and am getting the same unexpected behaviour.
1817350,2019-05-10 15:08:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817350,2019-05-17 14:43:35 UTC,Another detail that might be worth mentioning...
1817350,2020-01-16 16:24:05 UTC,"I can confirm the problem is present in Debian GNU/Linux 9.11 (stretch) and Ubuntu 18.04.3 LTS. I noted the issue after run by the second time an Ansible playbook with the apt module. As a workaround, I set `force_apt_get: yes` in the apt module."
1817351,2019-06-10 05:53:30 UTC,"Update the list as follows.
When using collectd-5.8.1-4.el7.x86_64 (the latest version), ISO deployment fails.
After restoring it to collectd-5.8.0-4.el7.x86_64, ISO deployment is successful,
and the reasons for deployment failure need to be further investigated."
1817351,2019-09-17 03:49:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/682529"
1817351,2019-09-17 13:41:29 UTC,"Reviewed:  https://review.opendev.org/682529
Committed: https://git.openstack.org/cgit/starlingx/monitoring/commit/?id=2dfb03de5b16581ddf2d20145fffc636d4ad6161
Submitter: Zuul
Branch:    master"
1817351,2019-09-16 17:42:07 UTC,"Reviewed:  https://review.opendev.org/653153
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=90da89899c9ac469db93804a8545dc114e1e8e7a
Submitter: Zuul
Branch:    master"
1817351,2019-09-16 17:40:09 UTC,"Reviewed:  https://review.opendev.org/653152
Committed: https://git.openstack.org/cgit/starlingx/tools/commit/?id=20f351a7994d470c07e219eae537fd55a519325b
Submitter: Zuul
Branch:    master"
1817351,2019-08-13 07:24:08 UTC,This is a feature instead of a bug. Mark it as stx.3.0 feature.
1817351,2019-05-07 14:03:48 UTC,https://review.opendev.org/#/c/653152/ was submitted by Erich. It's interesting that the LP was not updated.
1817351,2019-09-17 03:50:42 UTC,"Change abandoned by Erich Cordoba (<email address hidden>) on branch: master
Review: https://review.opendev.org/653513
Reason: The monitoring componentes were moved into the new monitoring repository. I'm abandon this review in favor of this one:"
1817351,2019-04-16 07:09:02 UTC,Please have CW working on this issue after QAT upgrade.
1817351,2019-03-27 02:32:36 UTC,"Here is the new version package list:
lighttpd-1.4.53-1.el7.src.rpm
julietaula-montserrat-fonts-7.200-5.el7.noarch.rpm
perl-generators-1.08-7.el7.noarch.rpm
libcmocka-1.1.3-1.el7.x86_64.rpm
libcmocka-devel-1.1.3-1.el7.x86_64.rpm
python2-qpid-proton-0.26.0-1.el7.x86_64.rpm
qpid-proton-c-0.26.0-1.el7.x86_64.rpm
collectd-5.8.1-3.el7.x86_64.rpm
cppcheck-1.87-1.el7.x86_64.rpm"
1817351,2019-03-27 00:40:22 UTC,"Hi Erich, will you work on this task? I could take this task if you have not started yet.
Thanks."
1817351,2019-03-20 14:56:15 UTC,"Erich, are you still working on this LP?"
1817351,2019-02-22 21:12:00 UTC,For people without access to CENGN this will cause an incomplete mirror and a build failure.
1817351,2019-02-22 20:04:57 UTC,"Not sure that this should be marked as release gating. Actually, not sure why this is considered a bug at all. The system is working fine with the current versions. This is a would-be-nice."
1817351,2019-04-16 21:41:12 UTC,This is an updated list:
1817357,2019-02-25 17:08:06 UTC,+1
1817357,2019-04-02 19:14:07 UTC,"Any four-digit number would be a ridiculously insecure password, and the last four digits of a phone number is even worse.  If a patron specifically tells me, ""set my password to 1234"", that's one thing; but automatically doing this sort of thing without an explicit say-so from the patron is borderline criminal in states with privacy laws.  The patron thinks they've signed up to check items out from the library, and in fact they've signed up to donate a list of all the books they've checked out to anyone who can look up or guess the last four digits of their phone number."
1817357,2019-10-04 17:37:26 UTC,"In my experience, libraries choose the last four of phone option at migration because it is easy for the patron to remember when they first login to their account. I agree that the last four of the phone is not a secure choice, but the patron always has the option to use the phone number for their first OPAC login, and change it after that. In fact, that should always be a standard follow through, even if a random password is generated at login. That password is not secure either because the library staff member who registered the patron knows what it is."
1817358,2019-11-16 18:28:19 UTC,Confirming the same bug on 16.04 via PXE boot.
1817358,2019-09-21 15:52:49 UTC,Confirm on latest mini iso 16.04.
1817358,2019-09-09 14:39:03 UTC,I can confirm that installation fails for (upcoming) Ubuntu 19.10 Eoan with Mini ISO that was downloaded from:
1817358,2019-04-05 22:57:51 UTC,For anyone using di-netboot-assistant to generate the tftp dir:
1817358,2019-04-30 14:30:38 UTC,"Hi,"
1817358,2019-04-11 10:37:01 UTC,"i m still having this issue with Ubuntu 16.04, using foreman as a pxe server.
failed for both xenial , and xenial-updates"
1817358,2019-11-27 14:29:58 UTC,Samething in my foreman 1.23 environment.
1817358,2019-06-18 05:22:39 UTC,I am also having this issue with Ubuntu 16.04 using Foreman as a PXE boot server. Works fine with Ubuntu 18.04.2 but wanted to have Ubuntu 16.04 as an option.
1817358,2019-12-04 19:07:48 UTC,Confirmed with Ubuntu 16 mini.iso downloaded right now (wanted to use it as a rescue disk). Both boot from a CD-RW and from a USB stick give the same problem. Also tried several mirrors in case it was a faulty mirror.
1817358,2020-03-15 08:25:09 UTC,I am experiencing this with Focal's netboot kernel/initrd and mini.iso from march 10th 2020
1817358,2020-01-09 15:13:03 UTC,Confirming this is still a problem for 16 LTS. Seeing in our foreman environment. foreman 1.22.1. Anyone know if there is a workaround? Is this likely to happen to ubuntu 18 LTS after its gets a bit older?
1817358,2020-02-22 22:15:33 UTC,"Hello,"
1817358,2020-03-01 15:23:10 UTC,"Hi,
i've stumbled upon this right now with foreman and bionic + xenial via tftp/pxe"
1817358,2020-03-15 11:10:05 UTC,@nik-mihailov are you by any chance testing this in kvm/qemu? What kind of architecture are u using?
1817358,2020-03-15 11:22:28 UTC,running into the same issue as soon as a disk is attached to the system (no matter if qemu or bare-metal).
1817358,2020-03-15 17:11:23 UTC,@strowi - I am installing on bare metal Ryzen ThreadRipper 1920X. I was already running 20.04 on the same machine for quite some time but yesterday I hit a problem with updates whereby libcrypt1 has some unsatisfyable dependencies so I decied to install from scratch. Oops! I then tried it in VirtualBox but the problem is the same so I think it's not architecture dependent. I think some packages in the repository are screwed up.
1817358,2020-11-19 20:12:34 UTC,Hello. I ran into this exact problem today with a 16.04 kickstart server[1] which has been working fine for over a year. I tried solution above posted by @elektromane however the problem persists. Is there something I'm missing?
1817358,2019-04-02 07:46:37 UTC,To #19. I think that the solution proposed in #10 implies to modify the netinstaller ISO image (February 21th 2019) by updating the linux and initrd.gz files.
1817358,2019-12-04 19:40:20 UTC,"Just tested with a ISO downloaded on Nov 7th, 2018, inside VirtualBox, booted via PXE: same issue. As far as I remember, in the past I could successfully use this image to install systems. Is this due to a change on one of the packages downloaded by the mini installer?"
1817358,2019-03-28 13:59:37 UTC,"We are also affected. Works on ubuntu18, not on ubuntu16."
1817358,2019-03-28 21:36:16 UTC,I use Foreman to provision and deploy Ubuntu 16.04 VMs and I am facing the exact same bug.
1817358,2019-03-27 14:27:58 UTC,"Some time ago I had also posted here[1] that I was affected, but then updating `linux` and `initrd.gz` had solved the issue."
1817358,2019-02-22 18:45:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817358,2019-02-22 18:48:15 UTC,"I am seeing the same thing, new in the last couple of days.
This has made it so that we can't build xenial machines via netboot+preseed anymore."
1817358,2019-02-22 20:03:51 UTC,"Marc also reported on IRC (#ubuntu, 2018-02-22 ~17:20 UTC) that this report refers to the mini.iso with MD5SUM ed2bbe59e5dac40b92e0ddeb6b206ef8
While Marc uses Xen, Jesse uses a different HV technology."
1817358,2019-02-24 00:00:00 UTC,We are having this exact problem with a regular PXE boot as well (not using Xen).
1817358,2019-02-25 19:21:28 UTC,Same problem for us too on 16.04 through PXE. We get the error right after it starts gathering the installer packages. 14.04 installer is also getting an error. 18.04 works fine.
1817358,2019-02-26 15:48:06 UTC,"I'm getting the same problem on a machine as well. Since it failed on 'Detect Disks,' I tried swapping my hard drive, to no avail."
1817358,2019-02-26 17:11:53 UTC,Updating to the latest netboot binaries solved the problem for me
1817358,2019-02-27 10:11:30 UTC,"@spidy
which one? please can you provide link"
1817358,2019-02-27 15:52:54 UTC,fixed for me with initrd.gz & linux file
1817358,2019-02-27 16:50:40 UTC,The proposed fix from buntix seems to work for us too on Ubuntu 16
1817358,2019-02-27 14:43:17 UTC,"Tried using the methods to correct the issue in the duplicate bug page. Tried using the initrd.gz & linux files from both xenial-updates and xenial-proposed and I still get the same ""Loading libc6-udeb failed for unknown reasons"" error."
1817358,2019-03-08 13:05:56 UTC,"Hi,"
1817358,2019-03-11 20:25:20 UTC,The proposed fix in #10 not work to me
1817358,2019-03-21 09:13:31 UTC,I still get this error too
1817358,2019-03-21 10:07:11 UTC,In attachment there is screenshot of error
1817358,2019-03-21 23:56:10 UTC,"The proposed fix in #10 does not work for me either.
See the attached error."
1817358,2019-03-22 11:06:15 UTC,"I get the same error as @hconan above, is it possible that the installer and the packages are misaligned? When is the new installer going to be released as a part of the regular updates?"
1817358,2019-03-22 13:51:44 UTC,Apologies for the noobish question could anyone be kind enough to explain how to apply the fix?
1817358,2019-03-22 18:46:11 UTC,Exact same issue on my end
1817358,2019-03-27 14:28:47 UTC,"Oops, here's the aforementioned link:"
1817358,2019-03-01 11:21:25 UTC,"Hi,"
1817364,2019-02-22 20:36:29 UTC,working on https://review.openstack.org/638763
1817364,2019-02-22 21:05:24 UTC,It would not be nice because it adds a whole bunch of extra time and stuff to this job that aren't really necessary. This feels like feature creep
1817364,2021-02-18 16:46:38 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1817368,2019-06-03 14:21:32 UTC,"On Fri, May 31, 2019 at 10:56 AM Robert Schweikert <
<email address hidden>> wrote:"
1817368,2019-05-31 15:41:57 UTC,"Still need help with the tests, Ryan, Dan?"
1817368,2019-07-17 20:23:44 UTC,"This bug is fixed with commit b3a87fc0 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=b3a87fc0"
1817368,2019-03-21 14:29:45 UTC,I'm still a little confused around the presence of 75-persistent-net-generator.rules AND having systemd creating persistent nic names.  That's going to cause problems unless it's always booted with net.ifnames=0.
1817368,2019-12-19 23:01:25 UTC,"This bug is believed to be fixed in cloud-init in version 19.2-1. If this is still a problem for you, please make a comment and set the state back to New"
1817368,2019-04-19 16:34:22 UTC,"I have updated the code. The current implementation works in the customer case. Also should not call settle in general, only when we get into the situation where things are ""racy""."
1817368,2019-02-26 15:44:14 UTC,"Well, the way I see, based on investigation and input from others at SUSE we have 2 options. We can set the default file name for the netrules_path to something safe (80-pesistent-netrules-cloud-init.rules) for example. That would avoid the issue, the cloud-init generated rules would be last and thus the user supplied network setup would be applied. If we choose this path then IMHO netrules_path should no longer be configurable."
1817368,2019-02-26 14:22:47 UTC,"I think we're in conflict with 75-persistent-net-generator.rules; as both cloud-init and that rule are attempting to map a MAC and interface name.  This is going to be trouble, as you've seen."
1817375,2019-02-22 22:45:45 UTC,"Actually, for this particular issue, we just need to add
global pexpect
after the import line."
1817380,2019-02-23 11:29:20 UTC,What is the motivation for such a change?  Is it strictly because you want to be able to nice these jobs?
1817380,2019-02-24 05:21:40 UTC,"Nope (although that is nice - I personally care more about the other restrictions you can do). I posted to devel-discuss about moving from anacron/cron to timers
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2019-February/018242.html"
1817387,2019-02-25 20:14:21 UTC,"Something I've noted, we've not run into this in the past as nova-compute has been in our personal ""order of upgrade"" to be upgraded before swift-storage."
1817387,2019-03-05 11:56:00 UTC,ceph-* is definitely selective in when an upgrade is triggered.
1817387,2019-03-05 11:58:04 UTC,"It might be possible to switch the swift packages to perform a selective upgrade, rather than a dist-upgrade but that will need validating; the swift project consumes less shared openstack libraries so being in a transitional state may be OK."
1817389,2019-02-23 08:58:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817389,2020-02-09 18:57:37 UTC,"I can confirm that issue on the latest development version of Ubuntu 20, on HiDPI 15"" display (3840x2160)
flatpak version looks less or more correct (still not very usable) and icon size setting works.
repository version has tiny icons and icon size settings does not work."
1817389,2020-04-26 21:25:40 UTC,"I have the same issue on a freshly installed Ubuntu 20.04, using the apt package of gimp.
The laptop is a X270 12"" with 1920x1080.
I noticed that the problem only occurs at fractional scaling (125%, 150%), at 100% scaling the icon sizes behave normal."
1817389,2020-06-15 20:47:45 UTC,"I have the same issue on Ubuntu 20.04 on a Macbook 13"" Retina and a PC with 4K 27"" Monitor, both scaling at 200%.
Im using an AppImage of Gimp 2.10.*, actual 2.10.20."
1817389,2020-09-09 21:49:28 UTC,I was able to work around the issue by changing the theme in Gnome Tweaks from Yaru to Adwaita or sticking with Yaru and removing the gtk-icon-sizes defintion (note it spans multiple lines) in the gtk2 rc at /usr/share/themes/Yaru/gtk-2.0/gtkrc
1817389,2020-11-24 12:25:28 UTC,"This is still happening on GIMP 2.10.18 on Ubuntu 20.04, and renders GIMP pretty unusable on a 4K display"
1817389,2020-12-10 08:01:39 UTC,"I just wanted to add a temporary workaround for those who stumbled upon this bug report, building off Kevin Barry(barryk)'s post and Archwiki's Gimp 2.10 section from the HiDPI article (https://wiki.archlinux.org/index.php/HiDPI#Gimp_2.10)"
1817389,2019-02-23 04:12:30 UTC,"I believe these settings are stored at '~/.config/GIMP/2.10/gimprc', although bug occurs before setting is saved when ""OK"" is pressed in Preferences."
1817390,2019-05-14 14:06:12 UTC,"@afreiberger is this problem still occurring in the latest charm release? If so, would you please attach bundles and crashdumps?"
1817390,2019-05-30 14:13:28 UTC,"As an update, I just performed a similar upgrade using 19.04 latest charms and did not witness this issue."
1817390,2019-10-28 13:17:28 UTC,Judging by #2 this is no longer an issue.
1817394,2020-03-07 10:15:47 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1817397,2020-10-22 19:14:22 UTC,closing since the package is removed from Ubuntu
1817409,2019-02-27 23:48:09 UTC,"There is nothing in the log file, so there is no actual error.
It would help to know what you intend to do. If the path following on from the reversal is very short, it could be that the train does reverse but then immediately terminates as it assumes it has reached the end of the path. If no information is set in the #dispose field, so there is no continuation as other train, the train would then indeed be 'dead' as it has no further actions.
What you could try is not to reverse the train but instead split it into two separate workings, using the $forms command in the #dispose field to continue from the first to the second part of the service.
What might help to understand what is happening is a screendump of the path (using the OR trackviewer), and a screendump after the incident showing the dispatcher hud."
1817410,2019-02-24 12:54:06 UTC,"I had the same problem. The usb modem was detected as CD-ROM. I had to install driver manually and now the modem works fine. See
https://askubuntu.com/questions/790490/ubuntu-16-04-usb-modem-detected-as-cd-rom-unable-to-connect"
1817410,2019-02-24 12:54:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817410,2019-02-25 04:41:51 UTC,Hi!
1817410,2019-02-25 04:44:15 UTC,Updates which apparently contain fix:
1817410,2019-02-25 12:04:53 UTC,Correction to previous post:
1817410,2019-03-01 19:14:50 UTC,Hello
1817414,2019-02-23 18:14:57 UTC,"Yes I tested it. Just load Magic Mountain with r8999 and Wood Gnome. It also takes ages writing the data. Since GunChleoc removed the postload in that revision, it writes only 2 saves."
1817414,2019-09-15 17:04:44 UTC,Migrated to https://github.com/widelands/widelands/issues/1086
1817414,2019-02-25 09:36:02 UTC,Changed the description and the report. Set it to new again to be not forgotten for b21 or later
1817414,2019-02-23 18:02:19 UTC,not sure if woodgnome and artifacts are affected in the same manner did you test it?
1817414,2019-02-23 20:33:50 UTC,"tested it as well.
woodgnome is affected in the same way.
Artifacts is not affected as it contains far less fields to save."
1817414,2019-02-23 16:36:15 UTC, Writing Scripting Data ... took 89594ms
1817414,2019-02-23 17:04:28 UTC,"BTW. That doesn't only affect territorial, but also woodgnome and artifacts."
1817414,2019-02-23 15:56:20 UTC,These lines here:
1817414,2019-02-23 15:31:22 UTC,here is the log for loading magicmountain in territorial time
1817414,2019-02-23 16:22:38 UTC,"and another one
as we have 3 saves at the start"
1817414,2019-02-23 15:24:13 UTC,It just takes very long but works
1817416,2019-02-23 15:17:42 UTC,https://forums.linuxmint.com/viewtopic.php?f=51&t=288672
1817416,2019-02-24 11:50:13 UTC,Thx for the fast reply!
1817418,2020-06-26 07:08:29 UTC,Happens to me whenever I have an update that involves nvidia drivers. The only way to shutdown or reboot is via the CLI.
1817418,2020-04-15 16:27:08 UTC,I experienced the same issue after going to launcher > leave > reboot after rebooting from CLI I cannot recreate
1817418,2020-04-15 16:28:44 UTC,^^^^^^^ Kubuntu 20.04 (opps)
1817418,2020-02-03 15:54:15 UTC,I have the same issue. But reboot is fix it.
1817418,2019-07-14 22:40:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817418,2019-02-23 15:08:57 UTC,APT history of packages updated before the crash.
1817418,2020-03-10 23:49:29 UTC,I think this problem started happening for me after adding the repository ppa:graphics-drivers/ppa and installing the packages nvidia-driver-440 libnvidia-gl-440 libnvidia-gl-440:i386 libvulkan1 libvulkan1:i386. Here's the generated crash information:
1817418,2020-03-10 23:54:27 UTC,Correction: I think it was when I updated those packages or their dependencies (not installed) and didn't reboot. A reboot fixed the issue.
1817422,2019-02-24 02:38:36 UTC,"Yeah, I've hit this too. As with everything else, the ""reusing existing partitions"" work is the answer, because that will include probing for existing LVM/mdraid/etc devices."
1817422,2020-03-25 12:43:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817424,2019-02-28 18:01:30 UTC,"Correction, service systemd-resolved restart does not solve the problem. Only systemd-resolve --flush-caches fixed the problem temporarily."
1817424,2019-08-02 23:09:57 UTC,I noticed the following in my syslog recently:
1817424,2019-08-03 18:09:21 UTC,Looking at this issue again I noticed some others having issues with /etc/resolv.conf so I check and indeed the symlink was incorrect:
1817426,2019-02-25 09:38:18 UTC,"Thanks, I reported that issue upstream now https://gitlab.gnome.org/GNOME/gnome-control-center/issues/389"
1817427,2019-02-25 09:41:47 UTC,"Thank, that was reported upstream now on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/390"
1817428,2019-02-25 09:43:06 UTC,"Thank you for your bug report, indeed that would be nice. Reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/391"
1817428,2019-09-12 16:21:14 UTC,With gnome-control-center 3.34.0.1 I see there's a search button now.
1817432,2019-02-23 20:32:03 UTC,"> What can I do? Please could anybody help me?
"
1817433,2019-08-01 19:42:07 UTC,"Hi Maarts,"
1817433,2019-08-02 19:47:54 UTC,"Hi Phill,"
1817434,2019-03-16 21:38:49 UTC,Can confirm on trunk with webengine
1817437,2019-07-24 19:40:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817437,2019-02-25 17:11:01 UTC,"When backporting ""meson"" from Disco, the build process works - but the Python tests still give an error (it works manually)."
1817437,2019-03-02 22:27:24 UTC,It can be built on Debian Stretch 9 (stable) without a problem using these packages from official backports:
1817444,2020-08-17 18:44:35 UTC,"i'm one of the active fossil SCM developers. If you can reproduce this on the latest (2.12), either by downloading a pre-build binary or building it from sources, it would be helpful. Much has happened in the nearly 2 years since 2.7 was released."
1817451,2019-02-26 09:53:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817451,2019-02-26 09:53:56 UTC,Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909577
1817455,2019-07-12 11:30:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670496"
1817455,2019-09-19 10:10:53 UTC,This issue was fixed in the openstack/neutron-fwaas 15.0.0.0b1 development milestone.
1817455,2019-07-23 21:41:21 UTC,"Reviewed:  https://review.opendev.org/670496
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=90a2707ccffd2175d76e0e2ac5a4cd87e5faa7ef
Submitter: Zuul
Branch:    master"
1817456,2019-05-14 09:23:08 UTC,This seems to have been resolved in https://review.opendev.org/#/c/648703/
1817462,2019-05-11 16:08:36 UTC,"question:
is it a second card from the same person or from another one ?
I question this because thinking (and just thinking in this case ticket) of introduce people for that and other things"
1817462,2019-05-20 07:43:18 UTC,in waiting maybe 1817274
1817462,2019-05-14 19:57:47 UTC,"I thought a second card on the same account use by another person. But
could also be used by the same person. Useful to filter payment from a card
to the other.
Best regards.
Alain"
1817465,2019-02-24 17:08:44 UTC,"First of all I'd suggest you to uncheck the option ""Automatically tune settings to keep performance level"". If this doesn't solve your problem, there could also be a trainset with some wrong parameters. I'm not sure, but I believe I already read about some trainset for zigzag route having problems, that were solved uploading a new release of it. Maybe you could try to re-download the trainsets."
1817471,2019-02-24 22:21:20 UTC,"Yes, I agree. Only changing the colour is also not always accessible for color blind people.
The purple color for red is not unambiguous.
Can you crosscheck the icons used in the other skins?
All these are only icons in the res/skins folder. I would be happy If you have an improved proposal."
1817471,2019-02-24 23:55:59 UTC,Thanks for your reply.  I am going to initially focus on the Deere icons.
1817471,2019-02-25 00:09:33 UTC,"I think we also need to change the shape of the icon, or add an overlay, in a way that it is unambiguous something broken."
1817471,2019-02-25 00:29:01 UTC,I am playing with a 'on' icon now in Libre Office Draw.
1817471,2019-02-25 00:34:00 UTC,Everything except the green outline and the solid white centre is transparent.
1817471,2019-02-25 00:52:06 UTC,I had a few thoughts on icons.
1817471,2019-02-25 13:13:44 UTC,"Thanks for the new skin input!
The satelite dish icon is quite complex if borders are added, maybe we can also somehow build upon the antenna icon from Tango.
I think it would be best if you just open a PR like ""Deere broadcast icons"" with graphic suggestions, to make it easier for others to follow."
1817473,2019-02-24 17:46:57 UTC,"Okay, I seem to have found what triggers it. The problem is no more after disabling gnome's night mode, 'killall redshift' then running it again"
1817473,2019-02-24 17:48:14 UTC,"running it again after 'redshift -x', since otherwise it modifies the previously modified colors... But this is another story (another bug ?)"
1817479,2019-07-19 08:35:56 UTC,After upgrade to Buster it seems the problem disappeared :) so closing.
1817479,2019-07-17 12:37:15 UTC,What is the output of simply running Kodi from the command line? If it is  bug https://bugs.launchpad.net/raspbian/+bug/1834970 please close this one. Please report also which version of Raspbian you are using.
1817480,2020-08-06 03:02:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817480,2020-08-06 03:07:30 UTC,Still a problem in 42.2.  No color-theme-* (thus no color-theme-modern that was proposed as a replacement).
1817480,2020-08-09 21:15:10 UTC,Not sure if that should be a bug anymore. In Ubuntu 19 and 20 I have started to use melpa which allows to install custom and safe color themes.
1817480,2019-02-24 20:32:54 UTC,Thanks for reporting.
1817483,2019-04-23 23:55:44 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1817483,2019-06-23 04:19:11 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1817484,2019-02-27 00:00:38 UTC,An update after using this patch suggested by Alberto: http://paste.ubuntu.com/p/fDbrrsBmdP/
1817484,2019-02-27 05:46:48 UTC,"It is possible to set keepalives specifically on the PostgreSQL connection, per https://www.postgresql.org/docs/10/libpq-connect.html#LIBPQ-PARAMKEYWORDS (which psycopg2 accepts as keyword parameters IIRC). It should be functionally the same as setting system-wide TCP settings, but might be easier to rollout as a fix (just a software update, no need to change system settings)."
1817484,2019-02-27 17:36:33 UTC,Tested in identical scenario as #19 (maas 2.5.1 with patches)
1817484,2019-02-27 20:00:56 UTC,Logs for #19 from 3 nodes (shut all of them down at the end).
1817484,2019-02-28 09:01:27 UTC,"Dmitrii,"
1817484,2019-02-28 13:40:26 UTC,"The patch, even with the keepalive settings, was not working for me on-site at customer so I added crm configuration to restart maas-regiond whenever pgsql gets promoted to master."
1817484,2019-03-01 08:31:37 UTC,"Dmitrii,"
1817484,2019-02-28 23:30:19 UTC,"Alberto,"
1817484,2019-03-01 10:13:34 UTC,Another update: I managed to reproduce the issue with missing regiond sockets.
1817484,2019-03-05 12:53:34 UTC,Have anybody looked at the logs mentioned in https://bugs.launchpad.net/maas/+bug/1817484/comments/29 with regards to API sockets disappearing?
1817484,2019-03-05 14:12:41 UTC,@dmitriis
1817484,2019-03-05 15:35:11 UTC,"In response to #26, from Blake Rouse: When I say it was not working, at first the dnsresource setting was getting 500 server errors (as expected) but when it succeeded, the new IP was set in the postgres DB but the zone files on each node still reflected the old IP."
1817484,2019-03-05 16:49:05 UTC,"Blake,"
1817484,2019-02-28 17:08:15 UTC,Can you describe what you mean by not working? Code is erroring? DNS still missing? What type of delay did you wait for?
1817484,2019-02-26 11:12:52 UTC,"Also to #15, #16 and #17:"
1817484,2019-02-27 23:17:37 UTC,Reverted to 2.5.0 and tried the patch with that:
1817484,2019-02-25 19:08:42 UTC,"Alberto,"
1817484,2019-02-26 06:48:39 UTC,I looked at the situation at a different angle:
1817484,2019-02-25 08:07:59 UTC,"Hi there,"
1817484,2019-02-25 10:05:23 UTC,"Hi Andres,"
1817484,2019-02-25 10:54:07 UTC,"Andres,"
1817484,2019-02-25 11:29:01 UTC,"Hi Dimitrii,"
1817484,2019-02-25 12:16:09 UTC,"Andres,"
1817484,2019-02-25 12:26:48 UTC,"Andres,"
1817484,2019-02-25 19:10:11 UTC,For #15:
1817484,2019-02-25 13:06:50 UTC,"Actually, the answer to the last question may be here in comment #5:"
1817484,2019-02-25 13:47:39 UTC,"Andres,"
1817484,2019-02-25 13:56:27 UTC,Hi guys.
1817484,2019-02-25 14:19:00 UTC,"How can we determine and observe externally that MAAS is fully functional
after a database failover?"
1817484,2019-02-25 14:34:20 UTC,"Andres,"
1817484,2019-02-25 16:18:39 UTC,"Dmitrii, could you please try this http://paste.ubuntu.com/p/QXQWdBsdwY/ and see if it solves your issue?
This will return a 500 if the region is not fully connected to the DB"
1817484,2019-02-25 16:34:14 UTC,"Apologies, the previous paste had an error in it, please try http://paste.ubuntu.com/p/SXhPsPqz8w/"
1817484,2019-02-25 13:02:03 UTC,"Hi guys,"
1817487,2020-10-14 01:58:15 UTC,"A transparent ""ghost"" control would be really handy"
1817496,2020-06-15 04:17:43 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1817496,2020-04-16 02:16:59 UTC,You should be able to manually do
1817496,2020-04-16 02:17:38 UTC,Please show the results of 'mount | grep sda5' and the contents of /etc/fstab.
1817501,2020-11-20 04:17:28 UTC,[Expired for mate-terminal (Ubuntu) because there has been no activity for 60 days.]
1817502,2019-12-28 22:37:42 UTC,this is really something in glib/gtk for me.
1817512,2019-06-03 20:47:26 UTC,It looks like the db isn't up or is locked up according to the logs.  Would need additional logs to troubleshoot.
1817512,2019-08-03 04:17:31 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1817513,2019-02-25 07:30:06 UTC,This change was made by a bot.
1817513,2019-02-26 10:39:52 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc8 kernel[0]."
1817513,2019-02-26 14:41:00 UTC,"Works with all mainline kernels that I tested: 5.0-rc8, 4.20, and 4.19."
1817513,2019-02-27 04:43:39 UTC,Disco will use v5.0.
1817513,2019-02-27 11:33:10 UTC,The bug doesn't exist with that PPA's kernel.
1817515,2019-04-25 12:56:12 UTC,"Since ubuntu disco dingo (19.04) is released, and disco dingo is delievered with python 3.7, my-weather-indicator does not work any longer. Looking in the crash file definitively proves that the problem is the one described above."
1817515,2019-04-29 17:23:11 UTC,my-weather-indicator now seems to work for systems that was upgraded to disco dingo and where the my-weather-indicator earlier worked. but it does not seem to work on systems that were installed without webkit-3.0. and that is not installed on disco dingo from start. It says Depends on: gir1.2-webkit-3.0. Disco dingo is delievered with gir1.2-webkit2-4.0
1817518,2019-02-28 12:48:42 UTC,Mark Xenial as WONTFIX per patch review comment.
1817518,2019-03-15 23:37:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1817518,2019-03-15 23:31:35 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1817518,2019-05-16 09:48:31 UTC,This bug was fixed in the package linux-firmware - 1.173.6
1817518,2019-05-16 09:27:26 UTC,This bug was fixed in the package linux-firmware - 1.175.4
1817518,2019-05-16 09:10:50 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1817518,2019-05-09 06:39:00 UTC,"verified:
* bionic-proposed 1.173.6
* cosmic-proposed 1.175.4
* disco-proposed 1.178.1"
1817518,2019-05-08 15:48:49 UTC,"Hello You-Sheng, or anyone else affected,"
1817518,2019-05-16 09:10:45 UTC,This bug was fixed in the package linux-firmware - 1.178.1
1817518,2019-05-08 15:47:40 UTC,"Hello You-Sheng, or anyone else affected,"
1817518,2019-05-08 14:25:48 UTC,This bug was fixed in the package linux-firmware - 1.179
1817518,2019-05-07 05:15:17 UTC,"There are couple of OEM images requires this fix and expected to be released next week. Can we expect the linux-firmware including this fix updated before May 15th, if possible?"
1817518,2019-04-10 06:56:27 UTC,Firmware landed in upstream https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=1b3456c3360be6c6333ba0350316500afa9b2524
1817518,2019-04-02 10:29:42 UTC,This bug was fixed in the package linux - 4.18.0-17.18
1817518,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1817518,2019-05-08 15:48:12 UTC,"Hello You-Sheng, or anyone else affected,"
1817528,2019-07-16 13:41:24 UTC,"in WW30/31, we need to try this recipe described above."
1817528,2019-12-30 19:52:08 UTC,"As per agreement with the community, marking unresolved medium priority bugs (>= 100 days AND not recently reproduced) from stx.3.0 to Low priority / no target release"
1817528,2019-08-23 17:46:00 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1817528,2019-08-08 16:13:45 UTC,"@zhangyifan, you might have several ways to get the guest image:
1. for ubuntu cloud image, you can download one: https://cloud-images.ubuntu.com/releases/
2. get the image from @Jan or @Bill.
3. use cirros http://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img"
1817528,2019-07-26 08:09:03 UTC,Can you provide the ubuntu image for me?
1817528,2019-07-16 13:41:56 UTC,@Bill to ask help from Hao (FiberHome).
1817528,2019-06-26 05:29:27 UTC,"Possibly the Cirros image as the image that you use need to contain the agent toolchain os-collect-config, os-refresh-config and os-apply-config."
1817528,2019-11-13 02:10:59 UTC,"@wanghao, could you have someone in your team working on this LP?"
1817528,2019-05-28 13:40:15 UTC,This defect needs to be retested since we rebased to upstream Stein and this issue may no longer exist.
1817528,2019-02-25 16:56:44 UTC,"From Al Bailey:
---------------
The config url is set to: (public endpoint in my lab)
 config_url http://128.224.151.57:8000/v1/waitcondition"
1817528,2019-02-25 18:13:21 UTC,"As already confirmed by the reporter, the suggested code change addresses the issue. However, this is just a workaround which is not suitable for submission in the StarlingX 2018.10 release as it would result in IPv6 and https issues with heat."
1817528,2019-02-26 09:32:28 UTC,I do not have a personal opinion in this. You know better which other parts of the code which will not work. However it would be nice with some kind of warning.
1817528,2019-06-25 18:59:49 UTC,"In my retest env (heat running in containerized openstack)
  m1.tiny as the flavor.
  cirros qcow image rather than ubuntu
  Used the tenant networking setup from the containers wiki to setup a network and selected: public-net0"
1817528,2019-03-05 14:53:46 UTC,We have re-based to Stein.  Need to retest this bug and make sure it has been addressed.
1817528,2019-04-05 19:53:46 UTC,Lowered priority to medium as a workaround exists.
1817528,2019-02-27 18:35:31 UTC,Agreed to live with the workaround for stx.2018.10. We will retest in stx.2019.05 after moving to Stein to ensure this is still working. Then we'll close the bug at that time.
1817529,2020-08-07 20:44:31 UTC,This was fixed in https://github.com/charmed-kubernetes/bundle/pull/775
1817530,2019-03-07 18:16:30 UTC,"This sounds like a problem with the cluster. The dashboard was enabled since the service was found, but the pods were not running when they tried to load the dashboard. Do we have a field agent run or any information about this cluster so we can try and figure out why the dashboard wasn't running?"
1817532,2019-02-25 10:56:23 UTC,"StacktraceTop:
 __assert_fail_base (fmt=0x7f88f54e57d8 ""%s%s%s:%u: %s%sAssertion `%s' failed.\n%n"", assertion=assertion@entry=0x7f88f54e1e46 ""numsize == 1 && n < d"", file=file@entry=0x7f88f54e1e81 ""strtod_l.c"", line=line@entry=1495, function=function@entry=0x7f88f54e9210 <__PRETTY_FUNCTION__.12088> ""____strtod_l_internal"") at assert.c:92
 __GI___assert_fail (assertion=0x7f88f54e1e46 ""numsize == 1 && n < d"", file=0x7f88f54e1e81 ""strtod_l.c"", line=1495, function=0x7f88f54e9210 <__PRETTY_FUNCTION__.12088> ""____strtod_l_internal"") at assert.c:101
 __GI_____strtod_l_internal (nptr=<optimized out>, endptr=<optimized out>, group=<optimized out>, loc=<optimized out>) at strtod_l.c:1495
 atof (__nptr=0x7f889bffde5c ""\210\177"") at /usr/include/x86_64-linux-gnu/bits/stdlib-float.h:27
 FoFiType1::parse (this=this@entry=0x7f88944ec9d0) at ./fofi/FoFiType1.cc:343"
1817532,2020-03-07 23:17:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817532,2021-01-21 02:33:07 UTC,I get this bug constantly. 30% chance of crashing on every compile.
1817538,2019-02-26 11:52:41 UTC,"Dig a bit murano code, and still think Murano should fix this."
1817538,2019-02-27 10:48:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639626"
1817542,2019-03-22 03:43:31 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1817542,2019-03-24 23:39:14 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1817542,2019-03-06 00:30:07 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/641173"
1817542,2019-03-05 20:42:51 UTC,"Reviewed:  https://review.openstack.org/639936
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=31fe7c76009e1c6d7859036e44b057d081b059b5
Submitter: Zuul
Branch:    master"
1817542,2019-02-28 07:18:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639936"
1817542,2019-03-13 20:48:35 UTC,"Reviewed:  https://review.openstack.org/641173
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e2185168f812286dd140936df64261e67568a410
Submitter: Zuul
Branch:    stable/rocky"
1817550,2019-02-25 20:20:46 UTC,I managed to create a hook. After the merge of the calculations branch I will create a new branch for b21.
1817550,2019-02-26 05:32:32 UTC,I'd be OK with both options. Percentage might be easier to understand.
1817550,2019-02-26 07:36:24 UTC,"I would go for percentage as well, as it is clearly visible how far away from the target (50%) a player is."
1817550,2019-02-26 08:13:43 UTC,+1 for percentage.
1817550,2019-02-26 09:05:17 UTC,"Ok I will start a branch tonight:
going for percentage using the image from collectors (small column diagram)
I will do the same for artifacts as well"
1817550,2019-02-26 09:37:21 UTC,I made an icon for the artifacts stats.
1817550,2019-02-26 17:10:57 UTC,Here is an icon for Territorial.
1817550,2019-02-26 17:12:55 UTC,Here is another icon for Territorial. I prefer the big over the small but have a look yourself.
1817550,2019-03-26 07:44:36 UTC,branch is onli´ne so we can already start the review
1817550,2019-09-15 15:59:18 UTC,Migrated to https://github.com/widelands/widelands/issues/1087
1817551,2019-03-05 16:49:27 UTC,"xenial/linux-azure=4.15.0-1040.44 promoted to -updates, setting 'stakeholder-signoff' to 'Fix Released'."
1817551,2019-03-05 17:36:26 UTC,All tasks have been completed and the bug is being set to Fix Released
1817554,2019-03-10 15:06:46 UTC,now working with 8.3. At least building with 7.4 shows test failures everywhere.
1817554,2019-03-11 11:36:19 UTC,fixed in disco
1817554,2019-03-21 22:47:32 UTC,"Thanks for uploading the fix for this bug report to -proposed.  However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process.  You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential.  Thanks in advance!"
1817554,2019-03-22 18:27:25 UTC,Marked incomplete per Brian's last comment.
1817554,2019-03-25 10:40:03 UTC,"setting back to NEW, it already is broken with any GCC 8 version in bionic."
1817554,2019-04-02 11:17:34 UTC,"Hello Matthias, or anyone else affected,"
1817554,2019-04-02 11:23:44 UTC,"Hello Matthias, or anyone else affected,"
1817554,2019-04-02 23:41:52 UTC,"the package built with the GCC 7.4.0 in bionic-proposed, and built with GCC 8.2.0 in cosmic-proposed."
1817554,2019-04-11 07:38:23 UTC,"I suppose this one should go out along with the gcc toolchain update SRU, right?"
1817554,2019-04-11 10:05:25 UTC,"On 11.04.19 09:38, Łukasz Zemczak wrote:

> I suppose this one should go out along with the gcc toolchain update
> SRU, right?
"
1817554,2019-04-29 19:03:48 UTC,"The verification of the Stable Release Update for ggcov has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1817554,2019-04-29 19:04:40 UTC,This bug was fixed in the package ggcov - 0.9+20190314-0ubuntu1~18.10
1817554,2019-04-29 19:08:18 UTC,This bug was fixed in the package ggcov - 0.9+20190314-0ubuntu1~18.04
1817555,2019-02-27 20:53:32 UTC,Here is another current example that shows devstack uses the requirements and not LIBS_FROM_GIT (the master source).
1817555,2019-12-15 04:17:29 UTC,[Expired for devstack because there has been no activity for 60 days.]
1817555,2019-10-15 08:32:04 UTC,"Sadly all the logs have expired, please attach fresh logs if this is still an issue."
1817555,2019-03-01 01:53:20 UTC,I agree with networking-sfc case that its dev version is not used. I am not sure why that happened.
1817555,2019-02-27 18:02:09 UTC,"I do not think LIBS_FROM_GIT and requirement.txt are two conflict entity. repo
mentioned in LIBS_FROM_GIT will be checked against the requirement.txt version and
they should satisfy with the latest master version of repo mentioned in LIBS_FROM_GIT."
1817555,2019-02-27 19:02:27 UTC,"In regards to networking-sfc...
Based on [1] it looks like networking-sfc 8.0.0.0b1 was just released a few days ago.
The job results in comment #2 are a bit old; before 8.0.0.0b1 was released. At that time I believe 7.1.0.dev45 was the latest."
1817555,2019-02-27 18:13:12 UTC,"Even I checked the master gate job on networking-sfc side and the latest networking-sfc version installed there is 7.1.0.dev45.
which confirm that networking-sfc and neutron version in tricircle job is from source. There is some issue on networking-sfc side."
1817556,2019-02-26 09:14:50 UTC,"The implemented workflow on multi monitor:
- press a toolbar button with a capture/selection feature
- all monitors should show a read frame and the capture/selection text
- pressing the mouse on one of the monitors will
  - will still show frame and text on this monitor
  - will no longer show anything on the other monitors
- since mouse dragging cannot be restricted to the selected monitor
  - the red frame stays visible (as a reminder)
  - the selection is restricted to this monitor (though the mouse may be outside)"
1817556,2019-02-26 18:26:44 UTC,Testing for Take Screenshot:
1817556,2019-02-27 09:01:46 UTC,great thanks for the systematic work and docs.
1817556,2019-02-27 10:12:40 UTC,I'm only too pleased to be able to help. The impression I get is you maintain Sikulix almost single-handed and that must involve a lot of work. It would be better if the workload could be spread a bit more.
1817559,2019-02-28 21:41:13 UTC,The trick with setting zero or negative number for interval_days won't be working since it will be meaning to trigger updater right away (see the attached screenshot with the related setting) - here is the related code (it's still the same in 18.10/Cosmic):
1817559,2019-02-28 21:24:35 UTC,"Now it's becoming interesting and really confusing. I had some time to dig through a little. Looks like that update-notifier can be configured through gsettings/dconf-editor (see the related attached screenshot). So, update-manager has nothing to do with notifications but it's update-notifier which runs update-manager."
1817559,2019-02-28 19:52:45 UTC,Some comments
1817559,2019-02-28 21:44:26 UTC,"> (see the attached screenshot with the related setting)
"
1817559,2019-03-01 10:27:37 UTC,"Ubuntu’s update prompt is a notification in the ordinary English sense of the word. <https://wiki.ubuntu.com/NotificationDesignGuidelines#Normal_window> So I guess the dconf keys predate update-notifier’s change from using FDo notifications to launching update-manager, but I don’t think that requires their name or description to be changed. (It is perverse, though, to have a boolean setting whose name starts with “no-”.)"
1817559,2019-03-01 14:53:58 UTC,"Specification updated <https://wiki.ubuntu.com/SoftwareUpdates?action=diff&rev2=230&rev1=229>: ‘Whenever “Automatically check for updates:” is set to “Never” (so any security updates are known from manual or previous checks), the “When there are security updates:” menu should consist of options “Remind me daily” (the default), “Remind me every two days”, “Remind me weekly”, and “Remind me every two weeks”. Whenever “Automatically check for updates:” is set to anything other than “Never”, the “When there are security updates:” menu should instead consist of options “Display immediately” (the default) and “Install automatically”.’"
1817559,2020-09-22 06:28:36 UTC,This bug is still present int 20.04.
1817559,2019-02-28 19:49:30 UTC,"> Should I mark this report as invalid now and create a new one related to `update-notifier' package at this time?
"
1817559,2019-02-28 23:02:17 UTC,Changing the setting for how often to automatically check for updates to 'Never' instructs the system not to automatically run 'apt-get update' to check for updates.  It does not invalidate the results of a previous 'apt-get update' run which has already found that there are updates waiting to be applied.
1817559,2019-02-28 19:07:35 UTC,"> what you call 'notification' seems to be in fact the application itself opening (you still didn't include any screenshot showing a notification so let's assume it's a vocabulary error)
"
1817559,2019-02-28 19:59:46 UTC,"$ apt-cache policy update-notifier
update-notifier:
  Installed: 3.168.10
  Candidate: 3.168.10
  Version table:
 *** 3.168.10 500
        500 https://mirror.one.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.168.7 500
        500 https://mirror.one.com/ubuntu xenial-security/main amd64 Packages
     3.168 500
        500 https://mirror.one.com/ubuntu xenial/main amd64 Packages"
1817559,2019-02-28 17:18:05 UTC,"And here is the *current* settings which *have been active* while I've got that dialog window ( on the previous attachment: https://launchpadlibrarian.net/413195181/update-manager-screenshot-with-ignored-settings.png ) with notification about updates, in the attachment."
1817559,2019-02-28 17:04:08 UTC,">> Could you take a screenshot/photo from one of those notifications?
"
1817559,2019-02-26 22:54:41 UTC,None of those screenshot show a notification...
1817559,2019-02-28 17:40:39 UTC,"Ok, so what you call 'notification' seems to be in fact the application itself opening (you still didn't include any screenshot showing a notification so let's assume it's a vocabulary error)"
1817559,2019-02-25 22:36:58 UTC,"> What do you call 'notification', the update-manager dialog itself?
"
1817559,2019-02-25 22:15:55 UTC,"What do you call 'notification', the update-manager dialog itself?
A notification is something like that, https://i.stack.imgur.com/HGjE9.png"
1817559,2019-02-25 20:49:07 UTC,"> The screenshot you are referencing is not a notification but update-manager itself...
"
1817559,2019-02-25 20:17:19 UTC,The screenshot you are referencing is not a notification but update-manager itself...
1817559,2019-02-25 16:55:32 UTC,"> Could you take a screenshot/photo from one of those notifications?
"
1817559,2019-02-25 14:53:01 UTC,Thank you for your bug report. Could you take a screenshot/photo from one of those notifications? What desktop environment do you use?
1817562,2019-02-26 16:03:41 UTC,apport information
1817562,2019-02-26 16:03:42 UTC,apport information
1817562,2019-02-26 16:03:44 UTC,apport information
1817562,2019-02-26 16:03:39 UTC,apport information
1817562,2019-02-26 16:03:45 UTC,apport information
1817562,2019-02-26 16:03:43 UTC,apport information
1817562,2019-02-26 16:03:38 UTC,apport information
1817562,2019-02-26 16:03:40 UTC,apport information
1817562,2019-02-26 16:03:35 UTC,apport information
1817562,2019-02-26 16:03:34 UTC,apport information
1817562,2019-02-26 16:03:33 UTC,apport information
1817562,2019-02-26 16:03:31 UTC,apport information
1817562,2019-02-26 16:03:30 UTC,apport information
1817562,2019-02-25 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817562,2019-02-26 16:03:37 UTC,apport information
1817564,2019-06-18 23:02:57 UTC,I'm removing the field-critical designation as this is a missing feature of the manual provider and doesn't match the SLA guidelines.
1817564,2019-06-18 13:12:45 UTC,"On AWS, controllers had only a single interface."
1817564,2019-06-18 13:03:16 UTC,"Please could someone look at comment #4 (for Pedro) and look into the logs, check if there is anything wrong, because enable-ha was failing on this env.  We're currently in the middle of a deployment and this is blocking our progress.  Many thanks."
1817564,2019-06-18 12:49:28 UTC,I am marking this bug as field-critical since we need enable-ha functionality for manual provider on ongoing deployment.
1817564,2019-06-18 12:48:48 UTC,"Hi, I am trying juju 2.6/candidate snap.
I manually added 3 machines to my controller model; run:"
1817564,2019-06-12 23:27:00 UTC,@joe can you please backport this in your AM?
1817564,2019-02-25 14:22:45 UTC,"For the record, when I added a second machine"
1817564,2019-06-13 10:27:59 UTC,2.6: https://github.com/juju/juju/pull/10325
1817568,2019-03-01 08:50:55 UTC,"Hi Daisy,"
1817568,2019-02-26 05:43:45 UTC,Thanks for your finding.
1817568,2019-02-26 08:28:36 UTC,"I'd suggest considering a black list, we define this as a configuration item and then
user is eligible to modify it .. MAINT640, MAINT, DIRMAINT , TCPMAINT etc should all be prevented
so a configuration item + (possible a REGEX) is something we need consider"
1817568,2019-02-27 11:03:41 UTC,"My collegue also mentioned a black list, but be aware this can mean at least a list of about 100 userid beforehand (z/VM has a lot of system users), so maybe a mix of include/exclude can make the configuration items smaller."
1817568,2019-03-01 07:17:34 UTC,"Herald,"
1817568,2019-03-04 01:40:32 UTC,"Herald,"
1817571,2020-04-09 09:29:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817571,2019-02-25 16:22:46 UTC,"The attachment ""Guard for tk < v8.6"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1817583,2019-02-25 15:30:57 UTC,I can't even break everything :(
1817583,2019-02-25 15:32:52 UTC,Nevermind that last comment.. just figured out I need to put --break_everything before the subcommand.
1817583,2019-02-27 10:40:41 UTC,"I could reproduce with the snap, but not with the .deb, I think we need to rebuild/publish the snap."
1817583,2020-01-29 15:04:38 UTC,"Following the example on https://mojo.canonical.com/ should now work without needing ""--break-everything""."
1817584,2019-05-25 06:30:02 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.opendev.org/661432"
1817584,2019-05-29 08:11:06 UTC,"Reviewed:  https://review.opendev.org/661431
Committed: https://git.openstack.org/cgit/openstack/training-labs/commit/?id=e246560caba3237fd11aa0e992d434a04be4ba1a
Submitter: Zuul
Branch:    stable/queens"
1817584,2019-05-29 08:08:05 UTC,"Reviewed:  https://review.opendev.org/661432
Committed: https://git.openstack.org/cgit/openstack/training-labs/commit/?id=0d8de0f81fb8e5aa0d5b3500670e434c39a80f20
Submitter: Zuul
Branch:    stable/ocata"
1817584,2019-05-29 08:00:08 UTC,"Reviewed:  https://review.opendev.org/661430
Committed: https://git.openstack.org/cgit/openstack/training-labs/commit/?id=4375f502985514c3ebea48a3f6bd376045111a4f
Submitter: Zuul
Branch:    stable/rocky"
1817584,2019-05-29 07:55:18 UTC,"Reviewed:  https://review.opendev.org/661433
Committed: https://git.openstack.org/cgit/openstack/training-labs/commit/?id=70eee13c86a01a869d845aa13fe21f2b686781f0
Submitter: Zuul
Branch:    stable/pike"
1817584,2019-05-25 06:30:26 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/661433"
1817584,2019-05-25 06:29:02 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/661430"
1817584,2019-05-21 13:05:37 UTC,"Reviewed:  https://review.opendev.org/659942
Committed: https://git.openstack.org/cgit/openstack/training-labs/commit/?id=e4dec38469acdac6f9e408ac8612e709405cd998
Submitter: Zuul
Branch:    master"
1817584,2019-05-10 04:11:06 UTC,this helped to resolve the issue
1817584,2019-05-10 03:54:47 UTC,Facing same issue with mac pro and virtual box 6...do i downgrade virtual box ..which version?
1817584,2019-05-08 23:35:09 UTC,I have the same issue on RHEL 3.10.0-957.12.1.el7.x86_64 AND virtualbox 6.0.0 thru 6.0.6 on both Rocky and Queens.
1817584,2019-05-25 06:29:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/661431"
1817588,2019-02-26 15:27:47 UTC,"Change abandoned by Eric Harney (<email address hidden>) on branch: master
Review: https://review.openstack.org/639143"
1817588,2019-02-25 16:04:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639143"
1817593,2019-10-04 14:03:59 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686728"
1817593,2019-11-07 16:42:57 UTC,Verified on 1102 load. IF naming convention is changed as described.
1817593,2019-10-17 18:30:14 UTC,"Reviewed:  https://review.opendev.org/686834
Committed: https://git.openstack.org/cgit/starlingx/metal/commit/?id=d6ea5446e9d008a065a12cecc6c6a4692aa2c3e9
Submitter: Zuul
Branch:    master"
1817593,2019-09-12 14:15:43 UTC,"The vlanNN naming scheme is documented here:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-naming_scheme_for_vlan_interfaces"
1817593,2019-10-17 16:50:48 UTC,"Reviewed:  https://review.opendev.org/686728
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=c823a241f9bf695883ac97c92681478986d1da55
Submitter: Zuul
Branch:    master"
1817593,2019-08-08 05:34:15 UTC,Can be worked around by explicitly defining the cluster network. Defer to stx 3.0 for final fix.
1817593,2019-10-04 20:25:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/686834"
1817593,2019-02-28 16:26:09 UTC,"Reviewed:  https://review.openstack.org/639683
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=575be13d684eb4763092bd391f41d168341dbe1f
Submitter: Zuul
Branch:    master"
1817593,2019-02-27 15:03:58 UTC,Lowering priority to medium.  Analysis indicates this only impacts 1 lab and can be worked around by changing a vlan name.
1817593,2019-02-27 14:43:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639683"
1817593,2019-02-26 23:44:02 UTC,Changing the bug summary as further investigation shows that the issue is related to assigning the cluster network IP address.
1817593,2019-02-25 18:18:21 UTC,Marking as release gating; high priority as containers do not come up in standard and storage configs. Recent commits maybe suspect.
1817593,2019-07-08 21:00:22 UTC,"Based on input from Matt Peters (networking TL), we should investigate an alternate naming scheme for vlan interfaces (e.g. vlanN) so that the vlanN:alias will not exceed the 15 char limit."
1817595,2019-10-29 18:44:43 UTC,"Julian, can you take another look at this bug? Your comments here give me the impression you've uploaded the package, but I only see the version in the -release pocket in Bionic:"
1817595,2019-10-30 00:28:10 UTC,"Hello simonschmeisser, or anyone else affected,"
1817595,2019-10-30 00:29:46 UTC,"Hello simonschmeisser, or anyone else affected,"
1817595,2019-10-31 08:50:00 UTC,"Hello Chris (raof), Matthew (mathew-hodson) and others involved,"
1817595,2019-11-06 10:42:10 UTC,That's why I would have preferred a simple update to 1.0.3 patch release ... it's not only cmake but also a support issue as now you have differentiate between upstream 1.0.0 and ubuntu 1.0.0
1817595,2019-11-06 10:30:19 UTC,I've just noticed that the version number stayed the same - 1.0.0. Now how can I recognize e.g. in CMake whether the user has the new fixed version of this package or the old one without the fix?
1817595,2019-10-21 23:08:12 UTC,Thanks Julian for the fixes. Let us know if we can help with the SRU verification once the testing packages have been generated.
1817595,2019-11-07 09:45:32 UTC,"The verification of the Stable Release Update for urdfdom has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1817595,2019-11-07 09:55:32 UTC,This bug was fixed in the package urdfdom - 1.0.0-2ubuntu0.1
1817595,2019-10-31 16:15:21 UTC,"Thanks for testing, Simon!"
1817595,2019-10-08 19:28:04 UTC,For SRU team review: The liburdfdom-headers-dev (>= 1.0.0-1ubuntu0.1) build-depends bump in urdfdom is needed because urfdom now uses the new function added in the header upload.
1817595,2019-11-07 09:55:34 UTC,This bug was fixed in the package urdfdom-headers - 1.0.0-1ubuntu0.1
1817595,2019-09-19 13:36:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817595,2019-02-26 12:11:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817595,2019-03-01 12:21:45 UTC,Workaround until the release actually happens: set LC_NUMERIC=C in your .bashrc.
1817595,2019-06-04 09:55:06 UTC,This is affecting me. This bug is very nasty because it is hard to trace the origin and many users are affected.
1817595,2019-07-31 08:36:50 UTC,Is there a chance to still update this for Bionic? It's likely the largest user base since the latest stable ROS release is based on Bionic.
1817595,2019-10-08 19:26:17 UTC,"Fixed some minor issues (missing LP: in changelog and update-maintainer for -headers), and uploaded it."
1817595,2019-09-12 19:54:23 UTC,Some review:
1817595,2019-09-12 20:08:14 UTC,"This patch is complex enough to make folks a little uncomfortable with the SRU. Beyond Julian's suggestions (thanks Julian), Jose, are you willing to commit to thoroughly testing this and resolving any autopkgtest regressions?"
1817595,2019-09-16 23:08:02 UTC,@Julian: thanks very much for reviewing.
1817595,2019-08-09 18:54:36 UTC,Thanks Simon for submitting the bug and the help to prepare this comment. SRU bugs in Ubuntu require to follow closely the instructions provided https://wiki.ubuntu.com/StableReleaseUpdates. Here we go:
1817601,2019-03-14 21:03:49 UTC,Pushed:
1817601,2019-05-16 19:25:29 UTC,Signoff pushed to user/rogan/lp1817601_signoff
1817601,2019-05-20 19:46:02 UTC,"Thanks, Rogan.  Merged to 3.2 and above."
1817610,2019-02-25 20:06:24 UTC,Thank you for your bug report and the upstream reference
1817613,2019-02-27 15:29:28 UTC,That's odd could you post the contents of your /etc/apt/sources.list file? I'd also try running apt-get update and then apt-cache policy fdisk.
1817613,2019-03-13 20:04:57 UTC,I am confused.  The program /sbin/fdisk is part of the package util-linux.
1817613,2019-02-27 20:19:14 UTC,Here it is.
1817613,2019-02-27 20:02:31 UTC,It looks like something is wrong with your /etc/apt/sources.list file. Could you please add it to the bug per my previous request?
1817613,2019-02-27 19:25:15 UTC,"~#  apt-get update
Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Reading package lists... Done
root@rlb5:~# apt-cache policy fdisk
N: Unable to locate package fdisk"
1817613,2019-05-13 04:17:25 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1817613,2019-02-26 23:26:54 UTC," apt-cache policy fdisk
N: Unable to locate package fdisk"
1817613,2019-02-26 22:37:16 UTC,"I give fdisk has been installed in /sbin, but I can't figure out how to reinstall it."
1817613,2019-02-25 21:47:23 UTC,You seem to be missing the essential package fdisk from your install. Please install it and then try upgrading.
1817613,2019-02-25 20:27:42 UTC,"grep Broken /var/log/dist-upgrade/apt.log
Broken e2fsprogs:amd64 PreDepends on e2fslibs [ amd64 ] < 1.42.13-1ubuntu1 | 1.44.1-1ubuntu1.1 > ( libs ) (= 1.42.13-1ubuntu1)
Broken libext2fs2:amd64 Breaks on e2fslibs [ amd64 ] < 1.42.13-1ubuntu1 | 1.44.1-1ubuntu1.1 > ( libs ) (< 1.43.9-1~)
Broken e2fsprogs:amd64 PreDepends on e2fslibs [ amd64 ] < 1.42.13-1ubuntu1 | 1.44.1-1ubuntu1.1 > ( libs ) (= 1.42.13-1ubuntu1)
Broken libext2fs2:amd64 Breaks on e2fslibs [ amd64 ] < 1.42.13-1ubuntu1 | 1.44.1-1ubuntu1.1 > ( libs ) (< 1.43.9-1~)
Broken e2fsprogs:amd64 PreDepends on e2fslibs [ amd64 ] < 1.42.13-1ubuntu1 | 1.44.1-1ubuntu1.1 > ( libs ) (= 1.42.13-1ubuntu1)
root@rlb5:~#"
1817613,2019-02-26 22:54:29 UTC,"On Tue, Feb 26, 2019 at 10:37:16PM -0000, Raymond Bates wrote:

> I give fdisk has been installed in /sbin, but I can't figure out how to
> reinstall it.
>
> #  apt-get install  --reinstall  fdisk
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package fdisk
"
1817615,2019-09-19 14:54:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1817615,2019-09-20 12:18:17 UTC,This sounds reasonable to me.
1817618,2019-06-13 04:29:42 UTC,Verified passed on 0611 master load.
1817618,2019-05-22 22:03:12 UTC,"Reviewed:  https://review.opendev.org/660268
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=4a88506bfdcb030b142cbf73b9f6766b61b9929a
Submitter: Zuul
Branch:    master"
1817618,2019-05-21 07:31:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660268"
1817618,2019-05-17 06:37:55 UTC,"The reason is found, when libvirt/qemu create the VM, it will create a pty device (/dev/pts/x) for the vm also. Due to libvirt/nova is containerized now, and /dev is sperated for each container. So nova running in nova-compute container cannot find the pty device, and reports the ""console logfile instance does not exist"" error, and cause the console log cannot be shown in horizon.
The fix is try to map /dev in host to nova-compute container. Code for the change is under test now."
1817618,2019-05-08 12:26:25 UTC,"Issue is reproduced, begin to check it."
1817618,2019-03-15 19:34:00 UTC,Assigning to Cindy to identify a prime to work on this issue.
1817618,2019-03-01 19:55:26 UTC,Marking as release gating; the vm console is a key tool to help debug issues in the guest. Medium priority.
1817618,2019-05-13 02:45:00 UTC,"From nova compute log, we could find below log, need check why nova/libvirt cannot get the log file.
{""log"":""2019-05-13 02:27:46.823 2527442 INFO nova.compute.manager [req-20970eda-4e51-4b49-bf34-0175f567897d e9d3a26729064fb3b57174e588c2d48f bc278a0009864e538ce7b18b7bb8ca95 - default default] [instance: cdccdeb9-98b1-4758-b223-534717b5f02c] Get console output\n"",""stream"":""stdout"",""time"":""2019-05-13T02:27:46.825988609Z""}
{""log"":""2019-05-13 02:27:46.823 2527442 INFO nova.compute.manager [req-20970eda-4e51-4b49-bf34-0175f567897d e9d3a26729064fb3b57174e588c2d48f bc278a0009864e538ce7b18b7bb8ca95 - default default] [instance: cdccdeb9-98b1-4758-b223-534717b5f02c] Get console output\n"",""stream"":""stdout"",""time"":""2019-05-13T02:27:46.8260216Z""}
{""log"":""2019-05-13 02:27:46.830 2527442 INFO nova.virt.libvirt.driver [req-20970eda-4e51-4b49-bf34-0175f567897d e9d3a26729064fb3b57174e588c2d48f bc278a0009864e538ce7b18b7bb8ca95 - default default] [instance: cdccdeb9-98b1-4758-b223-534717b5f02c] console logfile for instance does not exist\n"",""stream"":""stdout"",""time"":""2019-05-13T02:27:46.831918789Z""}
{""log"":""2019-05-13 02:27:46.830 2527442 INFO nova.virt.libvirt.driver [req-20970eda-4e51-4b49-bf34-0175f567897d e9d3a26729064fb3b57174e588c2d48f bc278a0009864e538ce7b18b7bb8ca95 - default default] [instance: cdccdeb9-98b1-4758-b223-534717b5f02c] console logfile for instance does not exist\n"",""stream"":""stdout"",""time"":""2019-05-13T02:27:46.831957786Z""}"
1817620,2019-04-30 04:17:33 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1817620,2019-06-30 04:17:46 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1817620,2019-06-30 04:17:45 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1817620,2019-05-01 02:16:26 UTC,Please try:
1817620,2019-04-30 04:17:32 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1817620,2019-02-27 02:44:12 UTC,"Also, please run this command to send us more information about the affected machine:"
1817620,2019-02-28 01:57:01 UTC,I think this bug is very clear already. It really requires someone (most likely future me) to do some profiling on the primary test case:
1817620,2019-02-27 12:54:50 UTC,Thanks for the reply. I'll run Apport as soon as I can access the machine again.
1817620,2019-02-27 02:43:04 UTC,Performance of window previews is significantly improved in mutter 3.28.4 (which doesn't exist yet :) due to:
1817620,2019-02-28 13:04:04 UTC,"OK, removed. Just found it weird that both issues disappered by restarting `gnome-shell`, so assumed they were related by some root cause. Thank you."
1817624,2019-02-28 21:42:54 UTC,Yes.
1817624,2019-02-28 21:33:50 UTC,Am I correct in assuming we would need to remove the 'cdk-addons: true' labels from the dashboard.yaml to ensure the charm hooks don't reap the manually deployed addons?
1817624,2019-02-28 14:35:15 UTC,"The solution proposed in comment #2 won't really work since get-addon-templates runs when the cdk-addons snap is built, so it wouldn't be able to alter the templates at charm run time."
1817624,2019-02-26 00:33:53 UTC,"It seems that the influxdb-grafana-controller template already sets some GF_* vars, we just need to alter this template to set some more variables like smtp host, port, sslverify"
1817624,2019-02-26 00:20:32 UTC,The follow-up comment on this heapster related issue is probably the answer to how to get smtp variables updated into the pod via image updates.
1817624,2019-02-27 15:36:34 UTC,"subscribed ~field-critical
per csanders - this bug is preventing customer from enabling grafana alerting."
1817625,2019-02-25 21:45:24 UTC,Actually only a logout is necessary for the UI and volume slider to respond to the amp change. So I'll add steps to reproduce.
1817625,2019-02-25 22:32:48 UTC,"One more difference between the default and flashback sessions is that the keyboard hot-keys DO work in the default Ubuntu session, but NOT in the flashback session. So that makes this even a lower priority, and passes part of the responsibility onto the flashback devs."
1817627,2019-05-02 13:04:56 UTC,This is a scary bug. I was just trying to verify the syntax of a timer file using systemd v237. I got an error message back suggesting something like rm -rf / was attempted to be executed instead!
1817627,2019-02-26 16:41:56 UTC,Marking the Ubuntu Manpage Repository task invalid and adding the systemd (Ubuntu) task.
1817627,2019-02-26 20:23:58 UTC,The commit fixing the issue is https://github.com/systemd/systemd/commit/114110cd
1817627,2019-03-18 16:13:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817627,2019-03-18 16:15:51 UTC,I use separate mountpoint for /tmp directory and also am affected by this issue on latest Ubuntu 18.04.2 with all package updates installed.
1817627,2019-03-20 14:50:07 UTC,I can confirm that this bug is on Ubuntu 18.04.2 LTS with all package installed. It happens on every machine I used 18.04 on.
1817627,2019-06-17 14:13:25 UTC,"This affects each system where /tmp is *not* on tmpfs which affects a lot of cloud-built servers and effectively prevents usage of systemd-analyze verify in Ansible, Puppet etc."
1817627,2019-09-16 14:30:58 UTC,I am also very interested in this fix; it is currently preventing integration with a CI/CD pipeline for deploying my company's web app to AWS cloud-based Ubuntu 18.04 servers.
1817627,2019-12-23 17:15:29 UTC,Also in need of a fix. Trying to run a very simple and popular program as a service and it's not working due to this.
1817632,2019-06-25 02:26:02 UTC,"There is plenty of messaging about the need to grant 'add-model' permissions: at successful register, as an output for 'juju models', at succesful 'juju login', etc. Detecting/figuring out cloud is described as well in another bug that you have created, bug # 1814395. I'll close this bug and will work on the other one."
1817632,2019-02-26 06:43:59 UTC,"When a user is added to a controller, they need to be granted add-model permission in order to be able to add a model. From the pastebin, it doesn't look like this was done."
1817633,2019-03-01 13:22:18 UTC,Fixed by: https://review.openstack.org/#/c/639216/
1817633,2019-03-20 20:47:11 UTC,This issue was fixed in the openstack/placement 1.0.0.0rc1 release candidate.
1817636,2019-04-17 15:49:55 UTC,"fat32 doesn´t support files bigger than 4gb. However, an allert should be issued"
1817638,2019-10-31 13:48:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1817638,2019-12-31 04:17:33 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1817639,2019-02-27 18:15:31 UTC,"Fixed in revision f494a24404b1b4a5845b3ac9430f157f0b53d5fd
https://git.launchpad.net/kicad/patch/?id=f494a24404b1b4a5845b3ac9430f157f0b53d5fd"
1817639,2019-03-01 00:45:38 UTC,@Jeff
1817645,2019-09-12 19:13:02 UTC,See bug 1843818 for addressing Galen's errata and any other small fixes.
1817645,2019-09-06 21:20:30 UTC,"Merged to master for inclusion in 3.4. Thanks, Jeff!"
1817645,2019-06-17 21:32:41 UTC,"Thanks, Galen. I've pushed an additional commit to the working branch, adding the appropriate reporter:selector attribute. It works for me."
1817645,2019-06-17 14:14:48 UTC,I've opened bug 1833080 for the eg-bool bug.
1817645,2019-06-17 14:00:09 UTC,"> The admin UI is auto-generated by Angular. Unfortunately the User
> Activity Type selector displays the id of the various user activity
> types, which is not very helpful; it ought to display the label. Do we
> need a specialized User Activity Type component for this? How would you
> implement that in an auto-generated UI?
"
1817645,2019-06-14 20:37:12 UTC,Working branch user/jeffdavis/lp1817645-remoteauth-patron-api-squashed-rebased has some updates:
1817645,2019-04-10 21:39:38 UTC,"And a blue-sky suggestion, probably for later: add something to the patron's My Account pages that tells them when their credentials have been used last, both for direct Evergreen login and for authentication for other services."
1817645,2019-03-07 23:52:40 UTC,Force-pushed a few tweaks (like returning the user object on successful patron auth so that future handlers can use it).  And now I'm un-assigning myself from this bug and leaving it alone for review.
1817645,2019-04-10 21:35:08 UTC,Some comments I posted to open-ils-dev: http://libmail.georgialibraries.org/pipermail/open-ils-dev/2019-April/010702.html
1817645,2019-04-04 22:53:43 UTC,TechRef documentation has been pushed to the working branch.
1817645,2019-03-07 23:19:03 UTC,"Sorry, under ""Apache configuration"" above, ""OILSRemoteAuthConfig"" above should be ""OILSRemoteAuthProfile"".  When I add documentation it will use the correct name."
1817645,2019-03-07 21:25:23 UTC,Working branch user/jeffdavis/lp1817645-remoteauth-patron-api has an initial implementation:
1817645,2019-04-10 21:37:23 UTC,But the quick summary:
1817648,2019-02-26 04:20:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1817648,2019-02-26 22:34:52 UTC,Additional Information as of 2019.02.26 (Ubuntu Linux 14.04.1)  Had to reset all directory permissions again in order to start Sendmail again.
1817648,2021-02-13 14:28:51 UTC,This error can happen when there is a problem with your sendmail.cf: It seems that Debian's sendmailconfig doesn't properly handle errors in sendmail configuration files. For instance if there is a syntactic error and you see a message like:
1817649,2019-02-26 03:00:06 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1817650,2019-03-20 17:51:45 UTC,What are the exact contents of /etc/netplan/50-cloud-init.yaml and /etc/netplan/60-puppet-netplan.yaml? Do both define bond0?
1817650,2019-05-20 04:17:29 UTC,[Expired for netplan.io (Ubuntu) because there has been no activity for 60 days.]
1817650,2019-05-20 04:17:30 UTC,[Expired for netplan because there has been no activity for 60 days.]
1817651,2021-01-19 20:57:59 UTC,@seyeongkim - nothing will appear at autopkgtest until the package has been accepted into the archive i.e. -proposed in this case.
1817651,2021-01-19 04:03:01 UTC,Hey @slyon
1817651,2021-01-19 20:58:30 UTC,"Hello Shahaan, or anyone else affected,"
1817651,2020-05-14 10:21:07 UTC,"A PPA for testing this fix can be found here:
https://launchpad.net/~slyon/+archive/ubuntu/fix-1817651"
1817651,2021-01-26 22:48:32 UTC,This bug was fixed in the package netplan.io - 0.99-0ubuntu3~18.04.4
1817651,2021-01-16 23:39:40 UTC,"Already backported to Focal.
---"
1817651,2021-01-26 22:48:36 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1817651,2021-01-20 04:58:15 UTC,Verification is done for Bionic
1817651,2021-01-15 13:51:46 UTC,"Thank you Seyeong for preparing the debdiff for Bionic. It is malformatted at line 36, but I fixed that."
1817651,2019-02-26 02:33:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817651,2020-05-15 06:25:54 UTC,"Comitted upstream:
https://github.com/CanonicalLtd/netplan/commit/35548a4f4fe99932122272f7bb2ef1bf4eb38bb9"
1817651,2020-09-22 11:41:00 UTC,This bug was fixed in the package netplan.io - 0.100-0ubuntu4
1817651,2020-05-14 08:06:27 UTC,I proposed a fix upstream: https://github.com/CanonicalLtd/netplan/pull/136
1817651,2020-05-13 15:44:56 UTC,"I can confirm this issue on Focal, netplan 0.99."
1817651,2019-11-28 07:13:31 UTC,"root@lab02:~# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)"
1817651,2019-11-28 07:06:41 UTC,"I'm having this problem too with Ubuntu 19.10. I was able to workaround by commenting out ""primary: enp65s0"", but this solution is far from optimal because eno1 is 10 GbE and enp65s0 is 56 GbE. I always want enp65s0 to be the primary, unless it is unavailable."
1817652,2019-02-26 04:20:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1817652,2019-04-05 09:24:35 UTC,"This bug might be related to input grabbing that the VirtualBox window does, and that might prevent the dock (or gnome-shell in general) from getting a grab that it needs to detect exterior clicks for closing the menu."
1817652,2019-06-05 04:17:17 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1817653,2019-02-26 03:00:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1817656,2019-02-26 03:34:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639247"
1817656,2019-03-01 08:16:07 UTC,"How can I reproduce this?
Is there any assumptions and/or pre-requisites?"
1817656,2019-03-01 08:46:38 UTC,"You can change the state of the volume to creating. First open the Create Volume modal box, then close it.input any value can be filtered out the status is the volume in the creating."
1817656,2019-05-20 04:57:07 UTC,"Reviewed:  https://review.opendev.org/639247
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=04399d69e46b666701accae9e10ba2318957498b
Submitter: Zuul
Branch:    master"
1817656,2019-06-12 14:44:18 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1817658,2019-04-02 20:08:00 UTC,Try installing libavcodec-extra. Does that make netflix play videos?
1817658,2019-06-02 04:17:34 UTC,[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]
1817663,2019-08-27 23:30:14 UTC,There are really two bugs here
1817663,2019-02-26 07:27:54 UTC,"I disabled the MAAS plugin on sosreport because it was doing a full pgdump which with boot images was going to be too large. If needed, let me know and I can arrange to do a dump without it."
1817663,2019-03-25 06:11:06 UTC,This happened again after rebooting the system. Generated another sosreport.
1817663,2019-03-25 06:18:47 UTC,"Ignore the OOM killer in dmesg, my journald was very large and there is a sosreport bug where it runs out of memory trying to get all of the output."
1817663,2019-03-25 14:02:44 UTC,What status is the rackd reporting for that service in MAAS?
1817663,2019-04-25 07:44:20 UTC,Unfortunately cannot see the status in MAAS as of now but I checked the sosreport.
1817663,2019-08-27 21:14:43 UTC,I just hit this upgrading a production maas server to 2.6 as well.
1817663,2019-08-27 21:35:25 UTC,"Here's what I did:
* Started on 2.4 with working dhcpd.
* Did an 'apt upgrade' after adding the maas/stable ppa to get to MAAS version: 2.6.0 (7802-g59416a869-0ubuntu1~18.04.1)
* When upgrade was done, did a reboot assuming things would be cleanly restarted from there."
1817663,2019-08-27 21:38:14 UTC,Here are the maas and apt logs
1817663,2019-09-05 07:42:47 UTC,"I can reproduce this quite easily by simply restart maas-regiond (and not maas-rackd). It doesn't happen every time, but every second or third time."
1817666,2019-02-27 02:52:47 UTC,Are you able to say what you were/are doing when the system hangs?
1817668,2019-02-26 08:07:54 UTC,"Hi,"
1817672,2019-02-27 08:29:48 UTC,"Reviewed:  https://review.openstack.org/639293
Committed: https://git.openstack.org/cgit/openstack/charm-manila/commit/?id=fac841f370477b42a19b0326d2c75ce7ac2477ef
Submitter: Zuul
Branch:    master"
1817672,2019-02-27 08:27:04 UTC,"Reviewed:  https://review.openstack.org/639309
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=4bf409fb18a43a97302bf78605b0813aa173d359
Submitter: Zuul
Branch:    master"
1817672,2019-02-27 07:32:09 UTC,"Reviewed:  https://review.openstack.org/639278
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=c73311350e3ae2826f755ead94f5c7ab1f76e4cd
Submitter: Zuul
Branch:    master"
1817672,2019-02-27 07:38:38 UTC,"Reviewed:  https://review.openstack.org/639270
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=56873b0c3e68fa6749cac9cc1612c9d297eb8a8a
Submitter: Zuul
Branch:    master"
1817672,2019-02-27 07:28:02 UTC,"Reviewed:  https://review.openstack.org/639302
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=5ae43bb056b59e47baccc206bef4e6d0b25920f2
Submitter: Zuul
Branch:    master"
1817672,2019-02-27 08:15:40 UTC,"Reviewed:  https://review.openstack.org/639275
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=5e3ffa90e6a875f59f56d383d73aaacaafc110a9
Submitter: Zuul
Branch:    master"
1817672,2019-02-27 08:48:32 UTC,"Reviewed:  https://review.openstack.org/639333
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer-agent/commit/?id=54530ab595a7e43c479e318b7cb459138024bd53
Submitter: Zuul
Branch:    master"
1817672,2019-02-26 09:56:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639290"
1817672,2019-02-28 08:45:34 UTC,"Reviewed:  https://review.openstack.org/639297
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=cb778a052770ff72dbc557f5c36d5f1816ad775b
Submitter: Zuul
Branch:    master"
1817672,2019-02-28 09:29:26 UTC,"Reviewed:  https://review.openstack.org/639287
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=06f8577a61109856abb111e0ce098b3130adf507
Submitter: Zuul
Branch:    master"
1817672,2019-02-28 13:06:36 UTC,"Reviewed:  https://review.openstack.org/639289
Committed: https://git.openstack.org/cgit/openstack/charm-aodh/commit/?id=9049b903f598452812ca73f304f11fc006679181
Submitter: Zuul
Branch:    master"
1817672,2019-02-28 21:17:27 UTC,"Reviewed:  https://review.openstack.org/639291
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=1938f5f8db9bd16bb59dd3b0f5239dd60937eea2
Submitter: Zuul
Branch:    master"
1817672,2019-03-05 20:26:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641118"
1817672,2019-02-27 07:25:45 UTC,"Reviewed:  https://review.openstack.org/639273
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=9254beb043bb73e914430125eceec03afd8ea855
Submitter: Zuul
Branch:    master"
1817672,2019-03-07 08:13:00 UTC,"Reviewed:  https://review.openstack.org/641118
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=efb1a1e2d9d160336dc6a2d8432a26dc63aa3cfe
Submitter: Zuul
Branch:    master"
1817672,2019-02-27 09:55:24 UTC,"Reviewed:  https://review.openstack.org/639271
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-dynamic-routing/commit/?id=3bedb660d484b07f12fc30f5553d53cd3bda0f15
Submitter: Zuul
Branch:    master"
1817672,2019-02-26 15:54:32 UTC,"Reviewed:  https://review.openstack.org/639274
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=66b4c91b5ff6e285f553af5f39b59a5dc68aacd0
Submitter: Zuul
Branch:    master"
1817672,2019-02-26 09:52:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639287"
1817672,2019-02-26 12:36:37 UTC,"Reviewed:  https://review.openstack.org/639296
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cell-controller/commit/?id=3919907d219bbdfba9ccae880a25208d70efe1a3
Submitter: Zuul
Branch:    master"
1817672,2019-02-26 11:09:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639309"
1817672,2019-02-26 10:55:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639302"
1817672,2019-02-26 10:22:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639296"
1817672,2019-02-26 10:08:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639293"
1817672,2019-02-26 10:00:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639291"
1817672,2019-02-26 09:58:46 UTC,"Reviewed:  https://review.openstack.org/639279
Committed: https://git.openstack.org/cgit/openstack/charms.openstack/commit/?id=93f4831605b5bff08af2af400aac76eb0bb8238f
Submitter: Zuul
Branch:    master"
1817672,2019-02-26 09:52:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639289"
1817672,2019-02-26 09:29:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639279"
1817672,2019-02-26 09:26:10 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639278"
1817672,2019-02-26 09:17:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639275"
1817672,2019-02-26 08:32:34 UTC,This change should be applied for >= ocata templates as this is the point that the now removed rabbitmq sectional configuration was deprecated.
1817672,2019-02-26 08:12:00 UTC,Snippet from nova-cloud-controller that DTRT:
1817672,2019-02-26 12:38:47 UTC,"Reviewed:  https://review.openstack.org/639290
Committed: https://git.openstack.org/cgit/openstack/charm-barbican/commit/?id=b43d331390241f16644374e3f8f9abc7f67e9c5e
Submitter: Zuul
Branch:    master"
1817673,2019-02-28 19:20:55 UTC,This is going to be added to the version 6 road map.  It's something that I've wanted to do for a long time but just haven't found the time to get around to it.
1817673,2019-02-26 08:16:15 UTC,Also fabs will not be required to publish lengthy descriptions like http://support.seeedstudio.com/knowledgebase/articles/1824574-how-to-generate-gerber-and-drill-files-from-kicad but rather just provide 1 simple downloadable preset with correct settings.
1817676,2019-04-19 00:12:14 UTC,This bug was fixed in the package linux-oem - 4.15.0-1035.40
1817676,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1817676,2019-04-02 10:45:28 UTC,This bug was fixed in the package linux-oem - 4.15.0-1035.40
1817676,2019-02-26 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817682,2019-03-20 10:08:08 UTC,"Nikolay,"
1817682,2019-03-20 10:06:48 UTC,"Jonas, that is bug 1812527 you have. Please comment in bug 1812527 instead."
1817682,2019-03-20 09:57:23 UTC,Re-pasting attachment cleaned from sensitive data.
1817682,2019-03-20 08:13:38 UTC,"Jonas, that is bug 1812527 you have. Please comment in bug 1812527 instead."
1817682,2019-03-20 07:45:52 UTC,I have exactly the same problem but it only happens when I talk to people that uses Windows on their desktop. I attached a section of my syslog where this happened.
1817682,2019-03-20 02:12:11 UTC,Please:
1817682,2019-03-20 02:10:15 UTC,If the problem relates to workspace switching in 18.04 then there's also a good chance that this is bug 1812527.
1817682,2019-03-19 10:27:19 UTC,A possible workaround is to just stop using multiple workspaces (put everything on the default one) and don't switch between them.
1817682,2019-03-06 01:51:38 UTC,"OK. My best guess is still bug 1754693, which doesn't yet have an 18.04 fix."
1817682,2019-03-05 15:40:57 UTC,"Hi, Dan,
thanks for your suggestions.
Unfortunately step 1 and 2 failed.
Then I applied the workaround from step 3, restarted, crashed the UI and retried 1 and 2
Looks there is no difference - no crash files and nothing for my user in errors.ubuntu.com/user"
1817682,2019-02-27 02:55:39 UTC,"This sounds like it might be bug 1754693. But still, please follow the steps above."
1817682,2019-02-27 02:54:16 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1817682,2019-02-26 12:24:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1817682,2019-02-26 11:34:35 UTC,Looks the issue appears when I'm on a video / screen sharing call and I switch between desktops.
1817682,2019-05-20 04:17:21 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1817683,2019-06-13 23:57:36 UTC,i belive you are correct that this behavior is caused by the fact you are creating a usever via cloud init.
1817684,2019-02-27 13:58:26 UTC,"I take back my suggestion about curling, as I think that it wouldn't be the common use case (though your debugging example or something like ""... | tee /dev/tty | ..."" don't seem hard-to-debug). I think it would be really useful to allow reading from stdin for the case of something like my first example, as it's really easy to debug something that's part of the command itself. That would also let it stick around in shell history, and for example I wouldn't come back to something a month after I initially figured it out and curse myself for deleting the overlay file in the meantime."
1817684,2019-02-26 11:01:12 UTC,"Doesn't this lead to hard-to-debug issues where everyone has slightly
different text in their overlay? It seems to quickly lead to each
deployment being slightly different in hard to understand ways, vs having
concrete artifacts that are shared."
1817685,2019-04-05 03:47:16 UTC,"Next time the problem happens, after rebooting, please run:"
1817685,2019-06-04 04:17:40 UTC,[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]
1817696,2019-02-26 11:53:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639316"
1817696,2019-03-02 09:06:44 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/639316
Reason: I will remove this test from tempest as same test is in neutron-tempest-plugin already. Fix for this bug will go to neutron-tempest-plugin repo"
1817696,2019-03-25 20:37:34 UTC,This issue was fixed in the openstack/neutron-tempest-plugin 0.3.0 release.
1817696,2020-10-21 09:13:41 UTC,The fix for this bug has been merged in neutron-tempest-plugin (since 0.3.0 release). I consider this bug fixed then.
1817697,2019-04-08 07:12:16 UTC,"Hi Akihiro,
It was with ocata and i dnt think there is any change in driver in latest release too,
so may be the driver needs this fix."
1817697,2019-02-26 14:46:44 UTC,"Which release do you use?
FWaaS v1 API was dropped in the development version, so we need more detail input."
1817697,2019-05-20 09:37:50 UTC,"After my test,FWaaS_v2 have no this problem."
1817701,2019-10-07 14:23:49 UTC,This issue was fixed in the openstack/tempest 22.0.0 release.
1817701,2019-09-03 20:47:49 UTC,"Reviewed:  https://review.opendev.org/639319
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=fa30d2fb51d40cb7ef527fa11ce5ab9dd81d6d94
Submitter: Zuul
Branch:    master"
1817701,2019-03-07 02:15:05 UTC,"Yeah, there are issue in few cases. I thought we always get complete server response and then pass it to get_server_ip."
1817701,2019-02-27 03:49:43 UTC,I run test with 18.0.0 and one case failed. But seems to be more failed test cases at master with same reason.
1817701,2019-02-26 12:02:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639319"
1817713,2017-10-31 13:50:35 UTC,"------- Comment From <email address hidden> 2017-10-31 09:49 EDT-------
Going deeper in the rabbit hole from IBM Comment 27 / RH Comment 12:"
1817713,2017-10-27 21:00:27 UTC,"------- Comment From <email address hidden> 2017-10-27 16:59 EDT-------
For now, I tried to look inside grub-probe to see if I could find any clues."
1817713,2017-12-11 20:31:04 UTC,"------- Comment From <email address hidden> 2017-12-11 15:28 EDT-------
Finally had quality time for this bug again. Carrying on:"
1817713,2017-04-23 08:25:16 UTC,"------- Comment From <email address hidden> 2017-04-21 12:48 EDT-------
Here's where I have stopped grub2-install in gdb:"
1817713,2018-06-06 19:01:20 UTC,This works for me using grub2-2.02-0.65.el7_4.2 on an EFI machine with a 4k disk:
1817713,2018-06-13 19:30:21 UTC,"------- Comment From <email address hidden> 2018-06-13 15:24 EDT-------
Hi, I'm still getting the result:"
1817713,2017-10-27 17:30:22 UTC,"------- Comment From <email address hidden> 2017-10-27 13:23 EDT-------
Hello Kevin,"
1817713,2018-01-16 19:10:44 UTC,"------- Comment From <email address hidden> 2018-01-16 14:09 EDT-------
Just for the record, I have also reproduced this bug in x86_64 with ubuntu 17.10."
1817713,2017-10-27 16:14:52 UTC,"(In reply to IBM Bug Proxy from comment #9)

> ------- Comment From <email address hidden> 2017-10-27 10:51 EDT-------
> (In reply to comment #23)
> > Is there any progress on this?
> >
> > We've just been hit by the same issue on an E850 during install, getting to
> > the point where we can't install a system using software RAID 1.
> >
> > As it stands, we're having to install without RAID to get a system up and
> > running...
>
> The install-side issue should already have been addressed for RHEL 7.4 via
> RH Bug 1184945.  The easy workaround is to not  use version 1.0 metadata for
> the RAID config.
"
1817713,2017-04-19 18:00:18 UTC,"------- Comment From <email address hidden> 2017-04-19 13:58 EDT-------
(In reply to comment #4)
...

> Additional info:
> Note, the issue was originally noted at installation-time as the default
> superblock format for PPC64 (PReP boot) systems is 1.0 according to the
> python-blivet library, used by the anaconda installer, code snippet below:
>
> def preCommitFixup(self, *args, **kwargs):
> """""" Determine create parameters for this set """"""
> mountpoints = kwargs.pop(""mountpoints"")
> log_method_call(self, self.name, mountpoints)
>
> if ""/boot"" in mountpoints:
> bootmountpoint = ""/boot""
> else:
> bootmountpoint = ""/""
>
> # If we are used to boot from we cannot use 1.1 metadata
> if getattr(self.format, ""mountpoint"", None) == bootmountpoint or \
> getattr(self.format, ""mountpoint"", None) == ""/boot/efi"" or \
> self.format.type == ""prepboot"":
> self.metadataVersion = ""1.0""
"
1817713,2017-10-27 11:32:30 UTC,Is there any progress on this?
1817713,2017-09-26 12:10:21 UTC,"------- Comment From <email address hidden> 2017-09-26 08:09 EDT-------
Hi,"
1817713,2017-06-12 21:40:19 UTC,"------- Comment From <email address hidden> 2017-06-12 17:33 EDT-------
As expected, migrating /boot to raid 1 using metadata 1.0 when it is the first partition after prep fails:"
1817713,2017-06-08 18:00:22 UTC,"------- Comment From <email address hidden> 2017-06-08 13:55 EDT-------
I just ran a fresh installation enabling raid on a 4k block disk and I could not reproduce the problem stated on additional notes ""the issue was originally noted at installation-time"". Here are the information right after the first boot:"
1817713,2017-04-23 08:19:23 UTC,.
1817713,2019-06-13 09:12:28 UTC,"ok ... with no news for this bugzilla since exactly one year
I am closing this Red Hat bugzilla now
and please reopen if required with then using the current RHEL7.7 ...
... thanks for your support ..."
1817713,2017-04-18 15:08:07 UTC,"Description of problem:
 Per the description above, Grub2 does not currently detect MD raid 1.0 superblocks when written to 4k block devices. The issue is only visible on disks that have 4K native sector sizes."
1817713,2017-10-27 15:01:01 UTC,"------- Comment From <email address hidden> 2017-10-27 10:51 EDT-------
(In reply to comment #23)

> Is there any progress on this?
>
> We've just been hit by the same issue on an E850 during install, getting to
> the point where we can't install a system using software RAID 1.
>
> As it stands, we're having to install without RAID to get a system up and
> running...
"
1817721,2019-12-10 23:53:20 UTC,"I'm seeing the ""upstream"" test suite fail in Eoan as well: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/ppc64el/s/systemd/20191206_074525_b4418@/log.gz"
1817721,2019-12-09 23:33:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817721,2020-07-01 00:40:26 UTC,"So after some investigation on systemd failures on ppc64el triggered by the kernel on eoan, I noticed some coredumps on processes when running under qemu inside the ADT environment."
1817721,2019-07-31 13:24:48 UTC,I'm fixing this.
1817725,2019-02-27 08:57:07 UTC,(Partial) return from ls -f on infra-3: https://pastebin.ubuntu.com/p/WbV3n847XZ/
1817725,2019-03-04 14:53:59 UTC,I was rechecking my configurations on Juju and I've found out that Juju's proxy was pointing at infra-3 node's. Although that is partially wrong (we should be pointing to the VIP instead) that explains why only infra-3 is seeing this issue.
1817725,2019-09-19 14:54:30 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1817725,2019-02-26 16:16:56 UTC,"Hi, Blake. Well, doing ls -l just hanged for several minutes and we
eventually had to ctrl+c it."
1817725,2019-03-05 14:18:33 UTC,Are you seeing errors in the rackd.log that look like this?
1817725,2019-02-26 16:03:34 UTC,Can you do?
1817725,2019-02-26 15:34:41 UTC,"Hi Pedro,"
1817725,2019-02-26 15:35:58 UTC,"FWIW, MAAS is complaining about lack of space:"
1817725,2019-02-26 14:14:51 UTC,"@andreserl, what do you need more as information?"
1817725,2019-02-26 15:59:49 UTC,"No Andres, we actually started troubleshooting by checking disk space. I dont have the print anymore, but it was not at all missing space. That was all fine on all 3 infra nodes."
1817732,2019-02-26 14:27:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639347"
1817732,2020-11-26 02:29:14 UTC,This was already fixed by https://review.opendev.org/670861
1817734,2019-04-02 10:30:17 UTC,This bug was fixed in the package linux-hwe - 4.15.0-47.50~16.04.1
1817734,2019-04-02 10:32:00 UTC,This bug was fixed in the package linux-hwe - 4.18.0-17.18~18.04.1
1817737,2019-02-27 03:08:38 UTC,"It seems to crash less for me in 18.10 than it did in 18.04. 18.04 has dock-applet .85 (https://packages.ubuntu.com/bionic/mate-dock-applet), while 18.10 has .87 (https://packages.ubuntu.com/cosmic/mate-dock-applet). Looking at the dependencies, I think you could install the 18.10 package on 18.04 that you can download from that page. (I'm pretty sure I did this on 18.04 before 18.10 was released.) You could probably even install the 19.04 version .88 (https://packages.ubuntu.com/disco/mate-dock-applet). If it installs but doesn't end up working, you can `sudo apt install --reinstall mate-dock-applet` to get the 18.04 package back."
1817739,2019-02-27 17:17:36 UTC,I tested this on our 3.2.4 system and can confirm.
1817739,2019-03-25 13:44:57 UTC,I can confirm issue at Evergreen Indiana with 3.2 as well. No errors in queue and log indicates attempt to use the deleted bib when that is the best match found out of 3 bibs in our case.
1817740,2019-04-02 10:58:25 UTC,This bug was fixed in the package linux-azure - 4.15.0-1041.45~14.04.1
1817742,2019-02-28 15:27:53 UTC,Interestingly I noticed that Fedora's SCons 3 package uses /usr/bin/python2 as the interpreter rather than Python 3.
1817742,2019-03-01 11:46:48 UTC,I'm also using python 2.7
1817742,2019-03-20 13:54:02 UTC,I am getting errors compiling Mixxx master on Opensuse Tumbleweed fresh install:
1817742,2019-08-23 13:24:34 UTC,See also: https://github.com/mixxxdj/mixxx/pull/2201
1817742,2019-08-10 19:34:36 UTC,"This is not an SCons, but a Python issue!"
1817742,2019-02-28 15:24:47 UTC,"It might also be a combination of SCons and the Python version. I once had a similar issue in Fedora 27 that required the installation of an older SCons version:
https://bugs.launchpad.net/mixxx/+bug/1732272"
1817742,2019-08-23 14:19:35 UTC,Looks like Jan was able to fix this bug!!
1817742,2019-04-08 21:28:58 UTC,Try to use a scons version of 2.5.x. This worked for me...
1817742,2019-02-28 14:40:41 UTC,Interesting: I just downgraded scons from 3.0.1-r100 to 2.5.1. Now the master branch just compiles fine and the programm executes just normal. Really strange. Seems to be a scons bug...
1817742,2019-02-27 14:02:56 UTC,"Sorry it seems that you meant ""/usr/include/qt5""."
1817742,2019-02-28 14:06:36 UTC,I deleted all scons dbs and directories as well as upgrading my distribution to the most current version. Currently I'm using QTcore 5.11.3-r2.
1817742,2019-02-28 08:31:18 UTC,just to make sure: you updated all dependencies and qt before running scons?
1817742,2019-02-27 13:45:55 UTC,I'm using Sabayon Linux which is a Gentoo derivative...
1817742,2019-02-27 13:39:42 UTC,"I tried with scons -c and scons qtdir=/usr/lib64/qt5/
however the problem still remains. I wasn't able to find the mentioned header file ""ui_dlganalysis.h"" on the whole system using find even though I'm running a KDE. What KDE packet provides this header-file? Maybe I just didn't install it!?"
1817742,2019-02-27 00:46:51 UTC,"That header file should be autogenerated by Qt's uic tool. This has come up for a few different people lately and it's not clear why. There may be a bug in the build system. Try explicitly specifying the qtdir argument for scons. Also try running ""scons -c""."
1817742,2019-02-28 14:09:03 UTC,If this header file isn't generated automatically while the build process is taking place; is there a way to manually generate this header file?
1817743,2019-06-03 20:49:10 UTC,I think this is still happening due to some missing dependencies.  This warning doesn't really affect anything
1817743,2019-02-26 15:29:35 UTC,https://bugzilla.redhat.com/show_bug.cgi?id=1658141
1817747,2019-10-05 17:50:21 UTC,"We have the same problem in Evergreen 3.3.2. I think the problem is in Author:
I am able to find matching record by
- Title + ISBN
- Title
- ISBN"
1817754,2020-02-25 21:41:18 UTC,"Yes please! I just had to tell a patron that partial payments were not possible with a credit card, and nobody was happy about that!"
1817761,2019-09-02 19:17:15 UTC,It looks like you have some clashing dependencies: https://github.com/urllib3/urllib3/issues/1456
1817762,2019-03-06 16:32:42 UTC,submitted review: https://review.openstack.org/#/c/639401
1817762,2019-11-26 19:26:03 UTC,"Change abandoned by Oleh Huzei (<email address hidden>) on branch: master
Review: https://review.opendev.org/696167"
1817763,2019-07-16 12:44:30 UTC,When is the last time that this behaviour has been observed?
1817763,2019-08-13 16:55:55 UTC,Lab installer was updated to send gard when floating ip issue is encountered.
1817763,2019-07-19 14:50:08 UTC,"Based on review with Matt Peters (networking TL) and Yang Liu (reporter), it was concluded that this is an intermittent lab issue in the WR labs which results in loss of connectivity to the floating IP. As a workaround, the lab installer sends a garp after the initial controller install to workaround this."
1817763,2019-05-24 15:08:38 UTC,This issue is seen consistently in IP 1-4 lab. Install of IP 1-4 fails by Floating IP address not reachable. Although the user can ping it and nslookup shows the IP address assigned to the right node.
1817763,2019-05-24 17:01:59 UTC,"That issue in IP 1-4 is a lab configuration issue, and not related to the original issue in this bug report."
1817763,2019-02-27 18:31:43 UTC,Marking as release gating; medium priority as the timeout is intermittent. This should be used to make the container download more robust and less dependent on the external registry.
1817763,2019-02-27 21:11:34 UTC,Update on this LP:  Actual issue is network conenctivity.  Title of LP is updated.
1817764,2019-02-27 06:35:42 UTC,I did that to make sure that we look at it. Retargetet to Build 21.
1817764,2019-02-26 17:44:15 UTC,Screenshots
1817764,2019-02-26 18:13:22 UTC,"I checked the replay, not entirely but I found the issue."
1817764,2019-02-26 19:06:52 UTC,This one can be easily reproduced:
1817764,2019-02-26 21:57:27 UTC,From my point of view the question is how hard is it to fix this and is it worth having it in b20.
1817764,2019-02-26 22:59:15 UTC,I wonder why this is targeted to build 20 anyhow...
1817764,2019-09-16 08:22:05 UTC,Migrated to https://github.com/widelands/widelands/issues/3390
1817774,2019-09-25 23:54:26 UTC,Point releases are made from the related branch. For example 2.6.9 release comes from the 2.6 branch.
1817774,2019-09-26 21:02:01 UTC,"Hi Tim, thanks for the explanation, this helps."
1817774,2020-01-21 17:56:20 UTC,We're hitting this too with juju 2.7.1
1817774,2020-01-21 18:15:30 UTC,"Can you please file a new bug and post with the config noted above? The fix
for this was landed and distributed and if we're hitting it again we'll
have to diagnose anew as we removed the custom config."
1817774,2019-09-25 21:49:32 UTC,"I'm not sure what branch the juju snap is coming from; is it master?  It seems master's last change was March 21st, whereas this change was merged to the develop branch and has yet to make it over to the master branch, as far as I can tell."
1817774,2020-01-22 08:38:52 UTC,"Sorry, didn't delete from all the right places..."
1817774,2020-01-22 09:08:05 UTC,"I just pushed an update to:
lp:~juju-qa-bot/+git/juju-2-6-edge-tracking-snap
lp:~juju-qa-bot/+git/juju-2-7-edge-tracking-snap
lp:~juju-qa-bot/+git/juju-lp-snap
lp:~juju-qa-bot/+git/juju-edge-snap"
1817774,2020-01-22 09:53:28 UTC,"I also confirmed for 2.7/edge and latest/edge. Those will still be waiting for us to do a final release (2.7.2, etc) before it is in a stable release."
1817774,2020-01-22 09:45:18 UTC,"I confirmed that at least 2.6/edge has been updated:
$ snap info juju
...
installed:       2.6.11+2.6-b96e122                   (10408) 75MB classic
$ sudo snap run --shell juju
# cat /snap/juju/current/meta/hooks/configure
#!/bin/bash"
1817774,2020-01-22 08:28:23 UTC,"We don't add the file any more, but if the file is there, we don't delete it."
1817774,2019-03-25 13:24:33 UTC,"Are you able to test the 2.6 edge snap and make sure it doesn't cause
problems? I think Rick wanted to wait until it had some real world exposure
before we change the stable snap branch."
1817774,2019-07-23 21:30:15 UTC,"I just hit this on one of the machines we use for charm testing, after freshly redeploying the host system today with Bionic.  Was at a loss as to why our inotify changes were being ""ignored""."
1817774,2019-03-25 11:32:32 UTC,Rick - would it be possible to backport this fix back to 2.5.x as well?
1817774,2019-02-28 09:11:08 UTC,I've put up a PR here: https://github.com/juju/juju/pull/9805
1817774,2019-02-28 08:43:35 UTC,"If lxd is always adding a reasonable value, we can just remove it from our
configuration. We only need it when Juju interacts with LXD. We added it to
Juju a long time ago because LXD was by-default-installed on all machines,
and they didn't want to tweak the value unless people were actually using
LXD."
1817774,2019-02-28 08:15:06 UTC,"Thanks, the fact that the client is installed makes sense now. I appreciate the analysis that helped me look and note that lxd added that sysctl file in Apr 2017 and we had added this to the snap setup in Feb 2017. I think it's just that we originally needed that config and set some default and lxd later set a larger default that we missed was added and would negate the need for Juju to set this when using the client."
1817774,2019-02-27 19:15:48 UTC,"Hi both,"
1817774,2019-02-27 16:18:18 UTC,"Just to clarify here, turned out the piece of code I pointed to initially has nothing to do with setting up lxd host, but rather setting up juju-client side host while building the snap.
Lxd host is being set up with just default parameters."
1817774,2019-02-27 15:57:37 UTC,Thanks Ed. I reviewed how this is setup and we had done some investigation around this in the past due to the localhost provider where you're more apt to run more lxd containers. During that investigation we followed the official LXD guidelines for running it as scale:
1817774,2019-02-27 14:29:17 UTC,This was creating LXDs on a VM with Juju targetting GCE.  Thanks
1817774,2019-02-27 07:15:25 UTC,Can you help clarify that this is a lxd provider based deploy or running lxd containers on another provider such as maas/openstack please?
1817775,2019-09-03 07:44:49 UTC,@rharding thank you for update. Will also juju export-bundle support CMR from the start?
1817775,2019-09-02 11:59:47 UTC,"This is upcoming in the 2.7 release of Juju. We can demonstrate it with the
edge snap with a scheduled release of October for the 19.10 cycle. It's
feature complete there, but not yet released in a stable Juju release."
1817775,2019-09-01 16:29:36 UTC,"We have CMR requirement from the field, to have logging, monitoring and alerting in a separate model for multiple k8s clusters. I cannot find any information about offer in bundles so I assume this is still not possible. Any details about the progress?"
1817775,2019-03-28 20:46:39 UTC,Use case:
1817775,2019-09-03 14:19:06 UTC,"Yes, so when you dump a bundle you'll get output that contains CMR specific
bits as well. You can see a really good idea of this from the PR in 2.7
here:"
1817775,2019-02-27 06:33:42 UTC,Bundles do not currently support cross model relations.
1817775,2019-02-27 06:11:12 UTC,"bundles are additive, so removing items from them won't remove those items
from your deployment. That behavior is expected. However, export-bundle
should definitely not generate a bundle that 'deploy' thinks is broken.
Traditionally bundles had to be self contained and define all applications
involved. Cross model changes that and you're referring to applications
that aren't available here."
1817775,2019-02-27 06:34:14 UTC,"Actually, any use cases you can contribute would help immensely."
1817779,2019-10-14 01:43:53 UTC,"Hi Drew,"
1817779,2019-02-26 19:25:35 UTC,"so, some conclusions from testing."
1817779,2019-12-13 04:17:21 UTC,[Expired for juju because there has been no activity for 60 days.]
1817779,2019-02-26 19:08:13 UTC,"Theory proven, variables previously user-set are confusingly showing 'source: default' in juju config output:"
1817779,2019-02-26 18:58:02 UTC,"To be clear, after deploying the bundle when it says ""setting application option X to $setting"", when we check the charm config, it still shows source: default for those options on the charm, even though the bundle deploy appeared to tell the operator it was explicitly user-setting it.  It is misleading/confusing."
1817780,2019-02-26 19:31:07 UTC,It looks like this also affects the guide in master [0].
1817780,2019-05-20 18:38:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660193"
1817780,2019-06-08 07:00:48 UTC,"Reviewed:  https://review.opendev.org/660193
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=bceab5871f4f6e1b65b6fdc69f701730b948d19b
Submitter: Zuul
Branch:    master"
1817780,2019-09-27 09:10:53 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1817782,2019-08-28 20:35:45 UTC,"Reviewed:  https://review.opendev.org/677915
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=0eb4fc518ef40faea466b0e23ae73fe74a9fd79d
Submitter: Zuul
Branch:    stable/stein"
1817782,2019-08-30 18:11:59 UTC,"Reviewed:  https://review.opendev.org/679183
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=9c9e797d07f64d4841ecb695d177c5e0c7d8266b
Submitter: Zuul
Branch:    stable/stein"
1817782,2020-03-25 14:33:10 UTC,This issue was fixed in the openstack/python-cinderclient 4.2.2 release.
1817782,2019-02-26 19:35:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/639422"
1817782,2019-04-02 16:51:51 UTC,"Reviewed:  https://review.openstack.org/639422
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=a39805c6f45baf94c0d14da3ae775ee204a267ee
Submitter: Zuul
Branch:    master"
1817782,2019-04-02 18:10:57 UTC,Fixed for cinderclient in https://review.openstack.org/#/c/649357/
1817782,2019-04-26 03:16:17 UTC,"Reviewed:  https://review.opendev.org/649357
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=0707191d43396026a6ddd18213b06e1b26d94e9e
Submitter: Zuul
Branch:    master"
1817782,2019-08-22 07:11:10 UTC,"In stein stable branch, UnicodeError is popping out in completion_cache when username has special characters like flügel. We need to cherry pick the fix to stein branch as well."
1817782,2019-08-22 07:12:09 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/677915"
1817782,2019-08-22 23:26:23 UTC,This issue was fixed in the openstack/python-cinderclient 4.3.0 release.
1817782,2019-08-29 05:11:27 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/679183"
1817784,2019-04-02 10:29:42 UTC,This bug was fixed in the package linux - 4.18.0-17.18
1817784,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1817784,2019-03-20 15:51:12 UTC,"Sorry, I'm unable to verify this for xenial. I submitted it as an SRU back to 4.4 because it had already landed in the stable queue for 4.4, and is a trivial change[*]. I think we'd need a system that either uses mvsas or aix94xx to actually exercise this libsas code on 4.4."
1817784,2019-03-19 18:51:02 UTC,cosmic verification:
1817784,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1817784,2019-03-15 23:31:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1817784,2019-03-15 20:04:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1817784,2019-03-15 23:37:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1817785,2021-01-27 14:50:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817785,2021-01-28 22:06:33 UTC,"This is affecting me in a fresh Ubuntu 18.04 installation. Thank's for the temporary solution, @Ernst."
1817793,2019-02-26 21:38:22 UTC,apport information
1817793,2019-02-26 21:38:31 UTC,apport information
1817793,2019-02-26 21:38:33 UTC,apport information
1817793,2019-02-26 21:38:28 UTC,apport information
1817793,2019-02-26 21:38:27 UTC,apport information
1817793,2019-02-26 21:38:25 UTC,apport information
1817793,2019-02-26 21:38:25 UTC,apport information
1817793,2019-02-26 21:38:24 UTC,apport information
1817793,2019-02-26 21:38:21 UTC,apport information
1817793,2019-02-26 21:38:20 UTC,apport information
1817793,2019-02-26 21:38:19 UTC,apport information
1817793,2019-02-26 21:38:18 UTC,apport information
1817793,2019-02-26 21:38:16 UTC,apport information
1817793,2019-02-26 21:38:15 UTC,apport information
1817793,2019-02-26 21:38:13 UTC,apport information
1817793,2019-02-26 21:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817806,2019-09-19 14:54:32 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1817811,2020-04-13 13:33:27 UTC,A little more detail.
1817811,2020-04-12 21:50:34 UTC,But how you are dealing with non admin tempest test cases that needs to be executed as non admin users? are they passing as well??
1817811,2019-09-06 02:00:06 UTC,"We handle this by creating a qa domain and running our tests with preprovision creds that we create the project with uuid for the test run. We give all creds admin roles for the test even if they are for the admin,primary or alt cred groups. When the test are done we delete the project and roles assignments.  Let me know if this helps and if you want to talk more about this IRC bigdogstl."
1817811,2019-08-29 01:25:37 UTC,see this bug and comment if you fell that this will help this bug. https://bugs.launchpad.net/tempest/+bug/1738076
1817813,2019-02-27 02:08:11 UTC,subscribed ~field-medium
1817813,2019-02-27 08:23:19 UTC,"Hi Wouter,"
1817818,2019-02-27 03:29:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/639486"
1817818,2019-02-28 19:21:47 UTC,"Reviewed:  https://review.openstack.org/639486
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=75f604ed778f5b3b2a8089cbcbb65e722d05d8c0
Submitter: Zuul
Branch:    stable/queens"
1817818,2019-06-21 15:26:10 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1817821,2019-02-28 02:15:06 UTC,I don't know that we'll actually fix this given it's a proxy API but I'll mark as triaged/low for now.
1817822,2019-02-27 05:03:48 UTC,I actually wonder if we can extract this from mailman via the domains it knows about and use those rather than setting it in a charm option.
1817823,2020-04-25 04:18:19 UTC,[Expired for tempest because there has been no activity for 60 days.]
1817823,2020-01-24 16:28:11 UTC,"Is this still an issue? If so, could you, please, provide more information such as links to specific code or related changes, tracebacks, etc?"
1817823,2020-02-24 09:26:54 UTC,I'm gonna mark this as Incomplete until more info is provided.
1817825,2019-02-27 07:16:53 UTC,"You need to use the MPI compilers, please see the documentation."
1817825,2019-02-28 04:54:16 UTC,"Unfortunately, ```FC=mpifort``` didn't solve the problem:
/usr/local/bin/mpifort -c -DMPI -I/usr/ports/science/siesta/work/siesta-4.1-b4/Obj/../Src/MPI -I/usr/ports/science/siesta/work/siesta-4.1-b4/Src/fdf      -I../ -DMPI -I/usr/ports/science/siesta/work/siesta-4.1-b4/Obj/../Src/MPI  /usr/ports/science/siesta/work/siesta-4.1-b4/Src/fdf/fdf.F90
/usr/ports/science/siesta/work/siesta-4.1-b4/Src/fdf/fdf.F90:507:10:"
1817825,2019-02-28 06:06:00 UTC,Did you do a make clean?
1817825,2019-02-28 06:28:53 UTC,"> Did you do a make clean?
"
1817825,2019-02-28 07:11:32 UTC,"> FreeBSD port always builds from scratch.
"
1817825,2019-02-28 07:51:19 UTC,"> on FreeBSD, I presume does NOT run:
> make clean ; make
"
1817825,2019-10-22 04:17:26 UTC,[Expired for Siesta because there has been no activity for 60 days.]
1817833,2019-11-22 03:38:40 UTC,"Note that during my recreate, I did not have any instances or old evacuations or unconfirmed migrations related to the compute service I deleted."
1817833,2019-11-22 04:13:30 UTC,"Another note for my QUEENS recreate, after restarting nova-compute process, I tried to boot an instance and it went to ERROR state with:"
1817833,2019-11-23 01:19:56 UTC,"The more I re-read the bug report in comment 0, the more I don't understand how the bug report could be correct. I also couldn't reproduce the reported behavior on stable/queens."
1817833,2019-11-25 15:41:36 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/695932"
1817833,2019-12-09 22:21:19 UTC,"Reviewed:  https://review.opendev.org/695932
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b18e42d20bd7d341e713292bdb179ae8e5530d33
Submitter: Zuul
Branch:    stable/stein"
1817833,2019-12-18 15:03:36 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/699698"
1817833,2019-12-13 04:13:52 UTC,"Reviewed:  https://review.opendev.org/698106
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6eda7409fff75449c97843b2d6ead0b3267a1099
Submitter: Zuul
Branch:    stable/rocky"
1817833,2019-12-18 03:45:41 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/699538"
1817833,2019-11-22 03:36:27 UTC,FWIW I just tried the recreate steps in QUEENS and did not run into the reported error:
1817833,2020-02-03 18:27:41 UTC,"Reviewed:  https://review.opendev.org/699698
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=23ca5e5ac9b90ff45074ae9171f63ca060ebcedd
Submitter: Zuul
Branch:    stable/queens"
1817833,2019-12-09 23:13:17 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/698106"
1817833,2019-10-25 13:27:36 UTC,Related mailing list discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007135.html
1817833,2019-11-14 15:38:01 UTC,Post-PTG discussion notes on this:
1817833,2019-02-28 02:12:12 UTC,Which release are you testing this against? master (stein)?
1817833,2019-08-22 20:08:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678100"
1817833,2019-03-07 15:40:51 UTC,"I found problems in Pike (our product based on Pike), and also affect master branch."
1817833,2019-05-03 17:03:55 UTC,The docs explicitly say that the nova-compute service needs to be stopped before you delete the resource:
1817833,2019-05-03 17:10:21 UTC,"Having said that, I see something missed in the fix for bug 1756179 here:"
1817833,2019-03-08 01:50:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641899"
1817833,2019-06-05 20:44:31 UTC,Bug 1829479 might be related somehow.
1817833,2019-06-06 18:03:07 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/663737"
1817833,2019-06-14 21:53:13 UTC,"Reviewed:  https://review.opendev.org/663737
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2629d65fbc15d8698f98117e0d6072810f70da03
Submitter: Zuul
Branch:    master"
1817833,2019-05-03 18:03:27 UTC,Ah there is a bug for the issue I mentioned in comment 5:
1817839,2019-02-27 07:18:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639586"
1817846,2019-05-28 04:17:53 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1817846,2019-03-04 15:58:41 UTC,"Could you provide a test binary (and the QEMU command line to run it) that demonstrates the bug, please?"
1817846,2019-03-28 14:42:54 UTC,Marking bug as incomplete -- we can't investigate without a test case.
1817872,2020-06-02 19:52:32 UTC,Can You explain how it's different than https://bugs.launchpad.net/neutron/+bug/1830014 ?
1817872,2020-06-02 15:52:23 UTC,"The 'diagnostics' is basically same to this, so I will add the ""router"" diagnostics as a first step."
1817872,2020-03-19 15:24:14 UTC,Do You still plan to work on this? Or maybe should we close this one due to lack of activity?
1817872,2020-09-17 19:45:22 UTC,"Ping @LIU. If You are still interested in doing that, please reply to my last question in c#4.
If there will be no any info about that for next few weeks, I'm going to close this RFE."
1817872,2019-11-29 08:53:00 UTC,"Do we need this new RFE? There is, as You mentioned already Blueprint related to that topic. Spec for it https://review.opendev.org/#/c/308973/ is already merged long time ago.
So IMO if You are interested in implementing it, You can continue work on this BPs and according to merged spec."
1817872,2021-02-18 15:27:16 UTC,No updates since long time. I'm closing this RFE for now.
1817881,2019-08-09 16:04:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675654"
1817881,2019-10-11 12:12:48 UTC,"Hi Liu,"
1817881,2020-05-29 15:01:48 UTC,"On the last drivers meeting we decided to approve this RFE.
However we would like to treat it as ""next generation metering"" in Neutron with potentially deprecation of old metering agent and we want to discuss details about that during the Virtual PTG."
1817881,2020-03-26 21:41:22 UTC,"Hi Liu,"
1817881,2019-07-26 04:54:19 UTC,"@Miguel Lavalle
We discussed this once in drivers meeting.
http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-03-29-14.00.log.html
So basicly we have a basic consensus is adding a new l3 agent extension. It is fine to me.
We need to retrigger another discuss in drivers meeting?"
1817881,2019-05-11 00:23:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658511"
1817881,2020-03-13 08:51:00 UTC,"Hi Liu,"
1817881,2019-03-08 15:08:16 UTC,@LIU
1817881,2019-03-08 02:27:06 UTC,"OK, let's see what the drivers team says"
1817881,2019-03-06 13:17:24 UTC,"@Miguel, sorry for the late reply.
Yes, it is tc counters.
We do not need new service plugin or REST api, current floating IP qos implementation is enough.
As I had written in the bug description, the metering agent is a bit heavy for the cloud deployment. Users need to add extra actions to enable the metering functionality. For this proposal here, I would like to add a L3 agent extension or refactor to achieve the L3 IP metering. Some new config settings will be needed for this, such as, how long to retrieve the data, how to store the data, how to report the data, etc."
1817881,2019-03-01 01:57:15 UTC,What you are saying is:
1817881,2019-03-20 14:57:17 UTC,"Hi YAMAMOTO Takashi,
Yes, the config will be needed to enable the l3 agent 'self service' metering.
For the REST API, I can image some new idea, for instance:
1. disable one IP's metering.
2. clean one IP's metering data.
3. change one IP's metering frequency (interval).
4. change one IP's report interval.
But yes, this will become more complicated. It is clear to find without these API changes, the IP's metering will be triggered by the fixed settings in l3_agent.ini. But we can let it be the first step of ""self service"" metering."
1817883,2019-03-02 01:40:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817885,2019-03-13 23:49:25 UTC,"Hi
Fedora 30 does not work on"
1817885,2019-03-14 00:16:35 UTC,"cut.patch working
Daniel Agocs thank you :)"
1817885,2019-04-16 14:03:07 UTC,"Same problem on Arch Linux with Python 3.7.3.
The previous fix solves the problem."
1817886,2021-02-18 15:28:07 UTC,No updates since long time. I'm closing this RFE for now.
1817886,2020-09-17 19:46:14 UTC,"Ping @LIU. If You are still interested in doing that, please reply to my last question in c#5.
If there will be no any info about that for next few weeks, I'm going to close this RFE."
1817886,2020-06-02 19:51:39 UTC,Can You write some more details about how You want to implement that in Neutron? Will it be configurable by API or config files? What resources will be limited?
1817886,2020-06-02 15:43:57 UTC,"For now, I want to add such ability for Neutron only. I'm going to upload a spec to describe the detail."
1817886,2019-03-08 01:22:30 UTC,"""This RFE propose to add some limitation of neutron to avoid user creating resource beyond the cluster capacity"". How do you express those limits? maximum number of ports? maximum number of networks? How is this going to play with other openstack projects, Nova for example?"
1817886,2019-12-06 10:44:10 UTC,"I think that problem described here isn't related only to Neutron and also isn't addressed by other projects too.
Maybe this should be discussed with whole community e.g. on ML?"
1817886,2020-03-13 08:56:18 UTC,"Liu, do You still have plans to work on this? Will You bring discussion about that to the whole OpenStack community? Or should we handle that only for Neutron?"
1817891,2019-04-03 04:54:28 UTC,"Hello,"
1817891,2019-06-03 04:17:18 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1817897,2019-02-27 18:19:43 UTC,"As far as I can tell, the BIOS is able to see the fingerprint reader -- I just booted into the BIOS and told it to reset the fingerprint data, and it said that it had done so successfully -- so this appears to be a Linux-specific issue."
1817897,2019-03-01 22:41:59 UTC,"I don't have an explanation of the behavior of pam-auth-update, but Debian bug #923362 has also just been filed regarding pam_systemd inexplicably getting disabled, and may be related."
1817897,2019-03-01 23:17:18 UTC,https://forums.lenovo.com/t5/Linux-Discussion/X1-Carbon-2018-X1C6-FingerPrint-Reader-under-Linux-Ubuntu-18-04/td-p/4255423 seems to discuss that topic as well
1817897,2019-03-01 16:10:23 UTC,I called Lenovo and asked and the support rep I spoke with said that the X1 Carbon's fingerprint reader isn't supported in Linux yet.
1817897,2019-02-27 17:49:58 UTC,"I have a new Thinkpad X1 Carbon 6th generation. I can see the fingerprint reader right next to the trackpad, and the specs say that it has one, but I don't see it showing up in the output of lspci or lsusb. Maybe I'm missing it? Maybe it's not supported? Or maybe there's a hardware issue? I'm not sure how to tell."
1817897,2019-02-27 14:08:17 UTC,"So, whether or not I needed to run pam-auth-update, doing so and enabling fingerprint authentication there should not cause GDM to break, nor should the other weird behavior I described above be happening."
1817897,2019-02-27 12:26:16 UTC,"Thanks for your bug report, what do you need pam-auth-update? What are you trying to configure? Enabling log-in with fingerprint shouldn't requiring having to fiddle with pam tools on a command line if that's what you are trying to enable"
1817897,2019-02-27 11:43:53 UTC,"Actually, it's even weirder than that."
1817897,2019-02-27 16:40:57 UTC,You are right that pam shouldn't lead to gdm not working in any case. Knowing the context help to define the priority of the issue though.
1817902,2019-11-13 21:26:36 UTC,"I assume this is the notorious ""RAID size calculation"" bug I just fixed."
1817902,2019-02-27 12:32:26 UTC,"There is a backtrace in my screen, and I don't see it anywhere in /var/log/installer"
1817902,2019-02-27 12:35:33 UTC,This is the partition layout I had
1817902,2019-02-27 12:40:23 UTC,I believe a rounding error caused this. I picked the exact strings/sizes that the installer told me was the maximum size for each partition.
1817904,2019-11-13 21:26:43 UTC,"I assume this is the notorious ""RAID size calculation"" bug I just fixed."
1817904,2019-02-27 14:09:56 UTC,With the traditional installer this partition layout works perfectly
1817904,2019-02-27 13:06:25 UTC,"This might be related, or even be the same, as bug #1817902"
1817904,2019-02-27 13:01:42 UTC,"Partitioning layout, and resulting error."
1817905,2019-09-10 20:42:14 UTC,Confirmed that this still doesn't show in 3.3.3.
1817907,2020-03-11 00:51:14 UTC,Fix PRd: https://github.com/snapcore/snapcraft/pull/2968
1817907,2020-03-10 22:22:38 UTC,"James I hit this issue too and Chris Patterson pointed out this will happen if you specify a source-commit AND source-depth. Once I removed the source-depth line, source-commit worked just fine."
1817912,2019-02-27 14:07:51 UTC,apport information
1817912,2019-02-27 14:07:52 UTC,apport information
1817912,2019-02-27 14:07:49 UTC,apport information
1817912,2019-02-27 14:07:54 UTC,apport information
1817912,2019-02-27 14:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817912,2019-02-27 14:07:57 UTC,apport information
1817918,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1817918,2019-03-15 20:04:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1817918,2019-03-18 15:51:40 UTC,"Tested kernel in -proposed, version 4.4.0-144-generic (in Xenial). Problem does not reproduce anymore."
1817918,2019-02-27 19:22:12 UTC,SRU request sent to the kernel team mailing list: https://lists.ubuntu.com/archives/kernel-team/2019-February/098872.html
1817922,2019-03-10 15:04:33 UTC,Same problem seen with light-locker 1.8.0 on Lubuntu 18.04 LTS and Xubuntu 18.10
1817922,2019-03-10 15:05:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817922,2019-03-11 17:04:17 UTC,After some extensive testing I have further information to report that may help solve this issue.
1817922,2019-04-29 23:31:36 UTC,"Of note this bug may eventually be overtaken by events. I installed Lubuntu 19.04, which does not use light-locker and it works fine."
1817922,2019-09-21 17:28:06 UTC,This information might be useful for affected users: https://fitzcarraldoblog.wordpress.com/2018/07/08/getting-the-lock-screen-to-work-reliably-when-resuming-from-suspension-in-a-single-seat-multi-user-lubuntu-18-04-installation/
1817925,2019-03-04 18:21:05 UTC,Confirmed on the PINES servers.
1817928,2019-02-28 08:15:19 UTC,"Hi, are you running as root? Remote user is root or using become in ansible?"
1817928,2019-02-28 16:47:40 UTC,"Eduardo, I deployed as issued all of the Kolla commands as root."
1817928,2019-02-28 18:55:06 UTC,"Eduardo, I deployed again as user: ubuntu, failed here with the same scenario."
1817928,2019-02-28 18:57:28 UTC,Output as ubuntu user: https://pastebin.com/spH8YUS2
1817930,2019-04-23 23:55:28 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1817930,2019-06-23 04:19:09 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1817932,2019-04-05 14:46:14 UTC,New installer built with version 0.3.0.  Can be downloaded here:
1817932,2019-04-05 20:47:16 UTC,I have used this to circumvent the ERROR causing it to not even try printing the labels but I get several errors and the print fails. Works fine in the Printer Settings tester but not on the label printing page.
1817932,2019-04-15 20:57:34 UTC,"Thanks, Christopher.  The settings do need to be created -- some as workstation settings, some should be stored locally.  I propose we open a separate LP for that.  In my case, I was still able to print to a Dymo 330, regardless of the issues with the settings."
1817932,2019-05-08 17:56:15 UTC,"Rebased branch to master and pushed another commit adding dependency fetcher support for ""mac""."
1817932,2019-05-08 18:04:59 UTC,Pushed one more commit with instructions for setting up Hatch on the Mac (INSTALL.adoc)
1817932,2019-04-04 22:02:14 UTC,My branch noted above has additions from Kyle with my sign-offs.  I also pushed another commit to tidy some of the installer bits/docs a bit more.
1817932,2019-03-13 19:59:06 UTC,Getting started with a Linux script to fetch openjdk/openjfx/json Linux/Windows dependencies and put them in a well-known location within the Hatch directory.  Also updates the hatch.sh and hatch.bat files to reference the new file paths.
1817932,2019-03-06 16:13:42 UTC,Bundling Java and JavaFX sounds like a fine idea. +1
1817932,2019-02-27 18:55:41 UTC,"Thanks, Jason."
1817932,2019-02-27 17:48:07 UTC,"Given how many lines of hatch.bat are just for cycling through all of the possible paths that Java may be hiding in and all of that nsi code that does the same, I'm 1000% for including everything you need in a single installer. (Especially if we can narrow down which jars we actually need vs ""everything."")"
1817932,2019-02-27 17:07:59 UTC,The Windows builds I tested for reference:
1817932,2019-02-27 16:57:57 UTC,"This is how I tested in Linux.  The same general procedures apply to Windows, assuming you fetch Windows binaries instead, of course, and manually install the JSON jar file."
1817932,2019-03-06 18:00:01 UTC,You've got my +1!
1817934,2019-02-28 23:37:50 UTC,"* nova.conf (except generic auth specific sections like keystone, glance, neutron, messaging):"
1817934,2019-02-28 14:55:34 UTC,Hi Malte
1817934,2019-11-25 11:28:01 UTC,Any progress on this? I'm hitting exactly the same problem when using BTRFS:
1817934,2019-12-03 17:48:33 UTC,"We are currently run a slightly patched version of nova-lxd. The attached patch is sufficient to get containers with ephemeral disk on ZFS. A similar approach might work for brtfs, too."
1817936,2019-08-08 11:47:41 UTC,"The probe connection action before going to time_wait state.
Probe connection
controller                                        service                     endpoint                            Chain                      TCP FLAG                           SEQ          ACK
10.10.10.3:50538  ------------------------------->    172.16.192.101:9292     raw:OUTPUT:policy:4               SYN                       2707980036        0
10.10.10.3:50538  <-------------------------------    172.16.192.101:9292    raw:PREROUTING:policy:4     SYN ACK                 1599414185    2707980037
10.10.10.3:50538  ------------------------------->    172.16.192.101:9292    filter:OUTPUT:rule:1                 ACK                       2707980037    1599414186
10.10.10.3:50538  ------------------------------->    172.16.192.101:9292     raw:OUTPUT:policy:4             FIN ACK                 2707980037    1599414186
10.10.10.3:50538  <-------------------------------    172.16.192.101:9292    raw:PREROUTING:policy:4       ACK                      1599414186    2707980038
10.10.10.3:50538  <-------------------------------    172.16.192.101:9292    raw:PREROUTING:policy:4      FIN ACK                1599414186    2707980038
10.10.10.3:50538  ------------------------------->    172.16.192.101:9292     raw:OUTPUT:policy:4               ACK                      2707980038    1599414187"
1817936,2019-10-03 15:24:20 UTC,The following testing was done by Elio Martinez with an stx.2.0 designer build with this fix
1817936,2019-08-06 00:58:36 UTC,"from this log , The root cause is found.
probe  was in TIME_WAIT connection(10.10.10.3:50538->172.16.192.101:9292)
client send a new connection 10.10.10.3:50538->10.109.43.235:9292, after NAT the output SYN package will be
10.10.10.3:24479->172.16.192.101:9292. the SYN ACK 172.16.192.101:9292->10.10.10.3:24479 will be modified by Mangle to 172.16.192.101:9292->10.10.10.3:50538, but this socket was still in TIME_WAIT state, will be sent INVALID and then drop."
1817936,2019-08-27 18:48:05 UTC,"Reviewed:  https://review.opendev.org/674719
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=171c43dca8b419c5ac579e289002ff4fdb1aee3f
Submitter: Zuul
Branch:    master"
1817936,2019-08-05 14:45:16 UTC,"Change abandoned by Austin Sun (<email address hidden>) on branch: master
Review: https://review.opendev.org/672387"
1817936,2019-08-02 12:14:20 UTC,"attachment is long trace for monitoring 9292 port , there are a lot of ports out of ip_local_port_range(49217  65500)
for example: No 233525, the port is 10325, 10.10.10.3:10325->172.16.192.130:9292"
1817936,2019-08-04 14:13:18 UTC,"when issue occured.
in echo-glance-api.cap (tcpdump -i any -vv port 9292 -w echo-glance-api.cap)
No468: 10.10.10.3:13550 ---> 172.16.192.99:9292
in echo-glance-api.con (conntrack -o timestamp -E -p tcp --dport 9292)
[1564902343.325301]         [NEW] tcp      6 120 SYN_SENT src=10.10.10.3 dst=10.98.65.211 sport=53720 dport=9292 [UNREPLIED] src=172.16.192.99 dst=10.10.10.3 sport=9292 dport=13550
[1564902343.325305]      [UPDATE] tcp      6 60 SYN_RECV src=10.10.10.3 dst=10.98.65.211 sport=53720 dport=9292 src=172.16.192.99 dst=10.10.10.3 sport=9292 dport=13550
The sport was changed from 53720 to 13550. it seems NAT change the port. will check netfliter code."
1817936,2019-08-06 00:49:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/674719"
1817936,2019-08-27 18:59:51 UTC,"Fix proposed to branch: r/stx.2.0
Review: https://review.opendev.org/678944"
1817936,2019-09-22 11:35:14 UTC,"Fix proposed to branch: r/stx.2.0
Review: https://review.opendev.org/683818"
1817936,2019-09-03 12:58:50 UTC,"change needs to be reverted, due to https://bugs.launchpad.net/starlingx/+bug/1841833"
1817936,2019-09-10 01:43:46 UTC,"once revert change merged, will submit a new change for another parameters net.ipv4_tcp_tw_resue=0."
1817936,2019-09-11 02:28:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/681363"
1817936,2019-09-16 17:33:52 UTC,"Reviewed:  https://review.opendev.org/681363
Committed: https://git.openstack.org/cgit/starlingx/config-files/commit/?id=fbc09b8db8a14fbf24976a0f7d8924af7a330f85
Submitter: Zuul
Branch:    master"
1817936,2019-09-19 17:02:34 UTC,"@Austin, the change has sufficient soak in master and sanity is green, please cherrypick to r/stx.2.0"
1817936,2019-09-19 17:04:52 UTC,"@Austin, when the change has sufficient soak in master and sanity is green, please cherrypick to r/stx.2.0"
1817936,2019-09-20 00:50:45 UTC,"Hi Ghada:
    The previous change was merged but sanity is green, so i think sanity did not cover some cases.  I will check with test team to check if they can perform some regression test after daily sanity is green"
1817936,2019-10-03 04:25:20 UTC,"Reviewed:  https://review.opendev.org/683818
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=457b4747e92255fa99340fa7cb1d7204873fb3c5
Submitter: Zuul
Branch:    r/stx.2.0"
1817936,2019-08-02 01:32:01 UTC,"from the attached tcpdump log.
@26151, there is a package 10.10.10.3:18794->172.16.192.89:9292 , but the port 18794 should not be valid, because 'net.ipv4.ip_local_port_range = 49216    61000', need checking where the packages comes from."
1817936,2019-09-03 09:06:04 UTC,"Change abandoned by Austin Sun (<email address hidden>) on branch: r/stx.2.0
Review: https://review.opendev.org/678944"
1817936,2019-07-31 14:53:27 UTC,"if remove glance-api readiness probe and livenessprobe , then test mentioned above run successfully w/o failure in 50000 times. it should be some conflict interfere between application with tcp probe."
1817936,2019-07-17 14:52:19 UTC,"Here is some finding , readiness or liveness deployment of nova-api-osapi or xxxx-api is using the tcp and port to check pod readiness and liveness
For example barbican-api readiness
readinessProbe:
          failureThreshold: 10
          periodSeconds: 10
          successThreshold: 1
          tcpSocket:
            port: 9311"
1817936,2019-07-30 09:04:06 UTC,"it seems curl command in centos is not controlled by net.ipv4.ip_local_port_range.
When I running curl command , the source port range is from 11728 to 65508 with tcpdump log."
1817936,2019-07-31 10:49:15 UTC,"although curl command is invalid test case, but for python test code.
import urllib
import datetime
for i in range(1,20000):
    now = datetime.datetime.now()
    print(""start %s at: %s"" % (i,now))
    try:
        response = urllib.urlopen(""http://glance-api.openstack.svc.cluster.local:9292"")
        print(response.read())
        response.close()
    except:
        now = datetime.datetime.now()
        print(""Error %s at: %s"" % (i,now))
        exit()
    now = datetime.datetime.now()
    print(""end %s at: %s"" % (i,now))"
1817936,2019-02-27 18:17:47 UTC,Marking as release gating until further investigation. medium priority.
1817936,2019-03-01 18:04:33 UTC,I have made some progress on the periodic message loss issue.
1817936,2019-03-13 16:34:04 UTC,"The connection fails only under specific conditions and is directly related to a conflict when setting up the NAT connection tracking information.  This issue occurs in about 1 in 500 connections and is only impacts that one connection, all other and subsequent connections are fine."
1817936,2019-06-07 08:22:15 UTC,"Bart, and Matt:
I have try reproduce this issue in virtual environment in latest version.
I run more than 10000 times the script Bart mentioned, but can not reproduce.
could you try latest version if the issue is there or not ?"
1817936,2019-06-10 15:03:39 UTC,This issue only occurs when the services (or test client) are co-located on the same host.  Can you confirm that your reproduction attempts were all localized to a single host?
1817936,2019-06-11 01:08:46 UTC,"Hi Matt:
    you mean run this in a AIO(All-in-One) Simplex setup ?"
1817936,2019-06-11 03:06:57 UTC,"I think you are right ,  in AIO Simplex setup ,the script stopped at
Request: 2083
06/11/19 03:03:48 523488226"
1817936,2019-03-13 16:35:27 UTC,"The statistics also show the ""invalid"" counts being begged every time the issue occurs."
1817936,2019-07-08 20:53:24 UTC,Assigning to Austin since he is actively working on this bug
1817936,2019-07-16 07:02:53 UTC,"in, kern_2019-07-15_15_04_50.log, from Line 24000 to 24001, a very weird:
Line 24000, mangle:cali-PREROUTING:rule:1 172.16.192.109:8774->10.10.10.3:33727
Line 24001, mangle:INPUT:policy:1 172.16.192.109:8774->10.10.10.3:53902"
1817936,2019-07-19 03:17:15 UTC,"in 1817936_iptrace.zip, kern_2019-07-15_15_04_50.log
Ln 23963, SPT=53902 , SYN Package from kernel, but it was not found in tcpdump package. tcpdump package only find source port =33727 sync package."
1817936,2019-07-23 06:37:08 UTC,"Some more tests are performed based on attached tcp_test.zip
Set-Up K8s with calico CNI On Ubuntu 18.04.1 LTS and CentOS Linux release 7.6.1810
'kubectl create ns policy-demo'
'kubectl apply -f tcp_echo.yaml'
and run test.sh in attached zip."
1817936,2019-07-23 08:52:40 UTC,"another interesting test was performed.  if using command
 ""curl --local-port 47250-67500 --connect-timeout 10  http://barbican-api.openstack.svc.cluster.local:9311"", then the issue is gone. it seems the port conflict in some case."
1817936,2019-07-23 16:02:04 UTC,"Changed the priority to High based on the outcome of discussions with PLs and TLs (Ghada, Brent, Frank). Numerous LPs have been reported over the past few months related to openstack commands intermittently failing.  Many of these look like message loss between openstack pods and could be due to this LP."
1817936,2019-07-23 23:59:26 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672387"
1817936,2019-07-08 05:28:24 UTC,"From, mytestnossh.cap15 tcpdump.  a very weird No 13523, it got a response from nova-api, but can not find any corresponding  request send from host in previous time."
1817944,2019-02-27 20:01:23 UTC,apport information
1817944,2019-02-27 20:01:25 UTC,apport information
1817944,2019-02-27 20:01:26 UTC,apport information
1817944,2019-02-27 20:01:28 UTC,apport information
1817944,2019-02-27 20:25:55 UTC,"For completeness, here the Xorg-log. It looks pretty similar to the log of that FreeDesktop bug 106017; that is trying for ages to get the display up. There it leads to heavy flicker, and here it leads to a fail."
1817944,2019-02-27 20:01:31 UTC,apport information
1817944,2019-02-27 20:21:53 UTC,"Nope, again.
After some 5 or 10 minutes of working, the screen began to look like the old TV-sets not being synchronized (diagonal coloured bars), and then it went away completely."
1817944,2019-02-27 20:01:21 UTC,apport information
1817944,2019-02-27 20:01:29 UTC,apport information
1817944,2019-02-27 20:01:20 UTC,apport information
1817944,2019-02-27 20:01:13 UTC,apport information
1817944,2019-02-27 20:01:18 UTC,apport information
1817944,2019-02-27 20:01:17 UTC,apport information
1817944,2019-02-27 20:01:16 UTC,apport information
1817944,2019-02-27 20:01:15 UTC,apport information
1817944,2019-02-27 20:01:14 UTC,apport information
1817944,2019-02-27 19:14:32 UTC,"Is it possible to remove a bug report, please?
I very much do hope so. Reason: I had bought a new cable mini-DP to HDMI (deleyCon), and found it also not working when booting to W10. Just rushed out and bought another one, another brand, and it works."
1817944,2019-02-27 18:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1817944,2019-02-27 20:01:19 UTC,apport information
1817953,2019-03-26 06:48:16 UTC,"Note that this issue does not happen in the master branch (train) and stable/stein branch.
http://paste.openstack.org/show/748363/"
1817953,2019-04-12 23:31:47 UTC,This issue was fixed in the openstack/neutron 12.0.6 release.
1817953,2019-04-12 23:32:09 UTC,This issue was fixed in the openstack/neutron 13.0.3 release.
1817953,2019-04-09 10:29:14 UTC,"Reviewed:  https://review.openstack.org/650955
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=44d34170ccc439f433697b2117d0251530e5d508
Submitter: Zuul
Branch:    stable/queens"
1817953,2019-04-26 16:46:59 UTC,This issue was fixed in the openstack/oslo.policy 2.2.0 release.
1817953,2019-04-08 16:31:47 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/650955"
1817953,2019-04-07 00:09:57 UTC,"Reviewed:  https://review.openstack.org/647595
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=96b0b90b89ceb8efe51f9b2270401cca2956079a
Submitter: Zuul
Branch:    stable/rocky"
1817953,2019-03-26 06:34:42 UTC,"As neutron, neutron rocky does not support policy-in-code (as a feature), so this bug sounds a request to support policy-in-code for the released version (rocky). Is there any problem if we don't fix it?"
1817953,2019-02-27 20:56:02 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639822"
1817953,2019-03-25 19:56:48 UTC,"Change abandoned by Nate Johnston (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/639842
Reason: Abandoning so that I can create a new patch, per amotoki's advice."
1817953,2019-02-28 16:46:46 UTC,"Reviewed:  https://review.openstack.org/639822
Committed: https://git.openstack.org/cgit/openstack/oslo.policy/commit/?id=61732757c0e934a7c61cef2b2d2651f5abbb6fc6
Submitter: Zuul
Branch:    master"
1817953,2019-02-27 21:29:24 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/639842"
1817953,2019-02-27 19:51:31 UTC,"The problem is that Neutron already includes the items that constituted the fix for the previous bug [1] - the get_enforcer() method is already defined in neutron/policy.py, and setup.cfg has get_enforcer defined."
1817953,2019-03-25 20:08:01 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/647595"
1817954,2019-02-27 20:02:12 UTC,"In report I see this line:
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/"
1817954,2020-03-07 10:40:40 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1817955,2019-02-27 20:37:10 UTC,"Yes, it is because of that change.
is the dn outside of the subtree?"
1817955,2019-02-27 21:06:32 UTC,"I do not think so, but I may not fully understand what ""subtree"" implies."
1817955,2020-06-12 09:09:31 UTC,Same error after upgrading krb5 packages from 1.12+dfsg-2ubuntu5.3 to 1.12+dfsg-2ubuntu5.4.
1817955,2020-06-12 09:34:22 UTC,Even explicitly added subtree doesn't work:
1817955,2020-06-12 10:24:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1817955,2020-06-16 07:36:30 UTC,Is the fix released in Trustu ESM repository ? I don't see it.
1817958,2019-11-15 15:24:32 UTC,This has been addressed as part of the authenticated registry story: https://storyboard.openstack.org/#!/story/2006274
1817958,2019-08-15 23:09:38 UTC,I sent the following fix proposal to the mailing list:
1817958,2019-06-21 12:25:21 UTC,Assigned to Bruce for re-assignment.
1817958,2019-07-17 04:39:58 UTC,I was able to reproduce this issue.
1817958,2019-03-01 19:50:02 UTC,Marking as release gating. The worker nodes should be pulling images from an internal registry on the controller; instead of going to the external registry every time. Medium priority as this is a performance optimization.
1817961,2019-02-27 21:28:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639840"
1817961,2019-03-04 14:04:36 UTC,"Reviewed:  https://review.openstack.org/639840
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=47061e699b9dbf6fdeea572a5abeaa72e499ec87
Submitter: Zuul
Branch:    master"
1817961,2019-03-22 03:43:44 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1817962,2019-02-28 09:40:31 UTC,It has nothing to do with the used image.
1817966,2020-04-17 19:21:19 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/720819"
1817966,2020-04-02 10:45:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/716926"
1817966,2020-04-04 22:48:50 UTC,"Reviewed:  https://review.opendev.org/716926
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=875a142980b77f2b6eacb3a4d7b8bcb8bb29eacd
Submitter: Zuul
Branch:    master"
1817966,2020-04-19 07:30:12 UTC,"Reviewed:  https://review.opendev.org/720819
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=4e594b43d03ac52eb5dbff9d357e63f07d1f28c8
Submitter: Zuul
Branch:    feature/losf"
1817971,2019-02-28 00:00:08 UTC,This change was made by a bot.
1817971,2019-03-01 03:07:35 UTC,Do you hard reset when you have this problem? Can you attach /var/log/kern.log to the bug?
1817978,2019-07-12 02:09:27 UTC,"Lubuntu 19.10 QA-test on motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)"
1817978,2019-02-28 02:08:06 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1817978,2019-04-24 04:16:43 UTC,// following is from exploration of 19.10 Eoan daily play
1817978,2019-04-25 01:54:13 UTC,"As a comparison and to look some more (plus help test debian), I downloaded https://cdimage.debian.org/mirror/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-lxqt.iso [2019-04-22 06:17] and played with it last night.  Today I'm playing again but with yesterday's [19.10] Lubuntu live-daily running on the machine next to it."
1818002,2019-02-28 03:50:25 UTC,"Yep, looks like Ubiquity really hates BTRFS raid. Reinstalling with a single non-raid BTRFS partition (which I plan to later convert to raid0) works just fine."
1818003,2019-09-19 14:59:19 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1818004,2019-02-28 14:10:30 UTC,The installed version of maas is:
1818004,2019-02-28 08:06:10 UTC,"Hi Wouter,"
1818013,2019-09-15 15:19:40 UTC,Migrated to https://github.com/widelands/widelands/issues/3391
1818013,2019-02-28 06:18:33 UTC,In-game screenshot
1818015,2019-05-13 04:17:21 UTC,[Expired for neutron because there has been no activity for 60 days.]
1818016,2020-08-18 09:17:29 UTC,"@popey
Agreed, description fixed."
1818016,2020-08-18 08:32:29 UTC,"I too would appreciate being able to use a custom mirror. However I'd rather not use --enable-geoip, but something which lets snapcraft use a specific mirror. For example I have a mirror at home on a specific host/IP which I'd prefer to use, to reduce my bandwidth usage, and speed up builds."
1818016,2021-02-03 09:23:46 UTC,"Hey, I just came here to file / look for this bug too."
1818018,2019-03-01 08:50:02 UTC,"Get all the text under the tr tag and the filter value for comparison.
Because there is a space in the text,
inputting a space can filter out the item.
but If the input space exceeds the text space,
the item cannot be filtered out."
1818018,2019-02-28 06:48:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/639931"
1818018,2019-03-01 08:24:44 UTC,I see the different behavior as reported in the description.
1818020,2019-02-28 07:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818021,2019-02-28 07:06:18 UTC,Failures in:
1818023,2019-02-28 07:55:00 UTC,"I can confirm the issue in general. But the issue is lightly different.
The latency usage meter is comparing the time it takes to process the audio buffers, with the length of the audio buffers. The resulting percentage is independent from the used cores."
1818024,2019-02-28 07:19:24 UTC,2 failures that were pre-existing:
1818027,2019-03-06 10:13:44 UTC,The bug is documented in bugzilla:
1818027,2019-03-07 09:12:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818027,2019-03-07 11:16:14 UTC,"in my case, it was caused by very long line of .profile in home directory. i solved it by renew it or deleting the .profile"
1818027,2019-03-07 07:54:59 UTC,"hi, i am having this too. just recently"
1818028,2019-02-28 07:57:05 UTC,"4 failures that were failing previously as well (and on other kernels):
      - ubuntu_kernel_selftests.seccomp
      - ubuntu_kernel_selftests.timers
      - ubuntu_kernel_selftests.memfd
      - ubuntu_kernel_selftests.cpu-hotplug"
1818037,2019-03-01 12:17:51 UTC,Prerequisites:
1818037,2019-09-17 07:23:41 UTC,Migrated to https://github.com/widelands/widelands/issues/3392
1818038,2019-10-31 04:05:11 UTC,We aren't going to deal with bootstrapping trusty controllers any more
1818038,2019-02-28 10:35:34 UTC,I can confirm this with the 2.5.1 and note that it works properly on 2.4.7. Will continue to look into what's changed to cause the issue.
1818038,2019-02-28 10:40:07 UTC,It looks like it's due to this change setting mongo params for better performance.
1818041,2019-03-08 04:16:48 UTC,"After discussions with Joel in IS, he strongly suggested not using UDP for heartbeats if we can help it."
1818041,2019-03-02 18:53:03 UTC,"I think we should have the presence worker publish ""I'm alive"" messages on udp on the controller port, failing back to the apiserver port if the controller port isn't there."
1818043,2019-02-28 11:46:33 UTC,please use:
1818043,2019-02-28 11:48:52 UTC,"... I currently do not have any multi-monitor environment available, sorry."
1818043,2019-03-01 07:39:56 UTC,"Hi,"
1818045,2019-05-08 01:58:34 UTC,"@Marco M (mmawaw),"
1818045,2019-05-07 09:08:50 UTC,"Thanks, I have updated the juju client to 2.6-rc2. I guess I need to upgrade the controller as well, but the ""juju upgrade-controller"" command does not allow me to specify a beta/candidate release, and it's stuck to 2.5.4."
1818045,2019-05-07 03:55:19 UTC,"We have added several fixes for removals and destructions in Juju 2.6. Additionally, remove-unit, remove-application and destroy-model have gained '--force' flag. The flag is provided as a hammer for difficult cases where you are 100% sure that you want an entity [machine, unit, application, model] gone. Could  you please try that version of Juju?"
1818045,2019-04-01 11:29:34 UTC,"I don't mean to hijack the ticket, but am experiencing exactly the same (on MaaS). After removing the CDK bundle, all machines are in stopped state but still very alive and all software is still running."
1818045,2019-03-21 02:03:16 UTC,Updated an open RT we have on this issue: https://rt.admin.canonical.com/Ticket/Display.html?id=116744#txn-2724284
1818045,2019-03-21 01:05:23 UTC,Can we please get the following information
1818045,2019-03-17 23:36:23 UTC,I cannot reproduce this at all.
1818045,2019-03-01 10:21:53 UTC,interesteing extract from machine-85.log (keeping here for future reference):
1818045,2019-02-28 11:12:41 UTC,I have a similar problem where a machine is stuck in down.
1818045,2019-02-28 10:24:16 UTC,Attached is the juju logs
1818045,2019-02-28 10:14:10 UTC,Juju status: https://pastebin.canonical.com/p/WRjh89gVnH/
1818047,2019-03-24 23:39:08 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1818047,2019-03-22 03:43:24 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1818047,2019-03-13 15:23:13 UTC,"Reviewed:  https://review.openstack.org/642611
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cfad7a1faae9aec6041c49149ad923c407f30219
Submitter: Zuul
Branch:    stable/rocky"
1818047,2019-03-11 23:33:35 UTC,"Reviewed:  https://review.openstack.org/641021
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=38f2ce549ce4b21d5085824df701f9d2392b5604
Submitter: Zuul
Branch:    master"
1818047,2019-03-05 12:52:09 UTC,OK this is the useful part of the error:
1818047,2019-03-05 14:10:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641021"
1818047,2019-03-05 12:59:08 UTC,"OK I see the problem, the template is only applied when using the CellMapping object, and the nova-status code is intentionally not using the objects, it is using the data models:"
1818047,2019-03-12 01:04:14 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/642611"
1818048,2019-03-02 15:53:25 UTC,Related to lp:1800513
1818048,2019-05-11 14:41:28 UTC,Paste now uses the center of the selection if it contains more than one item.
1818052,2019-03-02 09:20:36 UTC,"same here, this was feature in the amiga version I never ported to the linux/windows one."
1818052,2019-03-08 18:44:08 UTC,"but, why not use the existing way of manage recurring txn ?
- inherit
- template
- scheduling"
1818052,2019-03-09 18:06:15 UTC,"There's nothing wrong with those, but a right-click menu with some functions (and maybe some shortcuts as CTRL+C, CTRL+V) would help speed up the overall management. This would also be beneficial in that copy/pasting transaction would automatically paste it with today's date instead of the date of the original transaction as it is in ""inherit"" case (which is also a useful behavior and should not be replaced)."
1818052,2019-09-30 20:54:54 UTC,"ctrl+C = copy
ctrl+V = paste (same)
ctrl+shift+V = paste with today's date"
1818054,2020-11-19 00:29:01 UTC,Please excuse the delay the notification email went in the spam folder.
1818054,2020-08-31 11:06:52 UTC,https://github.com/mixxxdj/mixxx/pull/3043
1818054,2020-08-24 04:54:15 UTC,"Alright, Thanks a lot :)"
1818054,2020-08-23 21:01:17 UTC,"... and open a new thread in the development stream
https://mixxx.zulipchat.com/#narrow/stream/109171-development"
1818054,2020-08-23 21:00:36 UTC,"I'd say you also need to pick that default name here, instead of empty QString:
https://github.com/PawBud/mixxx/blob/master/src/preferences/broadcastprofile.cpp#L240"
1818054,2020-08-23 14:26:38 UTC,"I did switch to shoutcast and yet it didn't work, on top of that what if I tried putting a `QString kDefaultStreamName=QObject::tr(""Mixxx"")`, in here https://github.com/PawBud/mixxx/blob/master/src/preferences/broadcastprofile.cpp#L79, It was wrong but would you mind telling me what this file does then?"
1818054,2020-08-23 10:30:03 UTC,i am not very familiar with XML  but I tried to put a `property` tag with the name attribute and it didn't work.
1818054,2020-08-21 16:14:28 UTC,"this is the file where the dialog is set up and processed:
https://github.com/mixxxdj/mixxx/blob/master/src/preferences/dialog/dlgprefbroadcast.cpp
and the GUI file:
https://github.com/mixxxdj/mixxx/blob/master/src/preferences/dialog/dlgprefbeatsdlg.ui"
1818054,2020-08-20 14:28:26 UTC,"I have been trying to find the mixxx.cfg file, May I please be guided with a relevant path(I tried searching for the file on github too)?"
1818054,2019-04-27 19:52:41 UTC,"I looked in to this, it is more involved. The configuration file is created when Mixxx is run for the first time AND OR and or updated when Mixxx is upgraded."
1818054,2019-04-22 16:15:15 UTC,I would be happy to receive a GitHub Pull Request.
1818060,2020-04-23 10:21:17 UTC,filed a new bug for the issue discussed in comments 15-18 there https://bugs.launchpad.net/tripleo/+bug/1874418
1818060,2020-04-21 13:58:34 UTC,"thanks ykarel ... looks like you were right about this being some kind of race/not consistent issue. The latest run from today fails on the overcloud deploy, so it got passed that failing task looks like"
1818060,2020-04-21 08:38:01 UTC,"<< * https://logserver.rdoproject.org/openstack-periodic-master/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp_1supp-featureset039-master/763fc68/job-output.txt
                * 2020-04-20 02:57:22.439102 | primary | [2020/04/20 02:57:22 AM] [ERROR] stdout: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Error, some other host (FA:16:3E:FC:D1:41) already uses address 10.0.0.1."
1818060,2020-04-20 15:29:11 UTC,"18:23 < ykarel|away> marios, node meant compute node in rdo cloud not undercloud/overcloud vms
18:23 < marios> ykarel|away: i see so perhaps unrelated then
18:23 < marios> ykarel|away: thanks"
1818060,2020-04-20 15:19:45 UTC,o/ seeing a similar issue today for periodic centos8 fs39 ... log pointers below. Per comment 14 above https://bugs.launchpad.net/tripleo/+bug/1818060/comments/14 I also see that the node has         * net.ipv4.conf.all.arp_ignore = 0 in https://logserver.rdoproject.org/openstack-periodic-master/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp_1supp-featureset039-master/763fc68/logs/undercloud/var/log/extra/sysctl.txt.gz
1818060,2019-09-26 13:13:14 UTC,"With Rodolfo and Kieran we did some debugging today on environment provided by Yatin. Finally we found out that problem was ""arp_ignore"" sysctl option which was set on compute nodes to 0 (default value).
According to documentation https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt this means that kernel will reply for ARP request if requested IP address is on ANY of interfaces in the system. And indeed we had something like that. On one of compute nodes which hosted one of vms connected with Yatin's controller-2 on some interface (vlan111X) there was exactly same IP address configured.
When we switched ""arp_ignore"" to 1 problem was gone."
1818060,2019-09-25 07:20:15 UTC,"So today it got reproduced locally in an OVB deployment, some of the info i gathered:-"
1818060,2019-07-30 17:45:00 UTC,Just adding more info...
1818060,2019-05-16 13:37:31 UTC,"Gabriele - nothing in neutron should be using proxy ARP, but there could be something mis-configured, or a piece or network equipment doing it."
1818060,2019-05-15 15:53:32 UTC,"Brian,"
1818060,2019-05-15 19:36:57 UTC,"So the error is coming from the ifup-eth script on the instance, which probably looks something like this:"
1818060,2019-05-15 15:55:11 UTC,I would also like to have my team investigate the possible root cause as being something in https://openstack-virtual-baremetal.readthedocs.io/en/latest/  I'm not convinced it's rdo-cloud 100%
1818060,2019-05-15 15:54:03 UTC,FYI.. example filter for finding ip assignment issues
1818060,2019-02-28 12:42:42 UTC," openstack server list | grep -i error | wc -l                                        
184"
1818060,2019-05-15 15:16:23 UTC,"Wes - do you have a pointer to a recent failure?  I've been looking through logs.rdoproject.org and haven't found one yet.  I don't know of any issues where neutron DHCP would have allocated the same IP twice, I think the DB would have not allowed it."
1818060,2019-04-18 17:01:57 UTC,"dhcp should NOT distribute an ip that is already allocated.  AFAICT the heat stacks are deleted as much as possible during a CI run [1] , additionally clean up scripts are running in the background."
1818060,2019-04-17 15:26:40 UTC,"Reopening this bug. We hit the port failures when the stack list is clean.
Possibly while one stack is created while another is being deleted.
Reopening to monitor this."
1818060,2019-03-04 13:25:56 UTC,Proposing https://review.rdoproject.org/r/19048  the include error servers cleanup in the periodic cleanup
1818060,2019-05-16 10:41:37 UTC,"The arping output is suppressed, and we are using a catchall exception to assume somebody has our address."
1818065,2019-07-30 16:12:31 UTC,Trello card created to back-fill dimensions for existing media: https://trello.com/c/1yhI54Gf/407-back-fill-media-dimensions
1818065,2019-05-24 16:38:27 UTC,trying this out as my first Canonical MP
1818071,2019-02-28 21:08:14 UTC,mais pas si un tab est présent dans un champs: le csv est et restera un format de fichier peu fiable.
1818071,2019-03-01 18:02:39 UTC,"Maxime, merci pour ta réaction!"
1818071,2019-03-27 12:24:23 UTC,"depuis les report, si tu copie dans les presse papier tu as déja du TSV"
1818071,2019-03-28 08:33:26 UTC,"c'est pour IMPORTER que le option TSV soulagerait.
J'ai rencontré des "";"" dans le champ MEMO et le caractère TAB se trouve nulle-part la dedans. Un TSV, surtout pour IMPORTer les opérations, serait utile.
Merci Maxime"
1818071,2019-04-09 18:57:40 UTC,"Q: est-ce que le fichier à importer est valide, c'est a dire, est-ce qu'il contient pour les champs avec des ; des quotes ouvrantes/fermantes ?"
1818071,2019-04-16 20:32:12 UTC,"Oui, il contient des quotes ouvrantes/fermantes MAIS j'ai du manipuler
les données et dans AWK ces QUOTEs sont bien moins pratiques que les TABs."
1818071,2019-05-12 13:52:47 UTC,"added common ones: Tab, Comma, Semicolon, Space"
1818075,2020-06-18 16:04:49 UTC,"QEMU, like most open source projects, relies on contributors who have motivation, skills and available time to work on implementing particular features. They naturally tend to focus on features that result in the greatest benefit to their own use cases. Thus simply declaring that an open source project, must support something won't magically make it happen."
1818075,2020-06-18 16:03:13 UTC,"We do care about emulation; but as always with open source software projects, the parts that get more care and attention are the parts that people are either paid to work on or are personally interested in. x86 guest emulation in particular is not very well maintained (though it is better than some targets), because mostly people are happy to use x86 hardware, and adding support for emulation of large new architectural features like AVX is a lot of work. If you would like to help improve x86 guest emulation, you are welcome to submit patches to fix bugs or add new features. Merely saying ""X should be better and you should somehow magically find three months worth of developer time to make it so"" doesn't really do anything to move the situation forwards."
1818075,2020-06-18 22:28:05 UTC,"Of course it’s open source, I get that. When I say „xyz should be done“ then in the sense of „2+2 should be 4“ not in the sense of „you must implement xyz right now“ ;)"
1818075,2019-02-28 14:14:32 UTC,"Further debugging on IRC reveals that QEMU itself is not hanging, but the guest code is looping infinitely, because QEMU doesn't implement the AVX instruction set and isn't generating an undefined-instruction exception either. So the %rdx output from the AVX insn is wrong and the guest code never exits the loop (whose condition depends on %rdx)."
1818075,2019-02-28 14:13:04 UTC,"<pm215>	my guess is we're doing something unhelpful with the AVX insn, and so the guest code which is checking the result and using it as its loop condition for the jns is just looping forever"
1818075,2020-06-18 15:45:02 UTC,If I may be so free:
1818078,2019-02-28 14:28:35 UTC,The issue results in:
1818078,2019-03-26 15:33:08 UTC,See also https://bugs.launchpad.net/nova-lxd/+bug/1711568 for more details about maybe having to register the LXDLiveMigrateData object in nova.
1818078,2019-03-28 12:11:36 UTC,"Also, further interesting info:"
1818086,2019-02-28 16:13:41 UTC,"Also, the Angular client uses the title attribute approach, which results in the nice tooltip.  Probably a good idea to be consistent and use the title attribute (at minimum) in the AngularJS client."
1818087,2019-02-28 15:03:53 UTC,This proposed emerged during lp:1817974 discussion.
1818087,2019-04-11 23:31:02 UTC,"Fixed in revision 8ae0579436a6f51f5a2429f737b87dceaa57d5aa
https://git.launchpad.net/kicad/patch/?id=8ae0579436a6f51f5a2429f737b87dceaa57d5aa"
1818088,2019-12-25 08:35:48 UTC,"I encountered such question again with StarlingX 2.0 latest release. After deploying some virutual servers witch openstack, some compute nodes entered degradeded state and then offline state. With command 'fm event list' I found a lot of 'Plafrom memory exceed threshold', for detail, plz refer the attachment."
1818088,2019-07-17 17:54:50 UTC,Closing as per notes above
1818088,2019-07-16 20:01:06 UTC,"I looked at today's sanity on the same AIO-DX system, the results are much better now.
With similar test cases, the platform threshold alarm only appeared once during an evacuation test, and the alarm cleared after some idle time."
1818088,2019-07-16 17:10:50 UTC,"Numan, Many improvement have been made since the bug was filed, can you please retest this scenario to see if it is still an issue."
1818088,2019-05-06 20:59:08 UTC,Also seen on IP31-32 using build 20190505T233000Z
1818088,2019-03-01 19:46:35 UTC,There has been no system engineering done with containers. It is expected that more memory will be needed with this config. Putting on hold until the system engineering activities are done.
1818091,2019-02-28 17:32:36 UTC,This would seem to be the case but I'm not sure it can be mapped 100% to KiCad but it might be close enough to be worthwhile.  Does anyone have any reason as to why we shouldn't do this?
1818091,2019-03-13 08:45:32 UTC,Can DRC deal with filled polygons on the courtyard layer? If it can not then we might need to additionally convert such filled polygons to pure outlines as part of the import step. (Might be a good idea anyways as it would fit better with other kicad footprints. But if DRC can deal with filled polygons than this is only a bonus that might be best as an option of the import.)
1818091,2019-03-13 13:41:02 UTC,It can.  We pushed that off to v6 as polygons render filled to gerbers in 5.0
1818091,2019-03-13 16:22:15 UTC,Is the courtyard layer intended for gerbers? I thought that one is intended for kicad internal use only? (For checking if two parts are too close to each other.)
1818091,2019-03-13 17:04:57 UTC,You are right.  I'm conflating the Edge.Cuts layer.  But the logic we use for that can be used for courtyard as well.  And probably should.
1818092,2019-07-10 21:39:24 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1818092,2019-04-01 10:14:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/648939"
1818092,2019-03-24 23:39:21 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1818092,2019-03-22 03:43:42 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1818092,2019-07-04 00:16:26 UTC,"Reviewed:  https://review.opendev.org/648939
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9cbd2aeddec61c58aad5fd3efcf16c65612d2db7
Submitter: Zuul
Branch:    stable/queens"
1818092,2019-03-01 17:45:10 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640462"
1818092,2019-03-01 13:46:30 UTC,"Reviewed:  https://review.openstack.org/635350
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4da058723332a58323640fabce3d95902946a07d
Submitter: Zuul
Branch:    master"
1818092,2019-02-28 16:33:23 UTC,Chris' fix: https://review.openstack.org/#/c/635350/
1818092,2019-02-28 16:33:00 UTC,"Yeah this is a long-standing source of confusion, see bug 1195361."
1818092,2019-03-02 02:03:46 UTC,"Reviewed:  https://review.openstack.org/640462
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ecdf3c67ee464139d8a6f9cb8d332857f261228b
Submitter: Zuul
Branch:    stable/rocky"
1818113,2020-05-08 15:34:21 UTC,We are still hitting this bug using the keystone -next charm.  The artifacts can be found on the bottom of the test run.
1818113,2020-05-13 15:39:46 UTC,https://solutions.qa.canonical.com/#/qa/testRun/794aaeef-0d8d-438c-b21b-55faec2b8380
1818113,2020-05-13 15:44:16 UTC,octavia/2 failed to connect to keystone in the run above.
1818113,2020-05-13 15:55:51 UTC,"Basing this on the premise that this stble run is actually using the next charms as reported:
https://solutions.qa.canonical.com/#/qa/testRun/753c0272-f052-4450-8a5b-e205760774e6"
1818113,2020-05-14 05:26:01 UTC,Looking at the artifacts referenced in #33
1818113,2020-05-20 09:19:06 UTC,debug_log.txt contains lines like:
1818113,2020-05-20 22:51:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/729781"
1818113,2020-06-15 16:20:26 UTC,"David,"
1818113,2020-06-15 17:15:26 UTC,"Michael,"
1818113,2020-06-16 09:57:55 UTC,"Hi, this is currently blocked on this fix [0] to be packaged and published."
1818113,2020-06-23 08:42:08 UTC,Still blocked. Temporarily published to https://jaas.ai/u/aurelien-lourot/keystone for testing.
1818113,2020-07-15 18:41:46 UTC,"After some more analysis, we can also attack this bug from the Octavia side. The root cause is with Keystone but Octavia is also not handling the error condition gracefully."
1818113,2020-07-13 21:58:51 UTC,"We've been testing with @aurelien-lourot's fix and appear to still hit this issue, here is an example test run:"
1818113,2020-07-16 14:06:02 UTC,"I confirm that the last failing run is running my charm and that it contains my fix, since I can see these new traces [0] in debug_log.txt."
1818113,2020-07-16 15:23:05 UTC,@aurelion-lourot
1818113,2020-07-16 15:41:09 UTC,We found the new culprit:
1818113,2020-07-16 15:55:27 UTC,Thanks @mskalka for noticing! In the previous run with my charm [0] it took only 5 minutes (not 45):
1818113,2020-07-16 21:22:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/741547"
1818113,2020-07-16 22:54:42 UTC,"Reviewed:  https://review.opendev.org/729781
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=8b46dfd637908adeb5a817f85fc97fad249be8a0
Submitter: Zuul
Branch:    master"
1818113,2020-07-17 08:16:33 UTC,@mskalka I'm not sure why the latest run [0] timed out but from the debug_log.txt I see only 3 minutes (not 45):
1818113,2020-07-23 16:17:10 UTC,"Reviewed:  https://review.opendev.org/741547
Committed: https://git.openstack.org/cgit/openstack/charm-interface-keystone/commit/?id=a48a1e826ac0a74ab05a16c441cda4e4b34b1241
Submitter: Zuul
Branch:    master"
1818113,2020-08-07 17:28:51 UTC,"Reviewed:  https://review.opendev.org/741304
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=7be811606cd9000d57ef4483b9b266e9f613f4dd
Submitter: Zuul
Branch:    master"
1818113,2020-04-30 15:06:25 UTC,"Reviewed:  https://review.opendev.org/721558
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=53bcfd0a064c11d90009d42f9fbe61d79f963e9c
Submitter: Zuul
Branch:    master"
1818113,2020-07-03 06:59:59 UTC,Still blocked as long as https://bugs.launchpad.net/ubuntu/+source/python-oslo.policy/+bug/1880959 hasn't been backported to Queens
1818113,2020-04-21 09:36:50 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/721558"
1818113,2019-04-23 15:26:09 UTC,Attaching logs
1818113,2020-04-13 15:17:13 UTC,Hit this again: https://solutions.qa.canonical.com/#/qa/testRun/a69e03d1-fcb5-43b1-8c66-cdc2721e8282
1818113,2020-04-13 15:19:17 UTC,Twice over the weekend: https://solutions.qa.canonical.com/#/qa/testRun/493aa388-7575-4a43-a084-08f5f6994189
1818113,2019-03-01 16:05:13 UTC,Sub'd to field high as this is causing a sudden spike in failures
1818113,2019-03-01 17:20:30 UTC,"Hi Alex, please, could you provide the bundles you are using so that we can chase this down a bit.  Have those bundles changed recently (i.e. are they using stable or next, etc.)"
1818113,2019-03-01 18:11:20 UTC,This is happening in the new create_endpoint_check() that was added here:
1818113,2019-03-01 18:13:38 UTC,@ajkavanagh here is the bundle http://paste.ubuntu.com/p/b5YXFdyPfp/
1818113,2019-03-01 19:51:06 UTC,Looks like the openstack-service-checks is calling the relation for keystone before keystone is ready - should keystone not be blocking the relation until it's ready?
1818113,2019-03-01 21:22:52 UTC,"just after identity-credentials-relation-changed hook ran where we were passed authentication credentials from keystone, keystone is immediately not available for the next update-status for the charm to use keystone."
1818113,2019-03-04 07:38:43 UTC,Update released in cs:~canonical-bootstack/openstack-service-checks-11
1818113,2019-03-05 23:03:33 UTC,We found there was a race-condition between layer:apt installing packages and the reactive handlers kicking off in service_checks.py which lead to service_checks.py imports failing due to apt packages providing those dist-packages for python modules.  We have updated the code to use layer:basic's package installs on bootstrap and are working on review/release.
1818113,2019-03-01 15:38:15 UTC,I suspect this is something to do with the recent updates to the charm.
1818113,2019-12-11 16:33:38 UTC,"Saw a very similar issue with octavia today:
It requested data from keystone but keystone was not yet available."
1818113,2019-04-23 15:19:06 UTC,"Something very similar to this came up in another run, but at a slightly different place:"
1818113,2019-12-11 17:32:58 UTC,versioned overlay
1818113,2020-04-07 16:00:11 UTC,"The crashdump from comment #13 shows octavia trying to communicate with other
services once it has received credentials from keystone. Looking at the logs
all octavia units fail running setup_hm_port at around 11:48. But looking at
the keystone log at the same time keystone/0 and keystone/2 have yet to
setup their database connection and are still talking to their local sqllite
db, this results in them returning a 500 error."
1818113,2020-04-06 17:25:52 UTC,SQA hit this bug 3 more times over the weekend.
1818113,2019-12-11 17:32:07 UTC,attaching bundle
1818113,2020-02-20 21:38:05 UTC,'juju resolved' fixes the problem
1818113,2020-02-20 21:32:54 UTC,"However it affects octavia charm, not the openstack-service-checks charm. Symptoms: https://paste.ubuntu.com/p/vjCD4vrV9z/"
1818113,2020-03-30 15:38:22 UTC,"Solutions QA continues to hit this bug. All occurrences are listed here:
https://solutions.qa.canonical.com/#/qa/bug/1818113"
1818113,2020-01-08 16:55:51 UTC,We hit it again.  Crashdump is attached.
1818113,2019-12-11 18:15:56 UTC,"Actually, the hacluster charm config default of 3 units happens to align with the deployed number of units, and I would expect that to squash my concern in my comment #16."
1818113,2019-12-11 17:51:10 UTC,"Ryan,"
1818113,2019-12-11 17:38:59 UTC,The example bundles regarding comments 13 through 15 seem to be lacking a race-condition avoidance requirement of specifying the cluster_count on hacluster.  Can you confirm that this problem still exists when that is set?
1818113,2020-02-20 21:26:10 UTC,Happens from time to time in our deployment as well.
1818117,2019-03-01 08:31:17 UTC,Looks like this has been fixed.
1818118,2019-07-26 15:21:29 UTC,"It would also be good to know of the 25+ live migrations in the nova regression, how many hit this connectivity issue?"
1818118,2019-12-05 22:44:01 UTC,Closing; issue is not reproducible
1818118,2019-11-18 22:52:41 UTC,Requesting a re-test of this issue with openstack train
1818118,2019-08-23 17:46:36 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1818118,2019-07-29 20:00:52 UTC,"Adding logs from latest nova regressions on 2+3 system wolfpass3-7 with 20190727T013000Z load.
We have about 9 out of 60 ping failures after live-migrations."
1818118,2019-07-26 15:14:57 UTC,Please attach the logs from the most recent reproduction of this issue.
1818118,2019-12-03 15:21:45 UTC,"Issue was not reproduced in 35 runs on
Lab: WCP_3_6
Load: 2019-12-01_20-00-00"
1818118,2019-07-25 13:33:52 UTC,"@Yang, There are reports that live migration is not working:
https://bugs.launchpad.net/starlingx/+bug/1837759
https://bugs.launchpad.net/starlingx/+bug/1830915"
1818118,2019-03-01 19:37:56 UTC,Marking as release gating; possibly a neutron or vswitch issue. Needs further investigation.
1818118,2019-03-07 16:57:17 UTC,"Currently, this issue seems to be reproducible in only one system.
The recipe to reproduce is to do a VM live migration, followed by a reboot."
1818118,2019-07-25 14:50:00 UTC,"I did not see consistent live-migration failures in latest nova regression last weekend, which performed 25+ live migrations on various guest on standard and storage systems with local_image and remote instance backends."
1818118,2019-07-16 12:44:00 UTC,When is the last time that this behaviour has been observed?
1818118,2019-07-23 15:17:29 UTC,"I'm seeing similar issue in recent nova regressions, where vm becomes unreachable after live-migration.
The last time seen was on dedicated storage system wcp113-121 after live migrating a ubuntu guest on load 20190720T013000Z."
1818118,2019-03-18 15:11:12 UTC,Reducing the priority to medium since this issue is only reported in one system only.
1818119,2019-02-28 17:31:24 UTC,"On Thu, Feb 28, 2019 at 04:44:38PM -0000, Matthias Klose wrote:

> Public bug reported:
>
> britney handles autopkg transition ""neutral"" -> ""fail"" as a regression.
> It should not.
>
> Seen at
> http://autopkgtest.ubuntu.com/packages/a/acl/disco/amd64
"
1818122,2019-06-12 13:46:13 UTC,"Could you try with QEMU 4.0, please? There was a bug/incompatibility between earlier QEMU and the Alpine Linux libc which we fixed in 4.0, and so this might be that bug (or some other bug we've already fixed)."
1818122,2019-06-12 15:35:19 UTC,"@pmaydell
I'm willing to test. However, I encountered another bug introduced in 4.0 which even prevents me from installing xmlto. I'll preparing a bug report and will post it soon."
1818122,2019-07-03 09:39:40 UTC,@pmaydell I just tested the latest commit in git master and still got the same error.
1818123,2019-07-15 15:45:39 UTC,No longer seen this error message from sysinv log on multi-node or simplex system with 20190713T013000Z master load.
1818123,2019-07-05 12:45:07 UTC,"Reviewed:  https://review.opendev.org/669246
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=cfed685e5546ccb7f382fb9b66990c35984320f9
Submitter: Zuul
Branch:    master"
1818123,2019-07-05 03:52:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669246"
1818123,2019-06-27 21:44:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668060"
1818123,2019-05-07 20:56:15 UTC,"Reviewed:  https://review.opendev.org/657087
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=4802f1d96a1217124e39a057fd7a05e22177b81c
Submitter: Zuul
Branch:    master"
1818123,2019-06-28 12:30:49 UTC,"Reviewed:  https://review.opendev.org/668060
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=3ad728ac6db989b6edd5f134075bef5c3f5b2af8
Submitter: Zuul
Branch:    master"
1818123,2019-03-01 19:42:50 UTC,Marking as release gating; related to containers. Low priority as this is tracking the log. The re-apply failure is tracked by another LP: https://bugs.launchpad.net/starlingx/+bug/1817770
1818129,2020-02-25 07:07:54 UTC,"Hi Jochen,
I just came by looking at targetcli-fb and found that bug.
Let me update a few things to the current state."
1818129,2020-02-25 07:09:28 UTC,"Since a user can fix this as part of the local config I think it is low, but it is great to have this bug so that users can find it."
1818130,2019-06-23 04:19:08 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1818130,2019-04-23 23:55:08 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1818130,2019-03-07 18:01:43 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1818133,2020-01-29 20:17:36 UTC,"I had the same problem.
After the
 SystemError: E:Unable to correct problems, you have held broken packages.
line
the next one was a prompt about retrying. I did retry and everything worked"
1818134,2019-06-11 16:48:00 UTC,apport information
1818134,2019-06-11 16:48:01 UTC,apport information
1818134,2019-06-11 16:48:03 UTC,apport information
1818134,2019-06-11 16:48:04 UTC,apport information
1818134,2019-06-11 16:48:06 UTC,apport information
1818134,2019-06-11 16:48:08 UTC,apport information
1818134,2019-06-11 16:48:09 UTC,apport information
1818134,2019-06-11 16:48:12 UTC,apport information
1818134,2019-06-11 16:48:13 UTC,apport information
1818134,2019-06-11 16:48:24 UTC,apport information
1818134,2019-06-11 17:59:56 UTC,"@vandebo, your apport information shows the following:"
1818134,2019-06-11 18:06:33 UTC,"Other commenters, please confirm what kernel version you are seeing this behavior with.  If this is not reproducible with either the linux-generic 3.13 kernel or the linux-lts-xenial 4.4 kernel, then it is not going to be fixed."
1818134,2019-06-12 15:48:16 UTC,"I've confirmed that the problem went away by upgrading to the xenial kernel -- I reinstall shim-signed, rebooted to the new kernel and it worked. I also reinstalled the nvidia package after rebooting and it still worked."
1818134,2019-06-12 19:29:43 UTC,Thanks for confirming.
1818134,2019-07-07 00:52:47 UTC,"To be clear, my issue was on the 3.13 kernel line, which is supported. Not that it matters for me anymore because I've since upgraded to 18.04 for which doesn't have this issue."
1818134,2019-06-11 16:47:58 UTC,apport information
1818134,2019-06-11 16:48:21 UTC,apport information
1818134,2019-06-11 16:47:56 UTC,apport information
1818134,2019-06-11 16:58:39 UTC,I encountered this issue with the nvidia_384 modules.
1818134,2019-06-11 16:47:53 UTC,apport information
1818134,2019-03-01 07:00:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818134,2019-03-03 17:48:55 UTC,"I'm also seeing the same problem on a Dell XPS 13 9343 - Wifi is suddenly non-functional, whereas it'd otherwise been working fine for many years (I'm unsure exactly when the problem started, as I mostly use my laptop via wired ethernet, but it's definitely broken within the last couple of weeks)."
1818134,2019-03-03 18:43:04 UTC,"I had a look at my Updates history in Ubuntu Software Centre for the last couple of weeks to see if I could spot any ""likely culprits"", and I see that on the 18th February the 'dkms' package got bumped from 2.2.0.3-1.1ubuntu5.14.04.9 to 2.2.0.3-1.1ubuntu5.14.04.10 and the 'shim-signed' package got bumped from 1.33.1~14.0.4.3+13-0ubuntu2 to 1.33.1~14.0.4.4+13-0ubuntu2"
1818134,2019-03-03 20:21:39 UTC,I can confirm that the solution provided by Lurchman fixes my problem as well.
1818134,2019-03-09 02:13:59 UTC,"I had to do a little more than this and held several packages to downgraded versions due to dependencies. :(
#sudo apt-mark showhold
dkms
grub-common
grub-efi-amd64-bin
grub2-common
shim
shim-signed"
1818134,2019-06-11 16:47:55 UTC,apport information
1818134,2019-03-11 10:25:47 UTC,"I've done some more investigation this morning, and I think I've narrowed down the problem slightly further. It seems I *can* upgrade 'dkms' (and also install 'shim'), as long as I leave 'shim-signed' uninstalled, although this has a few caveats..."
1818134,2019-03-11 15:27:56 UTC,Please run 'apport-collect -p shim-signed 1818134' to provide further information about the state of SecureBoot on your system.
1818134,2019-03-14 00:35:12 UTC,"I have the same problem with the nvidia driver. Updated shim-signed + dkms installed a while ago, worked fine until kernel upgrade triggered dkms rebuild, then the nvidia driver failed to load, ""modprobe: ERROR: could not insert 'nvidia': Package not installed"". Uninstalling shim-signed, downgrading dkms and reinstalling the drivers solved my issue."
1818134,2019-03-14 04:57:12 UTC,"ok, so can someone who's experiencing this bug run the requested command so we can collect more information?"
1818134,2019-03-14 04:57:43 UTC,"There's a reasonable chance this is an issue with the lockdown kernel patches in Ubuntu 14.04, so opening a task on linux also."
1818134,2019-03-14 05:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818134,2019-03-14 12:10:12 UTC,I would rather not have to deliberately bring my system to a broken state just to run apport-collect. Is there anything else I can do?
1818134,2019-05-25 18:38:05 UTC,"Hello,"
1818134,2019-05-29 17:50:38 UTC,"Just want to add that this exact same issue affects Veeam Agent for Linux when dkms builds the veeamsnap module, and @Lurchman's solution works to solve it."
1818134,2019-06-11 16:47:49 UTC,".proc.sys.kernel.moksbstate.disabled: 0
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
DistroRelease: Ubuntu 14.04
EFIBootMgr:"
1818134,2019-06-11 16:47:50 UTC,apport information
1818134,2019-03-01 06:59:41 UTC,Also have the issue since yesterday:
1818137,2019-02-28 22:06:35 UTC,"Please let me know if this is a high priority issue. For now, I'll be delaying this to prioritize other work."
1818137,2019-02-28 21:50:27 UTC,"It looks this will be hard to support. A busybox-image option was added[1] back in August, but the latest stable release (0.2.0) does not include this option."
1818137,2019-02-28 21:13:10 UTC,Thanks for the report. It looks like elasticsearch-operator creates this DaemonSet. I'll see if there's an argument we can pass to it.
1818137,2019-02-28 21:53:22 UTC,A potential workaround is mentioned here: https://github.com/upmc-enterprises/elasticsearch-operator/issues/139#issuecomment-414067572
1818139,2019-03-20 17:43:04 UTC,"Netplan does not work that way. To configure custom DNS for an interface, you should include all the other features for that device as well."
1818140,2019-03-17 06:02:05 UTC,"I think the error message is a symptom instead of the cause.
Seems like the bluetooth connection gets disconnected without sending an event, so the sysfs doesn't get removed. Once a new connection is established, the sysfs clashed with the old one."
1818140,2019-03-16 20:09:26 UTC,"I don't know, I thing both my hardware - speaker and mouse were released
later than Ubuntu 15.04"
1818140,2019-03-16 16:27:48 UTC,"Also, does it happen on when your system was 15.04?"
1818140,2019-03-16 09:59:34 UTC,"The environment I tested is fresh installed 18.04, and everything is up-to-date."
1818140,2019-03-15 16:19:50 UTC,"It's not regular, dont know exactly it's caused often when I use two
Bluetooth devices - Logitech Anywhere Mouse MX and playing music through
JBL Charge 3. Something causes I no longer can play music and GUI loses
connect /not connected state. Often when another devices(e.g mobile phone)
""takes over"" bluetooth speaker. This may be hard to reproduce then, could
you possibly compile kernel for me so I can test in same setup or collect
more debug info when it will happen again?"
1818140,2019-03-15 06:26:23 UTC,I can't reproduce the issue on Bionic with kernel 4.15.
1818140,2019-03-13 17:00:10 UTC,Seems like we enabled this platform before. Let me see if I can find the same system in our lab.
1818140,2019-03-01 02:08:34 UTC,"> Bluetooth: hci0: last event is not cmd complete (0x0f)
>
> are causing:
>
> kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to register things with the same > name in the same directory
"
1818140,2019-03-13 14:41:32 UTC,"Ubuntu 18.10
Bluez Version: 5.50-0ubuntu1"
1818140,2019-03-12 17:44:07 UTC,So the bluetooth part is not proprietary. Does this issue happen to previous kernels?
1818140,2019-03-08 15:07:17 UTC,"It's BCM4352 802.11ac, both btusb and btbcm modules are loaded. I don't think full opensource driver exists the only avaliable package is bcmwl-kernel-source
Which causes:
[   11.678078] wl: module license 'MIXED/Proprietary' taints kernel."
1818140,2019-03-06 10:59:45 UTC,Does this device use regular btusb/btbcm or a proprietary one?
1818140,2019-03-01 03:00:05 UTC,This change was made by a bot.
1818140,2019-03-01 02:36:03 UTC,"Sorry, I see now. It was just a typo in the bug description:"
1818140,2019-03-13 15:46:08 UTC,"It was unstable from the begining, I can test some bisect kernels if you
can provide me with"
1818142,2020-12-29 16:15:13 UTC,"Something like (declaim (sb-ext:please-be-nitpicky)) in .sbclrc sounds good to me, and could certainly be advertised for newcomers to SBCL as a source of more useful information."
1818142,2020-12-29 15:47:53 UTC,I envision a general solution for enabling or disabling non-standard but useful warnings. So that they can be all enabled at once. Something like an OPTIMIZE declaration.
1818142,2020-12-29 15:37:07 UTC,"So, with this patch,"
1818142,2020-12-29 15:36:58 UTC,"I like defining just a method when there's a default, so I just have"
1818142,2020-12-29 15:18:05 UTC,I would've liked it to be signaled only when the user requests it. Possibly via a proclamation.
1818142,2020-12-29 15:07:46 UTC,"A patch, for discussion."
1818142,2020-12-29 15:34:57 UTC,"My desires: something that can turn it on, and something that can turn it off.   I'd like to be able to put something in the .sbclrc file, or something that could wrap a call to the compiler in asdf to enable it just for a particular system.   Default being turned off is fine, but I want to be able to enable it for the software of others without having to modify their files."
1818142,2020-11-19 22:09:16 UTC,"It was someone else, actually.  But you too. :)"
1818142,2020-11-19 21:25:18 UTC,"That someone was me. In particular, on SBCL 2.0.10 Linux amd64:"
1818142,2020-11-02 19:16:59 UTC,Just saw this happen again with someone.   Bump.
1818142,2019-03-07 14:29:37 UTC,Note the following comment in src/pcl/boot.lisp:
1818142,2019-03-01 15:15:16 UTC,"There can be more non-standard warnings issued, so it should be a more general solution."
1818142,2019-03-01 14:13:30 UTC,"What's the best way to do something like this?   An issue is making code using it play well with earlier versions of SBCL.   So if there's a symbol SB-EXT:*FOO* that controls the behavior, one might write (in the .sbclrc file, say):"
1818142,2020-12-29 01:46:24 UTC,+1 from me.  Today SBCL was complaining about an unset slot in a funcallable class when I was trying to use the MOP dependent maintenance protocol.  Turns out this was the culprit:
1818144,2020-08-18 12:47:31 UTC,"Thanks for testing Jessica. I'll take another crack at it. We don't have Advantage titles that are not shared so I did not see this problem, but Overdrive has a testing environment so I'll look at that."
1818144,2020-08-17 16:08:05 UTC,"We tested this patch, and it seemed to work in testing so we applied it to our production system. We discovered that it works for OverDrive Advantage titles that were shared with the consortium, but if titles are not shared, they are still displaying as ""null of null"" or ""0 of 0."""
1818144,2020-02-19 20:57:21 UTC,I added an upgrade script and updated seed data.
1818144,2019-05-23 15:50:42 UTC,OverDrive.pm sets a discovery_base_uri of 'https://api.overdrive.com/v1'.  I added an 'availability_base_uri' set to 'https://api.overdrive.com/v2' and changed the functions that lookup holdings and availability to use the new base uri.  Several other functions still require the v1 base uri.
1818144,2019-02-28 21:52:49 UTC,"Another example related to the bug report.  If copies of a title have been purchased both by NOBLE, Inc. and by one or more libraries through their OverDrive Advantage accounts, the copies purchased by the libraries do not display in the catalog.   A screenshot is attached.  In this case, NOBLE owns a total of 11 copies of Nine Perfect Strangers; 8 purchased by the consortium and 3 through libraries' OverDrive Advantage accounts."
1818144,2019-02-28 21:36:19 UTC,"Related to the above bug report, if a title was purchased by a member library through their OverDrive Advantage account, but was not purchased by our consortium (NOBLE, Inc.), the catalog indicates that no copies are available.  Note: in some cases the display indicates “status: null of null available” and in others “status: 0 of 0 available”.  A screenshot is attached."
1818144,2020-01-30 17:47:44 UTC,"Martha, thanks for the branch, but the code is incomplete. It is missing a database upgrade script to add the ebook_api.overdrive.availability_base_uri to the config.org_unit_setting_type table."
1818147,2019-02-28 21:40:54 UTC,This was noticed because MAAS creates a dictionary and then renders the YAML with yaml.dumps which places the order of the keys alphabetically.
1818147,2019-03-20 17:34:07 UTC,We specifically addressed this kind of issue before; and I can verify that the config presented does work:
1818147,2019-03-20 20:21:48 UTC,"This was deploying Bionic with MAAS. Would that fix be released in Bionic, because I did hit it on Bionic and it is affecting deployments with MAAS."
1818149,2019-03-05 23:56:35 UTC,A new test kernel is now available at:
1818149,2019-03-05 00:51:18 UTC,A test kernel with those patches backported is available at:
1818149,2019-02-28 22:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818152,2019-02-28 22:30:06 UTC,This change was made by a bot.
1818162,2019-03-15 23:37:52 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1818162,2019-03-19 16:51:35 UTC,"= bionic verification =
After running cert:"
1818162,2019-03-20 05:03:02 UTC,"= cosmic verification =
After running cert:"
1818162,2019-04-02 10:27:35 UTC,This bug was fixed in the package linux - 4.15.0-47.50
1818162,2019-04-02 10:29:42 UTC,This bug was fixed in the package linux - 4.18.0-17.18
1818162,2019-03-15 23:31:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1818164,2019-03-01 01:30:05 UTC,This change was made by a bot.
1818165,2020-06-01 16:09:02 UTC,https://github.com/openstack-charmers/vaultlocker/pull/12
1818165,2019-03-05 14:42:48 UTC,"Looking at the vaultlocker code, we could attempt to store and validate the key prior to actually using it to format the disk - this would leave the disk pristine in the event of a vault related error."
1818165,2019-12-11 16:12:31 UTC,The alternative is that vaultlocker could purge the block device if the storage of the key fails in vault for some reason - ensuring that the disk is left in a pristine state.
1818165,2019-03-04 12:39:50 UTC,"Great that does not mean data loss at this point in time. But having to manually doing the passphrase setup on 40 disks is not something I am looking forward to.
As there is no data written on them yet. It would be great if there would a command that we can use to get this revolved."
1818165,2019-03-01 01:50:06 UTC,"This isn't a total disaster; you can get the master key from dmsetup table --showkeys while the mapping still exists, and cryptsetup luksAddKey has a --master-key-file parameter you can use to add a known passphrase for adding to vault.  (I
m not sure if --master-key-file wants hex-encoded data, as printed by dmsetup, or binary.)"
1818165,2019-03-01 01:13:11 UTC,For reference I added the resulting lsblk of this host here: https://pastebin.canonical.com/p/Mwfzw4tzXY/
1818165,2019-03-05 14:40:34 UTC,Does the zap-disk action not manage to purge any cryptsetup from the block devices?
1818167,2019-03-05 20:10:19 UTC,No Gutenprint driver exists.
1818186,2019-03-03 23:46:01 UTC,"With Setup/copy/color at 75ppi and 75 ppi in the main menu, the images are satisfactory and identical to the results from Simple Scan at 75 ppi."
1818188,2019-05-23 10:07:39 UTC,Try to install guestOS with  ubuntu-19.04-server-amd64.iso in ESXi for more times.
1818188,2020-11-02 02:08:55 UTC,"As #17 say:
1) I hit this issue in ubuntu 19.04 with traditional installer but not the new installer ""subiquity"".
2) I did not hit such issue in ubuntu 19.10 server daily build Aug/28/2019"
1818188,2019-10-11 04:09:47 UTC,   > increasing the number of vCPUs can ensure the success of the install?
1818188,2019-10-10 22:12:25 UTC,"My apologies I got my bugs mixed up. Yes, this is the normal installer, not subiquity. Again without having access to the hardware or additional logs this is going to be difficult to triage."
1818188,2019-09-27 06:09:53 UTC,"> If this is fixed in the development release (eoan), can you retest with the latest installer from > disco? Please update the installer if prompted. You should have version 19.07.3 available to you > now.
"
1818188,2019-09-03 18:00:28 UTC,"If this is fixed in the development release (eoan), can you retest with the latest installer from disco? Please update the installer if prompted. You should have version 19.07.3 available to you now."
1818188,2019-09-02 07:44:36 UTC,No such issue in ubuntu 19.10 server daily build Aug/28/2019
1818188,2019-04-23 07:26:22 UTC,hit this issue ubuntu-19.04-server-amd64.iso (GA)
1818188,2019-03-06 09:05:37 UTC,"> Could you please provide more information as the vmware bugzilla is not accessible.
"
1818188,2019-03-27 07:00:21 UTC,This is urgent issue. Is any developer working on this ?   Thanks
1818188,2019-03-20 06:59:14 UTC,still hit the issue with ubuntu-19.04-server-amd64.iso daily build 19-Mar-2019
1818188,2019-03-07 02:40:30 UTC,"> What generation of HP machine was used? G7/Gen8/Gen9/Gen10? Is it running the latest iLO and
  RBSU (BIOS) firmwares?
"
1818188,2019-03-06 15:58:29 UTC,Thanks for the quick response. Please do get back to us about the generation and firmware information.
1818188,2019-03-05 19:56:55 UTC,Hi! Could you please provide more information as the vmware bugzilla is not accessible.
1818188,2019-03-01 05:59:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818188,2019-04-01 06:46:21 UTC,Hit the issue with disco-server-amd64.iso (daily build 2019-3-31) downloaded from http://cdimage.ubuntu.com/ubuntu-server/daily/current/
1818188,2019-03-05 19:58:11 UTC,Marking this as a debian-installer bug and as incomplete pending an update. Also marking the install-package task as invalid.
1818194,2019-09-06 21:37:42 UTC,I can't reproduce this issue.
1818194,2019-11-06 04:17:38 UTC,[Expired for mate-tweak (Ubuntu) because there has been no activity for 60 days.]
1818197,2019-08-04 19:18:56 UTC,"On Sun, Aug 4, 2019 at 1:21 PM Steve Dodd <email address hidden>
wrote:"
1818197,2019-04-26 19:02:03 UTC,I wonder what the config netplan generate complained about.
1818197,2019-08-04 17:10:46 UTC,"Having just been battling with this - config-set-passwords is run relatively late (config stage), which seems to mean the network has to be up properly before it is executed..
if you get dropped into maintenance mode, or manually edit the image to provide a log in, ""cloud-init status"" and ""cloud-init analyze show"" will tell you what is going on."
1818198,2019-03-04 13:42:25 UTC,"Hi,"
1818200,2019-03-06 12:15:56 UTC,All tasks have been completed and the bug is being set to Fix Released
1818200,2019-03-05 13:55:59 UTC,all tests completed
1818205,2019-03-01 10:10:12 UTC,a fix was suggested in https://code.launchpad.net/~mluto/mailman/qrunnersleep/+merge/363767
1818209,2019-03-06 00:44:31 UTC,Thanks for the report.
1818209,2019-03-06 01:06:27 UTC,Uhh is there some kind of special processing done where the device serial reported by udev is _not_ the name of the symlink in /dev/disk/by-id? Because that would be angry-making.
1818209,2019-03-06 01:12:08 UTC,"Ah well I see the rules (as in rules.d/60-persistent-storage.rules) for nvme really are different, so yes, probably need to look into this a bit."
1818209,2019-07-05 15:18:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818211,2019-03-04 15:29:37 UTC,Subscribing Marc (who did the recent uploads) but just as FYI
1818211,2019-03-04 15:28:39 UTC,The security Team usually keeps clamav up to date throughout releases - so if that is an issue upstream it woudl be fixed on the next merge. But the issue linked is not part of the clamav upstream.
1818211,2019-03-01 13:10:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818211,2018-06-25 17:15:56 UTC,"It wasn't quite clear at the offset of this bug, but ClamAV cannot support unofficial signatures from a development standpoint. For numerous reasons, we do not regress against those signatures, and in cases where sig writers publish non-functional signatures due to insufficient testing (which then cause crashes in newer versions of clam) we cannot devote our resources to fixing that problem."
1818211,2018-06-22 00:31:51 UTC,"I don't know you already know but just in case, antidebug_antivm.yar and EMAIL_Cryptowall.yar makes clamav-0.100 crashes"
1818211,2018-06-20 13:07:02 UTC,My solution to this was to remove the offending file from clamav-unofficial-sigs control file.
1818211,2018-06-20 12:29:38 UTC,My understanding (someone correct me if I'm wrong) is that the yara ruleset/database in question has been broken for a long time.
1818211,2018-06-20 02:05:26 UTC,"Hello ,
I have have this report https://bugzilla.redhat.com/show_bug.cgi?id=1590545 , and IMO we need a quick fix for clamav-0.100 ..."
1818211,2018-05-21 13:03:02 UTC,I agree that previously it looks as if the files failed to compile and as a result were ignored with the annoying side effect of the error messages coming out on stderr and appearing in places they shouldn't.
1818211,2018-05-11 11:51:30 UTC,"Marking as public so it can be referenced in the clamav-users list.
In addition, we have an internal (Jira) task to follow up on this issue."
1818211,2018-05-21 12:37:29 UTC,*** Bug 12103 has been marked as a duplicate of this bug. ***
1818211,2018-04-07 10:25:18 UTC,"Created attachment 7407
clamd std log"
1818211,2018-04-07 10:26:59 UTC,"Created attachment 7408
db packer.yar for example"
1818211,2018-04-07 10:24:33 UTC,"Created attachment 7406
backtrace with debuginfo"
1818211,2018-05-11 12:01:02 UTC,"Another user reported crash due to clamav handling of yara rule sets.
Source:
 clamav-users: http://lists.clamav.net/pipermail/clamav-users/2018-May/006185.html"
1818211,2018-05-21 12:40:03 UTC,It seems to me that the assertion fail 'crash' when using antidebug_antivm.yar comes about after this commit:
1818211,2018-05-18 00:28:56 UTC,"Created attachment 7427
Clamscan crash log"
1818211,2018-05-18 00:30:32 UTC,"I'm also using clamav-unofficial-sigs.sh, and I'm having clamscan crash."
1818211,2018-05-18 06:47:00 UTC,"In my case, clamav is used for the mail traffic (amavis, postfix, dovecot) and the webproxy (squid over c-icap).
Hardware: Intel xeon, 24GB ECC-Ram, Raid5.
System: ArchLinux
After the update to clamav 0.100 it came to coredums and the accesses to the Internet over the squid-proxy became unbearably slow.
The following steps helped me to get the system working almost normally again. However, the system load on the CPU is considerably higher with clamav 0.100 than with clamav 0.99.4.
But at least I can now use the system again, without having to turn off the virus protection altogether. There are about 30 workstations on the system that use the mail server and the proxy."
1818211,2018-05-16 20:38:30 UTC,*** Bug 12117 has been marked as a duplicate of this bug. ***
1818214,2019-09-11 11:26:54 UTC,"Trusty is now EOL (and firefox isn't included in the ESM edition), and since version 69.0 firefox in xenial isn't built with gcc any longer (clang is used instead)."
1818214,2019-03-08 13:26:39 UTC,gcc-mozilla 6.4.0-0ubuntu0.14.04.3 (trusty) and 6.4.0-0ubuntu0.16.04.4 in ppa:ubuntu-mozilla-security/ppa fix this.
1818215,2019-09-17 10:30:23 UTC,Occurd on an amd64 installation
1818216,2019-05-15 11:25:23 UTC,This was fixed on the 2.5 branch under https://github.com/juju/juju/pull/9807.
1818219,2019-03-05 07:56:40 UTC,"Didn't freeze overnight, so maybe 4.16 fixed the issue."
1818219,2019-03-01 11:30:07 UTC,This change was made by a bot.
1818219,2019-03-01 11:32:30 UTC,I attached my kern.log. Today (Mar 1 2019) this issue occurred sometime between 12:00 and 13:00.
1818219,2019-03-01 17:27:04 UTC,Hi Jussi:
1818219,2019-03-04 15:15:56 UTC,"Ok, I'm running 4.16 now. Let's what happens.."
1818221,2019-08-20 22:01:48 UTC,"This bug reads like a nice-to-have feature request.  If this bug has more context to drive a higher level of importance than 'wishlist,' please clarify. Thank you."
1818221,2020-01-16 13:55:44 UTC,"Reviewed:  https://review.opendev.org/701755
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=03cb557fc8afc9526cd32d13b0fe7162f10d8c24
Submitter: Zuul
Branch:    master"
1818222,2019-03-11 08:12:48 UTC,same here :/
1818222,2019-03-11 08:13:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818222,2019-10-02 13:50:10 UTC,as a workaround you may want to use
1818230,2019-03-01 13:29:48 UTC,"$ juju --version
2.5.2-bionic-amd64"
1818230,2019-10-08 20:27:50 UTC,bump!
1818230,2019-10-08 21:59:41 UTC,"Fumbling around trying to see what is going on here, I've commented out all charm code pertaining to the peer relation to see if things still error when a second unit is added."
1818237,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1818239,2019-09-13 17:33:53 UTC,"Since this has come up again in bug 1581977 as representing a security-related concern, I'm adding the security bugtag to it for increased visibility. Note this is not the same as treating it as a security vulnerability, and I don't have the impression that any CVE assignment or security advisory is warranted for this."
1818239,2019-03-05 22:05:36 UTC,"@James: per comment 2, see bug 1816360 :) Easy fix for that."
1818239,2019-03-05 22:35:11 UTC,"I've marked this as incomplete for nova since I'm not aware of any changes being asked to make here. The build failure weigher was added because of bug 1742102 and in response to operator feedback from the Boston summit to auto-disable computes if they experienced a build failure. So the auto-disable thing went into I think Pike, and then bug 1742102 talked about how that was too heavy weight because there were easy ways to auto-disable a lot of computes in a deployment (e.g. volume over-quota from multiple concurrent boot from volume server create requests). So Dan added the weigher stuff which can be configured to weigh hosts with build failures lower so they don't become a black hole, and once the host has a successful build the stats tracking for that compute node is reset."
1818239,2019-03-06 17:20:07 UTC,"Chris: I don't doubt that this could be a crippling incident, but you say you took down your own cloud and did so accidentally... can you provide a similar scenario where a non-admin user is able to intentionally bring about the same result? That's mostly what I'm looking for to be able to formulate an appropriate impact description for a possible security vulnerability advisory publication."
1818239,2019-03-05 19:44:31 UTC,"On Tue, 2019-03-05 at 18:30 +0000, Corey Bryant wrote:

> @Jeremy, I think it's more of limited denial of service (if we can
> call
> it that) where a certain amount of computes could get negative weight
> and not considered for scheduling. I don't think it's a complete
> denial
> of service.
"
1818239,2019-03-06 14:33:01 UTC,"Matt, What is your opinion on nova disabling the build failure weigher by default. It would then be secure by default, without any exposure to degradation of service attacks, and folks can opt in to it if they want. Btw, did you mean to triage as won't fix or incomplete? I think we have enough details to describe the issue but if anything else is needed please let us know."
1818239,2019-03-06 18:25:59 UTC,"With the weigher, you shouldn't be able to ""take down"" anything. You may stack a lot more instances on the non-error-reporting hosts, but once those are full, the scheduler will try one fo the hosts reporting errors, and as soon as one succeeds there, the score resets to zero. So can you clarify ""took down"" in this context?"
1818239,2019-03-06 07:15:17 UTC,@fungi - we accidentally took down 9/12 of the hypervisors in our QA cloud with this; 75% isn't quite a complete denial of service but definitely degraded the capacity significantly
1818239,2019-03-05 18:55:31 UTC,"Thanks! I'm mostly looking for an exploit scenario whereby a malicious actor can intentionally cause harm/deny access to the operating environment for other users. Absent this, we'd probably not bother to issue a security advisory about it."
1818239,2019-03-06 14:23:29 UTC,@mriedem - yeah that was my hack but I see you beat me to raising a review...
1818239,2019-03-05 18:11:55 UTC,Is the denial of service concern that an authenticated user could engineer a build failure (perhaps by attempting to boot an intentionally corrupt image they uploaded) and perform that action repeatedly to cause the environment to no longer to be able to schedule instances to any of the hypervisor hosts through which their build failures rotated?
1818239,2019-03-05 18:30:17 UTC,"@Jeremy, I think it's more of limited denial of service (if we can call it that) where a certain amount of computes could get negative weight and not considered for scheduling. I don't think it's a complete denial of service. For example, in the case you've mentioned the failure weight would become somewhat equivalent for all nodes if they all have a negative weight."
1818239,2019-03-01 14:11:24 UTC,as a side note its really hard to see the calculated weights for each host in the scheduler as the weighting is stripped before the debug log message is made here:
1818239,2019-03-01 14:50:25 UTC,for further context the only way I could find to reset the build_failures value for a hypervisor was to restart its nova-compute daemon.
1818239,2019-03-01 14:52:13 UTC,related bug 1742102
1818239,2019-03-05 15:05:34 UTC,"Opening this back up against the package and adding upstream as well. I may be missing something, but I think this is still an issue upstream."
1818239,2019-03-04 09:29:21 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640698"
1818239,2019-03-05 07:45:28 UTC,"Reviewed:  https://review.openstack.org/640698
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=c5029e9831ab5063485877213987d6827c4d86f1
Submitter: Zuul
Branch:    master"
1818239,2019-03-05 09:27:07 UTC,"Fix proposed to branch: stable/18.11
Review: https://review.openstack.org/640961"
1818239,2019-03-02 14:44:04 UTC,"Based on the fix for bug 1742102 a successful build on the host should reset the failure count to zero, but it seems impractical to get a successful build if it has a low weighting. So the code does still seem to leave the ability for a user to intentionally increase the failure count and lower the weight for a compute node or nodes, limiting the number of nodes an instance can be scheduled to."
1818239,2019-03-05 15:11:59 UTC,"Reviewed:  https://review.openstack.org/640961
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=56de84a81be00bf9ddffca4426d28c17d5d9798e
Submitter: Zuul
Branch:    stable/18.11"
1818240,2019-03-01 20:24:16 UTC,"If using git is possible, I could contribute as time permits."
1818240,2019-03-01 20:44:06 UTC,I have current no plans to switch to git. But there are mercurial to git bridges available.
1818240,2019-04-07 07:28:06 UTC,I unified some strings in the code. If you find other one please add them to this ticket.
1818243,2019-10-04 19:25:45 UTC,"Can you explain why this issue was closed with ""won't fix""?  I still see it in Disco."
1818243,2019-09-27 20:18:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818253,2019-03-06 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818253,2019-03-06 17:49:28 UTC,Sorry about that.
1818253,2019-03-18 16:02:42 UTC,The previously posted log was from this nightmare:
1818260,2020-06-02 18:50:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/732928"
1818260,2020-06-03 12:48:10 UTC,Subscribing field-high as this as killed another run: https://solutions.qa.canonical.com/#/qa/testRun/9f4bff3c-9f2e-47bb-ab93-792dc781c7d8
1818260,2020-06-03 17:19:10 UTC,"Fix proposed to branch: stable/20.05
Review: https://review.opendev.org/733285"
1818260,2020-06-03 17:23:25 UTC,"Michael,"
1818260,2020-07-20 16:20:23 UTC,"Fix proposed to branch: stable/20.05
Review: https://review.opendev.org/741983"
1818260,2020-06-10 12:59:08 UTC,"Reviewed:  https://review.opendev.org/733285
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=2cd2962c2b3582339577b6aabddcb95e681c8f03
Submitter: Zuul
Branch:    stable/20.05"
1818260,2020-06-16 08:32:50 UTC,"Reviewed:  https://review.opendev.org/732928
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=5318764cc6be62d54ba1bb4d998301f81fb2c63e
Submitter: Zuul
Branch:    master"
1818260,2020-07-20 16:02:48 UTC,Saw this crop up again during this run: https://solutions.qa.canonical.com/qa/testRun/1a4cbc69-b1ca-49d2-8faa-187529727f76
1818260,2020-06-02 17:26:01 UTC,"Reviewed:  https://review.opendev.org/732465
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=f1c3deac35138a5e0c8ecc5a3004a838f0322b95
Submitter: Zuul
Branch:    master"
1818260,2020-08-13 14:34:31 UTC,"Change abandoned by David Ames (<email address hidden>) on branch: stable/20.05
Review: https://review.opendev.org/741983
Reason: Released in 20.08"
1818260,2020-06-03 18:06:42 UTC,"David,"
1818260,2020-06-01 22:25:00 UTC,"I believe [0] will resolve this for SQA. However, I would like to discuss with Frode Nordahl, the original author of the check and removal code, on alternative approaches."
1818260,2020-06-01 13:22:49 UTC,Hit this again during stable testing: https://solutions.qa.canonical.com/#/qa/testRun/4cbf05c9-036d-4445-80cd-086f4b1a0e19
1818260,2020-06-01 22:22:59 UTC,The fix [0] for a 2017 bug [1] is colliding during deployment. The leader node is running update-status simultaneously as a non-leader node is joining the cluster. Such that the check_cluster_membership thinks the non-leader is a dead node and attempts to remove it.
1818260,2019-03-01 16:32:00 UTC,Full crash-dump logs
1818260,2020-06-01 22:23:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/732465"
1818260,2019-03-05 14:50:36 UTC,The first log message in the bug report would not confirm that:
1818260,2019-03-05 14:52:35 UTC,Please check the settings for 'landscape-rabbitmq-server' not 'rabbitmq-server'.
1818260,2019-03-01 16:47:57 UTC,"In the bundle, rabbitmq-server min-cluster-size is set to 3."
1818260,2019-05-03 20:08:53 UTC,The approach we need to take is the following:
1818260,2020-05-11 16:19:40 UTC,"We hit it again.
https://solutions.qa.canonical.com/#/qa/testRun/a254b67c-c212-4aa7-bf48-68560c820b79"
1818260,2020-05-26 16:08:41 UTC,Had another instance of this here: https://solutions.qa.canonical.com/#/qa/testRun/e4d4a810-1e68-45a2-89c2-6bbf2e4f5124
1818260,2020-06-01 14:53:26 UTC,UPDATE:
1818260,2019-04-19 17:20:13 UTC,QA caught this and Alex Kavanagh has also seen it:
1818260,2020-03-24 17:40:44 UTC,we hit this again today in SQA
1818267,2019-05-14 03:55:20 UTC,"$ smartctl -c /dev/sdX
supported"
1818268,2019-09-20 12:07:53 UTC,"The snapd repository has the COPYING file.
The core18 repository lacks one.
The core16 repository has the COPYING file."
1818272,2019-09-19 14:54:35 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1818273,2019-06-21 13:48:20 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1818273,2019-06-21 15:25:56 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1818273,2019-03-25 16:41:03 UTC,"Reviewed:  https://review.openstack.org/644550
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=86c8de92b3ac5758b152dc0c1f996f5d9c7aab38
Submitter: Zuul
Branch:    stable/queens"
1818273,2019-03-18 19:57:51 UTC,"Reviewed:  https://review.openstack.org/640480
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=9ae5fd8f35bb9c337f040b7181eb3b66ae04ffc8
Submitter: Zuul
Branch:    stable/rocky"
1818273,2019-03-01 18:07:18 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/640480"
1818273,2019-03-19 11:47:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/644550"
1818274,2019-03-01 18:02:25 UTC,Related but not duplicate: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1742443
1818275,2019-04-02 12:10:51 UTC,"Please collect some logs, let us check if oem-audio-dkms is installed or not on your machine."
1818275,2019-04-02 14:44:40 UTC,"Yes. I have the sound back again. The ""Speakers"" is showing in sound settings."
1818275,2019-04-02 14:21:37 UTC,"Just for completeness, at least the upgrade pulled in the new linux-modules and linux-modules-extra as it was supposed to do. Also saw that the update seems to have gone from 3.13.0-161 to 3.13.0-167 so this means a larger delta has to be considered. And one more note, there seem to be a large number of previous kernels still installed. This can cause issues with completely full filesystems (especially if /boot is small and separate). Unfortunately back in Trusty automatic purging did not work or was not yet implemented. So one had to do it manually (maybe ""sudo apt-get autoremove --purge"" works but one would need to be careful that neither -161 nor -167 appear in the list)."
1818275,2019-04-02 13:04:17 UTC,let us try to remove oem-audio-hda-daily-dkms.
1818275,2019-04-02 12:41:23 UTC,modinfo-hda-intel.txt
1818275,2019-04-02 12:40:34 UTC,dkms-status.txt
1818275,2019-04-02 12:39:53 UTC,dpkg-list.txt
1818275,2019-04-02 10:21:19 UTC,"yes, the list of all linux packages installed is attached"
1818275,2019-03-05 03:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818275,2019-04-02 08:58:59 UTC,I have no idea.
1818275,2019-04-02 08:14:44 UTC,"somehow I can't load the driver
That is what I am get when I do sudo modprobe snd_hda_intel:"
1818275,2019-04-02 00:09:18 UTC,"The driver module is there and it is not in the blacklist, then load the driver manually and upload the dmesg:"
1818275,2019-04-01 13:18:06 UTC,"hi,"
1818275,2019-04-01 06:11:06 UTC,"The sound driver snd_hda_intel.ko is not loaded when kernel is booting. Please check /lib/modules/$your-kernel_version/kernel/sound/pci/hda/, if there is snd_hda_intel.ko. If there is, please check /etc/modprobe.b/blacklist.conf, if putting the driver in the blacklist?"
1818275,2019-04-01 02:00:15 UTC,This is a surprisingly popular bug judging by the duplicates.
1818275,2019-03-08 02:24:46 UTC,It sounds like the problem started with kernel 3.13.0-165.215-generic which was released on 4 Feb 2019.
1818275,2019-03-05 09:00:12 UTC,Does this issue happen on previous kernel version?
1818275,2019-04-02 09:18:16 UTC,It definitively sounds like that. Normally I would expect an installation to have linux-generic or at least linux-image-generic installed which are meta-packages that pull in all dependencies. Could we get a full listing of all linux related packages installed right now? (dpkg -l|grep linux)
1818280,2019-07-02 01:45:08 UTC,"I had to take a break for a few days. I did install tornado and tested again just now but still get the problem of the program hanging after CTRL Q or click the close (x button).
In case it's relevant, this is a quite old (~2012) computer that is rather slow anyway. Hoping to upgrade it later this year."
1818280,2019-06-26 03:39:03 UTC,"Try updating tornado. First exit Rapid Photo Downloader, then:"
1818280,2019-06-26 03:16:56 UTC,"The original problem was what I saw again. ie: after a test download of 168 images, when I try to close the program, it just hangs and then eventually puts up a 'not responding' message with option to wait or force quit.
On the other hand, if I just open RPD and don't do any download and just close it with CTRL Q, it quits immediately, as you would expect.
That was the only new log file I could find. The other 2 most recent log files were from a few days ago, prior to downloading your beta 1 version which I did tonight."
1818280,2019-06-26 02:51:15 UTC,"What precisely do you mean by failure to close with 0.9.15b1? It looks like it closed just fine, without the database error. There is nothing in the log file indicating an error. What did you see?"
1818280,2019-06-26 02:24:06 UTC,this is the most recent log file after failure to close using 0.9.15b1
1818280,2019-06-20 20:22:42 UTC,And a fourth. (I have several more but hopefully that's sufficient.)
1818280,2019-07-03 20:11:38 UTC,It's possible the problem might be caused by the downloaded files database — it's hard to say because the problem is not showing up in the log file. You could try clearing it. See for details how: https://damonlynch.net/rapid/documentation/#commandline
1818280,2019-06-20 20:21:05 UTC,Another log file
1818280,2019-06-20 18:41:29 UTC,Here is another compressed log file.
1818280,2019-06-20 18:41:28 UTC,Here is another compressed log file.
1818280,2019-06-20 18:39:56 UTC,"Sorry for leaving this idle so long.
Since posting this I have updated Ubuntu now to 19.04 and did a test of closing the program after a photo download. It seemed to close alright, but was a bit slow doing so. I have seen the original problem up until this recent system update.
Here is the log file. It seems I can only attach one file and not several. I also have ~10 other files labeled rapid-photo-downloader.log1-gz up to ...log.10.gz"
1818280,2019-06-20 12:20:10 UTC,"Please respond to the query, or else the bug will be closed. Sorry, but sometimes it is not possible to fix bugs where information I ask for is not provided."
1818280,2019-03-01 20:48:05 UTC,"Please attach all the log files (there should be three more in compressed format), and the configuration file."
1818280,2019-06-20 20:21:54 UTC,A third log file.
1818286,2019-10-15 20:43:28 UTC,Fix released for eoan; needs backport to bionic and disco.
1818287,2019-03-01 20:11:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/640505"
1818287,2019-03-01 22:37:04 UTC,"Reviewed:  https://review.openstack.org/640505
Committed: https://git.openstack.org/cgit/openstack/puppet-openstack-integration/commit/?id=93af9524ceb598cae2df637c93ac7009cb636f05
Submitter: Zuul
Branch:    stable/queens"
1818295,2019-03-24 23:39:05 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1818295,2019-03-22 03:43:09 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1818295,2019-03-22 02:55:19 UTC,"Reviewed:  https://review.openstack.org/642863
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=229101e6af234a8f051544d07fbf01964ec39c34
Submitter: Zuul
Branch:    master"
1818295,2019-03-21 15:59:58 UTC,"Reviewed:  https://review.openstack.org/643098
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d4cea970c2d56ef8ff813473cd5ba0e38e3f04fd
Submitter: Zuul
Branch:    stable/rocky"
1818295,2019-03-13 12:08:49 UTC,"Reviewed:  https://review.openstack.org/640879
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e082bdc166cb8215576801e0c89ef1fe771681ed
Submitter: Zuul
Branch:    master"
1818295,2019-03-12 19:11:39 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/642863"
1818295,2019-03-04 21:32:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640879"
1818295,2019-03-13 16:30:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/643098"
1818302,2019-03-01 22:23:59 UTC,Logs
1818304,2019-03-01 22:30:18 UTC,An acceptable alternative would be a supported version of mkusb or equivalent
1818304,2019-03-01 22:30:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818306,2019-03-06 14:46:05 UTC,Note: I see this behavior with both the stable channel of the core snap (revision 6405 - snapd version 2.37.2) and also with the edge channel of the core snap.
1818306,2019-04-11 00:16:52 UTC,This also happens on a revert and still happens with snapd 2.38
1818306,2019-05-02 23:38:32 UTC,"A somewhat hacky workaround for this is to save the state of the services that ought to be disabled in config settings, then in the configure hook stop and disable those services based on the state in the config settings.
This isn't a full fix because after a refresh, all services are still started (and the install is still aborted if any of them fail), but at least with this workaround after the refresh tasks run the services that were disabled will be disabled again. This assumes that the services can at least ""somewhat start"" such that the installation doesn't get aborted however."
1818306,2019-06-19 20:50:01 UTC,"This also happens when calling `snap disable snap-name` and then doing `snap enable snap-name`, i.e. this flow is broken:"
1818309,2019-03-07 18:01:00 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1818312,2019-03-02 02:00:04 UTC,This change was made by a bot.
1818314,2019-03-05 01:02:18 UTC,"Change abandoned by wanghao (<email address hidden>) on branch: master
Review: https://review.openstack.org/640564
Reason: same patch as https://review.openstack.org/#/c/625396/"
1818314,2019-03-02 04:00:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640564"
1818315,2019-03-04 10:09:06 UTC,"Right, it's likely that the system was busy doing a refresh of the indexes or even installing security upgrades in background, those situations are not reflected nicely in the graphical session (and the gnome-software warning is not really nice either)"
1818315,2019-03-04 01:22:11 UTC,"Eventually, I got an upgrade notification (it listed a bunch of packages which were scheduled to be updated). I assume whatever process was doing silent updates in the background grabbed the lock, and once I closed the dialog software centre was able to install packages."
1818315,2019-03-02 13:00:11 UTC,"Thank you for your bug report, as indicated by the error message (which could probably be a bit nicer/user friendly) the packaging system seems currently locked by another proceess. Did you have any other packaging tools in use at the time? Did that resolve itself after some time?"
1818318,2019-03-04 16:20:46 UTC,"Another issue with DNS filtering. Looks like the Neutron Mitaka is capable to filter _ports_ by ""dns_name"", but the Neutron Queens returns all the ports."
1818318,2019-07-30 11:56:39 UTC,Any news on this?
1818318,2019-09-13 09:40:38 UTC,Do you have any news on this issue? It broke automation once neutron was upgrade from mitaka to queens.
1818318,2019-12-14 09:37:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/699062"
1818318,2019-12-14 09:38:50 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/699063"
1818318,2019-12-16 23:47:28 UTC,"Reviewed:  https://review.opendev.org/699062
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=79cd582084c4b23626a83a2e9059cb5c6e6a29ee
Submitter: Zuul
Branch:    master"
1818318,2020-09-25 15:45:39 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/699063
Reason: This review is > 4 weeks without comment, and failed Zuul jobs the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1818320,2019-03-02 09:18:43 UTC,"guess what: it is in the todo for long, and I do have event the status enum into the code.
so let's go with this :)"
1818321,2019-03-02 19:19:10 UTC,"@Wayne,"
1818321,2019-03-02 19:01:22 UTC,"@Miljan, the pad stack file format changes will most likely be discussed once someone has time to work on it.  If we discuss it to far ahead of time, the information tends to get lost on the developers mailing list so it's best to wait."
1818321,2019-03-02 18:45:31 UTC,"@Wayne,"
1818321,2019-03-02 18:09:51 UTC,"Hi Wayne,"
1818321,2019-03-02 17:58:13 UTC,"AFAIK, we do not support via anti-pads at the moment unless I'm misunderstanding what you mean by anti-pad."
1818321,2019-03-02 18:22:54 UTC,"@Miljan, thanks for the response.  We have talked about adding pad stacks to pcbnew during the version 6 development period.  I just haven't found the time to update the v6 road map.  It's on my short list as soon as we get 5.1 released."
1818323,2019-03-02 13:17:39 UTC,"In the meantime, hold ""Alt"" key and the snap will be easier as it avoids grid."
1818332,2019-03-06 23:28:35 UTC,"That's a good point, Jane -- +1 to some manner of in-place alert for this"
1818332,2019-08-08 14:23:22 UTC,"AFAICT, the workstation registration issue is indeed a regression from 3.1, which restricted that to those OUs with can_have_users set to true.  I suspect a problem with the OU flag checks and disabling selection when they (can_have_users and can_have_vols) was introduced when the widget was improved between 3.1 and 3.3 to add type-to-search and the like."
1818332,2019-03-07 20:23:55 UTC,"You can add sample data, complete with an org tree, users, and items if you add the --load-all-sample option to the eg_db_config step as mentioned in the README.  This data is not ideal for production use, but can be used for kicking the tires and is required for running the Evergreen automated tests.  There is documentation on the users added with the sample data set here:"
1818332,2019-03-07 19:33:35 UTC,"Hi,"
1818332,2019-03-04 20:40:14 UTC,"How about documentation at the point of need: like a little informative alert on the workstation admin screen that pops up when egadmin attempts to create a workstation at the CONS level?  Brand new users tend to get confused at the workstation registration screen anyway, so I'd prefer something that doesn't require them to look in the documentation first."
1818332,2019-03-04 16:54:07 UTC,+1 to considering this a documentation bug. Almost anything's okay as long as you document it. ;)
1818332,2019-03-04 16:16:02 UTC,"I think you're right, Andrea.  Unfortunately, the master admin login is the one that people testing out the system are most likely to be using. :-("
1818332,2019-03-04 15:59:07 UTC,"I may be wrong but I think this only happens when using the master admin login, because that is a special case as it ""lives"" at CONS."
1818332,2019-03-03 15:42:29 UTC,"So glad that it's working, Sören.  I do want to leave this bug open, because it does make it more difficult for people to evaluate Evergreen."
1818332,2019-03-03 10:38:19 UTC,"Hi,"
1818332,2019-03-02 17:29:10 UTC,"Hi Sören!  Thanks for your report.  Just to check, what is the value in the ""Owning Library"" dropdown (see attached screenshot)?  The ""Save and Exit"" button will fail if you attempt to add holdings to a consortium or system, rather than an individual library or branch.  Could you please try it again using a different Owning Library?"
1818332,2019-03-04 16:41:02 UTC,"Fair.  I believe there are Actual Reasons for having that login owned at CONS, so perhaps this should be considered a documentation bug?"
1818338,2019-03-04 11:43:44 UTC,Thank you for your bug report. WHat Ubuntu version do you use?
1818338,2019-04-06 11:18:08 UTC,"Thank you for your feedback and sorry for the delay. I looked at commit 675ff4be and compared it with the patch I referenced, which removes the xkb_symbols section in symbols/inet."
1818338,2019-04-06 22:54:56 UTC,"@Benjamin,"
1818338,2019-06-18 10:03:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818341,2019-03-07 09:30:05 UTC,"If your original problem was only about bluetooth sound quality, check the Profile shown in your Sound settings, confirm it is set to A2DP and not HSP/HFP."
1818341,2019-03-07 10:37:22 UTC,"Thanks for replying,"
1818341,2019-03-02 15:30:07 UTC,This change was made by a bot.
1818342,2019-03-03 18:50:31 UTC,OK so this is tricky because of the library view header state.
1818342,2019-03-17 12:02:53 UTC,WIP: https://github.com/mixxxdj/mixxx/pull/2046
1818342,2021-01-11 23:37:59 UTC,superseded by https://github.com/mixxxdj/mixxx/pull/3063
1818345,2019-04-05 07:43:51 UTC,"The 'device' seems optional in code.
But I cannot find cases that 'mountpoint' is not set.
Which case isn't 'mountpoint' set?"
1818345,2019-04-05 13:57:17 UTC,"What about the block_device_mapping_v2.no_device case? I don't know off the top of my head where mountpoint wouldn't be set, but the API logic clearly allow for not exposing a device if there isn't one on the BDM - maybe there was a legacy BDMv1 case for this, I'm not sure."
1818345,2019-10-22 19:09:46 UTC,See bug 1554440 - if the volume is attached to a shelved offloaded server with microversion 2.20+ then there is no device_name on the BDM object and mountpoint is None so 'device' is not returned.
1818345,2019-10-22 19:28:49 UTC,Fix is here: https://review.opendev.org/#/c/690383/
1818345,2019-10-22 19:36:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/690383"
1818345,2020-03-03 00:23:58 UTC,"Reviewed:  https://review.opendev.org/690383
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ee0da7e5bffcfa70bfae60d60345c42fbc881b9
Submitter: Zuul
Branch:    master"
1818348,2020-12-15 09:34:54 UTC,"the fix is not in any upstream release yet, it should land with GNOME 39 this cycle though"
1818348,2020-12-15 03:56:04 UTC,"This is fixed in the upstream, when is it expected to land in Ubuntu?"
1818348,2019-03-04 21:31:15 UTC,"Reported at https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/124. Launchpad won't let me link to that external bu report, says it doesn't recognize it."
1818348,2019-03-05 10:10:42 UTC,Thanks (and lack of gitlab support in launchpad is known/being worked on)
1818348,2019-03-04 11:43:48 UTC,"Thank you for your bug report. That's probably because the buttons box is then 'docked'  to the sidebar and the buttons don't fully fit in that width. That's an upstream issue, ideally to report to them on https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues"
1818350,2019-03-02 19:00:07 UTC,This change was made by a bot.
1818350,2019-03-04 10:45:26 UTC,"Thank you for your bug report, it's not exactly clear to me what's the problem you are reporting but there are several problems there
- the debconf dialog opened in the background, not making obvious that the update is blocked on input
- the way debconf is listed with a question mark is suboptimal
- the fact it's prompting/failing to communicate why it's prompting about?"
1818350,2019-03-04 10:47:44 UTC,"(reading again, the report is about trusty, that's something that got improved in newer versions of Ubuntu)"
1818350,2019-03-05 22:58:26 UTC,"@Brian, gnome-software doesn't pop up nor install updates, that's more like update-manager being used there"
1818351,2019-03-07 18:00:47 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1818352,2019-03-02 20:20:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1818356,2019-07-20 11:07:35 UTC,"> We rarely sync new packages into stable releases;
"
1818356,2019-05-17 09:03:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818356,2019-12-01 21:26:03 UTC,"The snap has restrictions that the pdftk-java package from Cosmic does not have: the snap refuses to process files in /tmp (even when the directory has been created securely with mkstemp), which makes it unusable for some server workloads, including mine."
1818356,2019-03-02 23:55:05 UTC,*** This is an automated message ***
1818356,2019-03-02 19:59:23 UTC,I have downloaded the Cosmic pdftk-java package and managed to install in on 18.04.2.
1818356,2019-04-20 20:12:34 UTC,"Hello Ciarán, thank you for the bug report."
1818358,2019-03-05 13:23:56 UTC,"I have attached another image which better shows how the image is being improperly rendered in the upper displays of both live and preview.  This image was taken on a 42"" monitor."
1818358,2019-08-22 23:20:19 UTC,I saw this on Windows when a backup was made on a large screen laptop and installed on a smaller screen laptop using version 2.4.6.
1818359,2019-09-19 08:49:20 UTC,"This seems like the Machiner isn't properly inventorying the network interfaces when bootstrapping with LXD. Which seems surprising, and seems worth investigating."
1818359,2019-09-24 08:31:37 UTC,"Looks like the machiner is populating link-layer devices correctly.
It is particular to `network-get` for the LXD provider."
1818359,2019-09-24 09:02:21 UTC,This will occur for providers that do not support subnet discovery.
1818359,2020-02-21 10:26:25 UTC,https://github.com/juju/juju/pull/11241
1818363,2019-03-14 08:46:10 UTC,The console output of an earlier working version may be helpful.
1818363,2019-03-14 14:46:47 UTC,"as you can see I have -t 120 with the output below with no issue,"
1818363,2019-03-11 19:35:13 UTC,"as requested .... output without the ""-t"" option,"
1818363,2019-03-19 01:03:29 UTC,"Here are the ffmpeg versions,"
1818363,2019-05-20 04:17:19 UTC,[Expired for ffmpeg (Ubuntu) because there has been no activity for 60 days.]
1818363,2019-03-12 20:29:06 UTC,"I have proven that this works in a previous version so I am relucktant to agree that this is not related to the ""-t"" option. Do you want to see the output from that version (using previous LTS version of Ubuntu)?"
1818363,2019-03-18 16:48:42 UTC,"Isn't the point of this bug report that current FFmpeg quits after 30 seconds while older FFmpeg works for longer - completely independent of the ""-t"" option?
Anyway, please run git bisect to find the change introducing the issue as I don't think there is another way to understand this issue.
FFmpeg compilation by default produces static libraries and a binary that you do not have to install, it can be tested from the build directory, the issue should be reproducible with ""./configure && make ffmpeg"" if you use ""-vcodec mpeg4 -qscale 5"" as encoder."
1818363,2019-03-12 19:38:48 UTC,Do you agree that the issue is (most likely) unrelated to the option -t?
1818363,2019-03-05 15:40:26 UTC,"You are using an input option (it used to be a global option in the past) that apparently does not (or cannot) work for your input, please use the output option that is supposed to work as expected."
1818363,2019-03-10 19:48:42 UTC,"How does the console output look without any ""-t"" option specified?"
1818363,2019-03-10 03:04:07 UTC,"I have tried the ""-t"" before the output URL with the same result. The command exits prematurely."
1818363,2019-03-09 19:47:27 UTC,"Instead of the input option ""-t"" (that used to be a global option) please use the output option ""-t""."
1818363,2019-03-05 19:16:07 UTC,"Using the ""-to"" option doesn't work either. If this is not the option you mean please advise on the option I should be using."
1818363,2019-03-03 00:44:21 UTC,"I confirmed the same command works on,
$ lsb_release -rd
Description:	Ubuntu 16.04.1 LTS
Release:	16.04"
1818363,2019-03-03 00:23:10 UTC,Output below. The feed is an IP camera so it is a constant stream. I am setting up another Ubuntu 16.04 instance to see if that still works.
1818363,2019-03-02 23:37:59 UTC,What's the output of that ffmpeg command?
1818371,2019-03-03 16:19:04 UTC,Please disregard my first bug description in my post #1.  Apologies for this confusion.
1818371,2019-03-03 02:56:28 UTC,"Ubuntu 18.04.2
Canon Pixma TS6220
These issues are similar to an earlier bug (#1818186) that I reported regarding the operation of Xsane."
1818378,2019-03-06 11:15:00 UTC,I cannot reproduce this with ccsm 0.9.14.1. Probably it was fixed when we switched from GTK 2 to GTK 3.
1818381,2019-03-09 23:30:16 UTC,apport information
1818381,2019-03-09 23:30:18 UTC,apport information
1818381,2019-03-09 23:30:20 UTC,apport information
1818381,2019-03-09 23:30:21 UTC,apport information
1818381,2019-03-09 23:30:23 UTC,apport information
1818381,2019-03-09 23:30:25 UTC,apport information
1818381,2019-03-09 23:30:26 UTC,apport information
1818381,2019-03-09 23:30:28 UTC,apport information
1818381,2019-03-05 04:46:56 UTC,apport information
1818381,2019-03-09 23:30:31 UTC,apport information
1818381,2019-03-09 23:30:33 UTC,apport information
1818381,2019-03-09 23:30:35 UTC,apport information
1818381,2019-03-09 23:34:17 UTC,"This time, I replicate the issue and run apport-collect afterward (requested by developer). I hope this helps!"
1818381,2019-03-11 04:08:31 UTC,Looks like it's not Hibernate (S4) but Suspend (S3).
1818381,2019-03-12 02:01:06 UTC,Okay. I checked the POWER setting. You're correct. It only showed Suspend (no hibernate).
1818381,2019-03-09 23:30:15 UTC,apport information
1818381,2019-03-09 23:30:29 UTC,apport information
1818381,2019-03-09 07:43:23 UTC,Yes please.
1818381,2019-03-03 01:58:10 UTC,Last attached
1818381,2019-03-05 08:16:03 UTC,Are the logs collected after hibernation?
1818381,2019-03-03 01:57:04 UTC,Another logfile attached
1818381,2019-03-03 01:57:44 UTC,Another attached
1818381,2019-03-03 02:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818381,2019-03-08 19:58:01 UTC,"Sorry. I was very busy this week. Ugh. Hmm. No. I did ""apport-collect"" long
after the incident (Sat) on Monday evening."
1818381,2019-03-05 04:46:54 UTC,apport information
1818381,2019-03-05 04:46:58 UTC,apport information
1818381,2019-03-05 04:46:59 UTC,apport information
1818381,2019-03-05 03:22:53 UTC,"Jeff, please run 'apport-collect 1818381', we need more information to diagnose the problem."
1818381,2019-03-05 04:47:01 UTC,apport information
1818381,2019-03-05 04:47:03 UTC,apport information
1818381,2019-03-05 04:47:04 UTC,apport information
1818381,2019-03-05 04:47:07 UTC,apport information
1818381,2019-03-05 04:47:08 UTC,apport information
1818381,2019-03-05 04:47:10 UTC,apport information
1818381,2019-03-05 04:47:14 UTC,apport information
1818381,2019-03-05 04:47:00 UTC,apport information
1818387,2019-03-07 17:57:56 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1818391,2020-04-28 04:02:25 UTC,This bug was fixed in the package libdist-zilla-perl - 6.014-1
1818392,2020-07-27 16:02:42 UTC,apport information
1818392,2020-07-27 16:02:34 UTC,apport information
1818392,2020-07-27 16:02:36 UTC,apport information
1818392,2020-07-27 16:02:55 UTC,apport information
1818392,2020-07-27 16:02:40 UTC,apport information
1818392,2020-07-27 16:02:43 UTC,apport information
1818392,2020-07-27 16:02:33 UTC,apport information
1818392,2020-07-27 16:02:45 UTC,apport information
1818392,2020-07-27 16:02:47 UTC,apport information
1818392,2020-07-27 16:02:48 UTC,apport information
1818392,2020-07-27 16:02:51 UTC,apport information
1818392,2020-07-27 16:02:53 UTC,apport information
1818392,2020-07-27 16:02:44 UTC,apport information
1818392,2020-07-27 16:02:31 UTC,apport information
1818392,2020-07-27 16:02:39 UTC,apport information
1818392,2020-07-27 16:02:27 UTC,apport information
1818392,2020-07-27 16:02:29 UTC,apport information
1818392,2019-03-03 11:27:29 UTC,There is an error with the command:
1818392,2019-03-03 11:35:16 UTC,I cannot change the package name of this issue from linux to linux-image-4.18.0-15-generic.
1818392,2019-03-28 10:54:14 UTC,Can someone else reproduce the problem?
1818392,2019-09-05 12:53:13 UTC,"A new kernel panic happened when upgrading to Ubuntu 19.04, any idea why? The workaround is to select an older Linux kernel version like 4.18.0-17-generic."
1818392,2019-09-05 13:06:10 UTC,"I am using Dell XPS 13 Developer Edition, revision 2."
1818392,2019-03-03 11:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818392,2020-01-31 09:33:30 UTC,Always at boot time. I have to select the previous Linux kernel.
1818392,2020-02-04 10:50:22 UTC,"Please test 20.04 daily image.
If the issue persists, please attach log or screenshot here."
1818392,2020-04-04 20:15:36 UTC,"I prefer to avoid installing daily images on my laptop since I use it for work. But anyway I noticed the problem is fixed after an update on Ubuntu 19.10. The problem has been fixed several times in the past and then after another update, it will come again. It would be nice to hear where the problem comes from and what has changed to fix the problem."
1818392,2020-07-27 14:21:53 UTC,The kernel panic happened again at boot time after upgrading to Ubuntu 20.04. Why is there no permanent fix?
1818392,2020-07-27 14:24:07 UTC,*happens again
1818392,2020-01-31 09:31:41 UTC,A new kernel panic happened when upgrading to Ubuntu 19.10 and there is still no explanation on this bug report. I guess I will have to choose another Linux distribution if it continues.
1818392,2020-07-27 14:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818393,2019-03-04 01:08:54 UTC,"Which process (initial state particles) and which energies you are
talking about?"
1818393,2019-03-04 07:35:15 UTC,"Hey Alexander,"
1818393,2019-03-03 13:01:01 UTC,Dear Sam Witte.
1818394,2019-03-04 16:32:51 UTC,Please provide tripleo package versions and repository configuration
1818394,2019-03-05 07:09:44 UTC,oh sorry
1818394,2019-03-31 06:16:45 UTC,"Hi
I don't know if what I did was a fix but it's working 'I guess'"
1818395,2019-03-11 14:31:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818400,2019-03-03 17:03:57 UTC,I've done some more testing and found that VMQ is also broken with the HWE kernel.
1818400,2021-01-06 05:11:25 UTC,"Hello,
as the 4.18 kernel is no longer supported, do you still seeing this issue with a newer (supported) kernel?"
1818402,2019-09-16 08:22:38 UTC,Migrated to https://github.com/widelands/widelands/issues/3394
1818402,2019-03-04 06:58:38 UTC,"I have dug into the saveloading code. There are some small tweaks that could be done for some of the packages, but the scripting packet, which is eating up most if the saveloading time on big maps cannot be speeded up because it depends on the Eris backend. We would have to dig into Eris itself."
1818402,2019-03-04 08:47:35 UTC,"As far as I understand, the speedup_saveloading branch hasn't the latest trunk merged. So we still have the calculations in the init (that caused the 4 Minutes wait time) and that branch is extremely fast, when starting a territorial or woodgnome game."
1818403,2021-02-14 09:56:56 UTC,Thanks. Let's close the report then.
1818403,2020-12-18 12:55:25 UTC,"Unfortunately, I can no longer check that. I upgraded to Ubuntu 20.04.1 and the problem no longer exists."
1818403,2020-12-17 18:19:18 UTC,Does this issue still affect cups-pdf 3.0.1 packages?
1818404,2019-06-20 09:04:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818406,2019-03-04 19:40:50 UTC,"Ok, I found what's the problem."
1818406,2019-03-04 19:52:24 UTC,Attached is an updated version of the python_2_to_3.diff (from gnat-gps-17.0.2017 deb) that should fix this issue.
1818406,2019-03-04 20:21:46 UTC,"The attachment ""Updated python_2_to_3.diff patch from deb"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1818407,2019-05-16 05:01:35 UTC,"I have exactly the same bug on a newly purchased Asus VivoBook Flip 12 TP202NA.
The emmc is an SanDisk DF4032 749B806."
1818407,2019-05-25 21:36:26 UTC,"Okay as a temporary solution lower the speed to hs200. Boot up the machine while hitting the F8 button, press cancel when the boot options box pops up. Then proceed to advanced mode(f7), here go to Chipset/South Cluster Configuration/SCC Configuration. Here select eMMC max speed and select hs200. Then click on Save & Exit in the middle, there click Save and reset. Do not touch anything else in there because it can brick the device and the only way to reset the BIOS is to blow it apart..."
1818407,2019-07-21 11:36:56 UTC,hello acer swift 1 with emmc onboard all was fine but lately got this error -84:
1818407,2019-08-31 09:36:50 UTC,"Affects Asus VivoBook Flip TP202NA-EH012T
BIOS Vendor: American Megatrends
Version: 208
GOP Version: 10.0.1036
EC Version: 02.10
Processor Information: Intel Pentium CPU N4200 @ 1.10GHz
Total Memory: 4096 MB RAM
Intel HD Graphics
LCD: 1366*768
Storage:
- Controller 0
- Device Type EMMC
- Model Name: SanDisk DF4064 6BDD5503
- 64 GB"
1818407,2019-08-31 09:41:10 UTC,Could this be due to the TPM (Trust Platform Module) error? There doesn't seem to be a way to disable the TPM in the ASUS BIOS Utility.
1818407,2019-08-31 10:46:22 UTC,"Yes there is, but up the machine while preesing f8, press esc when the boot popup shows up. Head to advanced mode then advanced and under that trusted computing. But AFAIK TPM dont have anything to do with storage."
1818407,2019-08-31 11:06:05 UTC,"See comment 26 if you're still interested in seeing this fixed. After sending mail there, be sure to mention it here, ideally with some kind of reference (mailing list name and (message id) or (date and time of message send, sender's e-mail address, subject line)) so others will not send duplicate reports."
1818407,2019-08-31 11:17:13 UTC,"Image referenced in comment 31 by _doom (duso315-gmail) - cropped + scaled down:
""mmc0: mmc_hs400_to_hs200 failed, error -84"""
1818407,2019-09-01 01:40:11 UTC,@tomreyn: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/comments/35
1818407,2019-09-01 02:29:50 UTC,Temporary solution listed at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/comments/30 works. Thank you
1818407,2019-09-01 07:07:04 UTC,"Only the dtorage will be slower:
https://forum.odroid.com/viewtopic.php?t=20739
(Not ubuntu but they tested the two modes.)"
1818407,2019-09-06 11:48:16 UTC,Hi!
1818407,2019-03-07 07:12:37 UTC,"Yes, through e-mail."
1818407,2019-09-11 01:40:13 UTC,"Tried with the latest ""generic"" kernel, i.e. 5.2.11."
1818407,2019-09-11 01:40:50 UTC,"Tried with the latest ""generic"" kernel, i.e. 5.2.11."
1818407,2019-10-08 20:13:26 UTC,"As a potential workaround, please try to boot a current kernel (one that was also tested to not work otherwise) with kernel parameter sdhci.debug_quirks=32832 as per https://forums.xilinx.com/t5/Embedded-Linux/Linux-Kernel-4-6-mmc-issue/td-p/727465"
1818407,2019-10-10 10:35:18 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc2/"
1818407,2019-10-14 20:58:45 UTC,"I had similar issues on Chuwi Hi13 tablet with the same eMMC module.
It looks like latest 5.4-rc3 fixed that issue for me. I haven't tried other 5.4 kernel, but tried some of older kernels and older distros and 5.3 family.
I tried 5.4-rc3 on Arch Linux and it worked all good."
1818407,2019-10-14 21:31:10 UTC,"Oh never mind, it also works with 5.3. I don't remember then which kernel I actually tried, but issue seems to be fixed."
1818407,2019-10-30 13:45:02 UTC,"I tried to reproduce this problem with an ASUS L403NA with an Intel N4200 processor and SanDisk DF4064 eMMC, but it worked fine."
1818407,2019-11-14 09:46:50 UTC,"Verified fixed with Linux Kernel:
5.3.0-23-generic"
1818407,2020-05-26 09:46:03 UTC,Hi. I have a ASUS Tp202NA convertible and setting the emmc speed to HS200 just made the internal disk discoverable. I'm going to install kubuntu 19.10 on it to see if it works and report here. Thank you all for your help!
1818407,2019-09-01 10:30:22 UTC,"@ovari: It's good that you contacted these mailing lists. Note, however, that the developers subscribed to these lists are extremely overwhelmed with e-mail. They will likely not respond to e-mails which do not (concisely) state the actual issue by means of error messages, version number and further context. I am afraid the message you sent (which did arrive on both lists according to the list archives, see below) is likely not to raise the kernel developers' attention. We can discuss this in more detail on IRC (""tomreyn"" on Freenode) or by e-mail (tomreyn at megaglest d0t org) if you like."
1818407,2019-03-07 07:00:20 UTC,"How exactly i do that, just send them an e-mail?
Just as a side note after a long trial and error i got into a different advenced section and i found some settings under Chipset\South Cluster Configuration\SCC Configuration:
SCC Card Support (D27:F0) Disable
SCC eMMC support (D28:F0) Enable
eMMC Max Speed HS400
SCC UFS Support (D29:F0) Disable
SCC SDIO Support (D30:F0) Disable"
1818407,2019-03-04 00:47:01 UTC,apport information
1818407,2019-03-06 17:39:43 UTC,Same result...
1818407,2019-03-04 00:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818407,2019-03-04 00:37:53 UTC,"We discussed this on IRC.
Linux reports (DMI) this is an: ASUSTeK COMPUTER INC. TP202NAS/TP202NAS, BIOS TP202NAS.209 07/19/2018
This systesm' only internal storage which is not detected here (other than the error messages quoted above) is a SanDisk DF4064 eMMC."
1818407,2019-03-07 05:37:21 UTC,"Ok, please raise the issue to sdhci-pci maintainers:
$ scripts/get_maintainer.pl -f drivers/mmc/host/sdhci-pci-core.c
Adrian Hunter <email address hidden> (maintainer:SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI...)
Ulf Hansson <email address hidden> (maintainer:MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) AND...)
<email address hidden> (open list:SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI...)
<email address hidden> (open list)"
1818407,2019-03-04 00:46:46 UTC,apport information
1818407,2019-03-04 00:46:48 UTC,apport information
1818407,2019-03-04 00:46:49 UTC,apport information
1818407,2019-03-04 00:46:50 UTC,apport information
1818407,2019-03-04 00:46:51 UTC,apport information
1818407,2019-03-04 00:46:52 UTC,apport information
1818407,2019-03-04 00:46:53 UTC,apport information
1818407,2019-03-04 00:46:54 UTC,apport information
1818407,2019-03-04 00:46:45 UTC,apport information
1818407,2019-03-04 00:46:57 UTC,apport information
1818407,2019-03-04 00:46:58 UTC,apport information
1818407,2019-03-04 00:46:59 UTC,apport information
1818407,2019-03-04 00:46:55 UTC,apport information
1818407,2019-03-04 06:12:58 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0]."
1818407,2019-03-04 15:26:17 UTC,"Yes, i installed kubuntu on a sd card as a temporary solution to test things. (Just as a note i used ukuu to install the new kernel.)"
1818407,2019-03-06 03:44:43 UTC,"Seems like this commit fixes the issue:
commit 2b0efe8204ecebbfd766220f1c7ed63f8016b6f7
Author: BOUGH CHEN <email address hidden>
Date:   Mon Jan 7 10:11:29 2019 +0000"
1818407,2019-03-06 05:21:06 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1818407/"
1818407,2019-03-06 06:52:48 UTC,"Okay, downloaded all debs then dpkg -i ./*.deb and update-grub then reboot:
patakija@patakija-TP202NAS:~$ uname -r
4.18.0-16-generic
patakija@patakija-TP202NAS:~$ dmesg | grep mmc
[    3.165138] mmc0: SDHCI controller on PCI [0000:00:1c.0] using ADMA 64-bit
[    3.284207] mmc0: mmc_select_hs400 failed, error -84
[    3.284218] mmc0: error -84 whilst initialising MMC card
[    3.399568] mmc0: mmc_select_hs400 failed, error -84
[    3.399579] mmc0: error -84 whilst initialising MMC card
[    3.533777] mmc0: mmc_select_hs400 failed, error -84
[    3.533788] mmc0: error -84 whilst initialising MMC card
[    3.696410] mmc0: mmc_select_hs400 failed, error -84
[    3.696419] mmc0: error -84 whilst initialising MMC card
patakija@patakija-TP202NAS:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    1 119,1G  0 disk
├─sda1   8:1    1     1G  0 part /boot/efi
├─sda2   8:2    1 114,1G  0 part /
└─sda3   8:3    1     4G  0 part [SWAP]
patakija@patakija-TP202NAS:~$"
1818407,2019-03-06 08:59:12 UTC,This patch [1] may solve the issue.
1818426,2019-03-04 10:24:59 UTC,Cannot reproduce on macOS.
1818426,2019-03-04 15:41:43 UTC,"This happens for me on windows.  @Mathieu, please copy the kicad version information into your bug reports."
1818430,2019-03-13 12:07:50 UTC,"As of right now there is no non-rc version of aufs with support for Linux 5.0. We will update it as soon as one is available. However, the regex isn't going to work even when we have a non-rc version since it is looking for a 4.x version, and the version will undoubtedly be 5.0 (looks like it would even be broken for 4.20)."
1818433,2019-04-02 15:45:11 UTC,Any news if this is going to be implemented?
1818438,2019-03-03 19:26:45 UTC,message interruption during installation with a CD live ubuntu mate it says he cannot find the Grub and the installation is stopped
1818442,2019-03-03 19:54:59 UTC,"If I change the first test there to (<= a 0), then the optimization works.  This suggests to me that most of the logic is already there in the type propagator."
1818442,2019-03-03 19:55:24 UTC,"(<= i 0), I mean"
1818442,2019-03-03 20:15:15 UTC,"For clarity, here's the modified LIST* function I was using for mutation testing of the LIST* tests in ansi-tests:"
1818450,2019-11-28 11:10:57 UTC,"Just adding my vote for this feature.
I see draxil  mentions YNAB as an example.
I think it can makes to have this as part of the whole budget."
1818450,2019-07-13 03:37:06 UTC,"In my last comment I was thinking that the saving pots concept would be within each account, and that they would hook into transactions somehow. I think I was looking at this the wrong way."
1818450,2019-05-21 04:10:48 UTC,"I think this would be really cool! I currently do this with multiple bank savings accounts, which has come to bite me back in ....
Long story short, I might have to switch banks for my savings, but setting up multiple new savings accounts in another bank and tracking them is annoying. So having this feature to divvy up the total amount into virtual pots under a single account would be quite useful."
1818450,2019-03-23 22:08:23 UTC,"Great idea, I want this too!"
1818450,2019-04-02 20:47:34 UTC,"If you know or have good example, please post here :)"
1818450,2019-04-02 22:28:23 UTC,"  I know some banks (sadly not mine) offer savings pot features, often as a part of their online interface. Examples I've been able to find include:"
1818452,2019-03-03 22:30:06 UTC,This change was made by a bot.
1818452,2019-03-04 04:26:40 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0]."
1818452,2019-03-27 09:07:17 UTC,Changed to Incomplete as per the request in comment #3
1818452,2019-05-27 04:17:20 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1818473,2019-04-16 19:32:42 UTC,This bug was fixed in the package open-vm-tools - 2:10.3.5-7~ubuntu0.18.04.1
1818473,2019-04-16 19:31:39 UTC,"The verification of the Stable Release Update for open-vm-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1818473,2019-03-11 08:07:16 UTC,"Ran the same on cosmic, which other than dates in the log does not differ at all.
Setting verified as well."
1818473,2019-03-11 07:59:58 UTC,"With the trick described in the test instructions:
Prior to the update even when restarting the service:
[2019-03-11T08:31:47.052Z] [ warning] [resolutionCommon] resolutionCheckForKMS: No system support for resolutionKMS."
1818473,2019-04-16 19:31:13 UTC,This bug was fixed in the package open-vm-tools - 2:10.3.5-7~ubuntu0.18.10.1
1818473,2019-03-08 21:23:08 UTC,"Hello Christian, or anyone else affected,"
1818473,2019-03-05 09:57:48 UTC,"After improving on what we have found triggered by the first SRU review this is ready again.
Changes:
- Despite being an MRE in general all associated individual bugs have full SRU templates now.
- maintainers correctly updated
- The change to the vgauth Dependencies is now safer"
1818473,2019-03-04 06:35:44 UTC,Added remote bugs as bug tasks
1818473,2019-03-08 21:29:52 UTC,"Hello Christian, or anyone else affected,"
1818473,2019-03-29 21:48:10 UTC,Thank you for fix. I can confirm this to be effective on Ubuntu 18.04 setup here. Pulled update from proposed repository. Rate of bug reproducibility was getting more and more intensive with the time. In the end there was quite no boot with right screen resolution. Fix resolved it immediately. If more details are needed kindly feel free to ask.
1818474,2019-03-18 19:30:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818475,2019-03-04 06:48:20 UTC,"By the way, my NTP configuration is correct: fuel-master serves as NTP server. Nodes can also synchronize with their normal time：
root@node-6:/var/log# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*fuel.domain.tld 106.187.100.179  3 u   26   64  377    0.231   -1.590   0.327"
1818477,2019-03-04 07:00:45 UTC,Controller logs uploaded to https://private-fileshare.canonical.com/~paulgear/lp1818477/ for analysis.
1818477,2019-03-04 07:08:11 UTC,"To clarify, the following VMs from the pastebin were created with identical names but different UUIDs, and the duplicate was never added to the juju model:"
1818477,2019-09-19 09:41:28 UTC,"I'm getting a 404 trying to look at the logs. I'm guessing one of the steps to create the instance succeeds, but a different step fails (like creating security groups, or something along those lines). Having the logs to find out what is erroring vs what is succeeding seems useful.
It may also be a case that we're not killing an instance that step 1 succeeded, but step 2 did not, we should tear down whatever did get set up."
1818477,2019-11-19 04:17:28 UTC,[Expired for juju because there has been no activity for 60 days.]
1818479,2019-05-04 16:47:30 UTC,As agreed on the PTG [1]:
1818479,2019-05-24 02:38:04 UTC,"Reviewed:  https://review.opendev.org/660687
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d10ba94d36da7ad7eb6ac9339bcac81ab169b93e
Submitter: Zuul
Branch:    master"
1818479,2019-05-22 11:45:49 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/660687"
1818479,2019-05-01 15:38:05 UTC,When I started to work out the details I hit a bunch of questions which I did write up on the ML:
1818479,2019-03-08 09:36:34 UTC,"Yes, this is not ready for the drivers meeting yet. I hope to do that investigation very early in the Train cycle and report the results here."
1818479,2019-03-08 01:14:57 UTC,"Above you say ""We need to investigate the costs and benefits of this refactoring and if it's feasible implement it in Train"". Is the result of that investigation going to be reported in this RFE. Or in other words, how do we know we are ready to discuss this in the drivers meeting"
1818479,2019-05-03 00:15:45 UTC,@Bence: it is correct what You wrote in last comment :) Thx.
1818483,2019-03-05 11:30:34 UTC,"I modified binfmt_misc.c to let it send one more args if the corresponding binfmt_misc flags include ""P"", also I modified main.c in qemu as attached patch_qemu_main.patch to check if the input args include such string. Then qemu user could support both scenarios.
Is this modification feasible?"
1818483,2019-03-05 11:56:06 UTC,"Doesn't doing the check like that break execution of a command like ""echo 'MISC_FMT_PRESERVE_ARGV0'"" in a chroot environment that isn't using -P ?"
1818483,2019-03-07 06:08:49 UTC,"hi Peter:
Thanks for your suggestion.
but anyway we have to modify qemu code when binfmt_misc passes argv[0] in, right?"
1818483,2019-03-07 09:52:27 UTC,The question is: can we have one set of QEMU code that copes correctly with both 'binfmt_misc with P flag' and 'binfmt_misc without P flag' ?
1818483,2019-03-07 10:19:36 UTC,"hi Peter:
You are right, any additional modification should not affect the previous.
We expect that if this issue could be resolved without code change it's the best.
it may need to modify both binfmt_misc side to pass more information for flag P and qemu side to handle it."
1818483,2019-03-10 13:50:45 UTC,@Peter Luyou and me are working on try to pass the info about whether P flag is enabled or not by enviroment var or auxval. While we have not found the right method to do it from binfmt_misc.
1818483,2019-04-03 14:45:25 UTC,This patch is for linux kernel.
1818483,2019-04-04 00:47:38 UTC,This patch is for qemu itself.
1818484,2019-03-26 13:52:47 UTC,Closing this for the systemd dependencies part of the issue. Can't fix for the kernel part.
1818484,2019-03-18 09:14:15 UTC,"A note for Kolla project: it is known, if libguestfs is installed without a kernel, it won't work."
1818484,2019-03-18 09:06:37 UTC,Related https://bugzilla.redhat.com/show_bug.cgi?id=1689829
1818484,2019-03-04 08:45:10 UTC,"Note, this cannot be backported as it relies on a new %systemd_ordering feature of RPM specs and the spec fixes will only be available as of RHEL8/F29"
1818484,2019-03-04 08:45:24 UTC,Addressed by:
1818484,2019-03-04 08:47:03 UTC,The same issue but for kernel https://bugs.launchpad.net/tripleo/+bug/1804822/comments/18
1818490,2019-05-21 13:04:12 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1818490,2019-05-14 22:54:07 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1818490,2019-05-14 19:08:52 UTC,This bug was fixed in the package linux - 4.4.0-148.174
1818490,2019-05-14 19:06:48 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1818490,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1818490,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1818490,2019-04-26 15:36:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1818490,2019-04-26 14:31:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1818490,2019-04-25 22:32:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1818490,2019-03-05 10:28:10 UTC,Upstream bug in https://bugzilla.kernel.org/show_bug.cgi?id=202571 .
1818490,2019-03-04 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818490,2019-04-29 16:03:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1818493,2019-04-08 13:42:58 UTC,Related bug: https://storyboard.openstack.org/#!/story/2004580
1818498,2019-03-05 06:02:28 UTC, > Tetsuro had some ideas on using better transaction defaults in mysql's configs
1818498,2019-03-20 20:47:10 UTC,This issue was fixed in the openstack/placement 1.0.0.0rc1 release candidate.
1818501,2019-03-14 17:25:09 UTC,It there any reproducer?
1818501,2019-03-12 08:32:56 UTC,"Unfortunately we don't have a dedicated test system here, and I don't really want to test this on the production system... I can confirm that upgrading to the HWE kernel (4.18, which contains the patches) seems to solve the problem."
1818501,2019-03-08 05:14:11 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1818501/"
1818501,2019-03-06 13:52:29 UTC,"It should be
63de8bd9328bf2a778fc277503da163ae3defa3c  ocfs2: make metadata estimation accurate and clear
71a36944042b7d9dd71f6a5d1c5ea1c2353b5d42  ocfs2: try to reuse extent block in dealloc without meta_alloc"
1818501,2019-03-04 11:35:04 UTC,"Adding log with apport-collect files is not easily possible due to our security setup, but should not be necessary because all information can be found in the linked debian bug report."
1818501,2019-03-06 09:18:24 UTC,"Seems like these are required commits:
3e10b793fc40dfdbe51762e0d084bd6f2c8acaaa ocfs2: budget for extent tree splits when adding refcount flag
06a70305812c3973c66824f26223656283c59b27 ocfs2: prohibit refcounted swapfiles
86544fbd853c49a9eccb3d0f4e7eb9317f3fccf9 ocfs2: add newlines to some error messages
84e40080bd6f363ddbcab75b04cb7bc742efbf12 ocfs2: convert inode refcount test to a helper"
1818501,2019-03-04 11:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818501,2019-03-06 09:21:19 UTC,But these are already in v4.15. Is the commit that fixes the issue identified?
1818503,2021-02-18 16:46:41 UTC,This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo
1818504,2019-03-07 12:22:38 UTC,"Reviewed:  https://review.openstack.org/641413
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=f5a733c084dfb3d5db2f8184ad8692b67f3f5092
Submitter: Zuul
Branch:    master"
1818504,2019-03-07 07:09:10 UTC,"Change abandoned by Silvan Kaiser (<email address hidden>) on branch: master
Review: https://review.openstack.org/641277
Reason: @Eric: Reverts are fine with me, thanks for the reverts"
1818504,2019-03-07 12:22:47 UTC,"Reviewed:  https://review.openstack.org/641414
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=ade7d89c2e9eb317f93c128a0b7bf09fd945c960
Submitter: Zuul
Branch:    master"
1818504,2019-03-06 15:09:11 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641413"
1818504,2019-03-06 08:19:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641277"
1818504,2019-03-06 15:09:24 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641414"
1818505,2019-03-04 14:21:35 UTC,"...
Installing new version of config file /etc/network/if-up.d/openssh-server ...
dpkg-query: error: parsing file '/var/lib/dpkg/updates/0047' near line 0:
 newline in field name '#padding'
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned error exit status 10
...
dpkg-query: error: parsing file '/var/lib/dpkg/updates/0164' near line 0:
 newline in field name '#padding'
dpkg: error processing package ufw (--configure):
 installed ufw package post-installation script subprocess returned error exit status 10"
1818507,2019-09-20 09:29:46 UTC,"Its an interesting chicken-and-egg problem where we don't know what pods you're going to start until you tell us, but you need to know how to configure those pods before you start them."
1818507,2019-09-23 09:04:25 UTC,"For my needs, the charm needs to know that the named storage has been attached (normally signalled by the foo-storage-attached hook), and will be mounted at the location defined in metadata.yaml when the pod is spun up."
1818507,2020-02-03 19:15:06 UTC,Putting this down as a feature request for when/if we do storage on k8s where things like the hooks would come into play.
1818507,2020-02-03 21:06:21 UTC,I don't understand comment #3. We do run storage hooks.
1818514,2019-03-15 08:07:40 UTC,Good job - besides adding features (commits on GitHub) I did not yet tell anything about that ;-)
1818514,2019-03-14 22:04:41 UTC,Just to continue off https://answers.launchpad.net/sikuli/+question/679034. I see there has been substantial progress made with allowing sikuli to run python scripts outside of .sikuli folders. I've already started testing some of my projects with a more pythonic layout and can say that this is a seriously amazing addition.
1818514,2019-03-15 08:19:39 UTC,About py4j usage:
1818514,2019-03-07 17:27:55 UTC,"This is something I'd love to see. The projects I've been working for have hit a road block in regards to automation. The applications I'm testing are cross platform on windows and web. We've been utilizing selenium and sikuli for different tasks but would love to be able to utilize both in the same scripts without using hacky work-arounds. I understand that it is already possible to implement selenium and Sikuli together by using java, but I'm really fond of python's easy syntax and flexibility."
1818514,2019-03-08 14:15:44 UTC,"I have to say, I am also very excited for this possibility (for pretty much the exact same reasons as @Dillon).  Anxious to see what happens!"
1818515,2019-03-04 14:39:46 UTC,"Additional Info:
VCSA 6.7.0.20000
NSX 6.4.4.11197766
ESXi 6.7.0 11675023"
1818515,2019-03-21 17:04:32 UTC,The router_distributed option is not defined in vmware-nsx; it comes from neutron.
1818515,2019-03-22 08:52:11 UTC,@Boden Thanks again for the input yesterday on IRC.
1818515,2019-03-22 12:05:33 UTC,"dpreussker thanks for the update.
I need to follow up with the neutron team on this one.
Based on what I know, it seems that the router_distributed option should be registered with the conf as part of the framework and should not be something a plugin has to do.
That said it seems to me the fix should go into neutron and not vmware-nsx, but I will follow up with the neutron team on this."
1818515,2019-03-22 17:00:40 UTC,"As we discussed on IRC [1] the specific problem in this bug is that the router_distributed config option is not being registered in the global CONF before its accessed. While vmware-nsx does not use or even support that option, it use of the RouterAvailabilityZoneMixin requires the option to be registered (under the covers)."
1818515,2019-05-22 04:17:20 UTC,[Expired for vmware-nsx because there has been no activity for 60 days.]
1818521,2019-03-04 14:43:09 UTC,My computer is an HP Compaq 8200 Elite All-in-one with 1 TByte disk
1818524,2019-03-04 15:12:18 UTC,"Also see  https://bugs.launchpad.net/ubuntu/+source/parole/+bug/1818529, both parole and VLC player did not provide a reasonable error message for a broken input file. VLC player did not react at all, parole issued a nonsensical error message to add a ""Text/html decoder""."
1818527,2019-06-13 12:32:22 UTC,"Hello Abam, or anyone else affected,"
1818527,2019-06-18 21:14:35 UTC,Some comments on the Autopkgtest regressions:
1818527,2019-06-14 20:07:35 UTC,Verified for Bionic:
1818527,2019-06-11 19:48:40 UTC,Sponsored in Bionic.
1818527,2019-06-20 22:28:20 UTC,This bug was fixed in the package systemd - 237-3ubuntu10.23
1818527,2019-06-05 14:27:26 UTC,[sts-sponsor]
1818527,2019-06-04 12:43:30 UTC,This bug also affects MaaS when commissioning is done with Bionic 18.04 and an external proxy is set.
1818527,2019-04-08 10:06:40 UTC,"This seems to be the same issue previously reported at https://github.com/systemd/systemd/issues/9833, which was fixed in https://github.com/systemd/systemd/pull/9836 (commit 3740146) and released in v240."
1818527,2019-04-08 10:02:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818527,2019-06-10 13:08:59 UTC,"I can include this in my next systemd upload, once the current -proposed versions are released."
1818527,2019-06-20 22:28:27 UTC,"The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1818529,2019-03-04 19:09:03 UTC,Short English version of the bug report:
1818533,2019-03-05 06:34:26 UTC,"The issue is that idiomatically k8s pods requiring storage are managed by a stateful set, which requires that each pod be homogeneous - the pod template defining storage requirements is configured up front and typically a PVC backed by a storage class providing dynamically provisioned storage is used. k8s applications will have their own strategies for dealing with importing data from existing volumes; it's currently a bit wild west. We're looking at the possibility of patching existing pods to dynamically attach existing storage but need to consider how this interacts with the stateful set and how it manages rolling updates etc which may override and individual pod customisation done outside of the stateful set."
1818536,2019-03-04 19:41:34 UTC,"Hi,"
1818537,2021-02-09 21:12:40 UTC,I just tested this on our test 3.6.1 server and it's working fine. Maybe I was having an off day two years ago...
1818544,2019-03-04 18:45:38 UTC,Setting LAN Card's MTU to below 1400 Should fix the issue.
1818545,2019-03-04 18:19:55 UTC,You need to read the sentence before and after as well. It says:
1818545,2019-03-05 12:34:40 UTC,Thank you for your response!  Now I see the correct meaning.
1818548,2020-05-06 18:56:19 UTC,"Yay, this appears to have been fixed in focal:"
1818549,2019-03-20 21:11:29 UTC,"Confirmed, chromium doesn't list the extensions installed by those packages.
However if I go to chrome://extensions, I can click on the button to load an unpacked extension, and point the file picker to /usr/share/chromium/extensions/ublock-origin, and the extension is correctly loaded."
1818549,2019-06-18 13:56:57 UTC,There is a separate package chromium-ublock-origin. Maybe try that one for Chromium?
1818549,2020-06-08 23:08:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818550,2019-05-15 04:17:28 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1818550,2019-03-15 05:25:14 UTC,"Grid works in modern canvases very bad for me. And It behaviour canvases not change in confivuration. It good for generic graphics software draw lines, poligons,
 but bad for work in pcbnew itself."
1818550,2019-03-14 20:15:39 UTC,V6 releases tomorrow or next week?
1818550,2019-03-14 20:13:42 UTC,"What about grid, color schema? Where it is setting? Between v4 and v5 how much time passed? Minimum one year..."
1818550,2019-03-14 20:02:33 UTC,"@Anton, don't get too used to the legacy canvas(F9), it's going to be removed for V6.  Both modern canvases (F11 and F12) support full transparency on every layer.  It just defaults to no transparency.  You are free to customize layer color and transparency until you get the exact results you are looking for.  The legacy canvas drawing mode (XOR) is slowly be removed from most platforms rendering code so it's only a matter of time.  It is unlikely anyone will find the time to fix this bug since the code is going to be removed."
1818550,2019-03-14 21:23:24 UTC,"All of the color settings can bet changed in the layer manager.  The grid style can be set in the configuration dialog for the appropriate main window.  It will most likely be 2 years before KiCad 6 is released but the removal of the legacy canvas from the development branch is slated to happen soon.  Once it's gone, the motivation to fix this bug in the 5.1 branch will be almost zero.  I suggest you start using the modern canvas now so you can learn to configure and use it.  If you have any questions about using KiCad, you should ask on the KiCad user forum at https://forum.kicad.info/."
1818550,2019-03-14 19:35:19 UTC,"About grid. In F11 and F12 modes when zooming grid acts in different way unlike in F9 mode. In F9 mode for me more suitable. When I do move the footprint i press M or G. In need move it at 4 or 5 grid dots. When grid small or component are small - for precise and fast component movement i do zoom. In F9 mode when I do zoom, grid dots count are constant, but visual distance between them are variable (depends on current scale, real grid step are const). So I do zoom and precisely move component at 4 or 5 grid dots. Perfect. If F11 and F12 mode when i do first zooming grid acts as above, do second zooming between two dots appears another N dots. For this I need to make calculations in my brain what distance in this new dots i need: how many points between these two points, and multiply it at 4 or 5 and slowly move component with horizontal or vertical scrolling... very difficult. The PCB class is determined by the grid step. Manufacturers makes its component with the reference of standard grid steps. When needed, i manually set grid step - if i need move component at distance less, than current grid step. Automatically scaling dots quantity when zooming - is very good for PCB making, when PCB are makes without standards. For me it makes PCB design process much slower and harder."
1818550,2019-03-14 18:55:08 UTC,About grid. In F11 and F12 modes when zooming grid acts in different way unlike in F9 mode. In F9 mode for me  more suitable
1818550,2019-03-14 18:21:17 UTC,"In addition, grid dots in F9 mode seen through an one copper layer and not seen through two copper layers (copper zones, smd copper pads, copper tracks). Color scheme in F9 mode, as for me, more fit with pcb making, than color scheme F11 and F12 modes. Why in F11 and F12 modes pads of THT components bright yellow? This knocks the pads from the shared visibility of the printed circuit Board - put them to the fore and the perception of other elements of the printed circuit Board worsens. It's not very convenient. In F11 and F12 not have transparency (see above) and color scheme as in F9 mode. If F9 mode is enabled in kicad 5, it should work without errors. Because in kicad 4 it worked perfectly. Even if it does not have any improvements which are in the modes F11 and F12."
1818550,2019-03-14 17:46:48 UTC,"John Beard (john-j-beard) no, i did not see this bug in F11 and F12 modes. But why F9 mode comes in kicad 5 from kicad 4 with bugs? In kicad 4.0.7 all works fine. As seems to me F11 and F12 modes works a little bit slower, than F9 mode."
1818550,2019-03-08 13:19:18 UTC,@Anton: this appears to be in the legacy canvas. Do you still see it in the OpenGL or Cairo canvas (F11 and F12)?
1818550,2019-03-14 20:01:54 UTC,"Seems to be in F9 mode canvas have fixed dot count, and when zooming dots count in viewport are decreases and distance between them increases. In F11 and F12 dot count in canvas are dynamic and depends on zoom. Dynamic scheme good with making a component or general purpose graphics editors, like inkscape."
1818552,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1818552,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1818552,2019-06-04 09:11:38 UTC,This bug was fixed in the package linux - 4.4.0-150.176
1818552,2019-05-20 20:39:20 UTC,"$ grep BINFMT_AOUT /boot/config-4.18.0-2[01]-generic
/boot/config-4.18.0-20-generic:CONFIG_BINFMT_AOUT=m
/boot/config-4.18.0-21-generic:# CONFIG_BINFMT_AOUT is not set"
1818552,2019-05-20 14:01:50 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1818552,2019-05-18 02:28:41 UTC,Xenial:
1818552,2019-05-16 15:03:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1818552,2019-04-08 17:49:37 UTC,"Adjusting the grep a little to focus on Cosmic, Bionic, and Xenial and to only match CONFIG_BINFMT_AOUT, I get this:"
1818552,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1818552,2019-04-08 17:38:22 UTC,"Another thing to note is that CONFIG_HAVE_AOUT=y does not indicate that the a.out binfmt handler is enabled but the grep output in the bug description does include those matches. For example, the file xenial/linux-flo/3.4.0-5.23/armhf-config.flavour.flo has these lines:"
1818552,2019-04-08 17:29:54 UTC,"The output from Seth's grep (in the bug description) is a little misleading because the archival of kernel configs on kernel.ubuntu.com is buggy. It is including kernel configs of the generic, lowlatency, etc., kernels in the directories of the derivative kernels. For example, these config files should not exist because the linux-kvm source package does not produce an i386 generic or lowlatency binary package:"
1818552,2019-03-12 18:40:26 UTC,This thread sheds more light on why it is a good idea to disable a.out support:
1818552,2019-03-04 20:32:32 UTC,Setting to confirmed to placate the bot. Thanks.
1818552,2019-03-04 18:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818552,2019-05-16 13:02:50 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1818557,2020-05-02 06:35:36 UTC,"Ubuntu 20.04 shipped with grub containing regexp.
Thank you cjwatson!"
1818557,2019-03-06 05:57:58 UTC,cjwatson committed this for Debian in https://salsa.debian.org/grub-team/grub/commit/07481aa3deecc58247525d4e69f1f4f7ffbefe33
1818558,2019-03-07 20:41:18 UTC,"There is nothing for the upstream ""ndctl"" project to do about this."
1818558,2019-10-19 09:46:49 UTC,"Practically speaking, packages in ""universe"" tend to be supported to some degree for a maximum of 3 years from the original release of an Ubuntu LTS. That 3 years is because generally Ubuntu flavors do not offer support past that point. Once a new LTS is released 2 years later, there just isn't as much interest from volunteers to try to backport bugfixes and especially new features to the older LTS."
1818558,2019-03-07 20:39:41 UTC,Thanks for filing this bug.
1818565,2019-03-04 20:33:20 UTC,"If you want 3.19.1, what is wrong with the Debian experimental package?"
1818565,2019-03-05 12:16:55 UTC,"Hi Brian,"
1818565,2019-03-08 20:53:03 UTC,"> I still hope you can look into what the script is doing
> upon retrieval of the missing dependencies.
"
1818565,2019-03-09 13:13:38 UTC,How could I do that?
1818565,2019-03-10 07:29:12 UTC,"Hi all,"
1818569,2019-03-04 21:46:10 UTC,"Good debugging on this issue, wonder if this happens without the cidr notation (/32)? I added the deduplication for cidr notations /32 and /128 here [1]; I didn't expect to hit races down in the database layer for that rather simple lookup."
1818569,2019-03-07 17:35:32 UTC,Will be discussed as part of PTG
1818572,2019-03-07 17:57:16 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1818574,2019-03-07 22:02:49 UTC,"Note that this type of ""free binding"" behavior is not desirable in MOST setups.  Discussing in the Ubuntu Server IRC channel, in MOST setups, if you can't do something like bind to an IP it should error; slow-to-configure IPv6 aside, the most desirable thing would be for improper IP/bind configurations to error out in most default configurations."
1818574,2019-03-07 21:02:46 UTC,Thanks for filing this bug in Ubuntu.
1818574,2019-03-07 21:08:02 UTC,"I found this thread:
https://forum.nginx.org/read.php?29,248807,248807#msg-248807"
1818574,2019-03-08 01:11:35 UTC,"Thank you Andreas, thank you Thomas, the workaround to depend on network-online.target is fine for me."
1818575,2019-03-04 22:48:47 UTC,HARDWARE log messages
1818575,2019-03-04 22:47:50 UTC,Registration messages SECURITY
1818575,2019-03-04 22:44:03 UTC,ALL registration message
1818575,2019-03-04 22:42:42 UTC,Important log messages
1818575,2019-03-04 22:45:09 UTC,Registration message APPLICATIONS
1818579,2019-03-06 16:31:58 UTC,submitted review: https://review.openstack.org/#/c/641162
1818579,2020-01-06 06:43:23 UTC,I'm also hitting the same issue and https://review.openstack.org/#/c/641162 fix's that issue
1818580,2019-03-08 23:52:21 UTC,"for 1) No change, even with only ""ro"" parameter"
1818580,2019-03-07 22:55:40 UTC,mesg==dmesg
1818580,2019-03-08 07:04:51 UTC,elhoir:
1818580,2019-03-07 22:55:14 UTC,"@Christopher,
i`m afraid kernel 4.19.0-7.8 does NOT work.
Here is the complete mesg output for that kernel"
1818580,2019-03-07 11:55:05 UTC,"elhoir, the next step is to fully commit bisect from Ubuntu kernel 4.19.0-7.8 to Ubuntu kernel 5.0.0-7.8. This will allow for a direct review of the offending commit(s) for either reverting, or further improvements. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow."
1818580,2019-03-07 12:26:58 UTC,"@christopher, are you sure 4.19.0-7.8 works? how could i test it?"
1818580,2019-03-07 12:10:17 UTC,"this will take time for me... im really noob and i have never bisected anything, not to say a kernel xD"
1818580,2019-03-09 12:03:20 UTC,"elhoir, while you are welcome to wait for whenever a maintainer may respond, given this issue has been reported a regression, it is known that it helps developers expedite a fix if the offending commit(s) are identified via bisect."
1818580,2019-03-07 14:53:17 UTC,"ok, i saw it, 4.19.0-7.8 corresponds to 4.19.5 mainline"
1818580,2019-03-09 15:40:32 UTC,"@Christopher,
I agree, but i cannot find a working scenario to start with"
1818580,2019-07-27 15:40:52 UTC,"""Linux versions 5.1 and 5.2 would also not work with this parameter set."""
1818580,2019-03-09 16:47:02 UTC,"@Christopher,"
1818580,2019-03-09 16:48:08 UTC,"i also tested previous linux-firmware package (from Bionic, 1.173.3), and previous xserver-xorg-video-amdgpu 8.1.0 package"
1818580,2019-03-09 17:58:24 UTC,"btw, i have checked that kernel is not completely halted. R-E-I-S-U-B key sequence still works for rebooting system."
1818580,2019-03-09 18:14:30 UTC,"elhoir, if its actually true you personally were able to boot using the RX470 without WORKAROUNDs, its possible that either when you are installing older kernels you aren't installing the correct packages, or you were mistaken and it only booted either with a WORKAROUND or when a different graphics card was installed."
1818580,2019-03-11 19:46:47 UTC,i contacted with a guy with an AMD RX 470 GPU and he says irs working fine on his system
1818580,2019-03-11 19:51:36 UTC,cmdlive==cmdline
1818580,2019-03-14 00:55:07 UTC,elhoir:
1818580,2019-05-09 07:35:48 UTC,"Hello,"
1818580,2019-07-26 16:16:20 UTC,"The ""[drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting."" was also reported in bug 1837945 where kernel / boot parameter ""amdgpu.dc=0"" worked around an otherwise boot to black screen. There, however, Linux versions 5.1 and 5.2 would also not work with this parameter set."
1818580,2019-03-09 15:53:38 UTC,elhoir:
1818580,2019-03-07 10:34:33 UTC,"this is the complete uncut dmesg output right after ""sudo modprobe amdgpu"""
1818580,2019-03-09 06:34:10 UTC,Please just wait for AMDGPU maintainer's response. We can't do much now.
1818580,2019-03-07 09:29:14 UTC,@Kai-Heng Feng (kaihengfeng)
1818580,2019-03-05 08:30:07 UTC,This change was made by a bot.
1818580,2019-03-05 08:49:52 UTC,What's the symptom when you remove all the kernel parameters?
1818580,2019-03-05 11:30:01 UTC,@Kai-Heng Feng (kaihengfeng)
1818580,2019-03-05 11:36:27 UTC,Have you tried -generic kernel instead of -lowlatency?
1818580,2019-03-05 11:40:07 UTC,nope i didnt.... lets test now
1818580,2019-03-05 11:51:30 UTC,@Kai-Heng Feng (kaihengfeng)
1818580,2019-03-05 14:32:33 UTC,elhoir:
1818580,2019-03-05 18:39:49 UTC,Christopher:
1818580,2019-03-05 18:43:58 UTC,probably an off-topic question... what is VGACON ???
1818580,2019-03-05 23:25:02 UTC,"@Christopher,
Sorry but i have no way to get those logs. Boot gets frozen, i have to dirty shutdown via power button. And now in Windows the Ext4 filesystem is unclean so i cant mount it to get logs from /var/log"
1818580,2019-03-06 01:05:57 UTC,elhoir:
1818580,2019-03-07 10:19:22 UTC,@Christopher:
1818580,2019-03-06 03:23:25 UTC,"Please add kernel parameter ""blacklist=amdgpu"", and boot with mainline kernel.
Once you can use shell, run `modprobe amdgpu` to see if any trace/panic can be seen. You may want to use SSH to do this."
1818580,2019-03-06 02:04:30 UTC,"1) only latest, Disco Dingo"
1818580,2019-03-06 12:10:51 UTC,"well, this is surprising and unexpected"
1818580,2019-03-06 16:39:05 UTC,"Ok, then use kernel parameter ""blacklist=amdgpu modprobe.blacklist=amdgpu""."
1818580,2019-03-06 22:49:10 UTC,"okay, the ""modprobe.blacklist=amdgpu"" parameter did work."
1818580,2019-03-06 23:14:16 UTC,"iḿ getting this logs in dmesg, maybe after trying to load amgpu with ""sudo modprobe amdgpu""?"
1818580,2019-03-06 23:53:15 UTC,"yes, system is totally messed up locally, still usable via SSH through"
1818580,2019-03-07 01:07:45 UTC,elhoir:
1818580,2019-03-07 01:31:15 UTC,"1) yes, its a copy paste of crash part of dmesg, not entire output."
1818580,2019-03-07 03:49:16 UTC,Log in #20 is really useful.
1818581,2019-08-01 15:41:09 UTC,Worked for me.  Sign off at user/rogan/lp1818581_signoff
1818581,2019-09-06 16:24:18 UTC,"Pushed to master for inclusion in 3.4. Thanks, Terran and Rogan!"
1818581,2019-03-05 21:48:58 UTC,"Not sure if I did all of these pieces right, but here goes!"
1818584,2019-03-07 08:20:01 UTC,snaps can not access any removable media until you connect the removable-meadia interface ...
1818584,2019-10-10 10:09:42 UTC,"Artyom, as an aside, please try to keep things polite."
1818584,2019-10-10 10:01:21 UTC,The confinement is working as designed.
1818584,2019-03-07 10:12:52 UTC,"You asked why you should fix this problem. So because you can transfer your
files from your USB Drive to program without arranging the dances with
tambourines in any other normal OS, as Windows or macOS. Your college tell
me about way to troubleshoot. But it seems that Ubuntu was created for the
red-eyed onanists engaged in anal balancing act. Sorry for being rude, but
the operating system should be intuitive for the average user. I hope you
will make Ubuntu better for non-geeks."
1818584,2019-03-07 09:56:18 UTC,"Thank for your advices! You really helped me. After I entered this command
to the konsole, I had troubleshooted. But I believe, you should allow to
turn this feature as default, because typical user can not guess for this
manipulation."
1818584,2019-03-07 08:20:37 UTC,"(oh, alex beats me, i should have reloaded the page before commenting)"
1818584,2019-03-07 02:43:15 UTC,Can you try connecting the removable-media interface for these snaps?
1818584,2019-03-06 22:16:38 UTC,Oh thank you for your conclusion! I hope you will solve this problem
1818584,2019-03-05 15:49:17 UTC,"1. So I can open this document from USB stick in the LibreOffice, but not
in the WPS Office. And I can send any file to Telegram if I will transfer
it from my USB Drive to my PC. But I can do it ahead (from the USB Drive to
Telegram)"
1818584,2019-03-05 21:20:45 UTC,I downloaded WPS Office frome the GNOME Software
1818584,2019-03-05 17:34:07 UTC,"Sorry. Can I said about one big problem that I noticed after Ubuntu
switched from Unity to Gnome 3? Why the launcher has so terrible animation.
I see the work for this element in the Ubuntu 19.04, but now it's not
completely good. Will the Ubuntu 19.04 a really fast system with good
animations without bugs and freezes? Lockscreen and GNOME menu work with
some efforts since Ubuntu 17.10 release."
1818584,2019-03-05 15:34:54 UTC,"Thanks, some extra questions
- is the issue specific to wps files (or do you get the same problem if you try to open e.g an image?)
- how did you install wps?
- how do you get the dialog from the screenshot, is that from ""open with""?"
1818584,2019-03-05 14:56:18 UTC,"Sorry for the inconvenience. I test Ubuntu with Russian localization. So OS
named screens in the cyrillic in the auto mode.
[image: Screenshot4.png]
[image: Screenshot3.png]
zation. So system automatically named files in cyrillic.
[image: Screenshot1.png]
[image: Screenshot.png]"
1818584,2019-03-05 13:36:48 UTC,"Launchpad seems to have issue with the filenames of your screenshot, could you either include them in an archive or rename them to use english names?"
1818584,2019-03-05 12:42:16 UTC,"[image: Снимок экрана от 2019-03-05 14-40-36.png]
[image: Снимок экрана от 2019-03-05 14-40-16.png]
[image: Снимок экрана от 2019-03-05 14-31-30.png]
[image: Снимок экрана от 2019-03-05 14-32-34.png]"
1818584,2019-03-05 10:06:32 UTC,Thank you for your bug report. Could you give some details on the error? Like you double click on a document file from the usb stick and then what happens? You get a dialog? What does it say? Could you make a screenshot? Can you also add your journalctl log from the session where you had the issue?
1818584,2019-03-06 21:55:20 UTC,Looks like the issue is that those snaps can't access your USB key
1818585,2019-03-07 17:57:04 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1818586,2019-03-05 01:14:46 UTC,"Ubiquity 19.04.6
/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py:54: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, GObject, GLib, Atk, Gio
debconf (developer): <-- VERSION 2
debconf (developer): --> 0 2.0
debconf (developer): <-- CAPB
debconf (developer): --> 0 multiselect escape
debconf (developer): <-- GET ubiquity/custom_title_text
debconf (developer): --> 0
debconf (developer): <-- GET oem-config/enable
debconf (developer): --> 10 oem-config/enable doesn't exist
debconf (developer): <-- GET ubiquity/automation_failure_command
debconf (developer): --> 0
debconf (developer): <-- GET ubiquity/failure_command
debconf (developer): --> 0
debconf (developer): <-- GET ubiquity/success_command
debconf (developer): --> 0
debconf (developer): <-- GET ubiquity/show_shutdown_button
debconf (developer): --> 0 false
debconf (developer): <-- GET ubiquity/hide_slideshow
debconf (developer): --> 0 false
debconf (developer): <-- GET debian-installer/locale
debconf (developer): --> 0
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:5: PyGIWarning: NM was imported without specifying a version first. Use gi.require_version('NM', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import NM, NMA
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:5: PyGIWarning: NMA was imported without specifying a version first. Use gi.require_version('NMA', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import NM, NMA
/usr/lib/ubiquity/plugins/ubi-timezone.py:195: PyGIWarning: TimezoneMap was imported without specifying a version first. Use gi.require_version('TimezoneMap', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import TimezoneMap
No such schema “org.gnome.nautilus.desktop”
debconf (developer): <-- VERSION 2
debconf (developer): --> 0 2.0
debconf (developer): <-- CAPB
debconf (developer): --> 0 multiselect escape
debconf (developer): <-- FSET localechooser/languagelist seen false
debconf (developer): --> 0 false
Mar  5 00:50:56 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/usr/lib/ubiquity/localechooser/localechooser']' for ubi-language.Page
Mar  5 00:50:56 ubiquity: Watching for question patterns localechooser/languagelist
debconf (developer): <-- CAPB escape
debconf (developer): --> 0 multiselect escape
Mar  5 00:50:56 debconf (filter): <-- CAPB backup
debconf (developer): <-- CAPB backup escape
debconf (developer): --> 0 multiselect escape
Mar  5 00:50:56 debconf (filter): <-- REGISTER debian-installer/language debconf/language
debconf (developer): <-- REGISTER debian-installer/language debconf/language
debconf (developer): --> 0
Mar  5 00:50:57 debconf (filter): <-- SUBST localechooser/languagelist CODES C, C.UTF-8, ca, zh_CN, zh_TW, hr, cs, sq, am, ar, ast, bn, eu, be, bs, bg, my, da, nl, dz, en, eo, et, fi, fr, gl, ka, de, el, gu, he, hi, hu, is, id, ga, it, ja, kn, kk, km, ko, ku, lo, lv, lt, mk, ml, mr, ne, se_NO, nb_NO, nn_NO,..."
1818586,2019-03-05 01:15:14 UTC,ubiquity 19.04.6
1818587,2019-03-05 03:27:35 UTC,I recall this issue was a problem for Unity desktops. Although I expect a different package is to blame (please reassign).
1818590,2019-03-05 02:32:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/640925"
1818590,2019-03-06 23:22:34 UTC,"Reviewed:  https://review.openstack.org/640925
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=9cb715a5e766909ad8ac4d2d949cc3c141d7923f
Submitter: Zuul
Branch:    master"
1818593,2019-03-05 08:59:15 UTC,Thank you for your bug report.
1818593,2019-03-05 10:06:08 UTC,"We were not aware of this, most probably because in most cases it does not influence the result, a correct printout."
1818596,2019-06-29 02:34:14 UTC,Logged issue VIA https://github.com/Microsoft/WSL/issues/ as :
1818596,2019-06-28 19:02:05 UTC,Thanks Balint
1818596,2019-06-28 17:47:50 UTC,"But thank you for filing the bug here, too!"
1818596,2019-06-28 17:47:15 UTC,"I can reproduce the problem in WSL on Insider build 18917 but not in WSL2. This looks like specific to the WSL implementation, please file an issue at:
https://github.com/Microsoft/WSL/issues/"
1818596,2019-05-07 13:17:28 UTC,Read above.
1818596,2019-05-06 04:18:09 UTC,[Expired for ksh (Ubuntu) because there has been no activity for 60 days.]
1818596,2019-03-07 00:54:37 UTC,Test script.
1818596,2019-03-06 23:31:32 UTC,#!/bin/ksh
1818596,2019-03-06 23:19:38 UTC,"-> sdiff a b
#!/bin/ksh							#!/bin/ksh"
1818596,2019-03-06 14:08:16 UTC,How do you run the script?
1818606,2019-05-16 15:11:22 UTC,"Reviewed:  https://review.opendev.org/642703
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=b0ce30142ececa9ad8d5508e9ed54930c63d3817
Submitter: Zuul
Branch:    master"
1818606,2019-05-24 10:46:26 UTC,"Reviewed:  https://review.opendev.org/642704
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=14a685d9e143c6a6235d0656e31472637986ebee
Submitter: Zuul
Branch:    master"
1818606,2019-09-15 19:06:41 UTC,This issue was fixed in the openstack/kuryr-kubernetes 1.1.0 release.
1818611,2019-03-08 21:14:33 UTC,"Due to bug 1819225, raw GPG keys aren't working."
1818611,2019-03-05 07:30:01 UTC,Marking this issue as field-critical as we need that feature for juju-http-proxy for an ongoing bootstack handover.
1818611,2019-03-05 08:18:32 UTC,"This is not a ~field-critical as there is a workaround (using full deb source lines and GPG keys):
https://code.launchpad.net/~dmitriis/fce-templates/+git/fce-templates/+merge/363271"
1818615,2019-03-12 14:55:38 UTC,+1 to this.
1818615,2019-04-20 11:28:18 UTC,"Perhaps something like this, which we use in various other places, to work out the primary / default IP address used by the unit to communicate with the world:"
1818619,2019-03-06 08:05:01 UTC,Fix committed in X1.3.1-29.
1818620,2019-04-18 18:47:38 UTC,not in stein
1818620,2019-03-05 08:53:02 UTC,"CentosOS 7.0
Kolla-ansible 7.0.1
binary
rocky
---
1 network node
3 ceph nodes BS
2 computer nodes
2 control nodes (major: 192.168.100.31)
1 monitor node
----"
1818620,2019-04-25 09:33:42 UTC,I don't see any changes that would explicitly fix this in kolla-ansible.
1818621,2019-03-09 11:49:23 UTC,"Since we don't have game speed in the editor, those hotkeys would be available."
1818621,2019-03-09 11:57:51 UTC,"@Benededitk could it be a problem with the keyboard settings? Something with keyboard scheme, like dead_keys?"
1818621,2019-03-09 11:58:24 UTC,"I have attached another branch that deactivated the hotkey. I'm not sure that we should have it for Build 20 though, because it will deactivate it for everybody, including those who don't have any problems."
1818621,2019-03-09 11:40:14 UTC,Okay… perhaps it could be replaced with a hotkey to increase/decrease the toolsize by 1? e.g. PageUp and PageDown?
1818621,2019-03-09 12:29:41 UTC,"Ah, found the cause by chance :)
I´m on Ubuntu MATE 18.10, 64 bit. And I always have the option to highlight the cursor location when Ctrl is pressed turned on. Disabling that option fixes this bug :)"
1818621,2019-03-09 14:07:42 UTC,It's hard to capture system settings like this - I also remember a conversation about the num lock state and that controlling it in Widelands wasn't feasible.
1818621,2019-09-17 10:21:10 UTC,Migrated to https://github.com/widelands/widelands/issues/3397
1818621,2019-03-09 12:27:52 UTC,"If i remember right Bendict uses a buildin intel graphics. He had also problems with initializing the graphics init system recently (bug 1817686). I wonder if this bug, which is obviously only reproducible by Benedict, is also related to the OpenGL/SDL driver of his graphics card."
1818621,2019-03-09 11:34:00 UTC,I cannot reproduce this bug on macOS.
1818621,2019-03-09 11:22:23 UTC,Then I have no other ideas left except for deactivating the hotkey for toolsize = 10
1818621,2019-03-08 19:26:49 UTC,"Tried out the branch, but it doesn´t fix the issue :(
I also tried it with a different keyboard on the same machine now. No difference…"
1818621,2019-03-05 10:11:12 UTC,I could not reproduce this.
1818621,2019-03-05 10:53:36 UTC,"I rather think a maximum toolsize of 10 is already way too small, please don´t decrease it ;)"
1818621,2019-03-05 11:25:29 UTC,Can't reproduce this also with bzr9005[trunk] (Release)
1818621,2019-03-05 10:06:21 UTC,"This will be very annoying, so I think we should fix it for Build 20. Should be an easy fix I hope - maybe having maximum tool size = 9 in the hotkeys will do it."
1818621,2019-03-05 21:15:32 UTC,Removing the keyboard shortcut would not reduce the maximum tool size - it can still be set via the GUI to whatever maximum size is defined there.
1818621,2019-03-05 21:36:24 UTC,I can't reproduce this with the latest appveyor win x64 bit build.
1818621,2019-03-08 19:00:21 UTC,Please try the attached branch to see if it fixes it.
1818621,2019-03-05 12:06:54 UTC,All other Hotkeys with and without modifiers work normally. I use Ctrl+Z and Ctrl+Y very often.
1818629,2019-08-30 12:03:26 UTC,"Wanted to add a ""Me, too."""
1818629,2019-06-07 05:12:27 UTC,"Similar problem with a Color Laser Jet Pro MFP M477fdw, 18.04, HPLIP 3.19.5."
1818629,2019-06-11 19:38:47 UTC,"Same problem here witch Laser Jet 100 color MPF 175a
HPLIP 3.19.5"
1818629,2019-06-14 04:12:25 UTC,"same here
Ubuntu: 18.04
HPLIP: 3.19.5"
1818629,2019-06-14 22:15:52 UTC,"me too
Ubuntu 19.04
HPLIP 3.19.5"
1818629,2019-07-05 11:16:39 UTC,same here. Ubuntu 18.10
1818629,2019-07-20 23:48:16 UTC,Solution for #19
1818629,2019-09-27 19:26:56 UTC,"Having issues with this as well. Was able to get the plugin installed after adding the links to the SANE directories, as specified here:"
1818629,2019-10-22 13:33:16 UTC,"It seems to be a problem with this line:
/usr/bin/gpg --homedir /home/jarl/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9"
1818629,2019-10-08 07:50:57 UTC,"Install apparmor utils
sudo apt-get install apparmor-utils
Run hplip-plugin
sudo aa-disable /usr/share/hplip/plugin.py
Run as normal user, not as root:
hplip-plugin
now the printer will get installed"
1818629,2019-10-11 09:54:18 UTC,"When running analysis on my hp-setup debug logs (on laptop running Fedora 29) I see that some libraries are missing, but then I can also see that they are found in different location... so not sure what to make of this."
1818629,2019-06-06 15:24:30 UTC,"I'm having much the same problems after starting to use debian 9 and trying to install my HP Color LaserJet CP1217 using hplip-3.19.3.run.  The printer used to work perfectly well with OpenSUSE, and still does with Microsoft.  I had various problems installing HPLIP, but seemed to succeed eventually in getting as far as the binary plugin, apparently without which I've printed in black and white but not colour, so have been reluctant to go back to the beginning.  I comment apparently because, like Cristina, I keep getting the message that my plug-in installation was successful, only to be told immediately that I should run 'hp-plugin' as normal user to install plug-ins."
1818629,2019-10-24 19:19:15 UTC,"It seems to be a problem with this line:
/usr/bin/gpg --homedir /home/jarl/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9"
1818629,2019-11-12 11:18:07 UTC,"Changing /usr/share/hplip/base/validation.py line 45 from ""pgp.mit.edu"" to ""keyserver.ubuntu.com"" works for me as well. But only with command line installation (hp-setup -i)"
1818629,2019-11-13 17:08:51 UTC,"I've found the solution here for Mint 19 and HP1606dn:
https://askubuntu.com/questions/1151526/cannot-install-hp-printer-plugin-installation-not-successful
But in my case link was created broken and i just made directory and copied 'sane' folder there. After this problem has gone and installation completed succesfully."
1818629,2020-05-25 08:24:41 UTC,I experienced same problem.
1818629,2019-09-28 04:50:29 UTC,"Just for the record I just got my ancient Laserjet 1000 working by:
1. changing pgp.mit.edu to keyserver.ubuntu.com (as per comment #11) and
2. running ""hp-plugin -i"" followed by
3. ""hp-setup -i"""
1818629,2019-06-03 16:53:31 UTC,"I tried to install in ubuntu 19.04 64 bit (kernel 5.0.0-15) hplip-3.19.5 with hplip-3.19.5.run but I couldn't install plugins. I couldn't install from repository, also. Same error.
I have compiled tar gz and, when i try to install plugins (from download site or from hplip-3.19.5-plugin.run) I have this error:"
1818629,2019-05-30 04:16:13 UTC,my version is HPLIP-Version: HPLIP 3.19.5
1818629,2019-05-30 06:08:44 UTC,https://developers.hp.com/hp-linux-imaging-and-printing/plugins
1818629,2019-03-05 11:06:30 UTC,"> I do appreciate HP's effort to make their devices work
> on Linux, but I simply can't afford to spend around 10
> hours per year setting up and troubleshooting a printer.
> I really just want to print, nothing fancy, one-side,
> black and white, A4, that's all.
"
1818629,2019-03-05 11:44:56 UTC,"Thanks for the kind words and the pointer, Brian, I'll look into that!"
1818629,2019-03-14 09:41:46 UTC,"Ubuntu 18.04.2, hplip 3.19.1:
command '/usr/bin/gpg --keyserver pgp.mit.edu --recv-keys 0x9013C005' (from here https://developers.hp.com/hp-linux-imaging-and-printing/hplipDigitalCertificate.html) returns:
gpg: keyserver receive failed: No data"
1818629,2019-03-14 10:58:37 UTC,"The server itself should be fine, it is possible to receive loads of other keys from there, maybe they're just blocking pings."
1818629,2019-03-14 11:08:29 UTC,"FWIW, on a fresh install of Ubuntu MATE 18.04.2, I managed to make the printer work again with HPLIP 3.17.10 (the package already comes installed with a default Ubuntu MATE install)."
1818629,2019-03-14 11:15:02 UTC,"None of the keys imports for me. Neither the one for old versions or the one for new. And it is not my network the issue, I have double-checked this. Can you please help me troubleshoot?"
1818629,2019-03-14 12:48:23 UTC,I have exactly the same issue here. :(
1818629,2019-05-30 06:14:55 UTC,https://sourceforge.net/projects/hplip/
1818629,2019-03-14 12:49:32 UTC,I'm using Ubuntu 18.10 with the printer HP Laserjet M1132 MFP.
1818629,2019-03-14 13:16:56 UTC,"I tried this too, using the keyserver.ubuntu.com... But when I try to install the plugin, the hp-plugin setup don't check the existing key in Gnome. So, unfortunately this solution doesn't work. :("
1818629,2019-03-14 14:27:05 UTC,"I try to change the line 45 on /usr/share/hplip/base/validation.py from ""pgp.mit.edu"" to ""keyserver.ubuntu.com"". This modification solve the keyserver issue, but continues with problem on plugin installation:"
1818629,2019-03-17 19:08:23 UTC,"I am using Ubuntu 18.04 LTS 64 bits
I did install the new HPLIP 3.19.1
And since i cannot install my 2 HP Printers
Laserjet M1212NF  MFP
Laserjet CP1025 NW  Color"
1818629,2019-05-06 02:40:25 UTC,I'm trying to install my LaserJet M1132 MFP. I've exactly the same problem described here. No solution for while.
1818629,2019-05-30 04:13:07 UTC,"I have exactly the same bug valentin !!!
some said in forum , that he desactivates apparmor and it works
may be a clue for dev men"
1818629,2020-10-02 22:12:00 UTC,"A printer from 2007, as HP Laserjet P1006. Working previously, I try to install today with the same error result about pgp.mit.edu and the keys."
1818629,2019-05-30 04:22:51 UTC,"the printer function works not scanner.
the scanner interface bugs and warns the hp-plugin missing"
1818629,2019-03-14 13:00:54 UTC,"I'm really not an expert myself, just a struggling fellow user ;-)"
1818629,2020-07-22 17:49:53 UTC,"Add me to the list. HP MFP M479. I have never gotten a printer of any brand to work consistently with Linux over 10 years and am forced to always have a Windows machine available. This fine HP did work across three computers for about one month, now the office computer will sometimes print, sometimes not. Today it will not scan, bringing me here with the same HP-plugin error described. Just frustrating that Ubuntu is simply not reliable for office use - we don't have time to spend debugging every month."
1818631,2019-03-05 15:34:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818631,2019-03-05 11:25:03 UTC,"Below is possibly same issue.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920562#5"
1818631,2019-03-05 12:59:54 UTC,"Similar report here.
https://github.com/multiarch/qemu-user-static/issues/18"
1818636,2021-02-19 13:26:51 UTC,There were changes in behavior with the 20.01 release.
1818638,2019-04-01 14:28:30 UTC,Thanks for the info and for installing the test packages
1818638,2019-04-01 09:01:05 UTC,I have done the upgrade asked on #9 for the next time.
1818638,2019-03-29 09:40:11 UTC,"Hi,
A few minutes ago (10:15), I had a crash.
This is the trace :"
1818638,2019-03-28 12:59:45 UTC,No. I didn't have a crash since the last time.
1818638,2019-03-12 17:28:48 UTC,"Thanks for bug tracking.
I raised the samba log level to 3, maybe it will help you for the next crash."
1818638,2019-03-08 16:23:08 UTC,Files inside crash directory
1818638,2019-03-28 12:40:38 UTC,Have you tried with the packages in the PPA I mentioned in comment #9?
1818638,2019-03-07 21:29:51 UTC,This might be https://bugzilla.samba.org/show_bug.cgi?id=12610
1818638,2019-03-07 21:22:24 UTC,Mar 5 11:33:46 ServeurDev smbd[4501]: dumping core in /var/log/samba/cores/smbd
1818638,2019-03-07 21:19:32 UTC,"Can you please attach the crash file that you probably have on the server? I would look in /var/crash/*, and /var/log/samba/cores/*/*"
1818638,2019-03-07 11:08:16 UTC,Thank you for the additional information you provided.
1818638,2019-03-06 09:54:20 UTC,"Hi,
This problem happens some days and I don't know how to reproduce it.
Since January, I had the segfault 8 times.
We are 4 users for this server only and we use it daily.
I have noticed the crash came from during office hours only and I know we have mapped the samba drive as network drive. Maybe samba crash during connection, disconnection or refresh of the network drive?"
1818638,2019-03-06 08:42:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1818638,2019-03-08 14:38:14 UTC,"Andreas,
You can find the files attached."
1818638,2019-03-11 22:43:51 UTC,Thanks. Unfortunately I couldn't get more info from the crash file.
1818640,2019-05-20 10:56:43 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660090"
1818640,2019-05-20 12:13:10 UTC,"Reviewed:  https://review.opendev.org/660090
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=2496c6fc017141100053a17c5571ba6ea3d9d400
Submitter: Zuul
Branch:    master"
1818641,2019-09-17 09:13:10 UTC,"Hey Chris,"
1818641,2019-11-17 04:17:30 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1818641,2019-09-17 04:17:38 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1818641,2019-04-29 14:19:47 UTC,"Hi,"
1818641,2019-09-17 08:48:20 UTC,Do I have to do anything or has the bug been verified/fixed?
1818643,2019-07-26 18:15:02 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.1.0 release.
1818643,2019-07-01 09:21:03 UTC,Derek has a patch fixing the scenario012-standalone job https://review.opendev.org/#/c/663586/
1818643,2019-07-03 20:46:25 UTC,"Reviewed:  https://review.opendev.org/663586
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=67d5ca35386056e40b1b62628fd637c138d229f3
Submitter: Zuul
Branch:    master"
1818643,2019-07-01 08:09:08 UTC,"Multinode job fails now on tempest test, overcloud deployment finishes successfully:
http://logs.openstack.org/23/655423/16/check/tripleo-ci-centos-7-scenario012-multinode-oooq-container/2f874f2/logs/undercloud/home/zuul/tempest.log.txt.gz#_2019-06-29_12_06_40"
1818643,2019-03-05 21:46:45 UTC,"The job you pasted is from when the scenario012 was first merged, and it's a successful run. Do you have logs with failed runs ?"
1818643,2019-07-01 08:10:20 UTC,"@Derek, can you take a look in your time please?"
1818649,2019-03-06 07:07:42 UTC,resolve this problem by adding these configurations to lbaas_agent.ini
1818649,2019-04-12 13:49:47 UTC,"Marking invalid for neutron, neutron-lbaas bugs are on storyboard now: https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas"
1818649,2019-03-06 01:57:03 UTC,Is this feature not supported by neutron-lbaasv2-agent and haproxy
1818651,2019-03-15 09:45:29 UTC,have you restarted neutron-server after an upgrade?
1818651,2019-03-19 07:59:48 UTC,"This is more like a neutron mechanism issue, I've reported such bug:
https://bugs.launchpad.net/neutron/+bug/1815463"
1818651,2019-03-15 05:43:20 UTC,"relevant change: https://review.openstack.org/#/c/618720/
maybe we should not have bumped the server version.
https://docs.openstack.org/oslo.messaging/latest/reference/target.html#target-versions"
1818651,2019-05-19 04:17:23 UTC,[Expired for neutron because there has been no activity for 60 days.]
1818653,2019-03-06 13:57:27 UTC,"Change abandoned by Javier Peña (<email address hidden>) on branch: master
Review: https://review.openstack.org/640999
Reason: Fixed in neutron, not needed."
1818653,2019-03-06 14:09:48 UTC,"This was fixed in neutron by https://review.openstack.org/641064, which made the new parameter optional."
1818654,2019-03-07 15:05:05 UTC,[SOLVED]
1818654,2019-03-11 22:05:24 UTC,"PS: the issue is not present any more. It had been for some two/three weeks, now it's gone... (no, I have not been using hibernation or suspend)"
1818655,2020-10-14 09:22:01 UTC,"Unable to reproduce this bug.
Checked with Victoria and Train.
So, closing this bug."
1818661,2019-03-05 14:45:59 UTC,"Hi Raphael,"
1818661,2019-03-05 17:53:43 UTC,"Ok, additional information provided (step to reproduce)."
1818661,2019-03-05 18:15:23 UTC,Thanks Raphael!
1818662,2019-03-05 14:53:11 UTC,https://bugs.launchpad.net/hplip/+bug/1818629
1818666,2019-07-19 13:12:43 UTC,Please report this bug to Trisquel. Thanks.
1818667,2019-07-05 15:52:26 UTC,"A possibly-related issue I've seen several times this morning in both eeschema and pleditor is that if you're doing a Move and you try to finish it up by hitting the <Enter> key, then it may ignore the first <Enter>.  In other words, sometimes you have to hit <Enter> twice to end the Move.  However, I've not been able to figure out any way to replicate."
1818667,2019-07-05 11:35:24 UTC,"Unfortunately, I cannot readily test 5.1.  Until the regression in bug #1827124 is fixed, I'm stuck on an older rev of 5.1."
1818667,2019-07-04 22:01:00 UTC,"I thought it had been working already, since I hadn't noticed a problem with the last couple of revisions I've used.  I'll exercise it tomorrow and pay better attention."
1818667,2019-07-04 21:12:41 UTC,"This /might/ be fixed.  I found a rather insidious bug that didn't have anything to do with zoom or the grid: the move tool would get the event before the cursor control handler, so it would always be one step behind.  This made it look like the first arrow did nothing (and even more strange, after arrowing up a few times the first down arrow would move it up one more)."
1818667,2019-06-18 09:24:06 UTC,"While this is really a different bug, I can confirm that it's an issue and one that is very annoying at times."
1818667,2019-06-18 00:36:55 UTC,"Yes and no.  In the few minutes I've been able to squeeze in to play with it, the problem as I originally described it seems to have been fixed."
1818667,2019-07-05 00:36:01 UTC,"The 5.1 code is quite a bit different, and quite a bit buggier.  I made several changes there (including fixing the most annoying one that it would snap to grid on the axis that /wasn't/ moving as well)."
1818667,2019-06-17 16:34:26 UTC,@Ron-  I believe that this is resolved in the current 5.1 branch.  Could you test with the 5.1 nightly builds from
1818667,2019-05-03 19:31:00 UTC,"@Nick, I don't think so.  I think this fix was part of Jeff's new tool framework changes so it was only broken in the master branch which would only affect nightly builds.  @Jeff, am I correct this correct?"
1818667,2019-05-03 13:54:48 UTC,"Does it make sense to cherry pick the fix in
https://bugs.launchpad.net/kicad/+bug/1810684
to the 5.1 branch?"
1818667,2019-05-03 13:39:41 UTC,Sweet! It looks like it works for me too with 2e8d930.
1818667,2019-05-03 13:23:12 UTC,"This appear to be solve at 6.0.0-unknown-2e8d930~86~ubuntu16.04.1 release. Could you confirm, @Wayne?"
1818667,2019-03-06 18:23:13 UTC,"This is related with the fix https://bugs.launchpad.net/kicad/+bug/1810684
Before, using arrow was causing canvas unsync. But now, the step is zoom dependent: high zooms (in...) move as expected, 1 grid step; but low zooms (out...) move more than 1 grid step."
1818667,2019-06-17 17:27:38 UTC,"@Seth, I'm afraid there will have to be a delay, because I'm obliged at the moment not to ugrade my 5.1 nightly build. (The 5.1 nightly version I'm keeping has stuff in it that no longer works with recent builds and that I can't afford to lose.)"
1818668,2019-06-26 20:30:15 UTC,"The ""Default Text Size"" is really the ""Default Schematic Text Size"" (as opposed to the ""Default Symbol Field Text Size"")."
1818668,2019-06-26 20:34:13 UTC,Preference property fixed under this bug #.
1818668,2019-06-26 20:55:59 UTC,"Fixed in revision f11de08fa98b9c27bba95f51e5f97fc1a10d982b
https://git.launchpad.net/kicad/patch/?id=f11de08fa98b9c27bba95f51e5f97fc1a10d982b"
1818668,2019-07-02 00:15:51 UTC,"@Ron, Global Edit Text and Graphics Properties is also now in.  Let me know (in the linked bug report) if it meets your needs."
1818668,2019-07-02 12:24:51 UTC,"@Jeff, I can't see any difference at all in how the preferences work, but the Global Edit Text and Graphics Properties is pretty sweet, and largely takes care of my complaint, in so far as font sizes of symbol fields are concerned."
1818671,2020-09-16 12:41:40 UTC,This issue has been further investigated and diagnosed to be a configuration mistake.
1818671,2020-09-16 12:06:48 UTC,Without a local reproduction I cannot really move forward with this bug. I'm marking this Incomplete. If you can reproduce this on a recent OpenStack version then please set it back to New and provide information about the reproduction.
1818671,2020-05-04 23:14:19 UTC,I too am puzzled for the same reasons gibi described.
1818671,2020-05-04 14:14:37 UTC,I tried with 3 servers and with limit=1. And I cannot reproduce the problem. I was able to iterate on the 3 servers one by one using the marker provided in the response [1]. Similarly with limit=2. I also tried using the next link in the response for pagination and that worked too. Then I also tried to set the [api]/max_limit in the nova.conf to 2 and removed the limit form the request URI. Still pagination work.
1818671,2019-03-15 18:18:51 UTC,I had a look through the code and don't see anything that jumps out that would cause this behavior. I need a bit more information from you to understand what the problem could be.
1818671,2019-09-18 05:59:14 UTC,"Nova/OpenStack Train version.
[root@localhost nova-specs]# nova-api --version
19.1.0
[root@localhost nova-specs]# openstack --version
openstack 3.19.0"
1818671,2019-09-18 03:14:34 UTC,"I deployed the master branch (now in trai), that command execute ok, like:
[root@localhost nova-specs]# nova usage-list
Usage from 2019-08-21 to 2019-09-19:
+----------------------------------+---------+---------------+-----------+----------------+

| Tenant ID                        | Servers | RAM MiB-Hours | CPU Hours | Disk GiB-Hours |


+----------------------------------+---------+---------------+-----------+----------------+

| 40d622ea71704a11a37115947b250b83 | 8       | 151681.87     | 296.25    | 296.25         |


+----------------------------------+---------+---------------+-----------+----------------+
[root@localhost nova-specs]# openstack usage list
Usage from 2019-08-21 to 2019-09-19:
+---------+---------+--------------+-----------+---------------+

| Project | Servers | RAM MB-Hours | CPU Hours | Disk GB-Hours |


+---------+---------+--------------+-----------+---------------+

| admin   |       8 |    151685.29 |    296.26 |        296.26 |


+---------+---------+--------------+-----------+---------------+"
1818671,2019-09-02 04:20:39 UTC,"Seeing this in two difference clouds, when operating as the admin user."
1818671,2019-05-15 04:17:39 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1818671,2019-10-29 17:42:02 UTC,"I have this issue happening on two environments, one running 17.0.10 and the other running 17.0.11."
1818675,2019-06-21 15:26:08 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1818675,2019-03-06 22:30:14 UTC,"Reviewed:  https://review.openstack.org/641025
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=6d44ae7b6d20c883ee60862777b15d4cd62b2d8e
Submitter: Zuul
Branch:    stable/queens"
1818675,2019-03-05 14:48:44 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/641025"
1818680,2020-11-09 18:06:04 UTC,The verification of the Stable Release Update for vaultlocker has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1818680,2020-06-18 12:26:21 UTC,I have validated that using proposed allows the machines to boot even when Vault is sealed by rebooting all of the instances in a deployment using vault + ceph-osd with encryption.
1818680,2020-03-17 15:15:46 UTC,"Hello Andrea, or anyone else affected,"
1818680,2019-06-12 10:00:22 UTC,"I've uploaded for bionic-backports and raised the associated bug task; with regards to xenial, this will be delivered via the Ubuntu Cloud Archive."
1818680,2019-06-11 20:12:52 UTC,"Would it be possible to backport the fix in Bionic (and maybe xenial, as well, since they're both LTS)? Thank you."
1818680,2019-04-15 16:15:21 UTC,This bug was fixed in the package vaultlocker - 1.0.3-0ubuntu1.18.10.1
1818680,2019-03-08 09:57:50 UTC,"Hello Andrea, or anyone else affected,"
1818680,2020-11-09 18:06:06 UTC,"This bug was fixed in the package vaultlocker - 1.0.4-0ubuntu0.19.04.1~ubuntu18.04.1~cloud0
---------------"
1818680,2019-03-07 07:01:34 UTC,I incorrectly duped this against bug 1804261 but they are not the same issue.
1818680,2019-03-07 07:54:13 UTC,unsealing of vault that is.
1818680,2019-03-07 07:54:02 UTC,As a temporary workaround:
1818680,2019-03-07 07:51:15 UTC,Uploaded to disco development and to cosmic UNAPPROVED for SRU team review.
1818680,2019-03-07 07:36:08 UTC,Proposed fix appears to have the desired effect.
1818680,2019-03-07 07:04:08 UTC,Raised:
1818680,2019-03-07 07:03:14 UTC,Marking charm task as invalid as this is a vaultlocker issue.
1818680,2019-03-07 07:02:07 UTC,Reproduced by power cycling a converged deployment; the Before=network-online.target stanza in vaultlocker-decrypt causes the boot to block.
1818680,2019-03-07 09:21:30 UTC,Thanks James for following up on this. Will the fix trickle down to Bionic and Xenial as well? We have deployments that use vault on both releases.
1818680,2019-03-07 10:32:50 UTC,This bug was fixed in the package vaultlocker - 1.0.3-0ubuntu2
1818685,2019-03-06 15:30:52 UTC,"It appears to me that it's very easy to reproduce this problem immediately after using the ""Zoom to Selection"" feature, if you use it to zoom in by perhaps 5X.  Just using it to zoom in by a small amount like 2X doesn't seem to trigger the problem."
1818685,2019-08-23 02:50:49 UTC,This should be resolved now by efc0325e1
1818689,2019-03-20 16:45:44 UTC,This is a red herring. The debug message does not mean that there isn't configuration.
1818689,2019-05-20 04:17:27 UTC,[Expired for netplan.io (Ubuntu) because there has been no activity for 60 days.]
1818690,2019-03-05 15:30:07 UTC,This change was made by a bot.
1818690,2019-03-05 21:52:20 UTC,Found a solution in this thread: https://askubuntu.com/questions/525629/touchpad-is-not-recognized
1818690,2019-03-29 04:46:07 UTC,"Possible to find the exact ""i8042.*"" that makes it work?"
1818692,2019-03-05 17:21:29 UTC,"Good questions, Rogan.  My preference is that we have a single list of barcode requirements, and not bother with best practices.  That way, as long as both developers and libraries are adhering to the same list, we shouldn't run into issues like the one you describe.  I don't really have a preference between a permissive or a strict list of requirements, as long as it isn't way too permissive or way too strict."
1818692,2019-03-29 17:04:38 UTC,"""Item barcodes should not contain spaces"" and ""do not have spaces in the middle of your barcodes"" are opinions that I'd prefer not to see baked in to Evergreen."
1818692,2019-03-05 16:24:39 UTC,Item barcode format is generally Codabar 13. That is what format is considered for the check digit option (at least it used to be!)
1818692,2019-03-05 16:58:17 UTC,"Evergreen really doesn't have a barcode requirement in the sense of a standard like Codabar.  Those standards are used by barcodes scanners to create a string that is then passed to Evergreen.  Someone could create a whole new barcode standard we've never heard of and so long as the scanner passes the string to Evergreen it is fine.  The only requirements are when things happen that cause issues with parsing barcodes.  So, in regards to https://bugs.launchpad.net/evergreen/+bug/1798187 the space is, for now, a bad thing (tm) though that could change based on how the regex changes.  For example, if they take out the space split and start splitting on new lines only.  That bug becomes messy because we're trying to guess to at the best way to clean up ugly input and no one set of rules will cover every scenario.  And all the other scenarios in that bug are purely having to do with passing the barcode not it itself."
1818696,2019-03-06 07:29:01 UTC,"For the last 7 days:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22RuntimeError%5C%5C%3A%20OVSDB%20Error%3A%20%5C%5C%7B%5C%5C%5C%22details%5C%5C%5C%22%5C%5C%3A%5C%5C%5C%22cannot%20delete%20QoS%20row%5C%22"
1818696,2019-03-15 04:29:14 UTC,"according to the logstash query Lajos Katona provided in comment #1, it didn't happen this week. do you think the problem still exists?"
1818696,2019-05-15 04:17:21 UTC,[Expired for neutron because there has been no activity for 60 days.]
1818697,2019-03-06 07:51:23 UTC,"Logstash query for this problem:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22test_bw_limit_qos_port_removed%5C%22%20AND%20build_status%3A%5C%22FAILURE%5C%22%20AND%20build_name%3A%5C%22neutron-fullstack%5C%22"
1818697,2019-03-15 04:13:15 UTC,"the logstash query Lajos Katona provided in comment #1 shows it didn't happen this week.
do you think the problem still exists?"
1818697,2019-05-14 04:17:25 UTC,[Expired for neutron because there has been no activity for 60 days.]
1818701,2019-03-22 03:43:23 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.
1818701,2019-03-13 00:26:15 UTC,"Reviewed:  https://review.openstack.org/641401
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=50cc1e8bb6fd31a86295aedcec83d49e4d4d52eb
Submitter: Zuul
Branch:    stable/rocky"
1818701,2019-03-24 23:39:09 UTC,This issue was fixed in the openstack/nova 18.2.0 release.
1818701,2019-03-06 00:08:36 UTC,"Reviewed:  https://review.openstack.org/641082
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cb5ad6d3c14caccfc2b222dc5d2f1f6c5e05da9c
Submitter: Zuul
Branch:    master"
1818701,2019-03-05 16:52:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641082"
1818701,2019-03-06 14:46:55 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/641401"
1818701,2019-03-05 16:56:31 UTC,Logs:
1818702,2019-03-05 20:20:24 UTC,https://bugs.launchpad.net/hplip/+bug/1818629
1818702,2019-06-18 12:30:38 UTC,"hp-check just crashes in /usr/share/hplip/base/utils.py  /etc/PolicyKit - No such file or directory
created a symbolic link ln -s /etc/polkit-1 /etc/PolicyKit -
still crashed, different error.
Made localauthority chmod 777 in polkit-1 instead of just root to test.
hp-check -i now runs, N.B. ./configure was run with policykit DISABLED. So unsure why PolicyKit was being tested."
1818702,2019-03-07 13:40:51 UTC,"> What gets me is this used to work. I have been away for
> a couple of weeks, ran a series of upgrades on my return
> and suddenly, but sadly not unsurprisingly, it stopped.
"
1818702,2019-07-21 00:22:34 UTC,This solution works for me:
1818702,2019-03-06 18:57:42 UTC,Your device has an AirPrint service. I would suggest you forget about the problems HPLIP and its plugin is giving you and focus on what is advised in
1818702,2019-03-06 17:36:35 UTC,"I forgot to mention I also tried
python3 /usr/share/hplip/setup.py"
1818702,2019-03-06 17:28:53 UTC,"Nope, tried all of the suggestions."
1818702,2019-03-07 11:22:40 UTC,"Unfortunately with the above technique, while the printer queues etc are configured, most jobs, including the test page, all result in the printer reporting ""Unable to print file. File is corrupt"". The selt-test page works, not that it does me any good."
1818702,2019-06-18 11:25:28 UTC,"Similar woes - printer worked, then stopped, on version hplip-3.19..;  But its a generic problem - affecting 3-18.6 3-18.12 - I am using Debian/sid but nothing I have tried overcomes 'plugin installation failed' - I'm using a P1005 USB printer.  Ironically, a networked HP5510 All-in-one which just reported 'filter failed', now works.  But that's reporting 3.16.11 driver from the Printer Test Page
I've tried changing the ./configure options and rebuilding - but Alex's posts above at least told me where the binary was supposed to go - in the past I've been using hp-firmware -n from root, which consistently allowed a print to come out.   Now, 'filter failed'"
1818703,2019-03-05 16:50:33 UTC,Subscribed ~field-high for tracking.
1818703,2020-02-04 15:58:56 UTC,This is most likely the same issue as bug 1794882.
1818704,2020-05-03 09:52:33 UTC,see github issue
1818708,2019-07-14 19:46:35 UTC,Fixed with https://bazaar.launchpad.net/~duplicity-team/duplicity/0.7-series/revision/1373#bin/duplicity
1818710,2019-03-18 17:00:41 UTC,Actually I was wrong: The windows get scrambled every time you change the amount of available screen space by either adding or removing monitors.
1818710,2020-02-14 22:42:07 UTC,I have this problem if I simply do:
1818711,2019-03-06 10:24:02 UTC,"Meh, I'd rather see /usr/lib/libvirt/libvirt-guests.sh at the end of stop, iterate across `virsh net-list` and call `virsh net-destroy` on them."
1818711,2019-03-06 07:19:49 UTC,"Currently (quite a while actually [3]) the ordering on shutdown is like this:
  libvirtd -> domain -> virt-guest-shutdown.target -> save-restore.service
And as Steve mentioned ""save-restore"" is to allow to shutdown or save guest state - and that not only via the default libvirt-guests.service but if wanted also via other services, therefore the .target in [3]."
1818711,2019-03-05 21:01:41 UTC,"I don't believe I do, nor does the surrounding context look similar."
1818711,2019-03-05 18:24:36 UTC,Does your libvirt have this patch?
1818711,2019-03-05 22:25:53 UTC,"> I don't know why libvirt has KillMode=process, but my guess is
> that one ideally wants to be able to restart libvirt without
> killing VMs / dnsmasq state. However, when doing shutdown,
> these should be really killed.
"
1818713,2019-03-05 18:40:59 UTC,"Please note: the package is elementary-icon-theme,  however when I try to select that package in the bug reporter, i get the following message (have tried waiting):"
1818714,2019-03-05 18:56:19 UTC,"For me, putting a ""if (nullptr)"" guard around the onMarkChanged handler fixes the problem for me, and the waveform marks are all in the right places so that may be the easiest way to fix it."
1818714,2019-03-05 19:51:22 UTC,Related bug. Set a loop on a track and tap the eject button -> Crash
1818714,2019-03-05 19:55:46 UTC,"So when ejecting a track, all the hotcues are set to -1. Concurrently, m_pCurrentTrack will be set to nullptr. Thus, we really need to check for nullptr in onMarkChanged.
Besides this, I'm investigating if we need to fix anything else."
1818714,2019-03-05 20:01:49 UTC,"Yes, so after loading a track we call updateCues in slotTrackLoaded. So we only need to check for nullptr on onmarkChanges and that's it. I'm opening a PR. Thank you very much for exposing the bug with such detail."
1818714,2020-05-09 06:58:34 UTC,"Fixed here:
https://github.com/mixxxdj/mixxx/pull/2053"
1818715,2019-03-06 14:28:38 UTC,apport information
1818715,2019-03-06 14:28:39 UTC,apport information
1818715,2019-03-06 14:28:41 UTC,apport information
1818715,2019-03-06 14:28:42 UTC,apport information
1818715,2019-03-06 14:28:43 UTC,apport information
1818715,2019-03-06 14:28:45 UTC,apport information
1818715,2019-03-06 14:28:51 UTC,apport information
1818715,2019-03-06 14:28:48 UTC,apport information
1818715,2019-03-06 14:28:50 UTC,apport information
1818715,2019-04-01 06:51:04 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc2 kernel [0]."
1818715,2019-04-01 19:59:32 UTC,"Cant test the upstream kernel, sorry but using the ppa installation from
Hauppauge it got"
1818715,2019-03-06 14:28:36 UTC,apport information
1818715,2019-03-06 14:28:47 UTC,apport information
1818715,2019-03-06 14:28:35 UTC,apport information
1818715,2019-03-06 14:28:44 UTC,apport information
1818715,2019-03-06 14:27:39 UTC,apport information
1818715,2019-03-06 14:27:21 UTC,apport information
1818715,2019-03-06 14:27:22 UTC,apport information
1818715,2019-03-06 14:27:23 UTC,apport information
1818715,2019-03-06 14:27:24 UTC,apport information
1818715,2019-03-06 14:27:25 UTC,apport information
1818715,2019-03-06 14:27:27 UTC,apport information
1818715,2019-03-06 14:27:28 UTC,apport information
1818715,2019-03-06 14:28:33 UTC,apport information
1818715,2019-03-06 14:27:30 UTC,apport information
1818715,2019-03-06 14:27:31 UTC,apport information
1818715,2019-03-06 14:27:32 UTC,apport information
1818715,2019-03-06 14:27:33 UTC,apport information
1818715,2019-03-06 14:27:35 UTC,apport information
1818715,2019-03-06 14:27:38 UTC,apport information
1818715,2019-03-05 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818718,2019-04-23 23:54:36 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1818718,2019-06-23 04:19:06 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1818721,2019-07-08 01:47:54 UTC,"Unfinished sentence: I'm okay with saying that ""HTML5 entity references"" is one of the features of HTML5 that you just can't get without using an HTML5 parser like html5lib."
1818721,2019-04-20 18:36:13 UTC,"I attempted to see what it would take to use the HTLM5 entity list, but it looks like it really won't work without some massaging and compromises. There are quite a bit of differences, such as multi char entities, etc."
1818721,2019-04-20 03:30:17 UTC,"Seems in Python 3 (staring in Python 3) they have a HTML5 entity list. It is not used by default for the codepoint2name and entitydefs, but we could easily generate one for ourselves. I think we can, and probably should fix this moving forward for Python 3."
1818721,2019-07-08 01:47:35 UTC,"This happens because when html.parser calls BeautifulSoupHTMLParser.handle_entityref, the semicolon isn't provided and we have to decide whether the original markup was ""&apos;"" or ""&apos"". Since we (think we) have a complete list of HTML named entities, and 'apos' isn't on the list, we assume the original markup was ""&apos""."
1818721,2019-04-14 17:45:46 UTC,"I was looking at this issue today, and noticed it is specific to the `html.parser`. Using `lxml` or `html5lib`, it is converted fine. I'm not sure yet if this is expected or not."
1818721,2019-03-05 22:04:52 UTC,"My apologies, I should have included that:"
1818721,2019-04-14 18:12:12 UTC,"After looking into this more, I understand why you are getting the results that you are."
1818721,2019-03-05 20:52:14 UTC,What Python version?
1818721,2019-03-05 20:51:53 UTC,"It might be an issue with Beautiful Soup, I think it would need to be evaluated first to be sure. Beautiful Soup derives its parsers from `html.parser`, `lxml`, etc. It derives from them so it can use them to build it's own HTML structure. The issue could be with either one. The issue would have to be investigated further."
1818722,2019-05-25 04:17:33 UTC,[Expired for OpenStack openstack-dashboard charm because there has been no activity for 60 days.]
1818722,2019-03-19 14:06:35 UTC,The CA certificate you supply through the ``ssl_ca`` configuration option is installed into the system wide certificate store by the charm.
1818722,2019-03-25 18:15:48 UTC,Thank you for providing info on the alternate way to manage keys ! I will have try it.
1818723,2019-03-05 21:30:04 UTC,This change was made by a bot.
1818725,2019-07-15 23:58:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670926"
1818725,2019-07-25 17:27:50 UTC,"Reviewed:  https://review.opendev.org/670926
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=52da4d0e129048d1b808bdde07364cde698cf475
Submitter: Zuul
Branch:    master"
1818725,2019-09-27 09:10:31 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1818730,2019-09-27 09:05:56 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1818730,2019-06-18 03:41:36 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1818730,2019-06-06 06:24:42 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1818730,2019-04-16 14:48:41 UTC,"Reviewed:  https://review.openstack.org/648691
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f1ac5183d43459614ba5a356c2c7b50251fcd94f
Submitter: Zuul
Branch:    stable/rocky"
1818730,2019-03-29 13:48:39 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/648691"
1818730,2019-03-28 19:02:12 UTC,"Reviewed:  https://review.openstack.org/641137
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=855b5546564f0ed96243623b67b1322e9b891c8b
Submitter: Zuul
Branch:    master"
1818730,2019-03-05 22:00:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641137"
1818730,2019-04-11 23:47:15 UTC,"Reviewed:  https://review.openstack.org/648688
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bcb42a43a9f12d929ec7025f29bd2e3d482cd406
Submitter: Zuul
Branch:    stable/stein"
1818730,2019-03-29 13:41:25 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/648688"
1818732,2019-09-07 04:15:26 UTC,https://review.opendev.org/607820
1818732,2019-09-16 18:02:12 UTC,Closed by https://review.opendev.org/607820
1818733,2020-07-18 20:38:42 UTC,This was fixed by some of the rotate / zoom changes upcoming in v1.7 (https://github.com/PintaProject/Pinta/commit/60266d3b860d6e49dac48b0efc1d46822798d3c3)
1818734,2019-08-21 09:16:40 UTC,"Reviewed:  https://review.opendev.org/676108
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9011220178dc1c6b684f9c2ab22a7f09758a4da7
Submitter: Zuul
Branch:    master"
1818734,2019-09-27 09:10:16 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1818734,2019-08-21 17:32:20 UTC,"Reviewed:  https://review.opendev.org/676115
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=cf572f9e843745fd3b0fb2040e8a7a9dec94432e
Submitter: Zuul
Branch:    master"
1818734,2019-08-21 02:21:36 UTC,"Reviewed:  https://review.opendev.org/675536
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=7d223bec9d77be3079830c71be398c68e502e71b
Submitter: Zuul
Branch:    master"
1818734,2019-08-13 06:22:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676108"
1818734,2019-08-09 06:53:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675536"
1818734,2019-08-08 08:46:54 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675272"
1818734,2019-08-21 02:21:17 UTC,"Reviewed:  https://review.opendev.org/675272
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=e4fb1e1fdd422a1093b5eedb587ede88d0d7eb8e
Submitter: Zuul
Branch:    master"
1818735,2019-03-05 22:12:02 UTC,"This is an error in the archival of previous point release images for this flavor, which are not meant to remain on cdimage.ubuntu.com once a new point release is out.  Łukasz, do you know what happened here?"
1818735,2019-03-05 22:54:54 UTC,"Historically, we've always kept all the LTS images for flavours until EOL, since they don't go to old-releases.  We can and should, however, make sure the pretty header from make-web-indices only points to the latest."
1818735,2019-03-05 22:55:36 UTC,"(And this might be on me, since I did 18.04.2, not Lukasz)"
1818736,2019-09-26 22:08:58 UTC,"Reviewed:  https://review.opendev.org/621024
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=e938c496281daa6d1dab66d66bdb2d34abd5ddc3
Submitter: Zuul
Branch:    master"
1818736,2019-09-27 09:09:43 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1818736,2019-09-26 05:03:24 UTC,"Change abandoned by Vishakha Agarwal (<email address hidden>) on branch: master
Review: https://review.opendev.org/684531"
1818736,2019-09-25 06:54:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/684531"
1818736,2019-09-26 07:48:52 UTC,"Reviewed:  https://review.opendev.org/621023
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f249c9e2b0f39b688ba356feaca7818adfc9f739
Submitter: Zuul
Branch:    master"
1818746,2019-03-05 22:31:18 UTC,I'm actually being generous above; a user is much more likely to do:
1818746,2020-12-08 06:01:44 UTC,I totally agree with this!
1818746,2020-12-08 06:05:35 UTC,Never mind... Just `ubuntu-drivers install` did the trick.. LOL
1818749,2020-12-08 06:02:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818749,2020-12-08 06:02:22 UTC,I totally agree with this!
1818749,2020-12-08 06:05:32 UTC,Never mind... Just `ubuntu-drivers install` did the trick.. LOL
1818749,2020-12-14 09:42:40 UTC,"Why do you mention netplan and networkd on this report, the issue seems different?"
1818755,2019-04-02 08:50:39 UTC,"Right, this is the result of transitioning from a world where the store series actually mattered for anything to one where the most important thing is the base, and that transition is only partially complete."
1818758,2019-09-27 19:51:39 UTC,"Hi Carlos,"
1818758,2019-06-25 22:21:31 UTC,"Reviewed:  https://review.opendev.org/657414
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=408348b5a47968822752260117e93b7a86b5d86a
Submitter: Zuul
Branch:    master"
1818758,2020-05-12 16:43:41 UTC,"Hi, Goutham! Sorry I took too long to answer to this question. I agree with you. I think this suffice and the bug could be closed."
1818758,2019-03-27 20:22:06 UTC,"Reviewed:  https://review.openstack.org/647973
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=5cd643785d81784d61e4d9b49ff0707ff5dd4ed9
Submitter: Zuul
Branch:    master"
1818758,2019-03-27 01:43:45 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647973"
1818758,2019-03-27 20:26:18 UTC,"Reviewed:  https://review.openstack.org/642099
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=3fe22863dba723ee189520c248a36587371b0275
Submitter: Zuul
Branch:    master"
1818760,2020-07-18 15:27:33 UTC,Seems like something flatpak-specific.
1818760,2020-07-19 12:30:38 UTC,"@Yuriy, can you please test this problem again and if problem still persists please report it to Flatpack package maintainer. You probably installed Pinta package from Flathub project:
https://www.flathub.org/apps/details/com.github.PintaProject.Pinta If this is true, then that page is referencing to report a bug at: https://github.com/flathub/com.github.PintaProject.Pinta/issues"
1818765,2019-03-06 02:40:22 UTC,https://review.openstack.org/#/c/641186/
1818765,2019-04-16 08:45:40 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1818765,2019-04-16 08:46:12 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.openstack.org/641186
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1818772,2019-04-14 18:42:09 UTC,"I tried to removed MOK , then enable back MOK ..."
1818772,2019-04-08 18:32:04 UTC,"I tried to purge and reinstall grub2 , there is still no grub menu list to choose my dual boot operating system as before. Tried to compare the grub.cfg with fresh installed disco , the cfg file is the same."
1818772,2019-03-17 22:49:32 UTC,I can't reproduce any issues with grub2 booting off a fully updated (as of today) 19.04 amd64 pre-release in BIOS boot mode.
1818772,2019-03-14 19:44:06 UTC,Hi Khairul
1818772,2019-03-14 17:18:21 UTC,I just upgraded the kernel in disco-proposed
1818772,2019-03-06 16:25:06 UTC,"Hi, Steve"
1818772,2019-03-06 05:04:49 UTC,"You have filed this bug against the 'grub' package, which is grub 0.97 and is no longer included in Ubuntu.  Normally, I would reassign such a bug report to the grub2 package, which is the current version of grub in use in Ubuntu; but your screenshots show menu entries that do not appear to match what is produced by the Ubuntu update-grub.  What version of the grub package do you actually have installed?"
1818772,2019-03-06 12:27:11 UTC,"Hi, Steve."
1818772,2019-03-06 03:57:30 UTC,One more confirmation that Kernel 5.0 is installed and version 4.19 is in use. Is it not the version of kernel 5.0 that should be in use?
1818772,2019-03-06 03:48:43 UTC,"Here is the neofecth image showing that even 5.0 kernel is installed, it is 4.19 that is being driven at boot time of Ubuntu Disk 19.04, where Kernel 5.0 does not appear in the advanced options of the initial grub."
1818772,2019-03-06 03:30:59 UTC,"There is only the Kernel 4.19 in the Grub options, even though you have installed the kernel 5.0."
1818772,2019-03-06 03:27:33 UTC,Image of kernel 5.0 installed and appearing in synaptcis
1818772,2019-03-06 03:26:37 UTC,Image of kernel 5.0 installed by terminal appearing in sudo update-grub
1818772,2019-03-06 16:15:30 UTC,"Ok, reassigning this to grub2 since it's now confirmed that this is what you're using."
1818778,2019-08-13 05:52:25 UTC,Matthias: Thanks for the upload in python3.8; I have verified this is working as expected
1818778,2019-11-04 15:59:00 UTC,"Hello Trent, or anyone else affected,"
1818778,2019-10-21 10:50:36 UTC,"Hello Trent, or anyone else affected,"
1818778,2019-05-15 20:34:31 UTC,This bug was fixed in the package python3.8 - 3.8.0~a4-3
1818778,2019-11-07 09:48:53 UTC,This bug was fixed in the package python3.8 - 3.8.0-3~19.04
1818778,2019-03-12 20:42:02 UTC,The systemtap dependency may be easier to handle this time around than last time: we've slightly changed the rules about build-dependencies:
1818778,2019-03-06 08:35:33 UTC,You can unsubscribe ubuntu-sponsors from this
1818778,2019-03-06 08:21:05 UTC,"The attachment ""lp1818778-python3.8-enable-usdt.patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1818778,2019-03-06 05:17:46 UTC,Adding patch (git format-patch) against upstream Debian cpython-team/python3 git repository (canonical home of debian/ for python3 packages)
1818778,2019-03-06 04:51:34 UTC,"Attaching debdiff showing how to enable build-time support. debian/control is generated for the python version by debian/control.in so we patch both files, then enable --with-dtrace in the rules."
1818778,2019-04-20 20:16:05 UTC,Unsubscribing the Ubuntu Sponsors Team as per the comment in #4.
1818785,2019-07-03 17:27:30 UTC,Here is a forum thread which shows that the need to keep the existing reference designators is a perennial problem: https://forum.kicad.info/t/move-blocks-between-sheets-maintaining-references/9081
1818785,2019-06-27 13:44:41 UTC,"@JP, I think the paste code by-and-large uses your algorithm from https://bugs.launchpad.net/kicad/+bug/1789048."
1818785,2019-06-27 10:55:34 UTC,Be *extremely* careful with annotate/clear annotate stuff:
1818785,2019-06-27 07:27:30 UTC,"OK, I have to test further how they work now. I just thought that it's natural that copy/paste will clear the annotations because inside one design there can't be the same annotation twice, and the most important (frequent) use case for copy/paste is inside one and the same design. Appending, on the other hand, comes from another design and it would make sense to keep the annotations, because they can be cleared and changed afterwards anyways but can't be restored when they have been automatically cleared."
1818785,2019-06-26 22:54:13 UTC,"My thinking was that now that there are two ways to accomplish it, it makes sense for one to clear the annotations (append) and one not to (paste)."
1818785,2019-06-26 20:52:45 UTC,"Jeff, what's the connection between your latest statement (which in itself is true) on the one hand and the original bug report and the Won't Fix status on the other? There may be a reason for the new status but the new copypaste capability isn't one as far as the original problem (appending schematic) is concerned."
1818785,2019-06-26 20:19:00 UTC,"The same-instance rules no longer apply.  Eeschema cut/copy/paste uses the system clipboard, so you can do it between instances (or even between, say, Eeschema and a text editor)."
1818785,2019-06-27 10:07:24 UTC,"Yeah, there are a bunch of different ways to slice and dice it."
1818785,2019-03-06 16:06:29 UTC,"@eelik, you have to do this in the same instance."
1818785,2019-03-06 19:05:42 UTC,I understand that copying between two files must be done in the same eeschema instance sequentially.
1818785,2019-03-06 09:45:57 UTC,It's not fixed.
1818785,2019-03-06 13:20:18 UTC,I think frank confused it with https://bugs.launchpad.net/kicad/+bug/1805695
1818785,2019-03-06 07:49:59 UTC,"I belive this has been fixed already
Can you test the nightly build?"
1818785,2019-03-06 14:59:56 UTC,I think a bug report for this was already submitted.  The solution discussed was a checkbox to keep the existing annotation.
1818785,2019-03-06 15:33:17 UTC,"I have tried the same procedure than with pcbnew: have the destination in the project, open standalone pcbnew, copy from there, paste to project's pcbnew. This doesn't work for schematic, it doesn't give Paste menu item in destination's menu."
1818785,2019-03-06 14:39:15 UTC,"Reusing old designs, both schematic and layout, would need better mechanisms anyways."
1818797,2019-03-06 08:37:58 UTC,"List of already applied patches:
  * xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE"
1818797,2019-03-06 09:18:23 UTC,"Skipped the following patches (modifications already applied via SAUCE patches):
  * proc: Remove empty line in /proc/self/status"
1818797,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1818802,2019-03-19 09:45:23 UTC,It*
1818802,2019-03-25 02:05:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818802,2019-03-25 02:07:32 UTC,Please try live booting 19.04:
1818802,2019-05-24 04:17:16 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1818802,2019-05-24 04:17:18 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1818802,2019-06-11 18:37:34 UTC,"Hey, Im not quite sure how I can reopen it, if you could tell me I would do it for you. For me this issue had fixed randomly before I upgraded to 19.04 and was not pressent since then."
1818802,2019-06-11 11:10:55 UTC,I can confirm that the same problem affects 19.04 too.
1818802,2019-06-12 01:50:10 UTC,"Filip,"
1818802,2019-06-12 04:57:20 UTC,"Will do, thanks."
1818802,2019-06-11 11:08:20 UTC,"Hey there, same problem here, audio has strange glitches, maybe we could reopen this issue? Both a collegue and I bought this same laptop and we are both affected by this issue, even on recent kernel builds."
1818802,2019-03-19 09:43:27 UTC,I did return yesterday. I uploaded the files you requested before.
1818802,2019-03-06 09:48:19 UTC,Can you please:
1818802,2019-03-14 07:07:09 UTC,"I was not able to replicate this bug for couple of days, thats why I have not uploaded files you requested. I'm not sure if it's gone, or is it just temporary. It used to affect both speakers and headphones. I will let you know when it's back"
1818802,2019-03-19 02:30:36 UTC,No problem. If the issue doesn't return after 60 days and there are no further comments then this bug will automatically close.
1818802,2019-03-06 09:52:05 UTC,"Finally, if the PID of pulseaudio is changing and there is no evidence of a crash then please try:"
1818802,2019-03-08 12:37:49 UTC,"Hey, thanks for helping me, I got a few updates regarding this issue:"
1818802,2019-03-08 13:00:25 UTC,"I forgot to tell you: this issue is only pressent on ubuntu, audio on Windows works fine"
1818802,2019-03-11 02:11:26 UTC,I wonder if 'tlp' or similar is at play...
1818802,2019-03-06 09:50:19 UTC,Please also follow these instructions to check for crashes on the system:
1818802,2019-03-11 18:53:00 UTC,"Hello, it seems like now audio is not working even when on full battery or plugged in. It's so weird."
1818802,2019-03-12 02:10:55 UTC,"Next, please wait until the audio has stopped working AND has later come back, then run:"
1818802,2019-03-12 02:11:45 UTC,"Also, does this bug apply to the laptop's internal speakers? Or are you using headphones?"
1818802,2019-03-14 06:17:22 UTC,Nothing wrong in the dmesg.
1818802,2019-03-11 10:54:34 UTC,There you go
1818803,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1818806,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1818807,2019-03-06 19:33:19 UTC,"Hmm, looks like the functions are registered in the wrong order: local first, then global, then EXSLT. Local functions should take precendence. PR welcome, see the _XPathContext class in ""xpath.pxi""."
1818811,2020-01-21 14:12:44 UTC,"I tried to make it work, doing a Ubuntu ISO chroot (I used Cubic software), I saw the part where the Btrfs subvolts are created and tried to modify them, obviously not having the skills in an advanced way, I'm not managed to make it work."
1818811,2020-07-16 09:17:46 UTC,"Thanks for your work.
Can you please open a merge request at [1]? Thanks!"
1818811,2020-06-21 23:29:40 UTC,"Hello. I finally managed to work and locate the files and the code to change to make the swapfile work on Btrfs, I have tested it on several installations for a few months and the swapfile is created both if you choose ext4 or btrfs.
I'm not a developer, so I don't know if the changes are correct and in style.
Hope it helps."
1818811,2020-06-21 23:13:58 UTC,"Hello. I finally managed to work and locate the files and the code to change to make the swapfile work on Btrfs, I have tested it on several installations for a few months and the swapfile is created both if you choose ext4 or btrfs.
I'm not a developer, so I don't know if the changes are correct and in style.
Hope it helps."
1818811,2020-06-21 23:13:08 UTC,"Hello. I finally managed to work and locate the files and the code to change to make the swapfile work on Btrfs, I have tested it on several installations for a few months and the swapfile is created both if you choose ext4 or btrfs.
I'm not a developer, so I don't know if the changes are correct and in style.
Hope it helps."
1818811,2019-12-14 14:58:03 UTC,Hello. Are there any news? Will it be correct for the 20.04 LTS release?
1818811,2020-06-21 23:35:53 UTC,"Hello. I finally managed to work and locate the files and the code to change to make the swapfile work on Btrfs, I have tested it on several installations for a few months and the swapfile is created both if you choose ext4 or btrfs.
I'm not a developer, so I don't know if the changes are correct and in style.
Hope it helps."
1818811,2019-04-01 04:19:51 UTC,"So the swapfile needs to be NOCOW before allocation [1]:
# truncate -s 0 /swapfile
# chattr +C /swapfile
# fallocate -l 512M /swapfile"
1818811,2019-04-01 11:39:37 UTC,"Now it works, swapfile will activate and work."
1818811,2019-03-06 10:30:07 UTC,This change was made by a bot.
1818811,2019-03-06 10:28:02 UTC,"I forgot to mention that the swapfile was created during the installation of Ubuntu 19.04, not selecting any swap partition, knowing that the swapfile would be activated and that the support would be shortly arrived for the swapfile, on the 5. * kernel"
1818811,2019-03-29 11:09:16 UTC,Unfortunately it doesn't help.
1818811,2019-03-29 13:57:41 UTC,"I don't know if it's useful, but I paste my ""/etc/fstab"" configuration"
1818811,2019-03-29 04:25:17 UTC,"Does ""sudo chattr +C /swapfile"" help?"
1818812,2019-07-11 08:33:50 UTC,The issue was fixed in 0.73 which is in Disco
1818812,2019-07-11 08:38:34 UTC,"Would be probably fine for a SRU but the patch doesn't apply cleanly to the current bionic version, could you try to backport/rebase it?"
1818812,2019-07-11 14:27:04 UTC,"I can't do it myself, I'll have to ask upstream to do it."
1818812,2019-07-19 15:45:07 UTC,"I wrote a comment on the upstream fixing commit asking if there are other commits that are required to apply the fix on Poppler 0.62.0, no answer yet, and I don't think upstream is interested in 0.62.0 any more."
1818813,2019-03-06 10:37:19 UTC,"List of already applied patches:
  * KVM: x86: work around leak of uninitialized stack contents (CVE-2019-7222)
  * KVM: nVMX: unconditionally cancel preemption timer in free_nested (CVE-2019-7221)
  * igb: Fix an issue that PME is not enabled during runtime suspend"
1818813,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1818815,2019-03-06 11:14:13 UTC,"Skipped the following patches (modifications already applied previously):
  * KVM: VMX: Fix x2apic check in vmx_msr_bitmap_mode()"
1818815,2019-03-06 11:05:36 UTC,"List of already applied patches:
  * kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)"
1818815,2019-04-02 10:26:27 UTC,This bug was fixed in the package linux - 4.4.0-145.171
1818816,2019-03-11 07:56:25 UTC,"@kai I tested by switching from UEFI to Legacy mode. There is no problem at all. No need to switch to noacpi mode while installation. After booting everything got worked.
lspci listing properly."
1818816,2019-03-11 06:06:09 UTC,Maybe try 418 series?
1818816,2019-03-07 09:41:15 UTC,Same error with 4.15.0-45-generic kernel
1818816,2019-03-08 04:49:07 UTC,"What happens if LightDM or GDM is in use, instead of startx?"
1818816,2019-03-12 16:30:39 UTC,"If the same kernel works under Bionic but not under Xenial, I guess it's grub2 in Bionic makes the difference."
1818816,2019-03-09 08:19:00 UTC,"Hi Kai,"
1818816,2019-03-13 14:25:55 UTC,"Hi, do you install vanilla/stock Ubuntu Xenial, or the preloaded OEM Xenial?"
1818816,2020-01-02 22:08:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818816,2019-08-07 07:03:06 UTC,"Any update on this request. We have more users reporting the issue on Ubuntu 16.04 UEFI instalallation. As a workaround, we are installing as Legacy mode."
1818816,2019-08-23 18:31:42 UTC,This is not a kernel bug.
1818816,2019-08-23 18:33:10 UTC,"For pciutils (lspci), we need this commit:
commit ab61451d47514c473953a24aa4f4f816b77ade56
Author: Keith Busch <email address hidden>
Date:   Thu Mar 17 13:19:17 2016 -0600"
1818816,2019-08-23 18:36:35 UTC,"However, for both libraries the new commits introduce ABI change, so all packages linked against libpciaccess and libpci need to be rebuilt. So I am not sure how feasible it is."
1818816,2020-01-02 22:09:25 UTC,I'm hitting this issue on some new server hardware when trying to use lspci from pciutils with a 16.04 installation. I'm wondering of there has there been any progress on getting this fix released for Xenial?
1818816,2019-03-17 14:49:11 UTC,Thanks @kai for the help.
1818816,2019-03-07 08:06:24 UTC,"I tried with both (lower) kernel , no luck :( It seems NVIDIA  384 proprietory deb package conflict with the running kernel."
1818816,2019-03-06 11:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818816,2019-03-06 12:04:17 UTC,apport information
1818816,2019-03-06 11:29:51 UTC,"Note:- This is clearly an OS issue. With 18.04 there is no problem. Please let me know where is the culprit...
Type of installation - UEFI with secure boot disabled"
1818816,2019-03-06 12:03:59 UTC,apport information
1818816,2019-03-06 15:14:40 UTC,Can you try to boot the previous kernel 4.15.0-45-generic?
1818816,2019-03-06 12:04:03 UTC,apport information
1818816,2019-03-06 12:04:05 UTC,apport information
1818816,2019-03-06 12:04:06 UTC,apport information
1818816,2019-03-06 12:04:01 UTC,apport information
1818816,2019-03-06 12:04:09 UTC,apport information
1818816,2019-03-06 12:04:10 UTC,apport information
1818816,2019-03-06 12:04:11 UTC,apport information
1818816,2019-03-06 12:04:13 UTC,apport information
1818816,2019-03-06 12:04:14 UTC,apport information
1818816,2019-03-06 12:04:16 UTC,apport information
1818816,2019-03-06 12:04:07 UTC,apport information
1818821,2019-03-06 12:05:10 UTC,"Hello,"
1818821,2019-03-06 12:09:56 UTC,"Hi ,"
1818823,2019-03-11 09:26:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642391"
1818823,2019-06-19 11:18:09 UTC,"Reviewed:  https://review.opendev.org/642391
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=6f807b6b05ea4a9df93ed23111f10a5041377612
Submitter: Zuul
Branch:    master"
1818823,2019-09-13 16:42:35 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.
1818824,2019-08-14 14:45:57 UTC,I agree that continuing to use the SNAT IP is an oversight. The semantics of associating a FIP imply that all communication across the router changes to a 1-1 NAT of the fixed IP to the floating IP. To me that implies that we should be using the FIP as soon as it is associated.
1818824,2019-12-04 08:52:24 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/656665
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1818824,2019-12-04 08:52:15 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1818824,2019-05-01 16:16:09 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656665"
1818824,2019-05-14 15:04:04 UTC,Getting back to Candido's original question: should we continue using the default SNAT IP once a floating IP is assigned?
1818824,2019-04-30 14:06:39 UTC,"Newbie here and there's a lot to learn. Expect slow resolution. If someone thinks this is too urgent to be assigned to me, please tell me."
1818824,2019-03-15 07:34:38 UTC,the 1818805 is not a duplicate. It is deleting the fip.
1818824,2019-03-15 04:06:19 UTC,the behaviour difference between legacy and dvr looks plausible. i'm not sure how it should be fixed though.
1818824,2019-05-01 11:05:22 UTC,"The only way to keep the connections open is to maintain the old routing path as an exception for the existing connections.
We could differentiate all the old connections updating the entries with a mark, then use the mark to route the traffic differently."
1818824,2019-03-14 14:55:51 UTC,"You mentioned that there is another bug related to this.
Is this a duplicate of the original one.1818805"
1818825,2019-03-31 17:27:57 UTC,"First part of the change for Flylink:
https://github.com/pavel-pimenov/flylinkdc-r5xx/pull/1720"
1818825,2019-03-31 18:16:30 UTC,"Proposed patch for advertising a list of supported protocols:
https://gist.github.com/dennwc/de336c848695232aab72c06b943349ab"
1818825,2019-04-03 23:03:32 UTC,"Same change for EiskaltDC++:
https://github.com/eiskaltdcpp/eiskaltdcpp/pull/396"
1818829,2019-03-11 02:53:12 UTC,apport information
1818829,2019-03-11 02:53:14 UTC,apport information
1818829,2019-03-11 02:53:16 UTC,apport information
1818829,2019-05-10 04:17:50 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1818829,2019-03-11 02:53:21 UTC,apport information
1818829,2019-03-11 02:55:09 UTC,"Done. I changed a couple things since reporting this though. I stopped setting the screen positions in the initial commands I posted. I booted with no monitor attached, without running the script, then connected the monitor and ran it (again, without settings positions) and sent the report while the laptop display was disabled (only using external monitor.) If you need me to run it some other way let me know."
1818829,2019-03-11 02:53:11 UTC,apport information
1818829,2019-03-11 02:53:20 UTC,apport information
1818829,2019-03-11 02:53:09 UTC,apport information
1818829,2019-03-11 02:53:23 UTC,apport information
1818829,2019-03-11 02:53:07 UTC,apport information
1818829,2019-03-11 02:53:05 UTC,apport information
1818829,2019-03-11 02:53:04 UTC,apport information
1818829,2019-03-11 02:53:03 UTC,apport information
1818829,2019-03-11 02:53:02 UTC,apport information
1818829,2019-03-11 02:53:00 UTC,apport information
1818829,2019-03-07 01:57:33 UTC,This doesn't sound like a bug to me. If you manually place your only connected display at a position that's not 0x0 then I would expect that invisible space.
1818829,2019-03-11 02:13:38 UTC,OK. Please run this command to send us more information about the system:
1818829,2019-03-07 14:59:49 UTC,"Do you have a better solution? If I change the HDMI display to -2560x-360 it doesn't work either. Now there is space to the bottom and right of the laptop display (captured in screenshot) and the external monitor is not actually at that position either, it's more like -2560x-180 (not sure if negative values are even supported.) I've attached a screenshot with no external display connected."
1818829,2019-03-11 02:53:08 UTC,apport information
1818834,2019-10-30 09:41:46 UTC,It's already cherry-pick in stein.
1818834,2019-10-30 09:29:45 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/692090"
1818834,2019-06-13 18:32:57 UTC,Installation fails when ipv6 is disabled (grub and systectl). Shouldn't be a check to run ip6tables only if ipv6 is enabled?
1818834,2019-10-30 09:40:11 UTC,"Change abandoned by Natal Ngétal (<email address hidden>) on branch: stable/train
Review: https://review.opendev.org/692090
Reason: Already merged."
1818834,2019-03-14 10:34:32 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.4.0 release.
1818834,2019-03-06 22:34:41 UTC,"Reviewed:  https://review.openstack.org/641316
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b1d82e6acbc79d9db1a54d53cd178080b72d0845
Submitter: Zuul
Branch:    master"
1818834,2019-03-06 13:19:00 UTC,https://review.openstack.org/641316
1818834,2019-03-26 12:50:41 UTC,"So the fix for this was actually okay for deployment, but we will still have the issue during a reboot of undercloud/overcloud"
1818844,2019-06-13 20:19:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665231"
1818844,2019-06-19 14:13:25 UTC,"Reviewed:  https://review.opendev.org/665231
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=092570fc5ef43497c29cf174bfff43323a49fb58
Submitter: Zuul
Branch:    master"
1818844,2019-09-27 09:10:45 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1818845,2019-09-27 09:10:30 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1818845,2019-07-23 17:22:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672334"
1818845,2019-07-24 19:10:01 UTC,"Reviewed:  https://review.opendev.org/672334
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0bf2d68520f57a44510f19aed50a26d217fe52dc
Submitter: Zuul
Branch:    master"
1818846,2019-09-27 09:10:19 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1818846,2019-09-08 05:59:32 UTC,"Reviewed:  https://review.opendev.org/676277
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a09163a3202c32f05cf636559a95fe45c6ea272b
Submitter: Zuul
Branch:    master"
1818846,2019-09-08 06:00:36 UTC,"Reviewed:  https://review.opendev.org/676995
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6aebf179b8b1b48909ea57666f61bbc080bd6888
Submitter: Zuul
Branch:    master"
1818846,2019-09-08 06:00:25 UTC,"Reviewed:  https://review.opendev.org/676847
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ea7acd80362e27c44a299c70504c21fdc7953e21
Submitter: Zuul
Branch:    master"
1818846,2019-09-08 06:00:04 UTC,"Reviewed:  https://review.opendev.org/676287
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=09e699baba89b94a020682ab7d916d67360f4481
Submitter: Zuul
Branch:    master"
1818846,2019-09-08 05:59:54 UTC,"Reviewed:  https://review.opendev.org/676284
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b100825a03920e59700dba7c45b2317344924867
Submitter: Zuul
Branch:    master"
1818846,2019-09-08 05:59:44 UTC,"Reviewed:  https://review.opendev.org/676283
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b5617eee416d168a674283e220f67e2a9f174a19
Submitter: Zuul
Branch:    master"
1818846,2019-09-08 05:11:00 UTC,"Reviewed:  https://review.opendev.org/675807
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0df8d0e2e1519154ec76100f7a4c2fdc8c9c04bb
Submitter: Zuul
Branch:    master"
1818846,2019-09-10 10:16:26 UTC,"Reviewed:  https://review.opendev.org/677004
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9be1caff97355099d25170fe390dd15d6f592d56
Submitter: Zuul
Branch:    master"
1818846,2019-08-16 18:22:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677004"
1818846,2019-08-16 17:41:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676995"
1818846,2019-08-16 01:49:50 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676847"
1818846,2019-08-13 23:14:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676287"
1818846,2019-08-13 22:29:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676284"
1818846,2019-08-13 22:00:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676283"
1818846,2019-08-13 20:46:21 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676277"
1818846,2019-08-12 04:15:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675807"
1818846,2019-08-10 04:42:50 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675720"
1818846,2019-08-19 04:45:17 UTC,"Reviewed:  https://review.opendev.org/675720
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5086709ae2d673716653cd8812247ea5a1cb5e69
Submitter: Zuul
Branch:    master"
1818848,2020-04-13 19:15:48 UTC,Issue already solved upstream.
1818848,2019-03-06 15:04:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641410"
1818848,2019-03-07 14:57:15 UTC,"Change abandoned by Jose Luis Franco (<email address hidden>) on branch: master
Review: https://review.openstack.org/641410
Reason: let's change quickstart to use networwork_data.yaml."
1818849,2019-03-06 15:08:34 UTC,juju_engine_report.yaml after killing two of three controllers.
1818849,2019-03-11 07:35:03 UTC,"If you lose Quorum we probably fail to even bring up the API server at all, to report anything to the user.
We could probably bring up something, though."
1818849,2019-03-11 07:36:10 UTC,"(there are a lot of potential reasons why we cannot, like not being able to authorize because the backend database cannot give us strong consistency, etc.) But you could put up some sort of static error response."
1818850,2019-09-08 05:59:31 UTC,"Reviewed:  https://review.opendev.org/676277
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a09163a3202c32f05cf636559a95fe45c6ea272b
Submitter: Zuul
Branch:    master"
1818850,2019-09-10 10:16:17 UTC,"Reviewed:  https://review.opendev.org/677004
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=9be1caff97355099d25170fe390dd15d6f592d56
Submitter: Zuul
Branch:    master"
1818850,2019-09-09 23:55:14 UTC,"Reviewed:  https://review.opendev.org/677020
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=686ec6dda6dfa73e9634979231bcd9b2edbd1da8
Submitter: Zuul
Branch:    master"
1818850,2019-09-08 06:00:14 UTC,"Reviewed:  https://review.opendev.org/676847
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=ea7acd80362e27c44a299c70504c21fdc7953e21
Submitter: Zuul
Branch:    master"
1818850,2019-09-08 06:00:02 UTC,"Reviewed:  https://review.opendev.org/676287
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=09e699baba89b94a020682ab7d916d67360f4481
Submitter: Zuul
Branch:    master"
1818850,2019-09-08 05:59:53 UTC,"Reviewed:  https://review.opendev.org/676284
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b100825a03920e59700dba7c45b2317344924867
Submitter: Zuul
Branch:    master"
1818850,2019-09-08 05:59:43 UTC,"Reviewed:  https://review.opendev.org/676283
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=b5617eee416d168a674283e220f67e2a9f174a19
Submitter: Zuul
Branch:    master"
1818850,2019-09-08 05:10:59 UTC,"Reviewed:  https://review.opendev.org/675807
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0df8d0e2e1519154ec76100f7a4c2fdc8c9c04bb
Submitter: Zuul
Branch:    master"
1818850,2019-09-27 09:10:20 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1818850,2019-08-16 18:57:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677020"
1818850,2019-08-16 18:22:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677004"
1818850,2019-08-16 01:49:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676847"
1818850,2019-08-13 23:14:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676287"
1818850,2019-08-13 22:29:12 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676284"
1818850,2019-08-13 22:00:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676283"
1818850,2019-08-13 20:46:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676277"
1818850,2019-08-12 04:15:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675807"
1818850,2019-08-10 04:42:48 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675720"
1818850,2019-08-19 04:45:15 UTC,"Reviewed:  https://review.opendev.org/675720
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5086709ae2d673716653cd8812247ea5a1cb5e69
Submitter: Zuul
Branch:    master"
1818857,2019-09-16 14:27:38 UTC,Migrated to https://github.com/widelands/widelands/issues/1723
1818860,2019-04-26 06:01:59 UTC,"Reviewed:  https://review.opendev.org/653374
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=476b3ca97c60d8af96cb383ff03e715374fbe402
Submitter: Zuul
Branch:    master"
1818860,2019-04-17 09:50:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653374"
1818860,2019-03-06 16:02:44 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641429"
1818860,2019-03-21 07:08:33 UTC,"looks green removing alert & fix released
http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-undercloud-containers"
1818860,2019-03-06 23:07:16 UTC,"Reviewed:  https://review.openstack.org/641429
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=6f66380490263ad4c55375509b878e38c6479604
Submitter: Zuul
Branch:    master"
1818860,2019-04-04 11:41:19 UTC,reopening because the job is green because we are skipping the test.
1818862,2019-03-25 14:03:16 UTC,See LP: #1821525
1818862,2019-03-11 09:32:07 UTC,Thanks. Upstream bug: https://github.com/intel/intel-vaapi-driver/issues/448
1818862,2019-03-11 09:22:51 UTC,"Hmm, not sure what I did wrong last time, but you're right: Uninstalling i965-va-driver does resolve the issue. I'll report the crash at the intel-vaapi-driver repo as suggested."
1818862,2019-03-11 02:17:27 UTC,"Can you clarify what ""did not do anything"" means?  Because if you have uninstalled package i965-va-driver then it should be impossible to encounter the crash mentioned above. If not doing anything means that totem still hangs then the cause of the hang is likely something different again."
1818862,2019-03-08 10:32:06 UTC,"Hmm, so removing i965-va-driver did not do anything, even after a reboot. What did work is to remove gstreamer1.0-vaapi. What are the side effects of this? Does it basically just mean that anything using gstreamer would have HW acceleration disabled?"
1818862,2019-03-08 02:10:43 UTC,"It may be a coincidence, but another Mesa Intel gen9 crash in totem is bug 1815236."
1818862,2019-03-07 21:28:42 UTC,And here is the backtrace for that error:
1818862,2019-03-07 21:23:32 UTC,"That was playing an .mp4 file. When I play an .mov file, totem crashes instead of hangs, providing a hopefully more useful error message:"
1818862,2019-03-07 21:20:07 UTC,"If I run totem from the command-line, it has the following output before it hangs:"
1818862,2019-03-07 17:51:55 UTC,Thank you for your bug report. I can't reproduce the issue here. Do you get any error/warning on the standard output/journal log when getting the issue? Could you get a gdb backtrace?
1818862,2019-03-08 02:13:50 UTC,Oh. gen9_mfd.c and gen9_hcpd_get_reference_picture_frame_id are from intel-vaapi-driver.
1818863,2019-03-06 17:36:06 UTC,Observed in 3.2.4.
1818863,2019-09-13 14:12:41 UTC,The problem remains present in 3.3.2. Probably the easy  solution would be to open links in a new tab.
1818865,2019-05-14 11:45:19 UTC,"I would expect to see this early in a deployment (before migrations are run). Can you attach the juju bundle that showed this error, or a new reproducer?"
1818865,2019-05-15 14:43:30 UTC,attached is the bundle.  It's deploying Rocky Bionic.
1818865,2019-07-15 04:17:27 UTC,[Expired for OpenStack nova-cloud-controller charm because there has been no activity for 60 days.]
1818867,2019-08-14 11:48:26 UTC,"Fixed in revision 6fb96891b15b7b55fdb51c368bb8a5b698e6ae83
https://git.launchpad.net/kicad/patch/?id=6fb96891b15b7b55fdb51c368bb8a5b698e6ae83"
1818867,2019-03-20 20:41:55 UTC,"I see that the trace image in one button (R-G-B) is 128 - 128 - 128 and the other is 0 - 128 - 0.  That sounds significant, but I think the relatively small size of the area with differentiated color makes it more difficult to discern."
1818867,2019-03-20 18:20:20 UTC,The colour difference is extremely subtle to say the least. Maybe an idea would be to mark the left toolbar as view options toolbar in some way. Or alternatively add some identifier that the button on the right is for adding zones while the left one is for selecting the view mode (A small plus on the button to add zone and a small display on the one for the viewing options come to mind.)
1818867,2019-03-07 08:27:01 UTC,I am not really sure if i would clasify this as a wishlist item to be honest. It is a clear bug if you want kicad to be accessible by people with bad vision (colour blindness for example.)
1818867,2019-03-11 13:37:39 UTC,"It is not the same icon. It has the same shape, but not the same colors."
1818867,2019-03-07 12:20:51 UTC,Fair enough.
1818867,2019-03-11 14:31:06 UTC,"Hi, Nick"
1818873,2019-03-06 16:58:48 UTC,Note that the migration.status is also set to 'completed' even if post_live_migration_at_destination fails:
1818873,2019-03-06 17:00:05 UTC,This might be a duplicate of bug 1628606.
1818874,2019-03-06 17:21:56 UTC,It is fixed in 3.2.3. I think this is a duplicate but the one I found is older and doesn't have the fix --- https://bugs.launchpad.net/evergreen/+bug/1206244
1818874,2019-03-06 17:25:50 UTC,https://bugs.launchpad.net/evergreen/+bug/1724348
1818876,2019-03-12 22:20:20 UTC,"Still not enough, as cryptsetup doesn't include anything in the initrd, if there are no crypto mount points available. Trying to fix this harder."
1818876,2019-03-29 15:39:08 UTC,I see one of the two branches merged? is this fix?  what else are we waiting on?
1818877,2019-03-07 09:24:10 UTC,"MP [1] linked
@Rbasak - for your review"
1818877,2019-03-06 17:10:49 UTC,Assigning to @paelzer as requested by him
1818877,2019-03-06 17:21:09 UTC,Link to the Xorg failure: http://paste.ubuntu.com/p/d6ypgxzkyv/
1818877,2019-03-07 09:10:00 UTC,"Yeah, since uvtool knows we have Ubuntu guests we can take QXL which should also be faster and more efficient.
It is working with VNC, but much better with the spice protocol which enables additional viewers as well as potential audio passthrough and such."
1818877,2019-03-07 09:10:53 UTC,"As I have assumed we don't need to cut VNC (our current default backend) to add spice, so that should work great for people relying on the old but also anyone that wants to benefit from the new things."
1818877,2019-03-07 09:11:43 UTC,I tested various templates and will propose a branch for x86 that will make it QXL and add Spice (using the same local only method as VNC to avoid streaming unintentionally).
1818877,2019-03-08 06:12:48 UTC,MP Pushed and merged.
1818877,2020-09-21 07:13:56 UTC,"This is in Focal, setting to Released"
1818879,2019-03-07 08:13:39 UTC,apport information
1818879,2019-03-07 08:13:40 UTC,apport information
1818879,2019-03-07 08:13:42 UTC,apport information
1818879,2019-03-07 08:14:28 UTC,Just the plain Disco kernel environment as you get it when spawning a new guest - data provided changing state of both bug tasks back.
1818879,2019-03-07 08:20:59 UTC,"ajax gave a patch to fix selecting a better default bpp, so that'll fix the server to start even without cirrus.ko"
1818879,2019-03-12 20:51:15 UTC,This bug was fixed in the package xserver-xorg-video-vesa - 1:2.4.0-2
1818879,2019-03-07 08:13:38 UTC,apport information
1818879,2019-03-07 08:13:43 UTC,apport information
1818879,2019-03-07 08:13:37 UTC,apport information
1818879,2019-03-07 08:13:35 UTC,apport information
1818879,2019-03-07 08:13:34 UTC,apport information
1818879,2019-03-07 08:13:31 UTC,apport information
1818879,2019-03-07 08:13:30 UTC,"ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116,  1 Mar  7 08:12 seq
 crw-rw---- 1 root audio 116, 33 Mar  7 08:12 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 19.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: xorg-server
PciMultimedia:"
1818879,2019-03-07 08:07:02 UTC,"@Daniel - on one hand it is also a change in xorg that makes the driver missing now - so an FYI for that.
But in an IRC discussion there were two potential paths to resolve this issue overall:
- make the cirrus.ko available in the non -extra package so that it works out of the box using this driver
- tjaaltonen identified the message around fbbpp (24) which could be a fix in X source to get base VESA working even without cirrus.ko being in place"
1818879,2019-03-07 02:04:57 UTC,"Are you suggesting anything in Xorg needs fixing, or is the Xorg task just an FYI because it's related?"
1818879,2019-03-06 17:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818879,2019-03-06 17:22:28 UTC,Adding a test for xorg for their consideration.
1818879,2019-03-06 17:21:46 UTC,"Another alternative would be to have vesa specify a working bpp value, if that is the only problem there."
1818881,2019-05-12 15:22:26 UTC,apport information
1818881,2019-05-12 15:22:25 UTC,apport information
1818881,2019-05-12 15:22:24 UTC,apport information
1818881,2019-05-12 15:22:23 UTC,apport information
1818881,2019-05-12 15:22:21 UTC,apport information
1818881,2019-04-04 03:11:39 UTC,@Stephan
1818881,2019-05-12 15:22:18 UTC,"ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  daniel     1740 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2019-04-28 (13 days ago)
InstallationMedia: Ubuntu 19.04 ""Disco Dingo"" - Release amd64 (20190416)
MachineType: Dell Inc. XPS 13 9380
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic  N/A
 linux-firmware                            1.178
Tags:  disco
Uname: Linux 5.0.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/29/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 0KTW76
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc."
1818881,2019-05-11 23:32:31 UTC,I have a 2019 Dell XPS 13 (9380). I bought the Developer Edition from Dell which came with Ubuntu 18.04.
1818881,2019-05-12 15:22:29 UTC,apport information
1818881,2019-04-03 10:03:40 UTC,"for record.
sosreport got from OEM image X37_A02 on ITAW-DVT2-C3 (201810-26509)"
1818881,2019-05-12 15:22:19 UTC,apport information
1818881,2019-05-12 15:22:31 UTC,apport information
1818881,2019-03-06 18:34:05 UTC,apport information
1818881,2019-05-12 15:22:33 UTC,apport information
1818881,2019-05-12 15:22:35 UTC,apport information
1818881,2019-05-12 15:22:36 UTC,apport information
1818881,2019-05-12 15:22:38 UTC,apport information
1818881,2019-05-12 15:22:40 UTC,apport information
1818881,2019-05-12 15:22:41 UTC,apport information
1818881,2019-05-12 16:06:49 UTC,I've attached logs from my XPS 13 (9380) with the same wireless chipset (Qualcomm Atheros QCA6174).
1818881,2019-07-28 00:46:07 UTC,"I still hit this issue a few times per week, usually after resuming from suspend."
1818881,2019-07-30 15:54:03 UTC,"from #31, the wifi should work well on preload image 18.04+oem kernel 4.15(also refer to [1]), so it could be a regression on non-LTS Ubuntu. In this case, the crash could be caused by a kernel regression or some binary in linux-firmware."
1818881,2020-10-30 07:47:29 UTC,I have xps 9370 and was affected by the same issue on Ubuntu 20.04. Recently updated the notebook to the 20.10 but the issue still persists.
1818881,2020-10-31 14:11:27 UTC,"Alexander,"
1818881,2019-04-03 08:13:05 UTC,"From what I can understand it can be a firmware bug.
The AM{P,S}DU data was read from firmware (via DMA) and get hashed. When the driver tries to assemble it in order, the address isn't in the hash."
1818881,2019-05-12 15:22:32 UTC,apport information
1818881,2019-04-02 17:45:15 UTC,I've reset the machine with the latest OEM image to retest. I am now experiencing system freezes at random times. I've generated a new sosreport and am attaching it to this case.
1818881,2019-03-06 18:33:59 UTC,apport information
1818881,2019-04-01 16:11:22 UTC,Hi
1818881,2019-03-06 18:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818881,2019-03-06 18:33:37 UTC,apport information
1818881,2019-03-06 18:33:38 UTC,apport information
1818881,2019-03-06 18:33:40 UTC,apport information
1818881,2019-03-06 18:33:41 UTC,apport information
1818881,2019-03-06 18:33:43 UTC,apport information
1818881,2019-03-06 18:33:44 UTC,apport information
1818881,2019-03-06 18:33:50 UTC,apport information
1818881,2019-03-06 18:33:52 UTC,apport information
1818881,2019-04-02 17:15:07 UTC,"shared more information from Stephan,
""
so just to be clear, I often times am able to stay on 5 hours on a Meet with no problem
then it just starts happening and I can't seem to get out of it
"""
1818881,2019-03-06 18:33:55 UTC,apport information
1818881,2019-03-06 18:33:56 UTC,apport information
1818881,2019-03-06 18:33:53 UTC,apport information
1818881,2019-03-29 10:43:07 UTC,"I tried ping out for about 2 hours on the same machine (CID:201810-26508) of #12
But not see this issue yet, I will put the machine ping out for over weekend to see if I can reproduce this issue."
1818881,2019-03-06 18:34:02 UTC,apport information
1818881,2019-03-08 05:57:50 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0]."
1818881,2019-03-08 05:58:55 UTC,"This commit particular:
commit 85bd0107c6cd445a33066a57658fc585244a1100
Author: Yu Wang <email address hidden>
Date:   Thu Dec 20 09:53:26 2018 +0200"
1818881,2019-03-29 03:35:31 UTC,"@sfabel
thanks for your report.
Do you convenient help to get sosreport for us to clarify which generation of xps 13 for this issue?"
1818881,2019-03-29 03:44:04 UTC,dmi.product.name: XPS 13 9380?
1818881,2019-03-29 07:53:29 UTC,"I just got a XPS 13 9380, not find the issue yet, I'm keep using that machine wireless to see if I can reproduce here."
1818881,2019-03-06 18:33:58 UTC,apport information
1818881,2019-04-01 04:22:57 UTC,"the sosreport of the environment of #21 and #22.
On that environment, the wifi works well on that machine after over weekend ping out + youtube playing."
1818881,2019-04-01 04:29:58 UTC,"this morning, I also tried older released 18.04.2 image[1], which have the same older kernel 4.18.0-15-generic as this ticket description."
1818883,2019-06-21 17:19:36 UTC,Committed to 5.1 in commit d80759efb8bc1ab9bf62f0319fd2b6b15259a023.
1818886,2019-04-10 17:05:23 UTC,"Arx, can you please check if we want to re-enable this test from skip_list ?
Thanks"
1818886,2019-03-07 23:12:28 UTC,"Reviewed:  https://review.openstack.org/641455
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=2c655258ed600d182870fbe78f610c6c087b4ec6
Submitter: Zuul
Branch:    master"
1818886,2019-04-11 09:02:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/651730"
1818886,2019-03-06 18:09:59 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641455"
1818886,2019-04-15 21:03:46 UTC,"Reviewed:  https://review.openstack.org/651730
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=3dabc41d032eeb8ab23b1f36d099b1757f2259d2
Submitter: Zuul
Branch:    master"
1818887,2019-08-22 15:35:16 UTC,"Email sent to mailing list:
http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005764.html"
1818887,2019-12-12 21:42:25 UTC,I asked Chris Winnicki to re-test this scenario in a recent load and he confirmed that he is not able to reproduce this issue.
1818887,2019-08-21 20:21:06 UTC,"The first time service-parameter-apply is applied, we have the process error and the fault alarm kept, the second time it executes with out error and the fault alarm is cleared:"
1818887,2019-08-23 18:50:57 UTC,"As per agreement with the community, moving all unresolved medium/low priority bugs from stx.2.0 to stx.3.0"
1818887,2019-07-10 13:46:41 UTC,My research (mental map) will be written down here: https://github.com/xe1gyq/starlingx/blob/master/bugs/1818887.md
1818887,2019-07-10 12:00:29 UTC,"I am taking the ownership of this bug to solve, after an initial review I was able to reproduce. I will provide more details and questions in the next couple of days looking to have an estimated time of completion."
1818887,2019-06-21 12:24:35 UTC,Assigned to Bruce for re-assignment.
1818887,2019-03-06 18:20:07 UTC,Marking as release gating until further investigation. Low priority given the issue is not reproducible 10% of the time.
1818887,2019-03-06 17:56:42 UTC,Logs attached: yow-cgcs-wolfpass-15-controller-0_20190304.193510.tar
1818892,2019-03-11 20:07:55 UTC,"Fwiw wheel 0.32.3-2 has been synced to disco-proposed, however it doesn't seem to have migrated to the release archive. https://bugs.launchpad.net/ubuntu/+source/wheel/0.32.3-2"
1818892,2020-07-23 16:59:01 UTC,0.32.3-2 Published in eoan-release on 2019-04-18
1818896,2019-03-07 07:26:13 UTC,"This is actually directly contra-indicated by the OpenStack security guide, which recommends removing the admin-token from Keystone."
1818896,2019-03-11 10:33:27 UTC,token != password
1818896,2019-08-02 15:07:50 UTC,"Unfortunately, dropping the token from the keystone.conf is still not going to help if we keep it on disk in the unit-state.db or relations.  Ultimately, charms start breaking if someone changes the admin password (even if intentional) outside of a charm operation to change admin-password."
1818896,2019-08-02 15:25:19 UTC,How about we completely hide the charm admin account from the end user and add an action to the keystone charm to allow an end-user admin account to be created; this helps mitigate this issue somewhat but does not completely remove it.
1818896,2020-03-30 18:36:07 UTC,"Its worth noting that the Openstack admin account password can be changed though the keystone config parameter for ""admin-password"", and that by using ""juju config keystone --reset admin-password"" it will remove the newly set password only from juju, and the admin account's password will remain as what was previously set."
1818899,2019-03-06 19:37:47 UTC,apport information
1818899,2019-03-06 19:37:48 UTC,apport information
1818899,2019-03-06 20:08:33 UTC,"I installed an older kernel, and was able to boot and log in. But the external display (HDMI) still didn't work. In desperation I went to Settings -> Users -> Automatic Login."
1818899,2019-03-07 02:10:54 UTC,"Judging by linux-image-4.15.0-46-generic.259292.crash, it appears a kernel crash in the nouveau driver is the problem here."
1818899,2019-03-07 02:30:06 UTC,This change was made by a bot.
1818899,2019-03-07 04:34:42 UTC,"There are two nouveau commits which landed in v4.18-rc6 get backport to Ubuntu's kernel.
Can you test mainline kernel v4.18-rc6 and see if the issue also happens there?"
1818899,2019-03-16 16:31:55 UTC,The next step is to test v4.18-rc5.
1818899,2019-03-08 09:55:32 UTC,"I tried installing 4.18, but it persisted. I tried an older kernel, and then the networking stopped working. I tried re-installing Bionic Beaver, and when booting from USB everything works. But after install and update, it's broken again."
1818899,2019-03-14 13:19:29 UTC,I have the same problem
1818899,2019-03-14 13:20:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818899,2019-03-06 19:37:45 UTC,apport information
1818899,2019-03-22 16:50:44 UTC,"Hi,
just an update, probably not related to the nvidia driver issue itself but perhaps useful for people that stumble upon this page for a similar problem."
1818899,2019-03-07 08:47:00 UTC,"@vanvugt, I installed nvidia-driver-390, and now the second display doesn't work (again). I have removed it, but the damage persists. I'll see what I can do re disabling in BIOS."
1818899,2019-03-06 19:37:44 UTC,apport information
1818899,2019-03-06 19:37:38 UTC,apport information
1818899,2019-03-06 19:37:41 UTC,apport information
1818899,2019-03-06 19:37:28 UTC,apport information
1818899,2019-03-06 19:37:29 UTC,apport information
1818899,2019-03-06 19:37:30 UTC,apport information
1818899,2019-03-06 19:37:32 UTC,apport information
1818899,2019-03-06 19:37:42 UTC,apport information
1818899,2019-03-06 19:37:34 UTC,apport information
1818899,2019-03-06 19:37:33 UTC,apport information
1818899,2019-03-06 19:37:35 UTC,apport information
1818899,2019-03-06 19:37:36 UTC,apport information
1818899,2019-03-06 19:37:37 UTC,apport information
1818899,2019-03-06 19:37:40 UTC,apport information
1818899,2019-03-06 19:37:34 UTC,apport information
1818903,2019-03-07 01:07:30 UTC,Reproduced the bug:
1818903,2019-03-07 01:08:18 UTC,After a reset:
1818904,2021-01-27 14:24:18 UTC,Noting that this is improved in both the Bootstrap OPAC and the new staff catalog.
1818912,2020-06-05 17:22:17 UTC,"Rogan, we have installed the patch for bug 1870605 on our training server where I can reliably test this bug. It does not seem to have any impact."
1818912,2020-06-05 12:59:31 UTC,Given the unclear cause reported here and it's presence in production but not test data I wonder if the actual cause (at least in part) might be:  https://bugs.launchpad.net/evergreen/+bug/1870605
1818912,2020-03-27 21:22:21 UTC,"Ah! Thanks for clarifying that, John!  I'll clean up the branch (per Rogan's note) in any case and go back through the timestamp logic to see if that is, in fact, needed."
1818912,2020-03-27 21:04:54 UTC,"FYI, I didn't test your branch, Mike. (very sorry if that wasn't clear!). I was just providing a steps a tester might be able to take in response to Rogan's comment. I was waiting for a pull request to look at the branch, (and time to do it). Time is an odd concept at the moment."
1818912,2020-03-27 20:51:59 UTC,"Thanks for testing, John.  I think the ""+ 1 second"" part that I removed with the second truncation may still be necessary, so I'll work on an update to my branch that adds that back (unless you want to grab that).  It'll be Monday before I can come back to it, though."
1818912,2020-03-27 19:18:43 UTC,I just performed the same test I presented in my initial report on a system running 3.4.2. Same behavior happened. I picked a day that only had 12 circulations due.
1818912,2020-03-24 15:18:59 UTC,"I believe I've identified a way some of this may be occurring.  I've pushed a branch for folks to look at, but not yet marking it pull-request."
1818912,2020-03-23 15:15:45 UTC,"Since my initial report, I noticed that the undesired behavior doesn't just happen on single day closures, but also multiple day ones depending on surrounding closed dates."
1818912,2020-03-20 21:49:39 UTC,The function evergreen.find_next_open_time is used to find the next time to set items.  After an initial misconfiguration on my part that involving time zones I tested this and don't see an issue with the date returned.  On a stock test data 3.4 beta system I set BR2 closed on Saturdays and set an emergency closing for a Yeti attack on today (Friday).  It correctly gave me the end of the next open day.
1818912,2019-11-11 21:24:55 UTC,"Hello,"
1818912,2019-11-11 19:42:14 UTC,"Hello All,
I can confirm that this bug is still affecting Evergreen 3.3.4. for the PAILS SPARK group."
1818912,2020-03-27 14:42:32 UTC,I've been trying to recreate the failed behavior on a stock test system and can't though I can see where on a production system something has definitely happened.  One closed emergency event where all circs should have pushed out to a Monday had 74 do so but another 184 did not and fell on the Sunday where the library was closed.
1818914,2020-08-05 17:51:36 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/744958"
1818914,2020-09-11 17:22:22 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/751367"
1818914,2020-09-11 16:33:12 UTC,"Related fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/751352"
1818914,2020-09-02 21:43:53 UTC,"Reviewed:  https://review.opendev.org/744958
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=44376d2e212e0f9405a58dc7fc4d5b38d70ac42e
Submitter: Zuul
Branch:    master"
1818914,2020-09-02 15:27:33 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/741995
Reason: Abandoning this in favor of https://review.opendev.org/#/c/744958/8 which is the same code change but with a better commit message that provides context on a bug the change also addresses."
1818914,2020-09-17 13:03:59 UTC,"Reviewed:  https://review.opendev.org/751352
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ce95af2caf69cb1b650459718fd4fa5f00ff28f5
Submitter: Zuul
Branch:    stable/ussuri"
1818914,2019-09-27 09:03:20 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1818914,2019-03-07 21:10:59 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/641806"
1818914,2019-04-27 19:14:53 UTC,"Reviewed:  https://review.opendev.org/641521
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=54877e06f13b13134f2030557cd779f947a43c24
Submitter: Zuul
Branch:    master"
1818914,2019-03-07 21:04:10 UTC,This is the related starlingx patch:
1818914,2019-03-06 23:52:34 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641521"
1818914,2019-03-06 22:10:28 UTC,Part of this is also sort of reported in a very old bug 1498126.
1818914,2019-06-07 12:35:57 UTC,"Reviewed:  https://review.opendev.org/641806
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ad9f37350ad1f4e598a9a5df559b9160db1a11c1
Submitter: Zuul
Branch:    master"
1818917,2021-01-21 20:32:21 UTC,"This is causing problems with our libraries. The documentation does not match the actual behavior and even if the documentation were updated to match the behavior, having it void only some of the fines doesn't make any practical sense to patrons or to library staff."
1818917,2020-04-15 13:01:30 UTC,Never mind! I figured it out with some help from my friends.
1818917,2020-04-14 23:05:58 UTC,Terran - I don't know what is controlling the behavior. Our org unit isn't listed for anything in Notification / Action Triggers. Equinox had to turn off our courtesy notices.
1818917,2020-04-14 15:25:06 UTC,"Diane - is your library system doing the change to Lost via an action trigger? If so, you can temporarily disable it through Local Admin > Notification / Action Triggers. (We have two related action triggers that we temporarily disabled - one for the action of changing the item status / creating the bill, and one that sends a message to the patron when that happens.) We'll re-enable it after we are able to reopen."
1818917,2020-04-07 18:14:29 UTC,"FWIW, relying on backdating/amnesty mode checkins doesn't work so well if one has an automated return system."
1818917,2020-03-17 18:55:42 UTC,"Hi John,"
1818917,2020-04-14 14:59:13 UTC,"We closed for Covid-19 on March 18. Items due in February are now six weeks overdue, the status is changing to LOST, and patrons have bills that prevent them from using our online resources. This is a big problem. We will be closed for six more weeks."
1818918,2020-11-15 20:43:49 UTC,@sergiodj many thanks for the help here
1818918,2020-11-14 00:08:04 UTC,This is still an issue with hirsute afaict.
1818918,2020-11-14 00:15:56 UTC,I was able to reproduce what Brian is reporting here.
1818918,2020-11-14 02:51:31 UTC,"So the issue is: if there is a .gnu_debugaltlink GDB will try to load that file and throw an error if it can't. That path is absolute and GDB does _not_ look for that path/file anywhere else, not even inside 'debug-file-directory'."
1818918,2020-11-15 00:07:11 UTC,"@tdaitx asked me to take a look at this problem, and here is what I found."
1818918,2020-12-02 03:09:35 UTC,"FWIW, the fix has just been pushed upstream:"
1818918,2020-11-06 19:11:16 UTC,I've come up with a simpler test case on an Ubuntu 20.10 system which follows:
1818918,2021-02-03 19:51:11 UTC,"@Brian, Ops, sorry.  I forgot about this bug, and then I kind of assumed that it had already been backported on Debian.  This is just for hirsute, right?  I can backport it now, give me just a second."
1818918,2021-02-03 19:55:14 UTC,"Ah, I see that is has indeed been backport by Debian, and is already in hirsute: debian/patches/2bf3b79d05bf85e41cbdcb020bd1cc424f59dd9a.diff is the patch.  @Brian, would you like me to backport the patch to another release?"
1818918,2021-02-03 20:26:02 UTC,gdb (10.1-1.3) unstable; urgency=medium
1818918,2021-02-03 20:30:48 UTC,"@Sergio - Given the way the retracers are currently setup we are using the version of gdb for the release for the crash we are retracing, subsequently we'd need to SRU this to every release. Given that I've already worked around this specific issue in apport backporting the fix seems unnecessary."
1818918,2021-02-03 20:56:10 UTC,"Ah, good to know!  No problem at all, Brian!  Cheers :-)"
1818918,2020-11-13 23:55:54 UTC,I tried the testcase from comment #12 in Focal and Hirsute and it worked just fine:
1818918,2021-02-03 19:26:18 UTC,@Sergio - Is this still something you are planning on backporting?
1818918,2020-11-13 23:34:06 UTC,"Ah, thanks for pointing that out but there is still an issue with the test case in comment #12 as the .gnu_debugaltlink file is still not loaded."
1818918,2019-11-05 04:17:55 UTC,[Expired for gdb (Ubuntu) because there has been no activity for 60 days.]
1818918,2020-11-12 21:02:35 UTC,This is also true with gdb 10.1 from hirsute-proposed.
1818918,2019-04-05 22:45:46 UTC,This is still an issue with gdb version 8.2.90.20190311-0ubuntu1 in disco.
1818918,2019-05-19 17:11:10 UTC,please can you can up with a test case not involving snaps?  Asking because I can't.
1818918,2019-05-21 17:33:39 UTC,"This test case doesn't involve snaps, notice the file switch to gdb:"
1818918,2019-07-21 04:17:31 UTC,[Expired for gdb (Ubuntu) because there has been no activity for 60 days.]
1818918,2019-08-29 06:03:48 UTC,"looking up the .gnu_debugaltlink in a normal debug session works perfectly fine.  Please can you show this behavior without any sandbox, or try to diagnose why it doesn't work in this sandbox?  I am not familiar with this sandbox environment."
1818918,2019-09-05 19:07:08 UTC,I've discovered that I can workaround this issue by modifying the argument passed to the 'set debug-file-directory' option of gdb e.g. by using the following:
1818918,2019-08-28 23:51:07 UTC,I recently started seeing issues with some other applications too e.g.:
1818918,2020-03-11 13:17:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818918,2020-10-13 19:49:53 UTC,"I've managed to workaround this in apport by creating a symlink from the host system's /usr/share/debug/.dwz to the gdb sandbox's /usr/share/debug/.dwz folder. That being said I still think there is an issue with gdb not checking the debug-file-directory for the ""Separate debug info file"" in the .gnu_debugaltlink section."
1818918,2020-11-13 19:06:51 UTC,"> 7) Execute ""gdb --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core' --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug'""
"
1818918,2020-11-06 19:12:45 UTC,Here's the full strace for the /bin/cat test case.
1818918,2020-11-06 19:14:36 UTC,Oh and using either of '/tmp/dbgsym' or /tmp/dbgsym/usr/lib/debug' for the debug-file-directory works.
1818920,2019-09-24 07:38:54 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1818920,2019-09-24 07:43:52 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu4.19.04.2
1818920,2019-09-24 07:55:04 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.12
1818920,2019-09-18 11:29:12 UTC,Confirmed in disco that gnome-software 3.30.6-2ubuntu4.19.04.2 uses the correct icon.
1818920,2019-09-18 11:41:34 UTC,Confirmed in bionic that gnome-software 3.28.1-0ubuntu4.18.04.12 uses the correct icon.
1818920,2019-09-17 13:49:43 UTC,"Hello Robert, or anyone else affected,"
1818920,2019-09-17 14:06:06 UTC,"Hello Robert, or anyone else affected,"
1818920,2019-06-18 13:10:48 UTC,Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version
1818920,2019-06-10 01:12:34 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu6
1818927,2019-08-02 17:21:56 UTC,Angular edition pushed:
1818927,2019-03-07 14:51:12 UTC,"Template Toolkit has a ""sort"" method for sorting lists. I'm not certain how the ""l()"" function works, but if it returns a string that TT knows how to sort properly, then we might be able to modify the ""interfaces"" array to make it easily sortable by the localized label (array of hashes?), then just sort it before sending it to the ""table"" plugin."
1818927,2019-05-24 08:28:08 UTC,"The alphabetical sorting for non English languages is good idea, however, when I consider it from a practical point of view, it might not be the best solution for every cases due to translations."
1818927,2019-05-24 11:45:37 UTC,+1 for topical grouping of the splash pages.
1818927,2019-05-28 19:03:53 UTC,"I've also thought it could be useful to have an auto-complete search box that takes you to admin pages.  For example, you type ""MARC"" and it lists all the admin pages with MARC in the name (and clicking or selecting one takes you to that page).  (It could contain other menu items, not just admin pages.)  This is similar to the fairly new Microsoft Office ""Tell me what you want to do"" search box on the menu row."
1818927,2019-08-02 16:54:51 UTC,I'm looking at this for the Angular interfaces.  My plan is to sort the links in real time based on the label by default.
1818928,2019-08-14 11:39:14 UTC,There's a degree of tension between too many distinct icons and icons being repurposed.  We've just gone away from an icon for every different purpose in 4.0.
1818929,2019-03-07 00:56:09 UTC,"shim-signed uses kmodsign from the sbsigntool package.  It declares a dependency on sbsigntool, but the dependency is unversioned, and kmodsign was first introduced in xenial in sbsigntool 0.6-0ubuntu10.1."
1818929,2019-03-07 00:58:19 UTC,"The version number is different for trusty, but the dependency needs to be versioned there as well for the same reason."
1818929,2019-04-08 17:39:09 UTC,"Hello Junior, or anyone else affected,"
1818929,2019-04-08 17:40:21 UTC,"Hello Junior, or anyone else affected,"
1818929,2019-04-11 20:43:46 UTC,Verification-done for xenial:
1818929,2019-04-11 21:02:59 UTC,Verification-done trusty:
1818929,2019-04-15 16:24:39 UTC,This bug was fixed in the package shim-signed - 1.33.1~16.04.5
1818929,2019-04-15 16:24:44 UTC,"The verification of the Stable Release Update for shim-signed has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1818929,2019-04-15 16:25:12 UTC,This bug was fixed in the package shim-signed - 1.33.1~14.04.5
1818930,2019-08-14 23:40:52 UTC,"@Michael, nope.  I already tried that as well as giving all of the static text unique mnemonics and changing all of the control and static text IDs to wxID_ANY.  It appears there is bug in wxBitmapComboBox that prevents the control from being selected when the static text mnemonic is pressed.  I will give a try on Linux to see if the behavior is any different."
1818930,2019-08-15 19:10:12 UTC,"I spent over half day trying to figure this out and I think I know what is going on.  If the combobox type wxCB_READONLY and the units static text controls are removed the mnemonics work as expected.  In order to resolve this issue, I had to move all of the edit controls and their associated mnemonic static text controls before all of the read only comboboxes and units static text controls and it seems to work as expected (at least on linux).  This doesn't change the position of the controls in the sizer.  It only changes the order in which objects are added to the sizer which appears to be the correct solution.  I'm guessing there are a lot of other dialogs with broken mnemonic dialog behavior."
1818930,2019-08-15 19:11:27 UTC,"Fixed in revision 92fe201c5bbdcfb57aa5f22a865d3c194f0e0b7d
https://git.launchpad.net/kicad/patch/?id=92fe201c5bbdcfb57aa5f22a865d3c194f0e0b7d"
1818930,2019-08-14 22:28:23 UTC,"@Wayne, dang. Admittedly it was a shot in the dark since macOS doesn't have mnemonics, so I can't reproduce it anyway. Does adding a new mnemonic to the next control (Pin length) help?"
1818930,2019-08-14 13:59:01 UTC,Something like this?
1818930,2019-03-07 11:43:59 UTC,"I think it makes sense to have a convention to reserve ""O"" and ""C"" for OK and Cancel for the sake of consistency. Orientation can use ""R""."
1818930,2019-08-14 21:54:23 UTC,"@Michael, your patch doesn't seem to work on windows.  Alt-R moves the cursor to the ""Pin length"" edit control rather than the ""Orientation"" combobox control.  I suppose it fixes the duplicate mnemonic issue."
1818931,2019-03-07 00:46:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/641528"
1818934,2019-03-07 23:55:04 UTC,*** This is an automated message ***
1818937,2020-12-09 21:16:12 UTC,Same here. Also on macOS host:
1818937,2020-12-16 13:25:00 UTC,"For the Mac Big sur 11.0.1 or 11.1, the HV_ERROR issue was caused by code signing issue.
the com.apple.vm.hypervisor is deprecated and now is com.apple.security.hypervisor"
1818937,2020-12-15 06:25:08 UTC,Same here on macOS 11.0.1 when specifying accel=hvf. Crash report is attached.
1818937,2020-12-09 19:35:03 UTC,I'm getting this error immediately and consistently when trying to boot the Win10 ISO with the following command:
1818937,2020-06-25 00:03:09 UTC,The issue should be fixed in QEMU v5.0+
1818937,2019-12-30 16:41:45 UTC,Are there any updates? Trying to run the IE11 image from Microsoft (based on Windows 8.1) and it is crashing with this error sporadically :-\
1818937,2019-07-30 10:05:39 UTC,"During the inspection of Apple reference, I have noticed that Guest CR0 and CR0 Guest/Host Mask has incorrect value. Apple defines that Guest CR0 is writable only if:
CR0.CD and CR0.NW are unset"
1818937,2019-07-30 09:36:03 UTC,"It's not possible to allocate MSR bitmap in userspace because it requires a physical address to be stored in the VMCS field. However, the bitmap page is already allocated inside kernel part of Hypervisor.framework. The 4k bitmap region is aligned to page boundary. It's worth to continue inspection of the checks (26.2 CHECKS ON VMX CONTROLS AND HOST-STATE AREA)."
1818937,2020-06-24 23:59:54 UTC,I'm not exactly sure what commit improved the situation (either https://git.qemu.org/?p=qemu.git;a=commit;h=e37aa8b0e410 or https://git.qemu.org/?p=qemu.git;a=commit;h=fbafbb6db7742)  but I have noticed that sporadic failures are gone after the series was applied: https://lists.gnu.org/archive/html/qemu-devel/2019-11/msg03977.html
1818937,2019-07-23 12:01:06 UTC,"Hi Roman,"
1818937,2019-07-23 01:03:36 UTC,"The log line I've got is the following:
➜  vms ~/dev/qemu/x86_64-softmmu/qemu-system-x86_64 -accel hvf -m 2G -cdrom ~/Downloads/ubuntu-18.04.2-desktop-amd64.iso -hda ubuntu.qc
ow2
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: hv_vcpu_run failed
qemu-system-x86_64: instruction error:      0x0000000000000007
qemu-system-x86_64: exit reason:            0x0000000000000030
qemu-system-x86_64: exit qualification:     0x0000000000000083
qemu-system-x86_64: pri proc based ctls:    0x0000000095206dfa
qemu-system-x86_64: sec proc based ctls:    0x00000000000000a3
qemu-system-x86_64: eptp:                   0x000000000000003f
qemu-system-x86_64: gpa:                    0x000000007d9ef000
qemu-system-x86_64: gla:                    0xfffffe0000000ec0
qemu-system-x86_64: Error: HV_ERROR"
1818937,2019-07-23 00:54:45 UTC,"For the triage of the issue we need the following VMCS fields:
* instruction error
* exit reason
* exit qualification"
1818937,2019-07-21 22:25:46 UTC,"We can reproduce this problem with Linux guests as well (running 4.15 Ubuntu Xenial and 4.14 Android kernels). Mac models with integrated GPU seem to be more affected according to our testing, and the crash does not always occur, needs multiple tries to be triggered. We would be happy to assist in debugging, once you have a patch that can generate more detailed logs."
1818937,2019-07-19 18:30:55 UTC,I'm looking into the issue... HV_ERROR is a high-level return value and doesn't give enough details about the nature of the error. The error is returned from vmexit handler in AppleHV.kext (which implements kernel part of Hypervisor.framework). Perhaps we should extract more data from the VMCS and print it before aborting the execution.
1818937,2019-04-29 17:40:52 UTC,^This is on version:
1818937,2019-04-29 17:38:23 UTC,I can reproduce this by booting the Windows 10 x64 install ISO with the command line:
1818937,2019-07-28 00:02:40 UTC,"My guess is that RFLAGS.ZF == 1 and one or a few of the checks on VMX controls have failed. So far I have verified the following checks (26-2 and 26-3 in Intel SDM Vol. 3C):
* Reserved bits in Pin-based VM execution controls are set according to associated capabilities MSR
* Reserved bits in Primary Proc-based VM execution controls are set according to associated capabilities MSR
* Reserved bits in Secondary Proc-based VM execution controls are set according to associated capabilities MSR
* CR-3 target count is not greater than 4. (the count is 0)
* Use I/O bitmaps check is not applicable because ""use I/O bitmaps"" VM-execution control is 0.
* Reserved bits in VM-exit controls are set according to associated capabilities MSR
* Reserved bits in VM-entry controls are set according to associated capabilities MSR"
1818938,2020-11-25 15:46:32 UTC,"So, this is an issue that depends on device."
1818938,2019-03-10 13:46:42 UTC,Okay! I just reported it to upstream.
1818938,2019-03-07 14:20:00 UTC,"Thank you for your bug report, could you maybe report that upstream? We don't have any active maintainer for that stack in Ubuntu and upstream is better placed to respond to the issues you are raising"
1818941,2019-05-22 18:42:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1830066, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1818943,2019-07-01 20:08:50 UTC,See similar in openstack-ansible https://review.opendev.org/#/c/668526/
1818960,2019-03-07 21:09:04 UTC,"I think that rule will get added when a prefix-delegated subnet is added to the external interface, or when you add a prefix from a configured address pool.  I don't think modifying that code is exactly correct at first glance."
1818960,2019-03-08 06:52:24 UTC,"Sure, I'll provide that."
1818960,2019-03-15 06:54:59 UTC,Setup without IPv6 : https://pastebin.ubuntu.com/p/Nqr33HQygG/
1818960,2019-03-15 15:00:58 UTC,"The prefix delegation code I mentioned is in _process_pd_iptables_rules(), and it's called when a port with an address scope is added to a router."
1818960,2019-05-15 04:17:33 UTC,[Expired for neutron because there has been no activity for 60 days.]
1818965,2019-03-08 10:34:14 UTC,"Application: kicad
Version: (5.0.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013"
1818965,2019-03-25 08:36:06 UTC,Dock the DRC window much like browsers or spreadsheet programs have a docked search function and let users scroll thru DRC issues.
1818965,2019-06-26 20:16:00 UTC,In 6.0 right-clicking on the DRC list item allows you to roll over the conflicting items and have them brightened (similar to Clarify Selection menu).  This worked on some platforms in 5.1.
1818965,2019-03-08 10:33:56 UTC,"Yeah, I think higlighting the marker and the two objects who are causing the error would be great. I got so many errors in my view that i didn´t realized the new centering when clicking the next list entry."
1818965,2019-04-12 01:34:38 UTC,"OK so that is a bigger project, perhaps for V6 we can think about ways to improve the UX."
1818965,2019-04-12 08:44:50 UTC,Wayne appears to be talking about the ERC dialog (which is not modeless).
1818965,2019-04-12 13:26:48 UTC,"I didn't realize the DRC is now modeless but I do know that the ERC is modal.  I agree with Jeff.  Let's avoid making any more major UI changes to 5.1 and come up with a plan to improve the DRC UI during v6.  What ever UI changes we make, I would like the DRC and ERC UIs to be the same for the sake of consistency."
1818965,2019-03-27 13:44:09 UTC,"@Jon, what you are proposing is going to require a modeless dialog which is a lot more effort.  Once you allow the user to edit the schematic, the information in the dialog may be invalid so you have to sync the information between the two.  I don't see how you can do what you are proposing with a modal or quasi-modal dialog.  I'm fine with this as long as you careful with your implementation."
1818965,2019-03-07 16:47:26 UTC,I think highlighting the drc marker the issue.  I'm guessing leaving the current drc error marker highlighted until another drc error is selected or the dialog is closed (assuming it's hidden modeless dialog) is the desired behavior.
1818965,2019-03-26 16:18:07 UTC,@Wayne what about changing the behavior so that we focus back on the main window on double-click instead of closing the DRC dialog outright?  I also think that closing the window on double-click is not great UX.
1818965,2019-03-07 16:18:30 UTC,I think it already centres.
1818965,2019-03-07 16:15:59 UTC,I'm thinking highlight and center the currently selected marker.  Leave double-click as is.
1818965,2019-03-07 14:57:24 UTC,What bug are we fixing here the highlighting or the double behavior?  The current double click behavior is by design so we need to clarify what exactly it is we are fixing and get some consensus before making any changes.
1818965,2019-03-07 13:42:03 UTC,@Seth - Thank you for the tip !
1818965,2019-03-07 13:21:25 UTC,@Laurent-  Right click on the text to get the items in question.  These will be highlighted.
1818965,2019-03-07 13:20:27 UTC,@Urs-  Please be sure to include your version information like the following.
1818965,2019-03-07 12:30:52 UTC,"A single click pans the PCB and doesn't close the DRC window, but unfortunately the cursor isn't located right on the marker as the double-click does, and if there are several marker in the area, it's not always easy to locate what marker it is. It would be useful to get the marker in question colored differently."
1818965,2019-03-07 16:19:00 UTC,Or maybe unhighlight when closing the dialog?
1818966,2019-05-15 09:18:50 UTC,Proposed fix:
1818966,2019-07-03 17:22:45 UTC,"This MP landed on the released charm but ""--skip"" expects one argument."
1818968,2019-12-16 08:30:24 UTC,This bug has been discussed also here https://github.com/ubuntu/yaru/issues/1243 and resulted in an upstream ticket https://gitlab.gnome.org/GNOME/gtk/issues/1768 since
1818968,2020-04-14 12:57:18 UTC,"the workaround is to use another (widget) theme, with all the issues that'll create.."
1818973,2020-04-08 05:59:37 UTC,"I filed Bug #1871539 to handle the problem where the charm gets stuck in the blocked state, and you cannot get out of it (even with the resume action or any other juju incantation) - due to faults in the flag logic."
1818973,2020-03-09 15:15:50 UTC,"It is also possible to reach ""blocked: Vault health check failed"" instead of ""blocked: Vault service not running"""
1818973,2020-03-10 08:32:18 UTC,"In the case of ""blocked: Vault health check failed"", the vault service is still running and able to recover when MySQL gets back up. In the case of ""blocked: Vault service not running"", it won't recover on its own but systemd has detected the service as failed, so indeed it should be possible to solve the issue by tuning Restart*= on the systemd unit."
1818973,2020-03-09 14:51:46 UTC,This can be reproduced with cs:vault-35 :
1818974,2019-07-24 08:09:28 UTC,"First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/"
1818974,2019-07-11 10:01:02 UTC,"And again, I woke my thinkpad t460p just from standby/suspend to ram and i first saw a black screen, then ""starting bpfilter"", then my user session crashed."
1818974,2019-07-12 07:52:54 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc7/"
1818974,2019-07-13 11:09:00 UTC,Thank you for your help.
1818974,2019-07-17 04:42:16 UTC,"Yes, please test hwe-edge kernel."
1818974,2019-07-17 08:48:42 UTC,"Still getting the issue in 5.2.
Do you think I should still test the Ubuntu HWE 5.0 for 18.04?"
1818974,2019-07-17 09:27:11 UTC,Please compare /sys/kernel/debug/wakeup_sources before and after suspend to see which device wakes the system up.
1818974,2019-07-20 09:10:44 UTC,Done.
1818974,2019-05-23 23:00:56 UTC,"Very weird.
I detached the awake laptop from my docking station, then i worked with it without attached power supply.
I watched something without using my laptop.
My laptop turned into standby.
Then I woke it up and the screen was just black, but the power LED indicated a awake laptop.
Only a forced shutdown by pressing the power button until ended this bug."
1818974,2019-07-22 06:46:36 UTC,Hibernate (S4) is not the same as S3. S4 wakeup is mostly controlled by BIOS.
1818974,2019-07-22 09:19:07 UTC,"Sorry, I think I translated it wrong. The menu entry is named ""Bereitschaft"", which means standby / suspend.
The stuff gets saved into the RAM, not the storage drive/disk."
1818974,2019-07-22 17:36:15 UTC,I think the quickest way is to do a kernel bisection.
1818974,2019-07-22 19:06:46 UTC,"How to do that?
I would need a guide. :)"
1818974,2019-07-22 19:07:56 UTC,"Oh
https://wiki.ubuntu.com/Kernel/KernelBisection
You mean I should install a specific previous version?
Which version do you want to get tested?"
1818974,2019-09-21 08:45:21 UTC,"I'm sorry, that I still had no time to bisect the kernel (job/studies)."
1818974,2019-10-03 10:34:32 UTC,"ERROR: apport (pid 19009) Thu Oct  3 12:03:14 2019: called for pid 1556, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 19009) Thu Oct  3 12:03:14 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 19009) Thu Oct  3 12:03:14 2019: executable: /usr/lib/xorg/Xorg (command line ""/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch"")
ERROR: apport (pid 19009) Thu Oct  3 12:03:14 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 19009) Thu Oct  3 12:03:14 2019: this executable already crashed 2 times, ignoring
ERROR: apport (pid 19155) Thu Oct  3 12:03:14 2019: called for pid 19150, signal 7, core limit 0, dump mode 1
ERROR: apport (pid 19155) Thu Oct  3 12:03:14 2019: Unhandled exception:
Traceback (most recent call last):
  File ""/usr/share/apport/apport"", line 483, in <module>
    exe_mtime = os.stat('/proc/%s/exe' % pid).st_mtime
PermissionError: [Errno 13] Permission denied: '/proc/19150/exe'
ERROR: apport (pid 19155) Thu Oct  3 12:03:14 2019: pid: 19155, uid: 1000, gid: 1000, euid: 0, egid: 0
ERROR: apport (pid 19155) Thu Oct  3 12:03:14 2019: environment: environ({})
ERROR: apport (pid 19153) Thu Oct  3 12:03:14 2019: called for pid 4599, signal 7, core limit 0, dump mode 1
ERROR: apport (pid 19153) Thu Oct  3 12:03:14 2019: Unhandled exception:
Traceback (most recent call last):
  File ""/usr/share/apport/apport"", line 483, in <module>
    exe_mtime = os.stat('/proc/%s/exe' % pid).st_mtime
PermissionError: [Errno 13] Permission denied: '/proc/4599/exe'
ERROR: apport (pid 19153) Thu Oct  3 12:03:14 2019: pid: 19153, uid: 1000, gid: 1000, euid: 0, egid: 0
ERROR: apport (pid 19153) Thu Oct  3 12:03:14 2019: environment: environ({})"
1818974,2019-09-21 08:51:56 UTC,Xorg.log after crash
1818974,2019-09-24 08:16:47 UTC,Maybe error in DRM i915 by intel causes this weird behaviour.
1818974,2019-09-29 11:24:11 UTC,Hoping the dumps are useful
1818974,2019-10-03 10:23:22 UTC,"Now my laptop connected to dockingstation connected to (the monitors and) the usb hdd hub connected to my HDD did go to standby.
I slept the night.
Next day I detached it from the docking station and connected the usb hdd hub with my directly to it before waking it up.
User session died."
1818974,2019-10-03 10:25:22 UTC,"[ 19109.693] (II) NVIDIA(0): Setting mode ""NULL""
[ 19109.707] (EE) modeset(G0): failed to set mode: No such file or directory
[ 19109.707] (EE)
Fatal server error:
[ 19109.707] (EE) EnterVT failed for gpu screen 0
[ 19109.707] (EE)
[ 19109.707] (EE)
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[ 19109.707] (EE) Please also check the log file at ""/var/log/Xorg.0.log"" for additional information.
[ 19109.707] (EE)
[ 19109.731] (EE) Server terminated with error (1). Closing log file."
1818974,2019-10-03 10:30:39 UTC,"Oct  3 12:03:14 deus-ex-machina systemd[1]: Stopped target Suspend.
Oct  3 12:03:14 deus-ex-machina NetworkManager[1342]: <info>  [1570096994.1383] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Oct  3 12:03:14 deus-ex-machina NetworkManager[1342]: <info>  [1570096994.1384] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Oct  3 12:03:14 deus-ex-machina acpid: client connected from 1556[0:0]
Oct  3 12:03:14 deus-ex-machina acpid: 1 client rule loaded
Oct  3 12:03:14 deus-ex-machina upowerd[2964]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3
Oct  3 12:03:14 deus-ex-machina kernel: [19109.240526] usb 2-1: new SuperSpeed Gen 1 USB device number 8 using xhci_hcd
Oct  3 12:03:14 deus-ex-machina kernel: [19109.261148] usb 2-1: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
Oct  3 12:03:14 deus-ex-machina kernel: [19109.261149] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Oct  3 12:03:14 deus-ex-machina kernel: [19109.261150] usb 2-1: Product: ASM1156-PM
Oct  3 12:03:14 deus-ex-machina kernel: [19109.261151] usb 2-1: Manufacturer: ASMT
Oct  3 12:03:14 deus-ex-machina kernel: [19109.261152] usb 2-1: SerialNumber: 00000000000000000000
Oct  3 12:03:14 deus-ex-machina kernel: [19109.265543] scsi host6: uas
Oct  3 12:03:14 deus-ex-machina kernel: [19109.265737] usb 2-4: USB disconnect, device number 6
Oct  3 12:03:14 deus-ex-machina kernel: [19109.265739] usb 2-4.1: USB disconnect, device number 7
Oct  3 12:03:14 deus-ex-machina kernel: [19109.266028] print_req_error: I/O error, dev sdc, sector 0 flags 801
Oct  3 12:03:14 deus-ex-machina kernel: [19109.268614] scsi 6:0:0:0: Direct-Access     ASMT     ASM1156-PM       0    PQ: 0 ANSI: 6
Oct  3 12:03:14 deus-ex-machina kernel: [19109.273083] sd 6:0:0:0: Attached scsi generic sg1 type 0
Oct  3 12:03:14 deus-ex-machina kernel: [19109.278705] sd 6:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
Oct  3 12:03:14 deus-ex-machina kernel: [19109.278707] sd 6:0:0:0: [sdd] 4096-byte physical blocks
Oct  3 12:03:14 deus-ex-machina kernel: [19109.278828] sd 6:0:0:0: [sdd] Write Protect is off
Oct  3 12:03:14 deus-ex-machina kernel: [19109.278829] sd 6:0:0:0: [sdd] Mode Sense: 43 00 00 00
Oct  3 12:03:14 deus-ex-machina kernel: [19109.278988] sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct  3 12:03:14 deus-ex-machina kernel: [19109.280494] sd 6:0:0:0: [sdd] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
Oct  3 12:03:14 deus-ex-machina NetworkManager[1342]: <info>  [1570096994.3234] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Oct  3 12:03:14 deus-ex-machina cinnamon-screen[3238]: cinnamon-screensaver-main.py: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
Oct  3 12:03:14 deus-ex-machina at-spi-bus-launcher[3226]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server "":0""
Oct  3 12:03:14 deus-ex-machina at-spi-bus-launcher[3226]:       after 8633 requests (8633 known pro..."
1818974,2019-10-23 14:25:24 UTC,"Kernel 5.0.0-32-generic
Put in standby on docking station
disconnected
wake up
user session crashed"
1818974,2019-10-25 06:30:00 UTC,"[ 14158.623] (II) NVIDIA(0): Setting mode ""NULL""
[ 14159.837] (EE) modeset(G0): failed to set mode: No such file or directory
[ 14159.837] (EE)
Fatal server error:
[ 14159.837] (EE) EnterVT failed for gpu screen 0
[ 14159.837] (EE)
[ 14159.837] (EE)"
1818974,2019-10-25 06:30:56 UTC,Can you confirm it doesn't happen under 4.15 based kernel?
1818974,2019-10-27 10:35:09 UTC,"Kernel 4.15.0-66-generic
Put in standby on docking station
disconnected
wake up
user session crashed"
1818974,2019-12-01 08:32:43 UTC,5.0.0-36-generic -> Still happening
1818974,2020-01-24 17:51:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818974,2020-03-20 10:17:25 UTC,"5.3.0-42-generic -> still happening.
Put my thinkpad in standby,
disconnect it from the docking station,
woke it up,
user session crashed."
1818974,2020-04-11 10:33:09 UTC,5.3.0-46-generic -> still happening.
1818974,2019-09-21 08:51:38 UTC,Xorg.log before crash
1818974,2019-05-18 08:41:59 UTC,I also now updated to the newest 18.04 HWE 4.18 kernel and disabled all mitigations to speed up my computer.
1818974,2019-04-27 13:32:27 UTC,"I'll switch now form permanently nvidia gtx 940mx to permanently i7-6700hq iGPU.
May take a bit until I can see if the bug happens or not, because it doesn't happen every time.
Luckily or badly it happens not often."
1818974,2019-05-12 13:04:35 UTC,I don't know if it is the same bug.
1818974,2019-03-07 09:09:27 UTC,"My mistake, I know now how to add the files separately without using an archive."
1818974,2019-03-07 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1818974,2019-03-07 09:43:25 UTC,apport information
1818974,2019-03-07 09:43:26 UTC,apport information
1818974,2019-03-07 09:43:28 UTC,apport information
1818974,2019-03-07 09:43:28 UTC,apport information
1818974,2019-03-07 09:43:30 UTC,apport information
1818974,2019-03-07 09:43:31 UTC,apport information
1818974,2019-05-18 08:34:42 UTC,"Sadly my screen was again black and my external monitors in standby.
Something happened while the laptop did go into auto standby this morning, so a forced reboot was needed at 10:24."
1818974,2019-03-07 09:43:33 UTC,apport information
1818974,2019-03-07 09:43:35 UTC,apport information
1818974,2019-03-07 09:43:36 UTC,apport information
1818974,2019-03-07 09:43:37 UTC,apport information
1818974,2019-03-07 09:43:38 UTC,apport information
1818974,2019-03-07 09:43:32 UTC,apport information
1818974,2019-03-07 09:43:40 UTC,apport information
1818974,2019-03-07 09:43:39 UTC,apport information
1818974,2019-04-01 17:57:45 UTC,"Are #31 and #25 enough?
or do you miss something else? :)"
1818974,2019-04-01 05:09:15 UTC,Possible to reproduce the issue and attach dmesg? #30 is hard to read.
1818974,2019-03-31 08:07:46 UTC,"But now it was forever at ""Started Bpfilter"" until I switched to the terminal screen and executed a shutdown."
1818974,2019-03-31 08:06:28 UTC,Happens too with fixed hdd filesystem.
1818974,2019-03-29 10:03:21 UTC,"SMART long offline test was successful.
Everything is fine.
I formatted the ext4 partition.
I assume the corruption came, because I turned of the external HDD hub too early several times."
1818974,2019-04-26 19:08:35 UTC,X crashed after resume. Do you see the issue when i915 is used instead?
1818974,2019-03-22 08:09:11 UTC,"It starts to happen more often.
The symptom is a black screen with only ""Started Bpfilter"", a blinking cursor and a long waiting time, before showing the login screen."
1818974,2019-03-21 08:30:30 UTC,"Now it happened even with my external HDD detached.
The laptop was in standby for 8 hours."
1818974,2019-03-14 12:01:09 UTC,"The /dev/sdb4 has some ext4 file system errors fsk.ext4 can't fix.
Maybe there is a relationship."
1818974,2019-03-14 11:59:48 UTC,"Every time my external HDD is connected via USB the wakeup takes a bit, showing a black screen.
Then I see my login window, and after login I don't see any window I opened. Everything is like a fresh computer restart, except the webdav mount I mounted before."
1818974,2019-03-14 06:26:30 UTC,What is the symptom? From dmesg everything looks fine.
1818974,2019-03-07 09:43:41 UTC,apport information
1818974,2019-03-28 07:25:22 UTC,"Other than offline fsck, it's a good idea to run full SMART test."
1818975,2019-05-24 08:35:49 UTC,"Reviewed:  https://review.opendev.org/660386
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=380adb7271c8de67d343f43b9226efa77eb5adc2
Submitter: Zuul
Branch:    master"
1818975,2019-05-21 13:28:26 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660386"
1818975,2019-03-07 09:31:29 UTC,"My bad, ""sriov-numvfs"" expects a number. So *all* SR-IOV enabled interfaces will get that number (or the maximum number available). Could this be made configurable? Thank you."
1818978,2019-03-07 10:09:21 UTC,Thanks - I've raised this upstream for you
1818978,2019-03-07 10:25:22 UTC,"Thanks, I suscribed it"
1818978,2019-03-07 10:49:07 UTC,Note - there is a workaround as detailed here:
1818978,2019-03-07 11:22:30 UTC,"Good to know! I only searched the web for the syslog-output which doesn't seem to be mentioned in this thread, so I didn't find it. It was hard to believe I am the only one affected. I will try it out, thanks."
1818978,2019-03-10 10:06:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818978,2019-03-10 11:28:20 UTC,This bug was fixed in the package budgie-desktop - 10.5~git20190308-0ubuntu1
1818981,2019-04-18 18:46:48 UTC,not a problem in stein
1818982,2019-07-02 07:54:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818982,2019-07-02 07:55:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818982,2019-03-11 07:15:24 UTC,"Re my previous comment, that fix is not in ubuntu-proposed yet."
1818982,2019-08-28 17:56:43 UTC,"I know it's not directly an Ubuntu problem, but for normal users this regular breakage (that occurs after release as well and also with Ubuntu-packaged extensions, see older posts) is a huge problem. Sometimes you can't even get to the desktop due to broken extensions."
1818982,2019-03-11 01:17:02 UTC,"dash-to-dock, extension-reloader, gsconnect, removable drive menu, activities-configurator, laine, media-player-indicator, cpufreq, and system-monitor all fail on my ubuntu 19.04 system since the last few days."
1818982,2019-03-10 17:28:14 UTC,gnome-shell-extension-dash-to-panel upstream claims to be 3.32-ready.
1818982,2019-07-02 07:58:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1818982,2019-03-11 03:20:39 UTC,It looks like a lot of extensions were broken due to a bug in glib (https://gitlab.gnome.org/GNOME/gjs/issues/227) and that the proposed repo has a new version of gnome-shell that might fix it (see https://ubuntuforums.org/showthread.php?t=2413138&p=13842678#post13842678).
1818982,2019-07-02 17:12:20 UTC,"gnome-shell-extension-workspaces-to-dock version 49-1 from Ubuntu repo loads but is terribly buggy with gnome-shell 3.32, e.g. it frequently covers the right side of windows and sometimes there is more then one panel. Version 50 from the extension website seems to work better at least so far, didn't try for long yet."
1818982,2019-08-28 16:02:02 UTC,"A bunch of extensions are not currently working in 3.34 as well. Would you like me to setup a new bug report to track those as well? Not sure if this bug report is still relevant. I know that pomodoro is working in disco, but I've moved to eaon now."
1818982,2019-08-29 01:29:50 UTC,For tracking 3.34 please use bug 1835706.
1818982,2020-04-14 07:21:35 UTC,"Gnome 3.32 is ""Won't Fix"" because that's in Ubuntu 19.04 which is no longer supported:"
1818985,2019-03-07 10:34:14 UTC,This is the Dockerfile I use to test:
1818985,2019-03-11 10:41:39 UTC,"The Docker only simplifies the setup of a Ubuntu container, which can be doen in any way someone prefers. The actual DB setup at the target was missing from the test steps."
1818985,2019-03-11 12:09:27 UTC,"Sorry, I forgot to mention!
There's a docker-compose file which contain a mysql setup. The README also
contains the commands/steps I use to reproduce it."
1818985,2019-03-11 14:44:07 UTC,"I'm trying to stay away from docker :-)
And [1] doesn't seem to do rocket science anyway."
1818985,2019-03-11 14:57:17 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1818985,2019-04-09 13:45:17 UTC,Sorry for the delay. I've updated the README over at GitHub https://github.com/tskardal/mysigsegv/blob/master/README.md#reproduce
1818985,2019-04-10 14:44:00 UTC,"Thanks, but you're missing some steps."
1818985,2019-04-11 06:42:46 UTC,Thank you for pointing out!
1818985,2019-04-11 09:26:08 UTC,"Thanks. I additionally had to edit /etc/mysql/mysql.conf.d/mysqld.cnf and adjust ""bind-address""."
1818985,2019-06-11 04:17:22 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1818987,2019-04-05 09:45:22 UTC,"Ah, I see what you mean now, sorry I had misunderstood."
1818987,2019-03-22 08:14:11 UTC,"Hi Oliver, thanks for checking."
1818987,2019-03-20 17:43:35 UTC,"Not seeing that here, neither in bionic nor in disco. The changelog and copyright files installed by chromium-codecs-ffmpeg are actual files, not symbolic links:"
1818989,2019-03-08 02:36:22 UTC,"This is a dumb proposal. If you have a broken IPv4 network for example, the answer is to fix IPv4, not turn it off!! Same goes for IPv6. It is the current version of the Internet and we need to use it, not avoid it."
1818989,2019-03-08 08:22:27 UTC,"william, the reality of enterprise networking is that we often cannot fully control what is configured at customer sites and need to have flexibility there. Consider e.g. a network that has both ipv4/6 but by policy filters nodes on ipv6 -- it would be useful there to prevent clients and containers hosted on nodes to ever try using ipv6."
1818989,2019-09-19 14:54:37 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1818997,2019-08-20 21:46:36 UTC,This bug reads like a nice-to-have feature request.
1818997,2019-09-05 01:31:27 UTC,I really think this needs to be parked until https://bugs.launchpad.net/keystone/+bug/968696 is resolved.
1818997,2019-09-05 02:40:11 UTC,"I agree, the third-party product mentioned in the issue description was Contrail with RBAC enabled."
1818998,2019-10-02 06:13:23 UTC,"For Pcb calculator, the issue can be closed."
1818998,2019-10-01 19:51:05 UTC,"Understand. So issue can be closed now, or there is something left?"
1818998,2019-10-01 18:19:45 UTC,"Download latest sources.
Pcb_calculator/attenuators contains *.md help files, coming from their old .html version.
And the result (in corresponding .h files) is easy to translate."
1818998,2019-10-01 17:47:21 UTC,Can you please give me a hint where I can see some example? I found only one in tracks_width_versus_current.cpp from line 444 and it is very similar as my solution.
1818998,2019-10-01 15:42:28 UTC,Using html in translatable help files is not the way to go.
1818998,2019-10-01 14:59:58 UTC,Another approach which exposes only strings which should be translated.
1818998,2019-03-14 02:56:32 UTC,Hmm... This is full HTML.  It should be feasible either by changing the compile setting to built-in or working with the gettext macros.  I think the first option will be easier.
1818998,2019-09-27 18:01:05 UTC,"Hi Jackub,"
1818998,2019-09-27 17:27:46 UTC,"Hi,"
1818998,2019-09-27 16:36:54 UTC,"Hi Jackub,"
1818998,2019-09-27 16:12:58 UTC,The first proposal. It is a question if it is good idea to make formulas translatable.
1818998,2019-09-27 18:33:37 UTC,"Another way is to use simple ""Zin desired input impedance in ohms"". This will not look nice as it can, but it will work. Or if it is possible, then some placeholders can be used."
1819001,2019-06-03 18:47:11 UTC,Closing as per input from the reporter
1819001,2019-03-08 23:02:27 UTC,"Please run the collect tool on the degraded controller and attach the collected logs to the launchpad. Alternatively, tar up the /var/log on the controller."
1819001,2019-03-11 17:37:46 UTC,Assigning to Forrest; he's contacted the reporter to assist with this issue
1819001,2019-03-12 05:06:46 UTC,The system is able to access by TeamViewer. We're trying to find out the right version and its license.
1819001,2019-03-12 11:44:28 UTC,"@Forrest: Do you need more information or othe rhelp with this issue? If yes, feel free to contact me directly. Thanks!"
1819001,2019-04-09 07:35:37 UTC,@Marcel: do you still see the same issue with latest StarlingX ISO image?
1819001,2019-04-09 13:44:08 UTC,@Forrest: We think we nailed it down to an incompatability of the network interfaces and the kernel driver. The configured network ports are disappearing after booting starlingx after a couple of minutes. We have ordered new network cards and will test it next week.
1819001,2019-04-09 14:00:09 UTC,@Marcel: Another alternative would be to attempt the deployment using OVS instead of OVS-DPDK as it has support for a larger variety of NICs.
1819001,2019-05-08 19:45:56 UTC,Any update on this bug? Can this be closed?
1819001,2019-06-03 16:42:56 UTC,@Ghada: Feel free to close this bug.
1819002,2019-03-07 13:18:38 UTC,Suplying sddm.conf from installaiton (not touched)
1819003,2020-07-29 11:14:18 UTC,"Reviewed:  https://review.opendev.org/743688
Committed: https://git.openstack.org/cgit/x/vmware-nsx/commit/?id=f219aae98eb746b72070b0d67a3cf3d9c8ad1357
Submitter: Zuul
Branch:    stable/queens"
1819003,2020-07-29 08:08:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/743688"
1819004,2019-03-07 23:24:43 UTC,"The cause of this issue is that the underlying OS is running two init systems concurrently, and our service abstraction doesn't handle that well."
1819004,2019-03-08 03:49:22 UTC,PR https://github.com/juju/juju/pull/9844
1819004,2019-03-08 03:50:46 UTC,Strategy decided for resolving this issue was to remove all snap functionality from the service/discovery.go machinery and to allow mongo/service.go to handle snaps as a special case itself.
1819009,2019-05-09 04:17:26 UTC,[Expired for lxterminal (Ubuntu) because there has been no activity for 60 days.]
1819009,2019-07-09 04:17:26 UTC,[Expired for lxterminal (Ubuntu) because there has been no activity for 60 days.]
1819009,2019-05-09 21:05:40 UTC,"Hi Walter,"
1819009,2019-05-09 05:36:52 UTC,"Re-opening because I neglected to answer. Sorry, Oliver."
1819009,2019-03-09 13:11:42 UTC,"Sorry, Walter, I forgot to ask!"
1819009,2019-03-08 21:47:44 UTC,"Oliver, did you look at the logs I mentioned?"
1819009,2019-03-08 02:08:47 UTC,"Dear all,"
1819009,2019-03-08 00:16:44 UTC,"I have to wonder if this isn't a graphics issue. I see that Chris is using the same hardware, but I know vendors sometimes swap out graphics cards within the same model. So perhaps the issue is related to some driver change? Syncing up kernels would be a good first start. Then check /var/log/{syslog,Xorg.0.log}."
1819009,2019-03-08 00:15:31 UTC,I am also unable to reproduce on an Atom N455 laptop running 18.04.2 and the 4.15.45 kernel. I did not have a blinking cursor enabled.
1819009,2019-03-07 23:15:24 UTC,I was UNABLE to reproduce this on two tested installed systems
1819009,2019-03-07 20:38:51 UTC,"After I realized this strange behavior I ran the live iso (lubuntu-18.04.1-desktop-amd64.iso) and it was the same. But when I run the live iso within virtualbox it does not happen. Maybe a particular device of my DELL Optiplex 755 is responsible.
In addition to my description, the prompt seems to show up ""earlier"" when other applications are running. It seems that any event, not only a mouse movement or keystroke brings up the prompt again. Maybe the problem is easier to reproduce if you run nothing but a terminal emulator with non blinking cursor. With blinking cursor the blinking stops when the focus is elsewhere. The blinking seems to be event enough to bring the prompt back."
1819009,2019-03-07 19:24:46 UTC,I cannot reproduce this on a fresh install or the live system using the instructions given. Is there something unique about the build on this particular machine?
1819009,2019-03-08 00:52:11 UTC,"I wrote Lubuntu 18.04.1 to thumb-drive (not the latest, but I'd still install with it if I didn't want the HWE kernel)."
1819010,2019-08-20 01:27:47 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1819013,2019-03-18 19:16:51 UTC,@patclash I don't see any fix in the PPA package?
1819013,2019-03-18 19:50:24 UTC,@Jo Shields I don't knowwhat was wrong;
1819013,2019-03-18 21:33:02 UTC,This report is about a problem on ppc64el.
1819013,2019-03-17 16:45:13 UTC,I install 66.0 rc3 version from the beta channel of Mozilla in the opt folder and it run without issue
1819013,2019-03-31 10:01:36 UTC,"I was also affected in 16.04 ppc64el and I fixed downloading IBM adv toolchain for Ubuntu from here
 https://developer.ibm.com/linuxonpower/advance-toolchain/.
Only rte is necessary and I also modify PATH to prepend /opt/at12.0/bin following the ibm istro.
If you want to avoid this hidden dependency you have to uninstall toolchain and rebuild the package.
AT replaces on the fly libstdc++ with a newer one with 3.4.22 in fact:"
1819013,2019-04-01 18:33:52 UTC,Please ignore it is wrong.
1819013,2019-04-02 12:01:42 UTC,"I'm back with a workaround (i know, it is not elegant)"
1819013,2019-03-18 18:35:53 UTC,Issue fixed by the latest PPA : firefox (66.0+build3-0ubuntu0.16.04.2) xenial
1819013,2019-03-19 21:17:22 UTC,"This doesn't appear to be a recent regression, at least. Builds for ppc64el as far back as 63.0.3+build1-0ubuntu0.16.04.1 are affected. 60.0.2+build1-0ubuntu0.16.04.1 isn't."
1819013,2019-03-18 17:40:29 UTC,"builder@xam-power8-1:~$ uname -m
ppc64le
builder@xam-power8-1:~$ objdump -T /usr/lib/firefox/libxul.so | grep GLIBCXX_3.4.22
0000000000000000      DF *UND*	0000000000000000  GLIBCXX_3.4.22 _ZNSt6thread15_M_start_threadESt10unique_ptrINS_6_StateESt14default_deleteIS1_EEPFvvE
0000000000000000      DF *UND*	0000000000000000  GLIBCXX_3.4.22 _ZNSt6thread6_StateD2Ev"
1819013,2019-03-16 10:01:30 UTC,"BTW, teh bug is in X84_64 for me"
1819013,2019-03-18 15:48:52 UTC,"Thanks for the confirmation Pat.
Please note the description of the PPA:"
1819013,2019-03-18 14:48:45 UTC,"Yes , I update firefox from ubuntu-mozilla-security PPA (firefox (66.0+build3-0ubuntu0.16.04.1) xenial);"
1819013,2019-03-18 14:36:17 UTC,I don't have the hardware to test on ppc64el. Can anyone else with such hardware confirm?
1819013,2019-03-16 12:05:30 UTC,This hapend after today xenial update (32bits)
1819013,2019-03-16 12:00:08 UTC,Same issue too :
1819013,2019-03-16 09:57:39 UTC,I have the same issue
1819013,2019-03-16 09:56:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819013,2019-03-18 17:25:11 UTC,"I'm not certain about the fine detail, but looking at the relevant build logs:"
1819015,2019-03-27 02:09:21 UTC,"You can somewhat already do this, but function-lambda-expression give you a form that isn't as simple as you'd like. e.g. after doing (declaim (optimize sb-c:store-source-form))
then you can recover method expressions thusly:"
1819021,2019-11-22 19:15:54 UTC,"Ran please update your current status for this issue.  Which of these tests do you now have working and which are not working?
aodh-test, barbican, ceilometer, glance, neutron, panko"
1819021,2019-08-23 17:46:57 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1819021,2019-11-25 06:34:25 UTC,"Frank, I will retest this issue on Openstack Train, and update the status later."
1819021,2019-07-31 08:58:35 UTC,"aodh:
solved by reversing the order of aodh and gnocchi should solve the issue."
1819021,2019-12-02 07:14:04 UTC,"issue ""Pod \""osh-openstack-glance-test\"" is invalid: spec.containers[0].image: Required value"" was caused by commit https://review.opendev.org/gitweb?p=starlingx/openstack-armada-app.git;a=commit;h=149dcb306dc831d9646b34da3f072f8aeee16211"
1819021,2019-12-11 15:29:04 UTC,Re-tagging this LP to stx.4.0 as changes will not complete in time for stx.3.0
1819021,2020-05-24 21:42:25 UTC,"Marking as low priority - As previously noted, this doesn't cause issues in the starlingx deployments as tests are set to disabled."
1819021,2019-11-28 08:51:48 UTC,"with openstack train (iso built by cengn at 20191115T023000Z):
test pods with name ""osh-openstack-*-test"" could not be created due to ""spec.containers[0].image: Required value"""
1819021,2019-07-30 08:35:39 UTC,"hi Joseph, I removed ""network_segment_range"" in list ""service_plugins"" of secrets neutron-etc and restarted neutron-server* pods but it did not help."
1819021,2019-08-05 08:58:59 UTC,"barbican:
Run ""openstack secret get <secret-href>"" manually failed with errors ""Secret retrieval attempt not allowed - please review your user/project privileges"" after barbican api is ready.
it should be an issue about barbican policy configuration. policy config should be fixed, or we do not support this case."
1819021,2019-07-24 22:09:07 UTC,"aodh:
Aodh test pod requires the gnocchi pod running. Currently, Aodh installs before Gnocchi. In the manifest openstack-telemetry chart_group, reverse the order of aodh and gnocchi should solve the issue."
1819021,2019-03-11 17:28:41 UTC,Assigning to Angie as the first failure appears to be related to aodh
1819021,2019-06-21 12:25:47 UTC,Assigned to Bruce for re-assignment.
1819021,2019-07-01 02:04:49 UTC,"Hi Kristine Bujold, do you know what's the pull time info of the last pass?"
1819021,2019-03-11 17:27:00 UTC,"Marking as release gating; medium priority. Right now, this doesn't cause issues in the starlingx deployments as tests are set to disabled. But, ideally, we want to address this issue and enable basic tests to be run on the services when they are launched."
1819021,2019-07-24 01:15:56 UTC,update logs of failed *-test pods
1819021,2019-07-24 01:20:11 UTC,glance test failed too with codes based on July 15th master branch
1819021,2019-07-29 13:52:13 UTC,Have you looked inside of the neutron logs at all?
1819021,2019-07-02 07:03:33 UTC,this issue can be reproduced based on iso built by cengn 26th June.
1819023,2019-04-04 02:03:59 UTC,2. Actually maybe use this image (higher quality): https://user-images.githubusercontent.com/15329494/44345316-4c2d8700-a493-11e8-8691-6e9d0978fdcc.png
1819023,2019-06-08 04:17:59 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1819023,2019-04-09 01:59:26 UTC,"I wouldn't expect the setting to be remembered across reboots, but it is a setting on the graphics card, so maybe it is remembered?..."
1819023,2019-04-08 12:34:14 UTC,"Alright, got the computer to reboot a second time and it appears as if the
problem is fixed! The gradient on the login screen isn't a perfect
gradient, but that's a different issue."
1819023,2019-04-08 12:30:15 UTC,"Upon doing the first command you suggested, after a reboot, the PC screen
turned on and off a few times and now the screen is just black. I'm
force-rebooting the PC now and seeing if I'll regain the image on my screen."
1819023,2019-04-08 01:50:43 UTC,That's good news.
1819023,2019-04-05 15:15:45 UTC,"Hey Dan,"
1819023,2019-04-04 02:02:34 UTC,"Jeb,"
1819023,2019-04-03 08:05:49 UTC,I thought of that and don't think it's similar.
1819023,2019-04-03 08:52:21 UTC,Those properties are unique to the nouveau kernel driver...
1819023,2019-04-03 08:51:45 UTC,"But before any fix is attempted we should probably verify the problem really is that ""auto"" is defaulting to ""dynamic 2x2"" and that's what looks too flickery."
1819023,2019-04-03 08:27:46 UTC,Thanks for the explanation!
1819023,2019-04-03 07:47:53 UTC,"Daniel, is this similar to LP: #1819968?"
1819023,2019-04-03 02:35:25 UTC,Thanks for the animation.
1819023,2019-04-02 15:40:44 UTC,"Apologies, I forgot to get back.
Please see the attachment included in this response. Note the effect is very minimal when recorded or shot as a moving GIF."
1819023,2019-03-08 02:28:40 UTC,Please do attach a photo or video of the problem ASAP.
1819023,2019-04-03 18:01:42 UTC,"I don't have these problems with Windows on the device, either.
I really hope a fix gets implemented. Thank you."
1819026,2019-03-07 17:22:58 UTC,"OTOH, reviewing how the f_layerci and built asset stuff works I am not sure how this ever worked as by the time we get to the smoke / full test run there is no git repository checked out."
1819026,2019-03-13 15:38:53 UTC,"I get it now, this was added to the gate as we were in the process of convertnig a couple of classic charms from ``Amulet`` to ``Zaza``.  So the feature works for classic charms but not reactive charms."
1819027,2019-03-08 16:59:24 UTC,"Update. If I install from pypi instead of github source, it works"
1819028,2019-03-23 13:39:50 UTC,"I used Ukuu to update to 5.1-rc1, the integrated WiFi still doesn't work"
1819028,2019-03-20 22:04:05 UTC,apport information
1819028,2019-03-20 22:04:19 UTC,apport information
1819028,2019-03-20 22:04:20 UTC,apport information
1819028,2019-03-20 22:04:49 UTC,apport information
1819028,2019-03-20 22:10:11 UTC,apport information
1819028,2019-03-20 22:22:36 UTC,apport information
1819028,2019-03-20 22:22:38 UTC,apport information
1819028,2019-03-24 08:56:13 UTC,"If latest kernel and latest firmware don't work,
Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: network-wireless"
1819028,2019-03-20 22:22:41 UTC,apport information
1819028,2019-03-20 22:22:43 UTC,apport information
1819028,2019-03-20 22:22:45 UTC,apport information
1819028,2019-03-20 22:22:46 UTC,apport information
1819028,2019-03-20 22:03:24 UTC,apport information
1819028,2019-03-20 22:22:48 UTC,apport information
1819028,2019-03-20 22:22:51 UTC,apport information
1819028,2019-03-20 22:22:54 UTC,apport information
1819028,2019-03-20 22:22:56 UTC,apport information
1819028,2019-03-20 22:22:58 UTC,apport information
1819028,2019-03-20 22:22:59 UTC,apport information
1819028,2019-03-20 22:23:02 UTC,apport information
1819028,2019-03-20 22:23:04 UTC,apport information
1819028,2019-03-21 04:51:43 UTC,Please test latest firmware from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
1819028,2019-03-21 18:42:15 UTC,"I'm going to update the Linux kernel to the latest option (4.15.0-46.49)
This will probably stop the Intel wifi from working, this should be a great
way to test the new firmware you sent"
1819028,2019-03-21 20:00:54 UTC,"just tried the firmware after updating, unfortunately doesn't work"
1819028,2019-03-22 07:11:21 UTC,"Please also try latest mainline build:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc1/"
1819028,2019-03-22 08:48:12 UTC,"I'm not sure how Linux Mint will react to that, I'll try it on the Ubuntu
partition."
1819028,2019-03-20 22:22:50 UTC,apport information
1819028,2019-03-20 22:02:59 UTC,apport information
1819028,2019-03-20 21:59:14 UTC,apport information
1819028,2019-03-20 22:01:49 UTC,apport information
1819028,2019-03-10 09:00:03 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819028,2019-03-11 05:44:06 UTC,Have you tried to use the HWE stack [1]?
1819028,2019-03-19 21:03:14 UTC,"Kai-Heng Feng,
I don't believe I've tried that, from the article you attached I'm not sure what going to a previous version would do to help as I have had this issue on several kernels since December 2018. I think the device team needs to modify the Intel driver for AMD B450 integrated WiFi compatibility, whether as an extended pci-e device or something a part of the chipset."
1819028,2019-03-19 21:04:31 UTC,"Sorry for the late replies, I've got a lot on at college and won't be able to give snappy responses."
1819028,2019-03-20 06:24:39 UTC,Please attach dmesg.
1819028,2019-03-20 16:48:18 UTC,"I'm sorry, but what's a 'dmesg'?"
1819028,2019-03-20 21:53:03 UTC,apport information
1819028,2019-03-20 21:53:05 UTC,apport information
1819028,2019-03-20 22:02:58 UTC,apport information
1819028,2019-03-20 21:54:45 UTC,apport information
1819028,2019-03-20 21:54:46 UTC,apport information
1819028,2019-03-20 21:54:47 UTC,apport information
1819028,2019-03-20 21:54:49 UTC,apport information
1819028,2019-03-20 21:53:28 UTC,apport information
1819028,2019-03-20 21:54:52 UTC,apport information
1819028,2019-03-20 21:54:50 UTC,apport information
1819028,2019-03-20 22:01:31 UTC,apport information
1819028,2019-03-20 22:01:30 UTC,apport information
1819028,2019-03-20 22:01:28 UTC,apport information
1819028,2019-03-20 22:01:27 UTC,apport information
1819028,2019-03-20 22:01:44 UTC,apport information
1819028,2019-03-20 22:01:04 UTC,apport information
1819028,2019-03-20 21:55:49 UTC,apport information
1819028,2019-03-20 21:55:47 UTC,apport information
1819028,2019-03-20 21:55:01 UTC,apport information
1819028,2019-03-20 21:55:00 UTC,apport information
1819028,2019-03-20 22:01:08 UTC,apport information
1819033,2019-03-08 06:04:54 UTC,"Odd, in a quick repro I haven't seen any delay."
1819033,2019-03-08 08:37:19 UTC,Thanks you very much for your analysis.
1819033,2019-05-01 12:07:12 UTC,"Thank you for working on this, figuring out the root cause and proposing the fix for 16.04."
1819033,2019-05-15 11:48:03 UTC,"> Otherwise, I'll mark this ""Won't Fix"" for php7.0 and reject from the queue when I next see this again after a couple of weeks.
"
1819034,2019-03-07 20:22:25 UTC,"Because this package has an SRU exception process, I am content to approve a standing FFe for this up to final freeze, provided the SRU exception process is followed for the uploads to devel also."
1819040,2019-03-07 17:47:40 UTC,"I'm not sure about it being windows specific, but I cannot recreate on Linux by following the video"
1819040,2019-03-07 18:07:24 UTC,"To be complete, here's the pcb file. It's been originally done by paulvdh (https://forum.kicad.info/t/seek-review-my-first-design/15510) and I modified it somehow as an exercise."
1819040,2019-03-07 18:43:48 UTC,"Oops, I've made a mistake here.  There is no current single layer select ability.  'U' will happily go through vias as long as there are only two tracks touching it.  My simple test had three.  So this will need to be a wishlist item for another select limit."
1819043,2019-05-08 15:10:47 UTC,This was fixed in commit:
1819045,2020-11-16 13:12:40 UTC,"please try and use /etc/vbox/vbox.cfg for the configuration values!
the fix for vboxweb will come in 6.1.16-dfsg-4"
1819045,2019-07-30 10:31:15 UTC,"Bionic-proposed  repository, now has Virtualbox 5.2.32 in there...
Can you confirm this fixes the above issue over the bionic 5.2.18 version?
If not, it may be possible (if hurry!) to get the community maintainer/updater to fix that issue in proposed update as well."
1819047,2019-03-08 11:19:22 UTC,"I don't think this is configurable: SetAxesColor would probably be the thing to change, but only the GAL ctors call it with hardcoded ""BLUE""."
1819050,2019-03-07 20:47:51 UTC,"As every app, you can exit Shutter completely via File > Quit, the shortcut Ctrl+Q or via the systray context menu. Does this not work for you?"
1819052,2019-03-11 16:27:09 UTC,"Thank you for your bug report, that might be best reported upstream on https://lists.gnu.org/mailman/listinfo/bug-tar"
1819054,2019-03-07 19:39:23 UTC,For reference this is where the charm gets use_tls:
1819054,2019-03-07 23:32:38 UTC,Not configuring use_tls when ldaps is used is intentional actually. use_tls has a confusing naming upstream. What it really means is use_starttls which is mutually exclusive with using ldaps explicitly.
1819054,2019-04-30 16:17:54 UTC,Agree with dmitri so we can close this issue now.
1819054,2020-10-03 04:17:25 UTC,[Expired for OpenStack Keystone LDAP integration because there has been no activity for 60 days.]
1819059,2019-03-08 14:32:58 UTC,"Confirming, and also making a note that when creating the bucket the Publicly Visible ticky does not stick. However, if you edit the bucket after it's already created and check Publicly Visible, it does stick. Also seen in item buckets."
1819059,2019-03-08 18:10:14 UTC,Adding a link to another bug that sounds similar and may/may not have a similar fix: https://bugs.launchpad.net/evergreen/+bug/1778571
1819063,2019-03-26 11:50:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819066,2020-02-29 16:16:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819069,2019-03-07 21:39:19 UTC,Forgot to mention as well:  package(s) created by backportpackage are able to install without issue. Software that depends on the library file : claws-mail - was tested directly and confirmed to function without issue.
1819070,2019-03-07 21:32:49 UTC,"Actually, looking at it closer, I really can't tell what it's sorting by. I just assumed, because the entries that are always at the top start in 2015. But looking closer they're really not in date order either. Anyway, original request still stands, I just can't tell what it's naturally sorting by."
1819070,2019-03-07 21:49:33 UTC,There's currently no default sort on the EDI message grid.  This is likely true of the other Angular admin UI's.
1819074,2019-10-12 21:35:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819074,2019-09-13 14:44:44 UTC,The following 3 bugs:
1819074,2019-09-13 12:13:14 UTC,Looks like this has been fixed in keepalived 2.x (detection of missing vip) - https://github.com/acassen/keepalived/issues/836 - but the patch is embedded with a whole load others that were merged at once so might be hard to backport.
1819074,2019-09-06 07:07:03 UTC,"Medium?  I've had this take a few prod clusters offline at highly inconvenient times, it effectively makes keepalived on 18.04 unfit for purpose.  We've had to build our own keepalived packages to keep things running - I think you need to give this a bit more priority please"
1819074,2019-08-20 15:22:42 UTC,"Fixed in later versions, Rafael will take a HA-POV look at this after FF in Eoan."
1819074,2019-06-19 23:39:03 UTC,"Oh, one other thing that will be necessary to file an SRU for this would be a a series of ""paint by number"" steps to reproduce the issue, and to verify the fix.  For example, something akin to:  https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1810583/comments/12"
1819074,2019-06-18 06:23:02 UTC,"Will anything be done here? This basically breaks keepalived for bionic. I.e, will keepalived >= 2.0.x be available for bionic?"
1819074,2019-06-19 23:34:49 UTC,"Given SRU and backport team policies, having a newer version of keepalived in bionic seems pretty unlikely.  SRU policy favors backports of specific fixes rather than entire package backports, while the backports team generally discourages backports of libraries or services since they can randomly break other software using them."
1819074,2019-03-08 18:37:07 UTC,"After reading the comments for bug 1810583 closer, it is also a symptom of this bug, and keepalived >= 2.0.x would fix it (restore the VIPs)."
1819074,2019-03-08 18:17:30 UTC,Bug 1815101 is a symptom of this bug.
1819074,2019-03-08 08:12:19 UTC,Also https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1810583
1819074,2019-03-08 06:28:08 UTC,Is this a dup to bug 1815101 ?
1819074,2019-03-08 06:26:51 UTC,Adding other components involved.
1819074,2019-03-08 06:09:04 UTC,(or at least related)
1819074,2019-03-08 06:08:00 UTC,"FYI that is about:
https://lists.ubuntu.com/archives/ubuntu-server/2018-October/007761.html
https://lists.ubuntu.com/archives/ubuntu-server/2018-November/007784.html
https://lists.ubuntu.com/archives/ubuntu-server/2019-February/007811.html
https://lists.ubuntu.com/archives/ubuntu-server/2019-March/007819.html"
1819074,2019-04-12 11:44:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819075,2019-07-18 08:27:27 UTC,This bug was fixed in the package kmenuedit - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:24 UTC,This bug was fixed in the package khotkeys - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:21 UTC,This bug was fixed in the package kde-gtk-config - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:15 UTC,This bug was fixed in the package kactivitymanagerd - 5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:12 UTC,This bug was fixed in the package drkonqi - 5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:08 UTC,This bug was fixed in the package bluedevil - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:23:07 UTC,This bug was fixed in the package plasma-pa - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:23:00 UTC,This bug was fixed in the package kwin - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:22:06 UTC,"The verification of the Stable Release Update for breeze has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819075,2019-07-18 08:22:13 UTC,This bug was fixed in the package kdeplasma-addons - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:22:09 UTC,This bug was fixed in the package breeze-gtk - 5.12.8-0ubuntu0.1
1819075,2019-07-18 08:21:58 UTC,This bug was fixed in the package breeze - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:20:11 UTC,Thank you for all the testing and verification! I have the feeling this new stack got enough time and love in -proposed now - let me release it.
1819075,2019-07-17 08:08:26 UTC,Testing done and results:
1819075,2019-07-14 15:10:00 UTC,"A test of the entire proposed stack was successful with a fresh install of Bionic.  Basic application and system functionality verified including KDE Connect, dolphin, kate, FF, System Settings, etc."
1819075,2019-07-18 08:27:30 UTC,This bug was fixed in the package ksshaskpass - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:22:21 UTC,This bug was fixed in the package kscreenlocker - 5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:32 UTC,This bug was fixed in the package ksysguard - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:37:22 UTC,This bug was fixed in the package kde-cli-tools - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:38 UTC,This bug was fixed in the package kwrited - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:43:25 UTC,This bug was fixed in the package plasma-vault - 5.12.8-0ubuntu0.1
1819075,2019-07-18 08:43:05 UTC,This bug was fixed in the package kinfocenter - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:38:15 UTC,This bug was fixed in the package systemsettings - 4:5.12.8-0ubuntu0.1
1819075,2019-07-05 06:51:39 UTC,"The autopkgtests against kscreenlocker and kwin succeeded on retry, as was a case of hiccups on the infra."
1819075,2019-07-18 08:33:22 UTC,This bug was fixed in the package plasma-workspace - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:33:20 UTC,This bug was fixed in the package plasma-sdk - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:33:16 UTC,This bug was fixed in the package plasma-desktop - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:36 UTC,This bug was fixed in the package kwallet-pam - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:33:06 UTC,This bug was fixed in the package libkscreen - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:28:07 UTC,This bug was fixed in the package user-manager - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:28:01 UTC,This bug was fixed in the package powerdevil - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:57 UTC,This bug was fixed in the package plymouth-kcm - 5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:53 UTC,This bug was fixed in the package plasma-nm - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:47 UTC,This bug was fixed in the package oxygen - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:44 UTC,This bug was fixed in the package milou - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:27:42 UTC,This bug was fixed in the package libksysguard - 4:5.12.8-0ubuntu0.1
1819075,2019-07-18 08:33:01 UTC,This bug was fixed in the package kscreen - 4:5.12.8-0ubuntu0.1
1819075,2019-07-04 20:41:41 UTC,"All autopkgtests for the newly accepted kwin (4:5.12.8-0ubuntu0.1) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1819075,2019-07-18 08:27:50 UTC,This bug was fixed in the package plasma-discover - 5.12.8-0ubuntu0.1
1819075,2019-07-04 19:22:17 UTC,"On 04/07/2019 19:35, Łukasz Zemczak wrote:

> I accepted all the packages. A thing to note though: some packages had
> dependency version bumps that made no sense, like for instance plasma-
> workspace had a libkf5sysguard-dev bump to 5.12.8 but the libksysguard
> upload had only translation changes (was it for some features from an
> earlier version?). Same for some of the uploads that had only
> translation changes - for instance khotkeys was a translation-only
> upload but was bumping the plasma-workspace-dev dep.
>
> I'm leaving this note here in case there was something missed in the
> uploads. Would be nice to know if those had any meaning.
"
1819075,2019-07-04 17:31:44 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:29:46 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:28:34 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:26:15 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:25:07 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:22:18 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:17:51 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:33:48 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:11:49 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:04:21 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:01:14 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 16:55:58 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 16:44:02 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 16:36:27 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 12:06:07 UTC,"I will be handling the review of this SRU. This is currently in progress, but since it's quite a lot of packages it might take a bit for me to get through them all."
1819075,2019-06-20 12:41:32 UTC,PPA packages are now in: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/ppa
1819075,2019-07-04 17:06:54 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:38:48 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:15:29 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:44:28 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:41:25 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 19:10:30 UTC,"All autopkgtests for the newly accepted kde-cli-tools (4:5.12.8-0ubuntu0.1) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1819075,2019-07-04 18:35:17 UTC,"I accepted all the packages. A thing to note though: some packages had dependency version bumps that made no sense, like for instance plasma-workspace had a libkf5sysguard-dev bump to 5.12.8 but the libksysguard upload had only translation changes (was it for some features from an earlier version?). Same for some of the uploads that had only translation changes - for instance khotkeys was a translation-only upload but was bumping the plasma-workspace-dev dep."
1819075,2019-07-04 18:32:52 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:31:31 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:28:04 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:23:57 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:18:08 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:16:03 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 20:14:40 UTC,"All autopkgtests for the newly accepted kscreenlocker (5.12.8-0ubuntu0.1) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1819075,2019-07-04 18:10:00 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:08:34 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:04:28 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:01:46 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:59:29 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:52:25 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 17:46:36 UTC,"Hello Rik, or anyone else affected,"
1819075,2019-07-04 18:12:32 UTC,"Hello Rik, or anyone else affected,"
1819076,2019-03-08 07:41:34 UTC,"to disable overcommit:
echo 2 > /proc/sys/vm/overcommit_memory
echo 100 > /proc/sys/vm/overcommit_ratio"
1819076,2019-11-11 18:22:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819076,2019-11-11 19:43:10 UTC,happen on 18.04.3 LTS bionic too
1819076,2019-11-11 19:44:14 UTC,"$ uname -a
Linux 02cor2130 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1819081,2019-03-08 15:31:10 UTC,Confirmed this behavior in EG. 3.1.8 and in 3.2.4.
1819082,2019-08-19 11:05:20 UTC,"This actually turned out to be an issue in the Debian package as well, which will be fixed in the 6.3.0 release later this week."
1819082,2019-08-09 15:42:17 UTC,"This crash has been resolved in the latest 6.3.0 LibreOffice snap, however, OpenCL itself is still not yet supported."
1819082,2019-08-06 10:33:00 UTC,"Apologies for the radio silence on this issue thus far. Over the next 2 weeks we'll be rolling out new versions of LibreOffice across the board. Once that's done, we will come back to this. Thank you for your patience."
1819082,2019-03-20 17:32:27 UTC,"I can reliably observe the problem.
Interestingly, if instead of ""Apply"" I click ""OK"" and select ""Restart Now"", I don't get the crash recovery dialog. Still, OpenCL is not enabled, so I'm guessing something is missing in the snap that makes OpenCL not functional. But I think the crash is only tangentially related: it's probably the code path triggered by ""Apply"" as opposed to ""OK"" that results in the crash."
1819084,2019-03-19 13:57:26 UTC,"Mar  8 01:55:10 ubuntu /install.py: keeping language packs for: en_CA.UTF-8 en_US.UTF-8
Mar  8 01:55:11 ubuntu ubiquity: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Mar  8 01:55:11 ubuntu ubiquity: E: Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable)
Mar  8 01:55:11 ubuntu ubiquity: E: Unable to lock directory /target/var/cache/apt/archives/
Mar  8 01:55:20 ubuntu /install.py: MD5 failure on /target/lib/firmware/intel/ibt-hw-37.7.bseq
Mar  8 01:55:21 ubuntu ubiquity: W: --force-yes is deprecated, use one of the options starting with --allow instead."
1819084,2019-05-19 04:17:57 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1819086,2019-06-27 17:05:06 UTC,"Dash to Dock works for me but pretty much nothing else does, including the apparently ""officially supported"" classic applications menu."
1819086,2019-06-15 16:24:24 UTC,yep
1819086,2019-06-15 15:07:43 UTC,"This report seems surprising to me, I never had problems using the ubuntu branch of the extension nor the upstream one in 19.04 (and I'm using it since the release). A couple of coworkers are using ubuntu 19.04 with a fully functional dock also. I also have used arch and fedora with gnome 3.32 and the extension enabled, no problem at all. Should I assume this has been fixed?"
1819086,2019-03-13 06:40:22 UTC,Looks like this was fixed for gnome-shell-extension-*ubuntu-dock* in upload 64ubuntu5 (March 7).
1819086,2019-03-13 06:20:36 UTC,This issue is affecting a fairly large number of extensions. The cause is an intentional breaking change in GNOME Shell 3.32 to move from Lang.class to ES6 classes.
1819086,2019-03-12 22:20:55 UTC,"Hello,"
1819086,2019-03-12 02:37:21 UTC,"yea I have no idea. seems its a prob with the dynamic dns site not the
software."
1819086,2019-03-12 01:55:25 UTC,"Stephen,"
1819086,2019-03-11 21:49:37 UTC,"Hi Dan,"
1819086,2019-03-11 19:27:11 UTC,Hi Dan.
1819086,2019-03-11 12:56:23 UTC,"Hi Daniel,"
1819086,2019-03-09 08:14:23 UTC,"in my case, ubuntu-19.04, besides dashtodock also activity configurator does not work anymore"
1819086,2019-03-08 03:20:00 UTC,Did you install the Ubuntu package 'gnome-shell-extension-dashtodock' or did you get it from https://extensions.gnome.org/extension/307/dash-to-dock/ (or github)?
1819086,2019-03-08 08:36:36 UTC,I'm guessing this is the result of gnome-shell 3.31 landing in 19.04 updates today.
1819086,2019-03-08 15:54:12 UTC,"Hi,"
1819086,2019-03-11 02:22:11 UTC,"OK, I have generalized this bug to cover any and all extensions (which exist in the Ubuntu archive) that might have stopped working in gnome-shell 3.31/3.32."
1819086,2019-03-08 16:05:38 UTC,"Hi Dan,"
1819086,2019-03-08 20:24:23 UTC,The problem occurred to me too. Dash to Panel and Dash to Dock are not working anymore.
1819086,2019-03-08 23:23:30 UTC,"Hi
Ok, I tested it on my laptop my desktop PC too.
Have a great weekend"
1819086,2019-03-08 15:57:03 UTC,"Hi Again,"
1819110,2019-09-06 08:20:30 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/295
1819111,2019-03-08 19:43:50 UTC,"Hi, Marcin,"
1819113,2019-03-08 07:18:59 UTC,"Sorry I thought I filed it to systemd, interface problem. It's obviously not a dpkg problem..."
1819113,2019-03-12 07:49:39 UTC,This happens if /home is on NFS. Even if it is perfectly healthy.
1819115,2019-03-21 16:59:33 UTC,Yes connection pools could keep those values down.  The activity your noticing is most likely (broadly speaking) part of swift's consistency engines active auditing.
1819115,2019-03-21 16:31:11 UTC,"No, it reduces the resources usage. But I htink that the solution should be maintain open conections, reuse the sockets ... beacuse I don't understand  what is the reason for using so many resources even without vm's or activity in the test bed."
1819115,2019-03-08 16:25:22 UTC,So did dialing back os level connection tracking resolves the issue for you?
1819116,2019-03-08 08:00:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819116,2019-03-12 10:20:41 UTC,Yes this issue can be found on other releases as well (B/C)
1819116,2019-05-21 17:07:58 UTC,affects disco 5.0.0-1007.7-aws amd64 & arm64
1819116,2019-05-21 18:49:09 UTC,affects cosmic 4.18.0-1017.19-aws amd64 & arm64
1819116,2019-05-22 16:34:05 UTC,"affects disco, 5.0.0-1007.7 	linux-azure"
1819116,2019-05-29 00:16:00 UTC,"affects bionic, 4.15.0-1040.42 linux-aws"
1819116,2019-06-03 16:31:29 UTC,affects bionic linux-gke 4.15.0-1033.35
1819116,2019-06-03 21:54:50 UTC,affects linux-oem-osp1 5.0.0-1008.9
1819116,2019-06-12 19:32:54 UTC,"This also affects Eoan 5.2.0-4.5-generic, on bare-metal or the AWS cloud."
1819116,2019-08-08 03:59:50 UTC,"Failed on D-AWS (t3.medium), this failure was not spotted across all instances"
1819116,2019-09-19 08:16:24 UTC,"Seems like the issue can't be reproduced on Disco anymore:
Summary:
passed   18
failed   0
skipped  0
warnings 0
<<<execution_status>>>
initiation_status=""ok""
duration=6 termination_type=exited termination_id=0 corefile=no
cutime=4 cstime=79
<<<test_end>>>
INFO: ltp-pan reported all tests PASS
LTP Version: 20190517"
1819116,2019-11-29 11:15:52 UTC,"This issue happens with NTFS, we have NTFS disabled for the test.
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=e544f2a5eb41dcded0a77ae3a1f6c5c1af204757"
1819116,2019-03-08 10:44:47 UTC,"Need to check if we can reproduce this on older kernel.
This is a new test case that just landed on Feb.21"
1819119,2019-07-13 07:04:54 UTC,This bug was fixed in the package plantuml - 1:1.2018.13+ds-2
1819119,2019-03-08 11:56:40 UTC,Here I have a patch attached.
1819119,2019-03-08 12:25:08 UTC,"The attachment ""patches /usr/bin/plantuml"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1819120,2019-06-03 20:52:53 UTC,https://review.opendev.org/#/c/643857/ fixed this
1819122,2019-03-08 08:07:55 UTC,The method to accomplish the patch is to add 'name' or 'severity' to neutron_acls or delete 'name' or 'severity' from ovn_nb_acls.
1819122,2019-03-08 08:16:21 UTC,"The reason cause this failure is when netwoking-ovn try to compare  the neutron_acls and ovn_nb_acls, the ovn_nb_acls which has 'name' and 'severity' will never be the same with neutron_acls."
1819129,2019-05-30 09:52:10 UTC,This bug was fixed in the package ubuntu-report - 1.3.1
1819129,2019-04-27 21:53:00 UTC,This bug was fixed in the package ubuntu-report - 1.5.0
1819129,2019-05-03 23:20:29 UTC,"Hello Jean-Baptiste, or anyone else affected,"
1819129,2019-05-03 23:22:07 UTC,"Hello Jean-Baptiste, or anyone else affected,"
1819129,2019-05-27 11:44:56 UTC,Using 1.4.2 on a Disco virtualbox image the CPU info are correctly listed indeed
1819129,2019-05-29 15:50:47 UTC,"On bionic the CPU info is included on a 18.04.2 iso booted in virtualbox (1.3.0~18.04, so before that SRU)"
1819129,2019-05-29 15:58:08 UTC,"Well, the update keeps working and has more flexible regexp which should allow things to keep working even if the lscpu behaviour change, so marking confirmed on that basis"
1819129,2019-05-30 08:19:27 UTC,"The verification of the Stable Release Update for ubuntu-report has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819129,2019-05-30 08:29:26 UTC,This bug was fixed in the package ubuntu-report - 1.4.2
1819139,2019-09-16 14:55:41 UTC,Test passed with the latest Disco kernel.
1819141,2019-04-16 09:32:54 UTC,This is an encoding problem ; the clipboard receives double-byte UTF-8 chars for the pound sign but the buffer length copied is the number of single chars.
1819141,2019-09-22 02:55:16 UTC,"I have implemented various improvements to pasaffe and I included your fix.
The results I have published on my ppa:
https://launchpad.net/~ckamphaus/+archive/ubuntu/pasaffe"
1819141,2019-09-22 11:11:05 UTC,"Thanks for reporting this bug! For some reason, it dropped off my radar. I'll review the patch this week."
1819141,2019-09-22 11:11:49 UTC,@ckamphaus: Those look like great improvements...could you please propose a merge request against the Pasaffe tree and I'll include them in a new release?
1819141,2019-09-22 11:12:54 UTC,"Oh! It looks like you did propose a merge, awesome, thanks!"
1819141,2019-09-23 17:33:38 UTC,"Before I merged @adrian-wilkins branch, I confirmed that the bug was real (it was real) and afterwards I double-checked that the bug was fixed (it is now fixed)."
1819141,2019-10-25 11:44:29 UTC,This was fixed in 0.54. Thanks!
1819142,2019-03-11 10:29:38 UTC,"I work a lot on many pcb with LEDs placed in array and in KiCad 5.0 it looks like this:
Typically if the project is complicated, I manually distribute them on special grid, draw minimal repeatable tracks and/or zones, and use array tool only for track and zones."
1819142,2019-03-13 08:03:54 UTC,"One thing else - why not ad a tool in pcbnew such as ""Edit symbol fields"" in eeschema?
Maybe it could be the same tool.."
1819162,2019-03-12 13:27:16 UTC,Thanks for filing this bug in Ubuntu.
1819162,2019-05-12 04:17:28 UTC,[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]
1819167,2020-09-23 22:34:34 UTC,"This is better done as an API microversion bump since we will be changing what the API returns, generating breakage or a very inconsistent behavior. Let's push this for next cycle and ensure consistency across other resources (snapshots, groups, replicas, etc)"
1819167,2019-10-29 16:22:28 UTC,Goutham has the train left :)
1819167,2019-10-30 19:00:12 UTC,Thanks for the reminder Jason :) Targeting this to Ussuri-2
1819170,2019-10-25 14:13:17 UTC,"Reviewed:  https://review.opendev.org/642045
Committed: https://git.openstack.org/cgit/x/cloudbase-init/commit/?id=4c80dd5d60ad05865aa4d2dd842e150e1baa0a1f
Submitter: Zuul
Branch:    master"
1819170,2019-03-08 14:08:55 UTC,"ErrorLog Snapshot, I currently cannot submit a text version of error log, I will update later once it is available."
1819170,2019-03-08 15:02:58 UTC,"Hello,"
1819170,2019-03-11 08:18:06 UTC,"Thanks for your reply, according to our test team, they are using 0.9.11 which is pretty new, and they said that master branch seems to have the same problem."
1819170,2019-03-11 08:19:48 UTC,"Patch proposed:
https://review.openstack.org/#/c/642045/"
1819170,2019-03-11 16:54:51 UTC,"Hi, this is a bit surprising: newer versions of OpenStack support the JSON network config, which is now supported in cloudbase-init, including IPv6."
1819170,2019-03-12 02:48:41 UTC,"Thanks for the reply, we are using Mitaka and cloudbase-init 0.9.11, it will still be good
to fix the issue for old versions, right?"
1819171,2019-03-11 07:45:03 UTC,"My first guess would be that we don't notice that manually provisioned
machines are in valid spaces. Because they are manually provisioned, there
is no Provisioner information about what that subnet actually means. Likely
we could try a best-effort matching ""if it looks like 192.168./16 then just
assume it is the same one as the others claim to be""."
1819171,2019-03-08 16:15:27 UTC,"PS.: for clarification, the ext-net on machine #0 has both ipv4 and ipv6; the interface of the metal actually only has an ipv4 addr bound"
1819171,2019-03-08 16:12:13 UTC,Pasting a redacted version below
1819171,2019-03-08 14:39:06 UTC,Can you also provide the output of juju spaces as we as juju show-machine X where it's the machine you added to the model manually?
1819177,2019-04-01 17:16:11 UTC,"Hi,"
1819178,2019-07-30 01:50:24 UTC,"Reviewed:  https://reviews.mahara.org/9946
Committed: https://git.mahara.org/mahara/mahara/commit/0a896c50c99024996aa5f9c307a038b933bd2840
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1819178,2019-05-02 04:44:53 UTC,"Hi Aurelien,"
1819178,2019-05-02 04:42:14 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9946"
1819181,2019-03-08 16:06:59 UTC,Nothing to it but to do it: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1819181_example_dob / working/user/jboyer/lp1819181_example_dob
1819181,2019-05-24 18:58:09 UTC,"Thanks, Jason.  Merged to 3.2 and above."
1819182,2019-03-18 18:25:30 UTC,"Well, 2.11 is way too old, but it still does reproduce on the latest development head."
1819182,2019-03-08 15:35:43 UTC,"$ ./go-create
#version: 2.11.1
qcow: PASS fmt=qcow auto=qcow exp=qcow [name=my-img.qcow opts=]
qcow2: PASS fmt=qcow2 auto=qcow2 exp=qcow2 [name=my-img.qcow2 opts=]
qed: PASS fmt=qed auto=qed exp=qed [name=my-img.qed opts=]
raw: PASS fmt=raw auto=raw exp=raw [name=my-img.raw opts=]
vdi: PASS fmt=vdi auto=vdi exp=vdi [name=my-img.vdi opts=]
vhdx: PASS fmt=vhdx auto=vhdx exp=vhdx [name=my-img.vhdx opts=]
vmdk: PASS fmt=vmdk auto=vmdk exp=vmdk [name=my-img.vmdk opts=]
vpc: PASS fmt=vpc auto=vpc exp=vpc [name=my-img.vpc opts=]
vpc-fixed: FAIL fmt=vpc auto=raw exp=vpc [name=my-img.vpc-fixed opts=-o subformat=fixed]
vpc-fforce: FAIL fmt=vpc auto=raw exp=vpc [name=my-img.vpc-fforce opts=-o subformat=fixed,force_size]
FAIL [2]"
1819186,2019-03-09 04:25:34 UTC,Could you make a video of how you are doing this?  I might be trying this differently
1819186,2019-03-09 05:37:45 UTC,@sethh i discovered that no net traces ignore keepouts so my guess is that your vias do not have a net assigned while the ones by @halzia have one.
1819186,2019-03-09 13:57:23 UTC,Ok i have a better understanding of the issue now.
1819186,2019-03-09 10:20:28 UTC,"@Rene
""You seem to be allowed to create a trace from the inside of the keepout and end it on the outside. This is at least strange if not a bug."""
1819186,2019-03-09 09:27:38 UTC,You seem to be allowed to create a trace from the inside of the keepout and end it on the outside. This is at least strange if not a bug. (Might need another separate bug report.)
1819186,2019-03-09 10:42:29 UTC,"To me saying that the topside track cannot be finished by pressing ""V"" and connecting immediately to its plane because this means creating a track in the keep out does not seem correct. Obviously extending a track in the keep out zone from the zone should not be allowed and seems to be the case."
1819186,2019-03-09 08:08:32 UTC,"A trivial example.
The B layer is a GND zone with a keep out zone, no tracks, but vias and copper fill allowed.
I draw a track from R1 to the left and try to drop a via to the plane below by pressing ""V"", but not allowed.
Using the via tool on the RH toolbar does work.
Strangely the via tool would not work for me either a few hours ago."
1819186,2019-03-09 05:54:03 UTC,I tested this in both nightly and stable now. It seems i can always add a via with the add via tool with the setup described here. So yes we will need further info from @halzia.
1819186,2019-03-09 05:47:47 UTC,Maybe.  But how do you get a via with a net in there with no track?  Placing free stitching vias works for me
1819186,2019-03-08 16:44:02 UTC,I am unable to recreate this.  Can you test with a nightly build of 5.1 9https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/nightly/)
1819186,2019-03-09 02:45:45 UTC,"I can replicate this on a recent Nightly.
Via placement is permitted and plane fill, but I still cannot place the via."
1819186,2019-03-09 09:25:40 UTC,"As expected you try to place a trace. KiCad does not allow that in a ""no traces"" keepout area."
1819188,2019-03-12 04:29:58 UTC,The issue is with the memlock value.
1819190,2019-05-13 14:24:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819191,2019-03-11 09:50:59 UTC,apport information
1819191,2019-03-12 16:24:19 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0]."
1819191,2019-03-11 09:51:03 UTC,apport information
1819191,2019-03-11 09:51:02 UTC,apport information
1819191,2019-03-11 09:51:01 UTC,apport information
1819191,2019-03-11 09:51:00 UTC,apport information
1819191,2019-03-11 09:50:58 UTC,apport information
1819191,2019-03-11 09:50:52 UTC,apport information
1819191,2019-03-11 09:50:55 UTC,apport information
1819191,2019-03-11 09:50:54 UTC,apport information
1819191,2019-03-11 09:50:53 UTC,apport information
1819191,2019-03-11 09:50:51 UTC,apport information
1819191,2019-03-11 09:50:50 UTC,apport information
1819191,2019-03-11 09:50:49 UTC,apport information
1819191,2019-03-09 07:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819191,2019-03-11 09:50:56 UTC,apport information
1819192,2019-03-08 18:02:06 UTC,apport information
1819192,2019-03-13 06:51:49 UTC,Please find the first -rc kernel between v4.16-rc* and v4.18-rc* that causes this regression in [1].
1819192,2019-03-12 18:05:14 UTC,4.15 (Before update 18.04.2)
1819192,2019-03-12 17:40:17 UTC,What is the kernel version when it's fast?
1819192,2019-03-08 18:02:11 UTC,apport information
1819192,2019-03-08 18:02:02 UTC,apport information
1819192,2019-03-08 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819192,2019-03-08 18:02:00 UTC,apport information
1819192,2019-03-08 18:01:58 UTC,apport information
1819192,2019-03-08 18:01:57 UTC,apport information
1819192,2019-03-08 18:01:55 UTC,apport information
1819192,2019-03-08 18:01:53 UTC,apport information
1819192,2019-03-08 18:01:50 UTC,apport information
1819192,2019-03-08 18:02:01 UTC,apport information
1819192,2019-03-08 18:01:48 UTC,apport information
1819193,2019-03-11 02:30:21 UTC,Maybe related to bug 1713931?
1819193,2019-03-16 13:37:45 UTC,"I am able to make this work by first stopping and then restarting the ""gnome-documents"" process. Search results from GNOME Shell will then be opened in Documents as expected. Unfortunately, after a few searches, Documents will crash and searching from g-s will no longer work."
1819193,2019-03-26 15:22:09 UTC,This is apparently an upstream bug: https://gitlab.gnome.org/GNOME/gnome-documents/issues/12
1819193,2019-03-26 18:51:12 UTC,Related to this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-documents/+bug/1592705
1819195,2019-03-21 06:56:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819196,2019-07-15 18:17:15 UTC,Fixed in stable r19009 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/19009>.
1819196,2019-09-02 14:22:37 UTC,build-base support is now in snapcraft for certain snap types.
1819197,2019-08-05 20:18:02 UTC,I'm testing a local build of the bionic package change linked in this bug and so far so good.
1819197,2019-08-02 22:39:07 UTC,I'm seeing this on 18.04/bionic.  What needs to happen to get it released there?  Thanks.
1819197,2019-03-22 17:56:17 UTC,This bug was fixed in the package libnfsidmap - 0.25-5.1ubuntu1
1819197,2019-03-20 20:29:51 UTC,"I'm trying to wrap my head around the terminology here, maybe you can help me."
1819197,2019-03-20 20:20:29 UTC,"The second hunk has a small mistake:
+	princ_realm = strrchr(princ, ""@"");"
1819197,2019-03-16 00:20:45 UTC,"The attachment ""03-nss.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1819197,2019-03-18 21:16:44 UTC,"Version 0.27, which is a release from Steve apparently (I emailed him asking) doesn't have the second bit in the patch either, just the first. Just looking at the code I can't tell if it's needed or not, depends on what the ""princ"" variable is in the nss_gss_princ_to_ids() function. If it's really just a principal, i.e., <email address hidden>, then the strstr call is ok. It's not clear to me when that is used."
1819197,2019-03-15 20:40:03 UTC,"Sorry, I had a typo on the second patch that applied to strrchr line 279.  I put strrstr instead :("
1819197,2019-03-15 18:02:00 UTC,Oh :/
1819197,2019-03-15 20:16:39 UTC,"Andreas,"
1819197,2019-03-15 19:52:53 UTC,Thanks for testing!
1819197,2019-03-15 19:27:21 UTC,"Thanks, Andreas,"
1819197,2019-03-15 17:08:25 UTC,"I'm sorry, I must have written my previous comment somewhere else, as I don't see it here."
1819197,2019-03-15 16:42:08 UTC,"This appears to be directly related to:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581199"
1819197,2019-03-15 13:42:20 UTC,"Thank you for confirming the bug, it looks like libnfsidmap's code base was
imported into nfs-utils by Redhat on 10/26/2017 by Justin Mitchell, it
already had the line modification inside nss.c at that point."
1819197,2019-03-14 15:16:29 UTC,"Looks like this commit your looking for is rather old since it doesn't show
up for me in the following file on that repo:
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=history;f=support/nfsidmap/nss.c"
1819197,2019-03-14 12:40:07 UTC,I'm having trouble finding the correct upstream for libndsifmap. The URL the packages point at (http://www.citi.umich.edu/projects/nfsv4/linux/) only lists 0.25
1819197,2019-03-15 20:20:11 UTC,The patch attached here works for me and is what was used I believe in your .deb files linked above.
1819197,2019-03-12 20:44:11 UTC,I was able to find a solution to this issue that will require a patch/update to the libnfsidmap to version 0.26.
1819208,2019-04-27 14:58:06 UTC,Thank you for your bug report. I played your audio track in Ubuntu 19.04 (final version) and had the problem as well and reported it to the Gnome developers: https://gitlab.gnome.org/GNOME/gnome-music/issues/281
1819210,2019-06-19 05:06:40 UTC,Fixed in b124599de
1819210,2019-06-10 18:47:46 UTC,"...but of course it's still a problem in 5.1 and I tested it in the wrong place, so this still needs a fix. But any fix does not need to be ported to 6.0."
1819210,2019-06-10 11:39:27 UTC,"This now appears to be working OK. It was probably fixed by the recent removal of all the legacy menus, as AFAICT, the issue was the hotkey was being picked up twice: once by menus and once by the tool action."
1819210,2019-05-12 16:25:05 UTC,@John:
1819210,2019-05-12 14:56:19 UTC,Related Ctrl+numbers or symbols: https://bugs.launchpad.net/kicad/+bug/1800720
1819210,2019-05-12 14:32:23 UTC,"Also, any Ctrl-<key> combo seems to not work for this action (eg Ctrl-K, Ctrl-7, Ctrl-`)."
1819210,2019-05-12 14:17:23 UTC,"So for me, when Ctrl-H is the hotkey, the function PCBNEW_CONTROL::HighContrastMode is actually hit twice for a single keypress, toggling the mode on and off again immediately."
1819210,2019-04-07 16:38:34 UTC,Simple press H and all. It works for me
1819210,2019-03-09 05:58:57 UTC,"Ctrl+H seems to start the file browser with help by default.
This is not in the list of hotkeys so maybe there is a conflict generated when changing something else to this key combination."
1819210,2019-03-08 19:58:42 UTC,Ctrl+H works fine on windows.  This may be specific to linux.
1819210,2019-05-12 15:42:29 UTC,"@Michael: That looks related but doesn't sound like the same symptom. This is on Linux, and the hotkey is firing twice. Because it's a toggle action, the net effect is nothing happens."
1819216,2019-03-08 20:31:43 UTC,"I was going to duplicate this against bug 1811235 since it's definitely related but sort of a different issue. In this case you have allow_resize_to_same_host=True (default in devstack but not nova) and two nodes. The scheduler picked the host that the instance is on for whatever reason, and then if you're not using the vcenter driver (you're using libvirt by default), you hit this in the compute and it blows up:"
1819216,2019-03-08 20:35:03 UTC,The change I'm referencing in comment 1 item 2 is this: https://review.openstack.org/#/c/538498/
1819216,2019-03-08 20:41:44 UTC,"Note that this is also extremely latent behavior, not a regression as far as I know."
1819216,2019-06-20 14:59:41 UTC,Here is an os-traits patch to add a compute capability trait for a potential fix mentioned in option 2 in comment 1:
1819218,2020-03-22 16:04:15 UTC,"@Gabriel José Dias Pinto (docmine7)
What is your Ubuntu MATE version?
Do you still have problem?"
1819218,2020-03-24 16:00:38 UTC,"What is your Ubuntu MATE version?
18.10
Do you still have problem?
No"
1819218,2020-09-11 04:17:15 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1819219,2019-11-20 04:17:26 UTC,[Expired for juju because there has been no activity for 60 days.]
1819219,2019-03-11 07:47:32 UTC,"Isn't that a case of needing better default images if you want to bootstrap
with ""enable-os-update=false"" ? We have that flag so that if you *know*
that your Apt cache information is up to date, you can ask us to skip that
step. If that isn't the case, then you shouldn't be setting the flag to
false."
1819219,2019-09-20 08:46:45 UTC,"If I try to bootstrap with ""enable-os-update-refresh=false"" I end up with errors like this:
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/c/ceph/librados2_12.2.12-0ubuntu0.18.04.1_amd64.deb  404  Not Found [IP: 91.189.88.24 80]"
1819219,2019-09-20 10:08:53 UTC,"What is odd is that 91.189.88.24 is still listed as one of the IP addresses that resolve for 'archive.ubuntu.com'. And I can hit that URL, and see a website. (Though I'm currently at a canonical conference which ends up redirecting archive.ubuntu.com to archive.conference to achieve local downloads of archive.)"
1819219,2019-09-19 10:07:51 UTC,"I feel like this is functionally ""images being published have incomplete archive details"".
It is likely we can only ""juju bootstrap --config enable-os-upgrade=false"" which is actually a setting I use in LXD.
I don't think there is anything *juju* can do about stale images."
1819226,2019-03-08 21:42:08 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/642164"
1819226,2019-03-11 23:43:03 UTC,"Reviewed:  https://review.openstack.org/642164
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=736a6aa161711e8ee31c0e0ab385ae59aa9cb026
Submitter: Zuul
Branch:    master"
1819227,2019-03-10 14:31:47 UTC,One option here is to ask in #ubuntu-release for this test failure to be ignored.
1819227,2020-10-02 16:25:41 UTC,the autopkgtests pass on armhf in recent releases.
1819227,2020-10-11 08:54:31 UTC,"It's _mostly_ fixed, but not completely: two variants of varmax
test_bse_oim, and test_pickle_fit_sarimax, still fail."
1819228,2019-03-21 14:31:56 UTC,This was fixed.
1819230,2019-03-08 21:36:56 UTC,"I've currently worked around this issue, which is more common when retracing crashes from the development release of Ubuntu, by disabling -proposed in the sources.list file for the retracers. The logic being that people shouldn't be using -proposed from the development release anyway as the packages have not migrated possibly due to failures in automatic testing."
1819232,2019-03-08 22:22:33 UTC,Related to the bug 1773450
1819233,2020-05-20 23:36:51 UTC,"I think I found the filtering bug.  If you have an open list of values, then click on the caret ^ button to close the list it all works fine.  However, if you close the list by clicking on the text input box, the list closes but filtering stops working properly.  I fixed this bug.  Also, it no longer shows console errors when values like [ are typed.  It's no longer case sensitive.  Typing ""t"" will match with ""Tuesday"", for example.  Branch here:"
1819233,2020-09-11 22:08:31 UTC,This works for me!
1819236,2020-02-21 16:49:54 UTC,Thanks Jane and Ruth.  Merged to 3.4 and master.
1819236,2019-03-08 22:51:26 UTC,"The Keyword search doesn't make much sense when combined with the ""Matches Exactly"" operator either."
1819236,2019-09-19 20:16:26 UTC,Fixes pushed:
1819236,2019-04-02 20:59:42 UTC,"Agreed, Jane.  Note the OPAC/TPAC has the same options on the advanced search page."
1819236,2020-02-19 14:18:52 UTC,"I have tested this code and consent to signing off on it with my name, rfrasur, and my email address, <email address hidden>."
1819238,2019-03-25 21:20:11 UTC,"Hi Eva,"
1819238,2019-05-24 17:07:12 UTC,I confirm the bug still appears in Evergreen 3.3.
1819238,2019-09-13 14:34:09 UTC,"Confirmed in 3.3.2
Note: there is certainly possibility to set the width, background color etc., as suggested by Meg, to provide that the information can be read (we solved the problem this way the library) but it is only a partial solution. All parts of the catalog should definitely be responsive by default (especially the one the user encounters first)."
1819238,2019-09-13 21:25:18 UTC,I agree with Eva that a default solution-- rather than a workaround-- would be preferable.
1819238,2019-09-16 06:25:42 UTC,This bug still appears in 3.3.2.
1819240,2019-05-19 04:18:01 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1819240,2019-03-12 00:28:19 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1819240,2019-03-18 07:56:13 UTC,It sounds like you might be having Internet problems. Are you having any problems with a particular app or browser?
1819240,2019-03-19 16:45:37 UTC, No sir. Seems to be running better. Thank you.
1819243,2019-03-09 02:19:49 UTC,more info
1819243,2019-12-20 10:10:36 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.opendev.org/641929"
1819245,2019-04-05 20:05:12 UTC,I just tried using '~/' in the Configure Paths dialog and it worked fine for me. Does this not achieve what you need?
1819245,2019-06-05 04:17:28 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1819249,2019-03-10 15:09:25 UTC,I would also add that eeshcema does not seem to implement the shift arrow keys to pan feature. As the controls are similar between eeschema and pcb_new I'm guessing that was an oversight. Also it would be nice to add it to eeschema and allow changing the hotkey bindings.
1819249,2019-03-21 19:49:47 UTC,KiCad 5.1.0 now implements the shift arrow key to pan in eeschema. I'm guessing this came along automatically when the rendering engine changed to the same one used by pcb_new.
1819249,2019-06-26 20:56:01 UTC,"Fixed in revision 7099614041f9492ef92409b1cf02ad186f66397c
https://git.launchpad.net/kicad/patch/?id=7099614041f9492ef92409b1cf02ad186f66397c"
1819250,2019-07-05 13:48:27 UTC,"Fixed in revision 867585c1f20f88bcb42003320db47fe961a95d49
https://git.launchpad.net/kicad/patch/?id=867585c1f20f88bcb42003320db47fe961a95d49"
1819250,2019-04-08 23:53:34 UTC,"@Tom, any thoughts on comment #5?"
1819250,2019-04-08 11:26:02 UTC,"Anton i have no idea how your comment applies to this report. We are not talking about pins here but about traces. Keepout for traces should not allow any traces. Not even ""no-net"" traces. (Such a keepout is typically used where no copper is allowed at all. If i want such a trace placed i can still select ""allow DRC violations"")"
1819250,2019-03-09 05:53:15 UTC,I also tested this in 5.0.2. Same behavior.
1819250,2019-03-09 14:04:57 UTC,Sorry about the video being corrupted. (I only tested it in vlc and that one did not complain. But even youtube seems to complain when i try to upload it there.)
1819250,2019-03-09 11:24:44 UTC,"I get a ""corrupt file"" message when trying to play that screen cast."
1819250,2019-04-07 16:27:17 UTC,Truly unconnected pins are free to pass through the fill or ban cast zones. Make them non-intersecting with all the elements on the PCB.
1819250,2019-03-09 12:18:18 UTC,"@Tom, this can be fixed by setting the keepout zone to net -1 in PNS_KICAD_IFACE::syncZone(), but I'm not sure if that's the ""right"" fix."
1819250,2019-03-09 12:04:58 UTC,"[OT]
@Jeff FWIW, I get the same ""corrupt file"" error, but after saving the file, I can play it with VLC flawlessly.
[/OT]"
1819253,2019-03-09 09:01:10 UTC,"Hi,
In the top of the screen you have a circle with a point in the middle. Tap
1 time on it and it will recenter the route.
Best regards."
1819255,2019-03-10 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819255,2019-03-11 05:32:57 UTC,I'd start from removing all additional kernel parameters.
1819255,2019-03-11 15:15:20 UTC,apport information
1819255,2019-03-11 15:15:22 UTC,apport information
1819255,2019-03-14 06:07:20 UTC,Does this issue happen under an Ubuntu kernel without all acpi* kernel parameters?
1819267,2020-07-22 20:47:23 UTC,This has been released.
1819269,2019-03-10 11:16:05 UTC,Not knowing the distribution and its version is a drawback. Assuming it is something recent:
1819269,2019-03-09 23:42:13 UTC,Wireless to a laptop on a network.
1819269,2019-03-09 19:51:01 UTC,"operating system is linxus on a USB drive, and the printer is hp deskjet
3510 that will not work on the drivers for Windows. I downloaded hplip
drivers 3.16.7.run and it didn't work."
1819269,2019-03-09 17:28:54 UTC,"Hello Jacqueline,"
1819269,2019-03-09 23:16:23 UTC,"We are, I think, not understanding each other. ""linxus"" doesn't make sense to me."
1819278,2019-03-09 17:47:33 UTC,That is indeed an interesting bug.  We will have to disable changing sheets when copying objects.  This would wreak havoc until we implement undo/redo across sheets.
1819278,2019-05-29 04:21:13 UTC,"I pushed a fix for the 5.1 branch here.  6 is sufficiently diverged that it needs a different fix, so I'm resetting this status and the milestone."
1819278,2019-06-14 15:55:39 UTC,"Fixed in revision 83ee51370c431fc33535137e8dff615a6819edb4
https://git.launchpad.net/kicad/patch/?id=83ee51370c431fc33535137e8dff615a6819edb4"
1819280,2019-03-11 08:06:03 UTC,"I forgot. I have a second laptop, also running Kubuntu 18.04, fresh installed. On this machine the exact same error occurs."
1819280,2019-11-19 13:54:06 UTC,Since then I really needed to use my scanners .. so I migrated my laptops to manjaro. bye Ubuntu
1819282,2019-03-09 18:30:05 UTC,This change was made by a bot.
1819282,2019-03-10 16:04:06 UTC,"The BIOS of your machine does not support S3 and so linux just does what it's been told:
[    0.345650] ACPI: (supports S0 S4 S5)"
1819283,2019-03-10 13:54:18 UTC,svg2shenzen (or even svg2mod) might be better options to interface between inkscape and kicad: https://github.com/badgeek/svg2shenzhen
1819283,2019-03-09 19:11:59 UTC,Filed bug with inkscape https://gitlab.com/inkscape/inbox/issues/204
1819283,2019-03-09 18:45:46 UTC,I just opened the included dxf file with DraftSight and the width of the outline is indeed 3.456 so the issue appears to be with the dxf file created with Inkscape.  This makes sense as 88/25.4=3.456.
1819283,2019-03-09 19:05:07 UTC,Seems like somewhere along the conversion inches and millimeters are mixed up. Saving the inkscape document in 88 x 55 inches and opening it in pcbnew will give me the size in mm.
1819283,2019-03-09 18:29:04 UTC,R12 DXF file made in inkscape with the shape to fit inside an altoids mints can. Dimensions shown in inkscape are 88.388 mm x 55.388 mm
1819284,2019-05-17 02:36:58 UTC,"Reviewed:  https://review.opendev.org/653899
Committed: https://git.openstack.org/cgit/openstack/rally-openstack/commit/?id=2da73584fdb2a77ebf6a35a3fe969f42924c3a2d
Submitter: Zuul
Branch:    master"
1819284,2019-05-29 17:49:27 UTC,This issue was fixed in the openstack/rally-openstack 1.5.0 release.
1819285,2020-04-06 21:52:32 UTC,"Reviewed:  https://review.opendev.org/717759
Committed: https://git.openstack.org/cgit/openstack/rally-openstack/commit/?id=6363976229966b726d1fb05f75e1b37a61d684f4
Submitter: Zuul
Branch:    master"
1819287,2019-03-09 20:15:54 UTC,"My understanding is that snap manifests are currently in use by cloud images and layered images, of which ubuntu desktop is neither yet."
1819287,2019-03-09 20:32:48 UTC,"No, since this was landed during the disco development cycle, I can't prove that it ever worked on non-layered / non-cloud images."
1819287,2019-03-11 10:48:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819287,2019-03-11 17:24:02 UTC,"The snaps were never published in the manifest in ""flat"" images: https://forum.snapcraft.io/t/no-more-preinstalled-snap-on-ubuntu-19-04/10339/7.
However, adding them is trivial and I can handle it."
1819289,2020-02-10 17:21:54 UTC,I just did an install of Windows 95 in 4.2 and it installs and runs out of the box with -accel tcg. Thanks!!
1819289,2019-08-22 01:14:16 UTC,Here is the exact working command line I used for Windows 95C (OSR2.5):
1819289,2019-08-22 00:02:18 UTC,"After hours bisecting various QEMU/SeaBIOS combinations, Brad figured out a new commit:"
1819289,2019-08-21 13:48:00 UTC,"> cd1bfd5ef336166b275a09dc9842542bf5e63ae3 is the first bad commit
"
1819289,2019-08-21 12:53:12 UTC,"I tried reverting that commit on top of master but it did not help, so I'm guessing it broke yet again (differently) somewhere else. I'll try reverting cd1bfd5 on top of the very next commit and bisect from there to master, and see where that takes me."
1819289,2019-08-21 03:42:04 UTC,"Just finished a bisect between cfcca36 (working) and current master (not working), here is the result:"
1819289,2019-08-20 21:43:48 UTC,"So it looks like even though that commit fixed it, it seems to break again (differently) in 3.0.0, so I'll need to do another bisect between cfcca36 and v3.0.0 then I guess. And keep working my way up to master as well."
1819289,2019-08-20 16:45:32 UTC,"Hopefully third time's the charm. I ran yet another bisect, between 2.5.0 (working) and 2.11.0 (not working), this time reinstalling the entire OS from scratch with a blank disk every single time. Results:"
1819289,2019-08-20 16:55:56 UTC,If your bisect hit e3af7c788b73a6495 can you try it with cfcca361d77142f25f applied on top? That commit fixed a bug in e3af7c788b73a6495 which may be throwing off your bisection results.
1819289,2019-08-20 09:08:07 UTC,"Yep, these types of bugs don't necessarily bisect cleanly if they're todo with code layout or dirty memory.
Still, it's good to keep a note of the earliest patches that you find a failure on - because then we know it must be somewhere before that."
1819289,2019-08-19 18:20:16 UTC,"I am not using anything related to migration, just launching with a simple flat qcow2 file, no snapshots, backing stores or anything like that."
1819289,2019-08-19 17:55:50 UTC,"On 8/19/19 7:26 PM, Brad Parker wrote:

> Whoops, 3.11.0 does not exist. Went back and did a full bisect. 3.0.0
> works fine, and the breakage starts before 3.0.1 and 3.1.0 was released,
> specifically, with commit 05306935b1ae49107c2dc2f301574dd6c29b6838.
"
1819289,2019-08-19 17:26:15 UTC,"Whoops, 3.11.0 does not exist. Went back and did a full bisect. 3.0.0 works fine, and the breakage starts before 3.0.1 and 3.1.0 was released, specifically, with commit 05306935b1ae49107c2dc2f301574dd6c29b6838."
1819289,2019-08-17 21:27:54 UTC,"I was able to get both running on 3.11.0, but something broke again by the time I re-tested on 4.0.0. 98 seems to work on 4.0 at least, but 95 just reboots infinitely after trying to boot from HDD after the initial setup. I tried searching their mailing list and asking around but nobody seems interested in fixing it."
1819289,2019-08-20 21:05:02 UTC,"e3af7c788b73a6495 was indeed one of the bad commits I tested during the bisect. If I apply cfcca361d77142f25f on top of it, Windows starts up normally instead of giving me a BSOD on bootup."
1819289,2019-08-20 00:21:11 UTC,"Just FYI that was the second bisect I had to do, the first time it produced an even more unrelated commit, so I assumed I must have done something wrong... apparently that is still the case. After trying the ""working"" commit outside of the Docker container, it now does not work... so I'm at a loss as to how to reliably bisect I guess. Never had any issues with other projects doing it though."
1819291,2019-05-20 12:17:15 UTC,"Reviewed:  https://review.opendev.org/660054
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=7497b32017b7c8bb4a3bbbf5000befdbe1d67b69
Submitter: Zuul
Branch:    master"
1819291,2019-05-20 09:02:03 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660054"
1819295,2019-03-11 20:22:41 UTC,Don't worry about answering; its's not that important to me and apparently you have no interest in responding.
1819295,2019-03-10 12:02:36 UTC,Possibly the same origin as Debian Bug#825383
1819295,2019-03-12 10:36:32 UTC,"I have installed a former version via Ubuntu. Package repos.
I understand some, disappointment from your tone. Bare in mind I am not
paid to make test of hplip that could be automated at HP. This issue caused
me already few hours of time loss so give me a bit of time ;)"
1819298,2019-03-27 03:55:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819298,2020-04-11 13:03:26 UTC,Affects Ubuntu 19.10 too.
1819301,2019-03-11 23:49:02 UTC,"Also, pcbnew hangs even when it is started outside Kicad environment, i.e. double clicking on the pcbnew icon in the kicad program directory."
1819301,2019-03-12 04:51:32 UTC,"OK, retested it, taking the known failing configuration file and remove the canvas_type=1. So, I have another data point. Fist some background on my computer setup."
1819301,2019-03-12 03:33:01 UTC,"OK, but the uploaded configuration doesn't have canvas_type=1.  It has canvas_type=2 on line 179."
1819301,2019-03-12 03:15:45 UTC,"@sethh That is correct. pcbnew hangs with the uploaded configuration. Remove the canvas_type=1, pcbnew starts fine."
1819301,2019-03-12 02:57:07 UTC,"I just re-read your comment in #10.  Are you saying that the configuration file you uploaded in #10 had canvas_type=1 as the first line and then you deleted it?  Before you deleted that line it didn't work and after you deleted it, it did work?"
1819301,2019-03-12 01:47:12 UTC,"I select the accelerated canvas by going to Preferences menu, then selecting the Modern Toolset (Accelerated) F11. Everything seems to work fine. I shutdown and restart pcbnew & shutdown & restart all of Kicad. After every restart, pcbnew starts fine."
1819301,2019-03-11 23:48:05 UTC,"Looks like Rene's suggestion is the correct one.  @Grant, does pcbnew lock up again when you select ""Accelerated Canvas"" in pcbnew?"
1819301,2019-05-12 04:17:25 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1819301,2019-03-11 23:15:25 UTC,"@Seth, you are probably right about the board file being malformed.  It would be nice if we could duplicate this one."
1819301,2019-03-11 19:54:14 UTC,Thanks JP and Wayne.  The malformed board file seems possible but then I don't understand why removing the configuration changes the behavior.
1819301,2019-03-11 19:47:11 UTC,No problems here for me either on windows 10 pro.  I even manually changed the path separator in my pcbnew config file and tried running pcbnew in stand alone mode with out any issues.  Could it possible be a malformed board file?
1819301,2019-03-11 19:31:23 UTC,"Filenames (in filexx=... in config) use sometimes / and sometimes \\ as dir separator, but it does not create issues on my W7 32 bits install."
1819301,2019-03-11 19:05:24 UTC,I assume that this us your configuration directory before you regenerated it.  Is that correct?
1819301,2019-03-10 18:03:25 UTC,"Update: Thanks to Rene's suggestion, I was able to get pcbnew to startup by removing the configuration files and having Kicad regenerate them. I've included the configuration directory as an attachment."
1819301,2019-03-10 17:57:16 UTC,"@Rene-  Definitely a possibility but now that we are using GAL for eeschema and op says they tried the nightlies, I am inclined to suspect network drive or AV."
1819301,2019-03-10 13:58:14 UTC,Might also be graphics driver related as pcb_new might be setup to use hardware acceleration. (So any change to graphics drivers or even a windows update might interfere with kicad that way.)
1819301,2019-03-10 03:37:50 UTC,It sounds like something changed in your setup.  There are a few things that can cause issues when pcbnew loads.  In no particular order (and not exclusive) the are:
1819301,2019-03-11 23:26:29 UTC,"Everyone, Thanks for your time and attention."
1819304,2019-09-23 14:30:26 UTC,"Alternative approach would be to allow multiple project, schematic and PCB document windows open at once.  I frequently find myself switching between projects and it would be a huge improvement to be able to keep multiple projects open."
1819305,2019-04-17 10:32:53 UTC,"Hello,
it looks like this is a fresh install,
does it work with the updated kernel on Bionic? (4.15.0-47, you can upgrade your system with the software updater)
Thanks."
1819305,2019-06-17 04:17:35 UTC,[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.]
1819318,2019-03-24 15:50:19 UTC,"Applies to Fedora as well, which doesn't have snapd+core installed in the first place."
1819318,2019-03-25 11:56:13 UTC,This is trivial to reproduce on a machine that doesn't have core installed:
1819318,2019-04-23 09:18:00 UTC,"I've seen this reported multiple times over the weekend. Seems Lubuntu and Pop!_OS! don't ship any snaps by default (although Lubuntu ships snapd) and as such, anyone who installs a core18 snap _first_ will have a bad experience."
1819318,2019-04-23 09:32:26 UTC,"Long time ago we have explored the ability to associate interfaces with a virtual snap called ""system"" but that idea was declined. As such all snaps must install snapd snap (which is currently not available as a stable feature) or install the core snap."
1819318,2019-04-25 11:13:38 UTC,I created a PR for this https://github.com/snapcore/snapd/pull/6778
1819318,2019-05-28 16:41:35 UTC,"Is this fix also going to be released in Xenial? Newer versions of the grafana snap (still in edge) use core18, and I also hit this bug on fresh installs (socket error: permission denied). Installing core snap fixed the problem."
1819318,2019-06-12 08:54:34 UTC,"The fix is in ""-proposed"" now and will soon land in -updates."
1819318,2019-03-24 14:28:18 UTC,"The applies to a Ubuntu Server instance on a VPS like DigitalOcean or Scaleway, where no snap is preinstalled. So installing any snap that has `base: core18` set doesn't work."
1819319,2019-04-24 22:50:51 UTC,"In the log, both ""Ziggy Marley""-files didn't load on D&D"
1819319,2019-06-14 20:08:47 UTC,I'm now on mixxx-2.3.0-alpha-pre-master-git6841-release-x64 and drag and drop from library to players still doesn't work.
1819319,2020-05-09 08:39:34 UTC,I think this is fixed in 2.3 alpha by upgrading the Qt Libraries
1819319,2019-11-01 22:19:50 UTC,Now on mixxx-2.3.0-alpha-pre-master-git6978-release-x64
1819319,2019-11-02 10:22:47 UTC,"> In the log, both ""Ziggy Marley""-files didn't load on D&D
"
1819319,2019-04-24 22:23:35 UTC,">Please attache the mixxx.log file form your mixxx-2.3.0 test.
By luck it is still there with a number prefix.
"
1819319,2019-06-23 10:44:58 UTC,I see this on 2.2.1 on Linux/NixOS as well. I think this is a regression from QT5 maybe ?
1819319,2019-04-24 22:14:52 UTC,"@Peter can you attach a log file with a failing drag and drop attempt?
https://bugs.launchpad.net/mixxx/+bug/1819319/comments/6"
1819319,2019-04-23 19:47:02 UTC,By the way? Are the GLSL Waveforms working in 2.2.1 on your device?
1819319,2020-05-22 18:28:46 UTC,Fix confirmed!
1819319,2019-04-23 19:48:28 UTC,"> milestone: 2.2.1 → 2.3.0
"
1819319,2019-04-23 19:45:39 UTC,"Please attache the mixxx.log file form your mixxx-2.3.0 test.
By luck it is still there with a number prefix.
https://www.mixxx.org/wiki/doku.php/finding_the_mixxx.log_file"
1819319,2019-04-23 18:27:31 UTC,mixxx-2.3.0-alpha-pre-master-PR1242-git6771-release-x64.exe still affected
1819319,2019-04-23 18:17:16 UTC,"@ Daniel
release candidate is unaffected. D&D works"
1819319,2019-04-22 16:06:12 UTC,"Is the release candidate for 2.2.1 effected?
http://downloads.mixxx.org/builds/2.2/release/mixxx-2.2.1-2.2-git6690-release-x64.exe"
1819319,2019-04-13 20:56:40 UTC,mixxx-2.3.0-alpha-pre-master-git6660-release-x64.exe just downloaded. Drag 'n Drop works on my system.
1819319,2019-04-24 21:51:06 UTC,"> By the way? Are the GLSL Waveforms working in 2.2.1 on your device?
They worked.
"
1819319,2019-04-07 20:46:28 UTC,"This is confirmed here:
https://www.mixxx.org/forums/viewtopic.php?f=3&t=12342&p=41529#p41236"
1819319,2019-04-23 20:04:37 UTC,"Oh sorry, I think I misunderstood the issue. I assumed this was an issue that was present in 2.2.0 that had been fixed in 2.2.1 and the fix had not been merged to master yet."
1819344,2019-03-12 00:18:10 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1819344,2019-04-23 23:54:22 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1819344,2019-06-23 04:19:04 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1819345,2019-03-10 16:41:39 UTC,test pkgs at https://launchpad.net/~ddstreet/+archive/ubuntu/lp1799697
1819345,2019-03-21 10:19:01 UTC,"The verification of the Stable Release Update for knockd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819345,2019-03-21 10:18:56 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu1.18.10.1
1819345,2019-03-18 14:29:13 UTC,"# dpkg -l |grep knockd
ii  knockd                                0.7-1ubuntu1                      amd64        small port-knock daemon"
1819345,2019-03-21 10:29:32 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu1.18.04.1
1819345,2019-03-13 20:12:15 UTC,"Hello Dan, or anyone else affected,"
1819345,2019-03-13 20:10:39 UTC,"Hello Dan, or anyone else affected,"
1819345,2019-03-12 16:16:39 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu2
1819345,2019-03-18 14:05:26 UTC,Note that the reproducer for bionic and cosmic requires manually editing the /lib/systemd/system/knock.service file to add:
1819362,2019-03-10 19:09:28 UTC,apport information
1819362,2019-03-10 19:09:21 UTC,apport information
1819362,2019-03-10 19:09:22 UTC,apport information
1819362,2019-03-10 19:09:23 UTC,apport information
1819362,2019-03-10 19:09:24 UTC,apport information
1819362,2019-03-10 19:09:25 UTC,apport information
1819362,2019-03-10 19:09:27 UTC,apport information
1819362,2019-03-10 19:09:30 UTC,apport information
1819362,2019-03-11 17:26:52 UTC,"Dear Christopher Penalver,"
1819362,2019-03-10 23:47:31 UTC,"Peter Schüller, in order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds ."
1819362,2019-03-11 17:14:23 UTC,I tested with linux-image-unsigned-5.0.1-050001-generic_5.0.1-050001.201903100732_amd64.deb and linux-modules-5.0.1-050001-generic_5.0.1-050001.201903100732_amd64.deb and it still shows the same behavior:
1819362,2019-03-11 17:25:08 UTC,"The same happens with 5.0.0 (it is the uppermost folder in the mainline builds, but I think it is older than 5.0.1). Still, I can reproduce the bug with both of them."
1819362,2019-03-10 19:09:20 UTC,apport information
1819362,2019-03-14 05:20:22 UTC,"Christoper, thanks for your help. But I think this should be mailed to the following recipients instead:"
1819362,2019-03-14 06:04:50 UTC,"Also:
https://github.com/EMnify/doc/wiki/How-to-use-a-Huawei-E3531-in-Modem-Mode"
1819362,2019-03-14 15:09:12 UTC,"Peter Schüller, please advise to all of the following:"
1819362,2019-03-16 07:57:03 UTC,The fix of Kai-Heng Feng works and the modem becomes available and at least SMS sending via modem-manager-gui works!
1819362,2019-03-16 08:53:42 UTC,"Yes, please let ""Bjørn Mork <email address hidden>"" to take a look, so we can make it work out of the box in the future."
1819362,2019-03-10 19:09:31 UTC,apport information
1819362,2019-03-10 19:09:18 UTC,apport information
1819362,2019-03-10 19:08:42 UTC,apport information
1819362,2019-03-10 19:09:16 UTC,apport information
1819362,2019-03-10 18:25:01 UTC,"# uname -a
Linux pshp 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1819362,2019-03-10 18:34:44 UTC,dmesg shows
1819362,2019-03-10 18:43:30 UTC,"Peter Schüller, thank you for reporting this and helping make Ubuntu better. Could you please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1819362"
1819362,2019-03-10 19:08:23 UTC,apport information
1819362,2019-03-10 19:08:24 UTC,apport information
1819362,2019-03-10 19:08:25 UTC,apport information
1819362,2019-03-10 19:08:27 UTC,apport information
1819362,2019-03-10 19:08:28 UTC,apport information
1819362,2019-03-10 19:08:30 UTC,apport information
1819362,2019-03-10 19:08:31 UTC,apport information
1819362,2019-03-10 19:08:33 UTC,apport information
1819362,2019-03-10 19:08:35 UTC,apport information
1819362,2019-03-10 19:08:36 UTC,apport information
1819362,2019-03-10 19:08:37 UTC,apport information
1819362,2019-03-10 19:08:38 UTC,apport information
1819362,2019-03-10 19:08:39 UTC,apport information
1819362,2019-03-17 18:41:34 UTC,I have reported the issue on the kernel mailing lists.
1819362,2019-03-10 19:09:13 UTC,apport information
1819362,2019-03-10 19:09:15 UTC,apport information
1819362,2019-03-10 19:09:17 UTC,apport information
1819362,2019-03-10 19:08:40 UTC,apport information
1819362,2019-03-30 15:22:19 UTC,"Syncing Ubuntu usb_modeswitch is hardly possible because it's a fork of the original, using a C implementation of the wrapper script."
1819362,2019-03-18 05:34:45 UTC,usb_modeswitch did once upon a time check that a driver bound to the dongles interface(s) and if not then it did a modeprobe of the option serial driver. If it still didn't get option to bind then it added the dongles usb id to option's new_id and if the driver bound then it asked the user to report the usb id to usb kernel developers so that it could be properly added to the driver.
1819362,2019-03-18 04:37:27 UTC,"It's ""2.5.2+repack0-2ubuntu1""."
1819362,2019-03-30 09:34:10 UTC,"According to Bjorn Mork [1], this modem should work out of the box without usb-modeswtich."
1819362,2019-03-18 03:29:52 UTC,"This is not an issue for Linux USB developers, it is a matter of usb_modeswitch's default switch message under linux and Canonical's implementation of usb_modeswitch."
1819362,2019-03-18 07:45:08 UTC,Addendum:
1819362,2019-03-18 17:28:33 UTC,Correction:
1819362,2019-03-18 07:37:32 UTC,The behaviour of Huawei modems depends on the respective firmware and may result in very different 'target modes'. These are the ones that can be used with Linux AFAIK:
1819363,2019-03-11 12:06:03 UTC,Attached is a patch for this issue.  I am noting that this patch is necessary when running in uefi mode to install shim-signed / grub-efi-amd64-signed / etc.
1819363,2019-03-11 12:29:30 UTC,"The attachment ""patch for 50mounted-tests"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1819363,2019-03-11 15:06:31 UTC,Which version of os-prober did you write this patch for?
1819363,2019-03-12 06:34:00 UTC,"I only stick to ""LTS"" so it is for version 1.74ubuntu1 for bionic.  Sorry I neglected to see if any updates had been made in any possible newer version"
1819365,2020-03-09 13:42:38 UTC,https://github.com/juju/juju/pull/11296
1819365,2020-02-21 06:21:00 UTC,Wrong link https://github.com/juju/juju/pull/11239
1819365,2019-12-13 04:17:21 UTC,[Expired for juju because there has been no activity for 60 days.]
1819365,2019-03-14 02:09:57 UTC,This looks specific to the case where you also specify tags as constraints but I managed to reproduce it even by just using an AZ constraint.
1819365,2019-03-11 07:32:21 UTC,"Juju defaults to 'least-used' HA placement. (So if you deploy APP -n3, we
will spread the units of the app to AZ1, AZ2, AZ3 to actually get the
benefit of *availability* zones to prevent a single failure from taking out
multiple units).
I believe we do have code that says ""try the next AZ, if we get a failure
provisioning there, skip that AZ and try the next one"". However, we need to
understand the failure is AZ specific, and not some other
could-never-be-satisfied error."
1819365,2019-03-10 18:36:37 UTC,"I've found a similar bug: https://bugs.launchpad.net/juju/+bug/1786309. But I consider it is discussing a different issue, with same final error."
1819365,2019-10-14 01:48:36 UTC,I know that some work happened in this area. Could we get this retested with the latest stable Juju?
1819367,2020-02-19 20:27:19 UTC,The New Developers Working Group also tested this and signed off:
1819367,2020-08-22 04:32:03 UTC,just noting that on bug 1332651 I'm going to offer a branch to tweak the whitespace stripping behavior
1819367,2020-08-21 18:32:17 UTC,Works great for me.  A nice addition.  Merged to master for 3.6.  Thanks!
1819367,2020-02-19 20:09:55 UTC,"I have tested this code and consent to signing off on it with my name, Elaine Hardy and by email: <email address hidden>"
1819367,2019-03-11 12:53:45 UTC,+1
1819367,2020-02-19 19:38:28 UTC,Looks like the fix may not have been added to that sandbox... will test again when we verify it has
1819367,2020-02-19 19:00:29 UTC,Tested on https://bugs.launchpad.net/evergreen/+bug/1819367
1819367,2019-09-13 16:48:58 UTC,Branch at user/stompro/lp1819367_item_status_csv_paste
1819367,2020-02-19 20:08:28 UTC,Tested again and works as expected. I tested a list of barcodes from a single record and barcodes from multiple record and all were retrieved!
1819379,2020-10-05 21:34:15 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11330"
1819379,2020-10-05 21:34:14 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11329"
1819379,2020-10-05 21:34:14 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11328"
1819379,2020-10-09 05:05:51 UTC,"Some of our behat tests are failing when run on the patch.  These tests are passing in current master.  Please see the attached document ""Bug 1819379: Behat results"" for details"
1819379,2020-10-05 21:18:52 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11327"
1819379,2020-08-11 03:56:28 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11128"
1819379,2020-09-04 20:20:25 UTC,"Reviewed:  https://reviews.mahara.org/11175
Committed: https://git.mahara.org/mahara/mahara/commit/166cffa64d2941341dcb5ffe656164cf1e2b3b6d
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1819379,2020-10-05 21:18:52 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11326"
1819379,2020-07-20 06:18:18 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11076"
1819379,2020-08-10 03:27:37 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11122"
1819379,2020-08-24 21:56:06 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11175"
1819379,2020-08-11 03:56:27 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11127"
1819381,2019-03-11 20:02:56 UTC,"What do you mean by ""I am operating a static train""? Have you switched player train to a static consist?
Can you attach a screenshot (showing track monitor, train list window and also the dispatcher info HUD) taken just before passing the red signal?"
1819381,2019-05-17 04:17:20 UTC,[Expired for Open Rails because there has been no activity for 60 days.]
1819382,2019-05-16 23:19:12 UTC,"Reviewed:  https://review.opendev.org/659156
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=e6086328f4e672192377d78c08d652b1aebc0625
Submitter: Zuul
Branch:    master"
1819382,2019-05-14 20:24:28 UTC,TRIAGE:
1819382,2019-05-14 20:26:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659156"
1819382,2019-05-16 14:58:50 UTC,"Reviewed:  https://review.opendev.org/659355
Committed: https://git.openstack.org/cgit/openstack/charms.ceph/commit/?id=cd5360736d217cedb80fed6538749508b240b236
Submitter: Zuul
Branch:    master"
1819383,2019-03-11 01:38:47 UTC,apport information
1819383,2019-03-22 08:52:49 UTC,I tried the latest v5.0.3 kernel and it has the same behaviour.
1819383,2019-03-14 06:20:57 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0]."
1819383,2019-03-14 06:20:22 UTC,"I guess it's still related to the kernel:
[    3.674022] [drm] {1680x1050, 1840x1080@119000Khz}"
1819383,2019-03-11 01:38:54 UTC,apport information
1819383,2019-03-11 02:25:06 UTC,"$ apt-cache policy xserver-xorg-video-radeon
xserver-xorg-video-radeon:
  Installed: 1:18.0.1-1
  Candidate: 1:18.0.1-1
  Version table:
 *** 1:18.0.1-1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status"
1819383,2019-03-11 02:22:08 UTC,"Actually, the Vega 64 uses the radeon driver"
1819383,2019-03-11 01:38:57 UTC,apport information
1819383,2019-03-11 02:27:16 UTC,No.  I was right the first time
1819383,2019-03-11 02:12:25 UTC,I don't think this is a kernel issue.  More likely Xorg
1819383,2019-03-11 01:38:46 UTC,apport information
1819383,2019-03-11 01:38:49 UTC,apport information
1819383,2019-03-10 23:05:57 UTC,My Xorg.0.log including logs of me switching modes many times.
1819383,2019-03-10 23:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819383,2019-03-11 01:38:34 UTC,apport information
1819383,2019-03-11 01:38:35 UTC,apport information
1819383,2019-03-11 01:38:37 UTC,apport information
1819383,2019-03-11 01:38:39 UTC,apport information
1819383,2019-03-11 01:38:40 UTC,apport information
1819383,2019-03-11 01:38:42 UTC,apport information
1819383,2019-03-11 01:38:51 UTC,apport information
1819383,2019-03-11 01:38:44 UTC,apport information
1819389,2019-03-11 01:05:19 UTC,"Version is 5.0.0+ (only patch applied for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547), so should not have impact here as the error exists with or without that patch."
1819389,2019-03-11 01:30:04 UTC,This change was made by a bot.
1819389,2019-03-11 18:01:23 UTC,NOTE: The pen also reports a 1% battery all of the time. I'm not sure if this is directly related.
1819389,2019-03-12 03:52:31 UTC,Workaround patch:
1819389,2019-03-15 20:56:59 UTC,"I will give this a shot today, however after pulling the latest kernel source, it looks like part of that patch made it in, but not all of it."
1819390,2020-06-30 02:18:07 UTC,Generating a new appKey without a slash was surprisingly easy.  It only took one try on the Backblaze website (I haven't played too much with the backblaze-b2 CLI command available in the AUR).
1819390,2020-06-27 19:39:57 UTC,This occurs with Duplicity 0.8.12 on Arch Linux.  I've had to resort to using my master keyID/appKey (which does not contain a slash in the appKey).
1819390,2020-06-30 02:21:38 UTC,"I assume this problem would occur if either key (keyID or appKey) contained a slash ('/'), but I haven't encountered a keyID containing a slash yet."
1819393,2019-03-11 08:44:47 UTC,"Hi Kentarou,"
1819393,2019-04-04 21:15:28 UTC,"Hi Kentarou,"
1819393,2019-07-10 07:26:36 UTC,"Dear Benjamin,"
1819393,2019-07-10 09:02:32 UTC,"Hi Iftah,"
1819393,2019-07-10 15:42:18 UTC,"Hi Benjamin,"
1819393,2019-07-10 21:27:08 UTC,"Hi Iftah,"
1819393,2019-07-12 14:04:09 UTC,"Hi Benjamin,"
1819393,2019-07-15 17:03:05 UTC,"Hi again,"
1819393,2019-07-16 06:21:23 UTC,Ok good. Let's focus on the other thread then (I was away for 4-5 days but am now back).
1819406,2019-07-27 08:26:27 UTC,"CVE-2019-13604 and CVE-2019-13621 have been assigned.
Please check the following PoC:
https://github.com/sungjungk/fp-scanner-hacking
https://github.com/sungjungk/fp-img-key-crack"
1819406,2020-11-25 16:27:39 UTC,As per upstream decision...
1819406,2019-03-22 05:17:49 UTC,It is demo video: https://www.youtube.com/watch?v=Grirez2xeas
1819406,2019-03-21 07:06:31 UTC,Please check the following PoC.
1819406,2019-03-14 15:24:26 UTC,What do you think of this issue?
1819406,2019-03-11 10:50:59 UTC,Could you check the following link?
1819406,2019-03-11 10:00:31 UTC,"sorry, commented on the wrong bug"
1819406,2019-03-11 09:57:41 UTC,"Thanks, it's https://gitlab.freedesktop.org/libfprint/fprintd/issues/16"
1819406,2019-03-15 11:51:37 UTC,"It seems that the uru4000 driver is affected by a weak? or broken? obfuscation feature, allowing MITM attackers to discover user's precious fingerprint images."
1819406,2019-03-11 09:49:57 UTC,"Thank you for your bug report, do you have any pointer to the discuss with the upstream maintainer?"
1819408,2019-03-15 04:29:28 UTC,"I can see why this is happening (we only read lock the source branch), but I'm having trouble reproducing it. Not sure why we don't hit this more often."
1819408,2020-02-09 01:50:22 UTC,I'm having trouble reproducing this. :-/ Do you have a simple script to reproduce it?
1819408,2020-02-09 14:20:56 UTC,Sorry... it was a while ago.
1819409,2019-09-04 01:58:16 UTC,PR for server-side: https://github.com/juju/juju/pull/10595
1819409,2019-08-29 00:30:49 UTC,"Since I am in the area, I am picking this up :)"
1819409,2019-08-30 07:29:54 UTC,PR against develop: https://github.com/juju/juju/pull/10580
1819409,2019-09-02 02:25:00 UTC,"The PR above deals with client side only. We'll have a separate PR that deals with server-side, i.e. at apiserver layer."
1819413,2019-10-17 08:17:06 UTC,"oem-osp1 was handled via bug 1836012, and 19.10 ships with 5.3"
1819413,2019-05-21 01:54:52 UTC,"On Intel ICL-Y SDP(alpha):
Before patched
short idle: 13.46w
long idle: 12.94w
s2idle: 12.67w"
1819413,2019-05-17 03:34:45 UTC,"Those commits doesn't affect the power consumption on Intel ICL-Y SDP(alpha), so I'm not sure if they help on power consumption on real products."
1819413,2019-05-06 06:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819413,2019-07-10 08:12:30 UTC,"The pmc_core commits listed in this bug have been submitted to oem-osp1-b kernel
https://lists.ubuntu.com/archives/kernel-team/2019-July/102063.html"
1819419,2019-04-25 17:52:35 UTC,"@JP, thanks. I forgot the wxITEM_CHECK fix would cause a conflict with the 5.1 branch. The attached excludes that for the 5.1 branch if it's still possible to get it merged."
1819419,2019-04-25 18:37:07 UTC,"@Michael,
I just committed your second fix to the stable 5.1.3 branch. Thanks."
1819419,2019-04-25 17:40:04 UTC,"@Michael,
I committed your fix only to the master branch. Thanks."
1819419,2019-03-11 11:07:54 UTC,"You can fix some of these by changing the Hotkey from Delete to Backspace, but only some of them."
1819419,2019-03-11 13:38:31 UTC,"Hi Sethh,"
1819419,2019-03-11 13:15:06 UTC,Cmd+Delete should work
1819419,2019-03-11 11:09:06 UTC,Note that it's not just the Page Layout Editor; Eeschema and Pcbnew also have this issue in places.
1819419,2019-04-25 13:15:19 UTC,This should make everything deletable using the delete key (Fn+backspace on Mac). Also I fixed a stray assert from the move of the zoom tools to the modern toolset.
1819420,2019-03-11 15:40:54 UTC,apport information
1819420,2019-03-11 15:40:58 UTC,apport information
1819420,2019-03-11 15:40:52 UTC,apport information
1819420,2019-03-11 16:00:56 UTC,"Please attach `journalctl -b -1 -k`, many some useful kernel log was collected."
1819420,2019-03-14 06:02:46 UTC,Also is the the same one as LP: #1819486? I built a test kernel in that bug.
1819420,2019-05-14 04:17:18 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1819420,2019-03-11 15:41:00 UTC,apport information
1819420,2019-03-11 15:40:51 UTC,apport information
1819420,2019-03-11 15:40:56 UTC,apport information
1819420,2019-03-11 15:40:48 UTC,apport information
1819420,2019-03-11 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819420,2019-03-11 15:40:37 UTC,apport information
1819420,2019-03-11 15:40:39 UTC,apport information
1819420,2019-03-11 15:40:41 UTC,apport information
1819420,2019-03-11 15:40:49 UTC,apport information
1819420,2019-03-11 15:40:44 UTC,apport information
1819420,2019-03-11 15:40:46 UTC,apport information
1819420,2019-03-11 15:40:47 UTC,apport information
1819420,2019-03-11 15:40:43 UTC,apport information
1819421,2019-03-11 08:45:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819421,2019-03-20 08:29:13 UTC,still hit the issue with disco-desktop-amd64.iso daily build 19-Mar-2019
1819421,2019-04-02 18:32:15 UTC,Can you give some more details about what's wrong here?
1819421,2019-04-03 02:50:05 UTC,"Please check that attached file ""Screen Shot 2019-03-08 at 11.58.00 AM.png"", It seems like part of the menu items is missing."
1819421,2019-04-03 08:11:57 UTC,"This is due to a change in the way GNOME handles ""the desktop"" where the wallpaper and icons can go.  There is a new menu here, and that's what you're seeing."
1819421,2019-04-03 08:49:01 UTC,"In Ubuntu 18.10 (and many years prior), it was nautilus-desktop which owned and rendered the desktop including its menus."
1819421,2019-08-19 03:41:18 UTC,"It doesn't sound like this is a bug. ""Not normal"" just means we changed how desktop icons and menus are rendered/generated in 19.04."
1819424,2019-03-11 09:12:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642388"
1819425,2019-09-27 09:03:36 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1819425,2019-03-27 16:19:20 UTC,I don't think this bug is valid. non-admin user can be configured to be allowed to filter by instance UUID by configuring the nova policy.json appropriately [1]:
1819425,2019-05-23 07:31:15 UTC,"Reviewed:  https://review.opendev.org/642403
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=31007102b019f93918046657c78ddf3b6b09711e
Submitter: Zuul
Branch:    master"
1819425,2019-03-11 10:18:59 UTC,Sorry but can you provide more information about this ? Its not exactly clear what the bug is.
1819434,2019-03-11 10:16:57 UTC,"Removing the package after the failed install is not straight forward, here is a workarond:
    sudo systemctl stop tenshi.service; sudo killall tenshi; sudo apt purge tenshi"
1819434,2019-03-13 01:51:28 UTC,Also fails on 16.04. Hanging on multiple installations.
1819434,2019-03-13 01:51:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819434,2019-03-13 02:04:53 UTC,Here is a startup hang and status on a 16.04 system.  Identical behavior on a 18.04 fresh install.
1819434,2019-04-15 01:33:27 UTC,Adding --background to the start-stop-daemon command in the init script seems to get around the issue.
1819435,2020-12-16 13:43:30 UTC,I'm facing a similar situation with building a focal autopkgtest container on s390x:
1819435,2020-12-16 13:45:28 UTC,"Here the versions in use:
$ snap list lxd
Name  Version  Rev    Tracking       Publisher   Notes
lxd   4.9      18675  latest/stable  canonical✓  -
$ apt-cache policy autopkgtest
autopkgtest:
  Installed: 5.11ubuntu1
  Candidate: 5.11ubuntu1
  Version table:
 *** 5.11ubuntu1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
        500 http://us.ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
        100 /var/lib/dpkg/status"
1819436,2019-10-08 06:47:46 UTC,"Tested with the udev data from the linkded submissions, it works with the latest stable release (Oct '19). Actually the code responsible for the crash is gone (the plainbox pkexec trusted launcher, aka ptl)."
1819436,2019-11-14 07:12:13 UTC,This issue was fixed in 50rc2 and verified passed.
1819437,2020-02-13 20:03:56 UTC,"This issue has been resolved upstream:
pr#30519 in 12.2.13
pr#30481 in 13.2.7
pr#30480 in 14.2.5"
1819437,2020-04-16 00:38:45 UTC,Posting an update with recent SRU activity.
1819437,2020-11-13 17:36:26 UTC,"The 12.2.13 SRU for bionic, and queens is available in -updates (bug 1861793)."
1819439,2019-03-12 14:44:47 UTC,"Confirmed, reload is triggering a restart in xenial, bionic and cosmic. It's fixed in disco."
1819443,2019-03-11 15:47:10 UTC,"1. The precompiled dtb's -> i can check if we can ship them in the d-i initrd preinstalled, or at least add them for the mini.iso and/or server.iso"
1819443,2019-03-13 10:16:03 UTC,1. Sounds good.  Please let me know your findings.
1819443,2019-03-26 10:50:32 UTC,Has there been any movement on this yet?
1819443,2019-03-11 11:20:23 UTC,1. Which files are these? can you please give names of .deb and file paths that are in the archive; but missing from the installer environments?
1819443,2019-03-11 12:01:16 UTC,Thanks for your rapid response.
1819444,2019-03-12 01:56:53 UTC,"Afaict these libraries are not being distributed by raspbian per-se but by the raspberry pi foundation as part of the packages they build on top of raspbian. So this needs to be discussed with them, not with us."
1819444,2019-04-10 15:44:35 UTC,"Yup, the userland repo does indeed contain the source for the libraries concerned (libbcm_host.so, libvcos.so, and libvchiq_arm.so). It also, as plugwash notes, has a GPL-compatible 3-clause BSD license."
1819446,2019-03-11 19:22:58 UTC,Confirmed using openstackclient.
1819448,2019-04-16 16:40:48 UTC,This bug was fixed in the package android-platform-system-extras - 8.1.0+r23-2~18.10
1819448,2019-04-16 16:40:35 UTC,This bug was fixed in the package android-platform-libnativehelper - 8.1.0+r23-1~18.10
1819448,2019-04-16 16:40:25 UTC,This bug was fixed in the package android-platform-external-libselinux - 8.1.0+r23-2~18.10
1819448,2019-04-16 16:32:37 UTC,This bug was fixed in the package enjarify - 1:1.0.3-4~18.04
1819448,2019-04-16 16:40:16 UTC,This bug was fixed in the package android-platform-dalvik - 8.1.0+r23-2~18.10
1819448,2019-04-16 16:40:03 UTC,This bug was fixed in the package android-platform-art - 8.1.0+r23-3~18.10
1819448,2019-04-16 16:40:51 UTC,This bug was fixed in the package android-platform-tools-apksig - 0.8-2ubuntu1~18.04
1819448,2019-04-16 16:32:12 UTC,This bug was fixed in the package apktool - 2.3.4-1~18.04
1819448,2019-04-16 16:31:57 UTC,This bug was fixed in the package android-platform-system-tools-aidl - 1:8.1.0+r23-1~18.04
1819448,2019-04-16 16:40:55 UTC,This bug was fixed in the package android-sdk-meta - 25.0.0+10~18.04.2
1819448,2019-04-16 16:47:13 UTC,This bug was fixed in the package libscout - 2.3.2-1~18.04
1819448,2019-04-16 16:41:50 UTC,This bug was fixed in the package dummydroid - 1.2-2~18.04
1819448,2019-04-16 16:42:53 UTC,This bug was fixed in the package f2fs-tools - 1.11.0-1.1~18.10
1819448,2019-04-16 16:47:50 UTC,This bug was fixed in the package libsmali-java - 2.2.6-1~18.04
1819448,2019-04-16 16:50:37 UTC,This bug was fixed in the package android-platform-frameworks-data-binding - 2.2.2-3~18.04.1
1819448,2019-04-16 16:50:40 UTC,This bug was fixed in the package android-platform-frameworks-base - 1:8.1.0+r23-3~18.10
1819448,2019-04-16 16:51:39 UTC,This bug was fixed in the package wala - 1.5.1-1~18.04
1819448,2019-04-16 20:49:38 UTC,This bug was fixed in the package android-platform-libcore - 8.1.0+r23-2~18.04
1819448,2019-04-16 20:51:09 UTC,This bug was fixed in the package android-framework-23 - 6.0.1+r72-5~18.04
1819448,2019-04-16 20:55:21 UTC,This bug was fixed in the package android-platform-build - 1:8.1.0+r23-2~18.04
1819448,2019-04-16 16:41:47 UTC,This bug was fixed in the package cava - 0.6.0-1~18.04
1819448,2019-04-16 16:31:53 UTC,This bug was fixed in the package android-platform-frameworks-native - 1:8.1.0+r23-2~18.04
1819448,2019-04-16 16:30:53 UTC,This bug was fixed in the package android-platform-dalvik - 8.1.0+r23-2~18.04
1819448,2019-04-16 16:31:47 UTC,This bug was fixed in the package android-platform-external-boringssl - 8.1.0+r23-2~18.04
1819448,2019-03-12 17:57:05 UTC,All packages have been uploaded and approved for bionic-proposed.
1819448,2019-04-16 16:31:50 UTC,This bug was fixed in the package android-platform-external-libunwind - 8.1.0+r23-2~18.04
1819448,2019-03-13 02:19:53 UTC,"I've removed android-sdk-meta 25.0.0+10~18.04 from bionic-proposed and cosmic-proposed, as it produced binaries with the same version as are already in disco, e.g. android-sdk-platform-tools-common 27.0.0+10."
1819448,2019-04-09 14:45:18 UTC,"Please, could android-platform-system-core 1:8.1.0+r23-5 be backported to 18.04 LTS, instead of 1:8.1.0+r23-4, it fixes two packaging bugs:"
1819448,2019-04-16 16:20:39 UTC,This bug was fixed in the package android-platform-art - 8.1.0+r23-3~18.04
1819448,2019-04-16 16:20:44 UTC,This bug was fixed in the package android-platform-external-libselinux - 8.1.0+r23-2~18.04
1819448,2019-04-16 16:20:49 UTC,This bug was fixed in the package android-platform-frameworks-base - 1:8.1.0+r23-3~18.04
1819448,2019-04-16 16:21:09 UTC,This bug was fixed in the package android-platform-system-extras - 8.1.0+r23-2~18.04
1819448,2019-04-16 16:21:14 UTC,This bug was fixed in the package android-platform-tools-apksig - 0.8-2ubuntu1~18.04
1819448,2019-04-16 16:21:17 UTC,This bug was fixed in the package android-sdk-meta - 25.0.0+10~18.04.2
1819448,2019-04-16 16:20:54 UTC,This bug was fixed in the package android-platform-frameworks-data-binding - 2.2.2-3~18.04.1
1819448,2019-04-16 16:22:19 UTC,This bug was fixed in the package dummydroid - 1.2-2~18.04
1819448,2019-04-16 16:23:17 UTC,This bug was fixed in the package f2fs-tools - 1.11.0-1.1~18.04
1819448,2019-04-16 16:27:21 UTC,This bug was fixed in the package libscout - 2.3.2-1~18.04
1819448,2019-04-16 16:31:44 UTC,This bug was fixed in the package android-platform-development - 8.1.0+r23-1~18.04
1819448,2019-04-16 16:27:28 UTC,This bug was fixed in the package libsmali-java - 2.2.6-1~18.04
1819448,2019-04-16 16:30:43 UTC,This bug was fixed in the package android-framework-23 - 6.0.1+r72-5~18.04
1819448,2019-04-16 16:30:46 UTC,This bug was fixed in the package android-platform-build - 1:8.1.0+r23-2~18.04
1819448,2019-04-16 16:31:11 UTC,This bug was fixed in the package android-platform-libcore - 8.1.0+r23-2~18.04
1819448,2019-04-16 16:31:13 UTC,This bug was fixed in the package android-platform-libnativehelper - 8.1.0+r23-1~18.04
1819448,2019-04-16 16:22:04 UTC,This bug was fixed in the package cava - 0.6.0-1~18.04
1819448,2019-04-16 16:31:34 UTC,This bug was fixed in the package wala - 1.5.1-1~18.04
1819450,2019-11-08 19:17:42 UTC,We're seeing this in 3.3.4 as well.
1819450,2020-04-06 23:04:37 UTC,This continues to be an issue in 3.5
1819453,2019-05-13 21:47:10 UTC,"Is there any update with regard to my comment https://bugs.launchpad.net/keystone/+bug/1819453/comments/15 ? What steps should I take to reproduce this, or can it be closed?"
1819453,2019-03-20 15:12:53 UTC,"@Colleen, I didn't get around to confirming on stein. The code seems to have changed around enough for the recreate patch above to not work."
1819453,2019-03-21 16:09:27 UTC,I can't reproduce this either on Stein or Queens with devstack. Haven't tried with Ocata yet. This is what I tried:
1819453,2019-03-20 15:21:19 UTC,I mean queens.
1819453,2019-03-20 15:20:33 UTC,"Sorry I triaged the wrong bug. I'll just mark this as triaged for ocata for now until I, or someone else, has more time to look at other releases."
1819453,2019-03-20 15:13:21 UTC,s/not to work/not to apply
1819453,2019-03-19 15:22:09 UTC,Here's a query I used to determine we have entries in id_mapping table that don't have a matching local_entity in the user/nonlocal_user tables.
1819453,2019-03-11 18:15:18 UTC,"I'm not able to recreate this on stein (that is, assuming I understand the problem correctly)."
1819453,2019-03-15 12:19:06 UTC,Is this confirmed for Stein or only for Queens?
1819453,2019-03-11 15:37:28 UTC,Note that 11.0.3 is Ocata. We do have an 11.0.4 package version available. First thing I'd like to check is to see if this is fixed in either 11.0.4 or a future keystone release.
1819453,2019-03-11 15:55:33 UTC,"David, just to be clear, is this an issue where the specified domain in 'openstack user list --domain customerdata' does not exist and it should fail gracefully rather than with a traceback? Also it seems that this is not LDAP specific, but please correct me if I'm wrong. I'm deploying stein to see if it recreates there."
1819453,2019-03-12 04:17:07 UTC,"Corey, the problem here is the fact that there are users in LDAP with None as id. The existence of a one such user causes `openstack user list --domain dom0` to fail with the error:"
1819453,2019-03-19 15:19:58 UTC,This is only confirmed on xenial Ocata.
1819453,2019-03-12 21:08:10 UTC,Here's a patch to force this failure to occur on Queens:
1819453,2019-03-13 11:47:50 UTC,"@Corey, we have no workaround for this error."
1819453,2019-03-12 12:15:57 UTC,"Thanks Alok. Do you have a work around for this? I'm assuming users with id=None are invalid, but obviously failing to list users is an issue and keystone should be handling that scenario."
1819454,2019-03-11 16:21:04 UTC,"The attachment ""debdiff.patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1819454,2019-04-20 20:18:30 UTC,"ogra has already sponsored the change to Disco, and there is no SRU bug template for the other stable releases."
1819458,2019-08-14 11:39:39 UTC,There's a degree of tension between too many distinct icons and icons being repurposed.  We've just gone away from an icon for every different purpose in 4.0.
1819460,2019-05-23 17:35:46 UTC,"Reviewed:  https://review.opendev.org/657602
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1c774315a5134937909f674b5c5a65f06efb3cb7
Submitter: Zuul
Branch:    stable/stein"
1819460,2019-09-27 09:05:18 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1819460,2019-07-30 16:18:22 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/673550
Reason: Does not apply to stable/rocky."
1819460,2019-07-30 16:18:16 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/673546
Reason: Does not apply to stable/rocky."
1819460,2019-07-30 15:58:02 UTC,"Actually ignore comment 15, claim_resources didn't raise AllocationUpdateFailed until Stein:"
1819460,2019-07-30 14:46:00 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/673546"
1819460,2019-07-30 14:41:32 UTC,I'll be backporting the non-fill provider mapping part of this to rocky and queens since the code fix and functional tests related to bug 1837955 rely on changes from the series that fixed this bug.
1819460,2019-06-06 06:24:07 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1819460,2019-05-22 20:30:07 UTC,"Reviewed:  https://review.opendev.org/657601
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c38a82190242aeea3c3577cd7dde9fba8bb04d72
Submitter: Zuul
Branch:    stable/stein"
1819460,2019-07-30 14:57:20 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/673550"
1819460,2019-05-07 13:50:32 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/657602"
1819460,2019-03-11 13:41:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/642444"
1819460,2019-03-11 14:27:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642470"
1819460,2019-03-11 14:31:45 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.openstack.org/642470
Reason: It was a mistake to push this with a new changeid, here is the orignal patch https://review.openstack.org/#/c/639608/"
1819460,2019-03-29 02:41:40 UTC,"Reviewed:  https://review.openstack.org/642444
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b63c42a0d4836fd0364cb306145d3474619f1e19
Submitter: Zuul
Branch:    master"
1819460,2019-05-22 20:27:47 UTC,"Reviewed:  https://review.opendev.org/657600
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=07a1a8ff7dcb00283ba7ebb6f59a70002a4ee4db
Submitter: Zuul
Branch:    stable/stein"
1819460,2019-03-29 16:26:44 UTC,"Reviewed:  https://review.openstack.org/648651
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fd3b86d1c35efdd8356233863b8ad5b628df8d29
Submitter: Zuul
Branch:    master"
1819460,2019-03-29 23:55:22 UTC,"Reviewed:  https://review.openstack.org/639608
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b096d9303acfea81ca56394cab681d2b2eed2d91
Submitter: Zuul
Branch:    master"
1819460,2019-05-07 13:49:59 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/657600"
1819460,2019-05-07 13:50:15 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/657601"
1819460,2019-03-29 09:23:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/648651"
1819461,2020-01-30 13:29:56 UTC,"Reviewed:  https://review.opendev.org/704808
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=2426780600c6d2f610e066111947d0655c325fd9
Submitter: Zuul
Branch:    master"
1819461,2020-01-29 14:05:48 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/704808"
1819461,2020-01-24 08:35:42 UTC,"for info, the patch has been integrated to kolla for a long time now:
commit c4b62490714ea849cedfe07d4b9a6aebf1f815c0
Author: Cédric Jeanneret <email address hidden>
Date:   Tue Apr 30 16:11:46 2019 +0200"
1819461,2019-04-11 08:47:28 UTC,"I wish :). The -E is needed because we need to pass down the KOLLA_ env variables. Kolla fails if it does not have the KOLLA_COPY_STRATEGY var, for example."
1819461,2019-04-10 16:10:37 UTC,So I looked at this a bit more and it is not specific to nova. This is how kolla really works.
1819461,2019-03-26 18:03:35 UTC,"/var/log/audit/audit.log:type=USER_ACCT msg=audit(1553621646.085:3730): pid=71808 uid=42436 auid=4294967295 ses=4294967295 subj=system_u:system_r:container_t:s0:c493,c684 msg='op=PAM:accounting grantors=pam_unix acct=""nova"" exe=""/usr/bin/sudo"" hostname=? addr=? terminal=? res=success'UID=""unknown(42436)"" AUID=""unset""
/var/log/audit/audit.log:type=USER_CMD msg=audit(1553621646.085:3731): pid=71808 uid=42436 auid=4294967295 ses=4294967295 subj=system_u:system_r:container_t:s0:c493,c684 msg='cwd=""/"" cmd=""kolla_set_configs"" terminal=? res=success'UID=""unknown(42436)"" AUID=""unset""
/var/log/audit/audit.log:type=CRED_REFR msg=audit(1553621646.085:3732): pid=71808 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:container_t:s0:c493,c684 msg='op=PAM:setcred grantors=pam_env,pam_unix acct=""root"" exe=""/usr/bin/sudo"" hostname=? addr=? terminal=? res=success'UID=""root"" AUID=""unset""
/var/log/audit/audit.log:type=AVC msg=audit(1553621646.085:3733): avc:  denied  { connectto } for  pid=71808 comm=""sudo"" path=""/run/dbus/system_bus_socket"" scontext=system_u:system_r:container_t:s0:c493,c684 tcontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tclass=unix_stream_socket permissive=0
/var/log/audit/audit.log:type=SYSCALL msg=audit(1553621646.085:3733): arch=c000003e syscall=42 success=no exit=-13 a0=4 a1=56057de3b810 a2=1d a3=7ffcbd665f90 items=0 ppid=71791 pid=71808 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=""sudo"" exe=""/usr/bin/sudo"" subj=system_u:system_r:container_t:s0:c493,c684 key=(null)ARCH=x86_64 SYSCALL=connect AUID=""unset"" UID=""root"" GID=""root"" EUID=""root"" SUID=""root"" FSUID=""root"" EGID=""root"" SGID=""root"" FSGID=""root""
/var/log/audit/audit.log:type=USER_START msg=audit(1553621646.085:3734): pid=71808 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:container_t:s0:c493,c684 msg='op=PAM:session_open grantors=pam_limits,pam_unix acct=""root"" exe=""/usr/bin/sudo"" hostname=? addr=? terminal=? res=success'UID=""root"" AUID=""unset""
/var/log/audit/audit.log:type=USER_END msg=audit(1553621646.180:3735): pid=71808 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:container_t:s0:c493,c684 msg='op=PAM:session_close grantors=pam_limits,pam_unix acct=""root"" exe=""/usr/bin/sudo"" hostname=? addr=? terminal=? res=success'UID=""root"" AUID=""unset""
/var/log/audit/audit.log:type=CRED_DISP msg=audit(1553621646.180:3736): pid=71808 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:container_t:s0:c493,c684 msg='op=PAM:setcred grantors=pam_env,pam_unix acct=""root"" exe=""/usr/bin/sudo"" hostname=? addr=? terminal=? res=success'UID=""root"" AUID=""unset""
/var/log/secure:Mar 26 17:34:06 undercloud-0 sudo[71808]: nova : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/local/bin/kolla_set_configs
/var/log/secure:Mar 26 17:34:06 undercloud-0 sudo[71808]: pam_systemd(sudo:session): Failed to connect to system bus: Permission denied
/var/log/secure:Mar 26 17:34:06 undercloud-0 sudo[71808]: pam_unix(sudo:session): session opened for user root by (uid=0)
/var/log/secure:Mar 26 17:34:06 undercloud-0 sudo[71808]: pam_unix(sudo:session): session closed for user root"
1819461,2019-04-29 14:05:51 UTC,"So, while I have not tried this personally yet, I am moderately sure this is due to pam+sudo (I say this because in https://review.opendev.org/#/c/629200/ we did something potentially similar)."
1819461,2019-04-11 05:48:45 UTC,"hmmmm. the right question is: ""is -E option really needed? What if we drop it?"" imho."
1819466,2020-05-25 22:23:19 UTC,"@Simon, as the one that dropped it to 9... thoughts? Meanwhile, should we continue using ""DejaVu Sans Mono"" as our terminal font?"
1819467,2019-03-11 15:00:06 UTC,This change was made by a bot.
1819470,2019-03-11 14:50:03 UTC,aaa
1819470,2019-05-24 04:17:12 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1819471,2019-03-11 15:48:58 UTC,"Thank you for your bug report, the key is ubuntu specific and buggy, but the feature request is also discussion upstream on https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/111"
1819472,2019-03-11 15:23:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642493"
1819480,2019-03-11 15:48:56 UTC,"Also, to confirm, you can try to delete the broam from netplan, udpate your config, and restart maas-regiond and confirm that the bond is there."
1819480,2019-03-11 15:58:31 UTC,Some logs with `debug: true` set on both rackd and regiond (after the latest restart):
1819480,2019-03-13 00:36:59 UTC,"#3 information is missing, setting as incomplete. Also, as per #2, the modeling is correct provided that the bond is used behind a bridge, and the bridge is discovered correctly. The region-controllers read shows that."
1819480,2019-05-12 04:17:36 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1819480,2019-03-11 15:47:33 UTC,I see this:
1819485,2019-05-08 19:53:59 UTC,The following patches will not be submitted:
1819485,2019-05-15 18:49:48 UTC,"Hi Kim,"
1819485,2019-05-15 19:47:56 UTC,"Michael,
You will need the following for the 256 Cores:"
1819485,2019-05-17 08:13:03 UTC,"Hi Kim,"
1819485,2019-05-20 14:13:55 UTC,"Andrea,
Thank you I will test."
1819485,2019-06-18 16:02:32 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1819485,2019-05-28 20:57:23 UTC,I have also tested this using the test kernel in comment #20 and it is working as intended.
1819485,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1819485,2019-08-22 16:15:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1819485,2019-11-14 04:34:23 UTC,"Patchset available in Focal, closing this."
1819485,2019-05-20 16:41:20 UTC,"Andrea,
I have confirmed it is working as intended."
1819485,2019-05-06 19:53:39 UTC,"Jeff, Yes this works with Disco and 5.0 kernel. My objective is to submit these patches to 18.04.1 LTS. There are 3 other patches as well.(Launchpad:1816669)."
1819485,2019-05-08 19:49:20 UTC,SRU
1819485,2019-03-11 16:30:06 UTC,This change was made by a bot.
1819485,2019-03-11 16:27:53 UTC,apport information
1819485,2019-05-06 15:10:41 UTC,Does this work in Disco w/ 5.0 kernel?
1819485,2019-03-11 16:27:59 UTC,apport information
1819485,2019-03-11 16:28:02 UTC,apport information
1819485,2019-03-11 16:28:04 UTC,apport information
1819485,2019-03-11 16:27:55 UTC,apport information
1819485,2019-03-11 16:28:09 UTC,apport information
1819485,2019-03-11 16:28:11 UTC,apport information
1819485,2019-03-11 16:28:12 UTC,apport information
1819485,2019-03-11 16:28:15 UTC,apport information
1819485,2019-03-11 16:28:26 UTC,apport information
1819485,2019-03-11 16:28:06 UTC,apport information
1819485,2019-03-11 16:28:01 UTC,apport information
1819486,2019-03-12 16:34:32 UTC,"Yes, that's the only commit between -45 and -46."
1819486,2019-11-14 14:34:00 UTC,"Hi,"
1819486,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1819486,2019-04-18 22:07:35 UTC,"Hello,"
1819486,2019-04-16 16:26:34 UTC,"Hello Nicolas,"
1819486,2019-04-04 18:03:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1819486,2019-03-14 19:40:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819486,2019-03-12 10:52:41 UTC,*modules* not installed?
1819486,2019-03-11 16:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819486,2019-03-12 10:36:07 UTC,"Kai, It looks like that the intel driver was not bundle in this kernel? No kernel panic but WM runs in software mode and additional display are not being detected."
1819486,2019-03-12 06:23:40 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1819486/"
1819486,2019-03-11 18:00:07 UTC,This change was made by a bot.
1819486,2019-03-11 17:52:05 UTC,apport information
1819486,2019-03-11 17:52:02 UTC,apport information
1819486,2019-03-11 17:52:01 UTC,apport information
1819486,2019-03-12 11:11:12 UTC,"pff, clearly I needed one cup of coffee before answering this.. sry. I will check again shortly.."
1819486,2019-03-11 17:51:59 UTC,apport information
1819486,2019-03-11 17:51:58 UTC,apport information
1819486,2019-03-12 12:02:44 UTC,"Yeah, it works fine with your module. Did you just revert ""drm-i915-fix-hotplug-irq-ack-on-i965-g4x.patch"" ?"
1819486,2019-03-11 17:51:55 UTC,apport information
1819486,2019-03-11 17:51:52 UTC,apport information
1819486,2019-03-11 17:51:50 UTC,apport information
1819486,2019-03-11 17:51:49 UTC,apport information
1819486,2019-03-11 17:51:48 UTC,apport information
1819486,2019-03-11 17:51:57 UTC,apport information
1819486,2019-03-11 17:51:45 UTC,apport information
1819486,2019-03-11 17:51:43 UTC,apport information
1819486,2019-03-11 17:51:47 UTC,apport information
1819486,2019-03-11 17:51:53 UTC,apport information
1819488,2019-05-27 21:21:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819488,2019-05-27 21:31:52 UTC,Same problem in 18.04.2  and the super grub disk I had on hand.
1819490,2020-06-25 17:49:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819493,2019-03-11 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819493,2019-05-14 10:58:02 UTC,"The following commits are required for 4.15:
  - 14a627313893 (""i40e: Check and correct speed values for link on open"")
  - 6f0c1b41ae95 (""i40e: Set fec_config when forcing link state"")
  - c3880bd159d4 (""i40e: link_down_on_close private flag support"")"
1819495,2019-03-11 17:31:08 UTC,"For a complete information on applications used to reproduce this issue:
""""""
juju deploy cs:trusty/keystone # vip=XX.XX.XX.10
juju deploy cs:trusty/percona-cluster mysql # vip=XX.XX.XX.11
juju deploy cs:trusty/neutron-api # vip=XX.XX.XX.12 neutron-security-groups=True
juju deploy cs:trusty/hacluster keystone-hacluster # cluster_count=1
juju deploy cs:trusty/hacluster mysql-hacluster # cluster_count=1
juju deploy cs:trusty/hacluster neutron-hacluster # cluster_count=1
juju add-relation keystone keystone-hacluster
juju add-relation mysql mysql-hacluster
juju add-relation neutron-api neutron-hacluster
juju add-relation keystone mysql
juju add-relation neutron-api mysql
juju add-relation neutron-api keystone"
1819495,2019-03-19 13:02:06 UTC,The original [0] implementation details that guarded against this has indeed weathered by subsequent changes to the charm.  It would be pertinent to restore this behavior.
1819504,2019-04-29 09:58:55 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1030.32~16.04.1
1819504,2019-04-29 09:58:18 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1030.32
1819504,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1819504,2019-04-23 21:38:10 UTC,This bug was fixed in the package linux-gcp - 4.18.0-1009.10
1819504,2019-04-04 18:02:30 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1819504,2019-04-04 18:04:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1819504,2019-03-18 16:19:56 UTC,"Note: The Disco 5.0 kernel already carries the required patches, via mainline."
1819504,2019-03-18 16:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819504,2019-03-18 15:41:40 UTC,We have confirmed that the patchwork.kernel.org patch originally requested was not the right one.
1819504,2019-03-12 15:58:46 UTC,"There may be some confusion between the requested patch versus the expected functionality:   The requested patch (https://patchwork.kernel.org/patch/10319623/) adds only a new **configfs** entry called ""reset_netlink"" but the returned test results (below) suggest that the tester was expecting a new **module parameter** called ""reset_netlink"".  I also note that the discussion thread attached to the patchwork patch does mention the idea of doing it as a module parameter, but that idea is apparently rejected in favor of the configfs scheme implemented by the patch.  Is it possible that the tester was originally working with an old version of the patch?"
1819504,2019-04-23 21:35:02 UTC,This bug was fixed in the package linux - 4.18.0-18.19
1819506,2019-07-13 21:10:45 UTC,"Please provide the exact steps one would need to take to reproduce this bug, including the actual monitor layout."
1819506,2019-07-13 23:47:23 UTC,"Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we could close it and convert it to a question in the support tracker."
1819506,2019-09-12 04:17:24 UTC,[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1819511,2019-08-31 10:40:30 UTC,Resolved in Eoan.
1819513,2019-08-08 09:19:16 UTC,in any case fixed in eoan
1819513,2019-08-08 09:19:08 UTC,you need to upgrade init-system-helpers...
1819513,2019-04-17 13:37:19 UTC,Could this affect more packages than the 2 already reported as having problems?
1819513,2019-04-04 05:04:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1819513,2019-03-31 14:35:48 UTC,"Not sure if it the same bug, but I got it with mpd
Errors were encountered while processing:
 mpd
Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an error code (1)"
1819513,2019-03-31 14:34:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819537,2020-10-29 16:11:20 UTC,merged the fix for this into cs:~llama-charmers-next/nagios.
1819537,2020-03-01 23:42:58 UTC,"I'm unable to find a reproducer for this, it's likely either been fixed by an update since the bug was reported, or I need to get some more info on how to demonstrate this issue."
1819537,2020-05-01 04:17:24 UTC,[Expired for Nagios Charm because there has been no activity for 60 days.]
1819537,2020-09-30 19:34:23 UTC,Reproducer:
1819540,2019-03-19 17:05:07 UTC,"Fix is here,"
1819540,2020-04-21 13:47:49 UTC,"Thanks, everyone. I have finally gotten around to pushing this to master, rel_3_5, rel_3_4, and rel_3_3."
1819540,2020-02-14 19:46:08 UTC,"I'm removing the needsdiscussion tag, assigning this bug to John Amundson who will look at it next week, and targeting this bug for 3.3, 3.4, and 3.5 branches."
1819540,2020-02-14 16:00:09 UTC,"+1 to Josh's suggestion, too."
1819540,2020-02-13 23:32:02 UTC,"+1 to Josh's suggestion ""Maybe this should be committed with Steve's fix, and a new bug created for allowing shorter than a day hold shelf expire intervals, since that seems like a new feature, while Steve's fix seems like a bug fix to me."""
1819540,2020-02-13 22:02:39 UTC,"Just in case there is consensus to apply Steve's fix now, here is a signoff branch."
1819540,2020-02-20 19:08:49 UTC,"This is looking good to me on my test server, as well. I'll add my signoff to the mix."
1819540,2020-02-13 20:30:00 UTC,Adding the needsdiscussion tag since it sounds like it may need some fine tuning.
1819540,2019-05-01 14:21:39 UTC,"Hi Steve, and good work finding the place to change."
1819540,2020-02-13 20:40:07 UTC,"Benjamin, it hasn't been targeted since there is still discussion going on about how exactly to solve it."
1819540,2019-11-07 20:23:05 UTC,"EG 3.3.4 - just had this behavior reported today.  The shelf expire report just happened to have been run after the time the pull list items had been checked in 10 days ago.  ""None of these expired holds will clear today Josh!"""
1819540,2020-02-14 15:38:43 UTC,"I also agree with Josh. Fix the bug now, and try to improve it later. Our libraries find this bug quite frustrating."
1819540,2019-11-12 22:33:39 UTC,"I just noticed that the web client - (3.3.4) holds shelf - edit holds dates doesn't allow specifying the exact time, just the day.  So if a location ever does want to use short hold shelf expire intervals, that may need to be adjusted also."
1819540,2020-02-13 18:26:35 UTC,We've rolled out the patch for this for our instance of Evergreen. Is this targeted for any forthcoming versions of Evergreen?
1819540,2019-11-08 18:53:11 UTC,"I think the library setting makes sense here, with the default behavior following the XUL."
1819542,2019-03-12 15:09:00 UTC,Related to bug: https://bugs.launchpad.net/evergreen/+bug/1529969 ?
1819542,2019-06-26 13:38:35 UTC,Related: Bug 1794575
1819542,2019-09-11 17:14:22 UTC,"Adding links to additional bugs which may contribute to the frequency of hanging transits, hence failed checkins:"
1819542,2020-05-22 12:59:56 UTC,"Michele, are you still able to reproduce this?  In Concerto, I checked in CONC90000436 (a BM1 item) at BR1, created a transit, then in the database set the item status to Available and tried checking it in again at BR1, BR2, and BM1, all with no error.  I also checked out a version of EG from from 2019-09 and still could not duplicate the problem."
1819542,2020-05-22 13:16:08 UTC,"Hrmm, but I didn't enforce the status change on the hold transit.  Will revisit."
1819542,2020-06-05 13:16:22 UTC,https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/phasefx/lp1819542-broken-transits
1819542,2020-05-22 14:14:33 UTC,"Jason,"
1819542,2020-05-26 16:25:07 UTC,Thanks John!  I'll give this a shot.
1819542,2020-05-27 12:45:10 UTC,"Interesting.  Per bug 1794575, put item into transit, tried to Mark it Damaged, and get an uncaught exception in the console: TypeError: Cannot read property 'charge' of undefined at circ.js:1375"
1819542,2019-09-11 17:00:57 UTC,"See comments on duplicate bug 1529969, which are more relevant to this bug than the original report."
1819542,2020-06-08 14:50:52 UTC,I want to add that John at CW MARS is also looking at the branch on this bug.
1819542,2020-06-08 17:15:40 UTC,"This code looks good to me, too. I'll add my sign off to the mix."
1819542,2020-07-26 15:02:10 UTC,"Pushed to master, rel_3_5, and rel_3_4.  Thanks, Michele, Jason, Rogan, and John."
1819542,2020-06-05 15:45:09 UTC,sign off at user/rogan/lp1819542_hanging_transits
1819543,2020-11-25 03:05:40 UTC,It affects me in 20.04 LTS. I didn't have it in 18.04 LTS.
1819543,2020-11-12 18:31:03 UTC,"It affects me since I migrated to Ubuntu 20.04 LTS
VLC 3.0.11"
1819543,2020-11-08 15:07:07 UTC,"Affects me on Kubuntu 20.04 in multiple machines. If I close the app via the ""X"" button AND it is playing some media file it gets stuck and I need to give a ""killall -9 vlc"" command. It closes just fine if I stop the media before closing with the ""X"" button. If I quit the app with CTRL+Q or with the close command in the ""media"" menu it exits just fine even if media is playing. Starting the app via command line, panel or by clicking on a file seems to have no effect on this behavior."
1819543,2020-11-05 10:09:23 UTC,"So far when this affects me (20.04) it is when I've opened the media from a file manager or started VLC via the menu.In both cases it uses ""vlc --start-from-file ...""  - if I start vlc on the command-line without that option it seems to quit/terminate correctly and not hang about."
1819543,2020-08-31 01:18:12 UTC,My machine is also suffering with the same issue.
1819543,2020-03-02 17:08:07 UTC,"Same thing still happens in VLC 3.0.8-0-gf350b6b5a7 on Xubuntu 19.10 as of 20200302 .
After playing, for example ""Cloud Atlas"", (Mp4 video) VLC does not exit normally.
(4ea7d873a5a5494ffcf09ccb939a8943e0c5bdcc magnet hash)"
1819543,2020-08-13 04:09:28 UTC,"I thought it was a KDE bug (I use KDE Neon), and this bug is present in VLC in KDE, too."
1819543,2020-07-28 16:10:11 UTC,I'm able to reproduce this bug on Ubuntu 20.04 with an AMD processor.
1819543,2020-07-25 17:07:51 UTC,"Happens to me with all media files. After closing VLC I can't double click another file until I kill VLC. The applet also does nothing.
This does seem to depend on which type of video output I use. Automatic often seems to cause this. VDPAU sometimes seem to cause, and OpenGL also sometimes. It seems to vary with the codec. X11 video output seems to never cause this, but consumes a lot of CPU. XVideo seems to be fine too, less CPU consumption.
Ubuntu MATE 20.04.1"
1819543,2020-04-20 13:58:59 UTC,"Still present in 20.04 (Focal) with vlc 3.0.9.2-1, though here at least it seems to only affect some URLs, not all. When I view a stream from my local webcam, vlc -vvv in the terminal shows"
1819543,2019-11-20 22:11:46 UTC,"This also happens on Ubuntu 19.10 with vlc 3.0.8-2.
Strangely it does close properly if you press Ctrl + Q or do it via ""Media -> Quit""."
1819543,2019-04-19 10:09:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819543,2020-08-19 14:50:11 UTC,"I didn't have this problem until upgrading 20.04, though I also upgraded the video card from HD5000 to R7 when I did. Try setting ""Hardware-accelerated decoding"" to something other than Automatic or VDPAU."
1819554,2019-06-03 22:08:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662867"
1819554,2019-06-12 01:16:02 UTC,"Reviewed:  https://review.opendev.org/662867
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=1745ef2f9317397e5e201d8c902a73ef8d204823
Submitter: Zuul
Branch:    master"
1819558,2019-06-18 13:10:29 UTC,Not going to be SRUed to cosmic which is neither nor a LTS nor the current stable version
1819558,2019-06-05 13:39:28 UTC,"Looks like the issue was fixed in eoan but not mentioned in the changelog of the upload
http://launchpadlibrarian.net/423619607/gnome-software_3.30.6-2ubuntu3_3.30.6-2ubuntu5.diff.gz"
1819560,2020-01-23 14:30:49 UTC,Another data point.  I have this problem on a Raspberry Pi 3B when using Ubuntu Server 18.04.3 LTS.  Problem is not present on the same hardware when using Arch Linux ARMv7.
1819560,2019-11-25 13:02:23 UTC,"pi-zerow stretch, usb audio, same problem.   Since Debian holds the radio transmit open, I've since had to switch to a pcm audio device (fe-pi hat), and stop using usb audio."
1819560,2019-08-16 17:10:04 UTC,The bug still exists on Raspberry Pi Zero and Buster for kernel 4.19.58+ and 4.19.58+ and for even 4.19.66+ (after rpi-update).
1819560,2019-07-17 23:34:25 UTC,Thanks for taking a look at this.
1819560,2019-07-17 13:15:26 UTC,Can someone reproduce this on Buster please?
1819560,2019-06-17 03:19:46 UTC,"Same unexpected, deficient behavior for me as well."
1819560,2020-05-22 20:17:03 UTC,Another data point:-
1819560,2019-05-30 20:49:35 UTC,Same Problem here.
1819560,2019-04-30 22:52:38 UTC,I have the same problem on my Raspberry Pi Zero with Raspbian Stretch Lite (release 2019-04-08). I have to move my project to Orange Pi Zero with Armbian Bionic (mainline based kernel 4.19.y) where the problem doesn't occur.
1819560,2019-04-01 12:06:43 UTC,Raspberry Pi 3 A+ also affected :(
1819560,2019-03-25 15:52:55 UTC,"Same here, up to a full second of delay before audio starts, happens at random.  Roughly one third of all starts have the delay.  Using cmedia USB audio dongle.  Raspberry Pi3,  Stretch image dated 11/13/18."
1819560,2019-03-19 13:58:30 UTC,Same problem here.
1819560,2019-03-19 13:49:22 UTC,I've got the same problem. Please help.
1819560,2019-03-19 06:21:35 UTC,I have a similar problem. I can not finish my raspberry pi project zero because of this.
1819560,2019-06-04 15:07:03 UTC,I can confirm that I'm experiencing the same issue on a Pi Zero and the 3B+. Multiple USB audio devices have been tested and everything is up-to-date in regards to what's available on the Raspbian repos for the two devices.
1819561,2019-03-12 15:38:47 UTC,"Thank you for your bug report. Unfortunately, you have not provided enough information to be able to investigate this issue. Please provide:"
1819561,2019-05-12 04:17:33 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1819563,2019-03-12 15:38:06 UTC,"Thank you for your bug report. Unfortunately, you have not provided enough information to be able to investigate this issue. Please provide:"
1819563,2019-05-12 04:17:32 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1819569,2020-05-25 04:17:17 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1819569,2019-03-14 21:16:48 UTC,Should probably ask mdbooth and/or lyarwood about this since I feel like they have fixed something like this before.
1819569,2020-03-25 11:45:36 UTC,Are you still seeing this?
1819569,2019-05-13 19:25:10 UTC,I see this issue with the Dell EMC SC driver as well. Seems like an issue not related to the driver
1819572,2019-03-12 15:24:27 UTC,I'm untargetting the specific releases so that this doesn't show up in our weekly reports.  I would like to see some more debugging and to better understand why it's just this one machine.  It doesn't yet sound like this is a release critical bug.
1819572,2020-01-25 15:35:16 UTC,"Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1819572,2020-03-26 04:17:22 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1819572,2020-03-26 04:17:24 UTC,[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]
1819573,2019-08-09 19:10:19 UTC,"This will be fixed when https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/45 and all of its dependencies are reviewed, merged, and released."
1819573,2019-08-12 16:12:51 UTC,"In addition to #1 and #2, the linked PR(s) significantly simplifies the installation story by using relations to manage the scraper jobs and dashboards.  See updated instructions in https://github.com/charmed-kubernetes/kubernetes-docs/pull/247"
1819573,2019-03-12 05:11:55 UTC,See https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/687#issuecomment-438202521 for context on when certain endpoints need to be exposed.
1819577,2019-03-12 09:01:54 UTC,"It would have been great to share a bit of more of details related to the issue. My thinking is that your patch can't work in case of multipath usage since the devices are not registered anymore in sysfs. But it's just one potential issue, it may have others."
1819577,2019-03-12 09:58:01 UTC,"Thanks Sahid.  Right now the goal is to revert the patch since a new version of os-brick was just released and this is broken, and we need a low-risk fix (revert).  After that we should definitely try to fix it."
1819577,2019-03-12 17:39:28 UTC,"Reviewed:  https://review.openstack.org/642648
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=6adbce5ef7f1af3d62a9ef145baa13730f16fb87
Submitter: Zuul
Branch:    master"
1819577,2019-06-26 16:35:12 UTC,"Avishay,"
1819581,2019-03-12 15:37:56 UTC,"Sorry, I don't understand what the issue is based on your summary. Could you please elaborate?"
1819581,2019-03-12 07:55:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642675"
1819581,2019-05-28 03:27:37 UTC,"Change abandoned by Ying Wang (<email address hidden>) on branch: master
Review: https://review.opendev.org/642675"
1819588,2019-03-13 12:33:07 UTC,Thank you for the report.
1819588,2019-05-13 04:17:17 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1819591,2019-03-13 02:41:00 UTC,i looked at the code but failed to find the implementation.
1819591,2019-03-13 07:39:37 UTC,This part of the function has not been completed yet. I think we can start the discussion and set a date to finish it.
1819593,2019-08-27 10:58:09 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678790"
1819593,2019-08-28 06:46:49 UTC,"2019-08-28 06:24:28 INFO juju-log Invoking reactive handler: reactive/octavia_handlers.py:89:setup_hm_port
2019-08-28 06:24:33 ERROR juju-log Hook error:
Traceback (most recent call last):
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/charms/reactive/__init__.py"", line 74, in main
    bus.dispatch(restricted=restricted_mode)
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/charms/reactive/bus.py"", line 390, in dispatch
    _invoke(other_handlers)
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/charms/reactive/bus.py"", line 359, in _invoke
    handler.invoke()
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/charms/reactive/bus.py"", line 181, in invoke
    self._action(*args)
  File ""/var/lib/juju/agents/unit-octavia-2/charm/reactive/octavia_handlers.py"", line 107, in setup_hm_port
    octavia_charm):
  File ""lib/charm/openstack/api_crud.py"", line 298, in setup_hm_port
    octavia_charm.local_address)
  File ""lib/charm/openstack/api_crud.py"", line 163, in get_hm_port
    resp = nc.list_networks(tags='charm-octavia')
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/neutronclient/v2_0/client.py"", line 818, in list_networks
    **_params)
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/neutronclient/v2_0/client.py"", line 369, in list
    for r in self._pagination(collection, path, **params):
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/neutronclient/v2_0/client.py"", line 384, in _pagination
    res = self.get(path, params=params)
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/neutronclient/v2_0/client.py"", line 354, in get
    headers=headers, params=params)
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/neutronclient/v2_0/client.py"", line 331, in retry_request
    headers=headers, params=params)
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/neutronclient/v2_0/client.py"", line 294, in do_request
    self._handle_fault_response(status_code, replybody, resp)
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/neutronclient/v2_0/client.py"", line 269, in _handle_fault_response
    exception_handler_v20(status_code, error_body)
  File ""/var/lib/juju/agents/unit-octavia-2/.venv/lib/python3.6/site-packages/neutronclient/v2_0/client.py"", line 93, in exception_handler_v20
    request_ids=request_ids)
neutronclient.common.exceptions.NeutronClientException: <!DOCTYPE HTML PUBLIC ""-//IETF//DTD HTML 2.0//EN"">
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request <em><a href=""/v2.0/networks"">GET&nbsp;/v2.0/networks</a></em>.<p>
Reason: <strong>Error reading from remote server</strong></p></p>
<hr>
<address>Apache/2.4.29 (Ubuntu) Server at 172.17.111.28 Port 9696</address>
</body></html>"
1819593,2020-01-16 16:32:08 UTC,"Reviewed:  https://review.opendev.org/678790
Committed: https://git.openstack.org/cgit/openstack/charm-octavia/commit/?id=15e56091b2e2b1b1794e37697235f4313841c845
Submitter: Zuul
Branch:    master"
1819595,2019-03-12 10:30:17 UTC,"Fixed in revision 23086deccdf91ab55fa762f5b4b991efe0ccd5ec
https://git.launchpad.net/kicad/patch/?id=23086deccdf91ab55fa762f5b4b991efe0ccd5ec"
1819615,2019-03-12 20:16:13 UTC,debdiff for modemmanager 1.10 in Bionic. The upstream source tarball is the same as for Disco.
1819615,2019-03-12 18:12:55 UTC,Added tasks for libmbim and libqmi as their current versions are needed by ModemManeger 1.10.
1819615,2019-05-14 08:45:24 UTC,"The network-manager SRU 1.10.14-0ubuntu2 is in -updates now and the autopkg test got successfully repeated with it, so this SRU can be tranferred to -updates, too."
1819615,2019-05-06 10:19:24 UTC,"yparitcher, thank you very much for your fix. We will add it to the SRU of the modemmanager package and also apply it to eoan. Please watch out this bug report for a new verification call.
To the SRU team: The regression of the modemmanager SRU is fixed and I will soon put up a new debdiff for upload. The two libraries (libmbim and libqmi) did not cause any regression. Please do not remove them from -proposed as they are still needed for the modemmanager SRU.
yparitcher, could you open a Launchpad bug report for your regression/fix for eoan and SRUs on disco and cosmic? Thanks."
1819615,2019-05-06 14:00:48 UTC,debdiff to fix the regression in eoan.
1819615,2019-05-06 14:27:17 UTC,debdiff for the full SRU for Bionic: Upgrade to 1.10 plus regression fix.
1819615,2019-05-06 18:16:05 UTC,"how do i open an sru for cosmic?, it looks like you took care of disco and eon already."
1819615,2019-05-07 07:17:11 UTC,"yparitcher, simply report a new bug describing the regression and in which Ubuntu/ModemManager versions you have found it. We will add the rest to make an SRU bug report out of it. Post a link to your bug report here. Thanks."
1819615,2019-05-07 16:19:20 UTC,This bug was fixed in the package modemmanager - 1.10.0-1ubuntu1
1819615,2019-05-07 16:40:01 UTC,"Hello Till, or anyone else affected,"
1819615,2019-05-07 18:31:37 UTC,"added bug for cosmic & disco
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102"
1819615,2019-05-07 19:34:54 UTC,"yparitcher, first, thanks for reporting bug 1828102, we need this separate bug as Cosmic and Disco originally came with ModemManager 1.10 and so did not suffer the bug treated here, only the regression which you have found. Eoan I have already treated here as the SRU team requires that the issues which are fixed by an SRU are also fixed in the current development cycle."
1819615,2019-05-07 19:38:09 UTC,"Alex Tu, please test the new packages in bionic-proposed whether they correctly support the modems for which you asked for support for. Thanks."
1819615,2019-05-07 21:02:56 UTC,regression fixed in 1.10.0-1~ubuntu18.04.2
1819615,2019-05-06 00:53:44 UTC,"found a fix upstream, was a issue in error propagation.
attached is a patch for ModemManager 1.10 in Bionic / Dingo, and 1.8.2 in Cosmic"
1819615,2019-05-08 09:29:48 UTC,Test passed by using the modemmanager 1.10.0-1~ubuntu18.04.2 with the related libmbim and libqmi library.
1819615,2019-05-08 13:37:41 UTC,"Robie, what do you mean with dep8 regression? The only mention of ModemManager on https://people.canonical.com/~ubuntu-archive/pending-sru.html is this bug report here. The regression reported by yparitcher got fixed upstream and the SRU re-posted with this fix. This is the version currently verified in comments #42 and #43."
1819615,2019-05-08 17:50:02 UTC,"On Wed, May 08, 2019 at 01:37:41PM -0000, Till Kamppeter wrote:

> Robie, what do you mean with dep8 regression? The only mention of
> ModemManager on https://people.canonical.com/~ubuntu-archive/pending-
> sru.html is this bug report here. The regression reported by yparitcher
> got fixed upstream and the SRU re-posted with this fix. This is the
> version currently verified in comments #42 and #43.
"
1819615,2019-05-09 11:31:15 UTC,This autopkg test failure does not look much as induced by ModemManager. Could someone with appropriate right re-initiate it? Thanks.
1819615,2019-05-10 13:45:55 UTC,The autopkg test failure is now fixed in the network-manager SRU 1.10.14-0ubuntu2.
1819615,2019-05-15 01:56:00 UTC,"Gah. Sorry about not picking this up on my first pass through, but what's happening with Cosmic here? As far as I can tell, this also applies to Cosmic (but not Disco), and Cosmic is still supported for a couple of months (long enough that I'm hesitant to go “sure, we don't need to worry about it”)."
1819615,2019-05-15 11:56:12 UTC,"@roaf:  This was driven by an OEM request, so the priority was bionic.  We also needed to make sure disco (and later) was covered to ensure we made the next LTS as well."
1819615,2019-05-16 09:56:07 UTC,"We should think about cosmic indeed, but it's not really blocking the release for bionic. Currently upgrades from bionic to cosmic will very very very rare. With disco released, there's no 'official' upgrade path - not to mention bionic users by default should be only informed of new LTS versions. So I'll proceed with getting this out."
1819615,2019-05-16 09:58:46 UTC,This bug was fixed in the package modemmanager - 1.10.0-1~ubuntu18.04.2
1819615,2019-05-16 09:58:52 UTC,"The verification of the Stable Release Update for modemmanager has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819615,2019-05-16 09:58:57 UTC,This bug was fixed in the package libqmi - 1.22.0-1.2~ubuntu18.04.1
1819615,2019-05-16 09:58:59 UTC,This bug was fixed in the package libmbim - 1.18.0-1~ubuntu18.04.1
1819615,2019-05-08 12:11:39 UTC,"> Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised.
"
1819615,2019-05-01 18:33:09 UTC,"yparitcher, thank you for the upstream bug report. As soon as upstream finds a (backportable) solution we will add it to this SRU and report back here."
1819615,2019-05-06 14:18:23 UTC,debdiff to update the Bionic SRU to fix the regression.
1819615,2019-05-01 01:28:59 UTC,Marking as verification-failed as per the last couple of comments.
1819615,2019-03-12 20:17:54 UTC,debdiff for libmbim 1.18.0 in Bionic. The upstream source tarball is the same as for Disco.
1819615,2019-03-12 20:20:21 UTC,debdiff for libqmi 1.22.0 in Bionic. The upstream source tarball is the same as for Disco.
1819615,2019-03-12 20:23:54 UTC,I have made Bionic packages for ModemManager 1.10 and the needed libraries now. I have attached the debdiffs and the upstream tarballs are the same as of the Disco packages.
1819615,2019-03-20 13:49:47 UTC,Replacement for the debdiff for libqmi 1.22.0 in Bionic.
1819615,2019-03-20 17:07:44 UTC,"Yuan-Chen, Alex: I have finished to prepare the three needed packages, including a fix on libqmi coming in yesterday. Now I am simply waiting for the upload of the packages getting sponsored (probably by Ken VanDine) and the SRU team putting the packages into bionic-proposed."
1819615,2019-03-20 18:46:04 UTC,The libqmi debdiff doesn't include the latest version that's in bionic (1.18.0-3ubuntu1) in the changelog and it also reverts the change in that version.  Please ensure the debdiff is against that version.
1819615,2019-03-20 18:47:26 UTC,The libmbim debdiff doesn't include the latest version that's in bionic (1.14.2-2.1ubuntu1) in the changelog and it also reverts the change in that version. Please ensure the debdiff is against that version.
1819615,2019-03-20 19:24:55 UTC,Fixed libqmi package.
1819615,2019-05-01 06:34:28 UTC,"regression submitted upstream see https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
for further details"
1819615,2019-03-20 20:14:47 UTC,Fixed modemmanager package.
1819615,2019-03-20 20:21:51 UTC,"Hello, I'm probably impacted by this bug here : https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1821052"
1819615,2019-03-21 01:39:27 UTC,"@Till, Add DW5821 which also need new mm to support. I'll test both here as it hit the proposed channel."
1819615,2019-03-20 19:49:29 UTC,Fixed libmbim package.
1819615,2019-04-23 14:58:58 UTC,"Hello Till, or anyone else affected,"
1819615,2019-04-23 15:16:38 UTC,"Hello Till, or anyone else affected,"
1819615,2019-04-23 15:19:09 UTC,"Hello Till, or anyone else affected,"
1819615,2019-04-26 03:14:50 UTC,"per test in bionic, turn on proposed channel, do a 'apt install modemmanager'. it will upgrade to version 1.10.0-1~ubuntu18.04.1 and also upgrade related libmbim and libqmi library."
1819615,2019-04-30 19:29:51 UTC,What's going on with the network-manager arm64 autopkgtest failure with the new modem-manager?
1819615,2019-04-30 19:42:06 UTC,"Brian, do you have some link (bug report, ...) to this failure?"
1819615,2019-04-30 20:01:36 UTC,"I would like to report a regression.
i have a verizon samsung phone using as a bluetooth CDMA/3G modem.
after the upgrade modemmanager disconnects ~30sec after connecting."
1819615,2019-04-30 20:03:43 UTC,"i am very happy to try any fixes helping to try different versions to see where the regression was introduced.
thanks."
1819615,2019-04-30 20:25:49 UTC,"yparitcher, as this SRU consists of three packages, ModemManager itself and the two libraries, try at first to downgrade only modemmanager to the original. If this solves the problem, it is caused by modemmanager, if not, downgrade one of the libraries, then try to downgrade the other, ... until you could spot one of the three packages having caused your problem."
1819615,2019-03-21 17:33:09 UTC,I've sponsored these packages
1819615,2019-04-30 20:50:15 UTC,"i downgraded ModemManager back to 1.6.8-2ubuntu1 and the problem went away, so it is caused by ModemManager."
1819615,2019-04-30 21:35:27 UTC,1.8.2-1 from cosmic also has this regression
1819616,2019-03-28 22:12:59 UTC,tests complete
1819616,2019-04-02 12:02:20 UTC,All tasks have been completed and the bug is being set to Fix Released
1819625,2019-03-13 22:38:03 UTC,"@ddstreet:

> are you upstream nameservers not reachable from your system?


upstream servers have no clue about local LXC/LXD (linuxcontainers.org) DNS names.
Configuration basically done via"
1819625,2019-03-14 15:02:12 UTC,This bug was fixed in the package resolvconf - 1.79ubuntu10.18.10.2
1819625,2019-03-13 21:44:13 UTC,"Hello Boris, or anyone else affected,"
1819625,2019-03-14 23:40:31 UTC,This bug was fixed in the package resolvconf - 1.79ubuntu10.18.04.2
1819625,2019-10-08 10:41:15 UTC,I'm experiencing this issue with Ubuntu 19.04
1819625,2019-03-14 21:10:59 UTC,I had troubles with DNS resolution in last days after reboot and I think it may be related to resolvconf package update. I spotted following entries in resolvconf-pull-resolved.service journal:
1819625,2019-03-13 21:33:16 UTC,"Hello Boris, or anyone else affected,"
1819625,2019-03-13 05:04:01 UTC,"For the affected, a workaround is available:
Download and manually install resolveconf from the previous version-1.79ubuntu10"
1819625,2019-03-13 20:46:23 UTC,@bruno-42 are you upstream nameservers not reachable from your system?
1819625,2019-03-13 13:36:09 UTC,No vpn - DNS resolver broken by update (on production server)
1819625,2019-03-13 04:28:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819625,2019-03-13 04:27:16 UTC,"Can confirm.  Specifically breaks DNS resolution in Firefox when I'm logged into an OpenConnect VPN.  I can resolve hosts that are in public DNS, but I'm uncertain if this is because of caching.  Internal DNS over the VPN no longer resolves.  Downgrading to the previous version of resolvconf restores functionality."
1819625,2019-03-13 21:25:00 UTC,"On a desktop system continuously upgraded from pre-xenial (through non-LTS releases), I have the following before upgrade:"
1819627,2019-04-18 15:34:05 UTC,We have experienced this again on AWS/Bionic 4.15 kernel..  c4/c5.large  m4.large/m5.xlarge
1819628,2019-03-12 13:26:13 UTC,This is an error across all of the UI. This is because the API returns a json string but the error handling on the UI doesn't deal with that correctly.
1819628,2019-05-08 14:04:18 UTC,"The errors come back to the UI as either a string or a JSON string so it's unpredictable, and in the case that it is a JSON string the format is inconsistent e.g. `__relay__` as a key in one case, `__all__` in another as examples."
1819632,2019-04-11 17:30:47 UTC,in fact my theory on this one is that we are missing https://review.rdoproject.org/r/#/c/20152/ and you already have https://review.openstack.org/#/c/650985/ in stein.
1819632,2019-04-11 16:43:25 UTC,"Reopening as the commit says it was not fixed. Also, seeing similar (if not the same) error when we switched to buildah...
https://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-infra/tripleo-ci/master/periodic-tripleo-ci-centos-7-scenario001-standalone-stein/4bf87d6/logs/undercloud/home/zuul/standalone_deploy.log.txt.gz#_2019-04-11_15_38_24"
1819632,2019-03-12 19:13:54 UTC,"Reviewed:  https://review.openstack.org/642741
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=d6abcac8dca1e57f1cede2a16359bcd9db857dca
Submitter: Zuul
Branch:    master"
1819632,2019-03-12 13:02:05 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/642741"
1819632,2019-04-11 17:15:18 UTC,"Do you have https://review.openstack.org/#/c/650985/ ? If no, then it's not good. You need this patch with latest buildah/podman."
1819632,2019-03-12 12:11:52 UTC,The real error is here:
1819632,2019-03-12 12:08:32 UTC,"It looks like the nova-libvirt container was pushed with some errors:
http://logs.openstack.org/90/583890/5/gate/tripleo-ci-centos-7-scenario004-standalone/fac9d52/logs/undercloud/var/log/tripleo-container-image-prepare.log.txt.gz?level=ERROR#_2019-03-11_23_29_12_505"
1819632,2019-03-12 12:14:21 UTC,So 2 things:
1819640,2019-03-12 16:28:58 UTC,"> Setting up grub-efi-amd64-signed (1.66.20+2.02~beta2-36ubuntu3.20) ...
> Installing for x86_64-efi platform.
> grub-install: error: cannot find EFI directory.
"
1819640,2019-05-12 04:17:33 UTC,[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]
1819650,2019-03-14 20:10:21 UTC,"I recompiled again, from buster package source, without debug.
I cannot reproduce the bug..."
1819650,2019-03-14 20:51:08 UTC,"I succeed in compiling 1.16.3 on my x64 computer, with ASAN.
Here is valgrind result:"
1819650,2019-03-15 22:01:49 UTC,"pi@raspberrypi:~/dtv-scan-tables/dvb-t $ valgrind dvbv5-zap -c dvb_channel.conf -v --lna=-1 'CBBC' -P -o - > /dev/null
==2702== Memcheck, a memory error detector
==2702== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2702== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==2702== Command: dvbv5-zap -c dvb_channel.conf -v --lna=-1 CBBC -P -o -
==2702==
using demux 'dvb0.demux0'
reading channels from file 'dvb_channel.conf'
service has pid type 05:  7103
tuning to 490000000 Hz
pass all PID's to TS
  dvb_set_pesfilter 8192
==2702== Warning: noted but unhandled ioctl 0x6f2d with no size/direction hints.
==2702==    This could cause spurious value errors to appear.
==2702==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
Lock   (0x1f) Quality= Good Signal= -45.74dBm C/N= 0.12dB UCB= 30 postBER= 2.93Lock   (0x1f) Quality= Good Signal= -46.07dBm C/N= 0.12dB UCB= 30 postBER= 0 PER= 43.9x10^-6
Lock   (0x1f) Quality= Good Signal= -46.03dBm C/N= 0.12dB UCB= 30 postBER= 0 PER= 43.9x10^-6
Record to file '-' started
^Creceived 28375404 bytes
Lock   (0x1f) Quality= Poor Signal= -46.11dBm C/N= 0.03dB UCB= 4294967266 postBER= 0 PER= 33.7x10^3
==2702== Invalid free() / delete / delete[] / realloc()
==2702==    at 0x4848B8C: free (vg_replace_malloc.c:530)
==2702==    by 0x491A717: free_dvb_dev (in /usr/lib/arm-linux-gnueabihf/libdvbv5.so.0.0.0)
==2702==  Address 0x4b7d248 is 0 bytes inside a block of size 28 free'd
==2702==    at 0x4848B8C: free (vg_replace_malloc.c:530)
==2702==    by 0x491C7B7: dvb_v5_free (in /usr/lib/arm-linux-gnueabihf/libdvbv5.so.0.0.0)
==2702==  Block was alloc'd at
==2702==    at 0x4847568: malloc (vg_replace_malloc.c:299)
==2702==    by 0x49E6933: strdup (strdup.c:42)
==2702==    by 0x491BDD3: ??? (in /usr/lib/arm-linux-gnueabihf/libdvbv5.so.0.0.0)
==2702==
==2702==
==2702== HEAP SUMMARY:
==2702==     in use at exit: 8,194 bytes in 3 blocks
==2702==   total heap usage: 1,407 allocs, 1,405 frees, 997,100 bytes allocated
==2702==
==2702== LEAK SUMMARY:
==2702==    definitely lost: 2 bytes in 1 blocks
==2702==    indirectly lost: 0 bytes in 0 blocks
==2702==      possibly lost: 0 bytes in 0 blocks
==2702==    still reachable: 8,192 bytes in 2 blocks
==2702==         suppressed: 0 bytes in 0 blocks
==2702== Rerun with --leak-check=full to see details of leaked memory
==2702==
==2702== For counts of detected and suppressed errors, rerun with: -v
==2702== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 6 from 3)"
1819650,2019-03-15 22:33:23 UTC,Looks like commit 6e21f6f34c1d7c3a7a059062e1ddd9705c984e2c fixed it.
1819650,2019-03-16 13:05:28 UTC,"Hi Sean,
thanks for your feedback.
Did you also reproduce random hangs?"
1819650,2019-03-17 16:35:37 UTC,"Hello Gregor,"
1819650,2019-03-17 15:50:18 UTC,"Sami, once I'm happy with the patches I'll file a request with the Debian release team to accept the patched for Debian Stretch."
1819650,2019-03-17 16:55:47 UTC,"Hi guys,
thanks for your help!"
1819650,2019-03-19 18:30:37 UTC,Hi!
1819650,2019-03-28 18:50:53 UTC,"There are still random hangs cases, the discussion is ongoing there: https://<email address hidden>/msg145702.html"
1819650,2019-03-14 07:25:05 UTC,"Well, event if the debug build wasn't producing errors, the:
while true;do timeout 10 dvbv5-zap -c channels.conf -v --lna=-1 'TF1' -P -o - > /dev/null;done"
1819650,2019-03-17 15:47:36 UTC,"Hello Sean,"
1819650,2019-03-13 22:28:12 UTC,"I recompile, but from buster package source, with:
DEB_BUILD_OPTIONS='nostrip noopt debug' dpkg-buildpackage -uc -us"
1819650,2019-03-15 22:27:02 UTC,"The invalid free seems to occur AFTER the ^C or when timeout sends a signal. So the issue is on shutdown, so it does not affect functionality of dvbv5-zap."
1819650,2019-03-13 21:18:28 UTC,"I was able to rebuild the debian package:
Add sources to /etc/apt/sources.list
sudo apt update
apt-get source dvb-tools
sudo apt-get build-dep dvb-tools
cd v4l-utils-1.12.3/
sudo apt-get install devscripts build-essential lintian
debuild -us -uc
cd ..
sudo apt purge dvb-tools
sudo apt autoremove
sudo dpkg -i libdvbv5-0_1.12.3-1_armhf.deb
sudo dpkg -i dvb-tools_1.12.3-1_armhf.deb"
1819650,2019-03-12 15:05:07 UTC,Thanks for your report. Would you be able to compile v4l-utils by yourself with address sanitiser enabled? That might give the upstream author(s) a better idea of what went wrong. It might even show you something on x86/64.
1819650,2019-03-13 22:00:31 UTC,"I also compiled with:
DEB_BUILD_OPTIONS='nostrip noopt debug' dpkg-buildpackage -uc -us"
1819650,2019-03-12 20:30:30 UTC,"I also tried a
$ valgrind --leak-check=full --show-leak-kinds=all dvbv5-scan"
1819650,2019-03-12 20:59:59 UTC,"I recompiled from v4l-utils-1.16.3 tag, with CFLAGS=""-g"" LDFLAGS=""-g"" CXXFLAGS=""-g -fsanitize=address"" ./configure --enable-static --disable-shared, and couldn't reproduce the issue"
1819650,2019-03-12 21:46:04 UTC,"I recompiled from v4l-utils-1.16.3 tag with a plain old ./configure, no specific flags, and I cannot reproduce the problem."
1819650,2019-03-13 10:39:42 UTC,Could you please try clang as a compiler?
1819650,2019-03-12 20:15:07 UTC,"Hi,"
1819650,2019-03-13 18:13:34 UTC,"Hi,"
1819650,2019-03-13 18:55:05 UTC,If you run make -k it should continue as far as it can.
1819650,2019-03-13 19:08:17 UTC,"The code does not compile because it uses nested functions, something clang does not support:"
1819650,2019-03-13 20:54:25 UTC,"The build still fails but after compiling dvbv5-zap.
So I could test and I cannot reproduce the issue (like with my own builds with gcc)..."
1819650,2019-03-13 10:48:28 UTC,If you're able to find the raspbian build logs you could have a look at the build flags. Debian ones are here: https://buildd.debian.org/status/package.php?p=v4l-utils
1819661,2019-03-12 20:56:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1819661,2019-05-12 04:17:35 UTC,[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.]
1819662,2019-03-26 11:40:44 UTC,"3.13.0-168.218~precise1 - generic
Regression test CMPL, RTB."
1819662,2019-04-02 11:01:35 UTC,All tasks have been completed and the bug is being set to Fix Released
1819672,2019-12-12 10:13:29 UTC,This issue was fixed in the openstack/python-tripleoclient 11.5.2 release.
1819672,2019-10-09 19:56:16 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/687661"
1819672,2019-10-15 16:18:34 UTC,This issue was fixed in the openstack/python-tripleoclient 12.3.0 release.
1819672,2019-10-12 04:42:07 UTC,"Reviewed:  https://review.opendev.org/687662
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=fa98192ac48cf463a16fddf8498c7e1f328060d9
Submitter: Zuul
Branch:    stable/queens"
1819672,2019-10-12 04:41:58 UTC,"Reviewed:  https://review.opendev.org/687661
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=58a8a0bd4e6f7fbdf4b3789e7c9958c1781bb4b0
Submitter: Zuul
Branch:    stable/rocky"
1819672,2019-10-09 19:58:37 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/687662"
1819672,2019-10-09 19:54:14 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/687659"
1819672,2019-10-12 04:41:49 UTC,"Reviewed:  https://review.opendev.org/687659
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=134f0716218e395e462e69e5ac1ca15782431e91
Submitter: Zuul
Branch:    stable/stein"
1819672,2019-09-17 16:14:24 UTC,"@nico.auv thank you for your comment. It helps indeed to run (with single quotes)
openstack workflow execution create tripleo.plan_management.v1.update_deployment_plan '{""container"": ""overcloud""}'"
1819672,2019-03-12 14:01:04 UTC,env: host with Python 3
1819672,2019-03-12 15:54:17 UTC,Yea this happens on py2 envs too. It's been doing this for a while but we haven't tracked down why. If you use 'openstack overcloud delete <stack>' it'll cleanup the plan as well as the stack
1819672,2019-05-13 14:44:45 UTC,We also see this error. Our command is:
1819672,2019-10-09 19:39:41 UTC,"Reviewed:  https://review.opendev.org/686202
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=72850060e058274bb55aadbf2963f4f46ba3be3a
Submitter: Zuul
Branch:    master"
1819672,2019-09-06 18:48:08 UTC,  I have the same problem while trying to upgrade from Rocky to Stein (openstack overcloud update prepare). Is there a workaround until the bug is fixed? It's being open since March...
1819672,2019-09-17 09:18:20 UTC,@anta-nok I don't know if it would help but I encountered the same issue with OSP13 due to a involontary stack update cancellation. I was able to perform stack updates again after executing this Mistral workflow :
1819688,2020-07-08 17:21:49 UTC,This is verified with new procedure on wcp69-70 with 2020-06-27_18-35-20 load.
1819688,2020-05-22 11:47:53 UTC,"Reviewed:  https://review.opendev.org/729812
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=539d476456277c22d0dcbc3cbbc832e623242264
Submitter: Zuul
Branch:    f/centos8"
1819688,2020-05-21 13:33:23 UTC,"Reviewed:  https://review.opendev.org/729825
Committed: https://git.openstack.org/cgit/starlingx/stx-puppet/commit/?id=d4617fbad74a05f2af81ee85a47565083991e6f8
Submitter: Zuul
Branch:    f/centos8"
1819688,2020-05-21 13:29:36 UTC,"Reviewed:  https://review.opendev.org/729817
Committed: https://git.openstack.org/cgit/starlingx/fault/commit/?id=f21b937b2565fa3f8651d4d72d47a18677959b20
Submitter: Zuul
Branch:    f/centos8"
1819688,2020-05-21 02:32:07 UTC,"Fix proposed to branch: f/centos8
Review: https://review.opendev.org/729825"
1819688,2020-05-21 02:09:39 UTC,"Fix proposed to branch: f/centos8
Review: https://review.opendev.org/729817"
1819688,2020-05-19 15:30:51 UTC,"Reviewed:  https://review.opendev.org/724291
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=491cca42ed854d2cb3ee3646b93c56a4f45f563c
Submitter: Zuul
Branch:    master"
1819688,2020-05-19 15:26:22 UTC,"Reviewed:  https://review.opendev.org/724270
Committed: https://git.openstack.org/cgit/starlingx/stx-puppet/commit/?id=04a3cb8cbad9b1700286c5de67aa5d974cf54400
Submitter: Zuul
Branch:    master"
1819688,2020-04-29 16:06:46 UTC,"Reviewed:  https://review.opendev.org/714939
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=8099bbbbcf6e67190dc2ede949c47da081317e2d
Submitter: Zuul
Branch:    master"
1819688,2020-04-29 15:49:56 UTC,"Reviewed:  https://review.opendev.org/714936
Committed: https://git.openstack.org/cgit/starlingx/stx-puppet/commit/?id=4107faed7e3466cba6fe7b6867152c91c869105b
Submitter: Zuul
Branch:    master"
1819688,2020-05-21 02:00:44 UTC,"Fix proposed to branch: f/centos8
Review: https://review.opendev.org/729812"
1819688,2020-04-29 11:34:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/724288"
1819688,2020-04-29 11:48:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/724291"
1819688,2019-03-15 18:55:52 UTC,"Marking as release gating; related to containers.
Assigning to Brent as this needs an architectural decision. This is likely an issue for any large images."
1819688,2019-07-23 17:44:43 UTC,"This issue occurred because the qcow image needs to be converted to raw and this is done via the glance/cinder containers and this is done using the docker_lv filesystem.  In the past couple of months the docker_lv filesystem was increased to 30G so this specific TC will now pass.  However glance images of larger sizes won't work and by using the docker_lv system, the I/O performance of all containers will be impacted when the conversion is done."
1819688,2019-07-23 17:46:52 UTC,Assigning to Kristine to implement in stx.3.0 as Kristine has experience with filesystems for StarlingX/containers.
1819688,2019-08-06 15:37:53 UTC,Updated the title to reflect the more generic issue.
1819688,2020-05-19 15:26:38 UTC,"Reviewed:  https://review.opendev.org/724288
Committed: https://git.openstack.org/cgit/starlingx/fault/commit/?id=bef81593f094f51d6f6ca3a577b7472a938414b8
Submitter: Zuul
Branch:    master"
1819688,2020-03-05 14:14:45 UTC,Re-assigning to Elena to implement a solution
1819688,2020-04-29 09:42:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/724270"
1819688,2019-11-25 16:25:53 UTC,This is more an enhancement request than a bug.  As such it will not gate stx.3.0.  Re-tagging to stx.4.0.
1819689,2019-04-22 20:22:57 UTC,"Hi, Joe. I'm including the patch for 4.15. Let me know if you find any issues on the test kernel."
1819689,2019-04-22 20:32:43 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100272.html
1819689,2019-05-09 20:55:47 UTC,"It was found that 4.15 has a couple more patches missing for NVMe, those patches are required to get to the target number of IOPS."
1819689,2019-05-09 20:57:16 UTC,"If it would be best, I can open a new bug for those two additional commits."
1819689,2019-05-14 19:04:29 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18
1819689,2019-05-14 19:09:49 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49
1819689,2019-05-14 19:52:13 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
1819689,2019-05-14 22:56:59 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819689,2019-04-18 20:26:45 UTC,"Hi, Joe."
1819700,2019-03-15 14:27:07 UTC,I'm working on a fix for this at https://review.openstack.org/#/c/643593/
1819700,2019-03-12 15:37:11 UTC,This bug is replacing https://bugs.launchpad.net/charm-swift-storage/+bug/1796651 as the linked one follows a dangerous precedent
1819706,2019-12-12 10:08:03 UTC,This issue was fixed in the openstack/cinderlib 1.0.0 release.
1819706,2019-08-31 23:42:49 UTC,"Reviewed:  https://review.opendev.org/643016
Committed: https://git.openstack.org/cgit/openstack/cinderlib/commit/?id=1e52ad632fb863eb93cc4208ffff3ae338328872
Submitter: Zuul
Branch:    master"
1819706,2019-03-13 11:40:52 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/643016"
1819710,2019-04-02 13:50:09 UTC,"This is a -meta only release, master kernel (bug 1819713) already promoted to -updates. Setting stakeholder-signoff to 'Fix Released'."
1819710,2019-04-02 15:03:34 UTC,All tasks have been completed and the bug is being set to Fix Released
1819714,2019-03-29 10:56:52 UTC,"4.15.0-47.50~16.04.1 - lowlatency
Regression test CMPL, RTB."
1819714,2019-04-02 11:06:49 UTC,All tasks have been completed and the bug is being set to Fix Released
1819721,2019-04-16 16:31:03 UTC,This bug was fixed in the package tomcat8 - 8.5.39-1ubuntu1~18.04.1
1819721,2019-04-10 17:04:47 UTC,"Hello Matthias, or anyone else affected,"
1819721,2019-04-10 17:02:07 UTC,"Hello Matthias, or anyone else affected,"
1819721,2019-04-10 11:33:43 UTC,"Steve, thank you, that sounds great from our perspective!"
1819721,2019-04-09 22:25:00 UTC,"based on discussion with Tiago this afternoon, I understand we have agreement to revert the addition of the systemd unit in this SRU in order to maximize compatibility with existing local configuration changes."
1819721,2019-04-09 10:56:33 UTC,That is for the future.
1819721,2019-04-09 10:55:13 UTC,@Sebastian (slovdahl)
1819721,2019-04-09 03:14:04 UTC,"Sebastian,"
1819721,2019-04-05 06:44:36 UTC,@Mathias - do you consider that a blocker that makes you re-modify the ongoing SRU in bug 1817567 ?
1819721,2019-04-04 08:11:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819721,2019-04-04 08:11:33 UTC,This change has the potential to be a showstopper in some cases.
1819721,2019-03-12 15:20:13 UTC,"A community user reported a startup delay for tomcat8, guessing missing entropy at the start?"
1819721,2019-04-09 07:49:18 UTC,"Tiago,"
1819721,2019-04-16 16:51:12 UTC,This bug was fixed in the package tomcat8 - 8.5.39-1ubuntu1~18.10
1819730,2019-05-14 20:44:40 UTC,"Ed,"
1819730,2019-03-14 12:08:10 UTC,"One other thought is that with the current configuration (vrrp clustering using overlay/tunnel network) if the tenant east-west traffic saturates the network such that vrrp health checks start to time out, this could cause unnecessary re-elections/transitions which would have the knock-on effect of adding extra load to the environment (as neutron would need to keep up with this and itself generate more load in doing so)."
1819734,2019-09-20 13:00:54 UTC,"This feels like a serious issue. One possibility is snap-confine misunderstanding the distribution and believing it is running on a core16 system. I asked on IRC but I will still check manually myself, if you can provide the information about the release of debian that you used."
1819734,2019-09-20 15:10:44 UTC,I know at least one was on sid: https://github.com/nextcloud/nextcloud-snap/issues/913#issuecomment-504719193
1819734,2019-09-21 16:22:42 UTC,"I hit this on Fedora 29, using the nextcloud snap."
1819734,2019-10-03 14:38:50 UTC,"Zygmunt, latest comment from another Nextcloud snap user (https://github.com/nextcloud/nextcloud-snap/issues/913#issuecomment-537892194):"
1819734,2019-10-29 22:06:05 UTC,We've discussed this issue and determined the following:
1819734,2019-10-30 12:22:04 UTC,"I understand the reason of why.
As a not-so-expert user, can you (or someone) explain which are the workarounds possible before next stable release? Like enable apparmor and if so, how to do it?"
1819734,2020-07-21 22:05:45 UTC,"As a snap developer, I am displeased that snapd's failing to provide consistent behavior across distros is considered invalid. The burden of ensuring snaps run properly across distros should not be left up to individual snap developers when that is one of the primary selling points of snapd."
1819735,2020-09-16 12:17:47 UTC,Does it happens always when you have more than two interfaces or it is random? If it is random does increasing the number of interfaces makes it more likely to fail?
1819735,2020-09-16 12:18:07 UTC,I mean incomplete not invalid
1819735,2020-09-16 13:02:10 UTC,there seam to be 2 issues
1819735,2020-11-16 04:17:18 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1819739,2020-03-24 11:50:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819741,2019-05-06 23:04:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819741,2019-03-14 20:47:10 UTC,"This is already fixed upstream (in AppArmor 2.12.2 and 2.13.2), especially commit f997977e6."
1819741,2019-05-06 23:04:16 UTC,I have the same issue with an enabled firefox profile on Ubuntu 18.04.2
1819751,2019-03-14 14:15:10 UTC,pytz/tests/test_docs.py also fails on Python 3.8 because repr(datetime.timedelta) changed to include parameter names. Example of failure:
1819751,2019-07-31 15:34:38 UTC,"The test ensures that an unpickled timestamp references the same instant in time (universal, not wallclock), even if changes to the timezone database have been made since it was pickled."
1819751,2019-07-26 13:45:06 UTC,"First patch, refactored for 2019.1."
1819751,2019-03-14 14:10:19 UTC,The failing test inspect pickle binary data... I'm not sure of the purpose of the test.
1819752,2019-05-14 16:19:07 UTC,"Reviewed:  https://review.opendev.org/642859
Committed: https://git.openstack.org/cgit/x/wsme/commit/?id=0ed01983a7d99917aeef2e19e79098df7666fc6c
Submitter: Zuul
Branch:    master"
1819752,2019-03-12 18:53:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642859"
1819756,2019-04-03 05:53:54 UTC,"List based file types are ideal. Kicad provides user inputs for filetype suffix, path to binary and program description this permits more usability with less obstructions."
1819760,2019-03-18 14:45:25 UTC,We indeed should at least document the expectations of the behavior.
1819760,2019-03-19 11:11:40 UTC,"I can take this, Erno :) once I get a mo this week I'll work with Keith to update!"
1819761,2019-09-23 06:50:29 UTC,"This is in the security Teams review queue (which is the proper next step).
Thanks Seth for all your work on this already."
1819761,2020-03-02 09:06:13 UTC,Seeed change MP opened: https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/380071
1819761,2020-03-02 07:17:17 UTC,"Now ready for promotion together with runc in bug 1817336.
We need to make a seed change to pull them in."
1819761,2020-02-28 18:17:00 UTC,"I reviewed containerd 1.3.1-0ubuntu1 as checked into focal. This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1819761,2020-01-14 14:43:59 UTC,"With above analysis done, in conjunction with the decisions in Paris and per the discussion in the MIR team meeting at [1] this is an ack."
1819761,2020-01-14 14:31:19 UTC,# containerd - vendorized dependencies
1819761,2019-07-19 02:36:37 UTC,There's a handful of text files that are marked executable:
1819761,2019-07-18 18:16:40 UTC,"Andreas, yes; we'd like to you build using golang -dev packages and not build the vendored code. There's no need to repack the orig tarball and no need to switch to dynamic linking."
1819761,2019-07-18 12:28:57 UTC,"Thanks for the review, Seth. Just to be clear, you are asking for the golang vendored bits to be split into their own packages (if not already available in the archive), and switch to shared linking for them?"
1819761,2019-07-18 04:11:19 UTC,"There's roughly half-million lines of code in vendor/ -- we have asked for Go packages to have their vendored code split out into their own packages to simplify triage, fixing, and minimize rebuilding:"
1819761,2019-07-18 01:54:09 UTC,The lintian errors appear to have been drastically reduced in the interim:
1819761,2019-03-28 15:05:08 UTC,"I see no obvious issues with the package, but it's huge and would benefit the Security Team reviewing it as well."
1819761,2019-03-18 23:11:02 UTC,ubuntu-server is now subscribed to bugs
1819761,2020-03-02 10:40:59 UTC,"Seed change approved and done, since this only is going to the supported seed but not getting a direct package/task dependency please help to let us later double check it actually shows up in component mismatches."
1819761,2020-03-04 11:02:48 UTC,"Override component to main
containerd 1.3.3-0ubuntu1 in focal: universe/misc -> main
containerd 1.3.3-0ubuntu1 in focal amd64: universe/admin/optional/100% -> main
containerd 1.3.3-0ubuntu1 in focal arm64: universe/admin/optional/100% -> main
containerd 1.3.3-0ubuntu1 in focal armhf: universe/admin/optional/100% -> main
containerd 1.3.3-0ubuntu1 in focal ppc64el: universe/admin/optional/100% -> main
containerd 1.3.3-0ubuntu1 in focal s390x: universe/admin/optional/100% -> main
golang-github-docker-containerd-dev 1.3.3-0ubuntu1 in focal amd64: universe/admin/optional/100% -> main
golang-github-docker-containerd-dev 1.3.3-0ubuntu1 in focal arm64: universe/admin/optional/100% -> main
golang-github-docker-containerd-dev 1.3.3-0ubuntu1 in focal armhf: universe/admin/optional/100% -> main
golang-github-docker-containerd-dev 1.3.3-0ubuntu1 in focal i386: universe/admin/optional/100% -> main
golang-github-docker-containerd-dev 1.3.3-0ubuntu1 in focal ppc64el: universe/admin/optional/100% -> main
golang-github-docker-containerd-dev 1.3.3-0ubuntu1 in focal s390x: universe/admin/optional/100% -> main
12 publications overridden."
1819764,2019-06-18 03:41:20 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1819764,2019-04-10 21:47:26 UTC,"Reviewed:  https://review.openstack.org/650060
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=17e6ca727207a21028f2878a1e01047c1be2ad36
Submitter: Zuul
Branch:    stable/stein"
1819764,2019-06-06 06:24:36 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1819764,2019-09-27 09:05:49 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1819764,2019-04-16 15:39:41 UTC,"Reviewed:  https://review.openstack.org/651797
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b8ca269a679ceecfcfa4e95ded148df07e8dd3b2
Submitter: Zuul
Branch:    stable/rocky"
1819764,2019-04-04 00:33:03 UTC,"Reviewed:  https://review.openstack.org/642877
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=521e59224e8a595af66ec898f1bb739a9dbe7d97
Submitter: Zuul
Branch:    master"
1819764,2019-04-04 16:04:00 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650060"
1819764,2019-03-12 20:12:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/642877"
1819764,2019-04-11 14:37:12 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/651797"
1819765,2019-03-12 20:22:49 UTC,"The attachment ""ubiquity-diff.txt"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1819767,2019-03-14 13:05:40 UTC,It seems like there could be some overlap between this idea and bug 1801999.
1819769,2019-08-24 09:25:25 UTC,Fixed in https://github.com/ubuntu/yaru/pull/1454
1819769,2019-08-26 18:52:06 UTC,https://launchpad.net/ubuntu/+source/yaru-theme/19.10.1
1819772,2019-03-12 23:55:04 UTC,*** This is an automated message ***
1819779,2020-01-21 08:19:28 UTC,"The new version is in focal now
https://bugs.launchpad.net/ubuntu/+source/gnome-software/3.34.2-1ubuntu1"
1819779,2019-09-07 09:49:00 UTC,Could it be updated to version 3.32.4 for Eoan?
1819779,2019-09-10 12:04:53 UTC,"The reasons for not updating still stand, the refactoring has regressions on debs support and lack testing, Debian didn't update as well for similar reasons"
1819779,2019-11-06 15:10:53 UTC,Is there a bug for the Debian side of things?
1819779,2020-01-13 12:26:08 UTC,"Are there any news about the possible gnome-software version in Focal? Debian Testing/Unstable currently has gnome-software 3.34.2, however Ubuntu is still on 3.30.6."
1819779,2020-01-14 02:51:20 UTC,I'm working on rebasing on the Debian 3.34 version.
1819786,2019-04-29 16:04:06 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1819786,2019-04-09 02:42:42 UTC,"Well, my apologies.   I retract my skepticism!   Your referenced -47 kernel above appears to have fixed the problem, while the stock -47 kernel showed the failure when I tested it this evening first (I already had the distributed 4.15.0-47 kernel installed, then I removed it and installed your references)."
1819786,2019-04-09 00:48:04 UTC,"Thanks for getting back to me on this.  Sorry for the slow response, did not get (or see?) an email notification about an update."
1819786,2019-04-29 23:28:41 UTC,"I'd like to note that I tested/verified BOTH these kernel version in their respective Proposed states that have the ipvs fix.   We really most need the 16.04 4.15 hwe kernel released, which appears to be in progress but this is a bionic bug so its unclear if another step is required."
1819786,2019-03-12 22:00:10 UTC,This change was made by a bot.
1819786,2019-05-14 22:54:10 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819786,2019-04-02 08:03:49 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1819786/"
1819786,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1819817,2019-03-13 06:47:21 UTC,"Hello,"
1819819,2019-03-14 14:42:57 UTC,FWIW it looks like rtslib-fb has been pip installed into /usr/local and the package has also been installed from Ubuntu; if I install the package by itself the rtslib-fb-targetctl.service starts correctly.
1819821,2019-03-13 12:32:45 UTC,"Hi, Rafi,"
1819821,2019-03-13 21:10:31 UTC,Hi Alberto
1819822,2019-03-13 05:48:58 UTC,Subscribing field-medium as this is blocking security updates for customer clouds.
1819822,2019-03-13 10:51:19 UTC,Why do you have 17.03 PPA in sources.list?
1819822,2019-03-13 13:22:44 UTC,"@Adam, that's a good question. I am attempting to figure it out."
1819822,2019-05-13 04:17:19 UTC,[Expired for landscape-client (Ubuntu) because there has been no activity for 60 days.]
1819831,2019-10-02 21:55:36 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819831,2019-10-02 21:55:08 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1~18.04.1
1819831,2019-10-02 21:54:51 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1~19.04.1
1819831,2019-09-30 21:28:29 UTC,Verification-done on bionic:
1819831,2019-09-30 21:01:56 UTC,Verification-done on disco:
1819831,2019-03-20 16:41:16 UTC,"Sound simple and straightforward. I was not aware that such shorthand was possible (in fact, it doesn't seem to be documented in the manpage?)"
1819831,2019-08-22 01:13:47 UTC,This bug was fixed in the package netplan.io - 0.98-0ubuntu1
1819831,2019-03-21 13:22:48 UTC,There is a PR for it at https://github.com/CanonicalLtd/netplan/pull/79/files - glad to fix up this PR for code coverage and whatever else it needs if it is likely to be merged
1819831,2019-08-27 22:48:14 UTC,"Hello Cullen, or anyone else affected,"
1819837,2019-03-13 20:10:06 UTC,All I am concerned with is discrepancy.
1819837,2019-03-13 16:00:55 UTC,"@Wayne-  We currently have shortcuts for the project directory (and other standard paths) in the dropdown menu at the bottom.  Because the project path is selected in the dropdown but not in the tree, the user needs to select a different item and then back to the project path.  We could simply make the dropdown match the tree (maybe even for 5.1.1?)."
1819837,2019-03-13 13:56:04 UTC,I cannot agree more that this selection dialog needs to be fixed.
1819837,2019-03-13 15:12:50 UTC,"@Seth, I agree that the file selector part of this dialog needs some work but the user is only requesting that the default path is the current project path.  In principal I agree with this but there is an equally valid argument that the default path should be where the 3D models are located.  I personally prefer the project path but that may not be the consensus."
1819851,2019-07-30 23:57:35 UTC,I checked this test case and it perfectly pass on gate - http://logs.openstack.org/86/672186/7/check/tempest-integrated-object-storage/48e6307/testr_results.html.gz
1819851,2019-10-16 04:17:33 UTC,[Expired for tempest because there has been no activity for 60 days.]
1819851,2020-06-17 15:46:16 UTC,We ran into this issue as well while deploying OpenStack with Swift running behind a reverse proxy/LB that does not use any Transfer-Encoding in its responses.
1819851,2020-06-17 16:16:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/736292"
1819851,2020-06-29 16:38:12 UTC,"I see, thanks Thomas for detail. I agree on the header selection when it runs under proxy or load balancer. let's not check this header."
1819851,2020-07-02 20:22:32 UTC,"Reviewed:  https://review.opendev.org/736292
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=42e111c7d8f1cdb5d51a1c4f2ce5c64c3d3471f1
Submitter: Zuul
Branch:    master"
1819851,2020-12-17 12:53:51 UTC,This issue was fixed in the openstack/tempest 25.0.1 release.
1819869,2019-03-14 17:25:42 UTC,I have verified that version 3.13.0-167.217 contains the missing files and that after installation hv_kvp_daemon and hv_vss_daemon are active.
1819869,2019-03-13 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819869,2019-03-13 10:09:05 UTC,"This is a packaging issue, so logs should be irrelevant."
1819869,2019-03-14 11:36:50 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed-trusty'."
1819869,2019-03-15 15:40:41 UTC,This bug was fixed in the package linux - 3.13.0-167.217
1819875,2019-07-03 06:38:42 UTC,This has just landed into master. The 2.40 backport will be released separately by mvo as a part of the 2.40 cycle.
1819875,2019-04-01 16:47:56 UTC,I've closed 6671 and re-opened as https://github.com/snapcore/snapd/pull/6673
1819875,2019-06-27 19:08:56 UTC,This is close to landing on https://github.com/snapcore/snapd/pull/7026
1819875,2019-06-12 20:11:13 UTC,This is preventing LXD from moving to core16 to core18 (roadmap item).
1819875,2019-03-13 10:30:21 UTC,Related bug https://bugs.launchpad.net/snappy/+bug/1819887
1819875,2019-04-01 12:08:31 UTC,I've implemented a fix in https://github.com/snapcore/snapd/pull/6671
1819875,2019-03-13 10:00:09 UTC,I would add that any snap refresh that changes base snap name must be handled with dedicated logic that we currently don't have a design for. It is unacceptable to run a snap against different base snap than a snap has declared to use.
1819890,2019-03-14 02:17:18 UTC,This is partly correct behaviour :)
1819890,2019-03-14 10:09:30 UTC,Thanks for your explanation of how gnome-shell workspaces work or should work.
1819890,2019-03-14 12:08:09 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1819890,2019-03-15 01:55:37 UTC,"No problem to keep this bug separate. That's why we have the tag 'noclick', to group similar bugs:"
1819890,2019-03-15 10:33:16 UTC,"Indeed, confirmed, it looks like an upstream regression and would be nice if someone could report it on https://gitlab.gnome.org/GNOME/gnome-shell/issues"
1819890,2019-03-15 10:51:54 UTC,Reported upstream as requested.
1819890,2019-03-15 10:58:14 UTC,Thanks!
1819890,2019-10-31 16:56:33 UTC,Upstream issue #1059 was closed as being a duplicate of https://gitlab.gnome.org/GNOME/mutter/issues/572. Updating upstream bug task and reassigning Ubuntu task. Still a problem in Ubuntu 19.10.
1819890,2020-03-24 19:12:11 UTC,This bug was fixed in the package mutter - 3.36.0-2ubuntu1
1819890,2020-12-09 18:36:48 UTC,I have the same issue
1819890,2020-12-10 02:04:27 UTC,This bug was closed almost 9 months ago so if you still have problems then please open a new bug.
1819897,2019-03-13 14:06:01 UTC,"This ""ExtensionsNotFound: Extensions not found: ['subnet-service-types']."" may only come from this refactor patch:
https://review.openstack.org/#/c/642834"
1819897,2019-03-13 14:25:31 UTC,"And most ""Neutron did not start"" failures are coming from this:
https://review.openstack.org/#/c/641186
it is trying to rename the process tittle by using this:
https://review.openstack.org/#/c/637019/"
1819897,2019-03-13 12:18:24 UTC,frickler also pointed out these other failures that result in the same devstack timeout but have obvious failures in the neutron API logs:
1819898,2019-03-13 11:46:18 UTC,We could also flag a major discrepancy between 'expected-osd-count' and the actual osd count in juju status to trigger the operator to run the action.
1819903,2019-03-13 13:43:01 UTC,3par hasn't implemented get_manageable_volumes() yet.
1819904,2019-04-11 21:46:49 UTC,Looks good and gets the job done. Thanks for the patch!
1819904,2019-04-11 21:46:24 UTC,Andre Miranda referenced this bugreport in commit 67582a97fc57810cefd78c271aed4660dbd93dfe
1819904,2019-04-10 03:17:10 UTC,"Created attachment 8395
0001-Fix-slider-labels-Bug-14395.patch"
1819904,2019-04-09 21:31:17 UTC,"From my perspective the workaround approach is ok. The only remark I have is that I would
- only apply the provider to the style context of the scale widgets and
- set the label insensitive (gtk_widget_set_insensitive) to mimick the previous style"
1819904,2019-02-16 01:18:38 UTC,*** Bug 15143 has been marked as a duplicate of this bug. ***
1819904,2018-12-07 03:17:07 UTC,"Created attachment 8157
WIP Patch"
1819904,2018-10-13 02:55:19 UTC,"Similar issue:
$ xfce4-power-manager-settings -V
This is xfce4-power-manager version 1.6.1, running on Xfce 4.12.
Built with GTK+ 3.22.26, linked with GTK+ 3.22.30."
1819904,2018-09-23 20:13:15 UTC,"Created attachment 8000
underscore separated values"
1819904,2018-05-12 09:17:37 UTC,"Created attachment 7727
missing 'minutes' at Light-Locker settings"
1819904,2018-05-12 09:15:06 UTC,"Created attachment 7726
missing 'hour and ...' ?"
1819904,2018-05-12 09:12:25 UTC,"Created attachment 7725
missing 'Hour' ?"
1819904,2018-05-12 09:10:47 UTC,"Created attachment 7724
missing 'Minutes' ?"
1819904,2018-09-25 02:34:40 UTC,"Created attachment 8003
sample.c"
1819906,2019-04-07 09:22:13 UTC,It's probably a duplicate of https://bugs.launchpad.net/ubuntu-mate/+bug/1806459
1819907,2019-04-13 01:20:18 UTC,"A “safe graphics” mode has just been added to 19.04. It is present in the latest daily test image, which can be found at http://cdimage.ubuntu.com/daily-live/current/. 19.04 will be release on Apr 18."
1819907,2019-09-25 04:17:17 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1819907,2019-04-04 05:57:22 UTC,"Use this ISO:
http://cdimage.ubuntu.com/daily-live/current/disco-desktop-amd64.iso"
1819907,2019-04-03 15:06:09 UTC,"Still broken in Ubuntu 19.04...With this Install nomodeset did not work.David had to blacklist the nouveau module
Are we going to get a permanent fix ?."
1819907,2019-04-04 03:28:22 UTC,"@Vamshee
Can you provide more details what you did and what did not work?"
1819907,2019-03-14 12:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819907,2019-03-15 01:06:23 UTC,"The suggest from Bin Li fixed the problem.P1, X1 Exteme and P52 worked fine after we implemented the fix.we may need a permanent fix from within the OS in the near future ?..."
1819907,2019-03-14 07:00:42 UTC,"@Bin, @Anthony, Can we have the fix before 19.04 GA? Thanks."
1819907,2019-03-14 03:51:34 UTC,It should be caused by the nouveau driver for Nvidia card.
1819908,2019-03-13 12:40:06 UTC,lsmod run on a non-maximized window. All looks good.
1819908,2019-03-13 12:41:10 UTC,"continuing from the previous screenshot, all I did here was to click the maximize button. We can already see some bad rendering on the top right corner."
1819908,2019-03-13 12:42:32 UTC,"Here, with the maximized window, I typed several commands again: lsmod, clear, clear. If you look carefully, you can see the clear at the bottom, then at the top again, and nothing changes. All I can see are the characters I type, but not the command's output or effect. The screen doesn't clear, and the list of modules produced by ""lsmod"" doesn't appear."
1819909,2019-03-14 02:22:57 UTC,"It sounds like the XFCE window manager has crashed, but I'm not sure. It might be a good idea to follow these steps:"
1819909,2019-05-13 04:17:29 UTC,[Expired for xfce4 (Ubuntu) because there has been no activity for 60 days.]
1819914,2019-03-13 14:04:25 UTC,"since we are resizing to the same host, during nova.compute.manager.ComputeManager.confirm_resize() virt driver does not perform the vif.unplug() operation[1]."
1819915,2019-03-25 04:24:03 UTC,"With the recomended nvidia driver and low ram usage, the system sucessfully hibernates, but then fails to resume and I get the login screen instead. With high ram usage it hangs trying to save the image to disk. That's a new behaviour to me."
1819915,2019-03-19 05:31:57 UTC,What packages you recommend me downgrade there?
1819915,2019-03-23 19:42:55 UTC,Ok so after running the right command to install the older kernel:
1819915,2019-03-23 19:46:04 UTC,"Okay, forget what I said, I just randomly run into the freeze with the the -43 version after 3 hibernation cycles, Ill be testing with -42 now...."
1819915,2019-03-23 23:42:42 UTC,also just happened on the -42 version now... Seems like was less likely to happen in older versions. I remember 2 months ago I made more than 10 hibernation cycles. Not sure whats happening now...
1819915,2019-03-24 07:58:28 UTC,So maybe it's caused by Nvidia driver update?
1819915,2019-03-25 03:10:23 UTC,I don't think that's the issue. The nvidia problem I was used to is being unable to resume. I also tested with the nvidia drivers disabled and this issue still persists. Something I noticed is that I was not on the recommended version of nvidia drivers which is 415 and I just changed that now upgrading to 418. Still exactly the same issue.
1819915,2019-03-25 04:15:56 UTC,Maybe try older kernel releases from Artful (4.13) or Zesty (4.10).
1819915,2019-03-19 05:59:38 UTC,Linux kernel and DKMS.
1819915,2019-03-25 04:27:35 UTC,"No, I am 100% sure it worked with kernel 4.15.0-42 and with the nvidia proprietary driver  nvidia-415 before the version .27"
1819915,2019-04-02 07:56:19 UTC,"I can successfully hibernate/resume Inspiron 7567 with kernel 4.18.0-17-generic, when Intel graphics is selected."
1819915,2019-04-02 01:35:36 UTC,So... After reconfiguring uswsusp I increased logging level to 7. Also i tried disabling the nvidia modules again but the same issue persists. This is the information I could get:
1819915,2019-04-02 03:19:10 UTC,"After researching a bit and with the help of a friend, I thought it could be the i915 module due to the drm and rc6, which in fact was in use:"
1819915,2019-03-19 05:21:03 UTC,Yes please. Most likely it's cause by kernel and drivers update.
1819915,2019-04-02 15:10:24 UTC,"Could you please test or tell what happens with nvidia selected? It used to worked fine to me with nvidia too, as I said before. Are you on the latest release? 18.04.2? Up to date? I haven't tested that kernel yet, and it wasn't automatically installed running apt upgrade or full-upgrade.... I'm running:"
1819915,2019-04-03 02:34:14 UTC,"> Could you please test or tell what happens with nvidia selected?
Hang at freeze or thaw stage. Can't really tell.
Nothing much as I do as it's proprietary.
"
1819915,2019-04-03 16:39:14 UTC,"Are really you using uswsusp? (hibernate command), pm-utils (pm-hibernate) or systemctl hibernate?"
1819915,2019-04-03 18:19:41 UTC,systemctl hibernate
1819915,2019-04-03 20:50:30 UTC,"Okay I found a way to get it working, first I gave up of uswsusp and runned:"
1819915,2019-04-03 20:52:02 UTC,"This seems to be an old bug with uswsusp, which is an old package: https://bugzilla.kernel.org/show_bug.cgi?id=75101"
1819915,2019-08-22 01:47:01 UTC,"I've also been experiencing a similar issue for some time - occurring intermittently, not when I'm using only a small amount of RAM - where s2disk would hang on writing the image:
s2disk: Saving xxxx image data pages (press backspace to abort) ...   0%"
1819915,2019-03-25 04:31:45 UTC,Isn't there a way to extract logs from s2disk or uswsusp???
1819915,2019-03-18 13:47:22 UTC,"As I said, the major change that I remember was updating from ubuntu 18.04.1 to 18.04.2. I'm attaching my apt history log to this message. I am 100% sure that hibernation wasn't crashing and worked flawlessly on 02/06/2019 and it wasn't anymore in 03/04/2019."
1819915,2019-03-23 04:41:24 UTC,"Alright, today  finally had some time and installed older kernels. 4.15.0-42 , 4.15.0-44, 4.15.0-45 and on the last I had the same bug as always. I installed the older linux images, with apt, and runed initramfs:"
1819915,2019-03-17 20:56:50 UTC,"Another thing I noticed is that changing from one DE to another does change nothing, Gnome or KDE same issue."
1819915,2019-03-18 04:49:34 UTC,"Sorry this is a bit confusing. The bug description says it works with v4.15 but now it doesn't?
What changes made the hibernation stops working?"
1819915,2019-03-14 21:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819915,2019-03-14 21:12:00 UTC,apport information
1819915,2019-03-14 21:12:04 UTC,apport information
1819915,2019-03-14 21:12:08 UTC,apport information
1819915,2019-03-14 21:12:11 UTC,apport information
1819915,2019-03-14 21:12:14 UTC,apport information
1819915,2019-03-14 21:12:17 UTC,apport information
1819915,2019-03-14 21:12:19 UTC,apport information
1819915,2019-03-14 21:12:22 UTC,apport information
1819915,2019-03-14 20:45:03 UTC,"unsure if that's the kernel or not, but that's a better bet that the settings UI you reported the bug against"
1819915,2019-03-14 21:12:28 UTC,apport information
1819915,2019-03-14 21:12:31 UTC,apport information
1819915,2019-03-14 21:12:33 UTC,apport information
1819915,2019-03-14 21:12:36 UTC,apport information
1819915,2019-03-14 21:12:41 UTC,apport information
1819915,2019-03-14 21:12:46 UTC,apport information
1819915,2019-03-15 03:59:23 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0]."
1819915,2019-03-15 13:56:50 UTC,Same result (freeze on s2disk screen) in both kernels.
1819915,2019-03-16 16:27:40 UTC,So does this happen to 4.15 + Nvidia driver?
1819915,2019-03-16 16:49:03 UTC,"Yes this is exactly how this this is happening. kernel 4.15 + propretary nvidia drivers, either with those drivers enabled or uninstalled. Also tested on kernel 5 without nvidia drivers."
1819915,2019-03-14 21:12:25 UTC,apport information
1819918,2019-03-13 14:25:11 UTC,"I reported this incorrectly, since the actual traces aren't included. Here's the kernel log."
1819919,2020-05-02 02:04:38 UTC,"Sorry for bumping an old issue, but the ""fix"" released on upstream seems to be the ""nuclear"" option of completely removing `snap`... which might not work for everyone. :("
1819919,2020-05-02 02:04:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819919,2019-03-14 21:03:49 UTC,I have created an issue here: https://gitlab.gnome.org/GNOME/gnome-system-monitor/issues/101
1819920,2019-03-14 02:41:39 UTC,Unfortunately this is the default power button behaviour.
1819920,2019-03-14 02:49:12 UTC,"That all said, it is a bug in gnome-session to represent that --power-off and --no-prompt should work at all."
1819920,2019-03-14 09:42:38 UTC,Ideally should be reported upstream on https://gitlab.gnome.org/GNOME/gnome-session/
1819920,2019-03-14 16:37:03 UTC,"Thank you @Daniel van Vugt for your thorough explanation and @Sebastien Bacher for suggestion of reporting at gitlab.gnome.org, I have created this issue:"
1819920,2019-03-14 20:05:26 UTC,Thanks!
1819921,2019-04-01 12:52:53 UTC,The patch has been dropped again from Bionic/master-next because it breaks the build on arm64:
1819921,2019-03-13 15:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819921,2019-04-15 03:29:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1819921,2019-04-24 08:01:51 UTC,This bug was fixed in the package linux-oem - 4.15.0-1036.41
1819921,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1819921,2019-05-14 22:54:12 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819921,2019-11-14 04:39:21 UTC,"Patch available in Focal, mark this as fix-released."
1819923,2019-07-09 14:10:26 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/669879"
1819923,2019-07-22 21:59:38 UTC,"Reviewed:  https://review.opendev.org/637955
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=54dea2531c887f77e4b7a8e7edb978d8f1ccfe50
Submitter: Zuul
Branch:    master"
1819923,2019-07-03 14:39:26 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/668925"
1819923,2019-07-23 15:46:46 UTC,"Reviewed:  https://review.opendev.org/668925
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7a37940ce9645add3b976a3609014a2b3f8c7193
Submitter: Zuul
Branch:    master"
1819923,2019-12-11 09:05:04 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/638207
Reason: Let's reactivate this if there is a report that confirms the need for such a cache"
1819923,2019-11-04 23:14:58 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/692923"
1819923,2019-11-05 16:39:21 UTC,"Reviewed:  https://review.opendev.org/692923
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=06caa62441ea977a52a1ed631d8aa49a6a43d32c
Submitter: Zuul
Branch:    stable/stein"
1819923,2019-07-01 10:37:59 UTC,"Reviewed:  https://review.opendev.org/667994
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=87365c760ee89493db87183c4c751ba5fc7b921a
Submitter: Zuul
Branch:    master"
1819923,2019-09-27 09:01:44 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1819923,2019-06-27 21:36:43 UTC,"Reviewed:  https://review.opendev.org/655459
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e2866609bbb4e70e2b781a80ecc1ad0bccf93813
Submitter: Zuul
Branch:    master"
1819923,2019-10-03 03:28:42 UTC,"Reviewed:  https://review.opendev.org/669879
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0044702e0dd51814be38818144c675cc8a7617ca
Submitter: Zuul
Branch:    master"
1819923,2019-06-27 19:48:01 UTC,"Reviewed:  https://review.opendev.org/655458
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9adcf53210747d34248702874494537ef2a46781
Submitter: Zuul
Branch:    master"
1819923,2019-06-27 17:26:51 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/667994"
1819923,2019-06-27 13:08:20 UTC,"Reviewed:  https://review.opendev.org/655457
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e6fc3162612e4dff73fc91519269f2318fa4e750
Submitter: Zuul
Branch:    master"
1819923,2019-04-24 14:27:44 UTC,"Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/637953
Reason: superseeded by multiple refactor patches on topic bug/1819923"
1819923,2019-04-24 14:26:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655459"
1819923,2019-04-24 14:25:48 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/655458"
1819923,2019-04-24 14:25:33 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/655457"
1819923,2019-03-13 15:30:35 UTC,Bugfix is proposed in https://review.openstack.org/#/q/topic:bug/1819923
1819923,2019-06-27 21:33:48 UTC,"Reviewed:  https://review.opendev.org/637954
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=307999c58101a5920e23ef181643d3b46bbf987c
Submitter: Zuul
Branch:    master"
1819924,2020-09-03 04:17:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1819924,2020-06-09 23:47:14 UTC,It had actually been working fine in 20.04 until a recent kernel update to 5.4.0-33.37.
1819924,2020-06-09 04:33:26 UTC,Please test 20.04.
1819924,2019-04-08 13:17:13 UTC,"Issue still remains with the mainline kernel.  The contents of the kernel Oops message differs slightly, but still very similar:"
1819924,2019-04-07 09:17:15 UTC,"My bad, didn't notice it's AMD graphics instead of Intel graphics. Please test mainline kernel."
1819924,2019-04-07 09:16:40 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc3 kernel [0]."
1819924,2020-07-04 13:09:01 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/"
1819924,2019-03-21 13:00:58 UTC,"It's possible, though it's hard to confirm as I cannot find a kernel OOPS message in that ticket."
1819924,2019-03-20 07:15:15 UTC,Similar to LP: #1820811?
1819924,2019-03-19 16:43:24 UTC,I have verified this issue still exists in kernel version 4.18.0-10.
1819924,2019-03-13 17:09:35 UTC,Would it be possible to try kernel < 4.18.0-16?
1819924,2019-03-13 15:00:14 UTC,This change was made by a bot.
1819924,2019-04-05 18:04:12 UTC,I don't think this issue is related to LP #1820811.
1819925,2019-03-13 14:48:53 UTC,"I've marked this as affecting gnome-shell as well since we're seeing the same thing when selecting ""Show details"" from the menu in the panel."
1819925,2019-03-14 01:07:45 UTC,It's passing the portal ID (so many IDs in slightly different formats...) to gnome-software which is why it's failing. Needs to be converted inside gnome-control-center.
1819925,2019-03-14 01:09:36 UTC,The shell case is probably passing the application name as an ApoStream ID or something similar. It should probably be passing a snap:// URL. That should probably be tracked in another bug.
1819925,2019-03-14 09:38:02 UTC,"Removing gnome-shell, Robert said it should be another report"
1819926,2019-03-26 00:31:26 UTC,"This appears to be related to the package manager snapd, not the DNA analysis tool snap."
1819926,2019-10-16 06:25:32 UTC,Thanks for your bugreport. We plan to work on this but have no clear target date yet.
1819929,2019-04-19 06:28:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819929,2019-03-13 19:41:51 UTC,Reported upstream as https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/508
1819932,2019-09-02 16:20:22 UTC,"Hi Ondrej, I cannot reproduce (snap version 2.41+git1457.73f3b15~ubuntu16.04.1, edge channel): I've  ""mysnap"" snap directory, then:
1. sudo snap try mysnap
2. rm -rf mysnap
3. sudo snap remove mysnap"
1819932,2019-09-05 22:48:59 UTC,"Unfortunately I can't test this, as I had to recover system from broken
state to continue with my daily development. So I can only update if I get
system to this state again"
1819932,2019-11-05 04:17:57 UTC,[Expired for snapd because there has been no activity for 60 days.]
1819933,2019-03-25 12:43:31 UTC,"@Seth, are you still having this issue?  I'm not seeing this on windows so it may be a linux specific issue."
1819933,2019-03-25 12:56:28 UTC,I saw that only using wxWidgets compiled with GTK3.
1819933,2019-03-26 02:21:06 UTC,"Yes.  As JP notes, appears to be limited to GTK3"
1819933,2019-04-11 17:21:34 UTC,I'm having the same issue - another datapoint:
1819933,2019-05-05 16:10:33 UTC,"I see this as well (Ubuntu 18.04, wxWidgets 3.0.4 with GTK+ 3.22). While the KiCad preview window has a black background, the color scheme in the actual printout and the system preview window is correct (e.g. not black background)."
1819933,2019-05-05 22:24:14 UTC,A search of the wxWidgets issues reveals this one: https://trac.wxwidgets.org/ticket/18371. They report seeing black across the entire page in the print preview in the sample program. So this appears to be upstream from kicad.
1819933,2019-05-27 13:25:31 UTC,Fixed in 720b26d11e4431978e9070b98d0198679a2ccb3b
1819934,2019-04-11 15:36:59 UTC,Thanks Jim!  Good to know I'm not the only one.  I look forward to meeting you at KiCon
1819934,2019-06-17 20:29:55 UTC,Fixed in b075886b1
1819934,2019-11-25 16:00:23 UTC,Nope.  Something has changed the ordering again.
1819934,2019-04-11 15:01:30 UTC,I also have this problem when I embed an image in a schematic. The page doesn't print correctly.
1819934,2019-11-25 15:38:56 UTC,I still experience this in kicad-5.1.5-1.fc31.x86_64.rpm. Is that expected?
1819934,2019-03-20 16:17:48 UTC,Thanks for the test Wayne.  I guess I'll fight with it.
1819934,2019-03-20 14:48:47 UTC,"@Seth, I took a look at the project you provided and it prints fine in windows using KiCad (5.1.0-37-g241c5f998).  The only issue I saw was that the bitmap in the print preview was still in color even when black and white printing was selected.  The printed copy of the schematic looked fine to me.  Perhaps this is a linux only issue."
1819934,2019-04-07 16:22:37 UTC,A video would help to understand the problem.
1819936,2019-09-11 01:38:35 UTC,This bug was fixed in the package golang-google-grpc - 1.6.0-3ubuntu0.19.04.2
1819936,2019-09-09 11:09:17 UTC,"Hello again, all,"
1819936,2019-07-02 19:01:04 UTC,"All autopkgtests for the newly accepted golang-google-grpc (1.6.0-3ubuntu0.19.04.2) for disco have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1819936,2019-05-13 10:41:52 UTC,This bug was fixed in the package golang-google-grpc - 1.6.0-3ubuntu0.18.04.1
1819936,2019-05-13 10:41:42 UTC,"The verification of the Stable Release Update for golang-google-grpc has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1819936,2019-05-13 10:41:39 UTC,This bug was fixed in the package golang-google-grpc - 1.6.0-3ubuntu0.18.10.1
1819936,2019-05-13 10:41:21 UTC,"Thank you for your verification. The disco failure is indeed quite a shame, but since you are actively working on all the issues, I'll release the bionic and cosmic parts regardless. Let's just make sure that the FTBFS is resolved with some follow-up upload for disco as soon as possible."
1819936,2019-07-02 17:31:08 UTC,"Hello Tiit, or anyone else affected,"
1819936,2019-05-07 13:55:46 UTC,"First up, thank you Simon for sponsoring this patch and Steve for accepting it into proposed."
1819936,2019-05-03 22:56:11 UTC,"Hello Tiit, or anyone else affected,"
1819936,2019-05-03 22:54:39 UTC,"Hello Tiit, or anyone else affected,"
1819936,2019-05-03 22:53:26 UTC,"Hello Tiit, or anyone else affected,"
1819936,2019-04-20 20:23:48 UTC,"I have uploaded the debdiff to Bionic, Cosmic, and Disco."
1819936,2019-05-08 13:15:32 UTC,I reported the disco FTBFS at https://bugs.launchpad.net/ubuntu/+source/golang-google-grpc/+bug/1828230.
1819938,2019-03-13 19:59:47 UTC,Also when moving could be interesting.
1819939,2019-03-14 12:58:29 UTC,"Bot stated:

> It is important that bug reports be filed about source packages...
"
1819939,2019-03-14 12:50:02 UTC,"Brian asked:

> What mirror are you using?
"
1819939,2019-03-13 20:21:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1819939,2019-03-13 20:52:43 UTC,What mirror are you using?
1819949,2019-04-28 18:13:53 UTC,Using Hyper as my terminal with zsh and running fine :)
1819949,2019-03-18 15:26:43 UTC,"Hi Mohammad,"
1819949,2019-04-18 19:53:47 UTC,"Hi there,"
1819949,2019-06-28 04:17:18 UTC,[Expired for zsh (Ubuntu) because there has been no activity for 60 days.]
1819949,2019-03-19 19:22:08 UTC,"Hi Mohammad,"
1819949,2019-03-19 19:03:15 UTC,~/.zshenv is not there. debsums was not installed. I installed it and attached the output.
1819949,2019-03-18 15:07:22 UTC,Yeah tried opening new terminal every time when commented out a line. Finally logged out and logged in to check. No luck :(
1819949,2019-03-18 08:18:32 UTC,I installed zsh via terminal using 'sudo apt install zsh'. After that I changed my shell from terminal 'chsh -s /usr/bin/zsh' then rebooted. After that my terminal stucked here. Can't even list directory with 'ls' command.
1819949,2019-03-18 14:09:55 UTC,"Running ""zsh -f"" works fine. However comment out all the lines on .zshrc file still didn't work. I'm attaching ""/usr/share/bug/zsh 3>&1"" commands output here."
1819949,2019-03-18 11:27:10 UTC,"Hi Mohammad,"
1819949,2019-03-18 10:05:35 UTC,https://linuxhint.com/install_zsh_shell_ubuntu_1804/
1819949,2019-03-18 09:54:07 UTC,"> Also followed this tutorial but same result.
"
1819949,2019-03-14 20:41:55 UTC,"Thank you for your bug report. How did you install zsh? How did you start using it? Is that from a graphical session? a vt?
could you take a screenshot/photo showing the issue?"
1819949,2019-03-18 14:41:23 UTC,"Hi Mohammad,"
1819952,2019-03-15 18:58:29 UTC,"Bah! Bloody open source projects, I thought they fixed themselves automatically!
Not sure if I'm up to working with Cython source but it doesn't look too hard. Would it be possible to have some kind of declarative setting for this? Feels like it should have one."
1819952,2019-03-15 21:45:50 UTC,"It should use the same mechanism as lxml itself for selecting prefixes, which is based on the ""_DEFAULT_NAMESPACE_PREFIXES"" dict. Users can change it via ""etree.register_namespace()"", but the XML namespace is special enough to always be in there. (Actually, I think lxml should even forbid registering a different prefix for it, but that's an unrelated change.)"
1819952,2019-03-13 18:45:00 UTC,"Right, the XML namespace needs special-casing in the serialiser. PR welcome. See
https://github.com/lxml/lxml/blob/fd81ebb9269e5955eca8d4e9668b1a1daf9e00c0/src/lxml/serializer.pxi#L1089
Tests are in ""test_incremental_xmlfile.py"".
It might actually be worth special casing everything that's in ""_DEFAULT_NAMESPACE_PREFIXES"" (defined in ""etree.pyx"")."
1819955,2019-03-13 18:37:21 UTC,Adding maas logs
1819955,2019-03-13 19:09:13 UTC,Can you try with a ending '/' in the URL?
1819955,2019-03-13 19:21:30 UTC,Works:
1819956,2019-06-26 17:27:43 UTC,"At a quick glance, it appears that the OPAC determines whether a title has holdable copies by looking at //*[local-name()=""holdings"" and @has_holdable=""true""] in the unAPI representation of the record.  So that might be the place to look."
1819957,2019-04-29 22:58:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/656420"
1819957,2020-01-28 08:54:48 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/704508"
1819957,2019-05-16 06:34:02 UTC,This issue was fixed in the openstack/oslo.cache 1.30.4 release.
1819957,2019-05-16 06:21:51 UTC,This issue was fixed in the openstack/oslo.cache 1.33.3 release.
1819957,2019-05-02 23:35:30 UTC,"Reviewed:  https://review.opendev.org/656420
Committed: https://git.openstack.org/cgit/openstack/oslo.cache/commit/?id=1d6d08f4911edb50debab4639e6a2825260b9e09
Submitter: Zuul
Branch:    stable/rocky"
1819957,2019-05-02 21:31:44 UTC,"Reviewed:  https://review.opendev.org/656419
Committed: https://git.openstack.org/cgit/openstack/oslo.cache/commit/?id=aeb95779c7bea4117ccb69b17eab31d452397964
Submitter: Zuul
Branch:    stable/stein"
1819957,2019-04-29 22:57:34 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656419"
1819957,2020-02-24 17:11:03 UTC,"Reviewed:  https://review.opendev.org/704508
Committed: https://git.openstack.org/cgit/openstack/oslo.cache/commit/?id=c31dd1aaac0a1dd8ca3f77b6da911ae85de6dc7a
Submitter: Zuul
Branch:    stable/queens"
1819957,2019-04-26 16:45:46 UTC,This issue was fixed in the openstack/oslo.cache 1.34.0 release.
1819957,2019-04-15 14:49:01 UTC,"Reviewed:  https://review.openstack.org/644774
Committed: https://git.openstack.org/cgit/openstack/oslo.cache/commit/?id=1192f185a5fd2fa6177655f157146488a3de81d1
Submitter: Zuul
Branch:    master"
1819957,2019-03-25 10:15:47 UTC,"Keystone is fixed with oslo.cache fix, marked as invalid for keystone"
1819957,2019-03-20 06:25:54 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/644774"
1819957,2019-03-19 13:33:10 UTC,"Unless there's a way for a malicious actor to trigger and take advantage of this condition, this is probably a class D (security hardening opportunity) report: https://security.openstack.org/vmt-process.html#incident-report-taxonomy"
1819957,2019-03-13 18:55:46 UTC,"""A concern with this model is that the memcached servers may be utilized by other tooling and may lose cache state (in the case the oslo.cache connection is the only thing affected by the network partitioning)."""
1819957,2019-04-29 22:49:57 UTC,is this going to be backported to stein/rocky? (the oslo.cache fix)
1819960,2019-09-20 05:09:10 UTC,Fixed in branch master. The fix will be in the next release. calibre is usually released every alternate Friday.
1819961,2019-04-02 04:54:17 UTC,xenial is using 2.26.
1819961,2019-04-02 05:09:27 UTC,"> On Apr 2, 2019, at 6:54 AM, Matthias Klose <email address hidden> wrote:
>
> xenial is using 2.26.
"
1819961,2019-12-09 16:06:31 UTC,Any updates on this one. It will be really helpful to have this bugfix backported to bionic binutils?
1819963,2019-04-19 00:47:47 UTC,"Reviewed:  https://review.openstack.org/648415
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=99cbbcfd61c3569b9c299c99e4a2eaf38d335d19
Submitter: Zuul
Branch:    stable/queens"
1819963,2019-04-17 22:57:34 UTC,"Reviewed:  https://review.openstack.org/648409
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=440c0fb0ad7b127dfdcfb7302e0e31fa41d5255a
Submitter: Zuul
Branch:    stable/rocky"
1819963,2019-04-17 22:58:06 UTC,"Reviewed:  https://review.openstack.org/648410
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1342cd75e9a091d28bec857f44f833ab5a7d1b96
Submitter: Zuul
Branch:    stable/rocky"
1819963,2019-04-18 20:41:10 UTC,"Reviewed:  https://review.openstack.org/648414
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1b15a342e3e174af745274ca62185e7e8f7f6cf9
Submitter: Zuul
Branch:    stable/queens"
1819963,2019-04-17 18:01:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653505"
1819963,2019-04-22 05:25:29 UTC,"Reviewed:  https://review.opendev.org/648421
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=59c65a15e69da459f3124aacff8e5fabee1fdc9c
Submitter: Zuul
Branch:    stable/pike"
1819963,2019-07-10 21:40:24 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1819963,2019-04-26 17:15:47 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1819963,2019-06-01 03:21:42 UTC,"Change abandoned by Eric Fried (<email address hidden>) on branch: master
Review: https://review.opendev.org/653504
Reason: Purpose served"
1819963,2019-06-01 03:21:50 UTC,"Change abandoned by Eric Fried (<email address hidden>) on branch: master
Review: https://review.opendev.org/653505
Reason: Purpose served"
1819963,2019-06-06 06:24:48 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1819963,2019-04-17 18:01:27 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653504"
1819963,2019-09-27 09:05:45 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1819963,2019-04-22 05:25:40 UTC,"Reviewed:  https://review.opendev.org/648422
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bf7112ee4d8e90c79f99526e9071e6e9e94031aa
Submitter: Zuul
Branch:    stable/pike"
1819963,2019-04-11 23:23:42 UTC,"Reviewed:  https://review.openstack.org/648402
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=26e59912838b145b627aa247c45b0b19393466c0
Submitter: Zuul
Branch:    stable/stein"
1819963,2019-06-18 03:41:39 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1819963,2019-03-28 14:39:52 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/648422"
1819963,2019-04-11 21:18:18 UTC,"Reviewed:  https://review.openstack.org/648401
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0b2345442dfc99586c1e2b5ca13c54fe8045e5c8
Submitter: Zuul
Branch:    stable/stein"
1819963,2019-03-13 19:52:43 UTC,"Note that even though the API shows the correct AZ when showing the server details in isolation, the 'availability_zone' query parameter when listing servers will be wrong."
1819963,2019-03-13 20:23:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/643155"
1819963,2019-03-27 10:03:56 UTC,"Reviewed:  https://review.openstack.org/643151
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=73aaead294b9df412305abb1cb01aac95477bcc1
Submitter: Zuul
Branch:    master"
1819963,2019-03-28 07:46:41 UTC,"Reviewed:  https://review.openstack.org/643155
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=40f6672f53794b563f4c7e27ede7b59a1d63c14a
Submitter: Zuul
Branch:    master"
1819963,2019-03-28 13:58:29 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/648401"
1819963,2019-03-13 19:55:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/643151"
1819963,2019-03-28 14:21:16 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/648409"
1819963,2019-03-28 14:21:35 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/648410"
1819963,2019-03-28 14:28:12 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/648414"
1819963,2019-03-28 14:28:31 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/648415"
1819963,2019-03-28 14:39:31 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/648421"
1819963,2019-03-28 13:58:53 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/648402"
1819966,2019-04-26 18:56:33 UTC,"Hello,"
1819966,2019-08-09 17:01:03 UTC,This also denies users from adding options like:
1819966,2019-08-12 11:41:45 UTC,"Hi Manuel,"
1819966,2019-08-16 12:17:04 UTC,"Hi Dan,"
1819966,2019-08-16 13:18:48 UTC,"Hi Manuel,"
1819968,2019-11-14 18:50:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1819968,2019-11-14 18:30:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1819968,2019-11-14 18:48:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1819968,2019-12-02 12:51:47 UTC,This bug was fixed in the package linux - 5.3.0-24.26
1819968,2019-12-06 15:57:44 UTC,This bug was fixed in the package linux - 5.3.0-24.26
1819968,2019-12-02 14:09:56 UTC,This bug was fixed in the package linux - 4.4.0-170.199
1819968,2019-12-03 15:42:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1819968,2019-10-19 17:00:15 UTC,I've just installed 5.3.7 and the problem persists.
1819968,2020-01-06 13:12:44 UTC,This bug was fixed in the package linux - 5.0.0-38.41
1819968,2019-12-02 13:04:55 UTC,This bug was fixed in the package linux - 4.15.0-72.81
1819968,2019-10-06 18:22:14 UTC,Exactly the same.
1819968,2019-03-14 22:20:28 UTC,"Since I am not familiar with the procedure of submitting patches upstream, I am hoping that you'll do it for the Lenovo G50 models, like you did it e.g. for the HP Pavilion a few months ago :-)"
1819968,2019-10-06 11:51:44 UTC,"Hi,
I keep trying all kinds of solutions found on the web to fix this but the banding stays on for me? Am I doing something wrong? Is there a method to manually specify the BPP?"
1819968,2019-04-02 11:38:57 UTC,https://lkml.org/lkml/2019/4/1/1633
1819968,2019-03-14 17:23:15 UTC,"I didn't find any indication that the patch was sent to upstream in the archlinux link.
How about sending the patch yourself? It can be fun ;)"
1819968,2019-03-14 16:57:26 UTC,Thank you for your quick response!
1819968,2019-03-14 04:43:45 UTC,"Please send a patch to upstream.
Also, 18514 should change to a hex value."
1819968,2019-03-14 01:00:43 UTC,"$ xrandr --props
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 32767 x 32767
VGA1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 410mm x 230mm
        EDID:
                00ffffffffffff001e6d094c07230800
                071601036c291778ead025a258559c28
                0f5054a76a00314f454f614f81c00101
                010101010101662156aa51001e30468f
                33009ae61000001e000000fd00384b1e
                3d09000a202020202020000000fc0045
                313934320a20202020202020000000ff
                003230374e444e5546503235350a005e
   1366x768      59.79*+
   1280x720      59.97 +
   1024x768      75.08    75.03    60.00
   832x624       74.55
   800x600       75.00    60.32    56.25
   640x480       75.00    60.00
   720x400       70.08
HDMI1 disconnected (normal left inverted right x axis y axis)
        Broadcast RGB: Automatic
                supported: Automatic, Full, Limited 16:235
        audio: auto
                supported: force-dvi, off, auto, on
DP1 disconnected (normal left inverted right x axis y axis)
        Broadcast RGB: Automatic
                supported: Automatic, Full, Limited 16:235
        audio: auto
                supported: force-dvi, off, auto, on
VIRTUAL1 disconnected (normal left inverted right x axis y axis)"
1819968,2019-03-13 21:09:28 UTC,Probably related:
1819968,2019-03-13 21:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1819968,2019-10-06 15:54:06 UTC,"Alexandru,"
1819969,2019-05-19 17:09:56 UTC,fixed in eoan
1819969,2019-03-22 20:24:43 UTC,"The attachment ""patch.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1819969,2019-03-22 20:12:23 UTC,"As per http://packaging.ubuntu.com/html/fixing-a-bug.html, I'm directly including a patch. I've tested this locally and confirmed that these changes enable debugging RISC-V programs running inside very recent versions of QEMU. As noted before, it has also already been applied to the Debian version of the package."
1819973,2019-03-14 16:33:18 UTC,"An update: This appears to be caused by a recent change to MAAS and/or curtin. Our preseed installs canonical-certification-server and its dependencies, and something about this is causing the latest MAAS/curtin to fail when it tries to set up the network."
1819973,2019-03-14 17:18:23 UTC,"From looking at the logs in bug #1819994, I see this:"
1819973,2019-03-14 19:32:46 UTC,"Andres, we've traced the problem to the network-manager package, which gets pulled in by a dependency in canonical-certification-server. Apparently, curtin or cloud-init (I'm not sure which) is now skipping netplan configuration when the network-manager package is installed."
1819973,2019-03-15 19:49:21 UTC,"For anybody following this, we have a workaround in maas-cert-server 0.3.9. If you're affected by this bug, please update maas-cert-server and you should be able to deploy. The drawback is that the Debian package database will be left in an inconsistent state, so you'll need to do a ""sudo apt --fix-broken install"" on the node after deploying it before you can install new packages. (This won't normally be necessary to run certification tests.) A true fix is expected shortly."
1819973,2019-06-19 20:18:47 UTC,"The cloud-init team has released a proper fix for the problem, and it's been pushed out, so starting with maas-cert-server 0.4.3, we've reverted the band-aid workaround introduced in 0.3.9. Problems might still occur if you start up a MAAS server that hasn't been booted in a while and immediately begin a deployment, though. If you experience this problem, wait a while, or temporarily disable the PPA, as noted in comment #1. Reverting this band-aid solution means ""sudo apt --fix-broken install"" should no longer be necessary when trying to install new software."
1819974,2019-03-20 11:41:36 UTC,"If you do the other way, having the multiline in the template instead of the overrides, it still doesn't output the correct multiline."
1819974,2019-04-24 16:45:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655496"
1819974,2019-07-08 22:38:42 UTC,"Reviewed:  https://review.opendev.org/655496
Committed: https://git.openstack.org/cgit/openstack/ansible-config_template/commit/?id=1769158a0e4ce66a8030ed66220268560c08ae0b
Submitter: Zuul
Branch:    master"
1819978,2019-03-15 14:13:13 UTC,The error persists with calls to (GC) but not with calls to (GC :full t).
1819978,2019-03-15 13:18:25 UTC,"You're skating close enough to the edge, I think, that it blowing up only on the third call shouldn't be taken as indicating a bug."
1819978,2019-03-15 12:10:16 UTC,It happens after the third call. The memory of the first two calls won't be reclaimed or is it the memory retained from the result?
1819978,2019-03-15 11:51:37 UTC,"For N = 5000, the list of lists L is ~25 million cons cells, occupying about 400M bytes of memory (on X86-64).  If I recall correctly, the default build for sbcl has a maximum heap size of 500M.   So it shouldn't be surprising you've run out of memory here, since GC needs some room for copying."
1819980,2019-03-14 02:37:27 UTC,"Hi Xav,"
1819980,2019-05-13 04:17:29 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1819983,2019-03-14 21:36:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1819986,2019-03-14 00:24:57 UTC,logged this in storyboard - https://storyboard.openstack.org/#!/story/2005227
1819993,2019-06-06 12:26:54 UTC,"Based on the attached log output I am assuming that you are trying to deploy
a local charm. That would trigger the POST operation that seems to be failing."
1819993,2019-06-28 06:48:30 UTC,"Hi Achilleas,"
1819993,2019-07-29 18:20:44 UTC,"For reference, here is a similar bug for snaps which was fixed some time ago. It is also about macaroon-bakery:"
1819994,2019-03-19 23:01:17 UTC,"Amy, I think you're confusing the MAAS version (which is 2.4.2 on one of our installations) and the maas-cert-server package version (the latest of which is 0.4.0). The maas-cert-server 0.3.9 package includes a workaround (but NOT A FIX) for this bug, and 0.4.0 provides some unrelated improvements, so the installation SHOULD succeed after you've upgraded maas-cert-server to version 0.3.9 or 0.4.0. If it's still failing, then it could be you'll need to apply the workaround described by Ryan Harper in comment #15, which is different from the workaround in maas-cert-server 0.3.9 and 0.4.0. (Post back if you need help applying Ryan's workaround.) It could also be that you're looking at a completely different problem."
1819994,2019-03-20 10:38:20 UTC,"hi Rod,"
1819994,2019-04-22 22:46:43 UTC,"This bug is fixed with commit 5de83fc5 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=5de83fc5"
1819994,2019-05-10 18:08:35 UTC,"This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1819994,2019-05-13 09:27:29 UTC,"Sorry for the later reply, the issue does not occur with current Cloud-init v. 18.5-45-g3554ffe8-0ubuntu1~18.04.1. please move on and close it. thanks a lot."
1819994,2019-06-20 10:16:23 UTC,"thanks for your kindly update, i will do the double check with the latest one."
1819994,2019-06-19 15:54:38 UTC,"Just a heads up, the fix is now in -updates, I've tested this locally on a couple deployments and it seems to resolve the issue we had before.  Asking my team to verify on a couple more deployments for due diligence."
1819994,2019-06-19 19:10:25 UTC,"I've tested this on three nodes on two MAAS servers (my own home MAAS server and maastiff, our MAAS server in the certification lab), using both 18.04 and 19.04. It looks good to me."
1819994,2019-03-19 11:20:07 UTC,"hi Jeff,"
1819994,2019-07-23 16:08:05 UTC,"Hi Amy et al,"
1819994,2019-05-13 15:28:26 UTC,"Hi Amy, it's likely that you're still using our patched tooling that includes a workaround.  cloud-init 18.5 should not work."
1819994,2019-03-18 15:58:34 UTC,"Amy: Also, could you send me a tarball containing /etc/maas/preseeds ??"
1819994,2019-03-15 20:51:06 UTC,"On Fri, Mar 15, 2019 at 2:50 PM Rod Smith <email address hidden> wrote:"
1819994,2019-03-18 09:54:52 UTC,"hi Jeff and all,"
1819994,2019-03-14 11:38:41 UTC,Looks like it might be an issue either in curtin or MAAS based on the network configuration.
1819994,2019-03-14 16:22:02 UTC,"FYI, I've added a cert task for this.  I don't know for sure this is curtin, it looks like something may have changed in one of the hundreds of dependency packages that checkbox pulls in causing curtin to fail."
1819994,2019-03-18 15:54:20 UTC,"Hi Amy,"
1819994,2019-03-14 19:36:05 UTC,"We've traced the problem to the network-manager package, which gets pulled in by a dependency in canonical-certification-server. Apparently, curtin or cloud-init (I'm not sure which) is now skipping netplan configuration when the network-manager package is installed."
1819994,2019-03-14 21:29:20 UTC,"Neither curtin, nor cloud-init will *skip* generating networking.  However, if there exists some additional netplan config in the target system that cloud-init is not aware (maybe  provided in the NetworkManager package (or something else)) then there may be a conflict in the configuration that prevents netplan apply from bringing up the network."
1819994,2019-03-14 19:29:51 UTC,"We have a bug for this as well, 1189973 but duping for that kills the MAAS (possibly curtin) task. So I un-duped it for now"
1819994,2019-03-15 14:51:10 UTC,"2019-03-14 17:32:34,606 - __init__.py[DEBUG]: Selected renderer 'sysconfig' from priority list: None"
1819994,2019-03-15 19:19:25 UTC,You can workaround this issue by including the following curtin config when deploying.
1819994,2019-03-15 19:44:41 UTC,"Thanks for the quick fix, Ryan! I've confirmed that your curtin config workaround in comment #15 works. Do you have an estimate for how long it'll be before a fix goes live? (I ask so we can plan whether we should push your workaround through one of the certification packages.)"
1819994,2019-03-14 22:43:47 UTC,"I've attached the /var/log/cloud-init.log file from a node that failed deployment. (This is a different node from the one that generated the earlier logs.) The /etc/netplan directory is empty, and neither there is no /run/systemd directory on this node that failed to deploy."
1819995,2019-03-15 05:18:50 UTC,Hmm well in theory it is do-able. You'd basically need to add hooks to the kindle and kobo drivers to initialize from an externally supplied path instead of the open() function. And modify the eject functionality similarly. Then add some config to the folder driver to tell it which device to emulate. Then modify all the API endpoints in the folder driver to delegate to the configured device instead.
1819999,2019-09-24 09:48:25 UTC,"This one should already fixed in stock Ubuntu.
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242
https://launchpad.net/ubuntu/+source/xf86-input-wacom/1:0.36.1-0ubuntu2"
1819999,2019-09-24 10:11:13 UTC,Not in bionic yet need SRU.
1820000,2019-05-14 12:03:03 UTC,"Depending on the configuration of the charm, this is by design. Can you please include a bundle that you are using in which you see this so we can determine if this is a charm bug or a misunderstanding of the charm configuration options?"
1820000,2019-07-14 04:17:36 UTC,[Expired for OpenStack swift-storage charm because there has been no activity for 60 days.]
1820001,2019-03-14 04:25:59 UTC,ps axu | awk '$8 ~ /^D/'
1820001,2019-03-14 04:36:24 UTC,It seems that simple
1820003,2019-05-14 20:51:21 UTC,Apologies for the cut and paste fail above. I don't seem to have edit rights.
1820007,2020-01-06 10:33:49 UTC,This issue was fixed in the openstack/os-brick 2.5.9 release.
1820007,2020-01-06 10:24:03 UTC,This issue was fixed in the openstack/os-brick 2.8.3 release.
1820007,2020-01-06 10:23:05 UTC,This issue was fixed in the openstack/os-brick 2.10.1 release.
1820007,2019-12-14 16:59:35 UTC,"Reviewed:  https://review.opendev.org/697117
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=1f811c412a172d5456d37cc748bc217fc4718cbf
Submitter: Zuul
Branch:    stable/rocky"
1820007,2019-12-13 18:11:39 UTC,This issue was fixed in the openstack/os-brick 2.11.0 release.
1820007,2019-12-13 14:24:26 UTC,Still seeing some failures on master:
1820007,2019-12-12 15:51:39 UTC,"Reviewed:  https://review.opendev.org/697116
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=d1f84dfd897d35053d39c22ae484f6586d1268bd
Submitter: Zuul
Branch:    stable/stein"
1820007,2019-12-09 23:12:20 UTC,"Reviewed:  https://review.opendev.org/697115
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=d8ed21e7d25f67c6d2bfe71515723f68ce15b887
Submitter: Zuul
Branch:    stable/train"
1820007,2020-02-18 14:45:38 UTC,"Reviewed:  https://review.opendev.org/697118
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=8972aa4add00e8c27642e5a39ee5dd3aedb39d9f
Submitter: Zuul
Branch:    stable/queens"
1820007,2019-12-03 15:40:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/697118"
1820007,2019-12-03 15:39:49 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/697116"
1820007,2019-12-03 15:39:36 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/697115"
1820007,2019-12-03 15:04:00 UTC,"Reviewed:  https://review.opendev.org/695564
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=331316827a60aa50ee26be08a06027525f5194ef
Submitter: Zuul
Branch:    master"
1820007,2019-11-26 20:28:35 UTC,https://review.opendev.org/#/c/695564/
1820007,2019-09-19 17:40:39 UTC,This is what Lee Yarwood said about the problem when investigating the failed CI job run:
1820007,2019-09-19 16:13:56 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22os_brick.exception.VolumeDeviceNotFound%3A%20Volume%20device%20not%20found%20at%20%2Fdev%2Fdisk%2Fby-id.%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d
1820007,2019-09-19 16:13:26 UTC,"I don't know if this is the same thing, but we've seen CI failures with a luks encrypted volume with a similar error:"
1820007,2019-12-03 15:40:06 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/697117"
1820008,2019-06-10 04:17:38 UTC,[Expired for tripleo because there has been no activity for 60 days.]
1820008,2019-04-10 15:50:20 UTC,"Usually this error
error: Failed to connect socket to '/run/user/1001/libvirt/libvirt-sock': No such file or directory"
1820008,2019-03-14 20:55:23 UTC,"Using the below links to check if it works :
https://wiki.libvirt.org/page/Failed_to_connect_to_the_hypervisor
https://wiki.libvirt.org/page/SSHSetup"
1820008,2019-03-14 20:57:07 UTC,"there was also another error : no acceptable C compiler found in $PATH
so ran > yum groupinstall ""Development Tools"""
1820011,2019-03-14 12:09:57 UTC,Thanks for filing this bug in Ubuntu.
1820011,2019-05-14 04:17:20 UTC,[Expired for python3-defaults (Ubuntu) because there has been no activity for 60 days.]
1820021,2019-03-26 13:21:24 UTC,"So nova-lxd doesn't support the console on the Horizon dashboard.  I'm going to make this a wishlist item, as it negatively affects people experimenting with OpenStack + nova-lxd when using conjure-up."
1820023,2019-03-18 14:52:27 UTC,Please try running the following command in a terminal:
1820023,2019-05-18 04:17:27 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1820031,2019-03-14 09:52:38 UTC,"Assuming your GUI is Gnome Shell, please..."
1820031,2019-03-14 11:23:51 UTC,Nothing new comes out in the crash report.
1820031,2019-03-14 13:29:02 UTC,"the kernel driver ""crashed"", which is why the screen froze"
1820031,2019-05-14 04:17:24 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1820032,2019-03-14 09:35:48 UTC,Requested new release in https://review.openstack.org/#/c/643258
1820038,2019-03-18 12:11:38 UTC,Thank you for the excellent test example.  Point 2 should not fail.
1820038,2019-03-16 21:01:49 UTC,"I can't clearly understand what's going on, but..
Try to set in Route-Interactive Router Settings - Mode: Highlight collisions, and check Allow DRC violations. With this setting you can drag T1 track any close (even onto) the GND track."
1820038,2019-03-18 10:33:33 UTC,"Thanks for reply. I forgot about one important thing...  I am trying to catch a problem that occurs when I dragging several tracks at the same time. It is impossible in ""Highlight collisions"" mode."
1820038,2019-08-28 15:50:51 UTC,I can confirm same behavior for version:
1820040,2019-03-15 14:33:48 UTC,"Hi Danilo,"
1820040,2019-03-15 15:13:33 UTC,"Hi Olivier,"
1820040,2019-03-15 15:52:10 UTC,"Thank you, Olivier."
1820040,2019-03-15 15:44:29 UTC,"Thanks,"
1820041,2019-03-14 11:55:37 UTC,"Sorry, the above hooks/config-changed run fixed ceph.conf, but the rbd driver could not be initialized. I had to remove/add the relation between cinder and ceph-mon to fix it."
1820044,2019-03-14 11:49:02 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/643302"
1820044,2019-03-14 12:58:37 UTC,"Change abandoned by Tom Barron (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/643302
Reason: in favor of https://review.openstack.org/#/c/642927"
1820044,2019-03-14 12:58:39 UTC,"https://review.openstack.org/#/c/642927/1 is already in place to fix this, sorry for not merging it in line with the patch that introduced this issue."
1820044,2019-03-14 16:29:03 UTC,https://review.openstack.org/#/c/642927/1 is merged now.
1820048,2019-04-06 06:59:14 UTC,"Ubuntu 18.10. My resolvconf package is currently 1.79ubuntu10.18.10.3, and with this it works. What the version number was that solved it I don't know, but it was the one released around the day I reported the bug solved."
1820048,2019-03-14 12:15:24 UTC,with new kernel:
1820048,2019-03-15 14:47:25 UTC,A new resolve package with today's update solved the problem; apparently it was an issue with name resolving.
1820048,2019-04-05 20:42:53 UTC,"Please add information on what Ubuntu distribution you experienced this problem, and what ""resolve package"" and version that solved it. Thanks!"
1820048,2019-06-06 04:17:19 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1820053,2019-03-15 10:27:17 UTC,I think this can be skipped by checking the release name.
1820054,2019-04-01 11:27:09 UTC,"Hi, Could you attach a debug log? https://manual.openlp.org/troubleshooting.html#mac-os-x"
1820055,2019-04-23 15:37:08 UTC,"Once snapd fixes the issue, snapcraft work can being to make sure we have end to end integration. Removing from the milestone until then."
1820055,2019-04-17 18:14:22 UTC,I agree we want to lift this restriction.
1820055,2019-04-08 12:32:21 UTC,I encountered this problem again with `command: bin/guvcview --audio=pulse` (the `=` character seems to be the trigger)
1820055,2019-09-25 21:59:03 UTC,It looks like the characters being requested here are probably:
1820055,2019-04-17 18:11:43 UTC,"We are following the snapd restrictions now for command, I will add a snapd task to sort this."
1820057,2019-04-11 18:47:33 UTC,"Fixed in revision 3c11b89e4c7bacdfbc878fa5e0fc7d64c9e5ebfd
https://git.launchpad.net/kicad/patch/?id=3c11b89e4c7bacdfbc878fa5e0fc7d64c9e5ebfd"
1820057,2019-04-11 09:23:31 UTC,"Rescan the disk in not the way to go, because it can be a long process on Windows.
Please avoid it in any case."
1820057,2019-04-11 10:05:30 UTC,"@JP, I should have been clearer: we only re-scan the files inside the library directory, but even that can be slow.  But there's no way to avoid it all-together because Unix tools don't update the directory's timestamp when modifying files within it."
1820057,2019-04-11 00:25:35 UTC,"It's expensive to scan the disk to see if things have changed.  However, we do re-scan if you close and re-open the Footprint Editor."
1820058,2019-03-17 19:27:43 UTC,I fond the problem. It was disk configuration for ceph. I misspelled a disk.
1820059,2019-05-27 13:13:16 UTC,"Fixed in revision 6936effaa7e26813f2938a759068b4d9f45a2e5e
https://git.launchpad.net/kicad/patch/?id=6936effaa7e26813f2938a759068b4d9f45a2e5e"
1820059,2019-03-14 19:43:52 UTC,Our general approach with undo/redo has been to store the circuit changes not the presentation.
1820059,2019-04-26 09:16:07 UTC,"I understand that it wasn't part of the original design, and therefore isn't a /coding/ bug."
1820060,2020-11-09 11:18:28 UTC,"Late, but for others who stumble across this: I tried with multiline string syntax (“|”) back in late 2019, but didn't work. But FWIW, I just re-checked with a core20-based gadget, latest snapd/mir-kiosk versions and this seems to work:"
1820060,2019-11-27 04:17:22 UTC,[Expired for snapd because there has been no activity for 60 days.]
1820060,2019-09-27 10:01:22 UTC,"Have you tried with ""|"" to denote multiline string in the defaults section, e.g."
1820061,2019-03-31 23:21:55 UTC,"there is no information about the issue, you're only stating that there is an issue."
1820061,2019-05-31 04:17:20 UTC,[Expired for gcc-7 (Ubuntu) because there has been no activity for 60 days.]
1820062,2019-05-19 19:21:37 UTC,I agree. The packaging looks now fine.
1820062,2019-05-11 17:54:54 UTC,Unfortunately the upgrade from 6.1.5 to 6.1.6 is actually broken. My apologies for the false verification. I will prepare a fix asap.
1820062,2019-05-16 12:09:48 UTC,"Hello Gašper, or anyone else affected,"
1820062,2019-05-16 12:10:29 UTC,"Hello Gašper, or anyone else affected,"
1820062,2019-05-16 17:29:31 UTC,"Upgraded libreoffice from 1:6.1.5-0ubuntu0.18.10.1 to 1:6.1.6-0ubuntu0.18.10.2 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice."
1820062,2019-05-17 20:52:08 UTC,Hello.
1820062,2019-05-17 21:18:18 UTC,"I made new video demonstrating current situation - better, but still issues (see previous post)"
1820062,2019-05-17 22:59:28 UTC,"Hi Gašper, thank you for the update."
1820062,2019-05-10 09:51:12 UTC,"Upgraded libreoffice to 1:6.1.6-0ubuntu0.18.10.1 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice."
1820062,2019-05-19 20:21:46 UTC,"Please log the bug here against the Ubuntu package first. Then, if we find that it’s not Ubuntu-specific, we can link it to an upstream bug. Thanks again!"
1820062,2019-03-20 11:57:31 UTC,Note: adding gstreamer1.0-gtk3 to the stage packages fixes video playback in the libreoffice snap. I have triggered a new snap build with that change (https://git.launchpad.net/~libreoffice/+git/libreoffice-snap/commit/?id=aeb8d4444b538564d312c0a4ffc258da3abe02a5).
1820062,2019-05-23 08:27:34 UTC,"The verification of the Stable Release Update for libreoffice has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820062,2019-05-23 08:27:45 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.1.6-0ubuntu0.18.10.2
1820062,2019-05-23 14:51:06 UTC,"Hello Gašper, or anyone else affected,"
1820062,2019-05-24 16:00:24 UTC,"Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.5 to 1:6.0.7-0ubuntu0.18.04.6 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the [Test Case] now passes."
1820062,2019-05-30 08:44:53 UTC,This bug was fixed in the package libreoffice - 1:6.0.7-0ubuntu0.18.04.6
1820062,2019-06-25 16:18:41 UTC,"Hello Gašper, or anyone else affected,"
1820062,2019-06-26 09:01:47 UTC,"Upgraded libreoffice-l10n from 1:6.0.7-0ubuntu0.18.04.6 to 1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the test case passes."
1820062,2019-07-03 13:35:28 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.0.7-0ubuntu0.18.04.7
1820062,2019-05-09 15:19:11 UTC,"Hello Gašper, or anyone else affected,"
1820062,2019-05-23 08:27:14 UTC,This bug was fixed in the package libreoffice - 1:6.1.6-0ubuntu0.18.10.2
1820062,2019-05-09 15:17:55 UTC,"Hello Gašper, or anyone else affected,"
1820062,2019-03-15 19:49:57 UTC,"I disagree with ""invalid"" bug in launchpad. Problem in in packaging. User should not manually install "" gstreamer1.0-gtk3"" package"
1820062,2019-04-02 20:22:07 UTC,Spin-off bug filed by Sam: bug #1821849.
1820062,2019-03-14 08:43:13 UTC,"Description:
When embeding videos in Impress presentation when vcl ""gtk3"" is used"
1820062,2019-03-14 08:55:14 UTC,"probably missing the gstreamer gtksink plugin on your machine (which works great, so install that if you can, package gstreamer1-plugins-good-gtk in fedora f.e), so its falling back to the non-gtksink implementation. I think Mark was making improvements to that fallback recently"
1820062,2019-03-14 09:12:59 UTC,"Thanks for reply. The installing package ""gstreamer1.0-gtk3"" in ubuntu 18.04 did help. It's working now."
1820062,2019-03-14 10:59:56 UTC,"Hi,"
1820062,2019-03-14 11:08:57 UTC,Thanks for reply.
1820062,2019-03-14 12:35:36 UTC,"For me the same problem as Gasper described. My system: LO 6.1.5.2 on Ubuntu 18.04.
After installing gstreamer1.0-gtk3 the problem is solved."
1820062,2019-03-14 20:16:03 UTC,Close as WFM after comment 4 and comment 5
1820062,2019-05-09 12:23:06 UTC,"The gstreamer1.0-gtk3 new binary dependency is currently in universe, while libreoffice is in main. But since the source of gstreamer1.0-gtk3 (gst-plugins-good1.0) is already in main, I will simply promote it as well as per our policy."
1820062,2019-03-19 20:41:59 UTC,"The source package for gstreamer1.0-gtk3 (gst-plugins-good1.0) is in main though, so that should be fine."
1820062,2019-03-19 20:24:54 UTC,Thanks for the report Gašper.
1820062,2019-03-20 20:48:56 UTC,The libreoffice snap version 6.2.2.2 in the candidate channel has that change. I tested and confirms that video playback is functional again.
1820062,2019-03-21 10:12:42 UTC,"As done in debian, it is libreoffice-gtk3 that should recommend gstreamer1.0-gtk3 (https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/a7307bd4d2ab671a47573e8b9b8f78a295e223e5)."
1820062,2019-03-21 10:15:36 UTC,Archive administration considerations were discussed on IRC (#ubuntu-release):
1820062,2019-03-21 16:32:55 UTC,I am glad that the issue is being solved.
1820062,2019-03-21 17:33:33 UTC,"This will require a Stable Release Update, of which a prerequisite is for the fix to be present in the development series."
1820062,2019-03-25 15:53:39 UTC,This bug was fixed in the package libreoffice - 1:6.2.2-0ubuntu1
1820062,2019-03-26 03:58:21 UTC,"The above image shows what happens when LibreOffice 6.2.2.2 Impress has an inserted video.  When the video is started, the previous slide is shown on top of the video as it is played.  Not a good view!!!!  This happens on Kubuntu 19.04 and I have added all the packages suggested in the above ""solution""."
1820062,2019-03-26 09:15:30 UTC,"Sam,
I found out similar issues also when starting slideshow with slide that contains video directly (shift + F5). This issue is not present if i start slideshow with first slide.
I also noticed if the video is not entirely inside slide - the video acts weirdly when in presentation."
1820068,2019-06-24 12:34:27 UTC,"Hello Jamie, or anyone else affected,"
1820068,2019-06-24 22:40:38 UTC,"FYI, I tested this and 2.13.2-9ubuntu6.1 fixes this bug."
1820068,2019-07-29 14:03:17 UTC,This bug was fixed in the package apparmor - 2.13.2-9ubuntu6.1
1820068,2019-06-07 12:09:03 UTC,This bug was fixed in the package apparmor - 2.13.2-9ubuntu7
1820068,2019-07-29 14:03:26 UTC,"The verification of the Stable Release Update for apparmor has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820068,2019-03-14 20:59:12 UTC,Adding an Ubuntu 19.04 task in anticipation of the 2.13.2 upload.
1820068,2019-03-14 14:40:13 UTC,I can say that this was also not introduced by these latest commits:
1820068,2019-03-14 14:04:23 UTC,I verified this does not affect Ubuntu 18.04 which uses 2.12.
1820068,2019-06-06 21:49:02 UTC,Upstream patch is here: https://gitlab.com/apparmor/apparmor/merge_requests/385
1820072,2019-03-26 08:19:24 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/449148
1820072,2019-03-18 01:32:23 UTC,"ok, first part should be much easier if we can use some command to query"
1820072,2019-03-15 03:41:55 UTC,"I assume you are talking about
https://www.ibm.com/support/knowledgecenter/en/SSB27U_7.1.0/com.ibm.zvm.v710.hcpa6/hcpa6dna.htm?"
1820072,2019-03-15 07:50:30 UTC,"That is the DNA, available since August 2017 on z/VM per APARs VM65925, VM65926, and VM65931."
1820074,2019-03-14 14:51:22 UTC,"The crash is in XorgLogOld.txt, and the backtrace reproduced here:"
1820074,2019-03-14 15:14:50 UTC,Also crashes with nVidia using nouveau drivers (see attached log)
1820074,2019-04-07 17:44:37 UTC,Also affects Disco
1820075,2019-10-15 03:50:08 UTC,This bug was fixed in the package linux-oracle - 5.3.0-1002.2
1820075,2019-04-02 10:46:31 UTC,This bug was fixed in the package linux-gcp - 4.18.0-1008.9
1820075,2019-05-30 20:44:19 UTC,linux-azure: https://lists.ubuntu.com/archives/kernel-team/2019-May/101009.html
1820075,2019-06-25 13:08:32 UTC,This bug was fixed in the package linux-azure - 4.15.0-1049.54
1820075,2019-06-26 20:48:30 UTC,This bug was fixed in the package linux-azure - 5.0.0-1010.10
1820075,2019-06-26 20:49:11 UTC,This bug was fixed in the package linux-azure - 4.18.0-1023.24
1820075,2019-06-26 20:50:52 UTC,This bug was fixed in the package linux-azure - 4.18.0-1023.24~18.04.1
1820075,2019-07-02 16:02:34 UTC,This bug was fixed in the package linux-azure - 5.0.0-1010.10
1820075,2019-10-09 20:32:41 UTC,This bug was fixed in the package linux-gcp - 5.0.0-1020.20~18.04.1
1820075,2019-10-10 13:21:06 UTC,This bug was fixed in the package linux-oracle - 5.0.0-1004.8
1820078,2019-06-04 04:17:36 UTC,[Expired for totem (Ubuntu) because there has been no activity for 60 days.]
1820078,2019-04-05 01:45:52 UTC,"Alternatively, please just try adding this to your /etc/environment:"
1820078,2019-04-04 12:22:30 UTC,Do you steps to trigger the issue? Could you try to get a valgrind log? (https://wiki.ubuntu.com/Valgrind )
1820078,2019-03-14 15:26:17 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f75c1e67952 ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f75c1e659cd ""corrupted double-linked list"") at malloc.c:5352
 unlink_chunk (p=p@entry=0x7f75780e95d0, av=0x7f7578000020) at malloc.c:1470
 _int_free (av=0x7f7578000020, p=0x7f75780e9480, have_lock=<optimized out>) at malloc.c:4350
 tcache_thread_shutdown () at malloc.c:2977"
1820080,2019-06-13 19:04:12 UTC,"See https://snapcraft.io/juju-helpers for a Juju plugin (the juju-bundle executable in that snap) that allows interacting with a bundle as a whole, including deploying it after first building each charm in the bundle."
1820083,2021-02-16 23:45:14 UTC,Resubmitted patches for verification
1820083,2020-08-18 16:58:41 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1820083,2021-01-04 20:31:26 UTC,"The attachment ""lp1820083-tlsparams-bionic.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1820083,2021-01-19 04:56:46 UTC,"Fixed in Ubuntu Hirsute.
---"
1820083,2021-02-16 21:31:26 UTC,debdiff for groovy
1820083,2021-02-16 21:41:04 UTC,groovy debdiff
1820083,2021-02-16 23:37:12 UTC,bionic debdiff
1820083,2021-02-16 23:44:52 UTC,focal debdiff
1820083,2021-02-17 18:39:30 UTC,revert test case description
1820085,2019-05-23 17:46:58 UTC,"This appears to only be an issue when you move and/or rotate a zone.  If we refill on changing the zone outline, we should probably refill when moving or rotating a zone as well."
1820085,2019-05-28 14:08:14 UTC,"@Jon, I still see this with 5.1.2-83-g356ccd031 on my laptop with ubuntu 18.04.  Whenever I move or rotate a zone, it doesn't automatically refill but if I modify the shape of the zone it does refill just like comment #8."
1820085,2019-05-11 07:02:03 UTC,"There appears to be an additional side effect, all though the zone refresh is fixed, moving a zone to a new location will not repour it until it is selected and a changed."
1820085,2019-07-08 21:21:40 UTC,For now we've removed the auto-fill on move/rotate/etc.  We may later implement a setting that controls it.
1820085,2019-07-06 22:27:39 UTC,See also the discussion on the dev list: https://lists.launchpad.net/kicad-developers/msg41394.html
1820085,2019-05-03 07:13:42 UTC,Previous behavior for comparison (was able to replicate using provided commit)
1820085,2019-05-25 14:09:18 UTC,I can't reproduce the behavior from Andrey's post #8 -- Wayne can you still reproduce it?  Is it OS-dependent somehow?
1820085,2019-03-15 17:29:45 UTC,I found a corollary to this that is still present.  I attach an example board.
1820085,2019-03-15 17:05:07 UTC,Board attached.
1820085,2019-05-03 07:11:57 UTC,"Hi Seth,"
1820085,2019-03-15 17:04:00 UTC,Hi JP-
1820085,2019-03-15 11:46:27 UTC,"Hi Seth,"
1820086,2019-03-19 11:31:07 UTC,"Hello Matthias, or anyone else affected,"
1820086,2019-03-19 11:33:12 UTC,"Hello Matthias, or anyone else affected,"
1820086,2019-04-11 16:24:31 UTC,"Hello,"
1820086,2019-04-16 16:37:09 UTC,This bug was fixed in the package icedtea-web - 1.8-0ubuntu8~18.04
1820086,2019-04-16 16:52:20 UTC,This bug was fixed in the package icedtea-web - 1.8-0ubuntu8~18.10
1820091,2019-03-14 17:02:36 UTC,"Hi Jeff,"
1820091,2019-03-14 17:32:57 UTC,Curtin sends a tar full of its configuration as well as logs to MAAS. We have an article on discourse explaining how to access the logs over the API
1820091,2019-05-14 04:17:21 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1820099,2019-03-14 18:38:33 UTC,"The problem is you have 2 boards, not only one.
(There is a small board inside the main board: see the edge cut layer))."
1820099,2019-03-14 18:30:36 UTC,"Sent to your email. Some 3D models will be missing.
Radovan Blažek (blazra) was able to replicate this bug. (Same OS and kicad build, pcb file was enough.)"
1820099,2019-03-14 18:23:57 UTC,I can reproduce it on windows but only in the ray tracing mode.  In the normal mode it renders just fine.
1820099,2019-03-15 19:37:47 UTC,I'm not sure about the odd of getting this fixed.  Does the person who wrote the ray tracing code even have time to look at it?  We should make the ray tracing work the same way as the normal rendering.
1820099,2019-03-14 17:39:02 UTC,"Sure, I even tried ""Reset to Default Settings""."
1820099,2019-03-14 17:23:10 UTC,"Can you attach an image of what your ""Display Options"" window looks like?"
1820099,2019-03-14 17:51:11 UTC,"I'm unable to replicate this locally.  Would you be able to attach your project to this report?  Alternatively, if you prefer, you can send it to me directly (my e-mail is listed in my profile on Launchpad)."
1820101,2019-03-28 13:56:50 UTC,"'juju restore-backup' is currently broken if the original backup was taken from an HA controller. This is due to a variety of reasons, mostly around the new controller isn't going to be HA, so a few of the restored bits bring up a configuration that says ""you should be HA, wait for the other agents."""
1820101,2019-03-28 15:35:57 UTC,"I would be happy to test any steps you have. As at the moment my juju installation is broken and has left me trying to manually maintain over 120 agents and their services. I will note, that everything is working correctly, I just cannot do any architecture changes, as the agents will still overwrite anything I attempt to change in the configs. I was just about to disable all of the agents, but if your steps work then I wont need to, if not I will go ahead with that."
1820101,2019-04-03 11:53:31 UTC,https://discourse.jujucharms.com/t/manual-steps-to-restore-a-backup/1330
1820102,2019-03-20 18:35:04 UTC,I can't reproduce this on master branch
1820102,2019-04-09 08:41:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651138"
1820102,2019-07-05 09:56:25 UTC,"Reviewed:  https://review.opendev.org/651138
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=1ac40ea95f000b1eb1915e74082f0be99698ac83
Submitter: Zuul
Branch:    master"
1820102,2019-09-13 16:42:18 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.
1820106,2020-02-17 04:26:26 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1820106,2019-04-12 20:22:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820106,2019-03-14 18:34:08 UTC,And how do I leave the option disabled in the settings?
1820109,2019-03-15 06:45:39 UTC,"This is a known limitation, quoting from https://forum.snapcraft.io/t/snap-layouts/7207"
1820115,2019-06-19 17:48:38 UTC,"Retested
Verdict: Passed"
1820115,2019-03-15 18:36:40 UTC,Marking as release gating; related to the cluster networking feature.
1820115,2019-03-15 18:37:09 UTC,Please include Teresa Ho on the code inspection. Any questions during investigation can also be directed to her.
1820115,2019-03-18 09:34:55 UTC,"Chris, for one question: is this new issue or regression issue?"
1820115,2019-03-18 15:33:47 UTC,This is related to SB: https://storyboard.openstack.org/#!/story/2004273
1820115,2019-03-21 06:57:34 UTC,"@Teresa, @Ghada,"
1820115,2019-03-28 19:11:32 UTC,"(1) The validation should be done in the API server, not the shell.
(2)&(3) The deletion of any of the networks should be blocked after the first controller is unlocked."
1820115,2019-04-18 09:01:39 UTC,"@Teresa, @Ghada,
Do we have a fix already available to this issue? If so, would you please kindly add the review link? Thanks."
1820115,2019-04-18 14:53:10 UTC,"@Kailun, There is no fix yet. Huifeng is assigned this bug."
1820115,2019-05-22 22:03:24 UTC,"Reviewed:  https://review.opendev.org/657557
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=bc39f1ea3c2f2c7e86c0b1c52c98089e3b67a403
Submitter: Zuul
Branch:    master"
1820126,2019-11-02 04:17:36 UTC,[Expired for snapd because there has been no activity for 60 days.]
1820126,2019-09-02 16:09:47 UTC,"I cannot reproduce, looks like whatever that was, it got fixed, can you confirm?"
1820128,2019-03-15 19:58:15 UTC,"I restored and tested the one I found in the Recycle bin but couldn't replicate the issue. The config folder may have been deleted even after the problem went away, I'm not sure anymore."
1820128,2019-05-15 04:17:47 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1820128,2019-03-15 19:40:15 UTC,"@eelik, do you still have the config folder used when the issue occurred?  It's possible that there is a specific configuration that causes the issue."
1820128,2019-03-14 22:11:49 UTC,"Strange, cpuld you try to install to a new location and open the pcbnew from there?"
1820128,2019-03-14 23:15:23 UTC,I uninstalled everything and deleted the config directory and reinstalled. Now it works.
1820130,2019-06-18 16:13:46 UTC,"The verification of the Stable Release Update for modem-manager-gui has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820130,2019-06-18 16:16:46 UTC,This bug was fixed in the package modem-manager-gui - 0.0.19.1-1ubuntu0.19.04.1
1820130,2019-06-18 16:13:42 UTC,This bug was fixed in the package modem-manager-gui - 0.0.19.1-1ubuntu0.18.04.1
1820130,2019-06-18 15:49:32 UTC,"I tested in disco, 0.0.19.1-1build1 crashes as described, 0.0.19.1-1ubuntu0.19.04.1 does not."
1820130,2019-06-18 12:11:05 UTC,We still need someone to perform the verification in Disco.
1820130,2019-06-11 05:28:55 UTC,"Jan, no the Disco package needs to be tested on Disco.  If you don't have access to another computer, a live CD, or virtual machine with USB pass-through could work."
1820130,2019-06-10 23:01:43 UTC,"Graham, I'm on Bionc. Can I test the disco package on bionic?"
1820130,2019-06-10 22:40:13 UTC,"modem-manager-gui (0.0.19.1-1ubuntu0.18.04.1) bionic-proposed – tested, fixes the bug."
1820130,2019-06-10 10:27:17 UTC,"Hi Jan
Yes, this package should be identical to the one in my PPA, but please test again with the official version from the archive."
1820130,2019-06-07 09:07:23 UTC,"Hello David, or anyone else affected,"
1820130,2019-06-09 22:49:47 UTC,"Hi Timo, is this package the same that was in Graham PPA https://launchpad.net/~ginggs/+archive/ubuntu/sru? I've already tested it and it fixes the bug."
1820130,2019-06-04 20:05:07 UTC,"The ""Regression Potential"" portion of the SRU template is to indicate how things might go wrong to improve testing of the Stable Release Update. Can you please update the regression potential with something that meets that criteria?"
1820130,2019-06-02 10:42:57 UTC,I don't think Cosmic needs to be targeted as it does not have modemmanager 1.10.
1820130,2019-05-31 22:49:32 UTC,"Hi Graham, I have installed modem-manager-gui from your PPA. It solves the problem. But unfortunately my problem with suspend is still present.
Modem-manager-gui in specific circumstances blocks system from suspend.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461"
1820130,2019-05-29 10:12:06 UTC,I've since updated to Eoan.  Don't know under what circumstances the bug triggers exactly but startup here appears to work currently.
1820130,2019-05-29 09:55:39 UTC,This sounds a lot like Debian bug #922608 [1] which is fixed in Eoan.
1820130,2019-05-28 23:08:36 UTC,"Same on Ubuntu 18.04 (4.18.0-20-generic), Modem Manager Gui(0.0.19.1-1).
This bug probably revealed another one – Modem Manager Gui prevents from suspend on Ubuntu 18.04 when mobile network connected and no WiFi connection.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461"
1820130,2019-05-17 00:20:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820130,2019-03-14 21:55:41 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8a1b39b952 ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f8a1b39d5a0 ""munmap_chunk(): invalid pointer"") at malloc.c:5352
 munmap_chunk (p=<optimized out>) at malloc.c:2840
 mmgui_module_devices_update_location (mmguicore=mmguicore@entry=0x55e1c841eeb0, device=device@entry=0x55e1c849d690) at mm07.c:1692
 mmgui_module_devices_update_location (device=0x55e1c849d690, mmguicore=0x55e1c841eeb0) at mm07.c:2013"
1820130,2019-06-07 09:05:51 UTC,"Hello David, or anyone else affected,"
1820131,2020-03-07 10:39:17 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1820132,2019-04-04 23:31:35 UTC,Here's the better changelog entry:
1820132,2019-04-11 17:06:09 UTC,To test this with whoopsie-upload-all one could do something like the following:
1820132,2019-04-04 19:36:12 UTC,This bug was fixed in the package apport - 2.20.10-0ubuntu25
1820132,2019-03-14 22:01:37 UTC,"apport does not depend on gdb so it's possible, even likely, that gdb is not installed on the system reporting the crash. Subsequently, report.add_gdb_info will fail and the docstring indicates that this should ""Raises ... OSError if calling gdb fails"" however the docstring is currently a liar perhaps because of a change I made. Regardless this should be sorted out. Here's the Traceback:"
1820132,2019-03-28 19:56:45 UTC,"Actually, I was looking at the wrong thing what's really missing is the executable which crashed from the top of the function gdb_command:"
1820133,2019-09-14 09:20:03 UTC,これはGNOME Shellの問題だそうです。
1820133,2019-10-30 12:19:50 UTC,"文字がはみ出て隠れる問題はfonts-takaoをインストールすれば回避できますが、
この問題の場合、Takaoフォントのアセンダ/ディセンダがUbuntuフォントよりも小さいせいか、
fonts-takaoをインストールしても解決しませんね。"
1820133,2020-02-23 07:16:13 UTC,これもなんとかしたいところ。
1820136,2019-03-14 23:41:13 UTC,Are you seeing errors on the MAAS side?
1820136,2019-03-15 14:22:24 UTC,"We are seeing these critical MAAS errors in `regiond.log`, and that's what led me to postgresql.log to find more hints.  Not sure if it's related."
1820136,2019-05-15 04:17:32 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1820140,2019-03-14 23:37:57 UTC,That has been fixed in disco with https://launchpad.net/ubuntu/+source/grilo-plugins/0.3.8-2ubuntu2
1820140,2019-03-19 21:30:56 UTC,"Hello Sebastien, or anyone else affected,"
1820140,2019-05-27 11:33:52 UTC,Using 0.3.8-2ubuntu1.1 euronews vides can be played correctly
1820140,2019-05-28 17:06:20 UTC,This bug was fixed in the package grilo-plugins - 0.3.8-2ubuntu1.1
1820140,2019-05-28 17:06:25 UTC,"The verification of the Stable Release Update for grilo-plugins has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820144,2019-04-12 11:14:02 UTC,Thank you for driving these SRUs! A couple of minor comments that I didn't think it was worth blocking on:
1820144,2019-05-28 17:41:14 UTC,"Hello WGH, or anyone else affected,"
1820144,2019-05-04 04:40:56 UTC,"Hello WGH, or anyone else affected,"
1820144,2019-06-03 18:32:51 UTC,"I've just tested the -proposed package on cosmic and bionic, works fine now."
1820144,2019-04-01 09:31:41 UTC,"> Can you please read through https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template and apply the template for SRU to your bug description, please? This is necessary before this can even be handled like an SRU.
"
1820144,2019-06-05 01:10:46 UTC,"The verification of the Stable Release Update for iptables-persistent has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820144,2019-06-05 01:11:00 UTC,This bug was fixed in the package iptables-persistent - 1.0.7ubuntu1
1820144,2019-04-12 11:10:40 UTC,Uploaded Bionic and Cosmic debdiffs.
1820144,2019-06-05 01:10:38 UTC,This bug was fixed in the package iptables-persistent - 1.0.4+nmu2ubuntu1
1820144,2019-04-12 11:05:43 UTC,"I verified that the || true pattern is used in the modprobe call in the two files being patched here in 1.0.11 (via sources.debian.net), so this looks good to me."
1820144,2019-03-19 22:52:30 UTC,"Confirmed, same issue affects Cosmic and is not fixed."
1820144,2019-04-01 11:40:03 UTC,"WGH: no, because I applied it.  Still have to wait for sponsors then the SRU team though.  The process is not super quick unfortunately."
1820144,2019-03-26 12:37:15 UTC,"Hello to all affected.  I have provided debdiffs attached here, and subscribed the Sponsors team as I do not have direct upload for these packages.  Once reviewed we can continue with the SRU process."
1820144,2019-03-22 14:20:06 UTC,Hello.
1820144,2019-03-19 22:51:06 UTC,"Checked this further in the code, this is what they're doing in latest upstream in Disco.  Marking as ""Fix Released"" for Disco as this is already solved there, going to check the Cosmic version next."
1820144,2019-03-16 11:09:10 UTC,"> This only works if the iptables modules aren't loaded in the 'host' system, correct?
"
1820144,2019-03-15 17:42:18 UTC,"This only works if the iptables modules aren't loaded in the 'host' system, correct?"
1820144,2019-03-15 08:28:01 UTC,Quick reproduction in LXD:
1820148,2019-06-11 04:17:29 UTC,[Expired for juju because there has been no activity for 60 days.]
1820148,2019-03-15 03:39:22 UTC,I don't understand why a local name for a cloud is a problem?
1820148,2019-03-15 03:00:39 UTC,See also #1641970 and #1641981
1820151,2019-03-15 04:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820151,2019-04-02 11:19:47 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1106.114
1820152,2019-04-02 11:20:12 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1110.115
1820154,2019-08-27 09:01:44 UTC,"Could you check please if you have this patch in your environment:
https://review.opendev.org/665995
By your description I have seen similar issues with the agent, and this fixed for me."
1820154,2019-09-13 08:28:42 UTC,"Reviewed:  https://review.opendev.org/680366
Committed: https://git.openstack.org/cgit/openstack/networking-l2gw/commit/?id=30326d75aa68657c433d6eb9f9696cff7ca5d0c1
Submitter: Zuul
Branch:    stable/stein"
1820154,2019-09-05 10:25:52 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/680366"
1820154,2019-09-04 08:07:34 UTC,"Good morning,"
1820154,2019-09-03 15:12:13 UTC,"Reviewed:  https://review.opendev.org/666019
Committed: https://git.openstack.org/cgit/openstack/networking-l2gw/commit/?id=852c8098ca50a2879776cb5437db1271c9a9d8e5
Submitter: Zuul
Branch:    master"
1820154,2019-08-27 09:18:08 UTC,Thank you very much. I'll check as soon as possible and will report back.
1820154,2019-08-26 13:31:56 UTC,"Hi, I checked with latest master (neutron is master and https://review.opendev.org/666019 for networking-l2gw).
I see the warning you referenced for stevedore not able to load L2gwRpcDriver, but a few lines later the driver is loaded:"
1820154,2019-08-10 14:00:24 UTC,The patch seems to have corrected the TypeError:
1820154,2019-08-22 06:53:37 UTC,"Thanks Kees for checking out, just arrived back from vacation, will check your comments."
1820154,2019-08-11 10:03:00 UTC,The RPC part still doesn't work in Neutron itself:
1820154,2019-08-10 12:11:24 UTC,Just downloaded the patch from Gerrit. Will try if it solves the problem in my case and will report back.
1820154,2019-06-18 15:14:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666019"
1820154,2019-08-26 14:02:34 UTC,"Ah, didn't spot that."
1820157,2019-04-02 10:42:45 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1043.49
1820158,2019-04-02 10:46:14 UTC,This bug was fixed in the package linux-aws - 4.4.0-1040.43
1820164,2019-03-21 12:23:13 UTC,Looks like a duplicate of https://bugs.launchpad.net/devstack/+bug/1820070
1820171,2019-03-16 08:46:12 UTC,"Lubuntu 18.10
4.18.0-16-generic"
1820171,2019-04-14 08:10:32 UTC,Or maybe I'm barking up the wrong tree and this has nothing to do with power management/screen savers but has something specific to do with Chromium or YouTube?
1820171,2019-04-14 08:09:05 UTC,I'm really struggling to understand the steps you took to create the problem or even what the problem is.
1820171,2019-03-15 21:53:51 UTC,"Please be specific in release and please avoid guessing, or terms that could be misinterpreted (like 'should be 18.10 or so')."
1820171,2021-01-09 13:27:34 UTC,"How to reproduce this bug is to install any supported version of Lubuntu, connect to the internet, turn on a youtube video, in firefox (chromium and chrome from other bug reports should work as well) and then wait for 15 minutes."
1820171,2019-03-15 17:29:19 UTC,"Latest Ubuntu.
Yes, happens every time. Is a power configuration, (screen off after xxx minutes), not screensaver.
Just set your screen to turn off after a certain time, and spend that time watching a YouTube video in chromium browser."
1820171,2019-03-15 11:14:39 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1820171,2019-06-14 04:17:22 UTC,[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1820171,2019-03-15 17:30:49 UTC,"Latest stable Lubuntu should be 18.10 or so.
Latest stable Linux kernel.
I didn't use any exotic screen drivers (my laptop has an Intel IGP)."
1820173,2019-07-27 19:17:50 UTC,"I have a similar netbook called Dell Inspiron 11 3162 in which this is reproducible. Changing brightness with the FN (function) key combinations change the gamma of the screen instead of the actual brightness. It's a fake brightness change, like the one Redshift can do if you're familiar with it."
1820173,2019-06-16 04:17:19 UTC,[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1820173,2019-04-16 04:19:53 UTC,One more: do you have the same results with 18.04 or 19.04?
1820173,2019-11-09 20:45:22 UTC,"I use the Acer Aspire 3 netbook. Lubuntu's brightness adjustment works nicely, although it differs from Xubuntu. With Lubuntu, the screen has a slightly eerie glow to it. Also, tilt the screen away from one, and it goes dark. Tilt it towards one, and it goes bright. Xubuntu, on the other hand, is consistently bright. Lubuntu, however, has a fortuitous benefit. In the dark it has the effect of lighting the keyboard. That is not the case with Xubuntu."
1820173,2019-07-28 13:46:25 UTC,Indeed! It's more like a 'screen dimmer' than a true screen backlight changer.
1820173,2019-04-15 23:53:56 UTC,"Gain meaning, the screen brightness is not affecting screen brightness but affecting the wrong setting.
Gain means it will brighten some parts of the screen (make the mids brighter, but keep the darks dark)."
1820173,2019-04-16 00:50:34 UTC,"I'd like to request some more info:
 1. Could you record what this looks like?
 2. The exact specs of your computer might help, too.
 3. I'd urge you to use `xev` to figure out what keycode is being used.
 4. Is there anything in the logs suggesting what is being done?
/var/log/syslog would be the most obvious place.
 5. What does your Openbox config look like?
 6. What about the lxqt-globalkeys config?"
1820173,2019-03-16 09:13:36 UTC,Lubuntu 18.10 Kernel 4.18.0-16-generic
1820173,2019-03-15 21:40:00 UTC,Latest Ubuntu??
1820173,2019-03-15 17:25:22 UTC,"Latest Ubuntu. Screen brightness keys are mapped to DN + F2 and f3 in my case.
I have no idea why lxfind was selected, but I can assure you that I did not do that.
Is there a way to move this bug to general Lubuntu bug report?"
1820173,2019-03-15 11:26:28 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1820173,2019-04-14 06:55:10 UTC,"Two questions:
 1. What do you mean by ""screen gain?"" I know this as a static property projection screens have, so I'm not sure how it's relevant.
 2. If you open terminal and run `xev -event keyboard` and press the key in the resulting window, what is the result?"
1820175,2019-03-25 18:46:11 UTC,"Are those pins connected to anything?  If not, then they should show the pin as unconnected even if they are not visible."
1820175,2019-03-25 19:13:15 UTC,"Yes. Those pins are hidden power pins ""connected"" to the VCC and GND power ports respectively. Of course there are not regular wires."
1820175,2019-05-25 04:17:34 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1820179,2019-04-30 13:15:21 UTC,"I reviewed coreapi 2.3.3-2 from eoan. This isn't a full security audit,
but rather a quick gauge of maintainability."
1820179,2019-07-03 05:41:22 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820179,2019-03-20 14:13:44 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820180,2019-03-20 14:13:30 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820180,2019-07-03 05:41:18 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820181,2019-03-20 12:27:04 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820181,2019-07-03 05:34:48 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820182,2019-07-03 05:41:14 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820182,2019-03-20 12:26:52 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820183,2019-07-03 05:34:44 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820183,2019-03-20 12:26:32 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820184,2019-09-19 11:54:18 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1820185,2019-07-03 05:41:11 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820185,2019-03-20 12:26:19 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820186,2019-03-20 12:24:55 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820186,2019-03-20 13:13:57 UTC,"FTR - minor fixup, no python2 bits produced by this package"
1820186,2019-07-03 05:34:39 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820188,2019-03-20 12:23:31 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820188,2019-07-03 05:41:06 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820189,2019-07-03 05:41:02 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820189,2019-03-20 12:23:15 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820189,2019-03-20 13:14:02 UTC,"FTR - minor fixup, no python2 bits produced by this package"
1820190,2019-03-20 12:22:55 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820190,2019-07-03 05:34:35 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820191,2019-03-19 11:32:38 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820191,2019-07-03 05:34:31 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820192,2019-03-19 11:32:15 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820192,2019-07-03 05:40:58 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820193,2019-03-19 11:31:54 UTC,"[Duplication]
This provides NFS save locks with timeout functionality.
Some projects implmented their own fctnlf bits while others use python-lockfile.
But there are more 8for example here [1]) than just these.
python-lockfile is deprecated in favor of fastener or oslo-concurrency [2].
The latter would even be in main but actually is about locking functions.
Finally none of those provide timeouts on the locks as mailman needs it from
flufl."
1820193,2019-07-03 05:40:55 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820194,2019-09-19 14:59:22 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1820195,2019-03-21 11:27:38 UTC,"MIR acceptance (and review) is done on source level.
And approving (another?) ""OAuth2 authentication server"" in MAIN just for some fonts feels wrong."
1820195,2019-07-03 05:52:05 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820195,2019-04-09 13:14:49 UTC,"Sounds like what you want is b). If all we need is the font, then also why is a font bundled with an OAUTH server?"
1820195,2019-04-09 13:16:41 UTC,Thanks Mathieu for the confirmation - Assigned to Server Team to resolve the packaging change in Debian
1820196,2019-07-03 05:34:26 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820196,2019-03-20 15:31:39 UTC,"[Duplication]
This is part of the six core packages of mailman3 that pull in further components as needed.
Since this represents mailman doing mailing list processing there is a duplication to mailman2.
But the intention is to stop seeding mailman2 as soon as mailman3 got promoted."
1820197,2019-03-21 12:45:29 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820197,2019-07-03 05:40:51 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820199,2019-03-19 11:31:33 UTC,"[Duplication]
No duplication for this functionality in main at the moment.
While there are many config handlers, this is a particular config format
that isn't in any other package that I'd have found."
1820199,2019-07-03 05:40:47 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820200,2019-03-19 11:30:37 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820200,2019-07-03 05:40:41 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820201,2019-03-15 10:03:33 UTC,Not yet subscribing the MIR team until we have clarified if we could drop the dependency to the nodejs bits completely (https://<email address hidden>/thread/HFNP4DPZ3CLXV3OOEJVHCVOLZ7OMAI7G/).
1820201,2019-07-03 05:53:47 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820202,2019-03-21 12:47:13 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820202,2019-07-03 05:34:22 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820203,2019-07-03 05:34:18 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820203,2019-03-21 12:47:47 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820204,2019-03-20 15:30:12 UTC,"[Duplication]
This is part of the six core packages of mailman3 that pull in further components as needed.
Since this represents mailman doing mailing list processing there is a duplication to mailman2.
But the intention is to stop seeding mailman2 as soon as mailman3 got promoted."
1820204,2019-07-03 05:34:13 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820205,2019-03-20 15:29:27 UTC,"[Duplication]
This is part of the six core packages of mailman3 that pull in further components as needed.
Since this represents mailman doing mailing list processing there is a duplication to mailman2.
But the intention is to stop seeding mailman2 as soon as mailman3 got promoted."
1820205,2019-07-03 05:34:09 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820206,2019-03-20 15:28:36 UTC,"[Duplication]
This is part of the six core packages of mailman3 that pull in further components as needed.
Since this represents mailman doing mailing list processing there is a duplication to mailman2.
But the intention is to stop seeding mailman2 as soon as mailman3 got promoted."
1820206,2019-04-28 22:36:03 UTC,"I reviewed mailman-suite 0+20180916-7 as checked in to eoan. This isn't a full security audit, but rather a quick gauge of maintainability."
1820206,2019-05-03 05:08:31 UTC,"I answered on IRC that the dependency to ruby-sass is planned to be dropped.
Therefore mailman-suite itself is complete as well, thanks for the review."
1820206,2019-07-03 05:40:36 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820207,2019-03-15 10:03:56 UTC,Not yet subscribing the MIR team until we have clarified if we could drop the dependency to the nodejs bits completely (https://<email address hidden>/thread/HFNP4DPZ3CLXV3OOEJVHCVOLZ7OMAI7G/).
1820207,2019-07-03 05:53:54 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820208,2019-07-03 05:54:01 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820208,2019-03-18 06:06:46 UTC,"Thanks Kapouer,
yeah the test/fixtures/throws_error5.js files are not really javascript - good hint."
1820208,2019-03-15 10:49:10 UTC,"There are several things about nodejs package that are not really right,
let me fix this below."
1820208,2019-03-15 10:03:46 UTC,Not yet subscribing the MIR team until we have clarified if we could drop the dependency to the nodejs bits completely (https://<email address hidden>/thread/HFNP4DPZ3CLXV3OOEJVHCVOLZ7OMAI7G/).
1820209,2019-03-21 12:48:35 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820209,2019-07-03 05:34:04 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820210,2019-03-20 15:27:53 UTC,"[Duplication]
This is part of the six core packages of mailman3 that pull in further components as needed.
Since this represents mailman doing mailing list processing there is a duplication to mailman2.
But the intention is to stop seeding mailman2 as soon as mailman3 got promoted."
1820210,2019-07-03 05:34:01 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820211,2019-05-06 12:06:11 UTC,Thanks for the hint on the upstream discontinuation Eduardo.
1820211,2019-04-25 18:13:44 UTC,"I reviewed python3-openid version 3.1.0-1 as checked into disco as of this
writing.
This shouldn't be considered a full audit but rather a quick gauge of
maintainability."
1820211,2019-07-03 05:33:57 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820211,2019-03-22 08:23:05 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820212,2019-03-22 08:22:44 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820212,2019-05-11 03:08:06 UTC,Eduardo is taking a look at this package for the security team and pointed out that it is doing a setuid to user 'nobody'.
1820212,2019-05-13 06:33:33 UTC,"On Sat, May 11, 2019 at 5:15 AM Seth Arnold <email address hidden> wrote:

>
> Eduardo is taking a look at this package for the security team and
> pointed out that it is doing a setuid to user 'nobody'.
>
> This isn't a safe design. User nobody is strictly for NFS's use and must
> not be used by any running processes on the system.
"
1820212,2019-05-13 18:56:28 UTC,"I reviewed python-aiosmtpd version 1.2-3 as checked into eoan as of this
writing."
1820212,2019-07-03 05:33:53 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820213,2020-03-10 14:12:14 UTC,"Openstack will take this one over as dependency for masakari packages.
@Jamespage pelase subscribe the openstack Team"
1820213,2019-03-21 14:27:02 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820213,2019-07-03 05:40:29 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820214,2019-07-03 05:40:26 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820214,2019-03-21 14:26:48 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820215,2019-07-03 05:33:49 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820215,2019-03-22 08:21:14 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820216,2019-04-23 21:30:44 UTC,"I reviewed python-django-gravatar2 version 1.4.2-3 as checked into
disco. This should not be considered a full security audit, but rather a
quick gauge of maintainability."
1820216,2019-07-03 05:33:46 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820216,2019-03-22 08:16:31 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820217,2019-07-03 05:33:41 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820217,2019-03-22 08:16:09 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular.
TBH there are other python REST frameworks, but none that seems integratable for mailman3 the way falcon is."
1820220,2019-07-03 05:40:23 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820220,2019-03-21 14:26:34 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820221,2019-07-03 05:33:35 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820221,2019-03-22 08:15:48 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820221,2019-05-01 19:17:43 UTC,I reviewed python-requests-oauthlib (1.0.0) from eoan.
1820222,2019-03-15 12:25:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1820222,2019-07-10 15:31:06 UTC,"This is presumably because you are on a system using UEFI with SecureBoot, and therefore the loading of external grub modules fails ('insmod udf'), and we do not build udf support into the signed UEFI GRUB image."
1820222,2019-07-22 18:26:11 UTC,"It is an UEFI system, but NOT SecureBoot enabled."
1820223,2019-03-21 14:26:15 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820223,2019-07-03 05:40:19 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820224,2019-03-22 08:15:22 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820224,2019-07-03 05:33:30 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820225,2019-07-03 05:40:16 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820225,2019-05-14 05:32:47 UTC,"Yeah that seems lake a good safety net, you might submit that to upstream hyperkitty I'd think."
1820225,2019-05-13 17:03:08 UTC,"""Based on a cursory audit of django, I could not find any condition where the user agent would be
returned as anything other than a string."""
1820225,2019-04-22 14:16:13 UTC,"I reviewed robot-detection version 0.4.0-1 as checked into disco. This
should not be considered a full security audit, but rather a quick gauge
of maintainability."
1820225,2019-04-23 20:56:21 UTC,"I confirmed with a django developer that django does, indeed, catch exceptions in the views.
https://github.com/django/django/blob/master/django/core/handlers/exception.py#L18"
1820225,2019-03-20 14:12:54 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820225,2019-05-13 16:32:43 UTC,"Regarding the point made about the lack of documentation, would it make sense to document the is_robot() routine itself?  Maybe something along the lines of the attached?"
1820226,2019-06-03 05:54:47 UTC,"> - There are different versions of twitter-bootstrap in the archive, after some
>   search we have that
[...]
>     It is used in mailman-website where you can manage lists. It is unclear to
>     me if the version 3 is a hard dependency.
"
1820226,2019-07-03 05:54:40 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820226,2019-06-03 14:03:20 UTC,"On Mon, 2019-06-03 at 05:54 +0000, Christian Ehrhardt  wrote:

> > - There are different versions of twitter-bootstrap in the archive,
> > after some
> >   search we have that
>
> [...]
> >     It is used in mailman-website where you can manage lists. It is
> > unclear to
> >     me if the version 3 is a hard dependency.
>
> Yes it is, I have checked with upstream already for the same reason
> (expect to be longer maintained) but the move seems to be non
> trivial.
> So for now it is a hard dependency on v3
>
"
1820226,2019-05-31 19:36:13 UTC,"I reviewed twitter-bootstrap3 3.4.0+dfsg-4 as checked into eoan. This shouldn't
be considered a full audit but rather a quick gauge of maintainability."
1820226,2019-04-09 13:26:42 UTC,Assigned to cyphermox in todays MIR Team meeting - thanks a lot for taking a look at this!
1820226,2019-04-10 18:47:20 UTC,"Couldn't this simply work with libjs-bootstrap4? Seems like using bootstrap4 would be a net improvement anyway, especially sicne it then wouldn't be encumbered by the open CVEs."
1820226,2019-03-21 11:05:24 UTC,"FYI: the package is also:
a) more complex
b) more likely to be a Deny or at least extra work to be triggered
Therefore I'm on next weeks meeting passing the review of this one to a fellow MIR team member"
1820226,2019-04-11 09:42:57 UTC,Thanks Mathieu for your review!
1820227,2019-03-21 11:05:11 UTC,"FYI: The FTBFS fix is in progress and soon resolved.
FYI: but the package is also:
a) more complex
b) more likely to be a Deny or at least extra work to be triggered
Therefore I'm on next weeks meeting passing the review of this one to a fellow MIR team member"
1820227,2019-04-09 13:26:46 UTC,Assigned to cyphermox in todays MIR Team meeting - thanks a lot for taking a look at this!
1820227,2019-04-18 18:07:30 UTC,"This is package is huge and terrible to review; I had a look at it, and I see a couple of places where it seems like it's security sensitive. To top that off, it's a CGI server, so obviously security sensitive in its own right. Let's have Security review it."
1820227,2019-06-26 02:51:50 UTC,I've been reading the uwsgi documentation and code for a few hours now; I fully concur with Mathieu's assessment.
1820227,2019-06-26 09:34:34 UTC,"Yeah, I agree that uwsgi is a beast."
1820227,2019-07-03 03:09:02 UTC,Here's the notes I took while reviewing this package:
1820227,2019-07-03 05:32:52 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820229,2019-12-11 07:31:34 UTC,"Thanks Corey - Ok, then this one would be ready to be promoted as needed"
1820229,2019-12-16 08:52:40 UTC,promoted
1820229,2019-11-27 07:27:14 UTC,"Hi Openstack team,
this (cmd2) is part of the Openstack context and now triggering this component mismatch.
Fortunately due to our past work for mailman3 this MIR would be all ready for you except one thing - the bug subscriber."
1820229,2019-12-10 20:07:42 UTC,"@Christian, I just ran across this for cmd2 and have subscribed OpenStack Ubuntu packagers to the bug reports. Thanks."
1820229,2019-11-27 07:08:45 UTC,this specific package now shows up as a dependency of cmd2.
1820229,2019-07-03 05:40:12 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820229,2019-03-20 14:13:13 UTC,"[Duplication]
No duplication of that functionality in the Archive in general or main in particular."
1820231,2020-01-27 13:43:18 UTC,The issue supposed to be solved by the underlying filesystem.
1820231,2020-01-27 09:02:03 UTC,Do you have any specific idea how to fix that?
1820233,2019-03-19 10:18:07 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820233,2019-06-19 21:54:03 UTC,"I reviewed zope.component 4.3.0-1 as checked into eoan. This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1820233,2019-07-02 13:08:13 UTC,"The right state for ack is ""in progress"" per [1], setting that."
1820233,2019-07-03 05:54:42 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820234,2019-03-19 10:17:47 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820234,2019-07-03 05:33:26 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820235,2019-03-29 07:24:34 UTC,"There is a check in PEXSI routine whether the auxiliary supercell is in use. So it should get caught, we are a little surprised in this case since I can't reproduce it."
1820236,2019-03-19 10:17:26 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820236,2019-07-03 05:33:19 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820237,2019-03-19 10:17:04 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820237,2019-07-03 05:33:11 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820238,2019-07-03 05:33:08 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820238,2019-07-02 18:00:10 UTC,"Only 2 issues opened in github project, not security relevant. https://github.com/zopefoundation/zope.schema/issues"
1820238,2019-07-02 17:59:05 UTC,"I reviewed zope.schema 4.4.2-3 as checked into eoan.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1820238,2019-03-19 10:12:09 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820239,2019-03-19 10:15:24 UTC,"[Duplication]
No duplication for this functionality in main at the moment."
1820239,2019-06-26 16:35:49 UTC,"I reviewed zope.i18nmessageid 4.0.3-2build6 as checked into eoan.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1820239,2019-07-03 05:33:03 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820240,2019-03-15 12:25:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1820241,2019-03-15 10:12:51 UTC,This affects the Rocky branch and is fixed by this commit on master:
1820241,2019-03-15 10:18:46 UTC,The commit on master which fixes the issue adds additional functionality over the minimal fix for this issue:
1820241,2019-03-15 10:54:23 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/643559"
1820241,2019-03-20 11:07:25 UTC,"Reviewed:  https://review.openstack.org/643559
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=47883649e03973d56d24d3e97c158494a7edf541
Submitter: Zuul
Branch:    stable/rocky"
1820241,2019-04-12 23:29:32 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.0 release.
1820242,2019-09-20 13:20:27 UTC,I cannot reproduce in multipass anymore: https://pastebin.ubuntu.com/p/7KmZcT3xt7/
1820242,2019-09-26 06:46:42 UTC,"This is fixed now, snapfuse is part of the snapd snap."
1820243,2019-04-01 06:56:27 UTC,Does this happen to previous v4.18 kernels?
1820243,2019-04-01 17:55:27 UTC,"I am using 4.18 since -v15 because it crashed often before -v15.
If I remembered correctly it was ""https://bugs.launchpad.net/bugs/1818974"" but happened more often."
1820243,2019-04-07 22:38:31 UTC,"Today I did put my laptop in standby.
Disconnected it from my dock.
Woke it up.
It worked.
I did put my laptop in standby again.
Connected it with my dock.
Woke it up.
Black screen.
Was forced to restart it by a hard reset."
1820243,2019-04-08 00:51:14 UTC,"Hi, could you try suspend again with dock connected and paste dmesg of the last boot. A nvidia xid error 69 was found in your attachments, but I'm not sure if it's related because it contains log of multiple boot/suspend."
1820243,2019-04-08 09:41:39 UTC,"My display manager is lightDM.
How can I set it to debug?
And with ""syslog"" you mean you mean journalctl ?"
1820243,2019-04-08 09:45:30 UTC,"Sorry to write another message, but I can't edit the previous one."
1820243,2019-06-28 20:01:43 UTC,"I see I did report it for kernel 4.15 in the past too.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781904
It worked in the release candidate of the 4.18 kernel."
1820243,2019-06-28 20:05:43 UTC,"Disconnected my laptop from the docking station by accident (human like kernel panic).
Wanted to dock again.
Still happening.
Kernel 4.18.0-24-generic"
1820243,2019-06-28 20:08:24 UTC,"Seeing my old friend I saw in 4.15
[drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF D idle bit"
1820243,2019-03-15 10:16:58 UTC,apport information
1820243,2019-04-08 09:44:01 UTC,I used
1820243,2019-03-15 10:16:57 UTC,apport information
1820243,2019-03-15 10:16:56 UTC,apport information
1820243,2019-03-15 10:16:55 UTC,apport information
1820243,2019-03-15 10:16:54 UTC,apport information
1820243,2019-03-15 10:16:53 UTC,apport information
1820243,2019-03-15 10:16:52 UTC,apport information
1820243,2019-03-15 10:16:51 UTC,apport information
1820243,2019-03-15 10:16:50 UTC,apport information
1820243,2019-03-15 10:16:49 UTC,apport information
1820243,2019-03-15 10:16:48 UTC,apport information
1820243,2019-03-15 10:16:47 UTC,apport information
1820243,2019-03-15 10:16:45 UTC,apport information
1820243,2019-03-15 10:16:44 UTC,apport information
1820245,2019-05-20 04:17:32 UTC,[Expired for netplan because there has been no activity for 60 days.]
1820245,2019-03-20 18:21:18 UTC,here config of keepalive
1820245,2019-05-20 04:17:32 UTC,[Expired for netplan.io (Ubuntu) because there has been no activity for 60 days.]
1820245,2019-03-20 13:57:59 UTC,"Can you provide configs, please? Cause I've it working."
1820245,2019-03-20 16:36:37 UTC,Evgeniy Yablokov:
1820247,2019-03-18 07:10:09 UTC,"Hi Premysl,
this has similarities to [1] which was fixed long ago.
In case it is reproducible for you - as it was asked back then - it might be helpful attaching SPICE_DEBUG=1 log, using remote-viewer."
1820247,2019-03-18 14:07:40 UTC,"Hi Christian,"
1820247,2019-03-18 14:21:07 UTC,"Hi,
the warnings around ""duplicate channel type 2 id 0"" where present in the other bug as well.
And since that often means it passes the same area of code I wanted to suggest to provide the same debug data."
1820247,2020-11-25 18:30:09 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1820248,2019-03-17 03:39:52 UTC,"Fixed in revision 0de25e557b45a9bccf3a0dbd59b208334f4b8b3f
https://git.launchpad.net/kicad/patch/?id=0de25e557b45a9bccf3a0dbd59b208334f4b8b3f"
1820248,2019-09-06 13:10:47 UTC,"@Seth acknowledged, in nightly 14089 (from aug.24) it seems working fine,"
1820248,2019-08-21 19:20:15 UTC,I forgot when this was addressed but it is fixed currently in the nightly builds.
1820248,2019-08-21 08:41:32 UTC,"@Chupacabras  Wouldn't say impossible: if you check previous comments, you can use holding down Shift/Alt buttons or set  Preferences - Pcbnew - Magnetic points - Snap to Tracks  to None.  It is cumbersome."
1820248,2019-08-21 08:13:31 UTC,"I have this issue too.
It seems that when moving a track it snaps to itself. Which is wrong. So it is impossible to move track a little bit."
1820248,2019-03-24 22:17:05 UTC,"Apparently, I only got the disconnected end case.  OK, back into the queue."
1820248,2019-03-22 18:30:33 UTC,"@Seth, I checked 12544 of March 22th, but I don't see any change. See video again. I
- move he cursor above the track,
- push D to drag
- slowly move mouse, but track is *not moving* at first
- track is suddenly jumping to a farther position, then gently following the mouse cursor
- when I move back toward the original position of the track, it is jumping back to its original posistion from a distance."
1820248,2019-03-17 10:26:57 UTC,"@Seth,  ok, I will check next nightly.
One more thought: you should differentiate between a new track segment where its free end to be connected to some snapping point,
and a segment having been connected and dragging.
It's everything is fine at the ""laying new track"" case.
At the ""dragging an already-placed segment"" case the only object(s) to be snapped to is
- parallel segments of the same net
- grid
but definitely not the old position."
1820248,2019-03-17 03:38:55 UTC,"Right.  @Novak, can you see if tomorrow's nightly works correctly for your use case?"
1820248,2019-08-21 08:59:56 UTC,"Yes I read all previous comments, I know about those key modifiers."
1820248,2019-03-16 21:30:56 UTC,"If you want to eliminate jags in the track, you want to snap.  This is almost always my use case when I am dragging tracks with 'd'"
1820248,2019-03-16 21:19:43 UTC,"When I do a 'G' on the end of a track I want it to snap -- so I don't want to set the preference to ""When creating tracks""."
1820248,2019-03-16 20:22:49 UTC,"The Preferences - Pcbnew - Magnetic points - Snap to Tracks is set to ""When creating tracks"". I don't know if this should be valid for dragging tracks already connected...If I set this to ""never"", no snapping occurs, you are right.  It is a better workaround than holding down Shift: I can set Snap to Tracks to Never for final track alignment phase."
1820248,2019-03-16 17:33:40 UTC,We could remove the original trace from the SetEndItem calculation and instead rely on the auxiliary axis for snapping to the original position.  That would allow grid override when the mouse is closer to a grid line than the origin lines.
1820248,2019-03-16 16:53:56 UTC,This isn't really snapping to tracks but rather snapping to itself.  The former is useful for connecting things; this is not (although it may be useful for other things).
1820248,2019-03-16 14:10:50 UTC,"Well, it is already an option.  If you don't like snapping to tracks, then you can turn it off in the preferences.  I'm fine with making the snap radius configurable as well."
1820248,2019-03-16 13:22:41 UTC,"This has been coming up a lot.  Even if we think it's valuable, perhaps snapping to 1/2 the track width or something would be better?"
1820248,2019-03-16 23:20:19 UTC,"Hmmm... yes, good point."
1820248,2019-03-16 13:11:58 UTC,"Sorry, Seth, I know there is a workaround, but IMO it *is* a bug. Previous versions (my oldest is nightly 8659 from October 2017) don't do this.
Using the workaround is a bit uncomfortable: press D to drag, then hold down Shift, move and click mouse, then release Shift.
The actual grid is 0.01mm, still track jumps to abt 0.3mm far, so it is not a normal snap-to-grid.
Please consider setting it to low importance confirmed if you can reproduce the issue."
1820248,2019-03-15 15:34:06 UTC,"Hold down Shift while dragging to disable snapping.
Hold down Alt while dragging to disable the grid."
1820259,2019-06-05 20:33:09 UTC,This bug was fixed in the package update-notifier - 3.192.1.7
1820259,2019-06-05 15:26:22 UTC,I've installed the latest version of update notifier.
1820259,2019-06-05 14:57:49 UTC,"3.192.1.7 works fine here, the indicator shows with the current status and is now not displayed when the service is not in use (not changing the tag yet so Will/Iain have a chance to also give it a try before we release it)"
1820259,2019-05-24 11:16:01 UTC,"Hello Andrea, or anyone else affected,"
1820259,2019-05-08 09:31:04 UTC,"> Also, I think that the design is to not show the icon if the livepatch client is not installed, but I will need to confirm that.
"
1820259,2019-05-07 20:08:32 UTC,"It seems we are missing the ""Show livepatch in the topbar"" options in s-p-gtk as per:
https://wiki.ubuntu.com/SoftwareUpdates#livepatch"
1820259,2019-06-05 20:33:58 UTC,"The verification of the Stable Release Update for update-notifier has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820259,2019-05-07 20:02:13 UTC,Why the verification-failed? It works here...
1820259,2019-04-25 16:58:56 UTC,"Hello Andrea, or anyone else affected,"
1820259,2019-04-25 16:57:47 UTC,"I will accept this, but could you make sure that the documentation for bionic won't have to be modified anywhere? Can you send an e-mail to the ubuntu-doc team as a heads up? Thanks!"
1820259,2019-04-11 12:11:55 UTC,It was fixed with https://bugs.launchpad.net/ubuntu/+source/update-notifier/3.192.15 (but the bug closing syntax was wrong so launchpad didn't automatically pick it up)
1820259,2019-03-19 10:25:22 UTC,"Ok, in this case where the indicator will not appear at all on systems where Livepatch is not supported, this should be good to go. Approved."
1820259,2019-05-07 20:05:19 UTC,I installed this and found a problem that should block releasing this:
1820261,2019-05-26 19:34:26 UTC,"Hi Charles,"
1820261,2019-05-26 16:02:57 UTC,"Jorge, I've ""assigned"" you the bug so that you will get credit for the work."
1820261,2019-05-26 15:58:18 UTC,I uploaded these translations to LaunchPad. Maybe it will be easier to work on them through that interface?
1820261,2019-05-26 13:53:46 UTC,Latest update
1820261,2019-04-28 15:21:54 UTC,"Okay. We can work on the mechanics of using the translation another time. For now, are you able to verify that the translation is correct? If correct, we can include the update in the next release of pcb."
1820261,2019-04-19 19:48:56 UTC,"Need make install for `LC_MESSAGES=""pt_BR.utf8"" pcb`.
`LC_MESSAGES=""pt_BR.utf8"" ./pcb` do not work."
1820261,2019-04-19 19:34:55 UTC,"I do not ""make install"""
1820261,2019-04-19 14:04:50 UTC,Sorry.
1820261,2019-04-19 09:33:01 UTC,git clone using the command:
1820261,2019-04-17 16:07:02 UTC,Yes I do.
1820261,2019-04-16 15:50:18 UTC,Jorge-
1820261,2019-03-26 13:36:42 UTC,"1. Can you please verify that the translation files were installed? You should search for files named ""pcb.mo"" in /usr/share/locale/pt_BR or /usr/local/share/locale/pt_BR"
1820261,2019-03-25 21:56:23 UTC,Hi.
1820261,2019-04-19 17:22:38 UTC,"LC_MESSAGES=""pt_BR.utf8"" pcb work fine."
1820271,2019-03-15 12:55:03 UTC,"In other words, I deployed a Ceph cluster from the Ocata UCA (i.e. Jewel) with charm defaults left alone so bluestore=enabled. The deployment worked fine and I ended up with 3 Filestore OSDs as expected. I then did add-disk for 3 more OSD disks and it failed with ^^."
1820271,2019-03-15 14:26:24 UTC,I'm not sure why gerrit isn't updating this but I'm working on this bug in this topic: https://review.openstack.org/#/q/status:open+topic:bug/1820271
1820271,2019-03-18 10:00:12 UTC,"Reviewed:  https://review.openstack.org/643575
Committed: https://git.openstack.org/cgit/openstack/charms.ceph/commit/?id=98183011bba073d6665780083ca54413d82d8dcf
Submitter: Zuul
Branch:    master"
1820271,2019-11-08 15:27:44 UTC,This bug is almost certainly fixed as the relevant charms.ceph code is merged (and more up-to-date) into the ceph-osd  charm.
1820278,2019-05-31 03:45:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820278,2019-05-31 03:49:02 UTC,"I stopped systemd-resolved, disabled it, restarted docker, no change."
1820278,2019-05-31 03:47:24 UTC,I ran into this on upgrade today.
1820278,2019-03-18 14:18:39 UTC,Anything useful in Docker's daemon logs?
1820278,2019-03-18 22:23:23 UTC,"I assume there is ""systemd-resolved is running, so using resolvconf: /run/systemd/resolve/resolv.conf"" in the deamon logs, or I don't understand what is going on at all."
1820278,2019-03-18 12:57:39 UTC,Have you tried restarting the Docker daemon? (IIRC it caches the DNS settings during startup)
1820278,2019-03-18 12:10:01 UTC,"I'm connecting to the VPN through Palo Alto Networks's globalprotect (https://www.paloaltonetworks.com/products/globalprotect/overview). I just run ""globalprotect connect --portal some.company.address.com -u my_vpn_user"" (so I assume most of the network config was bundled in the installer I got)"
1820278,2019-03-17 23:48:10 UTC,This looks likely to be the result of https://github.com/moby/moby/pull/37485
1820278,2019-03-18 13:47:30 UTC,"Yes, I tried that while connected to the vpn with no effect"
1820283,2019-03-15 15:41:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/643613"
1820283,2019-03-15 15:45:09 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/643615"
1820283,2019-03-19 07:56:31 UTC,"Reviewed:  https://review.openstack.org/643613
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=18c40cacc13d76bf8199d61cac6ecc2af3122c8f
Submitter: Zuul
Branch:    master"
1820283,2019-03-20 03:56:27 UTC,"Reviewed:  https://review.openstack.org/643615
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0c72e63948e053020e065769d353b95bc1989dd5
Submitter: Zuul
Branch:    master"
1820285,2019-08-09 17:30:12 UTC,"I would like to fix it, I am new to Openstack but I have worked on python earlier. So can pick this one?"
1820285,2019-08-09 18:01:05 UTC,"Veera, yes if this is something that is interesting to you please go ahead and assign it to yourself."
1820285,2019-08-13 10:19:23 UTC,"Thanks, Colleen. Will fix this soon"
1820287,2019-03-19 05:13:06 UTC,"If it's bare metal, the only way I know of is to use serial port."
1820287,2019-03-16 16:27:36 UTC,Would it be possible to get earlier trace?
1820287,2019-03-16 21:43:35 UTC,"This happens only sporadically. If it happens, is there some keyboard
sequence I can use to dump more information, or is the system totally
frozen at this point?"
1820287,2019-03-15 14:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820287,2019-03-15 14:20:43 UTC,I can't get logs from the system because it's kernel panic'd.
1820288,2020-02-27 08:29:32 UTC,Marking incomplete waiting for the debian discusison to happen to then jointly go on on this.
1820288,2020-02-17 08:58:05 UTC,"It seems that permission has been changed, in 16.04 localhost privileges are
drwxrwxr-x 2 root tomcat8 4096 Dec 22 10:22 localhost"
1820288,2020-02-26 14:20:15 UTC,"Hi Arnaud,
this is odd."
1820288,2020-02-27 07:42:17 UTC,"The subfiles are installed via:
debian/tomcat8-admin.install:1:debian/context/manager.xml          /etc/tomcat8/Catalina/localhost/
debian/tomcat8-admin.install:2:debian/context/host-manager.xml     /etc/tomcat8/Catalina/localhost/"
1820288,2020-02-27 07:49:46 UTC,"On install it already changes from:
drwxr-xr-x 2 root root  2 Sep  9 19:47 localhost/
(unpack)
to
drwxr-xr-x 2 root tomcat8  2 Sep  9 19:47 localhost/
(after postinst and service start)"
1820288,2020-02-27 08:02:50 UTC,"Arr, I'm blind - it could have been so easy:
lrwxrwxrwx 1 root root 12 Sep  9 19:47 /var/lib/tomcat8/conf -> /etc/tomcat8/"
1820288,2020-02-27 08:10:33 UTC,"The permission difference 775 vs 755 isn't in the same place.
The chown is from the postinst, but the initial (and never changed) 775/755 is from unpack:"
1820288,2020-02-27 08:28:47 UTC,Comparing build logs I see:
1820288,2020-06-26 23:54:22 UTC,Thanks for all the debugging Christian! Very useful :)
1820289,2019-03-15 14:23:15 UTC,"This is already fixed in master, needs to be backported in rocky."
1820289,2019-03-15 22:43:44 UTC,"Reviewed:  https://review.openstack.org/643507
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=745369e8ac77f84f03ad7498b112888392ee094d
Submitter: Zuul
Branch:    stable/rocky"
1820289,2019-06-21 13:48:07 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1820292,2019-03-15 20:22:52 UTC,"I think displaying all is a better solution (you may want to remove the First 30 barcode phrase). Hopefully, one would not have a file where that many failed very often. Usually that occurs when a file of previously deleted barcodes is inadvertently uploaded."
1820292,2019-03-15 19:18:24 UTC,"Elaine, unfortunately the egAlertDialog feature that I'm using to display the alert doesn't allow for paging or any text formatting.  And I don't think my skills are up to creating a new grid view popup of the results that would add in the paging."
1820292,2019-03-19 18:18:32 UTC,I am marking this as needsdiscussion -- since I think we should discuss what would be the most useful UI for catalogers
1820292,2019-03-15 15:05:13 UTC,Here is a screenshot of the alert.  I set it up to only show the first 30 barcodes that were not found.  I don't want the alert to grow too large if there are a huge number of not found barcodes.  I just arbitrarily chose 30 for the number to show.  If anyone has any arguments about more or less please let me know.  I figured 30 is enough for looking into what problems there are from the source data.
1820292,2019-03-15 15:22:17 UTC,I like the message but would prefer to either see all of them or have the ability to page through to the next 30 until all are viewed. I would probably copy the alert message so that I could follow up and find out why they didn't load.
1820296,2020-11-14 15:44:32 UTC,"Kernels do have to be signed with UEFI methods, we do not support GPG."
1820296,2020-11-14 15:24:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820298,2019-04-01 12:30:22 UTC,"Fixed in revision 33e594e63edb667a49289bf004a1151966841024
https://git.launchpad.net/kicad/patch/?id=33e594e63edb667a49289bf004a1151966841024"
1820298,2019-04-21 17:37:16 UTC,It would appear the symbol editor has the same bug....
1820298,2019-06-04 12:58:43 UTC,"Fixed in revision 7c337ec45df1a94261f4cb5e4d06da8242621eb6
https://git.launchpad.net/kicad/patch/?id=7c337ec45df1a94261f4cb5e4d06da8242621eb6"
1820298,2019-06-04 14:13:25 UTC,This needs cherry-picking to 5.1.
1820302,2020-07-21 07:29:03 UTC,Removing milestone as we're not able to reproduce this issue.
1820302,2020-04-07 11:48:50 UTC,I am going to mark this as incomplete. To reopen please follow Ryans requests in comment #6 and supply apparmor logs.
1820302,2020-04-07 11:43:50 UTC,On the hypervisor:
1820302,2020-04-07 11:42:37 UTC,Bundle used for test deployment
1820302,2020-04-07 11:41:11 UTC,I have not been able to reproduce this. I have done an sriov enabled bionic/queens deploy creating the sriov port as outlined in the bug description and it works for me. I will add the bundle I tested with as an attachment. After deployment I tested with:
1820302,2019-10-29 13:49:42 UTC,De-escalating to Field-High as we have a work-around in place which consists of disabling AppArmor.
1820302,2020-07-21 07:29:41 UTC,Its been over 3 months since this bug was last touched and there is no further information provided to enable reproduction no marking this bug as Invalid.
1820302,2019-08-20 22:15:46 UTC,"We've received more info about the reproducer, moving bug task back to NEW."
1820302,2019-05-15 07:06:41 UTC,"Hi David,"
1820302,2019-05-15 06:41:28 UTC,"Hi David,"
1820302,2019-05-14 20:56:16 UTC,"Nicolas,"
1820302,2019-12-10 19:41:58 UTC,"And, we seem to still be at the point of David's comment #1:  Need to reproduce and capture logs."
1820302,2020-10-30 15:50:08 UTC,Can i ask if you applied CIS hardening as part of reproducer?
1820303,2019-05-17 04:17:26 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1820303,2019-03-18 03:14:22 UTC,Can you select the session you want on the login screen by clicking on the cog/gear icon?
1820305,2019-03-15 16:19:28 UTC,"I should add that if the library is pulled from a DB, as is being discussed at https://lists.launchpad.net/kicad-developers/msg39676.html and https://lists.launchpad.net/kicad-developers/msg39686.html, or from GH if there is a v4-like behavior re-introduced, keeping the library tables in sync with the library folders would be important."
1820307,2019-03-15 17:18:55 UTC,A 409 means that a conflict has occurred. MAAS internally retries 10 times to try and handle conflicts with IP allocation when allocating a machine with AUTO IP addresses. If you are getting failures in this case then the its now the clients turn to retry the action.
1820307,2019-03-15 17:42:16 UTC,"Sam,"
1820307,2019-03-15 17:42:35 UTC,"We don't use AUTO IP, we use STATIC."
1820307,2019-09-19 09:34:35 UTC,Is this a request for us to treat 409 as a retry error?
1820307,2019-09-19 11:41:07 UTC,"IDK if you want to treat this bug as that issue, but gomaasapi should retry on 409 respecting the Retry-After header."
1820307,2019-09-20 12:29:31 UTC,"Returning 503 would be incorrect, since the service is in fact available. If anything needs to happen, it's either to debug to see if we somehow can avoid the 409, or Juju needs to retry on 409."
1820307,2019-11-20 04:17:37 UTC,[Expired for juju because there has been no activity for 60 days.]
1820308,2019-04-02 09:51:48 UTC,All tasks have been completed and the bug is being set to Fix Released
1820311,2019-04-02 09:51:36 UTC,All tasks have been completed and the bug is being set to Fix Released
1820311,2019-07-16 21:46:28 UTC,"linux-kvm is currently 5.0.0-1010.11 in disco, looks like this bug got left behind. Closing."
1820314,2019-04-01 11:12:06 UTC,"asrock-mobo from live 19.04 live, sudo alsa force-reloading, pulseaudio -k. Did not work"
1820314,2019-04-01 11:14:52 UTC,"xubuntu@xubuntu:~$ sudo alsa force-reload
Unloading ALSA sound driver modules: snd-seq-midi snd-seq-midi-event snd-seq snd-rawmidi snd-seq-device snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer (failed: modules still loaded: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer).
Loading ALSA sound driver modules: snd-seq-midi snd-seq-midi-event snd-seq snd-rawmidi snd-seq-device snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer.
xubuntu@xubuntu:~$ alsamixer -V all
xubuntu@xubuntu:~$ pulseaudio -k
xubuntu@xubuntu:~$ sudo apt remove timidity
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Il pacchetto ""timidity"" non è installato e quindi non è stato rimosso
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati."
1820314,2019-04-01 10:17:50 UTC,nope even under xubuntu live 19.04 sound card 0 does not work (alc662) 5.0.0.8
1820314,2019-04-08 07:30:56 UTC," I reported same bug (several times) on the same system (on different partition - one fresh installed and one xubuntu 18.04 ). On the first partion the on board sound card are not detected (dummy on pavucontrol). On the 2nd partition pavucontrol shows unplugged even modifyng with several options snd-hda-intel in /etc/modprobe.d/alsa-base.conf. Only HDMI on gpu workshop always. Diff alsa-info of both installation are 0.
    Il giovedì 4 aprile 2019, 04:50:49 CEST, Daniel van Vugt <email address hidden> ha scritto:"
1820314,2019-04-28 19:33:13 UTC,Any news??
1820314,2019-04-01 15:41:43 UTC,"Performing
sudo apt-get -y --reinstall install linux-sound-base alsa-base alsa-utils lightdm ubuntu-desktop linux-image-`uname -r` libasound2
On fresh install 18.04 partition on a different partition did not dolce the problem. Is there any step by step"
1820314,2019-04-01 07:48:12 UTC,"Tried also kernel 4.15, 4.18 & ppa alsa daily. No sound. None of the port work neither output nor input (mic). I will try live 19.04 asap"
1820314,2019-03-15 16:50:37 UTC,"In the summary it is shown xubuntu 16.04 by I upgraded a long time ago to 18.04 lts both the problem occured even under 16.04 lts
https://forum.ubuntuusers.de/topic/audio-problem-wie-folgend/"
1820314,2019-04-01 03:09:13 UTC,It appears part of the problem here is timidity (bug 1793640). Please uninstall timidity and timidity-related packages and reboot.
1820314,2019-03-19 13:30:33 UTC,BIOS setting in the video above
1820314,2019-03-19 13:29:57 UTC,https://streamable.com/5j96k
1820314,2019-03-19 10:40:43 UTC,The problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying alsa-base in options snd-hda-intel model=auto or options snd-hda-intel model=asrock-mobo or options snd-hda-intel model=generic.; all on board audio port are shown as unplugged. Thus HDMI of the Nvidia GTX 1050ti seems to work perfectly when I connected to TV HDMI input (but could not steal TV 4 ever)
1820314,2019-03-19 10:30:35 UTC,https://ubuntuforums.org/showthread.php?t=2414882&p=13845231#post13845231
1820314,2019-04-01 06:23:20 UTC," Timidity is not installed
    Il lunedì 1 aprile 2019, 05:16:02 CEST, Daniel van Vugt <email address hidden> ha scritto:"
1820317,2019-04-01 18:08:36 UTC,This bug was fixed in the package firewalld - 0.6.3-5ubuntu4
1820317,2019-03-25 14:08:14 UTC,I upload 0.6.3-5ubuntu4 for the Depends/Recommends update but expect it to fail due to the ipset issues. I filed bug 1821596 for that.
1820317,2019-03-25 13:59:38 UTC,I took a look at this and found that:
1820317,2019-03-25 14:03:50 UTC,"$ ./remove-package -m ""1.8.2 abandoned, will wait for 1.8.3 (LP: #1820317)"" -s disco-proposed iptables
Removing packages from disco-proposed:
 iptables 1.8.2-4ubuntu1 in disco
  iptables 1.8.2-4ubuntu1 in disco amd64
  iptables 1.8.2-4ubuntu1 in disco arm64
  iptables 1.8.2-4ubuntu1 in disco armhf
  iptables 1.8.2-4ubuntu1 in disco i386
  iptables 1.8.2-4ubuntu1 in disco ppc64el
  iptables 1.8.2-4ubuntu1 in disco s390x
  iptables-dev 1.8.2-4ubuntu1 in disco amd64
  iptables-dev 1.8.2-4ubuntu1 in disco arm64
  iptables-dev 1.8.2-4ubuntu1 in disco armhf
  iptables-dev 1.8.2-4ubuntu1 in disco i386
  iptables-dev 1.8.2-4ubuntu1 in disco ppc64el
  iptables-dev 1.8.2-4ubuntu1 in disco s390x
  libip4tc-dev 1.8.2-4ubuntu1 in disco amd64
  libip4tc-dev 1.8.2-4ubuntu1 in disco arm64
  libip4tc-dev 1.8.2-4ubuntu1 in disco armhf
  libip4tc-dev 1.8.2-4ubuntu1 in disco i386
  libip4tc-dev 1.8.2-4ubuntu1 in disco ppc64el
  libip4tc-dev 1.8.2-4ubuntu1 in disco s390x
  libip4tc0 1.8.2-4ubuntu1 in disco amd64
  libip4tc0 1.8.2-4ubuntu1 in disco arm64
  libip4tc0 1.8.2-4ubuntu1 in disco armhf
  libip4tc0 1.8.2-4ubuntu1 in disco i386
  libip4tc0 1.8.2-4ubuntu1 in disco ppc64el
  libip4tc0 1.8.2-4ubuntu1 in disco s390x
  libip6tc-dev 1.8.2-4ubuntu1 in disco amd64
  libip6tc-dev 1.8.2-4ubuntu1 in disco arm64
  libip6tc-dev 1.8.2-4ubuntu1 in disco armhf
  libip6tc-dev 1.8.2-4ubuntu1 in disco i386
  libip6tc-dev 1.8.2-4ubuntu1 in disco ppc64el
  libip6tc-dev 1.8.2-4ubuntu1 in disco s390x
  libip6tc0 1.8.2-4ubuntu1 in disco amd64
  libip6tc0 1.8.2-4ubuntu1 in disco arm64
  libip6tc0 1.8.2-4ubuntu1 in disco armhf
  libip6tc0 1.8.2-4ubuntu1 in disco i386
  libip6tc0 1.8.2-4ubuntu1 in disco ppc64el
  libip6tc0 1.8.2-4ubuntu1 in disco s390x
  libiptc-dev 1.8.2-4ubuntu1 in disco amd64
  libiptc-dev 1.8.2-4ubuntu1 in disco arm64
  libiptc-dev 1.8.2-4ubuntu1 in disco armhf
  libiptc-dev 1.8.2-4ubuntu1 in disco i386
  libiptc-dev 1.8.2-4ubuntu1 in disco ppc64el
  libiptc-dev 1.8.2-4ubuntu1 in disco s390x
  libiptc0 1.8.2-4ubuntu1 in disco amd64
  libiptc0 1.8.2-4ubuntu1 in disco arm64
  libiptc0 1.8.2-4ubuntu1 in disco armhf
  libiptc0 1.8.2-4ubuntu1 in disco i386
  libiptc0 1.8.2-4ubuntu1 in disco ppc64el
  libiptc0 1.8.2-4ubuntu1 in disco s390x
  libxtables-dev 1.8.2-4ubuntu1 in disco amd64
  libxtables-dev 1.8.2-4ubuntu1 in disco arm64
  libxtables-dev 1.8.2-4ubuntu1 in disco armhf
  libxtables-dev 1.8.2-4ubuntu1 in disco i386
  libxtables-dev 1.8.2-4ubuntu1 in disco ppc64el
  libxtables-dev 1.8.2-4ubuntu1 in disco s390x
  libxtables12 1.8.2-4ubuntu1 in disco amd64
  libxtables12 1.8.2-4ubuntu1 in disco arm64
  libxtables12 1.8.2-4ubuntu1 in disco armhf
  libxtables12 1.8.2-4ubuntu1 in disco i386
  libxtables12 1.8.2-4ubuntu1 in disco ppc64el
  libxtables12 1.8.2-4ubuntu1 in disco s390x
Comment: 1.8.2 abandoned, will wait for 1.8.3 (LP: #1820317)
Remove [y|N]? y
1 package successfully removed."
1820320,2020-04-29 12:53:48 UTC,"I set this bug to won't fix because I think it is too late, now, to go back and fix this old upgrade script. If anyone else disagrees, they can reopen this bug."
1820321,2020-05-21 06:00:31 UTC,Just a note:
1820321,2019-03-17 08:41:06 UTC,"Hi,
Cloud please provide the version of the neutron you tested?"
1820321,2019-03-17 19:20:11 UTC,"[stack@undercloud-0 ~]$ cat /etc/rhosp-release
Red Hat OpenStack Platform release 14.0.1 RC (Rocky)
[stack@undercloud-0 ~]$ yum info openstack-neutron
Loaded plugins: search-disabled-repos
Available Packages
Name        : openstack-neutron
Arch        : noarch
Epoch       : 1
Version     : 13.0.3
Release     : 0.20190119134915.886782c.el7ost
Size        : 28 k
Repo        : rhelosp-14.0-puddle/x86_64
Summary     : OpenStack Networking Service
URL         : http://launchpad.net/neutron/
License     : ASL 2.0
Description :
            : Neutron is a virtual network service for Openstack. Just like
            : OpenStack Nova provides an API to dynamically request and configure
            : virtual servers, Neutron provides an API to dynamically request and
            : configure virtual networks. These networks connect ""interfaces"" from
            : other OpenStack services (e.g., virtual NICs from Nova VMs). The
            : Neutron API supports extensions to provide advanced network
            : capabilities (e.g., QoS, ACLs, network monitoring, etc.)"
1820321,2019-03-17 19:21:48 UTC,"hi,"
1820321,2019-03-21 08:05:25 UTC,I have tested with the last version and the message is:
1820321,2019-04-28 07:57:02 UTC,"I set it as confirmed and wishlist priority because it is in fact valid proposal for improvement but IMO may be hard to implement because error message that attribute is unrecognized comes from neutron-lib's API validators and it is like that because ""dvr"" extension is not loaded simply."
1820322,2019-03-25 20:23:25 UTC,I agree with Anna. It is not something our libraries would wish to remove.
1820322,2019-03-25 19:11:44 UTC,"Our libraries love this feature, so preference would be to make it optional rather than removing it."
1820323,2019-03-16 15:32:20 UTC,"This bugreport was filed with the stock 16.04(.1) stack though, with kernel 4.4 and xserver 1.18 but with an updated mesa. The failure here is that some symlinks to amdgpu-pro got overwritten (since they were owned by mesa, not amdgpu-pro..), and those need to be fixed manually."
1820323,2020-01-17 07:04:45 UTC,"- Original shipping condition:
* Dell Farallon + WX2100
* linux-image-4.4.0-36-generic + amdgpu-17.10-429170"
1820323,2019-06-11 04:17:25 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1820323,2019-04-11 15:36:02 UTC,https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory  Is there a solution or workaround for this?
1820323,2019-04-10 14:37:45 UTC,Any updates on this bug?  Is there anything else I need to provide you?
1820323,2019-06-13 05:41:24 UTC,"the only solution is to install a newer amdgpu-pro which supports 16.04.3, there's nothing we can do on ubuntu side"
1820323,2019-03-18 07:46:02 UTC,From xserver.errors.txt:
1820323,2019-03-18 05:56:22 UTC,"No need for crash debugging, since this is a known issue in the amdgpu-pro package. This should help:"
1820323,2019-03-18 03:20:38 UTC,"Also, to help us find crashes from other people that are the same as this one, please follow these instructions:"
1820323,2019-03-28 19:33:02 UTC,The uninstall and reinstall of amdgpu-pro has not worked for me.  I have also tried to purge amdgpu-core and amdgpu-dmks which I was told by others got around this issue.  I have not been successful thus far.  Any other suggestions and or logs needed to help me find a suitable workaround until this is resolved?
1820324,2019-06-17 08:54:41 UTC,"Hello:
    I did the following in the 2019-5 and 2018-10 versions.
    In the 2019-5 version, after creating the endpoint, send the magnum service-list command to indicate that the connection is not on the service (log1). Directly starting the magnum service failed, indicating that there is no such service (log2). It is currently inferred that the 2019-5 version does not have the magnum service or other related components installed, causing the magnum service to fail to start.
    In the 2018-10 version, after the above-mentioned hand-operating operation, the connection timeout (log3) is prompted. During the investigation, it was found that there was a problem with the rabbitmq installed by default, and the rabbitmq service started to report an error (log4), inferring that rabbitmq caused magnum to fail to work properly. Attempts to reinstall erlang and rabbitmq, and then based on further results to determine whether I need to manually install magnum.
    Can you provide the steps to make the magnum service start successfully."
1820324,2019-07-04 03:15:02 UTC,"Close this ticket as Magnum is not a supported feature for stx.2.0. If anybody require Magnum support, we shall open a feature request from Storyboard."
1820324,2019-07-03 13:25:34 UTC,In the current codebase:
1820324,2019-07-04 03:24:18 UTC,"@Al Bailey (albailey1974):
  Thank you very much for your reply.
  The information you mentioned has been encountered before and has been resolved. Please refer to my information in step_3 in  my reply to ""#11"".
  It has been confirmed that the latest version of starlingx does not support the magnum service. It is recommended to turn off the bug."
1820324,2019-07-03 03:03:16 UTC,"Hello,
    I tried to configure magnum in the starlingx (2019/06/26) environment, according to the official website(https://docs.openstack.org/magnum/latest/install/install-rdo.html#top), after installation When the related service is prompted, there is no corresponding download resource. The log is as follows:
---------------------
controller-0:~$ sudo yum install openstack-magnum-api openstack-magnum-conductor python-magnumclient
Password:
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
base                                                                                                                            | 3.6 kB  00:00:00
extras                                                                                                                          | 3.4 kB  00:00:00
updates                                                                                                                         | 3.4 kB  00:00:00
No package openstack-magnum-api available.
No package openstack-magnum-conductor available.
Nothing to do
---------------------
    Trying to manually install the above 3 services did not succeed.
    It is currently judged that the new version of starlingx does not support the magnum service and may be replaced by other services.
    According to the current situation, if magnum is no longer maintained in the new version of starlingx, it is recommended to close the bug; if you need to further confirm other matters, then analyze it according to the actual situation."
1820324,2019-06-20 09:01:57 UTC,"Hello,
    Sorry, please ignore the last reply.
    According to the following steps, the ""magnum-service-list"" command is successfully sent.
   1.StarlingX 2018.10 virtual machine deployment,
    See https://docs.starlingx.io/deployment_guides/current/simplex.html
   2.Install MySQL5.6
   3.magnum related configuration,
    See https://docs.openstack.org/magnum/latest/install/install-rdo.html#top
   4.Execute the command ""magnum service-list"""
1820324,2019-04-09 09:15:44 UTC,"@mao Jiaming: Magnum was already in the build (you can check the rpm), I don't have to download it  but yes, it's true that I have to enable those services with the commands as given through the openstack cli."
1820324,2019-03-22 16:07:16 UTC,Another data point on this: I had a brief discussion with Jerry Sun who has some previous experience with magnum. He believes that magnum is not functional in stx.2018.10.
1820324,2019-04-01 01:43:42 UTC,"Hi,
    When I was trying to reproduce this bugs, I found some difference between the starlingx and the magnum installation guides. Would you kindly show me how you solve these problems.
     1. The database in starlingx is postgresql, Since the guides requires mysql.
     2. How do you start the magnum service Since I cannot find the file magnum-api.service and the magnum-conductor.service in the starlinx without downloading them."
1820324,2019-03-25 17:33:04 UTC,Thanks for the info. I'll leave it to Cindy to assign someone to investigate further if that's what she wishes to do.
1820324,2019-03-25 15:57:19 UTC,"I have enable as per the Openstack documentation as per link https://docs.openstack.org/magnum/latest/install/install-guide-from-source.html except downloading magnum, as it was already there. I had enabled endpoints accordingly.
I believe that StarlingX is open and support Openstack components  without any problem, so should be some only configuration problem."
1820324,2019-03-20 17:38:19 UTC,"Requesting that Bruce follows up with the reporter regarding the importance of this issue. My recommendation is to close as ""Won't Fix"" with a suggestion to use stx master for any container related activities."
1820324,2019-03-20 17:37:05 UTC,"There hasn't been any magnum testing done as part of the verification of stx.2018.10.
stx master now provides support for k8s containers. Suggest you try using master."
1820324,2019-04-08 17:32:18 UTC,Marking as Incomplete until the reporter provides the info requested by the developer investigating the issue.
1820325,2019-07-05 13:34:11 UTC,"Reviewed:  https://review.opendev.org/667363
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=99cd5ec10c910bff3c238942a613faafdce0a2e2
Submitter: Zuul
Branch:    stable/stein"
1820325,2019-06-25 13:11:12 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/667363"
1820325,2019-04-11 09:37:49 UTC,This issue was fixed in the openstack/kolla 7.0.2 release.
1820325,2019-04-09 12:32:33 UTC,"Reviewed:  https://review.openstack.org/650855
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d93c604d7af03e8b096faea8acaaaef718df2cd5
Submitter: Zuul
Branch:    master"
1820325,2019-04-08 11:26:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/650855"
1820325,2019-04-05 13:54:07 UTC,This issue was fixed in the openstack/kolla 8.0.0.0rc1 release candidate.
1820325,2019-04-05 13:59:30 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.
1820325,2019-03-18 15:42:24 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/644250"
1820325,2019-03-15 19:41:53 UTC,"dumb-init is executed with --single-process so only forwards the term signal to mysqld_safe script, which apparently just ignores it. We need to call this to shutdown:"
1820325,2019-03-15 19:21:22 UTC,"Looks like we're killing the maridb service, which leaves around old state, preventing the upgrade."
1820325,2019-03-15 18:42:19 UTC,"In order to run mysql_upgrade, I had to remove the directory /var/lib/mysql/.pki, otherwise we get the following error:"
1820325,2019-03-15 18:15:25 UTC,"Following https://serverfault.com/questions/379714/unknown-unsupported-storage-engine-innodb-mysql-ubuntu, I removed /var/lib/mysql/ib_logfile0 and /var/lib/mysql/ib_logfile1, which allowed the service to start. There are various bad looking logs, e.g."
1820325,2019-03-26 00:25:44 UTC,"Reviewed:  https://review.openstack.org/644250
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=b25c0ee4772fdf04fe6f263a8e81571204f706ff
Submitter: Zuul
Branch:    master"
1820328,2021-02-19 21:54:38 UTC,No longer applies to the website.
1820328,2019-03-15 21:38:39 UTC,"Thanks for the heads-up, but it's done on purpose (only for the next couple of Fridays). Some things are just more important than XML.
You can get the homepage back at https://lxml.de/index.html"
1820328,2019-05-14 17:39:53 UTC,"I think this should stay in place as long as FFF is a thing, and not just a couple of weeks."
1820328,2019-05-14 17:51:09 UTC,"Could it be iframed or have a couple second notice before redirect? I get
and think the cause/supporting is good but it was extremely confusing being
new to the project."
1820328,2019-05-14 18:07:44 UTC,"Granted that a frameset would be nicer. I didn't want to invest too much time into this at the beginning, so a redirect was the quickest way to do it."
1820328,2019-08-17 00:03:02 UTC,"""The road to hell is paved with good intentions.""
Are you aware that a plenty of people start to google until they find this bug because they are simply confused by this redirect? How big is the carbon footprint caused by this redirect?"
1820328,2019-08-18 12:57:54 UTC,1) Some people certainly need a little longer until they understand the obvious. That is perfectly ok.
1820329,2019-03-15 18:14:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820332,2019-05-18 04:17:30 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1820332,2019-03-18 16:20:41 UTC,There seems to be something wrong with the mirror of the Ubuntu archive which you are using:
1820334,2019-07-18 13:02:23 UTC,"Sahara is sadly lacking any owner within Ubuntu; the package originated from Debian, and we version (ubuntu-openstack) bump it alongside the rest of OpenStack in Ubuntu to keep it series aligned.  Its possible the Debian OpenStack team might be undertaking this work."
1820337,2019-09-27 09:05:31 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1820337,2019-07-10 21:40:28 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1820337,2019-06-18 03:41:41 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1820337,2019-06-06 06:24:50 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1820337,2019-04-22 05:26:03 UTC,"Reviewed:  https://review.opendev.org/647913
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ddc2c9118a2907b005c06ce30949c8c3fd7a7aef
Submitter: Zuul
Branch:    stable/queens"
1820337,2019-04-26 17:15:51 UTC,This issue was fixed in the openstack/nova 16.1.8 release.
1820337,2019-04-22 15:13:40 UTC,"Reviewed:  https://review.opendev.org/647916
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3d85f7e58197300473676980366369b29d14e187
Submitter: Zuul
Branch:    stable/pike"
1820337,2019-04-17 20:29:51 UTC,"Reviewed:  https://review.openstack.org/647911
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8cb120964cb33950a80c9775ffbfe4eb5818153
Submitter: Zuul
Branch:    stable/rocky"
1820337,2019-03-26 19:58:17 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/647902"
1820337,2019-03-26 22:38:57 UTC,"Reviewed:  https://review.openstack.org/645546
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=64f6cbc9120e3c288f312eddc59452dee4998f93
Submitter: Zuul
Branch:    master"
1820337,2019-03-22 11:44:13 UTC,"This is a genuine race which is still present in master, but for some reason I haven't managed to work out I can only reproduce on Rocky. I can reproduce it reliably on Rocky by adding a pdb breakpoint (a sleep doesn't work) to stub_check_num_instances_quota in test_bfv_quota_race_local_delete. The same does not reproduce on master... although the bug is still present."
1820337,2019-03-22 11:53:27 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/645546"
1820337,2019-03-22 17:38:59 UTC,"Just a note, that according to Logstash the problem is there in Queens and Pike, too."
1820337,2019-04-12 13:01:31 UTC,"Reviewed:  https://review.openstack.org/647902
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eec39762cf5343b354e2ac06a6682a7c3b4230c2
Submitter: Zuul
Branch:    stable/stein"
1820337,2019-03-26 20:12:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/647913"
1820337,2019-03-26 20:19:38 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/647916"
1820337,2019-03-26 20:07:11 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/647911"
1820338,2020-01-27 21:00:08 UTC,"I wouldn't so quickly assume this is an issue with Plank.  I recently ran into this same thing.  It seems the way Plank even knows which icons to show is the distributions .desktop files they ship, etc... and the name the Electron app sets must match some of the meta-data in the .desktop file."
1820339,2019-03-15 19:42:17 UTC,"Speaking of:
https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1820339_pg10_vandelay / working/user/jboyer/lp1820339_pg10_vandelay"
1820339,2019-04-25 18:25:14 UTC,"Hmm, this solution appears to not be backwards compatible with less than PG 10 (like if someone was running PG 9.4-9.6) because REGEXP_MATCH() only exists in PG10+ according to PG documentation.  They included a tip for changing these to some sort of sub-select for REGEXP_MATCHES() - https://www.postgresql.org/docs/current/functions-matching.html"
1820339,2019-04-25 22:27:01 UTC,"Ben Shum and I found a solution that works on Pg 9.4 through Pg 10. We use the REGEXP_MATCHES function that Pg 10 complains about, but by moving it into a subselect it returns an array instead of a set of rows."
1820339,2019-04-26 05:44:22 UTC,Signoff on changes:  user/bshum/lp1820339_pg10_vandelay_signoff
1820339,2019-05-08 14:54:44 UTC,"Tested and pushed to master and rel_3_3, thanks Jason and Ben!"
1820341,2019-03-15 20:38:48 UTC,after changing rabbitmq-server config to enable the plugin:
1820341,2019-03-15 20:40:48 UTC,"Also, `sudo rabbitmqctl list_users` shows:"
1820344,2019-03-15 19:44:03 UTC,"Note, we added a workaround rule to snapd and it is not blocked at this time."
1820344,2019-07-10 23:11:39 UTC,"I'd like to add that in updating the Snap to 18.09.7, this has changed slightly thanks to https://github.com/opencontainers/runc/pull/1984 such that the denial is now on ""/bin/runc"" instead of ""/"", which is slightly better I suppose (there will likely be a snapd PR shortly to update/increase the snapd workaround to compensate)."
1820344,2019-07-11 19:13:48 UTC,"@Tianon - FYI, snapd is being adjusted for this: https://github.com/snapcore/snapd/pull/7090"
1820348,2019-07-17 14:35:49 UTC,"So, looks like I reported a duplicate bug...
https://bugs.launchpad.net/launchpad-buildd/+bug/1836870"
1820348,2019-03-15 21:03:09 UTC,"And getgrid(110) returns NULL, so I believe this is why the package test is failing. I can probably work around that by checking for this, and selecting another group."
1820348,2019-03-15 20:40:01 UTC,"I also ran getent group from d/rules, and the resulting list has no group with gid 110. Is ldap enabled there, or some sort of network user/group source enabled?"
1820349,2019-05-29 09:08:26 UTC,I wonder WHY it is no supported.. we need to check that.
1820349,2020-01-06 07:58:02 UTC,"if coordination url is not defined then it is not supported.
after https://review.opendev.org/#/c/700507/ it is now supported by default in devstack"
1820349,2020-01-09 10:20:16 UTC,"Reviewed:  https://review.opendev.org/701164
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=bb94ca1fede74c84bd7192f19a7f8497f0756432
Submitter: Zuul
Branch:    master"
1820349,2020-03-02 14:51:44 UTC,This issue was fixed in the openstack/mistral 10.0.0.0b2 development milestone.
1820350,2019-03-21 17:35:06 UTC,"Thank you for you report. Please note that for usability a default ruleset is put in use by design and documented in the ufw(8) man page. Users are free to fine-tune those defaults for site-specific needs as described in the ufw-framework(8) man page. As a result option 'a' is out of scope. Option 'b' does make sense and is something that can be looked at with 'status verbose' (implementation-wise it might make sense to check if all the defaults are in use and if they are, mention those defaults, and if they are not, mention that custom rules are in effect. I'm not sure yet how this should be represented in the UI."
1820352,2020-04-28 12:32:44 UTC,Might be fixed by https://code.launchpad.net/~sylvain-pineau/checkbox-ng/+git/checkbox-ng/+merge/381568
1820357,2020-04-22 08:14:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820357,2020-04-22 08:19:54 UTC,"It seems better is to recommend free/open source communications services, like Jitsi https://meet.jit.si or Jami (GNU Ring)"
1820357,2020-04-22 10:10:44 UTC,Thanks for your report!
1820357,2020-09-10 19:09:29 UTC,"I decided to drop the whole ""Chat & Social Networking"" section. It has consisted of a few pages without any equivalent in GNOME Help. The contents is indeed obsolete, and I'm closing this bug by making it a duplicate of bug #1895065. The Ubuntu docs team does not currently have the resources to maintain the section."
1820358,2019-04-18 00:32:41 UTC,"That screen shows yo the metadata for the target book, not the result of
the merge, it would be confusing to add metadata for the merged book to
it."
1820358,2019-06-17 04:17:49 UTC,[Expired for calibre because there has been no activity for 60 days.]
1820360,2019-04-30 16:50:58 UTC,"On Tue, Apr 30, 2019 at 02:02:18PM -0000, Scott Moser wrote:

> Well you gave the example correctly.
> Which behavior should the user expect if they provide /seed and /seed
> exists?
>
> I'd argue that changing the behaviour based on the presence or lack of a
> directory is surprising. Rather than document that behaviour oddity I'd
> suggest just documenting that a trailing slash is required if that is what
> the user wants.
"
1820360,2019-04-30 14:02:18 UTC,"Well you gave the example correctly.
Which behavior should the user expect if they provide /seed and /seed
exists?"
1820360,2019-06-30 04:17:42 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1820360,2019-04-27 01:34:18 UTC,"This is functioning as designed and imo as it should. It allows for a
superset of function.  You can then see with something like
   http://myhost/my.cgi?file=
Or
   /data/seed-"
1820360,2019-04-26 18:51:20 UTC,"> Cloud-init ran, however it couldn't find the specified location as it tried to access
> /boot/firmware/seedmeta-data and /boot/firmware/seeduser-data
"
1820360,2019-04-29 13:39:20 UTC,"On Sat, Apr 27, 2019 at 01:34:18AM -0000, Scott Moser wrote:

> This is functioning as designed and imo as it should. It allows for a
> superset of function.  You can then see with something like
>    http://myhost/my.cgi?file=
> Or
>    /data/seed-
>
> Possibly it could have better fail messages, but insisting on concatenating
> with a '/' seems like a loss if functionality with little benefit.
"
1820361,2019-03-16 13:41:14 UTC,"# /etc/udev/udev.conf
#
# udev_log=debug"
1820361,2019-03-16 19:50:03 UTC,https://github.com/systemd/systemd/issues/12019#issuecomment-473578815
1820363,2019-03-16 00:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820363,2019-03-16 08:52:55 UTC,"Since it works in v4.8 but not v4.9, please do a kernel bisection."
1820363,2019-03-29 19:29:57 UTC,"What Firmware does Your card have?
There are many versions online and some of them are for Motherboards only (has different config for chips mounted on MB embedded chipset than for expansion card PCI/PCI_E)."
1820363,2019-03-31 14:00:36 UTC,"Hello,"
1820363,2019-04-03 16:58:25 UTC,@Fabien
1820363,2019-04-04 01:00:33 UTC,@Mike
1820363,2019-04-10 00:28:00 UTC,@Fabien
1820365,2019-07-14 04:17:39 UTC,[Expired for OpenStack API Layer because there has been no activity for 60 days.]
1820365,2019-07-14 04:17:38 UTC,[Expired for OpenStack Octavia Charm because there has been no activity for 60 days.]
1820365,2019-04-12 22:26:08 UTC,"Hi @fnordahl,"
1820365,2019-03-19 09:44:35 UTC,"@angelvargas does the deployment contain the Gnocchi charm, if so, did it require binding of the shared-db relation or was it able to cope without?"
1820365,2019-07-14 04:17:37 UTC,[Expired for mysql-shared charm interface because there has been no activity for 60 days.]
1820365,2019-03-19 09:23:53 UTC,"The classic charms appear to have a trick to do without the network binding:
https://github.com/openstack/charm-nova-cloud-controller/blob/b182ffa7f76c28220f6ee2430e7c320395a55956/hooks/nova_cc_hooks.py#L363"
1820365,2019-03-17 11:05:22 UTC,"Hi James, many thanks for the clear reply."
1820365,2019-03-17 09:41:11 UTC,Can you share your bundle including network space bindings for all charms?
1820365,2019-03-19 09:43:37 UTC,"I also see that the Gnocchi charm has this:
https://github.com/openstack/charm-gnocchi/blob/00adc4f2c856b120b634073620bfdd18dad48e81/src/lib/charm/openstack/gnocchi.py#L151"
1820368,2019-03-18 02:19:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1820368,2019-05-17 04:17:22 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1820369,2019-03-17 10:48:10 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1820369,2019-03-18 11:07:12 UTC,Thank you for your bug report. When/where did you get the issue?
1820369,2019-05-18 04:17:20 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1820370,2019-05-18 04:17:29 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1820370,2019-03-18 16:15:11 UTC,Please try installing the linux-generic package and then upgrading. From VarLogDistupgradeMainlog.txt:
1820371,2019-03-18 08:07:45 UTC,apport information
1820371,2019-03-18 08:07:44 UTC,apport information
1820371,2019-03-18 08:07:42 UTC,apport information
1820371,2019-03-18 08:07:41 UTC,apport information
1820371,2019-03-18 08:07:40 UTC,apport information
1820371,2019-03-18 08:07:39 UTC,apport information
1820371,2019-03-18 08:07:36 UTC,apport information
1820371,2019-03-21 05:58:53 UTC,Ok it's a Ubuntu preload system. Can you attach output of `dkms list`?
1820371,2019-03-18 08:07:34 UTC,apport information
1820371,2019-03-18 08:07:35 UTC,apport information
1820371,2019-03-18 08:07:33 UTC,apport information
1820371,2019-03-18 08:07:33 UTC,apport information
1820371,2019-03-18 03:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820371,2019-03-18 04:40:11 UTC,Is this due to recent upgrade?
1820371,2019-03-18 08:07:25 UTC,apport information
1820371,2019-03-18 03:28:24 UTC,The kernel is reporting zero supported sound cards:
1820371,2019-03-18 08:07:28 UTC,apport information
1820371,2019-03-18 08:07:30 UTC,apport information
1820371,2019-03-18 08:07:31 UTC,apport information
1820371,2019-03-18 08:07:32 UTC,apport information
1820371,2019-03-18 08:07:26 UTC,apport information
1820374,2020-08-16 03:15:44 UTC,I use CLI and openbox minimum install
1820377,2019-03-16 17:52:32 UTC,Turns out the problem was using SDDM as opposed to GDM.
1820381,2019-03-19 22:51:50 UTC,"Evergreen uses port 443 via Apache. So, if websocketd is running standalone it cannot use the same port as Apache. Whichever one starts first will block the other from using the port."
1820381,2019-03-25 16:37:07 UTC,Dear Jason
1820381,2019-03-23 11:14:40 UTC,That is correct. I should have noticed you are using OpenSRF version 3.0.2.
1820381,2019-03-23 08:22:05 UTC,Version 3.0.2
1820381,2019-03-23 08:13:03 UTC,Hi Jason
1820381,2019-03-19 22:28:44 UTC,"I tried through a diffrent machine..I am getting the error
http://192.168.10.3/eg/opac/home  : This url work fine.. but as soon as I tried to login..as staff.
This happen
https://192.168.10.3/eg/staff/login/
Not Found"
1820381,2019-03-19 16:36:52 UTC,Ps. I ran config with these options ./configure --prefix=/openils --sysconfdir=/openils/conf --enable-python  -with-websockets-port=443
1820381,2019-03-19 17:14:53 UTC,Hi Jason
1820381,2019-03-19 17:04:00 UTC,"Ok. You should have skipped the --with-websockets-port option if you're not using a proxy.  I'd try running configure again without that option, doing make, make install, and the chown steps of the instructions.  Then restarting OpenSRF services, apache2, and websockets. (This part of the README may not be very clear. Others have had similar issues.)"
1820381,2019-03-19 16:35:29 UTC,Hallo Jason
1820381,2019-03-18 19:21:06 UTC,"Hi, Edwin."
1820381,2019-03-19 22:21:27 UTC,"Hi Jason
I tried again.."
1820386,2019-06-25 08:33:12 UTC,I had some spare time to try to implemented the function with minimal changes to the code.
1820386,2019-06-25 18:13:21 UTC,"On 25/06/19 17:51, Wayne Stambaugh wrote:

> @Dino, thank you for the patch but given that the new schematic file
> format is going to be implemented soon, applying this patch doesn't make
> a lot of sense.  It will never be applied to the 5.1 branch because we
> have a strict policy of not making stable branch file format changes.
> It's generally a good idea to ask on developers mailing list before
> embarking on changes that may not be accepted.
>
"
1820386,2019-06-25 17:46:46 UTC,"On 25/06/19 17:35, Seth Hillbrand wrote:

> Hi Dino-
>
> Thank you for your patch.  There are a few coding style issues that it
> would be good to address.  You can run a style check using the built-in
> tools/check_coding.sh script.
>
> I'm attaching an image of what these look like for others to comment on.
> Generally, they look good to me.  We may want to differentiate the
> global outlines somehow.  Maybe chamfer the top/bottom edges?
>
> The only show-stopper I see here is that double-clicking on one of the
> new labels segfaults.
>
> ** Attachment added: ""NewLabelTypes.png""
>     https://bugs.launchpad.net/kicad/+bug/1820386/+attachment/5273161/+files/NewLabelTypes.png
>


Hi Seth,
I was thinking about removing the option for the global labels, since
for that use there are power ports available, but it can be done if it
makes sense (probably when the new file format for V6 will be
implemented), as Waine states."
1820386,2019-06-25 15:51:42 UTC,"@Dino, thank you for the patch but given that the new schematic file format is going to be implemented soon, applying this patch doesn't make a lot of sense.  It will never be applied to the 5.1 branch because we have a strict policy of not making stable branch file format changes.  It's generally a good idea to ask on developers mailing list before embarking on changes that may not be accepted."
1820386,2019-06-25 15:35:20 UTC,Hi Dino-
1820386,2019-04-04 20:06:32 UTC,"Agree if my ""surnamesake"" @Dino. The solution should fix both.
I report lp:1728250 because the same behavior, I used several time a module that had a isolated power supply. Using labels or just ignore the DRC at PCB seems like workarounds."
1820386,2019-06-25 21:08:12 UTC,...oops answered the wrong message in the last comment... It should start with:
1820386,2019-03-18 12:39:33 UTC,"Ah.  OK, I guess that makes sense.  I think this will be addressed by the fix for lp:1728250 rather than the other way around but I'll leave them separate in case someone sees a better way forward on this one.  Meaning a clear, easy to disambiguate graphical pin shape for power connections."
1820386,2019-03-18 07:08:43 UTC,"I would guess they ask for more ""pin types"" for the hierarchical labels. Right now these have input, output, bidirectional, tri-state and passive. They ask for one (or two) more type(s) representing power supply pins with a distinct shape from the 5 we now have."
1820386,2019-03-17 23:00:17 UTC,"@Rene, that is correct.  Presumably, they would want something that is visually distinct from the global GND symbol no matter what.  Otherwise, this would similarly be confusing."
1820386,2019-03-17 22:25:14 UTC,Seth that workaround would not create a label at all. Meaning it is just graphics and the user will need to still place the hierarchical pin. Furthermore i fear this will reduce the power of ERC as it might result in either false positives or missed errors depending on the exact combinations of all used pin types.
1820386,2019-03-16 14:24:58 UTC,Can you not just make your own GND symbol that is not global?  Edit the existing GND pin and make your own that doesn't have an invisible power input pin.  Then the isolated sheets won't connect to each other.
1820386,2019-03-19 10:33:30 UTC,"Exactly, the wish is just for ""power"" and ""gnd"" hierarchical labels (or some equivalent method), so that the power connection to a child sheet can be explicit, and easy to be visually checked on a schematic where insulation from one sub-sheet to another using the same file is needed.
Also, yes, the fix for lp:1728250 can solve this problem too, but in that case bringing the local power port outside the child sheet means to add an ""input"" or ""output"" hierarchical label to the external sheet to connect for instance to the external isolated power source. Here a label that is not graphically as the ""input"" but a ""power input"" could make sense too."
1820387,2019-03-22 19:06:35 UTC,I can confirm that this would be a very useful feature.
1820387,2020-05-11 08:27:45 UTC,Still needed. Installing Y PPA Manager every-time consumes more time than using Launchpad.
1820387,2020-07-29 06:45:27 UTC,Still needed.
1820391,2019-05-27 04:17:32 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1820391,2019-03-27 13:03:56 UTC,"If you can manage to duplicate this bug, please list the exact steps.  I cannot duplicate this."
1820391,2019-03-27 17:03:27 UTC,"I can't duplicate.
It was the first I sow after installing KiCad 5.1 (the first application I run was Footprint editor).
After changing the project to new one the bug disapeared and I could't get it back.
I supposed it is just after installing KiCad 5.1 on clear computer, but when I have done it next time I didn't got it.
I was installing second time at the same computer and in my opinion in the same situation and from the same file (before first installation I sow at KiCad forum someone writeing checksums for it so I have compared the checksum before first installation).
In my opinion it is connected with the window with few errors I sow first time opening Footprint editor, but after second installation (after uninstallation) I didn't got that window.
I had no time to try it once more. Since a month I am not working with KiCad. Only because I sow 5.1 released I have installed it, had a short look at it and get back to my other works."
1820395,2019-03-18 11:27:19 UTC,"Thank you for your bug report, from the log
ubiquity: E: You don't have enough free space in /var/cache/apt/archives/."
1820395,2019-05-18 04:17:23 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1820397,2019-03-16 15:30:07 UTC,This change was made by a bot.
1820409,2019-03-22 14:43:39 UTC,"I would'nt say it happens, i'd say its always there constantly."
1820409,2019-04-01 09:32:06 UTC,"5.1.0-050100rc2-generic, works great, does not have that issue."
1820409,2019-04-02 20:17:14 UTC,"Hm, that was a bit early. Now it has ""happened"" ONCE with the 5.1.0-050100rc2-generic kernel.
I think the battery of the laptop was pretty low at the time.
Youtube audio went totally out of sync with video."
1820409,2019-03-22 07:17:12 UTC,Please attach dmesg when this issue happens.
1820409,2019-04-01 07:33:14 UTC,Does latest mainline kernel [0] have the issue?
1820409,2019-03-18 08:21:43 UTC,Would it be possible to find the last kernel version that doesn't have this issue?
1820409,2019-03-16 19:44:57 UTC,"I mean the audio part of the video stutters in VLC.
(It's made with android phone and downloaded back from youtube.
Codec: H264 - MPEG-4 AVC (part 10) (avc1))"
1820409,2019-03-16 16:30:10 UTC,This change was made by a bot.
1820409,2019-03-21 19:44:42 UTC,"Yes, tried a few back now. 4.15.0-43-generic is the last good one."
1820425,2020-05-01 14:52:41 UTC,This was resolved by change I535640779da645e43ba6586308b07bf25dba7d89
1820427,2019-03-18 13:32:42 UTC,I can't reproduce this issue. Are you able to confirm that an old build downloaded from http://beta.airdcpp.net/updater/?C=M;O=D behaves differently? And what's your current version?
1820427,2019-03-19 14:49:36 UTC,This issue is currently blocking the release of version 3.54
1820427,2020-03-18 04:17:29 UTC,[Expired for AirDC++ because there has been no activity for 60 days.]
1820432,2019-05-01 21:48:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820432,2019-06-25 23:00:19 UTC,Unfortunately this won't be fixed as GNOME-Shell no longer supports the option to hide it.  The toggle still needs to be removed from Tweaks.
1820439,2019-05-18 04:17:21 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1820439,2019-03-18 11:14:29 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.
1820439,2019-03-17 00:13:55 UTC,"StacktraceTop:
 slab_allocator_free_chunk (chunk_size=<optimized out>, mem=0x55faaa8f4f80) at ../../../glib/gslice.c:1365
 magazine_cache_trim (allocator=0x7f1c2ad9dd40 <allocator>, stamp=<optimized out>, ix=22010) at ../../../glib/gslice.c:678
 magazine_cache_push_magazine (ix=ix@entry=0, magazine_chunks=<optimized out>, count=51) at ../../../glib/gslice.c:709
 thread_memory_magazine2_unload (tmem=0x55faa99343e0, ix=0) at ../../../glib/gslice.c:1198
 g_slice_free_chain_with_offset (mem_size=16, mem_chain=<optimized out>, next_offset=8) at ../../../glib/gslice.c:1198"
1820443,2019-03-17 02:16:29 UTC,系统预测的最大内存
1820443,2019-03-17 02:17:23 UTC,实际创建的内存为10G
1820447,2019-03-17 02:45:22 UTC,"There is also a duplication of concerns with the juju/names package. It would be good to consolidate where verification happens, probably upstream into that package."
1820465,2019-04-09 14:04:49 UTC,This bug was fixed in the package peony - 1.1.5.1-0ubuntu1
1820466,2019-03-17 03:39:39 UTC,PS:黑色主题~
1820466,2019-07-11 08:40:30 UTC,"1、由于19.04用的是新的联网程序，已和黄晟确认可能是因为程序只调用了16x16的图标。未动态调用32和64尺寸的图标。
2、企鹅图标调用的是其他社区的主题里的图标，并有16和32尺寸，没有64尺寸的图标。"
1820471,2019-08-01 02:17:24 UTC,优客助手的desktop名字与包名不同，已经进行处理可进行启动了，优客天气不提供启动项启动，另外不能直接启动的软件已处理为不会显示启动按钮。
1820477,2019-08-01 02:20:48 UTC,搜狗输入法已跟吴孝夷确认，desktop运行启动不会有界面效果，是正常现象。
1820487,2019-06-23 04:19:22 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1820487,2019-04-23 23:53:59 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1820487,2019-04-24 00:08:06 UTC,"Thanks! Yeah, I downloaded the ISO again and the error went away. Seems it
was corrupted."
1820490,2019-03-18 03:30:51 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1820490,2019-05-17 04:17:27 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1820491,2019-03-17 06:34:51 UTC,Additional Info: when I do a
1820493,2019-05-31 12:13:24 UTC,Seems sensible (this bug has a low heat anyway). Please reopen if there is still an unsolved issue.
1820493,2019-05-30 17:22:32 UTC,"Now that pcbnew supports hatched zone filling, would the status of the bug report be ""Fix Committed""?  I don't know what else there is to fix."
1820493,2019-03-20 15:11:56 UTC,"@Wayne,"
1820493,2019-03-19 17:51:50 UTC,"@JP, the last I heard you were looking at some performance issues.  If it's ready to go, please post the patch on mailing list so we can review and test it.  I would like to test it again.  It's been a while since you posted the original patch and I need to refresh my memory."
1820493,2019-03-19 17:30:33 UTC,"@kosthala @jpcharras Jean-Pierre wrote a patch last year that enables hatched filled zones. Search for the subject ""[RFC] Experimental grid pattern in zone fill"" on the developer mailing list. Since we're in the V6 development cycle now, this might get merged sooner or later."
1820493,2019-03-19 17:42:50 UTC,I am waiting for the green light from Wayne to commit the hatched filled zones.
1820493,2019-03-19 16:52:49 UTC,"I don't consider this a bug, it's just the complexity of the geometry of a DXF imported as a footprint that makes the router behave slowly."
1820493,2019-03-18 12:18:29 UTC,"Until we address this issue, the easiest workaround would be to change the DXF hatch to avoid the rounded corners."
1820493,2019-03-17 21:18:05 UTC,"I made a few tests and i realized what is the problem.
In my board i have import two dxf hatches and it seems that is the problem.
I have attached a demo board in order to recreate the track delay."
1820493,2019-03-17 19:26:26 UTC,Send us the board please :)
1820493,2019-03-19 17:14:17 UTC,I think that Kicad does not support hatching zones yet...only solid filled zones.
1820495,2019-03-17 12:40:29 UTC,"This menu is created on the fly and is filled with entries from the .executor files. These files can be install by Hugin system-wide and also from user-defined .executor files in the corresponding user directory.
So these entries can't be translated via the conventional way (via .pot/.po files). So this feature would require to add the translations to the .executor and .assistant files."
1820495,2019-03-22 17:09:19 UTC,Implemented in default branch.
1820496,2019-03-17 12:33:47 UTC,The same fix for sweethome3d-textures-editor and a ref to this ticket.
1820496,2019-03-18 09:52:53 UTC,"yes, in the long term that should be fixed in these packages itself"
1820496,2019-03-18 09:01:38 UTC,I also confirm that this kind of fix in icedtea-netx fixes the issue:
1820496,2019-03-17 12:32:01 UTC,The same fix for sweethome3d-furniture-editor
1820496,2019-03-17 10:53:06 UTC,It seems that netx.jar is no longer produced and /usr/share/icedtea-web/javaws.jar can be used instead. So here is a patch to replace netx.jar by javaws.jar.
1820496,2019-03-17 12:24:36 UTC,"The same patch, with a ref to this ticket."
1820496,2019-03-17 09:10:17 UTC,Just added Matthias in cc as he did the update and might know what's wrong :)
1820496,2019-03-17 12:28:21 UTC,The same fix for sweethome3d-textures-editor
1820499,2019-03-17 10:41:24 UTC,Testing tar archive.
1820499,2019-03-17 10:42:07 UTC,tar output on NFS4 filesystem (failing utime)
1820499,2019-03-17 10:43:21 UTC,Verbose strace of tar -zxf test.tar.gz on NFS4 (failing ftime syscall)
1820499,2019-03-17 10:43:55 UTC,Verbose strace of tar -zxf test.tar.gz on NFS3 (working ftime syscall)
1820499,2019-03-17 10:54:17 UTC,s/ftime/fstat/g sorry
1820500,2019-03-17 10:55:56 UTC,"StacktraceTop:
 js::PrimitiveTypeFlag (type=JSVAL_TYPE_PRIVATE_GCTHING) at ./js/src/vm/TypeInference-inl.h:220
 js::TypeSet::hasType (type=..., this=0x55d4ddd63e10) at ./js/src/vm/TypeInference-inl.h:958
 js::TypeScript::Monitor (cx=cx@entry=0x55d4d9fa41f0, script=0x7fe34b77a670, pc=pc@entry=0x55d4dab4598c ""5\n"", types=types@entry=0x55d4ddd63e10, rval=...) at ./js/src/vm/TypeInference-inl.h:606
 js::jit::DoTypeMonitorFallback (cx=0x55d4d9fa41f0, frame=0x7fff3d679758, stub=0x55d4dd4d5f20, value=..., res=...) at ./js/src/jit/SharedIC.cpp:2434
 ?? ()"
1820500,2019-03-18 03:35:35 UTC,Looks similar to bug 1820556.
1820500,2020-01-24 09:38:11 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1820501,2019-03-18 08:20:32 UTC,Does this happen to previous kernel versions?
1820501,2019-03-18 13:21:24 UTC,"Haven't tried, but it was working fine. I left my computer running out of battery and then when i turned it on the touchpad disappeared."
1820501,2019-03-17 12:00:07 UTC,This change was made by a bot.
1820508,2019-12-02 15:06:11 UTC,"As a first step I'll add all AutoDJ tooltip strings to dlgautodj.cpp and add the keyboard shortcuts there. Much like this:
https://github.com/mixxxdj/mixxx/blob/master/src/library/autodj/dlgautodj.cpp#L107"
1820508,2019-12-09 16:37:39 UTC,https://github.com/mixxxdj/mixxx/pull/2379
1820508,2019-03-18 00:42:03 UTC,"Ah, I ignored that legacyskinparser.cpp because I assumed that it was only for older pre-2.0 skins. Perhaps it should be renamed?"
1820508,2019-03-17 17:31:45 UTC,"In the skin area, the short cuts are automatically added here:
https://github.com/mixxxdj/mixxx/blob/8aeda6ff17ba7c135d6a373b3ffa6077c42f5b37/src/skin/legacyskinparser.cpp#L2192"
1820508,2019-03-18 07:32:48 UTC,It has already this name in Mixxx 1.11. I guess since the first attempt to switch to qml which is still on the wishlist.
1820509,2019-03-18 11:45:14 UTC,"Thank you for your bug report. That eems indeed worth fixing, it's a bit difficult to know how sensitive the problem is without details though. Could you provide a bit more context on the bug, maybe a way to trigger it?"
1820509,2019-03-18 15:10:33 UTC,Unfortunately I just stumbled over this commit by accident since I checked the commit log of libX11. So for a reproduction we would need to contact the original reporter Sami Farin (https://bugs.freedesktop.org/show_bug.cgi?id=93186) but I do not find any valid email address from him.
1820509,2019-10-03 19:10:52 UTC,Any news on this?
1820509,2019-10-03 20:47:37 UTC,this is fixed in 1.6.8-1 in eoan
1820510,2019-03-18 11:00:38 UTC,"There is a merge request on https://code.launchpad.net/~ricotz/libunity/syntax-fixes/+merge/362923 but it fails to build now with a dee
https://launchpadlibrarian.net/415297335/buildlog_ubuntu-disco-amd64.libunity_7.1.4+19.04.20190315.5-0ubuntu1_BUILDING.txt.gz"
1820510,2019-03-17 16:22:26 UTC,"The attachment ""0001-Fix-build-errors-but-not-warnings-with-vala-044.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1820510,2019-03-17 12:47:34 UTC,"Wrong package, apologies."
1820510,2019-03-17 13:27:03 UTC,Attached patch fixes build errors with valac 0.44
1820512,2019-03-18 08:44:30 UTC,Same issue on current stable 0.7.18
1820512,2019-08-03 02:01:59 UTC,"Had the same problem
pip install 'httplib2==0.10.3'
Resolved it.
Found this post that says it's a problem with httplib2.
https://github.com/httplib2/httplib2/issues/47"
1820513,2019-03-18 20:48:05 UTC,Does this answer your questions?
1820513,2019-03-20 15:41:56 UTC,Bug #1820389 has been fixed. It would be great if we could get some feedback on the android tools now. We would highly appreciate feedback on:
1820513,2019-03-18 21:20:23 UTC,"On 18.03.19 21:16, Andreas Schildbach wrote:

> So yes, the Android builds work with OpenJDK 8, Gradle 3.4.1 under
> Ubuntu 18.04 LTS. On OpenJDK 11, Gradle 4.4.1 under Ubuntu 18.04 LTS-
> proposed the described issues appear. All issues I reported are
> perfectly reproducable.
"
1820513,2019-03-20 18:59:53 UTC,Feedback on #2 is contained in https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389. As far as I can tell the blocker regressions are gone. However there is still the issue of the missing alternative dependency declaration: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1797761
1820513,2019-03-18 21:17:49 UTC,"On 18.03.19 21:38, Andreas Schildbach wrote:

> Actually I don't find an openjdk-10-jdk[-headless] package in Bionic, so
> I'm not sure if I ever tested OpenJDK 10. Probably not.
"
1820513,2019-03-18 20:47:10 UTC,"For completeness, I just tested the combination Gradle 3.4.1 and OpenJDK 11, all from current Bionic (updated):"
1820513,2019-03-18 19:33:21 UTC,One more thing: Please write down your test case here.
1820513,2019-03-18 20:16:04 UTC,"First, a clarification: I'm not yet using the android* packages for building my Android apps. I would very much like to, but they seemed incomplete and outdated whenever I checked."
1820513,2019-03-18 19:37:21 UTC,"Hi Andres,"
1820513,2019-03-18 19:32:31 UTC,"Andreas, two questions:"
1820513,2019-03-17 17:18:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820513,2019-03-18 20:38:44 UTC,"Actually I don't find an openjdk-10-jdk[-headless] package in Bionic, so I'm not sure if I ever tested OpenJDK 10. Probably not."
1820514,2019-04-03 13:40:36 UTC,"Created attachment 9055467
Bug 1536530, let save-page-as work even if there are invalid urls, r=gijs"
1820514,2019-04-03 09:18:24 UTC,"https://searchfox.org/mozilla-central/rev/44a212460990ffffecf50a8e972d3cbde2e7216b/dom/webbrowserpersist/moz.build#7-9 may help in figuring out how this happened. That said, I don't know of anyone actively working on embedding who would own this, and if anything that seems like a poorer fit in terms of what the code is doing..."
1820514,2019-04-03 12:57:26 UTC,"Kiitos Jani bugiraportista.
Tutkailen ja korjailen."
1820514,2019-04-03 13:22:48 UTC,Looks like PersistNodeFixup::FixupAnchor already just skips broken urls.
1820514,2019-04-03 14:55:23 UTC,"Pushed by <email address hidden>:
https://hg.mozilla.org/integration/autoland/rev/d2522fbc3ab9
let save-page-as work even if there are invalid urls, r=Gijs"
1820514,2019-04-02 20:10:23 UTC,"Gijs, thank you for diagnosing this!"
1820514,2019-04-05 01:32:57 UTC,"Sorry for being late here. I was off the last two days. Thanks Gijs, Boris and Olli."
1820514,2019-04-05 12:53:23 UTC,"Olli, do you think that this would be a valuable and safe uplift to beta or should we just let it ride the trains to 68? Thanks"
1820514,2019-04-05 14:54:28 UTC,"Given that we've had this bug at least from FF42 (bug 1101100), it is a bit hard to argue strongly why this should be taken to beta.
But, should be relatively safe."
1820514,2019-04-05 15:35:13 UTC,(In reply to Olli Pettay [:smaug] from comment #17)
1820514,2019-04-05 16:13:28 UTC,"I didn't say bug 1101100 regressed this. The code has been there at least from that bug, perhaps longer."
1820514,2019-04-04 04:47:06 UTC,https://hg.mozilla.org/mozilla-central/rev/d2522fbc3ab9
1820514,2019-04-03 02:31:44 UTC,Probably because it's doing a DOM walk and should generally be kept up to date with DOM changes...
1820514,2019-03-25 20:45:08 UTC,"Paul_B, can you do a quick check to see if this is a regression?"
1820514,2019-03-27 15:09:18 UTC,"Saving only the HTML works, ""web page, complete"" doesn't."
1820514,2019-03-25 20:58:08 UTC,"I tried running mozregression tool but I could not reach a regression range.
The generated builds for bisection revealed the same issue in 09/2016 / not working build on 06/2015 and a different issue on the last build 11/2014 when the page is saved but with 0 bytes."
1820514,2019-04-02 22:53:36 UTC,"huh, how did webbrowserpersist end up to DOM."
1820514,2019-03-25 17:05:14 UTC,"Hi reporter,"
1820514,2019-03-19 17:54:39 UTC,"Yep, retrying does work."
1820514,2019-03-19 17:53:06 UTC,(My) original report on Launchpad: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820514
1820514,2019-03-19 17:50:40 UTC,"User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"
1820514,2019-03-19 16:55:45 UTC,"This might be related to https://bugzilla.mozilla.org/show_bug.cgi?id=964213, although that bug is old and without recent activity."
1820514,2019-03-18 18:04:53 UTC,"Tested all combinations of both (Ctrl-s/context menu in safe mode and normal mode), all with the same results. Could this be locale-dependent? The UI is in English in safe mode though, so I'm guessing safe mode should be locale-independent, as I'm on fi_FI.UTF-8 otherwise."
1820514,2019-03-18 14:41:34 UTC,"Also, can you try running firefox in safe mode and see if that makes a difference?"
1820514,2019-03-18 14:40:58 UTC,"I can successfully save the page you linked to in the description.
That's on disco, fully up-to-date, on real hardware."
1820515,2021-02-23 02:27:43 UTC,"Hello,
4.18 kernel is not supported anymore, thus I am closing it here.
Please feel free to open a new bug if you're seeing any issue.
Thanks"
1820516,2019-03-18 14:12:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820516,2020-01-21 09:00:43 UTC,4.18 EOL. Please feel free to open a new bug with a newer kernel if you're still experiencing this issue.
1820523,2019-03-18 11:14:41 UTC,I opened Ubuntu 19.04 in a VM and selected The Try Ubuntu option. The bug is still present. This is the bug in gitlab gnome: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1079
1820523,2020-01-24 09:49:33 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1820523,2019-03-18 03:39:27 UTC,Please try live booting Ubuntu 19.04 and tell us if it has the same bug:
1820525,2019-03-17 22:56:02 UTC,"As discussed on IRC:
A package being dropped as unsupportable isn't really a functional bug (which you'd file a bug report on). According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917831 'pdfshuffler' is going to be replaced by an actively maintained fork, 'pdfarranger', in Debian. This also applies to Ubuntu 'disco' (will be 19.04), where 'pdfshuffler' is now a transitional package depending on newly introduced 'pdfarranger' package (which depends on current / supportable python libraries)."
1820527,2019-06-08 01:42:32 UTC,"Hi Steve, is this still a problem for you or has this been resolved with use of the latest build?"
1820527,2019-06-08 01:52:00 UTC,"Hi,"
1820527,2019-06-08 14:55:39 UTC,"Steve, thanks for your response. Using the latest build, I was not able to reproduce your reported bug. If you are able, please share any other specific information you may have associated with this issue."
1820527,2019-08-08 04:17:32 UTC,[Expired for debian-installer (Ubuntu) because there has been no activity for 60 days.]
1820529,2020-05-14 08:52:40 UTC,"I guess it depends, sometimes it paractical to be able to work on the same net. What we could do would be to give a warning or if you open the net twitch, overwrite the save file (so you don by accident overwrite the file)"
1820529,2020-05-16 08:08:12 UTC,A warning dialog saying that this behavior will happen is maybe a good idea.
1820530,2019-03-17 19:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820530,2019-05-17 04:17:17 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1820530,2019-07-26 20:49:54 UTC,Applied these updates to the kernel for eoan.
1820530,2019-08-09 11:38:28 UTC,This bug was fixed in the package linux - 5.2.0-10.11
1820540,2019-03-18 12:15:26 UTC,(I'm not a KiCad developer.)
1820540,2019-03-18 12:35:11 UTC,We should be able to adjust the bounding box to only account for the footprint and not the value field
1820540,2019-09-05 20:38:00 UTC,"Fixed in revision 3bd38ec2453aeaa9581f9ecbf83616001be8d25e
https://git.launchpad.net/kicad/patch/?id=3bd38ec2453aeaa9581f9ecbf83616001be8d25e"
1820544,2020-04-20 18:47:37 UTC,What is the status? Can we get a setting to change the behavior?
1820544,2019-03-21 04:54:33 UTC,"I've investigated a bit more, and if I interpret it correctly, it seems that the new vte way of doing it is not only more correct, but also allows access to more colours. It took me a few days to reconfigure dircolors/LS_COLORS, mutt, my prompt, etc., but I'm in agreement that this change is for the better."
1820544,2019-03-18 09:50:32 UTC,Fair point!
1820544,2019-03-18 09:27:43 UTC,"Ah okay, thanks for that information. I only really noticed the change in `ls --color=auto`, where the default colours were now quite difficult to tell apart. I suppose it must be possible to revert them, but a config in terminator would be even better!"
1820544,2019-03-18 09:09:59 UTC,"See also:
- bug 1740311
- https://bugzilla.gnome.org/show_bug.cgi?id=762247
- https://bugzilla.redhat.com/show_bug.cgi?id=1687141"
1820544,2019-03-18 09:37:22 UTC,What would be even better is for default ls colors to really ask for bright whenever it indeed wants bright. :)
1820547,2019-03-18 16:09:28 UTC,Did you try using ppa-purge as instructed?
1820547,2019-05-18 04:17:28 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1820547,2020-10-30 04:39:19 UTC,"As before you upgrade Ubuntu ,you have to remove unnecessary and corrupted packages . I have resolved issue by following commands:"
1820556,2019-03-18 03:35:23 UTC,Looks similar to bug 1820500.
1820556,2020-08-11 10:07:20 UTC,No crashes since 3.35 so consider it fixed.
1820557,2019-03-18 03:38:20 UTC,~# lshw -class network -businfo
1820557,2019-03-18 16:28:52 UTC,"While the linux-azure package has the necessary modules for running a virtual machine under Hyper-V, especially in Azure, it does not include every possible driver for PCIe. The other drivers should be available by installing the ""linux-modules-extra-azure"" metapackage. I have not checked on this particular driver."
1820557,2019-08-01 06:52:47 UTC,"Mark as ""Incomplete"" for question in comment #2."
1820557,2019-10-01 04:17:20 UTC,[Expired for linux-azure (Ubuntu) because there has been no activity for 60 days.]
1820561,2019-03-18 11:34:13 UTC,"Thank you for your bug report. That's still the current behaviour in disco. The color picker is made model for the writer view and gnome-shell does enforce the position and grey the background in those cases. Unsure if the dialog needs to be modal though, that's a libreoffice design decision"
1820561,2019-03-18 22:49:34 UTC,"To disable this behavior, open GNOME Tweaks, navigate to the “Windows” section and disable “Attach modal dialogs”."
1820561,2019-03-19 16:36:45 UTC,Related upstream bug: https://bugs.documentfoundation.org/show_bug.cgi?id=113913.
1820565,2019-03-18 13:30:34 UTC,"Although it might get tricky because shutdown_retry_interval is not the amount of time to sleep between checks, it's the amount of time in between trying to shutdown the guest."
1820565,2019-03-18 13:29:02 UTC,Yup code is here:
1820569,2019-03-18 07:56:45 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1820569,2019-05-18 04:17:17 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1820573,2019-04-20 17:56:51 UTC,"before going that further, what have you in mind with (please develop further and give example):
- personalised rules and reports ?
- fringe feature requests interfering with core development ?"
1820573,2019-06-20 04:19:26 UTC,[Expired for HomeBank because there has been no activity for 60 days.]
1820575,2019-03-18 10:40:49 UTC,"Hello, did you try to shutdown and save again?
from 5.x to 6.x the saved store format has changed, this is an incompatible change that is making the restore fail on some cases (it has been fixed in 6.0.4, but maybe there are a few more cases)"
1820575,2019-03-18 11:05:38 UTC,"That works (forgetting the current state of the snapshot, effectively rebooting the VM).
However after taking a new, updated snapshot and shutting down the VM, trying to restore it exhibits the same issue again."
1820575,2019-03-20 11:00:06 UTC,"@osomon, can you please check if you suffer from this issue?
https://www.virtualbox.org/ticket/18263"
1820575,2019-03-20 16:43:08 UTC,"That looks more like https://www.virtualbox.org/ticket/18331.
Attaching my log file."
1820575,2019-04-02 07:34:28 UTC,"This appears to be fixed, somehow, despite the fact that virtualbox hasn't been updated since I reported the issue."
1820575,2019-04-02 08:05:00 UTC,"Sigh, it's just done it again on my bionic i386 VM."
1820575,2019-10-23 22:55:15 UTC,still an issue with newer vbox version?
1820575,2019-10-24 07:06:34 UTC,"I haven't seen this issue for a while now (I'd say at least 3 months). I've been running eoan on my laptop since early in the development cycle, and I have used and regularly upgraded several i386 VMs without problems."
1820576,2020-04-21 08:13:56 UTC,"Hello,"
1820576,2019-03-29 10:20:49 UTC,Lowering to medium as this is a rare race condition when an ephemeral port matches the value reserved for keystone admin endpoint
1820576,2020-05-27 10:53:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/731157"
1820576,2019-03-29 10:19:01 UTC,"Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/644545"
1820576,2020-06-02 13:35:41 UTC,"Reviewed:  https://review.opendev.org/644545
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ffd31df7d3b6eb415bae76291b4adaaab4da8dd0
Submitter: Zuul
Branch:    master"
1820576,2020-06-03 10:10:46 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/733087"
1820576,2020-06-03 10:10:58 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/733088"
1820576,2020-06-01 16:04:23 UTC,"Change abandoned by Bogdan Dobrelya (bogdando) (<email address hidden>) on branch: master
Review: https://review.opendev.org/731157
Reason: back to https://review.opendev.org/#/c/644545"
1820576,2019-03-20 09:29:16 UTC,Addressed by: https://review.openstack.org/644545
1820576,2020-06-04 13:02:13 UTC,"Reviewed:  https://review.opendev.org/733087
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b225e6b48fe0f2409f0827c01d3c3c48cc40a133
Submitter: Zuul
Branch:    stable/ussuri"
1820576,2019-03-19 10:54:32 UTC,"Reminded with https://bugs.launchpad.net/tripleo/+bug/1623818/comments/2
how come we have lost those reserved_ports in tripleo?"
1820576,2019-03-19 10:45:58 UTC,"We have net.ipv4.ip_local_port_range = 32768	60999
we should exclude 35357 from the ephemeral ports"
1820576,2019-03-19 07:43:39 UTC,same for non periodic at http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-scenario002-standalone (last 3 runs green one failed on 19th) http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-scenario002-standalone
1820576,2019-03-19 07:41:37 UTC,looks like this failed exactly once with the error in description on 18th - otherwise green today (last 3 runs)
1820576,2019-03-18 11:32:43 UTC,It's for periodic job in master. Leaving it just to keep an eye for a few days to see it doesn't happen again.
1820576,2019-03-18 11:21:58 UTC,ah but for comment #2 it looks like the link in description is from the 18th and the green runs are latest from 17th right now
1820576,2019-03-18 11:20:32 UTC,lots of green runs in https://review.rdoproject.org/zuul/builds?job_name=periodic-tripleo-ci-centos-7-scenario002-standalone-master
1820576,2019-03-18 11:03:34 UTC,"It didn't happen in next run, seems like a casual error."
1820576,2019-03-19 11:11:46 UTC,"RabbitMQ - 41055 (we changed it to 25672 for tripleo),61613 (STOMP, not used in tripleo?)
Keystone - 35357 - let's add this to reservations
Qpidd - 49000 - 49001 - let's add this to reservations
libvirt 49152 - 49261- let's add this to reservations
ovs capwap 58881 - 58882 (is legacy and prolly not needed any more)"
1820576,2020-06-04 16:33:40 UTC,"Reviewed:  https://review.opendev.org/733088
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3d16a7009dccbcecd96a2d22a16f37b840c9294a
Submitter: Zuul
Branch:    stable/train"
1820576,2021-02-08 13:46:28 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.4.0 release.
1820579,2019-04-24 15:55:45 UTC,Tested deploying in MAAS 2.5 to see if this was a change with MAAS and there are no cloud-init messages to the console.  Seems that cloud-init has made a change.  Linking cloud-init to the bug for further investigation.
1820579,2019-06-30 04:17:36 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1820579,2019-04-30 13:29:30 UTC,"That cannot be set globally because machines in his environment are all
different and that can break the deployment."
1820579,2019-04-30 13:10:26 UTC,"I also have confirmed that console messages appear with MAAS 2.6 with Bionic ephemeral, deploying Bionic. This is with the global kernel parameters being empty."
1820579,2019-04-30 00:58:06 UTC,"Actually, I take part of that back, I was also not able to get it to work properly using console=tty0 console=ttyS1."
1820579,2019-06-30 04:17:35 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1820579,2019-04-25 13:23:08 UTC,@newell-jensen have you tried without the console= parameters in the global kernel parameters setting? do you get the same result with them removed?
1820579,2019-04-24 23:17:01 UTC,I am seeing the same behaviour in xenial and bionic.  I see cloud-init messages in /var/log/syslog of the deployed node and also in the virsh console log file but still not sure why nothing is being output to the console.  Still investigating.
1820579,2019-04-24 16:33:34 UTC,"We've no changes to cloud-init related to logs; we write to /var/log/cloud-init.log and ""console"" which is setup by boot parameters, typically /proc/cmdline would have console=ttySX,115200 console=tty0; where you'd see messages going to both serial as well tty0."
1820579,2019-04-29 23:04:16 UTC,"Blake,"
1820583,2019-03-18 11:49:51 UTC,apport information
1820583,2019-03-18 11:55:40 UTC,"Further information I have the neo keyboard layout installed.
And it even happend with the NEO keyboard layout even so, this layout doesn't have a caps lock functionality."
1820583,2019-03-18 11:49:56 UTC,apport information
1820583,2019-03-18 11:49:54 UTC,apport information
1820583,2019-03-18 11:49:53 UTC,apport information
1820583,2019-03-18 11:49:53 UTC,apport information
1820583,2019-03-18 11:49:52 UTC,apport information
1820583,2019-03-18 11:49:50 UTC,apport information
1820583,2019-03-18 11:49:47 UTC,apport information
1820583,2019-03-18 11:49:48 UTC,apport information
1820583,2019-03-18 11:49:46 UTC,apport information
1820583,2019-03-18 11:49:45 UTC,apport information
1820583,2019-03-18 11:49:44 UTC,apport information
1820583,2019-03-18 11:49:42 UTC,apport information
1820583,2019-03-18 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820583,2019-03-18 11:49:49 UTC,apport information
1820588,2019-05-03 22:35:59 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657079"
1820588,2019-05-23 07:09:46 UTC,"Reviewed:  https://review.opendev.org/657581
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a2b1ef5f11f38a3359613babff86ec861bff4373
Submitter: Zuul
Branch:    stable/stein"
1820588,2019-05-07 11:50:40 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/657581"
1820588,2019-05-07 11:27:49 UTC,"Reviewed:  https://review.opendev.org/657079
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e9d572ddfad10da18603c55da1aad2e70da15381
Submitter: Zuul
Branch:    master"
1820588,2019-03-20 17:16:58 UTC,"Reviewed:  https://review.openstack.org/644694
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=70989c3eb508ac4633a921a3760e02a4b74a9784
Submitter: Zuul
Branch:    master"
1820588,2019-03-19 22:53:45 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/644694"
1820588,2019-03-19 20:16:38 UTC,Thanks gibi. I'll remove the stein-rc-potential tag accordingly. I wonder if we should add the information about the workaround to the release notes Known Issues.
1820588,2019-03-19 13:18:45 UTC,"Btw, added a PTG cross project topic regarding this bug to https://etherpad.openstack.org/p/nova-ptg-train"
1820588,2019-03-19 10:01:52 UTC,"@Melanie: I don't think this is an RC blocker problem:
1) There is a clear workaround, detach the port via the nova API then delete the neutron port.
2) I only heard about one use case when the above direct delete might be used instead of the two step detach + delete. A nova server stuck in a wrong state where port detach cannot be used to free up the SRIOV VF and the admin needs that VF so she goes and deletes the port in neutron using that VF. However I don't think that in this case we need to expect that everything is cleaned up properly. When such stuck Server is finally deleted nova will clean up the resource allocation."
1820588,2019-03-18 11:52:43 UTC,Another possible workaround is to detach the port via nova API and then delete the port in neutron.
1820591,2019-08-23 20:58:25 UTC,"Reviewed:  https://review.opendev.org/672948
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=288634ce0bf042bed614b3f764753d7b65a7170f
Submitter: Zuul
Branch:    master"
1820591,2019-09-24 17:07:06 UTC,Will this be backported to stable/stein ?
1820591,2019-09-24 20:08:18 UTC,"The upstream patch required to heat is here https://review.opendev.org/#/c/678162/, as yet unmerged. I will try again to get clarification on if this patch is allowed to be merged. We can't back-port the endpoint fix in OSA until the underlying bug in Heat is fixed."
1820591,2019-10-16 10:24:50 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/688895"
1820591,2019-10-16 22:01:31 UTC,"Reviewed:  https://review.opendev.org/688895
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=eccb5c13fec9d9efcccb821dbcf0f344cd515eec
Submitter: Zuul
Branch:    stable/stein"
1820591,2020-02-03 20:58:55 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705555"
1820591,2020-02-03 21:30:47 UTC,"Change abandoned by Shannon Mitchell (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/705555
Reason: Submitting a separate bug just for the public/private url fix."
1820593,2019-03-18 11:56:30 UTC,"Sorry for not directly addressing your question, but perhaps for a while it would be better to avoid 8-2018q4-major, I had to patch it heavily to make it work:"
1820593,2020-02-26 11:40:27 UTC,"Hi Jussi,"
1820597,2019-03-18 23:55:05 UTC,*** This is an automated message ***
1820600,2019-05-31 19:06:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820602,2019-03-18 20:52:17 UTC,"Hi,"
1820602,2019-03-19 18:31:43 UTC,Yes I have this line in the UFO file.I need help regarding this issue. Can you please refer this bug to someone who can help me.
1820602,2019-03-19 20:41:05 UTC,"Hi,"
1820604,2019-07-16 14:31:58 UTC,"No, the purpose of this bug task is to tell us whether work needs to be done on this package. Leaving this task open wasted quite a lot of time."
1820604,2019-07-16 10:02:13 UTC,"However, in practice this is like fix-committed. As it will be fix released on 1st of August or later, when the 18.04.3 media is shipped."
1820604,2019-07-16 02:17:37 UTC,Ah but it was backported in https://launchpad.net/ubuntu/+source/livecd-rootfs/2.525.23 back in May. Bad bug discipline it seems.
1820604,2019-07-16 02:05:33 UTC,"Michael, the livecd-rootfs task for bionic is still open, which implies there's still work to be done to fix this for 18.04.3."
1820604,2019-07-16 01:51:17 UTC,I'm pretty sure this was fixed for disco and will be fixed for the next bionic point release.
1820604,2019-07-11 22:26:43 UTC,"I am having a same issue as reported by Jake and Jim.  Trying to install on Lanner hardware using USB stick with ""ubuntu-18.04.2-live-server-amd64.iso"" image.  I used serial console output by enabling console=ttyS0,115200n8 in Grub config.  The installer fails once install attempts to format a hard drive.  I get the following error:"
1820604,2019-07-02 04:00:45 UTC,"I also receive the same ""Unable to find helpers or 'curtin' exe to add to path"" error as Jim K reported in https://bugs.launchpad.net/curtin/+bug/1820604/comments/18, after defining a partition layout in the installer. I am installing on a Lanner FW-8758 using a Rufus-generated USB stick and have tried both ""ubuntu-18.04.2-live-server-amd64.iso"" and ""ubuntu-18.04.2-server-amd64.iso""."
1820604,2019-04-30 02:16:52 UTC,"I received the error below, on a physical device.  The device is an APU2D4 with a 120 GB mSATA SSD and has no video, so I was using the serial port as a putty terminal."
1820604,2019-03-26 00:51:29 UTC,This is fixed now I think? I guess the livecd-rootfs change needs to go back to bionic?
1820604,2019-03-19 17:51:23 UTC,"For PReP, you need:"
1820604,2019-03-19 17:19:16 UTC,New fail:
1820604,2019-03-18 13:28:12 UTC,(Marked as Incomplete until we have some more info on what's motivating this bug report.)
1820604,2019-03-19 15:33:58 UTC,Squashfs errors: https://paste.ubuntu.com/p/FhKBw2Hwp8/
1820604,2019-03-19 15:30:43 UTC,Maybe easier to read the curtin failure with this pastebinit:
1820604,2019-03-19 15:26:30 UTC,"Looks like there are ordering issues wrt. the default console to use hvc0 vs tty0, As I see lots of errors like this one:
Mar 19 14:44:32 ubuntu-server agetty[1923]: hvc0: can't exec /snap/bin/subiquity: No such file or directory"
1820604,2019-03-19 15:20:48 UTC,"Ok, but with even the respun images, i still see the same failure on ppc64le. Let me attach a few logs."
1820604,2019-03-18 22:45:36 UTC,"Oh, it might have helped if I saw this bug before commenting on the MP. It explains the ""what's new so that this is broken"" stuff, which is nothing: this way of invoking curtin has never worked."
1820604,2019-03-18 16:10:52 UTC,What's new in subiquity that we now see this?
1820604,2019-03-18 16:10:18 UTC,Curtin is designed to be called by it's shell wrapper (bin/curtin) in the code.
1820604,2019-03-18 14:32:22 UTC,Ditto with 727 subiquity snap.
1820604,2019-03-18 14:05:48 UTC,"Subiquity calls curtin, which then fails to find curtin_exe, which then fails the installation. With all subiquity disco images currently failing to install."
1820604,2019-03-19 17:16:03 UTC,Ok! Progress!
1820604,2019-03-18 13:27:26 UTC,"It's not clear to me why this is a bug; users shouldn't be driving the curtin in subiquity's snap themselves (right?), and the only evidence here is that that usecase breaks.  Could you expand on what user-facing issue this is causing?"
1820606,2019-04-13 19:10:27 UTC,"This issue is specific to the git implementation of Breezy; I can reproduce the problem you mention when I initialize with ""bzr init --git repo"" but not when I initialize with ""bzr init --bzr repo""."
1820607,2019-03-20 07:34:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820608,2019-03-19 20:28:13 UTC,Thanks for filing this bug in Ubuntu.
1820608,2019-03-19 20:34:22 UTC,"Oh, and I just now saw this:
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd"
1820608,2019-05-19 04:18:02 UTC,[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]
1820609,2019-03-18 13:59:35 UTC,"+1. we used dpkg because at one point at least, the ""packaged version"" meant more than the upstream version. Now in Ubuntu and in rpm packages built from packages/redhat/cloud-init.spec.in a simple 'cloud-init --version' will include the package information as well."
1820611,2019-03-18 14:27:24 UTC,The print preview also has this issue so it looks like the worksheet color setting is being ignored.
1820611,2019-05-26 22:55:44 UTC,"Fixed in revision d2a2dea9c40b50f6bc5f5a8430b73936fe32c32c
https://git.launchpad.net/kicad/patch/?id=d2a2dea9c40b50f6bc5f5a8430b73936fe32c32c"
1820612,2020-09-16 12:30:24 UTC,Going back to Matt's request in #9. We would need the resource inventory and resource usage of the both the source host and the destination host priory to the failed live migration.
1820612,2020-11-16 04:17:15 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1820612,2019-03-20 04:03:27 UTC,And possibly relevant.
1820612,2019-03-20 03:55:20 UTC,Some extra info:
1820612,2019-03-20 03:48:05 UTC,Issued the following commands that failed:
1820612,2019-03-19 14:23:46 UTC,"OK it's pre-Queens as I figured. As mentioned in comment 8 I'm not sure why that PUT /allocations request fails on the source resource provider. It would be helpful if prior to the live migration call, you dumped the resource providers and their existing usage using these commands:"
1820612,2019-03-19 13:41:06 UTC,As for why the PUT /allocations/71111e00-7913-4de9-8f45-ce13fcb8a104 request is failing with this:
1820612,2019-03-19 02:15:12 UTC,I missed that I was filing against the charm. It should indeed be the upstream nova project. Will look into that. Thanks for notifying.
1820612,2019-03-19 13:20:37 UTC,Heh I guess you're doing live migration because that's right in the bug title. :) Sorry for that noise. Please provide which release you're using.
1820612,2019-03-19 13:19:57 UTC,"> Issuing the command to migrate an instance from openstack-6 to another hosts (openstack-17) which does have enough resources
"
1820612,2019-03-19 13:10:25 UTC,On what release you hitting this? That's important information when you are reporting bugs upstream.
1820612,2019-03-19 13:09:52 UTC,"> also there does not seem to be an command to retrieve the resource-provider
"
1820612,2019-03-18 14:15:50 UTC,"While the bug you are reporting may have merits, I'm failing to see how this applies to the charm itself."
1820612,2019-03-19 13:39:07 UTC,The release is Pike 16.1.6-0ubuntu1~cloud1
1820616,2019-03-18 14:55:22 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/644165"
1820616,2019-06-04 14:08:10 UTC,"Reviewed:  https://review.opendev.org/644165
Committed: https://git.openstack.org/cgit/x/ospurge/commit/?id=79ecb6f53c157b651d13cd97d5dfdb7b8437042b
Submitter: Zuul
Branch:    master"
1820617,2019-06-28 17:30:23 UTC,"Working: ubuntu-18.04.2-server-amd64.iso
BUG: ubuntu-18.04.2-live-server-amd64.iso"
1820617,2019-03-18 19:35:21 UTC,"I think, tomorrow's daily will be fixed, but we shall see."
1820617,2019-03-19 01:02:41 UTC,We built new disco images and they passed testing (and local smoke testing). Bionic is still broken though.
1820617,2019-06-27 17:52:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820617,2019-06-27 17:54:03 UTC,Workaround to be able to install in the meantime?
1820617,2019-06-27 18:05:05 UTC,"I understand that the bug has been fixed and released, but the problem is still present in 19.04-live-server-amd64 and 18.04.2-live-server-amd64"
1820617,2019-06-29 17:03:25 UTC,"This was a critical bug that prevented installations of Ubuntu 19.04 from working during the devel series with the server live image.  We certainly did not release Ubuntu 19.04 with an installer image that could not install Ubuntu.  If you think there is something wrong with the Ubuntu 19.04 installer, please file a new bug report with logs showing exactly what is happening on your system."
1820619,2019-03-18 14:55:20 UTC,"This appears to be the mv_branch_product_update trigger, which scales with the number of branches attached to the product and takes about eight seconds on dogfood."
1820620,2019-03-18 16:03:27 UTC,I'm not sure we want to support this behavior.  What is the expected behavior of the router after you place a via while dragging a track?
1820620,2019-03-19 17:26:02 UTC,I would like to offer my sincere apologies to Tom.  I allowed my frustration to make comments (#9) that were poorly worded and thoughtless.  The new router tool is an amazing piece of engineering and I am grateful for all of the hard work Tom did.
1820620,2019-03-19 15:54:57 UTC,"@eelik: do you mean that when you press 'D' with the mouse cursor *at an end* of an existing trace, you can't place vias with 'V'? Is this the case?"
1820620,2019-03-19 14:56:18 UTC,"Yes, but I'm talking about the situation when I've already selected the routing tool, i.e. I'm routing. I consider dragging being part of routing then. If dragging is completely distinct from routing, why allow dragging in routing mode at all? You can't for example move footprints in routing mode."
1820620,2019-03-19 13:51:34 UTC,"I'm not opposed to this idea but it may be confusing to users.  Dragging and routing are distinctly different operations.  Once you fire up the router and begin routing a trace, dragging is no longer possible until you stop routing the current trace.  It sounds to me like it would be better if there was a ""Route From Endpoint"" context menu entry when a trace endpoint is under the cursor."
1820620,2019-03-19 15:43:55 UTC,"I think your missing my point.  It really doesn't matter whether the
router tool is enable or not.  Once you start routing a trace, you
cannot drag any traces.  Calling the action of routing a drag operation
is confusing no matter what tool is enabled."
1820620,2019-03-19 12:59:37 UTC,"I suppose that if we detect that the user is dragging the end of a trace, we could just put them into route mode instead of drag mode and make the dragged segment the head for a track.  Should be equivalent I think."
1820620,2019-03-19 12:20:14 UTC,"I think @eelik has a point. When you are dragging a track by a ""free"" endpoint, it's basically the same feeling as routing, until you realise you can't continue. At that point, seamlessly moving to routing on ""X"" (add more segments) or ""V"" (drop a via and change layer) would be quite intuitive."
1820620,2019-03-18 18:00:52 UTC,"Sometimes, or actually quite often, I draw a track but leave it dangling without continuing to a pad. For example when I'm going to connect it to an MCU but want to decide only after doing that for many other tracks where each one finally ends to. When I continue with a track later I want to start by dragging it because I may want it to go even to another side of the MCU. So, I want begin by dragging it but to continue seamlessly to normal routing."
1820620,2019-03-18 17:25:52 UTC,I second Seth. Why would I want to place vias *while dragging* tracks? Unless you mean dragging the mouse cursor while *routing* a track. Could you make a video of the issue?
1820620,2019-03-19 13:35:30 UTC,Now we are on the same page. I would like to use dragging in the routing mode so that it behaves as the routing mode. Not only vias but with other aspects if possible.
1820666,2019-06-04 02:39:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1820666,2019-06-04 17:20:31 UTC,"Unfortunately, I no longer have Ubuntu. Anyway, thank you for your time Daniel."
1820666,2019-08-04 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1820668,2020-01-07 06:08:12 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/701326"
1820668,2020-01-10 19:48:47 UTC,"Reviewed:  https://review.opendev.org/701326
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=f274615db5a54d28df2f547ecdc2d7177ca20d1e
Submitter: Zuul
Branch:    master"
1820668,2020-01-07 10:24:12 UTC,"Change abandoned by Chandan Kumar (raukadah) (<email address hidden>) on branch: master
Review: https://review.opendev.org/701158"
1820668,2020-01-06 07:53:33 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/701158"
1820668,2019-03-18 16:16:19 UTC,scenario002 not impacted http://logs.openstack.org/41/642941/1/check/tripleo-ci-centos-7-scenario002-standalone/6c5829e/logs/tempest.html.gz
1820668,2019-03-19 00:07:53 UTC,"Reviewed:  https://review.openstack.org/644270
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=a72f9f03d5a1221dd0f1042ddcf4e2f71dabe50e
Submitter: Zuul
Branch:    master"
1820668,2019-03-18 16:17:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/644270"
1820668,2020-01-03 17:54:20 UTC,Need the tempest and security dfg to look into this
1820671,2019-03-18 16:16:11 UTC,scenario002 not impacted http://logs.openstack.org/41/642941/1/check/tripleo-ci-centos-7-scenario002-standalone/6c5829e/logs/tempest.html.gz
1820671,2019-03-18 16:17:51 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/644270"
1820671,2019-03-19 00:07:54 UTC,"Reviewed:  https://review.openstack.org/644270
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=a72f9f03d5a1221dd0f1042ddcf4e2f71dabe50e
Submitter: Zuul
Branch:    master"
1820671,2020-01-07 06:08:13 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/701326"
1820676,2019-04-10 02:45:14 UTC,Thanks for fixing up the missing /EFI/BOOT/mmx64.efi.
1820676,2019-07-31 04:17:31 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1820676,2019-04-04 15:25:32 UTC,"This is probably fixed in the disco dailies (and in disco beta), which now include /EFI/BOOT/mmx64.efi on the image - a recent change.  Is this problem reproducible for you with the current image?"
1820676,2019-03-19 03:27:52 UTC,"Hmm, the 'current' symlink still points to the march 5 image: http://cdimage.ubuntu.com/daily-live/current/"
1820676,2019-03-19 06:53:18 UTC,"The Lenovo setup interface has put Secure Boot and UEFI/Legacy Boot on different pages even though the two prompts interact with each other. Turning Secure Boot off on one screen will then let you switch to Legacy Boot, and then the memory stick will boot again. More tomorrow."
1820676,2019-03-19 03:25:41 UTC,"I can't boot arch on a memory stick, either, but there's no error message. It just returns to the uefi boot menu:"
1820676,2019-03-19 13:32:53 UTC,\EFI\BOOT\mmx64.efi should be on all the images; we should investigate this in case it was somehow dropped.
1820677,2019-03-18 17:11:08 UTC,Fix a typo.
1820685,2019-03-19 02:34:47 UTC,Low resolution during boot is something usually caused by the Nvidia proprietary driver. So I wonder if you might still have some remnants of that installed?
1820685,2019-03-19 02:37:19 UTC,Actually it looks like just vesafb starting in low resolution:
1820685,2019-03-19 02:38:50 UTC,Can you please try some slightly older kernels and tell us if using those avoids the bug?
1820685,2019-03-19 21:17:53 UTC,After some reading on internet I decided yesterday to install the nvidia diverse in package nvidia-driver-390. This resulted in a non-working graphic display. So I had to restore my installed packages and remove the nvidia-driver-390 package.
1820685,2019-05-19 04:18:04 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1820686,2019-03-18 19:29:47 UTC,"Thanks.  If you spin a full patch (ie, ""git commit -s"" and then ""git show"") I can drop it on riscv-qemu-3.1, our backports branch.  Otherwise hopefully we got the bug via the decodetree conversion."
1820686,2020-11-21 22:51:07 UTC,"Since this bug isn't present in the decodetree version of the riscv decoder, we might as well just close this as fix-released; we won't be doing more point-releases of QEMU versions as old as 3.1."
1820687,2019-05-20 04:17:16 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1820687,2019-03-20 07:12:06 UTC,Let's check dmesg. Please run `apport-collect 1820687`.
1820687,2019-03-19 16:33:12 UTC," I am not sure I know what a cold boot is but that partition is not gone yet. I can try once I know what it is. This is on an older Dell Dimension 8400 tower. Dual booting with Win 7 and separate drive with Win XP. This machine is what I use as a hobby for some gaming my laptop with dual boot Win 10, Linux Cinnamon 18.3 and Ubuntu Bionic Beaver won't do with ease. Laptop heats now and shuts down. Off topic but let me know and I'll try it. Thanks for your help and efforts."
1820687,2019-03-19 04:51:12 UTC,Does the sound come back by booting an older kernel?
1820687,2019-03-19 05:49:39 UTC," I tried launching an earlier kernel, which has worked in the past. It did not this time and so I downloaded Linux Mint 19.1 to run side by side and transfer from its predecessor 18.3 to the newest one and when done will eliminate the elder partition. I have done that before, as well. This one was stubborn. The problem occurred once before in Ubuntu and I updated by clean install that time as well. I find it a bit tedious to state the many terminal commands suggested that I tried. I am still not so technically savvy. I do have a hands on like most around me don't but I am not there yet as far as a guru or wizard."
1820687,2019-03-18 17:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820687,2019-03-19 06:00:08 UTC,Does a cold boot help?
1820690,2019-03-18 22:06:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1820690,2019-05-18 04:17:31 UTC,[Expired for ibus-unikey (Ubuntu) because there has been no activity for 60 days.]
1820691,2019-05-23 12:28:25 UTC,Please try running:
1820693,2019-04-01 12:46:06 UTC,"Personally, I find this behavior more annoying when working in eeschema than pcbnew.  Mostly because hierarchical sheets will normally generate schematics without associated .pro files.  Opening one from stand-alone eeschema will pollute the directory."
1820693,2019-06-19 08:57:00 UTC,Or detect if the directory has already a project file and open that instead of a dummy one (as it is likely that one wants the same settings in such a sub sheet compared to the main sheet even if opening it via the file browser.) Only if there is no project file would i go for creating a dummy project. (See it as opening the project but on a different page than the main one.)
1820693,2019-04-02 13:18:22 UTC,"@Seth, I think using a temporary dummy project file is a workable solution."
1820693,2019-04-01 12:19:32 UTC,Maybe only make the .pro file when the board has changes saved?
1820693,2019-03-19 06:56:45 UTC,The normal way to use kicad is to have one project with all its files inside the project directory. Editing hierarchical sheets is then not done by opening them from the OS file browser but with the help of the hierarchical navigator.
1820693,2019-03-20 21:57:45 UTC,I also have this issue.
1820693,2019-03-19 07:09:23 UTC,different revisions or boards which do not need ANY accompanying schematic. The latter is something I have a plurality of boards for which each demand a .pro file for no purpose.
1820693,2019-04-01 01:19:45 UTC,Some board settings are stored in the project file.
1820693,2019-03-19 07:18:02 UTC,I especially make much use of bitmap to component converter. Its one of the more excellent and utmost useful features of kicad. With this I make boards which do not need any schematics or project files.
1820694,2019-03-18 18:19:24 UTC,"StacktraceTop:
 convert_alpha (height=1012, width=1886, src_y=0, src_x=<optimized out>, src_stride=4096, src_data=0x7feb8d7e3a30 """", dest_stride=7544, dest_data=0x55bea0b6d888 """") at ../../../../gdk/gdkpixbuf-drawable.c:187
 gdk_pixbuf_get_from_surface (surface=0x7feb8d7c1d10, src_x=<optimized out>, src_y=0, width=1886, height=1012) at ../../../../gdk/gdkpixbuf-drawable.c:295
 boxes_machine_real_take_screenshot_co (_data_=0x55bea0500f30) at ../src/machine.vala:375
 boxes_machine_real_take_screenshot (self=0x55be9ec29240, _callback_=0x55be9d3c0470 <boxes_machine_update_screenshot_ready>, _user_data_=0x55bea04f4630) at ../src/machine.vala:5
 boxes_machine_take_screenshot (_user_data_=0x55bea04f4630, _callback_=0x55be9d3c0470 <boxes_machine_update_screenshot_ready>, self=<optimized out>) at ../src/machine.vala:5"
1820728,2019-05-28 13:48:40 UTC,"Hi Peng,"
1820728,2019-03-20 17:46:26 UTC,This command is no longer valid for the container env. Marking as release gating; this bug will be used to remove this system command.
1820728,2019-04-08 06:48:08 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650619"
1820728,2019-04-30 07:24:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656452"
1820728,2019-05-13 16:59:40 UTC,"Reviewed:  https://review.opendev.org/656452
Committed: https://git.openstack.org/cgit/starlingx/gui/commit/?id=276b2a7cfb3606dcf6b4db918e552498376ad20e
Submitter: Zuul
Branch:    master"
1820728,2019-05-15 15:13:33 UTC,"Reviewed:  https://review.opendev.org/650619
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=b14faccecd9a218ae93badf4fd89a969ec962cb0
Submitter: Zuul
Branch:    master"
1820728,2019-05-28 13:34:39 UTC,the command seems still be seeing as below
1820728,2019-06-06 18:45:43 UTC,"verified on
20190604T144018Z"
1820741,2020-04-28 17:26:03 UTC,"Fixes pushed to master and rel_3_5.  Thanks Dan, Jason, and Terran!"
1820741,2020-04-28 15:20:39 UTC,"Terran was testing a server that also had applied the top commit here, which needs a signoff as well:"
1820741,2019-03-20 16:57:03 UTC,Fix in process
1820741,2020-03-16 17:00:28 UTC,"Daniel Pearl was working on this bug, among others, before he left CW MARS.  He left behind an omnibug branch that is intended to fix most of these issues.  I have had these bugs assigned to me since before his departure because it was my intention to clean his branch up, test it, and add any missing bits.  I have not had time to do this, so I am simply putting the branch out there in the hope that someone can test what's there during bug squashing week or whenever."
1820741,2020-04-27 21:24:36 UTC,This is fixed as part of the receipt omnibus patch. My signoff to that is at:
1820743,2020-02-08 16:54:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820747,2019-03-18 19:51:42 UTC,Looks like this code is truly dead now.  Confirming.
1820752,2019-03-19 13:02:15 UTC,This would clearly be a feature so it should have at least a blueprint:
1820753,2020-01-07 16:54:22 UTC,This issue is still present in 2.6
1820753,2019-09-19 14:59:25 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1820754,2019-11-21 19:49:33 UTC,"Hi, please test the following kernel to see if the issue is fixed: https://private-fileshare.canonical.com/~sultan/trusty-bcache-test1.tar.gz"
1820754,2019-03-18 20:32:41 UTC,Kernel oops when attempting to stop an online bcache device.
1820754,2019-03-18 21:00:08 UTC,This change was made by a bot.
1820760,2019-04-12 11:34:45 UTC,"Hello,
I have build a 4.18 HWE kernel that includes this fix, can you give it a try to see if it can solve this issue:
http://people.canonical.com/~phlin/kernel/lp-1820760-SYNA3602/"
1820760,2019-04-12 20:02:31 UTC,"Dear Po-Hsu Lin,"
1820760,2019-04-16 04:00:09 UTC,Fix already available in Disco kernel.
1820760,2019-05-03 15:21:55 UTC,"Dear Po-Hsu Lin,"
1820760,2019-05-16 07:44:11 UTC,"Hello Simone,"
1820760,2019-05-17 06:29:40 UTC,"Hello Po-Hsu Lin,"
1820760,2019-08-11 08:50:44 UTC,Yesterday my distribution updated to Ubuntu 18.04.3 and thanks to the new kernel the touchpad is recognized and perfectly working.
1820760,2019-08-12 01:57:51 UTC,"That's a good news, thank you for your patience."
1820760,2020-09-06 02:27:03 UTC,"I have a new Teclast F6 Plus.
Wi-Fi, touchscreen and touchpad are not working.
What would be a proper bug-fix request for this issue? Sorry if this is not a right place to ask this, I am a newbie."
1820761,2019-03-19 00:22:42 UTC,"The attachment ""replaces %U for %F in the Exec line of the desktop file."" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1820762,2019-04-17 16:43:44 UTC,"Hi,"
1820764,2019-07-18 08:17:12 UTC,This bug was fixed in the package edk2 - 0~20180803.dd4cae4d-1ubuntu1.1
1820764,2019-07-18 08:07:49 UTC,This bug was fixed in the package edk2 - 0~20180205.c0d9813c-2ubuntu0.1
1820764,2019-07-18 08:07:11 UTC,"The verification of the Stable Release Update for edk2 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820764,2019-07-15 19:16:44 UTC,"Verified both cosmic & bionic builds by booting an existing guest up, and by PXE booting in a way requiring DNS resolution."
1820764,2020-04-30 19:43:25 UTC,This bug was fixed in the package edk2 - 0~20160408.ffea0a2c-2ubuntu0.1
1820764,2019-07-10 20:14:23 UTC,"Hello dann, or anyone else affected,"
1820764,2019-03-27 16:19:21 UTC,"On Wed, Mar 27, 2019 at 9:35 AM Janåke Rönnblom <email address hidden> wrote:

>
> Can the edk2/ovmf package for Bionic be updated to the latest version?
>
> 0~20190309.89910a39-1ubuntu1
"
1820764,2019-03-27 15:26:12 UTC,Can the edk2/ovmf package for Bionic be updated to the latest version?
1820764,2019-03-27 15:23:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820764,2019-07-10 20:15:58 UTC,"Hello dann, or anyone else affected,"
1820765,2019-05-23 04:17:27 UTC,[Expired for thunar (Ubuntu) because there has been no activity for 60 days.]
1820765,2019-03-23 11:59:46 UTC,"Does ~/.xsession-errors contain any related messages? Furthermore, is this issue present when using a new user account?"
1820768,2019-03-21 09:41:32 UTC,ref: https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-next
1820768,2019-12-27 05:39:47 UTC,I verified following functions in fwupd 1.2.10 on Dell Latitude 5300:
1820768,2019-12-23 17:44:54 UTC,"On Tue, Dec 17, 2019 at 09:00:13PM -0000, Mario Limonciello wrote:

> I think that leaves two options then:
> 1) Remove unversioned Breaks: fwupdate-signed from fwupdate source package,
>    convert fwupdate-signed into transition package in Ubuntu as part of this SRU.
> 2) Change unversioned Breaks: fwupdate-signed from fwupdate source package into unversioned Conflicts: fwupdate-signed.
> From Steve's comment, I'm not sure this would work though.  So I think my preference would be <1> above.
"
1820768,2019-12-23 08:27:22 UTC,for D-5 verification:
1820768,2019-12-23 02:24:23 UTC,per
1820768,2019-12-20 11:16:38 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2019-12-20 02:42:03 UTC,Not sure we need Steve or someone else can just help on the version issue below.
1820768,2019-12-19 18:17:44 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2019-12-19 09:36:06 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2019-12-19 08:53:19 UTC,"The transitional fwupdate-signed is definitely needed, since all the desktop metapackages Recommend it and the image build fails due to the breaks. I've uploaded a new version with the preinst cleanup modified as on gitlab, it looks fine to me."
1820768,2019-12-19 04:17:08 UTC,"comment 30 is handle in another bug LP: #1856896. Per Robert, he upload another version to bionic queue."
1820768,2019-12-17 21:00:13 UTC,"Here is the revised preinst that should cover the different problems outlined:
https://salsa.debian.org/efi-team/fwupdate/commit/85533b1f392399ee53f88e71091044a69dabbdc4"
1820768,2019-12-17 20:27:31 UTC,"> /boot/efi/EFI/ubuntu
"
1820768,2019-12-17 20:04:37 UTC,"I've tested an apt upgrade on a chroot, and I see that fwupx64.efi is indeed left behind in /boot/efi/EFI/ubuntu, just like on my laptop install (eoan)."
1820768,2019-12-17 09:35:08 UTC,"per test again today with stock ubuntu image, it behaves differently from oem image."
1820768,2019-12-16 14:05:09 UTC,Just manage to do a quick test on case D and it does fail.
1820768,2020-01-08 02:51:55 UTC,regression: https://github.com/fwupd/fwupd/issues/1675
1820768,2020-01-09 09:00:22 UTC,version 1.2.10-1ubuntu2~ubuntu18.04.3~oem1 in ppa https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd-1.2.10-p3 fix the regression on #60.
1820768,2020-01-14 05:51:52 UTC,"upload 1.2.10-1ubuntu2~ubuntu18.04.3~oem2 to the ppa in #61,"
1820768,2020-01-17 12:06:42 UTC,"An upload of fwupd to bionic-proposed has been rejected from the upload queue for the following reason: ""You need to use -v when building the source package if there's an upload in -proposed already, otherwise the other bug would not get notified of the new version or closed automatically.""."
1820768,2020-02-17 10:12:31 UTC,This bug was fixed in the package fwupd - 1.2.10-1ubuntu2~ubuntu18.04.3
1820768,2020-02-17 10:02:36 UTC,"The verification of the Stable Release Update for fwupd has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820768,2020-02-17 10:02:36 UTC,This bug was fixed in the package libxmlb - 0.1.8-1~ubuntu18.04.1
1820768,2020-02-17 10:02:32 UTC,This bug was fixed in the package fwupdate - 12-7~ubuntu18.04.3
1820768,2020-02-17 10:02:28 UTC,This bug was fixed in the package fwupd-signed - 1.10~ubuntu18.04.3
1820768,2020-02-04 12:15:59 UTC,"per test 1.2.10-1ubuntu2~ubuntu18.04.3, with stock ubuntu and oem ubuntu image, fwupd upgrading with update-manager work perfetctly."
1820768,2020-02-04 10:10:11 UTC,"saninty check for 1.2.10-1ubuntu2~ubuntu18.04.3 passed.
1. downgrade to the previous bios via capsule file locally
2. upgrade to the latest bios version via online LVFS"
1820768,2019-12-16 03:25:48 UTC,"On Mon, Dec 16, 2019 at 02:54:12AM -0000, Mario Limonciello wrote:

> Archive administrator needs to release UEFI archives.
"
1820768,2020-02-03 06:42:07 UTC,"per test 1.2.10-1ubuntu2~ubuntu18.04.3, it fix the regression mentioned in #60."
1820768,2020-01-29 08:05:20 UTC,"I installed fwupd and fwupd-signed from -proposed and removed fwupdate
as a update for my bios is available I would like to upgrade but:"
1820768,2020-01-29 07:49:04 UTC,"@sil2100, Most of us still taking the Chinese New Year Holidays. I believe this can be verified in the first two days of next week. Let me know if you do need it earlier than that."
1820768,2020-01-28 11:46:10 UTC,"Can we get this verified for bionic? 18.04.4 is nearing, so I'd like to move as many things from -proposed to -updates as possible."
1820768,2020-01-21 17:54:58 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2020-01-20 10:52:56 UTC,"right, my mistake.. I've recovered the upload from the rejected queue and accepted"
1820768,2020-01-20 10:52:22 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2020-01-17 18:56:22 UTC,@Timo: Is that true even when the subsequent proposed upload merges all changes into the same package version?
1820768,2020-01-29 08:33:31 UTC,"sorry for the noise, it's a problem on my system which is a kde neonized ubuntu where the ID in /etc/os-release is set to neon. once switching back to ubuntu fwupd worked..."
1820768,2019-12-16 02:54:12 UTC,Archive administrator needs to release UEFI archives.
1820768,2019-12-20 11:06:34 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2019-12-14 02:53:00 UTC,"#37: need to check.
#38: please check #13. Shall be fine. Will still test again."
1820768,2019-07-25 18:30:11 UTC,"I'm unclear on the specifics goals required in terms of fwupdate compatibility during this transition.
1) 1 signed EFI binary in bionic?
2) Command line compatibility?
3) Other?"
1820768,2019-07-24 15:46:56 UTC,"libxmlb is accepted now into -proposed which is ok, and fwupd-signed has also been accepted into -proposed but is dep-wait because the corresponding fwupd has not yet been accepted, so this is also ok (though the accepting of fwupd-signed may have been an accident)."
1820768,2019-07-24 15:22:11 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2019-07-24 14:03:18 UTC,"Per information from Mario, we need the new fwupd efi app from the new fwupd. However it's not compatiable with existing fwupdate. That's how fwupd break fwupdate."
1820768,2019-07-24 13:52:13 UTC,this sru will break fwupdate package in bionic/main. However fwupdate is in disco/universe.
1820768,2019-07-12 16:12:16 UTC,"Per comment #8 and #9, #12"
1820768,2019-06-24 09:17:28 UTC,"for #8, in disco, after using ""fwupdmgr install xxx.cab"", fwupdx64.efi does been installed in /boot/efi/EFI/ubuntu."
1820768,2019-08-27 06:49:28 UTC,PPA for fwupd 1.2.10.
1820768,2019-06-24 07:20:41 UTC,A firmware download from lvfs is in cab format.
1820768,2019-12-16 01:35:57 UTC,"@Steve, not sure what went wrong, the archive seems not properly update."
1820768,2019-05-24 10:03:57 UTC,"an archive admin should review all of these at the same time, since libxmlb/fwupd-signed are in source NEW"
1820768,2019-05-09 21:32:16 UTC,"> 4) fwupd-signed needs to be introduced
"
1820768,2019-05-09 19:41:48 UTC,I didn't deal with fwupdate-signed but from past discussion I think we are going to want to remove this one to only have one signed binary in the archive. I don't think it's going to block the SRU to be accepted but would still be nice to handle it ... does anyone want to look at that one?
1820768,2019-05-09 15:24:16 UTC,"libxmlb backport uploaded to the bionic SRU queue, thanks Mario for the ""build with the old meson"" patch"
1820768,2019-03-25 20:22:51 UTC,4) fwupd-signed needs to be introduced
1820768,2019-03-25 20:21:48 UTC,To SRU fwupd 1.2.5 to bionic the following actions are needed.
1820768,2019-06-18 09:27:52 UTC,"per check apt-cache show fwupd / fwupd-signed, I didn't find any conflict and break on fwupdate."
1820768,2019-09-05 06:21:21 UTC,"Yuan-Chen, I installed fwupd from your ppa. Logitech fw-update works, thanks.
unfortunately system firmware on my xps13 does not as fwupd complains about missing signed bootloader:
""UpdateError:          missing signed bootloader for secure boot: /usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found"""
1820768,2019-06-18 08:40:56 UTC,per doing some investigation:
1820768,2019-09-05 09:32:01 UTC,fwupdate has been dropped from eaon in bug #1841744.
1820768,2019-12-13 21:21:13 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2019-12-13 21:19:04 UTC,"$ ls -l /boot/efi/EFI/ubuntu/fwup*
-rwxr-xr-x 1 root root 71400 Mar 21  2018 /boot/efi/EFI/ubuntu/fwupx64.efi
$"
1820768,2019-12-13 20:58:05 UTC,"Additionally I notice that on my eoan system which has been continuously upgraded, I have both a /var/lib/fwupdate and a /var/cache/fwupdate directory left behind.  Something should be taking care of cleaning these directories up on upgrade.  Since the fwupdate transitional package in later releases did not do so, I think this needs to be done in the fwupd package now since the fwupdate package isn't guaranteed not to have already been removed (it is removed on my system)."
1820768,2019-12-13 20:26:09 UTC,"Hello Yuan-Chen, or anyone else affected,"
1820768,2019-12-13 20:21:07 UTC,"An upload of fwupd to bionic-proposed has been rejected from the upload queue for the following reason: ""wtf g""."
1820768,2019-12-13 20:16:00 UTC,"An upload of fwupd to bionic-proposed has been rejected from the upload queue for the following reason: ""reuploading without additional bolt recommends""."
1820768,2019-12-13 20:12:50 UTC,"Sorry, I was looking at a wrong path in the diff and it seems the tpm2-* Recommends: are only present in contrib/debian/control.in, not in debian/control.in.  So that was done correctly and doesn't need changing.  I'll still be dropping the Recommends: on bolt however."
1820768,2019-12-12 08:37:00 UTC,"@Timo and Steve, for the patch in #30, I simply put the commit in debian/patch and modify series, then it can be perperly built."
1820768,2019-12-13 20:08:52 UTC,"I have added an explicit test case for the packaging changes, since that is a large part of why this SRU has taken as long to sort out - we need to ensure that the package upgrades work correctly."
1820768,2019-11-21 20:10:48 UTC,Can we please follow up on this?  This type of smooth upgrade stuff needs to happen before focal too so that people can jump from bionic->focal.
1820768,2019-09-05 07:38:39 UTC,"@Bearsh, Thank you for testing."
1820768,2019-10-25 09:26:19 UTC,"Steve, could you have another look at this? Mario addressed the concerns in #19, and fwupdate backport in the queue should make the upgrade smooth."
1820768,2019-10-25 09:06:37 UTC,"the updated the fwupd 1.2.10 ppa. It need the libxmlb that already in proposed channel.
https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd-1.2.10-2"
1820768,2019-10-25 08:38:45 UTC,"I've uploaded the transitional fwupdate to the queue, and rejected the old fwupd upload because it was based on 1.2.5 and AIUI the desire is to get 1.2.10 in bionic, ycheng promised to prepare that soon."
1820768,2019-09-24 15:01:55 UTC,"FYI That did sync back to Ubuntu eoan as well.  I think that as part of transitioning 18.04, it should come back to 18.04 with the updated SRU."
1820768,2019-09-05 16:02:29 UTC,"Here's link for what's happening in Debian at 12-6.
https://tracker.debian.org/news/1061561/accepted-fwupdate-12-6-source-into-unstable/"
1820768,2019-12-11 17:38:21 UTC,"Hello, any updates on this?  It would be good to get any review comments because the SRU will need to be modified again to include this as well: https://github.com/fwupd/fwupd/commit/004a0624d05211e8436060bb7af6b0c6f2d805a3"
1820770,2019-03-22 19:59:16 UTC,"Thanks for your reply.  I had used chrome browser to print the article and the preview did not show the break in but showed the document in entirety.  I just used foxfire and the document printed in entirety but with two more pages due to larger font, which is fine really, so I guess I will start using Firefox more for the the things that chrome won't do as it is becoming clearer that Firefox seems more versatile at this time than chrome (which I've been using since streaming Netflix was made possible years ago). Anyhow TMI,
Thx!"
1820770,2019-03-20 13:57:17 UTC,"Which browser did you use?
Does the preview of the browser's print dialog also show the broken printout?
Can you print the same web pages with another browser?"
1820770,2019-05-22 04:17:33 UTC,[Expired for cups (Ubuntu) because there has been no activity for 60 days.]
1820771,2019-03-20 16:27:11 UTC,"Reassigning to systemd -- netplan isn't limited, but if systemd-networkd crashes that's a bug in systemd-networkd."
1820773,2019-03-19 00:55:39 UTC,"Hi there,"
1820773,2019-03-19 01:32:11 UTC,Ah woops. That's embarrassing.
1820773,2019-03-19 03:21:28 UTC,Thanks for reporting this Matthew.
1820773,2019-03-19 03:33:48 UTC,"Actually, GUI issues are tracked in github. I have added here - https://github.com/juju/juju-gui/issues/3903"
1820776,2019-03-19 19:53:40 UTC,"Well, that's odd.  I have no issues with that.  A couple of questions:"
1820776,2019-03-20 02:04:50 UTC,"1) Holding Shift + Arrow Keys, makes the eeschema scroll horizontally/vertially (moves the sheet)"
1820776,2019-03-20 02:07:21 UTC,"1) Shift + Arrow_Keys = Moves the sheet, behaves like scrolling hrizontally/vertically
2) Ctrl + Arro3_Keys = Nothing happens"
1820776,2019-03-20 02:37:31 UTC,"Are these the arrow keys on the number pad or the inverted ""T"" arrow keys?"
1820776,2019-03-20 03:11:54 UTC,"They are the unique arrow keys I have on my laptop. It is an Dell XPS 15
(9570). Google it to see how it is. But is a standard keyboard."
1820776,2019-05-19 04:18:12 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1820779,2019-05-19 04:17:32 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1820779,2019-03-19 13:28:20 UTC,This appears likely to have been a transient network issue. Are you able to reproduce the same crash again if you try the install again?
1820780,2019-03-19 04:20:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1820781,2019-11-18 23:12:32 UTC,i think something snapped here recently
1820781,2019-12-04 14:54:14 UTC,I confirm that this is a packaging issue.
1820781,2019-12-04 15:39:11 UTC,Does this affect the most recent 5.1.5 package?
1820781,2019-12-04 16:14:49 UTC,It affects 5.1.5_1 and 5.1.5_2.
1820781,2019-12-04 16:42:09 UTC,"The original bug here is not a packaging issue, but rather that we
missed fixing the Python executable search path in eeschema the same
way we do in pcbnew, but that's different than the windows python.exe
vs python3.exe, buuut if someone fixes that via a patch, maybe we
could fix both at the same time."
1820781,2019-12-04 16:52:31 UTC,"Hmm, I am not sure what the original report is about, but I am talking about the issue in #1 and that is a windows packing issue. It will be fixed in the 5.1.5_3 windows build."
1820781,2019-12-04 20:08:43 UTC,"@Nick, what happened with the milestone and assignee?  Did you discover that the bug was not a windows package build issue?"
1820781,2019-12-04 22:10:59 UTC,"@Wayne, I have no idea what the original bug description is about. But it seems to be something different, what I fixed is what Nicholas reported in #1, and there was another bug for that."
1820781,2019-12-04 22:24:24 UTC,I propose to move the discussion here: https://gitlab.com/kicad/code/kicad/issues/1880
1820784,2020-06-25 00:23:45 UTC,This issue was fixed with https://review.opendev.org/#/c/682265/ and https://review.opendev.org/#/c/682512/
1820789,2019-03-20 09:18:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820789,2019-04-18 11:45:49 UTC,Same issue here. Are they any patches or currently developing some?
1820790,2019-03-19 12:59:55 UTC,"What release are you using? The flavor used to create an instance (and last resize it) are embedded in the database with the instance (see the instance_extra.flavor entry in the DB). If you are having issues because of deleting flavors that some servers are using, you might just be on a very old release that is not using the embedded flavors properly (like Juno or older?)."
1820790,2019-03-19 13:44:46 UTC,"Hi,"
1820790,2019-05-19 04:17:44 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1820790,2019-12-12 18:59:45 UTC,"You're saying that resize is failing on a server that is using a deleted flavor, but can you provide specific steps to recreate along with logs of the failure? I'm assuming these are the steps:"
1820790,2019-12-12 19:06:19 UTC,https://review.opendev.org/#/c/307518/ was the tempest integration test I was thinking of.
1820790,2020-02-11 04:17:29 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1820794,2019-03-19 06:33:53 UTC,According to the attached AlsaInfo.txt the kernel doesn't have a driver compatible with your internal sound card:
1820794,2019-03-19 06:39:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820794,2019-06-26 00:02:47 UTC,please run dpkg --list | grep oem-audio-*
1820794,2019-06-26 01:26:00 UTC,I tried it and this is what it says
1820794,2019-06-26 01:32:30 UTC,In that case please run:
1820794,2019-06-26 07:17:08 UTC,It's fixed! Thank you so much for your help ^_^
1820795,2019-05-19 04:17:58 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1820795,2019-03-19 15:35:55 UTC,"Oh, forgot to mention, the second installation attempt with previous installation removed succeeded without error."
1820795,2019-03-19 13:26:26 UTC,There are some odd errors in UbiquitySyslog.txt I haven't seen before:
1820795,2019-03-19 15:28:05 UTC,"Name entered was ""localadmin"" without the quotes
Machine name was ""vader-l"""
1820796,2019-03-19 04:57:08 UTC,LP: #1812099?
1820796,2019-03-19 05:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820796,2019-03-19 06:04:49 UTC,"Yep. I didn't find that, I filed a new Ubuntu kernel bug which I will now
close."
1820796,2019-03-19 06:08:06 UTC,already fixed (see https://lists.ubuntu.com/archives/cosmic-changes/2019-March/012430.html)
1820797,2019-03-25 14:58:35 UTC,"We will only allow this through set-description and set-summary actions similar to set-version given the complexities and documentation hurdles this will bring for what could be a one time things. Extracting info is a give or take action, overridable already by just declaring the keyword you wish not to take."
1820798,2019-04-20 20:39:52 UTC,Could you please submit this in the form of a MR against https://salsa.debian.org/debian/devscripts ?
1820798,2019-07-31 04:43:02 UTC,This bug was fixed in the package devscripts - 2.19.6
1820798,2019-07-09 12:29:40 UTC,"It's committed, will be in the next release."
1820798,2019-05-07 04:28:19 UTC,MR submitted in https://salsa.debian.org/debian/devscripts/merge_requests/121
1820798,2019-05-02 06:13:07 UTC,Sure I'll see what I can do - my understanding was the process was to get it into Ubuntu first and then submit it back to Debian but am happy to go the other way round.
1820798,2019-04-20 20:30:52 UTC,"Subscribing Mattia Rizzolo, who co-maintains devscripts in Debian."
1820798,2019-03-31 23:14:53 UTC,Will let the foundations team decide on the importance of this but the security team is keen for this to land in 19.10 / EE to support the toolchain hardening updates so I hope this is seen as a higher priority than Wishlist.
1820798,2019-04-09 07:43:19 UTC,The attached should is more robust to optimisation in gcc and is updated against the latest devscripts in disco
1820798,2019-04-08 00:40:06 UTC,It looks like the stack-clash detection is getting tripped up on optimization:
1820798,2019-03-22 01:33:32 UTC,Update the debdiff again to fix a possible runtime failure in a highly unlikely corner case.
1820798,2019-03-21 03:55:43 UTC,Updated debdiff with some minor improvements to the proposed changes to be a bit more efficient and add some more comments
1820798,2019-03-19 08:21:35 UTC,"The attachment ""debdiff against current version in disco to add this feature"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1820798,2019-04-10 05:15:12 UTC,Relaxed some of the checks to find additional stack-clash-protected binaries due to more optimisation shenanigans
1820802,2019-03-27 16:56:43 UTC,"Note that having nova be able to clean up instances it doesn't know about (nova-manage db archive_deleted_rows on deleted!=0 instances) is a fundamental shift from how things have historically been done. Today, nova will not touch instances that do not have records in the database. Scenario: ops engineer creates a libvirt domain on a compute host out-of-band from nova in order to do some testing -- nova-compute will not touch it today. If we make a change to be able to reap them, nova-compute could destroy that testing libvirt domain."
1820802,2019-04-01 07:45:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648912"
1820802,2019-04-01 07:45:31 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648913"
1820802,2019-04-01 07:47:45 UTC,"Change abandoned by Yongli He (<email address hidden>) on branch: master
Review: https://review.openstack.org/648913
Reason: duplicated with https://review.openstack.org/#/c/627765/"
1820802,2019-04-04 13:07:50 UTC,"Marking this wishlist because as Mel noted this is a new feature really, and not something nova has historically dealt with, but I've heard from several operators that run lots of live migrations that they need this kind of cleanup routine. It could be implemented external to nova, but it's nice to have one tool that handles it natively."
1820807,2019-03-19 09:28:21 UTC,The fillet tool is not compromised by the utility of the arc tool. They are not meant to serve the same roles.
1820807,2019-03-19 09:16:32 UTC,(I'm not a KiCad developer.)
1820811,2019-04-24 07:35:37 UTC,It seems 4.18.0-18 fixes the issue.
1820811,2019-04-05 17:27:39 UTC,"Yes, hang re-occurs regardless of whether the device was plugged in at boot or not."
1820811,2019-04-05 16:59:19 UTC,"Sorry for the delayed followup, but if your machine is booted with it plugged in, are you then able to unplug and re-plug the device without issue?"
1820811,2019-03-21 14:54:04 UTC,"> With the affected kernel versions, does the hang still occur if the dock is connected before booting?
"
1820811,2019-03-21 13:12:18 UTC,We are trying to determine if this bug is related to bug #1819924.
1820811,2019-03-20 07:13:48 UTC,Would it be possible for you to do a kernel bisection?
1820811,2019-03-19 09:46:08 UTC,apport information
1820811,2019-03-19 09:46:07 UTC,apport information
1820811,2019-03-19 09:46:06 UTC,apport information
1820811,2019-03-19 09:46:05 UTC,apport information
1820811,2019-03-19 09:46:03 UTC,apport information
1820811,2019-03-19 09:46:01 UTC,apport information
1820811,2019-03-19 09:46:01 UTC,apport information
1820811,2019-03-19 08:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820811,2019-03-19 09:45:54 UTC,apport information
1820811,2019-03-19 09:45:55 UTC,apport information
1820811,2019-03-19 09:45:56 UTC,apport information
1820811,2019-03-19 09:46:02 UTC,apport information
1820811,2019-03-19 09:45:58 UTC,apport information
1820811,2019-03-19 09:45:59 UTC,apport information
1820811,2019-03-19 09:46:00 UTC,apport information
1820811,2019-03-19 09:45:57 UTC,apport information
1820812,2019-03-20 17:34:06 UTC,"I could have sworn this had already been requested, but I couldn't find it...."
1820814,2019-05-11 00:59:19 UTC,I think trying to determine if a script is action plugin or not is moot point. It may be an action plugin but it can still do some calls in init that are crashing pcbnew. Problem is the API calls that are crashing the program if it's not in correct state.
1820814,2019-04-01 08:35:28 UTC,"It woyld be really nice to have kicad not crash when running a python script which is buggy, but I have no idea how that would work out."
1820814,2019-04-01 03:05:50 UTC,I think we should be able to determine whether scripts in the scripting directory are correct ActionPlugin derivatives without crashing.
1820814,2019-04-01 01:21:16 UTC,"So is this a ""won't fix"" then?"
1820814,2019-03-20 09:38:17 UTC,"It crashes on my W7 32 bits install.
Because the script crashes (segfault) when running from a msys shell, i am guessing this script is run by the action script loader and the line:
""board = GetBoard()""
is executed before initializations are made, thus creating a segfault."
1820814,2019-03-20 14:18:05 UTC,"AFAIR, all scripts in the action plugin script paths must be derived from the ActionPlugin object.  All other user python scripts should be placed a path not searched by the action plugin manager.  The documentation for this can be found at http://docs.kicad-pcb.org/doxygen/md_Documentation_development_pcbnew-plugins.html.  FYI, this documentation was not complete due to a markdown syntax bug.  The bug has been fixed and the documentation will be updated as soon as the build server is done."
1820814,2019-03-20 06:23:40 UTC,Tried this in the equivalent linux location but no issues.  Any windows devs can test this?
1820816,2019-03-19 08:47:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820817,2020-04-01 17:05:22 UTC,This issue was fixed in the openstack/glance_store 2.0.0 release.
1820817,2019-03-19 10:22:24 UTC,"Somehow Gerrit/Launchpad integration did not work, so here is the patch to fix this:"
1820817,2020-03-26 05:11:54 UTC,"Reviewed:  https://review.opendev.org/644390
Committed: https://git.openstack.org/cgit/openstack/glance_store/commit/?id=ee2a3d3032408ff3d12beafd6ae84d75b33f479f
Submitter: Zuul
Branch:    master"
1820827,2019-05-25 04:17:35 UTC,[Expired for neutron because there has been no activity for 60 days.]
1820827,2019-03-25 21:31:28 UTC,"Haven't heard back from submitter. Marking incomplete for the time being, until we get a response"
1820827,2019-03-21 08:49:46 UTC,1. Try to install with pip instead of apt-get [1]
1820827,2019-03-22 16:42:23 UTC,"@hanbo,"
1820828,2019-03-19 10:47:41 UTC,"Can't see this when verifying this manually, re-triggered on the jenkins."
1820828,2019-03-20 03:02:08 UTC,"It's failing with another issue:
FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest)"
1820828,2019-03-26 11:35:53 UTC,"I can see this again, and just like what happened here a re-run make this go away.
Maybe the test is not very robust?"
1820828,2020-05-21 01:49:42 UTC,"This issue can be found on T-amd64 in this cycle (3.13.0-177.228) on two different amd64 node ""onibi"" and ""kili"""
1820828,2020-06-23 09:45:04 UTC,This issue can be found on Precise 3.13.0-181.232~12.04.1 i386 with KVM node precise-i386
1820828,2020-06-23 12:49:05 UTC,It looks like this was caused by ubuntu_qrt_kernel_panic test which was executed before the security test.
1820829,2019-05-30 18:24:43 UTC,"Fixed in revision 6695209246ef223856e2f50bf9907133025b707d
https://git.launchpad.net/kicad/patch/?id=6695209246ef223856e2f50bf9907133025b707d"
1820829,2019-05-30 13:01:37 UTC,"There is a easy way: to be able to copy the exported bitmap to the clipboard from the bitmap2component tool.
I'll have a look into that."
1820829,2019-05-30 08:16:26 UTC,I think it makes more sense for this to be simplified to a File > Import > Bitmap... workflow and squash all the intermediate steps.
1820829,2019-05-30 12:38:37 UTC,+1 for Michael's suggestion.  I don't think we need to have a separate tool to import bitmaps.  This could be a window that is a child of pcbnew/modedit
1820832,2020-08-11 21:16:55 UTC,"Hello,"
1820832,2019-11-17 14:57:03 UTC,"Hello,"
1820832,2019-11-17 15:06:45 UTC,"Additionnal note for the previous comment: it also works when Sync to VBlank is enabled (tested with glxgears), but causes tearing for the 60 hz monitor."
1820832,2019-11-17 17:00:11 UTC,Thanks for pointing that out because.... I also had __GL_SYNC_DISPLAY_DEVICE=DP-0 in /etc/environment as completely forgot to mention that in my previous comment to yours here.
1820832,2020-08-12 09:54:35 UTC,Did you see it work on previous ubuntu version (19.10)? Or is 20.04 the first version you tested here?
1820832,2020-10-05 10:57:56 UTC,"dreamcat4,"
1820832,2020-08-17 20:24:29 UTC,"I confirm this issue on Ubuntu 20.04 LTS; Nvidia driver 440.100; Linux kernel 5.4.0-42-lowlatency; GeForce 1060 6GB
Two monitors: LG 27GL850 (144Hz DP connection) and Asus VG248 (60 Hz single-link DVI connection, despite display could more)
If the second (slow) display is connected ""effective"" refresh rate on first (fast) display is limited to 60 Hz. I mean effective, despite xrandr shows 140, actual window moving traces, effects in 3D games are similar to 60 Hz, and testufo.com also shows 60Hz. If I disable slow display in nvidia-settings, effective refresh rate (window moving, games) are smooth as supposed to be, and ufotest shows 144 Hz and smooth ufo moving.
I remember that there were no such issues with some previous version of nvidia driver (3xx)"
1820832,2020-09-25 16:32:46 UTC,I've also run into this issue on Pop!_OS 20.04 LTS; Nvidia driver 450.66; Linux kernel 5.4.0-7642-generic; GeForce GTX 1080 8GB; mutter 3.36.4; GNOME Shell 3.36.4.
1820832,2020-09-25 17:35:56 UTC,It would be nice to understand what is going on here. Currently on 19.10 and have not upgraded to 20.04 yet... because of this very same bug! It took so long to get rid of the last time around. Many months.
1820832,2020-10-04 18:09:50 UTC,"OK I have now regression tested on the latest 19.10, with the above ^^software stack. All except incrementing the kernel from 5.8.11 to 5.8.13."
1820832,2019-09-27 23:11:36 UTC,Hello there. Good news for a change:
1820832,2020-08-12 11:46:44 UTC,"Hello, dreamcat4!"
1820832,2019-07-29 21:44:38 UTC,"Good point, then there can be 2 explanations:"
1820832,2019-04-23 02:13:51 UTC,This bug is about Nvidia only so please discuss AMD elsewhere.
1820832,2019-07-29 17:28:24 UTC,I can confirm this bug too. But additionally I have noticed one more interesting fact:
1820832,2019-07-22 13:59:25 UTC,I can also confirm that this bug is still present. I'm on Ubuntu 19.04 with the latest drivers & updates installed.
1820832,2019-05-17 19:22:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820832,2019-04-24 01:27:00 UTC,"Yes, sorry. I am trying to track hundreds of bugs in my head and I don't always remember (or reread) the context of each one every day."
1820832,2019-04-23 13:25:44 UTC,"The original description specifically mentions both Nvidia and AMD cards being affected, as the bug was based on the experiences reported by myself and dreamcat4 in the bug for Mutter capping the FPS to 60."
1820832,2019-07-29 21:09:06 UTC,"well by that logic, then somebody with an amd ryzen APU (such as 3200G or whichever with the integrated Vega graphics). Would also not be affected by this bug."
1820832,2019-04-19 06:53:37 UTC,"For AMD users, I finally managed to get my primary display to correctly update at 144Hz under Xorg by manually enabling TearFree rendering, as described here:"
1820832,2019-03-27 16:17:30 UTC,"> As luck would have it, one user upstream found a solution for NVIDIA documented here:
>
> https://gitlab.gnome.org/GNOME/mutter/issues/503#note_463305
>
"
1820832,2019-03-20 09:01:29 UTC,"Sure, here's my Xorg.log"
1820832,2019-03-20 01:54:38 UTC,"dreamcat4,"
1820832,2019-03-20 01:52:49 UTC,This is a bug/limitation of the graphics driver itself. So I will reassign this bug to NVIDIA.
1820832,2019-03-19 12:56:03 UTC,Just confirming that this issue affects me also.  Here's my post from the other other bug:
1820832,2019-03-19 12:04:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820837,2019-03-19 18:21:41 UTC,"Right. PR welcome.
This affects not only etree.parse() but also etree.iterparse(), XSLT(), XMLSchema(), etc. I think this is best implemented in the _encodeFilename() helper function in apihelpers.pxi, with adaptations wherever it's used since it's usually preceded by a type test using _isString(). There should probably be a new type check function that detects path objects in Python versions that support it."
1820841,2019-05-22 23:55:53 UTC,This seems to be caused by only flipping the y-axis of the curves on the front layer. The attached patch flips all the curves (no matter the layer) to fix this. It is based on the current 5.1 branch.
1820841,2019-05-23 17:00:58 UTC,This seems to work correctly.  I'm not sure the original purpose of only flipping the module edge cuts from the top.
1820841,2019-05-29 03:41:24 UTC,"@JohnBeard - ping if you have a chance to review this one, otherwise it looks good from my end."
1820841,2019-05-30 02:43:39 UTC,"Fixed in revision 55261eb223e0ec0ebda381970d96d2985b52f20c
https://git.launchpad.net/kicad/patch/?id=55261eb223e0ec0ebda381970d96d2985b52f20c"
1820843,2019-03-19 23:12:11 UTC,"@Evan - could you please edit and remove all commands in the above snapfile.yaml except the first one. They were just commands I was playing around with and some don't compile, so are unnecessary to the problem at hand."
1820843,2019-04-17 18:10:08 UTC,"IIRC, the pip/requirements issue was fixed in 3.3, is this still reproduceable for you?"
1820843,2020-11-29 08:09:55 UTC,"I get this issue (it seems it's the same) with snapcraft 4.4.2:
""""""
Launching a VM.
                                                                                                                                                                                                                                          Skipping pull a1fbox (already ran)
Skipping pull blocker (already ran)
Building a1fbox
/root/parts/a1fbox/install/usr/bin/python3: No module named pip
Failed to run '/root/parts/a1fbox/install/usr/bin/python3 -m pip wheel --no-index --find-links /root/parts/a1fbox/python-packages --wheel-dir /tmp/tmpmx7gav05 --requirement /root/parts/a1fbox/build/requirements.txt': Exited with code 1.
Run the same command again with --debug to shell into the environment if you wish to introspect this failure.
""""""
doing a snapcraft clean fixes it."
1820847,2019-04-12 22:42:21 UTC,"I think I see how this could happen for swift3: When doing a ?encoding-type=url query, we used to quote() darn near everything [1] -- so the client would get back a response containing something like"
1820847,2019-04-16 06:21:17 UTC,"Thanks, Tim.
I am able to reproduce the issue with s3api and swift 2.19 (rocky)."
1820854,2019-03-19 14:06:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820859,2021-02-05 10:13:31 UTC,Ubuntu 20.10
1820859,2020-12-22 01:25:38 UTC,"Hello, what additional info can I provide to help diagnose the issue? I get these segfaults sometimes right after boot. Not sure if anything is broken though since the system works fine (aside from other segfaults/crashes)."
1820859,2020-07-10 10:41:50 UTC,"""nautilus --version"" crashes always (vanilla Ubuntu 2020.04 desktop installation)."
1820859,2020-05-18 07:44:37 UTC,On focal doing 'nautilus --version' is enough to trigger the issue
1820859,2019-06-14 06:42:16 UTC,How to reproduce this ?
1820859,2019-06-04 20:00:16 UTC,"Khurshid, could you have a look, it seems like you are the one who rebased the patch for the new nautilus"
1820859,2019-06-04 19:57:05 UTC,The issue seems to be due to a distro patch (19_unity_open_location_xid) and started in disco so maybe a rebasing issue
1820859,2019-06-14 15:42:03 UTC,Here is the Stacktrace from the Error Report:
1820861,2019-04-30 15:13:37 UTC,The issue got fixed upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/commit/f75c3a84
1820861,2019-05-29 11:52:25 UTC,This bug was fixed in the package gnome-control-center - 1:3.32.2-1ubuntu2
1820861,2019-05-30 10:47:53 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1820861,2019-06-05 15:22:05 UTC,"There are no report from 3.32.2 versions, also using 1:3.32.2-0ubuntu1 on disco shows no sign of visible regression"
1820861,2019-06-06 09:17:15 UTC,"The verification of the Stable Release Update for gnome-control-center has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820861,2019-06-06 09:27:15 UTC,This bug was fixed in the package gnome-control-center - 1:3.32.2-0ubuntu1
1820862,2019-07-02 16:48:33 UTC,Reported upstream https://gitlab.gnome.org/GNOME/gnome-control-center/issues/604
1820866,2021-01-14 15:29:15 UTC,Ubuntu 20.04 does not have this problem any more. I did a few tests (even shutting down the server for which I had a share bookmarked). The various different scenarios I tested all behaved as I would expect.
1820866,2021-01-11 09:06:52 UTC,Please check if the bug still occurs in a newer version of Ubuntu:
1820866,2021-01-11 08:54:02 UTC,This makes me dought do Ubuntu devs actually use Ubuntu.
1820866,2020-01-22 14:40:29 UTC,"Not sure if this bug is still active, but I can confirm this behaviour on both 18.04 and 19.10 and also that it is (in my case) caused by a NFS share from /etc/fstab that disappeared without being unmounted first."
1820866,2020-01-22 14:40:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820866,2019-03-20 02:34:54 UTC,It looks like the file dialog is being slowed by scanning network shares. Please try removing those (temporarily) and tell us if the problem goes away.
1820866,2020-07-12 21:34:19 UTC,I have the same problem when running gedit on Windows 10.
1820867,2019-05-19 04:17:59 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1820867,2019-03-19 16:19:58 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We noticed that you were installing the LTS version of Ubuntu using an older version of the installation media.  The latest point release of 14.04 is 14.04.5. Please try installing from that version of the installation media and see if that resolves your issue. Thanks in advance!
1820868,2019-05-14 19:04:02 UTC,This bug was fixed in the package linux-snapdragon - 4.15.0-1053.57
1820868,2019-05-14 19:00:55 UTC,This bug was fixed in the package linux-meta - 4.15.0.50.52
1820868,2019-10-29 11:13:40 UTC,This bug was fixed in the package linux-hwe-edge - 5.3.0-19.20~18.04.2
1820868,2019-05-14 22:54:15 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820868,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1820868,2019-04-13 07:57:01 UTC,This bug was fixed in the package linux-meta - 5.0.0.11.12
1820868,2019-05-06 12:43:18 UTC,"bionic/linux kernel 4.15.0-49.53 currently in -proposed is not producing the snapdragon binaries:
https://launchpad.net/ubuntu/+source/linux/4.15.0-49.53"
1820868,2019-04-29 16:03:46 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1820868,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1820868,2019-05-06 12:47:28 UTC,Additional notes on verification:
1820872,2019-03-19 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820872,2019-04-26 14:31:46 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1820872,2019-05-14 19:08:52 UTC,This bug was fixed in the package linux - 4.4.0-148.174
1820873,2019-03-19 17:38:24 UTC,"Confirmed, you can create multiple booking resources with the same name and owner.  Also, the UI should fail with a helpful error message when a user tries to make duplicative resources."
1820875,2019-06-06 11:42:27 UTC,This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.
1820877,2019-03-20 13:45:30 UTC,"Thank you for reporting this bug.  Could you please detail what version of vmware you are using (as well as which client you are using to perform the operation), the image URL, and the exact error you are seeing with steps to reproduce?"
1820877,2019-05-20 04:17:22 UTC,[Expired for cloud-images because there has been no activity for 60 days.]
1820882,2019-07-09 13:17:22 UTC,Has anyone from starlingx tested the proposed fix for bug 1821755 (of which this bug is a duplicate?): https://review.opendev.org/#/c/651969/ (note that the patch [PS10] is currently failing unit test jobs).
1820882,2019-07-09 02:06:17 UTC,I have test this case in stx.2.0 tag. And the issue still remains. I have post a patch to fix this issue to nova upstream and the patch is still in review.
1820882,2019-07-03 16:57:32 UTC,"I think this LP is duplicated to https://bugs.launchpad.net/bugs/1821755, which was confirmed a Nova upstream issue.
@Ghada, if you don't mind, I can duplicate this one to 1821755."
1820882,2019-07-08 16:10:20 UTC,"The live-migrations on 2 VMs were taking place within short interval (< 2 mins), and it triggered a Nova upstream issue confirmed in https://bugs.launchpad.net/bugs/1821755."
1820882,2019-03-20 17:42:08 UTC,See https://bugs.launchpad.net/nova/+bug/1820018 for the related Nova upstream bug
1820882,2019-03-20 17:25:38 UTC,This is a nova issue and will need to be reported as a nova launchpad.
1820882,2019-03-22 18:59:29 UTC,"Marking as release gating for stx given the severity of the issue (live migration not working with anti-affinity groups).
Needs follow-up with the nova community."
1820883,2019-03-20 11:26:34 UTC,"Thank you for your bug report. Confirmed and sent upstream
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/579"
1820885,2019-07-27 18:26:20 UTC,Both DTD validation and XML-Schema validation are implemented in libxml2. There is nothing lxml can do about this.
1820886,2019-05-21 20:06:34 UTC,"Hello João, or anyone else affected,"
1820886,2019-06-06 09:43:50 UTC,This bug was fixed in the package apt - 1.6.11
1820886,2019-06-06 09:44:23 UTC,This bug was fixed in the package apt - 1.2.32
1820886,2019-06-06 09:43:16 UTC,This bug was fixed in the package apt - 1.7.5
1820886,2019-06-05 13:07:17 UTC,For 1.7.5/cosmic:
1820886,2019-05-27 09:42:43 UTC,"Verified again on bionic - 1.6.11, as the previous verification missed the version number."
1820886,2019-05-27 09:17:35 UTC,Verified for 1.7.5 in cosmic:
1820886,2019-05-24 15:29:36 UTC,Verified fix for Xenial:
1820886,2019-05-22 11:01:35 UTC,I confirm the fix works for Bionic.
1820886,2019-05-21 20:09:35 UTC,"Hello João, or anyone else affected,"
1820886,2019-05-21 20:04:51 UTC,"Hello João, or anyone else affected,"
1820886,2019-04-09 18:15:39 UTC,Suggested workaround:
1820886,2019-05-21 15:12:23 UTC,This bug was fixed in the package apt - 1.8.1
1820886,2019-05-07 09:11:56 UTC,"Installed 1.8.1, running reboot as a user is inhibited:"
1820886,2019-05-06 15:24:08 UTC,This bug was fixed in the package apt - 1.8.1+19.10
1820886,2019-05-06 14:54:52 UTC,"Hello João, or anyone else affected,"
1820886,2019-05-03 14:42:01 UTC,OK so where we are right now:
1820886,2019-04-15 08:47:35 UTC,Inhibitor support:
1820886,2019-04-09 21:57:30 UTC,"@juliank The proposed service would reopen LP: #1778219 , just for apt. :-("
1820886,2019-04-09 18:20:56 UTC,Something like that Python script should be enough really to catch most issues:
1820886,2019-03-28 14:14:28 UTC,"This has been on my agenda for quite some time. It means apt will need to talk dbus, and it might need to be able to react to a shutdown notification from dbus, which might get pretty complex, but I have not checked in detail."
1820886,2019-05-21 15:12:30 UTC,"The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820887,2019-11-20 04:32:00 UTC,I think this is similar.
1820887,2019-09-19 19:41:06 UTC,I'm unable to replicate this in 3.3.3 in Chrome.
1820887,2019-03-21 15:31:31 UTC,Here is the promised second screen shot for #4 above.
1820887,2019-03-21 11:18:31 UTC,According to the reporting library it was Chrome.
1820887,2019-03-20 21:06:35 UTC,Thanks for reporting this.  I can't confirm this on Chromium.  Is this only happening in Firefox?
1820887,2019-03-21 15:30:57 UTC,From Reporting library:
1820889,2019-07-13 15:22:55 UTC,"Same for me in Archlinux, but not every time."
1820897,2019-08-10 14:15:06 UTC,This might be the same issue as #1705820 . Randy: could you try applying the patch described in https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1705820/comments/10 and see if that fixes the problem for you?
1820897,2019-10-06 10:06:07 UTC,"Sorry to take so long to get back to you, @ogerlich. I applied the patch, and yes, did confirm that this fixed the problem on updating to version Linux 5.0.0-31-generic x86_64. Than you so much for your help."
1820897,2020-06-23 11:25:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820897,2020-06-23 17:13:34 UTC,"The patch is no longer working. I have been hobbling along with my wired connection for several updates. With the latest upgrade to version 5.3.0-59, I tried to get it working again. I downloaded the module code from"
1820902,2019-07-29 14:29:41 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/673300"
1820902,2019-07-22 13:07:46 UTC,"Initial conclusiont point to a tricky helm-toolkit bug. I got some small guidance on the openstack-helm stash channel, but nothing to point me to a solutiom."
1820902,2019-07-25 13:45:36 UTC,"Indeed is a hard to catch bug in helm-toolkit, I opened an SB on the helm toolkit project
https://storyboard.openstack.org/#!/story/2006278"
1820902,2019-08-01 04:04:54 UTC,"Reviewed:  https://review.opendev.org/673300
Committed: https://git.openstack.org/cgit/starlingx/upstream/commit/?id=b120684a28a5830f5f2579a7a713450aadc134f0
Submitter: Zuul
Branch:    master"
1820903,2019-03-22 08:34:57 UTC,"It seems that you are using a texture file for the MSTS environment that OR does not accept. You may bypass the problem by unchecking the experimental option ""MSTS Environments""."
1820904,2019-03-20 16:39:06 UTC,would it be possible to find out which update fixed this issue and back port to 16.04? Majority of my systems (10+ boxes) are on 16.04 because many things broke (otherwise) on 18.04. I do not plan to upgrade in the next few years.
1820904,2019-05-20 04:17:26 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1820904,2019-03-20 10:01:20 UTC,Thank you for your bug report. What desktop environment do you use? Does this happen on any document? Could you try on newer ubuntu series?
1820904,2019-03-20 16:36:16 UTC,"on another machine running Ubuntu 18.04, the rendering of this PDF looks normal."
1820906,2019-04-14 17:25:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1820909,2019-03-23 00:16:52 UTC,"Hi Brian,"
1820909,2019-05-22 04:17:35 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1820909,2019-03-22 22:59:59 UTC,I'd try testing the latest point release of Ubuntu 18.04 instead of the image that you used. You can find the latest 18.04 iso here:
1820909,2019-03-20 10:00:29 UTC,"Thank you for your bug report, could you give some details on the type of installation/partitionning you did?"
1820909,2019-03-19 20:55:27 UTC,will try again without getting updated packages.
1820909,2019-03-20 12:56:22 UTC,"Hi Sebastien,"
1820910,2019-03-20 00:05:30 UTC,"This has been known for a long time, and the branch syntax-control is addressing this issue (that I wrote in 2015 or so). But this is a significant change enough that it warrants a new minor version of ASDF (so, 3.4), but we are still undermanned to release 3.3.3."
1820910,2019-03-20 00:06:06 UTC,Thanks though for giving a real-life example of the issue being relevant.
1820910,2020-05-20 16:32:14 UTC,Issue now tracked at https://gitlab.common-lisp.net/asdf/asdf/-/issues/31 - this one may be closed.
1820910,2020-05-26 18:27:06 UTC,Closing. See gitlab issue instead.
1820920,2019-03-20 02:47:01 UTC,Can you please explain what kind of problem you are seeing?
1820920,2019-05-19 04:18:10 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1820929,2020-09-29 19:59:12 UTC,"This has been verified successfully on Bionic by @jvosburgh
on a (complex) internal test setup for 3-netdev naming work."
1820929,2020-10-06 08:02:45 UTC,This bug was fixed in the package initramfs-tools - 0.130ubuntu3.11
1820929,2020-10-06 08:02:53 UTC,"The verification of the Stable Release Update for initramfs-tools has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820929,2020-10-07 00:28:25 UTC,I will get some time to test it this week. Are there other packages than initramfs-tools that are deem required  to make net_failover work on Bionic? I recall there's some systemd-udevd level change needed not just initramfs-tools that has to be fixed.
1820929,2020-11-11 00:29:48 UTC,"Si-Wei,"
1820929,2021-01-19 19:11:18 UTC,"Thanks, Jay. Sorry for getting back late."
1820929,2021-01-25 11:28:19 UTC,Marking all other packages/dev release as Invalid.
1820929,2020-09-24 13:55:43 UTC,"Hello Si-Wei, or anyone else affected,"
1820929,2020-10-07 00:59:30 UTC,"Si-Wei,"
1820929,2020-09-23 21:08:05 UTC,"Uploaded initramfs-tools to Bionic.
Attaching the updated debdiff for reference.
(Rebased on top of the more recent -updates.)"
1820929,2020-10-20 22:37:45 UTC,"Jay,"
1820929,2020-08-12 18:33:07 UTC,"Although the debdiff is hereby attached, 3 bugs have fixes carried on such patch - the main work is done on LP ##1879980 (and the other LP handled in this SRU is #1879987) ."
1820929,2019-03-30 00:24:37 UTC,FWIW this is the 'udevadm info' output on the primary slave:
1820929,2019-03-30 00:00:20 UTC,"So what's your opinion for the disposition? I don't mind moving this bug to initramfs-tools, but without having a way to identify the 3-netdev master interface in netplan yaml config, thing still don't work there. I'm not in a position to tell if it's possible for initramfs-tools to remove the ""match by mac"" in the /run/netplan/<interface>.yaml config file."
1820929,2019-03-28 21:50:11 UTC,"Yes, that does explain it."
1820929,2019-03-28 20:05:19 UTC,"Before answering your quesitions, I would wonder what do you know generates the /run/netplan/ens3.yaml file in the first place? This YAML file is not provided by us obviously, the only netplan config we have on the root disk is /etc/netplan/01-netcfg.yaml, derived from the debian installer. The YAML under /run overrides the one under /etc, for the DHCP case, and that's where the odds about the additional udev rule and various config options came from."
1820929,2019-03-28 18:45:55 UTC,I also forgot to mention another entry I see in some of the configs:
1820929,2019-03-28 18:36:43 UTC,All of these values should be coming directly from the netplan YAML. Are all of these options required?
1820929,2020-09-02 14:58:38 UTC,[sts-sponsor]
1820929,2019-03-25 20:42:26 UTC,"Note only DHCP configuration exhibits this particular issue. The cause is that when ""dhcp4"" is set to ""yes"" in the /etc/netplan/*.yaml config file, netplan would generate a temporary per-interface yaml file under /run/netplan, which matches interface using MAC address. While I don't see this specific MAC matching when using static IP configuration."
1820929,2019-03-23 01:16:51 UTC,There's barely anything can be used to distinguish but only the name (or ifindex) itself.
1820929,2019-03-21 19:25:15 UTC,netplan is currently writing about as much as we can for the networkd/udev configs; some values we don't know how to handle at all.
1820930,2019-05-14 22:57:24 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820930,2019-04-24 08:01:51 UTC,This bug was fixed in the package linux-oem - 4.15.0-1036.41
1820930,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1820930,2019-04-23 21:35:02 UTC,This bug was fixed in the package linux - 4.18.0-18.19
1820930,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1820930,2019-04-04 18:03:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1820930,2019-04-04 18:02:20 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1820930,2019-03-27 05:59:50 UTC,Nominated for bionic/oem as well since Hui proposed the patch to bionic/oem.
1820930,2019-03-20 01:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820933,2019-03-21 16:34:40 UTC,Hey Isryu:
1820933,2019-03-27 00:36:09 UTC,"In my case, the subnet option does not show.
What I know about the system is that the version is rocky.
I can try to get the exact git tag or commit hash if it will help."
1820933,2020-03-05 15:44:43 UTC,Revisted see http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-03-05-15.00.log.html
1820933,2020-03-06 01:19:58 UTC,"Hi Isryu,"
1820939,2021-01-28 14:23:14 UTC,"We have also run into this issue, in our case on a stein system. Any use of the glance import functionality (such as by using `web-download` to import directly from a URL) results in the image having `queued` status forever and associated tasks remaining forever in the `pending` state."
1820939,2021-01-28 15:07:09 UTC,This issue has been addressed for the train release (and continues to be supported in victoria) via the os_glance role variable `glance_use_uwsgi` which defaults to True (https://github.com/openstack/openstack-ansible-os_glance/blob/stable/train/defaults/main.yml#L264-L266).
1820939,2021-01-28 16:23:22 UTC,"After discussion in IRC, I believe the situation as I understand it for each release is as follows:"
1820945,2019-05-16 02:52:29 UTC,"AFAICT... this should resolve the issue you are hitting atm
https://review.opendev.org/#/c/658449/"
1820947,2019-06-21 15:25:55 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1820947,2019-06-21 13:48:01 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1820947,2019-03-25 18:21:31 UTC,"Reviewed:  https://review.openstack.org/644727
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=f7bae9b7ff453e113ed87eb46e0760a4cd518292
Submitter: Zuul
Branch:    stable/queens"
1820947,2019-03-20 04:21:23 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/644726"
1820947,2019-03-20 04:21:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/644727"
1820947,2019-03-21 20:25:10 UTC,"Reviewed:  https://review.openstack.org/644726
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=4bd3d245cf68702f96b75ad3bb37fcd6caa3cd29
Submitter: Zuul
Branch:    stable/rocky"
1820953,2019-03-20 07:08:11 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1820953,2019-03-22 22:54:07 UTC,"The documentation is wrong. There are three dots in the Wi-Fi settings menu near the close, minimize, maximize buttons. If you click that the ""Connect to Hidden network"" option is revealed."
1820953,2019-07-12 12:42:34 UTC,"19.10 QA-test (live) on
motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)"
1820953,2019-12-02 00:26:40 UTC,"Ubuntu 20.04 qa-test, (following part of comments)
sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT)
this crapbook has no ethernet so I try and connect hidden wpa2 wifi, no ""more"" option as per instructions in https://help.ubuntu.com/stable/ubuntu-help/net-wireless-connect.html.en"
1820957,2019-08-13 15:56:23 UTC,This bug was fixed in the package dpdk - 18.11.2-1ubuntu0.19.04.1
1820957,2019-08-13 15:46:22 UTC,"The verification of the Stable Release Update for dpdk has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820957,2019-08-05 12:43:31 UTC,"I checked installs with proposed enabled.
Now rdma-core is correctly pulled in on installs."
1820957,2019-08-05 09:17:18 UTC,"Hello Christian, or anyone else affected,"
1820957,2019-08-05 08:25:00 UTC,"An upload of dpdk to disco-proposed has been rejected from the upload queue for the following reason: ""Attached bug LP: #1784816 seems to point to a previous (different) stable version update (already released). Could we get a new bug for the new update, with proper release notes linked in?""."
1820957,2019-05-17 05:13:28 UTC,"Fixed in Eoan, forgot the bug ref :-/"
1820957,2019-04-17 07:48:44 UTC,"Fixed in Debian but not breaking the freeze in Disco.
This will be synced into 19.10 later on and then considered for an 19.04 SRU."
1820957,2019-03-20 12:04:52 UTC,After discussion with Luca I file a bug for rdma-core and put Luca as well as Thomas Monjalon on CC to get their opinion on all of this.
1820957,2019-03-20 08:51:12 UTC,"To underline here a message I just got from MLX:
""rdma-core is a must to be able to use MLX PMD's"""
1820957,2019-03-20 07:25:33 UTC,"I'll discuss that with Luca on Thursday, he has MLX in his setups as well."
1820957,2019-07-31 05:12:20 UTC,"Uploaded to -unapproved as part of the Stable release.
Adding SRU template here."
1820961,2019-03-20 08:12:46 UTC,testing https://review.openstack.org/#/c/644785/
1820961,2019-03-20 10:35:35 UTC,with https://review.openstack.org/#/c/644785/ we correctly get past this error.
1820967,2019-09-20 08:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820967,2019-09-19 14:54:41 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1820967,2019-09-20 07:31:37 UTC,This seems to be an issue with the kernel and not an issue with MAAS directly. Which Ubuntu release is set as the commissioning release on the Global Settings page? If you can provide the full console log of the boot that would be helpful as well.
1820967,2019-11-20 04:17:18 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1820976,2020-04-09 09:53:14 UTC,The ceph updates in proposed pockets include the backported fixes for this issue.
1820976,2019-07-03 10:40:26 UTC,"Backports are inflight upstream, will be picked up in the next round of stable updates."
1820976,2020-04-16 09:04:08 UTC,SRU updates for 13.2.8 and 14.2.8 have been released so marking this as 'Fix Released'
1820976,2019-03-29 13:13:43 UTC,Upstream ticket: http://tracker.ceph.com/issues/39031
1820976,2019-03-29 06:27:26 UTC,https://review.openstack.org/#/c/648618/
1820976,2019-04-03 10:56:58 UTC,"Reviewed:  https://review.openstack.org/648618
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-rbd-mirror/commit/?id=cc6897b738d65ec21d10ad596be4138e96990211
Submitter: Zuul
Branch:    master"
1820977,2019-03-20 09:16:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/644797"
1820977,2019-03-20 22:52:46 UTC,"Reviewed:  https://review.openstack.org/644797
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=8fd27641b030df92a903006a558a88082efce21c
Submitter: Zuul
Branch:    master"
1820979,2019-03-21 08:39:20 UTC,"This bug does not contain enough information to evaluate what may have happened. Can you please add more info about what steps were taken and also run ""apport-collect 1820979""."
1820979,2019-03-21 11:44:08 UTC,"I try, but I have ""No referer header"" error message in browser when login to launchpad.
It ask ""computer wants access to your launchpad account"", I choose allow access to this computer, then it show me "" 403 forbidden"" and this error about referer. Browser installed on this computer is Lynx."
1820979,2019-04-06 14:13:23 UTC,Looks like this bug fixed in latest updates. Thank you.
1820982,2019-03-20 09:54:36 UTC,"This is a bit special as nose was already in main for quite some time.
It was in main up until (including) Xenial especially since back in the day build-dependencies needed to be in main as well."
1820982,2019-03-20 09:55:28 UTC,"I couldn't find the old bug for sure, I think it might be bug 493594 where it was promoted as build-dependency."
1820982,2019-07-03 05:40:33 UTC,"After evaluating dependencies, required further changes and mostly maintainability for security and packaging it was decided there are too many concerns - not about any single package in particular, but the overall Mailman3 stack - about the ability to maintain and monitor it as well as we need it for support in main."
1820983,2019-03-27 23:36:13 UTC,The completion of this bug is currently blocked on this issue:
1820983,2019-03-21 14:03:35 UTC,"Hi Mark,"
1820984,2019-03-25 22:11:22 UTC,"As per discussion over IRC, the reason why this machine was failing to PXE boot is because there was a device already added with the same MAC address."
1820984,2019-03-31 10:48:17 UTC,"Could we make sure there is an entry in the relevant logs, as well as an
entry in the history of events on the device, reflecting this?"
1820989,2019-03-20 17:10:09 UTC,I happened to just run across this error myself.
1820989,2019-03-20 17:20:22 UTC,"Hi Eric,"
1820989,2019-03-20 18:01:48 UTC,I just got around to doing the same here and it solved the problem on my end too. :)
1820989,2019-03-20 18:39:28 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/644966"
1820989,2019-03-20 18:50:33 UTC,"I submitted a patch, we will see if it gets approved."
1820989,2019-03-25 08:49:32 UTC,"Change abandoned by Marcin Juszkiewicz (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/644966
Reason: https://review.openstack.org/#/c/641569/ fixed that"
1820990,2019-05-14 22:57:31 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1820990,2019-04-24 08:01:51 UTC,This bug was fixed in the package linux-oem - 4.15.0-1036.41
1820990,2019-04-23 21:35:02 UTC,This bug was fixed in the package linux - 4.18.0-18.19
1820990,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1820990,2019-04-04 18:04:22 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1820990,2019-04-04 18:02:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1820990,2019-03-20 10:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1820990,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1820996,2019-03-20 12:28:12 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/644848"
1820996,2019-03-20 18:45:12 UTC,"Reviewed:  https://review.openstack.org/644848
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=5ab3b3de04809153d004e600b5f5293f02ec5f3c
Submitter: Zuul
Branch:    stable/rocky"
1820996,2019-03-21 09:54:47 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/645088"
1820996,2019-03-21 16:56:45 UTC,"Reviewed:  https://review.openstack.org/645088
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=87cef2ea1db6efc420a853d5c3b573960e032747
Submitter: Zuul
Branch:    stable/queens"
1820996,2019-06-21 13:46:35 UTC,This issue was fixed in the openstack/tripleo-common 9.6.0 release.
1820996,2019-06-21 15:24:28 UTC,This issue was fixed in the openstack/tripleo-common 8.7.0 release.
1821008,2019-09-02 08:01:29 UTC,I cannot reproduce this under stress locally. It must have been fixed as part of other work.
1821009,2019-03-22 08:29:47 UTC,You must attach the file openrailslog.txt that you get on the desktop to provide useful info to understand your problem.
1821009,2019-05-22 04:17:16 UTC,[Expired for Open Rails because there has been no activity for 60 days.]
1821012,2019-03-20 19:43:16 UTC,"The snap is now working. (In other words, not able to reproduce.)
I'm not sure what made the change but I did reboot several times."
1821012,2019-03-20 16:07:54 UTC,Being discussed on https://forum.snapcraft.io/t/cant-run-gnome-system-monitor-ubuntu-18-04/10495/1
1821014,2019-03-21 11:00:10 UTC,"It crashed again, attaching a newer backtrace (this time an all thread one)."
1821014,2019-03-21 15:39:44 UTC,Sorry - cannot reproduce this - but you are right this is somewhere in clutter/mutter .  Can you tell me a bit more about your setup.
1821014,2019-03-22 14:26:39 UTC,"Well it is a real machine, the apport report (the attached txt files) are containing everything."
1821014,2019-04-04 07:43:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821014,2019-04-04 07:44:22 UTC,Tracking in: https://errors.ubuntu.com/problem/7700ef9eb2ee16eefb57a28cc0d72a9b11528630
1821014,2020-01-24 09:08:25 UTC,It appears the crash stopped happening universally some time after 19.04 and before 19.10.
1821015,2019-03-25 15:56:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647519"
1821015,2019-03-27 16:14:14 UTC,"Reviewed:  https://review.openstack.org/647519
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=44490142be5c20389703aeed54edca28f27c43c0
Submitter: Zuul
Branch:    master"
1821015,2019-04-02 21:12:13 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/649454"
1821015,2019-04-03 19:59:36 UTC,"Reviewed:  https://review.openstack.org/649454
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0fd77f3f658ea3b6e44a7c446f95be9d4c8c8b13
Submitter: Zuul
Branch:    stable/stein"
1821015,2019-04-05 01:38:37 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc2 release candidate.
1821015,2019-09-27 09:05:33 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1821016,2019-05-22 04:17:22 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1821016,2019-05-22 04:17:27 UTC,[Expired for neutron because there has been no activity for 60 days.]
1821016,2019-03-22 18:15:14 UTC,"hi can you provide addtional logs
VirtualInterfaceCreateException can happen for several reasons.
it could have been a time out waiting for a vif-pluuged event
it could have been a db conflict."
1821020,2019-06-12 19:35:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821023,2019-07-12 15:34:24 UTC,Hello
1821023,2019-03-20 14:56:40 UTC,"Simple test:
Core 16 system:"
1821023,2019-03-20 15:53:48 UTC,"I see the same issue in the reverse case, Ubuntu Core 18 system and a snap with a core16 base. Even more, it looks like /lib/firmware is also bad for snaps with core18 base in UC18."
1821023,2019-03-20 16:11:00 UTC,"you first case (core 18 with core 16 base) is aligned with generic
statement at the end of the description"
1821023,2019-03-21 17:28:09 UTC,"Please note that even if the files are available in the snap's runtime at a predictable location, we will not typically want snaps to be able to load firmware themselves for all the reasons that we don't want them to load kernel modules themselves. We can consider adding a firmware-control interface that allows it as an escape hatch, but I'd rather see either the gadget snap add support for this and/or a firmware backend is created that functions like the kmod one, where we can have snapd load firmware on behalf of the snap. Typical snaps shouldn't be expected to load firmware to function. Something else might be needed based on requirements."
1821023,2019-03-21 17:52:13 UTC,"correct, I'd still expect confinement limit what can be actually done.
In use case I have found, snap is using ifconfig, and has all needed network control plugs.
It was simple call ""ifconfig wlan1 0.0.0.0"" which was failing. I'm not sure if ifconfig was loading firmware as I assume it should have been loaded by then, or if it parses firmware file for some information, either way it was failing as it was unable to locate the firmware.
Once firmware file was there there was no confinement denial, so I assume it was not doing anything unusual."
1821023,2019-03-21 18:16:49 UTC,The problem I have seen is that the first usage from userspace after boot of some HW triggers loading the firmware for that device. It is not the snap explicitly asking the kernel to load FW. The issue is that the kernel tries to get the firmware files looking at the filesystem layout seen by the process calling the kernel.
1821023,2019-06-17 18:07:24 UTC,Is this slated to be fixed in 2.39.2 or has this now slipped to 2.40?
1821023,2019-07-12 15:47:04 UTC,I sent a proposal to fix this https://github.com/snapcore/snapd/pull/7104
1821026,2020-02-21 01:47:18 UTC,Joseph Richard will take this over as per agreement with Yong Hu
1821026,2019-12-20 03:01:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/700100"
1821026,2019-08-23 17:47:24 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1821026,2019-12-18 11:57:57 UTC,"coredns is by default configured to use the proxy plugin with resolv.conf as the proxy target.  Since resolv.conf has both dnsmasq (floating mgmt IP) and the public DNS servers.  The default policy for selecting a server for name resolution is ""random"" [1], therefore it is possible that occasionally the request will fail (and be cached) when resolving DNS entries that are only resolvable via dnsmasq (host names).  Furthermore, in a multi-node system, there are multiple instances of coredns that are used, each with the above random behavior."
1821026,2019-12-18 08:46:44 UTC,"Hi matt,
I tried to verify your submitted, but the test show all DNS resolutions that are not within k8s will go through dnsmasq.
the coredns-resolv.conf file show as below.
----------------------------------------------------------------------------------
[sysadmin@controller-0 ~(keystone_admin)]$ cat resolv.conf # this file copy from coredns pod.
nameserver 192.178.204.2 # dnsmasq listen on 192.178.204.2:53
nameserver 10.248.2.1
----------------------------------------------------------------------------------
the coredns will use dnsmasq as a upstream dns server when resolving domain that not within k8s.
the host interface also can receive some dns require when tupdump listen to 192.178.204.2:53.
...
08:41:35.573214 IP controller-1.45569 > controller.domain: 3673+ A? compute-1. (27)
08:41:35.573350 IP controller.domain > controller-1.45569: 3673* 1/0/0 A 192.178.204.39 (43)
..."
1821026,2020-05-20 20:47:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/729758"
1821026,2019-12-19 02:13:15 UTC,"Hi all,"
1821026,2020-06-02 19:15:49 UTC,"Reviewed:  https://review.opendev.org/729758
Committed: https://git.openstack.org/cgit/starlingx/ansible-playbooks/commit/?id=7ecbdadbfb33f407d87e5eb4458e92b86c1c6fb7
Submitter: Zuul
Branch:    master"
1821026,2020-06-19 18:58:38 UTC,"Reviewed:  https://review.opendev.org/736797
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=7639db0d71f53c147031c7edbfd530530a496cd6
Submitter: Zuul
Branch:    master"
1821026,2020-06-09 16:00:18 UTC,"Change abandoned by Matt Peters (<email address hidden>) on branch: master
Review: https://review.opendev.org/700100
Reason: This has already been fixed by:
https://review.opendev.org/#/c/729758/"
1821026,2020-06-12 03:08:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/735278"
1821026,2020-06-18 18:34:48 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/736797"
1821026,2020-06-18 18:37:05 UTC,"Change abandoned by Joseph Richard (<email address hidden>) on branch: master
Review: https://review.opendev.org/735278
Reason: Ran into issues with update to handle with simplex upgrades.  Abandoning and moving this change to an upgrade script.
See https://review.opendev.org/#/c/736797/"
1821026,2020-06-21 00:20:43 UTC,"Fixes are merged in stx master and will be included in the stx.4.0 release. Given no users have raised an issue with this when using stx.3.0, the plan is not to port back the changes due to complexity."
1821026,2020-10-13 13:55:56 UTC,"TC: test_vm_with_config_drive, all passed on recent loads."
1821026,2020-11-16 21:10:30 UTC,"Related fix proposed to branch: f/centos8
Review: https://review.opendev.org/762919"
1821026,2020-06-02 22:26:41 UTC,"Reviewed:  https://review.opendev.org/732910
Committed: https://git.openstack.org/cgit/starlingx/stx-puppet/commit/?id=9dc80285641d03e4abf7a2469c0a19e6f557d444
Submitter: Zuul
Branch:    master"
1821026,2019-12-12 14:44:17 UTC,"As per review in the stx networking team meeting (2019-12-12), we agreed that this bug should still be fixed for stx.3.0, so raising the priority to High as only high priority bugs are considered for cherry-picking in maintenance releases."
1821026,2019-08-02 12:04:38 UTC,"@Peng Peng
Hi, what your operation in ""- Add test data to config drive on vm"". I create an instance with this command:
""nova boot --nic net-id=d84f5dc2-26fd-41fa-a673-b502a0d0de43 --image 7f5915c0-ffcb-489e-b706-1bd38079bd74 --flavor 36d5ae34-8668-4efb-8bc4-2c98972fc217 --config-drive true --admin-pass Fh123456  VM-1"""
1821026,2019-11-25 09:23:43 UTC,"@fupingxie, could you please try with the latest build with train patch (e.g. ISO after 20191115) to see if you can reproduce this issue? Thanks!"
1821026,2019-03-20 17:11:41 UTC,Marking as release gating; requires investigation related to the VIM. Issue appears to be introduced recently.
1821026,2019-03-28 19:23:24 UTC,"The VIM is attempting to live migrate the instances, which is supported for instances with a config drive attached. Nova accepts the live migration request, but then the live migration fails:
2019-03-20T11:17:10.609 controller-1 VIM_Thread[81893] INFO _instance_director.py.151 Instance action allowed for tenant2-config_drive-5, action_type=live-migrate
2019-03-20T11:17:10.613 controller-1 VIM_Thread[81893] DEBUG _instance.py.1933 Live Migrate instance tenant2-config_drive-5.
2019-03-20T11:17:10.613 controller-1 VIM_Thread[81893] INFO _instance_state_initial.py.36 Exiting state (initial) for tenant2-config_drive-5.
2019-03-20T11:17:10.613 controller-1 VIM_Thread[81893] INFO _instance_state_live_migrate.py.28 Entering state (live-migrate) for tenant2-config_drive-5.
2019-03-20T11:17:10.614 controller-1 VIM_Thread[81893] DEBUG _instance_task_work.py.131 Live-Migrate-Instance for tenant2-config_drive-5.
2019-03-20T11:17:10.651 controller-1 VIM_Event-Log_Thread[82063] INFO fm.py.379 Generated customer log, fm_uuid=5f2cfded-3e11-45cc-967e-415780dd6e09.
2019-03-20T11:17:10.733 controller-1 VIM_Event-Log_Thread[82063] INFO fm.py.379 Generated customer log, fm_uuid=f754ad66-675d-4b75-b381-5647e46da715.
2019-03-20T11:17:10.811 controller-1 VIM_Thread[81893] DEBUG _vim_nfvi_events.py.235 Instance state-change, nfvi_instance={'attached_volumes': [], 'live_migration_timeout': None, 'name': u'tenant2-config_drive-5', 'recovery_priority': None, 'tenant_id': '018a4f4f-b194-48ba-9d4b-dec5205f280f', 'avail_status': [], 'nfvi_data': {'vm_state': u'active', 'task_state': u'migrating', 'power_state': ''}, 'live_migration_support': None, 'instance_type': None, 'oper_state': 'enabled', 'host_name': u'compute-2', 'admin_state': 'unlocked', 'action': 'migrating', 'image_uuid': None, 'uuid': u'293dbb8b-b3f3-4162-9cae-c328b5852ae5'}.
2019-03-20T11:17:10.815 controller-1 VIM_Thread[81893] INFO _instance_state_live_migrate.py.114 Live-Migrate starting for tenant2-config_drive-5.
2019-03-20T11:17:10.815 controller-1 VIM_Thread[81893] INFO _instance_director.py.1601 Instance tenant2-config_drive-5 has recovered on host compute-2.
2019-03-20T11:17:10.815 controller-1 VIM_Thread[81893] INFO _instance_director.py.1591 Instance tenant2-config_drive-5 state change notification.
2019-03-20T11:17:10.827 controller-1 VIM_Thread[81893] DEBUG _instance_task_work.py.110 Live-Migrate-Instance callback for tenant2-config_drive-5, response={'completed': True, 'reason': ''}.
2019-03-20T11:17:10.827 controller-1 VIM_Thread[81893] DEBUG _instance_tasks.py.122 Task (live-migrate-instance_tenant2-config_drive-5) complete.
2019-03-20T11:17:10.827 controller-1 VIM_Thread[81893] DEBUG _instance_state_live_migrate.py.99 Live-Migrate inprogress for tenant2-config_drive-5.
2019-03-20T11:17:10.857 controller-1 VIM_Event-Log_Thread[82063] INFO fm.py.379 Generated customer log, fm_uuid=d252c539-3bb9-4ee4-a59d-3629a42900d4.
2019-03-20T11:17:10.858 controller-1 VIM_Alarm_Thread[82065] INFO fm.py.180 Raised alarm, uuid=541557d8-8658-428d-949a-176a024f38c7, fm_uuid=0d2345c4-431a-460c-ba0f-ba8fe7b8d0f0.
2019-03-20T11:17:11.832 controller-1 VIM_Thread[81893] INFO _vim_nfvi_audits.py.873 Au..."
1821026,2019-04-03 19:20:44 UTC,From Peng's latest reproduction this looks to be an issue with nova not being able to resolve the compute hostname.
1821026,2019-04-08 23:41:49 UTC,Did some investigation of the could not resolve hostname issue in nova.
1821026,2019-05-13 17:38:27 UTC,"still failing in regression on load 20190508T013000Z
@ [2019-05-11 17:39:17,336] 'system host-lock compute-0'
@[ 2019-05-11 17:39:23,884]Send 'system host-show compute-0'
vim_progress_status | Migrate of instance tenant2-config_drive-1 from host compute-0 failed."
1821026,2019-06-25 22:28:46 UTC,"Issue was reproduced on
Lab: WCP_113_121
Load: 20190624T233000Z"
1821026,2019-06-26 17:59:40 UTC,"Easily reproduceable Build ID: 20190622T013000Z
{lab wp_3-7 nova/test_config_drive.py::test_vm_with_config_drive}"
1821026,2019-11-29 15:59:57 UTC,"Issue was reproduced on train
2019-11-21_20-00-00
wcp_3-6"
1821026,2019-06-26 18:27:13 UTC,attaching output of the ProcessExecutionError in nova compute logs for the failing instance edb6ee9d-8e3b-4497-9114-ef44f345b1c0
1821026,2019-07-18 19:04:00 UTC,"Fails in regression tests
Lab: wcp_63_66
Build ID: 20190713T013000Z
FAIL	20190714 18:36:22	testcases/functional/nova/test_config_drive.py::test_vm_with_config_drive"
1821026,2019-07-19 02:28:09 UTC,"Yesterday i tried to reproduce the problem in a All-in-one duplex R2.0 system, but not. So I'm trying to add a separate compute-node to reproduce the problem."
1821026,2019-07-22 01:30:43 UTC,"I tried to add a compute node for All-in-one duplex. However, when I have added, nothing service run at the compute node. Here is my operation:
1. add a compute host via portal
2. assign an new interface as datanetwork, and assign mgmt and cluster-host using one interface, via portal
3. unlock the compute node"
1821026,2019-07-25 02:56:54 UTC,"when i added compute nodes and apply helm-charts-stx-openstack-centos-dev-latest.tgz, I got this error in stx-openstack-apply.log:
Timed out waiting for jobs (namespace=openstack, labels=()). These jobs were not ready=['neutron-db-sync', 'nova-cell-setup']"
1821026,2019-08-05 01:21:53 UTC,"@Peng Peng
Here is my operation, but I can not reproduce your problem:
1. careat an VM:
nova boot --nic net-id=d84f5dc2-26fd-41fa-a673-b502a0d0de43 --image adcca643-ba09-437a-a966-9d486bcb782c --flavor 36d5ae34-8668-4efb-8bc4-2c98972fc217 --config-drive true --admin-pass Fh123456 --user-data test.config xiexie-5
and this is mu test.config:
chpasswd:
    list: |
        root:rootroot
        centos:centos
    expire: false
ssh_pwauth: yes"
1821026,2019-08-12 19:18:35 UTC,Our TC steps:
1821026,2019-07-12 19:03:06 UTC,"In order to be able to consistently resolve internal host names (those that are only resolvable by dnsmasq), the coredns configuration should be updated to use the dnsmasq floating IP rather than referencing resolv.conf which also has the external DNS servers listed.  This will ensure all DNS resolutions that are not within the K8s cluster will go through dnsmasq running on the controllers."
1821027,2019-04-24 11:34:14 UTC,"Hi Clement Yuan,"
1821027,2019-04-17 03:58:22 UTC,"Hello,
It looks like this fwupd.service issue cannot be 100% reproduced. It will just gone after reboot for this laptop at hand. I will change the title here."
1821027,2019-04-24 14:08:50 UTC,"Hi,"
1821027,2019-04-13 04:29:29 UTC,"I expected to boot within 20-30 sec. Why?
My old laptop G50-80 i7, 8GB DDR3, SSD take less than 30 sec. average boot time is 15 sec."
1821027,2019-04-27 02:12:42 UTC,"Reboot without haveged is 925.
Reboot with haveged is 1951."
1821027,2019-04-26 11:18:51 UTC,It is a bit odd to see this with older kernel.
1821027,2019-04-24 14:38:25 UTC,"All the attachments files from kernel ""4.15.0-42"" Same problem with older kernel ""4.15.0-20""."
1821027,2019-04-13 04:25:45 UTC,"On the first day using this laptop, I try to fix the boot time problem. Once you blacklist ""thunderbolt_power;thunderbolt"" in fwupd, it improve boot time. But it still take 1 mins to boot."
1821027,2019-03-20 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821027,2019-04-11 12:01:02 UTC,"I already install proprietary driver. I even try to use Nvidia X Server Settings switching between ""Nvidia (Performance Mode)"" and ""Intel (Power Saving Mode)""."
1821027,2019-04-08 09:33:26 UTC,"Grabbed a Dell G7 7588 (GTX1060), I can see the following behaviour (without the proprietary NVIDIA driver):"
1821027,2019-04-02 14:10:45 UTC,"This is my new laptop. I installed ubuntu 18.04 and keep on update to the latest kernel.
Until today, I take more than 1 min to boot up."
1821027,2019-04-02 07:13:12 UTC,"Hmm, there aren't much information in the kern.log."
1821027,2019-03-21 12:31:36 UTC,Here is the attached systemd-analyze blame output file.
1821027,2019-03-21 09:21:10 UTC,What's the output of `systemd-analyze blame`?
1821027,2019-03-20 15:12:31 UTC,"Startup finished in 8.017s (firmware) + 8.264s (loader) + 34.077s (kernel) + 9.694s (userspace) = 1min 54ms
graphical.target reached after 9.427s in userspace"
1821027,2019-04-12 12:47:46 UTC,"OK, I have this tested again with OS installed on the NVME."
1821028,2020-04-08 13:40:03 UTC,"Reviewed:  https://review.opendev.org/716928
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=e03a664f681834d740492cfbbe6e4b96ec19e57a
Submitter: Zuul
Branch:    stable/20.02"
1821028,2020-04-02 10:49:12 UTC,"Fix proposed to branch: stable/20.02
Review: https://review.opendev.org/716928"
1821028,2020-03-23 16:27:01 UTC,"Reviewed:  https://review.opendev.org/713449
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=cb0f757f185565bcec1179087be037d596e9885a
Submitter: Zuul
Branch:    master"
1821028,2020-03-17 13:56:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/713449"
1821028,2020-03-16 09:00:08 UTC,A context manager that uses 'get_local_osd_ids' and determines the status of each OSD pre-restart and then waits for that status post restart would appear to be a nice solution to this issue.
1821028,2020-01-30 15:52:54 UTC,charm-ceph-osd should wait until the OSD logs report something like the following:
1821028,2019-12-10 19:53:46 UTC,"Flagging back to NEW state.  Please provide the next steps, or specific next steps toward resolution in order to TRIAGE.  Thank you."
1821028,2019-10-15 14:00:00 UTC,"The upgrade from Jewel->Luminous does not require a directory permissions upgrade, so all of the OSD services on each unit are restarted at the same time:"
1821028,2019-09-23 08:40:47 UTC,"Hi, I would like to add to this as we are prepping an upgrade from Jewel to Luminous."
1821028,2019-05-15 10:36:44 UTC,Hello.  How did you do the upgrade from Jewel to Luminous?  I'm assuming that you are on Ubuntu Xenial and upgraded to OpenStack xenial-pike or later?  Or did you upgrade Xenial to Bionic?
1821028,2020-03-16 08:57:25 UTC,I'm not a huge fan of the approach proposed in #5 - we should just use the admin socket of the OSD to determine status:
1821032,2019-03-20 15:57:50 UTC,here's a branch with a suggested implementation.
1821032,2019-03-20 16:41:38 UTC,"I am big fan of code refactoring where it is needed, so please don't let the following discourage you!"
1821032,2019-03-20 17:31:03 UTC,readability is highly subjective and i don't mind if y'all prefer the original implementation.
1821034,2019-04-10 18:31:40 UTC,And do you have ca-certificates installed?
1821034,2019-06-10 04:17:40 UTC,[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]
1821034,2019-04-10 22:02:22 UTC,"Yep.
Version: 20180409"
1821034,2019-04-10 01:47:53 UTC,Version: 1:18.04.30
1821034,2019-03-28 19:10:24 UTC,What version of python3 are using? I'm unable to recreate this.
1821034,2019-04-09 17:22:45 UTC,Here ya go:
1821034,2019-04-05 21:17:14 UTC,"While you've identified a legitimate bug, the lack of https support, in url_downloadable that function isn't actually used to get the meta-release file. (Wacky I know!) This can be seen by reading UpdateManager/Core/MetaRelease.py's download function."
1821034,2019-04-03 02:36:00 UTC,"$ python3 --version
Python 3.6.7
# dpkg -s python3
...
Version: 3.6.7-1~18.04"
1821034,2019-04-09 22:54:42 UTC,What version of ubuntu-release-upgrader-core do you have installed? This looks like a duplicate of bug 1796940.
1821042,2019-04-03 15:17:38 UTC,"Worth noting, this is on Queens with the old configuration pattern in use."
1821042,2019-06-03 04:17:27 UTC,[Expired for kolla-ansible because there has been no activity for 60 days.]
1821044,2019-06-25 15:53:55 UTC,"The issue could not be reproduced. There have been many loads installed since the issue was reported, no new cases had been found. Mark it as invalid."
1821044,2019-06-12 12:59:12 UTC,"Found log below from sm.log on controller-0, which indicated that the controller-0 was in unhealthy condition since 2019-03-18T14:49:02.
2019-03-18T14:49:02.000 controller-0 sm: debug time[1624.218] log<541> INFO: sm[20734]: sm_node_utils.c(423): Node unhealthy file (/var/run/.sm_node_unhealthy) set."
1821044,2019-05-08 17:51:53 UTC,Setting as incomplete as the steps to reproduce are not clear yet.
1821044,2019-03-20 17:52:10 UTC,Marking as release gating; requires further investigation
1821044,2019-03-20 17:14:44 UTC,Adding controller-0 sm logs.
1821044,2019-03-20 17:15:09 UTC,Adding controller-1 logs.
1821045,2019-03-25 05:36:58 UTC,I agree with #2. Regular proxy settings should also be configured via cloudinit-userdata for the core snap the same way apt proxy setting are set. Otherwise they will be set only when proxyupdater runs which may be too late.
1821045,2019-03-20 17:52:43 UTC,"With the right config set, once the machine has finished bootstrapping, I do see:
root@juju-50ff28-0:~# sudo snap get core -d
{
        ""cloud"": {
                ""name"": ""unknown""
        },
        ""proxy"": {
                ""http"": """",
                ""https"": """",
                ""store"": ""yFsGTy6qwkrVISeJI1JjU09v9Uxlc0Gf""
        },
        ""refresh"": {
                ""hold"": ""2019-03-20T19:42:00.762131261Z""
        },
        ""seed"": {
                ""loaded"": true
        }
}"
1821045,2019-03-20 17:55:45 UTC,Arguably we should be setting the snap proxy stuff at the same time we are setting apt and http proxy information (possibly all the way into cloud-init). I think there are a few apps that by-default come from the snap store in bionic. Though I think those are mostly desktop apps right now.
1821045,2019-03-20 18:44:28 UTC,"As a quick workaround hack you can use cloudinit-userdata. In my ~/.local/share/juju/clouds.yaml:
clouds:
...
  lxd:
    type: lxd
    auth-types: [certificate]
    endpoint: https://10.210.24.1:8443
    config:
      apt-http-proxy: http://192.168.0.50:3142
      apt-https-proxy: http://192.168.0.50:3142
      enable-os-upgrade: false
      cloudinit-userdata: |
          preruncmd:
              - ""set -xe""
              - ""curl -s http://192.168.0.50/v2/auth/store/assertions | sudo snap ack /dev/stdin""
              - ""sudo snap set core proxy.store=yFsGTy6qwkrVISeJI1JjU09v9Uxlc0Gf""
      snap-store-proxy: ""yFsGTy6qwkrVISeJI1JjU09v9Uxlc0Gf""
      snap-store-assertions: |
..."
1821045,2019-03-20 18:58:40 UTC,"(note that the cloudinit-userdata hack above changes the time for:
export JUJU_DEV_FEATURE_FLAGS=mongodb-snap; time juju bootstrap --debug lxd lxd --no-gui 'juju bootstrap'"
1821047,2020-04-28 15:21:03 UTC,"Terran was testing a server that also had applied the top commit here, which needs a signoff as well:"
1821047,2020-04-28 17:26:59 UTC,"Fixes pushed to master and rel_3_5.  Thanks Dan, Jason, and Terran!"
1821047,2020-03-16 17:02:07 UTC,"Daniel Pearl was working on this bug, among others, before he left CW MARS.  He left behind an omnibug branch that is intended to fix most of these issues.  I have had these bugs assigned to me since before his departure because it was my intention to clean his branch up, test it, and add any missing bits.  I have not had time to do this, so I am simply putting the branch out there in the hope that someone can test what's there during bug squashing week or whenever."
1821047,2020-04-27 21:22:14 UTC,This is fixed as part of the receipt omnibus patch. My signoff to that is at:
1821048,2019-03-20 20:23:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1821048,2019-03-22 12:42:01 UTC,seems for french language it is working ok. But if changed to english language de home dir's are not translated
1821048,2019-03-26 13:43:40 UTC,"i have tracked the error to gdm,
Gdm does not change the language after user setup with other language (and login with password selected).
If I reboot before the user logs in for the first time, all is ok."
1821048,2019-03-27 08:29:12 UTC,"I tried to add this preseed value, but seems not working:
d-i oem-config/reboot boolean true"
1821050,2019-03-20 18:03:54 UTC,controller-0 sm logs
1821050,2019-03-20 18:04:30 UTC,controller-1 sm logs
1821050,2019-03-22 18:45:05 UTC,Marking as release gating; issue related to ha
1821050,2019-05-14 18:49:36 UTC,The issue was not reproducible with newest build (May 14).
1821050,2019-05-14 18:50:41 UTC,Test on AIO-DX and AIO-DX/DC.
1821052,2019-03-20 20:19:32 UTC,"It's noted, thank you very much. I'm keeping an eye out for this bug."
1821052,2019-03-20 20:09:53 UTC,"Edelharn, the update is not ready yet. Please keep watching bug 1819615 (subscribe to it) and when it is told there that the new package (modemmanager 1.10) is ready for testing, you can install it. And give your feedback also in that bug so that we can pass the new package into the official updates. Thanks in advance."
1821052,2019-03-20 20:05:02 UTC,And still no version available for libqmi and libmbim.
1821052,2019-03-20 20:02:40 UTC,I decommented all lines in sources.list and reinstalled modemmanager.
1821052,2019-03-20 19:55:00 UTC,In the link give from Till Kampetter here : https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1821052/comments/2
1821052,2019-03-20 19:25:35 UTC,Hello and thanks to help me.
1821052,2019-03-20 19:39:08 UTC,"On Wed, Mar 20, 2019 at 07:25:35PM -0000, Edhelharn wrote:

> My sources.list file (updated) :
>
> #deb http://fr.archive.ubuntu.com/ubuntu/ bionic main restricted
> #deb http://fr.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
> #deb http://fr.archive.ubuntu.com/ubuntu/ bionic universe
> #deb http://fr.archive.ubuntu.com/ubuntu/ bionic-updates universe
> #deb http://fr.archive.ubuntu.com/ubuntu/ bionic multiverse
> #deb http://fr.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
> #deb http://fr.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
> #deb http://security.ubuntu.com/ubuntu bionic-security main restricted
> #deb http://security.ubuntu.com/ubuntu bionic-security universe
> #deb http://security.ubuntu.com/ubuntu bionic-security multiverse
> deb http://fr.archive.ubuntu.com/ubuntu/ bionic-proposed restricted main multiverse universe
"
1821052,2019-03-20 19:35:19 UTC,sudo apt-get install modemmanager/bionic-proposed
1821052,2019-03-20 19:52:05 UTC,">You're currently configured to install *only* packages from bionic's
>-proposed pocket. Why are the other sources disabled?
>
>Thanks
"
1821052,2019-03-20 18:30:44 UTC,"This is most probably covered by the update to modemmanager 1.10, bug 1819615."
1821054,2020-11-26 07:52:54 UTC,"Ok, thanks for getting back. So I'm closing this now due to insufficient data."
1821054,2020-11-25 16:14:04 UTC,Hi! Did you ever get a backtrace? ... otherwise I think we have to close this ticket due to insufficient data...
1821054,2020-11-25 19:28:00 UTC,No I never did. I reached out to try and get info on how to run or get a backtrack and never heard anything. I finally gave up and ended up selling the computer since I never got it working how I wanted to.
1821054,2019-03-21 03:59:58 UTC,"I have requested additional info in the other forum. While I wait on reply there, i will say, since you dont know it well, that Unraid is a disto built on top of slackware. Are there any basic command line commands that i could run to get the output you requested, or something to keep things moving while i wait on additional info from the other forum."
1821054,2019-03-20 19:45:46 UTC,FYI: I was happy to find the board and I'm hopeful to get it working. My goal is to use old hardware to make a retro gaming machine for my girls to play games I used to play growing up.
1821054,2019-03-20 18:04:46 UTC,hmm that's a fun board.
1821054,2019-03-20 20:22:27 UTC,I don't know anything about unraid unfortunately; so I suggest you go back to their forums and ask how to get the backtrace.
1821058,2019-03-21 13:41:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645173"
1821058,2019-03-21 18:05:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645288"
1821058,2019-03-22 16:15:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645645"
1821058,2019-04-05 16:15:52 UTC,"This RFE was discussed and approved by the drivers team, under the assumption that the spec will be developed following the following principles:"
1821058,2019-06-24 14:18:30 UTC,"Reviewed:  https://review.opendev.org/645288
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=c26573f847958fc090ba55b9c086a1cc5756b15d
Submitter: Zuul
Branch:    master"
1821058,2019-06-26 21:10:35 UTC,"Reviewed:  https://review.opendev.org/645173
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=fde298d0a179987a4195c8e12a66a2aa968ddfb6
Submitter: Zuul
Branch:    master"
1821058,2019-07-09 14:29:12 UTC,"Reviewed:  https://review.opendev.org/645645
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a70f07deb155eef450d59ccd897730298f360a0a
Submitter: Zuul
Branch:    master"
1821058,2019-08-22 14:28:07 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/678027"
1821058,2019-09-13 15:17:24 UTC,"Reviewed:  https://review.opendev.org/678027
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=380825fcf8e5bdba10c3b2758dfb772e28f9461e
Submitter: Zuul
Branch:    master"
1821059,2019-07-24 07:24:55 UTC,Continued in bug 1837683.
1821059,2019-07-22 04:26:01 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1821059,2019-03-22 10:26:52 UTC,Thanks. I'll gladly switch back to the modesetting driver to help debug the problem.
1821059,2019-03-22 08:58:16 UTC,Yes that should work.
1821059,2019-03-21 02:12:43 UTC,It appears the Xorg modesetting driver is repeatedly trying and failing to put an image on the screen here:
1821059,2019-03-22 01:40:45 UTC,You can certainly try using the old non-modesetting driver. To do that you need to add a xorg.conf file forcing Xorg to use the old 'intel' driver instead. Something like:
1821059,2019-03-21 13:33:34 UTC,"So would it be best in the interim to move to the non-modesetting driver, disable the present extension, or disable page flipping? I don't really know what the impact of any of those would be, but the freezes are getting pretty impactful for me."
1821059,2019-03-22 08:46:55 UTC,"So that would go into /etc/X11/xorg.conf, and that would be all that's in it? I don't have an xorg.conf currently, and I haven't edited one in a very long time."
1821060,2019-03-21 16:23:09 UTC,"Curious.  @NhatKhai, could you try an experiment?  Go into Preferences->Hotkeys and change the hotkey mapping of one of the actions to right Alt + key and tell us what KiCad saves as the hotkey mapping?  For example, you could double-click on ""Drag Item"" and then hold right Alt and press 'G'.  Does this change the mapping to ""Alt + G"" or does it stay ""G""?"
1821060,2019-03-21 18:17:08 UTC,"OK.  It looks like KiCad sees the key as ""Alt"" but something is intercepting/not passing that key up."
1821060,2019-03-21 17:44:38 UTC,"Also, export do not save the current modified key. I was had to hit Ok, and come back for export."
1821060,2019-03-21 17:43:57 UTC,"I try set Alt+G for the Drag Item. Then I cannot drag the item with the new setting using any keys G, Alt+C, left or right. Below is the extraction of the ""export"" key setting:
```
$hotkey list
# Common
[common]
shortcut   ""Ctrl+N"":    ""New""
...
shortcut   ""R"":    ""Rotate Item""
shortcut   ""Alt+G"":    ""Drag Item""
shortcut   ""Return"":    ""Mouse Left Click""
...
# Schematic Editor
[eeschema]
...
```"
1821060,2019-03-21 13:41:27 UTC,"I'm using the English Keyboard. And I'm a lefty, so right Alt is the most key I use for menu, because my left hand need to use the mouse."
1821060,2019-05-21 04:17:25 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821060,2019-03-20 22:35:44 UTC,It could also be language issue. For example a german keyboard does not come with a right alt key at all but with a altgr key.
1821060,2019-03-20 18:46:54 UTC,Both alt keys work fine on windows 10 pro.  Maybe a windows 7 issue.  Anyone else with windows 7 seeing this?
1821060,2019-03-21 07:20:59 UTC,"In French KB the right alt key is also altgr key (W7 32 bits).
Left and right alt keys are *not* equivalent.
This is true for all applications I tested.
The left alt key always activates the menus.
In most of apps, altgr key does not.
In a few others, altgr key activates the menus only during it is down."
1821060,2019-03-20 19:27:27 UTC,The fact that the same version of kicad works on windows 10 but does not work on windows 7 suggests there is a difference between windows 7 and 10 that affects kicad.  It doesn't mean that difference will affect other applications.
1821060,2019-03-20 18:58:07 UTC,How is it Windows 7 issue when I can use this key for other application as usual?
1821061,2019-03-20 18:26:22 UTC,"@NhatKhai-  Do you happen to have a suggestion for doing this differently?  I don't experience problems with commenting text lines (just remove the '.' at the beginning), so I'm at a loss as to how to improve this."
1821061,2019-03-20 19:03:37 UTC,"I don't know. I happy with the way 4.x did - it clear, and not having ""accidental"" issue with normal comment text. I ok with current way. But the largest issue I see is that not able to disable the whole block."
1821061,2019-03-20 19:06:51 UTC,Why don't we keep the requirement of +spice or -spice for directive as including that whole block like 4.x? I struggle to understand the use case that 5.x had left out.
1821061,2019-03-20 20:03:27 UTC,Maybe use ngspice .if command?  Section 2.12 of http://ngspice.sourceforge.net/docs/ngspice-28-manual.pdf
1821061,2019-03-20 20:24:05 UTC,Thank - that would do. BUT wounder the .if would supported by other simulator?
1821061,2019-03-20 20:28:04 UTC,"Wait - It not really work for my plot commands. I do not know if this is a .if bug for ngspice or not.
I still think better to have a way from KiCad to turn on/off the directive."
1821062,2019-08-20 03:16:23 UTC,"@nhatkai-  Thank you for taking the time to comment here.  Triaging this bug report is an attempt to minimize future issues.  While I don't quite have enough time to review each point explicitly, I feel you deserve a response that has some content, though it may not be fully satisfying."
1821062,2019-08-20 02:39:15 UTC,I think my reply email directly from my mail box isn't get to here. So sorry for repeating my comment here:
1821062,2019-08-19 13:11:52 UTC,"After reading Seth's argument, I changed my mind.  Using a relative path by assuming it will always be relative to a library path is probably going to confuse more users than it is going to help.  I am comfortable with marking this as ""Wont Fix""."
1821062,2019-08-17 14:56:17 UTC,"@Seth, you make valid points, and I myself use environmental variables for this as you describe."
1821062,2019-08-16 22:29:56 UTC,I disagree that this behavior should exist.  Especially as we are moving to symbols cached in the schematic file.  Relative paths such as '..' should be banned completely as they do not move between libraries and schematics and they present both a security risk as well as a potential slowdown when the containing directory is not accessible.
1821062,2019-08-16 16:03:39 UTC,"I'm sorry. #1b) is not true. I'm conclude it too fast. The datasheet field always ""~"" in the text editor. So Event saved, it still should work for 4.0.7 after remove the prefix library name in the text editor."
1821062,2019-08-17 16:05:02 UTC,"This is a nest of bug reports waiting to happen.  Especially when we view the datasheet location in the schematic.  I can't imagine users looking at a symbol property in the schematic and thinking that the ""../doc/file.pdf"" must be relative to another file somewhere else on the system."
1821062,2019-06-26 19:56:39 UTC,"@NhatKhai, is this still an issue, or did the above-mentioned fix sort it out?"
1821062,2019-04-07 14:17:57 UTC,At least part of this might be fixed with https://bugs.launchpad.net/kicad/+bug/1818220 which is marked as fix commited
1821062,2019-03-25 21:43:25 UTC,It looks like this go broken somewhere along the version 5 development path.  I think restoring this behavior is probably a good idea.
1821062,2019-03-25 13:36:32 UTC,"Relative to the library file (.lib). I though if not relative to library file where it is created, then that really make no sense. If relative to project, I would think that is a mistake because it mean other project not going to able to use this symbol easily. If it relative to the global library or from environment variables, then this library cannot copy into other place, and use easily."
1821062,2019-03-25 13:18:44 UTC,"Relative to what path? Do you mean the current project path, the library path, etc."
1821062,2019-08-16 16:00:03 UTC,"Yes, this still an issue in new stable release. And yes, it wasn't and issue in 4.x versions. I'm going to break the explanation into three as bellow (as I try with new KiCad version):"
1821071,2020-01-24 16:24:01 UTC,"Is this still an issue? It's quite old, I kind of doubt that the jobs would be broken for such a long time :)"
1821071,2020-02-02 01:53:00 UTC,this is fixed in https://review.opendev.org/#/c/644699/
1821072,2019-03-20 18:52:34 UTC,workaround has been merged for this bug to unblock the gate - https://review.openstack.org/#/c/644699/
1821072,2020-02-02 02:10:21 UTC,open new bug for moving that var to gabbi-tempest side -https://bugs.launchpad.net/tempest/+bug/1861592
1821075,2019-09-04 01:19:03 UTC,"With -D, non-existent input files are not written to the .d file.  This can cause confusing failures in some complex situations where one substitution is pulled into a second substitution."
1821079,2019-03-21 01:29:54 UTC,A patch is attached which re-adds the Photosmart b109a-m to models.dat.
1821079,2019-04-13 06:48:31 UTC,"As anticipated by Vier Eck, I can confirm that the above affects the [hp_laserjet_100_colormfp_m175nw] device, which is no more recognised after the stratification of models.dat"
1821079,2019-04-30 14:25:18 UTC,"Can you please revert the stratification of `models.dat` from version 3.18 to version 3.19? It is very annoying that every update of HPLIP needs manual change of `models.dat` to make some printers working again, or the force to the older version 3.18 of HPLIP."
1821079,2019-04-30 14:46:34 UTC,"So, I manually re-added all the printer definitions removed from the `models.dat`. I also re-added `modelN=<string>` here and there, not really knowing what they mean exactly."
1821079,2020-03-22 10:16:47 UTC,"Yes this bug affects  me too, i just found by myself the solution but spent hours..
Now everything is back to normal when manually editing the .dat file section which is missing.
This happened when upgrading Fefora 29 to Fefora 31 which installs hplip 3.20 and caused the issue in my linux box."
1821079,2020-05-22 14:25:04 UTC,error: Unsupported model: Photosmart_B109a-m
1821079,2020-11-08 19:30:51 UTC,Problem still present with hplip 3.20.9.
1821084,2019-05-16 16:08:44 UTC,"Change I63cfd8ce29a78433923d517bf27539ff8524d732 is merged, this is fixed."
1821085,2020-04-20 21:39:09 UTC,"Sorry, forgot the url: https://discourse.ubuntu.com/t/service-sssd/11579"
1821085,2019-03-22 19:38:39 UTC,"Thank you, Timo, that seems to work fine.   It appears that the whitespace that pam-auth-update --package --enable mkhomedir adds to the entry is significant.  In my insertion, my whitespace was not aligned to the same column so although the pam_mkhomedir.so was identical in the printing characters, it didn't match."
1821085,2020-04-20 21:38:46 UTC,The sssd chapter in the server guide has been rewritten and the pam-auth-update command was incorporated.
1821085,2019-03-21 21:18:43 UTC,I wouldn't even be reporting it if apt packages weren't overwriting my configuration.
1821085,2019-03-22 07:05:12 UTC,"if your goal is to enable pam_mkhomedir on the system, you could run:"
1821085,2019-03-22 19:40:35 UTC,Timo's recommendation appears to pass a test of patching SSD.  The difference between patching it yourself and using pam-auth-update for me was that whitespace was significant.
1821085,2019-03-20 21:33:50 UTC,this has nothing to do with sssd itself
1821086,2019-03-21 09:42:52 UTC,"Hi, what distro you running. Might be a difference between ubuntu and centos bash? Havent seen those errors with centos."
1821086,2019-03-21 10:42:34 UTC,Hi!
1821086,2019-03-25 19:07:22 UTC,I've isolated the specific parts that makes up this bug and ran it through CentOS and Ubuntu Docker containers with the same result. It's still that variable in neutron/defaults/main.yml that isn't interpreted (later on when that container are started) as intended by the author of the commit(s) that introduced the rolling upgrade logic:
1821086,2019-03-25 19:52:20 UTC,"If anyone want to try this at home i've created a repo containing the isolated parts of this bug, hopefully this might clear things up a bit:"
1821086,2019-03-25 21:38:13 UTC,"OK, so this was merged into master today: https://git.openstack.org/cgit/openstack/kolla-ansible/patch/?id=42d664c15618a67e899f77b622845dab145dc91a"
1821088,2019-03-20 21:18:25 UTC,"As mentioned in the other bug, we likely just need to keep track of the VirtualInterface objects we create and if something fails we clean them up here:"
1821088,2019-05-04 16:50:42 UTC,"Hmm, this cleanup was added in newton:"
1821088,2019-05-04 17:07:40 UTC,I'm not seeing the error in logstash so this must be super rare if you're hitting it in Heat's CI testing.
1821088,2019-10-09 13:59:19 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Duplicate%20entry%5C%22%20AND%20message%3A%5C%22for%20key%20'uniq_virtual_interfaces0address0deleted'%5C%5C%5C%22%5C%22%20AND%20(tags%3A%5C%22screen-n-cond-cell1.txt%5C%22%20OR%20tags%3A%5C%22screen-n-api.txt%5C%22)&from=7d
1821089,2019-05-27 08:37:30 UTC,Does someone have some idea of this bug?
1821089,2019-05-27 13:00:38 UTC,"Stable device naming within the guest is OS dependent and strictly out of scope of nova to fix.
nova does not chose the address at which device are attached and the nova api doe not
guarentee stable nic ordering. the vm pci adress is determined by libvirt."
1821093,2020-06-12 14:53:49 UTC,Jane - that article captivated me for more than a half hour! Wow! I am left with no solution. It seems that it's a catch 22.
1821093,2019-11-25 16:51:38 UTC,"Westchester libraries also report concerns. We would definitely like to see some kind of ""are you human"" check."
1821093,2019-11-24 14:44:45 UTC,"Just a note that, when implemented, libraries must be able to enable or disable the CAPTCHA on this form (maybe through a library setting).  CAPTCHAs have serious, intrinsic accessibility issues: https://www.w3.org/TR/turingtest/#the-accessibility-challenge"
1821093,2019-11-05 13:51:56 UTC,Here is an example of how this impacts SPARK libraries - tons of 'junk' data in patron self-registration.
1821093,2019-03-25 15:06:06 UTC,Can confirm that South Carolina State Library (part of SCLENDS) has also experienced spam submissions. Something Captcha-esque would be helpful.
1821093,2019-11-23 17:45:05 UTC,Problems with useless data in the form are reported frequently by PaILS Members using SPARK Support.  Our response is to send them to this bug.
1821094,2019-07-23 22:13:18 UTC,"Thanks for this patch Jane! I have tested this code and consent to signing off on it with my name, Kyle Huckins and my email address, <email address hidden>."
1821094,2019-08-05 13:41:43 UTC,"I've tested the patch and it does indeed make updates of the item status grid faster. However, I've observed a tradeoff: when you do the update (or for that matter, when you load the holdings editor with 100+ items, although that's not a concern of this particular patch), it's easy to fire off so many PCRUD requests simultaneously that the pool of open-ils.pcrud backends get saturated."
1821094,2020-01-30 21:07:51 UTC,"Thanks for the helpful feedback, Galen."
1821094,2020-01-31 01:50:00 UTC,"One other note: on the Angular side, RxJS has some nice built-in options for batching concurrent API calls.  For example, the RxJS version of $q.all, merge, allows you to pass in a number for how large you want these batches to be [1].  In practice, the Angular client uses merge's cousin mergeMap more often so far, and that also has an option to pass in a batch size argument [2]."
1821094,2019-03-21 23:36:10 UTC,"Another thing that would help: I intentionally have the itemSvc.fetch calls running sequentially, rather than concurrently so that the rows don't get out of order.  If itemSvc.fetch offered a way to fetch a row in place, rather than unshifting, we could run those calls concurrently without the sorting issue."
1821094,2020-09-24 19:21:47 UTC,"Jane, could you please rebase this one?"
1821094,2021-01-04 23:45:21 UTC,"I tested this out without rebasing it to master.  I loaded 100+ barcodes, and then edited 15 at a time.  I'm seeing all changes show up simultaneously after a wait of around 1.5 seconds.  Looks good on my end.  I'll hold off on signing off because I don't have a lot of experience with backend performance testing, as was requested.  Also I haven't tested the rebase."
1821094,2019-06-13 04:36:46 UTC,I have force-pushed fixes to all the issues that John discovered in testing.  Let me know what you think!
1821094,2020-04-21 18:21:46 UTC,"While I could not test the back end performance testing, I did double check and make sure editing in item status was still speedy with those changes you may have made with those magical back end issues."
1821094,2019-05-24 20:59:57 UTC,"Thanks for your thorough testing, John.  The two bugs you mentioned are new with this patch.  I'm assigning myself so that I can:"
1821094,2019-03-21 18:31:08 UTC,EG 3.2.4
1821094,2019-05-03 22:42:48 UTC,"Here we go!  For me, this branch works up to 10 times faster than the old version did.  It fetches the updated rows concurrently, rather than sequentially.  Also, it only fetches the updated rows, not the ones that haven't been edited."
1821094,2019-04-26 17:46:59 UTC,I'll take a stab at this.  My plan is to:
1821094,2019-04-26 16:31:01 UTC,"I'm seeing confusingly slow refreshes with even smaller item sets on my training server, (even as little as 10 items)."
1821094,2019-03-22 17:24:51 UTC,Thanks!
1821094,2019-03-22 16:36:24 UTC,"It's currently just in master, Elaine.  It was added during bug squashing week."
1821094,2019-03-22 15:30:07 UTC,the new save icon
1821094,2019-03-22 15:29:55 UTC,What version of EG is the new icon available on?
1821094,2019-05-23 18:47:36 UTC,"Thanks for your work on this, Jane."
1821097,2019-09-06 08:20:56 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/296
1821097,2019-03-22 17:49:37 UTC,Let's just go with the permissions/groups that we already have in Django for now. Having developers get a badge is not that important for the forum.
1821097,2019-03-21 17:54:48 UTC,"Whereas we can get the website related privileges easily, we have to think about how we could get the developers: At least i do not want to maintain two lists (one for the game and one for the website). The File developers.json would be good for that, but the listed names may not be the same as on the website. We also don't want any developer from that list shown with as 'Developer' on the website (no, i don't say the name) ;)"
1821097,2019-03-21 09:22:00 UTC,"Yes, that would be good. What about people who are both developers and moderators? We could concatenate the titles I guess."
1821097,2019-03-21 06:32:53 UTC,"What about ""Developer""? For technical questions it might be important."
1821097,2019-03-21 06:05:01 UTC,"I'd like to be ""Chieftain"" just like on the developer's list, and ""Moderator"" for forum moderators."
1821102,2019-06-24 14:49:00 UTC,@Andy any change you could give the updated cloud-init package a test?
1821102,2019-06-07 16:07:53 UTC,"Hi Andy,"
1821102,2019-06-13 02:07:07 UTC,"Hi Ryan,"
1821102,2019-06-13 14:32:56 UTC,\o/
1821102,2019-06-13 20:32:10 UTC,I've updated the branch with some unittests and fixes (for other routes besides a /32).
1821102,2019-06-24 22:10:53 UTC,Thanks for the reminder! Oops.
1821102,2019-06-24 23:07:04 UTC,"> And I think we still need to bump the timeouts; you suggested that the default url timeouts from DatasourceEC2 are more realistic, correct?
"
1821102,2019-06-25 14:51:10 UTC,Thanks for verifying!
1821102,2019-07-11 01:13:21 UTC,"Hi Ryan,"
1821102,2019-07-11 15:35:49 UTC,"On Wed, Jul 10, 2019 at 6:20 PM Andy Botting <email address hidden> wrote:"
1821102,2019-07-12 00:08:50 UTC,"> The branch has not yet landed.  Once it does then the next
> cloud-init SRU will release this back through Xenial.  We'll
> also cut a 19.2 cloud-init release which would include the fix.
>
"
1821102,2019-07-16 22:40:18 UTC,"This bug is fixed with commit 07b17236 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=07b17236"
1821102,2019-07-17 17:12:03 UTC,"This bug is believed to be fixed in cloud-init in version 19.2. If this is still a problem for you, please make a comment and set the state back to New"
1821102,2019-06-06 22:51:46 UTC,"Thanks Ryan, great explanation. I really appreciate you looking into this for me."
1821102,2019-06-06 21:51:34 UTC,"Hi Ben,"
1821102,2019-06-06 22:10:32 UTC,"Andy,"
1821102,2019-04-04 21:50:40 UTC,"Hi Ryan,"
1821102,2019-06-05 01:38:42 UTC,Hi Ryan.
1821102,2019-06-05 00:09:29 UTC,Thanks.
1821102,2019-06-04 23:43:32 UTC,This is an example of network_data.json for a private network.
1821102,2019-06-04 23:42:05 UTC,Here's an example of network_data.json from our flat networking setup. This provides a public routable IP address to the instance.
1821102,2019-06-04 14:14:46 UTC,"Thanks for re-opening; after your response to my request for information, you can move the bug state back to New.  Sorry for the trouble and thanks for following up."
1821102,2019-06-04 11:19:17 UTC,"I've reopened this, and marked it as confirmed. Please let me know if there's any more information I can provide."
1821102,2019-06-04 04:17:31 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1821102,2019-06-06 18:36:30 UTC,"Andy, thanks for filing this. I believe I am running into it as well."
1821102,2019-04-04 20:47:31 UTC,"On Thu, Apr 4, 2019 at 3:36 PM Andy Botting <email address hidden> wrote:"
1821102,2019-04-04 20:21:05 UTC,"It never works in the first stage because the static route to
169.254.169.254 isn't set up. This is delivered by dhcp, which isn't
specifically handled by cloud-init. I verified this by looking at the
output of dhclient."
1821102,2019-04-04 14:57:01 UTC,Thanks for the logs.
1821102,2019-03-21 20:31:26 UTC,Logs attached.
1821102,2019-03-21 14:11:10 UTC,Thank you for filing a bug.
1821105,2019-03-21 22:50:47 UTC,"Thanks, James.  We'll look out for that."
1821105,2019-03-21 19:29:08 UTC,"Also of note from the log, perhaps something that could be captured by the charm to respond with some wrapper around which nodes run that resource?"
1821105,2019-05-15 11:32:40 UTC,"This seems to be fix-committed in master branch, and 19.04 was released with this on 2019-05-06.  I think, thus, this is resolved, as there is a workaround for older charms."
1821105,2019-03-21 09:16:57 UTC,"Naming of vip resources has changed in the master branch to not use the interface name for exactly this reason;  we now rely on the pacemaker resource to figure out which interface to bind the VIP to, and use a short hash of the actual vip for the resource name."
1821109,2019-10-18 06:09:42 UTC,"Seems like this is a duplicate of this bug, can we confirm?
https://bugs.launchpad.net/charm-hacluster/+bug/1400481"
1821109,2019-03-21 14:49:54 UTC,"After running the crm_node -R, you can then 'juju run --application <hacluster> hooks/config-changed' to trigger an update to corosync.conf file and running corosync status"
1821109,2019-10-18 15:04:38 UTC,"Confirmed, this is a duplicate of bug 1400481.  This bug does list workaround information missing from that bug that may be useful for future travelers."
1821109,2019-03-21 00:58:39 UTC,"Part of the workaround is on remaining nodes,"
1821118,2019-03-22 00:45:22 UTC,who will track this issue
1821120,2019-08-01 17:04:41 UTC,"Not sure, maybe something has been wrongly downloaded...
I would try again!"
1821120,2019-10-01 04:17:25 UTC,[Expired for llvm-toolchain-7 (Ubuntu) because there has been no activity for 60 days.]
1821126,2019-06-18 21:30:40 UTC,The issue looks like https://gitlab.gnome.org/GNOME/gnome-calculator/issues/101 which got resolved with newer updates
1821136,2020-12-16 13:33:33 UTC,The following errors can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1821139,2019-04-15 08:39:29 UTC,"Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master
Review: https://review.openstack.org/645072"
1821139,2019-04-15 08:39:23 UTC,"Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master
Review: https://review.openstack.org/645082"
1821139,2019-03-26 09:47:12 UTC,"Reviewed:  https://review.openstack.org/645083
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=e177129e59eace0cbc3bfa638ca9f3d06ca1e68d
Submitter: Zuul
Branch:    master"
1821139,2019-03-25 15:27:03 UTC,"Reviewed:  https://review.openstack.org/645548
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b3ce4f00b47522592afae2438c05fa03d7483305
Submitter: Zuul
Branch:    master"
1821139,2019-03-22 14:59:55 UTC,"Reviewed:  https://review.openstack.org/645501
Committed: https://git.openstack.org/cgit/openstack/tripleo-puppet-elements/commit/?id=47f2a759e4569595f3e32676df661fd9f8f559e1
Submitter: Zuul
Branch:    master"
1821139,2019-03-22 12:00:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645548"
1821139,2019-03-25 21:52:58 UTC,"Reviewed:  https://review.openstack.org/645498
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=388a42774a073220f8d28a722474c75c4e60ed24
Submitter: Zuul
Branch:    master"
1821139,2019-03-22 08:23:15 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645498"
1821139,2019-03-21 09:24:00 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645083"
1821139,2019-03-21 09:09:36 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645082"
1821139,2019-03-22 08:39:57 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/645501"
1821139,2019-03-21 08:31:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/645072"
1821139,2019-03-21 08:15:13 UTC,puppet-nova https://review.openstack.org/#/c/645071/
1821140,2019-06-12 19:41:05 UTC,Detecting USB wireless mouse but not touchpad on my end
1821140,2019-03-24 15:31:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821143,2019-03-31 09:12:53 UTC,Fixed in 1.3.1-39
1821144,2019-03-31 09:13:25 UTC,Fixed in 1.3.1-40.
1821145,2019-03-21 08:39:13 UTC,https://review.openstack.org/645069
1821145,2020-01-29 09:56:55 UTC,"Change abandoned by Sorin Sbarnea (<email address hidden>) on branch: master
Review: https://review.opendev.org/645069"
1821147,2019-03-21 09:00:03 UTC,"So I was wrong, it didn't assume that ""Insert always worked"" it uses this transaction:
 err := st.db().RunTransaction([]txn.Op{
  {
   C:      sshHostKeysC,
   Id:     id,
   Insert: doc,
  }, {
   C:      sshHostKeysC,
   Id:     id,
   Update: bson.M{""$set"": doc},
  },
 })"
1821147,2019-03-21 12:23:32 UTC,https://github.com/juju/juju/pull/9935
1821147,2019-03-21 13:24:43 UTC,https://github.com/juju/juju/pull/9938 into develop
1821148,2019-07-03 04:17:36 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821148,2019-05-03 11:04:52 UTC,"Since no one can seem to replicate this reliably, I'll mark as incomplete. Please change the status to New if steps to replicate reliably are found."
1821148,2019-04-07 16:17:59 UTC,Maybe this is the graphical shell of the operating system itself.
1821148,2019-04-07 16:17:12 UTC,It turns out some kind of roulette game with winning 95%)). Looks like the library copied functions and there are two duplicates and something like or some sort of cumulative error somewhere in the loop.
1821148,2019-04-03 17:49:16 UTC,"I just made a video of the problem. Unfortunately, this time I had a hard time making it appear."
1821148,2019-03-29 12:55:26 UTC,"No specific steps, just open any schematics, strike U over a component and, randomly, the reference field is either globally selected or just the number is selected."
1821148,2019-03-28 23:38:44 UTC,"I can't reproduce this on OSX.  Specific steps needed, or is it GTK-specific?"
1821148,2019-03-21 08:48:50 UTC,"Application: kicad
Version: 5.1.0-060a0da~80~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-141-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009"
1821148,2019-04-03 17:08:07 UTC,I'm not seeing this on windows either.  A screenshot of the incorrect behavior might be useful.
1821152,2019-05-22 19:49:37 UTC,affects linux-azure 5.0.0-1007.7
1821152,2020-10-09 20:46:44 UTC,failed on Bionic/azure-4.15 : 4.15.0-1097.107 : amd64  on Standard_B1ms
1821152,2019-03-21 10:35:30 UTC,"On Cosmic-KVM, it has passed after re-run.
But for Bionic KVM, it's still failing with the same issue."
1821152,2019-04-10 19:49:38 UTC,"appears to affect linux-azure: 4.18.0-1015.15, Standard_F2s_v2-ubuntu_lxc
04/05 16:42:33 DEBUG| utils:0153| [stdout] FAIL: lxc-tests: lxc-test-no-new-privs (37s)"
1821152,2019-05-02 13:57:37 UTC,"affects linux-azure: disco: 5.0.0-1005.5 , Standard_B1ms , Standard_F1s , Standard_F2s_v2"
1821152,2019-10-17 10:11:02 UTC,Still affecting 4.15 B-kvm
1821152,2019-11-26 19:23:53 UTC,"after running this test by hand inspecting what possibly could be failing, I am not able to reproduce this,  I feel that autotest itself might be the cause of some of the failures. will continue to investigate."
1821152,2019-11-26 19:24:41 UTC,"xc-tests: lxc-test-api-reboot (78s)
18:19:08 DEBUG| [stdout] PASS: lxc-tests: lxc-test-apparmor (0s)
18:20:01 DEBUG| [stdout] PASS: lxc-tests: lxc-test-apparmor-mount (52s)
18:20:02 DEBUG| [stdout] PASS: lxc-tests: lxc-test-attach (1s)
18:21:16 DEBUG| [stdout] PASS: lxc-tests: lxc-test-autostart (74s)
18:21:16 DEBUG| [stdout] PASS: lxc-tests: lxc-test-basic (0s)
18:21:18 DEBUG| [stdout] PASS: lxc-tests: lxc-test-cgpath (2s)
18:21:18 DEBUG| [stdout] PASS: lxc-tests: lxc-test-checkpoint-restore (0s)
18:21:23 DEBUG| [stdout] PASS: lxc-tests: lxc-test-cloneconfig (5s)
18:21:23 DEBUG| [stdout] PASS: lxc-tests: lxc-test-clonetest (0s)
18:21:24 DEBUG| [stdout] PASS: lxc-tests: lxc-test-concurrent (1s)
18:21:24 DEBUG| [stdout] PASS: lxc-tests: lxc-test-config-jump-table (0s)
18:21:26 DEBUG| [stdout] PASS: lxc-tests: lxc-test-console (2s)
18:21:34 DEBUG| [stdout] PASS: lxc-tests: lxc-test-console-log (8s)
18:21:38 DEBUG| [stdout] PASS: lxc-tests: lxc-test-containertests (4s)                                                                                            ..."
1821152,2019-12-09 09:42:55 UTC,Found on D-KVM 5.0.0-1024.26
1821152,2020-10-09 18:01:06 UTC,Spotted on Focal/azure : 5.4.0-1029.29 : amd64
1821164,2019-04-14 10:56:37 UTC,The fix pushed to trunk has some issues:
1821164,2019-03-22 13:43:57 UTC,"It is now confirmed that the issues in the binary of the engine. However, the GUI
should be more graceful and not just crash if it cannot parse the output from the engine
(and perhaps still run but say that there is an issue with one of the engines)."
1821164,2019-03-22 08:33:15 UTC,seems to be verifytapn64 that segfaults when running versioncheck (-v)
1821164,2019-03-21 15:05:37 UTC,"output from my machine (AdoptOpenJDK):
C:\Users\kyrke>java -version
openjdk version ""1.8.0_202""
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_202-b08)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.202-b08, mixed mode)"
1821164,2019-03-21 15:08:26 UTC,ahh.. not a java issue... seems to be when parsing VerifyTAPN
1821166,2019-03-21 12:06:38 UTC,"I often use the alternate units, so I wouldn't want to lose them."
1821169,2019-03-22 01:47:25 UTC,To verify if the problem really is with libinput please try:
1821169,2019-05-21 04:17:29 UTC,[Expired for libinput (Ubuntu) because there has been no activity for 60 days.]
1821170,2019-05-15 11:39:44 UTC,This has been overtaken by events.  Please update to the 19.04 charm which has a more robust osd services check and nrpe integration.
1821170,2020-03-13 07:31:52 UTC,"Change abandoned by José Pekkarinen (<email address hidden>) on branch: stable/18.11
Review: https://review.opendev.org/645123"
1821174,2019-10-15 12:40:44 UTC,This issue was fixed in the openstack/openstack-ansible 20.0.0.0b1 development milestone.
1821174,2019-08-29 09:49:15 UTC,This issue was fixed in the openstack/openstack-ansible 19.0.2 release.
1821174,2019-08-15 14:45:42 UTC,"Reviewed:  https://review.opendev.org/672980
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=d729e4819ae277a29e1abdf4fc00d7526a0e60d4
Submitter: Zuul
Branch:    stable/stein"
1821174,2019-07-26 13:36:03 UTC,"Change abandoned by Florian Haas (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/668843
Reason: Superseded by Ie0e2f376bd6a16f88801611b77fcfde5003d68e2"
1821174,2019-10-24 21:39:01 UTC,This issue was fixed in the openstack/openstack-ansible 20.0.0.0rc1 release candidate.
1821174,2019-07-03 09:30:57 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/668843"
1821174,2019-05-19 09:45:46 UTC,"Reviewed:  https://review.opendev.org/656496
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=590c86bc1010eae78a5df7ede26eb8dca0bf20a5
Submitter: Zuul
Branch:    master"
1821174,2019-04-30 11:19:03 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656496"
1821174,2019-07-26 13:34:47 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/672980"
1821176,2019-05-22 04:17:32 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821176,2019-03-22 13:31:48 UTC,Thank you for the crash dump.  It's rather interesting.  What I don't understand is how or why FOOTPRINT_PREVIEW_PANEL_BASE::Create() is being called after Close() is called for the main window frame.  By chance did you have the insert footprint dialog open or the footprint tool enabled when you closed pcbnew?
1821176,2019-03-22 18:51:12 UTC,"Sorry, I closed pcbnew in the middle of doing something else, clicking the X-button in the window corner of pcbnew, and have no idea about what was going on. Drmingw was set as the default crash handler in Windows so it opened up the dump automatically."
1821176,2019-03-22 19:35:34 UTC,"@eelik, if you manage to reproduce this, please note to the best of your ability to remember what you did before the crash and post it to this bug report.  There have been quite a few reports of crashes similar to this on windows.  I suspect it is a very specific set of conditions that cause the problem.  I'm having no luck reproducing any of them so the more information the better."
1821179,2019-05-14 16:36:50 UTC,"Confirmed 3.1.11. When testing, I can observe the behavior on the first load and subsequent loads."
1821180,2019-03-21 13:13:43 UTC,"When db_host is commented in publish, the worflow obviously fails on next action with:"
1821180,2019-03-21 13:15:30 UTC,And when db_password is commented it fails with:
1821180,2019-07-31 08:40:59 UTC,"hi, is it still relevant? Can you provide a simple example to reproduce this?"
1821182,2020-05-15 08:04:32 UTC,"Committed as of https://github.com/CanonicalLtd/netplan/pull/109
Released as of netplan.io 0.99"
1821183,2020-04-07 15:28:26 UTC,"KiCad has migrated to Gitlab, this issue is available here: https://gitlab.com/kicad/code/kicad/-/issues/3133"
1821183,2020-03-30 18:54:15 UTC,another comment saying that I really miss it...
1821183,2019-11-29 03:37:06 UTC,"Why not agreement on what correct display local ratsnest?
Correct is when footprint are not moving or grabbing its all pad ratsnests are hided, else are shown. Showing ratsnest per pad (for single pad, few separete pads) much less usefull, than show local ratsnest as it shows in kicad 4, when moving, grabbing."
1821183,2019-11-29 00:08:33 UTC,Backporting this issue from 6 to 5.1 would be prohibitive with many potential side-effects.  The fix implements new ratsnest options because there is no agreement on what the _correct_ display of ratsnest should be.
1821183,2019-11-28 20:31:50 UTC,This should definitely NOT be classified as a feature/wishlist bug.
1821183,2019-06-13 00:48:31 UTC,Fixed in daad58e51
1821183,2019-05-25 16:41:52 UTC,I am not sure this should be a wishlist bug as it was available in version 5.0.x so this is kind of a regression. See forum discussion https://forum.kicad.info/t/how-to-turn-on-net-of-interest/17220/6
1821183,2019-04-27 10:01:46 UTC,"It would be very nice if it were decorated with a button on the left vertical panel the button ""Show all ratsnests""."
1821183,2019-04-25 17:46:56 UTC,"Using the option ""Show ratsnest footprint when moving it"" and scaling with translation to the cursor is very convenient to orient footprints."
1821183,2019-04-25 17:44:50 UTC,"Please! Return this functionality! It is very convenient! I support! KiCAD 5.1.2
When you press the ""display local connections"" button, then when you select contact pads with a pencil, you press the right mouse button - ratsnest are disappear. Apply informational only to this button. Please make checkbox in the Pcbnew settings: ""Show the ratsnest footprint when it is moved"" and all. Thank you!"
1821183,2019-03-22 08:04:49 UTC,"(Edit: ""individual component are often close to unreadable"" obviously refers to the case when the whole ratsnest IS displayed.)"
1821183,2019-03-22 07:48:38 UTC,"Michael Kavanagh: as I understand, the function you are describing is the one that displays ALL ratsnests (and I confirm it works in that case).
I was referring specifically to the case when the global ratsnest is not displayed (whereby the connections of the individual component are often close to unreadable)."
1821183,2019-03-21 20:47:04 UTC,For me on macOS (and win 10) the ratsnest is shown when moving a footprint as long as the ratsnest is enabled in the Items tab in the Layers Manager (duplicated in the left hand toolbar). This matches the behaviour you describe for 5.0.2 and is IMO correct.
1821183,2019-03-21 16:31:13 UTC,"Note that when we add this, we should place it in the pcbnew preferences panel."
1821186,2019-03-21 15:39:51 UTC,I've downgraded kernel to 3.10.0-957.5.1 and all works fine
1821186,2019-09-20 13:08:56 UTC,We discussed this issue among the snapd team and we believe that this is a race caused by incorrect initialization of signal handlers. This bug was fixed a while ago. I've assigned this to my colleague to confirm.
1821187,2019-03-21 17:03:25 UTC,"I think the issue actually lies in the etcd interface layer.  The Vault code already has the failing code behind a check for the etcd.tls.available flag, which shouldn't be set if any of those values are None."
1821187,2019-05-13 06:00:12 UTC,https://github.com/juju-solutions/interface-etcd/issues/13
1821187,2019-05-13 06:00:28 UTC,I raised the above issue on the interface-etcd repo to track this issue there as well
1821193,2019-03-21 15:10:08 UTC,"Autodetection of this would be nice, but a workaround that I can manually enable cleanly using my ansible provisioning would be fine as well, right now, based on https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 I can fix this, but I expect this fix to be very fragile as I need to insert lines into config files that I suspect will be modified by future snapd upgrade."
1821196,2019-03-21 16:12:51 UTC,The branch is called: user/sandbergja/lp1821196_de-arrowify_item_status
1821196,2019-04-11 21:37:23 UTC,Issue and fix confirmed.  Merged to 3.2+
1821198,2019-10-25 18:21:11 UTC,"Saving selection time and improving workflow with a ""Select All"" option would definitely be beneficial to users -- recognizing that guidance is needed on consideration of basket size parameters."
1821198,2019-10-25 14:43:13 UTC,"Yes, we do this all the time -- do a search, look at the results, perhaps add limiters or otherwise refine the search, select all and move to a basket as a way to move them to a bucket.  I'm attaching a screenshot from OverDrive Marketplace showing how they handle this -- I like the fact that even though the number of search results appears with the pagination above, they repeat the number of records in the checkbox text to make it clear what the user is requesting."
1821198,2019-03-21 16:01:41 UTC,"I note that some limits may need to be placed on this sort of feature, including"
1821201,2019-03-22 13:22:46 UTC,I tested this on windows and linux without issue so it appears to be specific to macos.  Would one of our macos devs please confirm?
1821201,2019-03-22 13:42:24 UTC,"Works for me here.  @Christian, please post your version information from KiCad->About KiCad->Copy Version Information"
1821201,2019-03-22 16:00:51 UTC,Hi
1821201,2019-03-22 16:01:51 UTC,Hi
1821201,2019-03-22 16:28:45 UTC,@Christian-  Did you run this from the disk image?
1821201,2019-03-22 17:02:04 UTC,Hi
1821201,2019-03-22 17:18:21 UTC,Hi
1821201,2019-03-22 17:18:59 UTC,@Christian-
1821201,2019-03-22 19:25:12 UTC,Hi again
1821201,2019-03-22 19:25:43 UTC,Hi again
1821201,2019-05-22 04:17:31 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821203,2019-06-22 04:17:21 UTC,[Expired for neutron because there has been no activity for 60 days.]
1821203,2019-03-22 00:38:13 UTC,Which version of neutron are you running. Is this node running l3 agent in dvr-snat mode or dvr mode.
1821203,2019-03-23 00:13:55 UTC,"@Candido,"
1821203,2019-04-22 13:16:39 UTC,I'm sorry for having been slow to answer.
1821204,2020-03-18 11:57:47 UTC,"Related fix proposed to branch: feature/losf
Review: https://review.opendev.org/713632"
1821204,2020-01-24 23:37:28 UTC,"Reviewed:  https://review.opendev.org/702950
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=57ca3570e911bd290ce0e44bdebaa4b5b4ceca13
Submitter: Zuul
Branch:    master"
1821204,2020-03-18 16:19:05 UTC,"Reviewed:  https://review.opendev.org/713632
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=79bd2e59e5c15ee84814ec1c4f0893176ba79412
Submitter: Zuul
Branch:    feature/losf"
1821204,2019-03-21 17:01:28 UTC,Just to be clear you're thinking the ssync_reciever might be able to grab the subrequest response error and log it in the source replicator/reconstructor logs?
1821204,2019-03-22 13:06:39 UTC,"I was thinking that the ssync_receiver should grab the error and log it in its own log file. It's not perfect but easy to do. It already logs the HTTP code and method, so it's just about adding resp.body [1]"
1821205,2019-03-21 17:00:07 UTC,This change was made by a bot.
1821206,2019-03-21 17:42:39 UTC,From the logs and screenshot you provided everything looks like its working correctly. The screenshot you provided shows where PXELinux is downloading the kernel and initrd and is before Bionic loads. Does anything happen after that? Can you download download and post the SHA256 sums of the kernel and initrd from
1821206,2019-03-21 18:12:16 UTC,"Hi Lee,"
1821206,2019-03-22 14:34:14 UTC,"Hello, after updating MaaS from 2.4.2 to 2.5.1, all nodes are booting normally."
1821206,2019-05-22 04:17:19 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1821206,2019-09-29 05:51:07 UTC,"Hi,
  This is a problem happening for a while and there is not a proper resolution. After upgrading to the latest stable version of maas 2.6.1 (7832-g17912cdc9-0ubuntu1~18.04.1) as of today using an intel server S2600WTT it keeps rebooting while trying to pxe boot and it does it right after
provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/ga-18.04/bionic/daily/boot-initrd requested by ...."
1821206,2019-09-29 21:39:49 UTC,I tried commissioning using the hwe kerner and its now working. It seems like network drivers for this servers were included as part of the ga-18.03 or previous ones but now they are only available on hwe-18.04 kernels.
1821208,2019-12-13 15:04:36 UTC,On last drivers team meeting we agreed to abandon this rfe as this is going to address only corner case which can be easily workarounded.
1821208,2019-10-07 07:10:54 UTC,"@Akihiro: how about proposing config option, like ""policy_allows_default_values_always"" (or something like that, I'm not good in naming :)) and default it to False.
That way we may keep original behaviour and give some operators possibility to change it to make some custom scripts working if they are not affraid about leaking informations that way."
1821208,2019-10-04 13:54:59 UTC,Sorry for late.
1821208,2019-09-27 15:09:27 UTC,"is this only for POST? or, also for PUT matching the current value?"
1821208,2019-04-05 15:12:53 UTC,"> If we move the first viewpoint forward, doesn't it mean that non-admin user
> try to specify provider network attributes and if it matches current values
> it will succeed. The non-admin user can estimate what provider network
> attributes are actually used. I think it is not a good behavior from a
> security reason.
"
1821208,2019-03-29 00:25:17 UTC,Fair enough. Let's discuss it during the next driver meeting
1821208,2019-03-22 13:18:05 UTC,"1.) The reason not to implement this in oslo.policy is that oslo.policy has no concept of the rvalues for the operations it is filtering by policy.  This proposal discusses filtering by the tuple of ""API method:argument value"" while oslo.policy only screens by ""API method:identity of caller"".  I asked in #openstack-oslo about this kind of filtering, and they directed me towards the Keystone folks, who said for this end this was the proper means, ""so you can move bits up and pre-process the request as needed"" [1]."
1821208,2019-03-21 23:18:44 UTC,1) Why implement this in Neutron? Why not in oslo.policy?
1821208,2019-03-29 13:56:42 UTC,I have several comments on answers to 2) in #2.
1821209,2020-06-22 19:29:01 UTC,Closing this bug -- Please reset to NEW and add new logs and evidence if the issue persists.  Thank you.
1821209,2019-10-22 08:41:21 UTC,url = http://10.5.0.13:8200
1821209,2020-05-27 11:09:12 UTC,This field-crit bug has not had any updates in nearly 2 months - @aieri is this still an issue?  I'm pretty sure its a slow deployment hitting the TTL on the token used to retrieve the secret_id.
1821209,2020-03-30 09:13:58 UTC,@aieri - this bug still has a field-critical subscription - it would be good to get it moving forward or close it out as the TTL limit being hit due to slowness in the environment.
1821209,2019-10-22 14:38:32 UTC,"They expire after 1hr and are one-shot - i.e. once they have been used, they don't work any longer."
1821209,2019-10-22 14:38:07 UTC,The tokens used to wrap the secret are specific to each unit that needs one.
1821209,2019-10-22 14:20:51 UTC,"@james-page are the tokens relation-specific or global? One thing that surprised me was that re-adding the specific [vault:secrets, swift-storage-zone2:secrets-storage] relation resolved the issue with the other apps as well, but after reading your analysis it starts to make sense."
1821209,2019-10-22 14:08:08 UTC,"@james-page, no totally-unsecure-auto-unlock is set to false."
1821209,2019-10-22 09:09:59 UTC,@aieri are you using totally-unsecure-auto-unlock?  this will cause vault to be ready to start issuing tokens very early in the model deployment time which might exacerbate this issue.
1821209,2019-10-22 08:50:11 UTC,"I have a suspicion that the token is expiring before it gets used; the TTL is set to 1hr, which means the consuming charm must have a hook execution within that time frame or the token will no longer be valid; removing and re-adding the relation causes them to be re-issued, and as its not during the initial deployment, there are less hook executions going on so it all happens < 1hr."
1821209,2019-10-22 08:34:28 UTC,Note that the code that retrieves the secret_id (which is generating the InvalidRequest exception) does not use the vaultlocker configuration file - it directly uses the URL and response-wrapped token presented on the relation.
1821209,2020-03-30 09:13:05 UTC,As detailed in #17 still waiting for feedback from @aieri on whether the general sluggishness of the deployment environment caused the TTL's on the tokens to expire before the secret_id's could be retrieved.
1821209,2019-10-22 08:22:07 UTC,"as a workaround, removing and readding the relation worked for me"
1821209,2019-10-22 08:06:15 UTC,"Sorry, wrong unit log... this one does show the error message:
hvac.exceptions.InvalidRequest: wrapping token is not valid or does not exist"
1821209,2019-10-22 07:53:01 UTC,"I've just hit this, and I bet it's a race condition because over multiple redeploys of the same cloud it only happened once, and only on some units."
1821209,2019-04-01 14:25:29 UTC,Xenial was a customer requirement.
1821209,2019-03-22 06:54:05 UTC,"As an additional observation / question, why is a new deploy being done with Xenial instead of Bionic?"
1821209,2019-03-22 00:39:07 UTC,"The bug is set back to 'new' status. Does that mean that you hit it again?  If so, new logs, please & thanks."
1821209,2019-03-21 22:27:04 UTC,Network config used by FCB to configure spaces in maas.
1821209,2019-03-21 20:20:54 UTC,Thank you for your work on this.
1821209,2019-03-21 17:31:53 UTC,"Please provide a record of the expected cidrs on each space.  I need to interpret the unit ip addresses, network space cidrs, and vips, together, in order to get the full picture (ie. to understand the logical networks in play)."
1821209,2019-03-21 17:06:57 UTC,There is also a proxy in use at this site. So any http/https connection requirements are being added to juju's no-proxy model-config.
1821209,2019-10-22 08:33:33 UTC,I'm highly suspicious of the 10.5.0.13 IP address - that is the same as in the original bug report and its unclear as to where that is actually coming from.
1821213,2019-11-13 17:04:16 UTC,"We upversioned openstack-helm in https://review.opendev.org/#/c/683886, and the new version includes the upstream patch merged at https://review.opendev.org/#/c/673444/"
1821213,2019-10-30 08:36:03 UTC,"Change abandoned by YU CHENGDE (yu.chengde@99cloud.net) on branch: master
Review: https://review.opendev.org/678166
Reason: move to starlingx/openstack-armada-app
abandon the review"
1821213,2019-09-03 21:19:21 UTC,"Since the commit for r/stx.2.0 was not merged in time for the release final compile on August 26, this bug is now re-gated to stx.3.0. The fix should be merged in master only. The review of r/stx.2.0 should be abandoned."
1821213,2019-11-21 18:16:03 UTC,"Horizon errors reported when you attempt metadata update eg. flavor metadata
I would have expected this to be fixed in this recent load..."
1821213,2019-09-05 14:36:03 UTC,"Change abandoned by Don Penney (<email address hidden>) on branch: r/stx.2.0
Review: https://review.opendev.org/678167
Reason: Abandoning per release management request"
1821213,2019-11-21 18:18:03 UTC,It may be fixed upstream but it looks like we still override the config with the old value not including PATCH in this commit: https://review.opendev.org/#/c/684166/
1821213,2020-04-28 01:56:23 UTC,"Fix proposed to branch: r/stx.3.0
Review: https://review.opendev.org/723776"
1821213,2019-12-11 15:14:36 UTC,"As per community review on 12/11, the recommendation is to cherry-pick this fix to r/stx.3.0 for the first maintenance release. Therefore, changing the priority to High (only high priority bugs are cherrypicked after the final compile)."
1821213,2020-01-14 15:34:01 UTC,"Reviewed:  https://review.opendev.org/696035
Committed: https://git.openstack.org/cgit/starlingx/openstack-armada-app/commit/?id=6af1446084817776b76b41bd366da3df2b3855e0
Submitter: Zuul
Branch:    master"
1821213,2020-01-20 18:08:42 UTC,"resolved
verified in 20200115T023003Z
add flavor, update metadata, delete flavor working"
1821213,2020-04-27 16:38:43 UTC,"Zhipeng, This LP is marked as gating for stx.3.0. Please cherry-pick the code changes to the stx.3.0 branch if applicable or add a note explaining why it shouldn't be cherry-picked."
1821213,2019-08-23 14:12:17 UTC,"Reviews posted in starlingx
master: https://review.opendev.org/#/c/678166/
r/stx.2.0: https://review.opendev.org/#/c/678167/"
1821213,2020-08-04 01:59:27 UTC,"Reviewed:  https://review.opendev.org/723776
Committed: https://git.openstack.org/cgit/starlingx/openstack-armada-app/commit/?id=e889f2516227ddb13f8ddb7bb294f184df59b6b9
Submitter: Zuul
Branch:    r/stx.3.0"
1821213,2019-11-26 08:55:55 UTC,"Hi all,"
1821213,2019-08-21 14:44:48 UTC,"The equivalent patch needs to be applied to the starlingx/upstream repo
https://review.opendev.org/gitweb?p=starlingx/upstream.git;a=tree;f=openstack/openstack-helm;h=87344b5097cae1178e44d8448d11b4b716b91f9b;hb=HEAD"
1821213,2019-11-13 17:01:54 UTC,"Change abandoned by Chris Friesen (<email address hidden>) on branch: master
Review: https://review.opendev.org/692071
Reason: This change is no longer necessary, the new version of openstack-helm introduced by https://review.opendev.org/#/c/683886 already includes the change being made here."
1821213,2019-07-30 09:20:55 UTC,"I post the patch in openstack-helm:
https://review.opendev.org/#/c/673444/"
1821213,2019-03-22 18:35:22 UTC,This is a horizon issue and will need to be reported in a horizon launchpad.
1821213,2019-03-22 18:40:08 UTC,"Based on severity, this issue is not deemed gating for stx.
However, the issue needs to be reported to the horizon project so that the community can consider addressing it."
1821213,2019-03-25 17:29:56 UTC,"From Tyler:
There's a good chance this is a result of improper configuration or policy settings in either horizon or nova, which i think would be our issue. I'm doubtful this is broken in upstream horizon as it's pretty basic functionality, i haven't really investigated yet though"
1821213,2019-04-16 13:46:48 UTC,"In horizon update metadata operations continue to fail
eg. Update flavor metadata
eg. Update image metadata"
1821213,2019-04-17 19:25:30 UTC,"In horizon update metadata operations continue to fail
eg. Update flavor metadata
eg. Update image metadata
eg. Edit image operation(s)"
1821213,2019-06-21 12:29:01 UTC,Assigned to Bruce for re-assignment.
1821213,2019-08-09 13:57:58 UTC,"the patch has been merged in upstream, what it takes to make the fix available in StarlingX build?"
1821213,2019-07-15 20:33:50 UTC,"@Yan, do we have any update on this?"
1821213,2019-07-16 13:43:36 UTC,@Yan what response did you expect from community? any background discussion on this issue?
1821213,2019-07-17 01:50:32 UTC,"Need community suggestion on how to config horizon to authorize metadata update/create/delete.
Asked in the community channel on slack, but no response yet."
1821213,2019-07-25 22:17:23 UTC,"The extra property can be set by cmdline on 0724 cengn build, see the attachment."
1821213,2019-07-25 23:53:14 UTC,"On 0717 cengn build, I test it on both CLI and Horizon.
CLI can create or change metadata without porblem,
Horizon can reproduce the problem with 403 error."
1821213,2019-07-30 07:00:11 UTC,"I believe the reason of the bug has found:
The config file /etc/apache2/sites-enabled/000-default.conf in Horizon container, line 17"
1821213,2019-07-16 02:56:11 UTC,"@yong, not yet received response from the comunity."
1821216,2019-07-28 04:17:44 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1821216,2019-05-02 01:01:01 UTC,I wasn't entirely clear in the last post: the problem still persists after addressing your recommendation.
1821216,2019-05-28 16:56:24 UTC,"I think I see the problem, in your IMC config, you have one nic, but have not set it as primary:"
1821216,2019-04-26 18:49:08 UTC,"Hi,"
1821216,2019-05-02 00:49:15 UTC,"I rebuilt, removing the directory you mentioned and got new logs. I've printed the cloud-init-output.log and attached the cloud-init.log:"
1821236,2019-03-22 07:55:29 UTC,stress-ng is a command line application
1821237,2019-03-21 20:24:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1821237,2019-03-23 08:35:04 UTC,It seems that there is a difference in behaviour between Xorg and Wayland session.
1821239,2019-03-29 08:47:26 UTC,"Hello Seth, or anyone else affected,"
1821239,2019-04-12 12:27:35 UTC,Checked contents of the 1.173.5 and confirmed that the new firmware files are present. Marking verifiction as done.
1821239,2019-04-25 10:00:45 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821242,2020-02-19 19:35:43 UTC,Will this be released for LTS (18.04) as well. That was where the bug was found. :)
1821242,2020-02-19 17:56:40 UTC,"I can see this fix is landed in the 0.9.0 release, so this is fixed in Focal and later."
1821242,2019-12-18 13:08:14 UTC,"I see that I triaged this before but without comment. I don't know what I was thinking. I try to always ensure that next steps are clearly communicated when I triage, and I failed at that. Sorry."
1821242,2019-12-17 15:36:45 UTC,"Hi,
any news on this one? Is an update for that package planned using the patch provided?"
1821242,2019-04-03 19:28:27 UTC,We built a package using this patch: https://gitlab.freedesktop.org/realmd/adcli/commit/90c1e96cf3eea8718aa97a6fb97aa2029ef64670 and it fixed the issue.
1821242,2019-04-01 22:34:24 UTC,"But opened here, with trace back. https://gitlab.freedesktop.org/realmd/adcli/issues/17#note_140307"
1821242,2019-04-04 01:12:47 UTC,"To clarify ""fixed the issue:"" It did not fail with the original error, and exited with a `0` exit code. Running the command again return an error saying the computer was not in the domain (as expected)."
1821244,2019-07-04 07:30:15 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/669078"
1821244,2019-09-27 09:05:34 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1821244,2019-09-18 14:45:31 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/669082"
1821244,2019-09-18 14:45:26 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/669072"
1821244,2019-07-04 07:34:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/669082"
1821244,2019-07-04 07:17:32 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/669072"
1821244,2019-09-18 14:45:37 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/669078"
1821244,2019-06-19 21:37:46 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/647603
Reason: I got the functional test to correctly go down the get_stashed_volume_connector path but as noted in the change if the bdm.connection_info is None it's not going to fail as reported in the bug, which asserts that the serialized connection_info is 'null'. Anyway, abandoning again."
1821244,2019-06-19 21:17:15 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/647603
Reason: Couldn't get this to reproduce the issue, but maybe I'm missing something since there aren't enough details in the bug report to reproduce."
1821244,2019-03-25 20:58:53 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/647603"
1821244,2019-03-25 20:28:55 UTC,From discussing this in IRC I remember you said in this case the server was being created with a BDM where source_type=image and the failure in nova-compute during volume create was an OverQuota issue from Cinder.
1821244,2019-06-24 22:47:34 UTC,"Reviewed:  https://review.opendev.org/645352
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9fa03d4d72609b6eb2ace7b89eaf437f94252be0
Submitter: Zuul
Branch:    master"
1821246,2019-04-10 01:21:10 UTC,"Obviously, the API deprecation is the problem."
1821246,2019-04-10 01:58:10 UTC,I see the google photo API has been updated in digikam 6.0.0.  I'll try it.
1821247,2019-11-18 19:03:46 UTC,The upstream 3.5.x branch contains the fix too (currently 3.5.3).
1821247,2019-03-21 21:49:30 UTC,See also https://github.com/jaraco/configparser/issues/17
1821247,2019-03-24 03:57:52 UTC,PPA https://launchpad.net/~dank/+archive/ubuntu/python-fixes/ now contains a python-configparser with that fix applied.
1821247,2019-06-22 14:12:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821249,2019-06-08 08:49:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821251,2020-12-04 16:01:04 UTC,"please add the usual SRU details in the description, thanks"
1821251,2020-12-14 18:37:30 UTC,This bug was fixed in the package debmirror - 1:2.27ubuntu2.20.04.1
1821251,2020-12-13 12:00:04 UTC,"TEST CASE:
1. Deploy fresh (up-to-date) Ubuntu 20.10 (Groovy) machine.
2. apt install -qqy debmirror=1:2.27ubuntu1
3. debmirror -a amd64 -d groovy -s main --nosource --passive --method=http -h archive.ubuntu.com -r ubuntu --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --progress /opt/debmirror
4. echo 'deb file:///opt/debmirror groovy main' > /etc/apt/sources.list.d/file.list
5. apt update # expected E: failed to fetch file:/opt/debmirror/dists/groovy/main/cnf/Commands-amd64  File not found
6. apt install -qqy debmirror=1:2.27ubuntu2.20.10.1
7. debmirror -a amd64 -d groovy -s main --nosource --passive --method=http -h archive.ubuntu.com -r ubuntu --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --progress /opt/debmirror
8. echo 'deb file:///opt/debmirror groovy main' > /etc/apt/sources.list.d/file.list
9. apt update # All packages are up to date."
1821251,2020-12-08 12:21:31 UTC,"TEST CASE:
1. Installed current non-SRU package: apt install debmirror=1:2.27ubuntu1
2. Created a 20.04 Focal mirror: /usr/bin/debmirror -a amd64,i386 -d focal,focal-security,focal-updates,focal-backports -s main,universe,restricted,multiverse --nosource --passive --method=http -h archive.ubuntu.com -r ubuntu --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --progress /opt/debmirror
3. Exposed /opt/debmirror as webroot on test.example.com
4. On a separate node, configured APT to use the mirror, via sources.list such as:
   deb http://test.example.com/ubuntu/ focal main universe restricted multiverse
   deb http://test.example.com/ubuntu/ focal-security main universe restricted multiverse
   deb http://test.example.com/ubuntu/ focal-updates main universe restricted multiverse
5. Tried to use mirror on the newly configured client: apt update
   E: Failed to fetch http://test.example.com/ubuntu/dists/focal/main/cnf/Commands-amd64  404  Not Found [IP: 10.10.10.10 80]
   E: Failed to fetch http://test.example.com/ubuntu/dists/focal-security/main/cnf/Commands-amd64  404  Not Found [IP: 10.10.10.10 80]
   E: Failed to fetch http://test.example.com/ubuntu/dists/focal-updates/main/cnf/Commands-amd64  404  Not Found [IP: 10.10.10.10 80]
   E: Some index files failed to download. They have been ignored, or old ones used instead.
6. Installed SRU package: apt install debmirror=1:2.27ubuntu2.20.04.1
7. Repeated `debmirror` invocation from step 2, in order to pull in cnf files.
8. Repeated `apt update` invocation as from step 5, in order to try using the mirror."
1821251,2020-12-07 17:38:43 UTC,"Hello Jamie, or anyone else affected,"
1821251,2020-12-07 17:37:41 UTC,"Hello Jamie, or anyone else affected,"
1821251,2020-12-07 17:37:14 UTC,"I noticed that the version number is not perfect. Then again, I don't think it makes sense to re-upload just because of that. Let me accept it as is."
1821251,2020-12-07 17:31:47 UTC,"Hey! Ok, so let me help out with the formalities here and then accept the SRU. I'll update this bug with the description of LP: #1906541, as this is the bug number that is referenced in the upload. I'll then mark the other one as a duplicate of this bug. We should be good then!"
1821251,2020-12-04 22:11:21 UTC,"> The bug linked in the changelog of the SRU is this one, not bug #1906541.
"
1821251,2020-12-04 20:54:35 UTC,"> This was handled as a merge in #1892110 and is being handled as an SRU
> in #1906541 with the patch provided in that SRU ticket including
> further upstream commits.
"
1821251,2020-12-04 20:01:29 UTC,This was handled as a merge in #1892110 and is being handled as an SRU in #1906541 with the patch provided in that SRU ticket including further upstream commits.
1821251,2020-12-14 18:24:17 UTC,"The verification of the Stable Release Update for debmirror has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821251,2020-11-26 05:59:15 UTC,This bug was fixed in the package debmirror - 1:2.33ubuntu1
1821251,2020-12-14 18:24:11 UTC,This bug was fixed in the package debmirror - 1:2.27ubuntu2.20.10.1
1821251,2020-09-10 15:33:50 UTC,How do i patch the debmirror file please??
1821251,2019-03-22 13:25:46 UTC,Thanks for this Jamie. I just had the same problem with my local mirror here at home.
1821251,2019-03-22 13:31:37 UTC,"Yes Iain, I don't mirror ports. Thanks for the updated patch. :)"
1821251,2019-03-22 22:39:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821251,2019-03-22 23:25:26 UTC,For what its worth this worked on my Ubuntu 18.04 with debmirror installed.
1821251,2019-03-23 10:40:41 UTC,"Thanks.  I applied Jamie's patch, and took a slightly different approach for the problem that Iain reported:"
1821251,2020-11-19 12:30:58 UTC,"For completeness sake here, there is a merge request at https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110 which rebases the Ubuntu changes on top of the latest upstream debmirror version, in turn including the required `command-not-found` changes."
1821251,2020-03-17 14:47:38 UTC,Would be nice to have this into Ubuntu 20.04 so it can mirror itself...
1821251,2020-04-27 20:31:27 UTC,Please change status back to Confirmed
1821251,2020-05-05 09:17:47 UTC,I applied this patch and it still doesn't work. Still no cnf directories.
1821251,2020-05-05 10:54:55 UTC,The patch is not correct.
1821251,2020-05-28 09:04:28 UTC,"This may be patched upstream, but it is not present in the version which today installs on Focal 20.04 (reported as 1:2.27ubuntu1)."
1821251,2019-09-09 04:21:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821258,2019-05-15 04:22:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821264,2019-04-03 19:36:46 UTC,backtrace
1821264,2019-04-03 20:56:09 UTC,apport logs
1821264,2019-04-03 20:14:55 UTC,Valgrind output
1821264,2019-04-03 19:36:49 UTC,backtrace
1821264,2019-04-03 19:36:43 UTC,backtrace
1821264,2019-04-03 19:06:33 UTC,"I googled and found you could get more information with running the gnome-software --verbose.  Attaching that file in case it helps.  There was no gnome-software-dbg or gnome-software-dbgsym to install and or download, I checked."
1821264,2019-04-03 19:29:40 UTC,you can maybe try to catch the segfault using apport and use apport-retrace on the file from /var/crash
1821264,2019-04-03 19:17:25 UTC,"dmesg -T | grep seg
[Wed Apr  3 14:52:31 2019] pool[18867]: segfault at ffffffffffffffb8 ip 00007f8bf01e1b97 sp 00007f8bca5b0938 error 5 in libappstream-glib.so.8.0.6[7f8bf01c5000+42000]
[Wed Apr  3 14:57:24 2019] pool[25609]: segfault at ffffffffffffffb8 ip 00007fa7ef7d3b97 sp 00007fa7ccae3938 error 5 in libappstream-glib.so.8.0.6[7fa7ef7b7000+42000]
[Wed Apr  3 14:59:40 2019] pool[25764]: segfault at ffffffffffffffb8 ip 00007ff8e3d7fb97 sp 00007ff8a320c938 error 5 in libappstream-glib.so.8.0.6[7ff8e3d63000+42000]"
1821264,2019-04-03 19:08:37 UTC,Backtrace is not working since there are no debug symbols example attached
1821264,2019-04-04 18:07:27 UTC,"Customer installed U18.04 Dell OEM and that works as expected.  We can drop the severity.  I installed the Base Dell OEM image to confirm the issue.  When I first booted the issue was not there.  Then when I loaded the updates/upgrades and rebooted the segfaults came back.  I have nothing else installed on the image.  Let me know if you need me to redo the valgrind, apptrace, and or backtraces.  Looks like this issue is tied to U16"
1821264,2019-04-03 19:36:13 UTC,I ran backtrace with --verbose so hopefully that helps as well attaching
1821264,2019-04-02 13:58:26 UTC,Any updates on this bug?  What is needed from the customer or Dell to isolate this?
1821264,2019-04-03 15:43:56 UTC,Could you install the debug pacakges as described on the wiki? The issue looks somewhat similar to bug #1778135
1821264,2019-04-03 18:43:02 UTC,"I loaded the default debug symbols and I see Reading symbols from gnome-software... (no debugging symbols found)...done.  I then tried to load all and still I receive no debug symbols.  It is not that I didn't load them, it is I have no idea what the debug symbol for gnome-software is.  Can you confirm what packages I need to load?"
1821264,2019-03-22 09:30:22 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1821264,2019-03-22 19:25:12 UTC,attaching now
1821264,2019-03-22 19:30:02 UTC,Is this related too https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1781996
1821264,2019-03-28 19:27:26 UTC,Is there any updates on this bug?  Anything you need me to collect?
1821266,2019-06-27 08:07:27 UTC,"When this report was written, 'juju credentials' only displayed local credentials. It will soon cater for both. It is best to qualify credentials on the command output. Also in multi-cloud scenario, the credentials/clouds that are desired may not necessarily be on the local client but could be located  remotely on the controller."
1821266,2019-07-15 03:22:23 UTC,"When adding a model, juju will look at both local and remote credentials."
1821267,2019-06-21 02:47:17 UTC,Apparently Email notice is existing functionality and code was not changed in this patch.
1821267,2019-06-23 04:41:18 UTC,"Reviewed:  https://reviews.mahara.org/9652
Committed: https://git.mahara.org/mahara/mahara/commit/18b78eab3ab3caa13bdc4b850fa7c47e2453453d
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1821267,2019-06-23 04:28:29 UTC,Looking into the following bugs:
1821267,2019-03-22 01:22:15 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9650"
1821267,2019-03-22 02:43:24 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9652"
1821267,2019-06-21 02:42:56 UTC,"Commit hash: c924173dfcc42acbbb447d1cfe8ed7c32a6767a6	97607ef61eef076b3c8fc445ce9a343e8d9641df
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw | Default raw | Ocean | Modern | Primary school"
1821268,2019-08-27 22:41:06 UTC,Thanks!!
1821268,2019-04-27 14:43:37 UTC,"Fixed in revision eccadd92fb722de5226ad4ac16964e128766a517
https://git.launchpad.net/kicad/patch/?id=eccadd92fb722de5226ad4ac16964e128766a517"
1821268,2019-04-27 14:44:11 UTC,And also pushed to 5.1 as
1821268,2019-04-14 20:22:26 UTC,"The OnSize handler in dialog_lib_edit_pin_table.cpp should be looked at.
Nowhere else the columns are adjusted and the event is skipped only if the width has changed."
1821268,2019-03-25 15:34:59 UTC,"I'm also seeing strange behaviour on Mac.
1) Increasing dialog size vertically doesn't expand the grid to fit.
2) Resizing horizontally size corrects the grids vertical size.
3) Decreasing the dialogs vertical size ""truncates"" the bottom items in the grid that are no longer visible."
1821268,2019-03-25 14:03:09 UTC,This is strange.  It only happens when I resize the dialog vertically.  The issue doesn't occur when resizing the dialog horizontally.  I only tested this on windows so I'm not sure it effects all platforms.
1821268,2019-03-25 15:59:20 UTC,Linux is also affected.
1821269,2019-05-23 03:02:40 UTC,Please do a test:
1821269,2019-05-22 11:18:02 UTC,Please collect one more log:
1821269,2019-05-22 23:44:16 UTC,@hui.wang
1821269,2019-05-22 09:10:06 UTC,"@hui.wang
Thank you for reply."
1821269,2019-05-23 05:20:35 UTC,"Sorry. I am not familiar with Linux. So I don't know how to modify bootargs.
Can you explain me little more kindly? I'm sorry to bother you."
1821269,2019-05-22 04:17:13 UTC,[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]
1821269,2019-03-22 07:19:49 UTC,Thank you reply.
1821269,2019-03-22 02:57:20 UTC,For a 4-pole combo jack to work you need:
1821269,2019-05-23 05:33:26 UTC,Edit /etc/default/grub and add them to the line GRUB_CMDLINE_LINUX_DEFAULT...
1821269,2019-05-22 05:18:50 UTC,"@jimnong,"
1821269,2019-05-23 07:15:34 UTC,"@Ji-min,"
1821269,2019-05-23 06:55:17 UTC,@vanvugt
1821269,2019-05-24 03:46:43 UTC,"checked the alsa-info.txt in #14, found the lifebook-extmic doesn't take effect, ""model=liefbook-extmic"" was added to kernel-4.19 but we are using kerel-4.15. So please test this dkms, if headset-mic still doesn't work, please generate an alsa-info.txt too."
1821269,2020-05-05 14:50:59 UTC,My Notebook is a Acer Aspire E5-573G-72UF
1821269,2020-05-05 14:50:58 UTC,My Notebook is a Acer Aspire E5-573G-72UF
1821269,2020-05-05 14:41:42 UTC,Hello!
1821269,2020-03-27 01:43:43 UTC,"Does it have a workaround for manjaro linux, since I cant install .deb packages in manjaro?"
1821269,2019-07-29 04:17:17 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1821269,2019-05-29 04:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821269,2019-05-28 08:21:39 UTC,"It is fixed from kernel driver, So all linux distros have this issue. We plan to send the patch to upstream kernel and cc stable-kernel, after this patch is merged to stable-kernel, I guess all linux distros will have this fix automatically."
1821269,2019-05-28 10:26:05 UTC,I will take your opinion. Thank you.
1821269,2019-05-27 04:33:54 UTC,"Please install this dkms, reboot and redo the test."
1821269,2019-05-24 11:26:07 UTC,@hui.wang
1821269,2019-05-24 07:23:10 UTC,Reported to realtek.
1821269,2019-05-24 05:39:10 UTC,"I installed oem-audio-hda-daily-dkms_0.1_all.deb
And rebooted my PC and plugged in apple earset.
But earset's mic doesn't work too."
1821269,2019-05-28 05:31:33 UTC,@hui.wang
1821269,2019-05-23 10:32:43 UTC,@hui.wang
1821271,2019-04-17 09:10:56 UTC,"Verified bionic-proposed version 4.15.0-48.51 and cosmic-proposed version 4.18.0-18.19, WiFi interface recognized and connected automatically."
1821271,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1821271,2019-05-14 22:57:52 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821271,2019-04-23 21:35:02 UTC,This bug was fixed in the package linux - 4.18.0-18.19
1821271,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1821271,2019-04-04 18:01:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1821271,2019-03-22 03:15:55 UTC,"02:00.0 Network controller [0280]: Intel Corporation Device [8086:2526] (rev 29)
 Subsystem: Intel Corporation Device [8086:4018]"
1821271,2019-04-04 18:04:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1821272,2019-03-22 04:22:35 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1821272,2019-04-01 08:22:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821272,2020-04-30 13:30:11 UTC,Related: bug 1728616
1821275,2019-07-30 09:15:25 UTC,https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=1f97d91bf4668ecce0637f9b46916ab18eb1e06a
1821275,2019-07-23 03:49:53 UTC,This is blocking the ubuntu_zfs_fstest as well.
1821276,2019-04-23 21:35:02 UTC,This bug was fixed in the package linux - 4.18.0-18.19
1821276,2019-04-04 18:04:28 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1821276,2019-04-04 18:02:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1821276,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1821276,2019-05-14 22:57:56 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821281,2021-02-24 03:36:22 UTC,"I think it would be safe to say we don't care about Wayland support on Ubuntu 14.04. And the packages haven't been updated since 2018, which supports that."
1821284,2019-09-13 16:42:20 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.
1821284,2019-07-04 06:16:35 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/669058"
1821284,2019-06-12 06:24:15 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/664792"
1821284,2019-03-22 07:17:17 UTC,"In the cinder API reference, while the title is ""Group Type Specs"", ""group spec for a group type"" is used in the description. ""group spec"" sounds better to me."
1821284,2019-07-08 07:51:00 UTC,"Change abandoned by Vishal Manchanda (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/669058"
1821284,2019-07-03 16:21:06 UTC,"Reviewed:  https://review.opendev.org/664792
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=6c8674dc5d14c6a3d5bfcdadfce49a55232ca2ed
Submitter: Zuul
Branch:    master"
1821286,2019-03-22 07:40:39 UTC,"StacktraceTop:
 ?? ()
 SingleApplicationPrivate::terminate (signum=1) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:116
 <signal handler called>
 __GI___poll (fds=fds@entry=0x7f238873fcb8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
 poll (__timeout=-1, __nfds=1, __fds=0x7f238873fcb8) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46"
1821286,2019-07-23 14:17:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821286,2020-10-11 12:46:15 UTC,"Could you please retest the package of version 0.6.0+git20191001-2 from current release, Ubuntu 20.04? It is unclear for me how to reproduce the issue. I have checked the application in fresh Ubuntu environment, and it worked fine with no crashes."
1821290,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1821290,2019-03-22 07:46:14 UTC,"The first two patches, 4d4b0c52 and d1dd4211, are in 5.0-rc2.
The other two are in 5.1-rc1."
1821290,2019-04-17 07:28:10 UTC,We have 136824ef and da484d00 in Disco kernel through stable kernel updates.
1821290,2019-04-25 22:32:28 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1821290,2019-04-29 16:04:11 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1821290,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1821290,2019-05-14 22:54:17 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821293,2019-04-03 12:50:07 UTC,Have you checked /var/crash for apache crash files?
1821293,2019-04-01 11:08:27 UTC,"Hello Claudio,"
1821293,2019-04-01 10:44:47 UTC,"IIRC apache by default does not store dumps (to avoid exploiting remotely to fill disks or anything like it).
But it can be enabled [1][2]"
1821293,2019-06-08 04:17:36 UTC,[Expired for apache2 (Ubuntu) because there has been no activity for 60 days.]
1821293,2019-03-25 10:25:16 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1821293,2019-04-05 12:27:57 UTC,"Nothing found in /var/crash, enabled code dump but nothing happens:"
1821293,2019-03-29 08:37:44 UTC,"Today the same problem, no data added to /var/log/apache2/access.log, but in /var/log/apache2/error.log I found:"
1821293,2019-04-08 10:18:06 UTC,"The log holds nothing obvious that I'd see, if anything I wonder if something is overheating. 115 °C is really high for most components.
Hhave you tried to enable apache core dumps as I asked in comment #4"
1821294,2019-03-28 21:09:21 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1821298,2019-03-22 10:49:50 UTC,Thank you for your bug report. Could you add a file example to the bug?
1821298,2019-03-22 12:19:56 UTC,"You can find it here:
https://github.com/giampierosalvi/slides_with_video"
1821298,2019-05-21 15:04:35 UTC,It sounds a bit similar to https://gitlab.gnome.org/GNOME/evince/issues/1021 upstream
1821299,2019-03-23 00:43:14 UTC,"Hi Piotrrr,"
1821299,2019-03-25 10:40:27 UTC,"Hi Miguel,"
1821302,2019-03-22 09:00:03 UTC,Here's the strace output when trying to run the CLI
1821303,2020-05-06 10:23:44 UTC,"@Balazs, yes, you pointed to the right code. Sorry for not pasting the permanent links at first time."
1821303,2020-05-04 13:31:06 UTC,@Maciej: I'm trying to follow the problem you described in the report. Unfortunately you github links are not perma links and now the manage/cmd links are not pointing to the code you wanted to point. I guess the correct perma link is [1] and [2].
1821305,2019-03-22 09:30:07 UTC,This change was made by a bot.
1821305,2019-04-01 07:04:02 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc2 kernel [0]."
1821305,2019-04-29 14:21:18 UTC,"Hi,"
1821305,2019-04-29 15:19:52 UTC,working kern.log
1821306,2019-04-11 15:11:01 UTC,This was fixed with commit 957d116fe343bc99e59862b067b1b7d21ebb71f7 (see https://review.openstack.org/#/c/649650/).
1821307,2019-12-12 10:05:27 UTC,"os.register_at_fork(*, before=None, after_in_parent=None, after_in_child=None)
Register callables to be executed when a new child process is forked using os.fork() or similar process cloning APIs. The parameters are optional and keyword-only. Each specifies a different call point."
1821307,2021-01-09 04:44:15 UTC,Look like i am seeing same error in my compute (nova-compute) logs - https://bugs.launchpad.net/nova/+bug/1910837
1821307,2019-12-20 09:21:48 UTC,"GLOB sdist-make: /Users/steveguan/code/OpenStack/oslo.policy/setup.py
py37 inst-nodeps: /Users/steveguan/code/OpenStack/oslo.policy/.tox/.tmp/package/1/oslo.policy-2.4.2.dev1.zip
py37 installed: alabaster==0.7.12,appdirs==1.4.3,Babel==2.7.0,bandit==1.5.1,certifi==2019.11.28,cffi==1.13.2,chardet==3.0.4,cliff==2.16.0,cmd2==0.8.9,coverage==4.5.4,cryptography==2.8,debtcollector==1.22.0,decorator==4.4.1,docutils==0.15.2,dogpile.cache==0.9.0,dulwich==0.19.14,extras==1.0.0,fixtures==3.0.0,flake8==2.6.2,future==0.18.2,gitdb2==2.0.6,GitPython==3.0.5,hacking==1.1.0,idna==2.8,imagesize==1.1.0,iso8601==0.1.12,Jinja2==2.10.3,jmespath==0.9.4,jsonpatch==1.24,jsonpointer==2.0,keystoneauth1==3.18.0,linecache2==1.0.0,MarkupSafe==1.1.1,mccabe==0.5.3,mock==3.0.5,mox3==0.28.0,msgpack==0.6.2,munch==2.5.0,netaddr==0.7.19,netifaces==0.10.9,openstackdocstheme==1.31.2,openstacksdk==0.39.0,os-client-config==1.33.0,os-service-types==1.7.0,oslo.config==6.12.0,oslo.context==2.23.0,oslo.i18n==3.25.0,oslo.policy==2.4.2.dev1,oslo.serialization==2.29.2,oslo.utils==3.42.1,oslotest==3.8.1,packaging==19.2,pbr==5.4.4,prettytable==0.7.2,pycodestyle==2.0.0,pycparser==2.19,pyflakes==1.2.3,Pygments==2.5.2,pyparsing==2.4.5,pyperclip==1.7.0,python-mimeparse==1.6.0,python-subunit==1.3.0,pytz==2019.3,PyYAML==5.2,reno==2.11.3,requests==2.22.0,requests-mock==1.6.0,requestsexceptions==1.4.0,rfc3986==1.3.2,six==1.13.0,smmap2==2.0.5,snowballstemmer==2.0.0,Sphinx==2.2.2,sphinxcontrib-apidoc==0.3.0,sphinxcontrib-applehelp==1.0.1,sphinxcontrib-devhelp==1.0.1,sphinxcontrib-htmlhelp==1.0.2,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.2,sphinxcontrib-serializinghtml==1.1.3,stestr==2.5.1,stevedore==1.31.0,testtools==2.3.0,traceback2==1.4.0,unittest2==1.1.0,urllib3==1.25.7,voluptuous==0.11.7,wcwidth==0.1.7,wrapt==1.11.2
py37 run-test-pre: PYTHONHASHSEED='727722955'
py37 run-test: commands[0] | stestr run --slowest
{0} oslo_policy.tests.test_checks.CheckRegisterTestCase.test_register_check_decorator [0.001768s] ... ok
{0} oslo_policy.tests.test_checks.FalseCheckTestCase.test_call [0.000564s] ... ok
{0} oslo_policy.tests.test_checks.GenericCheckTestCase.test_constant_string_mismatch [0.004352s] ... ok
{1} oslo_policy.tests.test_checks.AndCheckTestCase.test_call_all_false [0.002167s] ... ok
{1} oslo_policy.tests.test_checks.GenericCheckTestCase.test_constant_literal_mismatch [0.001790s] ... ok
{1} oslo_policy.tests.test_checks.OrCheckTestCase.test_add_check [0.000673s] ... ok
{1} oslo_policy.tests.test_checks.OrCheckTestCase.test_call_first_true [0.000762s] ... ok
{1} oslo_policy.tests.test_checks.OrCheckTestCase.test_pop_check [0.000589s] ... ok
{0} oslo_policy.tests.test_checks.GenericCheckTestCase.test_deep_credentials_dictionary_lookup [0.002038s] ... ok
{1} oslo_policy.tests.test_checks.RoleCheckTestCase.test_format_value [0.001964s] ... ok
{0} oslo_policy.tests.test_checks.NotCheckTestCase.test_call_false [0.000896s] ... ok
{1} oslo_policy.tests.test_checks.RoleCheckTestCase.test_no_roles_case [0.001597s] ... ok
{1} oslo_policy.tests.test_checks.TrueCheckTestCase.test_str [0.000528s] ... ok
{0} oslo_policy.tests.test_checks.RoleCheckTestCase.test_accept [0.001403s] ... ok
{0} oslo_policy...."
1821307,2019-12-11 05:19:54 UTC,"➜  nova git:(master) tox -e  py37  nova.tests.functional.test_servers
py37 develop-inst-nodeps: /home/steveguan/code/Openstack/nova
py37 installed: alembic==1.3.1,amqp==2.5.2,appdirs==1.4.3,attrs==19.3.0,automaton==1.17.0,Babel==2.7.0,bandit==1.6.2,bcrypt==3.1.7,cachetools==3.1.1,castellan==1.4.0,certifi==2019.11.28,cffi==1.13.2,chardet==3.0.4,cliff==2.16.0,cmd2==0.8.9,colorama==0.4.1,coverage==4.5.4,cryptography==2.8,cursive==0.2.2,ddt==1.2.2,debtcollector==1.22.0,decorator==4.4.1,dnspython==1.15.0,dogpile.cache==0.9.0,eventlet==0.25.1,extras==1.0.0,fasteners==0.14.1,fixtures==3.0.0,flake8==2.6.2,future==0.18.2,futurist==1.10.0,gabbi==1.49.0,gitdb2==2.0.6,GitPython==3.0.5,greenlet==0.4.15,hacking==1.1.0,idna==2.8,importlib-metadata==1.1.0,iso8601==0.1.12,Jinja2==2.10.3,jmespath==0.9.4,jsonpatch==1.24,jsonpath-rw==1.4.0,jsonpath-rw-ext==1.2.2,jsonpointer==2.0,jsonschema==3.2.0,keystoneauth1==3.18.0,keystonemiddleware==7.0.1,kombu==4.6.6,linecache2==1.0.0,lxml==4.4.2,Mako==1.1.0,MarkupSafe==1.1.1,mccabe==0.5.3,microversion-parse==0.2.1,mock==3.0.5,monotonic==1.5,more-itertools==8.0.0,mox3==0.28.0,msgpack==0.6.2,munch==2.5.0,netaddr==0.7.19,netifaces==0.10.9,networkx==2.4,-e git+https://github.com/openstack/nova.git@2f31c8d1b97c2b64581d8f824b6547f93dfd94fb#egg=nova,numpy==1.17.4,openstacksdk==0.38.0,os-brick==2.10.0,os-client-config==1.33.0,os-resource-classes==0.5.0,os-service-types==1.7.0,os-traits==2.0.0,os-vif==1.17.0,os-win==4.3.2,os-xenapi==0.3.4,osc-lib==1.14.1,oslo.cache==1.38.0,oslo.concurrency==3.31.0,oslo.config==6.12.0,oslo.context==2.23.0,oslo.db==5.0.2,oslo.i18n==3.25.0,oslo.log==3.45.0,oslo.messaging==10.4.0,oslo.middleware==3.38.1,oslo.policy==2.4.0,oslo.privsep==1.33.3,oslo.reports==1.30.0,oslo.rootwrap==5.16.1,oslo.serialization==2.29.2,oslo.service==1.40.2,oslo.upgradecheck==0.3.2,oslo.utils==3.42.1,oslo.versionedobjects==1.36.1,oslo.vmware==2.34.1,oslotest==3.8.1,osprofiler==2.9.0,ovs==2.11.0,ovsdbapp==0.18.0,packaging==19.2,paramiko==2.6.0,Paste==3.2.3,PasteDeploy==2.0.1,pbr==5.4.4,pluggy==0.13.1,ply==3.11,prettytable==0.7.2,psutil==5.6.7,psycopg2==2.8.4,py==1.8.0,pyasn1==0.4.8,pyasn1-modules==0.2.7,pycadf==2.10.0,pycodestyle==2.5.0,pycparser==2.19,pydot==1.4.1,pyflakes==1.2.3,pyinotify==0.9.6,PyJWT==1.7.1,PyMySQL==0.9.3,PyNaCl==1.3.0,pyOpenSSL==19.1.0,pyparsing==2.4.5,pyperclip==1.7.0,pypowervm==1.1.24,pyroute2==0.5.7,pyrsistent==0.15.6,pytest==5.3.1,python-barbicanclient==4.9.0,python-cinderclient==5.0.0,python-dateutil==2.8.1,python-editor==1.0.4,python-glanceclient==2.17.0,python-ironicclient==3.1.0,python-keystoneclient==3.22.0,python-mimeparse==1.6.0,python-neutronclient==6.14.0,python-subunit==1.3.0,pytz==2019.3,PyYAML==5.2,repoze.lru==0.7,requests==2.22.0,requests-mock==1.6.0,requestsexceptions==1.4.0,retrying==1.3.3,rfc3986==1.3.2,Routes==2.4.1,simplejson==3.17.0,six==1.13.0,smmap2==2.0.5,sortedcontainers==2.1.0,SQLAlchemy==1.3.11,sqlalchemy-migrate==0.13.0,sqlparse==0.3.0,statsd==3.3.0,stestr==2.5.1,stevedore==1.31.0,suds-jurko==0.6,taskflow==3.8.0,Tempita==0.5.2,tenacity==6.0.0,testresources==2.0.1,testscenarios==0.5.0,testtools==2.3.0,tooz==1.67.0,traceback2==1.4.0,unittest2==1.1.0,urllib3==1.25.7,vine==1.3.0,vo..."
1821307,2019-12-20 09:22:20 UTC,"this error is gone, shall we close this issue"
1821310,2019-09-19 14:59:27 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1821310,2019-03-22 15:45:52 UTC,"Yes it is always created even if the disk is not a boot disk. Because based on the RAID configuration other disks can still end up with GRUB installed to allow for failure of a RAID disk, and keeping the system still bootable."
1821310,2019-03-22 13:47:13 UTC,"This is actually a UI error, it should show as it will be creating part2 not part1. That is because a disk that uses a GPT partition always reserves part1 for a bios_boot partition. That partition is not modifiable by the user or useful in anyway so its not presented in the UI or the API."
1821310,2019-03-22 15:26:44 UTC,"Oh. Well, I don't think the solution is to change the UI to show that part2 will be created. It's still very confusing that there's no part1. Even though the BIOS/EFI partitions can't be modified, it should be shown, so that it's clear what's happening."
1821311,2019-03-23 00:20:30 UTC,This bug should be filed against python-openstackclient
1821311,2019-08-29 08:10:30 UTC,I created storyboard for that: https://storyboard.openstack.org/#!/story/2006473
1821313,2019-03-22 13:12:42 UTC,Wireshark's use of debconf is standard:
1821313,2019-03-22 13:33:45 UTC,"As just discussed on ""Unbreakable Snapcraft"", we should neuter debconf so we never get prompts, regardless of whether the scripts respect DEBIAN_FRONTEND=noninteractive. One approach would be to replace /usr/share/debconf/confmodule with shell code that for any called function returns 0."
1821313,2019-03-22 19:52:40 UTC,"Neutering Debconf is a bit heavy-handed, and has literally never been necessary on Debian or Ubuntu buildds, so I'm not sure why Snapcraft would be special here.  On buildd chroots, we set debconf to priority=critical and frontend=noninteractive, and I don't recall ever having an issue with that in the last decade or two."
1821313,2019-06-14 14:58:54 UTC,https://github.com/snapcore/snapcraft/pull/2600
1821315,2019-05-10 20:27:11 UTC,Reported upstream as
1821315,2020-04-11 18:49:47 UTC,This bug was fixed in the package brisk-menu - 0.6.0-1ubuntu1
1821319,2019-03-22 14:50:45 UTC,The fact that kicad imports pins as stacked that are not connected in eagle is definitely a bug. I however disagree with the proposed solution. (I find it strange that connecting multiple footprint pins to the same symbol pins would not result in them being connected in eagle. Seems like an eagle bug to be honest. Not sure if we should replicate that behavior in kicad.)
1821319,2019-03-22 15:48:03 UTC,"@Rene- Can you expand on how connecting NC pins can be uniquely useful?  As in, if you want the pins to connect, why would you set them to NC type?"
1821319,2019-04-09 14:20:50 UTC,Generally i feel that not being able to connect an existing pin would be a mistake. It just does not feel quite right to change that behavior just to make eagle import easier. (KiCads core features should trump any import tools requirements. At least in my opinion.)
1821319,2019-06-10 00:04:56 UTC,"Fixed in revision bc096dc4ee9bf2a358d3690f69db52d652670a54
https://git.launchpad.net/kicad/patch/?id=bc096dc4ee9bf2a358d3690f69db52d652670a54"
1821320,2019-06-10 04:17:34 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1821320,2019-04-10 14:07:18 UTC,Also do:
1821320,2019-04-10 14:09:45 UTC,I can confirm this is not an issue:
1821320,2019-04-10 13:34:54 UTC,"I believe the problem is that 'maas' also refers to the maas-cli. When you are calling maas, you are not calling the one installed by the snap package."
1821321,2020-10-02 18:33:10 UTC,Same issue here. The command I use is:
1821322,2019-04-10 13:35:20 UTC,"I believe the problem is that 'maas' also refers to the maas-cli. When you are calling maas, you are not calling the one installed by the snap package."
1821322,2019-04-10 14:07:48 UTC,What is the output of:
1821322,2019-04-10 14:10:06 UTC,"roaksoax@rivals:~/project$ sudo maas config
Mode: none"
1821322,2019-04-10 14:10:20 UTC,I can confirm that this is not a problem.
1821322,2019-06-10 04:17:34 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1821323,2019-09-19 14:54:43 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1821324,2019-09-19 14:54:46 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1821325,2019-09-19 14:54:48 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1821328,2019-03-22 11:41:27 UTC,Config file
1821329,2019-09-19 15:04:35 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1821331,2019-09-19 15:04:38 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1821332,2019-09-19 15:04:40 UTC,"This bug has not seen any activity in the last 6 months, so it is being automatically closed."
1821341,2019-04-23 23:53:20 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1821341,2019-06-23 04:19:03 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1821343,2019-04-22 20:24:34 UTC,Verified according to test case in description for xenial:
1821343,2019-04-22 20:34:48 UTC,"There's a failing autopkgtest for gnupg2 that flagged this openldap update for cosmic, but openldap looks fine."
1821343,2019-04-22 20:20:56 UTC,Verified according to test case in description for bionic:
1821343,2019-04-22 21:38:06 UTC,gnupg2 autopkgtest failure due to bug 1825186
1821343,2019-04-16 09:39:45 UTC,"Hello Heitor, or anyone else affected,"
1821343,2019-04-23 09:05:05 UTC,"The verification of the Stable Release Update for openldap has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821343,2019-04-29 11:02:23 UTC,This bug was fixed in the package openldap - 2.4.45+dfsg-1ubuntu1.2
1821343,2019-04-29 11:08:05 UTC,This bug was fixed in the package openldap - 2.4.42+dfsg-2ubuntu3.5
1821343,2019-04-22 20:17:39 UTC,Verified according to test case in description for cosmic:
1821343,2019-04-23 09:04:56 UTC,This bug was fixed in the package openldap - 2.4.46+dfsg-5ubuntu1.2
1821343,2019-04-22 12:45:41 UTC,"Hello Heitor, or anyone else affected,"
1821343,2019-04-10 07:37:02 UTC,This bug was fixed in the package openldap - 2.4.47+dfsg-3ubuntu2
1821343,2019-03-22 16:42:49 UTC,"Hello Hector,"
1821343,2019-04-22 12:40:36 UTC,"Hello Heitor, or anyone else affected,"
1821343,2019-04-09 13:27:03 UTC,Sponsored in disco.
1821343,2019-04-09 13:14:07 UTC,debdiff v2 with fixed author information
1821343,2019-04-09 12:17:12 UTC,"@slashd I don't think we need anything special for systemd in the debian/{control,rules} files, since we're not shipping full systemd support with this. The slapd service is still handled by systemd-sysv-generator(8), so there's no service units that we need to include or activate in dh_systemd rules."
1821343,2019-04-08 16:02:31 UTC,"I've been doing some research on how we could implement a proper systemd unit file for slapd, and came up with interesting results."
1821343,2019-03-22 18:39:46 UTC,"The sysv init script does some funky parsing of configuration files that might give us some trouble in an independent service file. I'll check if we can't work around that and do away with the sysv init script altogether, otherwise we might as well go with the drop-in override since the new service wouldn't be much different from it."
1821343,2019-03-22 18:10:43 UTC,"> Do you need a whole service file for this? I thought you could achieve
> the same with a drop-in that just overrides the required keys
"
1821343,2019-03-22 16:23:16 UTC,"The attachment ""debdiff for disco"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1821347,2019-04-15 19:37:42 UTC,Fixed merged a while ago https://review.openstack.org/647504 not sure why this bug still open. Closing
1821347,2019-03-28 20:54:47 UTC,"Reviewed:  https://review.openstack.org/647504
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=febab2bf8888ed1ad7d20ed4f3b2a7d6dd10b415
Submitter: Zuul
Branch:    master"
1821347,2019-03-25 15:14:07 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/647504"
1821349,2019-04-18 22:23:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821349,2019-04-19 21:17:26 UTC,Also experienced this issue upgrading from 18.10 (stable) to 19.04 (stable).  This seems like a minor issue that should not halt the entire upgrade process in its tracks.
1821350,2019-03-22 13:33:11 UTC,apport information
1821350,2019-03-22 13:33:15 UTC,apport information
1821350,2019-03-22 13:33:12 UTC,apport information
1821350,2019-03-22 13:33:18 UTC,apport information
1821350,2019-03-22 13:33:00 UTC,apport information
1821350,2019-03-22 14:53:47 UTC,but apparently still an issue with the nouveau driver
1821350,2019-03-25 05:17:08 UTC,I don't find any suspend related message from log in #17.
1821350,2019-03-22 13:33:09 UTC,apport information
1821350,2019-03-22 14:20:10 UTC,Worked with doko on IRC and the nvidia 418 driver (currently in -proposed) fixes this.
1821350,2019-03-22 13:33:08 UTC,apport information
1821350,2019-03-22 13:32:56 UTC,apport information
1821350,2019-03-22 13:33:05 UTC,apport information
1821350,2019-03-22 13:33:03 UTC,apport information
1821350,2019-03-22 13:33:01 UTC,apport information
1821350,2019-03-22 13:32:59 UTC,apport information
1821350,2019-03-22 13:32:58 UTC,apport information
1821350,2019-03-26 14:42:22 UTC,"On 25.03.19 06:17, Kai-Heng Feng wrote:

> I don't find any suspend related message from log in #17.
"
1821350,2019-03-22 13:32:54 UTC,apport information
1821350,2019-03-22 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821350,2019-03-22 13:33:07 UTC,apport information
1821350,2019-03-27 02:34:30 UTC,"Do you mean you can no longer login GUI after lid open? Do you still have the access to the system after that? For example, is it possible to login your laptop via ssh over Wi-Fi/ethernet? If it's not even available, you may still paste /var/log/syslog of the last boot."
1821351,2019-03-22 13:42:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821351,2019-03-26 03:49:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821353,2019-05-28 15:51:19 UTC,Marking this invalid since DASDs can't be used directly without a partition table.
1821353,2019-05-29 07:49:48 UTC,"------- Comment From <email address hidden> 2019-05-29 03:46 EDT-------
IBM bugzilla status -> closed, set to Invalid by Canonical"
1821353,2019-04-02 08:09:41 UTC,"------- Comment From <email address hidden> 2019-04-02 04:03 EDT-------
(In reply to comment #12)

> @Peter
> I guess the question is, whether or not, we should be trying to use dasd as
> a bcache device at all.
"
1821353,2019-04-01 15:31:27 UTC,There are no restrictions on non-dasd devices so we can update curtin to ensure that we don't allow creating bcache devices on dasd without a partition.
1821353,2019-04-01 15:14:22 UTC,"@Peter
I guess the question is, whether or not, we should be trying to use dasd as a bcache device at all. Or like create a partition table, and use the partition as a bcache device then? In that case should the make-bcache fail on the full dasd device, as shows in the reproducer steps?"
1821353,2019-03-22 14:13:33 UTC,Requesting reverse proxy to ibm for attention
1821353,2019-03-25 09:39:31 UTC,"------- Comment From <email address hidden> 2019-03-25 05:32 EDT-------
This error is likely due to using the full block device node (dasda) instead of a partition device node (e.g. dasda1) of a CDL formatted DASD device."
1821353,2019-03-25 08:59:28 UTC,"------- Comment From <email address hidden> 2019-03-25 04:49 EDT-------
Description will be reversed mirrored from LP"
1821353,2019-03-26 21:28:00 UTC,Can you attach a core dump?
1821354,2019-04-02 21:05:39 UTC,Confirmed. Upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=945987
1821354,2019-08-01 16:38:59 UTC,"The reference upstream bug report is https://bugs.chromium.org/p/chromium/issues/detail?id=944941. It was reportedly fixed in chromium 74. I'm testing 75, and I can confirm this is fixed."
1821355,2019-03-22 15:02:09 UTC,Originally discovered over at the forum: https://forum.kicad.info/t/reference-designator-problem-with-kicad-5-1-0/15861/
1821355,2019-03-22 15:49:18 UTC,Please add the project for which this happens
1821355,2019-03-23 11:02:31 UTC,"I have added the ""project"" that I am having the problem with.
--Larry"
1821355,2019-03-23 12:59:30 UTC,Sorry to be unclear.  I meant that we need the complete project (eeschema files + custom libraries if any) to recreate.
1821355,2019-03-23 15:32:39 UTC,"It appears that Launchpad will only allow for attachment of a single file. Here is the Eeschema schematic diagram file. I will attach my custom symbol file in another comment/attachment.
--Larry"
1821355,2019-03-23 15:33:53 UTC,"And here is my custom symbol library.
--Larry"
1821355,2019-05-23 04:17:29 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821356,2020-04-23 11:21:39 UTC,We had this again on focal release day
1821360,2019-11-06 21:59:12 UTC,Attached some helpful comments from Holger
1821360,2019-07-19 15:46:55 UTC,for now i am using a gui written in lazarus by me. it starts the ngspice reading the netlist.
1821360,2019-05-27 00:46:49 UTC,"This is actually a feature request since OP simulation was never implemented before, so I'm bumping this to 6.0"
1821360,2019-04-13 20:57:53 UTC,"Not sure OP mode in the simulator GUI is fully baked yet.
See: https://bugs.launchpad.net/kicad/+bug/1821366"
1821362,2019-04-12 23:29:03 UTC,This issue was fixed in the openstack/kolla-ansible 6.2.0 release.
1821362,2019-03-22 15:08:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/645614"
1821362,2019-03-25 12:54:03 UTC,"Reviewed:  https://review.openstack.org/645614
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=192dcd1e1b9baf7f3177a694c2b1ce8bd62d9159
Submitter: Zuul
Branch:    master"
1821362,2019-03-26 10:12:26 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/647700"
1821362,2019-03-26 10:13:29 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/647701"
1821362,2019-03-26 10:15:59 UTC,"Fix proposed to branch: stable/pike
Review: https://review.openstack.org/647702"
1821362,2019-03-26 16:31:51 UTC,"Reviewed:  https://review.openstack.org/647700
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=59d518a75a4d31610dbbf70b0ea18c4104ae1dd9
Submitter: Zuul
Branch:    stable/rocky"
1821362,2019-03-26 18:27:18 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/647858"
1821362,2019-03-27 09:47:28 UTC,"Reviewed:  https://review.openstack.org/647858
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=1e2df9e3dbd676af6209fd15e8f1f7eab24f58e1
Submitter: Zuul
Branch:    stable/rocky"
1821362,2019-04-02 09:57:53 UTC,"Reviewed:  https://review.openstack.org/647702
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=780e1e4d974f49cce0a3cd6de90405b9a1fe0309
Submitter: Zuul
Branch:    stable/pike"
1821362,2019-04-02 09:58:03 UTC,"Reviewed:  https://review.openstack.org/647701
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=177787d5e9a3701a3a5caa6ac5c683ee666409d7
Submitter: Zuul
Branch:    stable/queens"
1821362,2019-04-05 13:59:31 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.
1821362,2019-04-12 23:28:55 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.5 release.
1821362,2019-04-12 23:29:29 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.0 release.
1821364,2019-03-23 12:37:19 UTC,"The package xfce4 depends on thunar, and starting with 18.10 thunar now recommends policykit-1-gnome."
1821364,2019-10-19 18:56:27 UTC,Same problem after updating to 19.10. I had to install it manually
1821364,2019-05-17 19:47:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821366,2019-05-27 00:47:32 UTC,Moving milestone to 6.0 since this is actually a new feature
1821366,2019-04-30 18:44:37 UTC,cool. I will.
1821366,2019-04-30 18:30:26 UTC,"Yes, I fixed the bug of extra tabs showing in commit d18b12c1a373c49b07ea9c670a2de6e9f2fea658"
1821366,2019-04-30 14:53:31 UTC,"@craftyjon - I just downloaded the (5.1.2)-1, release build on a Windows machine this morning. The tools / simulator / settings tab only contains AC, DC Transfer, Transient, and Custom. No other tabs. So, I don't think your bug 1) propagated to 5.1.2"
1821366,2019-03-22 15:17:18 UTC,"Application: eeschema
Version: (5.1.0)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013"
1821366,2019-04-14 14:44:04 UTC,"All tabs in 'Simulation settings' are visible in a MS Windows build (since ngspice support has been added, as far as I remember)."
1821366,2019-04-13 20:56:59 UTC,I'm a bit confused here -- the Noise tab in simulation settings is hidden since Orson's commit 324d277 years ago... so presumably that feature is not working yet.  How is there a build where this tab is accessible?
1821366,2019-04-14 17:48:13 UTC,It looks like there are two bugs:
1821367,2019-03-22 15:28:37 UTC,"Actually [?] block stay util I save the whole schematic, and reopen the hierarchical sheet."
1821367,2019-03-25 19:39:53 UTC,"It sounds like you either attempted to assign a schematic file to a sheet that was not remapped with 5.0 or later.  In other words, you have to remap a schematic file before you assign it to a sheet in a different schematic.  You may also have to update your symbol library table before you assign a remapped schematic file to a sheet.  Missing symbol library table entries with cause broke symbols links.  Conversely, once a schematic file is remapped, it is no longer compatible with v4."
1821367,2019-03-25 20:29:06 UTC,"@Wayne, I think that was what you wishing for. But not, I try remap everything before use 5.1. It is reset all my reference regardless. It is not thing to do with remap, or 4.x version file, or my library."
1821367,2019-03-25 20:29:55 UTC,"By the way, again the way remap currently work is very forcefull - everything I test these- took me quite time."
1821367,2019-03-25 23:54:17 UTC,"So to be clear, may be I should rewording my issue. I two schematic sheet A, and sheet B. The root schematic ""R"" have a hierarchy sheet block that point to either A, or B. Whenever I change the file name of the hierarchy sheet block to A/B (difference than the other). Then open the hierarchy sheet block I got two problems:
  * The symbol references always get reset to ""?"" very time
  * Open the hierarchy sheet show the [?] block until save the project, and reopen hierarchy sheet. The root schematic don't need to be close."
1821367,2019-05-25 04:17:40 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821368,2019-04-29 08:23:35 UTC,"Hello Timo, or anyone else affected,"
1821368,2019-05-29 10:13:48 UTC,"mesa backport in proposed has built, so the meson update works as intended"
1821368,2019-05-30 09:52:35 UTC,This bug was fixed in the package meson - 0.45.1-2ubuntu0.18.04.1
1821368,2019-05-30 09:52:39 UTC,"The verification of the Stable Release Update for meson has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821371,2019-03-25 02:00:06 UTC,This change was made by a bot.
1821371,2019-03-25 05:18:09 UTC,"Please file an upstream bug at https://bugs.freedesktop.org/
Product: xorg
Component: DRM/nouveau"
1821371,2019-03-25 01:50:04 UTC,It appears Xorg can't open the GPU device:
1821373,2019-05-16 02:48:18 UTC,"Reviewed:  https://review.opendev.org/658845
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aae5c7aa3819ad9161fd2effed3872d540099230
Submitter: Zuul
Branch:    master"
1821373,2019-09-27 09:03:51 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1821373,2019-03-26 12:09:34 UTC,I intend to fix this by changing instance.save() such that it will:
1821373,2019-05-13 14:11:31 UTC,"When writing tests for the above I discovered that this is not the issue. Specifically, OVO doesn't check the previous value when setting an attribute, so when we do:"
1821373,2019-05-13 14:27:54 UTC,"The root cause of this issue appears to be in sqlalchemy.api._instance_update. This method modifies the contents of the values dict when called, including popping the value of expected_task_state. If this results in db conflict due a concurrent update and it is retried, the second invocation is called without expected_task_state in values, and therefore it isn't checked."
1821373,2019-05-13 15:17:21 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658845"
1821373,2019-05-15 15:30:56 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/659317"
1821373,2019-05-15 15:31:46 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/659318"
1821373,2019-05-15 15:33:11 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/659320"
1821373,2019-05-21 19:32:07 UTC,"Reviewed:  https://review.opendev.org/659317
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=61fef49b1555c6509398fc47c21319c1b5e50505
Submitter: Zuul
Branch:    stable/stein"
1821373,2019-05-30 13:12:33 UTC,"Reviewed:  https://review.opendev.org/659318
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4540cd6ef9731837cf4ed1e56850bcfa3512ae1c
Submitter: Zuul
Branch:    stable/rocky"
1821373,2019-06-06 06:24:04 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1821373,2019-06-18 03:40:55 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1821373,2019-07-01 20:34:32 UTC,"Reviewed:  https://review.opendev.org/659320
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9c2503609bfad0b871d9e87227aa2bb5c137467
Submitter: Zuul
Branch:    stable/queens"
1821373,2019-07-10 21:39:47 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1821378,2019-05-14 22:57:59 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821378,2019-05-14 19:52:13 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
1821378,2019-05-14 19:04:29 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18
1821378,2019-05-14 19:09:49 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49
1821378,2019-04-22 20:30:31 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100267.html
1821378,2019-04-22 20:24:04 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100261.html
1821383,2019-03-22 18:30:08 UTC,This change was made by a bot.
1821383,2019-03-25 04:55:48 UTC,Please attach `dmesg` right after boot.
1821383,2019-04-09 05:09:38 UTC,"Please comment out ""blacklist i2c_i801"" in /etc/modprobe.d/blacklist.conf, reboot and test again."
1821385,2019-05-30 19:36:09 UTC,"New xorg publication corrects this bug:
https://lists.x.org/archives/xorg-announce/2019-May/002993.html"
1821385,2019-05-23 20:50:39 UTC,The issue was fixed upstream in https://gitlab.freedesktop.org/xorg/xserver/commit/2e18eec6
1821385,2019-03-25 01:54:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821385,2019-05-23 18:42:38 UTC,"The shock was brutal, all my applications were closed. And then GDM appears."
1821385,2019-03-22 18:40:09 UTC,"StacktraceTop:
 wl_proxy_destroy (proxy=0x97000001cf) at ../src/wayland-client.c:523
 wl_callback_destroy (wl_callback=<optimized out>) at /usr/include/wayland-client-protocol.h:1154
 xwl_present_sync_callback (data=0x55654040fd10, callback=<optimized out>, time=<optimized out>) at ../../../../../hw/xwayland/xwayland-present.c:284
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fff9e3d8f50, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7fff9e3d9020) at ../src/x86/ffi64.c:525"
1821385,2019-03-25 01:54:06 UTC,Tracking in https://errors.ubuntu.com/problem/008c7bd0fdc996890cce5f67e5f0214f280aefd8
1821386,2019-11-13 21:33:48 UTC,"Not sure what the complaint is. Pretty sure the config subiquity generates correctly points to the partition. The UX is a tiny bit misleading because it talks about a boot disk rather than a boot partition but really, are you going to have multiple PReP partitions on a single disk?"
1821386,2019-11-13 21:33:59 UTC,"Closing for now, reopen if you disagree."
1821390,2019-05-02 13:39:10 UTC,"also affects aws i3.metal disco , cosmic 4.18.0-1015.17"
1821390,2020-04-24 10:29:57 UTC,"For the timeout issue on Oracle B-5.0, VM.Standard2.16
this test will take about 2 minutes to run:"
1821390,2020-03-25 04:39:56 UTC,Passed on E 5.3 AMD64
1821390,2020-03-24 04:57:52 UTC,"Failed on T-4.4 / X-4.4 AMD64
Passed on X-4.15 / B-4.15 AMD64"
1821390,2019-12-17 16:42:38 UTC,"SRU 2019.12.02 Bionic linux-oracle, Kernel:5.0.0-1009.14~18.04.1"
1821390,2019-04-10 15:14:07 UTC,"affects, 4.18.0-1013.15 linux-aws"
1821390,2019-03-22 20:44:10 UTC,Also affects Xenial linux-aws 4.4.0-1078.88
1821390,2019-03-28 04:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821390,2019-03-22 19:10:37 UTC,Also affects Bionic linux-aws 4.15.1035.37
1821390,2019-03-28 12:38:04 UTC,"We see a similar failure in some Azure Cloud instances, it appears to be somewhat of the same."
1821393,2019-03-22 19:10:52 UTC,Also affects Bionic linux-aws 4.15.1035.37
1821393,2019-03-22 20:44:21 UTC,Also affects Xenial linux-aws 4.4.0-1078.88
1821393,2019-03-25 08:59:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821393,2019-03-25 09:44:20 UTC,"That affects all kernels, because that needs kvm modules parameter enable_vmware_backdoor. I am not comfortable enabling that by default on our kernels. We could enable that during the kvm-unit-tests. But for now, on our own branch of kvm-unit-tests, I decided to simply disable that test to be run by default."
1821394,2019-09-24 15:00:23 UTC,linux-oracle / disco / 5.0.0-1003.4
1821394,2019-08-25 23:41:50 UTC,"latest results from sru-20190812 differ a bit, but still crash  linux-azure , disco"
1821394,2019-09-24 14:59:56 UTC,Oracle is also affected by this. VM.Dense and VM.Standard instance types
1821394,2019-10-30 15:18:14 UTC,Failing on the 5.3 kernel Eoan / Azure
1821394,2019-05-29 07:29:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821394,2020-11-17 04:25:55 UTC,Still visible in Xenial 4.4.0-1118.132 AWS c5.metal
1821394,2020-03-24 05:01:52 UTC,"Failed on T-4.4 / X-4.4 AMD64
Passed on X-4.15 / B-4.15 AMD64"
1821394,2020-10-09 21:59:45 UTC,Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64
1821394,2019-12-16 15:07:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821394,2019-05-22 16:14:24 UTC,"affects , linux-azure 5.0.0-1007.7"
1821394,2020-03-19 15:58:19 UTC,"Time out on T-4.4, with a slightly different error:
 BUILD_HEAD=4671e4ba
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.1jzuZsx4Jy -smp 1 -cpu host,+vmx -append -exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test -vmx_controls_test -vmx_host_state_area_test -vmx_nm_test -vmx_nmi_window_test -vmx_intr_window_test -vmx_pending_event_test # -initrd /tmp/tmp.1FbpAwN033
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 477000
 cr4 = 20
 PASS: test vmxon with FEATURE_CONTROL cleared
 PASS: test vmxon without FEATURE_CONTROL lock
 PASS: test enable VMX in FEATURE_CONTROL
 PASS: test FEATURE_CONTROL lock bit
 PASS: test vmxon with unaligned vmxon region
 PASS: test vmxon with bits set beyond physical address width
 PASS: test vmxon with invalid revision identifier
 PASS: test vmxon with valid vmxon region
 PASS: test vmptrld with unaligned vmcs
 PASS: test vmptrld with vmcs address bits set beyond physical address width
 PASS: test vmptrld with vmxon region
 FAIL: test vmptrld with vmxon region vm-instruction error
 PASS: test vmptrld with valid vmcs region
 PASS: test vmclear with unaligned vmcs
 PASS: test vmclear with vmcs address bits set beyond physical address width
 PASS: test vmclear with vmxon region
 PASS: test vmclear with valid vmcs region
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: test vmclear flush (current VMCS)
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: test vmclear flush (!current VMCS)
 PASS: test vmptrst
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: VMWRITE/VMREAD
 PASS: VMREAD TSC_OFFSET after VMWRITE TSC_OFFSET
 PASS: VMREAD TSC_OFFSET_HI after VMWRITE TSC_OFFSET
 PASS: VMREAD TSC_OFFSET_HI after VMWRITE TSC_OFFSET_HI
 PASS: VMREAD TSC_OFFSET after VMWRITE TSC_OFFSET_HI
 VMCLEAR VMCS..."
1821394,2019-05-21 14:21:35 UTC,affects 5.0.0-1007.7-aws
1821394,2019-03-22 19:09:48 UTC,Also affects Bionic  linux-aws 4.15.1035.37
1821394,2019-03-22 20:44:37 UTC,Also affects Xenial linux-aws 4.4.0-1078.88
1821394,2019-03-28 17:28:57 UTC,"The vmx tests have been failing for me as well. There were some bugs that required me to revert some patches or apply some others, that ended up being fixed on kvm_unit_tests master regarding EPT. The disco branch of our own repo of kvm_unit_tests should work fine with our 5.0 kernel, but we still need to see that running on our test systems. So far, I only tested on a very old Intel Core 2 Duo processor."
1821394,2019-05-21 18:35:39 UTC,"affects , linux-aws-4.18.0 amd64, i3.metal"
1821394,2019-04-10 15:18:01 UTC,affects 4.18.0-1013.15 linux-aws
1821394,2019-05-02 13:20:52 UTC,I have seen this fail in Disco on linux-aws but only on i3.metal.
1821394,2019-05-02 13:53:19 UTC,"also affecting linux-azure Disco, 5.0.0-1005.5
Instances:  Standard_D16s_v3 , Standard_D2_v3 , Standard_D2s_v3, Standard_E2s_v3, Standard_F2s_v2, Standard_F32s_v2"
1821394,2019-03-29 11:52:34 UTC,Found on X KVM as well.
1821396,2019-10-07 11:26:37 UTC,Hello
1821396,2019-10-07 16:17:02 UTC,"No, it seems like it went away now."
1821396,2019-10-08 19:44:48 UTC,"Now it's happening again. Earlier I updated snapd (from 2.39) and the problem went away, but then it came back after a reboot. Now I reinstalled snapd, and the problem went away again, and rebooted again and the problem came back. So it seems it works properly from when update snapd until I reboot."
1821396,2019-10-09 05:57:58 UTC,Hello
1821396,2019-10-10 14:49:50 UTC,"I've attached the output of ""grep DENIED /var/log/audit/audit.log""."
1821396,2020-04-07 07:51:51 UTC,"I think I've now managed to resolve this, bases on things I learned from https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141. In /etc/apparmor.d/, in addition to usr.lib.snapd.snap-confine I also had usr.lib.snapd.snap-confine.rpmsave and usr.lib.snapd.snap-confine.old. The latter is presumably some backup I made when editing usr.lib.snapd.snap-confine, but I don't remember. After removing it and restarting apparmor, snaps work again."
1821397,2019-03-25 01:58:54 UTC,Can you please provide a screenshot or photo of the error you are seeing?
1821397,2019-05-24 04:17:15 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1821399,2020-04-28 15:21:22 UTC,"Terran was testing a server that also had applied the top commit here, which needs a signoff as well:"
1821399,2020-03-16 17:04:10 UTC,"Daniel Pearl was working on this bug, among others, before he left CW MARS.  He left behind an omnibus branch that is intended to fix most of these issues.  I have had these bugs assigned to me since before his departure because it was my intention to clean his branch up, test it, and add any missing bits.  I have not had time to do this, so I am simply putting the branch out there in the hope that someone can test what's there during bug squashing week or whenever."
1821399,2020-04-28 17:27:34 UTC,"Fixes pushed to master and rel_3_5.  Thanks Dan, Jason, and Terran!"
1821399,2020-04-27 21:23:17 UTC,This is fixed as part of the receipt omnibus patch. My signoff to that is at:
1821399,2019-06-26 16:50:51 UTC,call_number.label is available but doesn't work the heading for call numbers shows up but none of the actual call numbers
1821403,2019-03-22 19:40:19 UTC,The additional attached information was sampled at the time after the chromium-browser successfully completed its install (and after that was confirmed by successfully launching it as shown in the terminal session) so any traces of its misbehavior might be long gone before the attachments were created.
1821403,2019-04-05 09:41:03 UTC,"chromium-browser requires a newer version of libnss3 than what was initially installed. This is not a bug in chromium or libnss itself. A half-updated system is in an inconstistent state, and will result in undefined behaviours like this crash."
1821403,2019-04-09 17:01:00 UTC,"> chromium-browser requires a newer version of libnss3 than what was initially installed.
"
1821403,2019-04-09 17:03:10 UTC,"The chromium-browser metadata needs fixing (as explained in my last comment) so that libnss3 gets upgraded automatically on ""apt-get install chromium-browser""."
1821407,2019-05-21 20:35:09 UTC,This bug was fixed in the package putty - 0.67-3+deb9u1build0.16.04.1
1821407,2019-04-02 18:44:06 UTC,"Though for clarity, we won't be backporting 0.71 wholesale, but rather applying cherry-picked security updates.  I've been consulting with upstream on this."
1821407,2019-03-22 22:20:52 UTC,The launchpad cve integration was a nice idea but never really grew into anything.
1821407,2019-04-02 18:43:06 UTC,"This is in progress - I've been working on getting backports in place in Debian, and Ubuntu should mostly be able to use the same patches."
1821407,2019-03-22 21:48:44 UTC,Tried to link CVEs to the bug report but the database hasn't been pulled recently enough. Will try again later today or tomorrow.
1821407,2019-03-22 22:20:00 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures"
1821410,2019-03-27 16:33:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821410,2019-04-23 22:36:43 UTC,I uploaded an updated package on my personal PPA available at: https://launchpad.net/~danilopiazza/+archive/ubuntu/ppa/+sourcepub/10096097/+listing-archive-extra
1821410,2019-04-24 00:22:52 UTC,"The attachment ""Patch from 3.30.2-1ubuntu1 to 3.32.0"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1821410,2019-05-03 13:50:17 UTC,"Hello, thank you for your work on this bug!"
1821410,2019-05-10 07:49:41 UTC,"The new GPaste package worked perfectly with GNOME Shell 3.32.0+git20190410-1ubuntu1, but there are some regressions when using 3.32.1-1ubuntu1~19.04.1 from disco-proposed."
1821411,2019-09-27 09:05:27 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1821411,2019-06-18 03:41:28 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1821411,2019-06-06 06:24:33 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1821411,2019-04-11 18:33:39 UTC,"Reviewed:  https://review.openstack.org/650601
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=94e17f988dfb751df381341863a11c60267fcd30
Submitter: Zuul
Branch:    stable/rocky"
1821411,2019-04-10 20:24:18 UTC,"Reviewed:  https://review.openstack.org/650600
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ef25fff5ec741b146633df0c292dfefedcc14a22
Submitter: Zuul
Branch:    stable/stein"
1821411,2019-04-08 01:23:20 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650600"
1821411,2019-04-06 11:21:55 UTC,"Reviewed:  https://review.openstack.org/647972
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a71af2beada0ac46d7154994abbf955e9dfd99ac
Submitter: Zuul
Branch:    master"
1821411,2019-03-27 01:38:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647972"
1821411,2019-04-08 01:32:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650601"
1821413,2019-03-22 21:30:04 UTC,This change was made by a bot.
1821415,2021-01-04 14:56:18 UTC,"Can we raise the importance please? It is quite essential to let unprivileged users run certain commands, even if there is not GUI."
1821415,2020-08-07 09:38:31 UTC,"sru upload for bionic: needs sru template, and the bug doesn't seem fixed in newer releases?"
1821415,2019-06-27 15:48:56 UTC,Lubuntu is suffering what seems to be a related failure although I tracked that down to what I thought was a different upstream bug report. In Lubuntu's case the lxqt-policykit-agent suffers a SIGSEGV as a side-affect (I think) of polkit failing to authorise.
1821415,2019-05-07 17:23:55 UTC,"The plymouth package hook is using apport's ""attach_root_command_outputs"" function that same function is also used by the following package hooks: lightdm, shim-signed, ubuntu-release-upgrader, update-manager, synaptic, upgrade-system and all the xorg hooks. So it may be worth working around this is apport."
1821415,2019-04-01 12:00:01 UTC,I proposed a fix upstream [1]. A workaround can be added to apport to workaroud this while polkit is fixed upstream: we could for example spawn pkttyagent manually (a similar approach is used by systemd).
1821415,2019-03-26 14:40:29 UTC,Added to Trello: https://trello.com/c/sTIx3fol/288-bug1821415-pkexec-fails-in-a-non-graphical-environment
1821415,2019-03-26 14:39:44 UTC,"Marking as notfixing for release.  This doesn't mean that it won't get worked on, and Andrea might have an idea what's going on here, but we won't block release on this bug."
1821415,2019-05-07 14:22:37 UTC,"We reviewed it in the team meeting, while it would be nice to fix we don't believe it's an usecase common/important enough to justify team assignment & tracking, tagging rls-ee-notfixing"
1821416,2019-05-27 09:58:31 UTC,The attached patch decouples the X and Y step sizes when drawing the grid. It also cleans up some of the code in the DrawGrid function by fixing some type issues and an unused variable.
1821416,2019-05-29 03:35:55 UTC,"Fixed in revision 45f10fcff1b4429975634b6595d9acad86380074
https://git.launchpad.net/kicad/patch/?id=45f10fcff1b4429975634b6595d9acad86380074"
1821427,2019-04-18 02:56:52 UTC,"Not sure if related, but I do run under wayland (weird that it looks like an X11 error then, especially as evolution runs wayland native?), with fractional zooming on my laptop panel @ 175% and usually have an external, lower resolution screen at 100% scaling.  Evolution is usually the first app i open and stays open throughout my session, so has usually been running for days before being closed (and killing the session) -- but sometimes closing it is fine.  Haven't seen any other app trigger it."
1821427,2019-08-08 09:04:41 UTC,Upstream bug reports:
1821427,2019-08-08 08:59:57 UTC,I have an 100% reliable way to reproduce this crash :)
1821427,2019-04-18 03:09:05 UTC,"When you see X11 code in the gnome-shell process of a Wayland session that's nothing unusual. It just means some X11 app is running, talking to Xwayland and gnome-shell (which is both the Wayland display server AND the X11 window manager in this case)."
1821427,2020-08-07 09:52:47 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020."
1821427,2019-04-18 02:00:42 UTC,Unless you can think of anything that's special or unusual about your system that triggers this bug?
1821427,2019-03-25 03:22:30 UTC,problem persisting with extensions uninstalled & disabled:
1821427,2019-04-17 22:11:02 UTC,Anything else I can do to help debug this?
1821427,2019-03-25 01:41:52 UTC,I can't find any other reports of a crash like this.
1821427,2019-03-23 01:56:14 UTC,"StacktraceTop:
 XPending (dpy=0x55f60f94d000) at ../../src/Pending.c:55
 gdk_check_xpending (display=0x55f60f95d010) at ../../../../../gdk/x11/gdkeventsource.c:269
 gdk_event_source_prepare (source=<optimized out>, timeout=timeout@entry=0x7ffc22a6a374) at ../../../../../gdk/x11/gdkeventsource.c:287
 g_main_context_prepare (context=context@entry=0x55f60f192e80, priority=priority@entry=0x7ffc22a6a400) at ../../../glib/gmain.c:3499
 g_main_context_iterate (context=0x55f60f192e80, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:3907"
1821427,2019-04-18 01:59:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821428,2019-12-16 17:29:16 UTC,This was implemented in the Train release with change Id9019298482c040be05f540e71dacfdf0bd77469.
1821428,2019-12-16 17:29:33 UTC,Link to change: https://review.opendev.org/#/c/658422/
1821429,2019-08-18 18:42:15 UTC,"I wish I could at least start the config using an available entry type, then switch to `other` in the menu to manually tweak to see whats missing from the config generated from the previous type. Instead we just see a vague ""Error building boot sequence. Check parameters!"" message, and have no way of using the tool further, like copying the starter config generated by a entry type, like for iso."
1821429,2019-06-08 13:22:48 UTC,"Still no update about this bug? Either Grub-Customizer is bugged or GRUB, or both. It's not surprising anyway this application is really buggy and doesn't work as intended."
1821432,2019-04-15 09:43:51 UTC,"Hi wdonadelli,"
1821434,2019-04-12 03:03:13 UTC,"So the patched kernel reduce the fail rate, but not completely?"
1821434,2020-05-07 17:19:43 UTC,"As far as I am concerned this is verified for bionic, system has been rock solid with this patch."
1821434,2020-06-08 05:29:59 UTC,Thanks for the verification @vali !!
1821434,2020-05-06 07:12:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'."
1821434,2020-05-01 01:52:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1821434,2020-05-01 01:22:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1821434,2020-02-09 04:17:26 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1821434,2019-04-22 05:53:37 UTC,"Yes, it looks like that. I've done some more testing and it seems if a fs is mounted on a device attached to the ASM1062 SATA ports it will also oops with your patch."
1821434,2020-05-18 10:10:47 UTC,This bug was fixed in the package linux - 4.15.0-101.102
1821434,2019-04-11 18:24:54 UTC,"I think it's your kernel, I never shut it down after the upgrade and it has this build date: 4.15.0-47-generic #50 SMP Mon Mar 25 15:56:04 CST 2019 x86_64 x86_64 x86_64 GNU/Linux"
1821434,2020-05-19 21:37:06 UTC,This bug was fixed in the package linux - 5.3.0-53.47
1821434,2019-04-11 16:38:51 UTC,More logs about some failure of resuming the device
1821434,2019-04-11 16:38:14 UTC,"Unfortunately after many successful suspend/resume cycles I got the same crash again. Only difference from the previous times seems to have been the system under some I/O load, doing a fs scrub.
See attached kernel logs"
1821434,2019-03-27 09:05:06 UTC,https://lkml.org/lkml/2019/3/27/266
1821434,2019-03-26 17:39:22 UTC,"This kernel fixes it for me, I can suspend & resume no problem now with disks attached to the PCI adapter"
1821434,2019-03-25 08:24:08 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1821434/"
1821434,2019-03-25 07:39:59 UTC,"I had a try on kernel 4.15.0-46 in Bionic with efi-pstore module loaded as pstore backend, but I cannot reproduce that kernel panic. It really takes more information before one can investigation more into this issue, so apport runs, even before the panic taking place, is really mandatory. Please give apport a chance to collect some more information by executing `apport-collect 1821434`."
1821434,2019-03-23 08:10:36 UTC,"Can't do apport when the crash happens, I get the logs from efi-pstore."
1821434,2019-03-23 07:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821434,2020-05-19 18:08:11 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1821434,2019-04-11 17:42:58 UTC,"Does the system recently get update? My test kernel was -47 and it may be replaced by official kernel, which also has -47 suffix."
1821434,2020-05-19 00:17:21 UTC,This bug was fixed in the package linux - 5.4.0-31.35
1821435,2019-05-06 07:30:49 UTC,The issue got fixed upstream with https://gitlab.gnome.org/GNOME/nautilus/commit/4cffc1f2
1821435,2019-03-23 07:12:18 UTC,"StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x55eeaf3fa2c0 <__FUNCTION__.63830> ""nautilus_window_slot_get_location"", message=<optimized out>) at ../../../glib/gtestutils.c:2878
 g_assertion_message_expr (domain=0x0, file=file@entry=0x55eeaf3f9521 ""../src/nautilus-window-slot.c"", line=line@entry=3270, func=func@entry=0x55eeaf3fa2c0 <__FUNCTION__.63830> ""nautilus_window_slot_get_location"", expr=expr@entry=0x55eeaf3f9514 ""self != NULL"") at ../../../glib/gtestutils.c:2904
 nautilus_window_slot_get_location (self=0x0) at ../src/nautilus-window-slot.c:3270
 nautilus_window_slot_get_location (self=<optimized out>) at ../src/nautilus-window-slot.c:3266
 nautilus_window_on_undo_changed (manager=<optimized out>, window=0x55eeaffd43d0) at ../src/nautilus-window.c:1672"
1821435,2019-06-03 08:53:52 UTC,This bug was fixed in the package nautilus - 1:3.32.1-0ubuntu0.19.04.0
1821435,2019-06-03 08:43:52 UTC,"The verification of the Stable Release Update for nautilus has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821435,2019-05-30 14:46:31 UTC,"There are no report from 3.32.1, marking it as verification-done now"
1821435,2019-04-02 14:53:22 UTC,"Thank you for your bug report, I've reported it upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/970
(the error tracker report https://errors.ubuntu.com/problem/e31ebe2117daadf5ea0a969148735d423e102293 seems to be the same issue)"
1821435,2019-05-20 16:24:11 UTC,Will test om thursday
1821435,2019-05-20 14:20:58 UTC,"Hello Per-Inge, or anyone else affected,"
1821435,2019-05-12 17:37:24 UTC,This bug was fixed in the package nautilus - 1:3.32.1-0ubuntu1
1821435,2019-05-23 05:55:15 UTC,"I set the developer option and updated. Got the nautilus update among other
updates.
Copied a file from the server to Documents and starred the file. Worked OK
and got no crash.
Copied another file from the server to Documents and starred it. Got no
crash, but the file didn't show up in Starred.
Restarted Nautilus, but this didn't help.
Logged out and logged in again. Open Documents and starred the file again.
This time the file showed up in Starred."
1821436,2019-03-23 12:45:03 UTC,This is probably due to the way the netlist generator orders symbols.  I suppose we could check for the first non-power symbol pin in the net to display in the ERC warning message.
1821436,2019-03-23 13:26:04 UTC,"If we collect the full list of pins on the net, we can sort the invisible pins to the end and then pick the first in the list.  Since we don't have a dedicated power flag, we can't just skip the power input items or even the invisible power inputs.  But we could de-prioritize them."
1821436,2019-11-14 17:54:34 UTC,Hello
1821436,2019-11-15 15:40:17 UTC,Your request has nothing to do with this bug report. Make a separate report.
1821440,2019-03-23 16:43:15 UTC,extra info.
1821440,2019-05-15 13:34:57 UTC,Please could you provide:
1821440,2019-07-15 04:17:23 UTC,[Expired for OpenStack Bundles because there has been no activity for 60 days.]
1821441,2020-10-15 04:23:48 UTC,Has the problem been observed in kernel versions 5.x? Like in Ubuntu 20.04 onward?
1821441,2020-12-15 04:17:13 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1821441,2019-09-23 11:30:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821441,2020-10-15 04:18:10 UTC,"I'm seeing the same thing. Basically, any use of clock_gettime now requires a syscall (isntead of using vsdo). The applications I'm running do a lot of clock_gettime's, and basically cannot run performantly anymore after this happens."
1821444,2019-03-23 10:26:57 UTC,"My native system is x86_64-pc-linux-gnu with a few binfmt_misc handlers wired.
Checking other targets I have locally I get the following:"
1821444,2019-03-23 11:13:14 UTC,Shorter example without relying on printf() implementation. Looks like uint32_t<->float<->double transitions are enough.
1821444,2019-03-23 13:53:36 UTC,A bit more investigation:
1821444,2019-03-23 22:41:25 UTC,"Attaching the patch and sending for review as:
    https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg06562.html"
1821444,2019-03-25 07:52:04 UTC,"Alternatively 'uint64_t helper_todouble(uint32_t)' could be implemented via
    include/fpu/softfloat.h:float64 float32_to_float64(float32, float_status *status);"
1821444,2020-04-05 21:40:14 UTC,fix committed with c0e6616b6685ffdb4c5e091bc152e46e14703dd1 and released with 4.2.0
1821447,2019-08-09 11:57:35 UTC,I am also getting the same problem on CentOS 7
1821447,2019-08-09 12:00:44 UTC,"This is an initial deployment, not a rebuild.
Any workaround to try ?"
1821448,2019-03-23 17:18:04 UTC,"Hello! First of all thank you for using our free as in freedom software,"
1821448,2019-03-24 08:23:29 UTC,I found this in my logcat console:
1821448,2019-10-02 16:31:17 UTC,"Also, partially related to this bug title, when you have not any mapp app the app crashes with an ActivityNotFoundException."
1821450,2019-05-25 04:17:39 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821450,2019-03-23 14:26:51 UTC,"Application: kicad
Version: (5.0.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013"
1821450,2019-03-25 21:34:41 UTC,"Since the design rules dialog was completely rewritten, I suspect this bug has already been released."
1821450,2019-03-23 14:17:17 UTC,"Just to include more information: KiCad 5.0.2 running on Win7/64.
Unfortunately this happened multiple times, then things went normal. Probably some data structures have been being built in the back.
Will update to 5.1.0 just after the initial dust will fall down -- running on production environment so not very ""early adopter""."
1821450,2019-03-23 14:19:35 UTC,Please add proper version info
1821450,2019-03-23 13:48:08 UTC,"Thank you for the report.  Please note that 5.0.2 will not be receiving updates at this time.  Please download and test the 5.1 release.  If this behavior continues (which it should not), we'll be able to address it."
1821452,2019-03-26 00:17:24 UTC,"It looks like you have may have installed some packages from either the ubuntu toolchain test ppa or the oibaf graphics ppa, either of those could be causing issues with the upgrade calculation. I suggest using the 'ppa-purge' tool from the 'ppa-purge' package to remove the packages from those PPAs. If it complains that they are not enabled re-enable them and try the removal process again."
1821452,2019-05-25 04:17:42 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1821454,2019-05-15 13:39:54 UTC,TRIAGE:
1821454,2019-09-23 12:34:13 UTC,This might be related to this bug: https://bugs.launchpad.net/charm-ceph-osd/+bug/1844996
1821454,2019-09-23 13:16:47 UTC,"No, in this case ceph-mons are placed into LXD containers so they have separate file systems."
1821455,2020-01-19 07:46:43 UTC,"It is now can be edited.
I think this bug should be closed."
1821456,2019-03-23 23:24:04 UTC,See bug 1396804.
1821456,2019-03-24 10:44:07 UTC,"Upstream report:
https://bugzilla.xfce.org/show_bug.cgi?id=14456"
1821457,2019-03-23 15:54:56 UTC,"StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=<synthetic pointer>) at ../../../glib/gslice.c:538
 magazine_cache_trim (allocator=0x7f84a4646d40 <allocator>, stamp=<optimized out>, ix=21897) at ../../../glib/gslice.c:677
 magazine_cache_push_magazine (ix=ix@entry=1, magazine_chunks=<optimized out>, count=51) at ../../../glib/gslice.c:709
 thread_memory_magazine2_unload (tmem=0x5589773447c0, ix=1) at ../../../glib/gslice.c:1198
 g_slice_free_chain_with_offset (mem_size=24, mem_chain=<optimized out>, next_offset=8) at ../../../glib/gslice.c:1198"
1821457,2019-03-25 20:56:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821459,2019-07-12 20:23:58 UTC,marking incomplete due to tls support on queens.
1821459,2019-07-18 10:21:01 UTC,i cannot find periodic-tripleo-ci-centos-7-ovb-3ctlr_2comp_1supp-featureset039-queens running or defined any more
1821460,2019-10-19 20:29:52 UTC,This is partly modified fbp file
1821460,2019-10-19 20:28:51 UTC,This is screenshot how it can look like
1821460,2019-03-27 15:53:28 UTC,I wouldn't mind seeing this implemented myself.
1821460,2019-10-19 20:26:59 UTC,"Hi,"
1821462,2019-03-23 20:22:41 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1821462,2019-03-24 00:48:58 UTC,"Hello
I don't know what package census other drives my system information should
provide you with what you need."
1821462,2019-03-25 05:40:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821462,2019-05-07 01:35:27 UTC,also my case:
1821462,2019-06-22 14:18:44 UTC,"mine also take too much to boot
https://paste.ubuntu.com/p/nZQf5ySCT5/
And the time system booted up is
https://paste.ubuntu.com/p/BtwVSDCMTH/"
1821462,2019-07-07 05:01:58 UTC,"HI
I am also facing a slow boot issue. If I shut down my system, I am unable to start the system. IT takes 1 hour to start but I don't know exactly when it will get start. I do just on and off the system. I am using Ubuntu 19.04 version. can you please help me on the same."
1821464,2019-03-28 03:53:11 UTC,Please provide a solution as soon as possible
1821464,2019-04-02 07:32:01 UTC,"Hello,"
1821464,2019-06-02 04:17:25 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1821465,2019-03-27 14:49:40 UTC,does the virtualbox-guest-additions-iso package work?
1821465,2019-05-27 04:17:31 UTC,[Expired for virtualbox-hwe (Ubuntu) because there has been no activity for 60 days.]
1821466,2019-03-23 18:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821466,2019-03-25 02:55:45 UTC,"Hello, can you attach the error log mentioned in your screenshot, ""/var/log/vbox-setup.log""?
Thanks"
1821466,2019-05-24 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1821467,2019-03-23 18:30:32 UTC,Also seen here: https://forum.snapcraft.io/t/error-you-must-give-at-least-one-requirement-to-install-when-rebuilding-parts-with-python-plugin/9011/3
1821467,2019-04-16 22:49:12 UTC,What version of snapcraft is this seen on? I do not see it with 3.3
1821469,2019-03-25 10:24:24 UTC,The interface does intend to allow that but I see how the path encores more devices your system. It will likely contain a hub that was not present while we were developing the interface. I will address this shortly.
1821469,2019-03-25 10:29:00 UTC,This is now addressed in https://github.com/snapcore/snapd/pull/6646
1821469,2019-03-26 17:23:33 UTC,This has been merged in master. The next edge build of core should have this fix available for testing.
1821474,2019-03-24 13:31:29 UTC,I will add this for 2.39
1821474,2019-03-25 10:19:34 UTC,Dear reporter: the specified USB vendor ID is not listed in http://www.linux-usb.org/usb.ids - could you please send the data from your device there for reference.
1821474,2019-03-25 10:20:35 UTC,This is now proposed in https://github.com/snapcore/snapd/pull/6645
1821474,2019-03-26 07:38:48 UTC,This bug is now fixed in master and will be available in snapd from the edge channel with the next build.
1821480,2019-03-28 20:57:19 UTC,"Today I update UEFI model PC using CSM, restored backup from 2019-03-02.
use software-updater, and update normal.
and PC shutdown problem occur again."
1821480,2019-03-25 20:31:29 UTC,"Today I update UEFI model PC using CSM, restored backup from 2019-03-02.
use software-updater, and update normal.
but PC shutdown could not power-off(I force power-off by switch)
and power-on PC, and show /var/log/syslog, I found same error 1814364."
1821480,2019-03-29 21:12:49 UTC,"I use ubuntu-18.10 kernel and xstack, then update to use sofrware-updater.
my ubuntu environment shutdown/power-on trouble cleared."
1821480,2019-03-24 01:59:19 UTC,"UEFI model PC using CSM(Compatibility Support Module),
I restored backup file 2019-93-02, It may work fine."
1821480,2019-03-24 07:16:19 UTC,"My disk partition
UEFI model PC using CSM use mbr.
UEFI model PC not using CSM use gpt.
BIOS PC use mbr."
1821480,2019-03-29 10:10:08 UTC,"I update software updater to update developer option update.
kenel update to 4.15.0-47-generic.
shudown and power-on up need a lot of time.
and a lot of ureadahead found in syslog."
1821480,2019-03-24 00:22:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1821482,2019-03-24 23:11:36 UTC,"Great idea! Thank you for suggestion, Peter!"
1821482,2019-07-15 03:43:24 UTC,"Since this bug was filed, the scenario has been addressed by other work in the area.
On Juju 2.7-b1, I get:"
1821483,2019-03-23 23:46:34 UTC,"https://launchpad.net/~dank/+archive/ubuntu/python-fixes contains an updated pip with the cherrypicked fix.
(Also, http://kegel.com/linux/howto-ppa/ happens to document how it was prepared.)"
1821483,2019-03-24 21:00:54 UTC,"The first line of the bug report should have said ""and ubuntu 16.04""."
1821483,2020-05-25 14:30:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821483,2020-08-30 04:51:39 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu."
1821486,2019-03-26 18:44:27 UTC,"Hi Jon,
I agree, We should add a ""clear highlight"" message."
1821486,2019-05-04 20:19:48 UTC,"Fixed in revision e0ada1379f3c70bfd1bad4a802c82aff507a391d
https://git.launchpad.net/kicad/patch/?id=e0ada1379f3c70bfd1bad4a802c82aff507a391d"
1821490,2019-04-23 23:53:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1821490,2019-06-23 04:19:01 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1821492,2019-06-05 04:17:32 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821492,2019-03-24 21:23:07 UTC,"Hmm, that sounds really strange to me. Why would the M570 act differently from any other mouse here. It is not like it is a wacom tablet or something like that."
1821492,2019-04-05 21:00:53 UTC,"Do you have any Logitech software installed that could be interfering? My mouse has ""Logitech Options"", one of the scroll wheel settings makes zooming in KiCad (and other CAD packages) quite unstable."
1821494,2020-04-25 23:37:54 UTC,I've submitted an upstream MR here based on the OP's fix with some slight edits based on my tseting: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/286
1821494,2019-04-14 12:18:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821494,2019-04-15 02:12:06 UTC,Thanks Ben.
1821496,2019-03-24 08:16:11 UTC,"Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Sound(ALSA)"
1821499,2019-04-11 19:08:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821499,2019-04-11 19:19:03 UTC,"I presume this is referring to the hardcoded calculations
for NRDEVICES and the critical calculation using it:"
1821499,2019-05-01 14:57:41 UTC,"Starting with Disco Dingo (19.04) there is a new package `zram-tools'
which is roughly configurable as per many of the above wishes."
1821500,2019-03-24 23:55:04 UTC,*** This is an automated message ***
1821504,2019-03-30 12:01:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821504,2019-04-23 23:53:01 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1821504,2019-06-23 04:19:00 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1821508,2019-03-24 11:23:14 UTC,my laptop config
1821508,2019-03-24 22:42:40 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1821510,2019-03-26 00:09:08 UTC,"Do you continually get prompted to upgrade to Ubuntu 18.04? You could prevent this from happening by modifying the ""Prompt="" in line /etc/update-manager/release-upgrades to ""never""."
1821510,2019-05-25 04:17:41 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1821513,2019-05-25 04:17:28 UTC,[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]
1821513,2019-03-24 19:44:09 UTC,"Due to a bug in apport's method for creating a duplicate signature, the DuplicateSignature in this report was incorrect. We are fixing that now, sorry for the noise!"
1821513,2019-03-25 06:39:41 UTC,The error in your log is:
1821515,2019-03-24 12:12:23 UTC,The bug is in the same area as https://bugs.launchpad.net/qemu/+bug/1821444 but in another branch of 'uint64_t helper_todouble(uint32_t arg=0x1)'.
1821515,2019-04-05 08:26:31 UTC,We also hit this regression when testing CompCert for e5500 with qemu 3.1.0.
1821519,2019-03-24 14:08:07 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1821519,2019-03-24 19:39:29 UTC,"The output of lshw mentions the GPU driver ""nouveau"" -> bug 1631715."
1821519,2019-03-25 06:00:13 UTC,"ran another QA-test of same ISO on dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
i suspended system twice; it resumed as expected.  I could not re-create it  (using 'radeon' driver which fits @Theo's notation too)"
1821520,2019-03-24 13:44:01 UTC,HI Holger-
1821520,2019-06-04 21:09:13 UTC,I consider this bug for windows packaging only. I just updated to ngspice 30 on the builder.
1821520,2019-06-05 11:01:39 UTC,Please test https://kicad-downloads.s3.cern.ch/windows/testing/patched/kicad-patched-375-6f8a0a4ee-x86_64.exe
1821520,2019-06-05 11:04:41 UTC,Be aware that some exes are not included because they are not included in the ngspice 30 msys2 package.
1821520,2019-06-05 13:19:45 UTC,"Available in the current nightlies:
kicad-r13375.6f8a0a4ee-i686.exe
kicad-r13375.6f8a0a4ee-x86_64.exe"
1821520,2019-06-06 10:50:00 UTC,If have done some preliminary tests. All look good.
1821520,2019-06-06 11:05:07 UTC,I have pushed it for 5.1.2 as well as pkgrel 2.
1821520,2019-06-07 21:34:26 UTC,Some more tests with ngspice-30 in kicad-5.1-jenkins-298-x86_64.exe (about 20 different circuits). Everything is o.k.
1821520,2019-06-08 08:49:41 UTC,pkgrel 2
1821520,2019-11-27 23:25:28 UTC,"@Holger, I am not sure with the macos build. I have not followed it tightly this round, but given this pull request it looks like uses ngspice 31.3"
1821524,2019-04-02 07:29:19 UTC,"Hello,"
1821524,2019-06-02 04:17:23 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1821530,2019-03-24 16:47:18 UTC,What exactly is your runtime setup?
1821530,2019-03-24 17:23:56 UTC,"Hi,"
1821530,2019-03-24 17:46:17 UTC,how do you run the script?
1821530,2019-03-24 18:16:20 UTC,"1. Installed jython
2. Installed requests
3. Installed python
4. Downloaded sikulixapi.jar
5. Set CLASSPATH env to sikulixapi.jar
6. Set PATH to python and jython
7. Powershell as admin
8. In powershell:
Jython .\test.py"
1821530,2019-03-24 18:30:23 UTC,"Ok, will check tomorrow"
1821530,2019-03-25 08:53:19 UTC,"yes, a bug with the latest version."
1821531,2019-04-22 12:09:32 UTC,"Currently I think the best you can do is using the Aux input to have an PFL button.
Even Microphones have a PLF control, but it is not exposed in the skin GUI."
1821531,2019-05-17 12:03:51 UTC,i listen to the mic along with whe main mix going out to let me know if i left a hot mic from forgetting to click its button after announcements or that its actually on while making them. With a radio situation there's no live sound to go by. The direct monitor on the umc22 you mentioned gives me the dry mic but not controlled my  its on off button in mixx. Listening one the 4a's out in the back of the panel gives me the mix along with the mic for that purpose but leaves out being able to preview or cue songs off air using the headphone buttons. The preference to send the mic to master or direct used to send it to to mix side of the headphone mix fader for the headphone out before the booth out was added.
1821532,2019-09-20 13:16:28 UTC,Hello
1821532,2019-03-24 21:28:58 UTC,What's the output of 'snap version'?
1821532,2019-03-25 02:14:53 UTC,"This is snap version:
snap    2.37.4+18.04.1
snapd   2.37.4+18.04.1
series  16
ubuntu  18.04
kernel  4.15.0-46-generic"
1821533,2019-07-10 00:36:57 UTC,"Our company just purchased these laptops and we could really use a fix for
them. Would you mind sharing the edid files you created to get the displays
functioning?"
1821533,2019-05-14 07:21:23 UTC,"I'm able to display on both the internal monitor and an external one, by specifying the connector name in the edid firmware kernel boot option:"
1821533,2019-05-18 21:08:40 UTC,"JJJ, that worked, but now my audio does not work, any idea why?"
1821533,2019-07-09 20:57:02 UTC,Does Linux plan of patching this issue since 18.04 is an LTS? Anyone know?
1821533,2019-07-09 21:42:35 UTC,I'm not sure this is a Linux problem. It may be that the panel is reporting bad EDID data. I haven't investigated enough to say for sure. In any case none of the more recent Linux releases fixed the problem in my tests. Also no other open source OSs were able to deal with the onboard LCD panel either. (That may have changed since I tested.)
1821533,2019-07-10 00:39:12 UTC,Our company just purchased these laptops and we could really use a fix for them. Would you mind sharing the edid files you created to get the displays functioning?
1821533,2019-10-26 12:21:15 UTC,Thanks for help with edid! Works for me both for internal LCD and external HDMI monitor on ASUS Zenbook UX431FA with 18.04.
1821533,2019-08-14 17:30:28 UTC,"I had the same problem and a new Fedora solved this for me. On the other hand, I am experiencing some problems with wifi now..."
1821533,2019-08-14 20:51:50 UTC,"if current drm-intel-next mainline build or 5.3rc doesn't work, then this bug should be filed upstream at bugs.freedesktop.org, DRI: drm/intel"
1821533,2019-08-14 20:52:08 UTC,and attach the edid there
1821533,2019-04-27 16:06:50 UTC,"I was able to display on an external monitor, or the internal monitor, but not both simultaneously. I didn't spend too much time trying to solve the problem and now the laptop is with a family member at another location. If you work on this issue and find a solution please post it here."
1821533,2020-12-03 13:59:51 UTC,"Thank you so much for your help.
I created a script for anyone facing the same issue."
1821533,2019-07-10 01:13:47 UTC,"As I wrote earlier, the EDID file I used came from edid-generator github and it is called 1920x1080.bin . You want me to google that for you?"
1821533,2019-04-27 04:52:47 UTC,"I was able to reproduce your solution, but now my external monitor is not recognized. Have you worked this out?"
1821533,2019-05-17 07:35:33 UTC,JJJ (jeremy-fan): Could you please describe exact walkthrough? I'm clearly doing something wrong as its not working with this...
1821533,2019-03-25 18:21:13 UTC,Below is the EDID information from the onboard panel. Why can't drm/i915 deal with it?
1821533,2019-03-25 18:09:14 UTC,I think the problem is that the laptop's onboard LCD panel is reporting EDID data with version 2 and the i915 driver can only deal with version 1 at the moment. How can this be fixed?
1821533,2019-03-25 18:07:19 UTC,"Correction: last message should read ""Why is the driver/module expecting EDID major version *1* and getting *2*?"
1821533,2019-03-25 19:34:42 UTC,"I was able to get the onboard LCD panel working, finally, as follows:"
1821533,2019-03-25 17:57:34 UTC,"Progress! Based on information in dmesg, pasted in at the end of this message, I thought maybe the graphics device was found OK but the laptop was trying to drive an external monitor instead of the onboard display. Sure enough, when I boot without nomodeset option and with an external HDMI monitor attached the system does display to the external monitor with proper 1920x1080 resolution."
1821533,2019-03-25 15:54:04 UTC,Is it known whether any machines with Intel Graphics 620 with pci id 0x3ea0 have functioning graphics with any version of Ubuntu?
1821533,2019-03-25 15:44:11 UTC,"I tried booting 4.18.0-16-generic (which i believe is the hwe kernel) with kernel option drm.debug=0xff. When the system came up of course it had no video but I could ssh in and grab the dmesg output, which is attached to this message. dmesg had many drm-related debugging messages and i915-related messages, but none of it was particularly helpful to me yet."
1821533,2019-03-25 14:24:35 UTC,"Just in case my addition of i915 to initramfs was causing a problem with drm-intel-next, I removed i915 from initramfs and repeated the test. The result was the same, no video after a certain point in the boot process with nomodeset using the drm-intel-next kernel as in #8."
1821533,2019-03-25 14:15:54 UTC,"I installed kernel and modules and headers from https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/ and rebooted without nomodeset option. Same behavior: after the ""loading initramfs"" message the screen blanks and never comes back."
1821533,2019-03-25 13:03:09 UTC,"note that having 800x600 with nomodeset is perfectly normal, and expected..."
1821533,2019-03-25 13:01:50 UTC,"That pci-id should be known by all components of the stack on 19.04, so it should work with X just fine. If it doesn't, it's likely a bug in the kernel module. You could try with a mainline build of the drm-intel-next branch:"
1821533,2019-03-25 06:33:40 UTC,"Based on a lead from an Arch Linux blog post, I tried adding the i915 module to the initramfs. This could possibly lead to earlier initialization of the graphics device and it also seems consistent with the DragonFlyBSD ""probe early"" patch I linked to in my initial bug report which may have fixed the graphics problem in DragonFlyBSD (I cannot tell for certain if the graphics problem was fixed there due to another, unrelated problem, but the fix definitely allowed the boot to proceed further and the text did seem to switch to full screen resolution)."
1821533,2019-03-25 05:14:05 UTC,"Also: booting without nomodeset kernel option for v5.1-rc2 kernel leads to black screen, just as before. At that point the system cannot even be switched to text console with ctrl-alt-Fn."
1821533,2019-03-25 05:06:24 UTC,Thanks for your help.
1821533,2019-03-25 04:21:20 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc2 kernel [0]."
1821534,2019-05-24 04:17:20 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1821534,2019-03-25 02:17:48 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1821536,2019-05-09 04:13:26 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657916"
1821536,2019-05-09 04:17:40 UTC,"I am sorry, please ignore the comment above on ^%^.
This log is not at the end of LM operation(not a final status), so I think add the ""temporarily"" is suitable."
1821537,2019-03-24 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821537,2019-03-24 20:30:20 UTC,@ubuntu-kernel-bot: Missing things can't be logged. ;-)
1821537,2019-03-25 02:52:21 UTC,"Series tracked for Cosmic, as per Seth's comment:
USB_XHCI_DBGCAP has been enabled since cosmic. I've now enabled
CONFIG_EARLY_PRINTK_USB_XDBC as well in disco."
1821537,2019-03-25 09:28:13 UTC,"I suggest to enable CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP in Bionic HWE kernels as this will allow to debug via serial console with a simple USB 3 crossover-cable (aka ""USB 3.0 super-speed A-to-A debugging cable"") without the need of a physical RS-232 interface."
1821538,2019-03-24 19:25:14 UTC,This sounds like bug 1801629.
1821539,2019-03-30 19:21:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821539,2019-03-30 19:23:33 UTC,Fresh install of Ubuntu 18.10 (I did not configured or installed anything yet) and I can't fully upgrade. I get the following error:
1821542,2019-03-27 12:00:17 UTC,"try to launch with command line, you should have a more precise error"
1821542,2019-03-28 16:33:41 UTC,I know how to load up the command prompt on Windows 10 but I don't know what to type to launch the program. Sorry.
1821542,2019-03-28 17:52:52 UTC,"Go to C:\Program Files (x86)\HomeBank
then on the path bar (where there is C:\Program Files (x86)\HomeBank
erase all and type cmd + enter
this will prompt the commandine in to C:\Program Files (x86)\HomeBank
the just type HomeBank.exe + enter"
1821542,2019-03-29 01:49:21 UTC,I tried your method but I did not get a more detailed error message when I tried to save it. I did find a work around by saving the file under my desktop and then transferring it to my dropbox folder and overriding the original file. I have to do that every time but I can at least save again. Thanks.
1821542,2019-03-30 09:10:00 UTC,"please try with that debug version
unzip it into C:\Program Files (x86)\HomeBank"
1821542,2019-05-30 04:17:20 UTC,[Expired for HomeBank because there has been no activity for 60 days.]
1821547,2019-04-09 10:21:29 UTC,"The fix for this turned out to be based on some of Jon's net/bus changes, so it can't go to 5.1.1 after all."
1821547,2019-04-08 10:22:41 UTC,"Fixed in revision b6c0aeb608e352efc808268471246ee7b73e80ff
https://git.launchpad.net/kicad/patch/?id=b6c0aeb608e352efc808268471246ee7b73e80ff"
1821547,2019-04-07 22:43:20 UTC,"Changing importance to ""high"" as this can be a data loss issue."
1821547,2019-04-07 22:40:58 UTC,"I think Jon's suggestion while handy, would be too non-standard."
1821547,2019-03-25 00:35:07 UTC,"Confirmed.  Also in my opinion, wherever things are ""cut"", they should remain visible until they are pasted, but in some way highlighted (various other programs use italics / lighter color / dotted borders / etc).  That way, you can visually keep track of what you just cut and are preparing to paste."
1821557,2019-03-25 04:23:28 UTC,"Checked the private fips dev ppa, the only linux-fips package version is 4.15.0-1001.1, not the 4.4.0-1007.8 that we expected."
1821557,2019-03-25 05:02:02 UTC,"The recent changes for FIPS in kteam-tools by Andy ea4e0b66 (info/kernel-series.yaml: fix fips related PPA references) indicates that the kernel for the test should be available in ubuntu-advantage, so we need to know why the test request is asking for the CKT PPA here."
1821557,2019-09-17 12:17:58 UTC,Test request updated. Issue fixed.
1821563,2019-06-08 19:10:57 UTC,"@Wayne-  That may be the case but POTRACE only traces around the black objects on the screen.  If a user needs to trace around a white object, they can invert the bitmap using our basic algo or adjust it's colors in an external program.  I think if we back the background a different color, we will make it harder for the user to see what will be traced and what not."
1821563,2019-03-25 13:56:55 UTC,Rather than force a transparent background to white we should set the default background color to white give the user the option to change the background color.  There may be cases where a white background it not desirable.
1821563,2019-06-08 19:08:25 UTC,"Fixed in revision 35da498a329610f6f81ff57af6c27727d1fc5b3f
https://git.launchpad.net/kicad/patch/?id=35da498a329610f6f81ff57af6c27727d1fc5b3f"
1821563,2019-03-25 07:09:57 UTC,"This image looks like it has a transparent background.
Therefore an undefined background color, hard to convert in B&W.
Please avoid it to convert it, because a transparent background is not managed."
1821563,2019-03-25 07:41:59 UTC,IMHO I think bitmap2component should just consider transparent background all white.
1821564,2020-04-05 17:55:03 UTC,This problem still exists in Ubuntu Focal Fossa (development branch) 20.04 with linux-image-5.4.0-21-generic. It also exists in linux-image-unsigned-5.6.2-050602-generic_5.6.2-050602.202004020822_amd64.deb
1821564,2020-07-04 05:57:58 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/"
1821564,2020-06-09 15:49:24 UTC,I don't see a null pointer message but the b44 driver is still broken in 5.4.0-33-generic on my Dell Inspiron 6400:
1821564,2020-06-09 04:32:17 UTC,Please test latest 20.04 kernel.
1821564,2020-04-10 17:08:04 UTC," iommu=soft does not help, and I don't understand why it would help theoretically when the Core 2 Duo T7400 CPU doesn't have a hardware IOMMU. The problem seems to be that the 64 MB buffer is allocated beyond 1 GB."
1821564,2020-04-07 15:39:31 UTC,"@Boris Gjenero, try using the kernel parameter ""iommu=soft"" instead of limiting the memory to 1GB. It will force the use of a 64MB swiotlb bounce buffer to workaround this issue. Tested with Focal Fossa Beta ISO (Kernel 5.4.0-21-generic) on my Optiplex 320 with 2GB of RAM."
1821564,2020-01-02 21:36:35 UTC,"I don't normally use Ethernet on my laptop, and for some reason the b44 module for Ethernet doesn't get loaded normally. So I didn't notice this. But I'm getting the same problem reported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/comments/8 in Ubuntu 19.10 with linux-image-5.3.0-24-generic on my Inspiron 6400. This Debian bug report has some ideas about a cause: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939697"
1821564,2019-04-06 11:03:33 UTC,@Boris please test kernel 5.1.0-050100rc3-generic (or above) at least #1822913 was solved with this kernel
1821564,2019-04-06 02:58:09 UTC,linux-image-unsigned-4.20.0-042000-generic_4.20.0-042000.201812232030_amd64.deb is good but linux-image-unsigned-5.0.0-050000rc1-generic_5.0.0-050000rc1.201901062130_amd64.deb is bad. I'm not sure I'll have time for a git bisect.
1821564,2019-04-05 02:16:08 UTC,I just tested Kernel 4.20.17 an it is good. I will do the bisect but I don't have much time at this moment
1821564,2019-04-03 06:51:13 UTC,"Ok, I failed to find where the regression comes from."
1821564,2019-03-25 16:58:11 UTC,"Sorry, I mean bug is not present in 4.18.0-16-generic and present in 5.0.0-7-generic"
1821564,2019-03-25 06:30:08 UTC,This change was made by a bot.
1821564,2019-05-26 14:48:18 UTC,"@Hans P Möller, i've tested with kernel 5.1.0-050100rc3-generic and the b44 module loaded and worked fine, but it created some others warnings in the dmesg:"
1821565,2019-07-08 02:03:48 UTC,"I'm able to replicate the issue on 2.6.5-bionic-amd64. Bootstrap hangs at ""Running machine configuration script..."" until I hit Ctrl-C:"
1821565,2019-07-08 02:20:08 UTC,"Just to add, the line where it says ""Installing Juju agent on bootstrap instance"" happened while the instance was still PXE booting."
1821565,2019-07-08 03:24:45 UTC,More debug info:
1821565,2019-07-08 07:30:36 UTC,"Here's another log. At least with 2.6.5, it doesn't hang but times out waiting for the controller instance to be ready."
1821565,2019-07-09 03:12:45 UTC,"Apologies for the false positives above. Turns out the problem was with the MAAS being misconfigured, assigning the wrong Gateway IP to machines. The 2.6 series just hangs (which is a different bug) but juju 2.7-beta1-bionic-amd64 at least times out and reports an error showing that the machine was unable to reach https://streams.canonical.com."
1821567,2019-04-29 01:25:23 UTC,"Thanks @Miguel Lavalle (minsel)
https://review.opendev.org/#/c/655625/"
1821567,2019-03-25 21:51:55 UTC,"Looking at your traceback above, we see that the failure happens in this line:"
1821567,2019-03-25 13:49:59 UTC,"Slawek, you added the gate-failure tag for tricircle, right? The neutron gate does not seem to be broken by this."
1821567,2019-03-25 13:05:17 UTC,It seems to me the broken tricircle gate was worked around by removing the failing tests here: https://review.openstack.org/647274
1821567,2019-03-25 20:15:42 UTC,"@Bence: yes, I added it according to Tricircle. In Neutron gates are fine (at least regarding this issue :))"
1821568,2019-03-25 07:21:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647304"
1821568,2019-03-29 08:53:31 UTC,Is it about admin page?
1821568,2019-03-29 09:05:42 UTC,"Not only the admin panel, but also the project panel."
1821569,2019-06-08 04:17:38 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821569,2019-04-08 10:32:08 UTC,Reinstalling windows might not always delete v4 settings. If you have your personal user profile on a separate partition then it can survive a reinstallation. So make sure you do not have any github plugin libs still in the library table (check by using the library manager. if any entry reports itself as plugin type github then you have github libs.)
1821569,2019-03-26 14:36:48 UTC,">Any external or shared drives?
"
1821569,2019-03-26 07:21:53 UTC,Could it be that you use the github plugin for getting your libraries? Check the footprint library manager and make sure you use local libs. (The github plugin was the default in version 4. Updating to version 5 does not overwrite the library setup.)
1821569,2019-03-26 15:21:40 UTC,@Scott-  Thanks for reporting back.  We'll see if Jai has a similar issue.
1821569,2019-03-25 22:34:29 UTC,"I don't use any cloud-sync programs, and the only AV I have on this box is the bundled Windows Defender.  Disabling it makes no difference."
1821569,2019-03-25 22:17:22 UTC,"@Scott-  Can you please check to see if you have any synchronization applications (Dropbox or Google Drive or similar) or shared drives on your Windows machine that exhibits this issue?  If you do, can you test whether disabling them resolves the issue?"
1821569,2019-03-25 22:05:06 UTC,"The original report may have been less than useful, but when running KiCad on Windows 10, if I'm in the PCB layout editor or footprint editor and want to add a footprint library to the current project or a 3D model to a footprint, browsing for the library or footprint causes KiCad to hang every time.  The only way out is to kill it from the Task Manager.  I can add the footprint or model manually by hitting the ""add"" button to create an empty line and then fill in the details, but this is more cumbersome than browsing for it."
1821569,2019-03-25 09:13:06 UTC,"You might want to add a bit more information here. What steps did you take to get to this error? Which kicad subprogram are you in? What canvas? The screenshot says edit footprint field. Which one? Can you share the footprint as it is before trying to edit the field? Does it happen with any footprint when doing the same operation or only with some specific footprints?
Does it happen in any project or only in a specific one?"
1821569,2019-03-25 22:45:24 UTC,Any external or shared drives?  What we're looking for here are items that may cause Windows to pause while we attempt to query them during footprint browsing.  You might also check whether this happens when the network is disabled.
1821571,2019-05-12 12:13:44 UTC,Fixed in a6674ecd5602d9a233dc40ef1cbd7e38fa867781.
1821571,2019-03-25 10:06:04 UTC,"In 5.1, this is an advanced config option. Enable it by creating ~/.config/kicad/kicad_advanced with the content ""EnableSvgImport=1""."
1821571,2019-03-25 10:37:33 UTC,"Adding the advanced config option works.
I can now select a SVG file."
1821571,2019-03-25 15:34:09 UTC,"Yes, that is not ideal that the menu doesn't reflect the setting. I'll make resolving that the target of this issue."
1821571,2019-03-25 15:54:50 UTC,Just a heads up that minor point releases generally do not have string changes.
1821571,2019-03-25 16:05:37 UTC,"@Seth, ah right. The SVG advanced config is turned off (always available) in master, so there's not much point to switch it there."
1821571,2019-05-07 10:36:48 UTC,"This is fixed in master by 2a09664ebce0b4c03be14588c15e697a0560a58b, which was a fix for https://bugs.launchpad.net/kicad/+bug/1822907"
1821571,2019-05-07 10:48:50 UTC,"@Wayne, is this still good for 5.1? Or just leave it for master?"
1821571,2019-05-07 11:27:42 UTC,"Master, svg import is a new feature that was always slated for v6."
1821571,2019-05-10 11:43:53 UTC,"Fixed in 5.1 to just remove ""SVG"" from the menu to not advertise it. Keep ""DXF"" (rather than ""Vector""), to avoid gratuitous menu changes."
1821574,2019-09-26 11:34:53 UTC,With the change to https://maas.io/docs this is no longer the case
1821576,2019-09-16 17:13:15 UTC,"Reviewed:  https://review.opendev.org/649536
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=0ce6c7f6c02dd196057f3c2e750758cd04b9978e
Submitter: Zuul
Branch:    master"
1821576,2019-09-27 15:26:25 UTC,This issue was fixed in the openstack/blazar 4.0.0.0rc1 release candidate.
1821576,2019-04-03 08:30:00 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649536"
1821576,2019-03-29 05:38:07 UTC,Sure thing. Thank you for your suggestion.
1821576,2019-03-29 05:36:08 UTC,Note that it is good to update the api-ref as well accordingly fixing this bug.
1821576,2019-03-29 05:31:43 UTC,"I agree Tetsuro san. Also please correct me if I'm wrong ,but NONE_STRINGS = ('None', 'none').
I will push the patch soon."
1821576,2019-03-29 04:55:27 UTC,Thank you for reporting this.
1821579,2019-04-15 17:40:12 UTC,"Reviewed:  https://review.openstack.org/649612
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=dc13194200e794ca381eb2422bb543cde6b9d939
Submitter: Zuul
Branch:    stable/rocky"
1821579,2019-04-15 17:31:16 UTC,"Reviewed:  https://review.openstack.org/649611
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=fc9384117daaa697daf396dd5e35029a672754fc
Submitter: Zuul
Branch:    stable/rocky"
1821579,2019-04-05 13:59:17 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.
1821579,2019-06-14 01:32:39 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.1 release.
1821579,2019-04-03 13:29:07 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649612"
1821579,2019-04-03 13:02:17 UTC,"Reviewed:  https://review.openstack.org/645861
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=a4bb8567da3e0e1468d66048c5b46cdeefcb1332
Submitter: Zuul
Branch:    master"
1821579,2019-03-25 18:42:10 UTC,"Fix up perms: https://review.openstack.org/645861
Script to check owner & permissions in CI: https://review.openstack.org/647410"
1821579,2019-04-03 14:24:55 UTC,"Reviewed:  https://review.openstack.org/647410
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=8c4ab41ffa502a58714819e0407f3c17e6fde7d0
Submitter: Zuul
Branch:    master"
1821580,2019-06-21 15:23:46 UTC,This issue was fixed in the openstack/puppet-tripleo 8.5.0 release.
1821580,2019-06-21 13:45:53 UTC,This issue was fixed in the openstack/puppet-tripleo 9.5.0 release.
1821580,2019-04-18 14:56:38 UTC,This issue was fixed in the openstack/puppet-tripleo 10.4.0 release.
1821580,2019-04-11 09:37:47 UTC,This issue was fixed in the openstack/kolla 7.0.2 release.
1821580,2019-04-11 09:37:30 UTC,This issue was fixed in the openstack/kolla 6.2.1 release.
1821580,2019-04-05 13:54:03 UTC,This issue was fixed in the openstack/kolla 8.0.0.0rc1 release candidate.
1821580,2019-04-03 22:38:28 UTC,"Reviewed:  https://review.openstack.org/649361
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=2a5f69fa43dcab856f899a14214c0b504d941571
Submitter: Zuul
Branch:    stable/queens"
1821580,2019-04-02 22:14:55 UTC,"Reviewed:  https://review.openstack.org/649360
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=9517c7b0d232af44f0d45e5fd883fd80deb8573e
Submitter: Zuul
Branch:    stable/rocky"
1821580,2020-09-18 16:49:26 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.opendev.org/647404
Reason: https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html"
1821580,2019-04-02 15:04:57 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649360"
1821580,2019-03-29 18:57:57 UTC,"Reviewed:  https://review.openstack.org/647474
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=8e3060e487508cbc8b4c77249ed7ba450ded74db
Submitter: Zuul
Branch:    master"
1821580,2019-03-29 00:26:12 UTC,"Reviewed:  https://review.openstack.org/648202
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=752a4c07cd8155123507e56846a3e2b559f4c104
Submitter: Zuul
Branch:    stable/rocky"
1821580,2019-03-29 00:07:00 UTC,"Reviewed:  https://review.openstack.org/648203
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=d47b65025a8f7aa22f40af58f341cd7e6e2b04f0
Submitter: Zuul
Branch:    stable/queens"
1821580,2019-03-27 18:15:36 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/648203"
1821580,2019-03-27 18:12:20 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/648202"
1821580,2019-03-27 15:34:25 UTC,"Reviewed:  https://review.openstack.org/647882
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0c732805b1390e12521f50d666fc18319fe9e0f3
Submitter: Zuul
Branch:    master"
1821580,2019-03-25 13:54:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647474"
1821580,2019-04-02 15:05:23 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/649361"
1821584,2019-07-23 20:31:36 UTC,This is tracked in storyboard: https://storyboard.openstack.org/#!/story/2005349
1821585,2019-03-26 02:29:51 UTC,Possibly related to bug 1727321.
1821585,2020-05-27 05:44:19 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1821587,2019-03-25 13:26:07 UTC,"Added a resource task as well, this could be fixed in either/both places"
1821588,2019-03-26 11:24:36 UTC,"Code added in revision 961:
merged in branch lp:~tapaal-contributor/tapaal/Batch-export-PNML-XML-queries-1754675
adding batch export of files to PNML and XML"
1821588,2019-03-26 11:21:39 UTC,The bug is related to orphan tranistion check that throws NPE.
1821588,2019-03-25 13:30:52 UTC,"The issue is that earlier the GUI said that orphan transitions are removed before the verification, this is not working like this anymore in 3.5.0 release."
1821589,2019-03-25 13:39:56 UTC,"StacktraceTop:
 thunar_tree_model_unref_node (tree_model=0x7fa4781a2b20, iter=0x7fffe69d5900) at thunar-tree-model.c:821
 gtk_tree_row_reference_unref_path_helper (path=path@entry=0x56109f240830, model=model@entry=0x7fa4781a2b20, parent_iter=parent_iter@entry=0x7fffe69d5960, depth=depth@entry=3, current_depth=current_depth@entry=2) at ../../../../gtk/gtktreemodel.c:2263
 gtk_tree_row_reference_unref_path_helper (path=path@entry=0x56109f240830, model=model@entry=0x7fa4781a2b20, parent_iter=parent_iter@entry=0x7fffe69d59c0, depth=depth@entry=3, current_depth=current_depth@entry=1) at ../../../../gtk/gtktreemodel.c:2262
 gtk_tree_row_reference_unref_path (path=0x56109f240830, model=0x7fa4781a2b20, depth=3) at ../../../../gtk/gtktreemodel.c:2277
 gtk_tree_row_reference_unref_path (depth=<optimized out>, model=<optimized out>, path=<optimized out>) at ../../../../gtk/gtktreemodel.c:2273"
1821589,2019-05-08 22:03:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821589,2019-05-08 22:17:18 UTC,"Same here when using Thunar to mount other partitions, seeing this right before crash:"
1821589,2019-05-09 10:49:08 UTC,"Potential upstream report:
https://bugzilla.xfce.org/show_bug.cgi?id=15212"
1821589,2020-04-24 09:47:58 UTC,Thunar 1.8.14 is available in the 20.04 repository.
1821590,2019-03-25 13:41:16 UTC,Also added checkbox-support as that's where the script actually lives
1821592,2020-01-31 13:18:20 UTC,Fix proposed by Dincer: https://review.opendev.org/#/c/704258
1821592,2020-04-27 17:30:04 UTC,"Reviewed:  https://review.opendev.org/723031
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d576249f35e9a62ec2a21e80853cb85ece4aa54a
Submitter: Zuul
Branch:    stable/stein"
1821592,2020-04-24 20:21:54 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/723031"
1821592,2020-04-13 10:22:05 UTC,"Reviewed:  https://review.opendev.org/719035
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=37ffbe164bbb5ab0848947e65369950e9dfdcba9
Submitter: Zuul
Branch:    stable/train"
1821592,2020-04-10 15:34:19 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/719035"
1821592,2020-04-10 10:38:45 UTC,"Reviewed:  https://review.opendev.org/704258
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=4b5df0d8660543230a48d279f508c3205c8fc406
Submitter: Zuul
Branch:    master"
1821592,2020-03-02 17:56:16 UTC,"Change abandoned by Radosław Piliszek (<email address hidden>) on branch: master
Review: https://review.opendev.org/661068
Reason: obsoleted ^"
1821592,2020-01-31 01:28:50 UTC,"Hi Mark,"
1821592,2019-05-21 22:02:06 UTC,"Not sure if this is the best way to solve it.. but for those who want a fix, this can be added after these lines:"
1821592,2019-05-22 08:28:55 UTC,"Hi Marek, thanks for debugging this issue. In most containers (including watcher) we map /etc/localtime:/etc/localtime:ro as a docker volume. It seems this is not sufficient in this case though."
1821592,2019-05-21 21:25:23 UTC,"Hi again, seems I was wrong. After diggin in some code in apscheduler it seems it needs /etc/timezone as well. I included it and services started."
1821592,2019-05-21 19:05:34 UTC,Don't think this is related to timezone issues but configuration of Watcher.. I'll troubleshoot this and check back!
1821592,2019-05-21 18:35:52 UTC,"Hey, just tested this and can confirm the problem. Except for Watcher, Freezer is also affected by this issue."
1821592,2019-04-10 13:26:29 UTC,We map /etc/localtime into the container. What timezone are you in?
1821592,2019-04-10 13:26:12 UTC,Which version of kolla/kolla-ansible? Which OS? Source/binary?
1821592,2019-05-23 18:48:00 UTC,https://review.opendev.org/661068 Add missing timezone mount for watcher (apscheduler).
1821593,2019-04-10 13:16:15 UTC,This seems like it could be a Trove issue?
1821593,2019-11-12 04:17:56 UTC,[Expired for kolla because there has been no activity for 60 days.]
1821594,2019-06-26 19:00:49 UTC,Improved test case with more detailed steps in order to make it easier to script and validate the output
1821594,2019-06-26 13:08:50 UTC,"Hello Rodrigo, or anyone else affected,"
1821594,2019-06-18 20:37:54 UTC,"Hello Rodrigo, or anyone else affected,"
1821594,2019-06-18 03:40:50 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1821594,2019-06-17 18:55:10 UTC,"Rodrigo, thank you for the patches and debdiffs. I've uploaded your changes to cosmic and bionic unapproved queues where they are awaiting review from the SRU team.
https://launchpad.net/ubuntu/cosmic/+queue?queue_state=1&queue_text=nova
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=nova"
1821594,2019-05-30 18:34:00 UTC,"Reviewed:  https://review.opendev.org/658136
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=944b24f462f8785a5c039efb74eec5310ef7729e
Submitter: Zuul
Branch:    stable/queens"
1821594,2019-06-10 19:03:41 UTC,This will be fixed in the 19.0.1 stein stable point release via https://bugs.launchpad.net/cloud-archive/+bug/1831754.
1821594,2019-06-06 06:24:35 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1821594,2019-06-27 00:34:01 UTC,Cosmic Rocky verified using [Test Case]. Attached output.
1821594,2019-05-30 15:14:40 UTC,"Reviewed:  https://review.opendev.org/661349
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5600309a1fc38f0f98629608d3f41eacf66d714a
Submitter: Zuul
Branch:    stable/queens"
1821594,2019-05-30 10:13:28 UTC,"Reviewed:  https://review.opendev.org/652153
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b8435d6001c30e67ac277e414b11708d4d660555
Submitter: Zuul
Branch:    stable/queens"
1821594,2019-06-11 14:21:17 UTC,Fyi I'm currently working on a train snapshot (and blocked atm) which is needed prior to SRU of any other releases.
1821594,2019-06-27 00:34:32 UTC,Bionic Rocky verified using [Test Case]. Attached output.
1821594,2019-07-03 12:53:44 UTC,"This bug was fixed in the package nova - 2:18.2.0-0ubuntu2~cloud0
---------------"
1821594,2019-07-02 16:37:21 UTC,This bug was fixed in the package nova - 2:18.2.0-0ubuntu2
1821594,2019-07-03 12:53:43 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1821594,2019-07-03 16:26:59 UTC,"Hello Rodrigo, or anyone else affected,"
1821594,2019-07-05 15:16:29 UTC,Bionic Queens verified using [Test Case]. Attached output above ^.
1821594,2019-07-08 09:26:20 UTC,Marking Disco/Stein as Fix Committed since it is the same in bug 1831754
1821594,2019-07-10 21:39:42 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1821594,2019-09-27 09:05:20 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1821594,2019-07-11 15:57:47 UTC,"Hello Rodrigo, or anyone else affected,"
1821594,2019-07-11 19:32:45 UTC,Xenial Queens verified using [Test Case]. Attached output.
1821594,2019-08-06 17:39:36 UTC,This bug was fixed in the package nova - 2:17.0.10-0ubuntu2
1821594,2019-08-29 13:02:15 UTC,This was fixed in queens nova package version 2:17.0.10-0ubuntu2~cloud0
1821594,2019-05-24 19:11:23 UTC,"Reviewed:  https://review.opendev.org/658834
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=01bfb7863c80c43538632952ec9f1728f0b412d6
Submitter: Zuul
Branch:    stable/rocky"
1821594,2019-07-02 16:37:06 UTC,"The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821594,2019-05-24 19:11:12 UTC,"Reviewed:  https://review.opendev.org/659338
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dac3239e92fc1865cacc17bbfbd2316072a9d26e
Submitter: Zuul
Branch:    stable/rocky"
1821594,2019-03-26 13:58:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/647741"
1821594,2019-05-24 10:24:12 UTC,"Reviewed:  https://review.opendev.org/652150
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c6a42cd3b38528bbf410b33c3bfc384600ae053f
Submitter: Zuul
Branch:    stable/queens"
1821594,2019-03-25 14:01:50 UTC,IRC discussion here:
1821594,2019-03-25 17:20:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647546"
1821594,2019-03-25 18:06:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647566"
1821594,2019-03-29 11:08:50 UTC,"Reviewed:  https://review.openstack.org/647546
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=408ef8f84a698f764aa5d769d6d01fd9340de2e5
Submitter: Zuul
Branch:    master"
1821594,2019-04-02 18:33:21 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/649421"
1821594,2019-04-05 01:02:23 UTC,"Reviewed:  https://review.openstack.org/647566
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=03a6d26691c1f182224d59190b79f48df278099e
Submitter: Zuul
Branch:    master"
1821594,2019-04-05 01:02:35 UTC,"Reviewed:  https://review.openstack.org/647741
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4d0aab16ecac5128a20ab9229d444bc49a9c722b
Submitter: Zuul
Branch:    master"
1821594,2019-04-05 20:28:29 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650437"
1821594,2019-05-24 16:12:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/661349"
1821594,2019-04-12 20:37:32 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/652146"
1821594,2019-04-12 20:56:28 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/652150"
1821594,2019-04-12 21:10:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/652153"
1821594,2019-04-12 18:58:14 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/652127"
1821594,2019-04-12 21:46:49 UTC,"Oh furthermore we'd need https://review.openstack.org/#/c/479802/ (or a part of it) in Pike for Ic7d78ad43a2bad7f932c22c98944accbbed9e9e2, so I probably won't pursue that either for now."
1821594,2019-05-15 16:40:10 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/659338"
1821594,2019-04-12 21:35:25 UTC,I'm not sure how practical it will be to try and cleanup the leaked allocation in stable/pike because there was a pretty decent sized refactor of the allocation cleanup code in Queens:
1821594,2019-05-14 01:02:53 UTC,"Reviewed:  https://review.opendev.org/657870
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=873ac499c50125adc2fb49728d936922f9acf4a9
Submitter: Zuul
Branch:    master"
1821594,2019-05-13 21:53:09 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/658929"
1821594,2019-05-13 21:30:54 UTC,The bug is unfortunately not fixed in rocky as shown in this recreate test:
1821594,2019-05-14 16:47:57 UTC,"Reviewed:  https://review.opendev.org/658929
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d7d7f115430c7ffeb88ec9dcd155ac69b29d7513
Submitter: Zuul
Branch:    stable/stein"
1821594,2019-04-16 15:37:07 UTC,"Reviewed:  https://review.openstack.org/652146
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=37ac54a42ec91821d62864d63c486c002608491b
Submitter: Zuul
Branch:    stable/rocky"
1821594,2019-04-16 15:17:21 UTC,"Reviewed:  https://review.openstack.org/652127
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2a25d1e48bce34c7dd0d5783908fdb0dc1b19113
Submitter: Zuul
Branch:    stable/rocky"
1821594,2019-04-12 23:20:50 UTC,"Reviewed:  https://review.openstack.org/650437
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5f515060f6c79f113f7b8107596e41056445c79f
Submitter: Zuul
Branch:    stable/stein"
1821594,2019-04-12 23:20:39 UTC,"Reviewed:  https://review.openstack.org/649421
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=972d4e0eb391e83fe8d3020ff95db0e6a840a224
Submitter: Zuul
Branch:    stable/stein"
1821594,2019-05-08 19:05:03 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657870"
1821594,2019-03-25 15:56:30 UTC,This goes back to Pike as noted in the bug description. Before Pike the ResourceTracker.update_available_resource code would at least correct the allocations based on the instance.flavor and instance.host.
1821595,2020-04-09 18:28:26 UTC,"Folks seem to think this is the fix,
https://stackoverflow.com/questions/55197032/android-emulator-whpx-failed-to-emulate-mmio-access-exit-code-3"
1821595,2020-09-29 23:54:40 UTC,"Hi. I didnt build Qemu but I downloaded the last version 5.1.0 from https://qemu.weilnetz.de/w64/ and the error ""Failed to emulate MMIO access with EmulatorReturnStatus: 2"" happens when I use -drive if=pflash or -pflash with -accel whpx."
1821595,2020-04-12 01:31:53 UTC,Should say - I rebuilt (today). Still no joy.
1821595,2020-04-12 01:31:35 UTC,"Hi,"
1821595,2020-04-09 20:22:41 UTC,"Sorry, not quite following your comment - but it's likely me :-(."
1821595,2020-04-09 20:07:44 UTC,I don't think QEMU can do anything to fix this - you need to build against a new library.
1821595,2020-04-09 18:30:33 UTC,"And here,
https://www.reddit.com/r/androiddev/comments/c7u6h2/android_virtual_device_on_ryzen/"
1821595,2020-04-09 17:53:36 UTC,I think WHPX can't some MMIO requests for EFI.
1821595,2020-04-06 13:54:57 UTC,As far as I can tell QEMU just hands this off to the whpx emulation sub-system:
1821595,2020-04-06 07:36:22 UTC,Sorry for the typo. I should have mentioned that this issue is WHPX related. I have created an issue in WHPX Github page about it.
1821595,2020-04-06 07:23:13 UTC,"Which OS do you try with qemu? IIRC Windows 10 should work well with WHPX. Also,this issue is qemu depended that they don't handle specific MMIO instruction/exit."
1821595,2020-04-06 01:14:35 UTC,"FYI, I was curious if this was a Ryzen issue or not (which I am running), so I tried another machine - here are the two combos I tried,
1) Ryzen 5 2600X, Windows 19041.172
2) Core i5-6600K, Windows 18363.720"
1821595,2020-04-06 00:51:45 UTC,"Hi,"
1821595,2020-04-09 17:41:10 UTC,"Hi,"
1821596,2019-03-25 15:45:15 UTC,"The failures are still there https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/f/firewalld/20190325_151135_3b840@/log.gz:
2019-03-25 15:04:45 ERROR: COMMAND_FAILED: '/sbin/ipset add foobar 10.1.2.0/22' failed: ipset v6.38: Kernel support protocol versions 6-7 while userspace supports protocol versions 6-6
./rhbz1601610.at:60: hard failure"
1821596,2019-09-20 08:31:23 UTC,"The issues from previous cycle were resolved but it looks like it's failing again in eon now.
I spent some time on it previous cycle but don't plan to look at the new issue so I'm going to unassign myself now."
1821596,2019-03-25 14:22:18 UTC,"For whoever looks at this, FYI, it looks like the last time these two tests passed was with a 4.19 kernel: testbed running kernel: Linux 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 UTC 2019"
1821596,2019-03-25 14:25:03 UTC,"Ah, looks like seb128 was already aware of this since he prepared the ipset 7.1 upload: https://launchpad.net/ubuntu/+source/ipset/7.1-0ubuntu1"
1821597,2019-03-26 08:25:05 UTC,apport information
1821597,2019-06-10 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1821597,2019-04-10 09:28:10 UTC,Possible to update the BIOS to its latest version (A25)?
1821597,2019-04-03 11:03:37 UTC,"Not new. It's been haunting me since I upgraded from 14.04 to 16.04. I finally managed to make some sense of it and reproducible tests. Noticed first at #1663555, but was unable to narrow it down."
1821597,2019-03-26 08:44:18 UTC,"Apport logs are from test case B), since it's the most reliable way to both reproduce a problem and (in some cases) still get a working desktop."
1821597,2019-03-26 08:25:10 UTC,apport information
1821597,2019-03-26 08:25:09 UTC,apport information
1821597,2019-03-26 08:25:08 UTC,apport information
1821597,2019-03-26 08:25:07 UTC,apport information
1821597,2019-03-26 08:25:03 UTC,apport information
1821597,2019-04-03 08:50:47 UTC,Is this a new issue after kernel upgraded to 4.4.0-143?
1821597,2019-03-26 08:25:00 UTC,apport information
1821597,2019-03-26 08:24:49 UTC,apport information
1821597,2019-03-26 08:24:51 UTC,apport information
1821597,2019-03-26 08:25:02 UTC,apport information
1821597,2019-03-26 08:24:52 UTC,apport information
1821597,2019-03-25 14:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821597,2019-03-26 08:24:56 UTC,apport information
1821597,2019-03-26 08:24:58 UTC,apport information
1821597,2019-03-26 08:24:59 UTC,apport information
1821597,2019-03-26 08:24:53 UTC,apport information
1821599,2019-04-12 23:29:28 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.0 release.
1821599,2019-03-25 15:39:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647514"
1821599,2019-04-01 08:33:40 UTC,"Reviewed:  https://review.openstack.org/647514
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=6b0be5c5bacd91bb94ec6b75715affb9777e568d
Submitter: Zuul
Branch:    master"
1821599,2019-04-02 11:34:38 UTC,"Reviewed:  https://review.openstack.org/648958
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=79a976307b8dc1741f72788f88486b7289fdda34
Submitter: Zuul
Branch:    stable/rocky"
1821599,2019-04-04 07:35:24 UTC,"Reviewed:  https://review.openstack.org/649172
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=404dd96343e3fb25590a29b504ef1c952650a54a
Submitter: Zuul
Branch:    stable/pike"
1821599,2019-04-04 07:46:32 UTC,"Reviewed:  https://review.openstack.org/649171
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ffd68d7cadf92e49dd753de40839a634aa98ad0d
Submitter: Zuul
Branch:    stable/queens"
1821599,2019-04-05 13:59:27 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.
1821599,2019-04-12 23:28:53 UTC,This issue was fixed in the openstack/kolla-ansible 5.0.5 release.
1821599,2019-04-12 23:29:02 UTC,This issue was fixed in the openstack/kolla-ansible 6.2.0 release.
1821600,2019-04-12 21:16:17 UTC,"Reviewed:  https://review.openstack.org/647482
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=4826a2de3a7fecc8338cf113c15fa51006dfd020
Submitter: Zuul
Branch:    stable/queens"
1821600,2019-06-21 15:25:54 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1821600,2019-03-25 14:23:32 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/647482"
1821606,2019-03-25 15:57:09 UTC,Verified on Linux as well
1821606,2019-04-17 22:30:56 UTC,This can also be duplicated by the following steps:
1821606,2019-04-19 22:10:39 UTC,I've attached a screen recording of the issue.  It is not even necessary to add or remove a symbol library.  All you have to do is enable or disable the library and the effect is the same.  It is also not necessary to open and cancel the symbol chooser dialog.  All you have to do is left click on a symbol after the lib table change and boom.  The symbols are gone.  I tested this on:
1821606,2019-04-30 17:46:10 UTC,"Fixed in revision 7d803437e28517434282261a8ca75836ca6e37b8
https://git.launchpad.net/kicad/patch/?id=7d803437e28517434282261a8ca75836ca6e37b8"
1821606,2019-04-30 18:14:50 UTC,"I cannot believe the bug has not been a bigger problem than what it was.  It had the potential to break everything because the symbol library link in SCH_COMPONENT wasn't being cleared when the link resolver code failed to find the symbol which left all of the LIB_PIN pointer references broken.  If there are any other unexplained Eeschema crash bug reports when either a symbol library is removed or renamed, this fix most likely will resolved them."
1821606,2019-05-02 11:57:46 UTC,"Great job done, Wayne!
Please do not forget to cherry-pick and commit the same patch to 5.1 branch.
Cheers,
Miljan"
1821606,2019-05-02 12:16:17 UTC,"@Miljan, thanks.  I didn't forget to cherry-pick it to 5.1.  I wanted to give it some time to be tested to make sure there were no other issues before I cherry-picked it."
1821609,2019-04-07 00:10:42 UTC,third boot of same install ..
1821609,2019-04-06 23:45:31 UTC,"testing xubuntu-disco-daily.iso apr 06, 2019 First boot fine plymouth, and xorg/lightdm started normally.. did a number of updates and rebooted."
1821609,2019-04-05 17:43:33 UTC,just some summary thoughts in addition to point to some anomalies ..
1821609,2019-04-05 11:45:21 UTC,"I've been merrily switching between OS's without this kind of issue for more than 10 years ..
the behaviour changed recently in the last 30 days ..
it was fine prior to that ..
This is a regression bug and will annoy anyone working with multiple instances of disco xubuntu for testing.."
1821609,2019-04-05 07:23:00 UTC,"Your setup is anything but a typical one, and bugs should not be used to ""ask"" how something works the way it does. You mentioned that the ""original"" disco install always works fine, so I don't think there's a valid bug here at all?"
1821609,2019-04-04 17:43:29 UTC,whoops added the wrong attachment above it is the one including the grub-update dialog .. instead of being the bot after the command
1821609,2019-04-04 04:51:19 UTC,i915 is loaded just fine on your first journal log:
1821609,2019-04-04 16:16:44 UTC,here is the journalctl boot log for sda6 /zlink4 booted by it's own install of grub (self grub)
1821609,2019-04-04 16:01:58 UTC,here we have a normal journalctl boot log .. notice the size .. more entries .. about 1 minute start to finish source the partition that always works lightdm starts normally plymouth appears on screen etc.
1821609,2019-04-04 11:33:55 UTC,so why the peculiar behaviour that lightdm works when the partition installed native grub boots the system
1821609,2019-04-04 04:25:19 UTC,a little digging and plymouth is supposed to work with drm modesetting drivers which means i915 has to be loaded for it to work .. so not seeing it means ..some hardware detection has failed .. is that part of plymouth or something else?
1821609,2019-04-04 03:54:32 UTC,"Kernel module will load if added to /etc/ modules .. I have my sda1
partition running kernel 5.0.0-8.9  as are the iso's tested recently .. my
sda1 partition  loads i915 without using /etc/modules.. I notice that the
recent isos do not show Plymouth progress screen at startup..is that
relevant?"
1821609,2019-04-04 17:37:33 UTC,okay generated the default grub.cfg via sda6 grub-install boot instance .. vt.handle=1 is set by default for self root boot about a minute to boot
1821609,2019-04-09 18:43:05 UTC,okay apr 8 and apr 9 iso's have same issues kept logs of various boots into the fresh installs .. no change in grub-source during testing was made .. all with fresh installs
1821609,2019-06-18 04:17:30 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1821609,2019-04-11 14:54:49 UTC,okay I stumbled across something .. the network install .. used netplan to set-up my wifi connection to start on boot .. so as soon as systemd networkd starts wifi is started  NetworkManager thus has no access or anyway to try for other networks.. so I tried to change this.. If I edit the config files to give exclusive control to NetworkManager ..run netplan apply as long as I don't reboot I can use NetworkManager as per normal
1821609,2019-04-11 17:02:59 UTC,"okay a previous ""fresh install that was crashing plymouth screen/lightdm/xorg was fixed by copying a known working set of netplan conf files into  /etc/netplan .."
1821609,2019-04-15 13:25:31 UTC,"bug is still present in disco xubuntu iso ""final"" 04-13.1-2019"
1821609,2019-04-16 00:30:13 UTC,"Okay, this bug has absolutely nothing to do with grub or netplan. Changing the renderer couldn't possibly affect the behavior of X, and the grub configuration looks, at a glace, to be run-of-the mill; pretty much default if you disregard that there is any number of different installs on the system."
1821609,2019-04-16 02:12:10 UTC,I will try to do videos for you tomorrow it is getting late in the day here ..
1821609,2019-04-16 20:07:45 UTC,video of sda8 non-native grub boot (a disco-xubuntu iso install)  sda9 has installed grub (also a disco-xubuntu iso install )  will show in next video uploaded
1821609,2019-04-16 20:41:27 UTC,"video of sda9 boot using sda9 install of grub (native grub) .. note absence of plymouth .. flash at top edge of screen was missed .. note brief appearance of lightdm  .. short gap then lightdm reappears .. xorg.0.log.old records the crash .. similar to others above
xorg.0.log records successful xorg/lightdm start .."
1821609,2019-04-16 23:58:32 UTC,okay turned back the clock .. to a spinning metal disk previously installed in this hardware .. ran a number of test installs all work fine .. cosmic/bionic/disco early version disco final all work boot normally .. always ..
1821609,2019-04-17 00:47:15 UTC,"of course the sda1 partition (on the SSD) has never failed to work properly no matter which grub source (installs on sda1,sda6,sda7,sda8,sda9) is used plymouth always appears when sda1 boots..
this disco version was installed jan 10 with a bootstrap log date of oct 13, 2018 .. it has been updated regularly ever since .. daily from proposed .. without issues .."
1821609,2019-04-17 01:38:51 UTC,okay I have another solution  to the timing issue .. add two partition mounts to fstab ..
1821609,2019-04-18 13:35:57 UTC,Fine tuning:  only one extra mount is necessary .. then plymouth finishes very quickly .. and xorg/lightdm  start normally!
1821609,2019-06-18 04:17:28 UTC,[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.]
1821609,2019-04-04 02:07:38 UTC,If you're sure that's the problem then we would need to figure out which kernel version it started in. Please try some different kernel versions:
1821609,2019-04-11 11:12:22 UTC,"An additional data point  for reference .. did a netboot install of xubuntu  using ""daily"" amd64 netboot mini.iso ..  base install followed by taskselect install of xubuntu .."
1821609,2019-04-03 01:44:33 UTC,"now this begs the question why does kernel module i915 not auto load anymore?
i.e. the newer iso's since mid-march ..??? what got yanked out that would cause this ??"
1821609,2019-03-30 15:30:31 UTC,oh one thing I noticed and did not mention .. the plymouth screen fails to appear (just a redish flash at top of screen) when booting from a non-native grub for the recent daily xubuntu iso's  if the native grub is used plymouth screen appears..
1821609,2019-04-02 14:54:02 UTC,okay after rebooting via grub installed by sda1 .. as before .. red flash (no plymouth) lightdm briefly displays login screen .. then underline cursor then blank screen.
1821609,2019-03-25 16:14:09 UTC,"this bug was filed from sda6 partition..
with this command and the following errors generated"
1821609,2019-03-26 02:35:22 UTC,"You seem to be booting in recovery mode, which will also break graphics support in its own way :/"
1821609,2019-03-26 03:51:12 UTC,added journalctl -b-1 > prevboot.txt
1821609,2019-03-26 03:54:07 UTC,added: dpkg -l > allpackage.txt
1821609,2019-03-26 04:05:13 UTC,second attempt journalctl -b-1 > prevboot2.txt
1821609,2019-03-26 04:05:17 UTC,second attempt journalctl -b-1 > prevboot2.txt
1821609,2019-04-03 01:29:38 UTC,okay .. thought about this for a bit i915 compiled as module by default in kernel sources.. lets force it to load..
1821609,2019-03-26 04:19:09 UTC,It appears the problem is related to lightdm and PAM:
1821609,2019-03-26 04:21:40 UTC,Please have a look to see if any of the existing bug reports might be the same issue:
1821609,2019-03-26 04:26:00 UTC,It sounds like the solution might be a simple matter of adding 'derk' to /etc/group on line:
1821609,2019-03-26 04:55:38 UTC,"journalctl -b-1 > prevboot3.txt      post group change .. no joy ..also
makes machine wide open no passwd required
 .. i will revert this"
1821609,2019-03-26 05:21:37 UTC,the above comment .. is perhaps a bit brief .. in spite of the log showing a pam pass no login screen was available .. it was blanked out .. gone just a cursor and that also disappeared after a bit .. (still using testing partition sda6 for all this)
1821609,2019-03-26 21:19:31 UTC,okay determined all my installs of xubuntu including the one that works no matter what the others are doing ..
1821609,2019-03-26 21:32:52 UTC,"okay did something unusual .. i copyed my apt sources and trust files from the working version sda1
to the copy on sda6 the added a series of new proposed updates including a new kernel version
on reboot the updated sda6 worked as expected:"
1821609,2019-03-26 04:14:43 UTC,"okay tested twice by rebooting into sda6 using sda1-installed-grub ,"
1821609,2019-03-27 01:49:37 UTC,Thanks for figuring that out.
1821609,2019-03-27 01:57:17 UTC,Oh. On second thoughts I think you might have made a mistake.
1821609,2019-03-27 11:37:22 UTC,this effected only the more recent installs
1821609,2019-03-27 11:59:13 UTC,addional clarification .. if sda6 (recovery booted or chrooted) installed grub then sda6 boots with some brief flashing normally. if sda7 or sda1 (recovery booted or chrooted or a normal boot for sda1) installed grub then sda6 would boot and lighjtdm would briefly flash onto screen and the disappear (blank screen) showing just aflashing underline cursor.
1821609,2019-03-27 22:47:47 UTC,okay still bug present in xubuntu-disco-amd64-desktop-beta.. still uses kernel 5.0.0-7
1821609,2019-03-27 23:08:27 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1821609,2019-03-28 00:55:00 UTC,"stranger and stranger .. if you install kernel 5.0.0-8.9 at the first boot into any new install partition before changing any thing else .. it does not fix the issue .. once you return sda1 to being grub master .. neither sda7 nor sda6 will keep lightdm running ..both briefly flash lightdm login screen and then blank out screen , briefly showing a cursor ..  a long hold down of power button does eventually powerdown machine .. note: can't even get to consoles .. not a nice fail."
1821609,2019-03-28 02:02:50 UTC,Xubuntu daily images are still missing the fix for bug 1819943. So please wait until a newer image is available which includes that fix before retesting.
1821609,2019-04-01 02:22:01 UTC,It looks like daily images should now contain the fix for bug 1819943 (so we can rule it in or out). Please download and test an image dated April or later:
1821609,2019-04-01 12:09:09 UTC,"xubuntu iso for daily april 1, 2019 .. no change"
1821609,2019-04-02 14:36:06 UTC,iso april 2 2019 tested .. adding xorg.0.log & xorg.0.log.old files from first boot into fresh install .. There was a 1 to 2 second flicker in lightdm  appearing then blanking and then reappearing on first boot  .. have not yet rebooted into this from grub as installed by sda1 .. wanted to save the above log files first.
1821609,2019-04-02 14:40:01 UTC,"the "" surprise log file "" not expected on a first boot .. with normal xorg startup should not exist .."
1821609,2019-03-26 22:00:48 UTC,"okay did the same thing to my sda7  partition install the 5.0.0.8 kernel works lightdm is stable etc.
but boot with the 5.0.0.7 kernel fails as per before .. so choice of kernel or it's corresponding initrd is the problem ..here a kernal upgrade fixes the issues"
1821611,2019-05-03 23:39:45 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.opendev.org/651802"
1821611,2019-04-18 14:58:17 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.5.0 release.
1821611,2019-04-11 14:41:17 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/651802"
1821611,2019-03-26 17:48:05 UTC,"Reviewed:  https://review.openstack.org/647597
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=374fafd66afa792ba197403b479dadbfa3055bce
Submitter: Zuul
Branch:    master"
1821617,2019-03-25 17:00:08 UTC,This change was made by a bot.
1821617,2020-06-09 04:33:04 UTC,Please test 20.04.
1821617,2020-08-09 04:17:18 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1821625,2019-07-05 12:51:42 UTC,"> @Dan did that already contain the fix you expect or would considering a seccomp be useful?
"
1821625,2019-08-22 16:15:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1821625,2019-08-12 14:05:07 UTC,"to close this out, the latest systemd build, version 237-3ubuntu10.25, picked up the correct pkey_mprotect value from the updated kernel and now does not fail the test."
1821625,2019-08-22 17:04:59 UTC,"$ reverse-depends -b -r xenial libseccomp-dev
Reverse-Build-Depends
=====================
* golang-github-seccomp-libseccomp-golang
* lxc
* ocserv
* qemu
* systemd
* tor
* ubuntu-core-launcher"
1821625,2019-07-05 21:53:51 UTC,I agree with the analysis in comment #13 about stress-ng.
1821625,2019-07-05 14:49:17 UTC,"$ reverse-depends -l -r bionic -b libseccomp-dev |& xargs
apt chrony docker.io flatpak gnome-desktop3
golang-github-seccomp-libseccomp-golang kscreenlocker lxc man-db ocserv
qemu snapd stenographer systemd tor tracker-miners usbguard"
1821625,2019-07-05 14:16:12 UTC,"> Per [1] this symbol is present in: firejail, elogind, valgrind, glibc, musl, linux,
> systemd, strace, stress-ng, libseccomp, qemu
"
1821625,2019-07-05 12:53:43 UTC,"Marking this bug as Invalid for libseccomp; I still disagree with their upstream decision re: their header file, but it doesn't appear any rebuild or SRU code change is needed for it for this bug."
1821625,2019-07-05 07:38:03 UTC,"Per [1] this symbol is present in: firejail, elogind, valgrind, glibc, musl, linux, systemd, strace, stress-ng, libseccomp, qemu"
1821625,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1821625,2019-07-04 08:00:23 UTC,"I rebuilt systemd using the 4.15.0-55 kernel headers:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1821625.2"
1821625,2019-07-03 13:07:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1821625,2019-06-03 17:35:32 UTC,"FYI, please note that seccomp 2.4.1 was pushed to bionic in https://usn.ubuntu.com/4001-1/ on 2019/05/30. It shouldn't affect this bug report AFAICT because while the 2.4.1 Ubuntu packaging drops these patches, the upstream commits for lp-1815415-arch-update-syscalls-for-Linux-4.9.patch and lp-1815415-update-the-syscall-tables-to-4.10.patch are both included in 2.4.1. Based on the 2.4.1 changelog, nothing else was changed in this area, so 2.4.1 should be affected in the same way as 2.3.1-2.1ubuntu4.1."
1821625,2019-06-03 12:13:22 UTC,"I'm leaving this as marked against libseccomp, as I don't understand why it is redefining kernel header values as invalid numbers in its public header file (so that other programs using its header files pull in those invalid syscall numbers).  I don't think it should but I'll leave the decision to discuss this upstream to someone more familiar with libseccomp."
1821625,2019-06-03 12:11:15 UTC,"> After these patches are applied to bionic, both libseccomp and systemd
> will need to be rebuilt - libseccomp rebuilt against the kernel
> headers, and systemd against the libseccomp headers.
"
1821625,2019-06-03 12:03:37 UTC,coverletter explanation as sent to kernel-team list:
1821625,2019-05-25 12:14:42 UTC,"i marked this as against both libseccomp and the kernel, but as I mentioned in the last comment, only 1 of them needs fixing.  My suggestion for the best approach is to add pkey_mprotect support to the bionic ppc64el kernel."
1821625,2019-05-25 12:11:22 UTC,This is not a bug in systemd.
1821625,2019-07-04 08:03:30 UTC,"systemd will require a rebuild to pick up this fix in the kernel headers, but that happens often enough I don't think a no-change rebuild is needed."
1821628,2019-11-14 11:46:41 UTC,"Thank you :-)
M"
1821628,2019-11-14 01:35:18 UTC,Resuming full backups is now fixed in 40.3
1821630,2019-03-27 07:53:30 UTC,apport information
1821630,2019-06-04 15:54:40 UTC,"Tested this issue once more by enabling secure boot in the BIOS, and booting into Ubuntu 19.04 through GRUB2, no success as previously."
1821630,2019-06-03 20:47:36 UTC,"Thanks, that looks like the standard set of Microsoft-issued revocations, with two differences:"
1821630,2019-06-03 14:47:33 UTC,Ok.  It's interesting to see that you have two other vendor keys in your DB:
1821630,2019-06-03 04:17:30 UTC,[Expired for shim (Ubuntu) because there has been no activity for 60 days.]
1821630,2019-04-04 01:20:33 UTC,You should also have the mokutil command installed.  Please also run: 'mokutil --export --db' and attach the DB*.der files to this report.
1821630,2019-03-27 17:33:01 UTC,"The strange behaviour after installing: sudo apt-get install shim-signed
Is while Grub2 menu load up, the screen becomes completely black, however, Grub2 itself is fuctional to launch an operating system such as Ubuntu and responds to keyboard."
1821630,2019-03-27 16:28:11 UTC,"Ok, and your efibootmgr output shows:"
1821630,2019-03-27 07:53:31 UTC,apport information
1821630,2019-03-27 07:53:29 UTC,apport information
1821630,2019-06-03 18:56:50 UTC,"vaidas@vaidas-SATELLITE-L855:~/Desktop$ mokutil --dbx
[key 1]
  [SHA-256]
  0000000000000000000000000000000000000000000000000000000000000000"
1821630,2019-03-26 18:45:30 UTC,"Installing shim-signed didn't help much.
Maybe I'll just wait for the standard Ubuntu 19.04 which will happen in the next month?"
1821630,2019-03-26 18:42:00 UTC,"I restarted the laptop, enabled Secure Boot option in the UEFI."
1821630,2019-03-26 18:37:16 UTC,"Right now, I installed it myself."
1821630,2019-03-26 18:35:55 UTC,"I extracted all the /var/log/apt/history.log.*.gz,
and grep'ed through them, these are the only occurences it found:"
1821630,2019-03-26 17:52:43 UTC,"On Tue, Mar 26, 2019 at 05:14:17PM -0000, BoQsc wrote:"
1821630,2019-03-26 17:14:17 UTC,"I installed it from USB flash drive that contained Ubuntu Desktop 18.10, quite a while ago: 2018.10.17
I did dual boot installation: Windows 10 were preinstalled, and so I installed Ubuntu."
1821630,2019-03-26 14:57:37 UTC,"How did you install this system?  If you were using the Ubuntu Desktop 18.10 installer, your system should have had both UEFI and BIOS bootloaders installed for you automatically, and using shim, so you should not get verification errors from the firmware.  But your bug report shows that you don't have the shim package installed."
1821630,2019-03-26 08:42:20 UTC,"Ps. that message stops computer from booting into Ubuntu. So, I'm forced to disable Secure Boot, if I want to use linux operating systems."
1821630,2019-03-27 04:38:53 UTC,Please run 'apport-collect 1821630' from the affected system.
1821630,2019-03-26 08:26:16 UTC,"Well, my problem is that when I enable Secure Boot in my Laptop's UEFI, I get this message popped out:"
1821630,2019-03-25 21:42:35 UTC,"Sure, but you need to give detail about exactly what you did, and what didn't work as expected."
1821632,2019-11-19 21:25:41 UTC,"Oops. Ubuntu 18.04 has dmidecode 3.0 not 3.1; this patch should work with that version (at least, it applies against unpatched upstream 3.0 anyway)."
1821632,2019-11-20 00:26:46 UTC,"The attachment ""0001-dmidecode-Only-scan-dev-mem-for-entry-point-on-x86.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1821632,2020-09-08 20:15:43 UTC,https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1858615 contains the comments indicating which git commit fixed this in the Ubuntu packages.
1821632,2020-01-09 20:56:26 UTC,Is there any chance of importing the fix from Debian?
1821632,2019-12-02 17:25:05 UTC,Is there any chance of taking this patch into Ubuntu 18.04? Thanks.
1821632,2019-11-19 21:06:11 UTC,"The upstream bug report is:
savannah.nongnu.org dmidecode bug 109697
(launchpad won't let me paste the whole link)"
1821632,2019-11-19 21:21:56 UTC,The upstream patch (which was made after upstream release 3.2) back-ported to upstream 3.1 release (Ubuntu 18.04 contains dmidecode 3.1); it should presumably apply cleanly to Ubuntu's dmidecode-3.1 source.
1821632,2019-11-19 21:04:42 UTC,"This bug is actually fixed in the dmidecode source code:
(links removed in case that's why launchpad won't let me save this comment)."
1821632,2019-11-19 20:42:32 UTC,"> Reading illegal memory should not crash the system
"
1821632,2019-11-03 21:21:42 UTC,This problem seems to occur with kernels provided by NVIDIA for their Jetson T2 and Xavier boards. I got it when programs like cfengine or ocs-inventory-agent periodically called dmidecode. This crashed a Xavier board.
1821632,2019-11-03 21:14:30 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821632,2019-04-10 01:49:11 UTC,We are using Ubuntu 18.04 (Bionic) Arm64 variant of distro
1821632,2019-04-10 01:48:15 UTC,We could see the random crashes while using ubiquity plugins when dmidecode (arm64) is installed on the system. If dmidecode package is removed the system is stable and no crash is observed.
1821632,2019-11-19 21:04:54 UTC,"The upstream commit is:
http://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d"
1821639,2019-03-29 14:42:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821639,2019-03-29 14:44:35 UTC,The analysis in the Debian bug fully applies to the Ubuntu package too. The bug makes the package unusable in disco.
1821639,2020-03-01 21:18:33 UTC,Still reproducible in focal
1821641,2019-04-15 02:21:46 UTC,Please update your system and tell us if the problem is now fixed.
1821641,2019-04-06 16:12:49 UTC,apport information
1821641,2019-04-09 06:08:49 UTC,Is it a laptop or a 2-in-1?
1821641,2019-04-09 18:27:03 UTC,"The HP Elitebook 840 G1 is a regular laptop, so the accelerometer is not frequently used. Even when it's functioning properly like in 18.04, it can accidentally rotate 90 degrees when you tilt it slightly. You would never use this unit tilted 90 degrees or upside down, so if it's possible to entirely disable screen rotation on this model it would be preferable."
1821641,2019-04-10 01:42:52 UTC,We get a few bug reports about similar problems on HP Pavilions. Maybe look at bug 1726160 for more hints.
1821641,2019-04-13 22:28:29 UTC,"Absolutely, you mentioned bug 1726160 in an earlier comment and it contained a functioning workaround - removing iio-sensor-proxy. The problem seems to originate from systemd mount matrix issues on HP laptops using the lis3lv02d accelerometer, however determining the status of the github issue (and whether it applies to me) is beyond my skills."
1821641,2019-04-15 02:21:30 UTC,"It looks like the fix went into systemd version 240, so it should be fixed in Ubuntu 19.04 now if you update your system..."
1821641,2019-04-21 13:45:04 UTC,"I tried it now, and unfortunately the bug still happens on an updated final Ubuntu 19.04 install."
1821641,2019-10-21 02:21:53 UTC,If that's a sufficiently different issue to this then please open a new bug.
1821641,2019-05-01 09:38:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821641,2019-07-09 13:41:34 UTC,"Can you find out how it was inverted for x, y and z?"
1821641,2019-10-18 16:03:15 UTC,"The issue was there in 19.04. However, I was able to flip the laptop upside down and then click the rotation button. This fixed the issue and displayed the screen in proper orientation."
1821641,2019-04-06 16:12:48 UTC,apport information
1821641,2019-10-26 15:59:36 UTC,"im having the exact same problem on fresh install of 19.04
solution is to run this command (in terminal) after the machine boots:"
1821641,2020-01-26 21:34:48 UTC,"always true with ubuntu 19.10 and HP elitebook 2540p
it's a fresh install with all patches suggested"
1821641,2020-01-28 02:21:20 UTC,You should probably log a new bug for the 2540p.
1821641,2020-02-23 20:22:27 UTC,The bug is gone on 20.04 daily (2020-02-23). Screen orientation is now correct on my Elitebook 840 G1.
1821641,2019-04-23 02:14:49 UTC,No problem. That just means this bug is quite different to bug 1726160.
1821641,2019-04-06 16:12:47 UTC,apport information
1821641,2019-04-06 16:12:41 UTC,apport information
1821641,2019-04-06 16:12:43 UTC,apport information
1821641,2019-03-26 00:22:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1821641,2019-03-27 01:51:31 UTC,Could you please try some older kernels (like 4.18) to see if the problem is caused by the new kernel in Ubuntu 19.04?
1821641,2019-03-30 19:52:43 UTC,I have now reverted all the way back to the kernel I use on 18.04 (4.15) and the issue still happens.
1821641,2019-04-01 02:23:50 UTC,Sounds like this may be somewhat related to HP bug 1726160.
1821641,2019-04-01 02:25:42 UTC,As a workaround please:
1821641,2019-04-06 16:12:45 UTC,apport information
1821641,2019-04-03 02:43:56 UTC,It sounds like this bug is correctly assigned to the kernel. No need to move it in my opinion.
1821641,2019-04-03 03:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821641,2019-04-02 19:43:09 UTC,"I followed the suggestions in the related bug report. Removing iio-sensor-proxy indeed solved the problem completely, with no need for rotation lock. Should I move the bug report somewhere else at this stage?"
1821641,2019-04-06 16:12:33 UTC,apport information
1821641,2019-04-06 16:12:35 UTC,apport information
1821641,2019-04-06 16:12:36 UTC,apport information
1821641,2019-04-06 16:12:37 UTC,apport information
1821641,2019-04-06 16:12:39 UTC,apport information
1821641,2019-04-06 16:12:40 UTC,apport information
1821641,2019-04-06 16:12:42 UTC,apport information
1821641,2019-04-06 16:12:32 UTC,apport information
1821646,2019-06-08 04:17:18 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821646,2019-04-02 16:05:17 UTC,"@Willem-  Yes.  Please indicate which components are being substituted in your export.  If you can provide the STEP files for the models that are referenced, we can look into this."
1821646,2019-04-02 15:50:01 UTC,"Update: The STEP model now imports into Fusion 360 perfectly, and I'm not sure what changed to cause it. The same issues still occur when importing into SolidWorks, but as a work-around I can import into Fusion 360, export a STEP of the assembly from there, and then import that into SolidWorks. If someone wants an example of an exported STEP file exhibiting this issue, let me know, but I think the issue isn't strictly KiCad, and is some weird compatibility issue between KiCad and SolidWorks."
1821646,2019-03-30 18:51:17 UTC,"lp:1784257 seems to do with scale/shift. I'm seeing that issue (shifting, not scaling) here, but I'm also seeing KiCad just blatantly assign incorrect STEP models. For example, on my test project, I have a separate bolt-on module for my DC/DC converter module. That module exports to a STEP fine, but then when I add it as a 3D file to the footprint for it in the larger project (the board it mounts to), it displays fine in the 3D viewer but gets exchanged for other parts when exporting a STEP file of the whole project. This is actually a significant issue for me as I'm designing this board as part of a larger mechanical assembly, and I'm seeing it happen with the big connector, and the DC/DC module - the two most important parts in the context of a mechanical assembly. Right now as a work-around I'm importing those parts into MCAD as separate components and mating them."
1821646,2019-03-30 16:14:01 UTC,"I mostly assigned it 5.1.1 as I wanted to review the issue when I get home, and I conso
Ider bugs where people are kind enough to add example files more urgent. The reporter did link a test project in this case."
1821646,2019-03-31 02:43:31 UTC,@Willem- We'll address the scale/shift issue separately.  Then we can target this bug report to the issue of part substitution.  Can you say which STEP file in your example project is not exporting (filename and refdes)?
1821646,2019-03-30 15:35:31 UTC,"@Seth, I removed it as a duplicate again. I suspected ot was an issue wit an outdated wrl model. IIRC the 3d viewer silently uses wrl models if it is named the same as a step model to better support kicad stepup. But the other issue memtioned that there were no wrl models, so I removed it as a duplicate."
1821646,2019-03-30 14:16:35 UTC,@Nick-  Can you add some details about why you feel this isn't the same as the lp:1784257
1821646,2019-03-27 20:06:41 UTC,"I don't have WRL models, and I am very sure that KiCad is using STEP files (which I have for all my 3D models) to build the 3D model of the whole board for STEP export."
1821646,2019-03-25 22:25:00 UTC,Do you have wrl models of your step files? Maybe those are used for the 3d viewer?
1821646,2019-03-30 16:02:03 UTC,"Ok but lp:1784257 is the STEP issue.  If there's something distinct that you'd like addressed in 5.1.1, can you add the specific details?"
1821648,2019-03-26 02:41:19 UTC,Please:
1821648,2019-05-25 04:17:43 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1821650,2019-03-26 06:32:21 UTC,"Apparently only Caja opened as superuser is allowed to read the partition label. Non superuser windows can only display the volume size. In addition, the non-superuser window shows the partitions of my internal drives that the superuser version leaves out."
1821652,2019-08-30 08:08:22 UTC,"same issue today on lenovo thinkpad x201 (i5-m520, 4gb, i915)
ctrl+alt+T wouldn't open term, plus couldn't change arrangement of displays (external vga was connected) - `xfsettingsd --replace` fixed issue"
1821652,2019-05-10 06:28:30 UTC,"same issue today on dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)  - 19.10 QA-testing"
1821652,2019-05-02 12:53:06 UTC,19.10 daily qa-test on d780 still (see last comment)
1821652,2019-05-02 12:45:57 UTC,"dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
Xubuntu 19.10 daily ISO QA-Test - occurred again."
1821652,2019-04-16 03:26:01 UTC,comments #7 (& #8) were for/during a QA-Test install in 'live' mode
1821652,2019-04-16 03:07:12 UTC,"comment #7 occurred on
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)"
1821652,2019-03-26 11:58:24 UTC,"// PLEASE NOTE: this is a re-do of prior comment (#5) at a slower pace
// PLEASE NOTE: and some steps only. Firefox wasn't loaded, I saved
// PLEASE NOTE: this to `mousepad` & is copied from there to launchpad"
1821652,2019-03-26 11:53:07 UTC,"// PLEASE NOTE: this an next comment are re-do's of this, as my right-screen rototated during this
// PLEASE NOTE: next comment is a retry of only some of the steps in this"
1821652,2019-03-26 10:25:45 UTC,Please obtain a debug log with this command:
1821652,2019-03-26 00:08:18 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1821652,2019-03-26 00:01:58 UTC,screenshot of what (display setup) I was trying to achieve.
1821652,2019-04-16 02:49:05 UTC,19.04 daily (RC actually) test..  screens wouldn't swap & my 'right' (that is defaulted on left) wouldn't rotate left...
1821662,2020-09-15 22:33:44 UTC,The version of xfce4-weather-plugin in the proposed pocket of Xenial that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.
1821662,2020-09-03 17:00:11 UTC,"After looking into https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin , it seems the developpers have switched the ""locationforecast"" product upto v1.9 since branch ""xfce4-weather-plugin-0.10.1"" and upto ""locationforecast"" v2.0 since commit 97601ab2 : https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/commit/97601ab2"
1821662,2020-09-03 16:34:31 UTC,"The pb. is related to the version of the ""locationforecast"" product used :
$ pkill xfce4-panel
$ nohup xfce4-panel 2> xfce4-panel.log &
$ grep weather- xfce4-panel.log | tail -2
weather-Message: 18:25:28.961: getting https://api.met.no/weatherapi/locationforecastlts/1.3/?lat=48.791599&lon=2.647500&msl=101
(wrapper-1.0:32695): weather-WARNING **: 18:25:29.179: Download of weather data failed with HTTP Status Code 404, Reason phrase: Not Found
$ curl https://api.met.no/weatherapi/locationforecast/1.3/healthz
404 Not Found
The specified version number is end-of-lifed for this product
$"
1821662,2020-09-03 16:06:09 UTC,The package xfce4-weather-plugin - 0.8.11-0ubuntu0.18.04.1 released by ubuntu/bionic-updates see [comment #44](https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1821662/comments/14) is not working anymore since today (2020-10-03) :
1821662,2019-12-30 19:37:13 UTC,Tried installing xfce4-weather-plugin_0.10.0-1_amd64.deb on an 18.04.3 LTS install of Xubuntu. A dependency error immediately appeared: libc6>=2.29.
1821662,2019-12-29 17:45:00 UTC,"As of 29 Dec. 2019, this problem still exists. As this problem is fixed in newer versions of xubuntu, it should be added to this version."
1821662,2019-07-03 19:29:29 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for xenial for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1821662,2019-04-03 13:43:33 UTC,This bug was fixed in the package xfce4-weather-plugin - 0.8.11-0ubuntu0.18.04.1
1821662,2019-04-03 13:43:27 UTC,"The verification of the Stable Release Update for xfce4-weather-plugin has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821662,2019-04-03 13:43:21 UTC,This bug was fixed in the package xfce4-weather-plugin - 0.8.11-0ubuntu0.18.10.1
1821662,2019-03-27 00:20:56 UTC,Verified in Bionic.
1821662,2019-03-27 00:41:00 UTC,I was able to reproduce and verify in Cosmic as well. Same warning as above:
1821662,2019-03-29 11:02:19 UTC,"Hello Sean, or anyone else affected,"
1821662,2019-03-26 10:54:24 UTC,Attaching bionic debdiff
1821662,2019-03-26 10:54:55 UTC,Attaching xenial debdiff
1821662,2019-03-26 11:11:43 UTC,Uploaded the following package versions:
1821662,2019-03-26 10:53:55 UTC,Attaching cosmic debdiff
1821662,2019-03-26 21:53:12 UTC,"Hello Brian, the change to the moon phase integration was directly related to the API replacement. The replacement consists of 3 patches: The first replaced the API without support for moon phase; the second included some improvements; and the third restored the moon phase integration. I added a comment in the Other Notes section explaining the changes."
1821662,2019-03-26 22:41:15 UTC,"Hello Sean, or anyone else affected,"
1821662,2019-03-26 22:43:14 UTC,"Hello Sean, or anyone else affected,"
1821662,2019-03-26 15:39:54 UTC,"It also looks like there was a change to ""moon phase"" integration. Could you please add a test case and regression potential for that?"
1821663,2019-04-29 16:03:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1821663,2019-04-03 22:05:40 UTC,"@Hui: I've installed the package as per comment #19 (sorry for the typo at #20) and this has fixed the problem.
I've skipped the instructions at #12. Do you need additional tests?"
1821663,2019-04-04 02:13:27 UTC,"@venturia,"
1821663,2019-04-04 09:12:52 UTC,"FWIW, I think a better way to do this is to ask Realtek to implement correct de-pop function for this platform."
1821663,2019-04-25 22:32:22 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1821663,2019-04-26 15:35:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1821663,2019-05-06 06:05:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821663,2019-05-14 22:54:20 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821663,2019-05-14 19:03:14 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1821663,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1821663,2019-05-14 19:06:48 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1821663,2019-05-17 05:35:57 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1821663,2019-05-21 13:04:12 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1821663,2019-04-03 21:56:17 UTC,"@Hui: I've installed the package as per comment #18 and this has fixed the problem.
I've skipped the instructions at #12. Do you need additional tests?"
1821663,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1821663,2019-04-03 13:41:41 UTC,Added two machines in the runtime pm blacklist:
1821663,2019-03-26 06:25:52 UTC,"Daniel,"
1821663,2019-04-03 13:32:11 UTC,"CONFIG_SND_HDA_POWER_SAVE_DEFAULT should stay enabled. If it's a driver bug, users will still face the same issue once runtime PM is in use."
1821663,2019-03-26 02:52:14 UTC,Thanks for the bug report. Since pulseaudio is unchanged (the same version) in 19.04 from 18.10 I think we can exclude that as a possible cause.
1821663,2019-03-26 06:45:10 UTC,Great.
1821663,2019-03-26 21:41:01 UTC,"Today I'm busy. I will check it tomorrow.
A-"
1821663,2019-03-30 14:43:18 UTC,I've done many tests. The last working kernel is:
1821663,2019-03-31 03:32:03 UTC,"I checked the new patches between rc3 and rc4, there are only some minor changes. In theory they will not introduce this problem."
1821663,2019-04-01 21:11:23 UTC,"Check done without positive results. RC3 works without noise, RC4 has
noise in background."
1821663,2019-04-02 03:32:46 UTC,"Do you mean that you installed the deb of #7 in the kernel-rc3, there is no noise, while installed the deb of #7 in the kernel-rc4, still has noise? So looks like it is not the alsa hda driver's issue, since the deb contains the driver exact same as the rc3."
1821663,2019-04-03 13:41:37 UTC,Added two machines in the runtime pm blacklist:
1821663,2019-04-02 05:49:03 UTC,and the alsa for RC4
1821663,2019-04-03 05:12:14 UTC,"It is an issue of power_save setting. It is not a driver's code issue, it is a kconfig issue. From rc4, the CONFIG_SND_HDA_POWER_SAVE_DEFAULT is set to 1 rather 0, then the codec enables the runtime PM, that introduce the noise."
1821663,2019-04-03 05:29:03 UTC,"please install this dkms on rc4 or v5.0 kernel, reboot and test."
1821663,2019-04-03 12:05:07 UTC,"@Hui does the test driver in comment #13 add 1002:437b to power_save_blacklist? From the duped bug seems we also want to add 8086:a170 to the blacklist as well, or else change CONFIG_SND_HDA_POWER_SAVE_DEFAULT back to 0."
1821663,2019-04-03 12:37:44 UTC,"@Seth,"
1821663,2019-04-02 05:47:33 UTC,"""Do you mean that you installed the deb of #7 in the kernel-rc3, there is no noise, while installed the deb of #7 in the kernel-rc4, still has noise?"" ===>>>> yes"
1821663,2019-04-03 12:57:12 UTC,"Ok, I guess I got the wrong id. Can you also add the ids from the duped bug so that can be tested too?"
1821665,2019-03-27 03:53:26 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/449275
1821666,2019-03-27 03:54:00 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/449275
1821667,2019-03-27 03:54:37 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/449275
1821668,2019-03-27 03:54:59 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/449275
1821673,2019-03-26 09:45:46 UTC,"This looks like an issue with tacker and it's devstack plugin, not with the devstack code itself."
1821675,2019-03-26 19:21:01 UTC,mixxx.log.3 stopped while opening 01 Beg.mp3. Please try to play this file again.
1821675,2019-06-09 04:17:18 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1821677,2020-12-16 14:15:04 UTC,"The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821677,2020-12-16 14:15:02 UTC,This bug was fixed in the package glibc - 2.27-3ubuntu1.4
1821677,2020-12-14 11:24:40 UTC,"All autopkgtests for the newly accepted glibc (2.27-3ubuntu1.4) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1821677,2020-12-08 19:02:36 UTC,"Hello hongtao.liu, or anyone else affected,"
1821677,2020-12-07 16:36:30 UTC,"Cosmic did not receive the fix, but I've prepared the fix and will upload it in the next days. The release will still take more than a week due to the aging requirement and due to waiting for the test results."
1821677,2020-11-30 13:28:11 UTC,Great! Thanks!    Any tentative release date for the next version?
1821677,2020-12-13 11:50:45 UTC,"ubuntu@bb:~/test$ dpkg -l libc6 | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version         Architecture Description
+++-==============-===============-============-=================================
ii  libc6:amd64    2.27-3ubuntu1.4 amd64        GNU C Library: Shared libraries
ubuntu@bb:~/test$ wget -q https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1821677/+attachment/5252188/+files/dl-big-note.tar.xz
ubuntu@bb:~/test$ tar -xf dl-big-note.tar.xz
ubuntu@bb:~/test$ cd dl-big-note/
ubuntu@bb:~/test/dl-big-note$ make
gcc -c -o dl-big-note-lib.o dl-big-note-lib.S
gcc -shared -o dl-big-note-lib.so dl-big-note-lib.o
gcc -o dl-big-note dl-big-note.c -ldl
ubuntu@bb:~/test/dl-big-note$ ./dl-big-note dl-big-note-lib.so"
1821677,2020-11-13 16:39:11 UTC,I am experiencing this same issue on  LIBC 2.27-3ubuntu1.3 and it appears to be the same dll. I did not see it with GLIBC 2.27-3ubuntu1.2
1821677,2020-11-13 16:31:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821677,2019-05-21 18:27:52 UTC,Is it fixed in 18.04 update release OR any plan to fix it?
1821677,2020-11-25 19:21:57 UTC,@arsnyder16 Thank you for the report about the regression. I'll queue up the fix for the next update.
1821677,2019-04-12 16:05:36 UTC,This bug was fixed in the package glibc - 2.29-0ubuntu2
1821677,2019-04-02 19:31:57 UTC,Attached is small test case to reproduce this issue.
1821677,2019-03-29 05:23:23 UTC,This regression caused by following patch. It is mostly arm code but also affecting x86. If I remove this patch segfault will go away.
1821679,2019-03-26 06:27:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647661"
1821681,2019-11-06 01:14:59 UTC,This issue was fixed in the openstack/kolla 9.0.0.0rc1 release candidate.
1821681,2019-07-18 00:38:26 UTC,This issue was fixed in the openstack/kolla 8.0.0.0rc2 release candidate.
1821681,2019-03-29 01:40:22 UTC,"This commit fixes this problem.
https://review.openstack.org/647664"
1821681,2019-06-14 01:15:12 UTC,This issue was fixed in the openstack/kolla 7.0.3 release.
1821684,2019-04-23 14:51:41 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1821684,2019-06-23 04:18:32 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1821685,2019-11-22 14:59:24 UTC,"@Ian, for some things which aren't clear (like unfold bus when the bus definition doesn't parse) we do include the ""No whatever"" entry."
1821685,2019-11-24 01:28:01 UTC,"Fixed in revision 99b9354a513364faa87c8db08cf95187d4520f26
https://git.launchpad.net/kicad/patch/?id=99b9354a513364faa87c8db08cf95187d4520f26"
1821685,2019-11-22 14:26:38 UTC,"@devs, a UI design preference question."
1821685,2019-03-26 07:57:13 UTC,"Why would you need to do that? If you really need to clear it, why not edit the config file directly?"
1821685,2019-03-26 08:38:28 UTC,"So, let's consider that I work before with 20 projects. The main folder where they are placed is renamed. I this situation all 20 projects which are displayed in the recent list will not work and I need to remove them.
I don't know how to edit config file directory, please give me a bit help."
1821685,2019-07-03 14:51:31 UTC,"A smarter move than clearing the history of ""Open recent"" would be to check if file is available?"
1821686,2019-03-26 07:40:44 UTC,"StacktraceTop:
 g_list_foreach (list=0x6a, list@entry=0x55ee122b5520, func=0x7fcdecda5c60 <garcon_menu_item_action_unref>, user_data=user_data@entry=0x0) at ../../../glib/glist.c:1012
 g_list_free_full (list=0x55ee122b5520, free_func=<optimized out>) at ../../../glib/glist.c:223
 garcon_menu_item_finalize (object=0x7fcde002cdb0) at garcon-menu-item.c:424
 g_object_unref (_object=<optimized out>) at ../../../gobject/gobject.c:3346
 g_object_unref (_object=0x7fcde002cdb0) at ../../../gobject/gobject.c:3238"
1821686,2019-03-29 14:22:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821688,2019-04-10 10:31:19 UTC,This bug was fixed in the package ukui-control-center - 1.1.7-0ubuntu1
1821691,2019-03-26 08:06:33 UTC,So the treeview is updated correctly if the library removed from the library table is non-empty?
1821691,2019-03-26 08:25:04 UTC,Yes
1821691,2019-03-26 08:32:10 UTC,"Sorry, I was wrong
It seems that is not important of the library is empty or not
The bug happens when the library was added from Library Editor and the Library Editor is not restarted."
1821691,2019-06-13 21:34:21 UTC,"Fixed in revision 028973d182504380e3a3a2904e67d91b2f439974
https://git.launchpad.net/kicad/patch/?id=028973d182504380e3a3a2904e67d91b2f439974"
1821693,2019-03-31 00:53:30 UTC,"That's a Moodle issue not a Mahara one. It does not only happen with the assignment submission feedback, but also with any other feedback file on an assignment that is to be exported to the portfolio."
1821694,2019-09-20 12:33:30 UTC,"Alberto, the dependencies are missing, since some of the dependencies are only recommends, since they are not in Ubuntu main."
1821694,2019-05-14 03:37:49 UTC,Why was that dependency missing?
1821696,2019-03-26 09:43:24 UTC,Note that it was not possible to remove the encrypted volume attachment from the affected hosts - that would also yield a VolumeEncryptionNotSupported error.
1821696,2019-04-08 11:47:58 UTC,"Sure can! Not for a few days, though. I am away on a business trip."
1821696,2019-04-08 12:40:04 UTC,I proposed the above solution here: https://review.openstack.org/#/c/650853.
1821696,2019-04-08 12:43:24 UTC,Seems that the above method of making /etc/libvirt/secrets a docker volume alone means the container fails:
1821696,2019-04-08 12:48:26 UTC,"Just to get my understanding of the situation here, is there some process that is creating additional secrets under /etc/libvirt/secrets after the container has started, that are getting wiped out by the container restart?"
1821696,2019-04-08 13:12:03 UTC,"> is there some process that is creating additional secrets under /etc/libvirt/secrets after the container has started, that are getting wiped out by the container restart?
"
1821696,2019-04-08 13:31:54 UTC,"Yeah correct, since Queens with recent Libvirt and QEMU versions Nova will now store the passphrase (it's actually an asymmetric key but that's another story) as Libvirt secrets to decrypt a LUKS encrypted volume on the host. These Libvirt secrets need to persist reboots."
1821696,2019-04-29 22:03:58 UTC,"Reviewed:  https://review.opendev.org/649951
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=56ca4d32ddf944b541b8a6c46f07275e7d8472bc
Submitter: Zuul
Branch:    master"
1821696,2019-04-30 08:28:18 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/656464"
1821696,2019-05-04 15:35:37 UTC,"Reviewed:  https://review.opendev.org/656462
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c6432ac0212d15b6d8f1620b42937b2abcb66d46
Submitter: Zuul
Branch:    stable/stein"
1821696,2019-05-04 16:19:05 UTC,"Magnus, have you had a chance to test the kolla-ansible patch yet? (https://review.opendev.org/#/c/650853)"
1821696,2019-05-22 16:24:00 UTC,Magnus?
1821696,2019-06-06 06:24:21 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1821696,2019-06-11 22:50:34 UTC,"Reviewed:  https://review.opendev.org/656463
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2c6e59e835b123d6040e2a059aaa98bf9cced392
Submitter: Zuul
Branch:    stable/rocky"
1821696,2019-06-18 03:41:07 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1821696,2019-07-03 02:07:12 UTC,"Reviewed:  https://review.opendev.org/656464
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ec43a1348d871b52473b46bd895b609dc16fe8fe
Submitter: Zuul
Branch:    stable/queens"
1821696,2019-07-10 21:40:02 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1821696,2019-09-27 09:04:10 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1821696,2019-04-04 16:08:00 UTC,"^ Yeah that's an interesting use case, I think sda always wins the boot race there unless you set bootindex=0 on the initial image based volume you're booting from. Actually even then I'm not sure that we update the boot device in the XML to point to anything other than hd. Might be worth creating a separate bug for this."
1821696,2019-04-04 15:49:04 UTC,"Removing the properties from the SCSI image resolved the ""booting from hard disk"" problems."
1821696,2019-04-08 09:07:21 UTC,"Looks like there's been some good investigation on this already. We already map /etc/libvirt/qemu to a Docker volume, it looks like we need to do the same for /etc/libvirt/secrets. Are there any other subdirectories of /etc/libvirt we should persist?"
1821696,2019-04-04 14:06:39 UTC,So here is:
1821696,2019-04-02 11:00:01 UTC,The value of reraise should definitely be True when we hit VolumeEncryptionNotSupported.
1821696,2019-04-02 11:00:50 UTC,"> The value of reraise should definitely be True when we hit VolumeEncryptionNotSupported.
"
1821696,2019-04-02 11:42:18 UTC,So the fact that Nova is even creating an encryptor object in the first place is incorrect. Reviewing our _detach_encryptor code suggests that the volume secrets have gone missing in order for this to happen:
1821696,2019-04-02 14:18:13 UTC,"> Did you manually remove the associated libvirt secrets for this volume?
"
1821696,2019-04-03 08:04:19 UTC,What process did you follow to restart the services being deployed as Kolla containers?
1821696,2019-04-03 09:46:11 UTC,"> What process did you follow to restart the services being deployed as Kolla containers?
"
1821696,2019-04-04 14:16:42 UTC,and virsh dumpxml before and after Hard Reboot
1821696,2019-04-03 15:22:32 UTC,"> Also note that it is not necessary to restart any containers to reproduce the error.
> It is sufficient with a Hard Reboot from Horizon GUI.
"
1821696,2019-04-03 15:28:46 UTC,FWIW I can reproduce this artificially in devstack by manually removing the associated volume secret:
1821696,2019-04-03 10:44:35 UTC,"> What process did you follow to restart the services being deployed as Kolla containers?
"
1821696,2019-04-04 09:19:05 UTC,^ This change works around the manual out-of-band removal of Libvirt secrets in my devstack environment and allows instances to restart.
1821696,2019-04-04 09:31:03 UTC,Some more information:
1821696,2019-04-04 10:00:48 UTC,^ This is a completely different issue to the VolumeEncryptionNotSupported exception from the initial description that leaves the instance in an ERROR state.
1821696,2019-04-04 10:04:35 UTC,FWIW I don't see any changes to the disk ordering that could cause this in my devstack env:
1821696,2019-04-04 11:03:36 UTC,"When doing a shutdown of instance from Horizon, and then `docker stop` and then `docker start` on:
- nova_ssh
- nova_compute
- nova_libvirt"
1821696,2019-04-04 11:21:16 UTC,"Okay thanks so that is definitely a Kolla bug, it needs to persist /etc/libvirt/secrets/ somewhere and ensure it's injected back into the container on restart."
1821696,2019-04-04 13:17:59 UTC,verified that the patch works :clap: by
1821696,2019-04-04 13:36:46 UTC,^ I'd be interested in seeing the ordering of the devices in the domain XML and any n-cpu log snippets showing the instance booting if you are able to share.
1821696,2019-04-04 09:17:26 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649951"
1821697,2019-03-27 08:59:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648040"
1821697,2019-06-19 13:53:17 UTC,"Reviewed:  https://review.opendev.org/648040
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=3809df73fb10434b83e2eb789cd2a7dcc1271506
Submitter: Zuul
Branch:    master"
1821700,2019-03-26 08:39:37 UTC,"StacktraceTop:
 startwrite (ft=0x7ffe1a2573c0) at ao.c:38
 try_device (name=0x557b3474c7dc ""ao"") at sox.c:2547
 set_default_device (f=<optimized out>) at sox.c:2569
 parse_options_and_filenames (argc=11, argv=0x7ffe1a257cc8) at sox.c:2662
 main (argc=11, argv=0x7ffe1a257cc8) at sox.c:2885"
1821702,2019-03-26 09:42:04 UTC,"I just tested again. Weirdly, the output of rabbitmqctl list_queues stays the same in both cases."
1821703,2019-03-26 09:05:37 UTC,Ich bin bis 08.04. nicht im Haus und kann Ihre Nachricht daher leider nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
1821706,2019-09-16 15:02:23 UTC,https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=1de2e1c8115a7b3a7ab2fd89115b1a23ad772a8d
1821709,2019-03-29 04:12:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821709,2019-03-26 17:23:09 UTC,"Something has changed in grub behaviour between 18.10 and 19.04, at least on a Dell XPS 15 laptop."
1821709,2019-03-26 10:35:11 UTC,fyi - usb legacy mode is enabled in bios (Dell XPS 15 bios v1.8.1) and I'm booting in non-secure mode.
1821709,2019-03-26 10:45:15 UTC,"I can get the usb keyboard working if I force GRUB_PRELOAD_MODULES=""usb usb_keyboard ehci ohci uhci"" but then it is unable to find my nvme disk."
1821714,2019-03-26 11:32:49 UTC,Can you describe the situation with the manual machine. The code expects that if MAAS is the provider that the host machine is aware/using the MAAS dns and so the manual machine process messes up that logic. As a work around you'll have to have the manually added machine to the model have the DNS you are looking for.
1821714,2019-04-01 11:06:03 UTC,"Just to confirm, the manually provisioned machine indeed doesn't/didn't have the maas-dns set up, it's actually the bootstrap machine hosting maas-dns itself. Pointing the bootstrap machine to maas-dns works fine."
1821729,2019-03-26 14:09:06 UTC,Please provide the console log and libvirt xml for a failing VM.
1821729,2020-02-05 15:44:13 UTC,"Hey Dann, thanks a lot for the thorough analysis, the reasoning makes sense.
I'm just a bit sceptical because we use tinycore 9.x at the moment, with kernel 4.14, which includes the patch for the kernel panic you mentioned, it was just moved under drivers/firmware/efi/efi-bgrt.c, so I'm not sure that could be the explanation for the error.
We're in the process of upgrading tinycore to 10.x which will bring in kernel 4.19, although I don't see any substantial changes in he efi-bgrt management.
I wonder if there was a regression at some point, but it's unlikely.
I'll let you know how it goes with tinycore 10.x, in the meantime if you have any other ideas or advice, please let me know.
Thanks!"
1821729,2020-02-04 01:26:37 UTC,"I think I've figured out how to simulate the OVMF PXE -> iPXE chaining you are doing, which had me confused in Comment #14. I also see the problem being introduced between the versions you identified, and was able to bisect it down to the following commit:"
1821729,2020-01-28 13:13:01 UTC,"Hi, just wondering if we can provide any more info or help to be able to move forward with the investigation.
Thanks."
1821729,2019-11-26 21:29:00 UTC,"Setting back to ""new"" since the requested information was provided."
1821729,2019-11-21 17:01:23 UTC,"Hi Dann,"
1821729,2019-11-20 14:39:08 UTC,"Hi Dann,"
1821729,2019-07-20 04:17:29 UTC,[Expired for edk2 (Ubuntu Cosmic) because there has been no activity for 60 days.]
1821729,2019-07-20 04:17:28 UTC,[Expired for edk2 (Ubuntu) because there has been no activity for 60 days.]
1821729,2019-07-20 04:17:26 UTC,[Expired for edk2 (Ubuntu Bionic) because there has been no activity for 60 days.]
1821729,2019-05-20 19:57:29 UTC,"On Mon, May 20, 2019 at 2:15 AM Riccardo Pittau
<email address hidden> wrote:

>
> Hi Dann,
>
> Please find recent logs here:
>
> This is the correct output on bionic using virtio + ovmf package from xenial:
> http://logs.openstack.org/90/644590/8/gate/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/6232932/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-12:09:41_log.txt.gz
>
> Job on bionic using virtio + new package from your repo:
> http://logs.openstack.org/07/645507/10/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/d9a0a64/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-10:13:23_log.txt.gz
>
> Job on bionic using e1000 + new package from your repo:
> http://logs.openstack.org/38/648938/5/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/90c5126/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-10:08:08_log.txt.gz
"
1821729,2019-05-20 18:29:31 UTC,"Thanks Riccardo. I'm still unable to reproduce, but I'm not sure I'm doing the right thing. Can you elaborate on how iPXE is getting loaded in the ""good"" case? i.e. are you loading it from disk, or chainloading to it from OVMF's built-in PXE client? In your ""bad"" logs, it looks like you are booting using OVMF's built-in PXE, and that is just hanging. But in your ""good"" logs, I see no evidence of the OVMF PXE running (""Start PXE over IPv4."") iPXE just seems to start directly."
1821729,2020-01-30 01:04:26 UTC,"Hi Riccardo,"
1821729,2019-05-17 23:06:45 UTC,"@Riccardo: I found some time to try and reproduce the ipxe issue again today but, unfortunately, I don't remember what the failure looked like and the logs in comment #6 are no longer accessible. Would you be able to attach some logs here?"
1821729,2019-05-20 08:04:54 UTC,"Hi Dann,"
1821729,2019-03-27 09:31:18 UTC,console log attached
1821729,2019-03-27 09:31:52 UTC,libvirt xml of virtual node attached
1821729,2019-03-27 22:55:38 UTC,"Bisection led me to the following fix:
 https://github.com/tianocore/edk2/commit/272658b9971865812f70e494d0198f13df8b841b"
1821729,2019-04-01 14:01:50 UTC,"@Dann: thanks for checking that, I did some tests and, even if I can't reproduce the kernel panic anymore, I'm seeing another issue that was also happening before with virtio, the vm is not booting on ipxe."
1821729,2019-03-27 17:28:25 UTC,"@Riccardo: Thanks, I can reproduce by using machine='pc-1.0' in my XML (pc-i440fx-2.12 worked fine). I also found that the version of ovmf in disco works w/ pc-1.0, so I'll try to bisect down what fixed it."
1821729,2019-04-01 15:45:24 UTC,@Dann: what I'm saying is that I can't reproduce the kernel panic after installing a PPA build because it doesn't load from ipxe anymore.
1821729,2019-04-01 15:58:18 UTC,"On Mon, Apr 1, 2019 at 9:50 AM Riccardo Pittau
<email address hidden> wrote:

>
> @Dann: what I'm saying is that I can't reproduce the kernel panic after
> installing a PPA build because it doesn't load from ipxe anymore.
>
> I can't confirm or deny the issue with the kernel panic is actually
> fixed.
>
> If you prefer I can open another bug, although it seems a regression to
> me, but of course a different issue.
"
1821729,2019-04-04 22:37:38 UTC,"@Riccardo: The PPA builds I provided had both a fix for this issue and some security issues, some related to networking code. To help determine if it is the security fixes or the fix for this bug causing your iPXE regression, I've uploaded new packages *without* the security fix. Could you test those? They are in the same PPA."
1821729,2019-04-11 08:30:24 UTC,"@Dann: thanks for keep looking at this, I tested the new package both locally and in our CI, using virtio and e1000 drivers, but unfortunately I'm still seeing the issue where the vm can't load from ipxe.
The only thing that we change for the test is the ovmf package, the rest of the configuration is exactly the same.
I'm quite puzzled at this point seeing that you were actually able to correctly load from ipxe, in my case it seems the vm hangs before getting an ip during the pxeboot phase."
1821729,2019-04-01 14:22:56 UTC,"@Riccardo: Sorry, I'm not sure how to read your update. Are you stating that you are unable to reproduce the panic *after installing a PPA build*, or for some other reason?"
1821730,2019-03-28 13:24:46 UTC,"As I said, the problem seems to be related to how keys are assigned to the Mod1-5 flags. I have a slightly tweaked mapping, and apparently KiCad or wxWidgets doesn't like that. As I also said, I was able to shuffle the assignments in such a way that everything is working since all other applications correctly examine the mapping to determine which mod flag has what meaning."
1821730,2019-03-26 14:13:46 UTC,"You really mean *Num* lock ? Not *Caps* lock ? Either way, I can't reproduce on Windows 32-bit."
1821730,2019-03-26 16:55:34 UTC,"Yes, Num lock, the key at the top left of the number pad."
1821730,2019-03-28 00:02:48 UTC,I'm not seeing any issues with the normal shortcut keys such as 'A' on Debian testing so I'm wondering if there are some key mapping issues.  Are you using a non-US keyboard?  We have seen some issues with non-US keyboards.
1821730,2019-05-28 04:17:52 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821732,2019-09-02 12:34:57 UTC,installing alltray is a workaround...
1821733,2019-03-26 17:22:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/647831"
1821733,2019-04-01 15:21:21 UTC,"Reviewed:  https://review.openstack.org/647831
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=50a0c6a4b98a3ef1d893b0bb204a4a4868017cbb
Submitter: Zuul
Branch:    stable/queens"
1821733,2019-07-10 21:40:26 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1821736,2019-03-26 12:59:27 UTC,Can you attach the debug file?
1821736,2019-03-26 13:24:25 UTC,"This sounds a pure python bug.
Not sure what we can do to fix that."
1821736,2019-03-26 13:29:09 UTC,"I can run any shell script to produce data on my computer's internal disk or either a Mac OS formatted disk, but when i want to use an ExFAT disk and trying to write outputs in to the disk i got this error. Also i got all read&write permissions. Interesting."
1821736,2019-03-26 20:42:05 UTC,"Hi,"
1821738,2019-04-26 19:01:34 UTC,Is there an upstream commit to fix the issue?
1821738,2019-03-26 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821755,2019-03-27 13:35:43 UTC,"This is a long-standing known issue I believe, same for server build and evacuate (evacuate was fixed later in Rocky I think). There is a late affinity check in the compute service to check for the race in the scheduler and then reschedule for server create to another host, or fail in the case of evacuate. There is no such late affinity check for other move operations like live migration, cold migration (resize) or unshelve."
1821755,2019-03-27 15:10:39 UTC,Just to add a comment...I can confirm the external lock would not be sufficient if you have nova-conductor services running on multiple physical hosts.
1821755,2019-04-02 09:59:56 UTC,Hi Matt
1821755,2019-04-08 15:51:19 UTC,"I agree that option #1 (late affinity check in compute - probably during ComputeManager.pre_live_migration) is the easiest way to go, but could still potentially be racy although it should (for the most part anyway) solve a scheduling race where concurrent live migration requests are made and there are multiple schedulers running which pick the same host for servers in an anti-affinity group."
1821755,2019-04-12 05:24:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651969"
1821755,2019-05-10 03:44:43 UTC,"Well also if you do live migration to host where an instance of same anti-affinity group member was live_migrated away within ~70sec, it will fail as anti-affinity filter still thinks there is an instance of the same group present. I have had a manual fix in the code for a couple of years to have updated information in AntiAffinity filter code straight from DB. What seems to work also is SIGHUP to nova-scheduler. So some parallel migration checking might not be enough if the information used is not up-to-date."
1821757,2019-03-26 14:30:06 UTC,This change was made by a bot.
1821758,2019-05-27 14:11:05 UTC,"I'm pretty sure they are.  I just fixed an Eagle bug that was caused by FP divide by 0.  So at least linux x86 builds have them enabled by default.  This might be changed by packagers, of course."
1821758,2019-05-27 04:17:33 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1821758,2019-05-27 08:17:57 UTC,"Hm, I'd rather not ignore this."
1821758,2019-03-27 14:49:02 UTC,I don't know anyone with a PPC machine that can help us out debugging this.  The best we could do is provide a patch to ensure a divide by zero cannot happen and have someone with a ppc machine test it for us.
1821758,2019-03-27 19:27:33 UTC,"I have a 64 bit POWER machine, although it's not currently set up."
1821760,2019-04-17 14:45:48 UTC,This bug was fixed in the package znc - 1.7.1-2ubuntu0.1
1821763,2019-03-27 02:16:41 UTC,"Thanks for the bug report. Next time the problem happens, please:"
1821763,2019-03-27 20:10:18 UTC,"Hi Daniel, thanks for the reply! I am attaching the prevboot.txt file."
1821763,2019-03-28 02:05:40 UTC,"Yes, please do uninstall all extensions and retest."
1821763,2019-03-29 14:28:39 UTC,"I tried uninstalling the extensions and reinstalling gnome-shell, but it froze again today."
1821763,2019-04-01 02:40:46 UTC,"TabNine is probably not the cause. But your machine did run out of memory, which is at least now the main problem here..."
1821763,2019-05-31 04:17:22 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1821765,2020-02-19 17:11:38 UTC,"Not at the moment, I'm working on higher priority bugs and features."
1821765,2020-02-19 16:36:01 UTC,@osomon Are there any ETA/plan to try to fix this again?
1821765,2019-08-01 11:07:08 UTC,The fix introduced a nasty regression (bug #1838508) and had to be reverted.
1821765,2019-07-12 14:48:54 UTC,And I've confirmed on my end that the fix works too. Installing the Google Hangouts extension enables the appindicator icon.
1821765,2019-07-12 14:38:08 UTC,"I've confirmed the fix works, thanks!"
1821765,2019-07-10 15:59:58 UTC,Tentative fix: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=d5604a3dfd6f1f85c93a733219105ad14267128e.
1821765,2019-06-25 18:19:52 UTC,"Olivier,"
1821765,2019-07-10 11:42:29 UTC,Thanks Chris for those details.
1821765,2019-06-26 14:26:28 UTC,Is there an env variable we can set to change the location of tmp?  I think in generally it shouldn't be attempting to use /tmp for anything.
1821765,2019-06-19 16:04:52 UTC,"Chris, thanks for the confirmation. I haven't been able to observe the issue myself, can you share details on what shows that appindicator when using the chromium deb?"
1821765,2019-06-19 15:27:44 UTC,"Same issue, with additional icon for Google Hangouts as well."
1821765,2019-06-19 15:26:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821765,2019-07-10 15:55:17 UTC,It looks like setting TMPDIR to $XDG_RUNTIME_DIR in snapcraft.yaml's environment section for the app should do the trick (thanks Trevinho for the hint!).
1821766,2020-06-01 08:33:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821766,2020-06-05 03:18:40 UTC,"Hi,"
1821767,2019-05-15 14:43:39 UTC,Fix:   https://review.opendev.org/#/c/655803/
1821767,2019-05-15 13:42:46 UTC,TRIAGE: this might be a nova packaging bug rather than a charm bug as the apparmor profiles potentially need changing.
1821767,2019-05-15 14:32:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821767,2019-03-26 15:38:26 UTC,"After setting workaround, entire capture of dmesg from complain mode around volume attachment was:"
1821767,2019-03-26 15:43:35 UTC,Here are the detach app armor traces:
1821769,2019-03-26 15:54:48 UTC,"I wonder if we could do this by inventing a new bug sharing policy that's even more public than Public: that is, even Private Security is forbidden."
1821770,2019-11-20 04:17:54 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1821770,2019-09-20 13:20:22 UTC,Can you please try 2.6.0 and see if this bug still exists there?
1821770,2019-05-06 09:05:12 UTC,"@Andres: although the <iface_name>.<vlan_id> is a widespread convention that appears to be honored by ifenslave/ifupdown (which is why 'iface bond1.4001 inet manual' is a valid declaration of a tagged bond in /e/n/i), I'm pretty sure interface names are indeed just names. There's nothing that prevents one from doing the following:"
1821770,2019-04-12 08:23:21 UTC,"Here are the errors I saw - https://paste.ubuntu.com/p/WMBwTWjbp2/, it looks br-bond0.2734 has been identified as the type bridge by MAAS so it should have nothing to do with the <dot> in the interface name."
1821770,2019-04-10 07:51:39 UTC,"Hi Andres,"
1821770,2019-04-09 16:46:07 UTC,"@Andrea,"
1821770,2019-04-04 14:40:29 UTC,"Hi Andrea,"
1821770,2019-04-10 09:22:30 UTC,"another bug with the same error ""'NoneType' object has no attribute 'fabric'"" - https://bugs.launchpad.net/maas/+bug/1724252"
1821770,2019-04-03 14:55:19 UTC,"FWIW, i think doing bond1.4001 -> brext.4001 may even be incorrect config that may yield unexpected results!"
1821770,2019-04-03 14:51:52 UTC,"Looking at the networking configuration, I see the following:"
1821770,2019-04-03 08:22:08 UTC,"Hello Andres,"
1821770,2019-04-02 14:05:14 UTC,"Thank you for the bug report, unforunately, the data provided is not enough to triage the issue. COuld you please attach the following information:"
1821770,2019-03-27 12:48:59 UTC,"Hello Hua, yes, I've just filed LP#1821899 because these warnings are just one aspect of some other underlying issue. Basically, having an extra interface on one of the rack controllers is producing these warnings and errors. The two bugs may be merged if you think that's better for tracking."
1821770,2019-03-27 08:44:52 UTC,"@Andrea, do you have the detailed steps to reproduce the problem ?"
1821770,2019-03-27 08:41:35 UTC,"One client had similar problems, we saw lots of 'Address already in use' errors, but seems this kind of error is caused by 'parent_nic.vlan.fabric'=None in line 4528 of /usr/lib/python3/dist-packages/maasserver/models/node.py"
1821770,2019-04-04 11:12:21 UTC,"Hi Andres, thanks for looking into this.
AFAIK there's no way to tag a bridge, brext.4001 is just a name (just like bond1.4001). See the details of those interfaces:"
1821771,2020-08-03 12:24:56 UTC,"Documentation describing the current qemu behaviour is captured here, https://<email address hidden>/msg726442.html"
1821773,2019-03-27 11:14:40 UTC,"If I install the osmclient manually, instead of using the snap, it works. Should I install osmclient manually instead of using the snap until the snap is fixed?"
1821773,2019-03-27 14:12:19 UTC,"It looks like this is in the snap and not related to shared storage. I'll take over this, as part of my work on the osmclient snap."
1821773,2019-08-06 16:56:51 UTC,Refactored snap of osmclient now uses strict confinement. The snap has been uploaded to the edge channel for testing.
1821775,2019-09-02 09:01:40 UTC,This bug was fixed in the package samba - 2:4.10.0+dfsg-0ubuntu2.3
1821775,2019-08-30 18:52:34 UTC,Marking verification-done according to:
1821775,2019-08-30 06:52:26 UTC,FYI - this test fail was resolved by a retry as gvfs is somewhat flaky
1821775,2019-08-29 13:02:49 UTC,"All autopkgtests for the newly accepted samba (2:4.10.0+dfsg-0ubuntu2.3) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1821775,2019-09-02 09:01:56 UTC,"The verification of the Stable Release Update for samba has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821775,2019-08-13 16:45:44 UTC,"Hello Robert, or anyone else affected,"
1821775,2019-06-07 16:02:11 UTC,"The fix (Eoan) and SRU (Disco, Cosmic and Bionic) for this bug is being done at:"
1821775,2019-06-03 15:20:14 UTC,https://bugzilla.samba.org/show_bug.cgi?id=13984
1821775,2019-06-03 14:18:46 UTC,https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929931
1821775,2019-05-31 13:39:52 UTC,Doing the CTDB setup I faced the same issues as:
1821775,2019-04-01 01:15:11 UTC,"Changed /etc/init.d/ctdb
pidfile=""/var/run/ctdb/ctdbd.pid""  to pidfile=""/run/ctdb/ctdbd.pid"""
1821775,2019-04-01 00:16:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821775,2019-07-06 12:22:49 UTC,This bug was fixed in the package samba - 2:4.10.0+dfsg-0ubuntu5
1821776,2019-08-03 03:18:57 UTC,This got fixed some time ago.
1821776,2019-03-28 14:57:06 UTC,"@Jeff,
Copper layer names are also used to create plot filenames, so allowing chars not accepted in filenames is not a good idea."
1821776,2019-03-27 21:52:00 UTC,"Sounds like general consensus for 2.  I like Jeff's suggestion as well.  Barring objections, I'll target this for some time after v6 merge window opens.  Note that we should bump the file version number for this as well."
1821776,2019-03-28 22:53:23 UTC,"Ah well, all good ideas run into reality at some point. ;)"
1821776,2019-03-27 19:14:00 UTC,"I prefer #2.  Given that they are used as strings internally, I see no reason not to do this.  I wish I would have quoted all tokens used as strings when I wrote the original file format.  It would be obvious that the token is used as a string and it would be more flexible in terms of usable characters."
1821776,2019-03-27 06:54:24 UTC,"3) breaks the compatibility with previous kicad versions (non copper layer names are keywords), without benefit."
1821776,2019-03-26 18:15:50 UTC,I'd vote for (2) along with removing the restrictions on layer name characters.
1821776,2019-03-27 21:24:25 UTC,"@JP, spaces, slashes and colons mainly, although I suppose someone out there will no doubt want to use a vertical bar or angle bracket in a layer name."
1821777,2019-09-06 08:21:19 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/297
1821787,2020-08-31 06:03:35 UTC,"This should now be possible, as the bundle checking logic will happily process all models (including the controller) model on a cloud. I'd be happy to see an MR for specific rules that took advantage of this, but also think that the broader applicability of this pattern needs to be examined, especially with some related items for representing the Juju controller as an application being on the Juju roadmap, this specific implementation may need to change to accommodate."
1821788,2019-09-20 13:18:16 UTC,This area is under development / cleanup / design extensions by Ian from the snapd team. I will relay this bug to my colleague.
1821788,2019-09-20 13:24:11 UTC,"This is not a bug exactly because what happens is that the service fails to start, and thus the install is aborted."
1821790,2019-03-26 18:23:05 UTC,"Seems the issue is that ~tripleo-admin/.ssh/authorized_keys gets created with the container_t context and then ssh to localhost then fails:
[root@undercloud-0 ~]# ls -laZR /home/tripleo-admin/.ssh/
/home/tripleo-admin/.ssh/:
total 12
drwx------. 2 tripleo-admin tripleo-admin unconfined_u:object_r:ssh_home_t:s0              61 Mar 26 18:02 .
drwx------. 3 tripleo-admin tripleo-admin unconfined_u:object_r:user_home_dir_t:s0         74 Mar 26 17:12 ..
-rw-------. 1 tripleo-admin tripleo-admin system_u:object_r:container_file_t:s0:c85,c195  830 Mar 26 18:02 authorized_keys
-rw-------. 1 tripleo-admin tripleo-admin unconfined_u:object_r:ssh_home_t:s0            1864 Mar 26 17:12 id_rsa
-rw-r--r--. 1 tripleo-admin tripleo-admin unconfined_u:object_r:ssh_home_t:s0             428 Mar 26 17:12 id_rsa.pub"
1821790,2019-03-26 18:44:27 UTC,"So the problem is that we create the user via a host_prep_task in deployment/mistral/mistral-executor-container-puppet.yaml (see previous comment: happened at around 17:12), but then a container starts and fiddles with authorized_keys (see later timestamp at 18:02) and that changes the selinux context and messes things up for us."
1821790,2019-03-26 19:33:15 UTC,Likely https://review.openstack.org/#/c/638323/ will avoid this completely?
1821790,2019-03-27 12:08:08 UTC,Indeed https://review.openstack.org/#/c/638323/ fixes it for me
1821792,2019-03-27 19:23:01 UTC,This bug was fixed in the package nvidia-cuda-toolkit - 10.1.105-0ubuntu1
1821792,2019-03-26 20:16:45 UTC,Sounds like a good idea.
1821793,2019-04-05 20:28:28 UTC,You are correct.  For dailies we have a bug due to image publication parallelization where the VHD is not included in the signed checksums.  The release VHD images (like https://cloud-images.ubuntu.com/releases/xenial/release/) do include the VHD in signed checksums.  We are working on a fix for this but do not have an ETA.
1821793,2019-03-26 18:44:14 UTC,update:  i see the same type of checksum-related bug for Ubuntu Disco Dingo: the Hyper-V VHD images are newer than the checksums and are not listed inside the signed checksums themselves:
1821795,2019-03-27 10:16:50 UTC,"this looks pretty much like a network error on your pi, can you ping git.denx.de ? are you perhaps behind some proxy ?"
1821795,2019-03-28 21:07:47 UTC,Yes I can ping git.denx.de and I am not behind any proxy.
1821797,2019-03-26 18:59:56 UTC,Output of nova-api.log
1821797,2019-05-09 08:46:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821799,2019-04-08 11:21:23 UTC,"chown root:wireshark /usr/bin/dumpcap fails and the group seem to be present.
Could you please try this command manually and check why it does not work?"
1821799,2019-06-08 04:17:39 UTC,[Expired for wireshark (Ubuntu) because there has been no activity for 60 days.]
1821800,2019-05-04 20:39:29 UTC,"We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to 'New'. Thanks again!"
1821800,2019-05-04 20:48:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:"
1821800,2019-07-04 04:17:24 UTC,[Expired for masakari-monitors (Ubuntu) because there has been no activity for 60 days.]
1821800,2019-07-04 04:17:25 UTC,[Expired for placement (Ubuntu) because there has been no activity for 60 days.]
1821801,2019-03-27 13:46:20 UTC,"@Andrew, did you check to see if this bug hasn't already be proposed.  I thought it was but I could be wrong.  In any event, pad stacks are on the v6 road map which should cover what you proposed."
1821804,2020-12-18 17:57:46 UTC,This is still a problem in 3.6.1.
1821804,2019-04-09 22:34:42 UTC,We're seeing this in 3.1.7
1821804,2019-12-23 16:33:27 UTC,This is still a problem in 3.4.
1821807,2019-03-26 21:04:07 UTC,"Hi Markus, thanks for taking the time to file a bug. This doesn't appear to be a bug against the Ubuntu man page repository, but instead possibly against the run-one command. I've added that task to this bug and marked the manpage repo invalid."
1821807,2019-03-26 21:43:15 UTC,"Thank you, Joshua. Yes, I do mean the ""run-one"" command, not the manpage. Maybe it is not even a ""bug"", but I sadly faced that problem."
1821807,2019-04-08 10:38:03 UTC,It does not clean the locks at all (it explicitly re-uses old lock DIRs)
1821810,2019-04-22 19:48:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821810,2019-10-16 20:46:18 UTC,"I'm a Xubuntu flavour user and I've never seen Gdebi work (17.10-19.04). It just closes immediately after I press ""Install"" button. If I run Gdebi with root privilege through terminal (sudo -i gdebi) then it works."
1821810,2020-02-14 18:48:49 UTC,"Hello
what is the status of this bug,
I just have installed an ubuntu version (elementaryOS) and I have this bug"
1821813,2019-03-26 22:01:44 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9667"
1821813,2019-11-24 01:03:33 UTC,"Reviewed:  https://reviews.mahara.org/9667
Committed: https://git.mahara.org/mahara/mahara/commit/41969dd00a8f92feebf12e1abe9b0927af1ca3fe
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1821814,2019-12-30 01:57:04 UTC,"This is totally non-functional for those who don't run a GNOME 3 desktop, but have GNOME apps installed, such as gnome-todo + the todoist extension."
1821814,2019-06-06 09:17:48 UTC,"Ok, thanks for that info, that was useful to track is down to
https://gitlab.gnome.org/GNOME/gnome-online-accounts/commit/bf77325d"
1821814,2019-06-05 17:56:28 UTC,"When it's working, there's a Todoist option in the Online Accounts section of GNOME Settings, however on 19.04 that option is missing."
1821814,2019-06-03 14:30:11 UTC,"Thank you for your bug report, from the bug log it seems to be built. Where do you see that option when it's working?"
1821814,2019-05-28 08:57:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821818,2019-03-27 14:58:18 UTC,"Reproduces with:
1. set default_volume_type=None in cinder.conf
2. $ cinder create 1
3. $ cinder upload-to-image 69d43415-76e9-4a58-8c84-5f04ee633344 myimg
ERROR: 'NoneType' object has no attribute '__getitem__'"
1821818,2019-03-27 15:21:11 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648157"
1821818,2019-05-23 07:08:59 UTC,"Reviewed:  https://review.opendev.org/648157
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=274fa111696783e846561d12f670967ed01ebcbc
Submitter: Zuul
Branch:    master"
1821818,2019-06-03 14:54:30 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/662782"
1821818,2019-06-12 18:21:50 UTC,"Reviewed:  https://review.opendev.org/662782
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=0a2bab1d4d01df99bc9594f3f055ad99584949aa
Submitter: Zuul
Branch:    stable/stein"
1821818,2019-07-11 09:20:28 UTC,This issue was fixed in the openstack/python-cinderclient 4.2.1 release.
1821818,2019-08-22 23:26:21 UTC,This issue was fixed in the openstack/python-cinderclient 4.3.0 release.
1821819,2020-05-07 04:17:27 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1821819,2020-03-07 17:18:39 UTC,"Yes, so maybe you are correct."
1821819,2020-03-07 10:50:55 UTC,"If the live trial starts up, then the media must be ok?  If if I can't install from love trial, then the error must be in the live trial software stack?"
1821819,2020-03-07 10:14:35 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1821819,2020-03-07 11:05:56 UTC,"Hi Godfrey, may be just a small section of the written image was corrupt and that only became apparent when you attempted to install? Did you successfully install from that image?"
1821824,2019-04-15 11:07:00 UTC,"Reviewed:  https://review.openstack.org/649600
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c97466456f9a8525074ef78def44ecb491bfb793
Submitter: Zuul
Branch:    stable/stein"
1821824,2019-09-27 09:05:14 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1821824,2019-06-18 03:41:33 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1821824,2019-06-06 06:24:38 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1821824,2019-04-15 23:48:31 UTC,"Reviewed:  https://review.openstack.org/649602
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a40bce7f80fc002b1a4d774b1f9394adb747016e
Submitter: Zuul
Branch:    stable/rocky"
1821824,2019-04-15 11:29:42 UTC,"Reviewed:  https://review.openstack.org/649601
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6a5be4ae250b9ff1b8e48947ab80a65827460513
Submitter: Zuul
Branch:    stable/stein"
1821824,2019-04-03 12:58:07 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649603"
1821824,2019-04-15 23:48:42 UTC,"Reviewed:  https://review.openstack.org/649603
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6f07f769020bdbe5328b3991fc5e9bc89815a970
Submitter: Zuul
Branch:    stable/rocky"
1821824,2019-04-03 12:56:29 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/649601"
1821824,2019-04-03 12:56:12 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/649600"
1821824,2019-04-03 00:16:59 UTC,"Reviewed:  https://review.openstack.org/648653
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c088856c8c08f0ab0746db7c120da494c9dd42d4
Submitter: Zuul
Branch:    master"
1821824,2019-04-03 12:57:47 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649602"
1821824,2019-04-02 16:24:28 UTC,"Reviewed:  https://review.openstack.org/647957
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=13e661792d73c27bcc7616b6bf612b5784e994e3
Submitter: Zuul
Branch:    master"
1821824,2019-03-29 09:29:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648653"
1821824,2019-03-27 00:59:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/647957"
1821829,2020-08-22 11:46:17 UTC,"This issue cannot be reproduced and anyway applies for a version no longer maintained, so closing issue."
1821832,2019-03-27 04:30:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821834,2019-03-27 07:41:13 UTC,"PATH comes from your environment, though, not from the snapd package. Do you have ""."" in your PATH?"
1821834,2019-05-27 04:17:16 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1821836,2019-06-10 06:31:31 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/664199"
1821836,2019-09-26 17:19:38 UTC,"Change abandoned by Vishal Manchanda (<email address hidden>) on branch: master
Review: https://review.opendev.org/664199"
1821837,2020-08-17 16:47:41 UTC,"Reviewed:  https://review.opendev.org/745261
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=c650b63d33d6aaa2496b40e583e3aab9e3a92d31
Submitter: Zuul
Branch:    master"
1821837,2020-08-07 00:27:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/745261"
1821839,2019-04-03 21:07:54 UTC,"I didnt understand properly the output, it only can use opengl es 3.0. you should put that info because when i compile qemu it pass and it should if doesnt support my opengl setup."
1821839,2019-04-03 21:09:05 UTC,it shouldn't+
1821842,2019-03-27 03:58:45 UTC,The file /usr/share/scilab//modules/preferences/src/xslt/XConfiguration.xsl is there and belongs to scilab-data:
1821842,2019-06-23 09:28:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821843,2019-03-27 04:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821843,2019-03-27 05:04:03 UTC,Setting to confirmed because the existence of the anomalous behavior is uncontroversial (it is already documented in another package's bug).
1821843,2019-04-05 09:01:54 UTC,"I was affected by this bug. Thanks for posting it so I could find it. I installed the hwe kernel packages (4.15 kernel) for ubuntu 16.04, removed the old 4.4 kernels, then Parallels tools installed just fine."
1821845,2019-03-27 04:35:23 UTC,"Downgrading to f2c version 20100827-2 from 16.04 does not help.
Also to mention that the test program exits cleanly with exit code 0."
1821845,2019-09-16 00:59:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821849,2019-04-04 23:20:28 UTC,"Hi Olivier,"
1821849,2019-04-11 10:31:20 UTC,"It is now one week since you realized that the bug is with Kubuntu 19.04 and NOT with Ubuntu 19.04.  I assume that by now you have a VM with Kubuntu 19.04 and tested the impact of an embedded video. Since I have not heard from you, I expect that you have found the bug that caused me to start this report."
1821849,2019-04-05 10:24:25 UTC,"That is indeed interesting that Ubuntu 19.04 does not have this
problem.  I have just install the latest build of Kubuntu 19.04 into
another partition of my HP Spectre x360 15-ch004ng which has a 1TB SSD.
I tested the video after all the latest LibreOffice updates and it still
gave the same problems that I reported. Basically, when a video is
started the display goes full screen and is a mess."
1821849,2019-04-05 09:08:24 UTC,In comment #4 I stated that I am testing on disco.
1821849,2019-04-04 07:16:01 UTC,"Thanks for testing and the feedback Sam.
I haven't been able to reproduce the problems you're seeing locally.
Please file a bug report upstream, this might be a known issue, and if not upstream developers should be able to help us nail it down."
1821849,2019-12-15 06:03:51 UTC,This problem has been fixed for some time now and I no longer get a white screen at the start of a video. I currently have LibreOffice 6.4.3.2 and it works GREAT.  Thanks for all the improvements that have been made.
1821849,2019-04-03 08:36:01 UTC,Thanks for testing this Sam. Is this behaviour observable with all presentations that contain a video clip? (ideally you would test creating a new one)
1821849,2019-04-03 05:55:01 UTC,"Hi Olivier,"
1821849,2019-04-02 20:24:28 UTC,"I cannot reproduce this issue in an up-to-date disco VM, with libreoffice 6.2.2-0ubuntu1."
1821849,2019-03-30 20:14:42 UTC,"Disco's release is the 18 April and the next version, 6.2.3, of LibreOffice is 15-21 April."
1821849,2019-03-28 02:21:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821849,2019-04-04 04:21:37 UTC,"Hi Olivier,"
1821851,2019-03-27 06:52:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648013"
1821851,2019-08-08 07:14:07 UTC,"Reviewed:  https://review.opendev.org/648013
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=6dc4bd203d3e44ce6500a4b81a27158d6c73185c
Submitter: Zuul
Branch:    master"
1821851,2019-09-13 16:42:05 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.
1821854,2019-03-29 22:14:45 UTC,"Reviewed:  https://review.openstack.org/648674
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=8ec33d15a576f145e21189a77310be82a1080cbc
Submitter: Zuul
Branch:    master"
1821854,2019-03-28 09:29:58 UTC,"I believe these zombie processes are left by ansible, not tripleo. Since we are running in a container without init they are not reaped for us automatically."
1821854,2019-03-28 09:13:31 UTC,There are two code paths one uses oslo_concurrency.execute and another use subprocess.Popen and it depends on if the queue_mamed was passed to the action. To better understand where the issue I'd like to know which one should I deep dive into.
1821854,2019-03-28 09:08:09 UTC,"This isn't a Mistral bug. Mistral just runs the Ansible action that is in tripleo-common. AFAIK, Mistral has no good way to know that we are shelling out to ansible."
1821854,2019-03-27 10:45:35 UTC,mistral-server should be doing a better job on ripping those ssh processes started by ansible invoked via workflows
1821854,2019-03-27 10:43:53 UTC,Looks like a regression after https://bugs.launchpad.net/tripleo/+bug/1813832
1821855,2019-03-27 08:29:39 UTC,See LP: #1821678
1821855,2019-03-27 09:08:28 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1821863,2019-07-03 13:42:40 UTC,This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.1
1821863,2019-07-03 13:32:22 UTC,This bug was fixed in the package libdrm - 2.4.97-1ubuntu1~18.04.1
1821863,2019-06-24 23:58:48 UTC,This bug was fixed in the package xorg-server - 2:1.19.6-1ubuntu4.3
1821863,2019-06-24 23:48:45 UTC,"The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821863,2019-06-03 10:33:47 UTC,"@Timo, tried to upgrade to xorg-server into bionic-proposed and confirmed it fixes a laggy desktop issue found in some OEM CML platforms running on bionic image."
1821863,2019-06-03 08:08:48 UTC,"Hello Chih-Hsyuan, or anyone else affected,"
1821863,2019-04-24 08:01:51 UTC,This bug was fixed in the package linux-oem - 4.15.0-1036.41
1821863,2019-04-15 03:29:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1821863,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1821863,2019-04-04 10:07:22 UTC,This bug was fixed in the package xorg-server - 2:1.20.4-1ubuntu3
1821863,2019-04-04 07:30:59 UTC,This bug was fixed in the package mesa - 19.0.1-1ubuntu2
1821863,2019-03-29 17:15:57 UTC,This bug was fixed in the package libdrm - 2.4.97-1ubuntu1
1821863,2019-03-29 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821863,2019-03-29 09:01:05 UTC,"leaving cosmic out, this will only be needed in disco and bionic."
1821864,2019-05-15 14:05:27 UTC,This is fix-released as this issue was fixed in: https://review.opendev.org/#/c/655470/
1821865,2019-05-15 14:15:54 UTC,"On cosmic, LXD is installed as a snap which is not in the released charms yet.  This bug is thus a dup of https://bugs.launchpad.net/nova-lxd/+bug/1824161"
1821867,2019-04-30 21:59:12 UTC,"Hello Frank, or anyone else affected,"
1821867,2019-05-02 07:02:15 UTC,"netplan.io 0.96-0ubuntu0.18.10.2 on cosmic was already successfully verified (see comment #12),
but looks like this release wasn't good for other reasons (for others)?"
1821867,2019-05-02 07:05:38 UTC,netplan.io 0.96-0ubuntu0.18.04.2 was already successfully verified on bionic (see comment #13).
1821867,2019-05-08 00:00:42 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
1821867,2019-05-08 00:01:20 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
1821867,2019-05-09 21:57:24 UTC,"Hello Frank, or anyone else affected,"
1821867,2019-05-20 08:17:14 UTC,"I trust you have used the package versions from -proposed during verification, but for the future please always include information about the version numbers as part of the testing comment. Thanks!"
1821867,2019-05-09 22:02:43 UTC,"Hello Frank, or anyone else affected,"
1821867,2019-05-10 13:05:51 UTC,"I did another 3 installations, since the original problem I faced was after the post-install reboot, where the interfaces didn't came up properly.
   - hwe0005: bionic - up18042B
   - hwe0006: cosmic - up1810
   - hwe0007: disco - up1904
Obviously a parmfile was needed to enable proposed:
         listfiles up* * o
         UP18042B EXEC     O1
         UP1810   EXEC     O1
         UP1904   EXEC     O1
         listfiles PP* * o
         PP18042B UBUNTU   O1
         PP1810   UBUNTU   O1
         PP1904   UBUNTU   O1
         Ready; T=0.01/0.01 05:36:38
each PP-file with:
         00000 * * * Top of File * * *
         00001 ro locale=en_US apt-setup/proposed=true
         00002 * * * End of File * * *
double check kernel parameters in d-i shell before proceeding with the installations:
      ~ # cat /proc/cmdline
      ro locale=en_US apt-setup/proposed=true
Post-installation worked fine and the interfaces were properly activated on following reboot.
Triggered further reboots and could not identify any issue with the interface activation so far.
I let the systems run for several hours and worked with them w/o any problems,
hence setting tags to verification done."
1821867,2019-04-30 21:05:48 UTC,"Hello Frank, or anyone else affected,"
1821867,2019-05-20 08:29:26 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~19.04.1
1821867,2019-05-20 08:42:25 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.10.1
1821867,2019-05-20 08:44:12 UTC,"@ sil2100:
Yes, that's what I did - I used proposed and indicated it by the following kernel arg (mentioned above):
apt-setup/proposed=true"
1821867,2019-05-20 08:47:57 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.04.1
1821867,2019-04-15 22:34:00 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821867,2019-05-09 21:59:50 UTC,"Hello Frank, or anyone else affected,"
1821867,2019-04-11 07:31:19 UTC,"I installed the netplan.io version 0.96-0ubuntu0.18.04.3 from bionic-proposed on an LPAR system as well as on a z/VM guest.
Rebooted the systems, carried on with my remote work on them for some time and everything runs smoothly - the network is stable, no regression noticeable and the interface came always automatically up, hence I consider this as successfully verified.
Adjusting the tags accordingly."
1821867,2019-03-27 08:54:56 UTC,"After doing a restart the interface is down again, hence it's probably more a networkd / systemd issue:"
1821867,2019-03-27 09:08:26 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1821867,2019-03-27 09:10:17 UTC,systemd-networkd.service is not active after reboot:
1821867,2019-03-28 17:53:18 UTC,This seems quite likely to be an issue with netplan; I've had a similar report on UC18; where systemd-networkd isn't started.
1821867,2019-03-28 19:13:09 UTC,Just as a side note - this also happens (like expected) with LPAR installations.
1821867,2019-03-29 01:16:46 UTC,"Hello Frank, or anyone else affected,"
1821867,2019-03-29 01:23:23 UTC,"Hello Frank, or anyone else affected,"
1821867,2019-04-15 22:32:43 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.2
1821867,2019-03-29 09:13:00 UTC,Successfully verified on cosmic - since I was able to login to a newly installed system (that was installed using 'apt-setup/proposed=true') right away:
1821867,2019-03-29 10:54:24 UTC,Successfully verified on bionic (18.04.2) - since I was able to login to a newly installed system (that was installed using 'apt-setup/proposed=true') right away:
1821867,2019-03-29 15:46:00 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu4
1821867,2019-04-01 09:50:12 UTC,"Just for completeness reason:
I've just verified that the fixed package landed in disco-server-s390x.iso 2019-04-01
Hence installs incl. post-install reboot and automatically bringing up the interface is fine now."
1821867,2019-04-08 18:20:15 UTC,Thanks!
1821867,2019-04-10 21:22:08 UTC,"Hello Frank, or anyone else affected,"
1821867,2019-03-29 08:21:27 UTC,"I first of all tested the package:
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu4
from disco proposed, since it was on disco where I faced that problem, and that works now.
Tested just upgraded an already installed disco system to the netplan.io version from proposed, as well as doing a proposed installation (having 'apt-setup/proposed=true' added to the parmfile).
Both is good so far - looking forward to see it landing in one of the next disco daily images."
1821868,2020-07-02 19:28:46 UTC,"Ubuntu 19.04 reached end of life on January 23, 2020.  I am therefore marking this bug 'wontfix' for that release."
1821868,2020-03-06 20:23:26 UTC,Currently occurring after installing Kmail using apt on Kubuntu 20.04
1821868,2019-09-08 10:33:49 UTC,"Still occurs in 19.08.1 in Neon, and Kubuntu staging builds."
1821868,2019-04-09 08:03:20 UTC,Possible workarounds:
1821868,2019-03-27 11:08:39 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1821868,2019-03-27 10:08:08 UTC,"I think this is a race condition in the initial setup: the race could be that on first start the Maildir resource (that backs the ""Local folders"") starts discovering what folders exist in ~/.local/share/mail and starts creating them in Akonadi and at the same time KMail realizes there's no Inbox, Outbox etc. in Local Folders and starts creating them."
1821868,2019-03-27 10:02:48 UTC,Creating the ~/.config/specialmailcollectionsrc file with its default content of:
1821868,2019-03-16 02:06:31 UTC,Reproducible here on debian sid/buster.
1821868,2019-03-16 10:06:19 UTC,Also confirmed on KDE Neon user edition with PIM 18.12.3
1821868,2019-03-15 08:34:31 UTC,Can also see this on 18.12.3 packages staged for Kubuntu
1821868,2019-03-15 08:34:02 UTC,Also occurring on Debian Buster with 18.08
1821868,2017-05-25 16:35:45 UTC,with debug packages
1821868,2019-03-27 08:55:07 UTC,Ubuntu Bug: https://bugs.launchpad.net/kmail/+bug/1821868
1821868,2017-05-25 08:14:25 UTC,"Created attachment 105703
screenshot or error dialog window"
1821869,2019-04-29 16:47:44 UTC,This bug was fixed in the package python3.6 - 3.6.8-1~18.10
1821869,2019-06-10 16:04:38 UTC,This bug was fixed in the package python3.7 - 3.7.3-2~18.04.1
1821869,2019-04-29 16:47:51 UTC,This bug was fixed in the package python3.7 - 3.7.3-2~18.10
1821869,2019-04-11 20:38:16 UTC,"Hello Matthias, or anyone else affected,"
1821869,2019-04-04 03:06:59 UTC,This bug was fixed in the package python3.7 - 3.7.3-2
1821869,2019-04-02 20:55:53 UTC,This turned out to be a mis-aligned access in the _sha3 module. There's a NO_MISALIGNED_ACCESSES define that can be used on the relevant platform (armhf) to fix it. Fixed package uploaded to https://launchpad.net/~waveform/+archive/ubuntu/pkg
1821869,2019-04-11 20:40:28 UTC,"Hello Matthias, or anyone else affected,"
1821870,2019-03-27 08:53:11 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1821870,2019-04-07 15:35:28 UTC,https://errors.ubuntu.com/oops/9f40d39c-5948-11e9-a557-fa163ee63de6
1821870,2019-04-08 01:54:38 UTC,Thanks. Unfortunately that page doesn't (yet) show any stack trace or link to a problem page. Maybe it needs more time for the servers to analyse. If it doesn't change in the next day or two then you will need to repeat the crash and above steps :(
1821870,2019-04-09 14:43:08 UTC,https://errors.ubuntu.com/oops/9f40d39c-5948-11e9-a557-fa163ee63de6
1821870,2019-04-10 02:38:26 UTC,"Unfortunately that's the same crash from April 7th, and there's no new information on that page."
1821870,2019-04-14 13:17:21 UTC,"I keep getting:
[ 8831.746466] gnome-shell[3678]: segfault at 0 ip 00007f02a52a2021 sp 00007ffd231b8f10 error 4 in libmutter-clutter-2.so[7f02a5222000+161000] multiple times a day."
1821870,2019-06-14 04:17:23 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1821872,2019-03-27 09:15:26 UTC,This is probably not as easy as just changing the cirros image:
1821872,2019-04-04 13:40:31 UTC,Agreed that we need to fix this. Wishlisted for now -- will bump in priority when/if we expand the intended use case beyond a developer's laptop.
1821872,2019-11-21 20:56:06 UTC,"This isn't just a hypothetical wishlist item for much longer. Ubuntu now supports Raspberry Pi 4 which goes up to 4GB RAM. Add 4GB swap, you have an 8GB Ubuntu machine (stated microstack RAM requirements) for about $130, which will install the correct ARM architecture MicroStack and even let you get into OpenStack Horizon!"
1821872,2019-11-22 15:49:31 UTC,"p.s. a handy reference for how to make nova work on raspberry pi is here:
https://ask.openstack.org/en/question/123578/timeout-between-nova-conductor-and-nova-compute-on-arm64-raspberrypi-rockpi/"
1821873,2021-01-28 05:09:37 UTC,"I have an HP laptop running Ubuntu 20.10. Implementing iGadget's suggestion (Exec=bash -c ""sleep 10 && hp-systray -x"") fixes the issue."
1821873,2020-11-17 08:00:47 UTC,"'Solved' the problem by adding a startup delay of 10 secs. in /etc/xdg/autostart/hplip-systray.desktop, replacing the existing 'Exec=' line like so:"
1821873,2020-11-15 00:43:27 UTC,Same issue on Ubuntu 20.10.
1821875,2019-03-27 15:46:58 UTC,"hi, Here I attach my installation procedure and error log.
I installed Zun-UI using the steps explained in https://docs.openstack.org/zun-ui/latest/install/index.html#manual-installation"
1821875,2019-05-25 21:27:42 UTC,"As suggested by https://ask.openstack.org/en/question/105842/horizon-could-not-import-openstack_dashboardsettings/ , running the follow command might resolve the issue:"
1821875,2019-06-14 09:55:36 UTC,"my question is that i can see directory horizon, but when i type ""cd horizon""   -su: cd: horzion: No such file or directory  ?????  no requirements.tst"
1821875,2019-06-14 10:09:36 UTC,my version is queens
1821875,2019-06-15 16:20:54 UTC,"@yep,"
1821875,2019-06-15 16:23:50 UTC,"On Fri, Jun 14, 2019 at 6:00 AM yep <email address hidden> wrote:"
1821879,2019-03-27 09:30:06 UTC,This change was made by a bot.
1821882,2019-03-28 04:28:29 UTC,I tried the same while blacklisting nouveau driver in grub:
1821882,2019-03-28 07:08:30 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1821882,2019-03-29 08:37:41 UTC,Is this a regression from older releases?
1821882,2019-04-03 02:54:50 UTC,"Sorry Timo, I had missed your last comment."
1821882,2019-04-08 05:03:54 UTC,With BIOS settings:
1821882,2019-04-08 18:12:08 UTC,"I tried _BCM for both its ACPI graphics devices, and it doesn't work whether ""Enable Switchable Graphics"" is enabled or not. So for this platform, the brightness is not controlled by its ACPI interface."
1821884,2019-05-03 09:32:39 UTC,"Posted
[PULL 0/2] tests/uefi-test-tools: report the SMBIOS entry point structures
http://<email address hidden>"
1821884,2019-04-25 10:44:38 UTC,"Posted
[PATCH 0/2] tests/uefi-test-tools: report the SMBIOS entry point structures
http://<email address hidden>"
1821884,2019-05-06 16:21:21 UTC,Fixed in commit range 8482ff2eb3bb..24496b8d27d9.
1821884,2019-03-27 11:18:03 UTC,"Discussion on qemu-devel:
[Qemu-devel] [PATCH for 4.1 v2 09/13] tests: acpi: ignore SMBIOS tests when UEFI firmware is used
http://mid<email address hidden>
https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg07037.html"
1821888,2019-03-28 08:30:40 UTC,Would someone please review this backport request?
1821888,2019-03-28 08:25:54 UTC,xsd 4.0.0-4 *fails* to build against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:23:49 UTC,xml-security-c 1.7.3-1ubuntu0.1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:22:15 UTC,xmltooling 1.5.6-2ubuntu0.3 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:21:14 UTC,xmlcopyeditor 1.2.1.3-1build1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:20:19 UTC,xalan 1.11-5 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:18:53 UTC,vxl 1.17.0.dfsg2-4 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:18:08 UTC,sumo 0.25.0+dfsg1-2 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:17:12 UTC,sipxtapi 3.3.0~test17-1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:16:03 UTC,shibboleth-resolver 1.0.0-1build1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 08:13:44 UTC,xqilla 2.3.0-3 *fails* to build against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 10:14:32 UTC,The package builds without modification using `backportpackage --destination=xenial --source=bionic --build --builder=cowbuilder --key=0x6965D453D81531AD xerces-c`.
1821888,2019-03-27 16:33:21 UTC,qpid-cpp 0.16-9ubuntu2 *fails* to build against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 16:20:10 UTC,passwordsafe 0.98.1+dfsg-3 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 16:15:33 UTC,opensaml2 2.5.5-1ubuntu0.1 *fails* to build against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-28 07:24:28 UTC,shibboleth-sp2 2.5.3+dfsg-2.1build1 *fails* to build against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 16:06:58 UTC,libkolab 1.0.2-10ubuntu6 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 10:20:19 UTC,"Built packages install and upgrade cleanly, tested with `piuparts -b /var/cache/pbuilder/base-xenial-amd64.tgz --distribution=xenial --keep-sources-list --arch=amd64 -D ubuntu xerces-c_3.2.0+debian-2~ubuntu16.04.1_amd64.changes` (APT sources: xenial, xenial-updates, xenial-backports)."
1821888,2019-03-27 13:03:57 UTC,ace 6.3.3+dfsg-1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 13:07:17 UTC,anon-proxy 00.05.38+20081230-2.4 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 16:08:54 UTC,librcsb-core-wrapper 1.005-4build1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 13:26:51 UTC,cegui-mk2 0.8.4+dfsg-4ubuntu1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 13:28:42 UTC,clam 1.4.0-7 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 13:55:49 UTC,diet 2.8.0-1ubuntu1 *fails* to build against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 13:09:02 UTC,blahtexml 0.9-1.1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 14:14:15 UTC,flightcrew 0.7.2+dfsg-6 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 15:54:13 UTC,libkolabxml 1.1.2-0ubuntu3 *fails* to build against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 15:55:30 UTC,freecad 0.15.4671+dfsg1-4 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 15:56:38 UTC,freecontact 1.0.21-4 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 15:57:35 UTC,gdal 1.11.3+dfsg-3build2 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 16:04:02 UTC,gyoto 1.0.2-2ubuntu1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821888,2019-03-27 14:02:28 UTC,enigma 1.20-dfsg.1-2build1 successfully builds against libxerces-c-dev 3.2.0+debian-2~ubuntu16.04.1
1821897,2019-06-07 22:24:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821897,2019-09-15 17:14:41 UTC,Also a problem in Ubuntu 18.04.
1821897,2019-09-16 10:08:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1821897,2019-11-16 04:17:31 UTC,[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]
1821898,2019-03-27 11:35:10 UTC,"The issue is caused by the SVC driver accessing the database directly, which is not considered good practice in Cinder, though this code could come from a time when this was a common practice in Cinder drivers."
1821898,2019-03-27 18:52:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648212"
1821898,2019-03-27 19:21:06 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/648218"
1821898,2019-09-05 00:02:07 UTC,"Reviewed:  https://review.opendev.org/648218
Committed: https://git.openstack.org/cgit/openstack/cinderlib/commit/?id=c97367d89d341c5c2eba4102e46571ff92da2eeb
Submitter: Zuul
Branch:    master"
1821898,2019-08-28 16:12:45 UTC,"Reviewed:  https://review.opendev.org/648212
Committed: https://git.openstack.org/cgit/openstack/cinderlib/commit/?id=385e6f4a1ec5c382885321b3db9d80f26f66c117
Submitter: Zuul
Branch:    master"
1821898,2019-12-12 10:07:59 UTC,This issue was fixed in the openstack/cinderlib 1.0.0 release.
1821899,2019-04-04 14:33:19 UTC,To me the error is because of this:
1821899,2019-04-04 14:36:20 UTC,"Also, it seems this would be fixed by doing one of two things:"
1821899,2019-04-18 08:37:12 UTC,"@andrea, I always can't reproduce the problem in my test env with or without 'bond0.2 -> br-bond0.2', but I did see that one customer had this problem. what maas version are you using? do you have the detail steps to reproduce the problem ?"
1821899,2019-05-08 22:59:27 UTC,"Indeed, as you can see from the comment above, we are not double-tagging vlans.  we are merely calling out that the bridge name is the bondx.vlany environment by naming it brbondx.vlany, but only bondx.vlany is being tagged with 802.1q."
1821899,2019-05-08 23:03:07 UTC,"It appears that the regiond is trying to populate the vlanid of that probed interface based on name of the device, however name of the device has no bearing on whether there's actually vlanid tagging happening.  VLAN tagging should be introspected from /proc/net/vlan/config file, not inferred from the interface names."
1821899,2019-07-08 04:17:31 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1821903,2019-10-14 04:01:46 UTC,"For node gonzo with 4.15, it's:
  WARNING: vmx not supported, add '-cpu host'
  SUMMARY: 0 tests
  SKIP vmx (0 tests)"
1821903,2019-06-20 08:49:02 UTC,"Issue still exist with Cosmic amd64 (node gonzo):
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/svm'
 BUILD_HEAD=b5d7d7f1
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.VnkI4knNSX -smp 2 -cpu qemu64,+svm,+tsc-adjust # -initrd /tmp/tmp.Ool7CJM5vy
 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
 enabling apic
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 467000
 cr4 = 20
 PASS: null
 PASS: vmrun
 PASS: ioio
 PASS: vmrun intercept check
 PASS: cr3 read intercept
 PASS: cr3 read nointercept
 PASS: cr3 read intercept emulate
 PASS: dr intercept check
 PASS: msr intercept check
 PASS: mode_switch
 PASS: asid_zero
 PASS: sel_cr0_bug
 FAIL: tsc_adjust
 Latency VMRUN : max: 169094 min: 17443 avg: 17769
 Latency VMEXIT: max: 127855 min: 17870 avg: 18294
 PASS: latency_run_exit
 Latency VMLOAD: max: 61609 min: 4802 avg: 4958
 Latency VMSAVE: max: 36274 min: 4676 avg: 4869
 Latency STGI: max: 72350 min: 3969 avg: 4070
 Latency CLGI: max: 69159 min: 3511 avg: 3534
 PASS: latency_svm_insn
 SUMMARY: 15 tests, 1 unexpected failures
 FAIL svm (15 tests, 1 unexpected failures)"
1821903,2019-05-07 09:59:07 UTC,Saw this one passed with Bionic 5.0 kernel (AMD64)
1821903,2019-04-19 11:49:43 UTC,"I fixed the issue with tsc-adjust on kvm-unit-tests itself, sent upstream, fixed on our disco branch. That should fix it for 4.4 kernels as well, though I only tested on 5.0 kernels for now. Trusty likely needs further review."
1821903,2019-03-27 11:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821903,2019-03-27 11:09:19 UTC,Could be found on X-4.4 as well.
1821903,2019-04-19 11:50:29 UTC,"The upstream submission:
https://marc.info/?l=kvm&m=155561857003690&w=2"
1821904,2019-03-29 16:28:26 UTC,"Just to confirm, I also did this upgrade path (18.04 -> 18.10 -> 19.04) on my desktop and I get the same issue."
1821904,2020-01-24 09:33:01 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1821904,2019-06-01 04:17:30 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1821904,2019-04-01 09:23:05 UTC,"Yeah, it's only `Snap user application autostart helper` and `SSH Key Agent`."
1821904,2019-04-01 09:15:00 UTC,OK. Try running:
1821904,2019-04-01 09:00:07 UTC,"Hi Daniel,"
1821904,2019-04-01 02:45:45 UTC,There might be some old config setting that's wrong as a result of the upgrades.
1821904,2019-03-29 10:12:43 UTC,"Um, good question.  The volume in Gnome shell top right panel, as well in Gnome settings, appears muted (and it is muted when I try to play things).  All I need to do is unmute / press volume up or down to fix this, it's just a small niggle."
1821904,2019-03-28 11:37:51 UTC,apport information
1821904,2019-03-28 11:40:29 UTC,"Thanks Dan, hopefully they're all here."
1821904,2019-03-28 11:37:49 UTC,apport information
1821904,2019-03-28 11:37:48 UTC,apport information
1821904,2019-03-28 11:37:47 UTC,apport information
1821904,2019-03-28 11:37:46 UTC,apport information
1821904,2019-03-28 11:37:44 UTC,apport information
1821904,2019-03-28 02:10:54 UTC,Please run these commands:
1821904,2019-03-29 01:50:03 UTC,I assume this bug is about audio and you're not talking about something appearing muted...? :)
1821905,2019-04-19 05:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821905,2019-04-19 04:39:20 UTC,Found on Azure Trusty 4.15 as well.
1821906,2019-03-27 11:30:18 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821906,2019-07-17 02:39:49 UTC,"Failure on Trusty:
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.4VEzBBYPcp -smp 1 # -initrd /tmp/tmp.Ef5R8Mt7p5
 enabling apic
 PASS: #BP
 FAIL: hw breakpoint (test that dr6.BS is not set)
 FAIL: hw breakpoint (test that dr6.BS is not cleared)
 FAIL: single step
 FAIL: single step emulated instructions
 FAIL: hw watchpoint (test that dr6.BS is not cleared)
 FAIL: hw watchpoint (test that dr6.BS is not set)
 PASS: icebp
 PASS: MOV SS + watchpoint + ICEBP
 PASS: MOV SS + watchpoint + int $1
 PASS: MOV SS + watchpoint + INT3
 SUMMARY: 11 tests, 6 unexpected failures
 FAIL debug (11 tests, 6 unexpected failures)"
1821906,2020-01-23 21:33:31 UTC,"Target: Xenial
8.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: #BP
9.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: hw breakpoint (test that dr6.BS is not set)
10.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: hw breakpoint (test that dr6.BS is not cleared)
11.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: single step
12.	01/16 09:21:09 DEBUG| utils:0152| [stdout] FAIL: single step emulated instructions
13.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: hw watchpoint (test that dr6.BS is not cleared)
14.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: hw watchpoint (test that dr6.BS is not set)
15.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: icebp
16.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: MOV SS + watchpoint + ICEBP
17.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: MOV SS + watchpoint + int $1
18.	01/16 09:21:09 DEBUG| utils:0152| [stdout] PASS: MOV SS + watchpoint + INT3
19.	01/16 09:21:09 DEBUG| utils:0152| [stdout] SUMMARY: 11 tests, 1 unexpected failures
20.	01/16 09:21:09 DEBUG| utils:0152| [stdout] FAIL debug (11 tests, 1 unexpected failures)"
1821906,2020-11-17 04:25:39 UTC,Still visible in Xenial 4.4.0-1118.132 AWS c5.metal
1821908,2019-03-27 11:30:26 UTC,This change was made by a bot.
1821908,2019-03-27 11:30:36 UTC,"   dpkg: dependency problems prevent configuration of linux-image-extra-3.13.0-53-generic:
    linux-image-extra-3.13.0-53-generic depends on linux-image-3.13.0-53-generic; however:
     Package linux-image-3.13.0-53-generic is not configured yet."
1821911,2020-08-30 04:45:12 UTC,​​​Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1821912,2019-10-09 16:40:39 UTC,"Change abandoned by Miguel Lavalle (<email address hidden>) on branch: master
Review: https://review.opendev.org/653021
Reason: Not debugging this anymore"
1821912,2019-04-01 20:48:41 UTC,"This bug is meant to be a team effort, since we don't have a pattern that fits all the intermittent ssh failures we see in our tests. So, if you want to help, just use the logstash query in the bug description and find something to debug. Please keep us informed of what you are working on by writing updates in this bug. Thanks :-)"
1821912,2020-11-16 14:57:21 UTC,"Reviewed:  https://review.opendev.org/757662
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=297f4c20c4c914f7fc8528e70d572adbeff68b0f
Submitter: Zuul
Branch:    stable/rocky"
1821912,2020-10-13 01:31:55 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/757662"
1821912,2019-12-04 08:52:15 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/659009
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1821912,2019-12-04 08:49:41 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/670925
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results."
1821912,2019-07-25 14:54:21 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/672303
Reason: As can be seen in http://logs.openstack.org/03/672303/1/check/neutron-tempest-plugin-dvr-multinode-scenario-rocky/d71f994/testr_results.html.gz it don't work as expected"
1821912,2019-07-23 14:48:29 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/672303"
1821912,2019-07-15 23:09:02 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/670925"
1821912,2019-07-02 10:24:35 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: master
Review: https://review.opendev.org/655431"
1821912,2019-05-26 03:21:35 UTC,"Reviewed:  https://review.opendev.org/660758
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fe4fc33f1c1bbb655e99733edf762e3e9debdd3e
Submitter: Zuul
Branch:    stable/stein"
1821912,2019-05-22 15:28:06 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/660758"
1821912,2019-05-14 09:54:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659009"
1821912,2019-05-05 05:54:39 UTC,http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22line%20107%2C%20in%20_get_ssh_connection%5C%22%20AND%20build_status%3A%5C%22FAILURE%5C%22%20AND%20build_branch%3A%5C%22master%5C%22%20AND%20NOT%20build_name%3A%5C%22neutron-tempest-plugin-dvr-multinode-scenario%5C%22%20AND%20project%3A%5C%22openstack%2Fneutron%5C%22%20AND%20NOT%20build_name%3A%5C%22networking-ovn-tempest-dsvm-ovs-release%5C%22
1821912,2019-05-04 23:20:37 UTC,"I focused on analysis of issue with Authentication Failures.
First I tried to reproduce this issue locally to check if slow answer from nova-metadata-api can really cause this problem. So I added simple time.sleep(15) in https://github.com/openstack/nova/blob/e5b819fb75320f192f79e92384bac8be043e9600/nova/api/metadata/handler.py#L94 and I got exactly same error coming from ""ec2metadata"" script which is in cirrus image.
So it looks that really some kind of slowdown in nova-metadata-api can cause this problem."
1821912,2019-05-21 01:06:51 UTC,"Interim summary:
1. floating IP is DOWN status while trying to ssh
2. VM is still booting while trying to ssh
3. VM port is still DOWN status while trying to ssh
4. router processing is time-consuming may cause instance failed to retrieve metedata"
1821912,2019-04-26 09:45:05 UTC,@Slaweq: I think the public-keys query was answered by nova but it was delayed. I think this is the answer http://logs.openstack.org/47/653947/3/gate/tempest-slow-py3/629abee/controller/logs/screen-n-api-meta.txt.gz#_Apr_25_14_56_39_902289
1821912,2019-04-01 21:05:38 UTC,"From what I was checking, in all those cases (or almost all) instance was able to reach metadata server so connectivity from instance to router was fine.
So, I think that issue is somewhere between ""tempest runner""-- router, or maybe in router it self FIP is badly configured but that I'm not sure."
1821912,2019-04-10 14:57:15 UTC,"http://logs.openstack.org/04/637304/7/check/neutron-tempest-plugin-scenario-linuxbridge/e562437/testr_results.html.gz
http://logs.openstack.org/57/651357/1/check/neutron-tempest-dvr-ha-multinode-full/3a0f4ee/testr_results.html.gz
http://logs.openstack.org/82/643882/4/check/tempest-slow-py3/3432a15/testr_results.html.gz"
1821912,2019-04-10 15:00:36 UTC,"And I also noticed that some router was not actually set up done, but nova was booting the VM up. This may relate to the bug:
[L3] DVR router in compute node was not up but nova port needs its functionality
https://bugs.launchpad.net/neutron/+bug/1813787
Mostly, the ssh keypair setting may rely on this."
1821912,2019-04-26 10:44:53 UTC,"Reviewed:  https://review.opendev.org/654815
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9d60716cf1d61286a684f20ef8e05c77a0df5aa3
Submitter: Zuul
Branch:    master"
1821912,2019-04-10 16:20:29 UTC,"http://logs.openstack.org/04/637304/7/check/neutron-tempest-plugin-scenario-linuxbridge/e562437/testr_results.html.gz
http://logs.openstack.org/57/651357/1/check/neutron-tempest-dvr-ha-multinode-full/3a0f4ee/testr_results.html.gz"
1821912,2019-04-16 15:09:21 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653021"
1821912,2019-04-10 15:11:53 UTC,@LIU: please not that in Your 3rd example (http://logs.openstack.org/82/643882/4/check/tempest-slow-py3/3432a15/testr_results.html.gz) it was different (and known) issue. VM got kernel panic. So that case can be easily moved out from our analysis process :)
1821912,2019-04-18 13:43:29 UTC,"An example: try to ssh the VM but the cirros is just booting.
http://logs.openstack.org/56/648456/4/check/tempest-full/ad806b2/testr_results.html.gz"
1821912,2019-04-23 07:38:19 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/654815"
1821912,2019-04-24 13:39:47 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/655431"
1821912,2019-04-26 08:32:45 UTC,Today I spent some time to investigate one of the problems which I found.
1821912,2019-04-17 14:40:38 UTC,"message:""line 107, in _get_ssh_connection"" AND build_status:""FAILURE"" AND build_branch:""master"" AND NOT build_name:""neutron-tempest-plugin-dvr-multinode-scenario"" AND project:""openstack/neutron"" AND NOT build_name:""networking-ovn-tempest-dsvm-ovs-release"""
1821914,2019-08-23 09:59:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821914,2019-08-23 13:02:40 UTC,"Ran into the same issue today, tried a lot of stuff before being able to eventually fix it. I had to wipe my entire Banshee installation (I deleted all the Banshee files on my machine and ran sudo apt purge banshee + apt autoremove & apt autoclean) then rebooted my system and reinstalled banshee. The rebooting part seems to have been essential but I can't figure out why. Regardless, Banshee now starts properly again."
1821916,2019-04-11 18:33:28 UTC,"Reviewed:  https://review.openstack.org/648425
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bf3a6ad7c9047b3dccc13c73a9959f358bfbfaed
Submitter: Zuul
Branch:    stable/rocky"
1821916,2019-09-27 09:05:23 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1821916,2019-06-18 03:41:26 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1821916,2019-06-06 06:24:47 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1821916,2019-04-10 20:24:38 UTC,"Reviewed:  https://review.openstack.org/648412
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7ccea385b14a9cadb597d844310e3f8bf2ed237b
Submitter: Zuul
Branch:    stable/stein"
1821916,2019-03-27 13:39:52 UTC,"Heh, yeah, good catch, even the console example uses the correct CLI."
1821916,2019-03-28 14:26:39 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/648412"
1821916,2019-03-28 13:07:52 UTC,"Reviewed:  https://review.openstack.org/648299
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b71a5bae88e59b42a655322bf22dff5b9ff5aa2d
Submitter: Zuul
Branch:    master"
1821916,2019-03-28 01:06:47 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648299"
1821916,2019-03-28 14:42:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/648425"
1821919,2019-03-29 15:47:37 UTC,The same bug was on Ubuntu 18.04 and Mint 19.1  but not on Debian 9.8
1821919,2019-03-29 15:55:09 UTC,The same bug was on Ubuntu 18.04 and Mint 19.1 but not on Debian 9.8
1821921,2019-03-30 17:22:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821925,2019-04-08 13:41:49 UTC,Suggested change: https://review.openstack.org/#/c/648239/
1821925,2019-04-08 12:30:23 UTC,"OK for the general tracking list feedback, let's scale down to filtering that volume test (not likely to be fixe in EM branches): if you set the logstash request in initial comment to 7d ago (aka first week of April), you will see around 60 hits failing on ocata (and 40-50 on pike, but that is another subject)."
1821925,2019-05-13 19:53:06 UTC,"Reviewed:  https://review.opendev.org/648239
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=33c18a65f829295ca99cfb537e270986185f9ba4
Submitter: Zuul
Branch:    stable/ocata"
1821925,2019-03-27 16:11:15 UTC,"Ideally yes if new tests start to fail, the patch adding them to ""exclude list"" would be marked as related to this bug. I do not expect too many of them to pop in though (or it would mean the stable branch is really starting to get stale and should probably be EOLed)."
1821925,2019-03-27 14:26:05 UTC,I understand the motivation to limit the CI maintenance effort as a stable branch get older. But how do you want to use this bug report? Do you want to keep it open indefinitely and refer to it from changes marking tests to be skipped or unstable? Won't we mix multiple distinct problems in the same tracking report then?
1821925,2019-03-28 18:23:12 UTC,During reviewing stable patches what I see is:
1821926,2019-03-27 13:53:01 UTC,Subscribed ~field-critical
1821926,2019-03-27 14:07:12 UTC,"It's a cloud hyperconverged architecture, 6x machines."
1821926,2019-03-27 14:09:50 UTC,'nova --debug service-list' output attached.
1821926,2019-03-27 14:18:58 UTC,'openstack --debug host list' output attached.
1821926,2019-03-27 14:19:32 UTC,'juju status' output in YAML format.
1821926,2019-03-27 15:15:01 UTC,To summarize conversation from irc:
1821926,2019-03-29 16:55:56 UTC,This looks to have a been caused by the fact that Nova was unable to communicate with memcached and this was causing some nova api queries to hang. tl;dr is that memcache creates fw rules and the relation with nova-cc was using the wrong Juju space therefore choosing the wrong addresses.
1821926,2019-05-29 04:17:27 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1821927,2019-08-01 08:31:26 UTC,"On Thu, Aug 1, 2019 at 8:50 AM Robie Basak <email address hidden> wrote:

>
> Surely if we're in agreement that we should be consistent, that means
> that we either patch to make them one way, or we patch to make them
> consistent the other way.
"
1821927,2019-08-01 16:16:04 UTC,This bug was fixed in the package sssd - 2.2.0-4ubuntu1
1821927,2019-08-01 15:12:34 UTC,See also bug 1838380. Perhaps these should all be merged into the same bug.
1821927,2019-08-01 06:43:12 UTC,"Surely if we're in agreement that we should be consistent, that means that we either patch to make them one way, or we patch to make them consistent the other way. Patching to make them inconsistent doesn't follow, and nor does not patching an exception to leave that one different from all the others."
1821927,2019-03-29 07:33:29 UTC,"We discussed this yesterday and think that is a vlaid bug report - thanks!
It spawned a spin-off discussion how we want to handle auto-restart in general which will go on for a while."
1821927,2019-07-31 20:24:09 UTC,"I'm not keen on doing something special just for sssd. Either all ""server-y"" packages should be Restart=on-failure, or none of them, or we should have clear criteria. It's the job of the distribution to provide consistency across packages here."
1821927,2019-07-04 06:36:27 UTC,"It seems this fell through the cracks, sorry for that.
While cleaning up bugs and tasks I found it and filed an upstream discussion [1].
Depending on the outcome of this we can make the modification (or not)."
1821927,2019-08-01 04:37:06 UTC,"In this case Robie we are following upstream where we suggested it due to this bug.
And while I agree to making things consistent across packages we have talked about it before and nothing happened yet. IMHO: It is correct to say ""let us use this as a reminder to reconsider an effort across packages"" but not ""hold this one back as it might make it different (others are already)""."
1821927,2019-03-27 14:26:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1821930,2019-04-09 13:36:27 UTC,"Hi Pedro,"
1821931,2019-03-28 06:16:29 UTC,"Reviewed:  https://review.openstack.org/648048
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=db52a40628e8e90ae2499cbe259bfd69c11ade09
Submitter: Zuul
Branch:    stable/queens"
1821931,2019-03-28 06:27:30 UTC,"Reviewed:  https://review.openstack.org/648054
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=fb0a12206151223bf821e422bea9bbc4f4f95001
Submitter: Zuul
Branch:    stable/rocky"
1821931,2019-06-21 13:45:31 UTC,This issue was fixed in the openstack/os-net-config 9.4.0 release.
1821931,2019-06-21 15:23:10 UTC,This issue was fixed in the openstack/os-net-config 8.5.0 release.
1821934,2019-05-30 14:06:20 UTC,"I made a mistake on the disco patch and the buglink tag wasn't included. However the change is already released in disco/linux-azure so I'm marking it manually as ""Fix Released""."
1821934,2019-05-14 22:58:04 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1821934,2019-05-14 19:04:29 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18
1821934,2019-04-24 08:25:59 UTC,This bug was fixed in the package linux-azure - 4.15.0-1042.46
1821934,2019-04-24 08:15:30 UTC,This bug was fixed in the package linux-azure - 4.15.0-1042.46~14.04.1
1821934,2019-04-02 15:54:20 UTC,"Will do.  Thanks, Marcelo!"
1821934,2019-04-02 11:55:40 UTC,"Hi, Joe."
1821934,2019-04-01 16:26:30 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-March/099651.html
1821934,2019-03-27 22:34:35 UTC,"Thanks for the clarification. Is there any reason for this bug to remain private? It is well known that ""nosmt"" is needed to mitigate CPU side channel issues, such as CVE-2018-3646, and sufficiently paranoid folks have been using it quite a bit lately."
1821934,2019-03-27 17:55:26 UTC,"Sorry for the confusion.  You are correct.  The referenced patches fix a crash that is caused when nosmt is enabled, not the security issue itself."
1821934,2019-03-27 16:06:10 UTC,"Hey there, Joe! I'd like to make sure that I understand the problem a little better:"
1821935,2019-04-10 14:02:30 UTC,Could you please tell me where I have to set that level?
1821935,2019-04-10 13:32:13 UTC,"Could you set log level = 2 please, and then send the logs again when the panic happens?"
1821935,2019-04-10 12:50:24 UTC,Maybe quotas?e
1821935,2019-04-10 12:48:35 UTC,"Hm, the logs still say disk full... Could it be that someone is trying to upload a really large file and that is crashing the system? Maybe a backup job?"
1821935,2019-04-08 14:01:54 UTC,"df -h
Sys. de fichiers            Taille Utilisé Dispo Uti% Monté sur
udev                          457M       0  457M   0% /dev
tmpfs                          98M     39M   59M  40% /run
/dev/mapper/servamtex2-root   456G     76G  358G  18% /
tmpfs                         486M       0  486M   0% /dev/shm
tmpfs                         5,0M       0  5,0M   0% /run/lock
tmpfs                         486M       0  486M   0% /sys/fs/cgroup
/dev/mapper/servamtex-root    456G     36G  397G   9% /servamtex-old
/dev/sdc                      1,8T    1,1T  678G  62% /bu
/dev/sda1                     228M    135M   82M  63% /boot
tmpfs                          98M       0   98M   0% /run/user/1000"
1821935,2019-04-08 12:49:38 UTC,"Can you get a fresh set of these when the panic happens again please?
- df -h
- logs from /var/log/samba/log*
- crash file from /var/crash (you might want to remove any crash files from there right now, to be sure it's a new one when the panic happens again)."
1821935,2019-04-03 14:45:10 UTC,"df -h
Sys. de fichiers            Taille Utilisé Dispo Uti% Monté sur
udev                          457M       0  457M   0% /dev
tmpfs                          98M    3,0M   95M   4% /run
/dev/mapper/servamtex2-root   456G     76G  358G  18% /
tmpfs                         486M       0  486M   0% /dev/shm
tmpfs                         5,0M       0  5,0M   0% /run/lock
tmpfs                         486M       0  486M   0% /sys/fs/cgroup
/dev/mapper/servamtex-root    456G     36G  397G   9% /servamtex-old
/dev/sdc                      1,8T    1,1T  696G  61% /bu
/dev/sda1                     228M    135M   82M  63% /boot
tmpfs                          98M       0   98M   0% /run/user/1000"
1821935,2019-04-29 13:56:24 UTC,"Since last comment, no problem anymore.  An update for samba has been automatically installed in the mean time, as well as a couple of windows 10 updates."
1821935,2019-04-03 14:00:15 UTC,"The samba logs are full of:
  PANIC (pid 29821): reinit_after_fork() failed
  messaging_reinit() failed: NT_STATUS_DISK_FULL"
1821935,2019-04-01 14:25:38 UTC,"Thanks for the info, I'll look at it."
1821935,2019-03-29 13:34:35 UTC,apport information
1821935,2019-03-29 13:34:36 UTC,apport information
1821935,2019-03-29 13:34:33 UTC,apport information
1821935,2019-03-29 13:34:32 UTC,apport information
1821935,2019-03-29 13:34:31 UTC,apport information
1821935,2019-03-29 13:34:29 UTC,apport information
1821935,2019-03-29 13:34:29 UTC,apport information
1821935,2019-03-29 13:34:27 UTC,apport information
1821935,2019-03-29 07:53:11 UTC,@Paride - I think Andreas said we should ask for the .crash file right?
1821935,2019-03-29 13:34:38 UTC,apport information
1821936,2019-03-28 20:39:35 UTC,apport information
1821936,2019-03-28 20:39:53 UTC,"I did this yesterday per request and marked it as confirmed.  I just completed this for a second time agreeing to send some data which mentioned pulse-audio, etc., to you all. It completed at 16:39 local time, Miami."
1821936,2019-03-29 02:30:06 UTC,This change was made by a bot.
1821936,2019-03-29 05:39:25 UTC,"Does kernel parameter ""snd_hda_intel.model=alc256-asus-aio"" help?"
1821936,2019-03-29 19:34:42 UTC,"Added this and rebooted, did not help at all.  No sound."
1821936,2019-03-30 07:41:47 UTC,"Ah, that's because the model name wasn't included in kernel v4.18. Please use mainline kernel [1]
with the kernel parameter."
1821936,2019-03-30 13:12:23 UTC,apport information
1821936,2019-04-01 04:14:40 UTC,"Please attach dmesg, thanks!"
1821936,2019-03-30 13:17:54 UTC,apport information
1821936,2019-03-30 13:18:12 UTC,Same result - no sound.  apport-collect just ran again at 09:18 local for logs.
1821936,2019-04-01 18:28:31 UTC,dmesg
1821936,2019-04-02 03:54:48 UTC,The module parameter isn't applied.
1821936,2019-04-02 21:34:25 UTC,Command ran to add it again and run dmesg so it shows.  That does not help.  See attached dmesg.
1821936,2019-03-28 20:39:33 UTC,apport information
1821936,2019-03-30 13:13:11 UTC,That did not help.
1821936,2019-03-28 20:39:31 UTC,apport information
1821936,2019-03-29 02:09:58 UTC,I think you might be right about bug 1784485 being similar. In that case this would be a kernel bug. And the title should refer to the model of the computer instead of the model of sound chip.
1821936,2019-03-28 20:39:28 UTC,apport information
1821936,2019-03-27 21:40:12 UTC,Apologies my first run of apport was mainline 5.0. I immediately rebooted and use a standard default kernel for 18.04. I deleted both mainlines since they didn't solve my issue anyway.
1821936,2019-03-28 02:19:39 UTC,"Derek, are you saying kernel 4.18 (or earlier) does not have the bug?"
1821936,2019-03-28 02:20:54 UTC,"If the problem is the kernel version then please try to find the closest two versions where one works and the other does not, from this list:"
1821936,2019-03-28 09:49:31 UTC,"No, my point is that I tried other kernel versions to see if it was patched. No kernel world with ACL274 on this machine. Windows works great."
1821936,2019-03-28 11:31:53 UTC,See post #5 at https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485
1821936,2019-03-28 17:52:10 UTC,Please run `apport-collect 1821936` to collect log.
1821936,2019-03-28 20:39:14 UTC,apport information
1821936,2019-03-27 16:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821936,2019-03-28 20:39:16 UTC,apport information
1821936,2019-03-28 20:39:18 UTC,apport information
1821936,2019-03-28 20:39:20 UTC,apport information
1821936,2019-03-28 20:39:29 UTC,apport information
1821936,2019-03-28 20:39:22 UTC,apport information
1821936,2019-03-28 20:39:24 UTC,apport information
1821936,2019-03-28 20:39:26 UTC,apport information
1821936,2019-03-28 20:39:15 UTC,apport information
1821937,2019-04-01 19:06:44 UTC,"Sorry, without a sample GCStar database I can't analyze any details."
1821939,2019-03-29 08:00:58 UTC,"FYI - Might be:
- bug 1811580
Or broken /var/run / /run connection which is related to
- https://askubuntu.com/questions/1109934
- https://serverfault.com/questions/941855"
1821939,2019-05-29 04:17:18 UTC,[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]
1821939,2019-03-28 10:15:29 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1821942,2019-03-28 00:26:15 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1821942,2019-03-28 00:26:58 UTC,"Hello,"
1821942,2019-10-16 06:26:42 UTC,Looking at the error this looks like its insserv that breaks here - or smfpd which I cannot find as a package in ubuntu.
1821942,2019-12-16 04:17:28 UTC,[Expired for snapd because there has been no activity for 60 days.]
1821942,2019-12-16 04:17:29 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1821943,2019-03-28 00:27:21 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1821943,2019-03-28 00:27:36 UTC,Possible duplicate of 1821942
1821944,2019-03-28 14:21:38 UTC,"I am sorry for the repost. I only seem to see the first three comments, but I am getting the mails."
1821944,2019-06-07 04:17:20 UTC,[Expired for Snappy because there has been no activity for 60 days.]
1821944,2019-03-28 20:40:50 UTC,"Well, for some reason I can not comprehend, chromium works again. There was no update. Only another reboot."
1821944,2019-03-28 14:24:02 UTC,After having installed coredumpctl I tried starting chromium under sudo again and got some more output:
1821944,2019-03-28 14:16:43 UTC,"If there is a core dump, where would it reside?"
1821944,2019-03-28 13:44:22 UTC,/home/ace28/.config/chromium/Crash Reports/ is empty.
1821944,2019-03-28 13:41:21 UTC,It should have been intercepted by systemd. Try running coredumpctl.
1821944,2019-03-28 13:30:06 UTC,Usually I am not running chromium under sudo.
1821944,2019-03-27 18:31:49 UTC,"> If started with sudo it also reports the error message ('mkdir: cannot create directory '/run/user/0': Permission denied').
"
1821944,2019-03-27 18:30:26 UTC,Are you perchance running chromium under sudo?
1821944,2019-03-27 15:32:14 UTC,I hope this is the right place to submit this bug. Thank you for your good work ^^
1821945,2020-04-07 17:30:04 UTC,This behavior is observed for other tests as well:
1821950,2021-02-18 18:50:21 UTC,Removing milestone targets because the bug is tagged needsrepatch.
1821950,2020-08-20 18:59:50 UTC,"Based on the original ticket that describes using call number prefixes (and the assumptive suffixes), I attempted to add a copy/item without a Call Number Label using a prefix/suffix. The prefixes/suffixes established in the server admin menu editors are not populating the copy editor."
1821950,2020-08-20 18:55:58 UTC,"Based on Michele's testing, it sounds like the core of the issue might be that whatever function attempts to normalize the callnumber sortkey is unable to handle a null value on the callnumber label - so likely an addition to the existing functionality, rather than an error in the code as it currently stands. My guess is that the normalize functionality expects a bare minimum of having the callnumber label in order to work"
1821950,2020-08-19 13:46:05 UTC,Removing pullrequest due to testing comments
1821950,2020-08-18 21:49:06 UTC,I'm seeing the same sort of things as Michele.
1821950,2020-08-18 15:46:27 UTC,"I've tested the latest branch on a master test system, and also on a 3.4.3 system with production data."
1821950,2020-08-19 18:16:48 UTC,Adding a needsrepatch tag
1821950,2020-02-20 21:59:52 UTC,Note Mike Risher's comment on https://bugs.launchpad.net/evergreen/+bug/1713164
1821950,2019-11-11 15:54:55 UTC,"I believe that I've resolved the bug. Now an empty ""owning library"" field will disable the save button, and selecting a disabled owning library, will revert the the value back to the old value, instead of being null."
1821950,2019-10-08 21:04:47 UTC,Removing pullrequest and adding needsrepatch tag.
1821950,2019-09-05 16:22:30 UTC,"I have done some testing on this patch, and have seen the following problem with cat.require_call_number_labels set to FALSE:"
1821950,2019-05-20 16:26:52 UTC,"I've pushed a branch here, adding a new YAOUS, and modifying the volcopy editor's behavior to check the setting to determine whether or not to allow items with empty call number label boxes."
1821950,2019-03-27 18:55:33 UTC,"I think this should be a setting. Perhaps at the shelving location level, in the Shelving Locations Editor? That would allow finer control so that a library could require call numbers in some collections and not in others."
1821950,2020-02-26 00:39:00 UTC,I made the changes which were requested in this bug (now marked duplicate): https://bugs.launchpad.net/evergreen/+bug/1713164.
1821951,2019-04-15 14:28:12 UTC,That is not how I understand it. Once it is fixed in Gnome Nautilus won't have to misue the text clipboard so it will be fixed in Unity as well.
1821951,2019-04-01 12:16:28 UTC,Just read a bit more in the linked gitlab issue.
1821951,2019-04-01 20:28:06 UTC,Thanks Oliver.
1821951,2019-03-27 19:07:46 UTC,Not so sure this is an issue to be properly addressed in Diodon.
1821951,2019-03-29 16:51:26 UTC,There is no special types. It just appends protocol junk to file path as hence to diodon not a valid file path.
1821953,2020-04-10 13:51:19 UTC,"Thank you for your bug report. I'm not sure what the report is about, the fact that the name 'warty' is misleading there? It has been kept that way since we don't have a good way to migrate users upgrading, the content is changing every cycle but the name isn't"
1821953,2020-04-10 17:04:00 UTC,"OK, then this is not a bug, but a feature. Thanks for clarification."
1821955,2020-08-24 18:23:08 UTC,"Hi, sorry for getting back to you so late int the game."
1821955,2020-08-24 18:57:39 UTC,I will discuss in forum. You can close this.
1821956,2019-03-28 11:57:26 UTC,I understand the desire to support WSL but let one thing sink in: the snaps are not working *precisely* because the kernel layers is missing features.
1821956,2019-03-28 14:49:11 UTC,(I doubt that alone would be enough...)
1821956,2019-09-19 06:51:19 UTC,For WSL2:
1821956,2019-03-28 14:48:26 UTC,"For the mounting issue, try running snapd with SNAPPY_SQUASHFS_UNPACK_FOR_TESTS=1"
1821956,2019-03-28 11:44:20 UTC,@chipaca:
1821956,2019-03-27 19:54:45 UTC,How would bind mounts let you read a squashfs?
1821956,2019-03-28 11:14:26 UTC,"WSL also does not (last I checked) support GUI apps, nor daemons, or even ship systemd (not sure if systemd can run on WSL), nor udev, nor does apparmor work (does seccomp work?)."
1821956,2019-03-27 17:57:05 UTC,Snap command does not work either:
1821956,2019-03-28 11:41:04 UTC,@chipaca:
1821956,2019-03-28 10:36:02 UTC,"On Wed, Mar 27, 2019, 21:05 John Lenton <email address hidden> wrote:"
1821957,2019-03-27 19:00:25 UTC,The team only has access to two external screens connected via displayport.  They turned off the screen that did not have the locked dialog.  The other screen did not wake up - it remained locked.
1821957,2019-08-10 04:17:27 UTC,[Expired for Ubuntu Budgie because there has been no activity for 60 days.]
1821957,2019-08-10 04:17:28 UTC,[Expired for gnome-screensaver (Ubuntu) because there has been no activity for 60 days.]
1821959,2019-03-28 11:18:35 UTC,Why are you using snapd as a library?
1821959,2019-04-11 08:51:24 UTC,"It gets used for multiple projects that need assertions. The Serial Vault is one, and I'm also working on an agent that uses snapd API. The agent uses assertions as a part of the device identification with a cloud service."
1821959,2020-01-22 15:09:20 UTC,Any update on this? I have the same problem updating https://github.com/CanonicalLtd/serial-vault to the `go mod` and pin version of snapd
1821959,2020-01-22 15:43:33 UTC,"This should be fixed in recent snapd master, the PR that fixed this was: https://github.com/snapcore/snapd/pull/7634"
1821959,2020-01-22 16:55:12 UTC,Looks like it's fixed in https://github.com/snapcore/snapd/commit/4e8d74d5f6a37c31b48f0a34d5793d95e92db6c4 and awaiting release - thanks Zygmunt!
1821959,2020-01-22 16:56:00 UTC,"Apologies, I missed your update there Ian - thanks"
1821960,2019-03-28 02:31:42 UTC,Do you encounter audio stuttering in any other apps?
1821960,2019-05-27 04:17:34 UTC,[Expired for quodlibet (Ubuntu) because there has been no activity for 60 days.]
1821961,2019-04-24 07:39:21 UTC,This bug was fixed in the package linux - 4.15.0-48.51
1821961,2019-04-23 03:49:07 UTC,"Hey there, tested the proposed -48 kernel. Did 15 reboot cycles and everything started every time. Last time it succeeded approximately 90% of the time. That is whey I went to 15 this time. Seems good."
1821961,2019-03-27 19:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1821961,2019-04-04 18:04:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1821961,2019-04-19 20:25:56 UTC,"Hello all,"
1821963,2019-03-28 10:49:36 UTC,Thank you for your bug report. I'm trying to reproduce the problem. Is this the rally scenario you're running?
1821963,2019-03-29 15:07:24 UTC,Many thanks Bence for taking a look at the issue right away. The create_and_delete_subnets scenario has been working well for us as well. The test where I saw the issue was:
1821963,2019-05-29 04:17:21 UTC,[Expired for neutron because there has been no activity for 60 days.]
1821964,2021-02-11 09:40:09 UTC,Pushed up patch to add note to the docs: https://review.opendev.org/c/openstack/openstack-ansible/+/775085
1821964,2019-03-28 18:38:43 UTC,"I resolved this by removing the ""ceph_mons"" override"
1821964,2021-02-10 04:22:17 UTC,"I am having same issue with victoria and even i removed ""ceph_mons"" override it didn't help me"
1821964,2021-02-10 04:29:58 UTC,"nevermind in my case i had missing key, so i created manually on ceph-mons nodes"
1821965,2019-09-17 07:57:28 UTC,Migrated to https://github.com/widelands/widelands/issues/585
1821965,2019-04-02 20:15:02 UTC,"Ah, when removing the road between flag 18,14 and flag 16,14 one log is transported (goes to headquarters), the other log will still lay at the flag, although the previous removed road is build again."
1821965,2019-03-27 19:50:50 UTC,Another observation:
1821965,2019-04-02 19:46:30 UTC,"Somehow i managed to have two logs lying at flag 18,14 which get not transported anymore."
1821967,2019-08-01 20:27:38 UTC,This has hopefully been fixed in a number of small improvements made recently:
1821969,2019-05-08 01:12:07 UTC,A proposed fix is at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=55b14b6b37f6ad8879917593643876c8639db86b
1821969,2019-09-16 18:59:46 UTC,I've tested this patch and it properly displays the prefix and suffix (preferred when appropriate) in the patron summary.
1821969,2019-10-21 19:31:01 UTC,"Pushed to master, rel_3_4, rel_3_3, and rel_3_2 (3.1.x doesn't have the preferred name feature). Thanks, Garry and Michele!"
1821972,2019-03-29 14:07:01 UTC,Thanks for reporting the error.
1821989,2019-03-28 00:33:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1821989,2019-04-23 14:45:37 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1821989,2019-06-23 04:18:30 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1821990,2019-05-13 06:11:58 UTC,"Historically, the hacluster charm has been a bit of a special snowflake in that regards, simply as a matter of convenience. I doubt that we'd want to tie the TLS record creation to the hacluster charm."
1821990,2019-03-28 14:23:32 UTC,"Looks like hacluster charm has access to maas api.
https://bugs.launchpad.net/charm-hacluster/+bug/1764832"
1821990,2019-03-28 07:42:10 UTC,The charms don't have any kind of MAAS API access so that would be a difficult thing to achieve
1821998,2019-03-28 10:12:43 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1821998,2019-05-28 04:17:25 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1821999,2019-06-25 04:45:10 UTC,"Digging further into this, I am sure that the old contents were not used. However, since we identify cloud credential on the controller by cloud name, user name and credential name tuple, I am pretty sure that the actual cloud in this scenario would have been whatever cloud model is residing on."
1821999,2019-06-25 05:29:31 UTC,"Futhermore, if you managed to 'add-model' with '--credential' where credential name is the same as at bootstrap but the contents are different, I am not sure how you could add that model."
1821999,2019-06-25 14:27:11 UTC,Hi Anastasia. I don't have time to reproduce right now. I'll try to get back to this in the near future.
1822004,2019-03-30 22:33:49 UTC,"Note: it seems that probably after a reboot, snap resetted the AppArmor profile to the default, so breaking my dockerd installation. Therefore there is no really a work around and it requires a proper patch."
1822007,2019-03-27 23:35:28 UTC,This bug blocks the progress of completion of bug: https://bugs.launchpad.net/maas/+bug/1820983
1822007,2019-03-28 19:20:04 UTC,Seems that SUSE supports this in their grub because its well documented on their site:
1822007,2019-04-01 13:51:43 UTC,As a first step I'd look into whether grub is able to correctly get an IP from DHCP. I wonder if the client class string confuses it.
1822007,2019-04-08 16:49:58 UTC,Attached is the packet capture.
1822007,2019-04-18 16:22:28 UTC,"After additional testing with hardware (instead of in VMs), it looks like things are working fine on Lenovo hardware."
1822013,2019-04-01 11:37:30 UTC,This issue has been assigned CVE-2019-7305
1822016,2019-03-28 23:29:26 UTC,"I am not married to any specific implementation. My main goal with raising this bug, is to have Juju grow a means for LXD configuration to be applied to a deployed application in a way that suits environmental and user requirements, rather than assuming any and all LXD customisations can be forecast in the form of a per-charm hard-coded lxd-profile.yaml file, which is the current supported method (and is really useful, already, btw)."
1822016,2019-03-28 15:53:36 UTC,I just want to back John up on the principle side of it.
1822016,2019-03-28 14:03:42 UTC,"Working around a charm issue by *not fixing the charm* is not a feature we
really want to support. Because it just leads to fragmentation and nobody
else gets the benefit of the improvements you could have made to the
ecosystem."
1822016,2019-03-28 07:05:25 UTC,Encountered the same need for nested containers with Contrail charms as they deploy docker containers which either requires collocation on bare-metal or usage of kvm as standard lxd profiles do not allow nesting and we do not control the code base of the charm to modify its profile.
1822017,2019-03-28 18:35:17 UTC,"Thanks, what you ask for makes sense as actions normally fall outside the ""change the models"" route."
1822017,2019-03-28 21:27:41 UTC,"Hey @Rick, I had been talking with both James and Xav about this for a while. It is a simple task for us to do, and would have a high impact operationally, so I think we should get this in for 2.6."
1822017,2019-04-29 01:28:59 UTC,juju run-action is being modified to bypass blocking[0]. We're aiming to have this landed in a release candidate shortly.
1822020,2019-05-06 15:43:25 UTC,https://github.com/juju-solutions/layer-status/pull/14
1822020,2019-05-06 15:47:11 UTC,https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/10
1822020,2019-05-06 15:51:26 UTC,https://github.com/charmed-kubernetes/cdk-addons/pull/100
1822021,2019-07-30 19:38:24 UTC,Cherry-picked to stable:
1822021,2019-07-25 17:38:58 UTC,Follow-up bug to address the unnecessary writes:
1822021,2019-07-25 17:27:02 UTC,The original impl had to be partially reverting because we missed a few things in data_changed that kept us from writing an accurate kubeconfig:
1822021,2019-06-24 09:54:44 UTC,https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/33
1822023,2019-03-28 04:08:18 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1822036,2019-05-14 19:03:54 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1036.38
1822037,2019-03-28 07:08:25 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1822037,2019-03-29 03:22:05 UTC,This bug was fixed in the package ukui-screensaver - 2.0.5-0ubuntu1
1822041,2019-06-04 04:16:53 UTC,I can see that too.  Also in eeschema.
1822041,2019-06-04 08:49:45 UTC,This issue has diverged between master and 5.1. (The original reporter was on 5.1 and Oleg is on master)
1822041,2019-06-04 09:46:46 UTC,"We do not have a lot of available hot keys, so I am not thrilled by this idea, if it can be avoided."
1822041,2019-06-04 10:16:17 UTC,"@JP, this definitely relates to how the wxID_HELP events are generated and handled. From what I can tell, wxWidgets will generate this event for the program when specific actions are taken (one of which is pressing the ""help key"" on the system, which is usually F1 and doesn't seem to be user definable). This is unfortunately buried in the wxWidgets code, so the only way to deal with this is to disconnect the handler for wxID_HELP."
1822041,2019-06-04 12:31:06 UTC,"@Ian, try moving it to an ACTION (they don't have to have hotkeys), and then map wxID_HELP to the ACTION in TranslateLegacyId()."
1822041,2019-06-13 23:42:37 UTC,This was fixed by Jeff on master in this commit: 5e49517781705f11c4c046e13dac8815b535b2c5.
1822041,2019-06-12 01:03:39 UTC,This patch is for the 5.1 branch to make opening the help into an action with no hotkey. This disconnects the wxID_HELP event from all pcbnew/module editor/module viewer/gerview windows so that the F1 key no longer has a conflict.
1822041,2019-06-13 18:32:04 UTC,"@Ian, I merged your 5.1 patch into the 5.1 branch.  Thank you for your contribution to KiCad."
1822041,2019-06-13 20:19:32 UTC,Fixed in 71f5f96e64f84c6916e92941c05497c982943696
1822041,2019-04-20 22:35:34 UTC,"Commenting line 167 of pcb_edit_frame.cpp ""fixed"" this for me. Patch against the 5.1.0 tag:"
1822041,2019-06-04 15:01:34 UTC,"wxWidgets handles it's own internal command IDs (wxID_XXXXX) separately from user defined IDs.  This is to allow wxWidgets to handle platform specific short cuts for common command actions such as save, copy, help, etc.  If you choose to use a hotkey that is already assigned to one of the wxWidgets command IDs, you are always going to have this behavior because wxWidgets will intercept these IDs first.  This is described in the event handling overview in the wxWidgets documentation[1].  There are two ways to fix this.  Use a new help ID or change the zoom in hotkey to another key.  The latter still has a issue if someone decides to use the F1 key for something else."
1822041,2019-04-20 22:10:54 UTC,"Affecting me as well since 5.x on Arch Linux. I'm a heavy user of F1/F2 keys for zooming, so this is quite a nuisance."
1822041,2019-03-28 06:55:43 UTC,Forgot to add that it is Kicad version info:
1822041,2019-03-29 16:03:21 UTC,"Oh yeah, forgot about that."
1822041,2019-03-28 10:27:47 UTC,Please add the complete version information from Help->About KiCad->Copy Version Info.
1822041,2019-04-17 09:11:14 UTC,"I'm inflicted by the same bug! Didn't use to have it in previous versions, only since 5.x ( can't remember whether it was already with .0 or only after .1. Currently running .1 )."
1822041,2019-03-29 00:13:17 UTC,I just checked the other applications:
1822041,2019-03-29 02:30:54 UTC,"Fun fact: The ""View"" menu in all of the Kicad applications lists zoom in/out as ALT+F1 and ALT+F2.  In Linux Mint those hotkey combos are showing all the workspaces and showing the run bar respectively.  None of the Kicad applications respond to those hotkey combos.  I can't see in Mint's settings that either of those hotkey combos are actually map to any function though, and I have been through the list of hotkeys several times."
1822041,2019-03-28 15:21:31 UTC,"I added the version info to a comment last night.  Didn't realize at the time I was able to edit the original description, but now I have added the version info to the description as well."
1822041,2019-03-29 14:32:37 UTC,"I understand your comment about the number of window managers and hotkey conflicts. However, do you think it would at least be prudent to not conflict with the default hotkeys defined in the most popular Linux distro?  Maybe when the F1 issue is fixed the View menu options could drop the ALT modifier?"
1822041,2019-03-29 15:18:35 UTC,We have a lot of #ifdef's to make the zoom hotkeys and accelerators different on Mac. Also (side issue) the zoom in hotkey Cmd+ doesn't work (Cmd- for zoom out works fine).
1822041,2019-03-29 15:37:48 UTC,"Even though I'm already used to F1/F2 for zooming, I'm ok with the hotkey for zoom changing.  Personally though, I use the zoom hotkeys a lot.  I would assume the majority of users do, but I have no data to back that up.  With that said, I would like the hotkey to be something very convenient, without a modifier, and easy to locate on the keyboard without looking.  The ""-"" and ""="" (the Shift modifier for the ""="" key is ""+"") keys next to the Backspace key could fit this description if keeping F1/F2 is not an option.  I'm not sure where the number pad ""-"" and ""+"" fit in."
1822041,2019-03-29 16:00:10 UTC,Plain + and - without modifiers are already used for switching layers.
1822041,2019-03-29 13:14:21 UTC,The F1 key issue needs to be fixed.  There is not much we can do about keys grabbed by your window manager (Alt-F1).  You will either have to disable the key in your windows manager or change the key in KiCad.  There are so many windows managers on linux that there is almost no chance of no having a shortcut key conflict.
1822043,2019-08-08 06:59:18 UTC,"The patch has been upstreamed,
https://github.com/rhboot/shim/pull/182"
1822043,2019-03-29 03:50:45 UTC,"MokManager only uses the UEFI console interface.  If the UEFI text console API renders text too small to be legible, I think that should be considered a bug in the UEFI implementation, not a bug in MokManager."
1822043,2019-07-01 02:13:24 UTC,This is a pic take from a lenovo laptop with 4k panel
1822043,2019-07-03 04:48:01 UTC,This is the log of running uefi app.
1822043,2019-07-24 02:56:20 UTC,attached the test mmx64.efi
1822043,2020-04-09 02:22:45 UTC,"The patch has been accepted upstream, and already in the Ubuntu release."
1822046,2019-03-28 14:25:03 UTC,"Hi Massimiliano, seems this is being tracked upstream https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63578"
1822048,2019-03-28 08:03:31 UTC,Removing the array operator seems to fix the problem.
1822048,2020-08-28 05:41:04 UTC,The affects Ubuntu 20.04 too
1822048,2019-07-18 11:59:23 UTC,"The problem was finally easy to be fixed. As stated above, the problem is in cluster_view.php, line34. Just going to line 26 and substituting"
1822048,2019-07-18 11:14:03 UTC,I had the same problem. The upstream patch fixes it just partially. The view is not the way it should be.
1822048,2019-07-11 07:30:56 UTC,I have the same issue and the upstream patch fixes it.
1822048,2021-02-01 20:15:43 UTC,+1 for 20.04. Please patch this. I've wasted so much time thinking this was a configuration issue on my end.
1822048,2019-04-13 21:40:25 UTC,"Can confirm, applying the upstream patch fixes it. So, updating to the latest ganglia-web version would be nice."
1822048,2019-03-28 08:25:41 UTC,The previous patch had a problem on updating (and probably for multiple clusters). This one doesn't and this is what is in the upstream repo: https://github.com/ganglia/ganglia-web/blob/master/cluster_view.php#L25.
1822048,2019-03-28 08:24:17 UTC,"The attachment ""cluster_view.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1822048,2019-04-13 21:42:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822050,2019-03-29 01:03:09 UTC,I have encountered this as part of my --force remove-app and -unit work. I'll work on this as part of this enhancement.
1822050,2019-06-14 02:10:34 UTC,We are currently working in this area and are tracking progress via bug # 1831546. I'll mark this report as a duplicate.
1822052,2019-03-28 10:28:02 UTC,python-glanceclient version: stein
1822052,2019-04-09 16:44:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651325"
1822052,2019-04-09 16:49:00 UTC,"This makes sense,I proposed the above fix so that we can discuss it over a review :)"
1822052,2019-05-15 13:07:26 UTC,"Reviewed:  https://review.opendev.org/651325
Committed: https://git.openstack.org/cgit/openstack/python-glanceclient/commit/?id=d589aa257d3ab99a50444ff42f43b3b9d650d089
Submitter: Zuul
Branch:    master"
1822052,2019-09-13 14:59:16 UTC,This issue was fixed in the openstack/python-glanceclient 2.17.0 release.
1822053,2019-03-28 09:30:05 UTC,This change was made by a bot.
1822054,2019-09-30 19:45:32 UTC,"Reviewed:  https://review.opendev.org/643583
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=02bbc8bda563c904b5a5d753c5a80d1c92a70a6d
Submitter: Zuul
Branch:    stable/queens"
1822054,2019-09-23 19:22:35 UTC,"Reviewed:  https://review.opendev.org/643596
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=22e61c50b179f6f56e4a830625cd2d0154a3d02b
Submitter: Zuul
Branch:    stable/queens"
1822054,2019-07-31 21:46:16 UTC,"Reviewed:  https://review.opendev.org/643582
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ed9797c9a8f6260c3626224cc1139d611955323c
Submitter: Zuul
Branch:    stable/queens"
1822054,2019-07-26 17:54:55 UTC,"Change abandoned by James Slagle (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/643595
Reason: Abandoning this patch per the TripleO Patch Abandonment guidelines (https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html). If you wish to have this restored and cannot do so yourself, please reach out via #tripleo on freenode or the OpenStack Dev mailing list."
1822054,2019-09-17 22:10:46 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/643596
Reason: We are facing gate issue: https://bugs.launchpad.net/tripleo/+bug/1844446"
1822056,2019-03-28 09:31:07 UTC,Please:
1822056,2019-05-28 04:17:17 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1822059,2019-03-28 09:25:51 UTC,"Obviously, this is a problem with Gtk2 applications (see WinFF screenshot)"
1822059,2020-02-07 11:20:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822063,2019-03-29 17:58:35 UTC,"Hi David,"
1822063,2020-12-11 17:09:56 UTC,"I don't know this bug is related to my problem or not, unfortunately I cannot find out any workaround with my problem which is similar to this bug."
1822063,2019-04-09 14:38:21 UTC,See related:  https://bugs.launchpad.net/charm-keystone/+bug/1823743
1822063,2019-04-08 15:42:37 UTC,"Reviewed:  https://review.openstack.org/648448
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=299a9520031b1563be9c38218e8d352f1ed59832
Submitter: Zuul
Branch:    master"
1822063,2019-04-08 15:02:13 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/650919"
1822063,2019-03-29 20:21:42 UTC,"Ed, glad to hear it is working."
1822063,2019-03-29 18:04:09 UTC,Sorry should have clarified - by removing the auto-generate-root-ca-cert we're no longer hitting the race condition as you proposed - thanks again for the advice.
1822063,2019-03-28 16:52:07 UTC,Thanks for the quick response.
1822063,2019-03-28 22:08:10 UTC,"Ed,"
1822063,2019-03-28 16:16:16 UTC,"I have now reproduced it with the simpler bundle without SAML involved, but I'm going to have to hand this over to David Ames as I'm End of Day."
1822063,2019-03-28 16:26:42 UTC,We appear to be using soon to be deprecated testing settings. The auto-generate and unlock introduce the tls-certificate relation during deploy time. Which seems to have discovered a race condition.
1822063,2019-03-28 15:58:41 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/648448"
1822063,2019-03-28 15:33:50 UTC,"There is a small, unrelated, bug in the manger.py code in that it doesn't detect the socket closing and crashes out if a None is received from the uds_client.receive():"
1822063,2019-03-28 14:18:27 UTC,ok thanks - the first bundle (the big one) doesn't have keystone-saml-mellon involved yet though..... were you able to reproduce at all yet?
1822063,2019-03-28 14:09:53 UTC,"This also does not reproduce if I remove keystone-saml-mellon from your testing bundle, so I suspect it's related to the SAML integration bits."
1822063,2019-03-28 13:46:07 UTC,"mhm, my more basic bundle didn't hit that:"
1822063,2019-03-28 13:39:36 UTC,here you go:
1822063,2019-03-28 13:15:41 UTC,"Can we get a copy of this bundle, at least the parts including keystone and vault?"
1822064,2019-03-28 10:03:03 UTC,The bug breaks fakechroot command because mv command doesn't work with fake chroot environment anymore.
1822066,2019-03-28 10:22:05 UTC,"This doesn't affect 16.04.
It does affect 18.04 and 18.10."
1822066,2019-03-28 10:46:15 UTC,"Note that there's a different bug that also prevents you from importing `cec`:
https://bugs.launchpad.net/ubuntu/+source/libcec/+bug/1805620"
1822068,2019-05-29 04:17:20 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1822068,2019-03-29 08:02:19 UTC,"Hi Cr Viper,
Thank you for taking the time to report this bug and helping to make Ubuntu better."
1822068,2019-03-29 08:07:28 UTC,There would need to be better steps to rpreoduce the error at least.
1822069,2019-04-15 14:51:14 UTC,"What about Cosmic? Note that from SRU policy (https://wiki.ubuntu.com/StableReleaseUpdates), ""To avoid regressions on upgrade, any such feature must then also be added to any newer supported Ubuntu release."""
1822069,2019-04-29 03:38:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822069,2019-04-18 08:25:59 UTC,version in disco is the target one
1822069,2019-04-18 08:22:12 UTC,source package was renamed shibboleth-sp2 -> shibboleth-sp
1822069,2019-04-18 07:25:55 UTC,source package was renamed opensaml2 -> opensaml
1822069,2019-04-18 07:06:58 UTC,version in disco is the target one
1822069,2019-04-16 11:28:58 UTC,"On 16/04/2019 11.31, Robie Basak wrote:

>> Can you explain how the new soname is a problem? I think it
>> clearly separates the new and old libraries.
>
> We can't delete the old library from Bionic, so the new and old must
> exist concurrently. Therefore you can't just upload a replacement
> source package, because that would make a security fix or regular
> update for the old library impossible[1]. We call this situation
> ""NBS"", or ""not built from any source"". You'll need to create a new
> parallel source package with a different name (for example with a
> version number in it), so that's another whole bunch of renaming.
"
1822069,2019-04-16 09:31:40 UTC,"On Tue, Apr 16, 2019 at 07:23:36AM -0000, Etienne Dysli Metref wrote:

> On 15/04/2019 16.51, Robie Basak wrote:
> > I'm afraid that this is going to be too time consuming for me to
> > review - there seem to be additional complications the more I look
> > into it (eg. Cosmic and the new soname as you mention above). Based
> > on previous experience I think that the technical difficulties in
> > landing this safely to existing 18.04 users are going to overwhelm
> > the available volunteer time available from developers who are able
> > to review it.
>
> You are right that Cosmic must also be taken into account. However, the
> situation on Cosmic is much simpler: it already has the SPv3 stack so
> the upgrade would boil down to 3.0.2 -> 3.0.4. The only small issue it
> that Cosmic is still using the old package names with ""2"" in them (i.e.
> ""shibboleth-sp2""), but that can be dealt with Breaks/Replaces to ensure
> a smooth upgrade (as I've already done for Debian backports). Is there
> something else complicating the SRU for Cosmic you were thinking of?
"
1822069,2019-04-16 08:15:27 UTC,"Anyway, thank you very much Robie for your help so far! :D I really appreciate it."
1822069,2019-04-16 07:23:36 UTC,"On 15/04/2019 16.51, Robie Basak wrote:

> I'm afraid that this is going to be too time consuming for me to
> review - there seem to be additional complications the more I look
> into it (eg. Cosmic and the new soname as you mention above). Based
> on previous experience I think that the technical difficulties in
> landing this safely to existing 18.04 users are going to overwhelm
> the available volunteer time available from developers who are able
> to review it.
"
1822069,2019-04-10 12:20:00 UTC,"I've looked at the changes (git log) in opensaml2-tools and xml-security-c-utils to find out whether the programs they provide had changed, but apparently there are only internal changes, nothing changing the CLI. The man pages didn't change either."
1822069,2019-04-16 12:06:39 UTC,"[moving this thread over to ubuntu-motu@ from
https://launchpad.net/bugs/1822069]"
1822069,2019-04-09 07:30:27 UTC,"> I cannot further comment on the impact upon Moonshot-related packages, but I can ask their Debian maintainer if needed.
"
1822069,2019-03-28 12:03:24 UTC,"Package log4shib 2.0.0.-2 from disco builds without changes on bionic, tested with `backportpackage --destination=bionic --source=disco --build --builder=cowbuilder --key=0x6965D453D81531AD log4shib`."
1822069,2019-04-10 10:28:01 UTC,"Regarding #10:

> Usage of the libraries for other purposes is generally not supported.
"
1822069,2019-03-28 12:27:19 UTC,"Package xmltooling 3.0.4-1 from disco builds without changes on bionic, tested with `backportpackage --destination=bionic --source=disco --build --builder=cowbuilder --key=0x6965D453D81531AD xmltooling`."
1822069,2019-03-28 12:39:52 UTC,"Package opensaml 3.0.0-2 builds without changes on bionic, tested with `backportpackage --destination=bionic --source=disco --build --builder=cowbuilder --key=0x6965D453D81531AD opensaml`."
1822069,2019-03-28 13:27:01 UTC,Package shibboleth-sp 3.0.3+dfsg1-1 from disco needs a revert from debhelper compat level 12 to 11. No other changes are required to build on bionic.
1822069,2019-03-28 12:14:56 UTC,"Package xml-security-c 2.0.2-3 from disco builds without changes on bionic, tested with `backportpackage --destination=bionic --source=disco --build --builder=cowbuilder --key=0x6965D453D81531AD xml-security-c`"
1822069,2019-03-28 13:28:43 UTC,Would someone please review and sponsor this SRU?
1822069,2019-03-28 13:46:50 UTC,"The backported packages install and upgrade cleanly on bionic, tested with `piuparts -b /var/cache/pbuilder/base-bionic-amd64.tgz --distribution=bionic --keep-sources-list --arch=amd64 -D ubuntu --shell-on-error --single-changes-list log4shib_2.0.0-2~ubuntu18.04.1_amd64.changes xml-security-c_2.0.2-3~ubuntu18.04.1_amd64.changes xmltooling_3.0.4-1~ubuntu18.04.1_amd64.changes opensaml_3.0.0-2~ubuntu18.04.1_amd64.changes shibboleth-sp_3.0.3+dfsg1-1~ubuntu18.04.1_amd64.changes`."
1822069,2019-04-05 15:35:57 UTC,"For each of the packages for which you're proposing to do a major version bump, please could you explain what the situation is for existing users of that package on Bionic? Could there be users of these packages who are happily using them but will find the rug pulled out under their feet due to functionality or behaviour changes? What's the situation with the reverse dependencies of the packages you're proposing to update?"
1822069,2019-04-05 15:38:22 UTC,"To be clear, what I'm asking for is an analysis, per source package, that explains the different use cases that could be being used currently in Bionic, and how they will be affected by this proposed update. The use cases need to include direct uses, as well as use cases acting through reverse dependencies."
1822069,2019-04-08 09:47:50 UTC,"Hi Robie,"
1822072,2019-03-28 11:39:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822072,2019-03-28 11:40:11 UTC,"Confirmed, however, step 4 isn't accurate."
1822072,2019-03-28 14:15:12 UTC,"Thanks Popey, I've updated the description."
1822072,2019-03-29 02:21:12 UTC,"Reassigned to gnome-shell, which provides the GUI here."
1822072,2019-04-02 13:40:28 UTC,"This bug is being marked as notfixing for the Disco release.  This doesnt mean it won't get fixed, but it won't block release."
1822072,2019-04-02 13:44:49 UTC,"Setting to low, it's not an action users are going to do often and the workaround is easy. Would still be nice to upstream/get fixed though"
1822072,2020-01-24 09:42:24 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1822073,2019-03-29 02:31:54 UTC,I stand corrected. There is also ~/.config/pulse
1822073,2019-03-29 02:29:57 UTC,"AFAIK, only gnome-control-center has any memory of user preferences. So reassigning there."
1822073,2019-03-28 10:47:33 UTC,Added to Trello: https://trello.com/c/ckCJe76F/292-bug1822073-bluetooth-headset-profile-forgotten-after-disconnection
1822073,2019-03-28 13:50:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822074,2019-03-28 11:19:38 UTC,https://review.gerrithub.io/c/mfcloud/python-zvm-sdk/+/449152
1822077,2019-04-07 16:51:07 UTC,This looks like more of an issue with duplicity. Re-assigning.
1822082,2019-03-29 02:48:36 UTC,Please report this bug to the GNOME developers here:
1822082,2019-03-29 06:00:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822082,2020-01-24 09:43:16 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1822089,2019-04-24 17:16:05 UTC,apport information
1822089,2019-04-24 17:16:06 UTC,apport information
1822089,2019-04-24 17:16:08 UTC,apport information
1822089,2019-12-19 18:59:02 UTC,https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/90
1822089,2019-04-24 17:16:44 UTC,"Upgraded to 19.04, which has a kernel that works with the dock and attached the diagnostics."
1822089,2019-04-26 15:48:26 UTC,"Yes, will see if I can borrow a Windows laptop to do that.  How would I switch to hid-microsoft?"
1822089,2019-04-25 08:02:08 UTC,"Attaching the dmesg.log with dyndgg=+p Device that disconnected was ""Microsoft Comfort Curve Keyboard"""
1822089,2019-04-25 14:45:39 UTC,"I think the keyboard might want to use hid-microsoft. But before doing that, can you check if the TB16 has the latest firmware? You may need a Windows system to update the firmware."
1822089,2019-05-03 20:30:26 UTC,Having this same issue on my Dell Latitude 7490 with latest BIOS as of May 2nd (1.9.3). TB16 firmware is also up-to-date. If there is any info I can get from my system let me know. I'm willing to share any logs.
1822089,2019-12-19 17:40:42 UTC,I also experience this issue; you can find my dmesg log (with usbcore.dyndbg=+p) attached.
1822089,2019-04-25 05:01:23 UTC,"Please boot with kernel parameter ""usbcore.dyndbg=+p"", attach dmesg when the issue happens."
1822089,2019-04-24 17:16:04 UTC,apport information
1822089,2019-04-24 17:15:56 UTC,apport information
1822089,2019-04-24 17:16:01 UTC,apport information
1822089,2019-04-24 17:16:03 UTC,apport information
1822089,2019-03-28 12:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822089,2019-03-28 13:35:04 UTC,Dock is unusable with current Ubuntu kernel (screen locks up) as per https://bugs.launchpad.net/dell-sputnik/+bug/1752165
1822089,2019-04-24 17:15:50 UTC,apport information
1822089,2019-04-24 17:15:52 UTC,apport information
1822089,2019-04-24 17:15:49 UTC,apport information
1822089,2019-04-24 17:15:55 UTC,apport information
1822089,2019-04-24 17:15:57 UTC,apport information
1822089,2019-04-24 17:15:59 UTC,apport information
1822089,2019-04-24 17:15:59 UTC,apport information
1822089,2019-04-24 17:15:54 UTC,apport information
1822096,2019-04-02 08:51:36 UTC,"Interesting actually the new stack trace shows daemonStreamHandleWrite twice.
So it no more is the undefine call in this new code scenario."
1822096,2019-04-01 15:20:49 UTC,"Thanks to Michal I got the suggested d63c82df8b11b583dec8e72dfb216d8c14783876 as a fix.
This might need 4deed5f3c71f94acce387b68afbfc92911bf0a75 to backport.
Related is also a5445a3706b0bcbb6ec3f4f0f9e03b853ccf911b which also sounds close to the topic.
Essentially it is a 9 patch series and we can later check if/which subset we only need."
1822096,2019-04-02 08:43:06 UTC,First I made sure this really reproduces on libvirt 5.0 on x86 (we only had that combination on s390x before).
1822096,2019-04-02 08:46:15 UTC,I pinged upstream that this seems to be a different issue.
1822096,2019-04-02 08:54:13 UTC,"Silly me, the second thread obviously is on thread and not frame 5 :-)"
1822096,2019-04-03 13:36:51 UTC,"#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007f6adcbd2535 in __GI_abort () at abort.c:79
#2  0x00007f6adcc397b6 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6adcd5f952 ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
#3  0x00007f6adcc4060a in malloc_printerr (str=str@entry=0x7f6adcd61638 ""double free or corruption (fasttop)"") at malloc.c:5352
#4  0x00007f6adcc425a4 in _int_free (av=0x7f6ab0000020, p=0x7f6ab0022690, have_lock=<optimized out>) at malloc.c:4274
#5  0x00007f6adce923cb in virFree (ptrptr=ptrptr@entry=0x7f6ad765b6f0) at ../../../src/util/viralloc.c:581
#6  0x00007f6adcfabdc9 in virChrdevFDStreamCloseCbFree (opaque=<optimized out>) at ../../../src/conf/virchrdev.c:238
#7  0x00007f6adcebc839 in virFDStreamSetInternalCloseCb (st=<optimized out>, cb=cb@entry=0x0, opaque=opaque@entry=0x0, fcb=fcb@entry=0x0) at ../../../src/util/virfdstream.c:1444
#8  0x00007f6adcfabfaf in virChrdevFreeClearCallbacks (payload=<optimized out>, name=<optimized out>, data=<optimized out>) at ../../../src/conf/virchrdev.c:299
#9  0x00007f6adcec6f30 in virHashForEach (data=<optimized out>, iter=<optimized out>, table=<optimized out>) at ../../../src/util/virhash.c:575"
1822096,2019-04-03 11:02:42 UTC,"The locks we have seen are not the same (not both blocking on the same lock).
One is on the FDST (virObjLock)
And the other is on devs->lock of the virChrdevs
priv->devs->lock == fdst->icbOpaque->devs->lock, the assumption is that this is already held by the path undefine takes"
1822096,2019-04-03 11:32:43 UTC,"Michal might have already had that understanding, but for me it was worth to track that down.
The problem with the patch so far is that it allows priv->devs to go away and that is what is causing the issues with the patch applied (also as seen in comment #24 only one thread is left locking on the bad struct, but no two thread deadlock scenario anymore."
1822096,2019-04-03 12:46:06 UTC,"I had the simple suggestion of instead using this:
--- a/src/conf/virchrdev.c
+++ b/src/conf/virchrdev.c
@@ -310,8 +310,8 @@ void virChrdevFree(virChrdevsPtr devs)
     if (!devs || !devs->hash)
         return;"
1822096,2019-04-03 13:36:34 UTC,"Hrm with the latter is still crashes later on with a double free.
I wonder if we'd want a much higher lock that any of such paths would have to take.
Maybe a virObjectLock on the stream or so?
I'd leave that open for discussion as I'd be just doing trial and error which doesn't seem right.
I hope to find some more time the next days to look deeper into this ..."
1822096,2019-04-01 14:20:02 UTC,FYI info on all threads
1822096,2019-04-03 13:54:18 UTC,"I reported my findings upstream again, as I'm currently torn between trying a new debug session and implementing an upper lock level at streams (at least for all cleanup paths)."
1822096,2019-04-03 11:00:39 UTC,"There was another suggestion [1] but with it applied the case still hangs (after 12 and 1 iteration(s), so not much later than usual)."
1822096,2019-04-01 13:53:44 UTC,"Finally I seem to have found the way to make an example.
By using automated SIGINT I usually have it triggered in the first few runs, but since it is a race it might differ per platform."
1822096,2019-04-01 14:26:52 UTC,"Submitted upstream to get more eyeballs onto the problem
=> https://www.redhat.com/archives/libvir-list/2019-April/msg00080.html"
1822096,2019-03-29 16:40:38 UTC,"After adding some debugging messages to vm.py I can confirm the hang happens exactly when vm.undefine() is called at vm.py:445 [1]. But there's more: adding a debugging printout right before vm.undefine() prevents the hang from happening, confirming the idea you had since the beginning that the underlying problem is a race condition."
1822096,2019-04-01 11:59:27 UTC,"Thanks, even using that on the very same machine doesn't reproduce.
I pinged you to talk about early/late abort in your cases."
1822096,2019-03-28 12:16:27 UTC,Seems a deadlock on a futex
1822096,2019-03-28 12:16:49 UTC,"All threads are blocked lock related
  Id   Target Id         Frame
* 1    Thread 0x3ff9a75d130 (LWP 6518) ""libvirtd"" 0x000003ff9a011158 in __lll_lock_wait (futex=futex@entry=0x3ff8c017840, private=<optimized out>) at lowlevellock.c:46
  2    Thread 0x3ff956ff910 (LWP 6519) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e134) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  3    Thread 0x3ff94efe910 (LWP 6520) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e130) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  4    Thread 0x3ff946fd910 (LWP 6521) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e130) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  5    Thread 0x3ff8befc910 (LWP 6522) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e130) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  6    Thread 0x3ff93efc910 (LWP 6523) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e134) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  7    Thread 0x3ff936fb910 (LWP 6524) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e1d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  8    Thread 0x3ff92efa910 (LWP 6525) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e1d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  9    Thread 0x3ff926f9910 (LWP 6526) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e1d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  10   Thread 0x3ff91ef8910 (LWP 6527) ""libvirtd"" 0x000003ff9a011158 in __lll_lock_wait (futex=futex@entry=0x3ff74013180, private=<optimized out>) at lowlevellock.c:46
  11   Thread 0x3ff916f7910 (LWP 6528) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa4659e1d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  12   Thread 0x3ff8ad7f910 (LWP 6529) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa465eb550) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  13   Thread 0x3ff8a57e910 (LWP 6530) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa465eb550) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  14   Thread 0x3ff89d7d910 (LWP 6531) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa465eb550) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  15   Thread 0x3ff8957c910 (LWP 6532) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x2aa465eb550) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  16   Thread 0x3ff88d7b910 (LWP 6533) ""libvirtd"" 0x000003ff9a00d936 in futex_wait_cancelab..."
1822096,2019-03-28 12:17:37 UTC,"Maybe we can learn from the backtrace which lock and why:
The two main threads are #1 and #10, here their backtraces"
1822096,2019-03-28 12:18:32 UTC,"#1 is triggered via (it seems a guest goes away - qemu died and then cleanup runs after a write failed)
 daemonStreamHandleWrite (failing to write)
 -> daemonStreamHandleAbort (closing things and cleaning up)
    -> ... virChrdevFDStreamCloseCb
        virMutexLock(&priv->devs->lock);
        # priv = Domain's device information structure
        # client stream is client=0x2aa465d8f60
        # there would be code that is meant to avoid issues ""Unable to close"" if lock held
        # but the log doesn't show this"
1822096,2019-03-28 12:36:21 UTC,Thanks Christian for looking into it. The next time it happens I'll try to gather some more context and follow up.
1822096,2019-03-28 12:29:45 UTC,Based on UTAH code and on the assumptions made due to the debugging I created a test script that tries to trigger the cleanup being concurrent to the undefine calls.
1822096,2019-03-28 14:02:04 UTC,"@Paride
Could you make the test system use:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/stein-staging"
1822096,2019-03-28 14:15:39 UTC,"Sure, I'll try and report back."
1822096,2019-03-28 14:28:30 UTC,I've been able to reproduce the hang with libvirt-* installed from the stein-staging PPA. Once again it seems that having an open console to the VM when UTAH is interrupted is a relevant factor to reproduce the problem.
1822096,2019-03-28 14:44:47 UTC,It is reproducible even with all the packages grabbed from the stein PPA.
1822096,2019-03-28 15:57:11 UTC,"As just discussed, please add a few debug prints in utah so we can be sure if we are at [1] or somewhere else when you hit CTRL+C.
Please also check which code is run on CTRL+C (some cleanup maybe)?"
1822096,2019-03-28 14:00:25 UTC,"A debug log did not show a clear path further, but the idea came up that it might be related to either redirecting or attaching a console."
1822099,2019-10-19 09:20:58 UTC,"Reviewed:  https://review.opendev.org/670410
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=677bb330bf302649a85bb3ae590b61df0a045685
Submitter: Zuul
Branch:    stable/stein"
1822099,2019-11-12 11:32:49 UTC,This issue was fixed in the openstack/manila 8.1.0 release.
1822099,2019-09-26 19:50:24 UTC,This issue was fixed in the openstack/manila 9.0.0.0rc1 release candidate.
1822099,2019-03-28 12:39:04 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648387"
1822099,2019-07-11 22:46:13 UTC,"Reviewed:  https://review.opendev.org/648387
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=bc87926e60bca11a1bc91dfaadb8e571a38c0e5f
Submitter: Zuul
Branch:    master"
1822099,2019-07-11 23:05:20 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/670410"
1822103,2019-03-30 16:45:22 UTC,Also persists after purge and upgrade of different versions
1822103,2019-04-04 14:21:33 UTC,"Could you add the output of
$ udevadm info --export-db
$ sudo systemctl stop iio-sensor-proxy.service
$ G_MESSAGES_DEBUG=all sudo /usr/sbin/iio-sensor-proxy"
1822103,2019-06-04 04:17:29 UTC,[Expired for iio-sensor-proxy (Ubuntu) because there has been no activity for 60 days.]
1822106,2020-03-24 09:50:18 UTC,Can you please reword that and describe in more detail the problem you are seeing?
1822106,2020-03-24 09:54:02 UTC,Unless proven otherwise I will assume this is bug 1721988.
1822106,2020-05-24 04:17:17 UTC,[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]
1822108,2019-03-31 17:31:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822108,2019-04-06 00:37:46 UTC,I just spent some time tracking this down for a datacenter tech trying to do a fresh install:
1822109,2019-08-06 17:52:48 UTC,"Some news about that ""bug""."
1822110,2019-04-25 21:04:17 UTC,"This is available in cs:elasticsearch-36, currently in the candidate channel."
1822110,2019-03-29 13:19:00 UTC,MP: https://code.launchpad.net/~hopem/elasticsearch-charm/+git/elasticsearch-charm/+merge/365281
1822112,2019-03-28 15:13:59 UTC,I wonder if this is related to the grouping/sorting issues with browse described in bug 1467643
1822112,2019-09-13 20:59:46 UTC,Confirming (to a point) for 3.1.13; replicated following the steps above.
1822113,2019-05-24 14:06:32 UTC,"Perhaps something in common with
https://bugs.launchpad.net/openstack-ansible/+bug/1713663"
1822113,2019-06-27 08:14:48 UTC,"Just to tell that I have upgraded to Rocky, and the problem is still there."
1822113,2019-07-01 12:17:22 UTC,"Same issue in Gnocchi GitHub :
https://github.com/gnocchixyz/python-gnocchiclient/issues/102"
1822117,2019-06-28 07:21:47 UTC,"Addition of credential validity in 'show-model' and 'show-credential' output, develop: https://github.com/juju/juju/pull/10396"
1822117,2019-05-29 02:22:52 UTC,PR to reflect credential validity in model status and to show correct output in 'juju models' and 'juju status' against develop (heading into 2.7): https://github.com/juju/juju/pull/10249
1822117,2019-05-29 01:54:07 UTC,PR for 2.5: https://github.com/juju/juju/pull/10246
1822117,2019-05-24 07:51:01 UTC,PR for 2.6: https://github.com/juju/juju/pull/10228
1822117,2019-05-22 14:20:52 UTC,"+1, I think that this should be something that shows in the model status
output in the same place we show ""migrating/etc"" as well as the show-xxx
places noted above."
1822117,2019-05-28 01:50:40 UTC,Previously linked implementation was relying on status history to revert model status once the credential becomes valid. This is unreliable and undesirable. It was closed.
1822117,2019-05-21 06:05:08 UTC,"For 2.6, we will display in 'juju status' that model is suspended due to an invalid credential. Note that this will also mean that we'd need to check and update model status back to whatever it was before it got suspended when a credential validity is flipped back to 'valid'."
1822117,2019-04-02 04:05:00 UTC,See bug 1822637 for extra context.
1822117,2019-04-01 13:43:13 UTC,"> We do not use text from vendor's web site
"
1822117,2019-03-29 01:11:43 UTC,We do not use text from vendor's web site - this is our own copy of the text :) It is the most generic information that is worth providing without giving too much away in case the access was actually malicious. I would be very reluctant to re-word.
1822117,2019-05-21 06:06:21 UTC,"I have bumped it to a High since from user's perspective, there is no obvious way to determine at the moment that a model cloud credential is invalid and the model is suspended."
1822118,2019-09-25 08:43:43 UTC,"See above, I ran several thousand reboot tests on a lot of Basic_A3 instances, ranging from 50, 250 to 500 reboots.  Only one failed.  So this is *really* hard to reproduce."
1822118,2020-02-11 09:29:25 UTC,"@Finom, that's a good observation, much appreciated."
1822118,2020-01-06 20:54:55 UTC,"Hello,"
1822118,2020-01-06 20:45:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822118,2019-09-27 13:41:39 UTC,"@Joseph, so I can reproduce this hang/crash issue across a variety of instances. I can't get any info back on a console, so debugging this is not easy."
1822118,2019-09-27 13:40:32 UTC,And for Standard_D2s_v3
1822118,2019-09-27 07:37:37 UTC,Get more failures with Standard_B1ms
1822118,2019-09-26 14:01:03 UTC,So the best way to reproduce this issue is to run ~500 reboots across multiple instances rather than 5000-10000 reboots on once instance.
1822118,2019-09-26 13:59:31 UTC,I kicked off another ~20K reboot tests with Standard_B2S instances and hit hangs again:
1822118,2019-09-25 08:41:52 UTC,"IP addr	Mac Addr	Kernel	Reboots
13.64.67.186	00:0d:3a:3a:dd:04	5.0.0-1016-azure	50
104.42.152.115	00:0d:3a:35:b1:e6	5.0.0-1016-azure	50
65.52.121.205	00:0d:3a:3b:0f:52	5.0.0-1016-azure	50
13.88.28.42	00:0d:3a:3b:c7:da	5.0.0-1016-azure	50
40.118.165.237	00:0d:3a:3b:c2:4e	5.0.0-1016-azure	50
40.118.190.105	00:0d:3a:36:c6:d7	5.0.0-1016-azure	50
40.78.90.95	00:0d:3a:37:c0:d9	5.0.0-1016-azure	50
13.83.84.150	00:0d:3a:37:c0:15	5.0.0-1016-azure	50
104.42.74.129	00:0d:3a:36:c2:3e	5.0.0-1016-azure	50
40.85.154.162	00:0d:3a:37:cc:dd	5.0.0-1016-azure	50
40.78.43.4	00:0d:3a:37:c5:07	5.0.0-1016-azure	50
13.93.142.147	00:0d:3a:37:c8:5f	5.0.0-1016-azure	50
40.78.44.229	00:0d:3a:3b:e4:80	5.0.0-1016-azure	50
40.118.189.62	00:0d:3a:3b:e8:8e	5.0.0-1016-azure	50
40.78.85.10	00:0d:3a:3b:e6:37	5.0.0-1016-azure	50
40.78.13.203	00:0d:3a:3a:c2:b0	5.0.0-1016-azure	50
104.42.112.81	00:0d:3a:30:71:fb	5.0.0-1016-azure	50
40.80.156.132	00:0d:3a:30:2f:7c	5.0.0-1016-azure	50
13.64.173.138	00:0d:3a:30:73:b2	5.0.0-1016-azure	50
13.64.189.105	00:0d:3a:30:a4:6f	5.0.0-1016-azure	50
13.64.189.127	00:0d:3a:30:a4:1f	5.0.0-1016-azure	50
104.45.237.232	00:0d:3a:32:1e:3b	5.0.0-1016-azure	50
104.42.233.11	00:0d:3a:32:34:68	5.0.0-1016-azure	50
104.42.233.20	00:0d:3a:34:ed:42	5.0.0-1016-azure	50
23.101.202.206	00:0d:3a:32:32:b0	5.0.0-1016-azure	50
104.42.233.18	00:0d:3a:34:ee:ba	5.0.0-1016-azure	50
104.42.233.151	00:0d:3a:34:e9:0d	5.0.0-1016-azure	50
104.40.51.248	00:0d:3a:32:27:c6	5.0.0-1016-azure	50
104.40.69.158	00:0d:3a:34:f1:5d	5.0.0-1016-azure	50
52.160.41.95	00:0d:3a:35:9f:c8	5.0.0-1016-azure	50
104.42.158.74	00:0d:3a:34:c7:91	5.0.0-1016-azure	50"
1822118,2019-09-18 13:57:45 UTC,"@Joseph, any ideas how we can progress on this?"
1822118,2019-03-28 18:37:25 UTC,"So I don't think this is a kernel related issue.  The error message ""error while loading shared library"" is being emitted from the libc ""fatal_error"" shared library dynamic loader from init and an exit() is being called, causing the kernel to report that init has exited, which leads to the stack dump and the shutdown failure."
1822118,2019-05-07 12:42:01 UTC,"I can confirm this bug. My VPS servers are configured to automatically reboot daily and one of them started hanging up with similar error a few days ago. I am using Ubuntu 18.10 x64 running on Vultr VPS. When the VPS hanged today, the screen ended with these messages:"
1822118,2019-04-25 23:58:23 UTC,"I still haven't been able to reproduce this.  If you can reproduce this easily, maybe I can provide some kernels to be tested?"
1822118,2019-04-03 17:00:41 UTC,I modified your script to perform 5000 reboots.  I'm up to 3508 reboots now without hitting the bug.  I'll let it run for a while longer.  I'll also compare our environments to see if there is a difference.
1822118,2019-03-29 15:27:15 UTC,"Thanks Sean and Colin!  I'm going to see if I can reproduce it.  If I can, I do the usual investigation to see if its a regression, fixed upstream and if a bisect will help."
1822118,2019-03-29 02:25:40 UTC,"Hey Joe, Please see attached.  Simply update the system variable with the username@ip  and run it."
1822118,2019-03-29 00:47:15 UTC,"@Sean, can you add the info for Joseph?"
1822118,2019-03-28 21:48:55 UTC,Are you able to share the script that reporduces this bug and bug 1822133?
1822118,2019-03-28 18:18:26 UTC,Minor note: this appears to be a kernel panic during shutdown rather than a boot hang issue.
1822118,2019-09-20 09:05:38 UTC,"@Robert, was there a specific class of virtual machine you were using when this issue occurred?"
1822133,2019-05-31 03:02:20 UTC,"I rebooted our VM over 60 times today without any further issues. Since the VM network went down before I restarted the VM or lost access to the serial console login, I'm also thinking now it was a network issue to begin with. It could always be coincidence that I was able to get the VM back by force stopping and then starting the vm from a stopped state, when neither restarting nor redeploying helped, but there is one thing, correct me if this is wrong, that is different about force stopping and that is it deallocates the VM. If the network issue were internal to the VM I wonder if both restarting and redeploying could have with the best of intentions persisted the faulty network state to the point where the operations failed, while dealocating ended the issue and the VM was able to start over clean."
1822133,2019-05-31 04:23:32 UTC,"@Dexuan, the error 'WARNING ExtHandler CGroup walinuxagent.service: Crossed the Memory Threshold' started when the vm was first created on May 24, persisted until I stopped/dealocated the VM, and has not returned in syslog. Nor for what it's worth has this error been seen in over six months on another Ubuntu 18.04 VM we have."
1822133,2019-06-12 17:33:47 UTC,It looks like people are resolving this by upgrading to latest Disco with 5.0.0-1007.7 kernel?
1822133,2019-06-12 17:47:13 UTC,"@tom-wilberding  Hey Tom, are you able to capture the console logs of the instance when this occurs?"
1822133,2019-06-12 18:30:59 UTC,"@sfeole, checking with our devops folks. I don't have Azure access to the hosts in question."
1822133,2019-06-17 17:06:27 UTC,"@rnsc:  Can you please share the VM's full serial log, which can be obtained from Azure portal's Boot Diagnostics -> Serial log?"
1822133,2019-06-17 13:47:25 UTC,"@rnsc, what kernel were you using?"
1822133,2019-09-06 06:11:35 UTC,"Hi,"
1822133,2019-09-06 06:40:37 UTC,@Vald: This is from your attachment:
1822133,2019-09-06 21:09:39 UTC,"""ip: frags: fix crash in ip_do_fragment()"" is in 4.15.0-1057 in proposed right now for a separate issue."
1822133,2019-12-06 23:10:55 UTC,"Indeed, the commit is in in 4.15.0-1057 and has been released. Marking this bug as fixed released."
1822133,2019-06-17 06:54:32 UTC,"Hello, I noticed the same behavior on one of my Azure VM.
It wasn't rebooted thought, it just started blurting out ""hyperv_fb"" errors in a loop. (that's all I could display in the Serial Console on Azure, even sending SysRq to reboot the machine wasn't doing anything, I was forced to de-allocate my VM."
1822133,2019-05-30 13:18:19 UTC,"On 5/29/19 6:58 PM, Sean Feole wrote:

> I revisited this particular problem today. I ran a series of restart
> tests across westus2 and westus,  utilizing the same instance and
> series, but with the latest kernel in -proposed.  I was unable to
> reproduce this problem as originally reported in the bug. I also have
> not seen any of our SRU testing stall due to problems of this nature,
> where the instance fails to respond after a restart.
>
> I think it's safe to say we can close this bug and mark it resolved for
> the time being.
>
"
1822133,2019-05-30 23:45:13 UTC,I tried to reproduce the bug but couldn't.
1822133,2019-05-30 07:39:32 UTC,"I got the VM back by force stopping, then starting. It looks like 5.0.0-1007.7 only comes with 19.10, which is not available yet on Azure?"
1822133,2019-05-30 06:40:30 UTC,How do I upgrade the kernel to 5.0.0-1007.7 if that is what is recommended to avoid this issue? apt-get dist-upgrade on another vm with 4.18.0-1018-azure did not upgrade the kernel. Thank God it restarted! Or is  5.0.0-1007.7 not an Azure kernel so I would need to switch to stock Ubuntu kernel?
1822133,2019-05-30 06:33:04 UTC,@Dexuan I emailed you my serial log. I restarted via portal a number of times without success. I tried to redeploy twice and it failed. Trying to restart via cli now.
1822133,2019-05-30 06:12:31 UTC,@Kirk: I suppose you can get your VM back by Restarting the VM by force via Azure Portal (or Azure cmd line)?
1822133,2019-05-30 06:04:24 UTC,"@Kirk: Can you please share the VM's serial log, which can be obtained from Azure portal's Boot Diagnostics -> Serial log?"
1822133,2019-05-30 05:54:32 UTC,kernel is 4.18.0-1018-azure
1822133,2019-05-30 05:49:19 UTC,This bit me tonight on a few days old 18.04 VM with stock kernel. So far I can not get back in with reboot or redeploy to upgrade the kernel.
1822133,2019-05-30 01:25:10 UTC,It's glad to see the issue can not repro with the 5.0.0-1007.7 kernel.
1822133,2019-05-30 00:59:25 UTC,Test Parameters for comment #4
1822133,2019-05-30 00:58:10 UTC,"I revisited this particular problem today. I ran a series of restart tests across westus2 and westus,  utilizing the same instance and series, but with the latest kernel in -proposed.  I was unable to reproduce this problem as originally reported in the bug. I also have not seen any of our SRU testing stall due to problems of this nature, where the instance fails to respond after a restart."
1822133,2019-03-28 19:33:24 UTC,"walinuxagent is a package from the Ubuntu repository, but the upstream is here: https://github.com/Azure/WALinuxAgent"
1822133,2019-03-28 19:00:42 UTC,"I believe the ""ERROR ExtHandler /proc/net/route contains no routes"" is from the ""Azure Linux Agent"", so that's proprietary code that I don't have any idea how or why it is emitting that message."
1822133,2019-03-28 18:54:46 UTC,"The ""hyperv_fb: Unable to send packet via vmbus"" message is from synthvid_send(), drivers/video/fbdev/hyperv_fb.c (the Microsoft Hyper-V Synthetic Video Frame Buffer Driver). This error occurs when vmbus_sendpacket() fails to send a packet via the write ring buffer (see hv_ringbuffer_write())"
1822133,2019-05-30 07:52:28 UTC,"I see now 5.0.0-1007.7 is also available for 19.04, but I'll wait and see what you advise @Dexuan after looking at my serial log."
1822135,2019-05-28 17:49:57 UTC,It turns out we already have a backlog spec for implementing this:
1822135,2019-04-02 14:47:53 UTC,"++ on CADF notifications, which have an ""eventTime"" field which would specify in this case the time the project was created and by which user."
1822135,2019-03-29 14:36:45 UTC,"although through the log we can get the create time, it is hard to get a audit report through the regular project rest api. To get the create time, we have to dump the large quantity of logs which can make trouble in tow ways. One hand the log will not be constraint so it might be lost, the difficulty on getting the property will make the advanced operation impossible like sorting the project created from a to b. So, i do think adding project create time is quite necessary."
1822135,2019-03-29 08:15:16 UTC,What do you use the creation time for?
1822135,2019-04-02 14:32:23 UTC,Creating a project also emits a CADF notification which can be consumed by things like ceilometer:
1822157,2019-04-23 14:42:58 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1822157,2019-06-23 04:18:28 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1822158,2019-03-31 20:00:26 UTC,I'm also seeing this.
1822158,2019-04-01 12:07:01 UTC,Was the PL Editor included in the GAL-ification? I didn't think it was.
1822158,2019-05-13 13:21:21 UTC,This appears to be fixed in 5.1.2
1822161,2019-08-05 16:13:15 UTC,It’s not nonsense if you want to generate assembly drawings from the silk layer.
1822161,2019-08-21 18:03:56 UTC,See also: https://bugs.launchpad.net/kicad/+bug/1660148
1822161,2019-08-08 15:51:42 UTC,+1
1822161,2019-08-08 15:23:47 UTC,This seems like a valid solution to me.  At least it will be clear as why you would want to use it.
1822161,2019-08-08 13:28:09 UTC,Thanks JP!  What do people think about the following course of action:
1822161,2019-08-08 12:07:24 UTC,In fact this option has changed over the years and commits from contributors.
1822161,2019-08-05 16:36:35 UTC,"@Jeff-  Wow, I completely misunderstood what that option does."
1822161,2019-08-05 14:39:37 UTC,Including the silk layer in pads is complete none-sense (according to IPC which is kind of the authority with regards to footprint handling.)
1822161,2019-08-08 13:53:55 UTC,"- Option to substract soldermasked areas from silkscreen already exists (in Gerber format)
- Add option to plot pads onto a technical layer (from a dropdown) to replace the current option looks good to me."
1822161,2019-08-03 03:51:46 UTC,"OK, so the code performs what the OP thought."
1822161,2019-08-03 03:37:10 UTC,So the tooltip suggests it's supposed to do what the OP was looking for.  It doesn't.
1822161,2019-03-29 09:11:49 UTC,"@Hari, yes you have misunderstood the purpose.  I think Seth's comment points to terminology which would be clearer: we should rename the option ""Subtract pads from silkscreen""."
1822161,2019-03-29 05:47:06 UTC,"Hi seth,
I did not mean silkscreen line covers the pad.I meant i want the pad area to be printed on the silkscreen layer (for documentation pupose)."
1822161,2019-03-29 03:22:44 UTC,Hi Hari-
1822161,2019-08-03 03:54:49 UTC,"(BTW, if the above is the case and you want to produce assembly drawings, then just edit the pad definitions to include the silk layers you want them on.)"
1822161,2019-03-29 01:05:38 UTC,"I did not select 'exclude pads from silkscreen'. I've mentioned clearly, 'When i uncheck 'Exclude pads from silkscreen' and export pdf or gerber i am not getting pads on silkscreen layer'"
1822161,2019-03-28 23:27:10 UTC,Maybe the oxford dictonary definition makes it even clearer: https://en.oxforddictionaries.com/definition/exclude
1822161,2019-03-28 23:24:22 UTC,"What? You select ""exclude pads from silkscreen"" but still expect pads on silk? There is a contradiction here."
1822164,2019-03-29 14:32:49 UTC,"Could this be accomplished using the ""--custom-filters"" parameter for action_trigger_runner.pl?  Possibly by using different files for different cron jobs."
1822164,2019-03-29 16:35:40 UTC,"When I looked into this sort of thing a while back, I couldn't figure out how to create a custom filter expression that could join in other tables.  It seems like you can only effect the where clause, which can only act on data in the event target table.  So for overdues that would be the action.circulation data."
1822165,2019-03-28 17:34:41 UTC,"Acknowledging the bug, but marking ""invalid"" for chromium as this would have to be fixed in snapd. Added a snapd task for that."
1822165,2019-03-28 17:31:49 UTC,"When run from a terminal, the following message gives a clue:"
1822168,2019-03-31 05:50:54 UTC,"Could you provide a build log as proof that the Ubuntu change is obsolete, and resubscribe the sponsors team?"
1822180,2019-03-28 19:00:24 UTC,This change was made by a bot.
1822181,2019-04-19 07:27:50 UTC,"So, I Loaded up 19.04, didn't take too long, and, the result was identical, still doesn't work, still the same symptoms. For me, this is with nvidia 418 driver, my card doesn't work with 415 driver since it's an RTX2060. For me, xrandr -q shows all devices except the second monitor, it doesn't show at all, in my case, this is DP-2, not even listed. It's MIA from xrandr. However, it shows in nvidia-settings. Just like CJS says though, I can xrandr -display :0.1 and it does show and even says connected."
1822181,2019-07-22 18:27:00 UTC,I am VERY interested in continuing work on this.  I'm now running 19.04 and the problem persists.  I cannot change the status so please update it.
1822181,2019-07-22 04:26:14 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1822181,2019-04-30 15:48:48 UTC,"As previously reported, I've tried a number of different Nvidia and the X.Org drivers with no better results."
1822181,2019-04-29 22:59:08 UTC,I can't imagine that this bug has anything to do with xfwm4 or Xfce in general.
1822181,2019-04-20 19:05:05 UTC,"Definitely works with 18.04 xubuntu, got it working immediately with the same config, same nvidia driver, etc. Wanted to make sure nothing real recent, like within months, may have broken it. So, I agree that there was a change made that breaks it in 18.10+."
1822181,2019-04-19 16:54:46 UTC,"Steve, thanks for looking into this with 19.04.  I wasn't expecting that it would improve things, but I decided that if I was going to pour more effort into this, U would wait for the next OS release."
1822181,2019-04-19 08:31:38 UTC,"Wish I could delete that post! I saw the latest posts as 2019, but the bug was 2011. This worked long after that."
1822181,2019-04-19 08:08:59 UTC,I wonder if it has to do with this change:
1822181,2019-04-18 22:15:02 UTC,Thanks Steve.
1822181,2019-04-20 20:24:21 UTC,"Steve, I also made an earlier report to Nvidia regarding this.  You might consider adding a comment at the following link in order to prod more discussion and involvement there as well.  Regards."
1822181,2019-04-18 16:52:17 UTC,"Steve, glad to see that there is someone else with this problem, but sorry that you are also experiencing the difficulties."
1822181,2019-03-28 20:24:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1822181,2019-03-28 21:10:13 UTC,This is an automated message:
1822181,2019-04-18 19:56:18 UTC,"19.04 is released as of yesterday I think, that's why I shall test it hopefully today or tomorrow. Save yourself some time, I will do so."
1822181,2019-04-02 21:05:05 UTC,Any takers?
1822181,2019-03-28 21:11:24 UTC,"Not sure that this is the correct package, but it's a starting point."
1822181,2019-04-04 16:38:54 UTC,Is there anyone else in the Xubuntu world running a dual monitor dual desktop configuration?
1822181,2019-04-18 05:50:40 UTC,"I have the exact same issue in the exact same way, been struggling to make it work and it simply does not. It did work in previous xubuntu versions, but not 18.10, something broke it."
1822181,2019-04-18 08:59:58 UTC,"As mentioned before, please test with Xubuntu 19.04."
1822181,2019-04-18 13:25:02 UTC,"I will test with 19.04, but if it does not work, then, I am going to format and load 18.04."
1822181,2019-04-03 20:44:01 UTC,My suggestion would be to test with Xubuntu 19.04 Beta.
1822182,2019-04-02 16:24:38 UTC,"Reviewed:  https://review.openstack.org/648143
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=aee3ef71d91e89096fc8e6c45708c994b243d8fc
Submitter: Zuul
Branch:    master"
1822182,2019-04-03 09:25:41 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/649543"
1822182,2019-04-03 16:11:18 UTC,"Reviewed:  https://review.openstack.org/649543
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=1060782cbfd365f1ffeb3d419e27d43fd6ca359e
Submitter: Zuul
Branch:    stable/rocky"
1822183,2019-07-03 23:24:56 UTC,It would be extremely nice to have this feature in 5.x branch.
1822183,2019-04-07 16:43:12 UTC,Synchronized master. Rebuilt kicad. It turned out great. I see did not add buttons and fields. Still got comfortable. You can even form the skeleton of the component pins. Thank!
1822183,2019-04-05 17:53:27 UTC,"Fixed in revision d928aa9780299875a470c2068ee434e78dbc1337
https://git.launchpad.net/kicad/patch/?id=d928aa9780299875a470c2068ee434e78dbc1337"
1822183,2019-04-06 05:16:32 UTC,Good! I will wait kicad 5.1.1 release. Thanks!
1822183,2019-03-31 06:55:45 UTC,"please keep it at one distinct request/report per topic. Don't convert this bug into ""everything that is wrong with the pin table editor""."
1822183,2019-03-29 03:54:56 UTC,I would also add the length of the pins and the size of the fonts and the possibility of horizontal scrolling if the table is too wide.
1822183,2019-03-28 19:14:12 UTC,Add auto increment when adding new pin and use previously set pin type and direction
1822183,2019-03-31 07:30:41 UTC,Okay. I try
1822184,2019-03-28 20:23:42 UTC,"The attachment ""makes clear_console switch to either tty6 or tty5 instead of tty1/tty2"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1822184,2019-03-29 03:12:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822184,2019-04-04 06:49:13 UTC,This bug was fixed in the package bash - 5.0-3ubuntu1
1822184,2019-04-04 15:56:45 UTC,Thanks!  This also affects 18.04 and will need to be fixed there too please.
1822187,2019-06-26 19:54:23 UTC,I'm in agreement with Rene on most of this.  What's left should be handled by the grid and setting a local origin.
1822187,2019-03-30 08:25:08 UTC,Okay
1822187,2019-03-29 23:44:46 UTC,please keep it at one request or bug report per topic. Meaning open a new bug for your last response.
1822187,2019-03-29 17:01:05 UTC,"When I click the ""Change cursor shape"" button, the axes on the canvas disappear in the eeschema component editor"
1822187,2019-03-29 16:58:32 UTC,"Thanks for the information! I tried. Up to this point I was not aware of this. Indeed, it allows you to measure the scattering between two points. But. All elements are drawn in relation to the nodes of the grid or just the grid. Whether it is a seat or a conditional graphic designation of an electronic component. In this case, it is necessary to measure the distance in relation to the grid, that is, the cursor should always be attached to the grid when it is free, that is, when it does not move an element, does not place it from the library, or when a measuring tool is used (in this case, you can put which binds the cursor to the grid or disables this functionality) and so on.
I also noticed a strange thing in the eeschema component editor: the crosshair on the canvas disappears. If this is due to an increase / decrease, or is due to the button “Change cursor shape”. You press it - nothing happens. The shape of the cursor does not change."
1822187,2019-03-29 03:30:57 UTC,"Meet the expectations. I have not yet made the components in the footprint editor in version 5. Why they did not make the measure tool in the eeschema component editor, simple enough, not as visual as in pcbnew and the footprint editor. To help with balancing the location of the pins and the rest of the components of the circuit component."
1822187,2019-03-29 07:47:23 UTC,"In order for the circuit element to appear normally in the eeschema grid, it must be done in the eeschema component editor with the same grid parameters. Roulette is needed here to clearly observe the distance between the pins for visual convenience of perception. Some people still follow the standards because they are accustomed to them as in the perception of the proportions of the elements on the diagram. There is still a moment - printing schemes and requirements for the implementation of elements according to standards. There is another point - the center of the canvas. When inserting a component from the library, its position is taken into account apart from the center of the canvas of the component editor. The simplest roulette should be provided - a line connecting two points. Below the panel will display its length. And in general, wherever lines are drawn, it would be nice if the length and angle of the current segment of the line being drawn are displayed on the panel below.
And I also think that in order to eliminate the mismatch of the parameters of the eecshema grid and its component editor, the component editor should take the grid settings from the eeschema grid settings. Similarly for pcbnew and footprint editor. This option should be editors settings."
1822187,2019-03-29 06:57:33 UTC,"Footprints or anything on the pcb really need to be able to be made to measure. (Footprints to ensure the component fits onto the designed land pattern, the pcb itself to ensure it fits into a housing.)"
1822187,2019-03-28 23:38:41 UTC,@Rene I think he misses it in Eeschema and symbol editor (guessing from title)
1822187,2019-03-28 23:11:25 UTC,pcb new and the footprint editor have the measure tool since version 5. Did you miss it or does it for some reason not fulfill your requirements? (If it is the later then detail how its current behavior differs from what you expect.)
1822187,2019-03-29 10:04:04 UTC,"FYI if you press the spacebar it will reset the 'dx' and 'dy' coordinates in the bottom ""status bar"" to zero at the current cursor position, so you can use this for measuring point to point distances."
1822190,2019-04-09 16:40:54 UTC,Maybe we are talking past one another.
1822190,2019-04-09 16:46:55 UTC,Marking this bug as Triaged.
1822190,2019-04-09 16:19:16 UTC,"From a user perspective, goal state isn't providing any new functionality
here. There are no new use cases. It's just an implementation detail that's
part of a fix for something that's broken."
1822190,2019-04-08 15:57:21 UTC,"The heat charm also has a post-deployment action which has been required for quite some time.  With Juju goal state now being a feature, we can revisit this bug, and other areas where ultimate state was not predictable from an individual charm application perspective.  In the mean-time, this is the established method to address this type of issue where very serious and impactful race conditions would otherwise exist."
1822190,2019-04-08 16:17:15 UTC,"I respectfully disagree that this is a feature request; it is not enabling
any new functionality."
1822190,2019-04-09 16:10:17 UTC,"The fix is to leverage a feature in Juju which did not previously exist:  goal state.  To-date, goal state has not been widely adopted or developed within charms.  From that perspective, I'm holding the line that it is charm feature work."
1822190,2019-04-08 16:12:16 UTC,"I forgot to add initially, on the topic of juju-wait:"
1822191,2019-03-29 23:55:04 UTC,*** This is an automated message ***
1822204,2019-06-07 21:05:00 UTC,Thank you. I have notified our testing team to take care of this.
1822204,2019-07-12 07:49:49 UTC,"Hi Maher, in general all those questions/reports would be new bugs as it is not reopening or advancing this old bug. Giving you an answer now, but for the future it would be great if you could open new bugs for those."
1822204,2019-07-12 02:54:37 UTC,folks how can i update to open-vm-tools 10.3.10 ... when installing Ubuntu i only get version 10.2.0 and there is no online updates
1822204,2019-06-17 08:53:09 UTC,This bug was fixed in the package open-vm-tools - 2:10.3.10-1~ubuntu0.18.10.1
1822204,2019-06-17 08:44:19 UTC,This bug was fixed in the package open-vm-tools - 2:10.3.10-1~ubuntu0.18.04.1
1822204,2019-06-17 08:43:13 UTC,"The verification of the Stable Release Update for open-vm-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822204,2019-06-13 08:15:29 UTC,"Thanks Yuhua for pushing that through your tests.
Marking as verified"
1822204,2019-06-12 08:06:08 UTC,open-vm-tools 10.3.10 from -proposed works well in Ubuntu 18.04 Desktop and ubuntu 18.10 Server
1822204,2019-06-11 09:12:44 UTC,"Thanks Oliver!
Waiting for their reply then ..."
1822204,2019-06-07 20:50:47 UTC,"Hello Oliver, or anyone else affected,"
1822204,2019-06-07 20:48:52 UTC,"Hello Oliver, or anyone else affected,"
1822204,2019-05-17 06:10:12 UTC,Pushed to SRU team review - once in proposed I'll get into contact with VMWare to verify it on those releases as well (as usual).
1822204,2019-05-14 06:56:47 UTC,"open-vm-tools 11.0 will be too late this cycle (mid September), therefore in our ""one MRE per cycle"" approach to ensure the latest LTS stays up to match hypervisors we will backport 10.3.10 now."
1822204,2019-04-08 09:50:31 UTC,"I talked to the security Team (Marc), they said for the SRU our usual timing is enough as there is a another layer of protection against those kind of attacks. Therefore the bug will stay open for a while unless discussed otherwise."
1822204,2019-04-05 13:31:53 UTC,"Hi,
I try to remember the release notes, but my feeling here was they are too long for a bug description."
1822204,2019-04-05 11:10:07 UTC,"One request (not essential for now): In future, could you paste release notes into the bug so that I can see them without opening a link? :-)"
1822204,2019-04-05 10:54:22 UTC,"Ok, I see it in [1] disco-unapproved - up to the release team now to let it in (or not)."
1822204,2019-04-05 10:46:20 UTC,Reviewing the changelog after talking to Bernd (thanks) I realized that there are security critical issues in there.
1822204,2019-03-29 06:24:42 UTC,"Thanks Oliver, this will be to be considered for 19.10 then"
1822207,2019-03-29 05:18:15 UTC,"Just a short note that when using rclone, no problems occur - I was able to sync 1.7TiB of data without issue, which included over 1 million files."
1822213,2019-04-01 23:12:15 UTC,The MAAS user is unable to read any other users SSH keys. Even if it could in an HA environment every rack controller would need to have access to the key. However we should be able to add support to talking with virsh with an SSH key only.
1822216,2019-03-29 10:47:02 UTC,Kind of a duplicate of https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1433761
1822217,2019-04-03 12:52:13 UTC,"Thanks, please let us know what you find."
1822217,2019-06-03 04:17:24 UTC,[Expired for clamav (Ubuntu) because there has been no activity for 60 days.]
1822217,2019-04-01 22:57:55 UTC,"Hi Christian
After
$ sudo chown -R postgres:postgres /dbERP
You need to create"
1822217,2019-04-01 10:41:42 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1822217,2019-04-01 10:41:27 UTC,"Hi Ramiro, that would be a very severe bug.
But let us find what actually happened in your case as I can not reproduce."
1822217,2019-04-01 22:29:18 UTC,"Thank you Christian for answering my message
1. I said that clamav was the suspicious package but I cannot assure
this. The fact that clamav appears as the owner could be caused by
another package."
1822219,2019-03-29 01:41:21 UTC,"This commit fixes this problem
https://review.openstack.org/648576"
1822220,2019-04-13 12:24:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822220,2019-04-13 12:36:18 UTC,"This happened to me during a ""do-release-update -d"" on my 19.04 system.  I found a reference to a similar issue here: https://askubuntu.com/questions/146150/unable-to-fix-broken-packages-with-sudo-apt-get-install-f"
1822220,2019-04-13 12:37:55 UTC,"Correction, this was a  ""do-release-update -d"" on my 18.10 system."
1822220,2019-05-01 17:01:12 UTC,"I did the same, minus the -d flag. Not sure if this is the correct procedure, but it unblocked my usage of apt, which was critical."
1822223,2019-06-05 04:17:33 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1822223,2019-03-29 20:42:52 UTC,"You're right, 4G VRAM should easily accommodate a 300 MB buffer. Did you check if your Macbook has dynamic graphics switching (low performance/memory Intel / high performance Radeon), like Nvidia Optimus on PCs?"
1822223,2019-03-29 19:52:03 UTC,"Your computer doesn't have enough video memory to handle two high-DPI screens with 4x AA. 4x supersampling AA mode just renders the image in 4x larger resolution and then scales it down - so for a 3360x2100 display, the actual buffer size is 13340x8400x3 ~~ 300 MB. Kicad needs more than one such buffer to work."
1822223,2019-03-29 18:00:08 UTC,"It does!  I normally have it set to Supersampling (4x) since that works best on a scaled retina display.  If I set it to No Antialiasing it works fine on the external display.  In fact, it works on all settings other than 4x supersampling.  So it looks specific to that AA setting."
1822223,2019-03-29 20:23:47 UTC,"The ATI Radeon Pro 460 in the laptop has 4G VRAM, so no problem with a 300M buffer.  And it's tied to the scaled resolution on the internal display; if memory were a problem increasing the internal resolution would decrease the buffer memory available."
1822223,2019-03-29 17:06:46 UTC,"Application: kicad
Version: (5.1.0-0), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.6.4 zlib/1.2.11 nghttp2/1.24.1
Platform: Mac OS X (Darwin 18.2.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.54.0
    Compiler: Clang 9.0.0 with C++ ABI 1002"
1822223,2019-03-29 12:17:12 UTC,Could you please copy the full version info from the KiCad app menu -> About KiCad -> Copy Version Info
1822223,2019-03-29 02:48:35 UTC,"Oh, and I meant ""Display Menu"", not ""Display Manager""... apologies.
https://itunes.apple.com/us/app/display-menu/id549083868?mt=12"
1822223,2019-03-29 02:46:40 UTC,"Where I wrote ""If I plug in an external display I get an OpenGL error "" I meant ""If I plug in an external display and run KiCad and launch either eeschema or newpcb I get an OpenGL error """
1822223,2019-03-29 17:42:57 UTC,What are your antialiasing settings? Does disabling antialiasing help?
1822226,2019-05-31 04:17:18 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1822226,2019-03-31 19:36:30 UTC,"@Jan, I'll set this to incomplete so it expires if not updated. If you figure out a way to reproduce this please set it back to new."
1822226,2019-03-29 19:12:20 UTC,FWIW I used to use v5 on my MacBook Pro with two external displays and had no problem dragging the windows about or disconnecting/reconnecting the displays.
1822226,2019-03-29 17:06:15 UTC,"Application: kicad
Version: (5.1.0-0), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.6.4 zlib/1.2.11 nghttp2/1.24.1
Platform: Mac OS X (Darwin 18.2.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.54.0
    Compiler: Clang 9.0.0 with C++ ABI 1002"
1822226,2019-03-29 12:18:57 UTC,Could you please copy the full version info from the KiCad app menu -> About KiCad -> Copy Version Info
1822226,2019-03-29 18:51:13 UTC,"Now when I try to collect more info, and to see if it's affected by the aliasing settings, it works fine.  I *believe* what happened was I had launched KiCad before connecting the external display.  There's definitely something more peculiar going on than merely refusing to drag between displays in general.  I did also change the setting for ""Spaces"" to sync the displays where previously they weren't.  I will investigate further to see if I can figure out how to reliably reproduce this..."
1822227,2019-04-13 13:19:46 UTC,A short video would help to understand the problem.
1822227,2019-05-11 20:24:15 UTC,"Perhaps this is a problem in the library that draws the window and its contents (perhaps this is a problem in a bundle: wxwidgets - window manager - xorg), the closest problem is the interaction of wxwidgets or gtk3 with the window manager. I have a problem when I open the properties window every time and every time the window position floats higher and higher and the window title goes up behind the screen."
1822229,2019-09-27 09:03:17 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1822229,2020-07-21 11:46:41 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/742162"
1822229,2019-10-09 14:14:51 UTC,"Change abandoned by Sean McGinnis (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/679643
Reason: ""For this driver, multiattach is not supported in stable/queens (upstream), so I would abandon this patch."""
1822229,2019-10-04 08:51:54 UTC,This issue was fixed in the openstack/cinder 14.0.2 release.
1822229,2019-09-25 15:53:49 UTC,"Reviewed:  https://review.opendev.org/682776
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=767bdf1a5e28f18c12dba03adc429766f9be79d6
Submitter: Zuul
Branch:    stable/rocky"
1822229,2019-10-04 13:00:07 UTC,This issue was fixed in the openstack/cinder 13.0.7 release.
1822229,2019-09-18 03:09:53 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/682776"
1822229,2019-05-02 18:05:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656835"
1822229,2019-08-30 18:26:44 UTC,"Reviewed:  https://review.opendev.org/656835
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=08d35b099113679eb7d343f7463d63cb6f1adbbc
Submitter: Zuul
Branch:    master"
1822229,2019-09-18 17:52:41 UTC,"Reviewed:  https://review.opendev.org/679857
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9b5b380a6cb1a7e99d277ffe177ad02405f9fd00
Submitter: Zuul
Branch:    stable/stein"
1822229,2019-09-02 13:23:08 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/679643"
1822229,2019-09-03 20:17:49 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/679857"
1822230,2019-03-29 04:08:13 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1822230,2019-03-29 04:57:14 UTC,"I added all updates, did a reboot & same cosmetic issue remained."
1822230,2019-03-31 07:18:18 UTC,"You can view this by booting the daily ISO (noticed on 20190330) by booting it, logging out, and viewing the login screen there."
1822230,2019-09-19 08:59:25 UTC,"I'm changing to INVALID, it's a feature (design decision & is really useful if one display is turned off)"
1822232,2020-07-29 08:19:27 UTC,"Looks like neutron core plugin is the nsx MH plugin, but the configuration for it is missing."
1822233,2019-03-29 04:30:45 UTC,Thank you for taking the time to report this problem and help to improve Ubuntu.
1822233,2019-05-29 04:17:13 UTC,[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]
1822235,2020-11-05 09:07:21 UTC,"As for X/T i386 this test cannot be built (bug 1798007)
For Bionic i386 it's not failing on all the tests (comment #8)
For Bionic 5.4 i386, it's failing with vmexit* and hyperv_*"
1822235,2019-10-14 04:14:54 UTC,"For the kvm-unit-tests in this cycle with a Bionic kernel (4.15.0-66.75)
i386 node pepe has failed with on 12 tests:
  * msr
  * tsc
  * vmexit* (10 tests)"
1822235,2019-09-28 07:45:20 UTC,"For the record, onza is having problems running qemu-system-i386 on a 32-bit host kernel. It's stuck in a busy loop before loading/executing the kernel/test. The fact that pepe (same machine: Dell PowerEdge R310) doesn't exhibit that problem points to an onza hardware issue."
1822235,2019-10-01 14:10:44 UTC,So it seems something in 5.0.0-30 fixed this. 32-bit qemu hangs with 5.0.0-29 but runs just fine with 5.0.0-30 both on onza and pepe.
1822235,2019-03-29 10:15:51 UTC,"Bump the timeout threshold to 360 seconds for each test, they're still failing."
1822235,2019-03-29 05:30:06 UTC,This change was made by a bot.
1822235,2019-03-29 05:20:18 UTC,"Could be found on other kernels as well, for X/T the test will failed to build.
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798007"
1822235,2019-09-27 11:36:45 UTC,"For node pepe with D-i386, only those vmexit_* tests would fail."
1822238,2019-09-18 15:36:41 UTC,This issue was fixed in the openstack/glance 19.0.0.0b1 development milestone.
1822238,2019-10-25 13:34:12 UTC,"The fix ended into the-then master, but never into stein. As the supported Python 3.x version for 3.6, I proposed a backport of the patch."
1822238,2020-01-20 15:37:38 UTC,This issue was fixed in the openstack/glance 18.0.1 release.
1822239,2019-03-29 08:23:25 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1822239,2019-03-29 05:48:05 UTC,Automatically attached
1822239,2019-03-29 05:48:03 UTC,Automatically attached
1822239,2019-03-29 05:47:59 UTC,Automatically attached
1822240,2019-03-29 08:08:04 UTC,Thanks for your report.
1822240,2019-03-29 22:40:56 UTC,"I did, instead of the alpha version I tried the beta (unsure which
beta), same result, but this time I managed to make it to the 'enter
your details' page, when it terminated with thew same error message,
which I really hope the bug-report contained."
1822240,2019-05-29 04:17:32 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1822242,2019-04-01 07:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822242,2019-04-01 07:46:18 UTC,"Can't run the command ""apport-collect 1822242"" on the test machine."
1822242,2019-03-29 08:23:21 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1822242,2019-03-29 06:48:34 UTC,Automatically attached
1822242,2019-03-29 06:48:25 UTC,Automatically attached
1822242,2019-03-29 06:48:40 UTC,Automatically attached
1822243,2019-04-07 23:30:40 UTC,"Debianでは直しておきました。
https://tracker.debian.org/news/1037156/accepted-itamae-1910-2-source-into-unstable/"
1822245,2019-03-29 07:04:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648622"
1822245,2020-07-31 16:21:06 UTC,"Reviewed:  https://review.opendev.org/648622
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=47fb9574870c7a0317da425a3503bb0fb9957612
Submitter: Zuul
Branch:    master"
1822246,2019-03-29 07:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822246,2019-03-29 07:28:21 UTC,"Tried to run the test with TST_DISABLE_APPARMOR=1, but it seems this is not working as well:
root@zeppo:/opt/ltp# export TST_DISABLE_APPARMOR=1
root@zeppo:/opt/ltp# ./runltp -f /tmp/a"
1822246,2019-05-28 04:46:51 UTC,"This test was skipped on KVM kernels:
    binfmt_misc02 1 TCONF: binfmt_misc driver not available"
1822246,2019-10-03 13:16:00 UTC,"This may be unrelated however the failure is also found on disco, 5.0 kernel.  The actual failure messages themselves are the same, this is on the AWS Cloud, across all instance types.
This relatively new test was added back in Feb."
1822246,2019-10-22 17:44:18 UTC,http://lists.linux.it/pipermail/ltp/2019-October/014054.html
1822246,2019-10-25 12:01:24 UTC,Passed with D AMD64
1822247,2019-03-29 17:30:19 UTC,"I've not been able to reproduce this on my VMs, can I get access to one of these machines to figure out why it is failing and how to fix this."
1822247,2019-09-16 15:04:19 UTC,Test passed with 4.15.0-63.72 - generic on P9
1822247,2019-05-14 22:54:24 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822247,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1822247,2019-05-03 15:48:41 UTC,Thanks for testing!
1822247,2019-03-29 07:00:19 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822247,2019-04-29 16:03:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1822247,2019-04-12 11:26:30 UTC,Fix sent to mailing list: https://lists.ubuntu.com/archives/kernel-team/2019-April/099806.html
1822247,2019-03-29 10:52:45 UTC,"Similar failure could be found on X-4.15, AMD64 (onibi) / i386 (pepe)"
1822247,2019-04-30 11:59:09 UTC,"The nbd smoke test passed on Bionic P9 (4.15.0-49.53) without any issue.
Thanks!"
1822250,2019-03-29 07:23:56 UTC,"This commit fixes this problem:
https://review.openstack.org/648626"
1822252,2020-07-29 08:15:32 UTC,"The nsx version is not the issue.
This seems to be a configuration issue.
Please check connectivity to the nsx using the configured address & user & password from the neutron node to verify it works."
1822252,2020-09-28 04:17:15 UTC,[Expired for vmware-nsx because there has been no activity for 60 days.]
1822254,2019-04-18 11:35:43 UTC,"@Adam, Thanks, I saw that one but I was unsure if dnd from nautilus and from apps was the same cases?
Bug #1813441 is the other way around but might be the same missing code/Feature"
1822254,2019-05-28 18:38:18 UTC,Possible duplicates: #1813441 #858913
1822254,2019-04-18 08:17:55 UTC,Thank you for your bug report. That's a limitation of the new solution and should be reported upstream on https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
1822254,2019-04-18 08:33:23 UTC,Actually this issue is already known upstream:
1822254,2019-03-29 07:20:29 UTC,Automatically attached
1822254,2019-03-29 07:20:19 UTC,Automatically attached
1822254,2019-04-17 17:46:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822254,2019-03-29 07:20:27 UTC,Automatically attached
1822255,2020-08-11 14:08:34 UTC,gambas3-runtime (3.12.2+git5962.78f8359+build4.f16e457.8.7951239~ubuntu16.04.1)
1822260,2019-05-25 10:32:00 UTC,"The log file, 029_04_setup_nova_compute.auto, does not show an error. Without any further information, I do not know how to reproduce this."
1822261,2019-03-29 08:46:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822263,2019-03-29 08:42:50 UTC,sla1 for 9.0-updates
1822263,2019-04-03 15:02:03 UTC,"Hi Alexander,"
1822267,2019-03-29 12:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822267,2019-03-29 14:55:06 UTC,The kernel boot log is listed as attached file here in case someone is interested.
1822267,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1822268,2019-03-29 09:21:15 UTC,Also see Bug #1804125
1822269,2019-03-29 09:38:36 UTC,Note: coreutils verions as shown by dpkg -l command:
1822269,2019-04-11 19:02:43 UTC,"This is not a bug, it is expected & reasonable behaviour.
The `-p DIR' and `--tmpdir[=DIR]' mktemp(1) options
are the same, excepting that the <DIR> argument is
mandatory for -p and optional for --tmpdir.  (See
the manpage (`man mktemp') or try `mktemp --help'.)
That is, the following are equivalent:"
1822270,2019-05-16 10:20:57 UTC,This bug was fixed in the package debconf - 1.5.58ubuntu2
1822270,2019-05-16 09:48:22 UTC,This bug was fixed in the package debconf - 1.5.66ubuntu1
1822270,2019-05-16 09:27:11 UTC,This bug was fixed in the package debconf - 1.5.69ubuntu1
1822270,2019-05-16 09:10:11 UTC,"The verification of the Stable Release Update for debconf has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822270,2019-05-16 09:10:09 UTC,This bug was fixed in the package debconf - 1.5.71ubuntu1
1822270,2019-05-14 15:13:57 UTC,"makedumpfile failures in bionic probably are due to bug 1790788 which is in -proposed, and so should be ignorable"
1822270,2019-05-10 13:59:08 UTC,Some comments on the autopkgtest regressions:
1822270,2019-05-10 12:26:25 UTC,Validated debconf from xenial-proposed according to test case from description:
1822270,2019-05-08 18:27:47 UTC,"Hello Tobias, or anyone else affected,"
1822270,2019-05-08 20:33:48 UTC,Validated debconf from cosmic-proposed according to test case from description:
1822270,2019-05-08 20:28:31 UTC,Validated debconf from disco-proposed according to test case from description:
1822270,2019-05-08 18:30:50 UTC,"Hello Tobias, or anyone else affected,"
1822270,2019-05-08 18:29:21 UTC,"Hello Tobias, or anyone else affected,"
1822270,2019-05-08 18:24:38 UTC,"Hello Tobias, or anyone else affected,"
1822270,2019-04-02 22:25:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822270,2019-05-10 12:22:04 UTC,Validated debconf from bionic-proposed according to test case from description:
1822273,2019-12-01 15:25:54 UTC,This was a mistake: The template choice dialog was not seen by the user. Upstream has improved this problem.
1822273,2019-05-30 14:28:35 UTC,"hi Antoine,"
1822273,2019-04-06 18:05:47 UTC,"hi Antoine,"
1822274,2019-03-29 10:30:13 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822274,2020-11-05 03:02:23 UTC,"I haven't seen this recently, thus I am closing this."
1822275,2019-03-29 10:17:21 UTC,ping to mysql cluster vip didn't find any packet lost. The iperf3 testing looks really good from nova-cloud-controller/0 to this vip too as:
1822275,2019-03-29 10:56:24 UTC,"lost connection report was only from nova-api, also for other services of neutron, gnocchi, keystone etc. too."
1822275,2019-04-01 08:45:43 UTC,To adjust percona cluster charm wait_timeout (from 180 to 3600 seconds) and innodb-buffer-pool-size (from 512M to 2G) can reduces this timeout error/waring about 90%. To reduces work-multiplier to reduces would reduce db clients connect too (it would run less process for example neutron-server).
1822275,2019-04-06 14:54:24 UTC,It might better to set as 3630 to wait more 30s for client close.
1822276,2020-07-01 20:25:07 UTC,"Thank you for your bug report. It seems similar to upstream https://gitlab.gnome.org/GNOME/evince/-/issues/909 but the behaviour should be that it stores in the same directory as the current document by default, or if it's a temp location then fallback to the document directory and it's not there to the user dir
If you wish to discuss the behaviour it's better done on gitlab upstream than on launchpad"
1822278,2019-05-29 04:17:21 UTC,[Expired for juju because there has been no activity for 60 days.]
1822308,2019-04-10 15:19:57 UTC,seeing something similar on AWS/Cosmic 4.18.0-1013.15 	linux-aws
1822308,2019-05-21 18:34:13 UTC,"affects , linux-aws-4.18.0 amd64, i3.metal"
1822308,2019-11-07 07:45:01 UTC,"Failed on Oracle B-4.15
Passed on Oracle B-5.0"
1822308,2020-11-17 04:26:51 UTC,Still visible in Xenial 4.4.0-1118.132 AWS c5.metal
1822308,2021-02-16 21:54:28 UTC,Seen with linux-oracle 4.15.0-1065.73.
1822309,2021-02-16 21:57:24 UTC,Still seen with linux-oracle 4.15.0-1065.73.
1822309,2020-11-17 04:26:03 UTC,Still visible in Xenial 4.4.0-1118.132 AWS c5.metal
1822309,2019-10-17 08:58:49 UTC,Found on B-kvm as well.
1822309,2019-04-19 05:57:07 UTC,Found on T-AWS (4.4) as well.
1822309,2019-11-07 07:44:57 UTC,"Failed on Oracle B-4.15
Passed on Oracle B-5.0"
1822321,2019-03-29 13:50:14 UTC,"several attempts to install this current upgrade version...from ubuntu 18.04 only first install logs available!!! due to numerous attempts to fix the boot start up for amd64. (constant reload of the initramfs..)
error no operating system found error messages.until using a usb flash burned from WWW.ETCHER.IO.COM Works to install the version U18.10 after reboot system crashes no boot.
dvd-rw fails all operations
several attepts to run USB -flash iso removed cmos battery. and success
several more attempts to rebbot after installing from usb FINALLY INSTALL eased hdd.reinstalled so i could at least try and provide as much info as possible from own laptop.during new install.
partion could be in wrong place it would seem..and mmefix86 may be ext2 changing to ext4 in 'e' option worked on grub5 did not work with grub 2.02
regards Ray (Gangster-Jesus ) + i am a novice on linux 12 months"
1822322,2019-03-29 14:06:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648695"
1822322,2019-05-07 15:05:45 UTC,"Reviewed:  https://review.opendev.org/648695
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=cc280d9dcb9259c203481029df80524c6c458d3a
Submitter: Zuul
Branch:    master"
1822322,2019-05-09 11:44:37 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/658058"
1822322,2019-05-17 09:17:21 UTC,"Reviewed:  https://review.opendev.org/658058
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=9a4a33a7c868a4ba92d997ddc3d526554abb7ff5
Submitter: Zuul
Branch:    stable/19.04"
1822327,2019-06-21 15:25:46 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1822327,2019-03-29 13:51:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/648692"
1822327,2019-04-04 15:54:53 UTC,"Reviewed:  https://review.openstack.org/648692
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=f6c4f652c774ed2ef0a6e4307be7096e41dc02f3
Submitter: Zuul
Branch:    stable/queens"
1822327,2019-06-20 18:42:01 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/666658"
1822327,2019-06-20 19:06:38 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.opendev.org/666658
Reason: this was fixed in https://review.opendev.org/#/c/605728/ and not backported to Queens."
1822328,2019-03-29 14:32:04 UTC,https://gitlab.gnome.org/GNOME/gnome-boxes/issues/338
1822328,2019-03-29 14:21:28 UTC,"StacktraceTop:
 gvir_event_handle_update (watch=1, events=0) at libvirt-glib-event.c:231
 virNetSocketUpdateIOCallback (sock=0x7f7ee4005e30, events=0) at ../../../src/rpc/virnetsocket.c:2210
 virNetClientIOUpdateCallback (client=client@entry=0x7f7ee40089c0, enableCallback=enableCallback@entry=false) at ../../../src/rpc/virnetclient.c:1802
 virNetClientIO (thiscall=0x55c16a2cbba0, client=0x7f7ee40089c0) at ../../../src/rpc/virnetclient.c:1950
 virNetClientSendInternal (client=client@entry=0x7f7ee40089c0, msg=msg@entry=0x55c16a2c7860, expectReply=expectReply@entry=true, nonBlock=nonBlock@entry=false) at ../../../src/rpc/virnetclient.c:2128"
1822329,2019-03-29 16:52:26 UTC,"Efforts also pushed at [1]. For now, lint or tests don't work, but the lib/lib_grafana/* package has been split in multiple files, and code in reactive/grafana.py has started to point to the defined classes and methods."
1822329,2019-04-01 07:38:31 UTC,"Available stacked MPs (rewrite branch is a copy of master, for now):"
1822329,2019-06-28 12:55:01 UTC,"Initial phase of the rewrite has been completed and tested. Trusty support has been removed because snaps cannot work on trusty containers, and layer-snap returns an error instead of blocking the unit."
1822329,2020-02-06 07:11:04 UTC,"Multiple development cycles. Need to catch up with current master, and probably rebase these changes into an updated (in sync with master) ""rewrite"" branch."
1822331,2019-04-01 18:53:02 UTC,This bug was fixed in the package autopkgtest - 5.10ubuntu1
1822331,2019-04-01 14:16:20 UTC,"Sponsored in Disco based on 'ACK' from release manager (with regard to current freeze schedule) +  debian reverted the change + consideration about ESM, EOL different POV between Ubuntu and Canonical."
1822331,2019-04-01 12:51:04 UTC,"With my release team member hat: since it's debatable whether this is a feature or bugfix, even in the case of it being a feature I'd be +1 on letting it in. Since it's only introducing series to the list, there should be no regression potential that it could delay the release. So feel free to upload it."
1822331,2019-04-01 12:53:37 UTC,"The change has been reverted in debian, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925966#10"
1822331,2019-03-29 15:14:43 UTC,I agree that someone running disco today and/or after its release could still have the need to create a Ubuntu cloud image based VM for autopkgtest-virt-qemu with precise and trusty.
1822331,2019-03-29 15:10:31 UTC,"> precise has been EOL for 2 years
"
1822331,2019-03-29 14:59:07 UTC,"precise has been EOL for 2 years; trusty's support will end in about a month,  so I don't think we need to bother about this now."
1822331,2019-03-29 15:21:16 UTC,"Since we already entered a few freeze already, this bug is debatable as if it's a 'bugfix' or 'feature'. I'll coordinate with the SRU team next week and worst case I'll do the upload once Disco become stable (with no freeze restriction)."
1822337,2019-09-25 12:14:11 UTC,This is a reasonable claim: I'm marking it as a whishlist because it is a new feature.
1822347,2019-04-11 02:31:34 UTC,"""horizon"" project does not provide magnum support. Are you filing a bug against magnum-ui?"
1822347,2019-06-10 04:17:41 UTC,[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]
1822350,2019-03-29 16:40:13 UTC,"StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f7ab941a770 <__FUNCTION__.11777> ""g_hash_table_lookup_node"", message=<optimized out>) at ../../../glib/gtestutils.c:2878
 g_assertion_message_expr (domain=domain@entry=0x7f7ab941500e ""GLib"", file=file@entry=0x7f7ab941a415 ""../../../glib/ghash.c"", line=line@entry=468, func=func@entry=0x7f7ab941a770 <__FUNCTION__.11777> ""g_hash_table_lookup_node"", expr=expr@entry=0x7f7ab941a518 ""!g_atomic_ref_count_compare (&hash_table->ref_count, 0)"") at ../../../glib/gtestutils.c:2904
 g_hash_table_lookup_node (hash_table=0x55eb38c13930, key=0x55eb383f3191, hash_return=<synthetic pointer>) at ../../../glib/ghash.c:468
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x55eb383f3191, hash_table=0x55eb38c13930) at ../../../glib/ghash.c:452
 g_hash_table_lookup (hash_table=0x55eb38c13930, key=key@entry=0x55eb383f3191) at ../../../glib/ghash.c:1464"
1822350,2019-03-29 16:45:41 UTC,https://gitlab.gnome.org/GNOME/evince/issues/1120
1822351,2019-12-16 18:43:26 UTC,"Was able to have Nautilus back doing ""killall nautilus; nautilus --check"" on terminal, but just for the current session."
1822351,2019-10-04 13:41:17 UTC,"Same experience as julo. Also, I have a storage volume I use to mount manually after boot. If I mount it quickly I have no problems. Sometimes I get into this bug. And sometimes all starred locations on that volume disapper. It appears to be a race between me and the tracker."
1822351,2019-09-24 18:11:52 UTC,"Also in case that helps, I experience the same bug. In addition, #2 did not work for me. Immediately after executing ""tracker reset -e"" on a shell, nautilus shows instantly after a click, but the problem comes back at the next reboot."
1822351,2019-08-21 06:04:44 UTC,"Hi,"
1822351,2019-07-18 07:21:18 UTC,"Hello,"
1822351,2019-06-27 08:18:15 UTC,Could you report it upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/? From the backtrace it looks like it's stucked in some tracker call
1822351,2019-06-27 07:37:48 UTC,"Interestingly, I left virtual machine with not working Nautilus running, and few hours later found that Nautilus started after all. So it's not like it not working at all, it's just take few minutes/hours to show the window."
1822351,2019-06-26 19:07:38 UTC,"> https://wiki.ubuntu.com/Backtrace#Already_running_programs describes how to get a stacktrace of a program hanging
"
1822351,2020-05-24 17:48:18 UTC,Same for me on Ubuntu 20.04
1822351,2019-06-24 10:34:01 UTC,Same issue for me. It was working for a while and all of a sudden it stopped. The workaround mentioned in #2 doesn't work for me.
1822351,2019-05-02 21:53:22 UTC,https://wiki.ubuntu.com/Backtrace#Already_running_programs describes how to get a stacktrace of a program hanging
1822351,2019-05-02 20:42:35 UTC,"Same issue here, same workaround helps."
1822351,2019-04-04 14:23:25 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1822351,2019-03-29 17:11:59 UTC,Update: Enabling and disabling the search and notification permissions on Settings->Applications->Nautilus solved the problem.
1822351,2019-06-26 19:16:31 UTC,"Workaround does not help me too anymore. So there is possibility that after system upgrade there was one issue, and now it's another."
1822352,2019-04-01 14:48:20 UTC,Checked out.  Works great now.
1822352,2019-03-30 07:59:18 UTC,have to check.
1822352,2019-03-30 17:35:05 UTC,will be fixed in next build (most probably tomorrow)
1822353,2019-04-01 14:28:39 UTC,For help in debugging I have attached a console of an instance that failed to set up networking
1822353,2019-04-01 14:29:31 UTC,And for completeness I have attached a console of an instance that _successfully_ set up networking
1822353,2020-09-05 18:14:56 UTC,I'm also running into this kind of issues with Debian servers on 20.2-2~deb10u1. I'm not trying to rename the interfaces and final names are the kernel ones (ethX) instead of the expected predictive names. This is an issue for our inventory process.
1822353,2020-09-07 16:46:57 UTC,"Hi Johann,"
1822353,2020-11-07 04:17:19 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1822359,2019-04-05 14:36:06 UTC,bug #1208419 not found
1822359,2019-04-05 19:50:42 UTC,I had the exact same problem and error reports (as the OP above) a couple of weeks ago.
1822359,2019-03-29 18:20:13 UTC,"Thank you for taking the time to report this crash and helping to make this software better.  This particular crash has already been reported and is a duplicate of bug #1208419, so is being marked as such.  Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1822360,2019-07-04 15:39:10 UTC,The issue is about to be fixed in 18.04.
1822360,2019-07-16 04:03:38 UTC,Updated software - scanner still does not work
1822360,2019-07-16 04:15:39 UTC,"@Phil: It's still in bionic-proposed, but will be moved to bionic-updates any day now."
1822361,2019-04-15 06:38:12 UTC,"you're not actually using nouveau (the X driver), the error is from the kernel.. and since it's buggy, the later kernels have disabled nouveau modeset by default, so this shouldn't happen with 5.0.0-11 and up..."
1822361,2019-03-29 18:49:21 UTC,"PS: I must clarify that at the moment I have already updated the video driver of my notebook for nvidia (I used ""ubuntu-drivers"" for it). But the problem in question always happens, from the first installation of ubuntu where, originally, the nouveau drive is installed.
In this case I resolved to give a purge in the previous version of the nvidia driver that I had installed, to then redo the installation of the new version 418 ... after the purge I was forced to reboot the computer before reinstalling the nvidia driver. .. and had to go through the whole problem of trying to use the nouveau driver in this notebook. That's where I got the photos from the log screens."
1822363,2019-04-13 10:11:58 UTC,"Do you mean bisection in bisection (blank screen bisection), or the original bisection (xHC bisection)?"
1822363,2019-04-15 03:41:46 UTC,"1. Pause the original bisection.
2. Start a new bisection for the blank screen issue. Found the regression commit.
3. Resume the original bisection. Each bisected point needs to cherry-pick the fix or revert the regression commit."
1822363,2019-04-13 23:49:38 UTC,"Kai-Heng Feng pisze:

> Do you mean bisection in bisection (blank screen bisection), or the
> original bisection (xHC bisection)?
>
> For the blank screen one, the current commit is ""bad"".
>
> For the xHC one, we don't know yet. Cherry pick the fix on top of the
> current commit then we can decide it's good or bad.
>


I found git cherry-pick command but the situation is that I have passed
2 git bisect good on ""4.9-rc8"" and I have no boot problem on 4.10-rc2+3
which I now is somehow corrected on 4.10-rc8 because system hangs on USB
3.0 PCI again. But 4.10-rc8 is 11 steps ahead now (4.10-rc2+3). What
should I set to git cherry-pick?"
1822363,2019-04-13 10:27:15 UTC,"Kai-Heng Feng pisze:

>   Cherry pick the fix on top of the
> current commit then we can decide it's good or bad


I don't know how to do it."
1822363,2019-04-11 05:17:16 UTC,"Most of the time you need only ""linux-image-4.9.0+_4.9.0+-1_amd64.deb"". But if you have also some dkms based modules installed, you may want to install linux-headers-* as well."
1822363,2019-04-12 14:54:27 UTC,"Also to minimize the gamut of potential regressions, only includes necessary modules, e.g. PCI and xHCI. Things like graphics and network driver can be excluded."
1822363,2019-04-12 14:19:50 UTC,"When I encounter situation like this, I alway do another ""bisection in bisection"" to find the fix commit, then cherry-pick the fix to continue the original bisection."
1822363,2019-04-12 06:16:43 UTC,"After 3rd ""git bitsect"" built linux-image-4.10.0-rc2+_4.10.0-rc2+-3_amd64.deb which hangs on boot without any single boot line. I bet it is not connected with USB 3.0 PCI card at all (other kernel problem) what was corrected later by 4.10.rc8 which hangs again on USB 3.0 PCI card. I don't know if I should git biset this still as good or bad. Any help?"
1822363,2019-04-18 23:02:49 UTC,"1. I understand that it is done by command ""git bisect reset""
2. If I understand You well I am already on first regression commit (blank screen issue) becouse I can't boot on 4.10-rc2+3 but on 4.9.0+-2 it was possible."
1822363,2019-04-12 20:00:07 UTC,Resuming the situation I have to do git bisect bad now on this step?
1822363,2019-04-22 03:27:04 UTC,"> 1. I understand that it is done by command ""git bisect reset""
Before doing the reset, run
$ git bisect log > log
To record the current bisection steps.
"
1822363,2019-08-04 20:26:40 UTC,"You don't know PC architecture well. Your chip is natively connected to
PCIe.
My USB chip has PCI/PCI-X bridge to PCI and it is completly different
initialization procedure - not similiar to yours.
Scott Polley pisze:

> Available to help test/try solutions.
>
> I have a combo card (usb + sata) which has this chip as well, while I
> didn't have the boot-hang issue, no devices are seen (connected prior to
> boot or otherwise). Added comment on a thread specific to this card, but
> it is quite old, and marked as solved (gave up on card).
> https://answers.launchpad.net/ubuntu/+question/670407
>
> Mac pro 2010, Ubuntu 18, kernel 5.2.2
>
"
1822363,2019-07-08 05:54:56 UTC,"Commit ""174cc7187e6f"" has several several subsequent fixes, cherrypicks the fixes during bisection."
1822363,2019-07-08 17:37:07 UTC,"Spotted this commit when I am doing an unrelated task:
commit f7fac17ca925faa03fc5eb854c081a24075f8bad
Author: Andrey Smirnov <email address hidden>
Date:   Wed May 22 14:34:01 2019 +0300"
1822363,2019-07-08 18:48:30 UTC,"Thank's. I will return on sunday to this because I have a brake.
-------- Oryginalna wiadomość --------Od: Kai-Heng Feng <email address hidden> Data: 08.07.2019  19:37  (GMT+01:00) Do: <email address hidden> Temat: [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is
  detected Spotted this commit when I am doing an unrelated task:commit f7fac17ca925faa03fc5eb854c081a24075f8badAuthor: Andrey Smirnov <email address hidden>Date:   Wed May 22 14:34:01 2019 +0300    xhci: Convert xhci_handshake() to use readl_poll_timeout_atomic()        Xhci_handshake() implements the algorithm already captured by    readl_poll_timeout_atomic(). Convert the former to use the latter to    avoid repetition.        Turned out this patch also fixes a bug on the AMD Stoneyridge platform    where usleep(1) sometimes takes over 10ms.    This means a 5 second timeout can easily take over 15 seconds which will    trigger the watchdog and reboot the system.        [Add info about patch fixing a bug to commit message -Mathias]    Signed-off-by: Andrey Smirnov <email address hidden>    Tested-by: Raul E Rangel <email address hidden>    Reviewed-by: Raul E Rangel <email address hidden>    Cc: <email address hidden>    Signed-off-by: Mathias Nyman <email address hidden>    Signed-off-by: Greg Kroah-Hartman <email address hidden>Can you try this? It's in Linux kernel v5.2.-- You received this bug notification because you are subscribed to the bugreport.https://bugs.launchpad.net/bugs/1822363Title:  Booting hangs when USB 3.0 Etron EJ168 PCI card is detectedStatus in linux package in Ubuntu:  ConfirmedBug description:  I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI).  There are no devices connected to PCI USB card during boot.  The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this  card during boot (see attached ""photo log"" with boot and grub  options). I can't access/login Ubuntu or console. It was checked and  confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with  acpi=off option too).  Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present.  I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards.  The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices.  I can assist in any way to solve this bug as IT Professional.To manage notifications about this bug go to:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions"
1822363,2019-08-02 22:28:31 UTC,"I have checked v5.2 and it is working.
How to install it on upgraded 18.04 frm 16.04 which is not bootable due
to this usb bug?
Is it possible to install it from bootable 16.04 (I have it on on
different partition)?"
1822363,2019-08-03 07:55:29 UTC,"Yes I think it's possible. Mount it, chroot (e.g. systemd-nspawn) into the system and install the kernel packages."
1822363,2019-08-04 20:12:26 UTC,Available to help test/try solutions.
1822363,2019-08-05 15:51:55 UTC,"Sorry if I misunderstood the issue you are having, good luck"
1822363,2019-08-07 21:50:06 UTC,"Kai-Heng Feng pisze:

> Yes I think it's possible. Mount it, chroot (e.g. systemd-nspawn) into
> the system and install the kernel packages.
>


It's all done on kernel v5.2, which is fully bootable and working.
The conclusion is that Ubuntu from 16.4.3 till now and all Live CD are
unusable, because they are using buggy kernel's >= 4.10 && kernel's < 5.2.
They should be patched."
1822363,2019-08-08 19:24:10 UTC,"Eoan image uses Linux 5.2:
http://cdimages.ubuntu.com/daily-live/pending/"
1822363,2019-09-10 22:49:38 UTC,New Ubuntu 18.04 LTS supported kernel 4.15.0-60-generic is again bootable and USB 3.0 works.
1822363,2019-06-19 15:26:37 UTC,"I finally found 1st commit (not connected with USB problem) which prevents booting, but it is corrected much later in 4.10-rc8.I don't know how to locate correction commit for the one below
$ git bisect bad
174cc7187e6f088942c8e74daa7baff7b44b33c9 is the first bad commit
commit 174cc7187e6f088942c8e74daa7baff7b44b33c9
Author: Lv Zheng <email address hidden>
Date:   Wed Dec 14 15:04:25 2016 +0800"
1822363,2019-04-11 04:57:59 UTC,"Ok, I have retried to bitsect under main kernel 4.8.0 for 16.04.02 LTS instead installed on 4.9-rc8.
Using:
$ git bisect good v4.9-rc8
$ git bisect bad v4.10-rc8
I have built kernel under 4.8.0 with default (Enter) options becouse I don't know nuances in them yet.
I have got many files from kernel build and I need advice, what shall I install for test:"
1822363,2019-03-31 22:52:22 UTC,"lspci from Ubuntu 11.10 working kernel
Linux ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux"
1822363,2019-04-10 00:02:44 UTC,Are U waiting for expiration without fix? Anyone will take responsibility on his accout?
1822363,2019-03-29 19:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822363,2019-04-10 04:49:48 UTC,I don't see that issue on my system:
1822363,2019-03-30 02:15:05 UTC,"The same hanging behaviour in Centos-7 DVD
name = CentOS-7
family = CentOS
timestamp = 1543162874.22
variant =
version = 7
packagedir =
arch = x86_64"
1822363,2019-03-30 09:57:11 UTC,"Please try latest daily image which uses Linux v5.0:
http://cdimage.ubuntu.com/daily-live/current/disco-desktop-amd64.iso"
1822363,2019-03-30 09:58:21 UTC,According to LP: #1050778 it used to work on Ubuntu 11.10.
1822363,2019-03-31 02:38:49 UTC,"11.10 works without any problem with card and devices connected. disco-desktop-amd64.iso Ubuntu 19.4 hangs like Ubuntu 18.4 in the same manner. It must be something in xhci-pci.c driver broken. It is important to me and should be avoided by:
1) skipping error when it can't be resolved during boot (it shouldn't prevent Ubuntu 18.4-19.4 system load)
2) the xhci should be ""unbuged"" besouse it is workable in 11.10."
1822363,2019-04-01 04:35:38 UTC,Would it be possible for you to do a kernel bisection?
1822363,2019-04-02 11:02:39 UTC,I found Ubuntu 15.10 amd64 on 4.2.0-16 kernel linux is the last version where the EJ168 card is working and system boots from DVD. I have to find the way to access my installed 18.10 with card (way to disable xhci driver during boot or pci card) becouse I cannot access installed system to make anything with it and test.
1822363,2019-04-02 11:33:30 UTC,Would it be possible to find the last good -rc kernel between v4.2 and v4.4?
1822363,2019-04-03 00:50:22 UTC,"I was temporary installed Ubuntu 15.10 amd64 as base to test kernels, becouse it was working with card. After long retries I have discovered  that v4.9 (https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/) is working, but 4.10 (https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/) stops at this bug."
1822363,2019-03-29 23:47:25 UTC,I can't boot to do logs with any kernel pci options when Etron PCI USB 3.0 is present in slot.
1822363,2019-04-03 07:09:54 UTC,Are You sure looking that in 4.10-rc* not in 4.9.XXX ?
1822363,2019-04-03 06:53:04 UTC,One more step: please find the last good 4.10-rc* kernel.
1822363,2019-04-04 09:42:02 UTC,"kernel v4.10-rc8 boots until hang on bug under 16.04.2 LTS. I don't know why the same kernel under 15.10 it is not, but it is freezed release and not important."
1822363,2019-04-03 17:35:11 UTC,"Besiades my BIOS is not U/EFI I also experience the lag keyboard (connected to PS/2 port) in grub:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668105"
1822363,2019-04-03 17:08:57 UTC,"Why the xhci_hcd module which is unstable  driver itself and works with many unstable USB 3.0 controllers and devices (with bugs) is compiled in kernel and cannot be easoly disabled???
It is insane script-kiddie unprofessional kernel development."
1822363,2019-04-03 17:06:14 UTC,"@Kai-Heng Feng
The last stable for me was v4.9 not any single version v4.10 nor v4.10-rc* is bootable!"
1822363,2019-04-04 00:27:38 UTC,"Kai-Heng Feng
I switched to Ubuntu 16.04.2 based on 4.8 as a base LTS is better. I've tested kernel v4.9-rc8 as bisect good and v4.10-rc8 as bisect bad but I get:
$ git bisect good v4.9-rc8
$ git bisect bad v4.10-rc8
  Some good revs are not ancestor of the bad rev.
  git bisect cannot work properly in this case.
  Maybe you mistook good and bad revs?"
1822363,2019-04-03 13:47:22 UTC,Every kernel from 4.10.rc2 to 4.10.rc8 stuck just after Loading initial ram disk...(boot without quiet splash options). No log.
1822363,2019-04-03 12:45:18 UTC,Starting from kernel 4.10.rc1 is stuck during load after SSDT Intel line(captured to attached pic).(probably any another problem with it comparing to v4.10)
1822363,2019-04-03 07:20:18 UTC,"Yes, release candidates (rc) kernels are released between each major release."
1822363,2019-04-03 15:58:06 UTC,There are too many possible commits in PCI and USB between v4.9 and v4.10.
1822366,2019-05-28 13:07:09 UTC,"It is a data network.
system datanetwork-add group0-data0 vlan -m 1500"
1822366,2019-07-16 13:48:51 UTC,"@Yang, can you please re-test this scenario? There was a driver upgrade from the Niantic which was merged on 2019-06-11
https://review.opendev.org/#/c/664363/"
1822366,2019-05-28 11:00:59 UTC,"Hi Yang,"
1822366,2019-05-24 13:07:10 UTC,"The only step is to add sriov interfaces. e.g.,"
1822366,2019-05-24 10:25:06 UTC,"Hi Yang,"
1822366,2019-04-05 00:52:13 UTC,Following up with 2 in previous comment. It is reproduced on system with Niantic sriov interface.
1822366,2019-06-03 15:21:10 UTC,Needs to be re-assigned since the current developer doesn't have the NIC in question
1822366,2019-06-10 05:30:06 UTC,we also do not have the NIC specified in LP.
1822366,2019-07-16 15:17:55 UTC,"This issue is no longer seen after the driver upgrade for Niantic.
Load: master ""20190713T013000Z""
SRIOV NIC: Intel 82599 (Niantic)"
1822366,2019-04-03 18:57:33 UTC,Adding stx.distro.openstack to the tags as this maybe an openstack bug
1822366,2019-04-04 20:37:54 UTC,"1. My previous environment is gone. I tried it with latest load (20190404T013000Z) on a different system with CX-4 for sriov interface, and did not reproduce the issue. I notice the dev name changed after suspend/resume, but the MAC stays the same. The dev name reverted back after a reboot of the guest."
1822366,2019-04-04 20:21:49 UTC,"guest image were split into 5 files via split cmd and can be combined using
cat tis-centos-guest-* > tis-centos-guest.qcow2"
1822366,2019-04-04 06:47:14 UTC,"Yang, could you please provide the dumpxml of guest VM as well? (virsh dumpxml <instance>)"
1822366,2019-04-04 01:12:26 UTC,"Yang, where did you get your CentOS guest image? Download from the official site[1]? Or you built it by yourself? If you downloaded it, could you please provide the link, thanks."
1822366,2019-04-03 14:36:39 UTC,Adding stx.distro.other to the labels as this maybe an openstack bug
1822366,2019-04-03 12:49:49 UTC,CentOS guest.
1822366,2019-04-03 05:00:32 UTC,"Yang, what guest image were you using?"
1822366,2019-04-01 17:42:51 UTC,Marking as release gating; requires further investigation to determine if this is an upstream nova/neutron issue (which would then require an upstream bug to be opened) or something in the starlingx env
1822366,2019-05-29 15:14:41 UTC,"Hi Chenjie,"
1822366,2019-07-16 15:38:59 UTC,"Thanks Yang.
I am going to mark this bug as Fix Released; addressed by the driver upversion: https://review.opendev.org/#/c/664363/"
1822366,2019-05-29 11:46:02 UTC,"Hi Yang,"
1822366,2019-05-30 12:36:15 UTC,"Hi Yang,"
1822366,2019-05-30 13:03:51 UTC,It probably will not work then. Here's a list of supported NICs for SRIOV:
1822367,2019-05-29 11:02:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661939"
1822367,2019-06-06 16:22:36 UTC,"Reviewed:  https://review.opendev.org/661939
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ff7cce93ebcdf4fd868329be94d618f9e755049f
Submitter: Zuul
Branch:    master"
1822367,2019-06-07 07:14:01 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/663850"
1822367,2019-06-08 05:14:25 UTC,"Reviewed:  https://review.opendev.org/663850
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=c6294bd8a0638e50c867014d44c32933ccc15bfc
Submitter: Zuul
Branch:    stable/stein"
1822367,2019-07-05 12:51:50 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1822367,2019-07-26 18:16:17 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.1.0 release.
1822367,2019-09-26 15:42:52 UTC,What if someone wants to use ComputeHCI role ? Shouldn't CompueHCI role be required extarnal_bridge tag ?
1822367,2020-02-12 15:18:29 UTC,new related bug filed here https://bugzilla.redhat.com/show_bug.cgi?id=1801836 that raises concern in #c7
1822369,2020-05-14 13:38:15 UTC,My error is slightly similar:
1822369,2019-04-19 09:58:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822371,2019-03-29 19:51:38 UTC,"# check swift_public
# The following header was added automatically by juju
# Modifying it will affect nagios monitoring and alerting
# servicegroups: bootstack
command[check_swift_public]=/usr/lib/nagios/plugins/check_http -H <rados gateway public hostname> -p 80 -u None -S"
1822371,2019-07-04 14:53:28 UTC,"Hello Narinder, is this still an issue? I see this has been fixed at commit bd275a7. ""swift_check_params"" config parameter defaults to ""/"" but allows extra parameters."
1822372,2019-03-30 20:33:12 UTC,I managed to fix it by opening the default profile configuration:
1822376,2020-10-30 18:19:55 UTC,"We ran into this on our training system which we call ""egtraining"".  My fix to the regex is to make sure ""eg"" is followed by a slash.  I'm not sure if this will break under other circumstances:"
1822376,2019-09-13 20:42:44 UTC,Side note (for this bug and others):  an AngularJS tag would be helpful.
1822376,2019-03-29 20:49:15 UTC,"Specifically, the following line in Open-ILS/web/js/ui/default/staff/cat/catalog/app.js is at fault:"
1822378,2019-04-01 11:33:56 UTC,See also: bug 1694663.
1822378,2018-07-31 14:04:06 UTC,"Created attachment 1471812
SANE_DEBUG_HPAIO=255 SANE_DEBUG_DLL=255 SANE_DEBUG_SANEI_TCP=255 scanimage -L &> sane.debug"
1822378,2019-03-29 21:08:18 UTC,"I cannot scan with the HP M281fdw on Fedora 29.
See also: https://bugs.launchpad.net/hplip/+bug/1817214"
1822378,2019-03-29 21:21:23 UTC,"See also:
https://bugs.launchpad.net/hplip/+bug/1817214
https://bugs.launchpad.net/hplip/+bug/1821932
https://bugs.launchpad.net/hplip/+bug/1797501"
1822378,2019-04-15 09:46:23 UTC,"Hi Jan,"
1822378,2019-04-02 20:01:52 UTC,This 1816226 bug is probably the same issue as described in bug 1816226.
1822379,2020-07-18 15:24:45 UTC,I'm guessing this is a duplicate of 1786822?
1822387,2019-03-29 22:52:52 UTC,"Note that there's similar fun behavior with DELETEs, even without nesting:"
1822388,2019-05-24 16:21:29 UTC,"Verified.
Connection to node-3 closed.
[root@nailgun ~]# fuel nodes
id | status | name                      | cluster | ip         | mac               | roles             | pending_roles | online | group_id
---+--------+---------------------------+---------+------------+-------------------+-------------------+---------------+--------+---------
 2 | ready  | slave-04_compute_ceph-osd |       1 | 10.109.0.6 | 64:f1:86:74:e3:d0 | ceph-osd, compute |               |      1 |        1
 1 | ready  | slave-01_controller       |       1 | 10.109.0.3 | 64:55:a9:ec:15:64 | controller        |               |      1 |        1
 6 | ready  | slave-02_controller       |       1 | 10.109.0.4 | 64:70:75:42:22:8a | controller        |               |      1 |        1
 4 | ready  | slave-03_controller       |       1 | 10.109.0.5 | 64:01:57:e9:9d:cd | controller        |               |      1 |        1
 3 | ready  | slave-05_compute_ceph-osd |       1 | 10.109.0.7 | 64:90:24:71:e0:2b | ceph-osd, compute |               |      1 |        1
 5 | ready  | slave-06_compute_ceph-osd |       1 | 10.109.0.8 | 64:57:05:15:69:fb | ceph-osd, compute |               |      1 |        1"
1822388,2019-04-16 10:29:13 UTC,"Reviewed: https://review.fuel-infra.org/40949
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka"
1822388,2019-04-10 16:12:42 UTC,Backport: https://review.fuel-infra.org/#/c/40949/
1822388,2019-04-10 10:45:16 UTC,We need to consider backporting of https://review.openstack.org/#/c/409943/
1822391,2019-11-20 04:17:55 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1822391,2019-09-20 13:23:32 UTC,There has been a few changes regarding pods in 2.6. Could you please try and see if the bug is reproducable there?
1822392,2019-05-01 02:17:46 UTC,"that does never work for me
`sudo /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93
fish: “sudo /usr/lib/gnome-settings-da…” terminated by signal SIGSEGV (Address boundary error)
`
gsd-backlight-h[19085]: segfault at 0 ip 00007f7235fe25ee sp 00007fff88c62278 error 4 in libc-2.29.so[7f7235e86000+173000]
[499265.506514] Code: 0f 84 f9 fe ff ff e9 51 89 f3 ff 90 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 56 03 00 00 c5 fe 6f 0f <c5> f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 74 7e f3 0f"
1822392,2019-04-30 15:39:01 UTC,(start the command with sudo)
1822392,2019-04-26 20:31:25 UTC,"on 19.04 the issue still exists.
gsd-media-keys seems to be the problem after all..."
1822392,2019-04-29 13:53:46 UTC,Thank you for your bug report. Could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/ ?
1822392,2019-04-30 15:38:40 UTC,Does using e.g '/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93' works at the time you get the issue? If not does it give you any error?
1822392,2019-10-14 10:51:45 UTC,That's the command quoted in the log from the bug description?
1822392,2019-10-12 15:53:42 UTC,"Uh are you sure those are the correct arguments? Afaik gsd-backlight-helper wants a device and a value (e.g. gsd-backlight-helper /sys/class/backlight/intel_backlight/ 700), not any switches. If you don't pass a device, it fails on a strcmp with realpath(argv[1], device), which is NULL because ""--set-brightness"" is not a path."
1822394,2020-01-08 20:31:15 UTC,"The BIOS 1.9.1 from prev. comment #50 apparently was pulled by Dell, there is no reason given at the link."
1822394,2019-12-26 19:12:37 UTC,Dell released yesterday BIOS version 1.9.1 for the affected XPS 9575:
1822394,2020-01-22 15:19:53 UTC,On bios 1.10.0 that was released yesterday with kernel 5.4(fedora) I no longer have this issue.  The keyboard and mouse work on boot for me.
1822394,2019-12-17 05:01:12 UTC,"Mark,"
1822394,2020-01-23 00:46:50 UTC,I also see no change with BIOS 1.10.0 on Eoan (though with kernel 5.3 due to an unrelated issue; I ran 5.4 and 5.5 before with the 1.7.1 BIOS and had the problem with all three kernels).
1822394,2019-12-16 21:50:19 UTC,"On a new XPS 15 9575 2-in-1 with BIOS 1.8.1, the symptoms are similar to comment #24.  At the gdm login screen, the keyboard doesn't work at first but is OK after 20-30 seconds. The touchpad is not affected.  The Linux 4.15 kernel is not affected but later ones are.  I tried it with 4.18, 5.0 and 5.3 kernels.  I am running Mint 19.2, which uses the Ubuntu kernels."
1822394,2021-01-08 21:25:47 UTC,I did some distro hopping with my XPS 15 9575 (BIOS 1.13.0)
1822394,2020-09-29 20:38:11 UTC,Thanks so much!
1822394,2020-09-29 20:18:19 UTC,acpidump on latest (1.13.0) firmware.
1822394,2020-09-29 16:48:25 UTC,Thanks Joe!  By chance can you upgrade to current BIOS too and get that dump again?  There is that workaround now (blacklist intel-vbtn) which you should be able to use now if you have no other problems with current firmware.
1822394,2020-09-29 15:37:04 UTC,1.2.0 firmware acpidump attached
1822394,2020-09-29 14:21:45 UTC,To anyone who has been affected - there is a discussion going on the kernel mailing lists regarding this issue and it would be helpful if you can provide an acpidump.  You can attach it to this bug (or file a kernel bugzilla and attach it there).
1822394,2020-09-29 01:09:15 UTC,A very similar bug has started affecting me since I upgraded to Ubuntu 20.04.
1822394,2020-09-13 02:55:02 UTC,Recently installed Arch Linux and I am no longer encountering this issue at all.
1822394,2020-08-12 04:54:25 UTC,"I wonder if this commit helps:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cfae58ed681c5fe0185db843013ecc71cd265ebf"
1822394,2020-07-31 16:17:51 UTC,Same here. Thank you guys for finding a fix ;)
1822394,2020-07-24 16:17:50 UTC,"Just commenting to say I have the same problem with Dell XPS 15 2-in-1 9575, BIOS version 1.12.1. The problem was indeed fixed with blacklisting intel_vbtn. Using Fedora 32."
1822394,2020-05-20 13:29:14 UTC,"@Mario Limonciello Sorry, I am a bit out of the loop. Does #61 solve the issue? And if so, are there negative aspects of blacklisting intel-hid?"
1822394,2020-04-10 14:31:15 UTC,"Looking at the dmesg from #30, it's actually intel-hid.  Here is how to blacklist: https://askubuntu.com/questions/110341/how-to-blacklist-kernel-modules"
1822394,2020-04-10 00:09:48 UTC,Can you check if you have intel-vbtn or intel-hid driver loaded? I would think intel-vbtn.
1822394,2020-04-09 23:19:40 UTC,"Booting with acpi=off fixes this, so I am thinking a workaround could be to ignore the tablet ACPI events ex ""video/tabletmode TBLT 0000008A 00000000"". Not sure if it is possible to selectively disable ACPI event handling just yet though."
1822394,2020-04-09 20:46:18 UTC,Running into this issue on XPS 9575 with Ubuntu 18.04. My solution so far is to flip the screen into tablet mode then back into laptop mode to get the keyboard working.
1822394,2020-02-10 22:49:37 UTC,"Just checked, issue persists in 5.6.0 RC1 Kernel, Bios 1.10.0, Ubuntu 20.04.
Closing laptop lid while at login until suspend occurs and then immediately resuming from suspend appears to enable the keyboard and touchpad."
1822394,2020-02-02 22:01:38 UTC,"I am running BIOS 1.10.0, Kernel 5.5, Ubuntu 20.04 (development) and am getting the same issue. The duration appears to vary for the keyboard and track pad to activate, sometimes it is longer or shorter than 13seconds stated above.
I am also running 9575."
1822394,2020-01-22 21:22:39 UTC,"I am still experiencing the issue after updating the BIOS firmware to version 1.10.0, on Ubuntu 19.10 (kernel 5.3.0-26)."
1822394,2020-07-15 20:40:52 UTC,Same problem here with a Dell XPS 15 2 in 1 9575. BIOS version 1.11. Problem fixed with blacklisting intel_vbtn in /etc/modprobe.d/
1822394,2020-01-08 21:00:42 UTC,"Not sure if it matters, but I just rebooted and the wait time at the login screen is actually approx. 13 secs, not 30"
1822394,2019-04-01 03:52:25 UTC,"will try the ubuntu sessions tomorrow.  I normally run the gnome (wayland) session, but have keepass2 in startup applications.  Believe that it is running via xwayland, and its approximately when keepass2 starts up and/or gains focus that my laptop touchpad/keyboard start working again."
1822394,2019-07-30 07:48:41 UTC,This is information from Dell support team about 4.15 working and others don't
1822394,2019-07-30 10:03:10 UTC,user report:
1822394,2019-07-31 14:23:30 UTC,I believe I have a workaround provided by a kernel engineer I was discussing the issue with.
1822394,2019-07-31 14:36:25 UTC,That's interesting to me. Yes the EC will emulate an PS2 mouse until the OS brings up the I2C controller. I would think you can accomplish a similar result by blacklisting psmouse potentially.
1822394,2019-08-07 17:10:40 UTC,"Apologies, comment #32 is incorrect, this worked a couple times but the problem is still present intermittently. I have since downgraded to BIOS v1.2.0 to avoid the issue."
1822394,2019-08-08 15:18:23 UTC,#32 is not working for Precision
1822394,2019-09-27 10:50:43 UTC,It's worth mentioning that even with the downgraded bios the mouse cursor frequently gets stuck requiring a screen flex to fix.
1822394,2019-10-21 18:16:34 UTC,"Is there any hope that this will ever be fixed because as Bryn points out at #36 the temporary ""fix"" of downgrading the BIOS is far from satisfying."
1822394,2019-10-22 01:44:22 UTC,I can only imagine that it must be a small proportion of Dell systems affected. Otherwise we would see more bug reports and interest here...
1822394,2019-10-22 01:56:16 UTC,"XPS 9575 isn't (currently) available for purchase with Ubuntu.  So yes, it's below the radar for something that is typically tested, tracked, or fixed from a BIOS or validation team perspective."
1822394,2019-10-22 02:27:50 UTC,Yeah it sounds like the XPS 9575 is the main model affected. Also Precision 5530 (comment #14).
1822394,2019-10-22 14:21:04 UTC,"5530 2-in-1 also isn't available for purchase with Ubuntu, so same boat."
1822394,2019-10-24 18:14:28 UTC,The thing is I am really afraid of upgrading the BIOS just to give it a shot because of this:
1822394,2019-10-30 13:43:34 UTC,I have a workaround on linux(its not ideal).
1822394,2019-11-02 16:37:16 UTC,@ryder-tim Thanks for letting us know. As far as I understand your workaround is meant for people running the old 1.2.0 BIOS (in order to avoid the more serious bug of no registered input at login) and your workaround only fixes the trackpad issues associated with BIOS v. 1.2.0. Is that correct?
1822394,2019-11-03 22:18:26 UTC,@Peter_Lustig
1822394,2019-11-22 18:20:22 UTC,#43 does not work for me (latest v. of Fedora 31) but appeared to be working for a short time before upgrading from Fedora 30 to Fedora 31 (most likely it never worked though and it was a placebo effect).
1822394,2019-07-29 09:01:20 UTC,Can you confirm linux kernel v4.15 doesn't have this issue?
1822394,2019-07-28 17:19:32 UTC,"Hey everyone,"
1822394,2019-07-31 13:32:28 UTC,I can confirm I have encountered this issue with BIOS v. 1.6.1 from 21 Jul 2019
1822394,2019-05-13 09:25:41 UTC,"There is symptom that if you wait for 30 seconds, input devices will start to work again, without flipping hinge. Also closing lid to sleep laptop and wake it again will work also. System engineer from Dell reported that default kenrel 4.15 will not have this problem, every other higher version will have it, including latest main stream version."
1822394,2019-04-01 04:03:48 UTC,In that case please also try (temporarily) uninstalling keepass2. Does that avoid the bug?
1822394,2019-04-01 04:07:48 UTC,"Actually, a big problem I can see is that your journal.txt (system log) is full of:"
1822394,2019-04-01 14:09:47 UTC,Tests this morning seem to show that the internal devices get enabled right after any input from an external device on the gdm screen.  So choice of session isn't influencing anything.
1822394,2019-04-01 14:22:06 UTC,"additionally, forcing gdm to use X11 via `WaylandEnable=false` in /etc/gdm3/custom.conf displays the same bug behavior."
1822394,2019-06-24 07:26:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822394,2019-04-06 16:32:06 UTC,"I have the same issue, glad its not just me. The keyboard and touchpad only work once the hinge has been opened over 180degrees even after ive logged in so at least i have a work around till we get a proper fix."
1822394,2019-04-06 16:32:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822394,2019-04-09 15:35:50 UTC,"Same problem Precision 5530 2-in-1 with 1.4.8 bios. In my case touchpad is always working, keyboard will sometime came after 15-20 seconds. Closing and opening lid will fix problem. Also if you enter password with on screen keyboard (touchscreen) and get to gnome keyboard is working again. Ubuntu 18.04 kernel 4.18, 4.19, 4.20 and 5"
1822394,2019-04-10 01:49:15 UTC,Is is possible to downgrade the BIOS at all?
1822394,2019-04-04 22:00:19 UTC,"Perhaps this is somehow related to the convertible lid hinge.  Ordinarily when the laptop is in ""tablet"" mode (hinge open > 180 degrees), the keyboard and touchpad are disabled.  Even more reliably than using an external device, switching into and then back out of tablet mode by opening/closing the hinge seems to restore keyboard/touchpad functionality.  Not sure why they appear to work until the gdm screen though, or why sometimes using an external device causes them to work again."
1822394,2019-04-10 05:47:51 UTC,"downgrading on precision to 1.0.5 (last available), keyboard will work again - so BIOS bug"
1822394,2019-04-10 05:25:49 UTC,downgrading to the 1.2.0 bios on xps 9575 appears to be working properly (tested 3 reboots with no issues)
1822394,2019-11-23 23:02:34 UTC,"#46  Still working for me, have not had the issue since I made that change.  I'm on Fedora 31 as well, fully up to date. Maybe I have just been lucky so far."
1822394,2019-05-03 15:23:32 UTC,"FWIW a few other messages pop up to me in the above logs as suspicious to the described symptoms, especially with keyboard working in cryptsetup."
1822394,2019-05-01 13:02:07 UTC,"I have reported already problem to Dell, but apparently they are not doing anything about this. Only update for WD19. If more people report it, may be they will start to work. Will try to connect with notebookcheck to bring some fuss up. I am not using windows at all and this is big problem for me."
1822394,2019-04-01 02:53:26 UTC,"> If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again.
"
1822394,2019-04-30 19:14:23 UTC,I have the exact same issue on Fedora 30.  Bios 1.5.1 came out today and has the same exact issue.
1822394,2019-04-15 02:31:25 UTC,"^^^
FYI that would be bug 1824216."
1822394,2019-04-14 05:38:52 UTC,"OK, after compiling 5.0.7 mainline + Ubuntu Patches + this patch from here (https://patchwork.freedesktop.org/patch/296411/) to fix the link training issue for my laptop panel, I am able to boot with modesetting."
1822394,2019-04-14 04:19:59 UTC,"I also run a Dell XPS 9575 2 in 1, with BIOS 1.40 and my system is *not* exhibiting this particular problem after a fresh 19.04 install.  Keyboard and mouse work fine with GDM, but this is also after booting with the nomodeset kernel boot parameter."
1822395,2019-04-05 16:32:48 UTC,I uploaded a gnome-shell crash with oops id 1f2683ee-57bf-11e9-a367-fa163e102db1 but data collection was just performed after the upgrade.
1822395,2019-04-01 15:11:15 UTC,Are there any crash files from around the time of the upgrade in /var/crash?
1822396,2019-03-30 01:29:00 UTC,Marking as release gating; issue prevents changing an interface from data to pci-pt
1822396,2019-07-24 14:07:44 UTC,I just reproduced this in ironpass-7-12.  Previous attempts to reproduce in wildcat_71_75 was unsuccessful.
1822396,2019-07-24 17:13:05 UTC,"During the unlock, the stx-openstack application will only be reapplied if it is currently in the applied state.  If it is currently applying, then it will skip reapplying, so will not generate the required helm overrides.  See _reapply_system_app in sysinv."
1822396,2019-07-25 14:52:37 UTC,Adding the stx.containers label as this is a generic application apply issue; it's not specific to networking
1822396,2019-08-06 15:45:55 UTC,This issue will be addressed by the changes being made for https://bugs.launchpad.net/starlingx/+bug/1837750.  Marking this as a duplicate.
1822396,2019-08-23 17:48:30 UTC,Duplicate bug has been addressed in master & the r/stx.2.0 branch.
1822398,2019-05-23 06:44:04 UTC,"Resolve as invalid since the log is already included in kern.log
Please re-open the issue if there is any further work need be done."
1822398,2019-05-20 07:36:51 UTC,"I could find etcd log in kern.log. And kern.log is included in collect log, so it should not affect debug.
Hi Ghada,
I prefer to resolve the issue as invalid. Do you agree on it? Thanks."
1822398,2019-05-17 06:51:29 UTC,"Pick up the issue as it is not assigned yet. Per Bart's comment, etcd logs are in kern.log already. It seems we should be able to resolve the issue directly. Will double check it and update it."
1822398,2019-03-30 01:36:12 UTC,Marking as release gating; medium priority - logs are needed for debugging.
1822398,2019-04-01 12:15:00 UTC,I believe the etcd logs are going to /var/log/kern.log already:
1822400,2019-05-30 04:17:17 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1822400,2019-03-30 04:19:51 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We noticed that you were installing the LTS version of Ubuntu using an older version of the installation media.  The latest point release of 16.04 is 16.04.3. Please try installing from that version of the installation media and see if that resolves your issue. Thanks in advance!
1822405,2019-03-30 08:25:37 UTC,Seems like you installed redis and it does not start - maybe you have an old config file around that breaks it? Look at journalctl --unit redis and see what the log says.
1822405,2019-03-30 10:48:23 UTC,It says
1822405,2019-05-30 04:17:21 UTC,[Expired for redis (Ubuntu) because there has been no activity for 60 days.]
1822406,2019-03-30 08:32:40 UTC,"Fixed in revision b00413b7d6b719c249edbd291ec264ff2e2e3230
https://git.launchpad.net/kicad/patch/?id=b00413b7d6b719c249edbd291ec264ff2e2e3230"
1822407,2019-03-30 08:30:57 UTC,"To reproduce (use a machine with fast CPU...), on xenial as your host:"
1822407,2019-03-31 02:38:34 UTC,"I would suggest at minimum including virtio_blk.ko in the initrd that's downloadable in the directory, so people can skip running half the installer to have it be present."
1822407,2019-07-12 09:38:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822408,2019-05-22 20:31:54 UTC,Thanks JP!
1822408,2019-05-22 16:28:12 UTC,"@Wayne,"
1822408,2019-05-22 14:51:26 UTC,"Yes, only on windows.  I also tested Michael's patch and it did resolve the issue.  Please cherry pick your commit when you get a chance so we can fix this in the 5.1.3 release.  Thanks."
1822408,2019-05-22 14:11:05 UTC,"My fix is very similar to Michael's patch.
It can apply to the 5.1.3 branch, but I did not see this issue in 5.1.3 branch.
Did you?"
1822408,2019-05-22 12:40:04 UTC,"@JP, can you cherry pick your patch to the 5.1 branch or is it only applicable to the master branch?  If it's master only, I can apply Michael's patch to the 5.1 branch."
1822408,2019-05-21 20:52:47 UTC,"@Anton, I don't think this is a bug.  Try enabling the ""Always show crosshairs (not in Legacy)"" option on the ""Display Options"" panel in the symbol editor ""Preferences"" dialog."
1822408,2019-05-22 04:39:42 UTC,"@Wayne if you don't know please watch the video. I try to demonstrate it, how it correlates. Main problem is axes disappears and visual center of canvas are lost. And how place symbol with relaton with lost visual centre of canvas. How it places in eeschema?"
1822408,2019-05-21 21:43:54 UTC,Looks like adding
1822408,2019-05-21 21:17:12 UTC,"@Wayne, enabling the ""Always show crosshairs (not in Legacy)"" option also makes the blue axes disappear in the symbol editor. This is a bug that is not present in the footprint editor (note the blue axes against the black background are difficult to see)."
1822408,2019-03-30 10:57:22 UTC,It also happens when changing the Grid Style in Symbol Editor Display Options.
1822408,2019-05-22 09:19:22 UTC,"Fixed in revision f18807ea0fc38d364af9047e931aa58540e2727c
https://git.launchpad.net/kicad/patch/?id=f18807ea0fc38d364af9047e931aa58540e2727c"
1822408,2019-03-30 12:05:15 UTC,+1
1822410,2019-08-07 10:26:36 UTC,All the options are described in the documentation. Please read them. You find them also on the web page.
1822413,2019-06-02 04:17:24 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1822413,2019-04-02 07:30:58 UTC,"Hello,"
1822414,2019-04-01 16:00:00 UTC,"My plan is to give the date-select widget a readOnly mode so the value may be displayed as a string instead of a disabled selector, both for consistency and since strings are easier to read."
1822414,2019-04-01 16:52:24 UTC,Changes pushed:
1822414,2019-05-26 18:35:56 UTC,"Looks great, Bill.  Thanks for this!  Signed off and rebased branch here: user/sandbergja/lp1822414-ang-date-select-disable"
1822414,2019-07-31 15:02:47 UTC,"I've pushed this to master after rebasing, correcting the authorship of the rebased patches, and adding a follow-up. Thanks, Bill and Jane!"
1822414,2019-07-31 16:19:55 UTC,"Thanks for catching my authorship error, Galen.  Taking credit for Bill's work!"
1822415,2019-07-15 13:37:02 UTC,Setting this to INVALID since we haven't been able to reproduce it in ten runs with current code  via https://review.opendev.org/#/c/670339.  We can re-open if this starts happening again.
1822418,2019-04-16 17:52:17 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1822418,2019-04-17 10:14:35 UTC,The error in the log is
1822421,2020-07-13 13:24:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822422,2019-04-15 17:51:52 UTC,"Not release gating; marking as low priority.
This appears to be an issue if the configured filesystem size is close to the actual filesystem size, the resize doesn't succeed.  This is likely a day 1 issue and can be addressed by a configuring a larger fs size."
1822422,2019-04-11 14:25:21 UTC,"The test lab config the database size is 38, which seems make"
1822422,2019-04-01 17:38:20 UTC,What is triggering the filesystem resize?
1822422,2019-04-01 17:38:04 UTC,From Wei Zhou:
1822422,2019-04-03 17:53:26 UTC,Need more information from the reporter
1822426,2019-04-08 03:18:21 UTC,"uname -a: Linux Imagined 4.20.17-042017-generic
NVIDIA Driver Version: 418.56"
1822426,2019-05-20 03:14:10 UTC,It's no longer needed if the issue is fixed.
1822426,2019-05-20 03:00:39 UTC,"Though I closed report, I can still test 5.2-rc1 if feedback is needed/desired."
1822426,2019-05-20 02:56:09 UTC,I apologize for not responding sooner. This issues was fixed a few days after reporting the issue. The current 5.0.0-15 is working fine and I agree this must have been a temporary kernel regression. I will close the bug.
1822426,2019-05-20 02:48:53 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.2-rc1 kernel [0]."
1822426,2019-05-20 02:20:17 UTC,"Per comment #17, it sounds like this was just a kernel regression."
1822426,2019-05-20 02:18:06 UTC,If your issue is just timidity then that is bug 1793640.
1822426,2019-05-18 14:54:11 UTC,"FWIW, I ran into this after updating to 19.04 from 18.04.
Audio working fine with HDMI (yay) but not with back panel audio (boo)
unless I ran aplay as root, e.g.
sudo aplay -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Front_Left.wav"
1822426,2019-04-09 01:24:36 UTC,Sound is still working today with the 4.20.17 kernel.  I will give it another day before I draw any conclusions.
1822426,2019-04-08 01:56:59 UTC,"Darin,"
1822426,2019-04-04 02:22:04 UTC,Thanks. It looks like the audio driver in the kernel is broken/confused by suspend and resume:
1822426,2019-04-05 03:18:44 UTC,"According to the log, when problem happens, the Nvidia hdmi codec doesn't response the HDA controller, Usually it is nvidia graphic driver's issue."
1822426,2019-04-05 01:51:53 UTC,"Cristian,"
1822426,2019-04-05 01:50:59 UTC,"Cristian,"
1822426,2019-04-04 17:56:27 UTC,"Looks like my problem was unrelated to this issue, it was actually caused by timidity blocking the physical sound device."
1822426,2019-04-04 08:50:41 UTC,"I also noticed this, my laptop's integrated Intel audio device is also missing from pulseaudio(both as input and output), but I can see other HDMI or USB sound devices I may have attached and I can switch to them and they work as expected."
1822426,2019-04-04 02:25:15 UTC,"Separately, the ""tick"" and ""thud"" may be related to bug 1821663."
1822426,2019-04-04 02:23:08 UTC,Can you please try some older kernel versions and tell us if any of those avoid the bug?
1822426,2019-04-01 02:57:54 UTC,1. Please reproduce the problem and then while sound is not working run:
1822426,2019-04-04 00:41:55 UTC,Journal file when sound failed after resume.
1822426,2019-04-03 03:18:36 UTC,"Not sure if recent updates have fixed the issue, but problem has not appeared after several sleep and awake events.  I will ensure to post details and try the above edit if problem recurs."
1822426,2019-04-06 16:24:10 UTC,"I still lost sound after setting ""realtime-scheduling = no"" in /etc/pulse/daemon.conf."
1822433,2019-04-01 15:17:13 UTC,Here's a more complete error message:
1822433,2019-03-30 20:19:28 UTC,"Exception during installation:
Mar 30 17:38:43 ubuntu /plugininstall.py: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 70: invalid start byte
Mar 30 17:38:43 ubuntu /plugininstall.py:"
1822434,2019-03-30 18:02:54 UTC,How does it work currently?
1822434,2019-03-30 18:17:15 UTC,"It does nothing in labels, but have the described behavior in parts/symbols."
1822434,2019-03-30 18:19:45 UTC,I said that (and expecting this behavior) because R shortcut rotate both: symbols and label.
1822434,2019-03-30 20:22:53 UTC,"Will probably come for free with the modern toolset, so tentatively setting the milestone to 6.0.0-rc1."
1822434,2019-04-26 17:01:08 UTC,Implemented in my eemodern branch.
1822434,2019-04-26 17:18:50 UTC,"@Jeff, just test the release branch 201904252302+d89d0e6~86~ubuntu16.04.1
It allow rotate the labels just after placed. Should be interesting allow rotate and mirror during the place (if possible).
This will make the procedure of place a new label, with the correct orientation, quicker."
1822439,2019-03-30 19:57:36 UTC,Note: bluetooth does work in the same session: cli commands and blueman-applet allow using Bluetooth in the same session no problem.
1822439,2020-09-04 12:13:34 UTC,"Thank you for your bug report, gnome-control-center isn't meant to be used outside of GNOME but you could still try to report the issue to the upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues"
1822442,2019-08-23 07:53:45 UTC,Good!
1822442,2019-08-23 02:50:20 UTC,This should be resolved now by efc0325e1
1822442,2019-04-03 08:14:19 UTC,"I am also affected by this bug, is it possible that this is related to this other zooming issue: https://bugs.launchpad.net/kicad/+bug/1822617"
1822442,2019-11-17 03:18:19 UTC,Excelent!
1822442,2019-03-31 06:22:34 UTC,"I'm not a dev, but just to add some clear repro instructions:"
1822442,2019-03-30 21:45:39 UTC,"Problem when scaling with centering on the cursor. When I make the maximum reduction, it has a limited zoom and, of course, the canvas has limited dimensions. As you can see in the video, when the cursor goes beyond a certain invisible border when scaled, it automatically returns to the invisible borders of this rectangle. Looks like a bug. If the canvas zoom is limited and the size, respectively, too, why make this invisible border? Pay attention to scrolling. Runners should be the full width of the scroll bar when the zoom is minimal."
1822442,2019-03-30 21:37:01 UTC,"Application: kicad
Version: (5.1.0-rc2-26-g643d884fd), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.63.0 OpenSSL/1.1.1a zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.34.0
Platform: Linux 4.19.8-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.63.0
    Compiler: GCC 8.2.1 with C++ ABI 1013"
1822442,2019-03-31 07:29:29 UTC,"About the fact that the space outside the frame of the sheet is not used I can argue with you. EESchema, as for me, is used as a standalone schema editor - as a draft. I create one scheme in it, with a cat I make into it any changes to the copy made, so that it can be traced to what was at the beginning and at the end. As you can see in the video, zoom has limitations for zooming in and out - that's good for me. Why bother with something when there is a rather large margin to reduce. As I measured the dimensions of the canvas in real units of about 7,500 mm by 3,500 mm. This is quite a lot. And, as for me, this is quite enough. What happens if this invisible border is extended to the size of the canvas? It is clear that if you fill the entire canvas with elements, here the limit is the size of the RAM."
1822446,2019-04-01 04:31:21 UTC,"Thank you. I don't know if you know anything about guitar but it sounds
like a distortion pedal was activated. Overdriven sound. The volume was low
and I was watching a YouTube video in firefox. It started the distorted
sound in the middle of the video. I paused it then left. Came back about a
half hour later hit play and it played fine. It has done this only twice.
Again, thanks for the help and thanks for Ubuntu."
1822446,2019-04-01 04:16:36 UTC,Although maybe you're not talking about distortion in the same way I am. It's possible this is bug 1821663 so please try an older kernel version like 4.18...
1822446,2019-06-01 04:17:17 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1822446,2019-04-01 03:52:33 UTC,"The whole system is brand new including cables. I've used ubuntu 18.04 on
this machine since Christmas. No problem at all. Nothing was changed except
the format and install of 19.04beta."
1822446,2019-04-01 03:27:38 UTC,The most likely cause of distortion is a bad connection or bad cable on the headphone jack.
1822446,2019-04-01 04:14:32 UTC,I have experienced distortion with many brand new cables in the past. And sometimes it only happens when they are twisted (e.g. a mismatched connection between 3/4 pin jacks).
1822454,2019-03-31 08:37:53 UTC,this probably won't land for 2.5.4 but we don't have a 2.5.5 target opened up yet.
1822454,2019-03-31 11:59:54 UTC,https://github.com/juju/juju/pull/9987 is a PR for 2.5
1822454,2019-04-03 10:38:06 UTC,https://github.com/juju/juju/pull/9996/ merged this into develop
1822455,2019-10-30 22:10:22 UTC,"Hi,
I'm glad it worked for you :))
Remember that you'll only need a few zooms:
zoom 16,17 for cities and a zoom 12,13 for not cities
Best regards."
1822455,2019-11-04 00:57:32 UTC,"Quick update here. Referring to the #7 reply above, it took until now to finish moving the 434,095 tiles onto the phone via the USB wire. Yes, that was 101 hours of non-stop file transfer. Files were going in fairly quick at the start, but it was slowing at a constant rate. Towards the end, it was going at about a rate of 2 seconds per image file."
1822455,2019-10-31 18:19:40 UTC,"Hi,
No, run a OSM server in a phone would be so so so heavy.
Even if the map doesn't load because of your connectivity, you'll see the
blue line and you just have to follow it and the instructions. IMHO is
enough.
Remember that uNav is caching the maps in the current runtime, then you
could check the path and they will load without connectivity.
A hug.
--
Costales."
1822455,2019-10-30 22:41:20 UTC,"@costales I'm writing from a position of ignorance with what I say below, so I won't have my feelings hurt if this is a terrible idea, but..."
1822455,2019-10-30 20:02:32 UTC,"It worked! Using the instructions on https://openmaptiles.com/server/ and using the local URL of http://localhost:8080/styles/osm-bright/ in the JTileDownloader apps ""Alt. Tileserver:"" textbox worked. I guess I could have done it for osm-bright/ positron/ klokantech-basic/ or dark-matter/ since all four map styles come with that docker thing."
1822455,2019-09-17 21:36:45 UTC,"Hi Marco,"
1822455,2019-10-29 14:23:21 UTC,Just an update to my #4 comment:
1822455,2019-10-28 22:33:56 UTC,"Ha, like the way the multi-trillion-dollar Google company lets users download offline maps ""for free""."
1822455,2019-09-17 10:40:28 UTC,I tried to install offline maps but without success. It's not 'user friendly' for an unskilled like me. So the chance to select the map directly from the App would be really appreciated. I'm quite happy  about the uNAV and aware that is difficult to improve it.
1822455,2019-03-31 09:32:09 UTC,"Thanks for the feedback.
I would like to implement it, but this need vector maps and local routing library in specific language, then it's not easy :(
I'll keep the bug as reminder.
A hug!"
1822455,2019-10-29 21:15:57 UTC,"Hi,
I'm afraid that all servers listed in jTileDownloader are banned,
because this method is so aggressive for the tiles map server.
You should enter a custom URL with another free OSM server, which
allow you to download so much tiles.
As I saw you control Docker, you could install a local OSM server:
https://github.com/Overv/openstreetmap-tile-server
The final tiles are image files in .png format.
A hug
--
Costales."
1822462,2020-03-01 03:21:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822463,2019-05-01 07:19:52 UTC,"Well, so far the problem is pretty limited, and only those with the older us-controls sticking with DEV=default would experience the bug. And the simple work-around is to update to the fixed version in the ppa, re-save the configuration, and autojack should be happy after that."
1822463,2019-06-13 19:24:12 UTC,This bug was fixed in the package ubuntustudio-controls - 1.9.1
1822463,2019-05-01 19:28:00 UTC,line 371 and it's if statement have been removed. Please try the autobuilds version again. I think I was trying to be too smart with that anyway. It assumes there is always more than one device when there is a USB device... bad idea.
1822463,2019-05-01 15:14:36 UTC,"On Wed, 1 May 2019, Ross Gammon wrote:"
1822463,2019-04-29 03:10:40 UTC,"@rosco2 Should we make this an SRU as well, or do you feel a simple upload to the backport PPA would suffice?"
1822463,2019-04-27 11:36:19 UTC,"Hi Len,"
1822463,2019-04-27 17:44:17 UTC,"On Sat, 27 Apr 2019, Ross Gammon wrote:"
1822463,2019-04-27 06:43:21 UTC,Ross please check new version build in autobuilds: https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild
1822463,2019-04-26 17:06:39 UTC,"That is a bug. for sure, Line 367 or 536 is incorrect."
1822463,2019-04-26 16:48:38 UTC,@rosco2 Could you try the same steps with the checkbox in QJackCtl set to not shut down Jack at quit?
1822463,2019-04-26 15:51:36 UTC,"It's important to note that QJackCtl is set to stop Jack upon quit by default. This should probably be disabled prior to quitting QJackCtl, as Autojack probably doesn't like it when QJackCtl shuts down Jack prior to a reboot."
1822464,2020-04-25 20:26:47 UTC,This bug is also present during 20.4 installation.
1822464,2021-02-03 16:53:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822467,2020-03-28 18:01:47 UTC,"Just a thought, but in the case of using the NetworkManager plugin where I'm not certain you can easily modify the command line args (I've not looked into this at all)- I wonder if Ubuntu setting the priority similar to what Fedora is doing and providing a default gnutls configuration for OpenConnect that mirrored the default priority OpenConnect uses wouldn't be ideal. Seems like the most compatible solution to get the same behavior out the NetworkManager function or using it from the command line."
1822467,2020-03-28 17:22:44 UTC,"It's not an immediate fix for anyone, but we are working on a patch set which will allow the user to override the ciphersuite priority string from the command line, so that future issues related to ciphersuite incompatibility don't require recompilation to fix."
1822467,2020-03-28 15:30:17 UTC,"I'm not sure this ""fixable"" on Ubuntu with the standard build of openconnect, at least not by messing with system default priorities for gnutls. Correct me if I'm wrong but I've done some digging this morning and comparing the openconnect build on ubuntu 19.10 against the fedora build the main difference with regards to the priority strings is that the fedora build is specifically checking for a system or openconnect default policy:"
1822467,2020-03-28 03:39:38 UTC,"Any solution to this that doesn't involve building from source?  I have this problem in Ubuntu 19.10. Openconnect works fine in 18.04, but I get a TLS error in anything newer."
1822467,2020-03-28 09:56:13 UTC,On Fedora latest stable enabling legacy crypto policies solves this for me. I’m on my phone and haven’t spent a lot of time googling how to do this for Ubuntu but here’s the fedora docs for reference:
1822467,2019-04-06 01:45:50 UTC,"I've read through the bug report linked above and have tried building OpenConnect with +SHA256 added with no luck. I may be missing something else that was done to get it working. I do know if I build against gnutls 3.5.18 it does work so it does look like the priority string change going to 3.5.19 is likely the problem as discovered in that bug report and I'm doing something wrong building it, I guess."
1822467,2019-04-01 10:23:41 UTC,"Er, the latter. On request from the reported, after he attached a tcpdump. I've deleted that and made it public again. And also granted you permissions on the gitlab project so you should be able to see it anyway (amongst other things)."
1822467,2019-04-01 09:44:04 UTC,"@dwmw2, did you delete issue #21? Or make it confidential? I can't see it even when logged in to Gitlab."
1822467,2019-04-01 09:22:13 UTC,Is this https://gitlab.com/openconnect/openconnect/issues/21  ?
1822467,2019-07-24 18:04:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822469,2019-04-01 09:50:06 UTC,"I doubt it will be as simple as described. (Unless we want to add a feature tailored for exactly one usecase.)
You might not want to have tht pads simply copied to the other pcb (Why limit the use for THT pin headers if SMD can get you better results? What about castelated connection points?)"
1822469,2019-08-02 19:18:53 UTC,"At least could be possible copy and past between the Pcbnew canvas and the Footprint Editor canvas. Even change the silk layers and pins manually, it will be useful on this case."
1822469,2019-04-01 15:47:14 UTC,"Well, I thought about this with my use case in head and a relative simplicity of execution. However, your proposition is way more efficient, ambitious and adapted for a professional use."
1822471,2019-04-01 13:27:11 UTC,apport information
1822471,2019-04-01 13:27:20 UTC,apport information
1822471,2019-04-01 13:27:18 UTC,apport information
1822471,2019-04-01 13:27:17 UTC,apport information
1822471,2019-04-01 13:27:15 UTC,apport information
1822471,2019-04-01 13:27:12 UTC,apport information
1822471,2019-04-01 13:27:03 UTC,apport information
1822471,2019-04-01 13:27:09 UTC,apport information
1822471,2019-04-01 13:27:08 UTC,apport information
1822471,2019-04-01 13:27:07 UTC,apport information
1822471,2019-04-01 13:27:06 UTC,apport information
1822471,2019-04-01 13:27:04 UTC,apport information
1822471,2019-04-01 13:27:21 UTC,apport information
1822471,2019-04-01 13:27:10 UTC,apport information
1822471,2019-04-01 13:29:57 UTC,"On 31/03/2019 16:00, Ubuntu Kernel Bot wrote:

> This bug is missing log files that will aid in diagnosing the problem.
> While running an Ubuntu kernel (not a mainline or third-party kernel)
> please enter the following command in a terminal window:
>
> apport-collect 1822471
>
> and then change the status of the bug to 'Confirmed'.
>
> If, due to the nature of the issue you have encountered, you are unable
> to run this command, please add a comment stating that fact and change
"
1822471,2019-04-01 15:09:43 UTC,apport information
1822471,2019-04-01 15:09:32 UTC,apport information
1822471,2019-04-01 15:09:34 UTC,apport information
1822471,2019-04-01 15:09:35 UTC,apport information
1822471,2019-04-01 15:09:36 UTC,apport information
1822471,2019-04-01 15:09:37 UTC,apport information
1822471,2019-04-01 15:09:38 UTC,apport information
1822471,2019-04-01 15:09:39 UTC,apport information
1822471,2019-04-01 15:09:41 UTC,apport information
1822471,2019-04-01 15:09:42 UTC,apport information
1822471,2019-04-02 05:20:03 UTC,Yes spent 8 hours rebooting and hdd fails to overwtite hdd on new install also note no drives for cd rom fails..never had thiz before install 18.04 using it 11 months perfect stable unril upgrade via terminal to 18.10
1822471,2019-04-01 15:09:44 UTC,apport information
1822471,2019-04-01 15:09:45 UTC,apport information
1822471,2019-06-02 04:17:27 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1822471,2019-04-02 12:48:09 UTC,Trying to reboot using fat usb 4gb and ubuntu black screen still no hdd driver or cdrom dead
1822471,2019-04-01 15:09:31 UTC,apport information
1822471,2019-04-01 13:21:55 UTC,apport information
1822471,2019-03-31 14:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822471,2019-04-01 13:21:52 UTC,apport information
1822471,2019-04-02 04:39:17 UTC,Does this happen to 18.04?
1822471,2019-04-01 06:27:50 UTC,"Hello,
the pastebin link is not working. Can you please paste another one?"
1822471,2019-04-01 09:42:57 UTC,Whole boot process failed no boot partition mbr overwritten by 18.10. Reinstalled 18.04/ 14.04 same outcome trying to partition thd sda with 200 MB Of space at front of disk as i speak  with a reinstall of 18.04
1822471,2019-04-01 09:45:10 UTC,All device drivers failed ..grr no boot up
1822471,2019-04-01 09:46:46 UTC,Grub is purple blank screen no loading of kernel
1822471,2019-04-01 09:54:13 UTC,Etx4 in partition#1
1822471,2019-04-01 11:51:02 UTC,apport information
1822471,2019-04-01 11:51:03 UTC,apport information
1822471,2019-04-01 11:51:04 UTC,apport information
1822471,2019-04-01 11:51:05 UTC,apport information
1822471,2019-04-01 13:21:54 UTC,apport information
1822471,2019-04-01 11:51:07 UTC,apport information
1822471,2019-04-01 11:51:08 UTC,apport information
1822471,2019-04-01 11:51:09 UTC,apport information
1822471,2019-04-01 11:51:10 UTC,apport information
1822471,2019-04-01 11:51:06 UTC,apport information
1822471,2019-04-01 11:51:12 UTC,apport information
1822471,2019-04-01 13:21:51 UTC,apport information
1822471,2019-04-01 13:21:50 UTC,apport information
1822471,2019-04-01 13:21:49 UTC,apport information
1822471,2019-04-01 11:51:11 UTC,apport information
1822471,2019-04-01 13:21:48 UTC,apport information
1822471,2019-04-01 13:21:47 UTC,apport information
1822471,2019-04-01 13:21:46 UTC,apport information
1822471,2019-04-01 15:09:46 UTC,apport information
1822471,2019-04-01 13:21:44 UTC,apport information
1822471,2019-04-01 13:21:43 UTC,apport information
1822471,2019-04-01 13:21:41 UTC,apport information
1822471,2019-04-01 13:21:40 UTC,apport information
1822471,2019-04-01 11:51:13 UTC,apport information
1822471,2019-04-01 11:51:15 UTC,apport information
1822471,2019-04-01 11:51:16 UTC,apport information
1822471,2019-04-01 13:21:45 UTC,apport information
1822473,2019-10-17 10:39:18 UTC,I'm unable to reproduce this problem locally on a 16.04 host. Does the problem still reproduce on your host?
1822473,2019-12-17 04:17:22 UTC,[Expired for snapd because there has been no activity for 60 days.]
1822473,2019-12-17 04:17:21 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1822474,2019-03-31 17:27:54 UTC,"Thanks for your report, this is indeed a good idea to disable the buttons corresponding to actions that are actually disabled during installation."
1822476,2019-03-31 15:10:01 UTC,"It should be noted that this only happens when you choose ""Erase disk and install Ubuntu"", the options make more sense in ""Install Ubuntu alongside <current OS>""."
1822477,2019-04-08 04:48:44 UTC,Please provide a description about the bug you’re experiencing. “.” is not a description.
1822477,2019-06-08 04:17:22 UTC,[Expired for grub-installer (Ubuntu) because there has been no activity for 60 days.]
1822479,2019-03-31 15:30:04 UTC,This change was made by a bot.
1822479,2019-03-31 15:46:40 UTC,"For others running into this:
- Hold RIGHT shift during boot (left shift didn't work)
- In GRUB menu go to advanced > generic kernel (not lowlatency)
- Remove all -lowlatency packages"
1822480,2019-06-04 04:17:27 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1822480,2019-04-04 14:14:43 UTC,"I'm not sure what GTK theme I'm using. I did realize, however, that I'm
not using a Snap package. I had to switch to the latest .deb because
Mendeley extension integration wouldn't work with a Snap. I'll determine
more information and resubmit the bug report."
1822480,2019-04-01 19:41:20 UTC,"I am not seeing that in a 18.10 VM with the latest libreoffice snap from the stable channel. The list of fonts has arrows at its top and bottom, scrolling with the mouse wheel and arrow keys works."
1822482,2019-03-31 16:00:57 UTC,3.log
1822482,2019-03-31 16:30:10 UTC,This change was made by a bot.
1822482,2020-04-06 04:42:31 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1822491,2019-05-19 18:28:24 UTC,"It seems you still have the wine packages from https://launchpad.net/~ubuntu-wine/+archive/ubuntu/ppa installed. Unfortunately these 3rd-party packages conflict with the Ubuntu packages, causing your current issue."
1822497,2019-03-31 19:30:42 UTC,"Did you check:
https://answers.launchpad.net/mg5amcnlo/+faq/2460"
1822498,2020-01-20 03:10:43 UTC,"It's trying to copy a link onto itself. You'll need to edit /usr/lib/uck/remaster-live-cd.sh and you'll find the ""cp mtab"" command roughly on line 371. Add a new line before that saying:"
1822501,2020-03-02 12:45:31 UTC,"I decided to ""scratch my own itch"" and submitted a PR upstream."
1822503,2019-09-19 13:29:22 UTC,In precise/esm these CVE were fixed update/released in 0.100.3+dfsg-1ubuntu0.12.04.1
1822503,2019-04-08 13:13:35 UTC,This bug was fixed in the package clamav - 0.100.3+dfsg-0ubuntu0.18.10.1
1822503,2019-04-08 13:03:31 UTC,This bug was fixed in the package clamav - 0.100.3+dfsg-0ubuntu0.18.04.1
1822503,2019-04-08 12:53:32 UTC,This bug was fixed in the package clamav - 0.100.3+dfsg-0ubuntu0.16.04.1
1822503,2019-04-03 21:06:13 UTC,Thank you Marc.
1822503,2019-04-05 22:21:30 UTC,This bug was fixed in the package clamav - 0.100.3+dfsg-0ubuntu1
1822503,2019-04-03 19:25:57 UTC,I'll prepare updates for this.
1822503,2019-04-01 09:56:28 UTC,"Hi Chris,
usually in the past the security Team has done such updates. I subscribed them to get their feedback on the request for a newer clamav version."
1822503,2019-04-08 12:53:27 UTC,This bug was fixed in the package clamav - 0.100.3+dfsg-0ubuntu0.14.04.1
1822508,2019-04-03 03:29:13 UTC,I reinstall hplip with this options:
1822508,2019-04-03 03:32:35 UTC,solved
1822508,2019-04-02 22:58:02 UTC,"> avahi-browse -art
> returns nothing about the printer.
"
1822508,2019-04-01 11:26:25 UTC,"> I use this driver: HP-LaserJet-MFP-m129-m134
"
1822508,2019-04-02 10:05:15 UTC,"Hello David,"
1822508,2019-04-01 23:44:44 UTC," Hello Brian,"
1822508,2019-04-01 23:42:49 UTC,"Hello Brian,"
1822508,2019-04-02 22:39:11 UTC,"Hello,
Yes I try power-cycling the device."
1822515,2020-12-01 02:13:54 UTC,This bug has been closed for over a year. Please open a new bug for any issues in 20.10.
1822515,2020-11-30 09:42:58 UTC,Hi! I have this problem too. I just did a fresh install of Lubuntu.
1822515,2020-04-23 09:34:18 UTC,"I'm on mutter 3.34.3-1ubuntu1~19.10.1 and the bug is there. However, it does work sometimes, but really extremely rarely. I can't figure out what triggers the correct behavior."
1822515,2019-06-24 02:06:21 UTC,It's true that commit f9d6627fe03f68a132501a488f73e08080018115 is released in mutter version 3.32.2 already. Which is also fix released in eoan already.
1822515,2019-06-21 15:43:27 UTC,"The commit is in 3.32.2, needs to be SRUed to disco"
1822515,2019-06-18 10:22:17 UTC,Lenovo MIIX 310-10ICR here also with a Goodix Capacitive TouchScreen. This bug exists here as well. Used to work fine on Ubuntu 18.10
1822515,2019-05-12 12:53:49 UTC,"here you go - its the ""Goodix Capacitive TouchScreen"""
1822515,2019-05-12 13:40:03 UTC,rojtberg's build of the gnome patch fixed it for me too.
1822515,2019-05-12 12:55:14 UTC,I also uploaded a modified mutter package in the GNOME bug report which do fix the issue for me
1822515,2019-05-12 11:04:56 UTC,Could those having the issue give the output of that command?
1822515,2019-04-24 02:29:46 UTC,apport information
1822515,2019-05-11 12:37:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822515,2019-04-24 02:49:24 UTC,I'm using a vanilla ubuntu:GNOME session.
1822515,2019-04-24 02:29:47 UTC,apport information
1822515,2019-04-24 02:29:44 UTC,apport information
1822515,2019-04-23 02:18:36 UTC,"Alexandre,"
1822515,2019-04-20 12:20:52 UTC,I have 3.32.0+git20190410-1ubuntu1 which is supposed to fix bug #1821933.
1822515,2019-04-03 13:20:41 UTC,the issue looks similar to bug #1821933
1822515,2019-04-03 03:11:58 UTC,I have the same touchscreen rotation problem in a Wayland session.
1822515,2019-04-01 15:45:48 UTC,"I don't know whether this touch input issue should be marked as a duplicate of Bug #1822513 as I was experiencing before the ""part of the screen is black"" problem appeared."
1822515,2019-05-11 12:41:36 UTC,"if touchscreen rotation used to work, it is probably this: https://gitlab.gnome.org/GNOME/mutter/issues/581"
1822519,2019-04-01 02:20:15 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648892"
1822523,2019-06-06 03:05:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822523,2019-04-01 04:20:22 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1822523,2019-04-01 02:58:50 UTC,Automatically attached
1822523,2019-04-01 02:58:46 UTC,Automatically attached
1822523,2019-04-01 02:58:53 UTC,Automatically attached
1822527,2019-04-01 03:41:45 UTC,"When you think Wayland is being used by accident, please run:"
1822527,2019-04-02 02:58:37 UTC,I put  WaylandEnable=false in the actual .conf file. I apologize for the misspelling in the report.
1822527,2019-06-01 04:17:36 UTC,[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]
1822530,2019-04-01 05:43:10 UTC,Trying with a different install media (currently using a 32GB SD card via USB reader for the Ubuntu image). Will try a different card.
1822530,2019-04-01 21:52:24 UTC,"Works perfectly on a small (8GB) USB stick, so either something to do with
Sandisk SD card or the reader (tried multiple SD cards)."
1822530,2020-02-14 18:29:17 UTC,The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1822538,2019-07-12 09:14:04 UTC,"Confirmed. To observe the issue, enable dbgsym packages following the instructions at https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Getting_-dbgsym.ddeb_packages, then execute ""sudo apt install uno-libs3-dbgsym""."
1822539,2019-04-01 07:05:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648906"
1822539,2019-04-02 11:25:49 UTC,"I was not able to reproduce this bug on master. could you provide some evidence to confirm it.
I have attached a screenshot of the functionality in my environment."
1822539,2019-04-03 01:28:43 UTC,"Sorry, I didn't describe it clearly. This phenomenon appears in the Create Key form in the Create Instance Workflow."
1822542,2019-04-01 07:30:16 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822542,2019-04-01 11:10:44 UTC,nested kvm is disabled by default on s390x. One can force-enable that by booting with kernel cmdline kvm.nested=1 in /etc/zipl.conf and rerun $ sudo zipl; and reboot.
1822546,2019-04-03 21:03:53 UTC,"Reviewed:  https://review.openstack.org/645491
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=f4aac8ac424f7d57f6ca8ad99ccf96af5038fa7b
Submitter: Zuul
Branch:    stable/queens"
1822546,2019-06-21 13:45:55 UTC,This issue was fixed in the openstack/puppet-tripleo 9.5.0 release.
1822546,2019-06-21 15:23:48 UTC,This issue was fixed in the openstack/puppet-tripleo 8.5.0 release.
1822546,2019-04-01 17:20:04 UTC,"Reviewed:  https://review.openstack.org/645490
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=bfdd73002805ea1f3115f498d835bd238ec348c8
Submitter: Zuul
Branch:    stable/rocky"
1822550,2019-12-10 13:21:44 UTC,"Reviewed:  https://review.opendev.org/649637
Committed: https://git.openstack.org/cgit/x/cloudbase-init/commit/?id=d548fe93dd645b0d0417de132e8a8f83e3dad91f
Submitter: Zuul
Branch:    master"
1822550,2019-04-01 08:41:48 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/648923"
1822550,2019-04-02 01:41:44 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649207"
1822550,2019-04-02 03:34:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649215"
1822550,2019-04-03 14:46:37 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649637"
1822550,2019-06-14 07:34:32 UTC,"Change abandoned by Lucian Petrut (<email address hidden>) on branch: master
Review: https://review.opendev.org/649207
Reason: Duplicate of I350911e4a9e69b8081363a4303a2ec5065711195. Make sure you preserve the change id when sending subsequent patch sets."
1822550,2019-06-14 07:35:14 UTC,"Change abandoned by Lucian Petrut (<email address hidden>) on branch: master
Review: https://review.opendev.org/649215
Reason: Duplicate of I350911e4a9e69b8081363a4303a2ec5065711195. Make sure you preserve the change id when sending subsequent patch sets."
1822550,2019-06-14 07:36:21 UTC,"Change abandoned by Lucian Petrut (<email address hidden>) on branch: master
Review: https://review.opendev.org/648923
Reason: Duplicate of I350911e4a9e69b8081363a4303a2ec5065711195. Make sure you preserve the change id when sending subsequent patch sets."
1822558,2019-05-10 13:30:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658361"
1822558,2019-05-09 13:41:23 UTC,charm-helpers PR: https://github.com/juju/charm-helpers/pull/320
1822558,2019-05-02 11:38:47 UTC,"I think that to allow the neutron-openvswitch charm to silently ignore interfaces that don't exist might introduce unexpected false negatives. Having said that, the behaviour would be inline with that of when mac addresses are used but none found for that host."
1822558,2019-04-02 21:05:09 UTC,"This seems to have a workaround, with more detailed config unblocking the deployment.  Please update the bug, and the SLA level accordingly if this is the case (also confirm here).  Thank you."
1822558,2019-04-04 09:20:24 UTC,I can confirm the workaround (additional 'neutron-openvswitch-octavia' subordinate deployed and related with the Octavia units only - no 'data-port' set there) has worked properly.
1822558,2019-04-01 14:16:11 UTC,I think a part of the issue here is how ``neutron-openvswitch`` handles non-existent interfaces.
1822558,2019-04-01 13:44:20 UTC,Also the logs of OVS It may be interesting to see whether it reports errors.
1822558,2019-04-01 13:29:40 UTC,"Hello Lorenzo,"
1822558,2019-05-17 09:09:12 UTC,"Reviewed:  https://review.opendev.org/658361
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=f7cfbe8bd33e9b1d2c3c99f1969292b665b3c580
Submitter: Zuul
Branch:    master"
1822558,2019-04-01 14:20:26 UTC,"I deployed an additional 'neutron-openvswitch-octavia' subordinate charm just related with the Octavia service which hasn't any 'data-port' set and the deployment went good.
The next step it to activate Octavia to run some test of its LBaaS capabilities to check whether it really works in this configuration."
1822559,2019-09-19 10:09:14 UTC,This issue was fixed in the openstack/networking-odl 15.0.0.0b1 development milestone.
1822559,2019-04-08 12:46:05 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650876"
1822559,2019-07-18 12:02:45 UTC,"Reviewed:  https://review.opendev.org/650876
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=96c6972b9d4d8150ffd991ec3396feb56903b183
Submitter: Zuul
Branch:    master"
1822564,2019-04-03 13:16:54 UTC,Thanks for taking the time to file this bug in Ubuntu.
1822564,2019-04-03 14:37:58 UTC,"Yes, that was it. I was running python3.5."
1822564,2019-06-03 04:17:26 UTC,[Expired for python-markdown (Ubuntu) because there has been no activity for 60 days.]
1822569,2019-04-02 15:08:49 UTC,You can place at the coordinates entered if you don't touch the mouse after clicking Ok.
1822571,2019-09-13 15:07:32 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.1 release.
1822571,2019-09-12 09:33:08 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.1 release.
1822571,2019-07-31 00:57:25 UTC,"Reviewed:  https://review.opendev.org/664600
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=87ba89813397bad46b9b7ce377b4452033a36874
Submitter: Zuul
Branch:    stable/queens"
1822571,2019-07-05 12:51:41 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1822571,2019-07-02 06:36:42 UTC,"Reviewed:  https://review.opendev.org/661763
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=27de28a2c3faaa366ef23670679cc35067e57c0d
Submitter: Zuul
Branch:    stable/rocky"
1822571,2019-06-28 07:47:48 UTC,"Reviewed:  https://review.opendev.org/661566
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=1797d56cc59c2db92b87b8fe2db7b3f80e4279f6
Submitter: Zuul
Branch:    stable/stein"
1822571,2019-06-11 14:08:29 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/664600"
1822571,2019-05-28 14:11:08 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/661763"
1822571,2019-06-06 06:45:42 UTC,This issue was fixed in the openstack/puppet-vswitch 11.0.0 release.
1822571,2019-05-27 08:52:32 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661566"
1822571,2019-05-25 16:54:56 UTC,"Hi,"
1822571,2019-05-25 15:27:34 UTC,"It's unclear why you switched this report from Public to Public Security. Neither the bug description nor the patch indicate a suspected attack vector which could take advantage of it. For example, does this represent a possible denial of service condition which an unprivileged user can exploit?"
1822571,2019-05-23 00:22:24 UTC,"Reviewed:  https://review.opendev.org/650627
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3c5ad2aab98fa9a1ab26cc6c348a64806276e8b9
Submitter: Zuul
Branch:    master"
1822571,2019-04-08 08:16:18 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650627"
1822571,2019-06-07 19:29:51 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.0.0 release.
1822573,2019-04-15 10:45:39 UTC,"Hi Zdonal,"
1822574,2019-04-01 19:02:44 UTC,Fails was caused by #1822670
1822574,2019-04-01 16:40:17 UTC,"Sorry, I'm wrong."
1822578,2019-04-01 19:58:26 UTC,Confirmed on Win 10.
1822578,2019-05-13 21:25:47 UTC,"Fixed in revision 7200f4d7b5669cc03378ba4a8b9382de67f39f09
https://git.launchpad.net/kicad/patch/?id=7200f4d7b5669cc03378ba4a8b9382de67f39f09"
1822579,2019-04-01 12:30:07 UTC,This change was made by a bot.
1822579,2019-04-03 12:13:13 UTC,Adding a test case script to reproduce the bug.
1822579,2019-04-03 12:15:09 UTC,This problem is fixed by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be2d253cc98244765323a7c94cc1ac5cd5a17072. Only Xenial seems to be affected. I'll post an SRU soon.
1822579,2019-04-26 14:31:48 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1822579,2019-05-14 19:08:52 UTC,This bug was fixed in the package linux - 4.4.0-148.174
1822580,2019-08-04 05:42:50 UTC,The domain zeitgeist-project.com has been lost. ((
1822581,2020-04-22 16:53:01 UTC,Do you happen to dual boot to Windows?
1822581,2020-04-22 17:04:53 UTC,"Yes, I have a Dual Boot Setup with Ubuntu as primary System."
1822581,2020-06-18 08:58:53 UTC,It Turned out that the brightness key are working on my system while setting
1822581,2020-06-18 09:24:41 UTC,"Running 5.4.0-37-generic adding ""drm.vblankoffdelay=1 acpi_backlight=vendor"" to my grub config did not work, unfortunatelly"
1822581,2020-06-18 16:42:48 UTC,Interesting.  I came upon this HP form post today that suggest that booting into Windows does something that disables the brightness keys in Linux:
1822581,2020-04-22 15:39:54 UTC,"Hello, Marcel
Is that the same 5.3.0-42 kernel that's not working in your comment #19?"
1822581,2020-06-18 19:05:07 UTC,Can confirm as well!
1822581,2020-06-18 17:41:43 UTC,"Nice! I'll try this as well!
Do you have any special Kernel parameters set?"
1822581,2020-06-18 17:54:58 UTC,"No special kernel parms (at least that would relate to this).  I re-flashed the BIOS by booting into the system utils menu and then choosing ""firmware update"" or some such."
1822581,2020-10-04 07:59:28 UTC,"Seems to be hardware issue indeed.
Tried to upgrade to the latest BIOS — issue has remained."
1822581,2020-07-20 13:55:01 UTC,Why the status update to invalid?  Several people have confirmed this issue.
1822581,2020-07-21 05:43:21 UTC,Doesn't seem to be a software issue.
1822581,2020-08-11 15:44:40 UTC,Shouldn't it not be necessary to do a power reset every time one boots into Windows?
1822581,2020-06-18 17:20:10 UTC,"Confirmed.  I re-flashed the BIOS, then booted back into Linux, and now my brightness keys work again."
1822581,2020-03-20 19:09:51 UTC,"For some reason it now stopped working again...
Don't know why."
1822581,2019-04-26 19:15:53 UTC,Same. No Output for those keys.
1822581,2020-03-18 10:56:00 UTC,I'm so sorry. I did not have the time to reinstall Ubuntu on my machine for testing the kernel.
1822581,2019-04-19 17:30:08 UTC,This change was made by a bot.
1822581,2019-04-19 17:38:47 UTC,"Running scancode -s showed, that there is no scancode passed for those combinations."
1822581,2019-04-22 05:07:06 UTC,"Please use evtest, press hotkeys, and attach its output."
1822581,2019-04-22 08:05:10 UTC,"Here is the output.
I chose the keyboard output since the hp modules didn't generate any output.
The events for VOLUME_UP, VOLUME_DOWN and MUTE are working as expected.
The last two outputs are of the BRIGHTNESS_UP and _DOWN combinations (FN+F4 and FN+F3) and seem to be exactly the same"
1822581,2019-04-23 07:46:25 UTC,"Ok, please attach acpidump."
1822581,2020-03-19 16:45:04 UTC,Now running on 5.3.0-42 and the brightness controls are working!
1822581,2019-04-23 09:50:18 UTC,"HP WMI does generate any output at all for the fn Keys. (Volume seems to be handled by ACPI, since acpi_listen shows those events)"
1822581,2019-04-23 09:34:21 UTC,"""hp_wmi: query 0x4 returned error 0x5"" may just be red herring.
What's the output of evtest when choosing ""HP WMI hotkeys"" instead?"
1822581,2019-05-08 14:51:49 UTC,Any other idea?
1822581,2019-07-09 14:53:53 UTC,"Hello,
I recently bought the 1030 g3 and I noticed that on kernel 5.1.16 the switch works by setting acpi_backlight=native as kernel parameter. Hope it helps"
1822581,2019-11-06 15:19:26 UTC,"Strange. I now tried different Kernels and I just can't get those keys to function.
They just don't create the corresponding ACPI Events..."
1822581,2019-12-04 08:26:50 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1822581/"
1822581,2020-03-13 14:05:12 UTC,"I am sorry, it looks like it actually works when connected to AC. I can't test the kernel right now, but I assume there wasn't any further developement ;("
1822581,2019-04-26 18:57:28 UTC,"Please attach the evtest log, thanks!"
1822583,2019-04-02 00:28:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822585,2019-05-10 09:09:30 UTC,"------- Comment From <email address hidden> 2019-05-10 05:08 EDT-------
I installed a new 19.04, which came with kernel -13. I ran the same tests as before, and did not see any problem. Please see my complete log below for a replay."
1822585,2019-04-12 13:59:37 UTC,"------- Comment From <email address hidden> 2019-04-12 09:56 EDT-------
I added a self-defined vlan device"
1822585,2019-05-10 06:49:27 UTC,"------- Comment From <email address hidden> 2019-05-10 02:43 EDT-------
@Heinz-Werner: when I tested with pre-ga there was no kernel update to install available from our update servers. Will try soon with GA version that we have available."
1822585,2019-04-12 10:16:22 UTC,"Please can you share the output of ""lszdev qeth"", too?"
1822585,2019-05-15 14:05:05 UTC,"Obviously fixed with release kernel, didn't saw it afterwards anymore, hence closing."
1822585,2019-04-12 09:30:53 UTC,"------- Comment From <email address hidden> 2019-04-12 05:28 EDT-------
I installed Ubuntu 19.04 on my z/VM guest:"
1822585,2019-05-15 14:20:55 UTC,"------- Comment From <email address hidden> 2019-05-15 10:16 EDT-------
IBM bugzilla status -> closed, Not reproducable anymore by Canonical"
1822585,2019-04-12 10:08:51 UTC,I just tried with the very latest kernel from disco proposed:
1822585,2019-04-01 13:19:33 UTC,"Mar 29 10:31:45 s1lp15 sudo[1126]: pam_unix(sudo:session): session closed for user root
Mar 29 10:32:02 s1lp15 sudo[1144]: pam_unix(sudo:account): account ubuntu has password changed in future
Mar 29 10:32:02 s1lp15 sudo[1144]:   ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/sbin/chzdev qeth -e c003
Mar 29 10:32:02 s1lp15 sudo[1144]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0)
Mar 29 10:32:02 s1lp15 kernel: qdio: 0.0.c005 OSA on SC bb1 using AI:1 QEBSM:0 PRI:1 TDD:1 SIGA: W AP
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: Using default interface naming scheme 'v240'.
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: Could not set Alias=, MACAddress= or MTU= on eth0: Resource temporarily unavailable
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: eth0: Could not apply link config, ignoring: Resource temporarily unavailable
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: Process 'vlan-network-interface UDEV' failed with exit code 1.
Mar 29 10:32:02 s1lp15 kernel: qeth.6adf49: 0.0.c003: The device represents a Bridge Capable Port
Mar 29 10:32:02 s1lp15 kernel: qeth.cc0c57: 0.0.c003: MAC address 82:80:10:91:6a:a4 successfully registered on device eth0
Mar 29 10:32:02 s1lp15 kernel: qeth.26d434: 0.0.c003: Device is a OSD Express card (level: 0774)
                               with link type OSD_10GIG.
Mar 29 10:32:02 s1lp15 kernel: qeth.f02020: 0.0.c003: QDIO data connection isolation is deactivated
Mar 29 10:32:02 s1lp15 networkd-dispatcher[631]: WARNING:Unknown index 8 seen, reloading interface list
Mar 29 10:32:02 s1lp15 sudo[1144]: pam_unix(sudo:session): session closed for user root"
1822587,2019-04-14 00:32:31 UTC,Something similar happens to me. LP: #1824665
1822587,2020-02-19 14:00:17 UTC,This issue has started recurring again after the Ubuntu update I installed yesterday (18/Feb/2020).
1822587,2020-04-26 09:28:12 UTC,This behaviour has become noticeably worse since the recent updates the last couple days (26 April 2020 today).
1822587,2019-04-14 00:12:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822588,2019-04-01 13:08:23 UTC,Fix committed (Missing closing parenthesis for concat). Revision 1533.
1822588,2019-04-01 13:49:48 UTC,"As I mentioned in my follow-up note, I think you still need to pass 'nil t' to the containing function 'shell-command-on-region'.
The 't' says that 'shell-command-on-region' should replace the
existing text (which is necessary).
The required correction is just to move 'nil t' outside of the concat parentheses..."
1822588,2019-04-04 12:09:27 UTC,"Thanks!
Uday Reddy wrote at about 11:50:47 -0000 on Thursday, April 4, 2019:
 > Yes, noted.
 >
 > ** Description changed:
 >
 > - In the following function in the last line, 'nil t' cannot be arguments to 'concat'
 > - This is a residue from an earlier version when there was no concat.
 > - Solution is to delete 'nil t'
 > -
 > -
 > - (defun vm-mime-display-internal-lynx-text/html (start end layout)
 > -   (shell-command-on-region
 > -    start (1- end)
 > -    ;; (concat vm-lynx-program "" -force_html /dev/stdin"" )
 > -    (concat vm-lynx-program "" -force_html -dump -pseudo_inlines -stdin""
 > -            nil t)))
 > + vm-mime-display-internal-lynx-text/html has a missing closing
 > + parenthesis for concat.
 >
 > ** Tags added: mime
 >
 > --
 > You received this bug notification because you are subscribed to the bug
 > report.
 > https://bugs.launchpad.net/bugs/1822588
 >
 > Title:
 >   Bug in vm-mime-display-internal-lynx-text/html
 >
 > Status in VM:
 >   Fix Committed
 >
 > Bug description:
 >   vm-mime-display-internal-lynx-text/html has a missing closing
 >   parenthesis for concat.
 >
 > To manage notifications about this bug go to:
 > https://bugs.launchpad.net/vm/+bug/1822588/+subscriptions"
1822588,2019-04-04 11:50:47 UTC,"Yes, noted."
1822590,2019-04-02 13:55:20 UTC,Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1693356
1822590,2019-04-09 14:54:32 UTC,"As per upstream, the only way to safeguard the fingerprint data is to run with SELinux, AppArmor or another LSM enabled one.
(link: https://gitlab.freedesktop.org/libfprint/fprintd/issues/16#note_141207)"
1822590,2019-04-10 12:57:04 UTC,It would probably be useful for Ubuntu to have an apparmor profile there
1822590,2019-04-16 01:32:50 UTC,"In Ubuntu, that would be good."
1822590,2019-05-07 17:58:36 UTC,I'll include as a comment my reply to an email from the reporter:
1822590,2019-05-07 17:59:30 UTC,"Incidentally, there's nothing for the AppArmor project to do here -- any confined program will include or not include the fingerprint data as specified in the profile."
1822591,2019-04-03 14:22:53 UTC,"I can reproduce this on current devstack:
stack    20640  2.1  0.6 466476 108520 ?       Ss   10:23   7:32 /usr/bin/python /usr/bin/neutron-dhcp-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/dhcp_agent.ini
root     23941  0.0  0.0 272332  5632 ?        S    10:23   0:00  \_ sudo /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf
root     23944  0.0  0.1 467628 22496 ?        Sl   10:23   0:01      \_ /usr/bin/python /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf"
1822591,2019-04-05 06:40:49 UTC,I switched back from stable/pike-branch to tag 11.0.6 and Im no longer having any zombie-processes after running the complete tempest-test-suite.
1822593,2019-04-04 14:11:51 UTC,"Thanks, that's the same issue than bug #1798166"
1822615,2019-04-01 14:23:23 UTC,I worked around this by
1822615,2019-05-10 13:25:50 UTC,"I've been hit by this and investigated a bit. The problem is related to the fact that debuild (and hence the unit tests) are run as root in the container which tree_run spawns to build the .deb package. I can reproduce the problem for example by jumping in the container and running packages/bddeb manually in /root (where the source tree is placed). The exact same command succeeds if I copy the source tree in /home/ubuntu, chmod it ubuntu:ubuntu and run it from there."
1822617,2019-05-06 21:23:27 UTC,I can verify this on 5.1.2 as well as current nightly
1822617,2019-05-26 15:40:28 UTC,"I can't reproduce.  Seth, do you have a HiDPI monitor?"
1822617,2019-05-26 16:15:27 UTC,Yup.  I can take this one.
1822617,2019-08-22 17:09:57 UTC,"Fixed in revision 85df994eda4caae28049e92d9d48e7d45d160605
https://git.launchpad.net/kicad/patch/?id=85df994eda4caae28049e92d9d48e7d45d160605"
1822617,2019-05-06 20:59:29 UTC,Can anyone else duplicate this.  I don't have a high dpi monitor so maybe it's related to the scaling.  I even made a gtk2 build but no difference from the gtk3 build.
1822618,2019-04-02 21:22:47 UTC,Marking this as incomplete provided that:
1822618,2019-11-20 04:17:56 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1822618,2019-09-20 13:26:28 UTC,We did some changes recently in how MAAS detects that a database connection is broken and need to be reconnected. Do you see the same behavior with MAAS 2.6.0?
1822632,2019-12-05 23:55:26 UTC,"mwhudson, any news about a rebuild of gosu for ppc64le?"
1822632,2020-10-22 13:41:59 UTC,"I get this in focal as well:
ubuntu@ppc64el-focal:~$ gosu /bin/true
gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x000001800a64af58 for symbol `' out of range"
1822632,2020-10-22 13:46:42 UTC,A simple rebuild in focal fixed it for me:
1822632,2020-10-22 14:16:43 UTC,"Confirmed a rebuild also fixes it for bionic:
ubuntu@ppc64el-bionic:~$ gosu
gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000f5fcb4aaf58 for symbol `' out of range"
1822632,2020-10-22 14:17:56 UTC,"groovy is fine, marking that task as fix released"
1822633,2019-04-02 18:08:03 UTC,"I've just built and installed the master branch of gnome-bluetooth (commit b4edf6a8) and didn't see any behavioral change. Since it isn't even possible to pair through bluetoothctl, I wasn't particularly hopeful that an update to gnome-bluetooth would fix things."
1822633,2019-04-01 16:54:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822633,2020-06-05 20:14:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822633,2019-04-03 07:48:47 UTC,I think this issue worths raising to to bluetooth mailing list.
1822633,2019-04-02 20:57:23 UTC,"I've recently found that while pairing with this pen does not work, ""merely"" connecting to the pen does work. That is:"
1822633,2019-04-01 18:08:46 UTC,apport information
1822633,2019-04-01 18:08:45 UTC,apport information
1822633,2019-04-01 18:08:43 UTC,apport information
1822633,2019-04-01 18:08:41 UTC,apport information
1822633,2019-04-01 18:08:39 UTC,apport information
1822633,2019-04-02 02:33:53 UTC,The first thing I would try is to wait for a fix for bug 1822533 in case that helps.
1822633,2019-04-01 18:08:35 UTC,apport information
1822633,2019-04-01 18:08:34 UTC,apport information
1822633,2019-04-01 18:08:31 UTC,apport information
1822633,2019-04-01 18:08:30 UTC,apport information
1822633,2019-04-01 18:08:37 UTC,apport information
1822633,2019-04-01 18:08:28 UTC,apport information
1822633,2019-04-01 18:08:27 UTC,apport information
1822633,2019-04-01 17:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822634,2019-06-01 04:17:33 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1822634,2019-04-02 02:35:01 UTC,Could you please explain in more detail what problem you are experiencing?
1822636,2019-04-08 15:45:57 UTC,Related: Bug #1765739
1822638,2019-06-12 13:42:25 UTC,"change the status to ""incomplete"" and assign it to @ppeng, since @chen-dq couldn't reproduce with a newer version (0530)."
1822638,2019-07-29 23:57:28 UTC,you can re-open it or you can raise a new LP if the issue occurs.
1822638,2019-07-25 17:33:19 UTC,"We have not observed this issue for a while. If it is reproduced, we will collect more information like hardware environment."
1822638,2019-06-18 01:35:04 UTC,We concluded that the DB connection failed. Is there any other conclusion?
1822638,2019-06-17 13:29:35 UTC,The reason for the failure of VM creation may be the failure of DB connection.
1822638,2019-06-14 19:47:16 UTC,"@chen-dq, Did you look at the logs from the May 21st reproduction attempt? Do they provide any clues to what the issue is?  As already noted, this is an intermittent issue, so it's not likely that you would be able to reproduce easily."
1822638,2019-06-12 15:15:01 UTC,"If this issue is reproduced, we will reopen it."
1822638,2019-06-12 09:46:42 UTC,"test environment:
Currently deploying duplex uses the official stable version of iso and helm-charts on May 30:
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190530T152953Z"
1822638,2019-04-02 13:24:28 UTC,"Manually checked:
controller-1:~$ md5sum images/tis-centos-guest.img
68e5dce10f483cf08de436f56b573eb4 images/tis-centos-guest.img"
1822638,2019-05-21 21:23:25 UTC,"Issue was reproduced on
Lab: WP_1_2
Load: 2019-05-18_06-36-50"
1822638,2019-04-23 15:03:12 UTC,Issue is intermittent but is reproducible after enough attempts.  Marking as release gating since the impact is a VM fails to launch and its image is corrupted.
1822638,2019-04-22 19:58:56 UTC,"[2019-04-11 19:23:59,579] 262  DEBUG MainThread ssh.send    :: Send 'nova --os-username 'tenant2' --os-password 'Li69nux*' --os-project-name tenant2 --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default  --os-endpoint-type internalURL --os-region-name RegionOne boot --key-name keypair-tenant2 --flavor d4483929-fc21-44c8-8794-4119fc055aad --availability-zone nova:controller-0 --image d1053800-718a-48bd-8839-e8f2d8565fda --nic net-id=a79ba779-c87a-4870-90f3-68a64ea6f1b1 --nic net-id=38bc5c77-543f-4a24-a27d-e24200eb7352 tenant2-image_root-9 --poll'
[2019-04-11 19:24:29,019] 387  DEBUG MainThread ssh.expect  :: Output:"
1822638,2019-04-22 16:58:01 UTC,"For the reproduced issue in the 20190411T013000Z load, please provide a date and timestamp of when the failure occurred so that the person assigned to this LP can find the right logs in the logs that were provided (ALL_NODES_20190401.114311.tar)"
1822638,2019-04-15 17:49:43 UTC,Issue was reproduced on
1822638,2019-04-03 17:49:16 UTC,"Logs from the openstack pods are not persistent over host reboots/pod recreation yet and, therefore, are not included in collect. Therefore, there isn't enough information to debug this issue."
1822638,2019-04-01 17:23:55 UTC,Was the guest image actually uploaded properly when the error was reported? Did you verify the image checksum  on the system?
1822638,2019-06-06 07:33:12 UTC,"The reproduction environment of this bug is duplex, due to the limitations of the ODC side device,
Currently deploying simplex uses the official stable version of iso and helm-charts on May 30:
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190530T152953Z"
1822644,2019-04-03 21:32:41 UTC,"I've heard this from a few different people. The cli doesn't currently store any log of what it's done, but we could possibly have it do something like that.  I'd like to possibly limit it somehow though, rather than let it grow forever.  Having it check the status of jobs in that log could be really slow though, as it would currently need to do a query for each one"
1822644,2019-04-03 22:28:20 UTC,"Yeah, I can see that being a bit complicated, and just getting a list
of what's currently in progress.,"
1822644,2019-06-10 21:35:40 UTC,SO maybe something like:
1822644,2020-09-21 22:45:58 UTC,"This is now in the latest stable snap, see the testflinger jobs subcommand. Enjoy :)"
1822645,2019-04-01 18:55:28 UTC,Can you please provide an example board file?
1822645,2019-06-01 04:17:32 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1822646,2019-07-22 07:23:21 UTC,"""config.changed"" verification has been moved to the @when('nrpe-external-master.available') function. We don't want to trigger changes that first need the nrpe relation created."
1822647,2019-04-29 13:40:14 UTC,"I’m setting this to medium. Critical is used for issues that completely block the use of MAAS, cause crashes that affect operations, or severely hamper Maas usage."
1822648,2019-04-06 19:43:58 UTC,Fixed in x1.3.1-45
1822652,2019-04-08 04:49:14 UTC,Please provide a description of the bug you’re experiencing.
1822652,2019-06-08 04:17:24 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1822657,2019-07-25 14:22:45 UTC,"As per discussion with Cindy, restoring the priority to medium and putting back the stx.2.0 release tag. The config PL/TL will need to review and determine if this should be re-gated to Low / Not Gating."
1822657,2019-07-03 06:49:14 UTC,"As it is confirmed that the node was added, only the error message appears. And the test scripts updated with re-try logic. this bug is not blocking stx.2.0 and lower down to ""low"" priority."
1822657,2019-05-27 16:52:25 UTC,Reviewing old logs it turns out we had another instance of this issue in may 15 for standard and external storage configuration. The error appears but the nodes are added successfully
1822657,2019-07-26 12:44:40 UTC,"I reviewed this bug and would like to keep it as medium, rational is that the error massage is very misleading in case of successful add. i do agree that this should not gate stx-2.0 as the functionality worked."
1822657,2019-05-10 02:18:33 UTC,request log file saving in /var/log.
1822657,2019-04-22 20:24:36 UTC,"According to the code, there are two reasons on why this message can be returned. In [0] the API client returns a None value on mtce_api.host_add, while in [1] the API returns None on mtce_api.host_modify trying to power on the node."
1822657,2019-04-01 17:47:22 UTC,Marking as release gating; appears to be an intermittent issue during provisioning. Requires further investigation.
1822657,2019-05-13 14:39:22 UTC,"Logic were added to the test suite to handle this issue and try to add the host again, so in order to reproduce this issue again I think we need to provisioning manually."
1822659,2019-04-01 17:53:56 UTC,Could be related to: https://github.com/mate-desktop/caja/issues/1046
1822659,2019-04-10 10:37:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822660,2019-04-01 19:27:30 UTC,This is fixed by https://github.com/snapcore/snapd/pull/6675
1822664,2019-04-02 13:54:16 UTC,"まず、""補正が入っていない""という言葉が何処を指しているのか、何を意味するのか良く判らない"
1822664,2019-04-03 20:44:19 UTC,"因みに補正値の操作を行っているのは…
今日の方針はACT_MENU.ERB
ACT毎の補正はPLAYER_ACTM系のファイルです"
1822665,2019-04-02 02:40:24 UTC,Brightness keys (if not implemented in hardware directly) need to be known and mapped by the kernel.
1822665,2019-06-01 04:17:34 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1822672,2020-06-23 23:31:45 UTC,If I recall correctly this was discussed at a Foundations team meeting in September of 2019 where we decided not to prioritize fixing it because it has been broken since 18.04 LTS and as far as we know nothing is consuming the popcon data.
1822672,2020-06-25 12:59:02 UTC,"Francis, and that means what? It's going to be fixed, or not so much?"
1822672,2020-06-22 14:50:08 UTC,"@Brian, I'm tagging it incoming again, seeing the comments and details it seems our delta just makes the package non fonctional, if you decide to tag it notfixing again could you at least add some rational? If we don't care enough to fix problems should be move the package to universe and drop the delta we have or just remove it from Ubuntu?"
1822672,2020-06-24 18:30:19 UTC,If there was per package popcon I would like to consume it. Maybe it could be added to some qa page per maintainer at ubuntu? Not sure anyone would add it to the debian qa pages...
1822672,2020-02-12 17:24:02 UTC,Changing SUBMITURLS is not enough to fix this bug.
1822672,2019-09-24 15:37:53 UTC,This looks like the change that should have been kept when merging the package with Debian:
1822672,2019-08-06 11:01:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822672,2020-06-22 14:42:37 UTC,Could you report the regexp issue to Debian?
1822674,2020-07-02 18:35:42 UTC,Bug still present in focal as of today.
1822676,2019-11-01 16:03:55 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/692573"
1822676,2019-10-10 09:08:42 UTC,This issue was fixed in the openstack/nova 18.2.3 release.
1822676,2019-09-27 09:02:48 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1822676,2019-09-23 17:24:33 UTC,"Reviewed:  https://review.opendev.org/682946
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2b23ee7a3074e92167e68be1329467e8d602e9bc
Submitter: Zuul
Branch:    master"
1822676,2019-09-18 17:01:55 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/682946"
1822676,2019-08-16 15:55:57 UTC,"Reviewed:  https://review.opendev.org/674916
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d72f24569ea9da1f045927471b8d27c41837bf4a
Submitter: Zuul
Branch:    stable/rocky"
1822676,2019-08-12 20:41:19 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1822676,2019-08-06 19:22:09 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/674916"
1822676,2019-07-24 20:29:14 UTC,"Reviewed:  https://review.opendev.org/670972
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=186aff98b751b973dd5a7de9c8077b1a8bca0ba9
Submitter: Zuul
Branch:    stable/stein"
1822676,2019-07-17 09:53:31 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/670972"
1822676,2019-07-18 13:42:25 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/671490"
1822676,2019-07-16 07:51:49 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/670972"
1822676,2019-06-17 12:15:21 UTC,"Reviewed:  https://review.opendev.org/649372
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9606c80402f6db20d62b689c58aa8f024183628a
Submitter: Zuul
Branch:    master"
1822676,2019-04-26 04:50:56 UTC,nova patch is proposed here: https://review.opendev.org/649372
1822676,2019-04-02 13:35:54 UTC,"Reviewed:  https://review.openstack.org/649186
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=33c4f9df3dfc263e5f9084999fade492c30e77fe
Submitter: Zuul
Branch:    master"
1822676,2020-06-27 06:02:28 UTC,"Change abandoned by Dmitriy Rabotyagov (noonedeadpunk) (<email address hidden>) on branch: master
Review: https://review.opendev.org/671642
Reason: has been already implemented with https://review.opendev.org/#/c/729258/14/playbooks/defaults/repo_packages/nova_consoles.yml"
1822676,2019-04-01 20:51:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/649186"
1822676,2019-04-01 20:46:11 UTC,I'm investigating a fix for this in nova.
1822676,2020-04-17 15:57:55 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/720761"
1822676,2019-07-19 16:16:52 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/671769"
1822676,2019-11-04 15:44:22 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/692573"
1822676,2019-04-02 01:25:55 UTC,I've opened the following pull request for noVNC:
1822678,2019-04-03 16:06:25 UTC,"Fixed in revision 5ac96c6127bf92e384bbe0d9730f745cf4ff93fe
https://git.launchpad.net/kicad/patch/?id=5ac96c6127bf92e384bbe0d9730f745cf4ff93fe"
1822678,2019-04-03 16:06:32 UTC,"I _claim_ to have fixed this.  I added more mutex locks, and more importantly removed returning a reference from GetText() (which allows the resource to escape its RAII mutex locks)."
1822678,2019-04-03 11:30:47 UTC,"This still fails: even if we use the mutex in Void(), some other accessor such as EDA_TEXT's GetText() method is going to sink us."
1822678,2019-04-03 11:13:46 UTC,"@Jon, yes, but the crash is now intermittent."
1822678,2019-04-03 01:40:38 UTC,Are the stack traces identical after 948a617?
1822678,2019-04-03 00:20:54 UTC,Getting better! The crash in #5 still happens though but now its intermittent instead of every time.
1822678,2019-04-03 00:04:55 UTC,"Jeff, I found the other bug before I read your comment :)
Yes, there is a thread used in connection updating"
1822678,2019-04-02 23:57:29 UTC,"Fixed in revision 948a61711d5760b2752210f0aaeb000c79ba5de7
https://git.launchpad.net/kicad/patch/?id=948a61711d5760b2752210f0aaeb000c79ba5de7"
1822678,2019-04-02 23:44:33 UTC,I bet the MacOS crash is similar to this actually: https://bugs.launchpad.net/kicad/+bug/1761450
1822678,2019-04-02 15:48:37 UTC,"@Michael G -- I fixed this assert in 3eef4bce, however without access to your full project (for the symbol libraries) I cannot check to make sure the connectivity is okay.  Please check now and if you see any netlisting issues, could you please email me the whole project?  If you cannot share, let me know and I'll help debug some othe rway."
1822678,2019-04-02 23:38:04 UTC,"The #5, #6 and #10 crashes look to be wxString's lack of support for multi-threading."
1822678,2019-04-02 14:01:50 UTC,"It looks like the ""power_object"" issue goes back to commit 83c7e7fc6. I have assembled a schematic with cache files."
1822678,2019-04-02 13:00:07 UTC,"I'm having trouble reproducing these crashes.
Michael K -- are you also on Linux?
Can either of you try rolling back to f1882f333e7e6a2e0a90272ab6a99bc975360d3a and seeing if that changes behavior?"
1822678,2019-04-02 10:48:03 UTC,I also see a crash with another schematics. Could be different issue though.
1822678,2019-04-02 10:10:32 UTC,Also trying to open kit-dev-coldfire-xilinx-5213 KiCad crashes immediately on open.
1822678,2019-04-02 10:02:06 UTC,complex_heirarchy and pic_programmer now open fine but it crashes once you try and navigate into a hierarchal sheet
1822678,2019-04-02 06:46:50 UTC,"Thanks, that commit seems to fix this issue."
1822678,2019-04-02 02:18:30 UTC,Can you please check as of 8b30cd4389
1822678,2019-04-01 22:39:24 UTC,"I believe this is stack or heap corruption.  I also get a crash opening schematics, but only sometimes, and with a different stacktrace."
1822678,2019-04-01 21:33:49 UTC,"I'm seeing this as well, but I also can't open the pic_programmer."
1822678,2019-04-02 14:54:02 UTC,"@Jon, I'm on macOS, see my version info in comment #1. Rolling back to f1882f:"
1822679,2019-10-06 16:39:53 UTC,"Thanks. I never noticed that. I'll change it to be the host and the probably resolves the privacy issue enough to not hide it by default, but I need to think about that."
1822682,2019-04-02 22:03:57 UTC,"Sometimes after reboot system freezing and i can do nothing excepting hard-reboot.
Same issue on Manjaro Linux after nvidia drivers installing:
Kernel 4.20.17-1
from logs:
[TTM] Buffer eviction failed
nouveau 0000:01:00.0: DRM: failed to idle channel 0 [DRM]"
1822682,2019-04-12 14:23:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822682,2019-04-04 13:53:42 UTC,"fixed by downloading linux firmware from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
then after copy files from nvidia folder to /lib/firmware/nvidia/ everything become work.
Small story about ""warninings"" not even relating my videocard killing everything around.
nvidia drivers become work, rebooting as should to, no errors i got yet. This proves it was kernel issue. hope it's done."
1822682,2019-04-02 19:03:47 UTC,"lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
 Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1028:07fa]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort+ <MAbort+ >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>"
1822682,2019-04-02 18:56:00 UTC,"After updating kernel to 4.18.5 it's no more warnings and rcu_sched errors, but when i launch csgo from steam i get the same error:
Failed to create GL context; Could not make GL context current: GLXBadContext"
1822682,2019-04-02 01:47:08 UTC,"I see you mentioned GeForce 1050Ti in your bug. The commit I posted above is for GV100 ""Volta"". So the warning messages shouldn't affect you.
That said, it might be a good idea to add the relevant firmwares to Bionic."
1822682,2019-04-02 01:42:28 UTC,It is because of commit in 4.18 kernel:
1822682,2019-04-01 23:17:04 UTC,"Adding to it i had warning about missing some nvidia files in nouveau.
It's no problem on Ubuntu 18.04.01 with Kernel 4.15, and after update to Ubuntu 18.04.02 (with the same kernel) it's still no problem."
1822682,2019-04-02 12:49:34 UTC,"The problem appears when i start CS:GO in Steam, i got error smth about GLXContext and the game didn't start.
Drivers installed for nvidia were the same as i was installing in previous Ubuntu version (from default Software & Updates -> Additional Drivers (version 390))."
1822683,2019-04-03 13:28:45 UTC,Thanks for taking the time to report this bug in Ubuntu.
1822683,2019-06-03 04:17:25 UTC,[Expired for tomcat8 (Ubuntu) because there has been no activity for 60 days.]
1822684,2019-04-02 14:35:46 UTC,Something is wrong with either the mirror of the Ubuntu archive you are using or your connection to that mirror. You'll either need to switch mirrors of the archive or sort out your connection issue.
1822684,2019-06-02 04:17:33 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1822685,2019-10-06 16:39:03 UTC,"Sorry, commented on the wrong bug."
1822685,2019-10-07 00:33:25 UTC,"--- 2.9.1 (2019-10-06)
  * Use /run instead of /var/run
  * Fix-up sysv init so it works
  * Catch pyspf tracebacks so at least we don't die (thanks to Adi Pircalabu
    for both the report and the suggested fix) (LP: #1842005)
  * Correct over-writing of SPF identity by SPF reason for HELO checks and the
    reverse for Mail From (LP: #1822685)"
1822689,2019-04-02 17:26:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649405"
1822689,2019-10-14 20:56:58 UTC,"Reviewed:  https://review.opendev.org/649405
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5d29dccaf91c697ffc12a7289ce16cd83e60b07f
Submitter: Zuul
Branch:    master"
1822691,2020-10-15 17:49:59 UTC,"I'm looking in the cs:~llama-charmers-next/grafana charms revisions 9 and 11 and it looks like the CephOSD.json.j2 templates don't have the job=""$job"" fix from https://git.launchpad.net/charm-grafana/commit/?id=67f0cdbca9032ebc570cc23f99474bc72246030f"
1822691,2020-09-24 20:06:35 UTC,"I know it's a little late, but I subscribed ~field-medium for awareness"
1822691,2020-09-24 18:11:44 UTC,It looks like cs:~llama-charmers-next/grafana-9 has the commit:
1822691,2020-09-24 18:09:28 UTC,Is this commited fix available in a charm somewhere in the charm store?   (ie. cs:~llama-charmers-next/grafana)
1822691,2020-07-22 10:28:32 UTC,https://git.launchpad.net/charm-grafana/commit/?id=67f0cdbca9032ebc570cc23f99474bc72246030f
1822691,2020-06-23 05:39:47 UTC,"I have an environment with 3 ceph clusters, and I have applied the patch that was in the MP, and successfully the Ceph dashboards are now showing multi-ceph cluster metrics.
I have attached the screenshots of ceph-cluster, ceph-osd and ceph-pools."
1822695,2019-04-02 01:11:22 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9691"
1822695,2019-04-02 01:15:18 UTC,"In the .pendingfriendscard class in _btn.scss, I commented out the line 521: margin-bottom: -50px.  This will need to be examined further in the Release Candidate as the initial value was added there in order to manage the header size."
1822695,2019-04-03 00:31:20 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9702"
1822695,2019-04-05 00:56:33 UTC,"Commit: 7e45536ca347d6b0e52da9ef2b488115f7227e73
Environment tested: Master
Browser tested: Chrome"
1822695,2019-04-05 01:00:15 UTC,"Reviewed:  https://reviews.mahara.org/9702
Committed: https://git.mahara.org/mahara/mahara/commit/7e45536ca347d6b0e52da9ef2b488115f7227e73
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1822695,2019-04-05 01:00:25 UTC,"Patch for ""19.04_STABLE"" branch: https://reviews.mahara.org/9711"
1822695,2019-04-05 01:00:33 UTC,"Reviewed:  https://reviews.mahara.org/9711
Committed: https://git.mahara.org/mahara/mahara/commit/55435db533af9b5e125ab9e22af6c9b7dda9c642
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.04_STABLE"
1822698,2019-04-04 22:29:10 UTC,"Start by checking that all the qrunners are running, particularly IncomingRunner and OutgoingRunner. Check for a locked list. Check Mailman's logs, particularly 'error' and 'qrunner' for errors. See ttems 6.2, 7 and 8 at https://wiki.list.org/x/4030723"
1822702,2019-04-09 17:09:10 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1822703,2019-06-12 08:21:29 UTC,"This Watcher version is too old ,in the new version I can' t find this bug."
1822703,2019-04-02 05:57:20 UTC,Which Watcher version? Could you paste the function _is_audit_inactive?
1822703,2019-08-14 07:32:36 UTC,"Change abandoned by YUHAN (<email address hidden>) on branch: master
Review: https://review.opendev.org/649212"
1822703,2019-04-02 03:00:20 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649212"
1822709,2019-04-17 19:27:28 UTC,Thansk for the report.
1822709,2019-11-12 14:35:01 UTC,+1
1822711,2019-04-02 05:39:08 UTC,partial fix https://github.com/juju/juju/pull/9977
1822711,2019-04-11 22:02:05 UTC,next stage has landed https://github.com/juju/juju/pull/10008
1822711,2020-10-30 14:18:57 UTC,"Some of our dependencies use macaroon-bakery.v2-unstable macaroon.v2-unstable, but juju/juju code does not explicitly today.  But they appear to be older dependencies which are no longer used such as charmstore.v5 and charmrepo.v3."
1822712,2020-06-28 16:19:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822712,2020-06-30 22:24:38 UTC,Please provide your full /etc/apt/sources.list file so I can see what's going on. Thanks in advance!
1822712,2020-07-01 19:18:58 UTC,"Sources was:
deb https://mirrors.rit.edu/ubuntu/ focal main restricted universe multiverse
deb-src https://mirrors.rit.edu/ubuntu/ focal main restricted universe multiverse
deb https://mirrors.rit.edu/ubuntu/ focal-updates main restricted universe multiverse
deb-src https://mirrors.rit.edu/ubuntu/ focal-updates main restricted universe multiverse
deb https://mirrors.rit.edu/ubuntu/ focal-security main restricted universe multiverse
deb-src https://mirrors.rit.edu/ubuntu/ focal-security main restricted universe multiverse"
1822717,2019-04-29 19:03:37 UTC,This bug was fixed in the package binutils - 2.31.1-6ubuntu1.1
1822717,2019-04-29 19:05:36 UTC,This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04.1
1822717,2019-04-29 19:03:27 UTC,"The verification of the Stable Release Update for binutils has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822717,2019-04-02 23:44:42 UTC,"ppc64el, s390x and riscv64 packages are built on arm64, s390x and riscv64 packages are built on ppc64el"
1822717,2019-04-02 09:23:12 UTC,"Hello Matthias, or anyone else affected,"
1822717,2019-04-02 09:11:55 UTC,"Hello Matthias, or anyone else affected,"
1822722,2019-04-02 06:28:06 UTC,By default HEAT_DOCKER_CMD is set docker [1] and to be replaced with podman
1822722,2019-04-02 06:29:05 UTC,"When I changed HEAT_DOCKER_CMD to podman, I don't see this error in my setup."
1822722,2019-04-02 07:13:56 UTC,"> By default HEAT_DOCKER_CMD is set docker [1] and to be replaced with podman
"
1822724,2019-04-02 07:04:03 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649230"
1822724,2019-04-10 08:52:55 UTC,"Change abandoned by pengyuesheng (<email address hidden>) on branch: master
Review: https://review.openstack.org/649230
Reason: Fix this in [1]
[1] https://review.openstack.org/#/c/649491"
1822726,2019-04-02 07:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822726,2019-04-03 06:30:03 UTC,"Due to the nature of this issue, no log can be provided"
1822728,2019-04-02 13:21:52 UTC,"This is mostly broken because real-time connectivity updates were disabled at the last minute.  I'm working on some optimizations that may make it practical to re-enable.  If that doesn't pan out, I'll look into addressing this bug as a special case."
1822728,2019-04-11 04:18:53 UTC,"Fixed in revision 232b1c799fffe397a4d20527aa566cb2498c09e7
https://git.launchpad.net/kicad/patch/?id=232b1c799fffe397a4d20527aa566cb2498c09e7"
1822732,2019-06-14 19:43:29 UTC,I attached a proposed of how other EDA deal with (the resistors is not showing the pad because the software doesn't have full compatibly with Linux-Wine).
1822732,2019-05-02 12:30:42 UTC,"Do we want to do anything about this?  Given that Altium doesn't seem to handle this any better than we do, I'm not sure we should go to any great lengths to resolve the issue."
1822732,2019-08-19 20:17:38 UTC,"I'm going to close this as ""Won't Fix""."
1822732,2019-06-15 14:26:32 UTC,@Hildo-  I don't think your image is directly comparable yet.  You would need to make the hatch size larger than the hole size to see how your software handles this issue.
1822732,2019-04-05 18:26:41 UTC,"For me, there are 2 different cases:"
1822732,2019-04-05 17:40:45 UTC,What about an option that fills the hatch when it overlaps with the via cut-out ring?  That would add some additional copper but allow for valid fills when this happens.
1822732,2019-04-05 14:45:49 UTC,"FWIW, unless I haven't figured something out, even Altium can't do this automatically -- if you set your hatch size to be larger than ~2x the via diameter, it won't connect them.  I suspect this is a low-priority bug for them because generally there isn't a good reason to have such a sparse hatching."
1822732,2019-04-04 19:19:33 UTC,here is a pcb showing the errors
1822732,2019-04-04 18:21:52 UTC,"@Thomas, would you please attach a sample board showing this issue to this bug report."
1822734,2019-04-02 07:50:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649239"
1822734,2019-05-28 05:05:58 UTC,"Reviewed:  https://review.opendev.org/649239
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a6fae3b1090542e19fc90797ea4396d455b8b206
Submitter: Zuul
Branch:    master"
1822734,2019-06-12 14:43:48 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1822736,2019-10-05 14:44:11 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1822736,2019-04-03 02:43:04 UTC,"It is yet unclear what the root cause of this issue is - libpam, crypt, passwd and sudo seem like primary suspects. The 256 character password is hashed to a value which still allows a TTY login to succeed. Also, passwd run by a different user in the context of the affected user (using sudo) still works. So apparently it only breaks for the logged-in user. This may help identify the root cause."
1822736,2019-04-03 01:57:24 UTC,Booted up a Ubuntu 14.04 LTS box & followed test procedure.
1822736,2019-04-03 00:15:36 UTC,"I followed Tom's REPRODUCTION test, and got exactly what Tom said I would.
I can confirm the issue with 256 character passwords.
(I used `wc` to count characters in my buffer)"
1822736,2019-04-03 00:10:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822736,2019-04-02 10:54:44 UTC,This also affects Fedora 29 (Workstation).
1822738,2019-10-29 21:46:49 UTC,The following pull request was merged into master in relation to this bug https://github.com/snapcore/snapd/pull/6706
1822738,2019-04-10 02:02:41 UTC,"On Tue, Apr 09, 2019 at 07:58:20AM -0000, Maciej Borzecki wrote:

> Proposed tenative fix in snapd is to disable PIE builds. Relevant PR:
> https://github.com/snapcore/snapd/pull/6700
"
1822738,2019-04-09 07:58:20 UTC,Proposed tenative fix in snapd is to disable PIE builds. Relevant PR: https://github.com/snapcore/snapd/pull/6700
1822738,2019-04-09 07:57:19 UTC,"When investigating on the affected 32bit ARM system, we have observed that Go runtime would make a request to allocate system memory for it's arena allocator, using a size that was questionable. Even most trivial binary would request 150MB, using mmap(.., PROT_READ|PROT_WRITE, MAP_ANONYMOUS|MAP_PRIVATE..). At the same time, the system would report plenty of available memory, because although the request was satisfied, only few pages were eventually mapped, because the actual use of the mapped region (as reported by pmap -x) was no more than a few MB."
1822738,2019-04-05 09:30:49 UTC,I've looked as some /proc/meminfo dumps I was provided with.
1822738,2019-04-03 14:02:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822738,2019-04-02 12:53:28 UTC,"What architecture are they seeing the OOMs on?
Have they enabled swap?
What's the output of `free`?"
1822738,2019-04-02 10:07:44 UTC,This is a good idea from John:
1822738,2019-04-02 11:28:13 UTC,Repeated the same with 2.37:
1822738,2019-04-02 10:40:41 UTC,"The binaries themselves are quite large. Using current master (a057a16c6), and go 1.11.5, snapd is ~20MB, snap is ~15MB in size. I think it's fair to assume that whenever snapd or snap runs, most of it ends up in the memory. So calling 'snap refresh' would take up (worst case) 35MB to start with."
1822738,2019-04-02 10:10:36 UTC,The other option is to try the same with a recompiled snapd from 2.37  (if the issue is in our own code)
1822738,2019-04-02 10:08:18 UTC,"Another idea if we suspect go1.10 changes, is to try repeated refreshes with forced prune in between"
1822738,2019-04-02 08:17:26 UTC,"We need to factor that we keep changes around until pruning, not saying there's no leak but that we need to take that into account when searching for it."
1822738,2019-04-02 12:01:42 UTC,you probably want 2.38 and not current master because master now puts things in timings as well
1822739,2019-08-27 03:54:29 UTC,Hit this again: https://jenkins.juju.canonical.com/job/github-make-check-juju/634/consoleFull
1822739,2019-06-02 04:17:26 UTC,[Expired for juju because there has been no activity for 60 days.]
1822740,2019-05-07 10:54:48 UTC,Update:  Identified issue
1822740,2019-04-30 07:39:24 UTC,"Yes, it´s correct. They are using a script to build project/network/golden images/volumes_from_golden/instances booting from volumes. When troubleshooting these issues we added some delays but still hitting issue. Can you confirm that this error is caused by 3par limit? If so, can we increase this limit? MaxSessions?"
1822740,2020-02-19 11:21:26 UTC,"There is a limit to which concurrent operations are supported on 3par (eg. multiple create/delete volume requests).
Once this limit is reached, ssh exception is displayed."
1822740,2019-04-30 05:57:41 UTC,"We went through earlier mails as well.
If we understand correctly, some automated script is executed that …
creates projects, later creates multiple concurrent volumes, create instance, attach and detach volume to instance & so on.
This is when maximum connections limit of ssh and 3par is reached.
If possible the automated script can be tweaked [eg. introduce delays/retries] to overcome limit."
1822741,2019-04-17 18:32:43 UTC,"It seems the snapcraft version you are using was pip installed, we do not support that unless developing snapcraft itself, mind removing that install and instead `snap install snapcraft --classic` and trying again?"
1822741,2019-06-17 04:17:43 UTC,[Expired for Snapcraft because there has been no activity for 60 days.]
1822743,2019-04-02 12:28:44 UTC,"The attachment ""patch for 30parted"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1822749,2019-04-02 09:12:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649248"
1822749,2019-04-10 10:15:14 UTC,Security group is managed by neutron. Could you check the security group corresponding to the instance was NOT changed?
1822749,2019-04-11 01:36:49 UTC,the security group corresponding to the instance was not changed when the instances status is error
1822750,2019-04-02 09:02:59 UTC,This bug should be tested against 19.03
1822751,2019-11-25 12:59:27 UTC,"Unfortunately, due to https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1853173 this needs to be re-opened.  The fix broke the dashboard with ssl-enforce is on, probably because the Angular code can't read the CSRF cookie."
1822751,2019-11-25 14:22:32 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/695918"
1822751,2019-11-26 16:30:48 UTC,"Reviewed:  https://review.opendev.org/695918
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=5375df0b12657e3494a966a48d04878aba8d153a
Submitter: Zuul
Branch:    master"
1822751,2020-05-29 20:47:49 UTC,"I believe this was fix-released @ https://review.opendev.org/#/q/topic:bug/1822751, but the automatic bug management didn't occur.  If that is not the case, please reset this bug to a NEW status.  Thank you."
1822751,2020-05-29 20:46:11 UTC,"Change abandoned by Ryan Beisner (<email address hidden>) on branch: master
Review: https://review.opendev.org/649253
Reason: I believe this change is obseleted by https://review.opendev.org/#/c/649274.  If that is not the case, please rebase and reopen your review.  Thank you."
1822751,2019-08-22 11:33:09 UTC,"Reviewed:  https://review.opendev.org/649274
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=101098a1c2c1d7e30f5d4406e599074dee5d3ce7
Submitter: Zuul
Branch:    master"
1822751,2020-06-01 06:49:48 UTC,"Due to https://review.opendev.org/#/c/695918 I've re-opened the bug, as the aforementioned review reverted the 'fix'."
1822751,2019-11-26 16:31:01 UTC,"Reviewed:  https://review.opendev.org/695920
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=2ac72c39b480ae07df50edaac9802a7049773ca6
Submitter: Zuul
Branch:    stable/19.10"
1822751,2019-07-22 09:14:06 UTC,The Django settings mentioned in #3 seem to be related to the cookies managed by Django session. Horizon is managing some by is own [0].
1822751,2019-11-25 14:44:06 UTC,"Related fix proposed to branch: stable/19.10
Review: https://review.opendev.org/695920"
1822751,2019-07-19 02:57:36 UTC,"Subscribed field-medium as this is a commercial requirement, for a site running Bionic/queens."
1822751,2019-07-15 03:15:51 UTC,"A more recent scan of a cloud (Bionic, Queens, latest charms) resulted in a slightly better result, naming just two cookies that don't have the 'secure' flag set."
1822751,2019-04-23 12:07:46 UTC,"Hello Tilman,"
1822751,2019-04-02 11:43:23 UTC,"While we are at it, the same ""Security Scan"" revealed that there is no CSR policy. Which is apparently ""Critical"" too. :D"
1822751,2019-07-19 03:08:19 UTC,"It seems that even with the Django settings mentioned in #3, https://review.opendev.org/#/c/649274/ is still relevant as those particular settings are not included."
1822751,2019-04-02 11:32:22 UTC,That seems even better. I just went the path of least resistance with the charm change.
1822751,2019-04-02 10:56:18 UTC,"Hmm, I thought we set the secure flag in Django instead of Apache:
https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=47396b52dea795548a22e71fe8e51a414c7d300d"
1822751,2019-04-02 10:24:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649274"
1822751,2019-04-02 10:05:22 UTC,Agree it seems to be a reasonable ask.
1822756,2019-04-08 15:54:25 UTC,J'en ai profité pour remplacer le titre par Connexion à la documentation
1822756,2019-04-02 22:52:37 UTC,Ool indique sur la liste que ça pourrait se faire sur inc/lang/fr/login.txt
1822756,2019-04-08 18:19:21 UTC,ça donnerait ça
1822756,2019-04-02 09:51:11 UTC,Voir aussi discussion à ce sujet sur la mailing list des admins docs
1822759,2019-06-03 08:37:20 UTC,Temporary fix using NFS server to sync LCM and NBI shared folders released!
1822760,2019-04-02 10:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822760,2019-04-29 16:04:13 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1822760,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1822760,2019-05-14 22:54:27 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822761,2019-04-03 01:05:24 UTC,"We don't have a good way to do this yet. You basically have to either accept the defaults, or disable the addon that you want to customize, and deploy your own manifest."
1822761,2019-04-24 14:36:06 UTC,"We'd also like to see the memory limit of the influxdb container increased. We aren't running big clusters, and expect others would be running into the same issues we're seeing (11 restarts in the last 30 days on one cluster)."
1822761,2019-05-31 16:07:41 UTC,Up for review at https://github.com/charmed-kubernetes/cdk-addons/pull/121
1822761,2019-05-31 16:53:08 UTC,I've adjusted this summary to reflect this being a quick fix for influxdb. The larger generic issue of customizing cdk-addons will be handled in:
1822761,2019-05-31 19:39:43 UTC,"Looks like this isn't stable yet, so I don't think Fix Released is right."
1822761,2019-06-19 19:05:38 UTC,Now stable for 1.13/14 and in candidate for the upcoming 1.15 release:
1822762,2019-04-15 09:34:36 UTC,"Hi Zdohnal,"
1822762,2019-04-16 15:33:26 UTC,"Shouldn't there be a distinction between for what the plugin is required. For printing, or for scanning? And maybe also for faxing."
1822762,2019-04-15 18:09:09 UTC,"Hello Umesh,"
1822762,2019-04-16 15:43:05 UTC,It should be taken care of in plugin-reason directive (64 means 'needed for scanning')
1822762,2019-04-10 07:19:30 UTC,I did another test on a clean (i.e. a system where I did not apply any patches for testing) Fedora 29 with hplip-3.18.12-9.fc29.
1822762,2019-04-17 14:45:01 UTC,Earlier brian_p rashly said:
1822762,2019-04-17 16:16:17 UTC,Hmm... I can still see these cropped models in messages in the logs.
1822762,2019-04-17 17:01:55 UTC,Does this help?
1822762,2019-04-18 05:48:50 UTC,"Brian,"
1822762,2019-04-16 15:44:21 UTC,"Each section in models.dat has plugin-reason as an entry. At the end of the file, there is a list of reasons. 64 is scanning. 65 is scanning and printing."
1822762,2019-04-09 23:19:18 UTC,"Brian, I think the URL issue has also been fixed in hplip-3.18.12-9.fc29.
simple-scan works perfectly fine for me at the moment."
1822762,2019-04-10 07:44:50 UTC,">Upstream need to do more than patch one portion of models.dat. The attached file is for devices using >scan-type=5 (SOAPHT). Shouldn't this directive correlate with plugin=1?
>
>  [hp_laserjet_pro_mfp_m127fp]
>  plugin=0
>  plugin-reason=65
>  scan-type=5
"
1822762,2019-04-09 19:31:14 UTC,"Brian, the scanning was carried out from the command line with:"
1822762,2019-04-02 11:05:36 UTC,"Could you please also update the page: https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index that states that the ""HP Color LaserJet Pro MFP M281fdw"" does *not* require a driver plug-in. I specifically bought this printer because I did not want proprietary software on my system."
1822762,2019-04-02 16:02:08 UTC,"> The attached patch changes m278-m281 record in
> data/models/models.dat to that it needs plugin
> for scanning.
"
1822762,2019-04-03 14:42:52 UTC,I'm still not fully convinced that the plugin is needed for scanning. See https://bugs.launchpad.net/hplip/+bug/1816226 starting by comment 7 and the following comments.
1822762,2019-04-03 15:10:22 UTC,That was a typo in my previous comment. It should read *not sure*.
1822762,2019-04-02 15:36:41 UTC,"> I specifically bought this printer because I did not
> want proprietary software on my system.
"
1822762,2019-04-09 17:43:02 UTC,scantype5 attached.
1822762,2019-04-09 17:59:05 UTC,Jan said:
1822762,2019-04-09 19:52:56 UTC,"Thank you, Jan. I now understand."
1822762,2019-04-09 17:41:29 UTC,"> The attached patch changes m278-m281 record in
> data/models/models.dat to that it needs plugin
> for scanning.
"
1822763,2019-04-05 13:12:07 UTC,"Hello Rony,"
1822763,2019-07-15 04:17:24 UTC,[Expired for OpenStack nova-compute charm because there has been no activity for 60 days.]
1822767,2019-04-16 18:49:44 UTC,"I tried using XRender, but the problem is that it doesn't play nice with multiple monitors."
1822767,2019-04-19 06:08:02 UTC,A little update
1822767,2019-04-18 07:57:39 UTC,"I think there has to be a setting that's causing it to not play with NVIDIA.  Problem is, I don't know where it is."
1822767,2019-04-18 06:15:39 UTC,I forgot to mention that flickering is not occurring in the new user account.
1822767,2019-04-18 06:12:40 UTC,"I created a new user account, and I am now trying to isolate the problem, such as which desktop effect would cause this to occur."
1822767,2019-04-13 04:00:50 UTC,That was my exact issue when I was in Kubuntu 18.10.
1822767,2019-04-12 08:40:52 UTC,"This is an example of it, but it's not as crazy because it happens less frequently compared to that: https://youtu.be/Gn_dITHQFEs"
1822767,2019-04-12 10:11:48 UTC,"Hope this one helps, too."
1822767,2019-04-12 10:02:19 UTC,"GPU: GeForce GTX 1060 60GB
VBIOS: 86.06.0e.00.20
Driver: 418.56"
1822767,2019-04-12 09:33:01 UTC,"Don't think any of our testers on Nvidia have mentioned this, but I will pass it on to see."
1822767,2019-04-03 04:07:11 UTC,"After enabling Flipping, it happens much less frequently, but it still happens a whole lot more compared to 5.14."
1822767,2019-04-13 02:26:10 UTC,"I confirm this issue. I see flickering/screen flashing after waking from sleep on a GTX 1080 card, NVidia driver 418.56.  Disabling compositiing kills the flicker, but flicker returns upon compositing e-enable."
1822768,2019-04-02 11:02:53 UTC,A minimal example program to reproduce the behaviour.
1822768,2019-04-04 18:05:59 UTC,"Installing the Debian version of gtk on disco still shows the issue, it seems likely an upstream issue that should be reported on https://gitlab.gnome.org/GNOME/gtk/issues"
1822770,2019-04-02 12:09:20 UTC,Please integrate this fix in the kernel so also apple & its devices get a smooth experience
1822770,2019-04-03 23:00:33 UTC,"every reboot the apple magic mouse 2 has to click a few times on desktop
to get blueman recognize the mouse, after that the blueman indicator
lights up connected"
1822770,2019-04-02 11:43:00 UTC,"To make it work after a reboot, i had to 'trust' the apple magic mouse 2
in blueman to make it recognized automatic after reboot"
1822770,2019-05-30 00:00:20 UTC,Driver is in v4.20 according ot [1] - the site also documents some user-space configuration options.
1822770,2019-04-02 11:11:58 UTC,xinput list:
1822770,2019-04-02 11:27:49 UTC,FIX: https://github.com/rohitpid/Linux-Magic-Trackpad-2-Driver
1822770,2019-04-02 11:10:13 UTC,syslog with apple magic mouse 2 connected with lightning cable:
1822772,2019-05-06 09:33:48 UTC,"Fixed in revision 2e43c6c64e0bdf7a7c5897db2b7b53d0da31080e
https://git.launchpad.net/kicad/patch/?id=2e43c6c64e0bdf7a7c5897db2b7b53d0da31080e"
1822772,2019-05-07 17:09:29 UTC,"... tested with actual nightly and just compiled actual master-branch: The problem is still there.
It is visible in preview if mirroring is selected."
1822772,2019-05-07 17:27:50 UTC,"I agree with Duck. Here's a screenshot for a proof (Fallback canvas, flipped view)."
1822772,2019-05-07 17:30:06 UTC,"(I should have put the previous comment under some other bug report because mine was originally about printing, not Fallback canvas, but apparently it's the same problem...)"
1822773,2019-08-12 15:29:43 UTC,"What happens is, the sound in the login screen appears as 0, then in the desktop it goes to 100, then after a few seconds goes to 0. I have chromium and steam starting up on boot. Applies to Ubuntu 19.04."
1822773,2019-08-12 16:36:49 UTC,"Tried startup without steam and chromium, issue still occurs."
1822773,2019-04-03 15:45:29 UTC,The sound should be restored at the system/alsa level
1822776,2019-07-08 07:25:52 UTC,"The verification of the Stable Release Update for bash has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822776,2019-07-08 07:25:46 UTC,This bug was fixed in the package bash - 4.4.18-2ubuntu1.2
1822776,2019-06-20 11:58:52 UTC,"I installed bash from 'proposed' on a test server, and am running some tests on it, and parallel also on normal 18.04 servers. I'll expand this soon, and report back with the results."
1822776,2019-07-08 07:20:03 UTC,"It's not clear to me if cosmic has been tested as part of the validation. Please make sure that's the case and then adjust the tag accordingly.
That being said, since cosmic is going EOL soon, I will not block the release of bionic on the lack of cosmic validation."
1822776,2019-07-06 01:38:55 UTC,"Thanks for testing so thoroughly!  I've gone ahead and set the verification tags to done, to allow this to now go out.  I've also added your script to the Test Case, for future reference."
1822776,2019-07-04 19:58:02 UTC,Sorry for the delay. I had to write a bash script that increased the hit-chance of the bug. I now have 13 spinning bash on a non-updated test server. The one with bash 4.20 is working fine.
1822776,2019-07-01 21:41:58 UTC,"Hi halfgaar, just checking in on how the testing has been coming along?"
1822776,2019-06-19 16:00:46 UTC,"Hello halfgaar, or anyone else affected,"
1822776,2019-06-11 18:46:17 UTC,Fixes have been pushed to cosmic-proposed and bionic-proposed.
1822776,2019-05-29 17:47:10 UTC,"Thanks; it's not about getting it done yesterday so to speak, so I'll patiently await next week."
1822776,2019-05-29 17:12:35 UTC,"Hi halfgaar,"
1822776,2019-05-20 18:40:32 UTC,I added more info (edited the original description) hoping it covers everything the SRU requires.
1822776,2019-05-20 14:25:34 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1822776,2019-04-23 10:19:37 UTC,"I see this bug hasn't gotten attention, but isn't this quite critical?"
1822776,2019-06-19 15:59:18 UTC,"Hello halfgaar, or anyone else affected,"
1822781,2019-04-02 13:49:56 UTC,Can you provide a replication scenario for how to practice? What version of practicising are you running?
1822781,2019-04-02 14:52:36 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649354"
1822783,2019-04-02 13:34:21 UTC,commentcommentcomment
1822784,2019-04-02 13:38:06 UTC,Construct a door. Kendall knows.
1822797,2019-04-02 16:22:13 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1822797,2019-04-03 00:52:43 UTC,"This is because the raspi2 kernel package does not Provides:  zfs-dkms, zfs-modules, as expected for Ubuntu kernel packages which include ZFS support.  So if you try to install the zfs-initramfs package, apt will try to pull in something which satisfies the dependencies if nothing else is already installed which does, and it doesn't know that the kernel image it's pulling is not an appropriate provider of zfs for the running system."
1822797,2019-04-03 05:05:00 UTC,"I have had good experience with running ZFS on rpi3 using other distros. Of course it would be a complete craziness to use zfs in a desktop setup with just 1Gb of RAM. For what rpi is actually meant, 1Gb is plenty enough to run ZFS especially if the ARC size is set to a smaller value."
1822797,2019-10-24 20:23:06 UTC,"For what it is worth, zfs works quite well for a root fs rpool on a 4Gb RPI4b."
1822798,2019-04-02 14:24:09 UTC,The hover button color is changed so that is it effectively visible.  line number 307
1822801,2019-09-27 09:04:20 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1822801,2019-06-06 06:24:23 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1822801,2019-04-30 21:19:02 UTC,"Reviewed:  https://review.opendev.org/656176
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7cd816f43a9a699ccc5c5826b0904a3414664132
Submitter: Zuul
Branch:    stable/stein"
1822801,2019-04-28 15:47:35 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656176"
1822801,2019-04-28 11:43:56 UTC,"Reviewed:  https://review.opendev.org/649345
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=091aa3289694a27704e48931a579f50a3179b036
Submitter: Zuul
Branch:    master"
1822801,2019-04-17 02:26:53 UTC,The workaround for this would be to disable the periodic task by setting this config option to 0:
1822801,2019-04-15 15:45:56 UTC,This was regressed in Stein with change https://review.openstack.org/#/c/603844/.
1822801,2019-04-02 14:33:38 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649345"
1822815,2019-04-02 15:40:48 UTC,maybe we can do something along these lines ...
1822815,2019-07-25 21:53:11 UTC,"I commented on the patch Soledad submitted, but I'll add the relevant notes here:"
1822815,2019-07-31 18:45:50 UTC,"Change abandoned by Soledad Kuczala (<email address hidden>) on branch: master
Review: https://review.opendev.org/667744
Reason: The bug is in manila API"
1822815,2019-09-19 20:50:29 UTC,Manila patch is here: https://review.opendev.org/#/c/673913/
1822815,2019-09-20 02:24:43 UTC,"Reviewed:  https://review.opendev.org/673913
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=60254a4fd2bcb619ccf394e143583c6c226a21b9
Submitter: Zuul
Branch:    master"
1822815,2019-09-26 19:50:12 UTC,This issue was fixed in the openstack/manila 9.0.0.0rc1 release candidate.
1822818,2019-04-19 03:55:56 UTC,"4.15.0-48.51~16.04.1 - lowlatency
Regression test CMPL, RTB."
1822818,2019-04-24 08:09:17 UTC,All tasks have been completed and the bug is being set to Fix Released
1822821,2019-05-14 22:54:29 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822821,2019-04-02 15:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822821,2019-04-02 15:14:46 UTC,"This is easily verifiable on both Xenial and Bionic guests from uvt-kvm. I've brought up both as nested instances, and TSC fails to show up as an available clocksource:"
1822821,2019-04-02 17:51:41 UTC,Patches submitted to kernel-team list:
1822821,2019-04-26 14:31:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1822821,2019-04-29 16:04:19 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1822821,2019-04-29 19:22:42 UTC,Validated on linux 4.4.0-147.173 from xenial-proposed:
1822821,2019-04-29 19:24:22 UTC,Validated on linux 4.15.0-49.53 from bionic-proposed:
1822821,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1822821,2019-05-14 19:08:52 UTC,This bug was fixed in the package linux - 4.4.0-148.174
1822830,2019-04-25 10:43:14 UTC,All tasks have been completed and the bug is being set to Fix Released
1822830,2019-04-24 18:32:38 UTC,I ran a subset of the ADT tests manually using the following packages:
1822830,2019-04-14 23:24:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822836,2020-03-16 17:06:40 UTC,"Daniel Pearl was working on this bug, among others, before he left CW MARS.  He left behind an omnibus branch that is intended to fix most of these issues.  I have had these bugs assigned to me since before his departure because it was my intention to clean his branch up, test it, and add any missing bits.  I have not had time to do this, so I am simply putting the branch out there in the hope that someone can test what's there during bug squashing week or whenever."
1822836,2020-04-27 21:23:41 UTC,This is fixed as part of the receipt omnibus patch. My signoff to that is at:
1822836,2020-04-28 15:21:30 UTC,"Terran was testing a server that also had applied the top commit here, which needs a signoff as well:"
1822836,2020-04-28 17:27:48 UTC,"Fixes pushed to master and rel_3_5.  Thanks Dan, Jason, and Terran!"
1822839,2019-07-03 13:35:28 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.0.7-0ubuntu0.18.04.7
1822839,2019-05-09 11:53:08 UTC,"Hello Olivier, or anyone else affected,"
1822839,2019-05-10 09:24:24 UTC,"Upgraded libreoffice to 1:6.2.3-0ubuntu0.19.04.1 from disco-proposed in a clean and up-to-date disco amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice."
1822839,2019-05-14 14:30:08 UTC,This bug is no longer reproducible in
1822839,2019-05-14 14:38:41 UTC,"(In reply to Alex Brooks from comment #15)

> This bug is no longer reproducible in
>
> Version: 6.2.4.1 (x64)
> Build ID: 170a9c04e0ad25cd937fc7a913bb06bf8c75c11d
> CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win;
> Locale: en-GB (en_GB); UI-Language: en-GB
> Calc: threaded
"
1822839,2019-05-16 08:19:12 UTC,This bug was fixed in the package libreoffice - 1:6.2.3-0ubuntu0.19.04.1
1822839,2019-05-16 08:19:35 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.2.3-0ubuntu0.19.04.1
1822839,2019-05-23 14:51:38 UTC,"Hello Olivier, or anyone else affected,"
1822839,2019-05-24 15:39:02 UTC,"Upgraded libreoffice from 1:5.1.6~rc2-0ubuntu1~xenial6 to 1:5.1.6~rc2-0ubuntu1~xenial7 from xenial-proposed in a clean and up-to-date xenial amd64 VM, and verified that the [Test Case] now passes."
1822839,2019-05-09 11:51:27 UTC,"Hello Olivier, or anyone else affected,"
1822839,2019-05-24 16:00:22 UTC,"Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.5 to 1:6.0.7-0ubuntu0.18.04.6 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the [Test Case] now passes."
1822839,2019-05-30 08:44:53 UTC,This bug was fixed in the package libreoffice - 1:6.0.7-0ubuntu0.18.04.6
1822839,2019-05-30 10:03:47 UTC,This bug was fixed in the package libreoffice - 1:5.1.6~rc2-0ubuntu1~xenial7
1822839,2019-06-25 16:18:49 UTC,"Hello Olivier, or anyone else affected,"
1822839,2019-06-26 09:01:45 UTC,"Upgraded libreoffice-l10n from 1:6.0.7-0ubuntu0.18.04.6 to 1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the test case passes."
1822839,2019-05-23 14:59:29 UTC,"Hello Olivier, or anyone else affected,"
1822839,2019-05-06 11:55:22 UTC,"Can we get an SRU template for this bug? At least a viable test-case could be enough, with bonus points for everything else."
1822839,2019-05-16 08:19:28 UTC,"The verification of the Stable Release Update for libreoffice has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822839,2019-04-20 11:37:25 UTC,*** Bug 124855 has been marked as a duplicate of this bug. ***
1822839,2019-04-20 11:56:37 UTC,.
1822839,2019-04-02 15:27:42 UTC,Originally reported in Ubuntu: https://launchpad.net/bugs/1822839.
1822839,2019-04-02 16:49:52 UTC,So a new string would go into the OS build appropriate XML...
1822839,2019-04-02 16:55:15 UTC,"> @Stephen?
"
1822839,2019-04-03 09:50:25 UTC,"This knowledge about java.vendor strings encoded in a javavendors.xml is unfortunately at the heart of how module jvmfwk works internally.  I'm looking into changing that at least for current master (towards LO 6.3), so that jvmfwk assumes that a JRE with a java.vendor not listed in javavendors.xml can be used by LO."
1822839,2019-04-03 09:53:01 UTC,"(Comment 4 notwithstanding, it would nevertheless be useful if distros like Debian and Ubuntu wouldn't start to rename java.vendor strings from the well-known Oracle to something else.)"
1822839,2019-04-03 13:11:36 UTC,"I don't have control over what the OpenJDK packages in Debian/Ubuntu are using as a vendor name, but here is some related info:"
1822839,2019-04-03 09:08:56 UTC,See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926009#42
1822839,2019-04-04 09:52:06 UTC,Similar distro-patch for Ubuntu: https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/tree/patches/java.vendor-Ubuntu.patch?h=ubuntu-disco-6.2
1822839,2019-04-11 22:20:42 UTC,"Stephan Bergmann committed a patch related to this issue.
It has been pushed to ""libreoffice-6-1"":"
1822839,2019-04-05 05:34:56 UTC,This bug was fixed in the package libreoffice - 1:6.2.2-0ubuntu2
1822839,2019-04-09 20:32:48 UTC,"Stephan Bergmann committed a patch related to this issue.
It has been pushed to ""master"":"
1822839,2019-04-10 08:25:50 UTC,"(In reply to Commit Notification from comment #9)

> Stephan Bergmann committed a patch related to this issue.
> It has been pushed to ""master"":
>
> https://git.libreoffice.org/core/+/
> 3d27b2fa9c5a03f78e5145377402f8a88e3da1be%5E%21
>
> tdf#124503: Support JRE installations with unknown java.vendor property
>
> It will be available in 6.3.0.
"
1822839,2019-04-11 16:03:58 UTC,"Stephan Bergmann committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1822839,2019-04-03 13:15:34 UTC,"And the following distro patch was confirmed to work in Debian by Rene: https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/blob/master/patches/java.vendor-Debian.diff, so I will do something similar for the Ubuntu packages."
1822840,2019-04-08 15:52:15 UTC,"Hey Juan,"
1822840,2019-04-02 15:57:18 UTC,@andreserl Oh yes! I've discovered the way to manage spaces right now (I apologize for that). It's possible but it's not user-friendly from the point of view of the UX
1822840,2019-04-02 15:25:50 UTC,Spaces can be managed over the webUI. You can rename/delete them.
1822842,2019-04-05 13:36:43 UTC,Cosmic verfication:
1822842,2019-06-12 21:28:57 UTC,"The verification of the Stable Release Update for python-pip has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822842,2019-06-12 21:28:52 UTC,This bug was fixed in the package python-pip - 9.0.1-2.3~ubuntu1.18.04.1
1822842,2019-06-18 16:27:01 UTC,I opened a new bug with the information in the previous comment: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1833229 .
1822842,2019-04-25 08:40:25 UTC,"Thanks for the verification! The upload seems to report some autopkgtest regressions, could you take a look at those?"
1822842,2019-06-18 09:36:38 UTC,"It seems like `9.0.1-2.3~ubuntu1.18.04.1` breaks the `--extra-index-url`
functionality of PIP."
1822842,2019-04-05 11:28:49 UTC,I have tested and verified that this works as expected with the package from bionic-proposed. Note that the python-pip package change results in the change in python-pip-whl which is used for virtualenvs.
1822842,2019-05-08 12:12:08 UTC,Incomplete pending dep8 regression resolution.
1822842,2019-04-05 08:37:59 UTC,"Hello Dr., or anyone else affected,"
1822842,2019-04-04 14:59:37 UTC,For those impacted:
1822842,2019-04-03 11:08:32 UTC,package updates for bionic and cosmic uploaded for SRU team review.
1822842,2019-04-03 08:33:25 UTC,Sync from Debian unstable fixes in Ubuntu Disco:
1822842,2019-04-03 08:06:56 UTC,"Debian bug for this is https://bugs.debian.org/837764, the small fix should be able to be applied against the Bionic version, too."
1822842,2019-04-05 08:41:15 UTC,"Hello Dr., or anyone else affected,"
1822846,2019-06-03 09:14:21 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822846,2019-06-03 09:14:10 UTC,This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1~19.04.1
1822846,2019-05-07 05:55:46 UTC,looks ok in initial testing on 3.32.1-1ubuntu1~19.04.1
1822846,2019-05-01 11:34:40 UTC,This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1
1822846,2019-04-29 02:49:45 UTC,I also expect/hope gnome-shell 3.32.1 will reach Ubuntu 19.04 updates soon enough. So you may not need to do anything other than wait :/
1822846,2019-04-26 15:02:43 UTC,You can download the Pop!_OS gnome-shell packages here:
1822846,2019-05-06 12:34:39 UTC,"Hello Julian, or anyone else affected,"
1822846,2019-04-15 07:54:28 UTC,Unfortunately it seems the fix for this bug landed just hours/days slightly too late to be included in gnome-shell 3.32.0+git20190410
1822846,2019-04-03 09:39:21 UTC,"This also survived across a reboot, which was odd (or the bug triggered directly after boot)."
1822846,2019-04-03 03:27:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822846,2019-04-03 03:27:40 UTC,"Confirmed. This week (when using gnome-shell upstream, not the Ubuntu Dock) I've been seeing the same bug (occasionally) with my Files icon."
1822846,2019-04-02 15:50:37 UTC,"See attached screenshots. Not sure if upstream bug or Ubuntu bug, hence reporting here first."
1822846,2019-04-26 10:19:04 UTC,Does anyone know a workaround for this bug?
1822849,2019-04-02 15:59:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649379"
1822852,2019-04-13 14:53:01 UTC,Seth fixed this in https://bugs.launchpad.net/kicad/+bug/1824251
1822854,2019-04-02 16:40:50 UTC,apport information
1822854,2019-04-02 16:42:55 UTC,Interesting (?) difference between the i915 debug files:
1822854,2019-04-02 16:45:49 UTC,"Also, FYI: There are no log messages when the display turns on/off in the journal."
1822854,2019-04-02 17:00:07 UTC,This change was made by a bot.
1822854,2019-04-03 03:32:57 UTC,"I don't think this is going to be a gnome-shell or mutter bug. But in case it is, please test some other desktop environments to verify."
1822854,2019-04-04 05:15:08 UTC,"Marking this as Triaged / Low, as it seems to be only caused by these unusual options."
1822854,2019-04-03 13:06:03 UTC,"@Julian,"
1822854,2019-04-03 15:06:05 UTC,"I had added i915.enable_gvt=1 intel_iommu=on on the kernel commandline to enable Intel GVT-g, and connected an external monitor (with USB devices attached, and supplying power to the laptop) via USB C."
1822854,2019-04-02 16:40:48 UTC,apport information
1822854,2019-04-05 07:46:43 UTC,"Just happened without those options. But I'm not sure if it's a kernel bug, or a hardware/cable bug. Gotta investigate more I guess. It certainly happened less, the last two days have been issue free, but maybe I unplugged more and the cable got cleaner or something."
1822854,2019-04-03 06:22:56 UTC,It might be a kernel bug related to get/iommu which I had enabled to test with accelerated graphics in VMs. I think that the Kabylake are not really supported for that yet. I turned those off now.
1822854,2019-04-02 16:40:46 UTC,apport information
1822854,2019-04-02 16:40:36 UTC,apport information
1822854,2019-04-02 16:40:44 UTC,apport information
1822854,2019-04-02 16:40:45 UTC,apport information
1822854,2019-04-02 16:40:32 UTC,apport information
1822854,2019-04-02 16:40:33 UTC,apport information
1822854,2019-04-02 16:40:35 UTC,apport information
1822854,2019-04-02 16:40:31 UTC,apport information
1822854,2019-04-02 16:40:38 UTC,apport information
1822854,2019-04-02 16:40:40 UTC,apport information
1822854,2019-04-02 16:40:41 UTC,apport information
1822854,2019-04-02 16:40:43 UTC,apport information
1822854,2019-04-02 16:40:37 UTC,apport information
1822860,2019-04-03 17:19:01 UTC,Marking as release gating; low priority - cleanup of unused RESTAPI
1822860,2019-04-11 19:43:35 UTC,Can we close this bug as the storage usage option will be removed in https://bugs.launchpad.net/starlingx/+bug/1820728 ?
1822860,2019-05-07 05:45:55 UTC,Yes agree!
1822860,2019-05-25 00:43:24 UTC,"Duplicate bug was addressed on 2019-05-15
review: https://review.opendev.org/650619"
1822864,2019-04-03 00:07:03 UTC,"Hi Julien, could you please check the next nightly (after commit 948a61711d5760b2752210f0aaeb000c79ba5de7) and report if you still see the issue?  It may have been fixed already but I'm not sure based on the backtrace."
1822864,2019-04-03 15:51:54 UTC,"Seems fixed, thanks !"
1822866,2019-09-05 07:39:06 UTC,I had to remove /var/run/sendmail/mta/sendmail.pid then it worked.
1822866,2019-07-14 03:34:04 UTC,"Just adding another voice to this thread.  I had the same problem during the upgrade.  The failure for sendmail-bin to properly configure caused the sensible-mta, dovecot-core and inn2 packages to all fail to properly update due to dependency problems.  Thanks to Mirko above, who suggested a solution.  Stopping the sendmail service and running ""apt install -f"" allowed the configuration to complete."
1822866,2019-07-31 02:25:58 UTC,This bug was fixed in the package sendmail - 8.15.2-13
1822866,2019-07-12 21:12:33 UTC,"What worked for me was killing any running sendmail processes (stopping the service did not do this) and then updating worked with no noticeable issues.
The only thing I see is sm-mta warnings that ""My unqualified host name (HOSTNAME) unknown"", which for me is a non-issue since this box is on my home network with no domain."
1822866,2019-04-25 22:17:29 UTC,My workaround was the following:
1822866,2019-04-23 20:03:28 UTC,"Looks to me like it's a problem with the init.d script. (See the attached ""DpkgTerminalLog.txt"" file:"
1822866,2019-04-21 23:50:54 UTC,"Happened for me when trying to upgrade from 18.10.
When trying to configure the sendmail paclage, exit status 2 is returned.
Tried with linux 5.0.0-13."
1822866,2019-04-09 10:27:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822869,2020-03-16 17:08:34 UTC,"Daniel Pearl was working on this bug, among others, before he left CW MARS.  He left behind an omnibus branch that is intended to fix most of these issues.  I have had these bugs assigned to me since before his departure because it was my intention to clean his branch up, test it, and add any missing bits.  I have not had time to do this, so I am simply putting the branch out there in the hope that someone can test what's there during bug squashing week or whenever."
1822869,2020-04-27 21:24:09 UTC,This is fixed as part of the receipt omnibus patch. My signoff to that is at:
1822869,2020-04-28 15:21:52 UTC,"Terran was testing a server that also had applied the top commit here, which needs a signoff as well:"
1822869,2020-04-28 17:28:53 UTC,"Fixes pushed to master and rel_3_5.  Thanks Dan, Jason, and Terran!"
1822870,2019-04-29 13:38:22 UTC,"Marking Cosmic series as ""Fix Released"" following the Description comment:"
1822870,2019-04-29 13:41:10 UTC,"Next steps:
1) Kernel (security) team to add verification-bionic tags
2) IBM to verify bionic -proposed pocket, and update the bug tags"
1822870,2019-04-29 16:03:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1822870,2019-04-29 18:49:39 UTC,"------- Comment From <email address hidden> 2019-04-29 14:42 EDT-------
An initial test looks good, thank you!"
1822870,2019-04-29 19:56:32 UTC,Adjusting tag according to IBM's test result in comment #19
1822870,2019-04-29 21:50:36 UTC,"------- Comment From <email address hidden> 2019-04-29 17:43 EDT-------
I did some more testing, including toggling /sys/kernel/debug/powerpc/count_cache_flush and checking the code in xmon before:
c00000000000db58  7ee00026      mfcr    r23
c00000000000db5c  fae101a0      std     r23,416(r1)
c00000000000db60  f8230000      std     r1,0(r3)
c00000000000db64  4bffdb1d      bl      c00000000000b680        # flush_count_cache+0x0/0x2480"
1822870,2019-06-04 06:04:12 UTC,"Test Environment:
- Witherspoon DD2.3
- Ubu 18.04.2"
1822870,2019-05-14 22:54:31 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822870,2019-04-12 19:39:52 UTC,SRU Submitted: https://lists.ubuntu.com/archives/kernel-team/2019-April/100042.html
1822870,2019-09-02 14:59:37 UTC,"The Disco kernel is missing:
2b57ecd0208f (""KVM: PPC: Book3S: Add count cache flush parameters to kvmppc_get_cpu_char()"")"
1822870,2019-09-06 13:02:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1822870,2019-10-04 09:48:42 UTC,This bug was fixed in the package linux - 5.0.0-31.33
1822870,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1822870,2019-04-12 18:09:38 UTC,"------- Comment From <email address hidden> 2019-04-12 14:02 EDT-------
I tried out the PPA kernel you posted, Manoj, and it looks good here, too, from my testing:
mranweil@ltc-wspoon5:~$ cat /proc/version
Linux version 4.15.0-48-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)) #51~lp1822870+build.4-Ubuntu SMP Thu Apr 11 21:21:18 UTC 2019
mranweil@ltc-wspoon5:~$ dmesg |grep count-cache-flush
[    0.000000] count-cache-flush: hardware assisted flush sequence enabled
mranweil@ltc-wspoon5:~$ grep -H . /sys/devices/system/cpu/vulnerabilities/spectre_v2
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Software count cache flush (hardware acceleratd)"
1822870,2019-04-02 19:16:05 UTC,Default Comment by Bridge
1822870,2019-04-12 09:50:10 UTC,------- Comment on attachment From <email address hidden> 2019-04-12 05:43 EDT-------
1822870,2019-04-02 19:29:21 UTC,"------- Comment From <email address hidden> 2019-04-02 15:26 EDT-------
Disco appears to be missing only this patch on master, but it's included on master-next:
92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting"
1822870,2019-04-08 13:33:18 UTC,"Hi Michael R,"
1822870,2019-04-12 17:12:45 UTC,"On Fri, 12 Apr 2019, Michael Ranweiler wrote:"
1822870,2019-04-10 10:29:37 UTC,------- Comment on attachment From <email address hidden> 2019-04-10 06:26 EDT-------
1822870,2019-04-10 22:48:14 UTC,"Michael,"
1822870,2019-04-09 14:09:42 UTC,"------- Comment From <email address hidden> 2019-04-09 10:04 EDT-------
There's a couple extra patches we need to add to have all the mitigations (some that are from earlier than these DD 2.3 changes) from here:
https://github.com/linuxppc/wiki/wiki/Spectre-and-Meltdown-Related-Commits"
1822870,2019-04-11 07:19:27 UTC,"------- Comment From <email address hidden> 2019-04-11 03:16 EDT-------
We're missing one more patch - we need 51c3c62b58b3 powerpc: Avoid code patching freed init sections added in.  I will attach a new patch tarball including that after I try that out."
1822870,2019-04-11 15:16:46 UTC,"Michael,"
1822870,2019-04-12 00:32:57 UTC,"Michael,"
1822870,2019-04-12 06:31:35 UTC,"------- Comment From <email address hidden> 2019-04-12 02:19 EDT-------
This passed my tests in simulator."
1822870,2019-04-11 03:19:24 UTC,"------- Comment From <email address hidden> 2019-04-10 23:12 EDT-------
Hi Manoj,"
1822871,2019-04-10 18:18:28 UTC,"On Wed, Apr 10, 2019 at 11:01 AM Ard Biesheuvel
<email address hidden> wrote:

>
> On Tue, 9 Apr 2019 at 16:30, dann frazier <email address hidden> wrote:
> >
> > Yeah, no crash anymore - thanks Ard!
> >
> > ubuntu@d06-4:~$ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer
> > function
> > [   72.778123] ftrace: far branches to multiple entry points unsupported inside a single module
> >
> > ^ I assume this is expected
> >
>
> Uhm, not really.
"
1822871,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1822871,2019-05-17 09:31:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1822871,2019-04-15 18:45:36 UTC,"This patch resolves the problem for me, thx Ard!
  https://patchwork.kernel.org/patch/10899313/"
1822871,2019-04-10 16:48:42 UTC,"On Tue, 9 Apr 2019 at 16:30, dann frazier <email address hidden> wrote:

>
> Yeah, no crash anymore - thanks Ard!
>
> ubuntu@d06-4:~$ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer
> function
> [   72.778123] ftrace: far branches to multiple entry points unsupported inside a single module
>
> ^ I assume this is expected
>
"
1822871,2019-05-17 18:17:30 UTC,"disco verification:
ubuntu@d06-4:~$ cat /proc/version
Linux version 5.0.0-16-generic (buildd@bos02-arm64-013) (gcc version 8.3.0 (Ubuntu/Linaro 8.3.0-6ubuntu1)) #17-Ubuntu SMP Wed May 15 10:54:19 UTC 2019
ubuntu@d06-4:~$ sudo dmesg -c > /dev/null
ubuntu@d06-4:~$ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer
function
ubuntu@d06-4:~$ dmesg
ubuntu@d06-4:~$"
1822871,2019-04-09 23:21:37 UTC,"Yeah, no crash anymore - thanks Ard!"
1822871,2019-04-09 18:19:52 UTC,Does this fix the issue?
1822871,2019-04-02 19:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822871,2019-04-02 19:25:05 UTC,Bisection led to the following commit:
1822871,2019-04-10 00:07:58 UTC,"[   72.778123] ftrace: far branches to multiple entry points unsupported inside a single module
[   72.786657] WARNING: CPU: 121 PID: 3299 at /home/ubuntu/linux-5.0.0/kernel/trace/ftrace.c:2008 ftrace_bug+0xb0/0x2b0
[   72.786662] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio spi_dw ipmi_si ipmi_devintf ipmi_msghandler cppc_cpufreq sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 ses enclosure btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear marvell aes_ce_blk aes_ce_cipher hibmc_drm hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce syscopyarea sha2_ce sysfillrect sha256_arm64 ixgbe hisi_sas_v3_hw hns3 sysimgblt igb sha1_ce usbhid hisi_sas_main fb_sys_fops xfrm_algo drm hclge i2c_algo_bit hid libsas mdio hnae3 hinic ahci scsi_transport_sas gpio_dwapb aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
[   72.786826] CPU: 121 PID: 3299 Comm: tee Not tainted 5.0.0-9-generic #10
[   72.786830] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 2280-A CS V2.17.01 03/30/2019
[   72.786836] pstate: 60400009 (nZCv daif +PAN -UAO)
[   72.786843] pc : ftrace_bug+0xb0/0x2b0
[   72.786850] lr : ftrace_replace_code+0xa8/0xc0
[   72.786853] sp : ffff00002874bb20
[   72.786857] x29: ffff00002874bb20 x28: fffff244374049c0
[   72.786864] x27: 0000000000000000 x26: 0000000000000000
[   72.786870] x25: 0000ffffcad06548 x24: ffff40c2c5c23000
[   72.786876] x23: 0000000000000002 x22: 0000000000000001
[   72.786882] x21: ffff40c234f5b928 x20: ffffd23456ea0010
[   72.786887] x19: ffffd23456ea0010 x18: ffffffffffffffff
[   72.786893] x17: 0000000000000000 x16: ffff40c2c4f1f810
[   72.786898] x15: ffff40c2c5bec708 x14: 6c676e6973206120
[   72.786904] x13: 656469736e692064 x12: 6574726f70707573
[   72.786910] x11: 6e752073746e696f x10: ffff40c2c5bed168
[   72.786915] x9 : ffff40c2c5806018 x8 : ffff40c2c4cc4f80
[   72.786921] x7 : 6e61726220726166 x6 : ffff40c2c5c23f58
[   72.786926] x5 : fffff2444db53210 x4 : ffff40c2c471fce8
[   72.786932] x3 : 0000000000000000 x2 : b80552eea843d900
[   72.786937] x1 : ffffd23456ea0010 x0 : 00000000ffffffea
[   72.786944] Call trace:
[   72.786951]  ftrace_bug+0xb0/0x2b0
[   72.786957]  ftrace_replace_code+0xa8/0xc0
[   72.786964]  ftrace_modify_all_code+0xb0/0x148
[   72.786973]  arch_ftrace_update_code+0x10/0x18
[   72.786979]  ftrace_run_update_code+0x20/0x70
[   72.786986]  ftrace_startup_enable+0x4c/0x58
[   72.786992]  ftrace_startup+0xa4/0x140
[   72.786999]  register_ftrace_function+0x64/0x80
[   72.787007]  function_trace_init+0x50/0x98
[   72.787013]  tracing_set_tracer+0xf4/0x1c0
[   72.787019]  tracing_set_trace_write+0x10c/0x168
[   72.787028]  __vfs_write+0x48/0x80
[   72.787033]  vfs_write+0xac/0x1b8
[   72.787037]  ksys_write+0x6c/0xd8
[   72.787042]  __arm64_sys_write+0x24/0x30
[   72.787048]  el0_svc_common+0x78/0x120
[   72.787054]  el0_svc_handler+0x38/0x78
[   72.787061]  el0_svc+0x8/0xc
[   72.787065] ---[ end trace a7f7a5b79f6..."
1822873,2019-05-19 13:41:58 UTC,"Reviewed:  https://review.opendev.org/649473
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=d5a68a6b7039a66455d7e320379a6b0b3879891c
Submitter: Zuul
Branch:    master"
1822873,2019-04-02 22:58:35 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649473"
1822873,2019-04-02 22:48:30 UTC,Thanks Mel. For now I just disabled the n-novnc service in my local.conf and this time I was able to stack successfully I've got cell0/1/2 and 3 fake computes all pointed at cell1 in this case.
1822873,2019-04-02 22:35:03 UTC,"Sorry, I was way off on my other comment, so I've hidden it to avoid confusing people."
1822873,2019-04-02 22:35:26 UTC,Will propose a patch for this.
1822875,2019-07-16 21:41:11 UTC,"There appears to be a similar problem with query strings and multiple 505 fields. Only 1 shows up.  I suspect the root cause is the same, but if everyone thinks this should be a separate bug, I'll make one."
1822875,2019-10-30 18:48:43 UTC,"I'm not sure if this bug is the best place for this, but we are also noticing that the displayfield title seems to sort the subfields alphabetically when it outputs them.  Or at least doesn't follow the order that we are used to."
1822875,2019-10-30 18:30:24 UTC,"Thank you Michele. I don't understand how adding the 245c to the keyword index changes the data that the display fields extract for the title entry.  Is there any chance that there is another part to this, adding the responsibility display field info to the templates/opac/parts/record/summary.tt2?"
1822875,2019-10-30 14:00:58 UTC,"Josh,"
1822875,2019-10-30 13:06:26 UTC,"Hello, could I get a new paste of the config.metabib_field info from comment 1?  The current paste seems like it was taken over by spam."
1822875,2019-08-02 16:54:02 UTC,Insert the keyword entry and reingesting as suggest by Elaine Hardy in comment #2 does NOT fix the issue for me on an Evergreen 3.2 test system.
1822875,2019-07-16 22:21:10 UTC,"Jason, I'd like to see the multiple 505 fields as a separate bug.
Thanks,
Janet"
1822875,2019-06-10 14:52:13 UTC,One reason we want to see the 245c is for when the author's name originates from a non-roman alphabet. The authorized form in the 100 frequently does not match the spelling on the title page. We need to see both versions of the name represented in the public bib record display.
1822875,2019-07-15 20:36:43 UTC,"SCLENDS is seeing this on 3.1, and we are also interested in having 245 $c display."
1822875,2019-04-12 22:05:33 UTC,"um... ""Subfields included are: a, b, f, g, and k""."
1822875,2019-04-12 22:01:59 UTC,"Hi,"
1822875,2019-04-12 20:27:22 UTC,What was the reasoning behind the design choice to not display 245|c?
1822875,2019-04-03 17:45:38 UTC,"Wasn't it an intentional design choice not to display the 245$c when using display fields?  Those who want to show the 245$c can add the extra config.metabib_field entry, but for anyone who wants it suppressed (as intended?), the display will still be inconsistent as long as display fields are used inconsistently."
1822875,2019-04-03 13:39:02 UTC,"Just wanted to set the record straight that it was a combined effort of NOBLE staff members Martha Driscoll, Christine Morgan, Suzanne Paterno, Elizabeth Thomsen, Beth Willis and myself to identify the issue and come up with a solution to what we thought was a more local problem than it's turning out to be."
1822875,2019-04-03 13:09:39 UTC,"This was discussed on IRC before Feb 28. There doesn't seem to be a bug report about it, however. Since I'm not on IRC, I can't be more specific. Chris looped me in. I do know that Michele Morgan came up with a solution that has something to do with this table. Chris applied it and then had to reingest to see success."
1822875,2019-04-02 20:57:15 UTC,We see the same issue with $h in the 245 in 3.1.7
1822875,2019-04-12 22:09:04 UTC,"Hi Mike, yes the Angular catalog is using display fields instead of UNAPI for bib record metadata."
1822876,2020-05-22 17:40:38 UTC,"Hi Mathew,"
1822876,2020-07-22 04:17:30 UTC,[Expired for dovecot (Ubuntu) because there has been no activity for 60 days.]
1822884,2019-04-17 18:06:55 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653506"
1822884,2019-04-17 21:21:44 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/653609"
1822884,2019-04-23 11:44:26 UTC,the patch above solves (at least temporarily) the issues; the backport patch has enabled several compute hosts to be live migrated from
1822884,2019-04-26 18:41:51 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/649464"
1822884,2019-11-05 15:52:52 UTC,actull never mind that wrong link
1822884,2019-09-17 18:59:53 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/653609"
1822884,2019-05-09 21:42:23 UTC,"I'm still not really sure how the port binding stuff during live migration is working with the OSA->OSA live migrations but not the RDO stuff, I'm unsure what is updating the port's binding:host_id to the dest host before we call migrate_instance_finish in the OSA case but not the RDO case. Anyway, I for sure have a recreate in the cross-cell resize stuff so likely need Sean's fix anyway, and got the confirmation/details from Miguel in Neutron today on the difference between updating the port's binding:host_id indirectly by activating the dest host binding vs updating the port's binding:host_id directly to point at the dest host (when there is already an inactive dest host port binding). I guess I assumed those worked the same way, i.e. if you activate the inactive dest host port binding it updates the port's binding:host_id (works) and if you update the port's binding:host_id it would activate the dest host port binding (doesn't, and raises the error)."
1822884,2019-05-09 21:52:03 UTC,"I wonder if in your OSA case you had post-copy working during live migration such that the source host would activate the dest host bindings [1] before migrate_instance_finish ran on the dest [2]. Also note that _post_live_migration on the source will activate the dest host port binding as well [3], which is probably why we don't see this in the gate (upstream CI testing)."
1822884,2019-05-10 16:00:37 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/649464
Reason: This validates that https://review.opendev.org/#/c/653506/ resolves the issue reported in the bug."
1822884,2019-11-05 15:51:46 UTC,so is this a duplicate of https://bugs.launchpad.net/nova/+bug/1788014
1822884,2019-04-17 11:17:35 UTC,restarting conductor has not resolved the issue
1822884,2019-05-04 16:38:00 UTC,A bit unrelated but I seem to have recreated the problem in the nova-multi-cell job in this patch for the cross-cell resize tests:
1822884,2019-04-16 14:15:00 UTC,"after upgrading all nodes to rocky, RDO - RDO migrations are now broken as well. Testing a migration from 18.1.0 RDO -> 18.1.0 RDO fails with the same error"
1822884,2019-04-02 22:21:20 UTC,"port_id	host	vif_type	vnic_type	vif_details	profile	status
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute10-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}	{}	ACTIVE
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute24-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}		INACTIVE
Thu Feb  7 12:37:39 UTC 2019
port_id	host	vif_type	vnic_type	vif_details	profile	status
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute10-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}	{}	ACTIVE
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute24-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}		INACTIVE
Thu Feb  7 12:37:40 UTC 2019
port_id	host	vif_type	vnic_type	vif_details	profile	status
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute10-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}	{}	ACTIVE
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute24-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}		INACTIVE
Thu Feb  7 12:37:41 UTC 2019
port_id	host	vif_type	vnic_type	vif_details	profile	status
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute10-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}	{""migrating_to"": ""cc-compute24-kna1""}	ACTIVE
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute24-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}		INACTIVE
Thu Feb  7 12:37:42 UTC 2019
port_id	host	vif_type	vnic_type	vif_details	profile	status
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute10-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}	{""migrating_to"": ""cc-compute24-kna1""}	ACTIVE
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute24-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}		INACTIVE
Thu Feb  7 12:37:43 UTC 2019
port_id	host	vif_type	vnic_type	vif_details	profile	status
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute10-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}	{""migrating_to"": ""cc-compute24-kna1""}	ACTIVE
7cb143c7-2f20-413a-8f74-920ec538460f	cc-compute24-kna1	ovs	normal	{""port_filter"": true, ""datapath_type"": ""system"", ""ovs_hybrid_plug"": true}		INACTIVE
Thu Feb  7 12:37:44 UTC 2019"
1822884,2019-04-04 12:31:51 UTC,Hi Matt
1822884,2019-04-04 02:33:50 UTC,"https://review.openstack.org/#/c/649464/ didn't fail the nova-live-migration job, with or without post-copy enabled, meaning the destination port binding gets activated as part of post_live_migration_at_destination, which goes through the code that updates the port's binding:host_id value, which is what you reported caused the failure, so I'm not sure yet how to recreate this."
1822884,2019-04-02 22:39:39 UTC,I've also posted devstack patch https://review.openstack.org/649470 to pin the [upgrade_levels]/compute=queens RPC API version to see what happens with live migration while all code is newer than queens.
1822884,2019-04-02 22:34:30 UTC,"https://review.openstack.org/#/c/649464/ is an attempt at recreating this in our CI system, if it does recreate the nova-live-migration job should fail in the same way."
1822884,2019-04-02 22:29:07 UTC,RDO (Rocky)
1822884,2019-04-02 22:28:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/649464"
1822884,2019-04-02 22:19:50 UTC,"2019-02-13 13:41:33.890 56155 INFO nova.compute.manager [req-13e8d467-b162-42f4-8c0a-c0fae9e32df7 a3bee416cf67420995855d602d2bccd3 a564613210ee43708b8a7fc6274ebd63 - default default] [BRUCE](M-4): post_live_migration_at_destination: migrate_instance_finish(context, instance(Instance(access_ip_v4=None,access_ip_v6=None,architecture=None,auto_disk_config=False,availability_zone='nova',cell_name=None,cleaned=False,config_drive='',created_at=2019-02-12T11:40:46Z,default_ephemeral_device=None,default_swap_device=None,deleted=False,deleted_at=None,device_metadata=<?>,disable_terminate=False,display_description='osa_compute10_1',display_name='osa_compute10_1',ec2_ids=<?>,ephemeral_gb=0,ephemeral_key_uuid=None,fault=<?>,flavor=Flavor(7),host='cc-compute10-kna1',hostname='osa-compute10-1',id=282634,image_ref='f14f070e-8634-485b-b822-4b12a5bf87a0',info_cache=InstanceInfoCache,instance_type_id=7,kernel_id='',key_data='ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDJvlhaBlEg4cE2rzqr8XU5O/MWxgR2ERPeJEgMZJ0U8QOqKU1WvQUhdvY1aK+ZcIeiqX3HYcUwD3M7FgGCYD1eiKO7wuaBWC0fOxH3l7dx8WMOXW3kYswFgYen565arPu75ETaI4+tz3GFh9vnA+d6rkiCTUL1fvNs7Px37tN7J74Pxox17AuBGnyXtht2Vl0RGbbuHn1vbQ4Kk+Xw3AOgOonltOPW63IuprsiK1brAvwKn8XgLn5eT8/ovpLre2FQSiuzArHA15n+ppSY0du+MlZUQ2y63aKfZmdR765ORlXOiUToGfDxj0oowiTFvJO6VX0rHlkXU4CNlS7h1CsN /usr/local/lib/opensc-pkcs11.so',key_name='rcolvin_yubi',keypairs=<?>,launch_index=0,launched_at=2019-02-12T11:40:53Z,launched_on='cc-compute11-kna1',locked=False,locked_by=None,memory_mb=1024,metadata={},migration_context=<?>,new_flavor=None,node='cc-compute10-kna1',numa_topology=<?>,old_flavor=None,os_type=None,pci_devices=<?>,pci_requests=<?>,power_state=1,progress=80,project_id='a4cac02597bc4013b69a9cd9373f181c',ramdisk_id='',reservation_id='r-xqc9c0u0',root_device_name='/dev/vda',root_gb=20,security_groups=SecurityGroupList,services=<?>,shutdown_terminate=False,system_metadata={boot_roles='_member_,swiftoperator',image_base_image_ref='f14f070e-8634-485b-b822-4b12a5bf87a0',image_container_format='bare',image_disk_format='qcow2',image_min_disk='20',image_min_ram='0',owner_project_name='CN Eng',owner_user_name='CCP_User_35012_b8'},tags=<?>,task_state='migrating',terminated_at=None,trusted_certs=<?>,updated_at=2019-02-13T13:41:22Z,user_data='I2Nsb3VkLWNvbmZpZwpzeXN0ZW1faW5mbzoKIGRlZmF1bHRfdXNlcjoKICBuYW1lOiByY29sdmluCmNocGFzc3dkOiB7IGV4cGlyZTogRmFsc2UgfQpzc2hfcHdhdXRoOiBUcnVlCnBhY2thZ2VfdXBncmFkZTogdHJ1ZQphcHRfbWlycm9yOiBodHRwOi8vbWlycm9yLmNpdHluZXR3b3JrLnNlL3VidW50dS8K',user_id='d42829e49904441eb1834805fa1eb372',uuid=8fe8b490-13aa-4fc7-87a0-39706200b904,vcpu_model=<?>,vcpus=1,vm_mode=None,vm_state='active')), migration{cc-compute10-kna1, cc-compute29-kna1})
2019-02-13 13:41:33.953 56155 INFO nova.network.neutronv2.api [req-13e8d467-b162-42f4-8c0a-c0fae9e32df7 a3bee416cf67420995855d602d2bccd3 a564613210ee43708b8a7fc6274ebd63 - default default] [instance: 8fe8b490-13aa-4fc7-87a0-39706200b904] Updating port e314d12d-aff2-4e60-ae16-3eda2b6156b5 with attributes {'binding:profile': {}, 'binding:host_id': 'cc-compute29-kna1'}"
1822884,2019-04-02 21:37:34 UTC,"My suggestion would be to disable the neutron ""Port Bindings Extended"" API extension until you're fully upgraded to Rocky on all compute nodes because my guess is conductor is creating the deactivated target host port bindings because it's working with two computes that are both rocky, but because [upgrade_levels]/compute=auto and there are queens computes still, the versions of the MigrateData object is getting back-leveled which drops the 'vifs' field and that's what is used in the compute service code to determine if it's doing the new flow or the old flow."
1822884,2019-04-02 21:30:43 UTC,"(4:29:22 PM) NewBruce: [upgrade_levels]
(4:29:22 PM) NewBruce: compute = auto
(4:29:44 PM) mriedem: so that will pin to the lowest nova-compute service version in the deployment while you're upgrading,
(4:29:57 PM) mriedem: so if you have queens computes, it will be using the queens rpc versions and backlevel the migrate_data object
(4:30:12 PM) mriedem: which likely is dropping the vifs information for the 2nd deactivated port binding
(4:30:28 PM) mriedem: that's my guess anyway
(4:30:28 PM) NewBruce: Aha….
(4:30:37 PM) NewBruce: ok, so can we override that?"
1822884,2019-04-02 21:29:02 UTC,Do you have [upgrade_levels]/compute pinned to queens or something in nova.conf?
1822884,2019-04-02 21:26:22 UTC,This scenario doesn't really make sense to me:
1822884,2019-04-16 12:23:34 UTC,migrated the entire site to rocky
1822885,2019-06-03 04:17:29 UTC,[Expired for orca (Ubuntu) because there has been no activity for 60 days.]
1822885,2019-04-03 15:22:04 UTC,"Thank you for your bug report, from your dependencies list
python3-pyatspi 2.30.0+dfsg-3"
1822885,2019-04-02 22:23:47 UTC,"Atspi.KeySynthType.__dict__
mappingproxy({'__module__': 'gi.repository.Atspi', '__dict__': <attribute '__dict__' of 'KeySynthType' objects>, '__doc__': None, '__gtype__': <GType AtspiKeySynthType (37426864)>, '__enum_values__': {0: <enum ATSPI_KEY_PRESS of type Atspi.KeySynthType>, 1: <enum ATSPI_KEY_RELEASE of type Atspi.KeySynthType>, 2: <enum ATSPI_KEY_PRESSRELEASE of type Atspi.KeySynthType>, 3: <enum ATSPI_KEY_SYM of type Atspi.KeySynthType>, 4: <enum ATSPI_KEY_STRING of type Atspi.KeySynthType>}, '__info__': gi.EnumInfo(KeySynthType), 'PRESS': <enum ATSPI_KEY_PRESS of type Atspi.KeySynthType>, 'RELEASE': <enum ATSPI_KEY_RELEASE of type Atspi.KeySynthType>, 'PRESSRELEASE': <enum ATSPI_KEY_PRESSRELEASE of type Atspi.KeySynthType>, 'SYM': <enum ATSPI_KEY_SYM of type Atspi.KeySynthType>, 'STRING': <enum ATSPI_KEY_STRING of type Atspi.KeySynthType>})
(Pdb) Atspi.KeySynthType.LOCKMODIFIERS
*** AttributeError: type object 'KeySynthType' has no attribute 'LOCKMODIFIERS'"
1822890,2019-04-02 22:08:01 UTC,Can you provide some example dialogs? I just had a quick look (on macOS) and they all behaved as you describe.
1822890,2019-04-02 22:38:57 UTC,"I probably exaggerated by writing ""most if not all"", but I found the following ones in pcbnew :"
1822890,2019-04-03 11:42:11 UTC,Also found Text Properties in eeschema
1822890,2019-04-03 18:55:10 UTC,"We've had a work-around for this on OSX for a while now.  I just enabled it for MSW and GTK.  I think it will fix these (but it may also cause complaints, so we'll see how it goes)."
1822890,2019-04-03 21:15:22 UTC,"Fixed in revision 0fb956cdbe2c7920b5cc022da0c391a622787924
https://git.launchpad.net/kicad/patch/?id=0fb956cdbe2c7920b5cc022da0c391a622787924"
1822890,2019-04-03 23:16:16 UTC,Thanks for the fix. Works fine with nightly build kicad-r12643.0fb956cdb-i686.exe
1822896,2019-04-04 12:46:09 UTC,"The log has those errors
 'QUASHFS error: zlib decompression failed, data probably corrupt'"
1822896,2019-06-04 04:17:22 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1822898,2019-06-03 08:48:02 UTC,This bug was fixed in the package openssl - 1.1.1-1ubuntu2.2
1822898,2019-04-04 06:05:39 UTC,This bug was fixed in the package openssl - 1.1.1b-1ubuntu2
1822898,2019-04-05 08:46:18 UTC,"Hello Dimitri, or anyone else affected,"
1822898,2019-04-11 16:06:17 UTC,"booted cosmic mini-iso with proposed enabled, manually injected the 2.2 udeb, and wget geoip.ubuntu.com/lookup still works."
1822898,2019-06-03 08:48:11 UTC,"The verification of the Stable Release Update for openssl has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822899,2019-04-27 05:06:58 UTC,"https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/6
https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/14"
1822899,2019-05-02 14:26:26 UTC,This fix is avaiable in revision 523 of kubernetes-worker charm and revision 661 of kubernetes-master charm.
1822901,2019-04-02 23:41:35 UTC,"Considering this is coming from vmstat, which per, the source code, is measuring the vm_pswpout function for the ""so"" column, which is in turn, what we measure as swap_activity, this is measuring the volume of data being swapped, rather than the swap rate or number of pages being swapped."
1822901,2019-04-10 06:13:57 UTC,lgtm
1822902,2019-05-21 18:26:20 UTC,"OP here --- the ""bug"" seems to be affected by the ""Large Fonts"" settings under ""Universal Access"", and some other setting:"
1822902,2019-04-03 09:35:24 UTC,What is your monitor resolution? I have a 2560x1440 that does this
1822902,2019-04-03 11:32:30 UTC,It is 2560x1440 (the screenshot is taken at that resolution)
1822902,2019-04-07 16:01:01 UTC,Maybe something with the KDE GUI library. Something was not drawn in the way the KiCAD developers had planned. Collect kicad directly from the git repository and build.
1822902,2019-05-21 17:15:22 UTC,I cannot duplicate this using 5.1.2-53-g0403437ad on Linux.  I do not have a high dpi monitor and/or ubuntu unity which may be the issue.  Would one of our Linux devs with a high dpi monitor please take a look at this to see if this a high dpi issue or an ubuntu unity issue.  Thanks.
1822902,2019-05-21 17:36:05 UTC,Here's the dialog from xfce (3840x2160).  Might be a Unity issue?  The GTK3 preferences can change this.  I use Breeze and have the following line in my gtk.css file:
1822902,2019-08-05 17:19:29 UTC,@Wayne-  Good thought.  I'll give it a go this weekend.
1822902,2019-05-21 22:41:02 UTC,@Cal-linux Does it also look bad when you select properties on a track instead of text?
1822902,2019-05-22 13:32:38 UTC,"No, the dialog for Trace (track) properties shows perfectly ok  (I just tried on my account, on Unity, which has been the problematic one --- I didn't test on GNOME or with the newly-created user, but I see no reason to expect any problems there)."
1822902,2019-05-22 13:35:47 UTC,"In fact, it shows *perfectly* ok --- the color square and the text are perfectly aligned vertically (i.e., both centered)."
1822902,2019-06-19 13:02:28 UTC,I dug around on this some more and the only difference between the drop downs in the two dialogs is that the one that Unity displays correctly is in a sizer by itself and the one that unity doesn't display correctly shares a sizer with other elements.
1822902,2019-06-19 17:05:46 UTC,"@Seth, do we fix this by adding another sizer for the control or do we punt because the issue is clearly with Unity?"
1822902,2019-08-05 16:09:51 UTC,"@Seth, can you still duplicate this?  If so, would it be possible for you to test this without drawing the color swatch?  The combobox in question is in it's own cell of the flexible grid sizer so it may not be a sizer issue but rather an issue of how we report the size of the color swatch."
1822903,2019-04-30 15:23:34 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/656531"
1822903,2020-04-27 09:10:13 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: stable/19.04
Review: https://review.opendev.org/656531"
1822903,2019-04-26 07:48:53 UTC,"Reviewed:  https://review.opendev.org/651127
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=0697559b51666197eecc0985611ee563c9a70c6d
Submitter: Zuul
Branch:    master"
1822903,2019-04-09 07:58:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651127"
1822903,2019-04-09 07:03:37 UTC,"Trent's write-up on the issue (from https://pastebin.canonical.com/p/nsnjg4qH6h/)
======"
1822906,2019-04-03 01:38:00 UTC,Another option: some other tools I have used have you pick the reference object after executing the command.  This approach has the advantage of working the same way if you execute the align command from a keyboard shortcut (where there might not be an obvious reference object to pick).
1822906,2019-04-03 01:57:24 UTC,Picking the reference object after execution has the disadvantage of adding extra steps (unconditionally).
1822906,2019-04-03 08:39:10 UTC,"Compare this before/after dilemma with ""Position Relative To..."" dialog. It's not necessarily the best example of good usability, but KiCad should have internal consistency as much as possible. One tactic should be chosen and used in as many places as possible."
1822906,2019-04-03 10:34:04 UTC,Forum discussion: https://forum.kicad.info/t/more-bugs-misfeatures-in-5-1/16120
1822906,2019-04-03 12:39:33 UTC,I just checked Adobe Illustrator and it top/right/bottom/left aligns objects to the topmost/rightmost/bottommost/leftmost object.
1822906,2019-04-03 13:56:46 UTC,"I agree that the intuitive interpretation of ""Align to Right"" is that."
1822906,2019-04-08 12:18:14 UTC,Michael i agree that this might not be a high priority thing. But a clearer name for these tools could make it easier for users to understand them on an intuitive level. This means it would not really move this bug to opinion but maybe either wishlist or low.
1822906,2019-04-08 12:49:04 UTC,"IMHO the current menu text shouldn't be changed as its short, succinct and the ""standard"" phrase in all other graphical editing software/office suites/CAD packages etc. I have ever used. Maybe a tooltip or explanatory message in the status bar would help clear up confusion."
1822906,2019-04-21 18:33:20 UTC,"Hmm, I just wanted to submit a bug report for this - thanks for clarification :)
But what is still unclear to me -
I selected 10 SMD pads, two rectangle selections combined with shift. How do I assure the bottom-most pad is the reference pad? How can I verify before trying out?
Greetings and thank you for this incredible tool"
1822906,2019-04-27 19:28:26 UTC,"@Günter: right-click on the bottom-most pad when you go to execute ""Align to Bottom"". Then all the pads will share a bottom with that pad."
1822906,2019-06-05 12:07:54 UTC,"The menu texts are really wrong. They should say ""Align to the item on which context menu was called"" or something shorter but yet descriptive. It's not an opinion, just plain simple logic. And there should be only two items, not 2x3 (every one in one group of 3 now do the same thing)."
1822906,2019-08-13 17:13:51 UTC,"I'm in agreement with comment #3, although I think the ""Select reference point"" facility of the Copy command is more relevant."
1822906,2019-08-13 20:29:43 UTC,"Forget what I said in comment #11, I didn't understand how these work. Now it makes sense and the functionality is good. But my misunderstanding tells something about the ease-of-learning."
1822907,2019-05-02 15:20:38 UTC,"@Wayne, must have been an oversight (didn't notice it at the bottom of the menu). I have attached an updated patch."
1822907,2019-05-02 16:48:56 UTC,"@Michael, I merged your patch into the master branch.  I don't think I will cherry pick this into 5.1.  It's probably not a good idea to rearrange menus during a stable release series if we don't have to.  Thank you for your contribution."
1822907,2019-05-02 16:45:47 UTC,"Fixed in revision 2a09664ebce0b4c03be14588c15e697a0560a58b
https://git.launchpad.net/kicad/patch/?id=2a09664ebce0b4c03be14588c15e697a0560a58b"
1822907,2019-05-02 12:46:42 UTC,"@Michael, your patch looks fine.  Did you decide not move ""Export Footprint..."" and ""Export View as PNG..."" into a common ""Export"" sub-menu in the footprint editor for a specific reason or was it just an oversight?"
1822907,2019-05-02 16:52:17 UTC,"@Wayne thanks. Sure, no problem, thats why I set the milestone for 6.0.0-rc1."
1822907,2019-04-03 12:48:14 UTC,"No, this is grouping the export options in the Symbol Editor menubar into an Export Submenu (like the other applications). There is no change to that menu items help text."
1822907,2019-04-05 19:21:59 UTC,Rebased onto latest menubar changes.
1822907,2019-04-03 12:43:42 UTC,"If I'm understanding correctly the suggested change --- the text ""Create a SVG file from current symbol"" is being added (I guess that's the tooltip text?)."
1822907,2019-04-03 11:30:28 UTC,A slightly more invasive but IMO better change.
1822907,2019-04-03 11:00:02 UTC,"@eelik - Agreed, but I was going for minimal string changes."
1822907,2019-04-03 08:31:06 UTC,"@Michael: why not just be less verbose: ""Import Footprint from File""? It can safely be assumed that the file is existing without being explicit about that. Like, menus never have ""Open Existing File"" etc."
1822907,2019-04-03 12:46:01 UTC,"For that matter --- can that article be removed? (I think it could be ""Create SVG from ...."").  Similarly, it could (maybe even should) be ""Import footprint from file"", instead of ""Import a footprint from file""."
1822912,2019-09-02 16:15:04 UTC,Looks like we need to take a look at quantity.go - FormatDuration().
1822913,2019-04-03 12:30:27 UTC,"I cannot run apport-collect because when I have this issue I don't have wifi connectiom. I will try to connect via cable an do apport-collect, but It will take some time. Giving that 19.04 with Kernel 5 is almost ready to be delivered, I will change to confirm anyway."
1822913,2019-04-19 05:54:16 UTC,Exactly same issues on live version of Fedora 30 Beta with the same version of Kernel.
1822913,2019-04-19 05:44:26 UTC,"Exactly same issues here.
I tried live version of Ubuntu 19.04 with Kernel 5.0.0-13-generic and:"
1822913,2019-04-06 11:02:16 UTC,"problem is solved in kernel 5.1.0-050100rc3-generic
Is it necessary the bisect?"
1822913,2019-04-03 13:32:55 UTC,"If possible, please follow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/comments/4"
1822913,2019-04-03 01:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822913,2019-04-03 05:51:40 UTC,Dupe of LP: #1821564?
1822913,2019-04-22 20:10:26 UTC,"@Maurizio, could you test a newer Kernel? 5.1 for example to see if it's already solved, it is in my case."
1822913,2019-04-03 01:12:55 UTC,"forgot to add info about the audio and wifi:
*-multimedia
             description: Audio device
             product: NM10/ICH7 Family High Definition Audio Controller
             vendor: Intel Corporation
             physical id: 1b
             bus info: pci@0000:00:1b.0
             version: 01
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress bus_master cap_list
             configuration: driver=snd_hda_intel latency=0
             resources: irq:25 memory:efebc000-efebffff
*-network
                description: Wireless interface
                product: PRO/Wireless 3945ABG [Golan] Network Connection
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:0c:00.0
                logical name: wlp12s0
                version: 02
                serial: 00:18:de:8a:64:ec
                width: 32 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=iwl3945 driverversion=4.19.0-13-generic firmware=15.32.2.9 ip=192.168.0.18 latency=0 link=yes multicast=yes wireless=IEEE 802.11
                resources: irq:24 memory:efdff000-efdfffff"
1822913,2019-04-03 12:50:33 UTC,I saw in the comments that #1821564 was with kernel 5 it might be a dupe of it then.
1822913,2019-04-24 14:38:40 UTC,"@Hans, since Ubuntu 19.10 still has Kernel 5.0, i tried live version of Fedora Rawhide with Kernel 5.1.0-0.rc6 and i can confirm you that there are no one of issues listed above."
1822917,2019-04-30 11:27:19 UTC,"Reviewed:  https://review.opendev.org/652994
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2bbd7f4a0ce0df0a5d1789848796178491fbea40
Submitter: Zuul
Branch:    stable/stein"
1822917,2019-04-04 02:44:12 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649788"
1822917,2019-09-27 09:04:44 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1822917,2019-06-06 06:24:28 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1822917,2019-04-16 13:35:02 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/652994"
1822917,2019-04-04 01:38:20 UTC,"The ""Overwriting current allocation"" log message is output when reverting resize.
So it is a normal case."
1822917,2019-04-04 02:31:15 UTC,"Yeah I discussed this with gibi in IRC today and he didn't have any reason for the warning except it seemed like overwriting allocations was a bad idea, but maybe didn't connect that to the fact we are intentionally doing it when reverting the resize, so the warning should probably just be dropped to DEBUG level."
1822917,2019-04-16 11:15:01 UTC,"Reviewed:  https://review.openstack.org/649788
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d955ce42cc16149cc9ffe7f698210d85792b63a0
Submitter: Zuul
Branch:    master"
1822923,2019-04-03 02:19:09 UTC,"#git tag --contains 92a3e426ec06e72b1c363179c79d30712447ff76
v5.1-rc3
# git tag --contains edef1ef134180149694b86386277076f566d165c
v5.1-rc3"
1822923,2019-04-03 02:22:59 UTC,these patches are required in addition to LP#1802436 for CLX-SP.
1822925,2019-05-17 02:36:48 UTC,I realize if i change the following line in containers.module.js and the issue goes away
1822925,2019-05-25 22:17:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661471"
1822925,2019-06-03 02:23:05 UTC,"Reviewed:  https://review.opendev.org/661471
Committed: https://git.openstack.org/cgit/openstack/zun-ui/commit/?id=aad1d140500822e79fa2d7b2b4bc8180696bfefb
Submitter: Zuul
Branch:    master"
1822925,2019-06-03 02:31:59 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/662667"
1822925,2019-06-04 01:51:15 UTC,"Reviewed:  https://review.opendev.org/662667
Committed: https://git.openstack.org/cgit/openstack/zun-ui/commit/?id=58ca0552d1e9bfad966431abb6292f57e67a6180
Submitter: Zuul
Branch:    stable/stein"
1822925,2019-09-23 08:57:54 UTC,This issue was fixed in the openstack/zun-ui 4.0.0.0rc1 release candidate.
1822925,2019-10-02 11:27:08 UTC,This issue was fixed in the openstack/zun-ui 3.0.1 release.
1822927,2019-04-18 08:33:09 UTC,"Reviewed:  https://review.openstack.org/649496
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=105d201e1f8deb6e025a836c9fc290ec976be85a
Submitter: Zuul
Branch:    master"
1822927,2019-04-03 03:14:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649496"
1822932,2019-08-20 00:59:27 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1822937,2020-05-04 05:27:34 UTC,Emiliano (gaiagilder) Try installing the following packages
1822937,2020-05-18 08:49:20 UTC,"I am running Nvidia 440, and i have the same problem. :("
1822937,2020-04-05 21:35:12 UTC,"Fixed with 390.132 driver, NV-CONTROL Version:1.29, Ubuntu 20.04
Thanks"
1822937,2020-05-20 08:13:25 UTC,"Same as Guillermo, on Ubuntu 20.04 using Nvidia 440, same problem .."
1822937,2020-12-05 08:27:00 UTC,"I have also the same problem. With two monitors, I change the monitor positions (left/right) in the nvidia-settings tool (started with sudo) and write it to the X Configuration file (/etc/X11/xorg.conf). The file is changed, but the monitor positions are reset after next reboot."
1822937,2020-07-23 07:58:44 UTC,"Installing xserver-xorg-dev fixed the error:
Package xorg-server was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-server.pc '
to the PKG_CONFIG_PATH environment variable
No package 'xorg-server' found"
1822937,2020-08-01 03:08:15 UTC,Ok I just did a quick test.  It is writing to my xorg.conf.
1822937,2020-12-06 04:05:44 UTC,"Same here, with Nvidia 455.45.01 on Ubuntu 20.04. In fact I've been facing this for years, since 18.04."
1822937,2020-03-20 16:34:51 UTC,"I'm still having the problem in (X)Ubuntu 18.4,"
1822937,2020-07-18 22:27:23 UTC,I found the solution installing screen-resolution-extra 0.18 from https://packages.ubuntu.com/focal/screen-resolution-extra using dbkg -i place where u downloaded deb file.
1822937,2019-11-26 13:29:08 UTC,"Running into the same problem:
Ubuntu 19.04
NVIDIA Driver 440.33.01"
1822937,2020-07-22 21:07:06 UTC,I'm seeing what i think is a related problem using Ubuntu 20.04 and nvidia driver 440. IE default ubuntu 20.04 install from the ISO (and then updated).
1822937,2019-10-09 22:21:14 UTC,This bug is 'alive and well' with 340.107 driver in 19.10
1822937,2019-11-17 12:14:10 UTC,Also this bug wasn't fixed with 390 driver (19.10 stable release)
1822937,2019-04-17 23:07:53 UTC,What one would see from terminal (pkexec ls works fine)
1822937,2019-04-18 07:52:41 UTC,"what's the output of ""dpkg -l | grep screen-resolution-extra""?"
1822937,2019-04-18 11:11:15 UTC,ii  screen-resolution-extra    0.17.4      all     Extension for the GNOME screen resolution applet
1822937,2019-04-15 20:45:30 UTC,Thank you for your bug report. The issue seems similar to the one discussed on https://discourse.ubuntu.com/t/ubuntu-19-04-and-nvidia-settings/10580
1822937,2019-05-01 14:45:10 UTC,This bug also affects me on 19.04.
1822937,2019-05-21 14:53:38 UTC,This bug was fixed in the package nvidia-settings - 418.56-0ubuntu2
1822937,2019-09-16 02:23:42 UTC,"The bug was fixed in nvidia-settings 418.56, but I am using the nvidia 1650 gpu and the 418.56 driver doesn't support my gpu. Will the fix be released for the 430 driver as well?"
1822937,2019-09-16 10:20:01 UTC,"@Nils: which Ubuntu version are you running? nvidia-settings should work correctly in Ubuntu 19.10 (regardless of whether you are running the 430 driver, or the 435 driver, etc.)"
1822937,2019-04-22 13:02:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822944,2019-04-03 06:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1822944,2019-06-03 04:17:20 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1822964,2019-04-19 05:05:42 UTC,Problem is still there on nightly (2bcf38d)
1822964,2019-04-19 11:26:43 UTC,I cannot reproduce this issue with you test files kicad_bus2.
1822964,2019-04-19 17:29:33 UTC,"I have just re-downloaded the kicad_bus2.zip, opened it, hit ""update PCB from schematic"" in pcbnew and I get this log (which is obviously totally broken):"
1822964,2019-04-19 18:04:29 UTC,"Sorry, but the schematic is strange and must be fixed:
In sheet bleh, @ 566, 487 mm, I am seeing the bus D[15..0] connected to members DL0 to DL15."
1822964,2019-06-04 21:25:20 UTC,This seems to be an issue again.
1822964,2019-04-21 23:21:00 UTC,"I think this is fixed by https://git.launchpad.net/kicad/commit/?id=e2c12d8c2578dc6c3bf7293ccda2d747dfd9761c
Please re-open if you see further issues"
1822964,2019-04-23 04:30:08 UTC,Looks OK now.  Thanks a lot!
1822964,2019-04-13 02:53:03 UTC,I can reproduce the issue of wrong netname juggling with the test case that I have provided in #11.
1822964,2019-06-06 01:34:31 UTC,"Fixed in revision 42887544c941af8cf1d5796fb2e526635992e23e
https://git.launchpad.net/kicad/patch/?id=42887544c941af8cf1d5796fb2e526635992e23e"
1822964,2019-04-19 19:12:53 UTC,"Right, that D[15..0] connected to DL0 .. DL15 is a mistake, also in the original design.  It went unnoticed for years because it always worked."
1822964,2019-04-13 02:40:51 UTC,"I'm not on the latest 203019d.
The disconnection issue due to wrong global netname prefix seems to be gone.
However, now it mixes up netnames in the design (see attached screenshot) ... not sure what's with that ..."
1822964,2019-04-09 02:46:10 UTC,The last issue you mentioned is hopefully fixed by commit 94ba1bc
1822964,2019-04-09 03:17:20 UTC,"I was able to reduce the design and create a reproducer.  Please see the attachment.  Open the design, then update the PCB from the schematic -> some resistors will get dis/re-connected which is wrong."
1822964,2019-04-12 03:44:00 UTC,I believe this is fixed in 49d8c29
1822964,2019-04-03 08:42:28 UTC,"Recently a major update to the bus handling has been added. (Buses are now much more powerful)
This is very likely a result of that. Could you share a minimal project that showcases your behavior?"
1822964,2019-04-03 14:02:50 UTC,"Sorry, I can't share my designs.  However, the issue can be reproduced rather easily.  See the attached test project.  The resistors on both sheets are supposed to be connected together, but now they aren't anymore because the net names of the bus signals are not treated as global anymore.  The fact that the bus itself is global is not passed on to the bus signals."
1822964,2019-04-04 03:27:16 UTC,"Fixed in revision d5990100e18fc2f409cd72477116951eb69c91eb
https://git.launchpad.net/kicad/patch/?id=d5990100e18fc2f409cd72477116951eb69c91eb"
1822964,2019-04-03 12:27:36 UTC,"Hi Oleg,"
1822964,2019-04-07 03:03:48 UTC,"I've noticed that the problem does not occur in the test case I have provided.  I've tried to reproduce it in isolation, but without success."
1822964,2019-04-08 04:04:55 UTC,"Can you please check again after bd487d2 -- I don't think this is related to your issue, but it will help rule some things out."
1822964,2019-04-09 01:40:37 UTC,Just checked the latest nightly build (d88df89).  The issue is still there.
1822964,2019-04-07 01:20:12 UTC,Thanks for the quick response to this.
1822966,2019-04-05 14:45:41 UTC,"I was unable to recreate this with apport version 2.20.10-0ubuntu25 from disco on an Ubuntu mate desktop, using the apport-gtk frontend. When I click ""Other problem"" I receive a dialog indicating that I need to specify a package or PID and apport quits. Subsequently, I think this is specific to the kubuntu frontend."
1822966,2019-04-09 19:29:31 UTC,"Just to confirm, because Brian had a slightly different version number, this still exists on 2.20.10-0ubuntu26."
1822971,2019-06-12 14:43:46 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1822971,2019-04-03 09:22:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649542"
1822971,2019-06-05 12:46:29 UTC,"Reviewed:  https://review.opendev.org/649542
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a040c02a911ab3e880575761736258e5afce190d
Submitter: Zuul
Branch:    master"
1822973,2019-05-12 04:48:15 UTC,"Confirmed on Kubuntu 19.04. Any clicked links will open in the browser several minutes later. The time between each link actually opening in the browser (in my case, Firefox, but it also happens with Chrome) does not seem to be proportional to the time between clicks."
1822973,2019-05-15 05:30:02 UTC,"I was having the same issue until I found a solution. Whenever I tried to click a link in Slack, the logs in journalctl -f showed:"
1822973,2020-05-18 11:33:59 UTC,"This bug also affects me using Kubuntu 20.04 (Plasma 5.18) in the Wayland session, and Slack installed as snap.
Here, however, the fix of changing font settings does not work, and I don't see the error message in journalctl. Also, in my case the other processes that appear to be active are XWayland and dbus-daemon.
Not sure if this is a separate bug, however."
1822973,2019-05-02 00:35:37 UTC,"I tried to uninstall the slack snap and install it again, but it didn't change anything"
1822973,2019-05-15 16:24:49 UTC,"I can confirm the fix from Adan Koch.  I went into the Fonts panel, changed the anti-aliasing settings, Apply, change them back, Apply.  Now Slack links are opening almost immediately like in every other application.  I did not have to restart Slack."
1822973,2019-04-29 20:05:55 UTC,"I can confirm this as well.  For me it's only happening in Slack; a link will eventually open in the browser, after well over a minute rather than the 2 seconds previously.  So far that's the only application I've found where it happens.  Slack was installed via snap back on 18.10."
1822973,2019-06-18 18:47:28 UTC,"The fix from Adan Koch worked for me, too. System Settings > Fonts > Change anti-alias settings."
1822973,2019-04-26 07:18:28 UTC,could my issue mentioned in https://askubuntu.com/questions/1137876/opening-links-from-some-applications-takes-a-long-time be related?
1822973,2019-04-09 19:30:26 UTC,It might also be worth noting that clicking links in the telegram snap in the session work fine.
1822973,2019-04-03 15:29:21 UTC,"Running xdg-open and kde-open5 on the command line directly work fine as well, by the way."
1822973,2019-04-03 14:43:38 UTC,I haven't tried under gnome and I'm afraid I don't really want to mess about with my main desktop to do so. I've tested again under kubuntu 18.04 and it works fine there.
1822973,2019-04-03 13:44:08 UTC,"The issue looks like one in the kde portal, do you get the problem under GNOME?"
1822973,2019-04-27 01:34:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822984,2019-06-03 08:48:13 UTC,"The verification of the Stable Release Update for openssl has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822984,2019-06-03 08:48:02 UTC,This bug was fixed in the package openssl - 1.1.1-1ubuntu2.2
1822984,2019-04-25 08:33:08 UTC,Thanks for the verification! The SRU has some reported autopkgtest regressions - could you take a look at those?
1822984,2019-04-11 16:20:42 UTC,"generated new weak key, cert and try to use it with current cosmic's openssl and succeed:"
1822984,2019-04-04 06:05:39 UTC,This bug was fixed in the package openssl - 1.1.1b-1ubuntu2
1822984,2019-04-05 08:46:29 UTC,"Hello Dimitri, or anyone else affected,"
1822984,2019-04-03 16:05:35 UTC,"The patch was added by Dimitri in cosmic to restore compatibility with older and less secure TLS implementations using weak keys.  However, bionic shipped without compatibility with those less secure keys, and we are unaware of any complaints about this change in bionic.  This distro patch to lower the security baseline of openssl 1.1 was being introduced in SRU to bionic as part of the openssl 1.1.1 backport, and I rejected that upload after discussion with the security team, because it is not justifiable for the SRU to *lower* the security baseline in SRU without specific reports of breakage."
1822984,2019-04-03 15:41:17 UTC,looks like someone else accepted with this question still pending...
1822984,2019-04-03 14:40:06 UTC,that regression potential doesn't really describe what might regress... I think it could be improved.
1822984,2019-04-03 16:23:52 UTC,"But equally, I would not want to keep cosmic more insecure than what bionic and disco will be. And currently, cosmic is a release regression w.r.t. bionic GA. Upgrading to newer releases, should not result in looser acceptance of insecure protocols."
1822985,2019-04-09 08:47:26 UTC,Andrew I may have not well understand. From my point of view the comment is saying by default this will create 3 volumes of 1G so it warns us to have at least an env ready to handle it. Probably because by default volume_size = 1 [0]
1822985,2020-01-24 15:44:15 UTC,Based on the long inactivity I'm assuming that the reporter's problem got resolved.
1822986,2019-04-03 15:52:07 UTC,I've asked this same question before during a placement install guide review:
1822986,2019-06-06 07:33:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/663530"
1822986,2019-06-14 21:53:40 UTC,"Reviewed:  https://review.opendev.org/663530
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97ca86fad75dd601f6d38de95bb6a6709f0fdf80
Submitter: Zuul
Branch:    master"
1822986,2019-09-27 09:03:10 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1822987,2019-04-08 11:20:14 UTC,"There are two nouveau related patches added in 4.15.0-46
 - drm/nouveau: Use drm_connector_list_iter_* for iterating connectors
 - drm/nouveau: Avoid looping through fake MST connectors"
1822987,2019-04-12 10:38:58 UTC,"This can be reproduced in the very beginning of Bionic 4.15.0-20-generic, please see the attachment for boot dmesg."
1822987,2019-07-05 06:48:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822987,2019-04-08 10:42:22 UTC,"for Bionic, I can see that this issue occurs from 4.15.0-46."
1822987,2019-04-09 09:18:43 UTC,This issue might leads to the boot time increase in bug 1821027
1822987,2019-04-03 11:02:47 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1822987,2019-04-03 11:00:06 UTC,This change was made by a bot.
1822987,2019-04-08 04:41:05 UTC,"This issue could be found on Bionic as well, the system can boot to the desktop with nouveau driver."
1822989,2019-04-22 19:32:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1822991,2019-04-03 11:43:56 UTC,"Moved to https://storyboard.openstack.org/#!/story/2005356, probably it is better place. Sorry for duplicate."
1822991,2020-06-19 13:23:26 UTC,"These values were moved to overrides, so the default values.yaml shouldn't break RHEL/Centos for this reason anymore."
1822991,2020-06-19 13:24:30 UTC,https://github.com/openstack/openstack-helm/blob/master/nova/values_overrides/apparmor.yaml
1822993,2019-06-10 14:54:16 UTC,This bug was fixed in the package python3-stdlib-extensions - 3.6.8-1~18.04
1822993,2019-06-10 14:54:13 UTC,This bug was fixed in the package python-stdlib-extensions - 2.7.16-2~18.04
1822993,2019-06-10 14:53:28 UTC,"Autopkgtests are passing for both of the remaining bionic uploads. There is one ADT regression from sphinx, but the failure is the same as for any other package so it can be ignored. Setting as verified and releasing."
1822993,2019-04-29 16:58:13 UTC,This bug was fixed in the package python-stdlib-extensions - 2.7.16-2~18.10
1822993,2019-04-29 16:48:03 UTC,This bug was fixed in the package python3-stdlib-extensions - 3.6.8-1~18.10
1822993,2019-04-29 16:47:55 UTC,This bug was fixed in the package python2.7 - 2.7.16-2~18.10
1822993,2019-04-29 16:47:51 UTC,This bug was fixed in the package python3.7 - 3.7.3-2~18.10
1822993,2019-04-29 16:47:47 UTC,"The verification of the Stable Release Update for python3.6 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1822993,2019-04-29 16:47:44 UTC,This bug was fixed in the package python3.6 - 3.6.8-1~18.10
1822993,2019-04-29 15:37:52 UTC,"The disco packages are now successfully built. All autopkg tests except for ironic, murano and murano-agent pass. These are no regressions, related to Python 3.7, and according to Corey:"
1822993,2019-04-25 14:13:00 UTC,"Hello Matthias, or anyone else affected,"
1822993,2019-04-25 14:06:56 UTC,"Hello Matthias, or anyone else affected,"
1822993,2019-04-11 20:44:07 UTC,"Hello Matthias, or anyone else affected,"
1822993,2019-04-11 20:40:38 UTC,"Hello Matthias, or anyone else affected,"
1822993,2019-04-11 20:38:25 UTC,"Hello Matthias, or anyone else affected,"
1822993,2019-04-11 20:35:47 UTC,"Hello Matthias, or anyone else affected,"
1822993,2019-04-11 20:06:25 UTC,"Hello Matthias, or anyone else affected,"
1822993,2019-04-29 16:45:41 UTC,I checked those and hinted them for cosmic. This looks now good to release.
1822996,2019-04-05 12:51:52 UTC,"Can you please tell me if:
1) it works with latest vbox6 version
2) it is reproducible with the upstream deb file"
1822996,2019-06-05 04:17:22 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1822998,2019-06-23 04:18:26 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1822998,2019-04-23 14:39:15 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1822999,2019-04-05 15:17:14 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650337"
1822999,2019-04-05 15:17:52 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650340"
1822999,2019-09-19 10:14:48 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1822999,2019-04-09 17:25:06 UTC,"Reviewed:  https://review.openstack.org/650337
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ba64c6ab9798b833352cd1ace51883c6f5cb7ec9
Submitter: Zuul
Branch:    stable/stein"
1822999,2019-04-05 04:37:34 UTC,"Reviewed:  https://review.openstack.org/649615
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dd95246fbe584c3008af32464d90b41fb2d9f888
Submitter: Zuul
Branch:    master"
1822999,2019-04-06 05:39:23 UTC,"Reviewed:  https://review.openstack.org/650340
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5a099803149b2e85e6662ab85842bb087e92ed38
Submitter: Zuul
Branch:    stable/stein"
1822999,2019-04-05 04:37:24 UTC,"Reviewed:  https://review.openstack.org/649623
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fa5e9c6fabb8e3f2e16646a87ca29c754e7f8c7a
Submitter: Zuul
Branch:    master"
1822999,2019-04-16 17:56:13 UTC,This issue was fixed in the openstack/neutron 14.0.1 release.
1822999,2019-04-03 13:33:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649615"
1822999,2019-04-03 12:27:30 UTC,eg. http://logs.openstack.org/09/649309/5/check/networking-midonet-tempest-aio-ml2-centos-7/3eacd96/logs/screen-neutron-api.txt.gz
1822999,2019-04-03 12:29:35 UTC,"in the log in the comment #1, the backend (midonet) is complaining about the mac address ""FA-16-3E-29-79-FB""."
1822999,2019-04-03 13:59:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649623"
1822999,2019-04-03 13:14:53 UTC,"This is a relic of the shift to using the Port OVO object, which uses netaddr.EUI instead of string for MAC address.  The dashed form is it's default translation to string.  Let me see how I can go about fixing that."
1822999,2019-04-03 12:58:25 UTC,i added neutron because the change seems unintended.
1823003,2019-04-04 07:19:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/649901"
1823003,2019-04-16 01:07:13 UTC,"Reviewed:  https://review.openstack.org/649901
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=dc2f29ac9ba18f672964d25862fe7cd4907af36e
Submitter: Zuul
Branch:    stable/queens"
1823003,2019-06-21 15:22:49 UTC,This issue was fixed in the openstack/instack-undercloud 8.4.8 release.
1823004,2019-07-04 12:29:53 UTC,"Marking trigger bugs as duplicates of 1828639, to have one bug to track the fix in with a clean reproducer."
1823004,2019-05-31 19:07:00 UTC,Seems like this might be related to bug 1825211; seems like roughly the same issue (triggers looping) at about the same point (quite close to shared-mime-info; but that may be a red herring). We've had some discussions before that this may be a bug in dpkg / triggers.
1823004,2019-05-29 23:16:45 UTC,Anyone lucky enough to find any fixes to this? I faced this issue too yesterday.
1823004,2019-05-03 18:24:22 UTC,"I also received this error upgrading from 18.10. As with others, install seemed to nearly finish (as judged by the progress bar)."
1823004,2019-05-01 11:05:39 UTC,Interesting experiences.
1823004,2019-04-28 10:16:22 UTC,"See attachment - same error, other package."
1823004,2019-04-24 03:56:07 UTC,"To add to my previous comment, the uninstaller freezes with the following message every 10-30 seconds, uncountable times:"
1823004,2019-04-24 03:43:24 UTC,"This bug also affects me. Unfortunately, the automatic reversion to the previous version is a mess and doesn't seem to leave the system in the previous (working, 18.10) state."
1823004,2019-04-20 19:29:02 UTC,"I have discovered that the desktop context menu no longer contains choices to alphabetize icons, nor to lock into the underlying grid."
1823004,2019-04-20 19:11:26 UTC,I have this error too. The problem is that the upgrader is not continuing with the uninstall of programs and says that there's an error.
1823004,2019-04-19 16:27:58 UTC,More info regarding the bug during my upgrade to 19.04:
1823004,2019-04-19 15:06:18 UTC,Exactly the same issue for me too.
1823004,2019-04-18 22:41:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823004,2019-04-03 16:43:19 UTC,From Apttermlog.txt we can see:
1823005,2019-04-03 13:19:48 UTC,Fix proposed here: https://review.openstack.org/649403
1823005,2019-04-04 07:35:14 UTC,"Reviewed:  https://review.openstack.org/649403
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=524f969bfc8a96ebc2d331e241738c8ae4820b58
Submitter: Zuul
Branch:    master"
1823005,2019-04-05 13:59:15 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc1 release candidate.
1823005,2019-04-13 14:20:09 UTC,"Reviewed:  https://review.openstack.org/650267
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=a47870032db21744fbcd705903e5836f3c6f2803
Submitter: Zuul
Branch:    stable/rocky"
1823005,2019-06-14 01:32:38 UTC,This issue was fixed in the openstack/kolla-ansible 7.1.1 release.
1823009,2019-06-20 08:18:26 UTC,"User with ""neutron_interconnection_peer"" role also need to have ""advsvc"" role to be able to access interconnection ressources from another tenant."
1823011,2020-09-01 12:37:41 UTC,I am currently also experiencing this bug while I am attempting to create a monitoring overlay for the openstack-base bundle.
1823011,2020-03-12 03:03:06 UTC,Could you please provide us with a bundle and / or more instructions on how to reproduce the problem?
1823015,2019-04-19 11:47:48 UTC,"Hello James,
is it possible to collect the kernel panic message? (screenshots or etc.)"
1823015,2019-05-15 07:34:03 UTC,"Contacted by the bug reporter, this issue is still reproducible:"
1823015,2019-07-15 04:17:20 UTC,[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.]
1823020,2019-04-10 07:54:42 UTC,"Hello,"
1823020,2020-05-07 07:42:17 UTC,I've added support for auto-completion from outside of the openstack CLI shell but I'm a bit stumped as to why its not working from within the shell.
1823023,2019-04-04 08:25:20 UTC,"Hi,"
1823023,2019-04-08 09:42:02 UTC,"Simple ""ip netns"" commands failing sounds like this is out of neutron scope, adding OSA directly and marking incomplete on our side for now"
1823026,2019-04-12 09:43:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823026,2019-04-15 12:25:47 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1823026,2020-07-08 13:02:38 UTC,Looks like python3-m2crypto was added in https://launchpad.net/ubuntu/+source/m2crypto/0.31.0-5. It is available in Ubuntu 19.10 and newer releases.
1823028,2019-04-03 14:48:05 UTC,It seems to work correctly once I closed and reopened Zim. I think it may have been brought on by hitting the wrong key combination.
1823029,2019-04-16 17:32:16 UTC,"(but unlike the on-suspend lockup, the journal continues to accumulate some entries -- possible the system wasn't fully locked up but the display was?)"
1823029,2019-04-16 17:30:00 UTC,"From reading  the logs that's what it looks like -- it appears the lid was closed at 21:48:40 and then suspend was successful at 21:49:10 or 21:49:25, but then the system immediately resumes at 21:49:25, and doesn't fully recover"
1823029,2019-09-03 18:43:34 UTC,Alternatively this commit I suspect should help:
1823029,2019-04-16 14:13:02 UTC,"Had another failure with similar symptoms (fan on, screen black once laptop lid opened), but logs look different this time."
1823029,2019-04-18 00:09:58 UTC,"Either way, whatever fix is in the https://people.canonical.com/~khfeng/lp1823029/ kernel is very effective if not perfect -- can it be put into the main repo kernels or will I need to keep kernel packages held for a while?"
1823029,2019-04-16 14:42:32 UTC,"The may seem to the same, but do the symptoms occur at different time? The original issue happens at suspending, while #20 occurs at resuming?"
1823029,2019-04-22 09:21:14 UTC,https://lkml.org/lkml/2019/4/22/81
1823029,2019-10-22 21:52:14 UTC,"fwiw, with a 5.3 kernel on eoan and a system-sleep script that does `btmgmt power off` pre sleep, and `btmgmt power on` post sleep, I haven't been seeing the lock up issue."
1823029,2019-05-09 21:43:38 UTC,"What did you change? I have a colleague with the same device but a different distribution, so I'm interested in reproducing the fix with another kernel."
1823029,2019-05-10 06:07:43 UTC,Comment #25?
1823029,2019-06-19 05:52:02 UTC,"looks like no responses to v2, anything I can do to help move this along?  could it at least make it into an updated kernel build with security patches, if not the ubuntu patch set?"
1823029,2019-07-05 18:33:53 UTC,"I don't see this:
pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
Which is in the previous log."
1823029,2019-04-16 00:35:32 UTC,still looking good after several more sleep cycles today
1823029,2019-08-30 22:20:49 UTC,any chance we can see this in an ubuntu kernel despite the lack of response on lkml?
1823029,2019-04-22 09:21:29 UTC,"Yes, please use my custom built kernel in the interim."
1823029,2019-04-15 05:03:05 UTC,initial tests are looking good (4 successful suspends & resumes during this boot so far).  Will keep testing and report back.
1823029,2019-07-22 03:30:53 UTC,"ok thanks, my 2nd attempt at patching 5.0.0.20.21 with v2 appears to be working as well as your older build."
1823029,2019-04-13 21:04:56 UTC,linux-modules-extra package looks corrupt:
1823029,2019-04-14 09:13:37 UTC,Re-copied the files. Please try again.
1823029,2019-04-03 15:00:06 UTC,This change was made by a bot.
1823029,2019-04-04 07:16:20 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc3 kernel [0]."
1823029,2019-04-04 20:57:33 UTC,"trying to boot with the 5.1-rc3 kernel resulted in a black screen that never asked for my encrypted drive password.  I could ctrl+alt+delete to reboot back to bios/grub, but could not successfully boot the system."
1823029,2019-04-09 05:52:52 UTC,Have you seen the issue on Bionic kernel (v4.15)?
1823029,2019-04-09 13:59:19 UTC,"Yes, I've seen it on both bionic and cosmic kernels in addition to disco's"
1823029,2019-04-10 03:53:30 UTC,"Please boot with kernel parameter ""usbcore.dyndbg=+p"", reproduce the issue, and attach kernel log."
1823029,2019-07-05 17:09:50 UTC,"fwiw, i tried to build 5.0.0.20.21 with v2 applied, and was able to reproduce the bug (I may have built it incorrectly though?  I git applied the two patches from a clone of git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco and then did `fakeroot debian/rules clean` ; `AUTOBUILD=1 fakeroot debian/rules binary-debs` and installed the resulting packages)"
1823029,2019-04-11 05:39:05 UTC,The Bluetooth controller wakes up early when USB Controller is trying to suspend.
1823029,2019-04-11 16:57:07 UTC,"ok, have added those commands to a /lib/systemd/system-sleep script to have that happen before suspend and will report back if it helps or not."
1823029,2019-04-11 00:35:34 UTC,"here's the bottom of journalctl -b -1 from a boot with ""usbcore.dyndbg=+p"" that reproduced the issue (let me know if there's a better way to get the kernel log you're looking for):"
1823029,2019-04-11 17:38:49 UTC,Is gnome-bluetooth up-to-date? See LP: #1822533.
1823029,2019-04-11 20:51:37 UTC,"yes, all packages are up to date, and specifically the gnome-bluetooth package at 3.32.1-1 since april 3rd."
1823029,2019-04-12 04:36:10 UTC,"Saw same thing with the btmgr commands added to system-sleep script, attaching kernel log from that boot"
1823029,2019-04-13 17:11:04 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1823029/"
1823036,2019-04-06 15:34:12 UTC,Doing that would create a dependency loop which as I understand it is considered undesirable because it means installation order ends up unspecified.
1823037,2020-04-21 20:35:37 UTC,"@MasterCATZ, please check this with the 20.04 5.4 kernel. If it's still an issue could you please file a separate kernel bug for your corruption issue?"
1823037,2019-12-17 09:06:27 UTC,Running Ubuntu 19.10 5.4.3-050403-generic
1823037,2019-08-22 16:16:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1823037,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1823037,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1823037,2019-06-07 17:50:28 UTC,SRU Request submitted
1823037,2019-05-20 16:45:12 UTC,All three test kernels have passed 24+ hour testing.
1823037,2019-05-14 21:09:16 UTC,"Hi Jerry,"
1823037,2019-12-18 21:58:02 UTC,seems I finally found the real issue
1823037,2019-05-06 15:15:26 UTC,"So I'm a bit confused because I've been told that A: additional patches are necessary to solve the issue, and B: that the issue is solved without those additional patches."
1823037,2019-04-23 08:38:06 UTC,Confirming that I was unable to reproduce the issue on linux-image-4.15.0-46-generic (4.15.0-46.49) from the test kernels repository with my test setup.
1823037,2019-04-18 19:12:30 UTC,An additional patch has been identified that will be needed to solve this issue.
1823037,2019-04-08 12:41:03 UTC,"Test kernels are up here:
https://people.canonical.com/~jlane/testkernels/"
1823037,2019-04-05 07:33:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823037,2019-04-03 15:21:38 UTC,"related branch
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco/+ref/amd-iommu-cherrypick"
1823037,2019-05-06 16:55:19 UTC,"Jeff, The second patch improves the fix against the amount of memory in the system. We still need both patches."
1823041,2019-06-20 14:30:18 UTC,"Thanks, Jane!  Merged to 3.3 and master."
1823041,2019-06-19 21:48:53 UTC,"Works well for me, Bill.  Thanks very much."
1823041,2019-04-03 20:05:34 UTC,Separate branch with a single commit pushed for migrating dialogs to observables:
1823041,2019-06-19 20:47:14 UTC,"Thanks, Jane."
1823041,2019-06-19 18:55:06 UTC,"Here's a branch that signs off on Bill's commit, rebases against master, and welcomes some new dialogs into the world of Observables. :-D"
1823041,2019-04-03 18:42:18 UTC,"Addendum to my previous comment, a confirm dialog should still produce a success event with a true/false result, in part because they are both expected results, but also so the caller is not required to implement a complete handler to know the dialog is done."
1823041,2019-04-03 16:24:24 UTC,This turned out to be considerably less disruptive than expected.
1823041,2019-04-03 16:45:30 UTC,"Interesting, Jane, it had not occurred to me a dialog would produce multiple results, but I can see how that might be useful in some cases.  I suppose as a bonus, it's also easy to turn Observables into promises where preferred."
1823041,2019-04-03 16:24:18 UTC,+1 to not treating closing a modal as an error.
1823043,2019-04-03 15:55:53 UTC,"""or in the default 'nova' zone"" isn't really correct, the default_schedule_zone option is None by default, and really shouldn't be set to 'nova'. You probably confused that with the default_availability_zone (yes it's super confusing) which defaults to 'nova' but that is the default AZ for each compute service to be in, which is not necessarily the same as what the user requested when creating the server (or was given based on default_schedule_zone configuration)."
1823043,2019-04-05 21:07:07 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650444"
1823043,2019-06-15 00:15:42 UTC,"Reviewed:  https://review.opendev.org/650444
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=abe041ae1cc42d9a3ade187b7c930b7c6c3a9d5f
Submitter: Zuul
Branch:    master"
1823043,2019-09-27 09:04:49 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1823044,2019-04-03 16:15:44 UTC,"Note: support for ironic_inspector_pxe_filter was only added in the Stein release. We only use Docker CE in Rocky by default for Ubuntu, but it is possible to change docker_legacy_packages to false on other distros in Rocky to use Docker CE."
1823044,2019-04-03 16:17:25 UTC,Example iptables config for inspector:
1823044,2019-04-04 06:49:09 UTC,'Fix' proposed in master: https://review.openstack.org/649673
1823044,2019-04-10 09:17:48 UTC,"Reviewed:  https://review.openstack.org/649673
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=86e83faeb1fd088d44c5108a5ec835eba6316b2d
Submitter: Zuul
Branch:    master"
1823044,2019-04-10 09:24:56 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/651474"
1823044,2019-04-10 13:06:16 UTC,"We don't support the dnsmasq inspector filter in rocky, so it's not obvious what to do there."
1823044,2019-04-13 14:28:29 UTC,"Reviewed:  https://review.openstack.org/651474
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=16e982401191602efaf1c034b8fe645d62e7181e
Submitter: Zuul
Branch:    stable/stein"
1823044,2019-07-18 00:37:56 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc2 release candidate.
1823044,2019-11-11 15:40:50 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1823045,2019-05-14 19:09:39 UTC,This bug was fixed in the package linux-aws - 4.4.0-1083.93
1823045,2019-07-30 08:13:05 UTC,Config could be found in AWS Eoan as well. Mark this as fix-released.
1823051,2019-05-08 22:11:20 UTC,cosmic:
1823051,2019-04-03 16:55:19 UTC,"Two possible fixes for this are 1) to add ReadWritePaths=-/etc/ufw to the knockd.service, or 2) change the knockd.service from ProtectSystem=full to ProtectSystem=true.  Relaxing the ProtectSystem might actually be the best approach since the only change between 'full' and 'true' is allowing r/w access to /etc."
1823051,2019-04-24 15:14:55 UTC,Sponsored in 'Eoan'
1823051,2019-04-24 16:15:31 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu3
1823051,2019-04-30 22:52:51 UTC,"Hello Dan, or anyone else affected,"
1823051,2019-04-30 22:58:38 UTC,"Hello Dan, or anyone else affected,"
1823051,2019-04-30 23:01:18 UTC,"Hello Dan, or anyone else affected,"
1823051,2019-05-08 22:03:44 UTC,disco verified using steps from test case:
1823051,2019-05-08 22:17:56 UTC,bionic:
1823051,2019-05-09 09:04:06 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu2.1
1823051,2019-05-09 09:04:17 UTC,"The verification of the Stable Release Update for knockd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823051,2019-05-09 09:21:46 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu1.18.10.2
1823051,2019-05-09 09:25:58 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu1.18.04.2
1823053,2019-06-17 11:29:58 UTC,"> Sadly, there are RADIUS servers which suffer from TLS version intolerance and will refuse authentication when the client offers TLS 1.3
"
1823053,2019-06-17 11:19:02 UTC,"It seems this is also applicable to ubuntu bionic since openssl 1.1.1 landed in bionic-updates. We have bionic clients that cannot connect to the enterprise wifi because they attempt TLS 1.3. Recompiling openssl with the ""no-tls1_3"" Configure option fixes the problem. See also https://github.com/FreeRADIUS/freeradius-server/issues/2385"
1823054,2019-04-04 13:25:33 UTC,Confirming xdg-desktop-portal 1.0.3-0ubuntu0.0 fixes this issue and xdg-desktop-portal-gtk is working as expected. Thanks to all involved!
1823054,2019-06-04 04:17:24 UTC,[Expired for xdg-desktop-portal-gtk (Ubuntu) because there has been no activity for 60 days.]
1823054,2019-04-03 18:40:59 UTC,Thanks for the speedy reply and referral to the uncompleted bug report. I forgot about xenial-proposed (which I tend not to enable on LTS). After downloading http://archive.ubuntu.com/ubuntu/pool/universe/x/xdg-desktop-portal/xdg-desktop-portal_0.11-1_amd64.deb and manually editing dependencies to include xenial's dbus-x11 (default-dbus-session-bus | dbus-session-bus | dbus-x11) I succesfully installed xdg-desktop-portal-gtk.
1823054,2019-04-03 17:29:29 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1823054,2019-04-04 12:28:09 UTC,"The issue should be resolved now, could you try again?"
1823056,2019-05-14 22:54:34 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823056,2019-04-13 07:57:02 UTC,This bug was fixed in the package linux - 5.0.0-11.12
1823056,2019-04-25 22:32:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1823056,2019-04-25 23:40:03 UTC,"Requesting to rerun linux test cases, as triggered by gcc-8 to confirm the fix.
As currently they pass rebuild test, but end up as an overall FAIL due to regression suite.
they should turn green under:
http://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html#gcc-8"
1823056,2019-04-26 12:15:09 UTC,"https://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html#gcc-8 all is now green, and checking the results one can see that rebuild test passed, and the regression test suite was skipped, correctly."
1823056,2019-04-29 16:04:00 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1823056,2019-04-30 14:08:23 UTC,"Triggering for example linux adt test in bionic, as triggered by openssl to verify the fix."
1823056,2019-04-30 16:16:28 UTC,http://autopkgtest.ubuntu.com/packages/l/linux/bionic/amd64 and it passed. Works as expected.
1823056,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1823056,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1823056,2019-05-16 13:02:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1823056,2019-06-03 07:44:59 UTC,Confirmed that with the fix on xenial a autopkg test triggered by a package other then linux-meta triggers only the rebuild test and not the regression tests:
1823056,2019-06-04 09:11:38 UTC,This bug was fixed in the package linux - 4.4.0-150.176
1823061,2019-04-03 19:01:45 UTC,OK I found the solution at https://unix.stackexchange.com/questions/202332/sudo-source-command-not-found/202334 but it gave another problem:
1823061,2019-10-09 22:26:34 UTC,"The easy rsa documentation in this guide is outdated and should be updated.  Many of the commands after source vars are not available and should be converted to ./easyrsa commands.  Even the configuration data in /etc/openvpn/easy-rsa/vars is incorrect / outdated.  In its current state, the Ubuntu guide will not work with 18.04.  I have been working off 3rd party guides like: https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04"
1823067,2019-04-18 17:11:25 UTC,We have 3 relevant voices here:
1823067,2019-09-25 12:17:31 UTC,This is a new feature request and it is being discussed by appropriate people. I'm marking it as a wishlist item since it is a new feature. Please feel free to raise the importance if this is affecting you seriously.
1823070,2019-11-07 00:08:10 UTC,This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.12
1823070,2019-11-07 00:07:17 UTC,"The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823070,2019-11-07 00:07:00 UTC,This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.2
1823070,2019-11-07 00:04:00 UTC,"""1 updates""? Having an ""s"" for 1 update is incorrect."
1823070,2019-11-01 17:30:26 UTC,"root@uu-sru-x:~# unattended-upgrade --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial
Packages that will be upgraded:
root@uu-sru-x:~# update-motd
Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 5.0.0-32-generic x86_64)"
1823070,2019-11-01 17:29:33 UTC,"root@uu-sru-bb:~# unattended-upgrade --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
Packages that will be upgraded: file libidn2-0 libmagic-mgc libmagic1 libxslt1.1 python3-apport python3-problem-report
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
(Reading database ... 28655 files and directories currently installed.)
Preparing to unpack .../libidn2-0_2.0.4-1.1ubuntu0.2_amd64.deb ...
Unpacking libidn2-0:amd64 (2.0.4-1.1ubuntu0.2) over (2.0.4-1.1build2) ...
Setting up libidn2-0:amd64 (2.0.4-1.1ubuntu0.2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Log ended: 2019-11-01  17:09:03"
1823070,2019-11-07 00:09:12 UTC,This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.4
1823070,2019-10-24 20:31:48 UTC,"Hello Steve, or anyone else affected,"
1823070,2019-10-24 20:29:22 UTC,"Hello Steve, or anyone else affected,"
1823070,2019-10-24 20:24:12 UTC,"Hello Steve, or anyone else affected,"
1823070,2019-07-12 02:04:36 UTC,This bug was fixed in the package unattended-upgrades - 1.13
1823070,2019-05-23 11:21:51 UTC,https://github.com/mvo5/unattended-upgrades/pull/200
1823070,2019-11-01 17:21:59 UTC,"root@uu-sru-dd:~# unattended-upgrade --verbose
Initial blacklist :
Initial whitelist:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=disco, o=Ubuntu,a=disco-security, o=UbuntuESM,a=disco
Packages that will be upgraded: file libidn2-0 libmagic-mgc libmagic1 libxslt1.1 python3-apport python3-problem-report
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
(Reading database ... 28941 files and directories currently installed.)
Preparing to unpack .../libidn2-0_2.0.5-1ubuntu0.3_amd64.deb ...
Unpacking libidn2-0:amd64 (2.0.5-1ubuntu0.3) over (2.0.5-1) ...
Setting up libidn2-0:amd64 (2.0.5-1ubuntu0.3) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
Log ended: 2019-11-01  17:08:54"
1823071,2020-04-27 21:22:59 UTC,This is fixed as part of the receipt omnibus patch. My signoff to that is at:
1823071,2020-04-28 17:30:53 UTC,"Fixes pushed to master and rel_3_5. Thanks Dan, Jason, and Terran!"
1823071,2020-03-16 17:10:15 UTC,"Daniel Pearl was working on this bug, among others, before he left CW MARS.  He left behind an omnibus branch that is intended to fix most of these issues.  I have had these bugs assigned to me since before his departure because it was my intention to clean his branch up, test it, and add any missing bits.  I have not had time to do this, so I am simply putting the branch out there in the hope that someone can test what's there during bug squashing week or whenever."
1823071,2019-04-04 18:03:55 UTC,"This references the following in the schema
transit_copy ->copy_status"
1823072,2019-04-03 20:29:05 UTC,"Fixed in revision 591894c7e6ca12d69b54f1eaa96914b1b02ea69e
https://git.launchpad.net/kicad/patch/?id=591894c7e6ca12d69b54f1eaa96914b1b02ea69e"
1823073,2019-04-23 14:38:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1823073,2019-06-23 04:18:24 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1823074,2019-04-03 20:11:40 UTC,"I see that this is a result of LP #1764794, I've adjusted my copy debian-installer source package to compensate (using bionic version as a template)."
1823076,2020-07-06 21:24:18 UTC,"Hi You-Sheng,"
1823076,2020-05-13 13:37:54 UTC,"@Jerome, could you help testing my backport of the patches you mentioned to v5.6 in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1823076:"
1823076,2020-05-12 21:32:24 UTC,"A fix for this issue is planned for v5.7, included from rc1 up to rc5 so far, with this patch series: https://lore.kernel.org/patchwork/cover/1208369/ and the 4 commits from 9952d90ea2885d7cbf80cd233f694f09a9c0eaec up to 4867bd007d25a8dfd4ffc558534f7aec8b361789"
1823076,2020-05-04 08:42:16 UTC,"Same bug here. I'm using a Lenovo X1 Carbon 6th Gen.
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.67.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-46-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz
Memory: 15.4 GiB of RAM"
1823076,2019-12-27 16:04:35 UTC,"Please power off your laptop completely  and power it on again after 1
minute. Paste dmesg log since boot and your linux-firmware version, then we
may know which file to fix."
1823076,2019-12-26 16:49:09 UTC,I am having this issue also. Turning off bluetooth with bluez (Bluetooth Manager) applet icon and manually stopping bluetooth service the suspend works. Otherwise I have seen suspends but usually just wakes up in a few seconds. Lenovo P53 with Ubuntu 19.10 and kernel 5.3.0-24-generic
1823076,2019-10-08 17:17:22 UTC,Newer firmwares [1] may be required.
1823076,2019-10-07 15:24:43 UTC,"""Same Result"" means it wakes up a few seconds after sleep. With bluetooth disabled, it stays in sleep as expected."
1823076,2019-10-05 06:20:41 UTC,"""Same result"" here means it doesn't wake up anymore?"
1823076,2019-09-19 08:38:31 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3/"
1823076,2020-05-13 11:43:25 UTC,PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1823076
1823076,2019-09-07 10:28:08 UTC,You can use the following workaround.
1823076,2019-04-04 03:05:19 UTC,It sounds like you've found a good workaround but I am curious about the root cause here.
1823076,2019-09-15 15:52:51 UTC,I can confirm the same is happening to me at Disco running on Dell XPS 13 9380.
1823076,2019-04-04 03:06:02 UTC,"Also, are you able to change any settings in your BIOS to prevent wakeup from Bluetooth?"
1823076,2019-04-04 15:23:27 UTC,"I believe this issue was due to ""legacy suspend"" rather than ""modern suspend"" selected in UEFI. After a couple suspends I am no longer seeing the problem, but will reopen if it happens again."
1823076,2019-04-04 15:33:42 UTC,"Scratch that; the first couple suspend operations did work, and then they stopped again. I'll do more testing and report back. I did rule out mouse movement by using the hardware power switch on the mouse."
1823076,2019-10-04 11:26:19 UTC,"I have the same problem on my Lenovo T480s with Xubuntu 19.04. Disabling Bluetooth helps as a workaraound.
I also tried the mainline kernel 5.3.2 with the exact same result."
1823076,2019-04-05 23:14:44 UTC,If I remove the bluez package there are no issues with suspend.
1823076,2019-05-15 21:34:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823076,2019-08-31 12:52:09 UTC,"I think this issue is reproducible on laptops which do not have S3 system state, but rather use S0ix (like Dell XPS)."
1823076,2019-04-04 22:49:26 UTC,"So after some more investigation it's clear that the problem is inconsistent. Sometimes wake immediately follows suspend, sometimes not. Sometimes it takes a while to wake up, up to a few minutes, other times it's immediate. Occasionally, it seems to suspend fine; or maybe I'm not waiting long enough for the wake."
1823078,2021-01-22 21:45:44 UTC,Version 2.41: https://review.opendev.org/c/openstack/manila-ui/+/689681
1823078,2020-02-10 23:16:51 UTC,"Reviewed:  https://review.opendev.org/704157
Committed: https://git.openstack.org/cgit/openstack/manila-ui/commit/?id=7ff565844ae1e00be4025a488087f687fe5091ac
Submitter: Zuul
Branch:    master"
1823078,2020-04-06 21:52:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717866"
1823078,2020-04-06 22:57:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/717875"
1823078,2020-04-15 16:26:52 UTC,"Reviewed:  https://review.opendev.org/717866
Committed: https://git.openstack.org/cgit/openstack/manila-ui/commit/?id=c94ddec5c6897dd91aef8c8b98fb5f32c7a570d0
Submitter: Zuul
Branch:    master"
1823078,2020-04-15 19:38:28 UTC,"Reviewed:  https://review.opendev.org/717875
Committed: https://git.openstack.org/cgit/openstack/manila-ui/commit/?id=2db03371259afc730babf150496df2edc1170466
Submitter: Zuul
Branch:    master"
1823080,2019-05-06 16:41:49 UTC,"You mean, just the same as with graphical lines of the footprint. Those are always locked relative to the position of the footprint itself, just as pads."
1823080,2019-04-08 11:25:04 UTC,Anton i feel you misunderstood my request. It is not about locking the absolute position of the footprint inside the layout. Not even about locking the absolute position of any footprint element inside the layout.
1823080,2019-04-07 15:51:45 UTC,"The blocking of the positional notation of the component footprint is, in principle, already present; if you move the component footprint, they also move and occupy the same place as the footprint. It can be done in such a way that moving in no way is possible in principle, but then you need to adjust the font and text to the dimensions of the component's footprint."
1823085,2019-05-07 18:58:48 UTC,Confirmed in 3.2.5
1823087,2019-04-10 11:32:32 UTC,Just noticed from the original bug report:
1823087,2019-04-10 12:22:10 UTC,"@Jeff,
What is the purpose of your patch?"
1823087,2019-04-10 13:34:22 UTC,"@JP, there are two different solutions in the patch.  One replaces painted areas on board-open, the other only when zones are filled.  Both warn the user and allow them to cancel."
1823087,2019-04-10 13:47:14 UTC,"Judging by JP's statement, he favours no longer supporting existing segmented zones (ie: converting on file-open).  I'm now also in this camp.  @Wayne?"
1823087,2019-04-10 13:49:32 UTC,"@Jeff, my preference would be the latter.  If the user doesn't refill the zone, then no changes should be made to the zone filling.  If user is just opening the board to view it (unless you can no longer view boards with segment filled zones in which case that is different issue), forcing a refill on open doesn't make a lot of sense."
1823087,2019-04-10 14:08:44 UTC,"@Wayne, currently you can't plot a segment-filled zone.  I haven't been able to ascertain if that's just a recently-introduced bug, or something we simply don't support anymore."
1823087,2019-04-10 14:09:24 UTC,"(Just to be clear, segment-filled zones to display correctly today.  They just plot empty.)"
1823087,2019-04-10 14:09:46 UTC,^to^do
1823087,2019-04-10 15:08:15 UTC,"@Jeff, my preference would have been to leave the segment filled zone plotting alone since it was proven code and add the warning when plotting gerbers asking the user if they wanted to convert all segment filled zones to polygon filled zones.  Now that plotting segment filled zones has be removed, the problem is far more difficult and far less less user friendly.  How much trouble would it be to restore the segment filled zone plotting code?  I understand JP's concerns about sending segment filled zone plots to a board vendor but how serious of a problem is that really?  It seems like the cure was worse than the disease.  From the comments in this bug report there is a least one board vendor that still doesn't support polygon fills and requires segment filled zones so there are probably others.  Do we really want to force users either use an older version of KiCad or find a new board vendor?"
1823087,2019-04-10 16:12:24 UTC,There are 2 very different problems:
1823087,2019-04-10 16:24:45 UTC,"To be clear, the comment from #4 was the result of a mistranslation.  The board house actually wanted a grid fill rather than solid copper."
1823087,2019-04-10 16:42:52 UTC,"""a grid fill""
Do you mean a painted solid area or a hatched pattern?"
1823087,2019-04-10 16:46:44 UTC,"On 4/10/2019 12:12 PM, jean-pierre charras wrote:

> There are 2 very different problems:
>
> 1 - zone plotting works fine with painted zones.
> However the ZONE_FILLER has a bug: when the fill mode is SEGMENTS, in fact the filled polygons list is cleared but not recreated, so the list filled polygon list and the list of segments to fill the zone are empty.
> I just fixed that (it was a basic fix).
"
1823087,2019-04-10 16:49:53 UTC,"So the board house cannot handle solid fills.  That is significantly
different than the board house cannot handle polygon fills.  Even our
hatched filling uses polygons.  I hope we have this straight now ;)"
1823087,2019-04-10 16:57:02 UTC,"OK, so the plot bug is fixed (thanks JP!)."
1823087,2019-04-12 08:48:21 UTC,"@Wayne, can I commit plan (8) (comment #52)?  JP is on board (comment #53), and I'm pretty sure Seth is as well."
1823087,2019-04-11 06:36:23 UTC,"Yes, in ZFM_SEGMENTS, we need the polygons:
- to calculate the segment fill
- to plot the outlines of the solid area."
1823087,2019-04-09 22:19:26 UTC,Here's the two different implementation if anyone wants to check them out.
1823087,2019-04-12 13:58:57 UTC,"I'm not comfortable with the ""silent"" part.  I'm fine with forcing the user to convert segment filled zones to polygon filled zones.  The user should be warned that their boards will be irrevocably changed to polygon fills and that if they still need to use segment filled zones they will have to use an older version of KiCad.  There should also be an option to abort the file load if users do not want to accept the change.  Once the conversion to polygon is complete and the segment filling is blown away, I cannot think of any reason not to refill all zones."
1823087,2019-04-12 14:29:35 UTC,Will do.  (That's (6) then.)
1823087,2019-04-12 14:51:08 UTC,"Hi All-  This may be a good time to implement a larger ""These objects have been converted"" dialog rather than a single popup.  This will almost certainly not be the last time we convert objects from older files, so it might make sense to have the popup say something like"
1823087,2019-04-12 15:08:21 UTC,"I like Seth's plan, but for the next instance."
1823087,2019-04-12 19:20:23 UTC,"Fixed in revision dae41b7460464720c78a10215a64b9303fdee00f
https://git.launchpad.net/kicad/patch/?id=dae41b7460464720c78a10215a64b9303fdee00f"
1823087,2019-04-10 19:12:27 UTC,"@JP, I looked at your fix and zone filling and if I'm understanding this correctly we are creating both a polygon fill *and* a segment fill when the zone fill mode is ZFM_SEGMENTS.  What happens in this case when the gerbers are plotted?  Does it plot the polygon fill only, the segment fill only, or both?  If it only plots the polygon fill, is it really necessary to keep the segment fill information?"
1823087,2019-04-11 14:00:03 UTC,I did a trial rip-out of the segment support.  It's 635 lines of code spread over 43 files.  That's a non-trivial tax on development....
1823087,2019-04-11 13:55:27 UTC,"@JP, sorry but I have one more question.  Do the gal canvases render zones filled with segments correctly?"
1823087,2019-04-11 13:37:50 UTC,"Currently, if a zone fill type is ZFM_SEGMENT, the gerber uses these segments to fill the zone. It does not use solid polygon."
1823087,2019-04-11 13:36:33 UTC,"On 4/11/2019 9:02 AM, Wayne Stambaugh wrote:

> @JP, maybe I'm not seeing the answer in your repose to the question


                                            ^^ response ^^

> about plotting gerbers.  Are gerbers plotted with segments when the zone
> fill type is ZFM_SEGMENT?  In other words, if I opened an old board file
> with segment zone filling, would I still get the same gerber output or
> is the zone refilled with polygons and the gerbers plotted with the
> polygon fill?  If it's the latter, than Jeff's 8) suggestion makes
> sense.
>
"
1823087,2019-04-11 13:02:33 UTC,"@JP, maybe I'm not seeing the answer in your repose to the question about plotting gerbers.  Are gerbers plotted with segments when the zone fill type is ZFM_SEGMENT?  In other words, if I opened an old board file with segment zone filling, would I still get the same gerber output or is the zone refilled with polygons and the gerbers plotted with the polygon fill?  If it's the latter, than Jeff's 8) suggestion makes sense."
1823087,2019-04-11 10:41:37 UTC,I agree with 8)
1823087,2019-04-11 10:20:51 UTC,I'm sympathetic to JP's argument.  I'd now like to propose:
1823087,2019-04-11 13:58:50 UTC,Any time you edit a segment zone in 5.1 it will ask if you want to convert it.
1823087,2019-04-09 22:18:04 UTC,"It's not so much a question of the code difficulty, just the matter of bringing all of the various ZFM_SEGMENTS section up to date indefinitely into the future.  This means handling printing, plotting, sketch display, connectivity, view items, click selection, etc.  All of these are different for the segment fills.  If we allow segments past loading, doing half measures of only allowing plotting is asking for bug reports, I fear."
1823087,2019-04-11 15:03:02 UTC,"@Jeff,
Yes, I missed the prompt dialog when closing the zone dialog by OK in stable 5.10."
1823087,2019-04-09 19:06:49 UTC,"Don't we fill zones in a thread?  If so, putting up a dialog during refill would be a lot of work...."
1823087,2019-04-03 22:47:39 UTC,Yes.  This was removed on purpose.
1823087,2019-04-03 21:58:51 UTC,Yes i opened the board in version 5.1. There was no question about updating. I even added a second zone for the second net to test how this behaves. (The old zone stays as it was and the new one gets polygon fill.)
1823087,2019-04-03 21:43:37 UTC,Ok the original reporter updated their report. It seems their manufacturer can not deal with polygon fill so they would wish the option to use segmented fill.
1823087,2019-04-03 21:42:18 UTC,Did you try opening the board?  It should ask you if you want to update it.
1823087,2019-04-03 21:40:34 UTC,For reference this got originally reported on the forum: https://forum.kicad.info/t/where-is-the-fill-mode-option-in-kicad-5-1/16143
1823087,2019-04-03 21:28:17 UTC,For convenience here a board that has a GND zone set to segmented (created with v4.6 as i do not have a 5.0 available any more.)
1823087,2019-04-11 15:06:10 UTC,"The gal canvas of course render zones filled with segments correctly, it just does not use the extra data (paint segments) that are used only in plot files."
1823087,2019-04-04 14:58:55 UTC,"This now appears to be a request by the fab for a hatched fill, which 5.1 does not support"
1823087,2019-04-04 15:36:11 UTC,Back to the original topic:
1823087,2019-04-04 15:42:27 UTC,"@Rene-  Can you please post the 5.1 version information?  I just tested again and the gerber output I get from 5.1 does not look like yours.  Also, re-filling gives me the attached warning box."
1823087,2019-04-04 15:51:11 UTC,Seth i already have my version infos in #5
1823087,2019-04-04 15:56:34 UTC,That's the dialog I meant.  (I thought it came up at open rather than at fill.)
1823087,2019-04-04 15:57:00 UTC,Here also the project after i refilled and saved with version 5.1
1823087,2019-04-04 16:05:59 UTC,"@Jeff-  `git log -S ""legacy segment fill""` says it was removed in 7170720f3c when hatched zones were added.  Still exists in 5.1.x"
1823087,2019-04-04 16:10:18 UTC,I've updated the bug report to fix this issue.  Attached is an image of the gerber output in master at the moment with the test board Rene provided.
1823087,2019-04-09 21:43:43 UTC,"Zone filling is indeed threaded.  However, we unfill all zones first, so we'd have to check for segmented zones there anyway.  And the check-for-out-of-date stuff would need revision since a cancel would also have to affect that."
1823087,2019-04-04 16:37:39 UTC,I found out how to get the mentioned dialog regarding updating to polygon fill. (In my 5.1) I need to open the zone properties dialog and press ok. However this does not seem to do anything. As next time i open the zone properties i get asked the same question again. (And the file does not change with regards to the zone settings.)
1823087,2019-04-04 16:40:13 UTC,"@JP, did you remove the segment zone fill warning on purpose or was that an accident?  We definitely do not want to change the zone fill type of existing boards without warning the user."
1823087,2019-04-04 16:59:48 UTC,Maybe a question: should we split this up into multiple reports? One of them about the behavior of current nightlies. One of them for my strange 5.1 and one regarding if it is a good idea at all to remove this option completely.
1823087,2019-04-04 18:06:41 UTC,"@Wayne,"
1823087,2019-04-04 18:53:53 UTC,"@JP, I'm not suggesting we continue to support segment filled zones.  My concern is that warning dialog disappeared.  I'm surprised there are still board vendors out there who don't support polygon zone fills.  I would look for a new board vendor."
1823087,2019-04-04 19:34:32 UTC,"If the warning message is shown by the zone settings dialog, It was certainly lost when I replaced the old dialog by the new one."
1823087,2019-04-05 05:40:35 UTC,@jp-charras wrote:
1823087,2019-04-05 09:51:47 UTC,"The 5.1 version has a bug in zone settings dialog that prevent to convert filled by segment zones to filled by solid polygons.
I fixed it in 5.1.1."
1823087,2019-04-09 17:05:14 UTC,"JP has a good point: now that we need the Fill wxChoice, we might as well add segments to it.  I am going to make it conditional on the zone already having a segment fill, though, so it will only appear in the legacy case."
1823087,2019-04-09 17:37:56 UTC,@Jeff-  I have a preference to avoid the extra code if there isn't a driver for keeping segment fills.  The original report was a mistranslation.  Open and convert to polygon fills would allow us to eventually remove the ZFM_SEGMENTS sections.
1823087,2019-04-09 18:11:41 UTC,"@Jeff,"
1823087,2019-04-09 18:43:09 UTC,"So you guys are saying put the warning dialog back, but move it from Edit Zone to File Open?"
1823087,2019-04-09 18:55:03 UTC,"I would think any time refilling the zone will clobber the current zone segment filling would be the way to go.  If the user doesn't change the zone filling, I would think there would be no reason to warn the user."
1823087,2019-04-09 19:00:44 UTC,Wayne is right: this is the best and the most easy way.
1823087,2019-04-04 16:22:18 UTC,"With current nightly if i refill i do not see any fill in pcb_new on that layer.
The zone still keeps the mode segmented but the actual segments are removed from the file."
1823087,2019-04-09 19:05:09 UTC,@Wayne-
1823088,2019-04-04 16:21:20 UTC,"FYI charm-ceph is deprecated, and will not receive further patches (charm-ceph-mon and charm-ceph-osd are supported, and should be the focus for this)."
1823088,2019-04-03 21:53:09 UTC,To reproduce:
1823088,2019-04-03 22:23:24 UTC,"Agree, we should guard around this in the charm.  Thank you for the bug."
1823089,2019-04-03 22:21:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649752"
1823089,2020-02-19 06:47:02 UTC,"Reviewed:  https://review.opendev.org/649752
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=61ec305e33c54d2a8785a6409d2bb9459e1626c0
Submitter: Zuul
Branch:    master"
1823089,2020-03-23 17:25:57 UTC,This issue was fixed in the openstack/horizon 18.1.0 release.
1823091,2019-04-04 00:10:39 UTC,ee82b69af93c0803516035413a049cf087c08f1d
1823096,2019-04-04 04:53:02 UTC,Might this be a limit based on your account?
1823096,2019-04-04 05:06:34 UTC,I'm not aware of any limits on my account.
1823096,2019-06-04 04:17:20 UTC,[Expired for juju because there has been no activity for 60 days.]
1823098,2019-04-04 00:40:10 UTC,A hacky workaround is the constantly touch/update the timestamp of /etc/ntp.conf.
1823099,2019-07-09 04:17:30 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1823099,2019-04-26 18:45:24 UTC,Is this a duplicate of this one here:
1823099,2019-04-27 02:20:48 UTC,"On Fri, Apr 26, 2019 at 8:45 PM Scott Moser <email address hidden>
wrote:"
1823099,2019-04-27 01:37:29 UTC,"I suggest we attempt to use the 'hook-script' funtion that is available via
network-manager and dhclient. There is partial implementation in cloud-init
already in it's dhclient-hook. We should just extend that to support
network-manager."
1823099,2019-05-10 01:23:54 UTC,Not a duplicate of https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254
1823101,2019-06-21 15:25:45 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1823101,2019-06-21 13:47:53 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1823101,2019-06-21 15:23:44 UTC,This issue was fixed in the openstack/puppet-tripleo 8.5.0 release.
1823101,2019-04-10 22:48:50 UTC,"Reviewed:  https://review.openstack.org/647964
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=96de607edfc9552455bd6c3dff9e5244a221cf37
Submitter: Zuul
Branch:    stable/queens"
1823101,2019-04-04 17:23:07 UTC,"Reviewed:  https://review.openstack.org/647961
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=8851b8836bcd9ceca69d7398ecec427a50e75203
Submitter: Zuul
Branch:    stable/rocky"
1823101,2019-04-10 20:06:42 UTC,"Reviewed:  https://review.openstack.org/647963
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ecb01485cf8b72b33a6a747b4b1f10bf5e2bb332
Submitter: Zuul
Branch:    stable/rocky"
1823101,2019-06-21 13:45:51 UTC,This issue was fixed in the openstack/puppet-tripleo 9.5.0 release.
1823101,2019-04-04 17:23:17 UTC,"Reviewed:  https://review.openstack.org/647962
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=fbe6e4b1a01a9aae5bed6775fa8e1b01d9a9affc
Submitter: Zuul
Branch:    stable/queens"
1823102,2019-04-04 01:25:55 UTC,Marking as release gating; medium priority -- fields missing from stx-gui
1823102,2019-06-21 12:29:46 UTC,Assigned to Bruce for re-assignment.
1823102,2019-06-25 02:51:53 UTC,"Should have been fixed by https://review.opendev.org/664831
Please have a re-test."
1823104,2019-09-27 09:04:57 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1823104,2019-04-05 01:38:34 UTC,This issue was fixed in the openstack/nova 19.0.0.0rc2 release candidate.
1823104,2019-04-05 01:01:10 UTC,"Reviewed:  https://review.openstack.org/650043
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=afe5f0d4de6d30f119c89c2cfd1bdf0f7c5b3de9
Submitter: Zuul
Branch:    stable/stein"
1823104,2019-04-04 14:47:11 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650043"
1823104,2019-04-04 19:59:55 UTC,"Reviewed:  https://review.openstack.org/649775
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3301449e736af81fdbd96fd3f396dd01b02beaf2
Submitter: Zuul
Branch:    master"
1823104,2019-04-04 02:20:32 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649775"
1823104,2019-04-04 20:00:06 UTC,"Reviewed:  https://review.openstack.org/650020
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=88560094450bb4935909793965866b542d9ef3fe
Submitter: Zuul
Branch:    master"
1823104,2019-04-04 14:22:37 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/650020"
1823104,2019-04-04 13:34:15 UTC,"Thanks for spotting, it would be great to get this into stable/stein before release."
1823109,2019-04-04 02:54:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649791"
1823109,2019-06-04 06:00:02 UTC,"Reviewed:  https://review.opendev.org/649791
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d168e3f2f577b04e409a7c4afca53d1111d65851
Submitter: Zuul
Branch:    master"
1823109,2019-06-12 14:44:09 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1823113,2019-04-04 03:25:19 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/649806"
1823116,2019-04-04 05:00:10 UTC,This change was made by a bot.
1823116,2019-04-04 05:03:36 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1823122,2019-04-04 06:34:16 UTC,What the code said is that the following interaction:
1823123,2019-04-08 12:48:39 UTC,I'm not sure I follow what the problem is. Can you explain what you did and what output it generated?
1823126,2019-04-17 10:31:11 UTC,"Hello,
did you perform an update before this issue happened?"
1823126,2019-06-17 04:17:34 UTC,[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.]
1823127,2019-08-02 11:06:26 UTC,It's fixed the readme was added in both projects.
1823131,2019-04-05 22:14:07 UTC,"Finally, I'm down to only a single issue, and that's probably one of the only remaining problems I have in Stein:"
1823134,2019-05-20 07:28:41 UTC,fixed in 19.4 update
1823135,2019-04-04 09:47:11 UTC,Because after the install most people will have taken the CD-Rom out of the tray and you receive an error message that it is not available.  Maybe Bug is the wrong choice of wording.  Perhaps it Could/Would/Should be viewed as a bad default to leave it selected ?
1823135,2019-04-04 09:12:25 UTC,"Thank you for your bug report, why do you consider it as a bug to have the installation media source selected?"
1823135,2019-04-04 08:20:00 UTC,adding ubiquity as affected - apologies if not - reassign as appropriate.
1823137,2019-07-04 04:17:26 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1823137,2019-04-05 10:25:09 UTC,"Unfortunately there was a bug in the autosave code for Eeschema in 5.1, see https://bugs.launchpad.net/kicad/+bug/1820433"
1823137,2019-04-04 10:59:41 UTC,Disclaimer i am not a dev. Just active in the community.
1823137,2019-04-05 08:59:06 UTC,"Hi Rene,"
1823142,2019-04-04 08:50:57 UTC,"i have extracted this from larger code, and there is a typo in the above(because i had copied the validate call from another function where ""newtree"" was passed in as ""XMLtree""..."
1823142,2019-04-04 14:14:32 UTC,"simple examples attached.
testpass validates against Test Schema
testfail doesnt."
1823142,2019-07-27 18:27:27 UTC,"XML-Schema validation is implemented in libxml2, not in lxml."
1823143,2019-04-04 08:48:37 UTC,Traceback
1823145,2020-01-10 10:00:49 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/701923"
1823145,2020-01-24 18:49:05 UTC,"Reviewed:  https://review.opendev.org/701923
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=18d1cf6928ca276b0dab2f849aea293e3a8f42e7
Submitter: Zuul
Branch:    stable/rocky"
1823146,2019-06-04 04:17:30 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1823146,2019-04-04 14:26:49 UTC,"Hi,"
1823146,2019-04-04 10:24:14 UTC,"This seems to be an issue with network namespaces, which I assume may point to Linux. This report is about Ubuntu Kylin, a supported Ubuntu flavor."
1823146,2019-04-04 13:10:38 UTC,"Hi,"
1823146,2019-04-04 10:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823147,2019-04-04 12:28:04 UTC,Can you please attach the example board that shows this issue?
1823147,2019-04-06 14:48:14 UTC,"Same behaviour (version from git repository as of apr, 4). In the attached example it seems also that the pad changed its shape, not only dimensions."
1823147,2019-04-06 14:50:32 UTC,Also printing on pdf file generates the same behaviour. Attached the kicad_pcb file of the simpler example in the previous pdf.
1823147,2019-04-06 21:45:06 UTC,"Here is o of many PCB files with the same behaviour on mirrored printing.
Petr Sojka"
1823147,2019-05-06 09:33:52 UTC,"Fixed in revision 2e43c6c64e0bdf7a7c5897db2b7b53d0da31080e
https://git.launchpad.net/kicad/patch/?id=2e43c6c64e0bdf7a7c5897db2b7b53d0da31080e"
1823151,2020-01-06 13:36:26 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1053.57
1823151,2019-05-21 10:27:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823151,2019-05-21 09:56:01 UTC,"Still affected on Ubuntu Mate 18.04.02 64-bit.
Any fix or workaround out their?"
1823153,2019-10-29 23:36:01 UTC,"Hi,"
1823156,2019-04-09 06:43:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823160,2019-05-15 06:53:00 UTC,This bug was fixed in the package ubuntu-image - 1.7+19.10ubuntu1
1823161,2019-04-04 11:00:07 UTC,This change was made by a bot.
1823161,2019-04-04 13:02:55 UTC,"booting from
Linux raf-NG-A717-72G 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"
1823161,2019-04-05 11:23:06 UTC,Please try the kernels between 4.18.0-10 and 4.18.0-17 and find out the last good and first bad kernel.
1823161,2019-04-05 11:39:24 UTC,"Will try, but can take some days/weeks because other priorities for the
moment"
1823161,2019-04-07 14:21:50 UTC,fyi:
1823162,2019-04-04 20:01:47 UTC,"Great idea, I also find referencing external files annoying."
1823162,2019-04-05 07:50:55 UTC,"Thanks Thomasz,"
1823167,2019-05-30 10:34:18 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1823167,2019-09-02 09:08:53 UTC,"The verification of the Stable Release Update for tracker-miners has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823167,2019-09-02 09:08:49 UTC,This bug was fixed in the package tracker-miners - 2.1.6-1ubuntu1~19.04
1823167,2019-09-02 09:08:38 UTC,"Looking at the error tracker, the crash rate seems to have decreased indeed. Let's give it a try."
1823167,2019-08-30 05:38:57 UTC,"Note that the fix is a random crash fix. I didn't get the crash myself but upstream applied the fix upstream, which is supposed to remove the crash."
1823167,2019-08-29 19:29:10 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for disco for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1823167,2019-04-24 13:50:52 UTC,The fix has been merged upstream. I think it's worth SRUing it to disco because it's one of the most reported errors in errors.ubuntu.com. Tagging as rls-dd-incoming.
1823167,2019-05-30 10:33:41 UTC,"What I like in this bugfix upload is that most of the changes come with tests, so it certainly makes me feel a bit safer. But since the change involves rewriting of the tracker-extract quite significantly, I would like to request some normal-usage dogfooding of the package before switching the verification-done tag."
1823167,2019-05-29 09:05:36 UTC,This bug was fixed in the package tracker-miners - 2.1.6-1ubuntu1
1823167,2019-04-23 11:06:03 UTC,Fix proposed upstream: https://gitlab.gnome.org/GNOME/tracker-miners/merge_requests/60
1823170,2020-06-12 15:20:04 UTC,Just double checked this on my machine to verify this
1823170,2020-05-13 19:27:39 UTC,"This is an issue that I have with customer, and would like not to see this error. So would really like this merged if possible"
1823170,2020-06-12 14:57:45 UTC,"Actually this is not yet released. Current snap juju-lint is   latest/stable:    1.1.dev7+g9c9a145 2020-06-08 (17) 13MB classic
but that still doesn't have the mentioned fix merged."
1823176,2019-04-08 02:05:46 UTC,"^^^
To get that, run this command while the problem is happening:"
1823176,2019-04-05 11:00:46 UTC,Could you add your journalctl log when getting the issue?
1823176,2019-06-07 04:17:23 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1823176,2019-04-05 02:20:49 UTC,Thanks for the bug report.
1823180,2019-04-06 20:54:35 UTC,"@Jeff Young,"
1823180,2019-04-05 12:13:10 UTC,"If you had a large symbol and were zoomed in on a particular area and needed to edit that area in multiple units, and auto-zoom-to-fit might be very annoying."
1823180,2019-04-05 22:43:06 UTC,Discussion on developer mailing list: https://lists.launchpad.net/kicad-developers/msg40038.html
1823183,2019-09-25 10:27:59 UTC,Hello Björn !
1823183,2019-09-25 09:06:07 UTC,"I fixed a bug related to this, which was exactly what you described here, that the xyz.metal.example.com got an undeterministic IP. In fact, it would cycle through the list of possible IPs and point to one of them at a time."
1823183,2019-04-04 17:30:49 UTC,"Hi,
i am experincing the same behavior as Florian, the only difference is that i am using static IP to configure the interfaces before deploying them from juju. One thing i noticed is depending on which vlan or interface i configure first, it will be the first record created in the DNS domain, utlimatly the other records get created (bondx.x.host.domain).
But when i ping from host1 to host2 it is always the first record created that is returned by the DNS.
for example when i create my static assignements:
Host1 if i create in the following order:"
1823183,2019-04-04 14:07:16 UTC,"Hi Florian,"
1823183,2019-04-04 14:12:39 UTC,Hello Andres !
1823185,2021-02-02 14:59:05 UTC,I cannot confirm this issue in the 3.5 and 3.6 staff clients. Queue position is sorting numerically as it should. Marking Won't Fix.
1823188,2019-05-08 04:57:59 UTC,"@XueFeng Liu,"
1823188,2019-08-30 00:07:20 UTC,"Reviewed:  https://review.opendev.org/662677
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=85bf2626d99fe4f93fa8551ab30a4e58258ce82e
Submitter: Zuul
Branch:    master"
1823188,2019-09-27 17:04:03 UTC,This issue was fixed in the openstack/senlin 8.0.0.0rc1 release candidate.
1823191,2019-05-08 12:34:12 UTC,"(updated to indicate that the name is ""include-file"" and ""include-base64"" not ""include-file64"")"
1823191,2019-05-08 12:35:03 UTC,"I thought ""juju config"" supports @file syntax (juju config foo=@file), but probably --file foo.yaml does not."
1823192,2019-04-04 14:33:06 UTC,"Apparently the search function isn't great, but I found this in the nova admin docs:"
1823192,2019-04-04 14:48:48 UTC,Whatever happens here can point to the docs being worked in oslo.privsep https://review.openstack.org/#/c/649997/
1823193,2019-04-05 10:02:58 UTC,"Confirm. It works perfect.
I cant believe, so fast fix. Thank you, Raiman!"
1823193,2019-04-04 16:02:50 UTC,is fixed with the latest build 269
1823193,2019-04-04 14:53:24 UTC,"ok, I will check."
1823194,2019-04-04 14:50:11 UTC,"gvfs/bionic-updates,bionic-security,now 1.36.1-0ubuntu1.3 amd64 [installed]
cifs-utils/bionic,now 2:6.8-1 amd64 [installed]
mount/bionic-updates,now 2.31.1-0.4ubuntu3.3 amd64 [installed]"
1823194,2019-04-04 16:01:17 UTC,"Problem is not in gvfs.
I found that I am connected to the same network by the 1 Gigabit copper interface and by the wireless. When I used mount, traffic went through 1 Gbit copper, when I used gvfs, traffic went by Wireless (~100 Mbit).
Maybe is issue of the network manager?"
1823197,2020-04-28 17:28:46 UTC,"Fixes pushed to master and rel_3_5.  Thanks Dan, Jason, and Terran!"
1823197,2019-04-04 17:39:42 UTC,"Verified this it just prints the code for the Prefix and Suffix, not the actual text."
1823197,2020-03-16 17:11:55 UTC,"Daniel Pearl was working on this bug, among others, before he left CW MARS.  He left behind an omnibus branch that is intended to fix most of these issues.  I have had these bugs assigned to me since before his departure because it was my intention to clean his branch up, test it, and add any missing bits.  I have not had time to do this, so I am simply putting the branch out there in the hope that someone can test what's there during bug squashing week or whenever."
1823197,2020-04-27 21:25:43 UTC,This is fixed as part of the receipt omnibus patch. My signoff to that is at:
1823197,2020-04-28 15:22:08 UTC,"Terran was testing a server that also had applied the top commit here, which needs a signoff as well:"
1823198,2019-08-12 20:41:10 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1823198,2019-08-01 13:41:21 UTC,"Reviewed:  https://review.opendev.org/672384
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e9261764c90403d1b2e33790be96efea89068427
Submitter: Zuul
Branch:    stable/stein"
1823198,2019-07-23 22:50:02 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/672384"
1823198,2019-09-27 09:04:56 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1823198,2019-04-04 17:13:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650077"
1823198,2019-07-23 22:44:05 UTC,"Reviewed:  https://review.opendev.org/650077
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ade6c9393632e830c2368825568769853fce3b99
Submitter: Zuul
Branch:    master"
1823203,2019-08-12 20:42:08 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1823203,2019-04-04 16:46:31 UTC,"It should be relatively easy to recreate this in devstack by setting [quotas]/quota_port=1 in neutron.conf, create a server and then try to attach a new port to the server via the same network."
1823203,2019-04-04 18:25:01 UTC,Yup I was able to easily recreate this in devstack:
1823203,2019-04-04 18:49:58 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650097"
1823203,2019-06-14 22:08:05 UTC,"Reviewed:  https://review.opendev.org/650097
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8ff0fae42bce9f98fd5897888c3c4c739b4b5f45
Submitter: Zuul
Branch:    master"
1823203,2019-06-15 13:54:07 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/665513"
1823203,2019-06-28 19:17:49 UTC,"Reviewed:  https://review.opendev.org/665513
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=43926ebca0f9a7f59be96e965e5be70b84501fa3
Submitter: Zuul
Branch:    stable/stein"
1823203,2019-09-27 09:04:51 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1823206,2019-05-15 06:08:16 UTC,i'd suggest to check neutron server config and log to see if taas plugin is loaded
1823206,2019-07-15 04:17:17 UTC,[Expired for tap-as-a-service because there has been no activity for 60 days.]
1823207,2019-04-04 18:33:30 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650092"
1823207,2019-04-08 09:53:09 UTC,"Reviewed:  https://review.openstack.org/650092
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8795f591d541227cd704019f19f3a78c74fc8ac7
Submitter: Zuul
Branch:    master"
1823207,2019-04-08 15:35:19 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650929"
1823207,2019-04-13 04:51:04 UTC,"Reviewed:  https://review.openstack.org/650929
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fe5c8a517a74e344903131c283d676c5e06bb5e6
Submitter: Zuul
Branch:    stable/stein"
1823207,2019-06-06 06:24:31 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1823207,2019-09-27 09:04:54 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1823209,2019-04-05 03:26:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823210,2019-04-07 18:39:28 UTC,"Hi Jean-Max,
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1823210,2019-06-07 04:17:19 UTC,[Expired for mariadb-10.0 (Ubuntu) because there has been no activity for 60 days.]
1823212,2019-04-04 18:50:56 UTC,"Another test:
1. Started shutter on workspace1.
2. Moved the shutter to workspace2 (hit the win key, and then dragged the shutter window to workspace2).
3. switched to workspace2 (win+PgDn).
4. Take screenshot (hit the PrtScr key)."
1823212,2020-07-30 18:34:27 UTC,"Same repro steps for me on Ubuntu 18.04.2, shutter (from apt) 0.94 Rev 1290"
1823215,2019-09-18 16:27:52 UTC,"Reviewed:  https://review.opendev.org/681743
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8a9efe1cbdbf92261e2cb905ac519ee07bacaa0c
Submitter: Zuul
Branch:    stable/stein"
1823215,2019-09-12 13:28:37 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/681743"
1823215,2019-04-29 19:59:00 UTC,"Reviewed:  https://review.opendev.org/650155
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=78e04bbe2e0cdc197514770bf0d4be4b1f4f51b5
Submitter: Zuul
Branch:    master"
1823215,2019-04-04 21:59:33 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/650155"
1823215,2019-09-12 13:22:59 UTC,This was fixed with https://review.opendev.org/#/c/681540/ since I didn't remember we already had a bug for this.
1823251,2020-04-09 09:27:19 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/718629"
1823251,2020-12-17 15:17:40 UTC,Decreasing the scaling factor in https://github.com/openstack/nova/blob/master/nova/tests/unit/db/test_migrations.py#L101 makes the test to fail faster so I guess we just need to increase it and see if we are still in the time budget of the whole unit test run when on a slow node.
1823251,2020-12-17 16:55:05 UTC,My tests shows a 75% decrease of test runtime after the patches: https://review.opendev.org/q/topic:%22bp%252Fcompact-db-migrations-wallaby%22+(status:open%20OR%20status:merged)
1823251,2020-12-18 12:48:13 UTC,Increasing the timeout did not help so now I try to execute the db migration test in serial https://review.opendev.org/c/openstack/nova/+/767590
1823251,2021-01-07 13:21:24 UTC,"https://review.opendev.org/c/openstack/nova/+/767590 has been merged and it seems it does help, but does not fully remove the timeout. We need to merge  https://review.opendev.org/q/topic:%22bp%252Fcompact-db-migrations-wallaby%22+(status:open%20OR%20status:merged) to solve this"
1823251,2020-12-03 10:14:04 UTC,I'm trying another approach https://review.opendev.org/c/openstack/nova/+/765300
1823251,2020-05-22 16:36:58 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/682661"
1823251,2020-04-09 16:02:03 UTC,"Reviewed:  https://review.opendev.org/718629
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=316fef22c699a8dc5fc13ed8d779369043167874
Submitter: Zuul
Branch:    master"
1823251,2020-12-17 15:07:43 UTC,Finally I managed to reproduce the same issue locally.
1823251,2019-09-21 14:55:23 UTC,"Reviewed:  https://review.opendev.org/683011
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f261f98e19d28fa29ff6a4d62a6a3a8a4114575
Submitter: Zuul
Branch:    master"
1823251,2019-09-19 00:07:05 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/683011"
1823251,2019-04-04 20:05:59 UTC,This would also help to explain why we've been seeing a spike in unit test job timeouts for nova recently because these tests hit that thread switch and then timeout.
1823251,2019-04-04 20:14:18 UTC,"Since this is failing on more than just nova, I wonder if something more global changed on 4/1 that is causing this on limestone nodes."
1823251,2019-05-31 11:44:09 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/662434"
1823251,2019-06-22 01:31:33 UTC,"Reviewed:  https://review.opendev.org/662434
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=15b9e81d37d1adaf5a13be68d12c1544405488e3
Submitter: Zuul
Branch:    master"
1823251,2019-09-19 03:21:45 UTC,"Reviewed:  https://review.opendev.org/683009
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aebebe713a50d1057d5dfdfa4f13be6cc3ce625b
Submitter: Zuul
Branch:    master"
1823251,2020-12-14 16:55:07 UTC,https://review.opendev.org/c/openstack/nova/+/765300 has been abandoned
1823251,2019-09-18 23:58:45 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/683009"
1823251,2019-09-17 14:23:49 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/682661"
1823251,2019-08-22 16:08:30 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/678051"
1823255,2019-05-31 22:37:37 UTC,"Sorry, user/jeffdavis/lp1823255_signoff"
1823255,2019-04-04 20:27:41 UTC,Working branch user/jeffdavis/lp1823255_make_ident_value_required has a fix:
1823255,2019-05-22 01:40:54 UTC,"Hmm, noting that the submitted code was authored by Mark Bucholtz <email address hidden>, but is missing the Signed-off-by line for them.  We need to get his signoff on the commit properly, or get a DCO from Mark to allow the code to be used."
1823255,2019-09-06 22:03:34 UTC,"Pushed to master for inclusion in 3.4. Thanks, Mark and Jeff!"
1823255,2019-05-31 22:37:28 UTC,"Working branch user/mbucholtz/lp1823255_signoff has the same fix, but with Mark's signoff included."
1823258,2020-04-02 14:45:55 UTC,"Reviewed:  https://review.opendev.org/712182
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=34f6144a47e2594851db0321ecec9c890b6337b2
Submitter: Zuul
Branch:    master"
1823258,2020-02-04 22:21:59 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/705859"
1823258,2019-06-20 23:20:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666739"
1823258,2020-03-10 21:33:36 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/712182"
1823258,2019-08-09 03:27:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675509"
1823258,2019-09-14 01:06:07 UTC,"Reviewed:  https://review.opendev.org/666739
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a38d4a650f3573065848a372254c63c3a6598979
Submitter: Zuul
Branch:    master"
1823258,2019-09-14 01:10:32 UTC,"Reviewed:  https://review.opendev.org/675228
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a80d83e76dfb1114b8cd1b31bd2f175d36ae18ae
Submitter: Zuul
Branch:    master"
1823258,2019-09-14 16:19:03 UTC,"Reviewed:  https://review.opendev.org/675509
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5e06ec8163249a7581b12db321036979b7d0604c
Submitter: Zuul
Branch:    master"
1823258,2020-02-12 05:47:10 UTC,"Reviewed:  https://review.opendev.org/705859
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=da28046944aaa5b6068d2cc8f14e72ef1de6c012
Submitter: Zuul
Branch:    master"
1823258,2019-08-07 23:23:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675228"
1823259,2019-04-05 18:18:07 UTC,Could you please run:
1823259,2019-04-05 16:12:13 UTC,Please also attach /var/lib/grub/ucf/grub.previous.
1823259,2019-05-07 12:27:58 UTC,"That's OK, I appreciate you looking at it anyway.  I've since upgraded to Ubuntu 19.04, so I probably wouldn't be able to replicate it, either."
1823259,2019-05-07 11:45:26 UTC,I am still unable to reproduce this failure case. I don't know what else to try.
1823259,2019-04-10 18:32:53 UTC,Fantastic.  I wish I could give you more to work with.  Let me know if you think of anything.
1823259,2019-04-10 17:07:45 UTC,"Okay, I wonder if this could be because GRUB_CMDLINE_LINUX_DEFAULT was commented out earlier, and there's another entry with the value and we're maybe not catching this appropriately?"
1823259,2019-04-06 15:27:52 UTC,"I'll also include my apt history.  The issue started after the update on April 4, 08:38:07.  Be kind, I had no idea what was wrong, so I did a lot of silly stuff trying to fix it."
1823259,2019-04-05 16:10:51 UTC,"Reassigning this to the grub2 source package, which is the source for grub-common."
1823259,2019-04-06 15:15:29 UTC,"This is what my current grub file looks like (works).  It probably looks weird (nomodeset, but also modeset). Understand that I was struggling to get my system working, and forgot about the i915 bit I needed."
1823259,2019-04-06 15:11:38 UTC,"Here's the debconf.  Only the first command applies, as I'm not on an EFI system."
1823259,2019-04-06 15:09:56 UTC,Here's the /var/lib/grub/ucf/grub.previous
1823259,2019-04-06 15:07:42 UTC,I sincerely apologize if this ends up wasting people's time.
1823259,2019-04-06 15:18:06 UTC,"I also found this file hanging out in my /etc/default directory.  I don't recognize it.  it's dated July 24, 2018."
1823261,2019-04-05 02:23:28 UTC,It appears the kernel has stopped reporting any sound devices:
1823261,2019-04-05 02:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823261,2019-04-08 05:31:51 UTC,Please refer to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818275
1823261,2019-06-08 04:17:27 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1823263,2019-04-04 22:36:40 UTC,"Hi,"
1823264,2019-05-15 18:13:10 UTC,"Hi pekon, as I saw in your last bug report you want try to learn in documentation contribution? In this case, I would like to assign this bug to you. Let me know if you need more support or information."
1823264,2019-05-16 16:08:00 UTC,"The newton guide is unmaintained, we will not update it anymore."
1823265,2019-05-07 18:29:23 UTC,When using the CLI to compose a machine and specifying a hostname with an underscore the machine is assigned a random name. I would expect this to also return a message preventing the behaviour. Certainly seems like a backend issue.
1823265,2019-05-02 12:21:45 UTC,"That’s a possibility, that said, this issue is really a backend issue!"
1823265,2019-05-08 19:02:28 UTC,https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/367142
1823265,2019-04-22 13:17:38 UTC,The solution should that the backend needs to validate that hostnames never use underscores.
1823265,2019-05-02 10:37:10 UTC,"I think we should disable the ""Compose"" button, similarly to how the ""Save"" button is disabled upon entering an underscore, as otherwise the user can submit the invalid value and would then see an error."
1823268,2019-04-13 04:21:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823272,2019-04-20 06:33:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823272,2019-04-20 06:43:55 UTC,I've encountered the same problem. I received message for 'sgml-base' and 'linux-image-5.0.0-13-generic':
1823272,2019-05-10 12:12:33 UTC,"I have faced the same problem, not sure what's causing this."
1823279,2019-04-05 16:58:19 UTC,I'm curious what the HAProxy bug fix that you have identified is?
1823279,2019-04-05 17:16:34 UTC,https://bugs.launchpad.net/charm-haproxy/+bug/1818761
1823281,2019-04-05 04:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823282,2019-04-05 05:42:45 UTC,"I can optimise the 'reload' capabilities of the systemd units, however its not possible to use those as part of the debhelper generated systemd management code; using reload rather than restart appears to be an inflight feature in Debian:"
1823282,2019-09-07 20:25:11 UTC,This bug was fixed in the package openvswitch - 2.12.0~git20190903.1cdf291dc-0ubuntu1
1823285,2019-04-05 09:57:21 UTC,"It's difficult to see what you're saying, you should use words."
1823287,2019-04-12 00:40:51 UTC,"Reviewed:  https://review.openstack.org/650363
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=2ca1814a2b4d1e887974a71951b7e744273a43b4
Submitter: Zuul
Branch:    stable/stein"
1823287,2019-05-16 06:50:07 UTC,This issue was fixed in the openstack/python-novaclient 14.0.0 release.
1823287,2019-04-15 18:22:59 UTC,"Reviewed:  https://review.openstack.org/652033
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=efdbac35b0c00ca39b986b7fb58515e2b5059384
Submitter: Zuul
Branch:    stable/rocky"
1823287,2019-04-15 11:54:42 UTC,"Reviewed:  https://review.openstack.org/651925
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=60bf9a236dfbaa98e7d93b4baf0997e645b02bb0
Submitter: Zuul
Branch:    stable/stein"
1823287,2019-04-12 10:28:19 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/652033"
1823287,2019-11-12 11:35:16 UTC,This issue was fixed in the openstack/python-novaclient 11.0.1 release.
1823287,2019-04-11 20:49:29 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/651925"
1823287,2019-06-13 10:25:35 UTC,This issue was fixed in the openstack/python-novaclient 13.0.1 release.
1823287,2019-04-11 16:06:25 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/651827"
1823287,2019-04-11 20:14:37 UTC,"Reviewed:  https://review.openstack.org/651827
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=e8f7aaf9091330bbb046f2bd42dc9c92f1dcebaa
Submitter: Zuul
Branch:    master"
1823287,2019-04-05 06:54:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650235"
1823287,2019-04-05 15:36:06 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/650363"
1823287,2019-04-15 18:22:48 UTC,"Reviewed:  https://review.openstack.org/650364
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=488dd9940a88c33a5061bde5636e6338602a3a57
Submitter: Zuul
Branch:    stable/rocky"
1823287,2019-04-05 15:36:20 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650364"
1823287,2019-04-05 22:56:44 UTC,"Reviewed:  https://review.openstack.org/650235
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=a9b1125f7ba209887cac36b3c0900cffe2516fa8
Submitter: Zuul
Branch:    master"
1823291,2019-04-05 07:35:10 UTC,I'm marking this a Low - it needs fixing but the preferred key manager is vaultlocker which works fine.
1823294,2019-04-05 07:44:45 UTC,https://review.openstack.org/#/c/648522/ introduced the KeyError
1823294,2019-04-08 00:50:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650599"
1823294,2019-04-08 18:01:00 UTC,"Reviewed:  https://review.openstack.org/650599
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c760a83a5d9111e48333e1aff5f6dd043cb9e68f
Submitter: Zuul
Branch:    master"
1823294,2019-04-08 23:03:37 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/651021"
1823294,2019-04-10 20:24:07 UTC,"Reviewed:  https://review.openstack.org/651021
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0ce7f6e1b625f50756b821c7067940f2aee0930d
Submitter: Zuul
Branch:    stable/stein"
1823294,2019-04-16 17:56:05 UTC,This issue was fixed in the openstack/neutron 14.0.1 release.
1823294,2019-09-19 10:14:40 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1823295,2021-01-13 17:08:14 UTC,This bug was fixed in the package openvswitch - 2.9.7-0ubuntu0.18.04.2
1823295,2021-01-08 14:54:23 UTC,I believe the autopkgtest failure is now resolved.
1823295,2021-01-07 22:57:03 UTC,"All autopkgtests for the newly accepted openvswitch (2.9.7-0ubuntu0.18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1823295,2021-01-07 18:44:46 UTC,"Hello James, or anyone else affected,"
1823295,2021-01-06 15:19:52 UTC,"This is currently in the unapproved queue for bionic and paired with a few other SRUs.
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=openvswitch"
1823295,2021-01-08 15:25:03 UTC,Verified successfully on bionic-proposed.
1823295,2020-05-28 06:51:54 UTC,2.9.6 was released several months ago - will pick that up for SRU with this change.
1823295,2020-02-12 14:59:27 UTC,"I've committed this fix to the git repo for OVN for bionic, however there is no point in uploading it without another fix or point release as its related to package upgrade."
1823295,2019-04-12 17:34:43 UTC,This bug was fixed in the package openvswitch - 2.11.0-0ubuntu2
1823295,2021-01-05 15:59:50 UTC,Dropping field-high designation as this is pending another SRU. No point in releasing this until a functional change against the openvswitch package for bionic is needed.
1823296,2020-03-04 09:39:14 UTC,"GCC 8.4.0 has been released, adjusting target milestone."
1823296,2019-04-08 07:29:26 UTC,The ICE is much older that GCC-8:
1823296,2019-04-07 10:50:52 UTC,"The preprocessed source is included.
gcc -c test.ii
../test.cpp: In function ‘void test_shape_creator()’:
../test.cpp:19:18: internal compiler error: Ошибка сегментирования
  blaspp<1> v({14});
                  ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions."
1823296,2019-04-06 10:10:55 UTC,"$ g++-7 -c test.ii
test.ii:18:21: error: parameter '<anonymous>' includes reference to array of unknown bound 'const long int []'
   b(const long (&)[]);
                     ^
test.ii:23: confused by earlier errors, bailing out"
1823296,2019-04-06 10:10:24 UTC,"works on the gcc-7 branch and the trunk, ICEs on the gcc-8-branch."
1823296,2019-04-08 07:27:20 UTC,It's rejected on trunk since r268606.
1823296,2019-04-06 04:40:16 UTC,The file is included from blaspp.h
1823296,2019-04-06 10:09:33 UTC,"$ cat test.ii
template <int, int, bool, class> class a;
namespace b {
template <typename, unsigned long, long, unsigned long, typename...> class b;
template <unsigned long, typename> struct c;
template <typename l, unsigned long d, unsigned long dim, typename... curshape>
struct c<d, b<l, dim, 0, dim, curshape...>> {
  using e = typename c<d - 1, b<l, dim, 0, dim, a<0, 1, true, void>>>::e;
};
template <typename l, unsigned long dim, typename... curshape>
struct c<0, b<l, dim, 0, dim, curshape...>> {
  using e = b<l, dim, 0, dim, curshape...>;
};
template <typename l, unsigned long f,
          template <int, int, bool, typename> class baseclass, int g, int h,
          typename i, typename... j>
class b<l, f, 0, f, baseclass<g, h, true, i>, j...> {
  b(long);
  b(const long (&)[]);
};
} // namespace b
template <long dim, typename l = double>
using blaspp = typename b::c<dim, b::b<l, dim, 0, dim>>::e;
blaspp<1> k({4})"
1823296,2019-04-06 04:13:50 UTC,please attach the preprocessed source
1823296,2019-04-06 04:38:58 UTC,"The main header. The problem line numbers are 768-770.
The variadic constructor along with the constructor from plane array causes an error.
Removing one of them helps to compile successfully."
1823296,2019-04-06 04:32:11 UTC,The main file. The 19-th line causes error.
1823299,2019-04-05 08:49:09 UTC,Which version of Ubuntu are you using?
1823299,2019-04-08 14:40:02 UTC,It happens on 18.04 and 18.10.
1823299,2019-10-29 17:19:32 UTC,Telegram-desktop (as currently in Ubuntu 18.04) is now showing popups telling the user that their software is out of date and that they should upgrade.
1823299,2019-10-30 21:17:28 UTC,That popup message is coming with updateServiceNotification from Telegram backend.
1823299,2019-10-30 21:17:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823299,2019-04-17 04:01:36 UTC,"These Ubuntu series have already been released and have frozen repositories, no new versions will be uploaded there. But you can try to use my PPA with backports of the telegram-desktop package and those related to it."
1823301,2019-04-07 17:34:49 UTC,"So after upgrading, I cannot see any abnormal rise in memory consumption. I'm glad I risked it and upgraded. I do not use zsh and am using the latest stable kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ and the latest available nvidia driver from https://launchpad.net/~graphics-drivers."
1823301,2019-04-08 07:40:06 UTC,"Actually, your comment that:"
1823301,2019-08-10 00:36:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823301,2019-04-08 07:33:05 UTC,"Sorry, I still can't reproduce this bug. I am using Nvidia 390.116 on disco with nvidia-drm.modeset=1. Actually, that combination instead just makes Xorg crash for me (bug 1822616)."
1823301,2019-04-08 06:37:39 UTC,Thanks. Driver version 390 is one thing I haven't tried this week.
1823301,2019-04-08 06:28:02 UTC,"here is the output (reenabled drm to get it back):
$ glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1050/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 390.116
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 390.116
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.116
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
$ xrandr
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP-1-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080     60.02*+  60.01    59.97    59.96    59.93
   1680x1050     59.95    59.88
   1600x1024     60.17
   1400x1050     59.98
   1600x900      59.99    59.94    59.95    59.82
   1280x1024     60.02
   1440x900      59.89
   1400x900      59.96    59.88
   1280x960      60.00
   1440x810      60.00    59.97
   1368x768      59.88    59.85
   1360x768      59.80    59.96
   1280x800      59.99    59.97    59.81    59.91
   1152x864      60.00
   1280x720      60.00    59.99    59.86    59.74
   1024x768      60.04    60.00
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   800x512       60.17
   700x525       59.98
   800x450       59.95    59.82
   640x512       60.02
   720x450       59.89
   700x450       59.96    59.88
   640x480       60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   680x384       59.80    59.96
   640x400       59.88    59.98
   576x432       60.06
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 160mm x 90mm
   1920x1080     60.00*+  60.00    50.00    59.94
   1920x1080i    60.00    60.00    50.00    50.00    59.94
   1600x1200     60.00
   1680x1050     59.88
   1280x1024     75.02    60.02
   1440x900      74.98    59.90
   1280x960      60.00
   1280x800      59.91
   1152x864      75.00
   1280x720      60.00    60.00    50.00    50.00    59.94
   1024x768      75.03    70.07    60.00
   832x624       74.55
   800x600       72.19    75.00    60.32    56.25
   720..."
1823301,2019-04-08 02:07:12 UTC,"Dylan,"
1823301,2019-04-07 09:04:41 UTC,"Dylan,"
1823301,2019-04-06 06:09:45 UTC,Would I encounter this bug if I upgrade to disco?
1823301,2019-04-07 09:03:05 UTC,"didrocks,"
1823301,2019-04-05 09:07:45 UTC,"00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
01:00.0 VGA compatible controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1)"
1823301,2020-01-24 08:58:03 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1823301,2019-04-05 10:02:39 UTC,Didier:
1823301,2019-04-05 11:18:29 UTC,"-> I'm using 2 monitors (1 internal and 1 external).
-> The nvidia GPU is enabled, monitor is plugged to it through HDMI.
-> The CPU usage of GNOME Shell spikes. There is no writed at the same time (the led doesn't blink) and no other process seems to run for it. The memory usages seems stable though. See log attachement which is a snapshot of CPU and MEM usage every second (you can see at the end a freeze for multiple seconds corresponding to GNOME Shell CPU spike). CPU spike can go up to 200%.
-> I've run a wayland session for a period of time and didn't notice any issues. So seems Xorg specific."
1823305,2019-06-13 10:32:27 UTC,https://review.opendev.org/#/c/649689/
1823305,2019-09-13 15:06:12 UTC,This issue was fixed in the openstack/puppet-tripleo 8.5.1 release.
1823305,2019-09-12 09:31:35 UTC,This issue was fixed in the openstack/puppet-tripleo 9.5.1 release.
1823305,2019-07-26 18:13:14 UTC,This issue was fixed in the openstack/puppet-tripleo 11.1.0 release.
1823305,2019-06-20 16:45:57 UTC,"Reviewed:  https://review.opendev.org/666401
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=a00b779cd30afb03656f6ceea0cc11d2c2e50faa
Submitter: Zuul
Branch:    stable/queens"
1823305,2019-07-05 12:49:47 UTC,This issue was fixed in the openstack/puppet-tripleo 10.5.0 release.
1823305,2019-06-19 16:17:45 UTC,"Reviewed:  https://review.opendev.org/666153
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=76101c8971f8e66e59bf43ce636a09029a080a6d
Submitter: Zuul
Branch:    stable/rocky"
1823305,2019-06-18 19:43:08 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/666153"
1823305,2019-06-18 14:03:00 UTC,"Reviewed:  https://review.opendev.org/665473
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=af8b1cfbf78e87840b1d6200974069b2a2d38051
Submitter: Zuul
Branch:    stable/stein"
1823305,2019-06-14 20:51:23 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/665473"
1823305,2019-06-14 19:41:05 UTC,"Reviewed:  https://review.opendev.org/649689
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=610c8d8d41cd4b6bfd228ce1012416e424db625d
Submitter: Zuul
Branch:    master"
1823305,2019-06-19 17:02:45 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/666401"
1823307,2020-01-07 08:51:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823309,2020-05-27 09:25:40 UTC,"I think the fixes in
https://review.opendev.org/#/q/topic:bug/1874235+(status:open+OR+status:merged) may resolve the situation?  Note that the config item ""libvirt-migration-network"" is very much deprecated and only for systems that are using spaces: the ""migration"" space is the preferred way of doing things."
1823309,2020-02-07 01:20:20 UTC,"This config item is found on nova_compute_context.py, ""ctxt['live_migration_uri'] = 'qemu+ssh://%s/system'""."
1823309,2019-10-28 14:11:15 UTC,"Hi Mathias,
the only workaround i am using now it to manage hosts files on each compude node. Apparenttly there is a fix that shoudl address this in MAAS in 2.7 https://bugs.launchpad.net/maas/+bug/1823183
Regards"
1823309,2019-10-25 17:57:00 UTC,Any news here? Livemigration works only if i set the correct addresses in /etc/hosts on all compute-notes
1823309,2019-06-07 21:47:16 UTC,I have to correct: I did not make it work with my workaround suggestion. Unfortunately it does not work.
1823309,2019-05-13 11:51:33 UTC,I have also recently observed this change in how MAAS host addressing works. I'm not sure what the best solution will be to fix this issue is but there is definitely work to be done.
1823309,2019-05-15 20:13:21 UTC,I have the same problem and maybe I have a workaround:
1823313,2019-06-15 04:17:32 UTC,[Expired for apache2 (Ubuntu) because there has been no activity for 60 days.]
1823313,2019-04-15 12:02:52 UTC,"I tried to reproduce this by installing 2.4.18-2ubuntu3.9 in a container and then upgrading up to 2.4.18-2ubuntu3.10, but it restarted after upgrade correctly."
1823313,2019-04-08 11:26:30 UTC,"FYI hints on the config issue:
https://unix.stackexchange.com/questions/154811/apache-2-4-wont-reload-any-problem-with-my-configuration/
https://unix.stackexchange.com/questions/155150/where-in-apache-2-do-you-set-the-servername-directive-globally"
1823313,2019-04-09 13:59:43 UTC,"Hello,"
1823313,2019-04-05 12:38:59 UTC,"# journalctl -u apache2
-- Logs begin at Fri 2019-03-29 14:29:08 UTC, end at Fri 2019-04-05 12:34:50 UTC. --
[...]
Apr 04 06:25:04 0616675e8cc176244 systemd[1]: Reloading LSB: Apache2 web server.
Apr 04 06:25:04 0616675e8cc176244 apache2[15672]:  * Reloading Apache httpd web server apache2
Apr 04 06:25:04 0616675e8cc176244 apache2[15672]:  *
Apr 04 06:25:04 0616675e8cc176244 systemd[1]: Reloaded LSB: Apache2 web server.
Apr 05 06:25:04 0616675e8cc176244 systemd[1]: Reloading LSB: Apache2 web server.
Apr 05 06:25:04 0616675e8cc176244 apache2[20161]:  * Reloading Apache httpd web server apache2
Apr 05 06:25:04 0616675e8cc176244 apache2[20161]:  *
Apr 05 06:25:04 0616675e8cc176244 systemd[1]: Reloaded LSB: Apache2 web server.
Apr 05 06:33:34 0616675e8cc176244 systemd[1]: Stopping LSB: Apache2 web server...
Apr 05 06:33:34 0616675e8cc176244 apache2[20777]:  * Stopping Apache httpd web server apache2
Apr 05 06:33:35 0616675e8cc176244 apache2[20777]:  *
Apr 05 06:33:35 0616675e8cc176244 systemd[1]: Stopped LSB: Apache2 web server.
Apr 05 10:09:54 0616675e8cc176244 systemd[1]: Starting LSB: Apache2 web server...
Apr 05 10:09:54 0616675e8cc176244 apache2[22929]:  * Starting Apache httpd web server apache2
Apr 05 10:09:54 0616675e8cc176244 apache2[22929]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
Apr 05 10:09:55 0616675e8cc176244 apache2[22929]:  *
Apr 05 10:09:55 0616675e8cc176244 systemd[1]: Started LSB: Apache2 web server."
1823313,2019-04-05 12:25:55 UTC,"Sorry, wrong machine; here is the correct file:
# grep -i apache /var/log/syslog
Apr  5 06:33:34 0616675e8cc176244 systemd[1]: Stopping LSB: Apache2 web server...
Apr  5 06:33:34 0616675e8cc176244 apache2[20777]:  * Stopping Apache httpd web server apache2
Apr  5 06:33:35 0616675e8cc176244 apache2[20777]:  *
Apr  5 06:33:35 0616675e8cc176244 systemd[1]: Stopped LSB: Apache2 web server.
Apr  5 10:09:54 0616675e8cc176244 systemd[1]: Starting LSB: Apache2 web server...
Apr  5 10:09:54 0616675e8cc176244 apache2[22929]:  * Starting Apache httpd web server apache2
Apr  5 10:09:54 0616675e8cc176244 apache2[22929]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
Apr  5 10:09:55 0616675e8cc176244 apache2[22929]:  *
Apr  5 10:09:55 0616675e8cc176244 systemd[1]: Started LSB: Apache2 web server."
1823313,2019-04-05 11:54:14 UTC,Here is the result :
1823313,2019-04-05 11:28:07 UTC,"That's odd. Could you please also paste the result of ""grep apache /var/log/syslog""? Thanks."
1823313,2019-04-08 11:25:03 UTC,"Hi,
thanks for the log
This seems interesting at first
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message"
1823314,2019-04-16 09:56:04 UTC,"Reviewed:  https://review.openstack.org/651986
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=72c9a7ef8416f894a85a36c6b5bbf995e48599d1
Submitter: Zuul
Branch:    stable/queens"
1823314,2019-04-18 17:33:06 UTC,"Reviewed:  https://review.openstack.org/651987
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7f7dee73248b561bdefb289573990e8455a666c4
Submitter: Zuul
Branch:    stable/pike"
1823314,2019-04-17 01:54:49 UTC,"Reviewed:  https://review.openstack.org/651988
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4a45e1adebee9a72b6e8a36c5fd88a1380f81cb2
Submitter: Zuul
Branch:    stable/ocata"
1823314,2019-04-16 22:24:06 UTC,"Reviewed:  https://review.openstack.org/651983
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2aa200bdb994a72e8159f78c4439b81232436942
Submitter: Zuul
Branch:    stable/stein"
1823314,2019-04-15 22:09:59 UTC,"Reviewed:  https://review.openstack.org/651984
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ee2ed681c495c4fc5086d761853731b7dc2fd34f
Submitter: Zuul
Branch:    stable/rocky"
1823314,2019-04-17 10:49:41 UTC,I think that I know what is going on there.
1823314,2019-04-12 07:07:50 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/651987"
1823314,2019-04-12 07:02:40 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/651986"
1823314,2019-04-12 06:58:01 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/651984"
1823314,2019-04-12 06:57:46 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/651983"
1823314,2019-04-12 05:48:05 UTC,"Reviewed:  https://review.openstack.org/651495
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a8d0f557d504957aeb91f451105cca9eee2d6adb
Submitter: Zuul
Branch:    master"
1823314,2019-04-10 10:57:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/651495"
1823314,2019-04-12 07:08:32 UTC,"Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/651988"
1823315,2019-04-11 17:04:44 UTC,"ii  linux-generic-hwe-18.04-edge                 5.0.0.8.66                                   amd64        Complete Generic Linux kernel and headers
ii  linux-headers-5.0.0-8                        5.0.0-8.9~18.04.1                            all          Header files related to Linux kernel version 5.0.0
ii  linux-headers-5.0.0-8-generic                5.0.0-8.9~18.04.1                            amd64        Linux kernel headers for version 5.0.0 on 64 bit x86 SMP
ii  linux-headers-generic-hwe-18.04-edge         5.0.0.8.66                                   amd64        Generic Linux kernel headers
ii  linux-image-5.0.0-8-generic                  5.0.0-8.9~18.04.1                            amd64        Signed kernel image generic
ii  linux-image-generic-hwe-18.04-edge           5.0.0.8.66                                   amd64        Generic Linux kernel image
rc  linux-image-unsigned-5.0.0-050000-generic    5.0.0-050000.201903032031                    amd64        Linux kernel image for version 5.0.0 on 64 bit x86 SMP
rc  linux-image-unsigned-5.0.0-050000rc6-generic 5.0.0-050000rc6.201902102330                 amd64        Linux kernel image for version 5.0.0 on 64 bit x86 SMP
rc  linux-modules-5.0.0-050000-generic           5.0.0-050000.201903032031                    amd64        Linux kernel extra modules for version 5.0.0 on 64 bit x86 SMP
rc  linux-modules-5.0.0-050000rc6-generic        5.0.0-050000rc6.201902102330                 amd64        Linux kernel extra modules for version 5.0.0 on 64 bit x86 SMP
ii  linux-modules-5.0.0-8-generic                5.0.0-8.9~18.04.1                            amd64        Linux kernel extra modules for version 5.0.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.0.0-8-generic          5.0.0-8.9~18.04.1                            amd64        Linux kernel extra modules for version 5.0.0 on 64 bit x86 SMP"
1823318,2019-06-05 04:17:20 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1823318,2019-04-05 11:25:19 UTC,"Please can you test using 5.1.0, as the 5.0.0 series is no longer supported."
1823321,2019-04-05 11:41:57 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650265"
1823321,2019-05-14 20:44:14 UTC,"Reviewed:  https://review.opendev.org/650265
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=8b8158ed8f2f448a214ce3b1978b9cb5b039f6ed
Submitter: Zuul
Branch:    master"
1823322,2019-07-02 04:17:30 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1823322,2019-04-05 14:28:17 UTC,"Thank you for the report. This doesn't look like an Ubuntu-specific bug at a first glance, would you mind filing an upstream bug report at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and sharing the link to it here?
Thanks in advance!"
1823324,2019-04-05 20:02:14 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/650430"
1823324,2019-04-17 21:11:22 UTC,"Reviewed:  https://review.openstack.org/650430
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=3cadefbbc123e7f793b3b7f666e6107d75425cba
Submitter: Zuul
Branch:    stable/rocky"
1823324,2019-05-09 15:36:45 UTC,This issue was fixed in the openstack/cinder 13.0.5 release.
1823327,2019-04-05 12:05:28 UTC,For reference: https://github.com/CanonicalLtd/multipass/issues/715
1823327,2019-04-23 16:08:30 UTC,This bug was fixed in the package console-setup - 1.191ubuntu3
1823327,2019-04-05 15:55:10 UTC,"/etc/default/console-setup has:
ACTIVE_CONSOLES=""/dev/tty[1-6]""
and /usr/share/initramfs-tools/scripts/init-top/console_setup iterates over these active consoles."
1823328,2019-04-05 12:27:35 UTC,"org.mozilla.jss.ssl.SSLSocketException: SSL_VersionRangeSetDefault() for variant=0 with min=768 max=770 out of range (769:772): 0: (0) Unknown error
 at org.mozilla.jss.ssl.SSLSocket.setSSLVersionRangeDefault(Native Method)
 at org.mozilla.jss.ssl.SSLSocket.setSSLVersionRangeDefault(SSLSocket.java:1398)
 at com.netscape.management.client.comm.HttpsChannel.open(Unknown Source)
 at com.netscape.management.client.comm.CommManager.send(Unknown Source)
 at com.netscape.management.client.comm.CommManager.send(Unknown Source)
 at com.netscape.management.client.comm.HttpManager.post(Unknown Source)
 at com.netscape.management.client.util.AdmTask.exec(Unknown Source)
 at com.netscape.management.admserv.AdminServer.getServerStatus(Unknown Source)
 at com.netscape.management.client.topology.AbstractServerObject$StatusThread.run(Unknown Source)
org.mozilla.jss.ssl.SSLSocketException: SSL_VersionRangeSetDefault() for variant=0 with min=768 max=770 out of range (769:772): 0: (0) Unknown error"
1823328,2019-04-05 12:29:47 UTC,update Console Framework from 1.1.14 1.1.14 solved the problem.
1823328,2019-04-05 13:44:18 UTC,..to 1.1.17
1823328,2019-04-05 13:49:53 UTC,"cosmic and up has 1.2.0, so marking it fixed for other than bionic"
1823331,2019-04-05 12:50:38 UTC,"This makes sense to me, so we need to expose the stonith-action configuration option via charm config. I think the maas stonith plugin should also be updated to mark a node as broken in maas (with a comment if possible) if a node shutdown is requested."
1823332,2019-05-13 10:28:18 UTC,This bug was fixed in the package salt - 2017.7.4+dfsg1-1ubuntu18.04.1
1823332,2019-05-13 10:18:19 UTC,"The verification of the Stable Release Update for salt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823332,2019-05-03 23:49:07 UTC,"Hello Dimitri, or anyone else affected,"
1823332,2019-05-07 14:57:02 UTC,"# dpkg-query -W libssl1.1 salt-master
libssl1.1:amd64	1.1.1-1ubuntu2.1~18.04.1
salt-master	2017.7.4+dfsg1-1ubuntu18.04.1"
1823332,2019-04-25 09:54:53 UTC,Hello.
1823332,2019-04-25 23:54:14 UTC,https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=salt
1823335,2019-04-23 22:00:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823335,2019-05-02 13:17:36 UTC,Same here :( Right after updating to Ubuntu 19.04. Reinstalling Peek doesn't resolve this problem.
1823335,2019-05-02 13:20:49 UTC,Problem appears when recording GIF and APNG only.
1823335,2019-05-07 10:13:43 UTC,"Same here:
Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-13-generic
OS Type: 64-bit"
1823335,2020-02-18 17:58:45 UTC,"The fix is released since peek 1.3.1-6, which exists in Ubuntu 19.10 and 20.04. For users of Ubuntu 19.04: Ubuntu 19.04 is now End-Of-Life thus no longer supported. Please upgrade your system as soon as possible."
1823335,2019-04-12 14:40:49 UTC,Am facing the same issue
1823336,2019-04-05 17:46:29 UTC,"Unsure it's really a bug, mouse wheel scrolling is supposed to scroll on sliders and it's always a chance that you end up over a slider depending of the UI/screen size parameters"
1823336,2019-04-08 02:12:41 UTC,"IMHO, the mouse wheel shouldn't apply to horizontal sliders at all. It's too unintuitive, contentious about what the correct direction is (for Natural Scrolling), and a needless attempt at helping the user to avoid clicking and dragging. Plus, obviously, it causes this bug."
1823337,2019-06-30 04:17:40 UTC,[Expired for juju because there has been no activity for 60 days.]
1823337,2019-04-10 07:24:09 UTC,"I'd probably start by saying that fan networking is pretty much designed to
not be accessible outside of the local subnet. So if you want remotely
accessible services, then fan networking is not how you should be setting
up the applications. Part of the security benefit is that you know they
aren't accessible.
It would be possible to do something like put a load balancer in front
(HAProxy running on the host machine).
It is unclear to me why fan networking is a better solution for your case
than using the host's IP space in the first place. MAAS has no problems
handing out IP addresses to the containers we provision. It seems a bit of
a contradiction to put things into an unroutable space and then ask for
routes to it."
1823337,2019-04-30 16:16:14 UTC,On clouds by default juju use fan networking which causes all containers on fan network which breaks the log consolidation through Nagios. As Nagios uses public ip of container to access the units and it fails to contact as it is in different model.
1823337,2019-04-08 12:23:53 UTC,If the containers need addresses on a specific space to be contactable from other services during deployment the spaces requirements need to be specified using the bind configuration. Is there a sample of this behavior/bundle that defines the applicable network requirements for the topology you describe here?
1823338,2019-04-05 15:11:30 UTC,OpenSRF branch with the debug log line removed instead of commented is working/user/jmerriam/LP1823338: https://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/jmerriam/LP1823338
1823338,2019-04-05 18:39:54 UTC,We might have a way to remove this delay without removing the log line. I would say hold off on merging this until we see what comes of that. It involves changes to the logger that allow delayed exec subroutines in addition to strings for the $msg. If that pans out I will push a new branch that uses that method instead of just removing it.
1823338,2019-04-10 16:10:30 UTC,********
1823338,2019-06-07 15:09:33 UTC,"I prefer the alternative approach and am going to include it in today's release, so I'll close this bug."
1823338,2019-06-07 15:09:59 UTC,"Actually, I'll mark it as a duplicate."
1823339,2019-04-05 15:33:03 UTC,I tried to run app Port collect and it did not work
1823339,2020-04-15 21:32:33 UTC,Please attach debug logs from simple scanner.
1823339,2020-06-15 04:17:36 UTC,[Expired for simple-scan (Ubuntu) because there has been no activity for 60 days.]
1823341,2019-04-05 14:11:44 UTC,"--- server.py.orig      2019-04-05 14:10:49.653614025 +0000
+++ server.py   2019-04-05 14:11:09.589792248 +0000
@@ -110,6 +110,7 @@
         uuid = data.decode('ascii')
         LOG.debug(""<< %s VM-VC-UUID %s"", peer, uuid)
         uuid = uuid.replace(' ', '')
+        uuid = uuid.replace('-', '')
         self.sock_to_uuid[socket] = uuid"
1823341,2021-02-05 06:43:27 UTC,This has been fixed with https://opendev.org/x/vmware-vspc/commit/7ce7ead127390f50ddceaaf393bd71e392b765f0
1823343,2019-10-08 09:36:09 UTC,"Thanks for reporting this, and sorry for the delay in getting back to you."
1823346,2019-04-13 17:08:34 UTC,"This may be a regression introduced by this commit:
commit 20bd1d026aacc5399464f8328f305985c493cde3
Author: Jeremy Cline <email address hidden>
Date:   Tue Mar 6 21:47:32 2018 +0000"
1823346,2019-04-05 17:39:18 UTC,"it's more likely a kernel issue, reassigning"
1823346,2019-04-05 18:00:06 UTC,This change was made by a bot.
1823346,2019-04-07 09:13:06 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc3 kernel [0]."
1823346,2019-04-09 16:11:10 UTC,"Sorry, trying to follow your instructions, but some competency problems here:"
1823346,2019-04-11 05:42:11 UTC,"Did this ever happen to kernel v4.4, which is kernel for 16.04?"
1823346,2019-04-12 18:12:51 UTC,"I'm sorry, I don't know.  I don't use the card lock often at all."
1823346,2019-04-13 17:07:51 UTC,Please see if this issue doesn't happen on kernel version < Ubuntu-4.15.0-33.36.
1823348,2020-08-22 11:48:47 UTC,This was fixed in https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commit/0429e584d58be5af0da4eede4ea20cd7ca8fc597 and released in for MariaDB 10.3 in 1:10.3.22-1 (and a duplicate of #1612647)
1823348,2019-04-09 17:14:47 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1823348,2019-08-20 19:56:52 UTC,"Hi Jorge, unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1823350,2019-10-25 20:17:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823351,2019-04-25 16:57:41 UTC,"I will accept this, but could you make sure that the documentation for bionic won't have to be modified anywhere? Can you send an e-mail to the ubuntu-doc team as a heads up? Thanks!"
1823351,2019-04-25 16:59:05 UTC,"Hello Andrea, or anyone else affected,"
1823351,2019-05-24 11:16:06 UTC,"Hello Andrea, or anyone else affected,"
1823351,2019-06-05 14:53:47 UTC,"Using 3.192.1.7 on bionic with GNOME, the notification has a button at the bottom, clicking on it correctly open software-properties on the livepatch page"
1823351,2019-06-05 20:33:09 UTC,This bug was fixed in the package update-notifier - 3.192.1.7
1823351,2019-06-05 20:34:01 UTC,"The verification of the Stable Release Update for update-notifier has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823354,2019-04-05 17:36:48 UTC,Thank you for your bug report. Could you make a screenshot showing the issue? What printer do you use and how is it connected to the system?
1823354,2019-06-05 04:17:25 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1823355,2019-08-01 04:17:22 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1823355,2019-04-06 16:27:34 UTC,@zhqsoft- Does the crash also happen if you are running KiCad in English?  Or is it only when running in Chinese language?
1823355,2019-04-06 14:27:06 UTC,I cannot duplicate this on windows using the master branch so either this is specific to 5.1.0 or there is some specific sequence of operations that causes this.
1823355,2019-04-06 11:59:32 UTC,Me neither.  MSW-specific?
1823355,2019-04-05 15:28:46 UTC,Cant seem to reproduce on macOS using 5.1 or current master.
1823361,2019-07-31 10:51:26 UTC,Same on Ubuntu 18.04.
1823361,2019-08-07 14:38:06 UTC,"Quick and dirty test: I copied <email address hidden> from the upstream official build (thunderbird-60.8.0.tar.bz2) to /usr/lib/thunderbird/distribution/extensions/, and this was enough for thunderbird to pick it up and successfully use it."
1823361,2019-10-02 09:56:47 UTC,This bug was fixed in the package thunderbird - 1:68.1.1+build1-0ubuntu1
1823363,2019-04-25 20:16:37 UTC,Thank you for thanking me and letting me know! It's greatly appreciated.
1823363,2019-05-05 03:25:16 UTC,"The design of activity manager is to log otherwise hidden automated/background functions, so they can be ""seen"".  Manually initiated commands don't fit that category of event."
1823363,2019-04-15 15:49:32 UTC,"User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/73.0.3683.86 Chrome/73.0.3683.86 Safari/537.36"
1823363,2019-04-25 13:14:52 UTC,Thanks Paul for the upstream report!
1823363,2019-04-08 09:26:16 UTC,"This sounds like an upstream missing feature / bug. Would you mind filing it at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CThunderbird, and sharing the link here?"
1823363,2019-04-15 15:48:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823364,2019-04-05 15:24:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823366,2019-04-05 15:48:32 UTC,"This error appeared twice while /tmp/ubuntu-release-upgrader-ksrznuoq/disco was upgrading my system. It popped up scary-looking errors about the package. I wasn't scared, though."
1823366,2020-09-27 07:05:49 UTC,"Hello, I know this is an old bug report, but it sounds like it was resolved (you probably encountered https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1763690 )."
1823366,2020-11-27 04:17:18 UTC,[Expired for mpd (Ubuntu) because there has been no activity for 60 days.]
1823367,2019-08-01 18:42:37 UTC,"Merged the latest to master, including a follow-up that undoes the renaming of the eg.cat.transfer_target_vol local storage key to avoid a regression in the interaction between the AngularJS item status page and the Angular holdings view."
1823367,2019-05-29 21:36:08 UTC,"+1 to documenting style guidelines for the Angular Client.  Those guidelines might be more impactful if they live on the wiki (https://wiki.evergreen-ils.org/doku.php?id=dev:angular_dev_best_practices), where they'd be more discoverable and easily understandable to folks who don't use Asciidoc.  If they make more sense in the code, though, we should add links between the two documents.  Thoughts?"
1823367,2019-05-29 22:23:18 UTC,"My thinking on adding the doc here is mainly as a convenient and shared place for ideas to gel a bit.  I agree that the wiki would be the best eventual home, but I also don't want to add to the heap of half-baked pages on there (I've already added enough of those over the years)."
1823367,2019-05-29 22:29:44 UTC,"On another note, and I meant to raise this before the horse got out of the barn, but I failed.  This code adds a lot of new references to ""volume"" (and variations thereof) where I think, for clarity with UI decisions, we should use ""call number"" (and variations thereof).  I am going to create a branch in that direction, but please chime in if it sounds like a bad idea.  I would just rather deal with it now, before a lot of activity starts building on this, and not suffer through code/interface terminology mismatch for another entire generation of the Evergreen code."
1823367,2019-07-17 16:41:42 UTC,"I have rebased my working branch to master and pushed an additional commit to address Dan's concerns about the use of ""Volume"" instead of ""Call Number""."
1823367,2019-07-18 19:59:09 UTC,"Okay, new branch posted here:"
1823367,2019-07-18 17:29:19 UTC,Grabbing this to finish up the terminology changes...
1823367,2019-07-18 19:27:45 UTC,And beware my branch (user/berick/lp1823367-ang-catalog-post-3.3-omnibus-continued) has a couple of additional fix commits besides the Call Number patch.
1823367,2019-07-18 21:43:21 UTC,"+1 to ""Call Number"" label and internal migration."
1823367,2019-05-29 20:50:03 UTC,"Thanks, Dan!"
1823367,2019-07-18 17:00:19 UTC,"Dan's new color scheme is great, and so is its documentation.  I pushed those four commits to master and rel_3_3."
1823367,2019-05-29 19:39:01 UTC,"Okay, pushed everything so far to master and rel_3_3.  Thanks, Bill!"
1823367,2019-04-05 16:07:27 UTC,https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1823367-ang-catalog-post-3.3-omnibus
1823367,2019-05-28 15:21:49 UTC,I have rebased the working combo branch to current master.  I also pushed a commit to make the ident query default to ISBN searching (the first entry in the selector) as an improvement over having no value selected.
1823367,2019-05-27 17:37:46 UTC,A note that there are two things in this branch that would also be really handy for the Booking Refresh:
1823367,2019-05-24 20:39:17 UTC,"Thanks for the input, Jane.  Dan and I had a similar discussion at the conference.  I think he may be experimenting some with the colors..."
1823367,2019-05-24 18:39:57 UTC,"The Holdings View treegrid looks fantastic, and I think a lot of people will be happy to have it.  There are a few readability issues with the color scheme, though -- the dark blue text on dark blue background is particularly hard to make out."
1823367,2019-04-19 14:18:02 UTC,">
> Oddly enough, they use a lot of examples like (verb), and as a commenter
> pointed out, they specifically say to not use onVerb for output
> properties in the Angular style guide:
>
> https://angular.io/guide/styleguide#dont-prefix-output-properties
"
1823367,2019-04-18 21:18:15 UTC,I wondered if something like that might be the reason.  Bummer.
1823367,2019-04-18 20:30:25 UTC,"Thanks, Dan!"
1823367,2019-04-18 18:43:33 UTC,"Hello Bill,"
1823367,2019-04-05 16:16:49 UTC,The catalog work includes various general-purpose additions as well:
1823367,2019-05-28 16:11:38 UTC,"I have tested all but the first few commits, and I do have an alternative color scheme to propose.  Since Bill no longer has this claimed, I am going to grab it to signoff on what is there and post a possible color change."
1823369,2020-02-08 22:40:02 UTC,"@Jacolex, maybe you can test out Tetsuro's fix and see if it resolves your issue:"
1823369,2019-04-05 16:23:21 UTC,"Also, force_hosts/force_nodes could be accidentally persisted in this case as well:"
1823369,2019-04-05 16:29:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650376"
1823369,2019-04-24 01:14:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655278"
1823369,2019-12-11 18:49:16 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/650376
Reason: I'm no longer working on this."
1823369,2020-02-07 11:18:52 UTC,"Hello
I think I experienced this bug. I have the instance, which bahovior is very strange during resize. When the rezising occurs, nova scheduler returns all hosts from all availability zones (including downed hosts) and during the instance is migrating to another availability zone.
I spent 3 days to investigate the issue. Finally I found that the instance has different thing in request_specs table:
... ""scheduler_hints"": {""_nova_check_type"": [""rebuild""]}, ..."
1823370,2019-11-14 01:10:43 UTC,"Reviewed:  https://review.opendev.org/650429
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=95df2a239c32f2ee5d00f06a59a9e91b59f3aca5
Submitter: Zuul
Branch:    master"
1823370,2019-08-20 18:06:18 UTC,"Reviewed:  https://review.opendev.org/650424
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a7bd9688d533aaa622d6049a99d9339d1fbfa88f
Submitter: Zuul
Branch:    master"
1823370,2019-04-05 19:57:39 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650429"
1823370,2019-04-05 19:18:18 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/650424"
1823370,2019-04-05 16:18:46 UTC,I likely need to write a functional test to recreate this first to see how things fail.
1823372,2019-04-05 18:53:58 UTC,Do you think each Pod/Machine which accesses virsh needs its own public/private key pair or can one be used for everything? What I'm thinking is MAAS could generate its own public/private key pair which is synchronized across all regions and racks. When you configure a Pod or Machine to use virsh you could still use a password or leave the field blank and MASS's key pair would be used. This would require MAAS's public key to be manually added to virsh hosts if MAAS didn't deploy them.
1823372,2019-04-05 19:18:43 UTC,"I *think* one would suffice (but perhaps I'm insufficiently paranoid). Rather than ""every node for itself"", I think the appropriate paranoid behavior would be one per ROLE. But I'd defer to someone from the Canonical security group putting a stake in the ground (since the folks with ROLE other than admin shouldn't have visibility to the other machines, they shouldn't have the ability to power cycle them .. but my concern would be they could extract the key they have authority for and misuse it outside of MAAS) ... so one per ROLE (with admin's public key being everywhere ;>) should provide adequate paranoid protection."
1823374,2019-04-05 19:38:25 UTC,How long is locale generating taking for you and how did you time it? I just tested commissioning a virsh machine. From clicking commission to commissioning being finished it took me 144s. That includes 60s for the LLDP script to run.
1823374,2019-04-05 20:49:17 UTC,While it may well be other things which are slowing things up (and running the simulations on aged hw doesn't help performance ;>) the locales seemed like low hanging fruit. The start to finish time has been in the order of 10minutes or so per machine. Not immediately obvious what a good way to get a breakdown of where the time is being spent.
1823374,2019-04-05 20:53:29 UTC,"In case it is of interest, here's the lshw output on the machine hosting the VMs in question."
1823374,2019-06-05 04:17:31 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1823375,2019-08-23 17:49:18 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1823375,2019-11-25 21:03:56 UTC,"Tested on a Build with train, issue NOT reproduced"
1823375,2019-09-16 12:47:08 UTC,one more thing: the testing was done on 2.0 release candidate image.
1823375,2019-09-16 12:44:30 UTC,"after running reboot-active-controller test for over 20 times, K8S pods still kept running normally.
See the attachments (screen shots)"
1823375,2019-08-23 21:46:24 UTC,"I will run another round stress test with RC branch. If it is still functional correctly, I will close this issue, based on the rationale the recent enhancement patches of ""application-apply"" or ""-reapply"" take good effect."
1823375,2020-06-27 18:14:24 UTC,LP was verified a long time ago; removing the stx.retestneeded label
1823375,2019-08-07 04:26:18 UTC,"with recent build 0802 cengn build, the same test was performed with 27+ reboots on both controllers and the system worked well. See the attachments."
1823375,2019-04-05 18:57:46 UTC,"Marking as release gating; serious issue, but not seen frequently. Needs further investigation as it's a robustness issue."
1823375,2019-07-22 15:39:32 UTC,"With 0718 Cengn build, I tried the test (brutally restarting active controller) over 15 times on multi-nodes (2+2), this issue was NOT seen once. And the re-starting process for the pods also makes sense:
step #1: terminating the pod which is running on the rebooted active controller. In the test, it was pod keystone-api-5db97d877d-9zkbk.
step #2: generating another pod and putting it pending, here it was pod keystone-api-5db97d877d-7v6nd"
1823375,2019-07-08 17:33:29 UTC,"Yong - as I said in the description, the problem only happened in about 10% of active controller reboots. I have not been testing this recently, so I don't know if the problem still occurs. I suggest that you configure a 2+2 system and then attempt to reproduce this yourself."
1823375,2019-07-08 17:05:43 UTC,"The issue was observed from an old dev-build:
 - BUILD_HOST=""yow-bwensley-lx-vm2""
 - BUILD_DATE=""2019-03-20 08:05:38 -0500"""
1823375,2019-06-21 12:26:59 UTC,Assigned to Bruce for re-assignment.
1823375,2019-07-22 22:33:48 UTC,"keep running over 30 times, and 2 controllers run steadily with expected correct behavior, on BUILD_ID=""20190718T013000Z"""
1823378,2019-04-05 19:24:38 UTC,Hi there!
1823386,2019-09-12 07:48:12 UTC,Bionic has:
1823386,2019-09-12 07:47:18 UTC,Cosmic is past EOL
1823386,2019-09-12 07:46:47 UTC,Disco carries:
1823386,2019-09-12 07:49:21 UTC,"Ubuntu Eoan (19.10) has moved to php7.3, however it had a sufficiently updated php7.2 already:"
1823386,2019-04-17 18:57:09 UTC,"CVE-2019-11034
CVE-2019-11035"
1823386,2019-04-08 11:29:44 UTC,@security (now subscribed) are you on that already?
1823386,2019-09-12 07:45:11 UTC,Ubuntu eoan (19.10) now carries php 7.3.8
1823387,2019-04-05 18:11:07 UTC,Working branch user/jeffdavis/lp1823387-booking-url-double-slash-apache has a potential fix:
1823387,2019-04-15 23:40:23 UTC,"Nice job tracking down this issue, Jeff and Jeff.  This fix works for me; signoff branch here: user/sandbergja/lp1823387-booking-url-double-slash-apache"
1823387,2019-04-29 14:32:08 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks, Jeff, Jeff, and Jane!"
1823388,2019-09-25 08:07:17 UTC,"Thanks for your report. I agree that MAAS should be a bit smarter here. I would say this is a bug, considering that MAAS shouldn't be allowed to overload a system without any way of preventing it."
1823391,2019-07-16 21:42:47 UTC,This bug was fixed in the package grub2 - 2.04-1ubuntu1
1823391,2019-06-05 19:50:06 UTC,"I'm currently working on this. It's unclear, after brief testing on AWS, what the impact of grub-initrd-fallback.service is (even when re-ordering it's start); but the changes are done and I'll include them with the grub2 merge."
1823393,2019-04-05 19:29:42 UTC,Commits pushed:
1823393,2019-05-23 16:52:47 UTC,I've pushed a signoff branch to
1823393,2019-05-23 17:07:05 UTC,"Thanks, Galen.  I reviewed and tested your additions.  Signoffs for the new commits pushed:"
1823393,2019-05-24 18:00:22 UTC,"This interface looks great and works well.  Thanks, Bill and Galen!  Pushed to master so that it can be included in 3.4."
1823395,2019-05-22 13:33:57 UTC,report can re-open it if the issue can be reproduced in the latest ISO
1823395,2019-05-20 05:29:44 UTC,"Hi Peng, could you help check the issue again? Thanks."
1823395,2019-05-27 14:01:24 UTC,Not saw this issue recently
1823395,2019-04-23 00:16:07 UTC,"Hi Peng,
There is ima.log in my system. I cannot reproduce the issue with 20190418T013000Z image. Please help have a try with latest build for this issue. Thanks."
1823395,2019-05-08 13:01:51 UTC,"@peng, please retest it and see if you can repro."
1823395,2019-04-22 02:04:09 UTC,"I try it in VM environment with extended security configuration. Is it ok?
Thanks."
1823395,2019-04-22 02:02:16 UTC,"Hi Peng,
Issue cannot be reproduced with 20190418T013000Z image. Could you help double check the issue with latest build? Thanks."
1823395,2019-04-08 17:09:39 UTC,Marking as release gating; requires further investigation. The last time this was tested was before the merge of CentOS 7.6; unclear if it's related to that.
1823395,2019-04-22 20:16:32 UTC,"Yes.
And make sure your system has ima enabled.
[wrsroot@controller-0 log(keystone_admin)]$ ls /var/log/ | grep ima
ima.log"
1823398,2019-05-23 16:58:08 UTC,"I've created multiple disco Google GCE instances of type N1_Standard_2 and checked how much time setvtrgb.service took using ""systemd-analyze blame | grep setvtrgb"" and while there was some variance I never saw a result greater 500ms. Given that this isn't a significant amount of time I'm going to close this bug as Invalid."
1823401,2019-08-04 06:25:32 UTC,"HI,"
1823401,2019-10-04 04:17:21 UTC,[Expired for rpl (Ubuntu) because there has been no activity for 60 days.]
1823405,2019-04-05 20:54:56 UTC,"StacktraceTop:
 gtk_tree_model_get_valist (tree_model=tree_model@entry=0x55b69f8a84c0, iter=iter@entry=0x7ffd7935b4f0, var_args=var_args@entry=0x7ffd7935b3d0) at ../../../../gtk/gtktreemodel.c:1800
 gtk_tree_model_get (tree_model=0x55b69f8a84c0, iter=iter@entry=0x7ffd7935b4f0) at ../../../../gtk/gtktreemodel.c:1762
 baobab_window_open_item (self=self@entry=0x55b69f228450, iter=iter@entry=0x7ffd7935b580) at ../src/baobab-window.vala:375
 __lambda17_ (self=0x55b69f228450) at ../src/baobab-window.vala:432
 ___lambda17__gtk_menu_item_activate (_sender=<optimized out>, self=0x55b69f228450) at ../src/baobab-window.vala:428"
1823405,2019-04-05 23:18:23 UTC,https://gitlab.gnome.org/GNOME/baobab/issues/20
1823406,2019-04-05 21:01:19 UTC,"Further to this, I get the same error loading any activity, including ones that loaded successfully before."
1823406,2019-04-06 12:36:38 UTC,"You have an environment sky file that is in dds format instead of in ace format.
Either you locate and replace it or you uncheck the experimental option ""MSTS Environments"". Pls. report about the result."
1823406,2019-04-06 16:45:09 UTC,"yes, turning off MSTS Environments allows it to load.  What I don't know is how that even got turned on :)"
1823406,2020-12-18 21:00:00 UTC,"I get the same error, I was told by Jason at Trainsimulations, this was caused by my graphic card.
I also sent a bug report to Open Rails. i ran tests on other routes, had no problem.
Thank You Happy Holidays,
Jim"
1823408,2019-09-18 07:35:56 UTC,"Fixed by https://github.com/charmed-kubernetes/cdk-addons/pull/145, which was PR'd for bug 1841729."
1823409,2019-04-09 14:54:18 UTC,"usually when we have seen this before there was some issue before that, or a network issue. From above the compute can not reach the keystone endpoint:"
1823412,2019-04-11 02:32:14 UTC,"""horizon"" project does not provide magnum support. Are you filing a bug against magnum-ui?"
1823412,2019-06-10 04:17:43 UTC,[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]
1823414,2019-04-23 14:30:17 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1823414,2019-06-23 04:18:23 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1823416,2019-04-07 04:25:26 UTC,"BTW the associated bug was closed by upstream presumptuously but there is a linked pull request that actually seeks to fix the issue. Specifically:
https://github.com/lxqt/lxqt-session/pull/256"
1823422,2019-04-08 07:18:44 UTC,"same test failure in cosmic:
https://launchpadlibrarian.net/418305085/buildlog_ubuntu-cosmic-amd64.heimdal_7.5.0+dfsg-2_BUILDING.txt.gz"
1823422,2019-04-08 23:58:36 UTC,"Hmm, also ugly:"
1823422,2019-05-16 14:03:10 UTC,"hi there,"
1823422,2019-05-16 14:20:12 UTC,"The upstream issue links to a commit that fixes it:
https://github.com/quanah/heimdal/commit/e3cd069e5c40b455541508b81ffeb0563e882aed"
1823427,2019-06-18 12:55:53 UTC,same in eoan
1823429,2019-07-03 13:46:09 UTC,linux_4.15.0-54.58.dsc -> cannot be built on eoan. and failed very quckily.
1823429,2019-08-22 16:17:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1823429,2019-07-22 20:35:40 UTC,This bug was fixed in the package linux-oracle - 4.15.0-1018.20
1823429,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1823429,2019-11-14 04:38:37 UTC,"Patch available in Focal, mark this as Fix released."
1823429,2019-07-03 13:06:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1823429,2019-06-06 13:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823429,2019-06-04 21:41:45 UTC,It's up to the kernel team to manage kernel bugs.
1823429,2019-06-04 20:29:28 UTC,"This is difficult because security/selinux/ doesn't use the *actual* kernel headers for the kernel being built to get the AF_MAX/PF_MAX defines; those are not included in the kernel uapi headers.  Instead, those defines come from /usr/include/x86_64-linux-gnu/bits/socket.h which is provided by:
$ dpkg -S bits/socket.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/bits/socket.h"
1823429,2019-06-04 20:13:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823429,2019-06-04 20:12:55 UTC,"the same 4.15 kernel is getting built on b/c/d/e, and scripts/selinux/genheaders/genheaders.c includes the local header files, specifically <sys/socket.h>:
#include <sys/socket.h>
which define PF_MAX (via AF_MAX) as 45 for cosmic and later.  however genheaders.c also:
#include ""classmap.h""
which is security/selinux/include/classmap.h and that does:
#if PF_MAX > 44
#error New address family defined, please update secclass_map.
#endif"
1823429,2019-04-08 07:29:48 UTC,"also in cosmic:
https://launchpadlibrarian.net/418308401/buildlog_ubuntu-cosmic-amd64.linux-oracle_4.15.0-1009.11_BUILDING.txt.gz"
1823429,2019-06-04 22:02:43 UTC,"> Are you linux-oracle maintainer?
"
1823431,2019-09-12 18:08:11 UTC,same in eoan
1823434,2019-06-07 09:00:54 UTC,This bug was fixed in the package pkg-config - 0.29.1-0ubuntu3
1823436,2019-04-08 08:07:38 UTC,"also ftbfs in cosmic:
https://launchpadlibrarian.net/418304788/buildlog_ubuntu-cosmic-amd64.sg3-utils_1.42-2ubuntu1_BUILDING.txt.gz"
1823436,2019-04-27 21:53:02 UTC,This bug was fixed in the package sg3-utils - 1.42-2ubuntu2
1823436,2019-04-29 12:46:11 UTC,"I'll leave the cosmic task alone for now. If there is a need for an SRU for another reason, then this bug will be hit, found, and fix is here ready for being grabbed."
1823441,2020-01-13 17:44:00 UTC,This bug was fixed in the package xen - 4.9.2-0ubuntu6
1823441,2020-01-20 16:49:58 UTC,This bug was fixed in the package xen - 4.9.2-0ubuntu5
1823441,2020-01-20 16:50:18 UTC,"The verification of the Stable Release Update for xen has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823441,2020-01-23 14:00:32 UTC,"We don't specifically prevent such mal-ordered releases, we prefer to not do them, but as long as someone has taken responsibility for ensuring they are released we allow such things.  I have now released it in eoan as well."
1823441,2020-01-23 13:21:44 UTC,This bug was fixed in the package xen - 4.9.2-0ubuntu5
1823441,2020-01-07 10:29:32 UTC,"Hello Matthias, or anyone else affected,"
1823441,2020-01-21 20:57:05 UTC,The disco sru was released before eoan's?
1823441,2020-01-07 09:52:03 UTC,"An upload of xen to disco-proposed has been rejected from the upload queue for the following reason: ""cruft in the package (d/changelog.orig), and could use -0ubuntu3 as the version""."
1823441,2019-08-19 14:15:42 UTC,I'm also getting other building errors such as:
1823441,2019-07-23 21:31:00 UTC,"Looks like it built locally for me with this patch when I had gcc8 installed, but in the ppa it's defaulting to gcc9 for some reason, and fails to build."
1823441,2019-07-19 01:05:42 UTC,"Branches with the packaging changes:
    ~bryce/ubuntu/+source/xen:xen-sru-1823441-disco
    ~bryce/ubuntu/+source/xen:xen-sru-1823441-eoan"
1823441,2019-07-18 17:58:40 UTC,Dropping cosmic task since cosmic reached end of support this month.
1823441,2019-06-19 19:30:09 UTC,Looks like this is fixed upstream with commit 27751d89248c8c5eef6d8b56eb8f7d2084145080.
1823441,2019-06-18 12:41:44 UTC,also ftbfs in eoan
1823441,2019-04-08 08:17:06 UTC,"also ftbfs in cosmic:
https://launchpadlibrarian.net/418304930/buildlog_ubuntu-cosmic-amd64.xen_4.9.2-0ubuntu2_BUILDING.txt.gz"
1823441,2019-12-13 10:18:19 UTC,"the SRU upload was targeted for disco, while the changelog says it's about eoan.. and the version is bumped to -0ubuntu4 skipping 3 -> rejected"
1823444,2019-05-03 23:03:45 UTC,"Hello Mitsuya, or anyone else affected,"
1823444,2019-04-22 07:53:32 UTC,This bug was fixed in the package mozc - 2.23.2815.102+dfsg-4ubuntu1
1823444,2019-04-22 16:55:39 UTC,Sponsored to Xenial.
1823444,2019-04-25 17:53:03 UTC,"> Sponsored to Eoan, Disco, Cosmic, and Bionic.
> Sponsored to Xenial.
"
1823444,2019-05-03 23:02:51 UTC,"Hello Mitsuya, or anyone else affected,"
1823444,2019-05-03 23:04:50 UTC,"Hello Mitsuya, or anyone else affected,"
1823444,2019-05-03 23:06:18 UTC,"Hello Mitsuya, or anyone else affected,"
1823444,2019-05-04 12:47:45 UTC,I verified fixed in disco.
1823444,2019-05-04 12:48:51 UTC,I verified fixed in xenial.
1823444,2019-05-04 12:48:30 UTC,I verified fixed in bionic.
1823444,2019-04-21 16:52:21 UTC,"On 2019-04-21 18:05, Simon Quigley wrote:

> Sponsored to Eoan, Disco, Cosmic, and Bionic.
"
1823444,2019-05-13 08:38:31 UTC,This bug was fixed in the package mozc - 2.23.2815.102+dfsg-2ubuntu1.0.19.04.1
1823444,2019-05-13 08:38:37 UTC,"The verification of the Stable Release Update for mozc has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823444,2019-05-13 08:54:58 UTC,This bug was fixed in the package mozc - 2.23.2815.102+dfsg-2ubuntu0.18.10.1
1823444,2019-05-13 10:18:32 UTC,This bug was fixed in the package mozc - 2.20.2673.102+dfsg-2ubuntu0.18.04.1
1823444,2019-05-13 10:46:05 UTC,This bug was fixed in the package mozc - 2.17.2116.102+gitfd0f5b34+dfsg-1ubuntu1.2
1823444,2019-05-04 12:48:10 UTC,I verified fixed in cosmic.
1823444,2019-04-21 16:05:12 UTC,"Sponsored to Eoan, Disco, Cosmic, and Bionic."
1823444,2019-04-22 14:04:52 UTC,@Gunnar and @Simon
1823444,2019-04-21 10:18:28 UTC,@Gunnar and ubuntu-sponsors
1823444,2019-04-06 06:16:35 UTC,Add DEP-3 fields to patch
1823444,2019-04-21 14:47:30 UTC,"Thanks Mitsuya! I think it must make it into eoan first, though, and I put a merge proposal in a PPA:"
1823444,2019-04-08 06:13:52 UTC,@Gunnar
1823444,2019-04-08 08:06:52 UTC,"Well, it's highly unlikely that Debian will release a new version before Thursday."
1823444,2019-04-08 10:16:43 UTC,"From the release team POV, this is good to go to disco."
1823444,2019-04-08 12:32:12 UTC,"Thanks Łukasz. Changing back to ""In Progress"" then, to mark that it's ready to sponsor."
1823444,2019-04-08 15:40:03 UTC,"> As regards Debian, I happened to have a local git repository ready, so I have submitted a merge request:
"
1823444,2019-04-08 17:16:47 UTC,@Mitsuya:
1823444,2019-04-07 22:57:32 UTC,Thanks for the bug report and the patch!
1823444,2019-04-12 07:37:21 UTC,"In order to SRU the change the bug needs to follow the guidelines from https://wiki.ubuntu.com/StableReleaseUpdates , basically a description of the impact, a test case and a description of the regression potential of the change"
1823444,2019-04-15 05:20:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823444,2019-04-15 05:37:02 UTC,"Hi Mitsuya-san, thanks for your work."
1823444,2019-04-20 21:39:11 UTC,Unsubscribing the Sponsors Team as the bug description has not been updated to follow the SRU template yet.
1823444,2019-04-21 10:11:36 UTC,debdiff mozc_2.23.2815.102+dfsg-2ubuntu1.dsc mozc_2.23.2815.102+dfsg-2ubuntu2.dsc
1823444,2019-04-21 10:12:16 UTC,debdiff mozc_2.23.2815.102+dfsg-2.dsc mozc_2.23.2815.102+dfsg-2ubuntu1.dsc
1823444,2019-04-21 10:13:38 UTC,debdiff mozc_2.20.2673.102+dfsg-2.dsc mozc_2.20.2673.102+dfsg-2ubuntu1.dsc
1823444,2019-04-11 20:56:43 UTC,"This has now been merged into the Debian repository. Since we now have reached final freeze for disco, it will need to be SRUed to disco as well."
1823445,2021-01-14 14:40:23 UTC,I also am affected by this bug. Kyle's workaround in #7 works for me.
1823445,2020-11-24 17:52:54 UTC,"I hit this when using encrypted volumes. I had a misconfiguration of Barbican/Hashicorp Vault that meant that tokens expired after 10 uses. This allowed me to create 3 volumes successfully, followed by one that failed halfway through the creation. When retrying the creation flow, Cinder hits the metadata already exists issue."
1823445,2020-06-10 16:45:29 UTC,"Unsure if this is welcome here, but this page shows up when you google this error and I figured it might help someone."
1823445,2019-04-29 20:20:01 UTC,Another situation that caused a signature_verified issue:
1823445,2019-04-26 03:16:33 UTC,"I think the reason for these problems is：
There are multiple entries for creating data:
  1) _create_from_image_cache_or_download(create signature_verified)
  2) _handle_bootable_volume_glance_meta(create from glance)
Actually, we should do it just in _handle_bootable_volume_glance_meta,
this is the correct and initial design idea."
1823445,2019-04-16 21:39:50 UTC,"I'm pretty sure that Eric is right.  What's happening is that when CONF.verify_glance_signatures != 'disabled', the signature_verification flag is written directly to the cinder DB.  Later, in the normal flow, all of the image_metadata is written to the DB, and since the db API doesn't allow updating, if there's also a signature_verification present from the actual image metadata, that's causing the exception."
1823445,2019-04-16 13:57:11 UTC,"Sorry, I haven't had a chance to review this again - will try to review and provide feedback on Eric Harney's response soon."
1823445,2019-04-08 14:02:42 UTC,I wonder if this is the full scenario:
1823445,2019-04-16 21:43:40 UTC,"I think that although (1) would fix this issue, (4) is probably a better way to go.  (It looks like (1) would work, but it could be one of those things where there's an issue you don't find until later.  I looked at the original implementation, and when the signature_verification flag was introduced to the patch, it was in the current format of writing directly to the DB.  So I don't know whether that was a design decision forced by necessity or choice.)"
1823448,2019-08-26 12:15:59 UTC,It's fixed in https://launchpad.net/ubuntu/+source/cogl/1.22.4-3/
1823448,2019-09-17 03:21:57 UTC,"Hello Matthias, or anyone else affected,"
1823448,2019-10-24 07:19:26 UTC,"The new version built on i386 and seems to have no functional regression, marking as verified"
1823449,2019-04-09 01:38:20 UTC,"Fixed in revision 94ba1bcb87493d54cfc90225e2ce8781500304d5
https://git.launchpad.net/kicad/patch/?id=94ba1bcb87493d54cfc90225e2ce8781500304d5"
1823449,2019-04-08 12:59:03 UTC,"Hi Sebastian,
Can you please either provide the project files you were using when you see this bug, or a simplified test case that reproduces it?  It's important to know the exact scenario where the nets are not updated properly in order to find the bug.
Thanks!"
1823449,2019-04-08 16:04:33 UTC,"Hi John,"
1823449,2019-04-08 04:38:38 UTC,"Application: kicad
Version: (5.1.0-165-g615c49315), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013"
1823449,2019-04-10 16:09:12 UTC,"Fixen in latest nightly (r12707 from yesterday)- all works well now ;-)
Thanks a lot!"
1823449,2019-04-06 16:34:50 UTC,"NOPE!
on my side (Win10x64) I hit F8 over 10 times- erased net in Schema still be in PCB, even if KiCAD restarted.
Try same project in V5.1: everything is fine....."
1823449,2019-04-06 11:27:30 UTC,Looks similar to https://bugs.launchpad.net/kicad/+bug/1823177
1823449,2019-04-06 18:04:34 UTC,"Please include your KiCad version information.  There was recently a major change to the schematic netlist generator.  There were a few bugs which have already been fixed.  The last fix was in commit ec2c571a so if your nightly build is earlier than that, please try a more recent build to make sure your issue hasn't already been resolved."
1823451,2019-04-07 14:58:13 UTC,Changing the short to int uses two more megabytes for varyobj_page_scan_start_offset and allows 2^24 NOPs to be allocated.
1823451,2019-04-07 14:05:02 UTC,"I don't have the original code, but the fact that somebody has stumbled on that error means that it's a bit suboptimal. I did suggest (setf sb-c::*compile-file-to-memory-space* :dynamic), but that robs of some of the nice features provided by immobile code."
1823451,2019-04-07 13:53:32 UTC,"Well obviously, I wasn't asking _how_ to make it happen, I was asking _why_."
1823451,2019-04-07 00:51:27 UTC,"COMPILE-FILE is virtually incapable of producing such a large code object in anything other than contrived example such as this.  An organic example might motivate a fix, otherwise it is working as designed."
1823451,2019-04-07 10:42:42 UTC,"That error was reported to me, but without any code."
1823451,2019-04-07 10:46:13 UTC,Here it is without any tricks:
1823452,2019-04-08 13:40:52 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1823452,2019-04-23 14:24:51 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1823452,2019-06-23 04:18:21 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1823453,2019-12-30 22:49:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823455,2019-04-10 05:52:35 UTC,Thanks Tilmann for the feedback.
1823455,2019-04-09 20:22:38 UTC,"Hi Christian,"
1823455,2019-06-10 04:17:18 UTC,[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.]
1823455,2019-04-08 13:10:17 UTC,"Odd, I have not seen such a case yet.
All I found was a very old bug 577834 which also didn't end in a clear indication what the problem was."
1823456,2020-11-15 18:15:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823458,2019-05-13 18:40:13 UTC,"This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.37~cloud0
---------------"
1823458,2019-05-07 19:26:59 UTC,"@sil2100 yes I agree, let's wait longer before releasing.  We have the Canonical customer performing testing with the package, and we can run some additional sanity checks as well.  The config coming from the customer is an openstack setup using OVS, so that's what we will setup and perform sanity testing on."
1823458,2019-05-13 18:40:11 UTC,The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1823458,2019-05-16 12:34:05 UTC,"see bug 1829245 for regression introduced by this patch; these patches will be reverted from xenial, and then re-uploaded along with a patch for the regression in bug 1829380"
1823458,2019-05-13 18:37:51 UTC,The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1823458,2019-05-13 11:04:51 UTC,This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.37
1823458,2019-05-13 10:54:51 UTC,"The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823458,2019-05-13 10:54:38 UTC,"This is even more than what I wanted, thanks!"
1823458,2019-05-10 14:40:03 UTC,"On a Xenial DPDK setup with the proposed qemu version (1:2.5+dfsg-5ubuntu10.37), I created a VM and attached a vhost-user interface to it using this xml:"
1823458,2019-05-08 06:49:10 UTC,"> @cpaelzer, if you have any suggestions for specific tests/configurations
> that might be good to test the specific code changed here, please let me
> know.
"
1823458,2019-05-07 19:11:56 UTC,I'm setting this to Incomplete per sil2100's last comment.
1823458,2019-05-13 18:37:54 UTC,"This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.9~cloud5.1
---------------"
1823458,2019-04-30 10:07:20 UTC,"clarification: by ""original reporter"" I mean the customer of Canonical, reporting the problem to us."
1823458,2019-04-11 21:28:22 UTC,test builds in https://launchpad.net/~ddstreet/+archive/ubuntu/lp1823458
1823458,2019-04-23 09:50:07 UTC,"Note as mentioned in the description, it appears this was fixed upstream by commit e7c83a885f8, which is included starting in version 2.9. However, this commit depends on at least commit 5345fdb4467, and likely more other previous commits, which make widespread code changes and are unsuitable to backport. Therefore this seems like it should be specifically worked around in the Xenial qemu codebase."
1823458,2019-04-24 13:59:33 UTC,SRU note: please see Christian's MP review (linked from this bug) for some advice on additional care during SRU verification.
1823458,2019-04-24 14:00:19 UTC,"Hello Dan, or anyone else affected,"
1823458,2019-05-06 09:01:30 UTC,"Since this SRU is rather hard to verify + Christian's suggestion to let the SRU age a bit longer, I would still wait a few days before releasing."
1823458,2019-04-24 20:53:05 UTC,"Hello Dan, or anyone else affected,"
1823458,2019-04-24 20:54:33 UTC,"Hello Dan, or anyone else affected,"
1823458,2019-04-30 10:06:48 UTC,This has been verified by the original reporter to fix the problem of qemu crashing.
1823458,2019-04-24 16:40:56 UTC,"uca: workaround patches are needed in mitaka and ocata.  Mitaka can pull from Xenial build as usual, and debdiff for Ocata attached.  Other UCA releases are later than 2.9 and so are fixed with the upstream fix mentioned in the description."
1823459,2019-04-08 07:16:56 UTC,"ftbfs in cosmic as well:
https://launchpadlibrarian.net/418327942/buildlog_ubuntu-cosmic-arm64.guile-2.2_2.2.4+1-1ubuntu1_BUILDING.txt.gz"
1823459,2019-04-11 16:35:00 UTC,Fix proposed upstream: http://lists.gnu.org/archive/html/guile-devel/2019-04/msg00015.html
1823459,2019-04-16 13:40:36 UTC,"Thank you for the report but Cosmic build issues are low priority at this point, tagging as rls-cc-notfixing , that doesn't stop fixing those problems but they are not going to be tracked as rls issues"
1823459,2019-05-07 21:02:58 UTC,This bug was fixed in the package guile-2.2 - 2.2.4+1-1ubuntu3.1
1823460,2019-04-08 12:11:54 UTC,Thank you for your bug report. Could you add your journalctl log after getting the issue? Also it might be worth trying with another key in case it's a device issue
1823460,2019-06-08 04:17:44 UTC,[Expired for gnome-disk-utility (Ubuntu) because there has been no activity for 60 days.]
1823462,2019-04-06 16:54:08 UTC,"The dxf file shows nothing, both in FreeCAD and AcmeCad."
1823462,2019-04-08 19:21:06 UTC,"""Import Graphical Outlines"" isn't entirely correct either.  Honestly ""Import Vector Graphics File"" is what this feature actually does.  Bitmaps in a vector graphics file are not vector graphics.  I would be open on adding a tool tip that states the non-vector graphics in these files will not be imported."
1823462,2019-04-06 20:20:16 UTC,"Understood.
So:"
1823462,2019-06-08 16:45:29 UTC,"Fixed in revision f7550940ee5d676483f95f3ee32561e667fd9573
https://git.launchpad.net/kicad/patch/?id=f7550940ee5d676483f95f3ee32561e667fd9573"
1823462,2019-04-06 14:23:56 UTC,My version:
1823462,2019-04-06 14:21:00 UTC,Also the section title use bold text and huge text size. This is not coherent with the other dialogs style.
1823462,2019-04-06 14:23:38 UTC,"Other issue: the selected unit, when the dialog opens, is always millimeters (I use that) but should this follow the current unit of the canvas?"
1823464,2019-10-08 08:01:59 UTC,"The package is building fine now on 19.10 so marking fixed there
https://launchpad.net/ubuntu/+source/gnome-keyring/3.34.0-1ubuntu1"
1823464,2019-10-08 08:02:35 UTC,We are not going to spend effort fixing Disco/s390x at this point
1823466,2019-09-16 08:23:08 UTC,Migrated to https://github.com/widelands/widelands/issues/3405
1823466,2019-08-10 17:17:06 UTC,"Frisians are mentioned now, ""Wares in Transit"" still needs adding."
1823466,2019-04-15 05:25:47 UTC,"""wares in transit"" is that wares in the input queues become darker when they're on their way."
1823466,2019-04-13 14:31:28 UTC,What do you mean with 'wares in transit'?
1823466,2019-04-09 10:36:36 UTC,Ok changing the sentence to mention a new tribe is more then reasonable. I thought you meant adding them into a tutorial.
1823466,2019-04-07 16:02:01 UTC,"Oops, crossposted :)
But I´m also against having one of the tutorials featuring an advanced tribe, if that was what you mean"
1823466,2019-04-07 15:59:55 UTC,"Well, one of the very first sentences says "".. has three tribes the Barbarians, Imperials and Atlanters"". We shoud only change that one. The frisian campain was enough tutorial for me,
so we dont need this unless Benedikt will dot it, perhaps."
1823466,2019-04-07 15:48:12 UTC,"some new features have alredy been incorporated (e.g. barracks) however I agree ""wares in transit"" would be nice to be explained in the economy +1."
1823466,2019-04-07 16:00:47 UTC,"The first tutorial says ""There are three different tribes in Widelands: the Barbarians, the Empire and the Atlanteans."" At least this text should be updated."
1823471,2019-09-15 15:07:56 UTC,Migrated to https://github.com/widelands/widelands/issues/3407
1823471,2019-04-07 15:39:31 UTC,Ok I will add an objective test section like in the 1st and 2nd mission
1823471,2019-04-07 19:37:24 UTC,ok fix branch is uploaded. This is safe for b21. If it should be in b20 we would need to copy the translation for the victory headline from emp 02 to emp03 and emp 04 for all languages.
1823474,2019-06-18 04:17:31 UTC,[Expired for openssh (Ubuntu) because there has been no activity for 60 days.]
1823474,2019-04-08 12:54:38 UTC,I have seen such errors related to OpenVZ 6 - you can take a look at bug 1814124 and bug 1811580 for that if it applies to you.
1823475,2019-09-15 16:14:00 UTC,Migrated to https://github.com/widelands/widelands/issues/3408
1823476,2019-04-08 17:06:18 UTC,"With the advice of the Security Team, this rebuild is going to wait until such time that the SRU lands; pushing a change for this into proposed at this time could block security upgrades or cause some confusion if we need to push security updates at this time."
1823476,2019-04-06 17:17:41 UTC,Devel release = invalid because this is Bionic specific.
1823477,2019-04-06 17:33:44 UTC,"The reason might be that in N/KN versions ""media relevant technologies"" are not included, which in turn might led to the missing dependent lib problem."
1823490,2019-04-06 21:10:52 UTC,"Okay I see the git repo that this descends from, https://github.com/ar-/incron, has this fix and several others. And I see that the upstream is the debian package.  How do we go about getting the whole chain updated?"
1823490,2019-04-06 23:15:33 UTC,"Given how this package is not getting much love, I switched to using systemd's systemd.path functionality.
Very briefly:"
1823490,2019-06-25 15:34:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823493,2019-04-08 12:43:27 UTC,"Thank you for the report, this really is an ugly error.
I'll tag up the bug as fixed in Cosmic and later already, but need to discuss how to proceed in this case. The upstream discussion mentioned having a lot of ""header filters"".
You might help me understand, is that something the people commonly have or something that creeps up over time?"
1823493,2019-04-08 20:11:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823493,2019-10-16 15:51:28 UTC,"Dropping the ubuntu-server subscription, since there's still not enough information to proceed, and since the server team has not adopted mailman3 for active maintenance in main."
1823494,2019-04-08 01:03:20 UTC,I've tried having the option On and Off yet the part still gets thrown in the center of view when using the arrow keys to move. This also happens when trying to use the mouse to move.
1823494,2019-04-07 10:16:18 UTC,"Do you have ""Centre and warp cursor on zoom"" turned on or off?"
1823494,2019-04-08 03:39:40 UTC,One option might be to add bounding box corners to the list of drag origin points.
1823496,2020-08-11 08:29:46 UTC,"Removing the latest .crash log, which was produced by gnome-shell in my case, fixed the issue. No dialogue pops up on boot up."
1823496,2020-08-10 12:48:42 UTC,"This issue causes the ""System program problem detected"" dialogue on every boot up on my end, similar to bugs #794757 and #95727. Checking the syslog after a boot up or killing and launching update-notifier via Terminal reveals the same Gtk-Message."
1823496,2019-07-14 06:16:12 UTC,The bug seems to be connected with https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1821412
1823496,2020-03-18 19:42:25 UTC,I have the same problem.
1823496,2019-04-10 03:53:02 UTC,"I have same problem, too."
1823496,2019-04-10 03:53:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823497,2019-04-12 15:08:30 UTC,"This should be working now, please re-open if you see any issues"
1823497,2019-04-08 11:36:40 UTC,The same happens in the windows version too.
1823497,2019-04-08 14:13:15 UTC,This is probably because real time connectivity is currently disabled.  I can put in a workaround.
1823497,2019-04-07 13:32:21 UTC,Sure
1823497,2019-04-07 03:57:19 UTC,"Hi Oleg-  Please add the version information for which this is happening.  It may be a while before someone looks at it, at which point the ""a few days ago"" reference is hard to track down."
1823497,2019-04-07 06:00:28 UTC,"Sorry, I'm only using the nightly builds so I always forget to mention that I'm using the nightly builds on Ubuntu ;)"
1823497,2019-04-07 09:56:59 UTC,"@Oleg, please can you copy the exact version information from Help -> About KiCad -> Copy Version Info"
1823499,2019-04-07 03:30:07 UTC,This change was made by a bot.
1823499,2019-04-08 05:05:13 UTC,This seems to be fixed upstream by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a8ab5ea0cde753b03bfefe4c98a8c4c61f46550
1823500,2019-04-07 11:11:33 UTC,more info to eeschema text field
1823500,2019-04-07 03:35:23 UTC,"In addition as already stated version (5.1.0-153-gee14da309), release build"
1823500,2019-04-07 05:46:43 UTC,More information e.g.
1823501,2019-04-30 12:50:36 UTC,"Still issues, updated test file, when more than one component are on the two netlist DRC sees it as a duplicate, but still doesn't connect some of the components."
1823501,2019-04-30 12:52:36 UTC,Sorry forget to add version info
1823501,2019-04-23 04:30:25 UTC,Looks OK now.  Thanks a lot!
1823501,2019-05-06 08:26:24 UTC,"Sorry about that.
Regards"
1823501,2019-05-08 08:35:42 UTC,"Yes I can confirm it works with latest build.
Thanks."
1823501,2019-05-05 16:53:45 UTC,"Hi Alan, your file Test1.zip does not load, because it is missing the subsheet ""file5CB793ED.sch""
Can you please upload the test project including the subsheet so I can check it?"
1823501,2019-04-21 23:20:39 UTC,"I believe this is fixed by https://git.launchpad.net/kicad/commit/?id=e2c12d8c2578dc6c3bf7293ccda2d747dfd9761c
Please re-open if you see problems"
1823501,2019-05-06 23:44:18 UTC,"Hi Alan,
Thanks for the updated file.
It looks like it is working for me on a more recent build.
Your version 5.1.0-375-g3aaba79b8 is a week old or so, could you please try a newer nightly and report if you still see the issue?
Thanks."
1823501,2019-04-13 02:49:53 UTC,Checking on the latest 203019d ...
1823501,2019-04-12 04:27:33 UTC,"Some new fixes in tonight, please re-open if you see further problems"
1823501,2019-04-11 07:54:24 UTC,"Still not working, unless the master you are talking has not been migrated to the latest night build. DRC now picks up that there are more than one name given to this bus or net and then picks one of the names carrying to pcbnew.
Attached the project used to test."
1823501,2019-04-11 04:26:35 UTC,"I can no longer reproduce this as of latest master 3b46253
Can anyone else still see this problem?"
1823501,2019-04-07 03:55:03 UTC,"Regardless of the actual netname, a design like this clearly intends the two nets to be connected."
1823501,2019-04-13 02:57:49 UTC,This is the updated test case to reproduce the issue.
1823502,2019-04-08 13:33:32 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1823503,2019-04-07 11:25:32 UTC,"For new installations, the /etc/network/interfaces file does have text explaining that ifupdown is no longer used and network config is now done via netplan."
1823503,2019-06-07 04:17:17 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1823511,2019-04-17 18:23:28 UTC,This requires snapd 2.38 which provides a clean API to retrieve on host snaps
1823511,2020-05-26 21:08:24 UTC,This has been released many moons ago
1823512,2019-05-08 12:07:13 UTC,"Oh, this is complicated as the default command is ""snap"", so this is actually an option to the snap command."
1823512,2019-04-18 09:25:54 UTC,@sergiusens
1823512,2019-04-17 18:19:41 UTC,"I do not understand this, this is something we already support, do you mind clarifying?"
1823514,2019-04-07 07:57:55 UTC,"Foundation seems to change the URL to utilize third-party host servers
: https://github.com/OpenStackweb/openstack-org/commit/cc3fea17010402b12e94981d0bd51b5739242818"
1823514,2019-04-07 08:03:30 UTC,I submitted a bug fix to https://review.openstack.org/#/c/650570/
1823514,2019-04-07 08:18:45 UTC,"This was broken by a change to the openstack.org website, it needs at least a redirect there to allow old documents that won't get republished to see the new content. Added openstack-org as project."
1823514,2019-04-07 21:08:43 UTC,Thank you for the report.  This issue has been resolved.
1823514,2019-05-30 01:39:17 UTC,This issue was fixed in the openstack/openstackdocstheme 1.30.0 release.
1823515,2019-04-08 15:26:49 UTC,"agree with this.  I would even be in favor of abusing the precise timing a little bit to our advantage:  For tracks in a directory imported at the same time, set the timestamps and increase each file by one (one nanosecond or one nanosecond) for the alphabetical order of the files in the directory.  That way sorting by date added would still maintain a predictable and useful order."
1823515,2019-04-17 12:00:55 UTC,"yeah, I also had the a-Z sorting in mind.
I thought this would happen automatically as files aren't recognised at light speed, are they :)"
1823515,2019-04-27 09:20:28 UTC,"I have also asked this earlier, this will help much, when add many albums."
1823515,2020-04-21 00:59:32 UTC,"@Owen Williams: It would be really nice if tracks with identical albums were inserted in reverse track-number order, rather than alphabetical. Reverse because this would allow sorting by newest-first date-added to also sort albums in the correct order."
1823516,2019-05-21 02:07:52 UTC,Someone probably needs to find a relevant upstream Xorg bug link to see where/if it is being discussed there.
1823516,2020-08-24 02:43:19 UTC,Proposed fix/hack:
1823516,2019-05-22 20:51:40 UTC,"Couldn't find a bug, but it's described as a known issue here: https://blogs.gnome.org/uraeus/2019/04/03/preparing-for-fedora-workstation-30/"
1823516,2019-04-11 01:59:40 UTC,Apparently the feature doesn't exist in Xwayland yet. Someone mentioned that it's a known issue and the upstream developers will be looking at completing it this year.
1823516,2019-05-20 18:16:45 UTC,Is there any update on this?
1823516,2019-04-08 07:09:07 UTC,Rebuilding xorg-server with --enable-xwayland-eglstream didn't help (!?)
1823516,2019-04-08 01:32:45 UTC,"Added a xorg-server task, because I recall that needed rebuilding with EGLStreams support enabled in Xwayland. Maybe that's the only problem here?"
1823516,2019-04-07 15:20:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823516,2019-04-10 17:29:39 UTC,Is there anything one can do to help resolving this issue?
1823518,2019-04-07 10:32:40 UTC,"N.b. The automatically-added (by apport-bug(1)) /etc/updatedb.conf in
     this problem report has been modified by me to exclude both CryFS
     vaults, and also (as an additional precaution), some typically-used
     (by me) mountpoint names."
1823518,2019-04-11 16:44:29 UTC,"I think some solution here is needed. There are a lot of encrypted filesystems, and I don't think the /etc/updatedb.conf file should be a curated list of those. Given that both CryFS and EncFS are packaged in Ubuntu, I think it's reasonable that they should be in covered by /etc/updatedb.conf."
1823518,2019-07-30 22:09:19 UTC,This bug was fixed in the package mlocate - 0.26-3ubuntu3
1823519,2020-01-01 10:50:01 UTC,"✗ podman run --rm snapcore/snapcraft:stable snapcraft --version
snapcraft, version '3.8'"
1823522,2019-08-24 14:06:33 UTC,Can you confirm this is still an issue ? I am not able to replicate this.
1823522,2019-08-26 18:21:00 UTC,Confirming it is fixed.
1823527,2019-08-28 14:46:09 UTC,"I've been casually looking into this but have a question: Is the requirement to check with python-tripleoclient 11.3.1 a hard requirement for this, because the current version of python-tripleoclient is 12.1.0?"
1823529,2019-04-07 12:40:12 UTC,"StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x5588d0d734d8 <__FUNCTION__.63700> ""idle_callback"", message=<optimized out>) at ../../../glib/gtestutils.c:2878
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x5588d0d734b8 ""../src/nautilus-progress-info.c"", line=line@entry=215, func=func@entry=0x5588d0d734d8 <__FUNCTION__.63700> ""idle_callback"", expr=expr@entry=0x5588d0d7346b ""source == info->idle_source"") at ../../../glib/gtestutils.c:2904
 idle_callback (data=0x7f720800ce60, data@entry=<error reading variable: value has been optimized out>) at ../src/nautilus-progress-info.c:215
 g_timeout_dispatch (source=0x7f71f0020480, callback=<optimized out>, user_data=<optimized out>) at ../../../glib/gmain.c:4678
 g_main_dispatch (context=0x5588d2866bb0) at ../../../glib/gmain.c:3189"
1823529,2019-04-07 13:37:38 UTC,https://gitlab.gnome.org/GNOME/nautilus/issues/980
1823531,2019-06-12 14:02:38 UTC,"Reviewed:  https://review.opendev.org/663705
Committed: https://git.openstack.org/cgit/starlingx/ha/commit/?id=4b9ace1ef37e97543a60d8323a776136070c98d9
Submitter: Zuul
Branch:    master"
1823531,2019-06-06 15:47:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/663705"
1823531,2019-04-08 18:45:40 UTC,"SM monitors all interfaces, and only process failover on the ones that are configured as OAM, mgmt, or infra networks."
1823531,2019-04-08 17:24:46 UTC,"Marking as release gating; not urgent given there doesn't appear to be a serious system impact. However, this causes noise in the logs."
1823532,2019-04-08 12:07:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1823532,2019-06-08 04:17:42 UTC,[Expired for evolution-data-server (Ubuntu) because there has been no activity for 60 days.]
1823533,2019-05-29 10:31:27 UTC,"This should be fixable by updating to Krita 4.1.8 bugfix release with a stable release update, as would be bug #1825960"
1823534,2019-04-07 14:00:06 UTC,This change was made by a bot.
1823534,2019-04-08 05:17:14 UTC,"Hello,
It's unclear what is your situation here,
can you provide more details about what is happening here? (what's the expected behaviour / actual behaviour)"
1823534,2019-06-08 04:17:25 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1823539,2019-04-07 14:43:51 UTC,"StacktraceTop:
 g_date_time_to_instant (datetime=0x0) at ../../../glib/gdatetime.c:2506
 g_date_time_to_unix (datetime=0x0) at ../../../glib/gdatetime.c:2506
 queue_set_datetime (self=self@entry=0x564a422ac500) at ../panels/datetime/cc-datetime-panel.c:404
 change_time (self=0x564a422ac500) at ../panels/datetime/cc-datetime-panel.c:695
 am_pm_button_clicked (button=<optimized out>, self=0x564a422ac500) at ../panels/datetime/cc-datetime-panel.c:266"
1823539,2019-04-09 19:14:01 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1823539,2019-06-09 04:17:31 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1823542,2019-04-07 16:42:58 UTC,"That fix (commit 9a081a80b7c9 (""fix segfault on strtol"")),
which is in usbauth v1.0.1, does seem to have fixed this
problem.  Ubuntu 19.04(? disco) contains usbauth v1.0.1,
and installing that package on my 18.04 LTS (Ubuntu bionic)
system fixed the segfault."
1823543,2019-06-13 19:07:15 UTC,"@Nick, have you seen this recently, or did the wxString UTF-8 change fix it?"
1823543,2019-05-03 17:08:11 UTC,"Is lp:1825170 related with? (last report mine I release that the crash just happens when I search by alphabet characters and not just number, sometimes the crash is after place or give some zoom."
1823543,2019-05-03 17:48:39 UTC,This does not look like the same bug.
1823543,2019-04-17 21:02:15 UTC,Sounds good Jeff!
1823543,2019-06-23 18:35:59 UTC,I have not seen this recently and I can't seem to provoke it. I will mark it as invalid until I see it again.
1823543,2019-04-13 14:53:55 UTC,"Are you still getting these Nick?  If so, are the backtraces still the same?"
1823543,2019-04-07 15:28:11 UTC,"I got another crash, with another backtrace but triggered by similar actions. In this case I was placing a hierarchical pin in the symbol for a subsheet."
1823543,2019-04-17 20:50:05 UTC,"@Jon, I looked into the wchar_t vs char compiler flag, and I really don't think it's going to cause a lot of bugs like @Wayne worries.  The only downside appears to be more storage for strings, but it's not like we're a word-processor with tons of text (and besides, even then text is tiny next to bitmaps)."
1823543,2019-04-08 01:11:03 UTC,"Ahh, another wxString threading crash, it looks like.  At least the first one.
The second one might be also, but the backtrace is from a non-threaded area."
1823544,2020-01-24 09:35:24 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1823544,2020-03-25 04:17:18 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1823544,2019-10-16 08:41:45 UTC,I've experienced same issue. Kept my machine running overnight with open gnome-shells.
1823544,2019-04-10 01:55:56 UTC,Thanks. That suggests removing extensions might not have helped.
1823544,2019-04-09 10:42:06 UTC,"Yes but the amount of time I kept in the first test was not the same, I just do not have enough time to test"
1823544,2019-04-09 02:10:28 UTC,Thanks.
1823544,2019-04-08 11:56:51 UTC,"Ok, fine"
1823544,2019-12-19 17:36:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823544,2019-04-08 09:38:46 UTC,apport information
1823544,2019-04-08 09:38:45 UTC,apport information
1823544,2019-04-08 09:38:44 UTC,apport information
1823544,2019-04-08 02:37:52 UTC,Note to self and others:
1823544,2019-04-08 02:35:42 UTC,Thanks for the detailed bug report. Unfortunately we do still need more system information so please run:
1823544,2019-04-07 15:33:23 UTC,vram usage on fresh start
1823544,2019-04-08 09:52:48 UTC,Thanks.
1823546,2019-04-07 18:44:21 UTC,A second cursor might be a bit confusing but some less obtrusive way to indicated the relative cursor grid position wouldn't be a bad idea.
1823546,2019-04-08 09:45:41 UTC,"Perhaps just a small unobtrusive 1px crosshair about the size of the grid origin marker might be useful? I'd certainly like to see the current relative origin. If it was its own item class, visibility/colours could be controlled by the Items panel?"
1823546,2019-04-08 13:20:16 UTC,"On 4/8/2019 5:45 AM, John Beard wrote:

> Perhaps just a small unobtrusive 1px crosshair about the size of the
> grid origin marker might be useful? I'd certainly like to see the
> current relative origin. If it was its own item class,
> visibility/colours could be controlled by the Items panel?
"
1823547,2019-04-08 16:40:24 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc3 kernel [0]."
1823547,2019-04-08 07:08:50 UTC,"I cannot add a kernel log, as I wasn't even able to boot the system and install the Operating System."
1823547,2019-04-07 16:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823549,2019-04-07 21:33:58 UTC,"I get a ""corrupt file"" trying to play the video on OSX, but I'm pretty sure this is fixed by https://bugs.launchpad.net/kicad/+bug/1823090."
1823549,2019-04-08 06:31:22 UTC,"the video takes a long time to open. I saw the description of your bug report. and there and there the text, but I have several another. Bug found yesterday"
1823549,2019-04-13 13:53:01 UTC,"Good!
Everything is flipped correctly, but the designations of the element still have the property of separately flipping when you hover them and press F key."
1823550,2019-04-10 19:14:02 UTC,@Norbert
1823550,2019-04-13 14:11:48 UTC,"Thanks, Khurshid!"
1823550,2019-04-13 13:37:53 UTC,In lp: #1242984 light theme is already using (see https://code.launchpad.net/~larsu/ubuntu-themes/gedit-fixes/+merge/201212)
1823550,2019-04-12 17:50:26 UTC,@seb128
1823550,2019-04-12 16:02:36 UTC,It doesn't seem an issue on a default disco install with the new yaru theme?
1823550,2019-05-11 15:16:37 UTC,For reference this is the commit for ubuntu-mate-artwork that resolves this issue in our themes:
1823550,2019-05-29 20:06:53 UTC,This bug was fixed in the package ubuntu-mate-artwork - 19.10.2
1823550,2019-04-09 02:12:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823550,2019-04-08 15:30:07 UTC,"Did you try changing font by de-selecting ""use system fixed width font"" ?"
1823550,2019-04-08 13:27:33 UTC,"The problem is also exists in Gedit, which is by default themed with Ambiance theme from `light-themes` package.
Problem confirmed on Ubuntu session (means GNOME) of Ubuntu 18.04.2 LTS and in upcoming 19.04 while running Unity desktop. Here only Adwaita theme looks correct."
1823550,2019-04-07 22:27:32 UTC,"The issue:
*   exists with the following themes - Ambiant-MATE, Ambiant-MATE-Dark, BlackMATE, GreenLaguna, Radiant-MATE, TraditionalGreen, TraditionalOk;
*    does not exist with BlueMenta, Blue-Submarine, Green-Submarine, High Contrast, High Contrast Inverse, Menta."
1823550,2019-04-07 17:18:03 UTC,The correct (expected) font is presented on the screenshot from Ubuntu MATE 16.04 LTS.
1823550,2019-04-08 16:31:06 UTC,I'm using default clean installation of Ubuntu with default settings of GNOME desktop (say 18.04 LTS).
1823551,2019-04-08 18:08:13 UTC,Please try manually installing the linux-generic package and then upgrading again.
1823551,2019-06-08 04:17:52 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1823551,2019-04-07 17:16:21 UTC,"/etc/apt/source.list offers no assistance; in addition, I modified sources.list to use official endpoints, and got the same error."
1823553,2019-04-07 18:28:37 UTC,Appears only when using hierarhical sheets
1823553,2019-04-15 03:40:17 UTC,This was fixed by 63db3f7 (11-Apr) as far as I can tell.  Please re-open if you can reproduce it on the latest nightly.
1823553,2019-04-15 06:37:58 UTC,Okay
1823553,2019-04-15 06:52:31 UTC,"It works!
(5.1.0-247-g252934694), release build
Thank you!"
1823554,2019-04-07 18:14:36 UTC,9311db6b3ecbc2f1d1d3634d2352e64f85605af9
1823559,2019-08-13 14:17:58 UTC,I have noticed this before (maybe in another dialog?). Closing and reopening the dialog fixes the issue.
1823559,2019-10-13 04:26:15 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1823559,2019-08-08 22:10:05 UTC,"Fixed in revision 17d015ed5d662ca06b446fda0f84524f8e92006b
https://git.launchpad.net/kicad/patch/?id=17d015ed5d662ca06b446fda0f84524f8e92006b"
1823559,2019-08-08 21:59:35 UTC,I've added code to strip new-lines and tabs.
1823559,2019-04-07 19:33:37 UTC,"Related issue. ""-90.00 deg"" does not show completely inside the text field. Again, no need to save space on the text fields here."
1823559,2019-04-07 19:28:24 UTC,"Related issue. If the full path is added, the 3d part is not being displayed. Changing to a relative path solves the problem. But it should be fixed since the user should use the path as he needs."
1823559,2019-04-07 19:30:55 UTC,"Related issue. The + and - signs on the rotation group should rotate the object in 90 degrees steps. I never saw a wrong part that needs to be rotated in smaller steps. Also, If the user wants to fine-tune the rotation, he can always type the value on the field."
1823559,2019-04-07 19:26:41 UTC,"Related issue. The X, Y, Z input fields on Offset group, does not show the full text. The ""mm"" looks cut it is showing ""mn"". Please, ad a little more horizontal space for the input fields being always visible. There is no need to save so much area here."
1823559,2019-04-07 19:23:32 UTC,Related issue. The folder icon on the side of the Plus icon has its sides cut out.
1823559,2019-04-07 19:32:48 UTC,"Related issue. Why not to move the 3d buttons to the left, since the Scale, Rotation, Offset settings are on the left side of the Preview?"
1823560,2019-04-08 06:19:01 UTC,update: there is an undefinied error also with backup command --full-if-older-than 1M
1823562,2020-03-07 10:10:45 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1823567,2019-04-07 04:34:53 UTC,Description of problem: I just ran hp-check -i as root to see what the output was as when it finished I saw the following lines that worried me:
1823567,2019-04-07 04:37:52 UTC,There's a package conflict between libsane1-devel and lib64sane1-devel that also needs to be adressed at the same time.
1823567,2019-04-07 07:30:58 UTC,This is completely invalid as this is as this from some years now.
1823567,2019-04-08 16:15:20 UTC,Closing as INVALID!
1823572,2019-04-10 20:58:03 UTC,I ended up getting a USB DAC to avoid this issue all together.
1823572,2019-04-08 02:54:13 UTC,"I'm slightly concerned about this, although if Jack is not running then it shouldn't matter:"
1823572,2019-04-08 03:09:42 UTC,"This sounds like bug 1166529, but I am hesitant to mark any bug a duplicate of that because if it's a port routing issue then that's unique to the motherboard model and not unique to the sound chip."
1823573,2019-04-10 01:58:59 UTC,"To get to the grub menu and select a different installed kernel, you need to be fast. The instant the purple screen first appears on boot, tap Escape."
1823573,2019-04-09 16:08:47 UTC,"I can't seem to figure out how to boot to an older kernel on this laptop. Shift and Escape does noting, while the menus opened by F-buttons fail to give advanced boot settings. It's all within the UEFI safety net (which I kind of appreciate after years of BIOS trouble)."
1823573,2019-06-09 04:17:38 UTC,[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]
1823573,2019-04-08 03:12:27 UTC,Thanks for the bug report. The intermediate sound layer (PulseAudio) hasn't changed between 18.10 and 19.04 so this is either going to be a kernel problem or a GUI problem (gnome-control-center).
1823573,2019-04-08 03:13:49 UTC,Please try some older kernels (like 4.18 which was in Ubuntu 18.10) and tell us if that fixes the problem:
1823574,2019-04-08 19:40:56 UTC,patched in upstream debian unstable
1823574,2020-04-25 13:44:02 UTC,in focal: node-deep-extend (0.4.1-2) unstable; urgency=medium
1823575,2019-04-08 18:34:23 UTC,"This was missing code for this release.
Will be finished in 3.1"
1823576,2019-04-07 23:40:19 UTC,"StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x564bfc450f50 <__FUNCTION__.61085> ""nautilus_bookmark_connect_file"", message=<optimized out>) at ../../../glib/gtestutils.c:2878
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x564bfc4508f1 ""../src/nautilus-bookmark.c"", line=line@entry=372, func=func@entry=0x564bfc450f50 <__FUNCTION__.61085> ""nautilus_bookmark_connect_file"", expr=expr@entry=0x564bfc450bc0 ""!nautilus_file_is_gone (bookmark->file)"") at ../../../glib/gtestutils.c:2904
 nautilus_bookmark_connect_file (bookmark=0x564bff278c00) at ../src/nautilus-bookmark.c:372
 nautilus_bookmark_connect_file (bookmark=0x564bff278c00) at ../src/nautilus-bookmark.c:358
 nautilus_bookmark_constructed (obj=<optimized out>) at ../src/nautilus-bookmark.c:613"
1823576,2019-04-08 12:00:24 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1823576,2019-04-29 22:18:29 UTC,This issue appears to be reproducible when accessing a directory with a large amount of files. For me this is the Camera subdirectory in the DCIM directory.
1823576,2019-04-30 15:30:04 UTC,"Thanks for the steps, the ""times out' step relies on having a device hitting the problem then..."
1823576,2019-06-30 04:17:39 UTC,[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]
1823580,2019-09-25 12:19:22 UTC,This bug was explored in this pull request https://github.com/snapcore/snapd/pull/6697 but is has not been merged and indeed has been closed for now.
1823582,2019-05-22 12:52:46 UTC,"Reviewed:  https://review.opendev.org/657513
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=3dab5f30fdb1afa6fd8a71093528276061553d08
Submitter: Zuul
Branch:    master"
1823582,2019-05-14 13:33:43 UTC,thx for clarification. I think the last comment makes sense in focus of the document (image guide)
1823582,2019-05-10 17:53:37 UTC,"About the Windows images, I left a review on https://review.opendev.org/#/c/657513/1. I hope this helps in clarifying the status."
1823582,2019-05-10 14:51:39 UTC,"One other thing: there's a large amount of dynamic content (including an EULA), so it's possible that it doesn't show up correctly on older browsers. Please let us know if that is the case."
1823582,2019-05-10 14:16:09 UTC,"Thanks for filing this bug. I double checked the image download page and the links seem ok, both vhdx and qcow2 images are available: https://cloudbase.it/windows-cloud-images/#download"
1823582,2019-05-10 14:03:17 UTC,"It worked well, although I actually clicked twice to download a vhdx image.."
1823582,2019-05-07 12:08:54 UTC,"I can download the image from: https://cloudbase.it/euladownload.php?h=kvm
https://prnt.sc/nlirbv"
1823582,2019-05-07 02:24:11 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657513"
1823582,2019-04-08 17:17:10 UTC,???
1823582,2019-04-08 07:35:30 UTC,"Hi oymlaml, thanks for you reporting. I check the URL and it works in my side. :D"
1823583,2019-04-08 03:16:22 UTC,"Next time a freeze happens, restart the system and then run this command to collect the log from the previous (frozen) boot:"
1823583,2019-04-08 05:14:15 UTC,"I ve got it. I'll do it, probably soon ^^"
1823583,2019-04-16 06:34:01 UTC,"Also, in case the freeze was caused by something crashing please follow these steps too:"
1823583,2019-05-20 12:03:36 UTC,I added the prevboot.txt file at attachment. I realized in logs that there are some lines about cpu's execution like that:
1823583,2019-05-21 02:16:53 UTC,I can't see anything else in that log which might explain the freeze.
1823583,2019-07-20 04:17:31 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1823594,2019-04-08 02:33:40 UTC,Addition some more information in case helpful...
1823594,2020-05-04 13:00:36 UTC,I can reproduce the problem on the current master in devstack.
1823594,2020-07-13 08:23:23 UTC,"I have tried to reproduce this issue but in the time of resizing instances status is still in RESIZE state and task state is resize_prep, that mean resize is not completed successfully."
1823598,2019-05-22 18:42:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1830066, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.  Additionally, any further discussion regarding the bug should occur in the other report.  Please continue to report any other bugs you may find."
1823599,2019-10-25 05:56:39 UTC,"78153dd45e7e
v5.1"
1823600,2019-04-08 13:26:43 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1823602,2019-04-08 03:33:53 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/650609"
1823606,2019-04-16 01:43:49 UTC,"On x86 system, the issue comes from firmware, EDKII implemented on QueryCapsuleCapabilities runtime services uses boottime services, which causes system hang. The fixed patch has pushed into EDKII already, use the newer EDKII should fix the system hang."
1823606,2019-09-16 09:54:54 UTC,Thanks for great help. This issue is fixed.
1823611,2019-07-21 12:28:41 UTC,I have tried to gather some information about svg files and it looks to me that allowing svg files in the wiki can be dangerous. The main reason is: svg are xml files and can be manipulated by javascript in the same manner as a normal html document. More over svg files are allowed to contain script in it self.
1823611,2019-07-27 12:14:31 UTC,Let's scrap this idea then - we won't want to have to deal with potential JavaScript here.
1823613,2019-04-08 05:27:02 UTC,Please check full log as attached.
1823613,2019-04-08 05:34:08 UTC,"Snaps currently installed:
Name              Version          Rev   Tracking  Publisher            Notes
alsa-utils        1.1.2-5          68    stable    canonical          -
bluez             5.47-3           166   stable    canonical          -
caracalla         16.04-1.38       52    stable    canonical          gadget
caracalla-kernel  4.4.0-143.169    106   stable    canonical          kernel
checkbox          1.0              45    stable    ce-certification-qa  -
checkbox-plano    16.45            295   16        ce-certification-qa  devmode
core              16-2.37.2        6405  stable    canonical          core
docker            18.06.1-ce       321   stable    canonical          -
locationd         4.2.1            163   stable    canonical          -
modem-manager     1.8.0-7          222   stable    canonical          -
network-manager   1.2.2-22         379   stable    canonical          -
tpm2              1.0-5            42    stable    canonical          -
udisks2           2.6.4-2          100   stable    canonical          -
uefi-fw-tools     1.5.3-0.7.2+git  11    stable    canonical          -
wifi-ap           21               250   stable    canonical          -
wpa-supplicant    2.4.3            41    stable    canonical          -"
1823613,2019-04-08 05:34:47 UTC,snap list information from ethan:
1823613,2019-04-08 07:58:47 UTC,The automated test plan (which is the only one including the reboot test) requires a checkbox remote setup. The slave daemon will then run as root and you won't have this PermissionError.
1823616,2019-04-08 06:05:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823616,2019-04-08 06:10:50 UTC,Confirmed. I am also in Australia. Although I can't tell if the correct format should be that shown in:
1823616,2019-04-08 06:38:26 UTC,"On my fresh install, the correct date/time formatting is showing under:"
1823616,2020-01-24 09:40:41 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1823616,2020-10-30 03:26:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823618,2019-06-08 04:17:29 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1823618,2019-06-08 04:17:31 UTC,[Expired for linux-hwe (Ubuntu Bionic) because there has been no activity for 60 days.]
1823618,2019-04-08 07:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823618,2019-06-11 08:54:16 UTC,"FYI things resurfaced with monitors of higher resolution.
But it was so bad that I sent them back, so no testbed available atm."
1823618,2019-04-08 08:27:32 UTC,"As usual - thanks bug - with a proper ssh set up and logged in it just doesn't trigger anymore :-/
I tried multiple reboots and we can keep the bug if others are affected to join forces, but for now it is incomplete as I can no more reproduce it :-/"
1823618,2019-06-08 04:17:32 UTC,[Expired for linux (Ubuntu Cosmic) because there has been no activity for 60 days.]
1823618,2019-04-08 08:13:24 UTC,"We discussed if just the Graphics output might be dead, I'll set up SSH and try to retrigger."
1823618,2019-04-08 06:34:35 UTC,FYI: The system becomes unresponsive after the crash so I can only report the bug while rebooted into the former HWE kernel version.
1823618,2019-04-08 07:49:33 UTC,"Apport still refuses to attach data :-/
But I since I have the journal with the crash attached that should be ok."
1823618,2019-04-08 07:42:38 UTC,Setting linux-hwe per discussion
1823618,2019-04-08 06:38:16 UTC,"Apport seems to collect and send stuff, but it does not show up here - I'll stop hitting send for now to not have 50 attachments in 10 minutes :-/
Just let me know what you need and I'll make it available."
1823618,2019-04-08 06:35:11 UTC,"I was unsure which package to file it against as it is hwe, please feel free to adapt the bug tasks accordingly."
1823618,2019-04-08 07:54:02 UTC,"Confirmed to silence the bot, attaching a few logs on my own since apport refuses to do so"
1823622,2019-05-15 17:58:56 UTC,"I think you're looking for https://docs.openstack.org/contributors/ or
https://docs.openstack.org/infra/manual/developers.html"
1823629,2020-02-10 15:29:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823633,2019-07-18 17:16:05 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/671528"
1823633,2019-07-19 17:07:13 UTC,"Reviewed:  https://review.opendev.org/671528
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=6d9f9e2841edcf3a92bbcba7f7a45d9d464a14ee
Submitter: Zuul
Branch:    master"
1823633,2019-09-26 20:12:28 UTC,"Reviewed:  https://review.opendev.org/662874
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=c9782faa9a5dda329b6c2c13457350548a652f27
Submitter: Zuul
Branch:    master"
1823633,2019-09-16 12:00:55 UTC,"Reviewed:  https://review.opendev.org/670836
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2c095811afa8a66b30fa8cf34831b83fcb873fe6
Submitter: Zuul
Branch:    master"
1823633,2019-09-16 19:51:14 UTC,"Reviewed:  https://review.opendev.org/670837
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6c99bf195200422d6db4e8307f5a2e61c2242dc1
Submitter: Zuul
Branch:    master"
1823633,2019-08-30 03:50:34 UTC,"Reviewed:  https://review.opendev.org/650270
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=16679e9700b68b1bc64072751dd3b38b38492546
Submitter: Zuul
Branch:    master"
1823633,2019-07-15 13:49:48 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/670837"
1823633,2019-06-10 23:54:18 UTC,"Reviewed:  https://review.opendev.org/663446
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=7a0a41b90447a1b739d9da0f3498ca0916d0a315
Submitter: Zuul
Branch:    master"
1823633,2019-06-05 21:42:50 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/663446"
1823633,2019-05-21 17:53:36 UTC,"Reviewed:  https://review.opendev.org/650269
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3ab7878384b2c2738baead86919dd77821b53807
Submitter: Zuul
Branch:    master"
1823633,2019-04-21 19:39:18 UTC,"Reviewed:  https://review.opendev.org/650271
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=c6b907a2cfa9626260348f07284206ab87e5712d
Submitter: Zuul
Branch:    master"
1823633,2019-04-12 16:01:31 UTC,"This RFE was approved by the drivers today, with the assumption that the behavior will be the same for all distros"
1823633,2019-07-15 13:49:35 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/670836"
1823634,2019-04-08 16:24:26 UTC,"Good idea. We have to add a new integer field for the table then, e.g. 'position'."
1823634,2019-04-08 21:51:23 UTC,Having it soon would be nice :)
1823634,2019-04-09 08:04:15 UTC,"I decided to not have it too smart. Instead you can edit each screenshot in the admin page for the category. Default position is always 0, order will be like before then."
1823634,2019-04-10 16:33:17 UTC,We may want also to allow ordering of categories. Currently it is ordered by the name. This is no problem if we always have a name like 'Build x'. In the future one may has the idea to add a new category with name 'A new category'. With the current ordering this will be displayed below all other categories then.
1823634,2019-04-10 16:52:00 UTC,+1 to that - I'd say the move to Python 3 has higher priority though.
1823634,2019-09-06 08:22:37 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/298
1823636,2019-04-16 13:39:07 UTC,"Thank you for the report but Cosmic build issues are low priority at this point, tagging as rls-cc-notfixing , that doesn't stop fixing those problems but they are not going to be tracked as rls issues"
1823639,2019-06-09 04:17:36 UTC,[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.]
1823639,2019-06-09 04:17:34 UTC,[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]
1823639,2019-04-09 20:30:23 UTC,"try booting without 'splash', since it seems to be plymouth holding the device"
1823639,2019-04-09 20:31:34 UTC,"also, I don't think modesetting driver was yet good enough in xserver 1.18, so -intel probably is the best option on stock xenial"
1823639,2019-04-08 09:39:51 UTC,"Since your CPU/GPU is fairly new, you don't need that problematic driver installed at all."
1823639,2019-04-08 09:37:47 UTC,This might be the problem:
1823639,2019-04-08 13:28:56 UTC,"Hi Daniel,"
1823641,2019-04-16 13:39:41 UTC,"Thank you for the report but Cosmic build issues are low priority at this point, tagging as rls-cc-notfixing , that doesn't stop fixing those problems but they are not going to be tracked as rls issues"
1823643,2020-02-11 14:21:41 UTC,Cosmic is now end of life
1823644,2019-04-16 13:39:56 UTC,"Thank you for the report but Cosmic build issues are low priority at this point, tagging as rls-cc-notfixing , that doesn't stop fixing those problems but they are not going to be tracked as rls issues"
1823646,2019-05-22 15:09:55 UTC,This was fixed in (1.22-1ubuntu0.18.10.1)
1823650,2019-04-16 13:42:03 UTC,"Thank you for the report but Cosmic build issues are low priority at this point, tagging as rls-cc-notfixing , that doesn't stop fixing those problems but they are not going to be tracked as rls issues"
1823650,2019-04-14 11:54:59 UTC,"Hello,"
1823650,2019-04-08 20:01:25 UTC,I verified that https://git.linuxtv.org/v4l-utils.git/commit/?h=stable-1.14&id=b6c3e824967e25857a41e1c0e23d010317566467 and https://git.linuxtv.org/v4l-utils.git/commit/?h=stable-1.14&id=65b6f255a02de403621e478aac701e3ee56806a4 fix the build issue. However there are some more fixes (double free and uninitialised memory) that I'd like to ship as well. The double free patch backport seems to be incomplete and I asked upstream for clarification: https://<email address hidden>/T/#u
1823650,2019-04-08 13:19:57 UTC,"On 08.04.19 14:12, Gregor Jasny wrote:

> How could I re-create your setup?
"
1823650,2019-04-08 12:12:37 UTC,"Hello,"
1823655,2020-02-21 14:36:00 UTC,"This issue is resolved when using pi-kernel track 18-pi/stable (e.g. 5.3.0-1018.20~18.04.1), however such a version is not yet pushed to 18-cm3"
1823655,2019-10-25 09:31:14 UTC,OK thanks. And what's the problem? Seems the Pi is booting up just fine.
1823655,2019-11-26 10:11:03 UTC,Indeed
1823655,2019-11-26 09:32:27 UTC,In my case I don't get anything in the logs indicating that the kernel is trying to talk to mmc1.
1823655,2019-11-26 08:01:40 UTC,I've just checked this:
1823655,2020-03-09 09:23:25 UTC,"As mentioned on IRC, going forward there will only be a single channel 18-pi."
1823655,2019-11-22 15:40:22 UTC,I've added an SD card slot to my Raspberry CMIO board and verified that the SD card shows up when using the latest Raspbian image and the dtoverlay=sdio config.txt option. Seems to work fine.
1823655,2019-10-25 08:39:39 UTC,"Thanks for following up, here's the log from dmesg.
I've removed some audit logs that are non-applicable."
1823655,2019-06-06 07:43:22 UTC,Any clues on what I should start looking for?
1823655,2019-09-07 04:17:23 UTC,[Expired for linux-raspi2 (Ubuntu) because there has been no activity for 60 days.]
1823655,2019-07-08 06:37:16 UTC,Anyone?
1823655,2019-05-28 06:41:06 UTC,Hi
1823655,2019-05-27 15:40:49 UTC,Can you add all the relevant information here?
1823655,2019-05-27 14:50:35 UTC,Could someone please take a look at this?
1823655,2019-10-25 08:12:03 UTC,Can you please post a complete kernel log?
1823662,2019-04-09 01:51:35 UTC,Jonathan has provided a fix for this in February:
1823664,2019-04-08 11:38:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1823664,2019-04-08 11:40:15 UTC,"> Scrolls initially but does not scroll next.
"
1823664,2019-04-09 01:26:43 UTC,"I uploaded the video but it failed.
So I upload it on YouTube."
1823664,2019-04-09 14:19:56 UTC,Thank you for the video. Is the issue specific to nautilus or do you see it if you use a file selector in e.g gedit or eog? Does it happen in nautilus icons view or only listmode?
1823664,2019-06-09 04:17:29 UTC,[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]
1823668,2019-04-09 01:53:11 UTC,This issue was fixed in March:
1823672,2020-04-04 09:47:30 UTC,Thanks for reporting.
1823674,2019-04-09 02:19:07 UTC,Can you please clarify which icon the problem is in?
1823674,2019-06-08 04:18:01 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1823679,2019-10-29 21:35:08 UTC,Hello Igor
1823679,2019-10-30 08:09:23 UTC,"Hi Zygmunt, I'm currently not working on it. The status was, that with the current `flags` lib we use it's hart to achieve. If you have time, uou can work on this, but please sync with John"
1823680,2019-05-27 21:07:39 UTC,"If there is no warning message, $ snap okay might return nothing."
1823684,2019-11-06 00:17:56 UTC,I have Peach OSI Xubuntu 16.04 LTS 4.4.0-166 64bit
1823684,2019-11-06 00:30:09 UTC,"user@machine:~$ xinput --list-props 14
Device 'AlpsPS/2 ALPS DualPoint TouchPad':
 Device Enabled (136):	1
 Coordinate Transformation Matrix (138):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
 Device Accel Profile (265):	1
 Device Accel Constant Deceleration (266):	2.500000
 Device Accel Adaptive Deceleration (267):	1.000000
 Device Accel Velocity Scaling (268):	12.500000
 Synaptics Edges (290):	153, 870, 115, 652
 Synaptics Finger (291):	12, 15, 0
 Synaptics Tap Time (292):	180
 Synaptics Tap Move (293):	56
 Synaptics Tap Durations (294):	180, 100, 100
 Synaptics ClickPad (295):	0
 Synaptics Middle Button Timeout (296):	75
 Synaptics Two-Finger Pressure (297):	141
 Synaptics Two-Finger Width (298):	7
 Synaptics Scrolling Distance (299):	25, 25
 Synaptics Edge Scrolling (300):	1, 0, 0
 Synaptics Two-Finger Scrolling (301):	0, 0
 Synaptics Move Speed (302):	1.000000, 1.750000, 0.156495, 0.000000
 Synaptics Off (303):	0
 Synaptics Locked Drags (304):	0
 Synaptics Locked Drags Timeout (305):	5000
 Synaptics Tap Action (306):	2, 3, 0, 0, 0, 0, 0
 Synaptics Click Action (307):	1, 1, 0
 Synaptics Circular Scrolling (308):	0
 Synaptics Circular Scrolling Distance (309):	0.100000
 Synaptics Circular Scrolling Trigger (310):	0
 Synaptics Circular Pad (311):	0
 Synaptics Palm Detection (312):	0
 Synaptics Palm Dimensions (313):	10, 100
 Synaptics Coasting Speed (314):	20.000000, 50.000000
 Synaptics Pressure Motion (315):	15, 80
 Synaptics Pressure Motion Factor (316):	1.000000, 1.000000
 Synaptics Resolution Detect (317):	1
 Synaptics Grab Event Device (318):	0
 Synaptics Gestures (319):	1
 Synaptics Capabilities (320):	1, 1, 1, 0, 0, 1, 0
 Synaptics Pad Resolution (321):	1, 1
 Synaptics Area (322):	0, 0, 0, 0
 Synaptics Noise Cancellation (323):	6, 6
 Device Product ID (256):	2, 8
 Device Node (257):	""/dev/input/event6"""
1823684,2019-11-06 00:36:34 UTC,"user@machine:~$ grep -i touchpad /var/log/Xorg.0.log
[    15.043] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/event6)
[    15.043] (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass ""evdev touchpad catchall""
[    15.043] (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass ""touchpad catchall""
[    15.043] (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass ""Default clickpad buttons""
[    15.045] (II) Using input driver 'synaptics' for 'AlpsPS/2 ALPS DualPoint TouchPad'
[    15.045] (**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events
[    15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: x-axis range 0 - 1023 (res 0)
[    15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: y-axis range 0 - 767 (res 0)
[    15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: pressure range 0 - 127
[    15.116] (II) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: device does not report finger width.
[    15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: buttons: left right middle
[    15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: Vendor 0x2 Product 0x8
[    15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: invalid finger width range.  defaulting to 0 - 15
[    15.116] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
[    15.116] (**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events
[    15.168] (II) XINPUT: Adding extended input device ""AlpsPS/2 ALPS DualPoint TouchPad"" (type: TOUCHPAD, id 14)
[    15.168] (**) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[    15.168] (**) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: (accel) MaxSpeed is now 1.75
[    15.168] (**) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: (accel) AccelFactor is now 0.156
[    15.168] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) keeping acceleration scheme 1
[    15.168] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration profile 1
[    15.169] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration factor: 2.000
[    15.169] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration threshold: 4
[    15.169] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
[    15.170] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/mouse1)
[    15.170] (**) AlpsPS/2 ALPS DualPoint TouchPad: Ignoring device from InputClass ""touchpad ignore duplicates"""
1823684,2019-11-06 04:04:17 UTC,"Hi Jan Johansson,
your issue seems to be different, probably a 4.4 kernel regression."
1823686,2019-06-08 04:17:41 UTC,[Expired for evince (Ubuntu) because there has been no activity for 60 days.]
1823686,2019-04-08 10:10:10 UTC,"StacktraceTop:
 gdk_window_get_root_coords (window=0x3ff0000000000000, x=0, y=-13312, root_x=0x7ffd5b723430, root_y=0x7ffd5b723434) at ../../../../gdk/gdkwindow.c:6848
 notify_cursor_location (context=context@entry=0x55e0a6fd6c70) at ../../../../../modules/input/imwayland.c:360
 enable (context_wayland=0x55e0a6fd6c70) at ../../../../../modules/input/imwayland.c:618
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffd5b7235b0, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffd5b723680) at ../src/x86/ffi64.c:525"
1823686,2019-04-08 11:32:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1823686,2019-04-08 11:32:53 UTC,(the issue seems to be in the wayland im code)
1823689,2019-04-12 13:55:28 UTC,Thanks!
1823689,2019-04-08 12:25:26 UTC,"The attachment ""xdg-email.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1823689,2019-04-08 11:48:47 UTC,"Added a bug report upstream, see https://gitlab.freedesktop.org/xdg/xdg-utils/issues/149"
1823689,2019-04-08 11:31:29 UTC,"Thank you for your bug report, could you report it also upstream on https://gitlab.freedesktop.org/xdg/xdg-utils/issues ?"
1823689,2019-04-08 11:37:45 UTC,"Sure, will do it later."
1823696,2019-04-10 11:50:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651508"
1823696,2019-04-30 14:22:28 UTC,"Reviewed:  https://review.opendev.org/651508
Committed: https://git.openstack.org/cgit/openstack/charm-swift-proxy/commit/?id=1160493f3f1403bfd08c338c9099373d6c55e174
Submitter: Zuul
Branch:    master"
1823698,2019-04-08 11:29:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1823698,2019-04-08 11:55:55 UTC,bug could have been received by email on yahoo on another linked computer
1823698,2019-06-08 04:18:02 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1823700,2020-05-01 20:11:01 UTC,Bionic has 1.17.1 no 1.23; newer serie are updated
1823703,2019-12-09 19:03:21 UTC,Fix is at https://review.opendev.org/#/c/650879/
1823703,2020-04-06 07:08:33 UTC,"Reviewed:  https://review.opendev.org/650879
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=33626369e591b03eb75c44b5c45c7969c7cb40e9
Submitter: Zuul
Branch:    master"
1823703,2020-04-06 11:35:01 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/717716"
1823703,2020-04-14 09:38:53 UTC,This issue was fixed in the openstack/glance 20.0.0.0b3 development milestone.
1823704,2020-01-28 20:01:47 UTC,Thanks for reporting.
1823706,2019-04-08 12:00:07 UTC,This change was made by a bot.
1823706,2019-04-11 10:48:36 UTC,Updated in CKCT as well.
1823706,2019-04-09 04:08:35 UTC,"For kernel-testing, fix has been pushed here: https://kernel.ubuntu.com/git/ubuntu/kernel-testing.git/commit/?id=540a6936fe4adc654e3f3caddec705e38a1f1963"
1823707,2019-05-14 12:14:45 UTC,this should be good in later virtualbox releases
1823707,2019-05-14 10:35:08 UTC,This looks like an upstream issue... can you please open an upstream ticket?
1823708,2019-08-31 00:07:04 UTC,From your attached DpkgLog.txt:
1823708,2019-08-31 08:57:15 UTC,"Hello. Thank you for your reply!
That's what I did, after it was suggested to me at stack exchange."
1823709,2019-04-08 12:14:16 UTC,"CORRECTION: Apologies, I just realised (when attempting to modify su-to-root)
that lxsudo(1) & friends can only become superuser ""root""; an arbitrary user
is not supported.  Despite the name, su-to-root can become an arbitrary user;
i.e., it is not restricted to superuser ""root"".  Hence, at least in Cosmic,
su-to-root ""cannot"" use lxsudo &tc."
1823714,2019-04-23 09:08:23 UTC,"Hi Jon,"
1823714,2019-04-08 12:21:16 UTC,Please can you add the full version information from About KiCad -> Copy Version Info
1823714,2019-04-08 12:58:26 UTC,"Application: kicad
Version: (5.1.0-181-ge35d056e8), debug build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 GnuTLS/3.5.8 zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Platform: Linux 4.19.27-mt x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010"
1823714,2019-04-13 13:15:42 UTC,A short video would help to understand the problem.
1823714,2019-04-20 02:46:56 UTC,"Hi Martin,
I can't reproduce this on the latest code.
Can you still see this bug on the latest nightly?"
1823715,2019-05-31 14:34:17 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/662484"
1823715,2019-05-28 16:10:41 UTC,"Reviewed:  https://review.opendev.org/655407
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=3af381003e8ae78f56cae81a58dbc641c23485ee
Submitter: Zuul
Branch:    master"
1823715,2019-04-24 11:09:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655408"
1823715,2019-09-19 10:09:55 UTC,This issue was fixed in the openstack/networking-ovn 7.0.0.0b1 development milestone.
1823715,2019-04-15 13:14:16 UTC,"Reviewed:  https://review.openstack.org/652040
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=da94db44d97fa68bc637032a9f7a2d52fa34df28
Submitter: Zuul
Branch:    master"
1823715,2019-04-12 10:50:02 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/652040"
1823715,2019-05-31 21:54:33 UTC,"Reviewed:  https://review.opendev.org/655408
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=6ef5489cf70cbc140a8768727350a8556fc8e870
Submitter: Zuul
Branch:    master"
1823715,2019-04-24 11:09:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655407"
1823715,2019-06-03 08:15:05 UTC,"Reviewed:  https://review.opendev.org/662484
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=b9af1a1c4cbdf497dadaaa275405ad500df6c9cc
Submitter: Zuul
Branch:    master"
1823716,2020-01-20 09:17:01 UTC,"Hi Sapna,"
1823716,2019-04-11 05:42:07 UTC,"# DEPRECATED:
# This option specifies the URL for connecting to Neutron.
#
# Possible values:
#
# * Any valid URL that points to the Neutron API service is appropriate here.
#   This typically matches the URL returned for the 'network' service type
#   from the Keystone service catalog.
#  (uri value)
# This option is deprecated for removal since 17.0.0.
# Its value may be silently ignored in the future.
# Reason: Endpoint lookup uses the service catalog via common keystoneauth1
# Adapter configuration options. In the current release, ""url"" will override
# this behavior, but will be ignored and/or removed in a future release. To
# achieve the same result, use the endpoint_override option instead.
#url=http://127.0.0.1:9696"
1823716,2019-04-08 13:15:39 UTC,And the same also for compute node
1823716,2020-01-19 16:04:01 UTC,"@Slawek, @LIU, is this bug still needs to be fixed?
Shall I create a patch for this?"
1823716,2019-04-08 12:42:07 UTC,"Are You talking about ""neutron"" section in https://docs.openstack.org/neutron/rocky/install/controller-install-rdo.html#configure-the-compute-service-to-use-the-networking-service ?"
1823716,2019-04-08 13:14:08 UTC,Yes sorry: I meant [neutron] section of nova.conf
1823718,2019-12-19 12:42:01 UTC,"Change abandoned by James Page (<email address hidden>) on branch: master
Review: https://review.opendev.org/667929
Reason: libmaas py37 incompatibility was resolved in distro - this review is no longer required."
1823718,2019-07-29 13:59:30 UTC,"The verification of the Stable Release Update for python-libmaas has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823718,2019-07-29 13:59:25 UTC,This bug was fixed in the package python-libmaas - 0.6.0-0ubuntu2
1823718,2019-07-23 09:36:40 UTC,"# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 19.04
Release:	19.04
Codename:	disco
# apt install python3-libmaas (expect failure)
[ snip ]
dpkg: error processing package python3-libmaas (--configure):
 installed python3-libmaas package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 python3-libmaas
E: Sub-process /usr/bin/dpkg returned an error code (1)"
1823718,2019-07-22 11:12:55 UTC,"On Mon, 22 Jul 2019 at 11:56, Łukasz Zemczak <email address hidden>
wrote:"
1823718,2019-07-22 10:45:31 UTC,"From the description I assume this is only an internal module, not part of the public API, right? Since we wouldn't want to break any existing applications, if anything."
1823718,2019-07-18 10:53:32 UTC,Attached debdiff should fix this
1823718,2019-07-22 10:46:03 UTC,"Hello Frode, or anyone else affected,"
1823718,2019-06-27 16:34:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823718,2019-06-27 14:01:54 UTC,"Marking as fix released, as this has been fixed in eoan. The fix and/or new upstream needs to be backported."
1823718,2019-04-10 19:16:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823718,2019-04-08 15:21:16 UTC,This issue appears to be fixed in the upstream git repository but has not been released.
1823718,2019-04-08 15:19:31 UTC,https://github.com/maas/python-libmaas/commit/585a85ac9b93156e074702de05c56761ed09b9b9
1823718,2019-04-08 12:53:56 UTC,"Note that ``python3-libmaas`` is a dependency of ``charm-hacluster``, which means HA deployments of Ubuntu OpenStack are currently not possible on Ubuntu Disco."
1823718,2019-07-17 20:22:14 UTC,This issue is blocking general OpenStack Stein validation and backports due to the requirement to validate in disco distro ahead of the Ubuntu Cloud Archive.
1823721,2020-03-22 06:00:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823722,2019-05-06 12:17:25 UTC,"Hello Olivier, or anyone else affected,"
1823722,2019-06-03 09:13:58 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823722,2019-06-03 09:13:38 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1~19.04.1
1823722,2019-05-14 14:33:39 UTC,"@Olivier: mutter is fixed, which is what the verification is about. (Your change would block the pending mutter SRU from being moved to -updates.)"
1823722,2020-04-09 09:32:23 UTC,"It's finally fixed with language-pack-fr/focal,focal,now 1:20.04+20200407 all
on focal."
1823722,2019-05-14 12:32:18 UTC,The problem is still present on my disco after apply disco-proposed updates
1823722,2019-05-06 13:21:19 UTC,"Test case verified, which means that the build succeeded in the sense which applies to this bug report."
1823722,2019-05-01 15:38:54 UTC,"Ok, I ""SRUified"" it. Dropped the Ubuntu MP too."
1823722,2019-04-12 20:36:23 UTC,Submitted a Debian merge request too according to IRC conversation with Sebastien.
1823722,2019-05-01 13:14:55 UTC,"On 2019-05-01 11:13, Iain Lane wrote:

> Gunnar / Marco, could one of you please SRUify this bug? It's going
> to be included in the upload (backport from eoan).
"
1823722,2019-05-01 11:34:41 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1
1823722,2019-05-01 09:13:07 UTC,"Gunnar / Marco, could one of you please SRUify this bug? It's going to be included in the upload (backport from eoan)."
1823722,2019-04-14 14:35:50 UTC,"I've uploaded that to experimental, thanks!"
1823722,2019-04-10 10:09:14 UTC,"The strings come from mutter and it seems an issue with the template generation in launchpad, from the build log
https://launchpadlibrarian.net/418511049/buildlog_ubuntu-disco-amd64.mutter_3.32.0-1ubuntu2_BUILDING.txt.gz"
1823722,2019-04-08 13:49:20 UTC,"Those are translated in gsettings-desktop-schemas and can be translated, the issue there seems rather than the translations are not being used by the settings interface"
1823722,2019-05-01 13:50:17 UTC,"It'd be easier for me if the change could be accepted, even if it has no functional impact (that makes the SRU a straight backport). So to that end it'd be good to reassure the SRU team that this won't break anything."
1823725,2019-08-26 16:20:23 UTC,"This patch 993675a3100b (""packet: reset network header if packet shorter than ll reserved space"") landed in Bionic as part of a stable upstream update (bug 1835845) and has been released."
1823725,2019-04-08 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823725,2019-06-08 04:17:45 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1823725,2019-06-12 08:37:35 UTC,"This bug is still there, valid packets may be dropped with variable length protocols like IP tunnels for example. Any actions expected on my side?"
1823725,2019-06-12 09:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823725,2019-08-12 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1823725,2019-08-13 09:06:32 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823728,2019-05-22 21:29:22 UTC,"This is a duplicate of an old wishlist item, bug 1365693."
1823728,2019-04-09 14:48:25 UTC,"Hello Dan, you could do something like this now with a nightly sql script without too much trouble."
1823733,2019-05-11 22:06:18 UTC,"Also a link to development page should be available,so the user will be able to work issues and propose improvements."
1823733,2019-10-23 12:30:11 UTC,"If this interface allow to install plugins from Git, should be interesting to define the branch to install (master / development / stable). So, the user by default get the stable but could should to install the beta plugin."
1823733,2019-05-11 18:21:33 UTC,"I think this is a great feature to add. I think It should actually be expanded to a ""plugin/script manager/store"". I think this should be one of the core tools in the toolbar of the main KiCad window, not an external tool maintained only for one platform as mentioned above. I also don't think it should be only Python scripting specific. There are other tools out there that are not python scripts and would be useful to have access to through the ""KiCad Store""."
1823733,2019-05-08 16:30:35 UTC,This package appear to be related https://pypi.org/project/kipi/
1823734,2019-05-13 11:49:38 UTC,"I believe that this was a temporary blip in the repositories. While we might be able to better handle such situations, I don't know that this is an actionable bug."
1823737,2019-07-12 09:23:07 UTC,"Mark it as ""invalid"" because the current design makes sense and do not require a fix to change the behavior."
1823737,2019-04-08 17:28:41 UTC,"Marking as release gating for now; lower priority, but would be nice to clean this up.
For background and consulting, contact <email address hidden>"
1823737,2019-07-04 11:10:04 UTC,"No, this LP is related to the storage aspects of the system API; not the openstack API.  In the ""steps to reproduce"" section in the issue description I listed examples of which endpoints are affected:  ""volume groups, physical volumes, partitions, OSD, etc..."""
1823737,2019-07-03 02:43:44 UTC,Is the problem described in this bug the following?
1823737,2019-07-08 03:08:15 UTC,"Thank you very much for your answer, but I think this bug is not a problem."
1823739,2019-04-08 17:31:16 UTC,Marking as low priority / not gating as there is a concern about the churn required to address this. Will let Frank Miller review and comment accordingly.
1823741,2019-04-12 13:15:33 UTC,That's a relief!  I'll try again tomorrow.
1823741,2019-04-12 13:03:00 UTC,"They are nightly, I was just not remembering the time the build is triggered each night.  I put in my fixes after the build was already started, so unfortunately they won't be included until the next nightly."
1823741,2019-04-12 12:59:06 UTC,It looks like what I thought were nightly builds are not nightly builds at all.  So ignore my previous comment. I'll get back to you when I have the actual nightly build installed.
1823741,2019-04-12 12:53:30 UTC,"Hi Ron,
Your version 5.1.0-unknown-ca7aec2 does not include my latest fixes.
It looks like this was built an hour or so before my fixes went up, so it should be in the next one."
1823741,2019-04-13 15:22:41 UTC,"Jon, I've gone through and rerun every ERC that failed for me, I believe.  There were quite a lot of them, and they all seem to work fine now."
1823741,2019-04-12 01:28:18 UTC,"Hi Ron, can you please check again after df600fc (so tonight's nightly)"
1823741,2019-04-11 13:41:26 UTC,I forgot to add the new versioning info in my last post:
1823741,2019-04-11 13:17:09 UTC,"The fix has now shown up in the nightly build, but the ERC is extremely flaky with respect to hidden power/ground pins in components.  Sometimes it works, and sometimes it does not."
1823741,2019-04-08 15:39:21 UTC,"On 04/08/2019 10:22 AM, Jon Evans wrote:

> This should be fixed in the next build (after c07de84) -- please advise
> if it isn't.
>
> ** Changed in: kicad
>         Status: New => Fix Committed
>
> ** Changed in: kicad
>       Assignee: (unassigned) => Jon Evans (craftyjon)
>
> ** Changed in: kicad
>     Importance: Undecided => Medium
>
> ** Changed in: kicad
>      Milestone: None => 6.0.0-rc1
>


Cool!  Will do."
1823741,2019-04-08 14:58:50 UTC,"As an afterthought, it occurred to me to wonder if the netlists are affected by the same problem.  They are not.  A netlist generated today is identical to the one generated last week, and indicates that the hidden power/ground pins are connected correctly."
1823741,2019-04-12 12:48:14 UTC,"Yesterday I had checked about 30 or so schematics, Jon, with perhaps 2/3 of them passing ERC and 1/3 failing.  (That's just a general idea, not exact counts.)  I only rechecked 5 of them with last night's build.  4 that failed yesterday still fail today, and 1 that passed yesterday still passes.  It's probably of no use to you, but their URLs are:"
1823741,2019-04-08 15:22:45 UTC,This should be fixed in the next build (after c07de84) -- please advise if it isn't.
1823745,2019-05-15 14:29:32 UTC,"TRIAGE: This is technically a wishlist item, as cross-model relations are not explicitly supported for the OpenStack charms, but I've set it to medium as keystone might be a good charm to actually provide a cross-model relation on as it's key (!) to providing authn/authz in clouds."
1823748,2019-09-27 09:04:29 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1823748,2019-04-09 01:51:42 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651052"
1823748,2019-04-08 17:21:59 UTC,"Looking more closely, (C) and (D) are entirely different -- (C) is an interval in a fixed interval looping call, and (D) is the maximum number of times the code will check to see if a driver is ready (with a hard-coded 1 sec eventlet.sleep inside the loop).  So I think they'll need separate config opts."
1823748,2019-05-22 14:53:50 UTC,"Reviewed:  https://review.opendev.org/651052
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b0279f2080ea54a123a9249c7a1a8fb027909ce2
Submitter: Zuul
Branch:    master"
1823749,2019-04-08 19:27:49 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1823749,2019-06-08 04:17:53 UTC,[Expired for apturl (Ubuntu) because there has been no activity for 60 days.]
1823750,2019-06-22 10:37:24 UTC,Please don't switch a bug to Public Security (or Private Security) without first explaining why you suspect it represents a security vulnerability.
1823750,2019-07-04 09:47:42 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/669124"
1823750,2020-08-27 05:42:00 UTC,"Change abandoned by Rajat Dhasmana (<email address hidden>) on branch: master
Review: https://review.opendev.org/669124"
1823750,2020-08-27 16:02:43 UTC,Additional comments  http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-08-27-15.01.log.html
1823750,2020-08-27 16:22:57 UTC,"Hi,"
1823750,2020-08-27 16:39:42 UTC,"I'll answer myself here,"
1823750,2020-08-27 17:12:39 UTC,"Hi Goutham,"
1823750,2021-02-18 10:27:35 UTC,This issue was fixed in the openstack/cinder 18.0.0.0b1 development milestone.
1823750,2020-08-28 22:07:14 UTC,"Reviewed:  https://review.opendev.org/748493
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=090d903b707e0dd84c7cd68cf15476356ce5a83f
Submitter: Zuul
Branch:    master"
1823750,2020-09-28 22:26:58 UTC,"Reviewed:  https://review.opendev.org/669124
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d72f738c014fc76596d2f323e94cdb0e97116e71
Submitter: Zuul
Branch:    master"
1823750,2020-08-27 17:31:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/748493"
1823751,2019-04-08 17:15:44 UTC,Marking as release gating; removed inadvertently
1823751,2019-07-22 17:49:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672124"
1823751,2019-07-23 14:52:31 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672305"
1823751,2019-07-23 18:18:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672339"
1823751,2019-07-30 20:28:52 UTC,"Reviewed:  https://review.opendev.org/672124
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=56c534ad98dc8bf9206755bc97b3dc86961eee79
Submitter: Zuul
Branch:    master"
1823751,2019-07-30 20:33:41 UTC,"Reviewed:  https://review.opendev.org/672339
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=b6b8f645f78a7ad5d2b87efdd9f3a785f7352ab4
Submitter: Zuul
Branch:    master"
1823751,2019-07-30 20:53:23 UTC,"Reviewed:  https://review.opendev.org/672305
Committed: https://git.openstack.org/cgit/starlingx/metal/commit/?id=a03a1a51966768f8d912ec60910ddd44bb04fb41
Submitter: Zuul
Branch:    master"
1823755,2019-04-25 08:33:48 UTC,All tasks have been completed and the bug is being set to Fix Released
1823757,2019-04-08 15:53:07 UTC,https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/499257
1823757,2019-04-10 14:57:33 UTC,"On our side, this is working as implemented - the code handles malformed svgs properly, but logger.exception()'s which results in sentry alerts, the rationale being that we do want to know when someone tries to upload a malformed svg and why."
1823758,2019-04-09 10:30:42 UTC,"Ideally, when performing a release upgrade, we would have a mechanism in place which does hardware detection, and sees if there is a new driver series that might work for your GPU. Unfortunately, we have no such thing, and we rely on transitional packages, only when it is safe to do so."
1823758,2020-01-29 09:52:35 UTC,"It is false, transitional package are used even while the next branch would make the user unable to use the GPU due to nVidia dropping support for it."
1823760,2019-09-18 19:29:27 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.2.0 release.
1823760,2019-08-12 12:53:11 UTC,"Reviewed:  https://review.opendev.org/675070
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=520dd2a4cbca1579c2fd7cfd36b96f82d7bbc5e8
Submitter: Zuul
Branch:    master"
1823760,2019-08-14 17:07:25 UTC,"Reviewed:  https://review.opendev.org/675103
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=2cd9e44e66dbf83ce763cbe2d7bca1593b1bd891
Submitter: Zuul
Branch:    master"
1823760,2019-08-07 09:37:14 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/675070"
1823760,2019-08-07 12:16:16 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675103"
1823761,2019-04-11 12:09:25 UTC,That's a software-properties change right? (assuming the component was just wrongly selected and changing that)
1823761,2019-04-11 12:09:58 UTC,Could you make the bug SRU compliant (having the impact/test case/regression potential)
1823761,2019-05-04 01:40:47 UTC,"Hello Andrea, or anyone else affected,"
1823761,2019-05-20 12:40:38 UTC,"Hi Andrea,"
1823761,2019-05-20 15:10:35 UTC,"I've had 0.96.24.32.8 installed on bionic for some days, it works fine and the livepatch tab matches the design and work as expected (activate/desactivate the service, list applied changes, ...), I'm marking the SRU as verified"
1823761,2019-05-21 15:24:56 UTC,This bug was fixed in the package software-properties - 0.96.24.32.8
1823761,2019-05-21 15:25:03 UTC,"The verification of the Stable Release Update for software-properties has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823764,2019-05-14 07:19:34 UTC,"Hi Eric,"
1823768,2020-07-20 11:52:24 UTC,This should have been fixed a while ago adressing some other area. The relevant code was related to alases.
1823770,2019-04-08 17:29:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823772,2019-04-08 17:25:35 UTC,"date from nagios as in same Nagios server with two different ips. As 10.20.176.22 is public IPs and
192.168.100.16 on private network."
1823772,2020-01-31 12:16:16 UTC,"The issue is that here we set `address` to the relation's target-address:
https://git.launchpad.net/nagios-charm/tree/hooks/monitors-relation-changed#n131"
1823776,2019-05-14 09:03:34 UTC,This bug was fixed in the package livecd-rootfs - 2.208.17
1823776,2019-05-09 11:16:15 UTC,This bug was fixed in the package livecd-rootfs - 2.408.45
1823776,2019-05-09 11:06:15 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823776,2019-05-06 16:03:27 UTC,"https://launchpad.net/~canonical-foundations/+livefs/ubuntu/xenial/ubuntu-cpc/+build/164716 is a successful image build using the livecd-rootfs from xenial-proposed and the ubuntu-cpc project, which exercises the code path changed in this SRU."
1823776,2019-05-06 18:39:06 UTC,"https://launchpad.net/~canonical-foundations/+livefs/ubuntu/trusty/ubuntu-cpc/+build/164730 is an image build using the livecd-rootfs from trusty-proposed.  It fails to build, with an error unrelated to the SRU in question and which is a preexisting failure (as seen at https://launchpad.net/~canonical-foundations/+livefs/ubuntu/trusty/ubuntu-cpc/+build/164732, a build without trusty-proposed enabled).  The failure also happens at a point in the build past the point in the code that has been changed by the SRU (the failure is during a binary hook, the SRU change is to a chroot hook, all chroot hooks are executed before all binary hooks)."
1823776,2019-04-30 22:02:34 UTC,"Hello Steve, or anyone else affected,"
1823776,2019-04-09 19:20:34 UTC,Fixed in livecd-rootfs 2.525.20 for bionic.
1823776,2019-04-30 22:04:08 UTC,"Hello Steve, or anyone else affected,"
1823778,2019-04-29 14:11:34 UTC,"wait, you did, nm"
1823778,2019-05-16 09:44:51 UTC,This bug was fixed in the package gnome-control-center - 1:3.28.2-0ubuntu0.18.04.4
1823778,2019-05-16 08:37:44 UTC,"The verification of the Stable Release Update for gnome-control-center has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823778,2019-05-16 08:37:41 UTC,This bug was fixed in the package gnome-control-center - 1:3.32.1-1ubuntu4.1
1823778,2019-05-09 00:56:13 UTC,"On 2019-05-09 01:08, Brian Murray wrote:

> Could you add the workaround to the bug description just in case
> anyone on Cosmic stumbles upon this?
"
1823778,2019-05-08 23:09:55 UTC,"Hello momcilo78, or anyone else affected,"
1823778,2019-05-08 23:08:41 UTC,Could you add the workaround to the bug description just in case anyone on Cosmic stumbles upon this?
1823778,2019-05-08 22:21:37 UTC,I installed gnome-control-center 1:3.32.1-1ubuntu4.1 from disco-proposed and verified the test case.
1823778,2019-05-08 21:46:36 UTC,"On 2019-05-08 23:09, Brian Murray wrote:

> Is there a reason this has not been targetted to and uploaded to the
> cosmic queue?
"
1823778,2019-05-08 21:09:56 UTC,Is there a reason this has not been targetted to and uploaded to the cosmic queue?
1823778,2019-05-08 21:01:39 UTC,"Hello momcilo78, or anyone else affected,"
1823778,2019-04-29 14:21:38 UTC,This bug was fixed in the package gnome-control-center - 1:3.32.1-1ubuntu5
1823778,2019-04-29 12:23:21 UTC,Thanks for this Gunnar. I'll upload. I do think that Matthias's comments upstream make sense though - presenting the modifiers directly does not look particularly great. It'd be good if we could address this somehow.
1823778,2019-04-29 14:11:25 UTC,"Uploaded for eoan and disco. bionic doesn't cherry-pick cleanly - Gunnar, can you prepare a branch please?"
1823778,2019-04-12 18:49:00 UTC,This bug was fixed in the package gnome-control-center - 1:3.32.1-1ubuntu4
1823778,2019-04-08 18:34:49 UTC,Little correction: the correct language packages for Croatian as a reference are here:
1823778,2019-04-08 18:45:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823778,2019-04-13 01:19:25 UTC,"I think I have fixed the rest, including the modifier issue affecting e.g. Serbian-Latin and Catalan-Valencia."
1823778,2019-04-08 22:43:48 UTC,"I can reproduce the problem. I also tried to install Catalan, which ought to result in two additional language options: Catalan and Catalan-Valencia. However, only Catalan shows up in the list of selectable languages in gnome-control-center."
1823778,2019-04-08 22:53:48 UTC,Related upstream issue:
1823778,2019-04-08 18:46:33 UTC,"I recovered my long-lost launchpad account, please change reporter the account posting this message."
1823778,2019-04-10 22:28:04 UTC,Accidentally I found one reason why the Serbian language is hidden in the gnome-control-center GUI. In the add_all_languages() function in panels/common/cc-language-chooser.c the upstream code includes a call for gnome_get_all_locales(). That call is replaced by a call for gnome_get_all_languages() via ubuntu-region-langpack-install.patch. So I have submitted a MP where I propose that we simply disable ubuntu-region-langpack-install.patch for now (that feature for installing languages doesn't work anyway).
1823778,2019-04-11 14:59:39 UTC,I uploaded a modified bionic package to a PPA:
1823778,2019-04-11 18:31:41 UTC,"@gunnarhj: works!
That was quick."
1823778,2019-04-11 20:10:20 UTC,"@momcilo: Great! It's not in the bionic archive yet, though. That will probably take a few weeks, since I'd like to also fix the problem with setting Serbian-Latin as language."
1823778,2019-04-09 21:32:26 UTC,"I checked panels/common/cc-common-language.c and found that all the installed languages (including the two Serbian ones) are passed to the insert_language() function, whose label_own_lang variable is assigned the corresponding label. Hence the GHashTable returned by cc_common_language_get_initial_languages() ought to include it all."
1823780,2019-04-08 19:00:06 UTC,This change was made by a bot.
1823780,2019-04-09 05:11:09 UTC,"Does it happen to previous kernel release, 4.15.0-46?"
1823780,2019-04-09 05:45:37 UTC,"I resolved it some how by going to recovery mode. The problem was that the
touchpad was not even showing in the xinput and also in proc. So I think
the kernel version may be responsible."
1823782,2019-04-09 18:26:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823782,2019-04-09 04:06:48 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1823782,2019-04-10 06:11:57 UTC,And also I have an error while installing the NetBeans IDE.
1823782,2019-04-14 08:24:21 UTC,I just experienced the same bug while installing updates. Here’s the information requested:
1823782,2019-04-10 14:20:30 UTC,"This seems to be the error:
Setting up samba-common (2:4.3.11+dfsg-0ubuntu0.14.04.20) ...
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
dpkg: error processing package samba-common (--configure):
 subprocess installed post-installation script returned error exit status 128"
1823782,2019-04-15 12:29:35 UTC,Unfortunately it's not the problem Andreas suspected then.
1823782,2019-06-15 04:17:33 UTC,[Expired for samba (Ubuntu) because there has been no activity for 60 days.]
1823784,2020-08-03 09:03:11 UTC,The issue confirmed in Evergreen 3.5.0 (https://demo.evergreencatalog.com/)
1823787,2019-07-31 15:14:04 UTC,looking at this on request - looks like this should have fixed it?
1823787,2019-07-31 19:20:22 UTC,"I agree, the above commit fixed the issue and it's appropriate to close this."
1823790,2020-09-20 18:06:15 UTC,"In my case the issue with using Ubuntu 20.04 as a container host appears to have come down to the use of the F, or ""fix binary"", flag by binfmnt_misc:"
1823790,2020-08-28 21:03:16 UTC,Could you try the attached patch?
1823790,2020-08-28 20:14:36 UTC,"SO_PEERGROUPS is not implemented and processed as an ""int"" (this explains the ERANGE)"
1823790,2020-08-27 16:54:27 UTC,"I can confirm that I see the same issue when trying to run Ubuntu 20.04 aarch64 in a container, strace shows a tight loop on:"
1823790,2020-08-24 16:24:44 UTC,"Hmm, I'm using qemu-5.1.0 and I'm still seeing this (host is bionic, container image is focal)"
1823790,2020-08-18 14:05:06 UTC,"Sorry, posted this on the wrong bug :-/
I beg your pardon for the noise."
1823790,2020-08-18 14:04:40 UTC,Bisect worked and once you find it it seems obvious that this is exactly our case:
1823790,2020-04-30 13:36:05 UTC,"Fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=6d485a55d0cd"
1823790,2020-02-20 12:21:29 UTC,This seems to be the error reported in https://bugs.launchpad.net/qemu/+bug/1857811
1823790,2020-02-20 06:56:35 UTC,Laurent's patch worked for me as well.
1823790,2020-02-08 12:03:59 UTC,"Well, it's kind of irrelevant but I am trying that on archlinux and this does not work for me."
1823790,2020-02-04 12:51:07 UTC,I carried out the following test:
1823790,2020-02-03 13:54:03 UTC,"> Could you test the attached patch?
>
"
1823790,2020-02-03 08:07:26 UTC,"Thanks, Laurent! I'll get back to you, asap."
1823790,2020-01-31 20:51:51 UTC,Could you test the attached patch?
1823790,2020-01-29 06:20:57 UTC,"I'm a bit surprised that this bug doesn't get more attention, as it makes it very hard to run qemu-emulated containers of Bionic hosted on Bionic. Running such containers is a common way to cross-compile packages for foreign architectures in the absence of sufficiently powerful target HW."
1823790,2019-08-16 09:05:08 UTC,"I patched linux-user/syscall.c (see below, branch stable-2.11) which works around my problem.
So far so good, but the qemu-arm that i compiled is terribly slow compared to the one that came with Ubuntu 18.04. Any hints?
I configured as this:
./configure --static --enable-kvm --target-list=arm-linux-user"
1823790,2019-08-16 06:46:16 UTC,I filed the duplicate #1840252 of this bug.
1823790,2019-04-11 20:52:52 UTC,"I have just studied a bit the systemd code and this brought me to the following idea/temporary workaround: What about returning -1 (error) and setting errno when getsockopt(fd, SOL_SOCKET, SO_PEERSEC, ...) gets called? This would then let systemd know that SO_PEERSEC is not (yet) implemented."
1823790,2019-04-11 20:36:38 UTC,"This is probably the tight loop that gets triggered:
https://github.com/systemd/systemd/commit/217d89678269334f461e9abeeffed57077b21454"
1823790,2019-04-09 13:26:34 UTC,"As described on the systemd issue, the syscall we're getting wrong here is getsockopt(fd, SOL_SOCKET, SO_PEERSEC, ...). Our linux-user/syscall.c:do_getsockopt() doesn't have any special case code for the payload on this function, so we treat it as if it were just an integer payload, which is not correct here."
1823795,2019-08-02 19:22:24 UTC,Also merge/group graphical elements to be locked (as asked here lp:1837771).
1823795,2019-04-08 21:28:28 UTC,I find it's also a bit too easy to move zone fills by accident when working near the edges of them.
1823795,2019-04-08 21:40:32 UTC,"That's true as well, doesn't happen nearly as often for me but should definitely be included. Text in silk is also a case where it happens for me"
1823795,2019-04-08 23:52:54 UTC,"Me too.  Let's fix this.  How about we allow the locked flag on any element?  In the course of fixing this, I'd like to allow multiple select modes:"
1823795,2019-04-09 08:30:44 UTC,@Seth: I think a locked flag on every element is a good idea. I can see it could be useful on nearly every element (nearly anything could be hard design requirement w.r.t. board location). Also probably is easier from a consistency PoV.
1823795,2019-05-21 12:18:53 UTC,"Could be also interesting lock the full layer at the right panel. This cover the case of move edge-cuts (or tracks when we are just re-positing silks, ...)."
1823797,2020-05-07 22:49:26 UTC,I don't know if this is fixed or invalid or whatever but this whole feature is gone now so the bug is definitely closed!
1823797,2019-04-09 09:55:32 UTC,"For the record, I've been hit by this bug while working at"
1823797,2019-04-16 14:13:27 UTC,"The problem affects serial terminals, and the reason is that serial getty it not configured for automatic login unlike regular getty."
1823797,2019-04-09 09:52:31 UTC,"I'm not sure if related, but while booting the following error message is printed:"
1823801,2019-04-08 22:04:12 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9724"
1823801,2019-04-11 20:39:11 UTC,Revised the Behat script to include all of the following
1823801,2019-06-06 02:27:30 UTC,Revised the Behat script to include.
1823801,2019-11-23 20:05:02 UTC,"Reviewed:  https://reviews.mahara.org/9724
Committed: https://git.mahara.org/mahara/mahara/commit/939cdaa8bfc495d169f45a67f4b9d666d7c30e3d
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1823803,2019-06-05 00:25:44 UTC,"Reviewed:  https://review.opendev.org/659464
Committed: https://git.openstack.org/cgit/starlingx/upstream/commit/?id=6a341bbb5e9adde2e81b52abd0905cfd987f0eab
Submitter: Zuul
Branch:    master"
1823803,2019-04-15 17:41:38 UTC,Marking as release gating; high priority given the system becomes unusable after 10 hours.
1823803,2019-05-14 04:27:08 UTC,"I reproduced this issue with my deployment, simplex(two Intel(R) Xeon(R) Gold 6139 + 192G memory). There are three ingress controller pods. In each pod, there are one ngnix master process and 72 worker processes. In total, all nginx processes in the three pods consumed ~8G memory. I am working on a patch to modify nginx configuration."
1823803,2019-05-16 06:51:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659456"
1823803,2019-05-16 07:07:51 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659464"
1823803,2019-05-16 11:27:53 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659533"
1823803,2019-05-31 13:56:46 UTC,"Reviewed:  https://review.opendev.org/659456
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=f6e7130cabfd85697fd46ed345bbf220b5601360
Submitter: Zuul
Branch:    master"
1823803,2019-06-05 00:55:26 UTC,"Reviewed:  https://review.opendev.org/659533
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=6dfb75be644af97f75ca394aa46970c6550ed4aa
Submitter: Zuul
Branch:    master"
1823805,2019-05-14 22:58:16 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823805,2019-05-14 19:04:29 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18
1823805,2019-04-09 13:58:13 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/099939.html
1823805,2019-05-14 22:55:23 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18~18.04.1
1823805,2019-04-09 01:50:25 UTC,"The reason this missing commit is now causing a panic is because it Fixes the following commit, which is added by 4.18.0-1015:"
1823805,2019-04-09 02:19:33 UTC,"And looking a little further, commit ae6935ed7d42(Bionic commit c40598d9e67c) was added per bug 1812123 for DPDK.  In that bug, we requested two commits:"
1823808,2019-06-25 17:06:52 UTC,"Tee - can you please re-test this issue and update the book, thank you!"
1823808,2019-06-27 00:33:16 UTC,"Tee, thanks for the update. Then I am going to close this bug."
1823808,2019-06-26 20:17:25 UTC,"Had some hiccups installing the stx-openstack app in this lab as the original tarball copied to this lab by the installer did not have a cinder chart fix. After removing the app and reapplying using the latest tarball, the overall memory consumption showed a moderate climb of ~5% (from 62.5% - 67.6%) over the course of 3.5 hours. However, the memory consumptions of both baremetal and containerized rabbitmq have remained steady ~100M and ~200M respectively."
1823808,2019-06-25 21:43:00 UTC,"Just installed the latest load in the same lab, will soak it overnight without the stx-openstack app and start monitoring memory consumption after the stx-openstack app is applied tomorrow morning."
1823808,2019-06-25 17:07:13 UTC,"Whoops - I meant bug, not book :)"
1823808,2019-05-29 01:56:10 UTC,Sorry I have been occupied with higher priority issues. I have not had the opportunity to check if it is still reproducible in a recent build. Will try later this week.
1823808,2019-04-15 17:35:15 UTC,Marking as release gating; high priority given the system becomes unusable within 10 hours due to the memory growth
1823808,2019-05-10 01:50:25 UTC,"Tee,"
1823808,2019-05-03 16:48:09 UTC,"As Tee reported, an increase in rabbitmq contribute with the OOM problem, in #1826308 a high number of nova-schedulers which is not directly related with this one."
1823808,2019-04-26 00:39:00 UTC,please check https://bugs.launchpad.net/starlingx/+bug/1826308 if it's related.
1823808,2019-04-15 17:37:38 UTC,The focus of the investigation should be on identifying and addressing the rabbitmq memory leak. It's unlikely that this is an upstream rabbitmq issue. It's likely that there are stale queues that are not being processed resulting in the memory growth.
1823808,2019-05-28 08:23:09 UTC,"Tee, any updates from your side?"
1823809,2019-04-10 19:37:57 UTC,The text on the buttons are too long - would be better to change this to work like 'Add page' button with modal popup
1823809,2019-05-23 04:09:40 UTC,"The listing of pages and collections stays and each entry gets a copy button, which brings up a modal allowing you to select page or collection."
1823811,2019-08-01 19:28:19 UTC,"Hi Derek,
Our forums are our primary place for support. If you are still having this issue please submit a debug log."
1823811,2019-08-03 00:33:29 UTC,Here's the debug log.
1823818,2019-04-09 10:35:39 UTC,"And in the meantime, for the kolla side I filled https://bugzilla.redhat.com/show_bug.cgi?id=1697925 to track it for Rocky RDO (other branches are not impacted)"
1823818,2019-04-11 01:43:43 UTC,Great thanks!
1823818,2019-04-09 07:54:40 UTC,The linked RH bugzilla bug suggests that the OVS fix is included in v2.11.0. The kolla image just installs these packages:
1823818,2019-04-09 09:51:01 UTC,"It looks like this is really same issue as in https://bugzilla.redhat.com/show_bug.cgi?id=1667007 so it's not direclty issue in neutron but in openvswitch.
I will then mark it as invalid for neutron but feel free to change it if that would be different issue."
1823819,2019-04-09 01:00:08 UTC,This change was made by a bot.
1823819,2019-04-09 01:03:13 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1823823,2019-05-29 01:16:25 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10052"
1823823,2019-06-12 21:40:34 UTC,"Reviewed:  https://reviews.mahara.org/10052
Committed: https://git.mahara.org/mahara/mahara/commit/dcdc8a2847790346023adc8d265776ef2b835794
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1823825,2019-04-10 14:35:33 UTC,"Change abandoned by Boxiang Zhu (zhu.boxiang@99cloud.net) on branch: master
Review: https://review.openstack.org/649953"
1823825,2019-04-09 03:56:56 UTC,"Add the review link:
https://review.openstack.org/#/c/649953"
1823825,2019-04-10 14:45:49 UTC,"Add the review link:
https://review.openstack.org/#/c/649963/"
1823825,2019-04-09 03:29:23 UTC,"A same bug is found here https://bugs.launchpad.net/mos/+bug/1735407.
It has been set 'Fix Released'. And you can find the patch here https://review.openstack.org/#/c/525242/"
1823830,2019-04-09 04:27:57 UTC,"After re-deploying everything with the exact same sequence of commands, still not Internet access. The virtual public's network gateway is 10.0.2.1 and it also can't be pinged. The further it goes is the router's interface on the public interface (10.0.2.198 currently)."
1823830,2019-04-09 08:02:41 UTC,"Igor, when you say you lose internet access, do you mean from the machine running the all in one deployment, or one of the VMs running on it, or both?"
1823830,2019-04-10 22:21:51 UTC,"I mean both the VMs and the router namespaces that are their gateways to the internet, lose access to the Internet. Not just the real internet, but also the default public network gateway on the host (10.0.2.1)."
1823830,2019-04-11 07:00:01 UTC,"This can be hard to debug, but perhaps you can try checking ping and the route table (ip route) at various points to see what changes. You can check the neutron routers by entering the network namespace, ip netns exec <namespace> <command>."
1823830,2019-06-17 16:48:03 UTC,Can no longer reproduce this issue on a development installation for ubuntu/stein/source. Closing bug.
1823831,2020-05-12 19:26:25 UTC,"Yes, I've verified. It boots after countdown and responds to keyboard events."
1823831,2019-04-10 07:14:29 UTC,Git bisect shows that 92d5f1a4147c3722b5e9a8bcfb7dc261b7a8b855 is the first bad commit.
1823831,2019-04-10 10:17:49 UTC,"In good versions (27e18b8952f8b7a1e26350846f8a0d5a9b33bfb8), calls to x86_cpu_has_work(), likely due to IRQ 0, returned interchanging true or false."
1823831,2020-05-12 13:08:43 UTC,"Hi Chen,"
1823835,2019-05-22 06:59:00 UTC,"Reviewed:  https://review.opendev.org/651773
Committed: https://git.openstack.org/cgit/openstack/tacker-horizon/commit/?id=4f37772919b26f2689ca0e69866f3cd94772a79b
Submitter: Zuul
Branch:    stable/stein"
1823835,2019-04-11 12:32:07 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.openstack.org/651773"
1823835,2019-04-09 09:08:16 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/651146"
1823835,2019-04-11 11:18:03 UTC,"Reviewed:  https://review.openstack.org/651146
Committed: https://git.openstack.org/cgit/openstack/tacker-horizon/commit/?id=d27287d4aa3554ebc9b6d0c6a7fd77cf861549da
Submitter: Zuul
Branch:    master"
1823836,2019-05-09 06:19:08 UTC,"Interesting, thanks Brian for the hint.
Let me check what went wrong ..."
1823836,2019-04-25 06:51:26 UTC,Since the fixes will be in rdma-core add a task for that as well.
1823836,2019-04-26 07:47:34 UTC,FYI: Currently a lot of packages are building and testing against eoan which makes this process slower than usual. Once migrated there I can upload it for the SRU teams review.
1823836,2019-04-26 14:20:45 UTC,This bug was fixed in the package rdma-core - 22.1-1ubuntu1
1823836,2019-04-29 05:09:57 UTC,"The update to the latest dev release Eoan is complete, lets fix the affected Disco release as well.
I uploaded the same change, but for Disco for the SRU Team to consider it."
1823836,2019-05-08 21:20:39 UTC,"An upload of rdma-core to disco-proposed has been rejected from the upload queue for the following reason: ""Your source.changes file contains changes for more than the version you intended, please reupload it. https://launchpadlibrarian.net/421428873/rdma-core_22.1-1ubuntu0.1_source.changes""."
1823836,2019-05-09 08:12:00 UTC,"Checking:
- Disco (which the upload is for) is at rdma-core 22.1-1
- The upload was a proper 22.1-1ubuntu0.1 with just the fix on top
- The MP and git branch only has the fix (d/p/lp-1823836-clear-cmd-buffer.patch)
- Here is the issue, the .changes file contained all version history mentioned back until 15-1 (first version)
- if I run dpkg-buildpackage again the .changes is generated correctly (just the last fix as intended)
- TBH I'd not even know how I'd make the broken .changes file, if I add -v15-1 that version would be missing and if I add an empty -v it refuses to build.
- Only something like -v0 or so would do, maybe by accident I fetched something with a lower version from bash history by accident
- :-/ I might not find what happened, but a fix is easy - rebuild and re-upload
- The content was already right, just the too long .changes history"
1823836,2019-04-23 23:31:59 UTC,Now (re-)building at https://launchpad.net/~paelzer/+archive/ubuntu/bug-1823836-rdma-core-mem-clear/+build/16681326
1823836,2019-05-09 12:13:14 UTC,"@David - could you verify the version in Disco proposed with your setup please?
It should be the same result that we had with the PPA before."
1823836,2019-05-10 17:09:52 UTC,"------- Comment From <email address hidden> 2019-05-10 13:03 EDT-------
(In reply to comment #40)

> @David - could you verify the version in Disco proposed with your setup
> please?
> It should be the same result that we had with the PPA before.
"
1823836,2019-05-10 17:20:29 UTC,"------- Comment From <email address hidden> 2019-05-10 13:11 EDT-------
(In reply to comment #41)

> (In reply to comment #40)
> > @David - could you verify the version in Disco proposed with your setup
> > please?
> > It should be the same result that we had with the PPA before.
>
> Verification complete.
>
> I tested libibverbs1 version 22.1-1ubuntu0.1 from Disco Purposed,  I found
> the issue was successfully resolved with this update.
>
> Description of test:
> Rad testpmd on a ppc64le system with a Mellanox Technologies MT28800 Family
> [ConnectX-5 Ex] adapter,  the pmd correctly initialised the adapter with no
> errors.  This was failing prior to upgrading libibverbs.
>
> Thanks
"
1823836,2019-05-10 17:31:18 UTC,tags adjusted - thx David
1823836,2019-05-20 09:15:43 UTC,This bug was fixed in the package rdma-core - 22.1-1ubuntu0.1
1823836,2019-05-20 09:15:49 UTC,"The verification of the Stable Release Update for rdma-core has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823836,2019-06-11 10:57:48 UTC,"------- Comment From <email address hidden> 2019-06-11 06:38 EDT-------
IBM Bugzilla Status -> Fix Released for requested distro"
1823836,2019-05-09 11:34:30 UTC,"Hello bugproxy, or anyone else affected,"
1823836,2019-04-23 23:29:34 UTC,"arr - I mis-clicked powerpc instead of ppc64el, I will re-build it.
If only I could change my personal default to always have ppc64el and s390x enabled ..."
1823836,2019-04-12 22:19:41 UTC,"------- Comment From <email address hidden> 2019-04-12 18:13 EDT-------
I upgraded a built the following packages, I am continuing to see the same error with the new versions."
1823836,2019-04-23 07:39:11 UTC,Thanks for the Checks David!
1823836,2019-04-23 18:39:40 UTC,"------- Comment From <email address hidden> 2019-04-23 14:31 EDT-------
(In reply to comment #29)

> Thanks for the Checks David!
>
> This is tagged as being in v23 and Debian/experimental is already at v24.
> So mid term this will be resolved by a re-sync of a latter version.
> But for now we will need an Ubuntu Delta to fix it.
>
> Eoan isn't fully open yet, but we can prep SRU template, PPAs and MPs to
> review to get that already out of the way.
>
> An MP is opened at [1] and the respective MR is at [2].
>
> Until 19.10 is fully ready for development this might take a bit, but you
> should be able to use the PPA as needed until then.
>
> [1]:
> https://launchpad.net/~paelzer/+archive/ubuntu/bug-1823836-rdma-core-mem-
> clear/+packages
> [2]:
> https://code.launchpad.net/~paelzer/ubuntu/+source/rdma-core/+git/rdma-core/
> +merge/366380
"
1823836,2019-04-09 05:09:29 UTC,Default Comment by Bridge
1823836,2019-04-10 00:19:19 UTC,"------- Comment From <email address hidden> 2019-04-09 20:09 EDT-------
-EOPNOTSUPP is returned from ib_uverbs kernel module."
1823836,2019-04-10 12:24:34 UTC,"Hi David,
I added Thomas here as he knows Mellanox HW well and might know the case and/or someone who knows."
1823836,2019-04-10 12:52:56 UTC,"10/04/2019 14:24, Christian Ehrhardt :

> Hi David,
> I added Thomas here as he knows Mellanox HW well and might know the case and/or someone who knows.
>
>
> I realize that this is occurring on ppc64 - which recently was not very well maintained upstream
>  - gowrishankar became unavailable, Chao Zhu has had quite some other work - so I'm wondering if this might be ppc64 specific.
> Do you - by any chance - know if this can be reproduced on x86 or if it might be ppc64 specific?
"
1823836,2019-04-10 16:49:22 UTC,"------- Comment From <email address hidden> 2019-04-10 12:47 EDT-------
(In reply to comment #15)

> 10/04/2019 14:24, Christian Ehrhardt ?:
> > Hi David,
> > I added Thomas here as he knows Mellanox HW well and might know the case and/or someone who knows.
> >
> >
> > I realize that this is occurring on ppc64 - which recently was not very well maintained upstream
> >  - gowrishankar became unavailable, Chao Zhu has had quite some other work - so I'm wondering if this might be ppc64 specific.
> > Do you - by any chance - know if this can be reproduced on x86 or if it might be ppc64 specific?
>
> It seems to be mlx5_glue_create_rwq_ind_table which is unsupported
> with the version of libibverbs installed on the machine.
> Which version of rdma-core is it?
"
1823836,2019-04-10 18:08:19 UTC,"10/04/2019 18:49, bugproxy:

> ------- Comment From <email address hidden> 2019-04-10 12:47 EDT-------
> (In reply to comment #15)
> > 10/04/2019 14:24, Christian Ehrhardt ?:
> > > Hi David,
> > > I added Thomas here as he knows Mellanox HW well and might know the case and/or someone who knows.
> > >
> > >
> > > I realize that this is occurring on ppc64 - which recently was not very well maintained upstream
> > >  - gowrishankar became unavailable, Chao Zhu has had quite some other work - so I'm wondering if this might be ppc64 specific.
> > > Do you - by any chance - know if this can be reproduced on x86 or if it might be ppc64 specific?
> >
> > It seems to be mlx5_glue_create_rwq_ind_table which is unsupported
> > with the version of libibverbs installed on the machine.
> > Which version of rdma-core is it?
>
> Hi Thomas
>
> I have not tried this on x86.  Agreed it could be a ppc64le issue :)
>
> # apt list libibverbs*
> Listing... Done
> libibverbs-dev/disco,now 22.1-1 ppc64el [installed]
> libibverbs1-dbgsym/disco,now 22.1-1 ppc64el [installed]
> libibverbs1/disco,now 22.1-1 ppc64el [installed,automatic]
>
> I am not sure what you mean by mlx5_glue_create_rwq_ind_table which is
> unsupported.  Are you saying that dpdk 18.11 is not supported on this
> version of libibverbs?
"
1823836,2019-04-12 17:09:46 UTC,"------- Comment From <email address hidden> 2019-04-12 13:01 EDT-------
(In reply to comment #22)

> Ok, once my setup was fixed it worked fine.
> By any chance are your FW levels up to date?
> For your card that should be:
> ConnectX-5: 16.21.1000 and above.
> ConnectX-5 Ex: 16.21.1000 and above.
>
> You can run ibv_devinfo to get what you currently have.
> $ sudo ibv_devinfo
>
> If it is not your FW, we are back to my suggestion to file this with
> the infiniband/dpdk/mellanox folks to get their experience as well.
>
"
1823836,2019-04-11 06:11:33 UTC,"To document the versions used, he is on Ubuntu 19.04 which means we should talking about:
DPDK: 18.11-6 (latest LTS)
rdma-core (all ib things): 22.1-1
This matches ther versions mentioned in the comments before."
1823836,2019-04-10 19:39:43 UTC,"------- Comment From <email address hidden> 2019-04-10 15:31 EDT-------

> I'm not an expert of libibverbs.
> Please forward to Mellanox experts.
"
1823836,2019-04-18 21:59:44 UTC,"------- Comment From <email address hidden> 2019-04-18 17:51 EDT-------
(In reply to comment #27)"
1823836,2019-04-18 05:43:01 UTC,"Thanks for that check David, that is good news to finally get a hold on this."
1823836,2019-04-12 07:52:30 UTC,"> ------- Comment From <email address hidden> 2019-04-11 12:22 EDT-------
>. Can we agree to limit the discussion to this bug?
"
1823836,2019-04-11 16:29:35 UTC,"------- Comment From <email address hidden> 2019-04-11 12:22 EDT-------
----- Comment From paelzer 2019-04-11 12:22:31 UTC-------

> Sorry for the off topic post, lets keep the bug to the error you reported.
> I'll probably start a discussion for the general PPC64-DPDK status via mail
> and keep you and others I know being involved in the loop.
"
1823836,2019-04-11 07:13:08 UTC,"Sorry for the off topic post, lets keep the bug to the error you reported.
I'll probably start a discussion for the general PPC64-DPDK status via mail and keep you and others I know being involved in the loop."
1823836,2019-04-17 22:29:39 UTC,"------- Comment From <email address hidden> 2019-04-17 18:20 EDT-------
(In reply to comment #24)

> I upgraded a built the following packages, I am continuing to see the same
> error with the new versions.
>
> kernel 5.0.7-stable
> dpdk-19.02
> rdma-core (master branch,  commit 4bb3583c228566958e2c6f34392c9e39e799bacf)
"
1823836,2019-04-11 07:08:06 UTC,"TBH - I was even considering to drop ppc64 builds from the next Ubuntu release for the unreliable support in the last year. It seems the overall community feels that way as well reading [1], if you work on getting it into proper support (add ppc CI to the project, run tests regular, ensure all supported HW runs, ...) I'd highly appreciate that."
1823843,2019-07-16 15:40:30 UTC,This bug was fixed in the package kylin-nm - 1.0.0-1ubuntu0.1
1823843,2019-07-16 01:43:28 UTC,kylin-nm 1.0.0-1ubuntu0.1
1823843,2019-07-16 15:40:37 UTC,"The verification of the Stable Release Update for kylin-nm has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823843,2019-04-22 07:53:28 UTC,This bug was fixed in the package kylin-nm - 1.0.2-0ubuntu1
1823843,2019-04-17 15:00:18 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1823843,2019-07-02 17:41:42 UTC,"Hello liumin, or anyone else affected,"
1823843,2019-07-15 07:14:44 UTC,What package version has been used during verification?
1823844,2019-04-17 15:00:16 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1823844,2019-04-22 07:53:28 UTC,This bug was fixed in the package kylin-nm - 1.0.2-0ubuntu1
1823844,2019-07-02 17:41:53 UTC,"Hello liumin, or anyone else affected,"
1823844,2019-07-16 15:40:30 UTC,This bug was fixed in the package kylin-nm - 1.0.0-1ubuntu0.1
1823844,2019-07-16 15:40:39 UTC,"The verification of the Stable Release Update for kylin-nm has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823845,2019-07-16 15:40:42 UTC,"The verification of the Stable Release Update for kylin-nm has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823845,2019-07-02 17:42:06 UTC,"Hello liumin, or anyone else affected,"
1823845,2019-04-10 03:12:25 UTC,需要做单例启动判断
1823845,2019-04-17 15:00:14 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1823845,2019-04-22 07:53:28 UTC,This bug was fixed in the package kylin-nm - 1.0.2-0ubuntu1
1823845,2019-07-16 15:40:30 UTC,This bug was fixed in the package kylin-nm - 1.0.0-1ubuntu0.1
1823846,2019-04-10 03:10:52 UTC,qt本身机制决定无法去掉这个任务栏窗口，去掉的话右键点击托盘的事件会有各种问题，或者点不开。取舍之下采用了这种方案。
1823849,2019-04-09 07:18:24 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/651115"
1823849,2019-04-09 06:50:15 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/651110"
1823849,2019-04-17 22:28:39 UTC,"Reviewed:  https://review.openstack.org/651110
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=2a734381fc9ff3f1e1e369d20f2bd4fdb62c1237
Submitter: Zuul
Branch:    stable/queens"
1823849,2019-04-17 22:28:30 UTC,"Reviewed:  https://review.openstack.org/651182
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=dc9a67ced5f8cca1bc26fe8ee0fec610f197db7e
Submitter: Zuul
Branch:    stable/queens"
1823849,2019-04-17 22:28:21 UTC,"Reviewed:  https://review.openstack.org/651181
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=79eddd1552099ed212fb06b30490521935015efe
Submitter: Zuul
Branch:    stable/queens"
1823849,2019-04-09 07:18:11 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/651114"
1823849,2019-04-17 22:27:03 UTC,"Reviewed:  https://review.openstack.org/651114
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=fb77857f7bf60d25dcde2f12eb7fdbcde327b61c
Submitter: Zuul
Branch:    stable/rocky"
1823849,2019-04-09 10:08:44 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/651181"
1823849,2019-04-17 22:27:17 UTC,"Reviewed:  https://review.openstack.org/651115
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a39f0c56438a9a588685fa9a9016f36c43901c25
Submitter: Zuul
Branch:    stable/rocky"
1823849,2019-04-09 10:08:59 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/651182"
1823850,2019-05-01 05:54:52 UTC,Mario advised me that he tested the latest upstream Percona XtraDB Cluster 5.6 release (5.6.43-28.32) against his reproducer (using openstack rally) which causes foreign key violations even with wsrep_slave_threads=1 that it does not reproduce on the latest upstream release.
1823850,2019-05-13 15:28:53 UTC,"Hi, all."
1823850,2019-04-10 15:52:52 UTC,"Hi, Trent."
1823851,2019-04-09 19:19:21 UTC,I'm not seeing this.  The timestamp always updates for me down to the second.  I checked this in normal and stand alone modes.  Maybe there are some other steps involved in triggering this issue.
1823851,2019-06-09 04:17:32 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1823852,2020-01-06 10:24:33 UTC,This issue was fixed in the openstack/cinder 14.0.3 release.
1823852,2019-10-07 19:43:47 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/687148"
1823852,2019-10-14 20:57:58 UTC,"Reviewed:  https://review.opendev.org/687148
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=bcf25eb02404a8bf5c7f154f1a36116e2ce08a54
Submitter: Zuul
Branch:    stable/stein"
1823852,2019-05-03 00:36:22 UTC,"Reviewed:  https://review.opendev.org/651619
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=333e83b8a48b8bfe8960c45a79ab1661179eea2f
Submitter: Zuul
Branch:    master"
1823852,2019-04-10 17:56:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651619"
1823852,2019-04-09 11:55:40 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651209"
1823852,2019-04-09 11:51:20 UTC,This is actually an issue in the code. It should be able to handle different casing.
1823852,2019-09-03 23:54:24 UTC,"Reviewed:  https://review.opendev.org/651209
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0c1e261c8b73b07e1fd8d5e6d8f03998fec0fc8c
Submitter: Zuul
Branch:    master"
1823852,2019-09-27 09:04:31 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1823857,2019-04-09 08:37:59 UTC,I made this patch for myself and it solved the problem.
1823857,2019-04-09 12:27:04 UTC,"The attachment ""scaling-displays.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1823857,2019-05-29 14:34:41 UTC,The issue is fixed in newer serie but indeed sounds worth backporting to BIonic
1823857,2019-06-14 22:23:32 UTC,"Hello Mitar, or anyone else affected,"
1823857,2019-09-14 19:29:17 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1823857,2019-09-19 01:42:16 UTC,Sorry for the delay.
1823857,2019-09-19 09:16:25 UTC,This bug was fixed in the package gnome-control-center - 1:3.28.2-0ubuntu0.18.04.5
1823857,2019-09-19 09:16:34 UTC,"The verification of the Stable Release Update for gnome-control-center has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823859,2020-08-04 16:33:17 UTC,"this bug is present in the current upstream also (v5.8).
Red Hat is working on the fix (ref: 1739593, private)."
1823859,2020-10-26 22:01:02 UTC,"in case anyone's interested, the upstream fix is:"
1823859,2020-11-03 11:23:32 UTC,"Thanks for reporting this bug, Hóka."
1823860,2019-04-30 08:48:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656469"
1823860,2019-04-30 08:49:17 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656470"
1823860,2019-05-16 09:28:13 UTC,"Reviewed:  https://review.opendev.org/656469
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=1fe295ca88c73cd3eeec55cb671b1d5a99ac0701
Submitter: Zuul
Branch:    master"
1823860,2019-05-17 09:11:44 UTC,"Reviewed:  https://review.opendev.org/656470
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=aee46c86bbe87cbb8b6ebb3bd9b765aafd13df53
Submitter: Zuul
Branch:    stable/stein"
1823860,2019-09-27 08:54:58 UTC,This issue was fixed in the openstack/tacker 2.0.0.0rc1 release candidate.
1823863,2019-04-16 11:51:38 UTC,I compiled the last version just and the STEP Export seams to be working here. Thank you.
1823863,2019-04-16 11:37:53 UTC,"@Martin, were you doing the STEP test in a recent nightly?  That one was tracked under a different bug report, but I thought it was fixed too.  (On the Kicad side, anyway.  Maui is doing the work on the StepUp side, but I'm not sure what the timeline there is.)"
1823863,2019-04-16 06:41:10 UTC,"Yes I tested it and the copper pour works fine now.
And I figured out than I can export a STEP file without any issues if I open the board with an older version of pcbnew (in my case Application: pcbnew Version: 5.0.0-rc2-dev-107-g49486b83b) and save it.
If I open this file with the most recent version I could export a step file. This works until I save it again with the current version."
1823863,2019-04-11 21:21:22 UTC,"OK, now this is really fixed by JP (63db3f7c17)"
1823863,2019-04-10 05:29:32 UTC,I tested it with 37ae0bf809 yesterday and the problem was still there. Also the STEP Export does not work.
1823863,2019-04-09 18:17:42 UTC,"@Martin, none of the zones in the provided board are tied to net U_Half.  I believe there was a bug that was recently fixed in the zone properties dialog that caused zone nets to be changed when changing the zone priority or something along those lines.  Would you please try resetting the zone net and confirm the zone filling is broken or it was due to the net being changed?"
1823863,2019-04-09 18:17:42 UTC,I think that this is fixed by JP today in 37ae0bf809
1823863,2019-04-09 14:11:15 UTC,By the way the STEP Export and 3D Viewer is also working better with the Version from 97063440b...
1823863,2019-04-09 13:52:41 UTC,"The commit ""97063440bbf871a5aa8da9f8c5532199240f366e"" was the last which had no problem with the filled zones."
1823863,2019-04-10 05:45:17 UTC,@Jeff-  Do you have time to look at this?  It appears maybe to be related to the netname escaping.
1823870,2019-04-09 10:39:58 UTC,Also fails for latest bionic AMI (ami-0fba9b33b5304d8b4)
1823870,2019-09-25 12:24:45 UTC,"This was a bug in an older version of snapd installed as a Debian package, that subsequently re-executed into a newer version of snapd from the core snap. Looking at current packaging the snapd side of this bug is fixed as the code was re-worked to be future-proof."
1823871,2019-09-25 13:56:33 UTC,"I can confirm this issue on 2 of our VMs running Ubuntu 18.04.
Today I lost a secondary IP on one of the interfaces, after unattended upgrades installed a new systemd package."
1823871,2019-09-11 08:46:07 UTC,"Same again today. I will need to create some countermeasure, e.g. after every unattended upgrade a script that brings down and up the interfaces, otherwise I will not be able to keep my services availability. Kind of disappointed in this, but at least it will be a solution."
1823871,2019-09-04 06:15:22 UTC,Today the same issue happened again. After systemd update my server became unavailable...
1823871,2019-04-17 09:47:52 UTC,"Is the information provided already enough to change this report's status? I think we have provided details, as well as offered to give even more (thank you Joi!) if required, so it would be great to follow up on this.
Thanks!"
1823871,2019-04-24 05:28:35 UTC,"Got same thing, but not on all virtual machines."
1823871,2019-04-09 20:19:36 UTC,I have followed the instructions in the /etc/network/interfaces file to ditch netplan and use ifupdown:
1823871,2019-04-10 10:55:09 UTC,"I've done some more digging into the systemd package update issue.  We have a number of Ubuntu 18.04 hosts, most of them are virtual machines running simple eth0 configurations under Hyper-V.  All of those VMs updated the systemd package without issue.  The only hosts which had issues after the systemd package upgrade were the two SuperMicros running bonded 10G interfaces.  On both of those hosts, the bond defined in netplan seems to have lost its configuration during the systemd upgrade.  There were multiple kern.log messages regarding the bond leaving one of its ports in a disabled state after the update.  Both hosts logged this on the same second that dpkg.log shows the systemd package itself entering 'status installed', so I'm confident it was that systemd package rather than pam-systemd that followed several seconds later."
1823871,2019-04-09 13:16:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823871,2019-04-09 21:15:41 UTC,"I followed up with my coworker who originally built our two misbehaving boxes.  He also ended up having to reboot the second box I left for him, to get the br01 bridge configuration back in working order.  Simply running 'netplan apply' and restarting the systemd network service did not resolve it, but a full reboot did.  We are using the default 18.04 netplan setup, we haven't reversed back to ifupdown like the other reporter."
1823871,2019-04-09 13:19:41 UTC,Two of our Ubuntu 18.04 hosts applied this update this morning and both dropped offline.  They're both using netplan and have bonded interfaces.  The bond layer was offline.  I had to reboot to get the network stack running again.  I left one host offline so the coworker who configured them can look it over later this morning.  Two identical hosts did not apply this systemd update this morning and they're both still online.
1823871,2019-04-09 19:46:56 UTC,"> I statically configure the IP address using the interfaces file.
"
1823872,2019-04-09 10:17:03 UTC,Fix might be in qemu (add even more special cases) or in unattended upgrades (to properly handle or at least not die). Added a bug task for that.
1823872,2019-05-24 14:34:37 UTC,This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.14
1823872,2019-05-24 14:34:36 UTC,This bug was fixed in the package qemu - 1:2.12+dfsg-3ubuntu8.8
1823872,2019-05-24 11:28:30 UTC,There are qemu packages for testing in the security team PPA here:
1823872,2019-05-24 10:18:42 UTC,"@paelzer I would appreciate if you could handle this, I did not want to just drive by and update the package I usually don't touch and I just wanted to give a heads-up to the Security Team."
1823872,2019-05-24 05:30:35 UTC,"@rbalint:
While it isn't clear from the bug updates alone IRC chat gave me the impression that this will be handled by you and the security Team (to push to -security) - is that correct or is any help needed that I miss?"
1823872,2019-05-07 10:00:18 UTC,This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.1
1823872,2019-05-07 09:53:44 UTC,This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.11
1823872,2019-05-07 09:52:17 UTC,This bug was fixed in the package unattended-upgrades - 1.5ubuntu3.18.10.4
1823872,2019-05-07 09:50:17 UTC,"The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823872,2019-05-03 14:44:46 UTC,Verified 1.1ubuntu1.18.04.7~16.04.3 on Xenial:
1823872,2019-05-03 14:23:04 UTC,Verified 1.10ubuntu5.1 on Disco.
1823872,2019-05-03 05:58:56 UTC,With some more trickery I created this situation in Disco:
1823872,2019-05-23 17:10:45 UTC,Please add Breaks: unattended-upgrades (<< 1.1ubuntu1.18.04.11) to qemu-guest-agent for Bionic and similar breaks for other affected releases to prevent unfixed u-u from considering the upgrade the package. This allows installation of other security fixes.
1823872,2019-05-02 10:10:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823872,2019-05-03 05:50:53 UTC,I can indeed trigger it in cosmic with an upgrade from 1:2.12+dfsg-3ubuntu8 -> 1:2.12+dfsg-3ubuntu8.6
1823872,2019-04-09 11:41:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823872,2019-04-09 11:43:36 UTC,"I already found this in the dup-ed bug and will fix it in u-u.
The fix is almost done, I'm adding a few extra tests."
1823872,2019-04-10 05:58:34 UTC,"I'm subscribed here in case there is anything I'm needed, but the qemu task is actually invalid as the change won't be there.
Further I assigned it to rbalint to reflect that he is working on this in u-u."
1823872,2019-04-12 12:24:49 UTC,This bug was fixed in the package unattended-upgrades - 1.10ubuntu3
1823872,2019-04-15 06:49:15 UTC,"Thanks Rbalint for fixing that.
Since a triggering change in qemu is in at least >=Bionic and was reported to even affect continuous unattended upgrades there would you considering SRUing your changes as needed?
I added tasks for all releases, but set >=Bionic to high to to that being an issue in the field IMHO."
1823872,2019-04-15 09:59:12 UTC,"Yes, I'm SRUing that, but I also extend the fix first with https://github.com/mvo5/unattended-upgrades/pull/187 to not hold qemu needlessly back."
1823872,2019-05-07 09:58:10 UTC,This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.3
1823872,2019-04-29 15:16:35 UTC,"An upload of unattended-upgrades to cosmic-proposed has been rejected from the upload queue for the following reason: ""Some bugs are missing valuable SRU information and changelog links to an unrelated, old bug #182480. Please fix an re-upload.""."
1823872,2019-04-30 08:42:45 UTC,"Hello Christian, or anyone else affected,"
1823872,2019-04-30 09:11:02 UTC,"Hello Christian, or anyone else affected,"
1823872,2019-04-30 10:01:24 UTC,"Hello Christian, or anyone else affected,"
1823872,2019-04-30 11:16:46 UTC,"I only have a testcase for Bionic, I hope rbalint has one for the other releases."
1823872,2019-04-29 14:54:23 UTC,"Hello Christian, or anyone else affected,"
1823872,2019-04-30 20:36:38 UTC,"@paelzer: From LP: #1820291 it looks like there is a ready test package for Cosmic and that could be used to test Disco as well. ;-)
I'll set one up for Xenial using equivs."
1823879,2019-04-15 11:18:12 UTC,Increasing level to high since it's a CI issue and we should fix it soon as possible.
1823880,2019-07-25 14:05:14 UTC,This issue was fixed in the openstack/tempest 21.0.0 release.
1823880,2019-04-09 16:20:34 UTC,"ACK thanks Sean, I've jumped the gun slightly and posted a change in Tempest to ensure these are always cleaned up before we attempt to remove the volume type:"
1823880,2019-04-15 11:03:48 UTC,"Reviewed:  https://review.openstack.org/651238
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=be64e1ae7cfaea2a208ba42bbbf66fe4a5dee0e9
Submitter: Zuul
Branch:    master"
1823880,2019-04-09 11:59:21 UTC,"I believe this is expected, but I will wait to assign it to tempest to give others a chance to add some input."
1823880,2019-05-07 17:14:15 UTC,"I agree with Sean, we shouldn't delete the cache when we delete the last volume associated."
1823881,2019-04-11 22:54:56 UTC,resolved by https://sourceforge.net/p/sbcl/sbcl/ci/a3b0e8a9211bd834bc4d17bddf3f5c6ad30398f8/
1823901,2019-04-10 11:42:58 UTC,"http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-containers-multinode-rocky
tripleo-ci-centos-7-containers-multinode-rocky"
1823901,2020-05-27 07:27:12 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/731091"
1823901,2020-05-27 09:43:46 UTC,"Reviewed:  https://review.opendev.org/730629
Committed: https://git.openstack.org/cgit/openstack/tripleo-upgrade/commit/?id=81a64748923f40fe3f363e7b5ac2f7b62683f06e
Submitter: Zuul
Branch:    stable/train"
1823917,2019-04-10 01:43:26 UTC,To explore this bug
1823917,2019-04-10 02:53:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1823917,2019-04-10 05:34:08 UTC,"> xdg-settings: $BROWSER is set and can't be changed with xdg-settings
"
1823917,2019-04-10 08:59:33 UTC,"Not sure about opera, but IIRC firefox doesn't use xdg-settings to set itself as the default browser."
1823917,2019-04-13 04:18:16 UTC,"I will say, though, that there are many examples across various Linucies (that's the plural, right? ☺) suggesting to use the BROWSER variable to change the default browser. Case in point:
https://wiki.archlinux.org/index.php/Environment_Variables#Default_programs"
1823917,2019-04-13 06:25:12 UTC,"I've also made the suggestion to LXQt to discontinue using `$BROWSER` and instead using `xdg-settings` as I've shown how even though chromium is unique in its robustness, there is still not a complete definition of ""default browser"" (including dealing with file associations/mimetypes and scheme handlers) by using `$BROWSER` alone, whereas `xdg-settings` just resolves everything."
1823968,2019-04-10 22:34:41 UTC,Of course this problem is for Debian too.
1823970,2019-04-10 22:35:24 UTC,Psi can not be managed by dev team directly like psi-plus?
1823970,2020-10-24 21:11:50 UTC,"Currently, there is a Psi 1.5.x."
1823972,2019-04-09 14:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823972,2019-06-02 17:05:22 UTC,Thanks for fixing this issue. We confirm that the problem is gone with updated kernel.
1823972,2019-05-14 22:54:36 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1823972,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1823972,2019-04-29 21:15:51 UTC,"$ apt-cache policy linux-generic-hwe-16.04
linux-generic-hwe-16.04:
  Installed: 4.15.0.49.70
  Candidate: 4.15.0.49.70
  Version table:
 *** 4.15.0.49.70 500
        500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     4.15.0.48.69 500
        500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages"
1823972,2019-04-29 16:04:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1823972,2019-04-24 06:58:44 UTC,"@arighi, @kmously, thanks for pulling all fuse patches to bionic/master-next. Am I right in my understanding that the patches will also propagate to xenial/hwe eventually?"
1823972,2019-04-12 08:16:52 UTC,"@arighi, thanks. Let me know if you need more testing and/or help. Good luck with the review."
1823972,2019-04-12 06:28:22 UTC,All fixes applied here:
1823972,2019-04-11 19:07:17 UTC,"@navytux yes, a few of them require minimal changes, but most of them can be applied cleanly to 4.15."
1823972,2019-04-11 18:52:45 UTC,"Thanks. If I understood correctly, the patches should be more or less directly applicable to 4.15.y"
1823972,2019-04-11 18:44:17 UTC,"I'll take a look at the other patches, I think they can be easily applied to 4.15 if they don't require too much backporting work."
1823972,2019-04-09 15:40:09 UTC,apport information
1823972,2019-04-11 17:02:28 UTC,Sent an SRU fix to include 63576c13bd in Bionic.
1823972,2019-04-11 17:17:06 UTC,"Andrea, thanks."
1823972,2019-04-09 15:40:12 UTC,apport information
1823972,2019-04-09 15:40:13 UTC,apport information
1823972,2019-04-09 15:40:15 UTC,apport information
1823972,2019-04-09 15:40:16 UTC,apport information
1823972,2019-04-09 15:40:11 UTC,apport information
1823972,2019-04-09 15:40:18 UTC,apport information
1823972,2019-04-09 15:40:19 UTC,apport information
1823972,2019-04-09 15:40:20 UTC,apport information
1823972,2019-04-09 15:40:21 UTC,apport information
1823972,2019-04-09 15:40:23 UTC,apport information
1823972,2019-04-09 15:40:17 UTC,apport information
1823973,2019-06-28 21:43:47 UTC,I tried for a bit with 5.1 but could get a track to change without resorting to python.
1823973,2019-06-28 18:35:26 UTC,"@Seth, I don't have an issue with your fix but I am concerned that a track somehow ended up on a non-copper layer.  Is this even possible in Pcbnew or is it possible that this board was modified with a Python script or by hand?  If Pcbnew allowed this, we need to track down that bug as well.  We should not allow tracks on non-copper layers."
1823973,2019-06-28 18:24:43 UTC,+1
1823973,2019-06-28 18:15:32 UTC,I finally got the issue!
1823973,2019-06-28 18:01:42 UTC,Fixed in the 5.1 branch.
1823973,2019-06-28 16:31:16 UTC,"On 6/28/19 11:47 AM, Seth Hillbrand wrote:

> ""It's not as fixed as you would like it to be"" will be the epitaph on my
> tombstone. :/
"
1823973,2019-06-28 12:18:19 UTC,"@Seth, it's not as fixed as you would like it to be.  It still crashes for me 100% of the time using the project provided by the bug reporter.  It looks like there might be a corner case which this project nicely provides.  I have a fix but I'm not sure it is strictly correct.  I changed the assert to a logical if statement so when nothing is connected to the track passed to the connectivity algorithm dangling track test it just returns true.  I'm not entirely sure why this was considered an invalid condition and an assert was used but I'm not familiar with this code so maybe I'm interpreting what this is supposed to do.  It seems to me that it is entirely plausible that you could have a track segment that is completely orphaned which would trigger this bug.  If you see an issue with my fix (see patch) please let me know."
1823973,2019-06-28 01:18:48 UTC,No.  The fix exists in both branches already.
1823973,2019-06-28 15:47:42 UTC,"""It's not as fixed as you would like it to be"" will be the epitaph on my tombstone. :/"
1823973,2019-06-27 16:01:29 UTC,*fixed* (not introduced) in the dev branch.
1823973,2019-06-17 12:33:55 UTC,"@Tom, what is the status of this bug?  I would like to git 5.1.3 out soon and this is the only critical bug report."
1823973,2019-06-25 19:42:11 UTC,"Fixed in revision be42b80713f411ae38c9edb60154c341ee2eb0c0
https://git.launchpad.net/kicad/patch/?id=be42b80713f411ae38c9edb60154c341ee2eb0c0"
1823973,2019-06-25 20:48:59 UTC,I think this needs cherry-picking onto 5.1.
1823973,2019-06-26 19:07:25 UTC,"@Michael, this commit does not cherry pick cleanly.  It looks like there have been major incompatible changes to pcbnew/tracks_cleaner.cpp.  Either someone forgot to cherry-pick previous commits or the entire track cleaning code has been changed in a way that is not compatible with 5.1."
1823973,2019-06-27 19:22:52 UTC,"Just so I'm clear, does this need fixed in 5.1?  It appears to me that it does."
1823973,2019-06-26 20:01:26 UTC,"@Jeff, it's not hard to apply I'm just not sure it's correct given the magnitude of the changes."
1823973,2019-06-26 20:21:34 UTC,"@Wayne, agreed.  It's not clear to me if the bug existed in the old algorithm or was introduced in the re-write.  (My guess is that the bug exists in 5.1, but I haven't looked into it deeply.)"
1823973,2019-06-27 15:59:24 UTC,@Wayne-
1823973,2019-06-26 19:47:07 UTC,Cleanup tracks and vias was re-written for 6.0 to have the dry-run feature.
1823975,2019-04-10 20:06:06 UTC,Marking as release gating until further investigation; related to PTP functionality
1823975,2019-07-16 15:35:05 UTC,Incorrect provisioning process applied.
1823975,2019-07-22 17:48:22 UTC,Since PTP provision is not fully complete it a incorrect provision.LP accepted as invalid.
1823975,2019-05-10 00:26:22 UTC,PTP provisioning process violation.
1823977,2019-04-09 15:01:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651266"
1823977,2019-06-06 09:25:09 UTC,"Reviewed:  https://review.opendev.org/651266
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=eca9c9149406904d49205a93218a3dad3206d82a
Submitter: Zuul
Branch:    master"
1823977,2019-06-12 14:44:02 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1823981,2019-08-06 15:58:43 UTC,"Oh, and the p-3 => p-1 padding changes are in there too.. forgot about those."
1823981,2019-09-06 15:38:45 UTC,"Pushed to master for inclusion in 3.4. Thanks, Bill!"
1823981,2019-08-06 15:56:52 UTC,"Thanks, Galen.  New branch pushed:"
1823981,2019-06-25 17:47:46 UTC,"Same branch as previous comment rebased to master to update the dialog/observable handling.  Also, I added a filter feature to the group-linked permissions interface so the list of perms can be filtered by code / description."
1823981,2019-05-24 18:47:24 UTC,Branch rebased to master amid commit flurry.  This resolves the issue noted above about toasts not displaying.
1823981,2019-07-31 16:22:11 UTC,"I've reviewed the interface. It does the thing and will be a great improvement. I'm not quite ready to sign off, though, and have some comments:"
1823981,2019-04-09 15:13:06 UTC,Code:
1823982,2019-04-09 15:45:22 UTC,Fix pushed:
1823982,2019-05-10 18:04:08 UTC,"Thanks very much for this fix, Bill.  It works well for me.  I've pushed it to master and rel_3_3."
1823983,2019-04-09 15:37:24 UTC,This turns out to be a very straight-forward fix.  Branch here:
1823985,2019-04-10 08:34:47 UTC,Hi Arnold
1823985,2019-04-09 18:39:09 UTC,"On Tue, Apr 09, 2019 at 03:15:26PM -0000, Lars wrote:

> I set a custom leases file in the dhcpd.conf:
>  lease-file-name ""/test/var/lib/dhcp/dhcpd.leases"";
>
> and created a custom apparmor profile for that in /etc/apparmor.d/local/usr.sbin.dhcpd:
> /test/var/lib/dhcp/dhcpd{,6}.leases* lrw,
>
> But when I try to start I see the following errors from dhcpd:
"
1823985,2019-04-10 20:17:12 UTC,"On Wed, Apr 10, 2019 at 08:34:47AM -0000, Lars wrote:

> [root@myhost:~]↥ 1 # namei -l /test/var/lib/dhcp/dhcpd.leases
> f: /test/var/lib/dhcp/dhcpd.leases
> drwxr-xr-x root  root  /
> drwxr-xr-x dhcpd dhcpd test
> drwxr-xr-x dhcpd dhcpd var
> drwxr-xr-x dhcpd dhcpd lib
> drwxr-xr-x dhcpd dhcpd dhcp
> -rw-r--r-- dhcpd dhcpd dhcpd.leases
"
1823987,2019-04-09 17:14:34 UTC,It's the ubuntu-toolchain-r PPA which is probably causing your issue.
1823987,2019-04-15 15:20:32 UTC,Please use the command ppa-purge to remove the ubuntu-toolchain-r PPA.
1823987,2019-06-15 04:17:36 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1823989,2019-04-09 15:56:13 UTC,"First issue: keystone container apache config references WSGI scripts with a python3- prefix, but this is incorrect."
1823989,2019-11-11 15:40:48 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1823989,2019-07-18 00:37:51 UTC,This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc2 release candidate.
1823989,2019-04-20 11:09:16 UTC,"Reviewed:  https://review.opendev.org/652958
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=87febca7935e85112cd2210946d298ec2c739882
Submitter: Zuul
Branch:    stable/stein"
1823989,2019-04-18 10:00:24 UTC,"Reviewed:  https://review.openstack.org/651317
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d62ccca3e03013c0728c4a20b3930cde540b513a
Submitter: Zuul
Branch:    master"
1823989,2019-04-16 09:54:23 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/652958"
1823989,2019-04-12 08:09:23 UTC,"Reviewed:  https://review.openstack.org/651327
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=6c0065185943355851308ae4df23b73918fab7be
Submitter: Zuul
Branch:    master"
1823989,2019-04-10 11:39:57 UTC,Horizon container fails in CI:
1823989,2019-04-09 18:02:46 UTC,Target WSGI script not found or unable to stat: /usr/bin/python3-placement-api
1823989,2019-04-09 17:10:39 UTC,Placement-api restarting:
1823989,2019-04-09 16:48:44 UTC,"Kolla patch: https://review.openstack.org/651327
Kolla ansible patch: https://review.openstack.org/651317"
1823989,2019-04-15 06:35:59 UTC,"Reviewed:  https://review.openstack.org/652003
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0cfe0d74f6b83bd6ddc83bc1d0cb71fcf13f4739
Submitter: Zuul
Branch:    stable/stein"
1823989,2019-04-12 08:12:08 UTC,"Fix proposed to branch: stable/stein
Review: https://review.openstack.org/652003"
1823990,2019-04-09 17:13:39 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1823994,2019-04-26 03:05:07 UTC,I am still seeing this issue on ARM64 nodes for the SRU triggered yesterday:
1823994,2019-04-09 20:24:30 UTC,"adding 'lspci -vnvn' output and
```
$ cat /proc/version_signature
Ubuntu 4.15.0-47.50-generic 4.15.18
```"
1823994,2019-04-09 17:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1823994,2019-04-09 17:01:37 UTC,It appears that linux-signed-hwe-edge does not yet have the arm64 support we added to linux-signed.
1823994,2019-04-09 21:37:33 UTC,"I have a fix staged for this, but it relies on published signed binaries that aren't present."
1823995,2020-03-07 10:09:51 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1823998,2019-05-03 17:18:43 UTC,"I've submitted a patchset which I think should fix this, but if you could test that it actually does handle large images correctly that would be great."
1823998,2019-07-08 15:18:25 UTC,"Changes now in master, will be in 4.1."
1823998,2019-08-16 04:51:22 UTC,https://git.qemu.org/?p=qemu.git;a=commitdiff;h=5e6dbe1e8cbbe4b6f74
1824000,2019-04-16 23:43:58 UTC,Same here. I tried reinstalling all the related packages but the problem persists.
1824000,2021-02-15 18:34:40 UTC,I'm affected as well. Running Ubuntu Mate 20.04.
1824000,2020-12-06 10:45:13 UTC,Hello I use Kubuntu 20.10 and fixed this to be able to find a package and it worked.
1824000,2020-12-04 21:08:48 UTC,"I'm affected by this as well.
I'm curious if Noah's fix actually fixes the issue, as others noted it can reoccur after others manually chmodded the file."
1824000,2020-10-26 21:17:34 UTC,"These files are created by snapd with permission 0644, as can be seen here: https://github.com/snapcore/snapd/blob/master/advisor/backend.go#L71"
1824000,2020-10-21 21:45:38 UTC,Any chance to accept the patch soon? It's an annoying bug...
1824000,2020-10-16 21:22:56 UTC,Here is the patch!
1824000,2020-10-16 21:21:06 UTC,"As I suggested in https://code.launchpad.net/~nononoha/command-not-found/command-not-found/+merge/392242, simply chmoding the file after creation solves the problem!"
1824000,2020-06-30 19:47:42 UTC,Same problem on Ubuntu 20.04 LTS
1824000,2020-02-14 13:08:49 UTC,"Please check the thread. Fixing the permissions as in comment #2 fixes the issue only temporarily. See comment #4 by the same author of comment #2. Hence, this is no workaround."
1824000,2020-02-14 12:50:12 UTC,"Workaround from https://bugs.launchpad.net/command-not-found/+bug/1824000/comments/2
confirmed working in (K)Ubuntu 19.10"
1824000,2019-10-22 09:56:22 UTC,This is the third time this bugs affects me after an apt-update of a XUbuntu 19.04... Please fix the file permission issue in your (post-install) scripts... I'm annoyed having to do this manually after each update!
1824000,2019-09-25 12:26:28 UTC,I think both sides must be improved: on snapd side we should ensure the mode of the file is correct. On command-not-found side we should be much more graceful in face of permission errors. They should not be fatal like they are today.
1824000,2019-09-19 09:12:03 UTC,"Removing snapd seems to fix the issue. If you don't use any snap package, the workaround for the issue seems to be as simple as"
1824000,2019-05-03 10:39:06 UTC,"$ toto
Désolé, command-not-found s'est arrêté anormalement ! Veuillez remplir un rapport de bogue à :
https://bugs.launchpad.net/command-not-found/+filebug
Veuillez inclure les informations suivantes dans le rapport :"
1824000,2019-04-25 13:04:18 UTC,Next day permissions are broken again
1824000,2019-04-24 13:35:30 UTC,The files commands.db* are created by snapd. Presumably snapd should make the files readably by everyone.
1824000,2019-04-24 12:31:35 UTC,"It looks like permissions are broken after upgrade to 19.04 for the following files:
$ ls -l /var/lib/command-not-found
total 3184
-rw-r----- 1 root root 3252224 Apr 23 23:01 commands.db
-rw-r----- 1 root root    2403 Apr 23 23:01 commands.db.metadata"
1824000,2020-05-13 22:42:57 UTC,I was having a similar issue after upgrading from 19.10 to 20.04.
1824000,2019-11-06 07:54:01 UTC,Issue is still present in ubuntu 19.10.
1824000,2020-11-17 09:02:17 UTC,"$ lss
Désolé, command-not-found s'est arrêté anormalement ! Veuillez remplir un rapport de bogue à :
https://bugs.launchpad.net/command-not-found/+filebug
Veuillez inclure les informations suivantes dans le rapport :"
1824005,2019-06-17 04:55:28 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.6
1824006,2019-04-10 14:22:56 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1824006,2019-06-10 04:17:35 UTC,[Expired for samba (Ubuntu) because there has been no activity for 60 days.]
1824007,2019-04-10 14:23:29 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1824007,2019-06-10 04:17:36 UTC,[Expired for samba (Ubuntu) because there has been no activity for 60 days.]
1824009,2019-06-11 04:17:24 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1824009,2019-04-11 12:42:56 UTC,"I tried exporting the attached board.  It would not export correctly but kicad did not crash.  I'm not sure why the step file could not be created but I suspect that it's due to the missing footprint 3D models.  My guess is one of the missing 3D models is causing the crash.  If you could include the missing 3D models, that would be helpful.  I attached the message panel report of the step export which lists the missing models."
1824009,2019-04-11 09:43:50 UTC,"Kicad 5.10 found open border which 5.02 didn't.  Fixed that, DRC is clean; can view in 3D view.  But still crashes when exporting to step.
Note that I am connecting segments of the board outline so that the endpoints are on a 0.1mm grid; Should I be doing something else?"
1824009,2019-04-11 07:56:57 UTC,Still crashes in kicad 5.10.
1824009,2019-04-10 16:24:00 UTC,"It is.  However, this is an actual crash in the TKBO dll, so I'm not sure what was happening there.  Kobus will need to test with 5.1"
1824009,2019-04-10 14:00:36 UTC,"@Seth, I thought the KiCad to STEP conversion code filled board outlines to prevent this crash.  There may be limit to how long of a line segment is used to close the outline.  I though it was user configurable but I may be remembering this incorrectly."
1824009,2019-04-10 13:00:28 UTC,"Note that the outline is not closed.  In KiCad 5.1, DRC will indicate the location where it is not closed."
1824009,2019-04-10 11:02:13 UTC,Could you try kicad 5.1.0?
1824009,2019-04-10 10:37:30 UTC,"Version Info:
Application: kicad
Version: (5.0.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013"
1824009,2019-04-09 19:50:05 UTC,Please add your KiCad version information as well as the board file for which this fails.
1824010,2019-04-10 08:04:03 UTC,"Hello Steve, or anyone else affected,"
1824010,2019-04-10 08:05:57 UTC,"Hello Steve, or anyone else affected,"
1824010,2019-04-16 16:28:10 UTC,This bug was fixed in the package maven - 3.6.0-1~18.04.1
1824014,2019-05-29 03:36:34 UTC,This functionality already exists in the feature file recent_forum_posts.feature
1824016,2019-06-04 09:25:03 UTC,This bug was fixed in the package linux-signed-hwe - 4.15.0-51.55~16.04.1
1824016,2019-06-04 09:18:46 UTC,This bug was fixed in the package linux-signed - 4.18.0-21.22
1824016,2019-06-04 09:18:21 UTC,This bug was fixed in the package linux-signed - 4.15.0-51.55
1824016,2019-06-04 09:17:46 UTC,This bug was fixed in the package linux-signed-hwe - 4.18.0-21.22~18.04.1
1824016,2019-06-04 09:12:00 UTC,This bug was fixed in the package linux-signed - 4.4.0-150.176
1824016,2019-05-14 19:06:57 UTC,This bug was fixed in the package linux-signed - 5.0.0-15.16
1824016,2019-05-14 12:08:59 UTC,"In Xenial, hwe-edge is a meta-only source pointing at the hwe binaries. So there is no separate linux-signed."
1824016,2019-06-04 09:17:33 UTC,This bug was fixed in the package linux-signed-hwe-edge - 5.0.0-16.17~18.04.1
1824018,2019-04-16 21:44:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653155"
1824018,2019-05-27 05:36:33 UTC,"Reviewed:  https://review.opendev.org/653155
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=748dd8df737d28aad7dfd0a1e32659e0256126e2
Submitter: Zuul
Branch:    master"
1824018,2019-07-25 14:05:12 UTC,This issue was fixed in the openstack/tempest 21.0.0 release.
1824023,2021-01-11 15:03:52 UTC,@dn I'm having same issues with ubuntu 20.04.1 LTS and getting same 'pcieport' errors. Have you upgraded from 18.04 to something newer since your comment back in 2019?
1824023,2019-04-11 04:27:31 UTC,This bug also causes resume from suspend to fail.
1824023,2019-05-03 22:22:27 UTC,"This bug persists even after upgrade to the latest kernel updated, 4.18.0-18 and replacing the system firmware at /lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin with the latest firmware from
the ath10k firmware github repository: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1"
1824023,2019-05-30 01:50:03 UTC,"I updated the firmware to 4.4.1.c3 from:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
and now it doesn't crash anymore."
1824023,2021-01-18 02:28:54 UTC,"@craigwharding No, haven't upgraded and I'm still using the same firmware I posted about in 2019. There are newer firmware versions available on that github which I haven't tried, so if you find a better solution or a firmware which doesn't cause errors, please let us all know."
1824024,2019-05-07 18:53:19 UTC,Confirmed in 3.2.5
1824032,2019-04-10 06:52:23 UTC,"Hello,"
1824032,2019-04-10 07:04:31 UTC,"Also, check the [Additional settings] in the audio-recorder.
Activate the ""Show icon on the system tray"" option."
1824032,2019-04-11 17:01:53 UTC,"Thanks! Worked great!
Was the new app indicator that wasn’t updated.
In manjaro its as easy as .deb .rpm, just need to make sure chrome-gnome-extension is installed then it works from any browser once uninstall the gnome extension in the browser too.
As far as the app goes its amazing i love it, being very new to linux (MACOS user) i would have loved to see something similar on other OS. Has great potential specially with writers my only comment would be that the GUI could be improved and perhaps an audio to txt/doc would be fabulous,
Thanks for the prompt response,
Malco
On Apr 10, 2019, 02:15 -0500, moma <email address hidden>, wrote:

> Also, check the [Additional settings] in the audio-recorder.
> Activate the ""Show icon on the system tray"" option.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1824032
>
> Title:
> no top bar icon
>
> Status in Audio Recorder:
> New
>
> Bug description:
> when I upgrade from gnome 3.28 to 3.32 The top bar icon disappears/not there at all, unable to reach short menu from top panel
> I am using Manjaro 18.04 (arch) kernel 4.19.32.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/audio-recorder/+bug/1824032/+subscriptions
"
1824032,2019-04-11 17:21:23 UTC,"Hello Malco,"
1824035,2019-04-23 15:18:19 UTC,"https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/8
https://github.com/openstack-charmers/charm-interface-ceph-client/pull/2"
1824035,2019-08-16 18:45:42 UTC,Please see related bug re: supportability of the ceph-admin interface: https://bugs.launchpad.net/charm-kubernetes-master/+bug/1840492
1824038,2019-04-10 08:14:19 UTC,"Can you tell me how I would do that. I added the first name to the subscription list, but I can't do it with the second two."
1824038,2019-04-10 08:40:59 UTC,"Since Heiner Kallweit has an Launchpad account, let's wait for his reply."
1824038,2019-04-10 07:34:53 UTC,"Ok, please raise the issue to the maintainer and mailing list:
<email address hidden>
<email address hidden>
<email address hidden>"
1824038,2019-04-14 03:40:49 UTC,An update on this.
1824038,2019-04-14 03:50:29 UTC,Confirmed. The same behaviour in the original kernel 4.18.0-17.
1824038,2019-04-10 15:08:39 UTC,"Looks like it has a Haswell CPU, so older kernels should be able to work on this system."
1824038,2019-04-10 06:28:02 UTC,"Sorry, typo. 2. Re-tested with 5.1-rc4. Problem still occurs."
1824038,2019-04-10 11:23:55 UTC,"This sounds more like a platform issue (especially as WiFi seems to be affected too). Few months ago we had something similiar and it turned out to be a problem with Intel PCI bridge code.
The only way I see for now is to find a working version and then bisect."
1824038,2019-04-10 05:49:39 UTC,"There are several fixes in upstream r8169 driver, please test mainline kernel:"
1824038,2019-04-10 05:32:15 UTC,dmesg output as requested
1824038,2019-04-10 05:14:25 UTC,Please reproduce the issue and attach full dmesg.
1824038,2019-04-10 06:23:04 UTC,"1. Removed the r8169-refresh script
2. Rested with 5.1-rc4"
1824038,2019-04-10 02:04:48 UTC,apport information
1824038,2019-04-10 02:04:46 UTC,apport information
1824038,2019-04-10 00:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824042,2019-04-10 06:01:19 UTC,Subsheets are not really meant to be used that way. The annotation for them is stored inside the sheet itself. Meaning if you use the same sheet file in different projects then these projects will interfere with each other.
1824042,2019-04-10 08:25:41 UTC,"Rene, but why the reference designators unexpectedly changed by program into such as R?, C?, X? ? I think the program ought not to behave such a way. The reference designator of symbol ought be by user control (and the program should keep & let it be anyway)."
1824042,2019-04-10 23:15:35 UTC,Disclaimer: I am not a developer just very active in the community and head of the library team.
1824042,2019-04-13 13:14:25 UTC,A short video would help to understand the problem.
1824042,2019-04-13 15:26:57 UTC,This is related to lp:1818785.  The problem is not as simple as it would seem.  Schematics can be referenced by any number of sheets which means there could be any number of per sheet references.  We could allow the user to select the sheet path references to use but this information is stored as as a path of 32 bit hexadecimal numbers so it would be meaningless to the user.  This is also the reason we cannot remove existing sheet paths because there is no way of knowing if the schematic is being used by other projects.  So the easiest solution is to just clear the annotation when adding a sheet from an existing schematic.
1824043,2019-10-13 04:26:29 UTC,[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.]
1824043,2019-08-13 21:11:07 UTC,"Since April, I forgot. But I always use either apt-get install, either
synaptic. But in my report of April, I see update-notifier. I have a
faint remembrance of the update notifier giving it a try every day until
I got bored, filed the bug and found a workaround."
1824043,2019-05-10 07:01:54 UTC,"Found this workaround in #1655431. Quoting: Boris Rybalkin (ribalkin) wrote on 2017-11-26: #18
Was able to fix sf mirrors issue by replacing sf mirror with some github copy:
sudo sed -i 's#http://downloads.sourceforge.net/corefonts#https://github.com/pushcx/corefonts/raw/master#g' /usr/share/package-data-downloads/ttf-mscorefonts-installer
Then run:
sudo /usr/lib/update-notifier/package-data-downloader
All downloaded and good.
[End quote]
This solves the mirrors problems with Sourceforge. There remains a problem that an authentication dialog disappears even before you get a chance to answer."
1824043,2019-08-07 17:13:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824043,2019-08-13 20:37:43 UTC,Thanks for taking the time to report this issue. What package manager did you use to install ttf-mscorefonts?
1824048,2019-04-10 02:45:26 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/651429"
1824048,2019-07-01 14:24:33 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/651429
Reason: The bug was duplicated against bug 1805891 and I haven't seen a response so I don't know if this is valid for queens but I'm going to assume it's not so will abandon."
1824049,2019-04-10 22:17:35 UTC,"This is a question of policy, not of implementation."
1824050,2019-04-10 03:28:17 UTC,apport information
1824050,2019-04-10 17:18:27 UTC,"This linux-nfs list member found the origin of the problem:
https://marc.info/?l=linux-nfs&m=155480197614448&w=2"
1824050,2019-04-10 03:28:22 UTC,apport information
1824050,2019-04-24 10:10:12 UTC,The fix is not in linux-nfs tree yet.
1824050,2019-04-10 03:28:18 UTC,apport information
1824050,2019-04-10 03:28:16 UTC,apport information
1824050,2019-04-10 03:28:20 UTC,apport information
1824050,2019-04-10 03:28:13 UTC,apport information
1824050,2019-04-10 03:28:11 UTC,apport information
1824050,2019-04-10 03:28:10 UTC,apport information
1824050,2019-04-10 03:28:09 UTC,apport information
1824050,2019-04-10 02:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824050,2019-04-10 03:28:14 UTC,apport information
1824053,2019-04-13 02:04:01 UTC,Anyone else has a similar problem?
1824053,2019-04-15 04:07:13 UTC,I  can't reproduce this problem with  qemu.git/matser?  It seems to have been fixed in qemu.git/matser.
1824053,2019-04-15 19:02:49 UTC,"Hi, unfortunately a lot has changed from 2.8 and it might be hard to identify a single individual fix that may be responsible for this; there are aio_context fixes that go in nearly every version."
1824053,2019-04-16 05:31:49 UTC,Marking this bug as fixed according to comment 2.
1824053,2019-04-16 07:53:58 UTC,dann frazier met the same problem as me in (https://bugs.launchpad.net/qemu/+bug/1805256).
1824053,2019-04-16 08:08:37 UTC,"Ok, we can track the bug reported by Dann Frazier in ticket 1805256 instead."
1824053,2019-04-20 02:49:16 UTC,"I can reproduce this problem with qemu.git/matser. It still exists in qemu.git/matser. I found that when an IO return in
worker threads and want to call aio_notify to wake up main_loop, but it found that ctx->notify_me is cleared to 0 by main_loop in aio_ctx_check by calling atomic_and(&ctx->notify_me, ~1) . So worker thread won't write enventfd to notify main_loop. If such a scene happens, the main_loop will hang:"
1824058,2019-04-10 03:47:44 UTC,Changing the component for this bug.
1824059,2019-09-24 04:17:19 UTC,[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]
1824059,2019-07-25 10:49:19 UTC,Marking it as incomplete. Could you add more details about how to reproduce it?
1824059,2019-05-22 12:55:13 UTC,"pengyuesheng, I can't reproduce this issue. Could you please add more details?"
1824065,2019-07-11 12:54:48 UTC,not free anymore http://users.teilar.gr/~g1951d/License.pdf
1824065,2019-07-11 15:28:33 UTC,"Thanks for pointing that out, Lenin. That means that this bug cannot be fixed as the package cannot be updated to a newer version unless the license becomes free once more. As such, should be marked ""Won't Fix""."
1824065,2019-08-12 11:14:18 UTC,"Erich, I can't do so since Ubuntu says: ""Won't Fix
Doesn't fit with the project plans, sorry."""
1824065,2019-09-12 19:41:55 UTC,fix is here http://phd-sid.ethz.ch/debian/fonts-ancient-fonts/NEW3/ but will be non-free
1824065,2020-04-12 15:12:05 UTC,"It's not just ""non-free"". The new license is so restrictive that we can't even distribute the new font versions in a non-free section of our archives."
1824065,2020-04-12 16:05:03 UTC,https://dn-works.com/wp-content/uploads/2020/UFAS-Docs/License.pdf indeed network installs are prohibited
1824071,2019-04-10 13:05:49 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1824072,2019-04-10 06:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824072,2019-06-10 04:17:20 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824075,2019-04-11 21:31:57 UTC,So I've just tried to use the previous release and my problem goes away.
1824075,2020-02-26 11:39:20 UTC,"Dear Fraser,"
1824075,2019-07-15 17:25:25 UTC,Can you please try the latest release and see if it fixes your issue?
1824076,2019-04-10 07:00:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651445"
1824076,2019-06-04 02:40:44 UTC,"Change abandoned by pengyuesheng (<email address hidden>) on branch: master
Review: https://review.opendev.org/651445
Reason: you are right, I will abandon it."
1824076,2019-08-07 10:32:30 UTC,"Reviewed:  https://review.opendev.org/651445
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=26c5c8c34392124a5c81859ef0acfffd371e6743
Submitter: Zuul
Branch:    master"
1824076,2019-09-13 16:42:01 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.
1824088,2020-04-01 14:14:50 UTC,"It seems systemd actually supports restarting oneshot services now, so any options for timestamps will be removed (anything other than 0 will behave as always), and systemd timers will have to be configured via drop-ins instead. Finally."
1824088,2020-04-01 13:37:35 UTC,The thing is that it's only the delta that is handled in UTC not the iso-8601-part so it will work just fine.
1824088,2020-04-01 13:28:09 UTC,"But if I live in UTC+11, I don't want it to run when the day has changed in UTC+0?"
1824088,2020-04-01 13:20:15 UTC,"The interesting about the code is that it always only treat the timestamp of the file as ""YYYY-MM-DD"" and nothing else (this also includes ""now"")."
1824088,2020-04-01 12:34:16 UTC,"The attachment ""apt.systemd.daily.diff"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1824088,2020-04-01 12:32:06 UTC,Oh but we have the other issue where we have more interval options than systemd services. Sigh.
1824088,2020-04-01 12:31:15 UTC,"Arguably, a workaround might be to remove support for the interval options now, and then treat it as ""one day"", and just check that %Y-%m-%d for today != the one for the stamp."
1824088,2020-04-01 12:25:16 UTC,"It seems reasonable that setting TZ=UTC0 for date --iso-8601 could help (as that's where a time zone is relevant, the +%s conversion it is not relevant for)."
1824088,2020-04-01 12:12:27 UTC,"I know that we can sometimes miss a beat so to say, but fixing this will require fixing systemd to allow retrying of failed timer services, and then removing the options for intervals inside of apt."
1824088,2020-04-01 13:15:01 UTC,"https://salsa.debian.org/apt-team/apt/-/merge_requests/115 implements the proposed change for daily runs, and warns if intervals are configured to anything other than 1 or 0 (and soon, always), telling people to configure their systemd timer instead."
1824088,2020-04-01 12:05:59 UTC,Awesome work Magnus. Well done!
1824088,2020-04-01 11:29:30 UTC,Setting TZ for the complete script will not work as it will make strange behaviour if you are far away from UTC/GMT TZ. You can set it for just the date command that returns the epoch time.
1824088,2020-03-31 21:21:45 UTC,How about this idea?
1824088,2020-03-31 20:57:16 UTC,"If we look at lines 131 and 132 in /usr/lib/apt/apt.systemd.daily, we will se the following:"
1824088,2020-03-31 07:49:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824088,2020-03-31 07:02:08 UTC,"It will not run after 36h either. It will not run until next day because ""yesterday"" did not have 24 hours until next day."
1824088,2020-03-30 16:18:28 UTC,"It's hardly and issue given that the script runs twice per day, which compensates for that by running it after 36 hours instead of 24."
1824088,2020-03-30 16:16:17 UTC,"Yes we know that the script does not necessarily run once a day, that's not a surprise."
1824088,2020-03-30 15:02:11 UTC,This IS related to daylight saving.
1824088,2020-04-01 12:10:12 UTC,"I'm not convinced there is a bug here or that the patch actually fixes it. We convert our times to Unix time stamps, which are independent of time zones and DST."
1824094,2020-04-18 13:05:56 UTC,This is not a problem with the Ubuntu version.
1824095,2019-04-16 17:56:07 UTC,This issue was fixed in the openstack/neutron 14.0.1 release.
1824095,2019-04-11 12:13:19 UTC,"Reviewed:  https://review.openstack.org/651458
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f2bfb65b2b0292fbbe201dd93f268697ce99b5eb
Submitter: Zuul
Branch:    stable/stein"
1824095,2019-04-10 11:51:16 UTC,Addressed in https://review.openstack.org/#/c/651458/
1824111,2019-06-18 18:30:17 UTC,"Majority of them were due to ""Could not connect to ftpmaster.internal:80"" around Jun 6th, and openjdk8 tests have never passed AIUI."
1824111,2019-07-03 13:42:40 UTC,This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.1
1824111,2019-07-03 13:32:55 UTC,This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 - 19.0.1-1~18.04.1
1824111,2019-07-03 13:32:51 UTC,This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 - 1:19.0.1-0ubuntu1~18.04.1
1824111,2019-07-03 13:32:46 UTC,This bug was fixed in the package xserver-xorg-video-nouveau-hwe-18.04 - 1:1.0.16-1~18.04.1
1824111,2019-07-03 13:32:43 UTC,This bug was fixed in the package xorg-server-hwe-18.04 - 2:1.20.4-1ubuntu3~18.04.1
1824111,2019-07-03 13:32:27 UTC,This bug was fixed in the package libclc - 0.2.0+git20190306-1~ubuntu18.04.1
1824111,2019-07-03 13:32:22 UTC,This bug was fixed in the package libdrm - 2.4.97-1ubuntu1~18.04.1
1824111,2019-07-03 13:32:18 UTC,"The verification of the Stable Release Update for llvm-toolchain-8 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824111,2019-07-03 13:32:06 UTC,This bug was fixed in the package llvm-toolchain-8 - 1:8-3~ubuntu18.04.1
1824111,2019-06-19 07:06:30 UTC,autopkgtests cleared
1824111,2019-06-18 16:11:01 UTC,The mesa upload has created a fair number of autopkgtest regressions. What is the status of those?
1824111,2019-05-08 15:24:34 UTC,"Hello Timo, or anyone else affected,"
1824111,2019-06-06 18:21:29 UTC,"Hello Timo, or anyone else affected,"
1824111,2019-05-08 15:12:33 UTC,"Hello Timo, or anyone else affected,"
1824111,2019-05-09 19:21:44 UTC,"Hello Timo, or anyone else affected,"
1824111,2019-06-10 08:22:05 UTC,"tested on a Dell hybrid gfx laptop with Intel Skylake + AMD HAINAN, and everything seems fine. Tested glxgears, glmark2 on both GPU's"
1824111,2019-05-28 05:56:30 UTC,"I would suggest to ship at least Mesa 19.0.4, because of the bug https://bugs.freedesktop.org/show_bug.cgi?id=110355 in some popular programs."
1824111,2019-05-28 06:12:37 UTC,we'll get the last update of 19.0.x series eventually
1824111,2019-05-09 20:07:34 UTC,"Hello Timo, or anyone else affected,"
1824111,2019-06-03 20:56:22 UTC,"Boaz, I've filed bug 1831498 for tracking the radeon bug, though I'm a bit surprised no-one has filed this issue before now. Anyway, please test the update once it's available."
1824111,2019-06-06 17:25:11 UTC,"Hello Timo, or anyone else affected,"
1824111,2019-06-06 17:26:08 UTC,"Hello Timo, or anyone else affected,"
1824111,2019-06-06 17:26:55 UTC,"Hello Timo, or anyone else affected,"
1824111,2019-05-29 20:43:49 UTC,"Hello Timo, or anyone else affected,"
1824112,2019-08-15 11:00:44 UTC,https://github.com/juju/charm-helpers/pull/341
1824112,2020-02-19 13:52:44 UTC,"Change abandoned by Alex Kavanagh (tinwood) (<email address hidden>) on branch: master
Review: https://review.opendev.org/651982
Reason: Abandoning as disco is end of life."
1824112,2019-08-15 11:11:21 UTC,https://github.com/juju-solutions/layer-basic/pull/135
1824112,2019-08-15 11:10:42 UTC,https://review.opendev.org/#/c/676675/
1824112,2019-08-15 11:02:52 UTC,https://review.opendev.org/#/c/655394/
1824112,2019-08-15 10:59:28 UTC,https://review.opendev.org/#/c/655814/
1824112,2019-04-10 09:50:05 UTC,SUCCESS
1824112,2019-04-12 06:08:04 UTC,"Adding this to the wheelhouse.txt appears to fix the issue on Disco:
    setuptools>=40.6.0
    wheel"
1824112,2019-04-11 23:50:05 UTC,I was able to replicate this on Bionic simply by unpinning the pip requirement in layer:basic's wheelhouse.txt.  So it seems that it may have something to do with the newer version of pip that the charm starts out using to bootstrap itself when deploying on Disco.
1824112,2019-04-11 15:35:20 UTC,"Looking at this some more reveals that it is a difference in what version of Python package dependencies we need on the different distributions, so we will need to find a good set of lower/upper constraints that works across all supported distributions and include those in the Octavia charm wheelhouse.txt."
1824112,2019-07-12 03:42:05 UTC,Fixing this issue is a bit entangled as it involves changing the ``layer-basic`` configuration to not include system python packages and updating ``layer-basic``'s wheelhouse.  A consequence of not including system python packages is that we no longer can use the ``python-apt`` library as it is not feasible to distribute as a wheel with support for multiple Ubuntu releases.
1824112,2019-04-10 09:49:34 UTC,"# /var/lib/juju/agents/unit-octavia-0/.venv/bin/python3 -m pip install --verbose --log /tmp/pip --ignore-installed --no-user --prefix /tmp/pip-build-env-mf66uthh --no-warn-script-location --no-binary :none: --only-binary :none: --no-index --find-links wheelhouse -- setuptools>=18.5 wheel ""cffi>=1.8,!=1.11.3; python_implementation != 'PyPy'""
  Could not find a version that satisfies the requirement wheel (from versions: )
No matching distribution found for wheel
# cat /tmp/pip
Ignoring indexes: https://pypi.org/simple
Created temporary directory: /tmp/pip-ephem-wheel-cache-q9sr7v7k
Created temporary directory: /tmp/pip-req-tracker-helce6r8
Created requirements tracker '/tmp/pip-req-tracker-helce6r8'
Created temporary directory: /tmp/pip-install-fb08ewql
Looking in links: wheelhouse
Collecting setuptools
  0 location(s) to search for versions of setuptools:
  Skipping link wheelhouse (from -f); not a file
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/pyaml-18.11.0.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/asn1crypto-0.24.0.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/cryptography-2.6.1.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/python-keystoneclient-3.19.0.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/oslo.config-6.8.1.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/cliff-2.14.1.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/jsonpatch-1.23.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/prettytable-0.7.2.tar.bz2; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/oslo.utils-3.40.3.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/cmd2-0.9.11.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/decorator-4.4.0.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/appdirs-1.4.3.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/pyinotify-0.9.6.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/Jinja2-2.10.1.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/oslo.context-2.22.1.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/unit-octavia-0/charm/wheelhouse/cffi-1.12.2.tar.gz; Missing project version for setuptools
  Skipping link file:///var/lib/juju/agents/uni..."
1824117,2020-01-29 10:50:11 UTC,"------- Comment From <email address hidden> 2020-01-29 05:40 EDT-------
For completeness reasons some more details:
OSD interfaces of an LPAR in a CEC in (traditional) PRSM mode do not provide persistent MAC addresses.
For DPM mode this was solved, there the OSD interfaces do provide consistent MACs.
(HiperSockets interfaces in LPARs, OSD and HiperSockets in zVM guests also provide consistent MACs in PRSM mode and DPM mode)."
1824117,2020-01-29 11:04:14 UTC,Thx for the details - that's fine since we focus on DPM systems only with that (because there are even more features we need that only DPM provides).
1824117,2019-06-03 14:41:48 UTC,Waiting for an update from IBM - setting to Incomplete for now.
1824117,2020-01-28 15:29:44 UTC,"------- Comment From <email address hidden> 2020-01-28 10:19 EDT-------
Fix provide with z14 GA2 - Driver 32."
1824118,2019-06-04 04:35:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824118,2020-03-23 13:48:21 UTC,"Same here, trying to share my USB tethered internet connection."
1824118,2020-09-28 06:00:49 UTC,"Same problem affects me on Ubuntu 20.04 system. I have wifi adapter configured as hotspot. The hotspot also seems to be working normally but the log files are full of messages:
wpa_supplicant[1359]: wlp9s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1"
1824118,2020-10-21 03:39:31 UTC,"Same problem here. If I use my WiFi as a normal interface, no issues at all. I have wired ethernet and use this as a hotspot for some devices and once every second I see:"
1824119,2020-08-21 15:14:38 UTC,"Reviewed:  https://review.opendev.org/747159
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=88e450a6bbe5a484b50aee7e41f916d6bf926414
Submitter: Zuul
Branch:    master"
1824119,2020-06-25 14:33:21 UTC,"Also, does it in ussuri, and I expect train. (just hit it today on a mojo run with ussuri)."
1824119,2020-08-20 13:21:48 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/747159"
1824121,2019-09-13 16:05:50 UTC,This issue was fixed in the openstack/mistral 9.0.0.0b1 development milestone.
1824121,2019-05-16 08:53:18 UTC,"Reviewed:  https://review.opendev.org/652575
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=83c541acbfa88a92fbcd218c5fab5fabd44623b5
Submitter: Zuul
Branch:    master"
1824131,2019-04-18 13:10:44 UTC,Is this suppose to work? Can I get an answer to this?
1824131,2019-04-23 10:19:23 UTC,No I don't think this is mean't to work:
1824131,2019-04-23 10:32:15 UTC,However file is for sample; this gets configured in pipeline.yaml rather than event_pipeline.yaml
1824135,2019-06-18 09:19:05 UTC,log of 4.15.0-52-generic bionic with nvidia-390 installed and the command:
1824135,2019-06-18 06:17:47 UTC,log of 4.15.0-52-generic bionic and the command:
1824135,2019-05-15 10:40:50 UTC,It's able to reproduce with fwts (19.03.00-0ubuntu1~b).
1824135,2019-06-18 09:59:27 UTC,disco (5.0.0-17-generic) could reproduce this issue.
1824135,2019-05-09 00:49:06 UTC,I also notice it is using nouveau. Any chance we can try with NV's proprietary driver too?
1824135,2019-05-09 00:48:30 UTC,"FWTS uses ""g_dbus_proxy_call_sync"" to perform suspend. This can be related to gnome (and therefore related to VGA driver).. Let's try 19.04 (gnome shell 3.22) again."
1824135,2019-04-26 10:00:07 UTC,"""systemctl suspend"" could resume the system from suspending status successfully."
1824135,2019-04-26 09:41:02 UTC,It looks like this is an issue directly related to fwts because I could reproduce the issue with
1824135,2019-04-10 11:43:29 UTC,If we tried to dump /var/log/syslog when calling
1824135,2019-04-10 11:41:11 UTC,I feel like it is caused by fwts indirectly because the suspend/suspend_advanced_auto job calls checkbox-support-fwts_test to suspend.
1824135,2019-04-10 11:38:29 UTC,apport information
1824135,2019-04-10 11:38:27 UTC,apport information
1824135,2019-04-10 11:38:11 UTC,apport information
1824135,2019-04-10 11:38:24 UTC,apport information
1824135,2019-04-10 11:38:22 UTC,apport information
1824135,2019-04-10 11:38:20 UTC,apport information
1824135,2019-04-10 11:38:19 UTC,apport information
1824135,2019-04-10 11:38:17 UTC,apport information
1824135,2019-04-10 11:38:16 UTC,apport information
1824135,2019-04-10 11:38:14 UTC,apport information
1824135,2019-04-10 11:38:13 UTC,apport information
1824135,2019-04-10 11:38:09 UTC,apport information
1824135,2019-04-10 11:38:07 UTC,apport information
1824135,2019-04-10 11:38:06 UTC,apport information
1824135,2019-04-10 11:38:25 UTC,apport information
1824136,2020-11-24 09:17:42 UTC,Still visible on B-gcp-4.15.0-1088.101
1824136,2019-04-19 06:46:59 UTC,k8s.io/kubernetes/pkg/master test passed with Bionic GKE.
1824136,2019-06-03 16:19:40 UTC,affects linux-gcp 4.18.0-1012.13~18.04.1
1824136,2019-06-03 16:22:30 UTC,also affects linux-gke 4.15.0-1033.35
1824136,2019-12-10 04:42:31 UTC,"scheduler and spdy passed on Eoan 5.3 GCP (5.3.0-1010)
ok k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler	48.528s
ok k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpstream/spdy	0.197s"
1824140,2019-04-19 02:57:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824148,2019-04-10 13:44:11 UTC,Agreed. Alternatively if want to cover the not-found situation we could define the iface names as patterns and resolve the patterns at charm config time with the constraint that we require exactly one match
1824148,2019-04-10 13:57:17 UTC,I like that idea!
1824150,2019-04-14 12:51:45 UTC,some updates
1824150,2019-04-15 06:31:09 UTC,another some update
1824150,2019-04-15 08:55:50 UTC,I have found that openstack alarm list use public url which need certificate indeed but other commands which not related to aodh are using internal url so we need to make the alarms related commands' to use internal url
1824155,2019-05-05 12:51:08 UTC,This bug was fixed in the package gnome-flashback - 3.32.0-1ubuntu1
1824155,2019-05-04 15:13:04 UTC,"Hi,"
1824155,2019-05-02 16:37:11 UTC,"It is not hardcoded, I think... The default now is always FALSE, but with xsettings overrides user still can change that."
1824155,2019-05-02 16:13:17 UTC,@Alberts
1824155,2019-04-30 08:33:25 UTC,What is last release it worked? Check org.gnome.gnome-flashback.workarounds fix-app-menu setting...
1824155,2019-04-15 19:01:30 UTC,This is not an appmenu bug. Gnome flashback session disables showing appmenu in the panel. You need to override gtk-shell-shows-appmenu key. Please change affected project to gnome-flashback.
1824155,2019-04-30 08:52:01 UTC,"Khurshid, what value it must have?"
1824156,2019-09-25 12:27:06 UTC,This seems to have been implemented here https://github.com/snapcore/snapd/pull/7272
1824158,2019-12-03 11:18:48 UTC,This was fixed in snapd 2.41 release and in corresponding version of the package in Fedora.
1824158,2019-11-25 21:48:22 UTC,"Maciej, was this ever solved? I don't have a Fedora system immediately available to check this on"
1824158,2019-04-10 14:17:26 UTC,"On Fedora, the interpreter is #!/usr/bin/sh. The change is introduced automatically when building the RPM."
1824158,2019-05-07 13:17:06 UTC,I can confirm that this change helps on Fedora 29:
1824160,2019-06-25 13:14:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824160,2019-06-25 13:15:02 UTC,How do I update this on my system?
1824160,2020-02-12 07:17:33 UTC,Today is 2020-02-12 and this problem still exists. How to be?
1824161,2020-07-23 06:21:21 UTC,Project is no longer maintained.
1824162,2019-10-16 10:01:25 UTC,"My initial conclusion about go-udev being the culprit was premature, the socket closing & quit channel code looks fine after all, the problem lies somewhere else and may be something in the go runtime stack and it's very unclear for the time being."
1824162,2019-10-16 07:34:43 UTC,"The bug may occur regardless of experimental hotplug flag, and may prevent clean shutdown of snapd - of course only if there is udev netlink activity, therefore setting to critical."
1824162,2019-10-15 13:55:43 UTC,It looks like an udev/netlink related panic in snapd
1824162,2019-10-15 16:15:00 UTC,I think the bug is in the go-udev package (upstream). The Monitor() function returns a 'quit' channel that the caller uses to stop processing. Monitor() runs a backgroud goroutine that monitors/reads from netlink socket and stops if quit channel is written to. I think the problem is that the quit channel is a buffered/non-blocking channel - writing to it and calling Close() on the netlink object right afterwards (which we do when stopping snapd) means we might be closing the socket and disposing the object when the background routine is reading netlink events.
1824166,2019-09-25 12:29:11 UTC,Deepin is not a part of the snapd test suite. I would encourage anyone in the Deepin community to step up and work with us on addressing that.
1824166,2019-09-25 13:01:25 UTC,@zyga it looks like it's the opposite case.  Classic snaps can resolve DNS but strict snaps can not.  The example given is firefox can't and vscode can access the network.
1824166,2019-09-25 13:04:02 UTC,Thank you for clarifying this Ken. I've updated bug triage information now.
1824166,2019-09-25 13:07:34 UTC,This theory seems to be confirmed by this forum post https://forum.snapcraft.io/t/deepin-debian-9-snaps-have-no-internet-connection/11295
1824167,2019-06-27 02:52:19 UTC,System is 2+3. Please check attached Test execution log for all information you want.
1824167,2019-06-26 21:41:02 UTC,"@ppeng, please provide a bit more info:
1. what was your deployment like? for example, 2+2+2 (computer nodes)??
2. server group info in details, output from cmd: openstack server group list and openstack server group show <server_group_uuid>
3. before live-migration, where was VM1 and VM2 running respectively?
4. after live-migration, when saying ""successfully live_migrate VM_1, but failed to live_migrate VM_2"", where was VM_1 located? was it migrated to a different host?"
1824167,2019-06-26 19:45:29 UTC,Bruce can you try and find another person to prime this LP as Gerry is tied up with finishing his SB and other stx2.0 gating LPs
1824167,2019-06-27 20:23:00 UTC,"I deployed a 2+3 StarlingX and created 2 VMs by following the operations captured from ""test_execution_log.txt"", and I got some findings:"
1824167,2019-04-11 14:00:42 UTC,Expecting this to be resolved by the backport of Artom's changes from Train.
1824167,2019-04-10 20:01:53 UTC,Marking as release gating; live migration failure - 100% reproducible as per the reporter.
1824167,2019-06-26 11:58:25 UTC,I think this is separate from Artom's changes.  We need to retest/investigate this on a more recent build.
1824168,2019-04-10 15:38:31 UTC,"Result of:
strace -ff -o strace.txt /home/tomwardill/.steam/steam/steamapps/common/Factorio/bin/x64/factorio"
1824168,2019-04-10 15:44:43 UTC,"I'm running the proprietary nvidia drivers at release 390, on 19.04."
1824168,2019-04-13 14:49:51 UTC,"I had a look at the snap in question (Godot) and looked at how it is built. I believe, though I'm not sure of it, that without changing how it is build and how GL drivers are injected we cannot address this issue."
1824168,2019-10-17 10:21:05 UTC,"I can reproduce the issue with my GTX Titan X, proprietary nvidia drivers at 418 and Ubuntu 19.04 with snapd master. Same error messages"
1824168,2019-10-17 10:24:04 UTC,"Godot is a classic snap and cannot benefit from the mount namespace arrangement provided by snapd. As hinted in the previous comments, it's best if you bring this is up with Godot developers. The snap lists https://github.com/godotengine/godot/issues as their contact page."
1824168,2019-12-10 21:07:15 UTC,(Commenting here instead of a new issue since the symptoms/error messages seem close)
1824168,2020-02-09 04:17:37 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1824168,2020-02-09 04:17:40 UTC,[Expired for snapd because there has been no activity for 60 days.]
1824171,2020-08-18 15:33:17 UTC,"Did some digging on this one
hots 30 and 31 both grabbed the meta data and then started downloading the images
host 32 however got the meta data, and then just didnt progress from there"
1824174,2019-11-25 18:53:55 UTC,"@Peng, Is this issue still reproducible in stx master with openstack train?"
1824174,2019-11-26 18:24:05 UTC,Closing as the reporter confirmed that this issue is no longer reproducible.
1824174,2019-11-25 19:12:18 UTC,Not seeing this issue recently.
1824174,2019-07-13 00:16:02 UTC,"The external network cannot ping vm.
It seems to be the same as the bug below.
https://bugs.launchpad.net/starlingx/+bug/1836252"
1824174,2019-08-23 17:49:45 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1824174,2019-07-10 06:57:43 UTC,"Verification environment: bootimg iso version 20190623, Simplex and Duplex."
1824174,2019-04-10 19:55:04 UTC,Marking as release gating until further investigation; issue appears intermittent.
1824174,2019-07-12 09:24:42 UTC,issue reproduced by Neusoft engineer.
1824175,2019-04-10 15:30:08 UTC,This change was made by a bot.
1824175,2020-06-09 04:34:03 UTC,Please test 20.04.
1824175,2020-06-17 22:39:25 UTC,I'm not able to reproduce this using 5.4.0-37-generic
1824175,2020-08-17 04:17:28 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824176,2019-09-13 16:54:53 UTC,We have simply removed the tarball and gone w/ a separate init script. Closing this bug as invalid.
1824180,2019-05-14 13:58:06 UTC,"That is not GWorkspace in the screenshot, please reassign it to something with GNOME"
1824181,2019-04-10 16:05:04 UTC,"LP1824184 https://bugs.launchpad.net/opensrf/+bug/1824184
is the followup to this where we actually start making use of it."
1824181,2019-06-07 15:35:22 UTC,"Pushed to master, rel_3_1, and rel_3_0. Thanks, John!"
1824181,2019-04-10 15:51:50 UTC,"OpenSRF branch is working/user/jmerriam/allow_log_subs:
https://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/jmerriam/allow_log_subs"
1824182,2019-04-14 17:25:34 UTC,"Can you show your Interactive router settings?  And the settings of the net you are routing?  I experience different behavior with your test board, so I'd like to know the differences."
1824182,2019-07-25 15:58:29 UTC,When trying to route out of the corner pads as shown in the video the track does seem to want to jump away from the adjacent pad.
1824182,2019-08-21 02:37:52 UTC,"Fixed in revision 06cb21cc4797d613c9a8e1bacab18405af3920c3
https://git.launchpad.net/kicad/patch/?id=06cb21cc4797d613c9a8e1bacab18405af3920c3"
1824182,2019-04-14 19:08:51 UTC,"I'm not sure what settings of the net do you mean. Isn't everything in the board file?
The ""Magnetic points"" section in Preferences > Pcbnew does not have any effect on this."
1824182,2019-04-14 02:31:37 UTC,Could you attach a sample board that shows this issue?
1824182,2019-04-10 16:34:17 UTC,"Look at your Interactive Router settings (Right-click to get menu) and try to toggle ""Optimize Pad Connections"""
1824182,2019-04-13 13:13:10 UTC,"I had such a problem, turned off this option and the difficulties disappeared. Maybe she is not needed at all. What does she do? How to optimize?"
1824182,2019-04-10 17:54:23 UTC,I cannot recreate the issue.  Would you be able to attach your board or similar one that exhibits the behavior to this report?
1824182,2019-04-10 17:40:10 UTC,"It was already toggled.
Untoggled, i can see a slight change when going TO the pad, but going FROM the pad still has the same behaviour."
1824182,2019-04-14 00:39:03 UTC,"For me, ""Optimize Pad Connections"" does not help."
1824184,2019-04-10 16:03:14 UTC,"OpenSRF branch is working/user/jmerriam/slow_logging_use_subs:
https://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/jmerriam/slow_logging_use_subs"
1824184,2019-06-07 15:34:56 UTC,"Pushed to master, rel_3_1, and rel_3_0. Thanks, John!"
1824186,2020-01-14 01:24:52 UTC,this occurs for me as well with 3ctlr_3comp.yml
1824191,2019-04-10 16:37:04 UTC,"It seems the issue happens when GTK+ theme is selected in Chromium, it doesn't show with the ""classic"" theme"
1824191,2019-04-20 08:54:25 UTC,This happens in 19.04 too
1824191,2019-06-19 12:29:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824195,2020-04-15 17:02:03 UTC,I reproduced this in my duplicate bug Bug #1774476 reported 2018-05-31 on the original 18.04 ( https://lists.ubuntu.com/archives/ubuntu-announce/2018-April/000231.html )
1824195,2019-04-16 11:36:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824195,2019-04-16 12:00:10 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1824195,2019-04-17 23:42:37 UTC,"I was able to recreate this today with image 'Ubuntu 19.04 ""Disco Dingo"" - Release amd64 (20190416)'. Even starting up a virtual machine with no network produced the same results."
1824195,2019-06-30 18:33:46 UTC,Repod in my duplicate bug with 19.10 daily about the updates checkbox.
1824195,2020-04-16 19:18:15 UTC,This bug was fixed in the package ubiquity - 20.04.12
1824195,2020-08-18 16:48:09 UTC,"eoan has reached end of life, so this bug will not be fixed for that release"
1824205,2020-01-24 08:49:44 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1824205,2019-04-15 17:50:31 UTC,Only Line Out works
1824205,2019-04-10 17:05:18 UTC,Line Out it work but Headphone output doesn't appear.
1824211,2019-04-10 17:30:23 UTC,This is probably a packaging problem on the nvidia drivers rather than a bug in Ubiquiuty.  Moving there for more ideas.
1824212,2019-06-04 17:45:01 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-05-27 15:06:55 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-06-04 17:24:44 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-06-04 17:41:44 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-06-24 09:46:02 UTC,This bug was fixed in the package gce-compute-image-packages - 20190522-0ubuntu1~19.04.0
1824212,2020-05-28 22:07:25 UTC,This bug was fixed in the package gce-compute-image-packages - 20190315-0ubuntu1~14.04.0
1824212,2019-06-24 10:17:51 UTC,This bug was fixed in the package gce-compute-image-packages - 20190522-0ubuntu1~18.04.0
1824212,2019-06-24 11:30:40 UTC,This bug was fixed in the package gce-compute-image-packages - 20190522-0ubuntu1~16.04.0
1824212,2019-09-23 19:29:18 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for trusty for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1824212,2019-05-27 14:29:51 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-06-24 09:52:16 UTC,This bug was fixed in the package gce-compute-image-packages - 20190522-0ubuntu1~18.10.0
1824212,2019-05-27 14:19:39 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-06-04 17:37:36 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-05-23 11:24:48 UTC,Since 20190521 upstream release includes the 20190315 I'm marking this bug as a duplicate of the one targeting the newer upstream release.
1824212,2019-05-27 14:15:10 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-04-22 12:44:07 UTC,"@vorlon,"
1824212,2019-04-22 14:01:33 UTC,This bug was fixed in the package gce-compute-image-packages - 20190315-0ubuntu1
1824212,2019-04-25 12:55:00 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-04-25 13:05:43 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-04-18 21:31:24 UTC,"Balint,"
1824212,2019-04-25 13:13:45 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-04-25 13:30:19 UTC,"Hello Balint, or anyone else affected,"
1824212,2019-05-22 20:11:01 UTC,Due to regressions the targeted upstream version moved to 20190521.
1824212,2019-04-25 13:10:46 UTC,"Hello Balint, or anyone else affected,"
1824215,2019-04-10 18:42:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824217,2019-04-10 19:16:37 UTC,"Suggest adding function systemd_is_installed() and add another elif systemd_is_installed():  return service('is-active', service_name) before line https://github.com/juju/charm-helpers/blob/master/charmhelpers/core/host.py#L308 that checks.  This would cover a more generic case of using the os-native tools on trusty before reverting back to systemd, but would cover both snap and non-snap systemd-only services installed on trusty."
1824217,2020-07-17 16:28:18 UTC,"Looking for Reviews:
  https://github.com/juju/charm-helpers/pull/494"
1824217,2020-07-17 18:15:21 UTC,when charmhelpers 20.17 is available from pypi: re-run tests on prometheus-ceph-exporter and push charm to charm story
1824217,2020-07-17 18:17:03 UTC,https://pypi.org/project/charmhelpers/
1824217,2020-09-28 18:02:15 UTC,"Available here:
https://jaas.ai/u/llama-charmers-next/prometheus-ceph-exporter/5"
1824228,2020-10-09 22:09:07 UTC,Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64
1824228,2019-11-07 07:42:17 UTC,Failed on Oracle B-5.0 (node VM.DenseIO1.8 / VM.Standard1.4)
1824228,2020-10-09 14:30:01 UTC,Spotted on Focal azure : 5.4.0-1029.29 : amd64
1824228,2020-04-22 05:15:47 UTC,"Found on Oracle Bionic 5.3
5.3.0-1015.16~18.04.1"
1824228,2019-11-06 07:29:39 UTC,Passed with Oracle B-4.15 (node VM.DenseIO1.8 / VM.Standard1.4)
1824228,2020-10-09 15:33:19 UTC,"Apologies, the above was on Bionic, not Focal. Spotted on Bionic azure : 5.4.0-1029.29~18.04.1 : amd64"
1824228,2019-06-03 13:20:29 UTC,"Found on B-4.15 Oracle, instance VM.DenseIO2.16
TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append ""ept_access*""
FAIL ept (8489 tests, 5 unexpected failures)"
1824228,2019-05-02 13:50:40 UTC,"also affects disco, linux-azure 5.0.0-1005.5"
1824228,2019-04-10 20:16:37 UTC,"also affects bionic, linux-azure 4.18.0-1015.15~18.04.1"
1824228,2019-04-10 19:44:35 UTC,"Affected instances:
Standard_D2s_v3
Standard_D2_v3
Standard_DC2s
Standard_E2s_v3
Standard_F2s_v2"
1824228,2019-10-30 15:10:21 UTC,Also failing in the Eoan/5.3 kernel.
1824230,2019-04-11 10:16:34 UTC,I have not been able to reproduce this.
1824230,2019-06-11 04:17:23 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1824234,2019-04-11 21:22:22 UTC,"Experiencing the same problem trying to build an AMI using ami-03804ed633fe58109 as the base image:
""bionic server release 20190403 ebs-ssd amd64 us-west-2 ami-03804ed633fe58109 hvm"""
1824234,2019-04-11 21:22:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824234,2019-04-12 08:47:48 UTC,"Same here on Linux Mint 19.1 (Bionic as base).
Obvious workaround: rm -rf /var/cache/snapd/aux ; apt purge -y snapd"
1824234,2019-04-12 09:20:48 UTC,This is fixed in 2.38
1824235,2019-06-15 04:17:21 UTC,[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]
1824235,2019-04-13 01:15:20 UTC,"I may have not understood the terminology. Can you be more specific? I used
ubuntu-bug to file the issue and I see a crash report with these details."
1824235,2019-04-15 06:03:38 UTC,"See http://wiki.ubuntu.com/DebuggingProgramCrash for some details on the topic, but it's a program error which leads the application to close in a specific way"
1824235,2019-04-12 16:18:56 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1824235,2019-04-12 16:19:19 UTC,there is no crash in this report
1824236,2019-05-31 11:37:16 UTC,Thanks to both of you Ioanna and Richard for your quick reply.
1824236,2019-05-31 12:24:50 UTC,Sponsoring for 'E'.
1824236,2019-05-31 14:31:26 UTC,"Patch submitted to Debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929807"
1824236,2019-05-31 17:18:05 UTC,This bug was fixed in the package libguestfs - 1:1.40.2-2ubuntu2
1824236,2019-06-04 19:00:21 UTC,"Hello Ioanna, or anyone else affected,"
1824236,2019-06-04 19:28:42 UTC,"Hello Ioanna, or anyone else affected,"
1824236,2019-06-04 19:31:54 UTC,"Hello Ioanna, or anyone else affected,"
1824236,2019-06-06 09:47:29 UTC,Verification on Disco.
1824236,2019-06-06 10:35:30 UTC,Verification on Bionic.
1824236,2019-06-12 20:40:39 UTC,This bug was fixed in the package libguestfs - 1:1.40.2-1ubuntu1.1
1824236,2019-06-12 20:45:28 UTC,"The verification of the Stable Release Update for libguestfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824236,2019-06-12 20:46:07 UTC,This bug was fixed in the package libguestfs - 1:1.38.4-1ubuntu2.1
1824236,2019-05-31 11:01:48 UTC,Thanks Eric for reviewing the debdiffs.
1824236,2019-06-12 20:46:46 UTC,This bug was fixed in the package libguestfs - 1:1.36.13-1ubuntu3.3
1824236,2019-06-06 09:56:32 UTC,Verification on Cosmic.
1824236,2019-05-31 08:14:22 UTC,"It doesn't delete the system file, just a copy in a private tree.  This
code can never run outside the appliance."
1824236,2019-05-31 11:15:56 UTC,Concerning the changes to debdiff :
1824236,2019-05-31 00:45:40 UTC,Thanks Ioanna for providing a patch and work with upstream maintainer.
1824236,2019-04-18 09:55:52 UTC,"I posted a potential fix here:
https://www.redhat.com/archives/libguestfs/2019-April/msg00129.html"
1824236,2019-05-15 18:18:06 UTC,Debdiff for Bionic.
1824236,2019-05-15 18:19:23 UTC,Debdiff for Disco.
1824236,2019-05-15 18:19:25 UTC,Debdiff for Disco.
1824236,2019-05-15 18:19:55 UTC,Debdiff for Eoan.
1824236,2019-05-15 20:24:23 UTC,"The attachment ""lp1824236_bionic.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1824236,2019-05-16 12:48:49 UTC,[sts-sponsor]
1824236,2019-05-15 18:18:48 UTC,Debdiff for Cosmic.
1824236,2019-05-30 11:46:26 UTC,New debdiff for E.
1824236,2019-05-30 11:59:46 UTC,New debdiff for D.
1824236,2019-05-30 13:18:01 UTC,New debdiff for C.
1824236,2019-05-30 13:23:10 UTC,New debdiff for B.
1824236,2019-05-31 01:00:03 UTC,to continue my comment #16 ....
1824236,2019-05-30 23:42:52 UTC,Ok I'll review the debdiff for 'Eoan' tomorrow.
1824236,2019-05-30 11:45:40 UTC,"Patch merged upstream :
https://github.com/libguestfs/libguestfs/commit/2bb6be333e6347d3f18856627d8ad8e50b8e5427"
1824237,2019-04-11 13:50:32 UTC,"I was just able to reproduce this on our travis instance. In the /var/log/apt/history.log I see:
""""""
Start-Date: 2019-04-11  13:12:03
Commandline: apt-get remove -y --purge -y snapd
Purge: snapd:amd64 (2.37.4+18.04.1)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2019-04-11  13:12:12
""""""
and in term.log:
""""""
....
rm: cannot remove '/var/cache/snapd/aux': Is a directory^M
dpkg: error processing package snapd (--purge):^M
 installed snapd package post-removal script subprocess returned error exit status 1^M
Log ended: 2019-04-11  13:12:12
""""""
so I strongly suspect that this is the issue."
1824237,2019-04-11 12:38:01 UTC,I used:
1824237,2019-04-11 11:16:03 UTC,Looking at the ADT logs it looks like the tests started to fail at 2019-04-03 around 22:00utc.
1824237,2019-04-11 10:56:59 UTC,also - i get the same failure when testing with snapd_2.37.4+18.10.1.dsc so maybe this failure is coming from something outside the snapd package itself?  Maybe the autopkgtest pulls in snaps and/or github code that's changed recently and is causing the problem?
1824237,2019-04-11 10:55:12 UTC,"> I tried to reproduce it just now and ... nothing. It works:
"
1824237,2019-04-10 21:53:35 UTC,Additional IRC log with some useful information:
1824237,2019-04-11 09:52:52 UTC,I tried to reproduce it just now and ... nothing. It works:
1824237,2019-04-10 21:26:57 UTC,"for clarification, this is from the inside of an autopkgtest (cosmic) that's stopped on the failed test:"
1824237,2019-04-11 17:03:59 UTC,I looked into this a bit more and all the failures happen with 2.37.4 - the 2.38 SRU is actually fine and will fix this bug.
1824237,2019-04-11 10:49:00 UTC,I ran several more iterations without reproducing the problem. I will run some more but it would help if the reporter can clarify if the issue is still observed in the wild.
1824237,2019-04-11 18:07:58 UTC,"Thanks, Michael! Fixing the bug tags."
1824242,2019-04-16 15:13:53 UTC,Marking as 'invalid' cloud-images as this is not a issue particular to the cloud image build.
1824242,2019-10-29 21:23:05 UTC,The fix for the aux directory was released long ago. Marking as such.
1824242,2019-04-11 08:03:53 UTC,Thanks for the bugreport. This is fixed in xenial-proposed with snapd 2.38
1824245,2019-04-10 21:59:20 UTC,"I'll also note that it sometimes works with UEFI, but I've never gotten it to work with BIOS..."
1824245,2019-04-10 22:06:03 UTC,I'll note that this configuration is loop images on a disk that was created as a disk image file mounted as a loop.
1824245,2019-04-25 20:58:35 UTC,I've verified locally that this does fix my issue when I patch grub myself.
1824245,2019-05-20 13:23:05 UTC,Bump? What about Ubuntu 16.04?
1824245,2019-06-03 15:09:30 UTC,"cyphermox, could you please backport the fix for Ubuntu 16.04?"
1824245,2019-08-08 23:43:28 UTC,"cyphermox, if this helps, I've created a patch that directly applies on top of the existing grub2 sources reconstructed with `dpkg-source -x` that I've tested locally to work."
1824245,2019-09-16 14:17:55 UTC,The /sbin change there is wrong; please cherry-pick https://salsa.debian.org/grub-team/grub/commit/128487746598d3fac60569b11de12ffef58cd8f7 instead.
1824245,2019-09-16 15:14:55 UTC,"cjwatson, I've updated the patch accordingly..."
1824245,2019-11-29 12:31:14 UTC,"The bug description should follow the SRU style:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template"
1824245,2020-03-11 09:53:09 UTC,"An upload of grub2 to xenial-proposed has been rejected from the upload queue for the following reason: ""SRU information not provided.""."
1824247,2019-04-11 19:06:45 UTC,It looks like you have a PPA providing graphics drivers enabled which is causing the upgrade to fail. You should have received an error message like the following:
1824247,2019-06-12 04:17:24 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1824249,2019-04-10 23:33:13 UTC,provo a controllare cosa manca per linux-gnu
1824250,2019-07-30 17:12:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824251,2019-04-11 04:18:06 UTC,Maybe related to https://bugs.launchpad.net/kicad/+bug/1822852
1824251,2019-04-13 14:30:22 UTC,"Fixed in revision 3bdd69ad6bc6d3a7243bf6371137b82c1723d490
https://git.launchpad.net/kicad/patch/?id=3bdd69ad6bc6d3a7243bf6371137b82c1723d490"
1824253,2019-04-11 03:08:19 UTC,Changing the component for this bug.
1824253,2019-04-11 04:56:06 UTC,"I think you are saying that the device is hanging when you are reading a book sent to it from calibre. Is that correct? If so, it is more likely that the problem is on the device, not in calibre."
1824253,2019-04-11 04:58:46 UTC,"Just noticed the report summary mentioned a ""calibre database error"", but there is no mention of this in the details of the problem. What is the error? If it is one about the database version, then you should follow the instructions in the message. Otherwise, you need to give some details."
1824255,2020-01-26 07:21:21 UTC,"Ah, it's more nuanced. The deb in Xenial (still the default for the LP snap builders) doesn't have this problem. It regressed in the snap, both with and without bases. This should fix it for without bases: https://github.com/snapcore/snapcraft/pull/2893"
1824255,2020-01-29 00:35:07 UTC,OK I think I finally get it now :) Thanks for educating me everyone.
1824255,2020-01-30 15:58:20 UTC,"While there seems to be a regression, the bug here is explicitly about using command-chain for hooks and not the regression in wrapper generation we have."
1824255,2020-02-01 21:36:25 UTC,"> the bug here is explicitly about using command-chain for hooks and not the regression in wrapper generation we have.
"
1824255,2020-02-01 21:39:40 UTC,"Although it appears that, given https://github.com/snapcore/snapcraft/pull/2897 was merged. we're not going the command-chain route for master, which is also cool. I can confirm that hook wrappers in edge now get the environment placed within them. Question is, should that be Fix Committed for this bug, or would you like to track the hook command-chain work here instead (which needs a bit of unrelated work)?"
1824255,2020-01-25 21:16:05 UTC,"Ooo, I lied, that regressed in legacy as well."
1824255,2020-02-03 13:47:06 UTC,"To avoid further confusion, this bug is asking for adding environment for what is the `install` hook in my example (through command-chain), but if that is really wanted, just put it in a as seen below"
1824255,2020-02-03 16:33:59 UTC,"Sorry if I filed this bug poorly, but the original problem I had with this bug is that no hooks had environment setup for them, whether they were trampoline style hooks generated by a part or not. That's the bug I care about, it's fine to have hooks generated by a part for me, I just want them to have the same environment as apps."
1824255,2020-02-12 03:57:28 UTC,"OK then, this should be Fix Committed."
1824255,2020-02-21 11:46:01 UTC,Part of 3.10
1824255,2020-02-03 13:04:32 UTC,"Kyle, command-chain for hooks if they come from a part is fine."
1824255,2020-01-25 20:11:14 UTC,Note that this bug is a huge regression from snapcraft 2.x (i.e. snapcraft without bases) that hampers migration to using bases.
1824255,2019-12-11 15:53:49 UTC,One of my upcoming tasks is to use command-chain for hooks in core20+.
1824255,2019-12-11 15:14:56 UTC,"This is still a problem for snapcraft hooks, because even when I have a part that stages the hooks into $SNAPCRAFT_PART_INSTALL/snap/hooks/<hook-name> the generated hook in $SNAPCRAFT_PRIME/meta/hooks/<hook-name> just looks like this:"
1824255,2019-09-25 12:32:41 UTC,I don't believe this is something that requires changes to snapd itself. The format supports all kinds of hooks and the way they are executed does not need to change. I think this is a snapcraft-side feature to make it easier to define hooks.
1824255,2019-05-01 21:17:57 UTC,"I'd like to see us move to the `full` adapter by default, in which case using snapd's `command-chain` for hooks would be best. However, I think that ship has sailed until the next base is introduced given the backward-incompatible change to apps. So my recommendation is to just exec the generated chain in the hook's wrapper, keeping current behavior."
1824255,2019-05-01 21:12:24 UTC,"I see two ways to support this. Either snapcraft writes all hooks into the snap.yaml and uses snapd's `command-chain` directive and add the `assumes` (like the `full` adapter does for apps), or exec the command chain in the wrapper created for the hook."
1824255,2019-05-01 21:11:03 UTC,"As a work-around for this, if you define an app in snapcraft.yaml to use the full adapter, snapcraft still generates a command-chain that is usable for hooks that you can pass along to the snap.yaml using passthrough in the snapcraft.yaml like so:"
1824255,2019-05-01 21:06:10 UTC,"Confirmed, while a wrapper is still generated for hooks, wrappers don't include environment anymore-- that's all command chain, and hooks aren't using it like apps are."
1824255,2019-04-30 03:32:26 UTC,"Unfortunately, even after generating the hooks using a part in my snapcraft.yaml I can't get this to work, as the generated snap.yaml never specifies a command-chain for the hooks. I have tried also specifically mentioning the hooks in the top-level snapcraft.yaml with:"
1824255,2019-04-17 22:02:11 UTC,"Here's a quick one:
https://forum.snapcraft.io/t/golang-configure-hook-script/992/5?u=sergiusens"
1824255,2019-04-17 18:27:34 UTC,Actually I see from your comment it's snap/hooks not meta/hooks...
1824255,2019-04-17 18:26:28 UTC,"Can you give an example of creating hooks through a snapcraft part? Would we just copy hooks from somewhere in the git tree to $SNAPCRAFT_PART_INSTALL/meta/hooks/intstall, etc. ?"
1824255,2019-04-17 18:05:50 UTC,"In snapcraft, if you create the hook through a part, command-chain will be properly setup with the right environment, the hooks need logic to install to $SNAPCRAFT_PART_INSTALL/snap/hooks/<hook-name>"
1824255,2019-12-13 18:47:16 UTC,"Chris, if the snap.yaml does not have an entry for the hook, it is known as an implicit hook, and it should basically operate the same way as an explicitly declared hook in the snap.yaml without any plugs/environment set (but there have been bugs about this before). So it is not necessary to explicitly declare the hook in the snap.yaml or the snapcraft.yaml for snapd to use it at runtime."
1824256,2019-04-12 16:09:00 UTC,"<nhicher> apevec, weshay, rlandy: ticket #1690 for network issues on openstack-nodepool tenant"
1824256,2019-04-12 11:13:32 UTC,http://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-infra/tripleo-ci/master/periodic-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-master/6a18a34/logs/undercloud/home/zuul/overcloud_prep_images.log.txt.gz
1824256,2019-05-16 08:31:26 UTC,also removing promotion-blocker tag
1824256,2019-04-11 21:16:13 UTC,http://logs.rdoproject.org/17/651817/4/openstack-check/tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001/ad79b03/logs/undercloud/home/zuul/overcloud_prep_images.log.txt.gz
1824256,2019-04-11 01:57:07 UTC,"A number of engineers have seen these issues lately, the main intent here is warn infra, collect data and report details as we discover them"
1824256,2019-04-12 07:53:56 UTC,"Looks like this is similar to https://bugs.launchpad.net/tripleo/+bug/1790127/, cshastri is looking into it."
1824257,2019-04-23 18:21:55 UTC,"SOLVED. Some non-official package installed Evince through flatpak, which did not communicate properly with AUCTeX through D-Bus."
1824258,2019-04-11 02:21:06 UTC,crash at instalation into a SD card 32GB
1824259,2019-04-22 04:54:55 UTC,"Looks like put a wrong DMI matching string, could you upload the whole log of ""sudo dmidecode""."
1824259,2019-04-24 03:47:01 UTC,Here's the whole `sudo dmidecode` output (attached).
1824259,2019-04-24 04:46:51 UTC,"Please install this deb, and do the test as the #18."
1824259,2019-04-28 22:05:25 UTC,"OK, this second deb seems to solve my problem! The headphone jack state is detected correctly without the quirk! Thanks!"
1824259,2019-04-29 03:45:31 UTC,"OK, sent the patch to review."
1824259,2019-05-16 15:03:51 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1824259,2019-05-17 09:31:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1824259,2019-05-23 00:01:08 UTC,"Do I have to downgrade my system from Dingo to Cosmic in order to test this in Cosmic, to keep my bug from being closed?"
1824259,2019-05-23 00:33:54 UTC,"With chance of regression quite low, we will not remove this particular fix prior to release"
1824259,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1824259,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1824259,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1824259,2019-06-09 16:55:00 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1824259,2019-04-22 03:32:29 UTC,"Hello,"
1824259,2019-05-20 14:02:19 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1824259,2019-04-14 02:09:50 UTC,"Please install this deb for kernel-5.0.0-8-generic, and remove quirk=0x21 for that module, reboot and redo the test."
1824259,2019-04-13 19:18:24 UTC,apport information
1824259,2019-04-13 19:18:58 UTC,apport information
1824259,2019-04-11 02:55:28 UTC,If I save the ALSA state with the headphones unplugged to a file:
1824259,2019-04-11 04:26:51 UTC,"This may be a kernel driver bug, and a regression from 4.12. See http://www.lattepanda.com/topic-p24689.html?sid=1fa88916eb19dd9d65e0abd3ecbf6210#p24689"
1824259,2019-04-11 05:24:35 UTC,"This is actually a kernel bug, in Linux. The issue is the absence of platform data for this particular board in the snd_soc_rt5645 module."
1824259,2019-04-13 19:23:37 UTC,"I set the bug to Confirmed, despite being the original reporter, because the bot told me to."
1824259,2019-04-13 19:18:09 UTC,apport information
1824259,2019-04-13 19:18:11 UTC,apport information
1824259,2019-04-13 19:18:18 UTC,apport information
1824259,2019-04-11 05:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824259,2019-04-13 19:18:21 UTC,apport information
1824259,2019-04-13 19:18:23 UTC,apport information
1824259,2019-04-13 19:18:26 UTC,apport information
1824259,2019-04-13 19:18:27 UTC,apport information
1824259,2019-04-13 19:18:32 UTC,apport information
1824259,2019-04-13 19:18:19 UTC,apport information
1824260,2020-10-26 23:56:39 UTC,"On 2020-10-27 00:06, xiota wrote:

> not all monospace fonts have the same metrics as Courier
"
1824260,2020-10-28 09:37:44 UTC,Thank you. I have done as you suggest.  Upstream merge request is here:
1824260,2020-10-27 18:42:31 UTC,"Ok, I changed the Ubuntu patch in accordance with your suggestion. Maybe a bit better..."
1824260,2020-11-09 21:40:33 UTC,This bug was fixed in the package fontconfig - 2.13.1-4.2ubuntu2
1824260,2020-10-27 11:43:34 UTC,"> How do you make it replace CourierStd with Ubuntu Mono?
> Do you have custom font configuration which affect it?
"
1824260,2020-10-27 11:21:23 UTC,The following config would be better than the one I proposed earlier:
1824260,2020-10-27 02:46:17 UTC,"On 2020-10-27 02:32, xiota wrote:

> I just checked a few fonts. The fonts I thought might have problems are
> mostly fine. Only some consecutive capitals clash, like WWW.
"
1824260,2020-10-27 01:32:39 UTC,"I just checked a few fonts. The fonts I thought might have problems are mostly fine. Only some consecutive capitals clash, like WWW."
1824260,2020-10-26 23:06:28 UTC,The proposed patch might not fix the problem on all machines because not all monospace fonts have the same metrics as Courier. So it would be good to also add the following to 30-metric-aliases.conf:
1824260,2019-04-11 16:26:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824260,2020-10-26 18:58:04 UTC,"CourierStd is not defined in any of the config files at `/etc/fonts/conf.d`, so it falls back to sans-serif, not monospace. On my computer, the sans-serif fallback is set to Ubuntu."
1824260,2020-10-26 11:12:16 UTC,"On 2020-10-26 10:33, Sebastien Bacher wrote:

> Gunnar do you have any clue maybe about the issue there or an
> opinion about the proposed config?
"
1824260,2020-10-26 09:33:28 UTC,"Thanks for the comment and details, unsure why it does pick Ubuntu font as an alternative to CourierStd and if that's a problem with the fonts or configuration"
1824260,2020-10-24 15:54:57 UTC,"Looking at `ss-5.pdf`, I saw the same rendering issue. The problem appears to be associated with font substitution. In particular, CourierStd is replaced with Ubuntu, which obviously won't render properly."
1824260,2019-04-12 08:07:10 UTC,THanks!
1824260,2019-04-11 17:22:07 UTC,Update: poppler issue here:
1824260,2019-04-11 16:14:06 UTC,Done: https://gitlab.gnome.org/GNOME/evince/issues/1127
1824260,2019-04-11 12:30:59 UTC,"Thank you for your bug report, could you also report it upstream to the people writting the software on https://gitlab.gnome.org/GNOME/evince/issues ?"
1824260,2020-10-26 20:09:34 UTC,"Right xiota, and I think adding CourierStd to 45-latin.conf is sufficient."
1824262,2019-04-11 07:15:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824262,2020-01-24 09:01:39 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1824263,2019-09-25 06:52:39 UTC,"Reviewed:  https://reviews.mahara.org/10329
Committed: https://git.mahara.org/mahara/mahara/commit/c9a33e3ea7ebb4cee8a09bebf9ca35f4b64e2f3f
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1824263,2019-09-24 22:24:57 UTC,"Gerrit/Patchset: https://reviews.mahara.org/mahara refs/changes/29/10329/2
Browser tested: Firefox & Chrome
Theme used: Default"
1824263,2019-09-10 04:06:04 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10329"
1824263,2019-09-08 05:45:43 UTC,This may be looked at along with bug #1839223
1824263,2019-09-17 03:33:56 UTC,"Patchset: https://reviews.mahara.org/#/c/10329/
Browser tested: Firefox & Chrome
Theme used: Default"
1824264,2019-05-02 11:49:16 UTC,"Hi c3d, we had a similar report recently about high CPU usage that turned out to be a troublesome extension rather than LibreOffice itself:"
1824264,2019-07-02 04:17:28 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1824267,2019-04-12 16:14:30 UTC,setting status to incomplete because is not clear how to arrive in this status.
1824267,2019-06-12 04:17:25 UTC,[Expired for Hugin because there has been no activity for 60 days.]
1824269,2019-04-11 06:45:48 UTC,Could you provide more information?
1824269,2019-04-11 07:40:27 UTC,I used kolla-ansible to upgraded rocky to stein
1824269,2019-04-11 07:57:57 UTC,I assume this is not in production? Kolla Stein has not been released yet.
1824272,2019-04-11 23:16:46 UTC,Fix in develop has been previously committed.
1824272,2019-04-11 20:34:15 UTC,Got the cs:~juju/mariadb-k8s charm installed.
1824272,2019-04-11 18:30:59 UTC,"@wallyworld, how do i setup to deploy the local k8s charm for reproduction and testing purposes?"
1824272,2019-04-11 18:39:53 UTC,"I now remember to build the charm, use to the old ones with no building after charm pull...  but building the charm fails:"
1824272,2019-04-11 18:44:30 UTC,"In theory, SetCharmProfile() should not have been called due to early exit in setCharmWithAgentValidation() with a CAAS model: https://github.com/juju/juju/blob/develop/apiserver/facades/client/application/application.go#L926"
1824281,2019-04-11 05:40:35 UTC,"I am beginning to love Ubuntu again in Ubuntu Mate. It has a real solid feel to it, and the Quirang background expresses that solid feel very well. Most excellent image. Most excellent OS."
1824282,2019-05-28 08:43:21 UTC,ppa: https://launchpad.net/~ycheng-twn/+archive/ubuntu/nv-prime (bionic and disco)
1824282,2019-04-11 05:23:24 UTC,the last commit in
1824282,2019-06-28 19:24:27 UTC,"Would it be possible to change the ""intel"" profile to no longer alias the nvidia.ko and nvidia-uvm.ko modules to ""off""? The blacklisting can remain, and would prevent the modules from being loaded automatically in response to the device being present, but wouldn't prevent them from being explicitly loaded if desired."
1824282,2019-07-01 09:12:07 UTC,"Per my previous measurement, a machine consumes more power as nvidia.ko is loaded compare the situation that it's not loaded."
1824282,2019-07-01 09:17:27 UTC,I also have a patch to add the new mode to nvidia-settings. Will try to upload here when got chance to.
1824282,2019-07-09 16:57:11 UTC,This bug was fixed in the package nvidia-prime - 0.8.11
1824282,2019-10-30 22:08:06 UTC,"I think this was poorly implemented. If any of the concerned parties wish to discuss here, great. Otherwise I'll file a bug on."
1824282,2019-11-04 10:14:25 UTC,@Dough: feel free to file a bug report about it.
1824282,2019-11-13 15:14:08 UTC,"New bug
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1851416"
1824282,2020-11-17 01:19:47 UTC,The commit referenced here is super useful:
1824282,2020-11-17 14:23:30 UTC,@Phil: there are changes in ubuntu-drivers-common and in nvidia-prime that will make on-demand mode work for you. This work will land soon.
1824283,2019-04-11 12:30:21 UTC,"Thank you for your bug report, could you also report it upstream to the people writting the software on https://gitlab.gnome.org/GNOME/nautilus/issues ?"
1824283,2019-04-11 16:23:01 UTC,"Done.
Thanks for the suggestion.
https://gitlab.gnome.org/GNOME/nautilus/issues/985"
1824283,2019-04-12 16:23:29 UTC,Thanks
1824291,2019-07-24 08:02:32 UTC,Failed on AWS 5.0 Bionic as well.
1824291,2019-07-24 08:25:38 UTC,"For comment 2, this test should not be tested on AWS (test case issue). I will revert the tags."
1824293,2020-05-21 08:13:42 UTC,"Test passed with Trusty (3.13.0-177.228) node rizzo, closing this bug."
1824298,2019-04-22 14:09:36 UTC,"You can use pam_ldap with ldaps, or start_tls even (or even ditching pam_ldap, and switching to sssd). Is this bug about updating the KB article to show instructions on how to perform such configuration, or something else?"
1824298,2020-05-10 12:15:27 UTC,"As someone evaluating Landscape on-prem for my organization, having clear and concise documentation about integrating Landscape web portal auth with SSSD would be a welcome addition."
1824299,2020-02-18 17:03:26 UTC,"Reviewed:  https://review.opendev.org/705197
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=864555396728bc40dd696347c1ec59cd26bc0d53
Submitter: Zuul
Branch:    stable/queens"
1824299,2020-02-01 00:52:12 UTC,"Reviewed:  https://review.opendev.org/705195
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7945c60b0e2d56f2f1f7781b20aa9194af26082
Submitter: Zuul
Branch:    stable/stein"
1824299,2020-01-31 11:37:51 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/705197"
1824299,2020-01-31 11:37:21 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705196"
1824299,2020-01-31 11:34:31 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/705195"
1824299,2019-05-24 16:28:03 UTC,"Reviewed:  https://review.opendev.org/659511
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=38daf9eaae8538c74933b19c952ad0612751c027
Submitter: Zuul
Branch:    master"
1824299,2019-05-17 16:43:18 UTC,"but also, using backref() does have the effect that the other class won't need to see this related class, until this related class comes online and attaches its relationship to the other one.   it's very strange this happens all in one file like this.  so there is still a chance you can get a Flavor class or object that does not have a .service_profiles attribute yet.   since you're managing to access the class in between those two events."
1824299,2019-05-17 16:38:22 UTC,"wow neutron really wants to race on this!  so yes, that's the best SQLAlchemy can do.   you are importing modules while trying to serve requests.  that's the key architectural issue.    you can push the gerrit that you have which works around it but I personally wouldn't consider the architecrual issue here closed."
1824299,2019-05-17 15:03:33 UTC,"Ok, so my sqlalchemy version is 1.0.13 but the patch stays essentially the same. After applying I can see following errors: https://pastebin.com/tVT7N4f4 - so it clearly suggests ""adding this relationship() to the <class 'neutron.db.models.flavor.Flavor'> class after both dependent classes have been defined"""
1824299,2019-05-17 11:58:58 UTC,"and if it doesn't, if you can share the stack trace and surrounding logging assuming level of INFO for ""sqlalchemy.orm"" logger, thanks"
1824299,2020-02-17 18:44:19 UTC,"Reviewed:  https://review.opendev.org/705196
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d3492d9b0bb3ef224e01c1b49191fa484c9f1b5b
Submitter: Zuul
Branch:    stable/rocky"
1824299,2019-05-17 11:33:48 UTC,"@zzzeek so I reverted https://review.opendev.org/659511 and applied your above patch adding mutex into SQLAlchemy: in 1 out of 3 neutron server restarts I can still see ""Class 'neutron.db.models.flavor.FlavorServiceProfileBinding' is not mapped"" errors.
With just https://review.opendev.org/659511 - I did 5 restarts and no errors seen.
I understand https://review.opendev.org/659511 is not the right fix, but maybe it can help debug the race more. Thanks"
1824299,2019-05-16 15:31:01 UTC,"Current plan is to fix into the 1.3.x series, the mutex around the declarative process from the point at which the class is present in the registry (where relationship() resolves the string ""RelatedClass"") up until the class has a mapper() applied.   the mutex is shared with that of the configure process itself and is an RLock."
1824299,2019-05-16 14:49:34 UTC,"I've created https://github.com/sqlalchemy/sqlalchemy/issues/4686 to think about a possible mitigation here, however I haven't had time to consider both the full span of races that can occur if classes are used while imports happen, as well as if there are certain races that are much more likely and therefore worth mutexing.   In particular, the test script I have on my github issue produces this error in a slightly different way, and already shows that the above mutex I have in relationship.mapper() is not enough, depending on where the class setup process stalls."
1824299,2019-05-16 14:13:57 UTC,"OK so , the mutex in question would solve this very particular race, but it isn't a generalized solution.   I have two test scripts that reproduce the issue, one is fixed by a mutex in mapper() above, but the other is not.  The essential problem is that neutron is importing modules while simultaneously trying to build queries against the things being imported.  Neutron should have mutexes during its dynamic module importing that prevents it from proceeding with API requests within this process."
1824299,2019-05-16 13:43:34 UTC,"ah yes, this is a bug, probably in Neutron's import system though there may be a way to address it in SQLAlchemy by adding a mutex, it's a race.     note that the stack trace is generated on a different request id while the SQLAlchemy ORM logging shows it is still in the process of mapping the BGPVPNPortAssociationRoute class itself."
1824299,2019-05-16 13:20:39 UTC,"it's not possible for the target class to be imported but not be mapped, since it is using the declarative metaclass that maps the class immediately.  The order of relationships has nothing to do with it, and the stack trace here occurs within the configure_mappers() phase which assumes all classes have been imported, and therefore it should not be possible that they exist but are not mapped.  I need to look at this much more closely."
1824299,2019-05-16 09:47:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659511"
1824299,2019-05-16 07:38:46 UTC,"So, it appears that the race happens in case relationship is defined before the class it relates to. For example in bgpvpn case:"
1824299,2019-05-17 11:57:41 UTC,Hi Oleg -
1824299,2019-04-11 07:37:26 UTC,"In log above messages ""(BGPVPNPortAssociationRoute|bgpvpn_port_association_routes) constructed"" and ""(BGPVPN|bgpvpns) constructed"" can be seen after the error.
But if we wait till all BGPVPN objects got constructed and start agents, we're good."
1824300,2019-07-18 20:13:58 UTC,"Reviewed:  https://review.opendev.org/670038
Committed: https://git.openstack.org/cgit/x/nova-lxd/commit/?id=36b72b016b3be1538880a85379035665aee552f4
Submitter: Zuul
Branch:    stable/rocky"
1824300,2019-07-10 11:16:26 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/670038"
1824300,2019-07-18 19:47:06 UTC,"Reviewed:  https://review.opendev.org/670037
Committed: https://git.openstack.org/cgit/x/nova-lxd/commit/?id=5ce47afcb2e5ae6adbce5c2e43ebe432c394bc51
Submitter: Zuul
Branch:    stable/stein"
1824300,2019-04-12 15:13:50 UTC,"Reviewed:  https://review.openstack.org/652054
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=d0faf787d92e20a55faf35ea6d95dd4d7ae7e598
Submitter: Zuul
Branch:    master"
1824300,2019-04-12 12:20:34 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/652054"
1824300,2019-07-10 11:15:44 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/670037"
1824312,2019-04-11 09:17:23 UTC,"On Thu, 2019-04-11 at 09:09 +0000, J Prino wrote:

> NetworkManager  WARNING: This version of openconnect is v8.02-1 but
> NetworkManager           the libopenconnect library is v8.02
"
1824312,2019-04-11 09:45:05 UTC,I agree however there's no 8.02 version for openconnect (disco). Can libopenconnect be fixed?
1824312,2019-04-11 09:57:39 UTC,"On Thu, 2019-04-11 at 09:45 +0000, J Prino wrote:

> I agree however there's no 8.02 version for openconnect (disco). Can
> libopenconnect be fixed?
"
1824312,2019-04-11 10:47:49 UTC,thanks and sorry for the wasted time. This is now fixed with version correction
1824315,2019-05-15 21:04:25 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/659374"
1824315,2019-06-11 22:57:44 UTC,"Reviewed:  https://review.opendev.org/660327
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b9caf7d9c7423a658c837aaedb7c4fb3580bda47
Submitter: Zuul
Branch:    stable/rocky"
1824315,2019-07-01 20:28:04 UTC,"Reviewed:  https://review.opendev.org/660328
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0cad3089d3e84e8e3436e171d00c8cce8717fd6d
Submitter: Zuul
Branch:    stable/queens"
1824315,2019-05-23 17:43:00 UTC,"Reviewed:  https://review.opendev.org/660325
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2f7b1031a9b80d15052fcd9b22831f1db0486a4a
Submitter: Zuul
Branch:    stable/stein"
1824315,2019-05-21 09:54:48 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/660328"
1824315,2019-05-21 09:54:29 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/660327"
1824315,2019-05-21 09:54:04 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/660325"
1824315,2019-05-17 00:35:00 UTC,"Reviewed:  https://review.opendev.org/659374
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=66070416ab670daf4734f2c30ad2df5d96e615e6
Submitter: Zuul
Branch:    master"
1824315,2019-05-15 19:45:17 UTC,"Just to add info to this bug report, the traceback in the logs:"
1824315,2019-04-12 07:20:21 UTC,Looks like is working now and upstream is working too let's close this.
1824315,2019-05-15 16:08:05 UTC,"Arx, I don't see that that qemu-guest-agent rpm is installed on the standalone deployment.
That is something we can do in the os-temepst role itself or via adding qemu-guest-agent as part of the deployment."
1824315,2019-04-17 09:39:16 UTC,Here's what I found:
1824315,2019-04-17 09:22:02 UTC,Found this on http://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-infra/tripleo-ci/master/periodic-tripleo-ci-fedora-28-standalone-master/36994ee/logs/undercloud/var/log/containers/nova/nova-api.log.txt.gz:
1824315,2019-04-16 07:45:10 UTC,Also here
1824315,2019-04-15 18:02:38 UTC,https://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-infra/tripleo-ci/master/periodic-tripleo-ci-fedora-28-standalone-master/cf91a82/logs/tempest.html.gz looks like this may not be fixed
1824315,2019-04-12 11:29:12 UTC,Is it possible to track specific tests in sova?
1824315,2019-04-11 10:31:55 UTC,"Same error here
http://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-infra/tripleo-ci/master/periodic-tripleo-ci-fedora-28-standalone-master/c6d552d/logs/tempest.html.gz"
1824315,2019-05-15 16:08:38 UTC,http://logs.openstack.org/84/655684/2/check/tripleo-ci-fedora-28-standalone/eda3002/logs/undercloud/var/log/extra/rpm-list.txt.gz
1824318,2019-05-15 17:37:00 UTC,TRIAGE:
1824322,2019-07-19 08:28:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824330,2019-04-11 16:00:35 UTC,"Actually, i tried to play a video on my machine using vlc ( i.e; after changing the Display Manager to XFCE). This is the actual problem. Can you look into it once: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1824345"
1824330,2019-06-11 04:17:26 UTC,[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]
1824330,2019-04-11 14:28:22 UTC,Could you provide the details requested?
1824330,2019-04-11 12:23:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1824330,2019-04-11 12:23:55 UTC,"The issue you describe also seems to impact gedit not samba, why did you report it against that component?"
1824330,2019-04-11 12:41:48 UTC,"Yeah, actually this is my first time doing this. I'm sorry for that"
1824333,2019-05-21 13:04:12 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1824333,2019-05-14 22:58:19 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824333,2019-05-14 19:06:48 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1824333,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1824333,2019-05-06 10:10:12 UTC,In the proposed build [1] I see
1824333,2019-05-06 09:07:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1824333,2019-05-06 10:01:17 UTC,I added a Bionic task since you asked for a Bionic verification
1824333,2019-04-26 15:36:00 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1824333,2019-04-26 07:45:54 UTC,"ubuntu@cosmic-autofs:~$ find /lib/modules -name '*autofs4*'
ubuntu@cosmic-autofs:~$ modinfo autofs4
modinfo: ERROR: Module autofs4 not found."
1824333,2019-04-25 22:32:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1824333,2019-04-12 13:22:40 UTC,Submitted patch to mailing list for next SRU cycle.
1824333,2019-04-12 10:05:40 UTC,"Hi Robert,
I haven't found the reason.
For my limited kernel knowledge I have checked and discussed a bit."
1824333,2019-04-11 19:30:36 UTC,The module is contained in linux-modules-extra-4.18.0-17-generic which is not installed when linux-virtual-hwe-18.04 is selected.
1824333,2019-04-29 05:51:43 UTC,"After upgrade:
$ find /lib/modules -name '*autofs4*'
/lib/modules/5.0.0-14-generic/kernel/fs/autofs/autofs4.ko"
1824334,2019-12-19 14:41:30 UTC,This issue was fixed in the openstack/neutron 14.0.4 release.
1824334,2020-02-28 15:29:34 UTC,This issue was fixed in the openstack/neutron 13.0.7 release.
1824334,2020-02-18 16:24:26 UTC,"Reviewed:  https://review.opendev.org/702821
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9361af0ff66fa8f4970158f2d8dc852d8d0444d1
Submitter: Zuul
Branch:    stable/rocky"
1824334,2020-01-16 08:43:31 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/702821"
1824334,2019-11-06 11:18:41 UTC,"Reviewed:  https://review.opendev.org/692998
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=70391139906a673bde88210757656b35cb4c45bc
Submitter: Zuul
Branch:    stable/stein"
1824334,2019-04-11 15:26:01 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651815"
1824334,2019-11-05 12:48:22 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/692998"
1824334,2019-09-19 10:11:46 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1824334,2019-09-16 15:32:25 UTC,"Reviewed:  https://review.opendev.org/651815
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=49a66dba31f23d54972e962beef66c39307904df
Submitter: Zuul
Branch:    master"
1824334,2019-11-05 12:51:01 UTC,I've tried this patch for my error below on stein and it fixed it.
1824335,2019-05-16 09:15:03 UTC,This bug was fixed in the package mariadb-10.1 - 1:10.1.38-0ubuntu0.18.10.2
1824335,2019-05-16 07:55:19 UTC,"@otto, sorry it's not clear to me from your comment, is there something wrong with this upload?"
1824335,2019-05-16 07:12:18 UTC,See original bug report https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1757107 and in particular commit https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1757107/comments/11
1824335,2019-05-13 10:43:44 UTC,"The verification of the Stable Release Update for mariadb-10.1 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824335,2019-05-13 10:43:37 UTC,This bug was fixed in the package mariadb-10.1 - 1:10.1.38-0ubuntu0.18.04.2
1824335,2019-05-10 13:39:54 UTC,autopkgtest now passes for all archs (including arm64) on cosmic.
1824335,2019-05-09 13:49:53 UTC,"Hello Dan, or anyone else affected,"
1824335,2019-04-30 10:13:03 UTC,"jemalloc appears to need more serious work to fix correctly; instead, i opened bug 1827022 to simply do what has been done in disco and later for mariadb-10.1, which is disable building with jemalloc for arm64."
1824335,2019-04-29 17:47:41 UTC,"> bionic and cosmic autopkgtests all pass, with the exception of:
"
1824335,2019-04-29 11:16:02 UTC,"bionic and cosmic autopkgtests all pass, with the exception of:"
1824335,2019-04-25 13:28:03 UTC,"Hello Dan, or anyone else affected,"
1824335,2019-04-25 13:23:35 UTC,"Hello Dan, or anyone else affected,"
1824335,2019-04-16 09:01:07 UTC,"An upload of mariadb-10.1 to cosmic-proposed has been rejected from the upload queue for the following reason: ""The SRU carries backports of security-updates up to 10.1.38. Seeing that those were security updates this might be still good for an SRU, but pulling those into cosmic through a separate pocket without a tracking bug seems like a bad idea. Security updates are usually checked for regressions by the security team - here, since the security team is not directly involved, we need to have a way to track issues regarding backporting a new upstream version. Please include a tracking bug for the upstream backport (one bug is enough) and re-submit. Thanks!""."
1824335,2019-05-08 20:47:17 UTC,"autopkgtest regression fixed with bug 1827022, which is waiting in the cosmic upload queue for anyone from ~ubuntu-sru to approve it."
1824343,2020-03-07 10:12:32 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1824344,2020-03-17 03:11:11 UTC,This appears to be similar to https://bugs.launchpad.net/qemu/+bug/1866892 (and much simpler)
1824349,2019-04-25 18:55:55 UTC,"I encountered the same issue. In some conditions, the type of datum.value is dict instead of list.
I have below temporary fix in my environment, but not sure if it will break something."
1824351,2019-04-11 16:07:51 UTC,"(defun f371 ()
  (catch 'ct
    (flet ((%f14 (x)
             (the fixnum x)))
      (if (logbitp 0
                   (multiple-value-call #'%f14 1))
          (the integer (%f14 2))))))"
1824351,2019-04-12 13:05:14 UTC,Not sure if this is a duplicate of 1813839
1824351,2019-04-12 13:12:43 UTC,"I think it is, but i like this test case better."
1824352,2019-06-23 04:18:13 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1824352,2019-04-23 11:43:21 UTC,"@Brian Murray
Yeah you right, this is an installation error and when i reinstall the ubuntu, every things were good :)"
1824352,2019-04-22 22:03:50 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1824359,2019-04-12 01:27:40 UTC,"Fixed in revision df600fc1a2f55c032e02c41fbdf1b2db412954cc
https://git.launchpad.net/kicad/patch/?id=df600fc1a2f55c032e02c41fbdf1b2db412954cc"
1824360,2019-04-12 01:48:58 UTC,"While looking for a pattern, I figured out that there are ""swift_account"" resources in Gnocchi that exist for the missing ""ceph_account"" resources, and under the ""swift_account"" resources, there are ""radosgw.containers.objects"" and ""radosgw.containers.objects.size"" metrics."
1824360,2019-04-12 02:58:05 UTC,"I thought I would try deleting the above resources from Gnocchi, starting with the swift_account resources, thinking that they would be re-created by Ceilometer.  However, they did not."
1824360,2019-04-12 05:04:04 UTC,"I thought I'd try something a bit more drastic:
1) stopping Ceilometer
2) dropping the gnocchi MySQL table
3) purging all objects in the Ceph gnocchi pool
4) re-deploying (I'm using Kolla Ansible) gnocchi and ceilometer"
1824360,2019-04-12 06:06:25 UTC,I think I found the bug.
1824360,2019-04-12 06:12:37 UTC,"I forgot to include the latest patch for rgw_client.py in my message above.  It should have a try/except to deal with buckets that have no rgw.main, otherwise an error occurs that breaks everything. :)"
1824364,2019-04-21 16:43:49 UTC,Fix committed in x1.3.1-53.
1824370,2019-04-11 15:00:56 UTC,"A package containing version 2.50, adjusted for compilation on aarch64 is available from https://launchpad.net/~waveform/+archive/ubuntu/pkg/+packages"
1824370,2019-04-11 23:55:05 UTC,*** This is an automated message ***
1824370,2019-04-20 21:22:07 UTC,"Hi Dave, thanks for your work on this!"
1824370,2020-12-09 14:06:18 UTC,"This package is in ubuntu since focal, closing the bug."
1824372,2020-06-10 07:59:28 UTC,Does this issue still happen under 20.04?
1824372,2020-06-18 06:05:40 UTC,"Maybe test latest mainline kernel?
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc1"
1824372,2020-06-10 12:58:23 UTC,Sorry for various reasons I won't be able to test 20.04
1824372,2019-04-29 15:39:27 UTC,Actually the cma_alloc error is present much before VF creation. dmesg is attached.
1824372,2020-08-18 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824372,2019-04-18 09:37:11 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc5 kernel [0]."
1824372,2019-04-11 15:00:06 UTC,This change was made by a bot.
1824372,2019-04-29 15:37:56 UTC,"I am unable to test with latest mainline (5.1.0-050100rc6-generic) as the creation of a single VF starts spamming dmesg with ""cma: cma_alloc: alloc failed, req-size: 1 pages, ret: -12"""
1824384,2019-09-17 15:34:18 UTC,apparmor's library build uses automake and libtool so the static version of the library is built without -fPIC while the dynamic is built with -fPIC. It is possible to override this.
1824384,2019-09-17 22:09:25 UTC,@jjohansen thank you for looking into this!
1824385,2019-04-11 15:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824385,2019-04-11 16:20:30 UTC,"The python3-launchpadlib package is not installed. This functionality is not available. after when i try type command apport-collect 1824385 i saw the error
ERROR: The python3-launchpadlib package is not installed. This functionality is not available."
1824385,2019-06-11 04:17:28 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824386,2020-07-13 05:55:01 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/11069"
1824386,2020-07-27 04:17:28 UTC,"Reviewed:  https://reviews.mahara.org/11069
Committed: https://git.mahara.org/mahara/mahara/commit/042fb1c77daac5731154ed74882f3392a75415d3
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1824391,2019-04-26 15:32:04 UTC,Force pushed back to working branch code to support file writing for the Angular hatch service.
1824391,2019-04-12 20:28:57 UTC,Note also the Hatch branch is built atop the JDK11 branch.
1824391,2019-04-12 20:28:39 UTC,Two working branches:
1824392,2019-04-11 20:38:30 UTC,"The PR https://github.com/elastic/elasticsearch/pull/21899 introduces a
knob to prevent ES from demanding vm.max_map_count increases, could also try to set this when running in a container with low vm.max_map_count"
1824393,2019-04-11 16:30:08 UTC,first video
1824393,2019-04-11 16:30:28 UTC,second video
1824393,2019-05-16 12:14:10 UTC,I have also opened the following upstream bugreport: https://gitlab.freedesktop.org/xorg/xserver/issues/683
1824394,2019-06-07 18:01:50 UTC,This bug was fixed in the package snapd - 2.39.2+19.10ubuntu1
1824397,2019-04-29 11:49:56 UTC,Submitted a patch for review: http://patchwork.ozlabs.org/patch/1091175/
1824399,2019-09-16 14:23:06 UTC,"This is safe to deploy because the new issueAccessToken method will fail with ""RuntimeError: codehosting.git_macaroon_secret_key not configured"" until we get that configured.  I'll file a ticket for that."
1824399,2019-05-02 16:40:33 UTC,r18954 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18954) is part of this bug's fix.
1824399,2019-05-06 16:40:38 UTC,r18958 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18958) is part of this bug's fix.
1824399,2019-09-10 12:50:40 UTC,r19049 in stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/19049) is part of this bug's fix.
1824399,2019-09-16 11:00:50 UTC,Fixed in stable r19050 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/19050>.
1824399,2019-09-26 14:47:06 UTC,"Some more of this is deployed now.  However, we still need that configuration tweak, and I realised that we also need a way to create repositories via the API, so I'm working on that."
1824400,2019-11-14 00:42:16 UTC,I think this is fixed now. Please reopen if you see anything similar still.
1824400,2019-04-11 17:57:52 UTC,"Sorry, forgot to attach the screenshot"
1824401,2019-04-11 18:03:11 UTC,"This is on a VM, it waited more than 52s"
1824401,2019-04-11 21:49:05 UTC,Snap seeding is very slow yes. I don't think there's anything subiquity can do about this (except maybe slimming down the snap might help a very little bit).
1824401,2019-04-16 19:11:30 UTC,"The output of ""systemd-analyze blame"" and ""snap debug timings <chg-id>"" (where <chg-id> is the id of the change that did all the seeding (available via snap changes))."
1824401,2019-04-16 23:29:44 UTC,"Attaching a tarball with all that and a bit more. There are some other delays in the boot that are not related to snapd, it seems, which should probably be the subject of other bugs."
1824403,2019-04-12 13:03:56 UTC,Probably duplicate of https://bugs.launchpad.net/kicad/+bug/1824251 -- will keep an eye on this
1824403,2019-04-13 14:52:48 UTC,This should have been fixed by https://bugs.launchpad.net/kicad/+bug/1824251
1824407,2020-01-06 22:31:20 UTC,This bug was fixed in the package linux - 5.4.0-9.12
1824407,2019-11-06 22:16:57 UTC,"At least it doesn't mangle email notifications! Such that in email code is
readable."
1824407,2019-11-06 22:20:13 UTC,"I thought all lowerdirs must be read-only, and the first one in the stack
will win. Even if there are same ones down the stack it shouldn't matter.
But I guess needs testing."
1824407,2019-11-06 23:18:29 UTC,When I'm more awake tomorrow I'll send a patch upstream as a suggested fix and see if we can get a good solution on the UUIDs worked out.
1824407,2019-11-07 05:19:42 UTC,"I didn't mean actually random, and I think clock-based would be entirely fine, but my paranoia about stacking two things with identical superblocks might be just paranoia too.  I dunno."
1824407,2019-11-07 10:53:01 UTC,been iterating on a fix with upstream: https://lkml.org/lkml/2019/11/7/317
1824407,2019-11-07 11:52:43 UTC,pr_warn sounds awkward though
1824407,2019-11-07 15:18:28 UTC,"pr_warn can be removed with a sauce patch, so no worries with that."
1824407,2019-11-22 11:15:02 UTC,v4 patch is at https://lkml.org/lkml/2019/11/13/799
1824407,2019-12-05 11:27:14 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1824407,2019-12-03 15:42:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1824407,2019-12-04 11:03:44 UTC,Verified for disco:
1824407,2019-11-06 21:15:30 UTC,"While there may be arguments for synthesizing UUIDs in various fs drivers, or creating them in the first place in fs-creation tools, I agree that if overlayfs has a hard dependency on UUIDs for uniquely identifying layers, it needs to fill in the gaps where the previous tools/drivers failed to provide."
1824407,2019-12-06 17:50:55 UTC,"Hrm, I can't see the fix in the Ubuntu-5.3.0-24.26 kernel, so I think comment #34 a premature SRU test request. As it stands, I tested Ubuntu-5.3.0-24.26 and the issue still exists, and looking at the source the fix isn't present so that correlates with my test observations."
1824407,2019-12-07 17:39:49 UTC,The comment in #34 is about 5.3.0-25.27 which is in eoan-proposed.
1824407,2019-12-08 15:50:26 UTC,Tested with 5.3.0-25-generic #27-Ubuntu with the regression test and it now works fine. Marking bug as verification-done for eoan
1824407,2020-01-16 20:55:18 UTC,This bug was fixed in the package linux-hwe - 5.3.0-26.28~18.04.1
1824407,2020-01-06 13:12:44 UTC,This bug was fixed in the package linux - 5.0.0-38.41
1824407,2019-11-22 11:27:39 UTC,"I'm doing some testing right now on the current upstream fix, hopefully will SRU this by EOD."
1824407,2019-11-06 18:45:18 UTC,Just love the way launchpad mangles pasted code.
1824407,2020-01-06 12:53:38 UTC,This bug was fixed in the package linux - 5.3.0-26.28
1824407,2019-11-06 18:40:04 UTC,blkid
1824407,2019-11-06 18:44:15 UTC,"I was thinking of a more generalized overlayfs solution that detects if file systems don't initialize the superblock uuid and overlayfs improvises by generating the internal overlayfs uuid, something like:"
1824407,2019-04-11 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824407,2019-05-15 23:02:24 UTC,@dimitri are you still having this issue?  There isn't much to go on in this bug submission yet.
1824407,2019-07-15 04:17:29 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824407,2019-10-03 15:12:53 UTC,Yes this is still a problem affecting Ubuntu Desktop and Server (new one) ISOs.
1824407,2019-10-03 15:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824407,2019-10-23 16:34:10 UTC,"And need casper in focal to migrate to support the ""bebroken"" keyword"
1824407,2019-11-04 15:38:56 UTC,"Hi Dimitri,"
1824407,2019-11-04 15:41:00 UTC,"BTW, I can generate the mount move failure with the cut down script as follows (which follows the same mount patterns as the casper script)"
1824407,2019-11-04 17:39:07 UTC,"OK, now managed to get a reproducer script to kick this bug even outside the early install context.  Seems like we can force this bug by either remounting OR sync'ing and dropping caches."
1824407,2019-11-04 17:41:32 UTC,And if we change use a different file: /root-tmp/var/log/ubuntu-advantage.log we get the following error too:
1824407,2019-11-05 09:57:54 UTC,Replaced read-only squashfs with read-only ext4 partitions and can't reproduce the error.
1824407,2019-11-05 10:00:05 UTC,Replaced one of the two squashfs with read-only ext4 partitions and can't reproduce the error. Seems that we need 2 stacked squashfs file systems.
1824407,2019-11-05 20:20:02 UTC,"4.15: ovl_get_origin_fh detects zero sized files on lower paths and treats these a special zero sized ""copied up but origin unknown"" magic."
1824407,2019-11-06 15:19:34 UTC,Comparing the previous debug with 2 squashfs overlayfs lowers with the *same* data on ext4 as the 2 overlayfs lowers we have:
1824407,2019-11-06 17:21:57 UTC,"Adding a uuid into the superblock on squashfs seems to resolve the issue.  Since squashfs does not have UUID support, my hack below generates one based on some squashfs superblock metadata that provides a good enough UUID for our purposes."
1824407,2019-11-06 17:25:12 UTC,The concern I have is for other file systems that also don't populate the UUID - this seems to be a general problem for overlayfs. Perhaps a UUID can be autogenerated based on the superblock rather than file system specific UUID magic if the UUID is zero.
1824407,2019-11-06 18:30:29 UTC,"I think kernel already generates some faked up UUIDs, i.e. i think there is something for like FAT and DOS partition table, either fs uuid, or like partition table uuid, partition uuid, partition type uuid, some such."
1824407,2019-11-06 18:30:58 UTC,"There is mkfs-time of the filesystem superblock, which could be converted to a timebased UUID."
1824408,2019-08-28 18:26:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824408,2019-07-18 14:39:12 UTC,Thanks!
1824408,2019-07-18 13:50:50 UTC,I opened a bug upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1567176
1824408,2019-07-10 10:52:26 UTC,"Thanks for the report Franck.
This sounds like it might be an upstream bug. Would you mind filing it at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox, and sharing the link to it here? Thanks!"
1824408,2019-07-18 13:50:16 UTC,User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
1824409,2018-05-14 13:13:09 UTC,"Created attachment 8975470
Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs whitespace."
1824409,2021-01-19 15:22:10 UTC,I've lost context.
1824409,2018-05-30 07:57:46 UTC,"Comment on attachment 8975470
Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs whitespace."
1824409,2018-05-30 07:59:29 UTC,"Created attachment 8981781
Windows 7"
1824409,2018-05-30 11:33:48 UTC,*** Bug 1464373 has been marked as a duplicate of this bug. ***
1824409,2019-03-21 19:41:35 UTC,"I see the same issue on the Mac, 10.14.3 with FF developer edition 67.0b3"
1824409,2019-03-27 15:50:30 UTC,*** Bug 1538767 has been marked as a duplicate of this bug. ***
1824409,2019-07-10 10:50:34 UTC,"Thanks for the report Franck.
This sounds like it might be an upstream bug. Would you mind filing it at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox, and sharing the link to it here? Thanks!"
1824409,2019-07-18 18:04:22 UTC,"Created attachment 9079109
slight_imperfection.png"
1824409,2019-07-18 18:05:25 UTC,Bug filled upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1567246
1824409,2019-07-23 10:53:30 UTC,*** This bug has been marked as a duplicate of bug 1147847 ***
1824409,2019-07-23 10:54:18 UTC,*** Bug 1567705 has been marked as a duplicate of this bug. ***
1824409,2019-07-23 13:07:27 UTC,I don't think this is about scrollbars but about titlebar / tabs.
1824409,2019-07-23 13:09:17 UTC,I think this is related to left button box position - can you try to move the buttons to right and check if you still see this? Thanks.
1824409,2019-07-23 13:13:31 UTC,"(In reply to Martin Stránský [:stransky] from comment #3)

> I don't think this is about scrollbars but about titlebar / tabs.
"
1824409,2019-07-23 13:13:31 UTC,*** Bug 1567246 has been marked as a duplicate of this bug. ***
1824409,2019-07-23 19:41:02 UTC,"Moving the buttons to the right certainly hides (solves ?) the problem, as then the tab in drawn to the very left of the title bar..."
1824409,2019-07-24 17:58:40 UTC,Is this still something we want to land? We have a couple of duplicates so I think it's an issue that bothers users and it's also marked P1.
1824409,2019-07-25 07:03:17 UTC,"(In reply to Liz Henry (:lizzard) (use needinfo) from comment #31)

> Is this still something we want to land?
"
1824409,2020-05-23 12:12:36 UTC,*** Bug 1640177 has been marked as a duplicate of this bug. ***
1824409,2019-07-23 07:21:56 UTC,"Dao should know more, I hope it's the right component."
1824409,2017-12-04 23:58:17 UTC,"(In reply to Nihanth Subramanya [:nhnt11] from comment #21)

> Comment on attachment 8923047
> Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs
> whitespace.
>
> Review request updated; see interdiff:
> https://reviewboard.mozilla.org/r/194262/diff/4-5/
"
1824409,2017-11-10 12:26:29 UTC,"In support of Nihanths current solution, it's probably what we need to do to resolve bug 1403520 as well."
1824409,2017-12-04 12:38:19 UTC,"Hey folks, is there anything we can do to resolve this anytime soon? I'm happy to take the review if you're busy right now, Dão."
1824409,2017-12-04 23:54:15 UTC,"Comment on attachment 8923047
Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs whitespace."
1824409,2017-09-27 08:49:57 UTC,"Created attachment 8912611
Screen Shot 2017-09-27 at 10.46.56.png"
1824409,2017-10-09 10:39:42 UTC,*** Bug 1406681 has been marked as a duplicate of this bug. ***
1824409,2017-10-09 16:42:45 UTC,"Created attachment 8916677
Bildschirmfoto 2017-10-09 um 18.39.58.png"
1824409,2017-10-10 20:18:27 UTC,"Created attachment 8917126
Bug 1403483 - Set a border on the first tab instead of at the end of the pre-tabs drag space."
1824409,2017-10-10 20:36:46 UTC,"Comment on attachment 8917126
Bug 1403483 - Set a border on the first tab instead of at the end of the pre-tabs drag space."
1824409,2017-10-10 20:38:36 UTC,"This works well for me at the moment on current central, but I need to confirm with Johann whether some changes around this code he was talking about have landed already or not. Also, I'm not entirely sure this works for RTL, I'm going to investigate this tomorrow."
1824409,2017-10-10 20:39:13 UTC,"Hmm, and I think I need to make the Windows-specific selector account for the menubar as well as maximized mode. Canceling review for now."
1824409,2017-10-19 11:59:03 UTC,*** Bug 1408953 has been marked as a duplicate of this bug. ***
1824409,2017-09-29 08:50:07 UTC,"Let's do this after bug 1391539, otherwise we'll have to file another bug to adjust the height of this border when hovering (I'm happy to pick it up once bug 1391539 is done)."
1824409,2017-10-28 02:20:28 UTC,"Comment on attachment 8923047
Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs whitespace."
1824409,2017-10-28 02:15:39 UTC,"Created attachment 8923047
Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs whitespace."
1824409,2017-11-10 12:27:16 UTC,"I'm setting this to block bug 1403520 for now, as we probably shouldn't act there without solving this first."
1824409,2017-11-01 11:23:10 UTC,"Comment on attachment 8923047
Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs whitespace."
1824409,2017-10-30 00:10:02 UTC,"(In reply to Nihanth Subramanya [:nhnt11] from comment #13)

> TODO: Add a rule to hide the first tab separator when sizemode != normal on
> Windows.
"
1824409,2017-11-07 12:40:18 UTC,"(In reply to Dão Gottwald [::dao] from comment #16)

> Comment on attachment 8923047
> Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs
> whitespace.
>
> https://reviewboard.mozilla.org/r/194262/#review200420
>
> It's not clear to me why this patch moves the border away fron the pre-tabs
> whitespace. Why can we not just fix that border's height?
"
1824409,2017-10-28 13:10:36 UTC,TODO: Add a rule to hide the first tab separator when sizemode != normal on Windows.
1824409,2017-10-28 13:09:52 UTC,"Comment on attachment 8923047
Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs whitespace."
1824409,2017-10-28 02:24:39 UTC,"Dão, the only problem (as far as I can tell) with this patch is that there is no tab separator before the first non-pinned tab when the tabstrip is overflowing. A CSS-only solution might be to use a selector like .tabbrowser-tab[pinned] + .tabbrowser-tab:not([pinned]), but I worry about hidden tabs in between. Do you think this would be an OK solution or should we try and add an attribute to the first visible non-pinned tab in JavaScript for styling convenience?"
1824409,2017-10-30 00:08:33 UTC,"Comment on attachment 8923047
Bug 1403483 - Show tab separator on first tab instead of on the pre-tabs whitespace."
1824412,2019-06-06 18:38:50 UTC,"Issue not reproduced on
Lab: SM_2
Load: 20190604T144018Z"
1824412,2019-05-21 23:16:45 UTC,the following error is still present in simplex and duplex
1824412,2019-05-31 15:41:26 UTC,"Reviewed:  https://review.opendev.org/661875
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=4f74ea1d391696341c50c97eb3baf90755582098
Submitter: Zuul
Branch:    master"
1824412,2019-05-25 04:12:36 UTC,"I propose to remove it from AIO test case and just test it in multinode setup since
Nova project keep this disabled by default.
When we have to test it in AIO, we can enable it manually."
1824412,2019-05-24 21:36:18 UTC,We tried the mentioned workaround and AIO was able to resize without any issues.
1824412,2019-05-22 01:30:12 UTC,"Hi Maria,"
1824412,2019-05-16 01:31:34 UTC,"Hi Kopec,"
1824412,2019-04-23 23:08:01 UTC,Bug can be reproduced: http://paste.openstack.org/show/749679/
1824412,2019-05-05 02:27:05 UTC,"""This parameter should only be set to true for resize testing in
single-host environments."""
1824412,2019-04-30 17:45:47 UTC,"Looks like in the latest openstack-helm rebase (https://review.opendev.org/#/c/645806/) we picked up an upstream commit that removed the setting of nova config option allow_resize_to_same_host to true (see https://review.opendev.org/#/c/615707/).  Based on that, I'd expect this testcase to fail.  We'll now need to set it to true in our nova overrides."
1824412,2019-04-30 08:28:16 UTC,"Hi Peng,"
1824412,2019-04-15 17:25:57 UTC,Marking as release gating until further investigation. This maybe a nova issue and would require follow-up with upstream.
1824412,2019-05-07 23:36:03 UTC,"You should be able to change the config option and retest.
system helm-override-update nova openstack --set conf.nova.DEFAULT.allow_resize_to_same_host=true
system application-apply stx-openstack"
1824413,2019-10-15 23:02:51 UTC,This has been addressed by https://github.com/juju/juju/commit/8fc13b3
1824415,2019-04-16 10:43:09 UTC,"First things first - please test mainline kernel:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc4 kernel [0]."
1824415,2019-04-16 11:38:02 UTC,"Just tried to use v5.1.0-050100rc5, and unfortunately it still there.
When Chrome shows dynamic SVG it happens at once."
1824415,2020-08-09 04:17:24 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824415,2019-04-16 09:58:10 UTC,"I'll try to have a replacement, however, it really happens only in Chrome and electron applications ( see chromium forks)"
1824415,2020-06-09 05:38:37 UTC,Please test 20.04.
1824415,2019-04-16 02:19:22 UTC,As stated in comment #2:
1824415,2019-04-16 02:18:04 UTC,"I think that's a different flickering. That bug is about the Chromium web browser. This bug is about a hardware defect affecting bright/white areas of the LCD, and the fact that Linux handles hardware defects less elegantly than Windows does."
1824415,2019-04-15 12:07:31 UTC,It's looks like a bug with linux intel display drivers and chromium forks...
1824415,2019-04-15 03:00:07 UTC,This change was made by a bot.
1824415,2019-04-15 02:43:03 UTC,"Yes, unfortunately that is also my experience..."
1824415,2019-04-12 18:55:32 UTC,"Hi Danniel, it may be true, but have not this issue in windows.
Also see this https://photos.app.goo.gl/Ff7KgctcrY6JFXv88"
1824415,2019-04-12 01:19:06 UTC,"Sorry, but this looks to me like a broken (or just poorly connected) LCD panel in the laptop. Not a software problem."
1824420,2019-04-12 18:10:47 UTC,"A bit weird, there are two events for compute_check_can_live_migrate_destination with one that didn't finish (or the event wasn't finished anyway):"
1824420,2019-04-12 18:12:17 UTC,This should probably either be low or medium severity given it's extremely latent behavior.
1824420,2019-04-12 18:26:44 UTC,Another solution would be to change the instance action in post_live_migration once we are sure we had a successful live migration to drop the 'Error' message value from any events that may have failed. That maybe has an upside to doing it in the DB API with overwriting existing events because you'd (1) still have the event log of the various hosts that the event ran on so we can see those reschedules and (2) have context on why it's OK to do that rather than blindly just update / overwrite existing events for other operations where maybe that overwrite is not OK.
1824421,2019-07-05 12:51:54 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1824421,2019-06-21 15:25:03 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1824421,2019-06-21 13:47:13 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1824421,2019-06-07 19:29:38 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.0.0 release.
1824421,2019-06-06 16:48:52 UTC,"Reviewed:  https://review.opendev.org/663415
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=257315572855db45df5c3e01b7e8c6ada6124ee2
Submitter: Zuul
Branch:    stable/queens"
1824421,2019-06-06 09:03:40 UTC,"Reviewed:  https://review.opendev.org/663416
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=6c92c5195e426308c7d2d153f7ac809c627712fd
Submitter: Zuul
Branch:    stable/rocky"
1824421,2019-06-05 20:06:46 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/663416"
1824421,2019-06-05 20:06:15 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/663415"
1824421,2019-06-05 06:07:19 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/663235"
1824421,2019-06-05 05:40:33 UTC,"Reviewed:  https://review.opendev.org/651926
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7910cf3b487ba52e99bacfec4ecc86b1eeac4d16
Submitter: Zuul
Branch:    master"
1824421,2019-04-11 20:54:29 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651926"
1824421,2019-06-06 02:19:29 UTC,"Reviewed:  https://review.opendev.org/663235
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b74dad7a8544d9bfa23d1f105715906464eb32a0
Submitter: Zuul
Branch:    stable/stein"
1824423,2019-04-12 18:01:48 UTC,"Having a quick look at the build log of collectd for '5.7.2-2ubuntu1.1'.
Collectd has been build on top of openjdk-11-* found in bionic-proposed '11.0.2+9-3ubuntu1~18.04.*'"
1824423,2019-09-12 07:33:01 UTC,Up ?
1824423,2019-09-12 11:47:39 UTC,"I forgot to mention that a fews days after my initial report, as Eric explained, openjdk11 has been released with java11, and collectd java plugin was ok."
1824424,2019-04-11 20:54:07 UTC,https://github.com/openstack/tripleo-quickstart-extras/blob/master/roles/overcloud-prep-config/defaults/main.yml#L15
1824424,2019-04-11 21:01:06 UTC,https://review.openstack.org/651928
1824425,2019-07-19 14:47:51 UTC,"If mine is the only report of this problem, then yes, it should probably be closed wontfix."
1824425,2019-07-19 15:04:03 UTC,Closing then. Thanks.
1824425,2019-07-19 14:23:07 UTC,"vorlon, as it only happens during the Cosmic -> Disco upgrade and Cosmic is EOL, should we close this then?"
1824425,2019-07-19 14:08:10 UTC,No. This only happened the one time during the cosmic to disco upgrade.
1824425,2019-07-19 11:35:04 UTC,"Does this happen repeatedly since your update, for example at every boot? If so, could you provide a log of network-manager in debugging mode, as described on"
1824429,2019-04-15 17:22:39 UTC,Assigning to Eric as he is already familiar with this issue and is working on a fix.
1824429,2019-04-15 17:23:21 UTC,Marking as release gating; as this is a would-be-nice to fix. Not very high priority.
1824429,2019-06-05 14:51:52 UTC,"When we increase the maximum supported host length from 32 to something larger, we also need to update sysinv to prevent the addition/modification of hostnames longer than what we support. The user should not be able to add a host with a hostname so long that it causes the system to malfunction."
1824429,2019-06-05 15:16:53 UTC,I have not seen the system malfunction as a result of adding an extra long hostname since sysinv supports 255 byte names. Such extra long names longer than 63 bytes just won't resolve in the kernel and the host won't come online.
1824429,2019-06-18 12:36:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665969"
1824429,2019-07-12 14:35:29 UTC,"Reviewed:  https://review.opendev.org/665969
Committed: https://git.openstack.org/cgit/starlingx/metal/commit/?id=a4238c2a355899aa4d6d9bcd429a7f8614041416
Submitter: Zuul
Branch:    master"
1824431,2019-05-20 14:57:52 UTC,Confirmed in 3.1.10
1824434,2019-07-08 04:17:29 UTC,[Expired for maas (Ubuntu) because there has been no activity for 60 days.]
1824434,2019-05-03 15:19:42 UTC,Any news on this please Andreas? I'm not sure how to process this SRU without your answer to my comment above.
1824434,2019-05-08 19:25:46 UTC,Rejecting this upload because it does not appear to meet current Ubuntu SRU policy and I haven't been given any argument to the contrary.
1824434,2019-04-26 22:24:20 UTC,"What's the current status of this please? Is the current upload in the queue still required for Cosmic? If so, I don't follow why we'd be wanting to put a beta into a stable Ubuntu release. Please could you explain?"
1824434,2019-04-29 10:42:17 UTC,"Oh sorry, s/Cosmic/Disco/, but my question is otherwise the same."
1824435,2019-10-25 17:40:51 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/691403"
1824435,2019-10-25 05:36:13 UTC,"Reviewed:  https://review.opendev.org/688205
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7c41365f193fd5b08d0174b6cd8e349ac95b7907
Submitter: Zuul
Branch:    master"
1824435,2020-03-13 20:57:42 UTC,"Just wanted to add a note on here, if you have already begun an upgrade (and run nova-manage db online_data_migrations) on a version prior to this fix landing and hit the error, there is a manual step you need to take in order for the upgrade (i.e. nova-manage db online_data_migrations) to work after you have applied the fix."
1824435,2020-02-06 12:45:31 UTC,This issue was fixed in the openstack/nova 19.1.0 release.
1824435,2019-11-12 11:30:40 UTC,This issue was fixed in the openstack/nova 20.0.1 release.
1824435,2019-11-07 21:29:01 UTC,"Reviewed:  https://review.opendev.org/692907
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a80eb82f675ae4c933158fc097094cbbbb96f9dd
Submitter: Zuul
Branch:    stable/stein"
1824435,2019-11-07 21:28:47 UTC,"Reviewed:  https://review.opendev.org/692906
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=844209b064ab4fd4d66ec8d9fc7dc106ae6d6d4b
Submitter: Zuul
Branch:    stable/stein"
1824435,2019-11-04 21:34:23 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/692907"
1824435,2019-11-04 21:34:00 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/692906"
1824435,2019-11-02 17:11:06 UTC,"Reviewed:  https://review.opendev.org/691403
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=416290f1938631a95aaaf92a41f455ebf75b0732
Submitter: Zuul
Branch:    stable/train"
1824435,2019-11-01 22:50:21 UTC,"Reviewed:  https://review.opendev.org/691402
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=73b6cb897ecbfe95e50eee632e5e6f5b5c29f7c4
Submitter: Zuul
Branch:    stable/train"
1824435,2019-10-26 01:58:01 UTC,"Reviewed:  https://review.opendev.org/688206
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6ea945e3b126879a86fe78d9c0537f5d258cf91a
Submitter: Zuul
Branch:    master"
1824435,2019-10-25 17:40:33 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/691402"
1824435,2019-10-11 21:50:02 UTC,"I've proposed a different fix for this after investigating locally in devstack using Iain's repro steps. I found that our code for ""get or create default security group"" is creating a duplicate default group for project_id=NULL (this works despite a unique constraint on project_id because unique constraints are only enforced on non-NULL values, as mentioned in earlier comments on this bug [1]) because the group create happens in a separate database transaction but a later read happens in the same/current database transaction. The current transaction cannot ""see"" the earlier inserted security group record because of transaction isolation [2]. The bug is not reproducible with SQLite because SQLite provides no isolation between transactions on the same database connection (which will always be the case if the insert and later read are happening in the same instance_create method call [3]."
1824435,2019-10-11 21:26:05 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/688205"
1824435,2019-10-11 21:26:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/688206"
1824435,2019-04-11 22:24:18 UTC,It's because the context doesn't have a project_id so the first pass creates a record with project_id=None:
1824435,2019-04-11 22:37:50 UTC,"(5:33:08 PM) mriedem: hmm yeah i'm not sure how https://github.com/openstack/nova/blob/03322bb517925a9f5a04ebdb41c3fd31e7962440/nova/db/sqlalchemy/api.py#L3874 can't either return at least 1 or raise
(5:35:47 PM) efried: oh, that part is because there's two rows in the database with the ""right"" project_id (NULL)
(5:36:05 PM) efried: mriedem: So the initial check (==) fails because there's *more* db rows than expected
(5:36:18 PM) efried: and then the for loop doesn't hit because all the names match (because they're the same)
(5:36:23 PM) mriedem: ah yup
(5:36:35 PM) mriedem: i don't know why the unique constraint doesn't blow up - because NULL isn't considered unique?
(5:36:39 PM) efried: so the problem is that we're somehow creating two rows, and I don't know how that ....
(5:36:42 PM) mriedem: schema.UniqueConstraint('project_id', 'name', 'deleted',
(5:36:42 PM) mriedem:                                 name='uniq_security_groups0project_id0'
(5:36:42 PM) mriedem:                                      'name0deleted'),"
1824435,2019-04-11 22:38:54 UTC,I guess this answers it:
1824435,2019-04-11 22:45:19 UTC,I'm not exactly sure how to reproduce this though. I was able to recreate the unique constraint issue in the database after creating a server and then running the online_data_migrations command a few times:
1824435,2019-04-16 16:40:02 UTC,Seems there are two issues here...
1824435,2019-10-17 20:05:58 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/678776
Reason: https://review.opendev.org/688206 is much simpler and has test coverage."
1824435,2019-04-16 19:59:41 UTC,Iain reports that https://review.openstack.org/653065 at least works around the issue. Also a potential recreate:
1824435,2019-04-16 20:41:23 UTC,imacdonn's recreate works for me in devstack: http://paste.openstack.org/show/749391/
1824435,2019-05-13 16:12:27 UTC,I ran into the same bug today on my devstack.
1824435,2019-08-20 21:33:20 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/653065
Reason: I'm not working on this, someone else will have to pick up working on the bug."
1824435,2019-08-27 10:02:15 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/678776"
1824435,2019-04-16 18:05:22 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653065"
1824438,2019-04-12 08:32:57 UTC,What problem did you experience at the first place? What's your goal when you execute the mentioned command?
1824438,2019-04-12 11:08:23 UTC,I experienced no problem save the creation of that file. I had read somewhere that the existence of such a file owed to a problem with either `/etc/profile` or some (any) file within '/etc/profile.d`. I had read further that a way to test any such files was to run them via `sh -n`. I followed that procedure rather blindly and encountered the message that I gave above. What you say makes me realise that in fact I have no reason to think there is a problem with vte.
1824444,2019-04-13 13:05:48 UTC,I tested with rocky version(tag 18.2.0)
1824444,2019-04-12 21:23:20 UTC,What release are you using?
1824444,2019-06-13 04:17:16 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1824445,2019-04-12 00:44:13 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651947"
1824445,2019-06-07 19:30:23 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.0.0 release.
1824445,2019-06-14 07:45:24 UTC,"Reviewed:  https://review.opendev.org/651947
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5c544c7e2a7e266d69a9d0f0bf3ee8a0c636202b
Submitter: Zuul
Branch:    master"
1824445,2019-06-21 13:47:34 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1824445,2019-06-21 15:25:30 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1824445,2019-07-05 12:52:45 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1824445,2019-09-27 09:02:53 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1824446,2019-04-25 13:55:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824446,2019-04-25 13:56:56 UTC,Please try running the following command and let us know whether that fixes the problem:
1824450,2019-10-23 06:40:20 UTC,"ipmctl:2.0
libsafec:3.5.2"
1824452,2019-04-12 03:02:51 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/651962"
1824454,2019-04-12 08:01:29 UTC,Weird that all tpm2 libs are not in /lib/x86_64-linux-gnu/:
1824454,2019-04-12 08:29:26 UTC,@Robert you can try checkbox-snappy from edge to verify the fix works (in revision 1947):
1824454,2019-04-12 10:12:09 UTC,"@Sylvain,"
1824456,2019-04-12 15:07:09 UTC,Did you try using ppa-purge as suggested? Its the oibaf graphics drivers PPA which is preventing you from being able to upgrade.
1824456,2019-06-12 04:17:21 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1824460,2019-10-16 06:27:38 UTC,"The issue with:
rm: cannot remove '/var/cache/snapd/aux': Is a directory"
1824461,2019-05-23 08:26:35 UTC,"OK everything looks good on Xenial too now, all autopkgtests green."
1824461,2019-05-23 08:35:48 UTC,This bug was fixed in the package docker.io - 18.09.5-0ubuntu1~18.10.2
1824461,2019-05-23 08:39:20 UTC,"The verification of the Stable Release Update for runc has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824461,2019-05-23 08:39:22 UTC,This bug was fixed in the package containerd - 1.2.6-0ubuntu1~18.10.1
1824461,2019-05-23 08:49:20 UTC,This bug was fixed in the package runc - 1.0.0~rc7+git20190403.029124da-0ubuntu1~18.10.1
1824461,2019-05-29 22:56:21 UTC,This bug was fixed in the package runc - 1.0.0~rc7+git20190403.029124da-0ubuntu1~16.04.3
1824461,2019-05-23 09:09:14 UTC,This bug was fixed in the package runc - 1.0.0~rc7+git20190403.029124da-0ubuntu1~18.04.1
1824461,2019-05-23 09:09:17 UTC,This bug was fixed in the package docker.io - 18.09.5-0ubuntu1~18.04.2
1824461,2019-05-29 22:54:17 UTC,This bug was fixed in the package docker.io - 18.09.5-0ubuntu1~16.04.2
1824461,2019-05-29 23:06:30 UTC,This bug was fixed in the package containerd - 1.2.6-0ubuntu1~16.04.2
1824461,2019-05-22 14:11:07 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-23 09:09:12 UTC,This bug was fixed in the package containerd - 1.2.6-0ubuntu1~18.04.1
1824461,2019-05-22 04:25:15 UTC,"An upload of runc to xenial-proposed has been rejected from the upload queue for the following reason: ""debian/runc.{templates,preinst} in source package when they shouldn't be""."
1824461,2019-05-07 22:22:25 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-22 00:30:15 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-07 21:41:14 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-22 02:31:42 UTC,Verification done on bionic and cosmic; xenial needs another fix for runc which is currently in UNAPPROVED.
1824461,2019-05-07 21:46:42 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-07 21:55:06 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-04 07:49:37 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-07 22:33:02 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-07 23:10:55 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-07 23:27:15 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-09 23:07:15 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-09 23:10:25 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-09 23:16:21 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-16 03:45:17 UTC,"The runc currently in xenial is too old for the new version of containerd, so I need to upload containerd with a more appropriate dependency."
1824461,2019-05-16 04:13:49 UTC,"Hello Michael, or anyone else affected,"
1824461,2019-05-07 23:15:05 UTC,"Hello Michael, or anyone else affected,"
1824462,2019-06-17 04:17:51 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1824462,2019-04-18 03:57:54 UTC,"I just noticed a similar issue, elsewhere in the GUI."
1824462,2019-04-12 04:53:55 UTC,"The bug report field asks me to paste in ""Contents of /var/log/maas/*"". That is several megabytes long. What exactly would you like to see from there?"
1824462,2019-04-12 13:07:59 UTC,Can you provide the output of:
1824462,2019-04-12 04:54:34 UTC,"steps to reproduce: not sure, sorry."
1824462,2019-04-12 04:54:15 UTC,expected behavior: all subnets in the subnet table are unique.
1824462,2019-04-17 05:44:55 UTC,"Unfortunately I have changed my setup since logging this bug, so I cannot provide more debug information."
1824465,2020-06-11 06:49:04 UTC,https://github.com/juju/juju/pull/11695 will be landed to 2.7 to fix this issue.
1824465,2020-06-09 11:13:07 UTC,"You need to start out with a 2.4 model and upgrade.
The initial model needs to be created with the old basic SKU type.
On the upgraded model, Juju will by default use the Standard SKU type, so you use the model config to switch it back to Basic. But in making API calls to Azure, Juju is missing places where the SKU type needs to be passed in, so there's a mismatch."
1824465,2019-11-20 05:24:16 UTC,So with the latest changes:
1824465,2020-04-08 22:58:26 UTC,Juju 2.6.10 btw.
1824465,2020-04-08 22:58:15 UTC,"Unfortunately, even with load-balancer-sku-name=Basic, it's failing now with this:"
1824465,2019-06-25 05:39:00 UTC,"Merge PR, bringing this change into develop: https://github.com/juju/juju/pull/10376/"
1824465,2020-06-09 08:08:05 UTC,"Hi Haw,"
1824465,2019-06-25 02:58:45 UTC,yep.
1824465,2019-06-25 04:32:18 UTC,"Merge PR, bringing this change into 2.6: https://github.com/juju/juju/pull/10375"
1824465,2019-06-14 16:19:50 UTC,This is having a production impact since units cannot be added to any Azure model created with an older Juju release.
1824465,2019-06-14 22:28:34 UTC,This is top of the queue to address. Sadly there doesn't appear to be a work around as far as I know. We'll look to get a fix out asap.
1824465,2019-06-14 11:07:39 UTC,Is there any workaround you can recommend here?  We need to scale out on azure for production services.
1824465,2019-06-25 02:11:35 UTC,Thanks for the fix - I presume this will also be addressed in the 2.6.x series?
1824465,2019-06-25 02:00:23 UTC,A fix[0] for this issue has been merged into the Juju 2.5 branch. This will be released as part of 2.5.8.
1824465,2019-06-25 02:55:35 UTC,"@Joel Sing (jsing),"
1824467,2019-04-12 05:50:40 UTC,"FWIW, even 'juju status --format=yaml' doesn't provide much information as to why it failed:"
1824469,2019-05-18 13:17:06 UTC,"after a little study on how others do this, I decided to think to the gmail behaviour"
1824469,2019-05-18 17:54:40 UTC,I got your point but you missed the AND I'm searching for.
1824469,2021-01-01 16:07:39 UTC,no one else seem to need this so I close.
1824471,2019-04-22 15:43:27 UTC,I only see Field Name Templates under Eeschema in the Preferences dialog.
1824471,2019-05-03 15:43:43 UTC,Sometimes one also fully specifies a part in EEschema and by not being able to get this information backported into a/the library one has to do it at least twice.
1824471,2019-08-23 23:40:05 UTC,This use to work and not having it really disrupts the workflow of anyone that maintains their own library.
1824474,2019-06-27 16:18:08 UTC,This bug was fixed in the package linux-meta-raspi2 - 5.0.0.1012.9
1824474,2019-06-27 16:05:16 UTC,This bug was fixed in the package linux-meta-raspi2 - 4.18.0.1018.15
1824474,2019-06-17 19:55:32 UTC,This bug was fixed in the package linux-meta-raspi2 - 4.15.0.1038.36
1824474,2019-06-17 20:03:54 UTC,This bug was fixed in the package linux-meta-raspi2 - 4.4.0.1111.111
1824475,2019-04-12 13:10:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824477,2019-06-27 20:14:48 UTC,"The patch was merge, but since it didn't include a 'Closes-bug' tag in the commit message, this bug won't be updated when changes are tagged into a release."
1824477,2019-06-28 13:34:07 UTC,"Hello, Brian, but it will remain in Neutron?"
1824477,2019-06-28 17:15:02 UTC,I don't understand the question.  The fix is in the neutron tree.
1824480,2019-04-12 08:09:38 UTC,"I see this a lot on the current batch of SSL Mojo specs, targeting the -next charms"
1824480,2019-04-12 09:44:32 UTC,https://github.com/openstack-charmers/openstack-mojo-specs/issues/108
1824480,2019-04-12 09:57:40 UTC,/var/log/gnocchi/gnocchi-api.log has the following at the time it fails setup
1824482,2019-04-12 11:38:26 UTC,I do not see any bug here: the cursor display is exactly what the options are.
1824482,2019-04-12 12:54:41 UTC,"@Silviu: the button on the left toolbar is to change the cursor shape, not the visibility. When the ""always show cursor"" option is disabled (empty checkbox), you will only see a cursor in tools that use it (e.g. routing)."
1824482,2019-04-13 13:02:23 UTC,"As far as I remember in the legacy of a short crosshair it was never there, you may need to enter the F9 mode"
1824482,2019-04-14 09:49:34 UTC,Don't get too used to Legacy mode; it won't be around much longer.
1824482,2019-04-14 18:25:37 UTC," @jean-pierre charras
 &
 @John Beard"
1824483,2019-04-18 01:46:32 UTC,"You can escape to the terminal by switching to another vt with ctrl-alt-f2 or similar. The files I'd be interested in are /var/log/syslog or the output of ""sudo journalctl"".  Of course getting the files off the server might be fun if the network isn't getting set up, I guess you'll need to plug another USB drive in or something?"
1824483,2019-04-17 12:27:48 UTC,"Not as far as I could see during the normal installation flow. As I can easily reproduce this issue, which logs would you like to receive? Please include instructions on how to escape to the terminal from within subiquity and the location of the logs you're interested in."
1824483,2019-04-16 10:32:40 UTC,"That's strange, the dhcp part is all handled by systemd-networkd really so I don't think any subiquity changes here are very relevant. Is there anything revealing in the journal or syslog?"
1824485,2019-04-23 16:56:20 UTC,"As the reported error message seems to point to mutter (I am using compiz), I start mutter issuing"
1824488,2019-04-15 22:26:39 UTC,Offline installs will be supported in the 19.04 installer. You could try the pre-release installer on http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/ and see if that works for you.
1824488,2019-06-17 04:17:50 UTC,[Expired for subiquity because there has been no activity for 60 days.]
1824490,2019-04-12 12:27:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1824497,2019-04-12 08:57:16 UTC,"Thank you for your bug report, it could be useful to report to the software writters directly on https://gitlab.gnome.org/GNOME/nautilus/issues/
(note that it could be a gvfs/glib(gio) issue, do you get the same problem with gio copy?)"
1824497,2019-04-12 11:19:33 UTC,"After further test
the files, the samba server is ubuntu 18.04 lts"
1824497,2019-04-12 11:35:04 UTC,gio copy hangs after the firt file
1824497,2019-04-12 11:36:08 UTC,so you think we have to search the problem with gvfs ?
1824497,2019-04-12 11:56:21 UTC,"IF the gio copy command has the same issue then yes it's probably gvfs rather than nautilus to blame, you should report your finding on https://gitlab.gnome.org/GNOME/gvfs since that's the right place for upstream code issues (the Ubuntu team does integration and contribute in those projects but on launchpad you then only hit a subset of the people who can help getting it resolved)"
1824497,2019-04-12 11:58:38 UTC,"ok thanks
ad."
1824497,2019-04-13 07:55:41 UTC,Transferred to this location :
1824497,2019-04-15 06:02:16 UTC,Thanks!
1824498,2019-04-16 12:33:30 UTC,"you need to click in the ""build: <arch>"" to have the deb, e.g
https://bugs.launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/15249000
There is no repo for those though"
1824498,2019-04-16 12:00:32 UTC,@seb128 Is there a repo I can enable/activate to install this previous version? In the page you linked I didn't see any .deb file....
1824498,2019-04-12 15:06:28 UTC,"What happens when you try to connect?
What kind of wireless connection are you using?
Do you have anything relevant in your log files?"
1824498,2019-04-15 15:32:45 UTC,"Once again today I couldn't connect to the SSID I normally use, I tried something in network manager, through the drop down menu ( accessible through left click on the network icon/indicator located on the upper panel, all the way down the menu, select ""modifications des connexions"" ( don't know the English version for sure ) select the wifi connection you usually use then press the button ""modify"", a configuration window opens up, on the second tab, ""Wi-Fi"" the ""Mode:"" setting was set on ""Client"" I changed it to ""Ad hoc"" and was able to connect right away.
I switched back to ""Client"" and will monitor the behavior..."
1824498,2019-04-12 17:53:16 UTC,"Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2340] device (wlp3s0): Activation: starting connection 'freebox_QXJRWG' (28620c8f-8ae4-4660-844a-ed7a34983236)
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2341] audit: op=""connection-activate"" uuid=""28620c8f-8ae4-4660-844a-ed7a34983236"" name=""freebox_QXJRWG"" pid=1517 uid=1000 result=""success""
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2343] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2344] manager: NetworkManager state is now CONNECTING
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2349] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2353] device (wlp3s0): Activation: (wifi) access point 'freebox_QXJRWG' has security, but secrets are required.
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2353] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2440] device (wlp3s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2447] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2449] device (wlp3s0): Activation: (wifi) connection 'freebox_QXJRWG' has security, and secrets exist.  No new secrets needed.
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2450] Config: added 'ssid' value 'freebox_QXJRWG'
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2450] Config: added 'scan_ssid' value '1'
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2450] Config: added 'key_mgmt' value 'WPA-PSK'
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2450] Config: added 'psk' value '<omitted>'
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2470] sup-iface[0x1b54570,wlp3s0]: config: set interface ap_scan to 1
Apr 12 19:49:02 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091342.2629] device (wlp3s0): supplicant interface state: disconnected -> scanning
Apr 12 19:49:05 Thinkpad-X220 wpa_supplicant[1177]: wlp3s0: SME: Trying to authenticate with ea:b4:4a:60:5c:08 (SSID='freebox_QXJRWG' freq=2412 MHz)
Apr 12 19:49:05 Thinkpad-X220 kernel: [39992.008249] wlp3s0: authenticate with ea:b4:4a:60:5c:08
Apr 12 19:49:05 Thinkpad-X220 kernel: [39992.012704] wlp3s0: send auth to ea:b4:4a:60:5c:08 (try 1/3)
Apr 12 19:49:05 Thinkpad-X220 wpa_supplicant[1177]: wlp3s0: Trying to associate with ea:b4:4a:60:5c:08 (SSID='freebox_QXJRWG' freq=2412 MHz)
Apr 12 19:49:05 Thinkpad-X220 kernel: [39992.015930] wlp3s0: authenticated
Apr 12 19:49:05 Thinkpad-X220 kernel: [39992.018893] wlp3s0: associate with ea:b4:4a:60:5c:08 (try 1/3)
Apr 12 19:49:05 Thinkpad-X220 NetworkManager[1042]: <info>  [1555091345.3798] device (wlp3s0..."
1824498,2019-04-12 17:05:37 UTC,"@mdeslaur Thanks for replying quickly.
When I try to connect, the wifi indicator in the panel turn for ~103 sec, ( usually it was replaced by the wifi icon and ESSID name when it worked ) and then the ethernet icon appears but since there's no network cable plugged...
About the log I ran this script https://forum.ubuntu-fr.org/viewtopic.php?id=1089311 but I'd rather not post everything that came back here ( list of all available SSID, etc....) but if you point me toward what you need I'd be glad to provide you some of it"
1824498,2019-04-16 06:11:30 UTC,If it's easy to trigger maybe you could try to downgrade to https://bugs.launchpad.net/ubuntu/+source/wpa/2.4-0ubuntu6.3 to confirm the problem is resolved with that version (so we are sure it's an issue with the wpa update)
1824502,2019-04-13 23:10:32 UTC,"On the other hand, pre splitting classes, which is primarily how HTMl if navigated also makes things faster, so I don't know what is better."
1824502,2019-07-07 20:57:55 UTC,"Thanks for the feedback, I'll have a look at this. Thanks again for all the great work you did with BeautifulSoup!"
1824502,2019-07-07 20:43:51 UTC,"My fix to bug 1832978 makes it possible to customize or disable the process by which certain attributes are converted to lists. Although this doesn't precisely recreate the old behavior, it does make your underlying goal possible -- to find a tag by its exact string class value."
1824502,2019-04-13 22:35:27 UTC,"> Thus, I just wished that somehow, a similar processing what done on the input string provided to find to ensure that we do find what we'd expect to find (and what used to be found on older versions of BeautifulSoup).
"
1824502,2019-04-12 16:11:18 UTC,Here is my suggestion for a fix but I don't find it very satisfying:
1824502,2019-04-12 16:26:28 UTC,"Unfortunately whitespace was collapsed in my previous comment, but basically I was trying to illustrate that if you had multiple whitespace characters, bs4 always collapsed them between attributes so you never had 1:1 of what was in the document."
1824502,2019-04-12 16:23:52 UTC,"As I recall, BeautifulSoup has always turned certain attributes that are generally treated as lists to lists in the attribute dictionary. Previously, the logic would sometimes create lists with empty entries when dealing with leading or trailing whitespace `['', 'classname', '']`. This was weird, and kind of unexpected."
1824502,2019-04-12 14:14:05 UTC,After a deeper investigation with the following unit-test added in class HTMLTreeBuilderSmokeTest(object):
1824502,2019-04-12 14:20:08 UTC,Adding the relevant test in the relevant place:
1824502,2019-04-12 16:52:41 UTC,Thanks for your feedback.
1824505,2019-08-24 12:37:13 UTC,"It appears to be fixed in the master and 5.1 branches at least on MSW.  It also appears to be fixed in 5.1.4 so I'm setting this to fix released.  If someone can reproduce it, please set it back to confirmed."
1824505,2019-07-08 21:44:29 UTC,"@Wayne, the footprint loader/renderer is multi-threaded.  When arrowing down it will push the footprint to be loaded into the queue, and then will receive an event when it's ready.  When arrowing up they're already loaded, so they're just drawn."
1824505,2019-08-23 02:56:09 UTC,I suspect that this has been resolved.  I can no longer repeat it using Wayne's steps.  Anyone still seeing it?
1824505,2019-04-14 21:36:45 UTC,Addition:
1824505,2019-04-14 21:22:50 UTC,"There is no visible text that indicates any error or ""loading..."""
1824505,2019-04-14 19:44:27 UTC,I can't reproduce this on OSX.
1824505,2019-05-06 13:29:05 UTC,"I narrowed this down.  It only happens when using the down arrow key to navigate the footprint list and the footprint hasn't been loaded from the file.  Once the footprint has been loaded, then the down arrow key will show the footprint.  Interestingly, moving the cursor after pressing the down arrow key will cause the footprint panel to redraw and show the footprint.  Here are the steps to reproduce:"
1824507,2019-10-15 00:27:26 UTC,"https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1402059
and
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1576605"
1824507,2019-10-15 00:25:16 UTC,"#1402059 and #1576605 are probably related, namely, the unity-menubar.patch is filled with incomplete realization of exporting things and dirty hack on firefox UI"
1824507,2019-07-20 19:09:10 UTC,apport information
1824507,2019-07-20 19:15:55 UTC,"the apport is running under live iso of kubuntu, since the bug exist for long and holds true even on fresh live rom, I expect the apport has little help here..."
1824507,2019-07-20 19:09:12 UTC,apport information
1824507,2019-07-20 19:09:08 UTC,apport information
1824507,2019-07-20 19:09:00 UTC,apport information
1824507,2019-07-20 19:09:04 UTC,apport information
1824507,2019-07-20 19:09:03 UTC,apport information
1824507,2019-07-20 19:09:01 UTC,apport information
1824507,2019-07-20 19:08:58 UTC,apport information
1824507,2019-07-20 19:08:56 UTC,apport information
1824507,2019-07-20 19:09:06 UTC,apport information
1824507,2019-07-19 16:00:05 UTC,"Thanks for the report.
Can you please run the following command in a terminal to attach additional information to the bug report?"
1824508,2019-07-28 17:07:28 UTC,...and it seems problem arise when there is a pin connection point in close proximity
1824508,2019-07-28 17:02:09 UTC,"IMO the issue is with object selection.  I try to be more specific:
If there are two crossing but not attached wires, and I select the crossing,
instead of displaying a Clarify box for choosing from the two wires, a strange block gets selected and dragged. See attached video. The first case is the issue...others are fine."
1824508,2019-07-28 03:47:42 UTC,"Eeschema now supports selections.  The label is selected, so it gets dragged."
1824508,2019-07-27 22:28:09 UTC,"I still see this issue.
Attached screenshot shows what happens when dragging a wire corner.
The corner gets dragged correctly and one end of the wire stays put.  But the global label object is also dragged, which is wrong."
1824508,2019-04-24 03:05:07 UTC,This appears to be fixed as of d281f051ed9fe2156dbc9615149186dbc725f120.
1824508,2019-04-23 08:30:51 UTC,"Sorry, all I know that I've experienced dramatic speed increase lately: moving larger blocks of schema was terrible in older versions: block redraw took 2..5 seconds; now it is redrawn at 20-30+  fps."
1824508,2019-04-24 12:35:04 UTC,"I quickly tested this and couldn't recreate the original issue, so setting this as fix committed for now. However, Eeschema in the master branch is currently under heavy development at the moment so I'd expect there to be more issues/behaviour changes in the future."
1824508,2019-04-22 18:18:12 UTC,"No, it happens already on Accelerated modern toolset (F11). This mode is really great, as moving large blocks are fast now (and was painful at older eeschema), but the Clarify menu should be re-designed to be able to catch wire corners.
Anyway, version info should contain the actual graphics mode, as we are in a permanent transition for years."
1824508,2019-04-22 17:44:09 UTC,This will likely be changed with the introduction of the modern toolset.
1824508,2019-04-22 19:26:47 UTC,"@Novak, Eeschema still uses the Legacy toolset but with the modern canvases for rendering (yes the Preferences menu is misleading). It will be moved over to the Modern toolset in v6 (work currently in progress) where the selection tool model will change."
1824508,2019-04-22 18:24:43 UTC,"One more video, even more strange. (the first case when the upper junction moves)"
1824509,2019-04-12 10:05:16 UTC,"the log:
520 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage Traceback (most recent call last):
521 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/cinder/cmd/manage.py"", line 350, in _run_migrati    on
522 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     found, done = migration_meth(ctxt, count)
523 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/cinder/cmd/manage.py"", line 127, in shared_targe    ts_online_data_migration
524 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     non_shared_hosts, total_vols_to_update = _get_non_shared_target_hosts(ctxt)
525 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/cinder/cmd/manage.py"", line 110, in _get_non_sha    red_target_hosts
526 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     capabilities = rpcapi.get_capabilities(ctxt, service.host, True)
527 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/cinder/volume/rpcapi.py"", line 341, in get_capab    ilities
528 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     return cctxt.call(ctxt, 'get_capabilities', discover=discover)
529 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py"", line 179, in call
530 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     retry=self.retry)
531 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/oslo_messaging/transport.py"", line 133, in _send
532 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     retry=retry)
533 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 584    , in send
534 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     call_monitor_timeout, retry=retry)
535 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 573    , in _send
536 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     call_monitor_timeout)
537 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 459    , in wait
538 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     message = self.waiters.get(msg_id, timeout=timeout)
539 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage   File ""/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py"", line 336    , in get
540 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage     'to message ID %s' % msg_id)
541 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage MessagingTimeout: Timed out waiting for a reply to message ID 79fc13882d1945d9b8a60e8fcbd    eccb0
542 2019-04-12 16:38:59.542 139 ERROR cinder.cmd.manage"
1824509,2019-04-15 16:02:12 UTC,"Similar to https://bugs.launchpad.net/cinder/+bug/1806156 - different circumstances, but a solution that doesn't rely on an RPC call could solve both..."
1824509,2019-04-16 07:12:16 UTC,yes.This is similar to https://bugs.launchpad.net/cinder/+bug/1806156.But I think the db migration shouldn't rely on the service status.
1824520,2019-04-12 12:30:07 UTC,This change was made by a bot.
1824520,2019-04-12 15:04:29 UTC,"Please attach full dmesg and `rfkill list` when this issue happens, thanks!"
1824520,2019-04-15 06:08:42 UTC,https://github.com/systemd/systemd/issues/10704
1824520,2019-04-19 11:53:12 UTC,Both AT Keyboard and Dell-RBTN emit wireless hotkey event. I think we should handle this in kernel to let only one driver to handle the event.
1824520,2019-05-07 05:33:04 UTC,This is fixed in Disco. Cosmic needs to be fixed though.
1824520,2019-04-15 04:28:12 UTC,"Before hitting the airplane mode key
$ rfkill list
0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: nfc0: NFC
 Soft blocked: no
 Hard blocked: no
2: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no"
1824522,2019-05-12 08:29:23 UTC,"I have walked through all of those instructions with the exception of the parts which require registration on the Nvidia site for downloads, and I was unable to reproduce the problem of the deleted python modules.  If it was caused by that ppa, perhaps the problem has since been fixed?"
1824522,2019-07-13 04:17:54 UTC,[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.]
1824522,2019-05-13 05:59:59 UTC,"On Sun, May 12, 2019 at 09:30:12AM -0000, WIlliam PIAT wrote:

> Sorry to hear this wasn't helpful
"
1824522,2019-05-12 09:30:12 UTC,"Sorry to hear this wasn't helpful
We did the installation on 3 computers and only mine was subject to these
errors.
Do you want me to get some extra information from these computers to
compare them to my configuration?
What we you be interrested in? Installed Python packages? Installed apt
package? List of softwares?
William"
1824522,2019-05-10 23:40:15 UTC,This part might have something to do with the issue:
1824522,2019-04-18 23:33:26 UTC,"On Thu, Apr 18, 2019 at 08:20:15AM -0000, WIlliam PIAT wrote:

> output of dpkg -I python3-chardet: (Sorry for it being in french):
"
1824522,2019-04-18 08:20:15 UTC,output of dpkg -I python3-chardet: (Sorry for it being in french):
1824522,2019-04-17 23:27:40 UTC,Do you know why /usr/lib/python3/dist-packages/chardet is missing?  What is the output of 'dpkg -l python3-chardet'?
1824522,2019-04-12 16:31:25 UTC,"It is present in the folder : /usr/local/lib/python3.6/dist-packages
but not in the folder : /usr/lib/python3/dist-packages/
Should I simply copy the first folder
(/usr/local/lib/python3.6/dist-packages/chardet) to the second one (
/usr/lib/python3/dist-packages/chardet)?"
1824522,2019-04-12 16:18:00 UTC,"Yes chardet is, indeed, missing from my system
William"
1824522,2019-04-19 00:47:17 UTC,"Lucky for you, as the installation we made was for my current company we
traced all the steps we followed and I can give you the excerpt of the
report related to our installation of python3.6:
I hope this will prove useful to you"
1824522,2019-04-12 15:50:15 UTC,The error in your log is:
1824525,2019-04-12 15:01:12 UTC,"[    2.536487] psmouse serio1: synaptics: Your touchpad (PNP: DLL060d PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to <email address hidden>."
1824525,2019-04-12 12:30:17 UTC,This change was made by a bot.
1824528,2019-04-12 13:04:34 UTC,This struct represents the MTP protocol wire format so *must* be marked packed.
1824528,2019-04-12 13:05:50 UTC,"As a workaround, the simplest thing is to configure with --disable-werror, which will reduce these from errors to warnings. (This is the default if you're building from one of our release tarballs, but for builds from git we default to making all warnings into errors so we catch and fix them quickly.)"
1824528,2019-04-16 10:16:31 UTC,"Sure, Thanks, using the workaround to proceed."
1824528,2019-04-18 10:21:45 UTC,Fixed in
1824528,2019-05-09 16:35:47 UTC,The fixes for this issue in dev-mtp.c are now in QEMU git master and will be in the 4.1 release.
1824528,2019-04-12 12:53:57 UTC,"Tried to patch as below and it compiles fine, not sure if this is right fix though,"
1824530,2019-04-12 15:48:54 UTC,"Hi Dikkie,"
1824530,2019-04-12 16:11:33 UTC,"Heya Mike,"
1824530,2019-04-12 19:00:20 UTC,It's no trouble at all. Thanks!
1824534,2019-04-16 16:30:00 UTC,Hi.
1824534,2019-06-16 04:17:28 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1824539,2019-04-12 15:04:25 UTC,"Indeed, thank you for your bug report.  It's too late to change the string in disco now (it would invalidate the translations) but we should fix that next cycle"
1824539,2019-05-18 11:12:57 UTC,"it's fixed in git now
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-initial-setup/commit/?id=abb11c8d7"
1824539,2019-08-22 10:44:37 UTC,This bug was fixed in the package gnome-initial-setup - 3.33.91-1ubuntu1
1824550,2019-04-12 15:48:37 UTC,What WM are you using?  I'm not seeing either problem with gtk 3.24 on my Debian testing box.  I'm running a vanilla gnome desktop.
1824550,2019-04-12 18:34:17 UTC,"ah, right.
this is the xubuntu variant, with xfce"
1824550,2019-04-12 18:36:29 UTC,"to be more precise, this happens after a while. the UI is fine on startup. then after routing some lines, it starts to bug up"
1824550,2019-04-12 18:57:12 UTC,"I run xfce and have not noticed these issues.  Given the location of them, I suspect that this is graphics driver related."
1824550,2019-04-13 22:22:33 UTC,it does the same thing whichever toolset is used.
1824550,2019-04-14 02:42:58 UTC,It looks like that is grabbing image data from a different application.
1824550,2019-05-08 19:44:44 UTC,"I too am affected by this - after hiding/showing the Layer Manager 3-4 times these shiny metal tabs disappear. I can also see through some dialogue's drop-down selectors. Thought it's just my setup, my computer has Nothbridge Radeon graphics (not APU) and therefore (just) mesa GL...
The problem in the about dialog first looked like a too small pane for tabs 2-6, but after clicking on the shiny metal tabs it got weirder."
1824550,2019-05-08 19:45:37 UTC,About dialog after some tab changes...
1824550,2019-07-09 20:54:54 UTC,"@Nick,
sorry I did not have the time to install a development version by now. So, still on
'Version: 5.1.2-f72e74a~84~ubuntu18.04.1, release build'
, yes the problem is still there.
I guess the garbled About-Dialogue has its cause in that some panes have a horizontal stretch property, the others vertical stretch, but I did not touch wxwidgets since the time it had been called wxwindows :)
For the other redraw errors and choked click-events I did not dig any further, but if these widgets are WxAui elements then I fear the problems arise upstream."
1824550,2019-07-08 08:26:18 UTC,"@Guenter, is this still an issue?"
1824550,2019-04-14 06:20:34 UTC,"it's an intel integrated graphics, with the default drivers on ubuntu 18.04
looks to me that pcbnew is the only application doing that"
1824550,2019-05-08 19:58:40 UTC,"BTW it's not a foreign graphics buffer, it's just the underlying window/Desktop"
1824550,2019-07-08 04:17:30 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1824551,2021-02-06 12:25:30 UTC,"Closing, this issue, as the patch was committed here: https://gitlab.com/qreator-dev/qreator/-/commit/eb1b4b6413a187e60182419565728661fd13ca15 - Thanks!"
1824553,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1824553,2019-05-14 22:54:39 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824554,2019-07-08 22:10:29 UTC,"I'd prefer not.  This was a valid board in v5, so we shouldn't break it in v6."
1824554,2019-04-19 11:23:34 UTC,"After tests, I am not sure there is an issue in Pcbnew:"
1824554,2019-04-18 14:57:42 UTC,"Yes, like you, Jon, I am now convinced there is an issue in Pcbnew in connectivity calculations:
It really looks like it does not always rename tracks connected to pads according to the new net of these pads.
Obviously, any track connected to a pad must always inherit the pad net name."
1824554,2019-07-08 21:46:00 UTC,"Shall we close this one as ""Won't Fix""?"
1824554,2019-04-18 03:15:13 UTC,@Jon-
1824554,2019-04-18 02:55:46 UTC,"This took me wayyy too long to figure out:
There is no bug here; the design as checked in to Git is not consistent.
The behavior with old and new netlisting algorithms appears to be the same, so I'm going to close this out."
1824554,2019-04-13 12:58:24 UTC,Not quite clear what's up
1824554,2019-04-18 14:12:33 UTC,"This is a ""problem"" in pcbnew and has nothing to do with the new netlisting code in eeschema.
Because of the nature of the design change in the schematic, the pcbnew netlist updater is faced with a situation where both the old and the new net names exist, which seems to trip up the connectivity updater which is responsible for renaming tracks and vias when pads change their name."
1824557,2019-04-12 17:46:58 UTC,This is fixed by https://github.com/snapcore/snapd/pull/6717
1824559,2021-01-21 17:13:29 UTC,"Funny I was having this problem, or at least similar, and I found out the wifi was interfering. Moving the router away from the laptop resolved the issue."
1824559,2020-05-07 13:51:42 UTC,"Hi, I migrate my laptop to Manjaro, but kernell 5.6.8-1 is still slow and laggy with the yoga mouse"
1824559,2019-11-14 17:28:01 UTC,"Hi @pieq, juste tested with ubuntu 19.10 live session (I just paired the mouse with bluetooth GUI and moved the cursor around with the lenevo mouse).
The cursor is slow and laggy with the lenovo mouse (it's ok with trackpad)."
1824559,2019-10-22 05:26:22 UTC,"Hi @pieq, following your message I launched download of Ubuntu 19.10 image.
I will test with live session as suggested (as I keep my laptop on LTS for the moment)"
1824559,2019-10-22 02:29:41 UTC,"Device: XPS 13 7390
Image: 19.10 Final
Kernel: 5.3.0-19-generic"
1824559,2019-10-02 09:15:59 UTC,"Device: XPS 13 7390
Image: 19.10 Beta
Kernel: updated to 5.3.0-13-generic (from 5.3.0-10-generic)"
1824559,2019-09-20 08:51:32 UTC,"XPS 15 9570 Ubuntu 18.04 Linux 5.2.10
Logitech MX Master (M-R0052)"
1824559,2019-09-09 18:36:25 UTC,I just reproduced this issue with a bluetooth mouse 3600 on 18.04.3 LTS on a thinkpad x230.
1824559,2019-09-20 08:47:41 UTC,+1 Solved by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559/comments/10
1824559,2019-09-02 15:35:41 UTC,"Hi,
Following giors post #9 and a similar suggestion I get from a reddit user, I did the following:"
1824559,2019-04-12 16:21:52 UTC,Attached evhz output in case it helps.
1824559,2019-04-12 16:28:31 UTC,"Added bluetoothctl ""info"" output."
1824559,2019-04-15 03:01:41 UTC,"Thanks for the detailed bug report. I suspect the low polling frequency has more to do with the kernel than with bluez, so reassigning there."
1824559,2019-04-15 03:05:17 UTC,Please also try the Atheros kernel options mentioned in bug 1746164 (which is about Atheros wifi causing a low quality Bluetooth signal).
1824559,2019-09-07 15:09:54 UTC,I have Ubuntu 18.04 on a Dell XPS 13 with a Logitech bluetooth mouse m720 triathlon with the same issue (20Hz polling rate by default). Following the steps given by wysiwyg31 in #10 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559/comments/10) solved my issue.
1824559,2019-04-18 20:48:56 UTC,"Hi!
Similar problem with my old HP netbook (fresh ubuntu 18.04.02 install)"
1824559,2019-06-06 19:00:33 UTC,"in case it bring some information, a similar issue was reported here on Antergos:"
1824559,2019-08-07 06:21:07 UTC,"Hi!
Similar problem with a Lenovo T480 paired with M590 mice.
The solution found here
https://bbs.archlinux.org/viewtopic.php?pid=1857256#p1857256
works for me"
1824559,2019-04-15 08:07:58 UTC,"Hello Daniel,
Thank you for your answer!
OK for kernel assignment...to be honest, I was not sure where to assign it :)"
1824562,2019-04-12 16:45:20 UTC,"Before I was certain that this was a terminator bug, I created an issue in github for Cursive which you can find under https://github.com/gyscos/Cursive/issues/334. It also contains 2 screenprints that show the problem."
1824562,2019-04-13 08:42:46 UTC,Is it possible that Terminator has some shortcut that sends a command to all terminator incarnations?
1824562,2019-04-15 07:51:38 UTC,I found the shortcut that causes terminator to send the commands to all terminator instances. It is `alt-a`. The problem started from accessing the menu of an ncurses program that I was testing at the moment and the menu item started with an `a` (account). So I pressed `alt-a` and when the program didn't respond I just used a different menu option to enter the menu and navigated to account. What I didn't know was that all input I entered there after was sent to all terminals creating havoc on what I was doing (using vi).
1824562,2019-04-20 15:22:06 UTC,"As someone on the project pointed out, if you hit alt-a without knowing of its existence or while in an text-user-interface program (using ncurses, termion etc), unaware of what it is doing, it could be pretty dangerous if you subsequently enter userid / password in some other application (irc chat)."
1824562,2019-08-25 10:09:57 UTC,"Hello, Guus Bonnema!"
1824562,2019-08-25 10:12:21 UTC,"So I think the main idea of this bug report could be like this: ""User can't see the state of broadcasting feature if title bar switched off."""
1824562,2019-08-25 11:01:34 UTC,"I don't think I have the title bar switch off. I see a title bar, but I do not see any indication that it is broadcasting my commands to the other instances of terminator."
1824562,2019-08-25 11:03:47 UTC,"Yes, I can see a very small change in color on the title bar in the icon. But only if you already know what it means you might see it, and even then you might not see it because the icon change is pretty subtle."
1824566,2019-05-29 21:27:29 UTC,This issue was only seen in stable/ocata  and the patch had merged.
1824566,2019-04-12 17:52:15 UTC,"Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/652122"
1824566,2019-05-24 10:23:50 UTC,"Reviewed:  https://review.opendev.org/652122
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=85c1edd474fb659ebef709dade536abda83abd49
Submitter: Zuul
Branch:    stable/ocata"
1824569,2019-04-12 21:12:34 UTC,"Please note that this is not a regression, since it has been failing on xenial/linux-aws for a while."
1824570,2019-05-02 17:40:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824570,2019-05-02 17:56:13 UTC,Same here in Kubuntu 19.04 with
1824570,2019-05-06 13:15:28 UTC,Same here. Upgraded to 19.04 and now KOranizer Daemon crashes upon login and on any attempt to restart or run manually. Apport for some reason won't let me submit a bug (grayed out). Terminal output is as follows:
1824570,2019-09-12 17:21:26 UTC,The last update appears to have been 4 months ago. This is to just say it is still a problem...
1824571,2020-01-29 22:39:21 UTC,"Hello,"
1824571,2019-10-23 08:53:54 UTC,I'm taking back my earlier statement. The log message still occurs in 14.0.2 in a HA DVR environment.
1824571,2019-10-21 02:02:53 UTC,"If anyone has a second, I'm not sure if I'm hitting the same issue but I would just like to confirm. I am seeing two similar logs when I create two external networks within the same project."
1824571,2019-10-14 12:35:13 UTC,"My bad, kolla-ansible didn't properly respond to its upgrade playbooks and decided only to upgrade to 14.0.0 where the problem actually occurs."
1824571,2019-10-14 12:22:43 UTC,"Just to clarify, i upgraded from 13.0.4 -> 14.0.2 and getting this message. Using HA and DVR in this deployment."
1824571,2019-10-14 12:19:06 UTC,So I have kept rocky neutron in a overall stein installation but I'm still getting this issue in neutron 14.0.2. Here are the logs:
1824571,2019-09-19 10:13:33 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1824571,2019-07-01 02:49:07 UTC,This issue was fixed in the openstack/neutron 14.0.2 release.
1824571,2019-05-31 15:09:26 UTC,"Thank you very much Brian, very informative !
And Great News ... looking forward to the review !"
1824571,2019-05-31 13:39:17 UTC,"Hello everybody,"
1824571,2019-05-28 23:00:51 UTC,"Reviewed:  https://review.opendev.org/661509
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0b3f5f429d2e495eb78d78d46186092ac735e0d5
Submitter: Zuul
Branch:    master"
1824571,2019-05-28 19:59:16 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661835"
1824571,2019-05-28 13:57:51 UTC,Proposed fix at https://review.opendev.org/#/c/661509/ - somehow bug didn't get auto-updated.
1824571,2019-05-26 22:04:50 UTC,"This regression was introduced when we merged https://review.opendev.org/#/c/567369/, which removed the external_network_bridge option. Per commit message in change https://review.opendev.org/#/c/59359, ""l3 agent can handle any networks by setting the neutron parameter external_network_bridge and gateway_external_network_id to empty"". After removing the external_network_bridge option, we no longer perform this check https://github.com/openstack/neutron/blob/946faaf361003a0a67081be28565d3815c354510/neutron/agent/l3/agent.py#L311-L315, so we cannot no longer have several external networks"
1824571,2019-05-25 23:37:07 UTC,I can replicate this issue in an environment running master branch. When setting the external gateway:
1824571,2019-05-10 10:29:42 UTC,I set it as critical because at least 3 different people hits this issue already and were asking about it in neutron irc channel and OpenStack mailing list.
1824571,2019-04-15 21:25:02 UTC,This could be related to https://review.openstack.org/#/c/567369/ or at least is something to look at.
1824571,2019-05-31 14:12:24 UTC,"Florian - we try and tag all the stable branches on every release milestone, the next one being T-1 on June 6th [0].  Looking at stable/stein reviews we have only two outstanding, so once they merge I will send out a review to tag it."
1824571,2019-05-30 02:38:07 UTC,"Reviewed:  https://review.opendev.org/661835
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=62e0bee8206491690bd6b6b72fc38d9694d5083f
Submitter: Zuul
Branch:    stable/stein"
1824575,2020-06-09 04:40:53 UTC,Please test 20.04.
1824575,2020-08-09 04:17:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824575,2019-08-22 05:23:37 UTC,Does the same issue happen to Ubuntu? Sounds like it's a user space bug.
1824575,2019-08-22 00:37:53 UTC,"I was able to resolve this problem by setting
HandleLidSwitch=ignore
in /etc/systemd/logind.conf"
1824575,2019-04-12 19:30:07 UTC,This change was made by a bot.
1824575,2019-08-23 02:25:59 UTC,"Yes, I am using Kubuntu 18.04."
1824576,2019-04-15 03:04:56 UTC,"Yes, as a user, if I am not an admin, then I should only be able to get the current user or the specified user's instances. This problem exists not only in the rocky branch, but also in the master."
1824576,2019-04-15 08:16:59 UTC,I don't agree with allowing the user filter for non-admins. Sure its helpful for shared projects but for the whole cloud this should be an admin only filter. So if we are allowing this then we should do this per project (of which the requesting user should be a part of) per user which sort of redefines the meaning of the user filter: it would become more of a per project per user filter.
1824576,2019-04-15 08:58:10 UTC,"@tssurya, I think this is not contradictory. The admin is not limited to this restriction. Project users should only be able to obtain their own instance. Why do you want to get all the instances below the project? In theory, in a production environment, it is very dangerous to be able to see the server created by others."
1824576,2019-04-15 09:27:09 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/652602"
1824576,2019-04-15 14:21:38 UTC,I agree with @tssurya.
1824576,2019-07-22 01:37:10 UTC,"Change abandoned by Brin Zhang (<email address hidden>) on branch: master
Review: https://review.opendev.org/652602"
1824578,2019-06-14 04:17:27 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1824578,2019-04-15 03:12:24 UTC,"Sounds a little like bug 1769383, but you would have the fix for that already."
1824578,2019-04-12 19:58:17 UTC,"Hello Eyal, do you care about keeping the contents of your clipboard pastes private? the easiest way to get feedback on this bug is to make it public but I don't wish to do that if you've got content on that clipboard tool you'd like to keep private."
1824578,2019-04-12 19:38:56 UTC,"18.04.2 LTS
Keep Awake! gnome extension (maybe the cause?)
gnome 3.28.2"
1824578,2019-04-12 22:59:06 UTC,"No problem, make it public."
1824581,2019-04-23 14:31:59 UTC,The ``neutron-openvswitch`` charm needs to learn to deal with being deployed in a container differently than if it is on bare metal/in a VM.
1824581,2019-05-14 12:08:12 UTC,"I'm marking these as invalid/triaged on the idea that this needs to be resolved in the OVS charm by better handling being inside of a container. Additionally, it may be a better solution to, as Frode points out, deploy an additional OVS charm to reside with Octavia."
1824581,2020-07-22 12:51:49 UTC,"DVR, L3HA and enablement of metadata and local dhcp services are all now guarded with:"
1824581,2020-07-22 12:58:17 UTC,However I expect there is a load more that still needs to be guarded - DPDK and SR-IOV being two immediate features that spring to mind but won't work when deployed inside a container.
1824582,2019-04-23 08:54:20 UTC,"Reviewed:  https://review.opendev.org/653455
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=2f8b158b152d1e39022cb69cdde0bd906244a418
Submitter: Zuul
Branch:    master"
1824583,2020-02-25 10:47:54 UTC,"Hi Adnan
Since I cannot reproduce this bug and 19.04 has reached it's ""end of life"", I'll mark this bug as invalid. I recommend that you update to 19.10 or the soon to come 20.04."
1824583,2020-04-26 04:17:26 UTC,[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.]
1824584,2019-04-17 10:04:51 UTC,"Re-hello,"
1824585,2019-06-13 19:11:32 UTC,@Ken noted that he doesn't see this any longer and it is addressed. Marking incomplete so if anyone can find/repro it please add to the bug.
1824585,2020-01-01 04:18:04 UTC,[Expired for juju because there has been no activity for 60 days.]
1824586,2019-04-13 19:48:37 UTC,"Basically I would prefer not to report bugs against development branches and rather use the review process or a PM to do so. this would avoid cluttering the bug list.
If a bug is reproducible in trunk this is a different story of course."
1824586,2019-09-15 15:07:11 UTC,Migrated to https://github.com/widelands/widelands/issues/3410
1824586,2019-04-13 09:03:16 UTC,"Thanks, fixed :) Is this bug 'fixed committed' then?"
1824586,2019-04-13 07:21:43 UTC,"Since the ferry branch makes big changes to the economies, it's not clear if this would happen on trunk too."
1824586,2019-04-13 08:04:14 UTC,"This is a bug in the ferry branch, will push a fix soon"
1824586,2019-04-12 21:31:16 UTC,Will try to attach a save game tomorrow.
1824586,2019-04-13 08:08:32 UTC,"Thanks benedict, anyway here is a savegame. Just wait until the atlanteans small tower is conquered."
1824588,2020-03-16 18:09:28 UTC,"`sudo killall -9 gdm` immediately fixes the ""unresponsive"" problem for me. But you have to SSH into the box to do this, which is an extreme bandaid"
1824588,2020-01-24 09:09:12 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1824588,2019-05-01 16:14:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824588,2019-04-18 03:41:28 UTC,This problem is probably related to:
1824588,2019-04-18 03:12:22 UTC,I will follow up ASAP. The plot continues to thicken. I tried a different set of hardware today with a B43 chipset and it didn't seem to be effected. But that board has only DVI and VGA outputs whereas the effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI so now I ran another range of tests using DVI on the effected board and was unable to reproduce.
1824588,2019-04-17 05:30:18 UTC,"Sadly /var/crash is empty, and errors.ubuntu.com + whoopsie-id just displays a blank page. Also applying the workaround from bug 994921 does not result in creating a crash report."
1824588,2019-04-16 04:16:28 UTC,Thanks. This appears to be the most interesting part of the log I can see:
1824588,2019-04-16 04:16:22 UTC,"Based on those most recent results I ran ""dpkg-reconfigure grub-pc"" and removed ""quiet splash"". Now it boots to the gdm3 screen every time. So maybe something to do with how plymouth hands off the boot process to gdm3? Or how quickly that hand off is completed?"
1824588,2019-04-17 05:44:58 UTC,That sounds like a different bug; the login screen never appearing. Although both bugs might end up benefiting from a single fix.
1824588,2019-04-16 02:25:47 UTC,Thanks. Unfortunately that log is not helpful because it contains only one boot done in recovery mode with modesetting disabled:
1824588,2019-04-15 19:55:49 UTC,Method used to collect this info:
1824588,2019-04-15 19:47:42 UTC,As requested. Definitely C2D era board (Intel DG43GT) running a Pentium Dual Core.
1824588,2019-04-12 22:14:21 UTC,I found that turning auto-login off resulted in booting to a black screen so after unsuccessfully trying the nomodeset boot option I installed 'lightdm-gtk-greeter' and 'lightdm' from recovery mode which gives me a working system. I had encountered no problems with desktop behavior but this box has Intel GMA X4500 graphics (old-ish I know) so I wonder if it could be related to bug #1727356?
1824588,2019-04-15 03:21:03 UTC,This might also be related to bug 1819943.
1824588,2019-04-15 03:18:19 UTC,Please:
1824588,2019-04-14 07:00:08 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1824588,2019-04-14 06:41:35 UTC,"Slight change in behavior testing a fresh install of 20190413.2 - if installed with auto-login switched on logout did load and give the expected choices of Ubuntu and Ubuntu w/Wayland. But if auto-login is turned off I still get a black screen on reboot. I suspect that gdm3 is not even loading because I've tried blindly opening a tty, logging in as root, and sudo reboot but nothing happens."
1824588,2019-04-12 23:54:21 UTC,This does appear to be hardware related because I encounter no problem on a box with Intel G41 graphics but the X4500 is a no-go with gdm3.
1824588,2019-04-16 03:48:23 UTC,"This was tricky but I finally got a successful boot (following several failed boots) using gdm3 by selecting the kernel with ""e"" from grub and then removing 'quiet splash'. So I hope this is more helpful."
1824600,2019-08-15 23:58:37 UTC,"@Hildo, I think it'd be good to report it.  (To be clear, it /may/ be because we're not on the latest version, but I don't know that for sure.)"
1824600,2019-08-15 22:41:45 UTC,"@Jeff, should I report this to wxWidgets develop team or this is just present because KiCad is not using the most recent version?"
1824600,2019-04-13 00:26:55 UTC,If I remove the second monitor I have this behavior:
1824600,2019-04-13 13:43:27 UTC,"See that Linux Ubuntu still on GTk2 and I already reported more issues that may be related with this library.
There is a plan to upgrade KiCad to GTK3 but, I don't know how quick (and if yes, this report could be postpone to check with GTK3)>"
1824600,2019-04-13 12:54:49 UTC,Most likely this is an incorrect processing of the graphic library that is installed on the system. It would not be bad to make a pro-roll in such lists in order to avoid this kind of graphical problems altogether.
1824600,2019-08-15 22:26:30 UTC,This is a wxWidgets issue.
1824601,2019-04-15 16:12:48 UTC,"No, I am using modern + accelerated."
1824601,2019-05-26 18:22:25 UTC,"I have been using the last Nighties  and never occurred again (different boards and Canvas).
I am marking as fixed."
1824601,2019-05-26 17:57:24 UTC,"@Hildo, does this still happen for you?  (There have been a lot of changes around this area, but nothing specific that I'm aware of.)"
1824601,2019-04-15 15:48:03 UTC,Are you using the Legacy canvas?
1824601,2019-04-14 22:39:35 UTC,"First time that I press Pcbnew escape the place via tool normally. If I press <Enter> the via is placed and the PCbnew works correctly, the problem is just that the via is placed wrong."
1824601,2019-04-15 02:45:44 UTC,"Happened to me many times on different boards with previous KiCad versions.
Not sure how to reproduce other than: work on a board."
1824601,2019-04-14 22:50:35 UTC,Can you send us the board?
1824601,2019-04-14 18:44:25 UTC,What happens if you press ESC a number of times? Does the cursor unfreeze?
1824601,2019-04-15 12:14:05 UTC,"Never happens to me in Nightly version before the reported.
Follow PCB file."
1824603,2019-07-22 07:20:43 UTC,"The --class option lists all the different classes of stressor. When using the --class cpu? option it will list all the stress tests that are cpu stressors, e.g."
1824604,2019-04-15 14:26:44 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1824605,2019-04-15 03:24:38 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1824605,2019-06-14 04:17:28 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1824607,2019-10-08 10:48:19 UTC,"This sounds like a temporary issue with the snap store (there were a couple of issues where the store would struggle for a couple of hours). Does it work now? If you see something like this again, please check https://status.snapcraft.io to confirm it's not an issue with the store."
1824607,2019-12-08 04:17:24 UTC,[Expired for Snappy because there has been no activity for 60 days.]
1824609,2019-04-13 21:43:15 UTC,"Your bugreport file says ""KeyboardInterrupt"" - did you press Ctrl-C while aa-status was running?"
1824609,2019-06-13 04:17:20 UTC,[Expired for AppArmor because there has been no activity for 60 days.]
1824611,2019-09-16 17:31:41 UTC,Migrated to https://github.com/widelands/widelands/issues/2130
1824612,2019-04-13 09:11:26 UTC,It looks that this is a more generic problem. It also happens multiple-times during setup-openstack.
1824612,2019-04-13 07:43:14 UTC,Looks that I found the problem.
1824612,2019-04-13 08:32:28 UTC,"Yes: Copied over manually the files from the controller0 repo-container to the others, and re-run the setup-infrastructure: the problem vanished."
1824614,2019-04-30 19:13:51 UTC,"I've set the milestone to match the one in the related bug report linked by @Rene, so they can be considered together."
1824614,2019-05-31 17:25:23 UTC,If done right then the chamfered pad can even generate triangle pads with a right angle as requested in for example https://bugs.launchpad.net/kicad/+bug/1778622
1824614,2019-05-31 18:12:06 UTC,Hi Rene-
1824614,2019-05-31 18:50:21 UTC,"IPC only talks about simple pad shapes (based on simple rectangles). Chamfers are used where one can not achieve the necessary clearance otherwise (corner pads of some qfn packages are an example)
I would however assume that the same reasons for using rounded corners on normal corners apply also for ones on chamfered ones. (Easier paste release and better solder flow)
It also looks strange otherwise. But you are right it is not written in stone that it is needed."
1824615,2019-04-22 18:22:40 UTC,"Thanks, please keep us posted."
1824615,2019-06-24 04:17:22 UTC,[Expired for samba (Ubuntu) because there has been no activity for 60 days.]
1824615,2019-04-24 16:27:13 UTC,"That's ok, thanks for the update. Bugs are like that sometimes."
1824615,2019-04-24 14:18:33 UTC,"So far, no more lockups. (And I'm almost sorry to say that, as I realize that it's not much we have here in this bug report - and it seems to only affect me...)"
1824615,2019-04-15 11:42:22 UTC,"Done so. (FYI: upgrade came from 2.5, IIRC) 2:4.7.6+dfsg~ubuntu-0ubuntu2.7 installed now. I'll report what happens - if anything."
1824615,2019-04-13 08:45:05 UTC,apport information
1824615,2019-04-13 08:45:11 UTC,apport information
1824615,2019-04-13 08:45:07 UTC,apport information
1824615,2019-04-15 11:03:17 UTC,Thanks for reporting this issue. Could you try downgrading your packages to version 2:4.7.6+dfsg~ubuntu-0ubuntu2.7 ?
1824615,2019-04-13 08:45:09 UTC,apport information
1824615,2019-04-13 08:45:08 UTC,apport information
1824616,2019-04-13 08:32:30 UTC,s/install/git clone/
1824618,2019-04-13 12:47:32 UTC,"I do not see the pictures, which paramters are superfluous after all. I did not cause difficulties. It is another matter of default to select the most frequently changed parameter, for example, the diameter of the hole. If a selection of objects of a particular character is entered, then even you will not need to be selected by default."
1824618,2019-04-13 13:03:49 UTC,Anton you might not have understood what the purpose of this request is.
1824621,2020-07-19 02:10:48 UTC,"I am surprised this was triaged with ""Wishlist"" importance."
1824621,2020-07-19 09:03:59 UTC,https://gitlab.com/kicad/code/kicad/-/issues/2385
1824622,2019-05-18 09:51:19 UTC,Fix applied to qemu 4.1
1824622,2019-04-21 07:12:02 UTC,There is a Patch available which fixes this bug: https://lists.nongnu.org/archive/html/qemu-devel/2019-04/msg03497.html
1824622,2019-04-13 12:45:08 UTC,https://lists.nongnu.org/archive/html/qemu-discuss/2019-04/msg00026.html
1824624,2019-06-17 18:13:51 UTC,Should be fixed by https://github.com/mixxxdj/mixxx/pull/2176.
1824625,2019-07-22 18:54:42 UTC,The Smalltalk sketches examples need to be updated too!!
1824626,2019-04-19 17:23:12 UTC,@Seth didn't you fix this already?
1824627,2019-04-16 15:32:02 UTC,"@Aleksandr, does this still happen with today's nightly?"
1824627,2019-04-16 15:41:32 UTC,Yes
1824628,2019-04-13 14:30:19 UTC,"Fixed in revision 9ea7fe5338ac57a9ca90b563ca16c4b58452b2da
https://git.launchpad.net/kicad/patch/?id=9ea7fe5338ac57a9ca90b563ca16c4b58452b2da"
1824633,2019-06-10 21:27:11 UTC,"Minor point related to this. On windows 8 and 10 if you open pcbnew and then close it without creating a project, you get the footprint cache write error on close. This doesn't happen if you create a project in and save it in a (writeable) location."
1824633,2019-04-29 20:28:50 UTC,"@Wayne, I think that would be fine.  It wouldn't travel with the project if you moved it, but that's no big deal as it will just get auto-regenerated."
1824633,2019-04-29 19:57:08 UTC,"@Jeff, is there any downside other than loading speed in saving the fp-info-cache file to a temporary folder when the user doesn't have write privileges to the current folder?  It would be a bit less intrusive than the error message."
1824633,2019-04-19 12:01:07 UTC,Is there anything to fix here? I only get that message when the project/PCB file is in a read only directory (e.g. demo projects) and therefore is desired behaviour.
1824633,2019-04-13 15:46:57 UTC,Isn't this because it writes to a readonly location?
1824633,2019-04-19 12:26:11 UTC,"I also get that when I start pcbnew directly, without opening a project."
1824639,2019-04-13 16:53:45 UTC,"After some time I got this...
2019-04-13T12:50:49 ERROR Object of type ""op"" with parent """" arrived from client
2019-04-13T12:50:59 INFO Client hung up unexpectedly."
1824639,2019-04-21 21:21:45 UTC,"I've altered the logic for the entities quite a bit, and this is a consequence of that. Basically all characters have metabolism, which means that unless they eat they slowly starve to death.
When they are killed, they are automatically removed from the world.
This is unless they have a ""respawn"" property, as they have in the Braga world."
1824640,2019-06-29 06:04:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824641,2019-05-18 16:53:47 UTC,"Another update to 4.4.0-148, still the same, screen still blank after booting,"
1824641,2019-07-11 18:00:11 UTC,"Another update to 4.4.0-154, still the same, screen still blank after booting, 143 still works."
1824641,2019-06-22 17:56:12 UTC,"Another update to 4.4.0-151, still the same, screen still blank after booting, 143 still works."
1824641,2019-06-06 16:18:03 UTC,"Another update to 4.4.0-150, still the same, screen still blank after booting,"
1824641,2019-04-23 18:56:58 UTC,An update with 4.4.0-146 has been installed and there is no fix in it. The screen is still blank.
1824641,2019-09-21 14:56:17 UTC,Update to 4.4.0-164 has cured this bug. I can now boot with this kernel and log in OK.
1824641,2019-04-15 14:52:02 UTC,Attached is Xorg log for the boot of 4.4.0-145
1824641,2019-04-13 17:17:15 UTC,"Please not that Launchpad has automatically assigned this bug to mutter, but mutter is not installed on the notebook in question, so I have added linux"
1824641,2019-04-13 17:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824641,2019-04-16 03:10:33 UTC,How about 4.4.0-144? Would it help to narrow down the issue a bit more?
1824641,2019-04-15 14:31:53 UTC,Attached is a syslog for the boot of 4.4.0-145 from start up to shut down in the way described above.
1824641,2019-04-13 17:40:52 UTC,"Sorry I cannot collect log files for the kernel giving the bug.  If I can collect any useful information using the kernel that does work, please let me know"
1824645,2019-04-13 19:22:22 UTC,"This feature already exists (at least if I understand your request correctly.
We called it ""badges"" and they are what identifies the session in the session menu in the top panel - in case the user has multiple sessions available, just create a pull request adding your logo here:
https://git.launchpad.net/lightdm-gtk-greeter/tree/data/badges"
1824645,2019-04-14 01:18:00 UTC,"Watermark, while not essential, is nice to have, vendors will appreciate their brand being put there and users will be able to change it to their own preference, or just not show it at all. The value is in visibility, that's something that cannot be achieved with wallpapers considering the resizing and cutting off parts of it to retain the aspect ratio."
1824645,2019-04-14 07:39:47 UTC,"Yes I meant a watermark and what as hellcp already said, it is a nice customization option for distributions / vendors using for example the Xfce desktop to add their own logo to the welcome screen. Vendors providing devices with Linux preinstalled could potentially also add their own flair to it."
1824646,2020-02-03 21:30:45 UTC,"Change abandoned by Shannon Mitchell (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/705555
Reason: Submitting a separate bug just for the public/private url fix."
1824646,2019-04-15 09:38:26 UTC,BTW: the same problem occurs when using openstack ansible 18.1.6.
1824646,2019-07-26 10:55:29 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/672948"
1824646,2019-08-23 20:58:21 UTC,"Reviewed:  https://review.opendev.org/672948
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=288634ce0bf042bed614b3f764753d7b65a7170f
Submitter: Zuul
Branch:    master"
1824646,2019-10-16 10:24:49 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/688895"
1824646,2019-10-16 22:01:28 UTC,"Reviewed:  https://review.opendev.org/688895
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=eccb5c13fec9d9efcccb821dbcf0f344cd515eec
Submitter: Zuul
Branch:    stable/stein"
1824646,2020-02-03 20:58:53 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705555"
1824646,2019-04-14 13:02:02 UTC,"As a workaround, in the heat lxc container in the config file /etc/heat/heat.cfg in the section"
1824647,2019-04-15 11:42:23 UTC,"Thank you for your bug report. Could youa dd your journalctl log after getting the issue?
Could you also open the settings -> sound -> application tab and see if there is a slider added there when the sound is heard?"
1824647,2019-06-15 04:17:28 UTC,[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]
1824648,2019-04-13 19:30:07 UTC,This change was made by a bot.
1824648,2019-07-09 13:42:57 UTC,Do you still have this issue on latest 18.04 kernel?
1824648,2019-07-14 19:07:08 UTC,"Yes, I still have this issue even if I had upgraded my host to latest debian buster. This issue maybe related to seabios +　i440fx, I can get normal dispaly with seabios + q35."
1824648,2019-08-22 05:34:01 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc5/"
1824648,2019-08-22 15:31:19 UTC,I still have this issue on kernel 5.3-rc5.
1824648,2019-08-22 15:40:05 UTC,I also get black screen if a try to reboot multiple times with seabios + q35
1824648,2019-11-14 05:15:48 UTC,Does this issue still happen on an up-to-date kernel?
1824651,2019-04-24 11:52:43 UTC,"I tried to branch the code to add the osmdroid library (https://github.com/osmdroid/osmdroid), I use this library in a app I code and maintain."
1824651,2019-04-24 12:26:36 UTC,Thank you igor for your try. It seems a good library and we will surely try it.
1824651,2019-11-13 07:46:20 UTC,Moved:
1824651,2020-06-23 08:06:45 UTC,@igor-cali this can be considered resolved:
1824653,2019-06-16 18:25:57 UTC,"Hi,"
1824655,2020-11-06 06:23:34 UTC,"Just wanted to verify, if we are going to use QTime or QTimer?"
1824655,2019-04-14 07:08:27 UTC,"Such a widget should be quite easy to implement. We need a new ControlObject that is counting the air time and a copy of https://github.com/mixxxdj/mixxx/blob/master/src/widget/wtime.cpp
To show the time.
Later it can be enhanced by all sort of visible goodies.
Do you have interest to dive into this work?"
1824655,2019-04-14 09:40:32 UTC,Unfortunately I can't. I have never programmed.
1824655,2019-04-29 04:15:53 UTC,"On some skins there is a timer for ""Record Mix"". This could be copied for ""Broadcasting""."
1824656,2019-04-14 20:37:54 UTC,"IMO it is perfectly fine. You can see there are more arrows on top one another, and when clicking the bunch a ""Clarify"" window comes up (check my video). What would be the required behavior for you?"
1824656,2019-04-14 21:25:18 UTC,"On my screenshot, one arrow from the pile is selected. Through only small part of it is visible.
Compare that to a fallback mode attached here."
1824656,2019-04-14 21:27:05 UTC,"On the video, you don't actually select any of the markers."
1824656,2019-04-15 17:17:35 UTC,"I think, you want the arrow to be slightly transparent, so color differences might bbe seen between a single arrow and two (or even more) overlapping arrows.  Although it looks better at Legacy canves, for me it seems absolutely irrelevant, so I consider it as a wish only."
1824656,2019-04-15 17:45:31 UTC,"Althrough it would be nice to distinguish contours of arrows in Accelerated mode, it is not a problem. The problem is that a selected arrow cannot be seen at all behind other arrows. If a selected arrow is in the middle of the pile, it is not visible at all! Look at the attached screenshot. There is an arrow selected. Can you spot it?"
1824656,2019-04-16 21:18:15 UTC,"I agree there is a draw order issue here, the highlighted object is supposed to be pulled to the front."
1824656,2019-04-16 21:32:59 UTC,Maybe the same issue as https://bugs.launchpad.net/kicad/+bug/1825036
1824656,2019-08-03 23:23:06 UTC,"Fixed in revision c438686deb0b25f3b1014e205b0936694c9d1a35
https://git.launchpad.net/kicad/patch/?id=c438686deb0b25f3b1014e205b0936694c9d1a35"
1824657,2019-06-14 04:17:29 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1824657,2019-07-18 17:49:13 UTC,I also have problems with the GNOME desktop randomly crashing after upgrading to Ubuntu 19.04. Here is an output of /var/crash:
1824657,2019-04-15 03:28:15 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1824657,2019-04-13 21:35:23 UTC,"I put the logs also on pastebin, maybe they are more readable."
1824659,2019-04-14 11:33:11 UTC,This appears to be a duplicate of
1824659,2019-04-15 19:51:41 UTC,"You got quite a bit of information in response to your issue, but"
1824659,2019-04-16 00:24:20 UTC,"Sorry, didn't read the last sentence."
1824659,2019-04-16 15:22:20 UTC,"> No, ""scanimage -L"" produces the expected output:
>
> device `hpaio:/net/HP_LaserJet_100_colorMFP_M175nw?ip=192.168.1.2'
> is a Hewlett-Packard HP_LaserJet_100_colorMFP_M175nw all-in-one
"
1824660,2019-04-15 16:02:52 UTC,"Sorry about that! This project isn't actively maintained anymore, but I'm happy to review and merge a pull-request on Github, and if you are interesting in maintaining it let me know!"
1824661,2019-04-15 03:33:31 UTC,Please:
1824661,2019-04-15 12:40:42 UTC,"Daniel,"
1824661,2019-04-16 02:35:33 UTC,"Thanks. That log shows you are using lightdm and 'slick-greeter', so not regular Ubuntu."
1824661,2019-04-16 14:17:41 UTC,"I downloaded the latest Ubuntu daily last evening (20190413) and installed it. I was unable to use nomodeset to get to tty. I tried numerous times to no avail. This morning I booted to recovery mode and used the root terminal to run updates. A new kernel version was installed so I thought why not reboot and see if it made any difference. To my surprise, the system booted and was running normally with the 418 Nvidia driver active. I was able to use prime-select to switch to Intel and it works as well. I have no idea why it is working now but am happy to provide any additional logs if you want to investigate further."
1824661,2019-05-15 16:55:30 UTC,This issue was apparently resolved with the release of 19.04 as I have not encountered it since then. This report should be closed.
1824662,2019-04-13 23:30:04 UTC,This change was made by a bot.
1824668,2019-04-14 18:42:01 UTC,"The specification for new Python API in V6 includes export/import support - so it will happen, sooner or later..."
1824668,2019-05-04 13:57:28 UTC,"Fixed in revision 3e4913adce86ea3955b7dac39703425d9cb2c41e
https://git.launchpad.net/kicad/patch/?id=3e4913adce86ea3955b7dac39703425d9cb2c41e"
1824671,2019-04-15 05:59:41 UTC,"Thank you for your bug report, did you send the report?"
1824671,2019-06-15 04:17:18 UTC,[Expired for spice-vdagent (Ubuntu) because there has been no activity for 60 days.]
1824676,2019-04-17 13:55:19 UTC,PPA-purge certbot/certbot and removing unity tweak tool
1824676,2020-01-23 17:19:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824676,2019-04-17 13:57:03 UTC,helps resolve this issue
1824678,2019-04-15 13:16:07 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1824679,2019-04-15 13:13:04 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1824680,2019-06-19 04:17:22 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1824680,2019-04-19 18:46:36 UTC,I did that. The new report is Bug #1825564
1824680,2019-04-18 14:06:36 UTC,According to VarLogDistupgradeAptlog.txt You have installed vlc from ppa. Could you uninstall it with ppa-purge?
1824680,2019-04-18 11:47:47 UTC,"Thanks for looking into this issue, Brian."
1824680,2019-04-15 15:16:06 UTC,Please try installing the ubuntu-desktop metapackage and then upgrading.
1824680,2019-04-18 14:30:45 UTC,"On Thu, Apr 18, 2019 at 11:47:47AM -0000, flrtx wrote:

> Thanks for looking into this issue, Brian.
>
> I installed ubuntu-desktop and retried upgrading to 16.04. It didn't
> work. The error message is the same. Any other ideas?
"
1824681,2020-03-22 16:05:36 UTC,"@cairn overturf
What is your Ubuntu MATE version?"
1824681,2020-09-11 04:17:16 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1824682,2019-04-14 22:29:19 UTC,This sounds reasonable.
1824682,2019-11-27 19:34:50 UTC,https://github.com/mixxxdj/mixxx/pull/2373
1824685,2019-06-15 04:17:37 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1824685,2019-04-15 15:23:52 UTC,"Does ""a problem occured"" refer to a dialog box that you saw? Could you provide a screenshot of it?"
1824685,2019-04-15 18:34:43 UTC,"Hi Brian,"
1824687,2019-05-03 12:41:50 UTC,"From the upstream discussion thread it looks like I was on the right track (https://marc.info/?l=linux-netdev&m=155688404826002&w=2). For confirmation I am building another set of test kernel packages and once this can be confirmed will proceed to SRU this into the other series. This looks to have remained unnoticed so far, so anything after 4.18 and all the older kernels which have backported those changes would be affected."
1824687,2019-05-03 12:50:25 UTC,"Ok, http://people.canonical.com/~smb/lp1824687/ has been updated with a v2 set which has the upstream patch backported."
1824687,2019-05-03 12:58:15 UTC,"Thank you! I can test this on Monday, weekend is starting here in 2 minutes and this is not the greatest moment to start testing. :)"
1824687,2019-05-07 05:47:13 UTC,"Just a reminder for the test kernel. If this can be tested soon, it could make it into the next update cycle which starts next week. But for that it has to be submitted before end of Wednesday."
1824687,2019-05-15 09:49:58 UTC,"Sorry for the delay. I'm back in the office now and deploying the test kernel today to a few servers, and to additional ones tomorrow if it's OK on the first ones."
1824687,2019-05-17 07:45:07 UTC,"Unfortunately 4.4.0-144-generic #170+lp1824687v2 testing kernel still crashes. I have 4 hardware instances running it now, there were 2 panics (Australia, Sweden) within 24 hours. I installed linux-crashdump on them after the first crash to get the panic logs reliably. Attached a log from the second panic."
1824687,2019-05-17 09:40:45 UTC,"Thanks, quickly glancing at this it looks to be different as in crashing now at a different occasion (when releasing a buffer). I will have to take a closer look but probably not today."
1824687,2019-05-21 09:41:50 UTC,"Spend a little more time on this yesterday. While it is somewhat clear that this results from fixing the original issue (now it crashes when releasing memory a little later), My past experience of looking at network issues like that is that memory dumps are of rather limited use as the reasons lie in the past and by the time crashes happen all the interesting state is already lost.
On the other hand I also would rather avoid making experiments in production environments (if that can be avoided). But I am not sure how much chance there is for that."
1824687,2019-05-03 12:31:25 UTC,There is the kernel.org bug ticket which describes similar oopsing through ip6_expire_frag_queue() in 4.9 and 4.19 kernels: https://bugzilla.kernel.org/show_bug.cgi?id=202669
1824687,2019-05-28 07:24:11 UTC,"So far I have not been successful to trigger the code path which leads to the crashes on my test system. I have, however been able to extend the patch I had in v2 in a way that makes me a bit more hopeful that it might get us somewhere. Potentially not the most optimized handling but that could wait. The problem is a bit that all the changes come from a set of changes where I am not sure upstream really tested the intermediate steps too well. Anyhow, you would find the new debs again at http://people.canonical.com/~smb/lp1824687/
I know it sucks, but I would appreciate if we could put that again into production stress."
1824687,2019-05-31 11:53:06 UTC,"Thanks, I deployed the v4 debs on one server which was particularly unstable, and it's still up after 1 day and 8 hours now. I'll deploy more widely on Monday and Tuesday."
1824687,2019-06-05 07:50:09 UTC,"I've now got the v4 debs on 5 servers, and not a single crash since they were installed on each. Looks good to me. Thank you!"
1824687,2019-06-11 07:14:13 UTC,I reverted the changes to Cosmic because that needs at least a different approach. In that version the rbtree usage is not yet present and the IPv4 expire function does the exactly same thing (increment the refcount of the skb) and we have no hard evidence this actually causes crashes in the 4.18 kernel. So for now only keep the xenial change.
1824687,2019-06-18 16:04:12 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1824687,2019-06-19 19:14:31 UTC,"I tested with Kernel:
Linux tor3 4.4.0-149-generic #175+lp1824687v4 SMP Mon May 27 17:21:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
1824687,2019-06-19 19:15:22 UTC,Verfied fix by reporter
1824687,2019-06-20 07:35:17 UTC,"I deployed the actual -proposed kernel 4.4.0-152.179 on 4 servers, and it is stable for us. Previously there were multiple crashes per day. Confirming, verification done. Thank you!"
1824687,2019-07-24 20:29:02 UTC,This bug was fixed in the package linux - 4.4.0-157.185
1824687,2019-05-21 18:55:05 UTC,"I've now got 6 crashes within past 24 hours on the #170+lp1824687v2 testing kernel on a *single* server. It's a production environment, so I'll roll back for now. Two latest backtraces:"
1824687,2019-05-03 08:54:00 UTC,"As a status update: thanks for testing. I pity it did not help. So far I was looking through all related changes in that set but could not find anything that immediately stuck out. Thinking more over the crash stacktrace it is a netfilter contrack timer expiring which causes a call into ip6_expire_frag_queue() and that got rewritten in ""ipv6: frags: rewrite ip6_expire_frag_queue()"" to use the first entry in the frag list for sending an ICMP message. And before doing that, it calls skb_get() which does increment the user refcount. That might actually be the issue but it is still done that way in any kernel since v4.18 upstream. Could be that nobody is using those under heavy ipv6 traffic, yet. Since I am not that familiar with the network stack, I would like to reach out to upstream with that question."
1824687,2019-04-15 20:24:52 UTC,added logs of apport-collect 1824687
1824687,2019-04-30 20:42:24 UTC,"Thanks for the updated Kernel.
Sorry for the late reply. Changes of ipmi where without success."
1824687,2019-04-15 11:08:03 UTC,Which kernel version was used before (and did not show this crash)? Can you reproduce the issue on a non-production server (which would allow to experiment with the HWE (4.15) kernel)?
1824687,2019-04-15 11:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824687,2019-04-15 18:37:03 UTC,apport information
1824687,2019-04-15 18:37:04 UTC,apport information
1824687,2019-04-15 18:37:05 UTC,apport information
1824687,2019-04-15 18:37:06 UTC,apport information
1824687,2019-04-15 18:37:08 UTC,apport information
1824687,2019-04-15 18:37:08 UTC,apport information
1824687,2019-04-15 18:37:09 UTC,apport information
1824687,2019-05-01 18:11:45 UTC,"O.k. tested with the Kernel Provided. It does not improve the situtation.
Machine crashed first time after about 2hours - same error as always.
I rebootet it - took 2-3 hours until next crash."
1824687,2019-04-15 18:37:12 UTC,apport information
1824687,2019-04-15 20:34:12 UTC,regarding #2 I do not know which kernel ran before.
1824687,2019-04-16 08:53:16 UTC,"Knowing which was the last good kernel would be good to minimize the delta of changes. Note that if you are able to interact with the grub loader at boot, you can go back to at least the previous kernel before the reboot.
For the trace it would be good to capture the full message. If the server has IPMI capabilities you could add a console= kernel command-line to have messages observable through SOL."
1824687,2019-04-16 18:48:06 UTC,"I spend the better part of 2h to install java on an old windows to satisfy the IPMI needs.
I was able to start SOL. BUT it is just a black windows displaying nothing.
I give up. on this - sorry I do not know how to produce an better screenshot.
(Yes I googled). IPMI Viewer produced the same bad results."
1824687,2019-04-17 07:25:29 UTC,The latter means that you still have 4.4.0-143 around and could select that if you had any way of interfacing with the booting server. So you could go back and confirm the regression happened between 143 and 145.
1824687,2019-04-29 17:20:11 UTC,"I have had this crash, with the ip6_expire_frag_queue stack trace, more than 18 times since 2019-04-16 on more than 10 different servers in 8 different countries.  There have been some more crashes, but from these ones the panic dump managed to go out to a remote syslog server where it's easy to grep. Crash count by kernel version; these are on both trusty and xenial:"
1824687,2019-04-29 17:49:51 UTC,"kernel.org bug ticket, showing similar crashes on 4.9 and 4.19 kernels: https://bugzilla.kernel.org/show_bug.cgi?id=202669"
1824687,2019-04-30 07:36:26 UTC,Thanks for the stack traces. Those help a lot to pinpoint the problem. Will be taking a look.
1824687,2019-04-30 12:41:41 UTC,"The issue is a check which is causing a oops/crash when a send buffer is referenced more than once when calling pskb_expand_head(). As mentioned in comment #18, this seems to be introduced by a series of patches modifying the way fragments are handled."
1824687,2019-04-15 18:37:10 UTC,apport information
1824688,2019-04-16 19:45:26 UTC,re-assigning bug to glibc
1824688,2019-04-16 19:10:52 UTC,Trying on the current fedora 30 livecd they have the same issue
1824688,2019-04-16 17:33:46 UTC,"Assaf's test, attached."
1824688,2019-04-16 17:31:36 UTC,"Further exchange on https://debbugs.gnu.org/35289 suggests this is a libc6 problem, not a coreutils/date one."
1824688,2019-04-15 20:15:49 UTC,Here's the strace output.
1824688,2019-04-15 20:08:33 UTC,Thanks for the testing C de-Avillez.
1824688,2019-04-15 19:54:00 UTC,Assaf Gordon reports that he did not reproduce the problem on Ubuntu Live amd64 dated 2019-04-13 22:28; see:
1824688,2019-04-15 17:52:46 UTC,"I have ran a few tests on 16.04, 18.04, 18.10, and 19.04 (all X86_64):"
1824688,2019-04-15 17:03:03 UTC,I got a reply to my bug report on gnu.org which says:
1824688,2019-04-15 15:40:08 UTC,"Ok, it is now reported upstream:"
1824688,2019-04-15 11:45:28 UTC,"Thank you for your bug report, that sounds like an upstream issue and probably worth reporting on https://lists.gnu.org/archive/html/bug-coreutils/"
1824690,2019-05-07 10:59:23 UTC,I've uploaded kernel packages containing the fix at https://kernel.ubuntu.com/~cking/lp-1824690 - do you mind testing these to see if they resolve the issue for you?
1824690,2019-05-08 09:22:38 UTC,"Hi Giovanni, would you mind testing the fix as mentioned in comment #24 so that we can see if this addresses the issue for you?"
1824690,2019-05-14 11:14:04 UTC,"Hi Giovanni, do you mind testing the kernels as mentioned in comment #24,"
1824690,2019-05-26 15:05:56 UTC,"Hi Colin,"
1824690,2019-06-03 10:43:45 UTC,"I've applied the patch to the Ubuntu Bionic kernel, please re-test by downloading and installing all the packages in:"
1824690,2019-06-12 08:16:35 UTC,@Giovanni - any progress on testing this?
1824690,2019-06-12 08:33:50 UTC,"Hi @coling-king,"
1824690,2019-06-12 08:42:07 UTC,"Great, thank you!"
1824690,2019-07-03 23:40:34 UTC,"@colin-king,"
1824690,2019-07-25 16:04:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1824690,2019-05-07 10:03:28 UTC,"Ubuntu runs with a default log level of KERN_WARNING (4), so KERN_NOTICE (5) should be silently ignored."
1824690,2019-07-25 16:21:50 UTC,"@Giovanni it will be fixed for Bionic, Disco, Eoan etc."
1824690,2019-07-25 16:39:10 UTC,@colin-king Ok thanks. Do I still have to change the tag to verification-done-disco?
1824690,2019-07-25 18:32:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1824690,2019-08-07 08:34:23 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1824690,2019-08-09 17:00:51 UTC,"Hi Giovanni,"
1824690,2019-08-13 08:59:53 UTC,This bug was fixed in the package linux - 5.0.0-25.26
1824690,2019-08-13 11:27:47 UTC,This bug was fixed in the package linux - 4.15.0-58.64
1824690,2019-07-25 05:17:48 UTC,Will the fix be added to kernels 4.18 and onwards?
1824690,2019-08-19 07:42:05 UTC,I am now running kernel 5.0.0-26-generic and the error is gone. Thank you for everything.
1824690,2019-04-23 18:52:03 UTC,Thanks Srinivas for the update. If you can let us know when the patch has landed I can add this into the older kernels as part of a SRU procedure.
1824690,2019-04-23 18:39:54 UTC,"This is not related to thermald and thermald  may not fix this.
Rui is submitting a kernel patch to downgrade message level."
1824690,2019-04-15 04:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824690,2019-04-15 11:36:37 UTC,apport information
1824690,2019-04-15 11:36:38 UTC,apport information
1824690,2019-04-15 11:36:40 UTC,apport information
1824690,2019-04-15 11:36:41 UTC,apport information
1824690,2019-04-15 11:36:43 UTC,apport information
1824690,2019-04-15 11:36:46 UTC,apport information
1824690,2019-04-15 11:36:50 UTC,apport information
1824690,2019-04-15 11:36:51 UTC,apport information
1824690,2019-04-15 11:36:48 UTC,apport information
1824690,2019-04-15 11:36:55 UTC,apport information
1824690,2019-04-15 11:36:58 UTC,apport information
1824690,2019-04-15 11:37:00 UTC,apport information
1824690,2019-04-15 11:37:01 UTC,apport information
1824690,2019-04-23 07:43:44 UTC,Any idea how to solve this?
1824690,2019-04-23 08:00:01 UTC,This would require a kernel fix to disable this kernel message.
1824690,2019-04-23 08:18:54 UTC,"If I disable thermald, could it harm my laptop. Is there a chance of overheating?"
1824690,2019-04-23 08:33:39 UTC,"When a laptop reaches a CPU specific temperature threshold it will cause rapid and immediate shutdown to avoid physically damaging the machine.  Older laptops sometimes have issues because the cooling paths are not 100% effective and can lead to overheating, so you may be OK with disabling thermald if you laptop has good thermal dissipation."
1824690,2019-04-15 11:36:53 UTC,apport information
1824690,2019-05-06 19:25:02 UTC,"Rui submitted a patch to change to dev_notice()
https://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git/commit
/?h=next&id=3c7110fab805766450c5d2eac1c994d4c8c230d3"
1824694,2019-04-14 15:06:48 UTC,"The type on Windows is completely revised, so it now accepts any unicode sequence."
1824694,2019-04-14 16:05:13 UTC,"Sweet :) ...does work with type(u""ö"")"
1824694,2019-04-14 16:11:47 UTC,"Also cheers for fixing special chars like ""@"",""."","":""...work perfectly fine on German keyboards with type() :), so I don't have to rely on paste() anymore :D"
1824695,2019-05-18 19:20:24 UTC,6.0 Eeschema uses the modern toolset which doesn't suffer this problem.
1824695,2019-04-15 02:55:13 UTC,We should be able to have the contextual menu rotate action happen around the click point as opposed to the location of the menu item.
1824695,2019-04-14 20:22:56 UTC,"IMO it is not a bug, only ""simple behavior"". After mirror or rotate you probably will place the block, so if the starting position is ""dumb"" (not the center of old place of block but the actual mouse cursor position) it is not a problem. @Laurent, I think you may file a wish for a more sophisticated behavior."
1824695,2019-04-14 20:43:53 UTC,@Novak : I'm sorry to disagree.
1824699,2019-04-15 05:58:29 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
1824699,2019-04-17 02:25:20 UTC,"I found a solution:
i startet dconf editor and resetted everything in org/gnome/calendar/weather-settings."
1824699,2019-04-17 09:16:11 UTC,can you maybe figure out/try to remember what setting you had which created the issue?
1824699,2019-04-18 16:38:23 UTC,"I have the same issue with gnome-calendar 3.28.2, installed as default in Linux Mint Cinnamon 19.1 (Ubuntu 18.04)"
1824699,2019-04-18 16:48:50 UTC,*preventing me from opening
1824699,2019-04-18 21:25:06 UTC,"@John, can you get a backtrace of the issue (https://wiki.ubuntu.com/Backtrace)?"
1824699,2019-04-19 00:09:51 UTC,"@Sebastien Bacher, I can't install debug symbols. There are no -dbg for gnome-calendar so I added the ppa for -dbgsym but it won't update"
1824699,2019-04-19 03:09:48 UTC,"I tried to add my hometown Dorsten to weather inside calendar again.
When i enter Dorsten (this is in germany), the search does not find or offer my city.  When i press enter, this setting is set.  I checked in dconf editor, there was the default value"
1824699,2019-04-29 09:37:54 UTC,I can confirm this bug. Same problem here with Ubuntu 18.04.2 LTS (Kernel 4.18.0-18-generic #19~18.04.1-Ubuntu SMP). gnome-calendar crashes after entering a city in the calendar weather plugin for the first time:
1824699,2019-05-03 16:25:51 UTC,"Indeed that's an issue with those locations, thanks for the details"
1824699,2019-05-30 14:40:36 UTC,"The issue is fixed with that SRU
https://launchpad.net/ubuntu/+source/geocode-glib/3.25.4.1-4ubuntu0.18.04.1
(and it newer Ubuntu series)"
1824700,2019-04-24 06:47:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824700,2019-08-24 09:18:58 UTC,Thanks for reporting.
1824708,2019-08-28 13:38:13 UTC,"graylog 3 is available in the ""3"" track."
1824709,2020-09-18 03:06:28 UTC,"Here is a pull request branch that implements the domId input for <eg-combobox>.  I also added some label/domId pairs (just some low-hanging fruit, should not be considered comprehensive): user/sandbergja/lp1824709_combobox_id"
1824709,2020-09-21 18:34:51 UTC,"I tested using the MARC Batch Import page.  I used WAVE to determine that ""Apply/Create Form Template"" is the field that is being fixed."
1824709,2020-09-21 21:03:20 UTC,"Sure, thanks for asking, Mike!  Without the patch, the id is on the <eg-combobox>.  With the patch, the id is on the <input> within the <eg-combobox>."
1824709,2020-09-21 22:24:04 UTC,That explanation makes a lot of sense.  I went back to MARC Batch Import and re-tested and I see the id attribute is no longer on the eg-combox tag and got moved to the input.  I also tested these spots:
1824710,2019-06-01 20:56:56 UTC,Im a bug replrting noob. Why is this invalid ?
1824710,2019-06-25 01:49:09 UTC,"It's invalid (closed) for MATE (not really MATE's issue), but not necessarily invalid for Deja Dup."
1824710,2019-06-26 20:23:31 UTC,"Understood. Agreed I dont have enough space. Deja Dup says it will delete
backups as needed, but it turns out this will only happen if 2 full backups
exist. I guess this is a catch 22 which leaves me with no future backups,
ever. In reality off course I just backup manually, but a shame Deja Dup is
rendered useless if you dont have space for 2 full backups."
1824710,2019-08-26 04:17:21 UTC,[Expired for Déjà Dup because there has been no activity for 60 days.]
1824712,2020-03-17 08:01:26 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824712,2020-05-17 04:17:28 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824712,2019-04-14 15:14:13 UTC,Error message requesting again the password on the Ubuntu keychain after it has already been initialized.
1824712,2019-04-14 15:16:10 UTC,Error message crashing the ubuntu softwarer application store.
1824714,2019-04-14 15:30:08 UTC,This change was made by a bot.
1824714,2020-06-09 05:37:48 UTC,Please test 20.04.
1824714,2020-08-09 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824719,2019-04-14 16:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824719,2019-08-01 18:11:38 UTC,"SRU request here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838677"
1824720,2019-04-14 19:18:50 UTC,No.  I won't have time to look at this until after KiCon.  We need a 5.1.2 tag to target things for
1824720,2019-05-06 09:33:44 UTC,"Fixed in revision 2e43c6c64e0bdf7a7c5897db2b7b53d0da31080e
https://git.launchpad.net/kicad/patch/?id=2e43c6c64e0bdf7a7c5897db2b7b53d0da31080e"
1824720,2019-04-14 18:38:30 UTC,"@Seth, I'm getting ready to tag 5.1.2.  Do I need to hold off until this fix is pushed?"
1824720,2019-04-14 17:12:50 UTC,Related to lp:1822772
1824720,2019-04-14 18:47:44 UTC,"On 4/14/19 2:38 PM, Wayne Stambaugh wrote:

> @Seth, I'm getting ready to tag 5.1.2.  Do I need to hold off until this


                                ^^ 5.1.1 ^^

> fix is pushed?
>
"
1824722,2019-04-14 19:30:18 UTC,"I have never seen a condor cluster that require authentification when submitting jobs...
No I have heard recent issue with condor, but I do not have a condor cluster in order to try at the moment"
1824723,2019-04-16 19:00:07 UTC,Confirmed on EG version 3.2.4
1824723,2019-05-23 13:26:59 UTC,I think this bug could be related to the  bug 1804043
1824724,2019-04-24 01:21:38 UTC,"Hello German translators, what's involved in fixing translations and pushing an updated translation package to users? The new strings have broken some AppArmor utilities."
1824724,2020-04-02 21:07:09 UTC,This seems to have been fixed in eoan; disco is EOL. Closing.
1824724,2020-04-02 20:00:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824724,2019-04-24 10:21:14 UTC,"> id appears to be the only one to pick different letters.
"
1824724,2019-04-24 02:06:52 UTC,@Seth: The translators don't deal with the language pack packages directly. What's needed is that a German translator fixes those strings via LP:
1824724,2019-04-24 01:07:05 UTC,It looks like only the German translations broke the hotkeys. All the others in the apparmor-utils.po files I've got on my local Ubuntu mirror are either:
1824724,2019-04-20 18:48:52 UTC,"That's interesting[tm] - in all branches I checked, '(V)iew changes' is not translated to german..."
1824724,2019-04-22 21:29:36 UTC,Here we are:
1824724,2019-04-21 12:53:08 UTC,That makes it even more interesting[tm]
1824724,2019-04-21 08:50:47 UTC,"apparmor  2.12-4ubuntu5.1  amd64  user-space parser utility for AppArmor
apparmor-easyprof  2.12-4ubuntu5.1  all  AppArmor easyprof profiling tool
apparmor-notify  2.12-4ubuntu5.1  all  AppArmor notification system
apparmor-utils  2.12-4ubuntu5.1  amd64  utilities for controlling AppArmor
dh-apparmor  2.12-4ubuntu5.1  all  AppArmor debhelper routines
libapparmor-perl  2.12-4ubuntu5.1  amd64  AppArmor library Perl bindings
libapparmor1:amd64  2.12-4ubuntu5.1  amd64  changehat AppArmor library
python3-apparmor  2.12-4ubuntu5.1  amd64  AppArmor Python3 utility library
python3-libapparmor  2.12-4ubuntu5.1  amd64  AppArmor library Python3 bindings"
1824724,2019-04-20 15:59:42 UTC,"workaround:
LANG=en_US.utf8 LANGUAGE=en_US sudo -s
aa-logprof"
1824724,2019-04-20 11:10:22 UTC,"there is indeed a mistake in the translation, in a test profile with en-us setting aa-logprof works. please check the translated versions. tnx."
1824724,2019-04-23 11:44:44 UTC,"Great[tm]. I downloaded the ""po diff"" file, and it seems someone broke several hotkeys :-("
1824725,2019-04-14 20:43:54 UTC,"I resolved putting a theme in the configuration of the gedit: Preferences ----> Fonts and Colors and I putted the theme ""kate"" ..."
1824738,2019-04-30 15:40:21 UTC,The issue has been fixed upstream in git https://gitlab.gnome.org/GNOME/gvfs/commit/a9362fa
1824738,2019-04-29 12:05:11 UTC,Thanks
1824738,2019-04-26 21:27:17 UTC,"Thanks Sebastien, I've filed it at Gnome's Gitlab and added the bug tracker."
1824738,2019-04-15 11:46:04 UTC,/usr/lib/gvfs/gvfsd-admin --help
1824738,2019-04-15 05:54:07 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1824738,2019-04-14 22:27:08 UTC,"StacktraceTop:
 g_vfs_backend_admin_pre_setup (argc=0x7fff172c488c, argv=0x7fff172c4880) at ../daemon/gvfsbackendadmin.c:953
 main (argc=<optimized out>, argv=<optimized out>) at ../daemon/daemon-main-generic.c:37"
1824738,2019-04-15 20:25:36 UTC,"Right, that seems suboptimal/should be sent upstream on https://gitlab.gnome.org/GNOME/gvfs/issues"
1824739,2019-04-15 03:42:57 UTC,Please:
1824739,2019-06-14 04:17:30 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1824742,2019-08-19 03:55:02 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10268"
1824742,2019-08-22 23:35:32 UTC,"Commit hash: fb54181b701a7f0e09ae460732af790c59ce1a2e
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw"
1824742,2019-08-23 04:30:41 UTC,"Reviewed:  https://reviews.mahara.org/10268
Committed: https://git.mahara.org/mahara/mahara/commit/6af4b39e9bd77a2983388aa79f7671abaed882c8
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1824743,2019-04-15 01:01:48 UTC,"Also, the fonts do look ok at 1.0 scaling, but I can't really read them that small. They appear to be similarly broken on any factor above 1.0."
1824743,2019-04-19 00:44:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824743,2019-04-19 01:02:59 UTC,"Hi the same problem here. After I've installed the gtk3 package and removed both libreoffice-qt5 and libreoffice-kde5 the fonts seem to be OK but all of the icon packages are ugly, pixelated (even the *SVG* icons)"
1824743,2019-05-30 05:40:15 UTC,"Hi, same problem here. Nathan, thank you for posting the workaround!"
1824743,2019-05-30 07:56:33 UTC,"Hi Nathan, thanks for the bug report. This is currently a known issue with non-integer scaling factors in KDE [1]. There's unfortunately no big fix for everyone yet, just small fixes that work for some and not for others. Keep up-to-date with KDE updates and it's likely the issue will eventually go away (as it seems to have for some people [2])."
1824747,2019-04-15 11:34:43 UTC,Thank you for your bug report. The log indicates the issue is
1824747,2019-04-22 22:03:32 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1824747,2019-06-22 04:17:33 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1824749,2019-04-15 07:30:47 UTC,Seems like this is a duplicate of https://bugs.launchpad.net/devstack/+bug/1673825 . Help with getting the proposed patch there into working shape would be appreciated.
1824753,2019-04-23 18:17:20 UTC,"This bug is with all Qt applications. I used VLC to show it. And by the way, it happens with other distros that use GNOME 3.32."
1824753,2019-10-29 10:27:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824753,2019-05-20 04:45:44 UTC,"My knowledge (of language and so on) is very basic, I am using a web translator. It is very difficult for me to advertise on the web <https://bugreports.qt.io>? If someone can or wants to do it I will be very grateful.  I can provide as much information as required.
Thank you, greetings."
1824753,2019-04-26 18:18:11 UTC,Thanks for the video! Can you please file a bug upstream to <https://bugreports.qt.io>?
1824753,2019-04-24 08:56:58 UTC,I don't know if it's the GNOME 3.30 to 3.32 update or the Qt update. I know it happens with other distros because I tried Manjaro Gnome and it also suffers this bug. I left a message in the forums with another video https://forum.manjaro.org/t/gnome-two-monitors-and-qt-problems/83075
1824753,2019-04-23 18:34:12 UTC,"> And by the way, it happens with other distros that use GNOME 3.32.
"
1824753,2019-04-17 02:09:55 UTC,Thanks. The problem continuing is somewhat good news. It means this isn't some new regression in mutter.
1824753,2019-04-22 20:48:17 UTC,This bug talks about Qt applications and only gives vlc as example.
1824753,2019-04-16 08:06:45 UTC,"Thanks. It appears you have not downgraded all the packages, only one of them. Please repeat the steps in comment #2, being sure to download and install all the .deb files."
1824753,2019-04-16 07:54:03 UTC,"patrick@patrick-pc:~$ dpkg -l | grep mutter
ii  gir1.2-mutter-4:amd64                      3.32.0+git20190410-1ubuntu1          amd64        GObject introspection data for Mutter
ii  libmutter-4-0:amd64                        3.32.0+git20190410-1ubuntu1          amd64        window manager library from the Mutter window manager
ii  mutter                                     3.32.0-1                             amd64        lightweight GTK+ window manager
ii  mutter-common                              3.32.0+git20190410-1ubuntu1          all          shared files for the Mutter window manager
patrick@patrick-pc:~$"
1824753,2019-04-16 06:49:37 UTC,"OK, if you have successfully downgraded mutter then it looks like this problem existed before the introduction of xrandr-scaling. So that's good. But just to verify, please run:"
1824753,2019-04-16 05:53:32 UTC,"I've updated Mutter as indicated. The problem is still there but it seems to have improved the resolution.
https://youtu.be/3-wFNodO8Qo"
1824753,2019-04-16 05:41:39 UTC,apport information
1824753,2019-04-16 05:41:38 UTC,apport information
1824753,2019-04-16 05:03:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1824753,2019-04-16 05:09:16 UTC,"Also, please try downgrading to mutter version 3.32.0-1 by downloading *.deb from:"
1824753,2019-04-16 12:00:43 UTC,"Now I do. Before I just updated mutter_3.32.0-1_amd64.deb.
I have updated all deb and the problem continues."
1824755,2019-04-18 22:23:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824756,2019-04-15 05:54:21 UTC,This is what I see from strace (snip):
1824756,2019-04-15 06:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824756,2019-04-15 07:25:54 UTC,I have also ran apt-get remove on rc kernel packages before I have executed update-grub:
1824758,2020-02-09 22:32:16 UTC,"Fixed in 19.10, actually with this change to automatically use fullscreen:
https://phab.lubuntu.me/D19"
1824762,2019-07-03 16:40:58 UTC,"An upload of percona-toolkit to xenial-proposed has been rejected from the upload queue for the following reason: ""No response to questions after two months; clearing out the queue""."
1824762,2019-06-14 21:31:00 UTC,There's a question from Robie on the bug which is why this hasn't been accepted by any of the SRU Team.  Marking incomplete.
1824762,2019-04-15 07:38:24 UTC,"Made some progress on the test suite, but many tests already fail in the relevant upstream branch:"
1824762,2019-04-20 21:28:03 UTC,Uploaded to Xenial.
1824762,2019-04-15 08:21:57 UTC,"The attachment ""lp1824762-percona-toolkit-sprintf-warnings.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1824762,2019-04-15 07:19:32 UTC,Attaching patch for the issue.
1824762,2019-05-01 13:35:34 UTC,"> To that end I submit that it will be difficult to test this patch in a reliable fashion, and would seek feedback on what we should do about that.
"
1824768,2019-06-22 04:17:26 UTC,[Expired for QEMU because there has been no activity for 60 days.]
1824768,2019-04-22 15:18:27 UTC,">> ./qemu-system-i386 -cdrom alpine.iso --accel tcg,thread=multi
"
1824768,2019-04-21 17:58:36 UTC,When you say
1824768,2019-04-16 15:13:17 UTC,"Interesting, maybe that is the reason why it is not restricted to use mttcg from the command line."
1824768,2019-04-16 14:59:40 UTC,"That patch is already in QEMU (commit b32dc3370a666e23). It sounds like we're a bit further forward with this than I thought we might be, but clearly not everything necessary is implemented."
1824768,2019-04-16 14:41:31 UTC,"Yes, I can imagine that."
1824768,2019-04-16 14:17:17 UTC,"Implementing a stronger guest memory model than the host has is tricky -- we would need to emit barrier instructions after each guest load or store, which would slow down straight-line execution speed by quite a lot, perhaps by so much that it would outweigh the gain from being able to run more than one thread at once. (Perhaps some of the armv8 load-acquire/store-release insns would help, but they're no good to you on a v7 CPU.)"
1824768,2019-04-16 14:05:15 UTC,"Thank you for the explanation. I found some patches a few years old, so I thought the implementation is now complete especially when ARM is getting more and more popular."
1824768,2019-04-16 13:44:51 UTC,"This is expected. The warning from QEMU is telling you that MTTCG is not supported for the combination of an Arm host and an x86 guest. It warns that you might see ""strange errors"", and indeed you saw an error. Don't try to use MTTCG here."
1824770,2019-10-16 05:48:30 UTC,"Is there anything that snapd needs to do here? It already generates the caches, does it need to do more? It seems this is a ubiquity task, yes?"
1824777,2019-07-05 12:51:58 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1824777,2019-06-21 15:25:11 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1824777,2019-06-21 13:47:17 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1824777,2019-06-07 19:30:27 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.0.0 release.
1824777,2019-06-04 16:25:23 UTC,"Reviewed:  https://review.opendev.org/662941
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=9934640fc266fa5d64e2aa9a0b6d2edfe2f4a64d
Submitter: Zuul
Branch:    stable/queens"
1824777,2019-06-04 06:47:35 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/662940"
1824777,2019-06-04 16:17:18 UTC,"Reviewed:  https://review.opendev.org/662938
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=517175cce086e0a46d63a185390e44dd088cf659
Submitter: Zuul
Branch:    stable/stein"
1824777,2019-06-04 06:52:53 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/662941"
1824777,2019-06-04 06:44:24 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/662938"
1824777,2019-06-04 04:18:43 UTC,"Reviewed:  https://review.opendev.org/652603
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=9f6caf7724fb6529a838595a5a9d4607d2eebace
Submitter: Zuul
Branch:    master"
1824777,2019-04-15 09:28:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/652603"
1824777,2019-06-04 16:25:12 UTC,"Reviewed:  https://review.opendev.org/662940
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=0663f3feadc71fe26988ee3ab61db7a4fde940de
Submitter: Zuul
Branch:    stable/rocky"
1824780,2019-07-12 10:20:47 UTC,+1
1824780,2019-08-12 09:36:07 UTC,The experience is even worse if one tries to repackage a generic/ubuntu* libvirt box.
1824780,2019-09-26 14:46:38 UTC,+1
1824780,2020-10-28 08:14:43 UTC,Every other distro vendor provides libvirt images except Ubuntu. It makes our CI cry.
1824780,2020-12-11 17:49:56 UTC,"that, and virtualbox is not in good shape out there. it seems like ubuntu is happy to ship the virtualbox versions from Debian unstable, but Debian itself doesn't ship it as part of its stable releases because of serious problems with upstream management of security issues:"
1824783,2019-05-31 09:35:11 UTC,"Reviewed:  https://review.opendev.org/660863
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=877df152ddc6dcf83e5a92964a275de2dfc1444b
Submitter: Zuul
Branch:    stable/stein"
1824783,2019-11-06 01:14:54 UTC,This issue was fixed in the openstack/kolla 9.0.0.0rc1 release candidate.
1824783,2019-06-14 01:15:05 UTC,This issue was fixed in the openstack/kolla 7.0.3 release.
1824783,2019-05-24 22:28:56 UTC,"Reviewed:  https://review.opendev.org/660864
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=63d63ab97c87d4470be1cd72575869c32e1cb9c9
Submitter: Zuul
Branch:    stable/rocky"
1824783,2019-07-18 00:38:19 UTC,This issue was fixed in the openstack/kolla 8.0.0.0rc2 release candidate.
1824783,2019-05-22 11:22:38 UTC,"Reviewed:  https://review.opendev.org/652606
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=285814353af29395932e15d78c6a154796978a21
Submitter: Zuul
Branch:    master"
1824783,2019-04-15 16:11:28 UTC,Could be related to or duplicate of https://bugs.launchpad.net/kolla/+bug/1814172?
1824783,2019-04-15 16:13:14 UTC,"Possibly also this one: https://bugs.launchpad.net/kolla-ansible/+bug/1781232 ?
And this one: https://bugs.launchpad.net/kolla-ansible/+bug/1817928 ?"
1824783,2019-05-23 01:25:48 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/660864"
1824783,2019-04-15 09:40:28 UTC,https://review.openstack.org/652606
1824783,2019-04-16 07:23:23 UTC,@Mark Goddard (mgoddard)
1824785,2019-04-15 12:49:59 UTC,thanks for finding.
1824785,2019-04-24 10:34:30 UTC,"Works fine, thx)"
1824788,2019-04-15 15:46:47 UTC,Where is this link? I double checked the guide and still cannot find it!
1824788,2019-04-15 16:54:32 UTC,"Hmm, from quick look it indeed looks that link to https://docs.openstack.org/install-guide/launch-instance-networks-provider.html may be missing in docs' menu. Maybe that should be checked and fixed."
1824788,2019-04-27 15:33:03 UTC,The document that guides in the creation of the provider network is external to neutron. It's linked from this other document
1824788,2019-04-27 15:35:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656062"
1824788,2019-05-01 02:15:17 UTC,"Reviewed:  https://review.opendev.org/656062
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2b9655a78474a8cbec862c086bece4b074ade696
Submitter: Zuul
Branch:    master"
1824788,2019-04-15 15:19:03 UTC,"Hi @Realtime,"
1824791,2019-06-22 21:15:13 UTC,"The issue still exists, both on FreeBSD and on DragonFly BSD."
1824791,2019-04-15 10:55:14 UTC,Once upon a time we had
1824791,2019-06-24 19:36:21 UTC,Thanks. Applied as -r695
1824794,2019-06-27 04:12:49 UTC,"This issue was caused by the cleanup function, it will try to run SAFE_UNLINK() in the end of the test:
        SAFE_UNLINK(TEST_TMPFILE);
        SAFE_UNLINK(TEST_ELOOP);"
1824794,2019-06-27 04:35:51 UTC,Issue reported upstream: https://github.com/linux-test-project/ltp/issues/540
1824794,2019-06-24 04:52:46 UTC,"This test will need CONFIG_BSD_PROCESS_ACCT=y in the kernel config, which was not enabled in the KVM kernels."
1824795,2019-06-18 12:09:49 UTC,"yeah, we can remove the error message we are comparing in the test. BadRequest should be enough."
1824795,2019-06-19 16:10:03 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666373"
1824795,2019-06-27 12:41:09 UTC,"Reviewed:  https://review.opendev.org/666373
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=b025553642275302216ffa20545461cc4627c3eb
Submitter: Zuul
Branch:    master"
1824795,2019-07-25 14:05:03 UTC,This issue was fixed in the openstack/tempest 21.0.0 release.
1824798,2019-06-22 04:17:27 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1824798,2019-04-22 17:59:20 UTC,Thanks for filing this bug in Ubuntu.
1824799,2019-08-16 08:56:20 UTC,"After some analysis I don't think it is a bug. When new dnsmasq process is going to be spawned, it calls pm.enable() method here: https://github.com/openstack/neutron/blob/master/neutron/agent/linux/dhcp.py#L469"
1824799,2019-04-19 06:55:33 UTC,"Hi Brent, had your devstack-machine(or neutron-dhcp-agent service) been restarted when the debug messages occured ?"
1824800,2019-04-15 12:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824800,2019-06-15 04:17:30 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824802,2019-09-19 10:14:02 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1824802,2019-07-04 10:24:31 UTC,This issue was fixed in the openstack/neutron 12.1.0 release.
1824802,2019-07-01 02:49:16 UTC,This issue was fixed in the openstack/neutron 14.0.2 release.
1824802,2019-07-01 02:47:41 UTC,This issue was fixed in the openstack/neutron 13.0.4 release.
1824802,2019-05-24 05:38:45 UTC,"Reviewed:  https://review.opendev.org/661011
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=946faaf361003a0a67081be28565d3815c354510
Submitter: Zuul
Branch:    stable/rocky"
1824802,2019-05-24 03:42:47 UTC,"Reviewed:  https://review.opendev.org/661010
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=89e9c45e866190eb5526c51d14c234da7e2ec041
Submitter: Zuul
Branch:    stable/stein"
1824802,2019-05-23 14:25:41 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/661012"
1824802,2019-05-23 14:25:28 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/661011"
1824802,2019-05-23 14:25:14 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661010"
1824802,2019-05-21 12:20:18 UTC,"Reviewed:  https://review.opendev.org/658307
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5c433a027daab2419d974820589205253871885e
Submitter: Zuul
Branch:    master"
1824802,2019-05-10 08:50:45 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658307"
1824802,2019-04-23 13:22:18 UTC,Please also see comment https://bugs.launchpad.net/neutron/+bug/1760047/comments/24 - it may be that patch https://review.openstack.org/626830 is triggering this issue now more often.
1824802,2019-04-17 10:45:07 UTC,I was today investigating logs from http://logs.openstack.org/97/631497/7/check/tripleo-ci-centos-7-scenario007-standalone/42068d9/logs/undercloud/var/log/containers/neutron/dhcp-agent.log.txt.gz#_2019-04-10_14_18_36_934 once again.
1824802,2019-05-24 02:44:57 UTC,"Reviewed:  https://review.opendev.org/661012
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=55055172958bd278020d08cd80d7f7641a3f7520
Submitter: Zuul
Branch:    stable/queens"
1824803,2020-01-06 12:39:22 UTC,was fixed here https://review.opendev.org/#/c/682785/
1824803,2020-05-03 12:13:21 UTC,"Hi, the change https://review.opendev.org/#/c/682785/ broke designate actions at all:"
1824803,2020-05-03 12:25:21 UTC,"I want to suggest to replace old vocabulary like ""domain"" and ""records"" to new ""zone"" and ""recordset"":"
1824807,2019-05-14 09:19:00 UTC,"Please, use use_ipv6=true in nova.conf file."
1824807,2019-05-14 07:42:54 UTC,"Hello, is there any updates? is that possible to prepare the fix there ?"
1824807,2019-04-17 15:28:59 UTC,"As I understand customer use neutron and this feature works in neutron too. From my point of view, this rathe mistake in the documentation or description than a bug in the code. What exactly issues did the customer spotted when using this feature?"
1824807,2019-04-17 14:58:17 UTC,"In the OpenStack documentation this option is stated to be related to nova-network, which is not being used in the environment. Because of this, the customer wants to bypass its usage. If this backport is unreasonable, is it safe to use this option, and are there any relations/impacts/mismatches for this config option with neutron related services?"
1824807,2019-04-17 14:29:05 UTC,"I have tested this behavior in my environment, and confirm that network_data.json contains IP address for ipv6 only when use_ipv6=true option enabled. According to the code comments, this feature does what it has to do: "":param use_ipv6: If False, do not return IPv6 template information even if an IPv6 subnet is present in network_info."""
1824807,2019-04-18 08:39:20 UTC,The customer has been concerned about its usage with neutron and possible side effects. Because of this concerns they requested a feature backport as a way to bypass the usage of the option.
1824810,2019-04-15 13:42:29 UTC,"On s390x it only uses sysinfo for systemd-detect-virt,
  src/basic/virt.c:306:        r = get_proc_field(""/proc/sysinfo"", ""VM00 Control Program"",
  WHITESPACE, &t);"
1824810,2019-04-15 13:43:38 UTC,Ack. Also DPM mode has LPAR UUID we should be using.
1824810,2019-04-15 14:13:16 UTC,https://github.com/systemd/systemd/pull/12321
1824810,2019-04-15 14:19:25 UTC,https://www.redhat.com/archives/libvir-list/2019-April/msg00987.html
1824812,2019-04-15 22:48:12 UTC,"Okay, I have a fix for the shiftfs side I think. Attached here."
1824812,2019-04-15 22:53:48 UTC,I was able to narrow down this apparmor_parser error to shiftfs:
1824812,2019-04-16 00:22:49 UTC,"The attachment ""UBUNTU: SAUCE: shiftfs: use correct llseek method for"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1824812,2019-04-16 09:15:40 UTC,This bug was fixed in the package apparmor - 2.13.2-9ubuntu6
1824812,2019-05-07 13:50:14 UTC,Ordering was important:
1824812,2019-05-06 09:07:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1824812,2019-05-07 12:21:15 UTC,"I have not seen/triggered the kernel issue mentioned in here (identified by jdstrand).
But on request I'll try it at least."
1824812,2019-04-15 21:18:25 UTC,Uploaded 2.13.2-9ubuntu6 with the SFS_MOUNTPOINT change.
1824812,2019-05-14 19:06:48 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1824812,2019-12-17 19:58:46 UTC,This was fixed upstream in 61c27d8808f0589beb6a319cc04073e8bb32d860
1824812,2019-04-26 15:35:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1824812,2019-04-15 21:09:26 UTC,I noticed that confinement inside of LXD containers works fine when shiftfs is disabled:
1824812,2019-04-15 23:32:56 UTC,"When running a test kernel with Christian's patch, the dir-seek test case passes:"
1824812,2019-04-15 20:31:11 UTC,The following will reproduce the issue in a disco VM with disco LXD container:
1824812,2019-04-15 21:04:45 UTC,"Since the apparmor SFS_MOUNTPOINT change is small, I'll prepare an upload for that immediately. We may need another parser update for the other issue."
1824812,2019-04-15 14:04:15 UTC,"In my disco container they really start without apparmor isolation nowadays.
After startign a guest with uvtool I checked what was auto-labelled."
1824812,2019-04-15 14:06:34 UTC,"I had this kind of errors a few times in the past, need to check some conditions in this case ..."
1824812,2019-04-15 14:10:33 UTC,Pure parsing works (was broken int he past)
1824812,2019-04-15 14:20:19 UTC,"Apparmor is disabled in LXD containers now !?!
Compare aa-status after spawning a new container."
1824812,2019-04-15 14:36:51 UTC,"In that container that has no profiles at all I can explicitly load them.
 $ sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd
 $ systemctl restart libvirtd"
1824812,2019-04-15 14:34:15 UTC,"Since I started seeing this in libvirt There might be reasons that is done that way but this affects me and probably other use cases e.g. if I install libvirt:
  $ apt install libvirt-daemon-system
  $ aa-status | grep libvirt"
1824812,2019-04-15 14:56:45 UTC,Adding set -x and calling this directly:
1824812,2019-04-15 15:00:34 UTC,"Yep, adding
 Environment=SFS_MOUNTPOINT=/sys/kernel/security/apparmor/
to
 /lib/systemd/system/apparmor.service
Fixes the bug."
1824812,2019-04-15 15:05:26 UTC,"Perhaps because of bug 1823379, which broke some code's dynamic detection of apparmor being enabled via /sys/module/apparmor/parameters/enabled?"
1824812,2019-04-15 15:08:48 UTC,"Sorry, no. Ignore comment #10"
1824812,2019-04-15 15:47:37 UTC,"This is due to a bug in upstream parser/rc.apparmor.functions because SFS_MOUNTPOINT is only set after is_apparmor_loaded() is called, but is_container_with_internal_policy() doesn't call it. /lib/apparmor/apparmor.systemd calls is_container_with_internal_policy() prior to apparmor_start() and it is only through apparmor_start() that is_apparmor_loaded() is called."
1824812,2019-04-15 19:51:10 UTC,There are two bugs that are causing trouble for apparmor policy in LXD containers:
1824812,2019-04-15 14:48:49 UTC,"In Cosmic /lib/systemd/system/apparmor.service pointed to ""/etc/init.d/apparmor start""
This had some code, but it was not triggered:
                if [ -x /usr/bin/systemd-detect-virt ] && \
                   systemd-detect-virt --quiet --container && \
                   ! is_container_with_internal_policy; then
                        log_daemon_msg ""Not starting AppArmor in container""
                        log_end_msg 0
                        exit 0"
1824814,2019-05-16 00:48:33 UTC,"Mark this as duplicate to #1829260 , since it should be same root cause , the config uuid (reboot) is not right.the fix of #1829260 was just merged. so  if you reproduce this issue from today , please re-open it."
1824814,2019-06-17 19:31:28 UTC,"Verified in load ""2019-06-13"
1824814,2019-05-23 23:11:43 UTC,"Duplicate bug https://bugs.launchpad.net/starlingx/+bug/1829260 has been addressed by review: https://review.opendev.org/#/c/658391/
The fix merged in stx master on May 15"
1824814,2019-05-14 13:08:35 UTC,Thanks. from the controller-0 sysinv log. this is similar with https://bugs.launchpad.net/starlingx/+bug/1828271
1824814,2019-04-17 17:57:28 UTC,Marking as release gating given the issue is reproducible. Needs further investigation.
1824814,2019-05-13 19:12:24 UTC,I have attached logs that was captured from original issue.
1824814,2019-05-05 01:16:52 UTC,"when you meet this issue, could you run collect command and share the tar ball ?"
1824814,2019-04-29 13:26:13 UTC,"Please let me know which logs needed .
thanks
Anujeyan"
1824814,2019-04-18 08:04:41 UTC,"HI, I can not reproduce this issue, in my setup, could you provide more detail log?"
1824814,2019-04-15 14:07:04 UTC,I also observed this behaviour on a standard 2+X system.  System recovery was not possible in my case.
1824814,2019-05-13 19:48:15 UTC,This issue was reproduce in load  20190508T013000Z . Seen during the install after configuring ntp . To clear  alarm need to lock and unlock controller-0.
1824816,2019-04-18 15:41:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824820,2019-04-15 14:11:03 UTC,indicator-appmenu package was pre-selected and is probably wrong
1824821,2019-09-27 09:03:53 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1824821,2019-08-21 13:02:01 UTC,"Reviewed:  https://review.opendev.org/676533
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b9ab0590234a034aaddfecc53695669ee38ae65f
Submitter: Zuul
Branch:    master"
1824821,2019-07-03 15:55:31 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668943"
1824821,2019-08-07 03:18:00 UTC,"Reviewed:  https://review.opendev.org/674758
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0a0d55d8a95365f2a8b3bef861ab2410bec9e3ff
Submitter: Zuul
Branch:    master"
1824821,2019-08-06 08:56:00 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/674758"
1824821,2019-08-15 01:39:40 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/676533"
1824821,2019-08-04 20:26:19 UTC,"Reviewed:  https://review.opendev.org/668943
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=1e74f318d68c131948dcad566ac11034bcef49ab
Submitter: Zuul
Branch:    master"
1824822,2019-04-16 02:40:02 UTC,"Please tell us what the error message is that you see, ideally with a photo."
1824822,2019-06-15 04:17:50 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1824823,2019-04-15 14:46:33 UTC,This falls under the expansion of juju trust to enable Juju api itself as well. As part of that the credentials would be provided and this is a good reminder that the cert used should be part of that data as well.
1824824,2019-04-17 12:18:24 UTC,"Sorry, can you please try with the new virtualbox?
In case, please run apport-collect 1824824
because I can't see the dkms.log file..."
1824824,2019-06-17 04:17:36 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1824826,2019-04-15 17:07:09 UTC,"Apologies, please close, problem stemmed from include single quotes and using , in setup.cfg !!!"
1824827,2019-05-14 22:58:22 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824827,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1824827,2019-04-26 14:06:43 UTC,Verification successful on Cosmic.
1824827,2019-04-25 22:32:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1824827,2019-04-15 17:29:44 UTC,Patch posted for SRU:
1824827,2019-04-15 16:31:29 UTC,"testcase
========"
1824827,2019-04-15 16:31:17 UTC,"testcase
========"
1824827,2019-04-15 16:30:55 UTC,"testcase, userspace part."
1824827,2019-04-15 16:30:38 UTC,"testcase, kernel part."
1824827,2019-04-15 17:36:46 UTC,"The change introduced by the patch is evident in the kernel message log for Thread 0:
between page indexes 2 and 1 there's now another function call to write_cache_pages()
instead of just another iteration of the for-loop inside one call."
1824829,2019-06-13 14:46:46 UTC,"Reviewed:  https://review.opendev.org/653932
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=f6fb3cd53e5b9fb9c68797fe1f8563e6c461514c
Submitter: Zuul
Branch:    master"
1824829,2019-04-19 13:57:57 UTC,The fix patch is in review https://review.openstack.org/#/c/653932
1824829,2019-06-17 17:27:48 UTC,Issue was not seen recently
1824829,2019-04-15 20:08:40 UTC,"Reviewed:  https://review.openstack.org/652745
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=9f78bc667d9ed8911a55a11614146642e3e33ae9
Submitter: Zuul
Branch:    master"
1824829,2019-04-15 18:02:31 UTC,"Uploaded this review to get sanity passing
https://review.openstack.org/#/c/652745/"
1824829,2019-04-15 17:42:26 UTC,2019-04-15 08:58:20.842 104327 ERROR sysinv.conductor.kube_app [-] Application apply aborted!.
1824829,2019-04-15 15:27:21 UTC,"This is also reproducible on a storage system, using build 20190412T013000Z."
1824829,2019-04-18 21:36:56 UTC,"Re-opening this bug as only a temporary fix was submitted. As per the review comments from Bob Church in https://review.openstack.org/#/c/652745/, the proper way to do this is to introduce a meta_override for the wait field based on the vswitch type value. An example is available in helm/garbd.py which is providing a _meta_overrides() function to tweak the armada manifest. Something similar should be done in helm/openvswitch.py"
1824831,2019-08-21 18:34:07 UTC,"Following step is no longer valid.
system service-parameter-add nova pci_alias gpu-pf=""device_id=0522,vendor_id=102b,name=gpu""
Invalid service name nova."
1824831,2019-09-04 02:26:31 UTC,Yes agreed. Closing. Also the issue mentioned in #17 is not seen on Aug25 load.
1824831,2019-09-03 01:48:05 UTC,"Hi Yang,"
1824831,2019-08-23 02:21:13 UTC,"Hi Yang,"
1824831,2019-08-22 13:30:58 UTC,"However, with stx2.0 and master ""2019-08-20_20-59-00"" load, even the crypto QAT VF seems to be broken (it was working with stx2.0 2019-08-16_20-59-00 load).
# nova instance launches into error state right away
# compute host does not have virtual QAT devices listed via lspci (both C62x and dh895xcc)"
1824831,2019-08-22 13:30:33 UTC,"I think possible steps for GPU passthrough are as following:
1. Find out valid gpu devices via system host-device-list --a, enable it if not already enabled.
2. Find out all the existing pci alias minus the invalid alias without vendor id and product id via system helm-override-show stx-openstack nova openstack
3. Compose a helm override yaml file containing pci alias found in step2 plus the valid one for gpu with the device id and product id found in step1.
such as below:
conf:
 nova:
  pci:
    alias:
        type: multistring
        values:
        - '{""vendor_id"": ""8086"", ""product_id"": ""0435"", ""name"": ""qat-dh895xcc-pf""}'
        - '{""vendor_id"": ""8086"", ""product_id"": ""0443"", ""name"": ""qat-dh895xcc-vf""}'
        - '{""vendor_id"": ""8086"", ""product_id"": ""37c8"", ""name"": ""qat-c62x-pf""}'
        - '{""vendor_id"": ""8086"", ""product_id"": ""37c9"", ""name"": ""qat-c62x-vf""}'
        - '{""vendor_id"": ""102b"", ""product_id"": ""0522"",""device_type"":""type-PF"",""name"": ""gpu""}'
4. Override nova helm charts with above yaml file and reapply stx-openstack
5. create flavor with pci_passthrough:alias=gpu:1
6. launch vm using above flavor"
1824831,2019-08-21 20:22:23 UTC,"Raising the priority of this bug to High as this is basic VM pass-through functionality. If this is indeed broken and requires additional code changes, these will need to be cherrypicked to the stx.2.0 release."
1824831,2019-08-20 02:12:24 UTC,"Hi Yang,"
1824831,2019-08-22 14:06:37 UTC,"controller-0 and compute-1 logs from stx2.0 0821 load are attached, where compute-1 is available, QAT device is inventoried and can be seen via system host-device-list, but no virtual PCI devices listed in lspci on compute-1."
1824831,2019-08-19 15:05:36 UTC,"I revisited the automated testcase based on Zhipeng's comments. It failed in retest due to it was trying to launch a vm with sriov vif as well as qat vf, and the system I used does not have Ethernet device with sriov.
After removing the sriov vif requirement from the test, the VM with crypto QAT-VF was successfully launched."
1824831,2019-08-19 08:45:57 UTC,"Hi Yang,
Device type is not mandatory, we test PASS, also without device type.
In my patch, it just remove class_id.
In your latest log, you just test QAT?, I do not see gpu in alias list."
1824831,2019-08-15 13:14:43 UTC,Retest failed with stx2.0 0813 load.
1824831,2019-07-10 14:17:25 UTC,"Reviewed:  https://review.opendev.org/657535
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=05b7f6d4450ce1afc8e3f8b2d41f24ea647176a7
Submitter: Zuul
Branch:    master"
1824831,2019-04-15 17:11:47 UTC,Marking as release gating; functionality broken as part of the move to containerized openstack.
1824831,2019-07-08 16:51:33 UTC,"go to push for more +2 reviews from core reviewers, in order to merge the patch: https://review.opendev.org/#/c/657535"
1824831,2019-06-14 08:13:39 UTC,Be able to create vm with QAT passthrough devices
1824831,2019-05-22 02:43:03 UTC,"Hi Yang,"
1824831,2019-08-19 20:17:00 UTC,"GPU device is missing ""vendor_id"" and ""product_id"" in the alias, so nova instance ended up with a device from a random passthrough device, in my case, on a compute host with both Crypto and GPU devices, even though the nova flavor specifies ""pci_passthrough:alias""=""gpu:1"", eventually the Crypto VF got used."
1824831,2019-05-13 14:47:56 UTC,"Review posted for proposed fix:
https://review.opendev.org/657535"
1824832,2019-04-17 08:25:40 UTC,"We can test, no problem. If it works it's ok, and it not, we have to use still the extra step we make now to make it a swap disk, so no problem at all."
1824832,2019-04-16 01:35:24 UTC,I was told that usually the swap disk won't be a problem as we usually use VDISK
1824832,2019-04-16 08:01:24 UTC,"ok, thanks for the detailed explanation, the request make sense to me"
1824832,2019-04-16 07:37:59 UTC,"We have our systems with 2 vdisk as the 2 first swap devices, there is a 3rd one on disk. This is best practice for linux servers on Z. Depending how much memory there is on a LPAR, we decide how big the vdisks are. But we have always a 3rd one on disk, and that one depends on memory for the server. We make servers for Oracle Databases and during install/patching and sometimes due to more connections there is more memory necessary.
So we want to make this 3rd disk with cc with the option to format with swap."
1824832,2019-04-17 01:39:30 UTC,"ok, it seems not hard to add the 'swap' into white list, but I don't know whether I can do thorough test due to other work (actually the functions are already there just need enable them from API layer), so will you be able to give a try and provide some feedback? Thanks"
1824837,2019-06-04 22:08:43 UTC,"Reviewed:  https://review.opendev.org/652711
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=87daf8abe64f9b51fb840a455088b18fd0a791ff
Submitter: Zuul
Branch:    master"
1824837,2019-05-28 13:05:32 UTC,Quick update of what's going on with this bug:
1824837,2019-04-16 13:25:28 UTC,Jens Harbott found some uses via codesearch.openstack.org:
1824837,2019-04-24 14:02:35 UTC,"Patch to remove use of CINDER_PERIODIC_INTERVAL from networking-midonet:
https://review.opendev.org/#/c/655448/"
1824837,2019-04-15 16:06:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/652711"
1824837,2019-04-15 15:53:27 UTC,"Using 'grep -R -I -n -i CINDER_PERIODIC_INTERVAL *', I don't find any use of the var in the openstack-infra/openstack-zuul-jobs repo."
1824837,2019-04-24 14:09:53 UTC,"Patch to remove use of CINDER_PERIODIC_INTERVAL from openstack/devstack-gate:
https://review.opendev.org/655451"
1824840,2019-07-01 15:44:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/668498"
1824840,2019-09-13 15:07:37 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.1 release.
1824840,2019-09-12 09:32:58 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.1 release.
1824840,2019-07-26 18:15:30 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.1.0 release.
1824840,2019-07-08 18:41:14 UTC,"Reviewed:  https://review.opendev.org/668498
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=de9453ba2a4dabbf5d5e0838e7c12745237876aa
Submitter: Zuul
Branch:    stable/queens"
1824840,2019-07-06 02:01:30 UTC,"Reviewed:  https://review.opendev.org/668497
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=fd62ee68503df96091ef529041e394a550b3a5d4
Submitter: Zuul
Branch:    stable/rocky"
1824840,2019-07-05 12:51:05 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1824840,2019-07-02 00:56:40 UTC,"Reviewed:  https://review.opendev.org/668495
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=9a1491a42fd6679b9222eb22af5844ce3edf5067
Submitter: Zuul
Branch:    stable/stein"
1824840,2019-07-01 15:43:41 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/668497"
1824840,2019-05-07 21:03:16 UTC,"Reviewed:  https://review.opendev.org/656383
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=1762e9b636566e4a78c31def630fffaea44d8f84
Submitter: Zuul
Branch:    stable/stein"
1824840,2019-06-27 23:09:09 UTC,"Reviewed:  https://review.opendev.org/652699
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=8fac4c4334ad2b2ef67040d053a58a9ba8857425
Submitter: Zuul
Branch:    master"
1824840,2019-06-21 15:25:35 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1824840,2019-06-21 13:47:40 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1824840,2019-04-15 15:36:56 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/652699"
1824840,2019-04-29 19:12:09 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656383"
1824840,2019-04-17 22:28:02 UTC,"Reviewed:  https://review.openstack.org/652702
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=847ec663cc3af2c878cae5cd7acc575a9702f239
Submitter: Zuul
Branch:    stable/queens"
1824840,2019-04-17 22:27:53 UTC,"Reviewed:  https://review.openstack.org/652704
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=5203a4a8326b462226a3ac76a64b64164c8b27ca
Submitter: Zuul
Branch:    stable/rocky"
1824840,2019-04-15 15:47:37 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/652704"
1824840,2019-07-01 15:41:49 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/668495"
1824840,2019-04-15 15:45:45 UTC,"Fix proposed to branch: stable/queens
Review: https://review.openstack.org/652702"
1824842,2019-04-15 18:58:42 UTC,"More details from another run: from the failed unit, it didn't restart:"
1824842,2019-04-15 19:35:07 UTC,Also from the relevant rabbitmq-server unit (which is failed with the rabbitmq instance stopped):
1824842,2019-04-16 11:41:32 UTC,== Debugging rabbitmq issue: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1824842 ==
1824843,2019-04-17 16:25:20 UTC,"Hi Tareq,"
1824843,2019-06-17 04:17:42 UTC,[Expired for dovecot (Ubuntu) because there has been no activity for 60 days.]
1824846,2019-07-29 06:48:39 UTC,"I was finally able to find the cause of the error. The above mentioned patch introduced a regression in the pyroute2 library. The error was due to leakage of FDs which lead to NetlinkError: (17, 'File exists')."
1824846,2019-09-03 11:42:31 UTC,"Okay, seems like it's fixed now. We had a lot of tests with 0.5.6 as well and never hit the issue again."
1824846,2019-07-17 07:35:14 UTC,I was unable to reproduce the RuntimeError. However I was able to reproduce the NetlinkError.
1824849,2019-04-15 20:35:52 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1824849,2019-04-16 02:41:23 UTC,If the mouse pointer is moving then it's not Xorg that has frozen. Because Xorg moves the mouse pointer. It sounds like only your shell has frozen.
1824849,2019-06-15 04:17:51 UTC,[Expired for xfce (Ubuntu) because there has been no activity for 60 days.]
1824853,2019-05-03 16:34:29 UTC,"The fix should now be in git master (commits 8b86d6d25807e13a6 and 6e6c4efed995d9ec), so it will be in the 4.1 release."
1824853,2019-04-17 12:12:32 UTC,Unfortunately the fix is too big for this point in the 4.0 release cycle; it'll go into 4.1.
1824853,2019-04-16 08:36:29 UTC,"Patch set posted:
https://patchwork.ozlabs.org/project/qemu-devel/list/?series=102978"
1824853,2019-04-16 04:01:16 UTC,"Returning -1 does not help because all that signals that the buffer is full.
We then flush the buffer and try again, assuming the at the buffer will not fill.
Given that the buffer is usually many megabytes, this is reasonable."
1824853,2019-04-15 17:09:12 UTC,"Also attaching static-compiled executable ""s2.exe""."
1824853,2019-04-17 11:26:43 UTC,"Richard, thank you for solving this so fast!
I certainly can confirm attached executables work fine for me on patched version."
1824855,2019-06-11 13:34:42 UTC,"On Tue, Jun 11, 2019 at 02:07:14AM -0000, Daniel van Vugt wrote:

> What model machine are you seeing this bug on?
"
1824855,2019-06-11 11:22:40 UTC,*** Bug 1719180 has been marked as a duplicate of this bug. ***
1824855,2019-06-26 05:51:00 UTC,"The strange part for me is if I run ""systemctl start fprintd"", it starts successfully and everything works until it gets automatically stopped again after a short delay.  The problem is something specific to the way it's being started by other processes."
1824855,2019-10-03 09:51:24 UTC,I experience the same problem on my xps9360 (without fingerprint reader) after a clean install of ubuntu 19.10. I never experienced this problem on 18.04 and the earlier ubuntu versions I ran on this laptop. The delay is ~ 15-20 seconds and there are error messages in the Journactl log:
1824855,2019-10-03 10:22:27 UTC,"I tested uninstalling fprintd, this indeed works around the problem."
1824855,2019-10-03 16:24:25 UTC,"I'm on Debian Buster, seeing the same behaviour (i.e. long timeout before being shown the login screen in GDM3). Before the upgrade from Stretch all worked as expected.
Uninstalling fprintd and libpam-fprintd solves the issue. But I like to have the fingerprint reader working ;-) This is on a Lenovo T430 laptop, fingerprint reader ID 147e:2020 Upek TouchChip Fingerprint Coprocessor."
1824855,2020-01-24 09:50:06 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1824855,2020-04-30 21:19:53 UTC,"This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'."
1824855,2020-08-22 07:57:11 UTC,Encountering this issue on an up-to-date F32 :
1824855,2020-08-22 07:58:48 UTC,"Can this bz be reopened, or do I need to file a new bug report against F32 ?"
1824855,2020-08-22 08:46:57 UTC,"# strace -o /tmp/strace_fprintd-list.out -tt -f fprintd-list $USER
list_devices failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
1824855,2020-08-22 08:47:53 UTC,"Created attachment 1712228
strace output of ""fprintd-list $USER"""
1824855,2020-08-22 08:51:11 UTC,$ strace -o /tmp/strace_su.out -tt -f su
1824855,2020-08-22 08:51:40 UTC,"Created attachment 1712229
strace output of ""su"""
1824855,2020-08-22 08:56:22 UTC,"Note : this behaviour usually starts to occur after a couple of days uptime (this is on a Dell XPS7390 2-in-1 with unrecognized fingerprint reader), for every action which requires authentication (su, sudo, virt-manager, screensaver unlocking)."
1824855,2020-05-26 14:29:15 UTC,"Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1824855,2019-06-11 02:07:14 UTC,What model machine are you seeing this bug on?
1824855,2019-08-19 10:30:31 UTC,"(In reply to Christophe Fergeau from comment #3)

> backtrace of fprintd while it's hung
>


<snip>

> #19 0x00007fbcdda6f957 in sd_event_run (e=0x5627d5f75c10,
>     timeout=18446744073709551615) at
> ../src/libsystemd/sd-event/sd-event.c:2690
> #20 0x00005627d4abc5a2 in manager_loop (m=0x5627d5f77520)
>     at ../src/core/manager.c:2291
> #21 0x00005627d4a1ece1 in main (argc=5, argv=<optimized out>)
>     at ../src/core/main.c:1937
"
1824855,2019-06-08 00:50:12 UTC,"I've seen this too, but from a long time ago (like Christophe), not starting with F30 (like Matt and Michael). I figured out that removing fprintd helped a while back."
1824855,2019-06-10 22:38:12 UTC,I was wondering why it took so long to be able to unlock my laptop and it looks like it is this bug.
1824855,2018-01-16 07:40:09 UTC,"Description of problem:
After update to F27, I am facing issue during login to the system as a user. When a screen is locked (screen with the clock) and I hit any key to show password screen a system completely freeze for 15-20 seconds and after that time I am finally able to type my password."
1824855,2018-01-17 14:38:36 UTC,"Hitting that occasionally on my f27. Once it starts triggering, 'fprintd-list $username' triggers it too (it hangs for 25 seconds and dies with a service timeout rather than telling me ""no device found).
Commenting out ProtectSystem=strict in /usr/lib/systemd/system/fprintd.service makes it go away"
1824855,2018-01-17 14:58:49 UTC,"Looking at fprintd strace/backtrace while it's stuck, I figured out it was trying to run statfs on some stale cifs mountpoints I had on my laptop. After unmounting them (and with an unmodified systemd service file), I no longer get hangs running 'fprintd-list $username'"
1824855,2018-01-17 14:59:35 UTC,backtrace of fprintd while it's hung
1824855,2018-10-08 10:19:34 UTC,Still an issue with f29
1824855,2018-10-08 11:44:31 UTC,"I don't know why systemd is trying to bind remount the backup share on your NAS, but it probably (still) shouldn't be doing that."
1824855,2019-04-16 02:45:00 UTC,"Steve,"
1824855,2019-06-07 23:44:42 UTC,"Seeing this problem immediately after ""dnf system-upgrade"" upgrade from F29 to F30:"
1824855,2019-04-23 20:32:59 UTC,Could you try starting fprintd manually and see if it displays any error?
1824855,2019-04-23 20:57:13 UTC,There are no errors in the journal / systemctl status for fprintd aside from a timeout.
1824855,2019-04-24 01:33:32 UTC,"Yes the ""long delay"" appears to be mostly the 25 seconds mentioned in:"
1824855,2019-04-24 01:39:57 UTC,Can you please try uninstalling 'fprintd'?
1824855,2019-04-24 01:43:55 UTC,"Also, it is gnome-shell requesting fprintd via js/gdm/fingerprint.js"
1824855,2019-06-04 07:16:42 UTC,Same on f30.
1824855,2019-06-05 15:00:14 UTC,I'm also seeing this on F30.  It just started yesterday for me.
1824855,2019-04-23 19:23:38 UTC,"After locking my screen and trying to log in, here's what I see in the log corresponding to a delay in the login prompt being shown."
1824855,2019-06-08 00:05:24 UTC,"WORKAROUND:
For me,"
1824856,2019-06-14 13:57:44 UTC,"When you say state, do you mean status?"
1824856,2019-06-14 14:07:11 UTC,"Yes, I mean status :)"
1824856,2019-06-14 14:47:33 UTC,This RFE was approved by the drivers team
1824857,2021-02-11 16:19:08 UTC,"Well, it's because upgrade has changed the way we handle hosts files and we changed some other stuff that resulted that way."
1824857,2021-01-29 19:45:53 UTC,"I've just tried to set up rabbitmq cluster on 3 nodes from 22.0.0 and was not able to reproduce the issue.
I think you might be facing an issue when hosts file contain extra record that makes rabbitmq incorrectly resolve hostnames which we recently added as a release note https://opendev.org/openstack/openstack-ansible/commit/09fa3b6613462a2b508865b96618241ee15f364c"
1824857,2021-02-09 16:08:04 UTC,Can you kindly check if it's the case for you and if removing that record helps?
1824857,2021-01-26 10:42:22 UTC,I have the same issue with an ubuntu-based deployment and OSA 22.0.0.
1824857,2021-02-11 11:19:17 UTC,"Sorry, for the late reply. Seems that the mentioned hosts were the issue, but I don't know how/why they were created. A clean new deployment worked fine. Thanks for the tip."
1824858,2019-08-12 10:03:28 UTC,"If the directory left is empty and has no effect on cold migration, I'm wondering that can we think maybe this is not a bug?"
1824858,2019-08-20 15:26:05 UTC,"@yang, could you help check if the directory is also empty?"
1824858,2019-08-20 15:29:48 UTC,"@tianhao, Can you double confirm the directory is empty without any files inside?
If only having the empty directory, maybe nova code just doesn't delete the /var/lib/nova/instances/, because of either the permission issue or forgetting to delete it after code migration."
1824858,2019-08-21 03:47:32 UTC,"Ok, I will confirm the directory again."
1824858,2019-09-12 07:06:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/681652"
1824858,2019-09-17 01:59:02 UTC,"Change abandoned by hutianhao27 (hu.tianhao@99cloud.net) on branch: master
Review: https://review.opendev.org/681652
Reason: revert previous patch"
1824858,2019-09-19 08:04:06 UTC,"I have a patch to solve this problem, but it needs someone to review it.(https://review.opendev.org/#/c/682523/)"
1824858,2020-05-22 15:06:32 UTC,"Reviewed:  https://review.opendev.org/726863
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=44609c5847dfe591caf3f40497f1abc7c7aa7384
Submitter: Zuul
Branch:    stable/rocky"
1824858,2020-05-11 14:17:25 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/726861"
1824858,2020-05-11 14:18:00 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/726863"
1824858,2020-05-11 14:18:14 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/726864"
1824858,2020-05-20 00:26:50 UTC,"Reviewed:  https://review.opendev.org/726861
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=890882ebbf74db14a7c1904cca96cd7f5907493b
Submitter: Zuul
Branch:    stable/train"
1824858,2020-05-20 16:17:06 UTC,"Reviewed:  https://review.opendev.org/726862
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a63c97fd2d13de532330523587894163e32a892f
Submitter: Zuul
Branch:    stable/stein"
1824858,2019-08-10 12:30:05 UTC,There are files left after cold migration every time. But the directory left is empty and has no effect on cold migration. So I think maybe we can delete this empty directory and I'd like to know if this is appropriate。
1824858,2020-05-25 23:28:44 UTC,"Reviewed:  https://review.opendev.org/726864
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8ba6d8e9c043cc2682d5bb577c8dc3e49614d15f
Submitter: Zuul
Branch:    stable/queens"
1824858,2020-02-06 03:00:57 UTC,"Reviewed:  https://review.opendev.org/682523
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=404932f82130445472837095b3ad9089c75e2660
Submitter: Zuul
Branch:    master"
1824858,2019-08-02 02:10:02 UTC,"I have reproduced this issue, and there are files left after cold migration. I still try to find out why this issue happened."
1824858,2020-05-11 14:17:43 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/726862"
1824858,2019-07-30 11:29:57 UTC,I try to reproduced this problem. But there are no files left after cold migration everytime either using horizon or CIL.
1824858,2019-07-30 14:07:35 UTC,"Still seeing this issue in cold migration tests with remote storage using master load 20190727T013000Z, and this has been 100% reproducible."
1824858,2019-04-17 17:49:26 UTC,Assigning to the distro.openstack PL. Need team to determine if this is expected openstack behavior or if this is a bug that requires nova follow-up.
1824858,2019-04-17 18:18:09 UTC,"StarlingX is now running against upstream OpenStack Nova master, so this issue is possibly a Nova issue."
1824858,2019-06-04 13:17:41 UTC,"Wendy, can you please re-test and check to see if migration back to the original host is impacted by this issue?  That would help us determine the Importance of this."
1824858,2019-06-17 15:47:52 UTC,"I wasn't able to reproduce this on Nova master. I have vague memories of something like this being reported in older versions, but having been fixed since then, though I can't find hard evidence in the shape of bug reports and/or reviews. I'm going to leave this as Incomplete until we get more information, in the shape of:"
1824858,2019-06-17 17:12:05 UTC,This had failed on hardware lab remote storage system ip 20-27 in the following testcases on the following loads.
1824858,2019-06-17 19:04:18 UTC,Fails in the check to see that the source host no longer has instance files after the cold migration
1824858,2019-06-17 19:22:46 UTC,"For example
# stat /var/lib/nova/instances/4a6f01a6-d9be-4fab-8524-da901343f39f
  File: ‘/var/lib/nova/instances/4a6f01a6-d9be-4fab-8524-da901343f39f’
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: fd00h/64768d    Inode: 13762561    Links: 2
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2019-06-17 19:08:52.056799204 +0000
Modify: 2019-06-17 18:25:43.886821025 +0000
Change: 2019-06-17 18:25:43.886821025 +0000
 Birth: -"
1824858,2019-06-18 17:04:49 UTC,"It's not explicitly specified above, but the fault scenario involves compute nodes using RBD storage as opposed to local storage."
1824858,2019-09-17 01:57:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/682523"
1824858,2019-06-19 23:57:28 UTC,"On each compute node, nova.conf has the following set under the libvirt section:"
1824858,2019-06-21 19:30:20 UTC,"Setting status to ""Confirmed"" as per notes from Chris Friesen who is able to reproduce the issue in starlingx. I believe the next step is for the nova team to attempt to reproduce with the specific config above."
1824858,2019-07-05 20:33:26 UTC,Assinging to Yong Hu to follow-up since Bruce is out.
1824858,2019-07-15 20:56:42 UTC,"@Martin, which upstream LP was this issue duplicated to?
Or what's the analysis to prove this issue is a general Nova issue instead of a STX issue."
1824858,2019-07-16 04:50:15 UTC,Hi Chris
1824858,2019-07-17 16:59:44 UTC,"Still failures in regression
Lab: WCP_113_121
Load: 20190713T013000Z
AssertionError: Instance files found on previous host
FAIL	20190713 16:29:06	test_cold_migrate_vm[remote-0-0-None-2-volume-confirm]
FAIL	20190713 16:31:38	test_cold_migrate_vm[remote-1-0-None-1-volume-confirm]
FAIL	20190713 16:34:23	test_cold_migrate_vm[remote-1-512-None-1-image-confirm]"
1824858,2019-07-19 08:36:40 UTC,My reproduce step
1824858,2019-07-19 17:59:29 UTC,"Chen, can you explain why you manually moved the instance rather than using the nova cold migration? This is causing nova to take very different code paths than would normally be taken on a successful migration."
1824858,2019-06-19 23:27:32 UTC,I reproduced it with StarlingX.  After the initial cold migration we're left with this on the original compute node:
1824858,2019-07-26 22:06:35 UTC,"change the priority to low.
If upstream fixes this in future, stx will get it as a part of rebase."
1824866,2019-05-22 15:26:59 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824866,2019-05-20 16:20:36 UTC,I tested the new version of ubuntu-release-upgrader in bionic-proposed and confirm that the bug is now fixed.
1824866,2019-05-16 17:32:29 UTC,"Hello Brian, or anyone else affected,"
1824866,2019-05-22 15:26:55 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.33
1824868,2019-06-21 05:38:41 UTC,Can confirm I get this crash and also when I try to remove the Applications Menu shortcut. Not sure if a workaround and it doesn't appear Cairo is maintained anymore ???
1824868,2020-12-07 20:03:41 UTC,"I can also confirm this bug on Ubuntu 20.04 and the latest Arch Linux. A test on Manjaro 20.02 provides a stable cairo-dock, the launchers submenu ""edit"" works there.
A package comparison between Archlinux and Manjaro did not give any clues..."
1824868,2020-12-19 12:52:23 UTC,"Hi,
I think it is related to commit 92d66a7c1ab6d791a8fa0382e63bd46b4c09fc61
back in May.
Feel free to try the latest version from the sources, it should work."
1824870,2019-04-15 20:37:57 UTC,"The log suggests that the disk is having error, more likely an hardware/disk corruption problem than an ubiquity one..."
1824870,2019-04-17 10:33:42 UTC,Could you check your disk/filesystem and see if problems are reported?
1824870,2019-04-22 22:03:19 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1824870,2019-06-22 04:17:31 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1824873,2019-09-16 17:33:17 UTC,Migrated to https://github.com/widelands/widelands/issues/2131
1824873,2019-04-15 20:33:29 UTC,"I remember there were a similar idea for the trees: Instead looking into the help for which terrain make which tree grow well, define climate areas on a map. Of course this makes it possible to allow desert trees on green land terrains, but hey, why not :-)"
1824873,2019-04-16 11:25:09 UTC,"We would also need changes to the sound handler, maybe even switching to a more powerful backend. Rainfall is no fun when you can't hear it."
1824873,2019-04-16 17:39:35 UTC,"> If i remember right, SirVer was always against applying anything that makes the game time dependent.
> And what will happen if rain falls in the desert: Will the desert terrains will turn into summer terrains for a short time?
"
1824874,2019-04-15 20:23:54 UTC,Screenshot of the dialog in question.  The text comes from aptdaemon's policykit policy.
1824874,2019-04-15 20:31:11 UTC,"journalctl output for the period in question, taken from 'journalctl -l --since today | grep gnome-shell'."
1824874,2019-04-16 00:09:13 UTC,the window did go away when I did a kill -HUP gnome-shell.
1824874,2019-04-16 02:48:10 UTC,This sounds particularly relevant:
1824874,2019-04-16 02:53:30 UTC,It also sounds like this might be the new form of bug 1734095.
1824874,2019-04-19 20:27:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824874,2019-04-19 20:28:24 UTC,I saw the authentication window only once after resume from suspend to RAM.
1824874,2019-04-23 13:49:51 UTC,"Tagging as rls-dd-notfixing, it doesn't prevent the bug to be worked on/fixed but it's not easy enough to trigger/doesn't have enough impacted users or reports to quality as a rls bug atm"
1824874,2019-12-06 12:18:01 UTC,"Same problem here. I restarted (successfully) apache2 service a few hours ago, then I moved away from my computer, and when I came back, there was this little buggy window (and it's not the first time this bug happens to me)"
1824874,2019-12-06 12:19:39 UTC,"And when I press ALT+F2, then type ""r"" and press enter, it's gone !"
1824874,2019-12-06 12:57:54 UTC,Why haven't I thought it?! Thank you!
1824874,2019-04-15 20:20:11 UTC,Restarting polkit.service does not cause the window to disappear.
1824874,2020-01-03 05:19:49 UTC,"I get this all the time after resuming from sleep, unfortunately with wayland it's not possible to reload gnome-shell so I have to log out/in to get rid of it."
1824874,2020-02-19 23:41:06 UTC,I just tried some experiments with pam_yubico in my distro.
1824874,2020-08-24 08:28:10 UTC,"I encountered this issue on latest Fedora 32. So this is not unique to ubuntu. I have a dual booted system and when I tried to access windows partition data from fedora, I was required to type the password in authentication dialogue, after which I could access windows data. Then when I locked and unlocked again, this unclickable authentication dialogue box was stuck on top-left corner of the screen (If I tried to click it, whatever was 'behind' it was clicked)."
1824874,2020-08-24 18:45:53 UTC,"This happend to when, I set the system to update, and then left it unattended and system got suspended, when I wake it up again the dialog was there unclickable, non cancelable."
1824874,2020-09-07 05:59:09 UTC,"seeing more people encountering this - thought I'd share my observations:
- did not see this for a few weeks now
- toyed around with nextcloud for a bit yesterday (the new desktop sync client)
- also tried to connect a (hacked) amazon fire hd10 tablet (which failed, also tried to get connection using gMTP, then left my system to sleep/idle)
- came back to the invisible/unclickable thingie
- alt-f2 + r gets rid of it as usual"
1824874,2020-09-17 07:34:45 UTC,+1 from me
1824874,2020-09-19 20:22:58 UTC,Same as the rest got this after returning. But wanted to add one thing nobody did comment about is that I could keep *show/hide my password*! That's a security issue if you do not know yet you can use alt+f2 + r to get rid of the window.
1824874,2020-09-28 11:51:43 UTC,"Same here. Cannot kill it with xkill, but doing de Alt+f2 then press r does the trick."
1824874,2020-10-08 11:33:25 UTC,Problem still present. Just experienced it on Ubuntu 20.04.1 LTS. The provieded workaround to get it removed fixed it.. for now.
1824874,2020-10-15 08:06:41 UTC,"Same for me. Also Alt + F2 and executing ""r"" resolved it..."
1824874,2020-10-29 06:48:44 UTC,Can also confirm on Ubuntu 20.04.1 LTS. Didn't find the process so I couldn't kill this annoying window. It popped when I started to install dependancies within pycharm.
1824874,2020-10-30 09:19:20 UTC,"+1, bug still there in 20.04.1 LTS."
1824874,2020-11-04 11:14:47 UTC,"Bug exists in 20.10 too, I just triggered it. It happened after screen lock/unlock cycle."
1824874,2020-11-05 09:19:35 UTC,"I solved the problem with
$ sudo killall -9 gnome-shell"
1824874,2020-08-22 13:51:42 UTC,"Same problem here, just happened this morning.
---------------------------------------------------------------------------------------------------
vartan@system76:~$ ps axu | grep gvfsd
gdm         4984  0.0  0.0 248336  7500 ?        Ssl  Aug20   0:00 /usr/libexec/gvfsd
gdm         5002  0.0  0.0 312800  6360 ?        Sl   Aug20   0:00 /usr/libexec/gvfsd-fuse /run/user/125/gvfs -f -o big_writes
vartan      6798  0.0  0.0 248440  7748 ?        Ssl  Aug20   0:00 /usr/libexec/gvfsd
vartan      6803  0.0  0.0 378336  6504 ?        Sl   Aug20   0:00 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
vartan      7182  0.0  0.0 322844  8520 ?        Sl   Aug20   0:00 /usr/libexec/gvfsd-trash --spawner :1.3 /org/gtk/gvfs/exec_spaw/0
vartan      7337  0.0  0.0 171368  6764 ?        Ssl  Aug20   0:00 /usr/libexec/gvfsd-metadata
vartan    242879  0.0  0.0 396620  8880 ?        Sl   Aug21   0:00 /usr/libexec/gvfsd-network --spawner :1.3 /org/gtk/gvfs/exec_spaw/2
vartan    242922  0.0  0.0 323604  8360 ?        Sl   Aug21   0:00 /usr/libexec/gvfsd-dnssd --spawner :1.3 /org/gtk/gvfs/exec_spaw/4
vartan    330214  0.0  0.0  17664  2500 pts/1    S+   09:46   0:00 grep --color=auto gvfsd
---------------------------------------------------------------------------------------------------
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.1 LTS
Release:	20.04
Codename:	focal
---------------------------------------------------------------------------------------------------
Linux system76 5.4.0-7642-generic #46~1597422484~20.04~e78f762~dev-Ubuntu SMP Wed Aug 19 14:32:27  x86_64 x86_64 x86_64 GNU/Linux
---------------------------------------------------------------------------------------------------
GNOME Shell 3.36.4"
1824874,2020-11-11 23:10:16 UTC,"I'm also experiencing this bug, after a screen lock / unlock cycle."
1824874,2020-11-21 22:59:33 UTC,"20.04.01 right after install, essentially nothing else on the machine"
1824874,2020-12-10 21:36:06 UTC,"Just happened to me for the first time, on 20.04, ""Alt+F2"" then entering ""r"" worked for me, thanks to all who suggested it"
1824874,2020-12-15 04:29:05 UTC,Also seeing this on 20.10. Same workaround works.
1824874,2020-12-15 09:37:32 UTC,Those having the issue could you try to describe the actions you did before it happened?
1824874,2020-12-18 18:10:29 UTC,"So, the problem only happens to me when the computer locks the screen / suspends. Upon logging in the authentication window appears, being impossible to interact and sometimes causing system crashes. It seems to me that it is some authentication because of the wifi network ..."
1824874,2020-12-23 07:42:28 UTC,"Same issue here, it is the second time.
Ubuntu 20.04
Just wake up, and my laptop was locked the entire night, I unlocked it, and see the dialog. No other actions."
1824874,2021-01-21 10:30:26 UTC,"Same here, 20.04 installed on a reformatted disk.  Nine months without this problem (which had pestered me on 19.10), and now it suddenly pops up - literally.  Any progress?"
1824874,2021-02-10 08:54:39 UTC,Moved to upstream bug https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3701 which also has a fix proposed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1662
1824874,2021-02-12 20:00:22 UTC,"Just got this for the first time, 20.10. The cancel button reacts to click but does not dismiss. Looks shady so I'm not going to try my password. xkill has no effect. I see it's been nearly two years now."
1824874,2021-02-18 20:24:10 UTC,"damn it. folks, i clicked on the status by mistake and changed it to released. I am SO SORRY. Can someone please change it back to Fix submitted?
Again, sorry."
1824874,2020-02-18 14:51:49 UTC,"Last night I encountered similar bug behavior with a different message. Several hours after a printing related crash, another orphaned authentication dialog was painted on top of the gnome shell with the message:"
1824874,2020-02-12 20:45:41 UTC,"Sergey, I think you might be onto something. I use a yubikey and have PAM configured to detect the yubikey automatically for sudo. So it could be a timing issue as you suggest, or maybe GNOME is making inappropriate assumptions about whether authentication requires actual user input."
1824874,2020-11-11 23:10:55 UTC,(Freshly installed Ubuntu 20.04.1 here.)
1824874,2020-07-29 16:48:41 UTC,ID = #3026
1824874,2020-04-26 15:15:39 UTC,I might be experiencing same/similar bug on a fresh install of 20.04. I don't have a Yubikey. Or at least I don't think I do :).
1824874,2020-07-26 10:37:50 UTC,"thank you, people - restarting (Alt-F2 > r) indeed gets rid of the window.
Do we know what causes it?
How to fix?"
1824874,2020-01-24 09:36:44 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1824874,2020-04-27 11:57:13 UTC,"@Dimitry, could you give an example of folder triggering a such prompt?"
1824874,2020-07-28 03:41:17 UTC,It would be a problem in gnome-shell's dialog code so someone please report it to the gnome-shell developers at:
1824874,2020-02-07 00:09:59 UTC,I've seen this same bug three times in the past two days on a new (up-to-date) ubuntu 19.10 system. The bug is NOT therefore unique to 19.04. Clicking anywhere on the dialog does in fact produce the behavior that would be appropriate for clicking whatever is below the dialog. This appears therefore to be an incorrect painting problem in gnome shell. Restarting gnome-shell (<alt><F2> enter r) does in fact get rid of the incorrectly painted dialog.
1824874,2020-02-07 01:50:30 UTC,"Bruce,"
1824874,2020-02-12 19:24:47 UTC,"This morning, I managed to trigger this bug again. I installed a new component from the Activities/Search view. The component installed without requiring any authentication, but 30 minutes later, the offending authentication dialog image appeared on the screen."
1824874,2020-02-12 19:51:01 UTC,Just want to add five cents: I am not active user of Ubuntu right now but I faced with the same issue in many other versions of GNOME in other distributions (currently I suffer from this issue in Arch Linux). I suspect that it caused by custom PAM modules which add to authorization process some delays (in my case this module is pam_yubico which waits for user action) but I still do not have a chance to check it.
1824874,2020-05-01 15:46:26 UTC,"Like Dimitry, I have experienced the same (or a similar) bug on a fresh 20.04 install. I'm attaching a picture of it. Both ""Authenticate"" and ""Cancel"" buttons are clickable (""Authenticate"" only once) but don't make the window vanish. I confirm that killing the gnome-shell caused the window to disappear."
1824874,2020-05-02 01:55:04 UTC,"I also just experienced this same bug on fresh install of Focal 20.04. I don't have Yubikey. Since the appearance of the window is delayed from whatever triggers it, I don't know what the cause is. The behavior is as other describes, a orphaned window on top left corner of screen, clicking the window results in whatever is underneath being clicked. Logging out and relogging makes the window disappear."
1824874,2020-05-02 12:08:52 UTC,"Same here with a fresh Ubuntu 20.04 LTS on a laptop (Lenovo Y50).  Pressing Alt+F2, typing ""r"", and pressing enter helps as noted before when this appear.
The only thing related to elevated privileges I can think of is using admin:/// in nautilus.
The problem generally appears after coming back from suspended to resumed state."
1824874,2020-05-02 20:50:14 UTC,"Hello,"
1824874,2020-05-02 20:58:06 UTC,"Hello,"
1824874,2020-05-02 20:59:02 UTC,oups undismissable
1824874,2020-02-07 02:47:04 UTC,"Yes Daniel, it is the same as shown in the screenshot in comment #3."
1824874,2020-05-13 08:45:42 UTC,"I am having the same problem. A few days ago I upgraded my computer from Ubuntu 19.10 to 20.04. Normally I was starting the MySql server manually. It started working automatically with the update.
When I put the computer to sleep mode and turn it back on, the authentication window for the MySql server is opening at the upper left corner and is not closing in any way.
The thing that catches my attention here is that when I click on the window that does not close, the application under the window detects the click. However, the cancel button and the password text box is not performing their functions even though they sense the clicks correctly.
Notice: Restarting the shell closes the window."
1824874,2020-06-04 08:36:05 UTC,"Same problem here after the 20.04 update.
The dialog appears after wake from suspend state, and looks like the screenshot in #3.
Alt+F2, ""r"" makes the dialog disappear."
1824874,2020-06-27 00:38:37 UTC,"Encountered this problem two times in 20.04 LTS. Both times were after I moved away from my computer to go eat, and came back to see this bug."
1824874,2020-06-02 07:37:52 UTC,"For me, sometimes after login login overlay is not disappeared and prevent from showing any window, but mouse and maybe keyboard events still delivered to some screen areas (see screenshoot)."
1824874,2020-06-01 21:38:39 UTC,"Same issue, brand new fresh install of Ubuntu 20.04"
1824874,2020-05-04 14:54:40 UTC,"I've been getting exactly the same issue as described here, always when I log in and find an ""Authentication Required"" dialog window in the top left of the screen. I've attached a screen shot, the details of my environment are below:"
1824874,2020-05-20 15:41:20 UTC,"@~seb128 After resuming from the lock screen. Ubuntu 20.04, upgraded from 19.10."
1824874,2020-07-18 15:43:36 UTC,+1
1824874,2020-05-18 15:13:09 UTC,"I know this is Ubuntu bug reporting tool, but I have the same problem on Fedora. I didn't find this bug reported on Fedora (I'll report it), but I'd like to add some observations for you, so maybe someone will be able to solve this annoying issue.
I use Yubikey to login to my Gnome desktop. Everything works fine until I run any program as root (e.g. virt-manager, disks). Then I'm asked to touch my Yubikey to authorize and to run the program as root. So far good.
But then I lock the screen (or it locks itself after 5 minutes). When I unlock the screen by touching the Yubikey I see the annoyuing dialog with message ""System policy prevents management of the local virtualized systems"".
I've checked /etc/pam.d/polkit-1 if it uses Yubikey for authentication"
1824874,2020-05-18 07:16:57 UTC,Those adding comments stating you also have the issue could you describe how you trigger it?
1824874,2020-05-17 19:05:42 UTC,I have also been affected by this bug on 20.04
1824874,2020-05-16 05:24:33 UTC,The bug is also present in 20.04. I got it after a system resume from sleep.
1824874,2020-05-13 09:06:51 UTC,This screenshot is an example of controlling programs which are behind the faulty dialog.
1824874,2020-05-19 14:14:36 UTC,"@~seb128 I noticed it after resuming from lock screen. Ubuntu 20.04, upgraded from 19.10"
1824875,2019-04-16 06:08:49 UTC,Could you give details on how you do the partitioning? Which one do you select? What filessystem does it use and do you format it?
1824875,2019-06-16 04:17:24 UTC,[Expired for grub-installer (Ubuntu) because there has been no activity for 60 days.]
1824879,2019-06-26 20:48:30 UTC,This bug was fixed in the package linux-azure - 5.0.0-1010.10
1824879,2019-05-31 15:59:41 UTC,Disco: https://lists.ubuntu.com/archives/kernel-team/2019-May/101028.html
1824879,2019-05-14 19:09:49 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49
1824879,2019-05-14 19:52:13 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
1824879,2019-05-14 19:04:29 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18
1824879,2019-04-30 17:18:07 UTC,"On 4/30/19 10:11 AM, Joseph Salisbury wrote:

> ** Tags removed: verification-needed-xenial
> ** Tags added: verification-done-xenial
>
"
1824879,2019-04-26 10:32:33 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1824879,2019-05-14 22:58:32 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824880,2019-04-17 10:32:58 UTC,"Thank you for your bug report. Do you have specific steps to trigger the issue?
Ideally it should be reported upstream on https://us-bz3.devzing.com/powertopbugs/"
1824880,2019-04-22 18:03:18 UTC,This happens every time I run 'sudo powertop -c' on this machine.
1824881,2019-08-23 01:20:13 UTC,reproduced in 20190822 master ISO sanity tests.
1824881,2019-11-29 20:16:21 UTC,"Closing; as per above, issue is not reproducible on train"
1824881,2019-11-29 18:14:08 UTC,"Issue was not reproduced on train
2019-11-21_20-00-00
wcp_3-6"
1824881,2019-11-27 20:59:55 UTC,In all the attempts I was unable to reproduce this issue and a retest by the reporter was required.
1824881,2019-11-22 19:17:05 UTC,Erich please update this LP with your current status.  What are your plans to debug and address this LP?
1824881,2019-08-23 17:50:14 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1824881,2019-08-15 21:11:12 UTC,"If you want to mark the LP for retest, it should be retested again on the original lab (wp 3-7)"
1824881,2019-04-22 19:23:08 UTC,"BUILD_TYPE=""Formal""
BUILD_ID=""20190421T233001Z"""
1824881,2019-08-08 21:57:33 UTC,I'm unable to reproduce this bug in my virtual environment.
1824881,2019-08-15 21:09:56 UTC,"The original lab I reproduced this on was not available today.
This testcase was run on a different h/w lab (wcp63-66) this time with a newer build 2019-08-12_20-59-00"
1824881,2019-04-24 17:31:01 UTC,Based on Wendy's re-test this is not a bug but was a side effect of a lab MTU size mismatch.  Marking state as invalid since there is no bug.
1824881,2019-04-29 18:07:10 UTC,"Force lock, then unlock operation still appears to fail sometimes in enabling the hypervisor"
1824881,2019-04-22 19:22:47 UTC,"Retested on newer load and confirmed MTUs on both controllers. Force lock and unlock of compute-0
The hypervisor state and status revert to up enabled now."
1824881,2019-06-21 12:26:37 UTC,Assigned to Bruce for re-assignment.
1824881,2019-07-17 04:32:57 UTC,"I was able to reproduce this issue, the hypervisor went down after the lock/unlock. I need to figure it out which component is responsible to bring the hypervisor up to make a further debug. I'll keep updating this issue with the findings."
1824881,2019-08-07 20:35:32 UTC,The last attempt to root cause this issue was with this build:
1824881,2019-05-01 18:12:22 UTC,Based on Wendy's re-test this issue occurred at least once.  From her timeline the compute-2 nova hypervisor remained down 40 minutes after compute-2 went enabled after being unlocked.
1824881,2019-04-17 17:45:00 UTC,"The system in question has a mismatched mtu on the two controllers.
controller-0 has an mtu of 9000 and controller-1 has an mtu of 1500. This can cause issues."
1824884,2019-04-15 21:58:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/652782"
1824884,2019-05-04 22:38:59 UTC,"Reviewed:  https://review.opendev.org/652782
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=a9a51ca6382eb01c99fce51084f64a69f4c7d58a
Submitter: Zuul
Branch:    master"
1824886,2020-02-24 19:07:10 UTC,"> Does the issue occur on non-HWE kernel, i.e. v4.15?
"
1824886,2020-03-24 14:29:25 UTC,apport information
1824886,2020-03-24 14:26:22 UTC,"Also affected, the following was taken when running after 30 minutes on battery:"
1824886,2020-03-24 14:29:09 UTC,"ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  sperger    1086 F.... pulseaudio
 /dev/snd/controlC0:  sperger    1086 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2020-03-11 (12 days ago)
InstallationMedia: Kubuntu 19.10 ""Eoan Ermine"" - Release amd64 (20191017)
Lsusb:
 Bus 001 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 8087:8000 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite C55-B
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-42-generic N/A
 linux-backports-modules-5.3.0-42-generic  N/A
 linux-firmware                            1.183.4
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags:  eoan
Uname: Linux 5.3.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/19/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.30
dmi.board.asset.tag: *
dmi.board.name: ZSWAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: *
dmi.modalias: dmi:bvnTOSHIBA:bvr1.30:bd07/19/2014:svnTOSHIBA:pnSatelliteC55-B:pvrPSCLUU-05M07V:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
dmi.product.family: *
dmi.product.name: Satellite C55-B
dmi.product.sku: PSCLUU
dmi.product.version: PSCLUU-05M07V
dmi.sys.vendor: TOSHIBA"
1824886,2020-03-24 14:29:13 UTC,apport information
1824886,2020-03-24 14:29:15 UTC,apport information
1824886,2020-03-24 14:29:18 UTC,apport information
1824886,2020-03-24 14:29:20 UTC,apport information
1824886,2020-03-24 14:29:23 UTC,apport information
1824886,2020-03-24 14:29:37 UTC,apport information
1824886,2020-03-24 14:29:31 UTC,apport information
1824886,2020-03-24 14:29:32 UTC,apport information
1824886,2020-03-24 14:29:34 UTC,apport information
1824886,2020-03-24 14:29:41 UTC,apport information
1824886,2020-03-24 14:30:40 UTC,"Note: Running Kubuntu 19.10, all updates current as of today.  So this is affecting other Ubuntu-based distributions as well."
1824886,2020-03-24 14:31:29 UTC,Ran and submitted: apport-collect 1824886
1824886,2020-03-25 17:57:21 UTC,"I dont want to close this bug report as fix released, but after my update of ubuntu-base yesterday the issue is gone.  If the original bug reported agrees, then the bug report can be closed."
1824886,2020-06-18 17:28:01 UTC,Issue sill exist in focal fossa with kernel 5.4.
1824886,2020-02-04 03:55:46 UTC,Please perform a kernel bisection if it's a regression.
1824886,2020-03-24 14:29:27 UTC,apport information
1824886,2020-01-19 15:19:46 UTC,I got the same situation and output.
1824886,2020-03-24 14:29:29 UTC,apport information
1824886,2019-04-18 09:40:15 UTC,"Does the issue occur on non-HWE kernel, i.e. v4.15?"
1824886,2019-04-16 08:22:15 UTC,Hello Sebastien!
1824886,2019-04-16 05:53:28 UTC,"Thank you for your bug report. Could you take a screenshot showing the issue?
Could you also copy the output of ""upower -d"" to the bug?"
1824886,2019-04-16 08:29:37 UTC,"Sebastien,"
1824886,2019-04-16 12:45:59 UTC,"@Mike, arguing over the triaging details isn't really that useful, but for the record see https://wiki.ubuntu.com/Bugs/Importance. The battery estimate is indeed useful, but you are so far the only one reporting the issues and one report isn't enough to consider it as High then (for what we know it could be a problem with your laptop)"
1824886,2019-04-16 15:20:03 UTC,"If I unplug the charger and reboot, the command issues the following (100% always):"
1824886,2019-04-16 16:37:56 UTC,Ubuntu log.
1824886,2019-04-16 16:40:50 UTC,How it works in Linux Mint:
1824886,2019-04-16 16:42:10 UTC,Screenshot 1:
1824886,2019-04-16 16:42:47 UTC,Screenshot 2:
1824886,2019-04-16 16:43:20 UTC,Screenshot 3:
1824886,2019-04-16 16:53:41 UTC,"I was looking for a solution in Google. Many people have a problem with the charge indicator in Ubuntu. And basically they all gave up without finding any solution to this problem. If we now find a solution to this problem, it will help many people and make ubuntu even better."
1824886,2019-04-18 15:24:13 UTC,"Version 4.15 works well. Now I have installed Debian 9 with a kernel 4.9 on this device, it works well."
1824886,2019-04-16 19:33:56 UTC,Could you also give some reference on those discussions from others having the issue?
1824886,2019-04-18 06:02:43 UTC,"Thanks for testing, it confirms it's a kernel issue (and see the status is still wrong, worth reporting upstream probably)"
1824886,2019-04-18 06:30:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1824886,2019-04-16 19:33:29 UTC,Can you add your journalctl log from an Ubuntu bug having the issue? Does gnome-control-center display the correct status? (it's not clear from what session/system the screenshots are coming)
1824886,2019-04-17 12:33:31 UTC,upstream https://bugzilla.kernel.org/show_bug.cgi?id=201351 also
1824886,2019-04-17 12:30:34 UTC,"Looking to comment #20 it looks like a kernel issue, the /sys entry tell the charge level is 100%"
1824886,2019-04-17 22:20:59 UTC,"I booted from the LiveCD 19.04. Although charging status is indicated the other way round, percentages are correct and decrease with battery discharge."
1824886,2019-04-17 10:53:18 UTC,I disconnected the power adapter and worked ~30 minutes.
1824886,2019-04-17 10:02:03 UTC,"Thanks for the detail, the journal log you attached is fine it just got lost in the middle of the info."
1824886,2019-04-17 04:58:15 UTC,"https://bugs.launchpad.net/ubuntu/+source/upower/+bug/629258
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1640544
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/572970
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1231550
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/733866
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/455786
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1451195
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/994745
https://ubuntuforums.org/showthread.php?t=1627848
https://ubuntuforums.org/showthread.php?t=1601974
https://ubuntuforums.org/showthread.php?t=937255
https://ubuntuforums.org/showthread.php?t=1692765
https://ubuntuforums.org/showthread.php?t=1354867
https://ubuntuforums.org/showthread.php?t=1566962
https://ubuntuforums.org/archive/index.php/t-1035411.html
https://ubuntuforums.org/showthread.php?t=1627350
https://ubuntuforums.org/showthread.php?t=2415233
https://ubuntuforums.org/showthread.php?t=1634535
https://askubuntu.com/questions/894023/battery-is-stuck-on-estimating
https://askubuntu.com/questions/1062427/18-04-battery-charge-indicator-doesnt-reflect-state-of-charge
https://askubuntu.com/questions/76256/lubuntu-battery-monitor-always-says-100
https://askubuntu.com/questions/543508/indicator-power-stuck-on-the-first-value-after-logining
https://askubuntu.com/questions/587063/battery-indicator-always-says-using-battery-power-even-when-plugged-in-asus
https://askubuntu.com/questions/7205/battery-indicator-is-stuck-on-estimating
https://askubuntu.com/questions/922139/battery-shows-always-charging-even-its-not-plugged-in
https://askubuntu.com/questions/894023/battery-is-stuck-on-estimating/989607#989607
https://forums.linuxmint.com/viewtopic.php?t=251095
https://forums.linuxmint.com/viewtopic.php?t=65667
https://github.com/linuxmint/Cinnamon/issues/4925
https://arstechnica.com/civis/viewtopic.php?f=16&t=432885
https://forum.mxlinux.org/viewtopic.php?t=48113
https://bbs.archlinux.org/viewtopic.php?id=167767
https://romaco.ca/blog/2011/01/28/fix-that-annoying-laptop-battery-estimating-in-ubuntu/
https://www.reddit.com/r/archlinux/comments/5p7622/gnome_battery_indicator_is_stuck_on_estimating/
https://www.reddit.com/r/cloudready/comments/a3tnw5/battery_indicator_stuck_at_100/"
1824886,2019-04-17 00:09:45 UTC,"I attached journalctl from Ubuntu in the Ubuntu_debug.log file. If this is not what you need - teach me how to do it.
Screenshots made in Linux Mint. gnome-control-center shows the correct status only Linux Mint (and Windows)."
1824886,2019-04-17 11:00:37 UTC,"$ cat /sys/class/power_supply/BAT0/charge*
4200000
4300000
4200000"
1824887,2019-04-15 22:07:43 UTC,Related: https://bugs.launchpad.net/juju/+bug/1712269
1824887,2019-09-20 10:06:18 UTC,Is this moving into won't fix or do we know what this would look like? Is it just allow macaroons for sub resources?
1824888,2019-04-15 22:26:43 UTC,The error in your logs is:
1824888,2019-06-15 04:17:49 UTC,[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]
1824893,2019-09-30 07:42:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824893,2019-07-10 21:04:40 UTC,"Tried the most recent proposed kernel, 5.2.0-8 today, still gets stuck at the target reboot reached.
Not a huge deal at this point as the magic-sys-request is working so I can at least force the reboot from the keyboard at that point."
1824893,2019-04-25 08:55:48 UTC,"      I could not find what was going wrong with update-grub2, it showed it
doing the right thing but did not alter the boot screen.  I purged grub and
all it's configuration from my workstation then re-installed, now it is
working again."
1824893,2019-04-23 08:54:37 UTC,"      Actually there was petiboot which I never did get successfully working.
Wanted to be able to kexec-boot because the BIOS in this old Mac is so very
painfully slow."
1824893,2019-04-23 08:50:32 UTC,"      Grub and Grub2 are installed, no others, not lilo, etc.  I do not know
WHERE it is finding 5.0.9 at, no remnants in the boot, modules, initramfs
directories."
1824893,2019-04-23 08:03:12 UTC,Does the system have boot loader other than GRUB installed?
1824893,2019-04-23 07:44:54 UTC,"      Well I've managed to screw up my machine massively and don't know how
to get it back to a sane state."
1824893,2019-04-23 05:12:05 UTC,"Prebuilt binaries can be found here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/"
1824893,2019-04-22 02:50:57 UTC,"If this doesn't happen to v4.15, please run a kernel bisection to find the regression commit."
1824893,2019-04-18 09:49:25 UTC,"      Yes.  It has been an issue for a while.  It was a problem with 16.04,
16.10, fixed in 17.04, 17.10, 18.04, broken again in 18.10 and 19.04.  Since
I installed the development release I thought I'd try to get to the bottom
of it this time around."
1824893,2019-04-18 09:38:13 UTC,It can be a kernel bug. Do you see this issue if the system boots under kernel v4.18?
1824893,2019-04-17 07:34:46 UTC,"     Yes, I've deleted the failing packages, game servers, debomatic, etc,
or in one case masked it so systemd should not try to run it."
1824893,2019-04-17 06:27:21 UTC,see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachment/5256102/+files/SystemdFailedUnits.txt
1824893,2019-04-17 02:35:04 UTC,"      Sorry, which faulty units are those?"
1824893,2019-04-16 14:23:23 UTC,"Thanks, I don't see anything obvious in the log, setting as New again for now (would be good to see if removing the faulty units pointed in the previous comment makes a difference though)"
1824893,2019-04-16 08:49:56 UTC,Thank you for your bug report. Could you attach your journalctl log from that shutdown to the bug?
1824893,2019-04-23 04:38:21 UTC,"      I'm going to need a bit of help with respect to where to find old
canonical kernel packages so I can find at what point it broke exactly."
1824893,2019-04-16 12:18:49 UTC,"      I've added the last 250 lines of the log, if that's not enough let me
know.  Once it says it's reached target reboot the next thing it does is
send a kill signal to all processes, including journalctl so there is not
much useful information beyond that point.  Also I can not switch virtual
terminals at that point, no keyboard input has any effects at that point
including magic sys req key."
1824894,2019-06-15 04:17:52 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1824894,2019-04-16 03:36:43 UTC,"> 2. There are some .crash files but these look unrelated based on
timestamps.
"
1824894,2019-04-16 03:20:20 UTC,"Sorry, CORRECTION* 3. I have NOT shut down or reset after recovering from
my last crash."
1824894,2019-04-16 03:00:05 UTC,"1. When the problem happens, can you still move the mouse pointer?"
1824894,2019-04-16 03:19:25 UTC,"1. I cannot move my mouse pointer.
2. There are some .crash files but these look unrelated based on
timestamps. I've included a screenshot of the files that I have. If you
would like me to send them I would be more then happy to.
[image: Screenshot from 2019-04-15 21-16-05.png]
3. Here is my last prevboot.txt I have shut down or reset after recovering
from my last crash. Not sure if this is useful or not, but I'll be sure to
send the next one."
1824897,2019-04-16 00:01:36 UTC,"This is another file that produces the error when exporting the top silk layer. The layout will export successfully if enough holes are removed, but there does not appear to be any specific set of holes responsible for the error. Any sufficiently small subset of holes will export correctly, but sufficient combinations of holes will produce the error."
1824897,2019-04-16 12:30:47 UTC,Hi Charles-
1824897,2019-04-16 22:31:32 UTC,These were both generated from some python script I wrote. The first one was generated mathematically from just the code. The silkscreen-only one was parsed out of an SVG file.
1824904,2020-02-08 10:32:41 UTC,"Backtrace is the same as in https://github.com/mate-desktop/caja/issues/1046
The stop_cb callback is from libgioremote-volume-monitor.so (part of gvfs)"
1824905,2019-04-16 00:19:46 UTC,"This is an installer issue, not a ubuntu-release-upgrader issue.  However I could not get Launchpad to accept this bug any otherway."
1824905,2021-01-09 03:14:23 UTC,This bug was fixed in the package ubiquity - 21.04.4
1824905,2020-10-13 15:21:06 UTC,"However, we also discussed that we might not need to install those things in the live system."
1824905,2019-04-17 10:35:03 UTC,Hitting the same issue with Dell Precision device and the latest 19.04 RC image (0416).
1824905,2020-12-11 11:26:54 UTC,This is now merged into lp:ubiquity. We should have it released with the next ubiquity upload.
1824905,2019-04-16 17:22:50 UTC,"@FranksMCB - ""This is an installer issue, not a ubuntu-release-upgrader issue. However I could not get Launchpad to accept this bug any otherway."""
1824905,2019-04-16 08:22:39 UTC,"This is because ubuntu-drivers refreshes it's cache to check for drivers to install and install drivers on the system is there are any available.
The UI should indeed provide some feedback when it's doing this."
1824905,2019-04-16 08:20:58 UTC,"Would it be possible to get the installer logs (syslog, journal, ubiquity logging etc.) for when such a situation is happening? Is it only reproducible with selected hardware?"
1824905,2019-04-16 08:00:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1824905,2019-04-16 00:25:44 UTC,"I am experiencing this issue with dailies images for Ubuntu, Kubuntu, Xubuntu, Ubuntu MATE and Ubuntu Budgie when installing on a laptop with integrated discrete nvidia graphics."
1824905,2019-04-16 00:21:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824905,2019-04-16 17:59:16 UTC,"After install.  Alt-F2 and ran ubuntu-bug.  That brought up the Apport
screen with the options to select different problems to report.  Checked
Other problem and Got ""You need to specify a package or a PID. See
--help for more information."""
1824905,2019-04-17 10:51:04 UTC,In last case the download from archive.ubuntu.com is very slow and represents most of the 6 minutes
1824913,2019-04-16 11:10:45 UTC,I've prepared -- and just uploaded to Debian unstable -- version 1.9.0-2 which builds cleanly on Bionic without a need for backporting patches.
1824913,2019-04-23 13:26:44 UTC,"Imports from Debian being enabled again, 1.9.0-2 is now in Eoan, built with tests passing."
1824913,2019-10-23 06:40:41 UTC,1.9.0 in eoan
1824914,2019-04-16 11:16:50 UTC,"QFX file format is handled by 3rd party libofx library (not developped, supported by me)"
1824914,2019-04-16 15:29:50 UTC,The output from ofxdump indicates that the file format isn't supported:
1824914,2019-04-20 17:49:01 UTC,"yes I know about the lack of a scrollbar, which is a GTK problem for the moment.
HomeBank uses a native assistant GTk+ class, and they did not consider a scrollbar may be required here. SO at a point I maybe should migrate to my own assistant class."
1824914,2020-10-10 17:02:33 UTC,"this will hopefully chnage with GTK4
if not this could be reopened"
1824920,2020-06-29 08:52:40 UTC,Thank you for reporting this bug to Ubuntu.
1824920,2019-04-16 04:00:04 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1824920,2019-04-16 18:16:21 UTC,This really needs to be a bug against https://launchpad.net/ubuntu-manual-tests
1824920,2020-08-29 04:17:19 UTC,[Expired for light-locker (Ubuntu) because there has been no activity for 60 days.]
1824921,2019-04-16 12:24:07 UTC,From the logs:
1824921,2019-06-14 13:53:34 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1824925,2020-05-10 08:15:48 UTC,I ran into the same problem with sbcl-1.2.7 on Solaris 10 too. I was able to get past the problem by using sbcl-1.0.23 to build sbcl-2.0.2.
1824928,2019-07-14 01:34:27 UTC,Fixed in r1083 https://bazaar.launchpad.net/~armagetronad-ap/armagetronad/0.2.9-armagetronad-sty+ct+ap/revision/1083
1824933,2019-04-16 05:58:55 UTC,"SunOS 5.10 Generic_118833-33 sun4v sparc SUNW,Sun-Fire-T200"
1824933,2019-04-16 07:04:47 UTC,fixed by https://sourceforge.net/p/sbcl/sbcl/ci/b97e10661ea1335db7882d3696b19dc5aa185b71/
1824948,2019-04-16 13:28:20 UTC,"https://review.openstack.org/#/c/627941/ is the first step in getting rbd incremental backup working better in general, and will likely help with this."
1824948,2019-04-18 07:06:22 UTC,"In incremental backup， parent_id always specifies latest_backup. While，the latest_backup can not be remove until all the subsequent backups has been removed.
This is not appropriate in some situation, such as auto remove some old backups."
1824948,2019-10-15 11:57:18 UTC,It seems that the backup driver sets the parent_id falsely to the previous backup instead of the actual base.
1824951,2019-07-02 17:18:36 UTC,After a fresh installed with OSA at 18.1.4 keepalived is disabled and need to enabled manual:
1824952,2020-01-01 16:56:07 UTC,For record with https://github.com/containers/buildah/commit/c0633e38da4134135d35d32b56194790ca8acecd it was completely fixed for both dangling and non dangling symlink. So buildah-1.8.3 is needed.
1824952,2019-07-29 17:19:09 UTC,buildah-1.8.1 which contain the fix is in both stein and master delorean deps repo. Closing the bug.
1824952,2019-04-30 02:56:05 UTC,"The issue is fixed in buildah master with PR:- https://github.com/containers/buildah/pull/1558, now we need a new release and build for buildah."
1824952,2019-06-03 12:26:47 UTC,can be moved to fix released?
1824952,2019-04-16 12:24:51 UTC,The fix is likely going to be https://github.com/containers/buildah/pull/1443
1824952,2019-04-16 12:18:02 UTC,The issue is already reported in buildah:- https://github.com/containers/buildah/issues/1439
1824952,2019-06-03 12:47:24 UTC,"Yes can be closed, as buildah-1.8.1 with the fix is in master and stein where buildah jobs are running."
1824953,2019-04-16 07:30:07 UTC,This change was made by a bot.
1824953,2019-04-17 12:13:28 UTC,There should have been some output about the triggers involved in the loop; did you capture that? If not you might find it in /var/log/apt/term.log.
1824953,2019-04-17 14:04:38 UTC,"dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  libgtk2.0-0:amd64 -> libc-bin
 packages' pending triggers which are or may be unresolvable:
  linux-image-5.0.0-11-generic: linux-update-5.0.0-11-generic
  install-info: /usr/share/info
  sgml-base: /usr/share/xml: update-sgmlcatalog: /etc/sgml: /usr/share/sgml
  shared-mime-info: /usr/share/mime/packages
  dbus: /etc/dbus-1/system.d
  ca-certificates: update-ca-certificates
  systemd: /etc/init.d
  libc-bin: ldconfig
  libgtk2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules
  dictionaries-common: update-default-ispell: update-default-wordlist: aspell-autobuildhash
  cups: /usr/share/cups/ppd-updaters
  hicolor-icon-theme: /usr/share/icons/hicolor
  initramfs-tools: update-initramfs
  mime-support: /usr/share/applications: /usr/lib/mime/packages
dpkg: error processing package linux-image-5.0.0-11-generic (--configure):
 triggers looping, abandoned"
1824953,2019-06-17 04:17:39 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1824959,2019-06-12 14:43:42 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1824959,2019-06-03 01:43:37 UTC,"Change abandoned by pengyuesheng (<email address hidden>) on branch: stable/pike
Review: https://review.opendev.org/662369"
1824959,2019-06-05 12:57:20 UTC,"Reviewed:  https://review.opendev.org/652938
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=c81af496cffa7cc24ee95f388d57ef509704b08d
Submitter: Zuul
Branch:    master"
1824959,2019-04-16 08:06:43 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/652938"
1824959,2019-05-31 01:20:27 UTC,"Change abandoned by pengyuesheng (<email address hidden>) on branch: master
Review: https://review.opendev.org/652938
Reason: I will submit the bug to the pike branch."
1824959,2019-06-02 06:55:50 UTC,"Generally speaking, you should avoid proposing a fix to a stable branch directly."
1824961,2019-04-16 11:03:39 UTC,Reassigning to the kopanocore package as that is what contains the problematic profile.
1824961,2019-04-16 11:04:42 UTC,Do you have any examples of the denials it is hitting?
1824961,2019-04-16 11:25:53 UTC,"This is specifically not a kopanocore issue, but an issue with all Python programs that have an AppArmor profile. Patching each of them to allow Apport to run vs. the Python abstraction would make no sense."
1824961,2019-04-16 11:27:51 UTC,"I don't have any examples atm, but we know it tries to read cputable at least:"
1824961,2019-04-16 12:46:52 UTC,"Traditionally we have actually put these accesses in the packages that ship the profile, like Marc said, because profilers may not want the profile to automatically have everything apport requires. These accesses should *not* be in the python abstraction because the accesses have nothing to do with python applications, they have to do with python applications with apport hooks that are confined with apparmor."
1824961,2019-04-16 12:52:54 UTC,I might also mention on IRC the exact type of thing why we've had these rules in the profile that ship them:
1824961,2019-04-16 14:47:26 UTC,"> they have to do with python applications with apport hooks that are confined with apparmor.
"
1824961,2019-04-16 19:21:17 UTC,"""I guess the question is: Shouldn't we have a python-apport abstraction that apps (or local admin) can include to make debugging work under apparmor? It should probably live in apport, I guess, so apport can define which files it needs."""
1824966,2019-04-17 09:40:37 UTC,"Fixed in stable r18928 (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18928) by a commit, but not testable."
1824966,2019-04-18 15:11:52 UTC,"This doesn't appear to have worked.  eoan init didn't populate any post-release pockets, as far as I can tell."
1824967,2019-05-27 23:17:30 UTC,"Fixed in revision 27d097a78c7340d9ddebb4acc00c2b283441031c
https://git.launchpad.net/kicad/patch/?id=27d097a78c7340d9ddebb4acc00c2b283441031c"
1824967,2019-05-24 19:33:00 UTC,"This makes me nervous, but AFAICT it doesn't break anything."
1824967,2019-04-19 12:27:15 UTC,"Also occurs with ""Free angle mode (no shove/walkaround)""."
1824969,2019-04-16 12:39:28 UTC,Thank you for your bug report. Do you have steps that can be used to trigger the issue?
1824969,2019-04-16 12:51:15 UTC,it's exactly the same procedure has describe in Debian bug.
1824969,2019-04-16 13:45:58 UTC,"I just see the fix is committed, when will we see it ?"
1824969,2019-04-25 06:35:47 UTC,when you say next cycle it's version 19.04 or something else ? like 19.10 ?
1824969,2019-04-16 14:19:28 UTC,It's commited upstream and in Debian so we will get it when next Ubuntu cycle start. Then we can look at doing a SRU but for that we need a testcase which can be used to verify the SRU (and ideally which doesn't require buying hardware like an yubikey)
1824970,2019-04-16 12:29:26 UTC,"The attachment ""corrected english.xml file"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1824970,2019-05-05 08:22:00 UTC,"Thanks a lot Damiano, I updated the .xml.
Best regards."
1824973,2019-04-16 12:39:26 UTC,This is an annoying thing that has existed for a while.
1824973,2019-04-16 21:06:36 UTC,KiCad is not really designed to run multiple sessions at a time.  You should have seen a warning dialog that KiCad is already open.  Ignore that at your own peril.  Maybe in the future will will change to a multiple project interface but for the foreseeable future KiCad will have a single project interface.
1824973,2019-04-16 21:19:33 UTC,"On 4/16/19 5:06 PM, Wayne Stambaugh wrote:

> KiCad is not really designed to run multiple sessions at a time.  You
> should have seen a warning dialog that KiCad is already open.  Ignore
> that at your own peril.  Maybe in the future will will change to a


                                            ^^ we ^^

> multiple project interface but for the foreseeable future KiCad will
> have a single project interface.
>
> ** Changed in: kicad
>     Milestone: 5.1.2 => None
>
"
1824973,2019-04-17 14:36:44 UTC,"On 4/16/19 5:06 PM, Wayne Stambaugh wrote:

> KiCad is not really designed to run multiple sessions at a time.
"
1824974,2019-04-17 14:09:14 UTC,"I know about how that periodic can hit a failure for one instance which blows the whole task for all of them on that same host, similar to bug 1662867:"
1824974,2019-04-17 14:19:27 UTC,Note that this would fix your issue https://review.openstack.org/#/c/571410/.
1824975,2019-04-16 10:26:15 UTC,Except one (I believe arm64 which failed during setup) all fail because they cannot find a go binary.
1824975,2019-10-16 05:45:58 UTC,"We reworked how we run autopkgtests in 2.39, this  should no longer be an issue."
1824976,2020-04-22 21:45:44 UTC,"Thanks, just fixed in https://discourse.ubuntu.com/t/service-ldap-with-tls/11578"
1824979,2019-05-16 09:15:07 UTC,"The verification of the Stable Release Update for mariadb-10.1 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1824979,2019-05-10 13:40:40 UTC,autopkgtests now pass for all archs
1824979,2019-05-16 09:15:03 UTC,This bug was fixed in the package mariadb-10.1 - 1:10.1.38-0ubuntu0.18.10.2
1824979,2019-04-25 13:23:45 UTC,"Hello Dan, or anyone else affected,"
1824979,2019-04-16 11:26:19 UTC,"For context, mariadb-10.1 in Bionic has seen regular updates, including for security issues, while mariadb-10.1 in Cosmic has not had any released updates at all."
1824979,2019-04-29 11:17:20 UTC,"autopkgtest regressions noted in the other bug for this upload, bug 1824335"
1824979,2019-05-09 13:49:59 UTC,"Hello Dan, or anyone else affected,"
1824979,2019-04-16 14:50:46 UTC,"Since the package contains additional fixes and packaging changes, it is not appropriate to go directly to -security. Please go through the SRU process first. Thanks!"
1824982,2019-04-16 13:59:07 UTC,"Thanks for quick response!
It saves me a lot of effort :)"
1824982,2019-04-29 13:29:12 UTC,Monasca support in Rocky is addressed by the following two patch chains:
1824982,2019-06-06 15:19:25 UTC,The two patch chains above have now been merged into stable/rocky. This completes the backport of Monasca to rocky.
1824982,2019-04-16 11:43:34 UTC,"After fixing this, i have problem with kafka input."
1824982,2019-04-16 12:42:57 UTC,"Grzegorz Bialas, Monasca is tied to Logstash 2.4 at the moment. The work to add it to Kolla was not completed in the Rocky cycle. In other words, Monasca support is not finished in Rocky."
1824986,2019-04-16 13:02:26 UTC,And I have /home and /tmp mounted with noexec.
1824986,2019-07-15 17:25:06 UTC,"Hi, Twinkle upstream co-maintainer here.  If you could, please open an issue on our GitHub tracker[1], along with a backtrace[2].  (The strace attachment was appreciated, but it didn't really help in this case, unfortunately.)  Thanks!"
1824986,2019-07-15 23:15:53 UTC,Thank you very much for the backtrace.
1824986,2019-07-16 10:13:13 UTC,"Thank YOU, tremendous super cosmo-heroes."
1824986,2019-07-16 10:31:12 UTC,The previous gdb was with qt 5.9.5+dfsg-0ubuntu2.1 from ubuntu-security. This one is with qt 5.9.5+dfsg-0ubuntu2.3 from proposed updates.
1824986,2019-07-16 13:32:08 UTC,Hi Dima!
1824986,2019-07-18 05:10:41 UTC,"Yes, this does help. Thank you."
1824986,2019-07-18 12:49:50 UTC,"Thanks for confirming, adjusting the bug status accordingly."
1824986,2019-07-15 21:15:03 UTC,https://github.com/LubosD/twinkle/issues/157
1824987,2020-05-27 18:32:48 UTC,https://review.opendev.org/#/c/717381/1 also should cover that specific issue. Marking as resolved
1824987,2019-09-18 01:10:12 UTC,Also happens on Ubuntu 16.04.  I was running a Rocky to Stein upgrade and ran into this. Had to install the python2 version in my case(python-pymysql) but otherwise same behavior.
1824987,2019-09-25 07:58:56 UTC,"Working on it, it first needs to be fixed in the openstack-ansible-galera_server:"
1824990,2019-05-25 16:25:36 UTC,"Fixed in Eoan
---"
1824990,2019-06-25 16:43:41 UTC,Uploaded to Disco.
1824990,2019-07-27 04:07:40 UTC,This bug was fixed in the package kylin-nm - 1.0.0-1ubuntu0.1
1824990,2019-04-20 21:34:21 UTC,"Hello handsome_feng, thanks for your work on this!"
1824993,2019-08-29 17:26:50 UTC,WORKAROUND
1824995,2019-05-17 15:19:02 UTC,This is an issue in the documentation https://docs.openstack.org/openstack-helm/latest/install/developer/deploy-with-ceph.html.
1824998,2019-04-24 09:29:24 UTC,I consider this problem solved as the problem was notified to Lubomir Rintel. He said he will be more careful in the future.
1824998,2019-04-18 20:17:26 UTC,Okay done...
1824998,2019-04-18 11:55:26 UTC,Yes I am. But I translated master and Ubuntu is using branch 1.16
1824998,2019-04-18 09:49:28 UTC,Note this is fixing only the conflicting strings and not the pull from Red Hat translators.
1824998,2019-04-18 09:45:02 UTC,"I saw your comment :)
I sent a merge request upstream and was approved.
Hopefully I don't have to fix hundreds of Zanata strings again."
1824998,2019-04-18 08:35:22 UTC,"It's an upstream issue, those strings are buggy in git as well, I commented back on gitlab"
1824998,2019-04-17 14:16:44 UTC,"Yes, the string is upstream.
Yes, upstream was importing errors from Red Hat translators. I think is related with the Copy Trans feaure of Zanata.
I reported this issue upstream a few minutes after reporting in Launchpad and here is his reply:"
1824998,2019-04-17 10:29:34 UTC,"Thank you for your bug report, is the string in the upstream tarball? Could you explain what is happening exactly, is upstream important from fedora with those errors? Does upstream know about the issue?"
1824998,2019-04-18 11:36:55 UTC,"Thanks, not that you can also uploadf the .po to launchpad if you want to update the strings there (if you are part of the spanish translators team on launchpad)"
1825000,2020-08-18 16:48:00 UTC,"eoan has reached end of life, so this bug will not be fixed for that release"
1825000,2020-04-14 08:07:48 UTC,This bug was fixed in the package apt - 2.0.2
1825000,2020-04-02 14:24:34 UTC,Note that there were some I think somewhat valid privacy concerns to exposing the service name.
1825000,2020-04-02 15:01:41 UTC,"I think ""User-Agent: Debian APT-HTTP/1.3 (2.0.1) non-interactive"" would be enough."
1825000,2020-03-26 07:09:23 UTC,Probably ! What is it going to be for interactive uses though ?
1825000,2020-03-25 16:59:27 UTC,The attached merge proposal adds the name of the systemd unit that we are running under to the HTTP User-Agent field. Is that sufficient?
1825000,2020-03-25 16:58:28 UTC,https://salsa.debian.org/apt-team/apt/-/merge_requests/114
1825000,2019-06-06 15:55:07 UTC,"So, I think we want to do that for apt-daily.service which does the downloading of package lists and updates; but not for the actual upgrade job - which might fetch any remaining packages."
1825000,2019-06-06 15:54:35 UTC,"/usr/lib/apt/apt.systemd.daily should force set a Useragent apt.systemd.daily, for all operations."
1825000,2019-04-16 14:54:57 UTC,Obviously this may be equally relevant to unattended-upgrades.
1825000,2020-04-02 14:22:25 UTC,"Well, nothing, absence of service is interactive?"
1825001,2019-06-06 15:43:40 UTC,Seems my comment refers to the separate bug https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000
1825001,2019-04-16 15:50:55 UTC,apt currently considers the following errors transient:
1825001,2019-04-16 15:54:02 UTC,"FWIW, over capacity should be 503 usually, not a 4xx response code."
1825001,2019-06-06 15:41:50 UTC,"From my discussions in person at the last sprint, it would be useful to have User-Agent information that lets the server distinguish between interactive vs non-interactive clients (i.e.: unattended-upgrades) in order to tell u-u to go away and try later for cases when the server / Internet connection are saturated and delivering a poor QoS to all users due to events."
1825001,2019-04-16 15:55:29 UTC,"503 also has a Retry-After field that you can use to communicate when to retry, although we do not have any support for retrying things, apart from twice a day, as systemd does not offer this ability to our type of timer. And for interactive use, well, the user will retry manually."
1825002,2019-04-16 16:45:17 UTC,The check in target_cpu_copy_regs at linux-user/mips/cpu_loop.c:776 Is reading an uninitialized value:
1825002,2019-07-18 14:55:07 UTC,A fix for this was committed as abcac736c1505254ec3 and will be in the upcoming 4.1 release.
1825002,2019-04-24 13:34:30 UTC,"Fix posted on the list:
https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg04037.html"
1825002,2019-04-17 20:19:59 UTC,"This is certainly a bug, but it's not a a CVE, ie not a security bug. The entire purpose of the linux-user mode is to run the guest ELF file and let it perform whatever syscalls it likes -- it doesn't need to exploit any kind of bug in the ELF loader to be able to control what the process is doing."
1825002,2019-04-17 20:49:25 UTC,"Thanks Peter.  I was just reading up on the CVE process and I agree.  Obviously, it's dangerous to use uninitialized values, but that doesn't necessarily make it a vulnerability."
1825002,2019-04-17 14:17:19 UTC,"Actually, this is a better patch.  Let's sanitize struct image_info interp_info."
1825002,2019-04-17 14:15:26 UTC,Please send patches to the mailing list for inclusion. QEMU maintainers normally don't take patches from the bug tracker. See https://wiki.qemu.org/Contribute/SubmitAPatch
1825002,2019-04-17 13:47:01 UTC,"In load_elf_binary (linux-user/elfload.c b/linux-user/elfload.c:2644) the entire interp_info struct should be inited, I would call this a CVE.  At a very minimum, init the fp_abi field so we don't use whatever happened to be on the stack for the FPU mode should the ELF header not specify otherwise."
1825002,2019-04-17 20:49:46 UTC,And thank you Thomas for the instructions!
1825003,2019-04-16 16:00:05 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1825006,2019-04-16 15:16:10 UTC,the right package I think is : gnome-software-plugin-snap
1825006,2019-04-17 10:27:15 UTC,"Thank you for your bug report. Where are they not listed? Could you make a screenshot showing the issue?
What version of Ubuntu & gnome-software do you use?"
1825006,2019-04-17 10:44:21 UTC,"I use ubuntu 18.04.2 LTS, with default gnome-desktop."
1825006,2019-04-17 12:35:45 UTC,Where did you click to get the list from the first screenshot?
1825006,2019-04-17 13:02:53 UTC,"I think that ""Strumenti di sviluppo"" is ""Development tools"" in english."
1825006,2019-06-17 04:17:38 UTC,[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.]
1825007,2019-05-22 14:21:54 UTC,"This bug is believed to be fixed in curtin in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1825007,2019-04-23 16:08:31 UTC,This bug was fixed in the package curtin - 18.2-26-gd8e45d79-0ubuntu1
1825007,2019-04-17 14:47:15 UTC,"This bug is fixed with commit 309e76d8 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=309e76d8"
1825007,2019-04-16 15:24:57 UTC,"Thanks,  looks like python3.7 subprocess.Popen.communicate helpfully converts str to bytes, however that hid the bug when I tested this path on s390x disco."
1825010,2019-04-18 14:31:44 UTC,"juju plugin bug:
https://github.com/sosreport/sos/issues/1653"
1825010,2019-12-13 15:34:16 UTC,"There is currently an upstream discussion about a potential new sosreport (v3,9) release before Focal Freeze schedule (Feb 27th)."
1825010,2019-11-12 11:24:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825010,2019-09-16 14:42:49 UTC,sosreport 3.8 have been accepted into debian unstable.
1825010,2019-10-25 18:50:26 UTC,This bug was fixed in the package sosreport - 3.8-1ubuntu1
1825010,2019-08-27 18:10:42 UTC,"sosreport 3.8 has been released earlier today:
https://github.com/sosreport/sos/releases/tag/3.8"
1825010,2019-05-13 23:22:42 UTC,"@David Negreira, I want to make sure the runuser approach works before officially starting the SRU for this."
1825010,2019-05-13 23:19:31 UTC,"@David Negreira, can you test your refactoring plugin with 'runuser -u juju-user -P <COMMAND>' ?"
1825010,2019-05-13 23:14:52 UTC,Before pushing the sosreport v3.7 into Debian and Ubuntu. There is a couple of things that I want to see being merge upstream. The most important part is the refactoring of the juju plugin.
1825010,2019-04-26 20:05:55 UTC,"debbug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928049"
1825010,2019-09-09 17:32:28 UTC,"Debian/sosreport 3.8 has been uploaded into mentor debian, waiting for sponsorship:
https://mentors.debian.net/package/sosreport"
1825011,2019-04-17 09:19:10 UTC,"False alarm this later config actually make it, just seems that there was some hicups in the node
to get the ephemeral OS booting to run the curtin, but the node is currently deployed with one efi
raw fat partition, one empty fat on the second disk, and a raid on top using the second partition
of any node."
1825011,2020-05-01 20:08:58 UTC,"We recently landed code to enable grub2 in ubuntu to keep multiple ESPs in-sync.  with this in place, one can now supported multiple ESPs, and example config used is here:"
1825011,2019-09-25 08:52:35 UTC,"Marking this as invalid, since EFI doesn't really support software raid, and there's not much MAAS can do about it."
1825011,2019-04-17 07:52:21 UTC,"Ok, to remove the firmware variable from the bug, I'm trying right
now this config:"
1825011,2019-04-16 17:25:49 UTC,"mmmm... In my case it doesn't make it, can I ask why your example have
one disk using dos partition, and one using gpt?"
1825011,2019-04-16 18:59:54 UTC,"I'm marking this as triaged  as I understand the scenario, I've outlined that there is work to do make this work and it needs validation to ensure things are reliable.  Some elements are out of our control w.r.t how Firmware treats a raided partition."
1825011,2019-04-16 18:55:48 UTC,"I see now, you're attempting to mirror /boot/efi; that's not a support configuration.  The general issues are:"
1825011,2019-04-16 17:57:34 UTC,"That looks like a cut-n-paste error.  I'll fix that, thanks."
1825011,2019-04-16 17:22:51 UTC,Please provide the data requested here:
1825011,2019-04-16 16:42:00 UTC,This likely will be resolved with an updated config.  Please let me know if those suggested changes resolve your boot issue.
1825011,2019-04-16 16:41:05 UTC,"Hi,"
1825011,2019-04-17 06:26:38 UTC,"These are dell poweredge c4130, so perhaps we can get better insight on
the firmware support."
1825014,2020-04-14 11:34:16 UTC,Fixed in launchpadlib 1.10.11.  Thanks for the contribution.
1825016,2019-05-17 15:32:04 UTC,"Reviewed:  https://review.opendev.org/659241
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=3a15dd83494341d754b261e937a7354b191f6a00
Submitter: Zuul
Branch:    master"
1825016,2019-05-15 08:53:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659241"
1825016,2019-05-03 14:38:13 UTC,"Reviewed:  https://review.opendev.org/655641
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=089823288a23d73f2c86f9dd261b3d3ff9cebfea
Submitter: Zuul
Branch:    master"
1825016,2019-04-25 09:34:43 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/655641"
1825016,2019-04-17 12:19:34 UTC,There is a section-oslo-notifications [0] section in the template of nova.conf [1] which should do exactly what you are looking for I guess. I'm trying to figure out the right config.
1825016,2019-04-19 13:32:29 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653945"
1825016,2019-05-03 14:38:20 UTC,"Reviewed:  https://review.opendev.org/653945
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=599245bbd16bb986e43d753857e73da2555fc77b
Submitter: Zuul
Branch:    master"
1825017,2019-04-16 16:58:37 UTC,"Hi,"
1825017,2019-04-18 06:39:10 UTC,"Hi,"
1825017,2019-04-18 06:56:14 UTC,"Looks like this is a plotting issue.
Do you have the HePMC output?
What is the pythia8 log?"
1825017,2019-04-18 08:40:22 UTC,I don't have the HePMC output. I am attaching the log file.
1825017,2019-04-18 08:55:55 UTC,"Looks like a environment variable set up a wrong directory for PY8 to find the file related to his settings.
But I do not know PY8 enough to give you more details, you should ask a PY8 author about that."
1825018,2020-02-25 12:13:15 UTC,This issue was fixed in the openstack/nova 18.3.0 release.
1825018,2020-02-06 12:45:13 UTC,This issue was fixed in the openstack/nova 19.1.0 release.
1825018,2020-02-06 12:40:44 UTC,This issue was fixed in the openstack/nova 20.1.0 release.
1825018,2020-01-16 19:22:08 UTC,"Reviewed:  https://review.opendev.org/697505
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=179b556a5bebb8c5810b6065cd992a0a81bf288c
Submitter: Zuul
Branch:    stable/rocky"
1825018,2019-12-20 19:58:57 UTC,"Reviewed:  https://review.opendev.org/697480
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=99048af872743638b3628555e96351e00bf1eb7e
Submitter: Zuul
Branch:    stable/stein"
1825018,2019-12-05 15:39:58 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/697505"
1825018,2019-12-05 14:25:48 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/697480"
1825018,2019-12-05 14:03:08 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/697475"
1825018,2019-12-05 01:24:39 UTC,"Reviewed:  https://review.opendev.org/697122
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0461921d9e5313c3e92b039b90f713ed961e20c8
Submitter: Zuul
Branch:    master"
1825018,2019-12-03 15:57:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/697122"
1825018,2019-12-18 09:25:09 UTC,"Reviewed:  https://review.opendev.org/697475
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3ea6a7f79b0ad8a12c8ccfdeda838784c7922e63
Submitter: Zuul
Branch:    stable/train"
1825019,2019-04-18 21:10:21 UTC,Pretty sure this is fixed.  (There were a bunch of changes in that area and I can't reproduce it.)
1825020,2019-09-27 09:04:30 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1825020,2019-06-06 06:24:18 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1825020,2019-05-02 19:48:39 UTC,"Reviewed:  https://review.opendev.org/656666
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3285210add2758ad0182358317fabca626cdb0ee
Submitter: Zuul
Branch:    stable/stein"
1825020,2019-05-02 18:17:22 UTC,"Reviewed:  https://review.opendev.org/656511
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a1db4507ac832913a911afbee90f76f576d8ea20
Submitter: Zuul
Branch:    stable/stein"
1825020,2019-05-01 16:17:31 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656666"
1825020,2019-04-30 13:23:47 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/656511"
1825020,2019-04-29 19:59:10 UTC,"Reviewed:  https://review.opendev.org/653268
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a40c7f3e8d06f0bc8918a25b60f73ec2c18add05
Submitter: Zuul
Branch:    master"
1825020,2019-04-17 04:02:16 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653273"
1825020,2019-04-17 03:23:57 UTC,My fix is hitting a side effect of bug 1646740 where the min_disk stored in the image metadata for the server is based on the flavor root_gb rather than the volume size...
1825020,2019-04-17 03:16:28 UTC,"Hmm, even by passing the root_bdm to _validate_flavor_image_nostatus it can fail with VolumeSmallerThanMinDisk if the volume_size is smaller than the min_disk size of the backing image."
1825020,2019-05-01 15:17:24 UTC,"Reviewed:  https://review.opendev.org/653273
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8aae3e39e58a05ed50b891aeae261641f544ad1f
Submitter: Zuul
Branch:    master"
1825020,2019-04-17 03:10:10 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653268"
1825020,2019-04-17 00:25:47 UTC,Are you sure this is reproducible in pure nova code? Because this looks like forked nova code for starlingx:
1825022,2019-05-20 17:39:27 UTC,"Can mostly confirm in 3.1.10. I've replicated all reported inconsistencies except the template drop down in the volume/copy editor does NOT have a scrollbar as reported, so entire screen scrolls."
1825022,2019-05-20 19:28:24 UTC,"This bug may overlap some with bug 1669120 (fix committed, which changes the height of the ""scrollable-menu"" CSS class)."
1825025,2020-04-15 21:24:20 UTC,"Maybe there's an equivalent setting to?

> console-setup   console-setup/store_defaults_in_debconf_db      boolean false
"
1825025,2019-04-23 12:25:57 UTC,apport information
1825025,2019-04-23 12:25:58 UTC,apport information
1825025,2019-04-23 12:25:56 UTC,apport information
1825025,2019-04-23 09:47:13 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1825025,2019-06-23 04:18:17 UTC,[Expired for ldap-auth-client (Ubuntu) because there has been no activity for 60 days.]
1825027,2019-07-18 21:16:46 UTC,"Hi, thanks for the bug.  We generally want to avoid running any tests as root so as not to modify anything sensitive on the host."
1825034,2019-05-06 22:53:04 UTC,"Reviewed:  https://review.opendev.org/653158
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f9eb685bee156590600889449470b35c993cc4cf
Submitter: Zuul
Branch:    master"
1825034,2019-09-27 09:04:04 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1825034,2019-06-06 06:24:10 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1825034,2019-05-22 14:53:39 UTC,"Reviewed:  https://review.opendev.org/657421
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=af07ddb734474051ed77c425bf8a50426c2d1a88
Submitter: Zuul
Branch:    stable/stein"
1825034,2019-05-22 10:09:08 UTC,"Reviewed:  https://review.opendev.org/657420
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=840f109afc537c4818288a2bea09d550ca66ac14
Submitter: Zuul
Branch:    stable/stein"
1825034,2019-05-14 10:16:14 UTC,I know I am too late to the party here but just thought of leaving a comment here:
1825034,2019-05-06 18:45:12 UTC,"Reviewed:  https://review.opendev.org/653098
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=91056970b5359b8410348010ce7a96547272e1c8
Submitter: Zuul
Branch:    master"
1825034,2019-04-16 21:53:15 UTC,"I would have been in favor of the last option of hard deleting the fake instance record via direct DB access upon completion of the online data migration, but it doesn't help in the case where multiple runs of the migration are needed."
1825034,2019-05-06 18:01:53 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/657420"
1825034,2019-04-25 20:21:42 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/653131"
1825034,2019-04-16 21:51:17 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653158"
1825034,2019-04-16 21:38:23 UTC,"I'm leaning a bit towards specifically excluding the server with the (well-known?) fake UUID. The hard-delete option seems vulnerable to race conditions (this has to work during online migrations, right?)."
1825034,2019-04-16 20:21:20 UTC,I don't really have many good ideas on how to handle this.
1825034,2019-04-16 19:39:50 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653131"
1825034,2019-04-16 19:20:31 UTC,"Related fix proposed to branch: master
Review: https://review.openstack.org/653098"
1825034,2019-05-06 18:02:12 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/657421"
1825034,2019-04-16 19:19:42 UTC,The workaround is to archive the deleted marker instance after running the online data migration.
1825036,2019-04-16 21:15:49 UTC,"We should test to see if we can pull out the highlighted objects into the overlay layer so that they are on top of everything, although this might cause some draw order issues."
1825037,2019-06-24 09:44:48 UTC,This bug was fixed in the package scilab - 6.0.2-0ubuntu2~19.04
1825037,2019-06-20 22:31:47 UTC,This bug was fixed in the package scilab - 6.0.1-7ubuntu1~18.10.1
1825037,2019-06-20 22:29:53 UTC,"The verification of the Stable Release Update for scilab has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825037,2019-06-18 21:13:12 UTC,"Verified that bionic-proposed (6.0.1-7ubuntu1~18.04.1), cosmic-proposed (6.0.1-7ubuntu1~18.10.1), and disco-proposed (6.0.2-0ubuntu2~19.04) fixes this bug and can be successfully run."
1825037,2019-06-13 17:05:59 UTC,"Hello Norbert, or anyone else affected,"
1825037,2019-05-22 01:38:54 UTC,This bug was fixed in the package scilab - 6.0.2-0ubuntu2
1825037,2019-06-13 16:34:43 UTC,"Hello Norbert, or anyone else affected,"
1825037,2019-05-23 11:01:37 UTC,Please backport the fix to Ubuntu 18.04 Bionic Beaver (LONG TERM SUPPORT release).
1825037,2019-05-13 13:26:46 UTC,This Bug report and workaround works for me:
1825037,2019-04-16 20:43:59 UTC,Disco is affected too with Scilab 6.0.2-0ubuntu1 .
1825037,2019-04-16 20:24:57 UTC,Cosmic is affected too with Scilab 6.0.1-7ubuntu1~18.10 .
1825037,2019-06-13 16:51:23 UTC,"Hello Norbert, or anyone else affected,"
1825037,2019-07-07 07:26:23 UTC,"I was writing a small command on editor scriptin scilab in Ubuntu os. Somehow the script window vanished. I force closed the scilab. Next time opened the computer, it showed some dialogues that some process runs in the background.. now scilab script did not respond and now scilab icon in gnome does not respond. I tried to remove / update/reinstall scilab but the message said latest version installed. Please advise"
1825037,2019-06-20 22:29:47 UTC,This bug was fixed in the package scilab - 6.0.1-7ubuntu1~18.04.1
1825043,2019-04-23 10:03:01 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1825044,2019-06-26 19:40:19 UTC,"The new zone fill algorithm doesn't directly address this, but will improve it by being less stingy with thermal spokes."
1825044,2019-04-16 20:15:01 UTC,Fixing this would require taking traces into account when determining whether we have copper islands.
1825046,2019-07-05 12:50:41 UTC,This issue was fixed in the openstack/tripleo-common 10.8.0 release.
1825046,2019-06-07 19:29:08 UTC,This issue was fixed in the openstack/tripleo-common 11.0.0 release.
1825046,2019-05-21 23:15:10 UTC,"Reviewed:  https://review.opendev.org/660418
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=f38d89e72eb69183524091260ef9badf2ae4fae6
Submitter: Zuul
Branch:    stable/stein"
1825046,2019-05-21 15:01:21 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660418"
1825046,2019-05-20 20:36:21 UTC,"Reviewed:  https://review.opendev.org/653151
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=294f67bd7e38da759f7d53bc776933095029d8fe
Submitter: Zuul
Branch:    master"
1825046,2019-04-16 20:59:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653151"
1825047,2019-04-16 22:48:39 UTC,"Using DD in Linux create a working USB Flash which pass the media test, hmmmm"
1825047,2019-04-16 23:02:43 UTC,"Oh yea, I do ""of course"" use/select GPT partition scheme in Rufus"
1825049,2019-04-29 10:04:01 UTC,"Thank you for preparing these updates, providing all the SRU information, etc!"
1825049,2019-04-29 09:14:41 UTC,"Examining the source, the fix looks present in 3.0.8-2 which is in Disco and Eoan, and debian/changelog reports it fixed in that upload also."
1825049,2019-06-04 23:21:22 UTC,"The verification of the Stable Release Update for lexicon has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825049,2019-06-04 23:21:17 UTC,This bug was fixed in the package lexicon - 2.2.1-2ubuntu0.1
1825049,2019-05-16 14:47:26 UTC,"Great, thank you!"
1825049,2019-05-16 14:32:12 UTC,"Yes, of course!"
1825049,2019-04-26 21:42:44 UTC,"I am a maintainer of the Lexicon project, and want to propose a SRU for Lexicon 2.2.1 on Bionic and Lexicon 2.7.0 on Cosmic to fix that issue."
1825049,2019-05-16 06:41:54 UTC,"Hello Leon, or anyone else affected,"
1825049,2019-05-15 16:17:38 UTC,"Hello Leon, or anyone else affected,"
1825049,2019-04-30 10:43:51 UTC,Uploaded to Bionic and Cosmic. I fixed my own previous mistake: s/xenial/bionic/ in debian/changelog of my Bionic debdiff from above. Apart from that I uploaded the latest debdiffs as-is.
1825049,2019-04-29 16:12:33 UTC,I fixed the issue observed in Cosmic as observed with http://paste.ubuntu.com/p/VfDDrbR9qF/
1825049,2019-05-16 13:58:05 UTC,"Leon, please could you confirm exactly what testing you performed and the exact package version number of the package that you tested? This information helps us avoid mistakes, such as anything specific that we think should be verified being missed. Otherwise we cannot make any judgement as to whether the testing that has been performed is sufficient, which is required to release the package to the updates pocket."
1825049,2019-04-29 10:06:50 UTC,"I'm curious. Are there tests missing from the Cosmic patch, or are they already present and so not required in the patch?"
1825052,2020-01-06 17:43:35 UTC,"@pedronis - this was filed when working on system-usernames. Older golang-seccomp will not generate proper bpfs when using argument filtering in various ways. Ie, in non-system-username policy, using '>=' and '<=' comparisons, but this only affects one rule: setpriority (there is also a corresponding 'nice' rule, but this maps to setpriority in the kernel)."
1825052,2020-01-06 13:16:25 UTC,@jdstrand what is the status of this one?
1825052,2019-04-22 15:05:44 UTC,"FYI, at this point the seccomp sandbox should be disabled on any distro that doesn't have the upstream https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e (either via distro patch to libseccomp or using snapd's vendored golang-seccomp) because otherwise snap-seccomp generates invalid bpf."
1825052,2019-04-22 16:08:40 UTC,"FYI, escalated this via the forum: https://forum.snapcraft.io/t/disabling-seccomp-sandbox-where-a-buggy-golang-seccomp-is-used/11054"
1825052,2019-04-22 14:38:01 UTC,"I looked at the differences between Debian unstable and 18.10 and found that Ubuntu is carrying the ACTLOG patch. I didn't think that this would actually make a difference in the resulting pfc, but just to be sure, I rebuilt libseccomp without that patch on 18.10, then install those packages, then built snapd with those installed (since the snapd packages will statically link libseccomp). Indeed, the pfc was the same as the distro libseccomp. This makes me suspect the difference is between the golang-seccomp that Ubuntu uses and the one everyone else uses."
1825052,2019-04-22 14:01:25 UTC,"I looked at this a little more and the pfc (generate with 'SNAP_SECCOMP_DEBUG=1 /usr/libexec/snapd/snap-seccomp compile /var/lib/snapd/seccomp/bpf/snap.hello-world.sh.src /tmp/snap.hello-world.sh.bin > /tmp/snap.hello-world.sh.pfc) on Fedora (libseccomp 2.3.3) is simply wrong for our 'setpriority PRIO_PROCESS 0 <=19' rule (note, on amd64, sepriority is '141' as seen with scmp_sys_resolver) since it isn't ANDing the arguments:"
1825052,2019-04-17 12:30:07 UTC,"The difference between Debian 2.37.4 and 2.38 under reexec probably has to do with the reexec'd 2.38 are from Ubuntu, which doesn't have this problem."
1825052,2019-04-16 21:51:07 UTC,This is technically a security bug but not marking it as such because without file mediation the seccomp policy provides no real protection (the security technologies are meant to work together).
1825052,2019-04-22 15:03:25 UTC,"Ok, as it happens, upstream golang-seccomp 0.9.0 has a bug where it will incorrectly OR. The following commit is in upstream master but not a new release of golang-seccomp:"
1825053,2019-04-16 22:31:43 UTC,"Please provide the curtin debug logs, https://discourse.maas.io/t/getting-curtin-debug-logs/169."
1825053,2019-04-20 01:39:06 UTC,Attached is the Curtin debug log
1825054,2019-05-17 15:32:06 UTC,"I have a jar of a javafx application which I want to run, and I do not have the source code of the application. AFAIK, it has to run in java 8 with min version 8u171. On my machine I had opendk-11-jdk, openjdk-8-jdk, and openjfx installed, and ran the app with openjdk's java 8. On the 13th several openjdk packages were updated, unfortunately I do not have the full list. After the updates, the application threw class not found for the javafx application class on start up.
Downgrading just openjfx with:
sudo apt install openjfx=8u161-b12-1ubuntu2 libopenjfx-java=8u161-b12-1ubuntu2 libopenjfx-jni=8u161-b12-1ubuntu2
seems to work (I see the app gui), but from the terminal I see an exception for a different class not found: com.sun.deploy.uitoolkit.impl.fx.HostServicesFactory"
1825054,2019-08-06 04:17:21 UTC,[Expired for openjfx (Ubuntu) because there has been no activity for 60 days.]
1825054,2019-06-06 19:58:35 UTC,To downgrade openjfx to version 8 and put the packages on hold so they don't get updated the next time you do a system update:
1825054,2019-05-29 09:16:02 UTC,"I have faced the same problem. I have been working with ""dl4j-examples"" which are some example codes that uses the java based deep learning libraries from github.com. A month earlier it was ok and everything was doing fine, but from yesterday the compiler is unable to fitch the javaFX libraries and so complain about their existence. If you want to reproduce this error one should follow the following steps:
1- install java openjdk-1.8
2- install java FX
3- Dowload dl4j-examples probably using the git function from the: $ git clone https://github.com/deeplearning4j/dl4j-examples.git
4- cd dl4j-examples/
5- use the maven command (maven ustility should be installed before) to build the dl4j-examples project using the command: $mvn clean install"
1825054,2019-05-14 07:16:58 UTC,With all these comment it's still incomplete?
1825054,2019-05-15 14:40:21 UTC,"As mentioned by Marco Righele (#8), I think it is related to the update to openjdk 11, as the openjfx and libopenjfx-java are now upgraded from 8u161-b12-1ubuntu2 to 11.0.2+1-1~18.04.2 and 11* packages don't contain the files for openjdk-8. To fix the issue I had to downgrade these two packages and add the lib back in eclipse, i.e. sudo apt install openjfx=8u161-b12-1ubuntu2 libopenjfx-java=8u161-b12-1ubuntu2"
1825054,2019-04-17 00:49:07 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1825054,2019-04-24 11:26:30 UTC,"I have exactly the same problem, i cannot work with javafx anymore.
Openjfx does not contain the jfxrt file even if it's listed with apt file"
1825054,2019-04-23 13:40:29 UTC,"I confirm classes are missing to be able to compile with OpenJDK8, I know policies are changing for jdk ecosystem, but in an LTS version we all expect packages to be reliable during supported period. So not being able to compile from from day to another is somehow surprising."
1825054,2019-04-17 21:58:19 UTC,I managed to fix this for myself. I did upgrade to java 11 and then followed https://github.com/scalafx/scalafx on how to fix my build.sbt. Similar instructions for other build systems can be found here: https://openjfx.io/openjfx-docs/
1825054,2019-04-17 20:20:40 UTC,"I am not sure how to reproduce this. My build was working one day and stopped the other day. Given I don't know what happened and what the status was before it's hard to tell. I suspect the JavaFX jar file has vanished. And yes, I am using Java 8 so that might be it."
1825054,2019-04-17 15:12:16 UTC,"i have this problem too. After newest update i do not have javaFX jar file ...
This is also my post : https://askubuntu.com/questions/1134654/i-do-not-have-javafx-after-newest-update"
1825054,2019-04-26 10:21:01 UTC,"I have the same issue too.
Can I guess that it is related to this recent announcement https://blog.ubuntu.com/2019/04/19/announcing-openjdk-11-packages-in-ubuntu-18-04-lts ?"
1825055,2019-04-17 15:02:13 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1825055,2019-04-18 08:33:19 UTC,"Thank you for your bug report, the log has those errors
'SQUASHFS error: zlib decompression failed, data probably corrupt'"
1825055,2019-04-22 22:03:00 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD).  You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry your installation with new media.  In the event that is is not in fact an error with your installation media please set the bug's status back to New.  Thanks and good luck!
1825055,2019-06-22 04:17:30 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1825056,2019-12-13 18:01:08 UTC,Changed the priority to low and removed the stx.4.0 tag as this issue has a manual workaround and is a low runner scenario.
1825056,2019-11-26 14:58:55 UTC,This issue is not a high priority issue and similar to the above comment can be moved to stx.4.0.
1825056,2019-05-13 15:50:47 UTC,Lowering priority to medium given that the issue is specific to AIO-SX
1825056,2019-04-17 17:15:42 UTC,Marking as release gating; high priority - related to new container capability to pin pods to cpus
1825056,2019-07-15 21:00:10 UTC,"After reviewing with the containers TL, removed the stx2.0 gate and replaced with stx3.0 for the following reasons:
1) This issue existed in previous releases.
2) This is an AIO-SX issue only.
3) The workaround is to not have any VMs running on the AIO when the user changes the # of platform cores."
1825056,2019-05-13 15:43:49 UTC,"This is a AIO Simplex day-one issue. If we re-configure the platform cores while an instance is running, there is nowhere to evacuate. There ends up being no scheduling operation (eg, spawn, resize, migrate, evacuate, etc), so the instance pinning becomes invalid."
1825057,2019-04-18 10:53:21 UTC,"I would definitely say this is unexpected behavior, and if it is
reproducible I would potentially consider it Critical rather than just
high. Anyone who has access to both a testing and a production deployment
certainly doesn't want to destroy anything but the testing controller."
1825057,2019-04-18 11:04:41 UTC,"$ /snap/bin/juju controllers
Use --refresh option with this command to see the latest information."
1825057,2019-04-28 21:03:02 UTC,"Also unable to reproduce my own claims, and I'm happy to say so.  ;-)"
1825057,2019-06-28 04:17:22 UTC,[Expired for juju because there has been no activity for 60 days.]
1825057,2019-06-28 04:31:54 UTC,"I think that this is another occurrence of the bug where the controller specified on the command was ignored and the current controller was used, bug # 1832779 has a fix."
1825058,2019-05-14 22:54:45 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825058,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1825058,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1825058,2019-04-16 22:18:59 UTC,The non-HWE kernel for 16.04 is unaffected.
1825058,2019-04-25 22:32:24 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1825058,2019-04-17 03:08:53 UTC,https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a1881c9b8a1ed
1825058,2019-04-16 22:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825058,2019-04-29 16:03:42 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825060,2019-04-17 09:19:04 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1825060,2019-04-17 09:19:31 UTC,what ubuntu version do you use?
1825060,2019-04-17 22:08:05 UTC,"Hi, I have tested the beta of Ubuntu 19.04 and it seems that it is
already fixed. I will wait to update. Thank you and sorry for the
inconvenience."
1825060,2019-06-17 04:17:48 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1825061,2019-10-22 14:48:30 UTC,This issue was fixed in the openstack/python-novaclient 16.0.0 release.
1825061,2019-09-25 10:37:09 UTC,"Reviewed:  https://review.opendev.org/653683
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=d1c5dc61d60b29428484a38703a0064933cc7c0e
Submitter: Zuul
Branch:    master"
1825061,2019-04-18 08:15:49 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653683"
1825063,2019-04-23 13:05:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825063,2020-03-03 13:30:15 UTC,"Hi,
same here.
I mostly use Nemo and assumed it happens because both Nemo and Nautilus are installed."
1825063,2020-03-29 06:03:16 UTC,Ubuntu 18.04 backport of the fix is at Python 2 series:
1825063,2020-03-30 08:24:36 UTC,"The attachment ""Properly initialize GObject to get rid of runtime errors in syslog"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1825064,2019-05-13 23:52:04 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu5
1825064,2019-05-06 08:43:15 UTC,This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.10
1825064,2019-05-06 08:12:16 UTC,"The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825064,2019-04-29 03:27:58 UTC,Tested in 19.10 (gnome-software 3.30.2-0ubuntu11). When viewing the discord snap the linked review doesn't show.
1825064,2019-05-06 08:28:40 UTC,This bug was fixed in the package gnome-software - 3.30.2-0ubuntu11
1825064,2019-04-29 03:05:43 UTC,Tested in 18.04 LTS (gnome-software 3.28.1-0ubuntu4.18.04.10). When viewing the discord snap the linked review doesn't show.
1825064,2019-04-29 03:10:13 UTC,Tested in 19.04 LTS (gnome-software 3.30.6-2ubuntu4). When viewing the discord snap the linked review doesn't show.
1825064,2019-04-18 20:46:57 UTC,Please provide a test case that includes a specific application that is known to have non-Ubuntu reviews.
1825064,2019-04-18 21:00:22 UTC,The Discord snap is a good example.  This review should not appear:
1825064,2019-05-06 08:22:16 UTC,This bug was fixed in the package gnome-software - 3.30.6-2ubuntu4
1825064,2019-04-25 13:42:48 UTC,"Hello Robert, or anyone else affected,"
1825064,2019-04-25 13:49:01 UTC,"Hello Robert, or anyone else affected,"
1825064,2019-04-25 13:41:00 UTC,"Hello Robert, or anyone else affected,"
1825066,2019-04-17 09:18:27 UTC,Thank you for your bug report. Can you add your journalctl log from the session? Do you use the default Ubuntu session? What monitors?
1825066,2019-06-17 04:17:32 UTC,[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]
1825068,2019-04-16 23:51:45 UTC,Work to address this is underway https://github.com/juju/juju/pull/10044
1825069,2021-02-11 11:41:29 UTC,"I believe we should also think about using landmarks to identify page regions. I have looked at the issue in the Bootstrap OPAC a bit. There are only navigation Landmark present (see the attachment), but I think at least ""form"" and ""main"" landmark should be used too (or maybe any other, I am not an Aria landmark expert)."
1825069,2019-06-21 15:04:45 UTC,Specific case where aria-label provides a better accessible name than title does: https://bugs.launchpad.net/evergreen/+bug/1833726
1825069,2019-05-28 01:21:26 UTC,Another interesting article on providing accessible labels to buttons: https://www.sarasoueidan.com/blog/accessible-icon-buttons/
1825069,2019-05-09 17:35:14 UTC,And one more note: bootstrap makes it really easy to make the tooltips generated by the title attribute keyboard-accessible: https://getbootstrap.com/docs/4.1/components/tooltips/
1825069,2019-05-09 15:30:07 UTC,"A screed against the title attribute, with some interesting considerations for screen magnifier users: https://axesslab.com/title-texts-suck/"
1825069,2019-04-18 13:25:42 UTC,A message from Amy Drayer on the lib4a11y email list:
1825069,2019-04-17 14:57:25 UTC,"Also, sending this to the lib4a11y email list to get their feedback."
1825069,2019-04-17 14:49:05 UTC,"Very true, Bill!  And also a note that the tooltip generated by the title attribute is only visible on mouse hover, not on keyboard focus, so it provides that benefit only to users who navigate using a mouse and happen to hover their mouse over the icon, button, etc. (unless we, again, include additional CSS like this: http://pauljadam.com/demos/title-keyboard.html)"
1825069,2019-04-17 14:04:41 UTC,"There are cases where having the tooltip generated by a title attribute is helpful, especially when describing icons, buttons, etc. that don't have visible text.  As I understand it, making aria-label's do the same thing would require some additional CSS."
1825069,2019-05-03 14:51:08 UTC,Some interesting threads from the WebAIM email list:
1825069,2019-04-17 16:52:10 UTC,"I favor using the title attribute over aria-label specifically because of the tooltip. That said, I'm all for testing how modern screen readers handle title vs. aria-label to verify which option is better for accessibility."
1825070,2019-04-17 02:36:59 UTC,"Without a way to reproduce this behavior, there isn't any chance for me
to fix it. If and when you do find a way to reproduce, please update
this ticket."
1825070,2019-06-16 04:17:30 UTC,[Expired for calibre because there has been no activity for 60 days.]
1825072,2019-04-17 01:31:42 UTC,This can be fixed by dropping into a shell on the container and running:
1825073,2019-06-27 08:28:55 UTC,'juju add-cloud' without any arguments goes into an interactive mode.
1825074,2019-05-14 22:54:48 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825074,2019-04-29 16:04:17 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825074,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1825074,2019-04-17 05:37:12 UTC,"Patch to dump amdgpu_wb usage. Confirmed amdgpu_wb_free() is called with an offset returned from amdgpu_wb_get(), and yet it skips actual release call because offset is larger than AMDGPU_MAX_WB."
1825074,2019-04-17 02:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825074,2019-04-17 02:22:26 UTC,"commit 97407b63ea60 drm/amdgpu: use 256 bit buffers for all wb allocations (v2)
commit 63ae07ca4fb4 drm/amdgpu:fix wb_clear"
1825074,2019-04-17 02:23:49 UTC,This only affects Bionic as Xenial doesn't come with the two commits and Cosmic/Disco have already included the fix.
1825075,2019-04-17 02:41:45 UTC,"Setting Confirmed because this is replicating an issue reporting in the community, and I was able to reproduce the issue: https://utcc.utoronto.ca/~cks/space/blog/linux/SoftwareRaidAssemblySystemd"
1825075,2019-04-17 02:40:38 UTC,"A degraded array used for the root filesystem DOES boot as expected on Bionic. My guess is that during boot the ""poor-mans mdadm-last-resort@.timer"" code from debian/initramfs/script.local-block is executed where as with non-root devices that is not the case and it potentially should use the actual mdadm-last-resort@ timer service?"
1825076,2021-02-11 23:01:32 UTC,"Comment 1. Yes, the Org unit selector overlaps the No subscriptions are owned message, but I am not sure that is a problem."
1825077,2019-04-23 16:26:38 UTC,"It seems like this only occurs at certain browser widths, but it could be improved"
1825078,2019-08-28 08:01:45 UTC,"compass-adapters seems to be a dead project, you could check with the TC whether it should be retired."
1825078,2019-10-28 04:17:19 UTC,[Expired for OpenStack + Chef because there has been no activity for 60 days.]
1825080,2019-04-17 04:04:10 UTC,Example output for the given combination of versions:
1825083,2019-09-20 10:06:55 UTC,Is this still the case? I feel like this one has been addressed.
1825083,2019-09-20 10:42:36 UTC,The behaviour is still that scale defaults = 0 if not specified. This is consistent with non k8s bundles which will also set num_units = 0 if not specified. bundles have always behaved like this. Happy to discuss changing how they work but marking this as invalid unless we want to change bundle behaviour holistically.
1825084,2019-04-17 04:21:48 UTC,"Have assigned it to me, and will mark ""In Progress"" once work has started. Unless someone else wants to get their feet wet and pick this up."
1825085,2019-04-17 09:15:39 UTC,"Thank you for your bug report, that's an upstream issue and should ideally be reported on https://gitlab.gnome.org/GNOME/file-roller/issues/"
1825085,2019-04-19 12:06:48 UTC,Fix proposed upstream: https://gitlab.gnome.org/GNOME/file-roller/merge_requests/12
1825085,2019-11-16 05:13:41 UTC,The fix is in this version https://launchpad.net/ubuntu/+source/file-roller/3.32.2-1
1825091,2019-04-17 06:13:31 UTC,I logged into master and not able to find any pods in kube-system namespace
1825094,2019-05-25 18:43:12 UTC,"I also have the same problem with qpdfview 0.4.18beta1.
I tried different printers with same result."
1825094,2019-05-25 20:08:39 UTC,@kike Could you also give the dailydebs a try? My guess that the distributions have started packaging snapshots since I have a hard time actually getting a release out the door...
1825094,2019-06-18 17:30:24 UTC,"@AdamReichold I've installed https://aur.archlinux.org/packages/qpdfview-bzr/ and it looks it is printing as expected.
Thank you!"
1825094,2019-04-18 16:31:31 UTC,"Hello Terrance,"
1825094,2019-05-05 18:26:11 UTC,"I had the same problem with the version distributed with Lubuntu 19.04. But when I upgraded as described above, to 0.4.17.99~2090~63~ubuntu19.04.1, which seems to give ""qpdfview 0.4.18beta1"" in the ""About"" window, the problem went away."
1825096,2019-06-23 05:05:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825099,2019-04-17 06:47:43 UTC,This issue is blocking SRU testing on s390x KVM
1825099,2019-05-21 11:16:04 UTC,yeah \o/
1825099,2019-05-20 15:29:16 UTC,Verified fix released as kernel c-i is now passing for xenial s390x-kvm
1825099,2019-05-16 10:21:45 UTC,"The verification of the Stable Release Update for s390-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825099,2019-05-16 10:21:39 UTC,This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.10
1825099,2019-05-09 22:54:20 UTC,"Reviewed the changes made by Frank and Dimitri, thank you. As Dimitiri has verified this fixed I also verified the fix in -proposed, all appears to work, now waiting for it to land in main."
1825099,2019-05-09 12:22:48 UTC,"$ dpkg-query -W s390-tools
s390-tools	1.34.0-0ubuntu8.9
$ sudo chreipl /dev/vda1
chreipl: Could not find DASD CCW device ""virtio1"""
1825099,2019-05-08 13:58:22 UTC,"Hello Po-Hsu, or anyone else affected,"
1825099,2019-04-26 17:43:39 UTC,"I just recognized that you cherry-picked just the minimal needed changes in function ccw_busid_get_sysfs_new.
I thought you picked the entire latest chreipl command from a newer s390-tools version - and in this case it would have been good if lsreipl is aligned to it and on the same level (in case it had changes, too).
But with your minimal cherry pick this shouldn't be needed - I agree - and regression risk is also minimal."
1825099,2019-04-26 06:10:40 UTC,"I wondering if it makes sense to cherrypick also for lsreipl, since both tools are almost used every time in combination, hence I think it would be good if they are on a similar level.
Not totally sure if it is used here, but could be, for example for verification purposes ..."
1825099,2019-04-25 03:14:07 UTC,"Hello Andres,"
1825099,2019-04-24 22:49:36 UTC,Adjusting bug tasks
1825099,2019-04-24 20:43:07 UTC,"oh i see what's happening here, just to confirm:"
1825099,2019-04-24 20:23:18 UTC,"Then if this is a bug in chreipl, then there shouldn't really be any reason why MAAS couldn't deploy in Xenial. That said, what I'm surprised about is s390x VM off MAAS when [1] was never backported to Xenial."
1825099,2019-04-17 18:17:45 UTC,+1 for Xenial KVM guest support (not for xenial as base OS for MAAS)
1825099,2019-04-17 17:45:00 UTC,"s390x in general, is supported including qemu/kvm/openstack in xenial."
1825099,2019-04-17 16:02:07 UTC,We have never supported s390x on Xenial. s390x was enabled for bionic+.
1825099,2019-04-17 12:54:56 UTC,raising the prioirty to critical as this is blocking xenial s390x-kvm SRU testing
1825099,2019-04-26 12:18:09 UTC,cherrypick what for lsreipl? there are no code changes in lsreipl since forever...
1825099,2019-04-26 00:12:48 UTC,Hopefully this fixes s390-tools chreipl for xenial.
1825102,2019-05-29 12:39:27 UTC,"Reviewed:  https://review.opendev.org/653339
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f8e5c4ef8e1eb1c55aa380864b1a023f3c4b22ce
Submitter: Zuul
Branch:    master"
1825102,2019-04-17 07:38:46 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653339"
1825102,2019-06-12 14:43:59 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1825106,2019-04-23 11:40:12 UTC,"Thanks for your follow-up. While not ideal, it seems that the current behavior is the intended and documented[1] one, so I'm setting the status of this report to ""Won't Fix"", as it is very unlikely to be fixed with an Ubuntu-specific patch. Should the situation change feel free to set the bug status back to New and reopen the discussion."
1825106,2019-04-23 08:20:49 UTC,"The problem still exists in the latest libpcap version.
An issue report already exists: https://github.com/the-tcpdump-group/libpcap/issues/572
The solution seems to be not to use `pcap_open_live` but replace it with newer pcap functions.
In my opinion we can close this issue here. I would have done so, but I am uncertain what the right status would be that I should set (it is a valid concern, has no committed fix, will not get one, user should change code)."
1825106,2019-04-17 07:52:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825106,2019-04-18 13:43:02 UTC,Hi Paride!
1825106,2019-04-18 16:42:56 UTC,"Hello Werner,"
1825106,2019-04-18 12:50:41 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue.
1825111,2019-07-20 05:00:22 UTC,"Reviewed:  https://review.opendev.org/666861
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=a7f5e7a91bc9bfd8879fb2e4a4c0905b508dd3e5
Submitter: Zuul
Branch:    stable/stein"
1825111,2019-06-21 15:09:33 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/666861"
1825111,2019-05-21 19:32:17 UTC,"Reviewed:  https://review.opendev.org/656860
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0f2b36b2ad50694efa92a39649b778546cca3b31
Submitter: Zuul
Branch:    master"
1825111,2019-05-04 05:21:58 UTC,"This is a report for the keystone specific documents, not for openstack-manuals."
1825111,2019-05-10 22:05:34 UTC,"Frank, your proposed fix is not merged yet, did you mean to mark this as ""fix committed""? Changing to ""in-progress""."
1825111,2019-05-02 20:30:14 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/656860"
1825111,2019-04-19 22:59:27 UTC,"I suspect this is a packaging issue and not an issue with the keystone documentation or source code, so tagging the Ubuntu team."
1825111,2019-04-18 16:35:24 UTC,"Ok, can confirm the instructions don't work for stein, getting the same error. Installing libapache2-mod-wsgi-py3 works for me."
1825111,2019-04-18 16:11:40 UTC,You should be able to install keystone stein release with that method.  I will check again with the repo updated to stein from the default one.
1825111,2019-04-18 05:52:13 UTC,"Thanks for your response, but I'm not entirely with you, I'm sorry."
1825111,2019-04-17 14:31:23 UTC,"I couldn't replicate this, did a fresh ubuntu 18.04.2 install and the command ran fine."
1825111,2019-05-03 23:19:29 UTC,"this is not a keystone bug, it belongs to the documentation."
1825111,2019-05-03 23:22:17 UTC,"We checked that yesterday: the second and third parameters of the command are no longer needed, since the mentioned packages are already contained in the parent dependencies."
1825112,2019-04-17 08:18:36 UTC,"The code copying the setting is in casper, it has lightdm support but we should look at adding new code for gdm..."
1825112,2019-04-17 09:00:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1825112,2019-04-17 18:05:16 UTC,Is this the same as bug 1796275?
1825112,2019-04-18 08:18:44 UTC,"@Brian, no, see my comment on the bug you are pointing out. The other bug was about the feature not working anymore since the switch to GNOME, that bug is about the lack of gdm support"
1825112,2019-06-06 01:33:02 UTC,This bug was fixed in the package casper - 1.408
1825116,2019-04-17 11:11:25 UTC,"azzar1 and I think that what's happening is that the spinner (actually all spinners) is not animating in some VMs, due to animations in general being disabled."
1825126,2019-04-17 08:42:27 UTC,Screenshot
1825126,2020-01-24 08:59:18 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1825128,2019-05-14 07:13:38 UTC,"What does grub-check-signatures use mokutil for?
It makes more sense mokutil depends on shim not grub.
Can mokutil depend on shim package solve your issue?"
1825128,2019-05-14 07:55:51 UTC,This issue happens when installing grub-efi-amd64-signed while the image still using old mokutil so it is better to fix the issue directly in grub-efi-amd64-signed.
1825128,2019-08-11 00:45:04 UTC,"@Ivan, I update how grub-check-signatures use mokutils in bug description.
Can you please check again?"
1825128,2019-08-12 07:55:02 UTC,"shim-signed package has already depended on mokutil.
When secureboot enabled, shim is needed and mokutil should be installed."
1825128,2019-08-12 08:09:46 UTC,"per code in ubiquity:/usr/share/grub-installer/grub-installer
it install grub-efi-amd64-signed first, and then install shim-signed.
(grub_package=grub-efi-amd64-signed as the code run to here.)
===
        apt-install $grub_package || exit_code=$?
        case $grub_package in
            *-signed)
                apt-install shim-signed || true
                apt-install grub-pc || true
                ;;
        esac
==="
1825128,2019-05-14 06:10:50 UTC,per $4:
1825141,2019-07-20 17:16:08 UTC,"Instead of a ""back"" button, it now goes back by default."
1825141,2019-07-20 18:17:59 UTC,This bug was fixed in the package ubuntustudio-installer - 0.05
1825144,2019-04-25 09:41:14 UTC,This sounds like it would be a lot of work to change. Why is it easier to use SIGHUP than docker restart?
1825144,2019-04-26 01:06:57 UTC,"Hm.. I assume that it's natural to feel easier since it make more time to restart process than just reloading config files. But I realize without me who think fast development iteration important, it will be not a matter."
1825145,2019-04-17 10:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825145,2019-11-13 18:28:40 UTC,I don't see this failure in our test results for the Bionic 5.0 kernel any more and I also don't see it in the Bionic 5.3 kernel.
1825151,2019-06-04 04:55:50 UTC,"I was tested this reorder on
- checkbox-ng 1.4.0
- checkbox-support 0.41.0
- plainbox-provider-resource 0.40.0
- plainbox-provider-checkbox 0.48.0"
1825151,2019-04-17 10:33:08 UTC,"Attached
monitor-test-plan.pxu.modified/original
graphics-test-plan.pxu.modified/original
listbootstrapped After/original
session.tar"
1825151,2019-04-17 10:21:59 UTC,Automatically attached
1825151,2019-04-17 10:23:50 UTC,Automatically attached
1825151,2019-04-17 10:22:02 UTC,Automatically attached
1825151,2019-04-17 10:29:52 UTC,Automatically attached
1825152,2020-11-16 14:57:16 UTC,"Reviewed:  https://review.opendev.org/757662
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=297f4c20c4c914f7fc8528e70d572adbeff68b0f
Submitter: Zuul
Branch:    stable/rocky"
1825152,2020-10-13 01:31:52 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/757662"
1825152,2019-11-02 14:19:36 UTC,"@Xav: are You sure it's due to slow ovs db calls? IIUC L3 agent is only creating port in br-int and it don't have any other interactions with ovs db. Everything else is configured by neutron-ovs-agent later.
So if it is slow L3 agent, maybe the root cause is different?"
1825152,2019-10-31 21:37:17 UTC,"The cloud we support with 500+ routers is a xenial-queens cloud, packages from the Ubuntu Cloud Archive.  You're absolutely right, this is using the native interface, not ovs-vsctl, so the docs linked aren't a lot of use directly.  The point I'm making (not very clearly) is that we're creating each router individually, and that's slow for openvswitch (maybe others too?).  I was wondering if it's an option to group those transactions together so there's less calls to the ovs api, to speed things up a bit.  For some of the clouds I support, it can take hours to restart a L3 agent machine, and even moving a router from one agent to another takes 15 mins+ because (we think) of the slow ovs db calls at that scale."
1825152,2019-10-30 09:16:34 UTC,"@Xav, what version of Neutron are You using? Since long time default value of ovsdb_interface config option was set to ""native"" and it is even removed with https://review.opendev.org/#/c/570259/"
1825152,2019-10-30 03:51:36 UTC,"also relevant, from http://docs.openvswitch.org/en/latest/faq/issues/"
1825152,2019-05-26 03:21:32 UTC,"Reviewed:  https://review.opendev.org/660758
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fe4fc33f1c1bbb655e99733edf762e3e9debdd3e
Submitter: Zuul
Branch:    stable/stein"
1825152,2019-05-22 15:28:04 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/660758"
1825152,2019-04-26 10:44:52 UTC,"Reviewed:  https://review.opendev.org/654815
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9d60716cf1d61286a684f20ef8e05c77a0df5aa3
Submitter: Zuul
Branch:    master"
1825152,2019-04-23 07:38:18 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/654815"
1825152,2019-04-17 10:27:25 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653378"
1825152,2019-07-24 13:19:59 UTC,"Increase the bug level, because this issue has been submitted for a long time."
1825153,2019-10-17 14:27:47 UTC,I'd like to bump the importance of this a bit since combined with LP: #42791 this is the first point where users can become frustrated after a clean install.
1825154,2019-04-17 18:48:08 UTC,"> Can you guide me about the kind of debugging that should be done?
"
1825154,2019-04-17 15:10:00 UTC,The 1102w requires a firmware file (provided by the plugin package) to be downloaded to the printer. This happens when the printer is switched on connected to the computer.
1825154,2019-04-23 13:29:47 UTC,"Hi Brian
I've tried fixing the hplip and eventually messed up everything.
So I decided to install another linux distribution, fedora, which I was
curious about for a long time. The printer worked out of the box in fedora.
Thanks again for your help,"
1825154,2019-04-19 19:54:49 UTC,Hi Brian
1825154,2019-04-17 17:38:44 UTC,"Thanks Brian
I've done as you suggested, but it did not print. Can you guide me about
the kind of debugging that should be done?
Cheers,"
1825154,2019-04-18 11:38:40 UTC,"Hello Beny,"
1825154,2019-04-19 19:44:48 UTC,"There appears to have been a breakdown in communication. Nothing I have said, I hope."
1825154,2019-04-18 10:13:34 UTC,"Thanks, Brian"
1825155,2019-04-17 11:25:36 UTC,"StacktraceTop:
 cgfsng_payload_create (ops=0x5605602f54e0, handler=<optimized out>) at cgroups/cgfsng.c:1303
 lxc_spawn (handler=0x5605602f4340) at start.c:1633
 __lxc_start (name=name@entry=0x5605602dab60 ""perccli1"", handler=handler@entry=0x5605602f4340, ops=ops@entry=0x7f6292cf8340 <start_ops>, data=data@entry=0x7ffdb2f002f8, lxcpath=lxcpath@entry=0x5605602f1590 ""/home/luk/.local/share/lxc"", daemonize=daemonize@entry=false, error_num=0x5605602f16e0) at start.c:1937
 lxc_start (name=0x5605602dab60 ""perccli1"", argv=argv@entry=0x7ffdb2f003b0, handler=handler@entry=0x5605602f4340, lxcpath=0x5605602f1590 ""/home/luk/.local/share/lxc"", daemonize=<optimized out>, error_num=error_num@entry=0x5605602f16e0) at start.c:2053
 do_lxcapi_start (c=c@entry=0x5605602f16a0, useinit=useinit@entry=0, argv=0x7ffdb2f003b0, argv@entry=0x0) at lxccontainer.c:1096"
1825155,2019-04-18 02:28:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825155,2019-04-18 02:29:35 UTC,"Also tracking in:
https://errors.ubuntu.com/problem/8e0f1b9682f08bab5dedd4100e42f59cfe2cc004"
1825155,2020-03-10 15:11:40 UTC,"I bumped into this yesterday on bionic.
The commit 1e04bb71da3ed829 [1] reports to fix it."
1825157,2020-05-17 04:17:35 UTC,[Expired for charm-octavia-dashboard because there has been no activity for 60 days.]
1825157,2020-03-17 14:01:21 UTC,"Przemyslaw, do you disagree with Rodrigo's assessment above: ""it seems to me to be a role misconfiguration problem and not a defect""? If not, then this bug is, in fact, ""invalid"" rather than ""new"""
1825157,2019-09-03 04:17:24 UTC,[Expired for charm-octavia-dashboard because there has been no activity for 60 days.]
1825157,2019-07-04 14:54:28 UTC,I experience this issue on non-admin user on Stein. Adding a role load-balancer-observer to a non-admin user (as advised in #10) fixes the issue.
1825157,2019-05-20 16:45:35 UTC,"In light of Rodrigo's comment, I'm setting this to incomplete."
1825157,2019-05-20 15:57:11 UTC,"Hi Dmitrii,"
1825157,2019-05-03 16:19:05 UTC,"As a side effect of not having this role by default a non-admin user cannot perform other actions as well. For example, creating and deleting tenant networks is affected by the load-balancers pane because even if you do not open it right away as calls to Neutron are still made and errors are written in the dashboard log."
1825157,2020-05-17 04:17:36 UTC,[Expired for OpenStack Octavia Charm because there has been no activity for 60 days.]
1825157,2019-05-03 16:05:45 UTC,"Digging further, I noticed that there are default roles present specifically for Octavia."
1825157,2019-05-03 16:07:36 UTC,"The assignment can be done from the admin user by going into ""Projects"" -> ""Manage Members"" -> Role assignments drop-down menu for a particular member (see the screenshot attached."
1825157,2019-04-17 11:29:21 UTC,subscribed ~field-high
1825157,2019-04-18 13:44:24 UTC,"Triggering the Horizon charm ('juju config openstack-dashboard debug=true') has fixed out the issue.
Now the LB panel works properly."
1825157,2019-04-18 13:49:31 UTC,Fixed triggering a config change ('debug=true') on the Openstack Dashboard service.
1825157,2020-03-16 16:48:21 UTC,"I can still see this issue on bionic-stein with 20.02 charms. The workaround is to assign the role ""load-balancer_global_observer"" to the non-admin user."
1825157,2019-04-27 20:03:56 UTC,@lorenzo-cavassa any recommendation or work-around for this issue? I'm facing the same problem.
1825157,2019-04-28 21:18:22 UTC,Deploying OpenStack from ``https://github.com/openstack-charmers/openstack-bundles/tree/master/stable/openstack-base`` with overlay https://github.com/openstack-charmers/openstack-bundles/blob/master/stable/overlays/loadbalancer-octavia.yaml with ``openstack-origin`` set to ``bionic-rocky`` does not display the behaviour described in this bug report.  I.e. it does produce a working Load Balancer panel.
1825157,2019-04-29 06:49:30 UTC,"@Frode, I've attached the overlay bundle I'm using, which deploys Octavia+Dashboard using an HA configuration: please look at comment #1."
1825157,2019-05-03 15:59:13 UTC,I could only reproduce the issue with a non-admin user (bionic/stein).
1825157,2019-04-18 14:42:45 UTC,"Actually it looks like it works properly only when 'debug=true' is set for the openstack-dashboard service: if I revert it back to 'debug=false', the LB panel doesn't work.
I have to keep the 'debug' config value set to 'true'."
1825159,2019-04-18 13:34:59 UTC,"Use of config-flags is experimental and typically indicates that new charm feature work is necessary.  This path is untested and not implemented in OpenStack Charms.  If we need to get this feature in place, we should lab it, write a specification based on the findings in the lab, and put a plan in place to properly introduce the charm feature."
1825159,2019-04-18 20:05:19 UTC,"Ryan, I do think there is an issue somewhere (hopefully, on my configs).
Just to clarify, I am following the step-by-step as described on: https://jujucharms.com/cinder/"
1825159,2019-04-19 13:09:52 UTC,Ok that seems to be a different bug. It is certainly different than the title and description of this bug.
1825159,2019-04-22 09:18:19 UTC,"Ryan, agreed, my original understanding on this bug was that issues were related to the Filter I've added. However, I can see this is not the case anylonger."
1825160,2019-04-18 06:59:52 UTC,"It is an openstackclient issue, not a python-novaclient issue."
1825160,2019-04-18 07:01:46 UTC,There is a difference about REST API calls between python-openstackclient and python-novaclient.
1825161,2020-09-11 07:37:01 UTC,"Update: Ok, Ok I think that I understood it, I was thinking that CO stands for controls, but instead its controller objects and now everything makes sense :)"
1825161,2020-09-10 16:06:07 UTC,"I am extremely sorry to bother u again, but I really tried to understand what am trying to achieve, but I simply can't. so, my doubts are:-
1. U said ""Find the affected CO's in the code"", so do I have to go through the whole list of controllers https://github.com/mixxxdj/mixxx/wiki/Mixxxcontrols or is it that I have to work only with the Microphone Controllers? https://github.com/mixxxdj/mixxx/wiki/Mixxxcontrols/49407737fa36c55d4570597803c7ed362a344309#microphonen"
1825161,2020-09-09 16:42:15 UTC,"On it, thanks a lot"
1825161,2020-09-09 14:29:20 UTC,"I would like to work on this, may I be guided what needs to be done in brief and how can I achieve it? Thanks"
1825161,2019-04-18 22:11:53 UTC,https://github.com/mixxxdj/mixxx/blob/9da873a777a147a3afadfb3a988ec42112359d1e/src/effects/effectrack.cpp#L431
1825161,2019-04-18 21:40:07 UTC,"Yup, I hoped it would be that easy :)
can you point me to an alias example?"
1825161,2020-09-09 15:09:41 UTC,"Find the affected COs in the code.
Replace the name with the new name.
Insert aliases for the old names."
1825161,2019-04-18 19:26:10 UTC,It would be quite easy to use [Microphone1] and alias it to [Microphone] do be compatible with legacy skins.
1825163,2019-04-17 20:06:02 UTC,"@DiQ,"
1825163,2019-04-17 20:53:39 UTC,"18.04.2 works as expected, thanks  Was 18.04.1 really broken?  LTS??!!"
1825163,2019-11-15 22:19:40 UTC,"The LTS is not buggy but it looks like there was some corruption on your download or image written, from the log"
1825164,2019-04-18 21:06:02 UTC,"This is either a duplicate, or the Janitor is on holiday again...."
1825165,2019-04-18 01:19:56 UTC,Is this actually documented anywhere? :)
1825165,2019-04-18 12:53:28 UTC,"Well, in the examples :)"
1825166,2019-05-22 14:32:16 UTC,https://github.com/juju/juju/pull/10204 fixes this bug for the 2.6 branch
1825167,2019-04-17 12:59:53 UTC,https://gitlab.gnome.org/GNOME/nautilus/issues/991
1825167,2019-04-17 13:07:18 UTC,"Thank you for your bug report, could you provide the output of ""$ gio mount -li"" ?"
1825167,2019-04-17 13:26:29 UTC,I changed the name of the gmail account to USER.
1825170,2019-04-18 21:07:13 UTC,"@Hildo, is this reproducible for you?  Are there any specific steps?  (It's not crashing for me....)"
1825170,2019-08-08 04:17:33 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1825170,2019-06-08 15:08:18 UTC,"@Hildo, there were no changes that I'm aware of.  However, the crash is due to memory corruption, so changes elsewhere can render the corruption benign.  I suspect, though, that the bug will come back at some point."
1825170,2019-06-04 22:26:42 UTC,"Thanks @Jeff, I really like the footprint previews. And I am experience not more crash by the search, was there some changes in this portion of the code? (I am using the last Ubuntu 16.04 Nightly, always updated)."
1825170,2019-06-04 22:13:50 UTC,"@JP, were you running on a French system when you tried to reproduce it?  The reason I ask is https://bugs.launchpad.net/kicad/+bug/1676047."
1825170,2019-06-04 21:57:21 UTC,"@Hildo, do you need the footprint previews?  They're causing the crashes.  (You can turn them off in Preferences / Eeschema / Show footprint previews in symbol chooser.)"
1825170,2019-05-09 12:45:13 UTC,"Thanks Jons, more simple and keep ENVIROMENT mine that reproduce the bug."
1825170,2019-05-07 20:28:46 UTC,"Ah, I didn't know that Wayne.
Hildo -- you can try `apt-get install kicad-dbg` and re-run kicad"
1825170,2019-05-07 20:21:58 UTC,"Yes. I am using (yesterday compilation) Nigthly at Ubuntu 16.04 from PPA.
So, I just need to change some configuration?"
1825170,2019-05-07 20:16:14 UTC,If you are using JS Reynaud's PPA I don't think you need to build from source. There are debug symbols available for nightly builds.  See https://code.launchpad.net/~js-reynaud/+archive/ubuntu/ppa-kicad/+packages?batch=75&direction=backwards&memo=75.
1825170,2019-05-07 20:11:33 UTC,"I could use this information to create a ""how to start developing using KiCad code""."
1825170,2019-05-07 20:06:07 UTC,Looks like you are missing GLEW library dependency.  I think this command should get you most of the requirements:
1825170,2019-05-07 20:04:04 UTC,Error of  `cmake`:
1825170,2019-05-07 19:55:55 UTC,did the cmake command succeed?  If cmake fails it will not generate the makefile.
1825170,2019-05-07 20:22:43 UTC,I think for OCE you need:
1825170,2019-05-07 19:51:10 UTC,"by default it will install to /usr/local instead of /usr like the PPA.
If you want to install it somewhere specific, you can add -DCMAKE_INSTALL_PREFIX=/whatever to the cmake command line. If you specify a prefix somewhere in your home directory, you should not even need the sudo to run make install.
Keep in mind if you make a prefix that is not in your PATH, you will have to manually run kicad by the full path, like /home/username/whatever/bin/kicad"
1825170,2019-05-07 19:51:14 UTC,"Running `make` from 'build/debug' I had ""make: *** No targets specified and no makefile found.  Stop."""
1825170,2019-04-22 12:32:03 UTC,"Yes, totally. Just type and it crash.
Even after I update to today's Nightly (201904212302+223e24f~82~ubuntu16.04.1). I am using in two computer with same operational system (Ubuntu) but, this behavior is just in one of them (as far I now)."
1825170,2019-04-22 14:13:53 UTC,You may try to start out with a simple gdb sessions.
1825170,2019-04-22 15:04:36 UTC,"@all, follow log:"
1825170,2019-04-25 13:35:13 UTC,"I am attaching this new log because the same bug appear to be cause by a different segment fault (before in _eeschema.kiface, in this on libthread_db.so.1)."
1825170,2019-04-26 22:59:25 UTC,The duplicate has a more descriptive stack trace: https://bugs.launchpad.net/kicad/+bug/1826613
1825170,2019-05-03 13:21:47 UTC,Just to some useful information:
1825170,2019-04-26 13:54:28 UTC,Sadly the logs don't contain much of use.
1825170,2019-05-07 14:00:24 UTC,"Could it be. For example lp:1797680 from lp:779854 implementation never worked at Ubuntu 16.04 Unity but, one I tested in a Gnome desktop installed at Ubuntu 16.04 and worked."
1825170,2019-05-07 14:02:02 UTC,Correction lp:1797680 from lp:1779854
1825170,2019-05-07 14:41:08 UTC,"On my Ubuntu 16.04 LTS with Unity, I cannot reproduce this crash."
1825170,2019-05-07 15:09:42 UTC,"Yes I can. But I will need some help / instructions (the git link to clone and commands to run to compile).
My experience with gcc / make / compilers are just for embedded systems."
1825170,2019-05-07 19:36:26 UTC,Docs server is giving me 504 error right now so here are basic build instructions
1825170,2019-05-07 19:48:33 UTC,Will the `sudo make install` overwrite my current installation? How to reverse at the end?
1825170,2019-05-07 13:10:18 UTC,I cannot reproduce this with gtk2 or gtk3 builds on my Debian testing system so I am at a loss unless someone else can duplicate this.  It may have something to do with the Unity desktop since the reporter's system is Ubuntu 16.04.  Anyone else out there using Ubuntu 16.04 that can confirm this?
1825186,2021-02-19 19:50:30 UTC,"I can see autopkgtest completing successfully for most archs on http://autopkgtest.ubuntu.com/packages/g/gnupg2 for the new Bionic release, so I'll mark this as verified."
1825186,2021-02-22 16:57:58 UTC,This bug was fixed in the package gnupg2 - 2.2.4-1ubuntu1.4
1825186,2021-02-22 16:47:58 UTC,"The verification of the Stable Release Update for gnupg2 has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825186,2021-02-22 15:14:12 UTC,"Autopkgtest failures for gnupg2 on armhf have been fixed with a re-run, so it was likely due to a flaky testbed setup."
1825186,2021-02-15 17:00:05 UTC,"All autopkgtests for the newly accepted gnupg2 (2.2.4-1ubuntu1.4) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1825186,2019-04-17 17:41:09 UTC,nothing in ubuntu uses gpgv-win32 it's added and used in debian to validate debian cds on windows and we don't care.
1825186,2019-06-14 21:59:28 UTC,"An upload of gnupg to xenial-proposed has been rejected from the upload queue for the following reason: ""fixing tests only does not fit the SRU policy""."
1825186,2019-05-25 03:58:01 UTC,"An upload of gnupg2 to cosmic-proposed has been rejected from the upload queue for the following reason: ""fixing tests only does not fit the SRU policy""."
1825186,2019-05-25 03:57:07 UTC,"An upload of gnupg2 to bionic-proposed has been rejected from the upload queue for the following reason: ""fixing tests only does not fit the SRU policy""."
1825186,2019-05-02 07:40:05 UTC,"This is not a regression in any stable releases, failing tests is not a problem at all. As release and SRU processes only consider regressions (previously passed, now failing). Things that have always failed are treated as such by proposed-updates and the rest of the tooling (""always failed""). This is exactly the same as FTBFS - only regressions count, and we have many packages that have never built on certain arches."
1825186,2019-04-17 13:51:37 UTC,"i'm marking for disco (as well as b/c where it fails) because i think it would be better to add the test back in and get it working, instead of just removing it"
1825186,2021-02-15 10:17:05 UTC,"Hello Dan, or anyone else affected,"
1825189,2019-06-28 14:36:06 UTC,This bug was fixed in the package partman-multipath - 4ubuntu7
1825189,2019-06-28 13:44:54 UTC,So i think i undid all the bogus red-herring fixes that didn't fix anything.
1825189,2019-06-19 05:20:42 UTC,"According to our conversation and a quick test on eoan the initial issue reported by me seemed to be solved - and I just touched the project entry.
But since you mentioned that you discovered further issues, and more packages were added as being affected, I'll leave further updates up to you."
1825189,2020-01-27 06:28:38 UTC,"Since Ubuntu 19.04 / Disco reached it's end-of-life on January the 23rd:
https://lists.ubuntu.com/archives/ubuntu-announce/2020-January/000253.html
the entry that marks this ticket as affecting 'Disco' is changed to 'Won't Fix'
and with that the overall status adjusted, too."
1825189,2019-06-18 22:22:36 UTC,@frank stop marking things as done prematurely. this is far from done at the moment.
1825189,2019-06-18 22:55:02 UTC,Also my parted upload is broken!
1825189,2019-05-21 19:44:28 UTC,This bug was fixed in the package multipath-tools - 0.7.9-3ubuntu2
1825189,2019-06-22 01:01:19 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1825189,2019-06-18 10:17:54 UTC,This bug was fixed in the package partman-base - 206ubuntu2
1825189,2019-06-18 12:36:22 UTC,This bug was fixed in the package parted - 3.2-25ubuntu1
1825189,2019-05-22 08:44:23 UTC,"Next steps is to try to use eoan debian-installer, to see if this is now good or not."
1825192,2019-04-17 21:31:29 UTC,"Hi Hildo,"
1825192,2019-04-17 21:47:31 UTC,"True, sorry. It was fallback."
1825192,2019-04-17 23:07:08 UTC,No worries.  Let me know if it works for you when you get the new code.
1825192,2019-04-18 21:19:04 UTC,Appear that last server built version still 16-04-2019. No new with this fix.
1825192,2019-04-17 20:40:23 UTC,"A modern tool's activation routine de-activates other tools.  Legacy tools don't do this, so the last-selected modern tool will get ""stuck"" until another modern tool is chosen."
1825192,2019-04-17 21:16:38 UTC,I just test now. The issue happens in both: legacy and modern.
1825194,2019-05-06 08:46:22 UTC,"Thanks Robie, good catch. Please find attached the new patch for xenial: I have moved a bit below the call to flock to ensure the dir was created - the lines now out of the lock do not change any files so that should not be a problem."
1825194,2019-05-23 09:26:00 UTC,"The verification of the Stable Release Update for resolvconf has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825194,2019-05-23 09:25:57 UTC,This bug was fixed in the package resolvconf - 1.78ubuntu7
1825194,2019-05-16 15:23:13 UTC,"I have tested on xenial, the problem is solved with the change."
1825194,2019-05-15 12:55:20 UTC,"On Wed, May 15, 2019 at 12:42:24PM -0000, Steve Langasek wrote:

> Per
> https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/comments/4,
> I believe this is ""uninteresting"" to fix for releases other than xenial;
> xenial needs it because UC16 is netplan+resolvconf and may have both
> networkd and NetworkManager backends on some devices, UC18 does not use
> resolvconf, and Ubuntu 18.04 classic is unlikely to have users making use of
> resolvconf+netplan (since resolvconf is only present by default on upgrade
> for users who have their network configured using ifupdown).
"
1825194,2019-05-15 12:42:24 UTC,"On Wed, May 15, 2019 at 12:22:20PM -0000, Robie Basak wrote:

> Unsubscribing ~ubuntu-sponsors.
"
1825194,2019-05-15 12:22:20 UTC,Unsubscribing ~ubuntu-sponsors.
1825194,2019-05-15 12:21:44 UTC,"Hello Alfonso, or anyone else affected,"
1825194,2019-05-01 17:46:15 UTC,"On Wed, May 01, 2019 at 05:25:22PM -0000, Robie Basak wrote:

> Will this also need addressing in the development release?
"
1825194,2019-05-02 10:24:13 UTC,"An upload of resolvconf to xenial-proposed has been rejected from the upload queue for the following reason: ""Needs adjustment; see https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/comments/11""."
1825194,2019-05-01 16:03:56 UTC,"Thanks Robie, that's a very good point and something I didn't notice while sponsoring.  Alfonso, do you want to adjust the patch to address this?  (That will also give us a chance to reupload the SRU and remove the misapplied diff cruft.)"
1825194,2019-04-17 16:22:08 UTC,"The attachment ""debdiff.patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1825194,2019-05-01 17:25:22 UTC,Will this also need addressing in the development release?
1825194,2019-04-18 05:24:18 UTC,"I assume this is primarily an issue for UC16, since in UC18 we no longer use resolvconf at all, and have targeted the bug accordingly.  Do you want to prepare a corresponding debdiff for xenial, and adjust the bug description to include a complete SRU template per https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ?"
1825194,2019-04-18 06:33:23 UTC,This bug was fixed in the package resolvconf - 1.79ubuntu13
1825194,2019-04-20 21:40:31 UTC,Unsubscribing the Sponsors Team because there is no SRU bug template yet.
1825194,2019-04-17 17:28:42 UTC,@Alfonso
1825194,2019-04-22 07:39:19 UTC,"@vorlon, @tsimonq2, patch for xenial attached, and description changed for SRU. Sponsors teamm re-subscribed."
1825194,2019-04-22 22:50:08 UTC,uploaded to the SRU queue.
1825194,2019-04-22 22:50:43 UTC,(please note that the changelog had to be adjusted; the current version of resolvconf in xenial-updates is 1.78ubuntu6.)
1825194,2019-05-01 14:00:12 UTC,"Review question: what ensures that /run/resolvconf exists before flock is called? I only see an ""mkdir -p"" inside the block, not outside it. flock doesn't seem to create parent directories automatically in my test, and I don't see a tmpfiles.d entry."
1825194,2019-04-22 07:36:52 UTC,Patch for xenial.
1825197,2019-07-22 03:50:05 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1825197,2019-04-18 06:21:38 UTC,"Thanks for the feedback!
I just send in the report collected by apport-collect, hope it helps."
1825197,2019-04-18 06:18:51 UTC,apport information
1825197,2019-04-18 02:32:42 UTC,Thanks for the bug report. I have encountered the same problems myself this week when stress testing parts of gnome-shell. But those parts and the cause might be different to yours. So please run:
1825197,2019-04-18 06:18:50 UTC,apport information
1825197,2019-04-18 06:18:48 UTC,apport information
1825197,2019-04-18 06:18:50 UTC,apport information
1825197,2019-04-18 02:35:03 UTC,"As far as I can tell, the common error (from gjs):"
1825200,2019-04-19 14:47:12 UTC,The items are (currently) aligned to the target according the following rule:
1825200,2019-04-19 21:00:04 UTC,"Thanks John,"
1825200,2019-04-27 18:29:43 UTC,"Is there a bug here, or is it a misunderstanding?"
1825200,2019-06-27 04:17:28 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1825204,2019-04-19 14:38:26 UTC,Still present at version 5.1.0-unknown-2bcf38d~82~ubuntu16.04.1.
1825206,2019-05-01 21:17:38 UTC,Verification-done for cosmic:
1825206,2019-05-06 18:48:32 UTC,Verification-done for bionic:
1825206,2019-05-08 00:00:42 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
1825206,2019-05-08 00:01:06 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825206,2019-05-08 00:01:20 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
1825206,2019-05-09 22:02:55 UTC,"Hello Marc, or anyone else affected,"
1825206,2019-05-09 21:57:38 UTC,"Hello Marc, or anyone else affected,"
1825206,2019-05-09 22:00:02 UTC,"Hello Marc, or anyone else affected,"
1825206,2019-05-10 17:31:51 UTC,This is still verification-done; has not changed in releases: this SRU is a backport that includes the same upstream patch as what was previously cherry-picked in the previous round of SRUs; hence it appearing again in changelog.
1825206,2019-05-20 08:29:26 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~19.04.1
1825206,2019-05-20 08:42:25 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.10.1
1825206,2019-05-20 08:47:57 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.04.1
1825206,2019-05-08 00:02:21 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu4.1
1825206,2019-05-01 14:00:55 UTC,I can confirm that Gnome now displays the device even if 01-netcfg.yaml exists.
1825206,2019-05-01 18:10:33 UTC,Marc;
1825206,2019-04-30 21:06:00 UTC,"Hello Marc, or anyone else affected,"
1825206,2019-04-18 21:41:31 UTC,Could you add your journalctl log from a boot with the old and one with the new version?
1825206,2019-04-30 21:59:25 UTC,"Hello Marc, or anyone else affected,"
1825206,2019-04-18 23:49:29 UTC,"You also specifically mention /etc/netplan/01-netcfg.yaml, which is only meant to be created by netcfg when using the di-based server install ISO.  How did you install this system?"
1825206,2019-04-19 10:08:34 UTC,apport information
1825206,2019-04-19 10:08:35 UTC,apport information
1825206,2019-04-19 10:08:36 UTC,apport information
1825206,2019-04-18 22:56:04 UTC,"> EDIT: I've verified that I can add my wifi credentials
> to /etc/netplan/01-netcfg.yml and after a reboot the wifi
> connects successfully. The only thing not working is the
> Gnome integration.
"
1825206,2019-04-19 10:41:11 UTC,"I also cloned the gnome-control-center project and built it with debugging statements, and found that the found wifi device isn't chosen because it appears as unmanaged:"
1825206,2019-04-19 10:25:45 UTC,"> Prior to this edit, what were the contents of /etc/netplan?
"
1825206,2019-04-30 20:50:44 UTC,"Hello Marc, or anyone else affected,"
1825206,2019-04-30 18:20:26 UTC,This bug was fixed in the package netplan.io - 0.96-0ubuntu5
1825206,2019-04-19 10:51:36 UTC,"> You also specifically mention /etc/netplan/01-netcfg.yaml, which is only meant to be created by netcfg when using the di-based server install ISO.
"
1825206,2019-04-19 17:14:31 UTC,"I don't havae that particular file no, here's the tree of that directory:"
1825206,2019-04-19 16:57:53 UTC,This is independent of the the netplan.io issue but I'm curious to know if you have '/var/log/installer/media-info' on your installed system. If you do could you please provide the contents of it? Thanks!
1825206,2019-04-19 20:48:06 UTC,"> I installed Ubuntu cosmic via the netboot ISO.
"
1825208,2019-04-18 08:14:35 UTC,"Thank you for your bug report, that has been reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/305 and you should better comment there about your usecase (having a faulty battery is probably not going to convince them to add values that are not useful to most users though)"
1825210,2019-04-17 16:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825210,2019-04-26 15:35:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1825210,2019-04-27 11:31:42 UTC,"yes, the kernel contains the new kernel modules for vbox, thanks!"
1825210,2019-05-06 09:07:23 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825210,2019-05-06 12:59:14 UTC,"The bionic package contains the change!
(its linux-hwe-edge)"
1825210,2019-05-14 19:06:48 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1825210,2019-04-18 13:18:52 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100221.html
1825211,2019-07-04 12:30:23 UTC,"Marking trigger bugs as duplicates of 1828639, to have one bug to track the fix in with a clean reproducer."
1825211,2019-05-10 23:11:13 UTC,"I was able to recreate this today by taking a stock cosmic lxc image, installing ubuntu-mate-desktop, and then upgrading to disco.  Here's the DuplicateSignature from the crash:"
1825211,2019-05-31 19:55:17 UTC,Hi Brian:
1825211,2019-05-03 19:51:47 UTC,Julian had asked about events in term.log surrounding unpacking openssl. Here's what I found:
1825211,2019-04-22 22:13:32 UTC,Attached is my dpkg.log file from the incident.
1825211,2019-04-22 20:12:14 UTC,"Let's reassign to dpkg, this is not caused by menu; and happens during dpkg --configure-pending"
1825211,2019-05-31 19:08:50 UTC,The following bug report looks very similar to this one:
1825211,2019-04-22 06:28:24 UTC,this error causes termination of upgrade from 18.10 -> 19.04
1825211,2019-04-18 21:12:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825211,2019-04-22 13:35:48 UTC,Happened during upgrade from 18.10 to 19.04 but the system did update with nothing catastrophic obvious
1825212,2019-05-11 08:19:15 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825212,2019-05-11 08:21:40 UTC,"I can confirm this bug in Disco. It prevents to use application ""Datovka"". Exactly same problem as in Debian and Fedora. See https://gitlab.labs.nic.cz/datovka/datovka/issues/410"
1825212,2019-05-31 10:22:15 UTC,"Hello Dimitri, or anyone else affected,"
1825212,2019-06-01 22:17:38 UTC,"Fixed in Eoan
---"
1825212,2019-06-06 15:08:56 UTC,"I can confirm that 1.1.1b-1ubuntu2.1 from disco-proposed or 1.1.1b-2ubuntu1 from Eoan fixies this.
Thanks a lot!"
1825212,2019-06-10 14:41:02 UTC,This bug was fixed in the package openssl - 1.1.1b-1ubuntu2.1
1825212,2019-06-10 14:41:08 UTC,"The verification of the Stable Release Update for openssl has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825213,2019-04-27 09:41:18 UTC,similar problem here
1825213,2019-05-30 02:10:01 UTC,I've applied the suggested fix. Please confirm with git master and I'll get a release out soon.
1825213,2019-05-31 10:54:48 UTC,"Good work.
Thank you very much."
1825213,2019-06-01 03:42:08 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1825213,2019-04-22 11:50:11 UTC,"Hello, i had kinda the same problem and for me changing the system language to English worked."
1825213,2019-05-28 14:07:39 UTC,Hi
1825214,2019-04-19 23:05:24 UTC,"I suspect this is not expected behavior of the package and so I'm tagging the distribution, if that turns out not to be the case we can fix the documentation."
1825214,2019-04-19 22:49:29 UTC,"Is this for Stein, on Ubuntu Bionic?"
1825218,2019-04-17 17:47:16 UTC,"Looking at the versions of strace, xenial has 4.11, trusty 4.8 and bionic 4.21. Upstream is very active: https://github.com/strace/strace/commits/v4.21 but while bionic has 4.21, if I remove strace from xenial and snap install strace-static --edge, I get 4.23 and similar behavior, so there is something more going on:"
1825218,2019-09-25 12:37:44 UTC,I ran into this issue myself while working with the field and certification sprints during the Malta engineering sprint. I think we should either default to strace-from-snap or at least detect when strace is too old for the running kernel.
1825222,2019-11-19 19:52:51 UTC,"Hi,"
1825222,2019-08-02 06:50:44 UTC,Hello
1825222,2019-08-06 03:00:16 UTC,"Hi,
4.18 will reach EOL soon, the HWE stack will move to 5.0 kernel. I will add support to this instead."
1825222,2019-08-06 10:13:55 UTC,"This is the 5.0 test kernel for Disco, please give it a try:
https://people.canonical.com/~phlin/kernel/lp-1825222-rockchip-arm64/D/"
1825222,2019-11-16 19:43:48 UTC,"Hi,"
1825222,2019-11-19 10:38:22 UTC,"Hi Paweł,"
1825222,2019-04-18 03:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825222,2019-08-02 04:18:27 UTC,"Hello,"
1825222,2019-11-20 06:25:11 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-November/105575.html
1825222,2019-12-03 15:44:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825222,2019-12-05 11:27:37 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1825222,2020-01-06 12:53:38 UTC,This bug was fixed in the package linux - 5.3.0-26.28
1825222,2020-01-06 13:12:44 UTC,This bug was fixed in the package linux - 5.0.0-38.41
1825222,2020-01-06 13:26:17 UTC,This bug was fixed in the package linux - 4.15.0-74.84
1825222,2020-01-06 22:31:20 UTC,This bug was fixed in the package linux - 5.4.0-9.12
1825222,2019-12-03 15:42:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1825222,2019-04-18 18:00:31 UTC,I'm not able to add any logs since rockchip support is not enabled in ubuntu 18.04 armhf and aarch64 kernels.
1825224,2019-05-03 09:42:39 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825224,2019-04-19 16:44:35 UTC,"Sadly, there is nothing in the terminal output or in journalctl. It seems as though the username/password dialog box takes the input, but then the ""Add"" button fails to become active. Reproducible every time."
1825224,2019-04-18 08:22:50 UTC,"Thank you for your bug report. Can you add the journalctl log from the session where you add the issue?
(or remove the calendar, start gnome-calendar from a command line, try to add the ics and copy any warning/error which is printed out)"
1825224,2019-05-03 09:20:27 UTC,I think the other bug report you meant to point to is actually bug #1825227.
1825224,2019-05-03 09:46:51 UTC,"The same problem here with Ubuntu 18.04. Pushing the ""Add"" button after giving a caldav address to the gnome-calender isnt possible."
1825224,2019-05-03 10:53:14 UTC,could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-calendar/issues ?
1825224,2019-05-03 09:43:54 UTC,"This affects me too. I am on ubuntu 18.04 lts. Trying to add a caldav url to gnome-calender, the app doesnt let me push the button ""add"", although I am pretty sure the url is correct.
My caldav provider is www.posteo.de"
1825224,2020-09-16 15:28:35 UTC,Closing as fix released since this was fixed around the time of Gnome 3.34.
1825224,2019-05-03 16:14:23 UTC,"@seb128 Sorry for the noise, but looks like someone else discovered it as well."
1825224,2019-05-03 16:09:15 UTC,"@seb128 I thought I already had? Maybe that was the other bug. Either way, will do and will link here."
1825224,2019-05-03 16:06:19 UTC,"@tomreyn Yes, you are correct. Fixed as such."
1825227,2019-04-19 16:22:18 UTC,Added upstream bug https://gitlab.gnome.org/GNOME/gnome-calendar/issues/376
1825227,2019-04-23 12:23:32 UTC,Thanks
1825227,2019-04-18 08:29:25 UTC,Thank you for your bug report. Could you maybe report that problem upstream directly on https://gitlab.gnome.org/GNOME/gnome-calendar/issues ?
1825228,2019-08-05 10:08:00 UTC,"The verification of the Stable Release Update for kpatch has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825228,2019-08-05 10:07:56 UTC,This bug was fixed in the package kpatch - 0.5.0-0ubuntu1.1
1825228,2019-08-05 09:47:35 UTC,ii  kpatch-dkms                          0.5.0-0ubuntu1
1825228,2019-07-24 19:29:23 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1825228,2019-04-24 17:35:48 UTC,"Hello Thadeu, or anyone else affected,"
1825229,2019-05-14 19:03:43 UTC,This bug was fixed in the package linux-oracle - 4.15.0-1013.15
1825229,2019-04-17 20:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825229,2019-05-14 19:10:35 UTC,This bug was fixed in the package linux-oracle - 4.15.0-1013.15~16.04.1
1825229,2019-04-22 12:47:04 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100252.html
1825231,2019-11-02 03:16:41 UTC,This relates to bug #1826284
1825231,2020-04-01 18:23:04 UTC,https://reviews.mahara.org/#/c/9800/
1825232,2019-04-17 20:00:53 UTC,"Since `2ping --srv` requires dnspython, the .deb package should recommend python-dnspython as well."
1825234,2019-04-17 23:37:14 UTC,I tried recreating this with an upgrade from Cosmic to Disco today and was unable to. I then restored the apt-clone file in this report to at test system (minus some packages from PPAs) and again was unable to recreate the issue when upgrading from Cosmic to Disco. That being said looking at the dmesg log file this doesn't look great:
1825234,2019-04-17 23:39:31 UTC,Is there a /var/log/dist-upgrade/screenlog.0 file on the system at all?
1825234,2019-06-17 04:17:48 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825235,2019-07-29 09:27:08 UTC,Too bad that the fix mentioned in Comment #4 is now crashing my raspi2 on boot with a kernel panic :(
1825235,2019-04-17 21:00:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1825235,2019-04-19 14:24:46 UTC,I can reproduce the bug on a fresh installation of Disco/armhf rpi3.
1825235,2019-06-16 16:42:29 UTC,This is reported upstream: https://github.com/raspberrypi/linux/issues/2881
1825235,2019-07-22 20:18:54 UTC,This bug was fixed in the package linux-raspi2 - 5.0.0-1013.13
1825239,2019-04-18 22:23:58 UTC,"Re:#9, We have updated the instructions in the Ubuntu Advantage KB to specify upgrading apt versions first."
1825239,2019-04-19 16:02:54 UTC,"The verification of the Stable Release Update for ubuntu-advantage-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825239,2019-04-19 16:02:49 UTC,This bug was fixed in the package ubuntu-advantage-tools - 10ubuntu0.14.04.3
1825239,2019-04-18 19:08:35 UTC,"To verify the key, you can add this to sources.list and run apt-get update, it will complain about a missing key (if you don't have it), and you can then use it and verify the complaint is gone."
1825239,2019-04-18 19:13:44 UTC,"> I would suggest that we don't enable -updates at this stage,
> and defer that until the new client lands.
"
1825239,2019-04-18 19:21:49 UTC,I have verified the authenticity of ubuntu-esm-v2-keyring.gpg by this method:
1825239,2019-04-18 20:03:28 UTC,"Thanks for the review, re-uploaded with the fix to prevent re-enabling esm with it's already enabled."
1825239,2019-04-18 20:15:08 UTC,"Hello Andreas, or anyone else affected,"
1825239,2019-04-18 20:40:24 UTC,"Tested: 10ubuntu0.14.04.3 from direct deb download on ubuntu-daily:14.04 LXD
Verified it doesn't show as not available anymore.
Enabled and was able to install ansible from ESM."
1825239,2019-04-18 18:54:00 UTC,"Thanks, questions about this upload:"
1825239,2019-04-18 21:01:26 UTC,All working here.  Direct download of: ubuntu-advantage-tools_10ubuntu0.14.04.3_all.deb
1825239,2019-04-18 22:02:47 UTC,We found a case there installing esm packages will fail with a 401.
1825245,2019-09-05 23:24:40 UTC,"There is a side effect/tradeoff to not having the parts selection available from the ""replace barcodes"" screen."
1825245,2019-09-06 13:27:44 UTC,PINES libraries don't have required stat cats so do not have this issue. I much prefer having the interface to assign parts away from the replace barcode interface. This makes it more clearly a cataloging function. I would prefer a solution that keeps that distinction but doesn't negatively impact required stat cats.
1825245,2019-10-04 18:08:42 UTC,"We're completely fine if the interface for this is kept separate from replacing barcodes.  The only relation between the two activities is that they are together in the XUL client, and it works.  While they aren't in the web client, and it doesn't work."
1825245,2019-04-18 19:05:48 UTC,"I found that this is the case as well, however in the XUL client, when you used ""Replace barcode"" to actually replace barcodes, if you didn't re-choose the part for every item/barcode, the parts were removed from the items. This really messed things up when the patron had placed a part hold while the item was on order, but Acquisitions had (unknowingly) removed the parts when they received the items."
1825248,2019-11-13 16:37:54 UTC,"Yes, we're using accelerated graphics mode."
1825248,2019-04-17 22:19:26 UTC,"Probably we are running into GAL limitations here.  I have also seen these slowdowns when I was doing performance testing last year.  If any developers feel like diving into the graphics stack, we clearly have some work to do here to optimize things.  GerbView is kind of a worst-case stress test since Gerber layers can have way more graphics data than the equivalent PcbNew objects that generate them."
1825248,2019-11-13 16:39:54 UTC,One of our engineers also submitted a related bug that appears to duplicate this one;
1825248,2019-04-19 00:48:44 UTC,"Victor, it sounds like you are seeing both PcbNew and GerbView slowdowns since the 5.1 release?  They both use the same underlying graphics engine, so maybe that is a clue.  I assume you are using accelerated graphics mode?"
1825248,2019-04-18 23:37:41 UTC,"Dear Jeff,"
1825248,2019-04-17 23:08:39 UTC,I do mean to profile this at some point.  It's slow for me even on the first Gerber.
1825249,2019-06-03 04:05:35 UTC,"No, I haven't done that."
1825249,2019-06-02 11:31:33 UTC,Just providing some feedback as there have been no comments here for 6 weeks or so. I don't any garbled text here using the following:
1825250,2019-05-08 20:47:08 UTC,"Hello Heitor, or anyone else affected,"
1825250,2019-05-10 15:03:11 UTC,Verified resource-agents from xenial-proposed according to test case from description:
1825250,2019-04-23 19:26:11 UTC,"Sponsored for 'eoan' considering that the:
1) Both upstream fixes are merged upstream
2) Bug is reported in debian against resource-agents (debbugs #927311)
3) Eoan is now open (#ubuntu-release topic: ... Archive: Open | Eoan Release Coordination...)"
1825250,2019-04-23 20:23:22 UTC,"The attachment ""lp1825250-eoan.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1825250,2019-04-26 14:20:50 UTC,This bug was fixed in the package resource-agents - 1:4.2.0-1ubuntu2
1825250,2019-04-28 18:52:17 UTC,Unsubscribing sponsors because there is nothing else to sponsor.
1825250,2019-05-08 20:50:42 UTC,"Hello Heitor, or anyone else affected,"
1825250,2019-05-08 20:36:19 UTC,"Hello Heitor, or anyone else affected,"
1825250,2019-05-08 20:44:48 UTC,"Hello Heitor, or anyone else affected,"
1825250,2019-05-16 08:50:39 UTC,This bug was fixed in the package resource-agents - 1:4.2.0-1ubuntu1.1
1825250,2019-05-16 08:50:44 UTC,"The verification of the Stable Release Update for resource-agents has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825250,2019-05-16 10:20:30 UTC,This bug was fixed in the package resource-agents - 1:3.9.7-1ubuntu1.1
1825250,2019-05-16 08:49:35 UTC,Excellent. Thank you for the detailed verification and autopkgtest regression investigation. It's so satisfying to see competent SRU handling - makes everyone's work much easier. Hinted the failure. Thanks!
1825250,2019-05-14 19:14:13 UTC,Quick note on the autopkgtest regression for resource-agents:
1825250,2019-05-14 19:05:26 UTC,"# NOTE
Due to bug 1826045, I've done the test below with a patched version of pcs to work around the pacemaker/pcs version problems. The pcs package does not affect the resource-agents SRU, and is only used for an easy, straightforward reproducer.
#"
1825250,2019-05-16 09:20:06 UTC,This bug was fixed in the package resource-agents - 1:4.1.1-2ubuntu1
1825250,2019-05-10 15:46:11 UTC,"Verified resource-agents from cosmic-proposed according to test case from description. The WARNING messages about monitoring failure are fine, as long as we don't get ""WARNING: Interface virbr0-nic does not exist""."
1825250,2019-05-10 15:36:20 UTC,"Verified resource-agents from bionic-proposed according to test case from description. The WARNING messages about monitoring failure are fine, as long as we don't get ""WARNING: Interface virbr0-nic does not exist""."
1825250,2019-05-16 09:47:51 UTC,This bug was fixed in the package resource-agents - 1:4.1.0~rc1-1ubuntu1.1
1825254,2019-04-17 22:46:48 UTC,"core18 seems to be missing the bash-completion package.
It's also missing a symlink in /usr/share/bash-completion/completions/
to
/snap/snapd/current/usr/share/bash-completion/completions/snap
so that snap itself can tab-complete."
1825254,2019-04-17 22:59:26 UTC,This is also https://github.com/snapcore/core18/issues/89.
1825255,2020-06-25 13:38:39 UTC,"[2020-06-25T12:44:42.094Z] ERROR: maasserver.tests.test_listener.TestPostgresListenerService.test_calls_handler_on_notification
[2020-06-25T12:44:42.094Z] ----------------------------------------------------------------------
[2020-06-25T12:44:42.094Z] Traceback (most recent call last):
[2020-06-25T12:44:42.094Z] testtools.testresult.real._StringException: Twisted logs: {{{Listening for database notifications.Connection closed.}}}
[2020-06-25T12:44:42.094Z]
[2020-06-25T12:44:42.094Z] Traceback (most recent call last):
[2020-06-25T12:44:42.094Z]   File ""/run/build/maas/src/maastesting/runtest.py"", line 126, in _run_user
[2020-06-25T12:44:42.094Z]     result = function(*args, **kwargs)
[2020-06-25T12:44:42.094Z]   File ""/run/build/maas/.ve/lib/python3.6/site-packages/testtools/testcase.py"", line 719, in _run_test_method
[2020-06-25T12:44:42.094Z]     return self._get_test_method()()
[2020-06-25T12:44:42.094Z]   File ""/usr/lib/python3/dist-packages/crochet/_eventloop.py"", line 461, in wrapper
[2020-06-25T12:44:42.094Z]     return eventual_result.wait(timeout)
[2020-06-25T12:44:42.094Z]   File ""/usr/lib/python3/dist-packages/crochet/_eventloop.py"", line 231, in wait
[2020-06-25T12:44:42.094Z]     result.raiseException()
[2020-06-25T12:44:42.094Z]   File ""/usr/lib/python3/dist-packages/twisted/python/failure.py"", line 385, in raiseException
[2020-06-25T12:44:42.094Z]     raise self.value.with_traceback(self.tb)
[2020-06-25T12:44:42.094Z]   File ""/usr/lib/python3/dist-packages/twisted/internet/defer.py"", line 1386, in _inlineCallbacks
[2020-06-25T12:44:42.094Z]     result = g.send(result)
[2020-06-25T12:44:42.094Z]   File ""/run/build/maas/src/maasserver/tests/test_listener.py"", line 200, in test_calls_handler_on_notification
[2020-06-25T12:44:42.094Z]     yield dv.get(timeout=2)
[2020-06-25T12:44:42.094Z] twisted.internet.defer.CancelledError"
1825256,2019-04-17 23:28:05 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9805"
1825256,2019-05-01 03:28:48 UTC,TITLE:  The Manage -> Export page radio buttons alignment need to be better
1825256,2019-08-13 02:23:38 UTC,"Reviewed:  https://reviews.mahara.org/9805
Committed: https://git.mahara.org/mahara/mahara/commit/3a09a2e4e3b17c99afc462765e7d1bdfdc8d3210
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1825257,2019-04-18 00:08:38 UTC,I wish there was a Ubuntu PPA I could use to get the latest version of thg
1825258,2019-04-18 00:01:17 UTC,"Attempted to install again & got error flag right away,
""ubi-partman failed with exit code 10. Further information may be found in /var/log/syslog. Do you want to try running this step again before continuing? / . . ."""
1825261,2019-04-18 11:53:42 UTC,This was a very small thing and got fixed fast.
1825262,2019-04-18 07:50:04 UTC,"Thank you for your bug report, the error is
'grub-install: error: efibootmgr failed to register the boot entry: Block device required.'"
1825262,2019-06-18 04:17:26 UTC,[Expired for grub-installer (Ubuntu) because there has been no activity for 60 days.]
1825263,2019-04-29 17:12:42 UTC,"OK, thanks. Let's treat this report as exactly what I've renamed the subject line to then, since that's something that is reproducible today and can be directly addressed."
1825263,2019-04-29 16:48:51 UTC,Indeed that is the current behavior. I wouldn't have thought the packages updated in the last few days would have impacted this ... but clearly something has changed!
1825263,2019-04-29 16:11:57 UTC,"In your example it is the ""uvt-kvm wait"" that fails when there is a second NIC, not ""uvt-kvm ssh"", contrary to your original summary. Is this accurate?"
1825263,2019-04-29 15:48:07 UTC,"uvt-kvm create --memory 1024 --ephemeral-disk 8 dualb
superMkhb:/home/khb>uvt-kvm wait dualb
superMkhb:/home/khb>uvt-kvm ssh dualb
Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-48-generic x86_64)"
1825263,2019-04-29 11:01:58 UTC,Thank you for your report.
1825263,2019-04-18 00:01:22 UTC,"Sorry, neglected:
uvtool:
  Installed: 0~git140-0ubuntu1"
1825264,2019-04-29 17:07:05 UTC,"On Mon, Apr 29, 2019 at 04:43:59PM -0000, khb wrote:

> so make the $DOM: mandatory ... then just what complexity of the ""shim
> script"" am I missing? All it would appear to have to do is translate
> $DOM into $IP. globbing and any other shell dependent behavior remains
> shell (and scp) dependent behavior.
"
1825264,2019-04-18 15:21:10 UTC,"A little context. uvt is great for taking existing cloud projects local. The use-case(s) I'm evaluating it's use for is the other direction. Legacy apps (the most pessimal I've dealt with was primos->vms->unix(es)->linux ...) such projects tend to iterative layers of archeological discovery. Having a bunch of persistent tools can be accommodated by mounting a second volume ... but often results in prolonging the effort as dependencies on that volume creep in. Also, it's possible to use uvt-kvm create && wait && virsh shutdown && virt-copyin && virsh start ... or etc."
1825264,2019-04-29 10:55:18 UTC,Thank you for the report.
1825264,2019-04-29 16:01:36 UTC,Let's start with what I conjecture is the least difficult case.
1825264,2019-04-29 16:19:56 UTC,"On Mon, Apr 29, 2019 at 04:01:36PM -0000, khb wrote:

> Let's start with what I conjecture is the least difficult case.
>
> uvt-kvm scp $FILELIST $DOM
>
> This would copy $FILELIST from the host into the uvt-kvm managed $DOM
> (using pretty much whatever the wrapper for ssh is ;>).  The trialing
> "":"" could be optional or required (the former allows for a little less
> stress on aged wrists ... but trivially so ...).
"
1825264,2019-04-29 16:43:59 UTC,"so make the $DOM: mandatory ... then just what complexity of the ""shim script"" am I missing? All it would appear to have to do is translate $DOM into $IP. globbing and any other shell dependent behavior remains shell (and scp) dependent behavior."
1825264,2019-04-29 17:45:06 UTC,"that it's not entirely trivial is true; I regret characterizing it as such. If it were entirely trivial, it wouldn't be worth adding to uvt-kvm!"
1825264,2019-06-30 04:17:33 UTC,[Expired for uvtool because there has been no activity for 60 days.]
1825267,2019-04-18 01:38:10 UTC,"Seems this is more than just a matter of syncing charmhelpers, I probably am not the most appropriate person to dive in and fix."
1825267,2021-02-17 19:57:33 UTC,"This line in charmhelpers resolves the ppa issue.  The problem is that some keys are served by http rather than https, and only https proxy vars were being used for add-apt-repository calls in past charmhelpers."
1825267,2019-04-18 04:49:36 UTC,"For Xenial, noting https://github.com/juju/charm-helpers/issues/304 seems to have allowed this to work."
1825268,2019-07-19 19:42:33 UTC,"Just to close this, we haven't had any issues with this version of kicad, and its performance seems to be similar to the previous version."
1825268,2019-04-18 02:32:09 UTC,"130k nets? Waauw!
I have a pretty slow 11 year old PC myself and don't blame KiCad for performance issues. It gets a bit laggy when viewing the Olimexino 64 (example project on Kicad site / github) and it would not be fun to design such a board on my PC though."
1825268,2019-04-18 03:04:57 UTC,"While KiCad has some known shortcomings when it comes to handling very large designs, it's worth investigating this particular case as I'm not aware of a reason why PcbNew would have slowed down significantly between 5.1 and the current nightlies."
1825268,2019-04-18 18:21:16 UTC,"I'm not a developer, but as a normal user who likes to experiment it would be very interesting to try a project with that many layers. Is it proprietary or could you share it?"
1825268,2019-04-18 19:13:14 UTC,"Hi Victor,"
1825268,2019-07-06 21:58:21 UTC,"@Devs, did we ever get board files for this?  I think we could learn a lot from them...."
1825268,2019-07-08 23:46:37 UTC,"Dear Seth,"
1825268,2019-07-19 20:30:45 UTC,"Thanks for reporting back, Victor!"
1825268,2019-07-07 02:14:45 UTC,Yes.  I suspect that this is addressed.  Victor?
1825272,2019-04-26 15:36:05 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1825272,2019-05-17 05:35:57 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1825272,2019-04-18 02:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825272,2019-04-25 22:32:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1825272,2019-04-29 16:03:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825272,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1825272,2019-05-14 19:03:14 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1825272,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1825272,2019-05-14 19:06:48 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1825272,2019-05-14 22:54:50 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825272,2019-05-21 13:04:12 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1825276,2019-04-30 19:10:53 UTC,I can replicate this.
1825276,2019-04-19 12:52:11 UTC,Maybe related to https://bugs.launchpad.net/kicad/+bug/1809845 and https://bugs.launchpad.net/kicad/+bug/1814893
1825276,2019-04-29 19:50:05 UTC,"@Hildo, if possible please post the schematic file that demonstrates this issue or create a minimal sample schematic if you cannot share the original schematic."
1825276,2019-04-29 22:29:56 UTC,"Attached file example, see:
1) Inserted image on the template have alpha and are correct in Eeschema (lp:1809845);
2) Generated PDF at 'output' folder have the above mentioned images black."
1825276,2019-05-01 18:48:38 UTC,This also need to be fix at Pcbnew plot PDF.
1825276,2019-05-27 22:59:54 UTC,"Fixed in revision 0a6b1ea256e2756da4170a32f2914f78e8d7e45e
https://git.launchpad.net/kicad/commit/?id=0a6b1ea256e2756da4170a32f2914f78e8d7e45e"
1825277,2019-04-18 03:20:41 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653649"
1825279,2019-04-18 08:04:55 UTC,What kernel flavor and release is this failing on? I successfully ran that test with the 5.0 generic kernel in Disco.
1825279,2019-04-18 08:16:02 UTC,I'm betting that these tests were ran against Bionic linux-hwe-edge 5.0.0-8.9~18.04.1 but that kernel is quite outdated and is missing a lot of AppArmor and LSM changes that is in the Disco 5.0 release kernel.
1825279,2019-09-16 10:05:41 UTC,"Yes this issue has gone.
Thanks."
1825280,2019-04-18 03:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825280,2019-04-18 08:06:28 UTC,This shouldn't be a blocker to release the B-hwe-edge kernel but it is something that we'll want to fix in that kernel's config soon.
1825280,2019-04-18 08:20:51 UTC,Bionic linux-hwe-edge 5.0.0-13.14~18.04.1 has this config option set. Rerunning this test against that kernel will result in a passing test.
1825280,2019-05-23 20:54:54 UTC,Confirmed that this has been fixed in the linux-hwe-edge kernel config. Closing.
1825284,2019-06-14 01:36:21 UTC,I think most of the related work has been tacked through bug # 1827009. This report may very well be a duplicate.
1825284,2019-06-14 01:19:32 UTC,"We have recently dealt with bugs in the area and the machine agent code lost this code, see https://github.com/juju/juju/blob/2.6/cmd/jujud/agent/machine.go"
1825286,2019-04-18 07:04:13 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1825288,2019-05-13 16:15:38 UTC,"PRs to stable:
https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/22
https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/13"
1825288,2019-04-25 13:48:36 UTC,"https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/5
https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/11"
1825288,2019-04-23 12:46:24 UTC,"> Is this fixable?
"
1825288,2019-04-18 13:12:43 UTC,Can you tell us more about their deployment? Is kubeapi-load-balancer colocated with another unit on the same machine?
1825288,2019-04-23 10:28:40 UTC,"Right, I checked the customer's env"
1825289,2019-06-18 04:17:27 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1825289,2019-04-18 09:13:45 UTC,"Which apps of kicad are effected?
If it is pcb_new/footprint editor are all toolsets effected equally? (modern accelerated, modern fallback and legacy)
Are specific actions more likely then others to cause a freeze? (Is there a way to reliably trigger the freeze?)"
1825290,2019-08-20 01:26:58 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1825295,2019-08-14 18:25:42 UTC,"Reviewed:  https://review.opendev.org/675874
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8e9e0cbe142934e0ea5fe6e5dbf01c3f704d8d54
Submitter: Zuul
Branch:    stable/stein"
1825295,2019-04-19 02:39:36 UTC,"@Yang Li,"
1825295,2019-10-22 19:56:23 UTC,This issue was fixed in the openstack/neutron 12.1.1 release.
1825295,2019-10-22 19:53:19 UTC,This issue was fixed in the openstack/neutron 13.0.5 release.
1825295,2019-10-22 19:44:59 UTC,This issue was fixed in the openstack/neutron 14.0.3 release.
1825295,2019-09-19 10:14:04 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1825295,2019-08-14 22:17:31 UTC,"Reviewed:  https://review.opendev.org/675876
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=eabe3b707a6ff3178670ef5715e26de80d00cae0
Submitter: Zuul
Branch:    stable/queens"
1825295,2019-08-14 22:17:21 UTC,"Reviewed:  https://review.opendev.org/675875
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=56cd50e9d2a16b6823815b8420518978f1a50738
Submitter: Zuul
Branch:    stable/rocky"
1825295,2019-08-12 12:04:55 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/675876"
1825295,2019-08-12 12:04:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/675875"
1825295,2019-05-14 20:43:22 UTC,"Reviewed:  https://review.opendev.org/653668
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=82782d37639fab97e445e4bbb4daeb85dc829fcd
Submitter: Zuul
Branch:    master"
1825295,2019-04-25 02:56:28 UTC,"The bug was resolved in the last version, but not a indirect way, it was fixed because of self.plugin_rpc.register_legacy_notification_callbacks, in this function it will notify the local agent to update the port again, so the port will be handle twice, the second update will refresh firewall rule, and write the port to sg_port_map.
The get_or_create_ofport still remove the port from sg_port_map, and not added it back, perhaps it will be a hidden bug for some other situations."
1825295,2019-04-19 07:35:08 UTC,"Change abandoned by Yang Li (<email address hidden>) on branch: master
Review: https://review.openstack.org/653668"
1825295,2019-04-19 07:34:19 UTC,"My bad, seems the last version will raise an error if VM reboot too quick, the code will enter into 2 loops ,the first loop we get events both include added and updated, but the second loop will handle the port, and add it back to sg_port_map"
1825295,2019-04-19 05:12:31 UTC,"The root cause is VM quick reboot will remove this port from sg_port_map, then migrate/resize will trigger this bug, without reboot, it won't happend. I will add my env and configuration later :)"
1825295,2019-04-19 04:27:41 UTC,"If we do not run 1. and 2., just directly migrate/resize the instance, then the issue still exists?"
1825295,2019-04-18 07:12:22 UTC,"After some investigation, I found when we reboot a instance, the ovsdb-client will get such events.
# ovsdb-client monitor Interface name  ofport external_ids --format=json"
1825295,2019-08-12 12:04:01 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/675874"
1825297,2019-04-19 02:16:29 UTC,"@Sebastien Bacher
The issue submitted: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1185"
1825297,2019-04-18 11:33:56 UTC,Thank you for your bug report. Could you report the bug also upstream on https://gitlab.gnome.org/GNOME/gnome-shell/issues ?
1825297,2019-04-23 02:22:31 UTC,See also bug 1825299
1825297,2019-04-26 01:55:20 UTC,@Sebastien Bacher
1825297,2020-08-18 16:59:59 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1825298,2019-04-18 08:23:39 UTC,Hello
1825298,2019-10-16 06:19:10 UTC,We discussed this issue on IRC and we believe to understand the cause.
1825298,2019-10-16 05:43:38 UTC,Closing the cosmic task as its EOL but keeping the other tasks open.
1825298,2019-10-16 05:43:16 UTC,"I can reproduce this on cosmic, installing snapd and removing (but not purging) snapd gives me this error. It seems like removing removes the /var/lib/snapd/apparmor/snap-confine dir but keeps the /etc/apparmor.d/...snap-confine conf file in place (oh the joy of conffiles)."
1825298,2019-04-18 15:37:57 UTC,"Hi,"
1825299,2019-04-23 02:22:38 UTC,See also bug 1825297
1825299,2020-08-11 09:45:24 UTC,Is this still an issue?
1825299,2019-04-19 02:14:54 UTC,"@Sebastien Bacher
The issue submitted: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1184"
1825299,2019-04-18 11:33:32 UTC,"Thank you for your bug report. Could you report the bug also upstream on https://gitlab.gnome.org/GNOME/gnome-shell/issues ?
Also please specify what session you use and if it's on xorg or wayland (or if that doesn'""t make a difference)"
1825307,2019-04-20 06:21:03 UTC,The zone priority level is quite considerable since board-wide ground fill with same priority level as non ground fill will wreck a whole board incurring disaster if the user ever assembles it after its fabricated. These are likely difficult to prevent without default settings since this tool calls for rapid copper zone laying and without default options the zone priority level issue can occur.
1825307,2019-04-20 06:17:48 UTC,"It seems its worth implementing ""Default Copper Fill Zone"" properties into the Board Setup set of dialogs. Otherwise user might encounter spurious settings and its more ideal to have default options since most zones need a priority level of greater than typical whole board ground fills."
1825307,2019-04-19 11:57:47 UTC,"Could certainly be a relatively ""fluent"" feature."
1825307,2019-04-18 09:26:19 UTC,This is quite a simple but versatile feature request. Especially were boards demand many different fill zones.
1825307,2019-04-18 09:24:09 UTC,What this enables a user to do is rapidly tie pads in close vicinity together with copper fills rather than large round edged traces which overlap to adjoining pads. I constantly use copper fill to tie together close nets and edge nets were there are nets in pluralities coincident to the same netclass.
1825307,2019-04-18 09:00:22 UTC,"I can think of the following usecase for this:
Lets assume one is designing a PCB with some high current paths. One might want to draw these paths with copper zones instead of using traces to get the maximum available width."
1825311,2019-04-24 14:27:49 UTC,"Patch posted on the list:
https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03711.html"
1825311,2019-07-08 15:25:48 UTC,This bug should be fixed by commit 7353113fa482e697a77 now in QEMU master; it will be in the 4.1 release.
1825311,2019-05-17 09:00:37 UTC,Also attaching the 64-bit version of the reproducer.
1825311,2019-04-23 14:48:44 UTC,I am attaching a reproducer image and script.
1825313,2019-04-18 08:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825313,2019-11-13 18:32:36 UTC,Cosmic has transitioned into EOL.
1825314,2019-06-06 03:13:22 UTC,"Reviewed:  https://review.opendev.org/653348
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=e13b74e4a27f0aee25f2efa24646bfaf00f8bee4
Submitter: Zuul
Branch:    master"
1825314,2019-06-12 14:43:40 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1825317,2021-01-20 11:56:17 UTC,"We can do this with prometheus alerting, which we're currently doing here in Canonical IS."
1825318,2019-04-18 21:42:17 UTC,"This should be an easy one, we currently prefix nagios checks with ""site""."
1825321,2019-04-18 21:31:54 UTC,Or make this configurable with the default disabling DHE.
1825325,2019-07-02 10:23:18 UTC,So here's what I have planned for this:
1825325,2019-04-18 21:29:55 UTC,Automatically determine the cache max_size if none provided (something like 70-75% of total disk size since the nrpe charm is configured to alert at 80% by default).
1825325,2019-07-09 11:17:15 UTC,"> firstly, land a small change to allow overriding cache max_size as a charm config option.
"
1825326,2019-04-18 09:11:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653694"
1825330,2019-04-18 09:32:52 UTC,"This can fail for copies to public PPAs too, although the window is narrower in that case."
1825330,2019-04-18 09:36:03 UTC,"Dispatching private builds immediately (https://code.launchpad.net/~cjwatson/launchpad/build-private-bpb-immediately/+merge/345104 and its prerequisite) might help in this case, although only by chance.  While the linux-signed build would initially be dispatched earlier, it would immediately dep-wait because the main linux packages wouldn't have been published yet.  buildd-retry-depwait would retry it once the linux packages had been published, but that currently runs hourly, so it would have a reasonable chance of ending up in a good place."
1825331,2019-04-20 21:57:20 UTC,"KernLog.txt contains several ALLOWED lines for chromium, and also DENIED lines for firefox (unrelated to this bugreport, but nevertheless we should probably check them."
1825331,2019-04-25 09:27:44 UTC,"That's a long list of EPERMs in strace and mostly useless by itself, since chrome make use of nonblocking/asynchronous IO, so you always have to look for the syscall that had caused the EPERM. A full trace is rather huge."
1825331,2019-06-11 22:35:33 UTC,I can reproduce this issue with an AppArmor profile in complain mode for both Firefox 67 and Chromium 74 on ubuntu 18.04
1825331,2019-11-17 10:33:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825331,2019-11-17 10:35:51 UTC,I've the same problem with a not yubikey token (this one: https://www.amazon.it/gp/product/B01LZO0WE9/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1)
1825336,2019-04-22 01:55:07 UTC,@Slawek Kaplonski
1825336,2019-04-25 01:14:31 UTC,Hi forks. I sent initial PoC code for this issue. Please consider the patch below. Any comments would be appricated.
1825336,2019-04-26 03:42:21 UTC,"Hi Yang,"
1825336,2019-04-26 04:54:47 UTC,"Hi Miguel, Thanks for the comment."
1825336,2019-05-30 22:51:40 UTC,"Hi Yang,"
1825336,2019-05-30 23:30:58 UTC,"Sure, thanks for tracking this issue."
1825336,2019-06-06 22:24:53 UTC,"Hi Yang,"
1825336,2019-04-21 22:03:39 UTC,"We already have role based access control for some of resources (like networks or qos policies). We also have ""regular"" policy.json mechanism which can be used to define some access ""levels"" for users.
So I'm affraid if adding 3rd mechanism is really good idea. Maybe we should focus on e.g. improving rbac instead? Or maybe it's completly fine to have both things in place - I really don't know but I think that this should be discussed first :)"
1825338,2019-08-09 21:12:39 UTC,"This looks like an issue with sqlalchemy-migrate, so I'm adding that project to the bug. I'll leave oslo.db on it in case it turns out I'm wrong though."
1825340,2019-05-12 11:09:38 UTC,Looks like the fix from bug #1826400 should resolve this issue too
1825340,2019-04-18 10:17:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825340,2019-05-03 16:42:06 UTC,"Indeed, thanks for your report, I've forwarded it upstream
https://gitlab.gnome.org/GNOME/gnome-calendar/issues/385"
1825340,2019-05-30 14:39:29 UTC,It's the same as bug #1826400 and fixed with https://launchpad.net/ubuntu/+source/gnome-calendar/3.32.2-1~ubuntu19.04.1
1825345,2019-10-11 12:56:09 UTC,"According to my discussion with Zigo on IRC: http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2019-10-11.log.html#t2019-10-11T12:17:45 zigo's proposal is to add ""evacuate"" option for agents. Something like e.g.:"
1825345,2019-10-25 14:10:39 UTC,"According to decission on drivers meeting at 25.20.2019, this RFE is now approved. Thx for proposing it :)"
1825345,2019-10-22 10:13:23 UTC,"Thx for clarification Thomas.
More I'm thinking about it, more I'm convinced that this should be done on server side.
Lets talk one more time about it on drivers meeting."
1825345,2019-10-18 23:49:36 UTC,"Hi,"
1825345,2019-10-18 15:08:47 UTC,i feel it's natural to have it in server as we already have similar things like allow_automatic_dhcp_failover/allow_automatic_l3agent_failover
1825345,2019-10-18 15:08:17 UTC,@Zigo: according to our discussion on last drivers meeting (http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-10-18-14.01.log.html#l-44) we would like to clarify some things about potential new API:
1825345,2019-09-26 20:19:31 UTC,"So IIUC last comments from Miguel and Thomas, it seems that it is only some feature gaps in OpenStack client comparing to python-neutronclient. Is that true? If so, I think this should be reported as bug for OpenStack client instead of rfe for Neutron."
1825345,2019-05-16 22:26:14 UTC,Thanks for your responses. We will discuss it in the drivers meeting
1825345,2019-05-09 22:26:32 UTC,"@Thomas,"
1825345,2019-04-29 07:18:41 UTC,"I just tried in Stein, and to me, network agent remove network / network agent add network doesn't work (or at least, doesn't produce the same as neutron dhcp-agent-network-add/remove). At least, this needs investigation."
1825345,2019-04-26 08:40:47 UTC,@Thomas:
1825345,2019-04-26 07:52:36 UTC,"Hi Miguel,"
1825345,2019-04-26 03:55:43 UTC,"Hi Zigo,"
1825345,2019-04-19 02:49:08 UTC,This looks like an enhancement. I tagged it as RFE
1825345,2019-05-10 06:49:16 UTC,"Miguel,"
1825347,2019-09-25 08:53:45 UTC,This has been fixed in master and will be in 2.7
1825355,2019-05-07 17:17:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825356,2019-04-18 14:05:01 UTC,@James/Corey - have you seen any issue like that in your Ceph usage on queens?
1825356,2019-04-25 10:35:02 UTC,Interesting that you have no cinder-ceph volume at all from libvirt's POV.
1825356,2019-04-29 09:04:18 UTC,"Hi koalinux, please can you provide the requested logs or remove the field-critical tag please ?"
1825356,2019-04-18 14:32:07 UTC,"I have no ceph system around, but I asked for how the storage appears there.
Once I get that back we'd have something to compare."
1825356,2019-04-18 15:13:33 UTC,"This is what I got from a system for comparison:
ubuntu@swirlix33:~$ sudo virsh domblklist instance-000001c3
Target     Source
------------------------------------------------
vda        cinder-ceph/volume-0d816643-f816-4663-8c3f-fe8fde75bc15
vdb        cinder-ceph/volume-4371e9d5-f276-45e5-bf42-1607ad7e523d"
1825356,2019-06-29 04:17:17 UTC,[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]
1825356,2019-06-29 04:17:21 UTC,[Expired for Ubuntu Cloud Archive because there has been no activity for 60 days.]
1825356,2019-06-29 04:17:23 UTC,[Expired for ceph (Ubuntu) because there has been no activity for 60 days.]
1825356,2019-04-25 07:54:36 UTC,"Hi Christian,"
1825356,2019-04-25 19:55:31 UTC,"I wasn't able to recreate this on a bionic-queens deploy. My deployment was a bit different, quite a bit simpler. Results are attached. I did notice that you're using bluestore so it might be worth testing with that. Again logs or a small recreate scenarios will be useful to help us figure this out."
1825359,2019-04-18 12:31:06 UTC,"Yeah, this looks like a bug -- we should pass the access_type through rather than using MMU_DATA_LOAD."
1825359,2019-04-18 13:24:59 UTC,Should I make a patch then?
1825359,2019-04-18 14:11:20 UTC,"call stack for SEGFAULT that happens during the execution of small region. This will go away IF THE ENTRY ADDED TO TLB FOR THIS REGION IS OF SIZE TARGET_PAGE_SIZE. However, that would not be correct behavior."
1825359,2019-04-18 14:11:48 UTC,That should not happen unless you have some device that is incorrectly not providing a suitable read function in its MemoryRegionOps. If you look at 'mr' in the debugger you should be able to figure out which device is the problem.
1825359,2019-04-18 18:26:05 UTC,The problem seems to be this piece of code:
1825359,2019-04-18 18:46:01 UTC,This patch has fixed for me both issues. Although I am not very proud of the changes in the second hunk. Please let me know if there is a better way.
1825359,2019-05-03 16:33:12 UTC,Your patch is now in git master as commit ef5dae6805cce7b59d129 -- thanks!
1825359,2019-05-04 14:39:15 UTC,Thank YOU for all the supports along the way :)
1825359,2019-04-18 13:57:17 UTC,"The patch looks OK code-wise, but could you submit it to the mailing list, please?
https://wiki.qemu.org/Contribute/SubmitAPatch has the details, but the most important part is that it needs a Signed-off-by: line from you that says you have the legal right and are willing to contribute it to QEMU under our license. Otherwise we can't use the patch."
1825359,2019-04-18 14:09:38 UTC,"I have to say, after applying this patch, my test still fails while fetching the instructions from this _small_ region. Although there is no MMU_DATA_LOAD anymore, a few iterations later (while guest code has just jumped to the beginning of the executable region), QEmu segfaults (call stack is attached):"
1825362,2019-06-18 04:17:37 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825362,2019-04-18 17:56:02 UTC,"Your system has many packages which are out of date because you do not have the -updates pocket of the Ubuntu archive enabled. Please enable that, update your system, and try the upgrade again.  Additionally, reviewing your sources.list file you only have the main component enabled in your sources.list file while you have packages installed from other components (e.g. main, universe, multiverse). You'll also likely want to enable those components again so the upgrade will be calculatable."
1825368,2019-05-23 11:57:27 UTC,I assume that the OpenStack CLI (which is an alternative to the glance native CLI in this case) is just failing in this part https://github.com/openstack/python-openstackclient/blob/mitaka-eol/openstackclient/image/v2/image.py#L349 where it tries to get image info after uploading. This is just a cosmetic problem that is not worth inventing re-authorization mechanics in the CLI. There are plenty of workarounds and they all are well known:
1825376,2019-11-06 04:17:40 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1825376,2019-09-06 21:43:08 UTC,I can't reproduce this issue.
1825380,2019-04-18 21:25:46 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1825380,2019-06-18 04:17:38 UTC,[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.]
1825382,2019-05-13 06:08:12 UTC,"Looking at your status log above, I only see s little bit of duplication within a single hook:"
1825385,2019-10-15 13:28:23 UTC,The referenced URL is a 404
1825385,2019-12-15 04:17:40 UTC,[Expired for snapd because there has been no activity for 60 days.]
1825385,2019-12-15 04:17:42 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1825386,2019-04-18 16:32:37 UTC,"Yes, that's a known problem, because Nova hard-codes the OVMF binary file path:"
1825386,2019-05-31 19:32:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662552"
1825386,2019-06-01 19:20:20 UTC,"Reviewed:  https://review.opendev.org/662552
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=739647dffaee468122fa3984ab907c07cb6b9c16
Submitter: Zuul
Branch:    master"
1825386,2019-09-27 09:01:24 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1825386,2019-08-09 12:54:46 UTC,"Reviewed:  https://review.opendev.org/348394
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=363710b655434a15b6b85d9ca65343210b104e56
Submitter: Zuul
Branch:    master"
1825391,2019-04-19 14:36:09 UTC,"Hi Thomas,
Could you give us more details?
Do you mean using OpenGL rendering engine or using Raytracing?"
1825391,2019-04-20 11:35:56 UTC,from my perspective rendering is not really smooth in OpenG.- Ray-tracing is better
1825391,2019-04-22 22:33:33 UTC,"I don't experience so much aliasing as you. (as you can see in the screen-shot attached)
What is your GPU and driver version?"
1825391,2019-05-15 15:13:58 UTC,"Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2)  (0x591b)
    Version: 19.0.3
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.3
OpenGL core profile shading language version string: 4.50"
1825391,2019-05-15 15:35:29 UTC,"Hi Thomas, can you run and take a screenshot for each:
$ glxgears -samples 0
$ glxgears -samples 8"
1825391,2019-05-15 17:52:39 UTC,Huh:
1825391,2019-05-15 19:00:30 UTC,"Oh, there's something there. KiCad tries to apply 8 samples, 4 samples, 2 samples and 0.
Could you try 4 and 2 ?"
1825391,2019-06-26 15:34:32 UTC,I assume XWayland cannot work with antialiasing yet (https://www.phoronix.com/scan.php?page=news_item&px=XWayland-EGL-GLX-Provider)
1825391,2019-08-26 04:17:18 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1825393,2019-04-18 16:42:50 UTC,inital deployment with config
1825393,2019-04-18 17:37:54 UTC,Hi Narinder
1825393,2019-04-18 18:01:20 UTC,Alex I can provide few info not all as we are deploying the environment now.
1825393,2019-04-18 19:37:22 UTC,Thanks Narinda
1825393,2019-04-18 20:00:38 UTC,I agreed Alex and appropriate to have fix no 1.
1825393,2019-04-23 14:13:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655168"
1825393,2019-04-24 13:20:35 UTC,"Reviewed:  https://review.opendev.org/655168
Committed: https://git.openstack.org/cgit/openstack/charm-lxd/commit/?id=4bf72620c3cf9cef5905a07132510df2cec5de41
Submitter: Zuul
Branch:    master"
1825393,2019-04-24 15:28:55 UTC,"Reviewed:  https://review.opendev.org/655470
Committed: https://git.openstack.org/cgit/openstack/charm-lxd/commit/?id=6c61ad42b56866aa1dd5d031fda31b88d92d7c7b
Submitter: Zuul
Branch:    stable/19.04"
1825393,2019-04-24 15:10:15 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/655470"
1825394,2019-09-05 09:11:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825395,2019-04-23 18:26:28 UTC,Thanks for the logs. It seems like the BIOS does not handle S3 exit properly and leaves the Thunderbolt host router unconfigured. I wonder if there is a BIOS upgrade for this system and have you tried that?
1825395,2019-04-18 17:00:07 UTC,This change was made by a bot.
1825395,2019-04-18 17:52:31 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc5 kernel [0]."
1825395,2019-05-07 20:49:52 UTC,"I've come up with a theory that I think matches what I observe.  It seems that my laptop gets into the bad state if I suspend too quickly after hot unplug from thunderbolt.  If I wait long enough after hot unplug that all the thunderbolt devices are fully removed, then the system remains fine.  If I suspend while cleanup is still going on, then upon resume the system confuses itself trying to deal with devices that are no longer there (and that never get cleaned up)."
1825395,2019-04-25 15:18:24 UTC,No BIOS options changed.  I am on X1 Yoga 2nd gen - the BIOS exposes S3 by default.  X1 Yoga 3rd gen is the first Lenovo generation that defaults to S0i3 for suspend.
1825395,2019-04-24 07:46:53 UTC,"BTW, did you enable any Linux specific configuration in the BIOS? For example to enable S3 (many systems I've seen default to s2idle nowadays)."
1825395,2019-04-23 20:40:36 UTC,I see from https://pcsupport.lenovo.com/us/en/downloads/DS506115 that there is a firmware update available for my dock.  I am going to try and borrow a windows system and perform that update.
1825395,2019-04-23 19:20:15 UTC,"No, unfortunately I am on the latest BIOS.  dmidecode reports"
1825395,2019-04-18 20:15:08 UTC,"I will try the upstream kernel, although it will be a few days before I can confidently report if the issue is not present."
1825395,2019-04-23 17:29:59 UTC,"I can boot either connected or not, and the first connection will usually work.  I'd say my more common workflow is to boot away from my dock, use my laptop for a bit, suspend, and go to my desk and resume while docked.  That usually works, but if I then undock, use my laptop for a bit, suspend, come back to my desk and resume, then I hit the PCI issue."
1825395,2019-04-23 06:44:47 UTC,Can you also attach full dmesg of the boot so that we can see the initial PCI configuration? Now all the dmesgs are missing that information.
1825395,2019-04-23 05:00:55 UTC,Subscribing Mika.
1825395,2019-04-22 23:49:35 UTC,Attaching dmesg showing failed thunderbolt attachment.  There is a good hotplug starting with
1825395,2019-04-22 23:31:05 UTC,So I can confirm that this bug happens with upstream build 5.1.0-050100rc5-generic.  Will attach full dmesg.
1825396,2019-05-15 14:03:04 UTC,"OK got it in eoan, will update disco now (might take some time to be processed)."
1825396,2019-04-18 18:53:55 UTC,Marking this as security since the following directory name proves command execution is possible:
1825396,2019-04-18 18:55:11 UTC,"As discussed on IRC, command injection is actually possible here."
1825396,2019-04-29 15:05:04 UTC,"I've pinged upstream, expecting a release soon which I will try to SRU."
1825396,2019-04-18 20:15:01 UTC,"Iain, could you have a look to this one?"
1825396,2019-04-22 12:29:23 UTC,Upstream bug: https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/111
1825396,2019-05-30 08:18:16 UTC,"The verification of the Stable Release Update for gnome-shell-extension-desktop-icons has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825396,2019-05-21 18:13:19 UTC,"Hello Tom, or anyone else affected,"
1825396,2019-05-21 21:32:09 UTC,"I tested version 19.01.3-1~ubuntu19.04.1 (from -proposed) on a fully updated 19.04, and can no longer reproduce this issue: The terminal window opens - as expected - in directory ~/Desktop/aaa'bbb/. Injecting commands as discussed in comment 2 appears to be no longer possible."
1825396,2019-05-30 08:18:07 UTC,This bug was fixed in the package gnome-shell-extension-desktop-icons - 19.01.3-1~ubuntu19.04.1
1825400,2019-04-23 03:57:57 UTC,"Please uninstall all audio dkms, then reboot:"
1825400,2019-06-22 04:17:43 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825400,2019-04-23 03:00:08 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825400,2019-04-23 02:33:47 UTC,It appears the kernel doesn't support your sound chip :(
1825402,2019-04-19 11:48:00 UTC,Please attack `journalctl -k -b -1` after the issue occurs.
1825402,2019-06-19 04:17:17 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1825402,2019-04-19 00:02:00 UTC,Thank you for taking the time to report this issue and help to improve Ubuntu.
1825402,2019-04-19 11:38:43 UTC,Trying to downgrade systemd seems to be impossible. As soon as I try an apt install --reinstall systemd=<some version> apt tries to remove half of the system...
1825402,2019-04-19 11:48:13 UTC,s/attack/attach
1825403,2019-08-13 14:49:01 UTC,Confirming that this is still impacting PaILS not only in our current 3.1 installation but also in our updated-to-3.3 test server.
1825403,2019-04-18 18:04:34 UTC,Affecting SPARK libraries. One library reported they first noticed it happening after Feb 19 2019.
1825403,2019-05-06 19:45:57 UTC,"Some additional troubleshooting reveals that the Copy Tag management interface doesn't show all  of the tags that you can see in the database.
In my example on a copy of production data, we have a copy tag defined like this:"
1825403,2019-04-29 20:29:19 UTC,"This did not affect our library until April 23, 2019. The process worked fine for me until lunchtime on this date, and was not working at all after that time."
1825403,2019-10-22 13:26:01 UTC,There's a patch at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1825403-copy-tag-owner-display / working//user/jboyer/lp1825403-copy-tag-owner-display that fixes the copy editor and also adds owning location display to the Apply Tags feature of Copy Buckets.
1825403,2019-07-17 17:49:42 UTC,"I tested what happens when 2 libraries create tags with the same name. As long as they are properly ""owned"" then when adding a tag to the item, only the tag belonging to your library is available to select. For example, 2 libraries add a Friends tag, one saying ""Gift of Friends of X Library"" and the other saying ""Donation of the Friends of Z Library."" When adding an item to X library, the tag list will say ""Friends"" and the value displayed in the OPAC will be the note referring to X library."
1825403,2019-10-22 13:38:22 UTC,"Thanks, Jason.  That all works for me, and is pushed to master back through 3.1."
1825403,2019-07-17 17:28:39 UTC,It appears this is due to the change made in LP#1746769
1825403,2019-07-17 13:47:42 UTC,"I can testify that for us, copy tags worked correctly in mid-May when we were on 3.1.8. We upgraded to 3.1.11 around the end of May. I hadn't worked with copy tags after the upgrade until this week, when I found the tags displayed in the OPAC were not the values but the labels with the org unit in parentheses."
1825404,2019-08-29 22:01:32 UTC,"Reviewed:  https://review.opendev.org/653612
Committed: https://git.openstack.org/cgit/x/networking-vpp/commit/?id=e39e121283f5ac45970d4cce7e5ee07aef731764
Submitter: Zuul
Branch:    master"
1825406,2019-04-18 17:52:15 UTC,screenshot of the font-stretching in Libreoffice Calc & Write
1825410,2019-05-27 16:21:13 UTC,Addressed via https://review.opendev.org/#/c/661344/
1825410,2019-09-17 15:02:01 UTC,Changing the order of the duplicates here since I tagged the fix against the other bug.
1825410,2019-04-18 18:34:47 UTC,I noticed this while reviewing this list-table docs change:
1825410,2019-04-18 18:35:34 UTC,Related: https://review.openstack.org/#/c/652171/
1825410,2019-04-18 18:36:13 UTC,compare with https://docs.openstack.org/nova/stein/admin/configuration/schedulers.html#id16
1825410,2019-04-18 18:50:28 UTC,"(1:46:28 PM) efried: interestingly, when I build it locally, the table has a border.
(1:47:44 PM) efried: aha
(1:47:53 PM) efried: sphinx version makes the difference.
(1:48:10 PM) efried: at 1.8.4, borders are there. At 2.0.1, gone."
1825410,2019-04-18 18:54:05 UTC,Maybe some regression with https://github.com/sphinx-doc/sphinx/issues/6113
1825410,2019-04-18 19:30:55 UTC,"It's not 6113, or anywhere in the stylesheets. It's in the actual <table> tag, which used to have border=""1"" (at 1.8.5) and now (at 2.0.0) has no border attribute at all."
1825413,2019-12-17 20:48:45 UTC,"I had this problem occur recently and was able to work with one of my System Administrators to narrow it down.  I saw the floppy text in the output so I asked my Sys Admin to connect the Floppy Drive in VCenter to the VMs that were having this issue (3 new 18.04 installs) and the issue is now resolved on all of them.  blkid, mdadm, nor fdisk hang anymore; they all work as they should.  Not sure where the issue exactly lies, but connecting a floppy helped resolve it for now.  I have a lot of other 16.04 servers that do not have this issue, for what it's worth."
1825413,2019-10-10 15:43:23 UTC,"I see the same thing related to slowness in a old-style parallel port device passed to a VM. Shortly after there's traffic related to the parallel port the task will hang forever, eventually locking up the VM entirely.
This has happened on two SuperMicro servers, the problem did not exist in Xenial and began with the upgrade to bionic and remains in eoan.
Oct  9 03:43:40 noc2 kernel: [48455.643616] INFO: task CPU 0/KVM:18338 blocked for more than 845 seconds.
Oct  9 03:43:40 noc2 kernel: [48455.643624]       Tainted: P           O      5.3.0-13-generic #14-Ubuntu
Oct  9 03:43:40 noc2 kernel: [48455.643625] ""echo 0 > /proc/sys/kernel/hung_task_timeout_secs"" disables this message.
Oct  9 03:43:40 noc2 kernel: [48455.643627] CPU 0/KVM       D    0 18338      1 0x00000100
Oct  9 03:43:40 noc2 kernel: [48455.643630] Call Trace:
Oct  9 03:43:40 noc2 kernel: [48455.643643]  __schedule+0x2b9/0x6c0
Oct  9 03:43:40 noc2 kernel: [48455.643655]  ? handle_io+0x4c/0xc0 [kvm_intel]
Oct  9 03:43:40 noc2 kernel: [48455.643659]  schedule+0x42/0xb0
Oct  9 03:43:40 noc2 kernel: [48455.643661]  schedule_preempt_disabled+0xe/0x10
Oct  9 03:43:40 noc2 kernel: [48455.643663]  __mutex_lock.isra.0+0x182/0x4f0
Oct  9 03:43:40 noc2 kernel: [48455.643712]  ? kvm_arch_vcpu_put+0xe4/0xf0 [kvm]
Oct  9 03:43:40 noc2 kernel: [48455.643731]  ? kvm_arch_vcpu_ioctl_run+0x37a/0x590 [kvm]
Oct  9 03:43:40 noc2 kernel: [48455.643733]  __mutex_lock_slowpath+0x13/0x20
Oct  9 03:43:40 noc2 kernel: [48455.643735]  mutex_lock+0x2e/0x40
Oct  9 03:43:40 noc2 kernel: [48455.643738]  pp_ioctl+0x25/0x50 [ppdev]
Oct  9 03:43:40 noc2 kernel: [48455.643741]  do_vfs_ioctl+0x407/0x670
Oct  9 03:43:40 noc2 kernel: [48455.643745]  ? __secure_computing+0x42/0xe0
Oct  9 03:43:40 noc2 kernel: [48455.643747]  ksys_ioctl+0x67/0x90
Oct  9 03:43:40 noc2 kernel: [48455.643748]  __x64_sys_ioctl+0x1a/0x20
Oct  9 03:43:40 noc2 kernel: [48455.643752]  do_syscall_64+0x5a/0x130
Oct  9 03:43:40 noc2 kernel: [48455.643754]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Oct  9 03:43:40 noc2 kernel: [48455.643756] RIP: 0033:0x7fb9e75b167b
Oct  9 03:43:40 noc2 kernel: [48455.643764] Code: Bad RIP value.
Oct  9 03:43:40 noc2 kernel: [48455.643765] RSP: 002b:00007fb9e4d743a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Oct  9 03:43:40 noc2 kernel: [48455.643767] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fb9e75b167b
Oct  9 03:43:40 noc2 kernel: [48455.643768] RDX: 00007fb9e4d743b7 RSI: 0000000040017086 RDI: 000000000000000a
Oct  9 03:43:40 noc2 kernel: [48455.643769] RBP: 000000000000000a R08: 000055a2756817e8 R09: 000055a275289de0
Oct  9 03:43:40 noc2 kernel: [48455.643770] R10: 0000000000000001 R11: 0000000000000246 R12: 00007fb9e4d743ef
Oct  9 03:43:40 noc2 kernel: [48455.643771] R13: 0000000000000000 R14: 0000000000000001 R15: 000055a276e69010"
1825413,2019-04-18 19:00:07 UTC,This change was made by a bot.
1825413,2019-04-19 16:47:00 UTC,"Looks like something going wrong with the floppy driver. From the description this sounds like a race. I note that a bug with essentially the same stack trace was fixed in 4.20, de7b75d82f70 ""floppy: fix race condition in __floppy_read_block_0()."" We have that fix though, so not sure what is causing it here."
1825413,2019-04-22 20:20:30 UTC,"Hi Seth,"
1825413,2019-04-22 23:49:30 UTC,"On Mon, Apr 22, 2019 at 08:20:30PM -0000, Ryan Harper wrote:

> Hi Seth,
>
> notice only one of the stack tracks have the floppy, the mdadm one does
> not.  I've also recreated this on a qemu q35 machine type which does not
> include the floppy device.
"
1825413,2019-05-06 15:49:20 UTC,"Sorry, I missed responding."
1825413,2019-08-13 08:30:11 UTC,"Same thing happen in HyperV, when run apt-get install -yq linux-azure/disco, it hung in some rate. Like upgrade 3 VMs, 1 VM hung."
1825413,2019-04-18 18:53:07 UTC,"root@ubuntu:~# lspci -v -nn
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)
 Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
 Flags: fast devsel"
1825413,2019-11-05 22:24:33 UTC,Same on physical HW (Medion with QuadCore)
1825414,2019-04-19 08:43:41 UTC,"After deeper research, the repo container did contain the files, however the file rights seems wrong:
root@aio1-repo-container-0ca39ca3:/var/www/repo/os-releases/19.0.0.0rc2.dev16# ls -alh
total 60K
drwxr-sr-x 3 nginx www-data 4.0K Apr 18 21:05 .
drwxr-sr-x 3 nginx www-data 4.0K Apr 18 20:30 ..
drwxr-sr-x 2 root  www-data  20K Apr 18 21:05 debian-9.8-x86_64
-rw-r--r-- 1 root  root     2.5K Apr 18 21:05 keystone-19.0.0.0rc2.dev16-constraints.txt
-rw-r--r-- 1 root  root        1 Apr 18 21:04 keystone-19.0.0.0rc2.dev16-global-constraints.txt
-rw-r--r-- 1 root  root      105 Apr 18 21:04 keystone-19.0.0.0rc2.dev16-requirements.txt
-rw-r--r-- 1 root  root      241 Apr 18 21:04 keystone-19.0.0.0rc2.dev16-source-constraints.txt
-rw-r--r-- 1 root  root     2.7K Apr 18 20:33 utility-19.0.0.0rc2.dev16-constraints.txt
-rw-r--r-- 1 root  root        1 Apr 18 20:32 utility-19.0.0.0rc2.dev16-global-constraints.txt
-rw-r--r-- 1 root  root      880 Apr 18 20:32 utility-19.0.0.0rc2.dev16-requirements.txt
-rw-r--r-- 1 root  root      138 Apr 18 20:32 utility-19.0.0.0rc2.dev16-source-constraints.txt"
1825414,2019-04-21 10:47:46 UTC,Mmmm NGINX doesn't seem to be indexing the pages
1825415,2019-04-18 20:19:57 UTC,"Thank you for your bug report, could you provide details though?"
1825415,2019-04-18 20:38:47 UTC,"shift + delete on a desktop text file
text file moves to trash
this is reproducible"
1825415,2019-04-18 20:45:44 UTC,"If you do this from a nautilus window, you get the expected permanent delete."
1825415,2019-04-18 21:18:00 UTC,"The desktop is not handled by nautilus anymore, that's a bug in the new gnome-shell-extension-desktop-icons component.
Also next time please give some details in the description directly, it would avoid comment roundtrips to understand what's going on."
1825415,2019-04-18 21:18:49 UTC,"It's also known upstream, https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/30"
1825418,2019-04-27 01:52:45 UTC,"It was never intended to support anchors and the current implementation
won't support that. It is not too say it is entirely a bad idea, but not
currently supported."
1825418,2019-05-13 23:14:25 UTC,"Ah, Ok, thanks. Still would be nice to see this feature in the future."
1825419,2019-04-25 19:03:12 UTC,"Ok, thanks.  I missed that when perusing the changelogs.  My mistake, sorry."
1825419,2019-04-20 10:21:36 UTC,"With the upgrade from rancid 3.4 to 3.5 the Arista support changed from a stand alone arrancid to the module, which should be used by ""rancid -t arista""."
1825420,2019-04-18 20:30:05 UTC,This change was made by a bot.
1825420,2019-04-19 10:18:41 UTC,"Also affected:  Ubuntu MATE 18.10 -> 19.04 Upgrade.  Normal system (not VM).  18.10 was a hardly used clean install of Ubuntu MATE, up-to-date patch status before update.  Install appears complete and OK ..."
1825420,2019-04-20 04:53:21 UTC,"Same error message for me. Unable to boot into the 4 kernel backup as well. Repeatedly boots to the login screen, which shows my name but refuses to accept my password."
1825420,2019-04-20 04:53:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825420,2019-04-20 21:27:45 UTC,"Confirmed during upgrade of clean fully-updated Ubuntu MATE 18.10 to Ubuntu MATE 19.04, so I have marked Ubuntu MATE as affected by this bug."
1825420,2019-04-21 06:46:32 UTC,"Faced same problem while upgrading from 18.10 to 19.04
Upgrade completed but showed
"" Could not install 'linux-image-5.0.0-13-generic'
    The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it."
1825420,2019-04-22 17:07:14 UTC,"Upgrading a cloud image, I couldn't reproduce it. I also tried installing mate-desktop-environment-core + mate-dock-applet (because it depends on bamfdaemon) before upgrading, and still couldn't reproduce. I will install a cosmic mate desktop and see if I can reproduce this problem when upgrading."
1825420,2019-04-24 04:07:52 UTC,More info from post #4
1825420,2019-04-24 05:50:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825420,2019-04-24 06:28:17 UTC,"System: Dell Studio XPS 8300 64bit. memory: 7.8 GiB. CPU: Intel® Core™ i7-2600 CPU @ 3.40GHz × 8.
Graphics AMD® Juniper."
1825420,2019-04-24 22:31:44 UTC,I also reverted to Linux kernel 4.18.0-13-generic (The one that ships with Ubuntu 18.10) after upgrading to 19.04.
1825420,2019-04-25 00:35:31 UTC,"On 25/4/19 8:31 am, Troels Petersen wrote:

> I also reverted to Linux kernel 4.18.0-13-generic (The one that ships
> with Ubuntu 18.10) after upgrading to 19.04.
>
> System: HP Spectre 13 v000nf, 8 GB Memory, Dual core Intel i5-6200U CPU
> @ 2.30 GHz, Intel HD Graphics 520 (Skylake GT2)
>
> When running 'sudo apt upgrade' it complains about a missing dkms.conf
> file:
>
> Setting up linux-headers-5.0.0-13-generic (5.0.0-13.14) ...
> /etc/kernel/header_postinst.d/dkms:
> Error! Could not locate dkms.conf file.
> File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist.
> run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
> dpkg: error processing package linux-headers-5.0.0-13-generic (--configure):
>   installed linux-headers-5.0.0-13-generic package post-installation script subprocess returned error exit status 1
> dpkg: dependency problems prevent configuration of linux-headers-generic:
>   linux-headers-generic depends on linux-headers-5.0.0-13-generic; however:
>    Package linux-headers-5.0.0-13-generic is not configured yet.
>
> dpkg: error processing package linux-headers-generic (--configure):
>   dependency problems - leaving unconfigured
> Setting up linux-image-5.0.0-13-generic (5.0.0-13.14) ...
> No apport report written because the error message indicates its a followup error from a previous failure.
>       dpkg: dependency problems prevent configuration of linux-generic:
>   linux-generic depends on linux-headers-generic (= 5.0.0.13.14); however:
>    Package linux-headers-generic is not configured yet.
>
> dpkg: error processing package linux-generic (--configure):
>   dependency problems - leaving unconfigured
> No apport report written because the error message indicates its a followup error from a previous failure.
>       Processing triggers for linux-image-5.0.0-13-generic (5.0.0-13.14) ...
> /etc/kernel/postinst.d/dkms:
> Error! Could not locate dkms.conf file.
> File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist.
> run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
> dpkg: error processing package linux-image-5.0.0-13-generic (--configure):
>   installed linux-image-5.0.0-13-generic package post-installation script subprocess returned error exit status 1
> No apport report written because MaxReports is reached already
>                                                                Errors were encountered while processing:
>   linux-headers-5.0.0-13-generic
>   linux-headers-generic
>   linux-generic
>   linux-image-5.0.0-13-generic
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
"
1825420,2019-04-25 12:16:30 UTC,"I noticed that the OP had VirtualBox installed, same for me. This taints the kernel ..."
1825420,2019-04-25 15:04:33 UTC,Update to 2 hours ago:
1825420,2019-04-25 15:10:32 UTC,I went back to the 4.18 kernel but am not running VirtualBox (running bare metal).
1825420,2019-10-15 16:55:00 UTC,This is likely a duplicate of https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1828639.
1825420,2019-09-26 12:09:02 UTC,I tested an upgrade from Ubuntu 18.10 to Ubuntu 19.04 today with some of the packages from the DuplicateSignature.txt installed e.g.:
1825420,2019-05-18 15:25:04 UTC,"So, 4 weeks later, after my previous comments, and now running stably:"
1825420,2019-05-04 15:11:50 UTC,"Upgraded today from 18.10 and encountered same issue:
Could not install 'linux-image-5.0.0-13-generic'"
1825422,2019-04-23 14:39:57 UTC,"Change abandoned by Naveen Joy (<email address hidden>) on branch: master
Review: https://review.opendev.org/653851
Reason: Already addressed by a different patch.
https://review.opendev.org/#/c/652172/1"
1825426,2019-05-04 22:51:05 UTC,"In current master and in 3.2.5, I was able to remove both the phone number and SMS notification number from an existing hold by opening the notification settings for the hold, clicking the checkbox to the left of the Phone # and Text/SMS # labels, and leaving the input box blank.  I was not able to remove an existing SMS Carrier from a request, but this probably doesn't matter if you can remove the SMS number."
1825427,2019-04-20 06:56:07 UTC,"I'd say the Esc issue is fixed, but it's only working in the sense that the tool is no longer reactivated. The select tool is now broken: https://bugs.launchpad.net/kicad/+bug/1825613"
1825427,2019-04-19 16:27:47 UTC,<esc> issue should be fixed now too.
1825427,2019-04-19 13:18:55 UTC,"Indeed, the <esc> key is still broken (although the context menu ""End Tool"" item works).  I'll dig into it...."
1825427,2019-04-19 01:56:35 UTC,"If you click on the cursor tool, it does behave correctly, but the ""escape to exit tool"" functionality does not work before you do that. The cursor tool is misleadingly highlighted even though the previous tool is still active."
1825427,2019-04-19 01:09:54 UTC,"Hi Jeff, the sticky tool issue is still a problem as of 5.1.0-rc1-504-ge9c1cd2. Thanks for the fix!"
1825427,2019-04-18 21:24:26 UTC,Looks like the second part of this bug is the same as https://bugs.launchpad.net/kicad/+bug/1825192
1825436,2019-04-29 16:05:07 UTC,"Will be available in kubernetes-worker-523 and later, and kubernetes-master-661 and later."
1825436,2019-04-22 12:55:57 UTC,Implementation in nova-compute: https://github.com/openstack/charm-nova-compute/blob/master/hooks/nova_compute_hooks.py#L184-L195
1825436,2019-04-25 19:34:40 UTC,"https://github.com/charmed-kubernetes/layer-kubernetes-master-worker-base/pull/3
https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/4"
1825436,2019-06-06 17:09:12 UTC,"Fix released to stable with these charm revisions:
cs:~containers/kubernetes-master-684
cs:~containers/kubernetes-worker-541"
1825436,2019-06-04 14:26:33 UTC,"PRs to stable:
https://github.com/charmed-kubernetes/layer-kubernetes-master-worker-base/pull/4
https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/19"
1825436,2019-06-04 18:22:01 UTC,"Fix is available in candidate channels:
cs:~containers/kubernetes-master-684
cs:~containers/kubernetes-worker-541"
1825437,2019-04-25 13:41:44 UTC,The snapd part of this has landed in https://github.com/snapcore/snapd/pull/6771 and will be part of the 2.39 upload.
1825437,2019-04-24 22:56:44 UTC,just don't read the commit messages and you'll be fine
1825437,2019-04-24 21:41:32 UTC,"Yes, mvo lives in a future in which he's already implemented that feature, whereas us mere mortals are stuck waiting for it to arrive."
1825437,2019-04-24 14:48:57 UTC,"I am adding a livecd-rootfs task - it would be nice if seed.yaml manipulation would add an extra check at the end. Ideally we should call a new ""snap debug validate-seed <path>"" during the build process. livecd-rootfs already build-depends on snapd so that should be ok, yes? The PR for this is https://github.com/snapcore/snapd/pull/6771"
1825437,2019-04-24 10:59:31 UTC,I looked at this a bit more and the following change broke the installer:
1825437,2019-04-24 10:17:02 UTC,"From what I understand the immediate crisis is over, correct? We had an incorrect image right before the release but for the final release things got fixed. I would love to know what exactly happend with the image and if that was an installer or an image builder issues. I think we need to improve the tooling there to ensure we don't write incorrect seed.yaml. I also thing snapd should error and not ignore this issue."
1825437,2019-04-23 22:59:40 UTC,"Tried once with current release mage, works ok.
So maybe it was just the image 2 day prior to release though that seems curious.."
1825437,2019-04-23 07:16:25 UTC,"I did a clean install with the Alpha image and did not notice any issues, snapd did not panic, seed yaml looked correct."
1825437,2019-04-22 18:25:09 UTC,I hope it is this image only:
1825437,2019-04-20 12:02:52 UTC,Do you perhaps have logs from the system installer?
1825437,2019-04-20 11:42:23 UTC,HA
1825437,2019-04-20 10:45:57 UTC,"Hmm, I thought this was the final, maybe should try again the install.
Anyway this is the requested file.."
1825437,2019-04-20 07:28:38 UTC,"fwiw, at least the base seed in ubuntu-19.04-desktop-amd64.iso  Ubuntu 19.04 ""Disco Dingo"" - Release amd64 (20190416) looks correct"
1825437,2019-04-20 07:15:09 UTC,"snapd should error on this, not panic, but seed.yaml is intended to be strict a format,  nulls shouldn't be there"
1825437,2019-04-19 11:18:01 UTC,Keep in mind that apparently the ISO image is not the final relase one. The attached bug data has:
1825437,2019-04-19 10:51:55 UTC,I've started a tentative workaround for this issue under: https://github.com/snapcore/snapd/pull/6756
1825437,2019-04-19 10:48:12 UTC,Can you please provide the contents of /var/lib/snapd/seed/seed.yaml as an attachment?
1825437,2019-04-19 10:42:52 UTC,Thank you for providing the service logs. It seems snapd is crashing on a NULL pointer. I'm marking the bug as confirmed and bumping priority to critical.
1825437,2019-04-19 10:32:51 UTC,"Attaching output
(edited to just oe ""reboot""  as it's the exact same per each reboot"
1825437,2019-04-19 00:19:45 UTC,"What's the output of ""journalctl --system -u snapd""?"
1825437,2019-04-24 20:31:29 UTC,"On Wed, 24 Apr 2019 at 16:00, Michael Vogt <email address hidden> wrote:

>
> I am adding a livecd-rootfs task - it would be nice if seed.yaml
> manipulation would add an extra check at the end. Ideally we should call
> a new ""snap debug validate-seed <path>"" during the build process.
> livecd-rootfs already build-depends on snapd so that should be ok, yes?
> The PR for this is https://github.com/snapcore/snapd/pull/6771
>
"
1825437,2019-04-24 22:47:48 UTC,"Oh come on! Avengers Endgame comes out in 15 minutes in the UK, don't spoil it for me mvo!"
1825437,2019-04-22 14:40:58 UTC,I can't reproduce this with the released image.  Any idea what scenario it creates the broken seed?
1825439,2019-04-29 03:58:47 UTC,a PR https://github.com/juju/juju/pull/10088 merges into 2.6
1825439,2019-04-19 08:16:24 UTC,Let me know if you need any more information.
1825440,2019-04-29 03:57:31 UTC,a PR https://github.com/juju/juju/pull/10087 merges into 2.6
1825441,2019-06-22 04:17:29 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825441,2019-04-22 21:20:38 UTC,"@Malcolm Smith - and does your /etc/modprobe.d/iwlwifi.conf file contain the word ""options"" in line 8? If not please open a new bug report regarding your issue."
1825441,2019-04-20 04:55:25 UTC,I am getting the same error upgrading from Ubuntu 18.10 to 19.04.  The upgrade then aborted and ran the recovery 'dpkg-configure-a'.
1825441,2019-04-19 15:58:13 UTC,This line from VarLogDistupgradeAptlog.txt leads me to believe that you have modified that file:
1825445,2019-04-19 11:15:09 UTC,"Currently we have already two possible solutions we may improve:
* The AutoDJ playlist, which is able to auto load a parked track.
* Samplers"
1825445,2020-05-24 16:29:15 UTC,"related: lp:730572 ""Sidelist songs"""
1825445,2019-04-19 18:28:00 UTC,"I agree, if samplers can serve this function for you I think that's good enough and there's no need to create a new, special deck type just for this.  Samplers should be showing the information you describe -- even ""cover art"" could be an icon that makes it easy to remember what the sample is."
1825445,2019-04-19 12:15:30 UTC,"Basically tis boils down to lp:1743109 ""unify Sampler interface in all skins"""
1825445,2019-04-19 12:14:33 UTC,"A Preview deck history is a nice idea, but not suitable for quick access. Like using the AutoDJ playlist this would require to switch library features which is slow/complicated."
1825445,2019-04-19 00:39:32 UTC,"unplayable tracks should be refused, tough. But the check requires them to be loaded like in a regular deck, right? what's the peformance impact?"
1825446,2020-05-05 21:53:06 UTC,This was finally fixed with gedit 3.36.2 in Focal.
1825447,2019-05-10 04:32:51 UTC,"The extension is working fine with scroll events being delivered.
Thanks for the quick turnaround."
1825447,2019-05-14 16:39:17 UTC,That is the version I installed.
1825447,2019-04-24 23:41:38 UTC,"Upstream ubuntu branch wasn't updated since we synced from debian, so the branch isn't wrong."
1825447,2019-04-30 10:12:55 UTC,"synced, SRU uploaded as a backport of the eoan version"
1825447,2019-05-10 04:41:50 UTC,"Ed, just to confirm."
1825447,2019-05-07 15:42:24 UTC,https://bugs.launchpad.net/radiotray/+bug/1828069
1825447,2019-05-08 20:16:06 UTC,"Hello Ed, or anyone else affected,"
1825447,2019-05-15 23:27:03 UTC,This bug was fixed in the package gnome-shell-extension-appindicator - 29-1~ubuntu19.04.1
1825447,2019-05-15 23:27:09 UTC,"The verification of the Stable Release Update for gnome-shell-extension-appindicator has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825447,2019-06-26 16:02:21 UTC,Thank you for fixing this. The app-level volume control is working great now by scrolling on top of the RadioTray icon.
1825448,2019-05-01 14:42:56 UTC,"On Wed, May 01, 2019 at 02:10:52PM -0000, Dan Streetman wrote:

> Can you explain in more detail why you believe it's better to leave
> broken autopkgtests broken?
"
1825448,2019-05-25 03:58:02 UTC,"An upload of gnupg2 to cosmic-proposed has been rejected from the upload queue for the following reason: ""fixing tests only does not fit the SRU policy""."
1825448,2019-05-25 03:57:08 UTC,"An upload of gnupg2 to bionic-proposed has been rejected from the upload queue for the following reason: ""fixing tests only does not fit the SRU policy""."
1825448,2019-05-25 03:56:16 UTC,"""Other safe cases"" mentions:"
1825448,2019-05-02 07:37:19 UTC,"SRU policy, Section 2 ""When"", has three major categories listing in bullet points cases that are eligible for SRU."
1825448,2019-05-02 06:30:03 UTC,"> Adding new autopkgtests in stable series - not good.
"
1825448,2019-05-01 21:51:40 UTC,Adding new autopkgtests in devel series - good.
1825448,2019-05-01 15:37:33 UTC,"> Please don't mischaracterise my position like this
"
1825448,2019-06-14 21:59:31 UTC,"An upload of gnupg to xenial-proposed has been rejected from the upload queue for the following reason: ""fixing tests only does not fit the SRU policy""."
1825448,2019-05-25 03:59:28 UTC,"An upload of gnupg2 to xenial-proposed has been rejected from the upload queue for the following reason: ""fixing tests only does not fit the SRU policy""."
1825448,2019-05-01 14:10:52 UTC,"> please could you assess this against the concerns raised in the thread here
"
1825448,2019-05-01 13:50:18 UTC,Thank you for working on improving our test suites.
1825448,2019-05-01 14:31:39 UTC,"I was asking about how the points raised in the mailing list thread
specifically apply to this particular case."
1825449,2019-06-22 04:17:34 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1825449,2019-04-23 02:37:18 UTC,Please try uninstalling all these extensions:
1825452,2019-04-19 08:41:57 UTC,Removing this lines makes pa backend work fine again. Much better than 3.x versions due to buffer fixes.
1825452,2019-04-25 13:19:45 UTC,It looks like this code relies on the systemd specifics and doesn't work with OpenRC used in Gentoo by default. Still not fixed in 4.0.0 release.
1825452,2019-05-02 07:30:22 UTC,"You can use -audiodev pa,id=whatever,server=unix:/home/ivan/.pulse_server to get things going with your configuration."
1825454,2019-04-19 02:20:50 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653897"
1825455,2019-04-21 11:46:45 UTC,"Dear Olivier,"
1825455,2019-04-21 11:45:42 UTC,"Dear Olivier,"
1825455,2019-04-19 07:13:25 UTC,"Hi,"
1825461,2019-04-28 02:28:02 UTC,"Yes, that works. No crashes.
That explains why it works on some machines and not on others.
Thanks for your help."
1825461,2019-04-27 05:22:38 UTC,Is it simply a matter of upgrading my driver to fix the problem.
1825461,2019-04-27 05:21:39 UTC,Yes that made the waveforms work correctly in 2.2.1. Only until I rebooted of course.
1825461,2019-04-26 22:36:02 UTC,"@rockinrod: Your driver is blacklisted here because of a possible crash:
https://github.com/qt/qtbase/blob/dev/src/plugins/platforms/windows/openglblacklists/default.json"
1825461,2019-04-26 22:08:22 UTC,"For some reasons QT decides in Qt5 to use the GL ES render instead of pain GL.
It uses a translator to convert GL ES into direct 3 d.
Only the QT Waveforms are Hardware accelerated in this state."
1825461,2019-04-23 09:16:38 UTC,"On board graphics also. ""Intel HD Graphics 3000"". Driver version 9.17.10.4229.
I have the same issue with Mixxx 2.2.1.
I cannot find GL version in my waveform preferences. I can see ""Open GL Status"" which is blank in 2.2.0 and 2.2.1.
Loaded 2.1.8, no problem with waveforms. ""Open GL Status"" 3.1.
I am glad you can reproduce the error."
1825461,2019-04-23 06:23:01 UTC,"And which graphic card and driver do you use?
Which GL version is reported in the waveforms preferences? With Mixxx 2.2.x and Mixxx 2.1.8"
1825461,2019-04-23 01:15:33 UTC,"I don’t have stand alone soundcard. The soundcard is “Realtek high definition” on board an Asus high performance MB. The  Realtek driver is version 6.0.1.6251.
I will test v2.2.1 later on today."
1825461,2019-04-22 16:05:03 UTC,"Is the 2.2.1 release candidate effected?
http://downloads.mixxx.org/builds/2.2/release/mixxx-2.2.1-2.2-git6690-release-x64.exe"
1825461,2019-04-22 08:12:23 UTC,"Which graphic card and driver do you use?
Is Mixxx 2.1.8 also effected?"
1825461,2019-04-21 00:03:53 UTC,"Selecting different waveforms gave the following results.
Empty: Nothing Displayed
Filtered (GLSL): Nothing Displayed
RGB(GLSL): Nothing Displayed"
1825461,2019-04-20 11:50:05 UTC,"Please try to alter the waveform types in preferences.
Are all types effected? Are all skins effected?"
1825461,2019-04-20 11:37:24 UTC,"> dupe of https://bugs.launchpad.net/mixxx/+bug/1824620 ?
"
1825461,2019-04-19 09:41:59 UTC,dupe of https://bugs.launchpad.net/mixxx/+bug/1824620 ?
1825461,2019-04-27 15:47:21 UTC,"I am afraid any version of your driver is blacklisted.
If you not suffering the crash, you can set QT_OPENGL=desktop system wide.
https://superuser.com/questions/949560/how-do-i-set-system-environment-variables-in-windows-10"
1825461,2019-04-22 08:07:47 UTC,"Debug [Main]: Created QGLWidget. Context Valid: true Sharing: true
Debug [Main]: GLWaveformRendererSignalShader::loadShaders
Warning [Main]: QGLShader::compile(Vertex): ERROR: 0:5: 'gl_TexCoord' : undeclared identifier
ERROR: 0:5: 'gl_TexCoord' :  left of '[' is not of type array, matrix, or vector
ERROR: 0:5: 'gl_MultiTexCoord0' : undeclared identifier
ERROR: 0:6: 'gl_ModelViewProjectionMatrix' : undeclared identifier
ERROR: 0:6: 'gl_Vertex' : undeclared identifier
ERROR: 0:6: 'assign' :  cannot convert from 'float' to 'Position highp 4-component vector of float'"
1825464,2019-05-14 16:47:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825464,2019-04-19 17:19:06 UTC,"Hi,"
1825465,2019-04-19 05:18:48 UTC,I dumped a sample pnm file to hex:
1825465,2019-04-19 05:20:55 UTC,"For my own use, I wrote a quick and dirty PNM file fixer. Seems to work with everything I've run through my scanner."
1825466,2019-04-19 07:27:18 UTC,"Just a small comment for this, Swift3 was merged to OpenStack Swift code base at [1] so that currently no one actively maintains *Swift3* itself so that please try the newer Swift and s3api middleware instead of Swift3."
1825466,2019-04-19 09:52:28 UTC,"Thank you for your promt comment.
As you mentioned, Swift3 has been no longer available and it was merged to Swift. I just forgot it and left this report here. It was not appropreate place to report."
1825466,2019-04-21 11:08:42 UTC,I have also encountered the same error when I was trying to put a large object with a Chinese object name using S3 Multipart Upload.
1825468,2019-04-19 14:55:06 UTC,While you have deactivated the PPAs that actually isn't enough because you still have software installed from those PPAs.  You'll need to reenable them and then use the tool 'ppa-purge' to remove the PPA and uninstall the software from it.  The release upgrader should have instructed you to use ppa-purge.
1825468,2019-06-19 04:17:21 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825469,2019-06-14 03:10:06 UTC,"Change abandoned by Ryan Liang (<email address hidden>) on branch: master
Review: https://review.opendev.org/653912
Reason: New review is: https://review.opendev.org/#/c/665281/"
1825469,2019-09-27 09:04:03 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1825469,2019-09-03 16:02:49 UTC,"Reviewed:  https://review.opendev.org/665281
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=850013325b50e890ad240c360c782731e6b98a56
Submitter: Zuul
Branch:    master"
1825469,2019-04-19 06:23:44 UTC,The fix needs to modify the Cinder framework and VNX driver codes.
1825469,2019-04-19 06:59:14 UTC,"Fix proposed to branch: master
Review: https://review.openstack.org/653912"
1825469,2019-06-14 03:06:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665281"
1825474,2019-04-19 23:45:51 UTC,"That's just the nature of storing secrets for later use. The only way to store a key in an encrypted form would require the user to then supply a decryption key, probably in the form of a password that would then be handed to a key derivation function. That only slightly moves the goalposts."
1825474,2019-04-23 12:21:57 UTC,the issue should also probably be discussed upstream if you believe the software should handle keys in a different way
1825475,2020-05-21 10:28:50 UTC,"Migrated to new issue tracker, please follow the issue there for updates:
https://github.com/Xubuntu/xubuntu-website/issues/1"
1825477,2019-05-14 14:22:21 UTC,Hi there -
1825478,2020-05-21 10:28:16 UTC,"Migrated to new issue tracker, please follow the issue there for updates:
https://github.com/Xubuntu/xubuntu-website/issues/2"
1825479,2019-04-22 15:45:49 UTC,This looks like a probert issue with multipath discovery.
1825479,2019-04-22 17:59:13 UTC,I think this was was resolved in probert here:
1825479,2019-04-26 02:14:19 UTC,"The snap includes 31e973d130a137ef1713ac23a422af0e32108c01 which is indeed
a bit older than we should have used :( And of course because this crash is
at startup it happens before we get to offering a snap update."
1825479,2019-11-13 21:09:49 UTC,"We fixed this a while ago now, and all current media includes the fix."
1825484,2019-04-19 10:55:21 UTC,This bug seems related to https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1752526
1825486,2019-05-03 14:17:42 UTC,"Okay, now I could obtain some output from the first half of the test:
…
Script requests save to: inputqueues
# All Tests passed.
Gamesave: save requested: inputqueues
…"
1825486,2019-09-15 16:05:18 UTC,Migrated to https://github.com/widelands/widelands/issues/586
1825486,2019-06-06 18:29:31 UTC,"Well, that got me ""PANIC: unprotected error in call to Lua API"". Back to the drawing board..."
1825486,2019-06-06 18:24:38 UTC,"I have had a look at the save_handler. t saves the game at next tick. If we save immediately, the Lua script should theoretically wait for it. I'll do the coding to see if that fixes it."
1825486,2019-04-24 18:38:27 UTC,This seems to be happening mostly on GCC7 debug builds.
1825486,2019-05-03 14:02:49 UTC,"I could now reproduce it once locally: The script worked fine until it was reloaded from the save, then nothing happened. The stopped barracks just stood idling around. I repeated the test to get more output but was unable to reproduce again."
1825487,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1825487,2019-04-19 09:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825487,2019-04-25 22:32:20 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1825487,2019-04-26 15:36:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1825487,2019-04-29 16:04:08 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825487,2019-05-21 13:04:12 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1825487,2019-05-17 05:35:57 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1825487,2019-05-14 22:54:53 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825487,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1825487,2019-05-14 19:03:14 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1825487,2019-05-14 19:06:48 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1825491,2019-06-03 16:27:22 UTC,affects 4.15.0-1033.35 linux-gke
1825491,2019-04-19 10:03:48 UTC,"Yes,
the change from this patch: https://lists.ubuntu.com/archives/kernel-team/2019-February/098259.html
could be found in the code we use for testing this on GKE."
1825491,2020-01-17 11:06:01 UTC,"This issue can be found on 5.0.0-1029-gcp, but not on every instances, just on these:
* n1-highcpu-16
* n1-highmem-16
* n1-highmem-8
* n1-standard-64
* n1-standard-8"
1825491,2020-05-29 09:49:27 UTC,Spotted on Bionic 5.0.0-49.53~18.04.1 this cycle.
1825493,2019-11-13 19:50:05 UTC,"This is still an issue as looking through some of the logs there are failures.  It appears that this is the only cloud exhibiting this at this time.  I believe Azure did have this problem, will investigate further"
1825493,2019-04-19 14:15:53 UTC,"Yea, i'm seeing this carry over into azure, Since we dropped many non-critical elements of the job name, I see this much less of a problem. Only in particular cases."
1825493,2020-02-20 15:18:49 UTC,updates were made to adjust for this last year. ok to close.
1825495,2019-04-20 08:34:39 UTC,The current shortcuts are E and O as in vErtical and hOrizontal. You can't really have V and H instead because V is the standard for pasting.
1825495,2019-04-20 09:10:08 UTC,"Tilix shortcut for vertical splitting is Ctrl+Alt+R, which stands for ""Add terminal right"". I don't like Ctrl+Alt combination as it is hard to type with my only left hand on a notebook. Ctrl+Shift is much easier. Ctrl+Shift+R in Terminator is for ""Reset the terminal"". I have no idea what is it for - it does nothing when pressed."
1825495,2019-04-20 08:57:47 UTC,"It doesn't matter which scheme is used for shortcut as long as it is available from shortcuts help, and then it gets remembered the `vim` way - by practice."
1825495,2019-08-24 22:52:31 UTC,"Hello, Anatoli."
1825495,2019-08-26 18:27:51 UTC,"Hello, Grandma."
1825495,2019-04-20 09:10:34 UTC,I have no idea how often it is used. Are there any stats about Terminator shortcuts usage?
1825496,2019-04-19 09:54:33 UTC,"I tried to change ""flavour"": ""gke-4.15"", to ""gke"", but it's still not working."
1825496,2019-04-19 10:05:30 UTC,"OK the key is:
    ""package"": ""linux-gke-4.15"","
1825496,2019-04-19 10:24:15 UTC,"There are two meta packages for the GKE kernel:
ii  linux-gke                          4.15.0.1030.33                              amd64        Complete Google Container Engine (GKE) Linux kernel and headers
ii  linux-gke-4.15                     4.15.0.1030.33                              amd64        Complete Google Container Engine (GKE) Linux kernel and headers"
1825496,2019-04-19 13:53:12 UTC,I just started looking at this yesterday as I found the issue early in the morning. I'll own this and get it resolved
1825496,2019-11-13 19:47:24 UTC,We have transitioned to incorporating the major version into the kernel names. This has been resolved and fixed for a while now
1825498,2019-08-03 18:15:35 UTC,"Fixed in version 1.0.2, released yesterday."
1825498,2019-04-19 19:48:22 UTC,"Applied, thanks!"
1825499,2020-04-30 01:31:41 UTC,"Thanks #29!
Your fix worked for me as well."
1825499,2020-02-07 23:34:33 UTC,"Thanks #29!
Works like a charm on my HP Pavilion g6 2394sr"
1825499,2020-04-30 20:34:19 UTC,"This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'."
1825499,2019-04-21 04:56:02 UTC,"I tried using the command `xinput`, so libinput might be related?
I couldn't add systemsettings5 for KDE, but added systemsettings, because it should include GUI for this."
1825499,2020-05-26 18:07:49 UTC,"Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug."
1825499,2020-01-08 22:52:36 UTC,"There is a hwdb entry in systemd for the Paviliong6, but that seems to be a different device than what you have. To fix this, find the 60-evdev.hwdb file on your system, it has the instructions on what to do with this snippet. You can shorten the lookup rule a bit so you end up with this:"
1825499,2020-05-21 10:56:42 UTC,"My partners ""HP Pavillon g6"" started showing this issue upgrading from 19.04 -> 19.10."
1825499,2020-01-08 12:39:12 UTC,"Recently, touchpad movement is slow, before login to account only."
1825499,2019-04-21 04:50:49 UTC,This is the first time this bug happen to me with any distribution.
1825499,2019-12-13 19:20:48 UTC,"I solved this issue by the next actions:
- run the touchpad-edge-detector tool from the libevdev-utils package
in my case command is sudo touchpad-edge-detector 96x46 /dev/input/event6
- then I pasted output of previous command to file /lib/udev/hwdb.d/60-evdev.hwdb
- and apply this changes by commands
sudo systemd-hwdb update
sudo udevadm trigger /dev/input/event*
like commented in head of redacted file"
1825499,2019-04-23 05:14:52 UTC,"In Ubuntu 18.10, no, it doesn't happen.
I didn't try Ubuntu 19.10."
1825499,2019-04-23 05:15:45 UTC,Maybe Synaptic driver needs to be installed for laptops that need it.
1825499,2019-09-09 18:39:03 UTC,I installed Fedora 30 (64-bit) and I've the same issue.
1825499,2019-04-23 05:31:19 UTC,"I mean, does the problem happen in Gnome Shell in Ubuntu 19.04? To test that please try just booting it from USB:"
1825499,2019-04-23 05:33:30 UTC,Please also try installing some older kernel versions from here:
1825499,2019-04-23 05:34:49 UTC,Actually if the problem existed before you installed xserver-xorg-input-synaptics then we can exclude that as a cause.
1825499,2019-05-20 14:25:07 UTC,Also have same symptoms following 19.04 upgrade.
1825499,2019-05-21 17:33:17 UTC,HP Pavilion model G6-2264sa
1825499,2019-05-22 01:41:19 UTC,Someone please answer comments #7 and #8.
1825499,2019-05-22 09:45:52 UTC,Re: #7 - I'm running vanilla Ubuntu on Xorg / Gnome shell.
1825499,2019-05-22 10:03:18 UTC,OK then. This sounds like a regression in vanilla Ubuntu between versions 18.10 and 19.04. Next please try installing some older kernel versions from here:
1825499,2019-05-22 10:15:47 UTC,"Using Gnome 3.32.1 on Xorg, (vanilla Ubuntu).
Current kernel 5.0.0-15-generic, same behaviour in 5.0.0-13-generic"
1825499,2019-05-23 01:44:40 UTC,Ubuntu 18.10 (which does not have the bug) uses kernel version 4.18 so please start testing versions around there. If you find 4.18 fixes the bug then next please find a version roughly halfway between 4.18 and 5.0.0 ...
1825499,2019-05-23 10:13:31 UTC,"OK, installing old kernels seems to be beyond me at the moment, trying to install 4.20 & 4.19 following https://seagullbird.xyz/posts/how-to-install-an-older-kernel/ or some askubuntu results so far leaves me with non-booting kernels.  Is there a reliable beginners guide somewhere I can follow?"
1825499,2019-05-24 01:51:05 UTC,I don't know of a reliable beginners guide. The above link looks good and is what I would do.
1825499,2019-07-11 19:50:57 UTC,Hi.
1825499,2020-01-08 12:38:24 UTC,"I apologize for the late reply.
After either installing Fedora 31 or installing it followed by some updates, the problem seems to be fixed."
1825499,2019-04-23 02:39:27 UTC,Does the problem happen in Gnome Shell too?
1825499,2019-07-18 15:53:08 UTC,Maybe this? https://github.com/systemd/systemd/pull/10008
1825499,2019-07-18 20:00:59 UTC,"# 20: Yes, that's it. Thank you!"
1825499,2019-10-17 21:07:50 UTC,"you'll need to run it against the correct event node, run libinput record (libinput-utils.rpm) without arguments, it'll give you a list of devices. Pick your touchpad from that list. Note that you may have 2 touchpad kernel devices, only one of which will send events. So while libinput record is running, touch the device - if you see events scroll past that's the right event node."
1825499,2019-10-17 18:32:42 UTC,"How to use it? Sorry.
I tried:
$ sudo touchpad-edge-detector 40x60 /dev/input/event0
$ sudo touchpad-edge-detector 40x60 /dev/input/event1
The output was:
Error: this device does not have abs axes"
1825499,2019-10-13 22:54:32 UTC,"please run the touchpad-edge-detector tool from the libevdev-utils package and post the output here, thanks."
1825499,2019-09-10 04:34:23 UTC,Upstream bug with fix: https://github.com/systemd/systemd/issues/13116
1825499,2019-09-19 07:54:08 UTC,"This bug affects me linux wide.
Laptop: HP Pavilion G6 2209se
tried touchpad-edge-detector and it detects resolution correctly.
tried removing pre-set resolution in 60-evdev.hwdb for G6 model with no difference.
tried installing synaptics client and it detects and actually modifies the touchpad parameters normally but the issue still persists. (too high speed vertically and too low horizontally)."
1825499,2019-10-07 18:32:51 UTC,"Description of problem:
After installing Fedora 30, I found that vertical sensitivity is much higher than horizontal sensitivity."
1825500,2019-04-19 11:38:59 UTC,"Dear Ian,"
1825500,2019-04-30 16:07:00 UTC,This should be addressed in the imminent release candidate.
1825500,2019-04-23 10:24:12 UTC,Here is the content of the models.yaml:
1825500,2019-04-23 10:02:28 UTC,Can you look in ~/.local/share/juju/models.yaml and paste the YAML for the model you are working with?
1825500,2019-04-23 04:26:41 UTC,Tested with HA LXD controllers with tip of 2.6 branch today.
1825500,2019-04-19 14:01:16 UTC,Playing around a little bit I am also noticing that Juju GUI and Juju CLI are updating different mongo documents on the replica set for the same application. And changes with Juju GUI don't trigger the update hook.
1825500,2019-04-19 11:42:29 UTC,"Oops, apologies for the email reply quack."
1825500,2019-04-19 11:26:08 UTC,"We don't read from secondaries. This looks more like the config isn't
getting set."
1825500,2019-04-19 10:37:34 UTC,"Just a note - the config checksums are used to prevent unnecessary firing of the config-changed hook on units. The fact that the bug report seems to say that the config-change hooks are correctly firing each time a config change is made suggests that the change is correctly being stored and propagated to the unit agents. The config checksum is only used on the unit agents, not elsewhere."
1825502,2019-04-19 16:54:51 UTC,loosing out heartbeats and prematurely closes connection
1825502,2019-04-25 09:27:15 UTC,rabbitmq seems to be up on all nodes
1825502,2019-04-19 10:51:29 UTC,"""ping 192.168.100.32 -p 5672"" works fine"
1825502,2019-04-25 09:06:40 UTC,Looks like the problem is with the RabbitMQ clustering. Are all nodes able to communicate with each other without errors? Are the rabbit containers staying up on all nodes?
1825502,2019-04-19 16:13:30 UTC,rabbitmq crash.log
1825505,2019-04-20 00:04:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825505,2019-09-05 16:22:53 UTC,"Yes, definitely fixed."
1825505,2019-07-07 12:53:08 UTC,This seems to be fixed in one of the updates of late. @jerareyoshi - could you confirm?
1825505,2019-04-20 14:11:34 UTC,"^ If this is indeed directly related, I'd guess the priority has to be moved up."
1825505,2019-04-20 10:26:28 UTC,"This bug can also prevent to start the session.
You need then to remove gnome-clocks."
1825506,2020-01-19 16:02:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825510,2019-04-19 16:13:29 UTC,There are sections for
1825510,2019-04-29 10:26:30 UTC,@brian_p
1825511,2019-04-22 13:40:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825511,2019-04-21 22:31:47 UTC,"Searching, I found the following solution:"
1825511,2019-04-23 09:03:40 UTC,The fix works for me too
1825511,2019-08-04 07:25:30 UTC,"This solution works for me too.
Thanks"
1825511,2019-05-10 06:47:40 UTC,Thanks for the solution: it worked
1825511,2019-04-21 23:24:34 UTC,"This solution works for me too.
Grazie mille man."
1825515,2020-02-07 15:18:44 UTC,"Do you still observe the issue on 19.10 or later?
I'm reassigning to a package more related to the potential bug."
1825515,2020-02-07 20:47:59 UTC,"Dear Balint,
Thankyou for your reply concerning my login bug. Fortunately the problem
has disappeared with installation of 19.10 which I am finding to be the
best Ubuntu release since the return to gnome desktop. Many thanks to all
working on desktop Ubuntu for making it so successful.
Cheers, Mike Young."
1825516,2019-04-20 10:19:21 UTC,"Why isn't ""Scheduled xxxxx"" enough? When sending POST requests of volumes to Cinder API, they are just scheduled. There is no guarantee that the volumes are created successfully. That's the reason that horizon shows information messages. If we go to the route you suggest, we need more clear reason that ""Success"" is appropriate."
1825516,2019-04-20 10:20:50 UTC,"In addition, even if ""Success"" message is shown, a volume created can be in ""Error"" state. In this case, ""Success"" is confusing. Users expect a volume requested is created successfully for regular use."
1825516,2019-06-20 04:19:21 UTC,[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]
1825519,2019-04-19 16:23:53 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1825520,2019-04-20 12:14:03 UTC,"Confirmed but marking it as low-hanging-fruit. The current suggested way is to click ""Security Groups"" link at the top bar or in the left bar."
1825520,2020-05-20 07:23:21 UTC,"Hi all, this is my first bug planned to solve and may take time."
1825520,2020-06-17 12:33:44 UTC,"Hi Akihiro,"
1825528,2019-12-15 04:17:49 UTC,[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]
1825528,2019-10-15 17:44:33 UTC,"Setting back to Incomplete: it appears that /boot/efi is not mounted, we're trying to figure out why not. Furthermore, the files installed there are not up to date (probably because they were instaleld to the mountpoint, not to the real location), and SecureBoot is disabled on the system."
1825528,2019-06-25 04:17:38 UTC,[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]
1825528,2019-04-25 23:06:15 UTC,"According to this bug report, your EFI System Partition is not mounted at /boot/efi.  Why not?"
1825529,2020-05-01 12:18:00 UTC,"@jblesener-gensler, cool, thanks! I'd love to know more about how you're using Charmed Kubernetes, if you're interested in sharing. What does your deployment look like?"
1825529,2020-04-10 08:03:56 UTC,"Cory,"
1825530,2019-04-22 06:37:44 UTC,got me during update from 18.10 to 19.04
1825530,2019-04-22 06:33:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825531,2019-05-30 09:11:03 UTC,"It's available now, for the follow-up issue please see bug 1830888"
1825532,2019-05-24 02:47:37 UTC,"Fixed in revision 8c89847627f0f977b0837bb8acf1b2607f42a316
https://git.launchpad.net/kicad/patch/?id=8c89847627f0f977b0837bb8acf1b2607f42a316"
1825532,2019-05-22 18:05:24 UTC,"@Jon, the <space> works perfect. I think I found the last issue.
Now it is not connecting the inverted signals (`~NET~`): unique, in vector or in array. In the project attached the problem are in:
1) `~PWMfault[5..0]~`
2) `~SPI_CS[2..0]~` in the array `{SPI_CLK SPI_MISO SPI_MOSI ~SPI_CS[2..0]~}`
3) `~PWMreset~`"
1825532,2019-05-21 00:55:20 UTC,"That's a bug, I'll fix it!  I appreciate your testing these features, it will help make it more polished by the time we release."
1825532,2019-05-21 00:54:04 UTC,"Thanks @Jon for highlight my errors, I hope my user tests guide you in some way."
1825532,2019-05-16 15:31:56 UTC,"I am re-changing to in progress due the new issues that I found.
Basically (see the attached project) the issues is related with the `{ENC_A,ENC_B,ENC_I,ENC_S,SIG_Z}` or `{CANRX-A,CANTX-A}` structure, not connecting the `SIG_Z` or `CANT*-A`, and more when I use a vector inside it `{PWMtop[5..0],PWMbottom[5..0]}` or `{ADC-A[7..0],ADC-B[7..0]}`."
1825532,2019-05-09 12:37:22 UTC,"@Jon, appear fine now (I tested in some 2 / 3 level hierarchical projects)."
1825532,2019-05-08 02:59:44 UTC,"Hi Hildo
I have put in some more fixes, please let me know if you still see improper connections."
1825532,2019-05-06 15:51:11 UTC,The improvement about the name that I said 2 messages ago. Prioritize:
1825532,2019-05-06 15:24:20 UTC,"Application: kicad
Version: 6.0.0-unknown-09c9db4~86~ubuntu16.04.1, release build"
1825532,2019-05-06 15:21:59 UTC,I delete some parts to be able to share (attached in next message) and I am setting this issue as In-Progress due need some fix.
1825532,2019-05-06 13:26:28 UTC,"@Jon, it fix one use case mine (just one hierarchical level) but create a lot of issue on the a more complex hierarchical board."
1825532,2019-05-05 23:50:36 UTC,"Fixed in revision 09c9db472eecd3035a9de0f0abc36d4f41690578
https://git.launchpad.net/kicad/patch/?id=09c9db472eecd3035a9de0f0abc36d4f41690578"
1825532,2019-05-21 02:54:47 UTC,Fixed in c5f8a6b -- you should be able to add spaces now
1825532,2019-05-05 23:49:12 UTC,"OK, I think I have a fix.  Please check it and let me know if you still see issues."
1825532,2019-04-24 22:10:05 UTC,"Welcome, @Jon."
1825532,2019-05-20 23:31:57 UTC,"Hi Hildo,"
1825532,2019-04-23 03:10:05 UTC,"Thank you for the new test project. You are right that this case isn't handled correctly, I will fix it."
1825532,2019-04-23 02:29:22 UTC,"Yes @Jon. This project worked just fine.
I have one, design now quite more complex (more busses and hierarchical block) and this is not working properly.
I think the issue is related to the fact that (mainly the indicated *):
1) I use a sheet and use in 4 hierarchical blocks;
2) I rename the output bus from `signal[3..0]` to `signal0_[3..0]`, `signal1_[3..0]` ...
3) This ""opened busses"" are resorted in a `ADC[7..0]` *."
1825532,2019-04-21 23:24:17 UTC,Please check again after https://git.launchpad.net/kicad/commit/?id=e2c12d8c2578dc6c3bf7293ccda2d747dfd9761c
1825532,2019-04-21 02:36:47 UTC,The bug still on 201904202302+2b3b26b~82~ubuntu16.04.1 (released at 23h02min).
1825532,2019-04-20 02:35:05 UTC,"This might be fixed by my fix for https://bugs.launchpad.net/kicad/+bug/1825579
Please check again after the next build"
1825532,2019-04-19 19:41:59 UTC,"Also, some times I used the follow resource:
1) Build in the schematic in the hierarchical multi pages (more than one block refer to same SCH file);
2) Make the layout of one of these hierarchical sheets;
3) Copy several times changing the reference names;
4) Synchronize by reference;
5) Have coped multi part layout.
(Sure, I make using a script, but the step can be replicated as above)."
1825532,2019-04-19 14:26:51 UTC,"I though that was related with the fix lp:1823177. Because first, each synchronization had different results."
1825532,2019-04-24 22:11:25 UTC,"""new issue"" = related problem that emerged in last code that fix the (simple) bus case."
1825537,2019-10-30 14:17:43 UTC,This issue was fixed in the openstack/nova 17.0.13 release.
1825537,2019-10-17 23:18:08 UTC,"Reviewed:  https://review.opendev.org/675355
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1bb555c4c981d33de03cf70dfd73cc391d36cb89
Submitter: Zuul
Branch:    stable/queens"
1825537,2019-10-18 18:17:54 UTC,"Reviewed:  https://review.opendev.org/682722
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=343daa98e006e019ef3ce0bc1ee2a6a7fe03c916
Submitter: Zuul
Branch:    stable/queens"
1825537,2019-09-17 19:31:52 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.opendev.org/682725"
1825537,2019-04-19 16:00:22 UTC,Gerrit is down but I've written a functional regression test to recreate the bug and attached it as a patch for now.
1825537,2019-04-19 16:10:49 UTC,Thinking of options to fix this when it happens:
1825537,2019-04-19 16:57:37 UTC,I've got a fix locally for option 1.
1825537,2019-04-19 20:21:42 UTC,Update on the functional recreate test.
1825537,2019-04-19 20:22:24 UTC,This is the fix.
1825537,2019-04-20 22:07:49 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/654066"
1825537,2019-04-20 22:08:08 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654067"
1825537,2019-06-22 13:22:53 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/666959"
1825537,2019-06-24 16:45:11 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/667155"
1825537,2019-06-26 06:43:50 UTC,"Reviewed:  https://review.opendev.org/654067
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ea297d6ffba81c5dc982afe6519de09ff3744cad
Submitter: Zuul
Branch:    master"
1825537,2019-07-04 18:03:28 UTC,"Reviewed:  https://review.opendev.org/666959
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eaa1fc6159ca4437a1e0cbaa77a3da779afb8cb2
Submitter: Zuul
Branch:    stable/stein"
1825537,2019-09-27 09:04:22 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1825537,2019-07-04 18:03:38 UTC,"Reviewed:  https://review.opendev.org/667155
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e6c6178d22db43959103da1400017fa49b18f514
Submitter: Zuul
Branch:    stable/stein"
1825537,2019-07-05 16:16:03 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/669393"
1825537,2019-08-01 19:49:08 UTC,"Reviewed:  https://review.opendev.org/669361
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a977cb28c1c4f2e8d950476fa373326f636dfd6
Submitter: Zuul
Branch:    stable/rocky"
1825537,2019-08-08 14:37:12 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/675355"
1825537,2019-08-08 17:02:35 UTC,"Reviewed:  https://review.opendev.org/669393
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cbf6a46d8fcd3236bff44439c8d143a77167dfe2
Submitter: Zuul
Branch:    stable/rocky"
1825537,2019-08-12 20:41:44 UTC,This issue was fixed in the openstack/nova 19.0.2 release.
1825537,2019-08-12 21:11:26 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1825537,2019-09-17 19:19:17 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/682722"
1825537,2019-07-05 14:23:22 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/669361"
1825537,2019-06-21 20:39:41 UTC,"Reviewed:  https://review.opendev.org/654066
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f4bb67210602914e1b9a678419cf22cfbeaf1431
Submitter: Zuul
Branch:    master"
1825540,2019-07-13 04:18:07 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1825540,2019-05-13 15:17:06 UTC,"Hi, Lee."
1825540,2019-04-19 17:33:37 UTC,We are currently working on a suppress feature for MAAS 2.6. A suppressed test result will still be stored in the MAAS database however no warnings for the test will be shown. We are still working on the UI for this feature in 2.6 but API is currently available
1825543,2019-08-20 01:27:20 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1825544,2019-08-05 10:01:34 UTC,"For me, this bug just started happening when I did a software update yesterday."
1825544,2019-04-19 15:58:50 UTC,"I can still switch to the first virtual console with Ctrl-Alt-F1 and open a new session, also switch between the sessions with ctrl-alt-fX"
1825544,2020-01-24 09:51:39 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1825544,2019-09-02 10:24:34 UTC,Just installed 19.04. added a second account for the kids mother to watch netflix on. when I switched users it switched fine to the other account. however when I switched back to the main account (mine) it was like it just signed me out when switching users and did not keep anything open at all. then I checked processes and the other account (kids mothers account) is completely logged out.
1825544,2019-08-11 20:47:10 UTC,"When I log in to my (regular user) account early morning, the Switch User menu item is not present."
1825544,2019-08-11 20:19:22 UTC,"Following up to my remarks from yesterday: when I logged out of my primary account, I DID see a Switch User menu option from my secondary account.  When I returned to the primary account, Switch User was not present.  But that was yesterday.  On reboot today, Switch User has reappeared in my primary account.  Perhaps a patch has fixed the problem?"
1825544,2019-08-10 19:33:38 UTC,"Like Craig McQueen, I just lost the Switch User menu option within the past two or three days.  I have accepted a few automatic software updates recently."
1825544,2019-06-06 17:27:27 UTC,"After today's system update and upgrade, the fix from comment #8 has disappeared."
1825544,2019-07-09 08:24:14 UTC,"I got this problem after upgrading Ubuntu 18.04 to 19.04. My system was initially installed as KUbuntu, later I've installed Cinnamon so it's a mix of many packages. However, I couldn't change user while logging so I needed to use ctrl+alt+F* and start new session as specified user, then start X server. `startx cinnamon` somehow worked, but there were some issues while running, so I've been googling a bit and this is what I've done:"
1825544,2019-06-05 14:43:40 UTC,"I have the same issue. On my machine I have 2 accounts: and admin account and a regular user account. For the admin - the ""Switch User"" option never appears. For the regular user - the option appears sometimes (can't figure out what the circumstances that cause it to appear are)"
1825544,2019-05-21 12:13:15 UTC,"In reply to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829536/comments/2
please see the attached screenshot."
1825544,2019-04-23 06:44:21 UTC,"I upgraded both machines from Cosmic to Disco. In both instances, the menu item was there before and was gone after the upgrade."
1825544,2019-04-23 02:42:38 UTC,What release was the Switch User option in? I can't see it in either 19.04 or 18.04.
1825544,2019-04-22 17:09:08 UTC,For completeness' sake: Just upgraded another machine and I see the same here.
1825544,2019-04-22 08:57:08 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825544,2019-06-06 12:20:33 UTC,THE GOOD NEWS:
1825545,2019-04-23 02:44:10 UTC,Could you please attach a screenshot or photo of the problem?
1825545,2019-06-22 04:17:36 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1825550,2019-04-22 20:21:02 UTC,"I'm confident this is fixed, but if not, please re-open."
1825550,2019-04-22 19:44:27 UTC,"@Hildo, there have been some changes in this area since you submitted this. Can you still reproduce this? Would you be able to make a short screen recording of this issue?"
1825550,2019-04-23 02:03:23 UTC,"Yes, no more occurences."
1825550,2019-10-12 13:29:14 UTC,I'm having a bug very similar to this in PCBnew in 5.1.4 still. I can file a separate bug report if you'd like.
1825550,2019-10-20 18:52:14 UTC,"@Mike, yes it's a known issue in 5.1.  The 6.0 code that has the fixes is quite different from the 5.1 code, so the fixes can't be easily back-ported."
1825551,2020-03-11 08:42:13 UTC,This is fixed in libserial 1.0
1825551,2020-03-11 08:42:21 UTC,(focal)
1825553,2019-05-06 21:04:42 UTC,"The verification of the Stable Release Update for distro-info-data has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825553,2019-04-23 11:55:48 UTC,The requested precise-esm fixes should be there (once it mirrors) with:
1825553,2019-04-19 18:25:09 UTC,Marking fix-released for cloud-images as streams now correctly report trusty as supported.  This was through a manual distro-info-data change as noted in comment #3 and other changes in streams and distro-info data are needed.
1825553,2019-04-19 18:01:06 UTC,"We have locally corrected the date in /usr/share/distro-info/ubuntu.csv and streams are being regenerated, meaning we will have trusty marked as supported until April 25, 2019 if further changes are not made."
1825553,2019-04-19 18:00:05 UTC,Also adding the simplestreams project as our cloud-images streams are generated by that code and 'supported' was added at the request of multipass and is currently defined by the distro-info supported field.
1825553,2019-04-19 17:58:47 UTC,Streams uses distro-info-data which still contains an EOL date of the 17th which lp:simplestreams uses to determine the value of 'supported' in streams.  Adding distro-info package.
1825553,2019-07-23 16:52:33 UTC,"Marking this as Invalid for simplestreams; the bug here is addressed (AFAIK), and we should track any further discussions separately."
1825554,2019-04-20 06:52:50 UTC,apport information
1825554,2019-04-20 06:52:49 UTC,apport information
1825554,2019-04-19 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825554,2019-04-19 16:48:25 UTC,apport information
1825554,2019-04-19 16:48:24 UTC,apport information
1825554,2019-04-22 02:51:21 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc5 kernel [0]."
1825554,2019-07-02 17:07:00 UTC,Sorry for the late reply.
1825554,2019-11-21 18:53:13 UTC,"I was now able to reproduce this behaviour on Windows as well, and sent it for repair. They changed the LCD panel which was faulty and now everyting's ok. So, sorry for the inconvenience."
1825554,2019-04-30 17:28:07 UTC,"If it's in anyway helpful, here's an Xorg log of my device"
1825554,2019-04-27 13:28:25 UTC,"Hey, it's present in newest upstream kernel aswell."
1825559,2019-04-21 08:53:36 UTC,"Same problem here.  Also I can launch a terminal via keyboard shortcuts, but the focus doesn't seem to get set for the terminal window and nothing I type shows up in there."
1825559,2019-04-21 08:58:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825559,2019-04-21 09:03:37 UTC,related: https://bugs.launchpad.net/mutter/+bug/1817924
1825559,2019-04-21 09:33:22 UTC,It looks like I had some gnome shell extensions that were causing problems.  I was able to get things to work by following the instructions here to disabling them: https://askubuntu.com/questions/591757/how-to-activate-deactivate-a-gnome-shell-extension-from-command-line.
1825559,2019-04-23 02:48:06 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1825559,2019-06-22 04:17:37 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1825560,2019-04-19 18:04:28 UTC,The conflicting label should be tested by different names.
1825560,2019-04-19 21:19:14 UTC,"Also in the new assigning should be replaced the name of each label instance connected to the bus, not just kept the last."
1825560,2019-04-22 13:49:33 UTC,"Worked just fine!
Thinking: this test could be interesting to be called before the PCB synchronization and/or NET file export."
1825560,2019-04-22 16:30:38 UTC,"It should also be caught be ERC, we just added the dialog because this is a behavior change (so previously valid schematics are no longer valid)"
1825560,2019-04-21 23:27:13 UTC,Fixed by https://git.launchpad.net/kicad/commit/?id=a92bb946128772558f121275066497d543436ce3
1825562,2019-07-03 12:29:18 UTC,"The repository has been renamed as part of the OpenDev migration, although usually there should be a redirect in place that makes the old name still work. The new location, as mentioned in the current version of the docs, is https://opendev.org/openstack/devstack/"
1825564,2019-04-22 17:01:20 UTC,You'll want to use the tool ppa-purge from the package ppa-purge to remove the PPAs you have enabled and revert back to the official versions of the package which the PPAs provide. Here's an example from the man page.
1825564,2019-04-23 19:53:41 UTC,"I did my best to purge all PPAs. However, I got 'Warning:  Could not find package list for PPA:' on a couple of them. I tried dist-upgrading nevertheless and it didn’t work. Any suggestions?"
1825564,2019-06-23 04:18:58 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825568,2019-05-26 22:55:46 UTC,"Fixed in revision b40289c1bd3eda7fe322003fcb8e7ef1fd904aeb
https://git.launchpad.net/kicad/patch/?id=b40289c1bd3eda7fe322003fcb8e7ef1fd904aeb"
1825572,2019-05-16 04:13:42 UTC,"Sorry, I was using only 'dgit -d ubuntu clone mariadb-10.1 bionic,-security' to fetch repo contents, apparently need to use 'dgit -d ubuntu clone mariadb-10.1 bionic,-security,-updates' in the future. This is the first time anybody has ever done a non-securiy upload of MariaDB to a stable Ubuntu release."
1825572,2019-04-19 20:48:51 UTC,I'll keep you posted once Oracle published some info on what CVE maps to what actual issue and the page https://mariadb.com/kb/en/library/security/ updates.
1825572,2019-04-29 19:37:12 UTC,MariaDB 5.5.64 was released today and the 5.5 series update for 14.04 is now available.
1825572,2019-05-03 13:59:24 UTC,MariaDB 10.1.39 was released yesterday and the 10.1 series update for 18.04 is now available.
1825572,2019-05-14 19:52:16 UTC,Ping anybody?
1825572,2019-05-15 14:24:09 UTC,"I will be handling it for the security team, thanks Otto."
1825572,2019-05-15 15:32:08 UTC,"Hi Otto,"
1825572,2019-05-16 14:37:38 UTC,"OK, marking mariadb-10.1 as incomplete for now. Let us know once you have an update to sponsor. Thanks."
1825572,2019-05-23 17:56:14 UTC,This bug was fixed in the package mariadb-5.5 - 5.5.64-1ubuntu0.14.04.1
1825572,2019-06-01 18:21:41 UTC,"As documented on https://mariadb.org/about/maintenance-policy/ the 10.0 series is no longer maintained and will not get fixes without special arrangements. For the scope of this bug tracker I am marking it ""Won't fix""."
1825572,2019-06-01 19:08:21 UTC,"The 10.1 series update for 18.04 is now available.
Since the .39 upstream discovered regressions and thus there is now a .40 release which is the best release to ship these security fixes."
1825572,2019-06-05 16:20:32 UTC,"Thanks Otto for providing the update for 18.04.
We just released it and it should be available in the archive in some minutes.
We appreciate all the work you've done."
1825573,2020-05-22 04:17:37 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1825573,2019-04-20 06:40:31 UTC,"So this happened after the final upgrade and a reboot.
Did a second reboot a few hours later and the issue is gone!."
1825574,2019-06-23 04:18:08 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1825574,2019-04-23 08:58:08 UTC,"Thank you for your bug report. Could you add the output of the ""upower -d"" command to the bug?"
1825577,2019-04-22 20:14:03 UTC,"It appears that the landscape-server and landscape-client are from ppa:landscape-19.01.  Previously, we've been running server 18.03 and client 17.03, so this is a recent change in FCB templates."
1825577,2019-04-22 20:49:06 UTC,"Essentially with current charms client gets pointed to landscape.canonical.com even though the server is present in the cluster.
Right now manual config is requires to the client to point to the landscape-server endpoint."
1825577,2019-04-23 07:49:18 UTC,"Yes, unfortunately, this is still not merged: https://code.launchpad.net/~cpe-consulting/landscape-charm/client-relation/+merge/322015"
1825578,2019-04-19 21:25:37 UTC,A patch is available in the working repository:
1825578,2019-04-24 19:28:06 UTC,"Pushed to master and rel_3_3. Tnanks for testing, Bill!"
1825578,2019-04-22 14:10:24 UTC,+1 to swapping the arrow direction.
1825578,2019-04-24 18:15:00 UTC,"Thanks for signing off. I'm going to use this one in my demo of how to merge patches today, so I'm grabbing the bug."
1825579,2019-04-30 14:34:42 UTC,"Fixed in revision 5b226f6c964d0f4eca12ea42e0adf8f4f1acf077
https://git.launchpad.net/kicad/patch/?id=5b226f6c964d0f4eca12ea42e0adf8f4f1acf077"
1825579,2019-04-23 14:03:53 UTC,This will be fixed when we turn on real-time connectivity by default (working through some performance issues first)
1825579,2019-04-23 12:31:41 UTC,"All ok.
I been have just so update color issue when I copy some port and edit it to a different kind (bus->wire or vice-versa), or move a block and press <Ctrl>+z for return to the previous position.
Maybe the update color function could be called when create (coped) the new instance or even edit."
1825579,2019-04-21 23:25:25 UTC,"Please check again after https://git.launchpad.net/kicad/commit/?id=e2c12d8c2578dc6c3bf7293ccda2d747dfd9761c
I have not been able to reproduce this anymore"
1825579,2019-04-21 02:40:06 UTC,"Also, in the video the `ADC-A[7..0]` and `ADC-B[7..0]` are bus port. They are correctly identify internally the hierarchical page as a blue port but, at the block in the root page, they still yellow."
1825579,2019-04-21 02:24:43 UTC,"Just to add some comment, moving the port, sometimes it get the different color (identify as wire port or bus port)."
1825579,2019-04-19 21:43:17 UTC,Reported here: https://answers.launchpad.net/kicad/+question/680336
1825580,2019-04-24 00:47:11 UTC,Also seeing this:
1825580,2019-04-24 16:36:50 UTC,I have submitted upstream: GNOME/gnome-online-accounts#60
1825580,2019-04-23 12:23:20 UTC,Thank you for your bug report. Could you add your journalctl log after getting the issue?
1825580,2019-04-24 00:27:49 UTC,Added journalctl full log on a new install.  Let me know if there's more specific info I can look up or provide.
1825580,2019-04-24 00:28:28 UTC,"Added a log filtered for ""goa-"" items.  Let me know if there's more specific info I can look up or provide."
1825580,2019-04-24 10:18:48 UTC,thanks
1825580,2019-04-24 14:00:00 UTC,"Could you provide some extra details on what you are doing exactly. Is the account reporting an error in the settings/online account panel? Or in evolution?
Where is ""Error 7: Unexpected response from server"" displayed?
What version of exchange/server are you using?"
1825580,2019-04-24 14:17:31 UTC,"The error is in the Online Accounts menu from the settings panel.  The Error 7 appears as a red box over the account sign in window after I enter the same credentials and server address I used in 18.10.  I tested this on Majaro, Pop_OS and Ubuntu with Gnome 3.32 and it happens on all of them, so seems to be related to Gnome itself."
1825580,2019-04-24 14:20:16 UTC,"And on the one machine, the install of 18.10 had the EWS account working, then on upgrade it wouldn't connect--kept asking for the password even after entering multiple times. I deleted the account and tried to set up again, but it failed with this same error."
1825580,2019-04-24 14:56:07 UTC,"Thanks, it does sound like an upstream issue indeed and should be reported upstream on https://gitlab.gnome.org/GNOME/gnome-online-accounts/. Could you do that or would you prefer us to resubmit it there for you?"
1825580,2019-04-24 16:37:14 UTC,https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/60
1825580,2019-04-25 08:37:08 UTC,Thanks!
1825580,2020-05-11 10:47:01 UTC,could you try if that's still an issue in newer Ubuntu series?
1825580,2020-05-11 23:02:00 UTC,Still seeing it on Ubuntu 20.04: Code 6: Unexpected response from server.
1825580,2020-05-12 02:06:48 UTC,"Looking around some more, it seems it may be related to this: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974"
1825582,2019-11-05 06:04:12 UTC,"As of now, master contains the beginning of a nice Python based testing framework. Leaving this bug open until we decide how the OpenStack SDK fits in our roadmap."
1825583,2019-04-24 13:31:41 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/655429"
1825583,2019-04-27 23:40:19 UTC,"Reviewed:  https://review.opendev.org/654692
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6eaa6db0ee01ee5a7b56bc3176914d85e697b96a
Submitter: Zuul
Branch:    master"
1825583,2019-04-25 03:08:47 UTC,"Reviewed:  https://review.opendev.org/655429
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e6ca3838d940dea417cdeffe22c656d222737a7e
Submitter: Zuul
Branch:    stable/stein"
1825583,2019-04-22 13:45:44 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654457"
1825583,2019-04-25 13:39:10 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/655693"
1825583,2019-04-24 02:08:36 UTC,"Reviewed:  https://review.opendev.org/654457
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=13278be9f265e237fc68ee60acfacaa1df68522e
Submitter: Zuul
Branch:    master"
1825583,2019-04-28 02:36:32 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656096"
1825583,2019-07-10 21:39:58 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1825583,2019-07-01 20:34:21 UTC,"Reviewed:  https://review.opendev.org/656523
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ba3ad2d65af20332e768a6df0e2c2d64292f9e2c
Submitter: Zuul
Branch:    stable/queens"
1825583,2019-06-18 03:41:10 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1825583,2019-06-06 06:24:25 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1825583,2019-09-27 09:04:25 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1825583,2019-04-30 14:57:23 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/656525"
1825583,2019-04-30 14:50:10 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/656523"
1825583,2019-04-30 11:36:05 UTC,"Reviewed:  https://review.opendev.org/655693
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=35bda4ec385e4c2b3d4cee07467f5077b13b1dd9
Submitter: Zuul
Branch:    stable/rocky"
1825583,2019-05-26 21:31:06 UTC,"Reviewed:  https://review.opendev.org/656525
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d2ab3cef4eb05e5811d39d740274fdbdd1027a5b
Submitter: Zuul
Branch:    stable/rocky"
1825583,2019-04-30 11:27:07 UTC,"Reviewed:  https://review.opendev.org/656096
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=222f462444b72368cd5f22d4b0ac9baf0bbe8e0c
Submitter: Zuul
Branch:    stable/stein"
1825584,2019-10-02 17:54:51 UTC,"Reviewed:  https://review.opendev.org/662095
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a694952eacfe3a2dac34957cf95d5529eb89d4b2
Submitter: Zuul
Branch:    stable/stein"
1825584,2019-04-23 12:44:55 UTC,"https://review.opendev.org/#/c/647310/ hasn't landed in stable/stein yet, have you tested with it applied?"
1825584,2019-04-23 13:28:03 UTC,"I'm guessing so, because he mentions patching nova.monkey_patch, which is only introduced in that change."
1825584,2019-05-29 21:34:16 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/662095"
1825584,2019-04-23 15:23:16 UTC,"Yes, although that change is not in stable/stein yet, apparently it has been back-ported in RDO. I tried reverting it, but the problem persisted, until I also reverted the change that originally added monkey-patching to API."
1825584,2019-04-23 17:03:55 UTC,"Reproduced the problem (easily) with mod_wsgi, and confirmed that removing the monkey-patching ""fixes"" it."
1825584,2019-04-23 17:37:49 UTC,"Also, FWIW (probably not much), eventlet.monkey_patch(thread=False) seems to allow it to work OK."
1825584,2019-04-25 11:48:54 UTC,"As a follow up of the the thread on the ML [1], it appears that the AMQP hearbeat issues that we were seeing in other OpenStack services running under Apache mod_wsgi were due to a change in container healthcheck."
1825584,2019-05-04 21:05:26 UTC,Actually I'm taking comment #6 back... the issue I'm experiencing when running nova under mod_wsgi is exactly the one reported here.
1825584,2020-04-28 22:28:26 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/724188"
1825584,2020-05-22 15:06:39 UTC,"Reviewed:  https://review.opendev.org/728054
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1caddc4250b4acbdb8a945c8f26a0792bee5e2ed
Submitter: Zuul
Branch:    stable/ussuri"
1825584,2020-04-30 18:14:15 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/724725"
1825584,2020-05-08 02:32:39 UTC,"Reviewed:  https://review.opendev.org/724188
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d6f664524dfa4eecbe3e16fda0fec5359faf84c6
Submitter: Zuul
Branch:    master"
1825584,2020-05-08 02:37:24 UTC,"Reviewed:  https://review.opendev.org/724725
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ca2fe01cc1c73e9ca7b2376ea566db0fe45a44ea
Submitter: Zuul
Branch:    master"
1825584,2020-05-14 12:06:52 UTC,"Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/728054"
1825584,2020-05-14 12:12:03 UTC,"Related fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/728055"
1825584,2020-05-14 12:18:42 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/728057"
1825584,2020-05-14 12:18:54 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/728058"
1825584,2020-05-14 12:20:42 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/728059"
1825584,2020-05-22 17:20:42 UTC,"Reviewed:  https://review.opendev.org/728055
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ed0524606998847a7b1ea9103579d027db092e83
Submitter: Zuul
Branch:    stable/ussuri"
1825584,2020-06-11 10:50:43 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: stable/train
Review: https://review.opendev.org/728058
Reason: i based this on upper-constraitns not lower so this should not be backported to train"
1825584,2020-08-05 21:30:07 UTC,"Reviewed:  https://review.opendev.org/728057
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=280007c870b671de9439efba71fd3916403d15da
Submitter: Zuul
Branch:    stable/train"
1825586,2019-04-20 11:32:51 UTC,"On 20/04/2019 07:04, Cubic PPA wrote:

> Question:
>
> Do you also get the BusyBox if you...?
> 1. Remove the old kernel, as you did previously through `apt full-upgrade`.
> 2. This will also install a newer kernel.
> 3. Select the newer kernel Cubic's Boot Kernels tab?
>
> In other words, if you install a new kernel inside chroot, and if you
> select this same new kernel as your boot strap kernel, do you still get
> the get the BusyBox?
"
1825586,2019-04-20 09:09:43 UTC,"On 20/04/2019 06:22, Cubic PPA wrote:

> Travis,
>
> There are two kernel needed:
>
> #1 - A kernel to bootstrap the ISO. (Basically it tells a computer how
> to read and load files from the ISO, USB, DVD, CD, etc.).
>
> #2 - A kernel for your customized Linux file system. This is the kernel
> your customized ISO will **install** onto a new computer.
>
> I think you are convoluting these two different kernels...
"
1825586,2019-04-25 10:08:38 UTC,"On 25/04/2019 10:37, Tony Travis wrote:

> On 25/04/2019 05:00, PJSingh5000 wrote:
>> Referencing https://help.ubuntu.com/community/Grub2/Submenus, ""By
>> default GRUB 2 sets the most recent kernel as the default.""
>>
>> I had expected that the default kernel would be the most recently
>> installed kernel, but this does not seem to be the case. This is good
>> justification for your original proposal to use the newest kernel as the
>> default bootstrap kernel (for non-server images).
>
> Hi,
>
> I think a better default would be, as I later suggested, following the
> symlink:
>
>    /vmlinuz -> boot/<most recently installed kernel>
"
1825586,2019-04-20 05:22:28 UTC,"Travis,"
1825586,2019-04-20 17:15:30 UTC,"Ok, thanks for the clarification and re-testing..."
1825586,2019-04-20 06:04:28 UTC,Question:
1825586,2019-04-20 17:45:14 UTC,"On 20/04/2019 18:15, PJSingh5000 wrote:

> [...] > Based on your testing above, we probably want Cubic to select the kernel
> that is setup to be the default OS kernel, not necessarily the newest
> kernel. (Of course for server images, this rule wouldn't apply). This
> way, the bootstrap kernel matches the OS kernel, and everything
> (theoretically) should work smoothly.
>
> What do think of this suggestion? In your case, the default kernel would
> be the newest kernel, since that is the one that was setup last.
"
1825586,2019-05-16 01:57:42 UTC,"Based on test results, closing bug report."
1825586,2019-05-13 02:04:44 UTC,Performed additional tests using ubuntu-mate-18.04.2-desktop-amd64.iso.
1825586,2019-04-25 14:50:28 UTC,"Per https://help.ubuntu.com/community/Grub2/Submenus, ""By default GRUB 2 sets the most recent kernel as the default."""
1825586,2019-04-25 15:31:24 UTC,"HOWEVER, the symlinks in the root directory still pointed to the most recently installed kernel..."
1825586,2019-04-25 18:38:34 UTC,"On 25/04/2019 15:50, PJSingh5000 wrote:

> Per https://help.ubuntu.com/community/Grub2/Submenus, ""By default GRUB 2
> sets the most recent kernel as the default.""
>
> I also verified this by manually installing an older kernel ~after~ installing a newer kernel:
>    1. Install kernel_4.17.3, first
>    2. Install kernel 4.16.18, second
>    3. Execute update-grub
>    4. This created /boot/grub/grub.cfg
>    5. The 1st (default) entry in grub.cfg was for newest kernel vmlinuz-4.17.3-041703-generic
>
> The newest kernel takes precedence, regardless of the order in which
> kernels are installed.
"
1825586,2019-04-26 02:02:30 UTC,The following changes are available in the development branch:
1825586,2019-04-26 02:03:35 UTC,"Would you please test the fix for this issue in the *Development* branch, and let me know if it resolves your problem?"
1825586,2019-04-27 00:06:25 UTC,"Fix is now availabe in *Release* branch, revisoon 54."
1825586,2019-04-27 14:46:25 UTC,"On 27/04/2019 01:06, Cubic PPA wrote:

> Fix is now availabe in *Release* branch, revisoon 54.
>
> If you have the Release PPA enabled...
>
>      $ sudo apt update
>      $ sudo apt install cubic
>
> If you have the Development PPA enabled...
> [...]
"
1825586,2019-04-27 15:35:54 UTC,"Tony,"
1825586,2019-04-25 04:00:48 UTC,"Referencing https://help.ubuntu.com/community/Grub2/Submenus, ""By default GRUB 2 sets the most recent kernel as the default."""
1825586,2019-04-27 19:19:01 UTC,Reopening bug. See Comment #18 (https://bugs.launchpad.net/cubic/+bug/1825586/comments/18).
1825586,2019-04-29 20:54:49 UTC,"I'm not familiar enough to know if the issues I've just run into is related to this, but it seems similar."
1825586,2019-04-30 00:17:05 UTC,"On 29/04/2019 21:54, Pico wrote:

> I'm not familiar enough to know if the issues I've just run into is
> related to this, but it seems similar.
>
> With Cubic 2019.04-54 the ISO Boot Kernel defaults to ""the kernel
> version you are currently running"". I believe before it defaulted to
> ""the kernel used to boot the original live ISO"".
>
> When I generate an ISO with this new default option selected, and then
> try to boot to it I hit BusyBox and the error ""(initramfs) Unable to
> find a medium containing a live file system"".
> [...]
"
1825586,2019-04-30 01:48:05 UTC,"Pico,"
1825586,2019-05-01 00:39:39 UTC,"Regarding the boot file mismatch, please see Bug #1827157, ""The vmlinuz and initrd versions listed on the ISO Boot Kernel tab do not match."""
1825586,2019-05-01 02:58:44 UTC,I conducted the following test using Cubic Version 2019.04-54.
1825586,2019-05-01 10:48:51 UTC,"On 01/05/2019 03:58, Cubic PPA wrote:

> I conducted the following test using Cubic Version 2019.04-54.
>
> This test did not result in a ""BusyBox"".
>
> I tested using kernel versions 4.18.0-18 and 4.18.0-15 which are VERY
> similar.
>
> May be the issue occurs when ""INSIDE"" and ""OUTSIDE"" kernel versions are
> significantly different from each other? I will repeat the test with a
> very different kernel, perhaps something like 5.0.0-13-generic.
"
1825586,2019-05-01 14:45:15 UTC,OK. Thanks. I test with mkusb/dus.
1825586,2019-04-25 09:37:23 UTC,"On 25/04/2019 05:00, PJSingh5000 wrote:

> Referencing https://help.ubuntu.com/community/Grub2/Submenus, ""By
> default GRUB 2 sets the most recent kernel as the default.""
>
> I had expected that the default kernel would be the most recently
> installed kernel, but this does not seem to be the case. This is good
> justification for your original proposal to use the newest kernel as the
> default bootstrap kernel (for non-server images).
"
1825586,2019-04-27 16:23:14 UTC,"On 27/04/2019 16:35, Cubic PPA wrote:

> Tony,
>
> The purpose of the Boot Kernels tab in Cubic is to allow you to pick a
> bootstap kernel for your ISO.
"
1825587,2019-04-23 20:09:11 UTC,"ofcourse logout, login, done"
1825587,2019-04-25 20:11:46 UTC,it would be sufficient  just to symlink libfm-qt.so.6 -> libfm-qt.so in /usr/lib/x86* - maybe apt don't like it.
1825587,2019-04-25 19:56:45 UTC,"If you edit your repositories to include sources and make sure to use `sudo` on any `apt` commands, Alf's instructions could work, but it's an advanced and not a good ultimate solution. That solution has been implemented upstream and will be forthcoming."
1825587,2019-04-25 21:58:02 UTC,Gents:
1825587,2019-06-20 03:47:46 UTC,"For Eoan, the fix is now included here:"
1825587,2019-07-08 14:53:23 UTC,"Hello Walter, or anyone else affected,"
1825587,2019-07-08 14:57:04 UTC,"I have accepted the SRU into disco-proposed. That being said, the regression potential field mentions ""The immediate concern is that pcmanfm-qt could require a no-change rebuild, since it is closely tied to libfm-qt"" which is a bit hard to understand for me. Looking at the patch, it doesn't seem to affect the API/ABI, so I was wondering how it could warrant a rebuild of pcmanfm-qt. How does pcmanfm-qt use libfm-qt? Does it pull it in statically during build or something? Or maybe does this actually affect the ABI? I'd like to know that before we proceed with verification."
1825587,2019-07-08 20:36:51 UTC,"Using an upgraded 19.04 system, I enabled proposed and upgraded libfm-qt6 to 0.14.1-0ubuntu2.1. The change does not take affect immediately, but does after stopping and restarting pcmanfm-qt. That can also be accomplished by logging out and back in or by restarting."
1825587,2019-07-08 22:11:19 UTC,"I have since moved on to Lu 19.10 where this problem no longer is happening
. . . it has other problems, but this desktop file problem is seemingly
resolved in 19.10."
1825587,2019-04-25 16:44:36 UTC,@Walter:
1825587,2019-07-15 08:16:19 UTC,This bug was fixed in the package libfm-qt - 0.14.1-0ubuntu2.1
1825587,2019-04-24 00:36:37 UTC,@Alf:
1825587,2019-04-23 20:08:22 UTC,otherwise a local build with the patch applied is cheap
1825587,2019-04-23 18:10:35 UTC,Walter:
1825587,2019-04-23 17:39:10 UTC,"Fritz, the reason you see quick fixes is because LXQt is actively being
developed, unlike LXDE, which hasn't been in a long, long time. There's
a reason why every new release of Lubuntu was essentially a maintenance
release."
1825587,2019-04-23 14:19:09 UTC,"> We could work on ensuring it's in Disco, as we should be able to pull in
> just the patch that fixes it, but it will require testing and a bunch of
> paperwork. Since it has a relatively small impact, I'm a little
> disinclined to go through all that, but we're discussing it. We'll
> update the bug if we go this route.
>
> ** Package changed: pcmanfm-qt (Ubuntu) => libfm-qt (Ubuntu)
>
>
>
@Walter:
"
1825587,2019-04-23 06:00:07 UTC,"@Fritz the key to understanding what that means is that it's changed in *lxqt* rather than in *libfm-qt*. The LXQt project is a catch-all that allows us to link bugs on Launchpad (our bug tracker) with those upstream in LXQt (in GitHub, to be exact). It will auto update when changes have been made. libfm-qt, you'll see refers to the Ubuntu package, or the Ubuntu version of libfm-qt. That version does not include this fix."
1825587,2019-04-22 22:59:00 UTC,"On Sun, Apr 21, 2019 at 5:35 PM Bug Watch Updater <
<email address hidden>> wrote:"
1825587,2019-07-15 08:16:25 UTC,"The verification of the Stable Release Update for libfm-qt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825587,2019-04-25 15:33:06 UTC,"@Alf:
Well I guess I got my answer on this, simply running the list of commands
essentially ""errored out"""
1825588,2019-05-26 22:55:52 UTC,"Fixed in revision e156e4509ccee8aeaaebf8af69fc960232961414
https://git.launchpad.net/kicad/patch/?id=e156e4509ccee8aeaaebf8af69fc960232961414"
1825589,2019-04-22 20:53:05 UTC,From Apttermlog.txt:
1825589,2019-05-17 07:44:21 UTC,I just did upgrade from 18.10 to 19.04 and had the same problem. I am not sure what's the damage done. After rebooting I had to manually run `apt autoremove` to remove the old packages. I haven't tested other things yet that I depend on.
1825589,2019-05-17 07:42:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825590,2020-01-24 09:44:30 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1825590,2019-04-24 10:18:24 UTC,looks like bug #1734095 then (though the other one describe the auth failing but no locking)
1825590,2019-04-23 21:12:16 UTC,"Here is the tail of /var/log/syslog when I try and fail to select Canonical Partners"""
1825590,2019-04-23 12:22:47 UTC,Thank you for your bug report. Could you add your journalctl log after getting the issue?
1825591,2019-05-23 12:13:33 UTC,"I checked the feedback in the Feedback Hub and there is not any more information there either about the issue. The issue seems to be in WSL, not in Ubuntu and it can't be fixed in Ubuntu packages. :-("
1825593,2020-05-21 16:13:27 UTC,Update fixed it for me.
1825593,2020-06-15 02:04:15 UTC,"Cas,"
1825593,2020-06-12 19:54:37 UTC,I don't think this is quite fixed.
1825593,2020-05-22 12:03:47 UTC,"Thanks folks, this works for me now as well."
1825593,2020-05-22 05:55:55 UTC,"The update fixed it for me as well. Thanks for the effort to everyone involved in fixing, reporting, etc."
1825593,2020-05-21 08:04:26 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825593,2020-05-19 02:02:36 UTC,"Karl,"
1825593,2020-05-20 02:43:29 UTC,Yeah 'mutter' is a binary that we actually don't use in Ubuntu. The part we use for gnome-shell is 'libmutter'.
1825593,2020-05-14 13:22:22 UTC,Not working for me with the proposed package:
1825593,2020-05-14 10:06:40 UTC,Upgraded from proposed updates and it works like a charm.
1825593,2020-05-13 02:07:23 UTC,The cursor issue is bug 1873052.
1825593,2020-05-12 22:31:54 UTC,"Also to add, the cursor from GDM gets stuck after shell loads, now i have two cursors on the screen, one I control and a second on from gdm thats just stuck there."
1825593,2020-05-12 20:26:39 UTC,"Hello hackel, or anyone else affected,"
1825593,2020-05-07 06:15:28 UTC,This bug was fixed in the package mutter - 3.36.2-1ubuntu1
1825593,2020-05-04 06:32:32 UTC,We are tracking the issue in this bug now. Sorry for any confusion.
1825593,2020-05-01 20:23:16 UTC,"Hello people
So the bug report https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860 is closed, and this post you said it's not a suitable thread. (and at the same time gnome refuses to fix it and Ask Ubuntu closes the bug)."
1825593,2020-04-27 19:26:51 UTC,"Also this is not just scaling that is not remembered, but also screen relative positions."
1825593,2020-04-27 19:25:27 UTC,"Gnome Shell closed the report submitted by Evgeny saying it's an Ubuntu downstream feature.
The duplicate bug 1852860 looks now like a more suitable candidate for tracking at it is assigned to the proper project (?)."
1825593,2020-04-26 20:47:16 UTC,Bug report for gnome-shell submitted: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2690
1825593,2020-04-26 20:26:53 UTC,"What I found is, when I'm saving my settings in monitors.xml, is have the following:"
1825593,2020-04-25 03:56:13 UTC,"On fresh install of 20.04, 2 x LG 4K displays, AMD 5600XT GPU"
1825593,2020-04-21 01:49:10 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825593,2020-04-20 19:10:13 UTC,"Hey, can you verify this again in 20.04?"
1825593,2019-12-07 21:47:23 UTC,"I just installed 19.10 on a new laptop with a 4K display and am experiencing this same issue.  Once I enable x11-randr-fractional-scaling, scaling and orientation settings with an external display are not remembered.  I have to set them over again each time I log in.  The ~/.config/monitors.xml file looks right."
1825593,2019-04-23 08:57:31 UTC,Thank you for your bug report.
1825593,2020-05-14 15:13:10 UTC,Not working for me either.
1825593,2020-05-21 08:04:07 UTC,This bug was fixed in the package mutter - 3.36.2-1ubuntu1~20.04.1
1825593,2020-05-12 22:28:53 UTC,"Went ahead and enabled proposed updates, updated the machine and rebooted, fractional scaling and display arrangement was remembered. When logging into x11 there was a ""big"" flicker and display fragments but cleared up once shell loaded. on wayland I dont get the options for frac. scaling even when its enabled. I think thats a separate issue though."
1825593,2020-05-19 22:35:54 UTC,"Hi Daniel,"
1825593,2020-05-15 02:07:21 UTC,I should have thought of this earlier...
1825593,2020-05-15 00:59:43 UTC,Confirming that this is not fixed in Mutter 3.36.2-1ubuntu1~20.04.1
1825593,2020-05-14 15:14:16 UTC,Built in display resets to 200% and move to right hand side of external display on reboot.
1825593,2020-05-18 23:02:59 UTC,"Hi Daniel,"
1825597,2019-04-20 10:50:53 UTC,This was a problem with all of the modern tools and was fixed about 2 days ago.
1825598,2019-04-20 04:21:10 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1825598,2019-04-20 12:18:16 UTC,Left all my systems and routers unplugged all night.
1825598,2019-04-20 20:18:31 UTC,"Hello,"
1825598,2020-11-17 01:16:44 UTC,This bug was fixed in the package virtualbox - 6.1.16-dfsg-4
1825598,2019-04-23 01:36:18 UTC,"Hi,"
1825601,2020-05-22 04:17:38 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1825604,2019-07-01 08:01:57 UTC,This bug was fixed in the package netbeans - 10.0-3ubuntu2~18.04.1
1825604,2019-05-21 22:24:41 UTC,This bug was fixed in the package netbeans - 10.0-3ubuntu2
1825604,2019-06-13 16:17:58 UTC,"Hello agent, or anyone else affected,"
1825604,2019-06-13 17:03:10 UTC,"Hello agent, or anyone else affected,"
1825604,2019-06-13 17:04:04 UTC,"Hello agent, or anyone else affected,"
1825604,2019-06-27 19:49:24 UTC,"I have verified netbeans 10.0-3ubuntu2~18.04.1 from -proposed on 3 releases: bionic, cosmic, and disco; the fix works on all of them and it now requires a java11-jdk (or the default-jdk which is openjdk-11-jdk on these releases) to be installed."
1825604,2019-07-01 08:00:48 UTC,"The verification of the Stable Release Update for netbeans has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825605,2019-04-25 10:35:38 UTC,"No, they didnt, i still have acess to all of them"
1825605,2019-04-21 13:06:05 UTC,Did you happen to add any scripts?
1825605,2019-04-20 09:01:57 UTC,Please update to the latest stable (5.1.0) as the 5.0.0 series is no longer supported.
1825605,2019-04-21 14:09:58 UTC,"No, at least, dont remember adding any.
Files in the folder:
bitmap2component
eeschema
fp-lib-table
gerbview
kicad
kicad_common
KicadFrame.hotkeys
pcbnew
PcbNew.hotkeys
sym-lib-table
+ an empty 3d folder"
1825605,2019-04-22 13:29:17 UTC,Ive found a solution to my problem! All i needed to do is to delete pcbnew related files from %appdata%/kicad. I guess they gor corrupted and screwed my installs.
1825605,2019-04-22 14:04:59 UTC,Did you make a backup of the files before deleting them? It would be interesting to see if there was something unexpected.
1825605,2019-04-24 09:45:02 UTC,"Yes, here they are"
1825605,2019-04-24 15:03:31 UTC,You have some files located in network shares in your recently used paths. Did they change/become unavailable?
1825605,2019-04-20 16:50:58 UTC,"I have updated to 5.1.0_1 however the issue is still present. Im launching pcbnew from kicad launcher, however I tried to launch it standalone and got same result. I didnt make any changes on my PC on purpose, however ive added external parts library to kicad. The library however works on ubuntu, so it should not be the issue.
Full version information:"
1825605,2019-06-25 04:17:30 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1825607,2019-04-24 12:17:51 UTC,"Thanks a lot for this,"
1825609,2019-06-12 20:52:31 UTC,"On Wed, Jun 12, 2019 at 5:40 PM Sylvestre Ledru
<email address hidden> wrote:

>
> This patch https://salsa.debian.org/science-team/scilab/commit/af933fa83ed0cc731b54a8369888b7b165775798
> fixes the issue
> should be trivial to cherry-pick this change
"
1825609,2019-04-24 12:08:34 UTC,I was informed that the problem is only with scilab 6.0.1. You need to upgrade to version 6.0.2. Please put in repository version 6.0.2
1825609,2019-04-24 12:38:50 UTC,please check that this is fixed in the 19.04 disco release.
1825609,2019-04-25 10:36:05 UTC,"Unfortunately, I can't be sure, because I use Ubuntu 18.04 and I don't want to change the system, especially not the LTS version."
1825609,2019-06-12 20:12:15 UTC,Problem still happens in scilab 6.0.2 on Eoan.
1825609,2019-06-12 20:32:03 UTC,"The code for input(message) (see /usr/share/scilab/modules/io/macros/input.sci) calls prompt(message) and then mscanf(format_string). The prompt() function is meant to modify the prompt for the next user interaction, but for some reason calling this function does nothing at all."
1825609,2019-06-12 20:32:54 UTC,"This patch https://salsa.debian.org/science-team/scilab/commit/af933fa83ed0cc731b54a8369888b7b165775798
fixes the issue
should be trivial to cherry-pick this change"
1825609,2019-06-12 20:33:29 UTC,"Please notice that this only affects the GUI Editor (aka scilab), the scilab command line tool (ie. scilab-cli) works as expected."
1825613,2019-04-21 18:56:01 UTC,I think I see exactly the same on linux with master:
1825613,2019-04-20 07:41:06 UTC,Are you really still at release canditate 1? That is not really a release but a pre release. Update to the latest real release and report back if you still expirience the same problems. (depending on your operating system this will be either 5.1.0 or 5.1.1 as the later might not yet be available on all platforms)
1825613,2019-04-20 09:35:54 UTC,"@Paul, is that a nightly build or one you did yourself?  In either case, how recent is the code?"
1825613,2019-04-20 09:37:14 UTC,"(Note that I can't reproduce it, whereas I had no trouble with your other reports, so I think your code is a bit out-of-date.)"
1825613,2019-04-20 13:24:29 UTC,"@jeyjey,"
1825613,2019-04-20 13:38:44 UTC,"Also, thank you for pointing this out! I was unaware of the distinction between 5.1.0 and 5.1.1."
1825613,2019-04-20 19:48:06 UTC,"@Paul,"
1825613,2019-04-21 19:01:25 UTC,What I observe is that I can hold down the m key and it will move the symbol around on the screen following my mouse pointer. That do feel slightly laggy. But the reason that it seems to move it is that pressing m actually seems to update the canvas. Follow this:
1825613,2019-04-21 19:04:15 UTC,The same happens when moving symbol refdefs and value fields.
1825613,2019-04-21 22:39:15 UTC,This started to happen with the following commit.
1825613,2019-04-22 15:08:57 UTC,"@jeyjey,"
1825621,2019-04-23 12:20:56 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1825621,2019-06-23 04:18:16 UTC,[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]
1825621,2019-06-26 09:31:37 UTC,"Sehr geehrte Damen und Herren,
mein Problem ist gelöst. Ich habe Ubuntu 18.04 neu auf mein
Laptop installiert und die ""Textbearbeitung"" funktioniert jetzt
reibungslos.
Ich bitte zu entschuldigen, dass ich mich nicht mehr gemeldet habe."
1825623,2019-04-24 12:52:41 UTC,It looks like SOLVED my issue.
1825623,2019-04-24 12:30:31 UTC,"Sorry, forgot to attach screen shot image of my Post #7."
1825623,2019-04-21 19:15:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825623,2019-04-24 11:45:39 UTC,I have upgraded from Ubuntu 18.10 to 19.04 by do-release-upgrade command and I have exactry the same problem.
1825623,2019-04-24 11:48:07 UTC,The error in the screenshot seems like it's different from the appindicator log error? Did you submit it? If you click on report problems do you get more details on the issue?
1825623,2019-04-24 12:28:04 UTC,"Hi,
Error dialog box that I posted was popped up almost at same time when the following syslog was generated."
1825623,2020-06-08 09:10:53 UTC,"Hi all,"
1825623,2020-03-24 20:16:52 UTC,Me too // 3/24/20 4:11 PM	session-7.scope	Failed to load snap icon: local snap has no icon
1825623,2020-03-24 12:24:58 UTC,This bug was fixed in the package gnome-shell-extension-appindicator - 33-1
1825623,2020-02-18 13:46:10 UTC,Same issue here. This appears to cause major freezes during several seconds every time I receive a desktop notification and unlock my computer.
1825623,2019-08-20 18:04:28 UTC,"I have now reinstalled the extension and having been running for a day without problems. This leads me to think that this a persistent data, rather than code related problem. I can only assume that the purge reinstall cycle removed whatever was causing the problem."
1825623,2019-07-13 09:46:15 UTC,I have seen a number of issues related to this error message. Including slow wake up from sleeps. Long pauses in screen repaint. Long launch times for applications. The only sure fix I found was to completely purge the gnome-shell-extension-appindicator package and reboot. The system them becomes properly responsive again. I have no idea what visual flim flam this extension provides so I can certainly do without it. It is a shame that it is installed by default.
1825623,2019-05-22 13:04:27 UTC,"I get the same error in my log, and I was researching thinking it had to do with the KeepAwake Gnome-Shell extension:"
1825623,2019-04-30 18:00:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825623,2019-04-24 14:26:39 UTC,"Sorry, I have't took memo of file name and I couldn't recover deleted file.
However I'm sure that it was not Update-notifier."
1825623,2019-04-24 13:29:51 UTC,How was the file you deleted named? Did you report the issue? It does look different from the bug here indee
1825623,2019-04-23 11:57:48 UTC,Where is the error displayed? in the log or do you get an UI dialog? if so could you take a screenshot?
1825623,2019-04-24 02:27:54 UTC,I see this error in the logs.
1825624,2019-04-23 20:36:06 UTC,apport information
1825624,2019-04-23 20:36:02 UTC,apport information
1825624,2019-04-23 20:40:06 UTC,"I attach a screen shot. You will see that there are only two icons in the Dash to Dock Gnome extension. For the sake of clarity, I am not using the Ubuntu Dock extension."
1825624,2019-04-23 02:56:06 UTC,Could you please attach a screenshot or photo to clarify which dock you are talking about?
1825624,2019-04-23 20:36:04 UTC,apport information
1825625,2019-04-23 02:58:22 UTC,"Actually, this might not be the problem I was imagining..."
1825625,2019-04-23 08:00:37 UTC,Thanks!
1825625,2019-04-24 07:41:14 UTC,"Re #7: 90% of the applications experience this and that should be normal? Huhh.
Re #8: Fix released? So it could be fixed? What was the issue? How do we get the fix?"
1825625,2019-04-24 07:59:06 UTC,"Ignore the ""Fix Released"" comment. It is a mistake in the bug tracker. The upstream bug was closed because it was rejected, not fixed (https://gitlab.gnome.org/GNOME/mutter/issues/566)."
1825625,2019-04-23 07:42:51 UTC,"With framebuffer scaling some applications (e.g. the settings app) do work fine. Others don't (e.g. Firefox, but also LibreOffice)"
1825625,2020-04-15 03:56:25 UTC,My proposed branch (for integer scaling cases) was closed in favor of
1825625,2020-01-24 02:02:55 UTC,"Despite what I said in comment #7 I also now have a partial fix proposed:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/845"
1825625,2020-01-24 01:40:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825626,2019-05-16 02:07:29 UTC,/var/log/syslog shows the following line whenever it freezes up:
1825626,2020-02-16 09:09:49 UTC,"No, but this event seems to happen most often when I go in/out of fullscreen mode in celluloid (gnome-mpv) while playing a video with subtitles:"
1825626,2019-05-17 21:35:43 UTC,"I have the same problem. Running 19.04, 418 driver and GeForce MX150. Any news about a possible fix?"
1825626,2020-02-03 01:44:12 UTC,This sounds like the Nvidia driver not being patient enough to cope with gnome-shell's slowness. We have the same kind of issue with libinput too. But it is improving with each gnome-shell release...
1825626,2020-02-02 23:46:25 UTC,I can also report this bug
1825626,2019-05-27 18:10:33 UTC,UPDATE: I've upgraded the driver to 430 and the persists.
1825626,2019-04-21 00:31:27 UTC,"I have the exact same error.
Laptop: MSI GL62M 7REX
GPU: Nvidia GeForce 1050 Ti
Started after i upgraded to 19.04"
1825626,2019-04-21 00:33:38 UTC,"I tried older kernel, older nvidia-driver and switching to lightdm. Nothing helped."
1825626,2019-04-21 00:38:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825626,2019-05-14 08:41:00 UTC,"Same here with ubuntu 19.04, mentiond driver version and a Quadro M620"
1825626,2019-05-16 01:45:28 UTC,"Happening to me as well, with 418 drive, on 19.04 with a Geforce 940MX"
1825626,2019-12-19 17:54:11 UTC,This has been happening for a bit on a work computer that went through the built in update process to 19.10.
1825626,2019-11-14 08:45:09 UTC,"To add on my previous comment: after moving to 19.10 (which I think also comes with its pre-bundled nvidia driver, in any case I'm on 430 now), the issue seems to be greatly mitigated compared with what I was having on ubuntu 19.04... like I'm getting it once a day at most (no consistent repro case though)"
1825626,2019-05-19 16:09:47 UTC,"I have the same problem when enabling Nvidia Kernel Mode Setting. (nvidia-drm modeset=1)
Random freeze (about 1-2s)."
1825626,2019-11-04 08:38:16 UTC,"After upgrading to ubuntu 19.10 (and mutter 3.34.1), I cannot consistently reproduce it as I used to before (vscode tab drag or chrome bookmark drag) but I still managed to get it randomly while upgrading some gnome extension"
1825626,2019-06-09 04:28:50 UTC,"Same issue for me, also only appeared on Ubuntu 19.04, same freezing on Window resizes, moving windows or right clicking."
1825626,2019-06-17 13:20:52 UTC,This problem appears to been have resolved with nvidia 430.26-0ubuntu0~gpu19.04.1 for me.
1825626,2019-10-23 19:37:32 UTC,I am seeing this in 19.10 (POP_OS). Nvidia 1060. Mutter is indeed at 3.34.
1825626,2019-06-17 21:44:59 UTC,"I spoke too soon, it's back again this morning when I accidentally clicked and dragged a hyperlink in Chrome:"
1825626,2019-06-18 07:32:42 UTC,"the test of ""dragging hyperlink"" in Chrome  (or even a bookmark, or a tab in VSCode) is how I am able to replicate this issue 99% of the time myself.. I have a gut feeling it has something to do with transparency and possibly fonts (the dragged item becomes semi-transparent)"
1825626,2019-07-22 20:58:04 UTC,"Hi,"
1825626,2019-07-22 21:02:24 UTC,"That's so bad formatted, please take a look here at this gist:"
1825626,2019-07-23 12:20:57 UTC,For it was an issue with mutter:
1825626,2019-07-23 16:18:50 UTC,"@fguerlek I just tried downgrading mutter as suggested, but to no avail"
1825626,2019-07-24 18:43:32 UTC,3 months open and no closer to a fix :(   I tried downgrading mutter also but still seeing the issue.
1825626,2019-07-29 18:43:55 UTC,"i have same problem
ubuntu 19.04"
1825626,2019-08-15 08:28:49 UTC,"For using desktop/gnome/work, work-around for me is using :"
1825626,2019-08-29 11:59:05 UTC,"I can see this freeze also, and as other stated on a prime-laptop only in nvidia mode."
1825626,2019-08-29 12:21:45 UTC,A discussion at https://forum.manjaro.org/t/desktop-gnome-frequently-get-frozen-few-seconds-and-works-again/81603/29 for manjaro seems to nail down:
1825626,2019-08-29 12:25:20 UTC,"Did anyone try setting __GL_MaxFramesAllowed=1 as discussed in https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 ?
It helped me to get rid of the lockups on manjaro (didn't try on ubuntu though)"
1825626,2019-11-14 07:57:08 UTC,"Hello Everyone,
Any progress on this? I have the same problem here, and I had to deactivate my Nvidia graphical card to be able to use my computer..."
1825626,2019-09-24 10:10:26 UTC,"same problem here
Ubuntu 18.04"
1825626,2019-06-01 18:57:01 UTC,"I have the same problem, bug also appears with the 390 and 430 drivers. Only appeared after updating to Ubuntu 19.04."
1825626,2019-10-18 14:51:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825626,2019-10-21 02:25:30 UTC,Sounds like maybe a fix/workaround went into mutter 3.34. Does anyone see this problem in Ubuntu 19.10?
1825626,2019-10-24 12:21:50 UTC,Happy to try and make this happen.. I believe I can make it happen pretty reliably on my system. Perhaps I can do something while profiling gnome?
1825626,2019-10-24 01:41:06 UTC,I guess we need to reproduce the mutter freeze that the Nvidia driver is telling us about and with some luck force a stack trace or core dump while it is happening.
1825626,2019-10-24 01:37:06 UTC,Scrolling back I can't see why I was thinking that in comment #29.
1825628,2019-04-22 17:04:21 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825628,2019-04-22 17:08:07 UTC,Suggest that this si a duplicate of https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1784242
1825628,2019-04-22 17:06:22 UTC,This fixed it immediately for me:
1825629,2019-04-24 18:19:16 UTC,"I removed dropbox and google-chrome-stable, but it did not help.
/var/log/dist-upgrade/apt.log contains several Broken things, here is some extraction:"
1825629,2019-06-26 04:17:22 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825629,2019-04-26 21:50:59 UTC,The whole log file is about 300 kB. Should it be attached?
1825629,2019-04-22 20:49:00 UTC,"I was unable to recreate this bug after restoring the apt-clone file provided in the attachments. The only difference, according to apt-clone, between the system I test with and your system was the fact that my system had apt-clone and dpkg-repack installed while your system had dropbox and google-chrome-stable. Perhaps it is one of those two packages causing the failure to calculate the upgrade. Please try removing them and report back regarding your results. Thanks in advance."
1825632,2019-04-22 14:58:04 UTC,This looks to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420  Can you please confirm?
1825632,2019-04-20 11:30:04 UTC,This change was made by a bot.
1825635,2019-04-20 11:37:47 UTC,"Sorry, my Ubuntu version is Bionic, not Cosmic (I don't know why I wrote Cosmic?). I use Falkon  3.0.0-0ubuntu3"
1825636,2019-06-03 12:34:35 UTC,"OK, so it appears to be within the kernel itself, this is also happening when using openRC."
1825636,2019-06-03 19:05:01 UTC,"Fun fact: sometimes ""syncing filesystems"" is done before the system actually suspends, sometimes it is done after waking the system up:"
1825636,2019-06-03 13:01:50 UTC,Thanks for your research and input!
1825636,2019-04-20 16:11:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825636,2019-04-20 17:19:04 UTC,Same problem has existed for years on Ubuntu 16.04 with systemd and TLP in use. pm-utils is installed by default but for the most part inactive (last log entry Oct 28 2018).
1825636,2019-05-14 02:06:56 UTC,Also affecting Thinkpad X201 with Ubuntu 18.10 and TLP.
1825636,2019-06-01 10:10:29 UTC,Same issue here. Suspend happens before user space is suspended.
1825636,2020-09-16 04:17:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825636,2019-06-03 12:04:57 UTC,"Since I was affected on Ubuntu 19.04 using the generic Kernel (5.0.0-15-generic), I am not sure if ""linux-signed-hwe"" is the right thing to file this bug against..."
1825636,2020-07-17 10:14:00 UTC,"Hi, sorry for not replying. I don't own the L390 anymore.
But I can confirm this happened with a vanilla installation and with TLP installed. There was no difference in the behaviour.
I also believe this is not a problem only affecting the L390."
1825636,2020-07-09 06:33:48 UTC,The same behavior usually has different root cause.
1825636,2020-07-09 07:42:23 UTC,I bet 500 dollhairs they're being marked as duplicate in two seconds.
1825636,2020-07-09 05:42:00 UTC,Hey has the Status been changed from confirmed to incomplete? Ubuntu -devel is still affected.
1825636,2020-07-03 23:12:03 UTC,Reply to #22 (Timo Jyrinki):
1825636,2020-07-17 11:34:57 UTC,"I suggest that everybody with this problem files a report similar to this one.
It's a bit of work, but probably the only way to give it some weight."
1825636,2020-06-30 07:53:22 UTC,I'm no kernel triager but I have a few observations that can help focusing the bug report:
1825636,2020-05-08 05:28:35 UTC,simillar problem on HP EliteBook running Ubuntu 19.04
1825636,2020-03-26 08:49:34 UTC,Same issue here: S3 enabled only after wake up.
1825636,2020-02-17 17:07:37 UTC,I have similar issue on Ubuntu 19.10 + Toshiba R850.
1825636,2020-02-04 10:33:25 UTC,I've got a similar issue too. Any workaround available ?
1825636,2020-02-02 12:15:34 UTC,"Any update on this? I am using Ubuntu 19.10 on my XPS 15 9560 and I am facing this behavior, however, I am not using the signed kernel package, I believe it applies to the mainline as well."
1825636,2019-12-09 09:36:00 UTC,"Same issue
ThinkPad T460P with Nvidia GTX 940MX and Intel i7-6820HQ
Linux Mint 19.2 Cinnamon (Ubuntu 18.04) with kernel HWE 5.0.0-37-generic
Put in Sleep on Friday evening.
On Sunday in the middle of the day it did go into emergency wakeup because the battery did go empty.
On Monday morning I did boot it with my connected power supply and wondered why I have only 0% battery left."
1825636,2019-09-30 07:55:57 UTC,"Recently bought an L390 Thinkpad and noticed the battery drain when suspended. Checked the syslog and observed the same issue you've reported. Just tried it out on several other laptops, as well as a desktop lying around in the office. Can confirm that this issue affects all of them. Here's a list:"
1825636,2019-09-24 14:49:21 UTC,"Similar issue here with Ubuntu 19.10(5.3.0-10-generic) on Lenovo X1 Extreme Gen2 - i7-9750H, GTX 1650(nvidia-driver-435)"
1825636,2019-08-19 18:01:56 UTC,"Same issue with Ubuntu Mate 19.04 on Lenovo Thinkpad T460s.
Notebook gets warm and drains about 20% of the battery when in standby."
1825636,2020-07-17 09:55:33 UTC,Can confirm that this bug is also affecting Dell Latitude 7490 with Ubuntu 18.04 LTS
1825636,2019-08-05 20:17:25 UTC,"Same issue with Ubuntu 19.04 on Lenovo X1 Extreme (i7 6 core, Nvidia GPU with NVIDIA drivers).
Notebook gets warm/drains battery when in standby.
Log looks like some suspend tasks continue after waking up from standby."
1825636,2019-07-24 20:52:42 UTC,Facing the same issue elementary OS Juno which is based on Ubuntu 18.04. System suspends before kernel suspends all processes. Significant battery drain occurs.
1825636,2020-07-09 06:20:54 UTC,"Although this kind of bug /may/ seem device dependent, in this instance it's not."
1825636,2020-07-09 05:56:14 UTC,Because there's no response from the original bug reporter.
1825637,2019-05-07 07:47:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825638,2019-04-22 10:25:44 UTC,"Thanks, partially helped.
Ubuntu starts up normally, Kubuntu doesn’t run, which is a pity, because KDE I already like a lot more. I will stay at the Manjaro."
1825638,2019-04-22 07:45:29 UTC,"The system use Nvidia graphics, please use ""safe graphics mode"" provided by the live usb."
1825638,2019-04-22 07:02:22 UTC,in attach
1825638,2019-04-22 06:44:32 UTC,Not seeing lspci-vnvn.log here.
1825638,2019-04-20 12:07:48 UTC,"How to make them when loading live-usb, if you consider that the system does not boot and does not even give the command line interface?"
1825638,2019-04-20 12:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825640,2019-04-23 13:43:35 UTC,"It is an intermittent bug.  Sometimes, boot up is no problem and the Ubuntu splash screen does its usual thing.  Other times, (infrequently) normal blank screen boot sequence but without splash screen towards the end - just straight into login prompt.  At this point, after logging in all seems fine but after a short time a popup dialog box appears saying there is a problem and asks whether to report or not.  The problem is, it is not the normal sort of crash report and there is no confidence that report has been submitted and so I raised this manual bug report."
1825640,2019-06-25 04:17:32 UTC,[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]
1825640,2019-04-25 12:05:14 UTC,Just done update and noticed these upgrades; (includes plymouth) Will upgrade and advise if I see bug again.
1825640,2019-04-23 19:18:36 UTC,Added journalctl log for April 20 which from memory is when it happened - quite big sorry.
1825640,2019-04-23 14:39:48 UTC,Can you add a journalctl log from a boot having the issue?
1825640,2019-04-23 12:13:53 UTC,Thank you for your bug report. What's the issue? Do you get the wrong logo? No logo? A video showing the boot could help there...
1825640,2019-04-20 12:36:56 UTC,Same as Bug #1825509 but different device/laptop
1825641,2019-05-06 15:56:02 UTC,"@Anton, we still need bug reports filed against nightly builds not just release builds.  This helps us keep the nightly builds as usable as possible.  That's why it is critical to include the version information in bug reports so we don't waste time trying to determine in which branch a bug exists."
1825641,2019-05-06 14:23:55 UTC,"In my opinion, everything is much simpler. I used the git version of the program. I came to the conclusion that the overwhelming majority of errors occur for a banal reason and only in the git-version. Because in the place where errors occur, the work on one or another component has not yet been completed, it has not been brought to its logical conclusion. It is more expedient to react to bugs in the release versions (not in the git version), where all the work on the bug fixes and changes has been completed. In release 5.1.2, everything is fine with the text field. There are no such problems.
Release 5.1.2 is stable, with the exception of some artifacts from ratsnest and one crash. Users must use only latest release version, not latest git snapshot."
1825641,2019-05-06 13:39:54 UTC,Would it be possible for you to test this using version 5.1.2?  I cannot duplicate this on the latest 5.1 branch.  It could be an issue with gtk2 as I am using gtk3 on my linux builds.
1825641,2019-04-21 03:19:03 UTC,"The error manifests itself when you copy (via button C, context menu), transfer (via button M), for some reason you need to click several times to place, then the copy disappears when you try to double click on it."
1825641,2019-04-21 03:16:56 UTC,The text field lives its own life)
1825641,2019-04-21 03:13:43 UTC,"Application: kicad
Version: (5.1.0-291-gc5effadb2), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.63.0 OpenSSL/1.1.1a zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.34.0
Platform: Linux 4.19.8-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.63.0
    Compiler: GCC 8.2.1 with C++ ABI 1013"
1825641,2019-04-20 12:51:09 UTC,I can not reproduce this in kicad 5.1.1 under ubuntu 16.04.
1825641,2019-05-06 14:25:42 UTC,"As for the bug, you can write fix committed and so on."
1825642,2020-09-14 07:41:45 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1825644,2020-06-29 09:33:21 UTC,"Despite the merge of https://github.com/mixxxdj/mixxx/pull/1937 this problem still exists in master. Does anybody have an idea, how this could be solved?"
1825644,2019-04-28 06:56:29 UTC,"Looks like QT parses the language name from the file name. No matter the language node in the *.ts file or the content of the *.qrc file.
https://github.com/mixxxdj/mixxx/pull/1937"
1825644,2019-04-28 09:50:31 UTC,Fix for .tx file in https://github.com/mixxxdj/mixxx/pull/2092/commits/51a4e4e960aaf3b8dd45686aae597ab034135de4
1825644,2020-06-29 09:35:15 UTC,The commit was only meant to solve the problem for the double entry of german language. Can the fix be adapted to the other double language entries?
1825647,2019-04-20 16:20:08 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. We noticed that you were installing the LTS version of Ubuntu using an older version of the installation media.  The latest point release of 16.04 is 16.04.3. Please try installing from that version of the installation media and see if that resolves your issue. Thanks in advance!
1825647,2019-06-20 04:19:25 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1825648,2019-04-23 12:24:30 UTC,Thanks!
1825648,2019-04-21 13:52:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825648,2019-04-23 09:09:36 UTC,"Thank you for your bug report, could you also report it upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ ?"
1825648,2019-04-23 11:57:33 UTC,"I submitted bug on Gitlab:
https://gitlab.gnome.org/GNOME/nautilus/issues/1005"
1825648,2020-03-08 22:26:42 UTC,this still happens in 19.10
1825651,2019-05-06 14:37:29 UTC,This is the backtrace of the bug.
1825651,2019-05-06 13:53:00 UTC,Using the steps described it doesn't hang there. Could you get a backtrace using the instructions on https://wiki.ubuntu.com/Backtrace#Already_running_programs ?
1825651,2019-05-04 15:47:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825651,2019-04-24 16:21:25 UTC,Thanks
1825651,2019-05-06 16:27:18 UTC,This is the output after (gdb) t a a bt:
1825651,2019-04-24 12:17:04 UTC,"Magnet link is a kind of torrent without the need of downloading a torrent file (you just add link and it starts downloading).
I tried to use journalctl and this seems to be where the problem is:"
1825651,2019-04-23 12:12:58 UTC,Thank you for your bug report. What is a magnet? Could you add your journalctl log to the bug after getting the issue?
1825651,2019-05-06 14:40:58 UTC,This is the video of the whole process in case you need it.
1825651,2019-04-24 16:08:08 UTC,"The issue seems to only appear when directly clicking link from browser. You can go to https://nyaa.si/ in the ""Link"" column, there's U-like symbols, those are magnet link. Just click it."
1825651,2019-05-06 15:27:15 UTC,"Thanks, it's a bit weird that ctrl-C in gdb doesn't work and that you don't get a prompt back after killing the process. Could you try by exiting transmission and doing
$ gdb transmission-gtk
(gdb) r <enter>
... get the issue
(gdb) <Ctrl-C>
(gdb) t a a bt"
1825651,2019-04-24 13:32:25 UTC,Could you give an url example to test the issue?
1825651,2019-05-07 09:47:40 UTC,"The backtrace doesn't have anything obviously wrong (it lacks debug symbols also but unsure it would make a difference), setting back to ""New"" until someone has time to poke at it more, unsure why it doesn't happen here and is so consitent for you though"
1825651,2019-05-07 09:47:59 UTC,(do you use any non default option maybe?)
1825651,2019-05-07 10:33:41 UTC,I don't use any non default option. I remember this problem suddenly happened to me one day during the time of ubuntu 19.04 beta and it's still there when I freshly installed ubuntu 19.04 stable.
1825651,2019-05-07 10:54:15 UTC,Could you maybe also report it to the upstream code writers on https://github.com/transmission/transmission ?  They might have a better clue about the issue
1825652,2019-04-20 14:38:38 UTC,Is it possible to exclude this directory from debsums checking?
1825653,2019-04-20 17:44:15 UTC,homebank version ?
1825653,2019-04-20 18:07:00 UTC,Completed.
1825653,2019-04-20 23:41:36 UTC,5.2.4 for Linux has the same issue. I suppose this problem started after the tags implementation. My transactions since 2010 are a little bit messy.
1825653,2019-04-21 13:39:36 UTC,"@andre: not related, purely related to
1821458
1814213"
1825653,2019-04-22 03:17:27 UTC,"Hi Maxime.
I've read 1821458 and 1814213 as you suggested and I got it what was going on with me. In fact, I wasn't marking the option ""force monitoring this category"" in the subcategories. I did it only for categories and I was using this way until now. I really thought that marking this option only for category, would be enough to force the monitoring for all subcategories below it.  Yet it was working properly before the update, I believe.  I noticed I was wrong after has sight the example you have sent and I understood how to configure them.  Thank you very much."
1825653,2019-04-27 16:27:04 UTC,"Confirmed. If all the subcategories are forced, then computation is correct.
It was not necessary in 5.2.2.
Workaround is ok for me.
Thank you."
1825653,2019-04-29 11:15:08 UTC,"Still this is a bug, now fixed for next release."
1825653,2019-04-30 01:56:40 UTC,"Maxime, thank you so much."
1825655,2019-10-24 15:24:40 UTC,"If I am not mistaken, Disco/19.04 doesn't have the fix backported yet:"
1825655,2019-10-24 14:55:39 UTC,Yes.  Tried that.  Still getting the corrupt python3 error message.
1825655,2019-05-13 23:18:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825655,2019-10-23 21:01:35 UTC,Just hit the exactly same issue while trying to upgrade from 19.04 to 19.10
1825655,2019-10-23 23:08:55 UTC,"> Just hit the exactly same issue while trying to upgrade from 19.04 to 19.10
"
1825655,2019-10-24 00:44:25 UTC,"I'm experiencing the same issue as Nikita above.  I have tried to reinstall python3, I have tried replacing the symlinks, nothing has fixed this.  Help?"
1825655,2019-11-05 20:23:56 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825655,2019-11-05 20:23:43 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.15.2
1825655,2019-11-05 20:19:32 UTC,I tested this by installing python2 on an Ubuntu 19.04 system then symlinking /usr/bin/python to /etc/alternatives/python - an empty file but that's fine. I then ran 'do-release-upgrade' and received the error message in the description. I then ran 'do-release-upgrade -p' and the upgrade proceeded.
1825655,2019-10-24 03:04:49 UTC,"On Thu, Oct 24, 2019 at 12:44:25AM -0000, wolfgang rumpf wrote:

> I'm experiencing the same issue as Nikita above.  I have tried to
> reinstall python3, I have tried replacing the symlinks, nothing has
> fixed this.  Help?
"
1825655,2019-11-01 17:47:52 UTC,"I'm not really sure, if I am doing Brian's proposal right."
1825655,2019-10-31 21:45:53 UTC,"Hello Dmitrii, or anyone else affected,"
1825655,2019-10-24 19:17:38 UTC,"I do have python2 installed, but my /usr/bin/python points to /usr/bin/python3"
1825655,2019-10-14 16:08:05 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.15
1825655,2019-11-01 21:24:55 UTC,"Testing the distribution upgrade tarball is a bit different - you need to run ""do-release-upgrade -p"". Modifying /etc/apt/preferences.d/ is unnecessary."
1825659,2019-04-23 15:38:30 UTC,no it's not related.
1825659,2019-04-20 15:48:26 UTC,"Is this related to the recently you merged PR:
https://github.com/mixxxdj/mixxx/pull/2057"
1825662,2019-09-02 16:03:30 UTC,"I did a quick test, temporary dirs are set and work fine. We set both of these in snap-confine to ""/tmp"" and they are actually bind-mounted from the host' /tmp/snap.<snapname>/tmp."
1825663,2019-08-15 14:34:13 UTC,it works with the 430 driver from the graphics-drivers ppa: https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
1825663,2019-04-21 14:00:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825663,2019-08-13 07:44:16 UTC,today Ubuntu notified me that updates are no longer provided for 18.10 and that I should switch to 19.04.
1825663,2019-08-15 13:52:22 UTC,it also affects the nvidia 390 driver. startup after entering the unlock key takes ~1 minute. Here are all lines containing some nvidia from /var/sys/syslog:
1825663,2019-09-14 13:19:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825664,2019-04-20 18:15:44 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1825664,2019-04-21 22:54:13 UTC,"Yes, it appears I'm still using the version from https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak. Should I report the bug there instead?"
1825664,2019-04-21 23:57:41 UTC,Thanks for the info !
1825664,2019-06-21 04:17:23 UTC,[Expired for flatpak (Ubuntu) because there has been no activity for 60 days.]
1825665,2019-04-23 12:12:16 UTC,Thank you for your bug repor.t. Can't you use the GNOME settings to do that? Is the resoluton not listed or what is the issue?
1825665,2019-04-27 09:46:53 UTC,"Hi Sebastien,"
1825665,2019-04-27 09:48:42 UTC,"Oh here were are, I found my original report from 2016 when this started happening."
1825665,2019-04-29 07:32:24 UTC,It seems rather a kernel issue if modes are missing. if the request is to be able to add custom modes under GNOME/wayland you should probably report that request directly upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues
1825665,2019-04-29 08:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825665,2019-05-04 16:55:51 UTC,Thank you for the guidance.  I will do so!
1825665,2019-07-04 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825666,2019-09-19 09:29:32 UTC,"Yeah, Debian didn't do an upload of a new version since quite some time so the change that I was waiting on to happen (in April) didn't arrive yet."
1825666,2019-09-20 08:14:06 UTC,This bug was fixed in the package virt-manager - 1:2.2.1-0ubuntu2
1825666,2019-09-20 06:25:14 UTC,I ensured that in a system I used virt-manager in I can autoremove
1825666,2019-09-19 08:16:51 UTC,python-requests dependency still exists in virt-manager 1:2.2.1-0ubuntu1 on Ubuntu 19.10
1825666,2019-09-20 06:28:00 UTC,"uploaded to Eoan, lets check migration in a bit"
1825666,2019-04-23 10:41:52 UTC,"TL;DR: Nothing to do, it will resolve itself"
1825670,2019-04-23 06:10:53 UTC,Fixed in x1.3.1-53.
1825673,2019-04-20 19:10:11 UTC,when will this problem fixed?
1825673,2019-04-23 03:05:00 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1825673,2019-06-22 04:17:38 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1825678,2019-07-23 18:14:20 UTC,apport information
1825678,2019-07-23 18:13:16 UTC,"The same bug happens in Kubuntu 19.04. Since I've now bought a USB WiFi dongle, I can now file a report from a laptop where the internal WiFi card is down. apport-collect information included below, the key highlights are:
iwlwifi 0000:03:00.0: Error, can not clear persistence bit (full context in CurrentDmesg.txt)"
1825678,2019-04-22 06:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825678,2019-04-23 13:34:50 UTC,apport information
1825678,2019-04-23 13:34:52 UTC,apport information
1825678,2019-04-23 13:34:53 UTC,apport information
1825678,2019-04-23 13:34:54 UTC,apport information
1825678,2019-04-23 13:34:57 UTC,apport information
1825678,2019-07-23 18:14:18 UTC,apport information
1825678,2019-04-23 13:34:58 UTC,apport information
1825678,2019-04-23 13:35:01 UTC,apport information
1825678,2019-04-23 13:35:02 UTC,apport information
1825678,2019-04-23 13:35:04 UTC,apport information
1825678,2019-04-23 13:35:06 UTC,apport information
1825678,2019-04-23 13:34:56 UTC,apport information
1825678,2019-04-23 13:35:08 UTC,apport information
1825678,2019-04-23 13:35:10 UTC,apport information
1825678,2019-07-23 18:14:28 UTC,apport information
1825678,2019-09-28 16:08:38 UTC,"After finding a few reports of similar issues caused by a hardware problem, I replaced the WiFi card. For a month since, I've had no issues, which suggests it was a hardware problem. Therefore, I'd like to close this report"
1825678,2019-07-23 18:14:39 UTC,apport information
1825678,2019-07-23 18:14:37 UTC,apport information
1825678,2019-07-23 18:14:35 UTC,apport information
1825678,2019-07-23 18:14:33 UTC,apport information
1825678,2019-07-23 18:14:32 UTC,apport information
1825678,2019-07-23 18:14:30 UTC,apport information
1825678,2019-07-23 18:14:43 UTC,apport information
1825678,2019-07-23 18:14:27 UTC,apport information
1825678,2019-07-23 18:14:26 UTC,apport information
1825678,2019-07-23 18:14:41 UTC,apport information
1825678,2019-07-23 18:14:23 UTC,apport information
1825679,2020-07-21 15:07:06 UTC,"Rafael,"
1825679,2020-05-05 10:35:42 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825679,2020-05-05 15:48:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:"
1825679,2020-05-05 15:48:32 UTC,Could you also add a 'journalctl -b 0' log after getting the issue?
1825679,2020-07-05 04:17:31 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1825679,2020-07-21 14:07:30 UTC,"I also had this problem and the suggested workaround helped solving it. Actually, it additionally solved a delay issue on login screen when recovering from suspension and a delay on xdotool commands. Is it possible to reopen this bug report or should I open a new one?"
1825679,2020-07-22 01:13:04 UTC,'apport-collect 1825679' won't work because I'm not the author or because the report is closed. I'm attaching the journalctl output.
1825679,2020-07-22 01:54:56 UTC,"Rafael,"
1825682,2019-08-19 21:23:27 UTC,This is also true of the Ruby example.  I finally found someones library which works: https://rubygems.org/gems/maas-client/versions/0.3.1
1825686,2019-05-08 00:38:45 UTC,"Patch for ""19.04_STABLE"" branch: https://reviews.mahara.org/9974"
1825686,2019-04-24 01:08:47 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9839"
1825686,2019-05-21 02:55:30 UTC,"Commit hash: 8a9cd410809c24c8a93647a7aa9cd7a51d59e1b7
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw"
1825686,2019-05-21 22:55:26 UTC,"Reviewed:  https://reviews.mahara.org/9974
Committed: https://git.mahara.org/mahara/mahara/commit/158c68b0d64da2dca66b637e4cc192e02ef7c708
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.04_STABLE"
1825686,2019-06-24 06:43:06 UTC,Liam also fixed that the content chooser is sticky again and doesn't scroll.
1825686,2019-05-04 09:27:09 UTC,The content chooser will change in 19.10. Thus only relevant for 19.04.
1825691,2019-04-23 09:08:40 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
*  Could you try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report"
1825691,2019-06-23 04:18:10 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1825698,2019-04-21 07:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825698,2019-04-22 15:24:15 UTC,"Yes.. It looks like it is same problem.
As the bug 1825420 referred to virtual ubuntu, I thought this requires separate reporting.
You can consider this duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420 if it doesnt matter whether it is in virtual os or ubuntu"
1825698,2019-04-22 15:02:33 UTC,This looks to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420.  Can you please confirm?
1825698,2019-04-21 11:51:33 UTC,"Sorry I cannot add the log files now since i do not have the said kernel. I am running Ubuntu 19.04 now with 4.18.0-17.
But I can tell you what the error message was."
1825699,2019-04-24 17:07:14 UTC,"The kernel paramter ""psmouse.elantech_smbus=0"" did the trick.
Thank you very much. No need to downgrade."
1825699,2019-04-22 07:46:57 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1825699/"
1825699,2019-04-22 06:48:45 UTC,Could you try passing the following parameter in kernel cmdline:
1825699,2019-04-21 07:00:13 UTC,This change was made by a bot.
1825701,2019-06-17 20:25:17 UTC,Fix by dennisat.
1825701,2019-06-17 20:24:57 UTC,Fixed in x1.3.1-68
1825703,2019-04-27 12:42:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825705,2020-07-02 00:21:18 UTC,"This was not actually a fault in spamassassin but rather dpkg had gotten stuck in a dependency loop, and spamassassin was just the first thing to trip.  This was likely fixed by 1828639, I will dupe it up."
1825706,2019-04-21 11:34:43 UTC,"I am using Xubuntu 18.10 and I find that the delete key does not function at all, unless an image is opened in a separate window.
I have re-compiled Geeqie v1.3 with 18.10 and I find the same problem, so I suspect the problem is originating outside Geeqie.
I have only an ancient laptop with me at the moment, and it will be a couple of weeks before I am back home (where I have a more extensive range of ancient computers) and can take an in-depth look at this."
1825706,2019-04-21 10:26:19 UTC,Just to add that my second work-around isn't working as I thought. It's actually creating a folder called trash: in the same folder as the images. Didn't notice that before.
1825707,2019-05-09 06:25:09 UTC,I think ordering by date is fine.
1825707,2019-05-05 11:51:12 UTC,You can move a topic already:
1825707,2019-05-05 17:42:26 UTC,"The redirect would be for humans, not for the software. This would save us from having to PM topic participants about the move."
1825707,2019-05-05 19:07:09 UTC,"> This would save us from having to PM topic participants about the move.
"
1825707,2019-05-05 20:02:52 UTC,It depends. I sometimes only look at specific forums.
1825707,2019-05-05 20:26:09 UTC,"> Another way to solve this problem would be to show a user's posts in their profile,
"
1825707,2019-05-05 21:32:47 UTC,Let's prioritize that then - I want this a lot more than the temporary redirect.
1825707,2019-05-07 05:25:07 UTC,Do you want the same ordering as we have for the 'More latest posts' view? Currently it is ordered by date.
1825707,2019-09-06 08:14:23 UTC,Issue moved to https://github.com/widelands/widelands-website/issues/218
1825707,2019-05-15 20:25:06 UTC,Can we change the bugs title and description to 'move posts ...' now?
1825708,2019-04-21 10:37:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825709,2019-04-23 03:07:31 UTC,This sounds most likely related to temporal dithering (FRC) on the LCD screen.
1825709,2019-04-23 12:13:30 UTC,"Hello Mr. Daniel for your quick reply.
Unfortunately, I do not have a video recording of the issue. I have even
roll back my system to a previous back up since the issues was too
burdersome that i was not able to use my laptop correctly. That was
because, each reboot, I needed to go to tty and change the permissions (
owner) of the file .Xauthority and .ICEauthority, then recall 'startx' from
the tty. and even so the the graphic issue persist. now with the roll back
since last night  things are seem fine."
1825709,2019-06-23 04:18:15 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1825710,2019-04-23 03:08:19 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825710,2019-06-12 17:17:30 UTC,Note that the gnome-shell-extension-no-annoyance extension exists (presumably as a workaround rather than a solution to this bug).
1825710,2019-06-12 17:22:18 UTC,This window that keeps appearing is very annoying.
1825710,2019-06-13 02:04:24 UTC,Tracking upstream in: https://gitlab.gnome.org/GNOME/gnome-shell/issues/358
1825710,2020-01-01 10:48:24 UTC,"For some reason this behaviour is much more apparent in Ubuntu 19.10 (actually the CPU has more threads too, maybe it is also a hint..)"
1825710,2020-02-08 16:48:07 UTC,"Instead of saying ""Windows is ready"", the window should to usable at that instance instead of manually going through it."
1825710,2020-02-10 01:52:37 UTC,Since this is an upstream design issue please put future comments in the upstream bug:
1825710,2020-03-10 14:48:31 UTC,tagging rls-ff-notfixing that's an usability issue but not one we have the resources to address this cycle
1825710,2020-03-10 15:42:41 UTC,"I'll add that since updating from 18.04 to 20.04, Pidgin has been doing this very consistently.  Whenever I have Pidgin focused and then switch focus to another window, some time later, I get a notification saying:"
1825710,2020-03-10 15:52:00 UTC,"Yes, it's not just Pidgin - other apps do it as well."
1825710,2020-03-10 15:54:15 UTC,"I will add that when I see this in Pidgin, it leads me to believe someone has highlighted me, but no, no one has and I just spent some time context switching.  And this keeps happening over and over again..."
1825710,2020-10-28 10:42:03 UTC,"Can I add a +1 to this. Am using Gnome 3.63.3 on 20.04. The 'is ready' notifications from 'Microsoft Teams - Preview' are numerous and completely pointless, as more often than not, nothing noticeable has actually happened in the application. It's extremely distracting, as I don't know when the notification represents something actionable in the app or not."
1825710,2020-10-29 01:20:38 UTC,"To ""+1"" a bug you click the green link at the top of the page:"
1825710,2020-11-30 14:05:36 UTC,"I added +1 to this, since this notification is really irritating and not really useful."
1825711,2019-04-21 11:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825711,2019-06-21 04:17:20 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825712,2019-05-16 08:51:37 UTC,"The verification of the Stable Release Update for bind9 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825712,2019-04-22 19:52:14 UTC,Thanks for filing this bug in Ubuntu.
1825712,2019-04-22 20:27:17 UTC,Do you have an example at hand of such a breakage? It will make the testing and SRU easier. Something like using dig with @localhost and asking for info for such a public zone.
1825712,2019-04-22 21:16:51 UTC,Maybe this test is good.
1825712,2019-04-22 22:27:45 UTC,"I don't have simple test case, I use unbound as resolver.  I noticed the problem with my authoritative bind9 server failing to sign zones using Ed25519 keys with ""unsupported algorithm"" or similar error.  I just had to rebuild bind9 with eddsa support (and add the symbol) to keep on going."
1825712,2019-04-23 17:41:52 UTC,"This is also a good test, and doesn't require networking:"
1825712,2019-04-29 16:49:31 UTC,This bug was fixed in the package bind9 - 1:9.11.5.P1+dfsg-1ubuntu4
1825712,2019-05-08 20:10:53 UTC,"Hello Teemu, or anyone else affected,"
1825712,2019-05-09 07:52:46 UTC,This fixes the ed25519 zone signing for me.
1825712,2020-09-03 15:08:26 UTC,"For what it's worth, Bionic's bind9 version should support EdDSA according to https://bind.isc.org/doc/arm/9.11/man.dnssec-keygen.html
I dunno how well it would work on 9.11.3 though."
1825712,2020-03-04 17:45:20 UTC,"It's a valid request, I'm just not sure if the version of bind in bionic is good enough for this support. I vaguely remember reading somewhere that certain encryption types were not working well in certain versions of bind9 (sorry, very vague, I know). Because of that I'm confirming the bug, but this would have to be investigated."
1825712,2019-05-09 13:20:56 UTC,Disco verification:
1825712,2020-02-19 18:21:09 UTC,"This is also a problem in bionic. At least with bind9utils. On the system I tested I don't have bind9 available. I wanted to create a Ed25519 ZSK. Could this be backported? I wanted to add an Affects Link, but got an error instead."
1825712,2019-05-16 08:51:29 UTC,This bug was fixed in the package bind9 - 1:9.11.5.P1+dfsg-1ubuntu2.4
1825712,2020-02-27 15:47:58 UTC,It was never in Bionic and only added as a feature later.
1825714,2019-04-21 14:06:27 UTC,Try the solution from my answer on AskUbuntu - https://askubuntu.com/a/1135027/66509 .
1825717,2019-05-07 18:15:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825717,2019-05-07 18:16:49 UTC,"Same issue on 18.04.
Can PGP server present a problem for users outside of USA?"
1825717,2019-06-01 06:56:10 UTC,Additional Feedback.
1825717,2019-06-13 09:50:47 UTC,"The same problem with hplip-3.19.5.
Some notes from https://www.linuxquestions.org/questions/linux-software-2/hplip-keeps-looping-at-plug-in-installation-4175647505/ by user zaskar_84"
1825717,2019-06-14 01:06:21 UTC,Brilliant! Solved my problem.
1825717,2019-07-03 13:48:05 UTC,To the HP developers at HP:
1825717,2019-05-07 17:27:32 UTC,"I re-created the same issue on another install, this time Ubuntu-Budgie 19.04.
Same issue happened, same solution fixed it."
1825718,2019-10-04 09:48:42 UTC,This bug was fixed in the package linux - 5.0.0-31.33
1825718,2019-09-06 13:03:09 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1825718,2019-04-21 13:00:07 UTC,This change was made by a bot.
1825718,2019-04-21 14:03:54 UTC,"Please add psmouse.dyndbg=+p to the bootargs, boot the kernel, then upload the dmesg."
1825718,2019-04-21 14:33:49 UTC,"Hi Hui Wang,"
1825718,2019-04-22 03:02:08 UTC,"Oh, your touchpad is i2c-hid, so it has nothing to do with psmouse."
1825718,2019-04-22 04:54:43 UTC,Please check the latest dmesg.
1825718,2019-04-22 05:03:43 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1825718/"
1825718,2019-04-22 06:12:45 UTC,"Hi Kai-Heng Feng,"
1825718,2019-04-22 06:58:17 UTC,https://lkml.org/lkml/2019/4/22/38
1825718,2019-04-22 07:13:33 UTC,Okay..thank you
1825718,2019-07-09 12:56:39 UTC,"Can you please test this kernel:
https://people.canonical.com/~khfeng/lp1835040-2/"
1825718,2019-04-21 14:53:01 UTC,"Added psmouse.proto=bare to ""/etc/default/grub"" and rebooted.
GRUB_CMDLINE_LINUX_DEFAULT=""quiet splash psmouse.dyndbg=+p psmouse.proto=bare"""
1825718,2019-09-02 15:25:02 UTC,"Hi Kai-Heng Feng,"
1825718,2019-10-01 04:20:01 UTC,"Andan,
Can you please test latest mainline kernel? I think this commit can fix your issue:
commit 670784fb4ebe54434e263837390e358405031d9e
Author: Kai-Heng Feng <email address hidden>
Date:   Tue Apr 30 16:37:53 2019 +0800"
1825722,2019-07-01 14:28:00 UTC,Is this issue specific to Disco and Eoan?  Or does this happen in other releases as well?
1825722,2019-07-01 17:15:04 UTC,"To those affected, there are Disco and Eoan builds here for testing: https://launchpad.net/~teward/+archive/ubuntu/anki-1825722"
1825722,2019-07-01 23:16:26 UTC,"I did my testing locally in an Eoan and a Disco VM, and this fix does indeed work."
1825722,2019-07-01 23:28:26 UTC,SRU template applied.
1825722,2019-07-02 02:02:28 UTC,This bug was fixed in the package anki - 2.1.8+dfsg-1ubuntu1
1825722,2019-07-02 20:48:41 UTC,"Hello Fiona, or anyone else affected,"
1825722,2019-07-05 07:01:24 UTC,I've installed and successfully tested anki 2.1.8+dfsg-1ubuntu0.19.04.1. Testing included my usual use of anki:
1825722,2019-07-08 21:54:20 UTC,I went ahead and also confirmed the verification was completed for anki in Disco Proposed.
1825722,2019-07-10 21:46:06 UTC,This bug was fixed in the package anki - 2.1.8+dfsg-1ubuntu0.19.04.1
1825722,2019-07-10 21:46:12 UTC,"The verification of the Stable Release Update for anki has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825722,2019-07-26 20:21:05 UTC,"This worked for me, thanks! Anyway, I would like to point out that this is a problem upstream and it would be nice to port the fix to Debian. I have emailed the maintainer a couple of times because of this issue but never got an answer. It would safe to consider upstream to be unmaintained at this point, I guess."
1825722,2019-04-25 21:26:37 UTC,Proposed fix also worked for me. But look & feel of app is quite ugly. Are there maybe different skins/themes? I.e. a GTK3 CSS.
1825722,2019-04-23 01:07:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825725,2019-04-21 15:46:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654254"
1825725,2019-04-26 10:17:59 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/655863"
1825725,2019-04-27 01:24:33 UTC,"Reviewed:  https://review.opendev.org/655863
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=383a94a3f4ae21d777db1033921a6cdc282a9f40
Submitter: Zuul
Branch:    stable/stein"
1825725,2019-05-25 04:57:37 UTC,"Reviewed:  https://review.opendev.org/654254
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=587a273f5f885739635d401b0f97c563fa0cad6b
Submitter: Zuul
Branch:    master"
1825725,2019-09-25 08:47:31 UTC,This issue was fixed in the openstack/zun 4.0.0.0rc1 release candidate.
1825726,2019-06-22 04:17:39 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1825726,2019-04-23 03:12:55 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1825731,2019-05-16 07:58:06 UTC,I don't think we are seeing this any longer so going to close it out. Taking as example the job in the description it is very green at time of writing http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-scenario003-standalone
1825733,2019-05-05 13:34:01 UTC,"On 2019-05-05 14:16, Gordon Lack wrote:

> FYI: There's a screenshot (in English, so not a translation issue)
"
1825733,2019-05-10 15:00:47 UTC,I've uploaded this to the Disco queue and is waiting for review and the current SRU to be verified / age.
1825733,2019-05-14 15:41:15 UTC,"Hello Ferry, or anyone else affected,"
1825733,2019-05-14 21:00:19 UTC,Verified the test case; resulting string:
1825733,2019-05-07 17:57:15 UTC,s/mutter.mo/ubuntu-release-upgrader.mo/
1825733,2019-05-22 15:09:37 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.16.5
1825733,2019-05-22 15:09:45 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825733,2019-05-07 17:52:22 UTC,"On 2019-05-05 22:27, Ferry Toth wrote:

> @Gunnar ""However, I wonder from where the first occurrence of ""18.10""
> in Ferry's screenshot comes from..."" definitely not from
> window_main.ui then.
"
1825733,2019-05-05 23:43:00 UTC,"It's not the first occurrence of ""18.10"" that's the issue; it's the second, which should have been 19.04."
1825733,2019-05-05 20:27:06 UTC,"@Gunnar ""However, I wonder from where the first occurrence of ""18.10"" in Ferry's screenshot comes from..."" definitely not from window_main.ui then. Maybe is overwritten by translation text?"
1825733,2019-05-05 12:18:42 UTC,Sorry - that should have said that the screenshot is in: https://bugs.launchpad.net/bugs/1827669
1825733,2019-05-05 12:16:28 UTC,"FYI: There's a screenshot (in English, so not a translation issue) at https://bugs.launchpad.net/bugs/1825733"
1825733,2019-04-23 13:27:24 UTC,"@Brian: Updating window_main.ui ought to fix this, right?"
1825733,2019-04-22 21:40:47 UTC,"I suppose that Kubuntu uses qt, and it looks like the DistUpgrade/window_main.ui file was not updated in this upload:"
1825733,2019-04-22 20:17:05 UTC,"You are probably right. In that case:
- the EN version does not state FROM which version
- the NL version first line ""Upgrading Ubuntu 18.10 to version 18.10"" is not translated and should be ""Opwaarderen Ubuntu 18.10 naar versie 19.04"""
1825733,2019-04-22 16:52:13 UTC,"I tried recreating this by upgrading an Ubuntu 18.10 system to Ubuntu 19.04 and the dialog I received, in English, indicated that it was in fact upgrading to Ubuntu 19.04. Subsequently I suspect this is a translations issue."
1825733,2019-04-22 11:26:37 UTC,"The attachments may be reporting wrong versions. It appeared to be impossible to report the bug from the machine where I was performing the update, so I had to turn to another one."
1825733,2019-05-10 00:03:22 UTC,"After the fix of window_main.ui in eoan I installed Kubuntu 19.04, started an upgrade using the command:"
1825733,2019-05-09 21:49:43 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.4
1825734,2019-05-17 14:05:33 UTC,"The extra-nrpe-args config parameter has been available for months now. However, check_http timeout is also dependent on hard-coded check_nrpe timeout on the nagios-charm."
1825736,2019-04-21 18:30:08 UTC,This change was made by a bot.
1825736,2019-04-23 11:25:25 UTC,"I did not have this problem prior to upgrading to 19.04. The upgrade process was an upgrade from 18.04 to 18.10 with an immediate upgrade to 19.04 (after a clean reboot), so there was no usage of 18.10 as a desktop environment to compare with. The 18.04 install was kept up to date."
1825736,2019-04-22 05:21:41 UTC,Is this a regression? Does this issue happen to previous kernel releases?
1825736,2020-01-07 14:44:33 UTC,"Updating to 19.10 hasn't fixed the problem, but I have just replaced my mouse and found the issue is no longer there with the new one. The original was a Microsoft Wireless Mobile Mouse 1000 (045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth) and the new one is a Logitech M220 (046d:c534 Logitech, Inc. Unifying Receiver)."
1825736,2020-06-19 11:43:47 UTC,"This is sporadically reproducible for me. It's probably a hardware quirk. I have Ubuntu 20.04 with Linux 5.4.0-37-generic. I'm using a ""Microsoft Mobile Mouse 4000"" which presents itself as 045e:07b2 ""Microsoft Corp. 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop 900"". The issue only occurs when the transceiver is plugged into a desktop USB hub (MBHUB-43ST presenting as VIA Labs 2109:2813). When it is working, inspecting the event stream with cat /sys/kernel/debug/hid/.../events while slowly scrolling gives a series of events of size 3:"
1825736,2020-01-08 09:57:16 UTC,"I've now tested the Microsoft mouse on my desktop computer and the scroll wheel works find after a suspend / resume, so this looks to be a clash with the hardware in the laptop - a Lenovo G510."
1825739,2019-06-22 04:17:42 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825739,2019-06-22 04:17:40 UTC,[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]
1825739,2019-04-23 03:17:44 UTC,"Did the problem start recently, or has it always been present?"
1825740,2019-06-13 19:30:00 UTC,This issue was fixed in the openstack/ovsdbapp 0.16.0 release.
1825740,2019-05-31 22:11:53 UTC,"Reviewed:  https://review.opendev.org/654261
Committed: https://git.openstack.org/cgit/openstack/ovsdbapp/commit/?id=9f8dc4494dd5b273a282d21cc15057086624029d
Submitter: Zuul
Branch:    master"
1825740,2019-04-21 19:01:30 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654261"
1825741,2019-11-19 21:51:46 UTC,"(In reply to Bernard Decock from comment #37)

> In my case I'm using Linux Mint 19.2 Cinnamon. I have only this problem as
> soon as I enable the extension LanguageTool and try to insert a formula into
> writer. If I disable LanguageTool, then the problem is gone.
>
> I filed the bug as
> https://bugs.documentfoundation.org/show_bug.cgi?id=128491 which might be a
> duplicate of this bug. Today I managed to duplicate the menu as much as I
> wanted (see attachment)
"
1825741,2019-11-11 15:26:14 UTC,"Created attachment 155708
Double menus in LO ver. 6.3.3.2"
1825741,2019-11-11 15:28:36 UTC,"(In reply to the_cleaner from comment #32)

> Created attachment 155708 [details]
> Double menus in LO ver. 6.3.3.2
"
1825741,2019-11-11 19:24:40 UTC,"Created attachment 155715
Screenshot ot Help screen"
1825741,2019-11-19 16:43:12 UTC,"I can't reproduce this with current master and Unity environment.
Which DE are you using?
Can you try with a recent daily build?"
1825741,2019-11-19 18:42:52 UTC,"Created attachment 155949
Multiple instances of the menubar"
1825741,2019-11-19 18:43:28 UTC,"In my case I'm using Linux Mint 19.2 Cinnamon. I have only this problem as soon as I enable the extension LanguageTool and try to insert a formula into writer. If I disable LanguageTool, then the problem is gone."
1825741,2019-11-20 16:50:06 UTC,"Created attachment 155982
Screenshots - 6.4.0.0-alpha - Ubuntu 19.10 - Unity DE"
1825741,2019-11-22 11:08:41 UTC,"Created attachment 156037
6.4.0.0-alpha - Ubuntu 19.10 - Unity - SC"
1825741,2019-11-20 22:43:03 UTC,"(In reply to Marcus Tomlinson from comment #40)

> I don't have LanguageTool installed.
"
1825741,2019-11-22 11:06:16 UTC,"Description:
In certain situations, more than one global menu is displayed in GTK3 VCL, when used with Unity-style globalmenu - vala-panel-appmenu, or with GTK3 Backend on KDE."
1825741,2019-11-22 11:08:08 UTC,"Created attachment 156036
6.4.0.0-alpha - Ubuntu 19.10 - Unity - About"
1825741,2019-11-11 15:20:41 UTC,"Problem still appears on my system in following LO-components:
- LO manager screen
- LO Base
- LO Math
All other components are OK
I use LO version 6.3.3.2.0, Linux kernel 5.3.10"
1825741,2019-11-22 11:09:03 UTC,"Created attachment 156038
6.4.0.0-alpha - Ubuntu 19.10 - Unity - SC/Writer"
1825741,2019-12-11 12:55:23 UTC,"Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?"
1825741,2019-12-11 13:04:49 UTC,"Removed both ~/.config/libreoffice and ~/.config/libreofficedev directories, and the steps to reproduce are still valid."
1825741,2019-11-20 18:59:09 UTC,I don't have LanguageTool installed.
1825741,2019-11-05 11:43:03 UTC,*** Bug 128491 has been marked as a duplicate of this bug. ***
1825741,2020-01-10 17:15:09 UTC,Looks like a duplicate. Please explain if not.
1825741,2019-10-16 02:11:31 UTC,"This issue affects LibreOffice 6.3.2.2, the most recent version available in the Ubuntu MATE 19.10 Beta."
1825741,2019-08-20 09:29:18 UTC,REOPENED because issue appears again. I don't know why.
1825741,2019-03-28 11:19:02 UTC,"Created attachment 150350
Double menus in GTK3 VCL"
1825741,2019-03-28 11:20:23 UTC,"About attachment - there is just no place for double menu in panel, vala-panel-appmenu made next menu entries scrollable."
1825741,2019-03-28 11:21:42 UTC,"Created attachment 150351
Double menus in GTK3 in English (we see, than all menu entries are doubled)"
1825741,2019-03-29 00:13:29 UTC,"@Caolán, I thought you might be interested in this issue..."
1825741,2019-04-24 10:25:37 UTC,"Hi Jonty, could you please provide some more info about your system such as the version of Ubuntu you're running and which desktop environment(s) you see this issue on."
1825741,2019-04-25 17:09:58 UTC,Yes it still occurs.
1825741,2019-04-25 19:07:46 UTC,Ok thank you for that. I’ve managed to reproduce the issue locally now.
1825741,2019-04-26 12:35:15 UTC,This seems to be an upstream bug. It was resolved in 6.2.2 for some toolkits but not GTK3.
1825741,2019-05-03 22:53:10 UTC,"Created attachment 151169
Screenshot showing duplicate menu"
1825741,2019-05-19 09:17:03 UTC,I have the same problem with Ubuntu 16.04.6 with Unity and LibreOffice Version: 6.2.3.2
1825741,2019-06-10 15:41:16 UTC,"(In reply to Tor Slettnes from comment #5)

> Created attachment 151169 [details]
> Screenshot showing duplicate menu
>
> I see the same in Debian ""sid"", starting with LibreOffice 6.1.  It only
> appears when using the global ""appmenu"" plugin in my Window manager (either
> XFCE4 or MATE), not with Gnome 3 (since the latter does not have a ""global
> app menu"" feature anymore).
"
1825741,2019-07-27 09:29:57 UTC,*** Bug 124192 has been marked as a duplicate of this bug. ***
1825741,2019-07-27 09:31:56 UTC,Same problem for me with 6.2.5.2.
1825741,2019-07-27 09:34:36 UTC,"Set keyword regression because according to the following screenshot from Bug 124192 the bug did not exist in build 6.1.2.
https://bug-attachments.documentfoundation.org/attachment.cgi?id=150089"
1825741,2019-08-13 11:11:43 UTC,"Same issue with me. Global menu duplicated across top for Writer, Calc, Impress.  Running Ubuntu 18.04.03, Libreoffice 6.3.0.4, build ID:Libreoffice-6.3.0.4-snap1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US"
1825741,2019-08-13 12:14:55 UTC,"I imagine the GMenuModel is getting picked up twice, once from the native gtk menubar and once from the explicit dbus export."
1825741,2019-03-28 11:17:28 UTC,"Description:
We have double menus in GTK3 VCL, if it is used with Unity-style globalmenu - vala-panel-appmenu, or with GTK3 Backend on KDE (via https://github.com/KDE/plasma-workspace/tree/master/gmenu-dbusmenu-proxy)"
1825741,2019-08-15 21:44:48 UTC,Works for me with:
1825741,2019-10-25 22:29:14 UTC,"> This issue affects LibreOffice 6.3.2.2
"
1825741,2019-09-13 19:35:42 UTC,"The bug is still there in Libreoffice Build ID: 1:6.3.1~rc2-0ubuntu0.18.04.1~lo1, Running in KDE Neon 5.16.4."
1825741,2019-09-18 11:00:51 UTC,"I confirm this bug is present in version 6.2.6.2 as installed from the Ubuntu LibreOffice 6.2.x PPA.
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-2"
1825741,2019-09-18 10:59:08 UTC,"Created attachment 154256
doubled menus in Ubuntu 18.04 (Unity)"
1825741,2019-10-08 14:26:44 UTC,"Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to ""master"":"
1825741,2019-09-02 04:18:49 UTC,"(In reply to OfficeUser from comment #13)

> REOPENED because issue appears again. I don't know why.
"
1825741,2019-08-23 16:37:29 UTC,"Yes, changing VCL fixes an issue, because Gen is not GTK VCL)"
1825741,2019-08-23 15:46:01 UTC,Setting the environment variable SAL_USE_VCLPLUGIN=gen also disables the GTK menu and fixed the issue for me without uninstalling libreoffice-gtk.
1825741,2019-09-25 19:46:25 UTC,I confirm this bug is still present in LO 6.3.1.2 on Ubuntu 18.04.3 with Unity desktop...
1825741,2019-08-23 15:10:57 UTC,I solved the problem by removing libreoffice-gtk and installing libreoffice-kde. I'm using LibreOffice 6.3 and KDE Neon 5.16.4.
1825741,2019-10-09 03:10:33 UTC,"Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to ""libreoffice-6-3"":"
1825741,2019-10-09 03:10:46 UTC,"Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1825741,2019-10-09 10:24:10 UTC,*** Bug 123484 has been marked as a duplicate of this bug. ***
1825741,2019-10-09 10:26:25 UTC,*** Bug 122287 has been marked as a duplicate of this bug. ***
1825741,2019-10-09 10:28:55 UTC,"Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2-8"":"
1825741,2019-10-14 16:30:25 UTC,*** Bug 128142 has been marked as a duplicate of this bug. ***
1825741,2019-08-20 09:38:28 UTC,Maybe because Gtk2 VCL does not do menu exporting?
1825741,2019-10-07 08:35:00 UTC,Regression caused by https://cgit.freedesktop.org/libreoffice/core/commit/?id=3bedbfd9b3cee5a8d2da6ee0486859bd725979ba (bug 121555)
1825744,2019-08-03 18:23:08 UTC,Last time I somehow missed your second patch. Applied now.
1825744,2019-04-21 19:30:30 UTC,This patch replaces the external file link to locally installed documentation with a link to autopkgtest source on https://salsa.debian.org
1825744,2019-04-21 20:30:19 UTC,I have applied the second patch. Thanks!
1825744,2019-04-22 16:52:48 UTC,"Not sure if it warrants another bug report, so here's yet another patch that basically cleans up after the previous one plus rectifies some other broken links on the same page about autopkgtest."
1825745,2020-10-12 21:58:03 UTC,This is still an issue.
1825745,2020-02-16 04:17:42 UTC,[Expired for AppArmor because there has been no activity for 60 days.]
1825745,2019-04-21 21:01:43 UTC,"For completeness, this is an output of what happens when I disable apparmor
from the system, the same domain is used:"
1825745,2019-12-17 19:53:24 UTC,"This isn't an AppArmor bug, but rather, potentially a libvirt bug. With this error:"
1825747,2019-05-22 09:11:35 UTC,"The lazarus-ide package only contains the IDE, if you do:"
1825753,2019-04-29 00:32:00 UTC,Sounds like this is a kernel bug / change which has caused this - reassigning.
1825753,2019-04-29 20:12:41 UTC,apport information
1825753,2019-05-24 09:28:05 UTC,"So it works on Linux v4.15, but not v4.18 and v5.0?"
1825753,2019-04-29 20:12:54 UTC,apport information
1825753,2019-07-01 05:09:58 UTC,Is there any process hogs the processor?
1825753,2019-04-29 20:12:51 UTC,apport information
1825753,2019-04-29 20:12:48 UTC,apport information
1825753,2019-04-29 20:12:46 UTC,apport information
1825753,2019-04-29 20:12:44 UTC,apport information
1825753,2019-04-29 20:12:42 UTC,apport information
1825753,2019-05-24 12:44:23 UTC,this is correct
1825753,2019-08-31 04:17:18 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825753,2019-04-29 20:12:38 UTC,apport information
1825753,2019-04-29 20:12:36 UTC,apport information
1825753,2019-04-29 20:12:35 UTC,apport information
1825753,2019-04-29 20:12:33 UTC,apport information
1825753,2019-04-29 20:12:31 UTC,apport information
1825753,2019-04-29 20:12:29 UTC,apport information
1825753,2019-04-29 01:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825753,2019-04-22 14:10:48 UTC,Was working file on Ubuntu 18.04.
1825753,2019-04-29 20:12:39 UTC,apport information
1825754,2019-04-21 22:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825754,2019-06-27 02:24:08 UTC,"I had already downgraded and couldn't try the suggested workaround from #15. I've upgraded to disco again and the popping is still there, but the workaround quiets it."
1825754,2019-04-21 22:59:09 UTC,apport information
1825754,2019-04-21 22:58:57 UTC,apport information
1825754,2019-04-21 22:58:59 UTC,apport information
1825754,2019-04-21 22:59:01 UTC,apport information
1825754,2019-04-21 22:59:02 UTC,apport information
1825754,2019-04-21 22:59:04 UTC,apport information
1825754,2019-04-21 22:59:05 UTC,apport information
1825754,2019-04-21 22:59:07 UTC,apport information
1825754,2019-04-21 22:58:54 UTC,apport information
1825754,2019-04-21 22:59:10 UTC,apport information
1825754,2019-04-21 22:59:13 UTC,apport information
1825754,2019-04-21 22:59:15 UTC,apport information
1825754,2019-04-22 03:06:59 UTC,"Please edit the /etc/modprobe.d/alsa-info.conf, add ""options snd-hda-intel power_save=0"", then reboot."
1825754,2019-06-21 04:17:32 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825754,2019-04-21 22:58:55 UTC,apport information
1825755,2019-04-25 06:11:59 UTC,I created an issue in the github from apt-mirror. Don't know whether it is still in maintenance!
1825755,2019-04-21 23:17:06 UTC,"seems that even using more recent apt-mirror perl script doesn't solve the problem, Commands files aren't mirrored.
any idea ?"
1825755,2020-04-28 17:26:33 UTC,I have tested the version of apt-mirror from ppa:slashd/test and can confirm that with the updates Eric added it now works on bionic.
1825755,2019-04-24 03:34:50 UTC,"Might be worth updating the bug title and tags to indicate that this is not Xenial-specific, and also happens to the apt-mirror package in Disco."
1825755,2020-06-01 20:46:25 UTC,"This is quite ridiculous, would it not be possible to apply the fix toe apt-mirror already?"
1825755,2020-04-28 17:56:50 UTC,If other impacted users want to try the test package before moving forward with the SRU:
1825755,2020-04-28 18:00:31 UTC,I would definitely appreciate more feedbacks if possible.
1825755,2020-04-30 20:07:00 UTC,I just left a comment in the apt-mirror upstream bug[0] seeking for volunteers to test.
1825755,2020-05-01 15:35:20 UTC,"Eric, I think we may end up needing this commit as well:"
1825755,2020-05-05 12:19:08 UTC,"Hi,"
1825755,2020-05-05 12:25:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825755,2020-05-19 18:03:56 UTC,"I tested the ppa:slashd/test apt-mirror 0.5.4-1ubuntu0.18.04.1+testpkg20200428b2 package on my Bionic 18.04.4 LTS mirror host, and it successfully got all applicable cnf directories for the 20.04 focal release.  It looks good for me!"
1825755,2019-04-24 03:29:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825755,2020-06-01 21:00:45 UTC,@Eric
1825755,2020-06-03 16:55:07 UTC,"FWIW, I'm having this problem, too, specifically with the icons files, as noted in comment #12, on my mirror running on Ubuntu 18.04. Oddly, some installations using my mirror are fine with this, whereas others complain. Applying the patch linked in comment #12 fixed it for me."
1825755,2020-06-04 00:28:30 UTC,"I had this problem running apt-mirror on bionic, upgrading to the PPA version fixed it"
1825755,2020-06-11 09:00:46 UTC,Had this problem with apt-mirror on Xenial with Focal clients. Using apt-mirror 0.5.4-1ubuntu0.18.04.1+testpkg20200428b2 from ppa:slashd/test solved the problem for me. Thanks for the work on this.
1825755,2020-08-06 10:27:16 UTC,I'm running in this issue too. When will the fix be releases for 18.04? In the PPP there are no packages anymore.
1825755,2020-08-18 16:56:44 UTC,"The Eoan Ermine has reached end of life, so this bug will not be fixed for that release"
1825755,2020-09-29 08:27:14 UTC,"Just ran into this issue on with a Focal host mirroring Focal repositories with Focal clients.  Some searching led me to https://github.com/Stifler6996/apt-mirror which I can confirm works (i.e. fixes cnf, icons, and compression-related problems)."
1825755,2019-04-22 09:53:30 UTC,"tested on a fresh disco server install, apt-mirroring ubuntu disco :
# ll mirror/archive.ubuntu.com/ubuntu/dists/disco/main/
total 24
drwxrwxr-x 6 root root 4096 Apr 22 02:47 ./
drwxrwxr-x 6 root root 4096 Apr 22 02:44 ../
drwxrwxr-x 2 root root 4096 Apr 22 02:44 binary-amd64/
drwxrwxr-x 2 root root 4096 Apr 22 02:47 dep11/
drwxrwxr-x 2 root root 4096 Apr 22 02:45 i18n/
drwxrwxr-x 2 root root 4096 Apr 22 02:44 source/
# find . | grep Commands
-> nothing"
1825756,2020-01-24 09:47:48 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1825758,2019-04-26 16:55:12 UTC,Here the video showing the issue
1825758,2019-04-23 12:09:47 UTC,Thank you for your bug report Could you make a screenshot or video of the issue?
1825758,2019-04-29 14:21:45 UTC,Thanks for the video
1825758,2019-04-29 14:24:16 UTC,Do you do anything special to get the issue? Does it happen every time even on first use after a reboot?
1825758,2019-04-29 15:13:56 UTC,"@Sebastien, Hi! No, nothing. I've just tested rebooting, and launching the gnome-software just after the reboot. The only app that auto-lauches on start before the gnome-software is guake, but I don't think it's related."
1825761,2019-04-22 12:00:15 UTC,"You appear to have a system that had all i386 packages, but then you recently tried to install all amd64 packages, is that correct?  Your dpkg log shows the final entry trying to install systemd:amd64, which then removes systemd:i386."
1825761,2019-04-22 13:49:16 UTC,Yes. Although the truth is that I have already managed to install the 64-bit version of systemd.
1825761,2019-06-22 04:17:25 UTC,[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]
1825762,2019-04-24 14:19:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825766,2019-04-22 00:30:00 UTC,"Another program listed in apt but not in gnome-software:
-phpmyadmin"
1825766,2019-04-22 21:42:14 UTC,You can expect to find an app in GNOME Software if it is a GUI application (== has a .desktop file in /usr/share/applications/ that isn't NoDisplay and of Type=Application). For anything else (that likely includes phpMyAdmin) GNOME Software isn't the right tool and wasn't designed for.
1825766,2019-04-22 20:08:39 UTC,And gnome/gnome-software ended closing that issue because they don't think it is in gnome-software's scope.
1825766,2019-04-22 22:05:45 UTC,"I never liked Ubuntu trying/forcing snaps, but for 19.04 I gave up and tried to embrace it. It is very hard to know when to use gnome-software, when to use apt, when to use snap. Before snaps, I was always able to find every app via apt/aptitude, but now, this is very frustrating."
1825766,2020-05-01 22:36:04 UTC,"Still an issue in Ubuntu 20.04. Following @ximion's explanation, Guake IS a GUI application that should be listed in gnome-software. ""Ubuntu Sofware"", when searching for ""guake"" shows"
1825766,2020-05-02 02:44:58 UTC,"@stuardo:
The reason for Guake being missing is that the `guake.desktop` file in `/usr/share/applications` is a symbolic link *and* the application doesn't ship a metainfo file.
This is forbidden: https://wiki.debian.org/AppStream/Guidelines
The .desktop file being a symlink results in Guake basically not being seen by the metadata generator at all. To fix this, either the .desktop file needs to be an actual file, and not a symlink, or a metainfo file[1] has to be shipped with this package. Ideally both."
1825766,2020-05-07 22:23:29 UTC,@ximion
1825766,2020-05-08 00:10:57 UTC,"On 1): The metainfo/appdata file is only enough if it is complete, so, contains an icon reference and name/summary/etc. tags. If it doesn't, then you'll need the .desktop file as well and a launchable entry."
1825766,2019-04-22 13:42:26 UTC,"Gnome says it's a package issue, not a gnome-software issue."
1825767,2019-04-22 01:30:07 UTC,This change was made by a bot.
1825767,2021-01-07 03:56:38 UTC,Closing this bug as 18.10 and 19.04 has already reached their EOL
1825775,2019-04-22 04:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825775,2019-06-21 04:17:34 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825777,2019-05-20 09:52:40 UTC,"Verified on B-amd64, the test itself has passed, and the final result is passed as well."
1825777,2019-06-04 09:11:38 UTC,This bug was fixed in the package linux - 4.4.0-150.176
1825777,2019-05-16 13:02:47 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1825777,2019-05-16 15:03:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825777,2019-05-17 09:31:52 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1825777,2019-06-09 16:55:00 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1825777,2019-06-04 09:51:54 UTC,Verified on a KVM node / bare-metal with disco
1825777,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1825777,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1825777,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1825777,2019-05-03 02:52:42 UTC,https://github.com/torvalds/linux/commit/30c04d796b693e22405c38e9b78e9a364e4c77e6
1825777,2019-05-31 15:53:08 UTC,"On disco the ubuntu_kernel_selftest.net testcase is failing to compile (bug 1829812), so we are not able to verify it."
1825777,2019-05-22 10:48:45 UTC,"Verified with Cosmic, failing as expected."
1825777,2019-05-21 17:17:47 UTC,Re-triggered a variety of cloud jobs that have failed due to this bug. will verify passed on Cosmic
1825777,2019-05-20 14:02:04 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1825777,2019-05-20 09:42:10 UTC,"Verified on X-amd64, the test itself has passed, and the final result is passed as well."
1825778,2020-01-09 16:09:11 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1825778,2019-04-30 04:29:44 UTC,"This can only be cherry-picked into D, backport is needed for the rest of them."
1825778,2019-12-06 07:09:45 UTC,"Cosmic EOL, removed."
1825778,2019-04-30 03:25:47 UTC,https://github.com/torvalds/linux/commit/8c03557c3f25271e62e39154af66ebdd1b59c9ca
1825778,2019-12-06 07:08:16 UTC,"For Disco, it's fixed with Disco update: 5.0.17 upstream stable release."
1825778,2019-12-06 12:08:45 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-December/106195.html
1825778,2020-02-03 23:12:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825778,2020-01-27 12:13:59 UTC,This bug was fixed in the package linux - 4.4.0-173.203
1825778,2020-02-17 10:36:02 UTC,This bug was fixed in the package linux - 4.15.0-88.88
1825780,2019-05-16 13:02:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1825780,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1825780,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1825780,2019-06-04 09:11:38 UTC,This bug was fixed in the package linux - 4.4.0-150.176
1825780,2019-05-23 03:54:35 UTC,Passed with Cosmic i386 with proposed kernel.
1825780,2019-05-20 14:01:52 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1825780,2019-05-20 10:01:15 UTC,Test passed with Bionic i386.
1825780,2019-05-16 15:03:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825780,2019-04-23 11:00:45 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-April/100297.html
1825780,2019-04-23 06:47:49 UTC,"BTW,
this patch belongs to a patchset [1], in which further limiting kprobe-events probing on notrace function"
1825780,2019-04-22 10:26:46 UTC,"This issue can be fixed by patch:
https://github.com/torvalds/linux/commit/6fc7c4110cbaff85b1f49fd70b77950384c3a201"
1825780,2019-04-22 05:10:14 UTC,"Not sure about Disco, it seem that this test suite was not successfully tested on it."
1825780,2019-04-22 05:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825781,2019-04-22 05:30:05 UTC,This change was made by a bot.
1825783,2019-04-23 12:42:01 UTC,Thanks!
1825783,2019-04-23 12:26:41 UTC,Filed: https://gitlab.gnome.org/GNOME/nautilus/issues/1006
1825783,2019-04-23 09:12:23 UTC,"Thank you for your bug report, that seems indeed an issue, could you also report it upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ ?"
1825784,2019-04-22 05:52:07 UTC,This is a recent requirement from ironic and has been backported to queens:
1825784,2019-04-29 14:11:21 UTC,"Reviewed:  https://review.opendev.org/655690
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0cb2d2e34210416ecdbdb305e3452b236fb84c7e
Submitter: Zuul
Branch:    stable/rocky"
1825784,2019-04-24 09:35:53 UTC,"Thanks for raising this Tony. It appears that RDO includes the dependency: https://cbs.centos.org/koji/rpminfo?rpmID=160048, so this will just apply for source centos/rhel images and all debian/ubuntu images."
1825784,2019-04-24 09:58:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655369"
1825784,2019-04-25 12:39:47 UTC,"Reviewed:  https://review.opendev.org/655369
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=856b2c8824967e582c3d2e98851b58efab6757f8
Submitter: Zuul
Branch:    master"
1825784,2019-04-25 13:19:13 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/655688"
1825784,2019-11-06 01:14:52 UTC,This issue was fixed in the openstack/kolla 9.0.0.0rc1 release candidate.
1825784,2019-04-29 14:09:55 UTC,"Reviewed:  https://review.opendev.org/655691
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=8dbb962494750fe9c164113616e4864d9d84ac3e
Submitter: Zuul
Branch:    stable/queens"
1825784,2019-07-18 00:38:23 UTC,This issue was fixed in the openstack/kolla 8.0.0.0rc2 release candidate.
1825784,2019-04-29 14:18:07 UTC,"Reviewed:  https://review.opendev.org/655688
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=3e9b4406a499f395975992e016d03d60a6c61037
Submitter: Zuul
Branch:    stable/stein"
1825784,2019-06-14 01:14:53 UTC,This issue was fixed in the openstack/kolla 6.2.2 release.
1825784,2019-06-14 01:15:09 UTC,This issue was fixed in the openstack/kolla 7.0.3 release.
1825785,2019-10-30 08:45:19 UTC,I think I have the same bug.
1825785,2019-10-18 14:42:47 UTC,"I have same the issue on Debian after I upgrade to Debian buster. In my experience, it looks like related to Linux kernel. This bug can't reproduce on Linux 4.9:"
1825785,2019-06-24 01:20:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825790,2019-04-24 11:32:49 UTC,"Hi Richard,"
1825791,2019-06-22 04:17:19 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1825791,2019-04-22 07:49:05 UTC,CvPcb (assign footprints tool) is not the only option to assign footprints meaning there are other options that you can use as a workaround. I documented all of them in: https://forum.kicad.info/t/how-can-i-assign-a-footprint-to-a-symbol/8901
1825791,2019-04-22 08:39:43 UTC,"Hi Rene,"
1825793,2019-04-22 12:31:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1825793,2019-04-27 05:04:42 UTC,"i can not move the screen back to primary monitor even using KDE daemon short cut for switching display (Meta+P).
the buy doesn't affect particular package. it affects multiple packages."
1825808,2019-04-22 13:32:50 UTC,"I also opened this board (Linux. V5.1.0), and see no problem.
I also saved the board and uploaded it back to the kicad user forum."
1825808,2019-04-22 10:36:04 UTC,"5.1.1 does indeed use a different strategy for this.  Still, I can’t explain why 5.1.0 is doing it either, so I’m not quite sure this is “Fix Committed”."
1825808,2019-04-22 10:16:27 UTC,"Ehh, tested on 5.1.1"
1825808,2019-04-22 10:16:17 UTC,I just tested this on linux and I don't see the message dialog.
1825809,2019-04-22 13:49:17 UTC,"Ryan, here is the bundle: https://pastebin.canonical.com/p/DD4YhgDTpX/"
1825809,2019-04-22 13:40:33 UTC,"In pretty much all charm bug cases, an example bundle is the first thing I reference.  Can you please post a sanitized example bundle (reproducer)?"
1825812,2019-05-07 12:35:58 UTC,"Regarding the optimal behaviour u-u spends significant amount of CPU time on deciding which are the upgradable packages especially if there are held packages thus there is a tradeoff between network and CPU usage.
I believe both of the options have their benefits, and on a desktop system -updates are more likely to be installed quickly after downloading them thus software-properties seems to be doing the right thing by requesting all packages to be downloaded."
1825812,2019-05-07 12:25:27 UTC,Unattended-upgrades in not affected by this bug because it downloads only packages it would install and the configuration files it ships are set to only do that.
1825812,2019-04-22 20:37:58 UTC,"Hmm well it was not what I intended, otherwise I'd not have bothered with the u-u option. But um, worth weighing the options."
1825812,2019-04-22 20:27:33 UTC,"I somehow thought that this was intentional behavior, that we would download all of the packages so that they would be available to apply quickly, even if we would only automatically install the security updates."
1825812,2019-04-22 11:02:48 UTC,This is caused by these options:
1825816,2019-04-22 16:45:21 UTC,"It is OK to restart Mixxx after tweaking the preferences option.
It is better than fiddling with a batch file."
1825816,2019-04-22 15:42:08 UTC,"If we can change Qt's scale factor from the preferences, okay, but not elaborate hacks duplicating what Qt already does for us (like https://github.com/mixxxdj/mixxx/pull/1741). However I am doubtful we can adjust Qt's scale factor within a Qt application. IIRC it needs to be set before any GUI is shown."
1825816,2019-04-22 15:29:29 UTC,"why ""won't fix""?"
1825816,2019-04-22 15:26:14 UTC,It is not only Qt's responsibility since we decided to explicitly opt-in into auto-scaling with unforeseeable side effects. Now one has to set QT_AUTO_SCREEN_SCALE_FACTOR=0 to restore the default behavior in order to follow the instructions documented by Qt.
1825816,2019-04-22 15:00:10 UTC,"Once again, this is Qt's responsibility, not the responsibility of every application. We only need to inform users how to manually adjust scaling when Qt's automatic scaling fails, which it inevitably will in some cases with the wide variety of resolutions and physical screen sizes available."
1825816,2019-04-22 13:06:57 UTC,"```
export QT_AUTO_SCREEN_SCALE_FACTOR=0
export QT_SCREEN_SCALE_FACTORS=1.4
```
works for me."
1825816,2019-04-22 10:36:03 UTC,This is an other aspect of https://bugs.launchpad.net/mixxx/+bug/1793954
1825817,2019-05-03 15:40:25 UTC,"The problem is with GLib.markup_escape_text, because spanish fail too"
1825817,2019-04-27 09:39:43 UTC,same problem here (german system language)
1825817,2019-04-22 11:48:24 UTC,"OK, i just changed my system language from German to English and now its starting again"
1825817,2019-05-16 21:19:30 UTC,"Simple fix:
sudo sed -i ""/GLib.markup_escape_text(text, len(text))/s/len(text)/len(text.encode('utf-8'))/"" /usr/lib/python3*/*-packages/menulibre/util.py"
1825817,2019-05-03 15:41:07 UTC,"run as workaround:
env LANG=C menulibre"
1825819,2019-04-23 13:56:11 UTC,"Thanks for the output, that really helped. Your problem is that you don't have the tls_client.certs.saved flag. I noticed that the latest easyrsa charm is revision 231 and you have revision 192. I believe there was an interface change in that between those, which could result in the error you are seeing. Please upgrade easyrsa and let us know if the problem persists."
1825819,2019-08-02 12:39:34 UTC,Created PR for Kubernetes master to address RBAC concerns: https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/42
1825819,2019-04-22 11:04:51 UTC,"change
remove_state('kubernetes-master.components.started')
to
set_state('..')
fix this issue. but not sure this is proper way to do it."
1825819,2019-04-22 12:58:15 UTC,"> 1. install_snaps() delete kubernetes-master.components.started flag
"
1825819,2019-04-22 23:17:19 UTC,yeah I think start_master wasn't run.
1825819,2019-04-25 05:51:21 UTC,Upgrading caused the other issue
1825819,2019-04-25 18:24:56 UTC,"I'm not convinced that upgrading caused it.  It could have been coincidental, as 5 days prior to the observations in that ticket, a kubernetes-master upgrade was done.  It's quite possible that the problem described in that bug was actually due to the kubernetes-master upgrade rather than the easyrsa upgrade."
1825819,2019-07-12 14:07:06 UTC,"Having looked into this in more detial, the problem seems to be caused by the other version of easy rsa calling set_client_cert[1]."
1825819,2019-07-12 16:04:55 UTC,Opened Draft PR: https://github.com/juju-solutions/layer-tls-client/pull/18
1825819,2019-07-18 15:40:03 UTC,PR Ready for review: https://github.com/juju-solutions/layer-tls-client/pull/18
1825819,2019-08-15 17:36:03 UTC,"FWIW: if you are caught with this during an upgrade, upgrading the easyrsa charm will resolve the issue.  Once the easyrsa charm finishes updating, the kubernetes-master will see it and it will get unstuck."
1825821,2019-04-23 06:10:40 UTC,apport information
1825821,2019-04-23 06:10:39 UTC,apport information
1825821,2019-04-23 06:10:37 UTC,apport information
1825821,2019-04-23 06:10:36 UTC,apport information
1825821,2019-04-23 06:10:45 UTC,apport information
1825821,2019-04-23 06:10:31 UTC,apport information
1825821,2019-04-23 03:43:27 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1825821,2019-04-23 06:10:42 UTC,apport information
1825821,2019-04-23 06:10:34 UTC,apport information
1825821,2019-04-23 06:10:43 UTC,apport information
1825821,2019-04-23 06:10:32 UTC,apport information
1825821,2019-04-23 06:10:47 UTC,apport information
1825821,2019-04-23 06:10:48 UTC,apport information
1825821,2019-04-23 08:20:07 UTC,Thanks.
1825821,2019-04-23 08:44:53 UTC,"Hi Daniel,"
1825821,2019-04-23 09:02:39 UTC,"In that case it sounds like the 2.4GHz band is being drowned out by other local signals, either from other Bluetooth devices or from a 2.4GHz wifi network."
1825821,2019-04-23 09:47:31 UTC,I will try out your points.
1825821,2019-04-23 10:09:12 UTC,In my experience those error messages should be ignored. They are never related to connectivity problems.
1825824,2020-08-05 12:19:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825826,2019-05-16 08:02:30 UTC,I came here thinking i could close this as I'd seen some green runs for the standalone-upgrade on master. However looking at the top two fails in [1] at time of writing i found [2] and [3] which have the same signature but for different services - so this is likely no keystone specific:
1825826,2019-05-09 11:32:59 UTC,"Change abandoned by Marios Andreou (<email address hidden>) on branch: master
Review: https://review.opendev.org/654952"
1825826,2019-05-16 08:03:20 UTC,lowered to High from Critical and  removed alert tag please re-add if you disagree
1825826,2019-04-23 10:58:13 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/654952"
1825828,2019-04-23 10:00:13 UTC,This change was made by a bot.
1825828,2019-04-23 09:17:28 UTC,I have installed and boot into kernel v4.18 and the issue is not present.
1825828,2019-04-23 07:44:00 UTC,"OK, that's a different OS release though."
1825828,2019-04-23 03:33:03 UTC,Are you able to identify the last known kernel version where the problem did NOT occur?
1825828,2019-04-23 06:20:04 UTC,"Display was working fine in Ubuntu 18.04(LTS), Kernel - v4.15."
1825832,2019-09-29 07:48:26 UTC,Also seen on AskUbuntu - https://askubuntu.com/q/1177372/66509
1825832,2019-04-22 16:23:06 UTC,"The attachment ""patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1825832,2019-09-29 07:34:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825832,2019-09-29 07:36:30 UTC,"All current Ubuntu version are affected. So the package has wrong dependencies or ""import"" lines inside (see patch above)."
1825834,2019-06-26 06:34:41 UTC,The issue did not reproduce. Moving to incomplete.
1825834,2019-06-25 13:25:19 UTC,The glance[gl1.log]
1825834,2019-06-25 13:24:51 UTC,"I have checked behavior when the http connection is interrupted in the next environment:
MOS 9.2
glance API v1
packages:
swift - 2.7.1-4~u14.04+mos2
python-swiftclient - 1:3.0.0-2~u14.04+mos1
glance-api - 2:12.0.0-5~u14.04+mos26
python-glance-store - 0.13.1-1~u14.04+mos9
python-glanceclient - 1:2.0.1-3~u14.04+mos2"
1825834,2019-06-19 21:16:37 UTC,"Http is deprecated. And when the http connection is interrupted, swift-proxy-server writes the below error –"
1825834,2019-06-25 13:31:26 UTC,The swift[sw1.log]
1825835,2019-04-30 03:40:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825835,2019-04-22 16:23:34 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1825841,2019-04-22 17:04:03 UTC,What kernel version have this issue and what kernel version don't have?
1825841,2019-04-22 14:00:08 UTC,This change was made by a bot.
1825842,2020-02-24 02:07:59 UTC,"Yes, Gnome 3.36 will be in Ubuntu 20.04 before April."
1825842,2019-12-27 12:40:11 UTC,"Hello, I have this problem on my Ubuntu VMs (since 19.04). However, my Debian 10 VMs are not affected. I hope this bug will be fixed before the LTS. This graphics bug makes my VMs unusable.
Thank you."
1825842,2019-05-05 22:45:36 UTC,Same happening here in both Ubuntu 19.04 and Pop_OS! 19.04
1825842,2019-05-17 07:10:53 UTC,"I've noticed that if you enable fractional scaling, 125% is still ok, but beyond that the wallpaper turns white."
1825842,2019-05-17 07:11:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825842,2019-11-06 18:43:33 UTC,Issue is still in Ubuntu 19.10 with vmware workstation player 15.5.
1825842,2019-11-19 18:23:28 UTC,"Since Ubuntu 19.04, I can not use Ubuntu on my VMware virtual machines on my MacBook Pro Retina (200% scaling). The desktop is white. This still occurs under Ubuntu 19.10 (even with a clean install).
I hope this problem will be resolved quickly. I want to migrate to a newer version than my current version (Cosmic Cuttlefish)."
1825842,2019-11-21 23:10:55 UTC,Running Manjaro 18.1.0 x86 (GNOME) on VMWare Workstation 15.5 - can confirm that I have the same issue.
1825842,2019-11-23 09:04:04 UTC,I also have this problem on Ubuntu 19.10.
1825842,2019-12-09 18:10:00 UTC,Same problem with Ubuntu 19.10 running in VMware Workstation 15.5.1
1825842,2020-03-02 11:21:17 UTC,This bug was fixed in the package mutter - 3.35.91-1ubuntu1
1825842,2020-01-07 08:22:13 UTC,Same issue. Ubuntu Budgie 19.10.
1825842,2020-01-13 23:18:35 UTC,Same issue - 19.10 running on VMWare
1825842,2020-01-15 01:55:08 UTC,"Oh, actually, I think I stumbled on an explanation for this bug and have a potential fix:"
1825842,2020-02-05 02:53:26 UTC,I am assuming this was fixed by: https://gitlab.gnome.org/GNOME/mutter/merge_requests/1004
1825842,2020-02-06 16:41:54 UTC,I can confirm I have the same issue with 19.10 - fresh install.
1825842,2020-02-09 13:53:22 UTC,I can confirmed having the same issue with 20.04 fresh installed as guest on virtual box
1825842,2020-02-10 01:50:02 UTC,The (potential) fix mentioned in comment #15 is coming in Gnome 3.36.
1825842,2020-02-22 19:37:16 UTC,"The fix will also be coming with Ubuntu 20.04, is that right?"
1825843,2019-04-22 13:56:18 UTC,Subscribed field-high as this is an operational concern for go-live.
1825843,2019-04-22 17:48:51 UTC,Please add log files (pastebins are ephemeral and will vanish).
1825843,2019-04-22 14:05:03 UTC,This appears most definitely to be an upstream packaging issue than an issue with the charm itself.
1825843,2019-05-01 14:47:30 UTC,"Reviewed:  https://review.opendev.org/655913
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-radosgw/commit/?id=e034d5e18681fc2952093afe20a78d202ed5be62
Submitter: Zuul
Branch:    stable/19.04"
1825843,2019-04-22 19:03:34 UTC,I can verify that this happens with the minimal bionic-rocky bundle found in the ceph-radosgw charm's tests.
1825843,2019-04-22 19:28:36 UTC,"Workaround to get temporary fix into radosgw init script.  note, this will potentially restart all your rgw units at once, you may want to run one unit at a time."
1825843,2019-05-02 22:14:32 UTC,"Currently trying to get charm ceph-radosgw  rev 268, Ubuntu Bionic, OpenStack Stein (base bundle like)"
1825843,2019-04-22 23:51:35 UTC,"After further reading of code and testing, I think that I am completely wrong about what is or is not broken. radosgw is inactive, but that's deliberate. The charm has created a new service called ""ceph-radosgw@rgw..."", along with a service to keep track of it called ceph-radosgw.target. Those seem to be running just fine."
1825843,2019-04-23 00:50:28 UTC,"We upgraded the charms and radosgw got broken, ceph-radosgw release 267."
1825843,2019-04-23 08:53:28 UTC,"The switch from the init.d radosgw script to actual systemd units was intentional and was part of a tech debt payoff to support the implementation of RGW mirroring, which requires that all daemons have specific keys."
1825843,2019-04-23 08:55:03 UTC,The nrpe check code is using the new code paths for generating the service unit names in the new style.
1825843,2019-04-23 08:59:38 UTC,@angelvargas
1825843,2019-04-23 10:05:03 UTC,@james-page
1825843,2019-04-23 14:41:29 UTC,"After IRC conversations and more testing, I think that I have a clean reproduction of this bug, along with a root cause."
1825843,2019-04-24 13:43:12 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655434"
1825843,2019-04-24 21:57:18 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655574"
1825843,2019-04-24 21:59:45 UTC,"Change abandoned by Pete Vander Giessen (<email address hidden>) on branch: master
Review: https://review.opendev.org/655574
Reason: Accidentally created extra review due to bad squash."
1825843,2019-04-25 19:40:55 UTC,"Reviewed:  https://review.opendev.org/655434
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-radosgw/commit/?id=ff90c0f058073292739bab33309d700d9bcfc4c6
Submitter: Zuul
Branch:    master"
1825843,2019-04-26 13:07:54 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/655900"
1825843,2019-04-26 14:04:52 UTC,"Change abandoned by Pete Vander Giessen (<email address hidden>) on branch: stable/19.04
Review: https://review.opendev.org/655900
Reason: Cherry picked the wrong change!"
1825843,2019-04-22 17:51:29 UTC,Non-reproducing reproducer attempt attached.
1825843,2019-04-26 14:05:02 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/655913"
1825847,2019-04-22 18:43:14 UTC,"whoopsie..
result of <Style> and <BackPath> mix to style the small decks, color scheme color shift not applied to inline style attributes."
1825847,2019-04-22 18:54:22 UTC,https://github.com/mixxxdj/mixxx/pull/2085
1825848,2019-04-22 14:11:22 UTC,Currently there are no plans to support windows 2019. But will keep this as a feature request.
1825849,2020-09-14 07:40:52 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1825850,2019-07-26 14:06:23 UTC,Fixed in a different way.
1825850,2019-05-09 19:13:01 UTC,After talking to Jonathan via IRC I think the best course of action is:
1825850,2019-05-09 15:39:17 UTC,"Also note, those are all very common server ethernet devices, and manifest is detecting none of them."
1825850,2019-05-09 15:38:40 UTC,"But that's on me... perhaps that's a project my team can dig into later.  For now, we just need to figure out why the manifest job isn't setting things properly."
1825850,2019-05-09 12:56:57 UTC,"Also, when we had that discussion, I misunderstood you.  I believed you were going to do something like combine those two jobs so that there's a single, automated job to provide that data."
1825850,2019-05-09 12:55:55 UTC,"Right, but that's simply not what's happening here.  For whatever reason, it's not setting has_ethernet_adapter to true, even when an ethernet adapter exists.  Looking back at the examples I provided:"
1825850,2019-05-09 09:17:42 UTC,"I made the changes to the ethernet/detect job to make it work more like our other ""detect"" jobs. See the MR:"
1825850,2019-05-08 14:05:27 UTC,"This is not just on new servers; it also happens on kies (https://certification.canonical.com/hardware/201606-22356/), a Supermicro SYS-6018U-TR4+, when running 19.04 regression tests. The same system produced reasonable results when running 18.04.2 regression tests in February."
1825850,2019-05-09 19:13:47 UTC,also discovered that the info and detect arguments to network_device_info result in identical output :/ so I'll clean that up too.
1825850,2019-05-07 23:07:07 UTC,"from the job we discovered this on:
plugin: shell
category_id: com.canonical.plainbox::ethernet
id: ethernet/detect
flags: also-after-suspend
command: network_device_info.py detect
estimated_duration: 2.0
_summary:
 Detect if at least one ethernet device is detected
_description:
 Test to detect and return information about available network controllers on
 the system under test.
imports: from com.canonical.plainbox import manifest
requires: manifest.has_ethernet_adapter == 'True'"
1825850,2019-05-07 23:02:51 UTC,"Ok, root cause is this new/strange ""manifest"" job.  The errors are all around ""manifiest.has"" requirements which are failing. here is some info from a xenial system running tools from stable and from dev.  Note, the dev version runs this manifest job that returns nothing for has_ethernet_adapter.  And because of that, certain jobs simply fail to run because of the unmet dependency.  The stable tree, for now, does not have this manifest thing."
1825850,2019-04-26 16:08:50 UTC,"This also fails on s390x:
https://certification.canonical.com/hardware/201604-21858/submission/141444/test-results/skipped/
ethernet/detect	test	skip	job cannot be started: resource expression ""manifest.has_ethernet_adapter == 'True'"" evaluates to false
ethernet/info_automated	test	skip	job cannot be started: resource expression ""device.category == 'NETWORK'"" evaluates to false"
1825850,2019-04-22 16:28:15 UTC,"another system showing this failure on 18.04 but success on 16.04, so there's two sets of output we can examine:"
1825850,2019-04-22 14:50:24 UTC,https://certification.canonical.com/hardware/201904-26980/submission/140920/test-results/
1825850,2019-05-08 20:21:39 UTC,Adding checkbox-ng as this is because of the plainbox-manifest-* scripts buried in the checkbox-ng source.
1825850,2019-05-09 21:52:00 UTC,new output from network_device_info.py:
1825851,2019-05-23 21:06:14 UTC,"I have a qualm about the proposed migration path, particularly the bit about admins removing files from staff/share/print_templates."
1825851,2019-04-22 18:29:46 UTC,Cleaned up branch pushed:
1825851,2019-05-24 15:15:55 UTC,"All good suggestions.  Thanks, Galen.  Looking into these now."
1825851,2019-05-24 16:48:34 UTC,Force-pushed back to same branch implementing Galen's suggestions.
1825851,2019-07-12 21:46:02 UTC,Updated branch pushed with loads of changes:
1825851,2019-08-01 15:57:07 UTC,"I've made the changes to eg_vhost and eg_startup, and installed the Perl dependency, as noted in the release notes, and noticed a few things while testing this."
1825851,2019-08-01 18:02:32 UTC,"Thanks, Kyle!  Rebasing to master and looking at some of these issues..."
1825851,2019-08-01 20:47:28 UTC,Rebased continuation branch pushed:
1825851,2019-08-02 14:47:18 UTC,"Thanks Bill, that resolves the issues I noted. I did notice one new thing - it's possible to hit save when the owner field is empty, which closes the modal and leaves an error in the console that the print template failed to create. Failing to be created is expected, but we may want to have the owner field be required, in the same way that Name and Label are, graying out the Save button if unselected"
1825851,2019-04-22 18:40:40 UTC,"The branch also includes a sample configuration using HTML::Restrict to scrub HTML content for security.  The code is commented out, though, since it requires a new cpan-installed Perl module.  I wasn't quite ready to make that a requirement for testing and/or whether we wanted to consider other alternatives."
1825851,2019-08-02 15:40:31 UTC,"Thanks, Kyle.  I confirmed the 'owner' field is marked as required in the IDL, so this is more of an FMEditor / OrgSelect bug.  I'll open a new LP for that."
1825851,2019-08-02 15:51:33 UTC,Opened bug #1838784 for the org-select / fieldmapper editor form validation issue.
1825851,2019-08-28 21:37:59 UTC,"Pushed to master for inclusion in 3.4. Thanks, Bill and Kyle!"
1825851,2019-08-02 15:48:48 UTC,"With that in mind, I have tested this code and consent to signing off on it with my name, Kyle Huckins, and my email address, <email address hidden>."
1825853,2019-04-22 15:31:22 UTC,Please write the bug description in the bug description and not only in the title.
1825853,2019-04-22 19:54:06 UTC,"Ha, that's kind of groovy. Sometimes the text springs back to where its supposed to be, but sometimes it stays where its wandered off too (e.g. if group select, Cmd-C and Cmd-V)."
1825853,2019-04-22 20:19:29 UTC,"Yeah, I actually knew about this before I checked it in, but it just looked too cool.  Try dragging a whole bunch of stuff in a big schematic..."
1825853,2019-04-22 20:20:10 UTC,(I lowered the priority as it does actually move everything correctly; it just the display while moving that wonky.)
1825853,2019-04-23 18:29:47 UTC,"I confirm that fix works
https://bugs.launchpad.net/kicad/+bug/1826023
https://code.launchpad.net/~andrei-pozolotin/kicad/+git/kicad/+merge/366082"
1825853,2019-04-23 19:01:00 UTC,"@Andrei, thanks for following up."
1825854,2019-04-30 04:09:00 UTC,"""no addresses observed"" seems like it would be because those interfaces are
already bridged, and thus the IP address would be on the bridge and not the
device."
1825854,2019-10-28 04:17:26 UTC,[Expired for juju because there has been no activity for 60 days.]
1825854,2019-04-25 14:04:20 UTC,"hm, if this is an OIL run, then it is less likely that the issue is a mismatch between Juju's idea of what spaces are and what MAAS thinks spaces are."
1825854,2019-04-29 09:27:58 UTC,It appears there is some issue updating the provider addresses in state.
1825854,2019-04-29 09:38:18 UTC,"2019-04-20 12:49:44 INFO juju.network bridge.go:118 bridger returned nothing
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""eth0""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""eno2""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""eno3""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""eno4""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""eno49""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""eth6""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""eth7""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""bond0.2736""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""bond0.2735""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""eth1.2733""
2019-04-20 12:49:44 INFO juju.api.common network.go:140 no addresses observed on interface ""virbr0-nic""
2019-04-20 12:49:46 WARNING juju.provisioner provisioner_task.go:1350 failed to start machine 16/lxd/0 (unable to find host brid
ge for space(s) ""ceph-replica-space"" for container ""16/lxd/0""), retrying in 10s (10 more attempts)"
1825854,2019-04-30 05:21:33 UTC,"Yes, ""no addresses observed"" is a red herring here."
1825854,2019-05-02 14:32:42 UTC,I've marked this one incomplete for the moment.
1825854,2019-05-02 14:50:47 UTC,"Hi Joseph,"
1825854,2019-05-06 15:21:48 UTC,"The crashdumps had some logging at debug level, but the machine agent logs were at info."
1825854,2019-08-28 21:25:55 UTC,Marking incomplete looking for the additional details that Joe asked for while trying to chase this down.
1825855,2019-04-24 15:28:11 UTC,Looks like the intended fix (0445a9913) didn't work.
1825855,2019-04-24 13:00:35 UTC,Still seems to be present as of the below build:
1825855,2019-04-30 14:34:31 UTC,"Fixed in revision 6536b4766c767a8be248928d39ab6008e8cafd67
https://git.launchpad.net/kicad/patch/?id=6536b4766c767a8be248928d39ab6008e8cafd67"
1825855,2019-04-24 12:07:35 UTC,Please can you add full version information from About KiCad -> Copy Version Info.
1825856,2019-05-01 13:51:44 UTC,What's the actual impact please? What you've written describes the problem but I don't understand how this is a problem for users from that description.
1825856,2019-05-01 14:19:33 UTC,description updated to explain the problem.
1825856,2019-06-14 21:59:33 UTC,"An upload of gnupg to xenial-proposed has been rejected from the upload queue for the following reason: ""fixing tests only does not fit the SRU policy""."
1825858,2019-07-03 15:20:26 UTC,Fix proposed at https://github.com/snapcore/snapcraft/pull/2620
1825858,2019-04-23 15:18:00 UTC,I found this workaround that allows not doing a full rebuild:
1825858,2019-06-04 18:34:24 UTC,A potential fix is to add --force to the cargo arguments.
1825860,2019-04-23 07:37:08 UTC,"This behavior is common on the OpenStack Charms, too. The expectation is that removing this charm would remove the machine (container?) where it is running."
1825860,2019-04-23 07:58:42 UTC,"For a comparison, while developing the hw-health-charm I tried to make all actions reversible: install/uninstall tools, add/remove nrpe checks. But yeah, I can see how the assumption is that 1 charm == 1 instance, so removing the charm equals throwing away everything, so we don't necessarily have to care."
1825860,2019-07-04 12:50:47 UTC,"Hello Andrea. I have tested this by running the following:
juju deploy cs:openstack-service-checks
juju add-relation openstack-service-checks nrpe
juju add-relation openstack-service-checks keystone
# assumption is that nrpe<->nagios:monitors relation already exists, as well as a running OS env"
1825860,2020-02-14 23:05:33 UTC,"Using charm rev 30, I removed a unit and it did remove the checks."
1825861,2019-04-22 17:27:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825861,2019-04-22 22:01:09 UTC,From VarLogDistupgradeApttermlog.txt:
1825863,2019-10-03 07:43:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825863,2020-04-17 08:29:22 UTC,I also encountered this problem and did some digging. I believe it is caused by this: https://github.com/umlaeute/v4l2loopback/issues/172
1825863,2019-10-03 07:43:15 UTC,"Hello, did you succeeded with some solution?"
1825864,2019-04-23 03:27:34 UTC,Could you please attach a screenshot or photo of the problem?
1825864,2019-04-23 17:09:28 UTC,"Today this issue did not occur at all. But yesterday when i restarted my laptop several times, some 'Desktop Guide' load URL error is thrown and the guide dialog popped up. This did not allow me to open other applications. Is any log file, i need to look into to attach here?"
1825864,2019-04-24 02:03:21 UTC,No problem. Please just wait until the bug occurs again and then take a screenshot by pressing PrtScn. That will create an image in your Pictures folder.
1825864,2020-06-20 13:04:34 UTC,"I have faced same issue where in Ubuntu desktop guide pops of continously for certain duration. Even if we close it, it pops up again. Attaching the logs for more details"
1825864,2019-06-23 04:19:24 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1825864,2020-06-22 01:45:19 UTC,"Aside from anything else, this bug was reported against 18.10 which has reached end of life. So we need a new bug report from a supported version of Ubuntu."
1825864,2020-06-20 13:23:20 UTC,"This issue i am seeing from Ubuntu v18 till upgrade to Ubuntu v20. Have HP Laptop with AMD processor, configuration similar too the one mentioned by @Rajkumar"
1825864,2020-06-22 01:44:14 UTC,Please don't reopen bugs reported by other people. Please open a new bug instead.
1825865,2019-04-23 08:03:12 UTC,Which particular hashes are you referring to?  Launchpad has many components.
1825865,2019-06-23 04:18:05 UTC,[Expired for Launchpad itself because there has been no activity for 60 days.]
1825866,2019-04-23 07:47:06 UTC,"Issue is that the keystone credentials are requested as soon as the ""identity-credentials.available"" relation is available, and data is stored in unitdata sqlite db (""keystonecreds"" key)."
1825866,2019-04-23 13:09:20 UTC,Related to bug 1825951 (charm-interface-keystone-credentials)
1825867,2019-04-24 16:53:57 UTC,"py3 testcase fails coz of the change set proposed.
Considering a scenario for keystone.tests.unit.identity.backends.test_sql.TestIdentityDriver.test_authenticate_for_user_with_special_char with user_id='fl\xc3\xbcgel' (which actually is flügel, fl\xc3\xbcgel is the string representation in py2.)
In py3, as string/text means both ascii/unicode, fl\xc3\xbcgel as a user_id will mean flügel not mean flügel."
1825867,2019-09-27 07:25:53 UTC,"I'm hitting a similar problem in Keystone rocky, but in a different function. The ldap_filter attribute is an <str>. Casting this attribute to <unicode> fixes the problem (see the attached test patch)."
1825867,2019-09-17 14:56:06 UTC,The patch to fix this has not had any updates and the failing tests make it seem inconclusive as to whether this is actually a problem. Marking this as incomplete in order to wait for confirmation from another user or more evidence from the reporter or an update to the proposed bugfix.
1825867,2019-04-26 15:16:29 UTC,"I the queens release, we used to get unicode output from the database for ldap (keystone/identity/mapping_backends/sql.py:get_id_mapping()). In stein, we are getting string values. Need to check if this change was introduced to support py3 as it uses text/string."
1825867,2019-04-22 18:31:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654601"
1825867,2019-04-24 16:56:07 UTC,One more solution to this bug can be that we make sure only unicode values reach the point of failure rather than string value. In my investigation I found that these string values are got after we fetch values from database.
1825868,2019-04-25 13:44:28 UTC,Hi! Thanks for reporting this issue.
1825868,2020-08-11 23:44:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825868,2020-08-11 23:45:02 UTC,"hello
I have the same bug with ubuntu 20.04."
1825868,2019-04-25 19:38:21 UTC,"Sorry, I changed to public. Using Topicons Redux fixes this issue, but I don't call that a solution."
1825870,2019-05-18 09:15:14 UTC,"can you detail that:
""if I manually enter the transaction in the program, the program allows me to enter the transaction even beyond the expiration date"""
1825870,2019-05-10 18:11:03 UTC,"you mean for a debit/credit card ?
I don't see the point: usually you receive the new one before an in any case you cannot pay if the expiration date is in the past"
1825870,2019-05-10 19:30:47 UTC,"Yes, I mean a debit or credit card.
Yes, usually I receive the new one before.
If I go to the store I can't pay if the expiry date is in the past. if I manually enter the transaction in the program, the program allows me to enter the transaction even beyond the expiration date. I would not mistake the manual registration of a transaction by inserting an expired credit or debit card. I would like the program to remind me that that card cannot be used because it has expired."
1825870,2019-05-10 19:32:58 UTC,I wish the program would not allow me to use an expired card in a transaction.
1825870,2019-05-19 14:51:28 UTC,"anyway, this is not possible."
1825871,2019-04-24 03:34:32 UTC,"@jeyjey,"
1825872,2019-09-17 04:17:33 UTC,[Expired for neutron (Ubuntu) because there has been no activity for 60 days.]
1825872,2019-07-18 12:44:50 UTC,Switching to python3 in cosmic or bionic/rocky is 100% manual in terms of switching alternatives OR ensuring that the python-* modules are purged or not installed in the first place.
1825873,2019-04-22 20:30:54 UTC,"If this bug is about the failure to upgrade to the new release of Ubuntu that is because your /etc/apt/sources.list file contains ""mirror"" lines instead of http or https and the release upgrader does not understand those. If you switch your /etc/apt/sources.list file to use http then the upgrade may work better."
1825876,2019-04-22 17:47:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654584"
1825876,2019-05-14 11:42:01 UTC,"Change abandoned by Nikolay Fedotov (<email address hidden>) on branch: master
Review: https://review.opendev.org/654584"
1825879,2019-08-19 04:17:20 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1825879,2019-04-23 01:31:15 UTC,Needs nova-api log.
1825879,2019-04-23 02:07:02 UTC,How do I get nova-api log?
1825879,2019-05-21 15:13:36 UTC,"There should be a log for the nova-api service running on whatever host the nova-api service is running on, check your logging config, it depends on your setup. It could be writing to journald or /var/logs/ or httpd logs, etc."
1825879,2019-06-19 08:54:48 UTC,"If you are in devstack, you can get the nova-api log with: journalctl -f --unit <email address hidden>"
1825882,2019-07-10 21:39:55 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1825882,2019-04-25 13:51:11 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655696"
1825882,2019-07-03 18:20:27 UTC,This bug was fixed in the package nova - 2:19.0.0-0ubuntu2.3
1825882,2019-09-27 09:04:16 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1825882,2019-07-01 13:41:01 UTC,"This bug was fixed in the package nova - 2:17.0.9-0ubuntu3~cloud0
---------------"
1825882,2019-04-25 13:26:06 UTC,Yeah indeed it looks like the raise was used improperly. Probably a better thing to do here would be to use the excutils.save_and_reraise_exception() which provides a context manager that you can control if the exception should be re-raised or not.
1825882,2019-07-01 13:36:53 UTC,"This bug was fixed in the package nova - 2:19.0.0-0ubuntu2.3~cloud0
---------------"
1825882,2019-06-05 14:23:17 UTC,I have verified the following versions:
1825882,2019-05-20 19:04:37 UTC,"Hello Gustavo, or anyone else affected,"
1825882,2019-05-20 15:05:03 UTC,"Hello Gustavo, or anyone else affected,"
1825882,2019-05-17 12:50:13 UTC,"Hello Gustavo, or anyone else affected,"
1825882,2019-05-17 07:33:57 UTC,This bug was fixed in the package nova - 2:19.0.0-0ubuntu5
1825882,2019-05-16 17:54:43 UTC,"Hello Gustavo, or anyone else affected,"
1825882,2019-05-16 17:17:48 UTC,"Hello Gustavo, or anyone else affected,"
1825882,2019-05-16 17:11:14 UTC,"Hello Gustavo, or anyone else affected,"
1825882,2019-05-06 15:26:50 UTC,"Reviewed:  https://review.opendev.org/657050
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=63b45a87b82655824e61641016430a6613cee001
Submitter: Zuul
Branch:    stable/queens"
1825882,2019-05-05 17:41:58 UTC,"Reviewed:  https://review.opendev.org/657051
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=34b4220448395f10eb2fd39d68b3f527339ab414
Submitter: Zuul
Branch:    stable/rocky"
1825882,2019-05-04 15:21:02 UTC,"Reviewed:  https://review.opendev.org/657049
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b3dedefcc58a1fc76ba37f9f8bb1ef7d238aaceb
Submitter: Zuul
Branch:    stable/stein"
1825882,2019-05-03 21:14:57 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/657051"
1825882,2019-05-03 21:11:34 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/657050"
1825882,2019-05-03 21:10:54 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/657049"
1825882,2019-05-03 21:08:55 UTC,"Reviewed:  https://review.opendev.org/655696
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bc57ae50734fa6a70115b6369e867079fb5eb4b8
Submitter: Zuul
Branch:    master"
1825882,2019-06-05 21:17:01 UTC,This bug was fixed in the package nova - 2:17.0.9-0ubuntu3
1825882,2019-06-05 21:17:46 UTC,This bug was fixed in the package nova - 2:18.1.0-0ubuntu3
1825882,2019-06-06 06:24:16 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1825882,2019-07-01 13:36:50 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1825882,2019-06-18 03:41:04 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1825882,2019-06-14 22:48:39 UTC,"OK, verified S/Q/R as commented on https://bugs.launchpad.net/bugs/1826523"
1825882,2019-07-01 13:40:59 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1825883,2019-04-24 07:55:59 UTC,I was thinking about this bug some more and I'd like to work through a mental scenario:
1825883,2019-04-22 19:32:15 UTC,This is curious because I would expect this to work. I will write a spread test tomorrow and see what happens.
1825883,2019-04-23 07:03:52 UTC,I can reproduce this error according to the instructions given. I will now write an integration test that does the same in a reduced and reproducible environment.
1825883,2019-04-23 07:21:01 UTC,This is also easily reproducible with a regression test. I will now inspect what the heck is wrong.
1825883,2019-04-23 13:40:57 UTC,We understand the bug now but fixing it will require some discussion inside the team that we cannot do today due to partial presence of key members.
1825883,2019-04-23 08:32:47 UTC,We managed to debug this to the following observation:
1825883,2019-04-25 21:07:19 UTC,I've proposed a 2nd version of the patch fixing this as https://github.com/snapcore/snapd/pull/6781
1825883,2019-04-30 09:43:32 UTC,"This is being re-worked again, the 2nd fix wasn't correct after all and gets reverted."
1825883,2019-05-21 14:36:22 UTC,This was really fixed in https://github.com/snapcore/snapd/pull/6802
1825883,2019-04-24 13:26:42 UTC,I proposed an halfway there fix that addresses enough of the problem to fix the content interface https://github.com/snapcore/snapd/pull/6770
1825887,2019-06-14 01:21:10 UTC,I agree that adding a credential via --credential should be optional when adding a cloud.
1825887,2019-06-27 08:17:08 UTC,This is a correct behavior - user does not need to specify a credential when adding a cloud to a bootstrapped controller.
1825889,2019-06-14 01:24:17 UTC,It is true that a cloud on which a controller resides will dictate what clouds it is compatible with. We need to restrict what clouds bootstrapped controller accepts and guide users better.
1825889,2019-08-20 23:50:05 UTC,PR for develop: https://github.com/juju/juju/pull/10543
1825893,2019-04-23 07:48:34 UTC,I think triaging to gnome-shell-extensions might be the wrong approach in this case.
1825896,2019-05-13 17:05:20 UTC,"Thanks, Kyle."
1825896,2019-04-24 20:48:27 UTC,Some further discussion on the migration of Hatch data.directory to a shared/machine wide location on Windows:
1825896,2019-05-13 16:09:03 UTC,I've pushed a branch here built off Bill's hatch-workstations-hostname branch that ensures the windows installer will change the logging file/directory to exist within %ProgramData%/Hatch/
1825896,2019-05-13 17:14:15 UTC,Windows build posted:
1825896,2019-04-24 20:14:33 UTC,Summarizing some discussion from the hackfest:
1825896,2019-05-02 14:39:17 UTC,Note the Hatch working branch linked in the previous comment is built atop the JDK-11 branch for bug #1817932.
1825896,2019-05-02 14:29:18 UTC,Linked bug #1825891 as dupe to this one since they are so tightly linked.
1825903,2019-05-19 15:39:10 UTC,I tried python-pythonmagick_0.9.19-4_amd64.deb from eoan which works.
1825903,2019-05-19 15:31:50 UTC,Is there a way to find out if the Debian fix is going to be pulled into disco?  This bug also effects the python3 package.
1825906,2020-02-26 20:23:59 UTC,"Running into this issue in an openstack stein cloud with 39 nodes:
 - 37 nova-compute+ceph-osd
 - 2  neutron-gateway+ceph-osd"
1825906,2019-04-23 15:57:28 UTC,"To reduce queue build-up and alerting, you can use the following:"
1825906,2020-06-27 21:34:38 UTC,Neutron gateway should have an interface such as: https://github.com/openstack/charm-neutron-api/blob/master/metadata.yaml#L36
1825906,2020-07-03 10:21:19 UTC,"Reviewed:  https://review.opendev.org/738477
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=86eb58317fc1d28dccc76e201ddff2c9f5fd1235
Submitter: Zuul
Branch:    master"
1825906,2019-04-23 14:24:13 UTC,The behavior of keeping the lbaasv2-agent around on the ``neutron-gateway`` is intentional to support deployments migrating from the Neutron built in agent to Octavia.
1825906,2020-06-21 04:06:41 UTC,This is just happening to me in a Stein fresh install.
1825906,2019-04-23 15:41:34 UTC,"The message queue buildup, the log file accumulating errors that are invalid to the architecture, and the lbaasv2 agents showing as dead in neutron agent-list, which is alerted by openstack-service-checks"
1825911,2020-02-14 07:17:43 UTC,Attempted to reproduced this with current master (c8f1540a849312ab918acbc77aa40eab823efdf5) and at least now it seems to be working properly:
1825913,2019-04-27 18:04:15 UTC,"Fixed in
master: 33fe9a276169ba54b22c88375c48d83c0cdfd09e
5.1: 65a6e341ad79b2691cc440fe68ce081c80f2a788"
1825914,2019-06-23 04:18:04 UTC,[Expired for calibre because there has been no activity for 60 days.]
1825914,2019-04-23 07:06:51 UTC,"After fetching news,I just used the calibre to read the news.The file has no image ,and just can see the word image.And here are some nytimes e-book with no images."
1825914,2019-04-23 05:55:26 UTC,"Which viewer are you using to check if there are no images? I tried it
with the calibre viewer and the images show up."
1825916,2019-04-23 01:53:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654665"
1825916,2019-05-27 11:13:47 UTC,"Reviewed:  https://review.opendev.org/654665
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=f463afa625c703fb827f49f2edcd1da1307aacab
Submitter: Zuul
Branch:    master"
1825918,2019-10-31 23:32:35 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10551"
1825918,2019-12-18 07:23:41 UTC,"Reviewed:  https://reviews.mahara.org/10551
Committed: https://git.mahara.org/mahara/mahara/commit/d05fafa5e048775b41e5c567775183f2a3af38c8
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1825919,2019-04-25 14:47:11 UTC,It just happened now...
1825919,2019-04-23 02:51:31 UTC,I see this in my application logs:
1825919,2019-04-23 11:58:46 UTC,"Thank you for your bug report. Do you have some specific actions you do that lead to the problem,? Do you have non default extensions?"
1825919,2019-04-24 04:33:03 UTC,"NON_DEFAULT EXTENSIONS
----------------------"
1825919,2019-04-24 10:12:39 UTC,Do you have any gedit warning/error in the journalctl log when the problem stats? Could you try without the extensions you are using to see if that's due to one of those? (or maybe try disabling a few that are non essential to you)
1825919,2019-04-25 14:47:27 UTC,"Apr 25 10:17:42 PS006 systemd[1]: snapd.service: Succeeded.
Apr 25 10:17:45 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed
Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm=""/usr/bin/gnome-shell "" label=""unconfined"")
Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Logs'
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm=""/usr/bin/gnome-shell "" label
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm=""/usr/bin/gnome-shell "" label=""u
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Characters.BackgroundService' requested by ':1.15' (uid=1000 pid=1936 comm=""/usr/bin/gnome-shell "" label
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.clocks' requested by ':1.15' (uid=1000 pid=1936 comm=""/usr/bin/gnome-shell "" label=""unconfined"")
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm=""/usr/bin/gnome-shell "" label=""unconf
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.ControlCenter.SearchProvider'
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.clocks'
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application'
Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Characters.BackgroundService'
Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Calculator.SearchProvider'
Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: M
Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0
Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:”
Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm=""/usr/bin/gnome-shell "" label=""unconf
Apr 25 10:19:21 PS006 systemd[1]: Starting Snappy daemon...
Apr 25 10:19:21 PS006 snapd[1036]: AppArmor status: apparmor is enabled and all features are available
Apr 25 10:19:21 PS006 snapd[1036]: daemon.go:379: started snapd/2.38+19.04 (series..."
1825919,2019-06-25 04:17:36 UTC,[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]
1825920,2019-07-26 18:16:32 UTC,This issue was fixed in the openstack/tripleo-ipsec 9.2.0 release.
1825924,2019-04-26 04:37:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825927,2019-04-23 04:47:45 UTC,c.f. this for Mac: https://wl.widelands.org/forum/topic/2627/?page=3#post-27619
1825927,2019-09-16 14:21:51 UTC,Migrated to https://github.com/widelands/widelands/issues/1725
1825928,2019-04-24 14:29:29 UTC,"I'm sorry, I wanted ""apt-term.log"" not ""apt.log"". Thanks again!"
1825928,2019-04-23 16:56:04 UTC,The log files attached to this bug report do not cover the time frame when the linux package failed to install. Could you please look in /var/log/dist-upgrade for a folder with a date and time corresponding to when you upgraded from Ubuntu 18.10 to Ubuntu 19.04 and then attach the apt.log file from within that folder to this bug report? Thanks in advance.
1825928,2019-04-24 05:22:40 UTC,I am adding a second log just in case.  This would have been from my second attempt to update after the initial error.
1825928,2019-04-25 14:28:21 UTC,I have attached the apt-term.log file.
1825928,2019-06-25 04:17:37 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825928,2019-04-24 05:14:59 UTC,I added the apt.log from the appropriate time frame.  Let me know if I can provide anything else!
1825931,2019-05-09 01:42:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657909"
1825931,2020-11-19 15:44:03 UTC,"Change abandoned by Michał Dulko (<email address hidden>) on branch: master
Review: https://review.opendev.org/657909"
1825932,2019-09-15 15:47:44 UTC,Migrated to https://github.com/widelands/widelands/issues/1726
1825935,2021-01-09 04:17:28 UTC,[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]
1825935,2020-11-09 08:43:37 UTC,"Hello,
do you still have this issue with the latest kernel on Xenial? Is there anything not working for you?
Thanks"
1825935,2019-09-04 14:17:51 UTC,This issue was fixed in the openstack/oslo.utils 3.41.1 release.
1825936,2019-05-17 01:28:29 UTC,OK，thank you! I will try it later.
1825936,2019-04-23 06:19:09 UTC,https://review.opendev.org/#/c/654681/
1825936,2019-05-16 06:43:58 UTC,This issue was fixed in the openstack/oslo.serialization 2.29.1 release.
1825938,2019-05-04 19:57:54 UTC,"This issue affected me too, and I think I figured out what the issue is."
1825938,2019-04-23 20:41:39 UTC,"On Tue, Apr 23, 2019 at 08:20:47PM -0000, Jonathan H wrote:

> Many thanks - that's very helpful! They even suggested that the problem
> was because ""The do-release-upgrade will only upgrade an LTS version to
> the next LTS release by default"".
"
1825938,2019-04-23 20:20:47 UTC,"Many thanks - that's very helpful! They even suggested that the problem was because ""The do-release-upgrade will only upgrade an LTS version to the next LTS release by default""."
1825938,2019-04-23 19:08:33 UTC,Perhaps they are blocking by user agents.
1825938,2019-04-23 19:04:10 UTC,"I went ahead and switched my mirror of the Ubuntu archive to mirrors.digitalocean.com and set RELEASE_UPGRADER_ALLOW_THIRD_PARTY=1, which just prevents the unknown mirror question from appearing, and ran into the following issue:"
1825938,2019-04-23 17:49:46 UTC,"Note that in the error below, it complains about not being able to find ubuntu-minimal, however, if I try and install it, it says:"
1825938,2019-04-23 17:22:19 UTC,The log files attached to this bug report aren't particularly helpful for some reason. Could you include the terminal output when the upgrade attempt fails?  Thanks in advance.
1825938,2019-07-04 04:17:23 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825940,2019-07-02 14:01:05 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1012.13
1825940,2019-04-23 07:00:17 UTC,"new media will not supported in 19.04 as default. if want to do test, have to enable graphics firstly."
1825940,2019-04-23 06:58:41 UTC,2909bf0562693b39edda06359ea265fac877f937
1825940,2019-05-06 05:30:15 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825940,2019-05-28 08:56:34 UTC,backported patches for mesa 19.0:
1825940,2019-05-28 14:13:23 UTC,This bug was fixed in the package mesa - 19.0.5-0ubuntu1
1825940,2019-06-18 06:23:26 UTC,linux-oem-osp1 has backports in bionic-proposed
1825940,2019-06-26 00:20:48 UTC,"update for icl latest commmits compared with 2019/06/17
--- icl_commit_20190617.list_kernv_drm-tip      2019-06-17 17:10:09.330369948 +0800
+++ icl_commit_20190626.list_kernv_drm-tip      2019-06-26 08:10:11.102281024 +0800
@@ -1,6 +1,23 @@
-f4071997f1d,drm/i915/ehl: Update MOCS table for EHL,2019-05-30 16:40:14,not in drm-intel-next/linux-upstream
-cc49abc2460,drm/i915: Add Wa_1409120013:icl,ehl,2019-06-12 11:36:31,not in drm-intel-next/linux-upstream
-326fb6dd148,drm/i915/dmc: protect against reading random memory,2019-06-05 16:55:35,next-20190613
+fc25441c7b9,drm/i915/ehl: Add one additional PCH ID to MCC,2019-06-21 08:18:47,not in drm-intel-next/linux-upstream
+8dcfdfb4501,drm/i915/perf: fix ICL perf register offsets,2019-06-10 11:19:14,not in drm-intel-next/linux-upstream
+f9a393875d3,drm/i915: Disable SAMPLER_STATE prefetching on all Gen11 steppings.,2019-06-25 10:06:55,not in drm-intel-next/linux-upstream
+683d672c425,drm/i915/ehl/dsi: Enable AFE over PPI strap,2019-06-19 16:31:34,next-20190621
+6a7bafe8fdb,drm/i915/ehl/dsi: Set lane latency optimization for DW1,2019-06-19 16:31:33,next-20190621
+bdeb18dbcf8,drm/i915/ehl: Allow combo PHY A to drive a third external display,2019-06-18 10:51:31,next-20190620
+patches series of Update whitelist support for new hardware,,,
+1/4 5380d0b781c ADDED!,drm/i915: Support flags in whitlist WAs,2019-06-17 18:01:05,next-20190619
+2/4 ebd2de47a19 ADDED!,drm/i915: Support whitelist workarounds on all engines,2019-06-17 18:01:06,next-20190619
+3/4 7b3d4063109,drm/i915: Add whitelist workarounds for ICL,2019-06-17 18:01:07,next-20190619
+4/4 767662bc62a ADDED!,drm/i915: Update workarounds selftest for read only regs,2019-06-17 18:01:08,next-20190619
+c6f7acb80ab,drm/i915/ehl: Introduce Mule Creek Canyon PCH,2019-06-14 17:42:10,next-20190619
+patches series of Enable Multi-segmented-gamma for ICL,,,
+1/4 89a72304f2f,drm/i915: Change gamma/degamma_lut_size data type to u32,2019-06-12 12:14:57,next-20190619
+2/4 377c70edd48,drm/i915/icl: Add register definitions for Multi Segmented gamma,2019-06-12 12:14:58,next-20190619
+3/4 eec0778ec42 ADDED!,drm/i915: Rename ivb_load_lut_10_max,2019-06-12 12:14:59,next-20190619
+4/4 02ae8ba9664,drm/i915/icl: Add Multi-segmented gamma support,2019-06-12 12:15:00,next-20190619
+f4071997f1d,drm/i915/ehl: Update MOCS table for EHL,2019-05-30 16:40:14,next-20190617
+cc49abc2460,drm/i915: Add Wa_1409120013:icl,ehl,2019-06-12 11:36:31,next-20190617
+326fb6dd148,drm/i915/dmc: protect against reading random memory,2019-06-05 16:55:35,v5.2-rc5"
1825940,2019-08-14 01:08:31 UTC,"The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825940,2019-07-02 07:25:49 UTC,"20170702 update of ICL kernel (drm-tip)
--- icl_commit_20190626.list_kernv_drm-tip      2019-06-26 08:10:11.102281024 +0800
+++ icl_commit_20190702.list_kernv_drm-tip      2019-07-02 13:55:00.666216695 +0800
@@ -1,6 +1,10 @@
-fc25441c7b9,drm/i915/ehl: Add one additional PCH ID to MCC,2019-06-21 08:18:47,not in drm-intel-next/linux-upstream
-8dcfdfb4501,drm/i915/perf: fix ICL perf register offsets,2019-06-10 11:19:14,not in drm-intel-next/linux-upstream
-f9a393875d3,drm/i915: Disable SAMPLER_STATE prefetching on all Gen11 steppings.,2019-06-25 10:06:55,not in drm-intel-next/linux-upstream
+63c9dae71dc,drm/i915/ehl: Add voltage level requirement table,2019-06-25 18:40:53,next-20190628
+6e63790efdf,drm/i915/ehl: Remove unsupported cd clocks,2019-06-25 18:40:52,next-20190628
+9c811fce8a4,drm/i915/icl: Add new supported CD clocks,2019-06-25 18:40:51,next-20190628
+9a6a644096a,drm/i915/ehl: Add missing VECS engine,2019-06-14 14:37:49,next-20190628
+fc25441c7b9,drm/i915/ehl: Add one additional PCH ID to MCC,2019-06-21 08:18:47,next-20190628
+8dcfdfb4501,drm/i915/perf: fix ICL perf register offsets,2019-06-10 11:19:14,next-20190628
+f9a393875d3,drm/i915: Disable SAMPLER_STATE prefetching on all Gen11 steppings.,2019-06-25 10:06:55,next-20190628"
1825940,2019-07-09 06:25:33 UTC,"--- icl_commit_20190702.list_kernv_drm-tip      2019-07-02 13:55:00.666216695 +0800
+++ icl_commit_20190709.list_kernv_drm-tip      2019-07-09 13:40:15.070144631 +0800
@@ -1,13 +1,52 @@
+patches series of drm/i915: Random plane stuff,,,
+1/6 26443a4bc44 ADDED!,drm/i915: Add windowing for primary planes on gen2/3 and chv,2019-07-03 23:08:19,next-20190708
+2/6 423ee8e99aa ADDED!,drm/i915: Disable sprite gamma on ivb-bdw,2019-07-03 23:08:20,next-20190708
+3/6 94e15723df8 ADDED!,drm/i915: Program plane gamma ramps,2019-07-03 23:08:21,next-20190708
+4/6 d56e823ac32 ADDED!,drm/i915: Deal with cpp==8 for g4x watermarks,2019-07-03 23:08:22,next-20190708
+5/6 94e35ce2217 ADDED!,drm/i915: Cosmetic fix for skl+ plane switch statement,2019-07-03 23:08:23,next-20190708
+6/6 3e69db291bd,drm/i915: Clean up skl vs. icl plane formats,2019-07-03 23:08:24,next-20190708
+patches series of More mmio and intel_gt cleanups and refactorings,,,
+1/3 9b77011e412 ADDED!,drm/i915: Rework some interrupt handling functions to take intel_gt,2019-07-04 13:17:54,next-20190708
+2/3 f0818984fa5,drm/i915: Remove some legacy mmio accessors from interrupt handling,2019-07-04 13:17:55,next-20190708
+3/3 NOT-IN-UPSTREAM,drm/i915: Move dev_priv->pm_i{m,e}r into intel_gt,,
+56e9371bc3f,drm/i915: Deal with machines that expose less than three QGV points,2019-06-06 15:42:10,next-20190708
+8e9ecb3e1e3,drm/i915/display: Handle lost primary_port across suspend,2019-07-02 15:09:50,next-20190708
+patches series of drm/i915: CTS fixes,,,
+1/3 361b6905132 ADDED!,drm/i915: fix whitelist selftests with readonly registers,2019-06-29 14:13:50,next-20190703
+2/3 2c903da50f5 ADDED!,drm/i915: whitelist PS_(DEPTH|INVOCATION)_COUNT,2019-06-28 15:07:19,next-20190703
+3/3 3fe0107e45a,drm/i915/icl: whitelist PS_(DEPTH|INVOCATION)_COUNT,2019-06-28 15:07:20,next-20190703
+4a8134d57c6,drm/i915/icl: Drop port parameter to icl_get_combo_buf_trans(),2019-06-25 17:03:48,next-20190703
+patches series of drm/i915: Fix TypeC port mode switching,,,
+01/23 39a5883f867,drm/i915/icl: Add support to read out the TBT PLL HW state,2019-06-28 17:36:13,next-20190703
+02/23 28212321622 ADDED!,drm/i915: Tune down WARNs about TBT AUX power well enabling,2019-06-28 17:36:14,next-20190703
+03/23 bc85328ff43,drm/i915: Move the TypeC port handling code to a separate file,2019-06-28 17:36:15,next-20190703
+04/23 e9b7e1422d4 ADDED!,drm/i915: Sanitize the terminology used for TypeC port modes,2019-06-28 17:36:16,next-20190703
+05/23 3b2ed431342 ADDED!,drm/i915: Don't enable the DDI-IO power in the TypeC TBT-alt mode,2019-06-28 17:36:17,next-20190703
+06/23 29ae36abf08 ADDED!,drm/i915: Fix the TBT AUX power well enabling,2019-06-28 17:36:18,next-20190703
+07/23 dd7239c545b ADDED!,drm/i915: Use the correct AUX power domain in TypeC TBT-alt mode,2019-06-28 17:36:19,next-20190703
+08/23 ab7bc4e1a55,drm/i915: Unify the TypeC port notation in debug/error messages,2019-06-28 17:36:20,next-20190703
+09/23 c905eb28bd3,drm/i915: Factor out common parts from TypeC port handling functions,2019-06-28 17:36:21,next-20190703
+10/23 ddec362724f ADDED!,drm/i915: Wait for TypeC PHY complete flag to clear in safe mode,2019-06-28 17:36:22,next-20190703..."
1825940,2019-07-27 04:48:21 UTC,"Hello quanxian, or anyone else affected,"
1825940,2019-08-05 12:21:19 UTC,eoan has 5.2
1825940,2019-08-05 12:34:33 UTC,looks like a patch to disable softpin on mesa (to fix bug #1836721) actually regressed ICL which needs softpin... so now softpin needs to be backported to bionic kernel (4.15) so that the mesa revert can be dropped
1825940,2019-08-06 07:26:27 UTC,"while ICL support is broken right now, and the version in proposed doesn't change that, I'll still mark this verified so that the current version can move to -updates"
1825940,2019-08-07 08:25:13 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
1825940,2019-08-14 01:08:19 UTC,This bug was fixed in the package mesa - 19.0.8-0ubuntu0~18.04.1
1825940,2019-07-02 09:18:22 UTC,thanks
1825940,2019-04-29 08:53:33 UTC,"That commit is not in 5.1, but will be in 5.2."
1825941,2019-04-23 08:37:21 UTC,These issues seem to be related:
1825941,2019-04-24 14:52:24 UTC,"The fixed version is in Eoan!
https://packages.ubuntu.com/eoan/zulumount-cli"
1825941,2019-04-24 14:49:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825942,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1825942,2019-07-05 08:16:02 UTC,"I have now tested the updated Linux kernel from bionic proposed. The
new kernel seems to solve the problem and the fix appears OK for :"
1825942,2019-07-03 13:06:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825942,2019-06-28 12:10:38 UTC,"Hi Viktor,"
1825942,2019-06-17 06:14:55 UTC,"As I understood it, the fix was unfortunately some days to late for the he previous Kernel SRU cycle. I then expected the fix to be applied for the current SRU cycle, that is, 03-Jun through 30-Jun. I still assume that is the case?"
1825942,2019-06-13 10:21:47 UTC,"I did expect a change in status to ""Fix Committed"", indicating that the fix had been applied?"
1825942,2019-05-17 06:56:23 UTC,Fix against bionic submitted to the kernel ML: https://lists.ubuntu.com/archives/kernel-team/2019-May/100741.html
1825942,2019-05-16 15:58:24 UTC,Thanks a lot. That's great.
1825942,2019-05-03 10:51:33 UTC,"This crash is currently critical when using traffic control (tc) in one of the Ubuntu LTS releases, bionic and xenial linux-hwe."
1825942,2019-04-25 08:09:31 UTC,"I could have been more explicit. The thread linked to in the initial bug description also contains a simplified script by Ben Hutchings <email address hidden> that triggers the kernel crash (included below for the reference):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10"
1825942,2019-04-23 07:55:22 UTC,"Log files should not be required, as this issue is already confirmed and also fixed in the Linux kernel."
1825942,2019-04-23 07:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825942,2019-04-23 07:16:46 UTC,I should have added that there were a couple of other commits related to this issue (memory leaks in cls_tcindex) that were also merged in.
1825942,2019-04-23 07:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825942,2019-08-22 16:17:20 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1825943,2019-05-10 12:42:50 UTC,I agree with Slaweq's proposal of having separate config options for each type of process. Certain processes continue to run in the same container as the respective agent and others processes might require special service specific cleanups.
1825943,2019-04-26 07:10:55 UTC,"I agree with Cedric here. We are currently simply send ""kill"" (-9 in some cases) to the process, even if it is in fact container.
What we can IMHO do is provide e.g. config option (or options, one per type of process managed by neutron, like e.g. one for dnsmasq, one for keepalived and so on) that will allow to set some ""kill script"". If it would be set, it would be used instead of kill command to stop such processes."
1825943,2019-05-17 14:24:35 UTC,The neutron drivers team discussed and approved this RFE
1825943,2019-04-26 05:34:45 UTC,"Hello Miguel,"
1825943,2019-04-26 03:28:03 UTC,"Hi Cedric,"
1825943,2019-05-28 14:06:41 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661760"
1825943,2019-06-05 01:10:05 UTC,"Reviewed:  https://review.opendev.org/661760
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=93015527f02cb54b0b2bc07c8c9c239c63878264
Submitter: Zuul
Branch:    master"
1825943,2019-06-05 09:37:02 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/663289"
1825943,2019-05-10 06:39:59 UTC,"Hello Miguel,"
1825943,2019-06-08 02:40:39 UTC,"Reviewed:  https://review.opendev.org/663289
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=702d4b321447d94598e1962cb67a7da968fa5fba
Submitter: Zuul
Branch:    stable/stein"
1825943,2019-09-19 10:13:23 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1825943,2019-07-01 02:48:58 UTC,This issue was fixed in the openstack/neutron 14.0.2 release.
1825943,2019-05-09 22:19:30 UTC,"@Cedric,"
1825944,2019-04-23 17:03:50 UTC,Something is wrong with the name resolution service the system which you are trying to upgrade is using. From VarLogDistupgradeMainlog.txt we can see:
1825944,2019-06-23 04:18:40 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825946,2019-05-13 14:48:53 UTC,network-manager 1.10.14-0ubuntu2 witrh the fix for this bug got transferred to bionic-updates. Thanks to the SRU team for the great cooperation.
1825946,2019-05-14 08:42:22 UTC,"Dan, if you are on it, preparing a network-manager SRU for Xenial, could you also add the patch which fixes bug 1754671? Here we also need a network-manager SRU for."
1825946,2019-05-15 21:19:00 UTC,"> could you also add the patch which fixes bug 1754671
"
1825946,2019-10-29 08:32:55 UTC,"nm test no longer fails due to stderr output as listed in description.  nm test does now fail due to the test thinking dnsmasq is not available, but that's a separate bug."
1825946,2019-10-25 10:34:24 UTC,"Hello Dan, or anyone else affected,"
1825946,2020-05-11 15:52:51 UTC,"All autopkgtests for the newly accepted network-manager (1.2.6-0ubuntu0.16.04.4) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:"
1825946,2019-12-07 16:09:21 UTC,"test no longer prints gi warning, e.g.:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/network-manager/20191206_223737_58d54@/log.gz"
1825946,2019-12-07 02:24:33 UTC,"All autopkgtests for the newly accepted network-manager (1.2.6-0ubuntu0.16.04.4) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:"
1825946,2019-12-06 21:14:50 UTC,"Hello Dan, or anyone else affected,"
1825946,2019-12-02 17:23:35 UTC,"> nm test no longer fails due to stderr output as listed in description. nm
> test does now fail due to the test thinking dnsmasq is not available, but
> that's a separate bug.
"
1825946,2019-11-04 14:08:07 UTC,"The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825946,2019-11-04 14:07:48 UTC,This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.2
1825946,2019-07-31 14:03:12 UTC,"A fix for this was added for bionic at version 1.10.14-0ubuntu2, but that was reverted due to regressions, so this is not yet fixed in bionic-updates"
1825946,2019-10-25 12:24:41 UTC,"All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1825947,2019-05-14 02:13:45 UTC,"Set to invaild, the original issue will be handled in SB 2004760 task 30978"
1825947,2019-05-14 02:10:35 UTC,"Change abandoned by Mingyuan Qi (<email address hidden>) on branch: master
Review: https://review.opendev.org/655619
Reason: abandon the change due to adding a dedicated ironic network"
1825947,2019-04-25 06:43:21 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655619"
1825947,2019-04-24 20:25:38 UTC,Marking as release gating; functionality required for use of ironic
1825949,2020-04-03 05:21:52 UTC,"Reviewed:  https://review.opendev.org/668900
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=3446481a23d2c878297b4f535c7b9b44d07ed5fb
Submitter: Zuul
Branch:    master"
1825949,2019-07-03 13:17:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668900"
1825949,2019-07-03 13:18:09 UTC,"Thanks for the notification, I have create a patch for that document at https://review.opendev.org/668900 , please review and possibly propose a better wording."
1825952,2019-05-29 13:40:23 UTC,"Reviewed:  https://review.opendev.org/654889
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=564fb5aa5babfc16b72a9b1aa95f65b80c663d05
Submitter: Zuul
Branch:    master"
1825952,2019-06-12 14:43:56 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1825952,2019-04-23 09:06:41 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654889"
1825954,2019-06-12 14:43:49 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1825954,2019-05-29 12:18:50 UTC,"Reviewed:  https://review.opendev.org/654896
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=7c77637f7643f5500234b809fce348e3f1d7a80b
Submitter: Zuul
Branch:    master"
1825954,2019-04-23 09:18:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/654896"
1825958,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1825958,2019-05-15 02:45:37 UTC,"This has been released in linux-oem. For generic kernel, this has been landed to bionic/master-next but not yet released."
1825958,2019-05-02 07:44:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1825958,2019-04-23 09:33:48 UTC,"Need https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d3252ace0bc652a1a244455556b6a549f969bf99 , which is included in Disco and has been SRU-ed to Cosmic in bug 1788874 (for linux v4.18.5 stable release)."
1825958,2019-04-23 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825958,2019-05-14 19:03:14 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1825959,2019-04-23 09:48:01 UTC,Thank you for your bug report and for sending it upstream
1825960,2019-05-29 10:01:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825960,2019-05-29 10:04:42 UTC,Should be fixed in 19.10 Eoan with bugfix release:
1825960,2019-04-23 10:02:09 UTC,"ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 19:00:23 2019
Dependencies:
 adduser 3.118ubuntu1
 apt 1.8.0
 apt-utils 1.8.0
 bzip2 1.0.6-9
 ca-certificates 20190110
 coreutils 8.30-1ubuntu1
 dbus 1.12.12-1ubuntu1
 debconf 1.5.71
 debconf-i18n 1.5.71
 dpkg 1.19.6ubuntu1
 file 1:5.35-4
 fontconfig 2.13.1-2ubuntu2
 fontconfig-config 2.13.1-2ubuntu2
 fonts-dejavu-core 2.37-1
 gcc-9-base 9-20190402-1ubuntu1
 gpgv 2.2.12-1ubuntu3
 krb5-locales 1.17-1
 krita-data 1:4.1.7+dfsg-1
 kwayland-data 4:5.56.0-0ubuntu1
 kwayland-integration 4:5.15.4-0ubuntu1
 libacl1 2.2.53-4
 libapparmor1 2.13.2-9ubuntu6
 libapt-inst2.0 1.8.0
 libapt-pkg5.0 1.8.0
 libasyncns0 0.8-6
 libattr1 1:2.4.48-4
 libaudit-common 1:2.8.3-1ubuntu3
 libaudit1 1:2.8.3-1ubuntu3
 libavahi-client3 0.7-4ubuntu5
 libavahi-common-data 0.7-4ubuntu5
 libavahi-common3 0.7-4ubuntu5
 libblkid1 2.33.1-0.1ubuntu2
 libboost-system1.67.0 1.67.0-13
 libbsd0 0.9.1-2
 libbz2-1.0 1.0.6-9
 libc6 2.29-0ubuntu2
 libcap-ng0 0.7.9-2
 libcom-err2 1.44.6-1
 libcups2 2.2.10-4
 libdb5.3 5.3.28+dfsg1-0.5
 libdbus-1-3 1.12.12-1ubuntu1
 libde265-0 1.0.3-1build1
 libdouble-conversion1 3.1.0-2
 libdrm-amdgpu1 2.4.97-1ubuntu1
 libdrm-common 2.4.97-1ubuntu1
 libdrm-intel1 2.4.97-1ubuntu1
 libdrm-nouveau2 2.4.97-1ubuntu1
 libdrm-radeon1 2.4.97-1ubuntu1
 libdrm2 2.4.97-1ubuntu1
 libedit2 3.1-20181209-1
 libegl-mesa0 19.0.2-1ubuntu1
 libegl1 1.1.1-0ubuntu1
 libelf1 0.176-1
 libevdev2 1.6.0+dfsg-1
 libexiv2-14 0.25-4ubuntu1
 libexpat1 2.2.6-1
 libfam0 2.7.0-17.3
 libffi6 3.2.1-9
 libfftw3-double3 3.3.8-2
 libflac8 1.3.2-3
 libfontconfig1 2.13.1-2ubuntu2
 libfreetype6 2.9.1-3
 libgbm1 19.0.2-1ubuntu1
 libgcc1 1:9-20190402-1ubuntu1
 libgcrypt20 1.8.4-3ubuntu1
 libgif7 5.1.4-3
 libgl1 1.1.1-0ubuntu1
 libgl1-mesa-dri 19.0.2-1ubuntu1
 libglapi-mesa 19.0.2-1ubuntu1
 libglib2.0-0 2.60.0-1
 libglib2.0-data 2.60.0-1
 libglvnd0 1.1.1-0ubuntu1
 libglx-mesa0 19.0.2-1ubuntu1
 libglx0 1.1.1-0ubuntu1
 libgmp10 2:6.1.2+dfsg-4
 libgnutls30 3.6.5-2ubuntu1
 libgomp1 9-20190402-1ubuntu1
 libgpg-error0 1.35-1
 libgpm2 1.20.7-5
 libgraphite2-3 1.3.13-7
 libgsl23 2.5+dfsg-6
 libgslcblas0 2.5+dfsg-6
 libgssapi-krb5-2 1.17-1
 libgudev-1.0-0 1:232-2
 libharfbuzz0b 2.3.1-1
 libheif1 1.3.2-1build1
 libhogweed4 3.4.1-1
 libice6 2:1.0.9-2
 libicu63 63.1-6
 libidn2-0 2.0.5-1
 libilmbase23 2.2.1-2ubuntu1
 libinput-bin 1.12.6-1
 libinput10 1.12.6-1
 libjbig0 2.1-3.1build1
 libjpeg-turbo8 2.0.1-0ubuntu2
 libjpeg8 8c-2ubuntu8
 libk5crypto3 1.17-1
 libkeyutils1 1.6-6
 libkf5archive5 5.56.0-0ubuntu1
 libkf5completion-data 5.56.0-0ubuntu1
 libkf5completion5 5.56.0-0ubuntu1
 libkf5config-bin 5.56.0-0ubuntu1
 libkf5config-data 5.56.0-0ubuntu1
 libkf5configcore5 5.56.0-0ubuntu1
 libkf5configgui5 5.56.0-0ubuntu1
 libkf5coreaddons-data 5.56.0-0ubuntu1
 libkf5coreaddons5 5.56.0-0ubuntu1
 libkf5crash5 5.56.0-0ubuntu1
 libkf5guiaddons5 5.56.0-0ubuntu1
 libkf5i18n-data 5.56.0-0ubuntu1
 libkf5i18n5 5.56.0-0ubuntu1
 libkf5idletime5 5.56.0-0ubuntu1
 libkf5itemviews-data 5.56.0-0ubuntu1
 libkf5itemviews5 5.56.0-0ubuntu1
 libkf5waylandclient5 4:5.56.0-0ubuntu1
 libkf5widgetsaddons-data 5.56.0-0ubuntu1
 libkf..."
1825961,2019-09-13 16:42:32 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.
1825961,2019-06-12 06:31:33 UTC,"Reviewed:  https://review.opendev.org/653675
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=36515b38b2ab990aa16e14e9a410b710df661652
Submitter: Zuul
Branch:    master"
1825963,2019-04-23 15:45:38 UTC,could you add one of those files to the bug? does it stop doing that if you remove those?
1825963,2019-04-23 16:50:58 UTC,"Here you go. Those are texture files from a mod for the game ""Crusader Kings 2""."
1825963,2019-04-23 19:50:11 UTC,I have the same game installed as well.
1825963,2019-04-25 09:03:54 UTC,"After removing the folder with those .dds files, the memory leak of tracker-extract doesn't occur."
1825963,2019-04-26 14:25:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825963,2019-04-30 15:53:58 UTC,"The issue is an upstream one, could someone report it on https://gitlab.gnome.org/GNOME/tracker/issues ?"
1825963,2019-06-02 12:07:06 UTC,Thanks for providing the 'minimap_area.dds' file. How many other files are there in the same directory? And what is the total size of all of these .dds files?
1825963,2019-07-11 12:21:41 UTC,"In the directory there are 10666 files, total size 735,5 MB. There are 723 .dds files with a total size of 248.2 MB"
1825963,2019-11-03 18:28:45 UTC,The bug is still present in Ubuntu 19.10.
1825963,2019-12-05 21:09:38 UTC,I confirm the bug on 19.10 for DDS files ( from a mod for HOI4)
1825963,2020-07-03 15:51:53 UTC,"I get the same error as Alex, but for TGA files:"
1825963,2019-04-23 15:14:23 UTC,"I have the exact same issue as gert7. Tracker-extract fills my entire memory until kernel kills the process, after which tracker-extract gets started again with the same situation after a few seconds. The only way to make the system usable again is to forcibly kill all tracker processes."
1825963,2019-04-23 11:50:32 UTC,Thank you for your bug report. Could you add your journalctl log to the bug?
1825964,2020-03-09 13:18:04 UTC,"Thank you very much for pointing out this typo to us. This is now fixed
best"
1825964,2020-03-09 13:00:28 UTC,"Hi,"
1825965,2019-04-23 10:29:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825965,2019-04-23 10:39:50 UTC,"Actually, I think this does work, it is just labeled differently."
1825966,2019-05-08 01:57:03 UTC,submitted the patch for review - https://review.opendev.org/#/c/657719/
1825966,2019-05-08 06:41:17 UTC,Could you submit a patch for charm-neutron-openvswitch as well?
1825966,2019-05-08 10:33:08 UTC,"@dmitriis, thank you, this is patch for charm-neutron-openvswitch - https://review.opendev.org/#/c/657774"
1825966,2019-05-18 15:42:07 UTC,"Reviewed:  https://review.opendev.org/657719
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=4c150529b5725e25bfe53d7db15f2f11410c6111
Submitter: Zuul
Branch:    master"
1825966,2019-05-22 06:35:03 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/660574"
1825966,2019-05-29 09:57:18 UTC,"Change abandoned by Zhang Hua (<email address hidden>) on branch: stable/19.04
Review: https://review.opendev.org/660574
Reason: Hi Alex and icey, I'm going to abandon this change, thanks for the review"
1825966,2019-07-23 16:24:24 UTC,"Reviewed:  https://review.opendev.org/657774
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=786906d559d88efbf5b7e95f67ceb0441d653cbd
Submitter: Zuul
Branch:    master"
1825968,2019-05-06 08:50:06 UTC,"The verification of the Stable Release Update for ubuntu-fan has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825968,2019-04-29 19:36:15 UTC,"Since the only change was a modification to dep8 tests, there is nothing else to validate than the successful pass of all arches in xenial (http://autopkgtest.ubuntu.com/packages/u/ubuntu-fan)."
1825968,2019-04-29 10:23:53 UTC,"Hello Stefan, or anyone else affected,"
1825968,2019-05-06 08:49:59 UTC,This bug was fixed in the package ubuntu-fan - 0.12.8~16.04.3
1825969,2019-04-23 18:01:10 UTC,"I tried to recreate this but was unable to, likely because I was not running in a wayland session."
1825972,2019-06-20 19:44:24 UTC,"Removing packages from eoan:
 libgnome 2.32.1-6 in eoan
  libgnome-2-0 2.32.1-6 in eoan amd64
  libgnome-2-0 2.32.1-6 in eoan arm64
  libgnome-2-0 2.32.1-6 in eoan armhf
  libgnome-2-0 2.32.1-6 in eoan i386
  libgnome-2-0 2.32.1-6 in eoan ppc64el
  libgnome-2-0 2.32.1-6 in eoan s390x
  libgnome2-0 2.32.1-6 in eoan amd64
  libgnome2-0 2.32.1-6 in eoan arm64
  libgnome2-0 2.32.1-6 in eoan armhf
  libgnome2-0 2.32.1-6 in eoan i386
  libgnome2-0 2.32.1-6 in eoan ppc64el
  libgnome2-0 2.32.1-6 in eoan s390x
  libgnome2-bin 2.32.1-6 in eoan amd64
  libgnome2-bin 2.32.1-6 in eoan arm64
  libgnome2-bin 2.32.1-6 in eoan armhf
  libgnome2-bin 2.32.1-6 in eoan i386
  libgnome2-bin 2.32.1-6 in eoan ppc64el
  libgnome2-bin 2.32.1-6 in eoan s390x
  libgnome2-common 2.32.1-6 in eoan amd64
  libgnome2-common 2.32.1-6 in eoan arm64
  libgnome2-common 2.32.1-6 in eoan armhf
  libgnome2-common 2.32.1-6 in eoan i386
  libgnome2-common 2.32.1-6 in eoan ppc64el
  libgnome2-common 2.32.1-6 in eoan s390x
  libgnome2-dev 2.32.1-6 in eoan amd64
  libgnome2-dev 2.32.1-6 in eoan arm64
  libgnome2-dev 2.32.1-6 in eoan armhf
  libgnome2-dev 2.32.1-6 in eoan i386
  libgnome2-dev 2.32.1-6 in eoan ppc64el
  libgnome2-dev 2.32.1-6 in eoan s390x
  libgnome2-doc 2.32.1-6 in eoan amd64
  libgnome2-doc 2.32.1-6 in eoan arm64
  libgnome2-doc 2.32.1-6 in eoan armhf
  libgnome2-doc 2.32.1-6 in eoan i386
  libgnome2-doc 2.32.1-6 in eoan ppc64el
  libgnome2-doc 2.32.1-6 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #885768
1 package successfully removed."
1825972,2019-06-20 19:47:43 UTC,"Removing packages from eoan:
 orbit2 1:2.14.19-4 in eoan
  liborbit-2-0 1:2.14.19-4 in eoan amd64
  liborbit-2-0 1:2.14.19-4 in eoan arm64
  liborbit-2-0 1:2.14.19-4 in eoan armhf
  liborbit-2-0 1:2.14.19-4 in eoan i386
  liborbit-2-0 1:2.14.19-4 in eoan ppc64el
  liborbit-2-0 1:2.14.19-4 in eoan s390x
  liborbit2 1:2.14.19-4 in eoan amd64
  liborbit2 1:2.14.19-4 in eoan arm64
  liborbit2 1:2.14.19-4 in eoan armhf
  liborbit2 1:2.14.19-4 in eoan i386
  liborbit2 1:2.14.19-4 in eoan ppc64el
  liborbit2 1:2.14.19-4 in eoan s390x
  liborbit2-dev 1:2.14.19-4 in eoan amd64
  liborbit2-dev 1:2.14.19-4 in eoan arm64
  liborbit2-dev 1:2.14.19-4 in eoan armhf
  liborbit2-dev 1:2.14.19-4 in eoan i386
  liborbit2-dev 1:2.14.19-4 in eoan ppc64el
  liborbit2-dev 1:2.14.19-4 in eoan s390x
  orbit2 1:2.14.19-4 in eoan amd64
  orbit2 1:2.14.19-4 in eoan arm64
  orbit2 1:2.14.19-4 in eoan armhf
  orbit2 1:2.14.19-4 in eoan i386
  orbit2 1:2.14.19-4 in eoan ppc64el
  orbit2 1:2.14.19-4 in eoan s390x
  orbit2-nameserver 1:2.14.19-4 in eoan amd64
  orbit2-nameserver 1:2.14.19-4 in eoan arm64
  orbit2-nameserver 1:2.14.19-4 in eoan armhf
  orbit2-nameserver 1:2.14.19-4 in eoan i386
  orbit2-nameserver 1:2.14.19-4 in eoan ppc64el
  orbit2-nameserver 1:2.14.19-4 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #890459
1 package successfully removed."
1825972,2019-06-20 19:46:59 UTC,"Removing packages from eoan:
 gnome-vfs 1:2.24.4-6.1ubuntu2 in eoan
  libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan amd64
  libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan arm64
  libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan armhf
  libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan i386
  libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan ppc64el
  libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan s390x
  libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan amd64
  libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan arm64
  libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan armhf
  libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan i386
  libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan ppc64el
  libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan s390x
  libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan amd64
  libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan arm64
  libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan armhf
  libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan i386
  libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan ppc64el
  libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan s390x
  libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan amd64
  libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan arm64
  libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan armhf
  libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan i386
  libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan ppc64el
  libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan s390x
  libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan amd64
  libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan arm64
  libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan armhf
  libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan i386
  libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan ppc64el
  libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan s390x
  libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan amd64
  libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan arm64
  libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan armhf
  libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan i386
  libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan ppc64el
  libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #893922
1 package successfully removed."
1825972,2019-06-20 19:45:05 UTC,"Removing packages from eoan:
 libbonobo 2.32.1-3 in eoan
  libbonobo2-0 2.32.1-3 in eoan amd64
  libbonobo2-0 2.32.1-3 in eoan arm64
  libbonobo2-0 2.32.1-3 in eoan armhf
  libbonobo2-0 2.32.1-3 in eoan i386
  libbonobo2-0 2.32.1-3 in eoan ppc64el
  libbonobo2-0 2.32.1-3 in eoan s390x
  libbonobo2-bin 2.32.1-3 in eoan amd64
  libbonobo2-bin 2.32.1-3 in eoan arm64
  libbonobo2-bin 2.32.1-3 in eoan armhf
  libbonobo2-bin 2.32.1-3 in eoan i386
  libbonobo2-bin 2.32.1-3 in eoan ppc64el
  libbonobo2-bin 2.32.1-3 in eoan s390x
  libbonobo2-common 2.32.1-3 in eoan amd64
  libbonobo2-common 2.32.1-3 in eoan arm64
  libbonobo2-common 2.32.1-3 in eoan armhf
  libbonobo2-common 2.32.1-3 in eoan i386
  libbonobo2-common 2.32.1-3 in eoan ppc64el
  libbonobo2-common 2.32.1-3 in eoan s390x
  libbonobo2-dev 2.32.1-3 in eoan amd64
  libbonobo2-dev 2.32.1-3 in eoan arm64
  libbonobo2-dev 2.32.1-3 in eoan armhf
  libbonobo2-dev 2.32.1-3 in eoan i386
  libbonobo2-dev 2.32.1-3 in eoan ppc64el
  libbonobo2-dev 2.32.1-3 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #885770
1 package successfully removed."
1825972,2019-06-20 19:43:32 UTC,"Removing packages from eoan:
 libbonoboui 2.24.5-4 in eoan
  libbonoboui2-0 2.24.5-4 in eoan amd64
  libbonoboui2-0 2.24.5-4 in eoan arm64
  libbonoboui2-0 2.24.5-4 in eoan armhf
  libbonoboui2-0 2.24.5-4 in eoan i386
  libbonoboui2-0 2.24.5-4 in eoan ppc64el
  libbonoboui2-0 2.24.5-4 in eoan s390x
  libbonoboui2-bin 2.24.5-4 in eoan amd64
  libbonoboui2-bin 2.24.5-4 in eoan arm64
  libbonoboui2-bin 2.24.5-4 in eoan armhf
  libbonoboui2-bin 2.24.5-4 in eoan i386
  libbonoboui2-bin 2.24.5-4 in eoan ppc64el
  libbonoboui2-bin 2.24.5-4 in eoan s390x
  libbonoboui2-common 2.24.5-4 in eoan amd64
  libbonoboui2-common 2.24.5-4 in eoan arm64
  libbonoboui2-common 2.24.5-4 in eoan armhf
  libbonoboui2-common 2.24.5-4 in eoan i386
  libbonoboui2-common 2.24.5-4 in eoan ppc64el
  libbonoboui2-common 2.24.5-4 in eoan s390x
  libbonoboui2-dev 2.24.5-4 in eoan amd64
  libbonoboui2-dev 2.24.5-4 in eoan arm64
  libbonoboui2-dev 2.24.5-4 in eoan armhf
  libbonoboui2-dev 2.24.5-4 in eoan i386
  libbonoboui2-dev 2.24.5-4 in eoan ppc64el
  libbonoboui2-dev 2.24.5-4 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #885769
1 package successfully removed."
1825972,2019-05-09 12:49:51 UTC,Added tasks for the remainder of the old gnome/bonobo stack.
1825972,2019-05-09 17:45:58 UTC,New chromium has just migrated to release pocket.
1825972,2019-05-07 23:24:08 UTC," reverse-depends src:libgnome-keyring -b
Reverse-Build-Depends
=====================
* chromium-browser              (for libgnome-keyring-dev)
* libgnomeui                    (for libgnome-keyring-dev)"
1825972,2019-05-07 23:21:42 UTC,"Removing packages from eoan:
 libgnomeui 2.24.5-3.2 in eoan
  libgnomeui-0 2.24.5-3.2 in eoan amd64
  libgnomeui-0 2.24.5-3.2 in eoan arm64
  libgnomeui-0 2.24.5-3.2 in eoan armhf
  libgnomeui-0 2.24.5-3.2 in eoan i386
  libgnomeui-0 2.24.5-3.2 in eoan ppc64el
  libgnomeui-0 2.24.5-3.2 in eoan s390x
  libgnomeui-0-dbg 2.24.5-3.2 in eoan amd64
  libgnomeui-0-dbg 2.24.5-3.2 in eoan arm64
  libgnomeui-0-dbg 2.24.5-3.2 in eoan armhf
  libgnomeui-0-dbg 2.24.5-3.2 in eoan i386
  libgnomeui-0-dbg 2.24.5-3.2 in eoan ppc64el
  libgnomeui-0-dbg 2.24.5-3.2 in eoan s390x
  libgnomeui-common 2.24.5-3.2 in eoan amd64
  libgnomeui-common 2.24.5-3.2 in eoan arm64
  libgnomeui-common 2.24.5-3.2 in eoan armhf
  libgnomeui-common 2.24.5-3.2 in eoan i386
  libgnomeui-common 2.24.5-3.2 in eoan ppc64el
  libgnomeui-common 2.24.5-3.2 in eoan s390x
  libgnomeui-dev 2.24.5-3.2 in eoan amd64
  libgnomeui-dev 2.24.5-3.2 in eoan arm64
  libgnomeui-dev 2.24.5-3.2 in eoan armhf
  libgnomeui-dev 2.24.5-3.2 in eoan i386
  libgnomeui-dev 2.24.5-3.2 in eoan ppc64el
  libgnomeui-dev 2.24.5-3.2 in eoan s390x
  libgnomeui-doc 2.24.5-3.2 in eoan amd64
  libgnomeui-doc 2.24.5-3.2 in eoan arm64
  libgnomeui-doc 2.24.5-3.2 in eoan armhf
  libgnomeui-doc 2.24.5-3.2 in eoan i386
  libgnomeui-doc 2.24.5-3.2 in eoan ppc64el
  libgnomeui-doc 2.24.5-3.2 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #885767
1 package successfully removed."
1825972,2019-05-07 23:19:29 UTC,"Removing packages from eoan:
 linsmith 0.99.31-1 in eoan
  linsmith 0.99.31-1 in eoan amd64
  linsmith 0.99.31-1 in eoan arm64
  linsmith 0.99.31-1 in eoan armhf
  linsmith 0.99.31-1 in eoan i386
  linsmith 0.99.31-1 in eoan ppc64el
  linsmith 0.99.31-1 in eoan s390x
Comment: Depends on obsolete libgnomeui, removed from Debian testing; LP: #1825972, Debian bug #885742
1 package successfully removed."
1825972,2019-04-23 11:18:38 UTC,The other packages from LP: #1771031 can probably be removed now too.
1825972,2019-06-20 19:42:39 UTC,"Removing packages from eoan:
 libgnome-keyring 3.12.0-1build1 in eoan
  gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan amd64
  gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan arm64
  gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan armhf
  gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan i386
  gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan ppc64el
  gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan s390x
  libgnome-keyring-common 3.12.0-1build1 in eoan amd64
  libgnome-keyring-common 3.12.0-1build1 in eoan arm64
  libgnome-keyring-common 3.12.0-1build1 in eoan armhf
  libgnome-keyring-common 3.12.0-1build1 in eoan i386
  libgnome-keyring-common 3.12.0-1build1 in eoan ppc64el
  libgnome-keyring-common 3.12.0-1build1 in eoan s390x
  libgnome-keyring-dev 3.12.0-1build1 in eoan amd64
  libgnome-keyring-dev 3.12.0-1build1 in eoan arm64
  libgnome-keyring-dev 3.12.0-1build1 in eoan armhf
  libgnome-keyring-dev 3.12.0-1build1 in eoan i386
  libgnome-keyring-dev 3.12.0-1build1 in eoan ppc64el
  libgnome-keyring-dev 3.12.0-1build1 in eoan s390x
  libgnome-keyring0 3.12.0-1build1 in eoan amd64
  libgnome-keyring0 3.12.0-1build1 in eoan arm64
  libgnome-keyring0 3.12.0-1build1 in eoan armhf
  libgnome-keyring0 3.12.0-1build1 in eoan i386
  libgnome-keyring0 3.12.0-1build1 in eoan ppc64el
  libgnome-keyring0 3.12.0-1build1 in eoan s390x
  libgnome-keyring0-dbg 3.12.0-1build1 in eoan amd64
  libgnome-keyring0-dbg 3.12.0-1build1 in eoan arm64
  libgnome-keyring0-dbg 3.12.0-1build1 in eoan armhf
  libgnome-keyring0-dbg 3.12.0-1build1 in eoan i386
  libgnome-keyring0-dbg 3.12.0-1build1 in eoan ppc64el
  libgnome-keyring0-dbg 3.12.0-1build1 in eoan s390x
Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #892359
1 package successfully removed."
1825973,2019-04-23 15:49:14 UTC,Thank you for your bug report. Do you get the issue very time? Is the icon listed in the overview screen (the one you get my clicking on the activity corner in the top left)? Could you add your journalctl log to the bug after getting the issue?
1825973,2019-04-27 09:53:13 UTC,"Here is syslog: https://paste.ubuntu.com/p/XHM9DymqDK/
And here are messages from Remmina when I ran it from the command line."
1825973,2019-04-30 16:34:16 UTC,"Thank you for your bug report, could you make a screencast showing the issue (or at least a screenshot). Do you close the main windows? How do you open the connection and what options do you select? It works fine here"
1825973,2019-06-30 04:17:41 UTC,[Expired for remmina (Ubuntu) because there has been no activity for 60 days.]
1825974,2019-05-09 09:04:06 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu2.1
1825974,2019-05-09 09:25:58 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu1.18.04.2
1825974,2019-05-09 09:21:46 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu1.18.10.2
1825974,2019-05-09 09:04:19 UTC,"The verification of the Stable Release Update for knockd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1825974,2019-05-08 22:18:04 UTC,bionic:
1825974,2019-04-24 16:15:31 UTC,This bug was fixed in the package knockd - 0.7-1ubuntu3
1825974,2019-05-08 22:04:13 UTC,disco verified using steps from test case:
1825974,2019-04-30 23:01:30 UTC,"Hello Dan, or anyone else affected,"
1825974,2019-04-30 22:58:48 UTC,"Hello Dan, or anyone else affected,"
1825974,2019-04-30 22:53:08 UTC,"Hello Dan, or anyone else affected,"
1825974,2019-04-24 15:15:06 UTC,Sponsored in 'Eoan'
1825974,2019-05-08 22:11:31 UTC,cosmic:
1825975,2019-04-23 11:00:02 UTC,"Application: kicad
Version: (5.1.1)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 32 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 7.3.0 with C++ ABI 1011"
1825975,2019-04-24 05:39:06 UTC,I am voting up also. This is very annoying productivity killer.
1825977,2019-04-27 10:01:24 UTC,"Hmm, I think this would be a cleaner fix if the actual executable names were also capitalised correctly."
1825977,2019-05-13 21:25:40 UTC,"Fixed in revision 3c4f8c1bf7b65c2cfa14b6dc9aaefbeb14643d7d
https://git.launchpad.net/kicad/patch/?id=3c4f8c1bf7b65c2cfa14b6dc9aaefbeb14643d7d"
1825978,2019-04-23 16:50:00 UTC,There seems to be something strange with your httplib library given the following error from VarLogDistupgradeMainlog.txt:
1825978,2019-06-23 04:18:36 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1825980,2019-06-27 04:17:25 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1825980,2019-04-27 13:19:14 UTC,Is this a retina display? Jumping to the lower quarter specifically sounds suspicious.
1825980,2019-04-24 12:57:59 UTC,"I can't recreate this. Do there need to be pending changes (new symbols that need annotating, new nets etc?). Would it be possible to create a screen recording showing the steps to recreate this? Can you upload a project that shows this behaviour?"
1825980,2019-04-27 15:04:53 UTC,1) It's not a retina display.
1825983,2019-04-23 12:17:44 UTC,Seems related to https://bugs.launchpad.net/kubuntu-ppa/+bug/983777
1825983,2019-04-23 19:52:12 UTC,Can you compare the output of the following page when chromium is launched with and without the --proxy-server command-line parameter?
1825983,2019-04-24 06:08:24 UTC,"Doing what you say only shows two buttons: ""Re-apply settings"" and ""Clear bad proxies"". In both versions. There is nothing to compare."
1825983,2019-04-24 06:09:08 UTC,Here the log with command-line proxy
1825983,2019-06-11 17:28:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1825983,2019-06-14 00:13:03 UTC,"In my case, it's ignoring a file:// based pac, which looks to be intentional:"
1825983,2019-07-05 21:20:32 UTC,"This is also not working with a http:// url based pac, which should work."
1825985,2019-08-25 04:17:21 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825985,2019-06-25 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825985,2019-04-23 13:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825985,2019-06-23 04:18:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1825985,2019-06-25 08:32:40 UTC,Can I do something to help?
1825987,2019-04-24 07:49:54 UTC,apport information
1825987,2020-05-10 18:11:25 UTC,"The problem disappeared a few month ago, after a system update, perhaps a kernel update.
Sorry, I can't give any more specific information."
1825987,2019-05-06 06:03:16 UTC,Maybe this one https://github.com/systemd/systemd/issues/11368?
1825987,2019-05-05 17:19:41 UTC,mmm... This bug occurs randomly :-/
1825987,2019-04-24 07:50:12 UTC,apport information
1825987,2019-04-23 13:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1825987,2019-04-24 07:50:06 UTC,apport information
1825987,2019-04-24 07:50:05 UTC,apport information
1825987,2019-04-24 07:50:10 UTC,apport information
1825987,2019-04-24 07:50:03 UTC,apport information
1825987,2019-04-24 07:50:02 UTC,apport information
1825987,2019-04-24 07:50:00 UTC,apport information
1825987,2019-04-24 07:49:58 UTC,apport information
1825987,2019-04-24 07:49:57 UTC,apport information
1825987,2019-04-24 07:49:56 UTC,apport information
1825987,2019-04-24 07:49:55 UTC,apport information
1825987,2019-04-24 07:50:04 UTC,apport information
1825987,2019-04-24 07:50:07 UTC,apport information
1825988,2019-05-03 04:06:57 UTC,PR at https://github.com/charmed-kubernetes/layer-etcd/pull/152
1825988,2019-05-08 13:43:51 UTC,Available in etcd-420 and later.
1825989,2019-04-24 09:44:56 UTC,A workaround is to explicitly add the needed entry to sys.path. That is of course *extremely* unpleasant.
1825989,2020-12-07 12:06:29 UTC,The bug seems to have been resolved in 20.04.
1825990,2019-06-03 11:45:22 UTC,"Thanks Felix. That works good; here's a screenshot:
https://i.imgur.com/XH0rRTG.png"
1825990,2019-12-01 15:32:02 UTC,"As posted below, upstream does not know how to implement 4k autodetection in swing,
but there are options for changing this manually which do work."
1825990,2019-06-03 16:42:56 UTC,"hello Lonnie,"
1825990,2019-06-03 07:52:51 UTC,"hi Lonnie,"
1825990,2019-05-30 14:22:01 UTC,"Upstream has features for controlling menus and tool bar sizes.
The reporter has not responded for a month."
1825990,2019-04-24 13:30:59 UTC,"hello Lonnie,"
1825990,2019-05-30 17:10:34 UTC,It seems that some changes were made.
1825993,2019-07-02 04:17:36 UTC,[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.]
1825993,2019-05-02 16:19:42 UTC,"Stefan, please file a bug on Intel. You shouldn't have to disable bt coex."
1825993,2019-04-29 00:39:58 UTC,"Thanks for the suggestion, Stefan.  I just tried setting bt_coex_active to 0 (and confirmed it took by checking /sys/module/iwlwifi/parameters/bt_coex_active).  Unfortunately I still get the errors."
1825993,2019-04-26 19:52:31 UTC,"I tried the update from git.kernel.org, but no luck.  Still getting microcode errors."
1825993,2019-04-24 15:21:21 UTC,Have you already tested newer firmware to see if it fixes the issue? The latest firmware can be downloaded from here:
1825993,2019-04-24 11:11:26 UTC,You can open a bug on intel.
1825993,2019-04-28 09:35:12 UTC,I experienced this bug as well after update to Ubuntu 19.04.
1825998,2020-08-27 01:06:25 UTC,This has been fixed in the React rebuild
1825999,2020-01-07 11:37:30 UTC,"Reviewed:  https://review.opendev.org/659002
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=fa79fbe252210f966d8d7a085b002ba497620500
Submitter: Zuul
Branch:    master"
1825999,2020-01-07 11:36:57 UTC,"Reviewed:  https://review.opendev.org/659004
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=bfea6cc43f6d75598666bce3252fbcbb262a8775
Submitter: Zuul
Branch:    master"
1825999,2019-12-10 20:08:50 UTC,"We have scenario tests for openstack upgrades, they're just not in the third party CI gates.  I have re-opened and rebased these reviews.  We need to discuss testing approach and continue to drive the bug forward."
1825999,2019-08-28 14:22:09 UTC,"Change abandoned by Chris MacNaughton (icey) (<email address hidden>) on branch: master
Review: https://review.opendev.org/659002"
1825999,2019-05-14 09:46:59 UTC,https://review.opendev.org/659002 and https://review.opendev.org/659004 have been proposed to nova-compute and nova-cloud-controller to resolve this
1825999,2019-05-10 14:22:55 UTC,Marking field-high.
1825999,2019-08-28 14:22:04 UTC,"Change abandoned by Chris MacNaughton (icey) (<email address hidden>) on branch: master
Review: https://review.opendev.org/659004"
1826002,2019-08-24 23:06:22 UTC,See the same situation on my machine. Terminator version: 1.91.
1826003,2019-04-23 15:44:49 UTC,"Thank you for your bug report, it's likely coming software-properties doesn't providing the info needed"
1826003,2019-04-23 16:04:26 UTC,"it seems gnome-software is unable to find info also for all other applications.
may be related to a problem on sources.list"
1826003,2019-04-23 16:59:30 UTC,"problem also selecting 'show details' of an app from launcher. Ubuntu software does not find himself
here my sources.list:
corrado@corrado-HP-p4-ee:~$ cat /etc/apt/sources.list
#deb cdrom:[Ubuntu 19.10 _Eoan EANIMAL_ - Alpha amd64 (20190421)]/ eoan main restricted"
1826003,2019-04-24 05:55:51 UTC,Problem disappeared after today updates
1826003,2020-05-18 13:51:25 UTC,Problem disappeared. changed status to invalid
1826004,2019-10-25 01:24:38 UTC,"I confirm. The problem still exists with Bionic Queens and the latest version of the charm. Workaround helped, thanks!"
1826004,2019-10-03 08:00:59 UTC,"This behavior is still happening for gnocchi with TLS on Bionic Queens.
The work-around is to remove the relation with keystone and re-apply it.
Could someone re-open the bug?"
1826004,2019-05-16 20:17:05 UTC,"This does appear to be that the checks are deployed expecting http but the service listens https.  Interestingly, if we mangle the config-changed hook to re-write the checks entirely, the services are written correctly the second time around.  I suspect therefore that this is a function of the endpoints not being registered https first time round, and the charm doesn't re-read the catalog once it's generated the checks the first time."
1826004,2019-05-16 10:14:45 UTC,I experienced the same with SSL on a Bionic/Queens deployment with Vault enabled. The workaround was to enforce re-rendering of nrpe checks with:
1826004,2019-04-23 16:53:39 UTC,looks like the added url options for barbican and gnocchi that expect Unauthorized and x-openstack-request-id are causing failure:
1826005,2019-05-29 18:07:07 UTC,"It looks like this is the same issue as https://forum.snapcraft.io/t/snap-works-as-strict-devmode-not-as-classic/5989, and the solution posted there works. For completion's sake, the solution is"
1826005,2019-08-24 13:56:14 UTC,I think this can be closed. This snap no longer exists in order to triage this.
1826005,2019-08-24 16:11:18 UTC,"Sorry, the snap got shuffled around into `juju-helpers`. The problem is fixed over there due to the above-mentioned fix of running it as `./bin/bin-name`."
1826007,2019-06-03 12:29:35 UTC,"You are correct for EBS (that documentation links specifically to EBS boot volume considerations).  I do not believe this is correct for AMIs with instance-store backed root disks.  We had investigated this previously because we would like to support larger root volumes and we can check again, but we would not want to see the instance-store and ebs AMIs diverge.  This would be a change for a future release as it would be inappropriate to change this for users of existing releases."
1826009,2020-08-07 15:04:54 UTC,This was fixed in https://bugs.launchpad.net/charm-etcd/+bug/1852676 (https://github.com/charmed-kubernetes/layer-etcd/pull/165) which was released with 1.17
1826009,2020-08-07 15:05:56 UTC,"For clarification, the charm now installs the latest version available at the time of deploy and pins to that version's track, so major ver upgrades requires the config change."
1826010,2020-10-22 16:49:17 UTC,"We performed the test with 50 LIFs and the result is the same: no error. We might need more information to reproduce this, such as the client's openstack version and the error's complete traceback."
1826010,2020-10-20 17:24:33 UTC,All I can suggest is making 47 more LIFs and setting max_page_length to 50 like the customer had when they ran into the problem.
1826010,2020-10-20 12:00:25 UTC,"Hi, we tried to reproduce this on both python3 and python2 environments using the latest and queens devstack releases respectively and it didn't happen.
We set the max_page_length to 3 having 3 LIFs:"
1826010,2020-10-20 12:12:16 UTC,"I don't see a max_page_length in the API call, so I don't know what that will do.  To reproduce it with 3 lifs you need to send the API call with ""<max-records>3</max-records>"" so it will only return 3 records.  It should make another call to get 3 more and return a null value that Cinder will fail on."
1826010,2020-10-13 16:46:27 UTC,Can we have more information on how to reproduce this?
1826010,2020-10-20 13:26:32 UTC,"From NetApp driver the API argument ""max-records"" is passed using max_page_length, like so:"
1826012,2019-08-19 08:01:58 UTC,Does the date picker mean calendar widget for selecting the date?
1826013,2020-05-21 13:18:36 UTC,Is there any fix to this bug?  I am seeing the same issue.
1826014,2019-04-23 16:21:02 UTC,"Changed my mind, I think it's a high, it also messed with arcs in corners of boards (probably more common than circles)."
1826014,2019-04-23 16:06:42 UTC,"Confirmed! Definitely there should be a ""disco bug"" award for this report!"
1826014,2019-04-23 16:07:42 UTC,"I'm calling it a medium, as, as reported by the submitter, at least you can delete/change layer of the Edge.Cuts and then put it back later."
1826015,2020-05-28 04:36:32 UTC,Fixed in https://github.com/canonical-web-and-design/maas-ui/pull/962
1826016,2019-04-24 21:26:28 UTC,apport information
1826016,2019-04-24 21:26:31 UTC,apport information
1826016,2019-04-24 21:26:32 UTC,apport information
1826016,2019-04-24 21:26:33 UTC,apport information
1826016,2019-04-24 21:26:37 UTC,apport information
1826016,2019-04-24 21:26:35 UTC,apport information
1826016,2019-04-24 21:26:27 UTC,apport information
1826016,2019-04-24 21:26:40 UTC,apport information
1826016,2019-04-24 21:26:21 UTC,apport information
1826016,2019-04-24 21:26:43 UTC,apport information
1826016,2019-04-24 21:26:46 UTC,apport information
1826016,2019-04-24 21:26:47 UTC,apport information
1826016,2019-04-24 21:26:57 UTC,apport information
1826016,2019-04-24 21:27:49 UTC,apport information
1826016,2019-06-24 04:17:24 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1826016,2019-07-17 11:31:01 UTC,Would it be possible to test if the issue also happens on 64bit Ubuntu?
1826016,2019-04-24 21:26:41 UTC,apport information
1826016,2019-04-24 21:26:19 UTC,apport information
1826016,2019-04-24 21:21:56 UTC,apport information
1826016,2019-04-24 21:26:16 UTC,apport information
1826016,2019-04-24 21:26:18 UTC,apport information
1826016,2019-04-23 16:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826016,2019-04-24 21:21:45 UTC,apport information
1826016,2019-04-24 21:21:49 UTC,apport information
1826016,2019-04-24 21:21:50 UTC,apport information
1826016,2019-04-24 21:21:58 UTC,apport information
1826016,2019-04-24 21:22:00 UTC,apport information
1826016,2019-04-24 21:22:01 UTC,apport information
1826016,2019-04-24 21:21:47 UTC,apport information
1826016,2019-04-24 21:22:06 UTC,apport information
1826016,2019-04-24 21:22:09 UTC,apport information
1826016,2019-04-24 21:22:10 UTC,apport information
1826016,2019-04-24 21:22:12 UTC,apport information
1826016,2019-04-24 21:22:14 UTC,apport information
1826016,2019-04-24 21:22:45 UTC,apport information
1826016,2019-04-24 21:22:16 UTC,apport information
1826016,2019-04-24 21:22:18 UTC,apport information
1826016,2019-04-24 21:22:04 UTC,apport information
1826017,2019-04-23 18:05:11 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655225"
1826017,2019-04-23 22:00:57 UTC,"Reviewed:  https://review.opendev.org/655225
Committed: https://git.openstack.org/cgit/openstack/charm-designate-bind/commit/?id=58054337d52496d81c6ffc545f815bd466482642
Submitter: Zuul
Branch:    master"
1826018,2019-04-25 16:23:55 UTC,I think this issue may be related to https://github.com/juju/charm-helpers/issues/312
1826018,2019-07-03 12:56:05 UTC,Change is pending to be released in the charm store.
1826024,2019-05-07 15:20:30 UTC,"Issue to note in x86_64 (aws):
  libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only spotted on t2.small, passed on the rest"
1826024,2019-05-14 19:09:39 UTC,This bug was fixed in the package linux-aws - 4.4.0-1083.93
1826026,2019-04-23 17:40:00 UTC,"There is a lot of ambiguity as to what this password actually does. In my experience, it simply sets the MOK key password for the MOK key installation on the next reboot. That said, Ubiquity does not expressly state exactly what this password does, so some clarification on this is definitely essential."
1826026,2019-04-23 17:17:13 UTC,"I also suggest the the consequences of *not* knowing this password are described somewhere. I saw this screen, put in a password, and eventually hit 'cancel', but mmx64.efi was loaded on next boot anyway. I don't know if I can remember the password I put in here and don't know if I might need to destroy a filesystem in the future."
1826026,2019-04-23 17:38:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826028,2019-05-06 11:17:05 UTC,"4.4.0-1045.51 - kvm
Regression test CMPL, RTB."
1826028,2019-05-14 19:10:32 UTC,This bug was fixed in the package linux-kvm - 4.4.0-1046.52
1826029,2019-05-03 09:08:14 UTC,Hardware Certification have begun testing this -proposed kernel.
1826029,2019-05-10 04:52:11 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/tGZ9D1HN/960-pi2-kernel-440-1108116-87"
1826029,2019-05-10 09:26:55 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.4.0-1108.116/raspi2-4.4-proposed-published.html"
1826029,2019-05-14 19:10:46 UTC,This bug was fixed in the package linux-raspi2 - 4.4.0-1109.117
1826030,2019-05-08 11:27:25 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.4.0-1112.117/snapdragon-4.4-proposed-published.html"
1826030,2019-05-14 19:10:53 UTC,This bug was fixed in the package linux-snapdragon - 4.4.0-1113.118
1826030,2019-05-03 09:08:26 UTC,Hardware Certification have begun testing this -proposed kernel.
1826030,2019-04-30 11:22:49 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/Yz8ueCux/959-dragonboard-kernel-440-1112117-87"
1826032,2019-05-14 03:13:37 UTC,"4.4.0-1009.11 - fips
Regression test CMPL, RTB."
1826034,2019-05-13 12:22:56 UTC,regression-testing
1826034,2019-05-14 19:52:05 UTC,This bug was fixed in the package linux-aws - 4.4.0-1044.47
1826035,2019-05-13 06:51:01 UTC,"4.4.0-147.173~14.04.1 - generic
Regression test CMPL, RTB."
1826035,2019-05-14 19:52:28 UTC,This bug was fixed in the package linux-lts-xenial - 4.4.0-148.174~14.04.1
1826036,2019-04-30 11:22:59 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/OBS6iU0E/961-pc-kernel-440-147173-207"
1826036,2019-05-03 09:08:39 UTC,Hardware Certification have begun testing this -proposed kernel.
1826036,2019-05-09 07:51:45 UTC,Verification testing completed successfully with the Xenial kernel in -proposed (https://kernel.ubuntu.com/reports/sru-report.html).
1826036,2019-05-10 09:55:40 UTC,"4.4.0-147.173 - generic
Regression test CMPL, RTB."
1826036,2019-05-10 10:00:59 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-147.173/xenial-proposed-published.html"
1826036,2019-05-14 19:08:52 UTC,This bug was fixed in the package linux - 4.4.0-148.174
1826037,2019-05-06 02:10:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826038,2019-09-25 11:00:25 UTC,This issue was fixed in the openstack/solum-tempest-plugin 1.1.0 release.
1826040,2019-10-07 10:04:08 UTC,The same issue seems to be present in Ubuntu 19.10 beta as well.
1826040,2019-10-14 08:00:54 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826040,2019-10-14 08:51:58 UTC,Possibly related: https://gitlab.gnome.org/GNOME/nautilus/issues/448
1826040,2019-10-14 09:34:41 UTC,"Setting has wontfix for nautilus, they remove support to .desktop link type and don't seem interested to add that backb"
1826040,2019-10-15 13:53:34 UTC,"Untagging, Laney said he would fix it if there is a respin and if there is not then there is little point doing a SRU since it's an installer change"
1826040,2019-10-15 16:38:27 UTC,We just unseeded example-content so it's not important for the live session any more; this bug is still valid in itself...
1826040,2019-04-30 15:09:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826043,2019-05-03 16:23:38 UTC,"Thank you for your bug report. Indeed, that's reported upstream as https://gitlab.gnome.org/GNOME/gnome-calendar/issues/312"
1826044,2019-06-23 04:18:59 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1826045,2019-05-28 15:08:37 UTC,"Even in the case that you are operating on a remote server, the remote pcsd client needs pacemaker/corosync scripts. Without that, even the very basic commands won't work:"
1826045,2019-06-03 20:57:36 UTC,see also related corosync bug 1831492
1826045,2019-05-28 19:31:16 UTC,Going back to my previous list:
1826045,2019-05-28 14:55:15 UTC,Oh maybe 'pcs' can be operated from a remote server for pcs and provides a web UI.
1826045,2019-05-28 20:16:44 UTC,"On Tue, May 28, 2019 at 07:31:16PM -0000, Eric Desrochers wrote:

> Seems like 2) and 3) are now covered, we just need to come to an
> agreement about what we do next with Disco for 1).
"
1826045,2019-05-28 14:21:37 UTC,"On Tue, May 28, 2019 at 01:30:48PM -0000, Eric Desrochers wrote:

> At first I thought it has something to do with the use of 'Recommends:
> pacemaker (>= 2.0)' which is not as strong/powerful as 'Depends:'
"
1826045,2019-05-28 13:30:48 UTC,At first I thought it has something to do with the use of 'Recommends: pacemaker (>= 2.0)' which is not as strong/powerful as 'Depends:'
1826045,2019-05-10 18:28:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826045,2019-05-28 11:02:24 UTC,Thank you for working on this.
1826045,2019-05-28 14:47:48 UTC,"I don't think so, seems like 'pcs' is the 'Pacemaker Configuration System'.
I can't see how 'pcs' can be useful outside the pacemaker/corosync context."
1826046,2019-04-23 19:32:40 UTC,"SORRY Rebooting the system restores the correct display, restarting the disk utility did not help. Any action in the extended partitions distorts the display of those logical partitions."
1826047,2019-04-24 17:18:04 UTC,Suspicion is the sysinv failure is tied to recent sanity failures.  This LP will be used to focus on recovery when sysinv dies during stx-openstack apply.
1826047,2019-04-24 17:20:08 UTC,Marking as release gating; the system should recover on an application-apply failure such that a 2nd attempt to apply is possible even if stuck in 'retrieving docker images' state.
1826047,2019-04-24 17:21:19 UTC,Assigning to Cindy to identify a developer who can work on improving recovery when an application-apply fails leaving the system in 'retrieving docker images' state.
1826047,2019-06-11 07:57:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/664521"
1826047,2019-07-09 00:40:00 UTC,"Change abandoned by chen haochuan (<email address hidden>) on branch: master
Review: https://review.opendev.org/664521"
1826047,2019-07-09 00:40:09 UTC,"duplicate with.
https://bugs.launchpad.net/starlingx/+bug/1833323"
1826047,2019-07-17 04:45:41 UTC,"Change abandoned by chen haochuan (<email address hidden>) on branch: master
Review: https://review.opendev.org/664521"
1826047,2019-08-23 17:51:47 UTC,Duplicate bug is fixed in master and the r/stx.2.0 branch. Marking this as Fix Released to match.
1826047,2020-01-13 21:27:59 UTC,"This was marked duplicate to LP-1833323 which has already been retested and closed.
Closing this one."
1826050,2019-12-05 19:11:34 UTC,In my case it turned out this was because I had acpi=off in /etc/default/grub
1826050,2019-12-05 18:56:24 UTC,I have a similar problem on 19.04
1826050,2019-05-27 05:24:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826050,2019-07-25 04:10:43 UTC,"Hey all,"
1826051,2019-07-27 04:17:17 UTC,[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]
1826051,2019-05-27 05:43:53 UTC,"On Mon, May 27, 2019 at 5:25 AM Paul Hawkins <email address hidden> wrote:

>
> Just starting to use QEMU/KVM VMs on Ubuntu 18.04.1 Desktop.  Both host
> and quest are same release.
"
1826051,2019-05-27 03:17:46 UTC,Just starting to use QEMU/KVM VMs on Ubuntu 18.04.1 Desktop.  Both host and quest are same release.
1826051,2019-05-03 20:51:29 UTC,"Hi Christian,"
1826051,2019-05-06 06:05:07 UTC,"@Corey M.: Very odd/uncommon, but unfortunately with nothing actionable/fixable identified yet.
If you find anything more that could help leading us to the root cause and maybe a fix let me know."
1826051,2019-04-25 19:28:47 UTC,"Hi Christian,"
1826051,2019-04-25 06:59:50 UTC,@James/Corey: I subscribed you in case you have heard on other places about migrations from trusty->bionic level qemu (with ceph) that end up with a stuck guest that has some vCPUs on 100% and no more responds.
1826051,2019-04-25 06:58:36 UTC,"Thanks for the data so far,
the guest does not look very ""special"" other than the ceph storage and that looks fine at a first glance."
1826051,2019-04-24 15:44:09 UTC,"Hi Christian,"
1826051,2019-04-23 23:19:06 UTC,"Hi Corey,
that is bad news - I literally migrated 10s of thousands of VMs T->B now and newer hit that so far."
1826051,2019-04-26 06:16:46 UTC,"""This is new to me, so hopefully it's correct."""
1826052,2019-04-24 09:56:11 UTC,"This seems to be a duplicate of bug 123054, which means it's fixed, and the fix will be part of 6.2.4."
1826052,2019-05-26 08:55:28 UTC,6.2.4 released to Eoan.
1826052,2019-04-29 08:48:19 UTC,Upstream fix is scheduled for 6.2.4 (Week 21)
1826052,2019-04-24 09:35:04 UTC,"Created attachment 150969
Document open in 6.2.3.2"
1826052,2019-04-24 09:31:33 UTC,"Description:
Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826052"
1826052,2019-04-24 09:32:24 UTC,"Created attachment 150967
Formatted document"
1826052,2019-04-23 19:55:28 UTC,"Thanks for the report Eamon.
Would you be able to share such a document, so that others can test, confirm and investigate the problem?"
1826052,2019-04-24 08:36:45 UTC,This looks to be an upstream bug.
1826052,2019-04-23 20:15:26 UTC,It's pretty gigantic document (big images) ans not ideal for sharing. I will see if I can get the same outcome with a lighter document.
1826052,2019-04-24 09:34:33 UTC,"Created attachment 150968
Document open in 6.1.5.2"
1826055,2019-04-23 20:52:10 UTC,Thanks for your report!
1826055,2019-04-23 21:16:59 UTC,"Thanks for the clarification. It's not obvious that the recommended changes have the desired effect, since I created the /etc/lightdm/lightdm.conf.d/50-manual-login.conf file and restarted the computer, but I still see a list of local users plus a domain user that logged in. If I have understood the help page correctly, this change is supposed to remove user names from the login screen. I confirmed that the permissions and ownership of /etc/lightdm/lightdm.conf.d/50-manual-login.conf match those of /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf."
1826055,2019-04-23 22:37:38 UTC,The line
1826055,2020-04-20 21:13:22 UTC,"> should make sure that an option to type a non-listed username is available.
"
1826056,2019-04-27 23:59:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826056,2019-04-28 00:32:54 UTC,"Ubuntu 19.04 comes with gnome shell extension: ""desktop icons"". In previous versions of Ubuntu desktop icons was provided by nautilus, but new version of nautilus (3.32) lost desktop icons functionality."
1826056,2020-01-13 17:19:50 UTC,Applies to 19.10 as well
1826059,2019-11-13 21:34:50 UTC,"I'm pretty sure this is fixed now, please reopen if not."
1826059,2019-08-06 04:17:12 UTC,"Same issue here. Installer crashes and restarts when I hit ""Save"" once finished inputting manual network settings. Switching to a different subnet I have DHCP on, I am able to pull a valid lease, but selecting ""Info"" to view the lease info from the network screen also crashes the installer."
1826059,2019-04-26 02:15:42 UTC,"The next release of 18.04, 18.04.3 (due in July), will support null networking."
1826063,2019-04-23 23:53:53 UTC,"well, libssl1.1 >= 1.1.1 is available from bionic-proposed, but not yet from bionic-updates."
1826065,2021-01-07 03:55:50 UTC,"Closing this bug as this is a BIOS issue, plus 19.04 EOL"
1826065,2019-06-10 16:12:32 UTC,"  Hello,"
1826065,2019-06-09 19:40:05 UTC,The new BIOS version works for me also !
1826065,2019-06-08 19:50:30 UTC,I had a chance to test this and with the updated BIOS I can boot without any problems.
1826065,2019-06-06 21:35:28 UTC,"A new BIOS version (304) was released for the UX433FN a couple of days ago and that seems to fix the problem, at least I can boot newer Fedora kernels, which I couldn't before the BIOS update. I don't have a bootable Disco Dingo USB stick at hand, but maybe somebody else can try?"
1826065,2019-06-06 10:13:02 UTC,"No it doesn't change anything.
But by adding acpi=off, we can see some logs, but nothing that help."
1826065,2019-06-06 06:29:06 UTC,"Does kernel parameter ""dis_ucode_ldr"" help?"
1826065,2019-05-20 17:37:51 UTC,"Same problem with Fedora, starting there with kernel 5.0.14:"
1826065,2019-05-20 07:47:17 UTC,"More information part II :
I retry with Ubuntu 18.10, live boot and install => OK Kernel 4.15 but got CPU stuck :(
Reboot with nomodeset and did apt upgrade => KO stuck at boot with the lovely purple screen, kernel 4.18.0.20. Seems to be related to initram disk and kernel. How to see any messages ?"
1826065,2019-05-19 15:50:20 UTC,"More information :
after a lot of test the most stable configuration was with Ubuntu 18.04.2.
First I tried with fresh install with Fedora 30 kernel 5.0.6-300 which was working natively but after upgrading to kernel 5.0.16-301 same kind of problem with the boot. Stuck after booting with black screen.
So I decided to restart a fresh install with Ubuntu 18.04.2 LTS, thinking that a LTS should be more stable. Installation goes right (except the shutdown which stuck, manually shutdown did the job).
I restart and everything goes Ok
Then I upgrade Ubuntu packages (not upgrading to superior version of Ubuntu) and restart with kernel 4.18.0.20 and still OK.
Now installing nvidia property driver (nouveau is not well adapted to IGP + dedicated GPU, prime support), then I restart => OK
All I wanted is to save power consumption too, so I set in the nvidia profile to use Intel IGP then I restart => KO stuck on purple screen.
After a lot of search and try I found the good settings to boot : nomodset argument to kernel booting and delete the splash and quiet option. Since every boot seems to be stable.
My configuration :
Ubuntu LTS 18.04.2 up to date.
Asus Zenbook Pro 14 UX433FN
Intel Core i7-8565U CPU @1.80GHz x 8
Graphic card Intel HD Graphics (Whiskey Lake 3x8 GT2)"
1826065,2019-06-05 21:44:20 UTC,"Related to this bug :
https://bugs.launchpad.net/ubuntu/disco/+source/linux/+bug/1824216"
1826065,2019-04-30 12:47:04 UTC,"Same problem for me with Asus UX433FN.
Work fine with Kernel 5.0 on Ubuntu 18.10, but not on Uvuntu 19.04.
Maybe because of Wayland...
(This computer has 2 Graphics cards;
On previous Ubuntu version, I used nouveau.modeset=0)"
1826065,2019-04-25 07:16:33 UTC,"Yes, currently running 18.10 with mainline kernel 5.0.8 without any problems."
1826065,2019-04-25 04:31:50 UTC,Possible to install 18.10 and find out if latest mainline kernel fixes the issue?
1826065,2019-04-24 22:28:45 UTC,Mine is an Asus Zenbook 14 UX433FN
1826065,2019-04-24 21:51:00 UTC,"Same issue here, I'm on a ASUS Zenbook 15 UX533FD. Also tried every combination stated by @dunix-a with no luck."
1826065,2019-04-24 07:27:45 UTC,"Unfortunately not. I tried ""nomodeset""."
1826065,2019-04-24 07:13:33 UTC,"Does ""Safe Graphics"" mode help?"
1826065,2019-04-23 23:10:54 UTC,"I cannot add the missing log files because I cannot boot the system - setting to ""Confirmed"" as per comment #4"
1826065,2019-04-23 23:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826065,2019-04-23 22:53:54 UTC,"Oh, and I have tried with and without Secure Boot enabled."
1826065,2019-05-17 13:06:11 UTC,"   Hello All,"
1826066,2019-04-24 12:33:39 UTC,A few questions to help clarify things if you don't mind:
1826066,2019-04-24 20:39:21 UTC,And it looks like the output you are running the vpn-agent?  Does this happen if you just run the regular l3-agent?
1826066,2019-05-23 10:04:01 UTC,"1. This is openstack ocata version(with some additional patches from latest neutron version)
2. I haven't tried yet though it looks like it's easy enough
3. I'll try to reproduce and get some logs later"
1826066,2019-07-23 04:17:21 UTC,[Expired for neutron because there has been no activity for 60 days.]
1826068,2019-04-23 23:36:13 UTC,Additional information:
1826069,2019-04-27 09:42:25 UTC,"probably same as
#1825817 menulibre wont start after upgrade to 19.04"
1826069,2019-05-14 02:25:44 UTC,"… and #1825817 same as #1825213, #1817885"
1826072,2019-07-30 06:10:48 UTC,"In my case it does not rebuild.
It builds changed files if there are any but that's a feature."
1826072,2019-09-29 04:17:37 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1826074,2019-12-23 11:12:04 UTC,"ASDF still has not been updated, current version is 3.3.1.3 which is nearly two years old now. Would someone be open to a patch to (try) to update it ?"
1826074,2019-12-23 12:53:46 UTC,"Each time ASDF is updated there are problems cropping up, some of which are not bugs but backwards incompatible changes. When somebody updates SBCL they may not want to update ASDF at the same time. With it being a third party project we cannot direct the same attention to quality or have the same policy towards backwards compatibility.
If anyone wants to update ASDF they can do it locally, to any version at any time, by loading it before the one bundled with SBCL."
1826074,2019-12-23 13:08:50 UTC,"@stassats I'm not sure I understand. Since SBCL bundles ASDF, it becomes responsible for updating it. Of course never updating works, but then what is the point in bundling it?"
1826074,2019-12-23 13:44:11 UTC,"According to historic data, ASDF updates tend to break various unrelated things for many people. Therefore, AFAIK, SBCL prefers to stay on an older version of ASDF and support it instead of jumping onto the newest one in order to avoid getting hit in the face with various ASDF breakages."
1826074,2019-12-23 14:33:42 UTC,"> but then what is the point in bundling it?
"
1826074,2019-12-23 18:06:25 UTC,I'll quote contrib/asdf/README.SBCL:
1826074,2019-12-23 19:57:59 UTC,"Easy for you to say, you're not the one who has to face all the ""Hi, I updated SBCL and now my program doesn't build anymore""."
1826074,2019-12-23 20:44:38 UTC,"I understand where you are coming from, but what is the alternative ? From what I can see, the ASDF repository is maintained, so if SBCL decides not to update anymore, it means one cannot rely on ASDF anymore (and no bundling your own  ASDF in your systems is not a viable option because of the potential version conflicts; you can only load one single version in an image). In that case, why not announcing it clearly in the next release notes ? It would have really bad consequences for lots of people, but at least it would be clear."
1826074,2019-12-28 17:29:46 UTC,"You can update your own ASDF at any time, if your .asd depend on something new, insert a version assertion in them."
1826074,2020-01-12 19:57:15 UTC,I can understand the argument.
1826074,2019-12-23 13:05:53 UTC,"And here is a patch to update to ASDF 3.3.3. I'm not sure why the pull-asdf.sh script only consider major versions, but it's better than nothing."
1826077,2019-12-06 09:33:37 UTC,"For deb installs (as opposed to the snap), I suggest to rebuild https://launchpad.net/ubuntu/focal/amd64/acpica-tools/20191018-1 and dput the source package to our ppas"
1826077,2019-04-24 08:01:56 UTC,Colin gave us the link:
1826077,2019-04-24 07:50:40 UTC,"I'd prefer to bundle the acpidump command into the checkbox snap instead, as we already fo for stress-ng and fwts."
1826077,2019-05-15 13:20:44 UTC,Attached MR brings the acpi tools into the checkbox core snap. This will obviously only help testing of sommerville projects if snap distributed checkbox is used.
1826078,2019-04-24 10:13:21 UTC,"Thank you for your bug report, is there any chance you would also report that upstream on https://gitlab.gnome.org/GNOME/tracker/issues/ ?"
1826078,2019-04-24 10:53:39 UTC,Logged as https://gitlab.gnome.org/GNOME/tracker/issues/94
1826078,2019-04-24 13:48:57 UTC,Thanks
1826078,2019-11-24 07:11:58 UTC,"Response from Gnome folks was to add a "".trackerignore"" file to some of my more unwieldy directories, and then similar to Android's .nomedia files, Tracker will skip indexing those directory trees."
1826079,2019-04-24 05:40:37 UTC,Desired solution:
1826079,2019-07-18 12:42:09 UTC,Please redirect your bug report to the requestsexceptions bug tracker:
1826080,2019-04-24 05:32:47 UTC,"Well, HomeBank exist for decade and... No one just done this original thing, nor reported this. Usually I do think they input numbers by typing, which is faster, or use the import features.
Thanks for reporting anyway, I will have a look."
1826080,2019-04-24 20:00:56 UTC," ?????? ?????? I am a retired computer scientist and I have to tell you ... we
once found an error in an input method that had existed for over 30
years. As for doing original things: Idiot proof systems are impossible.
I am, like many others, VERY TALENTED at being an idiot (or so says my
wife at least)."
1826080,2019-05-13 19:24:45 UTC,Maxime:
1826080,2019-05-14 12:03:06 UTC,"so I was right at first !
thx, changed here and into the changelog as well"
1826081,2019-04-24 13:49:59 UTC,Thanks
1826081,2019-04-24 10:46:00 UTC,It appears someone has logged this upstream as https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/98
1826081,2019-04-24 10:11:35 UTC,"Thank you for your bug report, could you maybe also send it upstream to https://gitlab.gnome.org/World/ShellExtensions/desktop-icons ?"
1826081,2019-04-24 06:24:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826082,2019-04-24 13:13:25 UTC,"Changed the summary because the rotation before placement is a regression. Mirroring of labels was never possible, see https://bugs.launchpad.net/kicad/+bug/1822434"
1826082,2019-04-26 17:00:46 UTC,Fixed in my eemodern branch.
1826085,2019-04-24 20:09:49 UTC,the mesa link is broken
1826085,2019-04-24 20:10:34 UTC,"also, the second part of the kernel commits haven't been sent upstream yet, while ""[PATCH v3 0/9] drm/i915/perf: add OA interrupt support"" was."
1826085,2019-06-11 19:58:54 UTC,"Updating links:
Kernel patch review: https://patchwork.freedesktop.org/series/60916/
Mesa patch review: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/932/
Thanks!"
1826085,2019-10-25 06:02:10 UTC,"mesa 19.2
2b5f30b1d91b98ab27ba (""anv: implement VK_INTEL_performance_query"")"
1826085,2019-10-25 06:32:11 UTC,19.10 shipped with mesa 19.2.1
1826086,2019-04-24 12:44:14 UTC,"SCH_LINE::SetEndPoint(wxPoint const&) sch_line.h:82
SCH_DRAWING_TOOL::doDrawSegments(int, SCH_LINE*) sch_drawing_tool.cpp:982
SCH_DRAWING_TOOL::DrawWire(TOOL_EVENT const&) sch_drawing_tool.cpp:653
decltype(*(std::__1::forward<SCH_DRAWING_TOOL*&>(fp0)).*fp(std::__1::forward<TOOL_EVENT const&>(fp1))) std::__1::__invoke<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*&, TOOL_EVENT const&, void>(int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*&, TOOL_EVENT const&) type_traits:4280
std::__1::__bind_return<int (SCH_DRAWING_TOOL::*)(TOOL_EVENT const&), std::__1::tuple<SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> >, std::__1::tuple<TOOL_EVENT const&>, __is_valid_bind_return<int (SCH_DRAWING_TOOL::*)(TOOL_EVENT const&), std::__1::tuple<SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> >, std::__1::tuple<TOOL_EVENT const&> >::value>::type std::__1::__apply_functor<int (SCH_DRAWING_TOOL::*)(TOOL_EVENT const&), std::__1::tuple<SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> >, 0ul, 1ul, std::__1::tuple<TOOL_EVENT const&> >(int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), std::__1::tuple<SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> >&, std::__1::__tuple_indices<0ul, 1ul>, std::__1::tuple<TOOL_EVENT const&>&&) functional:2216
std::__1::__bind_return<int (SCH_DRAWING_TOOL::*)(TOOL_EVENT const&), std::__1::tuple<SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> >, std::__1::tuple<TOOL_EVENT const&>, __is_valid_bind_return<int (SCH_DRAWING_TOOL::*)(TOOL_EVENT const&), std::__1::tuple<SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> >, std::__1::tuple<TOOL_EVENT const&> >::value>::type std::__1::__bind<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> const&>::operator()<TOOL_EVENT const&>(TOOL_EVENT const&) functional:2249
decltype(std::__1::forward<std::__1::__bind<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> const&>&>(fp)(std::__1::forward<TOOL_EVENT const&>(fp0))) std::__1::__invoke<std::__1::__bind<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> const&>&, TOOL_EVENT const&>(std::__1::__bind<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> const&>&, TOOL_EVENT const&) type_traits:4339
int std::__1::__invoke_void_return_wrapper<int>::__call<std::__1::__bind<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> const&>&, TOOL_EVENT const&>(std::__1::__bind<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> const&>&, TOOL_EVENT const&) __functional_base:318
std::__1::__function::__func<std::__1::__bind<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> const&>, std::__1::allocator<std::__1::__bind<int (SCH_DRAWING_TOOL::*&)(TOOL_EVENT const&), SCH_DRAWING_TOOL*, std::__1::placeholders::__ph<1> const&> >, int (TOOL_EVENT const&)>::operator()(TOOL_EVENT const&) functional:1562
std::__1::function<int (TOOL_EVENT const&)>::operator()(TOOL_EVENT const&) const functional:1913
..."
1826086,2019-04-24 13:43:42 UTC,Fixed in 5e556f0c6a5682bcb4e519d0a8b8a7b3152766b7.
1826092,2019-04-26 14:39:47 UTC,"I think we'd want this to be configurable, fwiw. I think assuming we want to redirect http to https is fine as long as there's an option to disable that."
1826103,2020-07-03 19:51:01 UTC,"------- Comment From <email address hidden> 2020-07-03 15:41 EDT-------
All Ubuntu version after the 18.04.2 version (18.04.4 is the newest image) has an updated version of PCI IDS database. So, we can close this issue."
1826103,2019-10-29 22:40:04 UTC,"------- Comment From <email address hidden> 2019-10-29 18:36 EDT-------
Dropping to P3 to match S3, as there seems to be no reason for a P2 designation."
1826103,2019-04-24 13:51:14 UTC,Default Comment by Bridge
1826103,2019-04-24 13:49:54 UTC,Default Comment by Bridge
1826103,2019-04-24 13:49:40 UTC,"------- Comment From <email address hidden> 2019-04-24 09:41 EDT-------
Changed Target milestone to 18.04.1"
1826103,2019-04-24 08:25:05 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1826103,2019-04-24 13:51:12 UTC,Default Comment by Bridge
1826109,2019-05-09 20:51:14 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1826109,2019-07-09 04:17:25 UTC,[Expired for flatpak (Ubuntu) because there has been no activity for 60 days.]
1826113,2020-06-09 04:51:39 UTC,Please test 20.04.
1826113,2019-04-24 07:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826113,2019-04-25 07:10:02 UTC,"socket(AF_INET, SOCK_RAW, htons(ETH_P_ALL))  this socket creation is not supported in ubuntu 16.04 64 bit and all updated versions"
1826113,2019-04-25 07:50:00 UTC,"bug report:
(gdb) n
Single stepping until exit from function main,
which has no line number information.
Socket creation failed: Invalid argument
socket ret value s= -1, s1=-1[Inferior 1 (process 4991) exited normally]"
1826113,2019-04-25 07:51:20 UTC,I cant able to upload log file. pls. see the error which i got.
1826113,2020-08-09 04:17:20 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1826114,2020-02-06 13:35:28 UTC,Thanks @Hemanth for the quick testing.
1826114,2020-02-06 04:53:29 UTC,"Verified stein on bionic. Project and User pages on Horizon dashboard displayed the corresponding project/user information for the selected domain.
Test environment is built using stsstack-bundle with series bionic and release stein."
1826114,2020-02-05 19:40:19 UTC,"Hello Eduardo, or anyone else affected,"
1826114,2020-01-20 08:30:48 UTC,"Corey, it's ready to be merge/uploaded."
1826114,2020-01-23 11:22:57 UTC,This issue was fixed in the openstack/horizon 15.2.0 release.
1826114,2020-01-22 14:02:46 UTC,"Thanks all, this has been uploaded to the Ubuntu Eoan unapproved queue at:
https://launchpad.net/ubuntu/eoan/+queue?queue_state=1&queue_text=horizon"
1826114,2020-01-23 11:23:57 UTC,This issue was fixed in the openstack/horizon 16.1.0 release.
1826114,2020-02-07 16:05:35 UTC,"Hello Eduardo, or anyone else affected,"
1826114,2020-02-18 13:44:54 UTC,The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1826114,2020-02-10 13:55:27 UTC,"Hello Eduardo, or anyone else affected,"
1826114,2020-02-11 02:40:40 UTC,"Verified train on bionic. Project and User pages on Horizon dashboard displayed the corresponding project/user information for the selected domain.
Test environment is built using stsstack-bundle with series bionic and release train."
1826114,2020-02-17 09:20:53 UTC,"The verification of the Stable Release Update for horizon has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826114,2020-02-17 09:30:54 UTC,This bug was fixed in the package horizon - 3:16.0.0-0ubuntu1.1
1826114,2020-02-18 13:44:57 UTC,"This bug was fixed in the package horizon - 3:16.0.0-0ubuntu1.1~cloud0
---------------"
1826114,2020-02-18 13:48:27 UTC,The verification of the Stable Release Update for horizon has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1826114,2020-02-18 13:48:28 UTC,"This bug was fixed in the package horizon - 3:15.1.1-0ubuntu1.1~cloud1
---------------"
1826114,2020-02-10 04:16:38 UTC,"Verified on ubuntu series eoan. Project and User pages on Horizon dashboard displayed the corresponding project/user information for the selected domain.
Test environment is built using stsstack-bundle with series eoan."
1826114,2020-01-13 15:04:13 UTC,s/Rocky/Stein ^
1826114,2019-12-19 18:37:49 UTC,"Reviewed:  https://review.opendev.org/698866
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=02f4d8ab762cd8587873e832bdcb8e4c1ec0656c
Submitter: Zuul
Branch:    stable/train"
1826114,2020-01-13 15:00:41 UTC,This is fixed in the focal horizon package.
1826114,2019-04-24 06:43:57 UTC,Error
1826114,2019-11-26 04:37:51 UTC,Any news on this bug? It still affects the latest Train release.
1826114,2019-12-09 09:37:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/697962"
1826114,2019-12-11 04:40:16 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/698398"
1826114,2019-12-13 10:21:06 UTC,"Reviewed:  https://review.opendev.org/697962
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=9aca7a94e28589484e312770cc1ee2b8243211bb
Submitter: Zuul
Branch:    master"
1826114,2019-12-13 10:24:07 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/698866"
1826114,2019-12-13 10:24:28 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/698867"
1826114,2019-12-16 23:32:02 UTC,"Reviewed:  https://review.opendev.org/698398
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8fb86b2adbdf4fae63faabc8937728c43c1777d5
Submitter: Zuul
Branch:    master"
1826114,2019-12-17 02:37:09 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/699325"
1826114,2019-12-21 05:54:37 UTC,"Reviewed:  https://review.opendev.org/698867
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f6490abc288f667e9af299264e5eebf7eb931355
Submitter: Zuul
Branch:    stable/stein"
1826114,2020-01-06 15:22:29 UTC,"Reviewed:  https://review.opendev.org/699325
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4d19c56026e51ee496185734b18c896bee93023c
Submitter: Zuul
Branch:    stable/stein"
1826114,2020-01-06 15:22:37 UTC,"Reviewed:  https://review.opendev.org/699324
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=fbce904348db0143cfe5b48c13dc7d52416bf0e4
Submitter: Zuul
Branch:    stable/train"
1826114,2020-01-07 10:34:10 UTC,"Attached debdiffs for eoan, disco, uca train, uca stein."
1826114,2020-01-07 12:28:08 UTC,"The attachment ""lp1826114_eoan.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1826114,2020-01-09 18:47:06 UTC,This issue was fixed in the openstack/horizon 18.0.0 release.
1826114,2019-12-17 02:36:43 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/699324"
1826114,2020-01-13 15:04:00 UTC,Disco is EOL this month so we can fix this directly in Rocky.
1826115,2019-04-24 06:43:03 UTC,"Some log deleting snapshot with ceph 12.2.10:
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server [req-732fd601-576e-4a22-ae0e-35f1b6e62b62 fc26707fe5254e729431d3017250949e d900ebe92343410888fcd10c6c7737fb - - -] Exception during message handling: ImageNotFound: [errno 2] error listing images
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py"", line 163, in _process_incoming
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py"", line 220, in dispatch
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args)
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py"", line 190, in _do_dispatch
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args)
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""<string>"", line 2, in delete_snapshot
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/cinder/coordination.py"", line 151, in _synchronized
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server return f(*a, **k)
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/cinder/volume/manager.py"", line 1205, in delete_snapshot
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server snapshot.save()
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/oslo_utils/excutils.py"", line 220, in _exit_
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server self.force_reraise()
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/oslo_utils/excutils.py"", line 196, in force_reraise
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb)
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/cinder/volume/manager.py"", line 1195, in delete_snapshot
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server self.driver.delete_snapshot(snapshot)
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/cinder/volume/drivers/rbd.py"", line 1335, in delete_snapshot
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server children_list = self._get_children_info(volume, snap_name)
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/cinder/volume/drivers/rbd.py"", line 1156, in _get_children_info
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server children_list = volume.list_children()
2019-04-11 15:00:00.720 100073 ERROR oslo_messaging.rpc.server File ""/usr/lib/python2.7/site-packages/eventle..."
1826120,2019-06-12 14:43:45 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1826120,2019-04-24 07:32:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655341"
1826120,2019-05-28 08:09:27 UTC,"Reviewed:  https://review.opendev.org/655341
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4856a7e52006b1de69f02ee7c9c10084c6b23ca8
Submitter: Zuul
Branch:    master"
1826123,2019-04-24 08:15:26 UTC,Launchpad itself isn't the right target for this bug; that's for bug reports about the site itself.
1826123,2019-05-02 22:07:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826125,2019-09-05 19:00:18 UTC,"Created attachment 145270
attachment-3420-0.html"
1826125,2019-09-05 17:58:19 UTC,"(In reply to Paulo J. Matos from comment #29)

> (In reply to Kai-Heng Feng from comment #25)
> > Timo isn't around, please test this kernel:
> > https://people.canonical.com/~khfeng/bfo110511/
>
> This kernel works.
"
1826125,2019-09-03 07:05:30 UTC,Depends on which kernel we are talking about here.
1826125,2019-08-30 08:30:10 UTC,"Hi guys,"
1826125,2019-08-27 10:28:11 UTC,"(In reply to Paulo J. Matos from comment #26)

> I will take a look a this later. Apologies but I am on and off summer
> holidays these days.
"
1826125,2019-08-13 07:31:21 UTC,"According to
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/comments/19"
1826125,2019-07-19 19:19:05 UTC,"Many thanks, you are right, I'll post there!"
1826125,2019-07-19 15:30:26 UTC,"Hi Thomas, that sounds very similar to what we are seeing over in bug 1827790."
1826125,2019-07-17 09:00:23 UTC,I will take a look a this later. Apologies but I am on and off summer holidays these days.
1826125,2019-07-17 05:35:21 UTC,"Timo isn't around, please test this kernel:
https://people.canonical.com/~khfeng/bfo110511/"
1826125,2019-07-11 16:15:41 UTC,"Created attachment 144765
[PATCH] drm/i915: Try to use fast+narrow link on eDP again and fall  back to the old max strategy on failure"
1826125,2019-06-25 07:25:07 UTC,"Hi all,"
1826125,2019-06-08 21:25:09 UTC,I can confirm that the kernel with the reverted commit works. Apologies for the delay.
1826125,2019-06-07 06:59:58 UTC,"Apologies, I dropped the ball on this one. I will do that today."
1826125,2019-06-06 21:15:05 UTC,"Paulo, please test kernel build -10"
1826125,2019-09-06 11:30:40 UTC,The fix is nowhere yet. And judging from the ubuntu bug it may not even work :(
1826125,2019-07-19 15:13:00 UTC,"Hello, I would like to note that I think that I also have something related to this bug - although with the normal 1920x1024 panel (on XPS 13 9380) with a fresh Ubuntu 19.04 install (so kernel 5+) - I did not test the OEM Ubuntu 18.04 LTS."
1826125,2019-10-23 10:16:49 UTC,Just updated my ubuntu to 19.10 with kernel 5.3.0-19-generic and the problem is still here - so not fixed upstream. Will attempt to recompile this kernel using branch from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125/comments/91
1826125,2019-05-28 06:11:01 UTC,kernel -10 with the revert availabe behind the same url
1826125,2019-10-23 12:04:00 UTC,"Attempting to rebase
git://github.com/vsyrjala/linux.git dp_retry_max_vs_optim
onto v5.3 upstream seems to be a world of pain. :)"
1826125,2020-06-25 07:24:10 UTC,"My bad - I just noticed the discussion has moved upstream. Sorry for the noise here. Continuing discussion here:
https://gitlab.freedesktop.org/drm/intel/-/issues/272"
1826125,2020-06-25 07:22:10 UTC,"So this is not fixed yet with kernel 5.4.0-37 on ubuntu 20.04.
I have only been using this machine through ssh since it's unusable otherwise."
1826125,2020-05-04 12:43:43 UTC,"As mentioned in freedesktop's gitlab, this issue re-occurred after the upgrade to 20.04"
1826125,2019-11-29 19:04:58 UTC,-- GitLab Migration Automatic Message --
1826125,2019-11-08 14:41:02 UTC,"Correction, I just got a flicker, don't know why exactly what is triggering it, but it's not often."
1826125,2019-11-08 14:37:24 UTC,"I saw a flickering maybe once.. with the new kernel, but I can confirm it's not happening often."
1826125,2019-11-07 14:18:18 UTC,"OK, let me add I haven't seen this flickering anymore. It might have been just an artifact of something. I would say this is fixed unless someone else sees any other issue."
1826125,2019-10-23 12:02:24 UTC,Updated only launchpad:
1826125,2019-11-05 13:20:54 UTC,"This by the way, was literally just a couple of flickers for no apparent reason during an hours work under this kernel."
1826125,2019-11-05 13:02:39 UTC,"I can confirm this is working on Ubuntu 19.10.
Are we going to see the fix upstream at some point?"
1826125,2019-11-01 22:15:00 UTC,I've built a kernel here based on 5.3 plus the patch:
1826125,2019-11-01 18:14:40 UTC,"thanks for testing! it doesn't really matter which userspace you're on, this is purely a kernel bug"
1826125,2019-11-01 09:31:42 UTC,So with the kernel from: https://aaltoset.kapsi.fi/lp1826125 everything seems to work fine. However I am still on 19.04
1826125,2019-10-28 07:01:38 UTC,Paulo/Victor: please test the kernel here
1826125,2019-10-23 17:43:23 UTC,"no need to rebase anything, just cherry-pick the patch on top of 5.3.."
1826125,2019-10-23 12:32:09 UTC,I am back to a working monitor after installing https://people.canonical.com/~khfeng/bfo110511/
1826125,2019-11-05 13:20:00 UTC,Oh no! I just noticed some flickering in the monitor during work. Is there a way to understand what could be going on?
1826125,2019-05-27 12:01:22 UTC,Can we get a test with just 'git revert f11cb1c19ad0' ?
1826125,2019-09-03 07:25:54 UTC,"(In reply to Kai-Heng Feng from comment #25)

> Timo isn't around, please test this kernel:
> https://people.canonical.com/~khfeng/bfo110511/
"
1826125,2019-05-08 07:54:25 UTC,"Tiffany, apologies for the delay on this. I have been on holidays. Running the tests now."
1826125,2019-04-24 09:23:23 UTC,apport information
1826125,2019-04-24 09:23:22 UTC,apport information
1826125,2019-04-24 09:23:19 UTC,apport information
1826125,2019-04-24 09:23:17 UTC,apport information
1826125,2019-04-24 09:23:16 UTC,apport information
1826125,2019-04-24 09:23:15 UTC,apport information
1826125,2019-04-24 09:23:14 UTC,apport information
1826125,2019-04-24 09:39:08 UTC,Does the drm-intel-nightly help?
1826125,2019-04-24 09:23:12 UTC,apport information
1826125,2019-04-24 09:23:09 UTC,apport information
1826125,2019-04-24 09:23:07 UTC,apport information
1826125,2019-04-24 09:23:06 UTC,apport information
1826125,2019-04-24 09:23:04 UTC,apport information
1826125,2019-04-24 09:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826125,2019-04-24 08:25:02 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1826125,2019-05-25 16:40:26 UTC,"I can confirm that with Timo's kernel, with Ville's patch it all works smoothly.
Great job guys! Thanks so much for the support. I will keep using this kernel until upstream is fixed. Can you please update this bug once a proper fix hits upstream?"
1826125,2019-04-24 09:23:11 UTC,apport information
1826125,2019-04-24 09:53:47 UTC,I will give it a try. Is this just a matter of adding the ppa and `apt-get install drm-intel-nightly`?
1826125,2019-04-24 09:23:03 UTC,apport information
1826125,2019-04-24 11:22:00 UTC,Thanks Kai. Unfortunately it's still not ok. Interestingly now there is no flickering per-se. What I see is display corruption and flickering when refresh occurs - for example by moving the mouse or typing something.
1826125,2019-04-29 05:47:06 UTC,"Stan, any help here? I see hotplug events in dmesg."
1826125,2019-04-25 15:14:17 UTC,and happens with current nightly too
1826125,2019-05-02 05:57:15 UTC,"Hi Paulo Matos,"
1826125,2019-04-25 10:35:04 UTC,"I am however betting this is not a hw bug due to the way the flickering changed with the kernel upgrade. Compare the first video posted in this report and now:
https://photos.app.goo.gl/tpmTGWVJXpChoERz6"
1826125,2019-04-25 10:27:45 UTC,"Timo, it seems I can install windows 10 on a usb flash for installation. Will try that.
Ref: https://www.howtogeek.com/244678/you-dont-need-a-product-key-to-install-and-use-windows-10/"
1826125,2019-04-25 10:24:02 UTC,"Created attachment 144092
dmesg from boot"
1826125,2019-04-25 10:21:57 UTC,"maybe it would, yes.."
1826125,2019-04-25 10:12:14 UTC,"Hummm, I have almost zero experience with windows. Is there a windows version that I can install for free - windows 10 maybe?"
1826125,2019-04-25 10:24:33 UTC,"Timo, opened upstream as suggested: https://bugs.freedesktop.org/show_bug.cgi?id=110511"
1826125,2019-04-25 09:30:18 UTC,I have upgraded the BIOS to 1.2.1 but not changed its settings. Could it be that there's something there that I could try?
1826125,2019-04-25 09:29:22 UTC,Unfortunately not. It actually makes the flickering more like in the pre-5 kernel where it flickers constantly as opposed to only when the move is moved. Posting new dmesg with i915.enable_psr=0 in case its useful.
1826125,2019-04-25 04:46:25 UTC,"Does ""i915.enable_psr=0"" help?"
1826125,2019-04-24 17:40:17 UTC,Sure. Results are attached next.
1826125,2019-04-24 07:57:04 UTC,"Having problems posting apport data due to:
```
$ ubuntu-bug -c cartsheel.apport -u 1826125
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash file]"
1826125,2019-04-24 11:34:45 UTC,"Can you boot with kernel parameter ""drm.debug=0xe"" and attach full dmesg after boot?"
1826125,2019-04-24 11:24:39 UTC,"Removed the i915 boot params : i915.fastboot=1 i915.enable_rc6=0
No changes."
1826125,2019-04-25 09:53:34 UTC,Sounds like you should contact the upstream developers and file a bug at bugs.freedesktop.org
1826125,2019-04-24 10:04:33 UTC,Download linux-image-unsigned-5.1.0-994-generic_5.1.0-994.201904222200_amd64.deb and linux-modules-5.1.0-994-generic_5.1.0-994.201904222200_amd64.deb then install them.
1826131,2019-04-24 08:31:59 UTC,broken state :(
1826131,2019-04-24 08:37:07 UTC,"it gets stranger...
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 19.04
Release:	19.04
Codename:	disco"
1826131,2019-04-24 08:46:05 UTC,"I restarted the machine. Fearfully!
Then"
1826131,2019-04-24 14:22:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826131,2019-04-24 19:22:58 UTC,Adding that I just got the same error upon upgrade to 19.04. Will restart with trepidation to see if it will work...
1826133,2019-06-27 11:36:57 UTC,"Hi, thanks for the bug report, and sorry for late answer.
If you are interested in testing l2gw I suggest to start with this how-to:
https://opendev.org/openstack/networking-l2gw#getting-started"
1826139,2019-05-14 19:08:26 UTC,This bug was fixed in the package linux-raspi2 - 5.0.0-1008.8
1826141,2019-05-02 13:33:25 UTC,regression tests:
1826141,2019-05-14 19:07:01 UTC,This bug was fixed in the package linux-aws - 5.0.0-1006.6
1826142,2019-04-24 09:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826142,2019-06-18 12:01:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1826142,2019-06-19 08:52:40 UTC,Thanks. disco-proposed kernel works fine with TPM module.
1826142,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1826143,2019-05-02 14:00:24 UTC,regression testing:
1826143,2019-05-14 19:07:10 UTC,This bug was fixed in the package linux-azure - 5.0.0-1006.6
1826144,2019-05-02 14:48:22 UTC,Regression Testing:
1826144,2019-05-14 19:08:06 UTC,This bug was fixed in the package linux-gcp - 5.0.0-1006.6
1826145,2019-05-14 19:08:19 UTC,This bug was fixed in the package linux-kvm - 5.0.0-1006.6
1826146,2019-05-14 19:08:33 UTC,This bug was fixed in the package linux-snapdragon - 5.0.0-1012.12
1826147,2019-05-14 19:02:56 UTC,This bug was fixed in the package linux-hwe-edge - 5.0.0-15.16~18.04.1
1826147,2019-04-29 10:51:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826150,2019-05-08 15:37:28 UTC,Verification tests completed successfully with the Disco kernel in -proposed (https://kernel.ubuntu.com/reports/sru-report.html).
1826150,2019-05-09 10:35:58 UTC,Hardware Certification have begun testing this -proposed kernel.
1826150,2019-05-09 10:44:42 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/disco/5.0.0-14.15/disco-proposed-published.html"
1826150,2019-05-10 03:16:47 UTC,"5.0.0-14.15 - generic
Regression test CMPL, RTB."
1826150,2019-05-14 19:06:48 UTC,This bug was fixed in the package linux - 5.0.0-15.16
1826152,2019-05-09 21:15:09 UTC,Fixed in Disco with h2o 2.2.5+dfsg2-1
1826152,2020-01-21 06:41:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826154,2019-07-12 19:03:52 UTC,"I'm taking a look at in on windows right now.  It might take a while due to long build times on windows.
 Anyone have a sample board with a large netclass list that I can use to confirm this on windows so I don't have to generate one myself?"
1826154,2019-07-15 13:22:07 UTC,Great.  There are no string changes and minimal risk.  I've cherry-picked to 5.1
1826154,2019-07-15 12:47:38 UTC,I confirmed this doesn't cause any issues on windows at least with 30 netclasses.  Is there any other reason not to cherry-pick this to 5.1?
1826154,2019-07-12 18:53:17 UTC,"I'd prefer to hold off on cherry-picking until we have some confirmation that it works for all platforms.  If MSW devs can confirm before the 5.1.3 release, we'll cherry-pick it back, otherwise, we'll hold it for 5.1.4"
1826154,2019-07-09 20:43:12 UTC,"Here is a patch that fixes this beahviour. I had to lock the size of the two sections, and manually then recompute their size when the window is updated to get this to work. I also had to wrap the sizers inside panes since sizers can't have a defined maximum size."
1826154,2019-07-12 17:59:08 UTC,"I should note that sometimes these wx bits have unintended platform issues, so if any MSW devs observe netclass viewing issues, we may need to re-open"
1826154,2019-07-12 17:58:47 UTC,"Fixed in revision 39954b20fe4e81a64e9a0f3b042a2547100aaad8
https://git.launchpad.net/kicad/patch/?id=39954b20fe4e81a64e9a0f3b042a2547100aaad8"
1826154,2019-07-12 17:57:36 UTC,Works nicely.  Thanks Ian!
1826154,2019-07-12 18:36:19 UTC,"@Seth, are we going to wait to cherry-pick this into 5.1 until after 5.1.3 to give this time to settle in master?"
1826156,2019-04-24 09:43:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655361"
1826158,2019-10-11 04:04:02 UTC,"    > I would expect you may want to create an advisory for this issue then for that specific
    > release. > Or tell users to move to 19.10 next week once it is released."
1826158,2019-10-10 20:46:51 UTC,"The newer installer seems to have fixed this, which I believe means there is no further work to do here other than generate a new ISO. However, given 19.04 is a development release I do not expect there to be a new ISO."
1826158,2019-10-08 07:46:51 UTC,"   > Do you get at least to the language selection prompt, i.e., does the installer at least stop somewhere asking you a question?"
1826158,2019-10-03 21:40:07 UTC,"So, on the GA iso, one cannot get to the step where the installer is updated. Do you get at least to the language selection prompt, i.e., does the installer at least stop somewhere asking you a question? You say:"
1826158,2019-09-03 17:58:23 UTC,"If this is fixed in the development release (eoan), can you retest with the latest installer from disco? Please update the installer if prompted. You should have version 19.07.3 available to you now."
1826158,2019-09-02 07:44:03 UTC,No such issue in ubuntu 19.10 live server daily build Aug/28/2019
1826158,2019-05-07 17:16:54 UTC,"Traceback is from probert, so adding the probert task."
1826158,2019-04-30 03:57:34 UTC,capture the traceback of installer subiquity. Please check attached file traceback.png
1826158,2019-04-24 10:05:41 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826158,2019-09-27 06:03:15 UTC,"> If this is fixed in the development release (eoan), can you retest with the latest installer from > disco? Please update the installer if prompted. You should have version 19.07.3 available to you > now.
"
1826159,2020-03-14 14:40:01 UTC,May be related to this bug as printing issues started with it.
1826159,2020-03-25 17:32:26 UTC,"I seem to be getting both IPv4 & IPv6 with same hostname, so then printer does not connect.
I turned off IPv6 and now it works, but have to release it every time."
1826159,2020-01-06 12:30:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826159,2019-04-24 10:08:14 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1826159,2019-04-24 13:42:45 UTC,The cups-pl-helper error report is https://errors.ubuntu.com/oops/c2dbf84d-6692-11e9-a55b-fa163e102db1
1826159,2019-04-24 10:57:12 UTC,For the moment I do not seem to be able to reproduce this. So I guess it happened when I tried to send the report bug thing in the popup since that popup came because of another crash: _usr_lib_x86_64-linux-gnu_cups-pk-helper-mechanism.125.crash. But since that failed I edited the crashdb conf file. So it CAN be that this doesnt happen anymore. But very uncertain........
1826159,2019-04-24 09:40:18 UTC,"StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f247b810952 ""%s\n"") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f247b80ea9b ""free(): invalid pointer"") at malloc.c:5352
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:4181
 free_reason_data (user_data=0x7f246c0014e0) at ../plugins/print-notifications/gsd-print-notifications-manager.c:243
 g_list_foreach (list=<optimized out>, list@entry=0x564a05c2bd80, func=0x564a043b6e90 <free_reason_data>, user_data=user_data@entry=0x0) at ../../../glib/glist.c:1013"
1826159,2019-04-24 22:09:05 UTC,"I actually succeeded in getting this dump again. From the gnome settings up in the right corner, choose Test print. The printout went to the printer options and made a test print from the button in the left corner of the windows. That crash appeared in /var/crash despite it looks like everything works......This time I also got another crash at the same time:"
1826160,2019-05-14 19:06:03 UTC,This bug was fixed in the package linux-raspi2 - 4.18.0-1014.16
1826161,2019-05-03 19:59:36 UTC,regressiontests:
1826161,2019-05-15 02:05:41 UTC,This bug was fixed in the package linux-aws-edge - 4.18.0-1016.18~18.04.1
1826163,2019-05-02 13:42:17 UTC,regression testing
1826163,2019-05-14 19:04:21 UTC,This bug was fixed in the package linux-aws - 4.18.0-1016.18
1826164,2019-05-03 20:05:20 UTC,"regressiontesting:
amd64:"
1826164,2019-05-09 15:39:45 UTC,Tests complete
1826165,2019-05-15 11:39:00 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18~18.04.1
1826165,2019-05-14 22:58:36 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826165,2019-05-09 15:41:08 UTC,Tests complete.
1826165,2019-05-03 20:04:46 UTC,"regressiontesting:
amd64:"
1826165,2019-05-14 22:55:23 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18~18.04.1
1826166,2019-05-03 19:38:16 UTC,Regression Tests:
1826166,2019-05-14 19:04:29 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18
1826166,2019-05-14 22:55:23 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18~18.04.1
1826166,2019-05-14 22:58:39 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826166,2019-05-15 11:39:00 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18~18.04.1
1826166,2019-05-16 07:36:13 UTC,This bug was fixed in the package linux-azure - 4.18.0-1018.18
1826167,2019-05-14 19:02:41 UTC,This bug was fixed in the package linux-gcp-edge - 4.18.0-1011.12~18.04.1
1826168,2019-05-14 19:05:42 UTC,This bug was fixed in the package linux-gcp - 4.18.0-1011.12
1826168,2019-10-09 20:32:41 UTC,This bug was fixed in the package linux-gcp - 5.0.0-1020.20~18.04.1
1826169,2019-05-14 19:05:54 UTC,This bug was fixed in the package linux-kvm - 4.18.0-1012.12
1826170,2019-05-09 05:48:01 UTC,"4.18.0-19.20~18.04.1 - generic
Regression test CMPL, RTB."
1826170,2019-05-14 19:03:00 UTC,This bug was fixed in the package linux-hwe - 4.18.0-20.21~18.04.1
1826170,2019-05-03 09:07:43 UTC,Hardware Certification have begun testing this -proposed kernel.
1826170,2019-05-07 10:32:34 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/bionic/4.18.0-19.20~18.04.1/bionic-4.18-proposed-published.html"
1826171,2019-05-03 08:17:34 UTC,"4.18.0-19.20 - generic
Regression test CMPL, RTB."
1826171,2019-05-03 09:07:56 UTC,Hardware Certification have begun testing this -proposed kernel.
1826171,2019-05-06 09:57:07 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/cosmic/4.18.0-19.20/cosmic-proposed-published.html"
1826171,2019-05-13 09:48:33 UTC,Verification testing completed with the Cosmic kernel in -proposed.
1826171,2019-05-14 19:04:10 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1826171,2019-05-14 22:58:44 UTC,"The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826171,2019-05-16 07:35:52 UTC,This bug was fixed in the package linux - 4.18.0-20.21
1826172,2019-04-24 09:58:01 UTC,MinGW-w64 toolchain version:
1826172,2019-05-09 16:31:40 UTC,"Hi; thanks for this bug report. It should be fixed by commit 946376c21be1cd9dcc3c7 in git master, which will be in the 4.1 release."
1826174,2019-04-24 18:58:23 UTC,FYI the UI does accept an area parameter on the node details page to select which tab should be displayed. This is how the 'Back to machine details' link works when viewing the log of a commissioning or hardware test script. I tried using this to fix refresh and allow the forward and back browser buttons to work with [1] but got stuck and had to move onto other things.
1826175,2020-04-05 02:04:59 UTC,I am still running into this issue when compiling QEMU on Windows using MSYS2. I can manually apply the fix per the Capstone commit above and compile just fine.
1826175,2019-09-24 10:56:53 UTC,The fix in upstream capstone has been merged: https://github.com/aquynh/capstone/commit/29893c63e34ee21846744d02c396ae3c801b936b
1826175,2019-04-24 12:25:50 UTC,https://github.com/aquynh/capstone/issues/1464 is the upstream bug -- thanks for reporting it there.
1826175,2019-04-24 11:20:53 UTC,"This change needs to go in via the capstone project. capstone is just an unmodified ""submodule"" in QEMU - we do not include any QEMU-only changes here."
1826175,2019-04-24 11:57:54 UTC,"Re-opened, since although the fix needs to be done in capstone, QEMU also needs a commit to actually update the submodule hash to pull in the fix."
1826175,2019-04-24 12:10:21 UTC,I did submit a bug already to Capstone proper on their GitHub. Thanks for the heads-up about it needing to cover both cases for cross-compilers!
1826175,2019-04-24 10:21:21 UTC,"NB that patch will break Linux based Mingw builds, as they don't include ""mys2"" in their output from gcc, so it would need to match both."
1826176,2019-04-24 10:07:38 UTC,"Thank you for your bug report, could you also send the issue upstream on https://gitlab.gnome.org/GNOME/gnome-shell ?"
1826176,2019-06-03 09:14:10 UTC,This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1~19.04.1
1826176,2019-06-03 09:14:01 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826176,2019-05-09 08:44:00 UTC,"^^^
Tagged per above."
1826176,2019-05-09 08:17:11 UTC,"Ubuntu 19.04 with all updates installed, using Ubuntu on Wayland desktop session."
1826176,2019-05-07 12:46:47 UTC,"Hello Łukasz,"
1826176,2019-05-06 12:34:48 UTC,"Hello Silvio, or anyone else affected,"
1826176,2019-06-03 09:13:38 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1~19.04.1
1826176,2019-05-01 11:34:41 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1
1826176,2019-05-01 11:34:40 UTC,This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1
1826176,2019-04-26 06:58:38 UTC,Fixed upstream(?) assuming the upstream bug links are correct.
1826176,2019-04-26 01:49:15 UTC,"Just in case, please try uninstalling your extensions:"
1826176,2019-04-25 00:13:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826176,2019-04-24 11:10:52 UTC,"OK, I just filed issue #1211."
1826176,2019-05-06 12:17:36 UTC,"Hello Silvio, or anyone else affected,"
1826179,2019-04-24 11:26:25 UTC,13:22 <mschuppert> quiquell|rover: there is additional work to be done to support upgrades from nova-placement in Stein to an extracted service in Train https://review.opendev.org/#/q/topic:tripleo-placement-upgrade-from-nova-placement+(status:open++OR+status:merged)
1826179,2019-05-05 14:47:28 UTC,"[1] add the needed upgrade step to extract the DB data from nova_api db to the new placement db, but the upgrade tasks still fail with this error [2]."
1826179,2019-05-07 20:52:32 UTC,I've reproduced the CI and the links seams fine but the problem seems to be with packaging or CI configuration. Package that is installed does not contain placement puppet manifests as seen below.
1826179,2019-05-08 08:09:00 UTC,"good catch, so the issue is the that master repo has no master puppet-tripleo rpm containing the placement manifest. 10.4.2 is still stein."
1826179,2019-05-08 08:45:36 UTC,so the issue is that in the master repo [1] we have 10.4.1 version and in the stein repo [2] we have 10.4.2 . For the upgrade ci tests we get 10.4.2 (which does not include the placement manifest) and when we do the upgrade to master the files from master gets not installed as the rpm has a lower version.
1826179,2019-05-08 08:57:11 UTC,https://review.opendev.org/#/c/657758/
1826181,2019-08-06 05:57:05 UTC,"@M Willis Monroe, besides the oem-kernel, I think you also need a UCM config file, could you please install this deb package (attached) and reboot, then check whether the dmic works."
1826181,2019-08-07 08:25:13 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
1826181,2019-08-06 04:26:11 UTC,I found this through random googling... but I'm running a Lenovo X1 Carbon gen 7 with Disco and installing this oem kernel package doesn't seem to enable the DMIC.  Not sure if this is the correct place for that observation.
1826181,2019-10-17 09:13:10 UTC,"for the UCM config file in #7, you also can get it from this PPA (Bionic, Disco, Eoan supported):"
1826181,2019-07-02 14:01:05 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1012.13
1826181,2019-06-18 06:19:54 UTC,"this is in bionic-proposed, please test"
1826181,2019-05-02 14:15:27 UTC,"Got it, thx."
1826181,2019-07-26 15:21:25 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1015.16
1826181,2019-05-02 13:39:37 UTC,"note; technically, it's 'OEM-OSP1-B', disco doesn't have an oem kernel of it's own ;)"
1826182,2019-06-03 09:14:03 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826182,2019-06-03 09:13:38 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1~19.04.1
1826182,2019-04-26 02:09:50 UTC,Thanks Pekka.
1826182,2019-05-06 12:17:47 UTC,"Hello Ppaalanen, or anyone else affected,"
1826182,2019-05-01 11:34:41 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1
1826182,2019-05-07 09:43:24 UTC,"I installed:
- libmutter-4-0: 3.32.1-2ubuntu1~19.04.1
- gir1.2-mutter-4: 3.32.1-2ubuntu1~19.04.1"
1826183,2019-04-24 10:46:58 UTC,"Crazy, who has invalid unicode in package names?"
1826183,2019-04-24 10:47:37 UTC,"Probably a memory corruption somewhere, but this would need some deep digging."
1826183,2019-04-24 11:09:33 UTC,"There are many corruptions reported at
https://errors.ubuntu.com/?package=unattended-upgrades&period=week&version=1.10ubuntu5
:-("
1826183,2019-04-24 14:35:14 UTC,"On Wed, Apr 24, 2019 at 10:46:58AM -0000, Julian Andres Klode wrote:

> Crazy, who has invalid unicode in package names?
"
1826184,2019-11-02 22:03:44 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest stable version of Ubuntu (Ubuntu 19.10 - Eoan Ermine)."
1826184,2019-11-01 18:42:24 UTC,I tested that on Ubuntu 19.10:
1826184,2019-04-24 10:38:21 UTC,apport information
1826184,2019-04-24 10:38:22 UTC,apport information
1826184,2019-04-24 10:38:20 UTC,apport information
1826187,2019-10-20 15:07:12 UTC,This still happens to me.
1826187,2019-10-20 15:35:09 UTC,"Apparently, this happens if iptables <= 1.6.2-1.1, firewalld >= 0.6.3-5. Installing both in their latest versions fixes the issue."
1826187,2019-09-10 08:29:54 UTC,"This magically went away on the most recent daily cloud images. @wvengen, does it work for you again as well? If so, we can close this. Thanks!"
1826187,2019-07-17 12:59:32 UTC,"Wow, this is pretty serious! I recently discovered that I'd been running without a firewall for some time (exposing unsecured services, also on public WiFi). Previously it worked, some upgrade must have introduced this issue."
1826187,2019-04-24 23:14:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826187,2019-04-24 23:44:51 UTC,same trouble here
1826187,2019-04-24 11:18:03 UTC,"With the nftables backend, it's not just --state that's broken, it also at least affects --reload:"
1826187,2019-04-24 10:55:32 UTC,"The nftables backend actually does work reasonably well, only firewall-cmd --state seems to be broken."
1826187,2019-04-26 05:54:04 UTC,Doing this fixes it:
1826188,2019-06-11 16:09:43 UTC,This should be fixed now that block-discover branch has been merged.
1826188,2019-08-11 04:17:25 UTC,[Expired for curtin because there has been no activity for 60 days.]
1826190,2019-04-24 14:28:02 UTC,"Yes, we'll need to work with qemu on the host to sort out what device are available and update xkvm with those for arm64"
1826192,2019-07-10 10:22:46 UTC,This is a feature request that should be handled via the upstream tracker:
1826196,2019-04-26 02:15:00 UTC,This sounds a little like bug 1716232. But mostly the issue here seems to be that your touchpad doesn't support scrolling(?).
1826196,2019-06-25 04:17:39 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1826196,2019-09-04 14:17:30 UTC,This issue was fixed in the openstack/oslo.i18n 3.24.0 release.
1826199,2019-06-11 11:07:39 UTC,The issue has not been reproduced. Feel free to re-open it if you have more details on reproducing the issue.
1826200,2019-04-24 13:03:59 UTC,See also: https://github.com/puiterwijk/qemu-ovmf-secureboot/issues/25
1826200,2020-12-10 09:20:42 UTC,Released with QEMU v5.2.0.
1826200,2020-11-04 23:09:39 UTC,Merged: https://<email address hidden>/
1826200,2019-04-24 12:53:00 UTC,See also: https://bugzilla.tianocore.org/show_bug.cgi?id=1747
1826200,2020-08-12 11:51:54 UTC,"We'll probably never have resources for this -- nice to have feature, but has not become critical in ~1.5 years. LP doesn't allow me to close the ticket as ""Won't Fix"", so I'll have to go with ""Invalid"". (The report is not invalid at all, but the ticket status should *somehow* reflect that we have no resources for working on this.)"
1826200,2020-09-08 17:20:50 UTC,Surprise...
1826201,2019-05-16 08:36:50 UTC,"The verification of the Stable Release Update for gstreamer-vaapi has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826201,2019-05-16 08:36:46 UTC,This bug was fixed in the package gstreamer-vaapi - 1.15.90-1ubuntu1
1826201,2019-05-10 02:47:23 UTC,Fix verified on disco using gstreamer1.0-vaapi_1.15.90-1ubuntu1_amd64.deb
1826201,2019-05-09 05:03:42 UTC,A simple way to test the proposed fix for 19.04 is to download it directly:
1826201,2019-05-08 22:15:56 UTC,"Hello Thabang, or anyone else affected,"
1826201,2019-05-08 12:53:53 UTC,This bug was fixed in the package gstreamer-vaapi - 1.16.0-1ubuntu1
1826201,2019-05-03 10:04:56 UTC,"the patch proposed by seb128 fixes the problem for me.
now please fix also https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721248"
1826201,2019-05-03 07:07:26 UTC,Seb mentioned that he was going to patch the fix (into Ubuntu and likely Debian) soon. So reassigned.
1826201,2019-05-02 21:56:13 UTC,"OK thank you. everything now works as already mentioned.
The output from mpv when playing an mp4 video is shown below, if it is still required."
1826201,2019-05-02 15:50:17 UTC,"Upstream has a patch that seems to work, you can install that package that includes it if you want to test as well
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16722126/+files/gstreamer1.0-vaapi_1.15.90-1+test1_amd64.deb"
1826201,2019-05-01 06:40:02 UTC,These also have the bug:
1826201,2019-05-01 05:33:32 UTC,"Also gst-play-1.0 seems to work fine, and that does use gstreamer-vaapi."
1826201,2019-04-30 15:19:09 UTC,Looks like it has been reported upstream on https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/157
1826201,2019-04-29 02:58:58 UTC,"'mpv' is not a video format, it is a video player."
1826201,2019-04-26 20:16:43 UTC,------ The output to $ vainfo is shown below --------
1826201,2019-04-26 02:18:36 UTC,I would like to find out if this is a general VAAPI problem or is indeed specific to gstreamer.
1826201,2019-04-24 20:29:52 UTC,"I am affected by the same problem after the upgrade 1o 19.04 and can confirm that removing gstreamer1.0-vaapi solved it for me as well,thanks!"
1826201,2019-04-24 17:20:29 UTC,Yes that solved the problem. I removed the package and all is working now.
1826201,2019-04-24 16:22:52 UTC,Do you get the issue if you uninstall gstreamer1.0-vaapi?
1826201,2019-04-24 15:01:21 UTC,Sorry i see the formatting is rough. I don't know how to properly insert code in Launchpad.
1826201,2019-04-24 14:59:16 UTC,"The error is that i only see a ""green screen"" when i open an mp4 video."
1826201,2019-04-24 11:49:39 UTC,"Thank you for your bug report. Could you give the output of that command
$ dpkg -l | grep gstreamer"
1826201,2019-05-01 05:31:13 UTC,"OK, I can reproduce the bug now. Only in Xorg sessions and not Wayland."
1826201,2019-05-01 02:34:08 UTC,We haven't established for certain that this is a gstreamer-vaapi bug yet. Though it sounds likely.
1826202,2020-09-21 04:17:14 UTC,[Expired for TAPAAL because there has been no activity for 60 days.]
1826203,2019-12-07 04:17:39 UTC,[Expired for juju because there has been no activity for 60 days.]
1826203,2019-10-07 14:47:23 UTC,"We have observed this behaviour on other MAAS deployments, where things like firewall rules can prevent the MAAS hosts from accessing image streams for the containers. One particular culprit was Snort (https://www.snort.org/)."
1826203,2019-10-07 14:42:34 UTC,We had a user hitting this and found that the machine couldn't get the linux container images from the cloud-images.ubuntu.com. Turns out there was a snort rule that was blocking the urls. Testing was to verify if from a machine you could manually launch a lxc container and if not working through what was blocking it up.
1826207,2019-04-24 13:01:06 UTC,This was tested recently on Ubuntu 19.04 with the Mate DE added.
1826209,2019-04-27 01:38:47 UTC,"it seems likely there may be packaging or integration problems here, tho this bug emerges on multiple highly popular distributions."
1826209,2020-01-04 02:40:01 UTC,"Bug #1788481 seems similar, tho it's suggestion dbus-x11 is the fix appears to be false."
1826209,2020-01-04 17:08:34 UTC,"solved.  $HOME/.config had been owned by root, thus was unwriteable.  the problem was found when i installed kubuntu-desktop and launched startkde, which reported that $HOME/.config was unwriteable.  perhaps gnucash might consider emitting such a message."
1826209,2020-01-25 15:09:39 UTC,"Further to comment #3, assigning to gnucash and closing as invalid as not a bug in GnuCash."
1826211,2019-05-18 09:18:10 UTC,and so before doing the automatic assignment ?
1826211,2019-08-15 09:33:20 UTC,"I will add a checkbox at the end of import (so as the assign which is done with no user option right now)
and also a tools menu to be able to do this on each account"
1826211,2019-08-15 13:10:50 UTC,finally not in the menu as it doesn't really useful there in cas one input txn by hand the assign is already make when input a new txn
1826212,2019-04-24 13:45:32 UTC,"Skipped ""Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt"" since it is already applied for CVE-2019-3460.
Skipped ""Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer"" since it is already applied for CVE-2019-3459.
Skipped ""sched/fair: Fix new task's load avg removed from source CPU in wake_up_new_task()"" since it is already applied for bug #1643797.
Skipped ""btrfs: raid56: properly unmap parity page in finish_parity_scrub()"" since it is already applied for bug #1812845."
1826212,2019-06-04 09:11:38 UTC,This bug was fixed in the package linux - 4.4.0-150.176
1826213,2020-06-18 09:38:53 UTC,This bug was fixed in the package update-manager - 1:18.04.11.13
1826213,2020-06-18 09:38:04 UTC,This bug was fixed in the package update-manager - 1:19.04.8.1
1826213,2020-06-18 09:18:56 UTC,"The verification of the Stable Release Update for update-manager has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826213,2020-06-18 09:18:49 UTC,This bug was fixed in the package update-manager - 1:20.04.10.1
1826213,2020-06-10 23:00:46 UTC,I also followed the test case on Ubuntu 19.10 and update-manager version 1:19.04.8.1 from eoan-proposed. When the AssertionError was raised I saw the dialog boxes instead of the Traceback.
1826213,2020-06-10 23:14:36 UTC,"I tested the version of update-manger, 1:18.04.11.13, from bionic-proposed and did not receive the Traceback when I forced an AssertionError. I also saw the dialog boxes with the version of update-manager from -proposed."
1826213,2020-06-10 22:26:49 UTC,I followed the test case on Ubuntu 20.04 LTS with update-manager version 20.04.10.1 from focal-proposed and saw the dialog boxes instead of the Traceback - setting to verification-done.
1826213,2020-06-03 09:22:23 UTC,This bug was fixed in the package update-manager - 1:20.04.12
1826213,2020-06-05 14:45:23 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1826213,2020-06-05 14:27:43 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1826213,2020-05-27 22:56:56 UTC,A hackish test case for this bug involves the following:
1826213,2020-05-21 22:34:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826213,2020-04-15 17:39:40 UTC,I made a spot check of the first few crashes in the Error Tracker and curiously they all have:
1826213,2020-02-13 18:17:08 UTC,Here's the Traceback:
1826213,2020-06-05 14:56:46 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1826214,2020-01-20 13:34:19 UTC,Here is the traceback:
1826219,2020-01-24 09:51:54 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1826219,2019-05-14 09:16:13 UTC,@djcater this is a Dell XPS 13 9360 (not -80)—slightly older (2017 or 2018).
1826219,2019-05-13 20:49:49 UTC,"Hi Paul, thanks for pointing me to this bug from https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827791."
1826219,2019-04-26 20:53:54 UTC,"Thanks! My searches before filing the bug suggested that the log messages were symptoms, but I was unable to find any guideline on how to diagnose further."
1826219,2019-05-03 10:00:25 UTC,"More information, as this continues to occur:"
1826219,2019-04-24 14:39:38 UTC,"The lock also occurs when using claws-mail. I pressed [Delete] in a message list, and the lock caused that keypress to be repeated, deleting about a dozen messages that I then needed to retrieve from the trash."
1826219,2019-05-13 20:21:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826219,2019-04-26 02:41:57 UTC,The log messages you mention seem to be describing symptoms of the problem but not the cause.
1826220,2019-04-26 16:10:02 UTC,Note: implementing this is a lot harder than it sounds at first.
1826220,2019-05-21 06:55:03 UTC,"If you check it use updated_at,what is the reference to update_at? Less than the current time?"
1826220,2019-07-17 10:05:17 UTC,I think we can add some status-check before conditional_update.
1826220,2019-07-18 07:26:52 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/671416"
1826220,2019-07-19 06:08:44 UTC,"Change abandoned by ye (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/671416
Reason: thanks a lot, abandon this change."
1826220,2019-07-22 09:06:26 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671996"
1826221,2019-04-24 17:16:23 UTC,Marking as release gating; related to https SB which is a stx.2.0 gating SB; horizon login with https enabled should use secure login
1826221,2019-07-10 22:07:16 UTC,This is a security issue; related to https configuration
1826221,2019-08-01 21:06:52 UTC,"This issue is not reproducible using load BUILD_ID=""20190729T233000Z"".
The Openstack Horizon is accessible via https://horizon.<labname>.cumulus.wrs.com without the workaround specified in the Bug Description."
1826221,2019-08-12 14:18:32 UTC,"Retested in Wind River lab: cgcs-wolfpass-16-17.cumulus.wrs.com
Verdict: Passed"
1826222,2019-04-24 15:24:47 UTC,solved after installing proposed
1826222,2019-04-24 15:24:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826222,2019-04-24 15:23:01 UTC,@Sebastien
1826222,2019-04-24 14:37:40 UTC,See LP: #1825738
1826222,2019-04-24 14:58:08 UTC,Does https://bugs.launchpad.net/ubuntu/+source/python-apt/1.9.0~alpha0~ubuntu1 fix your issue?
1826222,2019-04-24 14:56:49 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826224,2019-05-15 06:53:00 UTC,This bug was fixed in the package ubuntu-image - 1.7+19.10ubuntu1
1826225,2019-04-29 06:52:33 UTC,This review addresses the issue: https://review.opendev.org/#/c/655516
1826227,2019-04-24 17:12:43 UTC,Marking as release gating; medium priority as the system should not be in dual standby mode when using an incorrect certificate.
1826227,2019-07-18 12:55:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671479"
1826227,2019-08-02 21:10:09 UTC,"Reviewed:  https://review.opendev.org/671479
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=6ac774799e1db3d2bf9cc5c053593005e8d9d763
Submitter: Zuul
Branch:    master"
1826227,2019-09-25 23:35:18 UTC,"# Testing Status
PASSED"
1826233,2020-09-04 21:04:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826234,2019-05-09 19:35:19 UTC,Noting for anybody who picks this up that org unit columns are another example of the same problem.
1826234,2019-04-24 17:46:59 UTC,"Did you mean: sorting is based on ID, not profile name? I think the problem is that the column *displays"" profile name but the sort order is ID. Sorry if I'm misunderstanding the terminology."
1826234,2019-04-24 17:56:42 UTC,I did indeed. I've corrected the bug description and tweaked the title.
1826237,2020-09-22 04:30:02 UTC,@james-page do you know the current status of this?
1826237,2019-07-18 12:50:40 UTC,Confirmed; hardware offloading of connection state tracking is an inflight feature in both the Linux kernel and OVS:
1826238,2019-04-25 05:21:02 UTC,CAP_SETPCAP should be allowed in the profile
1826238,2019-04-25 11:26:19 UTC,I just test this in a container (Bionic host/4.15 and Disco guest) and I can confirm the problem and the solution. Here is how to easily reproduce (and workaround):
1826238,2019-04-25 11:26:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826238,2019-04-25 14:38:59 UTC,A better workaround until this is officially fixed might be to use the local/ includes like this:
1826238,2019-04-26 05:27:42 UTC,"Thanks Simon,
as discussed this will be added (or if accepted by then picked up) at the strongswan merge for Eoan. But that has a few things it has to wait on first so this will take a while.
Fortunately you added the great apparmor override help in comment #4 which should help people affected until then."
1826238,2019-04-26 09:42:28 UTC,"FYI - I started the merge as I have realized I'd want to do that -before- resubmission of our Delta to Debian for bug 927961.
Therefore this should soon be in Eoan unless the merge turns out to be more complex than usual."
1826238,2019-04-26 14:44:04 UTC,Another bug in the profile [mentioned](https://github.com/trailofbits/algo/pull/1405#issuecomment-487079035) by @demyers
1826238,2019-04-26 15:02:08 UTC,"Those dbus rules feel like something that should go in an abstraction. That said, neither strongswan nor strongswan-swanctl use the dynamicuser feature of systemd so it is just noise, or at least, that's my understanding."
1826238,2019-05-03 12:52:45 UTC,FYI fix in Eoan-proposed
1826238,2019-05-03 14:12:23 UTC,This bug was fixed in the package strongswan - 5.7.2-1ubuntu1
1826240,2019-05-02 18:25:04 UTC,This is only happening on my (petevg) laptop.
1826240,2019-11-12 18:44:01 UTC,"This is fixed in --beta, and has been for a while. Closing the bug."
1826242,2019-07-29 22:22:51 UTC,"Reviewed:  https://review.opendev.org/656798
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-openstack_hosts/commit/?id=dae154531b22ae9067c8a06965ec676febed745b
Submitter: Zuul
Branch:    master"
1826242,2019-07-30 17:37:37 UTC,"Reviewed:  https://review.opendev.org/657773
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-plugins/commit/?id=fc9e016e90ca49d3630dcbc0bbf970277740edc7
Submitter: Zuul
Branch:    master"
1826242,2019-05-02 15:52:01 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/656798"
1826242,2019-05-08 10:27:31 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657773"
1826243,2019-04-24 16:45:25 UTC,"removing this actually, because we have 'name2int' module which does the same, which really should be a *filter* not a module, so let's keeps string_2_int and move name2int to it"
1826243,2019-05-02 11:07:59 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/656761"
1826243,2019-05-08 09:02:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657761"
1826243,2019-07-27 16:06:31 UTC,"Change abandoned by Jonathan Rosser (<email address hidden>) on branch: master
Review: https://review.opendev.org/656761
Reason: These tasks are removed in the master branch now"
1826243,2019-07-27 20:48:43 UTC,"Reviewed:  https://review.opendev.org/657761
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-plugins/commit/?id=5af0b9bcc34a93c6c49cb1c153dbba69f0fd79ea
Submitter: Zuul
Branch:    master"
1826244,2019-05-01 16:20:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826244,2019-05-05 14:18:59 UTC,Looks like the package was removed because it failed to build and it blocked transition of newer libzip. Please see https://launchpad.net/ubuntu/+source/mysql-workbench/+publishinghistory and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914761 for more details.
1826244,2019-06-05 05:19:23 UTC,When will this package be available again? Where can I track the status?
1826244,2019-06-05 14:02:47 UTC,"Thank you Hans, so it is missing but also it creates a huge negative domino effect if it gets included. For anybody coming here for the same issue, while we wait for this to resolve, go here and do those steps https://askubuntu.com/questions/1135823/install-mysql-workbench-in-ubuntu-19-04 I left an answer there for the 2 cases you will most likely run when installing it along with a link pointing over here."
1826244,2019-07-14 09:32:46 UTC,">When will this package be available again? Where can I track the status?
"
1826244,2019-08-24 08:47:28 UTC,"Looks like the issues in Debian has now been resolved and a new version of mysql-workbench has been synced to Ubuntu Eoan. Unfortunately, it fails to build :( See https://launchpad.net/ubuntu/+source/mysql-workbench/8.0.17+dfsg-1/+build/17360897 and https://launchpadlibrarian.net/437350165/buildlog_ubuntu-eoan-amd64.mysql-workbench_8.0.17+dfsg-1_BUILDING.txt.gz for details."
1826245,2019-07-30 19:08:44 UTC,"Reviewed:  https://review.opendev.org/672955
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-plugins/commit/?id=aba5c08446db1016f142bb988071cc491425cb05
Submitter: Zuul
Branch:    master"
1826245,2019-10-14 13:20:31 UTC,"Reviewed:  https://review.opendev.org/683326
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-plugins/commit/?id=24fe4789c89ca822bea3b3f01fa889f6b32002e4
Submitter: Zuul
Branch:    master"
1826246,2019-04-26 19:12:37 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655993"
1826246,2019-04-26 19:07:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655998"
1826246,2019-04-26 18:36:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655993"
1826249,2019-05-09 14:57:44 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658126"
1826249,2019-05-09 15:03:25 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658128"
1826249,2019-05-09 15:08:51 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658130"
1826249,2019-07-26 11:23:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/672955"
1826249,2019-09-28 16:56:52 UTC,"Reviewed:  https://review.opendev.org/658126
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_neutron/commit/?id=cdc9d88086426087cba34abe7cede2dded0263bf
Submitter: Zuul
Branch:    master"
1826250,2019-07-30 19:46:24 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655519
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:46:29 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655503
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:46:35 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655544
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:46:50 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655525
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:46:54 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655529
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:47:10 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655538
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:47:05 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655500
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:46:18 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655567
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:47:26 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655534
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:58:55 UTC,I do not agree with closing the PRs as this would have been a nice improvement for operating openstack as discussed per 1478133529.16340
1826250,2019-07-30 20:00:37 UTC,"Correction,  https://review.opendev.org/#/c/655559/1 is the link with the discussion"
1826250,2019-07-30 19:47:00 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655561
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:46:12 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655526
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-07-30 19:47:31 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655545
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826250,2019-04-24 20:42:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655567"
1826250,2019-04-24 17:19:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655503"
1826250,2019-04-24 18:25:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655519"
1826250,2019-04-24 17:10:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655500"
1826250,2019-04-24 18:41:16 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655526"
1826250,2019-04-24 18:46:21 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655529"
1826250,2019-04-24 18:37:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655525"
1826250,2019-04-24 19:16:04 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655538"
1826250,2019-04-24 19:58:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655544"
1826250,2019-04-24 20:04:03 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655545"
1826250,2019-04-24 20:25:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655559"
1826250,2019-04-24 20:30:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655561"
1826250,2019-04-24 18:57:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655534"
1826250,2019-07-30 19:45:57 UTC,"Change abandoned by Mohammed Naser (<email address hidden>) on branch: master
Review: https://review.opendev.org/655559
Reason: no follow up patch and adds an unnecessary variable which can just be used by an override"
1826251,2019-04-24 17:30:05 UTC,This change was made by a bot.
1826254,2019-09-13 21:53:30 UTC,"+1. Consistency makes training easier, and the different flavors of ""delete"" often come as a surprise to catalogers new to Evergreen (or so it seems, based on emails I receive!)."
1826255,2019-05-29 09:18:45 UTC,"Hi Rebecca,"
1826255,2019-09-08 04:46:13 UTC,The issue was bug #1835988
1826255,2019-07-29 04:17:29 UTC,[Expired for Mahara because there has been no activity for 60 days.]
1826255,2019-05-30 04:09:10 UTC,"Hi Paul,"
1826255,2019-05-29 00:54:52 UTC,"Hi Paul,"
1826255,2019-05-11 11:22:35 UTC,"I have the same problem as stated in #2: my Mahoodle setup does not allow login into Mahara from Moodle when switching to 7.1. Switching back to 7.0 everything works as expected. But next moodle release will require 7.1 soon.
I am on Ubuntu 16.04"
1826255,2019-05-06 01:47:26 UTC,"Hi Paul,"
1826255,2019-05-02 04:13:58 UTC,"Hi Cecilia,"
1826255,2019-05-02 02:11:09 UTC,"Hi Paul,"
1826255,2019-05-12 11:08:03 UTC,"Thank you hermannkm (h-klocker), I was beginning to think I was mad, but now someone else has the same problem makes me feel a whole lot better."
1826256,2020-10-26 20:58:42 UTC,improved consistency in this area see https://github.com/evergreen-library-system/Evergreen/pull/103
1826256,2020-11-09 04:39:29 UTC,"Pushed to rel_3_6 and master.  Thanks, Katie!"
1826257,2019-04-25 15:04:05 UTC,"I believe this bug was opened for our project Evergreen instead of Celery, which the code snippet seems to imply."
1826257,2019-04-25 16:32:17 UTC,"@bshum I assumed this was a ubuntu bug because it looked like a syntax error, but I can't replicate it :(  Maybe it is a celery bug? I'm not sure anymore."
1826258,2020-08-11 19:26:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826259,2019-07-30 06:04:19 UTC,"Found the upstream fix as below:
https://opendev.org/openstack/openstack-helm/commit/0afa508f068fa308daadf0be8c4ae23e95e7ac58"
1826259,2019-07-30 06:17:57 UTC,"""BUILD = 20190717T013000Z"" has this problem"
1826259,2019-07-31 03:22:56 UTC,"I mean the latest openstack-helm already has this default_type fix.
Are we using the latest openstack-helm?
Or we may need to add the default_type as override."
1826259,2019-07-26 22:04:47 UTC,"as @Kunpeng commented, this requires an update upon cinder helm-chart. Monitoring this issue on openstack-helm upstream for a while, and resolving it in stx.3.0 if necessary. So I would like to add stx.3.0 tag."
1826259,2019-08-21 19:24:06 UTC,"Given this was cherrypicked to the stx.2.0 release branch, I am changing the release tag from stx.3.0 to stx.2.0"
1826259,2019-08-09 15:44:59 UTC,"Reviewed:  https://review.opendev.org/672401
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=fc2423a5119423bd1fe55a7822d63bab58e783f1
Submitter: Zuul
Branch:    master"
1826259,2019-08-12 02:56:32 UTC,"Fix proposed to branch: r/stx.2.0
Review: https://review.opendev.org/675802"
1826259,2019-08-12 14:27:34 UTC,"Reviewed:  https://review.opendev.org/675802
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=9e599bd80121f4e06de411164e9a2d5726d84a20
Submitter: Zuul
Branch:    r/stx.2.0"
1826259,2019-08-08 02:58:58 UTC,"I don't known why launchpad not auto update the fix patch's link. Therefore i paste it here manual:
https://review.opendev.org/#/c/672401"
1826259,2019-07-23 03:25:16 UTC,This is not a horizon bug as Akihiro Motoki said. We can run the follow commands to fix this problem.
1826259,2019-07-31 04:13:09 UTC,"I don't know, but helm_chart default_type is ""rdb1"", will it be overrided without helm plugins of stx-config? If not, I think it is necessary."
1826259,2019-07-12 05:06:14 UTC,"@yong, yes, user can still manually select a volume type and create the volume successfully."
1826259,2019-04-26 19:18:27 UTC,"Marking release gating as horizon functionality is not working.
Assigning to Bruce to identify a prime to implement this change in stx-gui."
1826259,2019-05-09 05:43:04 UTC,"This is not a stx-gui feature, it is in Horizon Stein.
The error will pop-up when click ""Create Volume"" in the images panel, but if no volume type is selected, the volume can still be created successfully. Same result when we run:
  controller-0:/# openstack volume create --image cirros --size 1 new_volume"
1826259,2019-05-17 13:00:21 UTC,"There is no ""Create Volume"" button on the ""Images"" view."
1826259,2019-05-20 15:21:28 UTC,I am not sure this is a horizon bug or a configuration issue.
1826259,2019-07-16 13:54:00 UTC,"We have a workaround to select the volume type manually, so we don't make this issue gate Stx.2.0.
@Yan, have a try to find out in Cinder community if there is a fix for this issue.
If we have solution from Cinder upstream, we might take it in stx.3.0 or further release."
1826259,2019-06-13 02:39:00 UTC,"We are using the docker image of horizon and cinder, and we found the following error in the horzion log."
1826259,2019-07-11 06:24:44 UTC,"Based on the feedback from the cinder team, the default volume type is assumed to be public. Considering this, this is not a horizon bug apparently. I will remove horizon from the affected projects."
1826259,2019-07-11 07:29:36 UTC,"See from the log of cinder-api pod:
2019-06-24 02:29:47.321 17 INFO cinder.api.openstack.wsgi [req-c8bd9009-ac01-4463-9010-2b3365cad1ee d9061ace4fc84815aaeb43eb1a672099 6540413aaa6248eaa16e2d0cf15b018b - default default] http://cinder-api.openstack.svc.cluster.local:8776/v3/6540413aaa6248eaa16e2d0cf15b018b/types/default returned with HTTP 404
2019-06-24 02:29:47.321 17 INFO cinder.api.openstack.wsgi [req-c8bd9009-ac01-4463-9010-2b3365cad1ee d9061ace4fc84815aaeb43eb1a672099 6540413aaa6248eaa16e2d0cf15b018b - default default] http://cinder-api.openstack.svc.cluster.local:8776/v3/6540413aaa6248eaa16e2d0cf15b018b/types/default returned with HTTP 404"
1826259,2019-07-12 03:10:07 UTC,"@Yan, after this error happened, can we manually select a volume type?"
1826259,2019-05-20 15:23:50 UTC,"FYI: The similar issue on ""Create Volume"" in the ""Volumes"" table was reported as bug 1829527."
1826260,2019-05-13 16:04:07 UTC,PR to stable: https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/21
1826260,2019-05-13 15:57:22 UTC,Follow-up PR (merged already): https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/13
1826260,2019-04-26 22:18:07 UTC,PR has been updated with a fix that will ensure that changes to basic_auth.csv on the leader will be propagated to the other master units automatically (and immediately).
1826260,2019-04-25 18:26:41 UTC,"In case it helps, we ran this to propagate changes to that file: juju run --unit <kubernetes-master leader> charms.reactive clear_flag authentication.setup"
1826260,2019-04-25 14:29:07 UTC,"Yeah, it appears there's second part to this bug, and that's it - the file changes are not distributed to non-leaders reliably. Working on a fix for that too."
1826260,2019-04-25 06:38:49 UTC,@Tim
1826260,2019-04-25 03:18:51 UTC,https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/10
1826260,2019-04-24 20:05:38 UTC,subscribed ~field-high
1826260,2019-04-24 20:05:30 UTC,unsubscribed ~field-critical
1826260,2019-04-24 19:35:57 UTC,"basic_auth.csv will be naively overwritten, inadvertently deleting additions, any time setup_basic_auth() (see https://github.com/charmed-kubernetes/charm-kubernetes-master/blob/master/reactive/kubernetes_master.py#L1721) is called."
1826260,2019-04-24 19:25:51 UTC,subscribed ~field-critical
1826262,2019-08-19 07:24:35 UTC,I'm still seeing this from time to time.
1826262,2019-08-18 04:17:25 UTC,[Expired for Snapcraft because there has been no activity for 60 days.]
1826262,2019-06-18 15:18:30 UTC,"Yeah, I see this too."
1826262,2019-06-03 15:05:05 UTC,"> - what is the version of snapcraft?
"
1826262,2019-06-05 09:21:12 UTC,And attached is a debug log of snapcraft from a failed run.
1826262,2019-06-03 14:47:15 UTC,"Hi there, thanks for the report. To better triage, mind if I ask for answers to the following questions:"
1826262,2019-06-05 11:44:50 UTC,A more verbose log with the …DEBUG… variable set inside the instance as well.
1826263,2019-04-24 20:32:28 UTC,"Kristy Bauman worked on this at the docs hackfest for #evgils19.
Pull request # 84 submitted 4/24/19."
1826263,2019-04-25 16:19:23 UTC,"For easier finding, here's the GitHub branch:"
1826263,2019-08-01 18:51:14 UTC,"Thanks, Linnae, Katie, Kristy, and Remington.  Improving consistency in our documentation is always welcome.  I've taken your change and added it to the master, rel_3_3, rel_3_2 and rel_3_1 branches (aka the Current development version, 3.3, 3.2, and 3.1 official docs)."
1826266,2019-07-10 15:25:28 UTC,"Same thing here, it is really useful feature lost! It is really frustrating."
1826266,2021-02-03 15:22:55 UTC,"Just as a status update,
we are waiting on https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 to be merged right now. Perhaps people wouldn't mind doing a thumbs up to bump that PR?"
1826266,2020-12-04 23:01:33 UTC,"Currently, you can track the status of the MR for Nautilus for the fix of this regression: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573"
1826266,2019-12-03 14:04:56 UTC,"The Copy was the most important feature of the nautilus, now it does not work like it use to be. It was like that since 19.04. The same issue persists on 19.10. Please, what should we do to fix it? How can we accelerate that? Do you know any workaround for that?"
1826266,2019-08-01 10:50:10 UTC,"This change has significantly reduced useability when working with large numbers of files in different programs. It lowers the useability to that of Apple's OS X (where copying only copies the filename and not the path).
Also related to the lost functionality where copying or drag/dropping the path directory buttons in Nautilus no longer copies the folder path as text."
1826266,2019-07-29 10:18:43 UTC,"I agree. This was one of the first changes i notices upon switching to ubuntu 19. Its been annoying the hell out of me ever since. I would really like to see this restored to the original behavior where Ctrl+C on a file or folder just copies the absolute path to your clipboard.
Or at the very least i would like a config option to restore the old behavior."
1826266,2019-05-23 12:45:16 UTC,"Same here.
Actually, it was a killer feature for decades as for me and many my colleagues."
1826266,2019-04-29 23:21:05 UTC,"I am also one of those who want this. It was very useful to upload files in emails/browser, to open certain files in any program without browsing for the file. Hope it comes back, soon."
1826266,2019-04-30 14:17:26 UTC,"The new comments seem slightly different from the original, the report was about copy of file path and now comments are talking about interactions with the gtk fileselector which seems a different problem?"
1826266,2019-04-30 16:30:21 UTC,We are talking about the same issue. In the previous versions when you pressed Ctrl+C in nautilus after selecting a file the resulting data on the clipboard was the file path of this selected file.
1826266,2019-04-24 20:07:58 UTC,"I believe this is the same bug:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1824157"
1826266,2019-04-24 20:10:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826266,2019-04-25 08:36:23 UTC,"Thanks, could you reprort it upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/?"
1826266,2019-04-29 09:05:25 UTC,"For you rinformation, this issue is filed with Gnome as https://gitlab.gnome.org/GNOME/nautilus/issues/634"
1826266,2019-04-29 09:27:11 UTC,Thanks
1826266,2019-04-30 13:43:50 UTC,I can confirm that I have the same issue. It was terribly useful in the previous versions of Ubuntu for copying/uploading files.
1826267,2019-07-30 15:57:40 UTC,fixed in https://review.opendev.org/#/c/651188/
1826267,2019-08-08 17:21:26 UTC,The fix was merged into the master branch when the bug was filed.
1826267,2019-08-08 17:23:19 UTC,The fix can be backported to the stable branches.
1826269,2019-04-25 06:49:44 UTC,"James - can you please add more insight to the bug, like is it caused by some backlevel version of python-os-xenapi package? On which distributions?"
1826269,2019-04-25 09:01:04 UTC,"Also, which images? Source/binary? Container OS? Host OS? Release of kolla/kolla-ansible?"
1826269,2019-04-25 15:36:27 UTC,"Kolla- Rocky, 7.0.1
kolla-base-distro: centos
kolla-install-type: binary
DomU - CentOS 7 minimal
XenServer 7.0.0"
1826270,2019-07-20 18:02:50 UTC,"It's fixed in latest nightly:
kicad-r13792.920f128cc-x86_64.exe
It's also fixed in kicad-5.1-jenkins-335-x86_64.exe"
1826270,2019-07-18 11:25:43 UTC,"@Andrey, you are the QA. Please test the latest build on
https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/testing/5.1/"
1826270,2019-07-18 09:45:06 UTC,stable v5.1.2_2 on windows
1826270,2019-05-03 15:30:31 UTC,"I have the same problem with KiCad 5.1.2., WIndows 10.
Additionally when I try to place the track on a circular board (made with KiCad edition 5.1.1) I get something strange - see attached picture."
1826271,2019-04-25 07:24:26 UTC,"Hi Michael,
none of the updates we have made to virt-manager since Bionic released seems related to the issue you are describing."
1826271,2019-04-25 15:55:09 UTC,"christian,"
1826271,2019-04-26 07:29:43 UTC,"Hi,
I'm not at all an dconf expert.
But after identifying that even base dconf-editor does not let you save things I think we can eliminate virt-manager from the equation."
1826271,2019-11-29 10:09:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826271,2019-11-29 10:45:16 UTC,Thought I was hitting this same issue - turns out it wasn't quite the same as I did NOT have dconf-editor available.
1826273,2019-04-25 13:10:11 UTC,Hi! Thanks for reporting this issue.
1826273,2019-04-25 18:16:54 UTC,"Thank you for your reply. The paper is recently published at NDSS 2019.
Please feel free to make this bug public."
1826274,2019-04-26 02:46:12 UTC,"The bluez version hasn't changed (in any meaningful way) between cosmic and disco. So I don't think that's the cause. Also, those log messages are from the kernel."
1826274,2019-06-25 04:17:40 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1826276,2019-05-18 09:10:09 UTC,"To be accurate GTK+ 3.24.5 have lost this possibility, as this is a GTK feature.
And there is nothing I can do, except hove a future new GTK version will fix."
1826276,2019-05-18 09:10:35 UTC,and open a bug at GTK github :)
1826278,2019-04-24 21:49:02 UTC,"Appear like some invisible ""Keep zone"" is on the left size."
1826278,2019-04-25 09:33:35 UTC,This looks like a dupe of https://bugs.launchpad.net/kicad/+bug/1826014 - it what happens when you are routing near the arc corners (i.e. overlapping in x or y).
1826278,2019-04-25 13:17:40 UTC,"@John, you may be right. Sometimes appeared some green wire as report in lp:1826014 https://imgur.com/a/RpNTdIO"
1826278,2019-04-25 14:05:13 UTC,"@Tom, should the fix for this be cherry-picked onto 5.1? The commit mentioned in the commit message was."
1826278,2019-04-25 14:19:03 UTC,"Yes, please push it to 5.1."
1826278,2019-04-25 14:24:24 UTC,"Sorry, I don't have commit privileges, someone else will have to :p"
1826278,2019-04-25 18:38:49 UTC,Setting to 'In Progress' so this isn't forgotten.
1826278,2019-04-25 22:54:02 UTC,I have pushed this to 5.1 as well as a follow-up commit that fixes the fix (it only worked for circles and arcs that had a 0 starting angle).
1826278,2019-04-25 23:29:10 UTC,Thanks @John!
1826279,2019-08-22 15:24:41 UTC,All done! Thanks crydotsnake for the screenshots and help!
1826279,2019-08-21 20:33:30 UTC,It looks like someone updated the Music Player and we have the Video Player  and KDE Talk to update as well.
1826279,2019-08-21 23:03:06 UTC,VLC and Kontact images have been replaced with images from crydotsnake on IRC.
1826279,2019-08-22 03:30:32 UTC,"Thanks for taking this on, Aaron!"
1826280,2019-04-24 22:14:26 UTC,See a subnets tab that has the cue.
1826284,2020-04-02 00:28:19 UTC,"Reviewed:  https://reviews.mahara.org/10335
Committed: https://git.mahara.org/mahara/mahara/commit/68ebdd9d407ba5cb8f5cf476fa781a0339c8b75e
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:18 UTC,"Reviewed:  https://reviews.mahara.org/10353
Committed: https://git.mahara.org/mahara/mahara/commit/0307a929f0808761f43cca4d2f5ecd3b7986e0bb
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:19 UTC,"Reviewed:  https://reviews.mahara.org/10307
Committed: https://git.mahara.org/mahara/mahara/commit/f7406158b1bf15eac3f4f4eeb4432be7e6da363a
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:19 UTC,"Reviewed:  https://reviews.mahara.org/10300
Committed: https://git.mahara.org/mahara/mahara/commit/4f8eed9fcd38db8d274ce6bdcf8d9939e749e743
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:19 UTC,"Reviewed:  https://reviews.mahara.org/10318
Committed: https://git.mahara.org/mahara/mahara/commit/1a7efc06a54d762bd5d86ad151a0fe8d0b2cdb86
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:29:57 UTC,Any issues found now that this is merged can be their own bug reports
1826284,2020-04-02 00:28:20 UTC,"Reviewed:  https://reviews.mahara.org/10298
Committed: https://git.mahara.org/mahara/mahara/commit/e8dc71d351796e9e9bef54a9cece81d4739b6d71
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:20 UTC,"Reviewed:  https://reviews.mahara.org/10294
Committed: https://git.mahara.org/mahara/mahara/commit/ee9dd1582a9deb245ecd47dfa08bc14a7bd347ff
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:20 UTC,"Reviewed:  https://reviews.mahara.org/10267
Committed: https://git.mahara.org/mahara/mahara/commit/63ccc41ffe4cf65d562dd2617b33c11e35d641c8
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:21 UTC,"Reviewed:  https://reviews.mahara.org/9848
Committed: https://git.mahara.org/mahara/mahara/commit/d3425360bbc8aeb1b3008f942d2dc6b7969e0e74
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:21 UTC,"Reviewed:  https://reviews.mahara.org/9849
Committed: https://git.mahara.org/mahara/mahara/commit/177cdb2db4d0d53eaac6fd82deb2536b708f1082
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:18 UTC,"Reviewed:  https://reviews.mahara.org/10349
Committed: https://git.mahara.org/mahara/mahara/commit/d761c4f5109329915cda96d10f3bc7f135992f3a
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-02 00:28:19 UTC,"Reviewed:  https://reviews.mahara.org/10301
Committed: https://git.mahara.org/mahara/mahara/commit/d5c331d566cd7be9b995c8913fd1cc588e2ffed5
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-04-01 17:42:31 UTC,It goes into Mahara 20.04 as experimental feature.
1826284,2020-04-02 00:28:18 UTC,"Reviewed:  https://reviews.mahara.org/10344
Committed: https://git.mahara.org/mahara/mahara/commit/deff2790b4e0e3d2cb8d645b2dcb0b3da2945820
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2020-03-10 21:48:27 UTC,"Reviewed:  https://reviews.mahara.org/9800
Committed: https://git.mahara.org/mahara/mahara/commit/84712c3797b64083b6bb2473abdb9cf2f3a3032d
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1826284,2020-03-31 19:17:07 UTC,"Reviewed:  https://reviews.mahara.org/10348
Committed: https://git.mahara.org/mahara/mahara/commit/02c99babdef91dd5ed9711d5716b8dde0bf9c023
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2019-08-18 21:16:41 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10267"
1826284,2019-09-05 00:58:18 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10294"
1826284,2019-09-05 20:56:08 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10298"
1826284,2019-09-05 21:49:00 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10300"
1826284,2019-09-06 03:33:33 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10307"
1826284,2019-09-09 21:17:34 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10318"
1826284,2019-09-05 22:43:41 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10301"
1826284,2019-09-12 22:02:38 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10340"
1826284,2019-09-13 03:56:24 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10344"
1826284,2019-09-16 22:10:29 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10349"
1826284,2019-11-02 03:16:57 UTC,Also see bug #1825231
1826284,2020-02-02 01:12:05 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10743"
1826284,2020-03-09 20:10:58 UTC,"Reviewed:  https://reviews.mahara.org/10293
Committed: https://git.mahara.org/mahara/mahara/commit/ff63091b31b2d09b4f44e1daacf68f22a159bc7c
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826284,2019-09-11 02:09:18 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10335"
1826287,2019-04-26 09:44:20 UTC,"Thank you for the level of detail, Dirk. We have"
1826287,2019-10-12 14:43:28 UTC,"Has been a while, but I'd like to add some newer findings anyway.
I have stopped my Linux experiments on this meanwhile, but some observations with Win7 might give a hint..."
1826287,2019-04-26 16:31:38 UTC,"> That still leaves a problem 8730, of course.
"
1826287,2019-04-26 16:10:40 UTC,"> .....I completely forgot about this fallback mechanism.
"
1826287,2019-04-26 15:08:33 UTC,In the first post it was said:
1826287,2019-04-25 19:10:29 UTC,"user@user-ThinkPad-T60p:~$ avahi-browse -rt _uscan._tcp
+   wls3 IPv6 HP OfficeJet Pro 8730 [C90C3D]                _uscan._tcp          local
+   wls3 IPv4 HP OfficeJet Pro 8730 [C90C3D]                _uscan._tcp          local
=   wls3 IPv4 HP OfficeJet Pro 8730 [C90C3D]                _uscan._tcp          local
   hostname = [HP8730.local]
   address = [192.168.178.40]
   port = [8080]
   txt = [""duplex=T"" ""is=platen,adf"" ""cs=binary,color,grayscale"" ""rs=eSCL"" ""representation=images/printer.png"" ""UUID=37481cb7-ce79-5345-c7cb-2c5069ed6e5a"" ""mopria-certified=1.3"" ""note="" ""adminurl=http://HP8730.local."" ""ty=HP OfficeJet Pro 8730"" ""pdl=application/octet-stream,application/pdf,image/jpeg"" ""vers=2.5"" ""txtvers=1""]
=   wls3 IPv6 HP OfficeJet Pro 8730 [C90C3D]                _uscan._tcp          local
   hostname = [HP8730.local]
   address = [192.168.178.40]
   port = [8080]
   txt = [""duplex=T"" ""is=platen,adf"" ""cs=binary,color,grayscale"" ""rs=eSCL"" ""representation=images/printer.png"" ""UUID=37481cb7-ce79-5345-c7cb-2c5069ed6e5a"" ""mopria-certified=1.3"" ""note="" ""adminurl=http://HP8730.local."" ""ty=HP OfficeJet Pro 8730"" ""pdl=application/octet-stream,application/pdf,image/jpeg"" ""vers=2.5"" ""txtvers=1""]"
1826287,2019-04-25 16:35:04 UTC,"Ah. I noted ""...Mint 19.1 fresh install..."", which has HPLIP 3.17.10, but failed to absorb ""...HPLIP 3.19.3..."". We are on the same page now! 3.19.3 is the newest HPLIP and has a partial fix for bug 1797501. Please see Messages #20, #21 and #22 at bug 1822762."
1826287,2019-04-25 17:52:34 UTC,Ok. Obviously I am not allowd to attach files here. :-/
1826287,2019-04-25 17:19:38 UTC,Dear Brian
1826287,2019-04-25 16:39:01 UTC,Forgot. Please post the output of
1826287,2019-04-25 14:14:38 UTC,"Thanks Brian for the quick response!   But it seems, this doesn't really solve the problem."
1826287,2019-04-25 10:39:44 UTC,Probably bug 1797501. Fixed for the 8730 in recent HPLIP versions and can be worked round (bug 1817214).
1826287,2019-04-25 19:05:08 UTC,Re: 'systemctl stop cups'...
1826290,2020-11-26 10:30:41 UTC,"For the record, back in April 2019 Canonical requested a separate MLS API key to use in geoclue in Ubuntu, and the request was initially acknowledged, but then it was put on hold on Mozilla's end and we never heard back from them, despite a couple of follow-up e-mails."
1826290,2021-02-02 22:12:17 UTC,@Sebastien Bacher Just doing an occasional Python GET request to the same URL others are using: https://location.services.mozilla.com/v1/geolocate?key=geoclue
1826290,2021-01-28 00:20:14 UTC,"@osomon any news on the key request for Ubuntu ? I'm hitting usage limits randomly with the generic ""geoclue"" key which makes redshift not work sometimes. It's the same error as @heap"
1826290,2020-12-14 09:43:51 UTC,"@Robin, how do you trigger the issue exactly? could you describe what website you try and what error you get?"
1826290,2020-12-11 21:19:45 UTC,Update: key has not worked for several days.
1826290,2020-11-27 12:24:57 UTC,Update: key is working again.
1826290,2020-11-25 22:04:00 UTC,"Updated upstream bug: https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/136, opened 20 OCT 2020"
1826290,2020-11-26 20:55:40 UTC,Can confirm that this stopped working 2 days ago. But when called manually from a script:
1826290,2019-06-21 14:15:53 UTC,"Is anyone still getting the issue? It seems to work fine here now, GNOME was also discussing the issue so maybe they got the quota increased?"
1826290,2019-04-25 06:13:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826290,2019-04-25 20:11:39 UTC,Same.
1826290,2019-04-25 19:26:07 UTC,I tried it again just now (roughly around the same time of day I tried this previously):
1826290,2019-04-25 16:03:31 UTC,I tried it around 02:00 UTC on 25 April so the daily limit was probably reset by the time you tested it. I did check around and came across this issue on geoclue's GitLab https://gitlab.freedesktop.org/geoclue/geoclue/issues/101
1826290,2019-04-25 10:08:55 UTC,"Tested just now (25 April, 10:00 UTC) and a query to the service with the ""geoclue"" key returns a valid location. I wonder if someone already increased the quota for that key and the issue can be considered solved, or if it's just a lucky coincidence and the daily limit was reset before I tried."
1826290,2019-04-25 06:32:19 UTC,"I would imagine that the currently shipped API key of ""geoclue"" is some kind of universal default. Now that the use of keys is apparently being monitored and limited, perhaps it would be possible for Ubuntu to register its own key, and then ship that with this package?"
1826290,2019-06-21 14:25:49 UTC,"(seems like GNOME got it somehow resolved for now, https://gitlab.gnome.org/Teams/Board/issues/97 mentions it)"
1826291,2020-11-20 04:17:21 UTC,[Expired for pluma (Ubuntu) because there has been no activity for 60 days.]
1826297,2019-04-25 09:52:58 UTC,"I'm guessing the issue could be that if multiple units are requesting the
same resource, we aren't handling the caching and queuing on the controller
correctly. The controller should be downloading the resource on demand
(some charms have very large resources, so we don't want to cache them
unless they are needed). My guess is that multiple requests for the same
resource is causing confusion in the queuing system, and not having one
request start the download, and the rest be blocked until that is finished."
1826300,2019-04-25 04:20:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1826310,2019-04-26 02:49:45 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1826310,2019-04-26 02:52:18 UTC,"Also, it appears you are using the old graphics driver (""intel""). The newer driver which should work better is called ""modesetting""."
1826310,2019-06-25 04:17:42 UTC,[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.]
1826311,2019-04-29 14:34:18 UTC,"Thanks, it looks like the bug you are refering to is https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/29"
1826311,2019-04-25 08:34:52 UTC,"Thank you for your bug report, could you also report it upstream on https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/ ? They probably have more ideas about the topic that us as distributors do"
1826311,2019-04-26 02:19:56 UTC,"Looks like there is a similar open bug, so I will add a comment to it with additional info"
1826314,2019-04-25 06:18:54 UTC,It's not finding head because you called find with an empty string as the second parameter. If you call if you change the find call to this:
1826316,2019-04-29 06:09:09 UTC,"OK, so this is a real bug..."
1826316,2020-02-17 01:32:09 UTC,"The upstream bug was never fixed, just closed. So removing the task..."
1826316,2020-01-24 09:02:39 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1826316,2019-05-12 18:44:46 UTC,"since it can be reproduced in certain scenarios with ubuntu, kubuntu and arch, is there some output that i should provide to try to track driver issues?"
1826316,2019-05-12 17:48:47 UTC,"I managed to reproduce it on archlinux + kde. Not sure if this would help, but i can provide outputs from arch."
1826316,2019-05-06 01:45:16 UTC,Please let us know if and when you can reproduce the bug. Otherwise it will automatically close in 60 days.
1826316,2019-05-06 01:44:34 UTC,"""Long story short - i cannot reproduce it:"
1826316,2019-04-29 11:06:36 UTC,Done.
1826316,2019-04-29 03:07:00 UTC,Thanks!
1826316,2019-04-29 05:44:12 UTC,"so, wayland started working properly."
1826316,2019-04-27 06:18:00 UTC,xrandr-xorg.txt
1826316,2019-04-26 02:56:42 UTC,Please:
1826316,2019-04-26 06:16:27 UTC,And ideally run it in a Xorg session.
1826316,2019-04-26 06:15:25 UTC,Please run that as yourself in a regular desktop terminal window:
1826316,2019-04-26 05:25:23 UTC,"about xrandr.txt... this happens with wayland session (the bug is tagged properly i think)
honestly, i didnt try the xorg session... so the file is empty"
1826316,2019-04-26 05:21:34 UTC,lspci.txt
1826316,2019-04-26 05:21:12 UTC,journal.txt
1826316,2019-04-26 05:20:43 UTC,edids.txt
1826316,2019-04-26 05:20:26 UTC,dmesg.txt
1826316,2019-04-26 02:58:09 UTC,Please also:
1826316,2019-04-27 06:18:28 UTC,xrandr-wayland.txt
1826317,2019-04-25 06:14:15 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655617"
1826317,2019-04-25 06:25:00 UTC,"[root@localhost ~]# rpm -qa | grep qemu-img
qemu-img-ev-2.12.0-18.el7_6.3.1.x86_64
[root@localhost ~]# rpm -e --nodeps qemu-img-ev-2.12.0-18.el7_6.3.1.x86_64
[root@localhost ~]# rpm -qa | grep qemu-img
[root@localhost ~]# qemu-img
-bash: qemu-img: command not found
[root@localhost ~]#"
1826317,2020-03-26 10:01:18 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/715147"
1826318,2019-05-02 12:54:24 UTC,"Hi Duane,"
1826319,2019-11-02 17:09:25 UTC,"This is no longer a mere feature request: cgdb 0.6.7 doesn't work properly with Ubuntu's GDB 8.2.91 (Ubuntu 19.04) or GDB 8.3 (Ubuntu 19.10) as they use colored output by default, which cgdb can only deal with starting with version 0.7.0.  See bug #1850993."
1826319,2019-11-01 23:06:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826322,2019-04-25 06:50:29 UTC,Once I got an error report while I was trying to import an image by drag and drop
1826322,2019-07-29 22:13:59 UTC,It did the same thing on me except on the first try then I tried uninstalling and reinstalling Pinta now it just crashes and closes without any warning right after I copy the second image...
1826324,2019-04-25 08:47:40 UTC,Do you have a specific example of when this might be necessary?
1826324,2019-11-12 04:17:54 UTC,[Expired for kolla because there has been no activity for 60 days.]
1826326,2019-07-13 09:53:38 UTC,"Finally found out a bit more about this: it seems to be a theme bug. When testing Manjaro, I noticed that the context menu on initial Caja window opening displayed an arrow at the bottom to show more options, among which the ""empty trash"" one. I first thought it was because the apps versions were different and it has been fixed on Manjaro (as it's a rolling release version). But trying a different theme on Ubuntu MATE like Arc shows the same arrow."
1826326,2019-07-14 00:07:48 UTC,"Issue confirmed for me on Ambiant-MATE-Dark 19.04
ubuntu-mate-artwork 19.04.0
ubuntu-mate-themes  9.04.0"
1826326,2019-07-14 00:08:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826326,2019-07-14 00:15:18 UTC,damn  mate themes...typo I meant 19.04.0
1826327,2019-08-08 10:52:39 UTC,"Reviewed:  https://review.opendev.org/655845
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ad9e8786a3823895624e892c6a233d16d530d830
Submitter: Zuul
Branch:    master"
1826327,2019-11-11 15:39:57 UTC,This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.
1826327,2019-11-06 01:14:36 UTC,This issue was fixed in the openstack/kolla 9.0.0.0rc1 release candidate.
1826327,2019-09-09 09:18:46 UTC,This issue was fixed in the openstack/kolla 7.0.4 release.
1826327,2019-09-09 09:17:40 UTC,This issue was fixed in the openstack/kolla 6.2.3 release.
1826327,2019-06-27 13:47:15 UTC,"Reviewed:  https://review.opendev.org/666082
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=ac8609c0f1ebe0a6f87979811f5130286b4e9b18
Submitter: Zuul
Branch:    stable/stein"
1826327,2019-07-18 00:38:15 UTC,This issue was fixed in the openstack/kolla 8.0.0.0rc2 release candidate.
1826327,2019-06-19 21:51:20 UTC,"Reviewed:  https://review.opendev.org/666084
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=7951713790464eedaec1e59851a42febc4acc346
Submitter: Zuul
Branch:    stable/queens"
1826327,2019-04-25 09:03:41 UTC,"Looks like we're skipping B303, which is why this doesn't fail pep8."
1826327,2019-06-18 17:53:42 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/666084"
1826327,2019-06-18 17:53:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/666083"
1826327,2019-06-18 17:53:09 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/666082"
1826327,2019-06-18 11:57:33 UTC,"Reviewed:  https://review.opendev.org/655623
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0a2dc8aa1d267da3c1c2925b3f292bd96aa50edb
Submitter: Zuul
Branch:    master"
1826327,2019-04-26 09:18:11 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655845"
1826327,2019-06-24 15:57:38 UTC,"Reviewed:  https://review.opendev.org/666083
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=8001de09236504b6bfd7aa01ec5657ef0fb2136e
Submitter: Zuul
Branch:    stable/rocky"
1826332,2020-08-09 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1826332,2020-06-09 05:05:50 UTC,"Probably eventually, sure. But my life is too busy for that right now. Please test the version I reported?"
1826332,2020-06-09 04:52:27 UTC,Please test 20.04.
1826332,2019-04-25 07:30:08 UTC,This change was made by a bot.
1826332,2019-04-25 07:24:28 UTC,Original report: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1744737
1826334,2019-05-03 09:08:08 UTC,Hardware Certification have begun testing this -proposed kernel.
1826334,2019-05-10 04:52:19 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/M3jZxJdV/962-pi-kernel-4150-103537-30-18-pi3"
1826334,2019-05-10 09:26:39 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/raspi2/4.15.0-1035.37/raspi2-4.15-proposed-published.html"
1826334,2019-05-14 19:03:54 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1036.38
1826335,2019-05-14 19:04:02 UTC,This bug was fixed in the package linux-snapdragon - 4.15.0-1053.57
1826335,2019-05-09 11:23:22 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/snapdragon/4.15.0-1052.56/snapdragon-4.15-proposed-published.html"
1826335,2019-04-29 12:39:26 UTC,The following packages ended up in the wrong component in the -proposed pocket:
1826335,2019-05-02 17:47:08 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/vH774ROa/968-dragonboard-kernel-4150-105256-88-18"
1826335,2019-05-03 09:08:21 UTC,Hardware Certification have begun testing this -proposed kernel.
1826336,2019-05-03 09:08:02 UTC,Hardware Certification have begun testing this -proposed kernel.
1826336,2019-05-07 06:32:05 UTC,"4.15.0-1037.42 - oem
Regression test CMPL, RTB."
1826336,2019-05-09 11:28:17 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/oem/4.15.0-1037.42/oem-4.15-proposed-published.html"
1826336,2019-05-14 19:03:14 UTC,This bug was fixed in the package linux-oem - 4.15.0-1038.43
1826337,2019-05-07 15:32:33 UTC,"ubuntu_kvm_tests: 1821394 - vmx tests fail in kvm_unit_tests
ubuntu_kvm_tests: 1821390 - apic-split will fail in kvm_units_tests
libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only spotted on t2.small, passed on the rest
ubuntu_kernel_selftests - CPU Hotplug Failed t2.small Only. : running psock_fanout test failed on net test t2.small ONLY
vmx tests fail in kvm_unit_tests (1821394)
cpu_hotplug test failed because there is only 1 CPU (1812149)
ubuntu_lxc: 1828073: lxc-test-apparmor-mount fails on aws : r3.large"
1826337,2019-05-14 19:09:31 UTC,This bug was fixed in the package linux-aws-hwe - 4.15.0-1039.41~16.04.1
1826338,2019-05-14 22:53:43 UTC,This bug was fixed in the package linux-aws - 4.15.0-1039.41
1826338,2019-05-14 22:54:56 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826338,2019-05-15 11:38:42 UTC,This bug was fixed in the package linux-aws - 4.15.0-1039.41
1826339,2019-05-14 19:10:00 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1032.34~16.04.1
1826340,2019-05-15 20:08:32 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1032.34~16.04.1
1826340,2019-05-14 19:02:44 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1032.34
1826340,2019-05-14 19:10:00 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1032.34~16.04.1
1826340,2019-05-15 11:39:30 UTC,This bug was fixed in the package linux-gcp - 4.15.0-1032.34
1826342,2019-05-14 19:02:52 UTC,This bug was fixed in the package linux-gke-4.15 - 4.15.0-1032.34
1826343,2019-05-07 04:05:36 UTC,"4.15.0-1033.33 - kvm
Regression test CMPL, RTB."
1826343,2019-05-14 19:03:09 UTC,This bug was fixed in the package linux-kvm - 4.15.0-1034.34
1826345,2019-04-30 17:27:00 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826346,2019-05-14 19:10:35 UTC,This bug was fixed in the package linux-oracle - 4.15.0-1013.15~16.04.1
1826348,2019-05-14 19:03:43 UTC,This bug was fixed in the package linux-oracle - 4.15.0-1013.15
1826348,2019-05-14 19:10:35 UTC,This bug was fixed in the package linux-oracle - 4.15.0-1013.15~16.04.1
1826348,2019-05-15 11:43:39 UTC,This bug was fixed in the package linux-oracle - 4.15.0-1013.15
1826348,2019-05-15 20:11:09 UTC,This bug was fixed in the package linux-oracle - 4.15.0-1013.15~16.04.1
1826350,2019-05-08 16:25:48 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826350,2019-05-13 10:53:47 UTC,"4.15.0-1006.7 - fips
Regression test CMPL, RTB."
1826351,2019-05-08 21:42:34 UTC,"monotonic_time: 1774959 : clock test in monotonic_time will fail on Azure Instances
kvm_unit_tests: 1824228: ept test fails in kvm_unit_tests , 1821394: vmx tests fail in kvm_unit_tests , 1821152:"
1826352,2019-05-14 19:52:13 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
1826352,2019-05-13 13:06:27 UTC,"Regression Tests:
monotonic:1774959(clock test in monotonic_time will fail on Azure Instances Edit)
umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4(1821905), apic test in kvm-unit-test failed on azure cloud with 4.13/4.14 kernel(1748103)"
1826354,2019-05-08 21:42:14 UTC,"monotonic_time: 1774959 : clock test in monotonic_time will fail on Azure Instances
kvm_unit_tests: 1824228: ept test fails in kvm_unit_tests , 1821394: vmx tests fail in kvm_unit_tests , 1821152:"
1826354,2019-05-14 19:09:49 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49
1826354,2019-05-14 19:52:13 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
1826354,2019-05-15 20:07:21 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49
1826354,2019-05-16 07:38:42 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
1826356,2019-05-08 08:20:33 UTC,"4.15.0-49.52~16.04.1 - lowlatency
Regression test CMPL, RTB."
1826357,2019-05-03 09:08:33 UTC,Hardware Certification have begun testing this -proposed kernel.
1826357,2019-05-08 08:00:01 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.15.0-49.52~16.04.1/xenial-4.15-proposed-published.html"
1826357,2019-05-08 08:19:59 UTC,"4.15.0-49.52~16.04.1 - lowlatency
Regression test CMPL, RTB."
1826357,2019-05-14 19:10:30 UTC,This bug was fixed in the package linux-hwe - 4.15.0-50.54~16.04.1
1826358,2019-05-14 19:00:51 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1826358,2019-05-14 22:55:00 UTC,"The verification of the Stable Release Update for linux-aws has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826358,2019-05-13 09:47:58 UTC,Verification tests completed with the bionic kernel in -proposed.
1826358,2019-05-15 11:02:03 UTC,This bug was fixed in the package linux - 4.15.0-50.54
1826358,2019-05-06 06:43:46 UTC,"4.15.0-49.53 - generic
Regression test CMPL, RTB."
1826358,2019-05-02 19:03:40 UTC,"Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/7uzk3wuy/963-pc-kernel-4150-4953-210-18"
1826358,2019-05-07 04:07:52 UTC,"Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-49.53/bionic-proposed-published.html"
1826358,2019-05-03 09:07:50 UTC,Hardware Certification have begun testing this -proposed kernel.
1826360,2019-06-10 21:28:28 UTC,"You could just start a new file, after all you use a personal finance tool to track your business, and payee for personal usage do not vary that much."
1826360,2019-08-10 16:34:21 UTC,"from #1838404
if we could change the payee order and have the most used ones at the top. Custom order or even sorting them by usage would work."
1826362,2019-10-15 13:23:15 UTC,I've added the snapd project task to this bug report. I think it has several duplicates and we'll find and de-duplicate as we garden the bug tracker some more over the next few weeks.
1826362,2019-10-15 13:53:07 UTC,Thanks !
1826368,2019-04-25 08:49:50 UTC,This is a regression resulting from Bug #1780348
1826368,2019-04-25 08:55:09 UTC,"I can be worked around by setting:
juju config neutron-gateway sysctl=''"
1826368,2019-04-25 08:56:01 UTC,"Also note the workaround mentioned in:
https://ask.openstack.org/en/question/121359/error-neutron-gateway-in-openstack-on-lxd/?answer=121385#post-id-121385"
1826368,2019-04-25 09:11:59 UTC,"Heh, crossed wires. Agreed the charm should handle this situation. Possibly it could include an lxd profile as per https://docs.jujucharms.com/2.5/en/clouds-lxd-advanced , however the default sysctls don't include the ones set in bug #1780348 so ideally that should be extended"
1826368,2019-05-14 16:15:02 UTC,This sounds like a documentation issue and config validation issue associated with config('sysctl').  Marking as low priority as there is a workaround.
1826369,2019-04-26 18:40:47 UTC,"Hello,"
1826369,2019-04-27 01:41:14 UTC,We should probably change the warning to say 'cloud-init collect-logs'.
1826369,2019-06-26 04:17:24 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1826376,2020-08-10 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1826376,2020-06-10 12:58:56 UTC,Sorry I won't be able to test 20.04 as I don't have a Chelsio NIC anymore
1826376,2019-04-25 09:00:06 UTC,This change was made by a bot.
1826376,2020-06-09 04:50:38 UTC,Please test 20.04.
1826378,2019-04-25 09:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826378,2019-04-25 09:44:59 UTC,"No, there's no log missing."
1826378,2019-04-25 10:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826378,2019-04-29 14:45:08 UTC,~xnox's changes to our autopkgtests are now applied and in -proposed for both cosmic and bionic.
1826380,2019-07-31 06:54:56 UTC,"Hello,
several questions here:
1. Do they work after updating your kernel (sudo apt dist-upgrade)
2. Can you give 19.04 Disco a try to see if this can be reproduced?
3. Can you attach the output for the following commands:
  udevadm info -e
  cat /proc/bus/input/devices"
1826380,2019-09-30 04:17:22 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1826381,2019-05-25 22:15:10 UTC,"Interesting, it could possibly look like some ipv6 related options isn't present in the client configuration and thus the client rejects the IPv6 negotiation."
1826382,2019-04-25 19:47:39 UTC,What release is this?
1826382,2019-04-25 20:01:33 UTC,"Looking at stein, the SchedulerReportClient used by the ResourceTracker is a singleton per nova-compute process, and that client adapter is stored within the report client upon init:"
1826382,2019-04-25 20:13:30 UTC,I'm also not sure how common this should be expected and therefore this could be very low priority to try and deal without outside of the SIGHUP suggestion earlier (if SIGHUP weren't broken at the moment).
1826382,2019-04-26 13:33:18 UTC,"Hi Matt,
    Thank you for taking the time to triage the bug. I have tried out the decorator approach you mentioned ( https://paste.ubuntu.com/p/PDtwdNrqbx/ ) and it seems to work well. I am recreating a client whenever a 400 is returned because parsing the error string looking for the http/https error message looked brittle (and Apache specific). Do you think that's ok ?"
1826382,2019-05-01 03:51:31 UTC,"Based on the error message, this looks like a problem with how apache (or something else in the http stack) is configured. When the configured endpoint was changed from http to https, something on apache (or haproxy maybe) was left behind that is sending port 80 to port 443 and apache is saying (correctly) ""You're speaking plain HTTP to an SSL-enabled server port."""
1826382,2020-10-19 10:47:39 UTC,Work around in the charm committed here:
1826383,2019-04-25 10:45:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655666"
1826385,2019-04-25 14:07:25 UTC,"I was able to verify that deleting ftrace/test.d/kprobe/multiple_kprobes.tc allows the remaining ftrace selftests (from the cosmic kernel tree) to pass. That suggests that the ""Register/unregister many kprobe events"" (multiple_kprobes.tc) test is the test that puts the system into a bad state."
1826385,2019-04-26 08:41:57 UTC,"Checked again on the KVM that I used yesterday for this:
  1. ftrace test finished as expected with upstream tree https://pastebin.ubuntu.com/p/QmQfspFFR5/
  2. ubuntu-cosmic master branch with tip at 2e8c30c5 (Ubuntu-4.18.0-18.19) will hang https://pastebin.ubuntu.com/p/69gHfNpMRF/
  3. ubuntu-cosmic master branch with tip at fc64292e (Ubuntu-4.18.0-17.18) will pass https://pastebin.ubuntu.com/p/pgjNvCVK5F/"
1826385,2019-04-26 09:35:51 UTC,"I think this patch can get this issue fixed on Cosmic:
https://github.com/torvalds/linux/commit/43a1b0cb4cd6dbfd3cd9c10da663368394d299d8
(found in this thread https://lkml.org/lkml/2018/12/3/1219)"
1826385,2019-04-29 10:35:59 UTC,"More tests on a bare-metal and a KVM node with 4.18.0-18 / -17 / -16 / -11 shows that:
* This issue can be reproduced on these kernels
* Bare metal system tend to pass with the ftrace test on the first run, but it will hang with the second / third attempt if you run it again
* KVM nodes tend to fail on the first attempt (3 out of 4 kernels), and if it has passed, the second attempt will reproduce this as well."
1826385,2019-04-30 08:55:50 UTC,"Tried to reproduce this on Bionic with ubuntu-bionic source code and ubuntu-cosmic source code, but no luck."
1826385,2019-04-30 12:05:39 UTC,"This can be triggered on Cosmic with a OEM kernel built with gcc-8:
$ cat /proc/version
Linux version 4.15.0-1036-oem (root@rumford) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #41 SMP Tue Apr 30 10:57:32 UTC 2019"
1826385,2019-05-07 08:51:08 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-May/100573.html
1826385,2019-05-16 15:03:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1826385,2019-05-20 14:02:16 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1826385,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1826385,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1826385,2019-04-25 10:30:06 UTC,This change was made by a bot.
1826388,2019-05-16 19:56:42 UTC,"I hit this issue as well during my upgrade. Since I don't need any other architectures than x86, I edited /usr/lib/python3/dist-packages/maasserver/migrations/builtin/maasserver/0166_auto_select_s390x_extra_arches.py and basically stubbed out the add_s390x_to_pkg_repository_to_arches() function, ran apt-update -y again, and the upgrade finished up just fine."
1826388,2019-10-17 13:40:34 UTC,"i had a similar problem, when switching back from maas/next ppa to maas/stable"
1826389,2019-04-25 13:17:17 UTC,The converted unit doesn't belong to the original types any more. This is a limitation of how BuildLimit in the original game works.
1826390,2019-07-14 04:17:32 UTC,[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]
1826390,2019-05-14 10:33:30 UTC,did you add your user to vboxusers?
1826391,2020-09-30 13:49:35 UTC,"Thank you for your bug report, I'm not going to try to format my system partition but if there is no warning in the case one user try to do that it's an issue. Could ypu perhaps report it upstream as well on
https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues ?"
1826393,2019-04-29 15:47:33 UTC,"On Thu, Apr 25, 2019 at 11:37:02AM -0000, Waldemar Kozaczuk wrote:

> Public bug reported:
>
> Yesterday I have upgraded my laptop from Ubuntu 18.10 to 19.04 and that
> way got newer QEMU 3.1.0 along vs QEMU 2.12.0 before. I have noticed
> that everytime I start QEMU to run OSv, QEMU seems to hand noticably
> longer (~1 second) before showing SeaBIOS output. I have tried all kind
> of combinations to get rid of that pause and nothing helped.
>
> Here is my start command:
> time qemu-system-x86_64 -m 256M -smp 1 -nographic -nodefaults \
>  -device virtio-blk-pci,id=blk0,bootindex=0,drive=hd0,scsi=off \
>  -drive file=usr.img,if=none,id=hd0,cache=none,aio=thre\
>  -enable-kvm \
>  -cpu host,+x2apic -chardev stdio,mux=on,id=stdio,signal=off \
>  -mon chardev=stdio,mode=readline -device isa-serial,chardev=stdio
>
> It looks like qemu process starts, waits almost a second for something
> and then print SeaBIOS splashscreen and continues boot:
>
> --> waits here
> SeaBIOS (version 1.12.0-1)
> Booting from Hard Disk..OSv v0.53.0-6-gc8395118
> 	disk read (real mode): 27.25ms, (+27.25ms)
> 	uncompress lzloader.elf: 46.22ms, (+18.97ms)
> 	TLS initialization: 46.79ms, (+0.57ms)
> 	.init functions: 47.82ms, (+1.03ms)
> 	SMP launched: 48.08ms, (+0.26ms)
> 	VFS initialized: 49.25ms, (+1.17ms)
> 	Network initialized: 49.48ms, (+0.24ms)
> 	pvpanic done: 49.57ms, (+0.08ms)
> 	pci enumerated: 52.42ms, (+2.85ms)
> 	drivers probe: 52.42ms, (+0.00ms)
> 	drivers loaded: 55.33ms, (+2.90ms)
> 	ROFS mounted: 56.37ms, (+1.04ms)
> 	Total time: 56.37ms, (+0.00ms)
> Found optarg
> dev  etc  hello  libenviron.so	libvdso.so  proc  tmp  tools  usr
>
> real	0m0.935s
> user	0m0.426s
> sys	0m0.490s
>
> With version 2.12.0 I used to see real below 200ms. So it seems qemu
> slowed down 5 times.
>
> I ran strace -tt against it and I have noticed a pause here:
> ...
> 07:31:41.848579 futex(0x55c4a2fd34c0, FUTEX_WAKE_PRIVATE, 1) = 0
> 07:31:41.848604 futex(0x55c4a2ff6308, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
> 07:31:41.848649 ioctl(10, KVM_SET_PIT2, 0x7ffdd272d1f0) = 0
> 07:31:41.848674 ioctl(9, KVM_CHECK_EXTENSION, KVM_CAP_KVMCLOCK_CTRL) = 1
> 07:31:41.848699 ioctl(10, KVM_SET_CLOCK, 0x7ffdd272d230) = 0
> 07:31:41.848724 futex(0x55c4a49a9a9c, FUTEX_WAKE_PRIVATE, 2147483647) = 1
> 07:31:41.848747 getpid()                = 5162
> 07:31:41.848769 tgkill(5162, 5166, SIGUSR1) = 0
> 07:31:41.848791 futex(0x55c4a2fd34c0, FUTEX_WAKE_PRIVATE, 1) = 0
> 07:31:41.848814 futex(0x55c4a49a9a98, FUTEX_WAKE_PRIVATE, 2147483647) = 1
> 07:31:41.848837 getpid()                = 5162
> 07:31:41.848858 tgkill(5162, 5166, SIGUSR1) = 0
> 07:31:41.848889 write(8, ""\1\0\0\0\0\0\0\0"", 8) = 8
> 07:31:41.848919 futex(0x55c4a2fd34c0, FUTEX_WAKE_PRIVATE, 1) = 1
> 07:31:41.848943 ppoll([{fd=0, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN},
> {fd=8, events=POLLIN}], 5, {tv_sec=0, tv_nsec=0}, NULL, 8) = 1 ([{fd=8, revents=POLLIN}], left {tv_sec=0, tv_nsec=0
> })
> 07:31:41.849003 futex(0x55c4a2fd34c0, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
> 07:31:41.849031 read(8, ""\5\0\0\0\0\0\0\0"", 16) = 8
> 07:31:41.849064 futex(0x55c4a2fd34c0, FUTEX...
"
1826393,2019-04-29 16:25:19 UTC,"On Mon, Apr 29, 2019 at 11:47:33AM -0400, Stefan Hajnoczi wrote:

> On Thu, Apr 25, 2019 at 11:37:02AM -0000, Waldemar Kozaczuk wrote:
>
> Please try building QEMU 4.0.0 from source:
>
>   https://download.qemu.org/qemu-4.0.0.tar.xz
>
"
1826393,2019-05-01 04:13:58 UTC,"I tried with the bios  https://github.com/qemu/qemu/blob/v4.0.0/pc-bios/bios-256k.bin and it failed like so:
```
qemu: could not load PC BIOS 'bios-256k.bin'
qemu failed.
```"
1826393,2019-05-02 07:57:10 UTC,"Oh sorry, you're using the 'pc' machine, so please try this bios: https://github.com/qemu/qemu/blob/v4.0.0/pc-bios/bios.bin"
1826393,2019-05-06 17:40:05 UTC,The last bios indeed helped. It knows runs under 200ms.
1826393,2019-05-14 08:04:14 UTC,"On Mon, May 06, 2019 at 05:40:05PM -0000, Waldemar Kozaczuk wrote:

> The last bios indeed helped. It knows runs under 200ms.
>
> Do you anticipate doing minor release of 3.1.0 with updated bios to address
> this issue? Or users are expected to upgrade to QEMU 4.0.0?
"
1826393,2019-05-14 08:52:58 UTC,"On Tue, May 14, 2019 at 10:04:14AM +0200, Stefano Garzarella wrote:

> On Mon, May 06, 2019 at 05:40:05PM -0000, Waldemar Kozaczuk wrote:
> > The last bios indeed helped. It knows runs under 200ms.
> >
> > Do you anticipate doing minor release of 3.1.0 with updated bios to address
> > this issue? Or users are expected to upgrade to QEMU 4.0.0?
>
> CCing Gerd
>
> I'm not sure we will release SeaBIOS 1.12.1 with a minor release of QEMU
> 3.1.0, so upgrading to QEMU 4.0 should be the way to address this issue.
"
1826396,2019-04-25 12:36:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655680"
1826396,2019-05-23 19:57:08 UTC,"This RFE was approved in Denver. We are now in the specification phase: https://review.opendev.org/#/c/655680. As a consequence, marking this RFE as approved"
1826396,2019-06-25 23:41:07 UTC,"Reviewed:  https://review.opendev.org/655680
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=c1e12a0fd12ffd6b2934fdff5a0ee29de11a102d
Submitter: Zuul
Branch:    master"
1826396,2019-08-14 07:49:21 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/676365"
1826396,2019-08-14 18:30:12 UTC,"Reviewed:  https://review.opendev.org/676365
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=02b9204aa18b96d8c9c0c36dc9767c3d1d947fed
Submitter: Zuul
Branch:    master"
1826396,2019-09-19 10:11:44 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1826397,2019-04-25 13:03:00 UTC,Fix will be included in kubernetes-master charm revision 656.
1826397,2019-04-25 12:23:59 UTC,I'm just going to fix this.
1826397,2019-04-25 12:39:38 UTC,PR: https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/12
1826398,2019-10-04 12:19:37 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1826398,2019-12-04 04:17:28 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1826400,2019-05-03 16:32:33 UTC,"Thank you for your bug report, that's an issue in Disco indeed (doesn't happen in 18.04), I've reported it upstream
https://gitlab.gnome.org/GNOME/gnome-calendar/issues/384"
1826400,2019-05-10 16:04:12 UTC,Thanks for the report.
1826400,2019-05-13 07:17:36 UTC,This bug was fixed in the package gnome-calendar - 3.32.2-1
1826400,2019-05-13 13:06:55 UTC,"I agree that technically it is not needed to test if the original bug is fixed, but bonus points if someone does that anyway! Would be a nice double-check then."
1826400,2019-05-13 13:07:48 UTC,"Hello Potet, or anyone else affected,"
1826400,2019-05-30 14:38:19 UTC,"Using 3.32.2-1~ubuntu19.04.1 on disco, adding a day event work as expected, the event is on the correct date. Editing the event also keeps it on the same day. SRU is verified"
1826400,2019-05-30 17:40:58 UTC,"The verification of the Stable Release Update for gnome-calendar has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826400,2019-05-30 17:50:58 UTC,This bug was fixed in the package gnome-calendar - 3.32.2-1~ubuntu19.04.1
1826403,2020-10-02 10:08:58 UTC,Solved ! It was a cable problem ! change it and now everything works normal. I hope that would help.
1826403,2020-09-26 15:03:40 UTC,Ubuntu 20.04
1826403,2020-09-26 10:55:01 UTC,"Hello everyone
I don't know if this thread is still active but I'm facing the same problem with Ubuntu 20.04
I can provide all the necessary informations but I don't know what you will need.
Best regards"
1826403,2020-05-12 01:31:00 UTC,This is now resolved on my system. Thanks for following up.
1826403,2020-05-11 10:43:52 UTC,Upstream said it's more likely to be a kernel or driver issue. Do you still see the problem in newer Ubuntu versions?
1826403,2019-05-01 02:32:14 UTC,"Dear Sebastian,
Thanks for your response. I've raised the bug upstream here: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166"
1826403,2019-04-30 15:50:09 UTC,"Thank you for your bug report, could you report that upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ ?"
1826403,2019-04-27 01:03:32 UTC,"I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager still autoconnects just fine after boot. The configuration looks identical on both machines."
1826403,2019-04-27 01:01:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826403,2019-05-03 20:36:40 UTC,This could well be related to this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1793763
1826404,2019-04-25 15:29:25 UTC,Eoan does not yet exist in meta-release-development and ubuntu-release-upgrader has not been updated for eoan. One of these things is why the error message appears.
1826404,2019-04-25 15:37:09 UTC,"For clarity, my concern here is not that I can't upgrade to eoan, it's that I'm being given an invalid reason as to why I can't."
1826405,2019-08-15 21:55:23 UTC,"I was seeing the dreaded ""503 Inconsistent file state"" talking to the canonical (sorry) package repositories. As I said, there are no explicit upstream proxies, but who knows what the ISP is doing (this would be a big argument in favour of running apt-get over https to my mind..)"
1826405,2019-08-15 21:51:36 UTC,"Well, touch wood, something I've done has made things happier. I moved everything from the cache directory to a subfolder, made it inaccessible, removed apt lists from clients and ran apt-get update, then linked all the original cache files into _import and made acng reimport them."
1826405,2019-08-15 21:17:31 UTC,"Hi Steve,"
1826405,2019-12-06 15:01:06 UTC,VfileUseRangeOps: -1 fixed all my use cases.
1826405,2019-06-13 08:05:02 UTC,"Hoo my....
Our proxys are NOT fixed.
I go back to VfileUseRangeOps: 0.
I need to choose between a functional repository for daily updates or a functional repository for distribution release upgrade.
Will try if with VfileUseRangeOps: -1 I could get both."
1826405,2019-06-12 15:29:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826405,2019-05-16 14:27:19 UTC,"Further analysis shows that this problem is due to a fun interaction between lighttpd an ACNG. We use lighttpd to serve a local Debian/Ubuntu package repository. In about half the cases where we run 'apt update', it will fail with error 503 on the 'Release' file of such a repository."
1826405,2019-08-15 21:04:25 UTC,"acng seems totally broken in bionic. I'm not knowingly behind a proxy - can't completely rule out ISP doing something evil though. Anyone have any pointers on this? Very few google hits, nothing on bugs.debian.org that I can see, very little activity for acng on salsa.debian.org .."
1826405,2019-06-12 11:57:10 UTC,"Same bug different cause:
VfileUseRangeOps: 0
is no longer usable.
Ubuntu dis-upgrader-all tar.gz files (for do-release-upgrade) always trigger the same bug with the ""storage error [503 Inconsistent file state], last errno: File exists""."
1826406,2019-04-25 16:21:22 UTC,"The attachment ""unattended-upgrade-shutdown.patch"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1826406,2019-08-07 20:12:17 UTC,Fixed in 1.13. Thanks for the patch!
1826409,2019-04-25 16:21:42 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1826409,2019-04-26 14:47:34 UTC,IRC discussion on #UBUNTU-DEV today
1826409,2019-04-26 15:32:02 UTC,"Quick summary (from my POV, after discussing this with Marco in #ubuntu-bugs):"
1826409,2019-05-09 07:23:48 UTC,"I just installed Ubuntu 19.04 with UEFI boot, selecting Finnish as both the language and the keyboard layout. The layout happens to be correct for me after installation, ä and ö are working and only Finnish is listed in Input Methods / layouts."
1826409,2019-05-09 11:42:17 UTC,@Timo:
1826410,2019-07-16 08:21:53 UTC,"This is now a dup of its own clone per our IRC discussion:
[10:12] <apw> cpaelzer, it sometimes is just easier to make a new bug and dup the old against it :)
[10:18] <cpaelzer> to get rid of the stray tracking updates
[10:18] <cpaelzer> ok I can certainly do so if that helps"
1826410,2019-07-16 05:32:50 UTC,"Debian:
root@d10-sid:~# apt-cache show libbpf-dev libbpf4.19
Package: libbpf-dev
Source: linux
Version: 4.19.37-5
Installed-Size: 378
Maintainer: Debian Kernel Team <email address hidden>
Architecture: amd64
Depends: libbpf4.19 (= 4.19.37-5)
Description-en: eBPF helper library (development files)
 libbpf is a library for loading eBPF programs and reading and manipulating
 eBPF objects from user-space.
Description-md5: b8834dcec31d23cd9577fbae4ac6a867
Multi-Arch: same
Homepage: https://www.kernel.org/
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/l/linux/libbpf-dev_4.19.37-5_amd64.deb
Size: 289844
MD5sum: 52493b768caf815e814b60a4a4b9ee0e
SHA256: bcd283261336ae8ac5eefde91b4d43b8923c6eb48da9466b3485f95f86ca3506"
1826410,2019-07-15 22:40:05 UTC,This bug was fixed in the package linux - 5.2.0-8.9
1826410,2019-06-09 16:55:00 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1826410,2019-06-05 06:19:16 UTC,"Now that this is released, can we set it back to open again to reflect the real state in the archive?"
1826410,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1826410,2019-05-20 13:14:28 UTC,"It is, sorry about that. If we have no other need to re-spin we will have to hijack this bug report for verification and then reset things back after it claims to be released (the correct bug report would have been bug #1828234)."
1826410,2019-05-23 08:48:51 UTC,"I would change the verification status to done here (for now). The automatic processes will claim this bug fixed at some point and then we will have to roll back all states here. Again sorry, for the inconvenience caused."
1826410,2019-05-20 05:46:57 UTC,"Hmm,
no libbpf-dev package in any -proposed just yet.
Neither die I find it in a new queue?"
1826410,2019-05-20 05:32:32 UTC,"Sure you mean Disco and not Eoan?
... checking"
1826410,2019-05-17 09:31:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1826410,2019-05-03 10:08:38 UTC,From our IRC discussion who might work on it (as it is yet untriaged):
1826410,2019-05-03 07:54:33 UTC,"FYI here the package info from buster as of today
root@d10-buster:~# apt-cache show libbpf-dev libbpf4.19
Package: libbpf-dev
Source: linux
Version: 4.19.28-2
Installed-Size: 350
Maintainer: Debian Kernel Team <email address hidden>
Architecture: amd64
Depends: libbpf4.19 (= 4.19.28-2)
Description-en: eBPF helper library (development files)
 libbpf is a library for loading eBPF programs and reading and manipulating
 eBPF objects from user-space.
Description-md5: b8834dcec31d23cd9577fbae4ac6a867
Multi-Arch: same
Homepage: https://www.kernel.org/
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/l/linux/libbpf-dev_4.19.28-2_amd64.deb
Size: 262268
MD5sum: 2ab356bbbc421ac44f4106b6cf234f17
SHA256: f567734a69bc472f2f5a546ace4ad3abf42d69f09d2613bca52a411d78179718"
1826410,2019-04-25 14:20:17 UTC,"apport-collect makes no sense for this which is more a feature/packaging request, setting confirmed"
1826410,2019-04-25 14:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826410,2019-05-20 07:51:52 UTC,"After some discussion, probably just a bad bug ref in changelog?"
1826412,2019-04-25 18:08:59 UTC,This is fixed in my local tree.
1826414,2019-04-26 19:11:36 UTC,Marking release gating; as this is related to huge pages assigning to Austin to start.
1826414,2019-05-13 17:01:04 UTC,"Reviewed:  https://review.opendev.org/657733
Committed: https://git.openstack.org/cgit/starlingx/gui/commit/?id=9ae249e019ea1762365c7016eeb447f916be6665
Submitter: Zuul
Branch:    master"
1826414,2019-11-15 21:33:25 UTC,2019-11-11_20-00-00
1826414,2020-06-01 20:39:49 UTC,Restoring the release tag which was removed by mistake
1826414,2019-05-08 04:45:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657733"
1826415,2019-05-21 14:27:18 UTC,"Thank you for your bug report, could you add a file example to the bug?"
1826415,2019-05-21 14:55:47 UTC,"The issue seems to known upstream, https://gitlab.gnome.org/GNOME/evince/issues/869"
1826416,2019-06-18 19:16:54 UTC,"I can confirm the fix is included in the kernel ""4.4.0-152.179"": https://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/tree/include/linux/hyperv.h?h=Ubuntu-4.4.0-152.179"
1826416,2019-07-24 20:29:02 UTC,This bug was fixed in the package linux - 4.4.0-157.185
1826416,2019-05-23 20:14:01 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-May/100675.html
1826416,2019-05-07 19:26:10 UTC,"When the issue happens, there is no error message in dmesg or syslog, and it's just the host side NetVSP driver stops reading from the guest-to-host ring, and the guest network stops working. So we don't really have any logs to provide here."
1826416,2019-04-25 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826416,2019-06-18 16:04:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1826417,2019-05-09 13:22:57 UTC,"Let's not land anything until we have a plan written down on how this will work and be implemented. This isn't trivial, and if we do something naive, it may be very hard to make the MAAS fully confined in the end."
1826420,2019-09-02 04:17:24 UTC,[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]
1826420,2019-07-02 17:06:07 UTC,"Thank you for your bug report. What theme are you using? the folder icon seems different from the default Ubuntu one
Do you get the issue using the default ubuntu theme?"
1826420,2019-07-03 10:54:34 UTC,"Hi to all,"
1826422,2019-04-25 16:33:47 UTC,"Does adding ""kernel_irqchip=on"" to the comma separated list of options for -machine resolve it?"
1826422,2019-04-26 02:08:04 UTC,"This seems related to INTx (legacy) interrupt mode, which NVIDIA GeForce will use by default.  Using regedit in a Windows VM or adjusting nvidia.ko module parameters of a Linux VM can enable the driver to use MSI, which seems unaffected.  We also have the vfio-pci device option x-no-kvm-intx=on, which is probably a good compliment to configuring the driver to use MSI until we get this figured out, as the Windows driver likes to occasional switch MSI off, which would leave you in a bad state.  Routing INTx through QEMU would be a performance regression though, so while a workaround, having it routed through QEMU and not using MSI, is not a great combination."
1826422,2019-04-26 04:05:30 UTC,"Not just NVIDIA, forcing a NIC to use INTx also fails and it's apparent from the host that the device is stuck with DisINTx+.  Looks like the resampling mechanism that allows KVM to unmask the interrupt is broken with split irqchip."
1826422,2019-04-26 07:08:02 UTC,"ok, so, if I understand correctly, the workaround is:"
1826422,2019-04-26 13:11:49 UTC,"The change in QEMU 4.0 is only a change in defaults of the machine type, it can be entirely reverted in the VM config with kernel_irqchip=on or <ioapic driver='kvm'/> with libvirt.  Using a machine type prior to the q35 4.0 machine type would also avoid it.  There are no performance issues with these configurations that would favor using 3.1 over 4.0."
1826422,2019-04-29 15:59:17 UTC,"> The change in QEMU 4.0 is only a change in defaults of the machine type, it can be entirely reverted in the VM config with kernel_irqchip=on or <ioapic driver='kvm'/> with libvirt. Using a machine type prior to the q35 4.0 machine type would also avoid it. There are no performance issues with these configurations that would favor using 3.1 over 4.0.
"
1826422,2019-05-22 18:49:49 UTC,"Just to provide an update, patches are posted to revert this change in both the q35 4.1 machine type for the next release as well as introduce a q35 4.0.1 machine type making the same change for 4.0-stable.  References:"
1826422,2019-08-16 04:55:53 UTC,"Fix has been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=c87759ce876a7a0b17c2b"
1826422,2019-04-25 20:11:02 UTC,"> Does adding ""kernel_irqchip=on"" to the comma separated list of options for -machine resolve it?
"
1826426,2019-04-30 00:12:57 UTC,"This should be worked around by c054944
Please advise if you have problems after the next nightly build"
1826428,2019-04-25 15:55:11 UTC,"Also, this issue could be incorporated to lp:1160822 implementation."
1826432,2020-11-01 05:48:49 UTC,I'd suggest using magnum_config_overrides to cover missing options in the template rather then adding them (at least in this scenario)
1826432,2019-05-08 12:19:26 UTC,Gerrit change:
1826433,2019-04-26 11:59:50 UTC,I plan to work on the following topics:
1826433,2019-04-26 12:45:33 UTC,"So here are my main plans for build 21:
– Frisian scenarios 3 and 4, perhaps even 5 and 6 (4 is already complete, 3 good progress, 5 and 6 concretely planned)
– Graphics improvements (frisian worker icons, ferries)
– Extend lua support (I´m currently working on event listeners that will allow scripts to be notified of certain events instantly instead of using ""while not x do sleep end"" loops)
– Scenario-scripting support inside the editor
– And of course: Fixing bugs!"
1826433,2019-09-15 16:14:41 UTC,Migrated to https://github.com/widelands/widelands/issues/3415
1826433,2019-04-25 21:02:57 UTC,Best file new bugs whenever you find them.
1826435,2019-04-25 17:35:28 UTC,"More Images:
https://unsplash.com/photos/fWUOb2f0oug
https://handspinnen.beepworld.de/files/katzen_hunde_wolle/bilder/haspel.jpg
https://www.wollinchen.de/WebRoot/Store5/Shops/61105751/55AA/2265/A6A4/7B56/DFB4/C0A8/2BB9/9DD4/IMG_6222B_Web-1.jpg
http://www.nadelspiel.com/wp-content/uploads/2014/06/Wollhaspel-300x225.jpg"
1826435,2019-04-25 19:02:06 UTC,"+1 from me, but please don´t give me bugs related to atl/bar/emp 3D graphics. Their blender files use a different modelling technique, I already tried and failed to get familiar with it. We need a blender artist who can handle UV maps…"
1826435,2019-04-25 21:09:55 UTC,There is no obvious Blender file for the milking tongs - it might have been created as a PNG file as pixel art.
1826435,2019-09-16 13:54:31 UTC,Migrated to https://github.com/widelands/widelands/issues/2132
1826437,2019-07-25 13:59:35 UTC,"Adding the detection of floating wires - any place a green square is present - to the schematic would be highly helpful to me.  While not everyone seems to view the green square as an error, for those of us who implement a strict ""no-green-square"" policy in our schematics, it would be nice if we were alerted if a green square did happen to show up."
1826437,2019-05-02 14:17:52 UTC,"The way to upvote is to click ""this affects me"" in the upper left of the bug report.
Some kinds of this error can be detected, I'm planning to add it for 6.0"
1826437,2019-05-02 13:17:00 UTC,"I'd upvote this if there were a way to do so.  The problem is particularly frustrating when you have lots of passive component pins and have to use a smaller grid size.  (I have to use 25 mils.)   It's very tough to find ends of wires that are dangling 25 mils from a pin.  I just had to deal with 3 schematics, each having 3 such errors in them, but no problem detected by ERC.  Or at least, I _hope_ there were only 3 such errors each of those schematics!"
1826438,2019-04-25 18:07:31 UTC,"I've inferred that the reporting process itself possibly interferes with the misbehaviour. After submitting this report (before the terminal session was closed, however) (began through a terminal session and not the Alt-F2 launcher, using ubuntu-bug [PID of nautilus]) the reported behaviour is present again. The behaviour is identical to that recorded in the attached webm.
To confirm this interference I am beginning a second report, which won't be submitted. Using the Alt-F2 method to begin the reporting process doesn't interfere with the misbehaviour; beginning the process again through a terminal session did not reproduce the interference."
1826439,2019-04-26 13:10:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826439,2019-04-29 14:11:00 UTC,"Thank you for your bug report, it would be best reported upstream on https://gitlab.gnome.org/GNOME/tracker/issues/ if you can do that toob"
1826439,2019-05-02 08:27:41 UTC,"OK, filed upstream here: https://gitlab.gnome.org/GNOME/tracker/issues/95"
1826439,2019-05-02 16:37:52 UTC,Thanks!
1826440,2019-06-13 00:47:39 UTC,Fixed in daad58e51 for v6.  Backporting is unlikely here
1826440,2019-04-27 08:37:01 UTC,Make visible local ratsnests and them move all linked footprints through M button
1826440,2019-04-26 22:21:20 UTC,I can't recreate this. Can you provide a project that displays this problem?
1826441,2019-04-25 19:18:14 UTC,This would make the functionality similar to the highlight net tool.
1826441,2019-04-27 09:52:30 UTC,"Rather, everything here is more of a feature than an bug, nothing to fix. Only improve."
1826441,2019-04-27 09:48:44 UTC,"First Esc - disables tool, second Esc clears ratsnests"
1826441,2019-04-27 09:41:21 UTC," > Highlight net have two Esc presses: first press - tool is off, second press - highlight net is off.
Yes, agreed."
1826441,2019-04-27 09:01:06 UTC,"In fact, the Highlight Net and Display local ratsnests options both have two Esc presses: off tool, off highlight / ratsnests. Just discovered."
1826441,2019-04-27 09:47:22 UTC,"Yes, recreate this behaviour (two Esc presses) for display local ratsnest. It would be nice."
1826441,2019-04-26 09:40:32 UTC,Checkboxes in pcbnew settigs for both highlight net and display local ratsnest action on escape will good idea.
1826441,2019-04-26 09:36:55 UTC,"Saved a lot of time?
Why is this better? If you want, for example, some additional tool, cancel it and the ratsnest disappear, and if you want them to stay?"
1826441,2019-04-26 09:19:09 UTC,"I'd vote for making this configurable on an individual tool basis in settings, I personally prefer to have the net highlighting/ratsnest lines cleared on Escape."
1826441,2019-04-26 03:55:23 UTC,Yes!
1826441,2019-04-27 08:55:33 UTC,"Рighlight net have two Esc presses: first press - tool is off, second press - highlight net is off."
1826443,2019-08-20 01:01:12 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, and mentions a version of gimp not contained in the Ubuntu 18.04 repositories. Therefore, this bug is invalid."
1826446,2019-04-27 13:18:40 UTC,"@Michael,"
1826446,2019-04-27 14:37:27 UTC,"WRT to tabbed panels and so on, I did a little research, as far as I know:"
1826447,2019-08-19 16:13:40 UTC,This bug was fixed in the package linux-azure - 5.0.0-1016.17
1826447,2019-06-26 20:50:52 UTC,This bug was fixed in the package linux-azure - 4.18.0-1023.24~18.04.1
1826447,2019-08-01 14:44:49 UTC,Disco: https://lists.ubuntu.com/archives/kernel-team/2019-August/102726.html
1826447,2019-06-13 16:06:51 UTC,"Just confirming, I believe we need to include those patches to the 5.0 disco kernel as well, right?"
1826447,2019-05-30 20:48:03 UTC,Should we also include it to disco/linux-azure?
1826447,2019-06-26 20:49:11 UTC,This bug was fixed in the package linux-azure - 4.18.0-1023.24
1826447,2019-05-30 20:56:24 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-May/101013.html
1826448,2019-12-16 20:36:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826448,2019-12-16 20:42:46 UTC,"This impacts debmirror in Debian stretch & buster as well. IMO, this should be fixed by Canoncial in the ESM repositories vs. trying to update debmirror for this new naming convention they've introduced."
1826449,2019-04-29 20:26:55 UTC,"Thanks, agree that having a method of have more detailed config is something that we've wanted to do for a bit. Passwords, keys, etc are all solid use cases of not having them report to read-only users, in bundle exports, etc."
1826450,2019-07-20 06:12:03 UTC,"'Asia/Shangri-La' is not a valid IANA timezone name. At least I cannot find it here:
https://github.com/eggert/tz"
1826450,2019-07-20 19:20:23 UTC,"~xparks, you are correct. I'm glad this bug reporting system gets checked so often! I figured it out the next day, but apparently forgot I had reported it here. You can close this ticket."
1826451,2019-04-25 21:06:26 UTC,This is at least part of the problem.
1826453,2019-04-30 21:11:05 UTC,"Hi Brian, ""apt-get update; apt-get install grub2-common"" still reports ""grub2-common is already the newest version (2.02~beta2-36ubuntu3.21)"" to me, and the new version can not be found."
1826453,2019-05-06 08:49:50 UTC,This bug was fixed in the package grub2-signed - 1.66.22
1826453,2019-05-06 08:49:47 UTC,"The verification of the Stable Release Update for grub2 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826453,2019-05-06 08:49:39 UTC,This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.22
1826453,2019-05-02 14:29:50 UTC,Thanks! Marking verification-done-xenial since it's been confirmed to fix the issue.
1826453,2019-05-01 21:35:03 UTC,"Hi Mathieu,
Thanks for the hint! After I changed the Pin-Priority from 400 to 600 in the below file, I successfully installed the *3.22 version:"
1826453,2019-05-01 20:12:53 UTC,"Hi Dexuan,"
1826453,2019-04-30 17:24:32 UTC,"I added
deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main multiverse universe
into /etc/apt/sources.list and ran ""apt-get update"", and when I tried to upgrade to the .22 version, it can not be found:"
1826453,2019-04-30 02:41:19 UTC,It looks the .22 binary (2.02~beta2-36ubuntu3.22) for amd64 has not appeared in the -proposed repo yet.
1826453,2019-04-29 19:17:35 UTC,"Hi  Mathieu, thank you for the explanation and pushing the fix!"
1826453,2019-04-29 18:48:17 UTC,"Hello Dexuan, or anyone else affected,"
1826453,2019-04-29 18:14:56 UTC,"Dexuan,"
1826453,2019-04-26 20:23:39 UTC,I was not clear about the lifecycle of 16.04 and 14.04. :-)
1826453,2019-04-26 19:34:22 UTC,Marking Fix Released for other releases; the patch is already provided in Bionic and above.
1826453,2019-04-26 19:30:07 UTC,You're mentioning 14.04 here; elsewhere it's only question of 16.04. Is this patch really needed on 14.04 as well?
1826453,2019-04-30 17:50:49 UTC,"Hello Dexuan, or anyone else affected,"
1826454,2019-04-25 20:35:02 UTC,"Also the integer, float (0.5) and float (0,5) is not consistent?"
1826454,2019-04-25 20:35:46 UTC,Only integers seems respected. Floats are zeroed when adding new corners of the polygon.
1826454,2019-04-25 20:37:19 UTC,Also signed (negative) numbers does not seem respected.
1826454,2019-04-25 20:38:13 UTC,Please copy the full version information from About KiCad -> Copy Version Info.
1826454,2019-04-25 22:09:48 UTC,"Application: kicad
Version: (5.1.0-0), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.6.5 zlib/1.2.11 nghttp2/1.24.1
Platform: Mac OS X (Darwin 18.5.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.54.0
    Compiler: Clang 9.0.0 with C++ ABI 1002"
1826454,2019-05-30 17:27:36 UTC,Does this still occur with 5.1.2?
1826454,2019-07-30 04:17:28 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1826455,2020-01-15 10:32:48 UTC,I think this can be closed; bionic is at 11.0.5 as of 15/1/20.
1826455,2020-02-03 18:12:16 UTC,"Can be closed even more, now that it's 11.0.6"
1826455,2019-04-26 08:26:29 UTC,18.04 has all the security updates from 11.0.3.
1826455,2019-05-06 23:13:06 UTC,"What is the update policy for openjdk-lts in bionic?
Is it 11.0.2 + upstream security patches + debian/ubuntu patches or is it 11.0.$LATEST + debian/ubuntu patches?"
1826456,2020-03-07 13:55:13 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1826458,2020-08-06 23:19:08 UTC,"gadmin-samba has a reverse-dependency of gadmintools, which would need to be resolved first."
1826458,2020-10-06 04:17:23 UTC,[Expired for gadmin-samba (Ubuntu) because there has been no activity for 60 days.]
1826459,2019-04-25 21:04:14 UTC,heres also the netplan file for it:
1826459,2019-05-29 18:38:41 UTC,"enp0s31f6: Could not set route: Invalid argument
enp0s31f6: Routes set"
1826459,2019-05-29 18:48:23 UTC,"From what I can tell, the routing is exactly how it should be:"
1826459,2019-05-29 18:49:13 UTC,Closing as Invalid for netplan: the config generated is exactly as it should for the netplan YAML that was provided. This isn't a bug in netplan.
1826459,2019-06-12 09:52:47 UTC,"Hello,"
1826459,2019-06-17 12:56:58 UTC,heres btw the netplan config im using:
1826459,2019-12-13 16:42:00 UTC,">      addresses: [ 95.216.96.148/26 ]
>      gateway4: 95.216.96.129
"
1826459,2019-05-29 18:51:23 UTC,"The route looks invalid to me, please clarify...."
1826460,2019-08-02 10:54:03 UTC,"@aPlatypus I think your issue is different from this bug's: your home seems to be mounted in an unconventional location (/Mort/home/aplatypys ?), which snapd can't support."
1826460,2019-12-17 04:17:31 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1826460,2019-12-17 04:17:30 UTC,[Expired for snapd because there has been no activity for 60 days.]
1826460,2019-10-17 16:11:40 UTC,"I can no longer reproduce this issue, but I believe it likely was caused by using a mainline kernel as described in comment #3."
1826460,2019-09-25 12:41:35 UTC,"Dear reporter, please consider responding the question asked by John in comment number 7."
1826460,2019-07-31 16:46:58 UTC,Greetings ...
1826460,2019-04-26 07:09:51 UTC,"Also note, with that kernel, none of the AppArmor based sandboxing of snaps works anymore. All snaps are effectively running in devmode."
1826460,2019-04-26 07:03:33 UTC,"Can you provide the output of:
- mount |grep selinux
- dpkg -l |grep -e selinux -e policy -e linux-image"
1826460,2019-04-26 01:00:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826460,2019-05-21 17:29:44 UTC,"Apologies, Maciej for not getting you the Output you requested.  However, I think your suspicion is correct.  It was definitely 5.0.9 from the kernel ppa.  I recently built 5.1.3 and am not seeing the issue anymore."
1826460,2019-04-26 01:01:33 UTC,"I have the same issue since installing a fresh copy of Pop OS 19.04.  Can confirm it's every snap command I run.  VLC, LXD, etc."
1826461,2019-05-27 23:04:37 UTC,"Hi,
accidentally I might have discovered what was causing this problem. I was using Modem Manager Gui setup to auto-start after boot. Yesterday I have noticed that it's not working. I tried to start it manually but without success. It crashes immediately after start. But I have noticed one more thing – there is no problem with suspend anymore. It still needs testing but I think that it's safe to assume that Modem Manager Gui was causing my problems with suspend and mobile network connection."
1826461,2019-05-21 16:47:57 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.2-rc1 kernel [0]."
1826461,2019-05-23 00:04:05 UTC,"Hi Kai-Heng Feng, thanks for your time.
I would like to help but I have never installed mainline kernel before. Is it safe? Is it necessary since we know that this bug appeared after upgrade from Ubuntu 16.04 to 18.04 (so it didn't affect kernels before 4.15)? This is my only laptop and it is indispensable for me to work. Can I do it with ukuu or do I have to do it manually?"
1826461,2019-05-23 04:56:23 UTC,It should be safe.
1826461,2019-04-25 22:19:27 UTC,apport information
1826461,2019-06-01 09:00:07 UTC,This change was made by a bot.
1826461,2019-06-01 18:21:37 UTC,"Sure, but could you help me with that?
Do you still want me to check 5.2 kernel?
Can I install it with ukuu?
https://github.com/teejee2008/ukuu
I don't know how to test kernel parameter ""usbcore.quirks=1199:a001:m"".
Could you tell me how to do it?"
1826461,2019-06-02 15:17:28 UTC,https://wiki.ubuntu.com/Kernel/KernelBootParameters
1826461,2019-12-09 04:17:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1826461,2019-12-09 04:17:21 UTC,[Expired for modem-manager-gui (Ubuntu) because there has been no activity for 60 days.]
1826461,2019-06-01 08:33:54 UTC,I think it's a kernel bug.
1826461,2019-04-25 22:19:25 UTC,apport information
1826461,2019-04-25 22:19:11 UTC,apport information
1826461,2019-04-25 22:19:21 UTC,apport information
1826461,2019-04-25 22:19:19 UTC,apport information
1826461,2019-04-25 22:19:18 UTC,apport information
1826461,2019-04-25 22:19:16 UTC,apport information
1826461,2019-04-25 22:19:15 UTC,apport information
1826461,2019-04-25 22:19:10 UTC,apport information
1826461,2019-04-25 22:19:08 UTC,apport information
1826461,2019-04-25 22:19:07 UTC,apport information
1826461,2019-04-25 22:19:05 UTC,apport information
1826461,2019-04-25 22:19:03 UTC,apport information
1826461,2019-04-25 21:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826461,2019-04-25 22:19:23 UTC,apport information
1826463,2019-05-13 16:23:30 UTC,PR to stable branch: https://github.com/charmed-kubernetes/layer-docker/pull/1
1826463,2019-05-08 21:27:26 UTC,"> Is it possible to include it in the next stable hotfix release?
"
1826463,2019-05-03 15:17:05 UTC,Thanks for this fix! =)
1826463,2019-04-26 17:09:56 UTC,Thanks for the fix. It will be in kubernetes-worker revision 522+.
1826463,2019-05-06 17:59:59 UTC,Added a test to prevent regression:
1826463,2019-04-25 23:30:34 UTC,A simple patch that fix the regression
1826463,2019-04-25 22:45:29 UTC,Looks like we accidentally removed the code that handles docker-opts in this PR: https://github.com/juju-solutions/layer-docker/pull/135
1826463,2019-04-25 22:45:24 UTC,"Joseph Borg , your commit 0a6b0f97fa9446d0ae21dc872c2fe3d1a783fd29 generate a regression"
1826463,2019-04-26 16:04:51 UTC,i created a pull request  https://github.com/juju-solutions/layer-docker/pull/136
1826463,2019-04-25 22:40:19 UTC,"When you rollback this file
https://github.com/charmed-kubernetes/layer-docker/blob/master/reactive/docker.py
 to commit 907b7cbfe9ff50676d8143fec6c7434a6f749efb"
1826467,2019-04-26 07:24:44 UTC,Fix in-progress here:
1826467,2019-04-26 20:39:38 UTC,"After more debugging, I found more paths being blocked by apparmor:"
1826467,2019-05-16 11:14:41 UTC,"Reviewed:  https://review.opendev.org/655803
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=40914493c7be88a1c3cd80c937d65e044301c24b
Submitter: Zuul
Branch:    master"
1826467,2019-05-16 12:10:04 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/659543"
1826467,2019-05-29 07:41:58 UTC,"Reviewed:  https://review.opendev.org/659543
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=15f8a94e080ce4c708dfbfa7b602ebd165e44aa5
Submitter: Zuul
Branch:    stable/19.04"
1826468,2019-04-29 11:47:53 UTC,"Stephan Bergmann committed a patch related to this issue.
It has been pushed to ""master"":"
1826468,2019-04-29 14:19:06 UTC,The upstream bug has been marked duplicate of https://bugs.documentfoundation.org/show_bug.cgi?id=123472 which states that the issue is fixed in git and for 6.3.0
1826468,2019-04-29 16:44:42 UTC,"Stephan Bergmann committed a patch related to this issue.
It has been pushed to ""libreoffice-6-2"":"
1826468,2019-05-01 00:17:18 UTC,"I confirm it is fixed in
版本: 6.3.0.0.alpha0+
Build ID: 1ae5ca077119982ae83833871326c86d9930ae11
CPU 线程: 4; 操作系统: Linux 4.18; UI 渲染: 默认; VCL: gtk3;
区域语言: zh-CN (zh_CN.UTF-8); UI 语言: zh-CN
Calc: threaded"
1826468,2019-05-31 18:25:03 UTC,"After further testing, the bug persists."
1826468,2019-05-28 11:49:16 UTC,can confirm it's fixed in 6.2.4.2
1826468,2019-05-30 16:46:27 UTC,"Confirmed fixed, thank you."
1826468,2019-06-03 00:05:31 UTC,"Mike, please open a new bug report on that, and add the link to this one to the See Also field. Please also try to get a backtrace as described here:
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace"
1826468,2019-04-29 08:24:05 UTC,*** Bug 124985 has been marked as a duplicate of this bug. ***
1826468,2019-05-26 08:55:30 UTC,6.2.4 released to Eoan.
1826468,2019-04-27 11:00:53 UTC,Bibisected using the bibisect-linux-64-6.2 repo:
1826468,2019-03-21 15:14:11 UTC,Tried to save a file to the network share via gvfs/sftp with LO 6.2.2.1 today and got essentially the same result; the GUI errors were the same and the terminal was essentially the same:
1826468,2019-04-26 16:08:22 UTC,Thank you Jarosław.
1826468,2019-02-14 20:09:41 UTC,"Performed a clean install of opensuse tumbleweed to root while keeping an earlier ~. Under LO 6.1 I had no issues whatsoever creating files on a remote volume mounted using sftp via gvfs. In 6.2, attempting to create a new file (or rename a file via save as) results in two error messages:"
1826468,2019-04-27 00:39:35 UTC,"I have run into this same problem for my Linux clients. Windows client works fine. My server is Ubuntu 16.04 running samba and nothing has been changed on it. My client is Linux mint 19. After upgrading to Libreoffice 6.2.3 from 6.1, I can no longer create a new file, though an existing file can be updated."
1826468,2019-04-12 10:55:09 UTC,So it works in Libo 6.1 but not in Libo 6.2 ?
1826468,2019-04-12 19:04:11 UTC,"Created attachment 150719
Help/About Window"
1826468,2019-04-12 19:05:10 UTC,It worked in LO 6.1 and not LO 6.2. I did run a distro update on this openSuSE tumbleweed system and the LO upgrade was part of that update. Attached a png of help/about.
1826468,2019-03-21 14:22:01 UTC,"Hello,
LibreOffice 6.2.2.2 is going to be released today, could you please try again
with this version to see if the problem has been resolved meanwhile? Thanks in
advance"
1826468,2019-04-26 12:07:17 UTC,"I have the same version of LibreOffice installed. The problem is not only with exporting PDF to a network drive, but also with trying to ""Save As"" to the same drive. If I change the document and simply ""Save"" it, it works well."
1826468,2019-04-26 13:01:08 UTC,"You're right, this does seem to be the same upstream issue popping up again."
1826468,2019-04-26 15:52:34 UTC,"Description:
After upgrading from Ubuntu 18.10 to 19.04 Libreoffice lost its ability to write to network drives. In my case it's a DAVS system, which I connect to using Nautilus. I access the file on the drive with Nautilus, open a file by double-clicking it, it opes without problems, I can change it and save it, but I cannot export the document as PDF or ""Save As"" another document at the same location. I get one popup window saying: ""Error saving the document <document name>: Nonexistent file"" and after closing it another one opens with ""Error saving the document <document name>: General error. General input/output error""."
1826468,2019-04-26 15:54:09 UTC,"I have reported the bug there, here is the link:"
1826468,2019-04-26 10:10:55 UTC,"Hi Jarosław, please could you confirm which version of LibreOffice-Calc you’re using."
1826470,2019-09-25 12:44:29 UTC,I have attempted to reproduce this issue on Ubuntu 19.04 with snapd 2.42~pre2
1826470,2019-09-25 12:45:53 UTC,"For the record, the desktop file generated by snapd contains this line:"
1826472,2019-10-04 08:56:25 UTC,This issue was fixed in the openstack/nova 19.0.3 release.
1826472,2019-09-27 09:00:25 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1826472,2019-09-18 16:27:40 UTC,"Reviewed:  https://review.opendev.org/682183
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4adf563da0d7d8421df074b51773e3d7c65ae4a7
Submitter: Zuul
Branch:    stable/stein"
1826472,2019-09-18 16:27:30 UTC,"Reviewed:  https://review.opendev.org/682182
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=38fc7f6f1602640b8e8c7b9cfa3e48766a5c5b95
Submitter: Zuul
Branch:    stable/stein"
1826472,2019-09-13 22:25:13 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/682183"
1826472,2019-09-13 15:20:06 UTC,"Reviewed:  https://review.opendev.org/656594
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=481cb5ce04e220c26e5772f4253d63e212adca45
Submitter: Zuul
Branch:    master"
1826472,2019-09-05 21:08:43 UTC,"Reviewed:  https://review.opendev.org/678301
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9cbedea0bf5535fc45d78c80e6d7499512e4c5f5
Submitter: Zuul
Branch:    master"
1826472,2019-08-23 20:16:09 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/678301"
1826472,2019-04-30 21:49:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656594"
1826472,2019-04-25 22:15:40 UTC,I'm not really sure what we should do in this case. We could capture the InstanceNotFound here:
1826472,2019-09-13 22:24:58 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/682182"
1826473,2019-10-16 06:02:31 UTC,"The real issue is:
""""""
Configurando udev (229-4ubuntu21.21) ...
addgroup: El grupo `input' ya existe como grupo del sistema. Saliendo.
update-initramfs: deferring update (trigger activated)
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service smfpd if started
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depend..."
1826477,2019-04-26 00:08:34 UTC,"Someone on Reddit told that it should import from another project, so why not to improve the ""Import settings"" text to something like ""Import from another project""?"
1826477,2019-04-26 06:30:27 UTC,"Admittidely it's impossible to know that it requires an existing project (.pro) file unless you find out by accident. Usually in software there's symmetrical import/export inside one software suite. But rather than making the implementation more complicated by having new files, why not just make the button text clearer, as Leandro said. ""Import from project file""."
1826477,2019-04-26 09:08:56 UTC,"Marking as ""Medium"" only because this has come up several times.  Changing the button label is a good idea."
1826477,2019-04-26 09:10:16 UTC,"@Wayne, this might be nice to have in 5.1.2, but it's definitely a string change.  Let me know if you want it merged; otherwise I'll just leave it in 6.0."
1826477,2019-04-27 09:38:18 UTC,"Thanks Jeff. Just a small enhancement proposal - tooltip texts are good when there's any ambiguity. The button text is now ""Import Settings from Another Project..."" which still leaves room for question about exporting or about how the settings have been saved. Tooltip could tell that, e.g. ""Import board settings from a KiCad project file""."
1826477,2019-04-29 18:55:03 UTC,"@Jeff, go ahead and cherry pick this into the 5.1 branch.  Thanks!"
1826478,2019-04-29 20:45:25 UTC,We can definitely provide a better error message with the hint on how to possibly fix it. Thanks.
1826479,2019-04-28 00:26:31 UTC,"Sorry, is it possible to remove the comment #4? Sorry, it was for another bug. =/"
1826479,2019-04-28 00:23:42 UTC,"For some reason I could not record the screen yet.
But to reproduce:"
1826479,2019-08-14 14:19:42 UTC,"Since layer colours are user configurable, and the low bug heat, I'm closing as Won't Fix."
1826479,2019-04-26 22:49:33 UTC,Don't the lines end handles help make this less ambiguous?
1826479,2019-04-26 00:28:48 UTC,"OH, I see the issue better now. It looks that the hilighted line segment has the same gray as F.CtrdYard. Is it possible to improve this selected poligon/shape style? What if the selected layer is the same color it is, but with a blue-light or orange or (other selection color based on the user theme) on its border?"
1826479,2019-04-26 22:52:42 UTC,"There is a noticeable shade change (albeit minor, hence bugs low priority) when changing a selected graphic line from F.CrtYrd to F.Fab in the Footprint Editor using the default layer colours."
1826481,2019-09-13 07:55:03 UTC,"Can't snapcraft just look at environment variables ($http_proxy, $https_proxy) and pass them along in the container configuration?"
1826488,2019-10-09 20:37:39 UTC,"I suspect you've been able to resolve this, sorry we never got back to you about it.
I'm closing it as ""Won't fix"", because we didn't do anything about this, but if you're still stuck there's probably a cause for this that isn't necessarily snapd itself and we can probably figure it out.
Again, sorry."
1826493,2019-04-26 22:32:46 UTC,Do you have any Action plugins installed? See http://docs.kicad-pcb.org/5.1.2/en/pcbnew/pcbnew.html#action_menu
1826493,2019-04-28 00:38:45 UTC,"Hmm, it is possible. I will check this by Monday when I have that computer."
1826493,2019-05-07 13:35:48 UTC,@Michael
1826493,2019-05-07 14:04:04 UTC,"You should file the bug report for this at https://github.com/NilujePerchut/kicad_scripts.  This is not an official KiCad script.  If you are asking for a better Python action scripting error message, that is a different bug."
1826493,2019-05-08 21:49:32 UTC,"I did, reported there."
1826495,2019-06-12 14:43:55 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1826495,2019-04-26 03:33:47 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655826"
1826495,2019-05-28 07:51:42 UTC,"Reviewed:  https://review.opendev.org/655826
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=cca464fa95bca5164d3932182862c2ec569a37a7
Submitter: Zuul
Branch:    master"
1826501,2019-04-26 08:48:27 UTC,Looks to be a reasonable ask. An operator should be able to choose whether regular users can create ha routers.
1826501,2019-04-26 09:56:28 UTC,This is just one example out of many from my perspective. You would encounter the same with DVR routers and capabilities of other services besides Neutron.
1826504,2019-04-26 15:18:19 UTC,"I see a potential problem here: Since workareas can theoretically have any radius, we will need to iterate over all buildings of the player on the map to check for overlaps. That may be slow. Do we want to define a constant X so that a building with overlapping workarea will be ignored if it is further than X away from the new site?"
1826504,2019-04-27 10:39:36 UTC,"The tribes have the workarea information for each building. So, we could calculate a maximum workarea value when loading the tribes and use that as a radius for surrounding buildings."
1826504,2019-09-15 15:32:15 UTC,Migrated to https://github.com/widelands/widelands/issues/2133
1826509,2019-09-13 16:42:37 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.
1826509,2019-04-30 01:48:33 UTC,The reason seems to be because Horizon does the resize_confirm asynchronously hence not waiting for the finishing confirm operation.
1826509,2019-04-30 03:27:46 UTC,Now the problem here is that the button is disabled on submit however due to the functionality of auto-refresh the website no longer knows the previous action was submit and unblocks the button.
1826509,2019-07-08 10:32:21 UTC,"Reviewed:  https://review.opendev.org/660430
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d6c56c26b3b043a038b829a8afecdef7f2f18bb1
Submitter: Zuul
Branch:    master"
1826510,2019-04-26 06:50:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655834"
1826510,2019-05-29 12:18:39 UTC,"Reviewed:  https://review.opendev.org/655834
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=98c434c199f07831c84bc1cc04b5dfa74821329c
Submitter: Zuul
Branch:    master"
1826510,2019-06-12 14:43:50 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1826513,2019-05-31 00:14:25 UTC,"Reviewed:  https://review.opendev.org/653704
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=115826ff884d39092b39d22cfce88820e849b2c2
Submitter: Zuul
Branch:    master"
1826514,2019-04-26 07:38:45 UTC,"Unfortunately, Shutter development is dead, so it is highly unlikely that this will get fixed. Sorry for the bad news!"
1826514,2019-04-26 08:03:36 UTC,"Oh, ok, wasn't aware of that, however, thank you anyway."
1826516,2019-04-26 07:40:24 UTC,I'm not sure if bluez can do anything about this.
1826516,2019-04-26 07:46:52 UTC,"To increase the bandwidth available for Bluetooth, please also try to avoid using 2.4GHz wifi networks. And use 5GHz instead (or wired)."
1826516,2019-04-26 08:00:06 UTC,This change was made by a bot.
1826516,2019-07-22 03:47:11 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1826519,2019-06-17 15:52:26 UTC,"I don't think this is Nova's responsibility - as long as the new block device shows up with `lsblk`, it's up to the guest OS/tooling to mount it (or not). I've changed the component to cloud-init in case there's something actionable for them in this bug. Thanks!"
1826519,2019-06-17 16:48:03 UTC,"As far as I know, cloud-init does not rerun the module which was completed. So if there is nothing to re-launch the action(Nova maybe for this role), I think cloud-init could nothing to do."
1826519,2019-06-18 18:51:28 UTC,"Hi Yang,"
1826519,2019-08-18 04:17:31 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1826522,2019-09-25 12:47:52 UTC,I can confirm that brave does not exit after closing the last window. Having said that I would suspect it's a problem with the specific snap application rather than the snapd stack itself.
1826522,2019-09-25 12:48:33 UTC,"Having said that, force-closing brave and running it again did restore tabs for me. I was testing revision 59"
1826523,2019-06-03 19:57:27 UTC,I have verified the following versions:
1826523,2019-09-27 09:04:13 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1826523,2019-07-10 21:39:53 UTC,This issue was fixed in the openstack/nova 17.0.11 release.
1826523,2019-07-03 18:20:27 UTC,This bug was fixed in the package nova - 2:19.0.0-0ubuntu2.3
1826523,2019-07-01 13:41:08 UTC,"This bug was fixed in the package nova - 2:17.0.9-0ubuntu3~cloud0
---------------"
1826523,2019-07-01 13:41:07 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1826523,2019-07-01 13:37:02 UTC,"This bug was fixed in the package nova - 2:19.0.0-0ubuntu2.3~cloud0
---------------"
1826523,2019-07-01 13:37:01 UTC,The verification of the Stable Release Update for nova has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1826523,2019-06-18 03:41:02 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1826523,2019-06-14 22:47:09 UTC,"OK, verified S/Q/R"
1826523,2019-06-06 06:24:13 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1826523,2019-06-05 21:17:46 UTC,This bug was fixed in the package nova - 2:18.1.0-0ubuntu3
1826523,2019-06-05 21:17:01 UTC,This bug was fixed in the package nova - 2:17.0.9-0ubuntu3
1826523,2019-06-03 19:51:48 UTC,"I have verified that 2:19.0.0-0ubuntu2.3 fixes the issue on disco,
raising the following exception:"
1826523,2019-05-17 07:33:57 UTC,This bug was fixed in the package nova - 2:19.0.0-0ubuntu5
1826523,2019-05-20 15:05:16 UTC,"Hello Lee, or anyone else affected,"
1826523,2019-05-04 02:22:27 UTC,"Reviewed:  https://review.opendev.org/655712
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=091a910576d9b580678f1881fffa425ab4632f48
Submitter: Zuul
Branch:    master"
1826523,2019-05-04 12:23:39 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/657109"
1826523,2019-05-04 12:24:07 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/657110"
1826523,2019-05-04 12:24:43 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/657111"
1826523,2019-05-04 20:08:23 UTC,"Reviewed:  https://review.opendev.org/657109
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=048d5b790f3da2756a0a1bf2bc015812cb24d53a
Submitter: Zuul
Branch:    stable/stein"
1826523,2019-05-05 18:04:26 UTC,"Reviewed:  https://review.opendev.org/657110
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=786083c91fa69ba9ff90bafe80d3b83b9f9bbc69
Submitter: Zuul
Branch:    stable/rocky"
1826523,2019-05-20 19:04:44 UTC,"Hello Lee, or anyone else affected,"
1826523,2019-05-16 17:11:29 UTC,"Hello Lee, or anyone else affected,"
1826523,2019-05-16 17:18:02 UTC,"Hello Lee, or anyone else affected,"
1826523,2019-05-16 17:54:51 UTC,"Hello Lee, or anyone else affected,"
1826523,2019-04-26 12:34:49 UTC,https://review.opendev.org/#/c/655712/
1826523,2019-05-17 12:50:20 UTC,"Hello Lee, or anyone else affected,"
1826523,2019-05-06 15:32:50 UTC,"Reviewed:  https://review.opendev.org/657111
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=99a63a6633f623cc4e6c9b361965a9c0935113cf
Submitter: Zuul
Branch:    stable/queens"
1826527,2019-04-26 10:00:53 UTC,"$ lsmod
Module                  Size  Used by
btrfs                1126400  0
zstd_compress         163840  1 btrfs
xor                    24576  1 btrfs
raid6_pq              114688  1 btrfs
ufs                    73728  0
qnx4                   16384  0
hfsplus               106496  0
hfs                    57344  0
minix                  32768  0
ntfs                  102400  0
msdos                  20480  0
jfs                   188416  0
xfs                  1204224  0
ccm                    20480  6
nvram                  16384  0
msr                    16384  0
xt_CHECKSUM            16384  1
iptable_mangle         16384  1
ipt_MASQUERADE         16384  3
nf_nat_masquerade_ipv4    16384  1 ipt_MASQUERADE
iptable_nat            16384  1
nf_nat_ipv4            16384  1 iptable_nat
nf_nat                 32768  2 nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_conntrack_ipv4      16384  5
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
xt_conntrack           16384  1
nf_conntrack          131072  6 xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4,nf_nat,ipt_MASQUERADE,nf_nat_ipv4
libcrc32c              16384  3 nf_conntrack,nf_nat,xfs
ipt_REJECT             16384  2
nf_reject_ipv4         16384  1 ipt_REJECT
xt_tcpudp              16384  6
bridge                151552  0
stp                    16384  1 bridge
llc                    16384  2 bridge,stp
ebtable_filter         16384  0
ebtables               32768  1 ebtable_filter
ip6table_filter        16384  0
ip6_tables             28672  1 ip6table_filter
iptable_filter         16384  1
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               40960  11 ebtables,ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,ipt_MASQUERADE,xt_CHECKSUM,ip6_tables,ipt_REJECT,ip_tables,iptable_mangle
rfcomm                 77824  14
bnep                   20480  2
snd_hda_codec_hdmi     49152  1
snd_hda_codec_realtek   106496  1
snd_hda_codec_generic    73728  1 snd_hda_codec_realtek
rtsx_usb_ms            20480  0
memstick               16384  1 rtsx_usb_ms
btusb                  45056  0
btrtl                  16384  1 btusb
btbcm                  16384  1 btusb
btintel                16384  1 btusb
uvcvideo               86016  0
videobuf2_vmalloc      16384  1 uvcvideo
videobuf2_memops       16384  1 videobuf2_vmalloc
videobuf2_v4l2         24576  1 uvcvideo
videobuf2_core         40960  2 videobuf2_v4l2,uvcvideo
videodev              180224  3 videobuf2_core,videobuf2_v4l2,uvcvideo
bluetooth             557056  43 btrtl,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic           24576  1 bluetooth
media                  40960  2 videodev,uvcvideo
asus_nb_wmi            28672  0
asus_wmi               28672  1 asus_nb_wmi
sparse_keymap          16384  1 asus_wmi
intel_rapl             20480  0
snd_hda_intel          40960  5
snd_hda_codec         126976  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
x86_pkg_temp_thermal    16384  0
intel_powerclamp       16384  0
snd_hda_core           81920  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
coretemp               16384  0
snd_hwdep      ..."
1826527,2019-04-26 09:58:41 UTC,"$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=ab9c3c8a-b6dc-40f9-b9a7-eea4950cf89e ro verbose INIT_VERBOSE=y noplymouth"
1826527,2019-04-26 09:56:44 UTC,"Laptop uses only Intel graphics.
Laptop screen is 1366x768. Monitor is 1920x1200.
Moving mouse beyond 1366x768 results in 15 second lag."
1826529,2019-06-30 05:33:46 UTC,"Reviewed:  https://review.opendev.org/655062
Committed: https://git.openstack.org/cgit/openstack/os-testr/commit/?id=ad00e6d41b441e10f0b4ed81511e66660a9eeaa0
Submitter: Zuul
Branch:    master"
1826529,2019-07-10 21:35:03 UTC,This issue was fixed in the openstack/os-testr 1.1.0 release.
1826532,2019-04-29 07:28:40 UTC,"Hi Tim,"
1826532,2019-05-08 09:22:46 UTC,Let me add a little more info. The ultimate aim is to indeed to anonymise the deployment configuration of offered/consumed units. We've made some strides in that direction in terms of what's visible to the offering model - the offering side sees only anonymised consuming application names.
1826532,2019-05-10 08:15:19 UTC,"Hi Ian,"
1826532,2019-06-13 11:36:56 UTC,"Hi Ian,"
1826532,2019-06-17 23:25:04 UTC,"Sorry, I have not had a chance to look deeper into this particular deployment yet. We have re-evaluated other cross model deployment scenarios and there's no issue that we're aware of with the mechanics of how things hang together. Where there have been issues in the past it's either been the charms themselves and their use of deprecated hook tools to fetch address information, connectivity issues between the controllers/models, or connectivity issues between the workloads."
1826532,2019-12-13 04:17:22 UTC,[Expired for juju because there has been no activity for 60 days.]
1826532,2019-04-28 21:29:54 UTC,"Yes, this is by design. As a cross-model relation there is only a relation to a single ""entity"". The scale of the other side is not exposed over the relation on purpose."
1826534,2019-04-26 15:12:01 UTC,"Hi again,"
1826534,2019-04-26 17:55:42 UTC,"This is something that you should address with upstream (postfix-users mailing
list is the best venue)."
1826534,2019-04-29 09:31:45 UTC,"Hi Scott,"
1826534,2019-05-01 20:41:11 UTC,"Thanks for doing this, Lars."
1826537,2019-04-29 01:00:24 UTC,"This is the same bug as https://bugs.launchpad.net/subiquity/+bug/1821966, it's fixed in disco and will be fixed in 18.04.3. In the meantime, if you can switch to tty2 and run ""snap refresh subiquity"" you'll get a version with the bug fix fixed. (Or just leave search domain empty for now and fix it post-install)"
1826537,2019-04-26 12:34:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1826538,2019-08-20 01:01:38 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, and mentions a version of gimp not contained in the Ubuntu 18.04 repositories. Therefore, this bug is invalid."
1826540,2019-04-26 13:36:26 UTC,"No need to clean up the branches – when we move to GitHub, developers will take their active branches with them, the rest can moulder on lp ;)"
1826540,2019-04-28 07:57:04 UTC,We should definitely do a cleanup when we move. I'd rather do this once I have figured out how the move will be done though.
1826540,2019-04-28 08:17:19 UTC,BTW most of the branches are mine and waiting for a code review slot ;)
1826540,2019-04-28 13:44:09 UTC,"I did not mean branches with open reviews. I f you go down the list only a bit you will find lots of them with failed merge reviews (e.g. supeseded, dissaproved, and so on). Although they seem to be never merged they are still active as the branch state is not dependent on the merge state in this case so we could set a lot of them to abandoned. This might make it easier to see which are really still of interest."
1826540,2019-09-17 07:31:12 UTC,Migrated to https://github.com/widelands/widelands/issues/3416
1826542,2019-04-30 14:04:29 UTC,This was fixed in zaza
1826543,2019-04-29 11:16:40 UTC,"Likely an upstream issue, should be reported to https://github.com/micheleg/dash-to-dock/issues"
1826543,2020-04-20 08:43:43 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1826543,2020-06-20 04:17:23 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1826544,2019-04-30 16:16:20 UTC,https://gitlab.gnome.org/GNOME/gnome-shell/issues/1235
1826544,2019-04-30 16:07:41 UTC,"Help me with the history, though... I started on this machine with 15.10, then 16.04, and now 18.04.  Wasn't 16.04 _not_ Gnome but Unity instead?  This seems to be an issue with some left-over setting from 16.04 that's messing up 18.04.  (unless it's something left over from 15.10)"
1826544,2019-04-30 15:37:14 UTC,"Yes, that's what I was asking, weird bug... it might be worth reporting upstream on https://gitlab.gnome.org/GNOME/gnome-shell/issues"
1826544,2019-04-29 14:20:18 UTC,Thank you for your bug report. Does it work if you connect with another user? Could you also add your journalctl log to the bug after getting the issue
1826544,2019-04-26 16:37:43 UTC,I really have no idea what package to file this against because I don't know where the disconnect lies nor how to determine that.  Please let me know what additional information is needed.
1826544,2019-04-26 16:23:12 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1826544,2019-04-29 14:47:08 UTC,I'm not sure I understand your questions...
1826545,2019-05-28 17:17:37 UTC,"Reviewed:  https://review.opendev.org/657188
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=83234c0c47b5aa6678fd4cb175b4e24e1e158cd6
Submitter: Zuul
Branch:    master"
1826545,2019-09-27 17:04:11 UTC,This issue was fixed in the openstack/senlin 8.0.0.0rc1 release candidate.
1826547,2019-04-29 07:16:55 UTC,"Thank you for your bug report, it's likely an upstream issue, could you report it to them on https://gitlab.gnome.org/GNOME/gnome-control-center/issues ?"
1826548,2019-04-26 13:43:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/655902"
1826548,2019-05-14 10:10:49 UTC,"Reviewed:  https://review.opendev.org/655902
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=59e761afbf838d10484baeb0564db9ae4d5867b1
Submitter: Zuul
Branch:    master"
1826548,2019-05-27 09:07:01 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661570"
1826548,2019-05-31 18:21:34 UTC,"Reviewed:  https://review.opendev.org/661570
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=53ffeb980ce2a8958151070b8b2866e15f983846
Submitter: Zuul
Branch:    stable/stein"
1826548,2019-09-15 19:06:46 UTC,This issue was fixed in the openstack/kuryr-kubernetes 1.1.0 release.
1826549,2019-12-31 01:38:51 UTC,Comment #7 sounds like a potentially different bug. And comment #6 from last May sounds like this bug might be fixed already?...
1826549,2020-01-06 01:28:39 UTC,Thanks. If a fix exists in any release then we mark the bug as Fix Released.
1826549,2020-01-03 22:51:33 UTC,The problem still existed in December 2019 (Ubuntu 19.04). But I can confirm that Ubuntu 19.10 fixes this issue. Most probably fix will never be ported to Ubuntu 19.04 kernel.
1826549,2019-12-30 19:41:36 UTC,Please advise on the status of this bug. I'm using a Microsoft Arc and suffer from this issue where the scroll wheel stops working after some period of computer idle. A restart of the bluetooth service fixes it until the next time.
1826549,2019-04-29 14:36:05 UTC,Same issue here. MS wireless mouse via receiver plugged into USB. Worked fined before upgrade. Thanks
1826549,2019-05-05 14:59:25 UTC,I've found that Archlinux users also suffer from this problem. And they found a solution  https://bbs.archlinux.org/viewtopic.php?id=245501
1826549,2019-04-26 19:54:10 UTC,Have the same issue with a Microsoft Corp. Wireless Optical Mouse 3.0
1826549,2019-04-26 19:54:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826549,2019-05-06 06:42:28 UTC,It's in mainline and stable so it'll be in Ubuntu's 5.0 kernel soon.
1826550,2019-04-29 07:17:34 UTC,"Thank you for your bug report, it's likely an upstream issue, could you report it to them on https://gitlab.gnome.org/GNOME/gnome-control-center/issues ?"
1826550,2019-06-25 12:27:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826550,2019-06-25 12:39:16 UTC,Possibly related to https://gitlab.gnome.org/GNOME/gnome-control-center/issues/17
1826550,2020-04-29 02:00:20 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1826550,2020-06-28 04:17:36 UTC,[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]
1826551,2020-03-24 09:51:03 UTC,Is this a plymouth bug? More details?
1826552,2019-06-30 20:02:13 UTC,"Reviewed:  https://review.opendev.org/665652
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=04a0fc47b0a66adcaba34df0c50ccc956cd95922
Submitter: Zuul
Branch:    master"
1826552,2019-06-17 12:14:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/665652"
1826552,2019-07-12 11:03:22 UTC,"Reviewed:  https://review.opendev.org/656265
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=dfc0e8bfe2707b5654f84a45de4ad7fb7075ddc6
Submitter: Zuul
Branch:    master"
1826552,2019-04-29 12:23:38 UTC,"Tytus, there is a field which is indicating who is working on an issue ""Assigned to"". That one is used to avoid any waste of time by having several people working on it."
1826552,2019-04-29 10:10:35 UTC,There is already another PR in place:
1826552,2019-04-29 09:19:23 UTC,"A PR has been proposed in charm-helpers, let see how it goes:"
1826552,2019-04-29 12:49:06 UTC,"Sahid,"
1826555,2019-04-26 18:54:55 UTC,"Marking as release gating since it is expected that the glance commands should work.
Next step is to examine the logs for the timestamp given to determine if the glance pods/service is running at that time or some issue has occurred resulting in glance not running at that time."
1826555,2019-05-09 07:57:34 UTC,"@peng peng
From the log you provided, it shows the pod glance-api started at about 2019-04-26 10:03:57, but the test(glance image-list) you run is at 2019-04-26 09:10:11. So it seems glance is not ready at the time issue the test command."
1826555,2019-05-27 01:23:20 UTC,We are not able to reproduced this issue in recent loads.
1826559,2019-05-03 20:18:15 UTC,"I'm setting this as a feature request, that said I also wanted to clarify something."
1826559,2020-07-07 22:12:01 UTC,"From support case 00288146. Our support engineer suggested this as a solution to our use case. For clarity, let me be more specific about our needs."
1826559,2019-04-26 14:58:07 UTC,"Hi Jason,"
1826559,2019-04-26 15:31:20 UTC,"Andres, I've added some additional detail."
1826560,2019-05-09 11:52:08 UTC,"Hello Marcus, or anyone else affected,"
1826560,2019-05-09 11:53:47 UTC,"Hello Marcus, or anyone else affected,"
1826560,2019-05-10 09:24:18 UTC,"Upgraded libreoffice to 1:6.2.3-0ubuntu0.19.04.1 from disco-proposed in a clean and up-to-date disco amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice."
1826560,2019-05-16 08:19:12 UTC,This bug was fixed in the package libreoffice - 1:6.2.3-0ubuntu0.19.04.1
1826560,2019-05-16 08:19:32 UTC,"The verification of the Stable Release Update for libreoffice has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826560,2019-05-16 08:19:35 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.2.3-0ubuntu0.19.04.1
1826562,2019-06-05 18:18:58 UTC,verified the new list is as follows in cli and horizon
1826562,2019-05-09 05:08:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657917"
1826562,2019-05-13 16:52:03 UTC,"Reviewed:  https://review.opendev.org/657917
Committed: https://git.openstack.org/cgit/starlingx/gui/commit/?id=4f16cfc2acc90a59f4a0795514d4b0077e634ee2
Submitter: Zuul
Branch:    master"
1826562,2019-04-26 18:43:17 UTC,"Work items required for this LP:
1) Remove options to edit Gnocchi storage and img-conversion
2) Add options for Docker, etcd and docker-distribution"
1826562,2019-04-26 18:44:23 UTC,Marking as release gating since the new filesystems for containers need to be resizable from Horizon.
1826562,2019-04-26 18:47:55 UTC,Assigning to Bruce to identify a prime to implement this change in stx-gui.
1826566,2019-04-26 15:27:28 UTC,"Hi Jason,"
1826566,2019-04-26 15:45:50 UTC,"Hi Andres, I've added some more detail. Let me know if you have additional questions."
1826566,2019-04-29 14:04:43 UTC,This should really just be an IPMI setting in the power configuration on the node.
1826566,2019-04-29 17:09:59 UTC,"Maybe, but the fact that it's not the default setting and that boot devices
are available to select makes it very confusing, and end users end up
getting into bios mode when they didn't intend to. I want a system-wide ""no
bios"" setting."
1826566,2019-04-29 19:00:53 UTC,"You system-wide BIOS setting is not required. IPMI can be instructed to always boot the machine in EFI mode, a power setting is all that is needed."
1826566,2019-09-20 11:46:23 UTC,"Thanks for your feature request, please could you start a thread over on our Discourse (https://discourse.maas.io) to discuss the feature?"
1826567,2020-06-26 09:31:23 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826567,2019-04-26 16:53:22 UTC,"Workaround:
Before starting the installation (or after cancelling it during the first steps), click on ""Activities"" (top left corner of the screen), then type ""settings"" and press enter to bring up the ""Settings"" application. There, click on ""Region & Language"" on the left column menu, then, under ""Input sources"" click the ""+"" icon and select the preferred keyboard layout. Then click the trash icon next to the ""English"" 'input source' to delete this keyboard layout and make the preferred one default. Starting the installer now will make it use the desired keyboard layout both during the installation and on the installed system."
1826568,2019-05-06 15:50:46 UTC,"Hi Axel,"
1826568,2019-05-06 18:25:04 UTC,"Sorry, I don't have the test code, since this was created by a memory corruption. However, the way I understand the message is, that there is some internal disagreement how to decode the op-code ""051300009517e2bf"" - which mige be an invalid opcode anyway. So a simple test application would just consist of this opcode."
1826568,2019-05-07 09:30:13 UTC,"I've encountered this message before for invalid instructions, and it often doesn't really mean there was an error. In particular for variable instruction length ISAs you'll see the error if the translator reads part of the insn and determines that it's invalid without needing to read the rest of it -- https://lists.gnu.org/archive/html/qemu-devel/2017-06/msg06845.html talks about a case of that for x86."
1826568,2020-11-25 16:09:21 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1826579,2019-07-10 21:53:46 UTC,Still Not Reproduced; closing
1826579,2019-07-03 17:58:52 UTC,"Hi Ghada, per your comment above, shall we go ahead & close this?"
1826579,2019-06-04 15:04:39 UTC,"We are not able to reproduce this issue. Peng, please reproduce and contact Steve to investigate.
If the issue is not reproducible in the next two weeks, we'll close it."
1826579,2019-05-27 17:54:46 UTC,"Based on discussion with Steve, he didn't notice this issue when using the same lab for some developer testing. Need to monitor for a re-occurrence."
1826579,2019-05-13 18:14:51 UTC,Lowering the priority to medium as this appears specific to the mellanox NICs
1826579,2019-04-26 19:33:49 UTC,Marking release gating as it seems to take 40 minutes for inventory to add the interface.
1826579,2019-04-27 20:13:50 UTC,Another system (dell-r720-3-7) with 1 Niantic sriov interface on compute host does not have the unlock issue with same load.
1826579,2019-04-27 20:09:06 UTC,This issue is likely to be Mellanox specific and may only happen with non-default MTU.
1826579,2019-04-26 19:29:35 UTC,"1. On this system there are 3 computes, compute-0 does not have sriov interface, while compute-1 and compute-2 both have sriov interfaces using CX-4 nic."
1826579,2019-04-26 19:15:58 UTC,"2019-04-26 14:24:51 [admin@admin]> RUNNING: system host-label-assign compute-2 sriov=enabled
+-------------+--------------------------------------+

| Property    | Value                                |


+-------------+--------------------------------------+

| uuid        | f8af6b2f-d86a-4055-be7e-cd3dd56e63ac |
| host_uuid   | 62c1ddd9-126a-40df-a9b4-d2be3d037469 |
| label_key   | sriov                                |
| label_value | enabled                              |


+-------------+--------------------------------------+"
1826579,2019-04-30 13:41:51 UTC,"Based on Yang's analysis, assigning to a networking prime to investigate why it takes 40 minutes for a Mellanox port to go enabled.  Once Allain completes his analysis we can decide who would be best to prime a solution for this issue."
1826579,2019-04-26 18:40:02 UTC,"Please include the following:
1) The steps that were done to provision the interface for this compute
2) Status of the interface at the time of the unlock, ie: iplink output - need to determine if the link is up or if there is a hardware type issue with the interface."
1826581,2019-04-29 07:32:47 UTC,apport information
1826581,2019-04-29 07:32:45 UTC,apport information
1826581,2019-04-29 07:32:46 UTC,apport information
1826581,2019-04-29 07:32:44 UTC,apport information
1826581,2019-05-05 17:00:47 UTC,"i dunno but i can reach ~400Mbps with Manjaro
[jeanmarc@astrolabe ~]$ sudo lshw -class network
[sudo] Mot de passe de jeanmarc :
  *-network
       description: Ethernet interface
       produit: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       fabriquant: Realtek Semiconductor Co., Ltd.
       identifiant matériel: 0
       information bus: pci@0000:03:00.0
       nom logique: enp3s0
       version: 16
       numéro de série: e0:d5:5e:a7:59:ec
       taille: 1Gbit/s
       capacité: 1Gbit/s
       bits: 64 bits
       horloge: 33MHz
       fonctionnalités: pm msi pciexpress msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.045.08-NAPI duplex=full ip=192.168.0.26 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       ressources: irq:133 portE/S:3000(taille=256) mémoire:a3104000-a3104fff mémoire:a3100000-a3103fff
[jeanmarc@astrolabe ~]$ uname -a
Linux astrolabe 5.0.9-2-MANJARO #1 SMP PREEMPT Sun Apr 21 07:11:08 UTC 2019 x86_64 GNU/Linux"
1826581,2019-05-06 06:17:54 UTC,What's the network speed if r8169 is used instead of r8168 under Manjaro?
1826581,2019-05-02 05:16:02 UTC,Similar to https://www.spinics.net/lists/netdev/msg560600.html?
1826581,2019-04-29 07:32:43 UTC,apport information
1826581,2019-04-29 07:32:37 UTC,apport information
1826581,2019-04-29 07:32:41 UTC,apport information
1826581,2019-04-28 15:55:58 UTC,"Hmm it's look like i use r8169 in 19.04 (kernel 4.18). I can get ~400Mbps there.
Sadly r8169 dosen't seem available with kernel 5."
1826581,2019-04-29 07:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826581,2019-04-29 07:32:36 UTC,apport information
1826581,2019-04-29 07:32:42 UTC,apport information
1826581,2019-04-29 07:32:39 UTC,apport information
1826581,2019-04-29 07:32:40 UTC,apport information
1826581,2019-04-29 07:32:38 UTC,apport information
1826582,2019-05-20 17:42:52 UTC,This was also observed in the web staff client for Evergreen 3.1.6 today.
1826583,2019-07-12 18:23:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670614"
1826583,2019-07-17 20:24:38 UTC,"Reviewed:  https://review.opendev.org/671036
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=fbee52d52f49287b15da0e69aff4a3a8a049bf0b
Submitter: Zuul
Branch:    master"
1826583,2019-07-17 19:54:10 UTC,"Reviewed:  https://review.opendev.org/671034
Committed: https://git.openstack.org/cgit/starlingx/upstream/commit/?id=01ecb9c0a6a5c75bc3da68ce5218232a0323f12f
Submitter: Zuul
Branch:    master"
1826583,2019-07-16 13:31:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671036"
1826583,2019-07-16 13:28:16 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671034"
1826583,2019-07-15 15:43:03 UTC,"Reviewed:  https://review.opendev.org/670614
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=e02502733e769ecb67d885dce38fb39b17dfd8ea
Submitter: Zuul
Branch:    master"
1826583,2019-07-15 15:15:43 UTC,"Reviewed:  https://review.opendev.org/670613
Committed: https://git.openstack.org/cgit/starlingx/upstream/commit/?id=fc60572e87240a361af3746691978cf8d4b42368
Submitter: Zuul
Branch:    master"
1826583,2019-07-12 18:20:53 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670613"
1826583,2019-07-11 16:28:59 UTC,"Reviewed:  https://review.opendev.org/670188
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=7dc0b2d9fa09593d1321a1d03eed1c223e35afe4
Submitter: Zuul
Branch:    master"
1826583,2019-07-11 16:29:07 UTC,"Reviewed:  https://review.opendev.org/670124
Committed: https://git.openstack.org/cgit/starlingx/upstream/commit/?id=04dc50050acb213feb013ee33ee4c81fda6c2c78
Submitter: Zuul
Branch:    master"
1826583,2019-07-10 22:04:16 UTC,This isn't a networking issue. It's an issue related to https/security configuration. Updating the labels.
1826583,2019-07-10 21:02:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670190"
1826583,2019-07-10 20:41:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/670188"
1826583,2019-05-08 08:50:31 UTC,"According to Huifeng's analysis, this issue should be fixed by each component's helm plugin owner, including barbian, cloudformation, cinder, panko, placement, aodh, cinderv3, cinderv2, gnocchi, heat."
1826583,2019-05-08 08:26:48 UTC,"By looking into the code, the missing updated FQDN issue for some component's public API are caused by missing the endpoints overrides for 'host_fqdn_override'/'port'/'scheme' in its helm plugins:
e.g. the neutron API which is successfully updated with the new FQDN by below codes:
def _get_endpoints_overrides(self):
    overrides = {
           ...
           'network': {
                'host_fqdn_override':
                    self._get_endpoints_host_fqdn_overrides(
                        self.SERVICE_NAME),
                'port': self._get_endpoints_port_api_public_overrides(),
                'scheme': self._get_endpoints_scheme_public_overrides(),
            }
            ...
but for components such as: barbian, cloudformation, cinder, panko, placement, aodh, cinderv3, cinderv2, gnocchi, heat, such configuration is not overrides by the new FQDN configuration.
Each component's helm plugin owner may need to check what configuration are required to be overrided to solve this issue."
1826583,2019-04-26 18:37:09 UTC,"Marking as release gating as public endpoints will need the FQDN.
Assigning to Forrest (one of the networking team project leads) to determine who can work on this issue."
1826583,2019-07-11 16:36:05 UTC,"Reviewed:  https://review.opendev.org/670190
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=f6c89d3eb5849da59f03dd0f53083d4a3a16258b
Submitter: Zuul
Branch:    master"
1826584,2019-09-04 14:13:20 UTC,Non-Codabar barcodes can have spaces in them.  This will be fun!
1826584,2020-08-05 21:52:25 UTC,Removing pullrequest and adding needsdiscussion as per comments #8 and 9.
1826584,2019-09-16 15:39:17 UTC,I wonder how common it is for item barcodes that get checked out across the desk to legitimately have spaces in them.
1826584,2019-05-23 16:56:32 UTC,Branch w/ 2 commits as promised:
1826584,2019-04-26 18:09:29 UTC,I agree with Michele.
1826584,2019-04-30 17:29:37 UTC,"This patch arose from a discussion in the Circulation Interest Group at this year's conference. I asked if anyone knew what keystroke would work on dismissing such messages because we had not found one and were having to mouse it. No one else at the discussion knew of one, perhaps not enough people there had transitioned on to webby to encounter it."
1826584,2019-04-26 21:57:22 UTC,"thank you for the feedback, i hadn't considered that."
1826584,2019-04-26 17:49:04 UTC,"I haven't tested this, but I'm not in favor of the 'enter' key having the ability to dismiss dialogs."
1826584,2019-04-26 16:07:35 UTC,"here's a simple patch just adds the ""autofocus"" attribute the dialogs' primary button."
1826584,2019-05-23 16:32:39 UTC,+1 to allowing space bar to close dialogs in addition to Esc key.
1826586,2019-04-27 13:24:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826586,2019-04-29 07:34:06 UTC,"Thank you for your bug report, there is a similar upstream report on https://gitlab.gnome.org/GNOME/nautilus/issues/944"
1826586,2019-05-20 08:10:04 UTC,Upstream marked it as duplicate of https://gitlab.gnome.org/GNOME/nautilus/issues/615
1826588,2019-04-26 17:08:53 UTC,"This project demonstrates the issue. If one of the nets on the LIVE port is highlighted, the other one is also highlighted. The same merging happens on the PCB.."
1826588,2019-05-05 16:48:45 UTC,"This should have been fixed by recent commits, please re-open if you can reproduce after commit 6d918ea"
1826589,2019-04-26 17:43:31 UTC,It's possible this is already supported via site config. Will confirm on Monday.
1826589,2019-04-30 07:57:52 UTC,This is supported currently but needs testing.
1826589,2019-05-16 14:44:27 UTC,"This is obsolete, as we don't want to cache the 401s."
1826596,2019-05-13 18:32:27 UTC,"Now works, new memory module installed, could be related, could be new version fix."
1826596,2019-04-26 18:53:37 UTC,"Rest of the system:
https://termbin.com/45kl"
1826596,2019-04-26 19:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826596,2019-04-26 19:13:46 UTC,"'apport-collect' not included in Linuxmint, cannot boot into kernel affected anyway."
1826597,2021-02-23 12:22:15 UTC,"Just upgraded to 20.10, same story. Works in discreet graphics mode but is having hiccups - sometimes touchpad is not recognized, e.g. sometimes on non-clean reboot, sometimes when reboot with external monitor attached. Intermittent, clean reboot without attached peripherals seems to always help."
1826597,2021-02-22 03:56:50 UTC,This issue became apparent after installing Ubuntu 20.04.2 LTS. Switched BIOS to discrete mode and touchpad works.
1826597,2020-10-06 18:00:29 UTC,"Is there any news about it? Ubuntu 20.04.1, kernel 5.4.0-48, Nvidia CUDA driver 455.23.05, ThinkPad P50, latest BIOS/firmware 1.62, with VGA configured in discrete mode, integrated touchpad do not work."
1826597,2020-04-28 17:41:17 UTC,"I confirm what zob wrote. I switched from Discrete to Hybrid mode in BIOS and now touchpad work fine. I use Nvidia proprietary driver from ubuntu standard repository (440.64), my only problem is screen tearing (PRIME profile set to performance mode). I don't know if the drivers from PPA repository fix touchpad and tearing problem. I read that Nvidia 440.66.11 Linux driver fixes annoying bugs With PRIME Sync: https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-440.66.11-Linux.
Previously I used the card in discrete mode with Fedora 31 and the proprietary Nvidia drivers 440.82 from RPM Fusion repository without any problems for touchpad or for tearing."
1826597,2020-04-28 17:09:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826597,2020-04-23 20:37:29 UTC,Thanks Nikolay. I'm not sure that what you link to is related. That sounds much worse. My PC wasn't bricked. I just couldn't use the touchpad if I also chose to install the Nvidia driver.
1826597,2020-04-18 02:39:42 UTC,"There was a strong recommendation not to change ""Hybrid"" to ""Discrete"" mode in BIOS - not sure if it is still a problem, just beware: https://www.reddit.com/r/thinkpad/comments/a2g0k4/warning_do_not_change_from_hybrid_graphics_to/"
1826597,2020-04-12 15:39:44 UTC,"Ok. So I finally found a viable workaround (or fix). In BIOS the GPU must be set to ""Hybrid Graphics"" NOT ""Discrete""."
1826597,2020-04-12 11:10:05 UTC,"Yes. This is still an issue on the P50, same machine as above.
Now on kernel: 5.4.0-21-generic
xserver-xorg-input-libinput v. 0.29.0-1"
1826597,2020-04-12 14:49:54 UTC,"I though I might experiment a little. I installed xubuntu-desktop with the lightdm display manager. Didn't work either. Then I installed kubuntu-desktop with sddm display manger and the suddenly my touchpad started working.
I then did a dpkg-reconfigure gdm3, rebooted and logged back into the ""standard"" gnome session. And now my touchpad is working with the Nvidia drivers installed and working. I have no clue why but, to resume, there are 2 workarounds:
1: use nouveau drivers instead of nvidia
2: install kubuntu-desktop (and log into ubuntu-desktop or whatever floats your boat)."
1826597,2019-04-26 18:56:40 UTC,Btw adding synaptic_intertouch=0 to the parameters at boot doesn't change anything.
1826597,2019-04-26 19:22:57 UTC,"Oh, and forgot to mention that an external optical usb mouse works just fine."
1826597,2019-04-27 19:50:11 UTC,I just tested against the mainline kernel: 5.1.0-050100rc6-generic #201904211830 SMP Sun Apr 21 18:33:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
1826597,2020-04-12 15:24:36 UTC,"Ahh. Actually xinput now (with kubuntu-desktop installed) now has registered my touchpad as a standard mouse it seems (I don't have multitouch functionality, so no two-finger scrolling, etc)."
1826597,2020-03-07 04:17:19 UTC,"Have the same problems on p50 after installing NVIDIA-Linux-x86_64-440.64.
Linux <skipped> 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux"
1826597,2020-03-28 19:25:17 UTC,This also happens in 20.04.
1826597,2020-04-12 11:33:25 UTC,"I just tested installing the Nvidia binaries directly from the web-site. That did not fix the issue with the non-functional touchpad either.
That was the driver version 440.82"
1826597,2019-09-24 10:55:39 UTC,"A very similar thing just happened to me, with the 435 drivers via ppa. Reverting to 430 solved it. Ubuntu 19.04, P50. USB mouse works."
1826598,2019-05-14 11:45:46 UTC,ok
1826598,2019-05-14 09:08:05 UTC,"If there was news you would get an email notification or it would show on the webpage...
As said I'm not going to personnally look at it and it there is no active git/gnutls dedicated maintainer around and that bug only has one report so is not a high priority ticket so I wouldn't could on it"
1826598,2019-05-14 08:25:49 UTC,Any news?
1826598,2019-05-09 11:42:12 UTC,How can I proceed to help Ubuntu investigation?
1826598,2019-05-07 22:17:59 UTC,if you prefer I can let you access the VM via ssh.
1826598,2019-05-07 11:20:42 UTC,I've opened a question on kubuntu forum.
1826598,2019-05-07 22:16:25 UTC,"I've installed an ubuntu 19.04 from DVD just downloaded from ubuntu site,
and it doesn't work!!!
I can send you the qcow2 file of the virtual machine. Always the same
error. So it's not a kubuntu error."
1826598,2019-05-06 19:23:23 UTC,Any news? Do you need the image I've installed?
1826598,2019-05-01 08:33:35 UTC,"I've installed a new VM with kubuntu 19.04 without any customization and
the error is always the same.
If it can help, I upload you the VM somewhere: the bz2 file is 2.1GB"
1826598,2019-04-30 20:00:54 UTC,I'll try to install a new kubuntu 19.04 from scratch and let you know.
1826598,2019-04-30 15:35:40 UTC,"weird, it works here, probably something that has to do with your setup that gnutls doesn't handle"
1826598,2019-04-29 14:19:51 UTC,"The curl command works fine.
But git clone doesn't work. I had to recompile git source package with
OpenSSL instead of using GNUTLS library"
1826598,2019-04-29 14:07:40 UTC,"Thank you for your bug report. It works here on a disco system, do you still get the issue?
Does 'curl -L https://github.com/creationix/nvm.git -o download' work wirhout error?"
1826598,2019-05-07 09:43:30 UTC,"No news no, I was mostly triaging that issue but I'm not working on gnutls nor git. It works here on a standard Ubuntu installation, so either it's something specific to your internet/configuration or it's a kubuntu problem for some reason"
1826601,2019-04-29 22:12:37 UTC,"Andres, could you expand on this a bit please, as the header appears to be present on master."
1826601,2019-04-30 13:16:50 UTC,I have also confirmed that the header is present.
1826601,2019-06-30 04:17:34 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1826604,2019-07-20 23:37:31 UTC,"On my systems, this bug also affected saving files from firefox, regardless of the destination!
This is not about the time for downloading, I'm talking about ~1 kB files."
1826604,2019-05-15 08:54:04 UTC,"Thanks gonsolo, that workaround worked for me (with a restart)"
1826604,2019-08-26 06:29:14 UTC,I removed desktop icons. Clean a nice desktop and no more 5 seconds save on every file.
1826604,2019-05-03 10:53:31 UTC,Thanks
1826604,2019-05-03 09:57:45 UTC,Done.
1826604,2019-04-30 15:52:09 UTC,"Thank you for your bug report, could you report the issue upstream on https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues?"
1826604,2019-05-04 09:28:52 UTC,"This hits me twofold:
1. Quitting vim in a terminal takes more than one second which is very annoying.
2. I don't want desktop icons."
1826605,2019-04-26 23:37:27 UTC,This happens with non HA controllers too.
1826605,2019-08-28 21:25:14 UTC,We've updated the destroy logic in 2.6 and with the additional --force for issues not forseen I wanted to reset the status here to incomplete and see if folks hit it with a more modern example to see if the work in 2.6 has not helped this situation.
1826605,2019-10-28 04:17:25 UTC,[Expired for juju because there has been no activity for 60 days.]
1826606,2019-04-29 03:13:58 UTC,Please:
1826606,2019-06-28 04:17:23 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1826607,2019-04-26 22:43:57 UTC,"The error is telling you exactly what not to do, which isn't strictly speaking just a CLOS-related issue: don't make a macroexpand hook that invokes the macroexpand hook."
1826607,2019-04-26 23:28:22 UTC,I suspect I'll apply this diff after freeze. It makes the test case work.
1826607,2019-04-27 02:01:11 UTC,"What led to this was trying to use a generic function in the macroexpand hook.  That seems a perfectly reasonable thing to want to do -- but the CLOS implementation compiles the effective method function on demand, and it happens to do that using the user defined macroexpand hook.  Boom."
1826607,2019-04-29 13:18:55 UTC,"To make my previous note clear:  I am not interested in mutation testing the innards of the functions generated by the CLOS implementation, so your solution of rebinding *macroexpand-hook* to #'funcall would be just fine.   You will have to be careful that there isn't user code being compiled along with that (the forms in eql specializers, the bodies of methods) because compiling that could visibly depend on the user's *macroexpand-hook*."
1826608,2020-11-24 17:58:45 UTC,"This bug is believed to be fixed in cloud-init in version 20.4. If this is still a problem for you, please make a comment and set the state back to New"
1826611,2019-05-07 22:23:29 UTC,It appears this output can be avoided by also extracting the core18 snap (using unsquashfs and extracting to /snap/core18/current).
1826612,2019-08-20 13:04:49 UTC,"This looks fixed
http://zuul.openstack.org/builds?job_name=puppet-openstack-unit-5.5-centos-7"
1826612,2019-04-26 22:32:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656034"
1826612,2019-04-26 22:37:30 UTC,"Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.opendev.org/656034
Reason: https://review.opendev.org/#/c/635149/"
1826617,2019-04-27 03:28:42 UTC,Try to do it with:
1826617,2020-05-24 10:39:15 UTC,"sudo dpkg --force-overwrite -i libxxxx.deb
it‘s useful to me ,
and I wrote a blog to explain the details,
you can vist https://blog.csdn.net/qinglingLS/article/details/106315288"
1826618,2019-04-27 15:12:54 UTC,"I have never used automatic updates. As the only reference, I used https://help.ubuntu.com/lts/serverguide/automatic-updates.html to setup automatic updates on a test Ubuntu 18.04 server VM. I also added mail abilities to it and tested that it worked, using my main server as a destination for emails. Early this morning, it worked fine, doing automatic updates and e-mailing me that it did so.
It took about 11 minutes and many (~~60) packages were updated (since I purposely did not update the server when I started it)."
1826618,2019-04-29 16:48:20 UTC,"Thanks Doug for your feedback.
I'm also followed same automatic-updates document and updated config settings. Even though received notifications from Instance about package updates. Looks like facing some issue on Auto patch config here. So need assistance on this issue.
Let me know, what info are you looking here.
Advance thanking you"
1826618,2019-04-30 04:39:40 UTC,"As attachments, post your /etc/apt/apt.conf.d/50unattended-upgrades and /etc/apt/apt.conf.d/20auto-upgrades files. Also post any other changes you made."
1826618,2019-06-30 04:17:18 UTC,[Expired for Ubuntu Server Guide because there has been no activity for 60 days.]
1826620,2019-04-27 15:18:59 UTC,"Hi Andrew, can you please raise the issue on our support forum:
https://forum.peppermintos.com
where we'll try to get to the bottom of the issue."
1826620,2019-04-27 15:22:20 UTC,"Great, I see you've already posted to the forum."
1826625,2019-05-03 19:20:44 UTC,PR from cory_fu: https://github.com/juju-solutions/interface-tls-certificates/pull/17
1826625,2019-05-05 02:09:20 UTC,Fixes available in kubernetes-master revision 665 and greater and kubernetes-worker revision 526 and greater.
1826625,2019-05-03 20:18:12 UTC,More from cory_fu: https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/9 and https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/18
1826625,2019-05-03 19:18:25 UTC,"We don't see this in typical deployments because the kubernetes-master:loadbalancer interface only has a single unit related to it. Andrey's bundle has 4 units attached to it: 3 units of kubeapi-load-balancer, 1 unit of keepalived."
1826625,2019-05-13 16:34:57 UTC,"PRs to stable branches:
https://github.com/charmed-kubernetes/interface-public-address/pull/1
https://github.com/charmed-kubernetes/interface-tls-certificates/pull/1
https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/15
https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/23"
1826625,2019-04-29 21:04:08 UTC,I would also note that on a newly deployed cluster on AWS I am not seeing this thrashing of the cert. More information for reproduction would be very useful here so we can help.
1826625,2019-05-03 19:05:57 UTC,"Per IRC, it appears that on every hook, kubernetes-master is slightly changing the SANs on its certificate request."
1826625,2019-04-27 13:35:26 UTC,From the bug template:
1826625,2019-05-03 20:15:12 UTC,https://github.com/juju-solutions/interface-public-address/pull/5
1826625,2019-04-29 17:38:46 UTC,"Andrey,"
1826625,2019-04-28 04:54:16 UTC,"Tim,
Can you please elaborate on this script a little bit?
I ran it and it got stuck on the step ""juju debug-log --replay"" - it seems this option let the command run until it is interrupted, but if I do so - remaining commands from the script don't run obviously..."
1826626,2019-04-27 06:00:04 UTC,This change was made by a bot.
1826626,2019-04-30 00:29:10 UTC,This bug is a duplicate of LP 1825420.  I was going to mark it so but Launchpad warns this bug has duplicates itself so I am going to leave it as is.  Work is ongoing on LP 1825420
1826628,2020-02-23 16:03:22 UTC,"This looks to be long fixed, actually."
1826629,2019-05-30 08:12:06 UTC,This bug was fixed in the package deepin-qt5dxcb-plugin - 1.1.22-1ubuntu1.1
1826629,2019-05-28 07:00:04 UTC,"Thanks, marked as verified based on the last two comments."
1826629,2019-05-28 06:47:28 UTC,It seems to be fixed
1826629,2019-05-30 08:12:13 UTC,"The verification of the Stable Release Update for deepin-qt5dxcb-plugin has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826629,2019-05-21 19:18:45 UTC,"Hello Mikhail, or anyone else affected,"
1826629,2019-05-19 15:43:51 UTC,This bug was fixed in the package deepin-qt5dxcb-plugin - 1.1.24-1ubuntu2
1826629,2019-05-19 13:32:21 UTC,"I've built a fix in https://launchpad.net/~mikhailnov/+archive/ubuntu/deepin-screenshot , it seems that just rebuilding deepin-qt5dxcb-plugin will fix this issue."
1826629,2019-05-19 13:09:48 UTC,deepin-qt5dxcb-plugin is missing build dependency from libxcb-xinput-dev
1826629,2019-05-28 05:05:53 UTC,"Yes, this new proposed package successfully fixed the issue, at least for me, on deepin-music"
1826634,2019-04-27 08:59:58 UTC,This is already in Eoan: https://launchpad.net/ubuntu/+source/imagination/3.4-1
1826634,2020-01-01 20:45:05 UTC,"Adolfo, yes, but we're speaking about Bionic 18.04 ... !"
1826636,2019-04-29 03:17:40 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1826636,2019-06-28 04:17:24 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1826637,2019-06-26 19:09:38 UTC,This got implemented as part of the Immediate Actions work.
1826637,2019-04-27 12:59:36 UTC,This is much related to https://bugs.launchpad.net/kicad/+bug/1676814 (Persistent ruler instances)
1826637,2019-04-27 13:40:41 UTC,"The report is very similar to #1676814, but my implementation is much simpler, the behavior is similar to the behavior of other tools (Highlight Net and, possibly in the future, Display local ratsnest), in my opinion much more convenient. You can also make it so that several rullers are drawn in one cycle of using a measuring tool. Now only one ruler is drawn, the next mouse click draws a new ruler, the previous one disappears."
1826639,2020-07-02 09:07:57 UTC,"The verification of the Stable Release Update for wpa has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826639,2020-07-02 09:07:49 UTC,This bug was fixed in the package wpa - 2:2.9-1ubuntu4.1
1826639,2020-06-22 15:02:17 UTC,Working for me too. Many thanks.
1826639,2020-06-17 13:19:03 UTC,I installed this package:
1826639,2020-05-29 00:07:21 UTC,This bug was fixed in the package wpa - 2:2.9-1ubuntu7
1826639,2020-06-22 14:04:48 UTC,Thanks for testing!
1826639,2020-06-16 18:45:16 UTC,"Hello Laurent, or anyone else affected,"
1826639,2020-04-23 11:54:50 UTC,"NetworkManager[681]: <warn>  [1587639528.0703] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkM>
NetworkManager[681]: <warn>  [1587639528.0703] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/Netw>"
1826639,2020-04-12 16:23:54 UTC,Sorry for bad handling. #4 is attachment belonging to #5
1826639,2020-04-12 16:19:29 UTC,Suggested workaround:
1826639,2020-04-03 06:48:28 UTC,"Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
Kernel Version: 5.4.0-21-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.4 GiB of RAM"
1826639,2019-06-05 09:56:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826639,2020-05-20 10:29:50 UTC,It has been fixed in Debian in https://salsa.debian.org/debian/wpa/-/commit/00ec8743
1826640,2019-04-27 14:13:48 UTC,In top of the three typical stuff mentioned in the log you can also check that both the production alone and decay alone are not zero this will check if you do not have a zero coupling.
1826644,2019-05-15 09:52:59 UTC,"Hi,"
1826644,2019-05-05 11:11:52 UTC,"Hi Slawek,"
1826644,2019-05-05 11:06:53 UTC,lets take a failed router
1826644,2019-04-28 10:50:53 UTC,"Thx for checking that.
So if 2 routers in same tenant have got different vr_id configured than it's definitely not the same bug as something what https://review.openstack.org/651495 is trying to fix."
1826644,2019-04-28 03:36:26 UTC,"And also, can You check if it happens also with patch https://review.openstack.org/651495 ?"
1826644,2019-04-28 08:15:22 UTC,"Hi Slawek,"
1826644,2019-04-28 03:35:28 UTC,"Hi,"
1826644,2019-04-28 03:02:54 UTC,"Hi Dilip,
Could you please following this guide to add some information about your test/environment/version?
https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#bug-report-template"
1826644,2019-04-28 09:40:58 UTC,"Hi Slawek,"
1826645,2019-05-28 07:30:19 UTC,"Hi,"
1826645,2019-04-27 15:11:19 UTC,"Hi,"
1826645,2019-04-27 12:26:28 UTC,"Hi,"
1826645,2019-04-27 12:59:27 UTC,additional information:
1826645,2019-04-27 12:54:12 UTC,"For repairing it is neccessary to compile kernel. I'm sending solution for other and if is it possible, please add it in ubuntu kernel."
1826645,2019-04-27 14:10:34 UTC,"@Petr,"
1826646,2019-04-27 13:06:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656056"
1826646,2019-12-18 14:56:50 UTC,"Change abandoned by Stephen Finucane (<email address hidden>) on branch: master
Review: https://review.opendev.org/656056
Reason: -W for quite some time. I'm going to abandon to keep our review queue sane"
1826648,2019-04-27 14:08:23 UTC,Here is the core dump with backtrace:
1826648,2019-04-29 13:51:14 UTC,"Can you please attach your /etc/cups/cupsd.conf, /etc/cups/cups-files.conf, and /etc/cups/printers.conf files."
1826648,2019-06-29 04:17:27 UTC,[Expired for cups (Ubuntu) because there has been no activity for 60 days.]
1826648,2020-01-06 10:54:32 UTC,"I have the same problems as described in this bug. Every time I print something cupsd crashes with core dump and cups-browsed also crashes. My printer is a Samsung CLX 6260 Series. I can successfully print one job, then get the crash, then have to wait some minutes before the services are up again, and so on."
1826648,2020-01-10 23:22:02 UTC,"August Rydberg (august-rydberg), if you are using Focal, the cups-browsed crash is possibly caused by bug 1857815. Please follow the instructions I have given there for a debug log of cups-browsed, but please post your answer there, not in this bug report."
1826649,2019-09-11 14:52:14 UTC,"@Adam, I'll leave it open until the symlink-busting strategy is implemented.  If it resolves the issues at hand, I will close this report at that time."
1826649,2019-09-11 14:34:34 UTC,"It certainly shouldn't be worked on, but if the symlink-busting strategy
doesn't work for some reason, I'd like to reopen it.  (I don't know
Launchpad very well, if closing lets us do that, then yesss!)"
1826649,2019-09-11 13:39:05 UTC,"@Adam, does this mean that this bug report can be closed?"
1826649,2019-09-10 21:32:56 UTC,"Ha! That's awesome.  I'm going to migrate to that over the next few weeks, then."
1826649,2019-09-10 19:52:43 UTC,"The problem with signing is that each .app gets signed, and they
clobber each others signatures--so while every file inside the bundle
is signed, they're not all signed for the same .app.  (While things
can have multiple signatures, that's for things like signing a dmg and
the included apps, rather than the same file that is symlinked into
multiple .apps.)  When you verify the signatures, it says there is a
signing mismatch--but there is no problem adding signatures.  There
isn't really a log beyond ""app signature mismatch"".  If you delete the
subapps, and just sign/verify kicad.app, it verifies fine.  (The
problem with CMake is that it assumes that every file inside a bundle
belongs to that bundle, so when it processes each subapplication, it
messes with the rpaths so I have to add them back manually.)"
1826649,2019-09-10 18:21:48 UTC,"What needs to be done to make this happen?  I'm assuming at a minimum the gerber viewer, worksheet editor, calculator, and bitmap converter applications would have to be retooled to be child windows of KiCad instead of running in separate processes.  To be honest, I'm not sure how this would fly.  I know there are quite a few users who prefer to run Eeschema and Pcbnew as stand alone apps so I wouldn't see why this would be any different on macos.  I'm not opposed to doing this but we should you the Kiway interface so we can keep them as separate apps on other platforms."
1826649,2019-09-10 21:04:04 UTC,"Disk space is cheap.  Besides, duplicating all the apps only increases our footprint by 6%."
1826649,2019-09-10 18:34:39 UTC,Can we add a copy of the notarization log file that is generated?  This may provide more hints on the problem/how to resolve it.
1826653,2019-04-29 12:28:04 UTC,For branches this is useful because of the variety of possible URL formats and abbreviations; for snaps the URL in question is the URL of the repository that the snap builds from rather than the URL of the snap itself.
1826653,2019-06-29 04:17:24 UTC,[Expired for Launchpad itself because there has been no activity for 60 days.]
1826655,2019-09-15 15:31:31 UTC,Migrated to https://github.com/widelands/widelands/issues/2134
1826656,2019-04-27 17:39:42 UTC,UbiquitySyslog.txt reports (timestamps/hostname removed):
1826657,2019-05-16 12:56:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826657,2019-11-22 18:31:33 UTC,"Did you have the Wikipedia dictionary enabled? The English Wikipedia dictionary is enabled by default. And are you living in China? I assume it as your account name is Chinese characters. If both are true, please give a try to disabling the Wikipedia dictionary."
1826658,2020-02-13 07:49:25 UTC,Any updates on this matter?
1826658,2020-02-15 20:15:11 UTC,"@Viorel-Cosmin Miron,"
1826661,2019-09-25 12:50:31 UTC,"I think this is a particular behaviour of brave and not snapd that is at fault here. As in the previous issue filed by the reporter, I would encourage him to pursue this with the Brave upstream developers."
1826662,2020-10-07 06:07:24 UTC,"Having this problem with a new multipass based 20.04 VM - when I try to restart snapd.seeded.service, it hangs for about 5 mintues then errors out with:
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to restart 'snapd.seeded.service'.
Authenticating as: Ubuntu (ubuntu)
Password:
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
==== AUTHENTICATION FAILED ===
Failed to restart snapd.seeded.service: Access denied
See system logs and 'systemctl status snapd.seeded.service' for details."
1826662,2020-07-08 06:17:03 UTC,"I see this very same issue if I just populate a focal container and try
install a simple snap, in this test, juju-lint, which is the first run
by fce. The hint from Anton does mitigate the issue, though it takes
easily 30-60s to execute."
1826662,2020-05-15 03:17:10 UTC,Simply doing a:
1826662,2019-10-30 16:14:31 UTC,There's some useful discussion about this issue at https://forum.snapcraft.io/t/cant-install-or-refresh-snaps-on-arch-linux/8690/36
1826662,2019-10-08 20:38:48 UTC,Happens on brand new install for me. 18.04.2 LTS.
1826662,2019-09-25 12:53:50 UTC,"On first boot, snapd installs the pre-seeded snaps. During this operation installing additional snaps is not supported. There were additional bugs where an incorrectly prepared seed would stall snapd forever."
1826662,2019-06-19 06:49:22 UTC,"I got same issue on 18.04 system, here are the logs"
1826662,2019-05-28 12:31:55 UTC,@Chad Please provide the following information
1826662,2019-05-15 19:48:44 UTC,"I have exactly the same problem, but I want to add that I got this in 18.04 as well..."
1826662,2019-10-08 20:53:02 UTC,This seems to have worked for me.
1826664,2019-04-27 19:41:00 UTC,I've just pushed a fix for this here  https://github.com/MythTV/packaging/commit/578adfa06cb2e03772b83fc295cfaed073735144
1826665,2019-07-18 12:49:37 UTC,Please report this suggestion in the project bugtracker:
1826667,2019-04-27 19:15:14 UTC,"I've downloaded Clamav and COMODO. Did countless scans...found above 3000 malware and viruses and such...some I could remove others remained. Suspicious file that is 1 gb called ""swapfile"" is in my /. My home directory is not really home, when I press ""cd .."" there is something before it...I have screenshots...The hacker prbbly has root access to my PC as I'm writting this and is wetting his pants!"
1826668,2019-04-29 16:12:05 UTC,The message from the release upgrader should have mentioned using 'ppa-purge' which will downgrade the packages you've installed from the PPA to the official ones provided by the Ubuntu archive. 'add-apt-repository' will just disable the PPA and not downgrade the packages. Were you recommended to use ppa-purge?
1826668,2019-06-29 04:17:33 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1826671,2020-06-18 19:50:28 UTC,"Solved. Currently in beta, please check it out when it'll be available in my ppa (should not take more than one hour)."
1826672,2020-06-18 19:50:43 UTC,"Solved. Currently in beta, please check it out when it'll be available in my ppa (should not take more than one hour)."
1826672,2020-06-16 05:09:29 UTC,"I was doing a test for another potential bug and reproduced the issue, so it actually existed and will be fixed."
1826672,2020-06-11 23:43:41 UTC,It's been over a year now and I don't have the same setup I had at the time.  I tried on a fresh install and I could not reproduce either.
1826672,2020-06-11 20:22:28 UTC,"I tried to reproduce this and I'm not quite sure I understand / can reproduce the issue.
I tried entering values and buttons seem to activate properly."
1826673,2020-06-18 19:50:56 UTC,"Solved. Currently in beta, please check it out when it'll be available in my ppa (should not take more than one hour)."
1826679,2020-01-30 11:10:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826679,2019-08-22 15:39:22 UTC,utilizo el sofware generico no me permite actualizar
1826682,2019-05-02 01:04:32 UTC,"Fixed in revision cbc8faf49ba7fff8c95007398e788b9acbb4ab2f
https://git.launchpad.net/kicad/patch/?id=cbc8faf49ba7fff8c95007398e788b9acbb4ab2f"
1826682,2019-04-30 12:01:47 UTC,Yes I just noticed the issue you describe in #12 last night when I was considering whether to just implement it quickly or post here :-) I can take it on
1826682,2019-04-30 09:38:59 UTC,"@Jon, I haven't done anything about bus unfolding yet.  Like unit selection, it requires some research into how to do menu conditionalization that's more flexible than the standard method (we can't very well have a condition for symbols-with-2-units, symbols-with-3-units, etc.)"
1826682,2019-04-30 03:07:29 UTC,Reset to Confirmed since I can still repro the crashes as noted in #5
1826682,2019-04-30 01:23:51 UTC,"Hi Jeff,
I looked at eemodern and it looks like bus unfolding isn't implemented in the context menu yet.  Are you in the middle of that, or should someone else work on that?"
1826682,2019-04-29 23:26:30 UTC,"@John & @Jon,"
1826682,2019-04-30 09:42:29 UTC,"> Are you in the middle of that, or should someone else work on that?
"
1826682,2019-04-29 21:39:02 UTC,"@Jeff I just tried it and also see the same behavior Julien reports.
The original behavior was working like Julien's point 2 in #5:"
1826682,2019-04-29 22:01:45 UTC,"@John and @Jon,"
1826682,2019-04-28 15:11:19 UTC,@Jeff do you have time to review this patch to SCH_DRAWING_TOOL?
1826682,2019-04-28 17:03:08 UTC,"@Jon and @Julien, it's not quite correct as I don't think it will place the label correctly.  I'm about to submit a different fix; if you guys could let me know if it works that would be great."
1826682,2019-04-30 09:40:56 UTC,"PS: I'm not sure how familiar you are with the modern toolkit, but in case you're not, just to explain that pervious comment a bit further:"
1826682,2019-04-29 20:54:16 UTC,"@Jeff, thanks for your quick reply. It fix the segfault issue. However there is two remaining points :
1. It stills SEGFAULT if your cursor to the other side of the bus (let say you have an horizontal bus, unfold will start something at the bottom of the bus. If you cross it so place the bus to wire connection at the top side, instant segfault. Probably for the same reason."
1826682,2019-04-29 21:19:43 UTC,@Jeff: how much does the layout of this tool affect your ongoing modern tool framework work?
1826682,2019-04-28 17:46:32 UTC,https://github.com/KiCad/kicad-source-mirror/commit/3aaba79b878f34c57e5fa6e879ceafbd55d46240
1826684,2019-04-27 23:02:56 UTC,Attached is some analysis of the daemon's activity using the health-check tool.
1826684,2019-04-29 00:43:24 UTC,"This should probably be reported upstream at https://github.com/containerd/containerd/issues, although it's possible that there is some flag or other we could be passing when building that affects this behaviour."
1826684,2019-05-02 10:42:19 UTC,"Hrm, can't find the debug symbols package for containderd, attached gdb to the busy thread and observed:"
1826684,2020-08-18 13:12:37 UTC,"Hi Colin,"
1826684,2020-12-23 14:28:09 UTC,It's definitely reproducible with the latest 1.4.3~ds1-1 in Debian so I don't think it's likely to be fixed in other versions either.
1826684,2021-01-04 12:31:18 UTC,@Tomas: what can you reproduce exactly? The rapid system wakeup events or the strace output with the pselect6 calls specifically?
1826684,2021-01-04 22:41:44 UTC,@paride I'm seeing cca 20 wakeups/s in eventstat and strace shows some nanosleeps and epoll_waits which I think is the modern equivalent of pselect6.
1826684,2019-05-02 10:31:09 UTC,"Ubuntu Eoan, containerd 1.2.6-0ubuntu1"
1826685,2019-04-27 23:51:48 UTC,"By the way:
Extended Self Diagnostic Page - 1 to 2 via winxp is possible
If needed I can scan the two pages"
1826686,2019-12-03 00:46:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826688,2019-05-03 08:18:43 UTC,It appears this bug was first reported against gnome-shell 3.28.3-0ubuntu0.18.04.4 (from last December). So it doesn't sound like it's a very new problem. At least not in 'gnome-shell'. It might be a regression in some other package.
1826688,2019-05-03 08:15:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826688,2019-04-30 15:46:01 UTC,"Thank you for your bug report, could you add your journalctl log to the bug after getting the issue?"
1826688,2019-05-01 01:38:39 UTC,"I added the newest journalctl to the post above, and here's the entire thing."
1826689,2020-03-07 10:43:44 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. The following messages can be found in UbiquitySyslog.txt which was automatically attached to this bug report:
1826695,2019-04-28 03:16:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656105"
1826695,2019-08-22 05:18:06 UTC,"Reviewed:  https://review.opendev.org/656105
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=78629e0d3780af4a8a8cc1b5b0762e0bc8a48f1f
Submitter: Zuul
Branch:    master"
1826695,2019-09-19 10:12:11 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1826695,2020-01-31 12:12:29 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/705202"
1826695,2020-01-31 12:35:12 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705206"
1826695,2020-01-31 12:39:45 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/705208"
1826695,2020-02-03 12:29:17 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/705208
Reason: It has too many dependencies to make this backport really possible IMO."
1826695,2020-02-10 11:03:59 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/705202
Reason: I don't think we can backport it as this require https://github.com/openstack/neutron/commit/ab57410ec8e5fae97dec052a5940debd614e4e50 and this one require https://github.com/openstack/neutron/commit/975143fd08f38819859b2251da568af58c8f3a33 which changes requirements."
1826695,2020-02-10 12:05:09 UTC,"Change abandoned by Slawek Kaplonski (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/705206"
1826695,2019-07-24 13:10:46 UTC,"Increase the bug level, because this issue has been submitted for a long time."
1826698,2020-02-11 22:19:00 UTC,This issue was fixed in the openstack/python-magnumclient 2.17.0 release.
1826702,2019-09-06 21:45:23 UTC,Launch NVIDIA Settings and enable Force Composition Pipeline in the X Server Display Configuration tab under Advanced settings.
1826703,2021-02-13 12:04:57 UTC,"the same for me
jpb@jpb-HP-ProBook-4710s:~$ sudo efibootmgr  --create --disk  /dev/sda   --part  7  --label  ""grububuntu""  --loader   ""\efi\ubuntu\grubx64.efi""
[sudo] Mot de passe de jpb :
Could not prepare Boot variable: Function not implemented
jpb@jpb-HP-ProBook-4710s:~$ uname -a && lsb_release -a
Linux jpb-HP-ProBook-4710s 5.8.0-43-generic #49~20.04.1-Ubuntu SMP Fri Feb 5 09:57:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.2 LTS
Release:	20.04
Codename:	focal
jpb@jpb-HP-ProBook-4710s:~$ sudo fdisk -l /dev/sda
Disque /dev/sda : 232,91 GiB, 250059350016 octets, 488397168 secteurs
Disk model: Samsung SSD 860
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0xde2df8d4"
1826703,2019-04-29 11:40:36 UTC,Thank you for your bug report. Could you give some details on your partitions and what options/how you selected those in the installer?
1826703,2021-02-12 17:30:31 UTC,"Hello
I encounter a similar incident"
1826706,2019-04-29 11:14:13 UTC,"Could you also give a detailled example of item you add? (name, binary, etc)"
1826706,2019-04-30 16:47:13 UTC,"trying here on a fresh install
- open gnome-session-properties
- click 'add'
- write 'remmina' as name and command
- click 'add'
- the item is listed, close the dialog
- start gnome-session-properties again, the item is still listed
- restart the session, remmina is started"
1826706,2019-04-30 16:48:54 UTC,Do you have write access to ~/.config/autostart?
1826706,2019-05-01 06:25:36 UTC,"I did not have the problem in cosmic. Since I upgraded from bionic to cosmic and then immediately to disco, I did not notice whether this bug was introduced in cosmic or disco."
1826706,2019-05-01 06:29:20 UTC,"- Logged in.
- Guake did start.
- Opened Startup Applications.
- Item is not there."
1826706,2019-05-01 06:33:33 UTC,"- Logged out again.
- Logged in again.
- Guake did not start.
- Opened Startup Applications.
- Added Guake.
- Logged out and back in.
- Guake did start."
1826706,2019-07-01 04:17:17 UTC,[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.]
1826706,2019-07-01 09:04:24 UTC,Does it work if you try with remmina? Do you get any error on the command line if you start gnome-session-properties from there?
1826706,2019-07-06 07:00:41 UTC,"Thank you for following up, Sebastien. With remmina it works normally. And I've just tried again with guake. Issue persists. Does this reveal a clue?"
1826706,2019-07-06 13:06:43 UTC,"It's useful to know it's specific to some items, that might help debugging"
1826706,2019-04-29 11:13:24 UTC,"Thank you for your bug report. When you mention consecutive updates, do you mean you had the problem in cosmic already? or did you just do the update from bionic to disco (using cosmic as a step to upgrade)?"
1826706,2019-05-01 06:36:44 UTC,"It seems that in a second log in, Guake does not start. Only in the first login after adding it. And it does not seem like opening the Startup Applications is the cause of its removal."
1826708,2019-04-29 17:25:23 UTC,"Please use the StarlingX bug reporting template when creating new LPs.
Template is here: https://wiki.openstack.org/wiki/StarlingX/BugTemplate
Process is here: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process"
1826708,2019-05-08 19:51:17 UTC,"Not release gating given a reproduction scenario is not provided. Issue appears to be found by code inspection. Would be nice to fix, but not high priority. Please feel free to fix and review the code changes with the fault core (Tao Liu)"
1826710,2019-05-11 07:26:44 UTC,Security issue fixed in version 1.3.1: Do not popup unknown media types (security issue)
1826711,2019-04-28 08:52:20 UTC,"Update: installed the 418.56 driver from the PPA repository, works way nicer now.  To get here required a one time kernel boot option of nomodeset before installing the driver, also as pointed out by the IRC support channel.  Thanks!"
1826713,2019-04-29 03:24:09 UTC,"Could you please attach a screenshot of the ""stop the computer"" command you are referring to?"
1826713,2019-06-28 04:17:25 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1826716,2019-07-05 10:49:26 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826716,2019-08-13 09:06:37 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826716,2019-08-29 19:37:47 UTC,This bug was fixed in the package linux - 5.2.0-15.16
1826716,2019-09-02 13:02:10 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1020.22
1826716,2019-09-06 13:03:26 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1826716,2019-09-11 15:13:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1826716,2019-09-17 21:05:59 UTC,This bug was fixed in the package linux-oem - 4.15.0-1056.65
1826716,2019-09-23 13:44:51 UTC,This bug was fixed in the package linux-oem - 4.15.0-1056.65
1826716,2019-09-23 13:45:00 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1022.24
1826716,2019-09-23 22:36:59 UTC,This bug was fixed in the package linux-oem-osp1 - 5.0.0-1022.24
1826716,2019-09-30 21:48:23 UTC,This bug was fixed in the package linux - 4.15.0-65.74
1826716,2019-10-04 09:48:42 UTC,This bug was fixed in the package linux - 5.0.0-31.33
1826717,2019-10-16 02:06:43 UTC," I can confirm that this still occurs in Ubuntu MATE 19.10 Beta release (downloaded on 10/16/19 around 00:00utc).  I checked on my laptop and desktop, which both are affected.  My laptop has a 1366x768 screen, but my desktop has a 1920x1080, and on my desktop I can see that there are two (functioning) menus for LibreOffice in the global menu."
1826717,2019-10-16 02:07:45 UTC,Oops.  I did an alt-print screen in my previous comment.  Please see this attachment instead.
1826719,2019-07-18 17:48:43 UTC,"Fixed in revision bacbe86756bfa724c50edf886a1eb2d77ed750cd
https://git.launchpad.net/kicad/patch/?id=bacbe86756bfa724c50edf886a1eb2d77ed750cd"
1826719,2019-07-18 18:59:24 UTC,"Thanks. It looks pretty good now. I noticed the TODO note for config option. I think it would be good, it could be even more transparent for me."
1826719,2019-04-28 11:52:05 UTC,I think this should be added under the 'Items' tab in the Layers Manager.
1826719,2019-06-17 12:46:01 UTC,@Tom- I have a couple thoughts on this.  Do you mind if I handle it for 5.1.3?
1826721,2019-09-17 07:30:20 UTC,Migrated to https://github.com/widelands/widelands/issues/3417
1826723,2019-06-09 20:03:39 UTC,"Fixed in revision 00354454567108038a7c0f39aae47b55853ec2fc
https://git.launchpad.net/kicad/patch/?id=00354454567108038a7c0f39aae47b55853ec2fc"
1826724,2019-11-10 13:54:41 UTC,"As this bug is set to ""fix committed"" and the fix indeed solves the problem with fullscreen keyboard shortcut now showing correctly and working, decided to file a new bug for the remaining issue with skin preferences keyboard shortcut still missing to have a clean start and close this existing bug."
1826724,2019-09-17 19:12:05 UTC,Done (starting from terminal)
1826724,2019-09-16 17:27:18 UTC,< -bash: ./mixxx: No such file or directory
1826724,2019-09-16 14:01:48 UTC,"./mixxx --controllerDebug --developer --resourcePath res
-bash: ./mixxx: No such file or directory"
1826724,2019-09-16 10:20:04 UTC, > What exact terminal command are you using to start mixxx in developer mode?
1826724,2019-09-16 08:26:36 UTC,"when switching to english, the keybaord shortcut cmd 1 does show as expected"
1826724,2019-09-16 14:01:58 UTC,btw you are not on zulip are you?
1826724,2019-09-16 04:03:39 UTC,"Works for me, strange.
Any custom Mixxx keyboard configuration on your side?"
1826724,2019-09-15 23:13:13 UTC,or we can file a new bug for this remaining problem.
1826724,2019-09-15 23:06:56 UTC,"Hi @Jus
the shortcut for skin preferences is not shown. Is that working for you? Tested w macOS 10.14.6 + mixxx 2.3.0 (r6938)"
1826724,2019-09-15 17:25:51 UTC,Fixed with macOS 10.14.6 (18G95) and Mixxx 2.3.0-alpha-pre (build master r6938)
1826724,2019-09-14 18:08:14 UTC,Is this fixed now that https://github.com/mixxxdj/mixxx/pull/2178 has been merged?
1826724,2019-07-07 11:39:10 UTC,"https://github.com/mixxxdj/mixxx/pull/1950 merged
Also related:
https://github.com/mixxxdj/mixxx/pull/2178"
1826724,2019-04-28 11:14:05 UTC,https://github.com/mixxxdj/mixxx/pull/1950
1826724,2019-09-16 08:08:57 UTC,"Language is set to ""System""."
1826725,2019-06-30 04:17:37 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1826725,2019-04-30 12:43:37 UTC,"Yes, i have received the message and i have used ppa-purge and purged all ppas, but still no luck..."
1826725,2019-04-29 16:06:48 UTC,This is probably due to a ppa from which you have installed packages. Did you receive a message about using 'ppa-purge' to remove packages installed from ppas?
1826725,2019-04-30 15:19:12 UTC,Your VarLogDistupgradeAptclonesystemstate.tar.gz file indicates that you still had packages from PPAs installed at the time of the upgrade attempt. If you purged the PPAs after reporting the bug please open a new bug report using 'ubuntu-bug ubuntu-release-upgrader' and we'll make this one a duplicate of the new one.
1826727,2019-04-28 18:38:09 UTC,Here stdout.txt
1826727,2019-09-17 07:29:50 UTC,Migrated to https://github.com/widelands/widelands/issues/3418
1826727,2019-09-28 10:56:52 UTC,"@Pascal We can't load this savegame any more, because we had to break savegame compatibility for Build 20. So, we can't tell with 100% certainty whether this has been fixed or not. Try playing with Build 20 from now on :)"
1826729,2019-06-07 19:29:31 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.0.0 release.
1826729,2019-07-05 12:51:57 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1826729,2019-06-21 13:47:14 UTC,This issue was fixed in the openstack/tripleo-heat-templates 9.4.0 release.
1826729,2019-06-06 03:40:34 UTC,"Reviewed:  https://review.opendev.org/663400
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=42695fbd95bbbcc247886e62e971dd6eb786179d
Submitter: Zuul
Branch:    stable/rocky"
1826729,2019-06-05 17:13:33 UTC,"Reviewed:  https://review.opendev.org/663047
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a199e335b61806178f0f192138abae87336803dc
Submitter: Zuul
Branch:    stable/stein"
1826729,2019-06-04 14:22:05 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/663047"
1826729,2019-06-04 14:06:52 UTC,"Reviewed:  https://review.opendev.org/662863
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=d6b08579abbe27e2cd58ef83f95a7a1a115c9c96
Submitter: Zuul
Branch:    master"
1826729,2019-06-03 21:40:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662863"
1826729,2019-06-05 18:48:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/663400"
1826730,2019-07-20 19:30:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826730,2019-04-30 02:02:36 UTC,Is this an improvement or change compared to when you reported bug 1805077 a few months ago?
1826730,2019-04-30 04:49:00 UTC,The speaker has the crackle noise.
1826730,2019-04-30 03:52:36 UTC,"There are 3 output devices: speaker, headphone and HDMI audio, which one has this crackle noise issue?"
1826730,2019-04-30 02:31:35 UTC,"1805077 do not appear again.
1826730 is a different bug exist for a very long time(few years I think)."
1826730,2019-04-30 02:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826730,2019-04-29 12:43:22 UTC,apport information
1826730,2019-04-29 03:25:56 UTC,Please:
1826730,2019-04-29 12:43:19 UTC,apport information
1826730,2019-04-29 12:43:17 UTC,apport information
1826730,2019-04-29 12:43:15 UTC,apport information
1826730,2019-04-29 12:43:13 UTC,apport information
1826730,2019-04-29 12:38:56 UTC,"apport-collect is no reponse for a few hours, I think this program need to be rewrite."
1826730,2019-04-29 12:08:03 UTC,"I don't have ""Over-Amplification"" enabled."
1826730,2019-04-28 13:22:55 UTC,"widon@widon-X555YI:~$ cat /proc/asound/cards
 0 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xfea64000 irq 42
 1 [Generic        ]: HDA-Intel - HD-Audio Generic
                      HD-Audio Generic at 0xfea60000 irq 16
widon@widon-X555YI:~$ lspci | grep -i audio
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 02)"
1826730,2019-04-29 12:43:21 UTC,apport information
1826731,2019-05-11 11:36:20 UTC,This appears to be fixed in the cases described.
1826732,2019-06-28 04:17:21 UTC,[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]
1826732,2019-04-28 18:53:30 UTC,"The dpkg log shows that you are in the process of upgrading shim-signed and that you have DKMS modules installed.  In order to continue using DKMS kernel modules under the new Secure Boot policy, these modules must be signed, and the key used to sign them must be enrolled in your firmware."
1826736,2019-08-20 01:00:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826737,2021-01-21 22:07:17 UTC,"$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
1826737,2021-01-21 21:04:08 UTC,"lshw -version
unknown
the latest version is B.02.18"
1826737,2021-01-21 21:28:14 UTC,'dpkg -i | grep -i lshw' will provide the version. We just want to confirm you were using the package found in groovy-proposed.
1826737,2021-01-21 21:34:57 UTC,"At first glance, your lshw binary doesn't seem to come from our package."
1826737,2021-01-21 21:36:05 UTC,"root@gtest:~# lsb_release -cs
groovy"
1826737,2021-01-21 21:56:08 UTC,"My guess is that you have more than one 'lshw' on your system such as a compiled version (/usr/sbin) of 'lshw' and our Ubuntu package (/usr/bin), and when you are executing 'lshw' it calls the compiled one and not the one coming from our package."
1826737,2021-01-21 22:15:40 UTC,Yes. I had built from the source. lshw-B.02.18  and then lshw-02.18.85.
1826737,2021-01-21 19:39:20 UTC,"The way I see your outputs, is that you only get the error when performing: lshw ?"
1826737,2021-01-22 09:37:12 UTC,# VERIFICATION GROOVY
1826737,2021-01-22 09:44:25 UTC,# VERIFICATION FOCAL
1826737,2021-01-22 09:49:50 UTC,# VERIFICATION BIONIC
1826737,2021-01-26 21:45:57 UTC,This bug was fixed in the package lshw - 02.18.85-0.3ubuntu2.20.10.1
1826737,2021-01-26 21:46:03 UTC,"The verification of the Stable Release Update for lshw has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826737,2021-01-26 22:32:46 UTC,This bug was fixed in the package lshw - 02.18.85-0.3ubuntu2.20.04.1
1826737,2021-01-26 23:00:42 UTC,This bug was fixed in the package lshw - 02.18-0.1ubuntu6.18.04.2
1826737,2021-01-21 22:49:20 UTC,"No worries, glad we figured it out."
1826737,2021-01-21 19:28:14 UTC,https://en.cppreference.com/w/cpp/error/exception/what
1826737,2019-10-27 01:49:49 UTC,@Yuan - Thank you.
1826737,2021-01-21 15:38:40 UTC,"Hi Stephen,"
1826737,2021-01-21 19:06:23 UTC,I can't reproduce neither on container nor baremetal.
1826737,2019-10-26 23:14:40 UTC,I don't recall posting this bug that I don't think is a bug. NVM is not a disk so why should it be reported as a disk?
1826737,2019-10-26 15:14:54 UTC,Ref: https://github.com/lyonel/lshw/pull/45/commits/16e1d7b9e9a1aa69a59867de0aad6411c953fbfc
1826737,2019-10-27 05:56:17 UTC,"hmm, per check https://github.com/lyonel/lshw/pull/45https://github.com/lyonel/lshw/pull/45/commits/16e1d7b9e9a1aa69a59867de0aad6411c953fbfc/commits/16e1d7b9e9a1aa69a59867de0aad6411c953fbfc"
1826737,2019-10-27 13:00:18 UTC,This shows as 'nothing to compare'.
1826737,2019-12-28 13:48:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826737,2020-12-17 20:29:12 UTC,"The attachment ""lshw-hirsute.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1826737,2020-12-18 06:54:31 UTC,Has this been corrected?
1826737,2019-10-27 00:23:54 UTC,"@Stephane, I am open to it."
1826737,2021-01-07 15:12:47 UTC,[sts-sponsors[hirsute]
1826737,2021-01-07 22:14:42 UTC,This bug was fixed in the package lshw - 02.18.85-0.5ubuntu2
1826737,2021-01-14 16:07:31 UTC,[sts-sponsors][groovy][focal][bionic]
1826737,2021-01-19 17:28:21 UTC,"Hello Stephen, or anyone else affected,"
1826737,2021-01-19 17:31:29 UTC,"Hello Stephen, or anyone else affected,"
1826737,2021-01-21 03:25:16 UTC,Installed and ran the application. Although output for device is correct there is another issue.
1826737,2021-01-19 17:38:28 UTC,"Hello Stephen, or anyone else affected,"
1826737,2020-12-20 16:38:22 UTC,[sts-sponsors][hirsute]
1826742,2020-08-16 19:55:06 UTC,"Another thing to add is that the ""move"" button on the keyboard does not work with Wayland."
1826744,2019-09-15 15:06:19 UTC,Migrated to https://github.com/widelands/widelands/issues/3420
1826746,2019-05-06 05:09:01 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1826746,2019-05-06 05:08:47 UTC,I noticed that some of the sentences in this bug report are not in English.  If they were translated to English they would be accessible to more triagers.  Could you please translate them?
1826747,2019-09-25 12:57:11 UTC,"At least on Ubuntu 19.04 the socket is now placed in /run, making it accessible:"
1826749,2019-04-29 12:52:32 UTC,apport information
1826749,2019-06-29 04:17:25 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1826749,2019-04-29 12:52:44 UTC,apport information
1826749,2019-04-29 12:52:41 UTC,apport information
1826749,2019-04-29 12:52:38 UTC,apport information
1826749,2019-04-29 12:52:36 UTC,apport information
1826749,2019-04-29 12:52:34 UTC,apport information
1826749,2019-04-29 12:52:30 UTC,apport information
1826749,2019-04-29 12:52:19 UTC,apport information
1826749,2019-04-29 12:52:26 UTC,apport information
1826749,2019-04-29 12:52:24 UTC,apport information
1826749,2019-04-29 12:52:22 UTC,apport information
1826749,2019-04-29 12:03:13 UTC,Looks like this should have been filed against the linux kernel from your description.
1826749,2019-04-29 12:52:18 UTC,apport information
1826749,2019-04-29 12:52:15 UTC,apport information
1826749,2019-04-29 12:52:13 UTC,apport information
1826749,2019-04-29 12:52:28 UTC,apport information
1826752,2019-04-29 06:54:51 UTC,This seems light a straight forward enough fix to make and something that I could probably just do. Is there a preference on what to change the Place>Zone hotkey to? If so I'll make the change and submit a patch.
1826752,2019-04-29 09:25:46 UTC,"Place Zone Cutout was already changed to Shift+C (presumably due to collision with Copy), so it seems reasonable to make all the place zone commands Shift+<key>:"
1826752,2019-05-18 19:34:39 UTC,This appears to have gotten fixed at some point.
1826757,2019-05-21 15:10:54 UTC,"Created attachment 151572
This ODT is a cp/paste of the contents of the previous attachment, it loads within a second."
1826757,2019-05-21 15:14:48 UTC,This #14 fixes my package issues.
1826757,2019-05-21 15:29:12 UTC,Thanks for the update Christians. And thank you for the upstream report too.
1826757,2019-05-23 08:12:24 UTC,"(In reply to Christians from comment #5)

> Works with 6.3.0.0.alpha1+
"
1826757,2019-05-22 14:47:39 UTC,it takes 1 second in
1826757,2019-05-22 16:29:38 UTC,Works with 6.3.0.0.alpha1+
1826757,2019-05-23 02:50:58 UTC,[Automated Action] NeedInfo-To-Unconfirmed
1826757,2019-05-21 15:08:43 UTC,"Description:
Most of my ODTs take 25 secs to load in 6.2.3.2., even very small one-word docs."
1826757,2019-05-21 23:11:40 UTC,"Unconfirmed on windows 7 x64 with Version: 6.2.3.2 (x64)
Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac
CPU threads: 3; OS: Windows 6.1; UI render: default; VCL: win"
1826757,2019-05-21 13:05:51 UTC,Try the following:
1826757,2019-05-21 15:09:52 UTC,"Created attachment 151571
This ODT takes 25 secs to load in LO 6.2.3.2"
1826757,2019-05-21 11:26:44 UTC,"Unfortunately, for me, both files open quickly. Even so, this now seems to be a LibreOffice-specific problem rather than Ubuntu-related."
1826757,2019-05-20 18:09:42 UTC,"I attach an example of a document that takes 20 secs to load, followed by a cp/paste into a new document that loads very quickly."
1826757,2019-05-12 15:13:42 UTC,"From the details provided, this issue seems rooted in package misconfiguration. If you can get your packages clean and conflict free again I suspect the problem will go away. Try again:"
1826757,2019-05-03 14:05:59 UTC,"Upon Marcus' advice I installed from snap, and all works great...  tks Marcus!"
1826757,2019-04-29 17:13:56 UTC,"Thank You, yes libreoffice* was the reason for my mystery extension install..."
1826757,2019-04-29 14:48:15 UTC,"Those extensions are a result of installing like this: ""sudo apt install libreoffice*"". That pulls in all kinds of packages and extensions for libreoffice including the ones you've described."
1826757,2019-04-29 14:24:15 UTC,"Tks for looking into this guys!
* libreoffice does not appear in snap list
* in Nautilus my right click shows ""open with libreoffice writer"""
1826757,2019-04-29 13:56:04 UTC,"Could you also check that LibreOffice Writer is selected as the default ""Open With"" application for ODT files."
1826757,2019-04-29 13:48:21 UTC,"Hi Christians, could you check that you don't have the libreoffice snap installed. You can use `snap list` to check. If you do, that would explain libreoffice launching when the debians are uninstalled. You can remove it by calling `snap remove libreoffice`"
1826757,2019-04-29 13:28:28 UTC,I have since
1826757,2019-05-21 12:37:54 UTC,Opening with LO 6.2 from the links on this page
1826758,2019-06-25 15:04:34 UTC,I've just found that the issue with these hosts is that nf_conntrack_ipv4 was not a loaded module.
1826758,2019-05-16 13:47:38 UTC,"And yes, the netplan issue is in the process of being fixed but it wont be available for a little bit so I think we need a way for this to happen in the charm still. update-status maybe?"
1826758,2019-05-16 16:02:25 UTC,Another workaround is to run the following after reboot:
1826758,2019-04-29 06:28:11 UTC,I think this one is the same but for netplan: https://bugs.launchpad.net/netplan/+bug/1763608
1826758,2019-04-28 19:12:22 UTC,Interface configuration on an impacted system:
1826758,2019-05-16 13:46:39 UTC,This is the result of two things:
1826759,2021-01-28 19:47:36 UTC,Fix pushed here:
1826760,2019-05-08 15:07:38 UTC,"I find a workaround, it is not perfect but works in most the way I expect."
1826760,2020-02-10 10:08:29 UTC,"Thank you, oldmonkey, that's awesome information and helped me out tremendously."
1826762,2019-05-08 11:33:26 UTC,Please could you attach the log file for the crash.
1826762,2019-11-11 04:17:20 UTC,[Expired for Open Rails because there has been no activity for 60 days.]
1826765,2019-04-28 20:22:05 UTC,this a comment. Hi :)
1826772,2019-04-28 20:57:19 UTC,ok
1826778,2019-04-28 20:45:14 UTC,Satisfaction is more valuable.
1826778,2019-04-28 21:07:07 UTC,"You need to have money first and then ""bug it"""
1826784,2019-04-28 20:49:29 UTC,i did but  the computer say continuity: Please try again later ! :)
1826784,2019-04-28 20:50:42 UTC,#WorksAsImplemented
1826785,2019-11-08 11:53:46 UTC,"Now I use Ubuntu Mate 19.10 with Radiant Mate theme and the problem is still persistent, see my attached video for more info."
1826785,2019-11-08 04:17:26 UTC,[Expired for brisk-menu (Ubuntu) because there has been no activity for 60 days.]
1826785,2019-09-08 14:14:03 UTC,"I don't have UM 19.10 for now, but with UM 18.04.3 LTS and Brisk Menu 0.5.0 the problem is still persistent."
1826785,2019-09-06 21:51:36 UTC,I can't reproduce this using Ubuntu MATE 19.10 with Brisk Menu 0.6.0.
1826785,2019-11-08 04:17:24 UTC,[Expired for ubuntu-mate-artwork (Ubuntu) because there has been no activity for 60 days.]
1826786,2019-04-29 03:33:23 UTC,This appears to be a combination of multiple issues:
1826786,2019-05-04 08:56:06 UTC,Hello!> When I close firefox xorg ix in excution in the same way.
1826786,2019-07-04 04:17:16 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1826786,2020-08-06 03:37:41 UTC,"> I mean that xorg is working and using 50%of the cou without purpose.When I have just close fire fox.
"
1826786,2020-10-05 04:17:27 UTC,[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]
1826789,2019-10-03 14:44:15 UTC,"Base on the input from LP: #1826791, this is the way stress-ng behaves on newer series."
1826789,2020-08-06 14:58:44 UTC,We stumbled upon this issue. We were able to do some tests and results are:
1826791,2019-08-06 08:05:44 UTC,Marking this as won't fix.
1826791,2019-08-06 08:05:36 UTC,"Running with -a 0 will invoke every stressor with an instance on each CPU. Some of these stressors get I/O blocked or may be swapped out and blocked for a relatively long time before they get re-scheduled, and this can cause the timeout overrun.  Stress tests are timed out using SIGALRM so it may be the case that some of the system calls that are blocked that are not interruptible have to be waited for before completion before the stressor is terminated.   This cannot be fixed - it is a system behavioral issue that cannot be worked around."
1826791,2019-10-03 14:42:56 UTC,"Thank you Colin, I will update LP: #1826789, this has to be fixed in MAAS then."
1826791,2019-07-22 13:58:51 UTC,Can you re-run without the --aggressive and --ignite-cpu option and see if this helps?
1826791,2019-07-22 13:58:11 UTC,"Apologies for taking so long to get back to you, this issue slipped past my radar. Some triaging questions:"
1826791,2019-07-25 07:18:02 UTC,"Also, which version of stress-ng is being used? (stress-ng -V to find out)"
1826792,2019-04-29 09:50:20 UTC,"Hi FREDY,"
1826792,2019-05-04 16:29:24 UTC,"Thanks for your answer, I run de command hp-doctor and show many warnings, I could run sh *.plugin, however I tried again the command hp-plugin however it doesn't work."
1826792,2019-05-04 16:33:52 UTC,"I also tried to install the plugin download the file ""hplip-3.19.1-plugin.run"" but still doesn't work"
1826792,2019-05-07 07:30:46 UTC,"Hi Fredy,"
1826792,2019-05-28 16:07:59 UTC,"Same in hplip-3.19.5. (Ubuntu 19.10)
I tried to install with
sh hplip-3.19.1-plugin.run
But after, with hp-doctor, I have this error:"
1826792,2019-05-28 16:16:45 UTC,"Also, if I try to install with hp-plugin, I have:"
1826793,2019-04-29 01:09:30 UTC,"Hi KeePassXC maintainer here. This problem is not limited to KeePassXC-Browser Extension, any extension using Native Messaging will be blocked because of the nature with which native messaging works. The Browser itself launches a process that it communicates with using a named pipe."
1826793,2019-05-03 08:52:12 UTC,"Please note that the firefox apparmor profile is disabled by default, precisly because it has known limitations like this one. See /usr/share/doc/firefox/README.Debian."
1826793,2019-05-08 06:55:23 UTC,"Thanks.  Does anyone know if there's an upstream (Debian) bug report for this?  If not, should one be created?  Or is this simply a downstream (Ubuntu) thing?"
1826793,2019-05-08 07:19:15 UTC,"As far as I know, the firefox apparmor profile is Ubuntu-specific, not in Debian."
1826794,2019-04-29 16:02:12 UTC,"Hope you don't mind, I also pushed my patch that I was working on when I changed the status."
1826794,2019-04-29 15:40:56 UTC,"It is working. I was trying to claim it, but didn't refresh this page, and LP doesn't tell you you're overwriting things that have been changed since you loaded the issue."
1826794,2019-04-29 15:39:14 UTC,Is my fix not working?
1826794,2019-04-29 15:36:52 UTC,"Whoops, didn't see that changing! Damn..."
1826794,2019-04-29 15:23:39 UTC,I think that's a high because you can crash an actively edited file quite easily just by opening the dialog.
1826794,2019-04-29 15:28:57 UTC,Hi John:
1826795,2019-05-05 22:36:00 UTC,"Reviewed:  https://reviews.mahara.org/9958
Committed: https://git.mahara.org/mahara/mahara/commit/5ce05a26b473cc3f2d19ecf047b2004e15017b75
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    18.10_STABLE"
1826795,2019-05-05 22:34:19 UTC,"Patch for ""18.10_STABLE"" branch: https://reviews.mahara.org/9958"
1826795,2019-04-29 01:18:59 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9895"
1826795,2019-04-29 19:38:27 UTC,"Patch for ""19.04_STABLE"" branch: https://reviews.mahara.org/9904"
1826795,2019-04-29 19:38:18 UTC,"Reviewed:  https://reviews.mahara.org/9895
Committed: https://git.mahara.org/mahara/mahara/commit/59cf4d2417478be886a8f750c12fff7d710110eb
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826795,2019-04-29 19:38:35 UTC,"Reviewed:  https://reviews.mahara.org/9904
Committed: https://git.mahara.org/mahara/mahara/commit/345d6e348c2bee4ab5e80e585c27970164fea4eb
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.04_STABLE"
1826796,2019-04-29 14:50:50 UTC,"""I haven't checked the Python or Java libraries."""
1826803,2019-04-29 04:40:26 UTC,"When using depth=2, it takes 6 minutes to return, after changing it to depth=1, it takes 2 seconds only."
1826811,2017-06-23 10:52:41 UTC,"See also upstream https://bugs.kde.org/show_bug.cgi?id=381556
arm64: Handle feature registers access on 4.11 Linux kernel or later"
1826811,2019-12-19 10:03:24 UTC,"The verification of the Stable Release Update for valgrind has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826811,2019-12-19 10:03:20 UTC,This bug was fixed in the package valgrind - 1:3.13.0-2ubuntu2.2
1826811,2019-12-16 15:08:40 UTC,Thanks David for your time testing the proposed package.
1826811,2019-12-16 12:04:48 UTC,I tested on an ARM machine with the proposed package and it works fine.
1826811,2019-12-12 20:35:37 UTC,"@Jeffrey Walton,"
1826811,2019-12-12 19:01:33 UTC,[VERIFICAITON BIONIC]
1826811,2019-12-12 15:29:06 UTC,"Hello Jeffrey, or anyone else affected,"
1826811,2019-12-12 13:03:28 UTC,Uploaded in bionic[0]. It is now waiting for SRU acceptance for valgrind to start buiding in bionic-proposed and start the testing phase of the SRU.
1826811,2019-12-11 19:59:01 UTC,[Pre-SRU testing]
1826811,2019-12-11 17:41:43 UTC,I'll build a test package and start testing soon.
1826811,2019-12-11 17:40:07 UTC,-----
1826811,2018-06-14 12:40:40 UTC,"(In reply to Rob Clark from comment #13)

> heh, so this makes my problem a bit more obvious.. at one point in the past
> I had built my own valgrind (in /usr/local/bin which was ahead of /usr/bin
> in $PATH).. so in fact the problem all along was not with fedora's valgrind
> but pebkac ;-)
>
> /me reaches for brown paper bag
"
1826811,2018-06-13 20:14:44 UTC,"hohum, so that shows the HWCAP of valgrind itself, which then execs /bin/true and crashes before showing the auxv Maybe try:"
1826811,2018-06-13 20:05:40 UTC,"so, quick disclaimer, but I'm running a non-standard kernel atm, if any kernel config/etc could effect this, I can retry w/ a vanilla kernel (but not immediately, and possibly not on the same device)"
1826811,2018-06-13 19:48:17 UTC,It might be helpful to run “LD_SHOW_AUXV=1 /bin/true” with and without valgrind.
1826811,2018-06-13 19:47:16 UTC,That's from the midr_el1 read:
1826811,2018-06-13 19:36:52 UTC,"Created attachment 1451010
valgrind output"
1826811,2018-06-13 19:36:20 UTC,cmdline:
1826811,2018-06-13 19:24:33 UTC,"(In reply to Rob Clark from comment #5)

> hmm, I just saw the same issue on rawhide (valgrind 1:3.13.0-18.fc29).. did
> a patch get lost from the spec file?
"
1826811,2018-06-13 19:15:57 UTC,"(In reply to Mark Wielaard from comment #1)

> See also upstream https://bugs.kde.org/show_bug.cgi?id=381556
> arm64: Handle feature registers access on 4.11 Linux kernel or later
>
> For now worked around in valgrind valgrind-3.13.0-3.fc27 as suggested in the
> original description of this bug:
>
> --- a/coregrind/m_initimg/initimg-linux.c
> +++ b/coregrind/m_initimg/initimg-linux.c
> @@ -703,6 +703,12 @@ Addr setup_client_stack( void*  init_sp,
>                    (and anything above) are not supported by Valgrind. */
>                 auxv->u.a_val &= VKI_HWCAP_S390_TE - 1;
>              }
> +#           elif defined(VGP_arm64_linux)
> +            {
> +               /* Linux 4.11 started pupulating this for arm64, but we
> +                  currently don't support any. */
> +               auxv->u.a_val = 0;
> +            }
>  #           endif
>              break;
>  #        if defined(VGP_ppc64be_linux) || defined(VGP_ppc64le_linux)
>
> Keeping this bug open to see how upstream resolves this.
"
1826811,2017-07-07 23:05:15 UTC,"valgrind-3.13.0-4.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report."
1826811,2017-06-30 20:25:29 UTC,"valgrind-3.13.0-4.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-4315a2f0cd"
1826811,2017-06-29 20:11:01 UTC,valgrind-3.13.0-4.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4315a2f0cd
1826811,2018-06-14 11:50:06 UTC,"heh, so this makes my problem a bit more obvious.. at one point in the past I had built my own valgrind (in /usr/local/bin which was ahead of /usr/bin in $PATH).. so in fact the problem all along was not with fedora's valgrind but pebkac ;-)"
1826811,2017-06-22 16:23:16 UTC,+++ This bug was initially created as a clone of Bug #1464085 +++
1826813,2019-09-20 11:53:41 UTC,I believe this is fixed as I can no longer reproduce it on master. Please reopen if you see it again.
1826820,2019-05-01 07:44:38 UTC,"The command 'apt-get upgrade' upgraded gcc-7 from 7.3.0-27ubuntu1~18.04 to 7.4.0-1ubuntu1~18.04.
However, this bug still exists in gcc 7.4.0."
1826823,2019-08-01 19:45:27 UTC,"This is done, looks like the change wasn't tracked in launchpad since osc-placement is using storyboard."
1826823,2019-08-16 14:26:25 UTC,This issue was fixed in the openstack/osc-placement 1.6.0 release.
1826824,2019-06-27 12:47:15 UTC,"Change abandoned by caoyuan (cao.yuan@99cloud.net) on branch: master
Review: https://review.opendev.org/655075"
1826826,2019-05-13 16:48:32 UTC,"Reviewed:  https://review.opendev.org/655068
Committed: https://git.openstack.org/cgit/openstack/os-vif/commit/?id=9fb828291c31ca798f454b08ca1288d0e718398f
Submitter: Zuul
Branch:    master"
1826826,2019-06-06 19:46:57 UTC,This issue was fixed in the openstack/os-vif 1.16.0 release.
1826827,2019-05-06 06:37:52 UTC,IIUC there are two bugs here
1826827,2019-05-06 15:09:55 UTC,"> Btw, I'm assuming where you say...
My bad. Yes, you are correct. The problem is seen when decompiling the blob to source.
"
1826827,2019-07-04 03:25:53 UTC,"This assertion should be fixed by upstream commit 8f695676227 ""Avoid assertion in check_interrupts_property()"".  That should be included in dtc v1.5.1 which I hope to release soon."
1826827,2020-11-25 18:28:56 UTC,"The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to ""Incomplete"" now.
If you still think this bug report here is valid, then please switch the state back to ""New"" or ""Confirmed"" within the next 60 days, otherwise this report will be marked as ""Expired"". Or mark it as ""Fix Released"" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience."
1826829,2019-05-06 12:33:30 UTC,"Reviewed:  https://review.opendev.org/657334
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=3d8563887a2b5dd2b5e2c8705a1531888cc4af35
Submitter: Zuul
Branch:    stable/queens"
1826829,2019-05-06 08:00:12 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/657334"
1826829,2019-04-30 22:54:46 UTC,"Reviewed:  https://review.opendev.org/656451
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=d8b0dc73e2014d29908b5cc0406d5a1ffdc6b64d
Submitter: Zuul
Branch:    stable/queens"
1826829,2019-04-30 17:16:24 UTC,"Reviewed:  https://review.opendev.org/656450
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3c9f7577c4622e8fe353f53a7074dac1e5c14d4d
Submitter: Zuul
Branch:    stable/queens"
1826829,2019-04-30 16:48:48 UTC,"Reviewed:  https://review.opendev.org/656244
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=47034b224cd532c9b1d76f0aace0bdddbce9ea87
Submitter: Zuul
Branch:    stable/rocky"
1826829,2019-04-30 16:33:10 UTC,"Reviewed:  https://review.opendev.org/656442
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=b81c744370a6ef0676bb63384e5b65dbed0d4834
Submitter: Zuul
Branch:    stable/queens"
1826829,2019-04-30 05:02:11 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/656442"
1826829,2019-04-30 07:09:46 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/656450"
1826829,2019-04-29 21:12:57 UTC,"Reviewed:  https://review.opendev.org/656242
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=123535d8c92caa8be4c19aaf64eff55f8be0c50d
Submitter: Zuul
Branch:    stable/rocky"
1826829,2019-04-29 05:46:10 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/656244"
1826829,2019-04-29 05:43:41 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/656243"
1826829,2019-04-29 05:43:28 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/656242"
1826829,2019-04-30 07:21:16 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/656451"
1826829,2019-04-29 21:13:06 UTC,"Reviewed:  https://review.opendev.org/656243
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=cba7c2285758a25449fe108c304aeaad9f0c4ba3
Submitter: Zuul
Branch:    stable/rocky"
1826831,2019-07-08 04:17:19 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1826831,2019-04-29 06:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826831,2019-05-08 07:36:18 UTC,"Hello,
can you run the ""apport-collect 1826831"" command here in a terminal to collect all necessary logs?
After that please switch the report status to confirmed."
1826832,2020-05-07 04:52:57 UTC,This occurs on Ubuntu 20.04 LTS
1826832,2019-04-29 06:32:55 UTC,"This issue was introduced approximately in Ubuntu 16.04 (give or take 1 year), and I still observe it on Ubuntu 19.10."
1826833,2019-04-30 16:48:59 UTC,Did you mean /var/lib/kubelet/cpu_manager_state?
1826833,2019-06-03 14:05:00 UTC,Reverting to Fix Committed because this hasn't been released to stable yet.
1826833,2019-06-02 18:11:36 UTC,released in cs:~containers/kubernetes-worker-540
1826833,2019-05-23 09:47:08 UTC,PR link - https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/17
1826833,2019-05-23 02:33:17 UTC,"@tvansteenburgh, thanks, we will propose a PR later"
1826833,2019-05-31 14:40:48 UTC,CI should pick this up in the next 8 hours.  I'll post a revision here when it's known.
1826833,2019-05-22 03:44:38 UTC,k8s official doc [1] said:
1826833,2019-05-08 12:02:40 UTC,"> It seems that juju sets the charm config default value first.
"
1826833,2019-05-08 08:16:51 UTC,"Hi,"
1826833,2019-05-06 05:36:04 UTC,"Hi Tim,"
1826833,2019-05-22 11:24:41 UTC,"Okay, I like this idea. We'll take a look when we have time, or you are welcome to propose a PR and we'll review it."
1826834,2019-05-02 17:58:23 UTC,"# netstat -i
Kernel Interface table
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0      1500 12446482      0   1124 0       3318127      0      0      0 BMRU
eth1      9000  5429956      0      0 0       7585036      0      0      0 BMRU
eth2      9000  9629040      0      0 0      11615121      0      0      0 BMRU
lo       65536  6419518      0      0 0       6419518      0      0      0 LRU"
1826834,2019-05-02 13:37:41 UTC,From what I can see the options for the system profile are *1 :
1826834,2019-05-02 13:54:54 UTC,"After digging some more I think ""Performance per Watt (OS)"" is ok after all. Please confirm that that is the same across all the nodes."
1826834,2019-05-02 14:52:24 UTC,"To gather some stats on the previous network traffic run ""netstat -i"" on the nova-cloud-controller and pastebin the output."
1826834,2019-05-02 17:51:39 UTC,"With regards of the bios, they are set to ""perfomance"", so if you want them
in ""performance per watt(os)"" I'll ask customer to set it."
1826834,2019-05-03 08:51:13 UTC,"I see the eth0 has an mtu of 1500 where as the others are 9000 that looks like a mistake. Also, you can see from the netstat output that its been dropping some received packets"
1826834,2019-05-16 08:09:29 UTC,I believe that this is a duplicate of: https://bugs.launchpad.net/neutron/+bug/1606741
1826834,2019-05-03 15:49:29 UTC,oh and please check dmesg on the nova-cloud-controller to see if there are any pertinent messages.
1826834,2019-05-03 16:04:47 UTC,Can you also confirm that other metadata queries also take 40s+ For instancee:
1826834,2019-05-06 22:40:42 UTC,"Just popping in to make sure we are not running into LP Bug #1823740 [0]. In that bug, it is possible to have a mismatch between the space nova-cloud-controller uses and the iptables entry on memcached to allow nova-cloud-controller access. We describe the scenario and the workaround in the 19.04 charms release notes [1]."
1826834,2019-05-07 10:38:36 UTC,Hit by similar issue in Ocata: https://pastebin.canonical.com/p/SmqTpPWsyk/
1826834,2019-08-20 04:17:21 UTC,[Expired for OpenStack nova-cloud-controller charm because there has been no activity for 60 days.]
1826834,2019-05-02 12:25:32 UTC,"There is a system profile called: ""Performance Per Watt (OS)"" that seems
to be the only option close to what you describe, instead of that profile
another called ""Performance"" is selected."
1826834,2019-05-03 15:38:29 UTC,Please can you:
1826834,2019-05-02 10:02:32 UTC,I don't think we should progress with debugging until the bios has been updated and the machines rebooted.
1826834,2019-06-20 10:09:49 UTC,"I don't think this is a duplicate as in this bug the requests for metadata do return (all be it very slowly).
If anyone thinks they're are hitting this bug please check whether the following query does eventually return in the network namespace:"
1826834,2019-05-02 09:20:49 UTC,"I can't see the option, I see others that hint cpu is in performance
mode by bios, so I assume OS has no control on the power management."
1826834,2019-05-02 09:57:15 UTC,We need to be absolutely sure that the machines cpu governor is set to os control. If you are unsure about the bios options please can you list what options you do see.
1826834,2019-04-29 08:54:56 UTC,It is expected that the metadata call will be over http even though the api endpoints are https. This is because there is a special rule for the metadata ip address in the virtual router that your instance is attached to. It will intercept the metadata request and forward it to the local metadata proxy. Thats why we need the nova and neutron logs from the neutron gateway.
1826834,2019-04-29 14:47:29 UTC,It looks like ssl is a red herring here. Metadata requests are coming  into the dhcp namespace but then a broken pipe is reported in the neutron metadata proxy logs. The logs also show successfully calls out to the neutron api server and nova metadata proxy. As @dmitriis says this could be a related to https://bugs.launchpad.net/neutron/+bug/1722584.
1826834,2019-04-29 15:01:23 UTC,Actually that sport might be wrong. Lets drop it for this test:
1826834,2019-04-29 15:19:04 UTC,I'm afraid it didn't:
1826834,2019-04-29 15:58:07 UTC,Please can you delete thee previous rule and try:
1826834,2019-04-29 20:01:24 UTC,Still not there:
1826834,2019-04-29 08:06:34 UTC,Please can you provide a juju crashdump of the env? In the meantime the logs from the neutron gateway node (/var/log/nova/* and /var/log/neutron/*)
1826834,2019-04-30 17:22:17 UTC,After a bit of digging the three calls are:
1826834,2019-05-01 08:36:49 UTC,"I maybe wrong, but the query that corresponds to retrieving the slow step appears to be: https://paste.ubuntu.com/p/sttKMyRX8S/"
1826834,2019-05-01 13:56:52 UTC,"Also, please confirm that in the BIOS cpu frequency scaling settings is set to ""OS control"" mode (or equivalent) on all the nodes."
1826834,2019-05-02 07:14:08 UTC,"Query seems not to be correct when running locally, it needs to be revised:"
1826834,2019-05-02 07:29:26 UTC,"My bad, piece of the query was hidden to me locally:"
1826834,2019-05-02 08:00:35 UTC,"Sorry, I didn't quite follow the bios response. Are you saying you can't see the option in the bios or you can see it and it is set correctly?"
1826834,2019-05-02 07:37:18 UTC,no such a big difference running from nova-cc:
1826834,2019-04-30 15:46:05 UTC,The iptables rules appear to be a red herring as querying the nova metadata service directly on the nova-compute node is successful but takes 40+ seconds. The metadata request the guest makes times out after 20 seconds and hence the broken pipe messages.
1826836,2019-09-16 17:30:51 UTC,Migrated to https://github.com/widelands/widelands/issues/2135
1826836,2019-05-05 12:16:04 UTC,I don't know... i think the circumstance when a game is lost (or won) should be clear. When i started to play widelands i thought i had to conquer all the enemy military buildings to win the game.
1826836,2019-04-29 16:24:55 UTC,Although not completely against this I have some concerns:
1826836,2019-04-30 05:28:43 UTC,"I think we should not have this in multiplayer. When the enemy has destroyed your headquarters, they are usually stronger than you anyway, or you have neglected to build another warehouse."
1826845,2019-07-25 19:46:56 UTC,"The verification of the Stable Release Update for sysdig has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826845,2019-07-27 04:00:06 UTC,"Same patches were also applied to Disco
---"
1826845,2019-07-25 19:46:51 UTC,This bug was fixed in the package sysdig - 0.19.1-1ubuntu1.1
1826845,2019-07-22 13:37:13 UTC,Work with B-hwe 5.0 on Bionic.
1826845,2019-05-14 23:12:57 UTC,".debdiff attached to this comment, adding SRU paperwork to the original bug description."
1826845,2019-07-22 11:26:34 UTC,"Hello Po-Hsu, or anyone else affected,"
1826845,2019-06-03 21:34:02 UTC,affects 5.0.0-1008.9 linux-oem-osp1
1826845,2019-05-15 00:23:59 UTC,"The attachment ""sysdig_0.19.1-1ubuntu1.1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1826845,2019-07-22 11:34:08 UTC,"Also, this seems to be Fix Released in eoan, am I right?"
1826846,2019-08-29 08:31:37 UTC,"The verification of the Stable Release Update for lttng-modules has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826846,2019-08-29 08:31:32 UTC,This bug was fixed in the package lttng-modules - 2.10.5-1ubuntu1.3
1826846,2019-08-20 19:14:49 UTC,"Hello Po-Hsu, or anyone else affected,"
1826846,2019-08-19 08:02:55 UTC,"Passed with D-azure, but still failing with B-hwe Azure"
1826846,2019-08-21 14:26:04 UTC,I can confirm the package in proposed builds properly on 4.15 and 5.0 kernels and successfully installs:
1826846,2019-06-12 19:45:16 UTC,"This has trickled into Eoan as expected, 5.2.0-4.5-generic Eoan."
1826846,2019-06-03 21:41:14 UTC,Affects linux-oem-osp1 5.0.0-1008.9
1826846,2019-05-23 00:26:15 UTC,"The attachment ""lttng-modules_2.10.5-1ubuntu1.3.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1826846,2019-05-22 20:57:12 UTC,.debdiff attached to this comment. Adding SRU paperwork to original bug description.
1826846,2019-08-08 04:04:01 UTC,Test passed with D-AWS.
1826847,2020-03-11 10:41:32 UTC,"Hi,
this is a good bug, sorry to see it so late.
It is actually very similar to bug 1862138."
1826847,2020-05-11 04:17:25 UTC,[Expired for postgresql-9.5 (Ubuntu) because there has been no activity for 60 days.]
1826847,2020-03-11 10:58:19 UTC,"Oh, this was almos one year ago and as far as I concred my original attached Dockerfile with issue is working fine, so I think issue is solved"
1826848,2020-07-15 02:51:46 UTC,"All autopkgtests for the newly accepted linux-aws-5.3 (5.3.0-1032.34~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1826848,2020-06-08 18:01:25 UTC,https://git.kernel.org/torvalds/c/065fcfd49763ec71ae345bb5c5a74f961031e70e
1826848,2020-07-03 11:32:09 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1826848,2020-07-06 15:22:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'."
1826848,2020-07-14 02:58:18 UTC,"All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1826848,2020-07-14 21:52:01 UTC,"All autopkgtests for the newly accepted linux-azure-5.3 (5.3.0-1034.35~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1826848,2020-06-08 10:37:52 UTC,"The test failure is intermittent, I have sent a suggested fix upstream, will send it as SAUCE to the mailing list soon."
1826848,2020-07-20 07:58:40 UTC,The test has passed with 5.4.0-42.46 on all different arches.
1826848,2020-07-20 08:29:33 UTC,The test has passed with 5.3.0-64.58 on all different arches.
1826848,2020-07-20 16:18:05 UTC,This bug was fixed in the package linux - 5.4.0-42.46
1826848,2020-07-27 15:04:04 UTC,This bug was fixed in the package linux - 5.3.0-64.58
1826848,2020-07-28 00:57:39 UTC,This bug was fixed in the package linux - 5.4.0-42.46
1826848,2020-07-16 00:08:38 UTC,"All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1032.34~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1826848,2020-06-08 08:21:56 UTC,"BTW it has passed with the same node ""rizzo"" on 5.4.0-34.38 lowlatency kernel."
1826848,2020-07-15 22:09:42 UTC,"All autopkgtests for the newly accepted linux-aws-5.4 (5.4.0-1020.20~18.04.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1826848,2020-06-08 07:45:05 UTC,"This issue can be found on Focal 5.4.0-34.38 (node rizzo) as well.
 # selftests: net: ip_defrag.sh
 # ipv4 defrag
 # PASS
 # seed = 1591378573
 # ipv4 defrag with overlaps
 # PASS
 # seed = 1591378573
 # ipv6 defrag
 # PASS
 # seed = 1591378577
 # ipv6 defrag with overlaps
 # PASS
 # seed = 1591378577
 # ipv6 nf_conntrack defrag
 # PASS
 # seed = 1591378582
 # ipv6 nf_conntrack defrag with overlaps
 # seed = 1591378582
 # ./ip_defrag: sendto overlap: 2984: Operation not permitted
 not ok 18 selftests: net: ip_defrag.sh # exit=1"
1826848,2020-06-08 08:19:39 UTC,This is still failing with 5.4.0-33-generic on rizzo. Not sure why it passed last cycle.
1826848,2019-05-09 10:30:16 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1826848,2019-08-27 17:53:30 UTC,"I can't reproduce this in a local VM on the disco/master-next branch (tip of my branch is currently at: ebf9271500ba ""UBUNTU: upstream stable to v4.19.55, v5.1.14"")"
1826848,2019-08-30 08:12:21 UTC,"Hi Connor,
I found this was caused by ""ubuntu_cts_kernel"" that run before this kernel_selftest."
1826848,2019-09-17 15:22:31 UTC,"I've confirmed that if ""ubuntu_cts_kernel"" runs before this test, it will cause the test to fail. It will continue to fail between reboots of the virtual machine, too, so I suspect there's something persistent being added during the ""ubuntu_cts_kernel"" test that just isn't being cleaned up when it's done."
1826848,2019-09-29 16:03:37 UTC,"Test result on 5.3 Bionic-hwe:
 # selftests: net: ip_defrag.sh
 # ipv4 defrag
 # PASS
 # seed = 1569129774
 # ipv4 defrag with overlaps
 # PASS
 # seed = 1569129774
 # ipv6 defrag
 # PASS
 # seed = 1569129780
 # ipv6 defrag with overlaps
 # seed = 1569129780
 # ./ip_defrag: sendto overlap: 2120: Operation not permitted"
1826848,2019-12-10 08:55:00 UTC,Spotted on AWS 5.3 ARM64 (5.3.0-1009.10) with instance a1.large:
1826848,2020-02-25 08:00:44 UTC,"Didn't see this issue with B-5.3 (5.3.0-41.33~18.04.1), node rizzo"
1826848,2020-02-25 08:06:39 UTC,"Didn't see this issue with AWS-B-5.0 (5.0.0-1026.29-aws)
and 5.3.0-41.33-generic on node rizzo."
1826848,2020-03-05 07:11:10 UTC,Didn't see this issue with Eoan 5.3 on node rizzo
1826848,2020-03-11 03:19:26 UTC,"Found this with GCP 5.3.0-1014.15
 # selftests: net: ip_defrag.sh
 # ipv4 defrag
 # PASS
 # seed = 1583552965
 # ipv4 defrag with overlaps
 # PASS
 # seed = 1583552965
 # ipv6 defrag
 # PASS
 # seed = 1583552971
 # ipv6 defrag with overlaps
 # PASS
 # seed = 1583552971
 # ipv6 nf_conntrack defrag
 # PASS
 # seed = 1583552976
 # ipv6 nf_conntrack defrag with overlaps
 # seed = 1583552976
 # ./ip_defrag: sendto overlap: 2800: Operation not permitted
 not ok 18 selftests: net: ip_defrag.sh # exit=1"
1826848,2020-03-11 08:09:46 UTC,To give more information on this issue:
1826848,2020-04-22 07:27:30 UTC,Found this with 5.3 Eoan on node rizzo
1826848,2019-12-10 09:54:36 UTC,"I am working on this test case. ip_defrag.sh fails with non-overlapping as well, but only sometimes. I managed to find out the cause, and sent a fix upstream, but this is under discussion now on how to fix it."
1826850,2019-07-02 04:17:31 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1826850,2019-07-02 09:02:27 UTC,"Why is this ticket incomplete ? What information are you missing ?
I have seen several people having similar problems with discs marked as broken just because they where once connected to a broken controller or cable or just tested by the manufacturer with faulty components. The drive is still ok even if it once had transmission errors for example."
1826850,2019-05-02 13:24:39 UTC,next one
1826850,2019-05-02 13:23:37 UTC,one testlog from seatools
1826850,2019-05-02 13:21:52 UTC,Hi
1826850,2019-04-30 08:42:31 UTC,"I will try to run the seagate tool, but I want to point out that we
installed 32 band new durawrite drives in 32 different machines and they
all show the same behaviour in maas."
1826850,2019-05-02 13:24:07 UTC,another log
1826850,2019-04-30 08:04:22 UTC,It looks like the test failed due to the drive having many ECC errors. I would check these drives using the manufactures tool[1]
1826852,2019-09-25 12:59:27 UTC,I can confirm this bug but I don't believe it is a problem in snapd itself. I think the eclipse snap needs to be updated to work correctly with the JRE it bundles.
1826852,2019-09-25 13:53:53 UTC,This bug should probably be filed over at https://github.com/snapcrafters/eclipse/issues
1826853,2019-04-29 14:11:51 UTC,"This goes for all the appstream metadata, screenshots and icons etc not being picked up either."
1826853,2019-04-29 15:07:32 UTC,Ignore my comment above that issue should be fixed by our Snap builds updating the version of snapcraft they use.
1826853,2019-10-23 17:34:23 UTC,https://github.com/snapcore/snapcraft/pull/2762
1826857,2019-07-18 12:48:13 UTC,@axino
1826857,2019-07-23 14:28:50 UTC,"I don't think I tested with OVS out of the picture. However, none of the physical interface was enslaved to an OVS bridge, so I'd say this is not an ovs bug and can likely be repro'ed outside of OVS. I don't have time to do this in the short term though."
1826857,2019-08-14 16:09:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826857,2019-08-14 16:24:29 UTC,"Correction : I tested today and this bug cannot be reproduced without OVS, at least on 4.15.0-55-generic. Offloading works properly even when the interface is in a linuxbridge or in a bond."
1826858,2019-05-08 19:14:50 UTC,Maybe this can help https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/comments/42?
1826858,2019-05-08 15:34:49 UTC,Most freezes seem to happen while using Firefox
1826858,2019-07-17 11:29:02 UTC,Is it possible to find out it's a kernel regression or mesa?
1826858,2019-05-07 07:56:10 UTC,Had a couple more freezes while running the latest BIOS.
1826858,2019-06-13 15:41:48 UTC,With the workaround from the bug in comment #9 I am no longer experiencing freezes.
1826858,2019-05-02 08:22:08 UTC,Thanks for the heads-up about the BIOS update. I have applied it and will see if the hang reoccurs.
1826858,2019-05-02 05:18:51 UTC,Does update the BIOS to latest version (A19) help?
1826858,2019-04-29 10:30:09 UTC,This change was made by a bot.
1826858,2019-04-29 10:22:21 UTC,"I have not identified any common state with then freeze occurs, so don't have reproduction scenario at the moment."
1826858,2019-05-03 18:36:13 UTC,"Hi, same thing happens to my Dell 7390 after upgrading to 19.04, with kernel 5.0. This happens only after 30-40 seconds from when I connect my USB mouse to it. Downgrading kernel ""resolves"" issue."
1826859,2019-05-02 08:09:03 UTC,It looks like there's an external dependency here:
1826864,2019-04-29 10:57:51 UTC,"Assigning to Blake, since he wrote the code to send the ipxe config over http, IIRC."
1826865,2019-04-30 09:25:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656482"
1826865,2019-05-27 11:13:37 UTC,"Reviewed:  https://review.opendev.org/651580
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=685f4c456a1f5e0b0423b25d7d914d4303276f8a
Submitter: Zuul
Branch:    master"
1826865,2019-08-28 11:21:16 UTC,"Reviewed:  https://review.opendev.org/656482
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=5206717f084180c2d3cc994775f36f05f5475315
Submitter: Zuul
Branch:    master"
1826865,2019-09-15 19:06:08 UTC,This issue was fixed in the openstack/kuryr-kubernetes 1.1.0 release.
1826867,2019-05-30 14:18:09 UTC,"Upstream has released a fix, the  reported does not respond to my request for testing."
1826867,2019-05-11 19:54:05 UTC,"hi Lonnie,"
1826867,2019-05-04 17:29:41 UTC,"hi Lonnie,"
1826867,2019-04-29 11:42:20 UTC,"As a work around, I notice that Freemind is made available via a snap package in the GNOME Software center."
1826867,2019-05-06 02:25:27 UTC,"When I ran freeplane from a terminal window, I noticed this tiny box pop up on one of the three 4K monitors pop up:
https://i.imgur.com/TejMgt8.png"
1826868,2019-06-18 06:21:14 UTC,"this is added to linux-oem-osp1 in bionic-proposed, please test"
1826868,2019-08-22 16:15:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1826868,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1826868,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1826868,2019-07-08 09:39:46 UTC,This bug was fixed in the package linux-oem - 4.15.0-1045.50
1826868,2019-07-03 13:02:44 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1826868,2019-07-03 11:02:58 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1826868,2019-06-17 19:54:57 UTC,This bug was fixed in the package linux-oem - 4.15.0-1043.48
1826868,2019-05-28 10:42:55 UTC,Similar to #1829621? Please test the kernel in the bug.
1826868,2019-05-29 00:55:15 UTC,"supplement for #8, don't forget to remove the module para in the #3 before testing the #8"
1826868,2019-05-29 00:53:52 UTC,"I backported a i915 patch, let us see if it can fix this problem on glk machines, please test this kernel:"
1826868,2019-05-20 08:39:18 UTC,"Same on ""Teclast F7 Plus"" with Ubuntu 19.04
#3 worked perfectly, thanks! :)"
1826868,2019-05-12 13:01:05 UTC,same on dell precision 7740
1826868,2019-04-30 09:08:57 UTC,"Hi Hui,"
1826868,2019-04-29 13:24:43 UTC,Please take a try:
1826868,2019-04-29 11:30:06 UTC,This change was made by a bot.
1826868,2019-05-29 22:43:43 UTC,"Hi Hui,"
1826869,2019-08-29 16:25:43 UTC,Maybe same bug as here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416 ?
1826869,2019-04-29 12:00:07 UTC,This change was made by a bot.
1826870,2019-05-14 09:52:38 UTC,xenial: None of the failures are regressions; the apport one we can also see just with apport as trigger.
1826870,2019-05-16 10:22:34 UTC,This bug was fixed in the package python-apt - 1.1.0~beta1ubuntu0.16.04.4
1826870,2019-05-16 10:08:55 UTC,This bug was fixed in the package python-apt - 1.6.4
1826870,2019-05-15 20:40:07 UTC,"Well, no, I'm not going to waste resources retrying all the archs, I only retried ppc64el."
1826870,2019-05-15 20:25:54 UTC,I don't see apt-clone having been tried with itself as a trigger for amd64.
1826870,2019-05-14 11:40:55 UTC,"bionic: Only apt-clone and snapcraft left after retries. Retried them both with themselves as triggers, and they're still failing, so no regressions either."
1826870,2019-05-13 10:33:53 UTC,"xenial:
- ubuntu-make not a regression, same bug as before
- apport retried
- snapcraft not a regression, same issues as before"
1826870,2019-05-06 11:03:06 UTC,"Hello Julian, or anyone else affected,"
1826870,2019-05-13 08:54:47 UTC,"The verification of the Stable Release Update for python-apt has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826870,2019-05-06 10:55:32 UTC,"Hello Julian, or anyone else affected,"
1826870,2019-04-29 11:40:50 UTC,"This was fixed in disco, in 1.8.4. It also affects cosmic and bionic; and the proposed SRU for bug 1795407 in xenial."
1826870,2019-05-13 10:16:18 UTC,Both the bionic and xenial uploads seems to have a few ADT regressions - could you take at those and see if they're not regressions? Thanks!
1826870,2019-05-09 14:48:03 UTC,"I installed the upgrades, and ran the script in the bug description and see if it got fixed."
1826870,2019-05-13 08:54:42 UTC,This bug was fixed in the package python-apt - 1.7.1
1826870,2019-05-06 11:16:14 UTC,"Hello Julian, or anyone else affected,"
1826872,2019-06-23 12:35:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826872,2019-06-23 12:41:38 UTC,Same issue happens with 18.04 installer
1826872,2019-06-23 12:52:18 UTC,It looks like the installer install the efi directory to sda even if you ask it to install to the USB disk(sdb).
1826874,2019-07-03 08:16:38 UTC,"TB 60.8 ESR:
https://hg.mozilla.org/releases/comm-esr60/rev/cf751a447cd83a52d0c046d4605c915ba400b26b"
1826874,2019-06-11 20:51:47 UTC,"Well, that patch doesn't apply to comm-esr60 at all."
1826874,2019-05-07 20:37:04 UTC,"TB 67 beta 3:
https://hg.mozilla.org/releases/comm-beta/rev/006b4646c4f2e12645fcc5b6afd53da71d50da20"
1826874,2019-05-05 16:07:23 UTC,"Thank you - I think. When I filed this bug report with Mozilla, back on March 28th, I anticipated that this code would be REMOVED - providing only a fixed dialog box title instead, as with Empty Junk. No more, no less."
1826874,2019-05-05 06:42:02 UTC,"Pushed by <email address hidden>:
https://hg.mozilla.org/comm-central/rev/7e7a8c180b0c
Ask for confirmation on the real trash folder if a non-trash folder was selected. r=jorgk"
1826874,2019-05-06 20:57:39 UTC,These questions should be asked on the upstream bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1547664
1826874,2019-05-04 19:56:05 UTC,"Comment on attachment 9062698
1547664.patch"
1826874,2019-05-04 13:12:50 UTC,"Created attachment 9062698
1547664.patch"
1826874,2019-05-04 12:46:10 UTC,There is already a note about this weirdness in the code: https://searchfox.org/comm-central/source/mail/base/content/folderPane.js#2651 :)
1826874,2019-05-04 11:13:26 UTC,"And which folder does it actually empty?
I think we did this, because we also use this to empty the junk folder. But the context menu item to empty Junk or Trash shows only on the Junk and Trash folders. Not that this main menu item is active on any folder, but picks up the name of the current folder (but this one won't be emptied), this would be a bug."
1826874,2019-04-29 12:57:28 UTC,"Thanks for the report. I can reproduce the issue with upstream builds, so it's not Ubuntu-specific.
Upstream bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1547664"
1826874,2019-04-29 09:34:43 UTC,"Created attachment 9061306
tb-empty-trash.png"
1826874,2019-05-04 20:04:21 UTC,Yes.
1826876,2019-06-29 04:17:34 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1826876,2019-04-29 16:02:05 UTC,You appear to have graphics drivers installed from a PPA. Did you receive a message about using 'ppa-purge' to remove third party packages?
1826876,2019-04-29 16:43:42 UTC,"Yes I did recieve a message about using 'ppa-purge'. Although it is very unclear repository you should purge. I also did try upgrading with disabling everything under 'Other Sofware' and it still did not work, so I figured it couldn't have been any of the PPA:s."
1826878,2019-04-29 13:16:48 UTC,"I have another data point to add. As I was preparing to logout and log back in, I noticed that the menu became responsive again when I closed Nautilus, i.e. the two windows for ""Files"" that appear in the menu in the screenshot."
1826878,2019-09-09 02:20:18 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1826878,2019-09-09 12:20:51 UTC,"It has not happened since I reported it.  I have been rebooting a little more frequently, which I think helps."
1826878,2019-11-09 04:17:29 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1826879,2019-05-07 15:35:10 UTC,"As for the number of workers, I will increase it and let you know the outcome. Thank you,"
1826879,2019-11-26 04:17:42 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1826879,2019-05-28 19:20:56 UTC,It is good to hear that commands like 'get all machines' will be paginated!
1826879,2019-05-28 18:44:35 UTC,"Increasing workers won’t increase the speed of the API! As described above the API is slow because it’s *not* paginated, but there are plans to address that!"
1826879,2019-05-28 18:19:42 UTC,I increased the number of workers to 8 but it doesn't seem to have improve speed. We are adding more and more machines and this is becoming more and more of an issue.
1826879,2019-05-08 20:53:19 UTC,The workers won't help with API calls provided that this only helps in improving load handling for multiple rack controllers connected to the region controllers.
1826879,2019-05-07 15:29:12 UTC,"Like I said, this is an external process doing API calls to MaaS. This process is located on the same VM as MaaS, but still not part of MaaS code. To proove my point, here's the service and the script."
1826879,2019-05-07 15:34:41 UTC,"I have stopped this service and will report back after 24hours that it has been down. But at first glance, I don't see any improvement in performance."
1826879,2019-05-06 19:22:48 UTC,"Guillaume,"
1826879,2019-04-29 13:26:48 UTC,Please provide the following information:
1826879,2019-05-06 15:05:08 UTC,"Hello,"
1826879,2019-05-06 14:13:22 UTC,"Looking at the MAAS logs, I see the following:"
1826879,2019-05-03 12:45:42 UTC,https://www.dropbox.com/s/byepzib9q8nsvcg/maas_logs.tar.gz?dl=0
1826879,2019-05-01 19:29:12 UTC,"Guillaume,"
1826879,2019-04-29 14:38:11 UTC,"I am unable to attach MAAS Logs (/var/log/maas/*.log). the operation is timing out, my tar.gz file is around 500MB"
1826879,2019-04-29 13:53:40 UTC,"Hello,"
1826879,2019-05-06 22:18:43 UTC,"Also, have you tried increasing the number of regiond workers ? Try something like this and see if that makes any difference: https://docs.maas.io/devel/en/installconfig-region#increasing-the-number-of-regiond-daemon-workers-for-improved-performance"
1826883,2019-04-29 19:28:41 UTC,"I marked debian-bug 918742 as being the upstream for this, but technically that bug was against fakechroot and the only change was to disable the hanging test; however jemalloc2 in debian did fix this, and the changelog entry for the fix only mentions that debian bug."
1826884,2019-04-29 14:01:42 UTC,See <https://github.com/cffi/cffi/pull/142> for context.
1826886,2019-11-29 22:53:56 UTC,"2019-11-22_20-00-00
$ system application-list
+---------------------+--------------------------------+-------------------------------+--------------------+---------+-----------+

| application         | version                        | manifest name                 | manifest file      | status  | progress  |


+---------------------+--------------------------------+-------------------------------+--------------------+---------+-----------+

| platform-integ-apps | 1.0-8                          | platform-integration-manifest | manifest.yaml      | applied | completed |
| stx-openstack       | 1.0-19-centos-stable-versioned | armada-manifest               | stx-openstack.yaml | applied | completed
"
1826886,2020-01-16 20:16:50 UTC,closing
1826886,2019-12-30 19:50:47 UTC,"As per agreement with the community, moving unresolved medium priority bugs (< 100 days OR recently reproduced) from stx.3.0 to stx.4.0"
1826886,2019-12-10 08:24:33 UTC,"Hi pengpeng and Wendy:
    do you meet same issue recently?"
1826886,2019-12-10 06:00:08 UTC,We have not observed this error in our recent test.
1826886,2019-12-03 02:57:59 UTC,Latest case reported by Mitchell is not the same as Peng reported I think.
1826886,2019-11-29 23:07:01 UTC,"see bash.log (controller-0)
2019-11-29T22:27:58.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 openstack --os-username 'tenant1' --os-password 'Li69nux*' --os-project-name tenant1 --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne volume list
2019-11-29T22:28:52.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 openstack --os-username 'tenant1' --os-password 'Li69nux*' --os-project-name tenant1 --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne volume create --image=8263b829-062c-47c4-b765-de0b64f87724 --size=29 --bootable centos-size29-1
2019-11-29T22:28:59.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 openstack --os-username 'tenant1' --os-password 'Li69nux*' --os-project-name tenant1 --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne volume list
2019-11-29T22:30:25.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 openstack --os-username 'tenant1' --os-password 'Li69nux*' --os-project-name tenant1 --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne volume create --image=a1a2fbfb-e793-4d27-884e-89fc09b9849f --size=29 --bootable win-size29-1
2019-11-29T22:30:31.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 openstack --os-username 'tenant1' --os-password 'Li69nux*' --os-project-name tenant1 --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne volume list
2019-11-29T22:31:07.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 openstack --os-username 'tenant1' --os-password 'Li69nux*' --os-project-name tenant1 --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne image show a1a2fbfb-e793-4d27-884e-89fc09b9849f
2019-11-29T22:31:36.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 openstack --os-username 'tenant1' --os-password 'Li69nux*' --os-project-name tenant1 --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne volume list
2019-11-29T22:32:20.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 sudo tail /var/log/bash.log
2019-11-29T22:33:56.000 controller-0 -sh: info HISTORY: PID=2487534 UID=42425 openstack --os-username 'tenant1' --os-password 'Li69nux*' --os-project-name tenant1 --os-auth-url http://keystone.openstack.svc.cluster.loca..."
1826886,2020-05-13 17:27:11 UTC,Closing (marking status as Invalid which we use for Not Reproducible issues) based on notes above
1826886,2019-11-29 22:49:03 UTC,"I am seeing the command intermittently fail during volume creation eg. where the volume is ""downloading"" state
see 500 error during downloading in the attached logs (controller-1)"
1826886,2020-01-16 20:17:33 UTC,20200111T023000Z
1826886,2019-08-23 17:52:50 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1826886,2019-07-31 09:15:39 UTC,"The log is 2019-07-24, but test scripts runs on 2019-07-25.
Could you please make sure the log is valid? Thanks."
1826886,2019-07-25 13:42:09 UTC,This issue still seems to be apparent (intermittently)
1826886,2019-05-27 01:24:59 UTC,We are not able to reproduce this issue in recent loads.
1826886,2019-05-09 08:40:24 UTC,"From the log, it shows cinder failed to connect db at 09:24:45, but succeed to connect db after 09:52:08"
1826886,2019-05-08 18:58:48 UTC,Can this bug please be re-tested and verified if it still occurs?  It may have been fixed by the big Ceph upgrade.
1826886,2019-05-01 18:24:44 UTC,Marking stx.2.0 gating as continual access to the cinder CLI is a basic requirement for OpenStack containers. Issue is intermittent so setting priority to medium.
1826886,2019-05-01 14:39:59 UTC,"Peng - the timeline you provide is helpful.  Since it is taken from a load that was running on May 1st, please attach the logs for this May 1st timeline."
1826886,2019-05-01 14:06:09 UTC,Rebooting was not invoked before this cinder CMD failure.
1826886,2019-04-29 17:23:04 UTC,"There is not enough info in this bug to start an investigation.
Please provide the following:
1) What steps are done in the TC nova/test_evacuate_vms.py::TestOneHostAvail::()::test_reboot_only_host?
2) What steps were done on this lab in the 10 minutes or so leading up to the cinder command failing?"
1826886,2019-11-25 12:59:52 UTC,"Hi pengpeng:
   would you answer fangliang's question ?"
1826887,2021-02-12 12:37:44 UTC,Still there in focal.
1826887,2020-03-26 08:07:50 UTC,Still happens in Focal.
1826887,2019-04-29 14:22:34 UTC,apport information
1826887,2019-04-29 14:22:35 UTC,apport information
1826887,2020-03-26 07:59:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826888,2019-05-15 16:26:44 UTC,TRIAGE:
1826888,2019-05-17 09:10:35 UTC,@ajkavanagh you are correct that changing the rbd-image-backend while there are still instances in existence that are using a prior backend type is not supported by Nova (primarily because image conversion during migration is not supported). While it might be safer to make this option install-time-only I also think it might be a bit frustrating to not allow users to change their mind about backend type post-deployment. Therefore I think that adding a config option message (i.e. in config.yaml) to explain that this should not be changed while you still have running instances is a good idea. If we really wanted to make it one-shot then we could add an action to change it post-install.
1826888,2019-05-17 11:43:32 UTC,"@hopem - yes, I think we are agreed.  I don't really like config items you can't change later, so I was playing a bit of devil's advocate there :)"
1826888,2019-11-13 17:00:32 UTC,"Reviewed:  https://review.opendev.org/693736
Committed: https://git.openstack.org/cgit/openstack/charm-deployment-guide/commit/?id=e23edc0a81ac68881d455e5934c3344a7fa7ab68
Submitter: Zuul
Branch:    master"
1826889,2019-06-19 02:27:27 UTC,"Fixed in revision 1ef2f84f72d87760b702515adf2f6df80c944fb7
https://git.launchpad.net/kicad/patch/?id=1ef2f84f72d87760b702515adf2f6df80c944fb7"
1826889,2019-05-04 13:15:52 UTC,"Yes, that's my opinion. It's logical that if I use Save As, just like in any other software, the further edits go to the latest saved version, not to other versions saved elswhere. In this case it's logical that only the version saved to a library with Save As is edited, not the module which is in the board. But the tooltip and icon don't reflect that actual behavior."
1826889,2019-04-29 15:29:40 UTC,"Why do you think it should not also be saved on board, if it comes from the board?"
1826889,2019-04-29 16:36:33 UTC,I think this is a bug. This is normal:
1826889,2019-05-04 12:29:08 UTC,"Just so I clear, the issue here just the icon and the tooltip are wrong not the actual behavior?"
1826890,2019-04-29 14:58:53 UTC,A patch is available in the working/user/gmcharlt/lp1826890_page_title branch:
1826890,2019-05-04 22:16:12 UTC,Tested and works as advertised.  Signed-off branch at https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gcollum/lp1826890_page_title-signoff
1826890,2019-05-07 15:55:33 UTC,"Pushed to master, rel_3_3, rel_3_2, and rel_3_1. Thanks for testing, Garry!"
1826892,2019-05-01 13:57:39 UTC,I've had a look at the charms' code to see what this might entail and one potential way to implement a second binding could be to add a new publish_url method [1] which would provide the url for a second space/binding should it be configured. That way the vault charm can optionally be configured on more than one space such that other charms can consume it without needing to be configured on its primary network.
1826892,2019-05-17 11:46:54 UTC,Patch: https://review.opendev.org/#/c/659781/
1826892,2019-07-10 14:03:20 UTC,interface-vault-kv patch:
1826892,2019-08-29 01:15:28 UTC,It seems to me that Juju could be extended to better support things like this:
1826892,2019-09-12 19:29:30 UTC,Please see https://bugs.launchpad.net/vault-charm/+bug/1843809 which seems to have been caused by the above change.
1826892,2020-02-05 17:27:46 UTC,This is actually fixed and released since the patch in comment #5 landed and is synced into the charm as part of 19.10.
1826894,2019-11-22 11:36:55 UTC,"Reviewed:  https://review.opendev.org/694334
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3ea3c7ca92bb67696f64b0248a594d89b1fba05c
Submitter: Zuul
Branch:    stable/rocky"
1826894,2020-02-13 18:15:04 UTC,"Reviewed:  https://review.opendev.org/696059
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=f1eb048f7d22a2080c5ee9d68a09be7fb4ba9e60
Submitter: Zuul
Branch:    stable/queens"
1826894,2020-01-29 18:16:23 UTC,"Change abandoned by wes hayutin (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/696059
Reason: taking out of gate queue.."
1826894,2019-11-26 10:55:25 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/696059"
1826894,2019-11-14 15:47:37 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/694334"
1826894,2020-02-13 12:05:11 UTC,"Change abandoned by Emilien Macchi (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/696059
Reason: Gate is red, we said no recheck."
1826894,2019-07-05 12:51:18 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1826894,2019-06-26 12:28:05 UTC,"Reviewed:  https://review.opendev.org/666652
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=086238e9110555f8612cb39336e9b553b5353e18
Submitter: Zuul
Branch:    stable/stein"
1826894,2019-06-20 17:25:57 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/666652"
1826894,2019-07-26 18:16:13 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.1.0 release.
1826894,2019-06-20 16:45:20 UTC,"Reviewed:  https://review.opendev.org/656361
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7c379543ccab831da0bf4f8f4b850b534d5c5247
Submitter: Zuul
Branch:    master"
1826894,2019-04-29 15:53:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656361"
1826895,2019-05-31 20:14:55 UTC,Verified in load 2019-05-28_17-05-57
1826895,2019-05-01 17:53:03 UTC,"Marking stx.2.0 gating as alarms should not exist after an uncontrolled swact.
This issue is likely a duplicate of https://bugs.launchpad.net/starlingx/+bug/1826418 but assigning to Bin to confirm."
1826895,2019-05-14 19:04:17 UTC,This looks like a dup of https://bugs.launchpad.net/starlingx/+bug/1826418
1826895,2019-05-22 20:20:43 UTC,Duplicate bug was merged on May 22. Review: https://review.opendev.org/660424
1826896,2019-04-29 21:06:43 UTC,Ok solved it
1826896,2019-05-01 20:32:33 UTC,I was able to recreate this by removing the /var/log/installer folder and replacing it with a zero byte file.
1826898,2019-04-29 16:36:11 UTC,The other option that just came to my mind is to blacklist pacamaker/corosync AND their dependencies
1826898,2019-05-01 06:31:40 UTC,"I would suggest that we should fix the real problem, which is that restarting corosync causes pacemaker to stop but does not cause it to start again."
1826898,2019-06-04 10:26:56 UTC,"Just got hit by this over the weekend with corosync (https://usn.ubuntu.com/4000-1/) leaving pacemaker and haproxy dead. We're running an older hacluster charm rev 33, but it was still a bit annoying."
1826898,2019-06-04 16:36:43 UTC,"On Wed, 2019-05-01 at 06:31 +0000, Trent Lloyd wrote:

> I would suggest that we should fix the real problem, which is that
> restarting corosync causes pacemaker to stop but does not cause it to
> start again.
>
> On previous installations where I used Corosync/Pacemaker we actually
> configured corosync to start pacemaker. I remember looking at this
> myself at one point and I think technically that functionality might
> have been deprecated but I'd have to check I may be recalling that
> incorrectly.
>
> It would seem the same should be possible by updating the systemd
> units
> with the appropriate configuration to make them restart with each
> other.
> Off the top of my head I am guessing like most packages they are not
> native scripts though I wonder if we can add special headers to the
> sysV
> scripts like most other systemd generator sources, to set them
> anyway?
"
1826898,2019-06-05 10:38:26 UTC,we have correlated the apt-update on hacluster components with the start of the issue when the pacemaker loses the quorum....
1826898,2019-06-06 14:13:37 UTC,"As a note, in Foundations/Bootstack clouds, we solve this unattended-upgrades issue by deploying charm-landscape-client to all hosts and disabling unattended-upgrades through it's config options."
1826898,2019-06-11 07:06:50 UTC,"Previous bug, which supposedly fixed this issue on xenial & bionic:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892"
1826898,2019-11-12 14:07:09 UTC,Proposed patch - https://review.opendev.org/#/c/693080
1826898,2019-12-20 02:27:32 UTC,"Change abandoned by Felipe Reyes (<email address hidden>) on branch: master
Review: https://review.opendev.org/693080"
1826898,2020-03-03 09:17:01 UTC,The review in #10 mentions another approach to address this issue
1826899,2019-08-20 00:57:59 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, therefore this bug does not contain any information about the version of OS being used or any hints about hardware. Therefore, this bug is invalid. Please report bugs by opening a terminal and typing ""ubuntu-bug {packagename}"" in the future."
1826901,2019-04-30 10:30:04 UTC,"No I don't speak Burmese, it is for a friend. I'm looking to help him to move on LO, and maybe Ubuntu because he can't have an spellchecker in his language with MSOffice, and avoid him font problems (also with Indesign, utf-8 is not used for his language). If he moves to LO maybe he will be motivated to help. But it's pity to not create a package even if it is not complete. This don't encourage people to translate."
1826901,2019-04-30 10:14:14 UTC,"IIRC this language was not packaged at Debian because of its incompleteness [1]. If you speak Burmese, please help out! [2]"
1826902,2019-04-30 08:10:57 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?"
1826902,2019-06-30 04:17:28 UTC,[Expired for usbmuxd (Ubuntu) because there has been no activity for 60 days.]
1826908,2019-04-29 21:49:55 UTC,"That's got it properly triaged.  I only work on postfix in Debian, so I can't say if this will be fixed or not in Ubuntu."
1826911,2019-05-16 15:03:27 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1826911,2019-05-16 21:02:25 UTC,"Verification:
ubuntu@d06-2:~$ cat /proc/version
Linux version 4.15.0-51-generic (buildd@bos02-arm64-037) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #55-Ubuntu SMP Wed May 15 14:27:56 UTC 2019"
1826911,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1826912,2019-06-10 02:51:43 UTC,"It was tried with several minimal config in virtual environment and the issue was not reproduced for weeks, so close this."
1826912,2019-05-30 02:22:23 UTC,"@Elio, please update whether you can see this issue or not."
1826912,2019-05-23 06:51:39 UTC,"For LP1827952, it is just about 2 benign error message from stevedore. These 2 error message will not cause any issue. So it is not the same issue as this one."
1826912,2019-05-23 05:29:17 UTC,"today I check again, apply succeed. with configuration on wiki"
1826912,2019-05-23 03:50:06 UTC,"@Martin, I think this LP may of duplicate of https://bugs.launchpad.net/starlingx/+bug/1827952, please discuss with Shuicheng."
1826912,2019-05-23 01:53:04 UTC,I use 0428 daily build
1826912,2019-05-21 23:41:23 UTC,"@Martin, are you reproduce the issue using 20190428T013000Z? Or are you using the latest Cengen ISO? Please specify the build#."
1826912,2019-05-21 14:46:04 UTC,"application apply fail with this configuration
+---------------+-----------------+---------------+--------------+------------------------------------------+

| application   | manifest name   | manifest file | status       | progress                                 |


+---------------+-----------------+---------------+--------------+------------------------------------------+

| stx-openstack | armada-manifest | manifest.yaml | apply-failed | operation aborted, check logs for detail |


+---------------+-----------------+---------------+--------------+------------------------------------------+"
1826912,2019-05-17 16:30:31 UTC,Please retest it under minimal config documented on wiki:
1826912,2019-05-07 08:29:04 UTC,"@gprabakx, before running ""application-upload"", please check the status of ""tiller"" pod and deployment and service, by:
$ kubectl get pods --all-namespaces | grep tiller
$ kubectl get services --all-namespaces | grep tiller
$ kubectl get deployments.apps --all-namespaces | grep tiller"
1826912,2019-05-15 03:03:03 UTC,please check if this bug is of duplicate of LP: https://bugs.launchpad.net/starlingx/+bug/1826445
1826912,2019-05-10 01:20:58 UTC,"@elio1979 and @gprabakx, can you confirm that after having bigger RAM sizes with VMs, this application-apply can work well?"
1826912,2019-05-08 01:55:07 UTC,@elio1979 please see VM specs for 2+2+2 nodes in the attachment.
1826912,2019-05-07 20:00:03 UTC,"Yong, could you provide your vm specs?"
1826912,2019-05-07 12:17:04 UTC,"The issue couldn't be reproduced with Cengn 0428 build on virtual machines (not bare metal hosts), please see the details in the attachment.
So we need more info for further debugging."
1826912,2019-04-29 19:23:04 UTC,"As a matter of fact, if we try to execute system-apply after failure, it is going to be stucked on 26% showing the following message from sysinv.log"
1826912,2019-05-07 06:30:38 UTC,"this issue is different from ""LP#1827521"" which was stuck in the middle of applying mariadb helm chart. In this issue, the fatal error was:
2019-04-28 11:35:10.791 71 ERROR armada.cli [-] Caught internal exception: armada.exceptions.tiller_exceptions.TillerPodNotRunningException: No Tiller pods found in running state"
1826912,2019-05-07 05:05:42 UTC,we also have a similar bug LP#1827521 that Yong is investigating. Assign to Yong.
1826912,2019-05-01 18:31:41 UTC,Marking as stx.2.0 release gating as the standard configuration is one of the main configurations supported for StarlingX.
1826912,2019-05-15 03:34:47 UTC,"The symptom was not the same.
In this current failure, No Tiller pods were under running at all. As we know, Tiller is the ""daemon"" of Helm and actually does the work of installation of ""application"" helm-charts. So without Tiller pods running, none of helm-charts in packed in stx-openstack wouldn't be installed."
1826915,2019-06-04 19:06:24 UTC,Time stamps are there couldn't reproduce this issue.
1826915,2019-05-28 01:39:07 UTC,"Try the issue again today with last week's build. All the alarm log has correct time-stamp.
Mark the issue as invalid.
Reporter please re-open the issue if it is reproduced again.
Thanks."
1826915,2019-05-08 08:54:51 UTC,"Hi Anujeyan,
I cannot reproduce the issue with 5/5 build. All my logs with 'fm alarm-list' has timestamp, before/after the swact.
It seems there is date time in your ""fm alarm-list"", but miss hour/minute/seconds info. Is it correct?
Another thing is I don't have ""100.114"" alarm in my alarm list. Is it why I cannot reproduce the issue?"
1826915,2019-05-01 18:35:42 UTC,Marking stx.2.0 gating as timestamps on alarms are required/useful.
1826915,2019-05-20 05:33:26 UTC,"Hi Anujeyan,
Could you help check whether the issue still exist or not in your environment?
Thanks."
1826916,2019-05-06 17:59:36 UTC,"@chris.sanders: Since this happended on  2019-04-24 I assume the system still had u-u 0.90ubuntu0.10 installed. In that case it may have hit LP: #1803749.
If this is the case, the latest versions in all releases are fixed now."
1826916,2019-04-30 21:35:07 UTC,"Also, the big questions would be:"
1826916,2019-05-03 20:50:08 UTC,dpk logging from the same time period
1826916,2019-05-03 20:49:46 UTC,requested logging during the month of the error
1826916,2019-05-02 10:25:18 UTC,"@vorlon: Yes, but there is (was) a bug where u-u removes auto removable but not newly auto removable packages when an upgrade step fails and leaves a dirty cache behind: LP: #1824341 .
The fix is scheduled to be released for Xenial next week."
1826916,2019-04-30 21:31:33 UTC,"After having a look at all the provided logs, I see the following:"
1826916,2019-05-03 20:50:45 UTC,@rbalint I've included the logs but I don't see any Traces as mentioned in LP: #1824341
1826916,2019-04-29 23:21:56 UTC,"That's all relevant logs I could think of, when I am able to do a reinstall I'll include the above recommended debug option as well. If there's something I didn't think of let me know and I'll provide that as well."
1826916,2019-04-30 03:35:56 UTC,I've reinstalled with: sudo apt install maas -o debug::pkgproblemresolver=true 2>&1 | tee install.log
1826916,2019-04-29 18:23:58 UTC,"Hi Chris,"
1826916,2019-04-29 21:04:40 UTC,adding '-o debug::pkgproblemresolver=true' to apt commands may help here; e.g. if you try to reinstall maas.
1826916,2019-05-01 16:12:17 UTC,"Balint, can you comment here on the unattended-upgrades autoremoval behavior?  I think the intended behavior is only to remove packages that have newly become unused as part of an upgrade, is that correct?"
1826916,2019-04-29 23:19:59 UTC,attached apt term.log
1826916,2019-04-29 23:20:21 UTC,attached apt history.log
1826916,2019-04-29 23:19:32 UTC,Attached dpkg.log
1826917,2019-04-29 23:25:11 UTC,"This isn't a bug against Launchpad itself (that is, the launchpad.net website)."
1826917,2019-04-30 17:08:20 UTC,"Hello Colin Watson,
Thanks for giving reaction on my question,
Can you tell me the solution of my problem, I am stuck in login loop..
I hope that you again reply me ...
Thanks ..."
1826924,2019-05-02 16:30:37 UTC,Please create a review in Gerrit for this.
1826924,2019-11-21 09:09:27 UTC,Hi Björn. I believe this is fixed in the Rocky release with commit https://opendev.org/openstack/kolla-ansible/commit/a81a5d5d5d0f6f84d17850b50dc35585738853d6.
1826925,2019-08-29 10:13:25 UTC,This issue was fixed in the openstack/tripleo-common pike-eol release.
1826925,2019-06-28 17:24:32 UTC,"Reviewed:  https://review.opendev.org/667502
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=eca1924ec3bde5cad4f6f8545669cc23f14b1997
Submitter: Zuul
Branch:    stable/pike"
1826925,2019-06-26 03:50:22 UTC,"Related fix proposed to branch: stable/pike
Review: https://review.opendev.org/667502"
1826925,2019-06-24 15:26:51 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/667134"
1826925,2019-06-26 00:49:20 UTC,"Reviewed:  https://review.opendev.org/667134
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=19148898aabc58afb7c93957676c6cf408d0f962
Submitter: Zuul
Branch:    stable/queens"
1826925,2019-05-05 18:33:37 UTC,"Reviewed:  https://review.opendev.org/657063
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=f9801ec9bd0be9e24a274127f1d9849cc8aabf00
Submitter: Zuul
Branch:    stable/pike"
1826925,2019-05-03 21:40:57 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/657063"
1826925,2019-04-30 23:52:45 UTC,"Reviewed:  https://review.opendev.org/656379
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=4fe901d2d079a71f0e1bb91aa3dfd0f486cba30c
Submitter: Zuul
Branch:    stable/queens"
1826925,2019-04-29 18:42:19 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/656379"
1826925,2019-06-21 15:24:26 UTC,This issue was fixed in the openstack/tripleo-common 8.7.0 release.
1826932,2019-06-26 19:08:28 UTC,They can't always match because you can make selection and perform operations on the tree when an edited footprint is on the canvas.
1826932,2019-06-26 20:07:30 UTC,"I don't think you understood the situation correctly. You are talking about the footprint editor, I'm talking about the footprint browser, and only under certain circumstances."
1826932,2019-06-26 22:55:11 UTC,Indeed.  It's a whole 'nother ball of wax with the Footprint Browser.
1826932,2019-06-26 23:45:18 UTC,"Fixed in revision 8efe8d18356ba0b24d75ca13c05f45e07b0629bf
https://git.launchpad.net/kicad/patch/?id=8efe8d18356ba0b24d75ca13c05f45e07b0629bf"
1826932,2019-07-01 20:46:34 UTC,Michael set the milestone to 5.1.3 but I don't see this in the 5.1 git commits. And I think I saw this bug today in the latest 5.1 nightly build (from https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/testing/5.1/). I don't have it at hand right now.
1826932,2019-07-01 21:18:54 UTC,Cherry-picked in: ce329e13fb16eff7f206f7b0e1296f0594245041
1826934,2019-05-01 18:43:27 UTC,Marking as stx.2.0 release gating as memory alarms should not occur on any of the configs during normal operations.
1826934,2019-05-30 12:06:09 UTC,"This ""Platform Memory Usage Threshold Alarm"" has not been seen while deploying a Virtual Dedicated Storage 2+2+2:"
1826934,2019-05-31 03:06:28 UTC,"This ""Platform Memory Usage Threshold Alarm"" has not been seen while deploying a Bare Metal Dedicated Storage 2+3+2 with ISO image:"
1826934,2019-05-31 13:05:21 UTC,Marking as no reproducible (invalid) based on Abraham comment.
1826936,2019-06-03 09:14:10 UTC,This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1~19.04.1
1826936,2019-06-03 09:14:08 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1826936,2019-06-03 09:13:38 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1~19.04.1
1826936,2019-06-03 08:47:53 UTC,"OK, it's release to bionic-updates now."
1826936,2019-05-24 11:57:52 UTC,"That yaru upload is in disco-proposed now, so once it's ready to release we can push both out together."
1826936,2019-06-03 08:48:11 UTC,disco-updates*
1826936,2019-05-06 12:35:04 UTC,"Hello Marco, or anyone else affected,"
1826936,2019-05-06 12:18:10 UTC,"Hello Marco, or anyone else affected,"
1826936,2019-05-01 11:34:41 UTC,This bug was fixed in the package mutter - 3.32.1-2ubuntu1
1826936,2019-05-01 11:34:40 UTC,This bug was fixed in the package gnome-shell - 3.32.1-1ubuntu1
1826936,2019-04-30 02:06:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1826936,2019-05-21 14:38:50 UTC,We should hold it until https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829699 is fixed
1826938,2019-04-29 21:53:16 UTC,Addressed by https://github.com/juju/juju/pull/10111
1826939,2019-06-22 18:40:59 UTC,This problem has not occurred on my machine for some time now. So I think this bug can be closed.
1826940,2019-07-16 23:47:34 UTC,"Reviewed:  https://reviews.mahara.org/10165
Committed: https://git.mahara.org/mahara/mahara/commit/9f004185b193559986919cdc1664ee8ebb1f31e3
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.04_STABLE"
1826940,2019-07-16 23:46:47 UTC,"Patch for ""19.04_STABLE"" branch: https://reviews.mahara.org/10165"
1826940,2019-07-16 23:46:15 UTC,"Reviewed:  https://reviews.mahara.org/9907
Committed: https://git.mahara.org/mahara/mahara/commit/31fbdf0b99896508ddab8b5e35821c31f056402b
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1826940,2019-04-29 21:55:55 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9907"
1826940,2019-04-29 23:52:14 UTC,Ok it looks like the problem is based around this:
1826942,2019-09-20 11:55:47 UTC,I believe this is fixed as I can no longer reproduce it on master. Please reopen if you see it again.
1826943,2019-04-30 02:07:32 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed (""internal problem""). To help us find the cause of the crash please follow these steps:"
1826943,2019-06-29 04:17:34 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1826946,2019-04-29 23:55:29 UTC,Bug 1744489 sounds similar but is a different issue.
1826946,2019-05-08 21:05:56 UTC,I opened bug 1828301 to address the fact that asset.bib_source_default() isn't actually immutable.  It's a separate issue but it does complicate testing of the shelving location issue in the present bug.
1826952,2019-04-30 11:38:28 UTC,"Just checked the GERBERs files now and, even generated be the new Nightly, they still consistent with the old one (not present the strange clearance on B.Mask)."
1826952,2019-04-30 00:18:34 UTC,"Other behavior related to this issue is when I set the filled type of the copper zone to: 45deg, 1.016mm x 1.524mm (default),  0 smoothing, 0.1 smooth value."
1826952,2019-04-30 00:14:48 UTC,"If I correctly remember, this changed when was introduced the ""Fill type"" behavior."
1826953,2019-07-25 14:05:10 UTC,This issue was fixed in the openstack/tempest 21.0.0 release.
1826953,2019-05-16 23:08:37 UTC,"Reviewed:  https://review.opendev.org/657144
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=514495b1a0a44f03ddb870c7946bbd2101506e8b
Submitter: Zuul
Branch:    master"
1826953,2019-05-08 15:45:18 UTC,"Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.opendev.org/656532
Reason: https://review.opendev.org/#/c/657144/ is the revert and is approved."
1826953,2019-04-30 14:48:48 UTC,"Looks like this is happening most in the nova-next job which runs tempest.api.compute and scenario tests, slow and non-slow, concurrently, so maybe the concurrency on the scenario tests in that job is what is teasing out the race failure since the tempest-slow job runs the scenario tests serially."
1826953,2019-04-30 22:05:12 UTC,I am not sure if https://review.opendev.org/#/c/570161/ introduced it ? we still use random name for create volume_type
1826953,2019-04-30 15:25:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656532"
1826953,2019-04-30 14:56:18 UTC,"Looks like before change https://review.opendev.org/#/c/570161/ in tempest the volume type being created for the test was always a random name so we wouldn't hit the conflict, but after that change there is a single luks volume type created which means we could hit the 409."
1826953,2019-05-04 17:34:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657144"
1826955,2019-05-01 08:50:37 UTC,"Thanks a lot Jeffrey!
This will be fixed in next release 19.10.
A hug."
1826955,2019-05-01 16:57:47 UTC,"Thank you. I'm glad I could help. Not sure if it would be relevant, but it
might be helpful to also change the ""From:"" and ""To:"" labels to ""Host:"" and
""Client:"" because in English swapping them is valid for either (at least in
my mind): From the Host to the Client or From the Client to the Host? I
usually just go find another rule I've got working and copy it ;) Not a big
deal, but since you'll have the hood open, it might be a quick fix, lol.
Thanks again. All the best!"
1826955,2019-05-01 21:19:40 UTC,"Hi Jeffrey for the idea, but Gufw is an UI for ufw, then I'm keeping the
'keys' of ufw in Gufw.
ufw Is using from and to for everything, then I'll keep them :)
from ADDRESS [port PORT] [to ADDRESS [port PORT]
A hug!"
1826955,2019-05-01 21:29:20 UTC,I see; that makes sense. Thank you for your work on this.
1826957,2019-10-01 10:56:33 UTC,So as far as I could debug the following problems exists:
1826957,2019-10-01 11:24:42 UTC,"I'd prefer if we could update #2 so that both formats are acceptable and detectable. The main issue is that we can't break backward compatibility in a point release from 2.6 to 2.7, but the current lack of support for bi-directional input is a bug that we should address. This leaves us with having to support both formats."
1826957,2019-10-01 13:29:07 UTC,"Bth of these commands are about to change since we have discussions in Paris.
'juju clouds' will have 2 groups - clouds available on the client and clouds available on the controller.
'juju update-cloud' will gain functionality from 'juju update-clouds' making that command obsolete."
1826957,2019-10-01 13:55:36 UTC,"Thanks Anastasia. I was hoping that we'd just tweak the add-cloud command
to take the other yaml format but as you note what the output will
changing. I think the big thing from an end user perspective (noted in
https://discourse.jujucharms.com/t/how-get-controllers-yaml-from-existing-controller/1210/29?u=rick_h)
is that add-cloud (and update as well) should take the output of a yaml
dumped list/show cloud output so that users can easily backup/restore/share
these definitions. I think the credentials commands also fall into this
umbrella. I know it'd be nice to be able to show-credential --show-secrets

> backup.yaml or something and then be able to add-credential backup.yaml


to get it restored on another system, new controller, etc."
1826957,2020-03-12 03:12:36 UTC,"Due to current priorities, I am not currently working on this bug, so I am un-assigning myself from it."
1826958,2019-07-01 04:17:24 UTC,[Expired for pcmanfm-qt (Ubuntu) because there has been no activity for 60 days.]
1826958,2019-05-01 15:34:30 UTC,I've read and re-read your messages many times and I still don't understand. Please write a series of conditions and steps that anyone can reproduce.
1826958,2019-05-01 00:27:41 UTC,"Again, pictures could be helpful."
1826958,2019-05-01 00:09:50 UTC,"Ok, as soon as i can i'll send more info. And i may try to incorporate those info in LAUNCHPAD if it isn't automatic by answering as i'm doing now..."
1826958,2019-05-01 14:28:01 UTC,"Thank You for all!!! I 'm very glad for your suggestions. I've got about pictures, don't worry."
1826958,2019-04-30 17:47:36 UTC,Yeah I'm really unclear on what you mean. Pictures and steps to reproduce would be helpful.
1826963,2019-05-01 18:35:25 UTC,I found this in VarLogDistupgradeMainlog.txt:
1826963,2019-07-01 04:17:26 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1826967,2019-05-13 23:36:06 UTC,"Lee,"
1826967,2019-05-15 15:14:42 UTC,Talked with Lee and he said that he has been unable to reproduce as well.  If he runs across this again we will reopen.
1826967,2019-09-23 00:49:51 UTC,I just upgraded from 2.4 to 2.6.0 (7802-g59416a869-0ubuntu1~18.04.1) and I am seeing this as well.
1826967,2019-09-23 13:31:28 UTC,"The UI determines when the sub-status should be shown, so this need to be fixed in the UI."
1826968,2019-04-30 08:07:37 UTC,"Thank you for your bug report
- wget https://launchpad.net/ubuntu/+source/tzdata/2019a-0ubuntu0.16.04/+build/16645006/+files/tzdata_2019a-0ubuntu0.16.04_all.deb
- dpkg-deb -x tzdata_2019a-0ubuntu0.16.04_all.deb dir
- looking to the file extracted the corresponding line is
'RU	+5502+08255	Asia/Novosibirsk	MSK+04 - Novosibirsk'"
1826968,2019-06-30 04:17:27 UTC,[Expired for tzdata (Ubuntu) because there has been no activity for 60 days.]
1826968,2019-10-12 03:01:42 UTC,Re-installation didn't help.
1826972,2019-05-02 06:48:42 UTC,"Thanks Umesh,"
1826972,2019-04-30 06:21:28 UTC,"Hi,"
1826973,2019-05-03 23:27:40 UTC,"keypair_type is optional. It is not a required field. Thus, the solution should not be to require to select a keypair type."
1826973,2019-04-30 03:10:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656433"
1826988,2019-05-15 11:24:23 UTC,"Thanks Scott,"
1826988,2019-09-21 22:07:05 UTC,This has been an issue for a while now. A lot of the hplip functionality depends on that line of code. The translate function you're using doesn't work in python 3.
1826988,2019-09-21 22:08:45 UTC,"My bad, seems like a patch has been provided. Even better, hoping to see this fixed soon,"
1826988,2020-05-02 07:52:44 UTC,"Just wanted to bump this. This bug makes the package almost unusable, especially for less experimented users who can't patch utils.py manually, which is pretty grave in a stable distribution."
1826990,2019-04-30 07:54:02 UTC,https://github.com/openstack/charm-rabbitmq-server/blob/master/README.md
1826990,2020-11-24 05:20:53 UTC,looks like this bug had been fixed
1826995,2019-04-30 10:17:33 UTC,Thank you for your bug report. Does it give any error or act like it worked but did? Could you add your journalctl log after getting the issue?
1826995,2019-06-30 04:17:31 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1827002,2019-05-01 17:12:26 UTC,"Another opinion: A commercial eCAD tool I use separates PCB items into different types:
 - items from netlist (from schematic)
 - mechanical: this was used for things like barcode label box, UL logo, ESD symbol on silk screen; layer indicator on copper etc.
 - drawing: borders, drill tables, fab notes basically.
All this is displayed in an ""explorer"" with a tree and grid views."
1827002,2019-04-30 07:43:04 UTC,I see this a bit different from the lock feature all together. Right now it is coupled but i think that is generally a bad idea. But you are right that report could be extended to also include discussions about other concepts that are similar to locks. I am however uncertain if it is a good idea to have a single report ballooning to such proportions.(Might be hard to handle.)
1827002,2019-04-30 07:09:55 UTC,This could be part of https://bugs.launchpad.net/kicad/+bug/1745627
1827002,2019-05-01 14:50:11 UTC,"Setting the milestone to 6.0.0-rc1 so this can be included in the ""locked"" discussion [1]."
1827004,2019-04-30 07:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827004,2019-06-30 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827006,2020-02-16 21:52:26 UTC,Redirect to nagios-charm (not package)
1827007,2019-05-21 01:57:48 UTC,"Thanks and sorry for the delay. I've gone ahead and verified that the issue is fixed in 18.04 and newer for this issue as well as retriaged the other open ncurses issues, and committed the updated status in commit https://git.launchpad.net/ubuntu-cve-tracker/commit/?id=34df42f8af0dfe4805fe3309fc252e7c258097cd . These changes should visible from the web version of the tracker within an hour."
1827008,2019-05-29 18:45:15 UTC,"Reviewed:  https://review.opendev.org/655016
Committed: https://git.openstack.org/cgit/openstack/keystoneauth/commit/?id=068213574952ddd35c81b3e7b9c57d76cea21997
Submitter: Zuul
Branch:    master"
1827008,2019-07-15 14:53:24 UTC,This issue was fixed in the openstack/keystoneauth 3.15.0 release.
1827009,2019-05-15 12:56:08 UTC,"Other interesting lines:
2019-05-15 02:21:35 INFO juju.state.presence presence.go:194 watcher loop failed: write tcp 127.0.0.1:38766->127.0.0.1:37017: i/o timeout
...
2019-05-15 02:21:35 INFO juju.state multiwatcher.go:212 store manager loop failed: get unit ""neutron-openvswitch/29"": cannot get unit ""neutron-openvswitch/29"": write tcp 127.0.0.1:39172->127.0.0.1:37017: i/o timeout"
1827009,2019-06-14 01:37:23 UTC,"Since the fixes have been merged into 2.6 and develop, I am marking this report accordingly."
1827009,2019-06-06 08:34:40 UTC,I've landed a fix to 2.6 branch which removes the agent uninstall code entirely. Manual machine agents now simply stop when the machine is removed from juju. We need to add an additional juju command to explicitly clean up the agent and associated files from the manual machine.
1827009,2019-05-15 13:46:34 UTC,"Ah, sorry missed the comment that the logs do not contain a ""Failed to connect"" line."
1827009,2019-05-15 13:44:55 UTC,"Is it possible to get CodeNotProvisioned in ScaryConnect if for some
reason the state of a machine has been corrupted?"
1827009,2019-05-15 13:18:57 UTC,"Now, we did confirm that ""juju remove-machine -m controller 0"" will tell you ""cannot remove machine 0 as it is the only controller machine"""
1827009,2019-05-15 13:01:55 UTC,"If this was the code that triggers when we cannot login, we would expect to see a line like:
func ScaryConnect(a agent.Agent, apiOpen api.OpenFunc) (_ api.Connection, err error) {
 agentConfig := a.CurrentConfig()
 info, ok := agentConfig.APIInfo()
 if !ok {
  return nil, errors.New(""API info not available"")
 }
 oldPassword := agentConfig.OldPassword()"
1827009,2019-05-15 12:34:52 UTC,"The log has these lines at the end:
2019-05-15 02:21:41 INFO juju.worker.httpserver worker.go:168 shutting down HTTP server
2019-05-15 02:22:15 INFO juju.agent uninstall.go:47 agent already marked ready for uninstall
2019-05-15 02:22:15 INFO juju.cmd.jujud machine.go:1224 uninstalling agent"
1827009,2019-04-30 09:44:42 UTC,"I've now come across this in another two units in a separate (Juju 2.5.1 on GCE) environment also, so this isn't AWS specific, nor is it 2.4 specific."
1827009,2019-05-15 10:32:01 UTC,https://github.com/juju/juju/pull/10193 is a PR against 2.5
1827009,2019-04-30 11:34:11 UTC,Can you validate the disk usage of the machines missing agents. There's another bug report going around that mentions that if the disk filled up the agent was removed and I'm wondering if we can get some hint/confirmation of what's going on.
1827009,2019-05-03 02:15:30 UTC,"As far as our logging shows, none of the three units ever had a root partition full enough to cause alerts (threshold for that is 80%)."
1827009,2019-05-05 22:59:02 UTC,"We need to remove the codepath where the agent decides to uninstall itself. This is dangerous, and as shown here and in other similar bugs, the agent can get removed in situations where it is clearly wrong to do so."
1827009,2019-05-15 10:43:51 UTC,^ (machine-0.log supplied to John directly)
1827009,2019-05-15 08:54:30 UTC,"For the record, I saw this for the first time today on a controller unit (2.5.4) rather than within an application in a non-controller model."
1827009,2019-05-15 09:32:18 UTC,"Is it possible to get the tail of the machine log where it decides to uninstall itself (possibly out of band if you don't want to attach it to a public bug), so that we might see why it thought it should be uninstalled?"
1827009,2019-05-15 10:27:58 UTC,"I believe the original change for this was because of
https://bugs.launchpad.net/bugs/1611453"
1827009,2019-05-15 07:54:13 UTC,We've all agreed to stop uninstalling so marking critical and getting it targeted for releases.
1827010,2019-04-30 23:50:02 UTC,"-.mount is the mount unit for the root filesystem mount and it being masked suggests something is fairly wrong with your system. You could try ""systemctl status ?.mount"" (and also show and cat). But I don't think this is a problem with the docker.io package."
1827010,2019-05-10 17:18:59 UTC,I also have same problem on Fedora 30 after upgrade:
1827010,2019-05-11 19:38:42 UTC,"I fixed it by removing the '-.mount' file from the system. Looks like that during the upgrade that link got broken. This potential affect other services, not only docker."
1827010,2019-05-14 01:19:35 UTC,I'm glad you got your system working again. Not a bug in the docker.io package though.
1827011,2019-04-30 14:08:31 UTC,Which OS and Mixxx version do you use?
1827015,2019-09-20 12:04:17 UTC,Is this still effecting you with the latest MAAS and PowerEdge R630 firmware? If so what is the return code from the IPMI command?
1827015,2019-09-20 12:21:46 UTC,"Hi, I believe we can mark this issue as invalid. Eventually, I've found that network had some  latency and some of freeipmi commands were timing out. That explains why failures were random."
1827020,2020-01-24 08:50:00 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1827021,2019-04-30 13:57:37 UTC,"Hi Nils,"
1827021,2019-05-03 08:29:28 UTC,"Hi Dan,"
1827021,2019-05-03 13:36:18 UTC,"On Fri, May 03, 2019 at 08:29:28AM -0000, Nils Meyer wrote:

> I'd be happy to contribute the changes, I assume you need a signed CLA
> for that?
"
1827021,2019-12-12 19:17:09 UTC,https://github.com/canonical/cloud-init/pull/109
1827021,2019-12-12 19:19:19 UTC,"My apologies, I put the wrong merge link. It is actually https://github.com/canonical/cloud-init/pull/110"
1827021,2020-01-14 21:43:21 UTC,"This was merged as is live, so marking fix released."
1827022,2019-05-16 09:15:09 UTC,"The verification of the Stable Release Update for mariadb-10.1 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827022,2019-05-09 13:50:07 UTC,"Hello Dan, or anyone else affected,"
1827022,2019-05-10 13:41:16 UTC,autopkgtest for arm64 on cosmic now passes
1827022,2019-05-16 09:15:03 UTC,This bug was fixed in the package mariadb-10.1 - 1:10.1.38-0ubuntu0.18.10.2
1827028,2019-09-17 08:06:52 UTC,Migrated to https://github.com/widelands/widelands/issues/588
1827029,2019-06-01 02:39:11 UTC,"$ apt-cache policy mutter
mutter:
  Installato: 3.28.4-0ubuntu18.04.1
  Candidato:  3.28.4-0ubuntu18.04.1
  Tabella versione:
 *** 3.28.4-0ubuntu18.04.1 100"
1827029,2019-06-06 09:33:55 UTC,This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.1
1827029,2019-06-06 09:33:58 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827029,2019-05-28 20:47:03 UTC,"Hello Andrea, or anyone else affected,"
1827033,2019-09-15 14:48:40 UTC,Migrated to https://github.com/widelands/widelands/issues/589
1827033,2019-05-27 18:20:55 UTC,"By the way, I just discovered that the destination portdock of a ShippingItem is not set when loading. This may explain the invalid destinations and consequent bugs. I´m fixing this in the attached redesigning branch."
1827033,2019-05-26 12:09:16 UTC,I have now attached the original branch to this bug for easier bookkeeping.
1827033,2019-05-26 12:04:54 UTC,I have triggered the merge. I might look into this for Build 21 or not - we can always rip it out if not.
1827033,2019-05-05 18:18:08 UTC,"I accepted this bug now because I´m also getting it in a savegame now ;) My backtrace is identical to yours, so it seems this happens quite often."
1827033,2019-05-05 16:43:02 UTC,The backtrace of the assert
1827033,2019-05-05 16:39:55 UTC,I got this assert also with bzr9094 when loading the attached savegame and the second ship arrives at the port.
1827033,2019-04-30 11:35:34 UTC,The function in which the assert fail happens was introduced by the new ship scheduling algorithm…
1827033,2019-05-05 17:38:29 UTC,"If you are interested in the odd behavior ships navigating to a port unloading wares and immediately load the same wares again, here is the replay. Increase gametime until you are at 2hrs and 29 minutes, scroll the map to the position where you can see two ports and wait until the ships start bringing wares to the unseen port."
1827038,2019-04-30 12:12:59 UTC,"This is a good idea, I've used this feature in other tools. One feature that isn't quite this but might be easier to implement and help address the same need is to make it fast to toggle between the assigned minimum, nominal, and maximum trace widths while routing."
1827038,2019-04-30 12:43:49 UTC,"That would also help, yes. Zone-like filling would be nice because it would minimize the narrower part length while maximizing its width, without need to think or define how wide exactly it can be."
1827038,2019-05-01 02:29:10 UTC,Isn't the request similar to what other tools call automatic neckdown? (Which i would have expected to be already requested but the limited search functionality of this bugtracker only got me to https://bugs.launchpad.net/kicad/+bug/1799968)
1827038,2019-05-01 03:40:11 UTC,"It is similar but not the same (at least to automatic neckdown in Altium, not sure about other tools).  Automatic neckdown in Altium changes the segment widths when needed, but does not fill like a zone.  Filling like a zone would cause there to be more copper deposited when squeezing between round pads (like in a BGA) than just necking down the segment, although the difference is minor.  I think automatic neckdown is also a useful feature, probably provides 90% the benefit of ""zone traces"", and is easier to implement technically.  It might be good to add that as a separate feature request."
1827038,2019-05-01 08:25:19 UTC,"The use case in my mind was squeezing through a narrow space between pads and continuing the trace after that. As far as I understand, ""neckdown"" means track/pad connection. Zone-like track could take care of both situations. But on the other hand neckdown should typically be applied to an area (several track/pad connections at the same time), not to one segment. If neckdown could somehow be applied to segments passing between pads it would be enough for me."
1827040,2019-05-04 14:09:36 UTC,"Hello, Tyler,"
1827040,2019-05-03 19:48:06 UTC,"Hello Peret - To test the kernel that I built, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages and then reboot. After rebooting, run 'cat /proc/version_signature' and ensure that ""lp1827040.1"" is included in the output. Then try your iptables timestart rules to see if they work as expected."
1827040,2019-05-02 14:03:28 UTC,Hi Peret - Thanks for the bug report. I was browsing through the kernel commit log and I think this bug may already be fixed by the following commit:
1827040,2019-04-30 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827040,2019-05-03 07:09:55 UTC," Hello, Tyler,I am happy to know you have probably found the issue. And I am happy to test it. The problem is that I am not experienced in testing kernels at all.I am an advanced users, but not a programmer.I do not know how to switch (with no high risk) the kernel, test, and switch it back.If you can give me some indications, just to have an idea of the process, I think I will manage; maybe it is as simple as copying it to the place where kernels are copied, and changing the 'pointer' to the active kernel somewhere.Thanks!
    En jueves, 2 de mayo de 2019 16:15:31 CEST, Tyler Hicks <email address hidden> escribió:"
1827041,2020-05-11 12:40:26 UTC,"No, comment #8 shows disco is already fixed. This may be SRU material for Bionic."
1827041,2019-05-22 11:37:07 UTC,"Hi Robie,"
1827041,2019-05-15 16:52:35 UTC,"That's useful, thanks. I think we need to identify the fix, somewhere between 4.7.6 and 4.8.4. This task is in our backlog but I don't think we'll get to it any time soon. If someone can help with this task, please do."
1827041,2019-05-14 11:26:47 UTC,"Hi Andreas,"
1827041,2019-05-09 12:11:36 UTC,"It does, thanks a lot!"
1827041,2019-05-09 10:51:06 UTC,"I can try the cosmic version live as well early next week if it helps, it's 4.8.4."
1827041,2020-05-11 10:42:00 UTC,Is that still an issue in 20.04?
1827041,2019-05-07 16:37:33 UTC,"Hi Andreas,"
1827041,2019-05-07 12:31:18 UTC,"Hi Andreas,"
1827041,2019-05-06 01:11:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827041,2019-05-03 13:46:21 UTC,"Are you able to try with a newer samba version, preferrably the one in disco, which is 4.10? Booting from a disco pendrive and installing smbclient should be enough."
1827041,2019-04-30 13:52:22 UTC,"Small mistake in the previous comment, AIRTOP is the local Linux box."
1827041,2019-04-30 12:27:29 UTC,"This is observed when connecting to shares using the UI also. When gvfs launches the auth dialog, selecting to connect anonymously fails and results in the dialog appearing again. A successful connection can be achieved by typing a dummy username and a dummy password instead."
1827041,2019-04-30 13:43:31 UTC,I can reproduce the issue on 18.04 with smbtree as well:
1827041,2019-05-07 16:57:04 UTC,Good to know. Now to find out what the fix was between 4.7.6 and 4.10...
1827042,2020-11-28 08:56:03 UTC,I had this issue with ThinkPad X1 Extreme 3rd gen with Ubuntu 20.04 and Thunderbolt 3 Dock gen 2. It got resolved when I plugged second power adapter into the laptop directly. I have 135W adapters for both laptop and the dock and thunderbolt cable for connecting them. There is different type of the same dock called Thunderbold 3 Workstation Dock and the difference is in cables and adapter only. It has stronger adapters and the cable for connecting laptop and the dock has additional power wire in it. I contacted Lenovo support in order to replace them.
1827042,2020-01-14 13:46:03 UTC,I appear to be having a very similar issue which started for me in December of 2019.  I am running Ubuntu 19.10 and my system will no longer come out of suspend correctly.  It hangs and kern.log shows the following:
1827042,2020-01-08 17:30:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827042,2019-11-18 19:33:09 UTC,"I had a very similar issue on a Thinkpad T480s with a Lenovo Thunderbolt 3 docking station, 24GB of RAM. I did not test if removing RAM fixes the issue."
1827042,2019-07-19 08:55:26 UTC,"I think, I am seeing a similar or the same bug with the same Ubuntu version. I tried a fresh installation as well. Another commonalty is that my laptop also features 32GB of RAM (cannot test with less RAM unfortunately). The hardware (notebook and dock) will be different though. I am appending the dmesg output which is a bit longer (it begins with the connection of the dock to the thunderbolt port):"
1827042,2020-01-08 07:46:01 UTC,"Similar here, issue with power management.
While dell 7530 with 35gb and 18.04.
Most of the time doesn't boot for powermanagement issue. Most of the time I have to powercycle again, sometimes boots but i2c devices aren't enabled (touchpad), 15% everything works."
1827044,2019-06-18 10:18:11 UTC,This bug was fixed in the package binutils - 2.32.51.20190614-0ubuntu1
1827047,2019-11-08 16:29:32 UTC,"Reviewed:  https://review.opendev.org/662830
Committed: https://git.openstack.org/cgit/openstack/castellan/commit/?id=5d936763380b9d97df409de2d33b3e9b98d61a94
Submitter: Zuul
Branch:    master"
1827047,2019-11-25 16:58:22 UTC,This issue was fixed in the openstack/castellan 1.4.0 release.
1827047,2020-01-13 17:13:28 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/702263"
1827047,2020-01-28 14:13:23 UTC,"Reviewed:  https://review.opendev.org/702263
Committed: https://git.openstack.org/cgit/openstack/castellan/commit/?id=193b4a2cc3c6b65b531b95e6b8b8b7c604ca7b77
Submitter: Zuul
Branch:    stable/train"
1827049,2019-05-01 02:49:43 UTC,If you are using Xorg with fractional scaling then this issue is expected [1]. And I assume you are using Xorg if you have the Nvidia driver installed.
1827049,2019-04-30 14:29:07 UTC,Stock ubuntu 19.04 live usb don't have such issue. But ubuntu budgie 19.04 have.
1827049,2019-06-05 10:09:28 UTC,Experiencing the same issue on an Intel GPU
1827049,2019-04-30 13:44:31 UTC,"I have thinkpad P50 with Quadro M1000M
Stock ubuntu nvidia driver 418.56 was used"
1827049,2019-04-30 13:21:03 UTC,can you please also add your nvidia gpu details and nvidia driver loaded?
1827049,2019-04-30 13:45:28 UTC,"I just checked on live usb. Same issue presented, but cpu consumption was not to high."
1827050,2019-05-01 18:41:00 UTC,"Marking as stx.2.0 gating as StarlingX requires OpenStack containers to work reliably.
Issue was seen only 1 time so far so marking as medium priority.
Assigning to Chris for initial triage."
1827050,2019-06-11 17:42:12 UTC,"The health probe just does an RPC ""ping"" call to the BaseRPCAPI class in the nova code, which should just return a simple response.  This seems to indicate a RabbitMQ issue, although the fact that nova thinks compute-2 is up would indicate that it's successfully issued RabbitMQ calls to update the DB."
1827050,2019-06-19 16:43:25 UTC,Without further logs this bug cannot be investigated.  Marking as invalid.
1827051,2020-05-15 12:31:07 UTC,Branch for OpenSRF is here: https://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/dyrcona/lp1827051-remove-java
1827051,2020-10-06 22:51:04 UTC,"Following up on the developers' IRC meeting today, I have rebased the above two branches on master, and force pushed them."
1827051,2020-10-27 16:44:19 UTC,I pushed a version of the OpenSRF and Evergreen branches rebased on Bill Erickson's remove Python branch on bug 1827055.
1827051,2021-02-10 17:20:45 UTC,"Pushed to master.  Thanks, Jason!"
1827055,2021-02-09 18:48:52 UTC,"I have pushed this to Evergreen and OpenSRF master.  Thanks, Bill and Jason!"
1827055,2020-10-27 21:07:17 UTC,"Bill, the branches work for me, I have rebased the branches to remove Java and the Ubuntu 20.04 support branches on top of these so that they should apply smoothly."
1827055,2019-05-07 20:12:22 UTC,Noting per today's dev meeting that Dan Wells is evaluating whether to assume maintainership of the Python binding and Syrup.
1827055,2020-10-26 15:19:42 UTC,My proposal for moving the Python bits to a separate repo:
1827055,2020-04-09 15:01:14 UTC,"Quick update, just to keep this bug alive.  We have a branch of Syrup functional on Python 3.  It is currently entangled with all of our local customizations, and I can't provide at this point a solid ETA on getting that untangled, but mid-May would be a reasonable guess.  (Many of those customizations probably deserve consideration for inclusion in mainline Syrup as well.)  It should be noted that Syrup does not actually run Python OSRF services, so this does not mean that the full OpenSRF Python libraries (I don't like to call them bindings) are ready for Python 3.  In fact, I do not recall OTTOMH whether getting Syrup to work required any changes to the Evergreen Python code at all.  It certainly was not the majority of it."
1827055,2020-10-26 19:46:09 UTC,Extraction branches in progress:
1827057,2019-05-16 09:48:15 UTC,"Nice work, sorry for not participating with requested additional information."
1827057,2019-05-16 01:55:41 UTC,Fixed in trunk version 2019.05-204-development
1827057,2019-05-13 23:23:40 UTC,"Clarification: The bug happened When clicking ""Next"" on the ""Terminal"" page, not on the ""Existing Project"" page."
1827057,2019-05-03 01:49:11 UTC,"For reference, here is the portion of the log showing the button click events..."
1827057,2019-05-03 01:52:19 UTC,For reference here is the relevant portion of the log where the crash occurred.
1827057,2019-05-03 01:48:39 UTC,"The ""Expected"" outcome you described above is how Cubic should behave."
1827057,2019-05-01 00:19:17 UTC,"Anders, thanks for reporting this bug.
I'll investigate the log you have attached."
1827057,2019-05-13 23:21:47 UTC,Experienced this bug under Ubuntu 19.04.
1827061,2019-04-30 15:00:30 UTC,https://review.opendev.org/#/c/656526/
1827061,2019-05-07 09:55:31 UTC,"Reviewed:  https://review.opendev.org/656526
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=2e3808dd9bc523b626076d9a1c615ce91fc49622
Submitter: Zuul
Branch:    master"
1827063,2019-11-29 18:24:46 UTC,"Issue was not reproduced on train
2019-11-21_20-00-00
wcp_3-6"
1827063,2019-11-27 02:33:30 UTC,Set to invalid first since we could not reproduce it in latest build.
1827063,2019-11-27 02:29:45 UTC,"Not reproducible in 20191119T000000Z with train release.
Waiting for reporter's confirm！"
1827063,2019-11-25 13:02:11 UTC,"Maria:
   would you like to verify it on latest master build ?"
1827063,2019-08-23 17:53:10 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1827063,2019-11-22 02:17:24 UTC,"For recent update - Openstack Train version integration, we have setup an AIO-DX environment with load 20191119T000000Z.
Steps are as #13. We create a volume of 50GB with cirros-0.4.0-x86_64-disk.img. This bug is not reproduced in our testing."
1827063,2019-10-28 01:43:03 UTC,"Hi all,"
1827063,2019-09-18 08:20:15 UTC,We cannot reproduce this in an AIO-DX environment with load 20190902T230000Z. Steps are as #13. We create a volume of 50GB with cirros-0.4.0-x86_64-disk.img. And volume was created successfully.
1827063,2019-08-08 19:59:06 UTC,"Above issue happened in sanity. After sanity completes, there are a number cinder volumes stuck at creating status while one in in-use.
The volume that was in in-use status was the first one that having issue. Basically the vm uses it already deleted, but it was stuck at in-use. Ever since then, all volumes creation were stuck."
1827063,2019-07-10 08:27:07 UTC,"log show the latest create volume request is sent at: 17:36:24 from controller-0, it want to create a volume with 2GB from image 'b545cf51-0e6f-4422-b1a8-7e774c054801'. This request was served by controller-0, and the volume is successfully created."
1827063,2019-07-25 17:36:01 UTC,We have not observed this issue recently. Will provide more information if it is reproduced again.
1827063,2019-05-01 17:59:03 UTC,"Marking as stx.2.0 gating as creating volumes is fundamental to using StarlingX with VMs. Issue is intermittent so setting priority to medium.
This may be a duplicate of https://bugs.launchpad.net/starlingx/+bug/1827230"
1827063,2019-05-08 02:31:23 UTC,"Agreed, it should be the same issue as bug 1827230."
1827063,2019-05-27 13:11:30 UTC,We did not see this issue in recent loads
1827063,2019-08-08 19:32:04 UTC,This issue is reproducible using load 20190807T053000Z in a storage system. The collect all logs are attached.
1827063,2019-07-10 09:25:53 UTC,We found DB connection was lost at 15:56:56. Do you still have some record that shows at which time you send create volume request?
1827063,2019-07-10 21:56:36 UTC,Not sure why this bug has an stx.networking tag on it. This seems to be a storage issue. Internal connection to the DB is not part of the networking domain.
1827063,2019-07-12 15:49:36 UTC,"@peng, if volume number exceeded quota, e.g. 8, the volume status will be error. If reproduced, please take a look of quota, thanks."
1827063,2019-07-03 18:36:44 UTC,"Issue was reproduced on
Lab: WCP_113_121
Load: 20190703T013000Z"
1827065,2019-04-30 15:45:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656534"
1827065,2020-03-16 00:16:02 UTC,"In this case, tests resource might cross the allowed quote on tested cloud. Quota set on your env either it is default or override is what you want to restrict due to HW resource etc. I am not sure how it will help to customize quota on tempest side ?"
1827068,2019-09-03 15:19:35 UTC,This is done! (On --edge for now.)
1827072,2019-06-04 15:47:36 UTC,With the samba config that Michael posted I was able to install Eoan (subiqity install) on Power9 server (tiselius).
1827072,2019-05-21 15:04:10 UTC,"Next step would be to try to reflash the BMC and wipe the configuration settings. However, this may also wipe any BMC IP addresses, so hands-on will be required while doing this."
1827072,2019-05-20 20:35:44 UTC,"After the BMC firmware upgrade, I cannot DI install system even with the modifications to smb.conf. It consistently fails in ""Select and install software""."
1827072,2019-05-13 13:54:43 UTC,"I will repeat this test with the latest BMC fw I have recently flashed, and will  try the suggested smb settings. The system is currently being used to debug a different issue, so I will post this test information as soon I have a free system."
1827072,2019-05-10 08:04:53 UTC,"Your samba configs appear to differ with regards to ""mangled names"" (and maybe also ""mangle prefix"").  Could that also be playing a role here?"
1827072,2019-05-06 22:32:39 UTC,I tried this again quick after the fw update to 2.06 (PNOR 2.12) and it worked fine for me again.
1827072,2019-05-01 17:27:41 UTC,"I did not set the code page.  According to testparm my default is CP850 - I can try setting that directly, too.  I assume if you set it to CP850 you see the problem?  Ie, are we using the same defaults?  Mine show as:"
1827072,2019-04-30 20:55:01 UTC,Just to clarify.
1827072,2019-04-30 19:18:37 UTC,"Hi Manoj - I tried this on our Boston and it worked.  I have newer firmware, I was using a witherspoon with 18.04 as the samba server and using the file ubuntu-19.04-server-ppc64el.iso."
1827072,2019-04-30 17:15:05 UTC,"Looks like this is an issue with the way the samba server (linux) serves the BMC (like windows??), and the issue has to do with the dos code pages used. I used the code page ""437 - Original IBM PC hardware code page"" (https://en.wikipedia.org/wiki/Code_page_437) in my smb.conf and no longer see the failure during install. The working samba config is as follows:"
1827072,2019-04-30 16:05:47 UTC,"Michael,"
1827072,2019-05-06 13:49:05 UTC,Waiting on BMC firmware fix from IBM.
1827072,2019-04-30 18:14:45 UTC,"note: Samba defaults to code page 850, https://www.oreilly.com/library/view/using-samba/1565924495/ch08s03.html"
1827073,2019-05-01 03:18:38 UTC,The attached build log appears to be truncated and incomplete. Do you have any other build logs?
1827073,2019-06-30 04:17:48 UTC,[Expired for nvidia-graphics-drivers-384 (Ubuntu) because there has been no activity for 60 days.]
1827074,2019-05-30 13:55:02 UTC,Verified in load 2019-05-28_17-05-57
1827074,2019-05-22 20:20:56 UTC,Duplicate bug was merged on May 22. Review: https://review.opendev.org/660424
1827074,2019-05-01 17:51:09 UTC,"Marking stx.2.0 gating as alarms should not exist after an uncontrolled swact.
This issue is likely a duplicate of https://bugs.launchpad.net/starlingx/+bug/1826418 but assigning to Bin to confirm."
1827075,2020-03-09 11:28:57 UTC,"Hi,"
1827079,2019-06-13 23:33:47 UTC,"Indeed, starlingx picked up the change in the cengn build on 2019-06-13"
1827079,2019-06-13 23:11:46 UTC,This patch has been merged to stein branch.
1827079,2019-06-04 14:49:34 UTC,"cherry pick to stein in progress now, review:
https://review.opendev.org/#/c/662782/"
1827079,2019-06-03 14:22:52 UTC,The above review (https://review.opendev.org/#/c/648157/) was merged in openstack master. Is there a plan to merge it in the stein branch? Otherwise starlingx will not pick up the fix.
1827079,2019-06-03 14:22:31 UTC,The above review (https://review.opendev.org/#/c/648157/) was merged in openstack. Is there a plan to merge it in the stein branch? Otherwise starlingx will not pick up the fix.
1827079,2019-06-14 15:15:53 UTC,"verified in BUILD_ID=""20190613T013000Z"""
1827079,2019-05-17 08:48:40 UTC,code in review: https://review.opendev.org/#/c/659749/
1827079,2019-05-16 15:47:41 UTC,Reproduced.
1827079,2019-05-09 13:40:01 UTC,"It was hardware system with 2 controllers, 1 (or more) worker nodes."
1827079,2019-05-09 09:31:07 UTC,@Wendy What's the meaning of configuration 2+3? bare metal or virtualization? It looks like a real bug in cinder or glance and I want to reproduce in my side. Can it be reproduced in an AIO-Simplex virtualization environment? Thanks
1827079,2019-05-01 17:46:08 UTC,Marking stx.2.0 release gating as it is believed this functionality should be working.
1827079,2019-05-22 16:11:21 UTC,"this is fixed by another patch at the same time:
https://review.opendev.org/#/c/648157/
This patch is merged today."
1827080,2019-08-22 20:15:03 UTC,"Bug re-opened as recommended by John Kung.
@Tingjie, Please do NOT cherry-pick to the r/stx.2.0 branch. Since this is a medium priority bug, it will be moved to stx.3.0 on 2019-08-23. So the subsequent fix is only required in master."
1827080,2019-10-30 18:22:43 UTC,Verified in Build 2019-10-29_20-00-00
1827080,2019-08-23 11:39:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/678203"
1827080,2019-08-23 11:50:46 UTC,"I have raised another patch with one solution: remove the reservation for ceph-mon-lv on worker nodes. https://review.opendev.org/#/c/678203/ and also recover the check_node_ceph_mon_growth() with previous one with no special condition.
I have verified it and it is in line with expectations, please help review it and give comments "
1827080,2019-08-23 17:53:33 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1827080,2019-09-25 13:14:57 UTC,"@Tingjie to make a draft of solution (or patch) and quickly sync-up with Ovidiu.
This LP is important, so pls take it with priority."
1827080,2019-08-22 18:54:31 UTC,"@Tinjie,  Please note that I posted some concerns with https://review.opendev.org/#/c/677196/2/sysinv/sysinv/sysinv/sysinv/api/controllers/v1/utils.py ; in addition to the comment, the method signature is no longer correct as it never references the 'host' parameter passed in."
1827080,2019-09-27 06:00:33 UTC,"Change abandoned by Tingjie Chen (<email address hidden>) on branch: master
Review: https://review.opendev.org/678203
Reason: Abandon it since there is new solution patch."
1827080,2019-09-29 03:27:31 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/685576"
1827080,2019-10-11 16:12:46 UTC,"Reviewed:  https://review.opendev.org/685576
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=e6c862c99ab74ee40d9d8ae14681bf78b864aaa3
Submitter: Zuul
Branch:    master"
1827080,2019-09-25 12:32:51 UTC,"Since Reserving space for ceph-mon on all worker nodes was a product requirement from Brent, so I have to find another solution to check_node_ceph_mon_growth with consideration of cgts--vg-ceph--mon--lv reservation.
working on resolve patch ..."
1827080,2019-08-22 17:22:23 UTC,"@Tingjie, please cherrypick the fix to r/stx.2.0 before 2019-08-23"
1827080,2019-08-23 05:40:21 UTC,"1. About ceph_mon_gib, since the data of have to sync between 3 ceph monitors, and when we set ceph-mon-modify in sysinv (although command is on controller-0), we have to check some pre-requirements for all ceph monitors and modify all the configurations."
1827080,2019-08-19 13:12:05 UTC,"Before the fixing patch when ceph-mon-add:
-------------------------------------
2019-08-19 02:44:47.234 110684 INFO sysinv.api.controllers.v1.utils [-] check_node_ceph_mon_growth hostname: controller, ceph_mon_gib: 21, cgtsvg_growth_gib: 0, cgtsvg_max_free_gib: 167
2019-08-19 02:44:47.246 110684 INFO sysinv.api.controllers.v1.utils [-] get_node_cgtsvg_limit cgtsvg_max_free_gib=1
2019-08-19 02:44:47.251 110684 INFO sysinv.api.controllers.v1.utils [-] check_node_ceph_mon_growth hostname: compute-1, ceph_mon_gib: 21, cgtsvg_growth_gib: 21, cgtsvg_max_free_gib: 1
2019-08-19 02:44:47.251 110684 WARNING wsme.api [-] Client-side error: Node: compute-1 Total target growth size 21 GiB for database (doubled for upgrades), glance, scratch, backup, extension and ceph-mon exceeds growth limit of 1 GiB."
1827080,2019-08-22 16:48:39 UTC,"Reviewed:  https://review.opendev.org/677196
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=f1cd5557433bc45235256a4fe1620773bf3973ec
Submitter: Zuul
Branch:    master"
1827080,2019-05-01 17:41:01 UTC,Marking stx.2.0 gating as ceph functionality is required for all StarlingX configurations.
1827080,2019-05-07 05:09:57 UTC,"Maria, can you please retest it with the latest code base due to we've upgraded Ceph to mimic and the functionality is not exactly the same."
1827080,2019-05-08 14:53:21 UTC,This is still an issue.
1827080,2019-05-09 07:54:05 UTC,"Problem is that when a node is deleted we only remove the monitor from the DB, it should also be removed from Ceph. Search for ceph_mon_destroy() in sysinv's code. One of the functions from conductor/manager.py is:"
1827080,2019-05-14 15:11:03 UTC,"Thanks Ovidiu for your precise comments, the command with delete host (compute-0) include _remove_ceph_mon() but not really remove ceph mon, need to call CephWrapper which inherit CephClient.mon_remove() which execute command: ceph mon remove {hostname}."
1827080,2019-06-20 20:28:11 UTC,"Reviewed:  https://review.opendev.org/659094
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=70a249595184c3b40f3bebcd780c0e7b327a96be
Submitter: Zuul
Branch:    master"
1827080,2019-08-19 12:51:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677196"
1827080,2019-08-19 12:39:33 UTC,"This issue is side effect for patch: https://review.opendev.org/661900 for LP: 1827119, sorry for that."
1827080,2019-05-17 12:21:58 UTC,I have verified the gerrit patch: https://review.opendev.org/#/c/659094
1827080,2019-08-13 19:41:23 UTC,Reopening this issue as I have tried this on  more than one 2+2 system .. I am getting blocked from completing the operation.
1827080,2019-08-13 19:42:45 UTC,"Tried the following loads without success
2019-08-09_20-59-00
2019-08-12_20-59-00"
1827082,2019-09-06 21:50:52 UTC,I can't reproduce this using Ubuntu MATE 19.10 with Brisk Menu 0.6.0.
1827082,2019-09-06 21:51:15 UTC,Ugh. Wrong bug. Sorry.
1827082,2020-10-02 04:17:37 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1827083,2019-04-30 15:59:22 UTC,Looks like this started around 4/24.
1827083,2019-05-02 02:21:03 UTC,"From talking with clarkb and mnaser at the summit today, it sounds like there was something with some images that infra started publishing and glance, but I don't know the details."
1827083,2019-05-14 19:00:36 UTC,Patch to force ipv4 on vexxhost-sjc1 nodes to rule out ipv6 as a problem:
1827083,2019-05-15 18:12:46 UTC,Tracking this now: https://review.opendev.org/#/c/659181/
1827083,2019-08-19 19:59:12 UTC,This is no longer showing up in e-r so considering this fixed.
1827087,2019-05-29 22:09:18 UTC,Ditto on Centos 6.10 Final
1827087,2019-05-29 22:47:54 UTC,Used this release of bzr from openfusion and it seems to work: https://centos.pkgs.org/6/openfusion-x86_64/bzr-2.3.0-1.of.el6.x86_64.rpm.html
1827087,2019-10-13 19:40:05 UTC,This is also fixed in Breezy.
1827090,2019-06-20 22:30:25 UTC,"The verification of the Stable Release Update for tomcat8 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827090,2019-06-20 22:30:15 UTC,This bug was fixed in the package tomcat8 - 8.5.39-1ubuntu1~18.04.2
1827090,2019-06-14 10:52:21 UTC,"I can confirm that this is fixed with the package tomcat8-user 8.5.39-1ubuntu1~18.04.2 installed from the bionic-proposed repository.
Thanks a lot
ubbo"
1827090,2019-06-13 17:09:04 UTC,"Hello Stefan, or anyone else affected,"
1827091,2019-05-06 05:18:43 UTC,fixed by https://review.opendev.org/#/c/656542/
1827091,2019-06-07 19:28:42 UTC,This issue was fixed in the openstack/puppet-tripleo 11.0.0 release.
1827091,2019-12-12 10:13:09 UTC,This issue was fixed in the openstack/puppet-tripleo 10.5.2 release.
1827092,2020-06-21 13:06:19 UTC,Any news or details on this bug report? Does this still apply?
1827092,2020-08-21 04:17:13 UTC,[Expired for Mixxx because there has been no activity for 60 days.]
1827094,2019-04-30 17:17:19 UTC,Patch is here: https://review.opendev.org/#/c/656549
1827094,2019-05-01 03:57:45 UTC,"Reviewed:  https://review.opendev.org/656549
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=674c004231a3f7696962d7a7bfa69b4b31af4de8
Submitter: Zuul
Branch:    master"
1827094,2019-05-01 12:50:33 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/656632"
1827094,2019-05-03 20:43:42 UTC,"Reviewed:  https://review.opendev.org/656632
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b123b05a4866d4ad0868fba33964982f686ac57f
Submitter: Zuul
Branch:    stable/stein"
1827094,2019-06-06 06:24:20 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1827094,2019-09-27 09:04:09 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1827095,2019-05-07 01:33:20 UTC,https://github.com/snapcore/snapcraft/pull/2551
1827096,2019-04-30 21:01:12 UTC,EG 3.2.4
1827098,2019-06-08 00:50:39 UTC,"There is one caveat. Currently, when selecting a group of items, the system cursor position is used. If the KiCad cursor is used (which snaps to grid), it may be difficult to select a group of items. So additionally, I would also request to be able to toggle off grid snapping for the cursor."
1827098,2019-04-30 18:40:16 UTC,"If someone gets around to implementing this, please make it optional.  If not, there will be another bug report for the current use case."
1827099,2019-05-30 12:03:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827099,2019-05-30 12:04:55 UTC,ditto upgrading in two steps bionic->cosmic->disco
1827100,2019-06-20 14:53:22 UTC,This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-0ubuntu5
1827100,2019-11-21 12:32:54 UTC,"Hello Seth, or anyone else affected,"
1827100,2019-11-29 02:33:07 UTC,Tested bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5~18.04.1. The issue is resolved for me.
1827100,2019-12-05 12:51:58 UTC,This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-0ubuntu5~18.04.1
1827100,2019-12-05 12:52:02 UTC,"The verification of the Stable Release Update for bcmwl has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827106,2019-05-22 14:42:40 UTC,This has been fixed upstream in https://github.com/aabc/ipt-netflow/commit/fd37b58a81c3df1f375fe784547b77b7a9d1ebc4.
1827108,2019-04-30 19:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827108,2019-06-30 04:17:43 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827110,2019-04-30 22:33:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827110,2019-05-05 14:27:51 UTC,I confirm that NVIDIA driver 340.107 fails to build or work with Linux Kernel 5.1.0.
1827112,2019-05-14 11:36:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827118,2019-06-30 04:17:47 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1827118,2019-05-01 03:12:51 UTC,I can't see any problem in the files attached so far. We need a log file covering the period of time when the problem actually happened. To get that please:
1827119,2019-08-08 21:20:04 UTC,"20190807T053000Z
2 controller +2 worker node system"
1827119,2019-10-11 17:56:24 UTC,"# RETEST STATUS
PASSED"
1827119,2019-10-02 18:05:21 UTC,"Marking as Fix Released based on Ovidiu's recommendation.
If an issue is encountered during retest, this bug can be re-opened or a new open can be created."
1827119,2019-09-25 13:36:54 UTC,"The 'configuring' state should clear itself on lock/unlock even if there are issues with ceph-mon during initial configuration. Therefore, I also recommend a retest for 2/"
1827119,2019-09-25 13:12:09 UTC,"https://review.opendev.org/#/c/677424/ was merged, but @Tingjie to further check with @Wendy about another aspect."
1827119,2019-09-25 12:09:34 UTC,"@Ghada, In my opinion, there are 2 points raised by Maria,
1/ The alarm list for compute-0 missing, this issue is confirmed, and I will raise another patch to fix.
2/ compute-0 status in configuring, this still cannot reproduce."
1827119,2019-09-24 16:03:51 UTC,"@Tingjie, The commit above has ""Partial-bug"" instead of ""Closes-Bug"". Are you expecting to make additional code changes for this bug? Is this only a partial fix?"
1827119,2019-09-23 15:54:50 UTC,"Reviewed:  https://review.opendev.org/677424
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=abebb638603cb3297ae133d4e388d034d7d3eff8
Submitter: Zuul
Branch:    master"
1827119,2019-08-23 17:54:32 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1827119,2019-08-20 07:59:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677424"
1827119,2019-08-19 12:32:12 UTC,"I have tried 2 times for the 2 points,
1/ The alarm list for compute-0 missing, this issue is confirmed, and I will raise another patch to fix.
2/ compute-0 status in configuring, this still cannot reproduce."
1827119,2019-08-19 02:38:17 UTC,"Hi Wendy, I suppose your key point are:"
1827119,2019-08-13 12:33:32 UTC,This LP should be reopened.
1827119,2019-07-31 18:34:52 UTC,"Reviewed:  https://review.opendev.org/661900
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=39cb9d0c0b66a4f4920cd26ecd27bdf196d9b260
Submitter: Zuul
Branch:    master"
1827119,2019-06-24 08:49:26 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/667044"
1827119,2019-05-01 17:33:05 UTC,Marking stx.2.0 gating as ceph functionality is required for all StarlingX configurations.
1827119,2019-06-27 12:36:02 UTC,"Change abandoned by Tingjie Chen (<email address hidden>) on branch: master
Review: https://review.opendev.org/667044
Reason: Abandon it since it is debug only"
1827119,2019-05-08 15:38:38 UTC,This is still a problem:
1827119,2019-05-09 09:37:17 UTC,"We have two approaches here, depending on the path we want to take:"
1827119,2019-05-14 12:53:58 UTC,"Thanks Ovidiu for your suggestions,"
1827119,2019-05-15 10:23:34 UTC,Re #1. We got 3 answers on the ceph mailing list:
1827119,2019-05-15 10:44:41 UTC,"So, indeed Tingjie, #2B is too much. #1 is not a good idea (see prev comment). #2A is the way to go coupled with setting ""mon data avail warn"" to 10 (i.e. alarm will be raised when ceph mon disk usage reaches 90%) in $MY_REPO/stx/stx-integ/ceph/ceph/files/ceph.conf."
1827119,2019-05-07 05:16:27 UTC,"Maria, can you retest using the latest ISO (after 5/3 Ceph upgrade)?"
1827119,2019-05-23 07:58:51 UTC,"Change abandoned by Tingjie Chen (<email address hidden>) on branch: master
Review: https://review.opendev.org/660889
Reason: Abandon it since MON data need to sync on 3 MONs, change controllers without worker/storage does not make sense."
1827119,2019-05-23 11:32:28 UTC,Some update for the issue...
1827119,2019-05-29 07:00:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661900"
1827119,2019-05-30 01:18:24 UTC,"I have submit gerrit patch: https://review.opendev.org/661900, which following the #2A solution.
The way we resolve the issue is extend the check mechanism to controllers
and worker/storage nodes, if one node check cgtsvg limit failed, the
command will return error message and no action is implemented."
1827119,2019-06-17 19:25:02 UTC,"Something to note is that ceph-mon is also configurable from Horizon under ""Admin/Platform/System Configuration/Controller Filesystem"""
1827119,2019-05-23 06:21:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660889"
1827120,2019-07-30 15:38:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827120,2020-02-11 13:57:43 UTC,"in /openstack/venvs/keystone-18.1.5/lib/python2.7/site-packages/keystone/token/token_formatters.py on line 290 there is the named parameter ""hex"" missing for uuid.UUID()"
1827121,2019-06-03 12:26:54 UTC,"So it was related to old cirros image, now we have updated cirros image to 0.4.0 in tempestconf and here is the tests results from CI.
http://logs.openstack.org/16/662716/2/check/tripleo-ci-centos-7-standalone/4ed6ad1/logs/stestr_results.html -> test_server_basic_ops[compute,id-7fff3fb3-91d8-4fd0-bd7d-0204f1f180ba,network,smoke] -> passed"
1827121,2019-05-20 12:55:51 UTC,can we please check if this is still valid bug?
1827122,2019-05-17 09:31:50 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1827122,2019-05-20 15:46:49 UTC,"Verified on 5.0.0-16, it works as expected, thank you Christian!"
1827122,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1827124,2019-07-05 16:06:40 UTC,I don't get it.  How could that be platform-specific?
1827124,2019-07-05 14:26:28 UTC,"Nice catch jp! I missed your Launchpad post, thanks for fixing"
1827124,2019-07-05 13:24:32 UTC,"Well, rats.  Opening the top-level project works fine, but the bug doesn't reproduce."
1827124,2019-07-05 13:52:23 UTC,This is a bug in a plot function. I fixed it.
1827124,2019-07-05 13:09:45 UTC,"I probably should have explained better, sorry!  There's only one cache file (module.cache.lib), so you have to open the top-level drawing (module.sch) and navigate to the individual sheets from there.  If you open the p1of2 and p2of2 sheets directly rather than indirectly through module.lib, they'll have no cache files and won't be able to find the original libraries either."
1827124,2019-07-05 13:56:33 UTC,"Fixed in revision b74bccbb13230dfc5e69329c8c59d92bc9b6099e
https://git.launchpad.net/kicad/patch/?id=b74bccbb13230dfc5e69329c8c59d92bc9b6099e"
1827124,2019-06-26 21:17:14 UTC,"Well, that's definitely a curiosity, Jeff, since that's not what I see in the repo.  Nevertheless, here's a zipfile of precisely the folder on my local computer that I used this afternoon to perform the test:  https://drive.google.com/open?id=1bwzyHz5aIeojOAGWcx4pj35w82VnBmgc"
1827124,2019-07-05 12:07:07 UTC,"When I open p1of2 I don't get a rescue dialog, and since the zip doesn't include the libraries I just get a bunch of squares with ""??"" in them."
1827124,2019-06-26 19:04:43 UTC,"@Ron, are you still seeing this?"
1827124,2019-06-26 19:44:56 UTC,"Unfortunately, yes."
1827124,2019-07-05 13:27:15 UTC,"@Devs, could someone on GTK test this:"
1827124,2019-06-26 20:25:00 UTC,"@Ron, when I fetched the module_cache.lib file from your GIT repo the schematic I got with it was empty.  Did I fluff it up, or is the schematic in your screen-shots different?"
1827124,2019-06-26 19:51:11 UTC,"I hadn't really thought of it before, but my Linux desktop directly displays Postscript, and the numbers are missing when I view the Postscript directly as well.  I've uploaded the Postscript to Google Drive (https://drive.google.com/open?id=1tUznqVwxbHedad7eUqJmZg1wkAXO8FDQ) but the numbers are even missing in the Google Drive viewer."
1827133,2019-05-04 18:22:07 UTC,"Confirmed in 3.2.5.  Once the holds screen is refreshed either sorting or selecting another row limit, the holds display normally.  After you reproduce this bug initially, an easy way to reproduce it a second time is to log in as a different staff member and go through John's steps above."
1827135,2019-05-01 10:26:29 UTC,Setting importance as 'Low' because CvPcb's different filter behaviour could appear as a bug to users expecting the search behaviour used elsewhere.
1827135,2019-08-21 14:36:16 UTC,"Fixed in revision bfb8806682d4fc73d8738adac080b69ecd198f04
https://git.launchpad.net/kicad/patch/?id=bfb8806682d4fc73d8738adac080b69ecd198f04"
1827138,2019-05-05 17:52:14 UTC,"Hi,"
1827139,2020-05-21 10:26:59 UTC,"Migrated to new issue tracker, please follow the issue there for updates:
https://github.com/Xubuntu/xubuntu-website/issues/3"
1827140,2019-05-01 00:23:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1827140,2019-05-08 17:00:37 UTC,This seems to be just the first instance of such installer crashes.
1827144,2019-05-09 02:00:50 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827146,2019-05-24 23:09:00 UTC,"Reviewed:  https://review.opendev.org/657735
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=20161582ea8bb37b5652aed88ac5001461d601c1
Submitter: Zuul
Branch:    stable/stein"
1827146,2019-05-10 10:58:55 UTC,"Reviewed:  https://review.opendev.org/657736
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=23045496219b31a06280b64dd68e43c58400c0ba
Submitter: Zuul
Branch:    stable/rocky"
1827146,2019-05-08 05:39:55 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/657736"
1827146,2019-05-08 05:38:21 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/657735"
1827146,2019-04-30 22:51:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656603"
1827146,2019-05-07 19:28:51 UTC,"Reviewed:  https://review.opendev.org/656605
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=da24177fd03e79ab0936aa3f63bd38ae55cc63c3
Submitter: Zuul
Branch:    master"
1827146,2019-04-30 23:19:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656605"
1827150,2019-06-03 17:30:46 UTC,When pulling up a patron's group members the screen has to be refreshed for the group members to display. When it first opens it says no information to display or something to that effect. When you refresh the screen the group members display as they should.
1827150,2019-06-03 17:33:41 UTC,We are on EG 3.2.4 not 3.2.1
1827154,2019-04-30 23:44:43 UTC,https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503
1827155,2019-05-01 00:10:47 UTC,"Hi Chris,"
1827155,2019-05-01 01:27:09 UTC,2.5.2 (7523-ge4ecbd54d-0ubuntu1~18.04.1)
1827156,2019-09-17 04:17:37 UTC,[Expired for cloud-init because there has been no activity for 60 days.]
1827156,2019-07-18 21:14:01 UTC,"Hello,"
1827157,2019-05-17 00:13:25 UTC,"Just updated and tried to update my existing project. When I click Next out of Chroot, cubic hung forever. Quit and then ran again from Terminal to see if anything was logged and ran into the same hang. Here is the relevant output:"
1827157,2019-05-17 15:42:08 UTC,"Pico,"
1827157,2019-05-16 01:55:13 UTC,Fixed in trunk version 2019.05-204-development
1827157,2019-05-01 00:37:20 UTC,"The kernel version prior to the upgrade was 4.18.0-15.
The upgrade installed kernel version 4.18.0-18."
1827157,2019-05-01 01:34:04 UTC,Here is a work-around until this bug is fixed:
1827157,2019-05-01 00:53:08 UTC,Note that the kernel version used in the original 18.04.1 ISO (ubuntu-18.04.1-desktop-amd64.iso) is:
1827157,2019-05-15 22:10:26 UTC,Added initramfs-tools as a dependency to support querying initrd for version information.
1827157,2019-05-01 01:22:29 UTC,"The package ""linux-image-4.18.0-15-generic"" contains the missing file ""/boot/vmlinuz-4.18.0-15-generic""."
1827159,2019-06-17 09:30:31 UTC,This has been fixed in nagios-32 by deploying a custom check_all_disks_no_squashfs check
1827159,2019-06-19 17:52:43 UTC,"This can be overridden in /etc/nagios-plugins/config/disk.cfg, right? By adding the parameter you suggested."
1827159,2019-06-26 19:30:43 UTC,Was able to reproduce using the command in /etc/nagios-plugins/config/disk.cfg; I've added this as a test case in the report body.
1827159,2019-07-16 14:34:34 UTC,"Currently experiencing this issue at customer site where there is a permission issue as nagios user can't access this directory, this particular mount point/directory is owned by root and the permission set on this is 700."
1827159,2019-07-17 21:00:39 UTC,Looks similar to https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1516451
1827159,2019-07-17 21:07:20 UTC,"Ramon, I'm not certain yet if LP #1516451 and LP #1516451 are precisely the same issue, although it's likely they can be solved in similar fashion.  Your customer issue looks like a better match to 1516451 since it involves the /sys/kernel/debug/tracing file which I see you've already commented on with a better test case than I had found, so I'll follow up with you there."
1827159,2019-11-08 21:55:28 UTC,A PPA with the proposed fix is available at:
1827159,2019-11-14 19:53:02 UTC,Patch forwarded upstream to https://github.com/monitoring-plugins/monitoring-plugins/pull/1609
1827159,2019-11-15 22:50:33 UTC,This bug was fixed in the package monitoring-plugins - 2.2-6ubuntu1
1827159,2020-07-10 23:19:00 UTC,"df no longer shows squashfs mounts by default, as of today's coreutils update"
1827162,2019-06-18 21:29:24 UTC,"------- Comment From <email address hidden> 2019-06-18 17:28 EDT-------
*** Bug 157265 has been marked as a duplicate of this bug. ***"
1827162,2019-06-11 14:18:18 UTC,"Based on our analysis and comments from IBM confirming that this is an expected behavior, I am marking this as wont fix."
1827162,2019-06-11 08:35:40 UTC,"Yes, the devices are effectively missing on the systems - the explanation is said that there's a dummy vio (ie, powervm) bus created, but since it's not in use you get this message.  The message should be harmless, but ideally we should be able to just get rid of it.... This message has been around for a while."
1827162,2019-06-10 15:22:12 UTC,The kernel propagates the error back if /sys/../uevent file fails to write. /sys/bus/vio/devices/vio/uevent fails in this case because the drivers associated with it are:
1827162,2019-05-01 02:00:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827164,2020-01-08 04:13:00 UTC,This is excellent Matthew. Thanks for moving this forward.
1827164,2020-01-08 04:25:17 UTC,"Hi Tim,
I have posted a request here: https://discourse.jujucharms.com/t/promulgation-request-for-wordpress-charm/2494"
1827164,2020-01-14 22:18:20 UTC,"The promulgation request for the wordpress charm has been accepted, and the charm is now known as cs:wordpress-0."
1827169,2019-07-22 14:52:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827172,2019-11-27 04:21:24 UTC,The fix was released in sysv-rc 2.88dsf-41ubuntu6.3+esm1 for Trusty ESM.
1827172,2019-05-02 05:23:48 UTC,I have developed a patch which I believe fixes the problem.
1827172,2019-05-02 05:26:32 UTC,"This debdiff contains the patch for trusty. I have tested it, built it in a ppa and run autopkgtest, and things look fine to me."
1827172,2019-05-02 08:24:19 UTC,"The attachment ""sysvinit debdiff for trusty"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1827172,2019-06-07 00:26:48 UTC,"Attached is the final debdiff for release, mostly for having a record of it."
1827173,2019-05-01 05:47:22 UTC,"This can be fixed using an apache2 unit as a reverse proxy, if we desire.  Still would be good to have the ports exposed as an option."
1827175,2019-05-01 08:23:16 UTC,"I don't have the bandwidth or the equipment to work on a fix but I will take a patch for this.
it should not be too hard, this part of the code is pretty easy to understand"
1827175,2019-05-01 19:01:33 UTC,"On 01.05.19 07:21, Jeffrey Walton wrote:

> Public bug reported:
>
> I'm working on a Tritium ARMv7 dev board
> (https://www.amazon.com/gp/product/B07D4L7GXZ). It has a Cortex-A7
> (https://libre.computer/products/boards/all-h3-cc/).
>
> I'm testing native build of a package using Clang.
>
> GCC provides the following triplet:
>
>     $ gcc -dumpmachine
>     arm-linux-gnueabihf
>
> Clang provides the following triplet:
>
>     $ clang -dumpmachine
>     armv8l-unknown-linux-gnueabihf
>
> The Clang triplet is very unusual. I've never seen a compiler claim
> armv8l. ARM does not even have a hit for ARMv8l on their site
> (https://www.google.com/search?q=""armv8l""+site%3Aarm.com). According to
> https://github.com/tsandmann/armv8l-toolchain-linux, it is an ARM A-53
> toolchain. It looks like the mis-identification is causing some folks
> trouble, including me (https://stackoverflow.com/q/27121199/608639).
>
> Perhaps it would be a good idea if Clang reported something closer to
> the board it is running on.
"
1827175,2019-05-01 19:31:26 UTC,"I tested a LePotato, which is an Aarch64 dev-board from the same maker (https://www.amazon.com/gp/product/B074N5B8KZ). Here are the results. They look OK:"
1827175,2019-05-01 06:10:50 UTC,This may be helpful.
1827177,2019-05-06 11:35:13 UTC,you should check if your user have access to the location where the files are saved (and the backup as well)
1827177,2019-07-06 04:17:26 UTC,[Expired for HomeBank because there has been no activity for 60 days.]
1827181,2019-05-01 08:20:00 UTC,March 2019 may mean the problem started with the released of:
1827181,2019-07-01 04:17:19 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1827182,2019-05-01 15:04:56 UTC,"I just noticed that admin users are already coloured green in trunk (in the user list) & IRC users are prefixed with <IRC>. After some thorough thinking, I came to the conclusion that it would clutter the chat too much, if we add the symbols before every name, and I'm not sure what information a user would gain from these additions."
1827182,2019-09-15 15:46:55 UTC,Migrated to https://github.com/widelands/widelands/issues/1727
1827183,2019-05-06 05:07:52 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1827184,2019-07-31 03:52:49 UTC,"Hello,
can you try to install package ""haveged"" to see if this helps?
You can check the entropy availability before and after installing this package with command:
cat /proc/sys/kernel/random/entropy_avail"
1827184,2019-09-29 04:17:56 UTC,[Expired for linux-signed-hwe (Ubuntu) because there has been no activity for 60 days.]
1827191,2019-05-29 11:21:47 UTC,https://github.com/snapcore/snapcraft/pull/2577
1827191,2019-05-01 19:41:56 UTC,"Confirmed, I've run into this myself."
1827192,2019-05-02 11:11:12 UTC,"This would be an issue with designate-dashboard, please check the version of that package in your installation. Very likely the issue is a duplicate of https://bugs.launchpad.net/designate-dashboard/+bug/1750384"
1827192,2019-07-02 04:17:17 UTC,[Expired for Designate because there has been no activity for 60 days.]
1827193,2019-05-01 10:24:08 UTC,"I wanted to make ""internal transfer"" from one account other and HB is crushing."
1827193,2019-05-01 19:06:25 UTC,And after re run application to fake transaction internal are showing
1827193,2019-05-06 11:30:57 UTC,"when you say:
""I wanted to copy one transaction 100PLN and system is asking me that he found the same amount.""
how do you do this: inherit from the account window ?"
1827193,2019-05-06 11:37:18 UTC,is your OS windows ?
1827194,2019-05-03 14:56:29 UTC,Reported upstream on https://gitlab.gnome.org/GNOME/totem/issues/323
1827194,2019-05-03 13:23:01 UTC,"Here's a sample video I found that I assume is OK to share a link to. Just open it, turn subtitles off, and finally open the same file in the same Totem window."
1827194,2019-05-03 07:50:40 UTC,"Thanks, it looks like it's neither new nor a regression then (in the sense of something that used to work and stopped). Ideally having an example would make easier to test/work on the issue but I guess most of subtitled videos are non free content and can't be easily shared here?"
1827194,2019-05-03 03:42:51 UTC,"Added a gst-plugins-good1.0 task, assuming the problem is related to /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstmatroska.so"
1827194,2019-05-03 01:52:41 UTC,errors.ubuntu.com is timing out again today so I am unable to review the links in comment #7.
1827194,2019-05-02 21:59:28 UTC,the backtrace is not really that useful since it lacks debug symbols
1827194,2019-05-03 03:10:18 UTC,"Yes Sebastien, a .crash file appears in /var/crash/ if I killall -ABRT totem."
1827194,2019-05-02 16:30:26 UTC,Could you add a video example to the bug maybe?
1827194,2019-05-02 14:45:46 UTC,Five more:
1827194,2019-05-02 03:23:57 UTC,"That's certainly one totem crash, thanks :)"
1827194,2019-05-02 03:03:56 UTC,"Actually, this might be what you're looking for? The timestamp seems off though."
1827194,2019-05-02 03:03:31 UTC,Please follow all the instructions in:
1827194,2019-05-02 02:46:55 UTC,"I used ubuntu-bug as per instructions. The first time ubuntu-bug crashed when I hit the Send button, upon a second attempt it might have been successful, but I'm not sure. The ubuntu-bug window closed immediately when I hit Send, without feedback from either from the ubuntu-bug UI or in the terminal. I'm not sure if the information can find its way to this particular bug report given that I was never asked to specify where it belongs. This is all rather confusing."
1827194,2019-05-02 01:58:57 UTC,When totem is frozen please open a terminal and run:
1827194,2019-05-02 17:34:38 UTC,"Hopefully I'm adding the attachment correctly, and hopefully it contains some useful information."
1827196,2019-07-02 04:17:16 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1827196,2019-05-02 08:47:01 UTC,"The problem may have arisen due to a change in the footprint of an existing symbol. Footprints on the number of legs are the same. Something was incorrectly reassigned during the change, links with footprints for footprint were not reset, and so on."
1827196,2019-05-02 08:43:52 UTC,"Perhaps this is the imposition of background processes with ongoing work, such as backing up and editing footprins on the board. In the run-up to the fall, I added new components to the circuit, including my own creation (the symbol is my own), re-assigned footprints (footprints — official), worked with both buttons “Load Netlist” and “Update PCB from Schematic”. Components added - chips with 8 legs. Another moment when I reassigned the footprint to an existing symbol, the original footprint was already connected to the miel, the problem started when I changed the footprint, applied the changes and started deleting the tracks. The original footprint is an SO 8 foot IC, the new one is an SOP 8 foot IC. The error popped up when I hovered the mouse over the new footprint and under it was the track that was connected to the previous footprint. I press delete and warning are rises..."
1827196,2019-05-02 08:31:23 UTC,But what about the screenshot of the error and the description of my actions? Isn't that enough? I can not provide this project. Oral disclosure statements are not enough. Ask leading questions. Ask the tests. I work further and kicad has not fallen since that moment. The fall was preceded by a bug warning that is attached.
1827196,2019-05-02 08:52:07 UTC,"Try to make a separate project that contains about 30 footprints, among which there are several chips with 8 legs. Try to sort out the tracks and change the footprints in the chips for similar ones with the same number of legs. Then try to remove the track by hovering the mouse over the contact pad of the chip. I got this error after 3 hours of continuous work with the program."
1827196,2019-05-01 12:16:51 UTC,Not yet
1827196,2019-05-01 12:16:05 UTC,I continue to work and falls yet
1827196,2019-05-01 12:06:52 UTC,"No, this project I cannot attach, sorry"
1827196,2019-05-01 11:56:59 UTC,Could you attach the project for which this occurs?
1827196,2019-05-02 08:20:34 UTC,Could you split out the ratsnest stuff in a separate report please? It will go unnoticed in here.
1827199,2020-03-20 08:57:32 UTC,This bug still exist in ubuntu19.10
1827199,2019-08-07 16:32:08 UTC,I can reproduce the problem in a VM when changing the default language of the desktop to Traditional Chinese. The upstream build of firefox is similarly affected.
1827199,2019-05-15 07:19:21 UTC,"I think it is not a firefox's bug, it's a ubuntu's bug."
1827199,2019-05-03 15:47:31 UTC,"> gnome tweak developer says ""Tweaks on Fedora 30 allows changing the font of Firefox 66.0.3"", so I doubt this is a ubuntu's bug.
"
1827199,2019-05-03 11:26:31 UTC,"This is probably a ubuntu19.04 bug
In fedora, even if the locale is zh_CN, the firefox will use the font set by gnome-tweak."
1827199,2019-05-03 10:13:32 UTC,"I change /etc/default/locale from
widon@widon-X555YI:~$ cat /etc/default/locale
#  File generated by update-locale
LANG=""zh_CN.UTF-8""
LANGUAGE=""zh_CN:zh""
to
widon@widon-X555YI:~$ cat /etc/default/locale
#  File generated by update-locale
LANG=""en_US.UTF-8""
LANGUAGE=""en_US:en""
the firefox's menu font can be set now."
1827199,2019-05-03 09:32:37 UTC,"Well, it works here, see my screenshot."
1827199,2019-05-03 09:17:56 UTC,"gnome tweak developer says ""Tweaks on Fedora 30 allows changing the font of Firefox 66.0.3"", so I doubt this is a ubuntu's bug."
1827199,2019-05-03 08:55:30 UTC,"The firefox66.0.3's menu font not change definitely.
I set all font to Zfull gb(a bitmap font), so the effect is very obvious."
1827199,2019-05-03 08:40:31 UTC,"I can set the ""interface text"" font in gnome-tweaks and the font size in the firefox menu changes accordingly. I can do that both on 18.04 and 19.04."
1827199,2019-05-03 09:49:57 UTC,"I can see, you change firefox font successfully.
I do not format /home when I install ubuntu19.04.
I doubt there are some thing in /home do not allow me to change the firefox's font."
1827201,2021-01-21 16:06:03 UTC,"So we do pass '-t' twice intentionally:
        if options.allocatePTY {
                args = append(args, ""-t"", ""-t"") // twice to force
        }"
1827201,2021-01-21 13:36:17 UTC,Note that https://serverfault.com/questions/593399/what-is-the-benefit-of-not-allocating-a-terminal-in-ssh
1827201,2020-09-23 23:31:45 UTC,"Setting pty will have unintended consequences when ssh is used to shell into a machine but as shown in this bug, can be set explicitly when required."
1827201,2019-05-05 08:18:18 UTC,"Note that the code is aware of this:
                }
                // TODO (anastasiamac 2018-08-29) We want to have a new
line after here (fmt.Fprintln).
                // However, it will break all existing scripts and should
be done as part of Juju 3.x work.
                _, err := fmt.Fprint(ctx.Stdout, v)"
1827201,2019-11-20 04:17:28 UTC,[Expired for juju because there has been no activity for 60 days.]
1827201,2019-05-05 07:31:27 UTC,"I'm pretty sure we just shell out to ""ssh"" without changing anything about
line endings."
1827201,2019-05-01 15:32:14 UTC,juju config does not even have a new line character so the config outputs to the same line as the next prompt:
1827201,2020-09-21 11:54:23 UTC,"Hi, reopening to bring new information"
1827202,2019-05-01 11:33:07 UTC,This has been assigned CVE-2019-7306
1827202,2019-05-02 18:08:29 UTC,The .screenrc file format description does indicate that a password can be set in it (https://www.gnu.org/software/screen/manual/screen.html#Detach) so it does appear that in theory this could be a privacy problem.
1827202,2019-05-02 18:09:44 UTC,"(Since the apport hook is part of the ubuntu packaging, there is not a need for an upstream task here.)"
1827202,2019-05-03 15:20:47 UTC,"Sander Bos, thank you for your research and report. I agree that this is a potential privacy leak and it should be fixed, and I appreciate the work you've done in identifying it. However, while your work does identify a worthwhile improvement, I think that calling this a security vulnerability is a stretch, given the following. Please do correct me if I'm factually wrong. The following points are believe objective and not a matter of opinion:"
1827202,2019-05-06 13:42:24 UTC,MP to skip the inclusion of the user's .screenrc from the apport crash report:
1827202,2019-06-01 21:21:22 UTC,Fine.  I'll merge this upstream.
1827202,2019-07-17 11:43:15 UTC,Is there anything blocking this being merged upstream?
1827202,2019-07-17 13:01:35 UTC,"This has been merged already (rev2614), I updated the bug status."
1827202,2019-09-19 13:42:37 UTC,This fix is in 5.128-0ubuntu1 in Eoan
1827202,2019-09-19 13:46:22 UTC,"CVE classified as low, and Paride talked with Amurray and SRUs are not needed on this.
If security wants to push it still the patch is in the repo of byobu."
1827203,2019-12-15 04:17:48 UTC,[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]
1827203,2019-10-15 17:07:21 UTC,"Could you give some details on the installation? Is it using bios or uefi mode?
Do you have only one OS installed? (likely, otherwise you would get the menu without having to change the configuration)"
1827203,2019-05-02 21:35:57 UTC,"I'm unable to reproduce this on an X230 or T450s. I would have thought the firmware to be pretty similar, at least enough that I could see this issue when a similar config is applied."
1827204,2019-07-18 21:12:29 UTC,Thank you for capturing this scenario.
1827205,2019-05-01 19:07:26 UTC,Not actually related to the package
1827205,2019-05-01 19:12:55 UTC,Some of our archive mirrors are on hosts that require the Host: header to function. The presence of the default Apache2 page there shows you hit a working webserver.
1827205,2019-07-01 04:17:27 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1827206,2019-05-01 17:17:47 UTC,"While this issue does not gate the stx.2.0 release, the error paths in the code should be cleaned up to provide a proper error reason."
1827206,2019-05-08 19:52:16 UTC,"By convention, non-gating issues are marked as low priority."
1827206,2019-05-17 08:41:07 UTC,"Reproduced it, will try to check it."
1827206,2019-05-20 08:00:59 UTC,"Hi all,
I prefer to return ""400 BAD REQUEST"", ""to indicate that the input data is invalid."""
1827206,2019-07-05 08:06:14 UTC,"Hello,
  With the help of Allain Legacy, I have reproduced bugs in the latest starlingx (2019/06/26) environment. Currently, the script code is parsed and debugged mainly according to the log. The scope of the bug may be a bit large and takes a little time.
  If you have good suggestions, welcome to share.
  The following is the log of the bug reproduction."
1827206,2019-07-12 09:25:35 UTC,Issue reproduced by Neusoft engineer.
1827206,2019-08-07 08:25:21 UTC,"Hello,
    I recently mainly analyzed the log information of the command and the script code related to the http status code. Currently, I have not found a place to set the status code.In the course of the investigation, there are several speculations.
    1.code return value 200 indicates that the server and the client are successfully connected, and successfully received the POST request, and has not performed the related operations of the certificate installation, so it returns 200.
    2.The format of the command ""system --debug certificate-install -m dummy mykey.pem"" is correct. The parameter mode is set incorrectly (dummy). The http server does not recognize the error.
    3.http status code is a standard numeric code common to HTTP. In openstack, the corresponding code return value judgment processing, whether it may have been encapsulated, is directly obtained through system functions during use."
1827207,2019-07-01 08:01:22 UTC,"The verification of the Stable Release Update for vte2.91 has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827207,2019-06-28 10:56:47 UTC,"Sorry, I forgot to verify this for ages!"
1827207,2019-05-06 12:41:46 UTC,"Hello Iain, or anyone else affected,"
1827207,2019-07-01 08:01:17 UTC,This bug was fixed in the package vte2.91 - 0.56.2-1ubuntu1~19.04.1
1827208,2019-05-01 17:27:01 UTC,Marking stx.2.0 release gating as https functionality is not working via APIs.
1827208,2019-06-11 16:13:41 UTC,"Reviewed:  https://review.opendev.org/664607
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=f68e183cb0e47b0dea449ad9474314f80e9c26e4
Submitter: Zuul
Branch:    master"
1827208,2019-06-19 19:55:15 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666431"
1827208,2019-06-20 19:41:43 UTC,"Reviewed:  https://review.opendev.org/666431
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=7bb0b606bb1de7f97d146555b811252f60decc0d
Submitter: Zuul
Branch:    master"
1827208,2020-06-27 18:10:36 UTC,LP was fixed a long time ago; removing the stx.retestneeded tag
1827209,2019-09-15 15:05:31 UTC,Migrated to https://github.com/widelands/widelands/issues/3422
1827210,2019-06-13 19:29:58 UTC,This issue was fixed in the openstack/ovsdbapp 0.16.0 release.
1827210,2019-05-02 13:22:15 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656774"
1827210,2019-06-03 10:54:45 UTC,"Reviewed:  https://review.opendev.org/656774
Committed: https://git.openstack.org/cgit/openstack/ovsdbapp/commit/?id=776377f0b6d3785a2e0dc73542140e1c8b5bd3e9
Submitter: Zuul
Branch:    master"
1827212,2019-10-27 10:51:34 UTC,Thanks for reporting.
1827213,2019-05-02 17:15:59 UTC,"Which window manager do you use? Please look at the KiCad System Requirements webpage [1], and the known System Related Issues [2] to see if this sheds any light on the matter."
1827213,2019-07-28 04:17:39 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1827213,2019-05-02 20:28:17 UTC,"@Harald, thanks for the clarification.  My laptop runs ubuntu 17.10.  I was waiting until after KiCon to upgrade to 18.10 so I guess I'll bite the bullet and see if I can duplicate your bug.  I cannot duplicate it on 17.10 or Debian testing with a stock gnome desktop so it may be related to ubuntu.  It may take me a few days to get around to it.  If you have time, try logging into a vanilla gnome desktop on you system and see if it resolves the issue."
1827213,2019-05-02 19:22:06 UTC,@Michael:that's right. it has nothing to do with the broken Eagle file. I can not import lbr and mod files under Ubuntu. Nobody else seems to have problems under Ubuntu. It's laying maybe on my Ubuntu installation. When I find time i will tray to found out the differences of the libs between Suse and ubuntu next week and i also can compile Kicad for my self.
1827213,2019-05-02 18:17:52 UTC,"@Wayne, I think the choose file dialog on Ubuntu wasn't allowing the selection of the .lbr/.mod files even though they had valid extensions. I don't think the fact the file was broken should matter at that stage?"
1827213,2019-05-02 17:51:16 UTC,"If I'm reading this correctly, it sounds like the issue was a broken eagle file.  Do we need to keep this bug report open for any reason?"
1827213,2019-05-02 13:28:54 UTC,"I have it with English and German try - same result
No import of lbr and mod files with Ubuntu"
1827213,2019-05-28 13:13:33 UTC,I just tested both of the attached libraries using 5.1.2-83-g356ccd031 on Ubuntu 18.04 with a stock gnome desktop and I could not find any issues.  I'm at a loss as to how to duplicate this issue.
1827213,2019-05-01 16:51:25 UTC,Well I'm out of ideas. Please report back when you have tried it at your work tomorrow.
1827213,2019-05-02 08:16:29 UTC,Are you by any chance using kicad in any language different to english? We had a similar problem reported a while back where we discovered that for some reason the translation plays into this.
1827213,2019-05-01 13:25:54 UTC,"Please can you provide more information on the exact problem? (example files, detailed steps to reproduce, screenshots, screen recordings etc.)"
1827213,2019-05-01 14:50:37 UTC,. I added two files. I can not select these files in the footprinteditor. they are gray. In version 5.10 this still worked.
1827213,2019-05-01 14:54:04 UTC,"...sorry the mod-file is missing. Import mod-files is more important , i think...
hth"
1827213,2019-05-02 19:24:58 UTC,"@Michael
my windowmanager is KDEs Kwin, also at work under SuSE..."
1827213,2019-05-01 15:25:06 UTC,"I can also use the Eagle library (.lbr file) by including it in the fp-lib-table using the same method I detailed above (second procedure), but this time selecting ""Eagle 6.x (*.lbr)"" as the plugin type."
1827213,2019-05-01 15:10:33 UTC,"I can import the .mod file into the footprint editor no problem using the recent stable release.
1) Open footprint editor
2) File > Import Footprint from KiCad File...
3) Select .mod file (make sure the file extension hasn't been changed, my Mac for some reason added .html to the end, which stopped KiCad from importing it.)
You can then save the legacy footprint to the a new format library."
1827213,2019-05-01 15:32:42 UTC,"I tried again. Neither with the one described by you about the import function nor the add in
the fp-lib-table leads to success for me
The mod file remains gray. I can not choose it ..."
1827213,2019-05-01 15:47:43 UTC,"... no, the eagle lbr files don't work (same as the mod-files) .No error-messages.
I can not select this files.Always grayed not select-able."
1827214,2019-05-02 00:16:10 UTC,"Fixed in revision 4efed8a4dd4d2518da942686f031f2abcb99f0a2
https://git.launchpad.net/kicad/patch/?id=4efed8a4dd4d2518da942686f031f2abcb99f0a2"
1827214,2019-05-01 20:26:16 UTC,"If the 1REL label is removed and only the connection is left, the ERC
does not indicate that R1 has the terminal not connected.
Report error only if there is no wire connected to the pin."
1827214,2019-05-01 20:02:52 UTC,"So what is the ""Test single istances for global labels"" option for?"
1827214,2019-05-03 21:33:55 UTC,"Are we really sure that the ERC is working properly?
The patch has fixed the problem of single global labels.
It remains to understand why a pin connected to a disconnected wire is not highlighted"
1827214,2019-05-01 19:37:51 UTC,And pcbnew confirms it ...
1827214,2019-05-01 19:48:47 UTC,How would Eeschema know that 1REL and REL1 were not /supposed/ to be two different nets?
1827214,2019-05-01 14:29:14 UTC,"I can't reproduce this in the latest stable (5.1.2), the single label is flagged as expected."
1827214,2019-05-01 20:12:31 UTC,"Good question.  I don't know the answer to that.  I can research it later, but I'm knee-deep in the modern toolkit right now...."
1827214,2019-05-01 19:27:55 UTC,"I'm quite puzzled ...
I put down a really stupid schematic with the deliberately incorrect label 1REL instead of REL1."
1827214,2019-05-01 16:04:41 UTC,"@Michael the commit in the original report is on master branch, so this is with new ERC behavior."
1827218,2019-05-01 14:44:58 UTC,See https://manual.calibre-ebook.com/faq.html#my-device-is-not-being-detected-by-calibre
1827218,2019-07-01 04:17:23 UTC,[Expired for calibre because there has been no activity for 60 days.]
1827220,2019-05-01 15:00:31 UTC,Have linked this to github issue https://github.com/UbuntuBudgie/budgie-extras/issues/169
1827220,2019-05-01 18:02:49 UTC,"I removed the applet, it removed from the ""taskbar"", but that baloon still pop's up."
1827220,2020-05-15 09:48:48 UTC,Closing this.  Dropby has been completely reworked in 20.04
1827220,2019-05-01 15:17:08 UTC,"In the interim you can remove the ""dropby applet"" from your panel."
1827223,2019-05-02 05:39:52 UTC,"what is that ""??"""
1827223,2019-05-02 06:27:59 UTC,?? is a placeholder for an unused military_number. Sorry should have explained that.
1827223,2019-05-02 06:38:41 UTC,"OK, I believed that you already has the code... Do you need some help with finding unused number? I am using grep for this..."
1827223,2019-05-02 07:13:12 UTC,"I tested the code with a hardcoded value of 3 (which means an enemy military presence of 3 is allowed), but I thought some genetics should apply here."
1827223,2019-09-15 15:04:50 UTC,Migrated to https://github.com/widelands/widelands/issues/3423
1827228,2019-05-01 14:55:55 UTC,"Was hoping the kernel 5.0.x be a lot better for these kind of support, but now highly disappointed."
1827228,2019-05-01 15:16:54 UTC,"ubuntu-drivers list to see your availaible drivers list, try the 390 perhaps
or the ubuntu graphics drivers ppa"
1827228,2019-05-02 07:31:09 UTC,"Hi.
""try the 390 perhaps
or the ubuntu graphics drivers pp"". Is this a guess??? Or you knew this is
a fix???  Sorry, I think I was spending/wasting enough time trying to TS
this issue.  In some way, I think the Windows system works better, as far
as legacy driver support goes.  Or, should I wait for a newer kernel
release and hope they'll get this fixed?"
1827228,2019-08-06 05:00:34 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1827229,2019-05-01 17:26:56 UTC,Marking stx.2.0 release gating as https functionality is a release requirement.
1827229,2019-07-03 18:19:11 UTC,"After further thought and analysis about this issue, we have decided that adding a SAN for the floating IP address in the temporary self-signed certificate adds no value.  The preferred approach is to remove the FQDN from the CN so that the client does not attempt to validate against the server's source IP or FQDN at all.  The end user can then safely add a custom certificate over the TLS encrypted channel created with the self-signed certificate."
1827229,2019-07-03 19:59:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/668988"
1827229,2019-07-08 15:28:26 UTC,"Reviewed:  https://review.opendev.org/668988
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=99b32ff37f7763d92b5a4427f0c07e2967e0b57a
Submitter: Zuul
Branch:    master"
1827229,2020-06-27 18:10:58 UTC,LP was fixed a long time ago; removing the stx.retestneeded tag
1827231,2019-07-01 04:17:25 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1827231,2019-05-01 18:32:26 UTC,In VarLogDistupgradeMainlog.txt we can see:
1827232,2019-07-23 08:09:58 UTC,thanks! fixing in eoan shortly!
1827232,2019-07-23 08:10:13 UTC,"I don't consider this worth a fix in stable, let me know if you think otherwise"
1827232,2019-07-23 09:55:57 UTC,This bug was fixed in the package borgbackup - 1.1.10-2~build1
1827233,2019-05-01 16:17:13 UTC,This will address lp:1605049
1827233,2019-07-19 15:53:12 UTC,This should include vias.  Details from lp:1837207 :
1827234,2019-09-06 01:50:37 UTC,"tempest run just call stestr.command method so this should be a stestr issue but the doc say they say a black list can have comments https://stestr.readthedocs.io/en/latest/MANUAL.html
what version of stestr was installed?"
1827234,2020-01-24 16:16:54 UTC,"By default tox_envlist is set to 'smoke' [1]. Also notice that everything after '--' (starting by tempest_test_regex) in [2] is actually passed to tox as a posarg [3]. That said, --regex parameter already contains 'smoke' so if tempest_test_regex was defined it will fail because tox will try to run something like:"
1827234,2020-02-02 02:24:42 UTC,Multi line comments did not work as found in https://review.opendev.org/#/c/655222/6/.zuul.yaml@231
1827234,2020-02-05 14:59:30 UTC,(?x) works for single line ansible string variables
1827234,2020-02-05 15:00:06 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/705976"
1827234,2020-03-19 03:11:30 UTC,"Reviewed:  https://review.opendev.org/705976
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=4af65407b17bb29c7e2cc376697ee1ef5d1cb6ce
Submitter: Zuul
Branch:    master"
1827235,2019-05-02 02:01:33 UTC,Please:
1827235,2019-07-01 04:17:28 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1827236,2019-05-02 15:28:45 UTC,EG 3.2.4
1827238,2019-07-17 17:12:22 UTC,"This bug is believed to be fixed in cloud-init in version 19.2. If this is still a problem for you, please make a comment and set the state back to New"
1827238,2019-05-29 04:59:46 UTC,"This bug is fixed with commit ded1ec81 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=ded1ec81"
1827238,2019-05-04 00:34:00 UTC,"The misspelling is part of the original netplan;  it has been fixed but only in bionic and newer.  For max compatibility it's best to always render/supply the misspelling.  Cloud-init will accept either key, but for now will only render the misspelling as all netplan releases support this key."
1827238,2019-05-03 17:01:22 UTC,"cloud-init included the only (mis)spelling of gratuitous-arp, per"
1827238,2019-05-03 16:25:09 UTC,"To document what the issue is, MAAS sends the key 'gratuitous-arp', following netplan, however cloud-init misspells this key as 'gratuitious-arp'. MAAS will *workaround* this issue until cloud-init fixes it."
1827238,2019-05-03 15:52:55 UTC,MAAS sends this snippet:
1827238,2019-05-04 00:55:34 UTC,"On Sat, May 04, 2019 at 12:34:00AM -0000, Ryan Harper wrote:

> The misspelling is part of the original netplan;  it has been fixed but
> only in bionic and newer.  For max compatibility it's best to always
> render/supply the misspelling.  Cloud-init will accept either key, but
> for now will only render the misspelling as all netplan releases support
> this key.
"
1827238,2019-05-03 15:06:10 UTC,I'm struggling to find the right parameters to get serial console. I did notice we get this error when booting after the install
1827238,2019-05-02 20:28:04 UTC,"Do you have a tcpdump of the network traffic? That is needed to be able to determine what the issue is. We need to inspect the HTTP headers that is being sent from nginx to the client. Specifically the ""Content-Length"" header to see if there is a mismatch there."
1827238,2019-05-02 19:48:14 UTC,"So there are no apparent issues from the MAAS perspective, we really need to see console logs to be able to determine what's the issue. Keeping this as incomplete for MAAS until console logs can be provided."
1827238,2019-05-01 17:45:53 UTC,"I don't see any errors during this install for curtin.  It installs grub2 uefi, adds the entry (0017), reorders back to boot from network (0016)."
1827238,2019-05-01 16:43:18 UTC,"On Wed, May 1, 2019 at 11:40 AM Andres Rodriguez <email address hidden>
wrote:"
1827238,2019-05-01 16:34:38 UTC,So this is what I see on the logs:
1827238,2019-05-03 15:41:12 UTC,console output: http://paste.ubuntu.com/p/HyCmWrHYqw/
1827240,2019-05-22 20:49:18 UTC,"Fixed in revision 67cc2aac2e59b119f443f6951ff88a549503cffd
https://git.launchpad.net/kicad/patch/?id=67cc2aac2e59b119f443f6951ff88a549503cffd"
1827241,2020-12-08 23:49:04 UTC,"On first glance, this doesn't feel like a charm issue. It feels like its a problem with the designate horizon. If its never actually hitting the server, it feels like its browser side. And indeed the console log provided by peppepetra86 in comment #5 points to a javascript issue which matches LP#1750384."
1827241,2020-11-17 21:59:00 UTC,"Hi Team,"
1827241,2019-07-15 04:17:28 UTC,[Expired for OpenStack Designate Charm because there has been no activity for 60 days.]
1827241,2019-05-15 16:31:54 UTC,Please could you provide the bundle for this system and any logs from horizon instance that might show the error.
1827241,2019-08-05 08:51:57 UTC,"Hi,"
1827242,2019-06-08 18:26:27 UTC,I never use nightlies
1827242,2019-06-07 12:22:58 UTC,"I agree with #3. It may improve the situation for all if the item is deselected after an action is performed as autocad does. (someone suggestd this)  But this may also expose other usability issues, we need to be careful here."
1827242,2019-06-08 18:22:19 UTC,"You need to think about printed tracks, holes, pads, vias, layers, layering standards for production and so on, and not lines, polygons, brushes, 3d models, meshes, vertices, edges and so on ..."
1827242,2019-06-08 18:27:23 UTC,Use release 5.1.2 it stable
1827242,2019-06-08 18:17:26 UTC,"There are users who have been using KiCAD for many years, developing circuit boards. There are users who have worked for many years in GImp, AutoCAD, blender3d and they suddenly needed to make a PCB. Those tools that have been used in AutoCAD, Blender3D, and so on have been formed over the years by users who regularly used this software in their work, similarly to KiCAD. If we take and apply tools and manners from graphic editors, as their users say, KiCAD as a PCB design program will die. It will turn into a genetically modified vegetable: beautiful outside and no inside. I consider the priority to be those users who have been using KiCAD for many years. Naturally, everybody can speak. As for me, starting with KiCAD 5, developers are striving to make it more beautiful and add the same functionality that is found in modern graphic editors. KiCAD as software for developing printed circuit boards is slowly expressed.
What kind of compromise are we talking about? Make KiCAD a universal program for drawing and 3d-modeling?))
On the contrary !!! I don't want a lot of things to change in kicad. As I wrote above in this post, kicad took the path of external decoration and that's it. Some accelerated canvas added. What for? There was an error in pointing to the grid points. In the old canvas it was? What was wrong with the usual? He did not slow down a gram. How many projects I have on it (kicad 4.0.7)! I did not want to offend anyone. Who offended, I apologize.
As for the choice, wrote above. The existence of two ways of doing things leads to conflict. The habitual position of the broadcasts, which was in earlier versions of KiCAD, is rudely broken.
KiCAD is never a 2d or 3d graphic tool. Having the ability to view in 3d is for clarity and greater control. KiCAD draws not lines, points, fills, polygons, primitives, it draws printed tracks, copper zones, vias, footprints, text on the screen printing layer, and so on !!! This is the main thing. Have you ever designed circuit boards?"
1827242,2019-06-12 12:34:14 UTC,"For now, I've enabled the option #2 for pcbnew edit actions.  I'd like some feedback on this workflow change from folks.  Are we bumping into new issues?  Should we expand this to Eeschema?"
1827242,2019-06-12 19:10:30 UTC,"Yes. I think, for eeschema this way is good too. Single way selection for both eeschema and pcbnew is a good idea.I think that there were no problems in msw, when the context menu is called up (while moving an object) or the editing key is pressed on the keyboard, you need to use your program cursor or disable api msw cursor update. About x can not say anything. It would be good if you could return the selection of objects, if it was accidentally removed (undo selection), cancel the selection in two ways: by ESC with the current tool or via the context menu separately from the tool (cancel selection). The rest in the choice as usual: key shift, control and so on. Maybe it would be nice, in principle, to make a selection mode (like a check mark, which includes the ability to select, mass select objects)."
1827242,2019-06-12 20:05:19 UTC,"I, too, think that eeschema should behave like pcbnew. Especially because it behaved like this (cursor position says which item is acted upon) earlier before eemodern."
1827242,2019-06-07 08:10:17 UTC,"Anton,"
1827242,2019-06-12 12:29:56 UTC,"Fixed in revision e691704a822816c8f734f3c43a828479900fd710
https://git.launchpad.net/kicad/patch/?id=e691704a822816c8f734f3c43a828479900fd710"
1827242,2019-06-07 04:44:33 UTC,"Main target is to make PCB manually or automatically, not an pictures or 3d models."
1827242,2019-06-07 04:52:13 UTC,"If you familiar with AutoCAD make your PCB with it)). Try, may be it be much faster))"
1827242,2019-05-01 16:15:10 UTC,"We can't do number (1) without causing substantial problems.  Number (2) might make sense.  Then, if the mouse is not over the selection BB, we would revert to the unselected behavior."
1827242,2019-06-07 04:38:36 UTC,"KiCAD is not an autocad, blender3d, wings and so on!!! Is not an 3d 2d graphics editing software!!!"
1827242,2019-05-01 16:32:27 UTC,"I think the current priority is correct. Selecting something is a more deliberate action, so should take priority over ""cursor hover over item"". What about people who select to delete, but their mouse may wander whilst they look for the delete key on the keyboard? This was discussed recently on the mailing list [1] in a different context."
1827242,2019-05-01 16:41:21 UTC,"Yes this inefficient. You right.
KiCAD is not an graphical software. Is a tool, that creates electrical schematic and printed circuit boards, not an pictures, 3d-models and other."
1827242,2019-05-01 16:57:45 UTC,See how it works.
1827242,2019-05-01 17:02:28 UTC,"""Many times Esc pressing"" - is a bad standard, as for me. Action must be made ONLY under object, on which mouse cursor howers on. If object is selected and it is a part of selected group action takes on whole group (move, delet, edit some common priperties and so on)."
1827242,2019-05-01 16:27:08 UTC,"Make action ONLY with object, that under cursor. Be it selected or not. This implies that in order to perform an action on a group of selected objects, you must hover the cursor on one of the objects of this group. The action applies to the group. In my opinion it is quite real."
1827242,2019-05-01 23:06:36 UTC,"No matter how hard I try to learn, again and again I bump to this problem. I haven't analyzed it very deeply but I think it happens after I first have done something to the selected items and and KiCad has left them selected after the action. My brains kind of tell me I have finished what I was doing and now I'm starting afresh. I move the mouse and try to delete something but the previously selected items are deleted."
1827242,2019-05-02 05:54:36 UTC,"Probably the simplest solution will be to enter a warning dialog before deleting in any cases of deletion, for example, ""Do you really want to delete the selected object ""Object visible name""?"" or ""Do you really want to delete the object ""Object visible name""?"" or ""Do you really want to delete the selected group of objects?"". Continue frantically pressing Esc twice so that the entire selection is removed ..."
1827242,2019-05-02 05:57:31 UTC,"If you need to delete a lot of unconnected track segments, you will have to confirm the deletion dialog many times. This is pretty awkward."
1827242,2019-06-06 23:28:38 UTC,A solution (in-part) would be to have the item(s) automatically de-selected after completing an action.
1827242,2019-05-01 17:13:33 UTC,"The graphic engine will have to be modified so that all functions in kicad 4 are implemented in kicad5 and improved - expanded already in kicad6. I understand that it is easier to impose what the new graphics engine (wxWidgets) provides, but nothing good will come of it. Make a regular painter."
1827245,2019-09-29 19:37:35 UTC,This also pops up on Linux.
1827246,2019-09-24 03:53:18 UTC,"Reviewed:  https://review.opendev.org/677126
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=f8ec30d0c69ec0c843b8077bd892b8e932279c6c
Submitter: Zuul
Branch:    master"
1827246,2019-09-12 10:05:23 UTC,"Hi Team,"
1827246,2019-09-12 11:44:24 UTC,"Hi Anirudh,"
1827246,2019-09-16 10:05:15 UTC,Hi Zhipeng
1827246,2019-09-17 02:39:37 UTC,"My patch is ready for merge and I'm pushing now, hope it can be merged this week.
You can use new version with this patch after some days."
1827246,2019-09-19 09:03:47 UTC,Hi Zhipeng
1827246,2019-09-24 03:24:43 UTC,"Reviewed:  https://review.opendev.org/680908
Committed: https://git.openstack.org/cgit/starlingx/openstack-armada-app/commit/?id=2e63d41e5c429b616454fed0ac2073a73ad5d5b5
Submitter: Zuul
Branch:    master"
1827246,2019-09-24 19:37:18 UTC,"@Zhipeng, the fix will need to be cherry-picked to the r/stx.2.0 branch so that it's included in the next maintenance release. Please do this asap."
1827246,2019-10-03 15:21:30 UTC,"@Anirudh Gupta, The fix will be available in the next stx.2.0.1 (maintenance) release. Please monitor the stx-discuss mailing list for availability. A re-install of the new ISO will be required."
1827246,2019-09-25 01:42:05 UTC,"Fix proposed to branch: r/stx.2.0
Review: https://review.opendev.org/684443"
1827246,2019-09-25 18:43:26 UTC,"Reviewed:  https://review.opendev.org/684443
Committed: https://git.openstack.org/cgit/starlingx/upstream/commit/?id=104189e1618a5c4f2cebe538cbf2ce6ce3e2dfec
Submitter: Zuul
Branch:    r/stx.2.0"
1827246,2019-09-25 18:54:31 UTC,"Reviewed:  https://review.opendev.org/684440
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=707cdd9d68f223c84cd4a5d9ffb8fad0434629d2
Submitter: Zuul
Branch:    r/stx.2.0"
1827246,2019-09-26 06:47:20 UTC,"Hi,"
1827246,2019-09-09 04:54:07 UTC,"Change abandoned by zhipeng liu (<email address hidden>) on branch: master
Review: https://review.opendev.org/679913
Reason: Abandon as repo changed.
Resubmit with below patch
https://review.opendev.org/#/c/680908/"
1827246,2019-10-11 08:35:34 UTC,"Hi Ghada,"
1827246,2019-11-19 11:00:51 UTC,"hi,
this is my first try at STX 2.0 and i also run in this issue. after add ""10.10.10.2 novncproxy.openstack.svc.cluster.local"" to my host-file, the console-GUI is shown but my browser-debug-console tells me ""cant connect to ws://localhost:17523/""."
1827246,2019-11-19 11:15:29 UTC,"*
-- can i KEEP my current version..."
1827246,2020-01-17 15:27:22 UTC,"verified on load 20200115T023003Z (HWlab IP 20-27)
successfully accessed instance console (as admin/tenant)
successful access also when logged into floating IP."
1827246,2019-09-25 01:21:23 UTC,"Fix proposed to branch: r/stx.2.0
Review: https://review.opendev.org/684440"
1827246,2019-09-09 04:52:03 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680908"
1827246,2019-08-13 18:26:11 UTC,The issue is still present - as of: 2019-08-12_20-59-00
1827246,2019-09-03 09:59:58 UTC,"Hi all,"
1827246,2019-05-01 17:11:25 UTC,Marking stx.2.0 gating as access to VM consoles is a basic requirement for using VMs.
1827246,2019-05-05 02:21:06 UTC,Hi @chriswinnicki have you done these settings? I got this recipe from mailing list previously.
1827246,2019-05-07 14:21:46 UTC,"Hello Yong Hu, i tried to follow your WA but i'm not able to see the console after applying that values to the IP tables plus modifying /etc/hosts, any other suggestion?"
1827246,2019-05-07 22:24:30 UTC,"We tested the mentioned steps today as Elio mentioned. The steps worked before but know is not possible to reach the console. However, we tried a ssh tunnel with :"
1827246,2019-05-08 13:16:17 UTC,The root cause was 6080 on OAM was blocked by GlobalNetworkPolicy controller-oam-if-gnp
1827246,2019-05-08 18:22:37 UTC,"I tried WA from Erich,
I opened a tunnel with ssh command from my jumper to the controller:
   ssh -L 6080:localhost:6080 wrsroot@10.10.10.3
   Remark: the tunnel need to keep alive in order to keep the VM consoles opened.
I enabled ""AllowTcpForwarding yes"" flag in ""/etc/ssh/sshd_config"" file.
Once edited I restart the sshd config by ""sudo systemctl restart sshd"""
1827246,2019-05-10 07:53:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658288"
1827246,2019-05-10 07:56:53 UTC,"after this fix is accepted and with the original settings (https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Instance_Console_Access), the VM VNC console in Horizon (:31000) should be seen."
1827246,2019-09-04 05:42:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/679913"
1827246,2019-05-10 10:54:51 UTC,"OpenStack is not a platform service and should not be exposed via the OAM firewall by default.  When OpenStack is installed, the either with http or https enabled, then the appropriate GlobalNetworkPolicy should be configured to enable access to that port via the OAM network."
1827246,2019-06-03 13:03:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662748"
1827246,2019-06-20 20:28:20 UTC,"Reviewed:  https://review.opendev.org/662748
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=9b0820d1d65dca4c2d647f6e6aff435c58e84592
Submitter: Zuul
Branch:    master"
1827246,2019-07-25 19:23:32 UTC,"Issue was reproduced on
WCP_105
20190718T013000Z"
1827246,2019-07-25 20:15:24 UTC,I just now tested on 0724 build and this feature did work well. see the attachment.
1827246,2019-07-25 20:16:31 UTC,"did you set this as this wiki says ""https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Instance_Console_Access""??"
1827246,2019-08-07 12:51:21 UTC,"This issue reappeared on baremetal system as Peng commented above.
The wiki link for instance console access provided by Yong seems no longer valid, but I would expect no extra manual configuration needed on baremetal system. With the same environment, I was able to access the vm console from Horizon about a month ago."
1827246,2019-08-13 18:50:57 UTC,"@Frank, please assign some one to resolve this issue.
It was not about the nova-vnc port for which I made the patch anymore.
it requires a solution, mentioned by Matt in the attached mail."
1827246,2019-08-16 23:31:47 UTC,"@Zhipeng is to implement a node-port for novnc-proxy so that novnc console can be accessed by users on its explicit port, similar to Horizon (:31000)."
1827246,2019-08-19 07:30:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/677126"
1827246,2019-06-03 01:45:42 UTC,"Change abandoned by yong hu (<email address hidden>) on branch: master
Review: https://review.opendev.org/658288"
1827247,2019-11-07 15:42:25 UTC,"That's fine, works for me. Thanks Steve."
1827247,2019-11-04 16:19:19 UTC,"Removing packages from focal:
 percona-galera-3 3.21-0ubuntu3 in focal
  percona-galera-3 3.21-0ubuntu3 in focal amd64
  percona-galera-3 3.21-0ubuntu3 in focal arm64
  percona-galera-3 3.21-0ubuntu3 in focal armhf
  percona-galera-3 3.21-0ubuntu3 in focal i386
  percona-galera-3 3.21-0ubuntu3 in focal ppc64el
  percona-galera-3 3.21-0ubuntu3 in focal s390x
  percona-galera-3-dbg 3.21-0ubuntu3 in focal amd64
  percona-galera-3-dbg 3.21-0ubuntu3 in focal arm64
  percona-galera-3-dbg 3.21-0ubuntu3 in focal armhf
  percona-galera-3-dbg 3.21-0ubuntu3 in focal i386
  percona-galera-3-dbg 3.21-0ubuntu3 in focal ppc64el
  percona-galera-3-dbg 3.21-0ubuntu3 in focal s390x
  percona-galera-arbitrator-3 3.21-0ubuntu3 in focal amd64
  percona-galera-arbitrator-3 3.21-0ubuntu3 in focal arm64
  percona-galera-arbitrator-3 3.21-0ubuntu3 in focal armhf
  percona-galera-arbitrator-3 3.21-0ubuntu3 in focal i386
  percona-galera-arbitrator-3 3.21-0ubuntu3 in focal ppc64el
  percona-galera-arbitrator-3 3.21-0ubuntu3 in focal s390x
  percona-galera-arbitrator-3-dbg 3.21-0ubuntu3 in focal amd64
  percona-galera-arbitrator-3-dbg 3.21-0ubuntu3 in focal arm64
  percona-galera-arbitrator-3-dbg 3.21-0ubuntu3 in focal armhf
  percona-galera-arbitrator-3-dbg 3.21-0ubuntu3 in focal i386
  percona-galera-arbitrator-3-dbg 3.21-0ubuntu3 in focal ppc64el
  percona-galera-arbitrator-3-dbg 3.21-0ubuntu3 in focal s390x
Comment: Ubuntu-specific, only builds with gcc-6, unused; LP: #1827247
1 package successfully removed."
1827247,2019-11-04 16:21:50 UTC,"If a wider poll gets you a different answer, you can reupload a package fixed to not build-depend on gcc-6 :-)"
1827247,2019-11-04 15:21:57 UTC,"Steve, I believe we're ready to remove percona-xtradb-cluster-5.7 in favor of mysql 8. I'm going to poll a wider audience just to make sure though."
1827247,2019-05-03 20:25:16 UTC,The future of Percona is in question since the MIR was rejected. We should know better about this direction soon.
1827247,2019-11-04 16:18:17 UTC,"Removing packages from focal:
 percona-xtradb-cluster-5.7 5.7.20-29.24-0ubuntu3 in focal
  percona-xtradb-cluster-5.7-dbg 5.7.20-29.24-0ubuntu3 in focal amd64
  percona-xtradb-cluster-5.7-dbg 5.7.20-29.24-0ubuntu3 in focal arm64
  percona-xtradb-cluster-5.7-dbg 5.7.20-29.24-0ubuntu3 in focal armhf
  percona-xtradb-cluster-5.7-dbg 5.7.20-29.24-0ubuntu3 in focal i386
  percona-xtradb-cluster-5.7-dbg 5.7.20-29.24-0ubuntu3 in focal ppc64el
  percona-xtradb-cluster-5.7-dbg 5.7.20-29.24-0ubuntu3 in focal s390x
  percona-xtradb-cluster-server 5.7.20-29.24-0ubuntu3 in focal amd64
  percona-xtradb-cluster-server 5.7.20-29.24-0ubuntu3 in focal arm64
  percona-xtradb-cluster-server 5.7.20-29.24-0ubuntu3 in focal armhf
  percona-xtradb-cluster-server 5.7.20-29.24-0ubuntu3 in focal i386
  percona-xtradb-cluster-server 5.7.20-29.24-0ubuntu3 in focal ppc64el
  percona-xtradb-cluster-server 5.7.20-29.24-0ubuntu3 in focal s390x
  percona-xtradb-cluster-server-5.7 5.7.20-29.24-0ubuntu3 in focal amd64
  percona-xtradb-cluster-server-5.7 5.7.20-29.24-0ubuntu3 in focal arm64
  percona-xtradb-cluster-server-5.7 5.7.20-29.24-0ubuntu3 in focal armhf
  percona-xtradb-cluster-server-5.7 5.7.20-29.24-0ubuntu3 in focal i386
  percona-xtradb-cluster-server-5.7 5.7.20-29.24-0ubuntu3 in focal ppc64el
  percona-xtradb-cluster-server-5.7 5.7.20-29.24-0ubuntu3 in focal s390x
  percona-xtradb-cluster-source-5.7 5.7.20-29.24-0ubuntu3 in focal amd64
  percona-xtradb-cluster-source-5.7 5.7.20-29.24-0ubuntu3 in focal arm64
  percona-xtradb-cluster-source-5.7 5.7.20-29.24-0ubuntu3 in focal armhf
  percona-xtradb-cluster-source-5.7 5.7.20-29.24-0ubuntu3 in focal i386
  percona-xtradb-cluster-source-5.7 5.7.20-29.24-0ubuntu3 in focal ppc64el
  percona-xtradb-cluster-source-5.7 5.7.20-29.24-0ubuntu3 in focal s390x
Comment: Ubuntu-specific, only builds with gcc-6, unused; LP: #1827247
1 package successfully removed."
1827247,2019-11-01 06:08:51 UTC,"James, Corey, it's been a cycle since this bug was opened.  Any decision yet on whether these packages will be removed or fixed?"
1827249,2019-05-02 07:36:35 UTC,"L'acronyme se trouve dans https://git.launchpad.net/ubuntu-fr-doc/tree/conf/acronyms.local.conf
On met les deux ? à savoir : Integrated Development Environment / Environnement de Développement Intégré
Ou juste l'explication en anglais ou encore directement la traduction ?
Perso je serais plus pour l'indication des 2 (avec anglais en premier)"
1827249,2019-05-02 18:09:17 UTC,"Finalement ma proposition modifie IDE et ajoute l'acronyme EDI dans la liste.
J'ai préféré commenter (#) l'ancienne ""traduction"" d'IDE."
1827250,2019-05-01 18:10:59 UTC,"This appears to be caused by the last captured hold check in the new open-ils.storage.action.live_holds.wide_hash method.  This method was introduced in Evergreen 3.2, so 3.1 should not be affected by this bug."
1827250,2019-10-03 21:54:01 UTC,"Pushed all the way back to rel_3_2. Thanks, Jason and Michele!"
1827250,2019-09-13 19:51:49 UTC,"John, good points about retaining the current_copy for cancelled holds for the purposes of clearing the holds shelf and troubleshooting. I can see the value there, but it seems like retaining current_copy in every hold makes it more cumbersome to get the pertinent data out of action.hold_request."
1827250,2019-07-24 16:43:25 UTC,"Michele,"
1827250,2019-07-24 15:16:32 UTC,"We've gotten reports of this on our 3.2.4 system. I'll test the patch, but here's a question:"
1827250,2020-02-11 16:19:53 UTC,"Josh, see bug 1855329."
1827250,2019-05-02 12:48:33 UTC,"Thanks for the suggestion, Mike.  I tried both variants with explain analyze, and the nulls last version is overall faster.  (See the attached document with the results for a single copy.)"
1827250,2019-05-21 17:08:08 UTC,"BTW, CW MARS is using the branch from comment #5 in production since the 14th of May 2019 with no adverse consequences.  It is working for us as intended."
1827250,2019-05-01 20:16:52 UTC,My fix branch is here:
1827250,2020-02-11 15:56:32 UTC,"Hello, I'm finding that the ""NULLS LAST"" query takes 65 seconds to return 372 rows, while the ""AND RECHECK.capture_time IS NOT null"" takes 1.3 seconds to return 372 rows."
1827250,2019-05-01 20:26:15 UTC,"Comment #1 is a case of, I should have edited my comment in a text editor instead of directly into the web form."
1827250,2019-05-01 20:56:04 UTC,"Great catch, Jason."
1827251,2019-05-22 02:07:03 UTC,Thanks for reporting this Jason. Code that raises an error when the timeout has been reached and the state is still running/pending is currently under review.
1827253,2020-06-25 13:15:10 UTC,"Yeah I have considered it as nice drive-by improvement unrelated to this bug - and thanks for doing so.
I just had sorted out some lose ends on rsyslog and they both where part of it."
1827253,2020-06-25 12:24:37 UTC,"@Christian, https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345 was a 'drive-by' merge proposal not associated with any LP (is that OK?). As such, I don't consider it related to this bug which can be closed now AFAICT."
1827253,2020-06-24 15:13:03 UTC,I want to look at this again ...
1827253,2020-05-14 08:20:04 UTC,The version of rsyslog in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.
1827253,2020-04-15 23:34:06 UTC,"The 1st SRU for Bionic failed because I typo'ed the path to the binary (rsyslog != rsyslogd).
Focal is fixed and Bionic is left with a 'bad' package in bionic-proposed. I don't think redoing the SRU for Bionic is worth it, it's a default *disabled* profile after all."
1827253,2020-04-15 19:19:29 UTC,"Simon,"
1827253,2020-02-14 14:17:26 UTC,"The version in focal-proposed works well, thanks Christian! I hadn't anticipated the additional roadblocks so I really appreciate you pushing it forward nevertheless!"
1827253,2020-02-12 20:55:59 UTC,This bug was fixed in the package rsyslog - 8.2001.0-1ubuntu1
1827253,2020-02-11 07:34:04 UTC,We have a new MP that fixes things for real in Focal.
1827253,2020-06-25 12:04:39 UTC,"Let us kill the SRU - given what happened last time and that this is a
a) disabled by default profile
and
b) user fixable by editing a conffile"
1827253,2019-10-30 15:11:35 UTC,I feel really bad now :/
1827253,2019-10-30 14:13:36 UTC,"Hello Simon, or anyone else affected,"
1827253,2019-10-30 14:14:35 UTC,"Hello Simon, or anyone else affected,"
1827253,2019-07-03 14:47:03 UTC,"This actually is a perfect bug:
- simple case
- solution on a silver plate
- only changing d/* content
- already ubuntu Delta"
1827253,2019-07-03 17:01:19 UTC,This bug was fixed in the package rsyslog - 8.1901.0-1ubuntu2
1827253,2019-10-05 00:39:59 UTC,I'm hitting the same problem when using a Bionic host with a Bionic container when using the 5.0 HWE kernel.
1827253,2019-10-08 11:33:20 UTC,"The fix is trivial, so this should be fine.
But I'm just back from PTO and a bit swamped by TODOs right now, so bear with me as I'll need some time :-)"
1827253,2019-07-03 15:07:21 UTC,"On 2019-07-03 10:47 a.m., Christian Ehrhardt  wrote:

> I feel bad that this hung around so log, but today I saw it and gave it a review.
> This is building in Eoan now.
"
1827253,2019-10-16 05:33:46 UTC,MPs got reviewed and uploaded to D/B SRU queue
1827253,2019-10-24 14:30:04 UTC,"Reviewing this, it feels to me like something nice to have, but low-importance enough that I'd be worried about users getting an upgrade with no impact for them (and, as per the regression potential, some low-chance but still regression risk). The SRU policy is a bit conflicted there: on one side we should only do high-impact bugs *or* low-risk bugs in case of applications. But this is rsyslog, so something a bit more low-level, so it's up to some interpretation as to what the policy thinks about it."
1827253,2019-10-24 15:16:54 UTC,"Thanks for the review Łukasz,
I somewhat agree with your summary. The reason I went on with it was because it was very low hanging fruit and Simon (Bug reporter) is like ""The Ubuntu community good bug reports role model"".
But I agree that the update for everyone (it is always installed) might be too much."
1827253,2019-10-25 12:48:04 UTC,Thanks Łukasz and Christian. I find the block-proposed-* tags idea interesting if that's not too much work on your side.
1827253,2019-10-14 06:59:41 UTC,"I prepped the two MPs for the SRU as this isn't the biggest impact fix, but OTOH patch-on-a-platter and also easy to review for code/impact."
1827256,2019-05-07 11:19:59 UTC,global-physnet-mtu can be overridden by per-physnet values:
1827256,2019-05-20 08:05:47 UTC,"Reviewed:  https://review.opendev.org/657401
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=068471e6e5b3192997a51d17c2c93074d0c61915
Submitter: Zuul
Branch:    master"
1827256,2019-05-17 07:51:00 UTC,"Reviewed:  https://review.opendev.org/657400
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=9d0473c2a9444b1c04f5a6950ecc47b04c9796b0
Submitter: Zuul
Branch:    master"
1827256,2019-05-13 10:30:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658782"
1827256,2019-05-07 14:45:27 UTC,"Change abandoned by sahid (<email address hidden>) on branch: master
Review: https://review.opendev.org/657401"
1827256,2019-05-07 11:47:39 UTC,Thank you Dmitrii for the heads-up this looks something we should do.
1827256,2019-05-06 16:03:45 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657400"
1827256,2019-05-20 08:15:48 UTC,"Reviewed:  https://review.opendev.org/658782
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=440d6f0f49b74f713df1de72a4cec5726b85d0fc
Submitter: Zuul
Branch:    master"
1827256,2019-05-06 09:28:22 UTC,OK my mistake now I understand you are referring since the beginning to the DPDK devices plugged into the netdev bridge I was referring to the vhostuser interfaces [0].
1827256,2019-05-03 19:30:41 UTC,I'm not sure os-vif will set the MTU on the underlying dpdk devices presented from the network card.
1827256,2019-05-03 08:08:12 UTC,"Yes that makes sense, this option is really confusing."
1827256,2019-05-03 07:54:29 UTC,"The 'network_device_mtu' option is supposed to be deprecated as of Newton [0] [1] in favor of 'global-physnet-mtu' (which is set to 9000).
The version of python-os-vif is 1.9.0-0ubuntu1"
1827256,2019-05-03 06:21:04 UTC,"The problem is not the MTU configured in the deployed instances, it is just fine. I configured it through neutron-api to be 9000 and I have the correct value in the instances.
The issue that I'm facing is that the DPDK interfaces are not configured with the proper MTU value. That means that when trying to push traffic with an MTU of 9000 between two instances on a DPDK node that does not work.
For example, before changing the DPDK interface MTU value, if I try, in an instance:
ping 10.0.0.9 -s 9000"
1827256,2019-05-02 10:12:43 UTC,Normally libvirt or os-vif is responsible for creating the device and configuring the MTU I think they do that right. They both refer to the value passed via the network model which comes from Neutron.
1827256,2019-05-06 09:35:40 UTC,I had a look at the code my thinking will be to get the 'global-physnet-mtu' value from neutron-api that to set the MTU after to have added the interfaces into the bridge.
1827256,2019-05-03 07:40:05 UTC,I think I understand what you mean and as I mentioned os-vif should refer to the MTU indicated in the network object which comes from Neutron network model or it uses a default MTU which is configured via the option 'network_device_mtu' to configure the dpdkvhostuser interface.
1827258,2019-06-27 09:31:24 UTC,"By default, if no pending hugepage request, _update_huge_pages() will allocate
(m.vm_hugepages_possible_2M*0.9) 2M hugepage. But m.vm_hugepages_nr_2M_pending
will be used with priority. If user config 2M hugepage manually with a wrong
size, this issue will be triggered."
1827258,2019-06-27 08:54:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/667811"
1827258,2019-06-27 09:04:18 UTC,"After code review, the hugepage allocation check code has a problem."
1827258,2019-06-27 12:12:03 UTC,"I am seeing the same problem on a 2+2 lab. There are two compute hosts in this lab, with the same hardware and 32G of memory each. It looks like the two computes (same hardware) are reporting different numbers of available 2M pages:"
1827258,2019-06-23 09:38:44 UTC,"from compute-1_20190507.124154/var/log/kern.log
    2019-05-06T16:24:12.266 localhost kernel: debug [    0.000000] On node 0 totalpages: 4174118
    ...
    2019-05-06T17:28:56.749 compute-1 kernel: info [ 1515.471986] Node 0 hugepages_total=1 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
    2019-05-06T17:28:56.749 compute-1 kernel: info [ 1515.471987] Node 0 hugepages_total=6807 hugepages_free=6807 hugepages_surp=0 hugepages_size=2048kB
    ..."
1827258,2019-06-28 05:33:42 UTC,"some new findings from database dump:
=================================
node_memtotal_mib  platform_reserved_mib  ""vm_hugepages_possible_2M""  ""vm_hugepages_nr_2M_pending""  ""vm_hugepages_avail_2M""  ""vm_hugepages_nr_4K""
15428              8000                   3202                        \N                            6795                     0
15562              2000                   6269                        \N                            7177                     0
15643              8000                   3309                        \N                            6799                     0
15446              2000                   6211                        \N                            7172                     0"
1827258,2019-07-03 03:43:41 UTC,Patch (https://review.opendev.org/#/c/667811/) had been updated based on the discussion with Tao.
1827258,2019-07-12 15:28:01 UTC,"Updating the tag from stx.distro.other to stx.config as the issue is in the stx hugepage allocation, not with a 3rd party package."
1827258,2019-07-12 16:44:14 UTC,"Reviewed:  https://review.opendev.org/667811
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=5e42f69989433b7ac4c0aba6a4dd62900a45f905
Submitter: Zuul
Branch:    master"
1827258,2019-08-08 20:10:43 UTC,"closing based on verification in LP-1832647
2019-08-07_20-59-00"
1827258,2019-06-17 17:48:35 UTC,"The issue is we ran out of free kernel memory. We should never run out under any circumstances.
This LP needs to determine why we ran out and address the issue."
1827258,2019-07-12 15:26:36 UTC,"Raising the priority of this bug to high as it has been seen multiple times recently:
https://bugs.launchpad.net/starlingx/+bug/1836240
https://bugs.launchpad.net/starlingx/+bug/1835941"
1827258,2019-06-14 19:30:21 UTC,Can you elaborate on why this is not an issue? The system ran out of 4k pages. This is not expected under any condition.
1827258,2019-06-15 03:11:30 UTC,"As I mentioned above, "" free < min, kernel will start oom killer""."
1827258,2019-05-01 18:40:52 UTC,Some additional info:
1827258,2019-05-07 12:45:46 UTC,I'm seeing this again on a worker node in IP33-36 (worker-0) running load: 20190505T233000Z:
1827258,2019-05-08 19:55:47 UTC,"@Maria, was the stx-openstack application running at the time the oom error was reported?"
1827258,2019-05-09 00:25:06 UTC,"@Maria, do you think the issue is similar as this one? https://bugs.launchpad.net/starlingx/+bug/1826308
this was marked as ""fix released"" but we think it still there."
1827258,2019-05-09 13:26:58 UTC,"I'm not sure Cindy.  I think someone will need to look at the logs and triage it, to see if it is the same issue or different."
1827258,2019-06-27 16:32:12 UTC,"The above comment was for a designer load built on June 25, 2019."
1827258,2019-05-15 17:44:55 UTC,Marking as gating for now and will monitor for a re-occurrence.
1827258,2019-05-30 08:16:53 UTC,@Maria
1827258,2019-06-04 03:32:19 UTC,@Maria
1827258,2019-06-07 00:50:07 UTC,assign to @Bin Yang as he is looking into this bug already.
1827258,2019-06-10 05:57:34 UTC,"Based on the logs, it should not be a bug."
1827258,2019-05-10 19:30:47 UTC,"@Ghada, I believe application-apply was done when the original issue was seen but I'm not 100% sure.  Jim Gauld helped me investigate.  He may have some additional information."
1827263,2020-04-21 19:02:13 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827263,2020-04-22 04:43:46 UTC,Sorry I am a newbie here. But is it possible this was meant to be under Apache2 project?
1827264,2020-06-05 11:22:56 UTC,"yes,
dpkg -l | grep libc6
ii  libc6:amd64                           2.29-0ubuntu2                               amd64        GNU C Library: Shared libraries
ii  libc6-dev:amd64                       2.29-0ubuntu2                               amd64        GNU C Library: Development Libraries and Header Files"
1827264,2020-06-05 09:27:16 UTC,libc6?? ubuntu 1904 source?
1827264,2020-06-03 07:46:16 UTC,We managed to solve the problem by installing the libc version from the ubuntu disco repository.
1827264,2020-05-22 02:29:31 UTC,"I know this has been open for a year now, but for what it's worth, we're seeing the same issue on two of our three Neutron nodes. A whole lot of entries in /var/log/openvswitch/ovs-vswitchd.log like the following:"
1827264,2019-11-06 03:15:01 UTC,We catch this problem about a couple of times a week and have found a pretty non-trivial way to fix it quickly.
1827264,2019-11-05 13:54:13 UTC,Same on bionic with stein and ovs 2.11.0.
1827264,2019-05-13 18:00:26 UTC,A bit of follow up on this:
1827264,2019-05-08 17:51:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827264,2019-05-08 17:50:55 UTC,"I have same issue with highload cpu usage on network node Openstack Rocky Ubuntu 18.04
Kernel 4.15.0-48-generic #51-Ubuntu"
1827264,2019-11-11 08:55:25 UTC,"We are also seeing this in bionic with rocky neutron-openvswitch-agents. We haven't really found any pattern in when it occurs, but even after emptying out a compute node with live migrations and rebooting it, we will keep seeing it. Amount of traffic doesn't seem to be related."
1827265,2019-05-01 19:39:58 UTC,I am sorry that our PPA is outdated.
1827265,2019-05-01 19:40:49 UTC,https://launchpad.net/~mixxx/+archive/ubuntu/mixxx
1827266,2019-05-01 19:11:59 UTC,This is due to the way the test plans use wildcards where:
1827267,2019-09-27 08:51:49 UTC,"Hi Gabriel,"
1827268,2019-07-09 00:51:37 UTC,Could not reproduce with 0703-0705 daily build image
1827268,2019-05-22 02:44:29 UTC,"if reproduce again, could dump thread stack with these two command"
1827268,2019-07-25 14:33:31 UTC,"If this issue is not reproducible (as mentioned in comment #7), its status should be Invalid or Not Reproducible."
1827268,2019-05-07 05:18:18 UTC,"Maria, can you retest using the latest ISO (after 5/3 Ceph upgrade)?"
1827268,2019-05-03 18:08:59 UTC,"Marking stx.2.0 gating as this prevent the node to become available, might be related to ceph upversion to mimic."
1827268,2019-05-01 20:11:14 UTC,Looks like 'ls /opt/platform' is hanging.
1827268,2019-05-15 06:51:25 UTC,"Not reproduce on 0510 daily build image, will check  0426 daily build
http://edgehost03.sh.intel.com:8080/history-mirror-download/20190426T013000Z/"
1827270,2019-05-01 20:41:08 UTC,Changing of grid size should also be in the preferences/somewhere else that isn't just a right-click menu.
1827270,2019-05-01 23:31:09 UTC,"Why is the tool manager being called from the page layout editor?  AFAIK, the page layout editor hasn't be ported to the new tool framework."
1827270,2019-05-01 23:52:15 UTC,I think because the grid settings got moved to common in 94a948fd (@Jeff)
1827270,2019-05-01 23:58:47 UTC,It looks like some changes meant for legacy_gal/eda_draw_frame.cpp ended up in legacy_wx/eda_draw_frame.cpp.  I'll look into it tomorrow....
1827270,2019-05-02 23:12:07 UTC,"Fixed in revision 2e8d9302502219377332981724adfd71659dd480
https://git.launchpad.net/kicad/patch/?id=2e8d9302502219377332981724adfd71659dd480"
1827272,2019-06-12 21:26:59 UTC,"Reviewed:  https://reviews.mahara.org/10029
Committed: https://git.mahara.org/mahara/mahara/commit/33d1f34926a5233b3159d55978d2d0b0e9c41757
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1827272,2019-05-20 04:41:31 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10029"
1827272,2019-05-23 23:31:16 UTC,"Commit hash: d43aa090ab1f6681ad7464acbdafc648f5162f33
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw | Default raw | Ocean | Modern | Primary school"
1827272,2019-05-27 20:25:29 UTC,"New Commit hash: ccc80fbc97ff9bd85c58c5f905290ac36d8a2c2f
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw | Default raw | Ocean | Modern | Primary school"
1827274,2019-05-18 13:39:45 UTC,"Highlighting (of all hits) implemented.  Still need to do move logic and selection of current hit, and remove cursor warping UI controls."
1827274,2019-05-22 20:49:12 UTC,"Fixed in revision 67cc2aac2e59b119f443f6951ff88a549503cffd
https://git.launchpad.net/kicad/patch/?id=67cc2aac2e59b119f443f6951ff88a549503cffd"
1827275,2019-09-15 15:04:05 UTC,Migrated to https://github.com/widelands/widelands/issues/3424
1827279,2019-09-15 15:03:24 UTC,Migrated to https://github.com/widelands/widelands/issues/3425
1827279,2019-05-02 07:16:33 UTC,"I think stocklevel of carriers is available but not taken into account as it is calculated for ware by default, also the code is there to calculate it for workers as well. I'll have look into this for sure, cause currently frisians are favoured by Ai in this particular part."
1827279,2019-05-02 05:20:50 UTC,"I plan resume training soon, so you can just add more such lines and let AI training cope with them..."
1827279,2019-05-02 06:32:13 UTC,I currently tested these things in a local copy of the fri03 branch to see whether AI is capable of performing the scenario. I made good progress already. However I will prepare a branch over the weekend. I'll be afk of my development machine until Friday evening.
1827279,2019-05-02 06:44:53 UTC,"The problem with carriers are that it is hard to measure necessity of its output (no stocklevel of course), but if I remember properly, it is tied to number of buildings but also the building score might be too low..."
1827281,2019-05-14 09:28:29 UTC,A fix has been proposed at https://review.opendev.org/658999 for this
1827281,2019-05-14 13:42:26 UTC,"Reviewed:  https://review.opendev.org/658999
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=37d40405204c821b87fe1cf54fa7bbb2fcf8bd37
Submitter: Zuul
Branch:    master"
1827282,2019-05-06 05:07:42 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1827282,2020-05-01 19:54:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827284,2019-05-08 09:22:09 UTC,Fix landed upstream: https://gitlab.gnome.org/GNOME/gnome-shell/commit/8702d66
1827284,2019-06-06 09:33:53 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827284,2019-06-06 09:33:24 UTC,This bug was fixed in the package gnome-shell - 3.28.4-0ubuntu18.04.1
1827284,2019-05-29 22:18:02 UTC,gnome-shell version 3.28.4-0ubuntu18.04.1 fixed the bug for me.
1827284,2019-05-28 21:40:52 UTC,"Hello Alexandre, or anyone else affected,"
1827284,2019-05-08 07:38:01 UTC,"Fix proposed upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/538"
1827284,2019-05-23 12:37:47 UTC,"I'm extremely sorry. While trying to see what the different statuses mean, I accidentally changed the bug status to ""fix released"" and launchpad doesn't let me undo my mistake. I hope this doesn't cause any trouble."
1827284,2019-05-08 02:42:09 UTC,And the same bug is not in 19.10.
1827284,2019-05-02 02:05:40 UTC,I noticed this issue upstream in Gnome 3.30 and 3.32 too. But I assumed it was a *feature* and not a bug -- maybe an attempt by the developers to make opening the app drawer faster before the fix for bug 1750197 existed.
1827284,2019-05-08 02:41:08 UTC,"Sorry, yes, I failed to notice the attached video."
1827284,2019-05-08 02:38:00 UTC,"Strange. I do now have the animation in bionic today (gnome-shell version 3.28.3+git20190124-0ubuntu18.04.2), providing I use the mouse and not Super+A. So the ""regression"" I was thinking of isn't in bionic with the Ubuntu Dock at least."
1827284,2019-05-07 13:52:37 UTC,"Daniel, could you dig the details for bionic there? Did it regress in a SRU? If so what do you recommend we do next?"
1827284,2019-05-02 02:16:56 UTC,"If this bug does get fixed then the fix would likely go into Ubuntu 19.10 and 18.04, but not the versions in between. Because the versions in between were released with this behaviour, where it is arguably a feature."
1827284,2019-05-08 06:47:50 UTC,Finally got there in the end...
1827285,2019-05-06 03:37:57 UTC,https://github.com/juju/juju/pull/10139
1827285,2019-05-03 07:14:04 UTC,This is a test I've used https://github.com/juju/juju/pull/10133. Provided here as a reference.
1827285,2019-05-03 07:03:50 UTC,It's possible that this has similar if not the same symptom as bug # 1827461.
1827285,2019-05-03 06:54:41 UTC,So I am still investigating and am not entirely sue what is going on.
1827285,2019-05-03 00:07:21 UTC,"Ah, I remember now..."
1827285,2019-05-02 13:11:44 UTC,"Here are the controller logs and juju dump-db output from both reproductions.  Files with second in the name, are with the new machines."
1827285,2019-05-02 13:09:24 UTC,"@anastasia,"
1827285,2019-05-01 23:26:50 UTC,"@Heather,"
1827285,2019-05-03 02:43:59 UTC,"Also looking at the model-dump, the txn-queue on the actual machine has 3 entries! It looks like transactions get stuck somewhere? I am not convinced that this is a purely destroy issue atm..."
1827286,2019-05-06 08:44:11 UTC,"I played a bit with my config and found:
- the error is even reported if /home is set to mount something that won't work (e.g. non existent server), so it must failing early in the autofs processing
- one can mount things manually (as expected)"
1827286,2019-05-06 09:12:47 UTC,"In the kernel
$ git log -p v4.4...v4.15 -- fs/autofs4
has a bunch of fixes, but none is clearly matching the case here just by reading it."
1827286,2019-05-06 09:02:47 UTC,"Debugging per [1], did not show anything new.
There just is no activity on the actual access of /home all I see is the trigger for /home registering at startup."
1827286,2019-05-06 07:04:47 UTC,"Yep, here we go.
Setting up the same on Xenial got me:"
1827286,2019-05-03 09:37:40 UTC,"to summarize and be sure on the case:
1. there is a NFS target
2. you have autofs configured to mount /vol/home from that NFS
3. if there is a symlink /home -> /vol/home before that mount happens it fails
Is the above correct?"
1827286,2019-05-03 14:44:09 UTC,I did a little more testing and this looks to be specific to /home.  Even mounting over /home (no linking) with autofs results in the same issue.
1827286,2019-05-03 10:06:37 UTC,I followed the first hits that I have found [1][2] to set up a similar situation.
1827286,2019-05-02 18:37:22 UTC,Looks like the issue is symlinking to a director prior to autofs mounting it.
1827286,2019-05-06 06:43:01 UTC,"Hi Jason,
I understand your comment #12 that we can eliminate the symlink from the equation.
It is not needed for you to trigger the issue - thanks for that hint."
1827287,2019-05-01 22:13:02 UTC,"An example, where a flag is added to the config.yaml for the setting to indicate it's a risky move to change it:"
1827288,2019-06-03 17:57:11 UTC,@sil2100 Thanks for the review!
1827288,2019-06-04 08:58:36 UTC,"...since the debian/watch file still didn't quite work, I fixed it and pushed the changes to the repository. Now it's good to go!"
1827288,2019-06-04 08:32:12 UTC,"Thanks for addressing all the issues! I also see that the new version of the package build successfully on the autobuild PPA, awesome. I think this is now good for upload and acceptance - let me do that now."
1827288,2019-06-03 20:28:21 UTC,"Working with the upstream developer, I was able to apply patches that fix the test suite issues. @sil2100's question 2) above (and the item frustrating myself and @vorlon) is fixed. Git repo is tagged for 1.1.9-0ubuntu1 release to eoan."
1827288,2019-06-03 18:34:25 UTC,Addendum to previous comment (sorry about the noise):
1827288,2019-06-03 18:28:23 UTC,Question from the upstream developer RE: sil2100's question 2):
1827288,2019-06-03 17:47:18 UTC,"On Mon, Jun 03, 2019 at 05:03:53PM -0000, Łukasz Zemczak wrote:

> 2) I still see that override_dh_auto_test disables tests. In comment #6
> you mentioned that you were somehow able to make those working. Do those
> really not work currently? Of course if there's no way of running them
> during build then that's fine, but I want to make sure that they're
> disabled for valid reasons. Especially that there was some discussion
> regarding that previously.
"
1827288,2019-05-06 21:24:27 UTC,The version number in the debian/changelog of the git branch is wrong; this needs to be a non-native package using the upstream tarball from sourceforge.
1827288,2019-05-17 16:23:25 UTC,Uploaded to NEW queue per @vorlon
1827288,2019-05-07 19:11:44 UTC,"Thanks, this looks much better now, but there are a number of lintian errors that need to be addressed to get this archive-ready."
1827288,2019-05-07 01:16:34 UTC,"Hi Steve,"
1827288,2019-05-02 17:53:40 UTC,"Moved many variables to dpkg-buildflags, unable to fix the test run, appears to be unnecessary per http://manpages.ubuntu.com/manpages/disco/en/man1/dh_auto_test.1.html, unless I'm interpreting that wrong. Build works well, tested in the Ubuntu Studio Autobuild PPA (https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild)."
1827288,2019-05-02 14:37:58 UTC,Fixed the short descriptions. Pedantic returns nothing. Looking over the rules file.
1827288,2019-05-02 08:34:35 UTC,Also the short descriptions are all the same?
1827288,2019-05-02 08:33:08 UTC,"Not a full review, but I glanced at it, so in the hope that this can help speed things up:"
1827288,2019-06-03 17:03:53 UTC,Thank you for your upload! I did a quick review of the package in the NEW queue and I do have a few things I'd like cleared out before we get this one accepted into universe:
1827291,2019-09-08 04:16:19 UTC,"This was a catch-all reminder. Now that all necessary items have been created, we can remove this here."
1827292,2019-05-02 08:50:55 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1827292,2019-07-02 04:17:13 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1827296,2019-05-09 18:28:25 UTC,"I opened bug 1828456 for the AuthProxy issue, which can be fixed even if we don't fix the .init method."
1827298,2019-05-13 23:37:58 UTC,"Thanks Lutz, I have solved it and what I thought was a problem is not a problem. Sorry for that."
1827298,2019-05-10 05:53:07 UTC,"Thanks Lutz, what happens if you tag the same surface twice with two different physical tags - is this a problem?"
1827298,2019-05-02 02:11:12 UTC,"The top surface and potentially all other surfaces need to be added as ""Physical Surface"" to the geometry otherwise the surface elements are not written into the mesh file."
1827298,2019-05-10 14:33:23 UTC,first question: I am not so sure if this is a problem. The question is which tag is finally used.
1827299,2019-07-02 17:17:27 UTC,"Thank you for your bug report, could you report the issue upstream as well on https://gitlab.gnome.org/GNOME/nautilus/issues/ ?"
1827300,2019-05-04 17:30:44 UTC,This is complete in the eemodern branch.
1827302,2019-05-15 00:22:30 UTC,aka NET_WM_WINDOW_TYPE_POTATO
1827302,2019-07-23 14:17:36 UTC,"Beat me to it by 53 minutes Jesse!  I just updated my script too, but yours is more concise.  Thank you for the gist, it works great."
1827302,2019-07-23 13:23:19 UTC,"This no longer seems to be a problem with Slack 4.0.0, recently released and available via Snap. I modified the gist to only set an icon, which it is still missing, and updated it to work with the new window manager class and icon path."
1827302,2019-06-12 12:50:25 UTC,I made some further adjustments to the launch script from #12 and uploaded to:
1827302,2019-05-22 13:31:29 UTC,"As original reporter, I can confirm that the xprop trick works around this problem."
1827302,2019-05-15 23:16:36 UTC,Seems to fix Slack for me.
1827302,2019-05-15 20:51:36 UTC,Olivier Fourdan referenced this bugreport in commit 22fe30cdd99d111f043b3282a02f39df468c7ac2
1827302,2019-05-06 17:33:45 UTC,"Thank you so much Alistair!  That worked for me!  I actually already had a launch script for slack to do a bunch of stuff, one of the things is attaching an icon to it post-launch.  I was able to modify the script to handle running the ""xprop"" line above automatically."
1827302,2019-06-11 14:32:04 UTC,"Thanks!
It helped for me.
One thing I don't like it's after sleep time slack window goes to minimize."
1827302,2019-05-04 20:46:51 UTC,I suggest that you forward all details and the patch to the upstream devs.
1827302,2019-05-05 13:15:09 UTC,Slack is setting NET_WM_WINDOW_TYPE = NET_WM_WINDOW_TYPE_MAIN. This value is not defined in the EWMH spec and has zero results on Google.
1827302,2019-05-03 08:04:40 UTC,"I can confirm I have the same issue on Ubuntu 18.04, this started with Slack version 3.4.0."
1827302,2019-05-03 13:49:30 UTC,"The issue is also present on Xubuntu 18.04.2 LTS, slack 3.4.0, xfce."
1827302,2019-05-02 15:01:27 UTC,"This might just be bad timing.  I don't think it's your OS upgrade, I think it's the Slack release they just pushed.  I'm using Xenial and this broke for me this morning when I upgraded Slack's version, however I didn't change my OS version.  This might be a slack bug?"
1827302,2019-05-03 03:53:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827302,2019-05-03 18:17:47 UTC,"Sorry my bad, the diff is reversed. Use the following commands instead:"
1827302,2019-05-03 18:23:15 UTC,I'm attaching .deb and .ddeb (debug symbols) files I built myself if someone's too lazy or too busy to rebuild the patched xfwm4 him/herself.
1827302,2019-05-03 20:24:28 UTC,"The attachment ""Alt + Tab fix for xfwm4 and Slack"" seems to be a patch.  If it isn't, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team."
1827302,2019-05-03 18:12:58 UTC,This bug started in Slack 3.4.0 and affects Xubuntu 18.04.2 LTS too.
1827303,2019-05-02 11:28:22 UTC,"Hi Sarah, it seems I’m unable to reproduce these issues locally (see screenshots)."
1827303,2019-07-02 04:17:23 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1827304,2019-05-02 01:30:07 UTC,This change was made by a bot.
1827304,2019-05-02 01:50:48 UTC,Probably your device can't work well under i2c bus.
1827304,2019-05-02 06:38:49 UTC,">Probably your device can't work well under i2c bus.
>
>please have a try:
>add ""psmouse.synaptics_intertouch=0"" to the kernel bootargs.
"
1827306,2019-05-02 01:43:54 UTC,"OK, looking at some other resolved bugs and disabling UTF-8 does stop the status bar spam. So something in that ""Unknown"" question-mark box symbol is causing it to glitch out."
1827307,2019-05-02 22:24:05 UTC,"The /var/log/dist-upgrade/main.log file you've attached indicates there was a failure to contact the mirror the the Ubuntu archive which you are using.
2019-05-02 07:02:25,535 DEBUG examining: 'deb http://mirrors.aliyun.com/ubuntu/ cosmic main restricted multiverse'
2019-05-02 07:02:25,536 DEBUG verifySourcesListEntry: deb http://mirrors.aliyun.com/ubuntu/ disco main restricted multiverse
2019-05-02 07:02:25,536 DEBUG url_downloadable: http://mirrors.aliyun.com/ubuntu//dists/disco/Release
2019-05-02 07:02:25,536 DEBUG s='http' n='mirrors.aliyun.com' p='/ubuntu//dists/disco/Release' q='' f=''
2019-05-02 07:02:25,579 DEBUG error from httplib: '<urlopen error [Errno -2] Name or service not known>'"
1827307,2019-05-02 23:43:17 UTC,"Hi Brian, i will look into that, thanks for helping."
1827307,2019-07-02 04:17:42 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1827309,2019-05-06 05:07:14 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1827311,2020-04-27 02:08:37 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827313,2019-05-02 03:08:43 UTC,"query = model_query(context, models.Service).fitler_by(uuid=service_uuid)
should be revised as
query = model_query(context, models.Service).filter(uuid=service_uuid)"
1827314,2019-07-12 06:34:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827314,2019-10-16 13:25:37 UTC,"I experience the same issue. After suspend the lock screen and background image is gone, leaving only a ""white noise"" (see attached image). From what I can tell, this bug is purely aesthetical, and has no practical implications. I can still log in and use my computer like nothing happened."
1827314,2019-05-02 20:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827314,2019-06-05 02:42:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1809407, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1827316,2019-05-02 03:47:37 UTC,"No volume file：  /data02/fb7a4fb2face3a687595a60c83fb2c96/volume-5f6f0817-ffa4-4d46-a25a-701a261627f3
bug theare is a snapshot file：/data02/fb7a4fb2face3a687595a60c83fb2c96/volume-5f6f0817-ffa4-4d46-a25a-701a261627f3.5686f657-2594-42e8-a883-c8968e334f7c
and info file :/data02/fb7a4fb2face3a687595a60c83fb2c96/volume-5f6f0817-ffa4-4d46-a25a-701a261627f3.info"
1827316,2019-05-13 12:18:29 UTC,"It's unclear from your initial description why this has been marked as a suspected security vulnerability. Can you describe the impact which an unprivileged user is able to make on the system, for example denial of service to other tenants or escalation of access to perform actions normally limited to Cinder administrators?"
1827318,2019-07-25 13:02:43 UTC,This bug was fixed in the package blktrace - 1.1.0-2+deb9u1ubuntu0.18.04.1
1827318,2019-07-25 12:59:28 UTC,This bug was fixed in the package blktrace - 1.1.0-2+deb9u1ubuntu0.16.04.1
1827318,2019-07-25 09:38:26 UTC,"The verification of the Stable Release Update for blktrace has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827318,2019-07-24 10:34:07 UTC,"Updated tags to reflect ""verification-done-xenial"" based on Frank's posting #17."
1827318,2019-07-24 07:32:14 UTC,"Many thanks for taking the time and doing the verification on bionic.
Indeed 16.04 does not support P9.
However, attempting to satisfy the verification request for xenial, I just did a quick and basic test on a P8 system with xenial (running blktrace - and blkparse) and didn't faced any regressions.
I hope this satisfies the needed verification for xenial."
1827318,2019-07-24 06:43:32 UTC,"For Xenial, I can't deploy P9 node with it.
There is a 18.04 minimum requirement limit on power8-maas."
1827318,2019-07-24 06:37:17 UTC,"Tested on Bionic P9, test passed without any issue:
 PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-4.15.0-55-generic)"
1827318,2019-07-03 22:12:10 UTC,"> This issue will gone with Cosmic, looks like the blktrace tool was fixed in Cosmic.
"
1827318,2019-07-10 20:46:38 UTC,"Hello Po-Hsu, or anyone else affected,"
1827318,2019-05-22 13:23:22 UTC,"I've uploaded fixed packages in https://launchpad.net/~colin-king/+archive/ubuntu/ppa - tested on a power box, works fine."
1827318,2019-05-22 12:06:15 UTC,Two fixes required:
1827318,2019-05-20 17:09:06 UTC,"Re-assigning to kernel-team, as blktrace is a Universe package."
1827318,2019-05-20 17:07:44 UTC,"This bug has been marked 'medium' for the blktrace package and is in universe, which means it would not normally warrant an SRU.  If the Kernel Team needs Foundations support to resolve this for bionic in order to fix the test suite, the Kernel Team should ask Foundations directly."
1827318,2019-05-02 09:38:29 UTC,Tried this on another two Bionic P9 node:
1827318,2019-05-02 09:30:04 UTC,"Bug for P9 CPU in offline state (correct the wrong link in comment #4, which has been hide to prevent confusion).
https://bugs.launchpad.net/bugs/1827335"
1827318,2019-05-02 06:41:58 UTC,"Upstream bug for blktrace attempting to operate on offline CPUs:
https://bugzilla.redhat.com/show_bug.cgi?id=1321875"
1827318,2019-05-02 06:40:14 UTC,"This Invalid argument is caused by offline CPUs:
# cat /sys/devices/system/cpu/offline
156-159"
1827318,2019-05-02 06:26:05 UTC,It seems that the blktrace command is not working at all.
1827318,2019-05-29 16:44:44 UTC,Status update: blktrace package with fix is in SRU queue.
1827318,2019-07-10 20:46:02 UTC,"Hello Po-Hsu, or anyone else affected,"
1827321,2019-10-22 23:18:18 UTC,I wonder if this has been sufficiently addressed by a fix to bug # 1799476?
1827321,2019-10-31 05:47:25 UTC,"Works for me, thanks."
1827323,2019-07-02 04:17:39 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1827323,2019-05-02 07:09:28 UTC,"Please elaborate your full story in the bug description so developers can help you a better way
'issue' arise is not very helpful to debug"
1827323,2019-05-02 22:27:03 UTC,"Your /etc/apt/sources.list file has the release artful in it while you seem to have many packages installed from cosmic, Ubuntu 18.10. You'll need to fix your /etc/apt/sources.list file to reflect the release you are actually running for the upgrade to Ubuntu 19.04 to be possible."
1827324,2019-09-20 12:09:21 UTC,MAAS does not support custom Ubuntu images. Please use the standard Ubuntu image and customize either with the Curtin preseed or cloud-init user-data.
1827324,2019-05-14 13:31:35 UTC,Can we reproduce the issues with a clean setup enviroement which help us to isolate the problem for maas team?
1827324,2019-11-20 04:17:33 UTC,[Expired for OEM Priority Project because there has been no activity for 60 days.]
1827324,2019-05-02 07:02:55 UTC,">Are you saying that uploading an image to MAAS is not completing?
Yes
"
1827324,2019-05-02 06:16:00 UTC,"Hi there,"
1827324,2019-05-02 05:44:22 UTC,"# df -h
Filesystem                                  Size  Used Avail Use% Mounted on
default/containers/oem-taipei-staging-maas  315G  294G   22G  94% /
none                                        492K     0  492K   0% /dev
udev                                        3.9G     0  3.9G   0% /dev/tty
tmpfs                                       100K     0  100K   0% /dev/lxd
tmpfs                                       100K     0  100K   0% /dev/.lxd-mounts
tmpfs                                       3.9G   20K  3.9G   1% /dev/shm
tmpfs                                       3.9G  344K  3.9G   1% /run
tmpfs                                       5.0M     0  5.0M   0% /run/lock
tmpfs                                       3.9G     0  3.9G   0% /sys/fs/cgroup
tmpfs                                       787M     0  787M   0% /run/user/0"
1827324,2019-05-02 09:20:46 UTC,"btw, in physical host machine:
------------------------------
$ free -h
              total        used        free      shared  buff/cache   available
Mem:           7.7G        6.8G        464M        109M        446M        525M
Swap:          4.0G        1.7G        2.3G
------------------------------
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
22905 100116    20   0 1318908 546276   9416 S   0.0  6.8  48:10.92 regiond
22907 100116    20   0 1189652 435496   9400 S   0.0  5.4  54:52.02 regiond
22906 100116    20   0 1500976 424524   9260 S   0.0  5.3 243:08.89 regiond
22908 100116    20   0 1171404 380916   9388 S   0.0  4.7 209:34.20 regiond
21631 100111    20   0  320548 108548 107336 D   0.0  1.3   3:20.22 postgres
21475 100013    20   0  965216 107944   4592 S   0.0  1.3   0:30.91 squid
21632 100111    20   0  320188 105968 105132 S   0.0  1.3  14:10.15 postgres
22909 100111    20   0  327640  97692  94072 S   0.0  1.2   0:19.17 postgres
11196 100000    20   0  367704  97200  14888 S   0.0  1.2   0:03.75 maas-region
22626 100111    20   0  327428  97028  93424 S   0.0  1.2   0:19.49 postgres
22635 100111    20   0  328012  96056  92168 S   0.0  1.2   0:19.33 postgres
22505 100111    20   0  327320  95240  92368 S   0.0  1.2   0:19.10 postgres
22904 100111    20   0  327640  94940  91860 S   0.0  1.2   0:20.35 postgres
22620 100111    20   0  327756  94380  91344 S   0.0  1.2   0:18.90 postgres
22902 100111    20   0  3270..."
1827325,2019-05-02 06:04:09 UTC,"I recently noticed that long-appearance-time notifications happen when I'm reading and not using the mouse or keyboard.
A second after I click anywhere with my mouse, it disappears. If I don't do this, it will definitely remain there for minutes."
1827328,2019-10-04 06:48:29 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827328,2019-12-18 16:05:52 UTC,"Also observed on Ubuntu 18.04.3, with kernel 5.0.0-37-generic"
1827329,2019-08-24 07:12:32 UTC,(Just linking it together with the corresponding Debian report :) )
1827329,2019-11-16 17:57:05 UTC,"Build 20 was packaged in Debian and synced to Ubuntu Focal, which means it will be part of the upcoming Ubuntu 20.04 release (https://bugs.launchpad.net/ubuntu/+source/widelands/1:20-1)"
1827329,2019-11-16 18:06:40 UTC,"For older Ubuntu releases, it is possible to request a backport (https://wiki.ubuntu.com/UbuntuBackports)"
1827329,2019-11-16 18:11:45 UTC,"> ""Added eoan-backports task.""
"
1827329,2019-11-17 10:53:27 UTC,"`requestbackport` failed too, possibly also due to `eoan-backports` not existing. I've filed bug 1852901 to follow up on this."
1827330,2019-06-04 20:21:34 UTC,"Hi everyone,"
1827330,2019-05-21 19:22:27 UTC,If you provide us a kernel we can test it here or we can ship HBA's for your test environment or both.
1827330,2019-05-21 18:38:11 UTC,"Unfortunately, I do not have the hardware to test this. I can load the driver but without an HBA I can't recreate the crash."
1827330,2019-05-21 17:39:53 UTC,"commit fd9c40f64c514bdc585a21e2e33fa5f83ca8811b
Author: Bart Van Assche <email address hidden>
Date:   Thu Apr 4 10:08:43 2019 -0700"
1827330,2019-05-21 17:41:07 UTC,"Hi Shagun,"
1827330,2019-05-02 06:37:47 UTC,We have triaged the issue and mentioned the upstream commit that should fixes the issue in the bug description.
1827330,2019-05-02 06:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827330,2019-05-21 17:59:09 UTC,"This also looks to be in upstream stable as of May 19, so I presume will land in an SRU for Disco at some point."
1827331,2019-05-02 06:59:15 UTC,apport information
1827331,2020-06-18 05:10:16 UTC,I think it's worth a try with Ubuntu 20.04 and nvidia-440 there..
1827331,2019-05-02 07:53:27 UTC,"// After installed nvidia 418 , machine came back with login prompt :)"
1827331,2019-05-02 07:00:06 UTC,This change was made by a bot.
1827331,2019-05-02 06:59:20 UTC,For GTX cards its reccomended you try drivers from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa you could try version 418 or 430 as a test?
1827331,2019-05-02 06:59:18 UTC,apport information
1827331,2019-05-02 06:59:16 UTC,apport information
1827331,2019-05-02 06:59:14 UTC,apport information
1827331,2019-05-02 06:59:19 UTC,apport information
1827331,2019-05-02 06:59:12 UTC,apport information
1827331,2019-05-02 06:59:10 UTC,apport information
1827331,2019-05-02 06:59:09 UTC,apport information
1827331,2019-05-02 06:59:07 UTC,apport information
1827331,2019-05-02 06:59:06 UTC,apport information
1827331,2019-05-02 06:59:05 UTC,apport information
1827331,2019-05-02 06:59:03 UTC,apport information
1827331,2019-05-02 06:59:02 UTC,apport information
1827331,2019-05-02 06:45:09 UTC,Machine perfectly works with Ubuntu 16.04 LTS without any issues..
1827331,2019-05-02 06:59:13 UTC,apport information
1827332,2019-05-28 06:29:49 UTC,I made a first attempt to take a closer look at that.
1827332,2019-05-23 07:05:08 UTC,"The second link works fine for me but I've seen that behaviour previously, but I didn't try to debug it yet."
1827332,2019-05-21 09:48:35 UTC,"Did your second url https://feeds.fireside.fm/linuxunplugged/rss works for you?
If i add this i get linux unplugged in the podcast overview but without any informations"
1827335,2019-06-26 11:04:40 UTC,"Hello,"
1827335,2019-06-25 05:40:05 UTC,"------- Comment From <email address hidden> 2019-06-25 01:36 EDT-------
Closing this bug as its not a kernel issue."
1827335,2019-06-24 13:55:07 UTC,Based on my debugging as well as confirmation from IBM this appears to be a hardware issue that triggers the firmware to offline faulty cores. This is not a kernel issue so closing this bug as invalid.
1827335,2019-06-20 20:59:50 UTC,This isn't a kernel issue - I don't have an answer on the why for being forced offline but it's the not a kernel bug.
1827335,2019-05-21 14:10:59 UTC,Ran plc -b bmc on baltar and the files generated at included in this tar file.
1827335,2019-05-20 13:56:35 UTC,Status update: we believe that the off-lined cores are being intentionally forced off-line by the f/w after f/w tests have determined that the some cores are faulty. Waiting on IBM to confirm this interpretation.
1827335,2019-05-13 13:10:57 UTC,"------- Comment From <email address hidden> 2019-05-13 08:59 EDT-------
*** Bug 177393 has been marked as a duplicate of this bug. ***"
1827335,2019-05-13 13:10:35 UTC,"ubuntu@baltar:~$ sudo opal-gard list
 ID       | Error    | Type       | Path
-----------------------------------------------------------------------
 00000001 | 90000012 | Predictive | /Sys0/Node0/Proc1/EQ5/EX1/Core1
======================================================================="
1827335,2019-05-10 21:39:48 UTC,"------- Comment From <email address hidden> 2019-05-10 17:33 EDT-------
From the opal-utils package can you try:  sudo opal-gard list?  I think if there's something there you can use opal-gard show to get more details."
1827335,2019-05-08 14:24:10 UTC,Po-Hsu Lin (cypressyew) are you able to confirm that the issue can no longer be reproduced now that the firmware has been updated to the latest GA version?
1827335,2019-05-10 14:36:03 UTC,"Po-Hsu Lin, could you please tell me the release and the kernel version used?"
1827335,2019-05-10 08:36:23 UTC,"Hello,"
1827335,2019-05-08 10:59:45 UTC,"------- Comment From <email address hidden> 2019-05-08 06:52 EDT-------
(In reply to comment #17)

> upgraded the firmware on dradis to P9DSU20190404_IBM_prod_sign.pnor and
> tested with bionic and disco and the issue does not reproduce. Marking this
> bug as fix-committed, and if you are able to reproduce this again please
> re-open this bug.
"
1827335,2019-05-06 21:16:51 UTC,"upgraded the firmware on dradis to P9DSU20190404_IBM_prod_sign.pnor and tested with bionic and disco and the issue does not reproduce. Marking this bug as fix-committed, and if you are able to reproduce this again please re-open this bug."
1827335,2019-05-06 13:38:57 UTC,Waiting for a firmware update from IBM - hence set to Incomplete.
1827335,2019-05-02 15:17:26 UTC,"The pnor firmware that we have on our bostons are backlevel and needs to be upgraded. We have production and development level hardware, and when we performed a firmware upgrade we ran into issues related to secure boot. I will work with IBM (Michael) and get these systems upgraded to the latest firmware levels."
1827335,2019-05-02 07:30:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827335,2019-05-02 07:18:07 UTC,This issue can be reproduced with 4.15 Bionic as well.
1827335,2019-05-10 15:34:40 UTC,== From the BMC web UI ==
1827340,2020-04-02 21:00:11 UTC,"Hello,"
1827340,2020-04-21 20:25:54 UTC,"By the way, just in the mean time there is an init script for swift-container-sharder in Ussuri."
1827340,2020-04-03 15:13:55 UTC,"> The swift package in Debian has already moved to systemd though, and they
> went with a generated approach. To see what they did, pull-debian-source
> swift and take a look at the debian/*init.in files and debian/rules
> override_dh_installinit, override_dh_installsystemd.
"
1827340,2020-04-03 14:06:11 UTC,"Dan / Corey,"
1827340,2020-06-26 16:37:06 UTC,This bug was fixed in the package swift - 2.25.0-0ubuntu3
1827340,2019-06-13 11:42:17 UTC,"Hi Mathew,"
1827340,2020-04-21 20:27:59 UTC,I'm going to change the topic of this bug to focus on switch to systemd init.
1827340,2019-05-14 16:01:03 UTC,"Hi Bryan,"
1827340,2019-05-14 16:48:21 UTC,"Hi Tytus,"
1827340,2019-05-06 16:40:22 UTC,Patch attached
1827340,2019-05-06 20:25:28 UTC,"The attachment ""lp1827340.patch"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1827340,2020-04-03 13:20:23 UTC,"Hi Tytus and Dan,"
1827340,2019-05-13 11:19:03 UTC,I agree that it reveals a deeper issue. Would you suggest to remove all old Upstart / System V files (for all Swift services) and replace them with Systemd files?
1827340,2019-05-11 19:01:23 UTC,I don't see the point in enabling Upstart (or sysv init.d jobs) at this point - unless I really don't understand how this will be used Upstart jobs won't do anything on modern releases of Ubuntu.
1827340,2019-05-13 23:16:24 UTC,"Yea, I'd be for going systemd unit files only.  They will always take precedence on 18.04+, so might as well only provide them."
1827354,2019-05-02 16:34:08 UTC,Thank you for your bug report. Where is that error reported. Could you take a screenshot showing the issue?
1827354,2019-05-03 01:53:54 UTC,"When you get the ""error"" dialog that means something crashed, so..."
1827354,2019-05-03 02:44:31 UTC,"Hi Daniel
I can look tonight.
David"
1827354,2019-05-05 02:57:40 UTC,Step 2 provided the following report:
1827354,2019-05-06 01:49:35 UTC,Thanks.
1827354,2019-05-06 01:50:31 UTC,Unfortunately we are unable to debug it for some reason. So this bug report remains incomplete until/unless another such crash report comes in and we can debug that.
1827354,2019-07-05 04:18:05 UTC,[Expired for aptdaemon (Ubuntu) because there has been no activity for 60 days.]
1827356,2019-05-30 13:35:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662218"
1827356,2019-05-30 13:33:28 UTC,A new PR opened as agreed offline with Alex:
1827356,2019-05-08 12:36:03 UTC,"TBH, I am not happy with the quality of the patches I created, so any feedback from the community would be much appreciated."
1827356,2019-05-08 12:31:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657786"
1827356,2019-05-08 12:35:17 UTC,PR for charm-helpers:
1827356,2019-05-29 08:52:17 UTC,"Change abandoned by Tytus Kurek (<email address hidden>) on branch: master
Review: https://review.opendev.org/657786
Reason: Abandoning as per the discussion."
1827357,2019-05-08 22:55:19 UTC,"Hello Dimitri, or anyone else affected,"
1827357,2019-05-09 23:58:52 UTC,"# mount ./bionic-live-server-amd64.iso /mnt/
# cat /mnt/.disk/casper-uuid-generic
ed387af7-7c8f-4d98-8bca-4f8fbcabb0c8
# cat /mnt/.disk/casper-uuid-generic-hwe
6e6d655c-f35b-4361-9b5d-13bea0bbfb1b
# cd $(mktemp -d)
# unmkinitramfs /mnt/casper/initrd .
# cat main/conf/uuid.conf
ed387af7-7c8f-4d98-8bca-4f8fbcabb0c8
# unmkinitramfs /mnt/casper/hwe-initrd .
# cat main/conf/uuid.conf
6e6d655c-f35b-4361-9b5d-13bea0bbfb1b"
1827357,2019-05-10 00:00:26 UTC,booting with a black screen with the first line of text that appears is the getty tty1 message.
1827357,2019-05-10 00:10:58 UTC,"Above two things are tested with:
Ubuntu-Server 18.04.2 LTS ""Bionic Beaver"" - Beta amd64 (20190509)"
1827357,2019-05-10 10:14:33 UTC,"Tested
Ubuntu-Server 18.04.2 LTS ""Bionic Beaver"" - Beta ppc64el (20190510)"
1827357,2019-05-14 09:03:51 UTC,This bug was fixed in the package livecd-rootfs - 2.525.23
1827357,2019-05-14 09:03:57 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827362,2019-05-03 14:27:09 UTC,try a lubuntu 18.04 as a test?
1827362,2019-05-03 14:52:12 UTC,"Good idea, thanks!"
1827362,2019-05-02 11:08:54 UTC,"Ubuntu 14.04 is end of life, please install a supported version from https://www.ubuntu.com/#download"
1827362,2019-05-02 11:00:07 UTC,This change was made by a bot.
1827362,2019-05-03 13:34:39 UTC,"Upps,but the new ubuntu will run is such an old computer?"
1827363,2019-05-13 09:42:39 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658777"
1827363,2019-05-21 07:45:53 UTC,"Reviewed:  https://review.opendev.org/658777
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=94bc403078b1e5d2cddc697fc59b7f1d2d8a6045
Submitter: Zuul
Branch:    master"
1827363,2019-09-06 11:18:12 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/680665"
1827363,2019-09-06 11:18:37 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/680666"
1827363,2019-09-10 12:23:46 UTC,"Reviewed:  https://review.opendev.org/680666
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e3133d8ae9d5fdd94da024343ba8edde7cb4b63c
Submitter: Zuul
Branch:    stable/rocky"
1827363,2019-09-11 04:49:09 UTC,"Reviewed:  https://review.opendev.org/680665
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=677d1f5d03718b669b03f4d8c17f75ae00109304
Submitter: Zuul
Branch:    stable/stein"
1827363,2019-09-19 10:13:52 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1827363,2019-10-22 19:44:51 UTC,This issue was fixed in the openstack/neutron 14.0.3 release.
1827363,2019-10-22 19:53:00 UTC,This issue was fixed in the openstack/neutron 13.0.5 release.
1827363,2019-05-13 09:46:52 UTC,"In the second case, the filters are hard coded, and not limit is used. I think it's safe not to handle that."
1827364,2019-05-02 12:30:15 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1827364,2019-05-02 20:49:33 UTC,"According to the stack trace, it probably comes from this package, but it might actually be related to mono, not gstreamer"
1827366,2019-06-21 13:46:09 UTC,This issue was fixed in the openstack/python-tripleoclient 10.7.0 release.
1827366,2019-06-07 19:28:54 UTC,This issue was fixed in the openstack/python-tripleoclient 12.0.0 release.
1827366,2019-07-05 12:50:15 UTC,This issue was fixed in the openstack/python-tripleoclient 11.5.0 release.
1827366,2019-06-21 15:24:05 UTC,This issue was fixed in the openstack/python-tripleoclient 9.3.0 release.
1827366,2019-05-27 16:46:48 UTC,"Reviewed:  https://review.opendev.org/660565
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=901074e2b50ae4e424bd63cc9c4f23ac108cbe29
Submitter: Zuul
Branch:    stable/queens"
1827366,2019-05-20 08:26:27 UTC,"Reviewed:  https://review.opendev.org/656765
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=1fee54b9be6e877040a7d62183d72a35948767e0
Submitter: Zuul
Branch:    master"
1827366,2019-05-21 19:19:09 UTC,"Reviewed:  https://review.opendev.org/660300
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=ef8d2a16323af17a43acc04d0079decb82e23563
Submitter: Zuul
Branch:    stable/rocky"
1827366,2019-05-02 11:41:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656765"
1827366,2019-05-20 09:17:55 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660058"
1827366,2019-05-22 05:56:49 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/660565"
1827366,2019-05-21 08:58:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/660300"
1827366,2019-05-20 16:38:11 UTC,"Reviewed:  https://review.opendev.org/660058
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=a55573f20a14245526b3abd430754069751e1382
Submitter: Zuul
Branch:    stable/stein"
1827367,2019-05-03 09:22:32 UTC,"Hi Hadmut,
in rare cases where security maintenance is unbearable without upgrading this is done by the security team. Otherwise as you suggested this would be a package for backports pocket, but that is mostly a community effort."
1827367,2020-02-21 04:10:55 UTC,"3.6 is EOL since 31 May 2018.
3.7 is EOL'ing in 31 March 2020"
1827367,2020-02-21 15:45:46 UTC,"Discussion has been moved here:
https://bugs.launchpad.net/bionic-backports/+bug/1864212"
1827367,2020-07-15 16:51:25 UTC,"Hi Eric, should this LP be marked as duplicate for https://bugs.launchpad.net/bionic-backports/+bug/1864212 ? Thanks!"
1827367,2020-07-15 17:06:20 UTC,"@gpiccoli,"
1827368,2019-06-10 10:40:08 UTC,https://review.opendev.org/#/c/663868/ attempts to address this issue.
1827369,2020-06-02 16:56:56 UTC,This issue is also impacting me.
1827369,2020-02-29 21:54:40 UTC,"Hate to ""bump"" bugs, but it's been quite a while and it seems I still can't use EdDSA keys."
1827369,2020-02-03 10:08:18 UTC,"To people who might be inclined to mark this as a duplicate: please note that this is not a duplicate of bug 907675.  OpenPGP keys are not SSH keys, and the code involved in handling them is completely separate."
1827369,2019-05-02 12:09:20 UTC,over on https://answers.launchpad.net/launchpad/+question/680583  @cjwatson wrote:
1827372,2019-05-03 02:01:37 UTC,"Ah this is the bug about searchdomains. You can workaround it by not setting any searchdomains and configuring later, or switching to tty2 and running ""sudo snap refresh subiquity""."
1827375,2019-05-16 19:27:19 UTC,"Thanks Lorenzo,"
1827376,2019-05-02 13:31:33 UTC,"these stack buffer overflows do not appear to affect the other instances tested on aws/arm64, a1.large/a1.medium"
1827376,2019-09-19 09:12:29 UTC,The stress bad-altstack bug was fixed with bug: https://bugs.launchpad.net/ubuntu/+source/linux-aws-hwe/+bug/1830856 - commit https://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=dcd242164cbf6402154813d2fd148f6a73bda2a7
1827376,2019-09-19 12:43:04 UTC,"So I think base one this fact and combined with the procfs / sysfs (1839461) report, this can be marked as dup?"
1827376,2019-09-19 13:17:14 UTC,The sysfs bug was fixed with commit: https://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=05c32aac8224ce74e0de717beb0b3c4dffc11134
1827376,2019-09-19 13:20:39 UTC,Exercising /proc/bus/pci/0000:00/00.0 seems to hang the arm64 instance
1827376,2019-09-19 14:41:10 UTC,"I've disabled the /proc/bus/pci exercising for ARM64, commit: https://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=255b993a6e1df4a7ef3d78c477cf537c94c8ad2c"
1827376,2019-09-19 14:42:24 UTC,I've disabled the bad buffer I/O on /proc to fix SEGFAULT issues on arm64: https://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=25b4bbf4862cef025c165055ffeb38aff4d61768
1827376,2019-09-19 14:42:46 UTC,"@Sam, do you mind re-testing this to see if this now passes the tests"
1827376,2019-09-19 20:35:53 UTC,"Checked with AWS Disco ARM64, instance a1.2xlarge, kernel aws : 5.0.0-1017.19 : arm64"
1827378,2019-06-18 19:26:15 UTC,We have no StarlingX user requests at this time to support the HPE 3PAR storage backend in the stx2.0 timeframe.  As such removing the stx.2.0 tag and leaving this LP in our backlog.
1827378,2019-05-08 20:01:24 UTC,"Marking as release gating for now given this was supported in the previous stx release. As the storage prime, Frank Miller can decide if this support is no longer needed."
1827379,2019-05-02 14:30:07 UTC,This change was made by a bot.
1827379,2019-05-03 02:40:21 UTC,"Hello,"
1827379,2019-07-02 04:17:43 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827382,2019-05-03 09:57:37 UTC,"Fix proposed to branch: 9.0
Change author: Denis V. Meltsaykin <email address hidden>
Review: https://review.fuel-infra.org/41279"
1827382,2019-05-06 15:33:18 UTC,"Reviewed: https://review.fuel-infra.org/41279
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0"
1827382,2019-05-24 15:48:19 UTC,"Verified.
root@node-1:~# apt-cache policy libvirt-bin
libvirt-bin:
  Installed: (none)
  Candidate: 1.3.1-1ubuntu10.25~u14.04+mos1
  Version table:
     1.3.1-1ubuntu10.25~u14.04+mos1 0
       1050 http://eu.mirror.fuel-infra.org/mos-repos/ubuntu/snapshots/9.0-2019-05-22-104320/ mos9.0-proposed/main amd64 Packages
     1.3.1-1ubuntu10.19~u14.04+mos3 0
       1050 http://eu.mirror.fuel-infra.org/mos-repos/ubuntu/snapshots/9.0-2019-05-22-104320/ mos9.0-updates/main amd64 Packages
       1050 http://mirror.fuel-infra.org/mos-repos/ubuntu/9.2/ mos9.0-updates/main amd64 Packages
     1.2.9.3-9~u14.04+mos10 0
       1050 http://10.109.0.2:8080/mitaka-9.0/ubuntu/x86_64/ mos9.0/main amd64 Packages
     1.2.2-0ubuntu13.1.28 0
       1001 http://eu.mirror.fuel-infra.org/pkgs/snapshots/ubuntu-2019-05-24-000000/ trusty-updates/main amd64 Packages
       1001 http://eu.mirror.fuel-infra.org/pkgs/snapshots/ubuntu-2019-05-24-000000/ trusty-security/main amd64 Packages
     1.2.2-0ubuntu13 0
       1001 http://eu.mirror.fuel-infra.org/pkgs/snapshots/ubuntu-2019-05-24-000000/ trusty/main amd64 Packages"
1827382,2019-05-24 15:53:19 UTC,"apt-cache policy libvirt-bin
libvirt-bin:
  Installed: 1.3.1-1ubuntu10.25~u14.04+mos1
  Candidate: 1.3.1-1ubuntu10.25~u14.04+mos1
  Version table:
 *** 1.3.1-1ubuntu10.25~u14.04+mos1 0
       1050 http://eu.mirror.fuel-infra.org/mos-repos/ubuntu/snapshots/9.0-2019-05-22-104320/ mos9.0-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1.3.1-1ubuntu10.19~u14.04+mos3 0
       1050 http://eu.mirror.fuel-infra.org/mos-repos/ubuntu/snapshots/9.0-2019-05-22-104320/ mos9.0-updates/main amd64 Packages
       1050 http://mirror.fuel-infra.org/mos-repos/ubuntu/9.2/ mos9.0-updates/main amd64 Packages
     1.2.9.3-9~u14.04+mos10 0
       1050 http://10.109.0.2:8080/mitaka-9.0/ubuntu/x86_64/ mos9.0/main amd64 Packages
     1.2.2-0ubuntu13.1.28 0
       1001 http://eu.mirror.fuel-infra.org/pkgs/snapshots/ubuntu-2019-05-24-000000/ trusty-updates/main amd64 Packages
       1001 http://eu.mirror.fuel-infra.org/pkgs/snapshots/ubuntu-2019-05-24-000000/ trusty-security/main amd64 Packages
     1.2.2-0ubuntu13 0
       1001 http://eu.mirror.fuel-infra.org/pkgs/snapshots/ubuntu-2019-05-24-000000/ trusty/main amd64 Packages"
1827383,2020-05-18 15:32:06 UTC,"Spotted on 5.0.0-1037.38-gke, only with f1-micro instance."
1827384,2019-05-02 22:28:50 UTC,"The release upgrader does not support the ""deb mirror"" style entries you have in your /etc/apt/sources.list file. You'll need to switch to an http/https type of entry for the release upgrade process to work. Thanks!"
1827384,2019-07-02 04:17:41 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1827385,2019-05-02 17:30:41 UTC,"@James, the incorrect paths may have been left over from previous installs.  It's best to remove them unless you have a specific reason to use them.  With the latest windows installers, everything should work just fine without any kicad environment variables set."
1827385,2019-07-02 04:17:37 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1827386,2019-05-25 20:01:43 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827389,2019-05-27 17:37:35 UTC,Is this issue reproducible with more recent loads?
1827389,2019-05-28 17:54:25 UTC,"Yes, with latest iso its working fine without any issue.
I have reboot all nodes at a time and come up with available state."
1827389,2019-05-28 18:24:30 UTC,"Thanks Krishna for confirming.
Closing as the issue is no longer reproducible with more recent loads."
1827391,2019-05-12 22:52:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827392,2019-06-05 21:11:01 UTC,"Additionally, in this same vein it would be very useful to be able to specify arguments with "":"" in them, i.e. to specify the address to connect to for another app in the same snap, we need to do this:"
1827394,2020-02-01 02:22:04 UTC,"Reviewed:  https://review.opendev.org/656812
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=0606f404fe92a3c56014feba55069a206ddb1cc8
Submitter: Zuul
Branch:    master"
1827394,2020-03-18 11:57:27 UTC,"Fix proposed to branch: feature/losf
Review: https://review.opendev.org/713632"
1827394,2020-03-18 16:18:21 UTC,"Reviewed:  https://review.opendev.org/713632
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=79bd2e59e5c15ee84814ec1c4f0893176ba79412
Submitter: Zuul
Branch:    feature/losf"
1827395,2019-08-09 21:01:34 UTC,Fixed by https://review.opendev.org/#/c/656813/
1827396,2019-06-14 12:59:46 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827397,2020-04-21 19:24:50 UTC,"About logging the connection failures, python-memcached library is not using logging library, it simply does a sys.stderr.write()[0] if the debug=1 is passed when instantiating the client[1]"
1827397,2020-04-28 12:23:05 UTC,Did some research into this and specificlaly why nova gets so hung up rather than just timing out. A few findings:
1827397,2019-05-03 06:37:10 UTC,"This ""known issue"" degraded a charm-upgraded Cloud considerably. Because of haproxy-*-timeout, ""openstack service list"" (and the same via Horizon) aborted the connection before finishing. And there was a point where no logs identified this as an issue."
1827397,2019-05-03 06:38:36 UTC,"Cloud is 19.04, xenial-queens."
1827400,2019-07-02 04:17:38 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1827400,2019-05-02 22:18:46 UTC,"Hello, thanks for update on 5.1.2, but the problem seems to be still here.."
1827400,2019-05-02 17:33:46 UTC,Does this occur in 5.1.2?
1827401,2019-10-14 10:05:16 UTC,This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.2
1827401,2019-10-11 10:47:58 UTC,Verified for 3.28.4-0ubuntu18.04.2
1827401,2019-09-17 03:28:56 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1827401,2019-08-05 08:03:29 UTC,This bug was fixed in the package mutter - 3.32.2+git20190711-2ubuntu1~19.04.1
1827401,2019-06-27 17:15:10 UTC,This bug was fixed in the package mutter - 3.32.2+git20190626-1ubuntu1
1827401,2019-07-29 23:53:28 UTC,3.32.2+ versions...
1827401,2019-07-29 23:52:55 UTC,"No crash reported for any 3.32.x version, so we can consider this fixed"
1827401,2019-07-29 15:48:05 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1827401,2019-07-02 17:54:26 UTC,"Hello errors.ubuntu.com, or anyone else affected,"
1827401,2019-08-05 07:53:34 UTC,"The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827402,2019-05-08 20:08:31 UTC,Marking as release gating. System doesn't recover from a dead office recovery (power outage) type of test and goes into split brain.
1827402,2019-07-05 20:21:40 UTC,"The issue is not reproducible in latest build. Close the issue.
###
### StarlingX
###     Built from master
###"
1827402,2019-07-22 13:40:36 UTC,"This issue has not been seen either by PV or design in recent passed.
Removing the stx.retestneeded tag - this issue should be considered as not reproducible."
1827407,2019-05-02 18:32:24 UTC,I'd like to add that the glitch appears in right clicking with two fingers at the same time as well.
1827407,2019-05-03 04:30:28 UTC,"It's likely caused by the kernel. You should have some older kernel versions installed, but if not, you can install them via 'apt install linux-image-4.15.0-NN-generic' where NN is a number."
1827407,2019-05-03 04:31:31 UTC,..and testing an older kernel should verify if it's a kernel bug or not
1827407,2019-05-03 06:13:52 UTC,"Hey,"
1827407,2019-05-03 06:27:18 UTC,"if the boot menu doesn't show up, hit esc when the bios info screen disappears"
1827407,2019-05-06 17:28:27 UTC,"Moi,"
1827407,2019-05-14 13:13:55 UTC,English only here ;)
1827411,2020-06-18 10:01:47 UTC,This bug was fixed in the package indicator-appmenu - 15.02.0+20.10.20200617.2-0ubuntu1
1827411,2019-05-06 13:48:24 UTC,"Actually it's nor really related to nemo, it's happening since the split of nautilus-desktop as a separate binary from nautilus. Bamf somehow not considering desktop window as valid bamf window (see https://paste.ubuntu.com/p/wz32KF7Kqx/). As a result when indicator-appmenu tries to track menu it fails. We could just simply ignore tracking menus for desktop_windows for now."
1827412,2019-11-06 01:45:47 UTC,Fixed by https://github.com/openstack/swift/commit/6008b0a
1827415,2020-11-09 13:48:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827415,2020-11-10 02:18:36 UTC,Thank you for reporting this bug to Ubuntu.
1827415,2021-01-09 04:17:53 UTC,[Expired for pcmanfm-qt (Ubuntu) because there has been no activity for 60 days.]
1827415,2021-01-11 19:39:35 UTC,"Actually, I can confirm this in the latest daily."
1827417,2019-09-13 04:17:33 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827417,2019-09-13 04:17:31 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1827417,2019-07-15 04:08:47 UTC,Something like this http://cdimages.ubuntu.com/lubuntu/daily-live/current/?
1827417,2019-07-03 07:49:36 UTC,"Hello, thank You for reply,
I can try with new compilation during weekend,
but as my machine is quite old can I try with one of the older
/lighter/  LTS desktop (or would it be nonsense  in case of this issue)?
I.e Lubuntu 16.04 or Xubuntu 16.04 ?"
1827417,2019-07-03 05:41:05 UTC,Sorry for the late reply.
1827417,2019-07-03 04:17:33 UTC,[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]
1827417,2019-07-03 04:17:30 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827417,2019-05-03 10:28:36 UTC,apport information
1827417,2019-05-03 10:28:15 UTC,apport information
1827417,2019-05-03 10:28:03 UTC,apport information
1827417,2019-05-03 10:27:12 UTC,apport information
1827417,2019-05-03 10:27:36 UTC,apport information
1827417,2019-05-03 10:27:51 UTC,apport information
1827417,2019-05-03 01:58:23 UTC,Thanks for the bug report.
1827417,2019-05-03 10:26:24 UTC,apport information
1827417,2019-05-03 10:26:29 UTC,apport information
1827417,2019-05-03 10:26:33 UTC,apport information
1827417,2019-05-03 10:26:51 UTC,apport information
1827417,2019-05-03 10:27:16 UTC,apport information
1827417,2019-05-03 10:27:28 UTC,apport information
1827417,2019-05-03 10:27:32 UTC,apport information
1827417,2019-05-03 10:26:48 UTC,apport information
1827418,2019-05-16 23:33:59 UTC,"Reviewed:  https://review.opendev.org/656913
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8f6939b4f3651c9cd0609fd5c2960681f52dd47f
Submitter: Zuul
Branch:    master"
1827418,2019-05-17 06:56:05 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/659724"
1827418,2019-05-20 15:26:41 UTC,"Reviewed:  https://review.opendev.org/659724
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9fc95ca51229cd5f7be23356f62549cad062b479
Submitter: Zuul
Branch:    stable/stein"
1827418,2019-07-01 02:49:25 UTC,This issue was fixed in the openstack/neutron 14.0.2 release.
1827418,2019-09-19 10:13:56 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1827418,2019-05-03 02:36:57 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656913"
1827419,2019-05-02 21:36:39 UTC,"Thank you for your bug report. The desktop is rendered by a new component gnome-shell-extension-desktop-icons , reassigning there."
1827419,2019-05-02 21:39:59 UTC,"The issue should also be reported upstream on https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues , it would be nice if you could do that"
1827419,2019-05-04 03:03:12 UTC,Reported upstream.
1827419,2019-05-06 07:58:32 UTC,"Thanks for sending it upstream. Yes, the move to that new codebase is unfortunate and have backdraws but nautilus upstream didn't want to consider it any other way and we couldn't stick back to an old nautilus version for ever in ubuntu :-/"
1827420,2019-05-13 21:33:07 UTC,We should add this as well as the other quota model whiteboard from https://review.opendev.org/441203 to somewhere in our documentation.
1827421,2021-01-24 07:05:38 UTC,I also get this on Lubuntu 21.04 but only when I first open the menu.
1827424,2019-05-03 16:52:47 UTC,"Here is the reweight card. There is also a customize card that starts the initial weights. which were the same as the initial launch.
Thanks."
1827424,2019-05-02 21:48:28 UTC,"Hi,"
1827424,2019-05-13 20:32:45 UTC,"That did the trick!
Problem solved. Thanks for your help.
Kevin"
1827424,2019-05-11 22:13:02 UTC,"So looks like that
1) your script write a file: makegrid.dat which should contains the command
2) the script does not use the official scripting interface
The line:
cat makegrid.dat | ./bin/generate_events -n pilotrun
Should be replaced by
./bin/amcatnlo makegrid.dat
(and depending of the content of makegrid.dat, to modify that file to add at the begining the line launch -n pilotrun)"
1827424,2019-05-11 21:34:17 UTC,"Ah, well, that's one problem. I'm not quite sure how the gridpack text files directly translate to commands into madgraph.
A script is run which unpacks and installs madgraph, and takes input from text files in place of interactive commands.
The script isn't complicated, but would probably make more sense if I understood madgraph better."
1827424,2019-05-11 18:50:59 UTC,"HI,"
1827424,2019-05-10 18:46:23 UTC,"Okay, so it seems that running interactively on a desktop doesn't cause problems, but the gridpack does.
Here's something else I noticed in the output file of the gridpack:
============================================================================================
Using default text editor ""vi"". Set another one in ./input/mg5_configuration.txt
No valid eps viewer found. Please set in ./input/mg5_configuration.txt
No valid web browser found. Please set in ./input/mg5_configuration.txt
Plugin PLUGIN.CMS_CLUSTER has marked as NOT being validated with this version.
It has been validated for the last time with version: 2.6.0
INFO: cluster handling will be done with PLUGIN: CMS_CLUSTER
INFO: cluster handling will be done with PLUGIN: CMS_CLUSTER
launch -n pilotrun
The following switches determine which operations are executed:
 1 Perturbative order of the calculation:                               order=NLO
 2 Fixed order (no event generation and no MC@[N]LO matching):    fixed_order=OFF
 3 Shower the generated events:                                        shower=ON
 4 Decay particles with the MadSpin module:                           madspin=ON
 5 Add weights to the events based on changing model parameters:     reweight=ON
 6 Run MadAnalysis5 on the events generated:                     madanalysis5=Not installed
  Either type the switch number (1 to 6) to change its default setting,
  or set any switch explicitly (e.g. type 'order=LO' at the prompt)
  Type '0', 'auto', 'done' or just press enter when you are done.
 [0, 1, 2, 3, 4, 5, auto, done, order=LO, ... ][60s to answer]

>The following switches determine which operations are executed:


 1 Perturbative order of the calculation:                               order=NLO
 2 Fixed order (no event generation and no MC@[N]LO matching):    fixed_order=OFF
 3 Shower the generated events:                                        shower=OFF
 4 Decay particles with the MadSpin module:                           madspin=ON
 5 Add weights to the events based on changing model parameters:     reweight=ON
 6 Run MadAnalysis5 on the events generated:                     madanalysis5=Not installed
  Either type the switch number (1 to 6) to change its default setting,
  or set any switch explicitly (e.g. type 'order=LO' at the prompt)
  Type '0', 'auto', 'done' or just press enter when you are done.
 [0, 1, 2, 3, 4, 5, auto, done, order=LO, ... ][60s to answer]

>The following switches determine which operations are executed:


 1 Perturbative order of the calculation:                               order=NLO
 2 Fixed order (no event generation and no MC@[N]LO matching):    fixed_order=OFF
 3 Shower the generated events:                                        shower=OFF
 4 Decay particles with the MadSpin module:                           madspin=ON
 5 Add weights to the events based on changing model parameters:     reweight=OFF
 6 Run MadAnalysis5 on the events generated:                     madanalysis5=Not installed
  Either type the switch number (1 to 6) to change its default setting,
  or set any switch explicitly (e.g. type 'order=LO' at the prompt)
  Type '0', 'auto', 'done' or just press enter when y..."
1827424,2019-05-09 19:12:49 UTC,"Hi,"
1827424,2019-05-07 19:48:22 UTC,As you want it should not matter.
1827424,2019-05-07 19:24:42 UTC,"Okay, I can run that.
You want me to comment out the add processes for the test?
Thanks, Kevin"
1827424,2019-05-07 13:39:14 UTC,"Hi,"
1827424,2019-05-06 18:32:50 UTC,"Hi,"
1827424,2019-05-06 17:11:11 UTC,"I think the original card and new card identical might have something to do with the fact that in my earlier try, I accidentally reweighted to the central values.
When I corrected this I did not see that warning, although the key error is still there.
I cannot fine a rwgt directory.
Thanks, Kevin"
1827424,2019-05-06 07:10:43 UTC,"Hi,"
1827424,2019-05-09 18:59:16 UTC,"That seemed to work for 2-6-5, if I run it on a desktop.
none of the commands you wrote after launch seemed to have any effect when typed into the magdraph prompt, but I edited the appropriate cards."
1827426,2019-05-28 20:37:54 UTC,This bug was fixed in the package livecd-rootfs - 2.578.4
1827426,2019-05-28 20:38:00 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827426,2019-05-28 20:19:34 UTC,Thanks for pulling this into -proposed.   I will mark this as verification done now after validating image builds.
1827426,2019-05-02 21:21:33 UTC,I've proposed https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/366862 for this issue for master as well as https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/366863 for disco (I'll add an SRU template as well).
1827426,2019-05-02 22:17:45 UTC,I've pushed a commit to each branch to support comments and added them for the changes.
1827426,2019-05-02 22:08:44 UTC,"mwhudson has requested that the make-hooks command be amended to allow comments in series files and these series files have comments added to the effect ""# Ensure livecd.ubuntu-cpc.ext4 is consistent with other targets"""
1827426,2019-05-23 20:42:41 UTC,"Hello Robert, or anyone else affected,"
1827427,2019-07-24 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827427,2019-05-24 09:18:54 UTC,"Please test mainline kernel and see if it helps:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc1/"
1827427,2019-05-24 09:18:18 UTC,[  668.026515] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out
1827427,2019-05-02 22:51:45 UTC,apport information
1827427,2019-05-02 22:51:44 UTC,apport information
1827427,2019-05-02 22:51:43 UTC,apport information
1827427,2019-05-02 22:51:40 UTC,apport information
1827427,2019-05-02 22:51:42 UTC,apport information
1827427,2019-05-02 22:51:38 UTC,apport information
1827427,2019-05-02 22:51:37 UTC,apport information
1827427,2019-05-02 22:51:36 UTC,apport information
1827427,2019-05-02 22:51:35 UTC,apport information
1827427,2019-05-02 22:51:34 UTC,apport information
1827427,2019-05-02 22:51:33 UTC,apport information
1827427,2019-05-02 22:00:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827427,2019-05-02 21:51:14 UTC,"Thank you for your bug report. It does look like rather an hardware/driver/kernel issue than a network-manager one though, reassigning"
1827427,2019-05-02 22:51:39 UTC,apport information
1827428,2020-01-24 09:03:59 UTC,"Since the original bug report was for nvidia on Ubuntu 19.04 and that is end of life as of yesterday, please open a new bug from your affected machine."
1827428,2020-02-04 01:27:01 UTC,"I'm also having this issue on 19.04. Only happens when i'm using 2 screens. the cursor is a duplicate of the real one, ie it hanges to the text select cursor shape when i'm highlighting text, and it changes to the hand-pointer when hovering over a hyperlink."
1827428,2020-03-01 17:02:11 UTC,"Has this bug been re-added somewhere? If so, could someone post a link? I'm experiencing a dead cursor appearing in Ubuntu 19.10. I always run my monitors at 100% scaling and have dual monitors. I am also running an AMD RX Vega 56. I've been running in Wayland. I haven't seen if the issue occurs on X11 or not."
1827428,2020-04-15 07:51:55 UTC,This bug is closed so if you still experience any problems then please open a new one by running:
1827428,2020-03-19 15:38:42 UTC,"I am also having this issue on Fedora 31, Gnome 3.34.4 with a Radeon RX 590 using amdgpu on Wayland."
1827428,2020-03-31 05:51:26 UTC,Ubuntu 18.04 NVidia driver gnome desktop with 2 monitors.
1827428,2020-04-13 20:48:47 UTC,Having this problem in 20.04
1827428,2020-03-07 13:11:15 UTC,This also occurs in Fedora 32 and Xfce 4.14 for me.
1827428,2020-01-15 16:31:40 UTC,"Can confirm the issue on the Lenovo Flex Ideapad laptop.
Ubuntu 19.10
AMD Ryzen 5 3500U Mobile Processor with Radeon Vega 8 Graphics.
Fractional Scaling: 125%
Both X11 and Wayland.
Unscaled works fine. Hope this get resolved soon. Thanks."
1827428,2020-01-06 14:52:58 UTC,Also FWIW it also happens with amdgpu so I think it's probably mutter and not nvidia
1827428,2020-01-06 14:52:15 UTC,Been experiencing this on multiple distributions but haven't been able to find an upstream bug report
1827428,2019-10-23 04:06:03 UTC,I am experiencing this after upgrading to 19.10 and enabling fractional scaling on wayland.  The extra cursor appears at 125%/150% scaling and disappears at 100% scaling.
1827428,2019-08-06 08:14:33 UTC,A bit more detail to reproduce this that I think was missed out before:
1827428,2019-08-06 07:25:05 UTC,"My bug got marked a duplicate of this one but with the latest change that might be wrong: It affected me on a machine with AMD graphics, not nVidia. BTW I recently tried it again on the offchance it had been fixed since (by re-enabling the xrandr scaling setting), and it had not. Also not fixed on 19.10 (which tbh is barely advanced from 19.04 at this stage)."
1827428,2019-05-16 01:33:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827428,2019-05-03 02:08:50 UTC,This sounds like a bug I heard reported elsewhere recently but I can't find any such previous reports today.
1827428,2019-05-02 22:14:28 UTC,"> What desktop environment do you use?
"
1827428,2019-05-02 21:49:49 UTC,Thank you for your bug report. What desktop environment do you use? Could you take a screenshot or screencast showing the issue?
1827428,2020-01-10 07:25:00 UTC,"Another with this problem here.
I have Radeon HD 7850 - no nvidia - also scaling at 125%.
Unscaled is OK."
1827429,2019-08-22 19:04:20 UTC,"Removing packages from eoan:
 musica 2.30-0ubuntu1 in eoan
  musica 2.30-0ubuntu1 in eoan amd64
  musica 2.30-0ubuntu1 in eoan arm64
  musica 2.30-0ubuntu1 in eoan armhf
  musica 2.30-0ubuntu1 in eoan i386
  musica 2.30-0ubuntu1 in eoan ppc64el
  musica 2.30-0ubuntu1 in eoan s390x
Comment: Ubuntu-specific, unmaintained, depends on obsolete jquery-jplayer; LP: #1827429
1 package successfully removed."
1827431,2019-05-02 22:52:48 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/656898"
1827431,2020-03-31 14:39:16 UTC,Hi. Is anyone working over this?
1827431,2020-04-10 10:11:47 UTC,"Hi Vishaka,"
1827431,2020-04-16 18:25:35 UTC,Thanks Pavlo
1827431,2020-07-15 16:16:06 UTC,"Reviewed:  https://review.opendev.org/656898
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=c9c655a1e1e865a1f4e274c0aaea1749acc8a53b
Submitter: Zuul
Branch:    master"
1827433,2020-09-21 10:36:29 UTC,Thank you for reporting this bug to Ubuntu.
1827433,2020-11-21 04:17:18 UTC,[Expired for pcmanfm-qt (Ubuntu) because there has been no activity for 60 days.]
1827435,2020-04-16 18:28:42 UTC,Thanks Pavlo
1827435,2019-05-03 20:46:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657039"
1827435,2020-03-31 14:53:12 UTC,Hi. Is anyone working over this?
1827435,2020-04-10 10:10:41 UTC,"Hi Vishakha, I've got really distracted as you may see bu the dates :-/"
1827436,2020-02-08 16:52:02 UTC,This also happens on Lubuntu 18.04.04 LTS
1827436,2020-02-08 16:57:05 UTC,"I realized right now, that the chosen executable has to have the executable bit activated, even if it is a shell script or it will not be accepted."
1827436,2020-02-08 22:25:27 UTC,Thank you for reporting this bug to Ubuntu.
1827436,2020-04-09 04:17:25 UTC,[Expired for pcmanfm-qt (Ubuntu) because there has been no activity for 60 days.]
1827436,2020-09-20 20:47:41 UTC,Same happens on Ubuntu 20.04.
1827436,2020-02-08 16:50:55 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827437,2019-05-02 22:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827437,2019-05-16 15:03:59 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1827437,2019-05-16 21:12:27 UTC,"Bionic verification:
(initramfs) cat /proc/version
Linux version 4.15.0-51-generic (buildd@bos02-arm64-037) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #55-Ubuntu SMP Wed May 15 14:27:56 UTC 2019
(initramfs) modprobe -r hisi_sas_v3_hw
[  217.311945] systemd-udevd[1224]: passed device to netlink monitor 0xaaaac0e362f0
[  217.312494] systemd-udevd[1225]: passed device to netlink monitor 0xaaaac0de37d0
[  217.313119] systemd-udevd[842]: passed 182 byte device to netlink monitor 0xaaaac0dc2b40
[  217.313218] systemd-udevd[1225]: passed device to netlink monitor 0xaaaac0de37d0
[  217.313317] systemd-udevd[1226]: passed device to netlink monitor 0xaaaac0dbd710
[  217.313521] systemd-udevd[1227]: passed device to netlink monitor 0xaaaac0dbab80
[  217.313844] systemd-udevd[842]: passed 182 byte device to netlink monitor 0xaaaac0dc2b40
[  217.313884] systemd-udevd[842]: passed 182 byte device to netlink monitor 0xaaaac0dc2b40
[  217.313939] systemd-udevd[1227]: passed device to netlink monitor 0xaaaac0dbab80
[  217.313951] systemd-udevd[1225]: passed device to netlink monitor 0xaaaac0de37d0
(initramfs) modprobe hisis_sas_v3_hw
(initramfs)"
1827437,2019-05-20 14:02:10 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1827437,2019-05-31 16:18:24 UTC,"(initramfs) modprobe -r hisi_sas_v3_hw
[   70.546285] hisi_sas_v3_hw 0000:74:02.0: dev[4:1] is gone
[   70.552479] sd 3:0:1:0: [sdc] Synchronizing SCSI cache
[   70.561963] sd 3:0:1:0: [sdc] Stopping disk
[   71.161605] hisi_sas_v3_hw 0000:74:02.0: dev[3:5] is gone
[   71.168193] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[   71.180633] sd 3:0:0:0: [sdb] Stopping disk
[   71.785586] hisi_sas_v3_hw 0000:74:02.0: dev[2:5] is gone
[   71.794376] hisi_sas_v3_hw 0000:74:02.0: dev[1:2] is gone
(initramfs) cat /proc/version
Linux version 4.18.0-21-generic (buildd@bos02-arm64-052) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #22-Ubuntu SMP Wed May 15 13:14:00 UTC 2019
(initramfs)"
1827437,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1827437,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1827438,2019-06-12 14:41:17 UTC,"Reviewed:  https://review.opendev.org/664831
Committed: https://git.openstack.org/cgit/starlingx/gui/commit/?id=16174140f9afa616a0d6486ba319888c1288413e
Submitter: Zuul
Branch:    master"
1827438,2019-06-12 08:53:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/664831"
1827438,2019-06-11 05:57:29 UTC,Reproduced on 0604 codebase too. debugging.
1827438,2019-06-10 15:14:55 UTC,"I observe the issue still with new ISO:
ISO: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190531T013000Z/outputs/iso/"
1827438,2019-06-05 18:31:22 UTC,Perhaps someone in Cindy's team can take this on. Bruce indicated they have bandwidth
1827438,2019-06-03 14:09:59 UTC,"As discussed with Forrest, he recommends this bug be taken by someone more familiar with the starlingx gui."
1827438,2019-05-08 20:10:53 UTC,Marking as release gating; issue with horizon related to networking config.
1827439,2019-05-02 23:47:08 UTC,Source code reference: serverguide/C/virtualization.xml line 991:
1827439,2019-05-03 20:39:32 UTC,Thanks Doug!
1827440,2020-01-29 05:45:52 UTC,Update: a kernel upgrade solved the mic white noise for me. I had been running a 5.0 kernel. Updating to a 5.4 kernel fixed it.
1827440,2020-01-29 04:43:39 UTC,"Tyler, did you ever find a solution to this? I'm having the same problem with a the same laptop (X1 Carbon 6th gen) running Kubuntu 18.04. The only ""solution"" I've found is to turn off ""internal mic boost"" using alsa-mixer (hit F5 to show all channels, cursor all the way to the right) and keep the mic capture level below 20%. So it works, but far from ideal since the mic is low (but better than making the person on the other end of a call hearing a shitload of white noise that's produced otherwise)."
1827440,2019-05-08 03:37:45 UTC,"Cool, I will try that!"
1827440,2019-05-05 05:01:02 UTC,The sound in the #19 is not that bad.
1827440,2019-05-04 22:55:10 UTC,"Ya, here's a quick wav file I just recorded with arecord."
1827440,2019-05-04 15:01:56 UTC,Could you upload a wav file recorded by internal mic?
1827440,2019-05-03 03:18:03 UTC,apport information
1827440,2019-05-03 03:18:01 UTC,apport information
1827440,2019-05-03 03:17:58 UTC,apport information
1827440,2019-05-03 03:17:56 UTC,apport information
1827440,2019-05-03 03:17:45 UTC,apport information
1827440,2019-05-03 03:17:52 UTC,apport information
1827440,2019-05-03 03:17:54 UTC,apport information
1827440,2019-05-03 02:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827440,2019-05-03 03:17:38 UTC,apport information
1827440,2019-05-03 03:17:40 UTC,apport information
1827440,2019-05-03 03:17:42 UTC,apport information
1827440,2019-05-03 02:11:48 UTC,I wonder if another fix similar to bug 1817263 is required?
1827440,2019-05-03 03:17:46 UTC,apport information
1827440,2019-05-03 03:17:48 UTC,apport information
1827440,2019-05-03 03:17:49 UTC,apport information
1827440,2019-05-03 03:17:51 UTC,apport information
1827442,2020-02-27 04:21:39 UTC,"I reviewed libheif 1.6.1-1 as checked into focal.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability."
1827442,2020-02-26 06:54:18 UTC,"On Wed, Feb 26, 2020 at 04:02:33AM -0000, Seth Arnold wrote:

> Has it been used and found useful?
"
1827442,2020-02-26 04:02:33 UTC,"I've returned to this package, and I'm seeing enough // TODO markers that I'm starting to be concerned that this library implements sufficient functionality to be useful for us. The code that's there mostly looks good, but there's enough markers for ""handle errors"" and ""find out .."" that I'm wondering if enough of this is useful for the things we want it for."
1827442,2020-02-09 19:48:12 UTC,"> Is the libheif package still lintian clean?
"
1827442,2020-01-28 04:27:38 UTC,"Thanks Steve, I'm not sure why I thought the dependencies on libx265-179 and libde265-0 were overlooked. Now that I take another look it all looks pretty normal."
1827442,2020-01-18 19:46:04 UTC,"Seth, I'm not sure how you reached the conclusion that there are ""no install time dependencies declared in the Debian packaging"".  libheif1-1 in focal depends on both libx265-179 and libde265-0."
1827442,2020-01-18 01:54:06 UTC,"Has anyone looked to see if x265 and libde265 are also required to be MIR'd for this package to be useful in its target use? There's no install time dependencies declared in the Debian packaging but it's hard for me to imagine why these libraries would be required at build in order to enable some of the functionality, unless they also influence the runtime behaviour of the library."
1827442,2020-01-18 01:04:18 UTC,Is the libheif package still lintian clean? Using disco's lintian I get the following:
1827442,2019-10-25 01:54:45 UTC,"I forgot I already passed along the coverity results to the libheif team:
https://github.com/strukturag/libheif/issues/128"
1827442,2019-10-24 02:38:00 UTC,"Here's the Coverity results on libheif. The first third of the file is all about example code. It might be nice to get those issues fixed, both to help bring the overall number of findings closer to zero, but more importantly to improve the quality of potential copy-and-paste coding."
1827442,2019-08-03 13:18:48 UTC,"Just a question, I thought build-dependencies need not be in main any more to build packages in main. It was announced some time ago on ubuntu-devel. Am I wrong?"
1827442,2019-09-17 15:37:38 UTC,"Also the Samsung S10 creates HEIF images:
https://r2.community.samsung.com/t5/Galaxy-S/Here-s-how-to-make-Galaxy-S10-camera-photos-take-less-storage/td-p/1304386"
1827442,2019-09-18 15:21:27 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827442,2019-05-06 18:24:57 UTC,"I just noticed via https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg that libde265 wants to pull in:
 - qtbase-opensource-src (qt4)
  - qtchooser
  - double-conversion
  - qtsvg-opensource-src
  - qttranslations-opensource-src
 - libsd1.2
 - *ffmpeg*
  - zeromq3
   - norm
   - libpgm
  - libdc1394-22
  - libbs2b
  - x264
  - lilv
   - sratom
   - serd
   - sord
  - zvbi
  - libva
   - intel-vaapi-driver
   - intel-media-driver
    - intel-gmmlib
   - libset-scalar-perl
  - codec2
  - chromaprint
  - twitter-bootstrap3
  - libgsm
  - crystalhd
  - libopenmpt
  - game-music-emu
  - libvidstab
  - rubberband
  - aom
  - xvidcore
  - openjpeg2
  - libbluray
   - libaacs
    - libbdplus
  - openal-soft
   - sndio
  - shine
  - flite
  - libmysofa
  - libass"
1827442,2019-07-12 08:05:32 UTC,"libde265-0 actually pulls in a lot less dependencies:
https://packages.ubuntu.com/bionic/libde265-0"
1827442,2019-07-18 22:10:40 UTC,"Joachim, thanks for bringing this to my attention.  I've gone ahead and added libde265-examples to the exclusion list for main, and readded the libheif build-dep to imagemagick in order to revisit this MIR."
1827442,2019-05-08 01:51:05 UTC,"Wow, that's a pretty significant chain of deps. Thanks for pruning this one."
1827442,2019-05-03 20:38:06 UTC,"I've had a look, certainly seems fine packaging-wise; but should be looked at by the Security Team."
1827442,2019-08-03 18:20:46 UTC,It's correct that packages do not have to be in main merely for being build dependencies.  But most libraries that are build dependencies are linked against during build and become runtime dependencies.
1827442,2019-09-17 14:38:40 UTC,This MIR keeps imagemagick out of the release pocket in the devel release.
1827442,2019-09-17 15:24:17 UTC,Apparently this is useful for photos from iPhones.
1827442,2019-07-18 23:03:21 UTC,"Thanks Joachim, Steve, I've removed the comment in trello saying this is on hold."
1827443,2019-05-02 23:42:14 UTC,Here's the Traceback:
1827444,2020-07-10 07:38:30 UTC," Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest version of Ubuntu."
1827445,2019-09-23 01:37:09 UTC,"Reviewed:  https://reviews.mahara.org/10368
Committed: https://git.mahara.org/mahara/mahara/commit/4bcd9ee6dbc46237ab680ec85eb84104ab96b4f0
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827445,2019-10-05 16:41:20 UTC,"Reviewed:  https://reviews.mahara.org/10392
Committed: https://git.mahara.org/mahara/mahara/commit/fb37ef6e28a2156efcd35ce3d0a53268b4f93d59
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1827445,2019-10-01 02:36:35 UTC,"Reviewed:  https://reviews.mahara.org/10384
Committed: https://git.mahara.org/mahara/mahara/commit/ca2b5406848c44ab0cd8742f9f68a4cc235d68d6
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827445,2019-09-23 01:35:11 UTC,To test the latest patch (see comment 6):
1827445,2019-10-03 00:52:55 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10392"
1827445,2019-09-20 00:18:38 UTC,"Reviewed:  https://reviews.mahara.org/9950
Committed: https://git.mahara.org/mahara/mahara/commit/3e0cd370e245bd0eb011667430f30df6ab42c4f9
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827445,2019-09-20 00:18:38 UTC,"Reviewed:  https://reviews.mahara.org/10287
Committed: https://git.mahara.org/mahara/mahara/commit/6a26a0c72f6e595187a86befc5418c33276ee5ef
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827445,2019-09-04 01:18:12 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10287"
1827445,2019-05-03 00:13:03 UTC,"Ok, have made patch
https://reviews.mahara.org/#/c/9950/"
1827445,2019-05-03 00:02:32 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9950"
1827445,2019-09-23 00:51:30 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10368"
1827446,2019-05-03 01:19:21 UTC,The issue happens also when I am using lightdm
1827446,2019-05-03 01:39:53 UTC,Laptop Model XPS 15 9560
1827446,2019-06-01 15:02:40 UTC,I am planning to test this command :
1827446,2019-06-04 02:14:10 UTC,I have been able to reset my PCI with the following command:
1827447,2019-05-03 02:38:00 UTC,"One line fix
IsController:       doc.UUID == st.modelTag.Id(),
instead of
IsController:       st.isController(),"
1827447,2019-05-03 02:49:39 UTC,https://github.com/juju/juju/pull/10131
1827447,2019-05-03 02:21:31 UTC,That's weird. Thanks for reporting this.
1827447,2019-05-03 02:35:09 UTC,It's a straight out bug in the modelsummaries method newProcessorFromModelDocs()
1827448,2019-05-16 01:55:19 UTC,Fixed in trunk version 2019.05-204-development
1827451,2019-07-03 13:35:28 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.0.7-0ubuntu0.18.04.7
1827451,2019-06-26 09:01:43 UTC,"Upgraded libreoffice-l10n from 1:6.0.7-0ubuntu0.18.04.6 to 1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the test case passes."
1827451,2019-06-25 16:18:57 UTC,"Hello Ikuya, or anyone else affected,"
1827451,2019-05-23 08:27:14 UTC,This bug was fixed in the package libreoffice - 1:6.1.6-0ubuntu0.18.10.2
1827451,2019-05-24 16:00:20 UTC,"Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.5 to 1:6.0.7-0ubuntu0.18.04.6 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the [Test Case] now passes."
1827451,2019-05-24 15:38:50 UTC,"Upgraded libreoffice from 1:5.1.6~rc2-0ubuntu1~xenial6 to 1:5.1.6~rc2-0ubuntu1~xenial7 from xenial-proposed in a clean and up-to-date xenial amd64 VM, and verified that the [Test Case] now passes."
1827451,2019-05-23 15:00:13 UTC,"Hello Ikuya, or anyone else affected,"
1827451,2019-05-23 14:52:19 UTC,"Hello Ikuya, or anyone else affected,"
1827451,2019-05-23 08:27:45 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.1.6-0ubuntu0.18.10.2
1827451,2019-05-23 08:27:36 UTC,"The verification of the Stable Release Update for libreoffice has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827451,2019-05-21 14:51:35 UTC,"Agreed, thanks for the input Ikuya and Mathieu. With your help, I updated the [Test Case] section of the description. This was before carrying out the verification of this fix in comment #13 of course."
1827451,2019-05-30 10:03:47 UTC,This bug was fixed in the package libreoffice - 1:5.1.6~rc2-0ubuntu1~xenial7
1827451,2019-05-16 17:29:27 UTC,"Upgraded libreoffice from 1:6.1.5-0ubuntu0.18.10.1 to 1:6.1.6-0ubuntu0.18.10.2 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice."
1827451,2019-05-21 14:39:07 UTC,"Ikuya,"
1827451,2019-05-03 04:24:02 UTC,"The attachment ""libreoffice_6.0.7-reiwa-support.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1827451,2019-05-03 08:18:43 UTC,"Note that this patch is in the upcoming 6.1.6 release, which will be SRU'd independently to cosmic when it's out."
1827451,2019-05-09 15:18:07 UTC,"Hello Ikuya, or anyone else affected,"
1827451,2019-05-09 15:19:17 UTC,"Hello Ikuya, or anyone else affected,"
1827451,2019-05-30 08:44:53 UTC,This bug was fixed in the package libreoffice - 1:6.0.7-0ubuntu0.18.04.6
1827451,2019-05-10 09:51:08 UTC,"Upgraded libreoffice to 1:6.1.6-0ubuntu0.18.10.1 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice."
1827451,2019-05-11 17:55:00 UTC,Unfortunately the upgrade from 6.1.5 to 6.1.6 is actually broken. My apologies for the false verification. I will prepare a fix asap.
1827451,2019-05-13 19:02:26 UTC,"Is this really a sufficient test case? It seems to me like there should be extra work put in to making sure the glyphs also appear correctly on date formatting, to show, for example:"
1827451,2019-05-15 23:56:38 UTC,"> Is this really a sufficient test case?
"
1827451,2019-05-16 12:09:55 UTC,"Hello Ikuya, or anyone else affected,"
1827451,2019-05-16 12:10:36 UTC,"Hello Ikuya, or anyone else affected,"
1827452,2020-12-12 16:15:06 UTC,Please test this patch.
1827452,2020-12-15 16:25:22 UTC,Can someone please test it?
1827452,2020-12-15 17:06:34 UTC,Thanks I will test as soon as I get some time (weekend). I have to hook up my shoddy tester USB cable and compile a fresh kernel but in the meantime trying to get business wrapped up before holidays.
1827452,2020-12-22 09:06:23 UTC,Thanks I finally managed to set up the same test cable and give this patch a go.  I still see the same error - third attempt in the trace attached.  I'm still of the opinion that this would need to be fixed in usbcore.
1827452,2021-01-19 05:45:32 UTC,Can someone please test the patch in #23?
1827452,2020-12-23 07:54:22 UTC,"Well, it should."
1827452,2020-12-11 09:02:21 UTC,There it is: https://lore.kernel.org<email address hidden>/
1827452,2021-01-19 09:42:41 UTC,Sorry I've been reluctant to test it since that code block is never even hit during the issue.
1827452,2021-01-19 10:40:58 UTC,I am pretty sure it's called.
1827452,2020-12-22 09:32:30 UTC,"@kaihengfeng
The usb disconnect comes directly via interrupt. Execution doesn't hit uvc_disconnect and this patch has no effect. :/"
1827452,2020-12-11 08:55:34 UTC,Yes this was the original thread.  Alan was helpful and responsive but in the end he suggested I contact the uvcvideo maintainers which I did and got nowhere.
1827452,2020-12-23 07:56:34 UTC,Test take 2.
1827452,2020-12-10 08:13:37 UTC,I shared the stack trace.  Was there a reply somewhere I didn't get?  Is it on lkms?  Link?
1827452,2020-12-10 04:20:19 UTC,The maintainer merely wants to see the stack trace...
1827452,2020-12-09 19:47:28 UTC,"For what it's worth, as a dev who's spent plenty of time hacking the kernel in a prior job, I really appreciate the effort. Hopefully it won't be completely in vain."
1827452,2020-12-09 16:22:36 UTC,Hi latest on this.  I've played with about 50 custom kernel patches here and I can see exactly what happens.  When uvcvideo looks for webcam devices it finds a perfectly healthy idle webcam on the USB hub (even built-in hub).  Then when it starts a stream the webcam obviously requires more power.  I've seen this with multiple webcam vendors and a cheap USB extension cable.
1827452,2020-11-15 09:38:01 UTC,"Update again.
The kernel maintainers have been helpful but prefer NULL checking to be done in the drivers, not in the kernel.  I've explored further with some test builds and it turns out the NULL is actually on the dev config interfaces (usb.c:281 current line).  During initialization the Logitech C920 sometimes unplugs/deactivates itself. Apparently many Logitech models do this if you search the issue - Windows included.  Shame to have such a great quality camera paired with such subpar firmware."
1827452,2020-11-13 03:20:22 UTC,"Hi John,
thanks for the fix!
Let's wait for some good news."
1827452,2020-11-12 10:53:15 UTC,Update on this.  Pretty sure I managed to find the line in the kernel triggering this.  I've submitted a PR to the kernel USB maintainers. Hopefully tested and merged soon.
1827452,2020-11-12 10:05:13 UTC,I know this is closed but I've been having this same issue for months as well.  In fact I tried a different webcam from a different vendor and I see the same behaviour.
1827452,2019-05-03 02:00:07 UTC,This change was made by a bot.
1827452,2019-07-16 04:17:22 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827452,2019-05-16 11:25:51 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-2 kernel[1]."
1827452,2019-05-03 02:01:42 UTC,"To be clear, the line below (taken from the longer log output above) was not due to me physically disconnecting the camera. I disconnected it after capturing the kernel log."
1827452,2020-12-11 03:31:19 UTC,https://<email address hidden>/
1827458,2019-05-03 08:16:27 UTC,Setting to 'incomplete' as min-cluster-size was not changed from 0 to 2 in the HA bundle which is likely the reason why this happened.
1827458,2019-05-03 10:39:07 UTC,Verified with changing min-cluster-size from 0 to 2:
1827459,2019-05-03 04:00:03 UTC,This bug has been reported on the Ubuntu ISO testing tracker.
1827459,2019-05-15 01:20:38 UTC,"19.10 QA-Test on lenovo thinkpad sl510 (c2d-t6570, 2gb ram, i915)"
1827459,2019-06-04 05:40:27 UTC,Xubuntu 19.10 QA-test - following copied from qa-test report comments
1827459,2019-11-16 03:29:53 UTC,"xubuntu 20.04 QA-test on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
usual validate media, boot and main menu doesn't have all icons (none for web browser, terminal emulator or help), ctrl+alt+T doesn't work.."
1827459,2020-02-27 02:46:25 UTC,"xubuntu 20.04 QA-test on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
another box where this issue occurred."
1827459,2020-03-05 10:56:20 UTC,"xubuntu 20.04 QA-test on dell vostro 430 (i7-870, 8gb, nvidia geforce gt 6600 gt), or another box where this occurs
xfsettingsd --replace would restore CTRL+ALT+T to working, along with icons on desktop, and icons on menu.."
1827459,2020-06-19 05:45:28 UTC,"QA-test (live) of Xubuntu groovy/20.10 daily on
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
on boot desktop icons were shadow like, opened menu also has no icons for all.applications, accessories, internet, office, settings & ctrl+alt+T doesn't work..
A terminal opened and `xfsettingsd --replace &` command restored mentioned issues, with CTRL+ALT+T now working."
1827459,2020-11-24 10:40:01 UTC,"QA-test (live) using Xubuntu hirsute daily on
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)"
1827459,2019-11-16 08:05:03 UTC,"xubuntu 20.04 QA-test on lenovo thinkpad sl510 (c2d-t6570, 2gb ram, i915)
another box where this issue occurred."
1827460,2019-05-04 03:30:31 UTC,apport information
1827460,2019-05-04 03:30:39 UTC,apport information
1827460,2019-05-04 03:30:44 UTC,apport information
1827460,2019-05-04 03:30:29 UTC,apport information
1827460,2019-05-04 03:30:08 UTC,apport information
1827460,2019-05-12 13:00:09 UTC,Same behavior on dell precision 7740
1827460,2019-05-12 13:02:58 UTC,UPD: headphones connected to display and sound passed via hdmi cable. Switching the sound source to the analog output and then back to hdmi helps most of the time
1827460,2019-05-28 10:42:34 UTC,Similar to #1829621? Please test the kernel in the bug.
1827460,2019-05-29 03:48:15 UTC,"I backported an i915 patch for glk machines, please remove the workaround of ""probe_mask=1"" (#4) and test this kernel:"
1827460,2019-05-04 03:30:27 UTC,apport information
1827460,2019-05-04 03:33:28 UTC,"Followed ""Ubuntu Kernel Bot"" instructions - running : apport-collect 1827460.  Get error ""dpkg-query: no packages found matching linux""."
1827460,2019-05-04 03:30:26 UTC,apport information
1827460,2019-05-03 04:57:16 UTC,Please refer to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868. Looks like this is a similar bug with that one. They all have geminilake hdmi audio controller.
1827460,2019-05-04 03:30:22 UTC,apport information
1827460,2019-05-03 04:51:57 UTC,"This happens on the grounds that the PC rests with the speakers handicapped and the earphones controlled on. To keep this from happening separate the earphones before putting the machine to rest.
https://www.epsonprintersupport247.com/fix-epson-printer-offline/"
1827460,2019-05-03 05:14:40 UTC,Yes bug 1826868 sounds similar.
1827460,2019-05-03 05:17:10 UTC,Launching with the Kernel 4.15.0.47.50 v4.15.0-47.50 resolves the issue.  The more recent kernel (above this one) has the issue.  Seems the more recent kernel introduces some bug that needs to be fixed.
1827460,2019-05-03 07:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827460,2019-05-03 04:10:20 UTC,I can see a few audio-related error messages in your kernel log. But even if that wasn't true then I would still suggest this is most likely a kernel bug.
1827460,2019-05-04 03:30:13 UTC,apport information
1827460,2019-05-04 03:30:15 UTC,apport information
1827460,2019-05-04 03:30:17 UTC,apport information
1827460,2019-05-04 03:30:19 UTC,apport information
1827460,2019-05-04 03:30:10 UTC,apport information
1827460,2019-05-04 03:30:23 UTC,apport information
1827461,2019-05-03 07:00:47 UTC,Setting to incomplete per Tim's comment in IRC. I will need to reproduce the issue to provide a juju-db dump.
1827461,2019-05-03 07:07:28 UTC,"@Dmitrii Shcherbakov (dmitriis),"
1827461,2019-05-03 07:07:53 UTC,Also this could be related to bug # 1827285
1827461,2019-05-03 11:12:36 UTC,"Hmm, tried the following:"
1827461,2019-05-03 11:21:23 UTC,Attached a mongodump for the comment above (no repro unfortunately).
1827461,2019-10-28 04:17:27 UTC,[Expired for juju because there has been no activity for 60 days.]
1827463,2020-05-13 19:16:43 UTC,"The 4% recommendation is generally accurate for rdb/cephfs. For object storage, this can trend higher when there are huge numbers of small objects."
1827463,2020-06-01 17:43:34 UTC,The Octopus documentation on the recommended `db` sizes notes [0]:
1827463,2020-06-04 13:32:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/733613"
1827464,2019-09-30 16:53:58 UTC,"Fix for this was landed, and check now runs without warnings."
1827465,2020-11-10 00:42:57 UTC,"Additional info: When I changed a vip, I expected that to cause a relation-changed and roll the new VIP through the shared-db relations - however, the config files in Nova didn't change at all."
1827465,2019-05-03 08:22:39 UTC,This might be a symptom caused by LP#1513889. It would be worth testing if a mysql cluster deployed with multiple vips from the start instantiates both or only one of them.
1827465,2019-05-03 10:32:40 UTC,AFAIK this charm never supported multiple VIPs because it was meant to serve on a single network only.
1827467,2019-05-03 07:43:47 UTC,"Thank you for your bug report, it has been reported to Debian as well and seems a side effect of kernel changes, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912748 has some details"
1827467,2019-05-03 07:46:08 UTC,Looks like it was fixed upstream with https://gitlab.com/psmisc/psmisc/commit/1188315c
1827467,2019-05-03 10:18:25 UTC,To which version of psmisc should the patch be backported?
1827467,2019-05-03 10:39:27 UTC,"The current one, 23.2-1"
1827467,2019-05-06 19:07:57 UTC,"I don't think this is fix committed in ubuntu. Eoan still has 23.2-1, and the fix was applied to 23.4, and there are no patches applying that gitlab commit."
1827481,2020-01-24 09:44:51 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1827481,2019-05-07 09:27:13 UTC,"mac has the same feature, and it's very fast,
mac should not write this feature use slow script language like JS."
1827481,2019-05-03 11:10:46 UTC,look at the Lower left quarter，use mouse to click that button.
1827481,2019-05-03 09:06:33 UTC,Yes we know and expect other desktop environments will be faster than Gnome at some things.
1827481,2019-05-03 10:51:10 UTC,"Well, it's still unclear what you call ""show applications"" and how you trigger it. Can you make a screencast of the issue?"
1827481,2019-05-03 08:45:08 UTC,Please also:
1827481,2019-05-03 08:27:01 UTC,"This problem still occurs.
The deepin launcher is written by c++, the gnome launcher is written by js,
c++ is much faster (at least 5 times) than js I think."
1827481,2019-05-03 07:44:12 UTC,This bug report came from elsewhere. It's about the icon spring animation.
1827481,2019-05-03 07:37:21 UTC,"Thank you for your bug report. What do you call ""show application""? How do you trigger it?"
1827481,2019-05-03 08:58:35 UTC,I use mouse click and Ubuntu dock.
1827486,2019-05-03 08:15:58 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827486,2019-05-03 08:18:54 UTC,"I can't test it in 18.04 but it seems to be working in 19.04, in the Application and the Notification area"
1827486,2019-05-03 09:48:59 UTC,"Also confirming on Ubuntu 18.04.
FWIW, the later version I have on Fedora 30 works correctly."
1827486,2019-05-03 12:24:15 UTC,"workaround: edit /etc/inxi.conf, make line 2 B_ALLOW_UPDATE=true, then in terminal do> sudo inxi -U"
1827486,2019-05-03 17:20:39 UTC,"This is not a bug, the weather source that was in inxi 2.x and 3.0.31 and earlier is gone. The only fix for weather is to update to current inxi (3.0.33 in ubuntu, and 3.0.34 in master branch of github inxi)."
1827486,2019-05-06 05:56:13 UTC,"Howdy,"
1827487,2019-06-07 07:12:02 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827488,2020-05-22 04:17:41 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1827489,2019-12-12 19:01:59 UTC,Marking this as invalid for nova since it doesn't appear there is anything for nova to do with this:
1827489,2019-05-03 13:52:42 UTC,"I proposed https://review.opendev.org/#/c/656949/ to update the neutron docs with additional information on this, I can link this bug if we feel that is enough information to make this clearer."
1827489,2019-05-05 09:10:21 UTC,"Reviewed:  https://review.opendev.org/656949
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=252acc069465febdbd7b9662695cd11c48a07e1c
Submitter: Zuul
Branch:    master"
1827492,2019-05-15 12:31:00 UTC,We can make a distinction between existing VMs and newly-built VMs by `instance.launched_at` ;
1827492,2019-05-15 12:24:17 UTC,"I found the root cause, the `required_by` function in `nova.virt.config_drive` module did not take the case as follows into consideration:
""""""
def required_by(instance):
    image_prop = instance.image_meta.properties.get(
        ""img_config_drive"",
        fields.ConfigDrivePolicy.OPTIONAL)"
1827492,2019-10-29 14:00:28 UTC,"Change abandoned by sean mooney (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/691864
Reason: actully based on matts last comment on https://review.opendev.org/#/c/660914/ i wont backport this unless we decide to backport that upstream"
1827492,2019-10-29 13:56:54 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/691864"
1827492,2019-10-01 07:52:48 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/660917"
1827492,2019-10-01 07:52:42 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/660915"
1827492,2019-10-01 07:52:36 UTC,"Change abandoned by Lee Yarwood (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/660914"
1827492,2019-09-27 09:03:35 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1827492,2019-07-31 15:30:41 UTC,Note this is essentially a duplicate of bug 1241806.
1827492,2019-09-19 13:12:47 UTC,"Reviewed:  https://review.opendev.org/669738
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=641feb62a33e211a3ed1f9a2309ee16d827f5fe2
Submitter: Zuul
Branch:    master"
1827492,2019-07-08 18:18:14 UTC,"new bug
https://bugs.launchpad.net/nova/+bug/1835822"
1827492,2019-07-08 18:03:58 UTC,"there is a bug in the patch that was merged on master which im going to fix.
once i file the new bug."
1827492,2019-05-23 07:45:47 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/660917"
1827492,2019-05-23 07:45:19 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/660915"
1827492,2019-05-23 07:44:53 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660914"
1827492,2019-05-23 07:43:21 UTC,"Reviewed:  https://review.opendev.org/659703
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2af89cfea0531ab75b4f5765bb220073f42662d0
Submitter: Zuul
Branch:    master"
1827492,2019-05-17 03:03:50 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659703"
1827492,2019-07-08 18:42:22 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/669738"
1827495,2019-06-24 04:51:25 UTC,"The verification of the Stable Release Update for snapd has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827495,2019-06-24 13:02:03 UTC,This bug was fixed in the package snapd - 2.39.2+18.04
1827495,2019-06-24 04:51:31 UTC,This bug was fixed in the package snapd - 2.39.2+19.04
1827495,2019-06-24 04:51:20 UTC,This bug was fixed in the package snapd - 2.39.2+18.10
1827495,2019-06-24 13:02:13 UTC,This bug was fixed in the package snapd - 2.39.2
1827495,2019-06-11 09:02:52 UTC,"Hello Michael, or anyone else affected,"
1827495,2019-06-11 09:01:35 UTC,"Hello Michael, or anyone else affected,"
1827495,2019-06-11 09:01:02 UTC,"Hello Michael, or anyone else affected,"
1827495,2019-06-11 09:00:22 UTC,"Hello Michael, or anyone else affected,"
1827495,2019-06-07 18:01:50 UTC,This bug was fixed in the package snapd - 2.39.2+19.10ubuntu1
1827495,2019-06-21 11:07:13 UTC,"Hello, the validation has been completed with no issues.
The test document: https://docs.google.com/document/d/1PH650GbvVytncghI1yhTJK-TItliMm59lY_mq43q2E0/edit?usp=sharing"
1827497,2019-05-03 14:42:30 UTC,There seems to be a lot of duplication of tests:
1827498,2019-06-30 16:04:07 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827498,2019-11-01 23:49:03 UTC,Using Fedora 31 with geoclue2-2.5.5-1.fc31 I also see an RSS of over 3 GB.  gnome-shell is using almost as much; perhaps these are related?
1827498,2019-11-01 23:54:04 UTC,Oddly my system reports 2.5.5 installed but 2.5.3 active:
1827498,2020-05-10 15:08:33 UTC,I saw this issue using geoclue-2.0 2.5.3-1ubuntu1 on eoan.
1827498,2020-05-11 14:07:51 UTC,Is anyone still seeing that issue in focal?
1827499,2019-05-03 10:45:46 UTC,Confirmed in bionic and it's fixed in 5.0/disco
1827501,2020-05-19 09:34:04 UTC,I can confirm that this is still occurring in Focal 20.04.
1827501,2020-01-31 21:29:09 UTC,"The reason this works in MATE (and really everywhere that's not Lubuntu) is because they don't actually have a fully encrypted system. They're using LVM to do the decryption after GRUB boots, i.e. /boot is not encrypted. Calamares and how we have it set up needs to have LUKS decrypted before getting GRUB going, essentially, because /boot is encrypted. From a security standpoint, this is better. From a user experience standpoint, it's a little unfortunate."
1827501,2019-05-09 09:17:42 UTC,"""During the installation, it uses the keyboard layout, which you have selected. (Unless there is another bug.)"" - with ubuntu mate there does seem to be an issue because even if i select a non-qwerty layout the password that gets typed in the set up page in asteriks is for some reason, in QWERTY, and there is no way of knowing this (until after installation and trying different combinations at boot). Therefore I suggest the ability to show the password entered, during set-up, should one wish, so they can see what has been typed."
1827501,2019-05-08 19:46:30 UTC,"Now I understand, what you mean with the asterisks.
I think, it is normal to hide the passwords. And you have to enter the password twice, to ensure, that there are no typos. (And from a security point of view, it would be even better not to show the asterisks)
During the installation, it uses the keyboard layout, which you have selected. (Unless there is another bug.)"
1827501,2019-05-08 17:59:04 UTC,Thank you for reporting this issue.
1827501,2019-05-08 10:51:42 UTC,Thank you for reporting this issue. I can confirm this behavior in a Lubuntu 19.04 virtualbox VM. Calamares version 3.2.4-0ubuntu3
1827501,2019-05-08 18:52:21 UTC,"""After rebooting, Grub asks for the passphrase to unlock the encrypted LUKS container. I don't see any asterisks. How did you install Lubuntu 19.04?"""
1827503,2019-05-03 12:28:21 UTC,"In lieu of having the particular annotation scheme I wanted within eeschema itself, I ended up writing a standalone program in Python that read the .sch files and applied my annotation scheme to them.  I did that out of personal necessity, but it occurs to me that it might be a more-appropriate approach than trying to implement a bunch of different annotation schemes directly within eeschema that were each of use to only a few people."
1827503,2019-05-03 12:39:06 UTC,"I suppose I should actually have given a link to my own Python program in my last post.  Although it works for me, I'm sure it's probably completely worthless to anybody else, and doesn't even have the user-replaceable function in it that I proposed, but it might give some focus regarding my suggestion for a standalone annotating program."
1827508,2019-05-03 12:32:04 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827508,2019-05-13 09:16:42 UTC,"Hi Horst, thanks for bringing this to our attention. LibreOffice 6.2.3.2 is scheduled for release to Disco soon. Once it's released, if you don't mind, I'll ask for your help in testing this again. I'll keep you posted."
1827508,2019-05-16 08:45:42 UTC,"Hi again Horst, 6.2.3.2 has been released to Disco, please could you upgrade and let me know if this issue has been fixed. Thank you!"
1827508,2019-05-16 13:54:57 UTC,"Yes, I don't have the issue with the newly released LO 6.2.3.2 in Disco anymore.  Thanks!"
1827508,2019-05-16 14:03:33 UTC,Excellent. Thanks for the update!
1827513,2019-05-08 18:15:03 UTC,https://github.com/snapcore/snapcraft/pull/2556
1827514,2019-08-28 15:08:02 UTC,"Verified in build ""20190827T033000Z"" in a 2+2 system."
1827514,2019-06-24 14:13:34 UTC,"Reviewed:  https://review.opendev.org/666571
Committed: https://git.openstack.org/cgit/starlingx/gui/commit/?id=bc78cb23a06cb6e5e5d697294ba7b653582e5ab3
Submitter: Zuul
Branch:    master"
1827514,2019-06-24 11:51:18 UTC,I have no idea why was this reassigned :) I took it back.
1827514,2019-06-21 15:51:54 UTC,I don't understand why this was assigned to me.  It looks like there is a fix pending already.  Is Ovidiu's patch not valid or does someone need to take that over?
1827514,2019-05-13 15:25:15 UTC,"yes, the issue is there as of 2019-05-09 build"
1827514,2019-06-20 13:20:35 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666571"
1827514,2019-05-13 00:22:37 UTC,Can you please confirm if the issue still exist after Ceph upgrade? Need build after 5/3.
1827514,2019-05-08 20:13:32 UTC,It would be nice if this is fixed asap to enable this functionality thru Horizon.
1827514,2019-05-08 20:13:13 UTC,Marking as release gating given the issue is related to a new feature - adding osds w/o locks
1827514,2019-06-21 12:30:09 UTC,Assigned to Bruce for re-assignment.
1827518,2019-05-03 15:41:06 UTC,How bizarre... Surely the opacity slider in the layer colour picker should use/modify the transparency chosen with the { and } hotkeys?
1827518,2019-05-14 09:53:12 UTC,"@Michael: This looks like an uncomfortable interaction between the layer ""swatch"" (which is what's shown in the layer pane) and the current layer colour, which is modified with { and }."
1827518,2019-05-27 00:36:28 UTC,"Fixed in revision 638ac3838c499d1c4d1780e21233a327047fd147
https://git.launchpad.net/kicad/patch/?id=638ac3838c499d1c4d1780e21233a327047fd147"
1827521,2019-05-07 06:13:58 UTC,"@ppeng, looking into the log, the application-apply stuck at here:"
1827521,2019-05-08 11:10:52 UTC,This is likely an issue caused by Ceph Rest API not being available when stx-openstack is applied:
1827521,2019-05-13 07:43:14 UTC,ceph-mgr and restful plugin are restarted by mgr-restful-plugin because of a missing liveness request:
1827521,2019-05-16 20:15:57 UTC,Please add the above note to https://bugs.launchpad.net/starlingx/+bug/1828059 as this is the bug that reports the volume issue you are reporting now. This issue reports a different symptom entirely even if the root-cause of both issues are the same.
1827521,2019-05-14 19:00:04 UTC,Bob Church and Daniel Badea have identified an upstream fix that was targeted in ceph v13.2.3 (stx has ceph v13.2.2):
1827521,2019-05-06 23:07:06 UTC,"[wrsroot@controller-0 ~(keystone_admin)]$ system host-list
+----+--------------+-------------+----------------+-------------+--------------+

| id | hostname     | personality | administrative | operational | availability |


+----+--------------+-------------+----------------+-------------+--------------+

| 1  | controller-0 | controller  | unlocked       | enabled     | available    |
| 2  | compute-0    | worker      | unlocked       | enabled     | available    |
| 3  | compute-1    | worker      | unlocked       | enabled     | available    |
| 6  | storage-1    | storage     | unlocked       | enabled     | available    |
| 7  | storage-0    | storage     | unlocked       | enabled     | available    |
| 12 | controller-1 | controller  | unlocked       | enabled     | available    |


+----+--------------+-------------+----------------+-------------+--------------"
1827521,2019-05-22 18:40:21 UTC,"Not saw this issue is recent load.
Lab: WCP_99_103
Load: 2019-05-21_14-14-17"
1827521,2019-05-14 15:28:12 UTC,I've seen this a few times as well with a pull from yesterday.
1827521,2019-05-06 23:05:25 UTC,After our docker registry was updated with missing docker images the BM 2+2+2 was installed successfully. system application-apply stx-openstack succeed.
1827521,2019-05-16 19:41:58 UTC,Using CENGN image 20190515T220331Z: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190515T220331Z/outputs/iso/bootimage.iso
1827521,2019-05-06 05:06:01 UTC,"@ppeng, I deployed a simplex AIO (built from 0505 codebase) and it worked well with stx-application.
pls see the attachment."
1827521,2019-05-06 01:46:02 UTC,"another deployment (2+2+2) was done on Cengn 0504 build successfully, with stx-openstack application applied. see the attachment."
1827521,2019-05-06 00:46:57 UTC,"@fhernan2, I installed the build from the latest codebase for a 2+2+1 and I could successfully apply stx-openstack, AFTER I assured in my local registry all docker images are placed."
1827521,2019-05-06 00:46:24 UTC,"@fhernan2, I installed the build from the latest codebase for a 2+2+1 and I could successfully apply stx-openstack, AFTER I assured in my local registry all docker images are placed."
1827521,2019-05-06 00:45:59 UTC,"@fhernan2, I installed the build from the latest codebase for a 2+2+1 and I could successfully apply stx-openstack, AFTER I assured in my local registry all docker images are placed."
1827521,2019-05-05 01:56:52 UTC,"@ppeng, when you were trying to run ""application-apply stx-openstack"", how many controllers were available? only controller-0 or both controller-0 and -1?
From your log, ""ALL_NODES_20190503.134444.tar"" actually only has ""controller-0_20190503.134444.tgz""."
1827521,2019-05-05 01:33:56 UTC,"@fernando, ""stx-openstack"" applied failed due to a set of missing docker images in registry:
1. stx-glance:master-centos-stable-20190429T233000Z
2. stx-keystone-api-proxy:master-centos-stable-20190429T233000Z
3. stx-nova-api-proxy:master-centos-stable-20190429T233000Z"
1827521,2019-05-03 22:54:35 UTC,BM 2+2+2 sysinv.log
1827521,2019-05-03 22:34:59 UTC,It is also presented on BM 2+2+2 cluster.
1827521,2019-05-03 17:52:27 UTC,"Initial triage indicates, this is related to ceph upversion. ceph-mgr process is dying. Marking stx.2.0 gating as application apply is failing."
1827521,2019-05-06 13:56:24 UTC,Issue was reproduced on 20190505T233000Z. both hosts logs are collected and attached.
1827522,2019-05-03 15:34:19 UTC,Could you upload a project that exhibits this? It would greatly help in figuring out the issue.
1827522,2019-05-09 21:13:36 UTC,I can't reproduce this on macOS using 5.1.2 or latest master. @Anyone else?
1827522,2019-05-09 21:37:17 UTC,"I just fixed a similar bug in 6.0, which appears to have been in the code for some time.  While it might not fix this, I think it's worth merging back to 5.1.2."
1827522,2019-05-11 23:28:15 UTC,"The 5.1 code is different enough here that the changes can't be applied directly.  Since I'm not even sure it's the same bug, I'm not going to attempt to apply the other fix."
1827528,2019-05-13 16:18:31 UTC,PR to stable branch: https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/14
1827528,2019-05-03 18:57:11 UTC,https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/8
1827528,2019-05-06 13:42:37 UTC,Fix available in kubernetes-worker-527 or later.
1827529,2019-08-14 14:51:43 UTC,verified 2019-08-12_20-59-00
1827529,2019-06-13 14:54:17 UTC,"Reviewed:  https://review.opendev.org/662704
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=843abd69585875e04ada4e59ef7f4f5c1c92abd7
Submitter: Zuul
Branch:    master"
1827529,2019-06-05 14:50:29 UTC,"With the patch: https://review.opendev.org/#/c/662704/, I also verified case of this issue, in storage dedicated (2+2=2) deployment, replication can modify AFTER 2 controllers unlock and BEFORE first storage node installed."
1827529,2019-05-17 12:39:42 UTC,"Good discussion about the scenarios :)
so beside the needed change for SB_TASK_RECONFIG_CONTROLLER, I think maybe add some test cases to validate there has issues and we can re-consider whether to modify the related source code for the replication control strategy.
How do you think? Ovidiu and Fernando?"
1827529,2019-06-05 12:45:16 UTC,I have made patch: https://review.opendev.org/#/c/662704/ which expected to resolve the issue and reclaim teh state-machine and answer the comments with Ovidiu in patch review as following:
1827529,2019-05-15 20:44:18 UTC,"@Ovidiu, checking your comments, couple of questions:
-	<Per Ovidiu> 2. On a storage setup (i.e. one that has storage nodes) users can go from 2 to 3 if there are less than 2 storage nodes deployed.
<FH> Assuming your comment about “having less than 2 storage nodes” I was thinking having following scenario:
Scenario 1) when having 2 storage nodes in a dedicated storage with at least 3 osd.[x]s, meaning we can storage on osd.0 and get replicated on osd.1 and osd.2
[wrsroot@controller-0 ~(keystone_admin)]$ ceph osd tree
ID  CLASS WEIGHT  TYPE NAME              STATUS REWEIGHT PRI-AFF
 -1       2.17743 root storage-tier
 -3       1.30646     chassis group-0
 -4       0.43549         host storage-0
  0   ssd 0.43549             osd.0          up  1.00000 1.00000
  1   ssd 0.43549             osd.1          up  1.00000 1.00000
-5       0.87097         host storage-1
  2   ssd 0.43549             osd.2          up  1.00000 1.00000"
1827529,2019-05-14 14:31:52 UTC,SB_TASK_RECONFIG_CONTROLLER is no longer needed as a state. It should be removed. It was needed at some point in time but no longer.
1827529,2019-05-13 17:51:48 UTC,Found same behavior on BM 2+2+2 dedicated storage
1827529,2019-05-10 18:06:13 UTC,This is still a problem in 20190510T013000Z.  Output is as follows:
1827529,2019-05-06 18:19:50 UTC,Marking as release gating; replication 3 is a supported stx storage configuration.
1827529,2019-05-16 11:15:03 UTC,"Replied via email, see inline [Ovi] tag:"
1827530,2019-05-08 09:43:41 UTC,"Hi Franklyn,
thank you for your help making Ubuntu better!"
1827530,2019-10-20 04:17:25 UTC,[Expired for mariadb-10.0 (Ubuntu) because there has been no activity for 60 days.]
1827532,2019-05-06 08:14:39 UTC,"Thank you for the bug report, it's a bit of a side command but since we don't use offline updates is there a case in practice where we do call to it anf fail/get the grub menu described there? Or is it just an issue in case someone try to manual call to offline updates?"
1827532,2019-05-06 12:58:25 UTC,With fwupd there are two ways that it will occur:
1827544,2019-05-18 10:40:33 UTC,@Gun
1827544,2019-09-15 16:56:54 UTC,Migrated to https://github.com/widelands/widelands/issues/590
1827544,2019-05-13 12:47:01 UTC,This happens in the chat window where the text if the message is two pixels higher than the username.
1827544,2019-05-04 05:49:19 UTC,That looks like a rounding error.
1827555,2019-08-22 16:16:03 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1827555,2019-07-31 20:36:25 UTC,This bug was fixed in the package linux-hwe - 5.0.0-23.24~18.04.1
1827555,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1827555,2019-07-22 10:53:54 UTC,This bug was fixed in the package linux-hwe - 4.15.0-55.60~16.04.2
1827555,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1827555,2019-05-03 16:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827555,2019-07-03 16:27:12 UTC,"The proposed kernels for bionic, cosmic, and disco all contain the correct patch, which solves this bug."
1827555,2019-07-03 13:07:13 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1827555,2019-07-03 13:03:01 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1827555,2019-07-03 11:02:45 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1827555,2019-05-13 14:26:40 UTC,A mistake was made in the previous patch. A new patch was sent to the kernel-team mailing list on May 10. I have attached its contents.
1827555,2019-07-03 16:27:50 UTC,I tested on the affected systems and verified headset functionality.
1827576,2019-05-03 17:43:35 UTC,"Then why is this against ubuntu-dev-tools?  Maybe it should have been
against debootstrap?  You also didn't specify what you are using to create
said chroot."
1827576,2019-05-03 18:08:36 UTC,"My bad, I was using mk-sbuild."
1827582,2020-01-24 09:52:06 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1827628,2019-09-27 09:03:55 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1827628,2019-08-19 15:40:57 UTC,This issue was fixed in the openstack/nova 17.0.12 release.
1827628,2019-08-12 16:24:12 UTC,"Reviewed:  https://review.opendev.org/659247
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=472b9993550f1ffbcce769843f793652162cb8dc
Submitter: Zuul
Branch:    stable/queens"
1827628,2019-07-04 18:04:23 UTC,"Reviewed:  https://review.opendev.org/659246
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aa19788d7849780e4ca30ea0bd7577a349ece704
Submitter: Zuul
Branch:    stable/rocky"
1827628,2019-06-06 06:23:54 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1827628,2019-05-24 02:42:47 UTC,"Reviewed:  https://review.opendev.org/659239
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c094a6ef0c220ace7f717a07bef6fbd87a019190
Submitter: Zuul
Branch:    stable/stein"
1827628,2019-08-12 21:11:41 UTC,This issue was fixed in the openstack/nova 18.2.2 release.
1827628,2019-05-15 09:04:55 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/659246"
1827628,2019-05-15 08:48:51 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/659239"
1827628,2019-05-15 02:35:44 UTC,"Reviewed:  https://review.opendev.org/658110
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2f9e972ba3358fc5bc9bdc06faf47b21d509e20f
Submitter: Zuul
Branch:    master"
1827628,2019-05-15 09:08:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/659247"
1827628,2019-05-09 15:00:55 UTC,"I believe the same issue would exist if using the same_host or different_host hints which are used by the SameHostFilter and DifferentHostFilter. Those aren't for server groups, they are for saying ""I want my server on the same host as some other server(s)"" or ""I don't want my server on the same host as some other server(s)"". I think it predates groups."
1827628,2019-05-09 14:49:33 UTC,This is closer to bug 1777591 than bug 1805984.
1827628,2019-05-09 14:29:07 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658110"
1827635,2019-05-13 19:09:53 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827635,2019-05-13 19:09:46 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.16.4
1827635,2019-05-06 17:03:45 UTC,"Hello Brian, or anyone else affected,"
1827635,2019-05-08 17:09:47 UTC,"Hello Brian, or anyone else affected,"
1827635,2019-05-03 18:51:58 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.1
1827635,2019-05-09 23:22:21 UTC,I was able to upgrade to disco with the version of the release upgrader from -proposed.
1827640,2019-05-03 17:37:04 UTC,"From what I can see, the most likely cluprit is the ""dhclient-script"".
https://linux.die.net/man/8/dhclient-script
I am out of time, but the installer's ""/etc/dhcp/dhclient.conf"" file should be checked."
1827640,2019-05-03 20:24:54 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1827642,2019-05-26 22:55:49 UTC,"Fixed in revision 15cf25a6fc7b9e8802e80071490c210119678a4a
https://git.launchpad.net/kicad/patch/?id=15cf25a6fc7b9e8802e80071490c210119678a4a"
1827642,2019-05-06 16:04:26 UTC,I thought you could expand the drop down control to get to the selection but I see now that that is not the issue.  I can confirm that the 0.01mm and 0.025mm grids cannot be selected.  Sorry about the noise.
1827642,2019-05-06 14:39:20 UTC,"@Michael, can you not scroll the drop down list or hover over the scroll arrows on the top and/or bottom of the list when there are more items than the list can display?  When I open the list, I cannot see all of the grid entries until I scroll up or down."
1827642,2019-05-06 14:59:08 UTC,"@Wayne, everything seems to behave as expected (scrolling, hovering over arrows etc.). Just when I click on either 0.0250 mm or 0.0100 mm the selection is not changed (stays on what it was before opening the list)."
1827642,2019-05-06 14:23:18 UTC,"@Wayne, sure I can do that. Can you guide me what I should do to do that? Should I install a new OS? Should I build the kicad myself?"
1827642,2019-05-06 14:17:20 UTC,"I'm using macOS. From what I tested, it only occurs in GerbView and I can select all grid sizes except for 0.0250 mm and 0.0100 mm."
1827642,2019-05-06 14:00:07 UTC,I can get to all of the grid setting but I am using gtk 3.24.  I wonder if this a bug between wx and gtk.  Would it be possible for you to use a build of kicad that uses a more recent version of gtk3?
1827642,2019-05-06 14:35:12 UTC,"Oh, sure. It was mostly on GerbView. But I saw some issues related on PcbNew maybe with the Zoom Area is selected."
1827642,2019-05-06 14:01:12 UTC,"@Michael, I see that your triaged this.  I'm assuming that you duplicated the bug.  What version of gtk are you using that reproduced this bug?"
1827644,2019-12-17 01:23:12 UTC,"Even I Have this issue , Battery is showing red Icon / image at 48% . What is this ?"
1827644,2019-05-03 19:06:57 UTC,"Thank you for your bug report, what's the content of /sys/class/power_supply/BAT0/status?
Also do you have the updates from bug #1745032 installed?"
1827644,2019-05-03 19:12:43 UTC,"The system is up to date, so I think I have the updates installed. The content of /sys/class/power_supply/BAT0/status is ""Not charging""."
1827644,2019-05-06 08:11:27 UTC,"""Nor chargning"" seems to be the real state/what the kernel reports there then, it's similar to what is described in https://gitlab.gnome.org/GNOME/gnome-control-center/commit/6efaf85e
Not a bug?"
1827644,2019-05-07 18:37:27 UTC,"I think it's a bug, because all laptops I've ever seen show ""fully charged"" instead of ""not charging"" when they hit 100% of the battery. And there's some other strange behavior, like the Gnome indicator eventually being stuck at ""Estimating"" and, sometimes, if you disconnect the power plug while at 100% and connect it again after that, Upower shows ""discharging"", as if it didn't recognize the power supply again, which is only fixed by a reboot."
1827644,2019-10-29 09:30:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827644,2019-10-29 14:27:34 UTC,"Been trying for days to 'fix' the battery status, 9.7 hours to full? think ubuntu is on crack"
1827651,2019-06-26 18:49:06 UTC,Note that there's a preference to control this in Eeschema....
1827651,2019-05-04 09:10:52 UTC,"I think it would be bad to lose the current behaviour. Maybe the cursor could snap to the ""Footprint Origin"", but also be able to move the footprint from any arbitrary place."
1827657,2019-05-03 21:09:03 UTC,"We've never used that feature. We cancel shelf expired holds then perform a
normal check in."
1827657,2019-05-06 15:31:25 UTC,"In CW MARS, we have found that having checkin modifiers on, (like ""Clear Holds Shelf""), can slow down check-in. I would be worried that essentially always having this modifier on would have the same impact on speed and slow down check-in more than it already is in the web client."
1827657,2020-02-12 16:23:54 UTC,I'd be in favor of having this come back as the default behavior too.  I don't like that it's an extra step now if a hold has expired.
1827658,2019-07-18 20:20:41 UTC,"closing
The issue with the i/o not being populated properly in Horizon will be tracked separately
BUILD_ID=""20190715T233000Z"""
1827658,2019-06-10 08:11:58 UTC,"Please check if stx-openstack is applied when you check the Horizon ""Storage Overview"".
If openstack is not applied successfully the storage status cannot be displayed."
1827658,2019-06-10 05:30:32 UTC,"Please give me more details about the issue.
How did you config the deployment? Is it simplex/duplex/multi-node with/without standalone storage?
And please help to provide /var/log/horizon.log if you see this issue."
1827658,2019-06-10 05:22:54 UTC,Cannot reproduce on 06/03 and 06/04 image:
1827658,2019-06-07 14:05:11 UTC,Changed to Confirmed for Wendy.
1827658,2019-06-07 13:41:37 UTC,Reopening per retest results above.
1827658,2019-06-17 20:26:20 UTC,"Checked again on BUILD_ID=""20190613T013000Z""
standard 2+2 system *with stx-openstack applied*
(Tested without a storage node)"
1827658,2019-05-22 16:55:55 UTC,"Reviewed:  https://review.opendev.org/659214
Committed: https://git.openstack.org/cgit/starlingx/gui/commit/?id=17336123bd4c2031f0277102948d8fb4ac4bf9bc
Submitter: Zuul
Branch:    master"
1827658,2019-05-15 04:09:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659214"
1827658,2019-05-15 03:13:39 UTC,"Change abandoned by Yan Chen (<email address hidden>) on branch: master
Review: https://review.opendev.org/657762"
1827658,2019-05-08 09:08:12 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657762"
1827658,2019-05-08 08:56:22 UTC,"The new python-cephclient dont have APIs horizon needed to display the ceph status.
Will raise a patch to add the APIs."
1827658,2019-05-06 18:05:21 UTC,Marking as release gating; stx-gui not updated properly as part of the ceph upgrade feature.
1827658,2019-05-07 09:15:40 UTC,"Tried 4.28 image, the ceph status in Storage Overview page is ok.
But on 5.4 image it is broken. Will check ceph related patches during this period."
1827658,2019-06-06 21:29:05 UTC,"Tested by generationg a ceph warning as follows in the BUILD_ID=""2019-06-03_18-34-53""
I am still not seeing Horizon ""Storage Overview"" display changes other than objects misplaced."
1827659,2019-05-06 18:03:14 UTC,Marking as release gating; cmds no longer valid given the swift containerization work.
1827659,2019-06-21 20:17:12 UTC,This LP is no longer valid as swift will be put back to an optional service. Reference: https://bugs.launchpad.net/starlingx/+bug/1833738
1827660,2020-06-22 21:25:20 UTC,We believe this issue was resolved in: https://bugs.launchpad.net/bugs/1774710.
1827660,2019-05-03 22:09:49 UTC,This commit:
1827660,2019-05-03 21:02:37 UTC,I think this is bug 1774710; but please note there is a behaviour change in neutron which impacts rocky and queens which causes a different issue - neutron team are currently reviewing upstream but likely to revert a number of changes which includes the code that causes the issue you are seeing.
1827660,2019-05-03 20:08:58 UTC,sub'd to field high.
1827660,2019-05-03 20:08:17 UTC,"This is blocking our test of deploying k8s on top of FCB. I think I have a workaround in using dnsmasq-flags, so marking it high rather than critical."
1827660,2019-05-03 21:22:26 UTC,It would be good to see if the --domain argument is being passed to dnsmasq processes spawned in qdhcp namespaces.
1827664,2019-06-14 01:38:29 UTC,Landed in develop too as part of the bigger merge.
1827664,2019-05-09 12:46:12 UTC,"I think I worked out why it is triggering every 3s. Specifically the delay line is:
 delay = time.Duration(float64(delay) * math.Pow(engine.config.BackoffFactor, float64(info.startAttempts-1)))"
1827664,2019-06-12 03:27:29 UTC,2.6 fix: https://github.com/juju/juju/pull/10317
1827664,2019-06-12 02:46:20 UTC,"Upstream fix: https://github.com/juju/worker/pull/12
2.5 fix: https://github.com/juju/juju/pull/10315"
1827664,2019-05-28 12:37:06 UTC,https://github.com/juju/juju/pull/10240 is merging this into 2.5
1827664,2019-05-09 14:50:28 UTC,"A potential fix in the Worker package:
https://github.com/juju/worker/pull/11"
1827664,2019-05-09 12:14:29 UTC,So I set up an lxd container with limited disk space with:
1827664,2019-05-06 04:35:25 UTC,"If there is protection, it is not working - see https://bugs.launchpad.net/juju/+bug/1811147"
1827664,2019-05-07 04:51:20 UTC,This is a snippet of logs spewing from an agent:
1827664,2019-05-06 13:12:06 UTC,"(or is it that our change wasn't to 2.5.1 and it is just that they weren't
running that code.)"
1827664,2019-05-06 13:11:45 UTC,"@thumper
I know we did some work to have automatic exponential backoff when workers
are bouncing in their loop. Is the issue that this only triggers during the
Start of the worker, and not if it successfully started but then quickly
fails in the future?"
1827664,2019-05-06 11:26:57 UTC,Forgot to mention: this happened on a controller running 2.5.1.
1827664,2019-05-06 04:57:20 UTC,I've retitled this bug to specifically target the fact that Juju agents spew logs on ENOSPC. The unbounded growth of controller logs collections is targeted in https://bugs.launchpad.net/juju/+bug/1811147.
1827664,2019-05-05 06:22:58 UTC,"Controllers do rotate their log files and we prune the log database to keep
it around 4GB in size. It is possible that the rate of messages is higher
than the rate that we prune them, but there is some protection from it. We
also rate limit log messages, though this may not be aggressive enough."
1827664,2019-05-07 05:52:28 UTC,This is easy enough to reproduce - on an instance:
1827668,2020-07-23 10:39:40 UTC,comments https://bugs.launchpad.net/charm-keystone/+bug/1827668/comments/10 and https://bugs.launchpad.net/charm-keystone/+bug/1827668/comments/9 are unrelated to this bug.  That was due to [1] which broken mojo as the relative 'tests/' directory did not exist to put the keystone_juju_ca_cert.crt file in.
1827668,2020-07-23 06:59:17 UTC,"As Aurelien has noted, this is now a consistent bug on mojo tests in designate-ha.  I've run the test manually, and noticed that the mojo tests starts the vault unlocking script *before* keystone has finished it's final set of relation changes.  This sort of confirms what Aurelien is saying."
1827668,2020-06-30 08:24:55 UTC,Something related seems to be happening a lot on OSCI [0] at the moment. The test thinks keystone is ready and is trying to download via scp the certificates from a keystone unit. However the certificates haven't been written on the unit's filesystem yet.
1827668,2020-03-13 09:01:09 UTC,I just hit this issue again so going to work on a fix.
1827668,2019-07-03 09:40:15 UTC,There is still a race condition in the keystone charm relating to when it bumps the internal port to 35337 which it does prior to the certificates having been written to disk and the TLS endpoints being configured in Apache.
1827668,2019-06-27 16:25:24 UTC,Thank you for your work on this.
1827668,2019-06-27 00:26:53 UTC,subscribed ~field-critical
1827668,2019-05-11 08:11:12 UTC,The difference between the deployments where it goes well and where it does not is the time when a database migration is triggered (shared-db-relation-changed).
1827668,2019-05-10 11:46:55 UTC,Subscribed ~field-high.
1827668,2019-05-10 11:38:04 UTC,Reproduced it on a clean 19.04+Queens deployment without totally-insecure-unlock (did a manual unlocking procedure by hand):
1827668,2019-07-02 16:06:18 UTC,Unsubscribing field-critical. Customer decided not to go with Vault.
1827677,2019-05-03 21:00:12 UTC,This change was made by a bot.
1827677,2019-05-15 04:58:27 UTC,Does it work on previous kernels?
1827677,2019-05-15 05:27:36 UTC,"Is networking available when it resumes back? Is it possible to run apport right after the resume? For example, install openssh-server and login remotely after sysmtem resumes back. The dmesg log attached previously seems to be captured after force reboot, so it doesn't contain any information about the suspend/resume process."
1827680,2019-11-20 04:17:36 UTC,[Expired for MAAS because there has been no activity for 60 days.]
1827680,2019-09-20 12:14:08 UTC,What status was the machine being released from? Can you please attach the MAAS logs from /var/log/maas?
1827681,2019-08-20 00:57:24 UTC,"Thank you for reporting this bug. However, this was not filed using the ""ubuntu-bug"" tool, and mentions a version of gimp not contained in the Ubuntu 18.04 repositories. Therefore, this bug is invalid."
1827686,2019-05-03 22:32:02 UTC,Sample PCB (single via and trace) attached
1827686,2019-05-16 12:03:33 UTC,"I'm not sure this is a bug in KiCad.  When you print directly to a printer on your system, do you get the same output as you get when you print to PDF?  If not, this is not KiCad.  It's an issue with your system's PDF printer driver."
1827686,2019-05-17 03:49:50 UTC,"Wayne,"
1827686,2019-07-16 04:17:32 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1827689,2019-05-03 23:18:07 UTC,"This is not a glance bug, it belongs to the documentation..."
1827689,2019-05-04 05:20:32 UTC,"This is the documentation of glance, it lives in the glance repo. Thus bugs go to glance."
1827689,2019-05-14 15:43:22 UTC,"In addition to the named document:
After the paragraph ""note"" follow some instructions to edit the config file /etc/glance/glance-registry.conf. However, in the mentioned paragraph ""note"" it says that the service glance-registry from release ""S"" will no longer exist."
1827689,2019-09-09 02:20:28 UTC,"Change abandoned by Brin Zhang (<email address hidden>) on branch: master
Review: https://review.opendev.org/657104"
1827689,2019-10-07 09:18:46 UTC,Fixed in https://review.opendev.org/666973
1827690,2020-10-16 15:35:15 UTC,The fix [0] will resolve this bug but is currently blocked by LP Bug#1899104 [1].
1827690,2020-10-08 23:00:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/756931"
1827690,2019-05-04 00:38:19 UTC,Added the UCA package as well as I am not exactly sure where the root cause is.
1827690,2020-10-07 20:36:05 UTC,Doing some research.
1827690,2019-05-15 17:45:25 UTC,TRIAGE:
1827690,2020-10-08 10:07:24 UTC,After additional debug and research I can confirm the issue is the result of a race-condition situation when multiple barbican-worker units trying to populate the database with schema data simultaneously and upgrade the alembic version.
1827691,2019-05-06 02:32:10 UTC,"Ah, sorry. Ignore comment #7 then."
1827691,2020-01-24 08:50:26 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1827691,2019-05-06 04:30:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827691,2019-05-06 04:01:21 UTC,"From what I have seen in other bug reports, speaker/output routing is usually an issue in the kernel or can be worked around in alsa config files. So I am going to untask pulseaudio here."
1827691,2019-05-06 02:20:47 UTC,"I test the Notebook speaker not headphone, do you mean I should unpack my notebook then change the line, It's too trouble."
1827691,2019-05-04 01:41:55 UTC,apport information
1827691,2019-05-04 01:41:58 UTC,apport information
1827691,2019-05-04 01:41:53 UTC,apport information
1827691,2019-05-04 01:41:51 UTC,apport information
1827691,2019-05-04 01:41:50 UTC,apport information
1827691,2019-05-04 01:41:47 UTC,apport information
1827691,2019-05-06 02:04:46 UTC,Please try a different speaker cable/connector. Only getting sound in one channel is a very common problem with bad connections.
1827692,2019-07-03 16:59:29 UTC,"@zhipeng, as talked in OpenStack.distro meeting, please make a build with updated Nova stein branch and share the build with Ricardo."
1827692,2019-07-03 17:07:43 UTC,"Hi Ricardo,"
1827692,2019-07-08 19:39:31 UTC,"Hi, we are trying to get the proper hardware, because this issue was reported with specific network cards combination. However, currently we are running our regression test and this is adding difficulties to get the hardware."
1827692,2019-07-08 19:56:19 UTC,Using this build:
1827692,2019-07-11 02:33:41 UTC,"Thanks Ricardo!
I think you can test it with original build you tested before in the same setup.
If original build can reproduce the bug, and current EB couldn’t in your current setup,
That should be OK!"
1827692,2019-08-13 14:13:03 UTC,"Hi Yong, we are setting up the specified hardware, however, we have been hitting this issue constantly."
1827692,2019-08-13 13:32:22 UTC,"@Ricardo, could we run testing for this LP in this week?
I think we've just completed the regression testing lately?"
1827692,2019-08-13 15:54:48 UTC,After setting up the proper hardware. It looks that the issue is no longer present in the following ISO image:
1827692,2019-08-13 17:12:25 UTC,"Now it's confirmed the previous issue was not seen as expected, so close this LP with ""Fix Released""."
1827692,2019-11-27 18:38:15 UTC,Remove retestneeded label based on Ricardo's comments.
1827692,2019-06-26 13:39:34 UTC,Thanks Ricardo！
1827692,2019-07-23 17:19:12 UTC,"After our StarlingX Test Meeting, we agreed the following about this specific bug. It has to be tested again with the same specific hardware that it was originally reported."
1827692,2019-06-25 21:08:33 UTC,"Hi @zhipengs, sorry for my late reply, lately I have been focused on other tasks related to QAT. Currently, we are a little bit short of hardware to perform the validation. However, let me prioritize this task for this week. And I'll let you know the results."
1827692,2019-07-23 15:05:38 UTC,We have tested with duplex configuration and the issue is no longer seen. By now you can mark this bug to be closed. Thanks.
1827692,2019-06-10 02:10:07 UTC,"Hi Ricardo,"
1827692,2019-05-23 05:29:03 UTC,"not sure yet if this LP is related to LP: https://storyboard.openstack.org/#!/story/2005750, but temporary assign to Zhipeng as he is working on SB2005750."
1827692,2019-05-22 21:41:30 UTC,"@cindy, right now i'm trying to setup the environment for QAT, I'll let you know as soon as I have some hardware to test this again, or let me just get some progress on QAT, so I can switch to this again. Thanks."
1827692,2019-05-22 00:04:38 UTC,"@Ricardo, can you please report back with your test results using latest ISO?"
1827692,2019-05-14 21:16:30 UTC,"@Cindy, sure, we can re-test, as soon as we can get an stable ISO for 2+2 configuration."
1827692,2019-05-11 00:49:33 UTC,"@Cristopher @Ricardo, because we already have OVS/DPDK upversion patches merged, can you please re-test the issue on master Cengen build and check if the issue is still there?"
1827692,2019-05-08 20:22:46 UTC,"I don't believe the above issues are related. As noted, there is an explicit error from nova in this case. Assigning to the distro.openstack project lead for further triage."
1827692,2019-05-04 02:44:29 UTC,"controller-0:~# kubectl describe node compute-0
Name:               compute-0
Roles:              <none>
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/hostname=compute-0
                    openstack-compute-node=enabled
                    openvswitch=enabled
                    sriov=enabled
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: 192.168.206.50/24
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Fri, 03 May 2019 15:31:54 +0000
Taints:             <none>
Unschedulable:      false
Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  OutOfDisk        False   Fri, 03 May 2019 21:42:50 +0000   Fri, 03 May 2019 15:31:54 +0000   KubeletHasSufficientDisk     kubelet has sufficient disk space available
  MemoryPressure   False   Fri, 03 May 2019 21:42:50 +0000   Fri, 03 May 2019 15:31:54 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Fri, 03 May 2019 21:42:50 +0000   Fri, 03 May 2019 15:31:54 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Fri, 03 May 2019 21:42:50 +0000   Fri, 03 May 2019 15:31:54 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            True    Fri, 03 May 2019 21:42:50 +0000   Fri, 03 May 2019 15:32:06 +0000   KubeletReady                 kubelet is posting ready status
Addresses:
  InternalIP:  10.10.57.59
  Hostname:    compute-0
Capacity:
 cpu:                112
 ephemeral-storage:  20027216Ki
 memory:             196618812Ki
 pods:               110
Allocatable:
 cpu:                112
 ephemeral-storage:  18457082236
 memory:             196516412Ki
 pods:               110
System Info:
 Machine ID:                 318e5af8729f4377ae2289ba08b7b594
 System UUID:                00D7627F-0786-E811-906E-00163566263E
 Boot ID:                    c57e6e3c-b277-4bd1-b256-9d537a51b674
 Kernel Version:             3.10.0-957.1.3.el7.1.tis.x86_64
 OS Image:                   CentOS Linux 7 (Core)
 Operating System:           linux
 Architecture:               amd64
 Container Runtime Version:  docker://18.3.1
 Kubelet Version:            v1.12.3
 Kube-Proxy Version:         v1.12.3
PodCIDR:                     172.16.3.0/24
Non-terminated Pods:         (10 in total)
  Namespace                  Name                                               CPU Requests  CPU Limits  Memory Requests  Memory Limits
  ---------                  ----                                               ------------  ----------  ---------------  -------------
  kube-system                calico-node-rkdfn                                  250m (0%)     0 (0%)      0 (0%)           0 (0%)
  kube-system                kube-..."
1827692,2019-05-08 19:47:30 UTC,"Sorry, I pasted the same bug twice, this is the other one: https://bugs.launchpad.net/starlingx/+bug/1826308"
1827692,2019-05-08 19:22:30 UTC,Is it possible that these issues/errors are related to what was fixed on these bugs?:
1827692,2019-05-06 19:46:23 UTC,"Hi Ghada, this issue has been seen while testing ovs-dpdk, not sure about the cengn loads."
1827692,2019-05-06 18:00:39 UTC,Is this an issue with the standard cengn loads as well? Or is it specific to the custom load used for ovs-dpdk testing?
1827692,2019-05-04 02:51:29 UTC,ALL NODES Full Log Files
1827692,2019-05-04 02:45:00 UTC,"controller-0:~# kubectl describe node compute-1
Name:               compute-1
Roles:              <none>
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/hostname=compute-1
                    openstack-compute-node=enabled
                    openvswitch=enabled
                    sriov=enabled
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: 192.168.206.194/24
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Fri, 03 May 2019 15:31:21 +0000
Taints:             <none>
Unschedulable:      false
Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  OutOfDisk        False   Fri, 03 May 2019 21:43:20 +0000   Fri, 03 May 2019 15:31:21 +0000   KubeletHasSufficientDisk     kubelet has sufficient disk space available
  MemoryPressure   False   Fri, 03 May 2019 21:43:20 +0000   Fri, 03 May 2019 15:31:21 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Fri, 03 May 2019 21:43:20 +0000   Fri, 03 May 2019 15:31:21 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Fri, 03 May 2019 21:43:20 +0000   Fri, 03 May 2019 15:31:21 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            True    Fri, 03 May 2019 21:43:20 +0000   Fri, 03 May 2019 15:31:33 +0000   KubeletReady                 kubelet is posting ready status
Addresses:
  InternalIP:  10.10.57.228
  Hostname:    compute-1
Capacity:
 cpu:                64
 ephemeral-storage:  20027216Ki
 memory:             97534592Ki
 pods:               110
Allocatable:
 cpu:                64
 ephemeral-storage:  18457082236
 memory:             97432192Ki
 pods:               110
System Info:
 Machine ID:                 32f53d4e0dab4fd3b7e27cdcfd9e8f3d
 System UUID:                8005C491-C91B-E811-906E-00163566263E
 Boot ID:                    d45c3e35-8252-4249-800a-a4b7a83ac266
 Kernel Version:             3.10.0-957.1.3.el7.1.tis.x86_64
 OS Image:                   CentOS Linux 7 (Core)
 Operating System:           linux
 Architecture:               amd64
 Container Runtime Version:  docker://18.3.1
 Kubelet Version:            v1.12.3
 Kube-Proxy Version:         v1.12.3
PodCIDR:                     172.16.2.0/24
Non-terminated Pods:         (11 in total)
  Namespace                  Name                                               CPU Requests  CPU Limits  Memory Requests  Memory Limits
  ---------                  ----                                               ------------  ----------  ---------------  -------------
  kube-system                calico-node-v5kfl                                  250m (0%)     0 (0%)      0 (0%)           0 (0%)
  kube-system                kube-pr..."
1827692,2019-06-24 05:06:10 UTC,"Dear Ricardo,"
1827694,2019-05-05 02:44:23 UTC,That seems to help. Thanks!
1827694,2019-05-04 13:18:21 UTC,To add to the original report: it looks like problem also occurs after suspend/resume cycle. I.e.
1827694,2019-05-04 04:30:07 UTC,This change was made by a bot.
1827694,2019-05-05 02:33:50 UTC,"Could you try passing ""psmouse.synaptics_intertouch=0"" in kernel cmdline?"
1827696,2019-05-05 19:31:14 UTC,I do also prefer the arrangements like we have in the stock.
1827696,2019-09-15 15:30:48 UTC,Migrated to https://github.com/widelands/widelands/issues/2136
1827696,2019-05-09 06:22:28 UTC,"And yes, implement the layouting into a layout() function. Classes like UI::Box call this."
1827696,2019-05-09 06:21:40 UTC,"Regarding #22, you can play around with set_size, set_desired_size and set_center_panel."
1827696,2019-05-08 07:49:26 UTC,"> In my opinion applying a profile should apply the values without marking them
"
1827696,2019-05-08 07:14:53 UTC,To clarify:
1827696,2019-05-08 07:09:31 UTC,"Played around with this new feature, in the beginning it is a bit confusing:"
1827696,2019-05-06 10:50:41 UTC,Could now hack something together that works for most windows but not for all yet... Is this looking good so far (at least the stock menu)?
1827696,2019-05-06 09:52:16 UTC,"Um, another quick question: The AbstractWaresDisplay now recalculates its columns when notified of a GraphicResolutionChanged. This works already, but when it becomes wider due to lower yres, the additional columns disappear behind the window´s border.
Which method(s) do I now have to call to make sure the parent Window resizes itself? layout(), update_desired_size(), set_layout_toplevel(), ... , and on what object (this, get_parent(), ...)?"
1827696,2019-05-06 06:40:46 UTC,"Good suggestion, will do that :)"
1827696,2019-05-05 21:31:43 UTC,Sounds good to me.
1827696,2019-05-05 20:16:52 UTC,"I´ll stick with the stock-window-like layout then. Removed the apply button as in #18 and replaced the ""Save"" text with an icon.
The minimum width of the tab depends on the (tribe-specific) number of columns (which also depends on the screen height); I now optimized the window design for 8 columns."
1827696,2019-05-05 19:26:02 UTC,I like the spinbox design from #13.
1827696,2019-05-05 18:56:21 UTC,Spinbox-Style is online :) Are the buttons good like this or should I make them smaller?
1827696,2019-05-05 19:06:04 UTC,"There´s a built-in way to set this easily, but I am not convinced it looks better..."
1827696,2019-05-05 19:21:12 UTC,I prefer the stock. What about using icons instead of text for save and apply/use and tooltip the text? For save the floppy disc icon and for apply/use the green start button we use in buildings.
1827696,2019-05-04 14:42:17 UTC,Would it be possible to have the [R] and [S] button next to the dropdown? and the [+][-] centred atop?
1827696,2019-05-04 14:43:01 UTC,Hmmm Launchpad butchered the Layout...
1827696,2019-05-04 15:12:09 UTC,I gimped your pic a little
1827696,2019-05-04 15:17:24 UTC,"> The dropdown on the worker panel behaves as it should, the one on the ware panel refuses to open when clicking on it. Which peculiarity of dropdowns am I overlooking?
"
1827696,2019-05-04 18:46:54 UTC,"Hm, trying to found out who think()s too much led me to a nice chase in circles..."
1827696,2019-05-04 13:55:28 UTC,"Two quick questions:
– Any suggestions how to improve the user interface? (screenshot attached)
– The dropdown on the worker panel behaves as it should, the one on the ware panel refuses to open when clicking on it. Which peculiarity of dropdowns am I overlooking?"
1827696,2019-05-05 05:55:17 UTC,"The tab content´s width is set dynamically according to the number of columns to display. Previously this was solved by resizing the window when changing the tab so it completely filled the window, but the additional buttons give the window a fixed width.
The tab panel is an implementation of AbstractWaresDisplay which is used in many places, but I´ll check if I can add an optional hgap…"
1827696,2019-05-05 13:29:47 UTC,The + and + buttons could be replaced by a spinbox.
1827696,2019-05-05 17:39:47 UTC,"I have had another idea: How about arranging the wares/workers horizontally instead of vertically? This will avoid the problem with the blank space, allow us to put all buttons in 1 row and we can get rid of te layout code in Tribes::postload()."
1827696,2019-05-05 18:24:51 UTC,"OK, I´ll change the buttons´ style to mimic a spinbox."
1827696,2019-05-05 18:57:01 UTC,Rotating by 90°
1827696,2019-05-04 20:09:04 UTC,Is it somehow possible to remove the brown strip on the right hand side and let the content of the tab span over the complete width? Maybe by increasing the gaps between the icons?
1827701,2019-05-05 13:27:19 UTC,"True, but the two are linked. Like I said, it’s a compromise. You could also to some extent say the same thing about the Board Setup dialog."
1827701,2019-05-05 14:34:49 UTC,"Well, fair enough, clearly I’m overruled ;)"
1827701,2019-05-05 13:30:41 UTC,I think the distinction Nick is hinting at is metadata vs. primary data.
1827701,2019-05-05 13:03:22 UTC,But doesn't the properties dialog edit things shown on the canvas?
1827701,2019-05-04 10:08:36 UTC,"We're trying to move to generic commands (a noun + verb pattern, rather than combining the two)."
1827701,2019-05-05 11:49:25 UTC,"@JP,"
1827701,2019-05-05 11:15:03 UTC,"@Michael,"
1827701,2019-05-04 10:30:27 UTC,"Agreed. Also, isn't ""Properties..."" more at home in the file menu? Especially with the Footprint Editor ""every footprint is a file"" (and soon to be symbols as well)."
1827701,2019-05-04 09:30:43 UTC,"What should it be? I'm leaning towards ""Symbol Properties..."" and ""Footprint Properties..."", because you can also have pin properties, pad properties etc."
1827701,2019-05-05 11:53:06 UTC,... (add CATIA to the list of software I checked)
1827702,2019-05-04 09:28:51 UTC,"Don't know how xorg got selected - pretty sure the problem is with grub or with the kernel, and seeing as the 4.19.20 kernel used to work, I'm guessing it's grub"
1827702,2019-06-03 07:19:56 UTC,This bug is still showing with kernel 5.0.0-15 (was 5.0.0-13 before)
1827702,2019-06-14 21:09:05 UTC,Update: upgrading BIOS from 301 to 304 fixed this.  Problem may still occur on other machines but on my Zenbook 14 it's fixed.
1827703,2020-01-29 08:13:37 UTC,"NRPE needs to allow/whitelist Nagios' floating IP address as it is the address by which NRPE will see incoming connections. From NRPE's perspective this address would be the ""egress address"" (see https://jaas.ai/docs/charm-network-primitives) of Nagios."
1827704,2019-05-11 09:01:32 UTC,"And I think it would be useful to let in addition to user-config, vendor-data too change configuration frequency.  Is it possible it you work? Do you agree with It usefulness?"
1827704,2019-05-08 15:07:12 UTC,"Hi,"
1827704,2019-05-11 08:55:50 UTC,"Hi Rayn,"
1827705,2019-05-18 09:04:40 UTC,"I will not add input into this quick and common date range
your wish is more related to custom saved filter"
1827706,2019-05-04 15:12:46 UTC,why tf I can't delete a bug here?
1827706,2019-05-04 15:12:54 UTC,this platform sucks
1827707,2019-07-08 21:57:20 UTC,"Fixed in revision fb881ee209bd5e67c8371059df0bf11a0c53aa4c
https://git.launchpad.net/kicad/patch/?id=fb881ee209bd5e67c8371059df0bf11a0c53aa4c"
1827712,2019-05-04 11:30:07 UTC,This change was made by a bot.
1827712,2019-05-05 02:32:43 UTC,"Could you try passing ""psmouse.synaptics_intertouch=1"" in kernel cmdline?"
1827712,2019-12-27 03:37:52 UTC,Mark as Incomplete as per request in comment #3
1827712,2020-02-25 04:17:23 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827714,2019-05-04 12:09:54 UTC,See also bug #1262457
1827714,2020-01-14 00:58:38 UTC,"""Pages and Collections"" search has capacity to find tags, titles, descriptions used on pages but doesn't seem to find things on artefacts such as uploaded files etc... for example, have an Image Block on a page named ""dog.jpg"" then search for ""dog"" on ""Pages and Collections"" search and it won't return a result. Do the same thing with My Portfolio and it will return the result. ""Pages and Collections"" doesn't seem to find tags that are on artefacts only and not on the page (even though both are displayed in the same area ""tags"" under a page's title)"
1827724,2019-05-04 13:44:47 UTC,Passed the previous failing step:
1827725,2019-05-24 08:39:44 UTC,apport information
1827725,2019-05-24 08:39:40 UTC,apport information
1827725,2019-05-24 08:39:41 UTC,apport information
1827725,2019-05-24 08:39:42 UTC,apport information
1827725,2019-05-24 08:39:45 UTC,apport information
1827725,2019-05-24 08:39:39 UTC,apport information
1827725,2019-05-24 09:00:45 UTC,It floods this before reboot:
1827725,2019-06-11 08:03:46 UTC,And it's Toshiba Satellite L300-11Q laptop
1827725,2019-06-11 08:17:29 UTC,Possible dupe of LP: #1827884.
1827725,2019-06-13 01:19:44 UTC,"Yes, nopti helps. Thank you."
1827725,2019-05-24 08:39:47 UTC,apport information
1827725,2019-05-24 08:39:37 UTC,apport information
1827725,2019-05-08 04:25:05 UTC,kern.log has nothing about it
1827725,2019-05-24 08:39:34 UTC,apport information
1827725,2019-05-24 08:39:33 UTC,apport information
1827725,2019-05-24 08:39:32 UTC,apport information
1827725,2019-05-24 08:39:31 UTC,apport information
1827725,2019-05-24 08:39:29 UTC,apport information
1827725,2019-05-24 08:37:06 UTC,It does happen for 4.15.0-50-generic too.
1827725,2019-05-15 05:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827725,2019-05-15 05:05:47 UTC,Does it also happen to -generic kernel?
1827725,2019-05-08 05:09:22 UTC,I've returned to non-hwe
1827725,2019-05-04 14:10:14 UTC,"And I don't know why, but I had booted with 4.15.0-48-lowlatency once. Currently the ""not booting"" state is quite stable. Even after reinstallation of the kernel packages."
1827725,2019-05-24 08:39:36 UTC,apport information
1827726,2019-09-15 15:46:08 UTC,Migrated to https://github.com/widelands/widelands/issues/1728
1827727,2019-05-05 11:08:55 UTC,*** Bug 1549173 has been marked as a duplicate of this bug. ***
1827727,2019-05-05 12:54:21 UTC,*** Bug 1549118 has been marked as a duplicate of this bug. ***
1827727,2019-05-05 14:09:39 UTC,*** Bug 1549180 has been marked as a duplicate of this bug. ***
1827727,2019-05-06 05:45:14 UTC,*** Bug 1549218 has been marked as a duplicate of this bug. ***
1827727,2019-05-06 05:39:06 UTC,*** Bug 1549248 has been marked as a duplicate of this bug. ***
1827727,2019-05-05 06:30:46 UTC,*** Bug 1549143 has been marked as a duplicate of this bug. ***
1827727,2019-05-05 17:39:06 UTC,*** Bug 1549203 has been marked as a duplicate of this bug. ***
1827727,2019-05-05 06:27:36 UTC,*** Bug 1549138 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 21:26:48 UTC,*** Bug 1549110 has been marked as a duplicate of this bug. ***
1827727,2019-05-05 05:36:54 UTC,"See Also: → https://webcompat.com/issues/30556, https://webcompat.com/issues/30561, https://webcompat.com/issues/30562, https://webcompat.com/issues/30563, https://webcompat.com/issues/30564, https://webcompat.com/issues/30565, https://webcompat.com/issues/30566, https://webcompat.com/issues/30571, https://webcompat.com/issues/30572"
1827727,2019-05-05 05:10:07 UTC,*** Bug 1549137 has been marked as a duplicate of this bug. ***
1827727,2019-05-05 00:28:43 UTC,*** Bug 1549124 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 23:28:28 UTC,*** Bug 1549120 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 21:01:46 UTC,*** Bug 1549105 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 18:48:48 UTC,See https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/
1827727,2019-05-06 06:04:38 UTC,"See Also: → https://webcompat.com/issues/30576, https://webcompat.com/issues/30578, https://webcompat.com/issues/30584, https://webcompat.com/issues/30588, https://webcompat.com/issues/30600, https://webcompat.com/issues/30603, https://webcompat.com/issues/30637, https://webcompat.com/issues/30638, https://webcompat.com/issues/30643, https://webcompat.com/issues/30645"
1827727,2019-05-05 06:01:23 UTC,124 failures in 56 pushes (2.214 failures/push) were associated with this bug yesterday.
1827727,2019-05-06 06:46:16 UTC,124 failures in 4131 pushes (0.03 failures/push) were associated with this bug in the last 7 days.
1827727,2019-05-04 18:43:00 UTC,*** Bug 1549094 has been marked as a duplicate of this bug. ***
1827727,2019-05-06 13:39:18 UTC,(When) can http://ftp.mozilla.org/pub/firefox/candidates/ be opened again?
1827727,2019-07-31 14:55:10 UTC,*** Bug 1569470 has been marked as a duplicate of this bug. ***
1827727,2019-05-08 09:44:50 UTC,"is the part
""[first mitigation completed, working on a second one]""
in the bug title meanigful in any way?"
1827727,2019-05-08 08:12:26 UTC,This bug was fixed in the package firefox - 66.0.4+build3-0ubuntu0.18.10.1
1827727,2019-05-08 08:02:36 UTC,This bug was fixed in the package firefox - 66.0.4+build3-0ubuntu0.19.04.1
1827727,2019-05-08 08:02:26 UTC,This bug was fixed in the package firefox - 66.0.4+build3-0ubuntu0.18.04.1
1827727,2019-05-08 08:02:20 UTC,This bug was fixed in the package firefox - 66.0.4+build3-0ubuntu0.16.04.1
1827727,2019-05-08 06:58:57 UTC,"Shouldn't there be sub-tasks for ""Firefox on Ubuntu xenial""  ""Firefox on Ubuntu bionic""  ""Firefox on Ubuntu cosmic"" and  ""Firefox on Ubuntu disco"" to allow tracking the status for the older supported Ubuntu Releases?"
1827727,2019-05-07 18:35:25 UTC,*** Bug 1549200 has been marked as a duplicate of this bug. ***
1827727,2019-05-07 16:33:21 UTC,"While it may be true the ""studies"" feature which enabled the temporary fix is turned on by default it is a highly contentious feature which many security minded users (isn't that what most firefox users are) have disabled. Yes, it can be turned back on to get the ""fix"" but I choose not to compromise one form of security to regain another that was lost due to an unfortunate mozilla error. Just the same as I and many others choose to use LTS and the standard release system to minimize risk and maximize stability. I hope the maintainers can understand this."
1827727,2019-05-07 13:53:37 UTC,"The bug is marked ""Fix Released"" because a bug against a source package always targets the latest development series (in this case 19.10, where the bug is indeed fixed)."
1827727,2019-05-07 12:54:58 UTC,"I agree. At least an ETA would be nice instead of vague ""releases are coming"" for such a critical bug."
1827727,2019-05-07 12:41:11 UTC,arQon wrote:
1827727,2019-05-07 12:11:36 UTC,"This shouldn't be marked as ""Fix Released"" when the LTS's still don't have an update available. I realise the ""real"" work is done, but we can't have LTS's being treated as second-class citizens to the extent that this crippling defect doesn't even show up as an active issue to their users in Launchpad."
1827727,2019-05-07 10:08:36 UTC,*** Bug 1549679 has been marked as a duplicate of this bug. ***
1827727,2019-05-07 04:59:42 UTC,Fixed in 66.0.4+build3-0ubuntu1. Backports to stable releases are coming.
1827727,2019-05-06 15:05:37 UTC,"Please see https://support.mozilla.org/en-US/kb/add-ons-disabled-or-fail-to-install-firefox for current solutions and workarounds.
Status updates are posted here: https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/"
1827727,2019-05-06 14:55:47 UTC,"Please document here the root cause of this issue and what is being done to ensure that it does not happen again, or if that has already been documented elsewhere, please post a link to that documentation here. I've reviewed all the comments on this bug as well as the other information sources to which it links, and I don't see an explanation of the root cause or of steps being taken to prevent recurrence."
1827727,2019-05-06 11:36:00 UTC,*** Bug 1549352 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 18:16:21 UTC,"See Also: → https://webcompat.com/issues/30522, https://webcompat.com/issues/30529, https://webcompat.com/issues/30530, https://webcompat.com/issues/30534, https://webcompat.com/issues/30536, https://webcompat.com/issues/30539"
1827727,2019-05-05 15:58:08 UTC,*** Bug 1549198 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 15:19:01 UTC,An option is to enable 'Studies' and wait 6 hours until you receive the fix.
1827727,2019-05-04 01:32:08 UTC,Confirming that add-ons were also disabled here on 66.0.3 (Win 10) at approx 9pm ET.
1827727,2019-05-04 01:30:34 UTC,Can somehow signing  be disabled?
1827727,2019-05-04 01:29:26 UTC,CloudOps is taking a look at this
1827727,2019-05-04 01:27:26 UTC,*** Bug 1548983 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 01:27:07 UTC,"(In reply to Caspy7 from comment #12)

> We don't yet know how broadly affected the user base is.
"
1827727,2019-05-04 01:24:10 UTC,In case it's not understood I'm seeing a rash of reports of this across mozilla and freenode IRC networks as well as reddit.
1827727,2019-05-04 01:22:05 UTC,Should other bug reports be opened about the empty error message that the browser console shows and related symptoms to help people know what it's going on? Or should that be implemented in a post-morten?
1827727,2019-05-04 01:14:37 UTC,*** Bug 1548976 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 15:34:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827727,2019-05-04 01:14:07 UTC,*** Bug 1548978 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 01:13:37 UTC,*** Bug 1548979 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 01:13:17 UTC,*** Bug 1548980 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 01:13:03 UTC,*** Bug 1548975 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 01:11:09 UTC,TREES ARE CLOSED FOR THIS.
1827727,2019-05-04 01:05:45 UTC,I can confirm
1827727,2019-05-04 01:05:29 UTC,See also https://github.com/mozilla/addons/issues/978
1827727,2019-05-04 00:53:43 UTC,List of affected add-ons:
1827727,2019-05-04 01:34:45 UTC,(In reply to Milos from comment #16)
1827727,2019-05-04 01:35:02 UTC,(In reply to Milos from comment #16)
1827727,2019-05-04 01:14:23 UTC,(In reply to Andreea Pavel [:apavel] from comment #4)
1827727,2019-05-04 01:45:18 UTC,(In reply to Alex from comment #20)
1827727,2019-05-04 05:21:33 UTC,"caitmuenster has also said this page will receive official updates/statuses on the issue:
https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047"
1827727,2019-05-04 05:15:01 UTC,"If you want to watch somewhere for user-facing updates on this issue, it looks like https://twitter.com/mozamo is the place to watch."
1827727,2019-05-04 03:56:38 UTC,*** Bug 1549009 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 03:45:26 UTC,*** Bug 1549008 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 03:35:11 UTC,*** Bug 1549006 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 03:31:36 UTC,*** Bug 1549004 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 03:30:38 UTC,*** Bug 1549003 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 01:39:01 UTC,"Stable, Beta, Nightly and Dev got hit for me."
1827727,2019-05-04 03:30:11 UTC,*** Bug 1549002 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 03:01:49 UTC,*** Bug 1548998 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 02:41:03 UTC,*** Bug 1548996 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 02:40:11 UTC,*** Bug 1548984 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 02:39:28 UTC,*** Bug 1548981 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 00:49:37 UTC,User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0
1827727,2019-05-04 02:31:19 UTC,*** Bug 1548993 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 02:27:56 UTC,*** Bug 1548986 has been marked as a duplicate of this bug. ***
1827727,2019-05-04 01:47:24 UTC,We have confirmed this issue. Extra comments about this being broken will not advance this bug to being fixed.
1827727,2019-05-04 03:29:54 UTC,*** Bug 1549000 has been marked as a duplicate of this bug. ***
1827731,2019-05-04 15:31:34 UTC,"This occurred after updating yesterday (May 3, 2019) through Canonical."
1827732,2020-05-14 06:20:15 UTC,"Check the version of python, only version 2 is ok.
You can edit the file /usr/bin/ocrfeeder, change the first line to ""#! /usr/bin/python2""."
1827733,2019-09-27 09:04:20 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1827733,2019-05-04 16:49:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657135"
1827733,2019-06-06 09:16:15 UTC,"Reviewed:  https://review.opendev.org/657135
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b7a7ac7b5af0eacb9bbf4144013ea93257043653
Submitter: Zuul
Branch:    master"
1827734,2019-05-04 16:54:28 UTC,"Note: it starts with the touch pad being de-activated, grows to the keyboard later, and then the USB devices."
1827734,2019-07-05 04:17:18 UTC,[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1827734,2019-05-05 06:55:36 UTC,"You can find the hashes in the same directory as the images:
http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/"
1827734,2019-05-05 06:23:06 UTC,"I couldn't find the hash info. The download came from here: https://lubuntu.me/downloads/
And yes I ran the check the first installation."
1827734,2019-05-05 05:48:42 UTC,I wasn't suggesting a bad keyboard. More an issue with a bus or the motherboard.
1827734,2019-05-05 05:27:00 UTC,This has occurred consistently with two different re-installs.
1827734,2019-05-05 03:13:54 UTC,"cpuinfo, I meant. Anyways, it's irrelevant at this point."
1827734,2019-05-05 02:55:04 UTC,"I re-installed everything... touchpad and keyboard are working at the moment.
(took a couple hours)"
1827734,2019-05-04 21:34:58 UTC,That's not exactly the same. Also you haven't answered all my questions. And here's another: would 19.04 not install or not boot?
1827734,2019-05-04 20:43:22 UTC,Here are the complaints of the same issue found in a google search: https://www.google.ca/search?source=hp&ei=g_fNXPnwKoywtQWXnqqYDg&q=Touchpad+and+keyboard+stop+working+in+Lubuntu&btnK=Google+Search&oq=Touchpad+and+keyboard+stop+working+in+Lubuntu&gs_l=psy-ab.3..33i22i29i30.11377.27473..28523...2.0..0.181.4268.32j14......0....1..gws-wiz.....6..35i39j0i67j0i131j0i10j0j0i20i263j0i22i30j0i22i10i30.7AVZv4m1USw
1827734,2019-05-04 20:29:51 UTC,"Other versions can work on low RAM but with that little, it's hardly usable for things like web browsing."
1827734,2019-05-04 20:16:19 UTC,"It is a Pentium 4 M 1.7Ghz 32bit processor.
Motherboard only supports 512MB RAM
Ram is at its max.
That is why I downloaded the 18.04.2 version - Not enough RAM for the others."
1827734,2019-05-04 19:57:40 UTC,"This is the first bug I've seen describing this issue and the first time I've heard it mentioned anywhere including support channels and mailing lists. Similarly, having been involved in the testing of Lubuntu for a long time, I've never seen this come up. That said, I'm convinced it's hardware related. At minimum, it's a quirk about the hardware you have that the software doesn't adequately handle, but it is not universal to all computers, laptops, etc."
1827734,2019-05-04 19:36:09 UTC,"I don't think it is hardware.  I can re-boot into Windows XP and it works fine.  The keyboard works in the menus on Lubuntu bootup, but quits before login."
1827734,2019-05-04 17:30:27 UTC,This is strange stuff that reeks of a hardware issue of some kind. Finding the solution without having the same hardware ourselves is going to be tricky.
1827734,2019-05-04 20:54:49 UTC,I already tried 19.04.  It will not install.
1827737,2019-05-04 20:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827737,2019-05-14 20:21:00 UTC,"Hi, I am running KDE neon and apport is not found."
1827738,2019-05-04 23:13:12 UTC,change package to xorg
1827738,2019-05-06 09:26:02 UTC,"My memory of X window management is a bit hazy, but I think the ""Map State"" and window state (one of which is ""IconicState"") are allowed to have different values for the same window."
1827738,2019-05-06 09:32:04 UTC,"> The big problem is that graphical applications cannot distinguish their current state.
> If this is not a bug, then please give advice in how to query the iconified state.
"
1827738,2019-05-06 09:33:00 UTC,To do the same in code you need to use:
1827738,2019-05-06 09:41:15 UTC,But again that will only tell you if the window is iconified.
1827738,2019-05-07 08:29:33 UTC,Also the documentation you point to states:
1827738,2019-05-07 08:52:38 UTC,Thanks.
1827741,2019-05-04 20:55:41 UTC,"After this error, removing the Default-Release config and starting `update-manager -c` again shows a popup ""Failed to load the package list"". Clicking ""ok"" shows a spinner that takes some time and then offers a partial upgrade, which looks reasonable (but has not finished yet)."
1827741,2020-01-30 12:48:31 UTC,"This is still an issue: Just started the disco -> eoan upgrade through the GUI prompt I got, which broke on, I think, the second step (setting up software sources IIRC). A systray icon showed up saying there was a problem with the package manager (saying 'disco', which I have now configured as the default-release, is not a valid distribution)."
1827741,2020-01-30 14:48:33 UTC,"Just finished the upgrade without problems, so just disabling the default-release temporarily seems to be sufficient. Would be nicer if the upgrade somehow handled this, even if just detecting that it was set and bailing out before rather than during the upgrade and allow the user to unset it manually."
1827741,2020-08-16 12:53:14 UTC,"This is still a problem: I wanted to upgrade from eoan to focal and forgot about this bug, so the upgrade failed again (I think it actually crashed this time, the GUI window disappeared, but I accidentally dismissed the ""send report"" prompt, so I'm not sure how exactly)."
1827742,2019-05-04 21:50:12 UTC,Makes sense.
1827744,2019-05-04 22:16:10 UTC,"FWIW, it looks to me that the introduction of monkey_patching in lp#1787331 to run asynchronous tasks under mod_wsgi is not a good idea because IMHO the concurrency model of mod_wsgi was not designed to do that."
1827744,2019-06-03 11:14:50 UTC,"Change abandoned by Damien Ciabrini (<email address hidden>) on branch: master
Review: https://review.opendev.org/657168
Reason: Abandoning the review since removing monkey-patch is not working and is not the solution as agreed."
1827744,2019-05-04 22:04:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657168"
1827746,2019-05-04 21:36:42 UTC,"If nova would allow an admin to `force` an unbind, but still queue all the standard cleanup in nova, would that solve this? Is that unreasonable?"
1827746,2019-05-05 11:41:45 UTC,"The detach-interface is an RPC cast (async) to the nova-compute. When the nova-compute is down the RCP message waits in the queue to be processed. So when the compute comes up it will get the message and detach the interface successfully (I've tested in devstack). In theory nova-api could detect if the compute is down and can unbind the port in neutron (and maybe also de-allocate the resources in placement) if the compute is down. Then nova-api would still cast to the compute to make sure when the compute is up, it can detach the vif from the server."
1827746,2019-05-07 21:17:37 UTC,"I agree with gibi, it sounds like we could do something similar to ""local delete"" (when nova-compute is down and delete is requested, we deallocate ports, volumes, and placement resources) in nova-api for the detach-interface API. There might be some resistance to the idea as ""local delete"" has been a popular source of bugs in the past. But as always, it's a tradeoff, and if detach-interface while nova-compute is down is a greater pain point, it might be worth adding a ""local detach"" ability."
1827746,2019-05-13 23:31:18 UTC,Yeah I think it'd work fine with neutron understanding where the port should be bound correctly.
1827746,2019-07-05 13:35:10 UTC,it depnes on how the comptue node is down and if the queue still exists wheater it would get cleand up eventualy. until https://bugs.launchpad.net/oslo.messaging/+bug/1661510 is fix i dont think we can assume that it will definetly get recived and acted on when the compute node comes back up.
1827746,2019-07-05 13:39:18 UTC,"given a workaround to the quota issue would be to delete the server and or loadbalancer and recreate in this case
i would normally set this to low.  given the implication that that would be problematic in an octavia context ill mark it as medium but it would be good if you could add context as to why that is not recommended for octavia related instances. i would have assumed you could jsut delete the port and remove it form the load blancer and then re add the port somewhere else."
1827746,2019-07-05 15:53:41 UTC,"Sean, I'm not sure I can follow your last comments."
1827748,2019-09-15 15:30:00 UTC,Migrated to https://github.com/widelands/widelands/issues/2137
1827749,2019-09-15 15:45:26 UTC,Migrated to https://github.com/widelands/widelands/issues/1729
1827750,2019-07-22 20:18:54 UTC,This bug was fixed in the package linux-raspi2 - 5.0.0-1013.13
1827750,2019-07-22 10:55:58 UTC,This bug was fixed in the package linux-raspi2 - 4.15.0-1041.44
1827750,2019-05-13 01:21:28 UTC,"FYI the mainline arm64 kernels at https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.1/ boot on the 3B running arm64 on disco, with grub-efi-arm64-bin installed and a commandline of modprobe.blacklist=vc,vc4 (but I haven't tried without using the module blacklist for some time.)"
1827750,2019-05-20 21:29:26 UTC,"Take care, current kernel 4.15.0-1036.38 still not bootable with EFI."
1827750,2019-05-08 06:39:13 UTC,"Copied out that package, try again."
1827750,2019-05-08 05:39:58 UTC,Dependency error of linux-headers-4.15.0-1035-raspi2 package. This is required itself.
1827750,2019-05-07 14:22:53 UTC,Please test this kernel and tell us if it solves you problem:
1827750,2019-05-08 07:35:32 UTC,"System started, but I can't parse temperature. CPU freq info work fine."
1827751,2019-07-01 09:15:20 UTC,I am redirected here from gnome-shell/+bug/1834817
1827751,2020-03-02 11:21:16 UTC,This bug was fixed in the package gnome-shell - 3.35.91-1ubuntu2
1827751,2019-11-04 16:58:14 UTC,Quoting Florian Müllner from https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/767#note_627334:
1827751,2019-07-01 10:54:39 UTC,"1. Settings>Power>Blank Screen was OFF, but switched this back ON then OFF again
2. The randomness of the blanking period between 15-30 min suggested issue was with ScreenLock
3. ScreenLock (per this bug) is tied to screen blanking
4. GitHub upstream considering 3 options on screen blanking like Android (nothing, lock, hibernate)
5. Screen Lock in my case was a symptom of what appears to be a glitch in screen blanking
6. Toggling screen blanking ON/Off resolved my issue"
1827751,2019-07-01 10:01:31 UTC,"This is a clean system - nothing but default packages. Streaming video in Firefox.
Happy to run commands to provide you what you need to know."
1827751,2019-07-01 09:25:59 UTC,Playing movies should prevent the screen from blanking. If it doesn't then please log a bug against the video player you are using. If you are using Wayland sessions then it is mutter bug 1740771.
1827751,2019-05-23 00:52:06 UTC,Thank you for the update and the explanation.  I will post some feedback on gitlab.
1827751,2019-05-13 16:06:50 UTC,"My mistake, it is still present.  I just wasn't waiting long enough after the screen blank before waking the screen up.  Waited a bit and it is back, even with the extension running."
1827751,2019-05-18 17:02:26 UTC,"Correction: I have to push the Enter key to dismiss the screen, not any other key."
1827751,2019-05-18 12:55:29 UTC,Here is the screen capture with the background settings.
1827751,2019-05-18 12:54:10 UTC,"Sorry, but I am not sure I could tell the difference so I will try and describe it as best I can."
1827751,2019-05-16 15:46:52 UTC,"What do you call ""lock screen""? Do you have to enter your password or do you only mean the ""banner"" screen?"
1827751,2019-05-12 02:26:13 UTC,Also tried editing /etc/default/acpi-support and commenting out the line LOCK_SCREEN=true.  That did not work.
1827751,2019-05-06 02:08:07 UTC,"This sounds like a bug I have heard reported elsewhere, but can't find the other reports right now."
1827751,2019-05-21 09:01:07 UTC,"Thanks for the details, the screen is not locked in your case.
That has been reported upstream as https://gitlab.gnome.org/GNOME/gnome-shell/issues/681
You might want to comment on the gitlab to explain why you find it disturbing"
1827752,2020-05-18 09:45:38 UTC,"Changed the issue to ""Fix Released"" since it was most likely a hardware fault. The laptop needed an RMA since it was shutting off at random, after returning from RMA the hibernation issue also disappeared."
1827752,2020-05-18 09:43:58 UTC,Most likely a hardware fault (or the issue was solved recently in the kernel)
1827752,2019-05-05 01:30:06 UTC,This change was made by a bot.
1827752,2019-05-26 23:41:28 UTC,"I'm not entirely sure but it was before the 19.04 kernel releases, during 18.10. But even then it had issues since it would wake up by itself after some time."
1827752,2019-05-27 03:38:34 UTC,"Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc2/"
1827752,2019-05-20 05:14:53 UTC,What was the kernel version that can do S3 successfully?
1827753,2019-09-27 19:19:55 UTC,"@chaitrex, while it's not an acutal fix, modprobe does filter out duplicate named files in the modprobe.d search list, and /lib/modprobe.d is at the end of the list; so if you simply copy /lib/modprobe.d/fbdev-blacklist.conf to /etc/modprobe.d/fbdev-blacklist.conf, then you can edit the file in /etc/modprobe.d and the contents of the file in /lib/modprobe.d will be ignored by any calls to modprobe.  Upgrading the udev package will also not touch the /etc/modprobe.d/fbdev-blacklist.conf file since it did not place it there."
1827753,2019-09-27 19:23:42 UTC,"@rbalint, I think @chaitrex has a point in this bug that /lib/modprobe.d/fbdev-blacklist.conf isn't end-user editable without being overwritten by udev package update."
1827753,2019-10-02 13:12:59 UTC,"@chaitrex, IMO the workaround proposed by @ddstreet in #2 is the simplest solution, overriding default configuration by placing a configuration in /etc and this also follows the general concept of how systems should be configured.
The big miss here is not having the behavior documented in modprobe.d(5)."
1827755,2019-08-30 05:40:24 UTC,"------- Comment From <email address hidden> 2019-08-30 01:32 EDT-------
It works on the -proposed kernel for xenial.  I'm not sure if I was hitting the issue on the -159 kernel, but the test does pass now."
1827755,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1827755,2019-06-24 06:51:54 UTC,"I tested it and it looks good:
root@ltc-boston25:/home/ubuntu/comp_selftest# insmod comp_selftest.ko
root@ltc-boston25:/home/ubuntu/comp_selftest# ./testit
root@ltc-boston25:/home/ubuntu/comp_selftest# dmesg |tail
[   10.561010] audit: type=1400 audit(1561358069.720:8): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/NetworkManager/nm-dhcp-helper"" pid=3496 comm=""apparmor_parser""
[   10.561014] audit: type=1400 audit(1561358069.720:9): apparmor=""STATUS"" operation=""profile_load"" profile=""unconfined"" name=""/usr/lib/connman/scripts/dhclient-script"" pid=3496 comm=""apparmor_parser""
[  920.103139] comp_selftest: loading out-of-tree module taints kernel.
[  920.103358] comp_selftest: module verification failed: signature and/or required key missing - tainting kernel
[  931.871741] compression self test starting
[  931.871744]   compressor: 842-nx
[  931.871745]   repeat: Y
[  931.871745]   threads: 16
[  931.871747]   offsets 0-0/1, 0-0/1, 0-0/1
[  931.871749]   lengths 10000-10000/1, 10000-10000/1, 10000-10000/1
root@ltc-boston25:/home/ubuntu/comp_selftest# cat /sys/kernel/debug/comp_selftest/status
^Creads 16 MBps: 47121/42300 peak 47786/47470 off 0/0/0 len 10000/10000/10000
root@ltc-boston25:/home/ubuntu/comp_selftest# cat /proc/version
Linux version 4.15.0-53-generic (buildd@bos02-ppc64el-009) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #57-Ubuntu SMP Thu Jun 13 09:28:40 UTC 2019
root@ltc-boston25:/home/ubuntu/comp_selftest#"
1827755,2019-06-18 16:02:53 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1827755,2019-05-29 16:12:51 UTC,Changing to Fix Committed since the patch got applied.
1827755,2019-08-28 06:29:31 UTC,"------- Comment From <email address hidden> 2019-08-28 02:19 EDT-------
I did successfully check the HWE kernel on Xenial, but should have access to a p8 tomorrow to check against the standard kernel."
1827755,2019-05-20 19:39:19 UTC,"------- Comment From <email address hidden> 2019-05-20 15:29 EDT-------
We need this fix in 18.04.X. Without these patches, 842 compression is broken which can affect zswap or other workloads that can exploit HW compression. Simple fix which modifies only NX module"
1827755,2019-05-22 17:14:36 UTC,"Patch submitted for SRU:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100825.html"
1827755,2019-05-13 14:28:51 UTC,"Next steps: IBM to verify if this issue is already resolved in 19.04, and report back to this bug."
1827755,2019-05-16 17:29:18 UTC,"------- Comment From <email address hidden> 2019-05-16 13:25 EDT-------
This issue is already resolved in 19.04.  For 18.04 I verified adding the second commit:
656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca
fixes the problem:"
1827755,2019-08-22 16:17:23 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1827755,2019-05-20 12:54:04 UTC,I have backported the patch and built a test kernel in ppa:ubuntu-power-triage/lp1827755 could you please verify that this kernel works for you?
1827755,2019-05-20 14:12:51 UTC,"IBM is also working on a justification for this patch, that they are planning to add to this bug."
1827755,2019-05-20 19:19:24 UTC,"------- Comment From <email address hidden> 2019-05-20 15:09 EDT-------
I tried that kernel out and it works:
root@ltc-boston25:/home/ubuntu/comp_selftest# cat /proc/version
Linux version 4.15.0-51-generic (buildd@bos02-ppc64el-003) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04)) #55~lp1827755+build.1-Ubuntu SMP Fri May 17 18:53:29 UTC 2019
root@ltc-boston25:/home/ubuntu/comp_selftest# insmod comp_selftest.ko
root@ltc-boston25:/home/ubuntu/comp_selftest# ./testit
root@ltc-boston25:/home/ubuntu/comp_selftest# dmesg |tail
<snip>
[  354.958178] comp_selftest: loading out-of-tree module taints kernel.
[  354.958396] comp_selftest: module verification failed: signature and/or required key missing - tainting kernel
[  361.124620] compression self test starting
[  361.124623]   compressor: 842-nx
[  361.124624]   repeat: Y
[  361.124625]   threads: 16
[  361.124627]   offsets 0-0/1, 0-0/1, 0-0/1
[  361.124630]   lengths 10000-10000/1, 10000-10000/1, 10000-10000/1
root@ltc-boston25:/home/ubuntu/comp_selftest# cat /sys/kernel/debug/comp_selftest/status
^Creads 16 MBps: 45192/39510 peak 45509/43884 off 0/0/0 len 10000/10000/10000
root@ltc-boston25:/home/ubuntu/comp_selftest#"
1827757,2019-11-15 21:09:47 UTC,Can confirm that this problem still exist on the latest LTS release.
1827757,2019-11-15 21:14:36 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827757,2019-11-15 21:18:19 UTC,Tests were performed with Intel Dual Band Wireless-AC 7265 card.
1827757,2019-11-16 01:43:07 UTC,"A better workaround solution to this problem is the systemd wpa_supplicant.service override.
This is better than messing with broken packages and versions."
1827759,2020-05-13 22:44:10 UTC,Thanks for posting this bug. It's occurring for me as well. I fixed it with a default POSIX ACL on the /var/lib/command-not-found directory.
1827759,2020-05-14 14:13:09 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827759,2020-05-16 01:46:48 UTC,Thanks!
1827761,2019-05-20 09:36:00 UTC,"Reviewed:  https://review.opendev.org/654727
Committed: https://git.openstack.org/cgit/openstack/oslo.policy/commit/?id=f2e642a180aa31ba25f42fcd1a488540ee185ef4
Submitter: Zuul
Branch:    master"
1827761,2019-08-08 21:42:52 UTC,This issue was fixed in the openstack/oslo.policy 2.3.0 release.
1827762,2019-05-05 07:50:23 UTC,"Klaus can you test the linked branch, please? Also, Gun apparently had a crash with that branch. Can you try to reproduce this?"
1827762,2019-05-05 08:56:38 UTC,Duplicate of #1827749
1827762,2019-09-15 15:44:41 UTC,Migrated to https://github.com/widelands/widelands/issues/1730
1827763,2019-09-17 07:26:42 UTC,Migrated to https://github.com/widelands/widelands/issues/3426
1827764,2019-05-06 07:49:10 UTC,"Thank you for your bug report. That seems like an upstream issue, could you report it to them on https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues ?"
1827764,2019-05-11 06:09:32 UTC,thank you.
1827767,2019-05-05 09:00:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827767,2019-05-05 09:34:33 UTC,Fixed for the future in Eoan 19.10 with:
1827767,2019-05-05 09:58:52 UTC,This bug was fixed in the package ktouch - 4:19.04.0-0ubuntu2
1827767,2019-05-23 06:05:40 UTC,Thanks for taking care of this!
1827767,2019-06-04 18:04:18 UTC,"Hello Kuh, or anyone else affected,"
1827767,2019-06-06 17:59:08 UTC,"Yes, I have verified that the new version in disco-proposed, namely version 4:18.12.3-0ubuntu1.1 does indeed work again!"
1827767,2019-06-12 20:38:08 UTC,This bug was fixed in the package ktouch - 4:18.12.3-0ubuntu1.1
1827767,2019-06-12 20:38:15 UTC,"The verification of the Stable Release Update for ktouch has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827768,2019-05-05 08:41:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657213"
1827768,2019-05-05 08:47:54 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/657215"
1827768,2019-05-20 14:42:44 UTC,"Reviewed:  https://review.opendev.org/657213
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=fd000b8c131b3b5d23d2c45233353107536565e1
Submitter: Zuul
Branch:    master"
1827768,2019-05-22 02:06:17 UTC,"Reviewed:  https://review.opendev.org/657215
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=fc2586e852a6d308719cb668c785147a672341a2
Submitter: Zuul
Branch:    stable/stein"
1827768,2019-09-26 09:16:36 UTC,This issue was fixed in the openstack/ceilometer 13.0.0.0rc1 release candidate.
1827768,2020-02-27 12:49:44 UTC,This issue was fixed in the openstack/ceilometer 12.1.0 release.
1827770,2019-07-06 04:17:20 UTC,[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]
1827770,2019-05-06 06:08:12 UTC,It's a stock Ubuntu 19.04 installation with the default GNOME 3 + Ubuntu dock environment. The only thing I have changed is that Chrome is my default browser.
1827770,2019-05-06 05:13:03 UTC,I can't reproduce the behavior with Gnome shell (and Dash to dock extention). What kid of desktop environment and dock application is this?
1827770,2019-05-06 06:09:30 UTC,This screenshot shows the issue occurring where Firefox and Chrome are both grouped under the Slack icon
1827771,2019-05-06 12:39:26 UTC,"Am I understand right that this is a scaling operation, when you add a new host where you start dhcp-agent?"
1827771,2019-05-07 01:38:41 UTC,"Yes, this bug only affect on the first start of neutron-dhcp-agent for the new network node, the second start will sync all the network data on the node because the first start has already registered this agent to neutron-server."
1827771,2019-05-08 12:28:54 UTC,"I reproduced it with multihost devstack and even if I use dhcp_agents_per_network = 2, if I delay _report_state the namespaces will not be created."
1827773,2019-11-21 07:15:44 UTC,@jp-charras input pins do not generate this ERC message so the suggested rewording might actually be a good idea. Tested with 5.1.4 so this rewording could potentially even be done in v5.1.x
1827773,2019-05-06 22:39:48 UTC,@Jon-  This report appears to be a case of users not fully understanding the error and its causes/solutions.  Perhaps this is best addressed by documentation?  I'd hate to change this out from under our users who have already learned how to interact with this error.
1827773,2019-05-06 15:32:16 UTC,"OP has also mentioned this on the user forum:
https://forum.kicad.info/t/getting-random-erc-errors/16811"
1827773,2019-05-06 22:03:16 UTC,An alternative would be to suppress the error if the wire is connected to a connector and assume that power or a signal is being received from the connector pin.
1827773,2019-05-06 22:02:03 UTC,"Since this can apply to any input pin as well, I will restate that one must be able to configure connector pins as input, output, power, etc."
1827773,2019-05-06 22:00:20 UTC,"I have actually created at least a dozen boards with KiCad. This is the first time I have run into this, however."
1827773,2019-05-06 18:48:48 UTC,"So the new message only acounts for the most confusing instances, and is easy to distinguish from the others by the inclusion of (at least one) power pin in the net..."
1827773,2019-05-06 16:03:49 UTC,"Just renaming does not work:
The ERC message is not specific to power pins, this ERC warning happens every time an input pin is not driven, i.e. not connected to an output or something similar."
1827773,2019-05-06 15:38:28 UTC,"Or, state the problem and add the solution:
""This net has power input pins, and must also be connected to an power output pin or PWR_FLAG""."
1827773,2019-05-05 22:00:53 UTC,"@Aaron, a wish list item already exists for that: https://bugs.launchpad.net/kicad/+bug/1526213
Click the ""Does this bug affect you?"" to increase the 'heat'."
1827773,2019-05-05 11:38:15 UTC,"I get the following:
ERC report (Sun 05 May 2019 04:36:56 AM PDT, Encoding UTF8 )"
1827773,2019-05-05 21:19:10 UTC,https://forum.kicad.info/t/errtype-3-pin-connected-to-some-others-pins-but-no-pin-to-drive-it/10946
1827773,2019-05-05 20:57:27 UTC,How do I go about setting this flag? I am unable to edit the connector pin properties.
1827773,2019-05-05 20:10:47 UTC,"I looked at it a bit more, these errors are coming from the fact that your +5V and GND nets are coming from an off-board connector (so no pins on the nets are set as outputs) You can add PWR_FLAG components to the affected nets to get rid of them.  I'm going to think about if there is any way to make this more intuitive for V6."
1827773,2019-05-05 19:48:41 UTC,"Are there any suggestions on how I can ""fix"" my design, or should I just ignore this?"
1827773,2019-05-05 13:18:00 UTC,I can ensure this is fixed for 6.0 as I will be moving the pin-to-pin ERC checks to use the new connectivity algorithm.  If this is to be fixed for 5.x it will need to be investigated in the old algorithm
1827773,2019-05-05 13:16:00 UTC,"I can confirm that ERC errors are generated that I don't think should be.  The two instances of ""pin connected but not driven"" should not be there."
1827773,2019-05-05 11:38:48 UTC,"I might also add that the pcb layout is working, unlike my first post, though I'm early in the process."
1827773,2019-05-05 11:36:41 UTC,"My mistake in reporting, I was going from memory. The errors say ""Pin connected to other pins, but not driven by any pin"" which is incorrect."
1827773,2019-05-05 11:18:25 UTC,"I am not seeing a ERC error saying a pin is unconnected.
It is the opposite: it says the pin is connected."
1827773,2019-05-05 21:34:41 UTC,"Ideally it would be nice if each pin on a connector could be configured like in the symbol editor to specify if it's power input, power output, input, output, bidirectional, etc."
1827774,2019-05-05 11:14:30 UTC,"and i can add scope link to route table 200 via ip command:
sudo ip route add 10.10.56.0/21 dev eno1 scope link table 200"
1827778,2020-05-27 14:57:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827778,2020-05-27 15:00:06 UTC,I can confirm this behaviour. The current setup requires me to crawl behind my computer and unplug and re-plugin external HDDs after they have been safely removed.
1827778,2020-05-27 15:28:35 UTC,If you are interested in a workaround...
1827780,2019-05-05 14:07:44 UTC,"Please if you file a new bug, try to use ubuntu-bug yourpackage
so the bug report can collect your system info and the developers
can track your issue down the best way possible."
1827780,2019-05-05 14:42:22 UTC,"Hi, since I do not know the exact cause of this, I could not specifically list a package"
1827781,2019-05-05 13:30:53 UTC,I think the first request is covered by existing issues:
1827781,2019-05-05 14:23:49 UTC,Updating this to focus on #2 since I can't find a duplicate in the bug tracker for it.
1827781,2019-05-05 16:14:44 UTC,Thank you Jon :-)
1827781,2019-05-05 17:07:23 UTC,I think the clustering by sheet is already in kicad. (unless it has been removed since i last layed out a board sometime between 5.0 and 5.1 using a nightly build)
1827781,2019-05-05 17:14:25 UTC,"I guess you are right, I think that is a side-effect of the netlist from eeschema coming in with components ordered by sheet."
1827781,2019-05-05 17:56:15 UTC,"Well, this is not a side effect: they are grouped by sheet path since a long time."
1827781,2019-05-05 18:46:17 UTC,So you propose to use schematic sheets and then the components will be arranged according to the schematic sheets? So far I placed everything on one sheet - especially then you group components by function..
1827782,2019-08-17 04:17:22 UTC,[Expired for clamav (Ubuntu) because there has been no activity for 60 days.]
1827782,2019-06-17 09:38:19 UTC,"Thank you for your follow-up. This looks like a local configuration issue, rather than a bug in Ubuntu. You can find pointers to get help for this sort of problem here:"
1827782,2019-06-16 17:11:14 UTC,"Hello,"
1827782,2019-05-20 10:40:18 UTC,"I have just one problem,"
1827782,2019-05-15 21:00:08 UTC,"Sorry, what do you mean?"
1827782,2019-05-19 13:08:56 UTC,"Hello,"
1827782,2019-05-13 12:28:07 UTC,Hello I set up the first ask for add what missing ;)
1827782,2019-05-06 19:19:17 UTC,Thanks for filing this bug in Ubuntu.
1827782,2019-05-20 10:06:28 UTC,"Hello Dorian, just to be sure: did you solve the problem for which your filed this report? Can we close it? Thank you."
1827785,2019-05-05 14:11:23 UTC,Actually after closing the kicad it was able to find the footprint library.
1827785,2019-05-06 06:38:31 UTC,Symbol libs are loaded when opening either eeschema or the symbol editor.
1827785,2019-07-06 04:17:24 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1827786,2019-05-06 08:06:31 UTC,We should also add a password mode to the Editbox class that will show *** instead of the actual text.
1827786,2019-09-15 15:29:22 UTC,Migrated to https://github.com/widelands/widelands/issues/2138
1827787,2019-05-22 20:40:37 UTC,It looks like the KiCad janitor missed this.
1827787,2019-05-05 16:51:09 UTC,Nice. Thanks.
1827787,2019-05-05 15:36:28 UTC,I’ll milestone for 6.0.0-rc1 as this will probably be fixed already in eemodern.
1827787,2019-05-05 15:27:40 UTC,"Application: kicad
Version: (5.1.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013"
1827787,2019-05-05 15:04:16 UTC,Please copy the full version information from About KiCad -> Copy Version Info.
1827787,2019-05-05 16:12:22 UTC,This affects 5.1.2.  It should be fixed in the 5.1 branch even though eeschema in the master branch is well under way to modern toolset completion and may have already been fixed.  The 5.1 branch will continue to get bug fixes until 6.0.0 is released.
1827788,2019-05-10 23:42:54 UTC,"I have committed a tiny ""Community support"" page, which I think can be considered to address this bug:"
1827788,2019-07-09 05:17:48 UTC,"Thank you very much for all your work!!
here a screenshot of 19.10 ubuntu-docs patched"
1827788,2019-06-28 16:57:32 UTC,This bug was fixed in the package ubuntu-docs - 19.10.1
1827788,2019-05-31 10:14:59 UTC,It will enter 19.10. Not important enough to struggle with translations to make a backport possible.
1827788,2019-05-31 09:15:14 UTC,"@gunnarhj will the fix enter 19.10 or be backported to older ubuntu releases aswell?
just to know what to look for"
1827788,2019-05-07 05:15:14 UTC,"@8 Gunnar its a great idea to forward that community page, as long as its linked from the ubuntu-docs
so users can find this easy"
1827788,2019-05-06 16:47:44 UTC,Thanks for your report!
1827788,2019-05-06 17:06:23 UTC,"RE: Comment #6, Ubuntu Studio also has the website with an IRC link."
1827788,2019-05-06 14:00:33 UTC,"Confirmed kubuntu opens a browser from online help and howto irc, see screenshot"
1827788,2019-05-06 08:09:40 UTC,"Confirmed ubuntu-studio help docs have irc support as resource the help icon opens a browser to the manuals, see screenshot"
1827788,2019-05-06 08:01:52 UTC,"Ubuntu-budgie has the same ubuntu-docs as ubuntu-desktop no irc support, see screenshot"
1827788,2019-05-06 07:20:31 UTC,"Confirmed the ubuntu mate docs have irc support as resource, see the screenshot"
1827788,2019-05-06 03:37:43 UTC,"Confirmed the Xubuntu-docs have the irc support as resource, see screenshot"
1827788,2019-05-06 17:07:03 UTC,"RE: Comment #6, Ubuntu Studio also has a direct link to IRC in the menu."
1827788,2019-05-05 15:05:42 UTC,"Marking as confirmed/wishlist. The #ubuntu channel in Freenode (and the #lubuntu, #kubuntu, #xubuntu, #ubuntu-mate, #ubuntustudio channels -- there are probably others as well) are quite known as support channels."
1827791,2019-05-06 17:49:17 UTC,apport information
1827791,2019-05-06 17:49:18 UTC,apport information
1827791,2019-05-06 17:55:06 UTC,"(OK, I ran apport-collect 1827791 but that didn't seem to add much, so I ran apport-collect --package=xorg 1827791 and that added all of the output that was originally added)."
1827791,2019-05-06 19:13:12 UTC,I forgot to reply to the question about Gnome Shell extensions.
1827791,2019-05-07 02:28:35 UTC,Thanks for all that.
1827791,2019-05-12 11:51:09 UTC,"Hi Daniel,"
1827791,2019-05-13 02:07:56 UTC,Thanks.
1827791,2019-07-20 04:17:32 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1827791,2019-05-21 02:22:27 UTC,"Yes those messages themselves are safe, but I think they may suggest the kernel got stuck for a while (somewhere, anywhere). And that would correlate with this bug."
1827791,2019-05-06 17:49:15 UTC,apport information
1827791,2019-11-21 12:10:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827791,2020-01-24 09:52:24 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1827791,2020-01-24 10:19:13 UTC,Please re-open this bug report. I confirm this issue on a Dell XPS 13 9380 with 16GB RAM.
1827791,2020-01-24 10:20:38 UTC,Note that I am using Ubuntu 18.04 LTS which is not end-of-life.
1827791,2020-01-28 02:23:38 UTC,"sander,"
1827791,2019-05-13 18:49:15 UTC,This sounds very much like what I tried to describe in #1826219; also on a Dell XPS 13. Subscribing.
1827791,2019-05-06 17:49:12 UTC,apport information
1827791,2019-05-20 21:35:17 UTC,"In comment 28, the freeze happened just before taking the log, yet the last log entry was from ~1 minute earlier, so it doesn't look like there were any relevant log entries."
1827791,2019-05-06 17:49:09 UTC,apport information
1827791,2019-05-06 17:49:11 UTC,apport information
1827791,2019-05-06 02:13:53 UTC,"Please check that you haven't installed any gnome-shell extensions. If you have then please uninstall them all, reboot and retest."
1827791,2019-05-06 02:15:29 UTC,"Also, the attached kernel log shows ath10k (wifi driver) crashing a couple of times. I'm not sure if that could lead to any shell freezes though."
1827791,2019-05-06 02:19:13 UTC,"Also, your Xorg log shows the mouse ""BM30X mouse"" repeatedly disconnecting and reconnecting, which may cause the whole screen to freeze briefly because it is in Xorg. Please try removing that mouse from the machine and tell us if that fixes the bug."
1827791,2019-05-06 17:23:32 UTC,"Hi Daniel,"
1827791,2019-05-06 17:42:55 UTC,apport information
1827791,2019-05-06 17:42:57 UTC,apport information
1827791,2019-05-06 17:48:51 UTC,apport information
1827791,2019-05-06 17:42:56 UTC,apport information
1827791,2019-05-06 17:48:56 UTC,apport information
1827791,2019-05-06 17:48:57 UTC,apport information
1827791,2019-05-06 17:49:00 UTC,apport information
1827791,2019-05-06 17:49:01 UTC,apport information
1827791,2019-05-06 17:49:03 UTC,apport information
1827791,2019-05-06 17:49:04 UTC,apport information
1827791,2019-05-06 17:49:06 UTC,apport information
1827791,2019-05-06 17:49:08 UTC,apport information
1827791,2019-05-06 17:48:53 UTC,apport information
1827792,2019-08-01 19:25:03 UTC,"Simotsa, have you resolved this issue? if not can you try deleting the bible database file."
1827792,2019-08-02 01:53:49 UTC,"Thank you,"
1827792,2019-08-03 07:08:08 UTC,This error is caused because we assume that the book name is the same as that used in the url.
1827795,2019-05-10 07:22:21 UTC,I think we should do 2 things here:
1827795,2019-09-17 07:26:13 UTC,Migrated to https://github.com/widelands/widelands/issues/3427
1827795,2019-05-07 21:20:20 UTC,"Yeah, and i have the same opinion as you: The player should be able to manage the economy (and less automatically managing by the engine)."
1827795,2019-05-07 05:52:30 UTC,See bug 1075562 starting from comment 41.
1827795,2019-05-07 16:10:12 UTC,"Hm, that is a completely different aspect you mentioned and that was discussed (how many and when to produce trainers and initial trainer count).
(Btw: I was not blocked in any form in the Tutorial mission and the axe prodcution was already ongoing...)"
1827795,2019-05-06 09:45:50 UTC,"Hm, i missed that discussion.
But it does make no sense that a building requests wares first and the main worker second?"
1827795,2019-05-07 16:42:36 UTC,As said i am not against your suggestion :)
1827795,2019-05-06 08:44:44 UTC,This was discussed several times and we endet in the solution to add 3 trainers to the starting conditions. The conclusion was that only experienced players may need more than 3 buildings which need a trainer. And experienced players should be able to find the way to get an additional trainer (e.g. by just reducing the amount of axes in the barracks).
1827796,2020-05-22 04:17:39 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1827804,2019-05-05 22:01:20 UTC,Thanks for the report!
1827804,2019-05-06 00:00:50 UTC,Terrific!  Thanks for the quick response!
1827806,2019-05-14 08:33:56 UTC,"This is not worth the effort for me personally. If some one else wants to implement it, I will  be happy to supply any needed guidance. If so, re-open the ticket and we can discuss it."
1827807,2019-12-05 19:18:46 UTC,"related: lp:1811300
""drag'n'drop from hot/cue button to Play triggers [Channel],play"""
1827809,2019-05-20 04:45:33 UTC,Is the keyboard backlight on in display manager?
1827809,2019-05-20 07:30:37 UTC,"> Is the keyboard backlight on in display manager?
"
1827809,2019-06-25 04:50:29 UTC,i.e. Is the backlight on before login?
1827809,2019-07-03 10:10:57 UTC,"> i.e. Is the backlight on before login?
"
1827810,2020-09-17 03:30:04 UTC,"It happens in 20.04 too, so it could eventually be a Nouveau bug."
1827810,2019-05-06 00:22:55 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1827810,2019-05-12 21:03:27 UTC,Looks like a nouveau driver bug.
1827810,2020-09-17 00:23:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827811,2019-05-29 23:09:47 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10061"
1827811,2019-09-19 21:28:42 UTC,"Gerrit/Patchset: https://reviews.mahara.org/#/c/10355/2
Browser tested: Firefox only at present
Theme used: Raw"
1827811,2019-09-25 04:49:00 UTC,"Reviewed:  https://reviews.mahara.org/10304
Committed: https://git.mahara.org/mahara/mahara/commit/953a5eab46711322c071b7f4b25bf7431b14a4ed
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-25 04:49:01 UTC,"Reviewed:  https://reviews.mahara.org/10285
Committed: https://git.mahara.org/mahara/mahara/commit/b82df03d4b572aeaebdc690dccc634f953957d31
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-25 04:49:01 UTC,"Reviewed:  https://reviews.mahara.org/10157
Committed: https://git.mahara.org/mahara/mahara/commit/e6b6ecf9186d0f2bd9137da3ee5af105595126c9
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-25 04:49:01 UTC,"Reviewed:  https://reviews.mahara.org/10204
Committed: https://git.mahara.org/mahara/mahara/commit/79201b7d8a132a0b6f95a95f8e1ebfda71f092be
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-25 04:49:01 UTC,"Reviewed:  https://reviews.mahara.org/10299
Committed: https://git.mahara.org/mahara/mahara/commit/fb47b83103355158ec0646f8cc4d38b7408562f4
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-25 04:49:01 UTC,"Reviewed:  https://reviews.mahara.org/10283
Committed: https://git.mahara.org/mahara/mahara/commit/44fcc9c9f72e7a6a3605b795ec0365eafd5a6d0a
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-25 04:49:01 UTC,"Reviewed:  https://reviews.mahara.org/10189
Committed: https://git.mahara.org/mahara/mahara/commit/1885a18de3123509a4471de9ed1c680418be0de0
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-18 03:11:04 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10355"
1827811,2019-09-25 04:49:02 UTC,"Reviewed:  https://reviews.mahara.org/10102
Committed: https://git.mahara.org/mahara/mahara/commit/f7431a3a3034f5822727f0ab217d1dd9736beeaf
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-25 04:49:02 UTC,"Reviewed:  https://reviews.mahara.org/10162
Committed: https://git.mahara.org/mahara/mahara/commit/8df0061e76191227e27da29e50c8edf62f0ffa24
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-25 04:49:02 UTC,"Reviewed:  https://reviews.mahara.org/10061
Committed: https://git.mahara.org/mahara/mahara/commit/be7af61faa0f8cae4ccf72b53d29a10885ae1746
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-26 23:57:19 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10382"
1827811,2019-10-01 02:10:33 UTC,"Reviewed:  https://reviews.mahara.org/10355
Committed: https://git.mahara.org/mahara/mahara/commit/f5ca6b3aa22a682e9596ea20539f96a6ef3f8cab
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-10-02 01:38:07 UTC,"**Gerrit/Patchset: https://reviews.mahara.org/mahara refs/changes/55/10355/11
**Browser tested: Firefox
**Theme used: Default (Raw)"
1827811,2019-09-25 04:49:01 UTC,"Reviewed:  https://reviews.mahara.org/10302
Committed: https://git.mahara.org/mahara/mahara/commit/f8d9ec0a78363bcdab63a85aabbc735ed86badcf
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-12 23:51:03 UTC,"Patchset: https://reviews.mahara.org/#/c/10304/6
Browser tested: Firefox
Theme used: Raw"
1827811,2019-09-25 04:49:02 UTC,"Reviewed:  https://reviews.mahara.org/10107
Committed: https://git.mahara.org/mahara/mahara/commit/ece65af480bf5186e8738f0b3f3542d7f220cd0e
Submitter: Cecilia Vela Gurovic (<email address hidden>)
Branch:    master"
1827811,2019-09-06 02:26:52 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10304"
1827811,2019-06-19 01:42:59 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10102"
1827811,2019-06-19 05:03:54 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10107"
1827811,2019-06-24 02:43:16 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10125"
1827811,2019-06-25 02:37:05 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10129"
1827811,2019-06-25 05:30:59 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10131"
1827811,2019-07-14 23:31:56 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10157"
1827811,2019-07-16 05:07:58 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10162"
1827811,2019-07-22 02:38:56 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10204"
1827811,2019-07-18 23:12:45 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10189"
1827811,2019-08-08 21:56:02 UTC,"BUG #1 User can make a comment without entering text in the comment field
**************
#1 (Chrome)
When a user clicks comment button without entering a comment, an error message is displayed. However it is only for a few seconds before the modal appears to reopen and the error message is hidden. ✘"
1827811,2019-08-08 22:32:22 UTC,"Hi Steven,
I can not reproduce issues #1 or #2 from your last comment (#13).  Are there any extra steps I am missing?"
1827811,2019-08-22 19:29:28 UTC,"Bug #1 Fixed - BUG #1 When a user tries to make a comment without adding text into the ""Add comment"" text area an error message is displayed at the top of the modal window and also just below the ""Add comment"" field"
1827811,2019-09-03 03:53:22 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10283"
1827811,2019-09-03 06:02:12 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10285"
1827811,2019-09-05 21:38:13 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10299"
1827811,2019-09-05 23:00:09 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10302"
1827811,2019-08-05 23:34:16 UTC,"Commit hash: 013743dffc98b806474c4b9065c34bc21c329147
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw"
1827811,2019-09-12 01:33:33 UTC,"Patchset: https://reviews.mahara.org/#/c/10304/6
Browser tested: Firefox
Theme used: Raw"
1827812,2019-07-18 22:28:08 UTC,"Patch for ""19.04_STABLE"" branch: https://reviews.mahara.org/10186"
1827812,2019-07-18 22:29:55 UTC,"Reviewed:  https://reviews.mahara.org/10186
Committed: https://git.mahara.org/mahara/mahara/commit/6eb1106f027aac6e074468ca62c31c80b139af71
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.04_STABLE"
1827812,2019-07-18 22:27:46 UTC,"Reviewed:  https://reviews.mahara.org/10134
Committed: https://git.mahara.org/mahara/mahara/commit/8af3a59933d9b31997a33d2086146b37315e8545
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1827812,2019-06-26 06:24:56 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10134"
1827812,2019-06-11 00:03:19 UTC,"Environment tested: Master
Browser tested: Chrome
Theme used:  Raw"
1827812,2019-06-10 08:36:40 UTC,"This is also the case of other emails, e.g. forum notifications. Steven, can you please test the following?"
1827812,2019-07-16 20:08:36 UTC,"Commit hash: 1dd1bdf98e6e4d5aec54a58b2d3f5a624bfb692f
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw"
1827812,2019-05-06 21:23:08 UTC,"ADDITIONAL TESTING
====================
Can you please check if that was the same before we made the security update? Please ask Cecilia how you can check out 18.04.3. since i saw the issue on mahara.org, which runs on 18.04.4 now, we need to go back to the previous minor point release to see if the problem was there already or if is an issue that was introduced with the latest bug fixes."
1827816,2019-05-06 00:20:24 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9959"
1827816,2019-05-29 03:46:58 UTC,Bug Fixed - no issues when running script
1827816,2019-05-29 19:40:14 UTC,"Reviewed:  https://reviews.mahara.org/9959
Committed: https://git.mahara.org/mahara/mahara/commit/88de36c66db584d783ed8aaa67d25927e03c5bf2
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1827819,2019-05-06 00:45:10 UTC,Error.txt contains the verbose output of the stap command: stap --disable-cache --vp 0055 -p4 -m vigila.ko vigila.stp
1827819,2019-05-06 12:09:41 UTC,"commit eb8c8de940cb5e9256323e67a1757f9a45afed8c
Author: Frank Ch. Eigler <email address hidden>
Date:   Sat Feb 2 14:50:32 2019 -0600"
1827819,2019-05-06 16:46:49 UTC,Ok thanks. I'll download that release when it's available then.
1827819,2019-05-08 13:44:15 UTC,Downloaded and compiled Systemtap 4.1.
1827819,2020-03-24 14:54:19 UTC,"focal will ship with systemtap 4.2-3, fixing this."
1827820,2019-05-08 11:31:30 UTC,This behavior is correct as the NPTH pads are circular.  We would need to add a fourth option to not change pads with a different type to achieve the behavior you want.
1827822,2019-05-18 02:43:22 UTC,"No I can not reproduce this.  Which is not that surprising, deep kernel bugs are unlikely to be correlated with anything the user is doing at the UI level.  System is still crashing sporadically, they do not occur on any of my other systems, nor did they happen on this system before a certain date, which inclines me to claim that they were not happening with older kernels."
1827822,2019-10-05 22:30:10 UTC,I just had this happen to me. I'll attach the relevant part of the syslog. If there's any more info that I could give that would help just let me know. Using Kernel 5.3.0-10-generic from Eoan.
1827822,2019-10-06 01:52:33 UTC,"A month or so after reporting this, amid a frustrating series of unpredictable lockups, I figured out how to run memtest which indicated I had a bad memory card.  Since replacing it, I have had no further problems."
1827822,2019-10-07 19:28:45 UTC,Thanks for the response. What version of memtest did you run and how long did you have to run it? You ended up having a bad stick of ram? Did you have to test each one individually?
1827822,2019-10-18 23:11:00 UTC,"I'm also encountering this issue, only on 19.10. My GPU is a RX 580. Tested memory for 8 hours using livecd memtest
 BUG: kernel NULL pointer dereference, address: 00000000000002ac
 #PF: supervisor read access in kernel mode
 #PF: error_code(0x0000) - not-present page
 PGD 0 P4D 0
 Oops: 0000 [#1] SMP NOPTI
 CPU: 9 PID: 340 Comm: kworker/u64:9 Tainted: G        W  OE     5.3.0-18-generic #19-Ubuntu
 Hardware name: System manufacturer System Product Name/CROSSHAIR VI HERO, BIOS 7501 09/23/2019
 Workqueue: events_unbound commit_work [drm_kms_helper]
 RIP: 0010:dc_stream_log+0x12/0xc0 [amdgpu]
 Code: 83 f1 01 0f b6 c9 e8 8d c2 81 c7 e9 71 ff ff ff 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 f2 bf 04 00 00 00 48 89 e5 53 <8b> 86 ac 02 00 00 48 89 f3 8b 8e 0c 01 00 00 50 8b 86 28 01 00 00
 RSP: 0018:ffffc017c12d7b80 EFLAGS: 00010202
 RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000002
 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
 RBP: ffffc017c12d7b88 R08: 0000000000000000 R09: 0000000000000001
 R10: ffff9efbcea573c8 R11: 0000000000000000 R12: ffff9efa9f840000
 R13: ffff9efbbae30000 R14: ffff9efa9f840000 R15: ffff9efbbad40000
 FS:  0000000000000000(0000) GS:ffff9efbcea40000(0000) knlGS:0000000000000000
 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
 CR2: 00000000000002ac CR3: 00000003fe050000 CR4: 00000000003406e0
 Call Trace:
  dc_commit_state+0x7e/0xb0 [amdgpu]
  amdgpu_dm_atomic_commit_tail+0x3bf/0xfb0 [amdgpu]
  ? cpumask_next_and+0x1e/0x20
  ? free_one_page+0xb7/0x4b0
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? _cond_resched+0x19/0x30
  ? wait_for_completion_timeout+0x3a/0x120
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  commit_tail+0x41/0x70 [drm_kms_helper]
  ? commit_tail+0x41/0x70 [drm_kms_helper]
  commit_work+0x12/0x20 [drm_kms_helper]
  process_one_work+0x1db/0x380
  worker_thread+0x4d/0x400
  kthread+0x104/0x140
  ? process_one_work+0x380/0x380
  ? kthread_park+0x80/0x80
  ret_from_fork+0x22/0x40
 Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) xfrm_user vboxnetflt(OE) xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 l2tp_ppp l2tp_netlink l2tp_core ah4 ip6_udp_tunnel vboxdrv(OE) udp_tunnel af_key xfrm_algo pppox nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep input_leds snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer edac_mce_amd kvm_amd kvm irqbypass eeepc_wmi asus_wmi sparse_keymap video wmi_bmof snd k10temp ccp soundcore mac..."
1827822,2020-02-05 19:00:00 UTC,"[Wed Feb  5 20:09:17 2020] vfio-pci 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[Wed Feb  5 20:09:17 2020] BUG: kernel NULL pointer dereference, address: 0000000000000008
[Wed Feb  5 20:09:17 2020] #PF: supervisor write access in kernel mode
[Wed Feb  5 20:09:17 2020] #PF: error_code(0x0002) - not-present page
[Wed Feb  5 20:09:17 2020] PGD 0 P4D 0
[Wed Feb  5 20:09:17 2020] Oops: 0002 [#1] SMP NOPTI
[Wed Feb  5 20:09:17 2020] CPU: 3 PID: 3306 Comm: tee Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu
[Wed Feb  5 20:09:17 2020] Hardware name: System manufacturer System Product Name/PRIME H310T, BIOS 2602 07/24/2019
[Wed Feb  5 20:09:17 2020] RIP: 0010:mutex_lock+0x1d/0x40
[Wed Feb  5 20:09:17 2020] Code: 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 9e e6 ff ff 65 48 8b 14 25 c0 6b 01 00 31 c0 <f0> 48 0f b1 13 75 03 5b 5d c3 48 89 df e8 b1 ff ff ff 5b 5d c3 0f
[Wed Feb  5 20:09:17 2020] RSP: 0018:ffff9d4a42817d38 EFLAGS: 00010246
[Wed Feb  5 20:09:17 2020] RAX: 0000000000000000 RBX: 0000000000000008 RCX: 0000000000000000
[Wed Feb  5 20:09:17 2020] RDX: ffff8cd6d8f6da00 RSI: 0000000000000000 RDI: 0000000000000008
[Wed Feb  5 20:09:17 2020] RBP: ffff9d4a42817d40 R08: ffff8cd6dbc036c0 R09: ffff8cd6dbc03718
[Wed Feb  5 20:09:17 2020] R10: 0000000000000000 R11: ffffffff8285d518 R12: 0000000000000000
[Wed Feb  5 20:09:17 2020] R13: ffffffffc05b0000 R14: ffff9d4a42817ee8 R15: fffffffffffffff2
[Wed Feb  5 20:09:17 2020] FS:  00007f32cfe5f540(0000) GS:ffff8cd6ddd80000(0000) knlGS:0000000000000000
[Wed Feb  5 20:09:17 2020] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Wed Feb  5 20:09:17 2020] CR2: 0000000000000008 CR3: 0000000458984003 CR4: 00000000003626e0
[Wed Feb  5 20:09:17 2020] Call Trace:
[Wed Feb  5 20:09:17 2020]  snd_sof_ipc_free+0x20/0x40 [snd_sof]
[Wed Feb  5 20:09:17 2020]  snd_sof_device_remove+0x33/0xa0 [snd_sof]
[Wed Feb  5 20:09:17 2020]  sof_pci_remove+0x19/0x30 [sof_pci_dev]
[Wed Feb  5 20:09:17 2020]  pci_device_remove+0x3e/0xc0
[Wed Feb  5 20:09:17 2020]  device_release_driver_internal+0xe0/0x1b0
[Wed Feb  5 20:09:17 2020]  device_driver_detach+0x14/0x20
[Wed Feb  5 20:09:17 2020]  unbind_store+0xd1/0x130
[Wed Feb  5 20:09:17 2020]  drv_attr_store+0x27/0x40
[Wed Feb  5 20:09:17 2020]  sysfs_kf_write+0x3c/0x50
[Wed Feb  5 20:09:17 2020]  kernfs_fop_write+0x125/0x1a0
[Wed Feb  5 20:09:17 2020]  __vfs_write+0x1b/0x40
[Wed Feb  5 20:09:17 2020]  vfs_write+0xb1/0x1a0
[Wed Feb  5 20:09:17 2020]  ksys_write+0xa7/0xe0
[Wed Feb  5 20:09:17 2020]  __x64_sys_write+0x1a/0x20
[Wed Feb  5 20:09:17 2020]  do_syscall_64+0x5a/0x130
[Wed Feb  5 20:09:17 2020]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[Wed Feb  5 20:09:17 2020] RIP: 0033:0x7f32cf963154
[Wed Feb  5 20:09:17 2020] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 b1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5
[Wed Feb  5 20:09:17 2020] RSP: 002b:00007ffeacffedb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[Wed Feb  5 20:09:17 2020] RAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007f32cf963154
[Wed..."
1827822,2019-05-06 01:30:06 UTC,This change was made by a bot.
1827822,2019-05-16 11:11:41 UTC,"Hello,
can this issue be reproduced? How to trigger it?"
1827823,2019-05-06 07:58:28 UTC,"This is now a near-constant issue and occurs on multiple apps:
https://youtu.be/B1CYcDVZlrA
https://www.youtube.com/watch?v=EdF7EnLthxc"
1827826,2019-05-30 07:44:37 UTC,"Install the custom 5.0.0 kernel in mantis dvt2 (201905-27066) and run ""audio/speaker-headphone-plug-detection"", the error message didn't occur but checkbox also didn't detect the headset was plugged in. (Headset OSD didn't pop-up too)"
1827826,2019-05-30 08:00:45 UTC,"@Betty, please refer to this lp https://bugs.launchpad.net/somerville/+bug/1829101"
1827826,2019-05-06 09:00:06 UTC,pactl list provided by Intel
1827826,2019-05-06 07:17:38 UTC,The pactl parser fails to load the `pactl list` output. Could you please attach the output of this command. It will allow us to provide a fix for the new syntax.
1827826,2019-05-07 08:46:26 UTC,the checkbox-support parser needs to take into account the optional ALSA UCM pretags [1]:
1827826,2019-05-06 07:18:48 UTC,"@hao-sheng
please provide pactl list"
1827829,2019-08-14 15:52:08 UTC,"Reviewed:  https://review.opendev.org/675678
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=23889cf575c9d61cdc5a9fbf854d488dd1bbf40a
Submitter: Zuul
Branch:    master"
1827829,2019-08-09 18:38:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/675678"
1827831,2019-05-06 06:32:17 UTC,"COM71は""舌を入れる""だった時代の、調教者にペニスがある場合COM名称を""フェラチオ""に
変換する処理がそのまま残っていた故の不具合"
1827831,2019-05-07 09:37:07 UTC,実行COM名へのTRAINNAME代入処理を消してしまっていたので修正
1827833,2019-05-06 20:30:24 UTC,"Thanks for the report.
Fixed here: https://github.com/lxml/lxml/commit/bb2a4fd588d1cdf5ecd9badd618505d578ea2942"
1827834,2019-05-06 07:32:38 UTC,patch proposed : https://review.opendev.org/#/c/657223/
1827834,2019-05-06 10:01:22 UTC,This should have been reported against os-testr as networking-ovn doesn't do anything wrong.
1827834,2019-07-04 00:10:43 UTC,Fixed in https://review.opendev.org/#/c/651275/
1827837,2019-05-06 19:06:13 UTC,"You have installed the program from the Ubuntu universe repository, yes?"
1827837,2019-06-20 12:19:48 UTC,"Please respond to the query, or else the bug will be closed. Sorry, but sometimes it is not possible to fix bugs where information I ask for is not provided."
1827837,2019-06-27 05:36:00 UTC,"Sorry. your queries didn't reach me until now.
yes, from the Ubuntu universe."
1827837,2019-06-27 19:45:19 UTC,Please install 0.9.15 beta 1 from here: https://damonlynch.net/rapid/download.html
1827838,2019-05-10 16:04:05 UTC,"I've just came across the same exact problem yesterday.
Unfortunately I don't have direct access to the environment, but here is my summary:"
1827838,2019-05-09 18:23:40 UTC,"Hi manadart, yes thanks for all the help.
I do not see the issue or any other issues on the last few deployments.
We can mark as Fix Released."
1827838,2019-05-09 13:58:14 UTC,Are we able to resolve this bug based on the resolution of prior proxy issues?
1827838,2019-05-07 03:43:02 UTC,Thanks for giving it a test.
1827838,2019-05-07 14:03:42 UTC,"Hi, an update, I was running controller model with proxy, that explains issues I've faced on #4. Once proxy configs were set correctly, controller deployment works."
1827838,2019-05-06 18:34:05 UTC,"Hi, just tested your repo on my environment and it failed during juju deploy:
https://pastebin.ubuntu.com/p/FdgVjbr6n2/"
1827838,2019-05-06 16:10:08 UTC,"Proposed a patch against the 2.5 branch that fixes a missing error check on this code path:
https://github.com/juju/juju/pull/10142"
1827838,2019-05-06 09:27:13 UTC,This is an ongoing customer deployment:
1827838,2019-05-08 08:26:16 UTC,"Based on the log output in https://pastebin.canonical.com/p/qfxgQpZSqc/, I am bit concerned that we are not getting consistent results."
1827839,2019-05-07 14:15:00 UTC,Thanks for filing this bug in Ubuntu.
1827839,2019-05-24 14:07:46 UTC,"ii  libmysql++-dev                              3.2.2+pristine-1ubuntu1                      amd64        MySQL C++ library bindings (development)
ii  libmysql++3v5                               3.2.2+pristine-1ubuntu1                      amd64        MySQL C++ library bindings (runtime)
ii  libmysqlclient-dev                          5.7.26-0ubuntu0.16.04.1                      amd64        MySQL database development files
ii  libmysqlclient20:amd64                      5.7.26-0ubuntu0.16.04.1                      amd64        MySQL database client library
ii  mysql-client                                5.7.26-0ubuntu0.16.04.1                      all          MySQL database client (metapackage depending on the latest version)
ii  mysql-client-5.7                            5.7.26-0ubuntu0.16.04.1                      amd64        MySQL database client binaries
ii  mysql-client-core-5.7                       5.7.26-0ubuntu0.16.04.1                      amd64        MySQL database core client binaries
ii  mysql-common                                5.7.26-0ubuntu0.16.04.1                      all          MySQL database common files, e.g. /etc/mysql/my.cnf
ii  mysql-server                                5.7.26-0ubuntu0.16.04.1                      all          MySQL database server (metapackage depending on the latest version)
ii  mysql-server-5.7                            5.7.26-0ubuntu0.16.04.1                      amd64        MySQL database server binaries and system database setup
ii  mysql-server-core-5.7                       5.7.26-0ubuntu0.16.04.1                      amd64        MySQL database server binaries
ii  pinba-engine-mysql-5.7                      1.1.0-1ubuntu1.12                            amd64        realtime statistics server for PHP using MySQL as a read-only interface"
1827839,2019-05-24 14:27:30 UTC,"This looks fine, are you still experiencing problems?"
1827839,2019-07-24 04:17:35 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1827842,2019-10-24 07:17:16 UTC,"1:12.2-2ubuntu3.1 is working fine and not creating regressions, even if the bug seems to not happen on every install which makes the fix harder to verify the change is right on principle, marking as verified"
1827842,2019-10-24 13:14:43 UTC,"The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827842,2019-10-24 13:14:32 UTC,This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu3.1
1827842,2019-10-08 19:29:13 UTC,"The fix for this bug has been awaiting testing feedback in the -proposed repository for disco for more than 90 days.  Please test this fix and update the bug appropriately with the results.  In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository."
1827842,2019-10-24 13:13:08 UTC,"Yeah, I guess this will have to do it for the verification. Please be sure to re-open the bug in case someone reports the issue as not being fixed in the end."
1827842,2019-07-04 18:08:50 UTC,This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu4
1827842,2019-05-06 13:23:59 UTC,"Thank you for your bug report, indeed that line is an old Ubuntu diff and should probably be removed, I'm going to do that in the next upload"
1827842,2019-07-08 23:05:24 UTC,"Hello Pierre-Antoine, or anyone else affected,"
1827842,2019-05-22 14:48:51 UTC,"The request makes sense but I wonder if you saw any user visible impact? Trying on a recent disco installation, using the 'beep' command or press tab on a command line reflect the sound selected in gnome-control-center -> sound"
1827842,2019-10-13 09:27:33 UTC,Sorry (again) for the late reply.
1827842,2019-06-27 18:32:54 UTC,Sorry for the late answer.
1827842,2019-06-21 14:51:48 UTC,Could you provide the details asked in the previous comment?
1827842,2019-06-28 10:07:15 UTC,"Thanks, I can't confirm those problems but the patch seems indeed a distro divergence we don't need, remove it now in the packaging vcs
https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?id=227d3ade"
1827843,2019-06-04 18:43:46 UTC,"Here are some screenshots to prove to you including the times, notice the time in the top of the screenshots:"
1827843,2019-06-04 07:19:41 UTC,Please don't make it Invalid yet.
1827843,2019-06-04 07:13:13 UTC,"I double checked. Here is a pasteboard of my extensions: https://pasteboard.co/IhOQnMQ.png
I removed all my extensions (except for ones installed by Ubuntu) and the problem still happens."
1827843,2019-06-01 18:29:40 UTC,Looks like that was it. I removed all my extensions and I don't get that app display error anymore. I guess I will have to do without the net speed extension :(
1827843,2019-05-26 04:21:46 UTC,Ok will do
1827843,2019-06-23 14:26:00 UTC,"Hi any idea what could be causing this problem?
The problem still persists by the way.. Thanks."
1827843,2019-05-06 11:13:03 UTC,"I have noticed that the app pages disappear sometimes and when they do, the three dots on the right side are redrawn together once. Then after the app pages disappear."
1827843,2019-05-06 09:03:39 UTC,"Command: grep -Eh '""(uuid|url|version)""' ~/.local/share/gnome-shell/extensions/*/metadata.json"
1827843,2019-05-06 08:52:54 UTC,"This happened on and off. After posting this bug, Page 1 and Page 2 of menu were ok but Page 3 was empty. Its inconsistent."
1827843,2019-05-06 08:48:44 UTC,Page 3
1827843,2019-05-06 08:48:29 UTC,Page 2
1827843,2019-05-06 08:48:11 UTC,I am attaching screenshots of my app menu in Ubuntu 18.04. Screenshots of all three pages are attached.?field.comment=I am attaching screenshots of my app menu in Ubuntu 18.04. Screenshots of all three pages are attached.
1827843,2019-05-07 02:32:30 UTC,Please try uninstalling (or just renaming the directory of) the extensions mentioned in comment #6. Then reboot and retest
1827844,2019-06-13 10:06:34 UTC,This issue was fixed in the openstack/python-openstackclient 3.19.0 release.
1827845,2019-05-09 10:33:34 UTC,Issue could be found on KVM and LPAR.
1827845,2019-05-06 09:40:03 UTC,apport information
1827845,2019-05-06 09:40:02 UTC,apport information
1827845,2019-05-06 09:40:00 UTC,apport information
1827845,2019-05-06 09:39:58 UTC,apport information
1827845,2019-05-06 09:39:56 UTC,apport information
1827845,2019-05-06 09:39:55 UTC,apport information
1827845,2019-05-06 09:39:54 UTC,apport information
1827845,2019-05-06 09:39:52 UTC,apport information
1827845,2019-05-06 09:10:21 UTC,"It looks like this was caused by the test_bpf module, when you try to insert it manually, it will complain about: ""modprobe: ERROR: could not insert 'test_bpf': Invalid argument"""
1827845,2019-05-06 09:39:57 UTC,apport information
1827845,2019-05-06 09:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827846,2019-05-07 10:29:06 UTC,The problem in comment #6 is being tracked here: https://bugs.launchpad.net/kicad/+bug/1827872
1827846,2019-05-09 22:33:16 UTC,"@Hildo, please read Jeff's explanation in #1. The tab behaviour has been removed from Eeschema with the move to the modern toolset to align it with Pcbnew."
1827846,2019-05-09 22:16:04 UTC,"I just reported a bug marked as duplicated of this lp:1828476
Since my reported version is 2 days newer than the fix commited, I am marking this as ""in progress""."
1827846,2019-05-07 11:04:47 UTC,"Fixed in revision cf046e0548a49d358354abadd3a756708688549b
https://git.launchpad.net/kicad/patch/?id=cf046e0548a49d358354abadd3a756708688549b"
1827846,2019-05-07 09:19:51 UTC,"I still have an issue. It is not possible to grab the end and get it to the GND below by pressing ""g""."
1827846,2019-05-06 13:25:56 UTC,"Here you are. I pressed ""g"" but it was more like a move."
1827846,2019-05-06 10:36:04 UTC,There is no longer any need for two commands (drag block & drag item).  Drag does a drag of whatever is selected.  By default this is wired up to the ‘G’ key.
1827846,2019-05-06 14:16:50 UTC,He he... it's because of the new greedy selection model (select from right-to-left).  A wire that's entirely selected doesn't have an end anchored.
1827846,2019-05-06 11:49:26 UTC,"OK this is a good approach but it does not work as good as the ""move block"" command yes. I suppose the work isn't finished on that feature?"
1827846,2019-05-06 12:41:19 UTC,"Well, it's ""supposed"" to be done. ;)"
1827847,2019-05-06 09:05:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827847,2019-05-08 07:32:14 UTC,"5.0.0-1006.7 - oem-osp1
Regression test CMPL, RTB."
1827849,2019-05-08 06:57:54 UTC,It works now.
1827849,2019-05-07 11:04:51 UTC,"Fixed in revision 11ec7d4651ae366628fd98cf738951ecbc4f584a
https://git.launchpad.net/kicad/patch/?id=11ec7d4651ae366628fd98cf738951ecbc4f584a"
1827849,2019-05-07 09:23:17 UTC,Ahh... that explains it.  I didn't pay enough attention to the background in the video: I was always trying to reproduce it in the symbol editor.
1827849,2019-05-07 08:17:47 UTC,"To add to previous comment, the symbol editor works correctly in this respect. Still happens in the sch editor. Selecting and moving ref and val fields works OK now."
1827849,2019-05-06 14:15:25 UTC,"Clarification: I can click directly on the value or ref field and it selects that field normally, but at the same time may select a pin if it happens to be in the mirrored location."
1827849,2019-05-06 14:11:51 UTC,"It only happens vertically, like in the video. With a symbol with pins in all 4 sides I can see it is about coordinates. It mirrors the Y coordinates of the symbol, relative to the symbol's own zero point. But it doesn't happen with value and reference texts, only with pin names. If the zero point isn't in the center of the symbol, clicking outside the symbol causes the pin in the mirrored location selected."
1827849,2019-05-06 13:09:10 UTC,I can reproduce this one.
1827849,2019-05-06 12:46:53 UTC,Do you also get the text moving in the opposite direction if you drag a symbol text field?
1827849,2019-05-06 15:33:09 UTC,"The inability to move the ref or value is a different bug.  (Fixed, but not yet merged.)"
1827849,2019-05-06 17:03:52 UTC,"I just compiled on Linux and it happens there, too."
1827850,2019-05-06 12:06:01 UTC,"Hi Martin, I can take a look at this.  Please send your example by email and I will investigate.  Thanks"
1827850,2019-05-06 13:27:43 UTC,It is not easy to send it as you mail server does not like attachments.
1827850,2019-05-06 16:31:51 UTC,@Martin I think I have fixed my mail server issue
1827850,2019-05-07 02:25:54 UTC,"Fixed in revision 316be464abee09cb15afbe607bb55523eacfaf39
https://git.launchpad.net/kicad/patch/?id=316be464abee09cb15afbe607bb55523eacfaf39"
1827853,2019-05-06 09:50:14 UTC,This requires going between eeschema and pcbnew.
1827853,2019-05-06 09:37:39 UTC,"I can't even de-red the red symbol under some circumstances. Selecting another footprint makes another symbol red, but it stays red. There's some combination of actions which triggers this and something which clears it, but I didn't find the logic yet."
1827853,2019-06-26 20:56:04 UTC,"Fixed in revision fa84babefe247670b75e3ea9b95f8d6527e9d856
https://git.launchpad.net/kicad/patch/?id=fa84babefe247670b75e3ea9b95f8d6527e9d856"
1827854,2019-07-22 04:44:05 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019."
1827856,2019-09-17 07:34:48 UTC,Migrated to https://github.com/widelands/widelands/issues/3428
1827857,2019-05-09 13:41:24 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827857,2019-06-12 21:00:07 UTC,"I've been able to reproduce this bug consistently. It appears python3-apt is at cause. If a non-utf8 locale is configured, apt will returned descriptions in the preferred lang/encoding and python3 fails to interpret them as utf8. Python2.7 did ascii conversion, returning ""lossy"" unicode conversion but not crashing."
1827857,2020-04-02 20:14:10 UTC,landscape-client workaround: https://github.com/CanonicalLtd/landscape-client/pull/80
1827857,2020-04-15 18:06:11 UTC,The issue was fixed in python-apt =2.0.0
1827859,2021-02-08 16:32:23 UTC,For reference:
1827859,2021-02-08 16:20:30 UTC,This has been a long-time issue with the way Cura renders the UI.
1827859,2019-12-25 09:42:57 UTC,Hints for those stuck with broken cura:
1827859,2019-12-24 11:31:52 UTC,I have just installed 19.10 and I have the same problem
1827859,2019-07-17 21:26:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827859,2019-06-01 10:02:34 UTC,Affected me after my upgrade to 19.04 too -- looks the same as https://bugzilla.redhat.com/show_bug.cgi?id=1708956
1827859,2021-02-02 02:48:49 UTC,Thank you for reporting this bug to Ubuntu.
1827863,2019-05-13 07:43:13 UTC,rocky promotion on the weekend 11/05 apparently - lets see if that goes green https://review.opendev.org/#/c/658353/ for standalone-upgrade-stein
1827863,2019-05-27 12:48:51 UTC,"http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-standalone-upgrade-stein and http://logs.openstack.org/09/661009/3/gate/tripleo-ci-centos-7-standalone-upgrade-stein/d6aa92b/logs/tempest.html.gz tests are passing, closing this bug,"
1827863,2019-05-20 12:42:03 UTC,New python-temepstconf version is available now
1827863,2019-05-20 12:41:52 UTC,can we close this one ?
1827863,2019-05-10 13:07:19 UTC,current plan. we merge https://review.opendev.org/#/c/655661/7 to land the standalone-upgrade-stein job as voting albeit with skip on those two tests. I just posted https://review.opendev.org/658353 for unskipping once they are green.
1827863,2019-05-06 10:38:36 UTC,13:12 < chandankumar> marios: kopecmartin arxcruz temprory workaround for tempestconf upgrade https://review.rdoproject.org/r/#/c/20574/
1827863,2019-05-09 10:37:58 UTC,"https://review.rdoproject.org/r/#/c/20579/ -> updates tempestconf version 2.2.0 for stein, rocky and queens will fix the issue."
1827863,2019-05-09 10:37:29 UTC,"apparently chandan has already fixed this, we need temepstconf 2.2.0"
1827863,2019-05-09 10:33:01 UTC,@chandan .. do you mean we need to backport that https://review.opendev.org/#/c/637679/ to stable/stein then stable/rocky?
1827863,2019-05-06 13:30:05 UTC,"Facts:
1. python-tempestconf previously did create flavors with disk size = 0 - this got changed by this review [1] only a few months ago
2. [1] is not packaged yet -> python-tempestconf packages for Rocky and Queens don't contain the [1] change
3. flavors with disk size = 0 are forbidden in Stein
4. We're going to update python-tempestconf package for Rocky and Queens in order get there some features implemented over last few months (including [1])
5. When python-tempestconf creates flavors necessary for running Tempest it looks for flavors named 'm1.nano' and 'm1.micro'. If any flavor with such a name is found, python-tempestconf doesn't create a new flavor, it will reuse that one and doesn't matter what are the other specifics of the flavor like disk size , ... -> that said, if there is a flavor named 'm1.nano' or 'm1.micro' with disk size = 0, python-tempestconf will not create a new one, even if it created a flavor with disk size != 0 .. THIS IS NOT A BUG"
1827863,2019-05-06 11:31:47 UTC,Here is the dnm patch to verify the same: https://review.opendev.org/#/c/657372/
1827863,2019-05-06 11:30:35 UTC,Above workaroud is not going to work as in upgrade job we run tempest twice and here http://logs.openstack.org/67/656967/4/check/tripleo-ci-centos-7-standalone-upgrade/7a25341/logs/undercloud/var/log/extra/rpm-list.txt.gz -> python2-tempestconf-2.1.1-0.20190424160311.e0d5dd6.el7.noarch is used.
1827863,2019-05-10 12:13:05 UTC,related to https://bugs.launchpad.net/tripleo/+bug/1828550 stable/rocky
1827866,2021-01-22 04:30:04 UTC,"Found on B-aws-5.4
 Unhandled exception 13 #GP at ip 00000000004071a3
 error_code=0000 rflags=00010006 cs=00000008
 rax=0000000000000078 rcx=0000000000000809 rdx=0000000000000000 rbx=0000000000000009
 rbp=000000000047efdf rsi=000000000042568d rdi=000000000042568d
 r8=000000000000000a r9=00000000000003f8 r10=000000000000000d r11=0000000000000000
 r12=0000000000000000 r13=0000000000000000 r14=0000000000403dcc r15=0000000000000000
 cr0=0000000080010031 cr2=0000000000000000 cr3=0000000000477000 cr4=0000000000002020
 cr8=0000000000000007
 STACK: @4071a3 40170b 4004dd
 FAIL vmx_apicv_test"
1827866,2020-11-17 04:26:26 UTC,Still visible in Xenial 4.4.0-1118.132 AWS c5.metal
1827866,2020-10-09 22:05:50 UTC,Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64
1827866,2020-01-22 08:24:46 UTC,This issue can be found on AWS Trusty 4.4 as well (4.4.0-1061.65-aws):
1827866,2020-01-22 08:26:36 UTC,"BTW for AWS T-4.4, this is only failing on:
* r5.metal
* c5.metal"
1827866,2019-12-02 09:38:10 UTC,Passed with B-KVM 4.15.0-1051.51 this cycle.
1827866,2019-11-08 07:34:33 UTC,Failed on B-AWS-5.3 bare-metal instance i3.metal
1827866,2019-11-07 07:44:50 UTC,"Failed on Oracle B-4.15
Passed on Oracle B-5.0"
1827866,2019-11-01 10:11:33 UTC,Found on B-aws amd64 4.15
1827866,2019-10-18 10:48:26 UTC,"Can be found on X-Azure 4.15 as well:
 Running '/home/azure/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_apicv_test'
 BUILD_HEAD=e2c275c4
 timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.O2MSEezMNL -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.nFaa5lDEut
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 477000
 cr4 = 20"
1827866,2019-05-06 11:27:06 UTC,"vmx_apicv_test timeouted on B-KVM:
FAIL vmx_apicv_test (timeout; duration=10)"
1827866,2019-12-11 11:17:22 UTC,This failure can be found on Eoan bare metal node fili (5.3.0-25.27)
1827867,2019-05-14 12:53:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827867,2019-05-16 10:30:21 UTC,"Hello everybody,"
1827867,2019-05-17 20:21:57 UTC,I hit this as well. It looks like it is fixed over in https://bugs.launchpad.net/nova/+bug/1808951
1827868,2019-05-14 15:01:51 UTC,"Dmitri, which version of OpenStack / Ubuntu is this on please?"
1827868,2019-05-14 15:29:33 UTC,"Alex, it's bionic-stein"
1827868,2019-05-14 20:38:46 UTC,TRIAGE:
1827868,2019-12-02 14:34:37 UTC,"Marking as a duplicate of #1853851.  Note, although this one is older, the dupped bug has essentially outlined the solution."
1827870,2019-05-14 08:45:48 UTC,"Not sure what I can do here. The amazon metadata plugin was updated to
strip the text in brackets at the end of the title. This is because it is
almost always not useful text. There is no way for calibre to know which
particular text a particular user would find useful or not."
1827873,2019-05-06 14:36:14 UTC,Yep; reproduces readily with a rotated component.
1827873,2019-05-06 16:01:56 UTC,"Fixed in revision a76bcc204f4bce699e3494f1f3e90494c5e0a716
https://git.launchpad.net/kicad/patch/?id=a76bcc204f4bce699e3494f1f3e90494c5e0a716"
1827873,2019-05-06 13:12:23 UTC,"On 05/06/2019 07:39 AM, Jeff Young wrote:

> Hmmm... I'm not seeing this.
>
> Whey you say opposite, do you just mean on the Y axis, or on both?
>
> Anyone else seeing this?
>


Here's a link to a video:
https://drive.google.com/open?id=1CLmsOiIs3sjX0EQlXo5TIhKEGxs2xv6z"
1827873,2019-05-06 13:14:58 UTC,"In the video, that component is rotated 180.  That may be why you didn't see it."
1827873,2019-05-06 12:39:33 UTC,Hmmm... I'm not seeing this.
1827873,2019-05-06 13:07:02 UTC,"I'm not seeing it on macOS: select text field, hit 'M', everything moves in the direction I expect."
1827874,2019-07-07 04:17:27 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1827874,2019-05-07 17:31:38 UTC,Thanks for filing this bug in Ubuntu.
1827879,2019-09-18 04:17:15 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827879,2019-06-27 04:32:54 UTC,Please run `sudo modprobe -r btusb` before suspend and see if it helps.
1827879,2019-06-26 18:01:19 UTC,"Yes, nothing changed as far as i know, so the issue remains"
1827879,2019-06-24 03:41:49 UTC,Does the issue still happen?
1827879,2019-05-16 16:57:24 UTC,Please note that the killer wireless card is replaced by intel when running apport-collect.
1827879,2019-05-16 16:56:35 UTC,apport information
1827879,2019-05-16 16:56:25 UTC,apport information
1827879,2019-05-16 16:56:33 UTC,apport information
1827879,2019-05-16 16:56:31 UTC,apport information
1827879,2019-05-16 16:56:30 UTC,apport information
1827879,2019-05-16 16:56:29 UTC,apport information
1827879,2019-05-16 16:56:28 UTC,apport information
1827879,2019-05-16 16:56:27 UTC,apport information
1827879,2019-09-18 04:17:21 UTC,[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]
1827879,2019-09-18 04:17:20 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1827879,2019-05-16 16:56:34 UTC,apport information
1827879,2019-05-16 16:56:24 UTC,apport information
1827879,2019-05-16 16:56:21 UTC,apport information
1827879,2019-05-06 12:56:03 UTC,"The Crashlog:
May  2 12:20:17 AW17 kernel: [   33.622257] ath10k_pci 0000:03:00.0: firmware crashed! (guid a4d786d4-4867-4145-a4d6-3a0e2fa1b406)
May  2 12:20:17 AW17 kernel: [   33.622265] ath10k_pci 0000:03:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff sub 1a56:1525
May  2 12:20:17 AW17 kernel: [   33.622267] ath10k_pci 0000:03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
May  2 12:20:17 AW17 kernel: [   33.622651] ath10k_pci 0000:03:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08
May  2 12:20:17 AW17 kernel: [   33.622830] ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
May  2 12:20:17 AW17 kernel: [   33.622833] ath10k_pci 0000:03:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
May  2 12:20:17 AW17 kernel: [   33.624871] ath10k_pci 0000:03:00.0: firmware register dump:
May  2 12:20:17 AW17 kernel: [   33.624876] ath10k_pci 0000:03:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0x6C9F52F4
May  2 12:20:17 AW17 kernel: [   33.624879] ath10k_pci 0000:03:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
May  2 12:20:17 AW17 kernel: [   33.624882] ath10k_pci 0000:03:00.0: [08]: 0x6C9F52E0 0x00400000 0x00000000 0x000A5C88
May  2 12:20:17 AW17 kernel: [   33.624885] ath10k_pci 0000:03:00.0: [12]: 0x0000000D 0x00000000 0x0096C09C 0x0096C0A7
May  2 12:20:17 AW17 kernel: [   33.624888] ath10k_pci 0000:03:00.0: [16]: 0x00000004 0x0040A090 0x0000FFFF 0x00000001
May  2 12:20:17 AW17 kernel: [   33.624891] ath10k_pci 0000:03:00.0: [20]: 0x80996343 0x0041A7D0 0x0044FD68 0x0040D400
May  2 12:20:17 AW17 kernel: [   33.624894] ath10k_pci 0000:03:00.0: [24]: 0x80942BC4 0x0041A790 0x6C9F52E0 0x00400000
May  2 12:20:17 AW17 kernel: [   33.624896] ath10k_pci 0000:03:00.0: [28]: 0x0041A7B0 0x0041A790 0x00000024 0x00000000
May  2 12:20:17 AW17 kernel: [   33.624899] ath10k_pci 0000:03:00.0: [32]: 0x80947BA7 0x0041A7B0 0x00404D88 0x0040E074
May  2 12:20:17 AW17 kernel: [   33.624902] ath10k_pci 0000:03:00.0: [36]: 0x6C9F52C0 0x00000000 0x00000000 0x00000001
May  2 12:20:17 AW17 kernel: [   33.624905] ath10k_pci 0000:03:00.0: [40]: 0x809BDECC 0x0041A7D0 0x00404D88 0x0040E074
May  2 12:20:17 AW17 kernel: [   33.624907] ath10k_pci 0000:03:00.0: [44]: 0x004124C4 0x00404DB4 0x0000FFFF 0x00000001
May  2 12:20:17 AW17 kernel: [   33.624910] ath10k_pci 0000:03:00.0: [48]: 0x8099638C 0x0041A7F0 0x00404D88 0x00000000
May  2 12:20:17 AW17 kernel: [   33.624913] ath10k_pci 0000:03:00.0: [52]: 0x00000000 0x004124C4 0x00404DAC 0x00000005
May  2 12:20:17 AW17 kernel: [   33.624916] ath10k_pci 0000:03:00.0: [56]: 0x80992076 0x0041A810 0x0044FD68 0x0046FFE8
May  2 12:20:17 AW17 kernel: [   33.624918] ath10k_pci 0000:03:00.0: Copy Engine register dump:
May  2 12:20:17 AW17 kernel: [   33.624937] ath10k_pci 0000:03:00.0: [00]: 0x00034400   1   1   3   3
May  2 12:20:17 AW17 kernel: [   33.624952] ath10k_pci 0000:03:00.0: [01]: 0x00034800  22  22 217 218
May  2 12:20:17 AW17 kernel: [   33.624966] ath10k_pci 0000:03:00.0: [02]: 0x00034c00   7   7  70  71
May  2 12:20:17 AW17 kernel: [   33.624979] ath10k_pci 0000:03:00.0: [03]: 0x00035000  19  19  20  19
May ..."
1827879,2019-05-06 16:23:20 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1827879,2019-05-06 17:56:06 UTC,"Some additional information: It looks like NetworkManager is part of the problem / solution.
--> Linked to networkmanager <--
If wifi is disabled (nmcli radio wifi off) the suspend works as expected.
Unfortunately, when scripting this into a systemctl script hooking to suspend.target, networkmanager is killed before the script is executed, thus networkmanager cannot respond anymore to the command."
1827879,2019-05-16 15:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827879,2019-05-16 16:56:06 UTC,apport information
1827879,2019-05-16 16:56:07 UTC,apport information
1827879,2019-05-16 16:56:23 UTC,apport information
1827879,2019-05-16 16:56:09 UTC,apport information
1827879,2019-05-16 16:56:12 UTC,apport information
1827879,2019-05-16 16:56:13 UTC,apport information
1827879,2019-05-16 16:56:15 UTC,apport information
1827879,2019-05-16 16:56:16 UTC,apport information
1827879,2019-05-16 16:56:18 UTC,apport information
1827879,2019-05-16 16:56:19 UTC,apport information
1827879,2019-05-16 16:56:11 UTC,apport information
1827879,2019-05-16 16:56:22 UTC,apport information
1827880,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1827880,2019-05-16 15:03:36 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1827880,2019-05-06 15:30:15 UTC,"SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100541.html"
1827884,2019-07-18 06:45:54 UTC,"I could see that without ""quiet"" boot option."
1827884,2019-07-18 06:42:44 UTC,https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725
1827884,2019-07-18 06:41:46 UTC,It flooded this before reboot:
1827884,2019-07-08 05:51:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827884,2019-07-07 17:00:02 UTC,"Hi Andrea,"
1827884,2019-07-04 14:41:32 UTC,"Michael, first of all thanks for testing. It seems that (in your case at least) the problem was fixed by the extra commits that I backported into 4.15.0-54, so I think it's worth to have them applied."
1827884,2019-07-04 12:55:50 UTC,"Thanks Andrea, much appreciated."
1827884,2019-07-04 08:16:05 UTC,"My output:
uname -a
Linux TEPL-ET2013 4.15.0-54-generic #58+lp1827884 SMP Wed Jul 3 10:05:45 UTC 2019 i686 i686 i686 GNU/Linux"
1827884,2019-07-04 07:37:56 UTC,Thanks for the tests and the feedback @dima2017 and @valia0906! Could you also post the output of the following commands?
1827884,2019-07-04 07:02:49 UTC,But I use Lubuntu Xenial. Probably this is why xorg doesn't start with the last test version. I can upload dmesg or something else if it is needed.
1827884,2019-07-04 06:58:02 UTC,"I've rechecked the last test version. Previous problem is gone, but xorg doesn't start. Xorg doesn't start even with the ""nopti"" option."
1827884,2019-07-04 05:55:45 UTC,"I`ve tried second kernel test version on ubuntu 18.04(bionic), the problem still exists."
1827884,2019-07-03 23:27:08 UTC,"Seems I used wrong kernel for previous test. Sorry.
This new kernel works, but xorg doesn't start.
I'm testing on Lubuntu xenial. How to add ""Xenial"" under the ""Bionic"" on the top of this thread?"
1827884,2019-07-03 14:05:37 UTC,"So, it looks like bug 1830433 didn't fix this problem... assuming it's still an x86/mm issue, it'd be interesting to test another kernel (I've applied a few more x86/mm-related fixes)."
1827884,2019-07-03 06:15:48 UTC,"I`ve tried kernel test version, the problem is still happening."
1827884,2019-07-03 03:56:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827884,2019-07-23 05:49:25 UTC,The problem also present in kernel version 4.15.0.55.57.
1827884,2019-07-25 18:32:15 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1827884,2019-07-25 23:09:30 UTC,I can test it on xenial. Is the fix released in xenial proposed?
1827884,2019-07-26 06:10:31 UTC,"I-ve tested bionic-proposed kernel version 4.15.0.56.58, problem is still present."
1827884,2019-08-13 11:27:47 UTC,This bug was fixed in the package linux - 4.15.0-58.64
1827884,2019-08-07 16:22:30 UTC,So we use this tags for repositories only? I thought it can be used for a fix in the bug report thread too.
1827884,2019-08-07 08:34:02 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1827884,2019-08-01 01:00:04 UTC,I didn't know it. Thank you.
1827884,2019-07-31 09:43:09 UTC,"Dima, the tracking part of this problem is a little misleading. The Xenial 4.15 HWE kernel is basically the Bionic 4.15 kernel recompiled on Xenial and we track those problems only for the Bionic series (even though he problem technically showed up in Xenial). That's why I removed the Xenial tags and references."
1827884,2019-07-30 13:02:42 UTC,"user@user:~$ cat /proc/cmdline
BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-57-generic root=UUID=50c3a930-a3e9-4444-b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid
user@user:~$
user@user:~$ uname -a
Linux user 4.15.0-57-generic #63~lp1827884 SMP Mon Jul 29 15:10:18 UTC 2019 i686 i686 i686 GNU/Linux
user@user:~$"
1827884,2019-07-30 12:52:47 UTC,I've tested https://kernel.ubuntu.com/~cking/lp1827884/4.15 on xenial. It works. Xorg starts too.
1827884,2019-07-03 02:06:14 UTC,I've tried. It's still happening.
1827884,2019-07-30 12:25:50 UTC,Why this report is a duplicate of https://bugs.launchpad.net/bugs/1838115 ? That report is more recent than this one.
1827884,2019-07-30 08:53:39 UTC,"Dima, in comment #75 you mentioned that you experienced issues with Xenial. What kernel version were you running? We believe this issue is tied to PTI for 32-bit but that feature was only backported to the 4.15 kernel, not the 4.4. kernel."
1827884,2019-07-30 06:52:18 UTC,"I`ve tested 4.15.0 kernel from: https://kernel.ubuntu.com/~cking/lp1827884/4.15, the problem seems to be fixed."
1827884,2019-07-29 15:46:03 UTC,I've uploaded a 4.15.0 kernel with the same patches applied: https://kernel.ubuntu.com/~cking/lp1827884/4.15
1827884,2019-07-29 13:14:50 UTC,"I`ve tested kernel from: https://kernel.ubuntu.com/~cking/lp1827884/, the problems seems to be fixed, but what about kernel version 4.15.0?"
1827884,2019-07-29 10:32:18 UTC,I think this may be solved using the following fix: https://lists.ubuntu.com/archives/kernel-team/2019-July/thread.html
1827884,2019-07-29 07:15:44 UTC,"Anthony, I had that problem with fresh Lubuntu 16.04 on Toshiba Sattelite L300. I don't know why but after a while the problem disappeared. Try ""sudo update-initramfs -ck all"" and removing of ""quiet"" option from /etc/default/grub (and then ""sudo update-grub"").
And if ""nopti"" option doesn't help I think you should make a separate bug report."
1827884,2019-07-28 09:30:26 UTC,"I have been searching for this bug-report for a few weeks now, and I can confirm that I too am experiencing this bug.
After updating from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS, upon first boot I experienced a black screen on my laptop (HP Presario V4000 from 2014). The backlight was still on and so was the fan, though there was no hard-drive activity light. After waiting for around half an hour, I cut the power and rebooted.
Upon the second boot, everything worked fine, leading me to beleive it was simply a problem after updating. The next day, I booted the laptop again and experienced the black screen bug. I soon figured out that it occured every second boot (Roughly, sometimes I would experience the bug twice in a row).
I decided to try “Advanced options for Ubuntu”, and selected “Ubuntu, with Linux 4.15.0-45-generic”. This worked first try. After testing multiple times, I never got a failed boot.
Unfortunately I can confirm that this bug still occurs occasionally when I select:
“Ubuntu, with Linux 4.15.0-54-generic” or
“Ubuntu, with Linux 4.15.0-55-generic”."
1827884,2019-07-30 12:06:40 UTC,"Juerg, I used xenial-hwe kernel (4.15). Kernel 4.4 works fine."
1827884,2019-07-02 18:21:03 UTC,"On 2019-07-02 16:36:27, Andrea Righi wrote:

> This might be a duplicate of 1830433, could you give it a try with this
> test kernel and see if the problem is still happening?
>
> https://kernel.ubuntu.com/~arighi/LP-1827884/
"
1827884,2019-05-16 12:46:34 UTC,This problem also exists in kernel 4.15.0-50 version on Ubuntu 18.04.
1827884,2019-06-05 06:45:37 UTC,This problem also exists in kernel 4.15.0-51 version on Ubuntu 18.04 (i386).
1827884,2019-05-13 04:29:30 UTC,apport information
1827884,2019-05-13 04:29:27 UTC,apport information
1827884,2019-05-13 04:29:24 UTC,apport information
1827884,2019-05-13 04:29:21 UTC,apport information
1827884,2019-05-13 04:29:20 UTC,apport information
1827884,2019-05-13 04:29:18 UTC,apport information
1827884,2019-05-13 04:29:15 UTC,apport information
1827884,2019-05-13 04:29:13 UTC,apport information
1827884,2019-05-13 04:29:11 UTC,apport information
1827884,2019-05-13 04:29:09 UTC,apport information
1827884,2019-07-02 16:36:27 UTC,"This might be a duplicate of 1830433, could you give it a try with this test kernel and see if the problem is still happening?"
1827884,2019-05-13 04:29:04 UTC,apport information
1827884,2019-05-13 04:29:03 UTC,apport information
1827884,2019-05-12 13:39:48 UTC,Here is the Ubuntu-bug data collection for my other Dell the exibits the same problem.
1827884,2019-05-12 03:32:33 UTC,I have two old Dell computers which experience a problem similar to what Michael describes.  They work fine at Linux 4.15.0-47 but at 4.15.0-48 they show a corrupted display while booting.  I can revert to 4.15.0-47 and await a fix.
1827884,2019-05-06 15:24:33 UTC,You'll probably want the boot.log?
1827884,2019-05-06 14:00:07 UTC,This change was made by a bot.
1827884,2019-05-13 04:50:22 UTC,apport information
1827884,2019-05-13 04:50:24 UTC,apport information
1827884,2019-05-13 04:29:07 UTC,apport information
1827884,2019-05-13 04:50:29 UTC,apport information
1827884,2019-05-19 08:31:30 UTC,"I have the same issue on 3 Laptops (2 HP nc6230 and 1 Asus, all 32bit systems), only solution so far is to revert to Linux 4.15.0-47. I could not find any useful hint in any of the logs.
One strange thing is that only every second boot fails. After hard power-off a hanging boot the next boot works fine one time, but the next one again hangs.
I could not even get a text console with Ctrl-Alt-F1 in case it hangs."
1827884,2019-05-13 04:50:27 UTC,apport information
1827884,2019-05-18 19:15:20 UTC,I have a Lenovo G500 (32 bit laptop about 5 years old).
1827884,2019-05-17 06:49:17 UTC,I have three different machines running Xubuntu 18.04 i386. All are affected.
1827884,2019-05-28 11:32:56 UTC,"I have precisely the same issue:
Dell Latitude D530
Intel graphics GM965/GL960
Lubuntu 18.04 (32 bit)
Kernel 4.15.0-50"
1827884,2019-05-13 13:04:23 UTC,"This problem affected all Intel CPUs we have, except for Atoms"
1827884,2019-05-13 05:32:17 UTC,"Update:
HP Laptop: I have upgraded BIOS on the HP6710b laptop to F16, which included upgrade of video BIOS. It had no effect on the boot behaviour."
1827884,2019-05-13 04:50:48 UTC,apport information
1827884,2019-05-17 01:21:46 UTC,I am seeing a similar problem.
1827884,2019-05-13 04:50:42 UTC,apport information
1827884,2019-05-13 04:50:40 UTC,apport information
1827884,2019-05-13 04:50:39 UTC,apport information
1827884,2019-05-13 04:50:32 UTC,apport information
1827884,2019-05-13 04:50:37 UTC,apport information
1827884,2019-05-13 04:50:35 UTC,apport information
1827884,2019-05-13 04:50:45 UTC,apport information
1827884,2019-05-13 04:50:33 UTC,apport information
1827887,2019-05-08 13:31:27 UTC,Yes now since you define a base in the snap you can't use remote parts which is what the `go` part is.
1827887,2019-08-14 13:37:16 UTC,This is no longer part of the documentation
1827890,2019-05-06 16:01:59 UTC,"Fixed in revision b97d65e7919e7d37ecc5f8fce54dc2ace66a1b91
https://git.launchpad.net/kicad/patch/?id=b97d65e7919e7d37ecc5f8fce54dc2ace66a1b91"
1827894,2019-05-06 21:54:25 UTC,"Fixed in revision cd2bd23c37d466de490e8fc1cd4fdd210e74e82d
https://git.launchpad.net/kicad/patch/?id=cd2bd23c37d466de490e8fc1cd4fdd210e74e82d"
1827894,2019-05-06 18:02:27 UTC,Hmm... I can't reproduce this.  Old code perhaps?
1827894,2019-05-06 18:07:03 UTC,I take that back.  It just dropped them on top of existing ones so I didn't notice.
1827897,2019-06-21 15:22:46 UTC,This issue was fixed in the openstack/instack-undercloud 8.4.8 release.
1827897,2019-09-12 09:30:52 UTC,This issue was fixed in the openstack/instack-undercloud 9.5.1 release.
1827897,2019-05-07 18:10:41 UTC,"Reviewed:  https://review.opendev.org/657586
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=5babfee11193d7736d4ab5142121392b7887344c
Submitter: Zuul
Branch:    stable/queens"
1827897,2019-05-06 16:17:33 UTC,Just be aware this bug is more or less related to what I'm doing in https://review.opendev.org/655777
1827897,2019-05-07 03:16:40 UTC,"Reviewed:  https://review.opendev.org/656579
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=11d9fef529300a9268417979d701f45e100f0241
Submitter: Zuul
Branch:    stable/rocky"
1827897,2019-05-06 16:24:19 UTC,oh sorry your bug is for instack-undercloud...
1827897,2019-05-06 16:21:53 UTC,I was referring to: https://bugs.launchpad.net/tripleo/+bug/1763776
1827897,2019-05-07 12:45:13 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/657586"
1827898,2019-05-06 20:49:58 UTC,https://github.com/charmed-kubernetes/jenkins/pull/399
1827900,2019-05-06 21:35:25 UTC,"Hi Vuk, thanks for your input. We do intend to do this, probably within the next six months."
1827900,2019-05-21 13:20:57 UTC,"Hi Vuk,"
1827900,2019-05-21 15:09:09 UTC,"Hi Joseph,"
1827900,2019-05-22 20:32:19 UTC,"Thanks Vuk.  Feel free to ask any questions you may have on #cdk8s on freenode or #cdk on the Kubernetes slack channel, if you'd like more of a fluent discussion."
1827901,2019-11-05 22:03:44 UTC,"Adding a link to related bug 1851434, which is a bit further along toward a fix."
1827901,2019-06-13 16:31:08 UTC,"We're also seeing this in the 3.2.4 web client and it's a serious issue for some libraries because there is no way to override. In addition, we are seeing similar behavior when staff attempts to renew a Long Overdue item, but in this case the message is:"
1827902,2019-05-06 16:13:14 UTC,"Hi George,"
1827902,2019-05-06 21:30:22 UTC,"Hi Vuk, official bundles and docs are almost ready and will be published soon. In the meantime, here's a test bundle you can try:"
1827902,2019-07-01 14:08:23 UTC,CDK 1.15 is now shipped with containerd by default.
1827902,2019-05-06 16:00:30 UTC,Containerd support is a work in progress. It is not available yet in stable or edge.
1827905,2019-05-14 19:47:01 UTC,This issue has been noted as resolved by Madeliene after recent commits
1827905,2019-05-06 20:01:57 UTC,Sent direct message re: sharing design.
1827905,2019-05-06 16:38:27 UTC,"Hi Madeliene,"
1827905,2019-05-06 18:28:16 UTC,"Ok, then that is indeed a connectivity bug and I will work on fixing it.  Can you please paste the output of About->Copy Version Info?"
1827905,2019-05-06 17:57:22 UTC,"We've made some changes to the schematic, which need to be reflected in the PCB netlist."
1827905,2019-05-06 19:56:43 UTC,"Application: kicad
Version: (5.1.0-386-g9f189ca71), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 libidn2/2.1.1 libpsl/0.20.2 (+libidn2/2.1.1) libssh2/1.8.1 nghttp2/1.36.0
Platform: Linux 5.0.4-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.69.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: GCC 8.2.1 with C++ ABI 1013"
1827906,2019-11-22 09:52:16 UTC,"Change abandoned by Athlan-Guyot sofer (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/694145
Reason: This was squashed into https://review.opendev.org/#/c/694144/ to pass ci."
1827906,2019-11-21 16:52:58 UTC,"Reviewed:  https://review.opendev.org/694144
Committed: https://git.openstack.org/cgit/openstack/tripleo-upgrade/commit/?id=2422814df957a0caf340de97bd597d1d6cd5b548
Submitter: Zuul
Branch:    stable/queens"
1827906,2019-11-21 13:47:54 UTC,"Change abandoned by Lukas Bezdicka (<email address hidden>) on branch: stable/rocky
Review: https://review.opendev.org/694126
Reason: Already in rocky."
1827906,2019-11-21 01:18:31 UTC,"Reviewed:  https://review.opendev.org/694125
Committed: https://git.openstack.org/cgit/openstack/tripleo-upgrade/commit/?id=190d72c098ee2ff5e38fa79d2ba95a7aba8af99e
Submitter: Zuul
Branch:    stable/rocky"
1827906,2019-11-13 19:13:46 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/694145"
1827906,2019-11-13 13:39:56 UTC,This issue was fixed in the openstack/tripleo-upgrade 5.0.0 release.
1827906,2019-06-05 17:01:55 UTC,"Reviewed:  https://review.opendev.org/661751
Committed: https://git.openstack.org/cgit/openstack/tripleo-upgrade/commit/?id=707e380e7fa8cda94799c9cc1aef3b70cc6faad2
Submitter: Zuul
Branch:    stable/stein"
1827906,2019-05-28 13:09:39 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661751"
1827906,2019-05-27 11:45:58 UTC,"Reviewed:  https://review.opendev.org/661009
Committed: https://git.openstack.org/cgit/openstack/tripleo-upgrade/commit/?id=fdd2eac1a700747bc23ba4d089a75d2b6d13e041
Submitter: Zuul
Branch:    master"
1827906,2019-05-23 14:24:47 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661009"
1827906,2019-05-13 23:07:26 UTC,ERROR! Invalid options for include_tasks: tags
1827906,2019-11-13 18:16:28 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/694126"
1827912,2019-07-07 04:17:30 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1827912,2019-05-08 03:33:29 UTC,"Could you downgrade your linux version until there is no crackling noise, then we will compare two versions to get what introduced this issue."
1827912,2019-05-08 01:28:42 UTC,apport information
1827912,2019-05-07 03:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827912,2019-05-07 02:39:29 UTC,It sounds like this might be noise on the motherboard itself. Especially if you are hearing crackling when no sound is playing.
1827912,2019-05-08 01:31:15 UTC,"Update: After some unmeasured amount of time, for the first time since ubuntu install on this machine (2017), there is no crackling sound at any moment."
1827915,2019-05-07 09:02:48 UTC,There should definitely be a dialog asking you to confirm the changes (adding the missing library to the table?) and whether to proceed.
1827915,2019-05-07 10:51:57 UTC,Good idea @Michael. The dialog could have the options:
1827915,2019-05-07 11:53:46 UTC,"Popup message:
""It was detect symbol(s) that doesn't belong(s) to any existent library of current project. How do you want do proceed?"""
1827915,2019-05-08 18:00:39 UTC,"From discussion at lp:1828222 I realize that the hierarchical sheet files could be copied, with confirmation to rename, to the current project folder."
1827915,2019-05-11 19:57:52 UTC,"If libraries are available, no problems must be. Symbols must be available regardless of hierarchy"
1827915,2019-05-11 21:23:01 UTC,"@anton,2 not related problem here: copy the symbols and copy the hierarchical sheets (in loop in case of hierarchical sheets inside the copied one)."
1827915,2019-05-11 21:29:34 UTC,"Also, necessary to check the symbols availability when coping each hierarchical sheet and add the available to the current project.
The message to do this should be show just once, not each symbol occurrence."
1827915,2019-06-18 12:05:04 UTC,I think this bug will wait for the new schematic format that with embedded symbols.
1827916,2019-06-26 20:50:52 UTC,This bug was fixed in the package linux-azure - 4.18.0-1023.24~18.04.1
1827916,2019-06-26 20:49:11 UTC,This bug was fixed in the package linux-azure - 4.18.0-1023.24
1827916,2019-06-25 13:08:32 UTC,This bug was fixed in the package linux-azure - 4.15.0-1049.54
1827916,2019-06-26 20:48:30 UTC,This bug was fixed in the package linux-azure - 5.0.0-1010.10
1827916,2019-06-07 19:29:31 UTC,"https://lists.ubuntu.com/archives/kernel-team/2019-June/101209.html
https://lists.ubuntu.com/archives/kernel-team/2019-June/101210.html
https://lists.ubuntu.com/archives/kernel-team/2019-June/101211.html
https://lists.ubuntu.com/archives/kernel-team/2019-June/101212.html"
1827916,2019-06-03 12:59:39 UTC,Any updates on that?
1827916,2019-05-23 20:08:16 UTC,What version is being used on AKS nodes?
1827916,2019-05-06 17:11:53 UTC,This request is for the 16.04 and 18.04 kernels.
1827916,2019-06-10 14:32:37 UTC,"@Josh, @Joseph,"
1827917,2019-05-06 21:54:23 UTC,"Fixed in revision f1a38a6d417701cfdd2545fff4055dfbde027c58
https://git.launchpad.net/kicad/patch/?id=f1a38a6d417701cfdd2545fff4055dfbde027c58"
1827917,2019-05-20 14:08:16 UTC,"I am re-opening because <Escape> still not unselecting in Ubuntu last Nightly  Version 6.0.0-unknown-f21face~86~ubuntu16.04.1, release build.
With I press <Esc> in another toll that not the selection tool, Eschema change to the Selection tool (""blank point tool""). That is prefect correct.
But, once in this basic tool, pressing <Esc> again is expected that all selected objects go to unselect."
1827917,2019-05-20 17:13:53 UTC,We should be mimicking the Pcbnew behavior here.  The first escape drops out of the current tool to the select tool.  The second escape should clear all selections.  This is by design to allow keeping selected objects highlighted when working with a different tool.  I know this is less important than in the board editor but the behavior should be the same.
1827917,2019-05-20 17:27:39 UTC,"Totally agree, and it is work well at Pcbnew. In Eeschema that is missing the last <Esc> behavior."
1827917,2019-05-20 17:38:21 UTC,"@Hildo, sorry about that.  I misunderstood your comments."
1827917,2019-05-20 18:04:35 UTC,Doesn't worry @wayne. My contribution here is at least keep tracking my reported issues.
1827917,2019-05-22 12:18:31 UTC,"@Jeff, I am marking as ""in progress"" because the discussion with @Wayne. Please, close at your will."
1827917,2019-06-13 21:53:56 UTC,"Fixed in revision f1a38a6d417701cfdd2545fff4055dfbde027c58
https://git.launchpad.net/kicad/patch/?id=f1a38a6d417701cfdd2545fff4055dfbde027c58"
1827917,2019-06-26 12:21:37 UTC,I believe this is fixed.  Please re-open if you see it again (with steps).
1827918,2019-05-23 06:17:46 UTC,"Please help to retest this issue, as https://review.opendev.org/659214 is already merged."
1827918,2019-06-05 18:43:17 UTC,"verified
BUILD_ID=""2019-06-03_18-34-53"
1827918,2019-05-13 06:05:58 UTC,"This bug is duplicated with https://bugs.launchpad.net/starlingx/+bug/1826562.
The errors in the horizon.log is caused by cephclient, 3 apis are lost in the new python-cephclient."
1827918,2019-05-06 17:31:52 UTC,Marking as release gating; suggest to first focus on the errors reported in horizon.log
1827918,2019-05-15 06:14:17 UTC,Can be fixed by https://review.opendev.org/659214
1827919,2019-05-10 16:11:40 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827920,2019-05-10 16:55:41 UTC,"This discussion should probably be moved to the mailing list as its not related to this bug, but I'd be in favour of having handles for wires and buses also (with forced 90° angles by default, unlike regular graphic lines). See [1] for some inspiration."
1827920,2019-05-10 16:26:33 UTC,"Lines do have handles now, but wires and busses don't.  It'd be easy enough to add, it just felt a bit weird to me...."
1827920,2019-05-11 00:56:46 UTC,"Sometimes I need to do a free (not force 90° angles) wires, but it's a exception in the schematic to, for example, represent crossing wire cables. So, could be a option to disable, but default keep 90°."
1827920,2019-05-10 15:42:28 UTC,I interpreted this as not being able to resize a graphic line in Eeschema (used to be able to move a endpoint with 'G'). I assumed Eeschema would eventually get the drawing tools from Pcbnew (edit lines etc by selecting and dragging the handles around).
1827920,2019-05-10 15:38:02 UTC,I think it's related with a wrong report that I made about the extinct <tab> command. But:
1827920,2019-05-10 15:08:15 UTC,"@Hildo, can you be more specific?  What tool were you using?  What hotkey or context menu item?"
1827920,2019-05-10 16:22:50 UTC,"@Jeff, ah, looks like your latest commits solved it."
1827923,2019-05-06 18:23:42 UTC,"https://kb.isc.org/docs/aa-00716 is also helpful:
""""""
BIND 9.9.0 introduced multiple UDP listeners to improve performance, which means that in a multi-threaded BIND installation, there are effectively more sockets being monitored for client-side queries. If you are also listening on multiple interfaces (real or virtual), this might mean that # interfaces x # UDP listeners exceeds 64. The outcome of this is that on a busy server (particularly a busy recursive server that is also opening connections to make iterative queries of authoritative servers), the default number of FD events is already too small.
"""""""
1827923,2019-05-09 14:48:12 UTC,"I wonder what the downside is of rebuilding with a higher limit. If there is none, why isn't upstream doing this already?"
1827923,2019-08-02 14:37:43 UTC,This is already reported upstream at https://gitlab.isc.org/isc-projects/bind9/issues/220
1827923,2019-08-02 14:42:31 UTC,Not much else to do pending upstream feedback. This doesn't seem like it's important enough to warrant patching without upstream's lead. Please let me know if this turns out to be more essential to land - patching it shouldn't be difficult.
1827923,2019-08-05 07:29:56 UTC,"Thanks for the link Robie, I updated the upstream bug with some info that was requested. Lets see how the discussion there ends."
1827923,2020-01-14 21:04:18 UTC,"I'm updating bind9 to 9.14, which was mentioned in the upstream bug report in the phrase ""With 9.14 the problem should be much less prominent"", for which I asked for clarification."
1827924,2019-05-27 11:34:09 UTC,This bug was fixed in the package samba - 2:4.3.11+dfsg-0ubuntu0.16.04.21
1827924,2019-05-27 11:44:15 UTC,This bug was fixed in the package samba - 2:4.7.6+dfsg~ubuntu-0ubuntu2.11
1827924,2019-05-23 12:18:01 UTC,"I asked upstream and there is no reproducer for this bug at the moment, other than having affected people try a package with the fix for https://bugzilla.samba.org/show_bug.cgi?id=13315"
1827924,2019-05-22 19:51:36 UTC,"This may be https://bugzilla.samba.org/show_bug.cgi?id=13315, found also in https://bugzilla.samba.org/show_bug.cgi?id=13315, but we don't even have the crash file and I can't reproduce it at the moment by just connecting using SMB1: it won't crash."
1827924,2019-05-23 15:28:16 UTC,I have uploaded packages that contain the bugfix that likely solves this issue to the security team PPA here:
1827924,2019-05-23 12:04:16 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827925,2019-05-08 20:25:22 UTC,Marking as release gating; issue related to recent feature to use ceph backend for all configs
1827925,2019-07-09 09:49:17 UTC,This bug seems unreproducible with a current load.
1827925,2019-08-15 15:36:26 UTC,"Was unable to unlock after applying the label
fix from 1840262 needed to retest"
1827925,2019-08-15 19:16:07 UTC,Confirmed failure to unlock after applying the label. Tracking issue with LP-1840351
1827925,2019-05-07 16:41:33 UTC,Also seen on AIO-DX using build 20190506T233000Z
1827928,2019-08-27 01:55:57 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827928,2019-08-27 23:21:57 UTC,This may be a duplicate of bug 1565950. What version of Ubuntu were you trying to install where you encountered this?
1827928,2019-11-08 11:43:14 UTC,"ubuntu 18.04.3 LTS has this issue. I'm not interested in secure boot but encrypted /boot. The grub package points to grub2-common (2.02-2ubuntu8.13). Even with the update detailed in the other post, the problem still exists. I can't load cryptomount and ubuntu starts with only grub shell."
1827928,2019-11-08 13:46:37 UTC,"(replying to #2)
Sorry, I didn't see your reply earlier. This could be argued either way as a separate issue or not, but most importantly, the fix for bug 1565950 will also resolve this issue."
1827929,2020-05-22 19:47:20 UTC,"Lastly, much of the focus on DOS partition tables comes from subiquity's re-use
existing partitions; it's still extremely common to have a dos partition table
rather than gpt."
1827929,2020-05-22 18:01:16 UTC,"On Fri, May 22, 2020 at 04:09:51PM -0000, Ryan Harper wrote:

> We will need two formats for the hybrid mode, ptable: gpt and ptable:
> dos
"
1827929,2020-04-08 21:33:11 UTC,"On Wed, Apr 08, 2020 at 05:39:32PM -0000, Dan Watkins wrote:

> Steve, does ""the grub install to disk is triggered for both"" mean we
> should be invoking grub-install twice (once for each target), or do we
> have another mechanism that we can hook into to perform the install for
> all (available|applicable|...) grub targets?
"
1827929,2020-05-22 19:46:13 UTC,"> On Fri, May 22, 2020 at 04:09:51PM -0000, Ryan Harper wrote:
> > We will need two formats for the hybrid mode, ptable: gpt and ptable:
> > dos
>
> I don't see why this should be the case. Are we not emitting GPT everywhere
> today, even when the system is booting in BIOS mode? Late-model BIOSes do
> support booting from GPT; I would think at this point anything that doesn't
> support GPT is too old to be of practical concern.
>
> So a GPT table with a bios_grub partition and an EFI System Partition should
> suffice.
"
1827929,2020-05-22 16:09:51 UTC,"We will need two formats for the hybrid mode, ptable: gpt and ptable: dos"
1827929,2019-10-23 19:22:35 UTC,"I don't know what Dimitri's comment refers to.  As far as I'm concerned this is already well-defined, and you're correct that the curtin piece is simply enforcing that both shim-signed and grub-pc get installed (and the grub install to disk is triggered for both)."
1827929,2019-10-23 14:15:55 UTC,"Hi Steve, Dmitri,"
1827929,2019-10-22 20:54:19 UTC,"Hm, imho this needs more. One has to run and install grub on one or more devices."
1827929,2019-05-28 21:24:57 UTC,IIUC
1827929,2020-04-08 17:39:32 UTC,"Steve, does ""the grub install to disk is triggered for both"" mean we should be invoking grub-install twice (once for each target), or do we have another mechanism that we can hook into to perform the install for all (available|applicable|...) grub targets?"
1827930,2019-06-06 20:55:33 UTC,This bug was fixed in the package livecd-rootfs - 2.578.5
1827930,2019-06-04 10:40:45 UTC,Verified livecd-rootfs/2.578.5 on Disco:
1827930,2019-06-03 23:47:41 UTC,"Hello Balint, or anyone else affected,"
1827930,2019-05-20 14:31:52 UTC,This bug was fixed in the package livecd-rootfs - 2.408.46
1827930,2019-05-20 14:31:16 UTC,This bug was fixed in the package livecd-rootfs - 2.525.24
1827930,2019-05-20 14:30:45 UTC,"Since this is verified, change small enough and only affecting image builds, let me release this early as per uploader request."
1827930,2019-05-17 17:26:33 UTC,This bug was fixed in the package livecd-rootfs - 2.584
1827930,2019-05-17 17:21:08 UTC,"Verified livecd-rootfs/2.408.46 on Xenial:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/livecd-rootfs/20190517_164838_751fa@/log.gz
...
16K	livecd.ubuntu-cpc.wsl.rootfs.manifest
184M	livecd.ubuntu-cpc.wsl.rootfs.tar.gz
...
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/livecd-rootfs/20190517_155655_751fa@/log.gz
...
16K	livecd.ubuntu-cpc.wsl.rootfs.manifest
199M	livecd.ubuntu-cpc.wsl.rootfs.tar.gz
..."
1827930,2019-05-17 14:26:05 UTC,"Hello Balint, or anyone else affected,"
1827930,2019-05-17 14:25:18 UTC,"Hello Balint, or anyone else affected,"
1827930,2019-05-20 14:31:22 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827931,2019-05-20 12:53:31 UTC,https://review.opendev.org/#/c/657589 is the fix. In the gate.
1827931,2019-05-06 20:17:13 UTC,We can't have the rocky version of standalone parent to main standalone job where use os-tempest is set to true afaict.
1827931,2019-05-06 20:06:52 UTC,Use os_tempest is marked false in rocky
1827931,2019-05-06 20:05:51 UTC,master and stein have a os_tempest setup.cfg that works.  Rocky and prior does not.
1827931,2019-05-06 20:08:30 UTC,In http://logs.openstack.org/16/656416/4/check/tripleo-ci-centos-7-standalone/62fc8a1/logs/undercloud/var/log/extra/dump_variables_vars.json.txt.gz
1827931,2019-05-06 20:02:29 UTC,setup.cfg in openstack-ansible-tempest should put files in
1827931,2019-05-06 20:03:38 UTC,The bug is here:
1827933,2019-09-20 12:36:31 UTC,I can confirm this bug but I believe it is an issue in the Atom snap itself. It is not an issue affecting snapd or all snaps in general.
1827934,2019-05-06 19:30:08 UTC,This change was made by a bot.
1827934,2019-05-21 16:39:44 UTC,The HDMI port probably connects to the Nvidia card instead of Intel one.
1827936,2019-05-07 20:19:51 UTC,Same behavior on BM 2+2+2.
1827936,2019-05-07 20:23:17 UTC,"---------------------------------------------------
storage-1:~$ date
Tue May  7 06:20:58 CDT 2019
storage-1:~$ ps -A | grep ceph*
storage-1:~$ ps -A | grep ceph*
storage-1:~$ ps -A | grep ceph*
storage-1:~$ ps -A | grep ceph*
storage-1:~$ date
Tue May  7 08:43:50 CDT 2019
---------------------------------------------------
[wrsroot@controller-0 bin(keystone_admin)]$ ceph osd tree
ID CLASS WEIGHT  TYPE NAME              STATUS REWEIGHT PRI-AFF
-1       0.87097 root storage-tier
-3       0.87097     chassis group-0
-4       0.43549         host storage-0
 0   ssd 0.43549             osd.0          up  1.00000 1.00000
-5       0.43549         host storage-1
 1   ssd 0.43549             osd.1        down        0 1.00000
[wrsroot@controller-0 bin(keystone_admin)]$ ceph osd tree
---------------------------------------------------
[wrsroot@controller-0 ~(keystone_admin)]$ ceph -s
  cluster:
    id:     85261611-1245-4b21-bd0b-cc9afdc26cff
    health: HEALTH_WARN
            Degraded data redundancy: 1719/3438 objects degraded (50.000%), 147 pgs degraded, 856 pgs undersized"
1827936,2019-05-08 15:56:44 UTC,"Kernel warnings about jbd2/rbd0-* task blocked are to be expected because this system is running with a single OSD in replication 1 and killing ceph-osd blocks any client using Ceph including mariadb container:
- rbd0 is mounted to /var/lib/kubelet/plugins/kubernetes.io/rbd/mounts/kube-rbd-image-kubernetes-dynamic-pvc-765f2082-701c-11e9-8184-9662bc166b57.
- rbd1 is mounted to /var/lib/kubelet/plugins/kubernetes.io/rbd/mounts/kube-rbd-image-kubernetes-dynamic-pvc-a312923d-701c-11e9-8184-9662bc166b57
- mysqld (mariadb) is also blocked:
    2019-05-06T18:30:29.604 controller-0 kernel: err [ 4562.873872] INFO: task mysqld:249372 blocked for more than 120 seconds."
1827936,2019-05-08 20:27:23 UTC,Marking as release gating; process kill should not result in a kernel hang. Maybe related to the new ceph version.
1827936,2019-05-10 19:20:16 UTC,"For stx.retestneeded, this label should only be removed by the reporter of the bug when they've tested the provided fix."
1827936,2019-05-14 17:03:45 UTC,"It is hard for me to reproduce the kernel hang issue, and I killed ceph-osd process for many times but the thread will recover after seconds."
1827936,2019-05-22 13:27:54 UTC,"@Tingjie to add the build# for the issue reproduced once. May related to kernel driver.
@Ovidiu updated the analysis results, Ceph-osd was killed mulitple times.Need to retest it. if the user has more than 1 OSD in the system, the issue will not occur."
1827936,2019-05-22 19:59:09 UTC,"Since Cindy removed the stx.2.0 release tag, I'm setting the priority to Low as this bug is no longer considered gating."
1827936,2019-05-10 19:19:11 UTC,"Tingjie, Please don't remove tags added by me. They are added as part of initial bug screening. If you feel a bug should not be gating, please add a clear justification as to why. This then needs to be reviewed with the  sub-project lead and agreed to before the release tag is removed."
1827937,2019-05-06 20:21:59 UTC,Also applies to the System Information -> Services page.
1827937,2019-05-08 20:28:54 UTC,Not gating / low priority. Would be a good opportunity for someone ramping up (added stx.helpwanted)
1827937,2019-05-24 07:55:48 UTC,"Found it's an awkward one after some investigation. Two ways to solve this,but seems not worthy.1st:modify horizon code， add some hard code to transform faultmanagement to Fault Management.2nd: modify FM service entpoint's type to fault-management...,So, for now I am gonna leave it alone."
1827938,2019-07-10 18:35:30 UTC,+1 to providing access to result counts
1827939,2019-05-06 20:42:16 UTC,"Like this idea, if possible."
1827941,2019-05-11 13:25:56 UTC,"Application: kicad
Version: (5.1.2)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013
Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON"
1827941,2019-05-12 08:54:31 UTC,"I've just tried typing in every letter, number and symbol (uppercase and lowercase) and can't recreate this. Are you sure you have ""Filter footprint list using a partial name or a pattern"" checked? Whats the status of the other filter buttons?"
1827941,2019-07-12 04:17:22 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1827941,2019-05-06 20:40:12 UTC,Please copy the full version information from About KiCad -> Copy Version Info.
1827942,2019-09-17 19:39:37 UTC,"Zavier, have you worked on a solution for this bug? If so, could you post a comment here that explains what you've done or where you could share the code? We use the status ""Fix Committed"" to mean ""code has been shared and reviewed, and has been accepted into Evergreen"", and that process usually happens in comments on the bug ticket. Since that hasn't happened here yet, I'll set the status back to ""New"" for now."
1827942,2019-09-17 21:57:51 UTC,My mistake.
1827942,2019-09-17 22:25:51 UTC,"Thanks, Zavier!"
1827942,2019-12-11 15:37:03 UTC,"Thanks, Zavier!  It works well for me.  Signoff branch at user/sandbergja/lp1827942_angular_protect_modal_closures_signoff"
1827942,2019-12-11 15:38:12 UTC,"And I agree, Jeff.  This makes sense as a bugfix."
1827942,2019-12-27 15:33:48 UTC,"Pushed to master, rel_3_4, and rel_3_3. Thanks, Zavier and Jane!"
1827942,2019-12-27 16:07:20 UTC,I also pushed a follow-up that fixes lint warnings as well as an issue that prevented progress dialogs from appearing.
1827943,2019-05-06 21:06:21 UTC,"+1 from me to adding ""Editing X of Y rows"" and a cancel button"
1827943,2019-05-06 22:30:02 UTC,"Also +1 to ""editing x of y rows"" and a cancel button, for the current way of editing multiple rows."
1827944,2020-01-29 09:50:44 UTC,"Kernel 5.3 officially released by Canonical does not work with 418.56 from this PPA.
Branch 430 does not support my GPU."
1827944,2019-05-13 03:04:17 UTC,It sounds like only official Ubuntu kernels will support DKMS properly. So I don't think this is going to be a valid bug in dkms.
1827944,2019-05-22 19:52:30 UTC,Side note: the issue is fixed in nvidia-430.14
1827944,2019-05-14 11:38:56 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827944,2019-06-06 14:50:08 UTC,"According to Nvidia's website, nvidia-430 does not support all the nvidia-418 compatible hardware."
1827946,2019-05-06 23:20:59 UTC,Let me know if there's any command I can run in ldb to help. LDB is dark magic to me so detailed instructions are appreciated.
1827946,2019-05-16 21:10:00 UTC,6676d72b7fc38d61d93af5d2898f8175e0ac1fb7
1827946,2019-05-06 23:19:31 UTC,"* (run-crash-demo)
main thread: Starting main lisp on thread
main thread: Wait on sem #S(SB-THREAD:SEMAPHORE
                            :NAME NIL
                            :%COUNT 0
                            :WAITCOUNT 0
                            :MUTEX #<MUTEX ""semaphore lock"" (free)>
                            :QUEUE #<WAITQUEUE  {10036D3F03}>).
foreign callback : in callback waiting on mutex
main thread: Doing a full GC.
fatal error encountered in SBCL pid 8504(tid 00000000010D18C0):
thread 00000000050D2000: bogus esp: 0000000000C5F2B0"
1827946,2019-05-06 22:32:23 UTC,What does it say after entering ldb?
1827947,2019-05-08 13:47:33 UTC,This is somewhat annoying.  The problem is we have multiple open file statements in the file menu so the real issue may be somewhat larger than just a missing open file shortcut.  That's probably why no shortcut was provided.  Which open should you assign the shortcut to?  Perhaps we need to rethink all of these open file targets and use the more typical wildcard/file type selection paradigm.
1827947,2019-05-10 00:32:30 UTC,"Wayne, you are totally right, it is important to think a good approach here. While EEschema and PcbNew have really good shortcuts, the other tools lack this feature."
1827948,2019-06-27 21:34:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827948,2019-06-01 17:47:39 UTC,There is one problem with colibre: it doesn't work with dark themes :/
1827948,2019-05-31 09:38:48 UTC,I'm a +1 for Colibre too
1827948,2019-05-31 08:58:29 UTC,Thanks for the detailed analysis mpt!
1827948,2019-05-31 08:42:58 UTC,Would someone be able to post some screenshots showing Colibre so that we can all see what's being discussed?
1827948,2019-05-10 14:28:20 UTC,"Hmm. Personally I prefer Colibre as I find it to be the most professional icon theme for LibreOffice. But if the Yaru team feels that Breeze fits Yaru better, then go for it."
1827948,2019-05-26 12:34:14 UTC,"The breeze icons are calmer, and they are clearer in a few cases: for example, New (where elementary squanders 🗋 recognisability in redundantly conveying what kind of file will be created), Cut (where elementary’s puffy scissors look to me like a rabbit using binoculars), and, though it pains me to say it, Save (where a floppy disk might be a relic, but elementary’s arrow-on-a-rectangle is just mysterious). And breeze uses a “+” emblem more consistently, for the various Insert commands, than elementary does."
1827948,2019-05-07 16:58:11 UTC,"In isolation I don't prefer one icon set to the other, but I agree that Breeze is a better fit for the desktop style, so I would be +1."
1827948,2019-05-07 15:15:37 UTC,"Hm.  Tricky.  I quite like the straightforwardness of the Breeze icons.  But I also tend to use the ""feel"" of the icons to navigate quickly, and that comes from colour as well as shape.  So I don't really have a proper answer at this point.  I will loop in Design for more informed feedback."
1827948,2019-05-07 15:08:44 UTC,"On one side, breeze icons might look a bit colder, but they're actually graphically closer to yaru's symbolic icons"
1827948,2019-05-07 14:41:58 UTC,"Please could someone add a couple of screenshots for Before and After.
We can ask design to comment."
1827948,2019-05-07 14:33:31 UTC,"libreoffice selects the default icon theme dynamically based on the desktop environment. breeze is already the default icon theme on KDE and LXQt, whereas GNOME, Mate and Unity use elementary by default (see https://cgit.freedesktop.org/libreoffice/core/tree/vcl/source/app/IconThemeSelector.cxx#n51)."
1827948,2019-05-26 15:35:59 UTC,"Both breeze and colibre would be a great improvement over the elementary icons, in terms of consistency.
If colibre fits you more due to it's colors, I would also +1 this decision, to get rid of those eOS 3d icons, that really don't fit at all to the Yaru symbolic icon set."
1827949,2019-06-27 15:07:16 UTC,"verified
BUILD_ID=""20190620T013000Z"""
1827949,2019-05-22 20:31:40 UTC,"I expect this is a duplicate of https://bugs.launchpad.net/starlingx/+bug/1826418
Duplicate bug was merged on May 22. Review: https://review.opendev.org/660424"
1827949,2019-05-22 20:16:19 UTC,"yes, I would say unexpectedly reappeared"
1827949,2019-05-22 19:55:53 UTC,"Wendy, Is the issue basically that an unexpected config out-of-date alarm was raised after a swact?"
1827949,2019-05-22 20:15:38 UTC,The alarm 250.001 had cleared before the swact but reappeared after the swact without a corresponding set event in the fm-event.log
1827951,2019-05-06 22:00:31 UTC,Link to the Eoan fix:
1827951,2019-05-08 17:09:59 UTC,"Hello Brian, or anyone else affected,"
1827951,2019-05-10 14:41:26 UTC,I tested an upgrade from bionic to disco and confirmed that this is fixed.
1827951,2019-05-10 15:13:23 UTC,I've also verified this during an upgrade from Cosmic to Disco.
1827951,2019-05-13 19:09:46 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.16.4
1827951,2019-05-13 19:09:56 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827952,2019-05-24 13:36:41 UTC,"Reviewed:  https://review.opendev.org/660893
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=34c627eadc8ee589f28e7961e8648adbd1d15f80
Submitter: Zuul
Branch:    master"
1827952,2019-05-23 06:34:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660893"
1827952,2019-05-22 00:39:07 UTC,"I could find the error log in my deployment also. And it is benign as Al mentioned.
Will have a check with it."
1827952,2019-05-13 17:32:58 UTC,"Marking as release gating; needs further investigation.
The reporter says the issue is 100% reproducible (although this was not reported in the May 9th sanity), so marking as high priority"
1827952,2019-05-07 12:55:36 UTC,"The error flagged in this launchpad is benign, although it should be fixed.  That error log always occurs and adds excess noise in the logs."
1827952,2019-05-23 06:16:45 UTC,"please check the sysinv.log from https://bugs.launchpad.net/starlingx/+bug/1826912, wondering if you're seeing the similar issue?
and can we reproduce it in latest ISO? we've fixed some application-apply issue due to OOM (1826308, 1826445) and Ceph Rest API issue (1827521)?"
1827953,2019-07-18 19:17:57 UTC,The version of gnome-shell in the proposed pocket of Disco that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.
1827953,2019-07-31 16:34:40 UTC,This bug was fixed in the package gnome-shell - 3.32.2-2ubuntu1~ubuntu19.04.1
1827953,2019-07-31 16:24:42 UTC,"The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827953,2019-07-19 09:49:59 UTC,Did I miss something?
1827953,2019-07-09 19:03:51 UTC,"I tested gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 from disco-proposed and I had no problem to login, so it seems to be fixed."
1827953,2019-05-21 20:24:48 UTC,This bug was fixed in the package gnome-shell - 3.32.2-1ubuntu1
1827953,2019-07-02 18:10:57 UTC,"Hello Jan, or anyone else affected,"
1827953,2019-05-07 09:03:35 UTC,(installing gnome-clocks and adding dusserdorf as a location triggers the issue)
1827953,2019-05-07 09:02:17 UTC,"Ok, confirmed and it's reported upstream and fixed in https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/518"
1827953,2019-05-07 08:49:51 UTC,"what locations did you configure in gnome-clocks?
what's the output of that command
$ gsettings get orc.gnome.clocks world-clocks"
1827953,2019-05-07 02:41:05 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1827953,2019-05-06 22:32:54 UTC,"This seems to happen both when you have world clocks configured before upgrading from cosmic to disco, as well as when configuring them after upgrading."
1827957,2020-06-26 08:30:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827958,2020-03-23 19:26:47 UTC,Thanks for looking into this.
1827958,2020-03-22 10:50:18 UTC,"@solotareff, I've an Acer Swift SF514-52TP and you solution worked for me too!"
1827958,2020-03-22 10:25:41 UTC,"I have seek very long to find the solution on Switf5 Acer. the solution is :
sudo gedit /etc/default/grub"
1827958,2019-12-13 10:27:38 UTC,Any solution for that bug ? I'm on Manjaro and I've this bug too.
1827958,2020-03-22 10:48:51 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827961,2020-01-06 13:12:44 UTC,This bug was fixed in the package linux - 5.0.0-38.41
1827961,2019-12-05 11:27:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'."
1827961,2019-12-06 08:16:22 UTC,"Tested the proposed Bionic kernel (4.15.0-73) on a ThinkPad X1 Carbon 7th with Mac Pass Through Enabled in BIOS, this issue was fixed."
1827961,2019-12-06 09:15:19 UTC,"Also tested the disco-proposed kernel (5.0.0-38) on a ThinkPad X1 Carbon 7th with Mac Pass Through Enabled in BIOS, this issue was fixed."
1827961,2019-12-06 12:34:06 UTC,"Also tested the eoan-proposed kernel (5.3.0-25) on a ThinkPad X1 Carbon 7th with Mac Pass Through Enabled in BIOS, this issue was fixed."
1827961,2020-01-06 12:53:38 UTC,This bug was fixed in the package linux - 5.3.0-26.28
1827961,2020-01-06 13:26:17 UTC,This bug was fixed in the package linux - 4.15.0-74.84
1827961,2019-12-04 07:05:06 UTC,I am traveling and won't be able to connect to my docking station for a while. Should be back in the office mid January and will report back then if nobody else is able to confirm that the fix is working.
1827961,2020-01-10 08:33:39 UTC,Hi!
1827961,2020-01-31 07:15:11 UTC,"After booting into 5.3.0-26 on my Lenovo X390, it has started to loose network connection when connected to the Thunderbolt 3 Gen 2 dock after a while.  No traffic goes through.  Enabling wifi after it works fine, but unselecting ""Enable Networking"" in network manager makes the whole computer hang (can move mouse, but no input from keyboard is registered anymore, or so it seems at least)"
1827961,2020-02-04 05:34:53 UTC,"For a387 device:
https://lkml.org/lkml/2020/2/4/5"
1827961,2020-02-06 11:21:59 UTC,"OK, done: LP: #1862159"
1827961,2020-11-20 12:57:26 UTC,Hello!
1827961,2020-11-20 13:22:54 UTC,I don't think MAC passthrough should work for cross-vendor hardwares..
1827961,2020-01-06 22:31:20 UTC,This bug was fixed in the package linux - 5.4.0-9.12
1827961,2019-12-03 15:44:39 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1827961,2019-06-15 00:17:36 UTC,"Installed and booted your kernel, dmesg attached."
1827961,2019-11-05 16:56:15 UTC,https://lkml.org/lkml/2019/11/5/398
1827961,2019-05-20 20:39:49 UTC,Thank you for your reply and for looking into this issue. I will contact Lenovo but I won't get my hopes up. Operating the dock w/o MAC passthrough is luckily not a big deal for me.
1827961,2019-06-05 09:33:27 UTC,"Looks like it's very alike Dell's Mac passthrough, can you provide acpidump?"
1827961,2019-06-07 08:26:39 UTC,"Here you go...
Please let me know if you need anything else."
1827961,2019-06-14 07:21:23 UTC,"Please install and boot this kernel:
https://people.canonical.com/~khfeng/lp1827961/"
1827961,2019-05-07 01:00:07 UTC,This change was made by a bot.
1827961,2019-07-11 06:20:34 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1827961/"
1827961,2019-12-03 15:42:31 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1827961,2019-07-21 06:44:47 UTC,I can confirm that the new kernel indeed supports Dock MAC pass through.
1827961,2019-09-29 09:37:26 UTC,"Are there any updates regarding this patch? Personally I am using Fedora 30 right now on my ThinkPad L380 Yoga and have the same problem with MAC Passthrough. The Dock I am using is a Lenovo USB-C Dock (vid_17ef pid_a359). I guess it uses the same RTL8153 chip as the thunderbolt dock. I would appreciate it if you could publish the source patches, as there is only the ubuntu kernel binary. Thank you in advance for the help."
1827961,2019-10-07 17:54:22 UTC,Cleaned up patch to make it upstreamable. Only compiled tested.
1827961,2019-10-18 16:57:16 UTC,"Binary kernel package can be found here:
https://people.canonical.com/~khfeng/lp1827961-5.4/"
1827961,2019-10-21 06:38:51 UTC,I tested the above kernel on a ThinkPad X1 Carbon 7th with a Thunderbolt Dock 2nd Gen.
1827961,2019-10-21 06:50:23 UTC,dmesg attached.
1827961,2019-10-25 11:19:16 UTC,https://lkml.org/lkml/2019/10/25/392
1827961,2019-07-22 06:47:51 UTC,There's a conversation between Lenovo and Canonical. I'll upstream the patch once all details become clear.
1827961,2019-05-19 15:07:30 UTC,"The usb ethernet chip in LP: #1579984 is r8153, while this Lenovo Dock uses cdc_ether. In general this needs special driver support, where the mechanism is opaque to us."
1827962,2019-05-07 13:15:25 UTC,"Hi Jeff,"
1827962,2019-05-07 11:09:11 UTC,"Hi Tom,"
1827962,2019-05-07 14:25:18 UTC,"Hi Tom,"
1827967,2020-02-04 03:31:29 UTC,"Hi Hui Wang,"
1827967,2020-02-07 02:31:34 UTC,"OK, just added a commment in #1834771"
1827967,2020-02-06 15:04:01 UTC,correction: I don't have any testing kernels installed NOW. In December 2019 I tried your kernels and failed to uninstall them correctly. In the end I had to go back to a system backup. If you tell me how to unload/reload the HD-audio driver and what to do afterwards I'd be willing to help. But anyway I think this discussion should better take place there: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771
1827967,2020-02-06 02:27:56 UTC,"Ok, I'm just a user and don't have access to that mailing list but what I CAN say, is, that my affected system doesn't run radeon or nouveau driver but amdgpu."
1827967,2020-02-04 04:23:59 UTC,"@richy80,"
1827967,2019-11-10 07:30:44 UTC,"Rolando,"
1827967,2019-05-16 15:03:54 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1827967,2019-06-09 16:55:00 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1827967,2019-06-04 09:18:39 UTC,This bug was fixed in the package linux - 4.18.0-21.22
1827967,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1827967,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1827967,2019-05-20 14:01:56 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1827967,2019-05-17 09:31:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1827967,2019-05-07 02:30:21 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827967,2019-11-09 02:41:44 UTC,"The submitted fix causes many users to have no HDMI sound at all, because they are not able to select their sound device. See the corresponding bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771"
1827972,2019-06-09 16:55:00 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1827972,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1827972,2019-05-17 09:31:38 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1827972,2019-05-16 15:03:40 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1827972,2019-05-07 03:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1827972,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1827973,2019-05-15 09:47:06 UTC,"The neutron behavior is intentional. See https://opendev.org/openstack/neutron/commit/54c05b500ac3ffad98cb480dc5bfd04bdcf91229 for more detail reason.
Horizon behavior does not match what neutron expects.
If you add second IPv6 subnet to a router interface, you need to call router-interface-add with the subnet."
1827973,2019-05-15 09:47:38 UTC,I am not sure what the current assignee wangfaxin is thinking as a fix.
1827973,2019-09-13 15:50:43 UTC,"Abhinay, what are you thinking to fix?"
1827973,2019-09-23 11:38:47 UTC,"Hi Akhirio,
Tried to reproduce the issue by adding  ipv6 subnets to the router-interface and as you mentioned horizon was not provided with clear message and doesn't relate to horizon and it is normal behaviour of neutron but In L2 level we can assign a single port to multiple interfaces, so this issue should be invalid"
1827975,2019-09-08 22:32:27 UTC,"dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  man-db -> menu
 packages' pending triggers which are or may be unresolvable:
  man-db: /usr/share/man
  systemd: /etc/init.d
  doc-base: /usr/share/doc-base
  menu: /usr/share/menu"
1827979,2020-10-09 22:13:41 UTC,Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64
1827979,2020-04-22 05:53:39 UTC,"Found on Oracle Bionic 5.3
5.3.0-1015.16~18.04.1
with VM.Standard2.16"
1827979,2021-02-18 04:12:52 UTC,Seen with linux-oracle 4.15.0-1065.73~16.04.1.
1827979,2019-12-02 07:40:07 UTC,In this cycle with B-4.15 Oracle (4.15.0-1030.33) test failed with instances DenseIO1.8 and passed on VM.Standard1.4
1827979,2019-11-06 07:22:49 UTC,Passed with B-4.15 Oracle.
1827979,2019-11-28 10:42:57 UTC,"Failed on X-4.15 Oracle. (4.15.0-1030.33~16.04.1-oracle)
* VM.Standard1.4
* VM.DenseIO1.8"
1827979,2020-03-30 08:27:30 UTC,Failed on VM.Standard2.16 / VM.Standard2.1 with 4.15.0-1037.41 Oracle
1827980,2020-10-09 22:11:13 UTC,Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64
1827980,2020-09-28 04:57:37 UTC,"On Oracle B-4.15 (4.15.0-1055.59) it has passed with all 3 instances Standard2.52, Standard2.1 and VM.DenseIO2.8"
1827980,2020-08-10 06:37:56 UTC,"Time out on B-5.4 Oracle 5.4.0-1021.21~18.04.1
VM.DenseIO2.8
VM.Standard2.1"
1827980,2019-05-07 04:25:42 UTC,Failed with 10 minutes timeout setting as well.
1827980,2020-03-30 08:23:28 UTC,"With 4.15.0-1037.41 Oracle
Failed with VM.Standard2.16
Passed with VM.Standard2.1"
1827980,2019-06-03 13:23:09 UTC,Failed on B-4.15 Oracle instance VM.DenseIO2.16 (passed with VM.DenseIO1.8)
1827980,2020-04-22 05:50:23 UTC,"Can be reproduced on B-oracle-5.3
5.3.0-1015.16~18.04.1
Failed with VM.Standard2.16"
1827980,2019-12-02 07:31:18 UTC,"In this cycle with B-4.15 Oracle (4.15.0-1030.33), it has failed on DenseIO1.8 but passed with VM.Standard1.4"
1827980,2019-11-06 07:31:07 UTC,Passed with Oracle B-4.15 (node VM.DenseIO1.8 / VM.Standard1.4)
1827981,2019-05-07 09:02:01 UTC,"Fixed in revision 2c43d4d6bfce6c7de2d56421cc7a18d13089f5c5
https://git.launchpad.net/kicad/patch/?id=2c43d4d6bfce6c7de2d56421cc7a18d13089f5c5"
1827982,2019-11-06 07:31:33 UTC,Passed with Oracle B-4.15 (node VM.DenseIO1.8 / VM.Standard1.4)
1827982,2019-12-02 07:30:36 UTC,"In this cycle with B-4.15 Oracle (4.15.0-1030.33), it has failed on DenseIO1.8 but passed with VM.Standard1.4"
1827982,2020-03-30 08:22:06 UTC,"With 4.15.0-1037.41 Oracle
Failed with VM.Standard2.16
Passed with VM.Standard2.1"
1827982,2020-04-22 05:18:04 UTC,"Can be reproduced on B-oracle-5.3
5.3.0-1015.16~18.04.1
Failed with VM.Standard2.16"
1827982,2020-08-10 06:35:34 UTC,"Time out on B-5.4 Oracle 5.4.0-1021.21~18.04.1
VM.DenseIO2.8
VM.Standard2.1"
1827982,2020-09-28 04:55:42 UTC,"On Oracle B-4.15 (4.15.0-1055.59) it has passed with all 3 instances Standard2.52, Standard2.1 and VM.DenseIO2.8"
1827982,2020-10-09 22:09:58 UTC,Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64
1827982,2019-06-03 13:23:34 UTC,Failed on B-4.15 Oracle instance VM.DenseIO2.16 (passed with VM.DenseIO1.8)
1827982,2019-05-07 04:25:48 UTC,Failed with 10 minutes timeout setting as well.
1827984,2019-09-27 09:04:01 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1827984,2019-06-18 03:40:57 UTC,This issue was fixed in the openstack/nova 18.2.1 release.
1827984,2019-05-27 18:21:00 UTC,"Reviewed:  https://review.opendev.org/657709
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6310cdd27ce8d5c34e17778bf5fddbce359f26a7
Submitter: Zuul
Branch:    stable/rocky"
1827984,2019-06-06 06:24:02 UTC,This issue was fixed in the openstack/nova 19.0.1 release.
1827984,2019-05-08 00:06:22 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/657708"
1827984,2019-05-07 11:28:42 UTC,"Reviewed:  https://review.opendev.org/657525
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c411febf8b67f93cf16e639aed043f7312f9577
Submitter: Zuul
Branch:    master"
1827984,2019-05-07 04:48:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657525"
1827984,2019-05-08 00:09:24 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/657709"
1827984,2019-05-22 03:31:52 UTC,"Reviewed:  https://review.opendev.org/657708
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d250834734ea04ee202a8fee59abdca79aef8128
Submitter: Zuul
Branch:    stable/stein"
1827985,2019-05-07 11:27:32 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1827986,2019-05-07 08:45:44 UTC,"Thank you for your bug report. Could you give details about the error, like a stacktrace/the exact error message? Do you have the failed installation log?"
1827986,2019-07-07 04:17:17 UTC,[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]
1827987,2019-10-01 09:33:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1827987,2019-11-08 06:34:34 UTC,Thank you!!!
1827988,2019-06-04 03:45:19 UTC,PR for fix: https://github.com/juju/juju/pull/10272
1827989,2019-05-07 08:42:40 UTC,"The screenshot backend is in gnome-shell, the issue is probably there"
1827989,2019-05-07 08:49:31 UTC,Please run:
1827989,2019-07-07 04:17:21 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1827992,2019-09-17 07:34:13 UTC,Migrated to https://github.com/widelands/widelands/issues/3429
1827992,2019-05-12 11:12:12 UTC,Good idea if we can't make the automatic acceleration work. I'd prefer it if the player didn't have to learn an additional key combination though.
1827992,2019-05-10 18:29:21 UTC,Why don't we leave the speed as it is and add a second mode? Pressing SHIFT and the arrow keys could be 2x the speed of normal scrolling.
1827993,2019-06-06 14:19:00 UTC,Re-targeted at the rabbitmq-server charm
1827994,2019-08-20 17:00:49 UTC,This bug was fixed in the package peony - 1.1.6-1
1827995,2019-06-10 20:33:27 UTC,Removing block-proposed. Patviafore confirmed that manual tests are passing.
1827995,2019-06-10 20:39:40 UTC,Tests performed:
1827995,2019-06-10 21:12:19 UTC,This bug was fixed in the package walinuxagent - 2.2.40-0ubuntu1
1827995,2019-06-13 15:30:31 UTC,"Hello Roiy, or anyone else affected,"
1827995,2019-06-13 15:35:48 UTC,"Hello Roiy, or anyone else affected,"
1827995,2019-06-13 15:37:19 UTC,"Hello Roiy, or anyone else affected,"
1827995,2019-06-13 15:39:07 UTC,"Hello Roiy, or anyone else affected,"
1827995,2019-07-18 20:13:21 UTC,"Verification is confirmed to have been done on all releases affected, by the Azure team."
1827995,2019-07-22 08:44:27 UTC,This bug was fixed in the package walinuxagent - 2.2.40-0ubuntu1~19.04.1
1827995,2019-07-22 08:44:32 UTC,"The verification of the Stable Release Update for walinuxagent has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1827995,2019-07-22 08:56:44 UTC,This bug was fixed in the package walinuxagent - 2.2.40-0ubuntu1~18.04.1
1827995,2019-07-22 08:57:01 UTC,This bug was fixed in the package walinuxagent - 2.2.40-0ubuntu1~16.04.1
1827995,2019-06-05 19:54:15 UTC,Adding block-proposed tag to ensure this stays in eoan-proposed while we do the manual testing in cloud instances.
1827998,2019-05-15 11:27:36 UTC,"Hi Viviano,"
1827998,2019-05-17 08:08:28 UTC,"Downloaded the latest driver, scanner still not recognized."
1827998,2019-05-07 11:15:54 UTC,Supported since 3.11.7. Requires a plugin for scanning; is it installed?
1827999,2019-05-07 07:35:49 UTC,May be something similar to this CVE:
1828001,2019-05-07 14:29:08 UTC,So we process .j2 files so you would still use the non-j2 filename even though it doesn't exist.
1828001,2019-05-08 06:12:25 UTC,"Passing a path to a file that doesn't exist ??
OK but seems like a hack."
1828003,2019-05-07 11:30:55 UTC,networking_infoblox needs a patch in neutron/common/utils.py L374:
1828003,2019-05-07 11:43:54 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657578"
1828003,2020-01-14 13:14:18 UTC,"Change abandoned by Marcin Juszkiewicz (<email address hidden>) on branch: master
Review: https://review.opendev.org/657578"
1828003,2020-01-16 09:22:55 UTC,@Marcin is there any particular reason it has abandoned as it is affecting me as well in my python 3 environment.
1828003,2020-01-16 09:36:26 UTC,Kumar: no one bothered merging it == project is not maintained so I abandoned it.
1828004,2019-05-07 09:26:29 UTC,"On Windows 7 with the latest nightly builds I can click the ""Select item"" tool and it works, but Esc doesn't escape from tools."
1828004,2019-05-07 10:11:19 UTC,This is due to the modern toolset transition.  I put in a couple of temporary hacks for now that call the old code when the new code gets these events.
1828004,2019-05-07 11:04:49 UTC,"Fixed in revision f40408187e39381d90faff6dea283004b42e55d4
https://git.launchpad.net/kicad/patch/?id=f40408187e39381d90faff6dea283004b42e55d4"
1828005,2019-05-07 09:45:01 UTC,I can't reproduce the crash.
1828005,2019-05-09 21:19:45 UTC,Does this still happen on latest master?
1828005,2019-05-10 07:59:48 UTC,"When reported happened 4 times in a row. But now i can't make it happen.
Probably is better to close."
1828006,2019-05-07 19:41:52 UTC,"Fixed in revision 2e4d948535e5b875462b8985461d5c814ee2520a
https://git.launchpad.net/kicad/patch/?id=2e4d948535e5b875462b8985461d5c814ee2520a"
1828009,2019-05-07 08:49:11 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/657548"
1828009,2019-05-09 14:38:43 UTC,"Reviewed:  https://review.opendev.org/657548
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_placement/commit/?id=8529d01b2647d4b4398233bff5b9ab6df3739c3f
Submitter: Zuul
Branch:    master"
1828011,2019-05-09 07:52:36 UTC,"If the file is open in the browser (eg html, pdf, txt) then I can save that directly with no problem. (e.g. click one of the .txt files above and then hit Ctrl-S.)"
1828015,2019-05-07 09:55:43 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657562"
1828015,2019-05-07 20:46:01 UTC,Posted this in the PR but as an update to the bug here it is:
1828015,2019-05-15 22:57:25 UTC,https://review.opendev.org/659393
1828015,2019-05-17 09:08:26 UTC,"Reviewed:  https://review.opendev.org/659393
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=a103c15e40612b4c2c801543896bda4bbd5396f0
Submitter: Zuul
Branch:    master"
1828015,2019-05-27 05:57:50 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/661537"
1828015,2019-05-29 07:26:19 UTC,"Reviewed:  https://review.opendev.org/661537
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=84dac3c3626e1f434ccc9a88f8301d8b567bad4f
Submitter: Zuul
Branch:    stable/19.04"
1828015,2020-04-27 09:10:50 UTC,"Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: master
Review: https://review.opendev.org/657562"
1828015,2019-05-07 09:56:14 UTC,Subscribed ~field-medium.
1828017,2019-05-31 20:50:02 UTC,"verified in BUILD_ID=""2019-05-30_16-58-16"""
1828017,2019-05-28 15:49:55 UTC,"Reviewed:  https://review.opendev.org/661645
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=65cca0a22cc039c17d325e91232fe7c4d3cae197
Submitter: Zuul
Branch:    master"
1828017,2019-05-27 18:20:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661645"
1828017,2019-05-21 18:37:06 UTC,"Reviewed:  https://review.opendev.org/659158
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=762fc1b5c9420e1b54e6a80020041b42460e3dfd
Submitter: Zuul
Branch:    master"
1828017,2019-05-27 18:19:40 UTC,Re-opening based on Jeyan's testing. An additional fix is required.
1828017,2019-05-27 18:17:38 UTC,This issue was not resolved in load 2019-05-24 17:41:41 .
1828017,2019-05-14 20:35:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659158"
1828017,2019-05-07 12:54:08 UTC,Marking as release gating given LAG deployments are fairly common for hardware redundancy reasons
1828018,2019-05-15 17:24:26 UTC,TRIAGE:
1828018,2019-05-15 22:57:20 UTC,https://review.opendev.org/659393
1828018,2019-05-17 09:08:28 UTC,"Reviewed:  https://review.opendev.org/659393
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=a103c15e40612b4c2c801543896bda4bbd5396f0
Submitter: Zuul
Branch:    master"
1828018,2019-05-27 05:57:51 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/661537"
1828018,2019-05-29 07:26:20 UTC,"Reviewed:  https://review.opendev.org/661537
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=84dac3c3626e1f434ccc9a88f8301d8b567bad4f
Submitter: Zuul
Branch:    stable/19.04"
1828022,2019-05-07 10:30:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828022,2019-05-07 10:41:59 UTC,"FTR:
$ dpkg -x linux-modules-5.0.0-13-generic_5.0.0-13.14_amd64.deb linux-mods
$ dpkg -x linux-modules-extra-5.0.0-13-generic_5.0.0-13.14_amd64.deb linux-mods-extra
$ find linux-mods -name hio.ko
$ find linux-mods-extra -name hio.ko
linux-mods-extra/lib/modules/5.0.0-13-generic/kernel/ubuntu/hio/hio.ko"
1828023,2019-09-06 21:47:10 UTC,This is fixed in mate-settings-daemon 1.22.0-2 which is part of Ubuntu MATE 19.10.
1828024,2019-05-13 17:29:38 UTC,Launchpad is reporting an improvement; low priority / not gating. Related to ceph.
1828024,2019-07-10 16:26:06 UTC,"Reviewed:  https://review.opendev.org/659820
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=a4759b8e5ba5fee753a41fb03e92d2a8299bbb64
Submitter: Zuul
Branch:    master"
1828025,2019-05-07 19:44:07 UTC,"Inspecting the related Debian package, only in experimental the extension is updated to version 18 (which works on Gnome 3.32): https://packages.debian.org/experimental/gnome-shell-extension-multi-monitors"
1828026,2019-05-09 07:35:12 UTC,Can be found on Disco as well.
1828026,2019-05-09 08:00:07 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828029,2019-09-11 09:43:23 UTC,"This error is related with a bug in the cabview files:
TRAINS\TRAINSET\Fs-ETR500FR-45\Cabview\
etr500-30-TA_alias.cvf
etr500-30-TA_alias_rv.cvf
Once both files were fixed, the FDT-FR9734_VR-MI activity started without error."
1828029,2019-05-29 10:44:23 UTC,How to attach log files
1828029,2019-05-08 11:33:54 UTC,Please could you attach the log file for the crash.
1828031,2019-05-07 12:03:33 UTC,"Because this feature will be acessible in Eeschema execution time, where is possible to select the place to paste the schematic:
1) The layout portion can by just placed in a palce out of the border (square area used by the correspondent already place components);
2) The NET and components IDs of Eschema+Pcbnew have to be updated to keep the NET links."
1828031,2019-05-07 12:58:24 UTC,This is non-trivial so most likely wont happen any time soon but it's something that we will implement at some point.
1828031,2019-05-08 22:08:25 UTC,"Yes, just reporting to tag the milestone when convenient."
1828031,2019-05-31 17:28:13 UTC,This could be kind of related to design blocks as suggested in https://bugs.launchpad.net/kicad/+bug/1797683 (iteration 0 only requests schematic support but could be extended to schematic plus pcb and be used kind of hidden to implement copy paste of schematic plus layout)
1828034,2019-05-14 10:20:52 UTC,https://github.com/juju-solutions/layer-tls-client/pull/17
1828035,2019-06-27 06:51:33 UTC,"Since there is a kernel SRU request in progress to include that patch anyway,
( addressed in LP 1832623 '[UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing' - https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832623 )
I suggest to wait until this hits -proposed and is ready for verification - if that is okay for you?!"
1828035,2019-07-24 10:01:36 UTC,"------- Comment From <email address hidden> 2019-07-24 05:52 EDT-------
IBM bugzilla status -> closed, Fix Released by Canonical"
1828035,2019-07-23 08:00:19 UTC,"The 'gcm-aes-s390' patch landed today in bionic's release pocket.
The work was done based on the kernel SRU of LP 1832623, which is now Fix Released.
Hence I mark this ticket as Fix Released as well."
1828035,2019-07-09 08:55:44 UTC,"Thx for testing and confirming - this kernel (4.15.0-55) will soon be rolled out and copied from the proposed to the update pocket, which then will fix this issue - hence changing status to Fix Committed."
1828035,2019-07-09 08:29:36 UTC,"------- Comment From <email address hidden> 2019-07-09 04:27 EDT-------
With the new bionic-proposed kernel (4.15.0-55), the ping errors with GCM are eliminated and things look fine."
1828035,2019-07-05 16:18:12 UTC,According to LP 1832623 (especially https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832623/comments/6) the latest kernel available in bionic-proposed (4.15.0-55) includes the 'gcm-aes-s390' patch and is ready for test.
1828035,2019-06-28 15:19:10 UTC,"A rough outlook is: in ~ less than 2 weeks - it's planned to come with the next proposed kernel.
(If everything runs smoothly with the kernel SRU, but it looks good - there is already one Ack.)"
1828035,2019-06-28 09:10:12 UTC,"------- Comment From <email address hidden> 2019-06-28 05:04 EDT-------
Is there an outlook when this SRU will be available in proposed?"
1828035,2019-06-26 15:10:06 UTC,"------- Comment From <email address hidden> 2019-06-26 11:06 EDT-------
Canonical: any chance to get a test kernel build with the outlined patch applied?"
1828035,2019-05-29 10:59:28 UTC,"------- Comment From <email address hidden> 2019-05-29 06:55 EDT-------
Can you create a file
/etc/modprobe.d/blacklist.conf"
1828035,2019-05-27 08:49:23 UTC,"------- Comment From <email address hidden> 2019-05-27 04:43 EDT-------
Can you kindly give me a command do so? I get the following error when I try:"
1828035,2019-05-24 11:09:38 UTC,"------- Comment From <email address hidden> 2019-05-24 07:01 EDT-------
Does the problem goes away when you unload the  aes_s390 module and also prevent loading it. (maybe use a blacklist statement in modprobe.conf)"
1828035,2019-05-08 13:29:48 UTC,"------- Comment From <email address hidden> 2019-05-08 09:20 EDT-------
A little bit more information:"
1828035,2019-05-08 12:22:42 UTC,"Thanks Tobias for the advise, adding a kernel Task to pull in the kernel team as well (confirmed to stop the bot from asking for logs)."
1828035,2019-05-07 13:33:09 UTC,It's unlikely that this is a strongSwan issue as IPsec is handled by the Linux kernel. It's more likely a kernel bug related to that particular architecture.
1828035,2019-05-07 13:24:20 UTC,"What version of strongswan was used?
Have you been able to reproduce it on Eoan with strongswan 5.7.2?
Have you reported this upstream at https://wiki.strongswan.org/projects/strongswan/issues ?"
1828035,2019-05-07 12:22:18 UTC,Default Comment by Bridge
1828035,2019-06-26 12:19:24 UTC,"------- Comment From <email address hidden> 2019-06-26 08:06 EDT-------
When we remove the aes_s390 module, the GCM works and the error with the ping command is no longer visible."
1828042,2019-09-27 09:03:59 UTC,This issue was fixed in the openstack/nova 20.0.0.0rc1 release candidate.
1828042,2019-05-07 14:52:42 UTC,"Note that there is also an ""os_compute_api:servers:allow_all_filters"" policy rule which allows configuring the policy to allow non-admins to use all query filters, but it is not used for the all_tenants parameter (which has its own policy rules) so it's a bit confusing because a user could have access to os_compute_api:servers:allow_all_filters but not all_tenants. That's likely a separate bug though."
1828042,2019-05-07 18:58:11 UTC,"IMHO, for the comment #2, I don't think we should allow ""all-tenants"" to all users even if ""os_compute_api:servers:allow_all_filters"" is set right ? - since all-tenants is a super powerful filter targeted at all tenants/users ? But then, if we are allowing other restricted filters like host and user and project, then I guess this is valid too. Just that I am not happy about leaking user/tenant securities outside of admin. Anyways let's see what sorrison feels since he wanted ""os_compute_api:servers:allow_all_filters"" in the first place."
1828042,2019-05-07 14:49:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657620"
1828042,2019-05-13 12:48:09 UTC,"Reviewed:  https://review.opendev.org/657620
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=57646dfe7797a286d88918563d5bf9a6d1a7307a
Submitter: Zuul
Branch:    master"
1828043,2019-05-07 15:12:54 UTC,"Tail of tox -e output:
....
DEBUG:runner:2019-05-07 13:04:09 Config specifies num units for subordinate: neutron-openvswitch
DEBUG:runner:2019-05-07 13:09:38 The following units had errors:
DEBUG:runner:   unit: nova-compute/0: machine: 5 agent-state: error details: hook failed: ""config-changed""
DEBUG:runner:2019-05-07 13:09:38 Deployment stopped. run time: 358.56
DEBUG:runner:Traceback (most recent call last):
DEBUG:runner:  File ""/tmp/bundletester-ms0ttD/nova-compute/tests/dev-basic-cosmic-rocky"", line 22, in <module>
DEBUG:runner:    deployment = NovaBasicDeployment(series='cosmic')
DEBUG:runner:  File ""/tmp/bundletester-ms0ttD/nova-compute/tests/basic_deployment.py"", line 63, in __init__
DEBUG:runner:    self._deploy()
DEBUG:runner:  File ""/tmp/.tox/func27-smoke/local/lib/python2.7/site-packages/charmhelpers/contrib/amulet/deployment.py"", line 85, in _deploy
DEBUG:runner:    self.d.setup(timeout=timeout)
DEBUG:runner:  File ""/tmp/.tox/func27-smoke/local/lib/python2.7/site-packages/amulet/deployer.py"", line 714, in setup
DEBUG:runner:    subprocess.check_call(shlex.split(cmd))
DEBUG:runner:  File ""/usr/lib/python2.7/subprocess.py"", line 190, in check_call
DEBUG:runner:    raise CalledProcessError(retcode, cmd)
DEBUG:runner:subprocess.CalledProcessError: Command '['juju-deployer', '-W', '-c', '/tmp/amulet-juju-deployer-_BTSPR/deployer-schema.json', '-e', 'nickv-tenant-serverstack:admin/default', '-t', '5500', 'nickv-tenant-serverstack:admin/default']' returned non-zero exit status 1
DEBUG:runner:Exit Code: 1
DEBUG:bundletester.utils:Updating JUJU_MODEL: ""nickv-tenant-serverstack:admin/default"" -> """"
DEBUG:bundletester.fetchers:git rev-parse HEAD: 4e9bcbc28b9e7dca66c9b22d886ac5c1979eb73e"
1828043,2019-05-07 15:40:40 UTC,Maybe the same issue as: https://bugs.launchpad.net/charm-lxd/+bug/1801349/comments/20
1828043,2019-05-07 23:03:07 UTC,Looks like the root cause is the same. Cane be closed as dup of https://bugs.launchpad.net/charm-lxd/+bug/1801349/
1828045,2019-06-19 19:10:58 UTC,Verified in load 20190617T233000Z
1828045,2019-06-13 15:07:34 UTC,"Reviewed:  https://review.opendev.org/661640
Committed: https://git.openstack.org/cgit/starlingx/ha/commit/?id=8cd6cc65f1bccf2056c11d87ce609b87b1cad484
Submitter: Zuul
Branch:    master"
1828045,2019-05-07 13:54:36 UTC,64 bit Linux could have 7 digit PIDs. sm-dump has 7 characters for pid. Need to increase it to 8.
1828045,2019-05-10 19:04:13 UTC,"Minor display issue. Would be nice to fix, but not gating for any release."
1828049,2021-01-26 05:41:42 UTC,"I can confirm this is happening on Victoria release also, couple more issue"
1828049,2021-02-25 07:56:39 UTC,designate-manage logs the same way designate daemons do (which admittedly is a bit confusing). Check the content of /var/log/designate/designate-manage.log or something similar depending on your installation.
1828051,2019-05-07 15:27:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657628"
1828051,2019-05-23 14:11:58 UTC,"Reviewed:  https://review.opendev.org/657628
Committed: https://git.openstack.org/cgit/jjb/python-jenkins/commit/?id=190fbbb5ad04e97c4450fe7c78afe638b0d9e5e3
Submitter: Zuul
Branch:    master"
1828053,2019-09-19 10:13:58 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1828053,2019-05-12 01:56:35 UTC,"Reviewed:  https://review.opendev.org/657784
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b8a18dc22a8d3b5fa4d5915399feea88d4ceed9f
Submitter: Zuul
Branch:    master"
1828053,2019-05-08 12:19:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657784"
1828053,2019-05-08 12:02:11 UTC,"Hi LIU,"
1828053,2019-05-08 02:23:35 UTC,"Hi Slawek,
Could you please confirm if enable kod 'nf_conntrack_proto_gre' can fix the issue, or not?"
1828053,2019-05-08 12:23:31 UTC,"Ok, I think that docs update should be enough for this but lets check what others will say in review."
1828055,2019-05-07 15:00:05 UTC,How about
1828056,2019-08-07 00:54:38 UTC,"Fix proposed to branch: r/stx.2.0
Review: https://review.opendev.org/674969"
1828056,2020-01-22 15:59:07 UTC,"verified (on lab sm-2)
20200121T000002Z"
1828056,2019-08-12 15:24:33 UTC,"Reviewed:  https://review.opendev.org/674969
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=8009752d4e003bea7966030f446ab1fe52c37be6
Submitter: Zuul
Branch:    r/stx.2.0"
1828056,2019-07-17 14:11:46 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/671304"
1828056,2019-08-06 21:09:15 UTC,"Reviewed:  https://review.opendev.org/671304
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=71db99e824290231126022fe8af5cb7bd66d99dc
Submitter: Zuul
Branch:    master"
1828056,2019-07-11 14:37:09 UTC,will study why this command makes panko-db-init failed
1828056,2019-07-16 13:36:50 UTC,"openstack-helm issue, already submit bug
https://bugs.launchpad.net/openstack-helm/+bug/1836744"
1828056,2019-05-10 19:13:39 UTC,Marking as release gating for now until the dev prime triages the issue and provides a recommendation
1828056,2019-05-10 19:06:40 UTC,"As to the valid range of acceptable values, designers confirmed there is no restrictions."
1828056,2019-07-11 14:36:23 UTC,"I checked on latest image, type in this command, it will apply failed with osh-openstack-panko"
1828056,2019-05-10 18:59:45 UTC,"What's the reason behind using such a large# when updating panko?
event_time_to_live=24828899"
1828056,2019-06-21 12:27:21 UTC,Assigned to Bruce for re-assignment.
1828059,2019-05-29 20:08:58 UTC,Have not seen this issue recently
1828059,2019-05-21 00:41:09 UTC,I took a look at the cinder logs and saw the same failure signature. Can you confirm that you are running latest docker images? The docker images were rebuilt as part of this fix and are required to resolve this.
1828059,2019-05-20 21:22:34 UTC,Issue is still present on CENG Image: 20190519T233000Z
1828059,2019-05-18 10:45:04 UTC,"Merged in the cengn build: 20190517T223724Z
./cgcs-root/stx/git/ceph                          143ed7218158183529f928fd6833b85f760a1863  2019-05-17 18:30:11 -0400   brent-rowsell   <email address hidden>    Update verbose rados & rbd exceptions messages"
1828059,2019-05-17 20:55:57 UTC,"Fixed by pull request:
https://github.com/starlingx-staging/stx-ceph/pull/31"
1828059,2019-05-17 19:33:19 UTC,"From Bob Church:
I observed the following in the new cinder-volume pod logs from Peng:"
1828059,2019-05-17 02:08:11 UTC,"Issue was reproduced on
Lab: WCP_99_103
Load: 2019-05-15_18-01-07"
1828059,2019-05-14 19:05:55 UTC,"The root-cause is the ceph api synchronization issue.
This is a duplicate of https://bugs.launchpad.net/starlingx/+bug/1827521"
1828059,2019-05-10 18:55:43 UTC,Marking as release gating; this is causing stx sanity to fail
1828059,2019-05-10 18:52:23 UTC,Issue is caused by a synchronization issue in ceph-mgr restful plugin. See fix candidate and pull request here:
1828059,2019-05-07 23:19:00 UTC,the same issue is present in 2+2+2 BM
1828059,2019-05-07 16:08:12 UTC,Time frame when the error occured:
1828059,2019-05-16 20:21:44 UTC,"Providing updates to this bug, just in case that is not a duplicated of the other one and we are facing a different issue."
1828059,2019-05-16 20:18:18 UTC,"Re-opening as this issue was reported by Christopher Lemus using CENGN image 20190515T220331Z
More investigation is required."
1828060,2019-05-14 09:33:23 UTC,This was resolved in https://review.opendev.org/#/c/658153/
1828061,2019-05-22 22:17:01 UTC,Setting this to Low / not release gating.
1828061,2019-05-23 07:57:16 UTC,"Hi Peng,
I could run the cmd successfully with latest code. Could you help check the issue again with latest ISO?
Thanks.
[wrsroot@controller-0 ~(keystone_admin)]$ openstack --os-username 'admin' --os-password 'Local.123' --os-project-name admin --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne metric measures aggregation --resource-type=image --metric=image.size --query ""name='cirros'""
+---------------------------+-------------+------------+

| timestamp                 | granularity |      value |


+---------------------------+-------------+------------+

| 2019-05-23T07:45:00+00:00 |       300.0 | 12716032.0 |


+---------------------------+-------------+------------+"
1828061,2019-05-27 00:39:51 UTC,Need reporter check the issue again with latest build.
1828061,2019-05-27 01:20:09 UTC,"CMD is working on
Lab: WCP_99_103
Load: 2019-05-24_17-39-51"
1828061,2019-05-27 01:32:08 UTC,"Thanks Peng for the update.
Close the issue as ""Fix-Released"" since latest build doesn't have the issue."
1828061,2019-05-08 20:50:31 UTC,Appears to be an openstack related issue; assigning to PL to review/triage
1828061,2019-05-22 19:49:42 UTC,"Since Bruce set the priority to Medium, I am adding the stx.2.0 release tag. Non gating bugs must be set to Low priority."
1828063,2019-05-11 14:16:32 UTC,"Fix for prometheus2 is available with charm revision
cs:prometheus2-9"
1828063,2019-05-13 22:17:04 UTC,"We're still working on a hotfix release for etcd, kubernetes-master, kubernetes-worker, and kubernetes-e2e. Currently working through some issues with the release process. Hopefully soon we'll get a build onto the candidate channels; from there it will probably be another day or two of testing before we can release to stable."
1828063,2019-05-15 22:09:10 UTC,Hotfix releases are currently in candidate channels with the following charm revisions:
1828063,2019-05-10 21:48:31 UTC,"For etcd, kubernetes-master, kubernetes-worker, and kubernetes-e2e, we're in the process of getting a hotfix release out to stable. This is a new process for us so it's likely going to take us a few days to work out the kinks, get everything tested, and release it."
1828063,2019-05-23 17:30:39 UTC,Field critical removed
1828063,2019-05-18 16:10:38 UTC,"Fix for graylog is available with charm revision
cs:graylog-29"
1828063,2019-05-23 15:25:31 UTC,Fixes for all affected charms are now released to stable channels.
1828063,2020-03-03 06:15:45 UTC,Still need to have this fixed for Grafana - see https://code.launchpad.net/~graylog-charmers/charm-graylog/+git/graylog-charm/+merge/367201 for an example of the fix.
1828063,2020-03-03 06:26:17 UTC,"Marked grafana as invalid, as the current iteration installs via .deb rather than snap."
1828063,2019-05-17 14:51:47 UTC,Testing of the CDK charms is currently blocked by network issues in our testing infrastructure. We are working with IS to resolve this as quickly as possible.
1828063,2019-05-10 20:08:11 UTC,Fix for kubernetes-e2e is available in edge with charm revision cs:~containers/kubernetes-e2e-650
1828063,2019-05-08 22:30:34 UTC,"PRs for etcd, kubernetes-master, kubernetes-worker:"
1828063,2019-05-10 17:57:09 UTC,"PRs for backports to stable in etcd, kubernetes-master, kubernetes-worker:"
1828063,2019-05-10 19:22:54 UTC,PRs for kubernetes-e2e:
1828063,2019-05-07 17:26:28 UTC,To continue that discussion here...
1828063,2019-05-08 17:06:36 UTC,"Field critical applied, and approved by Vinod."
1828063,2019-05-08 17:07:55 UTC,This is preventing a customer deployment from completing.
1828063,2019-05-08 17:34:39 UTC,One of our old scripts accomplishes this by using juju scp and juju run[1]. Can you do the same as a temporary workaround?
1828063,2019-05-07 16:36:50 UTC,Past discussion: https://github.com/stub42/layer-snap/issues/9
1828063,2019-05-08 20:16:51 UTC,I'm actively working on this now.
1828063,2019-05-09 15:56:50 UTC,PR for vault:
1828063,2019-05-09 16:48:15 UTC,Gerrit code review request for vault:
1828063,2019-05-09 20:55:03 UTC,"Fix is available in edge channels of etcd, kubernetes-master, and kubernetes-worker with the following charm revisions:"
1828063,2019-05-08 17:54:22 UTC,"If i'm reading it correctly, that script is assuming that the machines are already added, and after it installs the core snap, it then deploys the application."
1828066,2019-05-08 14:19:08 UTC,apport information
1828066,2019-05-08 14:19:23 UTC,apport information
1828066,2019-05-08 14:19:21 UTC,apport information
1828066,2019-05-08 14:19:19 UTC,apport information
1828066,2019-05-08 14:19:17 UTC,apport information
1828066,2019-05-08 14:19:16 UTC,apport information
1828066,2019-05-08 14:19:14 UTC,apport information
1828066,2019-05-08 14:19:11 UTC,apport information
1828066,2019-05-08 14:19:09 UTC,apport information
1828066,2019-05-08 14:19:06 UTC,apport information
1828066,2019-05-09 02:30:07 UTC,This change was made by a bot.
1828066,2019-05-08 14:19:00 UTC,apport information
1828066,2019-05-08 14:18:59 UTC,apport information
1828066,2019-05-08 14:18:57 UTC,apport information
1828066,2019-05-08 14:18:55 UTC,apport information
1828066,2019-05-08 14:18:54 UTC,apport information
1828066,2019-05-08 14:18:52 UTC,apport information
1828066,2019-05-08 14:18:50 UTC,apport information
1828066,2019-05-08 14:18:43 UTC,apport information
1828066,2019-05-08 14:18:41 UTC,apport information
1828066,2019-05-08 14:18:39 UTC,apport information
1828066,2019-05-08 14:19:02 UTC,apport information
1828066,2019-05-08 01:59:43 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1828067,2019-05-07 15:22:27 UTC,"As a fun(?) experiment, I have retried this experiment with an earlier nightly build from a few weeks ago as well."
1828067,2019-05-07 15:49:36 UTC,"It appears to be a corrupt D_LIST.  It crashes when it finds a SCH_FIELD whose m_viewPrivData has been freed (or perhaps the upper bytes walked on?).  In any case, the pointer doesn't look right (0x900007ff1f82bdc3 -- what's with the '9' at the top?) and produces a segfault."
1828067,2019-05-09 22:15:32 UTC,Note: This crash happens anytime a non-select tool is active when doing to copy/paste or duplicate.
1828071,2019-05-25 13:52:11 UTC,"I tried to reproduce this by installing a clean copy of 5.1.2 on a VM running Windows 7 x64 with OpenGl support turned off.  I can't reproduce any of the hang/crash scenarios reported here.  I get the ""falling back to software rendering"" dialog, and then everything seems to work fine."
1828071,2019-08-09 04:17:31 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1828072,2019-05-13 19:11:14 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.32
1828072,2019-05-13 19:11:03 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.11.7
1828072,2019-05-13 19:09:58 UTC,"The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828072,2019-05-13 19:09:46 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.16.4
1828072,2019-05-09 23:20:50 UTC,And an upgrade from Bionic to Disco also passed:
1828072,2019-05-09 22:11:57 UTC,I tested this when upgrading from bionic to cosmic and it also passed the test.
1828072,2019-05-09 21:18:55 UTC,I tested this when upgrading from xenial to bionic and this worked well.
1828072,2019-05-08 17:14:44 UTC,"Hello Brian, or anyone else affected,"
1828072,2019-05-08 17:11:39 UTC,"Hello Brian, or anyone else affected,"
1828072,2019-05-08 17:10:14 UTC,"Hello Brian, or anyone else affected,"
1828072,2019-05-07 21:27:12 UTC,This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.3
1828072,2019-05-09 22:40:04 UTC,I tested this with an upgrade from cosmic to disco and it too passed.
1828074,2019-05-09 16:03:02 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1828074,2020-05-05 20:38:20 UTC,Standard support for cosmic has ended as of July 2019
1828076,2019-10-16 13:25:17 UTC,We haven't had this particular usecase recently (i.e. having a ssh-provided machine in a model and deploying a bundle with --map-machines=existing on top).
1828076,2019-10-14 02:08:29 UTC,Is this still happening? What work-arounds are being done?
1828076,2019-05-08 13:57:34 UTC,"I'm seeing this in a similar (but not the same) env. As in the case above, I have machine #0 which is added via ssh before deploying the bundle:"
1828076,2019-05-08 12:07:08 UTC,"According to your initial report, you were using:
 ""0"": {constraints: tags=infra zones=AZ1, series: *series}
  ""1"": {constraints: tags=infra zones=AZ1, series: *series}
  ""2"": {constraints: tags=infra zones=AZ2, series: *series}"
1828076,2019-05-08 12:25:43 UTC,A duplicate created earlier this year: https://bugs.launchpad.net/juju/+bug/1819365
1828076,2019-05-08 09:41:33 UTC,The list of potential machines from MAAS is the following:
1828076,2019-05-08 03:47:37 UTC,"Note that they have a manual machine as machine 0, not a machine recognized
by the provider. (I would guess it does ultimately come from the provider
but we don't have a way to know that as we don't have an instance id)."
1828076,2019-05-08 02:26:59 UTC,There isn't enough information here to do any debugging from the Juju point of view.
1828076,2019-05-08 13:35:09 UTC,"I don't think that is the same bug. 1819365 is because *juju* is adding a
Zone placement automatically to support enforced HA (distribute units to
unique AZ so that singular failures don't take out multiple units).
This bug is that they are requesting an explicit AZ, and it is failing."
1828077,2019-05-09 10:01:39 UTC,https://github.com/CanonicalLtd/maas-docs/pull/1150 is the GitHub PR for this.
1828079,2019-05-09 13:56:31 UTC,"Didn't say the issue wasn't valid, that is why its marked Incomplete and not ""Invalid""."
1828079,2019-05-09 11:25:52 UTC,I have that in the code already [1] but the promise is returned with some machines and then the datastores are added a few seconds later.
1828079,2019-05-09 12:07:37 UTC,"07:46 < blake_r> lilyana: use deleteDisk
07:46 < blake_r> it knows how to delete a datastore"
1828079,2019-05-08 14:22:10 UTC,"You are correct that the websocket handler doesn't return any data, but you can still wait for it to finish on the server-side."
1828079,2019-05-09 12:27:35 UTC,That fixed this bug: https://bugs.launchpad.net/maas/+bug/1828385
1828080,2019-05-07 16:47:20 UTC,@Seth: what is the right reaction to a horizontal scrollwheel? Horizontal pan?
1828080,2019-05-07 16:58:45 UTC,@Seth is right. The original fix invalidated some horizontal scrolling. I attached a new patch that does not mingle with the existing behaviour.
1828080,2019-05-07 16:59:34 UTC,The original patch should be reverted prior to applying the last one. Thank you!
1828080,2019-05-07 17:06:40 UTC,"@John, I'd assume pan but you are right, maybe we keep it off until we have the configure options available to users"
1828080,2019-05-08 10:11:46 UTC,"@Seth, @Adrian, I have pushed the above patch with some minor wording changes and a couple of minor variations. It should now work as before in pan-mode, and should not do anything with horizontal wheel events in zoom-mode."
1828080,2019-05-08 11:09:32 UTC,"Hi @John, looks good to me! I also had a chance to test the newest build and everything works OK for me. Thank you!"
1828080,2019-05-08 12:52:40 UTC,Good call John!  Looks good.
1828080,2019-05-07 16:28:37 UTC,"I would prefer that we handle the horizontal scroll events correctly rather than skipping them.  Skipping while a mouse button is depressed probably makes sense, however."
1828080,2019-05-07 16:36:36 UTC,"Fixed in revision e10c01aaff11d414386ce2886c9361211459d856
https://git.launchpad.net/kicad/patch/?id=e10c01aaff11d414386ce2886c9361211459d856"
1828082,2020-04-10 15:00:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828084,2019-10-03 07:12:45 UTC,https://kernel.ubuntu.com/git/ubuntu/ubuntu-eoan.git/commit/?h=master&id=e46b94d228458aefc2553ee7c34ab18c2e3288e3
1828084,2019-10-03 07:12:38 UTC,"Could be found in Eoan as well, closing this one with Fix-released."
1828084,2019-07-24 20:29:02 UTC,This bug was fixed in the package linux - 4.4.0-157.185
1828084,2019-07-23 05:25:24 UTC,This bug was fixed in the package linux - 5.0.0-21.22
1828084,2019-07-22 10:53:34 UTC,This bug was fixed in the package linux - 4.15.0-55.60
1828084,2019-07-03 13:06:21 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1828084,2019-07-03 13:02:55 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'."
1828084,2019-06-28 06:45:48 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-June/101708.html
1828084,2019-06-25 12:50:00 UTC,"amd64 counts as x86 for the purposes of supported architectures in Linux, and x86 does have the C version of recordmcount. Comment #3 includes a list of architectures that lack the C version of recordmcount. Of those architectures, ppc64le is the only one that is supported by the NVIDIA driver (the test case described in the reproduction steps). I did try to create a reproduction case independent of the NVIDIA driver, but was unsuccessful, as simpler kernel modules failed to cause a panic, and I hadn't isolated what specific behavior of the NVIDIA driver is problematic when recordmcount fails to run."
1828084,2019-06-25 06:01:04 UTC,Does this only happen on ppc64le?
1828084,2019-05-20 13:49:58 UTC,"Yes, that's the one. The kbuild maintainer modified the commit message to add a maintainer Signed-off-by line."
1828084,2019-05-20 04:40:21 UTC,Is it upstream commit e46b94d228458aefc2553ee7c34ab18c2e3288e3?
1828084,2019-05-07 17:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828084,2019-07-03 11:05:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'."
1828084,2019-07-03 11:02:25 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1828085,2019-05-07 17:43:35 UTC,Review related https://review.opendev.org/#/c/657649/
1828085,2019-05-17 09:11:53 UTC,"Reviewed:  https://review.opendev.org/657649
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=d491a10a81ce9aa228cab22927565a95a5123a45
Submitter: Zuul
Branch:    master"
1828085,2019-05-29 15:06:35 UTC,"Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/662014"
1828085,2019-05-30 08:33:55 UTC,"Reviewed:  https://review.opendev.org/662014
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=01ba0270fd2939f86c8fce73fe1e9521f90e0a01
Submitter: Zuul
Branch:    stable/19.04"
1828087,2019-09-20 12:33:01 UTC,Hello.
1828090,2019-09-25 13:05:50 UTC,I don't have gksu on Ubuntu 19.04 anymore but it feels like this is related to the way those programs handle environment. I've triaged the bug as low as it is not often the case that desktop snaps need to run as root and sudo itself seems to work for you.
1828091,2019-08-11 10:23:14 UTC,Finally checked it against xfce and got it fixed. Thanks for the reports! Please let me know if the fix works for you.
1828091,2019-08-11 17:46:21 UTC,"That does fix it, thanks =D"
1828091,2019-08-10 18:33:45 UTC,"Let me check, I don't have a xfce installed right now."
1828091,2019-08-10 18:17:53 UTC,"But it works as expected in stterm (/usr/bin/st) with xfce – there I can do `sleep 5;printf '\a'`, minimize, and see it blink, then when I raise and minimize again it stops blinking."
1828091,2019-08-10 15:00:25 UTC,"Hi. Sakura doesn't do any blinking. It just sets the urgency hint, and is the window manager (xfce in this case) which decides what to do when a window has the urgency hint."
1828091,2019-08-10 18:40:07 UTC,"Hm, by running `xprop -spy` on stterm, it seems st unsets the urgency bit when raised. https://tronche.com/gui/x/icccm/sec-4.html#WM_HINTS says ""Clients must provide some means by which the user can cause the UrgencyHint flag to be set to zero or the window to be withdrawn."" but from how I read it it doesn't seem like it's the WM's job to turn turn it off."
1828091,2019-05-07 16:54:09 UTC,(This is Version: 3.6.0-3 on Xubuntu 18.10)
1828092,2019-05-07 17:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828092,2019-05-17 09:31:43 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'."
1828092,2019-05-17 18:50:13 UTC,disco verification:
1828092,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1828097,2019-06-19 19:08:27 UTC,Verified in load 20190617T233000Z . This issue is resolved.
1828097,2019-06-10 18:07:24 UTC,"Reviewed:  https://review.opendev.org/664274
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=92b4517165dee160d7c45abffbe5ea7505f2266a
Submitter: Zuul
Branch:    master"
1828097,2019-06-10 15:36:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/664274"
1828097,2019-05-08 20:35:07 UTC,Marking as release gating; stuck alarm condition. Needs further investigation.
1828097,2019-05-08 14:59:04 UTC,The issue still appears related to an attempt to change the controllerfs while there was a 100.104 critical alarm. In this case the cli command to modify the controllerfs was accepted.
1828098,2019-05-07 18:22:24 UTC,"install-deps will force python_cmd to be python_2 unless it's set.
We need to set USER_PYTHON_OVERRIDE for rhel-8 to be python-3."
1828098,2020-02-11 12:56:42 UTC,This is fixed through other patches
1828099,2019-06-03 13:00:20 UTC,Accepted to universe.
1828103,2019-06-03 12:21:42 UTC,this is fixed
1828103,2019-05-27 12:54:07 UTC,"rlandy,  https://bugs.launchpad.net/tripleo/+bug/1812324 is fixed, do we still need this bug ?"
1828104,2019-08-20 13:28:12 UTC,This is done - see rhel 8 work
1828107,2020-11-24 22:59:51 UTC,"Getting frustrated because a bug that has existed so long and is key to network security (connection with SMB1), and has gone ignored for over 1.5 years, is not bad conduct. SMB1 was disabled because of it's egregious security issues, and having no solution for things like this as a result is unacceptable."
1828107,2020-10-26 14:26:57 UTC,"Ignore the comment about the duplicate status, https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 is about a request to implement a new protocol which is what is needed, updating the reference so the status is correct"
1828107,2020-10-26 14:38:08 UTC,"The issue went away for me in 19.10 not long after I saw reports that a fix was released. And same system, the issue came back when I upgraded to 20.04."
1828107,2020-11-24 20:58:16 UTC,"I AM STILL GETTING THIS ISSUE TO THIS DAY. WILL THIS EVER BE FIXED? This issue was reported over 1.5 YEARS ago and a fix was already made, but HAS NOT BEEN RELEASED TO UBUNTU 20.04 WHICH IS THE LONG TERM SUPPORT VERSION. WHEN WILL THIS BE FIXED?"
1828107,2020-11-24 22:44:17 UTC,"To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind."
1828107,2020-11-25 08:47:40 UTC,"The bug isn't ignored but implementing a new protocol is not trivial, also you are commenting on the wrong place, Ubuntu isn't writting that software. Stating that volunteers or companies not doing work for you for free is unacceptable is probably not going to bring you far though..."
1828107,2020-11-25 14:51:22 UTC,"I don't use Windows for serving SMB, I was simply linking the reason for deprecation. FreeNAS, and other non-windows systems serve SMB v2 and higher for network shares, and WSD is not present, relevant, or desired in those configurations. WSD is not the solution, nor replacement, and SMB v2 and v3 have existed for longer than WSD. Yes, netbios was used previously, but clearly after killing the process I can reach them without SMB v1, just not after the first boot."
1828107,2020-11-25 14:09:01 UTC,"Not to put too fine a point on it, but actually that is exactly what this requires. Microsoft phased out the SMBv1 protocol, (NetBios is dead, long live NetBios), in favour of their new protocol: Web Services Dynamic Discovery (WSD).  There has been a lot of discussion and work as to exactly HOW WSD should be implemented for SAMBA and gvfs and what to do in future if Microsoft do another flip of the switch."
1828107,2020-11-25 14:21:04 UTC,"Um, no. Microsoft did not deprecate SMB v1 for WSD, they did it because it has a blatant security flaw in it : https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858"
1828107,2020-11-25 14:27:58 UTC,"> I can browse to my SMB shares just by killing and restarting the gvfsd-smbd process
"
1828107,2020-11-25 14:32:36 UTC,In the very same article you linked: https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by-default-in-windows
1828107,2020-10-26 14:23:36 UTC,"The upstream bug closing seems buggy since they pointed it as a duplicate of https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 and that doesn't make much sense. Unsure also there was anything solved in 19.10, it's just that the situation is confusing and comments don't always speak about the same issue"
1828107,2020-11-25 17:58:07 UTC,"My apologies for sidetracking this far trying to explain differences between discovery and browsing but there seems to be a lot of mixing the 2 as one. The fact that you have ""discovered"" a server you wish to ""browse"" is irrelivant for this bug (afaik you shouldn't have been able to discover it as there are currently no working mechanisms to do so in LTS versions judging from the open bug reports). If however you are experiencing a crash whilst attempting to browse a share of the discovered host, that is relevant and is to do with the way SMB protocol versions themselves are being handled."
1828107,2020-11-25 13:50:01 UTC,"There's no way the solution to this is implementing a new protocol to replace SMB, that would be absurd. The discoverability and connectivity works when the process is terminated and restarted. Clearly this is achievable."
1828107,2020-10-26 14:10:55 UTC,"Oh I dunno, maybe the ""Fix Released"" part? You do realise there is code out there that fixes this that hasn't hit 20.04, right? It was solved in later 19.10, now broken in 20.04."
1828107,2020-11-24 21:07:36 UTC,"I second that!!
This is pathetic."
1828107,2020-10-23 13:48:37 UTC,When is this expected to hit main repos?
1828107,2019-05-07 21:37:12 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828107,2019-05-27 16:41:59 UTC,I too am experiencing this in Ubuntu 19.04.
1828107,2019-06-25 04:27:31 UTC,So... any word on this bug? :S Still getting it.
1828107,2019-06-25 12:41:39 UTC,"Looks like I missed a notification in https://gitlab.gnome.org/GNOME/gvfs/issues/307, I'll followup there"
1828107,2019-11-07 05:14:52 UTC,"So I just upgraded to 19.10 and I am _STILL_ having this issue. I have had this issue now through two whole major releases! SMB1 being turned off _SHOULD NOT BREAK THIS_. SMB1 is a _MAJOR_ security threat, and this really needs to get fixed!"
1828107,2019-11-07 05:16:34 UTC,"And as a reminder, my ""solution"" is to:"
1828107,2020-06-12 13:01:35 UTC,"This will only get better once another discovery service is used, since SMB1 won't come back."
1828107,2020-06-04 22:07:40 UTC,Can we please get this addressed already? This issue persists in 19.10 (haven't tested in 20.04 yet due to unrelated reasons)
1828107,2020-06-26 11:28:03 UTC,"I believe the real issue is that libsmbclient is still using the SMB1/NT1 protocol as the maximum, the issue should be solved upstream since SMB1 is deprecated (disabled by default in newer Samba server versions)."
1828107,2020-06-26 13:15:26 UTC,"Really hope this gets solved soon, have to kill the process after browsing shares every time I reboot."
1828107,2020-09-07 04:05:15 UTC,STILL getting this error in Ubuntu 20.04. Just upgraded to 19.10 and I get this error immediately. How exactly is this not already upstreamed and fixed already??? >:|
1828107,2020-09-28 16:25:00 UTC,Can confirm the bug is still present in Ubuntu 20.04.
1828107,2020-10-15 19:38:45 UTC,This Bug is embarrassing.
1828107,2020-10-16 00:17:30 UTC,"Why has this STILL not been rolled out to 20.04??? It was fixed for 19.10, but still not for 20.04..."
1828107,2020-06-12 16:00:26 UTC,"But once I nicely kill the process, I not only can connect to the share, I can still discover network shares. So, I don't really know how to explain that."
1828107,2020-10-26 09:34:49 UTC,"Which change do you expact to be made availble? The issue there is due to clients not handling the fact that the old unsecure protocal is disabled by default now, that's not coming back though..."
1828108,2019-05-15 14:18:56 UTC,Installing ubuntu-settings 19.04.3.1 the correct font is listed/displayed
1828108,2019-05-15 23:28:23 UTC,"The verification of the Stable Release Update for ubuntu-settings has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828108,2019-05-15 23:28:17 UTC,This bug was fixed in the package ubuntu-settings - 19.04.3.1
1828108,2019-05-10 10:58:39 UTC,This bug was fixed in the package gnome-flashback - 3.32.0-1ubuntu2
1828108,2019-05-08 21:38:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828108,2019-05-08 18:16:39 UTC,"Hello Sebastien, or anyone else affected,"
1828108,2019-05-07 21:27:10 UTC,This bug was fixed in the package ubuntu-settings - 19.04.4
1828108,2019-05-08 21:40:01 UTC,"This also affects gnome-flashback, when you use that session ""Cantarell 11"" is the default document font instead of Sans 11."
1828112,2019-08-22 02:45:08 UTC,"I think in here have a problem.. because i was try make a server with a profile like this above profile in last month. And, i was saw server created with security group."
1828112,2019-08-22 17:45:34 UTC,"@Bo Tran, can you explain what you mean by this:"
1828112,2019-08-23 03:56:48 UTC,"Nope, that is my wrong remember. But, current i was resolved this problem by:"
1828112,2020-05-04 19:21:05 UTC,I am having an issue with security groups as well.
1828113,2019-09-27 09:04:17 UTC,This issue was fixed in the openstack/cinder 15.0.0.0rc1 release candidate.
1828113,2019-05-09 13:29:52 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658077"
1828113,2019-05-30 17:48:22 UTC,"Reviewed:  https://review.opendev.org/658077
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=c549325bd2d9df21af46c2703a55a0ff97f5bfcc
Submitter: Zuul
Branch:    master"
1828114,2019-05-07 21:55:30 UTC,"I apologize, that patch has a mistake. This should be correct."
1828117,2019-05-08 03:55:59 UTC,"According to Rick interactive works if you supply --local, but we probably
want it to always work."
1828118,2019-05-14 09:04:24 UTC,This bug was fixed in the package livecd-rootfs - 2.578.2
1828118,2019-05-14 09:04:13 UTC,This bug was fixed in the package livecd-rootfs - 2.542.3
1828118,2019-05-14 09:03:59 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828118,2019-05-10 20:47:45 UTC,"Well ok but those are currently deleted downstream anyway by
https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh#L91.
Do you want to submit a patch there and then we can patch it here too? In
the mean time I still would like to release this change."
1828118,2019-05-10 07:21:50 UTC,Namely partial/ is an _apt owned sandbox arena. I think there is some code to restore a missing one and fixup permissions but that's super ugly.
1828118,2019-05-14 09:03:51 UTC,This bug was fixed in the package livecd-rootfs - 2.525.23
1828118,2019-05-09 23:39:11 UTC,"In what follows, the ubuntu-${series}-core-cloudimg-amd64-root.tar.gz tarball is the current tarball from https://partner-images.canonical.com/core/ and livecd.ubuntu-base.rootfs-${series}.tar.gz is a test build I made with -proposed enabled (see build pages at https://launchpad.net/~mwhudson/+livefs/ubuntu/disco/test/+build/165334 https://launchpad.net/~mwhudson/+livefs/ubuntu/cosmic/test/+build/165335 https://launchpad.net/~mwhudson/+livefs/ubuntu/bionic/test/+build/165336):"
1828118,2019-05-10 07:16:05 UTC,"I really do not want you to delete the auxfiles, partial directories and the lock file inside /var/lib/apt/lists, they should still be there."
1828118,2019-05-08 01:13:17 UTC,This bug was fixed in the package livecd-rootfs - 2.581
1828118,2019-05-07 23:39:07 UTC,"Uploads done for all series. Turns out we never backported the change that regressed here to bionic but I uploaded the new version of the fix to bionic UNAPPROVED anyway, it's definitely something we want done there in general."
1828118,2019-05-08 18:10:19 UTC,"Hello Michael, or anyone else affected,"
1828118,2019-05-08 22:55:29 UTC,"Hello Michael, or anyone else affected,"
1828118,2019-05-08 18:09:18 UTC,"Hello Michael, or anyone else affected,"
1828119,2019-07-15 03:04:16 UTC,I am unable to recreate this.  Do you still observe the same behavior?
1828119,2019-08-03 20:37:02 UTC,"My apologizes, I didn't see this response earlier."
1828119,2019-08-04 12:09:36 UTC,(5.1.0-1305-gc84c10fa0) is the newer version of the 6.0 development that you were using previously.
1828119,2019-08-04 14:24:37 UTC,"In fact the script is incorrect.
a working script (although not a very good script) is:"
1828122,2020-07-12 11:57:10 UTC,Is this still a problem with current builds?
1828122,2020-08-18 05:26:58 UTC,I'm experiencing this in version 2.2.4 from the Void Linux repos. I'll try compiling from the git tree and see what happens.
1828122,2020-08-18 06:11:20 UTC,I compiled mixxx from commit c0fb398 and this is unfortunately still occurring for me
1828123,2019-05-08 05:39:59 UTC,"Thank you for your bug report. What Ubuntu/nautilus version do you use?
Does ""gio ls dav://:..."" has the same issue or is it specific to nautilus?"
1828123,2019-05-08 09:15:03 UTC,"I'm using nautilus 3.32 on Ubuntu 19.04. ""gio list dav://..."" works perfectly fine, so the issue is specific to nautilus. Please see the following screenshot."
1828123,2019-05-08 11:44:37 UTC,Thank for the version info and the screenshot. It does indeed look like a nautilus bug there and it should be sent upstream to https://gitlab.gnome.org/GNOME/nautilus/issues/ . Do you think you can do that or would you prefer us to handle that part?
1828123,2019-05-08 14:33:36 UTC,I have already opened an issue there. Thank you!
1828123,2019-05-08 15:09:00 UTC,"It would have been useful to mention it and share the reference, I went to look for it now
https://gitlab.gnome.org/GNOME/nautilus/issues/1024"
1828124,2019-05-12 12:09:37 UTC,From a security PoV this is basic security by obscurity and effectively pointless - they are simply XORing each byte with a fixed value and then base64 encoding it - since the source code is public anyone can easily find this out and hence easily decode it - the only way to do this securely would be to have the DBus peers negotiate a session key and encrypt it properly using this - so I don't think there is any point adding this faux-encryption in this case.
1828124,2019-05-10 16:30:43 UTC,"The bug-report on GitLab is now public, they created a patchset for it."
1828124,2019-05-09 13:19:24 UTC,Thanks - I am guessing that bug is private as I can't see it - I just get a 404 - can you please let me know what upstream says?
1828124,2019-05-09 08:48:49 UTC,Done https://gitlab.gnome.org/GNOME/evolution-data-server/issues/113 .
1828124,2019-05-09 04:27:17 UTC,I am not certain this consitutes a security vulnerability however I would be interested to know the upstream developers' opinions - could you please file a bug with the upstream project in this regard? https://gitlab.gnome.org/GNOME/evolution-data-server/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=
1828125,2019-07-27 18:32:39 UTC,"XML-Schema (and its regular expressions) are implemented in libxml2, not in lxml."
1828126,2019-05-07 23:39:11 UTC,"Added Keystone (upstream), however, I am expecting a ""won't fix"" since this is about UUID tokens and it works with fernet."
1828126,2019-05-13 21:14:36 UTC,Queens is still maintained upstream[1] so we would still be happy to accept patches for it as long as we can confirm the behavior.
1828126,2019-05-28 17:32:49 UTC,"Marking this as low priority for keystone, we'd accept a patch if it conforms to the stable branch guidelines but I suspect fixing it may be too big of a change for such an old release."
1828126,2019-05-28 18:39:42 UTC,"Hi Colleen,"
1828127,2019-05-08 00:28:00 UTC,The above bug was run while I had patch 2d52712457ca0e3c759f521ce595c5915a709d88 checked out
1828127,2019-05-11 23:34:02 UTC,The report should be made on the patch itself as it is an issue with functionality currently in development.
1828128,2019-05-07 23:43:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657707"
1828128,2020-06-04 21:46:26 UTC,"Reviewed:  https://review.opendev.org/657707
Committed: https://git.openstack.org/cgit/x/networking-vpp/commit/?id=7fd0598f4de18bbef35742ad4097f1bd3f479c58
Submitter: Zuul
Branch:    master"
1828131,2019-05-25 08:38:53 UTC,Please check whether this patch fixes the issue: [1]
1828131,2019-05-12 20:45:14 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828131,2019-05-12 20:43:41 UTC,I don't think this is nvidia-related. I have the same on Arch with Intel card only.
1828131,2019-05-10 15:14:01 UTC,"Yes, had the same issue on 418."
1828131,2019-05-08 15:04:42 UTC,"1. Installed latest kernel using UKUU, but had the same issue on multiple earlier kernels. I can reproduce on stock."
1828131,2019-05-10 06:53:24 UTC,So I guess we should then file the bug against nvidia-driver-430 then?
1828131,2019-05-09 04:17:46 UTC,I've confirmed qemu works if I select intel instead of nvidia using prime-select.
1828131,2019-05-09 03:41:59 UTC,"After reproducing it a few times, looks like the kernel crash doesn't happen every time, but the nvidia crash does."
1828131,2019-05-08 09:18:57 UTC,"> Uname: Linux 5.1.0-050100-generic x86_64
"
1828131,2019-05-08 12:26:30 UTC,This version number reminds me of https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1/
1828131,2019-05-10 06:55:16 UTC,Since 430 is still from a PPA https://launchpad.net/~graphics-drivers/+archive/ubuntu/ I used 418 being the closest one.
1828133,2019-06-20 06:05:38 UTC,"Hello AceLan, or anyone else affected,"
1828133,2019-06-21 06:12:22 UTC,"Tested on a Lenovo ThinkPad with [8086:2723] Wireless card. After install the linux-firmware(1.173.7) from -proposed, the Wireless card works. tag ""verification-done-bionic"" added."
1828133,2019-06-26 05:28:16 UTC,"Hello AceLan, or anyone else affected,"
1828133,2019-07-03 13:40:30 UTC,"The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828133,2019-07-03 13:40:50 UTC,This bug was fixed in the package linux-firmware - 1.173.8
1828134,2020-04-21 07:58:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828134,2019-07-19 08:24:41 UTC,Reported upstream as
1828134,2019-05-23 10:40:44 UTC,The issue would probably be best reported upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/
1828134,2019-05-23 00:22:52 UTC,"Hello David, any new information on this problem?"
1828134,2019-05-09 01:14:07 UTC,Hi Andrea -- Thanks for the suggestion.
1828134,2019-05-10 02:15:27 UTC,Hi Andrea --
1828134,2019-05-09 06:46:54 UTC,Interesting that the d3cold_allowed change made some differences (I'm assuming it was failing 100% of the times before that change).
1828134,2019-05-08 06:11:12 UTC,Can you try to set the following before suspend:
1828134,2019-05-08 01:21:08 UTC,"Also note, the following sequence seems to avoid the problem so far (4/4 in testing, not conclusive, but it's looking good):"
1828134,2019-05-08 01:00:09 UTC,This change was made by a bot.
1828134,2019-05-10 02:24:18 UTC,Restarting network-manager.service fixes the issue reliably.  I'm going to see if there is more in the log there to determine what is failing.
1828136,2019-05-10 01:07:26 UTC,"I rebooted and went into the ""Ubuntu"" desktop and looked at the sound settings.  It shows an output tab and said ""dummy"".  I clicked and was able to switch it to the nvidia card.  I think maybe the nvidia card was off, which it should be since there's no output device connected."
1828136,2019-05-10 02:50:22 UTC,"I guess you alsa driver works after booing up, but the pulseaudio fails to get your built in sound card via alsa-lib."
1828136,2019-05-10 22:20:19 UTC,"I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the pactl command.  Results was as you predicted.  The pactl outputs before and after appear below."
1828136,2019-05-10 22:21:28 UTC,The before file was attached to the last comment.  Here's the after file from pactl.
1828136,2019-05-11 01:27:01 UTC,"Then edit /etc/pulse/client.conf, change the line ""; extra-arguments = --log-target=syslog"" to ""extra-arguments = -vvvv --log-target=file:/tmp/a.txt""."
1828136,2019-05-11 04:50:39 UTC,I followed the instructions but no log file was created.
1828136,2019-05-11 13:47:40 UTC,"This is something I never met before, this is the content of my /etc/pulse/client.conf, and I can find the /tmp/a.txt after booting up. Maybe this is the root cause of the problem you report, the pulseaudio doesn't start as the 18.10 or 19.04, the pulseaudio still act as the 14.04. Did you upgrade the system from 14.04?"
1828136,2019-05-11 14:07:23 UTC,"I believe that I upgraded incrementally as new releases came out from 14.04. (Hard to recall for sure back that far.)  But definitely I got to 18.10 from 18.04 to 18.04 from 17.10.  And 18.04, I didn't have this problem.  In fact, I have a second machine that I'm ""scared"" to upgrade that's still running 18.04 because I don't want to have this problem on two machines."
1828136,2019-05-11 14:37:12 UTC,there is no client.conf.d/00-disable-autospawn.conf on my computer too.
1828136,2019-05-11 15:33:55 UTC,I removed the 00-disable-autospawn.conf file and rebooted.  Then I get a.txt containing this:
1828136,2019-05-08 02:19:08 UTC,It appears 'audacity' is the exclusive user of /dev/snd/seq according to your AudioDevicesInUse.txt.
1828136,2019-05-12 01:17:03 UTC,"On my machine, this is the log the pulseaudio find the sound card via udev, could you find similar info in your a.txt?"
1828136,2019-05-12 01:29:21 UTC,I already posted the log file a.txt in its entirety.  Here it is again:
1828136,2019-05-12 02:33:49 UTC,E: [autospawn] core-util.c: Home directory not accessible: Permission denied
1828136,2019-05-12 12:35:37 UTC,"From ps I see that ""/usr/bin/pulseaudio --daemonize=no"" is running with user ""adrian"" and also my home directory is owned by ""adrian""."
1828136,2019-05-12 13:23:23 UTC,my system is ubuntu 18.04. And from log ps:
1828136,2019-05-12 13:52:59 UTC,On my ubuntu 18.04 system I only have
1828136,2019-05-13 02:12:07 UTC,User 'gdm' is normal and not a bug. That's the user which runs the login screen.
1828136,2019-05-18 21:40:23 UTC,So is the next step that I should post this to <email address hidden>?  Do I need to be a list member to post there?
1828136,2019-05-19 01:38:36 UTC,"Yes, and it looks like you need to be a list member first."
1828136,2019-06-20 16:00:53 UTC,I finally posted on the pulseaudio list and someone referred me to this bug:
1828136,2019-05-11 16:08:55 UTC,I forgot to mention that dpkg -S says:
1828136,2019-05-11 15:42:47 UTC,"I looked around a bit and found ~/.config/pulse, a directory with permission 700.  Changed it to 777.  That didn't make a difference.  Also found ~/.pulse with this contents:"
1828136,2019-05-10 00:17:29 UTC,"According to the log of ls and aply -l, your audio hardware is recognized by the driver after booting up."
1828136,2019-05-09 12:53:11 UTC,"After booting up, please run:"
1828136,2019-05-08 02:48:56 UTC,"I'm a little confused here.  What does audacity have to do with the fact that there is no sound after a reboot?  Audacity happens to be running now...perhaps that's why it's the only program using ALSA.  (Is ALSA deprecated?)  But audacity does not start automatically at boot, so it is irrelevant to the problem, which is that the sound device is not even recognized until ""alsa force-reload""."
1828136,2019-05-08 03:00:12 UTC,The attached file AudioDevicesInUse.txt suggests that 'audacity' is stealing the hardware device from pulseaudio -- bypassing it.
1828136,2019-05-08 10:06:53 UTC,"I repeat, immediately after a reboot, audacity is not running.  Are you saying that audacity can prevent the system from recognizing my sound hardware at boot just from being installed?"
1828136,2019-05-09 02:21:08 UTC,"Sorry, yes, while that problem is shown in the attached files it does sound irrelevant now."
1828136,2019-05-09 02:22:31 UTC,Added a kernel task because our kernel engineers are experts at such ALSA issues. And often the solution lies in the kernel.
1828136,2019-05-09 02:30:16 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828136,2019-05-09 02:38:57 UTC,apport information
1828136,2019-05-09 02:38:58 UTC,apport information
1828136,2019-05-09 02:39:00 UTC,apport information
1828136,2019-05-09 02:39:01 UTC,apport information
1828136,2019-05-09 02:39:03 UTC,apport information
1828136,2019-05-09 02:39:05 UTC,apport information
1828136,2019-05-09 02:39:06 UTC,apport information
1828136,2019-05-09 02:39:08 UTC,apport information
1828136,2019-05-09 02:39:09 UTC,apport information
1828136,2019-05-09 02:39:11 UTC,apport information
1828136,2019-05-09 02:39:13 UTC,apport information
1828136,2019-05-09 02:39:14 UTC,apport information
1828136,2019-05-09 02:41:04 UTC,"I ran the ""apport-collect 1828136"" command as directed by the automated script.  A little puzzled that it gave the message"
1828136,2019-05-09 02:44:32 UTC,"The automated script said I should change the status to ""confirmed"" even though I am the reporter."
1828136,2019-05-09 02:53:10 UTC,"Yeah, kernel bugs have a slightly different process regarding ""Confirmed""."
1828136,2019-05-10 00:50:04 UTC,"If I look at the sound settings using pavucontrol (I don't normally use gnome and don't seem to have a program called gnome-sound-setting installed) then under the configuration tab I see the nvidia hardware but not the built in audio.  (The nvidia card has only HDMI and my speakers don't have that input, so I can't try using that.  I don't have any devices with HDMI input.)"
1828136,2019-05-09 22:19:01 UTC,Summary: looks to me like aplay -l is showing the intel hardware.  No
1828138,2019-05-08 03:11:21 UTC,PR heading into 2.6.1: https://github.com/juju/juju/pull/10153
1828138,2019-05-14 00:05:38 UTC,PR for 2.7: https://github.com/juju/juju/pull/10175
1828140,2019-05-08 02:06:07 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9977"
1828140,2019-06-19 03:07:51 UTC,"Reviewed:  https://reviews.mahara.org/10106
Committed: https://git.mahara.org/mahara/mahara/commit/cd717b7b2c5c16854a076bad92eeabe3b8a1f40c
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.04_STABLE"
1828140,2019-05-08 03:19:40 UTC,"Commit hash:
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw | Default raw | Ocean | Modern | Primary school"
1828140,2019-06-19 03:07:43 UTC,"Patch for ""19.04_STABLE"" branch: https://reviews.mahara.org/10106"
1828140,2019-06-19 03:07:26 UTC,"Reviewed:  https://reviews.mahara.org/9977
Committed: https://git.mahara.org/mahara/mahara/commit/eeaeb4a202545152d2be74bd089427cff4bbd558
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1828142,2019-07-10 23:16:35 UTC,The expected behavior would be to check all the streams.
1828142,2019-07-10 22:57:43 UTC,Just to confirm the expected behaviour.
1828142,2019-10-31 03:27:24 UTC,Removing from a milestone as this work will not be done in 2.6 series.
1828150,2019-05-08 03:15:17 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9980"
1828150,2019-05-08 21:59:34 UTC,"Commit hash: 1b85e941a5b0529db39349f1114052c016659802
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw | Default raw | Ocean | Modern | Primary school"
1828150,2019-06-19 20:14:59 UTC,"Reviewed:  https://reviews.mahara.org/9980
Committed: https://git.mahara.org/mahara/mahara/commit/c27982479e346e4d454c8029161c588ff5dd3630
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1828150,2019-06-19 20:15:19 UTC,"Patch for ""19.04_STABLE"" branch: https://reviews.mahara.org/10109"
1828150,2019-06-19 20:15:28 UTC,"Reviewed:  https://reviews.mahara.org/10109
Committed: https://git.mahara.org/mahara/mahara/commit/d3af5786deea79f2e7b437f157e256cb9b551759
Submitter: Robert Lyon (<email address hidden>)
Branch:    19.04_STABLE"
1828150,2019-06-19 01:19:23 UTC,Re Test
1828158,2019-05-08 06:46:12 UTC,"This test has passed with Xenial 4.4 kernel.
So this feels like a kernel issue to me."
1828158,2019-05-08 06:46:53 UTC,"Passed on node ""starmie"" (ThunderX) on X:"
1828162,2020-08-26 14:24:12 UTC,"Yep, it mentions that in the marketing doc, but it's not in the doc.  Assigning this to me."
1828165,2019-05-08 07:00:07 UTC,This change was made by a bot.
1828166,2019-10-14 10:23:00 UTC,With the last update (and the patches already in eoan) this ticket can be closed as Fix Released.
1828166,2019-07-17 06:01:34 UTC,"I can also confirm that the issue still exists, but only if I run perf top as root or with sudo.
Running perf top it as regular user is fine - even w/o the patches packages!"
1828166,2019-07-17 15:10:07 UTC,"------- Comment From <email address hidden> 2019-07-17 11:06 EDT-------
How can I get the source code of the kernel tree iand the perf tool?"
1828166,2019-07-17 15:30:33 UTC,"------- Comment From <email address hidden> 2019-07-17 11:24 EDT-------
(In reply to comment #45)

> How can I get the source code of the kernel tree iand the perf tool?
>
> I have tried this command and it did not get the sources:
>
> root@s8360046:~# uname -r
> 4.15.0-55-generic
> root@s8360046:~# apt-get source linux-image-$(uname -r)
> Reading package lists... Done
> E: You must put some 'source' URIs in your sources.list
> root@s8360046:~#
>
> Thanks for your help
"
1828166,2019-07-17 15:51:49 UTC,"Sorry, I missed comment #31, just saw now #32."
1828166,2019-07-17 16:00:08 UTC,And afterwards you can get the package that contains perf like this:
1828166,2019-07-18 07:50:31 UTC,"------- Comment From <email address hidden> 2019-07-18 03:46 EDT-------
I have this /etc/apt/sources.list file with the following deb-src lines"
1828166,2019-07-18 10:29:59 UTC,'apt-get source' should work - just double checked it here:
1828166,2019-07-18 10:45:29 UTC,"Hi Thomas,"
1828166,2019-07-19 11:41:21 UTC,"------- Comment From <email address hidden> 2019-07-19 07:37 EDT-------
Thanks for your help."
1828166,2019-07-22 09:10:16 UTC,"------- Comment From <email address hidden> 2019-07-22 05:04 EDT-------
During execution of command 'perf top' the error message:"
1828166,2019-10-14 11:30:33 UTC,"------- Comment From <email address hidden> 2019-10-14 07:24 EDT-------
IBM Bugzilla status-> closed, Fix Released with Eoan"
1828166,2019-07-22 09:52:27 UTC,"Hi Thomas, thanks for looking into this and doing this analysis.
Sounds reasonable to bring it upstream first and do a backport afterwards.
Since 18.10/cosmic with kernel 4.18 is EOL in between, we just need to get it into bionic 4.15 and disco 5.0 - but I assume you've meant that anyway ..."
1828166,2019-08-13 10:36:17 UTC,"I tried if the two commits can be cleanly applied by cherry-picking them from bionic-master-next (and disco-master-next), and it looks good (with a little hick-up on disco)."
1828166,2019-08-16 16:00:44 UTC,"Hello IBM,"
1828166,2019-08-20 06:50:18 UTC,"------- Comment From <email address hidden> 2019-08-20 02:40 EDT-------
I have installed kernel and perf tool. Now it works ok. I ran the perf top command for nearly 20 Minutes
and generated a good workload. No core dump and OOM messages anymore.
I could not reprodure  the error and I used the same system as before when I debugged the issue."
1828166,2019-08-22 13:10:05 UTC,"------- Comment From <email address hidden> 2019-08-22 09:02 EDT-------
I talked to Thomas Richter and we agreed that his test is covering all aspects. So we can go ahead to bring this into the distros"
1828166,2019-08-22 13:21:04 UTC,"------- Comment From <email address hidden> 2019-08-22 09:10 EDT-------
@Can: Verification done by IBM. Please work on the integration... Many thx in advance"
1828166,2019-08-23 08:46:49 UTC,"Hello IBM,"
1828166,2019-08-23 11:12:32 UTC,These patches have already been committed to Eoan (LP: #1841110).
1828166,2019-08-23 12:09:30 UTC,"SRU request:
https://lists.ubuntu.com/archives/kernel-team/2019-August/103323.html"
1828166,2019-09-04 02:33:58 UTC,Note: The fixes for this problem were applied under a different bug number via stable updates:
1828166,2019-10-14 10:08:00 UTC,"The fixes for Bionic and Disco have been released, as stated on the stable update bugs mentioned on comment #50. Therefore I'm marking this bug report manually as 'Fix Released'."
1828166,2019-08-12 06:20:10 UTC,"------- Comment From <email address hidden> 2019-08-12 02:14 EDT-------
The patches have been picked up by the perf maintainer and are now upstream in the linux kernel v5.3-rc4"
1828166,2019-07-16 15:48:31 UTC,"Hi Klaus,"
1828166,2019-07-17 09:00:09 UTC,"------- Comment From <email address hidden> 2019-07-17 04:49 EDT-------
from LoZ and ZaaS performance point of  view we need perf for root to analyze system behavior"
1828166,2019-07-15 14:59:12 UTC,"Hello IBM,"
1828166,2019-05-08 06:49:24 UTC,Default Comment by Bridge
1828166,2019-05-08 06:53:35 UTC,"Hence, this needs to land in bionic (and cosmic) - disco (and eoan) kernels are already > 4.20"
1828166,2019-05-08 07:59:52 UTC,"------- Comment From <email address hidden> 2019-05-08 03:52 EDT-------
(In reply to comment #11)

> Hence, this needs to land in bionic (and cosmic) - disco (and eoan) kernels
> are already > 4.20
"
1828166,2019-05-08 15:12:12 UTC,"Hello IBM,"
1828166,2019-05-09 07:59:42 UTC,"------- Comment From <email address hidden> 2019-05-09 03:53 EDT-------
Talked to Thomas Richter for a fresh Ubuntu 18.04 where we can test the provided changes, he will provide this image later today (tessia). I can't use the image where I found this issue for this test."
1828166,2019-05-09 13:10:15 UTC,"------- Comment From <email address hidden> 2019-05-09 08:59 EDT-------
ok, I go the image with 18.04 and could recreate the problem.
Then I installed all packages with apt install ./package-name and did a reboot to activate the new kernel.
Questions:
- perf (binary) is no longer available via PATH after package install. Did the package install of linux-tools-common remove perf?"
1828166,2019-05-09 13:31:54 UTC,"Hi, perf should be in package linux-tools-common and each kernel versions has a dedicated linux-tool-common) package version.
$ dpkg -S $(which perf)
linux-tools-common: /usr/bin/perf
But on disk it's usually in /usr/bin."
1828166,2019-05-09 15:06:28 UTC,"Looks like a dedicated linux-tool-common package is needed, because perf too tight to the kernel ..."
1828166,2019-05-09 15:08:26 UTC,"------- Comment From <email address hidden> 2019-05-09 11:05 EDT-------
using perf from package recommended by Frank Heimes results in:
root@m3545035:/home/theurich/people.canonical.com/~ksouza/lp1828166/bionic/tmp/usr/bin# ./perf
WARNING: perf not found for kernel 4.15.0-49"
1828166,2019-05-09 16:19:30 UTC,"@ Klaus: Did you tried the linux-tools-common from klebers link ?
https://people.canonical.com/~ksouza/lp1828166/bionic/
especially:
https://people.canonical.com/~ksouza/lp1828166/bionic/linux-tools-common_4.15.0-49.53+lp1828166_all.deb"
1828166,2019-05-10 07:09:37 UTC,"------- Comment From <email address hidden> 2019-05-10 03:06 EDT-------
sure ... and this package does not have the perf binary included"
1828166,2019-05-13 09:51:37 UTC,"Hello Klaus,"
1828166,2019-05-13 13:06:08 UTC,"Klaus,"
1828166,2019-05-13 15:49:37 UTC,"------- Comment From <email address hidden> 2019-05-13 11:48 EDT-------
thanks, now I got the perf binary back."
1828166,2019-05-14 09:35:00 UTC,"Hi,"
1828166,2019-05-14 12:39:33 UTC,"------- Comment From <email address hidden> 2019-05-14 08:35 EDT-------
I have debugged this issue Klaus reported."
1828166,2019-05-24 11:52:16 UTC,Changed to Incomplete while waiting for new analysis results.
1828166,2019-05-24 12:29:52 UTC,"------- Comment From <email address hidden> 2019-05-24 08:19 EDT-------
I have debugged this issue and created three patches.  Two have been accepted by the perf maintainer
and the third is currently under review.
Once the patches are upstream I will post the commit id's for further processing by Ubuntu."
1828166,2019-06-04 06:59:36 UTC,"------- Comment From <email address hidden> 2019-06-04 02:52 EDT-------
Two patches are  now upstream and available in Linux 5.2-rc3:"
1828166,2019-06-04 07:38:12 UTC,"Thx for the analysis and the sharing of the commit IDs for the two patches from kernel 5.2-rc3 in comment #19.
Since you mentioned three patches in comment #18 I assume the 3rd one became obsolete?"
1828166,2019-06-04 08:19:41 UTC,"------- Comment From <email address hidden> 2019-06-04 04:14 EDT-------

> Since you mentioned three patches in comment #18 I assume the 3rd one became obsolete?


Yes."
1828166,2019-06-04 08:32:37 UTC,Thx for the confirmation
1828166,2019-06-19 13:13:15 UTC,"Just tried to cherry-pick 1) 6738028 and 2) ed9adb2 from 5.3-rc3 to bionic's master-next tree:
git://kernel.ubuntu.com/ubuntu/ubuntu-bionic --branch master-next
1) applied cleanly, but 2) did not - I got 3 conflicts while cherry-picking ed9adb2
Is there something still missing?
(I used bionic to check, because it's the oldest release this should SRUed to, and master-next is needed, because things progress and some patches might already got accepted on top of master, even if not yet released.)"
1828166,2019-06-20 21:29:34 UTC,"Hello Frank,"
1828166,2019-07-05 11:49:40 UTC,"------- Comment From <email address hidden> 2019-07-05 07:48 EDT-------
I have tried to last 2 days to find a patch series to apply the required patch which failed above."
1828166,2019-07-16 13:00:22 UTC,"------- Comment From <email address hidden> 2019-07-16 08:52 EDT-------
ran tests on m3545035. ubuntu 18.02 with latest updates. Recreated the problem first (Not enough memory for annotating '__irf_end' symbol!   and a hang) with perf top and a workload. Installed provided packages, reboot to activate the new kernel:"
1828168,2019-05-20 19:13:32 UTC,"PaulSchulz,  the issue you are reporting is an upstream one. Could you please report this problem following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Amitkumar Karwar, Nishant Sarmukadam, Ganapathi Bhat,  and Xinming Hu CC linux-wireless)?"
1828168,2020-03-15 21:53:46 UTC,Just linking here for future reference. Work on additional support for Surface Pro 3 hardware can be found here: https://github.com/jakeday/linux-surface
1828168,2019-05-09 02:05:01 UTC,"PaulSchulz, thank you for reporting this and helping make Ubuntu better."
1828168,2019-05-08 07:30:08 UTC,This change was made by a bot.
1828168,2019-05-20 13:04:11 UTC,(My apologies for the delay. I needed to turn off SecureBoot to do this testing.)
1828170,2020-02-28 08:15:02 UTC,https://github.com/charmed-kubernetes/layer-etcd/pull/168/files
1828171,2019-06-11 08:09:46 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-12 14:55:16 UTC,"Lukasz, all these packages look fine from the Ubuntu Security Team's perspective. Thanks!"
1828171,2019-06-13 11:53:31 UTC,This bug was fixed in the package binutils - 2.31.1-6ubuntu1.2
1828171,2019-06-13 11:53:42 UTC,This bug was fixed in the package eclipse-titan - 6.3.1-1build4.2
1828171,2019-06-13 11:53:50 UTC,This bug was fixed in the package gcc-7 - 7.4.0-1ubuntu1~18.10.1
1828171,2019-06-11 06:51:58 UTC,"Ah, now I see that, thanks Dimitri! Actually I see Colin did mention 'binary versions', but I didn't really read that properly yesterday night. duh. Anyway, will look into that now."
1828171,2019-06-13 11:53:54 UTC,This bug was fixed in the package gcc-7-cross - 26ubuntu1.2
1828171,2019-06-13 11:54:12 UTC,This bug was fixed in the package gcc-7-cross-ports - 21ubuntu1.2
1828171,2019-06-13 11:54:48 UTC,This bug was fixed in the package gcc-8 - 8.3.0-6ubuntu1~18.10.1
1828171,2019-06-13 11:55:33 UTC,This bug was fixed in the package gcc-8-cross - 21ubuntu1.2
1828171,2019-06-13 11:55:47 UTC,This bug was fixed in the package gcc-8-cross-ports - 12ubuntu1.2
1828171,2019-06-13 11:56:54 UTC,This bug was fixed in the package gcc-defaults - 1.179ubuntu1.2
1828171,2019-06-13 11:58:25 UTC,This bug was fixed in the package eclipse-titan - 6.3.1-1build1.3
1828171,2019-06-13 11:58:29 UTC,This bug was fixed in the package gcc-7 - 7.4.0-1ubuntu1~18.04.1
1828171,2019-06-13 11:58:31 UTC,This bug was fixed in the package gcc-7-cross - 21ubuntu0.3
1828171,2019-06-13 11:59:21 UTC,This bug was fixed in the package gcc-8 - 8.3.0-6ubuntu1~18.04.1
1828171,2019-06-13 11:59:54 UTC,This bug was fixed in the package gcc-8-cross-ports - 9ubuntu0.4
1828171,2019-06-13 12:01:50 UTC,This bug was fixed in the package ggcov - 0.9+20190314-0ubuntu1~18.04.1
1828171,2019-06-13 12:08:19 UTC,This bug was fixed in the package gcc-defaults-ports - 1.178ubuntu1.18.10.1
1828171,2019-06-13 12:08:47 UTC,This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04.2
1828171,2019-06-13 12:09:30 UTC,This bug was fixed in the package gcc-7-cross-ports - 17ubuntu0.3
1828171,2019-06-13 12:10:25 UTC,This bug was fixed in the package gcc-8-cross - 18ubuntu0.4
1828171,2019-06-13 12:11:59 UTC,This bug was fixed in the package gcc-defaults-ports - 1.176ubuntu1.3
1828171,2019-06-13 12:22:01 UTC,This bug was fixed in the package gcc-defaults - 1.176ubuntu2.3
1828171,2019-06-13 11:58:19 UTC,This bug was fixed in the package ggcov - 0.9+20190314-0ubuntu1~18.10.1
1828171,2019-06-10 23:34:47 UTC,"Note one can create .deb packages with arbitrary version numbers not
matching what is listed in debian/changelog.
And this package does that, for Spaß and clarity."
1828171,2019-06-05 16:38:08 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-10 22:13:52 UTC,"I had to remove gcc-defaults-ports from cosmic-proposed: https://launchpad.net/ubuntu/+source/gcc-defaults-ports/1.176ubuntu1.2 and https://launchpad.net/ubuntu/+source/gcc-defaults-ports/1.178ubuntu1.2 have overlapping binary versions in different builds, so these were unpublishable and were causing the publisher to OOPS frequently.  Could you please sort out a non-overlapping version scheme here?"
1828171,2019-06-10 23:04:32 UTC,"Hey Colin! I'm EOD now so I didn't have time to look into it (and am probably too sleepy to look at this sanely) but what do you mean by 'versions overlapping'? 1.176ubuntu1.2 and 1.178ubuntu1.2 seem like different versions (1.176 for bionic and 1.178 for cosmic), and one is smaller than the other. How does the overlap look like?"
1828171,2019-05-20 18:57:58 UTC,"Hi Łukasz, I'll take this for the security team. Thanks."
1828171,2019-06-05 16:23:24 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:24:00 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:25:46 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:26:38 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:27:24 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:28:17 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:28:43 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:29:11 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:29:40 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:30:21 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:31:41 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:33:20 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:33:49 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:34:34 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:35:15 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:35:51 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:36:51 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:37:41 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:38:32 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:38:55 UTC,"Hello Łukasz, or anyone else affected,"
1828171,2019-06-05 16:40:56 UTC,"@sbeattie Hey Steve! I bin-copied all the packages to cosmic-proposed and bionic-proposed. Could you have a quick look at those? Once I see some autopkgtest results for those, with your blessing I'd like to copy those to -updates and -security soon!"
1828171,2019-06-07 08:24:31 UTC,Autopkgtests look good. Updated hints to see installability of all the packages.
1828171,2019-06-10 12:45:00 UTC,"Ok, packages look fine from the releasability POV. Let me double-confirm with security if those are good to go and then perform the copies."
1828171,2019-06-05 16:32:45 UTC,"Hello Łukasz, or anyone else affected,"
1828172,2019-05-09 07:44:42 UTC,"TASK [ansible-role-tripleo-ci-reproducer : Push zuul.yaml to launch job] **********************************************************************************************************************
task path: /tmp/reproduce-tmp.I0LhG/roles/ansible-role-tripleo-ci-reproducer/tasks/launch-job.yaml:20
changed: [localhost] => {""changed"": true, ""cmd"": ""set -e\n#FIXME: for centos7 the git version is too old for the local gerrit\n#       hooks so we get them from upstream\nmkdir -p .git/hooks/\nscp -p -P 29418 -i /home/raukadah/.ssh/id_rsa \\\<email address hidden>:hooks/commit-msg \\\n  .git/hooks/\ngit config --local user.name Admin\ngit config --local user.email <email address hidden>\ngit remote add gerrit ssh://admin@localhost:29418/test1\nif ! git rev-parse --verify master; then\n  git checkout -t origin/master\nfi\ngit add zuul.yaml\ngit commit -m 'Add job to launch\nDepends-On: https://review.opendev.org/657626\n'\ngit push origin HEAD:refs/for/master 2>&1 | tee push.log\ngrep \""remote:.*http\"" push.log | awk '{print $2}' | tee url.txt\nsed \""s/.*\\/\\([0-9]*\\)$/\\1/\"" url.txt| tee review.txt\ngit rev-parse HEAD | tee commit.txt\necho -n $(cat review.txt),1 | tee change.txt\n"", ""delta"": ""0:00:05.347379"", ""end"": ""2019-05-09 13:10:27.192722"", ""rc"": 0, ""start"": ""2019-05-09 13:10:21.845343"", ""stderr"": """", ""stderr_lines"": [], ""stdout"": ""e2dc572a0278552c5781cea1026614f2bf0164e4\n[master 67144d4] Add job to launch Depends-On: https://review.opendev.org/657626\n 1 file changed, 16 insertions(+)\n create mode 100644 zuul.yaml\nremote: \rremote: Processing changes: refs: 1, new: 1\rremote: Processing changes: refs: 1, new: 1\rremote: Processing changes: refs: 1, new: 1\rremote: Processing changes: refs: 1, new: 1, done            \nremote: \nremote: SUCCESS        \nremote: \nremote: New Changes:        \nremote:   http://localhost:8080/c/test1/+/1001 Add job to launch Depends-On: https://review.opendev.org/657626        \nTo ssh://localhost:29418/test1\n * [new branch]      HEAD -> refs/for/master\nhttp://localhost:8080/c/test1/+/1001\n1001\n67144d420d59f6b4e731f40510e1ec07a4e912f8\n1001,1"", ""stdout_lines"": [""e2dc572a0278552c5781cea1026614f2bf0164e4"", ""[master 67144d4] Add job to launch Depends-On: https://review.opendev.org/657626"", "" 1 file changed, 16 insertions(+)"", "" create mode 100644 zuul.yaml"", ""remote: "", ""remote: Processing changes: refs: 1, new: 1"", ""remote: Processing changes: refs: 1, new: 1"", ""remote: Processing changes: refs: 1, new: 1"", ""remote: Processing changes: refs: 1, new: 1, done            "", ""remote: "", ""remote: SUCCESS        "", ""remote: "", ""remote: New Changes:        "", ""remote:   http://localhost:8080/c/test1/+/1001 Add job to launch Depends-On: https://review.opendev.org/657626        "", ""To ssh://localhost:29418/test1"", "" * [new branch]      HEAD -> refs/for/master"", ""http://localhost:8080/c/test1/+/1001"", ""1001"", ""67144d420d59f6b4e731f40510e1ec07a4e912f8"", ""1001,1""]}"
1828172,2019-05-09 07:22:45 UTC,"Set in /etc/ansible/hosts
[subnode-0:vars]
ansible_python_interpreter=/usr/bin/python2"
1828172,2019-05-08 07:51:46 UTC,Related issue: https://github.com/ansible/ansible/issues/54855
1828172,2019-05-08 14:15:46 UTC,Install python3-libvirt python3-lxml and python3-netaddr to avoid python3 import errors
1828172,2019-05-08 14:02:13 UTC,"Reinstall python3-pip then set python_cmd=${USER_PYTHON_OVERRIDE:=python3} then run
bash reproducer-zuul-based-quickstart.sh -e ""ansible_python_interpreter=/usr/bin/python3"" -l"
1828172,2019-05-08 08:28:09 UTC,"on adding with reproducer script -e ""ansible_python_interpreter=/usr/bin/python3"""
1828172,2019-05-08 15:11:35 UTC,"TASK [libvirt/setup/overcloud : Set hostname correctly for subnode-0] *************************************************************************************************************************
task path: /tmp/reproduce-tmp.7EdH4/roles/libvirt/setup/overcloud/tasks/register_vm.yml:37
fatal: [localhost -> 192.168.122.11]: FAILED! => {""changed"": false, ""module_stderr"": ""Shared connection to 192.168.122.11 closed.\r\n"", ""module_stdout"": ""/bin/sh: /usr/bin/python3: No such file or directory\r\n"", ""msg"": ""The module failed to execute correctly, you probably need to set the interpreter.\nSee stdout/stderr for the exact error"", ""rc"": 127}
 to retry, use: --limit @/tmp/reproduce-tmp.7EdH4/launcher-playbook.retry"
1828173,2019-05-08 11:09:52 UTC,"Timo, could you enable CONFIG_RANDOM_TRUST_CPU in linux-oem-osp1? It isn't an SRU cycle blocker but it would be good if the config option was enabled for the next cycle. Thanks!"
1828173,2019-05-16 10:23:22 UTC,https://lists.ubuntu.com/archives/kernel-team/2019-May/100752.html
1828173,2019-05-20 08:24:26 UTC,I'm not sure why the config change didn't make it to debian.oem-osp1..
1828173,2019-09-16 11:47:57 UTC,is fixed in the kernel now
1828176,2019-07-15 04:17:21 UTC,[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.]
1828176,2019-05-15 13:12:32 UTC,"Do you get the issue after a fresh login? Do you have any extensions loaded? Could you add your journalctl log to the bug after getting the issue? It works fine here (tested with gnome-system-monitor for example, which is installed  by default)"
1828176,2019-05-09 07:56:58 UTC,What Ubuntu version are you using?
1828176,2019-05-08 08:23:43 UTC,"did you try several snaps yet, here its working on 18.04?"
1828176,2019-05-08 08:23:37 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1828176,2019-05-15 07:01:38 UTC,I'm using the freshest Ubuntu 19.04 version and update it daily.
1828178,2020-02-24 15:36:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828178,2020-02-24 15:40:05 UTC,"Hello there,"
1828178,2020-03-09 16:12:36 UTC,"Hello,"
1828187,2019-06-24 14:39:42 UTC,"------- Comment From <email address hidden> 2019-06-24 10:37 EDT-------
Verified successfully on cosmic:"
1828187,2019-06-27 11:22:21 UTC,This bug was fixed in the package kexec-tools - 1:2.0.16-1ubuntu1.1
1828187,2019-06-27 10:13:17 UTC,"The verification of the Stable Release Update for kexec-tools has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828187,2019-06-27 10:13:04 UTC,This bug was fixed in the package kexec-tools - 1:2.0.16-1ubuntu3.1
1828187,2019-06-24 14:16:31 UTC,"------- Comment From <email address hidden> 2019-06-24 10:07 EDT-------
Verified successfully on -bionic"
1828187,2019-06-18 18:22:51 UTC,"Hello bugproxy, or anyone else affected,"
1828187,2019-06-18 18:20:41 UTC,"Hello bugproxy, or anyone else affected,"
1828187,2019-05-21 23:48:59 UTC,"Hi Hari,"
1828187,2019-05-22 16:59:53 UTC,".debdiff attached to this comment for sponsorship consideration to Cosmic, adding SRU paperwork to original bug description."
1828187,2019-05-22 11:29:22 UTC,"------- Comment From <email address hidden> 2019-05-22 07:24 EDT-------
Thanks for the taking the fix.
With this change, the device-tree is parsed appropriately.."
1828187,2019-05-22 17:00:20 UTC,.debdiff attached to this comment for sponsorship consideration to Bionic.
1828187,2019-05-22 20:22:37 UTC,"The attachment ""kexec-tools_2.0.16-1ubuntu3.1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1828194,2019-05-08 09:05:01 UTC,Also affects Eoan
1828194,2019-05-16 12:17:23 UTC,"The verification of the Stable Release Update for diaspora-installer has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828194,2019-05-16 12:17:20 UTC,This bug was fixed in the package diaspora-installer - 0.7.6.1ubuntu0.1
1828194,2019-05-16 12:13:23 UTC,"I have looked into that, but found no ""easy"" clou how to resolve this.
It is the same on Eoan btw, so it just generally faily on PPC64 it seems."
1828194,2019-05-09 06:48:05 UTC,Enabled proposed on a fresh Disco VM
1828194,2019-05-08 14:39:43 UTC,"MP approved, uploaded for the SRU Team to consider"
1828194,2019-05-16 08:36:05 UTC,Thank you for preparing and testing the package Christian! The autopkgtests for one architecture seem to be failing though:
1828194,2019-05-08 10:11:48 UTC,"This is Debian native it seems, but versioning works the usual way, all these are good:
# old D->E Upgrade
$ dpkg --compare-versions 0.7.6.1build1 lt-nl 0.7.6.1+debian1
# new upgrade D -> D-updated
$ dpkg --compare-versions 0.7.6.1build1 lt-nl 0.7.6.1ubuntu0.1
# new upgrade D-updated -> E
$ dpkg --compare-versions 0.7.6.1ubuntu0.1 lt-nl 0.7.6.1+debian1"
1828194,2019-05-08 09:46:57 UTC,Yep I think we need https://salsa.debian.org/ruby-team/diaspora-installer/commit/80dc2fd57d30e6fb67ad1734a31887cdf821e534
1828194,2019-05-08 09:42:34 UTC,Installing the version from Eoan 0.7.6.1+debian1 in Disco works.
1828194,2019-05-08 09:36:02 UTC,Differentiating Eoan and Disco which are on the same upstream version but with changes to the bundler also hint to the problem.
1828194,2019-05-08 09:29:12 UTC,"Ha, now things make much more sense and local testing matches more what I see on autopkgtest.
It fails only on Disco and there in regard to the Yard gem."
1828194,2019-05-08 09:12:28 UTC,"Hrm, the test results on autopkgtest suggest that this should be good in all but Disco.
At least in Eoan since diaspora-installer/0.7.6.1+debian which changed the bundler."
1828194,2019-05-08 10:43:19 UTC,"Tests against the PPA worked successfuly.
Pre-verification is complete."
1828194,2019-05-08 22:22:45 UTC,"Hello Christian, or anyone else affected,"
1828195,2019-05-08 09:33:29 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657765"
1828195,2019-05-29 10:47:59 UTC,"Reviewed:  https://review.opendev.org/657765
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=002c163d562f073ffebbdd23ea0682203da510d8
Submitter: Zuul
Branch:    master"
1828195,2019-06-12 14:43:51 UTC,This issue was fixed in the openstack/horizon 16.0.0.0b1 development milestone.
1828197,2020-01-24 09:45:27 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1828200,2019-05-08 19:11:47 UTC,"U-u fix:
https://github.com/mvo5/unattended-upgrades/pull/199"
1828200,2019-07-12 02:04:36 UTC,This bug was fixed in the package unattended-upgrades - 1.13
1828201,2019-05-08 10:58:42 UTC,Thank you for your report. I am unable to recreate this issue. In order to troubleshoot this issue further please provide the steps you used to remove the packages.
1828201,2019-07-08 04:17:21 UTC,[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]
1828203,2019-05-08 13:58:35 UTC,"Sorry, I spoke to Steve and Caleb directly and Caleb fixed the issue."
1828203,2019-05-08 13:44:10 UTC,COuld you please provide:
1828205,2020-04-28 23:57:45 UTC,"Reviewed:  https://review.opendev.org/722657
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=995018d7540bb4fdb47acf42cac554da40a5954c
Submitter: Zuul
Branch:    stable/stein"
1828205,2020-04-24 10:34:32 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/722657"
1828205,2020-04-24 10:33:44 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/722656"
1828205,2020-02-21 16:40:10 UTC,This issue was fixed in the openstack/neutron 16.0.0.0b1 development milestone.
1828205,2020-05-04 02:23:18 UTC,"Reviewed:  https://review.opendev.org/722656
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c945e5ccbadf35d1422828f654a960caf2cd979c
Submitter: Zuul
Branch:    stable/train"
1828205,2020-02-14 18:50:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/707898"
1828205,2020-02-14 18:27:36 UTC,Hello:
1828205,2019-10-14 20:58:15 UTC,"Reviewed:  https://review.opendev.org/687868
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=70f7b3222a9805ac1c58c25572b2e4e62de4d90a
Submitter: Zuul
Branch:    master"
1828205,2019-10-10 11:51:48 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/687868"
1828205,2019-05-08 12:56:02 UTC,"In a fresh devstack with curl I have no project_id in the response:
$ curl -H ""X-Auth-Token: $MY_TOKEN"" -X GET http://127.0.0.1:9696/v2.0/network-segment-ranges/ade20ea9-c2fe-47c7-805d-591f4e147ddc |json_pp
{
   ""network_segment_range"" : {
      ""used"" : {
         ...
      },
      ""default"" : true,
      ""revision_number"" : 0,
      ""tags"" : [],
      ""minimum"" : 200,
      ""physical_network"" : ""physnet1"",
      ""id"" : ""ade20ea9-c2fe-47c7-805d-591f4e147ddc"",
      ""created_at"" : ""2019-05-08T11:56:47Z"",
      ""shared"" : true,
      ""network_type"" : ""vlan"",
      ""available"" : [],
      ""name"" : """",
      ""maximum"" : 400
   }
}"
1828205,2020-02-19 21:07:16 UTC,"Reviewed:  https://review.opendev.org/707898
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3053caaa02adaadfffa53fb1070aaa60f49419e8
Submitter: Zuul
Branch:    master"
1828206,2019-05-08 15:26:36 UTC,There seems to be an issue with the mirror of the Ubuntu archive which you are using - the Release file is missing for at least Cosmic. http://mirrors.nayatel.com/ubuntu//dists/cosmic/ I'd suggest switching mirrors of the Ubuntu archive and trying the upgrade again.
1828206,2019-07-08 04:17:26 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1828207,2019-05-08 13:08:55 UTC,"Note that any use of the built-in VNC-auth scheme is always considered a security flaw. It should essentially never be used, especially not on any public internet facing service, even if fail2ban were able to be used."
1828207,2019-05-08 13:33:00 UTC,"On Wed, 8 May 2019 at 14:23, Daniel Berrange <email address hidden> wrote:

>
> Note that any use of the built-in VNC-auth scheme is always considered a
> security flaw. It should essentially never be used, especially not on
> any public internet facing service, even if fail2ban were able to be
> used.
"
1828207,2019-05-08 13:42:42 UTC,"The challenge is that this is the only auth scheme defined by the VNC protocol, aside from no-auth.
If we removed it, we'd no longer be compatible with the standard VNC protocol. We'd be making use of the TLS/SASL extensions mandatory if users want auth. This could ultimately push people to turn off auth altogether which is even worse."
1828209,2019-05-18 08:55:03 UTC,"could, not should :)"
1828210,2019-05-23 08:27:14 UTC,This bug was fixed in the package libreoffice - 1:6.1.6-0ubuntu0.18.10.2
1828210,2019-05-23 08:27:39 UTC,"The verification of the Stable Release Update for libreoffice has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828210,2019-05-16 17:29:34 UTC,"Upgraded libreoffice from 1:6.1.5-0ubuntu0.18.10.1 to 1:6.1.6-0ubuntu0.18.10.2 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice."
1828210,2019-05-23 08:27:45 UTC,This bug was fixed in the package libreoffice-l10n - 1:6.1.6-0ubuntu0.18.10.2
1828210,2019-05-16 12:10:01 UTC,"Hello Marcus, or anyone else affected,"
1828210,2019-05-11 17:55:03 UTC,Unfortunately the upgrade from 6.1.5 to 6.1.6 is actually broken. My apologies for the false verification. I will prepare a fix asap.
1828210,2019-05-10 09:51:15 UTC,"Upgraded libreoffice to 1:6.1.6-0ubuntu0.18.10.1 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice."
1828210,2019-05-09 15:19:23 UTC,"Hello Marcus, or anyone else affected,"
1828210,2019-05-09 15:18:17 UTC,"Hello Marcus, or anyone else affected,"
1828210,2019-05-16 12:10:43 UTC,"Hello Marcus, or anyone else affected,"
1828212,2019-05-09 08:08:36 UTC,https://github.com/mixxxdj/mixxx/pull/2107
1828212,2019-05-09 07:31:41 UTC,I will check the DownmixAndOverlapHelper (including some refactoring and code style fixes).
1828212,2019-05-09 05:24:01 UTC,"To clarify, the bug is present in commit 1fcbf31c07314edfe1c83b355554182b0fbb300e"
1828212,2019-05-09 05:21:12 UTC,"The multithreaded analysis branch ( https://github.com/mixxxdj/mixxx/pull/1624 ) was merged before the VAMP removal branch ( https://github.com/mixxxdj/mixxx/pull/926 ). The merge commit for the multithreaded analysis branch (b9c9b7f) correctly analyzes these tracks' keys, but the merge commit for the VAMP removal branch (18e9314) does not. I did a git bisect to find which commit introduced the regression, but I could not identify that because none of the commits in the VAMP removal branch build before 1fcbf31c07314edfe1c83b355554182b0fbb300e"
1828212,2019-05-09 07:38:50 UTC,"A simple logging statement gives some insights:
Warning [AnalyzerThread 0 #1]: No key detected in analyzed window: 25"
1828212,2019-05-08 23:09:03 UTC,That is not expected. All tracks that were able to be read and weren't blank filler tracks had a key detected with 2.2.
1828212,2019-05-08 22:55:21 UTC,"For a few track no key is detected, no matter how often or when I analyze them. I think that's expected. The settings of the QM key analyzer may affect this behavior."
1828212,2019-05-08 22:38:43 UTC,"The same tracks are affected when analyzing different databases, so I am doubtful this is because of a race condition."
1828212,2019-05-08 21:08:36 UTC,Unfortunately I'm not able to confirm this. Both the ad-hoc analysis of the PlayerManager as well as the multi-threaded batch analysis reliably detect both bpm and key of all analyzed tracks without exceptions.
1828212,2019-05-08 20:29:04 UTC,"I tried making a new database with 2.2 and analyzing it. All tracks that had a valid detected BPM also had a detected key, so this is a regression in master. Opening the database with analyses done with 2.2 with master works fine, so this is an issue with the analysis in master. I presume it is related to the recent multithreaded analysis changes."
1828212,2019-05-08 23:10:55 UTC,"Enabling the ""Re-analyze keys when settings change or 3rd-party keys are present"" preference option and reloading the affected tracks does not result in their keys being detected."
1828214,2019-05-08 16:42:26 UTC,Related? https://bugs.launchpad.net/kicad/+bug/1827141
1828214,2019-05-08 17:14:16 UTC,"I did some testing and this doesn't affect all fields.  It does not affect the value and reference fields text and the field name text for non-mandatory fields.  I does affect the footprint, datasheet and all non-mandatory field text.  It looks like we need some additional validators added to the field grid table in order to prevent this.  I suspect this also affects the field edit dialog in the symbol editor as well."
1828214,2019-05-13 21:25:52 UTC,"Fixed in revision ae54f34392407cfd9d4628cf3087f07f239cebb2
https://git.launchpad.net/kicad/patch/?id=ae54f34392407cfd9d4628cf3087f07f239cebb2"
1828215,2019-06-13 14:11:18 UTC,Cosmic
1828215,2019-09-30 08:14:58 UTC,This bug was fixed in the package openssl - 1.1.1b-1ubuntu2.4
1828215,2019-06-19 16:47:03 UTC,This bug was fixed in the package openssl - 1.1.1c-1ubuntu2
1828215,2019-06-14 02:05:26 UTC,"The verification of the Stable Release Update for openssl has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828215,2019-06-14 02:05:12 UTC,This bug was fixed in the package openssl - 1.1.1-1ubuntu2.1~18.04.2
1828215,2019-06-13 17:27:10 UTC,I have run bionic-proposed cosmic-proposed and disco-proposed through the usual security team test procedure. They can be released with the fix for CVE-2019-1543.
1828215,2019-06-13 11:37:35 UTC,ACK from the security team on the low CVE being included in this SRU.
1828215,2019-06-13 14:14:16 UTC,Disco:
1828215,2019-06-12 19:35:45 UTC,"Hello Dimitri, or anyone else affected,"
1828215,2019-05-08 12:00:29 UTC,"Hm, the test case is incomplete. As I appear to not be able to use the stock config, and I need a CA generated too. I should get better details for it."
1828215,2019-06-12 18:25:10 UTC,"Run through CA setup, and ended up corrupting my terminal due to binary output using the current bionic-updates 1.1.1-1ubuntu2.1~18.04.1"
1828215,2019-06-12 17:13:01 UTC,"Hello Dimitri, or anyone else affected,"
1828215,2019-06-10 17:37:38 UTC,"reset index.txt, and resigned pkac with upgraded openssl in eoan, the output is pure text and can be read/parsed by humans and machines."
1828215,2019-06-10 17:04:24 UTC,Follow roughly https://blog.felipe-alfaro.com/2005/11/18/setting-up-certificate-authority-ca-using-openssl/ to setup CA
1828215,2019-05-08 13:11:28 UTC,"Here's a recipe for generating a CA directory for testing.
It assumes you have already generated a CA key and cert."
1828215,2019-05-08 12:28:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828215,2019-06-12 19:40:10 UTC,"Hello Dimitri, or anyone else affected,"
1828217,2019-11-13 00:08:20 UTC,This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.7
1828217,2019-09-09 09:28:04 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu3.4
1828217,2019-09-09 09:25:34 UTC,"The verification of the Stable Release Update for landscape-client has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828217,2019-09-09 09:35:28 UTC,This bug was fixed in the package landscape-client - 18.01-0ubuntu7.1
1828217,2019-09-04 23:14:50 UTC,Verified bionic-proposed with the above instructions and it works as expected:
1828217,2019-09-05 19:06:03 UTC,"verified disco-proposed, also as expected:"
1828217,2019-07-09 16:43:20 UTC,"Hello David, or anyone else affected,"
1828217,2019-05-14 22:17:50 UTC,https://github.com/CanonicalLtd/landscape-client/pull/66
1828217,2019-08-13 20:24:50 UTC,"Hello David, or anyone else affected,"
1828217,2019-07-19 18:53:20 UTC,"Hello David, or anyone else affected,"
1828218,2019-05-09 04:13:53 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1828218,2019-05-13 06:48:16 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1828218,2019-07-13 04:17:58 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1828221,2019-05-11 19:30:23 UTC,false alarm. this was caused by the snapcraft-preload script used by that package.
1828222,2019-05-17 23:43:13 UTC,I've implemented better (or maybe just different) hit testing logic.  Let me know if it improves things....
1828222,2019-05-17 11:52:31 UTC,"Fixed in revision eba892009de29284a3482c3cb5945db8e74a3247
https://git.launchpad.net/kicad/patch/?id=eba892009de29284a3482c3cb5945db8e74a3247"
1828222,2019-05-15 16:52:53 UTC,"I think the part about click-mis-hits is due to the code I just put in to make selecting wires easier.  It allows 5 pixels of ""slop"", but I think it needs to keep track of distance and select the closest object."
1828222,2019-05-15 14:24:24 UTC,"1. I'm not even going to ask why highlighting a pin is so important.  If I click on a symbol (as you can see in the video, which I assume you watched) and not on the pin and the symbol is not highlighted - that is a problem.  Especially considering the fact that you can't really see that the pin is being highlighted.  It might work well in theory with bigger symbols, but for symbols which have pins close together (like the capacitor in the video) that creates a problem.  At the very least there should be a disambiguation menu."
1828222,2019-05-15 12:53:09 UTC,"1) Symbol selection: if a pin is highlighted then the pin is selected, not the symbol.  Tool which work on symbols are smart enough to promote the selection to the symbol if needed."
1828222,2019-05-15 12:18:42 UTC,That's funny.  Copying version info still doesn't work if you close KiCad after you copy the info.  Buffer gets emptied.
1828222,2019-05-15 12:12:59 UTC,"Well, its gone from unusable to ...what's worse than unusable?  Sorry for changing the status of the bug report.  Let me know if it is better to start a new one."
1828222,2019-05-10 22:43:49 UTC,"Copy/paste appears to work fine; it's the column selection that's busted.  Because the editor control is open for the first cell, it eats the ctrl-C command and we don't get it.  (If you click below the bottom of the grid the cell editor will close, the highlighting will change, and then you can ctrl-C and get all the cells.)"
1828222,2019-05-10 14:22:23 UTC,"@Art, I didn't mess it up.  I did those just to annoy you. ;)"
1828222,2019-05-10 19:40:15 UTC,"Ok, after living it on its own for a while it came back to life.  Not sure what happened there"
1828222,2019-05-10 19:39:06 UTC,"@Jeff, thanks.  Take it as a kindness... I didn't say you did.  I just said things got messed up."
1828222,2019-05-10 14:04:22 UTC,Forgot to mention one more thing:
1828222,2019-05-10 14:04:19 UTC,Please try Eeschema Preferences > Hotkeys > Set to Defaults. Some hotkeys were changed to align the tools with Pcbnew and this may cause conflicts. I cannot replicate any of the issues you list:
1828222,2019-05-10 13:32:43 UTC,"Dude, talk about getting things messed up!  Yes you fixed one aspect of copy and paste - you can do it now between the sheets, but there are numerous other issues that make it still unusable.  Here is my short albeit not exhaustive list:"
1828222,2019-05-08 18:01:49 UTC,"Yes far I tested, the copy-paste feature just miss to copy the symbol to the library, and now I realize the files to the new folder, reported here lp:1827915."
1828222,2019-05-08 17:02:16 UTC,Nice!
1828222,2019-05-08 15:04:21 UTC,"@Wayne, yes and yes."
1828222,2019-05-08 14:48:17 UTC,"@Jeff, does this include copying hierarchical sheets from the clipboard?  If so, did you run the pasted sheets through the litany of tests that are required to prevent infinite recursion bugs?"
1828222,2019-05-10 20:19:25 UTC,"You're running mostly into wxWidgets errors there.  Their wxGrid works better than the wxDataView we used to use, but it still has issues.  We try to work around them, but it can be pretty difficult.  (We build our own copy of wxWidgets on Mac, so it's easier there.)"
1828223,2019-05-09 09:47:16 UTC,"Hi Dimitri,"
1828223,2020-04-01 21:56:22 UTC,"As Paride mentioned, this is already fixed in Eoan and Focal and was an issue for Disco."
1828223,2020-04-01 21:57:40 UTC,"Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not."
1828226,2019-05-08 20:07:48 UTC,"@Rene As CvPCB has its own window (whose size is variable), and all columns already have variable widths, adding one column doesn't affect its ""multi-screen"" compatibility IMHO. Besides, as mentioned, this new column would be optional."
1828226,2019-05-08 19:47:50 UTC,This would need to work on multi screen setups for all platforms or the preview parts would be good to be detachable.
1828226,2019-05-09 21:41:13 UTC,Footprint and 3d views are already available through a button in the toolbar.
1828227,2019-05-08 13:00:06 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828227,2019-07-08 04:17:25 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1828228,2020-04-07 04:33:00 UTC,This bug was fixed in the package pcs - 0.10.4-3
1828228,2019-07-26 12:11:26 UTC,"This issue is fixed in both, pacemaker and corosync. Other regressions are being investigated at:"
1828228,2019-07-23 11:33:33 UTC,"Pacemaker also depends on corosync, =), and its autopkgtests can't run in armhf if in unprivileged container. Same change we did for corosync has to be done in pacemaker."
1828228,2019-07-22 16:18:59 UTC,"Steve, you are right. I was preparing this comment few mins ago:"
1828228,2019-07-21 20:42:30 UTC,Reopening per my preceding comment
1828228,2019-07-21 07:35:33 UTC,"On Sun, Jul 21, 2019 at 04:24:08AM -0000, Rafael David Tinoco wrote:

> Somehow the lxd containers being used for autopkgtest are, likely,
> different. x64 seems to be running privileged containers for need_root
> tests, while armhf is not (orelse x64 selfpkgtests wouldn't pass either,
> like demonstrated in previous comment).
"
1828228,2019-07-21 04:24:08 UTC,"Somehow the lxd containers being used for autopkgtest are, likely, different. x64 seems to be running privileged containers for need_root tests, while armhf is not (orelse x64 selfpkgtests wouldn't pass either, like demonstrated in previous comment)."
1828228,2019-07-21 04:28:55 UTC,corosync-qdevice autopkgtest is also failing because of the same reason (armhf architecture).
1828228,2019-07-20 21:33:04 UTC,"This ""bug"" happens because of ""unprivileged"" containers:"
1828228,2019-07-16 17:44:51 UTC,"Thanks Robie, and I totally agree. I'll give a fast look in lxd cases and comment back here so we can take a decision."
1828228,2019-07-16 11:59:40 UTC,"Note that if this turns out to be challenging a ""force-badtest"" is likely to be acceptable to get the package migrated for now."
1828228,2019-07-16 11:11:16 UTC,Quick clarifications on next steps:
1828228,2019-07-15 22:40:50 UTC,"Hello Dimitri,"
1828228,2019-07-15 17:41:45 UTC,"I flagged this as high as this is impacting pacemaker migration. After this being fixed, corosync (depending on libknet1 will still block migration, but thas has already been address in MIR https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/1811139)."
1828228,2019-07-08 16:17:27 UTC,I assigned to myself to address comment #1 from Robie and try to bump needed values from the test itself. I'll test in an armhf environment just to make sure its good. This will unblock:
1828228,2019-05-09 11:04:55 UTC,Am I right in thinking that the limits being too low are causing false positives in autopkgtests?
1828228,2019-07-21 04:21:45 UTC,## unprivileged x64:
1828229,2019-05-08 16:21:11 UTC,"Thanks, let's update the tox and pylint! =)"
1828229,2019-05-09 13:59:45 UTC,"This bug is fixed with commit 3bd9b2cb to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=3bd9b2cb"
1828229,2019-05-22 14:21:57 UTC,"This bug is believed to be fixed in curtin in version 19.1. If this is still a problem for you, please make a comment and set the state back to New"
1828230,2019-09-11 01:38:44 UTC,"The verification of the Stable Release Update for golang-google-grpc has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828230,2019-09-11 01:38:35 UTC,This bug was fixed in the package golang-google-grpc - 1.6.0-3ubuntu0.19.04.2
1828230,2019-09-09 11:04:24 UTC,"Hello again, all,"
1828230,2019-07-02 17:31:21 UTC,"Hello Tiit, or anyone else affected,"
1828230,2019-07-02 19:01:04 UTC,"All autopkgtests for the newly accepted golang-google-grpc (1.6.0-3ubuntu0.19.04.2) for disco have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1828230,2019-06-25 16:29:52 UTC,Uploaded to Disco.
1828230,2019-05-16 11:34:31 UTC,"Thank you for the input, Łukasz. I agree and went with the second approach."
1828230,2019-05-14 13:39:49 UTC,"I personally think that the right way to go here is the second approach. I don't think it's wise to downgrade golang-goprotobuf-dev for this reason, as it should be always the other way around (especially that here it seems like it's just 'dropping deprecated functionality')."
1828230,2019-07-02 19:41:00 UTC,The golang-collectd (armhf) autopkgtest seems to have failed due to an unrelated network error:
1828232,2019-05-08 16:30:37 UTC,Bug fixed in X1.3.1-56 by perpetualKid following the suggestion of mbm_OR.
1828233,2019-05-08 17:41:25 UTC,perhaps you can push this along https://review.opendev.org/#/c/651654/
1828236,2019-05-23 13:14:06 UTC,"@Sabrina,
you were right.  when I said ""OpenStack metadata source"", I meant ""DataSourceOpenStack""."
1828236,2019-05-13 19:40:32 UTC,"I'm confused.
From the uploaded .tar.gz:
$ cat run/cloud-init/ds-identify.log
[up 29.06s] ds-identify
policy loaded: mode=search report=false found=first maybe=all notfound=disabled
/etc/cloud/cloud.cfg.d/92_bms_configdrivedisable.cfg set datasource_list: [ NoCloud, OpenStack, Ec2, OpenNebula, Azure, AltCloud, OVF, MAAS, GCE, CloudSigma, CloudStack, None ]
DMI_PRODUCT_NAME=RH2288H V3
DMI_SYS_VENDOR=Huawei
DMI_PRODUCT_SERIAL=2102311GHQ10H6000507
DMI_PRODUCT_UUID=13D686BA-5D98-11E7-BBB8-F87588B6B9D4
PID_1_PRODUCT_NAME=unavailable
DMI_CHASSIS_ASSET_TAG=To be filled by O.E.M.
FS_LABELS=cloudimg-rootfs,config-2
ISO9660_DEVS=/dev/sda2=config-2
KERNEL_CMDLINE=BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=LABEL=cloudimg-rootfs ro console=ttyS0,115200n8 console=tty0 console=tty1 console=ttyS0
VIRT=none
UNAME_KERNEL_NAME=Linux
UNAME_KERNEL_RELEASE=4.15.0-48-generic
UNAME_KERNEL_VERSION=#51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019
UNAME_MACHINE=x86_64
UNAME_NODENAME=sab-u18-ci1805
UNAME_OPERATING_SYSTEM=GNU/Linux
DSNAME=
DSLIST=NoCloud OpenStack Ec2 OpenNebula Azure AltCloud OVF MAAS GCE CloudSigma CloudStack None
MODE=search
ON_FOUND=first
ON_MAYBE=all
ON_NOTFOUND=disabled
pid=725 ppid=706
is_container=false
is_ds_enabled(IBMCloud) = false.
ec2 platform is 'Unknown'.
No ds found [mode=search, notfound=disabled]. Disabled cloud-init [1]
[up 29.09s] returning 1"
1828236,2019-05-16 14:51:38 UTC,"@Sabrina,"
1828236,2019-05-20 12:37:43 UTC,"@Scott,"
1828236,2019-05-14 07:46:34 UTC,"Configdrive works so far.
BMS hosts works a little bit special in OTC as they needs to load datasources two times.
First:  configDrive
Second: openStack"
1828239,2019-06-25 15:10:20 UTC,It happened again.
1828239,2019-05-13 13:33:19 UTC,"Between when I wrote that and today, I was unable to duplicate the bug. There at least two updates after I reported the bug, and before today."
1828239,2021-01-08 04:27:21 UTC,"I now believe this is a known issue, although I do not have a reference. When there is an update, packagekitd may begin downloading the updates to save time. This saves time when the superuser authorizes updates be downloaded and installed. Unfortunately, this doesn't work well for users like me who have low bandwidth service."
1828239,2020-04-24 14:53:58 UTC,Uh ... err ... I don't know what was running for that hour-and-a-half this morning. It wasn't OpenJDK update. The version hasn't changed.
1828239,2020-04-24 14:10:21 UTC,"It happened again today. This time, it appears to be an OpenJDK update."
1828239,2019-05-14 13:24:38 UTC,"This morning, I was notified there were some updates. When Discover opened, I let it sit -- I neither closed it, nor clicked the update button. I did click a couple of the ""..."" icons to see more information."
1828239,2019-11-06 15:24:02 UTC,"This week, I had 9 small updates. I left the Discover update screen on top, and watched without interacting with it. While I watched, the number of updates decreased, one at a time. It went from 9 to 3. I let it sit for at 3 updates before I entered the password to allow the updates to run."
1828239,2019-11-06 16:12:42 UTC,"Just now, I had 5 updates, which included both Firefox and Chromium. It updated both, without waiting for my authorization, and without any indication it was downloading anything. Again, it slowed my use of the Internet."
1828239,2019-07-01 16:03:30 UTC,"It happened again today, but this time it was Thunderbird that was updated without permission. Thunderbird upgraded to version 60.7.2 (64 bit)."
1828239,2019-09-02 16:15:28 UTC,"Another oddity:  This morning, there were 23 (IIRC) updates."
1828242,2019-05-21 13:57:49 UTC,I replicated this in EG 3.3.0 test server (Czech localization - just for completeness).
1828245,2018-12-05 11:19:05 UTC,"Created attachment 8155
Screencast showing the clipping issue with multiple file operations"
1828245,2018-12-05 16:30:26 UTC,Andre Miranda referenced this bugreport in commit 4c0e17d7fc78525007833a10524e88d523123a40
1828245,2018-12-05 16:31:14 UTC,"Fixed, thanks for reporting!"
1828245,2019-05-08 15:57:20 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828245,2019-05-11 07:56:20 UTC,"The Fix is released upstream, but not in Xubuntu 19.04. Have you a date for the fix in downstream ?"
1828245,2019-05-12 11:27:38 UTC,"It will be fixed in 19.10 I guess. This is a minor bug and it probably does not qualify for the ""stable release update"" procedure."
1828245,2019-05-18 14:07:37 UTC,Andre Miranda referenced this bugreport in commit f9c45e09594ce18ad39a80188b64a07c461a8f57
1828245,2019-08-15 13:31:03 UTC,"In Ubuntu 19.10 (in dev.), with Thunar 1.8.9, I confirme the bug is fixed."
1828247,2019-09-11 19:07:48 UTC,"# Testing Status
PASSED
- host-add command is rejected with the expected message if the mgmt MAC is missing or incorrect format"
1828247,2019-08-22 18:39:52 UTC,"Change abandoned by Abraham Arce (<email address hidden>) on branch: r/stx.2.0
Review: https://review.opendev.org/678081
Reason: Regated to stx.3.0."
1828247,2019-08-22 18:27:05 UTC,"Since this issue is only the error message is not clear, this should not be stx.2.0 gating but instead stx.3.0 gating.  Changing the tag to be stx.3.0 gating."
1828247,2019-08-22 18:26:53 UTC,"Reviewed:  https://review.opendev.org/674875
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=46dbbd2cc3963602bb2d73083b403c6c470c6d6c
Submitter: Zuul
Branch:    master"
1828247,2019-08-22 18:16:56 UTC,"Fix proposed to branch: r/stx.2.0
Review: https://review.opendev.org/678081"
1828247,2019-08-06 16:57:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/674875"
1828247,2019-07-17 15:13:17 UTC,Email sent to Yong
1828247,2019-07-08 20:44:09 UTC,"I am taking the ownership of this bug to solve, after a initial review I was able to reproduce, here is my first set of questions to get mode guidance into the right approach to solve it."
1828247,2019-06-21 12:23:57 UTC,Assigned to Bruce for re-assignment.
1828247,2019-05-10 19:55:49 UTC,"Lowering priority based on discussion with David Sullivan. The issue here is the error message is not clear. If the user provides the proper parameters to the add-host cmd, the command passes."
1828247,2019-05-10 18:53:20 UTC,"Marking as release gating; this would prevent the addition of new nodes to the system.
Expect this to be part of typical initial system configuration for multi-node systems. Unclear when this issue started occurring."
1828247,2019-05-08 21:06:20 UTC,Issue is reproducible.  The following AttributeError occurs before sysinv-api performs the validate_and_normalize_mac() which would have raised an exception for the missing MAC address.  The client needs to provide the proper mgmt_mac address for the new host.
1828248,2019-05-14 19:52:13 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49~14.04.1
1828248,2019-05-14 19:09:49 UTC,This bug was fixed in the package linux-azure - 4.15.0-1045.49
1828248,2019-05-14 15:58:30 UTC,"Yes, that is correct.  Comment #6.  Sorry for the typo."
1828248,2019-05-14 15:41:53 UTC,"Morning Joe,"
1828248,2019-05-14 14:40:39 UTC,"@marcelo, we do want the changes requested in comment #5 in bug 1819689.  We can wait for the results of Long Li's investigation before proceeding there."
1828248,2019-05-13 16:45:50 UTC,@longli I would like your assessment of the changes that we've made here to get back to expected performance. I know we are not getting the same results on NVMe devices with 16.04 and 18.04 and I'm wondering if there's something substantially different with the 4.15 kernel in use on 16.04 that prevents us from making the same changes that we did with 4.18 to get better performance.
1828248,2019-05-13 16:15:38 UTC,"This patch was intended to increase performance, not reduce it.  Is it too late to revert it?"
1828248,2019-05-14 14:55:38 UTC,"Thanks for the feedback, @jsalisbury."
1828248,2019-05-13 16:11:10 UTC,"Exactly, Joseph. I'm attaching the exact patch I used for building the test kernel."
1828248,2019-05-13 15:50:47 UTC,"@Marcelo Cerri, just to confirm, the test kernel posted in comment #6 only had commit 7ac257b862f2c  reverted?"
1828248,2019-05-13 14:16:53 UTC,The test kernel is reaching 52K IOPS as expected.
1828248,2019-05-10 13:43:01 UTC,I built a test kernel reverting the commit that Joe has mention:
1828248,2019-05-09 16:43:22 UTC,VM size is Standard_DS14_v2
1828248,2019-05-09 16:31:54 UTC,"Adrian, can you add the VM size here, they are trying to reproduce."
1828248,2019-05-09 15:47:25 UTC,The bug number from comment one should have been bug 1819689
1828248,2019-05-09 15:46:23 UTC,This commit was also added to the Ubuntu-azure-4.18.0-1017 kernel.  Are we seeing expected performing with that kernel?
1828248,2019-05-13 16:14:29 UTC,"Hi, Joe. Do you think the revert is enough for now, or should we discuss about eventyually including the changes that you had mentioned on the comment #5 in the bug #1819689?"
1828248,2019-05-09 15:44:58 UTC,The following commit was added in bug fa55b5d226dd.
1828249,2020-01-24 08:50:52 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1828250,2019-07-05 12:52:13 UTC,This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.
1828250,2019-06-07 19:29:53 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.0.0 release.
1828250,2019-05-14 08:24:56 UTC,"Reviewed:  https://review.opendev.org/658885
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=038d887d845fd4fee7b981383b43346f33e9883f
Submitter: Zuul
Branch:    stable/stein"
1828250,2019-05-13 18:10:16 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/658885"
1828250,2019-05-13 17:59:57 UTC,"Reviewed:  https://review.opendev.org/657838
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=ef6c23ef64ec7d96a45aabb844cf9451c27ae29c
Submitter: Zuul
Branch:    master"
1828250,2019-05-08 15:17:40 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657838"
1828251,2019-05-21 11:51:46 UTC,"I have tried to purge patrons in the web staff client 3.3.0 (test server with Czech localization).
I have successfully purged both, the patrons with expired registration and the patrons with valid registration."
1828254,2019-09-29 19:06:17 UTC,"Change abandoned by Erich Cordoba (<email address hidden>) on branch: master
Review: https://review.opendev.org/666412"
1828254,2019-09-29 19:05:56 UTC,"Change abandoned by Erich Cordoba (<email address hidden>) on branch: master
Review: https://review.opendev.org/658203"
1828254,2019-09-29 19:05:47 UTC,"Change abandoned by Erich Cordoba (<email address hidden>) on branch: master
Review: https://review.opendev.org/657910"
1828254,2019-09-29 19:05:41 UTC,"Change abandoned by Erich Cordoba (<email address hidden>) on branch: master
Review: https://review.opendev.org/657903"
1828254,2019-09-27 19:36:27 UTC,This has been fixed by the recent repo restructuring activity.
1828254,2019-09-10 14:23:50 UTC,"Change abandoned by Bart Wensley (<email address hidden>) on branch: master
Review: https://review.opendev.org/658144
Reason: Abandoning this review since the change was already made under: https://review.opendev.org/#/c/681088/"
1828254,2019-09-06 16:47:12 UTC,"Change abandoned by Bart Wensley (<email address hidden>) on branch: master
Review: https://review.opendev.org/679997
Reason: The recent code restructuring activity fixed the issue so this change is no longer required."
1828254,2019-05-08 23:23:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657903"
1828254,2019-06-20 20:47:03 UTC,"If the build team things this is too risky to change in stx.2.0, then I will accept that. Note that I am not the one who decides which LPs gate release stx.2.0."
1828254,2019-06-20 15:43:44 UTC,The fix is ready but the build team thinks that it's better to integrate this change after release. Is this ok for the reporter fo this bug?
1828254,2019-06-19 17:56:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/666412"
1828254,2019-05-09 20:10:47 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658203"
1828254,2019-05-09 02:52:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657910"
1828254,2019-05-08 20:39:51 UTC,Marking as release gating given this is a developer productivity issue
1828254,2019-05-08 16:07:00 UTC,The long-term fix for this is to remove the need to have hard-coded paths in places like tox.ini to find dependencies.
1828254,2019-06-27 22:39:10 UTC,Changing the release tag to stx.3.0 as per above.
1828255,2020-03-26 03:04:02 UTC,There is configurable prompting for those that want it. We also refuse to delete running containers.
1828256,2019-05-23 15:43:45 UTC,Attaching more logs.  Hope this helps.
1828256,2019-05-23 15:41:16 UTC,Failure in kubernetes-e2e: junit_19.xml
1828256,2019-05-22 11:49:29 UTC,"We'll take a look. In the meantime, please explain why this is Field High. AFAICT, a conformance test failure does not meet the criteria."
1828256,2019-05-15 15:25:42 UTC,I see a similar error in another run:
1828256,2019-05-22 21:17:41 UTC,Here's a link to a test run this failed on.
1828256,2019-05-21 15:06:20 UTC,sub'd to field high
1828257,2019-05-09 09:24:30 UTC,"Windows Vista is no more supported in the latest versions of Open Rails. You must have either Windows 7 SP1, or Windows 8.1, or Windows 10."
1828260,2019-05-17 04:38:41 UTC,I don't see a KiCad issue here.  This is loading a python module that seems to work differently on different systems.
1828260,2019-05-11 01:44:32 UTC,"Yes, could be done with some more programmers (currently is just I). The bigger problem will be the wxPython, I think. Also could have some package not updated anymore to Py2..."
1828260,2019-05-10 08:05:10 UTC,"Is it not possible to make KiCost python 2 and 3 compatible?
Anyway, what error do you get when executing the mentioned commands?"
1828260,2019-05-16 00:51:02 UTC,Should this issue be pumped as LOW priority since it is a different behavior between OSs?
1828260,2019-05-09 21:43:40 UTC,"@Tomasz, I guess Hildo is trying to use a subprocess to call KiCost as a python3 (only) app, even if kicad is compiled with python2 support only."
1828260,2019-05-08 17:05:53 UTC,"For last, the point here is that KiCost install and run in all three-plataform (Mac / Ubuntu / Windows) just by typing `kicost` at terminal, as ""specif software"" as it is. And I can call it like this in Windows Pcbnew Python console, but no in Ubuntu."
1828260,2019-05-08 17:04:11 UTC,"KiCost use several python libraries that are automatically installed when using `pip`. Appear quite complicated to dispose all this files in the '.kicad_plugins' folder (or install in a separated process to a not experient python/terminal user).
Furthermore, nowadays KiCost works with BOM files provide by many EDAs including hand made CSV files. Making it just a action plugin will restring it application.
Least but not last, make it action will force to run as Python2 in some systems and Python3 in others. This will make difficult to code and maintain the package."
1828260,2019-05-08 16:50:09 UTC,Why wouldn't you integrate KiCost as an action plugin? Calling external programs from a plugin is a serious security risk.
1828260,2019-05-08 16:26:35 UTC,"You can install KiCost packege for test by
https://pypi.org/project/kicost/
https://github.com/xesscorp/KiCost/tree/octopart (stable branch)"
1828260,2019-05-09 21:52:54 UTC,"Exactly @Nick, is the best way since KiCost should be OS kind/version independent."
1828261,2019-05-08 17:03:09 UTC,"Hmm... this is a bit of a conundrum.  Junction dots aren't required there, so how do we know whether or not the user wants them?  We could look at other component-to-component junctions, but I'm not sure if that's a good idea or not."
1828261,2019-05-08 17:20:55 UTC,The original intention was that junction dots existed anywhere there were 3 or more endpoints.  There was an added requirement that endpoints could not be placed on a wire without the wire breaking into two segments - Thus creating the needed 3+ for a junction.
1828261,2019-05-08 17:34:59 UTC,"Technically, in the case shown in this report, the junction is useless, from the point of view of connection management."
1828261,2019-05-08 17:49:09 UTC,Seth's 3+ endpoints seems logical to me.  It doesn't delineate between wire and pin endpoints which keeps it simple.  Of course you could always use a brute force option to prevent a junction for users who don't like the junction connecting three pin endpoints.  I personally think that is overkill but then I'm not every user.
1828261,2019-05-08 19:00:39 UTC,I'll go ahead and implement Seth's 3-ends idea and we'll see how it goes over.
1828262,2020-06-27 18:06:30 UTC,LP was closed as invalid a long time ago; removing the stx.retestneeded tag
1828262,2020-05-13 13:30:25 UTC,"Hi, Wendy:
    is this still reproduce , or not, if not reproduce, we should close this issue.
@martin:
   assign to you in case need some follow action."
1828262,2019-11-27 01:38:22 UTC,"Hi TingJie:
    it seems  newly test log was 10/21, which 1827119 has already be merged.
@Wendy :
    would you like confirm your test was based on master or stx.2.0 release ?"
1828262,2019-11-19 05:09:27 UTC,"TingJie:
    would you like shortly update for this issue?"
1828262,2019-10-21 17:10:01 UTC,see puppet.log Errors
1828262,2019-11-26 15:58:21 UTC,"The duplicated LP: 1827119 has fix released with patch: https://review.opendev.org/#/c/677424/ which merged in Sep 23th, 2019.
I have tried with 20191120T023000Z to verify the issue, but cannot reproduce, since set ceph_mon_gib=23 cannot return sucess because the available space in compute-0 have only 1 GB growth."
1828262,2019-08-15 14:07:20 UTC,LP-1827119 was reopened. Waiting on fix for that before retesting.
1828262,2019-10-21 17:02:48 UTC,"BUILD_ID=""2019-10-20_20-00-00"""
1828262,2019-05-08 20:42:37 UTC,Can you please try a re-install without changing ceph parameters?
1828262,2019-05-09 14:17:57 UTC,Reinstall was successful on worker ceph-mon node that did not have any filesystem modifications.  This was observed with build 20190508T013000Z (master).
1828262,2019-10-21 17:56:51 UTC,Re-opening as the re-test failed as per above
1828262,2019-05-16 12:48:24 UTC,Error is:
1828262,2019-05-10 18:46:22 UTC,Marking as release gating; issue appears related to ceph
1828262,2019-05-16 12:52:40 UTC,This issue will be fixed once changes for https://bugs.launchpad.net/starlingx/+bug/1827119 will be implemented as this semantic (i.e. checking available space on computes and storages when doing the resize) is implied as part of solution 2A proposed there.
1828264,2019-05-08 18:00:06 UTC,"Note the fix should be as simple as removing this section of code:
https://opendev.org/starlingx/config/src/commit/9c5bf5771e2431cad11dfdbf3ad64d6671e6fad0/sysinv/sysinv/sysinv/sysinv/api/controllers/v1/host.py#L3382"
1828264,2019-05-08 20:44:18 UTC,Marking as release gating; issue is related to recent code changes for huge page re-work.
1828264,2019-05-14 17:03:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659126"
1828264,2019-05-15 13:59:09 UTC,"Reviewed:  https://review.opendev.org/659126
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=368f730ff109f1c5dd7cfa4da462a0eadb310b1c
Submitter: Zuul
Branch:    master"
1828264,2019-05-27 14:24:48 UTC,"Installed standard lab (2+2), with vswitch ovs-dpdk configuration.
The non openstack worker node appeared to unlock, becomes enabled/available (at least first time after removing the labels)."
1828264,2019-05-27 17:21:50 UTC,That issue does not sound related this bug. I'd recommend filing a new bug for that issue.
1828264,2019-05-27 18:00:47 UTC,"It looks like the original bug here is resolved on standard 2+2 lab.
This separate issue is tracked in 1828264"
1828268,2019-05-24 05:27:18 UTC,"Hi,
sorry for the delay. So, I have tried the approach you described but unfortunately I had the same problem. I understand the Cubic was created having in mind the Ubuntu ISO structure but it would be good to have the possibility to work also with ISO with a different FS format. Do you think you can add it in the future?"
1828268,2019-05-12 03:42:32 UTC,"By the way, you can try this your self. It may work on your system..."
1828268,2019-05-23 22:35:19 UTC,"Alberto,"
1828268,2019-05-12 03:17:49 UTC,"Cubic works with most Ubuntu based distributions.
The structure of the Cubic ISO's looks like..."
1828270,2021-02-23 08:57:17 UTC,"Hi team,"
1828270,2019-05-22 14:12:21 UTC,"Reviewed:  https://review.opendev.org/658823
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=6bd45c96dd05e819d70140f6fe4d27e073b3988a
Submitter: Zuul
Branch:    master"
1828270,2019-05-13 14:08:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658823"
1828270,2021-02-16 14:28:23 UTC,"Hi Team,"
1828271,2019-05-08 18:23:40 UTC,"It's a strange chain of events, we do reset the node to config-out-of-date when an OSD is configured, which is expected. Yet it should be cleared after unlock, but instead we get this:"
1828271,2019-05-08 18:33:33 UTC,That is the reboot required bit:
1828271,2019-05-08 20:46:23 UTC,Marking as release gating; affects system install/commissioning for AIO-SX
1828271,2019-05-10 14:34:03 UTC,"The issue is related to config_target and config_apply limitations not to storage stuff. A config uuid with the reboot flag is passed to puppet ONLY when host is unlocked (which makes sense as this is when we do the reboot). Runtime manifests don't pass the reboot flag to puppet (it is a runtime, reboot flag has to remain). So, at unlock we set it correctly then... since the last operation in Ansible is to run a set of runtime manifests we reset it one more time to a value w/o the reboot flag => the reboot flag is no longer set, that's why after unlock we get the one bit difference in:"
1828271,2019-05-10 14:44:22 UTC,A solution that would avoid situations like this is to move the reboot flag out of the config_uuid so that it won't get overwritten when runtime manifests are applied yet such a modification has a high impact as we extensively make use of runtime manifets throughout the code.
1828271,2019-05-10 15:13:16 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658391"
1828271,2019-05-15 21:57:47 UTC,"Reviewed:  https://review.opendev.org/658391
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=9720932899b69287871a419422880f04d618286f
Submitter: Zuul
Branch:    master"
1828271,2019-05-09 09:57:48 UTC,"Yeah... it should be cleared after reboot, it look like it's not. I need to take a look at the underlying mechanism."
1828272,2019-05-09 09:41:51 UTC,"Adding Gerd to the CC, since this is possibly caused by recent work to keyboard state tracking code."
1828272,2019-08-15 18:43:53 UTC,"Fix has been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=5fff13f245cddd3bc26"
1828273,2019-05-08 18:58:42 UTC,Found another page stating that vga=0 should be in GRUB_CMDLINE_LINUX_DEFAULT - this does not work either.
1828273,2019-05-08 18:17:23 UTC,"I found another comment online and tried it: I added ""blacklist efifb"" to /etc/modprobe.d/blacklist-framebuffer.conf. I then executed ""update-initramfs -u"" followed by ""update-grub"" and rebooted. Still no joy."
1828273,2019-05-08 19:14:44 UTC,"Yet another comment I found said that the following would work, but it did not:
systemctl set-default -f multi-user.target"
1828275,2019-06-20 19:57:15 UTC,You can 'sudo snap connect chromium:mount-observe' for /etc/fstab. /run/mount/utab is more complicated and you can read about it here: https://forum.snapcraft.io/t/namespace-awareness-of-run-mount-utab-and-libmount/5987
1828275,2020-04-06 08:39:28 UTC,Bug still present.
1828275,2019-06-21 11:35:59 UTC,"Thanks! FYI, for the udev accesses: https://github.com/snapcore/snapd/pull/7019"
1828275,2020-04-02 03:20:21 UTC,still happens to me ubuntu 20.04 snapd 2.44+20.04
1828275,2020-04-02 03:22:32 UTC,"e.g.
110737.448098] audit: type=1400 audit(1585797347.453:11057): apparmor=""DENIED"" operation=""open"" profile=""snap.chromium.chromium"" name=2F686F6D652F64616E69656C2F736E61702F6368726F6D69756D2F313035362F2E636F6E6669672F6368726F6D69756D2F44656661756C742F53796E6320446174612F53796E63446174612E73716C697465332D6A6F75726E616C pid=42006 comm=""Chrome_SyncThre"" requested_mask=""wc"" denied_mask=""wc"" fsuid=1000 ouid=1000"
1828275,2019-10-11 18:19:20 UTC,Marking as fix-released as this went in snapd 2.40 according to https://github.com/snapcore/snapd/commit/1832205560164f725d7400ba0c09b40aa1ba365f
1828279,2019-05-24 12:31:02 UTC,+1 for this feature. This would be particularly awesome in large consortia like PINES where we all own the same record and there are many catalogers with access to edit the record.
1828279,2019-05-24 17:50:07 UTC,"I think it would be helpful to state the requirements more explicitly.  Here are my suggestions of what this new feature might include, in order of importance:"
1828279,2019-05-24 19:13:41 UTC,"I guess because my mind equated this to the Acq line item history, I was thinking of this in terms of an Angular eg-grid. That would take care of points #1 and #4."
1828279,2019-05-24 19:55:01 UTC,"For my purposes, #1 and #4 would be the basic requirements. I want to know who edited what field and I want to be able to see other changes they made to see if they made the same sort of edit on multiple records."
1828279,2019-12-10 14:21:09 UTC,"In my mind, #1 is the necessary action.  Also, #4 though I'd like a date filter.  From my understanding, this information is contained in audit tables that are configured very differently across Evergreen deployments.  In some cases, these are retained for 3 months.  In the case of Evergreen Indiana, they are retained for 9 months.  I suspect there are places that retain the data in these tables for a year or longer."
1828279,2019-12-10 14:47:46 UTC,"I set this bug to ""Confirmed"" because at least 5 to as many as 8 people have reported this wishlist bug as affecting them based on the heat at this time (40)."
1828279,2019-05-23 16:04:14 UTC,I would also like to see this feature. It would be extremely helpful when a MARC record has evolved over a long period of time and even for trying to remember how you yourself have changed/fixed/enhanced a type of record previously. It's an additional learning and teaching tool.
1828279,2019-05-08 21:37:43 UTC,I would love to know who changed what in a Marc record at a glance.
1828281,2019-05-08 19:00:10 UTC,This change was made by a bot.
1828281,2019-09-23 11:53:45 UTC,I have the same problem. Advised to test the core 5.3 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865
1828282,2019-05-27 23:49:37 UTC,"Test suite got fixed in master too, all is good:
https://git.busybox.net/busybox/commit/?id=b2c123d484dbe261758f27ced213f4649173803b"
1828282,2019-05-23 14:07:05 UTC,Nice!
1828282,2019-05-23 12:55:43 UTC,"Fixed in git, lots of thanks!"
1828282,2019-05-28 17:01:27 UTC,This bug was fixed in the package busybox - 1:1.30.1-4ubuntu4
1828282,2019-05-15 14:29:54 UTC,"------- Comment From <email address hidden> 2019-05-15 10:19 EDT-------
IBM Bugzilla status ->closed, tracking will be done via LP only."
1828282,2019-05-15 13:55:05 UTC,"@IBM
Please close your LTC bugzilla entry. We will continue to use this LP issue to pursue busybox upstream. Thanks a lot for your input!"
1828282,2019-05-15 12:29:28 UTC,"------- Comment From <email address hidden> 2019-05-15 08:26 EDT-------
@Xnox: due to the fact that this bugzilla is a busybox problem , can I close it on my side. This still is than open in LP for your tracking.."
1828282,2019-05-13 11:29:18 UTC,"------- Comment From <email address hidden> 2019-05-13 07:27 EDT-------
Hi xnox,"
1828282,2019-05-23 10:56:10 UTC,"Originally reported at https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1828282 with initial suspicion at glibc, however later diagnosed to be a busybox issue."
1828282,2019-05-13 11:44:24 UTC,"Will do! thanks for digging into this even though it's well, busybox issue."
1828283,2019-05-09 02:30:16 UTC,The only relevant problem I can see in the above logs is:
1828283,2019-05-09 03:00:26 UTC,This change was made by a bot.
1828284,2019-05-08 20:48:22 UTC,Low priority / Not gating given this doesn't cause build failures on full builds. Would be nice to fix though.
1828284,2019-05-08 22:12:45 UTC,"I forgot to mention there is a patch to fix this bug:
https://review.opendev.org/#/c/657869/"
1828284,2019-05-13 13:31:07 UTC,"Reviewed:  https://review.opendev.org/657869
Committed: https://git.openstack.org/cgit/starlingx/fault/commit/?id=81eea299f5770064c76b1b1ff7d04f2f9ba1b2ce
Submitter: Zuul
Branch:    master"
1828284,2019-05-24 18:17:55 UTC,Adding the stx.2.0 release tag as this commit is merged for that release.
1828285,2019-05-29 18:44:32 UTC,"My first impression was incorrect here.  These are visibility settings that are stored in the board file.  The plan during v6 is to move these settings to a separate file.  But for now, we should respect the board file and minimize churn in the saved file."
1828285,2019-05-09 21:39:07 UTC,"I've confirmed the ratsnest visibility setting is not saved/loaded on 5.1.2 and master, but I cant find the commit hash in the version info provided so may have milestoned wrong."
1828285,2019-05-29 14:26:02 UTC,It's not just ratsnest but all layers/netclasses/track settings that are meant to go into the project file.
1828285,2019-05-29 18:28:50 UTC,"Fixed in revision e7e20b85b5275fabe2677d3bdb453c021dd791a9
https://git.launchpad.net/kicad/patch/?id=e7e20b85b5275fabe2677d3bdb453c021dd791a9"
1828288,2019-06-13 15:53:58 UTC,"Hello Rafael, or anyone else affected,"
1828288,2019-06-27 18:30:06 UTC,"For the original QEMU hanging in Bionic (with Bionic kernel and not HWE one), I have opened the following BUG: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834522 (fyio)."
1828288,2019-06-20 22:00:08 UTC,"The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828288,2019-06-20 22:00:03 UTC,This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.40
1828288,2019-06-19 18:03:18 UTC,Verified. All bad cpu missing flags are gone:
1828288,2019-05-31 05:39:48 UTC,"While the issue fixed is purely cosmetic we have had users led astray by these in the past.
Since we do an SRU anyway that should be ok to be uploaded."
1828288,2019-05-08 20:24:47 UTC,"The attachment ""qemu_2.5+dfsg-5ubuntu10.38.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1828288,2019-05-28 13:33:11 UTC,PPA looks good:
1828288,2019-05-30 17:09:01 UTC,There are 2 things in this bug:
1828288,2019-05-09 06:44:42 UTC,"Thanks Rafael for identifying the issue and already providing a patch.
A few other things need to clear the SRU pipe first, then we can take the change it LGTM."
1828288,2019-05-08 19:45:01 UTC,Upstream discussion regarding the topic can be found here:
1828288,2019-05-17 10:49:33 UTC,I received an e-mail ~2 hours ago telling me:
1828288,2019-05-13 00:50:39 UTC,"Hey Christian,"
1828288,2019-05-28 10:21:04 UTC,"MP to review:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/367971"
1828289,2019-05-14 23:24:10 UTC,"Hi Jeff this seems to fix the issue, Thank you very much!"
1828289,2019-05-11 22:52:16 UTC,It's safe enough it should probably go into 5.1 whether it fixes the bug or not.
1828289,2019-05-11 22:51:33 UTC,"commit 717b1d37bed647ef9dfe6258554ee5f51f999d6b
Author: Jeff Young <email address hidden>
Date:   Fri May 10 19:59:44 2019 +0100"
1828289,2019-05-10 19:00:53 UTC,"I can't reproduce this, but I've inserted some defensive code which may (or may not) fix it."
1828289,2019-05-11 21:23:34 UTC,"Hi Jeff, where did insert the code? And can you also add it to 5.1 branch? (perhaps this should be milestoned for 5.1.3"
1828289,2019-05-09 14:27:50 UTC,"@Jeff
Maybe 4020b568 is relevant here?"
1828289,2019-05-09 12:52:57 UTC,my steps to reproduce.
1828289,2019-05-09 11:49:32 UTC,"@Jon
I hope this is more useful"
1828289,2019-05-09 05:50:52 UTC,Sure thing. Ill try it later
1828289,2019-05-09 03:20:46 UTC,"Hi Frank,
Do you use KiCad from the Ubuntu PPA?
If so, can you install the `kicad-dbg` package?
This will make the backtrace more useful.
Thanks"
1828289,2019-05-09 15:45:19 UTC,Could be a null pointer (ie: no object had focus)?  Hopefully it's not a freed pointer or trashed memory...
1828289,2019-05-09 18:34:03 UTC,@Jeff please let me know if I can do anything to help
1828290,2019-07-27 22:42:53 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828290,2019-07-27 22:44:38 UTC,"Would you mind to add this plugin to the list? Or is there a specific reason why to exclude this?
nemo-rabbitvcs"
1828290,2019-08-04 13:58:09 UTC,I just didn't know about it. No problem to add it.
1828290,2019-08-04 14:10:28 UTC,"Because of a problem with the WineHG PPA I changed the pinning, see changed description ...
But no idea, where to add nemo-rabbitvcs."
1828291,2019-05-14 08:15:06 UTC,Fixed in branch master. The fix will be in the next release. calibre is usually released every alternate Friday.
1828291,2019-05-09 15:54:59 UTC,This is the default metadata editor pane width.
1828291,2019-05-09 15:55:31 UTC,"This is the my custom metadata editor pane width, which Calibre doesn't remember (after restarting Calibre)."
1828291,2019-05-09 11:21:51 UTC,"Am confused what editor window display comments and other metadata? Can
you post a screenshot?"
1828292,2019-06-20 19:51:14 UTC,This was already done at some point.
1828293,2019-12-03 14:48:33 UTC,"Marking the openstack-dashboard bug as invalid, as it was a packaging bug.  There is a separate bug (lp:1837457) about handling upgrade failures in charms as they were not reported."
1828293,2019-07-22 19:38:09 UTC,"Corey,"
1828293,2019-07-22 18:17:16 UTC,"@Dmitrii, I looked at a couple of OpenStack charms and they didn't appear to handle upgrade failures in the hooks/*utils.py or actions/openstack_upgrade.py. Would you be opposed to moving that part of this bug to a new bug where we can track the issue across all affected charms?"
1828293,2019-07-05 23:43:33 UTC,Looks like Rocky UCA hasn't been updated with 1.5.0-0ubuntu3.1 yet:
1828293,2019-07-03 22:15:07 UTC,"This bug was fixed in the package neutron-fwaas-dashboard - 1.5.0-0ubuntu3.1~cloud0
---------------"
1828293,2019-07-03 22:15:06 UTC,The verification of the Stable Release Update for neutron-fwaas-dashboard has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1828293,2019-07-03 22:13:14 UTC,"This bug was fixed in the package neutron-fwaas-dashboard - 2.0.1-0ubuntu1.1~cloud0
---------------"
1828293,2019-07-03 22:13:12 UTC,The verification of the Stable Release Update for neutron-fwaas-dashboard has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1828293,2019-07-03 16:37:12 UTC,This bug was fixed in the package neutron-fwaas-dashboard - 1.5.0-0ubuntu3.1
1828293,2019-07-03 16:36:32 UTC,"The verification of the Stable Release Update for neutron-fwaas-dashboard has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828293,2019-07-03 16:36:29 UTC,This bug was fixed in the package neutron-fwaas-dashboard - 2.0.1-0ubuntu1.1
1828293,2019-07-03 14:24:09 UTC,Successfully tested for cosmic-proposed and disco-proposed:
1828293,2019-05-08 21:10:16 UTC,"Hi Dmitrii,"
1828293,2019-06-08 13:19:17 UTC,Verified with a Queens -> Rocky upgrade with a workaround for lp:1832075 (pre-installing python3-pymysql).
1828293,2019-05-08 20:07:59 UTC,The charm bug is about not reporting a failed upgrade in its status.
1828293,2019-07-03 13:49:55 UTC,python-neutron-fwaas-dashboard binary package is not available after Bionic so testing for Cosmic and Disco will just involve installation of python3-neutron-fwaas-dashboard to ensure no regression.
1828293,2019-05-10 13:26:49 UTC,Fixed versions of neutron-fwaas-dashboard have been uploaded to eoan as well as disco/cosmic unapproved queues [1] where they are awaiting SRU team review.
1828293,2019-05-10 13:33:44 UTC,This bug was fixed in the package neutron-fwaas-dashboard - 2.0.1-0ubuntu2
1828293,2019-05-15 17:40:06 UTC,CHARM TRIAGE:
1828293,2019-05-10 01:51:57 UTC,That last step should've been:
1828293,2019-05-16 17:54:06 UTC,"Hello Dmitrii, or anyone else affected,"
1828293,2019-05-21 19:10:51 UTC,"Hello Dmitrii, or anyone else affected,"
1828293,2019-05-22 01:27:04 UTC,"Hello Dmitrii, or anyone else affected,"
1828293,2019-05-31 14:04:22 UTC,"Hi Dmitrii, if you get a chance, please can you test that this is fixed in -proposed and tag this bug accordingly (ie. verification-done-*, etc)? Thanks!"
1828293,2019-06-08 08:29:28 UTC,I can confirm that this no longer occurs with proposed.
1828293,2019-05-16 11:43:51 UTC,"Hello Dmitrii, or anyone else affected,"
1828294,2019-05-08 21:01:16 UTC,"Hi Andrew, we had a similar report recently about high CPU usage that turned out to be a troublesome extension rather than LibreOffice itself:"
1828297,2019-05-10 20:38:22 UTC,"Are the column widths persisted in other dialogs grids and it's just missing in the ""Edit symbol fields"" dialog? This sounds like something that should be handled by wxWidgets."
1828297,2019-05-11 10:44:30 UTC,"Dear Mike,"
1828297,2019-05-14 11:46:50 UTC,"AFAIK, none of our dialogs that have controls with resizeable columns have column width persistence.  The only persistence is the dialog size and position.  Any other persistence would have to be added."
1828298,2019-05-14 07:43:36 UTC,"Fix is here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1c6bca6d75bca2cc47b5eafb9f7f16e368ffbeca"
1828299,2019-05-20 08:42:25 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.10.1
1828299,2019-05-20 08:47:57 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.04.1
1828299,2019-05-20 08:29:26 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1~19.04.1
1828299,2019-05-09 22:00:15 UTC,"Hello Mathieu, or anyone else affected,"
1828299,2019-05-14 18:36:00 UTC,Autopkgtests are passing (linked above); marking this verification-done.
1828299,2019-05-09 22:03:06 UTC,"Hello Mathieu, or anyone else affected,"
1828299,2019-05-09 21:57:49 UTC,"Hello Mathieu, or anyone else affected,"
1828299,2019-05-20 08:19:29 UTC,"The verification of the Stable Release Update for netplan.io has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828299,2019-05-09 15:00:22 UTC,This bug was fixed in the package netplan.io - 0.97-0ubuntu1
1828300,2020-06-27 18:05:51 UTC,LP was closed as invalid a long time ago; removing the stx.retestneeded tag
1828300,2019-10-14 03:14:43 UTC,"Set it to invalid since not reproducible.
reopen when it is reproduced"
1828300,2019-06-28 08:32:14 UTC,"Dear tester,"
1828300,2019-08-22 06:26:54 UTC,"Keep open for one more week, if no update, we should set it to invalid."
1828300,2019-08-08 10:42:10 UTC,"Hi Daniel - going through some of the ""Incomplete"" Launchpads - can you comment on this (have you been able to reproduce this)?  Thanks."
1828300,2019-05-13 17:27:45 UTC,Marking as release gating; inconsistency with the dashboard.
1828300,2019-08-23 17:55:00 UTC,"As per agreement with the community, moving all unresolved medium priority bugs from stx.2.0 to stx.3.0"
1828303,2019-05-08 21:13:08 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9982"
1828303,2019-06-09 22:38:02 UTC,"Reviewed:  https://reviews.mahara.org/9982
Committed: https://git.mahara.org/mahara/mahara/commit/77433f099e19b268cf53675dc7394f6f193bfafa
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1828304,2019-08-26 20:22:25 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828304,2019-08-26 20:34:13 UTC,"I have the same card and experience similar problems. For me downloading is normal, but uploading is significantly slower."
1828304,2020-05-25 11:03:44 UTC,"It seems that this bug was fixed in Ubuntu 20, which is nice :)"
1828309,2019-06-09 22:38:09 UTC,"Reviewed:  https://reviews.mahara.org/9983
Committed: https://git.mahara.org/mahara/mahara/commit/e168d22f5534d0e830ecbb535c096b4cbd1e6fdd
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1828309,2019-06-18 22:46:16 UTC,"Reviewed:  https://reviews.mahara.org/9985
Committed: https://git.mahara.org/mahara/mahara/commit/5d825f94996938d7fd409e9a4fd91024b0c81c00
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1828309,2019-05-09 00:53:43 UTC,TITLE:  Create institution addUserAsStaff() and addUserAsAdmin() wrapper functions
1828309,2019-05-09 01:01:23 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9985"
1828309,2019-05-08 23:26:04 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/9983"
1828311,2019-05-09 17:42:01 UTC,Please do not change the message to
1828311,2019-05-13 23:41:05 UTC,"What did we want to do with this then?  Personally I feel that we should delete the DEBUG PXE events as I feel like the added information of PXE booting with the added information ""for installation"" isn't something to be fawned over."
1828312,2019-05-08 23:56:29 UTC,seems qemu-efi package is missing when deploying an arm64 kvm pod.
1828313,2019-07-19 08:42:48 UTC,"Could you do the logging like in your comment #4 of your question again but in debug mode, as described on"
1828313,2019-08-17 21:02:37 UTC,I can't found python script debug-helper.py  in /usr/lib/NetworkManager/
1828313,2019-09-04 13:32:46 UTC,"sudo /usr/lib/NetworkManager/debug-helper.py --mm debug
Traceback (most recent call last):
  File ""/usr/lib/NetworkManager/debug-helper.py"", line 10, in <module>
    mm_bus = bus.get_object('org.freedesktop.ModemManager', '/org/freedesktop/ModemManager')
  File ""/usr/lib/python2.7/dist-packages/dbus/bus.py"", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File ""/usr/lib/python2.7/dist-packages/dbus/proxies.py"", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File ""/usr/lib/python2.7/dist-packages/dbus/bus.py"", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
  File ""/usr/lib/python2.7/dist-packages/dbus/bus.py"", line 278, in start_service_by_name
    'su', (bus_name, flags)))
  File ""/usr/lib/python2.7/dist-packages/dbus/connection.py"", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ModemManager was not provided by any .service files"
1828313,2019-09-04 13:35:28 UTC,"sudo /usr/lib/NetworkManager/debug-helper.py --nm debug
Traceback (most recent call last):
  File ""/usr/lib/NetworkManager/debug-helper.py"", line 10, in <module>
    mm_bus = bus.get_object('org.freedesktop.ModemManager', '/org/freedesktop/ModemManager')
  File ""/usr/lib/python2.7/dist-packages/dbus/bus.py"", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File ""/usr/lib/python2.7/dist-packages/dbus/proxies.py"", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File ""/usr/lib/python2.7/dist-packages/dbus/bus.py"", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
  File ""/usr/lib/python2.7/dist-packages/dbus/bus.py"", line 278, in start_service_by_name
    'su', (bus_name, flags)))
  File ""/usr/lib/python2.7/dist-packages/dbus/connection.py"", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ModemManager was not provided by any .service files"
1828313,2019-11-04 04:17:28 UTC,[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]
1828314,2019-05-09 00:20:48 UTC,"As a work-around I'm using kcolorchooser
sudo apt install kcolorchooser"
1828314,2019-05-10 04:23:14 UTC,Maybe https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928723
1828315,2019-07-11 16:55:04 UTC,This bug was fixed in the package xca - 2.1.2-0ubuntu2
1828316,2019-07-11 16:55:04 UTC,This bug was fixed in the package xca - 2.1.2-0ubuntu2
1828318,2019-05-09 01:00:11 UTC,A bigger part of the logging can be found here: https://pastebin.canonical.com/p/vyDkQsHt9F/
1828319,2020-04-08 16:34:14 UTC,This has been fixed in train with https://review.opendev.org/#/c/670890/
1828324,2019-05-10 07:26:32 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1828324,2019-05-10 07:26:17 UTC,"You have removed mysql at
 2019-05-08  22:38:38
And then (re)installed it at
  2019-05-08  22:55:45"
1828324,2019-05-09 04:15:45 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1828324,2019-07-10 04:17:16 UTC,[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]
1828328,2019-09-16 11:17:05 UTC,18.04.3 subiquity failed to recognize the 400GB NVMe module as an installation target.
1828328,2019-09-18 07:39:45 UTC,install from edge r1181 works for me. (also confirm it's not work before refresh snap)
1828328,2019-05-09 18:02:03 UTC,"Hi,"
1828328,2019-09-17 16:57:44 UTC,"Thanks Ryan,"
1828328,2019-09-16 12:54:23 UTC,Thanks for providing the screenshots.
1828331,2019-05-11 23:42:28 UTC,"Hi Ghada,"
1828331,2019-05-20 05:38:04 UTC,Thanks Kristina.
1828331,2019-05-20 05:55:13 UTC,"Patch for ""master"" branch: https://reviews.mahara.org/10030"
1828331,2019-05-20 06:01:46 UTC,Affected locations:
1828331,2019-05-22 20:32:35 UTC,"Commit hash: 412b73280c4a4ef86b518134374a9af1839bb5a6
Environment tested: Master
Browser tested: Chrome
Theme used:  Raw | Default raw | Ocean | Modern | Primary school"
1828331,2019-06-14 23:07:51 UTC,"Reviewed:  https://reviews.mahara.org/10030
Committed: https://git.mahara.org/mahara/mahara/commit/412b73280c4a4ef86b518134374a9af1839bb5a6
Submitter: Robert Lyon (<email address hidden>)
Branch:    master"
1828331,2019-06-14 23:09:03 UTC,Will not backport this one to core 19.04 as I feel it is a functionality change rather than a bug fix
1828332,2019-05-09 05:01:40 UTC,"Ugh. The root cause here is an error in bootstrap in which a post process operation fails and masks the original error. At this stage, I think the only thing you can do is microk8s.reset to start again. We'll fix juju to properly report the root cause error."
1828332,2019-05-10 02:03:51 UTC,"https://github.com/juju/juju/pull/10162/files is merging to 2.6 to fix this.
Thanks!"
1828333,2019-07-03 12:37:15 UTC,A revert would probably cause https://bugs.launchpad.net/glance/+bug/1805765 to regress where the change was introduced. Maybe you would need to create /etc/glance/glance-api.conf.d/ and place additional config files there?
1828333,2019-09-02 04:17:30 UTC,[Expired for devstack because there has been no activity for 60 days.]
1828333,2019-05-09 04:58:56 UTC,After doing certain digging I have found that filesystem_store_datadir is defined in glance-api.conf and glance-cache.conf as well. Recently due to a change in devstack [1] glance-api is parsing all configuration files present in /etc/glance directory. As a result of this even you change the filesystem_store_datadir parameter in glance-api.conf it is overridden from the glance-cache.conf file.
1828333,2019-05-09 07:49:13 UTC,Easiest should be to make sure that the option is commented out on the -cache.conf that devstack deploys (and on every other config file in that dir as well). This is good reminder that the last config file always overrides anything set before when the config dir is used.
1828333,2019-05-09 07:56:44 UTC,Flagging this to Devstack as Glance parses the config files as designed.
1828334,2019-05-13 16:09:59 UTC,What version of senlin are you using?  Stein?
1828334,2019-05-14 02:03:48 UTC,"In that time, i used senlin was install from source code with master branch"
1828334,2019-07-22 04:17:25 UTC,[Expired for senlin because there has been no activity for 60 days.]
1828345,2019-05-10 08:58:07 UTC,"And a third crash, this time after upgrading to 4.4.0-146-generic. Uptime just 21h41m. Backtrace looks the same."
1828345,2019-05-10 09:26:07 UTC,"hello,"
1828345,2019-05-10 09:55:22 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828345,2019-05-10 11:32:09 UTC,"Hi Peter, and thanks for confirming the bug."
1828345,2019-05-13 05:28:54 UTC,"hello Tore,"
1828345,2019-05-24 00:23:26 UTC,"Hi,"
1828345,2019-05-28 08:15:50 UTC,"Same here with 4.4.0-144 and 4.4.0-148.
Kernel 4.4.0-143 is not affected"
1828345,2019-06-11 09:26:53 UTC,"We had another server running 4.4.0-148-generic crash just now. It has a different role then the firewalls that we originally saw the crash with. After an automatic reboot, it got back up with 4.4.0-150-generic (which had been installed at an earlier stage but not rebooted into), and crashed twice in rapid succession. I'm including the traces printed to the serial console below:"
1828352,2019-05-09 09:13:14 UTC,This is fixed in the following pull request: https://github.com/snapcore/snapd/pull/6846
1828354,2020-02-03 09:48:10 UTC,This is still in progress (some related bugs in the repository have been fixed recently) but has not been merged and is really not super critical. Demoting to high and marking as confirmed. I will change this back when I can work on the related branch again.
1828354,2019-09-06 12:53:25 UTC,"This took a while but the fix is close to being mergeable. I will open a new PR early next week, as prerequisites get merged."
1828354,2019-09-09 13:41:39 UTC,The v2 version of the fix is being worked on here: https://github.com/snapcore/snapd/pull/7436
1828354,2019-05-23 16:28:18 UTC,I've proposed a fix for this in https://github.com/snapcore/snapd/pull/6891
1828355,2019-09-16 07:47:36 UTC,Migrated to https://github.com/widelands/widelands/issues/3430
1828355,2019-05-27 20:14:12 UTC,"Ok, thanks for implementing this. I think I should learn how to upload a branch if I find more to work on."
1828355,2019-05-26 11:21:47 UTC,"P.S: actually, it should have one, but it will be empty."
1828355,2019-08-11 19:21:53 UTC,"fuchur, can you please test the attached branch?"
1828355,2019-05-22 21:57:45 UTC,Now I found a solution concerning the problem with the locale folder. In wlapplication.cc I replaced
1828355,2019-05-13 20:24:59 UTC,"Ok, I made a quick test, the --homedir option is recognised and the given directory is created. A config and stdout.txt are created as well. Starting a game and saving one works. The directories ai, save, replays and temp are then created."
1828355,2019-05-12 18:27:31 UTC,I have replaced the log command with cout in https://bazaar.launchpad.net/~widelands-dev/widelands/trunk/revision/9105
1828355,2019-05-12 13:57:21 UTC,"The problem is the windows logger which is initialized in WLApplication::setup_homedir(). But there is a call of log() in WLApplication::WLApplication(int const argc, char const* const* const argv) before that happens. See source below"
1828355,2019-05-09 19:52:56 UTC,With linux the --homedir option works as expected.
1828355,2019-05-26 11:20:13 UTC,The fix looks fine. I'll implement it into WLApplication so that we won't get a circular dependency between i18n and the file system.
1828356,2019-05-10 03:10:54 UTC,"Something worth mentioning: on this device and another with similar sound chip (201904-26953), the audio/alsa_info_attachment job stales until the the Settings panel is open (not even in the ""Sound"" section!). It's probably related to the same root cause."
1828356,2019-10-08 13:20:45 UTC,The following errors:
1828357,2021-02-09 21:53:37 UTC,Zygmunt was this work ever done?
1828357,2021-02-09 22:59:35 UTC,I think Maciek figured out a bug in sorting but we didn’t do the kind of sorting described here.
1828358,2019-05-20 06:04:01 UTC,"A similar screen blink (about 1-2 secs interval) also happens at screen
wipe/blackout/timeout whatever it's called. Seems a similar issue; a
""smaller"", other dpi (""high resolution"") screen is glanced in the flickering"
1828358,2020-01-24 08:58:28 UTC,"Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020."
1828358,2019-05-17 21:11:28 UTC,"Also affects video playback, switching between fullscreen and windowed mode becomes unusably slow. Playing games (The Long Dark as an example) also results in flickering of a black screen when the volume overlay is shown when changing volume"
1828358,2019-05-10 20:54:48 UTC,apport information
1828358,2019-05-10 20:54:50 UTC,apport information
1828358,2019-05-10 20:54:49 UTC,apport information
1828358,2019-05-10 01:46:50 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:"
1828358,2019-05-09 08:20:03 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1809407, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1828358,2019-05-10 20:54:52 UTC,apport information
1828360,2019-06-13 22:11:03 UTC,https://github.com/mixxxdj/mixxx/pull/2164
1828360,2019-06-13 22:31:27 UTC,"Now some infrequent crashes when exiting Mixxx should also be fixed, finally. Just a simple typo / copy&paste error."
1828361,2019-05-09 16:41:30 UTC,"This is already planned, and rolling out very very soon. I'll probably be doing some big upgrades on the server side today to support ssl, then the cli/agent pieces will be rolling out shortly after that."
1828361,2019-05-23 14:55:49 UTC,"This is resolved since last week really, but there are still some QA test runs that are using an old copy of testflinger-cli, which defaults to looking at port 80 instead of 443.  All they need to do is update that testflinger-cli snap or source tree that they are running from, and it will use https."
1828363,2019-05-09 08:49:24 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657958"
1828363,2019-05-21 00:48:16 UTC,"Reviewed:  https://review.opendev.org/657958
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8db230ab08da807e4d28b0fa559d9d97db580d0e
Submitter: Zuul
Branch:    master"
1828363,2019-09-19 10:14:05 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1828366,2019-05-09 09:02:18 UTC,"The nautilus's font can be set by my favorite bitmap font, look at the difference."
1828367,2019-09-19 10:13:35 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1828367,2019-05-16 22:33:41 UTC,Taken from the Ironic story indicted above:
1828367,2019-05-16 22:36:25 UTC,It was discussed with the Ironic team during the PTG and approved
1828367,2019-06-01 02:08:03 UTC,"Reviewed:  https://review.opendev.org/658787
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=afff649a3900dd75ffe699f4a599bcbdc449598c
Submitter: Zuul
Branch:    master"
1828367,2019-05-13 10:53:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658787"
1828374,2019-05-10 07:30:26 UTC,Also met the same issue on another HP system.
1828374,2019-05-09 09:32:32 UTC,This bug can happen when:
1828374,2019-05-09 09:33:34 UTC,"Perhaps you can abort that change (snap abort 1), stop snapd, edit the seed to include the extra core18 snap, add the snap and the assertions to the seed directory and restart snapd."
1828374,2019-10-15 11:24:07 UTC,It seems to imply that some OEM systems are either evaluated or have shipped with incorrect snapd seed that prevents the seeding from succeeding. There has been a number of issues related to incorrect seeds in OEM images. For example: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1772844 and https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767896
1828374,2019-12-15 04:17:38 UTC,[Expired for Snappy because there has been no activity for 60 days.]
1828375,2020-02-17 16:04:38 UTC,"Reviewed:  https://review.opendev.org/702365
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b51f231c9d912eb2082deb378a2671c10ae43564
Submitter: Zuul
Branch:    stable/rocky"
1828375,2019-08-29 08:18:59 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/679198"
1828375,2019-08-29 08:33:32 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/679200"
1828375,2019-08-29 16:08:46 UTC,"Reviewed:  https://review.opendev.org/679197
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c09e8295806a5f6932b7a2a3795aac008d6e3480
Submitter: Zuul
Branch:    stable/stein"
1828375,2019-09-03 16:02:04 UTC,"Reviewed:  https://review.opendev.org/679198
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1199207e7da977e1cd3c12f8a4242aafe6330d68
Submitter: Zuul
Branch:    stable/rocky"
1828375,2019-10-09 23:38:46 UTC,"Reviewed:  https://review.opendev.org/679200
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8167fb944ecc9d75b731c166b7fd4cf1bb97608c
Submitter: Zuul
Branch:    stable/queens"
1828375,2019-12-12 11:35:32 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/698698"
1828375,2020-01-13 20:36:25 UTC,"Reviewed:  https://review.opendev.org/698698
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ade35a233edb5c9489cc3a68ae00672fb328f63d
Submitter: Zuul
Branch:    master"
1828375,2020-01-14 08:16:43 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/702365"
1828375,2020-01-14 08:16:56 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/702366"
1828375,2020-01-16 00:58:12 UTC,"Reviewed:  https://review.opendev.org/702363
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8ec0c2d8658acd6fb0aaf80751914514bdb42334
Submitter: Zuul
Branch:    stable/train"
1828375,2020-01-28 20:46:38 UTC,"Reviewed:  https://review.opendev.org/702364
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7a8b59624c87b6b74f28e98a1cff1d6a40edc65f
Submitter: Zuul
Branch:    stable/stein"
1828375,2020-01-30 04:20:07 UTC,"Reviewed:  https://review.opendev.org/702366
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7a1e79e90b09e5d39d65c4f8da49fcf3af7e2c63
Submitter: Zuul
Branch:    stable/queens"
1828375,2019-08-29 08:18:45 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/679197"
1828375,2019-08-29 03:59:02 UTC,"Reviewed:  https://review.opendev.org/679053
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d1f8888843c53c1c4b95c2fd22b2b6ee97feb238
Submitter: Zuul
Branch:    master"
1828375,2020-01-14 08:16:22 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/702364"
1828375,2019-08-02 11:54:02 UTC,We were able to apply the fix and it seems to help. Thanks folks!
1828375,2019-08-28 13:16:25 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/679053"
1828375,2019-05-09 13:26:08 UTC,"Additionally I found that those bugs may be related (or duplicates possibly):
* https://bugs.launchpad.net/neutron/+bug/1805132
* https://bugs.launchpad.net/neutron/+bug/1738337
* https://bugs.launchpad.net/neutron/+bug/1716321"
1828375,2019-05-09 15:08:07 UTC,"Could you confirm that the same issue happens on master as well, or can you provide reproduction steps without containers?
I suppose something like this:
- create port as parent port
- create trunk --parent-port <parent_port_id>
- put trunk/add_subport"
1828375,2019-05-10 07:02:57 UTC,"Unfortunately I am not able to use master...
Reproduction without containers:
1. port create --network NetworkA --name portA
2. server create --nic port-id=portA
3. create trunk --parent-port=portA --name TrunkA
4. 40x port create --network NetworkB (subports)
5. 40x network trunk set --subport eachSubPort TrunkA
6. Wait for all subports to become ACTIVE."
1828375,2019-05-13 13:03:35 UTC,"Just a note, could you check this page: https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling
Perhaps you can find there something useful"
1828375,2019-05-22 13:43:26 UTC,I managed to reproduce the problem on master (commit dfc2586fb1) with a script like this:
1828375,2019-05-24 12:20:07 UTC,I'm starting to understand what's going on in this error. Here's a summary:
1828375,2019-05-24 12:22:01 UTC,The mysql-part of this problem can be reproduced by the following little standalone program by running to instances of it concurrenlty (after a little setup documented at it beginning):
1828375,2020-01-14 08:06:25 UTC,"Fix proposed to branch: stable/train
Review: https://review.opendev.org/702363"
1828375,2019-06-27 15:56:33 UTC,"Reviewed:  https://review.opendev.org/662236
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=618e24e241241c7323702a815542f11e91fd32a1
Submitter: Zuul
Branch:    master"
1828375,2019-07-30 21:37:50 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/673696"
1828375,2019-07-31 07:24:45 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/673744"
1828375,2019-07-31 07:24:58 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/673745"
1828375,2019-07-31 22:09:27 UTC,"Reviewed:  https://review.opendev.org/673696
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d090fb9a3cbad6c4c3f5c524907a94cb5f95b205
Submitter: Zuul
Branch:    stable/stein"
1828375,2019-08-01 21:32:42 UTC,"Reviewed:  https://review.opendev.org/673745
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=10191fd81706f302f2114c8a196d5e0a0cd1b5db
Submitter: Zuul
Branch:    stable/queens"
1828375,2019-08-01 21:32:52 UTC,"Reviewed:  https://review.opendev.org/673744
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=80389bb4ee8a9cd52401187b278e339c69d9f295
Submitter: Zuul
Branch:    stable/rocky"
1828375,2019-05-30 14:46:34 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662236"
1828376,2019-07-31 12:56:32 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828376,2019-07-31 13:02:40 UTC,"IMPORTANT: adb backup does not work anymore with this version, see https://stackoverflow.com/questions/49046843/how-to-fix-adb-backup-return-41-bytes"
1828380,2019-05-09 09:59:05 UTC,"Note that this issue does not exist on Disco AMD64 / ARM64 / PowerPC.
Just i386"
1828380,2019-05-09 10:00:09 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828382,2019-05-11 10:17:47 UTC,"Note that neutron rbac policy feature is available only when the corresponding neutron quota is enabled. In the network quota form, you need to check the neutron extension and enable the field if enabled."
1828386,2019-05-09 10:34:58 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/657985"
1828386,2020-07-21 17:34:47 UTC,"Reviewed:  https://review.opendev.org/657985
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0d22547fd246be4b09536c2da633af421e9c7df0
Submitter: Zuul
Branch:    master"
1828391,2019-05-09 11:30:10 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828391,2019-09-18 07:50:41 UTC,"Disco build OK.
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=cb7652573dc1237a6180d25250092aa31ea7d8ba
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=11ba1cfe613d49caa518fbb633345ef00acb3ad9"
1828394,2019-06-11 10:58:02 UTC,"------- Comment From <email address hidden> 2019-06-11 06:37 EDT-------
IBM Bugzilla status -> closed, Fix Released for requested distro"
1828394,2019-06-04 09:18:16 UTC,This bug was fixed in the package linux - 4.15.0-51.55
1828394,2019-05-21 14:56:07 UTC,"@afox thx for the verification, adjusting tags based on your successful verification."
1828394,2019-05-21 13:44:36 UTC,"------- Comment From <email address hidden> 2019-05-21 08:32 EDT-------
fix works as expected"
1828394,2019-05-16 15:03:29 UTC,"This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'."
1828394,2019-05-14 09:09:01 UTC,"There is no test kernel available, yet, but a kernel will be made available for verification purposes via the proposed archive pocket as part of the kernel SRU process.
The patch/commit was already accepted:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100674.html
and applied to the bionic-next tree.
One of the next steps is now to create that new kernel version and make it available via proposed.
Once available an (automated) comment will be added to this ticket and you will be asked for verification. This may take some days - see 'Kernel prep' here: https://kernel.ubuntu.com/"
1828394,2019-05-14 07:29:19 UTC,"------- Comment From <email address hidden> 2019-05-14 03:26 EDT-------
Canonical: Can someone provide the info where to download the test-kernel for our testing.."
1828394,2019-05-09 15:39:41 UTC,"Kernel SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2019-May/thread.html#100652"
1828394,2019-05-17 10:09:37 UTC,"------- Comment From <email address hidden> 2019-05-17 06:04 EDT-------
ok, we gone test the fix."
1828394,2019-05-09 11:47:33 UTC,"------- Comment From <email address hidden> 2019-05-09 07:46 EDT-------
Problem was detected on 16.04.5 but is the same kernel like 18.04.
Can a test kernel be provided for our test. That would be great......
Many thx in advance"
1828395,2019-05-09 11:39:59 UTC,"For this bug to be useful, I think some thoughts on exactly how this could work for the user is needed."
1828395,2019-05-09 12:51:07 UTC,"Something like this is in the works, it may make it to 6.0"
1828395,2019-07-09 04:17:22 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1828398,2019-05-30 23:03:28 UTC,"I have since removed the dependency on cJSON, opting to reduce dependencies by switching to jansson since it is already an indirect dependency of libnss-aad, (it is required by libjwt); therefore, I no longer have need of this bug."
1828404,2019-07-09 04:17:24 UTC,[Expired for gcc-7 (Ubuntu) because there has been no activity for 60 days.]
1828404,2019-05-09 16:36:06 UTC,please provide the preprocessed source and the command line arguments used to build this source.
1828404,2019-05-09 17:29:30 UTC,"Sorry, I don't know how to provide the requested information.
I just wanted to try out WireGuard by following the instructions at https://www.wireguard.com/install/ ."
1828406,2019-05-09 15:11:01 UTC,"Could you provide some environment details (like the branches you used), and reproduction steps?"
1828406,2019-05-13 14:22:11 UTC,"Thanks Ryan, I'll mark it as invalid and wait until we are on Stein."
1828406,2019-05-09 15:12:23 UTC,"If it is ryu I suppose neutron is older than stein as from stein instead of ryu os-ken is used, am I right?"
1828406,2019-05-13 13:55:18 UTC,This may have been fixed in os-ken on stein https://review.opendev.org/#/c/648993/
1828406,2019-05-09 15:40:01 UTC,"Ah sorry, it's a Rocky cloud so yeah it's still Ryu."
1828407,2019-05-10 07:41:19 UTC,"Config is in
/etc/mysql/mysql.conf.d/mysqld.cnf"
1828407,2019-05-10 09:03:01 UTC,"Default is enabled from mysql data directory
https://dev.mysql.com/doc/refman/5.7/en/creating-ssl-rsa-files-using-mysql.html
One can override that with parameters you mentioned (and use CA signed keys as opposed to default opportunistic attempt)"
1828408,2019-06-05 16:54:36 UTC,"Removing packages from eoan:
        circlator 1.5.5-2 in eoan arm64
        circlator 1.5.5-2 in eoan armhf
        circlator 1.5.5-2 in eoan i386
        circlator 1.5.5-2 in eoan ppc64el
        circlator 1.5.5-2 in eoan s390x
Comment: NBS
Remove [y|N]? y
5 packages successfully removed."
1828409,2019-06-20 19:38:38 UTC,"i386 as a whole will be removed soon, so wontfixing this bug."
1828409,2019-10-17 07:06:02 UTC,I think i386 status quo changed...
1828409,2019-11-06 01:13:01 UTC,"Removing packages from focal:
 bio-eagle 2.4.1-1 in focal i386
 bio-tradis 1.4.1+dfsg-1 in focal i386
 delly 0.8.1-2 in focal i386
 fastqtl 2.184+dfsg-7 in focal i386
 grabix 0.1.7-2 in focal i386
 kallisto 0.46.0+dfsg-1 in focal i386
 libtabixpp-dev 1.0.0-4 in focal i386
 libtabixpp0 1.0.0-4 in focal i386
 python3-cyvcf2 0.11.5-1build1 in focal i386
 nanopolish 0.11.1-1 in focal i386
 qtltools 1.2+dfsg-1 in focal i386
 segemehl 0.3.4-1 in focal i386
 shapeit4 4.0+dfsg-1 in focal i386
 stringtie 1.3.6+dfsg-1 in focal i386
Comment: ANAIS
14 packages successfully removed.
Removing packages from focal:
 libhts-dev 1.9-10 in focal i386
 libhts2 1.9-10 in focal i386
 tabix 1.9-10 in focal i386
Comment: ANAIS
3 packages successfully removed."
1828410,2019-05-09 13:16:43 UTC,The following patches have been skipped as they have already been applied:
1828410,2019-05-09 14:57:50 UTC,Built test passed on all architectures:
1828410,2019-05-13 15:24:33 UTC,"SRU request sent to the mailing-list:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100654.html"
1828410,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1828414,2019-06-07 19:29:55 UTC,This issue was fixed in the openstack/tripleo-heat-templates 11.0.0 release.
1828414,2019-05-17 21:52:03 UTC,"Reviewed:  https://review.opendev.org/658085
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=e4039299fc59103c5480c792c73c0915089bdeb4
Submitter: Zuul
Branch:    master"
1828414,2019-05-17 18:21:44 UTC,"Reviewed:  https://review.opendev.org/658084
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=063e493418e59c5aa5221baa1dbc222701f38528
Submitter: Zuul
Branch:    master"
1828414,2019-05-17 16:21:10 UTC,"Reviewed:  https://review.opendev.org/658081
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=20dbe32060f7db3b99cd8ca87d12e6571f1bde36
Submitter: Zuul
Branch:    master"
1828414,2019-05-09 13:56:44 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658085"
1828414,2019-05-09 13:51:21 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658084"
1828414,2019-05-09 13:48:25 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658081"
1828415,2019-05-09 13:32:06 UTC,The following patches have been skipped as they have already been applied:
1828415,2019-05-13 15:42:16 UTC,The following commits had to be added due to config changes:
1828415,2019-05-13 15:43:17 UTC,Compile tested on all supported architectures:
1828415,2019-05-13 15:51:17 UTC,SRU request sent to the mailing-list:
1828415,2019-06-04 09:17:48 UTC,This bug was fixed in the package linux - 5.0.0-16.17
1828416,2019-11-06 01:14:47 UTC,This issue was fixed in the openstack/kolla 9.0.0.0rc1 release candidate.
1828416,2019-10-17 10:18:56 UTC,This issue was fixed in the openstack/kolla pike-eol release.
1828416,2019-07-18 00:38:21 UTC,This issue was fixed in the openstack/kolla 8.0.0.0rc2 release candidate.
1828416,2019-07-03 07:38:03 UTC,"Reviewed:  https://review.opendev.org/668625
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=658090a3af8756f625ea9db08ea0826953b9264a
Submitter: Zuul
Branch:    stable/pike"
1828416,2019-07-02 07:41:50 UTC,"Fix proposed to branch: stable/pike
Review: https://review.opendev.org/668625"
1828416,2019-06-14 01:15:07 UTC,This issue was fixed in the openstack/kolla 7.0.3 release.
1828416,2019-06-14 01:14:50 UTC,This issue was fixed in the openstack/kolla 6.2.2 release.
1828416,2019-05-20 12:29:22 UTC,"Reviewed:  https://review.opendev.org/659855
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=916198a9e91a463f0334fefce950273bb203d9fd
Submitter: Zuul
Branch:    stable/queens"
1828416,2019-05-17 17:48:05 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/659855"
1828416,2019-05-15 08:08:40 UTC,"Reviewed:  https://review.opendev.org/658168
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=2b2218448f2562598c684b3dc4ca5ea1847b4ac7
Submitter: Zuul
Branch:    stable/stein"
1828416,2019-05-10 10:58:46 UTC,"Reviewed:  https://review.opendev.org/658169
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0eb7f031c29a5d4c6e05c1787af2e6a7d09749f5
Submitter: Zuul
Branch:    stable/rocky"
1828416,2019-05-09 18:01:05 UTC,"Reviewed:  https://review.opendev.org/658078
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=e6387634c6a7170e96606b9a8ff680f08d81e801
Submitter: Zuul
Branch:    master"
1828416,2019-05-09 18:13:55 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/658168"
1828417,2019-05-21 20:42:29 UTC,I had a go at this. Seems like this was introduced in 61f2dd21b1be5d25a2d9b75ee772064aa53fabf9 to workaround some bitmap/gal refresh issue. Someone with more knowledge should take a look.
1828417,2019-06-13 16:56:30 UTC,"@Hildo, are you still seeing this issue?  I'm not seeing it on the latest commit to master."
1828417,2019-06-13 17:29:50 UTC,"@Michael, you patch no longer applies cleanly to the master branch.  Please rebase when you get chance."
1828417,2019-06-13 17:40:23 UTC,"Don't. Now it's fine, clicking in <Ok> the page is just centralized and the zoom set to 0.0."
1828417,2019-06-13 17:53:56 UTC,Not sure where this got fixed but it did.
1828418,2019-09-16 15:49:17 UTC,Migrated to https://github.com/widelands/widelands/issues/2139
1828420,2019-06-04 09:11:38 UTC,This bug was fixed in the package linux - 4.4.0-150.176
1828420,2019-05-13 15:39:17 UTC,"SRU request sent to the mailing-list:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100678.html"
1828420,2019-05-13 15:18:09 UTC,Build tested on all supported architectures:
1828420,2019-05-13 15:00:11 UTC,The following commits had to be added due to changes on the config options:
1828420,2019-05-09 14:22:24 UTC,The following patch has been skipped as it has already been applied:
1828422,2019-12-04 17:37:52 UTC,This is particularly problematic when doing Q -> R and therefore py2 -> py3
1828422,2019-12-04 17:48:22 UTC,Also applies to neutron-gateway - none of my neutron service got restarted
1828422,2019-12-04 17:54:59 UTC,"Ammendment to comment #2, some did some didn't, specifically neutron-dhcp-agent did not get restarted."
1828422,2019-12-05 10:59:06 UTC,"I think a good way to achieve this is to place the openstack-origin in the container-scope relation to the subordinate and then the subordinate can choose whether to upgrade based on what the principal is doing.  This would be backwards compatible, as older charms would ignore the extra key."
1828422,2019-12-05 19:33:30 UTC,"On Thu, 2019-12-05 at 10:59 +0000, Alex Kavanagh wrote:

> I think a good way to achieve this is to place the openstack-origin
> in
> the container-scope relation to the subordinate and then the
> subordinate
> can choose whether to upgrade based on what the principal is doing.
> This would be backwards compatible, as older charms would ignore the
> extra key.
"
1828422,2019-12-09 11:12:16 UTC,"> the subordinate wouldn't own /etc/apt/sources.list.d/cloud-
archive.list, right?
"
1828423,2020-02-19 16:14:57 UTC,"Reviewed:  https://review.opendev.org/708123
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5a0c3e1fddd9863ff4d515e153ec67c0c3bbcb22
Submitter: Zuul
Branch:    stable/stein"
1828423,2020-02-19 01:43:46 UTC,"Reviewed:  https://review.opendev.org/708124
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9499467caedfd2b30d2514f15b41cbde6e8a9fe6
Submitter: Zuul
Branch:    stable/rocky"
1828423,2020-02-19 01:29:40 UTC,"Reviewed:  https://review.opendev.org/708125
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=de29b49b132b84f07329780958b503edbd5c77f6
Submitter: Zuul
Branch:    stable/queens"
1828423,2020-02-17 12:58:46 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/708125"
1828423,2020-02-17 12:58:30 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/708124"
1828423,2020-02-17 12:58:13 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/708123"
1828423,2020-05-27 21:15:27 UTC,Can we close this bug as resolved now? Or do we need anything else regarding to it?
1828423,2020-02-17 12:54:15 UTC,"Reviewed:  https://review.opendev.org/707077
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a0bb5763b277d7360554fd64813fdce01244d2fa
Submitter: Zuul
Branch:    master"
1828423,2020-02-17 12:57:52 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/708122"
1828423,2019-05-20 12:02:25 UTC,Hi:
1828423,2019-05-22 05:31:56 UTC,"Rodolfo, thx for detailed analysis of this issue.
I agree that we should handle correctly ports added to the cache when the network is created"" as You said. But isn't it what https://review.opendev.org/#/c/658307/ is doing? What else You would like to do here instead of just better checking if cache is out of sync?"
1828423,2020-02-19 03:35:53 UTC,"Reviewed:  https://review.opendev.org/708122
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e894904a7d8dbb0e01d9c4d18b524de4b436ead3
Submitter: Zuul
Branch:    stable/train"
1828423,2019-10-08 16:00:43 UTC,This fix helps and removes the semaphore that was present in the prior code but it is not fixing the root cause of the problem unfortunately.
1828423,2020-02-11 08:08:50 UTC,"Similar to my comment https://bugs.launchpad.net/neutron/+bug/1862315/comments/3 - if IP is reused quickly, we may get such ""Duplicate IP addresses"" messages due to lower priority of port delete events than port create events."
1828423,2020-02-11 08:27:46 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/707077"
1828423,2019-05-22 16:00:27 UTC,Hi Slaweq:
1828424,2020-02-11 11:37:26 UTC,"Reviewed:  https://review.opendev.org/705864
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=bc96662b42676e79dd6577149d385b1314bacdcf
Submitter: Zuul
Branch:    master"
1828424,2020-02-27 17:08:01 UTC,"Reviewed:  https://review.opendev.org/694566
Committed: https://git.openstack.org/cgit/openstack/charm-manila/commit/?id=b7b55b3a348123ffc69927f88488cef67e3868be
Submitter: Zuul
Branch:    master"
1828424,2020-03-06 08:30:06 UTC,"Reviewed:  https://review.opendev.org/684382
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer/commit/?id=bbf4ad60ddf0a00f1126c285219c49745d51d92e
Submitter: Zuul
Branch:    master"
1828424,2020-03-09 10:38:57 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/711892"
1828424,2020-03-12 12:43:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/712671"
1828424,2020-03-12 14:34:23 UTC,"Reviewed:  https://review.opendev.org/711892
Committed: https://git.openstack.org/cgit/openstack/charm-gnocchi/commit/?id=54bfb99b8f5ab26e34b795822edb8185975d56c7
Submitter: Zuul
Branch:    master"
1828424,2020-03-12 15:55:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/712720"
1828424,2020-03-13 15:29:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/712974"
1828424,2020-03-13 15:38:04 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/712980"
1828424,2020-04-02 06:21:59 UTC,"Reviewed:  https://review.opendev.org/712974
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=6923e7247e6e69bebda8b003a9283d33b3b13cac
Submitter: Zuul
Branch:    master"
1828424,2020-04-02 09:43:22 UTC,"Reviewed:  https://review.opendev.org/712720
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=e6338552ece8e2a6098462dcfdf60be55f3cb015
Submitter: Zuul
Branch:    master"
1828424,2020-04-03 08:03:57 UTC,charm-cinder-ceph review: https://review.opendev.org/#/c/715456/
1828424,2020-04-06 17:41:57 UTC,charm-nova-compute review: https://review.opendev.org/619763
1828424,2020-04-15 12:02:46 UTC,"Reviewed:  https://review.opendev.org/619763
Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=8490919e2fdf529e1a5d1d7a54b6fbf1d4507c67
Submitter: Zuul
Branch:    master"
1828424,2020-04-17 08:20:13 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/720658"
1828424,2020-04-20 12:47:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/721261"
1828424,2020-04-21 07:44:27 UTC,"Reviewed:  https://review.opendev.org/720658
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=c4eaed25f2a59485eaeea8723473c98a89c11397
Submitter: Zuul
Branch:    master"
1828424,2020-04-27 14:29:10 UTC,"Reviewed:  https://review.opendev.org/721261
Committed: https://git.openstack.org/cgit/openstack/charm-barbican/commit/?id=cccfdc343a337c5a9899620423bfec4265d80b54
Submitter: Zuul
Branch:    master"
1828424,2020-05-05 16:02:58 UTC,"Reviewed:  https://review.opendev.org/712980
Committed: https://git.openstack.org/cgit/openstack/charm-designate-bind/commit/?id=c43f159f37ebe203ca18d73c157b209898a87b3b
Submitter: Zuul
Branch:    master"
1828424,2020-05-12 12:12:10 UTC,"Reviewed:  https://review.opendev.org/712671
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-backup/commit/?id=f5eacbd0c91e70b9e9556276203b768d74430c2d
Submitter: Zuul
Branch:    master"
1828424,2020-05-20 09:14:31 UTC,"Reviewed:  https://review.opendev.org/715456
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=c0f870c4ff52d20ca326b592be147a28facd50fa
Submitter: Zuul
Branch:    master"
1828424,2020-06-17 11:57:13 UTC,"Reviewed:  https://review.opendev.org/734703
Committed: https://git.openstack.org/cgit/openstack/charm-manila-generic/commit/?id=03f69d3e8ed29cd2fa782ad9ae74da86eb322e2b
Submitter: Zuul
Branch:    master"
1828424,2020-02-11 11:36:34 UTC,"Reviewed:  https://review.opendev.org/705726
Committed: https://git.openstack.org/cgit/openstack/charm-designate-bind/commit/?id=6b514da320c7a1bab273440cea5af5b4720c0a02
Submitter: Zuul
Branch:    master"
1828424,2020-02-04 23:00:18 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/705864"
1828424,2020-03-06 08:34:22 UTC,"Reviewed:  https://review.opendev.org/711051
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=31fe0059f26697aec4678ca5fda5d6d3a9782b1e
Submitter: Zuul
Branch:    master"
1828424,2020-02-03 21:41:59 UTC,"Reviewed:  https://review.opendev.org/703696
Committed: https://git.openstack.org/cgit/openstack/charm-keystone-ldap/commit/?id=1549f44cc6c49a8608d40aabeab023acacbc9d82
Submitter: Zuul
Branch:    master"
1828424,2019-05-16 11:51:14 UTC,"Reviewed:  https://review.opendev.org/656634
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=01fb37ebeedd582e25e518be939346e8bd1d3313
Submitter: Zuul
Branch:    master"
1828424,2019-05-30 16:35:55 UTC,"Reviewed:  https://review.opendev.org/659548
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-proxy/commit/?id=8e08a9c22a41b8df5ddfdb662a2dc9d0965bcfaf
Submitter: Zuul
Branch:    master"
1828424,2019-06-05 12:57:37 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/663313"
1828424,2019-06-26 15:14:20 UTC,"Reviewed:  https://review.opendev.org/663313
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=05f373a27b3a5acfa1a8bff738bbcf4e812ab307
Submitter: Zuul
Branch:    master"
1828424,2020-02-04 16:10:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/705726"
1828424,2019-09-11 14:36:43 UTC,"Reviewed:  https://review.opendev.org/679599
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=35beb586dadd54c1b7a1917b2ae73f4cb517eecf
Submitter: Zuul
Branch:    master"
1828424,2019-09-12 18:13:34 UTC,"Reviewed:  https://review.opendev.org/680903
Committed: https://git.openstack.org/cgit/openstack/charm-glance-simplestreams-sync/commit/?id=660ce5b0217342237fde30ca075c60644655710c
Submitter: Zuul
Branch:    master"
1828424,2019-09-24 15:37:01 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/684382"
1828424,2019-09-30 01:05:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/685631"
1828424,2019-10-07 15:07:56 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/687074"
1828424,2019-10-10 14:39:18 UTC,"Reviewed:  https://review.opendev.org/687074
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-backup/commit/?id=478cda6ad61278fbec54a5ec2a5ac03ea61ff75c
Submitter: Zuul
Branch:    master"
1828424,2019-10-15 15:51:37 UTC,"Reviewed:  https://review.opendev.org/683846
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=466ab245578406479e30072a3dcd4c223f3485ef
Submitter: Zuul
Branch:    master"
1828424,2019-09-09 03:32:36 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680903"
1828424,2019-10-25 09:53:44 UTC,"Reviewed:  https://review.opendev.org/690596
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=830c3b2dd2e543b1a57dee7b9ac6b34cb341288e
Submitter: Zuul
Branch:    master"
1828424,2019-10-23 14:53:18 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/690596"
1828424,2020-01-31 22:58:15 UTC,"Reviewed:  https://review.opendev.org/685631
Committed: https://git.openstack.org/cgit/openstack/charm-ceilometer-agent/commit/?id=72107bc963af334840eddd9638d821b408018db8
Submitter: Zuul
Branch:    master"
1828424,2020-01-21 21:08:10 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/703696"
1828424,2020-01-16 00:26:59 UTC,"Reviewed:  https://review.opendev.org/700659
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=b3930738fb002c08b260b7ed95e61849f9432460
Submitter: Zuul
Branch:    master"
1828424,2019-12-26 23:36:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/700659"
1828424,2020-03-03 16:28:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/711051"
1828424,2019-12-19 11:41:20 UTC,"Reviewed:  https://review.opendev.org/696878
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-fs/commit/?id=4dfe62d344c2b1df4d33a22533b9347bf1226e5c
Submitter: Zuul
Branch:    master"
1828424,2019-12-18 07:29:48 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/699572"
1828424,2019-12-12 23:37:16 UTC,"Reviewed:  https://review.opendev.org/698189
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-gateway/commit/?id=6806db670befd48408287da55777c4a9079db000
Submitter: Zuul
Branch:    master"
1828424,2019-11-15 15:00:23 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/694566"
1828424,2019-10-31 14:22:17 UTC,"Reviewed:  https://review.opendev.org/691445
Committed: https://git.openstack.org/cgit/openstack/charm-heat/commit/?id=4e29bc37d71f18ed2fc703a61cdb45efc9b807f3
Submitter: Zuul
Branch:    master"
1828424,2019-12-19 23:34:14 UTC,"Reviewed:  https://review.opendev.org/699572
Committed: https://git.openstack.org/cgit/openstack/charm-hacluster/commit/?id=df5f114ae1aad11d236772f6b9d832f3baf9e338
Submitter: Zuul
Branch:    master"
1828425,2019-05-09 16:34:12 UTC,"It's triggered by the description having a line with an indent of 140+ spaces, which is rather pathological and tickled a bug."
1828427,2019-07-01 08:01:57 UTC,This bug was fixed in the package netbeans - 10.0-3ubuntu2~18.04.1
1828427,2019-07-01 08:00:52 UTC,"The verification of the Stable Release Update for netbeans has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828427,2019-06-18 21:09:52 UTC,"I have verified netbeans 10.0-3ubuntu2~18.04.1 from -proposed on 3 releases: bionic, cosmic, and disco; the fix works on all of them and I now can successfully create a java application using the Wizard."
1828427,2019-06-13 17:03:19 UTC,"Hello Tiago, or anyone else affected,"
1828427,2019-05-21 22:24:41 UTC,This bug was fixed in the package netbeans - 10.0-3ubuntu2
1828427,2019-06-13 17:04:13 UTC,"Hello Tiago, or anyone else affected,"
1828427,2019-06-13 16:18:10 UTC,"Hello Tiago, or anyone else affected,"
1828432,2019-05-24 09:39:29 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read ""How to report bugs effectively"" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem."
1828432,2019-05-24 09:40:35 UTC,Sorry copied on the wrong bug
1828432,2019-07-06 11:41:39 UTC,"Dear all, I seem to have the same problem. Will try to post a backtrace, but for now this may be a first step:"
1828432,2019-09-05 04:17:17 UTC,[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.]
1828433,2019-06-06 16:08:05 UTC,The reason is that the TexMaths version packages here is very old. Maintainers should upgrade to TexMaths 0.47 or above. Thanks.
1828437,2020-06-21 06:46:45 UTC,"Reviewed:  https://review.opendev.org/733112
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dc655cabcb9c21637029f864887901a3d85ce0f1
Submitter: Zuul
Branch:    master"
1828437,2020-06-03 11:27:00 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/733112"
1828437,2019-05-24 18:31:36 UTC,"Reviewed:  https://review.opendev.org/660654
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=079de324ab21bea96875c3d71eda268ec72430fa
Submitter: Zuul
Branch:    master"
1828437,2019-05-09 16:56:55 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658155"
1828437,2019-10-05 05:33:15 UTC,"Reviewed:  https://review.opendev.org/658155
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=db3001a7a2fe038704f1f74667f0019f833ba867
Submitter: Zuul
Branch:    master"
1828437,2019-05-22 10:34:29 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/660654"
1828438,2019-05-10 03:39:39 UTC,"Commit 55237a5f has already been applied in Bionic kernel,
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=02f4976643b29ebe7d93e79cd468cd41442af560"
1828438,2019-05-09 16:30:07 UTC,This change was made by a bot.
1828440,2019-12-04 15:22:33 UTC,"Reviewed:  https://review.opendev.org/696385
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=2e46deeaa109f46686171e9af6ea12e94eb9e1f7
Submitter: Zuul
Branch:    stable/queens"
1828440,2019-12-04 04:53:32 UTC,"Reviewed:  https://review.opendev.org/697133
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=34a3ca23b3184e9b356877432d0f44c836705a70
Submitter: Zuul
Branch:    stable/rocky"
1828440,2019-12-03 16:46:28 UTC,"Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/697133"
1828440,2019-11-27 18:33:02 UTC,"Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/696385"
1828440,2019-11-20 16:09:02 UTC,"Reviewed:  https://review.opendev.org/694890
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=8933503041529978b9fd816e1788b1b0c343b540
Submitter: Zuul
Branch:    stable/stein"
1828440,2019-11-19 02:28:09 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/694890"
1828440,2019-11-14 03:56:41 UTC,"Reviewed:  https://review.opendev.org/690640
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=708733e49598145eb8e898d486723dc3df00a52f
Submitter: Zuul
Branch:    master"
1828440,2019-10-24 14:30:47 UTC,This issue was fixed in the openstack/os-brick 2.3.9 release.
1828440,2019-10-23 17:06:56 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/690640"
1828440,2019-11-18 22:17:52 UTC,"Reviewed:  https://review.opendev.org/694314
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=c76b6dc514b8e17e1211e4a7465a7e2a635adea3
Submitter: Zuul
Branch:    stable/train"
1828440,2019-07-11 09:36:29 UTC,This issue was fixed in the openstack/os-brick 2.5.8 release.
1828440,2019-07-11 16:18:57 UTC,"Reviewed:  https://review.opendev.org/668567
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=66d9d2a908e9baeb36662a149c24c887bbd6ba2b
Submitter: Zuul
Branch:    stable/queens"
1828440,2019-05-09 16:56:27 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658154"
1828440,2019-06-12 15:41:31 UTC,"Reviewed:  https://review.opendev.org/658154
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=70899a9aa3e4bdd3f1b1a7024807390cd55c4958
Submitter: Zuul
Branch:    master"
1828440,2019-06-17 10:33:21 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/665641"
1828440,2019-06-21 17:07:27 UTC,"Reviewed:  https://review.opendev.org/665641
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=1ee6acb509910d7de1213fb71cd0d6166991609a
Submitter: Zuul
Branch:    stable/stein"
1828440,2019-11-14 14:41:58 UTC,"Related fix proposed to branch: stable/train
Review: https://review.opendev.org/694314"
1828440,2019-07-02 00:58:57 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/668567"
1828440,2019-07-08 17:46:23 UTC,"Reviewed:  https://review.opendev.org/667507
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=64cbaaea47822dff3ae5fbd104f9bff8fe79d08d
Submitter: Zuul
Branch:    stable/rocky"
1828440,2019-07-11 09:19:32 UTC,This issue was fixed in the openstack/os-brick 2.9.1 release.
1828440,2019-07-11 09:31:39 UTC,This issue was fixed in the openstack/os-brick 2.8.2 release.
1828440,2019-06-26 04:55:23 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/667507"
1828442,2019-05-25 02:12:17 UTC,"Fixed in revision 52a9e68093a5e857e63f87ffe57b0d37f5081d3c
https://git.launchpad.net/kicad/patch/?id=52a9e68093a5e857e63f87ffe57b0d37f5081d3c"
1828442,2019-05-09 17:16:07 UTC,"This threw me for a loop today.
I had moved a 40 pin header out of the way to see underneath for a sec, and it changed a bunch of vias in a critical subcircuit.
A simple undo moved the header back, but the via nets remain changed."
1828444,2019-05-09 17:30:51 UTC,"This should not be done just Adhoc, we should determine exactly what we want it to filter by and have it match how the UI will be filtered."
1828444,2019-05-10 08:37:34 UTC,"I agree it shouldn't be done ad-hoc. To do it properly, we should go in the direction of a more REST-y API, where we don't expand all the properties of an object, but rather have refs to related objects.
In this case, for instance, instead of including the VLAN/fabric info in the machine result, we'd have a ref pointing at a VLAN/fabric ID.
At that point it'd be easier to have generic filters that could take a value for any direct attribute of a machine, including VLAN/fabric ID (or pool, zone, domain, ...).
The same would apply to simple attribugtes like the hostname"
1828444,2019-05-10 14:12:58 UTC,Agreed. So this bug is only to address part of the things we would need to improve the API on. So these three things would be:
1828448,2019-05-10 18:41:51 UTC,Marking as release gating; this would cause confusion for operators using non-UTC timezone
1828448,2019-05-15 19:22:45 UTC,Another issue related to the same bug can be reproduce with this scenario
1828448,2019-05-31 14:17:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/662477"
1828448,2019-06-03 18:01:37 UTC,"Reviewed:  https://review.opendev.org/662477
Committed: https://git.openstack.org/cgit/starlingx/fault/commit/?id=e5803f2a5d3e9567f830b75c711d7d5f0dde629b
Submitter: Zuul
Branch:    master"
1828452,2019-05-10 15:25:40 UTC,"Thanks Bot,"
1828452,2019-05-09 20:26:17 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1828453,2019-06-21 12:28:16 UTC,Assigned to Bruce for re-assignment.
1828453,2019-08-01 17:23:25 UTC,"Reviewed:  https://review.opendev.org/673934
Committed: https://git.openstack.org/cgit/starlingx/fault/commit/?id=5e4774768b81389ac33c9d5c50ccdc0c056d8f42
Submitter: Zuul
Branch:    master"
1828453,2019-08-01 01:44:45 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/673934"
1828453,2019-07-30 13:48:32 UTC,Any update on your test result with and without the patch? Will you be able to fix this within stx-2.0 time frame?
1828453,2019-05-10 18:40:27 UTC,Marking as release gating; events missing for operators using snmp
1828453,2019-07-18 13:34:34 UTC,"What further information is required? There are steps documented in the bug to reproduce and a potential patch offered as solution, can you please elaborate what are you waiting for?
When you tried to reproduce you saw the traps in customer event logs?"
1828453,2019-07-08 22:02:46 UTC,"Attempt to replicate on a Duplex, waiting for further information."
1828453,2019-06-25 17:42:30 UTC,"This patch needs to be tested, but it should resolve the issue."
1828453,2019-07-18 15:25:19 UTC,"More details were requested for reproducing, information was received. Now working on reproducing and applying patch."
1828454,2019-05-09 18:56:08 UTC,Mo [french] = Mega octets [french] = Mega Bytes [english]
1828454,2019-05-10 13:05:07 UTC,"The issue is upstream as well
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/master/po/fr.po"
1828454,2019-05-11 09:16:06 UTC,How can it be “Fix Committed” when the upstream file at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/master/po/fr.po still has the wrong translation?
1828454,2019-05-11 16:16:45 UTC,"@Alexandre: It's about to be fixed in Ubuntu's language pack, but you are right, it's not yet dealt with in the network-manager package, neither in Ubuntu nor upstream. It would be good if someone could submit an upstream merge request."
1828454,2019-05-09 18:30:27 UTC,Thanks for reporting.
1828455,2019-05-27 11:51:20 UTC,Proposed: https://github.com/juju/juju/pull/10235
1828455,2019-08-05 13:27:57 UTC,Related: https://bugs.launchpad.net/juju/+bug/1831450
1828455,2019-05-14 15:07:55 UTC,Ooh short ones is bonus awesome
1828455,2019-05-14 12:03:53 UTC,Seems ok to me if it's not creating any issues.
1828455,2019-05-14 11:20:51 UTC,"Should we also allow ""juju switch"" to accept a UUID?"
1828455,2019-05-10 20:11:28 UTC,One note is that the controller call show-model doesn't accept a -m (since the model is a required arg) and would also need to match up appropriately.
1828455,2019-05-14 12:19:56 UTC,"I think it is just a case of ""where we take a model name, allow it to be a
model uuid"". Arguably we also would support short hash prefix of uuid. (eg
first 6-8 characters). I believe we've been using first 6 in log messages."
1828456,2019-05-15 18:24:02 UTC,Working branch user/jeffdavis/lp1828456-authproxy-native-login-method makes AuthProxy use open-ils.auth.login for native login:
1828456,2019-09-24 18:44:22 UTC,Note that there is a bug in open-ils.auth.login for some password values (bug 1830642); that bug has a pullrequest but a concern was raised about backporting the fix to maintenance releases. Probably both bugfixes should be released together.
1828456,2021-02-11 23:29:24 UTC,"Just to confirm - This involves being able to log in to the staff client under said conditions, correct? If so, I'm seeing no issues with the supplied branch on the festivus feedback fest server when trying to log in as the noted account set up to test this bug."
1828456,2021-02-12 00:21:01 UTC,"With this branch, login ought to work for both the staff client and the OPAC, assuming (1) auth_proxy is enabled, (2) you have a working authentication proxy that includes your test user's credentials, and (3) your authenticator config in opensrf.xml includes both ""staff"" and ""opac"" (or ""all"") under login_types."
1828456,2021-02-12 14:48:56 UTC,"To confirm: festivus does have auth_proxy enabled but is only using native auth (since native auth is what this branch is intended to fix). Jeff is right that bug 1827296 will still be an issue in the opac, which should probably also drop the init / complete login method and use open-ils.auth.login."
1828458,2019-05-15 15:52:42 UTC,I took some more time to poke at this a few days ago. It seems like the issue stems more from the collocation of services than an actual issue with the memcached or nova services alone. Launching memcached in a container using xenial alongside the cloud results in an accessible console where deploying the same configuration collocated does not. Closing this bug as we should be running these things in containers regardless.
1828458,2019-05-10 14:49:38 UTC,There's a simpler repro case. Simple deploy the charmstore memcached bundle with repached set to true:
1828458,2019-05-09 20:26:00 UTC,"Able to reproduce in my lab with the attached bundle, which rules out issues with bindings as this is a single-network installation."
1828458,2019-05-10 14:50:38 UTC,repcached is a fork of memcached with replication enabled. There is a newer ppa that supports xenial. Deploy w/ the following config file to get a working repcached:
1828459,2019-05-09 19:52:46 UTC,That's a case of being way too close to the code base.  Has it always been this way and if so how did that get missed?
1828459,2019-05-16 16:53:29 UTC,Apparently the janitor didn't pick this up.  The commit in master is https://git.launchpad.net/kicad/commit/?id=6f27ef7f663a0cdaaa355e62de66fa71f11cadc2.
1828461,2019-05-17 14:49:33 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828462,2019-08-01 10:10:40 UTC,"Please use the latest one, it works fine for gnome-3.28."
1828462,2019-08-01 09:58:44 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828462,2019-08-01 10:03:45 UTC,"$ dpkg -l  | grep gnome-shell
ii  gnome-shell                                3.28.4-0ubuntu18.04.1                        amd64        graphical shell for the GNOME desktop
ii  gnome-shell-common                         3.28.4-0ubuntu18.04.1                        all          common files for the GNOME graphical shell
ii  gnome-shell-extension-appindicator         18.04.1                                      all          App indicators for GNOME Shell
ii  gnome-shell-extension-move-clock           1.01-1                                       all          move clock extension for GNOME shell
ii  gnome-shell-extension-ubuntu-dock          0.9.1ubuntu18.04.3                           all          Ubuntu Dock for GNOME Shell"
1828462,2019-08-01 09:59:27 UTC,"After debug, I found below error."
1828463,2019-05-21 11:41:06 UTC,"This applies not only to the dark green menu, but also drop-down menus (see the attachment)."
1828463,2019-05-23 17:00:16 UTC,I've also had some feedback that it is easy to lose your place when editing a MARC record
1828463,2019-05-24 21:11:22 UTC,I strongly agree that the contrast of the active field in the Marc editor should be much greater than it is now (the green background in XUL client used to be helpful).
1828463,2019-05-24 21:12:32 UTC,"I have another comment from our staff - not related exactly to focus but to the contrast of the interface:
Some staff pointed, that it is hard to see, which card in the MARC record is currently being used; they would like the active card to be more distinctly distinguished than just by the gray frame (see the attachment)."
1828464,2019-06-03 19:26:08 UTC,What is the output of the following?
1828464,2019-08-03 04:17:27 UTC,[Expired for gnome-shell-extension-show-ip (Ubuntu) because there has been no activity for 60 days.]
1828466,2019-05-11 00:11:38 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828466,2020-10-17 02:38:32 UTC,Still happening in focal dub: symbol lookup error: dub: undefined symbol: _D3std3net4curl4HTTP9__mixin376onSendMFNdDFAvZmZv
1828468,2019-05-09 21:18:21 UTC,It might also be nice to be able to use the left and right arrows to move between menus.
1828468,2019-05-09 21:39:02 UTC,The menu also does not allow you to collapse a menu to go backwards and forwards through the menu system.
1828468,2019-05-09 21:53:07 UTC,"Updating to ng-bootstrap 4.1.0 or later should help with this, as that adds the ngbDropdownItem directive to specify that a dropdown menu item should be keyboard navigable."
1828469,2019-05-10 10:12:37 UTC,apport information
1828469,2019-05-21 16:48:30 UTC,"Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.2-rc1 kernel [0]."
1828469,2019-05-21 16:49:05 UTC,Please see if `noapic` can be removed on mainline kernel.
1828469,2020-02-25 04:17:25 UTC,[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
1828469,2019-05-23 10:39:53 UTC,dmesg running Linux 5.2.0-050200rc1-generic #201905191930 SMP Sun May 19 23:34:37 UTC 2019
1828469,2019-07-09 14:35:36 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1835040-2/"
1828469,2019-12-27 03:38:42 UTC,Mark as Incomplete as per request in comment #21
1828469,2019-05-10 10:12:36 UTC,apport information
1828469,2019-05-23 10:35:22 UTC,"No difference (5.2 kernel). Unfortunately it still needs ""noapic"". :-( Can this be the heart of the problem?"
1828469,2019-05-10 10:12:35 UTC,apport information
1828469,2019-05-10 10:12:30 UTC,apport information
1828469,2019-05-10 10:12:32 UTC,apport information
1828469,2019-05-10 10:12:31 UTC,apport information
1828469,2019-05-10 10:12:29 UTC,apport information
1828469,2019-05-10 10:12:28 UTC,apport information
1828469,2019-05-10 10:12:26 UTC,apport information
1828469,2019-05-10 10:12:25 UTC,apport information
1828469,2019-05-10 10:12:24 UTC,apport information
1828469,2019-05-10 10:12:23 UTC,apport information
1828469,2019-05-10 10:12:21 UTC,apport information
1828469,2019-05-09 21:00:12 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828469,2019-05-10 10:12:34 UTC,apport information
1828470,2019-09-17 21:13:26 UTC,"Reviewed:  https://review.opendev.org/682619
Committed: https://git.openstack.org/cgit/starlingx/utilities/commit/?id=2e7d2550b9c64a33910a567c3433a12f3e68f25a
Submitter: Zuul
Branch:    master"
1828470,2019-09-17 11:15:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/682619"
1828470,2019-09-16 20:55:34 UTC,"Reviewed:  https://review.opendev.org/682472
Committed: https://git.openstack.org/cgit/starlingx/utilities/commit/?id=613276c944504b972a38dec3618137ea81dc0dc9
Submitter: Zuul
Branch:    master"
1828470,2019-09-16 19:55:49 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/682472"
1828470,2019-09-16 16:36:46 UTC,"Reviewed:  https://review.opendev.org/680920
Committed: https://git.openstack.org/cgit/starlingx/utilities/commit/?id=9f73cd4f9bf4a8f284642b7940ac41d22b637d3e
Submitter: Zuul
Branch:    master"
1828470,2019-09-09 06:57:05 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680920"
1828470,2019-09-09 06:55:02 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/680915"
1828470,2019-05-29 08:23:01 UTC,change to Low as this is not stx.2.0 gating according to last week's bug triage.
1828470,2019-05-23 09:22:27 UTC,Created upstream bug https://tracker.ceph.com/issues/40013
1828470,2019-05-09 21:17:14 UTC,To retrieve ceph-mgr restful plugin self-signed certificate:
1828470,2019-05-09 21:07:21 UTC,To confirm urllib3.disable_warnins is not called without relying on log messages:
1828470,2019-09-11 16:36:17 UTC,"Reviewed:  https://review.opendev.org/680915
Committed: https://git.openstack.org/cgit/starlingx/integ/commit/?id=fcaa49ecaf002b97e450cb9e8d41b9d2c2094d67
Submitter: Zuul
Branch:    master"
1828473,2019-07-24 11:33:31 UTC,"Reviewed:  https://review.opendev.org/670691
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=00df9b0a853313ac2c58772e363099192e3dca4d
Submitter: Zuul
Branch:    stable/rocky"
1828473,2019-10-22 19:56:29 UTC,This issue was fixed in the openstack/neutron 12.1.1 release.
1828473,2019-10-22 19:53:29 UTC,This issue was fixed in the openstack/neutron 13.0.5 release.
1828473,2019-10-22 19:45:18 UTC,This issue was fixed in the openstack/neutron 14.0.3 release.
1828473,2019-09-19 10:13:54 UTC,This issue was fixed in the openstack/neutron 15.0.0.0b1 development milestone.
1828473,2019-07-23 18:52:12 UTC,"Reviewed:  https://review.opendev.org/670682
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=431ba12873c358260b1275470916ca2d3544a3dd
Submitter: Zuul
Branch:    stable/stein"
1828473,2019-07-13 09:47:30 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/670691"
1828473,2019-07-13 09:47:50 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/670692"
1828473,2019-05-10 02:36:47 UTC,It does seem like this should work correctly.  Let me throw something up to see how it behaves in testing.
1828473,2019-07-13 04:47:12 UTC,we also observe an excessive amount of same logs....
1828473,2019-07-13 04:45:50 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/670682"
1828473,2019-05-17 01:36:15 UTC,"Reviewed:  https://review.opendev.org/658240
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=09ee9347864d731ce7ccf241178559815e82f57c
Submitter: Zuul
Branch:    master"
1828473,2019-05-10 02:37:53 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658240"
1828473,2019-07-23 17:55:15 UTC,"Reviewed:  https://review.opendev.org/670692
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7ec7fd8fdf4dae028469b644c922cc47e8a6eab1
Submitter: Zuul
Branch:    stable/queens"
1828474,2019-05-10 00:38:33 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1828475,2020-10-02 04:17:17 UTC,[Expired for Ubuntu MATE because there has been no activity for 60 days.]
1828477,2019-05-10 15:31:16 UTC,"It was simple <ctrl>+d in some block. The <esc> wasn't cancelling.
But in t today's Nightly ""6.0.0-unknown-589a37b~86~ubuntu16.04.1, release build"" it's fine."
1828477,2019-05-10 15:10:00 UTC,"@Hildo, can you give specific steps?  There have been some changes here so it might be fixed, but I never reproduced it so I'm not sure...."
1828480,2019-05-09 22:53:14 UTC,Can reproduce in 5.1.2 but not in master. Maybe related to https://bugs.launchpad.net/kicad/+bug/1821268 ?
1828480,2019-05-09 22:56:00 UTC,Correction: I can reproduce this in both 5.1.2 and master for the *symbol editor* properties dialog. Is that what you originally meant @Leandro?
1828480,2019-05-10 00:21:22 UTC,"Yes. Thats it. Michael, look this video, this window is kinda wierd."
1828480,2019-05-11 08:58:07 UTC,I think a fix was just committed for this:
1828480,2019-05-09 22:26:36 UTC,"Application: kicad
Version: 5.1.2-f72e74a~84~ubuntu19.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.8.6/openssl/zlib nghttp2/1.36.0 librtmp/2.3
Platform: Linux 5.0.0-13-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: GCC 8.3.0 with C++ ABI 1013"
1828481,2019-05-10 14:47:45 UTC,<janitor hat>
1828482,2019-05-16 17:28:47 UTC,"As discussed with Al, this is not reproducible. Closing."
1828482,2019-05-13 16:51:24 UTC,"If ansible encountered a problem during setup, then that would explain the missing config file, however the logs for ansible and puppet are not included in this bug report."
1828482,2019-05-13 17:38:30 UTC,I'll try to reproduce with the latest ISO.
1828482,2019-05-10 18:34:06 UTC,"Marking as release gating; this would impact initial config of the system.
Unsure if the issue is reproducible or not. Further investigation is required."
1828482,2019-05-14 18:21:27 UTC,The /etc/kubernetes/admin.conf is created when the following bootstrap task is executed:
1828483,2019-05-21 12:33:17 UTC,libwww-perl needs to Recommend libio-socket-ssl-perl then.
1828483,2019-06-15 12:18:11 UTC,I cannot reproduce this bug since:
1828485,2019-05-10 08:47:49 UTC,Please set back to new if you find the steps needed to reproduce this.
1828485,2019-07-10 04:17:22 UTC,[Expired for KiCad because there has been no activity for 60 days.]
1828487,2019-05-10 10:59:34 UTC,"Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a ""regular"" (non-security) bug.  I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find."
1828489,2019-06-14 15:58:18 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828491,2019-05-10 03:21:59 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828491,2019-05-10 05:55:27 UTC,"Thank you for your bug report, indeed upstream removed that mimetype association because it would lean gnome-calendar to claim it can handle ics files which is not the case..."
1828491,2020-04-29 10:48:58 UTC,still not working at 20.04
1828494,2020-06-02 15:50:03 UTC,"'routers_max' can be an alternative scheduling mechanism of the case, but it does not hit the main point of the L3 resource usage, aka bandwidth of L3 IPs. But I'm OK to make that 'number of routers hosted by L3 agent' as a first step. I will update the spec."
1828494,2020-06-26 14:47:35 UTC,"We discussed that RFE once again in last drivers meeting: http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-06-26-14.00.log.html#l-54 and we decided to approve the RFE with ""routers_max"" parameter used to schedule routers.
Lets now discuss other details of this solution in the RFE and patch(es)."
1828494,2020-05-29 15:09:28 UTC,"@Liu we discussed this proposal once again on drivers team.
We would like to know what is Your opinion about proposal from comment #6 so base this scheduling simply on number of routers hosted by L3 agent instead of introducing new ""bandwidth"" parameter."
1828494,2020-03-13 08:52:52 UTC,"Ping Liu, are You still planing to work on this feature?"
1828494,2019-05-10 11:08:58 UTC,"@Slawek,
Thanks for the feedback. I know quota. But for a public cloud, the user (tenant) may be free to register. Then they will have some free quota. The unrestricted growth of tenant number will let the router number or any other free resource reach a unbearable number of cluster.
For the second, yes, a scheduling mechanism based on some physical resource will be needed, for intance physical NIC bandwidth ratio. LeastRoutersScheduler  can not work, since we do not have a maximum quantity for l3-agent. So router still is free to schedule to any l3-agent."
1828494,2019-05-26 17:54:16 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/661492"
1828494,2019-05-23 21:59:07 UTC,Please see comments that I left in the spec
1828494,2019-05-10 18:37:38 UTC,Spec proposed to: https://review.opendev.org/658451
1828494,2019-05-10 06:41:45 UTC,"First of all, to control number of resources used by tenants, there is quota mechanism. So it can be limited easily.
Second - is this rfe about adding new scheduler driver to https://github.com/openstack/neutron/blob/master/neutron/scheduler/l3_agent_scheduler.py ? Isn't LeastRoutersScheduler (https://github.com/openstack/neutron/blob/master/neutron/scheduler/l3_agent_scheduler.py#L344) something what You are describing here?"
1828494,2019-12-13 10:18:22 UTC,I read proposed spec again and I wonder if we can go with simpler solution like:
1828495,2019-08-06 06:05:35 UTC,"Thanks Rafael, I reviewed the MP, thanks for the fixup."
1828495,2019-08-05 22:19:17 UTC,I'll wait for the next SRU for bionic to be in -proposed to provide Bionic full verification just like I did to Disco. It shall not take too long and the version currently in -proposed will be superseded by the one we have in the merge request right now.
1828495,2019-08-05 22:17:44 UTC,# Disco verification:
1828495,2019-08-05 20:26:04 UTC,"Okay,"
1828495,2019-08-05 15:03:07 UTC,"Alright, working on it."
1828495,2019-07-16 21:23:21 UTC,"All autopkgtests for the newly accepted qemu (1:3.1+dfsg-2ubuntu3.3) for disco have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1828495,2019-08-02 22:26:03 UTC,"Hello Ai Lim,"
1828495,2019-07-24 14:55:56 UTC,"Hello Rafael,"
1828495,2019-07-23 11:14:07 UTC,I still have to check if default CascadeLake CPU with no flags will enable the features by default (should not) and verify Disco SRU. Unfortunately I have shutdown the remote machine (virsh console's fault :o) and will come back to this as soon as it is up again.
1828495,2019-07-23 11:12:52 UTC,## USING HOST CPU ONLY:
1828495,2019-07-22 20:05:27 UTC,I still need to verify this for the SRUs. There are no - up to now - regressions being showed in excuses for Disco and/or Bionic. Will provide verification soon.
1828495,2019-08-05 12:12:53 UTC,"@Ai Lim, it would be great to get your testing on the PPA asap."
1828495,2019-08-02 01:58:45 UTC,"Hello Ai Lim,"
1828495,2019-08-08 08:47:43 UTC,"The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828495,2019-08-06 11:45:26 UTC,From the MR:
1828495,2019-08-08 08:57:43 UTC,This bug was fixed in the package qemu - 1:3.1+dfsg-2ubuntu3.3
1828495,2019-08-13 00:43:51 UTC,"Hello Rafael,"
1828495,2019-08-13 15:50:02 UTC,This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.17
1828495,2019-08-20 08:51:14 UTC,"Recent libvirt versions (5.5) added more for arch_capabilities.
Lets get that into Eoan before considering the SRUs back to Bionic afterwards."
1828495,2019-08-20 08:55:46 UTC,"I started a test PPA [1] and an MP [2] to get this into Eoan.
@Rafael could you test this on the same system you used last time and review the MP?"
1828495,2019-08-20 11:46:16 UTC,Definitely! Will provide feedback soon!
1828495,2019-08-20 12:07:20 UTC,"Another bunch of related changes might be important.
Not sure how much of that will go into SRUs - I hope not all of it.
Already in Eoan we should try to use a reduced set or we could go directly to 5.5 which has other known issues."
1828495,2019-08-26 14:54:44 UTC,"Tests confirmed that the recent libvirt did in fact work fine.
FYI - this was analyzed in bug 1841066 which will also be the bug to track this little qemu addition which has to go alongside the libvirt portion of this once considering SRUs."
1828495,2019-08-27 08:36:52 UTC,"I was by accident changing the kernel task, fixed now."
1828495,2019-10-22 01:54:34 UTC,"@Christian,"
1828495,2019-10-22 05:31:02 UTC,"Hi Rafael,
thanks for giving it try. We knew it might be complex when we first saw the changes.
And I consider it wise to - at some point - step back and realize this won't be SRUable.
I'll summarize what we know about the libvirt portion of this:"
1828495,2019-10-22 11:22:31 UTC,"+1 on your summary, looks very good."
1828495,2019-10-22 13:36:15 UTC,For the Kernel Support:
1828495,2019-08-06 08:32:03 UTC,"Hello quanxian, or anyone else affected,"
1828495,2019-07-16 20:07:51 UTC,"All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.16) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1828495,2019-07-16 09:17:07 UTC,Tags pushed and uploaded to B/D unapproved for the SRU Team to do a final review and accept.
1828495,2019-07-16 17:08:34 UTC,"Hello quanxian, or anyone else affected,"
1828495,2019-07-16 17:17:56 UTC,"Hello quanxian, or anyone else affected,"
1828495,2019-05-10 02:11:43 UTC,Commit:2bdb76c015df7125783d8394d6339d181cb5bc30
1828495,2019-05-10 02:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828495,2019-05-10 18:49:32 UTC,List of commits needed to enable ARCH_CAPABILITIES:
1828495,2019-05-13 06:55:48 UTC,"The top three qemu patches are in qemu 4.0 which we plan as minimum for Ubuntu 19.10.
Tagging up to be part of the Qemu work in Ubuntu 19.10."
1828495,2019-06-03 15:25:36 UTC,This patch is also needed for kernels before 4.18
1828495,2019-06-11 02:31:41 UTC,WORKING
1828495,2019-06-11 02:32:16 UTC,"Sorry, last comment was posted 3 timex due to bad wrapping and mix of chars because of that. Fixed now, I've hidden 2 broken comments. Thanks"
1828495,2019-06-11 11:26:58 UTC,I just realized that from my previous comment I said:
1828495,2019-06-14 00:44:06 UTC,"### For the kernel team: This QEMU patchset basically adds 2 new CPU types (IceLake and CascadeLake) support to QEMU (i386/target/{pc,kvm}) AND creates those new CPU mitigations-query features in their structure, allowing QEMU to inform guest which mitigations should be in place for the vCPUs through its own MSRs."
1828495,2019-06-18 18:50:31 UTC,"Rafael - Is this completed for Bionic releases?
Thank you"
1828495,2019-06-21 14:14:15 UTC,"Alright, so we are still testing the version we're working on but here are some test results..."
1828495,2019-06-21 14:14:36 UTC,1) HOST (Bionic)
1828495,2019-06-21 14:14:58 UTC,2) OLD QEMU GUEST (Bionic)
1828495,2019-06-19 05:25:28 UTC,"Hi pragyansri,
If you track the progress on the merge proposal that is linked this looks good atm and will soon be in a PPA [2] with proposed changes for pre-evaluation with Bionic/Cosmic/Disco/Eoan."
1828495,2019-06-21 14:16:05 UTC,*) SUMMARY:
1828495,2019-07-16 13:19:47 UTC,"Some updates to libvirt:
- we already have ssbd/md-clear through security updates
- rdctl-no, ibrs-all, skip-l1dfl-vmentry, mds-no are part of
  c8ec678f  cpu_map: Introduce IA32_ARCH_CAPABILITIES MSR features
- arch_capabilities itself comes in 511df17a"
1828495,2019-07-11 06:05:41 UTC,"And qemu 4.0 is in Eoan, so this release is ""fix released"" (for the scope of adding the features, not the just discussed versioned CPUs)"
1828495,2019-07-11 05:29:09 UTC,"The series was merged in 3a1acf5d47295d22ffdae0982a2fd808b802a7da as a prep to qemu 4.1.
But the changes are rather invasive and after a review I think for the SRU we will not add them."
1828495,2019-06-21 14:15:19 UTC,3) NEW QEMU (w/ backport) GUEST: Bionic
1828495,2019-07-01 13:38:35 UTC,"Hello quanxian,"
1828495,2019-07-01 07:36:12 UTC,"we have verified that on 18.04.2 with Rafael David Tinoco (rafaeldtinoco)'s PPA qemy packages. And get that guest doesn't work as expected. After detailed discussion with Intel Upstream, there still needs some patches. But they are under review. Keep watch the process of process."
1828495,2019-06-25 15:25:49 UTC,https://<email address hidden>/msg626552.html
1828495,2019-07-02 02:23:43 UTC,"Expected results is:
HOST and Guest should enable IA32_ARCH_CAPABILITIES MSR.
MDS_NO is bit 5 of ARCH_CAPABILITIES. Expose this bit to guest."
1828495,2019-06-25 05:07:57 UTC,"> ssbd
> md-clear
> bpb
> ibrs-all
> rdctl-no
> rsba
> skip-l1dfl-vmentry
>
> I guess that we will have to backport this support in libvirt, in order
> to allow QEMU to pick specific CPU mitigation flags.
"
1828495,2019-06-24 16:02:56 UTC,"Alright. I had in mind that (for bionic/cosmic) but we definitely have to mention what you said (for started guests). About the migration, will cause the issue and report back after cosmic/disco backport."
1828495,2019-06-24 08:14:35 UTC,"This also affects ""Cascadelake-Server"" defined guests migrating from patched Bionic to unpatched Disco - that will fail. But requiring updates being applied is fine, only the enforced guest restart (which doesn't apply to the just mentioned use-case) is the thing that is really bad."
1828495,2019-06-24 08:12:23 UTC,"@rafaeldtinoco: I found some forther more ugly detail for the stepping change from 5 to 6.
Qemu 3.1 as in Disco had Cascade lake with the stepping 5.
So for Disco the SRU will change the definition.
Which is different to Bionic/Cosmic where we can say ""our Cascade definition will just always have been 6"" since it didn't exist before the SRU"
1828495,2019-06-21 14:23:36 UTC,TL;DR:
1828495,2019-06-25 05:26:49 UTC,"@rafael - One more question about Stepping 5/6.
I have formerly read your explanation that stepping 6 would be
required to be able to enable arch_capabilities.
And we planned to add all SRUs with stepping 6 right away and keep the
Delta to consider all versions to be stepping 6."
1828496,2019-07-17 19:53:56 UTC,Going over the details from comment #7
1828496,2020-04-23 08:35:24 UTC,Looks like HAProxy's 'hard-stop-after'[1] config might be the solution to this.
1828496,2020-03-15 07:08:41 UTC,"| haproxy:
|   Installed: 1.8.8-1ubuntu0.9
|   Candidate: 1.8.8-1ubuntu0.9
|   Version table:
|  *** 1.8.8-1ubuntu0.9 500
|         500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
|         500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
|         100 /var/lib/dpkg/status
"
1828496,2020-03-15 07:07:14 UTC,"Saw this elsewhere, on Bionic:"
1828496,2020-03-15 07:03:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828496,2019-10-07 04:17:13 UTC,[Expired for haproxy (Ubuntu) because there has been no activity for 60 days.]
1828496,2019-08-07 09:26:50 UTC,"Hi Paride, sorry for the late reply - summer holidays."
1828496,2019-07-15 13:48:24 UTC,"Hi Barry,"
1828496,2019-05-22 07:47:16 UTC,This is haproxy 1.6.3-1ubuntu0.2 on Xenial/16.04 running on amd64 hardware.
1828496,2019-07-12 06:12:39 UTC,Is there any new detail to the re-opening of the case?
1828496,2019-05-24 10:28:53 UTC,"Hi Barry,"
1828496,2019-05-24 07:48:03 UTC,"Never mind, here it is on Xenial:"
1828496,2019-05-23 18:16:24 UTC,"Note that there is a systemd wrapper process in xenial:
  411 ?        Ss     0:00 /usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid
  413 ?        S      0:00  \_ /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -Ds
  432 ?        Ss     0:00      \_ /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -Ds"
1828496,2019-05-23 09:55:18 UTC,"I'm marking this report a Incomplete for now, as we still miss some pieces of information needed to determine if this is actually a bug in Ubuntu. After providing them please change the bug status back to New, and we will look at it again. Thank you!"
1828496,2019-05-23 09:50:11 UTC,"Hi,"
1828496,2019-05-14 15:42:58 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1828496,2019-07-12 08:45:14 UTC,"It was marked Incomplete in #4, so there's new detail in #5, #7 and #8 - I just missed re-opening it until now."
1828500,2019-07-15 15:57:45 UTC,Maybe also useful: modifications to snap-tool to make it more resilient to connection failures of all sorts:
1828500,2019-07-16 12:24:18 UTC,"The attachment ""Backport for Bionic"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1828500,2019-07-16 15:33:10 UTC,"Hello Peter, or anyone else affected,"
1828500,2019-07-16 15:33:57 UTC,"Hello Peter, or anyone else affected,"
1828500,2019-07-16 17:53:06 UTC,"All autopkgtests for the newly accepted livecd-rootfs (2.578.6) for disco have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1828500,2019-07-16 17:58:57 UTC,Comment #27 is not correct.
1828500,2019-07-17 13:37:44 UTC,"I believe that comment #27 is correct, because after that the autopkgtests for ubuntu-image succeeded (triggered by a qemu update) using the previous revision of livecd-rootfs on disco. But I'm not able to tell how the changes made to livecd-rootfs affect the operation/testing of ubuntu-image."
1828500,2019-07-18 09:52:21 UTC,"I have verified (bionic 2.525.28 and disco 2.578.6) that the changes to snap_preseed do not break existing functionality and that an error is thrown when the helper _snap_preseed is called with an invalid snap name, resulting in snap-info failing to retrieve the base."
1828500,2019-07-17 15:31:16 UTC,It passed now.
1828500,2019-07-18 07:29:42 UTC,FYI: Comment #8 (with comment #5) fixed the problem for me :-)
1828500,2019-07-25 19:43:08 UTC,This bug was fixed in the package livecd-rootfs - 2.525.28
1828500,2019-07-25 19:43:16 UTC,"The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828500,2019-09-16 07:33:29 UTC,This bug was fixed in the package livecd-rootfs - 2.578.7
1828500,2019-07-15 10:34:53 UTC,Just as a heads up: the seed.yaml for the azure image also need gnome-3-28-1804 in the seed. The `snap debug validate-image` will validate all this once its landed so hopefully this will at least be easy to detect fix (build-time instead of runtime).
1828500,2019-07-17 14:02:10 UTC,"I should have been more explicit. When I wrote comment #28, the tests *had not finished running yet* so it was false at that point."
1828500,2019-07-15 07:37:27 UTC,Thanks everyone!
1828500,2019-07-15 05:54:44 UTC,My mistake that I didn't do proper error checking while determining the base of a snap. This here
1828500,2019-07-12 22:01:27 UTC,I ran the following test on the current version of livecd-rootfs for Bionic:
1828500,2019-05-13 09:39:47 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828500,2019-05-13 14:57:28 UTC,"'systemd-analyze blame' suggests to run 'systemctl list-jobs', this is its output:"
1828500,2019-05-13 15:54:34 UTC,After a long and fruitless digging around systemd unit and seed.loaded I have removed (purged) and installed snapd package and it fixed this issue for me.
1828500,2019-05-18 21:59:23 UTC,I've had the same problem and purging/re-installing via apt package manager is the only way I could figure out to fix it.
1828500,2019-06-11 23:00:13 UTC,This is a pretty bad first experience for 19.04 gallery image as its supposed to be 'out of the box'.  Must be lots of people trying this first time in hyper-v gallery and giving up.  Took few hours to find this bug post. I can verify that the #5 commands corrected problem. purge was needed. uninstall didn't work.
1828500,2019-07-12 08:46:34 UTC,"I can confirm this bug is still present in the optimised 18.04.2 image, and also verify that the commands from post #5 above worked for me to fix it. I actually had to purge snapd twice, as the first time it failed due to being unable to delete a folder with `rm` since it was a folder, not a file. `sudo rm -r /var/cache/snapd/aux` fixed it for me, and then the second purge completed properly. I had no issues after that with reinstalling snap or the core snap package, or a subsequent dist-upgrade, which had failed completely on a previous spinup of the 18.04.2 LTS image."
1828500,2019-07-12 10:14:06 UTC,I suspect these images have a broken seed.yaml. Could somebody attach that?
1828500,2019-05-10 03:36:06 UTC,To my limited understanding system appears to have not completed its start:
1828500,2019-07-12 10:45:16 UTC,"yeah. That seed.yaml is missing core18, and those snaps need it AFAIK."
1828500,2019-07-12 20:15:18 UTC,"I have no understanding of the test process used to check a system livecd build, but I imagine installing a snap that confirmed itself to the test-system would be useful on each platform."
1828500,2019-07-12 17:00:10 UTC,"I think we need to add validation of the seed.yaml to livecd-rootfs:
https://code.launchpad.net/~mvo/livecd-rootfs/+git/livecd-rootfs/+merge/370065"
1828500,2019-07-12 10:39:55 UTC,@chipaca: seed.yaml from the 18.04.2 image in the Hyper-V Gallery
1828500,2019-07-12 10:48:06 UTC,followup:
1828500,2019-07-12 10:46:18 UTC,"To confirm, (from memory), sudo snap info --verbose /var/lib/snapd/seed/snaps/*.snap | grep base:"
1828500,2019-07-12 10:50:06 UTC,"Yeah. The images are broken, because they ship a broken seed.yaml. Who creates the images? That's the project this bug needs to be assigned to."
1828505,2019-07-27 12:18:03 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828507,2019-05-10 14:05:51 UTC,"If one continues with the iso, and installs the OS in the
guest, the rebooting of the guest from within the guest
OS too causes qemu to exit fatally. So, one can run
'systemctl reboot' or 'reboot' within the guest OS and
see qemu crash (immediately after SLOF prints version,
etc. as part of the reboot sequence, as described before)."
1828508,2019-05-15 10:23:31 UTC,"On Fri, May 10, 2019 at 06:06:32AM -0000, Jake Mikelson wrote:

> Public bug reported:
>
> Using qemu-img version 3.1.50 (v3.1.0-13607-geb2db0f7ba-dirty) on a
> Windows 10 machine.
>
> Converting a VHD to VMDK.
> qemu-img.exe convert ""c:\test\AppD-VM01.vhd"" -O vmdk -o adapter_type=buslogic -p ""c:\test\AppD-VM01.vmdk""
>
> I have also tried:
> qemu-img.exe convert ""c:\test\AppD-VM01.vhd"" -O vmdk -o adapter_type=buslogic,hwversion=6 -p ""c:\test\AppD-VM01.vmdk""
>
> Attaching the VMDK to a VM in VMware produces the following error when
> powering on.
>
> Power On virtual machine:Failed to open disk scsi0:1: Unsupported or invalid disk type 7. Ensure that the disk has been imported.
> Target: MyVM1
> vCenter Server: VCENTER
> Error Stack
> An error was received from the ESX host while powering on VM MyVM1.
> Failed to start the virtual machine.
> Module DevicePowerOn power on failed.
> Unable to create virtual SCSI device for scsi0:1, '/vmfs/volumes/5cca0155-bdddf31d-2714-00215acbeb1e/AppD-VM01/AppDdisk1-VM01.vmdk'
> Failed to open disk scsi0:1: Unsupported or invalid disk type 7. Ensure that the disk has been imported.
>
>
> If I do not specify the adapter type, it creates an IDE VMDK which works perfectly.
>
> ** Affects: qemu
>      Importance: Undecided
>          Status: New
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1828508
"
1828508,2019-05-16 01:44:26 UTC,"Hi, I'm running 5.5."
1828509,2019-05-17 01:16:04 UTC,"Reviewed:  https://review.opendev.org/658449
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=eef85762b0a541242c883ba0de038b98f86bffce
Submitter: Zuul
Branch:    master"
1828509,2019-05-10 18:25:55 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658449"
1828510,2019-05-10 06:42:10 UTC,Sample Project
1828510,2019-05-10 16:47:01 UTC,"Hi Seth,"
1828510,2019-05-10 17:37:46 UTC,The alt key may be intercepted by your window manager?  Are you running gnome?
1828510,2019-05-10 17:56:50 UTC,I am indeed running GNOME and seems I hitting the known bug where Alt is hardcoded preventing me from invoking the context menu
1828510,2019-05-10 18:18:55 UTC,"FYI the ""finicky"" issue is already logged: https://bugs.launchpad.net/kicad/+bug/1815596"
1828510,2019-05-10 18:35:01 UTC,"Michael,"
1828510,2019-05-10 18:55:42 UTC,"Note that as far as we can tell, lp:1815596 is windows only and simply makes the context menu disappear.  It doesn't look like that is the same issue."
1828510,2019-05-10 19:04:00 UTC,"This should also get easier when we have a better selection filter, since you could just (for example) disable selection of footprints in this instance if you know you want to work with zones."
1828510,2019-05-10 19:06:33 UTC,"Seth,"
1828510,2019-05-10 13:01:57 UTC,"Can you hold the ""Alt"" key while clicking on the zone to get the disambiguation menu?"
1828513,2019-05-14 07:56:30 UTC,+1 Maciej. Exporting such a document from an ephemeral provider pxu could result in many problems. We could think that the corresponding tests are ready and under a git repo.
1828513,2019-05-13 20:25:05 UTC,"This is kind of by design. Side loading was made to quickly check if something works, this is why the sub-commands you've mentioned don't consider the side-loaded providers."
1828528,2019-05-10 09:01:23 UTC,We should likely switch to using check_cronned_output.
1828530,2019-05-10 09:15:22 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658315"
1828530,2019-05-10 10:22:09 UTC,"Reviewed:  https://review.opendev.org/658315
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=1f5a09b55ebfed7f3a0597316cffb04f512dc443
Submitter: Zuul
Branch:    master"
1828530,2019-05-10 12:49:16 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658350"
1828530,2019-05-10 13:11:19 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658356"
1828530,2019-05-10 15:04:20 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658387"
1828530,2019-05-13 07:03:45 UTC,"Reviewed:  https://review.opendev.org/658350
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=c9f44a7ceccea85693bb0afed6e721ca953fb04a
Submitter: Zuul
Branch:    master"
1828530,2019-05-13 07:05:27 UTC,"Reviewed:  https://review.opendev.org/658356
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=1cdfc381ad55e7ad1e8b9579091bb16589f2c5d8
Submitter: Zuul
Branch:    master"
1828530,2019-05-13 07:06:11 UTC,"Reviewed:  https://review.opendev.org/658387
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=822daf2794f44f61f5336a180752ba9e5482be81
Submitter: Zuul
Branch:    master"
1828534,2019-12-05 14:43:21 UTC,"I don't think we'll be fixing this in stable/rocky or stable/stein as it would break existing py3 deployments in a stable release. The trade off is that it would fix py2 deployments that upgrade to py3. For now I'm going to mark those releases as ""won't fix""."
1828534,2019-12-10 20:48:42 UTC,@Corey
1828534,2019-12-11 13:34:40 UTC,"@Dincer, that doesn't look the same"
1828534,2020-05-09 16:19:05 UTC,"Hi Corey, if we can't fix this, we need to at least document it as a known issue in the charm OpenStack upgrade documentation, surely?"
1828534,2020-05-12 14:52:40 UTC,"Yes let's update the charm deployment guide, specifically this section should call this upgrade issue out: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-upgrade-openstack.html#known-openstack-upgrade-issues"
1828534,2020-06-23 19:31:51 UTC,released as cs:~llama-charmers-next/memcached-4
1828534,2020-05-19 15:26:32 UTC,"This issue can be resolved by restarting the memcached service that designate is using for coordination. After this, the designate-producer service seems to run normally."
1828534,2020-05-19 16:30:59 UTC,adding project charm-memcached per @chris.macnaughton comment #24.
1828534,2020-06-13 21:35:13 UTC,"Reviewed:  https://review.opendev.org/733121
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=5c929b3ba950257cd612c1ba94d57c145ec03526
Submitter: Zuul
Branch:    master"
1828534,2019-12-04 19:18:51 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/697347"
1828534,2020-07-08 14:42:45 UTC,"Fix proposed to branch: stable/20.05
Review: https://review.opendev.org/740009"
1828534,2020-05-12 14:57:37 UTC,"Also we could consider cherry-picking the fixes back to rocky and stein packages. They've just not landed upstream. It would fix py2->py3 upgrades, which this bug reported. But I believe the fix would break py3->py3 upgrades. The charm deploys py3 as of rocky. The package was py2 by default in rocky (with py3 available) and py3 by default in stein."
1828534,2019-12-04 19:17:22 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/697346"
1828534,2020-05-19 16:46:00 UTC,Chris' doc update has been merged: https://review.opendev.org/#/c/729300
1828534,2019-08-26 04:46:54 UTC,"Reviewed:  https://review.opendev.org/673360
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=556a27e4e9c9c4e21fb0ea46d8d8832d28c85314
Submitter: Zuul
Branch:    master"
1828534,2019-07-29 20:17:33 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/673360"
1828534,2019-07-29 19:49:45 UTC,"I have a fix coming for this. It is very similar to the example at: https://docs.openstack.org/tooz/latest/user/tutorial/group_membership.html , where host-1 is binary encoded."
1828534,2019-07-25 20:31:16 UTC,From /usr/lib/python3/dist-packages/designate/coordination.py:
1828534,2019-07-25 19:45:56 UTC,"Reproducing with designate, the problem appears after we have one designate unit that is at bionic-rocky (py3) and one that is at bionic-queens (py2). It is resolved once all units are at bionic-rocky. More details on that:"
1828534,2019-07-25 19:38:03 UTC,This is reproducible in a python3 shell. The problem is that sorted() is called on a list that includes both bytes and str types:
1828534,2019-07-24 20:58:20 UTC,"I was able to reproduce this. It's specific to coordination backend code that is used for HA. For charms, the following bundle config was used (snipped for brevity to just show designate bits):"
1828534,2019-07-22 20:47:49 UTC,The traceback looks like an upstream designate issue with py3 support:
1828534,2019-07-04 16:45:16 UTC,Attached logs from a healthy unit as well.
1828534,2019-07-04 16:44:15 UTC,"Managed to reproduce it (only on one unit though), this time with debug=true - looks like it is a py2 - py3 issue:"
1828534,2019-09-27 09:35:05 UTC,This issue was fixed in the openstack/designate 9.0.0.0rc1 release candidate.
1828534,2019-07-03 21:12:17 UTC,I'm going to do another upgrade attempt.
1828534,2019-07-03 20:23:00 UTC,Any tips on how to reproduce this? I just upgrade designate from queens to rocky and didn't hit it.
1828534,2019-07-02 15:28:57 UTC,I think this is a packaging bug
1828534,2019-05-15 17:43:38 UTC,TRIAGE:
1828535,2020-06-30 04:17:25 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1828535,2019-05-10 13:25:15 UTC,OK I see the bulk deletes here:
1828535,2019-05-10 13:22:54 UTC,"Do you have a trace or something? I'm not clear on the bulk thing you're talking about. The command should be trying to delete different records because there are different instances in each cell. Does the lock just make each command take longer, or does it fail with a DBDeadlock error or something?"
1828535,2020-04-30 15:36:46 UTC,I'm marking this as Incomplete. Please set it back to New when the requested logs are provided.
1828536,2019-05-10 11:52:14 UTC,"Hi jacinto, please could you provide us with a little more info about your system, such as:"
1828536,2019-05-11 00:23:12 UTC,"Ubuntu version: 19.04 amd64
I'm actually using .deb package provided by LibreOffice Document Foundation."
1828536,2019-05-11 12:57:20 UTC,The snap version works.
1828536,2019-05-13 08:52:17 UTC,I'm unable to reproduce this behaviour locally. Could you please confirm that this issue occurs on the current archive release of LibreOffice (1:6.2.2-0ubuntu2).
1828536,2019-07-13 04:18:02 UTC,[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]
1828537,2019-09-15 19:06:45 UTC,This issue was fixed in the openstack/kuryr-kubernetes 1.1.0 release.
1828537,2019-06-04 11:31:00 UTC,"Reviewed:  https://review.opendev.org/661246
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=1c2503a5d6a65b73276f172af7ec924c6be0a510
Submitter: Zuul
Branch:    stable/stein"
1828537,2019-05-24 09:23:09 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661246"
1828537,2019-05-22 15:57:27 UTC,"Reviewed:  https://review.opendev.org/658338
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=7b0fbccd39c43535d0206c05b102fc7d0e7010f9
Submitter: Zuul
Branch:    master"
1828537,2019-05-10 11:27:17 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658338"
1828539,2019-05-10 11:26:41 UTC,Documentation of styles:
1828540,2019-05-14 15:44:06 UTC,Thank you for your report.
1828540,2019-07-14 04:17:43 UTC,[Expired for php7.0 (Ubuntu) because there has been no activity for 60 days.]
1828541,2019-05-16 21:10:02 UTC,"From the description, this bundle is deploying k8s-master and k8s-worker charms to the same unit. This is unsafe, as any relations/config-changes/updates to one charm would affect system-wide bits for all others. The process of deploying multiple charms onto the same unit is called ""hulk smashing""; it isn't supported because there is no way to know how one charm might affect the environment of another."
1828541,2019-05-16 19:23:03 UTC,Engineering Notes:
1828541,2019-05-13 07:27:09 UTC,The k8s cluster is created in openstack instances.
1828541,2019-05-13 00:42:08 UTC,I feel it might be a charm related issue.
1828541,2019-05-13 00:41:00 UTC,"Hi Lorenbzo,
Thanks for creating the bug.
Is the cluster a CDK k8s running on public cloud?"
1828541,2019-05-16 13:26:47 UTC,How are you co-locating the two charms? If they are both just on the same machine with --to <machine_number> what is happening is the worker and master charm are both writing the file /root/cdk/server.crt. This becomes a last write wins situation. These two charms are not designed to co-exist on the same machine and need to be split up.
1828542,2019-05-10 19:17:51 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658456"
1828543,2019-06-19 01:27:37 UTC,"Reviewed:  https://review.opendev.org/663979
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=62f55a12b053b753616747445bc9e3aa0e5e72d9
Submitter: Zuul
Branch:    master"
1828543,2020-08-04 13:58:45 UTC,"Change abandoned by Lajos Katona (<email address hidden>) on branch: stable/stein
Review: https://review.opendev.org/706820
Reason: The keystoneauth patch is blocked (I just abandoned it), if there's a real need for this fix, we can try ot workaround this in neutron-lib (that's ugly, but better than nothing)"
1828543,2020-02-10 13:00:58 UTC,"Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/706820"
1828543,2020-02-10 09:39:13 UTC,"Oh, no I see now the related bug line in commit msg, just not in a pattern as I expected, so it's possible to backport it perhaps."
1828543,2020-02-10 09:37:58 UTC,"I just checked and a fix for keystoneauth1 is necessary:
https://review.opendev.org/662281"
1828543,2020-02-10 09:24:56 UTC,The fixes are part of train.
1828543,2020-02-10 09:10:15 UTC,we received a bug report on stable/stein separately (bug 1862565). It is worth checking the possibility of backporting the fix in the master. I added backport-potential-xx tags.
1828543,2019-07-17 17:11:35 UTC,"Reviewed:  https://review.opendev.org/670105
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=12ab7c4cb149147e3e7886233f4ba99c3484f923
Submitter: Zuul
Branch:    master"
1828543,2019-07-10 15:50:32 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/670105"
1828543,2019-06-19 01:37:42 UTC,"Reviewed:  https://review.opendev.org/663980
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=95023227b77b72382fdbb06bddadf832b1f20f8f
Submitter: Zuul
Branch:    master"
1828543,2019-06-10 22:36:11 UTC,"Reviewed:  https://review.opendev.org/663978
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=28e71cbd74bf10da3332265659adb27ee9614582
Submitter: Zuul
Branch:    master"
1828543,2019-06-07 15:25:11 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/663979"
1828543,2019-06-07 15:27:07 UTC,"Change abandoned by Lajos Katona (<email address hidden>) on branch: master
Review: https://review.opendev.org/662204
Reason: https://review.opendev.org/662281 fixed the problem in keystoneauth"
1828543,2019-06-07 15:27:27 UTC,"Change abandoned by Lajos Katona (<email address hidden>) on branch: master
Review: https://review.opendev.org/662205
Reason: https://review.opendev.org/662281 fixed the problem in keystoneauth"
1828543,2019-05-10 17:58:26 UTC,"Queens is OK, on Monday I will check with Rocky."
1828543,2019-05-15 12:33:05 UTC,Short summary with my latest findings:
1828543,2019-05-16 11:01:11 UTC,I think I got to the depths of this issue. From this point I will refer to code and behavior on current master.
1828543,2019-05-16 12:07:28 UTC,"Just for fun:
https://opendev.org/openstack/placement/src/branch/master/placement/util.py#L94
placement.util.json_error_formatter is the method that formats the http body to be the above mentioned."
1828543,2019-05-13 14:03:30 UTC,Rocky is failing to report to placement with the same exception (TypeError: argument of type 'NoneType' is not iterable)
1828543,2019-05-30 13:02:25 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/662205"
1828543,2019-06-03 08:58:09 UTC,"The ultimate solution proposed to keystoneauth:
https://review.opendev.org/662281"
1828543,2019-05-30 13:01:07 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/662204"
1828543,2019-06-07 15:22:10 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/663978"
1828543,2019-06-07 15:25:26 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/663980"
1828544,2020-02-03 21:14:15 UTC,Marking as invalid for juju since i think it was intended to file this against charmed kubernetes
1828544,2020-06-08 19:03:33 UTC,"> We encountered this only when installing worker nodes on the same machine with masters
"
1828545,2019-05-10 12:00:11 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828545,2020-11-05 06:35:41 UTC,"Passed with:
  5.8.0-22.23~20.04.1 on ARM64 node hotdog-kernel
  5.4.0-52.57-generic on ARM64 node hotdog-kernel / ms10-34-mcdivittB0-kernel
  4.15.0-122.124-generic on ARM64 node hotdog-kernel / starmie-kernel"
1828546,2019-05-14 08:34:03 UTC,"This seems to happen on pepe because of the speed of the backing store and timeout value is probably too low.  The error occurs in nbd_xmit_timeout(), this issues the timeout error message, then nbd can't provide the backing store fs/buffer.c reports a bug in submit_bh_wbc():"
1828546,2019-05-14 09:01:10 UTC,Commit pushed to autotest: https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=dd9a3996d71618272ba9b00bfacb20d81cbd683e
1828546,2019-05-15 10:38:36 UTC,Node pepe passed with this test. Thanks.
1828547,2019-05-13 21:10:06 UTC,"I've seen this too, it looks like it works itself out on the next periodic re-sync. I'll take a look."
1828550,2019-05-10 12:12:46 UTC,related to https://bugs.launchpad.net/tripleo/+bug/1827863 which is stable/stein
1828550,2019-05-27 12:48:42 UTC,"http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-standalone-upgrade-stein and http://logs.openstack.org/09/661009/3/gate/tripleo-ci-centos-7-standalone-upgrade-stein/d6aa92b/logs/tempest.html.gz tests are passing, closing this bug,"
1828551,2019-05-14 15:47:28 UTC,Thank you for taking the time to report this bug and helping to make Ubuntu better.
1828552,2019-05-15 16:46:30 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1631246, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find."
1828553,2019-05-10 12:44:54 UTC,"BTW, deployment with Disco works well on these ARM64 Moonshot nodes."
1828553,2019-05-10 16:15:54 UTC,"After taking a look at the logs and speaking to the hyperscale team it would appear that this is leaning towards being a kernel signing issue, affecting specifically x-gene/uboot systems w/ bionic-hwe-edge"
1828553,2019-05-10 18:18:28 UTC,"I confirmed that if we compress the kernel (as Seth's patch does), the 5.0 kernel would boot fine on the HP m400[*]. I chatted w/ apw about this and we agreed that a respin isn't necessary because LP showed that there is no current linux-hwe-edge package in bionic, and therefore introducing one should not be a regression. ***But*** I now see that I gave him bad information. What I failed to recognize is that the linux-*meta*-hwe-edge package is already in bionic-updates - it just depends on binaries from the linux-hwe package at the moment. So, there could very well be users with the linux-image-generic-18.04-hwe-edge installed today (which currently depends on 4.18) that would get a broken update if they were to dist-upgrade to the new version that depends on the 5.0 kernel."
1828555,2019-05-10 12:46:11 UTC,"I do have tracks in my library that I'd basically never mixxx. I've hidden tose tracks but I kept the files to play those tracks on rare request.
We should be able to sort tracks in the Hidden feature to make full use of it."
1828556,2019-05-13 16:53:55 UTC,Solved removing index files
1828556,2019-05-10 12:54:34 UTC,"https://answers.launchpad.net/ubuntu/+question/680590
I've already made a question about this bug"
1828556,2019-05-10 16:27:28 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1828557,2019-05-29 08:39:47 UTC,GDB is needed for the autotest framework.
1828558,2019-08-19 23:23:35 UTC,"I have verified the fix for bionic and disco by doing netinstalls with apt-setup/proposed=true on the kernel command line with disk images that had had a raid6 with 0.90 metadata created on them and watching the output of wipefs $image outside of the VM. Immediatly before selecting the ""write changes to disk"" action in partman:"
1828558,2019-08-27 21:19:25 UTC,This bug was fixed in the package partman-base - 192ubuntu1.2
1828558,2019-08-27 21:19:01 UTC,"The verification of the Stable Release Update for partman-base has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828558,2019-08-27 21:18:55 UTC,This bug was fixed in the package partman-base - 206ubuntu1.2
1828558,2019-08-21 08:35:27 UTC,"I've now done the testing asked for in comment #10, verifying that additional disks are not touched by installing to one."
1828558,2019-08-13 17:01:32 UTC,"Hello lvm, or anyone else affected,"
1828558,2019-08-05 23:28:22 UTC,"Turns out my fix is wrong: it is clearing the superblocks in NEW_LABEL, but really the disk should not be touched until COMMIT."
1828558,2019-08-05 11:35:14 UTC,"Hello lvm, or anyone else affected,"
1828558,2019-08-13 16:59:44 UTC,"Hello lvm, or anyone else affected,"
1828558,2019-08-05 11:31:50 UTC,"Risky, but seems okay. Would like to see testing of some other, more normal scenarios as part of verification too: installing on a regular disk, possibly having like two different disks and installing on one (making sure no data loss happened on the other?). At least for bionic."
1828558,2019-08-05 11:33:12 UTC,"Hello lvm, or anyone else affected,"
1828558,2019-07-29 01:12:07 UTC,"Having looked into this a bit I'm a bit surprised -- assuming the drive was previously part of a raid array with metadata version 0.90 -- that your system ever booted at all. Partman creates a disk label with ped_disk_new_fresh, which arranges for ped_disk_clobber to be called on the disk. This zeroes the first and last 10 kiB of the disk, which will wipe out all the mdraid superblock for all other metadata versions. So if you use a device in a MD raid array with 0.90 metadata then install to it with ubiquity you get a disk that has both a partition table and raid metadata."
1828558,2019-07-31 02:00:09 UTC,"parted upstream NACKed fixing it there, so here's an attempt to do it in partman-base instead: https://code.launchpad.net/~mwhudson/ubuntu/+source/partman-base/+git/partman-base/+ref/wipey -- currently testing this."
1828558,2019-08-02 01:09:31 UTC,This bug was fixed in the package partman-base - 206ubuntu4
1828558,2019-05-11 06:29:08 UTC,"Zeroing the md superblock in ubiquity - if that's what you are thinking about, will fix this issue in my particular scenario, but what if disk was partitioned in some other way? I am afraid it is a partial workaround, the proper albeit more compex way of handling this issue is to make sure that properly formatted partition table always takes precedence over leftover superblocks during boot."
1828558,2019-08-02 12:35:27 UTC,"But netbook installs fetch partman-base udeb from the archive over the
network from -updates on the fly."
1828558,2019-08-02 12:35:41 UTC,*netboot
1828558,2019-08-05 00:03:23 UTC,Also just the usual thing of fixing a bug in all releases newer than the one we really care about (which is bionic in this case)
1828558,2019-08-02 07:23:46 UTC,"I don't think disco will have a new image built anymore, so an sru there seems a bit pointless?"
1828559,2019-05-15 15:56:41 UTC,it looks to be fixed in master of rally-openstack by this commit: https://github.com/openstack/rally-openstack/commit/5f1a8f7137c19d74d58fd0ddf9e2ab319662ad0b
1828559,2019-05-31 08:03:58 UTC,"rally-openstack 1.5.0 released with the required commit:- https://review.opendev.org/#/c/661984/1/deliverables/_independent/rally-openstack.yaml and is available on pypi:- https://pypi.org/project/rally-openstack/#history, and in browbeat rally_openstack_version is set to 1.5.0 now with:- https://review.opendev.org/#/c/662054/, to clear tripleo fs053 issue need to set rally_openstack_version in https://opendev.org/x/browbeat/src/branch/master/ansible/install/group_vars/zuul_all.yml"
1828559,2019-06-04 08:00:59 UTC,"Job is passing now:- https://review.rdoproject.org/zuul/builds?job_name=tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset053, https://review.opendev.org/#/c/662607/1/ansible/install/group_vars/zuul_all.yml has fixed it"
1828564,2019-05-10 13:50:10 UTC,"For SRU we need a justification -- fixing specific bugs, important new functionality, etc. Having ""quite old"" firmware is not sufficient justification. If you wish for newer firmware to be included in bionic please specify what bugs or features necessitate the update."
1828564,2019-05-10 15:19:01 UTC,"Thanks for the info, I wasn't aware of what policy was for firmware."
1828564,2019-05-10 15:45:15 UTC,"On Fri, May 10, 2019 at 03:19:01PM -0000, Jonathan Cave wrote:

> Thanks for the info, I wasn't aware of what policy was for firmware.
"
1828564,2019-07-10 04:17:26 UTC,[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.]
1828565,2019-07-20 14:33:19 UTC,"Reviewed:  https://review.opendev.org/658359
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6cdb3a8374599a95303dc9bf14dbe96c2d4c0f16
Submitter: Zuul
Branch:    master"
1828565,2019-09-27 09:10:38 UTC,This issue was fixed in the openstack/keystone 16.0.0.0rc1 release candidate.
1828565,2019-05-10 13:24:14 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658359"
1828565,2019-07-01 19:04:10 UTC,I was able to recreate this using the following steps:
1828566,2019-06-24 12:37:44 UTC,"Hello,"
1828566,2020-06-10 16:04:22 UTC,The bug description is confusing to me.
1828566,2019-05-29 17:06:49 UTC,attached is the updated patch for this proposal to support custom graylog plugins by attaching them as resource to the charm
1828566,2019-05-21 12:54:29 UTC,This bug's subject was reframed after discussion with the involved people on this one.
1828566,2019-06-05 17:13:17 UTC,updated patch that also triggers graylog restart after attaching plugins
1828568,2019-05-10 13:16:07 UTC,lspci.txt is empty
1828568,2019-05-10 13:17:06 UTC,acpi.tar.bz was not obtainable
1828568,2019-05-10 13:30:08 UTC,This change was made by a bot.
1828568,2019-05-10 15:44:54 UTC,Please try Safe Graphics mode in Disco live USB.
1828568,2019-05-11 00:18:41 UTC,What magic is required to get into safe graphic mode from the Disco live USB? (normal boot on that version fails in the same way)
1828568,2019-05-11 00:43:24 UTC,"Ah, you mean nomodeset. I have tried that now with both 18.04 and 19.04 with success. Both live USBs are stable for at least 10 minutes."
1828569,2019-05-10 16:27:26 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1828569,2019-05-12 11:16:16 UTC,"Thank you for your bug report, could you try if adding that option to the kernel boot line helps?
snd_hda_intel.power_save=0
(https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter/19487 has tip on how to do that if you need directions)"
1828569,2019-05-12 11:17:29 UTC,"Could you also use the command
$ apport-collect -p alsa-base 1828569
To add the details of you soundcard/driver to the report?"
1828569,2019-05-13 02:15:35 UTC,Moved to bug 1828613
1828570,2020-09-14 07:42:46 UTC,This issue cannot be reproduced anymore on bionic with linux-hwe-5.4 5.4.0-48.52~18.04.1:
1828570,2019-09-16 13:27:19 UTC,Taking ownership of this as if affects multiple arch types
1828570,2019-08-27 13:45:29 UTC,This also affects s390x:
1828570,2019-05-10 13:32:53 UTC,"Build log with upstream tree on B-hwe-edge, P9
The detection passed:"
1828570,2019-07-18 15:51:07 UTC,"On bionic, linux-hwe-edge has been moved to linux-hwe and it's still having the same compilation issue with ppc64el:"
1828575,2020-06-22 20:23:56 UTC,A branch has been pushed to improve accessibility of the grid:
1828575,2020-09-22 22:25:24 UTC,Very nice! My sign off is at:
1828575,2020-12-14 17:53:10 UTC,"I'd like to propose a different approach: using <button> rather than <a href=""javscript:void(0)""> tags."
1828575,2020-12-18 20:51:18 UTC,Thanks for the suggestions.  Not clear what you mean re: console log noise. I see no logging on my end.
1828575,2020-12-19 17:09:53 UTC,"Works well for me!  Thank you, Mike.  Signoff here: user/sandbergja/lp1828575-eg-grid-options-accessibility-v2-signoff"
1828578,2019-05-13 15:01:36 UTC,Refer -- https://askubuntu.com/questions/1128454/dell-xps-15-9570-ath10k-qca6174-wifi-adapter-crashing
1828578,2019-05-21 16:40:33 UTC,Does downgrade the linux-firmware package help?
1828578,2019-06-04 12:59:55 UTC,@kaihengfeng sure I will test this on 18.04.2 LTS and will update you..
1828578,2019-05-27 10:46:51 UTC,"@kaihengfeng, no downgrade also not helped
As a workaround we replace to Intel wireless 8260 , 7360 card. But this is not acceptable, we have more than 10x users working on Dell XPS 9570 , 9560 models. Please suggest"
1828578,2019-05-31 05:27:34 UTC,"Please test latest mainline kernel [1] and latest firmware [2]. If the issue persists, please attach `dmesg` output when the issue happens."
1828578,2019-06-04 13:29:15 UTC,"@kaihengfeng, one question with the installation of https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ , I can only see .tar.gz file, and no .deb pkg for this. Can I dwld this .tar.gz and extract this under /lib/firmware ? Please confirm"
1828578,2019-05-12 11:50:54 UTC,apport information
1828578,2019-08-01 05:56:11 UTC,"@bryce no luck, I tried with latest kernel and for failed to apply linux-firmware as per #28. So I moved to replace the wifi card."
1828578,2019-08-05 18:04:00 UTC,"That's too bad it didn't work, but thanks for testing it.  I've read suggestions that it relates to bluetooth, so am currently testing with that disabled in bios, but I don't have high hopes.  If it doesn't, I'll probably just go with the replacement option myself."
1828578,2019-08-07 07:12:14 UTC,These Dell XPS series laptop mostly comes with these killer wifi. It's better Dell to collaberately work with ubuntu to fix the issue.
1828578,2019-08-07 07:15:18 UTC,Have you tried this - https://www.dell.com/support/article/ba/en/babsdt1/sln306440/killer-n1535-wireless-firmware-manual-update-guide-for-ubuntu-systems?lang=en any luck?
1828578,2019-08-07 20:31:21 UTC,"Thanks, I've installed that firmware update and will give it a try."
1828578,2019-08-31 15:36:40 UTC,The firmware update seems to have done the trick.
1828578,2019-05-13 09:15:04 UTC,Exactly the same issue what I'm facing now - https://www.reddit.com/r/Dell/comments/a07wiw/dell_xps_9570_wifi_keeps_dropping_every_couple/
1828578,2019-07-29 18:13:12 UTC,"I'm able to reproduce this with QCA6174 802.11ac Wireless Network Adapter on a Dell XPS 13 9370 (07E6).  From a bit of googling this seems to be a widespread problem, but only mentioned solution is to replace the wifi card, as also mentioned in this bug report."
1828578,2019-05-12 11:51:06 UTC,apport information
1828578,2019-05-12 11:50:46 UTC,apport information
1828578,2019-05-12 11:51:00 UTC,apport information
1828578,2019-05-12 11:50:59 UTC,apport information
1828578,2019-05-12 11:50:58 UTC,apport information
1828578,2019-05-12 11:50:56 UTC,apport information
1828578,2019-05-12 11:50:52 UTC,apport information
1828578,2019-05-12 11:50:50 UTC,apport information
1828578,2019-05-12 11:50:48 UTC,apport information
1828578,2019-05-12 11:50:47 UTC,apport information
1828578,2019-05-12 11:51:02 UTC,apport information
1828578,2019-05-12 11:50:44 UTC,apport information
1828578,2019-05-12 11:47:20 UTC,// more info--
1828578,2019-05-11 15:08:11 UTC,"@dear team, we have more than 10x users facing the wifi reconnection issue over home network with this kernel on killer wifi. Please suggest"
1828578,2019-05-10 19:02:04 UTC,Does any of the linux-firmware supports these killer wifi driver ?  http://mirrors.edge.kernel.org/ubuntu/pool/main/l/linux-firmware/
1828578,2019-05-10 18:57:08 UTC,"Does this kernel supports  Killer 1435, 1435s and 1535 wireless cards ?"
1828578,2019-05-10 15:16:18 UTC,This wifi drop and freeze issue happens only in home wifi networks. Not on home networks.
1828578,2019-05-10 14:00:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828580,2019-05-10 15:43:34 UTC,"Andrea, which interface is this?  The grid in question probably just needs a persistKey=""eg.foo.bar"" attribute."
1828580,2019-05-13 14:12:51 UTC,Oops -- misunderstanding on my part as to what the desired LP was.  Marking this invalid & will file the actual issue in a new (wishlist) bug.
1828582,2019-05-14 22:55:33 UTC,"OK I think I see the issue. Watcher is getting an instance.update notification while a server is building, this is part of the instance.update payload:"
1828582,2019-05-15 15:03:38 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/659307"
1828582,2019-05-22 02:58:02 UTC,"Reviewed:  https://review.opendev.org/659307
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=8a206a6ae55220687a240a33062c68d947df3512
Submitter: Zuul
Branch:    master"
1828582,2019-05-22 15:39:04 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/660762"
1828582,2019-05-29 08:13:41 UTC,"Reviewed:  https://review.opendev.org/660762
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=3c75c13f80bfb9d82f043beae6bed97ca72557ff
Submitter: Zuul
Branch:    stable/stein"
1828582,2019-09-25 08:46:18 UTC,This issue was fixed in the openstack/watcher 3.0.0.0rc1 release candidate.
1828584,2019-05-10 15:40:34 UTC,https://review.opendev.org/658401
1828584,2019-05-15 15:48:08 UTC,"Reviewed:  https://review.opendev.org/658401
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=14d4cb54fa4af20a4cee216f16ce918f9b4d6545
Submitter: Zuul
Branch:    master"
1828584,2019-09-25 08:46:19 UTC,This issue was fixed in the openstack/watcher 3.0.0.0rc1 release candidate.
1828585,2019-09-19 10:09:59 UTC,This issue was fixed in the openstack/networking-ovn 7.0.0.0b1 development milestone.
1828585,2020-02-28 15:27:03 UTC,This issue was fixed in the openstack/networking-ovn 5.1.0 release.
1828585,2020-02-18 14:09:45 UTC,This issue was fixed in the openstack/networking-ovn 6.0.1 release.
1828585,2019-10-28 14:45:50 UTC,This issue was fixed in the openstack/networking-ovn 4.0.4 release.
1828585,2019-06-19 18:49:06 UTC,"Reviewed:  https://review.opendev.org/659760
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=b80adc1b9fb80866b6e0e3a8ff60e3720bdaa9d0
Submitter: Zuul
Branch:    stable/queens"
1828585,2019-05-14 23:05:48 UTC,"Reviewed:  https://review.opendev.org/658383
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=1888f19d24b17697d3a7cd5c5a0ea550af3ddb66
Submitter: Zuul
Branch:    master"
1828585,2019-06-13 12:47:19 UTC,"Reviewed:  https://review.opendev.org/659763
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=71a29c8c3be8ea33c0cf20f1723665c61f99d5df
Submitter: Zuul
Branch:    stable/stein"
1828585,2019-05-17 09:06:46 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/659763"
1828585,2019-05-17 09:06:21 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/659761"
1828585,2019-05-17 09:06:01 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/659760"
1828585,2019-06-19 18:18:42 UTC,"Reviewed:  https://review.opendev.org/659761
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=7442d0c120b5723fd5f09fa7b1e0b201852ad3b5
Submitter: Zuul
Branch:    stable/rocky"
1828586,2019-06-20 18:58:45 UTC,"This issue was resolved on GitLab
The manual was updated."
1828586,2019-06-20 19:03:49 UTC,"This was fixed on GitLab
The manual was updated"
1828586,2019-06-20 19:04:31 UTC,manual was updated on GitLab
1828587,2019-05-10 14:47:31 UTC,Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903737
1828590,2019-06-21 15:25:25 UTC,This issue was fixed in the openstack/tripleo-heat-templates 8.4.0 release.
1828590,2019-05-27 12:45:28 UTC,Closing. Please reopen if the problem still exists.
1828590,2019-05-27 12:29:33 UTC,"Reviewed:  https://review.opendev.org/658389
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=181ecb583fc5452b2bb59baec85a32f7be43546e
Submitter: Zuul
Branch:    stable/queens"
1828590,2019-05-10 15:11:30 UTC,"Fix proposed to branch: stable/queens
Review: https://review.opendev.org/658389"
1828591,2019-05-13 07:36:48 UTC,"For ha-setup, it is the correct way to add 3 new memcache units and add a relation from memcache to the nova-cloud-controller?"
1828591,2019-05-14 14:36:41 UTC,"For an ha setup (i.e. with an hacluster configuration), then at least one memcached unit is required."
1828591,2019-05-14 14:58:56 UTC,"okay, thank you. I did not read this information in the documentation from the nova-cloud-controller charm. Maybe you can add that? Is there a good complete example of Openstack Ha setup with Juju anywhere?"
1828595,2019-05-25 22:22:58 UTC,"Please note that you patch only fixes the issue for single file plugins.
Same issue exists (both on py2 and py3) for complex plugins that are imported as modules, see LoadOneSubdirPlugin().
It would be good to address that too."
1828595,2019-05-28 23:56:40 UTC,Here is a patch that fixes the reload of both the complex and simple plugins. It also unifies the import function to simplify the code.
1828595,2019-05-25 23:28:37 UTC,I did a bit more research.
1828595,2019-05-25 23:17:28 UTC,"Yes, issue is __import__ does not reimport a module if it is already in namespace.
Potential solution would be to first del(ModuleName) and then __import__() but I have not tested it."
1828595,2019-05-25 22:52:47 UTC,"@Andrew, do you have a complex plugin that is failing to reload that you could attach for me to test with? (I don't have an example handy) Looking through the code inside LoadOneSubdirPlugin() it appears that is uses the __import__ statement which works on both python 2 and 3 when used in the LoadOnePlugin() function."
1828595,2019-05-24 19:56:08 UTC,"@Wayne, I saw that in the testing originally when I was reproducing the issue (see comment #2) and also at the end (see comment #6), but that is not what I thought the main issue in this bug was about. When I reproduced this on python 3, no plugins were being reloaded (even if only the code inside run() changed not the name). This meant that the entire reload mechanism was broken."
1828595,2019-05-29 00:20:10 UTC,Looks good.  Thank you for the contribution to KiCad!
1828595,2019-05-24 15:54:19 UTC,"Antoine,"
1828595,2019-05-24 15:52:51 UTC,"The attached patch fixes the reload call when using python 3. reload() was moved into a new module called importlib in 3.4, so the old call just to reload() was failing in python3. I tested this with both python 3.6 and 2.7 on master and 5.1 and it reloads properly."
1828595,2019-05-24 09:40:34 UTC,"Hi Ian,"
1828595,2019-05-24 09:09:49 UTC,"Ok, disregard the last comment I made. It appears I had tested the wrong version on my machine (python 2 instead of python 3). This does lead to the conclusion that this issue is only with the python 3 build, since python 2 refreshes properly."
1828595,2019-05-24 00:21:50 UTC,"Antoine,"
1828595,2019-05-10 18:47:10 UTC,Steps to reproduce :
1828595,2019-05-24 18:49:58 UTC,"@Ian, your patch seems to reload the script as expected but it doesn't remove the previous script name from the menu so you end up with an extra menu entry that no longer has the correct script name.  Did you not see this in your testing?"
1828595,2019-05-29 15:22:10 UTC,It looks like the janitor missed this. Fixed in commit d8e7892081554c62edaaa973dd1fd83f793c2d2a.
1828596,2020-01-14 08:28:36 UTC,"Hello bugproxy, or anyone else affected,"
1828596,2019-05-17 19:00:40 UTC,"At my ppa, there is a version with the change. Can you please test? The package is available for bionic, cosmic, disco and eoan."
1828596,2019-09-23 19:11:28 UTC,"Hi, Hari."
1828596,2019-09-25 06:50:29 UTC,"------- Comment From <email address hidden> 2019-09-25 02:41 EDT-------
(In reply to comment #47)

> Hi, Hari.
>
> makedumpfile 1:1.6.5-1ubuntu1~18.04.2+cascardo2 on ppa:cascardo/ppa uses a
> try-reload instead. Can you test it, please?
"
1828596,2019-10-23 19:23:02 UTC,New version on ppa:cascardo/ppa for bionic. That should handle fadump and lock in the case of try-reload/condreload.
1828596,2020-01-03 15:32:39 UTC,"Focal was uploaded but it's failing in ppc64el again (see LP #1851663).
I've submitted a merge request[0] in Britney to skip this test once more."
1828596,2020-01-03 23:10:57 UTC,"A recent issue on makedumpfile was reported and investigated on LP#1857616. Due to the relevance of that, it makes sense to respin the debdiffs. So, I've reworked debdiffs for Bionic and Eoan, that should replace the ones above. Disco is not affected.
Since those packages are not in -proposed, the respin is on top of the same version, to replace the old upload."
1828596,2020-01-03 23:17:05 UTC,"I'm re-attaching the untouched disco debdiff, just for organization/completeness."
1828596,2020-01-03 23:18:55 UTC,"I'm re-attaching the untouched Xenial debdiff, just for organization/completeness."
1828596,2020-01-07 20:45:37 UTC,This bug was fixed in the package makedumpfile - 1:1.6.6-4ubuntu1
1828596,2020-01-10 18:03:50 UTC,"Hi Guilherme, Thadeu,"
1828596,2020-01-13 14:56:27 UTC,"Hello bugproxy, or anyone else affected,"
1828596,2020-01-13 15:54:08 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.6-2ubuntu2) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:"
1828596,2019-09-23 17:30:23 UTC,"------- Comment From <email address hidden> 2019-09-23 13:28 EDT-------
Sorry about the delay. Observed that kdump/fadump is loaded even when
kdump-tools service is disabled. Not desirable, I guess. Probably need to
check if kdump-tools service is active before trying a reload?"
1828596,2020-01-14 09:55:45 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.4) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1828596,2020-01-14 14:18:41 UTC,"Hello bugproxy, or anyone else affected,"
1828596,2020-01-15 20:41:43 UTC,"------- Comment From <email address hidden> 2020-01-15 15:34 EDT-------
Verified successfully on eoan with kdump-tools
version 1:1.6.6-2ubuntu2"
1828596,2020-01-15 21:01:48 UTC,"------- Comment From <email address hidden> 2020-01-15 15:44 EDT-------
With EOL for disco this month, marking as verification done
as this is verified successfully on bionic, eoan & xenial."
1828596,2020-01-16 06:04:42 UTC,"Yes, that's fine - disco was already set to Won't Fix on the Launchpad bug side, since it will reach it's EOL on Jan the 23rd."
1828596,2020-01-16 10:10:22 UTC,"Hello Hari,"
1828596,2020-01-16 17:16:27 UTC,"------- Comment From <email address hidden> 2020-01-16 11:02 EDT-------
(In reply to comment #78)

> Hello Hari,
>
> Glad to see you around on bugs again. :)
"
1828596,2020-01-29 03:37:21 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828596,2020-01-29 03:38:31 UTC,This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu2
1828596,2020-01-29 03:47:35 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.4
1828596,2020-01-29 03:50:17 UTC,This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.2
1828596,2019-05-10 16:42:41 UTC,I will start working on an upload to eoan by next week. I should have something for you to test early in the week.
1828596,2020-01-14 12:56:42 UTC,"Thanks for the verification! Can you please verify the Eoan version too?
Cheers,"
1828596,2019-09-23 15:22:44 UTC,"Hi Hari, did you have a chance to re-test using the latest version Cascardo pointed in his last comment?"
1828596,2019-10-25 10:40:28 UTC,"------- Comment From <email address hidden> 2019-10-25 06:29 EDT-------
(In reply to comment #49)

> New version on ppa:cascardo/ppa for bionic. That should handle fadump and
> lock in the case of try-reload/condreload.
>
> Hari, can you give it a try?
"
1828596,2019-09-18 14:23:15 UTC,https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1844524
1828596,2019-05-20 13:58:35 UTC,"Marking as ""incomplete"" while awaiting test results from Thadeu's PPA kernel."
1828596,2019-05-21 13:44:13 UTC,"------- Comment From <email address hidden> 2019-05-21 06:16 EDT-------
Cascardo, the udev rules (/lib/udev/rules.d/50-kdump-tools.rules) should have been:"
1828596,2019-05-21 13:58:42 UTC,"Hi, Hari."
1828596,2019-05-22 06:39:24 UTC,"------- Comment From <email address hidden> 2019-05-22 02:33 EDT-------
(In reply to comment #11)

> Hi, Hari.
>
> So, as you said, other architectures will use add/remove instead of online,
> and we want to support them too. Any reason not to do it that you are
> thinking of?
"
1828596,2019-05-22 11:19:27 UTC,"------- Comment From <email address hidden> 2019-05-22 07:16 EDT-------
(In reply to comment #12)
[...]

> But I thought this rules were there by accident and the entries would be put
> under arch flags to avoid them for ppc64..
"
1828596,2019-05-29 16:29:45 UTC,"Based on the last comment, it looks like IBM's testing was successful and this patch is ready for SRU.
Thanks."
1828596,2019-06-20 18:35:45 UTC,This is now in eoan-proposed. Please verify. I will start the backport process when it hits eoan.
1828596,2019-09-19 14:05:48 UTC,"A fixed grep is already in bionic-updates. Either that or the one on my ppa must be installed in order for the makedumpfile version in my ppa to work. I will wait for testing feeback before I get this fix uploaded to eoan, disco and bionic."
1828596,2019-06-28 16:14:20 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu2
1828596,2019-07-03 12:36:58 UTC,"On Mon, Jun 24, 2019 at 11:59:48AM -0000, bugproxy wrote:

> ------- Comment From <email address hidden> 2019-06-24 07:49 EDT-------
> Thanks for the change. With it, try-restart is being triggered for
> kdump-tools service after CPU add operation but systemd reported
> failure with below logs:
>
> Jun 24 06:47:06 ubuntu systemd[1]: Stopped Kernel crash dump capture service.
> Jun 24 06:47:06 ubuntu systemd[1]: Starting Kernel crash dump capture service...
> Jun 24 06:47:06 ubuntu kdump-tools[2023]: Starting kdump-tools:  * Creating symlink /var/lib/kdump/vmlinuz
> Jun 24 06:47:06 ubuntu kdump-tools[2023]:  * Creating symlink /var/lib/kdump/initrd.img
> Jun 24 06:47:06 ubuntu kdump-tools[2023]: Modified cmdline:BOOT_IMAGE=/vmlinux-5.0.0-17-generic root=/dev/mapper/ubuntu--vg-root ro systemd.unit=kdump-tools-dump.service maxcpus=1 irqpo
> Jun 24 06:47:06 ubuntu systemd[1]: kdump-tools.service: Main process exited, code=killed, status=15/TERM
> Jun 24 06:47:06 ubuntu systemd[1]: kdump-tools.service: Failed with result 'signal'.
> Jun 24 06:47:06 ubuntu systemd[1]: Stopped Kernel crash dump capture service.
> Jun 24 06:47:06 ubuntu systemd[1]: Starting Kernel crash dump capture service...
> Jun 24 06:47:06 ubuntu kdump-tools[2071]: Starting kdump-tools:  * Creating symlink /var/lib/kdump/vmlinuz
> Jun 24 06:47:06 ubuntu kdump-tools[2071]:  * Creating symlink /var/lib/kdump/initrd.img
> Jun 24 06:47:06 ubuntu kdump-tools[2071]: Modified cmdline:BOOT_IMAGE=/vmlinux-5.0.0-17-generic root=/dev/mapper/ubuntu--vg-root ro systemd.unit=kdump-tools-dump.service maxcpus=1 irqpo
> Jun 24 06:47:06 ubuntu systemd[1]: kdump-tools.service: Main process exited, code=killed, status=15/TERM
> Jun 24 06:47:06 ubuntu systemd[1]: kdump-tools.service: Failed with result 'signal'.
> Jun 24 06:47:06 ubuntu systemd[1]: Stopped Kernel crash dump capture service.
> Jun 24 06:47:06 ubuntu systemd[1]: kdump-tools.service: Start request repeated too quickly.
> Jun 24 06:47:06 ubuntu systemd[1]: kdump-tools.service: Failed with result 'signal'.
> Jun 24 06:47:06 ubuntu systemd[1]: Failed to start Kernel crash dump capture service.
>
> ---
> Looks like a ratelimit issue with systemd. Is there some systemd option to workaround it?
>
> I am running the below command on a PowerVM machine:
>
> # drmgr -c cpu -r -q 1 (to remove a core)
> # drmgr -c cpu -a -q 1 (to add it back -> this triggers 8 CPU online udev events as SMT is 8)
>
> To conclude, udev rule alone is not sufficient. Need a way to address the multiple
> requests at once..
"
1828596,2019-07-15 10:40:39 UTC,"------- Comment From <email address hidden> 2019-07-15 06:36 EDT-------
Cascardo, I did not tinker with other options but disabling ratelimit helped:"
1828596,2019-07-20 19:21:43 UTC,"Disabling the ratelimit in general would break other failure modes, so I would rather just reset-failed when calling try-restart because of the hotplug events."
1828596,2019-07-25 09:50:03 UTC,"------- Comment From <email address hidden> 2019-07-25 05:43 EDT-------
(In reply to comment #27)

> Disabling the ratelimit in general would break other failure modes, so I
> would rather just reset-failed when calling try-restart because of the
> hotplug events.
>
> Can you try the package in ppa:cascardo/kdump2? Packages for eoan, disco and
> bionic available.
"
1828596,2019-06-24 11:59:48 UTC,"------- Comment From <email address hidden> 2019-06-24 07:49 EDT-------
Thanks for the change. With it, try-restart is being triggered for
kdump-tools service after CPU add operation but systemd reported
failure with below logs:"
1828596,2019-07-26 10:50:05 UTC,"------- Comment From <email address hidden> 2019-07-26 06:48 EDT-------
Guilherme, the initial fix (udev rule) is still available. But while testing I observed failure
due to systemd ratelimiting. I proposed to disable ratelimit but IIUC, Cascardo
preferred a different approach that does not involve disabling systemd ratelimit
and provided an updated package with a different approach to solve ratelimiting.
My recent comment is that there is no updated package but just the initial fix.
Hope that clears it up.."
1828596,2019-07-25 14:29:34 UTC,"Hi Hari, did you manage to try the package in https://launchpad.net/~cascardo/+archive/ubuntu/kdump2?"
1828596,2019-09-18 02:05:33 UTC,"Hi, can you try the package in ppa:cascardo/ppa ?"
1828596,2019-09-17 13:55:24 UTC,The version of makedumpfile in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.
1828596,2019-08-30 06:50:10 UTC,------- Comment (attachment only) From <email address hidden> 2019-08-30 02:48 EDT-------
1828596,2019-08-29 13:00:47 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1828596,2019-09-18 12:16:28 UTC,"There is some interaction between systemd MemoryDenyWriteExecute=yes setting on udevd and how grep has been built (possibly pointing out at the toolchain), so the new solution on the ppa isn't working on bionic."
1828596,2019-08-28 13:50:44 UTC,"Hello bugproxy, or anyone else affected,"
1828596,2019-08-28 13:43:43 UTC,"Hello bugproxy, or anyone else affected,"
1828596,2019-08-05 12:01:05 UTC,"It was implemented, but the upload did not build on that ppa, because I used different versions. I am still catching up after vacation time, so will post some updates as soon as I have them."
1828596,2019-07-26 13:11:38 UTC,"Hi Hari, thanks for clarifying! I can now understand, seems we need to wait for Cascardo's input, to see if he already implemented the systemd reset-failed thing or not."
1828596,2019-08-29 12:40:12 UTC,------- Comment on attachment From <email address hidden> 2019-08-29 08:34 EDT-------
1828597,2019-09-30 13:53:39 UTC,"Even though the bionic and disco verifications were successful (thanks for verifying), these patches were bundled in a single submission with other patches (from other bugs) which could not be successfully verified. As a result, all patches have had to be removed."
1828597,2019-10-10 18:09:48 UTC,New version of makedumpfile/kdump-tools now without the fix that failed verification. It contains the fix for this bug and 3 more.
1828597,2019-10-23 13:56:53 UTC,"Hello bugproxy, or anyone else affected,"
1828597,2019-10-23 14:00:11 UTC,"Hello bugproxy, or anyone else affected,"
1828597,2019-10-23 15:31:47 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:"
1828597,2019-11-11 15:56:26 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1.3
1828597,2019-10-25 13:01:58 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.3) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1828597,2019-11-11 15:56:44 UTC,"The verification of the Stable Release Update for makedumpfile has completed successfully and the package is now being released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828597,2019-11-11 15:57:55 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.3
1828597,2020-01-28 09:26:23 UTC,"Hi, Mathew."
1828597,2019-10-25 10:59:44 UTC,"------- Comment From <email address hidden> 2019-10-25 06:58 EDT-------
On disco, with kdump-tools/makedumpfile package version 1:1.6.5-1ubuntu1.3
maxcpus=1 is used instead of nr_cpus=1 by default as expected."
1828597,2019-08-30 06:30:22 UTC,"------- Comment From <email address hidden> 2019-08-30 02:19 EDT-------
Resolved with makedumpfile/kdump-tools version 1.6.5-1ubuntu1.1 on Disco"
1828597,2019-06-20 18:36:21 UTC,"This is now on eoan-proposed. Please, verify. I will SRU to disco and cosmic soon, after it gets to eoan."
1828597,2019-08-29 11:49:38 UTC,"------- Comment From <email address hidden> 2019-08-29 07:44 EDT-------
With kdump-tools package version 1.6.5-1ubuntu1~18.04.2, the kdump kernel
is loaded with maxcpus=1 instead of nr_cpus=1"
1828597,2019-08-28 13:50:59 UTC,"Hello bugproxy, or anyone else affected,"
1828597,2019-08-28 13:44:00 UTC,"Hello bugproxy, or anyone else affected,"
1828597,2019-06-28 16:14:20 UTC,This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu2
1828597,2019-06-24 11:39:31 UTC,"------- Comment From <email address hidden> 2019-06-24 07:37 EDT-------
This looks good. With the change, now we are defaulting to ""maxpus=1""
instead of nr_cpus=1 while passing parameters to kdump kernel.."
1828597,2019-05-10 16:40:05 UTC,"This is really a bug on the kernel, after and including 4.18."
1828597,2019-05-29 16:31:23 UTC,"Based on the last comment, it looks like IBM's testing was successful and this patch is ready for SRU.
Thanks."
1828597,2019-05-21 13:43:59 UTC,"------- Comment From <email address hidden> 2019-05-21 06:29 EDT-------
The change looks good. Thanks!"
1828597,2019-05-20 13:59:39 UTC,"Marking as ""incomplete"" while awaiting test results from Thadeu's PPA."
1828597,2019-05-17 18:55:35 UTC,"I have pushed a fix to my ppa ppa:cascardo/kdump2, for bionic, cosmic, disco and eoan."
1828597,2019-05-10 18:56:25 UTC,"Okay, let's consider this option on makedumpfile side. I'll test it and provide a test package by next week."
1828597,2019-05-10 17:29:28 UTC,"------- Comment From <email address hidden> 2019-05-10 13:25 EDT-------
Right, Cascardo."
1828597,2019-08-29 13:00:46 UTC,"All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running.
The following regressions have been reported in tests triggered by the package:"
1828598,2019-05-16 18:43:10 UTC,Related: https://review.opendev.org/#/c/658973/
1828598,2019-05-14 02:38:29 UTC,"Reviewed:  https://review.opendev.org/658399
Committed: https://git.openstack.org/cgit/openstack/watcher/commit/?id=5c2939f23b8ebf23ccfd0a4dd41fadc9f344ac6e
Submitter: Zuul
Branch:    master"
1828598,2019-05-13 14:52:54 UTC,"It's the tempest plugin / test that is deleting the server, right? As part of the test resource cleanup. The question is why is the test cleaning up the server before the live migration is complete? The test is waiting for the action plan to complete, which it says it is successful, but the thing I couldn't figure out (due to lack of debug logs in the nova_helper code in watcher) was at what point watcher thought the live migration was complete and why - because then it would mark the action plan as successful which triggers the test to start tearing down."
1828598,2019-05-13 03:31:03 UTC,"In http://logs.openstack.org/74/657374/6/check/watcher-tempest-workload_balancing/3e34c3f/controller/logs/screen-watcher-decision-engine.txt.gz
log all the notification events from nova.
It seems devstack deleted the server before it finished the migration.
Maybe we should wait until finished migration before doing other action."
1828598,2019-05-10 15:34:37 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658399"
1828599,2019-06-29 09:00:56 UTC,"Reviewed:  https://review.opendev.org/664551
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_octavia/commit/?id=2b39df7d8de3856185ebef0b24382cd0d8b18cca
Submitter: Zuul
Branch:    master"
1828599,2019-07-01 07:26:59 UTC,"Fix proposed to branch: stable/stein
Review: https://review.opendev.org/668369"
1828599,2019-07-01 07:34:14 UTC,"Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/668373"
1828599,2019-07-23 09:30:46 UTC,"Reviewed:  https://review.opendev.org/668373
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_octavia/commit/?id=82c5de33f573406a78992a4c3ef1fd144c967a12
Submitter: Zuul
Branch:    stable/rocky"
1828599,2019-07-23 18:04:43 UTC,"Reviewed:  https://review.opendev.org/668369
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_octavia/commit/?id=54006a86908ecb0c8943165fc3320926826358d7
Submitter: Zuul
Branch:    stable/stein"
1828600,2019-05-15 20:36:58 UTC,"This seems to be an encoding issue related to terminal, click, snapcraft and store interaction:
https://pastebin.canonical.com/p/5BdCDTTGsf/"
1828602,2019-05-17 09:39:04 UTC,"Hi Andres,"
1828602,2019-05-16 12:11:07 UTC,"Dylan,"
1828602,2019-05-16 11:58:06 UTC,"Thanks, it does fix our issue."
1828602,2019-05-15 08:21:19 UTC,I believe the issue is how get_routable_address_map is taking into account that undefined spaces are routeable between each other. Which is completely against the definition of the undefined space.
1828602,2019-05-14 11:45:12 UTC,I thought I explained already:
1828602,2019-05-14 09:56:28 UTC,"I agree with you, but without the required data to understand your envirownt we cannot effectively work to solve the issue."
1828602,2019-05-13 13:11:12 UTC,"I think I found the problem, the dns resolution for maas-internal domain somehow is not working after deploy."
1828602,2019-05-14 07:41:27 UTC,Can you provide a bit more information on how your infrastructure is implemented? DNS servers should only be one of two things:
1828602,2019-05-14 05:42:10 UTC,"I found the root problem, according to systemd-resolved log, the dns servers list is too long, dns resolution is not working anymore."
1828602,2019-05-12 20:44:10 UTC,"Hi Anderes,"
1828602,2019-05-12 16:27:19 UTC,Hi there!
1828602,2019-05-11 09:10:41 UTC,"ever since this happen, all the machine in all rack controller now stucking at this stage."
1828602,2019-05-10 15:55:06 UTC,"The error effectively means that the machine never booted into the installed environment, or if it did, it could have failed in many ways, like failing to configure networking by cloud-unit, or failing to boot from proper disk, or crashing, or failing to reboot, etc."
1828602,2019-05-14 09:31:46 UTC,"Apparently that isn't true. We have a single, different vlan for each rack."
1828604,2019-05-28 12:53:04 UTC,"@binli can not see it from log and can not reproduce the issue, can you elaborate why gnome-characters is hanged?"
1828604,2019-05-29 06:28:12 UTC,"I tried to install the 3-28-1804, but it's failed, so this solution also need to debug."
1828604,2019-05-29 06:35:53 UTC,"@Rex,"
1828604,2019-05-29 07:17:34 UTC,Looks in our oem image we used the wrong channel.
1828604,2019-05-29 07:29:23 UTC,gnome-3-26-1604 could be downloaded from stable/18.04.
1828604,2019-05-29 15:17:14 UTC,"Reproduced with the sutton-mccarthy-bionic-amd64-20190426-96.iso, here is summary of the finding -"
1828604,2019-05-30 03:56:31 UTC,Looks like this bug expands to more applications from app store..Example I tried to install VLC player and get the same error. So it could be more...will try some common applications and update the is bug asap..
1828604,2019-05-31 09:32:06 UTC,"I tried to remove all the gnome-* snaps in /var/lib/snapd/seed/seed.yaml and run ""snap abort --last=seed"", ""sudo systemctl restart snapd""."
1828604,2019-05-30 10:23:26 UTC,@chipaca agree. The build processes need to be fixed and improve the QA tests to capture the issue.
1828604,2019-05-31 09:14:56 UTC,"@Rex,"
1828604,2019-05-31 09:48:49 UTC,"Yes, you also need to pull core18."
1828604,2019-07-15 10:48:45 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828604,2019-08-05 12:22:18 UTC,"-------------------------------------------------------------------------------
You have successfully initiated a package propagation request!
-------------------------------------------------------------------------------
URL            : https://bugs.launchpad.net/bugs/1838973
Assignee       : oem-archive
Urgency        : High
Title          : request of copy_package [sutton-base-timbuktu-bionic-devel]
[Description]
 Operation: copy_package
 Source: sutton-base-timbuktu-bionic-devel
 Destination: sutton-base-timbuktu-bionic-staging
 Package: sutton-base-meta (==3.0sutton6)
 Production: bionic-sutton-base-timbuktu
 ===== Description ====="
1828604,2019-09-06 07:03:34 UTC,"@Vamshee,"
1828604,2019-05-28 08:55:45 UTC,"Based on comment #19, I build image, and I found there are still problems. After I removed the gnome-calculator, it will hang at gnome-characters. :)"
1828604,2019-05-30 09:43:29 UTC,"Yes, an invalid seed.yaml will trip up snapd. Please don't seed images with an invalid seed.yaml."
1828604,2019-05-28 06:42:13 UTC,Another solution is remove the gnome-calculator from preinstalled package list.
1828604,2019-05-14 09:04:04 UTC,Image : sutton-mccarthy-bionic-amd64-20190426-96.iso
1828604,2019-05-28 06:03:38 UTC,"I removed the gnome-calculator from seeded-snaps, building a new image now."
1828604,2019-05-28 06:37:40 UTC,"@Rex,"
1828604,2019-05-14 08:38:36 UTC,"I tried the official 18.04.2, installed the 66.05(64bit) snap successfully from 'Ubuntu Software' 3.28.1."
1828604,2019-05-14 08:39:13 UTC,And it could also start up correctly. :)
1828604,2019-05-14 08:53:06 UTC,"$ snap list
Name     Version    Rev   Tracking  Publisher   Notes
core     16-2.38.1  6818  stable    canonical✓  core
firefox  66.0.5-1   212   stable    mozilla✓    -"
1828604,2019-05-14 09:02:31 UTC,I can reproduce the issue. Please refer to the picture Appstore.png
1828604,2019-05-14 09:25:23 UTC,"U@Test:~$ dpkg -l | grep ubuntu-software
ii  ubuntu-software    3.28.1-0ubuntu4.18.04.9   all    Utility for browsing, installing, and removing software"
1828604,2019-05-20 07:15:42 UTC,"Found the root cause, the snapd seeded service was waiting."
1828604,2019-05-13 06:13:20 UTC,It should be a snap package issue.
1828604,2019-05-27 07:46:05 UTC,"- The default search result of firefox from software center is a snap[1].
- The issue is the user want to install a snap before the snapd on the device is initialized and to be ready for install snaps.
- It's not directly related to oem-image, but a timing issue of snapd, the error is from snapd. Depends on the network environment, some times snapd takes a bit longer to talk to the Ubuntu snap Store.
- Eventually, the snapd will finish the seeding process and ready for install, unless the Ubuntu Store API is banned from that network. ""snap changes"" can show you the latest progress of the snapd."
1828604,2019-05-27 08:07:18 UTC,"@Rex,"
1828604,2019-05-27 08:41:55 UTC,"-- Reboot --
May 27 04:30:55 u-ThinkPad-X390-Yoga systemd[1]: Starting Snappy daemon...
May 27 04:30:56 u-ThinkPad-X390-Yoga snapd[1066]: AppArmor status: apparmor is enabled and all features are available
May 27 04:30:56 u-ThinkPad-X390-Yoga snapd[1066]: AppArmor status: apparmor is enabled and all features are available
May 27 04:30:56 u-ThinkPad-X390-Yoga snapd[1066]: helpers.go:717: cannot retrieve info for snap ""gnome-calculator"": cannot find installed snap ""gnome-calculator"" at revision 406: missing file /snap/gnome-calculator/406/meta/snap.yaml
May 27 04:30:56 u-ThinkPad-X390-Yoga snapd[1066]: daemon.go:379: started snapd/2.38.1 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-1039-oem.
May 27 04:30:56 u-ThinkPad-X390-Yoga systemd[1]: Started Snappy daemon."
1828604,2019-05-27 08:58:08 UTC,"Tried below workaround, but it couldn't work for our case."
1828604,2019-05-27 09:59:20 UTC,"In bugsy-config, I found the base image had their own hook to install snaps, I doubt it's related to this issue. I just try to build a new image to verify it."
1828604,2019-05-27 12:49:38 UTC,Hi @binli
1828604,2019-05-28 05:35:37 UTC,"@Rex,"
1828604,2019-05-21 09:44:08 UTC,"Tried the old oem-image, I could not reproduce this issue."
1828606,2019-05-10 16:27:23 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1828606,2019-05-10 17:07:35 UTC,"OK, I used ""ubuntu-bug -w"" and the package seems to be ""nautilus 1:3.26.4-0~ubuntu18.04.4"""
1828606,2019-05-10 20:59:55 UTC,"Thank you for your bug report, the issue looks like an upsream one though, maybe you could report it to them on https://gitlab.gnome.org/GNOME/gvfs/issues ?"
1828606,2019-05-15 23:14:31 UTC,https://gitlab.gnome.org/GNOME/gvfs/issues/398
1828606,2019-05-16 09:06:47 UTC,Thanks
1828607,2019-11-27 00:36:17 UTC,"Reviewed:  https://review.opendev.org/658414
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=796309e571dcffc86b75ac9ab405904cc7c0c9bb
Submitter: Zuul
Branch:    master"
1828607,2019-05-24 16:11:40 UTC,"This RFE was discussed during the Neutron drivers meeting. It was approved as a ""directional RFE"", meaning that it sets a general direction over several cycles that will spawn several smaller efforts. There are three major goals to be achieved:"
1828607,2019-05-10 16:25:34 UTC,"Related fix proposed to branch: master
Review: https://review.opendev.org/658414"
1828607,2019-05-10 17:16:04 UTC,Ryan can we split this into multiple RFEs.
1828607,2019-05-10 17:30:07 UTC,We can. I went this route because the discussion at the PTG ended with an action item to create a spec.
1828608,2019-05-10 16:28:09 UTC,"If the problem only happens with a websockets channel enabled, it possibly a bug in the QIOChannelWebsock impl rather than the chardev"
1828608,2019-05-13 08:16:40 UTC,"I wrote a websocket client to help reproduce the bug without a browser:
https://github.com/anisse/websocktty"
1828609,2019-05-10 17:20:57 UTC,"https://launchpadlibrarian.net/423140934/VarLogDistupgradeAptlog.txt seems to suggest you have packages from multiple Ubuntu releases installed. If this can be confirmed, then this is more of a support case than a bug in the software."
1828609,2019-05-10 19:39:07 UTC,"Thanks Tom.  I will check whether I have multiple Ubuntu releases on
that computer and if so may submit a separate bug report as suggested."
1828609,2019-07-10 04:17:27 UTC,[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]
1828610,2020-04-16 18:16:27 UTC,"Reviewed:  https://review.opendev.org/716610
Committed: https://git.openstack.org/cgit/openstack/tooz/commit/?id=4d24f41e47c6a16fbb85ffce974e90e70d07ff76
Submitter: Zuul
Branch:    stable/stein"
1828610,2019-05-17 15:44:32 UTC,"Reviewed:  https://review.opendev.org/658204
Committed: https://git.openstack.org/cgit/openstack/tooz/commit/?id=8207427fffc72547387369ce7ba2696a86bf7626
Submitter: Zuul
Branch:    master"
1828610,2019-06-10 15:34:31 UTC,This issue was fixed in the openstack/tooz 1.65.0 release.
1828611,2019-07-18 21:09:06 UTC,Thanks for filing the issue and providing your workaround.
1828612,2020-01-21 15:27:41 UTC,"Try:
juju config hw-health ipmi_check_options=""--noentityabsent """
1828613,2019-06-09 22:32:26 UTC,Facing the same.
1828613,2019-05-13 22:28:04 UTC,apport information
1828613,2019-05-13 22:27:57 UTC,apport information
1828613,2019-05-13 22:28:01 UTC,apport information
1828613,2019-05-13 22:27:59 UTC,apport information
1828613,2019-05-13 22:27:55 UTC,apport information
1828613,2019-05-13 22:28:02 UTC,apport information
1828613,2019-05-13 22:27:53 UTC,apport information
1828613,2019-05-13 22:27:51 UTC,apport information
1828613,2019-05-13 22:27:49 UTC,apport information
1828613,2019-05-13 22:27:48 UTC,apport information
1828613,2019-05-13 22:27:47 UTC,apport information
1828613,2019-05-13 02:30:05 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828613,2019-05-13 02:18:04 UTC,"This sounds like bug 1821663. But because the fix for that bug is specific to laptop/motherboard models, we should keep this bug separate."
1828613,2019-05-13 22:27:54 UTC,apport information
1828615,2019-06-04 23:32:00 UTC,"The verification of the Stable Release Update for v4l2loopback has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828615,2019-06-04 23:31:56 UTC,This bug was fixed in the package v4l2loopback - 0.10.0-1ubuntu1.1
1828615,2019-06-04 23:26:07 UTC,I forgot to verify this for 4.15 in addition to 5.0. The package in -proposed (0.10.0-1ubuntu1.1) installs correctly without any compilation errors for 4.15 and 5.0.
1828615,2019-05-10 20:25:14 UTC,"The attachment ""v4l2loopback_0.10.0-1ubuntu1.1.debdiff"" seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff.  If the attachment isn't a patch, please remove the ""patch"" flag from the attachment, remove the ""patch"" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team."
1828615,2019-05-28 18:08:31 UTC,"Hello Connor, or anyone else affected,"
1828615,2019-05-11 18:13:46 UTC,"Could you also please file a bug in Debian, so we can pull the change down from there?"
1828615,2019-05-10 19:10:29 UTC,.debdiff attached to this comment.
1828615,2019-05-30 16:52:58 UTC,The package in -proposed (0.10.0-1ubuntu1.1) installs correctly without any compilation errors. Updating the verification tag on this bug.
1828616,2019-10-14 22:49:40 UTC,"@Janvi, yes, it's fixed in master.  (The Milestone field above gets set to the first version it's fixed in.)"
1828616,2019-10-14 19:37:40 UTC,"Stumble about this using (5.1.4-87-g78af1daa2)-1, release build at W10/10.0.18362.418
Its not only the tooltip, rather than the complete dialogs of some of the tools.
Several editors need complete restart of Kicad to switch i18n while others switch immediately.
Schematic, Symbol Editor, PCB and footprints behave well while
GerbView, BitMapConverter, Calculator and Layout Editor require Kicad restart to switch.
Sorry if already fixed in Master(?)"
1828616,2019-05-17 00:30:38 UTC,"Note that many of these don't have translations for whatever reason.  However Footprint Editor does, and now updates in real-time."
1828616,2019-05-17 00:06:03 UTC,"Every bug-fix carries a risk of regression.  I don't think this is important enough to put in 5.1.3, so I'm going to leave it 6.0-only unless I hear different."
1828617,2019-06-04 10:01:15 UTC,Let me word that last comment differently.
1828617,2019-06-04 11:55:17 UTC,Do you have access to the /var/log/ceph/ceph-volume-systemd.log after the latest reboot? That should give us some details such as:
1828617,2019-06-04 22:55:12 UTC,"The pvscan issue is likely something different, just wanted to make sure folks are aware of it for completeness."
1828617,2019-06-05 12:17:19 UTC,Any chance the log files got rotated and zipped? What does an ls of /var/log/ceph show?
1828617,2019-06-07 12:41:02 UTC,I chatted with xav in IRC and he showed me a private link to the log files. The ceph-volume-systemd.log.1 had timestamps of 2019-06-03 which matches up with the last attempt (see comment #37).
1828617,2019-06-07 12:54:18 UTC,Note that the code looks for wal/db devices in the block device's LV tags after it is found. In other words:
1828617,2019-08-29 22:25:41 UTC,This bug was fixed in the package ceph - 14.2.2-0ubuntu2
1828617,2019-06-12 13:02:21 UTC,Py2 bug found in code review upstream. Updated PPA again with fix.
1828617,2019-06-13 16:55:32 UTC,Just adding that I've worked around this issue with the following added to the lvm2-monitor overrides (/etc/systemd/system/lvm2-monitor.service.d/custom.conf):
1828617,2019-06-17 19:08:23 UTC,"@David, thanks for the update. We could really use some testing of the current proposed fix if you have a chance. That's in a PPA mentioned above. The new code will wait for wal/db devices to arrive and has env vars to adjust wait times - http://docs.ceph.com/docs/mimic/ceph-volume/systemd/#failure-and-retries."
1828617,2019-05-31 21:29:29 UTC,I've cherry-picked that patch to the package in the PPA if anyone can test. I'm fairly sure this will fix it as I've been testing and removing/adding the volume backed storage in my testing environment and it will wait for the wal/db devices for a while if they don't exist.
1828617,2019-07-03 11:41:49 UTC,Building in ppa:ci-train-ppa-service/3535 (will take a few hours).
1828617,2019-07-03 11:42:13 UTC,Alternative fix: https://github.com/ceph/ceph/pull/28791
1828617,2019-06-03 23:46:44 UTC,"After installing that PPA update and rebooting, the PV for the wal didn't come online till I ran pvscan --cache.  Seems a second reboot didn't do that though, might have been a red herring from prior attempts."
1828617,2019-09-05 12:32:40 UTC,"Hello Andrey, or anyone else affected,"
1828617,2019-09-30 08:20:14 UTC,This bug was fixed in the package ceph - 12.2.12-0ubuntu0.18.04.3
1828617,2019-09-06 07:30:21 UTC,"Hello Andrey, or anyone else affected,"
1828617,2019-10-30 11:56:55 UTC,"This bug was fixed in the package ceph - 12.2.12-0ubuntu0.18.04.3~cloud0
---------------"
1828617,2019-10-30 11:56:53 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1828617,2019-10-14 12:48:33 UTC,"This bug was fixed in the package ceph - 13.2.6-0ubuntu0.18.10.3~cloud0
---------------"
1828617,2019-10-14 12:48:31 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1828617,2019-10-14 12:45:23 UTC,"This bug was fixed in the package ceph - 13.2.6-0ubuntu0.19.04.4~cloud0
---------------"
1828617,2019-10-14 12:45:21 UTC,The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
1828617,2019-09-05 12:37:07 UTC,"Hello Andrey, or anyone else affected,"
1828617,2019-09-30 10:12:42 UTC,"Hello Andrey, or anyone else affected,"
1828617,2019-09-23 09:18:03 UTC,"The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828617,2019-09-20 13:20:43 UTC,Verification completed for bionic-rocky-proposed
1828617,2019-09-20 12:52:11 UTC,Verification completed on bionic-stein-proposed:
1828617,2019-09-20 07:36:43 UTC,"$ apt-cache policy ceph-osd
ceph-osd:
  Installed: 13.2.6-0ubuntu0.19.04.4
  Candidate: 13.2.6-0ubuntu0.19.04.4
  Version table:
 *** 13.2.6-0ubuntu0.19.04.4 500
        500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     13.2.6-0ubuntu0.19.04.3 500
        500 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages
     13.2.4+dfsg1-0ubuntu2 500
        500 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 Packages"
1828617,2019-09-19 10:14:07 UTC,bionic-proposed tested with a deployment using separate db and wal devices; OSD's restarted reliably over 10 x reboot iterations across three machines.
1828617,2019-09-06 07:31:06 UTC,"Hello Andrey, or anyone else affected,"
1828617,2019-09-23 09:28:03 UTC,This bug was fixed in the package ceph - 13.2.6-0ubuntu0.19.04.4
1828617,2019-05-31 21:11:49 UTC,Upstream pull request: https://github.com/ceph/ceph/pull/28357
1828617,2019-07-03 11:41:20 UTC,Alternative fix proposed upstream - picking this in preference to Corey's fix as its in the right part of the codebase for ceph-volume.
1828617,2019-05-31 14:52:45 UTC,The 'ceph-volume lvm trigger' call appears to come from ceph source at src/ceph-volume/ceph_volume/systemd/main.py.
1828617,2019-05-28 21:00:42 UTC,"Charm is cs:ceph-osd-284
Ceph version is 12.2.11-0ubuntu0.18.04.2"
1828617,2019-05-28 20:58:55 UTC,"Andrey, I don't know if you saw James' comment as yours may have coincided but if you can get the ceph-osd package version that would be helpful. Thanks!"
1828617,2019-05-28 14:53:04 UTC,"Yes, it is latest - the cluster is being re-deployed as part of Bootstack handover."
1828617,2019-05-28 14:37:13 UTC,"This feels similar to https://bugs.launchpad.net/charm-ceph-osd/+bug/1812925. First question, are you running with the latest stable charms which have the fix for that bug?"
1828617,2019-05-28 14:35:38 UTC,The ceph-osd package provide udev rules which should switch the owner for all ceph related LVM VG's to ceph:ceph.
1828617,2019-05-28 14:34:07 UTC,by-dname udev rules are created by MAAS/curtin as part of the server install I think.
1828617,2019-05-28 22:55:54 UTC,journalctl --no-pager -lu systemd-udevd.service >/tmp/1828617-1.out
1828617,2019-05-28 14:31:07 UTC,"Steve,
This is MAAS who creates these udev rules. We requested this feature to be implemented in order to be able to use persistent names in further services configuration (using templating). We couldn't go with /dev/sdX names as they may change after the reboot, and can't use wwn names as they are unique per node and don't allow us to use templates with FCB."
1828617,2019-05-23 03:40:58 UTC,"Just one update, if I change the perms of the symlink made (chown -h) the OSD will actually start."
1828617,2019-05-22 23:52:48 UTC,"Added field-critical, there's a cloud deploy ongoing where I currently can't reboot any hosts, nor get some of the OSDs back from a host I rebooted, until we have a workaround."
1828617,2019-05-22 23:45:30 UTC,"I'm seeing this in a slightly different manner, on Bionic/Queens."
1828617,2019-05-13 13:32:04 UTC,"This manifests itself as the following, as reported by lsblk(1). Note the missing Ceph LVM volume on the 6th NVME disk:"
1828617,2019-05-13 13:27:35 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828617,2019-05-31 16:07:30 UTC,Upstream ceph bug opened: https://tracker.ceph.com/issues/40100
1828617,2019-05-28 06:00:37 UTC,"> LVM module is supposed to create PVs from devices using the links in /dev/disk/by-dname/
> folder that are created by udev.
"
1828617,2019-05-28 22:58:03 UTC,udevadm info -e >/tmp/1828617-2.out
1828617,2019-05-28 14:42:17 UTC,"Please can you confirm which version of the ceph-osd package you have installed; older versions rely on a charm shipped udev ruleset, rather than it being provided by the packaging."
1828617,2019-05-29 18:39:31 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828617,2019-05-31 14:38:07 UTC,Thanks for testing. That should rule out udev as the cause of the race.
1828617,2019-05-31 01:45:52 UTC,"Hi,"
1828617,2019-05-29 12:17:37 UTC,Thanks for all the details.
1828617,2019-05-30 14:30:27 UTC,Referenced from:
1828617,2019-05-30 14:30:01 UTC,Some further references:
1828617,2019-05-30 14:16:10 UTC,Any output in /var/log/ceph/ceph-volume-systemd.log would also be useful
1828617,2019-05-30 14:12:53 UTC,The ceph-volume tool assembles and primes the OSD directory using the LV tags written during the prepare action - it would be good to validate these are OK with 'sudo lvs -o lv_tags'
1828617,2019-05-30 17:03:42 UTC,Note that there may only be a short window during system startup to catch missing tags with 'sudo lvs -o lv_tags'.
1828617,2019-05-30 11:46:32 UTC,"@Wouter, Thanks for testing. I'm rebuilding the package without the checks as they're probably preventing the udevadm settle from running. In the new build the 'udevadm settle --timeout=5' will run regardless. Let's see if that helps and then we can fine tune the checks surrounding the call later. Would you mind trying again once that builds (same PPA)?"
1828617,2019-05-30 02:43:56 UTC,"Hi,"
1828617,2019-05-29 21:21:35 UTC,"Thanks, will do.  FWIW, the symlinks are in place before reboot."
1828617,2019-05-29 19:42:46 UTC,I didn't recreate this but I did get a deployment on serverstack with bluestore WAL and DB devices. That's done with:
1828617,2019-05-29 21:13:48 UTC,I'm building a test package for ceph with additional logic added to /usr/lib/ceph/ceph-osd-prestart.sh to allow block.wal and block.db additional time to settle. This is just a version to test the fix. I'm not sure if the behavior is the same as journal file (symlink exists but file doesn't) but that's what I have in this change. Here's the PPA: https://launchpad.net/~corey.bryant/+archive/ubuntu/bionic-queens-1828617/+packages
1828617,2019-05-29 19:45:35 UTC,"Couple typos in comment #19:
I think bluestore-wal and bluestore-db needed 2G.
Also s/exists/exits"
1828617,2019-05-30 11:48:35 UTC,"@Wouter, since ceph takes so long to build you could also manually add 'udevadm settle --timeout=5' to /usr/lib/ceph/ceph-osd-prestart.sh across the ceph-osd units to test that."
1828619,2020-04-25 04:18:27 UTC,[Expired for OpenStack keystone charm because there has been no activity for 60 days.]
1828619,2020-02-24 15:05:11 UTC,"I've tried to reproduce this, but clearly I'm missing something.  Which versions of the charms were you using when this occurred?"
1828619,2019-05-10 21:02:05 UTC,The issue in #2 is due to https://bugs.launchpad.net/ubuntu/+source/neutron-fwaas-dashboard/+bug/1828293 based on the gathered outputs: https://paste.ubuntu.com/p/vh7jQKpYfQ/
1828619,2019-05-10 20:01:50 UTC,Noticed the same pattern with apache catching sigterm on openstack-dashboard units:
1828619,2019-05-10 19:49:42 UTC,"Unfortunately, while trying to trace it I restarted both backends which seems to have brought them into a healthy state."
1828619,2019-05-14 15:17:52 UTC,"Dmitrii, I've seen something like this before with keystone; I wondered if it was (in the case I was looking at) whether some apache processes were being 'held' (which due to WSGI held the keystone processes) and they were out of date and thus 500-ed.  Restarting apache (and killing any existing threads) resulted in a working keystone."
1828624,2019-05-22 16:10:47 UTC,"This came up a bit during the sprint latetly and we agree that the idea of ""juju run this hook and let me debug it"" via manual triggering is a really useful development idea."
1828625,2019-05-10 20:47:43 UTC,"And I guess the solution is in deleting ""exit 1"" on line 120 of bionic ppa-purge script"
1828629,2019-05-15 17:38:17 UTC,"Marking as low priority / not gating
As per above, the logs are available in a different location."
1828629,2019-05-15 19:22:35 UTC,"Thanks Angie,
Yes, logs in different location.
Able find Gnocchi version using kubectl logs command, as you have mentioned."
1828629,2019-05-15 15:11:15 UTC,"I have found two container for gnocchi-metricd, but those containers metricd.log file is not present.
please find the below logs."
1828629,2019-05-15 16:49:45 UTC,I just remember we don't have logs stored in the container. Seems as other services.
1828629,2019-05-14 20:03:24 UTC,"Angie,
Please let me know to find log file in container file system."
1828629,2019-05-10 21:57:17 UTC,"The openstack services are running in containers. The log files are present in the appropriate container, not on the controller filesystem."
1828629,2019-05-13 17:25:44 UTC,"Assigning to Angie to answer the above question.
I assume this bug is invalid given the logs were checked on the host filesystem"
1828629,2019-05-13 15:59:31 UTC,"Please let us know, how to find log(/var/log/gnocchi/metricd.log) in container file system?"
1828629,2019-05-15 14:22:39 UTC,"To find the gnocchi metricd containers:
kubectl get pods -n openstack | grep gnocchi-metricd"
1828630,2019-05-14 07:39:23 UTC,"This should certainly be able to be handled in the normal ceph upgrade code, but will take some thought on how to do it in the best way."
1828630,2019-05-20 21:05:00 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/660210"
1828630,2019-05-24 17:57:02 UTC,"Also, here's a command for checking what require_osd_release is set to:"
1828630,2019-05-30 15:43:23 UTC,"Reviewed:  https://review.opendev.org/660210
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-mon/commit/?id=63b38bf5ce7080c0c1f7b815efaf41e3c862c309
Submitter: Zuul
Branch:    master"
1828631,2019-05-10 22:03:26 UTC,The terminology problem originates with PCBNew where “flip” means move to the other side of the board.
1828631,2019-05-24 17:15:02 UTC,"Fixed in revision 43a5bb72ca8bcf812933f3818bd86649e7fdc3d7
https://git.launchpad.net/kicad/patch/?id=43a5bb72ca8bcf812933f3818bd86649e7fdc3d7"
1828631,2019-05-24 17:15:16 UTC,"@Michael, I merged your patch.  Thanks."
1828632,2019-07-02 15:22:52 UTC,I think this one is a duplicate of #1830433 (and the fix has been already applied to bionic).
1828632,2019-05-13 16:24:14 UTC,"dom xml is attached. netbeans is the version in bionic-updates/-security, 10.0-3~18.04.1ubuntu1."
1828632,2019-05-14 07:34:02 UTC,"Thanks Steve, but I'm still not able to reproduce the kernel crash. If I start netbeans, the current session is killed and I'm thrown back to the login screen. If I do this multiple times the VM eventually simply dies. But no kernel crash."
1828632,2019-05-10 22:00:08 UTC,This change was made by a bot.
1828632,2019-05-10 21:49:30 UTC,"In discussing this with Tyler Hicks, he noted that is a somewhat similar i386 PTI failure report:  https://lore<email address hidden>/ and that the response to it needs fixes from the tip/x86/mm branch. Is it possible that the bionic PTI i386 backports are missing some additional fixes?"
1828632,2019-05-13 16:11:51 UTC,I'm unable to reproduce this issue. Can you share your libvirt domain xml? And what version of netbeans are you using?
1828634,2019-05-11 05:31:22 UTC,"I'm sorry, I don't know what app you used to determine that update-notifier was writing to disk, but I don't think this analysis is correct.  update-notifier certainly *shouldn't* be writing to disk, and an strace of update-notifier on my desktop (Ubuntu 19.04, same as this report) over a 10minute+ interval confirms that no writes are happening.  So there's no evidence that polling once every 10 minutes has any effect other than a CPU wakeup, and once every 10 minutes is not that frequent for CPU wakeups."
1828634,2019-05-11 10:22:16 UTC,"Hello Steve, all,"
1828634,2019-05-12 10:41:07 UTC,"Hello,"
1828634,2019-05-12 11:07:56 UTC,So the bug is invalid right?
1828637,2019-05-23 18:48:52 UTC,Successful Bionic Maas deployment log with full proposed system upgrade set to True.
1828637,2019-05-27 16:26:14 UTC,This bug was fixed in the package cloud-init - 19.1-1-gbaa47854-0ubuntu1~16.04.1
1828637,2019-05-27 16:26:06 UTC,This bug was fixed in the package cloud-init - 19.1-1-gbaa47854-0ubuntu1~18.04.1
1828637,2019-05-27 16:25:53 UTC,This bug was fixed in the package cloud-init - 19.1-1-gbaa47854-0ubuntu1~18.10.1
1828637,2019-05-27 16:25:44 UTC,"The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828637,2019-05-27 16:25:39 UTC,This bug was fixed in the package cloud-init - 19.1-1-gbaa47854-0ubuntu1~19.04.1
1828637,2019-05-23 22:20:12 UTC,Attach file azure-sru-19.1.1.txt.
1828637,2019-05-23 19:22:42 UTC,Successful Xenail Maas deployment log with full proposed system upgrade set to True.
1828637,2019-05-23 00:06:59 UTC,"When deploying from maas, using this proposed version of cloud-init, the deployment fails. More detail is available in https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1830129"
1828637,2019-05-15 19:40:19 UTC,"Hello Chad, or anyone else affected,"
1828637,2019-05-22 21:35:52 UTC,Attach file nocloud-kvm-sru-19.1.1.txt.
1828637,2019-05-21 02:37:47 UTC,Attach file openstack-sru-19.1.1.txt.
1828637,2019-05-21 02:37:39 UTC,Attach file azure-sru-19.1.1.txt.
1828637,2019-05-21 02:37:31 UTC,Attach file gce-sru-19.1.1.txt.
1828637,2019-05-21 02:36:13 UTC,Attach file ec2-sru-19.1.1.txt.
1828637,2019-05-15 19:31:25 UTC,"Hello Chad, or anyone else affected,"
1828637,2019-05-15 18:40:01 UTC,"Hello Chad, or anyone else affected,"
1828637,2019-05-15 18:02:50 UTC,"Hello Chad, or anyone else affected,"
1828637,2019-05-22 21:36:03 UTC,Attach file nocloud-lxd-sru-19.1.1.txt.
1828639,2019-08-05 12:24:56 UTC,I just finished verifying the cosmic->disco upgrade (the reproducer). What is important:
1828639,2019-08-06 12:22:49 UTC,autopkgtest regressions have been fixed except for
1828639,2019-08-07 14:39:51 UTC,testing procedure:
1828639,2019-07-16 22:47:50 UTC,"All autopkgtests for the newly accepted dpkg (1.19.0.5ubuntu5.1) for cosmic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1828639,2019-08-08 08:40:13 UTC,"The verification of the Stable Release Update for dpkg has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828639,2019-08-13 15:31:52 UTC,This bug was fixed in the package dpkg - 1.18.4ubuntu1.6
1828639,2019-08-20 21:32:04 UTC,This bug was fixed in the package dpkg - 1.19.0.5ubuntu2.2
1828639,2019-08-07 15:09:20 UTC,disco:
1828639,2019-07-16 21:21:57 UTC,"All autopkgtests for the newly accepted dpkg (1.19.6ubuntu1.1) for disco have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1828639,2019-08-08 08:50:18 UTC,This bug was fixed in the package dpkg - 1.19.6ubuntu1.1
1828639,2019-07-16 20:17:09 UTC,"Hello Brian, or anyone else affected,"
1828639,2019-07-16 20:14:23 UTC,"All autopkgtests for the newly accepted dpkg (1.18.4ubuntu1.6) for xenial have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1828639,2019-07-16 19:10:44 UTC,"Hello Brian, or anyone else affected,"
1828639,2019-07-16 19:06:46 UTC,"Hello Brian, or anyone else affected,"
1828639,2019-07-16 19:00:05 UTC,"Hello Brian, or anyone else affected,"
1828639,2019-07-16 13:33:27 UTC,SRUs uploaded for all releases. git branches in
1828639,2019-07-11 16:01:22 UTC,"cosmic is reaching eol in 8 days, removing that task."
1828639,2019-07-04 12:28:49 UTC,I could verify this bug report in a lxd container and that dpkg 1.19.7 (not yet merged) fixes the issue.
1828639,2019-07-16 20:57:25 UTC,"All autopkgtests for the newly accepted dpkg (1.19.0.5ubuntu2.2) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures."
1828639,2019-07-04 12:27:17 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828641,2019-05-27 16:26:14 UTC,This bug was fixed in the package cloud-init - 19.1-1-gbaa47854-0ubuntu1~16.04.1
1828641,2019-05-27 16:26:06 UTC,This bug was fixed in the package cloud-init - 19.1-1-gbaa47854-0ubuntu1~18.04.1
1828641,2019-05-27 16:25:58 UTC,"The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions."
1828641,2019-05-23 22:42:00 UTC,"SRU verification of ubuntu-advantage retained behavior.
xenial expected fail (known bug)
bionic expected success
cosmic expected fail (invalid platform)
disco expected fail (known bug)"
1828641,2019-05-15 19:40:31 UTC,"Hello Chad, or anyone else affected,"
1828641,2019-05-15 19:31:38 UTC,"Hello Chad, or anyone else affected,"
1828641,2019-05-15 18:40:12 UTC,"Hello Chad, or anyone else affected,"
1828641,2019-05-27 16:25:53 UTC,This bug was fixed in the package cloud-init - 19.1-1-gbaa47854-0ubuntu1~18.10.1
1828643,2019-05-14 09:18:56 UTC,This is indeed a big oversight. Is this something you'd be interested to work on?
1828643,2019-05-14 10:37:56 UTC,"If you can give me some guidance on how to actually do this, i could do it. I have no experience with libffi though."
1828643,2019-05-14 12:29:00 UTC,"So, the first step is to learn how to set up callbacks using libffi. I'm guessing their Closure API is the way to go. You could do this in C first and then translate that to CFFI, or start with CFFI, depending on how familiar you are with CFFI. You definitely need to be familiar with C, I think. :-)"
1828643,2019-05-14 12:58:16 UTC,I'll try to check it out and will write back later.
1828643,2019-05-14 13:05:40 UTC,"Although it'd be nice to also know how libffi integrates with CFFI, since the libffi system is pretty small and i don't see direct places that explain passing strcutures by-value."
1828643,2019-05-14 18:54:49 UTC,"foreign-funcall-form/fsbv-with-libffi (
https://github.com/cffi/cffi/blob/master/libffi/funcall.lisp#L82) is the
main entry point."
1828643,2019-06-01 08:17:36 UTC,"It seems that `cffi:defcallback` doesn't currently use libffi for creation callbacks.
E.g. in case of sbcl, it calls `%defcallback`, that is defined in `cffi-sbcl.lisp` and calls SBCL's own `alien-sap`."
1828643,2019-06-01 09:43:30 UTC,"Alexey, that shouldn't be necessary. Have a look at how DEFCFUN (and FOREIGN-FUNCALL, etc) decides to use libffi when needed without resorting to an auxiliar DEFCFUN-LIBFFI."
1828648,2019-08-27 20:18:55 UTC,Fix cherry-picked into 5.1.x.
1828648,2019-08-21 19:35:18 UTC,"Fixed in revision 97212acecb87f1ba27a7e644a898eddb5ca46fc4
https://git.launchpad.net/kicad/patch/?id=97212acecb87f1ba27a7e644a898eddb5ca46fc4"
1828648,2019-08-27 19:50:44 UTC,"Here is an example using the ""MCU_NXP_ColdFire:MCF5328-BGA256"" symbol."
1828648,2019-08-27 19:51:34 UTC,"And here is the below nightly showing ""F9,F10,F11"":"
1828648,2019-05-11 00:05:16 UTC,"Looking more at the cell mentioned above, note the placement of the *10 and *11 ball number for each ball prefix. Sometimes *11 follows *10 and other times *10 is after *1 with *11 following *9."
1828649,2019-05-17 17:48:15 UTC,"# journalctl rotate
# journalctl --vacuum-time=1s
<logout of gnome xfree session>
<attempt login to gnome wayland session>
<computer locks up>
<power cycle laptop>
<login gnome xfree session>
journalctl -b-1 --no-pager > prevboot.txt"
1828649,2019-05-17 17:51:47 UTC,I believe I made a mistake in the steps taken above.
1828649,2019-05-20 02:24:34 UTC,"Re comment #5, yes that does sound like a mistake."
1828649,2019-07-19 04:17:31 UTC,[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]
1828649,2019-05-12 11:11:29 UTC,Thank you for your bug report. Could you add your journalctl log from a boot that got the issue?
1828649,2019-05-13 02:49:09 UTC,"We would need to see a system log containing the timeframe in which the freeze occured. To do this, please:"
1828652,2019-05-11 00:40:51 UTC,"BTW
This only occurs in Saved Searches. The regular search/replace works correctly with keyboard shortcuts."
1828652,2019-05-14 10:02:11 UTC,"I cannot replicate this. What keyboard shortcut are you using to trigger
the replace button? Alt+R?"
1828652,2019-05-14 10:02:52 UTC,"Note that Ctrl+R will trigger the replace button in the normal search
panel, not the saved search replace button."
1828655,2019-05-11 08:45:50 UTC,"@Robert, the fix should be in the next nightly (you're using the commit before)."
1828655,2019-05-11 08:35:41 UTC,Can confirm on Linux. Rotating a symbol also causes circles to increase in size (see screenshots attached).
1828657,2019-10-13 05:37:58 UTC,"It looks like there have been some changes in this area of the Linux kernel sometime around July, so I tried updating to the 5.4.0-rc2 upstream kernel today.  This updated kernel appears to fix the issue I've been having.  I'll run with the 5.4.0-rc2 kernel for now.  Hopefully the update that fixed the slow resume issue will be included in the next Ubuntu release."
1828657,2019-10-13 14:15:36 UTC,"It looks like there were some changes made to the upstream kernel in this area over the past few months, so I updated my kernel to upstream version 5.4.0-rc2.  This seems to address the slow resume problem.  I will run with the 5.4.0-rc2 kernel for now.  Hopefully, the changes that addressed this issue will be applied to the next Ubuntu release."
1828657,2019-10-18 22:28:33 UTC,I upgraded to Dawn Weasel (Ubuntu 19.10).  This issue is fixed in the 5.3 kernel supplied with Ubuntu 19.10 and can be closed.
1828657,2019-10-18 22:29:56 UTC,Fixed in Ubuntu 19.10
1828657,2019-05-14 12:30:04 UTC,This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
1828658,2019-06-06 05:05:36 UTC,You're fighting with charm-helpers here writing that out as 0600:
1828658,2019-09-08 23:27:39 UTC,Related upstream charm-helpers PR - https://github.com/juju/charm-helpers/pull/371
1828659,2019-10-26 14:34:06 UTC,https://www.bleachbit.org/news/bleachbit-30
1828659,2019-05-11 19:31:45 UTC,There's a comment here about the issue and way to patch your system
1828659,2019-05-11 22:09:48 UTC,Thanks Andrew. I will use the info in the link
1828660,2019-05-13 14:38:01 UTC,Are you sure the duplicates aren't filtered out in the nova/objects/instance.py _expected_cols function as a result of this change?
1828660,2019-05-13 15:02:13 UTC,I made this change on master and ran the functional tests and nothing failed so I think we'll need a more explicit recreate of the issue to move forward:
1828660,2019-05-14 08:29:23 UTC,The _expected_cols function won't filtered out duplicate items.I print parameters and find metadata in both columns_to_join_new and manual_joins.
1828660,2019-07-14 04:17:27 UTC,[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]
1828663,2019-07-19 00:42:28 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828663,2019-06-27 15:49:32 UTC,"Possibly related to Bug #1821415 ""pkexec fails in a non-graphical environment"""
1828663,2019-06-27 15:29:59 UTC,"I've found that there appears to be a fundamental bug in policykit and have added the upstream bug report covering it, which has been around for several years but the developers don't seem able to come up with a fix for."
1828663,2019-06-27 15:46:57 UTC,"Using gparted (which requires root access to the block storage devices) ""test"" user fails whilst original ""lubuntu"" user is successful:"
1828663,2019-06-26 23:29:43 UTC,There's a SIGSEGV; gdb bt full attached.
1828663,2019-06-23 02:13:03 UTC,"See the same error with two admin accounts.
synaptic-pkexec brings up the admin confirmation dialog but fails to authorize.
""Error executing command as another user: Not authorized"""
1828663,2019-06-23 02:05:05 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828663,2019-05-11 12:29:36 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1828663,2019-06-26 23:54:04 UTC,Looks like there may be two problems but I'm not familiar enough with the code bases to figure it out.
1828664,2019-12-18 03:33:11 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828664,2019-12-18 11:14:14 UTC,Also tagging snap since the issue is present on snaps that have run in the user session.
1828664,2019-12-18 22:01:01 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828664,2019-12-19 12:45:50 UTC,"It's unclear to me why you've added snapd to this bug. I'm setting it as Invalid, but if you have a reasoning please explain it and set it back to New so our triage picks it up again."
1828664,2019-12-19 13:40:18 UTC,@John
1828664,2019-12-19 14:07:24 UTC,@sean
1828665,2019-05-24 07:02:46 UTC,"For the confirmation, I'd need guidance.  Which source/mutter link to click to reinstall the prior version (or is it all of them?)."
1828665,2019-05-24 07:29:07 UTC,It sounds like this bug is now fixed(?). If so then we don't need any further investigation thanks.
1828665,2019-05-13 02:43:28 UTC,"Although 'mutter' isn't mentioned in the attached 'dpkg.log'. That may indicate the bug is not in mutter, or it may indicate that the assertion of 'dpkg.log' containing the regressed package might be wrong."
1828665,2019-05-13 02:40:18 UTC,"Sorry, I misread the dates."
1828665,2019-05-13 03:00:07 UTC,This change was made by a bot.
1828665,2019-05-13 02:37:37 UTC,Curious.
1828666,2019-05-11 10:28:07 UTC,The i7-6700k has the same network interface cards as the i7-6850k so not an issue with the cards.
1828666,2019-05-11 10:28:52 UTC,"Also, this machine is critical so I can not reboot frequently to test kernels and I have no other machines with this specific hardware to test with."
1828666,2019-05-11 10:30:08 UTC,This change was made by a bot.
1828666,2019-05-12 22:48:52 UTC,Was kind of hoping something severe enough to render the Operating System unusable on some platforms would get assigned someone and get a reasonable priority rather that sitting in limbo.
1828666,2019-06-04 23:10:33 UTC,"Hi Robert,"
1828666,2019-06-05 01:28:19 UTC,"      I can maybe do this but a 15 step bisection is not something I can do.
This machine needs to be in service 24x7 and it's 21 miles away, I have to
go there to reboot because when it comes up with no network then I'm stuck."
1828668,2019-05-16 20:02:30 UTC,If this is packaging related a issue should be raised on the relevant GitHub repo: https://github.com/KiCad
1828669,2019-11-11 15:17:45 UTC,Attaching Hardware info for my iMac
1828669,2019-11-11 15:21:26 UTC,Attaching output of `lspci -vk`
1828669,2020-02-04 06:42:27 UTC,"Please test this kernel:
https://people.canonical.com/~khfeng/lp1828669/"
1828669,2019-05-11 11:30:11 UTC,This change was made by a bot.
1828669,2019-11-11 15:12:55 UTC,My installation is also affected by this bug:
1828670,2019-05-11 11:31:56 UTC,Related to https://bugs.launchpad.net/kicad/+bug/1663896
1828671,2020-05-07 01:16:35 UTC,"From memory, there were bugs reported, but it seems it's:"
1828671,2020-05-01 13:04:52 UTC,Status changed to 'Confirmed' because the bug affects multiple users.
1828671,2020-05-06 16:56:06 UTC,Absolutely.
1828671,2020-05-01 16:23:45 UTC,Is that still an issue in newer series?
1828671,2020-05-06 21:18:15 UTC,"Thanks, it would be worth reporting upstream even if you don't have the debug cycles to investigate"
1828673,2019-07-06 20:10:53 UTC,Note that the hotkeys listed in the report were fixed earlier as part of https://bugs.launchpad.net/kicad/+bug/1835616.
1828673,2019-07-06 20:11:00 UTC,"Fixed in revision c600b758b384ce76288f2debcb851b516d5b919f
https://git.launchpad.net/kicad/patch/?id=c600b758b384ce76288f2debcb851b516d5b919f"
1828673,2019-07-07 02:06:34 UTC,"Hi Jeff, I think this was a fixing a different bug report"
1828673,2019-07-07 02:10:16 UTC,"Ah, found it.  This fix was https://bugs.launchpad.net/kicad/+bug/1835628"
1828673,2019-07-07 23:11:12 UTC,Oops; thanks for catching that Seth!
1828675,2019-05-11 16:22:00 UTC,"Thank you for taking the time to report this bug and helping to make Ubuntu better.  It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general.  It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it.  You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.  You might also ask for help in the #ubuntu-bugs irc channel on Freenode."
1828675,2020-01-25 19:44:44 UTC,We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
1828675,2020-03-26 04:17:47 UTC,[Expired for Ubuntu because there has been no activity for 60 days.]
1828676,2020-01-21 10:32:18 UTC,Still an issue on latest Ubuntu Focal with GNOME Software 3.34.2.
1828676,2019-05-13 15:12:48 UTC,"The icon 'system-help-symbolic' sounds like a weird one to use for ""education"", Ubuntu is shipping a ""?"" which is appropriate for help"
1828676,2019-05-12 13:46:28 UTC,"Thanks, I have reported it here: https://gitlab.gnome.org/GNOME/gnome-software/issues/663"
1828676,2019-05-12 14:40:01 UTC,Thanks!
1828676,2019-05-12 10:59:38 UTC,"Thank you for your bug report, that looks like an upstream issue
https://gitlab.gnome.org/GNOME/gnome-software/blob/master/plugins/core/gs-desktop-common.c#L306"
1828676,2019-05-13 15:06:18 UTC,"The upstream ticket was closed with: ""I think this is best tracked downstream. Sounds like Ubuntu isn't shipping the icon gnome-software needs."""
1828677,2019-05-14 06:09:04 UTC,"I have renamed ""E-Mail settings"" like you suggested. It's much better :-)"
1828677,2019-05-15 15:41:36 UTC,How is this keeping you from fixing up the text that you newly added to wlggz/templates/wlggz/edit_ggz.html in the merge request?
1828677,2019-05-15 06:56:46 UTC,Current state:
1828677,2019-05-13 21:08:40 UTC,"How about you just move the new tab next to the e-mail settings, so we wont alternate between content and settings tabs."
1828677,2019-05-13 17:12:10 UTC,+1
1828677,2019-05-13 20:37:26 UTC,"I guess ""Account Settings"" could lead into misunderstanding, because: The website account or the Metaserver account?"
1828677,2019-05-13 17:51:09 UTC,"How about joining the e-mail settings and the gaming password into 1 tab called ""Account Settings""? I see it like that a lot on other websites, so people should be able to find it there."
1828677,2019-05-13 16:49:04 UTC,I have made it as a tab now. Does this fit?
1828677,2019-05-12 17:44:50 UTC,Having it on the edit profile page directly will fit?
1828677,2019-05-13 21:05:35 UTC,removed superfluous tabs from profile page
1828677,2019-05-11 15:10:28 UTC,And I just noticed that the label has one colon to many:
1828678,2019-05-17 20:36:39 UTC,What do you mean by reset everything?
1828678,2019-05-16 19:15:03 UTC,It looks like something gone wrong with compiz settings. Try resetting everything. I can't reproduce this 19.10.
1828678,2019-05-16 13:32:26 UTC,I was wrong about this:
1828678,2019-05-16 13:38:19 UTC,Does anyone know of a workaround to bring a window into the screen? I can't believe there's no way to do that.
1828680,2019-05-11 15:05:48 UTC,Forgot to add that this is
1828680,2019-05-11 19:01:32 UTC,Ok. Got the gist of this. Are you just reporting an issue which you see as a bug or are you seeking help to print?
1828680,2019-05-15 11:30:48 UTC,"Hi Malte,"
1828680,2020-12-01 16:22:05 UTC,I can confirm this BUG
1828680,2020-12-01 16:23:05 UTC,"Package: hplip
Version: 3.20.3+dfsg0-2"
1828680,2020-12-06 22:16:04 UTC,A fix should be easy:
1828682,2019-05-15 17:00:33 UTC,A handy extension is available:
1828682,2019-05-14 10:08:02 UTC,"No upstream fix was released, the upstream ticket was just closed, for this reason: ""I don't think we can define ""system tools"" at all, it breaks down with all kinds of edge cases. For bugs like this you need to talk to the people in #gnome-design and if they agree they will give us new mockups to build. It's not the kind of thing we can just decide on our own, sorry."""
1828682,2019-05-13 04:27:15 UTC,"@Daniel: By setting the status ""Opinion"" for gnome-software (Ubuntu), you closed it. Was that your intention? Keeping it open as ""Wishlist"" is more appropriate, I think."
1828682,2019-05-13 02:28:31 UTC,Per the upstream bug:
1828682,2019-05-12 10:45:17 UTC,"It would be good to have design input on that, I'm not convinced that things like the system monitor, language-selector or usb creater should be moved outside the main list. That folder split seems a bit random, maybe it should be removed?"
1828682,2019-05-11 17:53:38 UTC,Please disregard my comment #2. I understand now that you are talking about grouping in the gnome-shell overview based on categories in the .desktop files.
1828682,2019-05-11 17:34:48 UTC,"Please, see: https://gitlab.gnome.org/GNOME/gnome-software/issues/642 and https://developer.gnome.org/AppFolders/"
1828682,2019-05-11 17:10:48 UTC,What Utilities folder?
1828682,2019-05-11 16:47:40 UTC,"Please look at <https://packages.debian.org/unstable/>. What makes you think that ""Utilities"" is the most proper section for all those packages?"
1828682,2019-05-11 15:56:05 UTC,The Snap version of System Monitor seems to have this issue as well on latest Ubuntu 19.04.
1828682,2019-05-11 20:23:56 UTC,Maybe post about it at <https://discourse.ubuntu.com/c/desktop> to have a discussion on the desirable way to organize the icons on Ubuntu.
1828682,2019-05-11 17:33:01 UTC,"Ah, so I finally get it."
1828685,2019-05-15 21:07:05 UTC,Thanks for filing this bug. I believe this falls under the umbrella of bug #216847
1828685,2019-05-15 22:09:32 UTC,"Le 15/05/2019 à 23:07, Andreas Hasenack a écrit :

> *** This bug is a duplicate of bug 216847 ***
>      https://bugs.launchpad.net/bugs/216847
>
> Thanks for filing this bug. I believe this falls under the umbrella of
> bug #216847
>
> ** This bug has been marked a duplicate of bug 216847
>     sshd will not start at boot if ListenAddress is set, because network interface is not yet up
>


Hi,"
1828689,2019-05-12 14:14:20 UTC,You can use the footprint browser found in the view menu. It would however be really nice if it was possible to open a footprint for editing from it.
1828689,2019-05-12 19:34:54 UTC,"Good point, but that feels like a nesting doll of library browser windows. :)"
1828690,2019-08-07 10:57:25 UTC,Fixed in repository. Should be take some time until the changes are synchronized with the web server.
1828691,2019-05-13 10:07:28 UTC,"Fix proposed to branch: master
Review: https://review.opendev.org/658779"
1828691,2020-11-19 15:43:08 UTC,"Change abandoned by Michał Dulko (<email address hidden>) on branch: master
Review: https://review.opendev.org/658779"